diff --git a/src/helper_scripts/cleaning_scripts/0217_ve_phab_comments.csv b/src/helper_scripts/cleaning_scripts/0217_ve_phab_comments.csv
new file mode 100644
index 0000000..6b24987
--- /dev/null
+++ b/src/helper_scripts/cleaning_scripts/0217_ve_phab_comments.csv
@@ -0,0 +1,192743 @@
+task_title,comment_text,date_created,AuthorPHID,TaskPHID,comment_type,status
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"When running Echo extensions tests under HHVM/Zend, Jenkins ends up with a failure:
+
+```
+1) EchoTitleLocalCacheTest::testGet
+Failed asserting that null is an instance of class ""Title"".
+
+extensions/Echo/tests/phpunit/includes/cache/TitleLocalCacheTest.php:37
+tests/phpunit/MediaWikiTestCase.php:141
+```
+
+In a workspace with the following extensions:
+
+mediawiki/extensions/Echo
+mediawiki/extensions/JsonConfig
+mediawiki/extensions/Mantle
+mediawiki/extensions/MobileApp
+mediawiki/extensions/MobileFrontend
+mediawiki/extensions/VisualEditor
+mediawiki/extensions/WikiGrok
+mediawiki/extensions/ZeroBanner
+mediawiki/extensions/ZeroPortal
+
+
+Running the Echo tests standalone pass ( php tests/phpunit/phpunit.php extensions/Echo )
+
+The whole testsuite fails though:
+```
+cd tests/phpunit
+php phpunit.php --testsuite extensions
+```
+
+Or slightly faster:
+```
+cd tests/phpunit
+php phpunit.php --testsuite extensions --filter 'Echo' --stop-on-failure
+```",1418676203,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_description,resolved
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,Filed separately as T88039 since that one is not related to HHVM.,1422579129,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,Filed separately as T88039.,1422579113,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Failed again just now:
+
+https://integration.wikimedia.org/ci/job/mwext-Flow-testextension-zend/344/consoleFull",1422575320,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184420 abandoned by Hashar:
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184420]]",1421532092,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184420 had a related patch set uploaded (by Hashar):
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184420]]
+
+#patch-for-review",1421094198,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"I have pushed the fix to 1.25wmf13 and 1.25wmf14 mediawiki/core branches (and ""deployed"").",1421075512,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184344 merged by jenkins-bot:
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184344]]",1421072935,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184343 merged by jenkins-bot:
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184343]]",1421072933,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184344 had a related patch set uploaded (by Hashar):
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184344]]
+
+#patch-for-review",1421072694,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184343 had a related patch set uploaded (by Hashar):
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184343]]
+
+#patch-for-review",1421072672,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,Merged in by Matthias \O/,1420817606,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 183840 merged by jenkins-bot:
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/183840]]",1420817440,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"The patch [[ https://gerrit.wikimedia.org/r/183840 | 183840 ]] for Echo does fix the job testing multiple extensions together:
+ 
+https://integration.wikimedia.org/ci/job/mediawiki-phpunit-integration-hhvm/15/console
+
+Pending review/merge.",1420810604,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 183840 had a related patch set uploaded (by Hashar):
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/183840]]
+
+#patch-for-review",1420808267,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Could someone from the #Collaboration-Team assist in tracking down this bug?  I have looked a bit at the cache code and attempted to debug it but eventually got lost in the code :-/
+
+The way to reproduce:
+
+Clone core / vendor and:
+
+mediawiki/extensions/Echo
+mediawiki/extensions/JsonConfig
+mediawiki/extensions/Mantle
+mediawiki/extensions/MobileApp
+mediawiki/extensions/MobileFrontend
+mediawiki/extensions/VisualEditor
+mediawiki/extensions/WikiGrok
+mediawiki/extensions/ZeroBanner
+mediawiki/extensions/ZeroPortal
+
+Setup a basic wiki via maintenance/install.php
+
+```
+cd tests/phpunit
+php phpunit.php --testsuite extensions --filter 'Echo' --stop-on-failure
+```
+
+Should fails.
+
+If one only run the Echo tests they pass ( php tests/phpunit.php extensions/Echo ).
+
+
+
+
+",1420729467,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"I forgot to reopen this task, see above for a way to reproduce.",1420711820,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Example to reproduce:
+
+```
+cd tests/phpunit
+php phpunit.php --testsuite extensions --filter 'Echo' --stop-on-failure
+```
+
+There must be a race condition somewhere in the MRU Cache or Title local cache.",1420557287,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"The standalone job pass now https://integration.wikimedia.org/ci/job/mwext-Echo-testextension-hhvm/3/  but fails when being run with other extensions https://integration.wikimedia.org/ci/job/mediawiki-phpunit-integration-hhvm/11/console
+
+That last job uses:
+
+mediawiki/extensions/Echo
+mediawiki/extensions/JsonConfig
+mediawiki/extensions/Mantle
+mediawiki/extensions/MobileApp
+mediawiki/extensions/MobileFrontend
+mediawiki/extensions/VisualEditor
+mediawiki/extensions/WikiGrok
+mediawiki/extensions/ZeroBanner
+mediawiki/extensions/ZeroPortal
+
+I can reproduce the failure on my local install using Zend",1420551626,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,I couldn't get MediaWiki-Vagrant to work to reproduce this.,1420495047,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"You can trigger the hhvm job on an Echo proposed patch by commenting in Gerrit: ""check experimental"".  That will run a build of https://integration.wikimedia.org/ci/job/mwext-Echo-testextension-hhvm/",1418737731,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+VisualEditor has been disabled unexpectedly on fr.wiktionary,"Hi,
+
+Visual Editor has been enabled on fr.wikt after https://phabricator.wikimedia.org/T65187 ; but now it has been disabled, it seems since last night (maybe since the installation of the version 1.25wmf9 of MediaWiki).
+
+Any idea?",1417040370,PHID-USER-76b52mrhaky23u2wzwmg,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_description,resolved
+VisualEditor has been disabled unexpectedly on fr.wiktionary,So sorry about this; now fixed.,1417046899,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_subcomment,NA
+VisualEditor has been disabled unexpectedly on fr.wiktionary,"Change 176182 merged by jenkins-bot:
+Followup 313c29f: correct spelling of wiktionary
+
+[[https://gerrit.wikimedia.org/r/176182]]",1417046763,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_subcomment,NA
+VisualEditor has been disabled unexpectedly on fr.wiktionary,"Change 176182 had a related patch set uploaded (by Catrope):
+Followup 313c29f: correct spelling of wiktionary
+
+[[https://gerrit.wikimedia.org/r/176182]]
+
+#patch-for-review",1417046167,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_subcomment,NA
+VisualEditor has been disabled unexpectedly on fr.wiktionary,"Hey, yes, sorry, it looks like we broke this. My apologies; will get it fixed.",1417040870,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_subcomment,NA
+VisualEditor does not open at en.wikipedia.beta.wmflabs.org,"- go to http://en.wikipedia.beta.wmflabs.org/
+- log in as Selenium user
+- make sure VisualEditor is enabled at http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences#mw-prefsection-betafeatures
+- go to http://en.wikipedia.beta.wmflabs.org/wiki/Language_Screenshot?veaction=edit
+- VisualEditor never opens
+- the loading bar in the top-right part of the screen just cycles (see screen shot) {F15998}",1416911298,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-j7cnykjnzlc5nu27zqtt,task_description,duplicate
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416275760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hlczvkjyex42kxtfvcdr,task_description,resolved
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified the fix in en.wiki,1417044518,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hlczvkjyex42kxtfvcdr,task_subcomment,NA
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified the fix in Betalabs and test2,1416275919,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hlczvkjyex42kxtfvcdr,task_subcomment,NA
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Fixed by 
+
+Followup ca6a16f: use parent selector both for hiding and showing windows
+
+https://gerrit.wikimedia.org/r/173977",1416275894,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hlczvkjyex42kxtfvcdr,task_subcomment,NA
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"From Ritu Swain:
+
+Reopen this issue.
+In test2 and beta only.
+
+steps-
+
+1> open the link/math/comment/special characters/ inspectors in Media Settings -> caption sub-editor or the References sub-editor. The inspectors are blank with no UI.
+
+Also see Bug 68130 https://bugzilla.wikimedia.org/show_bug.cgi?id=68130.",1416275852,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hlczvkjyex42kxtfvcdr,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"see e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Links_VisualEditor_Test?vehidebetadialog=true&veaction=edit
+
+see screen shot for error
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1415899860,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-6stmkadongdngovinrsy,task_description,resolved
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,I'm not sure why OCG broke or what that is but this would have been noticed if things ran tests for extensions that depended on them. In this case MobileFrontend should run qunit and phpunit tests for zero and Mantle should run qunit and phpunit on Flow and MobileFrontend,1415931146,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,*** Bug 73375 has been marked as a duplicate of this bug. ***,1415921818,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Please correct me if I am wrong:
+
+The change https://gerrit.wikimedia.org/r/#/c/168233/ to Mantle removed a bunch of javascript which turned out to be used by several other extensions (ZeroBanner and OCG at least).
+
+I guess running the qunit tests of ZeroBanner and OCG with that Mantle patch applied would have caught the issue. If someone has some spare time to verify that it would be rather nice.
+
+From there, I am willing to have a generic qunit job that will tests together all extensions having qunit jobs. This way if Mantle change something, the other extensions would complain.  Does that sounds like a good idea?",1415917656,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Beta labs is working again. Thanks Jon and Jeff.
+
+No need to add anything to anything because merged changes are deployed to beta labs automatically.",1415911888,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,(it's going to be easier to update Zero than Mantle and all its dependencies),1415911758,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,Greg does the patch solve the issue? Can we just add to the build?,1415911638,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"To be clear:
+This is breaking A LOT OF THINGS, pretty much all browser tests are failing all day due to bits not responding.
+
+Jon/Jeff: Can you just revert the change ASAP? The ""build is broken"" as it were, we can't leave it broken all day.",1415910756,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"This is breaking the OCG progress bar in beta as well.
+
+I'm assuming/hoping that Top Men are hard are work on this, and the bug won't survive into production?",1415910491,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Change 173069 merged by jenkins-bot:
+Use templates in core to avoid fatals
+
+https://gerrit.wikimedia.org/r/173069",1415909747,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Change 173069 had a related patch set uploaded by Jdlrobson:
+Use templates in core to avoid fatals
+
+https://gerrit.wikimedia.org/r/173069",1415906602,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,Jeff Hobson and I will work to get this fixed asap.,1415905615,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,This looks like it is coming from Zero. I didn't realise they were using this class. I had thought the deprecation warning had been running for long enough to remove it. Will chat to Adam.,1415905390,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/9dGlL33Y",1415903714,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,(Not a Beta Cluster bug),1415903685,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,This commit <https://gerrit.wikimedia.org/r/#/c/168233/> is breaking ZeroBanner <https://github.com/wikimedia/mediawiki-extensions-ZeroBanner/commit/c930255ed39ef11288d5e9e079fa5cd5837675b6>,1415903511,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Nov 13 18:22:44 deployment-mediawiki01 hhvm: #012Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506
+Nov 13 18:22:44 deployment-mediawiki01 hhvm: {#012    ""message"": ""Class undefined: ResourceLoaderTemplateModule"",#012    ""file"": ""/srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php"",#012    ""line"": 506,#012    ""context"": [],#012    ""backtrace"": [#012        {#012            ""file"": ""/srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php"",#012            ""line"": 506#012        },#012        {#012            ""file"": ""/srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php"",#012            ""line"": 111,#012            ""function"": ""getModule"",#012            ""class"": ""ResourceLoader"",#012            ""type"": ""->"",#012            ""args"": [#012                ""zerobanner""#012            ]#012        },#012        {#012            ""file"": ""/srv/mediawiki/php-master/includes/resourceloader/ResourceLoaderStartUpModule.php"",#012            ""line"": 438,#012            ""function"": ""preloadModuleInfo"",#012            ""class"": ""ResourceLoader"",#012            ""type"": ""->"",#012            ""args"": [#012                [#012                    ""site"",#012                    ""noscript"",#012                    ""startup"",#012                    ""filepage"",#012                    ""user.groups"",#012                    ""user"",#012                    ""user.cssprefs"",#012                    ""user.options"",#012                    ""user.tokens"",#012                    ""mediawiki.language.data"",#012                    ""mediawiki.skinning.elements"",#012                    ""mediawiki.skinning.content"",#012                    ""mediawiki.skinning.interface"",#012                    ""mediawiki.skinning.content.parsoid"",#012                    ""mediawiki.skinning.content.externallinks"",#012                    ""jquery"",#012                    ""jquery.accessKeyLabel"",#012                    ""jquery.appear"",#012                    ""jquery.arrowSteps"",#012                    ""jquery.async"",#012                    ""jquery.autoEllipsis"",#012                    ""jquery.badge"",#012                    ""jquery.byteLength"",#012                    ""jquery.byteLimit"",#012                    ""jquery.checkboxShiftClick"",#012                    ""jquery.chosen"",#012                    ""jquery.client"",#012                    ""jquery.color"",#012                    ""jquery.colorUtil"",#012                    ""jquery.confirmable"",#012                    ""jquery.cookie"",#012                    ""jquery.expandableField"",#012                    ""jquery.farbtastic"",#012                    ""jquery.footHovzer"",#012                    ""jquery.form"",#012                    ""jquery.fullscreen"",#012                    ""jquery.getAttrs"",#012                    ""jquery.hidpi"",#012                    ""jquery.highlightText"",#012                    ""jquery.hoverIntent"",#012                    ""jquery.localize"",#012                    ""jquery.makeCollapsible"",#012                    ""jquery.mockjax"",#012                    ""jquery.mw-jump"",#012                    ""jquery.mwExtension"",#012                    ""jquery.placeholder"",#012                    ""jquery.qunit"",#012                    ""jquery.qunit.completenessTest"",#012                    ""jquery.spinner"",#012                    ""jquery.jStorage"",#012                    ""jquery.suggestions"",#012                    ""jquery.tabIndex"",#012                    ""jquery.tablesorter"",#012                    ""jquery.textSelection"",#012                    ""jquery.throttle-debounce"",#012                    ""jquery.validate"",#012                    ""jquery.xmldom"",#012                    ""jquery.tipsy"",#012                    ""jquery.ui.core"",#012                    ""jquery.ui.accordion"",#012                    ""jquery.ui.autocomplete"",#012                    ""jquery.ui.button"",#012                    ""jquery.ui.datepicker"",#012                    ""jquery.ui.dialog"",#012                    ""jquery.ui.draggable"",#012                    ""jquery.ui.droppable"",#012                    ""jquery.ui.menu"",#012                    ""jquery.ui.mouse"",#012                    ""jquery.ui.position"",#012                    ""jquery.ui.progressbar"",#012                    ""jquery.ui.resizable"",#012                    ""jquery.ui.selectable"",#012                    ""jquery.ui.slider"",#012                    ""jquery.ui.sortable"",#012                    ""jquery.ui.spinner"",#012                    ""jquery.ui.tabs"",#012                    ""jquery.ui.tooltip"",#012                    ""jquery.ui.widget"",#012                    ""jquery.effects.core"",#012                    ""jquery.effects.blind"",#012                    ""jquery.effects.bounce"",#012                    ""jquery.effects.clip"",#012                    ""jquery.effects.drop"",#012                    ""jquery.effects.explode"",#012                    ""jquery.effects.fade"",#012                    ""jquery.effects.fold"",#012                    ""jquery.effects.highlight"",#012                    ""jquery.effects.pulsate"",#012                    ""jquery.effects.scale"",#012                    ""jquery.effects.shake"",#012                    ""jquery.effects.slide"",#012                    ""jquery.effects.transfer"",#012                    ""json"",#012                    ""moment"",#012                    ""mediawiki"",#012                    ""mediawiki.apihelp"",#012                    ""mediawiki.template"",#012                    ""mediawiki.apipretty"",#012                    ""mediawiki.api"",#012                    ""mediawiki.api.category"",#012                    ""mediawiki.api.edit"",#012                    ""mediawiki.api.login"",#012                    ""mediawiki.api.parse"",#012                    ""mediawiki.api.watch"",#012                    ""mediawiki.content.json"",#012                    ""mediawiki.confirmCloseWindow"",#012                    ""mediawiki.debug"",#012                    ""mediawiki.debug.init"",#012                    ""mediawiki.feedback"",#012                    ""mediawiki.hidpi"",#012                    ""mediawiki.hlist"",#012                    ""mediawiki.htmlform"",#012                    ""mediawiki.icon"",#012                    ""mediawiki.inspect"",#012                    ""mediawiki.notification"",#012                    ""mediawiki.notify"",#012                    ""mediawiki.pager.tablePager"",#012                    ""mediawiki.searchSuggest"",#012                    ""mediawiki.Title"",#012                    ""mediawiki.toc"",#012                    ""mediawiki.Uri"",#012                    ""mediawiki.user"",#012                    ""mediawiki.userSuggest"",#012                    ""mediawiki.util"",#012                    ""mediawiki.cookie"",#012                    ""mediawiki.toolbar"",#012                    ""mediawiki.action.edit"",#012                    ""mediawiki.action.edit.styles"",#012                    ""mediawiki.action.edit.collapsibleFooter"",#012                    ""mediawiki.action.edit.preview"",#012                    ""mediawiki.action.history"",#012                    ""mediawiki.action.history.diff"",#012                    ""mediawiki.action.view.dblClickEdit"",#012                    ""mediawiki.action.view.metadata"",#012                    ""mediawiki.action.view.postEdit"",#012                    ""mediawiki.action.view.redirect"",#012                    ""mediawiki.action.view.redirectPage"",#012                    ""mediawiki.action.view.rightClickEdit"",#012                    ""mediawiki.action.edit.editWarning"",#012                    ""mediawiki.language"",#012                    ""mediawiki.cldr"",#012                    ""mediawiki.libs.pluralruleparser"",#012                    ""mediawiki.language.init"",#012                    ""mediawiki.jqueryMsg"",#012                    ""mediawiki.language.months"",#012                    ""mediawiki.language.names"",#012                    ""mediawiki.libs.jpegmeta"",#012                    ""mediawiki.page.gallery"",#012                    ""mediawiki.page.ready"",#012                    ""mediawiki.page.startup"",#012                    ""mediawiki.page.patrol.ajax"",#012                    ""mediawiki.page.watch.ajax"",#012                    ""mediawiki.page.image.pagination"",#012                    ""mediawik",1415903021,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,Failed to load resource: the server responded with a status of 503 (Service Unavailable) http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*,1415900551,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"As visible in the first line of your screenshot, there's a load.php request that's 503ing. For me, it's an earlier load.php request that 503s (the startup request), and so I don't get the error, but no JavaScript works.
+
+Is beta labs broken again?",1415900104,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Created attachment 17121
+Reference error
+
+**Attached**: {F15211}",1415899926,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","screenshot
+
+""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker
+
+**Attached**: {F15023}",1415213160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_description,resolved
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",Verified the fix in production,1416446814,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 172440 abandoned by Catrope:
+Followup d4c133b: also make TargetEvents depend on ve.track()
+
+Reason:
+Sorry, this was not a wmf7 regression, so this should not be cherry-picked
+
+https://gerrit.wikimedia.org/r/172440",1415663293,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 172440 had a related patch set uploaded by Catrope:
+Followup d4c133b: also make TargetEvents depend on ve.track()
+
+https://gerrit.wikimedia.org/r/172440",1415663118,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 172431 merged by jenkins-bot:
+Followup d4c133b: also make TargetEvents depend on ve.track()
+
+https://gerrit.wikimedia.org/r/172431",1415662611,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 172431 had a related patch set uploaded by Catrope:
+Followup d4c133b: also make TargetEvents depend on ve.track()
+
+https://gerrit.wikimedia.org/r/172431",1415660295,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",latest failures is https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/322/testReport/junit/(root)/VisualEditor%20Mobile/Switch_from_VisualEditor_to_source_editor/,1415660157,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","new js error from logged in user e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Sextet#/editor/0 is 
+
+Uncaught TypeError: undefined is not a function VM156:850ve.init.mw.TargetEvents.track VM156:850(anonymous function) VM156:840(anonymous function) load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:46fire load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:44self.fireWith load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:46done load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:135callback load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:141",1415659958,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",Verified the fix in test2,1415227876,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",Verified the fix in Betalabs,1415218406,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 171306 merged by jenkins-bot:
+Follow-up 07251d0: Add mobile target to RangeFix
+
+https://gerrit.wikimedia.org/r/171306",1415214648,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 171306 had a related patch set uploaded by Catrope:
+Followup 07251d0: add mobile target to rangefix
+
+https://gerrit.wikimedia.org/r/171306",1415214210,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",*** Bug 73039 has been marked as a duplicate of this bug. ***,1415213710,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"Can't work out why; supportedSelections is set for both.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1415152200,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nohpzqcpzjmuxbicpotc,task_description,resolved
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"Verified the fix in Betalabs,test2 and production.",1415657798,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),Fix now live in production.,1415233236,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"**gerritadmin** wrote:
+
+Change 171451 merged by jenkins-bot:
+Followup 31bafa1: forgot to rename 'data' to 'args' for citation commands
+
+https://gerrit.wikimedia.org/r/171451",1415232673,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"**gerritadmin** wrote:
+
+Change 171451 had a related patch set uploaded by Jforrester:
+Followup 31bafa1: forgot to rename 'data' to 'args' for citation commands
+
+https://gerrit.wikimedia.org/r/171451",1415224619,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"**gerritadmin** wrote:
+
+Change 171447 merged by jenkins-bot:
+Followup 31bafa1: forgot to rename 'data' to 'args' for citation commands
+
+https://gerrit.wikimedia.org/r/171447",1415224584,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"**gerritadmin** wrote:
+
+Change 171447 had a related patch set uploaded by Catrope:
+Followup 31bafa1: forgot to rename 'data' to 'args' for citation commands
+
+https://gerrit.wikimedia.org/r/171447",1415224131,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,"Steps to reproduce:
+
+1.Insert any template in the page
+
+Observed Result:
+VE gets completely unresponsive after this action,Cannot make any other change or save the page. No error in the console.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1415127300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k34jgliglfher6oyvsj3,task_description,resolved
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,Verified the fix in production,1415834025,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,Verified the fix in test2,1415228528,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,Verified the fix in Betalabs,1415128541,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,"**gerritadmin** wrote:
+
+Change 170991 merged by jenkins-bot:
+Followup 0165a53: don't store an mw.Title object instead of a string in TemplateModel
+
+https://gerrit.wikimedia.org/r/170991",1415127764,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,"**gerritadmin** wrote:
+
+Change 170991 had a related patch set uploaded by Catrope:
+Followup 0165a53: don't store an mw.Title object instead of a string in TemplateModel
+
+https://gerrit.wikimedia.org/r/170991",1415127629,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","On any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click Cite/Website or any other Cite selection. 
+
+Nothing happens. No Cite inspector appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415111400,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-s4icej2snebqglex3pcn,task_description,resolved
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined """,The fix is re-verified in betalabs and test2.,1415234910,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined """,Opening a distinct bug for that one.,1415151534,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined """,This started happening again? Although not for basic reference but for citations and no error in console this time,1415147217,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","Verified in betalabs  - Safari, Chrome, and FF.",1415128323,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","**gerritadmin** wrote:
+
+Change 170985 merged by jenkins-bot:
+Followup 0165a53: fix typo causing undefined to be passed to mw.Title
+
+https://gerrit.wikimedia.org/r/170985",1415127378,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","**gerritadmin** wrote:
+
+Change 170985 had a related patch set uploaded by Catrope:
+Followup 0165a53: fix typo causing undefined to be passed to mw.Title
+
+https://gerrit.wikimedia.org/r/170985",1415127276,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","js error is ""TypeError: title is undefined""",1415112905,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a template for example: Cite Web/Citation needed
+3.Save the page
+4.Reopen the page
+5.Reopen the Transclusion dialog for the template you just added
+
+Observed Result:
+Instead of the template dialog with all the parameters in it , it appears as an empty ""Add Template"" dialog 
+
+See the screenshot attached
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14841}",1414622880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,Verified the fix in production,1415834079,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,Verified the fix in test2,1415228454,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,Verified the fix in Betalabs,1414703204,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,Fixed by: https://gerrit.wikimedia.org/r/169966,1414703188,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_subcomment,NA
+VisualEditor: Clicking in a table that contains templated rows causes JS error,"1. Go to http://en.wikipedia.beta.wmflabs.org/wiki/User:RoanKattouw/Evil_table?veaction=edit
+2. Click on a non-templated cell in the table (e.g. the cell that says ""simple"" in row 2)
+3. ""undefined is not a function"" error appears in console
+
+What happens is that TableMatrix#update runs, and when it hits cell (2,0) (3rd row, 1st column), it will find that cellNode is a ve.dm.MWTransclusionNode rather than a ve.dm.TableCellNode, and so calling .getRowSpan() on it will explode.
+
+We probably need some way to deal with templated rows/cells in the middle of an otherwise normal table, but I'm not entirely sure what that should look like. Maybe we can get away with skipping over these rows/cells everywhere in a consistent manner, and hopefully that will work out OK?
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1414622340,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dnykg7zlhhhsxuhitddq,task_description,resolved
+VisualEditor: Clicking in a table that contains templated rows causes JS error,Verified with the Evil_table given in the link - the js error is not displayed anymore.,1415234703,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dnykg7zlhhhsxuhitddq,task_subcomment,NA
+VisualEditor: Clicking in a table that contains templated rows causes JS error,"**gerritadmin** wrote:
+
+Change 170245 merged by jenkins-bot:
+Add support for non-table nodes in tables (e.g. aliens)
+
+https://gerrit.wikimedia.org/r/170245",1415041463,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dnykg7zlhhhsxuhitddq,task_subcomment,NA
+VisualEditor: Clicking in a table that contains templated rows causes JS error,"**gerritadmin** wrote:
+
+Change 170245 had a related patch set uploaded by Esanders:
+Add support for non-table nodes in tables (e.g. aliens)
+
+https://gerrit.wikimedia.org/r/170245",1414710274,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dnykg7zlhhhsxuhitddq,task_subcomment,NA
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,"Steps to reproduce:
+
+* Open https://en.wikipedia.org/wiki/Snowman?veaction=edit
+
+* Mark the sentence ""It was 113 feet 7 inches (34.62 m) tall and weighed over 9,000,000 pounds (4,080,000 kg).[1]"" and cut it (Strg+X).
+
+* Paste it in again (Strg+V).
+
+* Click before ""It"" to place the cursor at the beginning of the sentence.
+
+
+Result: The editor starts adding copies of the sentence in an endless loop, with the templates (see below) replaced by snowmen:
+
+""It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ...""
+
+(Actually, if one scrolls or clicks somewhere in the page, the loop may stop, but I've observed it going on for more than a minute, generating 378 copies of the sentence.)
+
+
+Here is the wikitext source of the sentence:
+
+""It was {{convert|113|ft|7|in|m}} tall and weighed over {{convert|9000000|lb|kg|-4}}.<ref>{{cite web|url=http://www.sundayriveron-line.com/AngusSnowman_1.htm|title=Angus, King of the Mountain &mdash; World's Largest Snowman|date=February 19, 1999|publisher=Sunday River On-Line|archiveurl=http://web.archive.org/web/20071012082219/http://www.sundayriveron-line.com/AngusSnowman_1.htm|archivedate=2007-10-12}}</ref>""
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1414245600,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-kghawjstykvx6zxoqfju,task_description,resolved
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,Checked in betalabs and test2 - seems to be fixed.,1415059620,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-kghawjstykvx6zxoqfju,task_subcomment,NA
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,*** Bug 72491 has been marked as a duplicate of this bug. ***,1414692988,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kghawjstykvx6zxoqfju,task_subcomment,NA
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,"Yeah, sorry for this; fixed and back-ported on Monday. :-(",1414625279,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kghawjstykvx6zxoqfju,task_subcomment,NA
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,"PS: Observed in Chromium 37 (no extensions) under Ubuntu both while logged in and while logged out. Under Firefox I can't even get the cutting (step 2) to work, which appears to be a separate bug.",1414246140,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-kghawjstykvx6zxoqfju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,"screenshot
+
+Environment- beta
+
+1> click on Cite and pick any citation(book/web/news/journal).E.g- select cite -> book. Cite book dialog opens.
+2> JS console error “Uncaught TypeError: undefined is not a function”.
+3> Click to Add more information and error in console is “Uncaught TypeError: Cannot read property 'on' of undefined”. See screenshot.
+4> Clicking on cancel or insert does not close the dialog.
+
+Screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14994}",1413212460,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-h5qveiikflwo46ebtb77,task_description,resolved
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,Verified the fix in production,1414101056,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,Verified the fix on test2,1413575893,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,Verified the fix in Betalabs,1413392288,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,"Change 166628 merged by jenkins-bot:
+Followup 1fc13cc: fix JS errors caused by incorrect context binding
+
+https://gerrit.wikimedia.org/r/166628",1413318986,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,"Change 166628 had a related patch set uploaded by Catrope:
+Followup 1fc13cc: fix JS errors caused by incorrect context binding
+
+https://gerrit.wikimedia.org/r/166628",1413314878,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select any focusable node: citation note,math ,template or image
+
+Observed Result:
+
+The following error appears in the console:
+NS_ERROR_FAILURE: 
+
+The context menu for that focusable note is still active in CE ,if you select some other focusable note after this, no context menu appears for it or the one for previous node appears on top of it
+
+Environment:test2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15335}",1412290980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fjl7kogsfw35mh64piys,task_description,resolved
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes",Verified the fix in production,1413503136,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes",Verified the backport in test2,1412805362,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes",Verified the fix in Betalabs,1412708406,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Change 164593 merged by jenkins-bot:
+Revert ""ve.ce.Surface: Magic workaround for broken Firefox cursoring""
+
+https://gerrit.wikimedia.org/r/164593",1412358925,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Change 164548 merged by jenkins-bot:
+Revert ""ve.ce.Surface: Magic workaround for broken Firefox cursoring""
+
+https://gerrit.wikimedia.org/r/164548",1412358831,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Change 164593 had a related patch set uploaded by Jforrester:
+Revert ""ve.ce.Surface: Magic workaround for broken Firefox cursoring""
+
+https://gerrit.wikimedia.org/r/164593",1412358796,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Change 164548 had a related patch set uploaded by Bartosz Dziewoński:
+Revert ""ve.ce.Surface: Magic workaround for broken Firefox cursoring""
+
+https://gerrit.wikimedia.org/r/164548",1412342794,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Caused by 0d7eaf51767c4061b478610a035a3bc387c0973a (workaround for bug 70724 about broken Firefox cursoring). Calling .collapseToStart() sometimes fixes the selection, and sometimes causes this cryptic exception.
+
+This looks very ugly and very internal, so I'm just going to revert the patch and update the upstream bug report.",1412342724,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes",Reproducible in standalone with comment nodes too.,1412342100,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Jobs running on Ubuntu Trusty for repositories with submodules are currently broken due to a bug in the Jenkins GIT Plugin.
+
+We use Jenkins GIT Plugin 1.5.0, which uses git-client-plugin 1.0.6:
+https://github.com/jenkinsci/git-client-plugin/blob/git-client-1.0.6/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L401-L412
+
+        args.add(""submodule"", ""foreach"");
+        if (recursive) {
+            args.add(""--recursive"");
+        }
+        args.add(""git reset"");
+        if (hard) {
+            args.add(""--hard"");
+        }
+
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/4684/console
+
+
+Cleaning workspace
+Resetting working tree
+FATAL: Command ""submodule foreach --recursive git reset --hard"" returned status code 1:
+stdout: Entering 'lib/ve'
+stderr: /usr/lib/git-core/git-submodule: 552: /usr/lib/git-core/git-submodule: git reset: not found
+Stopping at 'lib/ve'; script returned non-zero status.
+
+Trying to reproduce:
+
+jenkins-deploy@integration-slave1007:/mnt/jenkins-workspace/workspace/mwext-VisualEditor-npm$ git submodule foreach --recursive git reset --hard
+> works fine
+
+The version of git on Ubunty and Precise both support this command.
+The problem lies in the quoting and separation of the arguments.
+
+jenkins-deploy@integration-slave1007:/mnt/jenkins-workspace/workspace/mwext-VisualEditor-npm$ git submodule foreach --recursive 'git reset' --hard
+> /usr/lib/git-core/git-submodule: 552: /usr/lib/git-core/git-submodule: git reset: not found
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: critical",1412198400,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-htn6d4t4wffqwtpyga74,task_description,resolved
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")",Plugin bumped to upstream 1.7.1,1432822495,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Apparently this is fixed upstream with: https://github.com/jenkinsci/git-client-plugin/commit/f75720d5de9d79ab4be2633a21de23b3ccbf8ce3  which was shipped with version 1.6.4
+
+```
+lang=diff
+-        args.add(""git reset"");
+-        if (hard) {
+-            args.add(""--hard"");
+-        }
++        args.add(""git reset"" + (hard ? "" --hard"" : """"));
+```
+
+Thus the whole command is passed as a single string.
+
+
+Will switch from our fork/patched version to upstream one as part of T100655
+",1432820455,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Apparently this is fixed upstream with: https://github.com/jenkinsci/git-client-plugin/commit/f75720d5de9d79ab4be2633a21de23b3ccbf8ce3  which was shipped with version 1.6.4
+
+```
+lang=diff
+-        args.add(""git reset"");
+-        if (hard) {
+-            args.add(""--hard"");
+-        }
++        args.add(""git reset"" + (hard ? "" --hard"" : """"));
+```
+
+Thus the whole command is passed as a single string.
+",1432820109,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Thank you Timo!
+
+I testing out with the job that shown the issue yesterday: https://integration.wikimedia.org/ci/job/pywikibot-core-tox-nose34-trusty/
+
+Test case:
+* Precise fresh workspace > OK
+* Precise, rebuild on existing workspace > OK
+* Trusty fresh workspace > OK
+* Trusty, rebuild on existing workspace > OK",1412237886,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","https://wikitech.wikimedia.org/wiki/Nova_Resource:Integration/Jenkins_Plugin
+
+Deployed the .jpi file to Jenkins.",1412204994,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","(In reply to Krinkle from comment #0)
+> Jobs running on Ubuntu Trusty for repositories with submodules are currently
+> broken due to a bug in the Jenkins GIT Plugin.
+> 
+> We use Jenkins GIT Plugin 1.5.0, which uses git-client-plugin 1.0.6:
+> 
+
+Actually, we while GIT Plugin requires git-client-plugin v1.0.5, we currently use git-client-plugin v1.4.6
+
+--
+
+https://github.com/wikimedia/git-client-plugin/commits/git-client-1.4.6%2Bwmf1
+https://github.com/wikimedia/git-client-plugin/commit/5d4c940519352a0a38038154f8c9690a7a5dba58#diff-4a13310f7c84a9d6e133def48c0aed5aR558",1412199962,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Created attachment 16643
+IRC log of a diagnostic on #pywikibot earlier (time is UTC+2)
+
+For what it is worth, attached is an IRC log from earlier today on #pywikibot.  That resulted in the previous attachment showing the 'git reset' not found issue.
+
+**Attached**: {F15207}",1412199778,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Created attachment 16642
+git submodule with GIT_TRACE=1
+
+I found that bug while testing a job for pywikibot/core.git which needs to be run on Trusty (it uses python3.4 which is not on Precise). It yielded:
+
+ /usr/lib/git-core/git-submodule: 552: /usr/lib/git-core/git-submodule: git reset: not found
+
+I have added to the job a parameter GIT_TRACE=1 and ran it again (see attached console output for https://integration.wikimedia.org/ci/job/pywikibot-core-tox-nose34-trusty/9/console ).  The git command shown:
+
+ stderr: trace: exec: 'git-submodule' 'foreach' '--recursive' 'git reset' '--hard'
+
+
+Note how git reset is enclosed in quote.  Since git version 1.9.0, that is passed as a single argument to git-submodule which can find such executable 'git reset'.
+
+I eventually had an audio call and had to be back home.   The Jenkins git-client-plugin needs to be patched to split 'git reset' to be two args, then compiled via maven and uploaded to Jenkins.
+
+You can take backup of the existing version by looking on gallium under /var/lib/jenkins/plugins/ for some .jpi files.
+
+
+Note: last time I have upgraded the Jenkins git plugin,  the whole CI setup went mad :-/  I gave up investigating the java code change and just stuck to the version we currently have.
+
+**Attached**: {F15206}",1412199342,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Release notes of git 1.9 detailing this change in git-submodule semantics:
+ https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/1.9.0.txt
+
+Basically, it used to interpret the argument as a long string (similar to ssh), and letting bash separate the command and arguments. And it now does this at the git level.",1412199080,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","screenshot
+
+Environment-test2
+
+1> In a blank page, insert a comment.
+2> open edit comment dialog. While the dialog is still open and cursor is blinking inside it, select any of the font styles except Language. For ex- select Bold or Italic.
+
+JS console error is -:
+
+“Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node”
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F14867}",1412007720,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_description,resolved
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment",Verified the fix in production,1412889048,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","(In reply to Ritu Swain from comment #6)
+> Issue resolved in test2, but can be reproduced in beta.
+
+Issue fixed in beta as well.",1412276069,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Issue resolved in test2, but can be reproduced in beta.",1412088735,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Change 163656 merged by Catrope:
+Followup a618491: fix JS errors when slugging near annotated inline nodes
+
+https://gerrit.wikimedia.org/r/163656",1412028314,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Change 163656 had a related patch set uploaded by Jforrester:
+Followup a618491: fix JS errors when slugging near annotated inline nodes
+
+https://gerrit.wikimedia.org/r/163656",1412020258,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Change 163636 merged by jenkins-bot:
+Followup a618491: fix JS errors when slugging near annotated inline nodes
+
+https://gerrit.wikimedia.org/r/163636",1412020222,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Change 163636 had a related patch set uploaded by Catrope:
+Followup a618491: fix JS errors when slugging near annotated inline nodes
+
+https://gerrit.wikimedia.org/r/163636",1412015281,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment",This bug also causes VE to throw errors when loading on pages like http://www.mediawiki.org/wiki/Parsoid/Deployments?debug=true&veaction=edit . This bug happens when an annotated inline node appears at the start of a paragraph.,1412014301,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"Cannot open comment box in Betalabs. Throwing the following error in the console:
+Uncaught TypeError: Cannot read property '0' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411584480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,Verified the fix in production,1412283385,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,Verified the fix in test2,1411684683,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,Verified the fix in Betalabs,1411591138,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"**gerritadmin** wrote:
+
+Change 162647 merged by jenkins-bot:
+Update VE core submodule to master (6e68242)
+
+https://gerrit.wikimedia.org/r/162647",1411586687,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"**gerritadmin** wrote:
+
+Change 162647 had a related patch set uploaded by Catrope:
+Update VE core submodule to master (6e68242)
+
+https://gerrit.wikimedia.org/r/162647",1411586349,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"**gerritadmin** wrote:
+
+Change 162671 merged by jenkins-bot:
+Account for WhitespacePreservingTextInputWidget#getValue being called early
+
+https://gerrit.wikimedia.org/r/162671",1411585983,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"**gerritadmin** wrote:
+
+Change 162671 had a related patch set uploaded by Catrope:
+Account for WhitespacePreservingTextInputWidget#getValue being called early
+
+https://gerrit.wikimedia.org/r/162671",1411584596,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"Edit any page on beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click the Link button. Nothing happens.
+
+Error console shows ""TypeError: this.isValid(...).done is not a function""
+
+No other controls seem to be affected by this issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1411574820,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Link button does nothing,Verified the fix in production,1412283348,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,verified the fix in test2,1411684768,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,Verified the fix in Betalabs,1411591061,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"**gerritadmin** wrote:
+
+Change 162647 merged by jenkins-bot:
+Update VE core submodule to master (6e68242)
+
+https://gerrit.wikimedia.org/r/162647",1411586684,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"**gerritadmin** wrote:
+
+Change 162646 merged by jenkins-bot:
+Account for isValid() becoming async
+
+https://gerrit.wikimedia.org/r/162646",1411585729,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"**gerritadmin** wrote:
+
+Change 162647 had a related patch set uploaded by Catrope:
+Make MWLinkTargetInputWidget#isValid asynchronous
+
+https://gerrit.wikimedia.org/r/162647",1411584675,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"**gerritadmin** wrote:
+
+Change 162646 had a related patch set uploaded by Catrope:
+Account for isValid() becoming async
+
+https://gerrit.wikimedia.org/r/162646",1411584614,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: Saving replaces categories with [[MediaWiki:Badtitletext]],"http://de.wikipedia.org/w/index.php?diff=134089498
+http://de.wikipedia.org/w/index.php?diff=134090414
+
+VisualEditor is replacing categories in articles with ""[[MediaWiki:Badtitletext]]"". Please fix it as soon as possible or deactivate VE. We do not have any time or desire to check and correct hundreds of revisions caused by broken software.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1410893460,PHID-USER-vvufz7opk2hhimdzyznx,PHID-TASK-3t7mpi32hxkzdcilczeh,task_description,resolved
+VisualEditor: Saving replaces categories with [[MediaWiki:Badtitletext]],This is caused by bug 70894; we have made an emergency modification to VE which should stop this recurring for now whilst we fix the problem. Sorry for the disruption.,1410895179,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3t7mpi32hxkzdcilczeh,task_subcomment,NA
+VisualEditor: Saving replaces categories with [[MediaWiki:Badtitletext]],"some other occurences:
+[1] http://de.wikipedia.org/w/index.php?diff=134086405
+[2] http://de.wikipedia.org/w/index.php?diff=134086148
+[3] http://de.wikipedia.org/w/index.php?diff=134085483
+[4] http://de.wikipedia.org/w/index.php?diff=134085429
+
+in [2], there is also some garbage added to an image invocation.",1410895070,PHID-USER-vvufz7opk2hhimdzyznx,PHID-TASK-3t7mpi32hxkzdcilczeh,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"When you edit a page with VE in IE, CSS styles are normalized, causing dirty diffs. This is because Internet Explorer very aggressively normalizes styles, to the point where we can't tell what the original value was without some nasty hackery.
+
+In practice, this means that any time you save a page in IE, things like style=""color: #ffffdd;"" get normalized to style=""color: rgb(255, 255, 221);"", bgcolor=""#FFFFDD"" gets normalized to bgcolor=""#ffffdd"" and invalid CSS is removed. The former two are annoying dirty diffs, the latter is actual information loss (someone else can come along later and fix invalid CSS, but not if we remove it).
+
+This normalization is a bug in Internet Explorer. I'm working on a workaround where I extract the original value using an XML parser and stash it so I can restore it later.
+
+hex to rgb normalization: https://fr.wikipedia.org/?diff=107359735
+bgcolor normalization: https://sv.wikipedia.org/?diff=27502354
+Invalid CSS removal: https://cs.wikipedia.org/?diff=11849661
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1410805080,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-b56uk34hrwocyqm77dht,task_description,resolved
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,Deploy scheduled for 08:00 SF time tomorrow.,1410837485,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160597 merged by Catrope:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160597",1410835912,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160596 merged by Catrope:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160596",1410835903,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160584 merged by jenkins-bot:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160584",1410835181,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160597 had a related patch set uploaded by Jforrester:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160597",1410835115,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160596 had a related patch set uploaded by Jforrester:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160596",1410835097,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160584 had a related patch set uploaded by Catrope:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160584",1410831715,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160583 had a related patch set uploaded by Catrope:
+Work around IE's normalization of style attributes by abusing XML parsers
+
+https://gerrit.wikimedia.org/r/160583",1410831704,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Initial case:
+
+1. Go to https://www.mediawiki.org/wiki/VisualEditor/status?veaction=edit.
+2. Scroll to the final section, remove the ""…"", and insert template.
+3. Pick ""key press"" in the normal way.
+4. Set parameter 1 as ""Ctrl"", parameter 2 as ""Shift"", and parameter 3 as ""V"".
+5. Press ""Insert"".
+
+Result: dialog remains pending whilst endless snowmen get inserted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://www.mediawiki.org/w/index.php?title=VisualEditor/status&oldid=1152478",1410545940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ndseob64bszecd4p2h7o,task_description,resolved
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,Verified the fix in mediawiki.org with the case mentioned above.,1410825529,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Change 160105 merged by jenkins-bot:
+Account for the case where a FocusableNode has an empty outerRects array
+
+https://gerrit.wikimedia.org/r/160105",1410559650,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Change 160105 had a related patch set uploaded by Jforrester:
+Account for the case where a FocusableNode has an empty outerRects array
+
+https://gerrit.wikimedia.org/r/160105",1410559279,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Change 160102 merged by jenkins-bot:
+Account for the case where a FocusableNode has an empty outerRects array
+
+https://gerrit.wikimedia.org/r/160102",1410559231,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Change 160102 had a related patch set uploaded by Catrope:
+Account for the case where a FocusableNode has an empty outerRects array
+
+https://gerrit.wikimedia.org/r/160102",1410559069,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog","On any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Cite_VisualEditor_Test?veaction=edit
+
+click Cite, then choose any of Website, Book etc. 
+
+User should see an inspector dialog for that cite, but nothing appears
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1408638180,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_description,resolved
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",Verified the fix in production,1409866340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",Verified the fix in test2 for all dialogs in Chrome and Firefox,1408729928,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",Believe that this is now fixed in phase 0 (test2 etc.),1408726524,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",Verified the fix in Betalabs but this is happening in test2 right now,1408658332,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",This was because we failed to do the MW-core pull-through of a breaking change in OOUI (whoops).,1408642084,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog","
+Also true of Insert, etc, anything with a selection list",1408638585,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+VisualEditor Mobile: Cannot load Mobile VE in Betalabs in iOS safari,"I cannot load any page with Mobile VE with iOS safari but it works fine in desktop Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406840040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sbk42chhxkin6ieg2dfm,task_description,resolved
+VisualEditor Mobile: Cannot load Mobile VE in Betalabs in iOS safari,Verified the fix in Betalabs.,1406929334,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sbk42chhxkin6ieg2dfm,task_subcomment,NA
+VisualEditor Mobile: Cannot load Mobile VE in Betalabs in iOS safari,"This should be fixed now.
+
+See https://gerrit.wikimedia.org/r/#/c/150995/",1406927676,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-sbk42chhxkin6ieg2dfm,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Scrolling and tapping into CE goes dead after using link inspector,"This just appeared as of a couple hours ago:
+
+1. Go into VE edit mode on beta labs
+2. Select a word and tap link inspector icon in toolbar
+3. Tap done to make the word a link
+4. When you return to the article in edit mode, you're no longer able to scroll the content or tap in to drop the cursor anywhere. All you can do is save, reopen the link inspector, or abandon changes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406757000,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-6bxeocfqy65faxfgqvze,task_description,resolved
+VisualEditor Mobile: [Regression pre-wmf16] Scrolling and tapping into CE goes dead after using link inspector,Verified the fix in betalabs and test2,1407190387,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6bxeocfqy65faxfgqvze,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Scrolling and tapping into CE goes dead after using link inspector,"Change 150719 merged by jenkins-bot:
+Revert ""Make scrolling in PanelLayout smoother on iOS""
+
+https://gerrit.wikimedia.org/r/150719",1406761528,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6bxeocfqy65faxfgqvze,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Scrolling and tapping into CE goes dead after using link inspector,"Change 150719 had a related patch set uploaded by JGonera:
+Revert ""Make scrolling in PanelLayout smoother on iOS""
+
+https://gerrit.wikimedia.org/r/150719",1406760425,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6bxeocfqy65faxfgqvze,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),"1. Make a change to a page on en.wiki and click review changes form the save dialog
+2. Close the save dialog and make another change, go back to the review changes page
+
+Observe that only your first change is visible. The same is true if you submit the change.
+
+This does not happen on my local wiki where I don't have pre-save caching enabled, so presumably it has something to do with that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1406389140,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-633guswlzr7odpcbch5o,task_description,resolved
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),*** Bug 68764 has been marked as a duplicate of this bug. ***,1406578618,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),*** Bug 68761 has been marked as a duplicate of this bug. ***,1406577779,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),"Nasty regression, but awesome response time - thanks, James & Ed!",1406565607,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),*** Bug 68693 has been marked as a duplicate of this bug. ***,1406564584,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),Now back-ported to wmf14 and wmf15 in production.,1406564578,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),*** Bug 68595 has been marked as a duplicate of this bug. ***,1406409644,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),Was fixed by https://gerrit.wikimedia.org/r/#/c/149392 . Quite serious though so should be deployed asap.,1406390642,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),This is fixed by this - https://gerrit.wikimedia.org/r/#/c/149392/,1406389557,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,"I cannot open any page with Mobile VE with iOS Safari, however in desktop Safari I am not seeing this issue
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1406315700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_description,resolved
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,Verified the fix,1407265254,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,This could be the HHVM issue…,1406656292,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,"It seems, it got resolved! Did anyone work on this one?",1406656252,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,"This occurs on desktop Safari too.
+
+It disappears when debug=true is used. Looking at the content response, it looks like Safari is getting the gzip'ed content and not decoding it for some reason.",1406582651,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,The error message that I get in the console is:SyntaxError: Invalid character '\u0031',1406582107,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,What was the error message you were seeing? Something about an invalid character.,1406580277,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor Mobile: MobileContext is not in the DOM,"**Author:** `jgonera`
+
+**Description:**
+When running VE on mobile, in the console:
+
+$('.ve-ui-context')
+[]
+$('.ve-ui-mobileContext')
+[]
+
+I thought that the context not appearing on mobile was a CSS regression but it seems it's no longer attached to the DOM. Too tired today to figure out why (or to figure out how DesktopContext is attached to DOM).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406248440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zy4ezl7vztln3ygf33xm,task_description,resolved
+VisualEditor Mobile: MobileContext is not in the DOM,Verified the fix in production,1408047681,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zy4ezl7vztln3ygf33xm,task_subcomment,NA
+VisualEditor Mobile: MobileContext is not in the DOM,Verified the fix in Betalabs and test2,1407190172,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zy4ezl7vztln3ygf33xm,task_subcomment,NA
+VisualEditor Mobile: MobileContext is not in the DOM,"Change 149356 merged by jenkins-bot:
+Attach mobile surface to the toolbar
+
+https://gerrit.wikimedia.org/r/149356",1406330663,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zy4ezl7vztln3ygf33xm,task_subcomment,NA
+VisualEditor Mobile: MobileContext is not in the DOM,"Change 149356 had a related patch set uploaded by Catrope:
+[WIP] Attach mobile surface to the toolbar
+
+https://gerrit.wikimedia.org/r/149356",1406311845,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zy4ezl7vztln3ygf33xm,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which contains a link 
+2.Press return after the link
+
+Observed Result:
+Uncaught TypeError: Cannot read property 'getOuterLength' of undefined VM112:521 
+appears in the console
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14637}",1406073900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fwehkkee2lr5fjpovjuq,task_description,resolved
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,Verified the fix in production,1407188817,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,Verified the fix in test2,1406324279,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,Verified the fix in Betalabs,1406160428,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,Verified the fix in Betalabs,1406160422,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,"Change 148559 merged by jenkins-bot:
+Followup b6cc76d4: call parent's onSetup/onTeardown
+
+https://gerrit.wikimedia.org/r/148559",1406074955,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,"Change 148559 had a related patch set uploaded by Catrope:
+Followup b6cc76d4: call parent's onSetup/onTeardown
+
+https://gerrit.wikimedia.org/r/148559",1406074567,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","In hebrew wikipedia, when I have created a new article, added a tamplate to it, wrote text and made it bold or italic - instead of the text appeared a pawn symbol, that was bold or italic according to the button I have clicked.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68147
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68691",1405590900,PHID-USER-em3l7mquu7qcck24eqq5,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_description,resolved
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660955,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659008,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658992,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658728,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656771,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646176,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646095,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645968,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645929,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645498,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645482,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630073,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594970,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 149920 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406573306,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","The cause here is template with multiple unwrapped siblings,
+
+e.g. Template:Done -> [[File:tick.svg|20px]] Done",1406573226,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",*** Bug 68691 has been marked as a duplicate of this bug. ***,1406565502,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","1. Add a new page in Wikipedia, with the visual editor.
+2. Add tamplate to it (I used ""מיון"" tamplate in the hebrew wikipedia).
+3. Write any text after the tamplate.
+4. Select the text.
+5. Click on the ""bold"" or ""italic"" buttons.
+6. A pawn symbol appears.",1406522131,PHID-USER-em3l7mquu7qcck24eqq5,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",Can you clarify the instructions?,1406466413,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",*** Bug 67797 has been marked as a duplicate of this bug. ***,1406341653,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",Confirmed in Chrome and Firefox.,1406341635,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,"Screenshot
+
+After saving a page,cursor still remains enabled on readmode in Betalabs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14361}",1405447980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b3df6m2mchn3utytvuaf,task_description,resolved
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,WFM – BetaLabs hiccup?,1406220733,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,This is happening again on Betalabs,1406146680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,Verified the fix in test2,1405719998,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,Verified the fix in Betalabs,1405556462,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,"Change 146984 merged by jenkins-bot:
+Close the save dialog on teardown only, not on save
+
+https://gerrit.wikimedia.org/r/146984",1405555253,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,"Change 146984 had a related patch set uploaded by Jforrester:
+Close the save dialog on teardown only, not on save
+
+https://gerrit.wikimedia.org/r/146984",1405554415,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,"<Krenair> So we're not destroying the surface, because the SaveDialog closing promise doesn't get resolved
+<Krenair> it's rejected with ""Cannot close window: window already closing with different data""
+<TrevorParscal> Krenair: that's not good
+<TrevorParscal> Krenair: have you identified why it doesn't get resolved?
+<Krenair> Not past that error, yet
+<Krenair> Even if I check !this.saveDialog.getManager().isClosing() before trying to this.saveDialog.close() it does that
+<Krenair> It's fine if I check !this.saveDialog.getManager().closing instead though
+<Krenair> well, then I get ""Uncaught TypeError: Cannot read property 'getComputedStyle' of undefined"", but the surface is torn down
+<Krenair> TrevorParscal, want to investigate further?
+<TrevorParscal> that's to do with removing the window from the dom before it's done with teardown
+<TrevorParscal> I added code in my rewrite which used promises in init to wait for the window to close before removing things, I saw that same error
+<TrevorParscal> maybe I missed something?",1405546313,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,*** Bug 68116 has been marked as a duplicate of this bug. ***,1405534284,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,*** Bug 68110 has been marked as a duplicate of this bug. ***,1405528387,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"From bug 58221:
+
+Tilman Bayer 2014-07-14 04:16:20 UTC
+
+Another example:
+
+In https://en.wikipedia.org/w/index.php?oldid=616866203&veaction=edit , place the cursor left of ""F"" in the word ""Former"" in the first paragrah, and hit the delete key. The ""F"" is deleted correctly, but the cursor jumps two to the left (between ""s"" and ""."").
+
+Reproduced in Firefox and Chromium under Ubuntu 14.04.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405341540,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_description,resolved
+VisualEditor: Cursor positioning broken after about-grouped inline alien,*** Bug 68037 has been marked as a duplicate of this bug. ***,1405445319,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Now fixed. Thank you, all.",1405381338,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146166 merged by Mwalker:
+Update VE core submodule to cfdb3a54
+
+https://gerrit.wikimedia.org/r/146166",1405379310,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146165 merged by jenkins-bot:
+Update VE core submodule to e3fa7ec8
+
+https://gerrit.wikimedia.org/r/146165",1405379165,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146166 had a related patch set uploaded by Jforrester:
+Update VE core submodule to cfdb3a54
+
+https://gerrit.wikimedia.org/r/146166",1405364698,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146165 had a related patch set uploaded by Jforrester:
+Update VE core submodule to e3fa7ec8
+
+https://gerrit.wikimedia.org/r/146165",1405364457,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146161 abandoned by Jforrester:
+Update VE core submodule to cfdb3a54
+
+https://gerrit.wikimedia.org/r/146161",1405364324,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146159 abandoned by Jforrester:
+Update VE core submodule to e3fa7ec8
+
+https://gerrit.wikimedia.org/r/146159",1405364318,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146161 had a related patch set uploaded by Jforrester:
+Update VE core submodule to cfdb3a54
+
+https://gerrit.wikimedia.org/r/146161",1405363675,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146159 had a related patch set uploaded by Jforrester:
+Update VE core submodule to e3fa7ec8
+
+https://gerrit.wikimedia.org/r/146159",1405363602,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146138 merged by jenkins-bot:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146138",1405363540,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146137 merged by jenkins-bot:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146137",1405363528,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146138 had a related patch set uploaded by Jforrester:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146138",1405359116,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146137 had a related patch set uploaded by Jforrester:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146137",1405359096,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146079 merged by jenkins-bot:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146079",1405357551,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146079 had a related patch set uploaded by Esanders:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146079",1405352260,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"The problem here appears to be the IPA template which returns two <span>s which are about-grouped (about=""#mwtX""). I imagine the cursoring logic is expecting an alien to consist of only one node.",1405342403,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Anywhere we do logical cursoring you get off by two errors, e.g. delete/backspace/arrow keys (after clicking)",1405341629,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Cannot open any cite options or template in betalabs or add it in an article throwing error:
+Uncaught TypeError: Cannot read property 'bind' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405015260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_description,resolved
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Verified the fix in production.,1405625558,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Verified the fix in test 2,1405106330,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Change 145431 merged by jenkins-bot:
+Fix cite/template dialogs
+
+https://gerrit.wikimedia.org/r/145431",1405033579,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Verified the fix in Betalabs,1405030191,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Fixed on master. Need to get a deployer to deal with production (test sites + mediawiki.org currently effected),1405027053,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Change 145427 merged by jenkins-bot:
+Fix cite/template dialogs
+
+https://gerrit.wikimedia.org/r/145427",1405026352,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Change 145431 had a related patch set uploaded by Jforrester:
+Fix cite/template dialogs
+
+https://gerrit.wikimedia.org/r/145431",1405026242,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Change 145427 had a related patch set uploaded by Alex Monk:
+Fix cite/template dialogs
+
+https://gerrit.wikimedia.org/r/145427",1405024797,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Whoops.,1405015648,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Formula
+3.Attempt to insert ""\pi"" inside the inspector
+
+Observed Result:
+As soon as you type \ in the inspector , it loses its focus and tries to parse that \ and shows error ""Failed to parse (lexing error)""
+
+
+Environment:Betalabs
+See the screenshot attached
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14534}",1404157860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eav5fcndl4mja6vawvjn,task_description,resolved
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,Verified the fix in production,1407189188,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,Verified the fix in test2,1406322027,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 147501 merged by jenkins-bot:
+Ignore staging events in CE surface
+
+https://gerrit.wikimedia.org/r/147501",1406162466,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 145442 abandoned by Esanders:
+Keep focus when live editing
+
+Reason:
+Fixed better by If03a200cead in core.
+
+https://gerrit.wikimedia.org/r/145442",1405698730,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 147501 had a related patch set uploaded by Esanders:
+Ignore staging events in CE surface
+
+https://gerrit.wikimedia.org/r/147501",1405698680,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 145444 had a related patch set uploaded by Alex Monk:
+Fix rerendering in VE
+
+https://gerrit.wikimedia.org/r/145444",1405029588,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 145442 had a related patch set uploaded by Esanders:
+Keep focus when live editing
+
+https://gerrit.wikimedia.org/r/145442",1405028031,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","On https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-06-11?veaction=edit I am getting this stack trace from VE:
+
+Error: Models must be subclasses of ve.dm.Model
+    at VeDmModelRegistry.ve.dm.ModelRegistry.register (eval at <anonymous> (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:4:670), <anonymous>:276:655)
+    at mw.loader.implement.math-visualeditor-mwmathinspector-title (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.math.visualEditor&skin=vector&version=20140613T004358Z&*:1:363)
+    at runScript (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:171:201)
+    at checkCssHandles (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:171:602)
+    at execute (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:172:384)
+    at Object.mw.loader.implement (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:178:208)
+    at https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.math.visualEditor&skin=vector&version=20140613T004358Z&*:1:11
+
+Chromium 35.0.1916.153, Linux
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1402629360,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2idu63bmownfe3nmo7uw,task_description,resolved
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Fixed. Thank you, Ori!",1402683992,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Change 139445 merged by Ori.livneh:
+Fix the VisualEditor parts of Math-wmf9 with a working cherry pick of I7d5e1174
+
+https://gerrit.wikimedia.org/r/139445",1402683632,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Change 139445 had a related patch set uploaded by Jforrester:
+Fix the VisualEditor parts of Math-wmf9 with a cherry pick of I7d5e1174
+
+https://gerrit.wikimedia.org/r/139445",1402683390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Change 139429 merged by Ori.livneh:
+Fix the VisualEditor parts of Math-wmf9 with a cherry pick of I7d5e1174
+
+https://gerrit.wikimedia.org/r/139429",1402682543,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Change 139429 had a related patch set uploaded by Jforrester:
+Fix the VisualEditor parts of Math-wmf9 with a cherry pick of I7d5e1174
+
+https://gerrit.wikimedia.org/r/139429",1402680599,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","I can reproduce this issue in Chrome 35.0.1916.114 and Firefox 29.0.1 on openSUSE, for any page on mediawiki.org.",1402650583,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Note: This happens in mediawiki.org (1.24wmf7 (941d0e1)), but not in en.wikipedia (1.24wmf6 (4331f6b)).
+
+To reproduce:
+1. Edit an article. Make a change.
+2. Press ""Save page"".
+3. Try writing an edit summary.
+
+Observed: The text is added to the article.
+
+Expected: The cursor must automatically focus in the edit summary field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1401957480,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7htliylswhsoxwr2ubyy,task_description,resolved
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Change 137926 merged by jenkins-bot:
+Move save panel init to getReadyProcess
+
+https://gerrit.wikimedia.org/r/137926",1402080830,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,Thanks Ed!,1402080269,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Change 137971 had a related patch set uploaded by Jforrester:
+Move save panel init to getReadyProcess
+
+https://gerrit.wikimedia.org/r/137971",1402080246,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Change 137926 had a related patch set uploaded by Esanders:
+Move save panel init to onReady
+
+https://gerrit.wikimedia.org/r/137926",1402060727,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Sorry, that comment was half-written about a different bug. Bah Bugzilla.
+
+I can indeed replicate in wmf7 and above (which is now everywhere).",1402000427,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"I can still reproduce it in Firefox and Chrome on mediawiki.org.
+
+In Firefox after opening the Save dialog, if I type, the text is added to the article.
+
+In Chrome the text doesn't seem to be added anywhere.
+
+And what's worse, I can now also reproduce it in the English Wikipedia.",1402000321,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"This is concerning; bug 65222 should have fixed this from happening. What browser were you using? I can't replicate in wmf7 in Chrome, Safari or Firefox.
+
+However, it does seem to have regressed in wmf8.",1401997686,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile","This is bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1400777100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jgbkfgky2myuop7wzuxk,task_description,resolved
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile",Apparently…,1401324126,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jgbkfgky2myuop7wzuxk,task_subcomment,NA
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile",Is this now fixed?,1401321231,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jgbkfgky2myuop7wzuxk,task_subcomment,NA
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile","Change 135012 merged by jenkins-bot:
+Add createSurface to base target
+
+https://gerrit.wikimedia.org/r/135012",1401318950,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jgbkfgky2myuop7wzuxk,task_subcomment,NA
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile","Change 135012 had a related patch set uploaded by Jforrester:
+Add createSurface to base target
+
+https://gerrit.wikimedia.org/r/135012",1400903688,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jgbkfgky2myuop7wzuxk,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"A few users are reporting (default) gadgets are missing on Portuguese Wikipedia:
+* https://pt.wikipedia.org/w/index.php?oldid=38937709#Scripts_n.C3.A3o_funcionando.21
+* https://pt.wikipedia.org/w/index.php?oldid=38937709#Sem_fast-buttons.2C_sem_hot-cat
+* https://pt.wikipedia.org/w/index.php?oldid=38937709#Problema_com_naveboxes
+* https://pt.wikipedia.org/w/index.php?oldid=38937709#Marcas_de_destaque_n.C3.A3o_aparecem
+
+Currently, ptwiki is running 1.24wmf4.
+
+Maybe related:
+* Bug 65340
+* Bug 65375
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Caf%C3%A9_dos_programadores&oldid=38938024#Problemas_com_os_gadgets",1400280420,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-q27xrsziqqu2gvfpstjp,task_description,resolved
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),Thanks! :-),1401904218,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),Posted at https://wikitech.wikimedia.org/wiki/Incident_documentation/20140517-bits,1401901021,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"Depooled. There is no indication that this was caused by a software fault, so I'm closing this bug as resolved. Once we have the full story on what happened to that server, a postmortem will be posted to <https://wikitech.wikimedia.org/wiki/Incident_documentation>.",1400289578,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"Of the 4 application servers for bits in eqiad (mw1149, mw1150, mw1151, mw1152), I've identified mw1151 as the problematic one.
+
+Using requests like the following https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.echo.badge%7Cext.gadget.BugStatusUpdate%2CDRN-wizard%2CReferenceTooltips%2CWatchlistChangesBold%2Ccharinsert%2Cedittop%2CmySandbox%2CrefToolbar%2Csearch-new-tab%2Cteahouse%7Cext.geshi.language.css%2Chtml4strict%2Cjavascript%2Ctext%7Cext.geshi.local%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cmw.PopUpMediaTransform%7Cskins.vector.styles%7Cwikibase.client.init&only=styles&skin=vector&*bust123
+
+(keep changing the bust query to make different cache misses).
+
+Ori noticed mw1151 has as CPU spike in ganglia and disk issues.
+
+I confirmed via mwscript on the local apache that its memcached is unable to retreive or store a value for cache key 'enwiki:gadgets-definition:7', from Gadget::loadStructuredList()
+
+We should depool that node and have ops look into it.",1400286015,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"Change 133871 merged by jenkins-bot:
+[wmf debug] resourceloader: Output servedBy when load.php has an error
+
+https://gerrit.wikimedia.org/r/133871",1400284542,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"The summary as of right now is that Gadgets' generated modules are sometimes missing in load.php (and thus gadgets are not loaded) and we don't know why, but top people are on it. :P
+
+It doesn't seem to affect any other modules nor any of Gadget's UI (like the special page or preferences).",1400284403,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"[01:32]	<MatmaRex> Krinkle: unless you have better ideas, i'd check if Gadget::loadStructuredList is sometimes returning null when it shouldn't be, and if yes, why is it doing that
+[01:33]	<Krinkle> MatmaRex: yeah, I'm mw-evalling now
+[01:35]	<Krinkle> Gadget::loadStructuredList() and the underlying memcached object is fine
+[01:35]	<Krinkle> at least not critical, let me inspect it",1400284258,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"[23:19]	<greg-g> now I just need to figure out what is causing: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Skin_and_gadget_issues_16_May_2014
+[23:24]	<MatmaRex> huh, i reproduced it
+[23:24]	<MatmaRex> and looking at this URL: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.echo.badge%7Cext.gadget.BugStatusUpdate%2CDRN-wizard%2CReferenceTooltips%2CWatchlistChangesBold%2Ccharinsert%2Cedittop%2CmySandbox%2CrefToolbar%2Csearch-new-tab%2Cteahouse%7Cext.geshi.language.css%2Chtml4strict%2Cjavascript%2Ctext%7Cext.geshi.local%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cmw.PopUpMediaTransform%7Cskins.vector.styles%7Cwikibase.client.init&only=styles&skin=vector&*
+[23:24]	<MatmaRex> i see a debug comment
+[23:24]	<MatmaRex> Problematic modules: {""ext.gadget.BugStatusUpdate"":""missing"",""ext.gadget.DRN-wizard"":""missing"",""ext.gadget.ReferenceTooltips"":""missing"",""ext.gadget.WatchlistChangesBold"":""missing"",""ext.gadget.charinsert"":""missing"",""ext.gadget.edittop"":""missing"",""ext.gadget.mySandbox"":""missing"",""ext.gadget.refToolbar"":""missing"",""ext.gadget.search-new-tab"":""missing"",""ext.gadget.teahouse"":""missing""}
+[23:24]	<MatmaRex> so, gadgets have magically disappeared
+…
+[23:26]	<ori> they're in the startup module
+[23:26]	<ori> mw.loader.getState('ext.gadget.teahouse')
+[23:26]	<ori> > ""ready""
+[23:27]	<ori> nothing missing for me
+[23:27]	<ori> in that url
+[23:28]	<MatmaRex> ori: took a few page refreshes for me
+[23:28]	<ori> oh yeah
+[23:28]	<MatmaRex> i refreshed that URL now and it loaded right
+[23:28]	<ori> i got it now
+…
+[00:49]	<greg-g> ori: MatmaRex odder can still repro
+[00:50]	greg-g just asked Krinkle to take a look now that he's back online
+[00:51]	<MatmaRex> yeah, i can reproduce still too
+[00:52]	<MatmaRex> seems to happen randomly, like 20% of time when i load an uncached URL
+[00:53]	<MatmaRex> all gadget modules are ""missing""",1400284154,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),//**content hidden as private in Bugzilla**//,1400284137,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"Change 133871 had a related patch set uploaded by Krinkle:
+[wmf debug] resourceloader: Output servedBy when load.php has an error
+
+https://gerrit.wikimedia.org/r/133871",1400284017,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),//**content hidden as private in Bugzilla**//,1400283898,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"Seen in Firefox 27 on Windows 8, FF 29 on OSX 10.6
+Reported also on Win7, OSX 10.9
+
+Edit any page on mw.o (or beta labs)
+
+Save button is clickable but does nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1400256360,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5iwkyaqeklkuqfwuota4,task_description,resolved
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"Hm.. not caused by the save button click, but due to the dialog being opened. So the same as bug 65373.
+
+*** This bug has been marked as a duplicate of bug 65373 ***",1400260271,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"Also, I was wrong above, FF on Ubuntu/Linux also shows the problem.",1400260227,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"(In reply to Krinkle from comment #3)
+> (In reply to Chris McMahon from comment #2)
+> > JS console log reports ""JQMIGRATE: jQuery.browser is deprecated""
+> 
+> Unrelated.
+
+Specifically, that's bug 65404.",1400259437,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"(In reply to Chris McMahon from comment #2)
+> JS console log reports ""JQMIGRATE: jQuery.browser is deprecated""
+
+Unrelated.",1400258968,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"JS console log reports ""JQMIGRATE: jQuery.browser is deprecated""",1400256819,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"
+Note: FF on Linux is fine.",1400256386,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"NS_ERROR_NOT_AVAILABLE: appearing while trying to save a page in Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1400192580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_description,resolved
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,Verified the backported fix in test2,1400543255,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Marking this as ""FIXED"".",1400540821,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134159 merged by jenkins-bot:
+MWTransclusionDialog: Remove setMode() call from teardown()
+
+https://gerrit.wikimedia.org/r/134159",1400535862,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,All dialogs are now opening and closing without any error in Betalabs.,1400531406,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134159 had a related patch set uploaded by Jforrester:
+MWTransclusionDialog: Remove setMode() call from teardown()
+
+https://gerrit.wikimedia.org/r/134159",1400525656,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134156 merged by jenkins-bot:
+MWTransclusionDialog: Remove setMode() call from teardown()
+
+https://gerrit.wikimedia.org/r/134156",1400525573,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134156 had a related patch set uploaded by Krinkle:
+MWTransclusionDialog: Remove setMode() call from teardown()
+
+https://gerrit.wikimedia.org/r/134156",1400525082,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Confirmed. Closing the Template dialog triggers it as well. Looks like we found another hole that needs to be plugged.
+
+
+Trace:
+
+ curCSS() load.php:6129
+ .css() load.php:6718
+ .css/<() load.php:6867
+ jQuery.access() load.php:4153
+ .css() load.php:6868
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4170
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4139
+ OO.ui.BookletLayout.prototype.toggleOutline() oojs-ui.js:4382
+ ve.ui.MWTransclusionDialog.prototype.setMode() ve.ui.MWTransclusionDialog.js:229
+ ve.ui.MWTransclusionDialog.prototype.teardown() ve.ui.MWTransclusionDialog.js:335
+ OO.ui.Window.prototype.close() oojs-ui.js:1357
+ OO.ui.Dialog.prototype.close/<() oojs-ui.js:1753",1400524182,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Also, if you just close the Template insertion dialog without adding anything, it throws the error.",1400524088,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Yes, the dialogs are working opening for me now, but I still get this error when I click on Insert Template on Template dialog.",1400523573,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"It has not been backported to production yet (will happen soon).
+
+The automatic deploy to beta.wmflabs.org ran 2 minute after your comment was submitted.",1400523037,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Also, when I try to open Language inspector.",1400522710,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"I am still getting that error : when I try to open Media Settings Dialog, Template and Media Settings.",1400522568,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"(In reply to Greg Grossmeier from comment #26)
+> (In reply to Gerrit Notification Bot from comment #25)
+> > Change 134110 merged by jenkins-bot:
+> > Window: Apply display:none after initialize, not before
+> > 
+> > https://gerrit.wikimedia.org/r/134110
+> 
+> Is this now fixed?
+
+Yes, this should fix it.",1400521759,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"(In reply to Gerrit Notification Bot from comment #25)
+> Change 134110 merged by jenkins-bot:
+> Window: Apply display:none after initialize, not before
+> 
+> https://gerrit.wikimedia.org/r/134110
+
+Is this now fixed?",1400521718,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134110 merged by jenkins-bot:
+Window: Apply display:none after initialize, not before
+
+https://gerrit.wikimedia.org/r/134110",1400520536,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Instead of trying to fill all the wholes where we're doing style computation to early, I've revised https://gerrit.wikimedia.org/r/134110 to instead extend the time window where we can do style computation.
+
+I don't think it was intentionally made this short. The idea was to do it at the end of initialize(), and instead, due to our large code base and sub classes, it ended up at the beginning of initialize().
+
+This moves it back to where it belongs.",1400518868,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Hmm.. with https://gerrit.wikimedia.org/r/134110 applied locally, GridLayout dialogs still fail, this time a little further down the line:
+
+demos/dialogs.html#GridDialog
+ curCSS() jquery.js:6131
+ .css() jquery.js:6723
+ .css/<() jquery.js:6872
+ jQuery.access() jquery.js:4153
+ .css() jquery.js:6873
+ OO.ui.Element.getClosestScrollableContainer() oojs-ui.js:464
+ OO.ui.Element.scrollIntoView() oojs-ui.js:491
+ OO.ui.Element.prototype.scrollElementIntoView() oojs-ui.js:603
+ OO.ui.OptionWidget.prototype.setSelected() oojs-ui.js:6171
+ OO.ui.SelectWidget.prototype.selectItem() oojs-ui.js:6556
+ OO.ui.BookletLayout.prototype.updateOutlineWidget() oojs-ui.js:4616
+ OO.ui.BookletLayout.prototype.addPages() oojs-ui.js:4511
+ GridDialog.prototype.initialize()",1400517114,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134110 had a related patch set uploaded by Krinkle:
+[WIP] GridLayout: Don't call getDir() during initialize
+
+https://gerrit.wikimedia.org/r/134110",1400517008,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"* Media Edit dialog
+ mw.log</log.warn() load.php:11380
+ curCSS() load.php:6131
+ .css() load.php:6723
+ .css/<() load.php:6872
+ jQuery.access() load.php:4153
+ .css() load.php:6873
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4168
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4137
+ OoUiGridLayout() oojs-ui.js:4069
+ OoUiBookletLayout() oojs-ui.js:4232
+ ve.ui.MWMediaEditDialog.prototype.initialize() ve.ui.MWMediaEditDialog.js:150
+
+* Template (transclusion)
+ mw.log</log.warn() load.php:11380
+ curCSS() load.php:6131
+ .css() load.php:6723
+ .css/<() load.php:6872
+ jQuery.access() load.php:4153
+ .css() load.php:6873
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4168
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4137
+ OoUiGridLayout() oojs-ui.js:4069
+ OoUiBookletLayout() oojs-ui.js:4232
+ ve.ui.MWTemplateDialog.prototype.initialize()
+ ve.ui.MWTransclusionDialog.prototype.initialize()
+
+* Page settings
+ mw.log</log.warn() load.php:11380
+ curCSS() load.php:6131
+ .css() load.php:6723
+ .css/<() load.php:6872
+ jQuery.access() load.php:4153
+ .css() load.php:6873
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4168
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4137
+ OoUiGridLayout() oojs-ui.js:4069
+ OoUiBookletLayout() oojs-ui.js:4232
+ ve.ui.MWMetaDialog.prototype.initialize() ve.ui.MWMetaDialog.js:47",1400515257,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"btw, since Firefox's NS_ERROR_NOT_AVAILABLE exceptions have no stack trace. This is how you catch it:
+
+Locally modify jquery.js like this:
+
+--- a/resources/lib/jquery/jquery.js
++++ b/resources/lib/jquery/jquery.js
+@@ -6122,10 +6122,15 @@ if ( window.getComputedStyle ) {
+                var width, minWidth, maxWidth, ret,
+                        style = elem.style;
+ 
++               try {
+                computed = computed || getStyles( elem );
+ 
+                // getPropertyValue is only needed for .css('filter') in IE9, see #12537
+                ret = computed ? computed.getPropertyValue( name ) || computed[ name ] : undefined;
++               } catch (e) {
++                       mw.log.warn(e);
++                       throw new Error('Firefox computed styles poop');
++               }
+ 
+                if ( computed ) {
+
+
+Then reproduce the error (preferably in debug mode), and fine a stack like the following (this one is for Media Edit dialog):
+
+console.trace:
+ mw.log</log.warn() load.php:11380
+ curCSS() load.php:6131
+ .css() load.php:6723
+ .css/<() load.php:6872
+ jQuery.access() load.php:4153
+ .css() load.php:6873
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4168
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4137
+ OoUiGridLayout() oojs-ui.js:4069
+ OoUiBookletLayout() oojs-ui.js:4232
+ ve.ui.MWMediaEditDialog.prototype.initialize() ve.ui.MWMediaEditDialog.js:150
+
+
+Conclusion, like in OO.ui.PanelLayout (fixed in I31b495fc2d9725f), GridLayout, too is doing (what seems to be erroneous) style computation on a hidden frame. So the values of it are already useless, but are now throwing in Firefox.
+
+Should probably be dealt with similarly (in case we find more).",1400514330,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"As far as I can tell the above didn't fix the issue for opening the media edit dialog. The save dialog is now working for me (bug 65401) and mobile citation dialog (bug 65422).
+
+Dialogs that seem to work for me:
+
+* Citation
+* Reference
+* Reference list
+* Media insert
+* Save
+
+* Inspectors all seem to work – Link, language, hieroglyphics, gallery, special character
+
+
+Dialogs that do not:
+
+* Media edit
+* Template (transclusion)
+* Page settings
+
+
+What's the plan for fixing these?",1400312961,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 133738 merged by jenkins-bot:
+PanelLayout: Remove call to getDir()
+
+https://gerrit.wikimedia.org/r/133738",1400282374,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,*** Bug 65422 has been marked as a duplicate of this bug. ***,1400278074,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Upstream bug report:
+ http://bugs.jquery.com/ticket/15098",1400264994,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,*** Bug 65407 has been marked as a duplicate of this bug. ***,1400263581,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"More elaborate trace:
+
+
+Error: [Exception... ""Component is not available""  nsresult: ""0x80040111 (NS_ERROR_NOT_AVAILABLE)""  location: ""JS frame :: http://krinkle.dev/wikimedia/oojs/ui/demos/lib/jquery.js :: curCSS :: line 6128""  data: no]
+
+Not much, but new phrases that can help are ""Component is not available"" and ""JS frame"".
+
+Possibly related:
+https://bugzilla.mozilla.org/show_bug.cgi?id=358415
+> ""And yes, I'm cool with getComputedStyle throwing something like NS_ERROR_NOT_AVAILABLE if there's nothing in the window. """,1400262225,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Happens when opening any dialog that inherits directionality (OO.ui.ConfirmationDialog, ve.ui.MWSaveDialog, etc.)",1400260312,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,*** Bug 65401 has been marked as a duplicate of this bug. ***,1400260271,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 133738 had a related patch set uploaded by Krinkle:
+[WIP] Element: Work around Firefox exception in getDir()
+
+https://gerrit.wikimedia.org/r/133738",1400260087,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"To reproduce:
+
+ http://jsfiddle.net/v8Syf/4/",1400251670,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"So it's no longer using the global window and pass the (foreign) node, but uses the correct window now (ownerDocument.defaultView). If anything, that should fix issues, not cause Firefox to throw.",1400249891,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Inside .css():
+
+[1.8.3] jQuery.fn.css
+-> curCSS
+
+ computed = window.getComputedStyle( elem, null ),
+ style = elem.style
+ if ( computed ) {
+   // getPropertyValue is needed for .css('filter') in IE9, see #12537
+   ret = computed.getPropertyValue( name ) || computed[ name ];
+
+
+[1.11.1] jQuery.fn.css
+-> curCSS
+  computed = .. || getStyles( elem );
+  style = elem.style
+
+  // getPropertyValue is needed for .css('filter') in IE9, see #12537
+  ret = computed ? computed.getPropertyValue( name ) || computed[ name ] : undefined;
+
+-> getStyles
+  return elem.ownerDocument.defaultView.getComputedStyle( elem, null );",1400249861,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Caused by 
+
+OO.ui.ConfirmationDialog.prototype.initialize
+
+-> OO.ui.PanelLayout
+  (only when passing $: this.$, without it it works fine, so it is frame
+  related, this is OO.ui.ConfirmationDialog/OO.ui.Dialog/OO.ui.Frame.$)
+
+-> this.$element.addClass( 'oo-ui-' + OO.ui.Element.getDir( this.$.context ) );
+   Removing this line makes it go away.
+
+-> OO.ui.Element.getDir( HTMLDocument frame$context )
+   isDoc
+   obj = obj.body
+-> $( HTMLBodyElement obj ).css( 'direction' )
+
+
+When doing it step-by-step, the error doesn't happen.",1400243458,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Narrowed it down...
+
+A breakpoint doesn't seem to work as this is a lower level exception, this is most likely a bug inside Firefox as well. After this bug most of the page is unresponsive and even reloading the page in the same or a new tab doesn't work (like it has somehow frozen the network layer or no longer allows itself to make requests to this domain). So finding where in our code we go down that path is hard to find.
+
+Inside VisualEditor, it happens for dialogs that have iframes. Specifically the kind that copies link tags. I can see that it does make requests (which get HTTP 304, as it should) for several of the parent document's stylesheets before NS_ERROR_NOT_AVAILABLE is thrown.
+
+When using the oojs-ui dialogs demo, after having manually upgraded lib/jquery.js to jQuery 1.11.1 (without Migrate plugin), I can reproduce this exception in Firefox. But, only for the confirmation dialog. Small, medium, large, and medium footless dialogs are all fine.",1400236738,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Most likely, such as was with Ia7db42b7727b8ca16ae, this is one of three things:
+
+1) We're giving the DOM or jQuery garbage, and previous versions silently just assumed stupidity and used a default. Now it's throwing the garbage back at us. In case of Ia7db42b77, we passed a VeDmDocument object as second parameter to $() for creating a new <div>. That was a nonsensical function call. It defaulted to the global Document. In many cases this would never be merged as that would obviously conflict with iframes, but it happened to be right one here.
+
+* We're relying on an undocumented behaviour (e.g. an old bug, or feature was that really just tolerance or coincidence). E.g. weird code was written, it code worked, got shipped. A good example is eg. doing something like:
+ .css( 'font-size', '100potatoes' )
+or
+ .css( 'font-size', '100pxlz' )
+
+Maybe it previously used parseFloat to strip off 'px' and just assumed it was px, and changed to stripping only 'px' and passing on to the DOM without taking the blame for it and we'd now be getting weird exceptions.
+
+(example, afaik this was not an actual change).
+
+2) We're relying on something that was intentionally changed. Happy reading:
+
+ http://blog.jquery.com/2013/01/15/jquery-1-9-final
+ http://blog.jquery.com/2013/02/04/jquery-1-9-1-released/
+ http://blog.jquery.com/2013/05/24/jquery-1-10-0
+ http://blog.jquery.com/2013/05/30/jquery-1-10-1
+ http://blog.jquery.com/2013/07/03/jquery-1-10-2
+ http://blog.jquery.com/2014/01/24/jquery-1-11
+ http://blog.jquery.com/2014/05/01/jquery-1-11-1
+ http://jquery.com/upgrade-guide/1.9/
+
+3) Oh my, jQuery can have new bugs?",1400234472,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,Caused by the jQuery 1.11 upgrade.,1400198702,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Correction, not ALL dialogs. The media insertion dialog isn't affected, all the others do seem to be.",1400198177,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"New in wmf5, happens when opening any dialog.",1400195029,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"This is not happening with Chrome though, but with Firefox",1400192809,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Intention:
+Fix the URL in a citation
+
+Steps to Reproduce:
+1. Open an existing citation, using the citation tool.
+
+2. Change something.
+
+3. Apply changes.
+
+4. Look, now you have two:  first an old/wrong version, then a new/corrected version.
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_%28WMF%29/Sandbox&diff=91692&oldid=91691
+
+
+
+Reproducible: Always
+
+Same problem in Firefox and Safari.  No problems with this using the Insert>Reference editor, even though that opens the citation tool for editing citation templates.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398978480,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_description,resolved
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Change 131091 merged by jenkins-bot:
+Fix typo: this.transclusionNode -> this.selectedNode
+
+https://gerrit.wikimedia.org/r/131091",1399332438,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Change 131065 merged by jenkins-bot:
+Fix typo: this.transclusionNode -> this.selectedNode
+
+https://gerrit.wikimedia.org/r/131065",1399054384,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Change 131091 had a related patch set uploaded by Jforrester:
+Fix typo: this.transclusionNode -> this.selectedNode
+
+https://gerrit.wikimedia.org/r/131091",1399053679,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Change 131065 had a related patch set uploaded by Esanders:
+Fix typo: this.transclusionNode -> this.selectedNode
+
+https://gerrit.wikimedia.org/r/131065",1399045808,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs","Type anything or do any edit on any page in Betalabs 
+
+The undo button remains disabled even you made some changes to that page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398104580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_description,resolved
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs",Verified the fix on https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1398987929,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs",Verified the fix on test2,1398904982,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs","Verified the fix on Betalabs:
+http://en.wikipedia.beta.wmflabs.org/wiki/21staprilchrome?veaction=edit",1398117570,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs","Change 127693 merged by jenkins-bot:
+Revert ""Add aggregate method""
+
+https://gerrit.wikimedia.org/r/127693",1398109266,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs","Change 127693 had a related patch set uploaded by Catrope:
+Revert ""Add aggregate method""
+
+https://gerrit.wikimedia.org/r/127693",1398109162,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Screenshot
+
+Steps to reproduce:
+
+
+1.Try to open the Heiroglyphics inspector
+
+Observed Result:
+The following error shows up in the console:
+Uncaught TypeError: Cannot read property 'forcedLtr' of undefined 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13714}",1397767500,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_description,resolved
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,Verified the fix in production,1398990705,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,Verified the fix in test2,1398123512,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Change 127174 merged by Catrope:
+Extension inspector directionality
+
+https://gerrit.wikimedia.org/r/127174",1398120919,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Verified the fix in Betalabs:
+http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29?veaction=edit",1397780484,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Change 127156 merged by jenkins-bot:
+Extension inspector directionality
+
+https://gerrit.wikimedia.org/r/127156",1397775204,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Change 127174 had a related patch set uploaded by Jforrester:
+Extension inspector directionality
+
+https://gerrit.wikimedia.org/r/127174",1397775139,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Change 127156 had a related patch set uploaded by Jforrester:
+Extension inspector directionality
+
+https://gerrit.wikimedia.org/r/127156",1397772038,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,This is happening for Math and Gallery inspector too.,1397768776,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5",1397767633,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Save page button does not become enabled upon adding any text/changing format/adding reference in CE for Betalabs,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add a text/change the format of a text
+
+Observed Result:
+The""Save Page"" button remains disabled on the page
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397695080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tqwxzdskyfhflxbbieky,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Save page button does not become enabled upon adding any text/changing format/adding reference in CE for Betalabs,verified the fix in production with chrome and FF,1398378602,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tqwxzdskyfhflxbbieky,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Save page button does not become enabled upon adding any text/changing format/adding reference in CE for Betalabs,verified the fix on test2,1398196651,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tqwxzdskyfhflxbbieky,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Save page button does not become enabled upon adding any text/changing format/adding reference in CE for Betalabs,Verified the fix on betalabs,1397758979,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tqwxzdskyfhflxbbieky,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Close the VE for it
+3.Again reopen the page with VE
+4.Go to the last and hit return twice
+
+Observed Result:
+The following error appears in the console:
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds
+
+See the screenshot attached
+
+Test Environment:http://en.m.wikipedia.beta.wmflabs.org/
+Page: http://en.m.wikipedia.beta.wmflabs.org/wiki/New_page_for_testing_the_special_characters_by_creating_a_new_page#editor/0
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13638}",1397687700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-okkoyig77ax6awinvswk,task_description,resolved
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,verified the fix on production,1398990962,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,Verified the fix on test2,1398127109,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,"I can still reproduce this issue on 
+http://en.m.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29#editor/0",1397760473,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,"Change 126881 merged by jenkins-bot:
+Destroy the VE target after saving
+
+https://gerrit.wikimedia.org/r/126881",1397695962,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,"Change 126881 had a related patch set uploaded by Catrope:
+Destroy the VE target after saving
+
+https://gerrit.wikimedia.org/r/126881",1397694778,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add some references
+3.Insert a reflist
+4.Click on the ""Save Page"" button
+5.Click on ""Review your changes""
+
+
+Observed Result:
+There is no wikitext for the reflist , in the review changes panel it says:
+Could not start the review because your revision matches the latest version of this page.
+
+After saving the page no reflist is appearing on the page
+An error is appearing on the read mode:
+
+
+
+Cite error: There are <ref> tags on this page, but the references will not show without a {{Reflist}} template or a <references /> tag; see the help page. ().
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397673360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mker322rzvciw5p7awgr,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,Verified the fix in production in Chrome and FF,1398384674,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,Verified the fix on test2,1397865515,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,Verified the fix on Betalabs,1397677674,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,"Change 126817 merged by jenkins-bot:
+Make inserting reference lists work again
+
+https://gerrit.wikimedia.org/r/126817",1397673915,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,"Change 126817 had a related patch set uploaded by Catrope:
+Make inserting reference lists work again
+
+https://gerrit.wikimedia.org/r/126817",1397673752,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,"While trying to edit a new page the following error appears in the console:
+Uncaught TypeError: Cannot call method 'isCollapsed' of null
+
+Also there is no toolbar appearing over the page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63945",1397585820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kzdbresrul4febvg7lyl,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,Verified the fix on test2,1397865921,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,Verified the fix on Betalabs,1397606723,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,"Change 126144 merged by jenkins-bot:
+Don't call select on a fragment if it's null
+
+https://gerrit.wikimedia.org/r/126144",1397601366,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,"Change 126144 had a related patch set uploaded by Trevor Parscal:
+Don't call select on a fragment if it's null
+
+https://gerrit.wikimedia.org/r/126144",1397599588,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,"While trying to save the edit on an existing page the following error is appearing:
+
+Uncaught TypeError: Cannot call method 'select' of null",1397585966,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf1] Selection in Firefox can get to 0,0 which then breaks horribly","seen on beta labs as of 15 April in Firefox not in Chrome
+
+on a page that begins with text such as ""two words"" open VE and click link without clicking any other item in the page
+
+insert a link such as ""http://www.example.com""
+
+in Chrome this correctly creates a link like 
+
+	
+[http://www.example.com two] words
+
+
+but in Firefox we get incorrectly instead 
+
+	
+http://www.example.com 	
+  	
+two words
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1397573220,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-gudx655lxaye4zq5b6ff,task_description,resolved
+"VisualEditor: [Regression pre-wmf1] Selection in Firefox can get to 0,0 which then breaks horribly","Change 126835 merged by jenkins-bot:
+Fix initial selection when focusing in Firefox
+
+https://gerrit.wikimedia.org/r/126835",1397678986,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gudx655lxaye4zq5b6ff,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf1] Selection in Firefox can get to 0,0 which then breaks horribly","Change 126835 had a related patch set uploaded by Esanders:
+Fix initial selection when focusing in Firefox
+
+https://gerrit.wikimedia.org/r/126835",1397677823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gudx655lxaye4zq5b6ff,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf1] Selection in Firefox can get to 0,0 which then breaks horribly","With gerrit 126169 this is now slightly better (initial selection is 1,1 but collapses to 0,0 if you click in), but still needs work because 0,0 is achievable. Badness.",1397607544,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gudx655lxaye4zq5b6ff,task_subcomment,NA
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","After wmf21 deployment cannot load VE on en.wiki.GEtting the following error:
+
+Uncaught TypeError: Object #<Object> has no method 'lookup' VM734:1505
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397166240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_description,resolved
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","Looks like a caching issue.
+
+The offending line is 25 of ve.ui.Toolbar.js
+
+Fixed by Timo",1397169111,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_subcomment,NA
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","Looks like Rummana and Trevor can reproduce it on their machine, but Ed and myself cannot.
+
+And on their machine it also doesn't happen in Incognito mode, so looks like it is a caching bug.
+
+-- 
+[#wikimedia-operations]
+ !log krinkle touched php-1.23wmf21/resources/oojs-ui/oojs-ui.js'
+ !log krinkle touched php-1.23wmf21/resources/startup.js
+ !log krinkle touched php-1.23wmf21/extensions/VisualEditor/lib/ve/lib/oojs-ui/oojs-ui.js
+ !log krinkle touched php-1.23wmf21/extensions/VisualEditor/lib/ve/modules/ve/ui/ve.ui.Toolbar.js",1397168178,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_subcomment,NA
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","Uncaught TypeError: Object #<Object> has no method 'lookup' VM1319:1505
+OO.ui.Toolbar.setup VM1319:1505
+ve.init.mw.Target.setUpToolbar VM1319:19180
+ve.init.mw.ViewPageTarget.setUpToolbar VM1319:21943
+(anonymous function)",1397168039,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_subcomment,NA
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","oojs-ui was pulled through to MW core with a breaking change ( https://gerrit.wikimedia.org/r/#/c/121537/ ) before the update to VE extension.
+
+It was correctly pulled through to ve core with changes: https://gerrit.wikimedia.org/r/#/c/120844/",1397167060,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Page options>Categories section
+3.Type in a category name which does not already exist
+
+Observed Result:
+The new category does not get added 
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63544
+
+**Attached**: {F13724}",1396643100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_description,resolved
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,"Verified the fix in production:
+https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox",1397775530,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,verified the fix on mw.org,1396998519,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,Verified the fix on test.wikipedia.org,1396917397,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,"This issue got fixed with: https://gerrit.wikimedia.org/r/124381
+Verified the fix in Betalabs",1396911172,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Search for a template by typing in something on the search box for example: Cite
+4.When the matching transclusion names appear in the list try to select the first name
+
+Observed Result:
+
+The first match does not get selected .
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63547
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63554
+
+**Attached**: {F13706}",1396638000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r7qy3zpmgywloionffwx,task_description,resolved
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,Verified the fix on mw.org,1396998382,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,Verified the fix on test.wikipedia.org,1396917642,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,Verified the fix in Betalabs: http://en.wikipedia.beta.wmflabs.org/wiki/7thaprilchrome?veaction=edit,1396910740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,"Change 124381 merged by jenkins-bot:
+[BREAKING CHANGE] Death to initializeSelection
+
+https://gerrit.wikimedia.org/r/124381",1396907061,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,"Change 124381 had a related patch set uploaded by Catrope:
+[BREAKING CHANGE] Death to initializeSelection
+
+https://gerrit.wikimedia.org/r/124381",1396898021,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Screenshot
+
+Steps to reproduce:
+
+
+1.Add a link
+2.Apply format on it like Bold/Strikethrough
+3.Now add a space right after that and add a text
+
+
+Observed Result:
+An error appears in the console  Uncaught TypeError: Cannot read property 'constructor' of undefined and the text gets added in a weird way: One letter appears before the link and some letters gets typed inside the link text
+
+See the screenshot attached
+
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/31stMarChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13199}",1396304520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7tigxc4wvpbca2apofph,task_description,resolved
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,Verified the fix in production,1397178212,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,Verified the fix on mediawiki.org,1396989855,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Change 124488 merged by jenkins-bot:
+Adjust loop counters in word break detection when removing item
+
+https://gerrit.wikimedia.org/r/124488",1396912963,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Change 124488 had a related patch set uploaded by Catrope:
+Adjust loop counters in word break detection when removing item
+
+https://gerrit.wikimedia.org/r/124488",1396911225,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,Verified the fix on Betalabs,1396483273,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Change 123373 merged by jenkins-bot:
+Adjust loop counters in word break detection when removing item
+
+https://gerrit.wikimedia.org/r/123373",1396466070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Change 123373 had a related patch set uploaded by Esanders:
+Adjust loop counters in word break detection when removing item
+
+https://gerrit.wikimedia.org/r/123373",1396465703,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+"VisualEditor: ""Unbalanced set of replace operations found"" when deleting table cells","Screencast
+
+If I select a few cells in a table at
+https://pt.wikipedia.org/wiki/Quadrado_perfeito?oldid=38495158&veaction=edit
+and then press DELETE, I get the error ""Unbalanced set of replace operations found"".
+
+See the screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13276}",1395835140,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-bcgfqlvc5q7seezob47j,task_description,resolved
+"VisualEditor: ""Unbalanced set of replace operations found"" when deleting table cells",Verified the fix in test2 and production.,1415910570,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-bcgfqlvc5q7seezob47j,task_subcomment,NA
+"VisualEditor: ""Unbalanced set of replace operations found"" when deleting table cells",This should now be fixed with the new table editing code that replaces this broken issue.,1415883023,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bcgfqlvc5q7seezob47j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,"screenshot
+
+There are wide varieties of type errors I get for undoing typing references in different way.I will try to document each cases in this same bug report:
+
+
+Case 1:
+
+Steps to reproduce:
+
+1.Insert a reference with text for example : reference[1]
+2.Press ""Undo""
+
+Error 1:
+Uncaught TypeError: Cannot read property 'length' of undefined 
+
+3.Place the cursor at the end of the text
+
+Error 2:
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 12 is out of bounds 
+
+
+Case 2:
+
+1.Insert two references with text , for example:
+reference [1]
+reference [2]
+
+2.Now keep on pressing Undo untill the page gets empty
+
+Errors:
+Uncaught TypeError: Cannot read property 'length' of undefined VM484:296
+Uncaught Error: Offset could not be translated to a DOM element and offset: 12 VM484:447
+Uncaught Error: Invalid end offset: 21 VM484:252
+Uncaught Error: Unbalanced input passed to document 
+
+In both cases, after the Undo action , clicking on ""Save Page"" does not do anything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13217}",1395775560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-owiuxjd7oca7orel6ps4,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,Verified the fix in Betalabs: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Reference_numbering&veaction=edit,1395783576,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-owiuxjd7oca7orel6ps4,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,"Change 120874 merged by jenkins-bot:
+Rename stray this.refGroup usage to this.group in MWReferenceModel
+
+https://gerrit.wikimedia.org/r/120874",1395781742,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-owiuxjd7oca7orel6ps4,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,"Change 120874 had a related patch set uploaded by Catrope:
+Rename stray this.refGroup usage to this.group in MWReferenceModel
+
+https://gerrit.wikimedia.org/r/120874",1395780514,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-owiuxjd7oca7orel6ps4,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,"Created attachment 14904
+screenshot 2
+
+**Attached**: {F13218}",1395775877,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-owiuxjd7oca7orel6ps4,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"On http://en.m.wikipedia.beta.wmflabs.org/
+
+Log in to edit
+Settings to alpha to get VisualEditor
+Attempt to edit any page
+
+A spinner appears and spins forever.  The VE UI never appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1395761400,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-rfstox6mxs6jh237skev,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"Change 120842 merged by jenkins-bot:
+Make generateCitationFeatures() not explode when citation code isn't loaded
+
+https://gerrit.wikimedia.org/r/120842",1395773184,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"Change 120842 had a related patch set uploaded by Catrope:
+Make generateCitationFeatures() not explode when citation code isn't loaded
+
+https://gerrit.wikimedia.org/r/120842",1395771997,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"Looks like the citation code broke this, sorry. I'll fix it.",1395771864,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"Looks like the problem might be in VisualEditor
+
+TypeError: Expecting a function in instanceof check, but got undefined TypeError {stack: (...), message: ""Expecting a function in instanceof check, but got undefined""} load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:9515
+log load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:9515
+handlePending load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:10492
+markModuleReady load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:10632
+nestedAddScript load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:10639
+(anonymous function) load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:10644
+script.onload.script.onreadystatechange load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:105",1395771506,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1798",1395761710,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Media Settings icon is not clickable since it got overlayed by image highlight box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image
+3.Select the image
+
+Observed Result:
+The media settings icon is getting hidden by the  Image highlight box and hence not clickable
+
+See the screenshot attached,
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Slug?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F12847}",1394829300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vlfpk6ajyvlxh6hgotnl,task_description,resolved
+VisualEditor: [Regression pre-wmf19] Media Settings icon is not clickable since it got overlayed by image highlight box,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Slug?veaction=edit,1394831749,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vlfpk6ajyvlxh6hgotnl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Media Settings icon is not clickable since it got overlayed by image highlight box,https://gerrit.wikimedia.org/r/#/c/118757/,1394831715,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vlfpk6ajyvlxh6hgotnl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,"I am getting this error while trying to save a page on betalabs:
+Uncaught TypeError: Cannot read property 'saveDialogSave' of undefined
+
+However, if you cancel the dialog box and reload again, it shows that the new content actually got saved
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394480520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-buwthuzxtqpnnddxy6dq,task_description,resolved
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1395350273,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,verified the fix on test2 :https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394846471,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,Verified the fix in betalabs.,1394490633,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,"Change 118021 merged by jenkins-bot:
+Followup 4bd80b62: fix JS error on page save
+
+https://gerrit.wikimedia.org/r/118021",1394489641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,"Change 118021 had a related patch set uploaded by Jforrester:
+Followup 4bd80b62: fix JS error on page save
+
+https://gerrit.wikimedia.org/r/118021",1394489530,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Unrelated edit removes ""upright"" parameter from images","Verified in the linked URL (I'm using Chrome, Win7, Vector), all I did was adding a few words at the top. I'll add that the edit did trigger the ""corrupted edit, please check"" warning, but I didn't verify what that caught, since the article is very large.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**URL**: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=598527246&oldid=598527036
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53853",1394185740,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lntjwslyqekt7yy463bc,task_description,resolved
+"VisualEditor: [Regression wmf16] Unrelated edit removes ""upright"" parameter from images",*** Bug 62499 has been marked as a duplicate of this bug. ***,1394476478,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lntjwslyqekt7yy463bc,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Unrelated edit removes ""upright"" parameter from images",Fixed with gerrit 117445 backport.,1394223314,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lntjwslyqekt7yy463bc,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Unrelated edit removes ""upright"" parameter from images","**letartean** wrote:
+
+This happens also on fr.wikipedia : https://fr.wikipedia.org/w/index.php?title=%C3%89glise_de_J%C3%A9sus-Christ_des_saints_des_derniers_jours&diff=prev&oldid=101872119
+This is clearly an unintentionnal removal of the upright parameter.",1394215385,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lntjwslyqekt7yy463bc,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection appearing in en.wiki,"Screenshot
+
+Tried to load VE in en.wiki getting the following error in the console and the label of insert button is missing:
+
+Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13187}",1393007340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dwqhppzvqivqkml7bog4,task_description,resolved
+VisualEditor: Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection appearing in en.wiki,Kk.,1393015148,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dwqhppzvqivqkml7bog4,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection appearing in en.wiki,"(In reply to James Forrester from comment #1)
+> Is this the bug that Roan fixed with the no-op deployment touch this morning?
+Yes, I believe so.",1393015114,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dwqhppzvqivqkml7bog4,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection appearing in en.wiki,Is this the bug that Roan fixed with the no-op deployment touch this morning?,1393014992,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dwqhppzvqivqkml7bog4,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Seen on for example  http://en.m.wikipedia.beta.wmflabs.org/wiki/Selenium_Edit_Test 
+
+As logged-in user with 'alpha' mode set, attempt to edit a page on beta labs. 
+
+VE never appears, Mobile user sees only a spinner. 
+
+VE seems to work correctly for non-Mobile user.  
+
+(Possibly related may be a recent change to Parsoid on beta labs https://bugzilla.wikimedia.org/show_bug.cgi?id=60694)
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1391631060,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-hkzhgk7ageafae2dzf72,task_description,resolved
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Change 111919 merged by jenkins-bot:
+Move paste rules to Target
+
+https://gerrit.wikimedia.org/r/111919",1391732037,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Change 111912 merged by jenkins-bot:
+Move paste rules to Target
+
+https://gerrit.wikimedia.org/r/111912",1391727694,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Change 111919 had a related patch set uploaded by Jforrester:
+Move paste rules to Target
+
+https://gerrit.wikimedia.org/r/111919",1391727639,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Change 111912 had a related patch set uploaded by Jdlrobson:
+Move paste rules to Target
+
+https://gerrit.wikimedia.org/r/111912",1391726513,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner",Seems to be a problem in the VE codebase. Managed to debug it with Trevor..,1391724891,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner",Actually it was a different parsoid bug. See bug 60755,1391635458,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner",Please provide more detail. It does sound like the parsoid bug...,1391632828,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1669",1391631323,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: Cannot Save any page on Betalabs:""TypeError: this.toolbar is null"" appears","Screenshot
+
+I cannot save any page on Betalabs with FireFox and Chrome.It shows an error Unknown error on the dialog box and in the console it shows:
+TypeError: this.toolbar is null
+
+For Chrome, it shows:
+GET http://bits.beta.wmflabs.org/static-master/extensions/VectorBeta/less/images/unwatch-icon.svg 404 (Not Found) 
+
+Also ,Edit button is not loading VE sometimes.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13034}",1391108340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2nuk4asg3igwqhymztcn,task_description,declined
+"VisualEditor: Cannot Save any page on Betalabs:""TypeError: this.toolbar is null"" appears",Not happening anymore though.Page is loading properly now on Betalabs.Also I am able to save the content on any page,1391121473,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2nuk4asg3igwqhymztcn,task_subcomment,NA
+"VisualEditor: Cannot Save any page on Betalabs:""TypeError: this.toolbar is null"" appears","(In reply to comment #0)
+> http://bits.beta.wmflabs.org/static-master/extensions/VectorBeta/less/images/
+> unwatch-icon.svg
+> 404 (Not Found) 
+
+Not sure if related at all; but recent change is http://git.wikimedia.org/commit/mediawiki%2Fcore.git/58f72c5f227b9a16ca9f489cef5171a508a059ee",1391121115,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2nuk4asg3igwqhymztcn,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Steps to reproduce:
+
+1.Open a page with VE
+2.Select an image
+3.Go to Insert>Gallery
+
+Observed Result:
+An error appears in the console ""Uncaught TypeError: Cannot read property 'body' of undefined""
+
+After that the Media Settings option does not appear on any other image .Also the reference dialog option does not show up when you select a reference note.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390861980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_description,resolved
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Change 110652 merged by jenkins-bot:
+Don't throw JS errors when opening MWExtensionInspector on the wrong node type
+
+https://gerrit.wikimedia.org/r/110652",1391470642,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Change 110652 had a related patch set uploaded by Jforrester:
+Don't throw JS errors when opening MWExtensionInspector on the wrong node type
+
+https://gerrit.wikimedia.org/r/110652",1391209857,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,*** Bug 60699 has been marked as a duplicate of this bug. ***,1391204983,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,Verified the fix in test2 and mw.org,1391123779,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=29th_January&veaction=edit,1391021279,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Change 109832 merged by jenkins-bot:
+Don't throw JS errors when opening MWExtensionInspector on the wrong node type
+
+https://gerrit.wikimedia.org/r/109832",1390936358,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Change 109832 had a related patch set uploaded by Catrope:
+Don't throw JS errors when opening MWExtensionInspector on the wrong node type
+
+https://gerrit.wikimedia.org/r/109832",1390879415,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"There's no validation going on in MWExtensionInspector at all, so it's happy to try and inspect references or images or anything that's inspectable, even if it can't be inspected by the inspector you tried to open.",1390862654,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Created attachment 14386
+Screenshot
+
+**Attached**: {F13418}",1390862238,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Select a Text and press command+k
+
+Observed Result:
+Observe that no page suggestions are appearing on the link inspector regardless of whether it is a new page or an existing page.
+
+
+See the screenshot attached.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13086}",1390502760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-txpk2gqbin5ejaia7ygi,task_description,resolved
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,Verified the fix in test2 and mw.org,1391124077,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-txpk2gqbin5ejaia7ygi,task_subcomment,NA
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Jan_27th,1390863216,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-txpk2gqbin5ejaia7ygi,task_subcomment,NA
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,"Change 109738 merged by jenkins-bot:
+Followup 7994eae8c2: fix MWLinkInspector breakage
+
+https://gerrit.wikimedia.org/r/109738",1390857394,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-txpk2gqbin5ejaia7ygi,task_subcomment,NA
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,"Change 109738 had a related patch set uploaded by Catrope:
+Followup 7994eae8c2: fix MWLinkInspector breakage
+
+https://gerrit.wikimedia.org/r/109738",1390857187,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-txpk2gqbin5ejaia7ygi,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a gallery from Insert>Gallery or just simply close the inspector without adding anything.
+3.Click on the ""Save Page"" button
+
+Observed Result:
+
+The page cannot be saved.
+
+An error appears in the console:
+Uncaught Error: InvalidCharacterError: DOM Exception 5
+
+See the screenshot attached.
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Thedomtest&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12917}",1390339800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gfuv2xwswyf4byfslddo,task_description,resolved
+VisualEditor: Cannot save a page after adding gallery to a page,"Change 110826 merged by jenkins-bot:
+Add tagName to ve.dm.MWGalleryNode
+
+https://gerrit.wikimedia.org/r/110826",1391470681,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"Change 110826 had a related patch set uploaded by Jforrester:
+Add tagName to ve.dm.MWGalleryNode
+
+https://gerrit.wikimedia.org/r/110826",1391299617,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,Verified the fix in mw.org and test2,1391124375,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,Verified the fix in betalabs.,1390869782,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"Change 109759 merged by jenkins-bot:
+Add tagName to ve.dm.MWGalleryNode
+
+https://gerrit.wikimedia.org/r/109759",1390862079,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"Change 109759 had a related patch set uploaded by Catrope:
+Add .tagName to MWGalleryNode
+
+https://gerrit.wikimedia.org/r/109759",1390859181,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"**cmitasch** wrote:
+
+I can confirm the behaviour. It does not work in Chrome but it is working with Firefox 26.0.",1390392224,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Comment to follow from Roan.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1389836760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vcsituk4chxvmxz2c4wl,task_description,resolved
+VisualEditor: Copying references is completely broken,Checked the cases mentioned above.All of them are working now on Betalabs.No JS error is appearing now after copy -paste of reference.,1390937533,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,This patch may not have been merged into ve-mw yet. Please check commit history.,1390929298,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"The following JS error appears if I copy a reference note with some text following it.
+Uncaught Error: Unbalanced input passed to document",1390865438,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 109481 merged by jenkins-bot:
+Fix balancing of data in cloneSliceFromRange
+
+https://gerrit.wikimedia.org/r/109481",1390862444,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 109481 had a related patch set uploaded by Esanders:
+Fix balancing of data in cloneSliceFromRange
+
+https://gerrit.wikimedia.org/r/109481",1390675462,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 108720 merged by jenkins-bot:
+Fix up result of selectNodes
+
+https://gerrit.wikimedia.org/r/108720",1390415384,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 108720 had a related patch set uploaded by Esanders:
+Fix up result of selectNodes to remove empty items
+
+https://gerrit.wikimedia.org/r/108720",1390331335,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 108692 merged by jenkins-bot:
+Fix exception thrown by findEndOfNode
+
+https://gerrit.wikimedia.org/r/108692",1390330490,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 108692 had a related patch set uploaded by Esanders:
+Fix exception thrown by findEndOfNode
+
+https://gerrit.wikimedia.org/r/108692",1390323703,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Based on these findings, my expectation of what will and won't work is:
+
+Probably broken:
+* Copying a reference by itself, where that reference is immediately preceded by text in the same paragraph (foo|[1]|bar)
+* Copying a reference plus some text before it (f|oo[1]|bar)
+* Copying a reference plus some text after it, where there is no text immediately preceding that reference in the same paragraph (|[1]ba|r)
+
+Probably works:
+* Copying a reference plus some text after it, where that reference is immediately preceded by text in the same paragraph (foo|[1]ba|r)
+* Copying a reference plus text before and after it (f|oo[1]ba|r)
+* Copying a reference by itself, where there is no text immediately preceding that reference in the same paragraph (|[1]|bar)",1389839300,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"I forgot to include how these things lead to the actual failure:
+
+* cloneSliceFromRange returns a slice with an unclosed paragraph opening at the very beginning, as described above
+* The tree build algorithm in ve.dm.Document doesn't actually care about the unclosed opening and builds the tree as if the mwReference was the first node. This means we get a mostly valid tree except that all the offsets are off by one because the paragraph opening element was ignored
+* When we try to get the contents of the internalItem associated with the reference from this unbalanced slice, the range in the tree is one off from the range in the data array. And so instead of [ {type:'paragraph'}, 'F', 'o', 'o', {type:'/paragraph'} ] we get [ {type:'internalItem'}, {type:'paragraph'}, 'F', 'o', 'o' ] when calling .getFullData( itemNodeRange, true ) in ve.dm.MWReferenceNode.static.toDomElements on line 135 (it's actually written as .getFullData( new ve.Range( itemNodeRange.start, itemNodeRange.end ), true ) which is just WTF and should be simplified)
+* This data with two openings and zero closings then gets fed to getDomSubtreeFromData(), which calls removeInternalNodes(), which spots an internalItem as the very first element and tries to find its end with findEndOfNode()
+* findEndOfNode() can't find the internalItem closing because there are no closings, so it tries to throw an error, but that fails because dataElement is undefined and so accessing dataElement.type is itself an error",1389838450,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Well, not *completely*, just mostly :)
+
+Go to https://www.mediawiki.org/w/index.php?title=VisualEditor:TestReferenceContents&veaction=edit and select reference [3] by clicking on it, then press Ctrl+C. You'll get a JS error.
+
+There are several things wrong here:
+
+In findEndOfNode() inside of ve.dm.Converter.prototype.getDomSubtreeFromData:
+* Line 1172 tries to throw an error using dataElement.type, but dataElement isn't set anywhere, so the generation of the error itself throws an error
+
+In ve.ce.Surface.prototype.onCopy:
+* On line 693, cloneSliceFromRange() returns a slice with unbalanced data: [ {type:'paragraph'}, {type:'mwReference'}, {type:'/mwReference'}, {type:'internalList'}, ..., {type:'/internalList'} ]
+
+In ve.dm.Document.prototype.cloneSliceFromRange:
+* On both lines 378 and 431, selectNodes() for a range exactly covering a reference returns the text node as well. In my test case, the return value is [ { node: TextNode, range: [69,69] }, { node: ReferenceNode } ]. This is clearly a bug in selectNodes()
+* Even if selection was correctly set to something of length 1, line 388 does not allow for selection[0].range to be undefined, but that's actually expected when a node is completely selected. This case should be handled, and selection[0].nodeRange should be checked against range instead in that case. So something like else if ( selection.length === 1 && range.equalsSelection( selection[0].range || selection[0].nodeRange ) ) . Otherwise, even if we fixed the selectNodes bug, the selection.length===1 code path still wouldn't be taken.
+* Because selection.length>1, the else path is taken, and we populate balanceOpenings and balanceClosings. These two are populated separately in a way that's broken: because the first node is a text node (not wrapped) we add an opening for that node's parent, but because the second node is a reference node (wrapped), we don't add a closing after it. The result is unbalanced output. This code seems to wrongly assume that leaf nodes are always unwrapped.",1389837554,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Attempt to invoke VE by clicking the Edit button on my near-empty user page http://en.wikipedia.beta.wmflabs.org/wiki/User:Cmcmahon, get error: 
+
+Error loading data from server: internal_api_error_ErrorPageError: Exception Caught: &lt;editpage-notsupportedcontentformat-text&gt;. Would you like to retry?
+
+Note: several hours ago a number of automated browser tests failed by timing out waiting for 10 seconds for the diff viewer to manifest in the browser.  There may have been a performance problem before this error appeared.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1389282300,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-uuqogx3zmcprkfif7yn7,task_description,resolved
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Synchronisation for betalabs has been broken for over a week due to bug 49846 – see http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version which says ""VisualEditor 0.1.0 (3e925e6) 20:50, 2 January 2014"". Re-closing as that's a distinct issue.",1389371498,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,*** Bug 59903 has been marked as a duplicate of this bug. ***,1389369253,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"This is fixed on test2/mw.o but still broken on beta labs.  Perhaps it was a hotfix in prod, but master not updated yet?",1389368904,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,Verified the fix in test 2 and mw.org.VE is now loading properly on wmf10.,1389307056,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106628 merged by Ori.livneh:
+Update VisualEditor for cherry pick I5cc44c5ef35 (bug 59867)
+
+https://gerrit.wikimedia.org/r/106628",1389306417,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106628 had a related patch set uploaded by Ori.livneh:
+Update VisualEditor for cherry pick I5cc44c5ef35 (bug 59867)
+
+https://gerrit.wikimedia.org/r/106628",1389306237,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,Fix now being deployed.,1389305985,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106627 merged by jenkins-bot:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106627",1389305883,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106621 merged by jenkins-bot:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106621",1389305529,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106627 had a related patch set uploaded by Jforrester:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106627",1389305464,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Asking here instead of in IRC:
+What's the offending commit? When was it merged into master?",1389303854,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"(grumble mid-air collision bz, really adding reedy now)",1389303036,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Adding reedy:
+
+Reedy, if this isn't fixed very quickly, we'll need to revert :/
+
+Rob: Can you get that reviewed and merged and tested on beta cluster ASAP?",1389303014,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106621 had a related patch set uploaded by Krinkle:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106621",1389302979,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"new patch
+https://gerrit.wikimedia.org/r/#/c/106621/",1389302413,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106619 abandoned by Robmoen:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106619",1389302281,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106619 had a related patch set uploaded by Robmoen:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106619",1389300935,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Added Rob Moen and Greg Grossmeier and changed importance, this affects mediawiki.org also",1389300663,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,This is happening on test2 environment now after 1.23wmf10 deployment,1389300217,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,Confirming.,1389283082,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=63377772&oldid=63377716
+
+I added the Citazione Necessaria template to my sandbox,
+and added some text to its only parameter.
+
+As a result I get an additional superscripted ""Citazione necessaria"" which is broken:
+<sup data-ve-ignore=""true"" class=""noprint""><span title=""Il testo selezionato deve essere comprovato da una fonte affidabile. Modifica la pagina per aggiungere fonti."" style=""color:red;"">[''<a href=""/wiki/Wikipedia:Uso_delle_fonti"" title=""Wikipedia:Uso delle fonti"">senza fonte</a>'']</span></sup>
+
+(Not sure if bug 59154/bug 55855 are related.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1388857800,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-euzbw3vi7isnaf55vkqs,task_description,resolved
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","What about these:
+https://en.wikipedia.org/w/index.php?title=Seattle%E2%80%93Tacoma_International_Airport&diff=592102043&oldid=592065880
+https://en.wikipedia.org/w/index.php?title=Lega_Nord&diff=594074863&oldid=593959708
+https://en.wikipedia.org/w/index.php?title=Swedish_Hockey_League&diff=591935813&oldid=589894884
+
+It looks like the fix here was not complete... Did that get fixed at some point?",1410029748,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)",This was fixed by https://gerrit.wikimedia.org/r/#/c/107559/,1390322597,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","(Copy/pasting isn't involved in the cases I reported at least, but thanks for assigning this.)",1389910134,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)",*** Bug 59902 has been marked as a duplicate of this bug. ***,1389904122,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","I've seen this in users of Windows 7, Windows 8, Mac OS 10.8, and Linux.  Editors have encountered this in at least Chrome, Firefox, and Safari.  Systematic testing of browsers can be seen at https://en.wikipedia.org/w/index.php?title=User:Ceyockey/sandbox_spantest&action=history
+
+Other examples include:
+ 
+https://en.wikipedia.org/w/index.php?title=List_of_information_graphics_software&curid=2891117&diff=590578180&oldid=590577937
+
+https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28Greece_season_4%29&curid=40567903&diff=590510331&oldid=590492954
+
+https://en.wikipedia.org/w/index.php?title=Tour_de_Ski&curid=8516243&diff=589296570&oldid=589296376
+
+https://en.wikipedia.org/w/index.php?title=Kamal_Haasan&curid=222346&diff=589232047&oldid=589174733
+
+https://en.wikipedia.org/w/index.php?title=PTC_Therapeutics&curid=13883765&diff=589307581&oldid=589306439
+
+https://office.wikimedia.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=105448&oldid=105447",1389897063,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","**mr.heat** wrote:
+
+This obviously is the same error:
+https://de.wikipedia.org/wiki/Nest_Labs?diff=126472789
+
+Reported/discussed here:
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/HTML_output_from_template_leaked_into_wikitext
+
+I tried to reproduce it but it did not happen.",1389888156,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","The French template ""etc"" gets a similar error:
+https://fr.wikipedia.org/w/index.php?title=Gremlin&diff=99848534&oldid=92711100
+
+{{etc}}<abbr data-ve-ignore=""true"" class=""abbr"" title=""et cetera"" xml:lang=""la"" lang=""la"">etc.</abbr>",1388961477,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","The French version of that template also gets that bug, while the English one probably works differently: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=589354249&oldid=583268893 .",1388961303,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+SVG icons embedded in stylesheets broken in Wikimedia production due to mime-type confusion,"Screenshot of problem in production.
+
+As of recently, we have SVG versions of the external link icons in MediaWiki. These are embedded as base64 encoded data uris by CSSMin in ResourceLoader.
+
+Locally, these are working fine for me. Comes out as:
+
+ background-image: linear-gradient(transparent,transparent),url(data:image/svg+xml;base64,PD...
+
+In production, however, they are broken.
+E.g.: https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet#Links
+
+ background-image: linear-gradient(transparent,transparent),url(data:application/xml;base64,PD...
+
+I can consistently reproduce this in Chrome (latest stable). I eliminated other causes by verifying that it breaks locally if I change the mime type in the CSS manually, and visa versa by changing it to image/svg+xml in the browser console when looking at production.
+
+
+Not sure if this supposed to work according to the spec, but fact is, Chrome (maybe other browsers as well) does not accept application/xml in data uris for background images.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major
+
+**Attached**: {F12090}",1388754600,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ej7jssp2ujl54r7e4pzw,task_description,resolved
+SVG icons embedded in stylesheets broken in Wikimedia production due to mime-type confusion,"
+
+*** This bug has been marked as a duplicate of bug 59234 ***",1388755125,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ej7jssp2ujl54r7e4pzw,task_subcomment,NA
+SVG icons embedded in stylesheets broken in Wikimedia production due to mime-type confusion,https://github.com/wikimedia/mediawiki-core/blob/master/includes/libs/CSSMin.php#L118-L142,1388754911,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ej7jssp2ujl54r7e4pzw,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"On MediaWiki.org (1.23wmf9), MW thinks that the appropriate MIME type for SVGs embedded in CSS as data: URIs is application/xml instead of image/svg+xml, causing them not to show up in any browser. It works for me locally.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: major
+**URL**: https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet#Links",1388703960,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_description,resolved
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #33)
+> I'll clone this ticket to cover the general issue.
+
+Filed as bug 59744. I only CC'd Kevin. The rest of you can CC yourselves if you'd like.",1389053266,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Both https://www.mediawiki.org/w/index.php?title=Requests_for_comment/Custom_inter-namespace_tabs&action=edit and [[mw:Special:RecentChanges]] look good to me now. Thanks!
+
+Marking this ticket as resolved/fixed. I'll clone this ticket to cover the general issue. Kevin: thanks as always for digging into this. :-)",1389052804,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #29)
+> (In reply to comment #23)
+> > I'm seeing missing arrows next to ""Templates used on this page:"" below the
+> > edit
+> > window on mediawiki.org as well. Example URL:
+> > <https://www.mediawiki.org/w/index.php?title=Requests_for_comment/
+> > Custom_inter-namespace_tabs&action=edit>.
+> > I'm not sure if this is already covered by the Gerrit changes linked above.
+> 
+> Ditto.
+> 
+> Also seeing it on the Beta Cluster, eg at
+> http://en.wikipedia.beta.wmflabs.org/w/index.
+> php?title=Dido_Sotiriou&action=edit
+> 
+> The Beta Cluster is already running with
+> https://gerrit.wikimedia.org/r/#/c/105469/ though, ie: even the cherrypick to
+> wmf9 (https://gerrit.wikimedia.org/r/#/c/105477/) won't fix it on mw.org most
+> likely.
+> 
+> So, this issue isn't fixed with any of the already merged (to master)
+> patches.
+
+I think I mispoke here/wasn't looking at the right thing. I think this one is indeed fixed by the patches.
+
+I think thanks to Reedy's lastest push, everything is back to normal/good. Anyone seeing any other inconsistencies/lack of images?",1389028137,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #30)
+> Change 105477 merged by jenkins-bot:
+> Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+> 
+> https://gerrit.wikimedia.org/r/105477
+
+Fixed mediawiki.org for me",1389027935,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Change 105477 merged by jenkins-bot:
+Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+
+https://gerrit.wikimedia.org/r/105477",1389027746,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #23)
+> I'm seeing missing arrows next to ""Templates used on this page:"" below the
+> edit
+> window on mediawiki.org as well. Example URL:
+> <https://www.mediawiki.org/w/index.php?title=Requests_for_comment/
+> Custom_inter-namespace_tabs&action=edit>.
+> I'm not sure if this is already covered by the Gerrit changes linked above.
+
+Ditto.
+
+Also seeing it on the Beta Cluster, eg at http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Dido_Sotiriou&action=edit
+
+The Beta Cluster is already running with https://gerrit.wikimedia.org/r/#/c/105469/ though, ie: even the cherrypick to wmf9 (https://gerrit.wikimedia.org/r/#/c/105477/) won't fix it on mw.org most likely.
+
+So, this issue isn't fixed with any of the already merged (to master) patches.
+
+(In reply to comment #16)
+> Created attachment 14228 [details]
+> Screenshot of missing arrows from [[mw:Special:RecentChanges]]
+> 
+> (In reply to comment #13)
+> > I don't know what you are looking at on mw.org, but it certainly isn't fixed
+> > for me or Mz ;)
+> 
+> I uploaded a screenshot of how [[mw:Special:RecentChanges]] looks to me at
+> the
+> moment. Perhaps cache?
+
+I don't see that issue on the BetaCluster, but I can confirm on mw.org.
+
+So, this one is indeed fixed with the patches merged to master.
+
+**Attached**: {F12054}",1389026304,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #16)
+> Created attachment 14228 [details]
+> Screenshot of missing arrows from [[mw:Special:RecentChanges]]
+
+I can still reproduce MZMcBride's screenshot after enabling ""Group changes by page in recent changes and watchlist"" on https://www.mediawiki.org/w/index.php?title=Special:Preferences#mw-prefsection-rc
+
+<span class=""mw-collapsible-toggle mw-collapsible-arrow mw-enhancedchange…-enhancedchanges-arrow-space mw-collapsible-toggle-collapsed"" tabindex=""0""></span> is empty but should probably show a collapsible arrow (if I interpret the classes correctly here).
+
+**Attached**: {F12054}",1389026166,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"This seems to have been fixed in file 5.04; however, PHP uses a bundled,
+patched copy of the library that was only updated from 5.03 to 5.11 in
+12cf930a403d.
+
+Running ""git tag --contains 12cf930a403d"" in php-src tells me that
+affected versions of PHP were 5.3.10 and older, as well as 5.4.0.
+Wikimedia runs 5.3.10 in production.
+
+Here's a snippet of the diff:
+
+--- file-5.03/magic/Magdir/sgml	2008-07-26 11:03:55.000000000 -0400
++++ file-5.04/magic/Magdir/sgml	2009-09-19 13:31:35.000000000 -0400
+@@ -1,36 +1,59 @@
+ #------------------------------------------------------------------------------
++# $File: sgml,v 1.24 2009/09/19 17:31:35 christos Exp $
+ # Type:	SVG Vectorial Graphics
+ # From:	Noel Torres <tecnico@ejerciciosresueltos.com>
+ 0	string		\<?xml\ version=""
+ >15	string		>\0
+->>23	search/400	\<svg			SVG Scalable Vector Graphics image
++>>19	search/4096	\<svg			SVG Scalable Vector Graphics image
+ !:mime	image/svg+xml
+
+Note that the start offset of the search for ""<svg"" was dropped from 23 to 19, and the newer, shorter XML declaration was the following 22-character string:
+
+<?xml version=""1.0"" ?>
+
+So this problem could have been avoided by either adding a DOCTYPE or leaving one more whitespace character in the right place.",1388924843,PHID-USER-3ampiwske4lc434cm6ot,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #24 and comment #25)
+
+Neither of these comments were helpful as a reply to comment 23. Thanks for adding Reedy to the relevant changeset, though.",1388895458,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,(I hoper we aren't using yet another set of arrows icons for that),1388890874,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"the arrow fixed hasn't been merged and deployed in wmf9, i've tagged reedy on that changeset.",1388890845,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"I'm seeing missing arrows next to ""Templates used on this page:"" below the edit window on mediawiki.org as well. Example URL: <https://www.mediawiki.org/w/index.php?title=Requests_for_comment/Custom_inter-namespace_tabs&action=edit>. I'm not sure if this is already covered by the Gerrit changes linked above.",1388890745,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #21)
+
+> https://gerrit.wikimedia.org/r/105477
+
+This one is the backport to 1.23wmf9, which someone else will need to merge+deploy.",1388888219,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Change 105477 had a related patch set uploaded by Legoktm:
+Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+
+https://gerrit.wikimedia.org/r/105477",1388888054,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Change 105469 merged by jenkins-bot:
+Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+
+https://gerrit.wikimedia.org/r/105469",1388887982,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Done, sorry about the mess. Backport and deploy to taste.",1388882251,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Change 105469 had a related patch set uploaded by Bartosz Dziewoński:
+Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+
+https://gerrit.wikimedia.org/r/105469",1388882194,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"IIRC I was silly enough to optimize the recent changes arrows in a different commit, eh. Sorry about that, patch on the way.",1388881771,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Created attachment 14228
+Screenshot of missing arrows from [[mw:Special:RecentChanges]]
+
+(In reply to comment #13)
+> I don't know what you are looking at on mw.org, but it certainly isn't fixed
+> for me or Mz ;)
+
+I uploaded a screenshot of how [[mw:Special:RecentChanges]] looks to me at the moment. Perhaps cache?
+
+**Attached**: {F12054}",1388881150,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #14)
+> I'm looking at the main page on mw.o with FF26 on OSX10.9.1 and it looks fine
+> to me.
+
+Tried recent changes with enhanced recent changes on?",1388881144,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,I'm looking at the main page on mw.o with FF26 on OSX10.9.1 and it looks fine to me.,1388880979,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #12)
+> Ori just reverted it via https://gerrit.wikimedia.org/r/#/c/105413/ and
+> pushed
+> it out to wmf9. Looks fixed on the Beta Cluster and mw.org to me.
+
+I don't know what you are looking at on mw.org, but it certainly isn't fixed for me or Mz ;)",1388880710,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Ori just reverted it via https://gerrit.wikimedia.org/r/#/c/105413/ and pushed it out to wmf9. Looks fixed on the Beta Cluster and mw.org to me.
+
+His commit message:
+On my Mac, calling finfo_file on external-link-ltr-icon.svg gets the correct
+MIME-type (""image/svg+xml""), but in production I get  ""application/xml"".
+This is probably due to the version of fileinfo or libmagic that is deployed on
+the cluster. Reverting for now.
+
+
+Robla made the point that just upgrading libmagic isn't the right/full solution: we shouldn't break backwards compat here that quickly.",1388794113,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,*** Bug 59452 has been marked as a duplicate of this bug. ***,1388766487,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #8)
+> (In reply to comment #6)
+> > Bartosz: Can you get a patch for re-adding in the doctype on those svgs?
+> 
+> I didn't even remove doctypes from most of these files (they haven't had
+> any).
+> I'll leave shotgun debugging to someone who has access to production
+> environment; if you need this fixed immediately, try reverting If05ee0e0.
+
+That's what the Beta Cluster is for :).
+
+But you're right, just first random file change I looked at removed the doctype, but the external link svg, which is not shown in that test case on Beta Cluster, didn't have doctype before either.
+
+I'm confused now.
+
+On en.wiki (production), the lock icon next to an external url is a base64 encoded image/png.
+
+On en.betawiki, the lock icon is a base64 application/xml, that is in fact valid/renders if you load it directly. It just doesn't show on the page.
+
+Both viewed with Iceweasel 24.2.",1388766397,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #7)
+Not sure anymore if that's the same problem. Filed as bug 59452 instead.",1388765431,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #6)
+> Bartosz: Can you get a patch for re-adding in the doctype on those svgs?
+
+I didn't even remove doctypes from most of these files (they haven't had any). I'll leave shotgun debugging to someone who has access to production environment; if you need this fixed immediately, try reverting If05ee0e0.
+
+
+(In reply to comment #7)
+> From #mediawiki a few minutes ago, pasting as it mentions IE difference:
+> <SVG^> Hey all. Is there already a bug report about the missing arrows in the
+> recent changes at MediaWiki.org with Chrome and FF (IE shows them properly)?
+
+Old IE uses the fallback PNG images, which show up correctly.",1388764905,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"From #mediawiki a few minutes ago, pasting as it mentions IE difference:
+<SVG^> Hey all. Is there already a bug report about the missing arrows in the recent changes at MediaWiki.org with Chrome and FF (IE shows them properly)?",1388764605,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Bartosz: Can you get a patch for re-adding in the doctype on those svgs? If you can get that merged today it'll be on Beta shortly after.
+
+The problem is exhibited on Beta Cluster, see eg:
+http://en.wikipedia.beta.wmflabs.org/wiki/User:Greg_%28WMF%29",1388764478,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(Quote from bug 59249 comment #1)
+> https://github.com/wikimedia/mediawiki-core/blob/master/includes/libs/CSSMin.
+> php#L118-L142
+
+It probably works for us locally because it uses a different function than production, or maybe the underlying library has a different upstream version or configuration of an upstream C-library dependency.
+
+(In reply to comment #4)
+> Since this has worked before, a possible culprit is my commit optimizing the
+> SVGs: If05ee0e0 – lots of things that are supposedly non-essential were
+> removed
+> from the SVGs' source code.
+
+Yeah, let's find out if putting the doctype back makes it work for mimetype library Wikimedia uses in production.
+
+Otherwise we'll have to abstract mime type detection to make sure that valid XML documents of which the root tag is ""<svg>"" are detected as SVG (instead of plain XML).",1388756022,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Since this has worked before, a possible culprit is my commit optimizing the SVGs: If05ee0e0 – lots of things that are supposedly non-essential were removed from the SVGs' source code.",1388755333,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,*** Bug 59249 has been marked as a duplicate of this bug. ***,1388755125,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,The empty gap is pretty confusing plus might create side effects (bug 59239); hence supporting blocking next deployment (bug 38865). CC'ing greg.,1388748128,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"For example, this affects the little icons shown next to links; a blank space appears instead.",1388704047,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+VisualEditor: Broken on mobile due to ULS dependency,"When loaded in alpha on beta labs I get 
+Error: Unknown dependency: jquery.uls Error {} 
+
+Given this is the second dependency related error I've now seen I'm a bit concerned about the speed at which dependencies are added to the mobile version of VisualEditor. Is there a way to better sandbox the mobile code? I find it hard to believe that ULS is actually needed for the stripped down mobile version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387229700,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-rurycjmbtcjhdokp3fmq,task_description,resolved
+VisualEditor: Broken on mobile due to ULS dependency,"Change 102368 merged by jenkins-bot:
+Move additional module loading from mw.Target to mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/102368",1387380981,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rurycjmbtcjhdokp3fmq,task_subcomment,NA
+VisualEditor: Broken on mobile due to ULS dependency,"Change 102368 had a related patch set uploaded by Jdlrobson:
+Move additional module loading to viewPage vs general target
+
+https://gerrit.wikimedia.org/r/102368",1387330337,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rurycjmbtcjhdokp3fmq,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Something&veaction=edit
+
+The error is :
+ailed to load resource: the server responded with a status of 500 (Internal Server Error) http://en.wikipedia.beta.wmflabs.org/w/api.php
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386196320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-expmgbsecy7tgvchmyll,task_description,resolved
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,Verified the fix on betalabs:http://en.wikipedia.beta.wmflabs.org/,1386223067,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Change 99317 merged by jenkins-bot:
+Followup ec3d1d67c: fix fatals because of removed run() methods
+
+https://gerrit.wikimedia.org/r/99317",1386220207,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Change 99317 had a related patch set uploaded by Catrope:
+Followup ec3d1d67c: fix fatals because of removed run() methods
+
+https://gerrit.wikimedia.org/r/99317",1386212974,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Chad – Not sure if this is solely caused by CirrusSearch, but it'd be great to get that factored out.",1386212972,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Exception associated with the HTTP 500 in the Apache logs on beta:
+
+Dec  5 03:02:04 10.4.0.187 apache2: PHP Fatal error:  Class CirrusSearchLinksUpdateJob contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Job::run) in /data/project/apache/common-local/php-master/extensions/CirrusSearch/includes/CirrusSearchLinksUpdateJob.php on line 22",1386212665,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"**jhall** wrote:
+
+Problem also successfully repros for me using Linux (Ubuntu) with Chrome v31 and Firefox v25.",1386203364,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"I am still getting it:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Something&veaction=edit
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5",1386201947,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Cannot reproduce. 
+Generic Labs bug 57968, maybe?",1386201645,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Steps to reproduce:
+
+1.Edit a page
+2.Click on ""Save Page""
+
+Observed Result:
+Unknown Error shows up in the dialog box.
+The error in the console is:
+Failed to load resource: the server responded with a status of 500 (Internal
+Server Error",1386196797,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Created attachment 13987
+Screenshot of the error
+
+**Attached**: {F12113}",1386196499,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Steps to reproduce:
+
+1.Click on Switch to source editing from the down menu for an article on betalabs
+
+Observed Result:
+Nothing happens.It does not switch to source editing from VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1386101520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aunwbewxqem2omz7rmcs,task_description,resolved
+"VisualEditor: [Regression] ""Switch to source editing"" dies","(In reply to comment #9)
+> Seeing something slightly odd after this fix was deployed to Betalabs - not
+> sure this is Bad Thing, so not re-opening the bug at this point…
+> 
+> There are 2 pathways to switch from VE to wikitext, and they now navigate the
+> user to different URLs (this didn't happen prior to the bug fix).
+> 
+> If you start in VE editing mode, and use the ""Edit Source"" tab to switch to
+> wikitext, you end up at:
+> 
+> http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:
+> Oldjoe&action=edit
+> 
+> On other hand, if you start in VE editing mode and select ""Switch to source
+> editing"" from the Page Settings drop-down, you end up at:
+> 
+> http://en.wikipedia.beta.wmflabs.org/wiki/User:Oldjoe?action=submit
+> 
+> Is this the intended behavior?
+
+The change to the primary entry point isn't explicitly intended, but I don't think it's the end of the world to push people towards the canonical (and simpler) URLs.",1388917392,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies",verified in production,1386880493,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","**jhall** wrote:
+
+Seeing something slightly odd after this fix was deployed to Betalabs - not sure this is Bad Thing, so not re-opening the bug at this point…
+
+There are 2 pathways to switch from VE to wikitext, and they now navigate the user to different URLs (this didn't happen prior to the bug fix).
+
+If you start in VE editing mode, and use the ""Edit Source"" tab to switch to wikitext, you end up at:
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Oldjoe&action=edit
+
+On other hand, if you start in VE editing mode and select ""Switch to source editing"" from the Page Settings drop-down, you end up at:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/User:Oldjoe?action=submit
+
+Is this the intended behavior?",1386115369,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Verified the fix on beta labs 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386111795,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies",This should now be fixed.,1386110720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Change 98989 merged by jenkins-bot:
+Fix naked request for save dialog's summary in save
+
+https://gerrit.wikimedia.org/r/98989",1386110546,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Change 98989 had a related patch set uploaded by Jforrester:
+Fix naked request for save dialog's summary in save
+
+https://gerrit.wikimedia.org/r/98989",1386110218,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Yes, it is still occurring.",1386109276,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies",Bug 57926 is now fixed - does this still occur?,1386109221,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies",Sorry Test Environment should be betalabs in my previous comment.,1386101679,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+Example Pagehttp://en.wikipedia.beta.wmflabs.org/wiki/Groel?veaction=edit",1386101651,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"- go to any article
+- edit it with visual editor
+- instead of text of the article in visual editor, text of another article appears
+
+- reproducible for every article I have tried at http://en.wikipedia.beta.wmflabs.org/
+- not reproducible at http://test2.wikipedia.org/
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57233",1386082320,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-owz56g6evszntatdaa2y,task_description,resolved
+beta: Parsoid is returning the wrong articles,"hopefully cleared parsoid cache using:
+
+
+ deployment-parsoidcache3$ sudo varnishadm ban.url .",1386108976,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"And it is fixed now!
+
+Gabriel kindly answered all my newbie questions related to Parsoid architecture. Ended up confirming that Parsoid running on deployment-parsoid2 did query the production infrastructure despite a localsettings.js  claiming otherwise.
+
+Roan showed up and noticed that /var/lib/parsoid/Parsoid points to the shared NFS directory (/data/project/apache/common-local/php-master/extensions/Parsoid/).  That one is autoupdated and did NOT contain the localsettings.js file
+
+Roan copied the settings file, I restarted the server and now it seems to be serving the proper pages.
+
+The root cause is https://gerrit.wikimedia.org/r/98014 from last Friday which I did not bother to verify :-(",1386108793,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"On deployment-parsoid2 , I have edited /usr/bin/parsoid to enable some log, namely the launch command is something like:
+
+ sudo -E -u parsoid nohup node \
+   /var/lib/parsoid/Parsoid/js/api/server.js \
+   >/data/project/logs/parsoid-stdout.log \
+   2>/data/project/logs/parsoid-error.log &
+
+/data/project being the shared project directory, that might gives some clue.",1386107800,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"[13:41] <gwicke> parsoid is not using action=visualeditor
+[13:42] <gwicke> I'd double-check that VE is actually using parsoidcache3
+[13:42] <gwicke> and that the request goes to the right parsoid backend",1386107024,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"The Parsoid does queries to the MediaWiki API to get some content to render. One of the request is logged in api.log as:
+
+ format=json action=visualeditor page=Marching_band paction=parse
+
+I used ApiSandbox to reproduce that query:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:ApiSandbox#action=visualeditor&format=json&page=Marching_band&paction=parse
+
+The response contains among other things:
+
+ http://en.wikipedia.org/wiki/Special:Redirect/revision/51845
+ <title>Marching_band</title>
+ Describe the new page here.
+
+ ""basetimestamp"": ""20120103034343"",
+ ""starttimestamp"": ""20131203212539"",
+ ""oldid"": 51845
+
+The redirection to old id 51845 yields page https://en.wikipedia.org/w/index.php?oldid=51845 which is the 'Pérez Prado' article.",1386106293,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,There is no more 404 errors but some articles still gives content that does not match the page being requested :/,1386101805,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"I upgraded the varnish on parsoidcache instance while I was investigating.
+
+Now it seems VE is querying the parsoid with some invalid URL and it popup a 404 error :-/   Nothing obvious in the logs though, maybe VE has a wgDebugLogGroup we should enable to get more logs.",1386090291,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"
+The articles returned do not seem to originate from beta enwiki or production enwiki",1386088489,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"I have updated Parsoid code on deployment-parsoid2 in /srv/deployment/parsoid/Parsoid
+
+Forgot to run npm install to update the node modules, might be related :/",1386087321,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,This very much looks like an artefact of the changes for bug 57233 - marking as such.,1386086570,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+VisualEditor:Cannot Save a page after adding an image/template/link in the article in beta,"Screenshot attached
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Add any image/template/link in the article
+3.Click the ""Save Page"" button
+
+Observed Result:
+Cannot Save the Article.
+
+The following error is found in the developers tool:
+
+Uncaught TypeError: Object #<VeDmInternalItemNode> has no method 'isCollapsed'
+ve.dm.Transaction.newFromRemoval
+ve.ui.MWReferenceDialog.teardown
+OO.ui.Window.close
+(anonymous function)
+proxy load.php:10
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker
+
+**Attached**: {F12504}",1385855220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5smx3vzr2s6nuq4uvikr,task_description,resolved
+VisualEditor:Cannot Save a page after adding an image/template/link in the article in beta,"
+
+*** This bug has been marked as a duplicate of bug 57683 ***",1386012532,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5smx3vzr2s6nuq4uvikr,task_subcomment,NA
+VisualEditor:Cannot Save a page after adding an image/template/link in the article in beta,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 and FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/wiki/Groel?veaction=edit",1385855466,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5smx3vzr2s6nuq4uvikr,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Steps to reproduce:
+
+1.Click on the Edit page
+2.Select a text or place the cursor at the end of any text
+3.Click on More>Reference
+4.Click on Insert reference
+5.Click on Save Page
+
+Observed Result:
+No reference is getting added in the article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1385585280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytsxsndot74amowyp5vy,task_description,resolved
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,Moved my comments to bug 59599 and bug 59600.,1388769354,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"I think this just happened to me on the Danish Wikipedia?
+I used my userpage as a sandbox https://da.wikipedia.org/w/index.php?title=Bruger:Elitre_(WMF)&action=history, and the edits in which I tried to add references do not show up in the history, although I managed to save them and also got the message that confirms this.
+
+(For the record, I was trying to reproduce https://da.wikipedia.org/w/index.php?title=F-35_Lightning_II&diff=prev&oldid=7409486 and https://da.wikipedia.org/w/index.php?title=Enhedslisten&diff=prev&oldid=7414100 , where there might be a connection between adding a reference and getting a duplicated infobox).",1388180229,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,verified the fix in production,1386880605,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Verified in betalabs.
+http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386024384,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Change 98587 merged by jenkins-bot:
+Fix JS errors when inserting references
+
+https://gerrit.wikimedia.org/r/98587",1386018934,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Change 98587 had a related patch set uploaded by Catrope:
+Fix JS errors when inserting references
+
+https://gerrit.wikimedia.org/r/98587",1386012914,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,*** Bug 57785 has been marked as a duplicate of this bug. ***,1386012532,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"(In reply to comment #2)
+> Please note that, this is working fine in Live right now.
+By Live, I meant production in :https://en.wikipedia.org/",1385585912,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Please note that, this is working fine in Live right now.",1385585494,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Test Environment: Betalabs
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+Example Page:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_(WMF)?veaction=edit",1385585446,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Seen in Firefox on beta labs as of Nov 25 (Chrome behaves correctly):
+
+Login and navigate to some page with text, e.g. as Selenium_user/User:Selenium_user
+
+Without touching anything on the page, click the ""Link"" icon in the menu bar. 
+
+Expected:  First word in the page is highlighted and link UI appears, referring to highlighted text. 
+
+Actual:  Link icon shows being pressed, but no link UI appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1385424900,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-3bskmko72vtqvqb4i7uh,task_description,resolved
+VisualEditor: Inspectors fail to appear at all in Firefox,Verified in production,1386881095,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Verified in Betalabs.
+http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386024454,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Change 98688 merged by jenkins-bot:
+Use visibility: hidden; for the ui.Context and its popup
+
+https://gerrit.wikimedia.org/r/98688",1386019137,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Change 98688 had a related patch set uploaded by Catrope:
+Use visibility: hidden; for the ui.Context and its popup
+
+https://gerrit.wikimedia.org/r/98688",1386018229,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,Also partially fixed in gerrit 98598.,1386014515,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Change 98569 merged by jenkins-bot:
+Use visibility: hidden; to hide inspectors
+
+https://gerrit.wikimedia.org/r/98569",1386012369,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Change 98569 had a related patch set uploaded by Catrope:
+Use visibility: hidden; to hide inspectors
+
+https://gerrit.wikimedia.org/r/98569",1386009867,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,Looks like transplantStyles isn't resolving in OO.ui.Frame.,1386006923,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,*** Bug 57779 has been marked as a duplicate of this bug. ***,1386005444,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Also, after clicking on the ""Link"" icon, the ""Save Page"" button does not work anymore even if I close the editor and reopen and re-edit it.Related issue?",1385499120,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"**jhall** wrote:
+
+Now it seems as though the Link interface is completely broken in Firefox.  Following repro steps above, when I click the ""Link"" icon, nothing happens at all (Chrome stills seems to work fine).",1385497011,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Created attachment 13905
+link is pressed, 'Starting' should be highlighted, link UI should appear but does not
+
+**Attached**: {F12079}",1385425033,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"As discovered today with the Wikidata weekly summaries run, MassMessage ignores the namespace if it is a interwiki link.
+
+Example; {{#target:Wikidata:Status updates|www.wikidata.org}}
+
+The message gets delivered to https://wikidata.org/wiki/Status_updates which then errors due to it being in NS_MAIN and not NS_PROJECT which was specified.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58524",1385166000,PHID-USER-4n6zx4s5v23pjdztvtnr,PHID-TASK-mlk3wsew3wcl527ku3ln,task_description,resolved
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Seems to happen again? https://meta.wikimedia.org/w/index.php?title=VisualEditor/Newsletter/Wikis_with_VE&oldid=11801108
+",1430317571,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,This went out to the rest of the sites with today's deployment and looks to be working fine: <https://en.wikipedia.org/w/index.php?title=Wikipedia:Sandbox&diff=prev&oldid=589970369>,1389298817,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"(In reply to comment #22)
+> (In reply to comment #21)
+> > I've been using MassMessage the whole time. Just replace the namespaces with
+> > 'Project:' (if this is not deployed within time).
+> 
+> Is the canonical namespace name safe to use?
+
+Let's see: <https://meta.wikimedia.org/w/index.php?title=Special:Contributions/AnankeBot&dir=prev&offset=20121207114449&limit=39&target=AnankeBot>.",1388578857,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"(In reply to comment #21)
+> I've been using MassMessage the whole time. Just replace the namespaces with
+> 'Project:' (if this is not deployed within time).
+
+Is the canonical namespace name safe to use? If so, that's a handy workaround. :-)
+
+(In reply to comment #20)
+
+People continue to use EdwardsBot, both locally and globally. Bug 58962 is probably more pressing to get resolved, but this bug (bug 57464) is medium priority given the rather nasty side effect (failed deliveries). It can probably go out to Wikimedia wikis on Monday or Tuesday of this week. That'd be a question for Sam, Ori, or Aaron S., I imagine.
+
+There's also bug 54859 about adding an API module for MassMessage. This would help for the Signpost in particular given its use of LivingBot, in my estimation.",1388381982,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"(In reply to comment #20)
+> Dan or Greg, is there any chance we can get this deployed this week?
+> 
+> Because of this bug, we're still dependent on EdwardsBot for global message
+> delivery, and EdwardsBot is planned to be retired from global delivery in 2
+> days. The sooner we can fully transition to MassMessage, the better :)
+
+I've been using MassMessage the whole time. Just replace the namespaces with 'Project:' (if this is not deployed within time).",1388318666,PHID-USER-4n6zx4s5v23pjdztvtnr,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Dan or Greg, is there any chance we can get this deployed this week?
+
+Because of this bug, we're still dependent on EdwardsBot for global message delivery, and EdwardsBot is planned to be retired from global delivery in 2 days. The sooner we can fully transition to MassMessage, the better :)",1388310020,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101814 merged by jenkins-bot:
+Store title as a job parameter
+
+https://gerrit.wikimedia.org/r/101814",1387912109,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101814 had a related patch set uploaded by Legoktm:
+Store title as a job parameter
+
+https://gerrit.wikimedia.org/r/101814",1387174822,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101810 merged by jenkins-bot:
+Add debug logging for bug 57464
+
+https://gerrit.wikimedia.org/r/101810",1387170522,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101810 had a related patch set uploaded by Legoktm:
+Add debug logging for bug 57464
+
+https://gerrit.wikimedia.org/r/101810",1387170502,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101808 merged by jenkins-bot:
+Add debug logging for bug 57464
+
+https://gerrit.wikimedia.org/r/101808",1387169802,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101808 had a related patch set uploaded by Legoktm:
+Add debug logging for bug 57464
+
+https://gerrit.wikimedia.org/r/101808",1387168721,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"At [[Special:Log/massmessage]] I currently see:
+
+---
+08:38, 9 December 2013 Delivery of ""[[m:Special:MyLanguage/Tech/News/2013/49|Tech News: 2013-49]]"" to Village pump (technical) was skipped because target was in a namespace that cannot be posted in
+---
+
+This is pretty gross. ""Village pump (technical)"" should be ""Wikipedia:Village pump (technical)"". Not sure what's going on with ""[[m:...]]""; that may be a separate bug.
+
+Ori: any chance you could take a look here?",1386882945,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"I'm not able to see where the namespace is being lost, so here are the steps the data goes through. Maybe someone else will spot it.
+
+1. Picked up by MassMessageHooks::storeDataParserFunction as a string
+2. MassMessageHooks::verifyPFData validates that it is a valid title (checks !is_null( Title::newFromText ) ), but returns the original string
+3. MassMessage::getParserFunctionTargets unserializes the string.
+4. MassMessage::normalizeTargets simply re-arranges the list of targets, not modifying the string.
+5. Back to SpecialMassMessage::submit, which feeds the result from normalizeTargets to MassMessageSubmitJob.
+6. the SubmitJob creates a Title object, and submits a group of MassMessageJobs.
+7. On meta, in MassMessageJob::__construct, there is ""$this->title = Title::newFromText( $this->title->getPrefixedText() );"", which was the original fix for this bug. It *should* do nothing when being run on meta.
+8. When the job is executed on the target wiki, that line is run again. Title::getPrefixedText should return the entire title (including interwiki) except for any fragments (url anchors). By re-creating the title, the namespace should be re-parsed as a real namespace instead of an interwiki prefix.
+
+The issue:
+If the namespace is not an interwiki prefix, it is re-parsed correctly as can be seen by the successful deliveries.
+
+If the namespace is an interwiki prefix, it is still thought to be an interwiki prefix (I think), and the delivery fails since it is not interpreted as a namespace.
+
+My hunch is that somewhere step 8 isn't working as I expect it would.",1386652693,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Not fixed apparently, see https://meta.wikimedia.org/w/index.php?title=User_talk:Guillom&oldid=6668167
+
+Glancing at the list of wikis, the first thing I notice is that for all the wikis in the ""did not work"" list (except for one), they all have namespaces that are also interwiki prefixes on meta.
+
+The lone exception is ttwiki, https://tt.wikipedia.org/wiki/%D0%9C%D0%B0%D1%85%D1%81%D1%83%D1%81:%D0%9A%D3%A9%D0%BD%D0%B4%D3%99%D0%BB%D0%B5%D0%BA/massmessage?uselang=en
+
+The weird thing about that is that link is to the correct page. The link on the failed commons delivery is missing the namespace, see https://commons.wikimedia.org/wiki/Special:Log/massmessage",1386649637,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,This was deployed at some point.,1386559175,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"(In reply to comment #6)
+> Kunal: Yeah, please prepare a backport to wmf5.
+
+I've created a branch called '1.23wmf5' and cherry-picked the patch onto it.",1386023039,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 98709 merged by jenkins-bot:
+Create a fresh Title object in the job
+
+https://gerrit.wikimedia.org/r/98709",1386022839,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 98709 had a related patch set uploaded by Legoktm:
+Create a fresh Title object in the job
+
+https://gerrit.wikimedia.org/r/98709",1386022765,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Kunal: Yeah, please prepare a backport to wmf5. And when would you be available to help with the deploy this week? We might be able to get this in tomorrow.
+
+(I assume the only bit that is needed to be backported is gerrit 97162.)",1386005323,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Thanks for the quick fix. This probably didn't get caught because we only deployed to test.wikipedia.org and test2.wikipedia.org, instead of a project such as Wikidata or Commons, which share an interwiki prefix and a namespace name. This probably points to an area where a unit test might make sense? (Or additional test inputs?) Maybe. In any case, this bug is no longer PATCH_TO_REVIEW. I'll leave it to someone else to figure out what to set it to.",1385352969,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Greg, Sam, would it be possible to get this backported and deployed next week? Global message delivery basically won't work because of this.",1385346361,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 97162 merged by jenkins-bot:
+Create a fresh Title object in the job
+
+https://gerrit.wikimedia.org/r/97162",1385343942,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"I guess this might also affect Commons (https://meta.wikimedia.org/wiki/Distribution_list/Global_message_delivery ).
+
+It looks like this issue prevents MM from being used for most of the usual global message deliveries to village pumps, so it's great that we already have a patch, and a timely review and deployment would be useful.",1385178044,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 97162 had a related patch set uploaded by Legoktm:
+Create a fresh Title object in the job
+
+https://gerrit.wikimedia.org/r/97162",1385167775,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Try to reuse a reference in VE in an article featuring references.
+
+All you get is the list of number in brackets, which are the numbers of the references, and nothing else.
+
+(Actually, if you test it in https://en.wikipedia.org/wiki/Alex_Timbers?veaction=edit , you will notice that it does provide the ""ref name"" for the first reference; but that's it).
+
+It seems it does not matter which OS, browser or skin you are using.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://commons.wikimedia.org/wiki/File:VisualEditor_ref_dialog_box_showing_numbers_and_ref_names.png",1384810020,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fndgxh4r76y6bofc4pwd,task_description,resolved
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Created attachment 14498
+Screenshot of testing the fix
+
+**Attached**: {F12146}",1391644263,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,Verified the fix in test2,1391643894,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,Fixed and back-ported.,1391625632,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111232 merged by jenkins-bot:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111232",1391558723,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111229 merged by jenkins-bot:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111229",1391558662,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"(In reply to comment #11)
+
+Thank you for your reply.",1391557114,PHID-USER-4cgt73x34j35pnbem65l,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111232 had a related patch set uploaded by Jforrester:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111232",1391538518,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111229 had a related patch set uploaded by Jforrester:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111229",1391538506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111203 merged by jenkins-bot:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111203",1391538435,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111203 had a related patch set uploaded by Esanders:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111203",1391529322,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Sorry, this bug got entirely missed.
+
+For major regression bugs like this, if they've clearly missed out on immediate triage, please shout out-of-band (e.g. on IRC or the various Feedback pages) as otherwise it's likely to continue to get missed for weeks or even months, as in this case. :-(
+
+Assigning. Ed, please fix urgently.",1391485488,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Nemesis, what you're seeing for the fourth reference is the ref name (<ref name=""Couratier_Transvaal"">).  This is displayed, and might be helpful if the ref name were both sensibly chosen (e.g., not just a number or random letter) and if it already existed for every ref that you wanted to re-use.",1391442591,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"(In reply to comment #9)
+> This is ABSURD.
+
+Please discuss high-level team priorities or workflows e.g. on https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback - this specific bug report is only about this specific bug and its technical aspect. Thanks.",1391432944,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"This is ABSURD. It's been two and half months of having something that *used to work* no longer work. And that something was very USEFUL - if you wanted to use a existing citation/reference to support text in more than one place in an article, you could do so easily. 
+
+Why does it take the VE team MONTHS to fix something that gets broken? How difficult is this, really? Why don't regressions get TOP priority for fixing? 
+
+(Just so there's no misunderstanding about what's broken:
+
+a. In the ""Insert"" menu, select ""Reference""
+b. At the bottom left corner of the dialog box, click ""Use an existing reference"".
+
+While you can still select any existing reference, what you CAN'T do is actually see what the references consist of (author, title, date, publication, etc.). Yes, occasionally some text does appear, but REALLY?
+
+And yes, there is a workaround - first you should look at the References section in the article, and note the reference number you want, BEFORE you do a. and b. above. But REALLY - is this supposed to be user-friendly? Is this the sort of step-by-step procedure we want to put into a user manual?
+
+So to repeat - it's ABSURD that someone can't easily (and quickly) fix a problem that simply involves DISPLAYING SOME TEXT. And if there is an underlying problem with VE or Parsoid that prevents DISPLAYING SOME TEXT, then perhaps someone would post a brief explanation here so that this wouldn't seem so ABSURD.",1391381391,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Actually, when test on my sandbox page, https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Ch%C3%A2teau_Rothschild_%28Boulogne-Billancourt%29?veaction=edit, there is some text displayed for the 4th ref. Still, if these two words are indeed in the reference, they are sperarated by many other words. And why for this reference, and not for the others ? The 2nd and the 7th references are very similar but no words are displayed in the tool...",1391380408,PHID-USER-4cgt73x34j35pnbem65l,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"The screenshot at https://en.wikipedia.org/wiki/File:Use_existing_reference_bug_for_VE.jpg shows how inadquate the interface is.  Even if you search for a word that you know is in the ref, you may still be left with many unidentified ref numbers.  ""Please blindly guess which one is the right one"" is not a desirable interface.",1390505223,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"**Wikifram** wrote:
+
+This is not a duplicate, these are completely different issues, and this one isn't fixed in MediaWiki. This bug is not about autonumbering, this is about ""use an existing reference"", where you only get to see the numbers, not the contents of the ref, which is totally useless. Please don't merge unrelated bugs.",1386670773,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Also reported as bug 57420, fix pending. Sorry for the disruption.
+
+*** This bug has been marked as a duplicate of bug 57420 ***",1385374223,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Hey Cainamarques, about this last comment, let's keep this conversation at https://en.wikipedia.org/wiki/User_talk:Cainamarques#Bug.3F . Thanks!",1385064692,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,FORGET my last comment. I did not know I could not edit simple external hiperlinks (with only the url). At least I am assuming I cant...,1385043855,PHID-USER-qlrpm27qlsmjh2pg65bg,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Yeah, I was not paying attention Elitre. This bug happens to me as well. I did some testing and found something interesting. In the Alex Timbers article, I ""named"" more than one reference to see if the names would show up in the existing references list (as the first one did) and they do. But for whatever reason I can not edit those ""named"" references using VE. It only shows:
+
+[1]
+
+I can edit the first named reference and all the others perfectly. Is that a known bug?
+
+Test page:
+https://en.wikipedia.org/w/index.php?title=User:Cainamarques/sandbox&oldid=582669663",1385041839,PHID-USER-qlrpm27qlsmjh2pg65bg,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"This makes the """"Use an existing reference"" functionality almost *useless*. You can't see *any* information about the existing references - the author, title, url, etc., etc. I *could* modify the user guide to say ""Remember the footnote number you want to use again, because if you don't, the dialog box that appears will be worthless"", but that would be embarrassing. Also, hopefully, this regression will be fixed quickly. (I'd feel better if it were prioritized as at least ""High"" priority.)",1385000267,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: Categories are showing up in wikitext format in the view mode of a page,"Categories
+
+Steps to reproduce:
+
+-Click on the Edit button of a page
+-Click on the Page Settings button
+-Add some category to this page
+-Click on ""Apply Changes""
+-Click on the ""Save Page""
+
+Observed Result:
+The categories appear in wiki text format in the view mode of the page.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12703}",1383611400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ejqmybntf4qgjjx56ees,task_description,resolved
+VisualEditor: Categories are showing up in wikitext format in the view mode of a page,Verified in betalabs,1383764711,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ejqmybntf4qgjjx56ees,task_subcomment,NA
+VisualEditor: Categories are showing up in wikitext format in the view mode of a page,Fixed in https://gerrit.wikimedia.org/r/93640,1383702017,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ejqmybntf4qgjjx56ees,task_subcomment,NA
+VisualEditor: Categories are showing up in wikitext format in the view mode of a page,Thanks for reporting this. It looks like newly added categories are getting mangled this way because Parsoid was rolled back to a version that does not recognize the new mw:PageProp/Category type we're sending it. Gabriel and I are looking into the possibility of redeploying Parsoid with the UTF8 bug fixed later today.,1383612777,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ejqmybntf4qgjjx56ees,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"VE is breaking text encoding on *all* edits on fr.wp. Looks like UTF-8 is being intepreted as ISO-8859-2 or something.
+
+Example edits:
+https://fr.wikipedia.org/w/index.php?title=Tulle&curid=51555&diff=98030422&oldid=98028576
+https://fr.wikipedia.org/w/index.php?title=Herv%C3%A9_Jolly&diff=prev&oldid=98030048
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1383596160,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xnks7a25xfso6juiiyae,task_description,resolved
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"**Wikifram** wrote:
+
+Thank, Bartosz",1383917531,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"Let's just add ""VisualEditor"" to the summary to make this easier to find.",1383833607,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,Bugzilla is primarily a tool for developers and its primary classification is based on codebases (products and components).,1383828783,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"**Wikifram** wrote:
+
+(In reply to comment #9)
+> Reverting. This was a bug with config, not with code, and so belongs in
+> ""Wikimedia"". Also, it was a bug with Parsoid, not with VisualEditor.
+
+This means that people looking for VE bugs won't find it though; this may make sense from a devs point of view, but not from an editor's point of view. They encountered severe problems when editing with VE (and not with wikitext editing), but can't find that bug when searching VisualEditor bugs. 
+
+Take a look at the ""search"" box for Bugzilla; first is status, second is product;  how many people trying to find info on this or similar bugs will look for ""Wikimedia""?",1383826508,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"Reverting. This was a bug with config, not with code, and so belongs in ""Wikimedia"". Also, it was a bug with Parsoid, not with VisualEditor.",1383754027,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"**Wikifram** wrote:
+
+Why ""Wikimedia""? It only happened to VE edits, so for the sake of being able to track bugs in VE editing (fixed and non-fixed, major and minor), I have moved this back to VisualEditor. Wikimedia is much too vague for this...",1383725953,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"Not that it matters, but there is no Apache involved here. Moved it to General.",1383671105,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,Relabelling and moving to the correct component.,1383668957,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,Post mortem has been posted at https://wikitech.wikimedia.org/wiki/Incident_documentation/20131104-Parsoid,1383606352,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,This is fixed now that the Parsoid update has been reverted.,1383599438,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,(gwicke restored working version of the code. Awaiting a post-mortem :) ),1383598310,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,*** Bug 56584 has been marked as a duplicate of this bug. ***,1383598243,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"Happens on other wikis too, including sv and pl.",1383596651,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Tested on both the Italian and the English Wikipedia;
+Reach the bottom of any page: the style drop down menu does not open (it does when you're at the top of the page); the link inspector does not present the list of options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55465",1380976920,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-64s56xzrc22ustp2z7wx,task_description,resolved
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox",Note that this is fixed and has been deployed to the cluster. Please re-open if it still occurs for you after a refresh.,1381281033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88226 merged by Robmoen:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88226",1381274919,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88225 merged by Robmoen:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88225",1381274909,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox",*** Bug 55362 has been marked as a duplicate of this bug. ***,1381267451,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88226 had a related patch set uploaded by Jforrester:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88226",1381179193,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88225 had a related patch set uploaded by Jforrester:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88225",1381179178,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88195 merged by jenkins-bot:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88195",1381178266,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88195 had a related patch set uploaded by Trevor Parscal:
+Bug 55343 - The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88195",1381174021,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","(In reply to comment #6)
+> Krinkle, do I need to file a different bug for the non-working wikilink menu
+> part? Thanks.
+
+Yes, let's keep that separate. Could be related, but different user end bugs.",1381168024,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Krinkle, do I need to file a different bug for the non-working wikilink menu part? Thanks.",1381142922,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Can't reproduce it in Chrome, but in Firefox.
+
+Note that (this is difficult to see in the screenshots), the height decreases only when you close and re-open the More menu.
+
+If you open the More menu on top of the page and scroll down, it stays that way and only when you resize the window does the menu grow/shrink (as it should).
+
+But when you close/re-open the menu when scrolled down, it seems to belief the page is shorter than it really is and draw the menu too small (by a factor that relates to how far one scrolls down) until very soon it is completely collapsed.
+
+For me the collapsed point is far from the bottom of the page (I scrolled down a few pixels each time, and after having scrolled a mere 100px it was already completely collapsed).",1381105970,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","From bug 55357:
+
+TeamGale reports:
+
+""while I was getting more down to the page, the drop down menus were getting
+""shorter"" and sometimes disappear at the very end. I tried it to many pages to
+see if it was happening everywhere and it does. I don't know exactly how to
+describe it that's why I took screencaps from the page. All three are from the
+same page, in different height. See how the drop down menu of ""more"" can be
+seen entirely at the top of the page and how it gradually disappear as I get
+closer to the bottom. It's really weird!! The same thing happens when I am
+trying to add a wiki link in the article's text and to be honest, that's how I
+notice the gradually disappearing.""
+
+The screenshot is at [[File:Drop Down Menus.jpg]]
+
+I can reproduce this in Firefox 24 on Linux when using the vector skin, but not
+when using Monobook. 
+
+Trying to add a link after the end of the first paragraph I get no suggestions
+when my window is not maximised. Even when it is maximised it has completely
+disappeared by the end of the page. 
+
+What seems to matter is where the view is, not where the cursor is.",1381080341,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox",*** Bug 55357 has been marked as a duplicate of this bug. ***,1381080286,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Created attachment 13447
+Screenshot of the 0px-height menus
+
+These 3 menus have a height of 0px.
+
+I’ve attached a screenshot of these menus without height.
+
+**Attached**: {F12608}",1381055815,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox",Same bug with « more » menu,1380984143,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"load.php request for ve.base (when it crashes)
+
+At this time, on most Wikipedias that have just been switched to 1.22wmf19, VisualEditor is fatally broken.
+
+It cannot be consistently reproduced, but trying 3 or 4 times will hit the exception.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51766
+
+**Attached**: {F12689}",1380831300,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yznolfyf24iw64vdzaqk,task_description,resolved
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Fixed by touching the JS file in production.
+
+And yeah, this is another artefact of 43805, I think. :-(",1380839704,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),*or bug 43805,1380838980,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),Is this a dupe of bug 51766 or bug 51766?,1380838956,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Contrary to what one might think, both scenarios do not automatically resolve themselves the next 5-minute window of the startup module.
+
+The next time the startup module is generated, 5 minutes later, the max() timestamp of a module will still be the same.
+
+Touching startup.js won't help either.
+
+You'd have to artificially touch the individual module that got corrupted in cache and sync it and hope the same race condition won't happen again.",1380832743,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"The two ve.base request are (naturally) from different cache servers, but the Content-Length is identical, and the Age is close enough (sent out at different times, and my request is at a few seconds later as well).
+
+
+However the ve.core request is significantly different (eventhough we're giving the exact same url with the same timestamp from the startup module).
+
+I think this is a case where it once again shows how conceptually flawed our deployment system is (swapping out files and directory inside /a/common while apache is still fully serving and pooled) – or, how we did not take this into account in the design of ResourceLoader (take your pick).
+
+As a result I think one of the following 2 scenarios happened:
+
+Scenario A:
+- sync deployment starts
+- sync to srv100 complete
+- user visits Wikipedia
+- user requests load.php?module=startup
+  - load balancer picks srv100
+- user requests load.php?module=foo&version=123
+  - (timestamp the user got from srv100)
+  - load balancer picks srv200, which still runs the old code
+  - this url is now cached on some servers
+- user requests load.php?module=bar&version=212
+- sync to srv200 complete
+- sync deployment ends
+
+
+Imagine module bar depends on the (new version of) module foo. From this point on, users hitting srv100 for the module=foo request will keep getting an old version and results in broken scripts in unpredictable ways.
+
+
+
+Scenario B:
+- sync deployment starts
+- sync to srv100 complete
+- user visits Wikipedia
+- user requests load.php?module=startup
+  - load balancer picks srv100
+- sync to srv200 is busy (started, but not complete)
+- user requests load.php?module=foo&version=123
+  - (timestamp the user got from srv100)
+  - load balancer picks srv200, which has mixed code
+    so some of the files concatenated/minified are old some are new
+  - this url is now cached on some servers
+- sync to srv200 finishes
+- user requests load.php?module=bar&version=212
+- sync deployment ends
+
+In this scenario a dependency between different requests/modules doesn't even matter because in our deployment system a server can even be in mixed state within itself (as opposed to a mixed state across the datacenter, as scenario A).
+
+Again, it is cached under the new timestamp.",1380832336,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Created attachment 13436
+load.php request for ve.core (when it does not crash)
+
+**Attached**: {F12692}",1380831357,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Created attachment 13435
+load.php request for ve.core (when it crashes)
+
+**Attached**: {F12691}",1380831344,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Created attachment 13434
+load.php request for ve.base (when it does not crash)
+
+**Attached**: {F12690}",1380831326,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Splitting from bug 54322.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1380823320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ez4hz7oidp3mnpniacp,task_description,resolved
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"(In reply to comment #3)
+> Change 87442 merged by jenkins-bot:
+> ve.Element: Fallback to body, window is not scrollable
+> 
+> https://gerrit.wikimedia.org/r/87442
+This was just deployed.",1380843163,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87466 merged by jenkins-bot:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87466",1380841953,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87467 merged by jenkins-bot:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87467",1380841897,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87467 had a related patch set uploaded by Jforrester:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87467",1380839286,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87466 had a related patch set uploaded by Jforrester:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87466",1380839274,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87442 merged by jenkins-bot:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87442",1380839259,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87442 had a related patch set uploaded by Krinkle:
+(DRAFT) ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87442",1380832685,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"I can reproduce this in Chrome on en.wikipedia.org. Though not every time.
+
+Stack trace:
+
+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
+
+In plain English:
+- User clicks Page settings button
+- Dialog doesn't exist yet, so we instantiate it and initialise it
+- MWMetaDialog.initialize adds the 'categories' section
+- SelectWidget sees we don't have a selected panel yet, and now that
+  we have > 0 panels, it selects this new one
+- OptionWidget is brave and tries to ensure the selected panel is
+  visibile attempting to scroll it into view
+- ve.Element traverses up from the panel element until it eventually is
+  unable to find any element that is scrollable and falls back to
+  ve.Element.getWindow( el )
+- We hand off this element (= detached iframe's window), to $.fn.animate
+  which will try to animate scrollTop to 60px.
+
+Both in our jQuery version (v1.8.3) and the current one in use on jquery.com (v1.9.1) animating scrollTop on either window, document or document.documentElement (<html>) is not supported and results in :
+
+
+$(window).animate({'scrollTop': 100})
+< TypeError: Cannot use 'in' operator to search for 'scrollTop' in undefined
+
+* $.css: There is no window.style, and thus no 'scrollTop' in window.style
+* Also, there is no window.scrollTop
+
+$(document).animate({'scrollTop': 100})
+< TypeError: Cannot read property 'ownerDocument' of null
+
+* There is no document.scrollTop.
+
+$(document.documentElement).animate({'scrollTop': 100})
+> [ <html> ]
+
+* No exception, but scroll unchanged.
+* There is a document.documentElement.scrollTop, but it doesn't appear to
+  do anything (defaults to 0, setting is a no-op)
+
+ 
+$(document.body).animate({'scrollTop': 100})
+> [ <body> ]
+
+* Works!
+
+
+
+.... so, we should fix getClosestScrollableContainer to not fallback to window, because that's not a viable fallback as that is in fact not a scrollable container.",1380830178,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+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}",1380558180,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-mvlnrj6updlhvfhvduhk,task_description,resolved
+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",1380559572,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mvlnrj6updlhvfhvduhk,task_subcomment,NA
+VisualEditor: Editing at top of page shows pawn/slug character,*** Bug 54785 has been marked as a duplicate of this bug. ***,1380559441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mvlnrj6updlhvfhvduhk,task_subcomment,NA
+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",1380558906,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mvlnrj6updlhvfhvduhk,task_subcomment,NA
+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",1380383040,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_description,invalid
+Don't release any new VE updates for three months,"**Wikifram** wrote:
+
+Allright, thanks to both for the reply.",1380707473,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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.""",1380637726,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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?",1380583797,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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.",1380525615,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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.",1380525374,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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]].",1380395466,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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.",1380394985,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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",1380298800,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_description,resolved
+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.",1406341511,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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 .",1406307637,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.",1406146981,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,"Um, folks, this may be happening again... please see bug:61272...",1392229880,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,*** Bug 54976 has been marked as a duplicate of this bug. ***,1380936671,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.",1380843132,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380842062,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380842006,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380837106,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380837082,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380837069,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380836809,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,*** Bug 54917 has been marked as a duplicate of this bug. ***,1380835733,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.,1380832805,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.,1380832424,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380831976,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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)",1380789059,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,"My edit above to [[OpenOffice.org]] was in Firefox 24.0, Ubuntu 12.04 distro version.",1380644594,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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 ""<ref name="":0"" />"", and it's added another spurious one of those higher up",1380643572,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,"Please replace the word ""pawns"" with ""snowmen"". Sorry for the confusion.",1380643247,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.",1380300630,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,"**seudeau** wrote:
+
+%%%*** Bug 54708 has been marked as a duplicate of this bug. ***%%%",1380300556,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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  :-)>>",1380299308,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+"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",1379680980,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_description,resolved
+"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",1379977939,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379977741,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379977609,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379977566,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379702067,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379684992,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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"")",1379683942,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379683839,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+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",1379613840,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_description,resolved
+VisualEditor: [Regression] Unnamed references get their names corrupted,*** Bug 54445 has been marked as a duplicate of this bug. ***,1380836921,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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).",1380542637,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+VisualEditor: [Regression] Unnamed references get their names corrupted,*** Bug 54654 has been marked as a duplicate of this bug. ***,1380220185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379977590,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379977489,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379977417,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379977381,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379680077,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+VisualEditor: [Regression] Unnamed references get their names corrupted,"Change 85144 had a related patch set uploaded by Catrope:
+Failing test for <ref name="":3""> bug
+
+https://gerrit.wikimedia.org/r/85144",1379634802,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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 <ref> 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 <ref name="":3""> 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 <ref name="":n""> tags to the source), then removing or reordering references so the ref tags are aligned exactly right for this bug to occur.",1379625242,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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: ""êtt<newline>t"" 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",1378943700,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-mb4drpsu5auacyiu42kp,task_description,resolved
+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 ***",1378959962,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mb4drpsu5auacyiu42kp,task_subcomment,NA
+VisualEditor: Corruption with circumflexes,"This is a dupe of bug 53747, bug 53680 or both.",1378945993,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mb4drpsu5auacyiu42kp,task_subcomment,NA
+VisualEditor: Corruption with circumflexes,"Also, circumflexes that are entered in VE are completely stripped on save. Instead, characters are jumping around to its location.",1378944232,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-mb4drpsu5auacyiu42kp,task_subcomment,NA
+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",1378296540,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_description,resolved
+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 :/",1379174957,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.",1378958511,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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!",1378943228,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.",1378745638,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.,1378745123,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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)",1378402971,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.,1378313646,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.",1378313289,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.",1378297413,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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",1378296668,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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",1378127940,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_description,resolved
+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. ***,1378959962,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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.",1378958522,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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!",1378943119,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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.",1378309729,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,Same as bug 53747?,1378308416,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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 <save> or even <backspace> 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.",1378307780,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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.",1378194601,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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",1377477420,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5bbhrorxovykfuz52i3u,task_description,resolved
+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).,1378223041,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-5bbhrorxovykfuz52i3u,task_subcomment,NA
+Parsoid: Annotated text after a template is deleted,"
+
+*** This bug has been marked as a duplicate of bug 53434 ***",1378222889,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-5bbhrorxovykfuz52i3u,task_subcomment,NA
+Parsoid: Annotated text after a template is deleted,"HTML
+
+<p><span typeof=""mw:Transclusion"" data-mw=""{&quot;target&quot;:{&quot;href&quot;:&quot;Template:Inline&quot;,&quot;wt&quot;:&quot;Inline&quot;},&quot;params&quot;:{&quot;1&quot;:{&quot;wt&quot;:&quot;Foo&quot;}}}""></span><b>bar</b>quux</p>
+
+Expected wikitext
+
+{{Inline|Foo}}'''bar'''quux
+
+Actual wikitext
+
+{{Inline|Foo}}quux
+
+:(",1377884301,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5bbhrorxovykfuz52i3u,task_subcomment,NA
+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.",1377538637,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5bbhrorxovykfuz52i3u,task_subcomment,NA
+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}",1377188700,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-2o36gh7lztukgi2lajdg,task_description,resolved
+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",1392229930,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1392218875,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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.",1392138773,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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.",1392137133,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+VisualEditor: [Regression] Link inspector prevents insertion of section links,… and now deployed.,1377213471,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377212160,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377212156,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377211215,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377211126,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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.,1377206624,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377206517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377196029,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+VisualEditor: [Regression] Link inspector prevents insertion of section links,"Ah, good that someone already reported. Confirmed in mediawiki.org.",1377190610,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1375867440,PHID-USER-mapumhlp3gw5qefhvafn,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_description,resolved
+VisualEditor: Template gets removed without editing it,Moving to date we likely fixed this with the changes to DM.,1379348384,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+VisualEditor: Template gets removed without editing it,"I can't reproduce it anymore either, so I'm closing it.",1378994061,PHID-USER-mapumhlp3gw5qefhvafn,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+VisualEditor: Template gets removed without editing it,"* ""I can't reproduce"" ... the issue. :)",1376929139,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+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
+}}",1376928153,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+VisualEditor: Template gets removed without editing it,"Roan, thoughts? Selser issue?",1375934940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+"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",1375462680,PHID-USER-ppvnwr24o32pux3le5ov,PHID-TASK-2czs2gshamoxbwaweocz,task_description,resolved
+"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.,1375469052,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2czs2gshamoxbwaweocz,task_subcomment,NA
+"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",1375468933,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2czs2gshamoxbwaweocz,task_subcomment,NA
+"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",1375468694,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2czs2gshamoxbwaweocz,task_subcomment,NA
+"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link","<<When I was trying to add a link to Classic XI, (didn't know it didn't exist) it repeatedly took the word ""Classic"" and continually tried to make the link go to Classical music. [...] --buffbills7701 19:42, 1 August 2013 (UTC)>>
+
+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",1375391400,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-q6smnzvqe6vc4eby67me,task_description,resolved
+"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link",Fixed and will be deployed tonight.,1375408346,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"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",1375408026,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"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",1375404594,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"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.",1375392847,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"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.",1375392350,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link",*** Bug 52421 has been marked as a duplicate of this bug. ***,1375391536,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+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",1375331160,PHID-USER-7ey733eainlhx5xqp4d3,PHID-TASK-x7tgs2fyboki473gy3pu,task_description,resolved
+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.",1375332474,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-x7tgs2fyboki473gy3pu,task_subcomment,NA
+VisualEditor.php attempts to register a hook handler that was removed,Ia4e2a7854b3a2a5cbbe4da,1375331403,PHID-USER-7ey733eainlhx5xqp4d3,PHID-TASK-x7tgs2fyboki473gy3pu,task_subcomment,NA
+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}",1375261620,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-btjddhvc23db2mven5vt,task_description,resolved
+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. ***,1375312992,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,This is fixed and being pushed live right now.,1375312939,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375308246,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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. ***,1375303552,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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]]",1375296594,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375291680,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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.",1375287482,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375287357,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375286909,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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.",1375280775,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375120080,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hdwzoxwzxwme4zwudykf,task_description,resolved
+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.",1375156109,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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"".",1375144061,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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.",1375135721,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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.",1375124710,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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.",1375124287,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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",1375123842,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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",1375123752,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+Anonymous users getting VisualEditor on German Wikipedia and making edits,"This appears to be a caching issue, yes",1375122380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+"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",1375049820,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sa6s63ajvv65ik2b7344,task_description,resolved
+"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",1375208914,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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. :-)",1375136346,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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?",1375129191,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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.,1375122779,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375119647,PHID-USER-dczyqgtdvr5hclqcljrr,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375116096,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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.",1375115973,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia",This is now done.,1375115930,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375115875,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375112857,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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?",1375086074,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375075738,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375073521,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375072767,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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: <https://gerrit.wikimedia.org/r/#/c/75543/4/wmf-config/InitialiseSettings.php,unified>.
+
+wmgVisualEditorDefault would be set to false for dewiki.
+
+wmgVisualEditorDisableForAnons would be left as true for dewiki.
+
+Is this correct?",1375070977,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","From bug 49998 comment 8:
+
+---
+In the quick poll (see #7) the results at the moment are as following:
+
+1) enabeling VE as default for all users: 21 votes
+2) VE as default for logged-in users: 6 votes
+3) VE to be opt-in only until all bugs are fixed: 430 votes (!)
+4) enabeling VE under another link name (suggestion was ""Visual Editor (beta)""
+instead of ""Bearbeiten"" (""edit"")): 31 votes
+
+According to this large majority of users who oppose defaulting VE by tomorrow,
+I hereby ask you to put VE back to opt-in for logged-in users until the most
+important bugs are fixed. Thank you.
+---",1375070446,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","From bug 49998 comment 7:
+
+---
+the German wikipedia just started a quick poll over the weekend to at least
+postpone this activation for anonymous users on monday:
+
+https://de.wikipedia.org/wiki/Wikipedia:Umfragen/VisualEditor_Opt-in
+
+the poll has currently also a option for the previous state where VE was Opt-in
+for users instead of Opt-out if this is still possible.
+
+It would be appreciated to take the outcome on monday into account and postpone
+this activation for dewiki if desired.
+---",1375070430,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"VisualEditor: A <nowiki> on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1374661020,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_description,resolved
+"VisualEditor: A <nowiki> on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare",Now fixed.,1375139113,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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",1375127248,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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",1374883810,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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.",1374796813,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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",1374730027,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","Change 75636 merged by jenkins-bot:
+Put <nowiki> edting in experimental for now
+
+https://gerrit.wikimedia.org/r/75636",1374683103,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","Change 75636 had a related patch set uploaded by Jforrester:
+Put <nowiki> edting in experimental for now
+
+https://gerrit.wikimedia.org/r/75636",1374682887,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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 <nowiki> 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",1374661437,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+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",1374250680,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-shna2ollivhvhx6ukpk5,task_description,resolved
+VisualEditor: Newly-added references need a page save before being reusable,This is still the case for references added inside a table though?,1432297031,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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",1377889950,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+VisualEditor: Newly-added references need a page save before being reusable,Now fixed in master and will be deployed next week.,1377889823,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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",1377885677,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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.",1375427074,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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.",1375406536,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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.)",1375398952,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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.",1375346304,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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",1373508480,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_description,resolved
+VisualEditor: Refactor references dialog to allow immediate insertion of reference content,This was done and deployed last week.,1374646985,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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",1374183566,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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",1374182076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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",1374090269,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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.",1373510033,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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",1373505480,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_description,resolved
+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]]",1418771598,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1418759614,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1374636985,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"**wicke** wrote:
+
+%%%*** Bug 51175 has been marked as a duplicate of this bug. ***%%%",1374270889,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373928857,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373927744,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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?",1373756996,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,*** Bug 51161 has been marked as a duplicate of this bug. ***,1373756843,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373590110,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373590022,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373561945,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373561592,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373561010,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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=""{&quot;target&quot;:{&quot;wt&quot;:&quot;echo&quot;,&quot;href&quot;:&quot;../Template:Echo&quot;},&quot;params&quot;:{&quot;1&quot;:{&quot;wt&quot;:&quot;foo&quot;}},&quot;i&quot;:0}""
+
+data-mw through VE after changing 'foo' to 'bar':
+data-mw=""{&quot;target&quot;:{&quot;wt&quot;:&quot;echo&quot;,&quot;href&quot;:&quot;../Template:Echo&quot;},&quot;params&quot;:{&quot;1&quot;:{&quot;wt&quot;:&quot;bar&quot;}}}""
+
+Note that the ""i"" member is gone.",1373555079,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,Aha. Gotcha.,1373554659,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373554601,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"It is either data-mw.i or data-mw.parts[<n>].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 
+<body><p about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""a"":{""wt"":""foo""},""b"":{""wt"":""c""}},""i"":0}' data-parsoid='{""dsr"":[0,27,null,null],""src"":""{{echo|a   = foo\n|b   = c}}"",""pi"":[[{""k"":""a"",""spc"":["""",""   "","" "",""\n""]},{""k"":""b"",""spc"":["""",""   "","" "",""""]}]]}'>{{{1}}}</p>
+</body>",1373554563,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373554450,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,*** Bug 51161 has been marked as a duplicate of this bug. ***,1373554368,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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?",1373507539,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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,1373505675,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373067660,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ldrbm7zdbq6hmivijiqq,task_description,resolved
+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],1440343623,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ldrbm7zdbq6hmivijiqq,task_subcomment,NA
+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.",1373916884,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ldrbm7zdbq6hmivijiqq,task_subcomment,NA
+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",1372968840,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_description,resolved
+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",1395689849,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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",1395363046,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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.,1394036852,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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?",1394027803,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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.",1390411348,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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?",1390406910,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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. ***,1385382810,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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.",1384848197,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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. ***,1384845361,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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. ***,1384845303,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+"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}",1372931040,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-b5zzf7lh657agk5cdqkw,task_description,resolved
+"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)",Merged and will hopefully go out soon.,1373053892,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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",1373049617,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1373016135,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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",1373004125,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1372969315,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1372952624,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1372952431,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1372951540,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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}",1372910460,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-r4klwzo7lxdsgw53zery,task_description,resolved
+"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.,1373497407,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r4klwzo7lxdsgw53zery,task_subcomment,NA
+"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",1373497073,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r4klwzo7lxdsgw53zery,task_subcomment,NA
+"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",1373483215,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r4klwzo7lxdsgw53zery,task_subcomment,NA
+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",1372896120,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_description,resolved
+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.,1373359485,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.",1373333744,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.,1373303590,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.),1373303527,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.",1373303412,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.",1373301240,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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",1372901309,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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}",1372793160,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_description,duplicate
+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.",1377128046,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1374018125,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1374017295,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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?",1374016361,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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).",1373642100,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1373070573,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1373066776,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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). <B>Please be aware that wiki syntax (e.g.
+> ""[[link to another page]]"") will not work in this editing mode.</B> 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.",1373066249,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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). <B>Please be aware that wiki syntax (e.g. ""[[link to another page]]"") will not work in this editing mode.</B> 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.",1373065091,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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?",1372817358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1372801407,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1372801273,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1372796561,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.,1372793189,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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",1372554780,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-mtdexeiuriq5cdelhc5o,task_description,resolved
+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.",1373328432,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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",1373325377,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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. ***,1373155391,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.,1373061153,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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",1373010998,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1373010956,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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).",1373009694,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1373009612,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1372984760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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?!",1372976195,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1372973949,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1372973401,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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. ***,1372747009,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1372597774,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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}",1372597673,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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",1372596485,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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?",1372558082,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+"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",1372520820,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-4rutvvnh7fiqox2z3go4,task_description,resolved
+"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.",1373917573,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373917479,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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.",1373780299,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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!,1373771135,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work",*** Bug 51302 has been marked as a duplicate of this bug. ***,1373759844,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373653678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373584937,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373584284,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373566281,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373566278,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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 <references\>, 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}",1372515720,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_description,resolved
+"VisualEditor: ref warning appears within template that contains references, post-modification",I'm forking this off into bug 51337.,1373852785,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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",1373812887,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"VisualEditor: ref warning appears within template that contains references, post-modification",Should probably leave this open to track improvements.,1373543056,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"VisualEditor: ref warning appears within template that contains references, post-modification",Also: https://gerrit.wikimedia.org/r/73096,1373543029,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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.",1373497983,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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",1373497512,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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",1373492178,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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.",1372690617,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+VisualEditor: Reference toolbar icon missing in wmf9,"The references list one is still there; did Trevor's change break it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372404000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vek6torvduvoml55paap,task_description,resolved
+VisualEditor: Reference toolbar icon missing in wmf9,Fixed with new pull.,1372442860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vek6torvduvoml55paap,task_subcomment,NA
+VisualEditor: &nbsp;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",1372385580,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-77axhndq3mqnxx2kqcjc,task_description,declined
+VisualEditor: &nbsp;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.",1373056593,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+VisualEditor: &nbsp;s converted to space characters (32s not 160s) on round-trip,Chrome Version 27.0.1453.116 on Windows 7 Home Premium.,1372412479,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+VisualEditor: &nbsp;s converted to space characters (32s not 160s) on round-trip,Will inquire.,1372386501,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+VisualEditor: &nbsp;s converted to space characters (32s not 160s) on round-trip,Do you know which browser was used for this edit?,1372386315,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+VisualEditor: &nbsp;s converted to space characters (32s not 160s) on round-trip,Odd. I can't reproduce this locally or on the article.,1372386209,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+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",1372290900,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-y6bkvqygqya2opqdmv3c,task_description,resolved
+load.php error?  many symptoms...,Ah it seems the cached load.php got cleared finally.   I got AFT and VisualEdit working properly now :-],1372325082,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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 :(",1372324986,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+load.php error?  many symptoms...,Changes above reverts the two patches mentionned in bug 45918.,1372324616,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+load.php error?  many symptoms...,Related URL: https://gerrit.wikimedia.org/r/70806 (Gerrit Change Ie373d1f407788a8e2456c3d8a34cc79ac9ed8bb6),1372324322,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+load.php error?  many symptoms...,Related URL: https://gerrit.wikimedia.org/r/70805 (Gerrit Change I02ed22e324435e362cabdfc67e69c224ad9e2550),1372324295,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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""",1372323805,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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",1372294623,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+load.php error?  many symptoms...,"not a blocker, sorry, mw.o is a workaround",1372294116,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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.",1372293962,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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",1372281720,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-d2rlcey47hxosbomhyfo,task_description,resolved
+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!",1372294327,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d2rlcey47hxosbomhyfo,task_subcomment,NA
+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",1372267200,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qadhatjuo4mjlpfaic7,task_description,resolved
+VisualEditor: Be able to have enabled for all logged-in users but not anonymous users,We achieved this. Obviously. :-),1372726673,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qadhatjuo4mjlpfaic7,task_subcomment,NA
+"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","Screenshot
+
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11809}",1372263180,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_description,resolved
+"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",1372794337,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"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",1372354311,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","Appears to be now fixed; marking as resolved. Thanks, Rob! :)",1372340043,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"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.,1372269443,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","(Firefox 21.0, Windows 7)",1372263239,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"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}",1372146600,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-k6rdk2swblj7w4zhblsz,task_description,resolved
+"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.,1372379698,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+"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",1372379566,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+"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",1372361704,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+"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.,1372270138,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+"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.,1372187179,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+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",1372115280,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-ih6vrsjge6cjapq5orey,task_description,resolved
+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.",1372266003,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+VisualEditor: Link inspector creates the text twice if not running on a selection,"Great! Thanks for the quick response, James and team!",1372265845,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+VisualEditor: Link inspector creates the text twice if not running on a selection,Fixed and being deployed right now.,1372264523,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+VisualEditor: Link inspector creates the text twice if not running on a selection,Related URL: https://gerrit.wikimedia.org/r/70623 (Gerrit Change I8c68468a95cddbc7efb222cf3a1f9868b2949285),1372251641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+VisualEditor: Link inspector creates the text twice if not running on a selection,*** Bug 50188 has been marked as a duplicate of this bug. ***,1372214415,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+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?,1372115781,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+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",1372106580,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_description,resolved
+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.",1372704161,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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.",1372701493,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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",1372355719,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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?",1372314964,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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.",1372292154,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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.",1372291914,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+VisualEditor: Transclusions not properly round-tripped,"
+
+*** This bug has been marked as a duplicate of bug 50070 ***",1372127871,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+VisualEditor: Transclusions not properly round-tripped,The nowiki escaping in Schuylar_Oordt is Parsoid bug 50144. It would normally be hidden with selective serialization.,1372123167,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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",1372120806,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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",1372100100,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cl3n6ut5q64yapdxwsov,task_description,resolved
+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.",1373500285,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373497930,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373494750,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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 <span>\n</span><table>...</table><link>
+* 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 <p>
+* The browser receives this HTML and is unhappy about the <table> inside the <p>, so it moves both the <table> and the <link> out of the <p>, leaving <p><span>\n</span></p><table>...</table><link>. 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 <p> 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;""",1373494553,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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,1373484409,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,*** Bug 50554 has been marked as a duplicate of this bug. ***,1373484208,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,"See also: bug 50554, bug 50385.",1373484037,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373483575,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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 <link> 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.",1373479449,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373476466,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,Possibly related: bug 50332.,1373476038,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373475508,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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 <link rel=""mw:WikiLink/Category"" href=""Category:foobar""> (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 <table> 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?",1373475152,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373440943,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.,1373439890,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373439837,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373439682,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373399973,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.,1373303777,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373301012,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373130413,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.,1373053343,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.,1372360097,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,"Roan, thoughts?",1372109030,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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,1372105662,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,"Perhaps related to:
+
+| PLACE OF BIRTH    =[Alexandria], [[Egypt]]",1372100226,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+VisualEditor: Link editor does not work in the reference editor in Firefox,"Self-explanatory; Firefox 21.0, Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372094820,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-fftdwlrkyjt5yc2hamtk,task_description,resolved
+VisualEditor: Link editor does not work in the reference editor in Firefox,Fixed and will be going out in a few minutes.,1372210400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fftdwlrkyjt5yc2hamtk,task_subcomment,NA
+VisualEditor: Link editor does not work in the reference editor in Firefox,Patched in: https://gerrit.wikimedia.org/r/#/c/70559/,1372202020,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-fftdwlrkyjt5yc2hamtk,task_subcomment,NA
+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",1372089360,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-qsgca2wst2byl7ix2pwv,task_description,resolved
+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",1395689846,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+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",1395363039,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+VisualEditor: Provide way for local wikis to auto-prompt reference templates,*** Bug 51185 has been marked as a duplicate of this bug. ***,1377829415,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+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
+> <ref> tags and not about templates that add the <ref> tags themselves.
+
+Correct.",1374859109,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+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 <ref> tags and not about templates that add the <ref> tags themselves.,1374823336,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+VisualEditor: Provide way for local wikis to auto-prompt reference templates,*** Bug 51683 has been marked as a duplicate of this bug. ***,1374260100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+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}",1372035120,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-awj25x4zsacz62adi3j5,task_description,resolved
+VisualEditor: Template-based references never editable from reference editor in Firefox,Related URL: https://gerrit.wikimedia.org/r/70119 (Gerrit Change I29e210aba9a6265d8364ff8ae49408cb4c2428b9),1372040060,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-awj25x4zsacz62adi3j5,task_subcomment,NA
+VisualEditor: Template-based references never editable from reference editor in Firefox,Confirmed by a second user.,1372035227,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-awj25x4zsacz62adi3j5,task_subcomment,NA
+"VisualEditor: If a sanity check doesn't work out, encourage the user to do a wikitext diff before saving","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372029300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e3u3nzdde2xltny25tvr,task_description,resolved
+"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.,1372387323,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e3u3nzdde2xltny25tvr,task_subcomment,NA
+"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",1372387308,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-e3u3nzdde2xltny25tvr,task_subcomment,NA
+"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),1372029924,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-e3u3nzdde2xltny25tvr,task_subcomment,NA
+VisualEditor: Metadata not preserved in references,"They get stripped out when rendered back to HTML.
+
+e.g.
+
+<ref>Foo<!--bar--></ref>
+
+->
+
+<ref>Foo</ref>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372007340,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ibds6gk456ofg6szjteu,task_description,resolved
+VisualEditor: Metadata not preserved in references,Related URL: https://gerrit.wikimedia.org/r/70060 (Gerrit Change I3bbea49132ef4a720a147ba9b170c39a0c00f711),1372008261,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ibds6gk456ofg6szjteu,task_subcomment,NA
+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 <b> 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",1371986880,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-yc4hfzr5ombibggchvok,task_description,resolved
+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",1372001636,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yc4hfzr5ombibggchvok,task_subcomment,NA
+"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",1371859260,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7sjurdxqyilrckxefznc,task_description,resolved
+"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.,1373053912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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",1373049614,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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",1373039964,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1373039949,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1373035918,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1373033397,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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),1372289786,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.,1372280988,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1372264953,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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. ***,1372264868,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1372252282,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.,1372173256,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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",1371855300,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-uuaax5ooenq6lyv32r7j,task_description,resolved
+"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.",1372355114,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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",1372354202,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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),1372255145,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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 <a href=""Porcupine"">p</a><a href=""Porcupine"">orcupine</a> (adjacent <a>s with the same href) and possibly <a href=""porcupine"">p</a><a href=""Porcupine"">orcupine</a> as well (adjacent <a>s with different hrefs that normalize to the same title).",1372036243,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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.",1371982074,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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?",1371855415,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+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",1371684540,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-7sbdbkrfcvaejzeycoty,task_description,resolved
+mediawiki/extensions.git does not update some extensions,"Change 317923 merged by Dzahn:
+contint: remove python-requests
+
+[[https://gerrit.wikimedia.org/r/317923]]",1477523670,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]
+",1477429966,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]",1474048424,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]
+",1474047362,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]",1473409160,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]",1473361798,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1473329510,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]
+",1473329426,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]
+",1473329159,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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] <hashar> 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",1473329009,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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] <hashar> 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. ",1473328926,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1465398703,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Upstream bug is https://code.google.com/p/gerrit/issues/detail?id=2393,1454694024,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Same issue with `Cards` and `mediawiki/extensions/Cards` at T125182,1454594877,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1390501982,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1390341294,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1390341257,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1390334487,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1390334462,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1390332631,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389991554,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"Still failing :(
+
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-sync-gerrit/9/console",1389942210,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.,1389910865,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389909836,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389892786,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"Change 107862 merged by jenkins-bot:
+mwext-VisualEditor-sync-gerrit
+
+https://gerrit.wikimedia.org/r/107862",1389891995,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389891791,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389886128,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389885751,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389882277,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389882267,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389866906,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389866900,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389796145,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389796012,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389795448,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389722159,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389720044,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.,1389653054,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Assigning to self and moving to CI,1389652979,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389652459,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Re-opening rather than having a fork in bug 59758.,1389149782,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,*** Bug 59758 has been marked as a duplicate of this bug. ***,1389149751,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"happened again, see bug 59758",1389084905,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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/<foo>.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"".",1378225794,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1378204152,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,VisualEditor is finally working. I hope. I pray.,1376592201,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.,1374253962,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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'",1374232184,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1374228032,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,*** Bug 51635 has been marked as a duplicate of this bug. ***,1374228000,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,*** Bug 48893 has been marked as a duplicate of this bug. ***,1374227951,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"Change 73736 merged by Hashar:
+update VisualEditor to latest master
+
+https://gerrit.wikimedia.org/r/73736",1373881472,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1373881426,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,I hate life.,1373521899,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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 :(",1373491637,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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).",1372775601,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"I fixed it before.
+
+Now I've fixed it once again.
+
+This is annoying.",1372695781,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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 :)",1372694917,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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
+$",1372669990,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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
+
+:-)",1371759767,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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!",1371759694,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1371759443,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Actually moving this bug under 'git/gerrit'.,1371754174,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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'.",1371722282,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1371721861,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1371656400,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-j6slyvhfp3d6ozltvruk,task_description,resolved
+VisualEditor: Parsoid ate a reference,This is now fixed (Parsoid selser issue); sorry!,1371782480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j6slyvhfp3d6ozltvruk,task_subcomment,NA
+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!",1371779509,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j6slyvhfp3d6ozltvruk,task_subcomment,NA
+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",1371582180,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ivktalncu225io76zzys,task_description,resolved
+VisualEditor: Image insertion does not work,Fixed. Sorry about this.,1371782583,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ivktalncu225io76zzys,task_subcomment,NA
+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",1371542880,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-vm7v6vojqzplbnspgwqk,task_description,resolved
+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.",1372027620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vm7v6vojqzplbnspgwqk,task_subcomment,NA
+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.",1371549819,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-vm7v6vojqzplbnspgwqk,task_subcomment,NA
+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",1371547249,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-vm7v6vojqzplbnspgwqk,task_subcomment,NA
+VisualEditor: Page with a <references /> block and no <ref>s throws fatal error on load,"Have a page with a <references /> block but no <ref>s and you get:
+
+| Uncaught TypeError: Cannot call method 'connect' of null 
+
+This is bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371431820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cheeem2iuszopjmd3axj,task_description,resolved
+VisualEditor: Page with a <references /> block and no <ref>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.",1371479770,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cheeem2iuszopjmd3axj,task_subcomment,NA
+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",1371265140,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-b7q472kz3l2dnhbtziiw,task_description,resolved
+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.",1417635932,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+VisualEditor: HTML comments are dropped from transclusion calls,"verified in betalabs - HTML comments are preserved both - generally and, specifically, in transclusions.",1417635694,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+VisualEditor: HTML comments are dropped from transclusion calls,"That's a separate bug, will raise as such.",1372002624,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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 :)",1371996558,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.",1371511467,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.,1371465156,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.",1371425926,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+VisualEditor: HTML comments are dropped from transclusion calls,"[[Wikipedia:VisualEditor/Feedback#Removal_of_comments_in_Infobox]]
+
+See also bug 42124.",1371424680,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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",1371424467,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.",1371420455,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.",1371269621,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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",1371244680,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-2z2izcavd5te3dkswczw,task_description,resolved
+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. ***,1372002331,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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.",1371690785,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),What about commend 5 and comment 6?,1371684547,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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.",1371682009,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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:
+| <figure typeof=""mw:Image/Frame"" class="" mw-halign-right"">
+| <a rel=""mw:thumb"" href=""http://commons.wikimedia.org/wiki/File:Apples.jpg"">
+| <img src=""http://upload.wikimedia.org/wikipedia/commons/thumb/e/ee/Apples.jpg/
+|   100px-Apples.jpg"" width=""100"" height=""150"" resource=""undefined""></a></figure>
+| 
+| 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]].",1371659496,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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. ***,1371659407,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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"")",1371648653,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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:
+> <http://pt.wikipedia.org/w/index.
+> 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"".",1371640850,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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. ***,1371627753,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),I get the same type of error: <http://pt.wikipedia.org/w/index.php?title=PLoS_ONE&diff=36119075&oldid=34872658>,1371391157,PHID-USER-vyidforzdhnrsoweujao,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"For additional examples, if that will be helpful, see:
+http://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29&diff=560023092&oldid=541758155
+
+http://en.wikipedia.org/w/index.php?title=Keshi_%28demon%29&diff=559979773&oldid=559978871",1371305701,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"Roan, do we get the typeof:/etc. wrong at our end, or is this a Parsoid issue?",1371244860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: EventLogging gives the same pageViewSessionId for all edits,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371231960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-myow2awxzmx4c4ssz6ta,task_description,resolved
+VisualEditor: EventLogging gives the same pageViewSessionId for all edits,Merged and we'll get this out on Monday so we can test it.,1371234407,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-myow2awxzmx4c4ssz6ta,task_subcomment,NA
+VisualEditor: EventLogging gives the same pageViewSessionId for all edits,Related URL: https://gerrit.wikimedia.org/r/68712 (Gerrit Change Iddb9eb9c64b55b25445ddf9e474d312b685978a6),1371233987,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-myow2awxzmx4c4ssz6ta,task_subcomment,NA
+VisualEditor: EventLogging gives the same pageViewSessionId for all edits,"(In reply to comment #1)
+> 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.",1371232257,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-myow2awxzmx4c4ssz6ta,task_subcomment,NA
+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.",1371232111,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-myow2awxzmx4c4ssz6ta,task_subcomment,NA
+VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371231900,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-znkh7fhdepbxk6h3va36,task_description,resolved
+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.,1371234387,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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),1371233985,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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),1371233983,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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).",1371233068,PHID-USER-qb5aoo443n6fezsozhv4,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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. :-)",1371232172,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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",1371213300,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-m3novk5xasw5lqvg62ye,task_description,resolved
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,*** Bug 50049 has been marked as a duplicate of this bug. ***,1372004983,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Yes, <https://bugzilla.wikimedia.org/show_bug.cgi?id=49701>. It is apparently fixed.",1371657346,PHID-USER-vyidforzdhnrsoweujao,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,Did you open a new bug? If so could you please link it? I have someone with a similar issue.,1371652833,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Ah, sorry, I missed the tag. I think you should; this is certainly something different than what was happening here.",1371483619,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,It has the VisualEditor tag and was reported in the feedback page <http://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia%3AEditor_Visual%2FComent%C3%A1rios&diff=36129760&oldid=36054006>. Should I open a new bug?,1371482523,PHID-USER-vyidforzdhnrsoweujao,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"It's not, this bug had different symptoms, and that edit doesn't even seem to have been made using VE.",1371480754,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Not sure if this is related: <https://pt.wikipedia.org/w/index.php?title=CMM_-_Canal_Meninos_e_Meninas&diff=36129698&oldid=36129686>, but that edit was made today.",1371477080,PHID-USER-vyidforzdhnrsoweujao,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"To update, this bug was in an overly-keen Operations cacheing server configuration change which broke the caches' responses completely (and corrupted every response to not be what we want).
+
+Sorry everyone for the disruption; we've now found (and killed) this problem, and re-enabled VisualEditor as before.",1371235366,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"It looks like an update to the libraries Parsoid depends on might have caused this issue. It would have been visible in the diff, but since the user is not seeing that by default any more few noticed.
+
+Parsoid is rolled back, so this issue should be fixed.",1371223781,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"**ignatus31oct** wrote:
+
+(One more example from En-wiki) See this edit (if your traffic is easy, the diff is half-Mb):
+
+http://en.wikipedia.org/w/index.php?title=Russian_grammar&diff=559881732&oldid=558109653
+
+I only wanted to change one section, but after pressing a link everything was opened in VE. Well, I added text to different sections. There were no trouble with it, except that when I tried to type text into ''()'' italicised parentheses leaved by previous editor, when I pushed [BackSpace] at end (wrongly started to type in Cyrillic rather than Latin), first ( was doubled.
+
+When I entered enough and pushed ""Save"", I was introduced to type in the desc, and to view changes or to save page. I've just read the digest of how good is the VE now and pushed ""Save page"", but after a time I've seen.........",1371221239,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Also note; as you can see from the gerrit change above, it looks like Ariel and James will be temporarily disabling the VE until this is solved for. I'm going to go round and notify people now :)",1371221206,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,Related URL: https://gerrit.wikimedia.org/r/68667 (Gerrit Change I267c8ba13a6ec1444010ce996fba05dfcba460fa),1371221157,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,Related URL: https://gerrit.wikimedia.org/r/68667 (Gerrit Change I267c8ba13a6ec1444010ce996fba05dfcba460fa),1371221153,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"A note; I've just spoken to James F; a fix to this is highest-priority. I'm deeply sorry about this (and think I speak for James and the VE team on that front, too).",1371220263,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"(In reply to comment #3)
+> 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",1371219908,PHID-USER-jtxavgb3caz53o45csni,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+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",1371219726,PHID-USER-3qvsqam4jxugqg2l7qpw,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+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).,1371217642,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+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,1371215939,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+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",1371214660,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,*** Bug 49573 has been marked as a duplicate of this bug. ***,1371214602,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+VisualEditor: En hard-coded as TemplateData fetch language,"Should be user interface language.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1370893260,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g43ik5bj4ejp7p75b5p4,task_description,resolved
+VisualEditor: En hard-coded as TemplateData fetch language,"This is resolved in the latest version
+
+I3bcf924a3e179cb65f19e833277a39dfd3dad8bd",1370985573,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-g43ik5bj4ejp7p75b5p4,task_subcomment,NA
+"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",1370535240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v44oexl4vlksqgaeptjm,task_description,resolved
+"VisualEditor: Move back to ""normal"" Save dialog with optional rather than mandatory Review",Fixed and will go out with wmf7 from next Thursday.,1370654365,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v44oexl4vlksqgaeptjm,task_subcomment,NA
+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",1369387560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r7nekr4d3omjjmecwwq6,task_description,resolved
+VisualEditor: Link corruption oddity in production on links (Parsoid issue?),I believe this is now fixed.,1372017998,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r7nekr4d3omjjmecwwq6,task_subcomment,NA
+VisualEditor: Link corruption oddity in production on links (Parsoid issue?),Can't reproduce in master.,1369389553,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-r7nekr4d3omjjmecwwq6,task_subcomment,NA
+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",1368667200,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5refjnnnoyqumq4ge53g,task_description,resolved
+VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox,This is not an issue anymore.,1371602123,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-5refjnnnoyqumq4ge53g,task_subcomment,NA
+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",1368622500,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-glwrzzfq4ph2os2n2f6r,task_description,resolved
+VisualEditor: [Regression] Link inspector button doesn't work,Merged into master; will go out with wmf5.,1368638702,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-glwrzzfq4ph2os2n2f6r,task_subcomment,NA
+VisualEditor: [Regression] Link inspector button doesn't work,Related URL: https://gerrit.wikimedia.org/r/63850 (Gerrit Change Icda3305e422bedaf0d490b8fbe51f55b8c8e79e8),1368626182,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-glwrzzfq4ph2os2n2f6r,task_subcomment,NA
+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?)",1368625612,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-glwrzzfq4ph2os2n2f6r,task_subcomment,NA
+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",1368561900,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-52eneev7kw444gspkrww,task_description,resolved
+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.",1371142270,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-52eneev7kw444gspkrww,task_subcomment,NA
+VisualEditor: Pawn appears when creating new list item in Firefox,@Quim: Are you still able to reproduce this problem? I can't.,1371073013,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-52eneev7kw444gspkrww,task_subcomment,NA
+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?",1370177174,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-52eneev7kw444gspkrww,task_subcomment,NA
+VisualEditor: Indenting & unindenting multiple list items fails,"Problems in IndentationAction that Ed it working on right now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1368392940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r45sjfea3cr6rhagxvom,task_description,resolved
+VisualEditor: Indenting & unindenting multiple list items fails,Code is merged into wmf4.,1368471026,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+VisualEditor: Indenting & unindenting multiple list items fails,Related URL: https://gerrit.wikimedia.org/r/63485 (Gerrit Change I5ce0c385214f30c5e5c66b5b5b755c9937267cd0),1368466116,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+VisualEditor: Indenting & unindenting multiple list items fails,*** Bug 48069 has been marked as a duplicate of this bug. ***,1368465449,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+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.",1368465399,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+VisualEditor: Indenting & unindenting multiple list items fails,Fixed by https://gerrit.wikimedia.org/r/#/c/63394/,1368393902,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+VisualEditor: [Regression] Lists badly broken again,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1368386340,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-iowbxqgcysomfeaijbgp,task_description,resolved
+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",1384458232,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+VisualEditor: [Regression] Lists badly broken again,Fixed in https://gerrit.wikimedia.org/r/63413. Will close after it gets merged.,1368428040,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+VisualEditor: [Regression] Lists badly broken again,Related URL: https://gerrit.wikimedia.org/r/63413 (Gerrit Change I8d7aeffc8166487806e3489b054f508c5e9418ff),1368427993,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+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.",1368388912,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+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",1368386572,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+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 <br> has appeared from nowhere:
+  <p><br><span slug></span></p>
+
+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",1368384600,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vv7dhxcel5yesltb4ctu,task_description,resolved
+VisualEditor: Delete contents of slugged paragraph results in double line break visible,This is fixed with my refactor to handleDelete method.,1372369906,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-vv7dhxcel5yesltb4ctu,task_subcomment,NA
+VisualEditor: Delete contents of slugged paragraph results in double line break visible,Deeming that this is now fixed.,1371781383,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vv7dhxcel5yesltb4ctu,task_subcomment,NA
+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.",1371520995,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vv7dhxcel5yesltb4ctu,task_subcomment,NA
+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.",1371072856,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-vv7dhxcel5yesltb4ctu,task_subcomment,NA
+"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",1368250320,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_description,resolved
+"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.",1384457027,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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.,1368498108,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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!",1368390197,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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.",1368390088,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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?",1368379669,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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?",1368303523,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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",1368255099,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption",Confirmed in Safari and Chrome as well.,1368252786,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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",1368251518,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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",1368251303,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+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",1368089940,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-bxvvumd26q44ufzm7ua5,task_description,resolved
+VisualEditor: Aborted empty list creates a pawn,Merged into master; will be deployed from Monday.,1368206349,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+VisualEditor: Aborted empty list creates a pawn,"(In reply to comment #3)
+> Related URL: https://gerrit.wikimedia.org/r/63102 (Gerrit Change
+> If22d9b904b8861e24d56944d791545635b2e4254)
+
+Merged.",1368206273,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+VisualEditor: Aborted empty list creates a pawn,Related URL: https://gerrit.wikimedia.org/r/63102 (Gerrit Change If22d9b904b8861e24d56944d791545635b2e4254),1368148455,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+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 <li> (return at the end of the list) it doesn't check that the <ul> is empty, so you get a node inside the <ul>.
+
+Note that in casual testing this 'worked', because backspace deletes the pawn and <ul> together. Bother.",1368126833,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+VisualEditor: Aborted empty list creates a pawn,Same when entering text instead of Delete,1368090135,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
+Put the cursor somewhere in the text.
+Type ""Enter"" 2 times.
+Type ""Up"".
+Type ""Delete"".
+Click Bullet List
+Type q
+Type Left
+Type Enter
+Type Up
+Type Delete
+
+Wild pawn appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368089760,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-beabkw6yw7remnijbvdm,task_description,resolved
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"(In reply to comment #3)
+> James, do you mean the pawn does not appear for you?
+> I tried just now on wikipedia.org, the pawn appears.
+> Please note that the correct instructions are those in Comment 1.
+> 
+> Ubuntu 2012.10, Firefox 20.0
+
+I didn't say it doesn't appear in production, I said it doesn't appear in master; had I been unable to reproduce, I would have said. :-)
+
+I think this is fixed through changes made in master but not deployed, but bug 47795 appears to have broken itself; I'll close this and mark that as re-opened.",1368211364,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-beabkw6yw7remnijbvdm,task_subcomment,NA
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"James, do you mean the pawn does not appear for you?
+I tried just now on wikipedia.org, the pawn appears.
+Please note that the correct instructions are those in Comment 1.
+
+Ubuntu 2012.10, Firefox 20.0",1368153322,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-beabkw6yw7remnijbvdm,task_subcomment,NA
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"I can reproduce bug 47795 in master in Firefox, but not the pawn issue; all works in Chrome, as normal.",1368126046,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-beabkw6yw7remnijbvdm,task_subcomment,NA
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"Sorry, ignore the first Delete step above.
+
+Steps should read:
+
+Type ""Enter"" 2 times.
+Type ""Up"".
+Click Bullet List
+Type q
+Type Left
+Type Enter
+Type Up
+Type Delete",1368089888,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-beabkw6yw7remnijbvdm,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"1. Open http://en.wikipedia.org/wiki/Enterprise_content_management
+2. Add a space and remove it
+3. Press ""Review and Save""
+4. Wait forever.
+
+The text stays greyed out and nothing changes. Changes can't be saved.
+Same for any article I tried.
+
+Ubuntu 2012.10, Firefox 20.0
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1367893860,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-32fs65piddaapoc5z4hg,task_description,resolved
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"
+
+*** This bug has been marked as a duplicate of bug 48181 ***",1368023940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],Bug is gone indeed.,1368018208,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],Can't reproduce in Chrome or FF. I see other bugs (which I think have been filed elsewhere) but nothing that stops me from reviewing.,1368018032,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"Ed, marking this as immediate for when you wake.",1367895324,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],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,1367894800,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"Uncaught Error: toDomElements() failed to return an array when converting element of type alienBlock load.php:4092
+> ve.dm.Converter.getDomElementsFromDataElement load.php:4092
+> ve.dm.Converter.getDomSubtreeFromData load.php:4629
+> ve.dm.Converter.getDomFromData load.php:4444
+> ve.init.mw.ViewPageTarget.swapSaveDialog load.php:101
+> ve.init.mw.ViewPageTarget.showSaveDialog load.php:99
+> ve.init.mw.ViewPageTarget.onToolbarSaveButtonClick load.php:87
+> proxy load.php:10
+> ve.EventEmitter.emit load.php:11
+> ve.ui.ButtonWidget.onClick load.php:8696
+> proxy load.php:10
+> jQuery.event.dispatch load.php:45
+> elemData.handle.eventHandle",1367894666,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"(In reply to comment #0)
+> 1. Open http://en.wikipedia.org/wiki/Enterprise_content_management
+> 2. Add a space and remove it
+> 3. Press ""Review and Save""
+> 4. Wait forever.
+> 
+> The text stays greyed out and nothing changes. Changes can't be saved.
+> Same for any article I tried.
+> 
+> Ubuntu 2012.10, Firefox 20.0
+
+Confirmed on Firefox 20, Mac OS X.",1367894611,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],What does the console error log say?,1367893927,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: Indenting multiple list items now broken in Firefox,"Multiple list items don't indent properly.
+
+Steps to duplicate the bug:
+
+Write a couple of lines. Mark all the lines and click the ""list"" button - producing bullet-list. 
+
+If the indent button is clicked when the cursor is on a single list item, that item will be indented. However, if you mark a couple of list items and indent them at once, the indentation is jumbled: some of the items are indented and some double-indented (and the item above the selection seems to be indented as well)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367650560,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-cilebqon5xuldg2g3esr,task_description,resolved
+VisualEditor: Indenting multiple list items now broken in Firefox,"
+
+*** This bug has been marked as a duplicate of bug 48390 ***",1368465449,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cilebqon5xuldg2g3esr,task_subcomment,NA
+VisualEditor: Indenting multiple list items now broken in Firefox,"I am entirely not sure if I am in the right direction here, but I figured I'd share my intuition --
+
+I am thinking this is some bug with the definition of child-nodes vs same-level nodes, which results in indentation as if some of the nodes selected are parents.
+
+There was a change in ve.ce.BranchNode.js and ve.ce.ContentBranchNode.js regarding child nodes -- could this have caused it?
+
+
++ve.ce.BranchNode.prototype.onModelUpdate = function ( transaction ) {
++       this.emit( 'childUpdate', transaction );
+
+And there are a couple of other changes in the ve.ce.BranchNode.prototype.onSplice method. Perhaps something went wrong with the definition of what is a child and what is a same-level node, which then jumbles up the hierarchy of the list?
+
+(I do hope I am in the right direction here, I thought I'd share my thoughts)",1367694128,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-cilebqon5xuldg2g3esr,task_subcomment,NA
+VisualEditor: Indenting multiple list items now broken in Firefox,Broken in master for Firefox but not in wmf3 - presumably we changed something in the last week that did this?,1367692978,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cilebqon5xuldg2g3esr,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox","*that* was an amusing bug to find.
+
+Tested on mediawiki.org.
+
+Steps:
+
+1. Write text in an ordered list item
+2. Select some of the text
+3. Hit ""end""
+
+Expected:
+
+Cursor at end of line
+
+Actual:
+
+Cursor at end of line, text gone
+
+I would *suspect* this is an easy bug, unmark it if it's not.
+
+Found bug on Firefox 23 alpha 1
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367530560,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-kcoehi5bluofxq2bsd4i,task_description,resolved
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",*** Bug 48288 has been marked as a duplicate of this bug. ***,1369093388,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",https://gerrit.wikimedia.org/r/63223 (Gerrit Change I7a8d6c474ecca5af02b72b6453c900ed61acea58) | change APPROVED and MERGED [by jenkins-bot],1368221634,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",Related URL: https://gerrit.wikimedia.org/r/63223 (Gerrit Change I7a8d6c474ecca5af02b72b6453c900ed61acea58),1368219098,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",*** Bug 48039 has been marked as a duplicate of this bug. ***,1367600124,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",Whoops. :-),1367545406,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+VisualEditor: VE sometimes posting to the wrong API when serializing wikitext?,"See Parsoid bug 47998.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1367509980,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-5wvor46u2dd3dffehhqn,task_description,invalid
+VisualEditor: VE sometimes posting to the wrong API when serializing wikitext?,"As far as we can tell, this isn't reproducible in live, so I'm marking as INVALID; happy to re-open if we see this happen in the wild.",1368216302,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5wvor46u2dd3dffehhqn,task_subcomment,NA
+VisualEditor: VE sometimes posting to the wrong API when serializing wikitext?,"Argh, a mess - Roan, could you investigate?",1367510099,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5wvor46u2dd3dffehhqn,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,"Steps to reproduce problem:
+1. Edit https://www.mediawiki.org/wiki/Git/Commit_message_guidelines in VisualEditor
+2. Add some text
+3. ""Review and save""
+4. ""Something is wrong""
+5. ""Report problem""
+
+Expected behaviour:
+Make an http request somewhere and report back in the UI.
+
+Actual behaviour:
+No http request is made and UI is unresponsive.
+
+console:
+> Uncaught TypeError: Converting circular structure to JSON
+> at:
+> > mw.Target.prototype.reportProblem = function(message) {
+> > var ...., report = { title: .., oldid: .., .. };
+> > $.post(mw.config.get('wgVisualEditorConfig').reportProblemURL, {'data': JSON.stringify(report)}, function() {
+
+debug:
+
+var objs = [];
+JSON.stringify(a, function (k, v) {
+  var i;
+  if (v === Object(v)) {
+    i = objs.indexOf(v);
+    if (i !== -1) {
+      console.log('dupe at #' + i, v);
+    }
+    objs.push(v);
+  }
+  return v;
+});
+dupe at #66 
+<p data-parsoid=​""{""dsr"":​[0,139,0,0]​}​"">​
+""The ""
+<b data-parsoid=​""{""tsr"":​[4,7]​,""dsr"":​[4,24,3,3]​}​"">​commit message​</b>​
+"" play an important role in revision control systems. They are the first thing other people will see of your commit.""
+</p>​
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1367434260,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dt7csod4a2evm53mkmur,task_description,resolved
+VisualEditor: JSON.stringify won't work if data contains DOM elements,Fixed in master.,1368038305,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,"Ah, because native DOM element objects have all kinds of ""convenience"" pointers like ""firstChild"", ""children"", ""nextSibling"", ""paretNode"", ""ownerDocument"", which all have the same as well, so its like a circular reference nightmare.",1368030444,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,Related URL: https://gerrit.wikimedia.org/r/62811 (Gerrit Change Id807ccc6ff31d063be815ed4988cb35684adb76a),1368020696,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,This is caused by the linear data now contain DOM elements in alien nodes (and other nodes that store original HTML). We will need to pre-process the data before serialising. We already do this in the unit tests so shouldn't be too difficult.,1368019429,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,"@Ed: I suspect the circular reference is coming from inside the data model. Can you look into this?
+
+See ve.init.mw.Target.js, method #reportProblem.",1367860376,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,"Currently we don't alert users that they're outing their IP when they save. This is a Bad Thing(tm).
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1367266320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bkkyo5d2dquufftw2sz,task_description,resolved
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,I see - wan't looking at main namespace.,1367604012,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,Merged and will go out with wmf4.,1367602898,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,"(In reply to comment #4)
+> mediawiki.org? I don't see it there.
+
+Compare https://www.mediawiki.org/w/index.php?title=MediaWiki_1.21&action=edit with https://www.mediawiki.org/wiki/MediaWiki_1.21?veaction=edit in an isolated browser (e.g. Chrome Incognito).",1367599367,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,mediawiki.org? I don't see it there.,1367598917,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,"(In reply to comment #2)
+> Currently the extension doesn't let anon editors use it at all (
+> $skin->getUser()->getOption( 'visualeditor-enable' ) is required ), but I've
+> put in a fix for when we do.
+
+Except for mediawikiwiki, where it's forced on for everyone, logged in or out, regardless of preference. :-)",1367594947,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,"Currently the extension doesn't let anon editors use it at all ( $skin->getUser()->getOption( 'visualeditor-enable' ) is required ), but I've put in a fix for when we do.",1367577948,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,Related URL: https://gerrit.wikimedia.org/r/62143 (Gerrit Change Ib5c3284c646ebcc0a8cad0b02de559d7820e05a0),1367577674,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Editing lists results in PILE_OF_POO symbol ;),"1. Edit a page with an unordered list.
+
+2. Delete all the text on the last line.
+
+3. Press the <delete key>. The bullet should be erased.  Instead, it will
+remain and the cursor will move to the end of the previous line.
+
+4. down-arrow
+
+5. down-arrow off of the empty line.
+
+Turd appears in the empty line.
+
+Very many arrow-key actions will produce the turd.
+
+Firefox 20.0, linux.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367217060,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-dciqnjw7tyxyl2dkeuls,task_description,resolved
+VisualEditor: Editing lists results in PILE_OF_POO symbol ;),"Actually those are two separated issues. One is about turds appearing and the other one is about bullet not being erased. So in my previous comment I referred to the first issue, and second issue is something that I'm working on now (as a part of broader refactoring to handle deletion operations).",1367281537,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-dciqnjw7tyxyl2dkeuls,task_subcomment,NA
+VisualEditor: Editing lists results in PILE_OF_POO symbol ;),I believe that this is fixed in master: https://gerrit.wikimedia.org/r/#/c/61055/,1367281446,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-dciqnjw7tyxyl2dkeuls,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,"jQuery have WONTFIX'ed this bug (13821) so we'll have to work around.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+http://bugs.jquery.com/ticket/13821",1366992360,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_description,resolved
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,"(In reply to comment #5)
+> (In reply to comment #0)
+> > jQuery have WONTFIX'ed this bug (13821) so we'll have to work around.
+> 
+> Any link? http://bugs.jquery.com/report/13821 returns error.
+
+http://bugs.jquery.com/ticket/13821 (in the see also field).",1367595136,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,"Another place we had to work around:
+https://gerrit.wikimedia.org/r/#/c/62028/",1367577189,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,"(In reply to comment #0)
+> jQuery have WONTFIX'ed this bug (13821) so we'll have to work around.
+
+Any link? http://bugs.jquery.com/report/13821 returns error.",1367562927,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,*** Bug 47860 has been marked as a duplicate of this bug. ***,1367545048,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,Ed's code is merged and will be going out with the regular deployment train on Monday.,1367097148,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,Related URL: https://gerrit.wikimedia.org/r/61180 (Gerrit Change I3df8f49b170c31da9610129d53cf8cb65dd5d5f8),1367066588,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,*** Bug 47712 has been marked as a duplicate of this bug. ***,1366992520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: Saved annotated content cannot be unannotated,"This has reappeared (in live on hewiki and others) - if the page on load has bold annotation on some text, pressing the ""bold"" button doesn't remove bold but adds a second bold annotation (which can be removed, but not in a way that stops the text being bold).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366932000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b7yvvcuza7umneartpgv,task_description,resolved
+VisualEditor: Saved annotated content cannot be unannotated,Merged and deployed.,1366937647,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b7yvvcuza7umneartpgv,task_subcomment,NA
+VisualEditor: Saved annotated content cannot be unannotated,Roan fixing now.,1366934154,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b7yvvcuza7umneartpgv,task_subcomment,NA
+VisualEditor: Saved annotated content cannot be unannotated,Related URL: https://gerrit.wikimedia.org/r/60948 (Gerrit Change I77f00e63c8732420063b0453fede7f453083c913),1366934093,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b7yvvcuza7umneartpgv,task_subcomment,NA
+VisualEditor: Link inspector crashes when trying to annotate first character in the document,"Make a selection that includes the first character, and press the access key for creating a link (Ctrl+K?). You'll get a JS error.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366853220,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-67bjy5it2mluh5artfn6,task_description,resolved
+VisualEditor: Link inspector crashes when trying to annotate first character in the document,Mysteriously works upon updating to the current HEAD.,1367880698,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-67bjy5it2mluh5artfn6,task_subcomment,NA
+VisualEditor: Link inspector crashes when trying to annotate first character in the document,"I wanted to check this out, and I noticed that this fails (I reproduced the error) in Chrome and Firefox 20.x in Windows, but it works perfectly (no crash on first character) in my Firefox 20.x in Ubuntu.
+
+Also, if it helps, here's the error I'm getting on Firebug:
+
+Error: Error in Rangy Position module: Cannot get position for range [WrappedRange(<P>[4][<a href=""sdjfh"" titl]:0, <P>[4][<a href=""sdjfh"" titl]:0)]
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Crangy%7Cunicodejs.wordbreak&skin=vector&version=20130505T030747Z&*
+Line 224
+
+It seems it has something to do with the wordbreaks (??). Can there be a difference in wordbreaks that are used at the beginning of a document/paragraph between Linux and Windows? (Like ther'es a difference in endofline chars and whitespaces) ?
+
+Not sure if it helps, but here's for sharing.",1367812636,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-67bjy5it2mluh5artfn6,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,"As the title says. The bug seems to be in postHTML:
+
+array(
+        'postData' => array( 'content' => $html ),
+        'timeout' => $wgVisualEditorParsoidTimeout,
+        'oldid' => $parserParams['oldid']
+)
+
+
+should be:
+
+array(
+        'postData' => array( 'content' => $html, 
+                             'oldid' =>  $parserParams['oldid']),
+        'timeout' => $wgVisualEditorParsoidTimeout
+)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366408980,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-uw2enw4anj5qqfz3lyei,task_description,resolved
+VisualEditor: No oldid is sent on POST to Parsoid,*** Bug 47498 has been marked as a duplicate of this bug. ***,1366641916,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,Merged; to go out in next push as a critical priority.,1366641892,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,Related URL: https://gerrit.wikimedia.org/r/60082 (Gerrit Change Ib1b7079a7fd3357903e5a14795ed0d2f2bdc5d16),1366409690,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,Verified that this fixes the problem and lets Parsoid actually use selective serialization. Current production code does not use selective serialization for this reason.,1366409237,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,This would explain a great deal. :-),1366409214,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use","The link tool showing ""undefined"" in step 5 of the bug report
+
+1. Hit an article on English Wikipedia and click ""Edit"" to invoke Visual Editor. I used http://en.wikipedia.org/wiki/Savage%2C_Montana.
+
+2. Double-click any word to highlight it. I used the first word of the ""History"" section, ""Savage"".
+
+3. Click the Link Tool icon, and the tool pops up.
+
+4. Choose any article title in the dropdown (I chose ""Savage Land"") and press Enter.
+
+5. The dropdown closes, and in the tool's text input, instead of saying ""Savage Land,"" it says ""undefined."" (See screenshot to be uploaded.)
+
+6. Now click outside the tool -- somewhere else on the article. The tool becomes completely blank (see second screenshot) and article text disappears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F10425}",1366381800,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_description,resolved
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",Now fixed by gerrit 60907 - thanks Trevor!,1366919875,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",Seemingly not fixed at all - still broken in master/production with same behaviour as before.,1366918173,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",Now merged and going out tomorrow.,1366854691,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",Related URL: https://gerrit.wikimedia.org/r/60781 (Gerrit Change I286a28002c1691e58bbd7de04ed08cceb8b3bb07),1366852733,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",*** Bug 47546 has been marked as a duplicate of this bug. ***,1366741802,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use","Same for me.
+
+In addition to Dan's step 6, i note that after step 6 I see: ""TypeError: 'undefined' is not an object (evaluating 'dataElement.attributes.title')""",1366464797,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use","Confirmed in Chrome/Mac, Firefox/Mac and Firefox/Linux. Looks like a general critical issue.",1366387816,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",This is in Chrome 25.0.1364.172 on Ubuntu Linux.,1366381926,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use","Created attachment 12146
+The link tool going completely blank, and the article text behind it disappearing, as in step 6 of the bug report.
+
+**Attached**: {F10426}",1366381880,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+Master broken (jsduck),"Master is failing jenkins tests right now due to some JSDuck failures.
+
+Examples: https://gerrit.wikimedia.org/49364 , https://gerrit.wikimedia.org/r/57922
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: blocker",1365447240,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-exzifkfq2psfgq3kiwzv,task_description,resolved
+Master broken (jsduck),Original patch has been resubmitted by Roan with https://gerrit.wikimedia.org/r/#/c/58134/ . That new version passed the JSDuck job \O/,1365454559,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),"Changed merged by Jenkins, so that definitely fixed the issue :-]",1365449081,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),"(In reply to comment #3)
+> Maybe the V+2 and submit rights should be taken away from human users for
+> core?
+> We did this in VisualEditor a few months ago.
+
++10, best idea ever",1365448352,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),Maybe the V+2 and submit rights should be taken away from human users for core? We did this in VisualEditor a few months ago.,1365448120,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),"Most probably caused by https://gerrit.wikimedia.org/r/#/c/56637/ that has been force merged.
+
+Revert is https://gerrit.wikimedia.org/r/#/c/58131/",1365447919,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),Related URL: https://gerrit.wikimedia.org/r/58131 (Gerrit Change I2d945b7ffb7cfbcc5024a1c3bdcf0c9506b0cf76),1365447873,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+"VisualEditor: Switch integration for deployed wikis from tabLayout ""add"" to ""replace"" mode","In preparation for making the VisualEditor the ""default"" editor, we should have the existing integration switched over for users so that they can see, test and feedback on the final UX for triggering edits in the run-up to switch-over.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1365032940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gngjvjs5g5d7kc4osh37,task_description,resolved
+"VisualEditor: Switch integration for deployed wikis from tabLayout ""add"" to ""replace"" mode",Now merged.,1366320602,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gngjvjs5g5d7kc4osh37,task_subcomment,NA
+"VisualEditor: Switch integration for deployed wikis from tabLayout ""add"" to ""replace"" mode","See https://gerrit.wikimedia.org/r/59557 , https://gerrit.wikimedia.org/r/59558",1366156038,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gngjvjs5g5d7kc4osh37,task_subcomment,NA
+Jenkins merged a faulty change,"Aaron Schulz wrote:
+
+I noticed that https://gerrit.wikimedia.org/r/#/c/33971/ passed the tests but after it was merged, the new tests started failing for everything. The commit to revert it also failed so I override Jenkins and merged anyway, and the failures went away for new commits. This indicates that something broken is going, possibly Jenkins running tests just against master rather than master + the patch, which would explain this problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364653620,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_description,resolved
+Jenkins merged a faulty change,"Change 117045 merged by jenkins-bot:
+Parsoid: uses ZUUL_COMMIT as a git refspec to build
+
+https://gerrit.wikimedia.org/r/117045",1394446468,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Change 117045 had a related patch set uploaded by Hashar:
+Parsoid: uses ZUUL_COMMIT as a git refspec to build
+
+https://gerrit.wikimedia.org/r/117045",1394053460,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,I have verified the jobs triggered over the past few days. Seems to work fine now :-)  The root cause was using ZUUL_BRANCH as a branch specifier instead of ZUUL_COMMIT.,1366463506,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"hashar@gallium:~$ ./checkbug46723.py mediawiki-core-phpunit-api --filter 2013-04-16*
+Found 0 mismatches in 29 log files.
+hashar@gallium:~$ ./checkbug46723.py mediawiki-core-phpunit-misc --filter 2013-04-16*
+Found 0 mismatches in 29 log files.
+$
+
+Seems it got fixed :-]  Will verify again during the week, but so far that looks good.",1366117226,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,Will monitor over the next few days. Lowering priority for now.,1366023198,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"https://gerrit.wikimedia.org/r/#/c/58865/ has been deployed.
+
+I am now manually updating the jobs which are not under JJB:
+
+analytics-libanon
+analytics-udp-filters
+analytics-webstatscollector
+analytics-wikistats
+mwext-PoolCounter-pep8
+mwext-VisualEditor-docgen
+operations-debs-python-voluptuous-debbuild
+parsoid-parse-tool-check
+parsoid-roundtrip-test-check
+parsoid-runTests
+test-mediawiki-merge",1366022481,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,https://gerrit.wikimedia.org/r/58865 (Gerrit Change Iafebfffe480886fc8956e56517291b1b3b1fc0cc) | change APPROVED and MERGED [by Hashar],1366022447,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,*** Bug 47208 has been marked as a duplicate of this bug. ***,1365939442,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"(In reply to comment #13)
+> Related URL: https://gerrit.wikimedia.org/r/58865 (Gerrit Change
+> Iafebfffe480886fc8956e56517291b1b3b1fc0cc)
+
+Why is this comment duplicated?",1365759643,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"I have updated mediawiki-core-whitespaces job to use ZUUL_COMMIT as a refspec specifier. The job is non voting so that is not going to do any harm.
+
+The experimental change is https://gerrit.wikimedia.org/r/58865",1365759586,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,Related URL: https://gerrit.wikimedia.org/r/58865 (Gerrit Change Iafebfffe480886fc8956e56517291b1b3b1fc0cc),1365759515,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,Related URL: https://gerrit.wikimedia.org/r/58865 (Gerrit Change Iafebfffe480886fc8956e56517291b1b3b1fc0cc),1365759512,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"The branch specifier in the git plugin is set to ZUUL_BRANCH which is 'master'. 
+
+In the git plugin (at git-plugin/src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java ), the getCandidateRevisions() will recognize whether the branch looks like a sha1 (if it matches /[0-9a-f]{6,40}/) and in such a case will create a detached branch using that commit.
+
+Seems the Jenkins job macro should then use ZUUL_COMMIT as a branch specifier.",1365758998,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"ZUUL_COMMIT=76cb37f0c69dcd69884fc6e66681e77c8045a08e
+
+but it fetched origin/master instead :-(",1365717544,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Created attachment 12084
+Console output for https://integration.wikimedia.org/ci/job/mediawiki-core-phpunit-parser/5386/console
+
+**Attached**: {F10684}",1365717500,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,We are lacking the git plugin verbose mode in production due to a bug. It is corrected with https://gerrit.wikimedia.org/r/58489  . That will help find out what the plugin is doing internally.,1365595161,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"I have traced the issue as far as mediawiki-core-lint build #19 from made on November 22nd 2012).
+
+
+MISMATCH in /var/lib/jenkins/jobs/mediawiki-core-lint/builds/19/log
+Pipeline: gate
+Zuulcommit: 76606b66b006ac0e62087e6d00b1e4bdd56fff09
+Checkedout: 232e34733fc68739ba96cccc31d3ff88f9484a23",1365590692,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Extract for the two builds referenced somewhere above:
+
+Verifying /var/lib/jenkins/jobs/mediawiki-core-phpunit-misc/builds/5222/log
+Zuulcommit: 8cc0b601aa2db6db09ac0e4d70847293d75875aa
+Checkedout: 8cc0b601aa2db6db09ac0e4d70847293d75875aa
+Verifying /var/lib/jenkins/jobs/mediawiki-core-phpunit-misc/builds/5223/log
+Zuulcommit: 7dd3356a51951f8cdfe463552b5e5aae272e8e60
+Checkedout: 4c69569db71d149feff6c4b10ea7a493425d67fd (MISMATCH)
+
+
+We can see that build 5223 did not used the proper commit :-]
+
+
+I suspect git plugin does not fetch the proper references / can't find it. That result internally in an unknown sha1 and then git plugin fallback to master or something else.
+
+I will try to reproduce the issue in labs with git plugin set to verbose. That needs to start Jenkins with -Dhudson.plugins.git.GitSCM.verbose=true",1365542339,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Created attachment 12066
+output of checkbug46723.py
+
+The result script output highlight that some builds are not testing what they should be testing because they check out a parent commit.  By looking at the Jenkins Git plugin source code, it seems that whenever the reference is not parseable (aka: git rev-parse $ZUUL_REF), the plugin fallback to use master or some parent commit.
+
+I need to improve the script to find out if that happens in a specific pipeline or for some specific refs.
+
+**Attached**: {F10683}",1365541824,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Created attachment 12065
+python script parsing build logs to find Zuul commit vs Git plugin checkout
+
+**Attached**: {F10682}",1365541532,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"build #5223 
+
+
+Workspace did get wiped:
+ 02:46:53 Wiping out workspace first.
+
+It check out the revision:
+ 02:46:56 Checking out Revision 4c69569db71d149feff6c4b10ea7a493425d67fd (origin/master)
+
+That is the master revision NOT the change. The commit should have been
+7dd3356a51951f8cdfe463552b5e5aae272e8e60
+
+----
+
+The related merge job
+https://integration.wikimedia.org/ci/job/mediawiki-core-merge/11333/console
+
+02:44:17 Commencing build of Revision 7dd3356a51951f8cdfe463552b5e5aae272e8e60 (origin/master)
+02:44:17 Checking out Revision 7dd3356a51951f8cdfe463552b5e5aae272e8e60 (origin/master)
+
+----
+
+The ZUUL_REF has probably not been resolved properly and the git plugin fallback to master.
+
+There is also the possibility that the mediawiki-core-phpunit-misc job was using ZUUL_COMMIT as a refspec instead of ZUUL_REF. That might prevent the plugin from fetching the revision.   The job history is no more accessible due to an unexpected upgrade (see bug 47040).",1365514200,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"From bug 47031 : https://gerrit.wikimedia.org/r/#/c/57436/ has been merged although it is faulty.
+
+The unit tests ran on patchset upload did catch the issue:
+
+https://integration.wikimedia.org/ci/job/mediawiki-core-phpunit-misc/5222/console : FAILURE
+
+But the gating run after CR+2 did not catch it:
+
+https://integration.wikimedia.org/ci/job/mediawiki-core-phpunit-misc/5223/console : SUCCESS
+
+
+The root cause is that despite the ZUUL_REF points to the proper merge commit, the Jenkins Git plugin seems to use the current origin/master to build.",1365497215,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,Related URL: https://gerrit.wikimedia.org/r/58283 (Gerrit Change I4b3fadccaae9c35964a0c47d63b22c4f35148a24),1365495617,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+VisualEditor: Leaving a link while the inspector is open can remove the link,"0. Open a document with links already in it.
+1. Click on a MediaWiki link, then click the icon to open the inspector.
+2. Click anywhere else in the document to lose focus.
+3. You're link has now been removed :(
+
+Note that this doesn't happen if you have just created a link, or if you have edited a link, so I assume this is functionality for letting people abandon the creation of a link.
+
+The only way to remove a link should be with the delete icon in the inspector, or clear formatting.
+
+This doesn't appear to affect external links.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363095900,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rl3v4wnjsqhxlyzhy4r4,task_description,resolved
+VisualEditor: Leaving a link while the inspector is open can remove the link,*** Bug 46505 has been marked as a duplicate of this bug. ***,1364164432,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rl3v4wnjsqhxlyzhy4r4,task_subcomment,NA
+VisualEditor: Leaving a link while the inspector is open can remove the link,Code now merged.,1363139966,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rl3v4wnjsqhxlyzhy4r4,task_subcomment,NA
+VisualEditor: Leaving a link while the inspector is open can remove the link,https://gerrit.wikimedia.org/r/53488,1363132183,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-rl3v4wnjsqhxlyzhy4r4,task_subcomment,NA
+VisualEditor: Node API re-write,"The re-write of the node API that dm provide up to the rest of VE is necessary for most of the added support that VE is aiming to provide this year.
+
+[Mostly done now.]
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1360975080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oua6msncukecknrhwrdf,task_description,resolved
+VisualEditor: Node API re-write,… which is now merged. Hurrah.,1361576303,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oua6msncukecknrhwrdf,task_subcomment,NA
+VisualEditor: Node API re-write,Done in gerrit 50025 and related changes.,1361380955,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oua6msncukecknrhwrdf,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"**Author:** `phil`
+
+**Description:**
+visual editor after deleting lines 3 and 4 - note that 4 is still visible and the gap inbetween 2 and 4 is marked as 'cannot be edited'
+
+I had text
+1
+2
+3
+4
+
+selecting the last 2 lines ( 3 and 4 ) and deleting and saving, on looking at the page again '4' is visible and there is a gap that is marked as 'cannot be edited'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10499}",1360728000,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_description,resolved
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"Looks like this is similar to bug 44701. The linear model is correct, but is incorrectly serialized or parsed.",1419136405,PHID-USER-4yggyv53vecfrsed5djx,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),This is now fixed given the Parsoid update. Sorry for the delay.,1366396346,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"**orbit** wrote:
+
+Looks like this is similar to bug 44701. The linear model is correct, but is incorrectly serialized or parsed.",1361488266,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"**phil** wrote:
+
+Safari on Mac
+
+used the trackpad on my Mac to select the text
+
+Look at page
+http://en.wikipedia.org/wiki/User:PhilK10/sandbox/lines",1361484161,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"**orbit** wrote:
+
+What browser did this happen with? How did you make the selection (mouse vs. keyboard)? Can you link to the revision?",1361483818,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Parsoid selective serialisation issue when single LI made from P (?),"**Author:** `phil`
+
+**Description:**
+error message on save after changing bullet format
+
+Blank page
+Add some text e.g. 'test' and make it a numbered bullet
+Save the page
+Edit the page
+Remove the text 'test'
+Click on the '1' and click the numbered bullet control to remove it
+Save page
+""Error loading data from server: Unsuccessful request: Error contacting the Parsoid server.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10836}",1360092960,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ukt7mx53j5m7gaxam7vy,task_description,resolved
+VisualEditor: Parsoid selective serialisation issue when single LI made from P (?),This is now fixed given the Parsoid update. Sorry for the delay.,1366396184,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ukt7mx53j5m7gaxam7vy,task_subcomment,NA
+VisualEditor: Parsoid selective serialisation issue when single LI made from P (?),"Can reproduce (not as a Parsoid error, which is just a ""this is not working"", but as a null diff.)
+
+This is a Parsoid bug; holding back for new Parsoid release to live to re-check before assigning.",1360209793,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ukt7mx53j5m7gaxam7vy,task_subcomment,NA
+VisualEditor: Backspace creating a slug then deletes again,"Pressing backspace creating a slug then deletes again:
+
+* Create a new page (or go to an existing one), and enter ""AB\nCD\nEF""
+* Place the cursor down-page of ""F"" and press backspace; ""F"" is deleted correctly.
+* Then press backspace again; ""E"" is deleted, as is the remaining slug, and the cursor moves us.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1354563540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jye77ivrdahrtvdtxmyb,task_description,resolved
+VisualEditor: Backspace creating a slug then deletes again,Fixed here: https://gerrit.wikimedia.org/r/#/c/37162/,1354754116,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-jye77ivrdahrtvdtxmyb,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog","
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1354562580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v466mnsvk3gmqhazwrti,task_description,resolved
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog",Merged into master.,1355176624,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog",Change-Id: I9d05ef6e3e2461bdcf363232f7b0fbad5e24f506,1354930076,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog",Now in gerrit as gerrit 37601.,1354929606,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog","Ic34fae7a8dbfc2a91ab36ba77613e17a91f29f6f is going to resolve this, when it's done.",1354921857,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog","The VisualEditor should have a ""show changes"" button in the save dialog, taking the user to a wikitext diff in a hover over the editor surface; backend is now written but the front-end is still needed.",1354562716,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+VisualEditor: Paragraph changed to be a heading using the drop-down has its content deleted,"A paragraph when changed to be a heading using the toolbar drop-down has its content deleted (but the presence still stays).
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1354218900,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wh5lwbsbwcapw3b5fkjp,task_description,resolved
+VisualEditor: Paragraph changed to be a heading using the drop-down has its content deleted,"This was resolved in I994b8c43123c3cd02b9a550d5d7eac7d5052418e
+
+This bug was introduced in I4600e984b287c6ff9267f4281d2f09bab9e1ad95 because ve.ce.ContentBranchNode's onUpdate method was being overwritten by ve.ce.HeadingNode.",1354225226,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-wh5lwbsbwcapw3b5fkjp,task_subcomment,NA
+VisualEditor: Backwards selection fails over inline alien nodes,"Start with an article with an inline alien - e.g. ""ABC<tt>:-)</tt>DEF"". Place cursor ""up page"" (in LTR, left) of inline alien; selection with keyboard down-page works as expected. Now place the cursor ""down page"" (in LTR, right) of the inline alien; selection with keyboard up-page fails when reaching the alien, clearing the selection and placing the cursor immediately up-page of the alien.
+
+Note that in RTL this appears to work fine(!).
+
+Confirmed in both Chrome and Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353718440,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6tkrmk42gm6l4ttp56da,task_description,resolved
+VisualEditor: Backwards selection fails over inline alien nodes,"This was resolved in Iba55cfc3d531e7d1333b78c94912ff22179aace8
+
+The issue was that the cursor ""fix-up"" code was not preserving non-zero-length selections.",1354066309,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-6tkrmk42gm6l4ttp56da,task_subcomment,NA
+VisualEditor: Pass reference to data element to DM node constructor,"Post-December cleanup:
+
+Rather than passing the type, length, attributes and (soon) annotations into the dm.Node constructors separately, we should just pass a reference to the data element. This will make a lot of things cleaner, and make the constructors more consistent between node types.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353704640,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7hihps7ry67el6iq5omz,task_description,resolved
+VisualEditor: Pass reference to data element to DM node constructor,https://gerrit.wikimedia.org/r/#/c/34956/,1354054120,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7hihps7ry67el6iq5omz,task_subcomment,NA
+VisualEditor: Link inspector should edit existing annotation rather than creating new one,"When editing an existing link, the link inspector should grab the existing annotation and edit it, rather than starting over with a brand new annotation.
+
+Destroying the existing annotation loses metadata we need for preserving syntactical variation (hrefPrefix and origTitle), which means that currently, simply inspecting a link without actually changing its target can cause that link to be changed in the wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353380340,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vfbpfzavk4xiw4bzbauh,task_description,declined
+VisualEditor: Link inspector should edit existing annotation rather than creating new one,"Roan and I agree that as long as the annotation isn't re-applied (and meta data stripped) unless we actually changed the target, this behavior is OK.
+
+The concept is, if you touch something with the editor we have the right to normalize that bit.",1353971898,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-vfbpfzavk4xiw4bzbauh,task_subcomment,NA
+VisualEditor: Link inspector should edit existing annotation rather than creating new one,"What happens when the annotation type changes from internal to external? We have to create a new object at some point.
+
+What about when someone removes an annotation, then adds it back in? Do we then have a diff?
+
+I'm suspicious about this being the only way we cleanly round-trip.",1353957557,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-vfbpfzavk4xiw4bzbauh,task_subcomment,NA
+VisualEditor: First character in empty document behaves strangely in Firefox,"Steps to reproduce:
+1. Go to a nonexistent page
+2. Click the Create tab
+3. Type ""foobar""
+
+Result: ""f"" appears on a line by itself, ""oobar"" appears on the next line. The document model only contains ""oobar"". The ""f"" jumps around when rerendering (e.g. when you press enter).
+
+Can NOT be reproduced if:
+* you use Chrome
+* you click out of the editor and back into it before typing
+* you press Ctrl+A, Backspace before typing text
+
+The editor document looks like this:
+
+<div contentEditable=""true""><p><span class=""slug""></span></p></div>
+
+I think the cause of this bug is that Firefox initially puts the cursor before the <p>, rather than inside the <p> or inside the <span>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353377280,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-euqyxfrrhmfrgg76hheq,task_description,resolved
+VisualEditor: First character in empty document behaves strangely in Firefox,https://gerrit.wikimedia.org/r/#/c/34681/,1353545923,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-euqyxfrrhmfrgg76hheq,task_subcomment,NA
+VisualEditor: Add tab layout that adds a ve-tab instead of replacing the default,"Taken from bug 42117 which I'm de-prioritising
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1353122700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ffv55y77ier7bslrsyco,task_description,resolved
+VisualEditor: Add tab layout that adds a ve-tab instead of replacing the default,Change-Id: I3fe29c52b743837c2e1d66f25ccdca6115b8bd25,1354126331,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ffv55y77ier7bslrsyco,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1353021960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_description,resolved
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"Max,
+
+The reason for knowing which edits come from which source is so where the bugs are likely to be (and has the bonus of being possible to do statistical analysis).
+
+Longer-term, as we make editing through the API easier, we'd like to move every user of the API to be labelled as the source (this is the approach taken by Twitter, for example). And of course, for the edit box to go through the API too, though that's more for sanity and security model than for tracking down bugs given how stable that code is.
+
+It's entirely possible that Tags aren't the best venue for this data, but it's what we have for now, and we can move to a better one later.",1353704947,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"The use-case for adding this functionality/feature is still unclear to me. In theory, there should be no distinction between VisualEditor edits and edits made via the standard (the classic?) textarea editor.",1353704521,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,https://gerrit.wikimedia.org/r/34686,1353551242,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"(In reply to comment #1)
+> I guess for the testing phase it won't be too bad, but as Terry points out on
+> wikitech-l, the tagging system hasn't gotten much love since it was
+> implemented, so it may not scale well (fire hose and all...).
+>
+I think we'll be fine for a while. According to https://en.wikipedia.org/wiki/Special:Tags , the most-used tag (references removed) has been used over half a million times. There are five tags used >100k times, and they add up to about 1.8 million. Overall the number of tagged revisions on enwiki is probably about 2 million.
+
+Based on a quick toolserver query, the number of edits by logged-in users in the main namespace in the hour between 18:15 UTC and 19:15 UTC today (Nov 21) was about 4,500. Even if all those edits used VE, it would take 18 days for VE-tagged edits to reach 2 million at that pace. That's kind of fast, but it's slow enough that we'll have time to respond. I made change tagging configurable and turned it on by default. If it causes problems, we can turn it off.",1353551175,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"(In reply to comment 0)
+> Edits should add a VisualEditor tag (using MediaWiki's revision tagging
+> system) so they can be identified
+
+What's the use-case?
+
+I guess for the testing phase it won't be too bad, but as Terry points out on wikitech-l, the tagging system hasn't gotten much love since it was implemented, so it may not scale well (fire hose and all...).
+
+(Please don't file bugs with empty descriptions [comment 0]. Summaries often change and it makes replies with quoting more difficult.)",1353115901,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Meta-fy comments,"Comments should be stored in the meta-linmod, right now they're just ignored, which leads to all comments being removed when we save a page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352940240,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6whfmphns7qcm6tbt5j3,task_description,resolved
+VisualEditor: Meta-fy comments,"Ahm, I meant https://gerrit.wikimedia.org/r/34257 of course :S",1353384366,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6whfmphns7qcm6tbt5j3,task_subcomment,NA
+VisualEditor: Meta-fy comments,https://gerrit.wikimedia.org/r/3425,1353384355,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6whfmphns7qcm6tbt5j3,task_subcomment,NA
+VisualEditor: Add handling for mw:Entity,"Currently these are being alienated, which is bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352938560,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-d53w6sbodbcpx4rkzth3,task_description,resolved
+VisualEditor: Add handling for mw:Entity,Fixed with https://gerrit.wikimedia.org/r/#/c/34444/ and https://gerrit.wikimedia.org/r/#/c/34575/,1353528384,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-d53w6sbodbcpx4rkzth3,task_subcomment,NA
+VisualEditor: Remove feedback link for deployment,"Remove the MW feedback link for December deployment; it's not helpful given the different paradigm for users in this content.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1351911840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yvetu3dh7pwz6hn5x7ii,task_description,resolved
+VisualEditor: Remove feedback link for deployment,Fixed in https://gerrit.wikimedia.org/r/#/c/33500/,1352941206,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yvetu3dh7pwz6hn5x7ii,task_subcomment,NA
+VisualEditor: Support most common citation templates (special-case),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345761780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ldu3pqks4ww5ptxdm5nq,task_description,invalid
+VisualEditor: Support most common citation templates (special-case),We've decided to take a different tack which means this kind of special-casing won't be needed. Hopefully. :-) Consequently marking as invalid.,1364928248,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ldu3pqks4ww5ptxdm5nq,task_subcomment,NA
+VisualEditor: Support most common citation templates (special-case),Is this going to work also for languages other than English (e.g. Portuguese)?,1357400999,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ldu3pqks4ww5ptxdm5nq,task_subcomment,NA
+VisualEditor: Support references,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345761720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zzor3of7nndkvfeeo4kt,task_description,declined
+VisualEditor: Support references,That issue is tracked as T52896.,1422564475,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,That's covered in specific tasks. Please don't open dead tasks from two years ago with drive-by comments; it's unhelpful and doesn't get anything done except wasting time diverting the conversation from the actual tasks.,1422562386,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,"I'm not clear as to why this is shown as ""Closed, Resolved"". VE still won't edit citations/footnotes where the body of the citation is in the References section (that is, within the reflist template), as demonstrated by the first two citations here: http://en.wikipedia.org/wiki/Pope_Francis#Name
+
+If this is a WONT FIX, it would be helpful to so state. And if so, I'll just note that decisions not to (ever) have VE be able to handle existing, widespread Wikipedia functionality, even where that is an ""ugly hack"", are one of the exact reasons that cause experienced editors to not want to use the VisualEditor.",1422426915,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,Fixed in master and very soon in production.,1371968442,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,Related URL: https://gerrit.wikimedia.org/r/70031 (Gerrit Change I1551ddaa3d52c4827c7dcac2a02e31859769890a),1371958250,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,"(In reply to comment #1)
+> VisualEditor must be able to handle grouped footnotes ( as discussed here:
+> http://en.wikipedia.org/wiki/Help:Footnotes#Grouping_footnotes ) - at least,
+> not breaking these.
+
+I agree. In fact, you and I have discussed this several times, and each time I've told you that we're working on it, and that we won't go ""live"" for the beta without it. :-)
+
+> It also must be able to handle articles where the text
+> for
+> footnote is placed in the References section rather than in the body of the
+> article - see, for example,
+> http://en.wikipedia.org/wiki/Pope_Francis#References .
+
+Ugly hacks for wikitext like this are one of the exact reasons that cause us to want everyone to use the VisualEditor.",1367959088,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,"VisualEditor must be able to handle grouped footnotes ( as discussed here: http://en.wikipedia.org/wiki/Help:Footnotes#Grouping_footnotes ) - at least, not breaking these. It also must be able to handle articles where the text for footnote is placed in the References section rather than in the body of the article - see, for example, http://en.wikipedia.org/wiki/Pope_Francis#References .",1367958327,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Link types need to be used by the UI so that the link inspector doesn't fail completely. :-),"As DM now has been adopted to the new RDFa link types, the UI needs to be adapted to them. Right now, all link inspectors fail utterly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1344375240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bnfj7ezq3zkwfxcrblkm,task_description,resolved
+VisualEditor: Link types need to be used by the UI so that the link inspector doesn't fail completely. :-),"Patched in https://gerrit.wikimedia.org/r/#/c/18048/ 
+Roan advised he will attempt a deploy of this today.",1344376085,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-bnfj7ezq3zkwfxcrblkm,task_subcomment,NA
+VisualEditor: New annotation API (tracking),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1343672040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4xi6ukfplmi5m5nx7n2s,task_description,resolved
+VisualEditor: License text should not be hard-coded,"The save dialog mentions but does not link to CC-BY-SA license, Project:Copyright page. These should be linked so you can get to them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1340905500,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-gmkobaxn2aw3klv7tvlc,task_description,resolved
+VisualEditor: License text should not be hard-coded,Change-Id: I84fee641162cdeed290092e56fb0e1d2562d833d,1354771701,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-gmkobaxn2aw3klv7tvlc,task_subcomment,NA
+VisualEditor: License text should not be hard-coded,In modules/ve/init/targets/ve.init.ViewPageTarget.js,1340926855,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gmkobaxn2aw3klv7tvlc,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature","IE11 on Windows 7 
+See the two screenshots to compare - VE in betalabs and in test2. 
+Production VE looks like test2 VE.{F24999}
+
+{F25001}",1419370204,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-lv7kzqodvetkfp53usel,task_description,invalid
+"VisualEditor incompatible with ""Fixed header"" beta feature",">>! In T85247#947266, @Se4598 wrote:
+> reopening: what's invalid here? (tasktitle had been changed to reflect incompatibility)
+
+(Now abandoned) Tools not designed to work with VE don't work with VE.",1441739949,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature",Thought that  since it's by design - not an issue/bug. ,1419873108,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature",reopening: what's invalid here? (tasktitle had been changed to reflect incompatibility),1419872711,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature","Yes, unchecking 'Fixed header'  makes VE be back to normal. Should be there some warning to VE users?",1419870543,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature",another report: https://www.mediawiki.org/wiki/Topic:S4opda1x12kcc54w,1419553818,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature","Looks okay to me. You have the ""Fixed header"" [[ http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences#mw-prefsection-betafeatures | beta feature ]] enabled, I guess VE isn't compatible with it. (You also have ""Compact personal bar"", but that isn't problematic AFAIK.)",1419523897,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature","Actually, I see VE is broken in Chrome too - so the issue is not specific to IE. ",1419374069,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+Create right-click menus for VisualEditor,"When I do Wikipedia editing workshops with VisualEditor, participants repeatedly suggest adding a right-click context menu.
+
+Something like that exists in Google Docs, and it's surprisingly useful. For MediaWiki It can include similar functions - formatting, styling, linking, commenting, suggesting edits, etc.",1419081869,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-zf3equ3kmfihdlt4bfvt,task_description,declined
+Create right-click menus for VisualEditor,"We have intentionally designed VisualEditor to not use right menus because they can't ever work on touch devices, because of user complexity, and because of their lack of find-ability. Even if these would start out purely as secondary UX controls, it would lead us down the road to Word's bloat.",1420842469,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zf3equ3kmfihdlt4bfvt,task_subcomment,NA
+ VisualEditor JavaScript and tests should only be added if VisualEditor is installed,"According to Antoine when he runs the tests using the following extensions together:
+
+- JsonConfig
+- Mantle
+- MobileApp
+- MobileFrontend
+- WikiGrok
+- ZeroBanner
+- ZeroPortal
+
+This yields two failures:
+
+ResourcesTest::testMissingDependencies
+The module 'ext.visualEditor.mobileViewTarget' required by
+'mobile.editor.ve' must exist
+Failed asserting that an array contains 'ext.visualEditor.mobileViewTarget'.
+
+ResourcesTest::testUnsatisfiableDependencies
+Undefined index: ext.visualEditor.mobileViewTarget
+
+
+",1419008593,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-v7rf6nwt2u72ghyq4kad,task_description,resolved
+ VisualEditor JavaScript and tests should only be added if VisualEditor is installed,"Change 181403 merged by jenkins-bot:
+Don't add VisualEditor related modules if VE isn't installed
+
+[[https://gerrit.wikimedia.org/r/181403]]",1419447395,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7rf6nwt2u72ghyq4kad,task_subcomment,NA
+ VisualEditor JavaScript and tests should only be added if VisualEditor is installed,"Change 181403 had a related patch set uploaded (by Florianschmidtwelzow):
+Don't add VisualEditor related modules if VE isn't installed
+
+[[https://gerrit.wikimedia.org/r/181403]]
+
+#patch-for-review",1419257192,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7rf6nwt2u72ghyq4kad,task_subcomment,NA
+Familiarize yourself with edit-reportcard.wmflabs.org,"https://edit-reportcard.wmflabs.org is a very rough beginning in the analysis of data related to the use of VisualEditor in the main wikipedias. The VisualEditor team needs help improving this space, so it provides metrics that help the team understand problematic areas, trends, impact of new features...
+
+At this point there is basically no documentation. T84926 and T84927 are very basic starts. Can you dig in these metrics and the raw data associated, and understand what is being shown there?
+
+Also, these graphs are created using [[ https://www.mediawiki.org/wiki/Analytics/Limn | Limn ]]. Have a look at the documentation in order to understand how it works. Bonus point if you install it locally and play with it a bit. 
+
+If you have any questions about Limn you can ask in the [[ https://lists.wikimedia.org/mailman/listinfo/analytics | analytics mailing list ]]. In any case, considering your background it is a good idea to subscribe to this list.",1418947018,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-sj4lh4ptvu2lzgg743rk,task_description,resolved
+Familiarize yourself with edit-reportcard.wmflabs.org,https://wikitech.wikimedia.org/wiki/Analytics/Dashboards is the documentation specifically about dasboards.,1418955612,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sj4lh4ptvu2lzgg743rk,task_subcomment,NA
+Familiarize yourself with edit-reportcard.wmflabs.org,"Great, I'm on it.",1418955520,PHID-USER-d3457iccsv4uq5ki2zkw,PHID-TASK-sj4lh4ptvu2lzgg743rk,task_subcomment,NA
+Special:MyLanguage should have a way to redirect to the fallback language if there is no translation,"If, for example, we want to give a link from VisualEditor in the Afrikaans Wikipedia to the VE user guide in mediawiki.org, we can only link to the source page in English. It would be more convenient to link directly to Afrikaans, but Special:MyLanguage only works if the user defined the language in the preferences of the same wiki, and [[VisualEditor/User guide//af]] will appear like a non-existent page if there is no translation.
+
+I can think of several options to fix this:
+* Make a non-existent sub-page redirect to the fallback language.
+* Make Special:MyLanguage work across wikis somehow.
+* Global cross-wiki language options (this would be Very Useful for a lot of other things).
+
+",1418930787,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-bifywkolpcqrbipm7zgp,task_description,duplicate
+Special:MyLanguage should have a way to redirect to the fallback language if there is no translation,@amire80 Do you have more information that can be used by Nemo and Niklas for this?,1433410170,PHID-USER-ttw4tpoosxc4pbmskrla,PHID-TASK-bifywkolpcqrbipm7zgp,task_subcomment,NA
+Special:MyLanguage should have a way to redirect to the fallback language if there is no translation,"> Make Special:MyLanguage work across wikis somehow.
+
+Do you mean, redirecting the user to another wiki?",1422318533,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-bifywkolpcqrbipm7zgp,task_subcomment,NA
+Special:MyLanguage should have a way to redirect to the fallback language if there is no translation,"This bug is vague. You can already link to [[mw:Special:MyLanguage/Page/af]] with the following caveats:
+* Set interface language in target wiki (if available) overrides the subpage request
+* It falls back directly to English.
+
+I think there is a task for the fallback thing already.",1422298572,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-bifywkolpcqrbipm7zgp,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"The undo link in the page history leads to the source editor and not VisualEditor. It should lead to the VisualEditor for people who prefer to use it.
+
+It's probably not a high priority at this point, but if the VisualEditor is supposed to replace the source editor, this issue should be handled at some point.",1418657683,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-mt3dwshqj2hvmp73flaa,task_description,open
+The undo link in the page history leads to the source editor and not VisualEditor,"I came across this issue while working on {T185548}, which in turn led me to {T185542}.
+
+I rebased the patch on `master` and overall it works (nice work!), but there are a few small issues:
+
+1. Undo notifications are still broken per T185548 because `undidRevId` isn't set when updating via the API (it's currently only set in `WikiPage.php`'s `doEditContent()`. This should be pretty easy to fix and I could push a commit to this patchset if you'd like.
+1. The edit summary is no longer working. As noted in {T185542} (item 5 in the task description), the edit summary used to correctly autopopulate with VE but it doesn't with this patch.
+1. When going to ""View history"" and then clicking on ""Undo"", I'd often be prompted by VE that ""This page was edited since you last loaded it."" VE then prompts to resume editing or start a new edit. If you click ""Resume editing"" the diff review won't show, but if you click ""start a new edit"", it will.
+1. Something is not quite right with auto-save functionality (line 518 of `ArticleTarget.js`). If you don't comment out `surfaceModel.restoreChanges();`, then VE informs you ""Changes recovered"" and you don't see the diff window.
+
+All of these seem pretty minor. I may have some time to work on them this week so I can move forward on resolving T185548, just let me know.",1529530774,PHID-USER-jzbjfcs2csloltie4voe,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"@Esanders: Yes, the priority should be higher. @Esanders, @AlexMonk-WMF (@Krenair): What is the status of this? How far is the patch to merge?",1520540365,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"Change 323357 restored by Esanders:
+[WIP] Undo support
+
+[[https://gerrit.wikimedia.org/r/323357]]",1483754459,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"Change 323357 abandoned by Alex Monk:
+[WIP] Undo support
+
+[[https://gerrit.wikimedia.org/r/323357]]",1483652990,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,This is higher priority with the new source mode.,1483226320,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"Change 323357 had a related patch set uploaded (by Alex Monk):
+[WIP] Undo support
+
+[[https://gerrit.wikimedia.org/r/323357]]
+",1479959213,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"I just hit this problem in my pet project, which has SET with VE enabled by default to everyone. Indeed, this problem is more annoying in this context because then editors who preferred VE or who didn't even use the wikitext editor are left with two problems after clicking Undo:
+
+# They are now facing a wikitext UI.
+# Their preference has now changed to wikitext, which means that all future edits will be presented on wikitext unless they find out how to bring VE back.",1474267745,PHID-USER-h6xz2shsbvhdtx5puurj,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"I just hit this problem in my pet project, which has SET with VE enabled by default to everyone. Indeed, this problem is more annoying in this context because then editors who preferred VE or who didn't even use the wikitext editor are left with two problems after clicking Undo:
+
+# They are now facing a wikitext UI.
+# Their preference has now chanded to wikitext, which means that all future edits will be presented on wikitext unless they find out how to bring VE back.",1474267609,PHID-USER-h6xz2shsbvhdtx5puurj,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"I just hit this problem in my pet project, which has SET with VE enabled by default to everyone. Indeed, this problem is more annoying in this context because then editors who preferred VE or who didn't even use the wikitext editor are left with two problems after clicking Undo:
+
+# They are now facing a wikitext UI.
+# Their preference has now chanced to wikitext, which means that all future edits will be presented on wikitext unless they find out how to bring VE back.",1474267416,PHID-USER-h6xz2shsbvhdtx5puurj,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,For some reasons I thought this was already fixed? It's particularly annoying/confusing on SET wikis.,1463397158,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"> the VisualEditor is supposed to replace the source editor
+
+Thunders and lightnings!",1451456248,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"When you press an undo button, not only do we set the revision text to the previous revision, but we also set up the standard revert summary as the default summary, and show the diff they're about to cause, and show a warning. I'm wondering what a similar experience in VE would look like.",1451449874,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"Suggest that specifically the undo link should lead to the editing interface selected in the user preferences or, in the absence of preference, to the default editor.  ",1423015674,PHID-USER-yif6nz5uhka5cnltixpc,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+"[gdash] ""VisualEditor: Latency"" graphs look dead",https://gdash.wikimedia.org/dashboards/ve/ seems to be missing data since the end of November.,1418651695,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-gfulce44jv65rvyd7kt2,task_description,duplicate
+<templatedata> cannot be used as Template Data,"I installed VisualEditor on MediaWiki 1.24.0. It works well now, I can edit and save pages.
+
+But when I tried to add Template Data to my old template page, it cannot be formate as a table. VisualEidtor cannot use template data when editing pages.
+
+My template data:
+
+```
+<templatedata>
+{
+    ""description"": ""插入注意文本框，突出显示注意内容"",
+    ""params"": {
+        ""1"": {
+            ""label"": ""注意内容"",
+            ""description"": ""注意文本框的内容"",
+            ""required"": true,
+            ""type"": ""string"",
+            ""aliases"": [ ""注意内容"" ]
+        }
+    }
+}
+</templatedata>
+```
+
+Template page: http://xuexiii.org/w/%E6%A8%A1%E6%9D%BF:%E6%B3%A8%E6%84%8F
+
+You can see template data is displayed as plain text. But in English Wikipedia, it should become a table.",1418381694,PHID-USER-g2bnzp2j6voh3sihftsl,PHID-TASK-hys6f6g7uxyhvocshtwi,task_description,resolved
+<templatedata> cannot be used as Template Data,,1439832857,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hys6f6g7uxyhvocshtwi,task_subcomment,NA
+<templatedata> cannot be used as Template Data,,1418406238,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hys6f6g7uxyhvocshtwi,task_subcomment,NA
+<templatedata> cannot be used as Template Data,@Jdforrester-WMF Thanks!,1418402337,PHID-USER-g2bnzp2j6voh3sihftsl,PHID-TASK-hys6f6g7uxyhvocshtwi,task_subcomment,NA
+<templatedata> cannot be used as Template Data,http://xuexiii.org/w/%E7%89%B9%E6%AE%8A:%E7%89%88%E6%9C%AC shows that you don't have the #TemplateData extension installed. If you install that (and then make an edit to any templates with TemplateData blocks on them so they can be re-parsed) it should work.,1418401710,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hys6f6g7uxyhvocshtwi,task_subcomment,NA
+Feedback link in VisualEditor needs to play nicely with LiquidThreads,"Steps to reproduce:
+
+1.  Open VisualEditor on MediaWiki.org.
+2.  Click on ""Leave feedback"" in the help menu.
+3.  Choose to leave feedback onwiki.  Type something and submit your feedback.
+
+Result:
+
+The feedback is posted as a ==Regular section heading== with normal, signed ~~~~ comments to a feedback page that is using LiquidThreads.  It either needs to post correctly within LiquidThreads or it needs to post to a different page.",1418189771,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-q4c2ad3gdnidfwio3wwp,task_description,duplicate
+Feedback link in VisualEditor needs to play nicely with LiquidThreads,">>! In T78120#836065, @TTO wrote:
+> I don't think it is fair to merge this. Realistically, that LQT task is never going to get resolved. VE needs to either work around this, or stop using a LQT-based feedback page (which is a WMF config issue).
+
+I disagree; the standard feedback form provided by Platform is what all feature teams are meant to use. The problem that it's particularly poor and needs fixing in various ways is something the Editing team have been (slowly) helping to improve. However, there are wider issues that are beyond our team and need specialists to fix. When all the LQT pages get converted to Flow, of course, the issue becomes the parallel {T59989}.",1418233399,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q4c2ad3gdnidfwio3wwp,task_subcomment,NA
+Feedback link in VisualEditor needs to play nicely with LiquidThreads,"I don't think it is fair to merge this. Realistically, that LQT task is never going to get resolved. VE needs to either work around this, or stop using a LQT-based feedback page (which is a WMF config issue).",1418200649,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-q4c2ad3gdnidfwio3wwp,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,Can we create consistency between the naming convention of the (sub)projects related to Visual Editor and Wikitext editor to make them more easily findable and have better parity?,1418160470,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-hy7qluemr2knghxwplss,task_description,declined
+Rationalize the project names of VE and wikitext editor,We're not going to merge all the 20+ editing-related projects together.,1418165494,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,Umbrella projects having a distinct color seems sane.  Upstream seems to do this I think.,1418165382,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"> the wikitext editor in Flow, which is dealt with inside MediaWiki-extensions-Flow
+> the VisualEditor issues specific to the Flow integration, which are, well, not currently filed anywhere, but I guess would go in VisualEditor and MediaWiki-extensions-Flow together.
+
+The VE integration is not actively being worked on, though we still want to use it later, of course.
+
+We basically use the standard scheme (MediaWiki-extensions-ExtensionName).  We also have a team board ( #Collaboration-Team ), but if you file it in the extension component you don't need to worry about the team board (we may add that project later, though).
+
+Are there any action items for #Collaboration-Team ?  If not, we'll remove our projects from this task.",1418165300,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"There's also:
+* **Mobile Web**
+** the wikitext editor in Mobile Web, which is dealt with inside #MobileFrontend-General-or-Unknown (no specific project for editor issues)
+** VisualEditor issues specific to the Mobile Web integration, which are dealt with in #VisualEditor-MediaWiki-Mobile
+* **Apps**
+** the wikitext editor in the iOS mobile app, which is dealt with in #Wikipedia-App-iOS-App (but not really, because they haven't migrated to Phabricator yet)
+** the wikitext editor in the Android mobile app, which is dealt with in #Wikipedia-App-Android-App (but not really, again)
+* **Flow**
+** the wikitext editor in Flow, which is dealt with inside #MediaWiki-extensions-Flow
+** the VisualEditor issues specific to the Flow integration, which are, well, not currently filed anywhere, but I guess would go in #VisualEditor and #MediaWiki-extensions-Flow together.
+* the wikitext editor in **LiquidThreads**, which is dealt with inside #MediaWiki-extensions-LiquidThreads
+* the **code editor**, which is dealt with in #MediaWiki-extensions-CodeEditor
+
+… and probably some others I'm forgetting. 
+",1418162160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"No, not really. Core's wikitext editing must stay under MediaWiki- and VisualEditor (and WikiEditor) must be separate.",1418162003,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"thanks for clarifying @matamarex, you kind of hit on what I'm saying. Is there any way we can make the phab project names for these more clearly show those relationships you just outlined?",1418161813,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"We have three distinct editors and three corresponding projects.
+
+* The **VisualEditor** is #VisualEditor, this is an umbrella project that includes all tasks from all of the subprojects like #VisualEditor-EditingTools. You should never file tasks in subprojects only or they may get lost (until we have project inheritance or whatever in Phabricator).
+* The **WikiEditor extension**, which is #MediaWiki-Extensions-WikiEditor. This is what most people know as //the// wikitext editor and implements all of the fancy buttons around the wikitext editing area.
+* The **built-in** MediaWiki editor, which you never see unless you're the kind of person who still uses MonoBook and hates new things. It doesn't have a dedicated project, but any issues can be filed under #MediaWiki-Page-editing (this project also covers things like editing pages suddenly being broken or something).
+
+I'm not sure what this task is about.",1418161345,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"I've added what I know and can find to the task, but others may be present and hard to find, due to the issue in this task (Catch-22)",1418161019,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"What are the ""subprojects related to Wikitext editor""?
+Or basically: Which existing projects are we discussing here?",1418160799,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Compatibility in Beta Features,"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/35 //
+
+== Narrative ==
+
+As a user, I want to know if a beta feature doesn't work work for my browser or technical configuration.
+
+
+
+== Acceptance Criteria ==
+
+Browser and technology compatibility can vary from one feature to another (VisualEditor in particular isn't available for IE yet). Other features may require Javascript, CSS or other technical configurations as well, that could cause them to malfunction if not enabled.
+
+So each beta feature extension needs to have a blacklist of platforms that it cannot support, stored in Javascript, JSON or other machine-readable format that can be sent to Beta Features.
+
+The Beta Features (or the extension) then needs to check whether the user's configuration matches one of these restricted platforms, so it can let the user know if their platform is not compatible with that feature.
+
+Last but not least, we also need to inform the user about features that are not compatible with their particular browser or configuration. For example, we may want to display a message like: ""This feature is not compatible with your browser yet.""
+
+This is required so the user understands why they cannot enable that feature (even though it's still checked in their preferences -- so they can use it on other platforms).
+
+That message could be bolded and/or colored in red, to provide a visual cue that this feature will not work. Maybe the entire feature could be grayed out, to make it even more explicit?
+
+Here are the types of notes we may need to display, when a feature is not compatible for the user's configuration:
+* Notes about browser compatibility
+** Text displayed to user ""This feature is not compatible with your browser yet.""
+* Notes about JS compatibility
+** Text displayed to user ""You must  [[http://www.enable-javascript.com/ | enable JavaScript]] in your browser to use this feature.""
+* Notes about CSS compatibility
+** Text displayed to user ""Your site skin or custom CSS is not compatible with this feature, to enable it use the default site skin.""
+
+Only one error message should be displayed at any given time, the order of display should be as follows
+# CSS/Skin compatibility
+# JS compatibility
+# Browser compatibility
+e.g. if there is both a browser and JS compatibility issues the user would only see the JS issue.
+
+See the most current feature requirements here:
+
+ [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] 
+
+
+
+== Related Bugs ==
+
+== Related Stories ==
+
+ [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/2 | #2]]  Beta features
+
+See also:
+
+ [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] ",1418054212,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-vz22yajno24klsq4wdsy,task_description,resolved
+Compatibility in Beta Features,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/35 | mingle]] on 2013-10-30 at 23:57:09, @MarkTraceur wrote:
+
+https://gerrit.wikimedia.org/r/88987",1418054215,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-vz22yajno24klsq4wdsy,task_subcomment,NA
+Compatibility in Beta Features,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/35 | mingle]] on 2013-10-11 at 18:06:37, @MarkTraceur wrote:
+
+https://gerrit.wikimedia.org/r/88987",1418054214,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-vz22yajno24klsq4wdsy,task_subcomment,NA
+OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing,"OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing. 
+
+svgo emits SVG like `<path d=""M-1-2 …"">` or `<path d=""M.3.5 …"">` which rsvg is unable to parse (this is valid path data fragment that represents a points (-1; -2) and (0.3; 0.5), and the SVG 1.1 spec even explicitly discusses this syntax). The same issue affects ImageMagick when compiled with rsvg support.
+
+This means that some of OOUI's and VisualEditor's icons will not appear correctly e.g. when uploaded to Commons, and blocks {T76473} since we're unable to rasterize the SVGs to PNG.
+
+This can be worked around using some search-and-replace, but this leaves some questions:
+
+* Can this be fixed in rsvg? Gotta file a bug, even if it'll probably be ignored, and even if not no one is going to upgrade their copy.
+* //Where// do we apply the workaround? To the files in git? During build process? In MediaWiki's RL module from T76473?
+* Should we maintain the workaround ourselves somewhere, or maybe it could be upstreamed to svgo? (As a command-line option for people who want rsvg compatibility at the cost of a few bytes, like us?)",1417782237,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5qhy3k4ikqcg7djrpejr,task_description,resolved
+OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing,The patch is included in rsvg 2.40.6. https://git.gnome.org/browse/librsvg/log/,1417796826,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5qhy3k4ikqcg7djrpejr,task_subcomment,NA
+OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing,"Haha, I just learned that we have //just// deployed a rsvg patch to fix this on Wikimedia wikis last week: https://gerrit.wikimedia.org/r/#/c/173639/ (80dd6ad665610979af294aeff4db417599363250). rsvg upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=620923, patch is https://git.gnome.org/browse/librsvg/commit/?id=5ba4343bccc7e1765f38f87490b3d6a3a500fde1.
+
+So let's forget applying to fix to existing files or bothering svgo people, and just keep the one in ResourceLoaderImage patch for third-parties who don't have the most recent rsvg.",1417783585,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5qhy3k4ikqcg7djrpejr,task_subcomment,NA
+OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing,"The workaround goes like this: https://github.com/trevorparscal/colorize/pull/1/files – in the simplest form, we insert some spaces and zeroes to create path data that is readable to rsvg.
+
+This has already been implemented in [[ https://gerrit.wikimedia.org/r/#/c/165922/ | ResourceLoaderImageModule for icons ]] for T76473 (see `ResourceLoaderImage::massageSvgPathdata()`).
+
+I think we should keep the workaround there (for potential third-party users) **and** apply the fix to SVG files in our repos, for the benefit of people wishing to have copies of the files on Commons. It costs us little and isn't just theoretical, but has already been complained about: https://lists.wikimedia.org/pipermail/wikitech-l/2014-November/079532.html",1417782558,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5qhy3k4ikqcg7djrpejr,task_subcomment,NA
+wikibugs fails to link Phab task in some IRC notifications,"wikibugs fails to link Phab task in some IRC notifications, dunno why. From #-visualeditor (times in CEST or something):
+
+```
+[20:38]	<wikibugs> OOjs-UI: MediaWiki, Apex: Provide default margins for buttons and other widgets
+...
+[20:41]	<wikibugs> OOjs-UI: ComboBoxWidget: Provide a getMenu method
+```
+
+The tasks it should have linked are T76643 and T76646.",1417635858,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-35mqsk5kwrqhdyst3iki,task_description,resolved
+wikibugs fails to link Phab task in some IRC notifications,Fixed by https://gerrit.wikimedia.org/r/#/c/181523/,1419290531,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-35mqsk5kwrqhdyst3iki,task_subcomment,NA
+wm-bot facts have too much bugzilla in them,"Ctrl + F on http://bots.wmflabs.org/~wm-bot/db/%23mediawiki.htm gives 27 usages
+
+Some are probably ok (aliases and such), but some plainly need updating
+
+[22:10:20] <Reedy> !bug
+[22:10:20] <wm-bot> https://bugzilla.wikimedia.org/
+
+Another being vebug giving ""Submit a new ticket on Bugzilla for the VisualEditor: https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditor""",1417558557,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-d2wd3ojejdgstj6g3h2c,task_description,resolved
+wm-bot facts have too much bugzilla in them,Pretty sure I cleaned up most of those I could find.  Please ping me if more are found.,1422127750,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-d2wd3ojejdgstj6g3h2c,task_subcomment,NA
+wm-bot facts have too much bugzilla in them,"note, you can use !bug replace <new text>",1417959454,PHID-USER-ppytiem7rcsbnstfsrvq,PHID-TASK-d2wd3ojejdgstj6g3h2c,task_subcomment,NA
+"VisualEditor ""basic"" image type should be called ""inline""","The media type ""basic"", described using the message Visualeditor-dialog-media-type-none does not explain the real meaning of how the image will be inserted.
+
+It will be clearer to call it something like ""Inline"", and possibly to change the icon as well.",1417524575,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-cxmbeijkrc3gdlqivbjg,task_description,declined
+"VisualEditor ""basic"" image type should be called ""inline""","Change 176919 abandoned by Jforrester:
+Change Basic image type to ""Inline""
+
+Reason:
+See comments on the task.
+
+[[https://gerrit.wikimedia.org/r/176919]]",1417542089,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cxmbeijkrc3gdlqivbjg,task_subcomment,NA
+"VisualEditor ""basic"" image type should be called ""inline""","No. ""Inline"" is absolutely not what this sets. MediaWiki's Multimedia support is terrible, but lying to users to confuse them more is a terrible idea.",1417542081,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cxmbeijkrc3gdlqivbjg,task_subcomment,NA
+"VisualEditor ""basic"" image type should be called ""inline""","Change 176919 had a related patch set uploaded (by Amire80):
+Change Basic image type to ""Inline""
+
+[[https://gerrit.wikimedia.org/r/176919]]
+
+#patch-for-review",1417524806,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cxmbeijkrc3gdlqivbjg,task_subcomment,NA
+Module 'mobile.editor.ve' has incompatible target 'desktop',"```
+2) ResourcesTest::testUnsatisfiableDependencies
+The module 'mobile.editor.ve' must not have target 'desktop' because its dependency 'ext.visualEditor.mobileViewTarget' does not have it
+```",1417494246,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dtnazl6m376lv35fjrzu,task_description,resolved
+Module 'mobile.editor.ve' has incompatible target 'desktop',"Change 178731 merged by jenkins-bot:
+Don't load mobile.editor.ve module in desktop target
+
+[[https://gerrit.wikimedia.org/r/178731]]",1418181350,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dtnazl6m376lv35fjrzu,task_subcomment,NA
+Module 'mobile.editor.ve' has incompatible target 'desktop',"Change 178731 had a related patch set uploaded (by Jdlrobson):
+Don't load RL module for VE in supported mode
+
+[[https://gerrit.wikimedia.org/r/178731]]
+
+#patch-for-review",1418172098,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dtnazl6m376lv35fjrzu,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","This is so we can manage tasks as being definitely fixed, not just that it worked in test.
+
+Descriptions: ""Project for tasks verified by QA as being fixed in phase<N>.""
+
+Access as normal; icon as normal.",1417042379,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k26xtxmrbja4nhavgk5s,task_description,resolved
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","I archived unused project tags #Verified-in-Phase0, #Verified-in-Phase1, #Verified-in-Phase2 last used 27 months ago.",1623921585,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","#Verified-in-Phase0 and #Verified-in-Phase2 were last used (set) in March 2019. 
+#Verified-in-Phase1 was never used.
+Is there still any use for them, or can they be [archived](https://www.mediawiki.org/wiki/Phabricator/Project_management#Archiving_a_project)?",1608415211,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#818733, @Aklapper wrote:
+> I've updated to yellow color and tag icon + added a link to the deployment train to project descriptions.
+
+Thank you!",1417809246,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","I've updated to yellow color and tag icon + added a link to the deployment train to project descriptions.
+
+>>! In T76104#801982, @Jdforrester-WMF wrote:
+> The old #verified tag is not fit for purpose and should be marked as inactive.
+
+If the Wikidata team has agreed on that and also plan to use the new Verified-in-PhaseX tags instead, I'm happy to archive it.",1417699280,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#789665, @Se4598 wrote:
+> Is it intentional that this are ""normal"" projects and not of (visual) type ""Tag"" as per https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Guidelines?
+
+Yes, but I'm sure QA don't particularly care. There is an on-going project to ensure that tasks marked as resolved are actually proven to be resolved in practice, which is what these are for…
+
+>>! In T76104#801766, @Aklapper wrote:
+> The project descriptions of those three projects should link to https://wikitech.wikimedia.org/wiki/Deployments ( https://www.mediawiki.org/wiki/MediaWiki_1.25/Roadmap unfortunately isn't a stable URL) . 
+
+The link can be changed as the current MediaWiki version requests; https://wikitech.wikimedia.org/wiki/Deployments is significantly less stable as an information resource.
+
+> These projects should be tag style. 
+
+Sure.
+
+> These projects might also create slight confusion towards the already existing, generic ""verified"" tag
+
+The old #verified tag is not fit for purpose and should be marked as inactive.
+
+> (at least I want the descriptions to refer to each other and explain the differences in usage).
+
+I see no value in using it.
+
+> For future reference, I appreciate waiting a little bit longer for further feedback on such ideas, if we're not in some urgent hurry. Thanks. :)
+
+There was an urgent hurry. The complete absence of a viable ""verified"" status in Phabricator made it impossible for QA to do their jobs of marking tasks as confirmed-fixed. Phabricator might have been in its first few days, but we are still shipping live code every week, and can't wait for a few days to restart our work.",1417541625,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#801791, @Qgil wrote:
+> I guess ""Visible To: All Users"" is simply a consequence of lack of awareness
+
+Yeah, chatted with James and that's fixed now",1417541010,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","I guess ""Visible To: All Users"" is simply a consequence of lack of awareness of  https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Default_policy. I have started to insist on View Public in proposals from new project creators.",1417538356,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","Also, why are these projects set as ""Visible To: All Users"" instead of ""Public""?
+Please always provide reasons, as explained on https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Policy
+
+Currently going to e.g. https://phabricator.wikimedia.org/T75378 and not being logged in I see two restricted projects (VisualEditor-Tables being the other one).",1417538204,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","...and I also appreciate pointers where the practice to use these new tags is documented on-wiki, as that should also **definitely** be part of the project descriptions.",1417538062,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","The project descriptions of those three projects should link to https://wikitech.wikimedia.org/wiki/Deployments ( https://www.mediawiki.org/wiki/MediaWiki_1.25/Roadmap unfortunately isn't a stable URL) . 
+These projects should be tag style. 
+These projects might also create slight confusion towards the already existing, generic ""verified"" tag (at least I want the descriptions to refer to each other and explain the differences in usage).
+
+If there's no opposition I am going to go ahead tomorrow or so.
+
+For future reference, I appreciate waiting a little bit longer for further feedback on such ideas, if we're not in some urgent hurry. Thanks. :)",1417538015,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#789703, @Qgil wrote:
+> They look indeed like better suited for tags.
+
+I agree (especially if QA don't care).
+>>! In T76104#789656, @Jdforrester-WMF wrote:
+>[...]
+>> And just curious, where can I learn about Phase0, 1, 2?
+> 
+> wikitech.wikimedia.org/wiki/Deployments and a few dozen other places.
+
+Based on that I assume this means the specific wiki sets/groups and so I updated the descriptions of the projects to reflect that. Please correct me if I'm wrong at this.
+
+I'm also confused of the usage of these different terms (group/set and phase), so it would for me initially clearer if they were named Verified-in-Group2 as group seems to be the normally used term for this.",1417044849,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",They look indeed like better suited for tags.,1417043564,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#789665, @Se4598 wrote:
+> Is it intentional that this are ""normal"" projects and not of (visual) type ""Tag"" as per https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Guidelines?
+
+Yes, but I'm sure QA don't particularly care. There is an on-going project to ensure that tasks marked as resolved are actually proven to be resolved in practice, which is what these are for…",1417043208,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","Is it intentional that this are ""normal"" projects and not of (visual) type ""Tag"" as per https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Guidelines?",1417043124,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#789646, @Qgil wrote:
+> Just checking, are you in sync with QA?
+
+Yes; this was at @RYasmeen's request.
+
+> And just curious, where can I learn about Phase0, 1, 2?
+
+wikitech.wikimedia.org/wiki/Deployments and a few dozen other places.",1417042800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","You provided less than a minute for consensus.  :)
+
+Just checking, are you in sync with QA? And just curious, where can I learn about Phase0, 1, 2?",1417042591,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","Done:
+
+#Verified-in-Phase0
+#Verified-in-Phase1
+#Verified-in-Phase2
+",1417042467,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+VisualEditor is not displayed after clicking on Edit,"MediaWiki version is 1.25wmf9
+
+VisualEditor 1.25wmf9 is installed and enabled:
+```
+require_once ""$IP/extensions/Parsoid/Parsoid.php"";
+require_once ""$IP/extensions/VisualEditor/VisualEditor.php"";
+
+$wgDefaultUserOptions['visualeditor-enable'] = 1;
+$wgHiddenPrefs[] = 'visualeditor-enable';
+//$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
+$wgVisualEditorParsoidHTTPProxy = false;
+$wgVisualEditorParsoidURL = 'http://[my.nodejs.host]:80';
+$wgVisualEditorParsoidPrefix = 'myWiki';
+//$wgSessionsInObjectCache = true;
+$wgVisualEditorParsoidForwardCookies = false;
+$wgVisualEditorNamespaces = array_merge( $wgContentNamespaces, array( NS_USER ) );
+```
+
+If I curl Parsoid for the Main Page (from the same host where MediaWiki is installed) I can see page parsed and a log on Parsoid
+```
+curl http://[my.nodejs.host]/myWiki/Main_Page?oldid=1
+```
+
+If I click on Edit {F16470} the page is refreshed (?title=Main_Page&veaction=edit), but I can't see the VisualEditor editing area. Moreover, nothing is logged on Parsoid (like if the request has never be done).
+If I click on Edit source the standard editor is displayed.",1417033425,PHID-USER-aost7ybqf3mbefvdfsdc,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_description,resolved
+VisualEditor is not displayed after clicking on Edit,"Yes, I found it and already did it, thanks.
+
+Now I'm investigating another issue.
+{F16587}
+After I click on Edit the loader bar rolls forever and the editing area never appears.
+I just found this error in the browser console
+
+```
+Exception thrown by ext.visualEditor.mwlink 
+
+
+TypeError: Expecting a function in instanceof check, but got undefined TypeError: Expecting a function in instanceof check, but got undefined {stack: (...), message: ""Expecting a function in instanceof check, but got undefined""}message: ""Expecting a function in instanceof check, but got undefined""stack: (...)get stack: function () { [native code] }arguments: nullcaller: nulllength: 0name: """"prototype: StackTraceGetterconstructor: function () { [native code] }arguments: nullcaller: nulllength: 0name: """"prototype: StackTraceGetterconstructor: function () { [native code] }arguments: nullcaller: nulllength: 0name: """"prototype: StackTraceGetterconstructor: function () { [native code] }arguments: nullcaller: nulllength: 0name: """"prototype: StackTraceGetter__proto__: function Empty() {}<function scope>__proto__: Object__defineGetter__: function __defineGetter__() { [native code] }__defineSetter__: function __defineSetter__() { [native code] }__lookupGetter__: function __lookupGetter__() { [native code] }__lookupSetter__: function __lookupSetter__() { [native code] }constructor: function Object() { [native code] }hasOwnProperty: function hasOwnProperty() { [native code] }isPrototypeOf: function isPrototypeOf() { [native code] }propertyIsEnumerable: function propertyIsEnumerable() { [native code] }toLocaleString: function toLocaleString() { [native code] }toString: function toString() { [native code] }valueOf: function valueOf() { [native code] }get __proto__: function __proto__() { [native code] }set __proto__: function __proto__() { [native code] }__proto__: function Empty() {}apply: function apply() { [native code] }arguments: nullbind: function bind() { [native code] }call: function call() { [native code] }caller: nullconstructor: function Function() { [native code] }length: 0name: ""Empty""toString: function toString() { [native code] }__proto__: Object<function scope><function scope>__proto__: Object__proto__: function Empty() {}apply: function apply() { [native code] }arguments: nullcaller: nulllength: 2name: ""apply""__proto__: function Empty() {}<function scope>arguments: nullbind: function bind() { [native code] }arguments: nullcaller: nulllength: 1name: ""bind""__proto__: function Empty() {}<function scope>call: function call() { [native code] }arguments: nullcaller: nulllength: 1name: ""call""__proto__: function Empty() {}<function scope>caller: nullconstructor: function Function() { [native code] }length: 0name: ""Empty""toString: function toString() { [native code] }__proto__: Object<function scope><function scope>__proto__: Object__proto__: function Empty() {}<function scope>set stack: function () { [native code] }arguments: nullcaller: nulllength: 1name: """"prototype: StackTraceSetter__proto__: function Empty() {}<function scope>__proto__: Error
+```",1417044265,PHID-USER-aost7ybqf3mbefvdfsdc,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_subcomment,NA
+VisualEditor is not displayed after clicking on Edit,"Aha. That means you didn't checkout the actual code for VisualEditor itself, just the MediaWiki extension that embeds it. You need to do `git submodule update --init `. See https://www.mediawiki.org/wiki/Extension:VisualEditor#Download.
+",1417041211,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_subcomment,NA
+VisualEditor is not displayed after clicking on Edit,"Maybe I found something:
+
+```
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: "".../extensions/VisualEditor/lib/ve/src/ve.track.js""' in .../includes/resourceloader/ResourceLoaderFileModule.php:843
+Stack trace:
+#0 .../includes/resourceloader/ResourceLoaderFileModule.php(362): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 .../includes/resourceloader/ResourceLoader.php(901): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 .../includes/resourceloader/ResourceLoader.php(647): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 .../load.php(45): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: "".../extensions/VisualEditor/lib/ve/src/ve.js""' in .../includes/resourceloader/ResourceLoaderFileModule.php:843
+Stack trace:
+#0 .../includes/resourceloader/ResourceLoaderFileModule.php(362): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 .../includes/resourceloader/ResourceLoader.php(901): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 .../includes/resourceloader/ResourceLoader.php(647): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 .../load.php(45): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+```
+The folder .../extensions/VisualEditor/lib/ve is empty, maybe something went wrong while downloading with git.",1417038630,PHID-USER-aost7ybqf3mbefvdfsdc,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_subcomment,NA
+VisualEditor is not displayed after clicking on Edit,What if any output is there on your browser's console log?,1417034461,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_subcomment,NA
+Mismatch between new page text seen by AbuseFilter and actual new page content,"On frwiki, we have false positives on a filter that tags edits that remove all categories.
+
+Filter: https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Filtre_antiabus/14
+Example of false positive: https://fr.wikipedia.org/w/index.php?title=Bertrand_Chameroy&diff=prev&oldid=109458887 (it should not have the tag ""suppression des catégories"")
+Details of the AbuseFilter log event: https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1204633
+
+I am sure that this is not an error in the filter itself, because in the details of the AbuseFilter log event, the diff shows that categories are indeed removed. But this diff does not match the real diff, where categories are unchanged.
+
+Expected behavior: the content of the 'new_text' variable of AbuseFilter should always match the new page text.
+
+I found 4 such false positives for this filter in the last two months. In all cases, modification also has the 'VisualEditor' tag, so this could be related.
+
+Other cases:
+https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1200961
+https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1190456
+https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1164028
+",1417029094,PHID-USER-5h57zgttfaaarfvo4g6s,PHID-TASK-g5mewjy3ybwuscrobyvx,task_description,duplicate
+"Cite inspector does not disappear upon clicking Insert, prevents page save","Edit any page in beta labs, e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Cite_VisualEditor_Test?vehidebetadialog=true&veaction=edit
+
+Click Cite and fill in the textareas
+
+Click Insert
+
+Cite inspector should disappear but does not. 
+
+Also note that the appearance of the Cite inspector is exceptionally small, in both Firefox and Chrome",1416844281,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-sx57fjn2ccu5x2lvqnvi,task_description,resolved
+"Cite inspector does not disappear upon clicking Insert, prevents page save",The issue is not reproducible anymore.,1423275793,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-sx57fjn2ccu5x2lvqnvi,task_subcomment,NA
+Newly made links are red until page is saved,"When I put in the template ""Infobox road"" onto a subpage of my user page, and added some parameters, the links they made were red.
+
+Screenshot link:
+
+[[https://en.wikipedia.org/wiki/File:Philroc-VEBug.png|The screenshot (red links circled)]]
+
+More info:
+
+[[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Newly_made_links_are_red_until_page_is_saved|The bug at Wikipedia]]
+
+I hope somebody gets to this soon.
+
+Thanks!",1416840250,PHID-USER-tx42osyrriffbzlseejv,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_description,invalid
+Newly made links are red until page is saved,"Right, it was T95247",1429147082,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,I can replicate the issue. I think it's separate - the reason those links get marked red is because their CE elements get a blank href element set somehow. Do you want to open a separate bug or shall I?,1429146825,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,"I don't know, but I'm seeing red links in Citoid.  It's in the initial
+display, not when you go back to look at it later.  I suspect that this is
+a separate bug, though.  (Steps to reproduce:  Add a ref to books.google.com;
+Insert; look at the red ISBN link.)",1427927039,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,Has this been fixed as T94315?,1427852197,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,This has re-appeared.  You can read the editor's report at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=651892335#Weird_bug_with_VE,1426661730,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,And feel free to reopen if you do still run into these issues,1421886602,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,Please try again. I think we fixed these issues already.,1421363927,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,"Updating [[ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_4#Newly_made_links_are_red_until_page_is_saved | feedback page ]] link. This bug looks like a regression to me.
+Wittylama reported something similar today: <<See this edit https://en.wikipedia.org/w/index.php?title=National_Library_of_Australia&diff=636455550&oldid=636107184 - where I replace a raw link with the ""main"" template. Before saving, the Visual editor shows the link as a redlink and adds an extra line of whitespace above and below the new template. However, when I actually save the edit the link goes blue and the whitespace disappears. So, the saved result is exactly what I wanted to happen, but the visual editor 'preview' made it look like there were going to be two mistakes.>>",1417708202,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+"""Maximum function nesting level"" fatal when visiting an imported page with nested conversations","I imported https://www.mediawiki.org/wiki/VisualEditor/Feedback into Flow with the LQT importer (plus some small changes for https://gerrit.wikimedia.org/r/#/c/172925/ that are probably not relevant to this bug).
+
+The import crashed (bug 73638), but a lot of stuff was already imported by then.  However, when I visit it, I get:
+
+""Fatal error: Maximum function nesting level of '200' reached, aborting""
+
+The stack is https://phabricator.wikimedia.org/P98 .
+
+It seems that the nesting level of a topic may influence the nesting level of the function stack, and cause it to go over the limit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416453300,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nscjwo6mgqab76opx5wt,task_description,declined
+"""Maximum function nesting level"" fatal when visiting an imported page with nested conversations","This error comes from xdebug.max_nesting_level.
+
+XDebug is not enabled in production, so we shouldn't have to worry about this.
+
+I confirmed it can be worked around locally by raising the limit or switching to HHVM.",1416454279,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nscjwo6mgqab76opx5wt,task_subcomment,NA
+"""Detected overflow for millisecond timestamp"" UID error when importing large LQT board into Flow","I hit this when testing https://gerrit.wikimedia.org/r/#/c/172925/ against https://www.mediawiki.org/wiki/VisualEditor/Feedback .
+
+So far I haven't retested against master, since the import is pretty slow.  I suspect it will be present there.
+
+Command was:
+
+mwscript extensions/Flow/maintenance/convertLqt.php --wiki=wiki User_talk:VE_Feedback_1 --allowunknownusernames 1 --remoteapi=https://www.mediawiki.org/w/api.php --srcpage=VisualEditor/Feedback --verbose 
+
+Log is https://phabricator.wikimedia.org/P97 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416452820,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-l54ayivuqbmpreuplbak,task_description,resolved
+"""Detected overflow for millisecond timestamp"" UID error when importing large LQT board into Flow","Change 174830 had a related patch set uploaded by EBernhardson:
+Bug: UID generator counter overflow
+
+https://gerrit.wikimedia.org/r/174830",1416522076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l54ayivuqbmpreuplbak,task_subcomment,NA
+[Regression] VisualEditor: Switching to read mode after rendering diff leaves ve.ce.Surface behind,"Screenshot of Read mode after editing
+
+Steps to reproduce bug:
+
+1. Edit a page
+2. Insert some text or a table
+3. Click ""Save page"" in the toolbar
+4. Click ""Review your changes"" in the dialog
+5. Click ""Return to save form""
+6. Click ""Resume editing"" in the dialog
+7. Click ""Read"" tab from the MediaWiki navigation
+
+
+Expected:
+
+Original page re-appears.
+
+Actual:
+
+* The modified state from the editor persists.
+* Even the highlighting is still there (e.g. can highlight different cells in the table  we just inserted).
+* The ""Edit"" tab in the MW nav is now broken (clicking it does nothing, no exception thrown).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15110}",1416363840,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2zl7jj2byve5amcxz4nc,task_description,resolved
+[Regression] VisualEditor: Switching to read mode after rendering diff leaves ve.ce.Surface behind,"
+
+*** This bug has been marked as a duplicate of bug 73589 ***",1416364083,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2zl7jj2byve5amcxz4nc,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"switch edit mode fails in Chrome
+
+This manifests in several ways, see the browser test failures at
+Chrome: https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+Firefox: https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/
+
+The common case for Chrome and Firefox:
+
+As a logged-in user with access to VisualEditor, edit any page. 
+Attempt to switch from the wikitext editor to VE using the dropdown controls. 
+Nothing happens, VE does not show up.  See screen shot. 
+
+The Firefox-only issue: 
+
+Attempt to edit a new page by supplying a bogus URL, e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Foobarbaz
+
+Clicking the edit icon does nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15094}",1416354960,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-a27c6scsdqjxaingm45j,task_description,resolved
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,I can edit new pages on Firefox so I think this has been fixed. Please reopen if you can still duplicate it.,1416813191,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"**gerritadmin** wrote:
+
+Change 174384 abandoned by Florianschmidtwelzow:
+Don't try to set cursor on hidden elements
+
+Reason:
+Function reverted in: I672d04c16f9348f7e08c4f64b339b307276d2a5a
+
+https://gerrit.wikimedia.org/r/174384",1416517242,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,I captured the other issue in bug 73646,1416483048,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,If there are two problems here there should be 2 bugs..,1416479425,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"okay,just to keep note, this bug is now in test2 as well after today's deployment since it was regression from wmf9.I will test the fix in test2 once it is merged and backported.",1416451353,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"Unhappily no, this patch adresses the Firefox problem. For now, I haven't had the time to look into it, why VE doesn't work :/",1416434101,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"Ah got it, so this patch is going to fix for all pages in all browsers?",1416433265,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"Jon is talking about the Firefox only problem :) The VE problem is right, it doesn't work on all pages :(",1416432160,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"Nope, this is not a browser/page specific issue,was happening for me in all pages even in iOS safari.Once you switch to edit source mode the ""Edit"" button will no longer work from that point on.And then for a new page, it always opens the Edit Source mode first, so thats why its always reproducible for a new page too.",1416424643,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,This seems to be specific for new pages in Firefox.,1416421472,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"**gerritadmin** wrote:
+
+Change 174384 had a related patch set uploaded by Florianschmidtwelzow:
+Don't try to set cursor on hidden elements
+
+https://gerrit.wikimedia.org/r/174384",1416388806,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"For the second (FF only):
+[10:11:21.144] ""[Exception... ""Failure""  nsresult: ""0x80004005 (NS_ERROR_FAILURE)""  location: ""JS frame :: http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T090804Z :: EditorOverlay<._loadContent/< :: line 17""  data: no]"" [object XPCWrappedNative_NoHelper]
+
+Caused by: I2a3eab234338bae6258abcde99144bdd2464805f
+
+VE: confirmed :/",1416388781,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/LKgERdDV",1416355223,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+VisualEditor:[Regression pre-wmf9] Inserted Media caption is not displayed correctly,"Caption without background
+
+Betalabs only in Chrome, FF, and Safari. test2 is fine.
+
+
+VE - Insert Media and enter Caption - save the page. The Media caption is displayed with white background. 
+See the attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15369}",1416006000,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-khh4rz3t6eqnbtz47oby,task_description,invalid
+VisualEditor:[Regression pre-wmf9] Inserted Media caption is not displayed correctly,"This is how Beta Labs is configured, irritatingly.",1416433677,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-khh4rz3t6eqnbtz47oby,task_subcomment,NA
+small race condition in Links inspector,"Edit a page on beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Links_VisualEditor_Test?vehidebetadialog=true&veaction=edit
+
+Click the Links inspector
+
+Note that the ""Done"" button is enabled
+
+Quickly paste (do not type by hand) an external link e.g. http://www.example.com in the link field
+
+Note that upon pasting ""http://www.example.com"", VE takes some time before displaying the ""External link/New page"" overlay. 
+
+If the user clicks ""Done"" after pasting text in the link field but before the ""External link/New page"" overlay appears, VE creates a local link [[foo]] instead of the desired external link [http://www.example.com foo]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415985120,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-sk5dddkhjvxvi76fjcya,task_description,resolved
+small race condition in Links inspector,"Re-checked in betalabs - there is no noticeable delay in displaying ""External link/New page"" overlay(some performance improvements were made). ",1423276267,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-sk5dddkhjvxvi76fjcya,task_subcomment,NA
+VisualEditor: Safari - white spaces are dropped for copied formatted text,"Safari cut and paste formatted text-white spaces issue
+
+Steps to reproduce: 
+
+Safari only - test2, Betalabs.
+
+1. In VE type some text - e.g. underlined text. Apply underlined format to 'underlined'.
+
+2. Highlight 'underlined text' and copy/paste it somewhere else on the page. 
+
+It will be displayed as: underlinedtext. Underlined formatting will be gone and a white space between words is lost. 
+
+This is affecting many options in formatted text - see the attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15096}",1415831700,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_description,resolved
+VisualEditor: Safari - white spaces are dropped for copied formatted text,This was verified in betalabs.  It is sort of a  test case for the bug fix for 71718.,1416265549,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_subcomment,NA
+VisualEditor: Safari - white spaces are dropped for copied formatted text,"
+
+*** This bug has been marked as a duplicate of bug 71718 ***",1415898350,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_subcomment,NA
+VisualEditor: Safari - white spaces are dropped for copied formatted text,Syntax fix: bug 71718,1415892093,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_subcomment,NA
+VisualEditor: Safari - white spaces are dropped for copied formatted text,"Duplicate of [[bug 71718]], I think.",1415890623,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_subcomment,NA
+VisualEditor: Using the VE toolbar in MSIE causes the cursor to jump to the start of the page,"Saw lots of bugs reported and fixed about the jumping of focus when using the toolbar.  Now seeing the problem in MSIE for many uses of the toolbar.  Would like a clue about fixing it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415771100,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-eohxemedb6jupuzhjihr,task_description,duplicate
+VisualEditor: Using the VE toolbar in MSIE causes the cursor to jump to the start of the page,Related bug/fix? T66041 ,1427391137,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-eohxemedb6jupuzhjihr,task_subcomment,NA
+VisualEditor: Using the VE toolbar in MSIE causes the cursor to jump to the start of the page,"Some examples when a page scrolls up in IE11 
+
+- Using Backspace button 
+
+- changing existing Page title, Heading, and sub-headings to other format",1415821431,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-eohxemedb6jupuzhjihr,task_subcomment,NA
+VisualEditor: Paste from Word to MSIE fails to insert anything,"Pasting anything besides plain text into MSIE fails.  Tried this with Word in FF and Chrome (see bug #73292) and had at least some success.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415766540,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-hiemxvbjccwrbpce5noi,task_description,resolved
+VisualEditor: Paste from Word to MSIE fails to insert anything,Closing this for now since it has been solved elsewhere.  At least *some* pasting works.,1429106123,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-hiemxvbjccwrbpce5noi,task_subcomment,NA
+VisualEditor: Paste from Word to MSIE fails to insert anything,Also bug 65714 comment 2.,1415767124,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-hiemxvbjccwrbpce5noi,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","When the categories suggested in the drop down are long enough, a scroll bar appears.  Clicking on this scroll bar causes the drop down to close.
+
+
+It would be nice if you could use the scrollbar like others -- to scroll up and down the list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415743920,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_description,resolved
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","
+
+*** This bug has been marked as a duplicate of bug 65774 ***",1415843475,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","Change 172933 had a related patch set uploaded by Catrope:
+Don't close PopupToolGroups when the scroll bar is clicked
+
+https://gerrit.wikimedia.org/r/172933",1415843388,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","Merging into bug 65774.
+
+*** This bug has been marked as a duplicate of bug 65774 ***",1415807884,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","Change 172723 had a related patch set uploaded by Alex Monk:
+MenuWidget: Don't close menu when you click the scroll bar
+
+https://gerrit.wikimedia.org/r/172723",1415802742,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","Okay, I was just lucky and the last category would fit always without a scroll bar, unless I changed the window height. This feels like a duplicate bug though...",1415753833,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","I've reproduced this on https://www.mediawiki.org/wiki/Project:Sandbox?veaction=edit using Chrome and Firefox on Windows and Linux.
+
+What steps are you trying?  Maybe I need to provide more information?",1415752854,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown",Can't reproduce...,1415749132,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style","Enviornment-test2, beta
+
+1> Select language and click done, when the language inspector opens.
+2>type some text ,on the CE.
+//the text has language style
+3>now place the cursor to the start of the line and type in some more text.
+// also has the language  style
+4> after typing the additional text insert a space. Then delete that space.
+Notice the cursor moves to the start of the line and also the language annotation from the recently typed text has been removed. Whereas the previously typed text still retains the annotation style.
+
+See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1415627460,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ksiwshyonkquzpb6aoz4,task_description,resolved
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style",The issue was checked - does not exist anymore. ,1423524357,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ksiwshyonkquzpb6aoz4,task_subcomment,NA
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style","Confirmed. 
+
+The scenario for the issue is actually simpler. 
+
+1. Select language and click done, when the language inspector opens.
+2. type some text ,on the CE.
+3. then add text to the beginning of the line - just start typing something and after some text click delete as if you were to correct something - all entered text  from your cursor to the beginning of the line will be deleted.",1415646640,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ksiwshyonkquzpb6aoz4,task_subcomment,NA
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style",Also found in FF 33.1.,1415631019,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ksiwshyonkquzpb6aoz4,task_subcomment,NA
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style",http://youtu.be/qzzJDdPJGQY,1415630681,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ksiwshyonkquzpb6aoz4,task_subcomment,NA
+VisualEditor: Can't delete text... which is actually not there,"User added the words ""La mui"" to https://fr.wikipedia.org/wiki/Audiomachine#Utilisations_de_leurs_musiques . Then proceeded to edit elsewhere in the page. When he went back to those words, he found out he couldn't remove them at all (see screencast at https://www.youtube.com/watch?v=IMlMZt1FMvY : all his actions seem to affect the header below). When he reviews his changes, that content is actually not there.
+
+Windows 7, Firefox Aurora 35.0a2 (2014-11-05), Vector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415610300,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-3jzj5p7wyiyt5e2ugrkb,task_description,resolved
+VisualEditor: Can't delete text... which is actually not there,"Could not reproduce. Sometime when a user session has been open for long and/or editing has taken long time(many edits) - UI becomes somewhat irresponsive. 
+However, no specific and reproducible details have been reported yet. ",1423692980,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3jzj5p7wyiyt5e2ugrkb,task_subcomment,NA
+VisualEditor: Can't delete text... which is actually not there,"(In reply to Ed Sanders from comment #1)
+> Can't reproduce this.
+I am the user to which it happened. I actually don't know how it happened, I did nothing special as far as I can remember. Elitre has suggested it may be because of my PC (I have sometimes other bugs that happen only to me). However the same bug or an extremely similar one also happened to me last year (in November 2013) but with my old PC with Firefox and Windows 7.",1415661001,PHID-USER-4cgt73x34j35pnbem65l,PHID-TASK-3jzj5p7wyiyt5e2ugrkb,task_subcomment,NA
+VisualEditor: Can't delete text... which is actually not there,Can't reproduce this.,1415648109,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3jzj5p7wyiyt5e2ugrkb,task_subcomment,NA
+VisualEditor: Tables wikitext can be inconsistent,"In wikitext editor, you can separate cells with a double bar ""||"" on the same line :
+
+|Cell 1 || Cell 2 || Cell 3
+
+(same thing for headers, except two exclamation marks ""!!"" are used).
+
+When adding a new cell with VE, the result will look like
+|Cell 1 || Cell 2 || Cell 3
+|Cell 4
+
+rather than |Cell 1 || Cell 2 || Cell 3 || Cell 4 .
+
+While this still works, it makes the table less understandable and usable for those who do not use VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415608980,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5bbju6mqrb4hytvcocfv,task_description,duplicate
+VisualEditor: Tables wikitext can be inconsistent,"Merging into bug 63356; ideally we'd want Parsoid to use inline or per-line syntax per precedent in the context, which sounds messy.
+
+*** This bug has been marked as a duplicate of bug 63356 ***",1415618411,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5bbju6mqrb4hytvcocfv,task_subcomment,NA
+VisualEditor: Annotation on top of a link produces inefficient wikitext ([[asd|''asd'']]),"Annotation on top of a link produces inefficient wikitext ([[asd|''asd'']]).
+
+1. Type text, for example ""asd"".
+2. Select it.
+3. Press Ctrl+K to create a link, accept ""asd"" as link target.
+4. Press Ctrl+I to italicize.
+
+Result: [[asd|''asd'']].
+
+Compare with:
+
+1. Type text, for example ""asd"".
+2. Select it.
+3. Press Ctrl+I to italicize.
+4. Press Ctrl+K to create a link, accept ""asd"" as link target.
+
+Result: ''[[asd]]''.
+
+I would expect both ways to produce the same wikitext, ''[[asd]]''.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415552880,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kkuldyxop75uyhtvgofe,task_description,resolved
+VisualEditor: Annotation on top of a link produces inefficient wikitext ([[asd|''asd'']]),"Yeah, merging with bug 50098.
+
+*** This bug has been marked as a duplicate of bug 50098 ***",1415618227,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kkuldyxop75uyhtvgofe,task_subcomment,NA
+VisualEditor: Annotation on top of a link produces inefficient wikitext ([[asd|''asd'']]),bug 50098 ?,1415605943,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kkuldyxop75uyhtvgofe,task_subcomment,NA
+"VisualEditor: [regression] Inserting new internal link inserts text, but doesn't linkify it, if you complete the dialog before page title suggestions appear","Inserting new internal link inserts text, but doesn't linkify it.
+
+1. Place cursor on empty paragraph
+2. Open the link inspector (Ctrl+K)
+3. Type in title of a page and press Enter
+
+A new link to that page should appear. Instead, only the text typed is inserted, without the link annotation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415543760,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zk2f2rtykxd7etnlrmtb,task_description,resolved
+"VisualEditor: [regression] Inserting new internal link inserts text, but doesn't linkify it, if you complete the dialog before page title suggestions appear","Seems that you need to complete the dialog before page title suggestions appear, so just press Enter really quickly after typing.",1415547012,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zk2f2rtykxd7etnlrmtb,task_subcomment,NA
+"VisualEditor: Newly added template added with ""Template:"" prefix","https://www.mediawiki.org/w/index.php?title=Google_Code-in_2014&diff=1255073&oldid=1255066
+
+Newly added ""Bug"" template was added as {{Template:Bug|…}} rather than just {{Bug|…}}. As far as I know I did nothing special to cause that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415462520,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7h5p3whd42ak5tbojlbc,task_description,resolved
+"VisualEditor: Newly added template added with ""Template:"" prefix",Verified on www.mediawiki.org - the Bug template added as {{Bug|73179}}.,1416260589,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-7h5p3whd42ak5tbojlbc,task_subcomment,NA
+"VisualEditor: Newly added template added with ""Template:"" prefix",Should've been fixed by Roan in Gerrit change 172319.,1416188116,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-7h5p3whd42ak5tbojlbc,task_subcomment,NA
+Get Parsoid (and thus VisualEditor) working again on Wikitech,"They broke and were disabled, but we should get them back.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415318040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vkpbe46usd5elh6546nv,task_description,resolved
+Get Parsoid (and thus VisualEditor) working again on Wikitech,Looks like this was fixed at some point.,1426689638,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vkpbe46usd5elh6546nv,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"flow_tree_revision
+
+Parsoid is running happily. I can edit pages using VisualEditor without issue.
+
+I can visit a Flow page and add a new topic or comment. However, upon saving I don’t actually see the content of the comment. Topic titles do show up.
+
+I’m not a DB guru, but upon inspecting the flow-specific database tables I noticed some weird syntax in the fields. Maybe it’s my editor (Sequel Pro) or an encoding issue.
+
+I turned on MW debugging and I see this message:
+
+Warning: DOMDocument::saveHTML() expects exactly 0 parameters, 1 given in /var/www/html/w/extensions/Flow/includes/Parsoid/Utils.php on line 273
+
+1.25wmf5, PHP 5.3.3, most recent head/master build of Flow, most recent build of Parsoid.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+
+**Attached**: {F15052}",1415226120,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-yrjidyow5pz4cmjn4or3,task_description,declined
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"While this is incredibly specific to my situation, I would like to point out that PHP 5.3.3 is still the standard version provided with RHEL-6. Which isn't the latest version, but still supported by Redhat.
+
+Again, I realize this extension is a WMF-focused endeavor, but it's too cool to not be used elsewhere. :)
+
+I'm off to argue with my linux sysadmins on updating PHP. Wish me luck!",1415905967,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"https://www.mediawiki.org/wiki/Extension:Flow now documents Flow's php 5.3.6+ requirement. I'm proposing WONTFIX, although patches welcome.",1415386992,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),I just tested on a system with 5.6.1 - Flow works as intended.,1415299051,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Erik is right.  Core requires 5.3.3, so we have the option of keeping support for that or documenting requiring 5.3.6.  The former may be doable if it's not much work, but core will probably bump above that soon anyway.",1415234960,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Actually i didn't read close enough, you are on 5.3.3.  I'm almost certain the problem is that, and we will have to update Flow's minimum requirements to 5.3.6.",1415234734,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"The problem with DOMDocument::saveHTML is most likely our issue, it looks like that argument was added in php 5.3.6
+
+Which version of php are you on?  I think we advertise support of 5.3.3, but we might need to bump that.",1415234562,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Sorry, I should have checked your screenshots first.  I see it's MySQL.  The weird characters are the binary UUID values.  Basically, consider the ID an arbitrary blob of bits (it does appear in the UI, serialized, in some places, e.g. in Topic URLs).
+
+I'm not sure why it's not working, though.",1415234520,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"What database engine are you using (MySQL, PostegreSQL, etc.)?",1415234334,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Created attachment 17047
+mystery comments
+
+**Attached**: {F15054}",1415226207,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Created attachment 17046
+flow_revision
+
+**Attached**: {F15053}",1415226159,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+VisualEditor Mobile: Calling VisualEditor from MF spins forever,"As a logged in user with VE available, edit any page in beta labs e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Cyrion_and_Candidus#/editor/0
+
+Page is white and shows spinner, editor never appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415213400,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ju3dj4ysqtrezth635p2,task_description,resolved
+VisualEditor Mobile: Calling VisualEditor from MF spins forever,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/z22jBbGj",1415213714,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ju3dj4ysqtrezth635p2,task_subcomment,NA
+VisualEditor Mobile: Calling VisualEditor from MF spins forever,"
+
+*** This bug has been marked as a duplicate of bug 73038 ***",1415213710,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ju3dj4ysqtrezth635p2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,"Safari blurs text
+
+1. Open a page in Safari VE Read mode - the text is displayed normally.
+
+2. Switch to Edit  - the beginning of the page displays a blurred text.
+Clicking in the text does not make it clearer. 
+
+See the attached screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15010}",1415209920,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,Now seems fine?,1417578010,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,"Created attachment 17040
+Safari Read mode - text s clear
+
+**Attached**: {F15011}",1415212973,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,"Created attachment 17039
+Safari Read mode - text is clear
+
+//attachment Safari Read mode.png ignored as obsolete//",1415210338,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,"Created attachment 17038
+Safari displays clear text in Read mode
+
+//attachment Safari Read mode.png ignored as obsolete//",1415210103,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_subcomment,NA
+Fix the language screenshot test for new VE architecture,"VE no longer has iframes.  I don't really understand how ""iframe_element"" is being used: 
+
+$ grep -r ""iframe_element"" *
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, -2)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, -2)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Page_Settings_Redirects-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.page_settings_heading_element, @current_page.prevent_redirect_element], @current_page.iframe_element, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Page_Settings_TOC-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.table_of_contents_element], @current_page.iframe_element, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Page_Settings_Edit_Links-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.page_settings_editlinks_element], @current_page.iframe_element, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Apply_Changes-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.settings_apply_button_element], @current_page.iframe_element, 3)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.link_list_element, @current_page.iframe_element, @current_page.new_link_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element])
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Media_alternative_text-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.media_alternative_block_element], @current_page.iframe_element)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element])
+features/step_definitions/language_screenshot_steps.rb:    page.iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element, @current_page.formula_image_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, 0)
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1415209320,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-6l5wjfkbykj3jdrufonn,task_description,resolved
+Fix the language screenshot test for new VE architecture,"**gerritadmin** wrote:
+
+Change 171531 merged by jenkins-bot:
+[BrowserTest] Fixed failing language screenshot browser tests
+
+https://gerrit.wikimedia.org/r/171531",1415624810,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6l5wjfkbykj3jdrufonn,task_subcomment,NA
+Fix the language screenshot test for new VE architecture,"**gerritadmin** wrote:
+
+Change 171531 had a related patch set uploaded by Vikassy:
+Fixed failing browser tests
+
+https://gerrit.wikimedia.org/r/171531",1415276609,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6l5wjfkbykj3jdrufonn,task_subcomment,NA
+Fix the language screenshot test for new VE architecture,"Vikas, can you take a look?
+
+Amir, if Vikas does not have the time to fix this, we could work on it during our regular pairing sessions.",1415265896,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-6l5wjfkbykj3jdrufonn,task_subcomment,NA
+VisualEditor: Safari only - typing text in a table cell - the page scrolls up,"1. Safari - open any page and make sure that a page has enough content to have a vertical scrollbar. 
+
+2. Insert a table at the bottom of the page.
+
+Start typing in a table cell - the page scrolls up with each typed character.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415149320,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-vgdeswcro65dp4sojtrt,task_description,resolved
+VisualEditor: Safari only - typing text in a table cell - the page scrolls up,This was resolved some time ago.,1417577587,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vgdeswcro65dp4sojtrt,task_subcomment,NA
+VisualEditor: line height in intro message is wrong causes collusions,"text collisions
+
+line height should be increased to not have text and controls run together.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14807}",1415128920,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-sz7lovyjgkskrmxay2d6,task_description,invalid
+VisualEditor: line height in intro message is wrong causes collusions,"on en.wiki:
+
+go to article bonshō, click edit beta.",1415145904,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-sz7lovyjgkskrmxay2d6,task_subcomment,NA
+VisualEditor: line height in intro message is wrong causes collusions,"...and in general, steps to reproduce (which site is this about?) are welcome.",1415139729,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-sz7lovyjgkskrmxay2d6,task_subcomment,NA
+VisualEditor: line height in intro message is wrong causes collusions,Local per-wiki templates need to be fixed locally…,1415130154,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sz7lovyjgkskrmxay2d6,task_subcomment,NA
+VisualEditor: featured article template is hidden and easy to accidently delete,"icon not showing in VE
+
+the featured article template added a significant amount of blank headspace to articles and doesn't draw the icon, so it is easy to accidently delete.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14803}",1415128800,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-t4mn4nb76mzz3ahxoggz,task_description,resolved
+VisualEditor: featured article template is hidden and easy to accidently delete,"
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1415129033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t4mn4nb76mzz3ahxoggz,task_subcomment,NA
+VisualEditor: unexpected results while copy/pasting reference contents,"See https://www.mediawiki.org/w/index.php?title=User:Elitre_(WMF)/sandbox&diff=prev&oldid=1249997 .
+
+References at the words ""this"" were created by copy/pasting the contents of the reference at the word ""complex"".
+
+Notice:
+1) The spaces between the elements get removed (Bug 71718?)
+2) The wikilink gets changed;
+3) If you selected until after the ""citation needed"" template only, this wouldn't appear when pasting (Bug 49396?).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415024640,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-altlbz4ow72qgwhpfdya,task_description,resolved
+VisualEditor: unexpected results while copy/pasting reference contents,"(In reply to Elitre from comment #0)
+> See
+> https://www.mediawiki.org/w/index.php?title=User:Elitre_(WMF)/
+> sandbox&diff=prev&oldid=1249997 .
+> 
+> References at the words ""this"" were created by copy/pasting the contents of
+> the reference at the word ""complex"".
+> 
+> Notice:
+> 1) The spaces between the elements get removed (Bug 71718?)
+
+Looks like.
+
+> 2) The wikilink gets changed;
+
+This is bug 70743.
+
+> 3) If you selected until after the ""citation needed"" template only, this
+> wouldn't appear when pasting (Bug 49396?).
+
+That bit works for me?
+
+Merging with bug 71718.
+
+*** This bug has been marked as a duplicate of bug 71718 ***",1415063629,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-altlbz4ow72qgwhpfdya,task_subcomment,NA
+"VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down","Steps to reproduce:
+
+1.Insert a table
+2.Add any focusable node inside content cell like template/image/math function
+3.Place the cursor at the end of the table
+
+Observed Result:
+The page scrolls down to the end of it
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414734360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h3ux7jbm3qrdgpuszex2,task_description,duplicate
+"VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down","Oh *that* outside of the table. Yeah - you're not supposed to put your cursor there...
+
+*** This bug has been marked as a duplicate of bug 71560 ***",1415203500,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-h3ux7jbm3qrdgpuszex2,task_subcomment,NA
+"VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down","Created attachment 17002
+video capture
+
+Still happening for me , See the video capture
+
+**Attached**: {F15093}",1415045420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h3ux7jbm3qrdgpuszex2,task_subcomment,NA
+"VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down",Works for me in Chrome & FF,1415025275,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-h3ux7jbm3qrdgpuszex2,task_subcomment,NA
+"VisualEditor does not display Files, and can not access the local files","**Author:** `lhug`
+
+**Description:**
+Intention:
+Trying to edit a page with linked files on a private wiki. Mainly to test if the Visual Editor functions are usable.
+
+Steps to Reproduce:
+1. Open page with a linked file
+2. click ""edit""
+3. wait and see
+
+Actual Results:  
+The linked file simply disappears and is not visible to the editor. after saving, it is accessible again. Trying to insert media showed no local media.
+
+Expected Results:  
+Picture is editable of course, and at least a list of media to add.
+
+Reproducible: Always
+
+Using vector as skin. Changing skin did not resolve the issue. Wiki is running on a CentOS with self certified SSL. 
+Accessing files that are on the commons is possible, and these are viewable by the editor. Copying the Link properties to other media links does not help, they are still invisible to the editor. Normal Text is editable and media are accessible there. Tried Workarounds found on several pages:
+
+Changing permissions to all-read-true and/or all-read-edit-true did not resolve the issue. (in fact, if I do that, many pictures are not viewable - they are still there and linked, but show broken image)
+Granting the ImageSearch read permissions did not help.
+granting localhost, 127.0.0.1, our url and our IP read permissions did not help.
+2 API-Queries returned expected results (https://dpaste.de/0Adz for ?action=query&prop=imageinfo&iiprop=url|size&iiurlwidth=220&titles=File:Logo.jpg&format=json and ?action=query&prop=imageinfo&iiprop=url|size&titles=File:Logo.jpg&format=json
+
+Locally (on a Ubuntu machine) the pictures are being shown, yet the local media repo is empty to the VE.
+
+We are running parsoid as a service run by root, the log file reports API request failed when trying to edit a page with pictures in it.
+
+The used versions are MediaWiki 1.23.5, VE Snapshot 1.23, nodejs 0.10.30, Parsoid snapshot 1.23
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414670820,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5jsfxjyzrxm3or6trnvk,task_description,invalid
+"VisualEditor does not display Files, and can not access the local files","This bug could not be reproduced and is now three years old, so I'm closing.",1513167417,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-5jsfxjyzrxm3or6trnvk,task_subcomment,NA
+"VisualEditor does not display Files, and can not access the local files","**lhug** wrote:
+
+Parsoid Log w. debug
+
+This is the Parsoid log with debugging info when opening a page with a picture in it. Since I have no idea what exactly is happening in that parsoid service, or when it happens, maybe someone else can tell me what to do with this.
+
+The fails API-request is easily notable
+
+**Attached**: {F14960}",1414674704,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5jsfxjyzrxm3or6trnvk,task_subcomment,NA
+"VisualEditor does not display Files, and can not access the local files","**lhug** wrote:
+
+A direct call of the api query the VE starts shows definite parsing errors.
+https://dpaste.de/8AhK is the result of the API-Query on the live system.
+
+https://dpaste.de/DKwm is the result of the same page on the local system.
+
+Notice the imagelinks in the first link are still in [[]].",1414673006,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5jsfxjyzrxm3or6trnvk,task_subcomment,NA
+Build jsduck through Gruntfile,"VisualEditor build documentation via Grunt [1] and publish via Jenkins.
+One of the benefits of this is you can use a jsduckcatconfig that pulls in documentation from core.
+
+We should do the same.
+
+[1] https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor/f35d577acb57319241ea992a95cb045298662cd8/Gruntfile.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414622580,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-kvh4xexeziejdfpxnqcl,task_description,resolved
+Build jsduck through Gruntfile,"Change 174851 merged by jenkins-bot:
+Run jsduck through grunt
+
+[[https://gerrit.wikimedia.org/r/174851]]",1417427917,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kvh4xexeziejdfpxnqcl,task_subcomment,NA
+Build jsduck through Gruntfile,"Change 174851 had a related patch set uploaded by Bmansurov:
+Run jsduck through grunt
+
+https://gerrit.wikimedia.org/r/174851",1416526479,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kvh4xexeziejdfpxnqcl,task_subcomment,NA
+Build jsduck through Gruntfile,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/w96Isqis",1414622716,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kvh4xexeziejdfpxnqcl,task_subcomment,NA
+VisualEditor Mobile: There is no Preview bar appearing at the top in iOS Safari for tablet and desktop browser while saving the edited content,"screenshot in desktop browser
+
+Steps to reproduce:
+
+1.Open the wikitext editor for any page in en.m.wikipedia.org 
+2.Make some edit
+3.Click on ""Next""
+
+Observed Result:
+
+There is no preview bar appearing at the top of the page indicating it's a preview as it does in iOS safari for iPhone.
+
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14824}",1414619880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rff3kdscndxezxto7luz,task_description,invalid
+VisualEditor Mobile: There is no Preview bar appearing at the top in iOS Safari for tablet and desktop browser while saving the edited content,Duplicate of T76624,1418171147,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-rff3kdscndxezxto7luz,task_subcomment,NA
+VisualEditor Mobile: There is no Preview bar appearing at the top in iOS Safari for tablet and desktop browser while saving the edited content,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/C7zx3kLC",1414620014,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rff3kdscndxezxto7luz,task_subcomment,NA
+VisualEditor Mobile: There is no Preview bar appearing at the top in iOS Safari for tablet and desktop browser while saving the edited content,"Created attachment 16947
+screenshot from iPhone
+
+**Attached**: {F14825}",1414620011,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rff3kdscndxezxto7luz,task_subcomment,NA
+Newly filed bugs with empty description are not accounced on IRC,"Newly filed bugs with empty description are not accounced on IRC. Bug 72705 wasn't pushed to #mediawiki-visualeditor when I filed it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414619700,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-alwvf22pdixzdjmak4za,task_description,resolved
+Newly filed bugs with empty description are not accounced on IRC,"Yeah, Bugzilla doesn't send messages to wikibugs-l, so pywikibugs cannot report anything. See #64836.
+
+*** This bug has been marked as a duplicate of bug 64836 ***",1414620496,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-alwvf22pdixzdjmak4za,task_subcomment,NA
+Issues with icons in alpha. Get fixed so we can move it to beta.,"* CtaDrawer down icon is not centered
+* Switcher in VisualEditor/Wikitext editor
+* Notification icon tiny mw-ui-icon-notification isn't sized correctly – font-size: 1.3em
+* Clicking the notification icon doesn't hide it while the notifications are loading
+* #page-actions .mw-ui-icon:before (the page actions) margin needs to be lowered
+Animation of the watchstar is broken
+* Toggleable (?) elements (Contents, section headings) don't have cursor: pointer
+* Watch star in page actions moves slightly to the left every time you click it
+* Provide SVG versions of all icons which currently only use SVGS
+The watchstar in the search results is tiny
+.mw-ui-icon-arrow-up isn't positioned hard-right when Contents is open
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414539120,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-dikhm6z5abefq6sfybiz,task_description,invalid
+Issues with icons in alpha. Get fixed so we can move it to beta.,I split this into various bugs to be more actionable,1415228819,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-dikhm6z5abefq6sfybiz,task_subcomment,NA
+Issues with icons in alpha. Get fixed so we can move it to beta.,"Also:
+* face icon (logged in vor not logged in) in Special:MobileDiff repeats itself",1414911471,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-dikhm6z5abefq6sfybiz,task_subcomment,NA
+Issues with icons in alpha. Get fixed so we can move it to beta.,"Also 
+* close icon in image overlay repeats itself",1414613484,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-dikhm6z5abefq6sfybiz,task_subcomment,NA
+Issues with icons in alpha. Get fixed so we can move it to beta.,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/Vh51EzgU",1414539310,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dikhm6z5abefq6sfybiz,task_subcomment,NA
+VisualEditor edit summary is not saved,"Example: https://www.mediawiki.org/w/index.php?title=Project%3ASandbox&diff=1242918&oldid=1242833
+
+Summary input: ""Test"". The summary was not saved.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414484940,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-pquqanuuilo2pfgkwyps,task_description,resolved
+VisualEditor edit summary is not saved,"No, sry for delay.",1416062866,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"All patches mentioned in this report were merged or abandoned - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?",1416054282,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169953 merged by jenkins-bot:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169953",1414624795,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169952 merged by MaxSem:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169952",1414624577,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169953 had a related patch set uploaded by MaxSem:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169953",1414624551,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169952 had a related patch set uploaded by MaxSem:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169952",1414624527,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Maybe LD this patch in the next SWAT? The latest wmf branch was created today (without this patch), so Wikipedias will get thid patch in 14 days, which is a long time :/
+
+The edit summary is an important feature to summarize an edit, it's bad, that a users summary message will not be saved and a reviewer maybe think the user doesn't submitted a summary.",1414623408,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169778 merged by jenkins-bot:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169778",1414614516,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169778 had a related patch set uploaded by Bmansurov:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169778",1414610567,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Hmm :/ I tested it again: https://m.mediawiki.org/wiki/Special:MobileDiff/1245793
+
+Used Chrome desktop and stable mode. Clicked the lead section edit, write down some test text and click save. In the ""Summary"" field i insert ""Test submit"" and clicked save. The edit is saved, but not the summary :(",1414605927,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"I'm not able to reproduce. My summary has been saved correctly:
+https://www.mediawiki.org/w/index.php?title=Project%3ASandbox&diff=1245788&oldid=1245681
+
+also this: https://www.mediawiki.org/w/index.php?title=Project%3ASandbox&diff=1245791&oldid=1245788
+
+Can you give me instructions how to reproduce this?",1414605618,PHID-USER-grftjc3ekkyjf6bwlsqi,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/9UaadG2M",1414485010,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+Jenkins: Create and enable MobileFrontend npm test job,"I notice VisualEditor has lots of Grunt magic. If I'm not mistaken the Gruntfile on each merge [1].
+
+Can a similar job be setup on mobile and could I grab one of either Krinkle and Antoine to see what else Mobile can do to get the most out of this Gruntfile?
+
+[1] https://integration.wikimedia.org/ci/job/oojs-ui-npm/1740/console
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1414453200,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_description,resolved
+Jenkins: Create and enable MobileFrontend npm test job,Fixed by @Jdlrobson who added the necessary npm  / package.json entries and crafted the Jenkins jobs.,1416824815,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_subcomment,NA
+Jenkins: Create and enable MobileFrontend npm test job,"Change 174696 had a related patch set uploaded by Krinkle:
+Add mwext-MobileFrontend-npm job
+
+https://gerrit.wikimedia.org/r/174696",1416506232,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_subcomment,NA
+Jenkins: Create and enable MobileFrontend npm test job,"The Gruntfile is created. Is there anything else we need to do? I'm not sure what you mean by ""once its working"" does this mean working locally or working in some other form?",1414532750,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_subcomment,NA
+Jenkins: Create and enable MobileFrontend npm test job,"Creation of Gruntfile is to be done by MF maintainers. Once it's working, let me know and I'll create/enable the job. Or alternatively, submit a patch to integration-config (should be a 2-3 line change) that I'll merge/deploy.",1414523483,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"Email I sent to Yuvi:
+
+tl;dr: grrrit-wm is broken right now, it's not relying messages, and
+when we try and attempt to kill it with qdel, it goes into some error
+state and keeps connecting/quitting.
+
+huh (PiRSquared) thinks he broke it when quieting it in another channel,
+it was down for a while before I came online. He asked if he could
+upgrade the irc node module it was using, so I said sure since he
+already had access...that didn't work, so he reverted it, but it's still
+not working.
+
+I logged into gerrit-to-redis, and based on the log messages it appears
+to be working fine (I also restarted it just in case, and it was working
+fine after the restart)
+
+So yeah...halp?
+
+<http://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-dev/20141026.txt> is
+our log trying to figure stuff out.
+
+---
+
+Second email:
+
+To stop spam, we moved the config.yaml to ""config_moved-cuz-bug"" so it
+would stop joining. It also finally died from qstat.
+
+At this point I'm not going to touch it until you or someone else has
+time to debug it...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414294380,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-z6jywipl5zqujo3htvlq,task_description,resolved
+grrrit-wm: runs into infinite loop if unable to join channels,I think this should be fixed now in https://github.com/martynsmith/node-irc/pull/187,1478251444,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,Leaving this open as the actual bot still needs fixing...,1414382570,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"**gerritadmin** wrote:
+
+Change 168927 merged by jenkins-bot:
+Bug 72523: Remove #wikimedia-growth
+
+https://gerrit.wikimedia.org/r/168927",1414381762,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"**gerritadmin** wrote:
+
+Change 168927 had a related patch set uploaded by Legoktm:
+Bug 72523: Remove #wikimedia-growth
+
+https://gerrit.wikimedia.org/r/168927",1414381729,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"Thanks, Merlijn!",1414376996,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"I can't get the patch in from tools and the patch uploader has memory issues, so here's the patch:
+
+commit 419e36d490f14d623633e79cf54dc46bb15dbd94
+Author: Merlijn van Deen <valhallasw@gmail.com>
+Date:   Sun Oct 26 20:23:16 2014 +0000
+
+    Bug 72523: Remove #wikimedia-growth
+
+diff --git a/config.yaml b/config.yaml
+index 01797e0..adb052d 100644
+--- a/config.yaml
++++ b/config.yaml
+@@ -126,10 +126,6 @@ channels:
+         ""mediawiki/extensions/ValueView"",
+         ""mediawiki/extensions/Capiunto""
+         }
+-    ""#wikimedia-growth"": {
+-        ""mediawiki/extensions/GuidedTour"",
+-        ""mediawiki/extensions/GettingStarted""
+-        }
+     ""#wikimedia-multimedia"": {
+         ""mediawiki/extensions/CommonsMetadata.*"",
+         ""mediawiki/extensions/MultimediaViewer.*"",",1414355628,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"So there were two issues currently:
+
+1) gerrit-to-redis was not running. From https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.gerrit-to-redis/SAL :
+19:46 valhallasw: grrrit-wm still not reporting anything; checking redis stream
+19:50 valhallasw: gerrit-to-redis reconnects to gerrit every two hours, but does not push to clients (last 'pushed to 1 clients' message was 26-10-2014 04:00:41,241)
+19:51 valhallasw: and gerrit-to-redis does not seem to be running ATM - qstat is empty
+19:53 valhallasw: job resubmitted; now running on continuous@tools-exec-10; SSH and redis connections are open
+19:57 valhallasw: ""2014-10-26 19:56:30,333 Pushed to 1 clients""
+
+2) grrrit-wm could not join #wikimedia-growth, and does not handle that correctly:
+https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lolrrit-wm/SAL
+
+20:02 valhallasw: 2014-10-26T20:01:00.911Z - error: prefix=hitchcock.freenode.net, server=hitchcock.freenode.net, command=err_channelisfull, rawCommand=471, commandType=error, args=[grrrit-wm1, #wikimedia-growth, Cannot join channel (+l) - channel is full, try again later]
+20:02 valhallasw: but I'm not sure if thta's the actual cause...
+20:11 valhallasw: kicked #wikimedia-growth from the config, let's see if that helps
+20:15 valhallasw: judging from the log, that seems to have been the issue indeed
+
+
+The following is in the log:
+
+2014-10-26T02:51:40.222Z - info: joining channels 0=#mediawiki-i18n, 1=#mediawiki-parsoid, 2=#mediawiki-visualeditor, 3=#pywikibot, 4=#semantic-mediawiki, 5=#wikimedia-analytics, 6=#wikimedia-dev, 7=#wikimedia-fundraising, 8=#wikimedia-corefeatures, 9=#wikimedia-labs, 10=#wikimedia-mobile, 11=#wikimedia-operations, 12=#wikimedia-qa, 13=#wikidata, 14=#wikimedia-growth, 15=#wikimedia-multimedia, 16=#wikipedia-en-ambassadors, 17=#wmt, 18=#brickimedia, 19=#mediawiki-feed
+2014-10-26T02:51:49.403Z - info: Joined channel #mediawiki-i18n
+(...)
+2014-10-26T02:51:58.412Z - error:  prefix=wilhelm.freenode.net, server=wilhelm.freenode.net, command=err_channelisfull, rawCommand=471, commandType=error, args=[grrrit-wm, #wikimedia-growth, Cannot join channel (+l) - channel is full, try again later]
+2014-10-26T02:51:59.411Z - info: Joined channel #wikimedia-multimedia
+(...)
+2014-10-26T02:52:03.426Z - info: Joined channel #mediawiki-feed
+2014-10-26T02:53:52.211Z - info: joining channels 0=#mediawiki-i18n, 1=#mediawiki-parsoid, 2=#mediawiki-visualeditor, 3=#pywikibot, 4=#semantic-mediawiki, 5=#wikimedia-analytics, 6=#wikimedia-dev, 7=#wikimedia-fundraising, 8=#wikimedia-corefeatures, 9=#wikimedia-labs, 10=#wikimedia-mobile, 11=#wikimedia-operations, 12=#wikimedia-qa, 13=#wikidata, 14=#wikimedia-growth, 15=#wikimedia-multimedia, 16=#wikipedia-en-ambassadors, 17=#wmt, 18=#brickimedia, 19=#mediawiki-feed
+(repeats)
+
+
+After kicking #wikimedia-growth out:
+
+2014-10-26T20:12:23.103Z - info: joining channels 0=#mediawiki-i18n, 1=#mediawiki-parsoid, 2=#mediawiki-visualeditor, 3=#pywikibot, 4=#semantic-mediawiki, 5=#wikimedia-analytics, 6=#wikimedia-dev, 7=#wikimedia-fundraising, 8=#wikimedia-corefeatures, 9=#wikimedia-labs, 10=#wikimedia-mobile, 11=#wikimedia-operations, 12=#wikimedia-qa, 13=#wikidata, 14=#wikimedia-multimedia, 15=#wikipedia-en-ambassadors, 16=#wmt, 17=#brickimedia, 18=#mediawiki-feed
+2014-10-26T20:12:32.315Z - info: Joined channel #mediawiki-i18n
+(..)
+2014-10-26T20:12:45.365Z - info: Joined channel #mediawiki-feed
+2014-10-26T20:12:45.366Z - info: Joined 19 channels. Starting relay
+2014-10-26T20:12:51.784Z - info: Sent message from apps/android/wikipedia to #wikimedia-mobile
+
+
+
+
+So, instead of retrying to join *all* channels when one fails, the bot should rather set up the relay for the joined channels, and try re-joining the failed channels.",1414354875,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"I reverted the config.yaml move and the bot is now connected to freenode and seems stable. The stream seems broken, though.",1414297374,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+VisualEditor:Link inspector opens with an animation from top while trying to open it for the first time in an edit session,"video capture
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.click on link inspector icon 
+
+Observed Result:
+Link inspector opens with an animation from top
+
+See the video capture attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14920}",1414184760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u34r5p3uaxlfwzfdw4om,task_description,resolved
+VisualEditor:Link inspector opens with an animation from top while trying to open it for the first time in an edit session,This is no longer happening.,1421864811,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-u34r5p3uaxlfwzfdw4om,task_subcomment,NA
+VisualEditor:Link inspector opens with an animation from top while trying to open it for the first time in an edit session,There's an animation?,1421803269,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-u34r5p3uaxlfwzfdw4om,task_subcomment,NA
+VisualEditor:Link inspector opens with an animation from top while trying to open it for the first time in an edit session,Can't reproduce.,1419350022,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-u34r5p3uaxlfwzfdw4om,task_subcomment,NA
+Get Grunt setup in MobileFrontend,"VisualEditor team is using a grunt file. Flow have also moved to one of these.
+
+One of the benefits of the Gruntfile is Jenkins will run `grunt test` on every commit meaning we can get Jenkins automating quite a few things for us.
+
+MobileFrontend should also use it.
+
+One of the benefits of this will be jscs running on every Jenkins build (currently this only runs in a pre commit hook)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414090680,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-srlf3r7iawflrql5il7l,task_description,resolved
+Get Grunt setup in MobileFrontend,"Change: https://gerrit.wikimedia.org/r/#/c/168656/
+
+Merged.",1416103527,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-srlf3r7iawflrql5il7l,task_subcomment,NA
+Get Grunt setup in MobileFrontend,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/ecXDbChX",1414090828,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-srlf3r7iawflrql5il7l,task_subcomment,NA
+At nowiki the nowiki-tag shows up in some edits done with VisualEditor,"It seems like nowiki-tags show up at edits done at nowiki with VisualEditor.
+
+The first of the two examples (https://no.wikipedia.org/w/index.php?title=Cologne_Business_School&diff=13473599&oldid=13473538) could be a copy-paste. If so it is an user error and the same as in Bug 68928 VisualEditor: Copy/pasting causes <nowiki> and <em> tags to appear.
+
+The second edit seems to be different (https://no.wikipedia.org/w/index.php?title=Bergen&diff=prev&oldid=13467156) and I'm not sure what has happened here. Perhaps it is Bug 49820 - VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor. If this is the case the user has clicked through a warning (has it failed?) and still saved.
+
+There is a thread at nowiki about this, https://no.wikipedia.org/wiki/Wikipedia:Torget#Tomme_nowiki-tagger (""Empty nowiki-tags"")
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414090140,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-o6yfcomtzmhncilri75a,task_description,declined
+At nowiki the nowiki-tag shows up in some edits done with VisualEditor,"@Elitre is correct that the two bugs look like they are due to pasting wikitext into a place where wikitext doesn't work. Given the changes since then, this is unlikely to be as much of an issue, but we really can't stop users from doing the wrong thing in all occasions.",1421377390,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o6yfcomtzmhncilri75a,task_subcomment,NA
+At nowiki the nowiki-tag shows up in some edits done with VisualEditor,This should perhaps be a feature request as it seems to be about additional warning messages.,1414374118,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-o6yfcomtzmhncilri75a,task_subcomment,NA
+At nowiki the nowiki-tag shows up in some edits done with VisualEditor,"Allow me to underline the irony of a nowiki at no.wiki :D
+
+I don't think the first case is related to that bug - that simply looks like wikicode copy/pasted in a VE instance, that's why the nowiki tags are generated.
+
+The second case looks more like a confused attempt to edit a wikilink, similar to [[bug 70286]].
+
+As for wikitext warnings, those do exist, but I don't know if they're currently working (I filed a bug about that today) or if they're supposed to work when you copy/paste (not type) wikicode. I'd argue this should be possibile, since this is not the first time we see copy/pasting confusion.",1414156632,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-o6yfcomtzmhncilri75a,task_subcomment,NA
+"VisualEditor Mobile: Misaligned ""Cancel"" and ""Ok"" button in the confirmation dialogs for abandoning edit and switching to Edit Source mode","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE using desktop Safari
+2.Edit something on the page, click on the back button at the top left corner and observe the alignment of ""Ok"" and ""Cancel"" button in the confirmation dialog for abandoning edit
+3.Click cancel and now click on the button to switch to the edit source mode from the Settings menu
+
+4.Observe the alignment of ""Ok"" and ""Cancel"" button in the confirmation dialog for switching to edit source mode
+
+Observed Result:
+The buttons are misaligned as seen in the screenshot attached
+
+Environment:
+Betalabs, test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14709}",1414022820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2tym47dhhlsomwrn7ywj,task_description,invalid
+"VisualEditor Mobile: Misaligned ""Cancel"" and ""Ok"" button in the confirmation dialogs for abandoning edit and switching to Edit Source mode",Going with the latter for now.,1415070112,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2tym47dhhlsomwrn7ywj,task_subcomment,NA
+"VisualEditor Mobile: Misaligned ""Cancel"" and ""Ok"" button in the confirmation dialogs for abandoning edit and switching to Edit Source mode","These are native confirm dialogs, so this bug is upstream or invalid...",1415068013,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2tym47dhhlsomwrn7ywj,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","While some templates are easy to use in VE, this is not. At first VE doesnt load automatically its parameters, at second you need to enter hyperling to its values, but VE doesnt offer tools for that.
+
+Its often used template which gives information, about subjects with the same title.
+
+https://cs.wikipedia.org/wiki/%C5%A0ablona:Mo%C5%BEn%C3%A1_hled%C3%A1te
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413870600,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-ytvabqehjgq7vzt7rym4,task_description,invalid
+"""Možná hledáte"" template on cs.wp not easy to use with VE",That's tracked as bug 52581.,1414347550,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","(In reply to Alex Monk from comment #4)
+> How would VE grab a list of parameters without there being TemplateData...?
+
+Thats a question for you. I am not a specialist, I dont know.",1414343819,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE",How would VE grab a list of parameters without there being TemplateData...?,1414336556,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","Andre: I dont think so.
+
+Elitre: I thought VE grabs it even there is no TD.",1414336318,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","I don't think so. It seems to me this template lacks TemplateData information (https://www.mediawiki.org/wiki/Help:TemplateData ). That's easier to add now (see my announcement at https://cs.wikipedia.org/wiki/Diskuse_k_Wikipedii:VisualEditor/TemplateData ).
+At the moment, you need to use wikimarkup inside templates' fields, so you can use double square brackets to make links.
+If you need further help, please feel free to reach me at your wiki.",1413880860,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","(In reply to Juan de Vojníkov from comment #0)
+> At first VE doesnt load automatically its parameters
+
+Is that bug 69734?",1413877541,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+VisualEditor:  Some links to URLs are being displayed as red,"This may only be happening to links inside templates or refs.  
+
+Steps to reproduce:
+
+1.  Click on https://en.wikipedia.org/wiki/HOSxP?veaction=edit
+
+2.  Watch the URL in the infobox turn red.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413849660,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gbdas2p32dgcym35jznx,task_description,resolved
+VisualEditor:  Some links to URLs are being displayed as red,"
+
+*** This bug has been marked as a duplicate of bug 72251 ***",1413849744,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gbdas2p32dgcym35jznx,task_subcomment,NA
+ext.eventLogging.subscriber.js broken,"File: https://github.com/wikimedia/mediawiki-extensions-EventLogging/blob/master/modules/ext.eventLogging.subscriber.js
+
+
+The ext.eventLogging.subscriber.js has not worked since past April. Visual Editor editor was using it to submit its events to EL. 
+
+While VE is removing usage of this class (as it really not needed on their case) we should either fix it or remove other usages of it. Sounds like its only usage on the codebase (besides Visual Editor's) is to report usage of deprecated javascript functions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413581220,PHID-USER-mwkkwzbzlkvdl4w2og44,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_description,resolved
+ext.eventLogging.subscriber.js broken,"Change 167326 merged by jenkins-bot:
+Fix off-by-one error in mw.track subscriber
+
+https://gerrit.wikimedia.org/r/167326",1414548076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_subcomment,NA
+ext.eventLogging.subscriber.js broken,"(In reply to Roan Kattouw from comment #1)
+> Specifically, what's broken is the way that it tries to derive the schema
+> from the topic name. The things that are broken about it are:
+> 
+> * It ends up trying to load schema..foo (double dot)
+My patch fixes this.
+
+> * It documents that the topic must start with 'event.', and tries to strip
+> that (leaving the dot), but none of the callers actually pass 'event.'
+This seems to be deliberate, because it only listens for events that start with 'event'. My patch changes this to 'event.' so we don't capture random other stuff.
+
+> * If the schema is not found (which due to the bugs above is virtually
+> always the case), it fails silently with no warning logged anywhere
+> 
+This doesn't seem to be true: ResourceLoader does log an error about not being able to find a module called schema..foo
+
+> It's been suggested that subscriber.js (and mw.track(), which it
+> facilitates) just needs to be put out of its misery. VisualEditor is using
+> it, but there's no good reason for that and I'm porting it to call
+> EventLogging directly. However, a few things in MediaWiki are using
+> mw.track(), and some of them would benefit from deferred loading (they may
+> call mw.track() very early, before EventLogging has been loaded), so those
+> would have to be looked at.
+
+Right now Dan is suggesting we just keep it around.",1413583515,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_subcomment,NA
+ext.eventLogging.subscriber.js broken,"Change 167326 had a related patch set uploaded by Catrope:
+Fix off-by-one error in mw.track subscriber
+
+https://gerrit.wikimedia.org/r/167326",1413583341,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_subcomment,NA
+ext.eventLogging.subscriber.js broken,"Specifically, what's broken is the way that it tries to derive the schema from the topic name. The things that are broken about it are:
+
+* It ends up trying to load schema..foo (double dot)
+* It documents that the topic must start with 'event.', and tries to strip that (leaving the dot), but none of the callers actually pass 'event.'
+* If the schema is not found (which due to the bugs above is virtually always the case), it fails silently with no warning logged anywhere
+
+It's been suggested that subscriber.js (and mw.track(), which it facilitates) just needs to be put out of its misery. VisualEditor is using it, but there's no good reason for that and I'm porting it to call EventLogging directly. However, a few things in MediaWiki are using mw.track(), and some of them would benefit from deferred loading (they may call mw.track() very early, before EventLogging has been loaded), so those would have to be looked at.",1413581625,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_subcomment,NA
+VE instrumentation is not showing up in databases,"VE has a variety of schemas[1] that are not correctly feeding into the EL databases. They need assistance in figuring out what's happening.
+
+Dario suspects that the events are failing validation.
+
+[1] https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=VisualEditor&fulltext=Search&ns470=1&profile=advanced
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413517140,PHID-USER-ud7f5gp5h3uqup6viq4e,PHID-TASK-xzgjkfv633ag6fmt7rky,task_description,resolved
+VE instrumentation is not showing up in databases,"Edit team has a dashboard that is fed data from the DB, so everything seems ok from our point of view: http://edit-reportcard.wmflabs.org/",1421079666,PHID-USER-vbyvvtbztxaeuaxelxx4,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VE instrumentation is not showing up in databases,Roan.. can you clarify a bit your last comment? me no comprendo.,1413591244,PHID-USER-mwkkwzbzlkvdl4w2og44,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VE instrumentation is not showing up in databases,"(In reply to Roan Kattouw from comment #2)
+> Turns out EventLogging's mw.track subscriber is broken, and VisualEditor was
+> using it for no good reason. I'll port VE to use EL directly, but there are
+> other uses of mw.track and those are probably broken too:
+> 
+> resources/lib/jquery/jquery.migrate.js:65:mw.track( ""jquery.migrate"", key ||
+> ""unknown"" );
+> resources/src/mediawiki/mediawiki.js:567:mw.track( 'mw.deprecate', key );
+> resources/src/mediawiki/mediawiki.js:572:mw.track( 'mw.deprecate', key );
+
+ACTUALLY... the WikimediaEvents extension includes subscribers for both ve.* events and for these two. So they DO end up in EventLogging, just not via EventLogging's subscriber. It looks like nothing is just EventLogging's subscriber, which only subscribes to things starting with 'event.*'
+
+The schemas used by WikimediaEvents are:
+ve.* --> Schema:TimingData
+jquery.migrate --> Schema:JQMigrateUsage
+mw.deprecate --> Schema:DeprecatedUsage",1413589327,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VE instrumentation is not showing up in databases,"Turns out EventLogging's mw.track subscriber is broken, and VisualEditor was using it for no good reason. I'll port VE to use EL directly, but there are other uses of mw.track and those are probably broken too:
+
+resources/lib/jquery/jquery.migrate.js:65:mw.track( ""jquery.migrate"", key || ""unknown"" );
+resources/src/mediawiki/mediawiki.js:567:mw.track( 'mw.deprecate', key );
+resources/src/mediawiki/mediawiki.js:572:mw.track( 'mw.deprecate', key );",1413581032,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VE instrumentation is not showing up in databases,"No new events are coming in for schemas like VisualEditor%:
+
+zsub vanadium.eqiad.wmnet:8600 | grep '""schema"": ""VisualEditor'
+
+But at least two of the events used to validate at some point at the end of 2013, beginning of 2014:
+
+mysql:research@analytics-store.eqiad.wmnet [log]> select min(timestamp), max(timestamp) from VisualEditorDOMSaved_6063754;
++----------------+----------------+
+| min(timestamp) | max(timestamp) |
++----------------+----------------+
+| 20131016202600 | 20131121114538 |
++----------------+----------------+
+1 row in set (0.00 sec)
+
+mysql:research@analytics-store.eqiad.wmnet [log]> select min(timestamp), max(timestamp) from VisualEditorDOMRetrieved_5961496;
++----------------+----------------+
+| min(timestamp) | max(timestamp) |
++----------------+----------------+
+| 20131010222635 | 20140128212543 |
++----------------+----------------+
+1 row in set (0.00 sec)
+
+The most likely explanation is that the events are no longer emitted, as we don't see them in the raw stream.  So, in short, look around 20131121114538 and 20140128212543 to see what changed in your instrumentation.  We're setting up a meeting to discuss further, but feel free to comment here too.",1413565037,PHID-USER-vbyvvtbztxaeuaxelxx4,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VisualEditor: Moving the cursor with keyboard over a footnote number goes back and forth,"1. Go to https://www.mediawiki.org/w/index.php?title=Manual:Coding_conventions/Ruby&redirect=no&veaction=edit (revision: https://www.mediawiki.org/w/index.php?title=Manual:Coding_conventions/Ruby&oldid=1226556 )
+
+2. Put the caret at the end of the second paragraph after ""staff"".
+
+3. Move the caret forward with the keyboard using the ""right arrow"" key repeatedly
+
+Expected: The caret must move forward through the three footnote numbers.
+
+Observed: The caret moves to the first reference and then back before it.
+
+This is similar to bug T73550.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413473340,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-3elt5ys3qqz7nivrswhi,task_description,resolved
+VisualEditor: Moving the cursor with keyboard over a footnote number goes back and forth,Works for me now. Wish we could confirm when we'd fixed this. :-(,1423676182,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3elt5ys3qqz7nivrswhi,task_subcomment,NA
+VisualEditor[Regression wmf3]:Category context menu appears out of position.,"screenshot
+
+Environment- test2, beta
+
+1> Add a new category say- Japan.
+2> select the category to delete it. Notice the context menu appears out of position.
+
+see screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F15006}",1413215220,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-apuow26xcvt52fvqwwvs,task_description,resolved
+VisualEditor[Regression wmf3]:Category context menu appears out of position.,"
+
+*** This bug has been marked as a duplicate of bug 72052 ***",1413817416,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-apuow26xcvt52fvqwwvs,task_subcomment,NA
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.","Environment- test2
+
+1> In VE enter external link e.g- http://lowes.com . Save the page. Takes you to Read mode.
+2> Select Edit tab again and Edit the external link to google.com. Save the page.
+3> In the Read mode click on the external link to open the page. Navigates to google page. Now click on the back browser button. You would expect this to navigate you to the most recently saved page in VE , but click on the link and it opens lowes page . 
+4> Now click on Edit tab and it would show google.com as the link.
+
+
+Page in VE with lowes.com ->edit and saved the page with google.com -> google.com(current page)
+                                                                            
+                                                                                                                                                  
+                                                                                                                                                                                                                                                                                            
+Hit the back button.
+
+Page in VE with lowes.com(takes me here)  -> edit and saved the page with google.com (should have navigated here)-> google.com
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1412959980,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-6k2emu2psnugqtpitixd,task_description,resolved
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.",Re-checked it in test2 and betalabs - seems to be working fine.,1415387271,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-6k2emu2psnugqtpitixd,task_subcomment,NA
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.","(In reply to Ritu Swain from comment #2)
+> (In reply to James Forrester from comment #1)
+> > I can't reproduce this; can you confirm it's still an issue? (Test
+> > environment: Beta Labs, Chrome 38, Mac OS X 10.10)
+> 
+> I cannot reproduce it anymore in test2 or beta.
+
+OK, marking as FIXED though I know not how.",1414104706,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6k2emu2psnugqtpitixd,task_subcomment,NA
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.","(In reply to James Forrester from comment #1)
+> I can't reproduce this; can you confirm it's still an issue? (Test
+> environment: Beta Labs, Chrome 38, Mac OS X 10.10)
+
+I cannot reproduce it anymore in test2 or beta.",1414041545,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-6k2emu2psnugqtpitixd,task_subcomment,NA
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.","I can't reproduce this; can you confirm it's still an issue? (Test environment: Beta Labs, Chrome 38, Mac OS X 10.10)",1414008818,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6k2emu2psnugqtpitixd,task_subcomment,NA
+VisualEditor: Annotations pull-down closes before scrolling it.,"Environment- test2, beta
+
+In the Reference dialog and Media Settings Caption dialog, before even  I could scroll down the Annotations menu list and select the Language tool or Clear styling,  the pull-down closes, making it difficult to  apply them to existing content.
+
+
+Environment-test2 only
+
+Similarly, in the Transclusion dialog -> Add a Template field, when you start typing and the suggestion list is shown, before you could scroll the list, it closes, making it unusable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP",1412775960,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ajcga6hkx4kdoeksqocl,task_description,resolved
+VisualEditor: Annotations pull-down closes before scrolling it.,"Merging into bug 65774.
+
+*** This bug has been marked as a duplicate of bug 65774 ***",1415807863,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ajcga6hkx4kdoeksqocl,task_subcomment,NA
+VisualEditor: Wikilinks with a final space,"This bug has been observed for a while on fr.wp and thus unofficially reported time ago, but now User:Drongou has kindly provided instructions to replicate it, so:
+
+1) Copy/paste something between square brackets, say [[2013]]
+2) Place the cursor before the 3 and type 4, so that it becomes [[20143]]
+3) Type a space, so it now looks like [[2014 3]]
+4) Remove the 3 and save.
+ 
+The result will be <nowiki>[[2014 ]]</nowiki>.
+Confirmed at least on Safari 7.1, Mac OS-X 10.9 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412365620,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-amkdzmp26p5hbs2ljuus,task_description,resolved
+VisualEditor: Wikilinks with a final space,"This is already covered in bug 52037 – it's really messy, yeah.
+
+*** This bug has been marked as a duplicate of bug 52037 ***",1412365997,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-amkdzmp26p5hbs2ljuus,task_subcomment,NA
+VisualEditor switcher isn't visible,"Switcher icon not visible
+
+In EditorOverlay the icon for the editor switcher (VE or Source) isn't visible (see attachment). You can still click/tap on the position and you can switch, but nobody know, that the switcher is there.
+
+Reported first on https://www.mediawiki.org/wiki/Thread:Extension_talk:MobileFrontend/visualeditor_abandoned
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15397}",1412337840,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-nnnzye23nj6ys3ykaygo,task_description,resolved
+VisualEditor switcher isn't visible,Working now :),1412361115,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164584 merged by jenkins-bot:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164584",1412359552,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164587 merged by jenkins-bot:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164587",1412359548,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164543 merged by jenkins-bot:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164543",1412358084,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164587 had a related patch set uploaded by Florianschmidtwelzow:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164587",1412357897,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164584 had a related patch set uploaded by Florianschmidtwelzow:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164584",1412357781,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164543 had a related patch set uploaded by Florianschmidtwelzow:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164543",1412339180,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/799d4SR5",1412337917,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"The author of this revision https://fr.wikipedia.org/w/index.php?title=La_Grange_au_Lac&diff=107837547&oldid=107804115 realizes that the wikicode he copy/pasted was not valid. The question is, does VE really need 5 nowiki tags to inform us? Can there be a good way of warning the user, maybe one which at the same time allows unexperienced editors to avoid saving and fix that mess?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412014620,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gcgx64v3je25kov2xxdy,task_description,resolved
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"Yes, T73426.",1430414002,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,">>! In T73422#754038, @Elitre wrote:
+> I'll file a bug against Parsoid, thanks.
+
+Any ticket ID handy?",1423702692,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"It could also be a warning just like those for ""Comments"", with a different icon and/or color. This plus a warning on save, indicating the line, suggesting to ""switch to source editing"" and correct it directly in the code ?
+But this won't be efficient if the user doesn't know the wikicode.",1412288331,PHID-USER-4cgt73x34j35pnbem65l,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"I'll file a bug against Parsoid, thanks.
+Could we expose the specific issue, like, telling at which line it is and highlighting it? I realize pointing at code is not a great idea in a visual editor.",1412015341,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"Maybe we could have an additional warning on save, like we do for suspected page corruption?",1412014905,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"There is already a warning that appears in the top right corner. Maybe that warning could be made better?
+
+The number of nowiki tags there is a bit excessive; that's a bug in Parsoid.",1412014882,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Letters getting added and duplicated on pages featuring chess templates,"See https://de.wikipedia.org/wiki/Benutzer:Elitre_(WMF)/sandbox?veaction=edit .
+Place your cursor after the last period of any section, and start typing. 
+The first letter of your word will get added to the beginning of the following line.
+Hit Backspace; now the whole word appears there.
+Verified also on en.wp on the Chess article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51932",1411981620,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-zuvvxfljo3m4uvk2s3ea,task_description,declined
+VisualEditor: Letters getting added and duplicated on pages featuring chess templates,Please reopen if you manage to reproduce this issue again.,1416182820,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-zuvvxfljo3m4uvk2s3ea,task_subcomment,NA
+VisualEditor: Letters getting added and duplicated on pages featuring chess templates,Is this still occuring? I can't reproduce the issue...,1414802369,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-zuvvxfljo3m4uvk2s3ea,task_subcomment,NA
+"VisualEditor: In Firefox ""TypeError: this.$documentNode is undefined"" appears while selecting a citation note for a second time but not consecutively","Screenshot
+
+Steps to reproduce:
+
+1.Insert 3 citation notes next to a text
+2.Now select the 3rd one
+3.Select the second one and edit it
+4.Select the first one and edit it
+5.Again select the 3rd one to edit it
+
+
+Observed Result:
+""TypeError: this.$documentNode is undefined"" appears in the console.
+
+See the screenshot attached.
+
+This happens in Firefox only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14758}",1411774380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ohb2gmeqf4uqlyoctr2o,task_description,resolved
+"VisualEditor: In Firefox ""TypeError: this.$documentNode is undefined"" appears while selecting a citation note for a second time but not consecutively",The error is not displayed anymore. ,1424134417,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ohb2gmeqf4uqlyoctr2o,task_subcomment,NA
+"VisualEditor:The ""Use this group"" drop down box is getting cut off in Basic Reference dialog","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Cite>Basic 
+3.Open the drop down box for ""Use this group""
+
+
+Observed Result:
+The drop down box appears very small 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14754}",1411772520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-g4ont2tuuoxetvha3ayd,task_description,resolved
+"VisualEditor:The ""Use this group"" drop down box is getting cut off in Basic Reference dialog","Sorry ,it is a duplicate, I could not find this bug in BZ, so reported it.",1411772893,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-g4ont2tuuoxetvha3ayd,task_subcomment,NA
+"VisualEditor:The ""Use this group"" drop down box is getting cut off in Basic Reference dialog","Sorry ,it is a duplicate, I could not find this bug in BZ, so reported it.
+
+*** This bug has been marked as a duplicate of bug 71178 ***",1411772879,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-g4ont2tuuoxetvha3ayd,task_subcomment,NA
+Visual editor screenshot job fails,"Most of the language jobs fail with the same errors. This is example for cs[1]. The parent job is [2].
+
+...
+00:18:18.444 Failing Scenarios:
+00:18:18.444 cucumber features/language_screenshot.feature:42 # Scenario: VisualEditor_Page_Settings
+00:18:18.444 cucumber features/language_screenshot.feature:142 # Scenario: VisualEditor_cancel_save
+...
+
+1: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox/LANGUAGE_SCREENSHOT_CODE=cs,label=contintLabsSlave%20&&%20UbuntuPrecise/5/console
+2: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1411650900,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_description,resolved
+Visual editor screenshot job fails,Looks like the problem is fixed by the above commit. Please reopen the bug if something is still failing.,1412082716,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+Visual editor screenshot job fails,"Change 163185 merged by jenkins-bot:
+[BrowserTest] Fixed failing language screenshot scenarios
+
+https://gerrit.wikimedia.org/r/163185",1411754440,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+Visual editor screenshot job fails,"Change 163185 had a related patch set uploaded by Jforrester:
+[BrowserTest] Fixed failing language screenshot scenarios
+
+https://gerrit.wikimedia.org/r/163185",1411753767,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+Visual editor screenshot job fails,"Change 162879 merged by jenkins-bot:
+[BrowserTest] Disable screenshots for broken scenarios
+
+https://gerrit.wikimedia.org/r/162879",1411651353,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+Visual editor screenshot job fails,"Change 162879 had a related patch set uploaded by Zfilipin:
+[BrowserTest] Disable screenshots for broken scenarios
+
+https://gerrit.wikimedia.org/r/162879",1411651132,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+remove messages for features that aren't going to be developed,"Some features of WikiEditor probably aren't going to be developed much in the future. One such feature that I noticed is ""Side by side preview"". (I might actually be wrong, and this feature may be in development.)
+
+If these features will no be developed further, the messages for them should be removed, because currently translators' time is wasted on them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411637940,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_description,resolved
+remove messages for features that aren't going to be developed,"All messages of modules that aren't actually in use (either at WMF or externally) have been removed.
+
+Publish and side-by-side preview have remained.",1426443107,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,"The following patch removes previewDialog, since it probably isn't used anywhere anyways.
+https://gerrit.wikimedia.org/r/#/c/176512/",1417375699,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,">>! In T73287#795508, @TheDJ wrote:
+> side by side (aka preview), is a mode where you can switch between 3 tabs (source, preview, diff) that have live preview features
+Now //THAT// sounds like something Wikisource, Wikibooks, & the like could really use.. and even build upon -- //but I know better than to get my hopes up by now though//.
+
+If the consensus is better to trim it out, then I'd be OK with that too. 
+
+> previewDialog, even I don't know about ...(probably because it's disabled for everyone, incl fresh installs).
+If we follow the existing premise, its safe to say its going to do the same thing as 'preview' does using tabs hinged to the basic WikiEditor but with a MediaViewer-ish type of floating window/interface instead. //yawn// I see no point in pursuing something like that.",1417375664,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,"side by side (aka preview), is a mode where you can switch between 3 tabs (source, preview, diff) that have live preview features
+
+Publish gives you a dialog that basically replaces the summary and copyright disclaimer that is below the edit screen.
+
+Both have some users outside of Wikimedia, I know from bugreports that have been filed over the past few years.
+
+previewDialog, even I don't know about ...(probably because it's disabled for everyone, incl fresh installs).",1417374258,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,"Most of the ""original"" modules like 'toc', 'highlight' & 'templateEditor' are already gone. Not sure what ""Side-by-side preview"" is; I've never come across anything like that. But if you go by a current mock-up of features...
+```
+lang=php, name=mock $wgWikiEditorFeatures, lines=4, counterexample
+
+// Each module may be configured individually to be globally on/off or user preference based
+$GLOBALS['wgWikiEditorFeatures'] = array( 
+
+	/* Textarea / i-frame compatible (OK to deploy) */
+
+	// Enhanced toolbar
+	'toolbar' => array( 'global' => false, 'user' => true ),
+	// Provides interactive tools using dialogs
+	'dialogs' => array( 'global' => false, 'user' => true ),
+	// Hide signature button from main namespace
+	'hidesig' => array( 'global' => true, 'user' => false ), 
+
+	/* Textarea / i-frame compatible, but still experimental and unstable (do not deploy!) */
+
+	// Adds a tab for previewing in-line
+	'preview' => array( 'global' => false, 'user' => true ),
+	// Adds a button for previewing in a dialog
+	'previewDialog' => array( 'global' => false, 'user' => false ),
+	//  Adds a button and dialog for step-by-step publishing
+	'publish' => array( 'global' => false, 'user' => true ),
+
+); 
+```
+... the only thing I can guess that might be is the in-line (or live?) preview module. I've never seen 'publish' at work or heard anything about it either. And of course, hideSig is still in effect though it hasn't ""worked"" for months now.
+
+That said, I can go along with removing the ""abandoned"" feature bits - unless somebody knows better. The focus is on developing VisualEditor as far as I can tell anyway. I just hope they keep something like WikiEditor around for the non-Wikipedia types of projects.
+
+",1417373821,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,"Most of the ""original"" modules like 'toc', 'highlight' & 'templateEditor' are already gone. Not sure what ""Side-by-side preview"" is; I've never come across anything like that. But if you go by a current mock-up of features...
+```
+lang=php, name=mock $wgEditorFeatures, lines=4, counterexample
+
+// Each module may be configured individually to be globally on/off or user preference based
+$GLOBALS['wgWikiEditorFeatures'] = array( 
+
+	/* Textarea / i-frame compatible (OK to deploy) */
+
+	// Enhanced toolbar
+	'toolbar' => array( 'global' => false, 'user' => true ),
+	// Provides interactive tools using dialogs
+	'dialogs' => array( 'global' => false, 'user' => true ),
+	// Hide signature button from main namespace
+	'hidesig' => array( 'global' => true, 'user' => false ), 
+
+	/* Textarea / i-frame compatible, but still experimental and unstable (do not deploy!) */
+
+	// Adds a tab for previewing in-line
+	'preview' => array( 'global' => false, 'user' => true ),
+	// Adds a button for previewing in a dialog
+	'previewDialog' => array( 'global' => false, 'user' => false ),
+	//  Adds a button and dialog for step-by-step publishing
+	'publish' => array( 'global' => false, 'user' => true ),
+
+); 
+```
+... the only thing I can guess that might be is the in-line (or live?) preview module. I've never seen 'publish' at work or heard anything about it either. And of course, hideSig is still in effect though it hasn't ""worked"" for months now.
+
+That said, I can go along with removing the ""abandoned"" feature bits - unless somebody knows better. The focus is on developing VisualEditor as far as I can tell anyway. I just hope they keep something like WikiEditor around for the non-Wikipedia types of projects.
+
+",1417373777,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+Template editor does not load,"Intention:
+I tried to insert a template using VisualEditor when editing or creating pages on dewiki.
+
+Steps to Reproduce:
+1. Enable Visual Editor in the Beta preferences
+2. Open a random page on dewiki and edit it.
+3. Click ‘Einfügen’ → ‘Vorlage’ (= ‘Insert’ → ‘Template’).
+
+Actual Results:  
+A pop-up opens, but does not load (title: ‘Laden …’ = ‘Loading …’). The pop-up cannot be closed (hitting ‘Abbrechen’ = ‘Cancel’ does not work), so the previous changes are lost.
+
+Expected Results:  
+Instead the template editor should open normally.
+
+Reproducible: Always
+
+Using vector with Firefox 32.0 on Kubuntu 14.04.
+
+JS error (Firefox web console):
+TypeError: queue is undefined ve.dm.MWTransclusionModel.js:136
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411479300,PHID-USER-valtn43cik2zouepilqb,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_description,declined
+Template editor does not load,"You're welcome. On de.wp you can find me at https://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07 . Please let us know of any further issues, or just leave your thoughts about your experience with VE. Thank you.",1411482149,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_subcomment,NA
+Template editor does not load,"Hmm, strange.  The problem does not occur with a blanked common.js, though the user scripts did not report an error.  Anyway, thanks for the assistance; I’ll have another look at the user scripts.",1411481741,PHID-USER-valtn43cik2zouepilqb,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_subcomment,NA
+Template editor does not load,"I can't reproduce with the same browser but in Windows 8.
+Robin, can you please try to add a template in incognito mode to https://de.wikipedia.org/wiki/Benutzer:Elitre_(WMF)/sandbox?veaction=edit and tell us what happens? Thanks.",1411481150,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_subcomment,NA
+Template editor does not load,"Created attachment 16552
+Screenshot of the stuck template pop-up with Firefox 32.0 on Kubuntu 14.04
+
+**Attached**: {F14915}",1411479513,PHID-USER-valtn43cik2zouepilqb,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_subcomment,NA
+"VisualEditor: Citations appear broken for a few moments, before getting inserted in a Basic Reference dialog .","Citations broken display
+
+Environment- Test2, beta, production
+
+1> Cite Basic -> Select to insert any citation(book/journal/news/website)
+2> In the resulting modal, just click insert button.
+3> Notice the citation appears broken momentarily and then gets added to the Reference editor.
+
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14809}",1410879600,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gqixviakwxjhwko6a5nu,task_description,declined
+"VisualEditor: Citations appear broken for a few moments, before getting inserted in a Basic Reference dialog .",Done.,1415031297,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqixviakwxjhwko6a5nu,task_subcomment,NA
+"VisualEditor: Citations appear broken for a few moments, before getting inserted in a Basic Reference dialog .","Please close this issue, i cannot reproduce it anymore.",1415027667,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gqixviakwxjhwko6a5nu,task_subcomment,NA
+VisualEditor: {{lowercasetitle}} is not reflected in Display title in Advanced page settings,"The article [[iOS]] in the English Wikipedia has {{lowercasetitle}}, which is a wrapper for {{displaytitle}}.
+
+It works correctly for display, but isn't shown in the Advanced settings dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410854280,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-4tcm2evcvzrqvo5xtchr,task_description,duplicate
+VisualEditor: {{lowercasetitle}} is not reflected in Display title in Advanced page settings,I'm guessing this is because the displaytitle is transcluded in?,1420942044,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-4tcm2evcvzrqvo5xtchr,task_subcomment,NA
+"VisualEditor: In Safari, Citation dialog opens with a weird animation and placing the cursor inside a parameter field enlarges it","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the citation dialog for an existing citation
+3.Place the cursor on any field that has an input in it.
+
+Observed Result:
+The citation dialog opens with a weird animation and the first textbox appears much larger
+
+
+See the screenshot attached.
+
+Environment:Betalabs, test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14782}",1410822360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d4545cy7z4y2r2mrze77,task_description,resolved
+"VisualEditor: In Safari, Citation dialog opens with a weird animation and placing the cursor inside a parameter field enlarges it",This seems to now be fixed?,1417577714,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d4545cy7z4y2r2mrze77,task_subcomment,NA
+"VisualEditor[Regression wmf21] :New Section/Add Topic tab when first enabled/disabled,  gets added to the toolbar only after clicking on the Edit Source tab.","New Section tab in Beta
+
+Environment-Production, Test2, beta
+
+1> Go to Advanced Settings and enable the “Show a tab on this page to add a new section” and apply changes.
+2> Save the page.Switch back and forth between the Edit beta and Read tab, notice the new section/Add topic tab is not added to the Toolbar. It gets added only after clicking on Edit Source tab and then Edit beta tab.
+3>Now  go back to Advanced Settings.Change the “Show a tab on this page to add a new section”  to No and apply changes.
+4>Save the page.
+5> Go back to the editor and notice the new section tab is still visible . And it is only when you click on the Edit source tab, that the New Section tab goes away from the Toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14727}",1410796380,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-v72oxbgvsl4t35xhcxhi,task_description,resolved
+"VisualEditor[Regression wmf21] :New Section/Add Topic tab when first enabled/disabled,  gets added to the toolbar only after clicking on the Edit Source tab.","
+
+*** This bug has been marked as a duplicate of bug 20177 ***",1410805042,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v72oxbgvsl4t35xhcxhi,task_subcomment,NA
+"VisualEditor[Regression wmf21] :New Section/Add Topic tab when first enabled/disabled,  gets added to the toolbar only after clicking on the Edit Source tab.","Created attachment 16470
+Add Topic in Test2
+
+**Attached**: {F14728}",1410796456,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-v72oxbgvsl4t35xhcxhi,task_subcomment,NA
+"VisualEditor: [Regression wmf21] :  Citations deleted, are still shown in “Use  this group” suggestion list.","References list
+
+Environment- Test2, beta
+
+1> Have at least 2 citations on the page.
+2> Select Basic  -> Use an Existing Reference. The selected citation to re-use gets inserted on the page.
+3> Now while the  re-used citation is still highlighted. Select “Basic” again and type in a name  in the “Use this group” input box.
+4> Apply changes.
+5> In the editor that citation gets replaced by the group name. Now delete all the citations from the page.
+6> Select Insert -> References list. And click on the arrow in the “Use this Group” drop-down. Notice the group name assigned in step#3 is still visible in the suggestion list drop-down.
+
+Same thing happens when you try to access the “Use this group” in the basic citation.
+See screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14722}",1410793920,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-fgqx6dqjpzobxffe3bcw,task_description,declined
+"VisualEditor: [Regression wmf21] :  Citations deleted, are still shown in “Use  this group” suggestion list.","(In reply to Rummana Yasmeen from comment #2)
+> Hey Ritu, this is intentional, because even if user deletes the citations
+> that belongs to a specific group, user might want to use that group later
+> and add other citations to that in that edit session.So, instead of making
+> user to do the same step again , we are keeping the group name for that
+> session, however if you save your edit after step 6 , you will no longer see
+> that group name.
+
+yes, i saw that too. But was assuming that the suggestions would get updated too when the page has no citations. got it now.",1410809854,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-fgqx6dqjpzobxffe3bcw,task_subcomment,NA
+"VisualEditor: [Regression wmf21] :  Citations deleted, are still shown in “Use  this group” suggestion list.","Hey Ritu, this is intentional, because even if user deletes the citations that belongs to a specific group, user might want to use that group later and add other citations to that in that edit session.So, instead of making user to do the same step again , we are keeping the group name for that session, however if you save your edit after step 6 , you will no longer see that group name.",1410804727,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fgqx6dqjpzobxffe3bcw,task_subcomment,NA
+"VisualEditor: [Regression wmf21] :  Citations deleted, are still shown in “Use  this group” suggestion list.","Created attachment 16468
+Basic Citation
+
+**Attached**: {F14723}",1410793999,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-fgqx6dqjpzobxffe3bcw,task_subcomment,NA
+Category description not displayed after save,"I added a description to my new category https://en.wikipedia.org/wiki/Category:Conspiracy_theories_in_popular_culture using VisualEditor.
+
+After I saved the category page, my new description was not visible. I had to reload the page, and then it was displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410675780,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-mlkcxdg52un5am2qjmf2,task_description,resolved
+Category description not displayed after save,"Merging this with bug 56289.
+
+*** This bug has been marked as a duplicate of bug 56289 ***",1415046616,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mlkcxdg52un5am2qjmf2,task_subcomment,NA
+VisualEditor: Moving an image in the document results in pixelated thumbnail,"## Steps
+
+1. Select an image node.
+   https://www.mediawiki.org/wiki/VisualEditor:Basic_example_worksheet#Media_files
+2. Resize a one of the small ones to be bigger. It'll fetch a large thumbnail momentarily.
+3. Drag and drop the image to a different position in the surrounding paragraph.
+
+## Unexpected behaviour
+
+The original image resource is re-used after a drag/drop, but now upscaled by the browser, thus pixelated. And no new thumb is fetched, either.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410639060,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yaxez2im35xxygh33vod,task_description,resolved
+VisualEditor: Moving an image in the document results in pixelated thumbnail,"It seems like it's been fixed - when resized(enlarged) images are dragged&dropped - they do not get reversed to the original resolution(and, therefore,  pixelated). 
+
+Or it could be that only specific images displayed the issue. ",1424211819,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-yaxez2im35xxygh33vod,task_subcomment,NA
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present","Span tag as seen in Firefox
+
+https://en.wikipedia.org/wiki/Everyone_Poops?veaction=edit produces an ugly span tag above the infobox.  
+
+The infobox is not displaying correctly at all in Safari, but in both Firefox and Safari it shows a long, large, bold-face span tag.  This appears to be caused by the <ref> tags.  See https://en.wikipedia.org/w/index.php?oldid=625300040 for a single-parameter infobox that causes the mess.
+
+These span tags are not saved, so they don't corrupt the wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15303}",1410561720,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-63hk7m7naae6ypxuy7z5,task_description,declined
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present","This is just a buggy template / template use.
+
+The wikitext on https://en.wikipedia.org/w/index.php?oldid=625300040 leads to the following template expansion for the infobox:
+
+...
+<span class=""Z3988""
+          title=""ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Everyone+Poops<ref name=""bnn"">{{cite web|url=http://search.barnesandnoble.com/Everyone-Poops/Taro-Gomi/e/9780916291457|title=Everyone Poops, My Body Science Series, Taro Gomi, Book|accessdate=2008-02-14|year=2009|publisher=[[Barnes & Noble]]}}</ref>""></span
+...
+
+See how the span has a title attribute that has a ref tag and transclusion. But even that brokenness is okay .. the real problem is the use of double quotes for the name attribute of the <ref> tag that is embedded in the title attribute.
+
+So, the wikitext is effectively something like this:
+
+<span title=""....name=""bnn""...""</span>
+
+That is broken because of the use of double quotes which terminates the title attribute early. This is one of those edge-case differences between PHP parser and Parsoid. If the name=""bnn"" is replaced with name='bnn', this will work.
+
+This is a wontfix on the Parsoid end since there is a wikitext edit that will handle this strange edge case.
+
+Please reopen if there is something to do on the Parsoid end.",1416237485,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-63hk7m7naae6ypxuy7z5,task_subcomment,NA
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present",Looks like a Parsoid issue?,1412366992,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63hk7m7naae6ypxuy7z5,task_subcomment,NA
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present",Also reported here:  https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Infobox_on_en.wikipedia%27s_The_Little_Prince,1411949566,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-63hk7m7naae6ypxuy7z5,task_subcomment,NA
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present","Created attachment 16456
+Infobox as seen in Safari.  Note that the content of the box does not display in Safari.  It's blank for half a screen, and then the article text begins.
+
+**Attached**: {F15304}",1410561833,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-63hk7m7naae6ypxuy7z5,task_subcomment,NA
+"VisualEditor:  ""Clear styling"" is confusing.  If it's going to clear links, too, then it should say, ""Clear styling and links""","If ""clear styling"" is going to clear links, too, then it should say, ""Clear styling and links"".  
+
+(I'd rather that it didn't clear links, because, when I copy a link from another page, I want a way to get rid of character formatting and colors without killing the links, too.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410464640,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-xcx7l75kyfn73sjmenqd,task_description,resolved
+"VisualEditor:  ""Clear styling"" is confusing.  If it's going to clear links, too, then it should say, ""Clear styling and links""","
+
+*** This bug has been marked as a duplicate of bug 51757 ***",1410482044,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xcx7l75kyfn73sjmenqd,task_subcomment,NA
+VisualEditor:  Links to disambiguation pages should be highlighted in a different color,"This is related to bug 61072 and bug 50240.
+
+Please consider marking all links to disambiguation pages in a different color, not just in the link inspector tool itself, but in the regular text that editors see when typing in VisualEditor.  This will help editors realize that there is something different (and probably wrong) with links that were previously added to the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410463440,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jtmdegkv2zterww5ielc,task_description,resolved
+VisualEditor:  Links to disambiguation pages should be highlighted in a different color,"This is (effectively) a duplicate of bug 7936 (which is only asking for Special:AllPages, but we'd also change it in the content display). It's nothing particularly specific to VisualEditor; VE just follows MW's lead here.
+
+*** This bug has been marked as a duplicate of bug 7936 ***",1410488331,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jtmdegkv2zterww5ielc,task_subcomment,NA
+VisualEditor:  Links to disambiguation pages should be highlighted in a different color,"BD2412 has specifically requested that this be available to everyone, not just for himself/people using a script.",1410468169,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jtmdegkv2zterww5ielc,task_subcomment,NA
+VisualEditor:  Links to disambiguation pages should be highlighted in a different color,"They already are! (Or rather can be.) I implemented a way to color them in 066283dde745fcc372ffab8d753962858813d032 (the links on the editing surface now have a .mw-disambig class that can be styled with user/site CSS). I also did the same functionality in the MW parser (8cc16d021410f49fa12a2f35c97cdac51adf4380, this is not rolled out yet).
+
+I'm not sure if we want to actually color them. Colors can be distracting/confusing, especially if it's not clear what they mean. MediaWiki has been providing a .mw-redirect CSS class in parser output for years and it was never styled in any way, as far as I know. (Some special pages mark redirects with italics, though.)
+
+For the record, such coloring functionality has sometimes been implemented by gadgets. pl.wp has a opt-in gadget to color redirects green and disambigs maroon and add a form to the page to selectively correct the links; ru.wp has some tool enabled for everyone that gives disambigs pink background with red outline (or had, last time I checked). I am not aware of any such thing on the English Wikipedia (but I'd be love to learn about it if it exists).",1410464649,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jtmdegkv2zterww5ielc,task_subcomment,NA
+VisualEditor:  Language dialog box didn't draw correctly,"Language dialog box, as it's not meant to be
+
+While testing on Meta, the language inspector did not open correctly.  It had some odd box drawing and no buttons.  See the screenshot.
+
+(This is not the problem described in bug 70731.  This oddly drawn box was the correct size.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15132}",1410461400,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kn7dujwu6ne4iw4jweqi,task_description,resolved
+VisualEditor:  Language dialog box didn't draw correctly,"This appears to now be fixed for me – testing in Firefox, Chrome and Safari.",1417480519,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kn7dujwu6ne4iw4jweqi,task_subcomment,NA
+"VisualEditor:  Saving produced a ""Something went wrong"" generic error message, but it silently and successfully saved the page","User:Mike Christie made ten small (often single-character) edits to [[w:en:2002 Pacific typhoon season]] recently.  Edits #1 and #3 produced a generic error of ""Something went wrong"", and it appeared the save had failed.  
+
+In both cases, the save worked.  The diffs are https://en.wikipedia.org/w/index.php?title=2002_Pacific_typhoon_season&diff=624878218&oldid=624550518 and https://en.wikipedia.org/w/index.php?title=2002_Pacific_typhoon_season&diff=next&oldid=624881675  None of the other, similar edits made to the article (including one in between these two) produced any errors. 
+
+Mike usually edits in Chrome on Windows 7.  I've seen the same behavior with a generic ""There was an error"" message in Firefox on Mac OS 10.8.5, so it's probably affecting everything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53093",1410457800,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-mgurrwf77bjbyrtqm46n,task_description,duplicate
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","I am following quick start instructions[1] on a Mac.
+
+1. https://www.mediawiki.org/wiki/MediaWiki-Vagrant#Quick_start
+
+```
+$ sw_vers -productVersion
+10.9.4
+
+$ git --version
+git version 2.1.0
+
+$ vboxmanage --version
+4.3.16r95972
+
+$ vagrant -v
+Vagrant 1.6.5
+
+$ git pull origin master
+From ssh://gerrit.wikimedia.org:29418/mediawiki/vagrant
+ * branch            master     -> FETCH_HEAD
+Already up-to-date.
+
+$ git submodule update --init --recursive
+
+$ ./setup.sh
+Plugin vagrant-vbguest is already installed
+Installing plugin mediawiki-vagrant-0.1.4.gem
+- Installing the 'mediawiki-vagrant-0.1.4.gem' plugin. This can take a few minutes...
+- Installed the plugin 'mediawiki-vagrant (0.1.4)'!
+You're all set! Simply run `vagrant up` to boot your new environment.
+
+$ vagrant destroy
+    default: Are you sure you want to destroy the 'default' VM? [y/N] y
+==> default: Removing puppet created files...
+==> default: Destroying VM and associated drives...
+==> default: Pruning invalid NFS exports. Administrator privileges will be required...
+Password:
+==> default: Running cleanup tasks for 'lsb_check' provisioner...
+==> default: Running cleanup tasks for 'puppet' provisioner...
+
+$ vagrant up
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'trusty-cloud'...
+==> default: Matching MAC address for NAT networking...
+==> default: Setting the name of the VM: vagrant_default_1410428807331_61896
+==> default: Clearing any previously set forwarded ports...
+==> default: Clearing any previously set network interfaces...
+==> default: Preparing network interfaces based on configuration...
+    default: Adapter 1: nat
+    default: Adapter 2: hostonly
+==> default: Forwarding ports...
+    default: 80 => 8080 (adapter 1)
+    default: 22 => 2222 (adapter 1)
+==> default: Running 'pre-boot' VM customizations...
+==> default: Booting VM...
+==> default: Waiting for machine to boot. This may take a few minutes...
+    default: SSH address: 127.0.0.1:2222
+    default: SSH username: vagrant
+    default: SSH auth method: private key
+    default: Warning: Connection timeout. Retrying...
+==> default: Machine booted and ready!
+GuestAdditions versions on your host (4.3.16) and guest (4.3.10) do not match.
+stdin: is not a tty
+ * Stopping VirtualBox Additions
+   ...done.
+stdin: is not a tty
+Reading package lists...
+Building dependency tree...
+Reading state information...
+The following packages were automatically installed and are no longer required:
+  dkms fakeroot gcc gcc-4.8 libasan0 libatomic1 libc-dev-bin libc6-dev
+  libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libfakeroot libfontenc1
+  libgcc-4.8-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgomp1
+  libice6 libitm1 libllvm3.4 libpciaccess0 libpixman-1-0 libquadmath0 libsm6
+  libtsan0 libtxc-dxtn-s2tc0 libx11-xcb1 libxaw7 libxcb-dri2-0 libxcb-dri3-0
+  libxcb-glx0 libxcb-present0 libxcb-sync1 libxcomposite1 libxdamage1
+  libxfixes3 libxfont1 libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1
+  libxshmfence1 libxt6 libxxf86vm1 linux-libc-dev manpages-dev x11-common
+  x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common
+  xserver-xorg-core
+Use 'apt-get autoremove' to remove them.
+The following packages will be REMOVED:
+  virtualbox-guest-dkms* virtualbox-guest-utils* virtualbox-guest-x11*
+0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
+After this operation, 12.1 MB disk space will be freed.
+(Reading database ... 60914 files and directories currently installed.)
+Removing virtualbox-guest-dkms (4.3.10-dfsg-1) ...
+
+-------- Uninstall Beginning --------
+Module:  virtualbox-guest
+Version: 4.3.10
+Kernel:  3.13.0-30-generic (x86_64)
+-------------------------------------
+
+Status: Before uninstall, this module version was ACTIVE on this kernel.
+
+vboxguest.ko:
+ - Uninstallation
+   - Deleting from: /lib/modules/3.13.0-30-generic/updates/dkms/
+ - Original module
+   - No original module was found for this module on this kernel.
+   - Use the dkms install command to reinstall any previous module version.
+
+
+vboxsf.ko:
+ - Uninstallation
+   - Deleting from: /lib/modules/3.13.0-30-generic/updates/dkms/
+ - Original module
+   - No original module was found for this module on this kernel.
+   - Use the dkms install command to reinstall any previous module version.
+
+
+vboxvideo.ko:
+ - Uninstallation
+   - Deleting from: /lib/modules/3.13.0-30-generic/updates/dkms/
+ - Original module
+   - No original module was found for this module on this kernel.
+   - Use the dkms install command to reinstall any previous module version.
+
+depmod....
+
+DKMS: uninstall completed.
+
+------------------------------
+Deleting module version: 4.3.10
+completely from the DKMS tree.
+------------------------------
+Done.
+Removing virtualbox-guest-x11 (4.3.10-dfsg-1) ...
+Purging configuration files for virtualbox-guest-x11 (4.3.10-dfsg-1) ...
+Removing virtualbox-guest-utils (4.3.10-dfsg-1) ...
+Purging configuration files for virtualbox-guest-utils (4.3.10-dfsg-1) ...
+Processing triggers for man-db (2.6.7.1-1) ...
+Processing triggers for libc-bin (2.19-0ubuntu6) ...
+stdin: is not a tty
+Reading package lists...
+Building dependency tree...
+Reading state information...
+dkms is already the newest version.
+dkms set to manually installed.
+linux-headers-3.13.0-30-generic is already the newest version.
+linux-headers-3.13.0-30-generic set to manually installed.
+The following packages were automatically installed and are no longer required:
+  libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libfontenc1 libgl1-mesa-dri
+  libgl1-mesa-glx libglapi-mesa libice6 libllvm3.4 libpciaccess0 libpixman-1-0
+  libsm6 libtxc-dxtn-s2tc0 libx11-xcb1 libxaw7 libxcb-dri2-0 libxcb-dri3-0
+  libxcb-glx0 libxcb-present0 libxcb-sync1 libxcomposite1 libxdamage1
+  libxfixes3 libxfont1 libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1
+  libxshmfence1 libxt6 libxxf86vm1 x11-common x11-xkb-utils xfonts-base
+  xfonts-encodings xfonts-utils xserver-common xserver-xorg-core
+Use 'apt-get autoremove' to remove them.
+0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+Copy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
+stdin: is not a tty
+mount: block device /tmp/VBoxGuestAdditions.iso is write-protected, mounting read-only
+Installing Virtualbox Guest Additions 4.3.16 - guest version is 4.3.10
+stdin: is not a tty
+Verifying archive integrity... All good.
+Uncompressing VirtualBox 4.3.16 Guest Additions for Linux............
+VirtualBox Guest Additions installer
+Copying additional installer modules ...
+Installing additional modules ...
+Removing existing VirtualBox DKMS kernel modules ...done.
+Removing existing VirtualBox non-DKMS kernel modules ...done.
+Building the VirtualBox Guest Additions kernel modules ...done.
+Doing non-kernel setup of the Guest Additions ...done.
+Starting the VirtualBox Guest Additions ...done.
+Installing the Window System drivers
+Could not find the X.Org or XFree86 Window System, skipping.
+An error occurred during installation of VirtualBox Guest Additions 4.3.16. Some functionality may not work as intended.
+In most cases it is OK that the ""Window System drivers"" installation failed.
+stdin: is not a tty
+==> default: Checking for guest additions in VM...
+==> default: Setting hostname...
+==> default: Configuring and enabling network interfaces...
+==> default: Exporting NFS shared folders...
+==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
+==> default: Mounting NFS shared folders...
+==> default: Mounting shared folders...
+    default: /tmp/vagrant-puppet-5/manifests => /Users/z/Documents/wmf/mediawiki/vagrant/puppet/manifests
+    default: /tmp/vagrant-puppet-5/modules-0 => /Users/z/Documents/wmf/mediawiki/vagrant/puppet/modules
+==> default: Running provisioner: lsb_check...
+==> default: Running provisioner: puppet...
+==> default: Running Puppet with site.pp...
+==> default: stdin: is not a tty
+==> default: Notice: Compiled catalog for mediawiki-vagrant.dev in environment production in 2.88 seconds
+==> default: Info: Applying configuration version '1410428953.no-git'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/multiversion-install]/ensure: created
+==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/51-cloudguest]/ensure: removed
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/mwscript]/ensure: created
+==> default: Notice: /Stage[main]/Main/File[/etc/apt/apt.conf.d/20shared-cache]/ensure: defined content as '{md5}711fa2f2a913db3990e7beb15cf57b5b'
+==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/00-header]/ensure: removed
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/alldbs]/ensure: created
+==> default: Notice: /Stage[main]/Misc/Exec[fix_root_profile]/returns: executed successfully
+==> default: Info: mount[files]: allowing mediawiki-vagrant access
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d]/group: group changed 'root' to 'vagrant'
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/bash_completion.sh]/ensure: removed
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/mediawiki-vagrant.sh]/ensure: defined content as '{md5}e9dcf6a1136af35370d9d8191cb11483'
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/Z99-cloud-locale-test.sh]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/var/www]/ensure: created
+==> default: Notice: /Stage[main]/Main/File[/srv]/owner: owner changed 'root' to 'vagrant'
+==> default: Notice: /Stage[main]/Main/File[/srv]/group: group changed 'root' to 'www-data'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/MWMultiVersion.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/defines.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/resources]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/missing.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/CREDITS]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/opensearch_desc.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/api.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/MWScript.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/thumb_handler.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/skins]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/thumb.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/10-help-text]/ensure: removed
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/index.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/dblist.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/foreachwiki]/ensure: created
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/Z97-byobu.sh]/ensure: removed
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/img_auth.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/COPYING]/ensure: created
+==> default: Notice: /Stage[main]/Mysql/File[/home/vagrant/.my.cnf]/ensure: defined content as '{md5}ef06fc0c2fb48af1df465c01df0f9634'
+==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/50-landscape-sysinfo]/ensure: removed
+==> default: Info: /etc/update-motd.d: Scheduling refresh of Exec[update_motd]
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/load.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Misc/Motd::Script[mediawiki_vagrant]/File[/etc/update-motd.d/50-mediawiki-vagrant]/ensure: defined content as '{md5}3aba016b0d0dda7268fcb1b655ea78f9'
+==> default: Info: /Stage[main]/Misc/Motd::Script[mediawiki_vagrant]/File[/etc/update-motd.d/50-mediawiki-vagrant]: Scheduling refresh of Exec[update_motd]
+==> default: Notice: /Stage[main]/Motd/Exec[update_motd]: Triggered 'refresh' from 2 events
+==> default: Notice: /Stage[main]/Php::Composer/Exec[download_composer]/returns: executed successfully
+==> default: Notice: /Stage[main]/Php::Composer/File[/usr/local/bin/composer]/mode: mode changed '0644' to '0755'
+==> default: Notice: /Stage[main]/Apt/File[/etc/apt/sources.list.d/multiverse.list]/ensure: defined content as '{md5}a4108116df82d5428debf4b06fbd0f54'
+==> default: Notice: /Stage[main]/Apt/File[/usr/local/share/wikimedia-pubkey.asc]/ensure: defined content as '{md5}39e2c3119a82a59d706317fce97a6bfc'
+==> default: Info: /Stage[main]/Apt/File[/usr/local/share/wikimedia-pubkey.asc]: Scheduling refresh of Exec[add_wikimedia_apt_key]
+==> default: Notice: /Stage[main]/Apt/Exec[add_wikimedia_apt_key]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Apt/File[/etc/apt/sources.list.d/wikimedia.list]/ensure: defined content as '{md5}81cc6c07729914e993ebf1829da0e002'
+==> default: Notice: /Stage[main]/Apt/Exec[update_package_index]/returns: executed successfully
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/extensions]/ensure: created
+==> default: Notice: /Stage[main]/Php::Composer/Env::Var[COMPOSER_CACHE_DIR]/File[/etc/profile.d/set_COMPOSER_CACHE_DIR.sh]/ensure: created
+==> default: Notice: /Stage[main]/Main/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+==> default: Notice: /Stage[main]/Main/Package[build-essential]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Misc/Package[ack-grep]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[python-pip]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[ruby-dev]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Misc/Package[htop]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php::Remote_debug/Package[php5-xdebug]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Redis/Package[redis-server]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[python-dev]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[chef-zero]/ensure: removed
+==> default: Notice: /Stage[main]/Mysql::Packages/Package[mysql-server]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[chef]/ensure: removed
+==> default: Notice: /Stage[main]/Redis/File[/srv/redis]/ensure: created
+==> default: Notice: /Stage[main]/Apache::Mod::Php5/Package[libapache2-mod-php5]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Misc/File[/etc/ackrc]/ensure: defined content as '{md5}744cd26afe93f6ae5e3f04cee2bbc188'
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/envvars]/content: content changed '{md5}331419cf134c3cdce519b0d0f151cbc9' to '{md5}adf14ad862398d9eaab25c196ffb4f40'
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/envvars]/group: group changed 'root' to 'vagrant'
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/envvars]: Scheduling refresh of Service[apache2]
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/envvars]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache::Mod::Proxy_fcgi/Apache::Mod_conf[proxy_fcgi]/Exec[ensure_present_mod_proxy_fcgi]/returns: executed successfully
+==> default: Info: /Stage[main]/Apache::Mod::Proxy_fcgi/Apache::Mod_conf[proxy_fcgi]/Exec[ensure_present_mod_proxy_fcgi]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mediawiki::Apache/File[/var/www/favicon.ico]/ensure: defined content as '{md5}b1d335c7c87c3d9b0693db6a5dc69d7b'
+==> default: Notice: /Stage[main]/Mediawiki::Apache/File[/var/www/info.php]/ensure: defined content as '{md5}fb92f9147037f47dcf29c96dbc68154d'
+==> default: Notice: /Stage[main]/Php/Package[php5-mysql]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php5-gd]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php-apc]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php5-mcrypt]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php5]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Apache::Mod::Headers/Apache::Mod_conf[headers]/Exec[ensure_present_mod_headers]/returns: executed successfully
+==> default: Info: /Stage[main]/Apache::Mod::Headers/Apache::Mod_conf[headers]/Exec[ensure_present_mod_headers]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Php/Package[php5-sqlite]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/sites-enabled/000-default.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Php/Package[php-pear]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php5-curl]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/env-enabled]/ensure: created
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/env-enabled]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Php/Php::Ini[debug_output]/File[/etc/php5/mods-available/_debug_output.ini]/ensure: defined content as '{md5}d063cce793713a4e99892c1076fcaa4c'
+==> default: Info: /Stage[main]/Php/Php::Ini[debug_output]/File[/etc/php5/mods-available/_debug_output.ini]: Scheduling refresh of Service[apache2]
+==> default: Info: /Stage[main]/Php/Php::Ini[debug_output]/File[/etc/php5/mods-available/_debug_output.ini]: Scheduling refresh of Exec[/usr/sbin/php5enmod -s ALL _debug_output]
+==> default: Notice: /Stage[main]/Php/Php::Ini[debug_output]/Exec[/usr/sbin/php5enmod -s ALL _debug_output]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Php/Php::Ini[session_defaults]/File[/etc/php5/mods-available/_session_defaults.ini]/ensure: defined content as '{md5}7236471110ece2bbd4ff508af9030132'
+==> default: Info: /Stage[main]/Php/Php::Ini[session_defaults]/File[/etc/php5/mods-available/_session_defaults.ini]: Scheduling refresh of Service[apache2]
+==> default: Info: /Stage[main]/Php/Php::Ini[session_defaults]/File[/etc/php5/mods-available/_session_defaults.ini]: Scheduling refresh of Exec[/usr/sbin/php5enmod -s ALL _session_defaults]
+==> default: Notice: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/File[/etc/php5/mods-available/_remote_debug.ini]/ensure: defined content as '{md5}f1115221d2629974b905dc37476797a1'
+==> default: Info: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/File[/etc/php5/mods-available/_remote_debug.ini]: Scheduling refresh of Service[apache2]
+==> default: Info: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/File[/etc/php5/mods-available/_remote_debug.ini]: Scheduling refresh of Exec[/usr/sbin/php5enmod -s ALL _remote_debug]
+==> default: Info: /etc/apache2/sites-enabled: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Php::Composer/Exec[update_composer]/returns: executed successfully
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/security.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Php/Php::Ini[session_defaults]/Exec[/usr/sbin/php5enmod -s ALL _session_defaults]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/other-vhosts-access-log.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/env-available]/ensure: created
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/env-available]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/Exec[/usr/sbin/php5enmod -s ALL _remote_debug]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/serve-cgi-bin.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/security.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/localized-error-pages.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/other-vhosts-access-log.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/charset.conf]/ensure: removed
+==> default: Info: /etc/apache2/conf-available: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/charset.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/localized-error-pages.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/sites-available/default-ssl.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/ports.conf]/content: content changed '{md5}a961f23471d985c2b819b652b7f64321' to '{md5}832989c376f29c4740c3bc5eb9ed3f12'
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/ports.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/site-confs]/ensure: created
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/site-confs]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/serve-cgi-bin.conf]/ensure: removed
+==> default: Info: /etc/apache2/conf-enabled: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mysql/Exec[set_mysql_password]/returns: executed successfully
+==> default: Notice: /Stage[main]/Role::Mediawiki/Package[tidy]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Role::Mediawiki/Package[php5-tidy]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Redis/File[/etc/redis/redis.conf]/content: content changed '{md5}e79ac99a5236e6ab3faf86bdd99affaf' to '{md5}dedc5a2ff609b5cceadc08307646ad54'
+==> default: Info: /Stage[main]/Redis/File[/etc/redis/redis.conf]: Scheduling refresh of Service[redis-server]
+==> default: Notice: /Stage[main]/Redis/Service[redis-server]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Redis::Php/Package[php5-redis]/ensure: ensure changed 'purged' to 'present'
+==> default: Info: /Stage[main]/Redis::Php/Package[php5-redis]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Hhvm/File[/usr/local/bin/hhvmsh]/ensure: defined content as '{md5}db1312e407c8fb05c1fb193692ce5c2f'
+==> default: Notice: /Stage[main]/Hhvm/File[/etc/hhvm]/ensure: created
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-dev]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/File[/etc/hhvm/php.ini]/content: content changed '{md5}38e0be69fb5da2bebc90f17f7fe3c705' to '{md5}ef2004ca4a64aea1d212962c34738666'
+==> default: Info: /Stage[main]/Hhvm/File[/etc/hhvm/php.ini]: Scheduling refresh of Service[hhvm]
+==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/File[/etc/apache2/site-confs/hhvm-admin]/ensure: created
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-luasandbox]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-wikidiff2]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/File[/etc/hhvm/config.hdf]/ensure: defined content as '{md5}2a46fb84966afc8fc3b51fd9abe57378'
+==> default: Info: /Stage[main]/Hhvm/File[/etc/hhvm/config.hdf]: Scheduling refresh of Service[hhvm]
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-fss]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/File[/etc/init/hhvm.conf]/content: content changed '{md5}48267cf8f84fd68070699cf68ce7f663' to '{md5}329e085674306cc428a3440a0916b40f'
+==> default: Info: /Stage[main]/Hhvm/File[/etc/init/hhvm.conf]: Scheduling refresh of Service[hhvm]
+==> default: Notice: /Stage[main]/Hhvm/Service[hhvm]/ensure: ensure changed 'stopped' to 'running'
+==> default: Info: /Stage[main]/Hhvm/Service[hhvm]: Unscheduling refresh on Service[hhvm]
+==> default: Notice: /Stage[main]/Php/Package[php5-intl]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/File[/etc/apache2/site-confs/hhvm-admin/00-default.conf]/ensure: created
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/sites-available/000-default.conf]/ensure: removed
+==> default: Info: /etc/apache2/sites-available: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Git/Package[git]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Git/Package[git-review]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/tests]/ensure: created
+==> default: Notice: /Stage[main]/Php/Package[php5-readline]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Misc/File[/usr/local/sbin/isfresh]/ensure: defined content as '{md5}6fee8323b6bdd6afc7c37faa4491794a'
+==> default: Notice: /Stage[main]/Apache/Misc::Evergreen[apache2]/Exec[check_apache2_freshness]/returns: executed successfully
+==> default: Info: /Stage[main]/Apache/Misc::Evergreen[apache2]/Exec[check_apache2_freshness]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/MWVersion.php]/ensure: created
+==> default: Notice: /Stage[main]/Php/Package[php5-dev]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Mediawiki/File[/usr/local/bin/run-mediawiki-tests]/ensure: defined content as '{md5}cb1918d4464e50c256399b91c411bb05'
+==> default: Notice: /Stage[main]/Mediawiki/File[/usr/local/bin/import-mediawiki-dump]/ensure: defined content as '{md5}81874e61ef7c14f0a5b1aa87a337cfbb'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/vagrant/settings.d/wikis]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/File[/var/cache/mediawiki]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/vagrant/settings.d/wikis/LoadWgConf.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/File[/usr/local/bin/run-git-update]/ensure: defined content as '{md5}5ff218ed45bf3ea414f9c4776e9210d2'
+==> default: Notice: /Stage[main]/Mediawiki/Env::Profile_script[add mediawiki vendor bin to path]/File[/etc/profile.d/50-add-mediawiki-vendor-bin-to-path.sh]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Env::Var[MW_INSTALL_PATH]/File[/etc/profile.d/set_MW_INSTALL_PATH.sh]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/vagrant/settings.d/wikis/CommonSettings.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/jobrunner.json]/ensure: defined content as '{md5}670966939c990598a91362cb0ffb75ac'
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/File[/etc/jobrunner.json]: Scheduling refresh of Service[jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/default/jobrunner]/ensure: defined content as '{md5}baefee683608d285b2c4895c8f76c563'
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/File[/etc/default/jobrunner]: Scheduling refresh of Service[jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki/File[/srv/images]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: Composer could not find a composer.json file in /vagrant/mediawiki
+==> default: Notice: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: To initialize a project, please create a composer.json file as described in the http://getcomposer.org/ ""Getting Started"" section
+==> default: Error: composer install --optimize-autoloader returned 1 instead of one of [0]
+==> default: Error: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: change from notrun to 0 failed: composer install --optimize-autoloader returned 1 instead of one of [0]
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/wgConf.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/dbConf.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/File[mediawiki_upstart_bridge]/ensure: defined content as '{md5}b1cfb3aa1f75ada7780442b4a8a1ca76'
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/settings.d]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/settings.d/puppet-managed]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/settings.d/puppet-managed/README]/ensure: defined content as '{md5}64ae42537fb40c737e432f1e747355f7'
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_setup]/returns: executed successfully
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_include_extra_settings]/returns: executed successfully
+==> default: Notice: /Stage[main]/Mediawiki/Exec[copy_LocalSettings]/returns: executed successfully
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/logrotate.d/mediawiki_jobrunner]/ensure: defined content as '{md5}108922f7a7305cd4f69202fa6ba6d2ee'
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Git::Clone[mediawiki/services/jobrunner]/Exec[git_clone_mediawiki/services/jobrunner]/returns: executed successfully
+==> default: Info: Git::Clone[mediawiki/services/jobrunner]: Scheduling refresh of Exec[git_install_checkout_mediawiki/services/jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Exec[git_install_reset_mediawiki/services/jobrunner]/returns: executed successfully
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Exec[git_install_reset_mediawiki/services/jobrunner]: Scheduling refresh of Exec[git_install_checkout_mediawiki/services/jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Exec[git_install_checkout_mediawiki/services/jobrunner]: Triggered 'refresh' from 2 events
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: fatal: destination path '/vagrant/mediawiki/skins/Vector' already exists and is not an empty directory.
+==> default: Error: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]
+==> default: Error: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: change from notrun to 0 failed: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]
+==> default: Notice: /Stage[main]/Mediawiki/File[/var/www/mediawiki-vagrant.png]/ensure: defined content as '{md5}f9afb7d19e39247820bc1e81883a96f7'
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Dependency Exec[git_clone_mediawiki/skins/Vector] has failures: true
+==> default: Warning: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Skipping because of failed dependencies
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/init/jobrunner.conf]/ensure: defined content as '{md5}e2302b512e81c3d406f8f2159dd4dbcd'
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/File[/etc/init/jobrunner.conf]: Scheduling refresh of Service[jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Service[jobrunner]/ensure: ensure changed 'stopped' to 'running'
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/Service[jobrunner]: Unscheduling refresh on Service[jobrunner]
+==> default: Notice: /Stage[main]/Apache::Mod::Rewrite/Apache::Mod_conf[rewrite]/Exec[ensure_present_mod_rewrite]/returns: executed successfully
+==> default: Info: /Stage[main]/Apache::Mod::Rewrite/Apache::Mod_conf[rewrite]/Exec[ensure_present_mod_rewrite]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/Apache::Conf[disable sendfile]/File[/etc/apache2/conf-available/50-disable-sendfile.conf]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/Apache::Conf[devwiki]/File[/etc/apache2/sites-available/50-devwiki.conf]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/Apache::Conf[devwiki]/File[/etc/apache2/sites-enabled/50-devwiki.conf]/ensure: created
+==> default: Info: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/Apache::Conf[devwiki]/File[/etc/apache2/sites-enabled/50-devwiki.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/Apache::Conf[php5-devwiki]/File[/etc/apache2/sites-available/50-php5-devwiki.conf]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/Apache::Conf[php5-devwiki]/File[/etc/apache2/sites-enabled/50-php5-devwiki.conf]/ensure: created
+==> default: Info: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/Apache::Conf[php5-devwiki]/File[/etc/apache2/sites-enabled/50-php5-devwiki.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/File[/etc/apache2/site-confs/php5-devwiki]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/File[/etc/apache2/site-confs/php5-devwiki/00-default.conf]/ensure: created
+==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/Apache::Conf[hhvm-admin]/File[/etc/apache2/sites-available/50-hhvm-admin.conf]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/File[/etc/apache2/site-confs/devwiki]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/File[/etc/apache2/site-confs/devwiki/00-default.conf]/ensure: created
+==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/Apache::Conf[hhvm-admin]/File[/etc/apache2/sites-enabled/50-hhvm-admin.conf]/ensure: created
+==> default: Info: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/Apache::Conf[hhvm-admin]/File[/etc/apache2/sites-enabled/50-hhvm-admin.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/Apache::Conf[disable sendfile]/File[/etc/apache2/conf-enabled/50-disable-sendfile.conf]/ensure: created
+==> default: Info: /Stage[main]/Apache/Apache::Conf[disable sendfile]/File[/etc/apache2/conf-enabled/50-disable-sendfile.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/Service[apache2]: Triggered 'refresh' from 22 events
+==> default: Info: Creating state file /var/lib/puppet/state/state.yaml
+==> default: Notice: Finished catalog run in 180.74 seconds
+The SSH command responded with a non-zero exit status. Vagrant
+assumes that this means the command failed. The output for this command
+should be in the log above. Please read the output to determine what
+went wrong.
+```",1410429960,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_description,resolved
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""",">>! In T72705#976450, @Kabhi2104 wrote:
+> {F28605} Uploaded provision.log here too for future reference and this is the link of new paste https://phabricator.wikimedia.org/P216 
+
+Further discussion moved to {T86787}",1421257654,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","{F28605} Uploaded provision.log here too for future reference and this is the link of new paste https://phabricator.wikimedia.org/P216 
+",1421256985,PHID-USER-cqpeh4jvvexbszsxogrw,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""",">>! In T72705#975760, @Kabhi2104 wrote:
+> I am facing the same problem in ubuntu 14.04.
+> When i run vagrant up i get  **"" VirtualBox VM is already running. ""**
+> While running 127.0.0.1:8080  says  **webpage not available**
+> http://imgur.com/R5ZDXCJ  regarding roles in **vagrant list-roles**
+> I get full bunch of red errors while running **vagrant provision** Here: http://imgur.com/yWohm04
+
+Adding a ""me too"" to a closed ticket probably isn't the best way to get good support. ;)
+
+The errors shown from your puppet provisioning run in the screen capture don't show enough to indicate where things went wrong, just that you had a cascading dependency failure. Based solely on past experience I would guess that there was an apt-get failure that ended up blocking Puppet from doing anything else.
+
+To get a real trace of the problem, you could run `PUPPET_DEBUG=1 vagrant reload --provision | tee provision.log` and then upload provision.log as a paste here and open a new ticket referencing it. The command given will restart the virtual machine and then force a Puppet run. The `PUPPET_DEBUG=1` environment var will tell Puppet to output more information on what it is doing at each stage of the run and `| tee provision.log` will make a copy of all the information sent to the screen in a log file that will be easier to cut-n-paste into [[https://phabricator.wikimedia.org/paste/create/|a new pastebin issue]].",1421253858,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","I am facing the same problem in ubuntu 14.04.
+When i run vagrant up i get  **"" VirtualBox VM is already running. ""**
+While running 127.0.0.1:8080  says  **webpage not available**
+http://imgur.com/R5ZDXCJ  regarding roles in **vagrant list-roles**
+I get full bunch of red errors while running **vagrant provision** Here: http://imgur.com/yWohm04",1421240910,PHID-USER-cqpeh4jvvexbszsxogrw,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""",Thanks for reporting this and writing it up.  I just ran into this. :(,1418456754,PHID-USER-qsj6mtmeexjxulfje7ie,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","(In reply to Bryan Davis from comment #4)
+> Was the vagrant/mediawiki clone new too or potentially very old?
+
+My vagrant/mediawiki clone was so old... (insert joke here).
+
+Documented:
+
+https://www.mediawiki.org/w/index.php?title=MediaWiki-Vagrant&diff=1151216&oldid=1139643",1410524423,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","(In reply to Bryan Davis from comment #4)
+> $ cd vagrant/mediawiki
+> $ git pull
+
+Wait, mediawiki (core?) does not get updated automatically!? Trying this now, will report in a few hours (when the machine is up).",1410521945,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","Was the vagrant/mediawiki clone new too or potentially very old? At least some of these errors look like your vagrant/mediawiki/skins/Vector directory is from before the changes were merged that made Vector a separate repository. The fix for that is given in <https://bugzilla.wikimedia.org/show_bug.cgi?id=70114#c1> :
+
+$ cd vagrant/mediawiki
+$ git pull
+$ cd skins
+$ rm -rf Vector  # might not be a dir here to delete now but worth trying
+$ vagrant provision",1410448617,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","Surprisingly, mediawiki is available at http://127.0.0.1:8080/wiki/Main_Page",1410430516,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","No roles are enabled, I have forgot to mention that.
+
+$ vagrant list-roles
+Available roles:
+
+  accountinfo                graph                      poem                    
+  analytics                  guidedtour                 popups                  
+  antispam                   gwtoolset                  proofreadpage           
+  antispoof                  hadoop                     renameuser              
+  apisandbox                 hive                       scholarships            
+  apparmor                   https                      scribunto               
+  babel                      hue                        simple_miser            
+  betafeatures               imagemetrics               simple_performant       
+  categorytree               interwiki                  sitematrix              
+  centralauth                jsduck                     svg                     
+  centralnotice              jsonconfig                 templatedata            
+  chromium                   labledsectiontransclusion   textextracts            
+  cirrussearch               mantle                     thumb_on_404            
+  cite                       massmessage                timedmediahandler       
+  cldr                       math                       translate               
+  codeeditor                 mathsearch                 uls                     
+  cologneblue                mleb                       uploadwizard            
+  commons                    mobileapp                  urlshortener            
+  commonsmetadata            mobilefrontend             usermerge               
+  confirmedit                modern                     vectorbeta              
+  doublewiki                 molhandler                 visualeditor            
+  echo                       monobook                   warnings_as_errors      
+  education                  multimedia                 wikidata                
+  eventlogging               multimediaviewer           wikidiff2               
+  featuredfeeds              navigationtiming           wikieditor              
+  flow                       newusermessage             wikihiero               
+  fss                        oauth                      wikilove                
+  fundraising                oozie                      wikimediaevents         
+  gadgets                    pagedtiffhandler           wikimediaincubator      
+  gadgets2                   pageimages                 wikimediamessages       
+  geodata                    pagetriage                 wikimetrics             
+  geshi                      parserfunctions            wikitech                
+  gettingstarted             parsoid                    xhprof                  
+  globalcssjs                pdfhandler                 zend                    
+  globaluserpage             phptags                    zero                    
+
+Roles marked with '*' are enabled.
+Note that roles enabled by dependency are not marked.
+Use ""vagrant enable-role"" & ""vagrant disable-role"" to customize.",1410430492,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","Lines from ""vagrant up"" that are highlighted in my terminal (yellow or red) and one line before and after, for context:
+
+$ vagrant up
+...
+==> default: Machine booted and ready!
+GuestAdditions versions on your host (4.3.16) and guest (4.3.10) do not match.
+stdin: is not a tty
+...
+mount: block device /tmp/VBoxGuestAdditions.iso is write-protected, mounting read-only
+Installing Virtualbox Guest Additions 4.3.16 - guest version is 4.3.10
+stdin: is not a tty
+...
+Could not find the X.Org or XFree86 Window System, skipping.
+An error occurred during installation of VirtualBox Guest Additions 4.3.16. Some functionality may not work as intended.
+In most cases it is OK that the ""Window System drivers"" installation failed.
+stdin: is not a tty
+...
+==> default: Notice: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: To initialize a project, please create a composer.json file as described in the http://getcomposer.org/ ""Getting Started"" section
+==> default: Error: composer install --optimize-autoloader returned 1 instead of one of [0]
+==> default: Error: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: change from notrun to 0 failed: composer install --optimize-autoloader returned 1 instead of one of [0]
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki]/ensure: created
+...
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: fatal: destination path '/vagrant/mediawiki/skins/Vector' already exists and is not an empty directory.
+==> default: Error: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]
+==> default: Error: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: change from notrun to 0 failed: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]
+==> default: Notice: /Stage[main]/Mediawiki/File[/var/www/mediawiki-vagrant.png]/ensure: defined content as '{md5}f9afb7d19e39247820bc1e81883a96f7'
+...
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Dependency Exec[git_clone_mediawiki/skins/Vector] has failures: true
+==> default: Warning: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Skipping because of failed dependencies
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/init/jobrunner.conf]/ensure: defined content as '{md5}e2302b512e81c3d406f8f2159dd4dbcd'
+...
+==> default: Notice: Finished catalog run in 180.74 seconds
+The SSH command responded with a non-zero exit status. Vagrant
+assumes that this means the command failed. The output for this command
+should be in the log above. Please read the output to determine what
+went wrong.",1410430161,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+VisualEditor: Media search not working in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Enter something in the search box to search for images
+
+
+Observed Result:
+
+Nothing happens. ""No Results"" found message stays in the dialog instead
+
+Environment:Betalabs
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14832}",1410289080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-miymejtyr774ogj6oozg,task_description,resolved
+VisualEditor: Media search not working in Betalabs,Yeah may be..Working for me now as well,1410302702,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-miymejtyr774ogj6oozg,task_subcomment,NA
+VisualEditor: Media search not working in Betalabs,Works for me… Search blip?,1410299536,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-miymejtyr774ogj6oozg,task_subcomment,NA
+VisualEditor: The Field description popup looks weird on mediawiki.org,"Field description popup for template:Bugzilla on mediawiki.org
+
+See attachment. A lot of wasted empty space, and a scrollbar :) Possibly related to other reports, or a dupe.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70423
+
+**Attached**: {F14777}",1410258120,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-un6exrb6nu4tk4ohkbsk,task_description,resolved
+VisualEditor: The Field description popup looks weird on mediawiki.org,"My patch for bug 70423 seems to fix this.
+
+*** This bug has been marked as a duplicate of bug 70423 ***",1410356188,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-un6exrb6nu4tk4ohkbsk,task_subcomment,NA
+VisualEditor: The Field description popup looks weird on mediawiki.org,Same for the Special Characters dialog.,1410259729,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-un6exrb6nu4tk4ohkbsk,task_subcomment,NA
+"VisualEditor: The References List dialog looks too big, much unnecessary empty space","References list trying to impress us
+
+See screenshot (which was taken in IE), I tried with other browsers and it looked the same there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68226
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70423
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70016
+
+**Attached**: {F14773}",1410253440,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kecyjmzzfanyavgzh5ry,task_description,resolved
+"VisualEditor: The References List dialog looks too big, much unnecessary empty space","
+
+*** This bug has been marked as a duplicate of bug 70016 ***",1414137121,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kecyjmzzfanyavgzh5ry,task_subcomment,NA
+VisualEditor: The link inspector and comment box are appearing with no UI while opening them after an idle time,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Keep it open for a while (~10-15 mins)
+3.After coming back to this page, open a link inspector or a comment box 
+
+Observed Result:
+They open with no UI, see the screenshot attached.
+
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61078
+
+**Attached**: {F14719}",1410209040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5vpeo4fnxwtoxb7qsyxu,task_description,duplicate
+"VisualEditor: Link icon stays selected but is not inserted, with language style text.","screenshot
+
+Environment- test2, beta
+
+1> open a page in VE, insert some text. Open the language inspector and click on link icon.
+2> Now click anywhere on the Editor and type in some more text, the language inspector closes but the link icon stays selected.See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14676}",1410192240,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-oaaxxaeryjuj676qlgup,task_description,declined
+"VisualEditor: Link icon stays selected but is not inserted, with language style text.","(In reply to etonkovidova from comment #1)
+> Checked in test2 on Chrome - cannot confirm.
+
+Not reproducible. close the issue.",1415642571,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-oaaxxaeryjuj676qlgup,task_subcomment,NA
+"VisualEditor: Link icon stays selected but is not inserted, with language style text.",Checked in test2 on Chrome - cannot confirm.,1415406839,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-oaaxxaeryjuj676qlgup,task_subcomment,NA
+VisualEditor:  Bad things happen when you paste cruft-laden text from somewhere else,"An editor pasted text at the newly created https://en.wikipedia.org/w/index.php?title=Kalles_Fraktaler&oldid=624532595
+
+which resulted in this when the page was saved:
+
+<object type=""cosymantecnisbfw"" cotype=""cs"" id=""cosymantecnisbfw"" style=""width: 0px; height: 0px; display: block;""></object><object type=""cosymantecnisbfw"" cotype=""bgpage"" id=""cosymantecnisbfwbg"" style=""width: 0px; height: 0px; display: block;""></object><script type=""text/javascript"" defer=""defer"" id=""NortonInternetSecurityBF"" tab=""0"" browser=""0"">function NavigateTo(url, newWindow) { var myObject = new Object(); myObject.url = url; myObject.newWindow = newWindow; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcBFNavigateTo', false, false, myObject); document.dispatchEvent(theEvent); } function ChangeToolbarIcon(inText, inImage) { var myObject = new Object(); myObject.text = inText; myObject.image = inImage; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('changeToolbarIconEventHandler', false, false, myObject); document.dispatchEvent(theEvent); } function DimPage() { dimElement = document.createElement('div'); dimElement.id = 'coShastaDimDiv'; dimElement.style.cssText = 'z-index:10;width:100%;height:100%;background-color:black;opacity:0.60;position:absolute;top:0;left:0;'; var theBody = document.getElementsByTagName('body')[0]; theBody.appendChild(dimElement); } function NPNNew() { theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcBFActivate', false, false, 0); document.dispatchEvent(theEvent); } function UpdatePageStatus(inURL) { var myObject = new Object(); myObject.blockURL = inURL; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('updatePageStatusEventHandler', false, false, myObject); document.dispatchEvent(theEvent);}function UpdateToolbarMenu(inSafeSearch) { var myObject = new Object(); myObject.SafeSearch = inSafeSearch; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('updateToolbarMenuEventHandler', false, false, myObject); document.dispatchEvent(theEvent);}function SetBarVisibility(barstatus) { var myObject = new Object(); myObject.barstatus = barstatus; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('setBarVisibilityEventHandler', false, false, myObject); document.dispatchEvent(theEvent);}function SetCachedStrings(inText, inImage, inTextNA, inImageNA) { var myObject = new Object(); myObject.text = inText; myObject.image = inImage; myObject.textNA = inTextNA; myObject.imageNA = inImageNA; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('setCachedStringsEventHandler', false, false, myObject); document.dispatchEvent(theEvent); } function SetResourceFolder(inFolder) { var myObject = new Object(); myObject.resFolder = inFolder; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('setResourceFolderEventHandler', false, false, myObject); document.dispatchEvent(theEvent); } function SetSafeSearchValues(isSSEinPrefs, isSSEinSafeMgr,isBuzz, showMyAccount) { var myObject = new Object(); myObject.showMyAccount = showMyAccount; myObject.isSSEinPrefs = isSSEinPrefs; myObject.isBuzz=isBuzz; myObject.isSSEinSafeMgr=isSSEinSafeMgr; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('setSafeSearchValuesEventHandler', false, false, myObject); document.dispatchEvent(theEvent); } function ShowSafeSearchOffering() {theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcShowSafeSearchOffering', false, false, 0); document.dispatchEvent(theEvent); } function SafeSearchOfferResponded() {theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcSafeSearchOfferResponded', false, false, 0); document.dispatchEvent(theEvent); } function SetSearchString(inQuery) { var myObject = new Object(); myObject.query = inQuery; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcSetSearchString', false, false, myObject); document.dispatchEvent(theEvent); } </script><object type=""cosymantecnisbfw"" cotype=""cs"" id=""SILOBFWOBJECTID"" style=""width: 0px; height: 0px; display: block;""></object> Kalles Fraktaler is a Windows-based fractal zoom computer program used for zooming into the Mandelbrot set or the Burning Ship fractal. <object type=""cosymantecnisbfw"" cotype=""cs"" id=""SILOBFWOBJECTID"" style=""width: 0px; height: 0px; display: block;""></object>
+
+cosymantecnisbfw appears to be related to NortonInternetSecurityBF
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410129540,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yb4podernpcrt5eyrrqt,task_description,resolved
+VisualEditor:  Bad things happen when you paste cruft-laden text from somewhere else,"
+
+*** This bug has been marked as a duplicate of bug 63229 ***",1410130325,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yb4podernpcrt5eyrrqt,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21]TypeError: boundingRect is undefined and TypeError: surfaceRect is undefined appears when opening Media Settings dialog,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+
+Observed Result:
+The following errors are appearing in the console:
+
+
+TypeError: boundingRect is undefined
+
+TypeError: surfaceRect is undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15082}",1409946720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4irstsowbqex2mh6wzgk,task_description,invalid
+VisualEditor: [Regression pre-wmf21]TypeError: boundingRect is undefined and TypeError: surfaceRect is undefined appears when opening Media Settings dialog,"Yes, working fine now",1409959016,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4irstsowbqex2mh6wzgk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21]TypeError: boundingRect is undefined and TypeError: surfaceRect is undefined appears when opening Media Settings dialog,This was fixed by https://gerrit.wikimedia.org/r/#/c/158519/ but not pulled through. Sorry! It's pulled through now.,1409952229,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4irstsowbqex2mh6wzgk,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.","screenshot1
+
+1> open a blank page in VE, open the Language inspector. 
+2> Now click anywhere in the Editor, the inspector stays open but the language style text drop-down selection turns blank. After that any selection you make, it continues to stay blank. And if you type in any text, a pawn gets inserted beside the text. See screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F15074}",1409943780,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-mwpy2efniouotho4t26d,task_description,declined
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.",Per submitter.,1415143058,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.",Not reproducible.,1415108215,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.","Apologies.. here are the steps-
+
+1> open a blank page in VE, open the Language inspector and select a text style from the drop-down,for ex- select Heading.
+2> Now click anywhere in the Editor, the inspector  closes, but the text style drop-down selection turns blank. After that any selection you make, it continues to stay blank. And if you type in any text, a pawn gets inserted beside the text. See screenshots.
+
+Delete the text and the pawn character and reapeat steps #1 and 2, JS console error is ""Uncaught Error: Offset could not be translated to a DOM element and offset: 3"".",1410208205,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.","After deleting the text and pawn characters as mentioned in the steps above when i  repeat the steps #1 and #2, i get this console error 
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 3",1409944218,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.",Environment-test2,1409943850,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.","Created attachment 16388
+screenshot2
+
+**Attached**: {F15075}",1409943820,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+VisualEditor: comment feature should be removed by default,"<!-- comments are not recommended for users: it is hidden!  -->
+
+Comments aren't recommended for new editors (and for 99% of the times for advanced users too), as must comments should be written in talk page.
+
+It is not just a non useful feature, it is a harmful feature, as people get confused between reference and comments and it leads to ""too many icons"" problem. Please remove comment button from toolbar completely, or at least change it to opt-in/out feature.  (Only the toolbar icon, as the option to show and edit already written comments is important)
+
+Side benefit: less code to maintain and less bugs ;)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1409923860,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-c4uueulkx7xekhb35rdo,task_description,declined
+VisualEditor: comment feature should be removed by default,"James, comments are great to VIEW & EDIT, but there is no reason to ADD comments in VE. Please consider removing the button, as new editors don't understand what is ""comment"" (they use it instead of citation).",1410209524,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-c4uueulkx7xekhb35rdo,task_subcomment,NA
+VisualEditor: comment feature should be removed by default,"(In reply to Eran Roz from comment #0)
+> <!-- comments are not recommended for users: it is hidden!  -->
+> 
+> Comments aren't recommended for new editors (and for 99% of the times for
+> advanced users too), as must comments should be written in talk page.
+
+The principal use of HTML comments in articles is to warn new editors to not do something that seems ""obvious"" but there is talk-page consensus to not do. This was a very widely-requested pain point from experienced editors who felt now showing the comments was very damaging to new users' expereience. Hiding comments which are there for new users seems like the wrong way around…
+
+Long term, this will hopefully be replaced by a proper in-editor discussion system, but until that's done, this will have to do.",1410198549,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c4uueulkx7xekhb35rdo,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,"**Author:** `gryllida`
+
+**Description:**
+I'd like to enable a new beta feature on a wiki, but I wouldn't like the users to enable it thoughtlessly, as it currently breaks a lot of things. For this reason, I'd like to be able to append a 'do NOT use this! only for developers' note to such beta feature in the beta tab.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409922720,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ack5uaxekj6oz3tbot5c,task_description,declined
+BetaFeatures should have means to provide a custom note on-wiki,"(In reply to Gryllida from comment #4)
+> James Forrester, I expected you to be most familiar with the context here --
+> installation of visualeditor at non-Wikipedias as a sort-of-pre-beta
+> feature, while people script visualeditor to suit the project needs.
+
+This is the very first time you've suggested it, so no, I'm not remotely familiar with your idea. :-)",1410060066,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,"**gryllida** wrote:
+
+James Forrester, I expected you to be most familiar with the context here -- installation of visualeditor at non-Wikipedias as a sort-of-pre-beta feature, while people script visualeditor to suit the project needs.
+
+If it's put as a beta feature, a lot of people will enable it and make edits that break things or at least don't provide the relevant features (for wikipedias, this is the common use of <ref> tag, for instance; for its sisters, it's a need in other toolbar buttons and often lack of need in <ref> tag in the first place).",1409969828,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,"If there are severe issues that would ""break a lot of things"" it's not ready to be a Beta Feature and for WMF servers we wouldn't let it go live. Consequently I don't see a valid use case and am marking as WONTFIX.",1409950426,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,Editing the MediaWiki messages isn't good enough?,1409948431,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,"Hmm. Does that sound like a common usecase, or rather like something that you could hack up yourself if really wanted? I don't know...",1409925140,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+"VisualEditor bugs: wikilinks, tables, nowiki and other","VisualEditor editor is full of bugs. Since his implementation i have disabled it for me, because, as experimented user i just like to edit clean code.
+So, i noticed folowing bugs
+when you edit a part of a wikilink (termination) visual editor leaves old wikilink as adrress and only add new edited variant as label. For example if you want to correct digit of an wikilinked year - your action will just add a correct label but wikilink will be the same, old.
+I first noticed this on rowiki when anonymous users edited wikipedia. One fresh example can be this https://ro.wikipedia.org/w/index.php?title=Gustar_%28festival%29&diff=8812463&oldid=8805982
+Now i tested myself this ""phenomenon"" on test2wiki and i obtained the same result
+https://test2.wikipedia.org/w/index.php?title=Edit_page_for_firefox&diff=104063&oldid=104062
+
+Other bug: when you try to remove title of a section from a page (for merging 2 sections), visual editor removes only caption but it keeps the real section heading (====) and adds between equal sign an ""<nowiki/>"". The result will be ==<nowiki/>== and section will exist further without title. Test edit: https://test2.wikipedia.org/w/index.php?title=New_page_for_bugzilla&diff=104066&oldid=104065
+
+Also there exists some problems when copying of tables in a page edited via VisualEditor. VisualEditor adds again some <nowiki> </nowiki> tags, and in some cases adds magic words like __INDEX__ and __NEWSECTIONLINK__
+Example (real edit on rowiki): https://ro.wikipedia.org/w/index.php?title=Kiesza&diff=next&oldid=8808818
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1409835300,PHID-USER-kzriyxckmvupw2nlyshe,PHID-TASK-i3da234yo25qxkfj7b4k,task_description,resolved
+"VisualEditor bugs: wikilinks, tables, nowiki and other","I noticed again a bug related to <nowiki/>
+
+Some user tried several times to add image and each time image (code) was put betweeen <nowiki/> tags
+Diffs:
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969441&oldid=8969436
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969445&oldid=8969444
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969449&oldid=8969448",1419347371,PHID-USER-kzriyxckmvupw2nlyshe,PHID-TASK-i3da234yo25qxkfj7b4k,task_subcomment,NA
+"VisualEditor bugs: wikilinks, tables, nowiki and other","Again noticed bug related to <nowiki/>
+
+Some user tried several times to add image and each time image (code) was put betweeen <nowiki/> tags
+Diffs:
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969441&oldid=8969436
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969445&oldid=8969444
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969449&oldid=8969448",1419347343,PHID-USER-kzriyxckmvupw2nlyshe,PHID-TASK-i3da234yo25qxkfj7b4k,task_subcomment,NA
+"VisualEditor bugs: wikilinks, tables, nowiki and other","Thanks for posting this.
+
+The first problem is ""working as designed"", but the design is seriously being discussed because of exactly this problem.  This item is best described as a duplicate of multiple other bug reports.  See bug 48789 for a list of most open link-related bugs.
+
+The second problem is bug 50100.  Also, this is what you'd expect from a word processor (like Microsoft Word):  if you type ""My Title"" and set bold formatting or a large font size on those words, and then you remove all the letters on that line, and start typing again, then you do expect the font size and bold formatting to be retained.  This report is a duplicate.
+
+On the third one (the table in ro.wp's [[Kiesza]]), it appears that the editor copied the wikitext code out of en.wp's article, and pasted it directly into VisualEditor.  VisualEditor then assumes that you wanted this pasted text to display (i.e., as if you were writing a help page telling someone what wikitext to type, so you really wanted the wikitext on the page).  Magic words can be set in VisualEditor by going to the Page options menu, choosing ""Advanced settings"", and clicking the buttons to turn on those magic words.  This report should be closed as ""working as designed"".
+
+I'm going to mark the whole thing as ""Resolved"", but without trying to specify it as a duplicate, because I don't know if Bugzilla can handle multiple duplicate numbers.  If you have other questions, then please feel free to follow up at those other open bugs.",1410804889,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-i3da234yo25qxkfj7b4k,task_subcomment,NA
+"VisualEditor bugs: wikilinks, tables, nowiki and other","Please file only one specific problem per report and stick to the topic (general complaints about perceived quality of software can go to wikis, mailing lists, blogs). https://www.mediawiki.org/wiki/How_to_report_a_bug might come handy. Thanks.",1409839210,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-i3da234yo25qxkfj7b4k,task_subcomment,NA
+VisualEditor:  Do not permit empty section headings (wikitext like == == or similar),"Sometimes users set the format of a line to be a == Section heading ==, but never put anything in it.  In that case, the section heading formatting should be removed.  There's no good reason to have == == or === === by itself on a line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409787120,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-n3nv2432ws3qayvnnhn2,task_description,resolved
+VisualEditor:  Do not permit empty section headings (wikitext like == == or similar),"
+
+*** This bug has been marked as a duplicate of bug 49452 ***",1415886608,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n3nv2432ws3qayvnnhn2,task_subcomment,NA
+Page Options Dialog width is not wide enough,"**Author:** `josephsieh`
+
+**Description:**
+On http://en.wikipedia.beta.wmflabs.org/wiki/Cite_VisualEditor_Test?veaction=edit, when you click on the ""Page Options"" icon, the pop-up page options dialog appears to be too narrow.  Characters are missing.
+
+OS X 10.9.4.
+Safari 7.0.6
+Firefox 32.0
+
+visual editor version: https://git.wikimedia.org/tree/mediawiki%2Fextensions%2FVisualEditor.git/bfbe8cbbebe0a461d0ee68c0491b901507636fe2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1409704920,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pidkwinuimfpigrlcpjx,task_description,resolved
+Page Options Dialog width is not wide enough,"Yeah, this is a painful issue; merging with bug 57366.
+
+*** This bug has been marked as a duplicate of bug 57366 ***",1409767558,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pidkwinuimfpigrlcpjx,task_subcomment,NA
+Page Options Dialog width is not wide enough,"**josephsieh** wrote:
+
+Screen shot
+
+**Attached**: {F14703}",1409704989,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pidkwinuimfpigrlcpjx,task_subcomment,NA
+VisualEditor:  Adding a template to a redirect did not let me save the page,"Steps taken:
+
+1.  Open a redirect to edit.
+
+2.  Add a template:  {{R from other languages}}
+
+3.  Discover that I can't save.  The green 'save' button is still gray and non-functional.
+
+4.  Mash the keyboard to add some text to the page.  
+
+5.  Still can't save.  Give up and cancel the edit.
+
+
+This happened in Firefox on my Mac; when I closed the page and tried again, it worked correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409696880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-c5xlvoaq4xlahtprsd7f,task_description,resolved
+VisualEditor:  Adding a template to a redirect did not let me save the page,"Sounds like the editor had crashed by the time you added the template… Can't reproduce now, however. :-(",1423675003,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c5xlvoaq4xlahtprsd7f,task_subcomment,NA
+VisualEditor:  Adding a template to a redirect did not let me save the page,"Created attachment 16345
+Screenshot showing the template that I just added (highlighted in blue) and the still-gray 'Save' button
+
+**Attached**: {F14679}",1409697055,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-c5xlvoaq4xlahtprsd7f,task_subcomment,NA
+"VisualEditor:  When image search results are returned very slowly, remove the ""No results found"" error message","""No results found"" overlaps with the results that were found
+
+Steps to reproduce:
+
+1.  Open VisualEditor and Insert > Media
+
+2.  Search for File:Alf Cooke's Packaging Factory - Hunslet Road - geograph.org.uk - 483165.jpg 
+
+3.  Nothing happens:  ""No results found"".
+
+4.  Spend a few moments grumbling about the stupidity of a search tool that cannot find a file even when you give it the complete and exact file name.
+
+5.  Spend a few moments groaning because there's no way to add this image unless the search tool can find it, even when you know the exact file name.
+
+6.  Hey!  Search finally found the image!  Why does VisualEditor still say ""No results found"" on top of the results?
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14693}",1409620980,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-buxz75urt74gcutli3bm,task_description,resolved
+"VisualEditor:  When image search results are returned very slowly, remove the ""No results found"" error message","
+
+*** This bug has been marked as a duplicate of bug 67438 ***",1409669754,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-buxz75urt74gcutli3bm,task_subcomment,NA
+VisualEditor: inserted special characters doesn't respect the surrounding text formatting,"To reproduce:
+
+1. Write text. Make it bold.
+2. Put the caret in the middle of the bold text.
+3. Insert a special character.
+
+Actual: The inserted character is not bold.
+
+Expected: The inserted character is bold like the surrounding text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409595060,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-a3kbjn7bnws47ljk6ywa,task_description,resolved
+VisualEditor: inserted special characters doesn't respect the surrounding text formatting,"
+
+*** This bug has been marked as a duplicate of bug 60476 ***",1409596086,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a3kbjn7bnws47ljk6ywa,task_subcomment,NA
+VisualEditor: inserted special characters doesn't respect the surrounding text formatting,"Change 157703 had a related patch set uploaded by Esanders:
+Annotate inserted special characters
+
+https://gerrit.wikimedia.org/r/157703",1409595941,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a3kbjn7bnws47ljk6ywa,task_subcomment,NA
+VisualEditor:  Be able to copy the name of an image,"Sometimes you want to re-use an image (or otherwise need to know its name).  Some file names are too long to display in the tab.  It would be nice if something in the media dialog box exposed the name of the file, so that it could be copied.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409542860,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-2clz3t46qatency62ael,task_description,duplicate
+Link target choice box scroll bar does not work,"If VisualEditor is used to introduce a link (Ctrl-K) and the list of suggested link targets is long enough to require a scroll bar, this scroll bar cannot be used: clicking on it immediately closes the target list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7",1409432400,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_description,resolved
+Link target choice box scroll bar does not work,"Merging into bug 65774.
+
+*** This bug has been marked as a duplicate of bug 65774 ***",1415807855,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_subcomment,NA
+Link target choice box scroll bar does not work,"Just noticed that the (non-functional) scroll bar is only shown if the target list is displayed too far down on the screen. Otherwise, the list just contains 10 items and no scroll bar. To test on mediawiki.org: start a new empty link with Ctrl-K and type R.",1409671182,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_subcomment,NA
+Link target choice box scroll bar does not work,"(Notice that using the mouse wheel works as intended, at least in the categories' case, so assuming it's the same bug we'll need to edit its title.)",1409662547,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_subcomment,NA
+Link target choice box scroll bar does not work,"I don't have examples for the link tool, but can confirm in the categories' one.",1409662111,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_subcomment,NA
+VisualEditor: Incorrect highlight while trying to add reference in a slug,"Screenshot
+
+The highlight that appears after inserting a reference in a slug is pretty weird.
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14232}",1409086200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ukh27frjetxrfd5snx42,task_description,resolved
+VisualEditor: Incorrect highlight while trying to add reference in a slug,"That bug is T89192, this particular issue was fixed with staging.",1423749557,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ukh27frjetxrfd5snx42,task_subcomment,NA
+VisualEditor: Incorrect highlight while trying to add reference in a slug,"Breaks even worse at the moment, appears to corrupt the document CE node.",1423749431,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ukh27frjetxrfd5snx42,task_subcomment,NA
+VisualEditor: Incorrect highlight while trying to add reference in a slug,Breaks even worse at the moment.,1423749379,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ukh27frjetxrfd5snx42,task_subcomment,NA
+VisualEditor: Incorrect highlight while trying to add reference in a slug,"It seems that if you insert a reference into a slug, the selection ends up as |<p>, <ref>, </ref>, </p>| rather than <p>, |<ref>, </ref>|, </p>
+
+We should see how this behaves in Ed's ""Stage slugs"" code, though, because that's the future.",1409164870,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ukh27frjetxrfd5snx42,task_subcomment,NA
+VisualEditor:  Hung while trying to save,"This edit was actually saved, but it seemed like it wouldn't be at the time:  https://en.wikipedia.org/w/index.php?title=Integrated_circuit&diff=622517186&oldid=622152913
+
+
+The report was this:
+
+Error saving to server: Empty server response
+
+Hangs when editing ""Integrated circuit"" page - section SSI, MSI and LSI - tried to remove redirect wikilinks to SSI, MSI and LSI (keywords). Chrome 36.0.1985.143 m, Win7 64bit Kozuch (talk) 21:08, 23 August 2014 (UTC)
+
+Hi, I see my edit was saved, but probably was later than what my patience allowed me to wait for :). I was looking at page history before cancelling the edit save, but it was not there, probably shower up later. VE interaction definitely ended up deadly though (hung on the ""saving"" dialog and when I canceled it the above error just was quickly show and then dialog closed by itself.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409007600,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kgomrdkqhh5iwoae4w4d,task_description,invalid
+VisualEditor:  Hung while trying to save,"This bug could not be reproduced and is now three years old, and was probably a random transient issue, so I'm closing.",1513167493,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-kgomrdkqhh5iwoae4w4d,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"http://bits.beta.wmflabs.org is entirely down with 503.  E.g.:
+
+http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=true&lang=en&modules=ext.visualEditor.viewPageTarget.noscript&only=styles&skin=vector&*
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408737480,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nu7ca5igwfzpwjjvumze,task_description,resolved
+bits.beta.wmflabs.org down with 503,"Still working for me.  If you still get a 503, please re-open, and add the URL and error text you get.",1409777765,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"**physik** wrote:
+
+It worked fine this morning but now I'm getting 503 again.
+It's somehow hard to decide when a Temporarily bug has been fixed.",1408982845,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"The link works for me now, so it seems fixed.  If it is still broken when you test, please re-open.",1408937112,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"**physik** wrote:
+
+The link seems to be still broken (503).",1408792371,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"**gerritadmin** wrote:
+
+Change 155806 merged by BBlack:
+declare hhvm_appservers lvs service ip for labs, too
+
+https://gerrit.wikimedia.org/r/155806",1408739606,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"**gerritadmin** wrote:
+
+Change 155806 had a related patch set uploaded by Ori.livneh:
+declare hhvm_appservers lvs service ip for labs, too
+
+https://gerrit.wikimedia.org/r/155806",1408739331,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+VisualEditor: Language selector should be able to use div,"Currently language selector adds <span lang="".."" dir=""...""> which is good for multiple words. However, sometimes longer text such as [few] paragraphs, lists etc should be makred as different language, and in this case it should wrap it with div.
+
+Example: https://he.wikipedia.org/wiki/%D7%A9%D7%9E%D7%A2%D7%95%D7%9F_%D7%90%D7%95%D7%9C%D7%9E%D7%9F?veaction=edit&uselang=en - the second title is ""Books"" and since all the books are in English, the whole list should be wrapped with <div lang=""en"" dir=""ltr"">.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408703280,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-auvoatapd5phg6h74xvs,task_description,resolved
+VisualEditor: Language selector should be able to use div,"Merging with bug 60187; this will require a major amount of work to provide a block-level editing concept more widely, of which this is the most obvious (but not sole) user.
+
+*** This bug has been marked as a duplicate of bug 60187 ***",1408734760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-auvoatapd5phg6h74xvs,task_subcomment,NA
+"Media: bogus ""no results found"" message when searching media returns results","bogus ""no results"" found in Media interface
+
+Seen if Firefox, less so in Chrome
+
+On any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit 
+
+Click Insert/Media.  Message ""no results found"" appears.
+
+Search for media that returns results.  ""no results found"" message persists. See screen shot. 
+
+In Chrome, ""no results found"" flickers but ultimately disappears when media thumbs are displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14384}",1408656900,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-xez3lpoguhhnw27ay3na,task_description,resolved
+"Media: bogus ""no results found"" message when searching media returns results","(In reply to Chris McMahon from comment #1)
+> Also note that search results for Media in Firefox are different than in
+> Chrome, and Firefox seems to be less correct.
+
+Search results is a Cirrus problem. :-) But yeah.",1408657073,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xez3lpoguhhnw27ay3na,task_subcomment,NA
+"Media: bogus ""no results found"" message when searching media returns results","
+
+*** This bug has been marked as a duplicate of bug 67438 ***",1408657052,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xez3lpoguhhnw27ay3na,task_subcomment,NA
+"Media: bogus ""no results found"" message when searching media returns results","Also note that search results for Media in Firefox are different than in Chrome, and Firefox seems to be less correct.",1408657028,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-xez3lpoguhhnw27ay3na,task_subcomment,NA
+VisualEditor:  Adding text to a category resulted in an extra section heading with span tags,"I have not been able to reproduce this at en.wikipedia.beta, and I didn't want to edit live category pages for testing.
+
+In Firefox, I added a line of text.  VisualEditor added a level 1 section headign after it:
+
+= <span dir=""auto"">Category:Medical and health organizations</span> =
+
+You can see the diff here:  https://en.wikipedia.org/w/index.php?diff=621943590&oldid=615616525
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408562400,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5hcwojrrrykznqwemq5q,task_description,resolved
+VisualEditor:  Adding text to a category resulted in an extra section heading with span tags,"Inclined to mark it as resolved since it seems to be fixed.
+
+Instead of 
+```<h1><a href=""#Category:Medical_and_health_organizations"" class=""mw-headline-anchor"" aria-hidden=""true"" title=""Link to this section"">§</a>
+<span class=""mw-headline"" id=""Category:Medical_and_health_organizations"">
+<span dir=""auto"">Category:Medical and health organizations</span></span></h1>```
+
+when testing  span dir=""auto"" is not added anymore: 
+
+```<h1><a href=""#Category:Medical_and_health_organizations"" class=""mw-headline-anchor"" aria-hidden=""true"" title=""Link to this section"">§</a>
+<span class=""mw-headline"" id=""Category:Medical_and_health_organizations"">
+Category:Medical and health organizations</a></span></h1>```
+<h1>
+<a href=""#Some_page_titile"" class=""mw-headline-anchor"" aria-hidden=""true"" title=""Link to this section"">§</a>
+<span class=""mw-headline"" id=""Some_page_titile"">Some page titile</span></h1>",1425596458,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5hcwojrrrykznqwemq5q,task_subcomment,NA
+VisualEditor:  Adding text to a category resulted in an extra section heading with span tags,"We fixed this a while ago, I think.",1425594010,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5hcwojrrrykznqwemq5q,task_subcomment,NA
+"VisualEditor: The custom tab does not get enabled after making an image of type ""Frame"" to full size","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Change the type of the image to ""Frame""
+4.Click on ""Apply Changes""
+5.Reopen the media settings dialog for that image
+
+Observe that the ""Make full size"" button is now active
+Click on that.
+The Custom tab does not get enabled, even though the size has just been customized by making it full size.
+
+Environment:Betalabs
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408557240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ppa4557zfmdweuq2ycvp,task_description,resolved
+"VisualEditor: The custom tab does not get enabled after making an image of type ""Frame"" to full size",Correct MediaWiki behaviour.,1423675100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ppa4557zfmdweuq2ycvp,task_subcomment,NA
+VisualEditor: Suggest templates more proactively in the template adding dialog,"Currently, in the template adding dialog there is just one search box and a lot of empty space.
+
+A user needs to know the name of the template to insert.
+
+A template could be suggested in a more proactive way. One idea can be to simply show the currently available templates by category, starting from the top and let the user drill down (in enwiki the top is https://en.wikipedia.org/wiki/Category:Wikipedia_templates ; the top category should probably be defined in a wg variable). This will require each project to maintain their templates neatly categorized, but this should be done anyway ;)
+
+Another possibility is to let the projects define lists of commonly used templates, or to show a list of the most frequently transcluded ones.
+
+[And see also the trivial bug 69692.]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408550460,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-p5prxsfn6jdj43jb5hhk,task_description,resolved
+VisualEditor: Suggest templates more proactively in the template adding dialog,"I think this is bug 53590.
+
+*** This bug has been marked as a duplicate of bug 53590 ***",1408571387,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p5prxsfn6jdj43jb5hhk,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"The Hebrew Wikipedia, as well as a few others, have a gadget for canned edit summaries:
+https://he.wikipedia.org/wiki/MediaWiki:Gadget-Summarieslist.js
+
+If the forceeditsummary user preference is enabled and the user uses this gadget to insert a summary, the warning about an empty edit summary is issued, even though it shouldn't.
+
+I suspect that the problem is in the VE code.
+As far as I can see, this preference is checked in
+modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.js on line 867
+and the summary values are not what I expect them to be.
+
+(See also Bug 52085.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408466400,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-giznvs23bxpaswgircgp,task_description,declined
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Hmm. That is actually a very good point. Talked with @trevorparscal and you have us both convinced.
+
+Let's file a separate task for this (filed T86868), I'll adapt your patch ({F14710} from T71749#745592) for other InputWidgets.",1421283561,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Sync of the value to the DOM can be done in lazy way on the getValue() (so timer polling isn't really needed...)
+
+What is the correct policy to handle DOM value not equal to the OOUI widgets? Don't know but here are some possible options
+* Trigger change event - this is what I suggested above. This is WYSIWYG - you see X in DOM, X would be the value in the widget.
+* Raise exception - If you fear the above is too dangerous, and this moves the responsibility to the script writter but let him know
+* log.warning(...) - If OOUI lost DOM synchronization too often to raise exceptions. If this is the case then OOUI is probably broken.
+",1421181572,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Documented how/where? I'd be happy to if you come up with a sensible way to do it. :) (This isn't really a supported use-case for OOUI, but it's useful and people are going to do it anyway, so documenting something would make sense.)
+
+Just to be clear, when you modify `.value` from JavaScript (or use jQuery's `.val()`, etc.), there's literally no way for VisualEditor or any other script to pick up the changes in real-time (which we need for things like validation of the inputted values), unless you trigger a 'change' event or something like that (well, short of polling for changes every 100 ms or so, but let's not do that please). That's just how this works, whether we like it or not.",1421179322,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Documented how/where? I'd be happy to if you come up with a sensible way to do it. :) (This isn't really a supported use-case for OOUI, but it's useful and people are going to do it anyway, so documenting something would make sense.)
+
+Just to be clear, when you modify `.value` from JavaScript (or use jQuery's `.val()`, etc.), there's literally no way for VisualEditor or any other script to pick up the changes, unless you trigger a 'change' event or something like that (well, short of polling for changes every 100 ms or so, but let's not do that please). That's just how this works, whether we like it or not.",1421179274,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),Per Bartosz.,1421025800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"At least it should be documented properly.
+Usually  the UI should be consistent with the DOM.",1421004471,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"I think this should be closed as invalid. Like Trevor said above, the script should call `.trigger( 'change' )` on the <input/> node.
+
+We could change #getValue to actually get the .value of the <input/> every time (like in the proposed patch), rather than relying on the cached one, but any scripts interacting with input fields //must trigger the 'change' event anyway//; there's more machinery that often depends on this – in this particular case, the script that limits the length of edit summary to 255 bytes.
+
+It is a bit weird that OOUI widgets rely on events only to update their internal state, but that's intentional per Trevor's design and I think the design is sensible. It can result in the state of the widget becoming inconsistent with the state of the DOM node when other scripts modify it without triggering events, but on the other hand it ensures that the state of the widget itself is //internally// consistent.",1420984193,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),Isn't this an OOjs UI thing?,1420938082,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"There are actually several reasons for the setTimeout, but the real problem here is that getValue compensating for not noticing the value changed previously causes other issues.
+
+The OO.ui.TextInputWidget has a ""change"" event, which is depended on by other systems. If we just make getValue compensate for not noticing the value changed previously, then systems depending the aggregated change event will behave incorrectly. The best way to handle this is to either trigger the event or come up with a way to access the input. We could, for instance, leave references to widgets in the elements using jQuery.data().",1408476850,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"This is onEdit function  (with setTimeout) that protect against browsers mishaps if I understand correctly.
+
+BTW - don't scar to change getValue, as it is used only in ~35 places in the code ;)",1408476130,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"The problem is that we really should be caching the value; it's done to protect the behavior against a lot of event triggering and browser mishaps that otherwise would make interaction with inputs pretty horrible.
+
+We can't have ooui deal with the jQuery element directly; if you notice, htere's also a SetTimeout() method inside 'setValue' -- that's on purpose to make sure that if the user types quickly we don't emit crazy amount of events. Changing ooui to deal with the jQuery element's value directly will remove a lot of its intended functionality.",1408475612,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"@Trevor Parscal, I already fixed it with triggering input event. However it should be fixed in oojs-ui itself for later cases.
+The browser should not emit event in this case (see RFC: http://www.w3.org/TR/html401/interact/scripts.html#adef-onchange), and even if the spec was the other way - oojs-ui can't blame browsers...",1408475334,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"The problem is actually to do with the fact that the browser isn't emitting events when it should. OOjs UI is listening for the change event.
+
+Just use:
+
+$input.val( newValue ).trigger( 'change' );",1408474763,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Created attachment 16237
+Fix for oojs-ui
+
+Attaching a proposed patch for oojs-ui.
+
+**Attached**: {F14710}",1408473504,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Fixed by triggering manually input event.
+
+However oojs-ui should use the widget value to get must up to date value (e.g protype.getValue( return this.widget.val(); ), and not to be based on some cached variable.
+If it does something smart with the value it can be check that if this.value !=this.widget.val()  then it should trigger the function for updating this.value, before actually return the widget value.",1408472348,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Got it.
+
+The issue was a mixup between dealing directly with the textarea object through jQuery (which updates .val()) and dealing with VE's OOUI elements (which update through .setValue() )
+
+I've created a fix to the gadget, but I don't have the permissions to edit it. I've asked Eran to take a look and implement the fix.",1408470567,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"This gets a bit weirder for me. It seems that with the gadget that summaries aren't saved at all, even if I type something manually in the textbox, and this behavior is inconsistent:
+
+If I add automatic summaries from the buttons and save, the summary isn't saved.
+If I add automatic summaries from the buttons and then add a text, they are saved as a summary. 
+If I add a summary by hand, it isn't saved.
+
+I'm not sure what would cause this to happen; the gadget fills in automatic text by adding into the textbox.val() which should make this work.",1408467289,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: Provide content-based descriptions when focusing references or templates,"In particular we've had a community request to display a citation summary when focusing citation nodes.
+
+We could list template values in order until we run out of room, but this may not lead to desirable results, for example the first parameter in {{Cite web}} is URL.
+
+A more complex solution would be to come up with a format for defining how to generate the summary of a template and store it in template data, either as a value on the column (summary order):
+
+Field     Desc  Summary order
+url       ...   null
+publisher ...   2
+title     ...   1
+date      ...   3
+month     ...   null
+
+A simplified version of this would just flag one field as being used in the summary.
+
+etc.
+
+Or as a string concatenation message somewhere:
+
+""{{{title}}}, {{{publisher}}} - {{{date}}}""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408463340,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-iboqexwepmrgmkfwmdpm,task_description,resolved
+VisualEditor: Provide content-based descriptions when focusing references or templates,Clearly I was protecting against typos in the bug number :),1408464073,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-iboqexwepmrgmkfwmdpm,task_subcomment,NA
+VisualEditor: Provide content-based descriptions when focusing references or templates,"I'm going crazy...
+
+*** This bug has been marked as a duplicate of bug 69474 ***",1408464025,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-iboqexwepmrgmkfwmdpm,task_subcomment,NA
+VisualEditor: Provide content-based descriptions when focusing references or templates,"Is this the same thing as bug 69474? (You filed that one too, and the bug numbers are confusingly similar. :D)",1408463781,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-iboqexwepmrgmkfwmdpm,task_subcomment,NA
+"VisualEditor:  After you create a link and close the link inspector, please de-select the newly linked text","Steps to reproduce:
+
+1.  Type some text:  ""Foo bar baz bat""
+
+2.  Select the last word, because you want to create a wikilink before you finish typing the sentence.
+
+3.  Type Command-K to create a link.  
+
+4.  Make a link.  Click ""Done"".
+
+5.  Finish typing the sentence.
+
+6.  Oops, where did [[bat]] go?
+
+
+Results:
+
+When you exit the link inspector, the linked text remains highlighted, and typing results in it being overwritten by your next character.  
+
+Expectation:  after I've made a link, de-select the link and put the cursor at the end of the word, so I can keep writing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408389720,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kmwl4sqnbhfoukhb367a,task_description,declined
+"VisualEditor:  After you create a link and close the link inspector, please de-select the newly linked text",We've intentionally chosen this behaviour after a huge amount of user and product research.,1423675223,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kmwl4sqnbhfoukhb367a,task_subcomment,NA
+VisualEditor: Dropdown menu shows scrollbars,"screenshot of the problem
+
+Confirmed this on Safari 7, mac, Vector and Firefox 31, Windows 7, Monobook
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54705
+
+**Attached**: {F14614}",1408380300,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-5iagtk7ef7sicdms3ksc,task_description,resolved
+VisualEditor: Dropdown menu shows scrollbars,"Merging into bug 57366 (FIXED).
+
+*** This bug has been marked as a duplicate of bug 57366 ***",1409892989,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5iagtk7ef7sicdms3ksc,task_subcomment,NA
+VisualEditor: Dropdown menu shows scrollbars,I guess this became a problem when the cancel button was removed.,1409836500,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-5iagtk7ef7sicdms3ksc,task_subcomment,NA
+VisualEditor: Dropdown menu shows scrollbars,"The clipping is correct, but we aren't repositioning for the edge of the screen, like we do with link inspectors (context popups).",1408648098,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5iagtk7ef7sicdms3ksc,task_subcomment,NA
+VisualEditor: Dropdown menu shows scrollbars,Also Firefox 30 on a Mac.  I suspect that it's everywhere.  This problem has been present for at least a few weeks.,1408391451,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5iagtk7ef7sicdms3ksc,task_subcomment,NA
+VisualEditor: allow parameter per line in inserted templates,"It is customary for big templates with a lot of parameters, such as infoboxes, to have each parameter written on a separate line in the wiki source code.
+
+If I am not mistaken, VE inserts all templates in one long line.
+
+As long as source code editing is common, VE should insert templates according to the above community practice.
+
+How to know whether to insert one line or multiple lines? Either do it with multiple lines if there are more than x parameters, say 4, or have a parameter in template data that suggests multiline insertion.
+
+**See Also**:
+* {T52584}",1408335060,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-jr2a2h6e2iclnvx4wa2e,task_description,duplicate
+VisualEditor: allow parameter per line in inserted templates,"It seems that VE users still get [[https://fi.wikipedia.org/wiki/Keskustelu_k%C3%A4ytt%C3%A4j%C3%A4st%C3%A4:Kuriuss#Infolaatikot | yelled at]] for this (or perhaps that was rather a manifestation of T52584, because in the offending edits - [[https://fi.wikipedia.org/w/index.php?title=Resedakasvit&diff=prev&oldid=14486819 |example]] - the parameters were already present).",1427240949,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-jr2a2h6e2iclnvx4wa2e,task_subcomment,NA
+VisualEditor:  Pasting a link label causes the link to split,"What I started with was a link to a disambiguation page:
+
+  Foo bar [[CML]] baz bat.
+
+
+What I wanted was a link to a real article, so I repointed the link:
+
+  Foo bar [[chronic myelogenous leukemia|CML]] baz bat.
+
+
+Hmm, that initialism doesn't appear to be expanded anywhere on the page.  Okay, what we need is:
+
+  Foo bar [[chronic myelogenous leukemia]] baz bat.
+
+
+So I copied the long name out of the link tool's field, and pasted it into the middle.  It produced:
+
+  Foo bar [[chronic myelogenous leukemia|CM]]chronic myelogenous leukemia[[chronic myelogenous leukemia|L]] baz bat.
+
+None of this would have been so difficult if we could edit labels in the link tool, in a separate box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408236960,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-2o5afywhjm53xfqkmeux,task_description,resolved
+VisualEditor:  Pasting a link label causes the link to split,"This is because of bug 48720. Grumble.
+
+*** This bug has been marked as a duplicate of bug 48720 ***",1408272633,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2o5afywhjm53xfqkmeux,task_subcomment,NA
+firsteditve no longer points to VisualEditor,"The step in firsteditve that appears when you start editing the document in VisualEditor no longer points to the ""Save page"" button due to an incompatible change to the VE HTML DOM.
+
+It still shows up, but it's no longer attached.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1408162620,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-o3mocvfmdnarvi5x2cyl,task_description,resolved
+firsteditve no longer points to VisualEditor,"Change 155234 abandoned by Phuedx:
+Point to the ""Save page"" button
+
+Reason:
+Abandoned in favour of I81fdc4f2fa41c86a6481cf478c154b5d6c99d41d.
+
+https://gerrit.wikimedia.org/r/155234",1408553781,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o3mocvfmdnarvi5x2cyl,task_subcomment,NA
+firsteditve no longer points to VisualEditor,"**swalling** wrote:
+
+Fixed in https://gerrit.wikimedia.org/r/#/c/155280/",1408553774,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-o3mocvfmdnarvi5x2cyl,task_subcomment,NA
+firsteditve no longer points to VisualEditor,"Change 155234 had a related patch set uploaded by Phuedx:
+Point to the ""Save page"" button
+
+https://gerrit.wikimedia.org/r/155234",1408530620,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o3mocvfmdnarvi5x2cyl,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,"When I open the VisualEditor on mobile in stable on enwiki using Chrome on desktop (OSX), I get the following JS error:
+Discontiguous selection is not supported. 
+
+I loaded it with ?debug=true here's what I see in the console:
+Discontiguous selection is not supported. rangy-core-1.3.js:2842
+(anonymous function) rangy-core-1.3.js:2842
+(anonymous function) rangy-core-1.3.js:2852
+(anonymous function) rangy-core-1.3.js:327
+init rangy-core-1.3.js:249
+loadHandler rangy-core-1.3.js:365
+
+Incidentally, I'm also seeing this in the console with ?debug=true (however I do not see this without ?debug=true):
+Uncaught Error: Module not found: loggingSchemas/MobileWebClickTracking load.php?debug=true&lang=en&modules=mobile.head&only=scripts&skin=minerva&version=20140815T031511Z&*:53
+mw.mobileFrontend.require load.php?debug=true&lang=en&modules=mobile.head&only=scripts&skin=minerva&version=20140815T031511Z&*:53
+(anonymous function) load.php?debug=true&lang=en&modules=mobile.languages&only=scripts&skin=minerva&version=20140815T101…:67
+(anonymous function)
+
+Not sure if the click tracking thing is related, a separate bug, or just a result of something going wonky with load order as a result of ?debug=true - if it seems like a separate issue, I'm happy to file another bug but figured it'd be worth mentioning here for now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408123380,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-a3yfrijahd6twdq67xo2,task_description,resolved
+JS error on loading mobile VE: Discontiguous selection is not supported.,"Duplicate of bug 68493 which is now fixed.
+
+*** This bug has been marked as a duplicate of bug 68493 ***",1412803537,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,Not sure if this is still a relevant bug. Guessing VE folks will know.,1412795473,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,"**jgonera** wrote:
+
+This (""Discontiguous selection is not supported"") is not a mobile bug. It happens on desktop too.",1408664773,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/nqeGVbpJ",1408123813,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/7MTSGUCb",1408123513,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+VisualEditor:  Offer to pre-fill the DEFAULTSORT field,"Usually, DEFAULTSORT contents need only a little re-arranging or capitalization changes.  If the name is long or unfamiliar, it may be difficult to type it to make these relatively minor changes.  It would be nice to pre-fill the box with the page title.
+
+But if VisualEditor simply fills in the box whenever you open the Page settings menu, then we'll get a lot of errors (because people won't notice that it needs to be updated).
+
+Possible solution:  Add a button next to the DEFAULTSORT item to insert the current page title as text that the editor can then change as needed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408048080,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-v3n4j4kb2ell4h52eujf,task_description,resolved
+VisualEditor:  Offer to pre-fill the DEFAULTSORT field,"This is the same as bug 50002 (and needs a huge amount of design thought).
+
+*** This bug has been marked as a duplicate of bug 50002 ***",1408096620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3n4j4kb2ell4h52eujf,task_subcomment,NA
+VisualEditor Mobile: removing a link takes me to the top of the page,"Steps to repro:
+
+1. In production/stable, enter VE edit mode and scroll down to a section that's below the fold.
+2. Tap on a wikilink
+3. Use the ""remove"" button to remove the link & tap done.
+
+Expected: I am taken back to the section I was on.
+
+Actual: I'm taken back to the top of the page.
+
+Observed on iPad 2 & mobile site on desktop Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408047960,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-p5kjnipb4qiha2arheu4,task_description,resolved
+VisualEditor Mobile: removing a link takes me to the top of the page,"**jgonera** wrote:
+
+Can't reproduce anymore on latest master. Other bugfixes might have fixed this too. Reopen if it's still happening.",1409100209,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-p5kjnipb4qiha2arheu4,task_subcomment,NA
+VisualEditor Mobile: removing a link takes me to the top of the page,"**jgonera** wrote:
+
+I suspect this might be related to bug 66697.",1408058394,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-p5kjnipb4qiha2arheu4,task_subcomment,NA
+VisualEditor Mobile: removing a link takes me to the top of the page,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/JUXz2uL6",1408048213,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-p5kjnipb4qiha2arheu4,task_subcomment,NA
+Cannot copy text when dm.surface.enabled === false,"**Author:** `ryan.wold`
+
+**Description:**
+When disabling an Editor's .target.surface (by calling .disable()), the text is no longer editable, which is great.  However, the text in the disabled Editor cannot be copied and pasted.  It does not appear to make it to the clipboard. 
+
+Desired behavior is that the text can be be copied even when the editor is disabled.  Or perhaps there could be a setting/option around that.
+
+
+
+We traced this to ve.dm.Surface.prototype.changeInternal, where it returns immediately if the surface is disabled.
+
+if ( !this.enabled ) {
+  return;
+}
+
+I found this here: https://doc.wikimedia.org/VisualEditor/master/source/ve.dm.Surface.html#ve-dm-Surface-method-changeInternal
+
+
+I'm using OSX Mavericks and Google Chrome Version 36.0.1985.125.
+
+Thanks!
+
+- Ryan Wold
+  ryan.wold@neo.com
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1407976380,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-brolhdih457kpowhgvqe,task_description,resolved
+Cannot copy text when dm.surface.enabled === false,"**ryan.wold** wrote:
+
+
+
+%%%*** This bug has been marked as a duplicate of bug 69515 ***%%%",1407976455,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-brolhdih457kpowhgvqe,task_subcomment,NA
+VisualEditor:  Too much tabbing in the Template dialog,"From John Broughton:
+
+""This is what tabbing through Cite templates (in the mini-editors) looks like: type, tab, tab, tab, type, tab, tab, tab, type, ... You have to tab three times to get from one field to the next. That's because tabbing always includes both the “Field description” and “Remove field” icons. There isn't any reason to include these icons in tabbing; tabbing should bypass these icons.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407974220,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_description,resolved
+VisualEditor:  Too much tabbing in the Template dialog,"
+
+*** This bug has been marked as a duplicate of bug 68768 ***",1414084060,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_subcomment,NA
+VisualEditor:  Too much tabbing in the Template dialog,"(In reply to James Forrester from comment #2)
+> Using a <button> rather than a <div> in OOUI for buttoned elements takes us
+> into really horrible issues more widely, though…
+
+Can you elaborate, because I don't see why that would be ? We have gotten them pretty down even in mediawiki.ui",1408696342,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_subcomment,NA
+VisualEditor:  Too much tabbing in the Template dialog,"(In reply to WhatamIdoing from comment #0)
+> From John Broughton:
+
+[…]
+
+> There isn't any reason to include these icons in tabbing
+
+The reason is ""accessibility"". That's a pretty strong sine qua non for how we build things.
+
+(In reply to Derk-Jan Hartman from comment #1)
+> Using an actual button might fix 'excessive' tabbing here, since browsers
+> sometimes have different default tab behavior for buttons vs. fields, a
+> behavior overridden if you need to force button behaviors on a div/a.
+
+Using a <button> rather than a <div> in OOUI for buttoned elements takes us into really horrible issues more widely, though…",1408642685,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_subcomment,NA
+VisualEditor:  Too much tabbing in the Template dialog,"Also shift tab behaves differently (this is due to presence of icon only in focus state. WAI-ARIA has some further thoughts on how bot build fields like this, but I think it might be a bit too much effort right now.)
+
+Using an actual button might fix 'excessive' tabbing here, since browsers sometimes have different default tab behavior for buttons vs. fields, a behavior overridden if you need to force button behaviors on a div/a.",1408628873,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_subcomment,NA
+VisualEditor:  Links added to captions for new images not quite working,"What happens when you try to make a link.  (Notice that the box is too small; that will be a separate bug in a moment.)
+
+I can only make this happen in Safari, not Firefox, but I believe that the user reporting this was using Firefox.
+
+Steps to reproduce:
+
+1.  Open VisualEditor and Insert > Media.
+
+2.  Pick and image and add a caption.
+
+3.  Select a word and press Command-K to make an internal link. 
+
+4.  Notice that you get no search results to help you find the correct page for your link.
+
+5.  Click inside the box.  Now you have search results.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14163}",1407973740,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wvmydl4bbkdtqm7osvyj,task_description,declined
+VisualEditor:  Links added to captions for new images not quite working,"I think it is the firefox which is different from Chrome and Safari, not sure which one is correct though!And not just for a link inside image, for a link in CE too,in Chrome and Safari, you will not get any list of link target suggestions unless you click inside the box.",1410220995,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wvmydl4bbkdtqm7osvyj,task_subcomment,NA
+VisualEditor:  Links added to captions for new images not quite working,"Experience in Safari:
+
+1.  Open VisualEditor and Insert > Media.
+
+2.  Pick and image and add a caption.
+
+3.  Select a word and press Command-K to make an internal link. 
+
+4.  Notice that you get no search results to help you find the correct page for your link.
+
+5.  Click inside the box.  Now you have search results.
+
+
+Experience in Firefox:
+
+1.  Open VisualEditor and Insert > Media.
+
+2.  Pick and image and add a caption.
+
+3.  Select a word and press Command-K to make an internal link. 
+
+4.  Notice that you are immediately given a long list of search results, even if you don't want them.
+
+
+Since they don't behave the same, then one of these two browsers isn't working as designed.",1410217842,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wvmydl4bbkdtqm7osvyj,task_subcomment,NA
+VisualEditor:  Links added to captions for new images not quite working,I don't see a bug here? This seems to be working as expected. Have I missed something?,1410202699,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wvmydl4bbkdtqm7osvyj,task_subcomment,NA
+VisualEditor:  Information fields in template dialogs are sometimes very large,"See https://en.wikipedia.org/wiki/File:Cite_dialog_with_large_boxes_for_fields.png
+
+This is intermittent and may be relate to zooming in/large text size.  The fields go back to normal size when you click inside them.  Seen in both Firefox and Safari on Macs.
+
+Today, I'm getting pretty consistent results by opening https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&veaction=edit in Safari and selecting the infobox.  Opening it (double-clicking) the first time works as expected.  Cancelling it (escape key) and opening it again produces larger than necessary fields.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407972240,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uz4ebiomuh52dqhalxqd,task_description,resolved
+VisualEditor:  Information fields in template dialogs are sometimes very large,"Tried in Safari on Mac with the link provided - cannot reproduce. Also, checked if transclusion boxes will scale up/down with the selected zoom rate - all look fine. ",1419990286,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-uz4ebiomuh52dqhalxqd,task_subcomment,NA
+VisualEditor:  The Categories dialog should indicate which cats are red links,"Of a non-existent category has been added on a page, there is no indication in the Categories dialog that it is a red link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407971580,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rlvjrs3munfatsc5rqfz,task_description,resolved
+VisualEditor:  The Categories dialog should indicate which cats are red links,"
+
+*** This bug has been marked as a duplicate of bug 65517 ***",1414805875,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rlvjrs3munfatsc5rqfz,task_subcomment,NA
+VisualEditor:  Categories should be displayed at the end of the page,"VisualEditor should display categories in the page's footer, just like they will display when the page is saved.  Clicking on the footer could open the Categories editing tool.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407971340,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-mkaptpov6nx3eewv7jvc,task_description,duplicate
+VisualEditor:  Categories should be displayed at the end of the page,"
+
+*** This bug has been marked as a duplicate of bug 50239 ***",1414806319,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mkaptpov6nx3eewv7jvc,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"Article URL: https://ru.wikipedia.org/wiki/%D0%A2%D0%B0%D0%B1%D0%BB%D0%B8%D1%86,_%D0%91%D0%BE%D0%B3%D1%83%D1%81%D0%BB%D0%B0%D0%B2
+
+The infobox is shown correctly while reading the article, but broken when editing in VisualEditor. HTML code is shown above the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407844800,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-btruvlfdq3qyqvht2rk7,task_description,resolved
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"> Looks like a bug in broken attribute heuristics.
+
+On second thought, I think what we're doing is fine. This is just broken wikitext.
+
+The php parser gets away with it by refusing all ""greater than"" chars in attributes. ie.
+
+  <div class=""class>ey"">stuff</div>
+
+is rendered as,
+
+  <div>ey""&gt;stuff</div>
+
+which seems worse.",1408488269,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"The template was returning something like,
+
+  <table><tr><th style=""text>great</th><td>""test</td></tr></table>
+
+which parsoid rendered as,
+
+  &lt;th style=""text>great
+  <table>
+  <tbody>
+  <tr>
+  <td>""test</td></tr></tbody></table>
+
+Looks like a bug in broken attribute heuristics.",1408482811,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"Fixed the template in,
+https://ru.wikipedia.org/w/index.php?title=%D0%9C%D0%BE%D0%B4%D1%83%D0%BB%D1%8C%3AUniversal_infocard&diff=64929809&oldid=64897667
+
+But we should be more robust against unclosed attributes.",1408478247,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"(In reply to James Forrester from comment #1)
+> Looks like [[ru:Template:Универсальная карточка]] is getting a bunch of
+> content fostered out somewhere?
+
+I didn't go too deeply into the code, but it is build using this Lua module:
+https://ru.wikipedia.org/wiki/Module:Universal_infocard
+
+It pulls data from Wikidata, and seems to build tables using HTML rather than wiki table syntax. Maybe that is the cause.",1407846830,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,Looks like [[ru:Template:Универсальная карточка]] is getting a bunch of content fostered out somewhere?,1407845929,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+Chrome not populating text fields correctly,"Reported by S Page at QA mailing list[1]. Reported to Sauce Labs support[2].
+
+1: http://lists.wikimedia.org/pipermail/qa/2014-August/001843.html
+2: http://lists.wikimedia.org/pipermail/qa/2014-August/001846.html
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1407767220,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-yata753fflzx3ifjicto,task_description,resolved
+Chrome not populating text fields correctly,"**gerritadmin** wrote:
+
+Change 153408 merged by jenkins-bot:
+Chrome 28 is the last version that works properly on Sauce Labs
+
+https://gerrit.wikimedia.org/r/153408",1407917621,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yata753fflzx3ifjicto,task_subcomment,NA
+Chrome not populating text fields correctly,"I have started builds for all Chrome jobs. The jobs should be more green now.
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-test2.wikipedia.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Math-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-MultimediaViewer-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-PageTriage-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-UploadWizard-commons.wikimedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-test2.wikipedia.org-linux-chrome-sauce/",1407769872,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-yata753fflzx3ifjicto,task_subcomment,NA
+Chrome not populating text fields correctly,"**gerritadmin** wrote:
+
+Change 153408 had a related patch set uploaded by Zfilipin:
+Chrome 28 is the last version that works properly on Sauce Labs
+
+https://gerrit.wikimedia.org/r/153408",1407768857,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yata753fflzx3ifjicto,task_subcomment,NA
+Chrome not populating text fields correctly,"Sauce Labs support answer:
+
+Allison Wilbur (Sauce Labs Help Desk)
+Aug 09 02:03 AM
+
+Hi there,
+
+I'm sorry this issue suddenly popped up for you! Sauce Labs just recently updated the default versions of Chrome, ChromeDriver, and Selenium that we serve up when no version is explicitly requested in the Desired Capabilities we receive.
+
+Previously, the default values were:
+
+Selenium: 2.30.0
+Chrome: 27/28 (depending on environment - 28 for Linux)
+ChromeDriver: 26.0.1383.0
+
+The new default values are:
+Selenium: 2.40.0
+Chrome: 35
+ChromeDriver: 2.10
+
+If you set your Desired Capabilities to the previous values, I suspect your tests will behave as they used to. For example:
+
+desired_capabilities['selenium-version'] = '2.30.0'
+desired_capabilities['browserName'] = 'chrome'
+desired_capabilities['version'] = '28'
+desired_capabilities['chromedriver-version'] = '26.0.1383.0'
+
+The extremely odd behavior you saw with the recent versions update is something I'm currently investigating, and I've filed an internal ticket to get this problem fixed. It seems to be related to the later versions of Chrome/ChromeDriver for some reason, and specific to Linux. I found this issue with send_keys on the ChromeDriver forums: https://code.google.com/p/chromedriver/issues/detail?id=467 It's not quite the same issue, but it looks like there's some strange behavior with text input in Linux.
+
+I hope the previous values perform well for you as a workaround while we investigate the issues with the more recent versions of Chrome. I've linked this ticket to the issue, so I'll be sure to let you know when the fix is out so that you can test on more recent versions. If you want to try the later versions, I've had some success looping through my input and sending one key at a time, so perhaps something like that would help out.
+
+Sorry again for the trouble here. Let me know if you have any additional questions and I'll be happy to help. Hope you have a great weekend!
+
+Best,
+Allison",1407767724,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-yata753fflzx3ifjicto,task_subcomment,NA
+VisualEditor: <ref>s in a section-edit get re-numbered,"https://en.wikipedia.org/wiki/Sonic_Adventure#Development
+
+When I go here and click ""edit beta"", the <ref>s are re-numbered when ?veaction=edit loads.
+
+For example, at the implicit ?action=view:
+
+---
+The character of Sonic was redesigned for the game by Sonic Team artist Yuji Uekawa, with longer legs and spines that Iizuka subsequently noted were more suitable for 3D than Sonic's original and more compact design, which was meant to be seen from the side.[46][47] 
+---
+
+At ?veaction=edit:
+
+---
+The character of Sonic was redesigned for the game by Sonic Team artist Yuji Uekawa, with longer legs and spines that Iizuka subsequently noted were more suitable for 3D than Sonic's original and more compact design, which was meant to be seen from the side.[42][43]
+---
+
+This is super-confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407700140,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6myt7vl23u4acnyzoq5w,task_description,resolved
+VisualEditor: <ref>s in a section-edit get re-numbered,"This sounds like the same thing as what's described as bug 50474.
+
+*** This bug has been marked as a duplicate of bug 50474 ***",1407719768,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6myt7vl23u4acnyzoq5w,task_subcomment,NA
+VisualEditor:  Dialog for inserting new templates doesn't play well with search results,"Goal:  Insert a new template.
+
+Steps to reproduce:
+
+1.  Insert > Template
+
+2.  Start typing the template's name:  Citation nee…
+
+3.  Think, ""Ah, it's found it!  It's highlighted and has a checkmark next to it!  Great, I can stop typing that long name and just hit return to add the template that I want.
+
+4.  Press return.
+
+5.  Think, ""Um, [[Template:Citation nee]] is a redlink.  Why did it add that?  Why didn't it add the highlighted-and-checkmarked [[Template:Citation needed]]?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407651480,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gyjrpnwlzlseuj5ay2wq,task_description,resolved
+VisualEditor:  Dialog for inserting new templates doesn't play well with search results,"I am inclined to close as Resolved: the feedback to a user for inserting templates has improved
+
+- there is no check mark to a highlighted suggested selection anymore
+- clicking Return with 'Citation nee'  selects the first highlighted template from the suggestions list
+ - the next dialog box displays the template's  title and info/description to inform a user what kind of a template is about to be inserted
+-  That dialog box requires a user to click 'Insert' button explicitly - not just pressing Return keyboard buttonn.
+
+
+",1424904354,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-gyjrpnwlzlseuj5ay2wq,task_subcomment,NA
+Add parameterless GENDER as insertable,"When {{GENDER:|...}} is part of a source string, GENDER: is not available as insertable.
+
+Example string: https://translatewiki.net/wiki/MediaWiki:Visualeditor-editconflict/en
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1407519060,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-6zqiurw6oqkkhhopo7w5,task_description,resolved
+Add parameterless GENDER as insertable,"Change 153571 merged by Jsahleen:
+Add parameterless GENDER as insertable
+
+https://gerrit.wikimedia.org/r/153571",1410260970,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6zqiurw6oqkkhhopo7w5,task_subcomment,NA
+Add parameterless GENDER as insertable,"Change 153571 had a related patch set uploaded by Nikerabbit:
+Add parameterless GENDER as insertable
+
+https://gerrit.wikimedia.org/r/153571",1407837498,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6zqiurw6oqkkhhopo7w5,task_subcomment,NA
+VisualEditor: Distorted UI of Language Inspector/Special Character appears while trying to open them when the link inspector is already open in CE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text
+3.Click on Link inspector
+4.While the link inspector is open, open Language inspector or Special Character inserter
+
+Observed Result:
+The UI of both the inspector appears a bit distorted having a whitespace at the bottom
+
+See the screenshot attached
+
+Environment:Production,test2,Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14605}",1407356580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tjl4vryiojzktgcw53ge,task_description,resolved
+VisualEditor: Distorted UI of Language Inspector/Special Character appears while trying to open them when the link inspector is already open in CE,Checked betalabs  - all is displayed correctly.,1425329715,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-tjl4vryiojzktgcw53ge,task_subcomment,NA
+VisualEditor: Distorted UI of Language Inspector/Special Character appears while trying to open them when the link inspector is already open in CE,"Re-checked it in Ptoduction and test2 -  the Language, Link inspectors and Special character inserter looks normal. 
+
+I will check betalabs when the env will be back to normal. 
+",1425002064,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-tjl4vryiojzktgcw53ge,task_subcomment,NA
+"VisualEditor:Edit beta tab not shown, when not logged in.","Environment- beta, production
+
+1> Try to open your User page without logging in.
+2> Shows the ""Welcome to VE"" popup, click on ""continue"" to proceed.
+3> opens the page in VE mode , but the VE Edit tab is not seen on top.
+
+In test2 follow the above steps and the page would open in the Read mode and all the tabs(Read, Edit and Edit source can be seen).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1407343860,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-pamojafdtnhybmzjhew6,task_description,invalid
+"VisualEditor:Edit beta tab not shown, when not logged in.","Yes, this is intentionally how it's configured on some wikis.",1407364526,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pamojafdtnhybmzjhew6,task_subcomment,NA
+"VisualEditor: Enable toggling between tabs and dropdown menus in the Vector skin ,  does not make the Read, Edit tabs squeeze into one “View” tab for FF and Safari.","screenshot
+
+1> Preferences -> Gadgets
+2> Enable this under Appearance -> Enable toggling between tabs and dropdown menus in the Vector skin. 
+3> Save 
+4> go back to User page. Notice now the Tabs Read, Edit and Edit Source all have been moved into a single drop down labeled “View”. However, enabling the same appearance in FF and Safari does not show the “View” dropdown.
+Also, the “View” is out of position as compared to “More” and does not show the drop down arrow.See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14485}",1407271560,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-mkqig7y2abufhee3e6a4,task_description,declined
+"VisualEditor: Enable toggling between tabs and dropdown menus in the Vector skin ,  does not make the Read, Edit tabs squeeze into one “View” tab for FF and Safari.","We don't track issues with gadgets in Phabricator, sorry.",1417577754,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mkqig7y2abufhee3e6a4,task_subcomment,NA
+"VisualEditor: Enable toggling between tabs and dropdown menus in the Vector skin ,  does not make the Read, Edit tabs squeeze into one “View” tab for FF and Safari.",Environment-test2,1407272360,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-mkqig7y2abufhee3e6a4,task_subcomment,NA
+VisualEditor: Citation number 0,"* Add a basic citation
+* Add another non-basic(?) citation
+* Go back and set group of basic citation to something, apply changes
+* Undo changes twice
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407187800,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vqi7xz3ct5esenmosj2r,task_description,resolved
+VisualEditor: Citation number 0,"
+
+*** This bug has been marked as a duplicate of bug 69119 ***",1414806524,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vqi7xz3ct5esenmosj2r,task_subcomment,NA
+VisualEditor: Citation number 0,"Also if you undo again, you get this:
+Uncaught TypeError: Cannot read property 'length' of undefined
+Then this:
+Uncaught TypeError: Cannot read property 'canHaveChildren' of null
+Then this:
+Uncaught Error: Unbalanced input passed to document",1407188306,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vqi7xz3ct5esenmosj2r,task_subcomment,NA
+VisualEditor:  Placing some templates in bulleted lists causes complex transclusions,"Steps to Reproduce:
+1. Open https://ru.wikipedia.org/w/index.php?oldid=63644335&veaction=edit and look at the second section.
+
+The wikitext is:
+
+=== Б ===
+
+* [[Борисов, Бойко Методиев]] (род. 1959) — болгарский политик.
+* {{NL|Борисов, Борис}}
+
+{{NL}} is a template that transcludes the rest of this short list.
+
+2. The first bullet point is plain wikitext.  Click on the first item and try to change some of the text (e.g., to change the birth date from 1959 to 1960).
+
+
+Actual Results:  
+The first bullet point can only be edited as the ""content"" part of a complex transclusion.  
+
+Expected Results:  
+That plain-text list items can be edited as plain old list items.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407177240,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-x4x3miva4uelxlwoeyn2,task_description,declined
+VisualEditor:  Placing some templates in bulleted lists causes complex transclusions,"This is not a problem with lists per se. This is a result of how Parsoid represents templates in the DOM, and where some transclusions doesn't generate well-balanced DOM structures.
+
+Parsoid marks complete DOM subtrees as template-generated/affected. So, in scenarios where output of a template spans multiple dom subtrees, all those affected subtrees are wrapped as one piece.
+
+You can reproduce this behavior with a simple example like: ""a {{echo|b\n\nc}} d"". In this example, b and c belong to different paragraphs which also contain content from outside the transclusion. So, all of it is pulled into the template wrapping.
+
+This is the same behavior where multiple transclusions are used to generate football tables, succession tables, etc.",1408574718,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-x4x3miva4uelxlwoeyn2,task_subcomment,NA
+"VisualEditor: Media Settings dialog does not close, when inserting a media with a link or language  ""Uncaught TypeError: undefined is not a function""","screenshot
+
+Environment-test2
+
+Steps- 
+
+1> Insert-> Media.
+2> In media Settings dialog insert a link or type in some text in a language.
+3> Click on ""Insert media"". notice the file gets inserted in the background, and yet the media settings dialog never closes.
+
+See screenshot.
+
+Also See bug 65568.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows XP
+
+**Attached**: {F14256}",1406931420,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-otkdojq77s5a7dnwv5td,task_description,declined
+"VisualEditor: Media Settings dialog does not close, when inserting a media with a link or language  ""Uncaught TypeError: undefined is not a function""",I cannot reproduce it anymore in test2 or beta.Please close this issue.,1407162115,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-otkdojq77s5a7dnwv5td,task_subcomment,NA
+VisualEditor:  Can't re-use the same reference twice,"Intention:
+Re-use an existing reference
+
+Steps to Reproduce:
+1.  Open a page containing a citation.
+
+2.  Cite > Re-use.  Click on a reference.
+
+3.  Go to another sentence.
+
+4.  Cite > Re-use.  Click on the same reference (it's already highlighted).
+
+
+Actual Results:  
+The first time, it adds the ref.  The second time, it does nothing.  You have to insert a different (wrong) ref, delete that, and then add the one that you wanted (now that it's stuck on the ""wrong"" one).  Canceling and trying again doesn't help.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406928360,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rl2y2ishipdsqzcikuvr,task_description,resolved
+VisualEditor:  Can't re-use the same reference twice,"
+
+*** This bug has been marked as a duplicate of bug 68582 ***",1406929690,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rl2y2ishipdsqzcikuvr,task_subcomment,NA
+VisualEditor:Insert -> Comment not working in Betalabs,"steps-
+1> open a page in VE.
+2> Insert -> Comment. Add/Edit Comment dialog does not pop.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP",1406912520,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-dko2nwcat2a5enwq6736,task_description,resolved
+VisualEditor:Insert -> Comment not working in Betalabs,"This is the same bug as https://bugzilla.wikimedia.org/show_bug.cgi?id=68960
+Just in Chrome the JS error is different , so initially I thought its a different one.",1406921165,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dko2nwcat2a5enwq6736,task_subcomment,NA
+VisualEditor:Insert -> Comment not working in Betalabs,"
+
+*** This bug has been marked as a duplicate of bug 68960 ***",1406921057,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dko2nwcat2a5enwq6736,task_subcomment,NA
+VisualEditor:Insert -> Comment not working in Betalabs,"yes, the error appearing in the console is:
+Uncaught TypeError: undefined is not a function",1406916416,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dko2nwcat2a5enwq6736,task_subcomment,NA
+VisualEditor:Insert -> Comment not working in Betalabs,Any errors in the JS console?,1406912940,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dko2nwcat2a5enwq6736,task_subcomment,NA
+"VisualEditor Mobile:Mobile VE does not load after saving the first time edit in production (en.wiki), shows Error,can't load section","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE in prouction
+
+2.Make any edit and save it
+
+3.Try to reopen the page with Mobile VE
+
+Observed Result:
+VE does not load the page and the error appears:
+Error,can't load section
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14658}",1406838660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ndrboycjw5r2mnma3qfj,task_description,declined
+"VisualEditor Mobile:Mobile VE does not load after saving the first time edit in production (en.wiki), shows Error,can't load section",Think this was solved long ago?,1409669905,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ndrboycjw5r2mnma3qfj,task_subcomment,NA
+Weird behavior of the Cite extension with VisualEditor,"References in MediaWiki view mode (rendering correctly)
+
+This is most likely due to Cite, but the extension works in ""view"" mode and fails in VE in my local wiki.
+
+The problem: 
+
+Citations/References work well in view mode but when VE loads, they appear as their ""raw"" tags <ref>Something</ref> and <references />. 
+
+More details: From within VE, even when the references appear broken like above, I can still add a reference, which renders correctly as [1]. When I save the page the wikitext is correct and the view mode recognizes all references (both those that were broken and those that were just inserted). Then if I re-edit the page, the references are broken again.
+
+Details -
+
+Cite extension is installed from the git repository, and this line is in LocalSettings.php:
+require_once ""$IP/extensions/Cite/Cite.php"";
+
+This happens in Chrome 36.0.1985.125 and Firefox 31.0 under Ubuntu 14.04
+
+
+Attachments: 
+
+View mode and edit mode of the same page (no change to wikitext)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14545}",1406787600,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-p274rceja3pbo4jwirun,task_description,invalid
+Weird behavior of the Cite extension with VisualEditor,"Apparently, the solution was to update and restart Parsoid.",1406832203,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-p274rceja3pbo4jwirun,task_subcomment,NA
+Weird behavior of the Cite extension with VisualEditor,"Created attachment 16107
+Same page in view mode
+
+**Attached**: {F14547}",1406787705,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-p274rceja3pbo4jwirun,task_subcomment,NA
+Weird behavior of the Cite extension with VisualEditor,"Created attachment 16106
+Same page in view mode
+
+**Attached**: {F14546}",1406787665,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-p274rceja3pbo4jwirun,task_subcomment,NA
+MediaWiki 1.24wmf6 required when trying to install VisualEditor_REL1.23,"**Author:** `sure4us`
+
+**Description:**
+A number of people trying to install 1.23.1 + VE + Parsoid are finding an error that crashes the site.
+
+https://www.mediawiki.org/wiki/Extension_talk:VisualEditor#MediaWiki_1.24wmf6_required_when_trying_to_install_VisualEditor_REL1.23_45012
+
+
+I'm also experiencing it, here's the error messaging:
+
+
+[d64ccb4d] /wiki/ Exception from line 3279 of /home/mywiki/public_html/wiki/includes/GlobalFunctions.php: MediaWiki 1.24wmf6 required--this is only 1.23.1
+
+Backtrace:
+
+#0 /home/mywiki/public_html/wiki/extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW(string)
+#1 [internal function]: VisualEditorHooks::onSetup()
+#2 /home/mywiki/public_html/wiki/includes/Setup.php(601): call_user_func(string)
+#3 /home/mywiki/public_html/wiki/includes/WebStart.php(156): require_once(string)
+#4 /home/mywiki/public_html/wiki/index.php(43): require(string)
+#5 {main}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406767620,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vvn3l4s5izeg73ehqg63,task_description,declined
+MediaWiki 1.24wmf6 required when trying to install VisualEditor_REL1.23,"This sounds like the creation of the temporary tarball was very broken, but thanks to Kunal's work on ExtensionDistributor this should now be moot. Sorry for the troubles.",1408566124,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vvn3l4s5izeg73ehqg63,task_subcomment,NA
+MediaWiki 1.24wmf6 required when trying to install VisualEditor_REL1.23,"I just downloaded the latest tarball from <https://www.mediawiki.org/wiki/Special:ExtensionDistributor?extdist_extension=VisualEditor&extdist_version=REL1_23&extdist_submit=Continue>, and I see wmfUseMW( '1.22' ) in it.",1408563323,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-vvn3l4s5izeg73ehqg63,task_subcomment,NA
+MediaWiki 1.24wmf6 required when trying to install VisualEditor_REL1.23,"If they installed VisualEditor master, than that is bound to fail because it requires 1.24alpha (as all extensions do unless otherwise noted).
+
+There is a REL1_23 branch[1] which requires 1.22 or higher (not 1.24alpha).
+
+It seems however that the custom 1.23 download made available is packages from some arbitrary version not documented anywhere and that version contains ""wfUseMW( '1.24wmf6' );"" in its code.
+
+I suggest whatever hacks were applied to produce this tarball are applied to REL1_23 following regular code review. If it's based on master instead of REL1_23, we can fast-forward REL1_23 to master and apply the fixes then.
+
+Either way whatever we promote as 1.23-compat should be git and go through review. And when it does, it should be fixed to not require wfUseMW( '1.24wmf6' ); which is a bit silly for code explicitly made for 1.23.
+
+[1] https://github.com/wikimedia/mediawiki-extensions-VisualEditor/tree/REL1_23
+[2] https://www.mediawiki.org/wiki/Extension:VisualEditor",1406819171,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vvn3l4s5izeg73ehqg63,task_subcomment,NA
+VisualEditor:Categories when added are shown as return character in VE.,"screenshot1
+
+Environments-test2, betalabs, production.
+
+Steps-
+1> open a blank page in VE and type in some text.
+2> while the cursor is still at the end of the last character, add at least two categories.
+3> Save the page.
+4> Now open the page again in VE. Notice the categories are shown as return characters at the end of the text(one for each category added).See screenshots.
+
+Happens only in Chrome and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14346}",1406656560,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-dm6dyr2mel4tbhvuduxe,task_description,resolved
+VisualEditor:Categories when added are shown as return character in VE.,"Yeah, these are bug 48290 issues…
+
+*** This bug has been marked as a duplicate of bug 48290 ***",1406754254,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dm6dyr2mel4tbhvuduxe,task_subcomment,NA
+VisualEditor:Categories when added are shown as return character in VE.,"Created attachment 16096
+screenshot3
+
+**Attached**: {F14348}",1406656613,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-dm6dyr2mel4tbhvuduxe,task_subcomment,NA
+VisualEditor:Categories when added are shown as return character in VE.,"Created attachment 16095
+screenshot2
+
+**Attached**: {F14347}",1406656586,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-dm6dyr2mel4tbhvuduxe,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.","screenshot
+
+Environments-test2
+
+Steps-
+1> open a page in VE.
+2> Insert ->Media. 
+3>Select to add a media file. Opens the Media Settings dialog.
+4>Now click on “Caption” pane and Select to insert a Link .
+5> Click on the style text menu to select the Language and type some text. See screenshot.
+6> Now move the cursor to the link, notice the link icon is not appearing, but the icon in the toolbar does get selected. 
+7>Now  try to insert a new link by selecting the link icon on toolbar, does not open the link inspector and the text in the pane gets typed as normal text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14342}",1406652060,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_description,resolved
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",Issue fixed in test2.,1409667851,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",Assuming yes.,1409345322,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",Possibly fixed in 2014-07-31?,1407166916,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",Cannot reproduce it anymore in test2 or beta.,1407163211,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.","Yeah, this is not very good.",1406754539,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",same issue found in betalabs,1406653055,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.","screenshot1
+
+Environment-test2, production
+
+Steps-
+1> Open a page in VE.
+2> Insert ->Media. 
+3>Select to add a media file. Opens the Media Settings dialog.
+4>Now click on “Alternative Text”, with cursor in this input field. Select to insert a Comment or Special Character or a link.
+5> Notice that the inspectors open up in the Alternative text input field (see screenshots), but when entered they do show up in the Caption pane.
+Also see 62410 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14337}",1406650800,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_description,resolved
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.","
+
+*** This bug has been marked as a duplicate of bug 68806 ***",1406655142,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_subcomment,NA
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.",same issue found in betalabs.,1406652915,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_subcomment,NA
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.","Created attachment 16092
+screenshot3
+
+**Attached**: {F14340}",1406650898,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_subcomment,NA
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.","Created attachment 16091
+screenshot2
+
+**Attached**: {F14339}",1406650875,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"cloudbees branch was a step in moving jobs from Cloudbees. Now that the move is finished, the branch should be merged with master.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1406640060,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wkzeswtrlltjtokvlumh,task_description,resolved
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,Resolved in https://gerrit.wikimedia.org/r/#/c/156809/,1409589895,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"I might have attempted this merge, but I proved to myself yesterday that I still don't understand jjb well enough to do this with confidence.",1408550925,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"Change 152905 abandoned by Hashar:
+Merge cloudbees branch into master
+
+Reason:
+Was merely to highlight how to handle the merge with git.  Will revisit when Zeljkof is back from vacations.
+
+https://gerrit.wikimedia.org/r/152905",1408537513,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"Here what I did:
+
+ git remote update
+ git checkout master
+ git reset --hard gerrit/master
+ git merge --no-ff gerrit/cloudbees
+ # fix conflict
+ git push gerrit HEAD:refs/for/master
+
+
+I think the issue was when using git rebase. That create new commits that Gerrit does not know about.
+
+git merge --no-ff prevents the rebase and thus keep all the commits from cloudbees branch as is.",1407503476,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"Change 152905 had a related patch set uploaded by Hashar:
+Merge cloudbees branch into master
+
+https://gerrit.wikimedia.org/r/152905",1407503364,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"Antoine, is the the way to go? Or is there a better way?",1407428025,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"$ git checkout cloudbees
+
+$ git checkout -b the_big_merge
+
+$ git rebase master
+First, rewinding head to replay your work on top of it...
+...(fixed all conflicts)...
+
+$ git review
+You are about to submit multiple commits. This is expected if you are
+submitting a commit that is dependent on one or more in-review
+commits. Otherwise you should consider squashing your changes into one
+commit before submitting.
+
+The outstanding commits are:
+
+64e8d18 (HEAD, the_big_merge) Add job for PageTriage tests
+017c8e2 Language screenshot job should run on test2.wikipedia.org
+657f627 Add Chrome build for Math extension on beta labs
+9ad0a82 Tie language screenshot to UbuntuPrecise
+4a70f3f Tie all jobs to UbuntuPrecise
+239bbdb The first job for Math extension
+fc7283c Language screenshot feature file runs only in language screenshot job
+64af5d1 Run language screenshot job manually
+5f3072b Language screenshot jobs run in serial now
+224139e VisualEditor renamed ""test"" folder to ""tests""[1]
+69cb80e mediawiki/core Jenkins job should not send e-mail notifications to ULS team
+3637bbd Remove mobile-tech from Jenkins notifications
+8e51dc8 language-screenshot jobs should use LanguageScreenshotBot user
+6637a2a Upload the language screenshots
+cbc0ff2 Normalize ZeroBanner job
+8a57c13 Support setting VERSION for phantomjs browser
+90eba50 Tests moved from ZeroRatedMobileAccess to ZeroBanner repository
+c85965f WikiLove job runs at Sauce Labs
+d322815 Moved mediawiki_user variable from jobs section to project section
+9254600 Running all CirrusSearch jobs at Sauce Labs
+95d9d29 Moved mediawiki_user variable from jobs section to project section
+e553524 Deleted CentralAuth job
+dcce7bf browsertests: matrix project to take screenshots
+313ca1d Deleted browsertests jobs, created Flow jobs
+2658ea7 Created the first job to run Selenium tests in mediawiki/core
+158770b Moved MultimediaViewer jobs from Cloudbees
+dce5026 Moved two browsertests-qa jobs to Sauce Labs
+522a666 Moved a couple of UploadWizard from Cloudbees
+e75d259 All language team jobs are now running at Sauce Labs
+56263c9 Deleted en.m.wikipedia.org MobileFrontend job
+9f6397d Moved the last two MobileFrontend jobs from Cloudbees
+88a2f1b Replace underscore by spaces in PLATFORM
+f3947d7 Moved the last VisualEditor job from Cloudbees
+53bf24c Created the first Windows XP job
+23be398 Created a couple of VisualEditor test2.wikipedia.org jobs
+ad0ccfa Refactored Flow, MobileFrontend and VisualEditor Sauce Labs jobs. Deleted local VisualEditor jobs.
+52561f5 Deleted local MobileFrontend jobs, refactored MobileFrontend Sauce Labs jobs
+8d65d8b Deleted two local Flow jobs, created two Flow jobs that run on Sauce Labs
+982f9df Disable MF/VE jobs moved to SauceLabs
+64cb2bf Sauce jobs for MobileFrontend
+de563e1 Chrome job for VisualEditor on en.beta
+b09d3ec Add support to pass VERSION for Chrome browsers
+62ca809 Create a -sauce template with headless set to false
+745ce86 Make headless a JJB variable
+427054b Let us manage disable manually
+8d3943c Disable all browsertests jobs
+f775cd1 Adjust node label
+7edd9c8 Notify qa-alerts@lists.wikimedia.org
+ee18913 Reset branch based on origin, not local copy
+67cd040 Fallback to master branch when test repo miss branch
+08a04ae Get mw branch from target URL and check it out
+249dfc4 Allow user to claim failed build
+5ef9dca Refactor UploadWizard API template to use mediawiki_url
+28c4f1f Refactor job template to include mediawiki_url
+54855f7 Add Screenshots for ZeroRatedMobileAccess
+2f66f2b browsertests: Change irc message-type from summary-scm to summary
+2bf9cd6 Export MEDIAWIKI_API_URL when running browser tests
+ea0d30d ZeroRatedMobileAccess had a cloudbees phantomjs install
+5e1b510 Normalize user/pass for language-stage instance
+2f153ee Normalize user/pass for language-browsertests instance
+4c70068 Prefix the two qa/browsertests jobs with 'qa-'
+b82a2b1 Make the job templates to vary by platform
+65031b2 Make platform all lower case
+2d0df48 Vary VisualEditor and ZeroRatedMobileAccess by browser
+671ecd7 Restore WikiLove job!
+76f83f6 Drop version parameter entirely
+906e611 Make the job template to vary by browser
+5b55a1b Rename build 'default' to 'browsertest-website'
+e5ae11d Rename default to 'browsertest'
+f397f8e Use YAML anchors and alias to maintain emails lists
+db84dab Write junit report under /log/junit/
+937cf75 Explode a long line in ZeroRatedMobileAccess
+50b487b Make sure we have a '/log' directory
+ff4f8c1 Split long line into several shorter ones
+d8c842d Tweak git scm to keep the workspace between build
+c14ab86 Avoid error when creating vendor directory
+4919d45 Take a screenshot when a test fails
+a694a43 Moved wikimedia.template to integration/jenkins repository
+2e92f77 Only notify #wikimedia-qa for browsertests results
+3232e6a Deleted job templates that are no longer used
+0b2a346 Added ""browsertests-"" to the beginning of every job
+842ad50 Deleting all Internet Explorer and Chrome jobs
+86e6897 Force cucumber to use colors
+f73b76f Run browser tests on the local machine headlessly
+5cf4441 Add timestamp and ansicolor to the console
+98b95c9 Make the ircbot publisher a macro
+2587d22 Use gem 1.9.3 and the installed bundler version
+59c668b Make bundle install verbose!
+3475b4d Install gems in a shared dir
+e94c1d1 Remove ruby 2.1.1 when running on wmflabs
+b3ba732 Tie browsertests jobs to wmflabs slaves
+1d617b8 .gitreview file for the cloudbees branch
+60e446b Created CentralAuth job
+85842ef Replaced browser_version JJB variable with BROWSER_TAG shell variable
+c643972 Added browser specific tags to ContentTranslation Cucumber feature
+72d9905 Fixed browser for several Jenkins jobs
+c707fa2 Added per-browser tags to MobileFrontend builds
+86a33c7 Renamed a couple of Flow jobs to follow the convention
+d78c52b Added browser specific tags to Cucumber features and scenarios
+4f17984 Update Chrome at Sauce Labs to the most stable version
+f65462a Change recipient for MultimediaViewer alerts
+1d66ec9 Fixed username and password for a Translate job
+3c0a9d5 Merged default and browsertests dcm section
+a72ae6d Refactored shell builders
+7c77449 Refactoring: grouped job templates and builders
+b8fa80d Moved UploadWizard job template to the template file, and jobs to jobs file
+ecbf4e0 Refactored VisualEditor job to use job template
+bbc1072 Refactored Zero job to use the job template
+1e14b88 Moved browsertests to the bottom of the file
+82a7254 Refactored an ULS job to use the template
+aef3275 Rename user for CX to TranslatorToDa
+113b5e5 Created the first ContentTranslation job
+5974b36 Documented Extended E-mail Notification plugin setup
+f58e24e Minor formatting improvements for Jenkins documentation
+217f6b0 Moved environment variables above IRC notification
+d921f3c Renamed e-mail template file so it has the same name as at Cloudbees
+e059c36 Moved Jenkins documentation from mediawiki/selenium[1] repository
+2cb2c9c Using new e-mail notifications
+c846509 Sending MobileFrontend e-mail notifications to mobile-tech
+dfb6b01 Removed myself from all Jenkins e-mail notifications
+ba130d0 Removed Jeff from all e-mail notifications
+a16b4fb Fixed Translate jobs
+a908cc9 Updated Ruby version from 2.1.0 to 2.1.1
+ec8ef0f Add the whole eng MM team to the recipient list of UW test failures
+bd6391a added browsertests-test2.wikipedia.org jobs
+3466d51 added browsertests-en.wikipedia.beta.wmflabs.org jobs
+abb996e refactoring: moved everything from default job template to defaults
+a72ac64 refactoring: moved disabled and triggers from job template to defaults
+46aa64d refactoring: extracted scm out of job template
+5467697 refactoring: extracted publishers out of job template
+7e78369 refactoring: extracted shell builder out of job template
+3baf71e Added the rest of UploadWizard jobs
+c6a2145 added ""api-"" to names of UploadWizard API jobs
+a6ff524 Added missing ""-windows"" to Flow IE job names
+ff68e9a added remaining UniversalLanguageSelector jobs
+d596706 Spread load evenly
+b5a13f6 Updated UniversalLanguageSelector and VisualEditor jobs
+c12b00b added Translate jobs
+4900cbd added comments, where the jobs run
+0ea737b Fixed mediawiki_url for test2 Flow jobs
+9478a96 PLATFORM environment variable should be quoted
+19a9888 added Flow jobs
+aabbe80 added MobileFrontend jobs
+3748443 Separated repositories with comments
+71c909f Add the whole eng MM team to the recipient list of e2e test failures
+3cdf7c5 Added TwnMainPage job
+2e76c52 ZeroRatedMobileAccess does not need to fetch a commit from Gerrit any more
+7bac79e added MultimediaViewer job
+e5824fe Sorted job variables alphabetically
+5e9d306 Spreading load evenly
+eacd407 added CirrusSearch jobs
+87c4b66 moved job template and jobs to separate files
+b920181 shorter file names
+a472a19 deleted unused job
+8106cde one job template to rule them all
+fdc8cfe VisualEditor and WikiLove are using the same job template
+3a992de yaml file for the first UniversalLanguageSelector job
+ac6ad09 Merged UploadWizard yaml files into one
+ab4f0fe Created one VisualEditor job template to rule them all
+6a27177 Combined two VisualEditor jobs into one file
+86a78ea Make sure the job does not fail if phantoms is not already installed
+bedc0f3 yaml file for ZeroRatedMobileAccess
+93fe2b6 yaml file for WikiLove-en.wikipedia.beta.wmflabs.org-linux-firefox
+376ca73 yaml file for VisualEditor-test2.wikipedia.org-linux-firefox
+0f3dcb5 forgot junit publisher
+bfaa8d3 yaml file for VisualEditor-test2.wikipedia.org-linux-chrome
+7705392 looks like James was not receiving some e-mail messages
+6154a38 yaml file for VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox
+8dad741 make it explicit that the job should care just about master branch
+7f82e70 yaml file for VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome
+9f05512 yaml file for VisualEditor-production.wikimedia.org
+a6fd55e yaml file for UploadWizard-commons.wikimedia.org
+777b7ca config file for UploadWizard-commons.wikimedia.beta.wmflabs.org job
+1f0359a Updated readme file with basic informatioin
+f9f9a0d Installing PhantomJS using the latest advice from Cloudbees support
+5a2b6af Ported free-style job to jenkins-job-builder
+d736f27 Initial commit
+
+Do you really want to submit the above commits?
+Type 'yes' to confirm, other to cancel: 
+Aborting.",1407427995,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"screenshot1
+
+Environment- test2,betalabs.
+
+Steps-
+1>Open a page in VE.
+2>open Advanced Settings .Enable Display title and enter a title. Click “Apply Changes”.
+3>Click on “Save Page”
+4>Click on “Review your Changes”. Notice DISPLAYTITLE:titlename is shown under your text.
+5> Now click on Return to Save form. Click on “Cancel” on the Save your changes dialog.
+6>Go to Advanced Settings again in Page options. 
+7>Uncheck the “Enable Display title” checkbox and click to “Apply Changes”. 
+8> Repeat step#3 and #4. Notice even after disabling the display title it is still visible under your text in the “Review your changes” dialog. Open the advanced settings and you would notice that the enable display title is unchecked, but it shows up in Review your changes.
+
+Try the above steps with the other settings such as “Let this page be indexed by search engines”, “Show a tab on this page to add a new section”and with Categories too.Please see screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14247}",1406578140,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-zdzo44mp6rva2lnt47x2,task_description,resolved
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"Yes, this is bug 68619.
+
+*** This bug has been marked as a duplicate of bug 68619 ***",1406578618,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zdzo44mp6rva2lnt47x2,task_subcomment,NA
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"Created attachment 16071
+screenshot2
+
+**Attached**: {F14248}",1406578218,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-zdzo44mp6rva2lnt47x2,task_subcomment,NA
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"screenshot1
+
+Environment- test2,betalabs.
+
+Steps-
+1>Open a page in VE.
+2>open Advanced Settings .Enable Display title and enter a title. Click “Apply Changes”.
+3>Click on “Save Page”
+4>Click on “Review your Changes”. Notice DISPLAYTITLE:titlename is shown under your text.
+5> Now click on Return to Save form. Click on “Cancel” on the Save your changes dialog.
+6>Go to Advanced Settings again in Page options. 
+7>Uncheck the “Enable Display title” checkbox and click to “Apply Changes”. 
+8> Repeat step#3 and #4. Notice even after disabling the display title it is still visible under your text in the “Review your changes” dialog. Open the advanced settings and you would notice that the enable display title is unchecked, but it shows up in Review your changes.
+
+Try the above steps with the other settings such as “Let this page be indexed by search engines”, “Show a tab on this page to add a new section”and with Categories too.Please see screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14243}",1406577600,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ojclybdvdmwc7icip62q,task_description,resolved
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"
+
+*** This bug has been marked as a duplicate of bug 68619 ***",1406577779,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ojclybdvdmwc7icip62q,task_subcomment,NA
+"VisualEditor: Comment Edit dialog does not close, after inserting a list.","screenshot
+
+Environment- test2 and betalabs
+
+Steps-
+1> Open a blank page in VE and type in some text.
+2>At the end of the text insert a comment.
+3>Click on the Comment , to open the comment edit dialog.
+4> Now while the cursor is till in the comment edit dialog , click to insert a bullet point / numbered list.
+5>Now click on “Done” or “Remove” to close the dialog. The dialog stays open.Please see screenshot.
+
+Same behavior in Chrome, FF and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows XP
+
+**Attached**: {F14169}",1406559660,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-rci6ybeykugoc2ofg22w,task_description,resolved
+"VisualEditor: Comment Edit dialog does not close, after inserting a list.","Merging with bug 68679.
+
+*** This bug has been marked as a duplicate of bug 68679 ***",1406597593,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rci6ybeykugoc2ofg22w,task_subcomment,NA
+VisualEditor should display entire comment when the orange icon is clicked,"Screenshot of too-small comment popup
+
+Currently, when the orange comment icon is clicked, we see only the first few words of the comment.
+
+To read the whole comment, we have to click again, which takes us to the edit view. You shouldn't have to launch the editor just to read the whole text.
+
+The little popup that comes up when you first click the icon (I've lost track of VE jargon, sorry) should show the entire comment text, over multiple lines if necessary, and preferably in black or a darker gray.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14130}",1406542140,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-mxtw6d3rc6477dklsvnc,task_description,declined
+VisualEditor should display entire comment when the orange icon is clicked,"(In reply to This, that and the other (TTO) from comment #2)
+> You don't think 8 words is rather too short?
+
+The number of words shown is language dependent.
+
+On my system, if the comment is ""This is a ridiculously-long sesquipedalian comment."" you get everything except "" comment.""
+
+If the comment is ""Please don't change Obama's name."" it shows the entire thing, which is the point of showing the snippet version.",1406584613,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxtw6d3rc6477dklsvnc,task_subcomment,NA
+VisualEditor should display entire comment when the orange icon is clicked,You don't think 8 words is rather too short?,1406582833,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-mxtw6d3rc6477dklsvnc,task_subcomment,NA
+VisualEditor should display entire comment when the orange icon is clicked,"No. People writing long comments is a sign that they're doing it wrong, and encouraging such bad practice is contrary to helping editors.",1406564517,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxtw6d3rc6477dklsvnc,task_subcomment,NA
+"beta: ResourceLoader CSS URL gzipped twice, causing skins to be broken","One of the CSS resource loader URL yield content which is gzipped twice :-(
+
+The content is shown by piping to gzcat twice:
+
+curl 'http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles%7Cwikibase.client.init&only=styles&skin=vector&*'|gzcat|gzcat
+
+Headers:
+
+> User-Agent: curl/7.30.0
+> Host: bits.beta.wmflabs.org
+> Accept: */*
+> 
+< HTTP/1.1 200 OK
+* Server Apache is not blacklisted
+< Server: Apache
+< Access-Control-Allow-Origin: *
+< Expires: Mon, 28 Jul 2014 09:22:53 GMT
+< X-Content-Type-Options: nosniff
+< Content-Encoding: gzip, gzip
+< X-Powered-By: HHVM/3.3.0-dev
+< Cache-control: public, max-age=300, s-maxage=300
+< Vary: Accept-Encoding
+< Last-Modified: Thu, 24 Jul 2014 03:43:51 GMT
+< Content-Type: text/css; charset=utf-8
+< Content-Length: 24050
+< Accept-Ranges: bytes
+< Date: Mon, 28 Jul 2014 09:19:08 GMT
+
+
+
+Same goes on when passing Accept-Encoding: gzip
+
+I restarted varnish on the bits cache to clear up the bits cache, hasn't solved anything.
+
+
+The minified CSS cache key is enwiki:resourceloader:filter:minify-css:7:e07e6ad07840d291e66cf3fe9f0980c3
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406539320,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-j7533hletfeocs3ygieq,task_description,resolved
+"beta: ResourceLoader CSS URL gzipped twice, causing skins to be broken",Fixed in 4bdfea04cea2e54e6076a1c6b955ba1e1b51209f.,1411712675,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-j7533hletfeocs3ygieq,task_subcomment,NA
+"beta: ResourceLoader CSS URL gzipped twice, causing skins to be broken","Niklas reported it to be fixed in Vagrant:
+
+ hhvm: set GzipCompressionLevel = 0 to avoid double-gzip
+ https://gerrit.wikimedia.org/r/#/c/145771/
+
+Which was bug 67928",1406561078,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-j7533hletfeocs3ygieq,task_subcomment,NA
+"beta: ResourceLoader CSS URL gzipped twice, causing skins to be broken","Proper command:
+
+curl 'http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles%7Cwikibase.client.init&only=styles&skin=vector&*' | gzcat | gzcat
+
+** yields some CSS **",1406560868,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-j7533hletfeocs3ygieq,task_subcomment,NA
+VisualEditor: Edge case of unintentional image removal,"See https://it.wikipedia.org/w/index.php?title=Vallo_Atlantico&oldid=66317144&veaction=edit :
+Reach the paragraph ""Comandi del Vallo Atlantico"", see there's a list there.
+It looks weird because the syntax for the picture on the right is in the middle of the list.
+Average user doesn't actually know/realize this and just wants to fix the list.
+S/he will place the cursor right after the word ""Danimarca"" on the second line and hit Canc. The pic suddenly disappears.
+ 
+(Right now there's a further bug 68708 which did lead to the image being removed without the user really noticing it: he noticed that the ""Commando tedesco"" line was not aligned properly and tried to fix that by going on that line and hitting Backspace. He didn't notice the pic getting highlighted and hit Backspace again, so the page lost focus and all he could see when he read the list again was that he had fixed it.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406532480,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5usl4n5awcjbcbomw5bs,task_description,resolved
+VisualEditor: Edge case of unintentional image removal,"This is probably now fixed, as we change the selection when you type and move the object into view (so it's clear what's going to happen).",1444159075,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5usl4n5awcjbcbomw5bs,task_subcomment,NA
+VisualEditor:  Changes made after canceling a Save are lost,"Steps to Reproduce:
+1. Add some text to a page (""abc"").
+
+2. Click 'Save'.
+
+3. Think, ""Oops, I forgot to add…""
+
+4. Click the cancel button on the Save dialog.
+
+5. Go add the other text (""xyz"") (or add or change images, templates, refs, or remove the abc text that you typed earlier; it doesn't matter what changes you make).
+
+6. Save the page.
+
+7. Where's the ""xyz"" text I just added?!
+
+Actual Results:  
+This is a ""lose most of your work"" bug:  
+
+Everything you do after cancelling the first time is irretrievably lost, and unless you just happen to Review Changes before saving, you won't know that you're going to lose everything until it's too late to copy it to another page.
+
+
+Reproducible: Always
+
+Reported in Safari 7.1 on OS X 10.9.4; confirmed in Safari 6.1.4 and Firefox 30 on Mac OS 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1406498640,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-geqryn2sngosctjjau7u,task_description,resolved
+VisualEditor:  Changes made after canceling a Save are lost,"
+
+*** This bug has been marked as a duplicate of bug 68619 ***",1406564584,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-geqryn2sngosctjjau7u,task_subcomment,NA
+VisualEditor: Pawn ♙ appears if you type near a [[Link]] after the {{convert}} template,"Intention:
+Add a missing word (""and"") towards the end of a sentence.  
+
+Steps to Reproduce:
+1. Start with a pragraph that contains:
+
+* the en.wp {{convert}} template
+* several [[Links]] after the template
+
+2. Click before or after one of these links.
+
+3. Type a space and the word ""and"" (or any word, but don't press return to create a new paragraph).
+
+4. See the pawns?
+
+5. Now click somewhere else, and watch the pawns and text replicate.
+
+Actual Results:  
+See https://en.wikipedia.org/w/index.php?oldid=618713444#Composition for an example of the results.
+
+
+Reproducible: Always
+
+Found in Firefox 31 on Windows 7; confirm in Safari 6 on Mac OS 10.8.5
+
+May be related to Bug 68151
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/w/index.php?oldid=618713444#Composition
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68151",1406497380,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wbqcdudfren5nxeb76rg,task_description,resolved
+VisualEditor: Pawn ♙ appears if you type near a [[Link]] after the {{convert}} template,"Yeah, I think this is the same.
+
+*** This bug has been marked as a duplicate of bug 68151 ***",1406565501,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wbqcdudfren5nxeb76rg,task_subcomment,NA
+VisualEditor: copying a text and moving down using the arrow adds a space,"It often happens to me that I select a letter in a word, copy it using Ctrl-C, and move the caret to the next line using the arrow-down keyboard key, and a space is added before the letter that I selected.
+
+It's not completely consistent, but it happens in about 70% of my attempts to do the above.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406466780,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7eeeai67evjmijctkql6,task_description,resolved
+VisualEditor: copying a text and moving down using the arrow adds a space,"Not reproducible anymore - marking it as Resolved. 
+
+For such issues any additional info would be helpful: which browser/OS the issue was happening. Also, the structure of a page may be important - say, the issue happens in bulleted list, or within a text with inline images etc",1425003675,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-7eeeai67evjmijctkql6,task_subcomment,NA
+PHP Notice:  Undefined index: REQUEST_TIME in extensions/EventLogging/includes/EventLogging.php on line 56,"php5 phpunit.php
+
+When doing http://paste.debian.net/111811/ , phpunit incurs in this:
+
+PHP Notice:  Undefined index: REQUEST_TIME in /srv/vagrant/mediawiki/extensions/EventLogging/includes/EventLogging.php on line 56
+PHP Stack trace:
+PHP   1. {main}() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:0
+PHP   2. MediaWikiPHPUnitCommand::main() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:160
+PHP   3. PHPUnit_TextUI_Command->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiPHPUnitCommand.php:42
+PHP   4. PHPUnit_TextUI_TestRunner->doRun() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/Command.php:176
+PHP   5. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/TestRunner.php:350
+PHP   6. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+PHP   7. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+PHP   8. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+PHP   9. PHPUnit_Framework_TestSuite->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:749
+PHP  10. MediaWikiTestCase->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:779
+PHP  11. PHPUnit_Framework_TestCase->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiTestCase.php:133
+PHP  12. PHPUnit_Framework_TestResult->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:783
+PHP  13. PHPUnit_Framework_TestCase->runBare() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestResult.php:648
+PHP  14. PHPUnit_Framework_TestCase->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:838
+PHP  15. ReflectionMethod->invokeArgs() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988
+PHP  16. SpecialNewPagesFeedTest->testAddArticles() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988
+PHP  17. ApiTestCase->doApiRequestWithToken() /srv/vagrant/mediawiki/extensions/PageTriage/tests/phpunit/SpecialNewPagesFeedTest.php:100
+PHP  18. ApiTestCase->doApiRequest() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:142
+PHP  19. ApiMain->execute() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:99
+PHP  20. ApiMain->executeAction() /srv/vagrant/mediawiki/includes/api/ApiMain.php:332
+PHP  21. ApiEditPage->execute() /srv/vagrant/mediawiki/includes/api/ApiMain.php:907
+PHP  22. EditPage->internalAttemptSave() /srv/vagrant/mediawiki/includes/api/ApiEditPage.php:401
+PHP  23. Article->doEditContent() /srv/vagrant/mediawiki/includes/EditPage.php:1973
+PHP  24. Article->__call() /srv/vagrant/mediawiki/includes/EditPage.php:1973
+PHP  25. call_user_func_array() /srv/vagrant/mediawiki/includes/page/Article.php:1992
+PHP  26. WikiPage->doEditContent() /srv/vagrant/mediawiki/includes/page/Article.php:1992
+PHP  27. wfRunHooks() /srv/vagrant/mediawiki/includes/page/WikiPage.php:2032
+PHP  28. Hooks::run() /srv/vagrant/mediawiki/includes/GlobalFunctions.php:4031
+PHP  29. call_user_func_array() /srv/vagrant/mediawiki/includes/Hooks.php:206
+PHP  30. WikimediaEventsHooks::onPageContentInsertComplete() /srv/vagrant/mediawiki/includes/Hooks.php:206
+PHP  31. WikimediaEventsHooks::logPageCreation() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:254
+PHP  32. EventLogging::logEvent() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:196
+
+Notice: Undefined index: REQUEST_TIME in /srv/vagrant/mediawiki/extensions/EventLogging/includes/EventLogging.php on line 56
+
+Call Stack:
+    0.0005     252912   1. {main}() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:0
+    3.1858   25034984   2. MediaWikiPHPUnitCommand::main() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:160
+    3.1859   25047464   3. PHPUnit_TextUI_Command->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiPHPUnitCommand.php:42
+   43.5670  196201632   4. PHPUnit_TextUI_TestRunner->doRun() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/Command.php:176
+   43.6076  196524896   5. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/TestRunner.php:350
+ 2979.9686 1021381672   6. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+ 2979.9689 1021383176   7. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+ 3006.5969 1036522696   8. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+ 3007.1232 1037095048   9. PHPUnit_Framework_TestSuite->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:749
+ 3007.1232 1037095048  10. MediaWikiTestCase->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:779
+ 3007.1233 1037095208  11. PHPUnit_Framework_TestCase->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiTestCase.php:133
+ 3007.2455 1037095568  12. PHPUnit_Framework_TestResult->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:783
+ 3007.2457 1037096512  13. PHPUnit_Framework_TestCase->runBare() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestResult.php:648
+ 3007.6986 1037467560  14. PHPUnit_Framework_TestCase->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:838
+ 3007.6987 1037468504  15. ReflectionMethod->invokeArgs() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988
+ 3007.6987 1037468776  16. SpecialNewPagesFeedTest->testAddArticles() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988
+ 3007.6987 1037469976  17. ApiTestCase->doApiRequestWithToken() /srv/vagrant/mediawiki/extensions/PageTriage/tests/phpunit/SpecialNewPagesFeedTest.php:100
+ 3007.6987 1037471616  18. ApiTestCase->doApiRequest() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:142
+ 3007.6992 1037528872  19. ApiMain->execute() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:99
+ 3007.6992 1037528920  20. ApiMain->executeAction() /srv/vagrant/mediawiki/includes/api/ApiMain.php:332
+ 3007.7069 1037555016  21. ApiEditPage->execute() /srv/vagrant/mediawiki/includes/api/ApiMain.php:907
+ 3008.1653 1037899936  22. EditPage->internalAttemptSave() /srv/vagrant/mediawiki/includes/api/ApiEditPage.php:401
+ 3008.2155 1037909472  23. Article->doEditContent() /srv/vagrant/mediawiki/includes/EditPage.php:1973
+ 3008.2155 1037910264  24. Article->__call() /srv/vagrant/mediawiki/includes/EditPage.php:1973
+ 3008.2155 1037910704  25. call_user_func_array() /srv/vagrant/mediawiki/includes/page/Article.php:1992
+ 3008.2155 1037911512  26. WikiPage->doEditContent() /srv/vagrant/mediawiki/includes/page/Article.php:1992
+ 3008.3812 1037999520  27. wfRunHooks() /srv/vagrant/mediawiki/includes/page/WikiPage.php:2032
+ 3008.3812 1037999568  28. Hooks::run() /srv/vagrant/mediawiki/includes/GlobalFunctions.php:4031
+ 3008.3813 1038001544  29. call_user_func_array() /srv/vagrant/mediawiki/includes/Hooks.php:206
+ 3008.3813 1038002848  30. WikimediaEventsHooks::onPageContentInsertComplete() /srv/vagrant/mediawiki/includes/Hooks.php:206
+ 3008.3813 1038002848  31. WikimediaEventsHooks::logPageCreation() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:254
+ 3008.3813 1038003736  32. EventLogging::logEvent() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:196
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14495}",1406409960,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-svm6hns77rkpqj4hta5x,task_description,invalid
+PHP Notice:  Undefined index: REQUEST_TIME in extensions/EventLogging/includes/EventLogging.php on line 56,"The `REQUEST_TIME` code that assumed HTTP context and was problematic when called from the command-line (e.g. in PHPUnit) was removed in {c12e93f9e1f5b05776bfb96ae467ffef15e7f13c}.
+
+```lang=diff
+@@ -53,22 +60,17 @@ static function logEvent( $schemaName, $revId, $event, $options = 0 ) {
+-			'timestamp'        => $_SERVER[ 'REQUEST_TIME' ],		
+```",1475706089,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-svm6hns77rkpqj4hta5x,task_subcomment,NA
+PHP Notice:  Undefined index: REQUEST_TIME in extensions/EventLogging/includes/EventLogging.php on line 56,"Your definition of ""a bunch"" differs of 1-2 orders of magnitude from mine. :) I still have open patches to fix the bugs I found in the last phpunit run; until those are merged in gerrit, I won't try again.",1421413832,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-svm6hns77rkpqj4hta5x,task_subcomment,NA
+PHP Notice:  Undefined index: REQUEST_TIME in extensions/EventLogging/includes/EventLogging.php on line 56,"Seems EventLogging works fine under HHVM with a bunch of other extensions. Proposed https://gerrit.wikimedia.org/r/#/c/185405/ passed and ran with:
+
+```
+mediawiki/extensions/AbuseFilter
+mediawiki/extensions/CheckUser
+mediawiki/extensions/ConfirmEdit
+mediawiki/extensions/Echo
+mediawiki/extensions/EventLogging
+mediawiki/extensions/JsonConfig
+mediawiki/extensions/Mantle
+mediawiki/extensions/MobileApp
+mediawiki/extensions/MobileFrontend
+mediawiki/extensions/SpamBlacklist
+mediawiki/extensions/Thanks
+mediawiki/extensions/VisualEditor
+mediawiki/extensions/WikiGrok
+mediawiki/extensions/ZeroBanner
+mediawiki/extensions/ZeroPortal
+```
+
+Can you still reproduce?",1421407816,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-svm6hns77rkpqj4hta5x,task_subcomment,NA
+VisualEditor Mobile: fresh accounts being taken to VE by default on beta labs,"Possible regression: Today I created a few fresh accounts on beta labs (desktop Chrome browser, mobile site) to test other stuff, and I noticed that when I tapped the edit pencil for the first time, I was taken to the VE editor instead of wikitext editor. Awhile back, we decided *not* to send new users to VE by default on any wiki and merged a patch to fix this -- looks like it's no longer working 
+:-/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406312100,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-nhp4v32xljmakc2dxomi,task_description,declined
+VisualEditor Mobile: fresh accounts being taken to VE by default on beta labs,"When I cleared cookies, the problem disappeared, so it must've been just lingering VE cookie crumbs on my machine from all those sockpuppets I've been using on beta labs :) Closing.",1406742992,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-nhp4v32xljmakc2dxomi,task_subcomment,NA
+VisualEditor Mobile: fresh accounts being taken to VE by default on beta labs,So far haven't been able to reproduce this. Tested in desktop Chrome on beta labs.,1406316292,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-nhp4v32xljmakc2dxomi,task_subcomment,NA
+VisualEditor Mobile: fresh accounts being taken to VE by default on beta labs,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/0AK0U7Nl",1406312415,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nhp4v32xljmakc2dxomi,task_subcomment,NA
+"VisualEditor: Sidebar button ""Add more information"" in template dialog is cut off / too long","Screenshot of bug
+
+In general items in the sidebar are wiki input (template names, parameter names) which are fine being cut off.
+
+When the item is a UI element for inserting a new parameter though, it shouldn't be cut off. We might as well put the ellipsis in the localisation message (joking) for it is never rendered fully... (also no tooltip with full version). This is even more problematic considered it's localised. In English the first two words are enough to make sense of it, but we can't assume that for all languages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14224}",1406169480,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-27c6qwr5exrk2ddgkl7k,task_description,declined
+"VisualEditor: Sidebar button ""Add more information"" in template dialog is cut off / too long","Width is fine in en/fr/de/nl, and appears in response to user action, selected at first.",1415062542,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-27c6qwr5exrk2ddgkl7k,task_subcomment,NA
+VisualEditor: Template dialog should provide a way to add parameters up front,"Right now there's imho two usability issues with the default (simplified) Template editor related to getting to the screen for adding parameters.
+
+I expect to see an input field and a pool of parameters to pick from right after clicking.
+
+Instead there is a widget labelled ""Add more information"". This is apparently the button to unhide the panel to add parameters. I'm not sure how this is useful, we can just ditch that button and have that always be visible? (maybe in the odd case of templates with no known parameters or explicitly documented as taking none we could hide it behind a button to avoid confusion, but we should optimise for the common case).
+
+This widget is confusing because:
+* It's labelled ""more"" information, but at this point it's the first parameter, not an additional one (unless you count the template name as information).
+* It's called ""information"" which is a bit vague (we use ""parameter"" and ""field"" elsewhere).
+* After inserting a parameter, the insertion panel goes away and I have to re-open it again. I recall it being there from the start and staying there in the past. Because it's implemented as a placeholder for an individual parameter now, this is presumably no longer possible. I think we should make this panel the ""add parameter"" interface, and not have ""add parameter"" insert this placeholder panel for a one-off use.
+
+I'd say, as a first step (enough to fix this bug), hide the button, have the panel be visible from the start. And then continue like it is now (after inserting the first, the ""add more information"" button is used to add additional parameters.",1406169000,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qxncvpizrrogrxizezsv,task_description,resolved
+VisualEditor: Template dialog should provide a way to add parameters up front,"It seems like the current version of the template dialog has fixed these usability problems, so I'm closing.",1434390920,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-qxncvpizrrogrxizezsv,task_subcomment,NA
+VisualEditor: Page Settings option is getting cut off in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open any page in betalabs with VE
+2.Open the page settings option
+
+Observed Result:
+The Page Settings menu is getting cut off
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14188}",1406154540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gns6o7tbrfc7vxzburbb,task_description,resolved
+VisualEditor: Page Settings option is getting cut off in Betalabs,"
+
+*** This bug has been marked as a duplicate of bug 57366 ***",1406156548,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gns6o7tbrfc7vxzburbb,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Screenshot tests have their own build, we do not want them running in the regular VE build: https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/115/testReport/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1406143740,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-kpls4bc5j2jlc3ln667n,task_description,resolved
+don't run screenshot tests in normal VE build,"Change 149045 merged by jenkins-bot:
+Language screenshot feature file runs only in language screenshot job
+
+https://gerrit.wikimedia.org/r/149045",1406547587,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Change 149047 merged by jenkins-bot:
+[BrowserTest] Language screenshot feature runs only for language screenshot job
+
+https://gerrit.wikimedia.org/r/149047",1406224326,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Change 149047 had a related patch set uploaded by Vikassy:
+[BrowserTest] Language screenshot feature runs only for language screenshot job
+
+https://gerrit.wikimedia.org/r/149047",1406222044,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Change 149045 had a related patch set uploaded by Vikassy:
+WIP: Language screenshot runs only for language screenshot job
+
+https://gerrit.wikimedia.org/r/149045",1406221503,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Vikas and I will pair on this, probably today.",1406186868,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+VisualEditor: The highlight that appears after adding a template while selecting an image is not proper,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Select the image and insert a template like citation needed
+
+Observed Result:
+A highlight appears all around the image 
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14620}",1406068320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cz65rk35yeaxpnwx5nca,task_description,resolved
+VisualEditor: The link inspector appears over the toolbar while trying to add it inside an image for the first time,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE.
+2.Go to Insert>Media.
+3.Search for an image.
+4.Select an image.
+5.When the Media Settings>General settings for that image appears,click on the link inspector icon
+
+Observed Result:
+The link inspector icon appears over the toolbar,overlapping with the border of the Media dialog
+
+See the screenshot attached
+
+
+This issue was found in test2, I need to test it in master once Betalabs is alive again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14472}",1405986960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2bpmj5q3ahfokc4zz46h,task_description,resolved
+VisualEditor: The link inspector appears over the toolbar while trying to add it inside an image for the first time,Resolved months ago.,1423675914,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2bpmj5q3ahfokc4zz46h,task_subcomment,NA
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself","When I select (highlight) some text on the edit mode and start to type some text by replacing the old text, Visual Editor starts copying the text and typing by itself. I've seen it happening only on few articles, like https://fi.wikipedia.org/w/index.php?title=Arseni_Jatsenjuk&veaction=edit and https://fi.wikipedia.org/w/index.php?title=Mykola_Azarov&veaction=edit
+
+I tried this with Firefox and Chrome, logged-in / logged-out, and the same happens on both browsers.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405796700,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-e7pblfgszxhcuzstcumk,task_description,resolved
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself",Seems to be fixed - not reproducible.,1415061931,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-e7pblfgszxhcuzstcumk,task_subcomment,NA
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself","Yeah, I'm pretty sure we fixed this CE buggy stuff a few months ago.",1415055305,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e7pblfgszxhcuzstcumk,task_subcomment,NA
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself",I can't reproduce this issue...,1414806783,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-e7pblfgszxhcuzstcumk,task_subcomment,NA
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself","In case someone didn't understand my explanation, I have a video uploaded to http://tinypic.com/r/mbik2w/8
+On the video I only typed ""k"" (it doesn't matter what key you hit), and that's what happened.",1405963159,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-e7pblfgszxhcuzstcumk,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"https://test.wikipedia.org/w/index.php?title=Topic:Foo&action=edit&redlink=1
+
+[42ec2509] /w/index.php?title=Topic:Foo&action=edit&redlink=1 Exception from line 2340 of /usr/local/apache/common-local/php-1.24wmf14/includes/EditPage.php: This content model is not supported: flow-board
+
+Backtrace:
+
+#0 /usr/local/apache/common-local/php-1.24wmf14/includes/EditPage.php(960): EditPage->toEditText(Flow\Content\BoardContent)
+#1 /usr/local/apache/common-local/php-1.24wmf14/includes/EditPage.php(536): EditPage->initialiseForm()
+#2 /usr/local/apache/common-local/php-1.24wmf14/includes/actions/EditAction.php(49): EditPage->edit()
+#3 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(431): EditAction->show()
+#4 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(295): MediaWiki->performAction(Article, Title)
+#5 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(603): MediaWiki->performRequest()
+#6 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(452): MediaWiki->main()
+#7 /usr/local/apache/common-local/php-1.24wmf14/index.php(46): MediaWiki->run()
+#8 /usr/local/apache/common-local/w/index.php(3): require(string)
+#9 {main}
+
+--------------------------
+**Version**: master
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=73443",1405736340,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-dqhh6futiytkca6um27i,task_description,resolved
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"This bug is about the behavior of a wiki link `[[Topic:NoSuchUUID]]` MW detects the page doesn't exist so turns it into a URL with `?action=edit&redlink=1`.
+
+Flow's behavior with such a ""redlink"" URL is now:
+  # Redirect to plain Topic:NoSuchUUID
+  # With the fix in T75443 , that results in HTTP status 500 and a friendlier ""The requested page title was invalid. Pages in the Topic namespace are automatically created by Flow."" (`flow-error-invalid-topic-uuid` msg)
+
+I think this is reasonable behavior, so we can declare this resolved ",1418762041,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"Update: there is still an exception being thrown at 
+https://test.wikipedia.org/w/index.php?title=Topic:Foo&action=edit&redlink=1",1409838575,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,S Page is aware of this issue. He describes it here: https://www.mediawiki.org/wiki/User:S_Page_(WMF)#Flow_board_links,1408845798,PHID-USER-zcsdm7lwcehnusyhh6xp,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"(In reply to Justin Breeze from comment #3)
+> Just a note...
+> 
+> I am getting this same error on new pages only. I am using VisualEditor.
+> 
+> When I update the portion of the URL from ""&action=edit&redlink=1"" to
+> ""&veaction=edit&redlink=1"" it works fine.
+
+The only reason this works is because the &veaction=edit is completely ignored, thus not creating any problem.",1407458788,PHID-USER-zcsdm7lwcehnusyhh6xp,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"Update: VisualEditor isn't the problem. Its the &action=edit portion of the link. If I click on a link that doesn't include &action=edit (even if the page isn't created), such as http://website/w/index.php/User_talk:User, everything works like normal. But if I click a link, such as http://website/w/index.php?title=User_talk:User&action=edit&redlink=1, I get the error described.",1407458552,PHID-USER-zcsdm7lwcehnusyhh6xp,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,Confirmed on my wiki. Only happens with new pages and when VisualEditor is on. Everything is resolved when VisualEditor is turned off.,1407192765,PHID-USER-zcsdm7lwcehnusyhh6xp,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"**jbreeze** wrote:
+
+Just a note...
+
+I am getting this same error on new pages only. I am using VisualEditor.
+
+When I update the portion of the URL from ""&action=edit&redlink=1"" to ""&veaction=edit&redlink=1"" it works fine.",1406563136,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"Just for the record, a different error is seen at https://test.wikipedia.org/wiki/Topic:Foo
+
+== Error ==
+
+Invalid value was provided for loading flow content. 
+
+Return to Main Page.
+
+[6cf2bd00] /wiki/Topic:Foo Exception from line 162 of /usr/local/apache/common-local/php-1.24wmf14/extensions/Flow/includes/Model/UUID.php: Unknown input to UUID class
+
+Backtrace:
+
+#0 /usr/local/apache/common-local/php-1.24wmf14/extensions/Flow/includes/Actions/Action.php(118): Flow\Model\UUID::create(string)
+ #1 /usr/local/apache/common-local/php-1.24wmf14/extensions/Flow/includes/Actions/Action.php(70): Flow\Actions\FlowAction->detectWorkflowId(Title, WebRequest)
+ #2 /usr/local/apache/common-local/php-1.24wmf14/extensions/Flow/includes/Actions/Action.php(32): Flow\Actions\FlowAction->showForAction(string)
+ #3 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(431): Flow\Actions\FlowAction->show()
+ #4 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(295): MediaWiki->performAction(Article, Title)
+ #5 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(603): MediaWiki->performRequest()
+ #6 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(452): MediaWiki->main()
+ #7 /usr/local/apache/common-local/php-1.24wmf14/index.php(46): MediaWiki->run()
+ #8 /usr/local/apache/common-local/w/index.php(3): require(string)
+ #9 {main}",1405997915,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"Put this in the backlog: https://trello.com/c/L7Kokob5
+
+Thanks for the report!",1405960431,PHID-USER-37czexl6ekrvcmp2tyqq,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+VisualEditor:  No Language selected in the Language Selector shows “$1”,"Screenshot
+
+Steps-
+1> Select Language form the Style text drop down.
+2>In the Language Selector dialog delete the two-letter code. Press done.
+3> Now type in some text in the editor, notice that beside the Language icon there is “$1” in the tootltip. See Screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14154}",1405639620,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-73pt5ehjfcwtumxwpuww,task_description,resolved
+VisualEditor:  No Language selected in the Language Selector shows “$1”,Fixed as a side effect of https://gerrit.wikimedia.org/r/#/c/160098/,1414136569,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-73pt5ehjfcwtumxwpuww,task_subcomment,NA
+VisualEditor:  No Language selected in the Language Selector shows “$1”,"Yes, happening in Betalabs as well.",1405642206,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-73pt5ehjfcwtumxwpuww,task_subcomment,NA
+VisualEditor:  No Language selected in the Language Selector shows “$1”,Tested on test2.,1405639745,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-73pt5ehjfcwtumxwpuww,task_subcomment,NA
+can't search image when inserting media in private wiki,"**Author:** `Coiby.Xu`
+
+**Description:**
+I'm testing VisualEditor on 1.23.1. Everything is OK except for inserting an image. When you insert media, you can't use search function. The error message is 'error"":{""code"":""readapidenied"",""info"":""You need read permission to use this module""}'. However if I set  $wgGroupPermissions['*']['read'] = true, the pictures will be shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405582980,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hnf7dr4pfcowjzfzszvb,task_description,resolved
+can't search image when inserting media in private wiki,"I think this is bug 64822.
+
+*** This bug has been marked as a duplicate of bug 64822 ***",1406584368,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hnf7dr4pfcowjzfzszvb,task_subcomment,NA
+can't search image when inserting media in private wiki,Confirmed on officewiki,1406314983,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hnf7dr4pfcowjzfzszvb,task_subcomment,NA
+can't search image when inserting media in private wiki,"I can confirm this issue. The problem is related to the use of the parameter 'callback=jQuery...' in the api call. 
+
+According to https://www.mediawiki.org/wiki/API:Data_formats#Callback_restrictions, when callback mode is used clients are treated as anonymous users, even after logging in. Is callback mode strictly necessary?",1405967872,PHID-USER-wz5bw3q6zykhqbbeohzq,PHID-TASK-hnf7dr4pfcowjzfzszvb,task_subcomment,NA
+VisualEditor: Blank link inspector UI appears when trying to open it inside the Media Settings while selecting another image in the caption,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page and insert an image
+2.Insert another image inside it
+3.Select the image inside and try to open link inspector
+
+Observed Result;
+The link inspector appears without any UI'
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14529}",1405550460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fsbewl22leh75q5wxi4m,task_description,resolved
+VisualEditor: Blank link inspector UI appears when trying to open it inside the Media Settings while selecting another image in the caption,"The inspector now ""works"", but due to bug 72431 immediately closes, AFAICT. Nominally FIXED.",1416342840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsbewl22leh75q5wxi4m,task_subcomment,NA
+"VisualEditor: Select text, type = garbled, repeated text + snowman on el.wp","See https://el.wikipedia.org/w/index.php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82%3AElitre_%28WMF%29%2Fsandbox&diff=4757904&oldid=4757901 .
+Replace one or more words with ""Foobar"" (that is, highlight the word(s), then type Foobar). Works once, works twice, then the third time corruption happens and le wild snowman appears.
+Must say that I only managed to reproduce that in my sandbox, which features content from https://el.wikipedia.org/wiki/%CE%95%CF%80%CE%B9%CF%84%CF%8C%CE%BA%CE%B9%CE%BF , and in this article page.
+It happens in Chrome and Firefox, tested under Windows 7, Ubuntu 13.10 and OS X 10.8.
+During an attempt to reproduce, VE also suppressed existing nowiki tags: https://el.wikipedia.org/w/index.php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82:P.a.a/%CF%80%CF%81%CF%8C%CF%87%CE%B5%CE%B9%CF%81%CE%BF&diff=next&oldid=4757859 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405545780,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bnj7f5cnhoxzikonjjvj,task_description,resolved
+"VisualEditor: Select text, type = garbled, repeated text + snowman on el.wp","I think the Πηγή template is the issue here; down-page of the template everything breaks, up-page it works. That means it's almost certainly a duplicate of bug 67992.
+
+*** This bug has been marked as a duplicate of bug 67992 ***",1406598882,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bnj7f5cnhoxzikonjjvj,task_subcomment,NA
+"VisualEditor: Select text, type = garbled, repeated text + snowman on el.wp","I found another, smaller, text that manifests this bug https://el.wikipedia.org/w/index.php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82:P.a.a/%CF%80%CF%81%CF%8C%CF%87%CE%B5%CE%B9%CF%81%CE%BF&oldid=4767252",1406051395,PHID-USER-sbwcezpm5yhfcbntreum,PHID-TASK-bnj7f5cnhoxzikonjjvj,task_subcomment,NA
+"VisualEditor: Select text, type = garbled, repeated text + snowman on el.wp","(In reply to Elitre from comment #0)
+> See
+> https://el.wikipedia.org/w/index.
+> php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82%3AElitre_%28WMF%29%2Fsan
+> dbox&diff=4757904&oldid=4757901 .
+> Replace one or more words with ""Foobar"" (that is, highlight the word(s),
+> then type Foobar). Works once, works twice, then the third time corruption
+> happens and le wild snowman appears.
+> Must say that I only managed to reproduce that in my sandbox, which features
+> content from
+> https://el.wikipedia.org/wiki/
+> %CE%95%CF%80%CE%B9%CF%84%CF%8C%CE%BA%CE%B9%CE%BF , and in this article page.
+> It happens in Chrome and Firefox, tested under Windows 7, Ubuntu 13.10 and
+> OS X 10.8.
+> During an attempt to reproduce, VE also suppressed existing nowiki tags:
+> https://el.wikipedia.org/w/index.
+> php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82:P.a.a/
+> %CF%80%CF%81%CF%8C%CF%87%CE%B5%CE%B9%CF%81%CE%BF&diff=next&oldid=4757859 .
+
+The nowiki tags around the percentage signs were added by me, in an effort to eliminate a possible, if remote, cause of interference.",1405546425,PHID-USER-sbwcezpm5yhfcbntreum,PHID-TASK-bnj7f5cnhoxzikonjjvj,task_subcomment,NA
+VisualEditor: Easy way to reproduce a weird behavior with the link tool,"Take a page like https://en.wikipedia.org/wiki/Heliozela_rutilella?veaction=edit (that is, starting with a template, so there's some space above the first line of the article).
+Clicking on the link tool and pressing ESC will automatically make the first word (Heliozela) a link to the Heliozela article. 
+Click on the up arrow, then click on the link tool again, and press ESC. You get the word Heliozela again (with no links).
+
+**See Also**:
+T70101",1405518780,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-4gkkbuwk3jlg27h57c3x,task_description,resolved
+VisualEditor: Easy way to reproduce a weird behavior with the link tool,Serious comment: Seems to be fixed now. Closing.,1434390715,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-4gkkbuwk3jlg27h57c3x,task_subcomment,NA
+VisualEditor: Easy way to reproduce a weird behavior with the link tool,Test comment! Hi mom!,1430243737,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-4gkkbuwk3jlg27h57c3x,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"Load VE. Say ""Foobar"" is the first word on the page.
+If you click on the link tool, by mistake or not, without selecting anything before, Foobar will automatically become a link to the Foobar page (it doesn't help that pressing ESC doesn't abort the action, the link gets applied anyway, as we know).
+NicoV noticed this in several French articles, where you can quite tell links happened ""by mistake"" since the first word is an article, ""le"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68102",1405517940,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-huk6uolixsrw4vl5idv3,task_description,declined
+VisualEditor: Don't allow a linking action if no text was highlighted before,"Ah. Bug 69407. Alright, thanks.",1407778944,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"I hereby distance myself from that guy who wrote ""enhancement"" in comment 8, as differing interpretations and judgements of that term might trigger ""lies"". Please feel free to argument why not supporting Esc is a ""serious bug"" in a separate, non-enhancement request if you wish so. Thank you.",1407778842,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"**ronnirubin** wrote:
+
+(In reply to Andre Klapper from comment #8)
+> (In reply to Arthur Rubin from comment #7)
+> > I don't know how to reopen this.
+> 
+> You were asked to not reopen this, but to file a new and separate
+> enhancement request for the Esc behavior if you wish so.
+
+So, you want me to lie and call it an ""enhancement request"" rather than a bug fix.  _That_, I won't do.  I'll still call it a bug fix, and apparently a serious one.",1407776541,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"(In reply to Arthur Rubin from comment #7)
+> I don't know how to reopen this.
+
+You were asked to not reopen this, but to file a new and separate enhancement request for the Esc behavior if you wish so.",1407775711,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"**ronnirubin** wrote:
+
+I don't know how to reopen this.  As an Admin on en.Wikipedia, I can say that having ""Escape"" _not_ close the box and take none of the actions indicated in the box is a deal-stopper for me.  I will argue against VE be made default if this isn't fixed.",1407772821,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,Please don't edit war on Bugzilla. Create a new bug about an actual issue if you wish.,1407699357,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"Well, give me one example of a software behaving like that: in any software I know, when you click on a button that open a dialog, if you cancel the dialog then no action is done.
+
+The current behavior is probably the reason of many links created in frwiki to pages ""Le"", ""La"", ""Les"", ... (all created by VE) which we have to fix on a regular basis. And we obviously miss all the other links created by mistake.
+
+Please, change the current behavior, so that Esc key behaves as in any normal software.",1407697489,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"(In reply to NicoV from comment #2)
+> But the main problem with this is that the ESC key is not working correctly
+> (it should cancel the action and not silently validate it). Do you plan to
+> do something to make the ESC key work as it works in every other application
+> ?
+
+You are mistaken. The Escape key is doing exactly what users expect; it closes the window. The user clicking the link button – not the closing the link editor window – is what makes the link.",1407697132,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,Please read my comment: the main problem is ESC key not working at all as could be expected by any user.,1407692120,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"I was the one reporting the issue with words like ""le"" being made into internal links by mistake on frwiki. I think the behavior of automatically selecting the entire word when make an internal link should be kept (it's probably causing less issues than it's avoiding).
+
+But the main problem with this is that the ESC key is not working correctly (it should cancel the action and not silently validate it). Do you plan to do something to make the ESC key work as it works in every other application ?",1405575017,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,This is explicitly a feature that was requested (years ago now). People clicking buttons and not paying attention to what they're doing seems more like a social issue than a software bug.,1405533552,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+performance degradation with new UI,"Seen on beta labs as 15 July: 
+
+Upon loading a simple page such as http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+The contentEditable surface used to appear reliably in under ten seconds.  Now I am seeing 10+ second load times for about one page load of every three.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405466760,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-hfno6mirclxxp4wamoqs,task_description,invalid
+performance degradation with new UI,"
+I reported this poorly, needs more research.",1405467205,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-hfno6mirclxxp4wamoqs,task_subcomment,NA
+Opens wrong page in Edit source after making change in VE in old version of artcle,"*open old version of artcle
+*press tab Edit
+*make some changes
+*press tab Edit source
+*in warnng window press ""Discard changes""
+->will open this page https://en.wikipedia.org/w/index.php?action=edit&veswitched=1
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 8.1
+**Platform**: PC",1405437840,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-c57y4fdc3ukcmw6umira,task_description,declined
+Opens wrong page in Edit source after making change in VE in old version of artcle,"(In reply to James Forrester from comment #1)
+> This is consistent with how the wikitext editor works – on an old page, the
+> ""Read"" link goes to the latest (not old) version of the page. VisualEditor
+> deliberately does the same as that.
+
+
+May be possible change link for tab Editsource while user work in VE and do the same thing that do [Ξ]->""Switch to source code"". This enough intuitive behavior.",1405448944,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-c57y4fdc3ukcmw6umira,task_subcomment,NA
+Opens wrong page in Edit source after making change in VE in old version of artcle,"This is consistent with how the wikitext editor works – on an old page, the ""Read"" link goes to the latest (not old) version of the page. VisualEditor deliberately does the same as that.",1405448377,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c57y4fdc3ukcmw6umira,task_subcomment,NA
+"VisualEditor: switching to ""Default"" image size in image inspector does not make Apply Changes button active","in order to save this change a user must make another change in the dialog in addition to setting the image size to default
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405390800,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-vfapjnaswl6rsvgrurvh,task_description,resolved
+"VisualEditor: switching to ""Default"" image size in image inspector does not make Apply Changes button active","Yeah, dupe of bug 67684.
+
+*** This bug has been marked as a duplicate of bug 67684 ***",1406427644,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vfapjnaswl6rsvgrurvh,task_subcomment,NA
+"VisualEditor: switching to ""Default"" image size in image inspector does not make Apply Changes button active",Has this bug been fixed? It works fine for me.,1406312751,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vfapjnaswl6rsvgrurvh,task_subcomment,NA
+VisualEditor: required parameter not showing,"**Author:** `manueltassi91`
+
+**Description:**
+In itwiki, we've noticed that when including [it.wikipedia.org/wiki/Template:A] in a page using VE doesn't show all required parameters, but just one. In fact, with VE there should be three required parameters (""Motivazione"", ""Data di inserimento"" ""Argomento""), but in the dialog only ""Motivazione"" is shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405346700,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_description,declined
+VisualEditor: required parameter not showing,I wonder if it was just waiting for someone to null edit the template page. I guess this bug is WFM.,1406314288,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_subcomment,NA
+VisualEditor: required parameter not showing,"**manueltassi91** wrote:
+
+No. At the moment the problem seems to be solved.",1406312725,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_subcomment,NA
+VisualEditor: required parameter not showing,Is this still valid? I just checked and the three required parameters are showing.,1406312461,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_subcomment,NA
+VisualEditor: required parameter not showing,"Possibly a dupe of bug 50747, but still: if a parameter is mandatory, I need to 1) know it is, 2) know I need to add it or the template will be broken. I don't understand why we 1) aren't making the user aware that such parameters exist, 2) are even hiding them, dooming templates to be incomplete and users to be confused.",1405348327,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_subcomment,NA
+VisualEditor: In [[Pristina International Airport]] the backspace key makes the cursor jump further back,"I couldn't reproduce this in any other article, but it may happen elsewhere:
+
+1. Edit https://en.wikipedia.org/wiki/Pristina_International_Airport (I tested in this version: https://en.wikipedia.org/w/index.php?title=Pristina_International_Airport&oldid=615886404 ).
+
+2. Put the caret in the first paragraph, in the word ""handles"".
+
+3. Press Backspace.
+
+Expected: The caret moves one character and deletes it.
+Observed: The caret deletes one character before it, but moves back 26 characers to the beginning of the word ""international"".
+
+Happened to me in Firefox and Chrome on Fedora.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405201260,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-65is3y3rbqummqu5reci,task_description,resolved
+VisualEditor: In [[Pristina International Airport]] the backspace key makes the cursor jump further back,"Aha, this was a dupe of bug 67862. Sorry!
+
+*** This bug has been marked as a duplicate of bug 67862 ***",1406319801,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-65is3y3rbqummqu5reci,task_subcomment,NA
+VisualEditor: In [[Pristina International Airport]] the backspace key makes the cursor jump further back,I guess it was fixed at some point. Thanks for testing.,1406316186,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-65is3y3rbqummqu5reci,task_subcomment,NA
+VisualEditor: In [[Pristina International Airport]] the backspace key makes the cursor jump further back,Hmm... Can't reproduce on the latest version with Chrome.,1406315955,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-65is3y3rbqummqu5reci,task_subcomment,NA
+A menu item of VisusalEditor in Ukrainian Wikipedia has been changed by mistake.,"**Author:** `002soym`
+
+**Description:**
+Intention:
+To edit a wiki code
+
+Steps to Reproduce:
+A menu item of VisusalEditor in Ukrainian Wikipedia has been changed by mistake. Now we have instead of the correct menu item '''Редагувати код''' (Edit code) the absolutely incorrect '''Править викитекст'''. It's not even in Ukrainian.
+[https://uk.wikipedia.org/wiki/MediaWiki:Visualeditor-ca-editsource shows] the correct label here.
+
+Actual Results:  
+menu item '''Править викитекст''' 
+
+Expected Results:  
+menu item '''Редагувати код''' (Edit code)
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://uk.wikipedia.org/wiki/%D0%92%D1%96%D0%BA%D1%96%D0%BF%D0%B5%D0%B4%D1%96%D1%8F",1405130040,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qcsqvh62dwh2bjvi4jg5,task_description,resolved
+A menu item of VisusalEditor in Ukrainian Wikipedia has been changed by mistake.,"As I replied on wiki to you, this is bug 67805
+
+*** This bug has been marked as a duplicate of bug 67805 ***",1405130110,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qcsqvh62dwh2bjvi4jg5,task_subcomment,NA
+Option to use VisualEditor not showing up on non-enwiki projects,"In production in beta. Steps to repro:
+
+1. Go to French, Polish, or Russian Wikipedia (where VE should be the default editing experience). 
+2. Opt into beta, log in, and attempt to edit a page.
+
+Expected: I am taken to VE editing mode, since VE is the default editing experience on those projects.
+
+Actual: I am taken to wikitext editing. Furthermore, I don't have the option to switch to VE editing in the edit window (the cog that shows me the drop-down menu is missing). 
+
+Also observed on Portuguese and Spanish Wikipedia. It seems to be everywhere except enwiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405115820,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-7qcly6qjxshoqdfuzt3e,task_description,invalid
+Option to use VisualEditor not showing up on non-enwiki projects,"Derp, helps to enable beta again after you clear your cookies for testing purposes :)",1405116083,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-7qcly6qjxshoqdfuzt3e,task_subcomment,NA
+Option to use VisualEditor not showing up on non-enwiki projects,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/EShXsKmu",1405116019,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7qcly6qjxshoqdfuzt3e,task_subcomment,NA
+VisualEditor: new autoadded reflist does not display when in VE edit mode,"new reflist behavior adds in the reflist to the saved/rendered display like TOC but when in VE edit mode the reflist is not displayed, which is confusing, especially when user is adding references
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405104840,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-pk3xxotbd2cygxbic2dv,task_description,duplicate
+VisualEditor: new autoadded reflist does not display when in VE edit mode,What is the problem here on the Parsoid end?,1408573896,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-pk3xxotbd2cygxbic2dv,task_subcomment,NA
+VisualEditor: new autoadded reflist does not display when in VE edit mode,I guess this refers to https://gerrit.wikimedia.org/r/#/c/141583/ / bug 66860.,1405105577,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pk3xxotbd2cygxbic2dv,task_subcomment,NA
+"VisualEditor: Table cell templates are editable, but their re-rendering is broken","Screenshot
+
+Table cell templates are editable, but their re-rendering is broken.
+
+Example: try modifying any of the table cell templates at https://nl.wikipedia.org/wiki/Gebruiker:Ad_Huikeshoven/jh?uselang=en&veaction=edit#Prestatietabel
+
+They can be edited, such an edit can be saved and results in correct wikitext, but is rendered broken (the markup is rendered as text, instead of creating a table cell).
+
+(Found when playing with bug 67850.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://nl.wikipedia.org/wiki/Gebruiker:Ad_Huikeshoven/jh?uselang=en&veaction=edit#Prestatietabel
+
+**Attached**: {F14539}",1405090260,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-unakgbnnnqhghsth6f2x,task_description,duplicate
+"VisualEditor: Table cell templates are editable, but their re-rendering is broken","This is because we don't (can't) send context right now when asking for the template to be re-rendered – bug 51146 is the original report of this issue. Merging. (Boo.)
+
+*** This bug has been marked as a duplicate of bug 51146 ***",1405107160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-unakgbnnnqhghsth6f2x,task_subcomment,NA
+VisualEditor: Pawns and reverse typing,"Reported on fr.wp. Verified so far in Win 7 (Chrome and FF). 
+
+You can use this page https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_%28WMF%29/Prove2&oldid=105329509 to reproduce.
+Steps:
+
+    1) Place the cursor immediatly after ""croisières"", before the non-breaking space.
+    2) Add a space. This space is added after the cursor.
+    3) Press Right Arrow then Left Arrow to make the cursor move, but it is finally at the same place.
+    4) Add a space : the pawn appears in the link.
+    5) Again right arrow, then add another space : a second pawn appears after the link.
+    6) If you try to type text after the last pawn, only a pawns appears. No text.
+
+    To have text written from right to left :
+    1) Place the cursor immediatly after ""croisières"", before the non-breaking space.
+    2) Add a space. This space is added after the cursor.
+    3) Press Right Arrow to make the cursor move.
+    4) Add a space : the pawn appears.
+    5) Again right arrow, then add another space (so efter the colon) : a second pawn appears.
+    6) Left arrow twice (cursor before the colon) and type text : it's written from right to left.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404992460,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-oxgjzrxg7p6u7stnpafd,task_description,resolved
+VisualEditor: Pawns and reverse typing,"
+
+*** This bug has been marked as a duplicate of bug 68151 ***",1406341653,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oxgjzrxg7p6u7stnpafd,task_subcomment,NA
+"VisualEditor:  Cite tool's dropdown menu is not displaying (it's ""underneath"" the toolbar)","Cite menu is inaccessible
+
+The dropdown menu for the Cite tool is not displaying correctly for me in Safari 6.1.4.  
+
+The screenshots show two different font sizes/resolutions.  This isn't consistent for me.  I zoomed in before it happened the first time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14279}",1404928980,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-y32jhfrfnhzhio3fteie,task_description,resolved
+"VisualEditor:  Cite tool's dropdown menu is not displaying (it's ""underneath"" the toolbar)","This sounds like bug 64388 which is very troubling. :-(
+
+*** This bug has been marked as a duplicate of bug 64388 ***",1404965618,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y32jhfrfnhzhio3fteie,task_subcomment,NA
+"VisualEditor:  Cite tool's dropdown menu is not displaying (it's ""underneath"" the toolbar)","Created attachment 15883
+What happens is you have zoomed in
+
+**Attached**: {F14282}",1404929051,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-y32jhfrfnhzhio3fteie,task_subcomment,NA
+VisualEditor: Support non-image media (tracking),"We currently don't. We should.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1404850380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aanmrkvizmwbalha5bbk,task_description,duplicate
+VisualEditor: Support non-image media (tracking),"
+
+*** This bug has been marked as a duplicate of bug 67690 ***",1404851265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aanmrkvizmwbalha5bbk,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","Steps to reproduce:
+
+1.Open a page with Mobile VE with desktop safari or iOS safari
+2.Create a link to a new page and save the page
+3.Go to that new page that you just created link to
+4.Edit that page and save it
+
+Observed Result:
+
+It will redirect you to the page that you started with at step1
+
+Environment:Betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60848
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65041
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69559",1404775860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_description,resolved
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page",Bug is no longer reproducible due to https://gerrit.wikimedia.org/r/#/c/164131/,1412632719,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page",I think this bug is actually the same as bug 60848 and bug 65041. Bug 60848 was closed by Jon as WONTFIX. Should we reopen it? Bug 65041 is just another specific case of the underlying issue.,1405984487,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","The issue here is that we're adding a hash to the URL when we launch the editor, and then doing history.back() after it's saved to restore the original URL. The only problem is that redlinks link directly to the editor, so once you're done, going back takes you to the previous article. Linking directly to the editor is the correct behavior (it's the same as is done on desktop). The problem is the  history.back() hack (IMO).",1405979859,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page",Reproducing this bug is currently blocked by bug 68249.,1405978411,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","Just checked with Rumana and it's actually an issue in beta mode too.
+So not necessarily related to ajax page loading/link hijacking :)",1404840427,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","OT: I notice you are testing VisualEditor in alpha since the bug is assigned to alpha. Please don't.... Please use beta which is more stable and will help us filter out bugs in VE vs bugs in mobile.
+
+Can you confirm the above problem happens in the alpha mode or is it beta mode (it does indeed sound like alpha)?",1404838690,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page",Sounds like another lazy-loading bug.,1404778093,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/wdlVRRim",1404777020,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+VisualEditor: A pawn appears while trying to type something to the the left/right of a reference note in Firefox,"Screenshot
+
+Steps to reproduce:
+
+1.Select a reference note in VE with firefox
+2.Press right/left
+3.Type something
+
+
+Observed Result:
+A pawn appears instead of the text
+
+
+See the screenshot attached
+
+Environment:Production (en.wiki)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14615}",1404763200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fz7qljplu3bbp45jxtbz,task_description,resolved
+VisualEditor: A pawn appears while trying to type something to the the left/right of a reference note in Firefox,"Boo.
+
+*** This bug has been marked as a duplicate of bug 58315 ***",1404763355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fz7qljplu3bbp45jxtbz,task_subcomment,NA
+VisualEditor: Clear styling does not work when the cursor is the middle of a text but de-selects the option from style menu,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make a text Bold
+3.Now place your cursor somewhere in the middle of that text
+4.Select the option ""Clear Styling"" from style menu
+
+
+Observed Result:
+The text is still styled as Bold, however the highlight on Bold option in style menu is not anymore there.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14613}",1404762480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-42zqimydtpfzutihf66c,task_description,declined
+VisualEditor: Clear styling does not work when the cursor is the middle of a text but de-selects the option from style menu,"This is intentional; ""clear styling"" without a selection applies to the pre-annotation stack.",1404762894,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-42zqimydtpfzutihf66c,task_subcomment,NA
+Allow users to disable VE in their preferences on otrswiki,"RD asked me to file this bug for him.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404687060,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-jmmp4zdhs654ea55j6sa,task_description,invalid
+Allow users to disable VE in their preferences on otrswiki,"Hmm, I guess ""Temporarily disable VisualEditor while it is in beta"" works. Missed that.",1404688768,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-jmmp4zdhs654ea55j6sa,task_subcomment,NA
+Allow users to disable VE in their preferences on otrswiki,"I am the RD to which Lego refers to. ;-)
+
+Rather than creating a css hack to hide the effects of VE, it should be an option somewhere in user preferences to ""disable"" VE.  The default can be set to having VE enabled.
+
+I am an OTRS administrator.  Some were originally under the impression that this was going to be the case but as of now there is no way to opt-out other than personal scripts.",1404687301,PHID-USER-vwkldpcvthnpctszjph7,PHID-TASK-jmmp4zdhs654ea55j6sa,task_subcomment,NA
+VisualEditor: Link annotation gets cut off when label contains linktrail end characters,"Screen recording of bug
+
+1. Edit page with a link is applied to multiple words in sequence.
+   such as ""QUnit - Foo bar baz"".
+2. Select part of it (e.g. ""Foo bar baz"")
+3. Type something new (e.g. ""Quux"")
+
+Expected:
+
+Quux replaces ""Foo bar baz"" and is a link as well.
+
+Actual:
+
+The text is removed, the link now ends at ""-"" and the inserted text ""Quux"" is just plain unlinked text.
+
+This might have to do with linktrail processing and the operation happening as separate delete/insert.
+
+
+Video: http://cl.ly/2K1q1A471G2N
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14240}",1404349800,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tdor3tpvb3ykeaupjgx6,task_description,declined
+VisualEditor: Link annotation gets cut off when label contains linktrail end characters,"(In reply to This, that and the other from comment #2)
+> (In reply to James Forrester from comment #1)
+> > This is intentional behaviour.
+> 
+> Doesn't it strike you as something a user may very legitimately and
+> intuitively want to accomplish?
+
+Yes. We spent months discussing this, looking at dozens of different rich editors' behaviours. That's why I'm reasonably confident that the answer is ""tough"".",1404356644,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tdor3tpvb3ykeaupjgx6,task_subcomment,NA
+VisualEditor: Link annotation gets cut off when label contains linktrail end characters,"(In reply to James Forrester from comment #1)
+> This is intentional behaviour.
+
+Doesn't it strike you as something a user may very legitimately and intuitively want to accomplish?",1404354735,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-tdor3tpvb3ykeaupjgx6,task_subcomment,NA
+VisualEditor: Link annotation gets cut off when label contains linktrail end characters,"You've failed to spot the key part of this – you have to select *to or past the end of the link*.
+
+Selections from inside a whitespace-terminated annotation to outside it which replace into it with a whitespace character will terminate it. Selections from inside said annotation to another place inside it (in your example, ""Foo bar ba"" but not ""Foo bar baz"") don't.
+
+This is intentional behaviour.",1404353692,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tdor3tpvb3ykeaupjgx6,task_subcomment,NA
+VisualEditor: Link inspector should indicate link target when applied via keyboard shortcut,"Screen recording of bug
+
+1. Select text
+2. cmd+K (Mac) to apply a link annotation
+
+Expected:
+
+Either it shows page titles with a default selection (e.g. a link to the exact link text), or only shows suggestions and require I pick one.
+
+Actual:
+
+Becomes link to the exact link text but with no way of knowing that, nor with an intuitive way to select a different target (see attached video).
+
+http://cl.ly/3P2P2E1a1w1A
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14235}",1404349500,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zmkykyh2tvcwalgnx52u,task_description,resolved
+VisualEditor: Link inspector should indicate link target when applied via keyboard shortcut,"The current link inspector solved this bug. To clarify, as seen in the video, the problem was that the selection menu did not open by default (required an additional needless click/focus). Leaving the user in a confused state.
+
+This has nothing to do with what the most common use case is. We still link to the target by default. But we now show the other options so that the user knows that it was actually turned into a link. Not just a pre-filled text box waiting for a user action. This made the most common use case more intuitive.",1433344252,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zmkykyh2tvcwalgnx52u,task_subcomment,NA
+VisualEditor: Link inspector should indicate link target when applied via keyboard shortcut,"No. We chose to not show this as the most common case is making an internal link to the term you've selected, and we wanted this to be as painless as possible.",1404353268,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zmkykyh2tvcwalgnx52u,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**Author:** `jazeckel`
+
+**Description:**
+wiki debug log for navigating to and attempting to edit a page
+
+I am attempting to configure the VisualEditor REL1_23 to run with my MediaWiki instance.  I am using MediaWiki 1.23 and it is a private wiki.  It's served by IIS on Windows Server 2012 R2.  I am able to create a very simple page using it, although it runs slowly.  However, any attempt to edit the page -- even a page containing only one simple sentence -- times out with Parsoid.  I ran all of the Parsoid tests following installation and they all passed, and from Parsoid's test webpage (localhost:8000) I was able to run those tests and they succeed quickly.  However, I can't edit any pages of my wiki.  This is the output from the Parsoid service during an edit attempt:
+
+[warning/api][null/Test] Failed API request, 8 retries remaining.
+[info][localhost/Test] starting parsing
+[info][localhost/Test?oldid=834] completed parsing in 45006 ms
+
+The completed parsing line occurs after I click cancel on the prompt telling me the request timed out.  When I had the timeout set to 60s, I would see ""8 tries remaining"" and then ""7 tries remaining"" before it timed out (I have since changed the timeout to 45s).  The content of the page in this example is simply ""this is a visual editor test.""
+
+Relevant information:
+- Windows Server 2012 R2
+- IIS v8.5.9600.16384
+- 32-bit node.js
+- Parsoid on port 8000
+- Browser used is Chrome 35.0.1916.153 m
+- MediaWiki 1.23, set to require log in to view/edit
+- same problem in all skins that VisualEditor runs on
+
+A debug log from MediaWiki is attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: other
+**Platform**: PC
+
+**Attached**: {F14490}",1404148260,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_description,resolved
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","(In reply to C. Scott Ananian from comment #16)
+> gwicke: we should probably not be timing out if the api request returns an
+> error.  Maybe we should look into this?
+
+My understanding of the code is that we only retry when getting an error object, but not if we got an HTTP status code. There's either no proper HTTP status returned by this particular wiki setup, or the request library returns an error when it should not. 
+
+I just tested this locally, and there's no retrying on unauthorized requests. This means that this is probably an IIS-specific issue, where IIS does not return a proper HTTP status on authentication errors.",1404344823,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Okay, I finally have it working.  I think this boils down to configuration errors so the instructions for setup for Parsoid and the VisualEditor should probably be clarified, but also it would be nice to improve the error messaging so that a permissions error doesn't cause a timeout.
+
+Here's what I did to fix it:
+- made the key in parsoidConfig.setInterwiki equal to $wgVisualEditorParsoidPrefix, both of which I set to ""auc"" (rather than ""localhost/auc"")
+- set $wgSessionsInObjectCache = true (this is the line that didn't seem to have any effect before, but that was probably because the rest was not configured right)
+- set $wgVisualEditorParsoidForwardCookies = true (I already had that one set)
+
+Thanks for your help!",1404321623,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+FWIW if I go to http://localhost:8000/auc/Main_Page from a browser where my login credentials are cached, the content will load.  If I'm logged out of the wiki in that browser, I will get an error.",1404242245,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+(In reply to C. Scott Ananian from comment #16)
+> I'm guessing that one of these is prohibiting anonymous access to the API. 
+> I bet it's not actually the case that it works when you use the server name,
+> I bet that somehow you're actually accessing the wrong wiki in that case. 
+> I'm not a mediawiki permissions expert though, so take what I say with a
+> grain of salt.
+
+Yes, this is exactly what happens -- it loads the content from the wrong wiki.
+
+> If you are mucking with permissions, this link may be useful:
+> https://www.mediawiki.org/wiki/Extension:
+> VisualEditor#Linking_with_Parsoid_in_private_wikis
+
+I had already set $wgVisualEditorParsoidForwardCookies = true as instructed in that portion.  I didn't uncomment the line about session cacheing because it didn't seem to make a difference.
+
+> Yes, the 'localhost' part here has to match the string you set 
+> $wgVisualEditorParsoidPrefix to.
+
+Okay, thanks for letting me know that.  It wasn't clear from the installation/configuration instructions.
+
+(In reply to C. Scott Ananian from comment #18)
+> In particular, one running parsoid can service multiple different
+> mediawikis.  They are distinguished by the $wgVisualEditorParsoidPrefix and
+> corresponding localsettings.js.  For example, you should be able to visit
+> your running parsoid instance on http://localhost:8080 (or whatever port you
+> used) and then get different pages for:
+> 
+> http://localhost:8080/enwiki/Main_Page (links to wikipedia using 'enwiki'
+> prefix)
+> http://localhost:8080/localhost/Main_Page
+> http://localhost:8080/foo/Main_Page
+> 
+> given
+> 
+> parsoidConfig.setInterwiki( 'localhost', 'some api endpoint' );
+> parsoidConfig.setInterwiki( 'foo', 'some different api endpoint' );
+> 
+> Our docs could probably explain this better.  Suggestions welcome.
+
+Thanks, that explains some more.  I have set them both to ""auc"" and now it's not loading data from the wrong wiki anymore, but it's timing out again.  Perhaps there is some other detail of configuration for a private wiki that is causing a problem.  Can I go into Parsoid's code and hard code a username and password and make a private account just for Parsoid to resolve this?",1404242055,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","In particular, one running parsoid can service multiple different mediawikis.  They are distinguished by the $wgVisualEditorParsoidPrefix and corresponding localsettings.js.  For example, you should be able to visit your running parsoid instance on http://localhost:8080 (or whatever port you used) and then get different pages for:
+
+http://localhost:8080/enwiki/Main_Page (links to wikipedia using 'enwiki' prefix)
+http://localhost:8080/localhost/Main_Page
+http://localhost:8080/foo/Main_Page
+
+given
+
+parsoidConfig.setInterwiki( 'localhost', 'some api endpoint' );
+parsoidConfig.setInterwiki( 'foo', 'some different api endpoint' );
+
+Our docs could probably explain this better.  Suggestions welcome.",1404241663,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","(In reply to jazeckel from comment #15)
+> Also, if I comment out the entire parsoidConfig.setInterwiki line in my
+> localsettings.js, it loads the visual editor but with the wrong wiki's
+> content.  It appears that having ""localhost"" as the key on that line will
+> cause it to fail regardless, and if I change ""localhost"" to anything else it
+> loads the wrong content.  For example, I could make the line:
+> parsoidConfig.setInterwiki( 'foo', 'http://localhost/auc/wiki/api.php' );
+> 
+> and it will load the editor but with the wrong content.
+
+Yes, the 'localhost' part here has to match the string you set $wgVisualEditorParsoidPrefix to.",1404241409,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","(In reply to jazeckel from comment #11)
+> Hmm, so this is kind of interesting.  If I go to the URL but with the server
+> name instead of ""localhost,"" I get what I assume is the correct result -- a
+> big block of key value pairs about locales and such.  If I go to the URL
+> with ""localhost"", I get this: 
+> 
+> {""error"":{""code"":""readapidenied"",""info"":""You need read permission to use
+> this module""}}
+> 
+> I don't see any PHP error logs created though perhaps I am not looking in
+> the right place.
+
+This is generated if the anonymous user doesn't have appropriate permissions to access the API.  In include/DefaultSettings.php there is a group of permissions including:
+
+$wgGroupPermissions['*']['writeapi'] = true;
+
+I'm guessing that one of these is prohibiting anonymous access to the API.  I bet it's not actually the case that it works when you use the server name, I bet that somehow you're actually accessing the wrong wiki in that case.  I'm not a mediawiki permissions expert though, so take what I say with a grain of salt.
+
+If you are mucking with permissions, this link may be useful:
+https://www.mediawiki.org/wiki/Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis
+
+gwicke: we should probably not be timing out if the api request returns an error.  Maybe we should look into this?",1404241346,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Also, if I comment out the entire parsoidConfig.setInterwiki line in my localsettings.js, it loads the visual editor but with the wrong wiki's content.  It appears that having ""localhost"" as the key on that line will cause it to fail regardless, and if I change ""localhost"" to anything else it loads the wrong content.  For example, I could make the line:
+parsoidConfig.setInterwiki( 'foo', 'http://localhost/auc/wiki/api.php' );
+
+and it will load the editor but with the wrong content.",1404241027,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+To clarify, when it succeeds and loads the page from the wrong wiki, the URL I see in the debug output is ""http://localhost/wiki/api.php"" whereas the correct wiki is ""http://localhost/auc/wiki/api.php"", which is as specified in Parsoid's localsettings (although in localsettings it is specified now with servername instead of localhost).",1404240426,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+This is extremely confusing.  Here are the current issues:
+1) I don't understand why changing out localhost for servername should make a difference, considering they are the same machine.
+2) If I change out localhost for servername in parsoid/api/localsettings.js, then when I try to edit the visual editor loads, but it loads with the content of a page from a different wiki that runs on the same server.  Is there a missing database configuration in the Parsoid localsettings?
+3) If I change the wiki/localsettings.js to also use servername instead of localhost, it times out again.",1404240259,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time",It sounds like your configured API URL should actually include the real server name instead of 'localhost'. Could you change the config & verify that this fixes your issue?,1404237866,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Hmm, so this is kind of interesting.  If I go to the URL but with the server name instead of ""localhost,"" I get what I assume is the correct result -- a big block of key value pairs about locales and such.  If I go to the URL with ""localhost"", I get this: 
+
+{""error"":{""code"":""readapidenied"",""info"":""You need read permission to use this module""}}
+
+I don't see any PHP error logs created though perhaps I am not looking in the right place.",1404222602,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","@jazeckel: so, when you visit http://localhost/auc/wiki/api.php?format=json&action=query&meta=siteinfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensiontags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols manually, what happens?  Does anything show up in your PHP server logs?
+
+It sounds like there's something wrong with your wiki's API entrypoint.",1404221407,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Okay, I applied the patch, ran ""node api/server.js"" in the console, then loaded up my test page and clicked edit for the visual editor.  Some time passed with no output, then I got this:
+
+Request 1: http://localhost/auc/wiki/api.php?format=json&action=query&meta=sitei
+nfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensio
+ntags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols: 40016ms
+
+TypeError: Cannot read property 'statusCode' of undefined
+    at Request.cb [as _callback] (D:\public\jazeckel\parsoid\lib\mediawiki.ApiRe
+quest.js:99:49)
+    at self.callback (D:\public\jazeckel\parsoid\node_modules\request\request.js
+:121:22)
+    at Request.emit (events.js:95:17)
+    at null._onTimeout (D:\public\jazeckel\parsoid\node_modules\request\request.
+js:679:12)
+    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
+worker 3128 died (8), restarting.
+ - worker(3040) loading...
+ - worker(3040) ready on :8000
+
+After that I hit my 45 second timeout.",1404217137,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time",It might be easiest just to open lib/mediawiki.ApiRequest.js and apply the patch manually in your favorite editor.  It's only nine lines to copy-and-paste.  The lines with '+' at the front are additions.  The single line with '-' is a removal.,1404160847,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Can you point me to instructions on how to apply the patch?  I won't be able to do it until tomorrow morning.  Thanks!",1404160479,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","Created attachment 15795
+Debugging patch to dump timing and status code of API requests
+
+Well, we don't have anything built in, but the attached patch is a hack which will dump the request timing and status codes.  If you apply this and then visit (say) http://localhost:8765/enwiki/Main_Page you should get a bunch of output on console about all the upstream API requests which Parsoid is making.  I suspect one or more of them is timing out.
+
+**Attached**: {F14491}",1404158191,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","Ok, I think we can rule out platform slowness.  So now I think my theory in comment 3 is probably on the right track.  Subbu, gwicke: do we have any tools to diagnose timeout issues in API requests made by Parsoid?",1404157376,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+1) node --version reports v0.10.29
+2) running tests/parserTests.js --quiet took 30 seconds, and reported no unexpected results.
+3) it is not a virtual server.  It has 8GB RAM, and here's all the info about the CPU.  Not sure if CPU cache is the cache you wanted to know about or a different cache. 
+
+Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
+Intel64 Family 6 Model 45 Stepping 7, GenuineIntel
+HTT             *       Hyperthreading enabled
+HYPERVISOR      -       Hypervisor is present
+VMX             *       Supports Intel hardware-assisted virtualization
+SVM             -       Supports AMD hardware-assisted virtualization
+EM64T           *       Supports 64-bit mode
+
+SMX             *       Supports Intel trusted execution
+SKINIT          -       Supports AMD SKINIT
+
+NX              *       Supports no-execute page protection
+SMEP            -       Supports Supervisor Mode Execution Prevention
+SMAP            -       Supports Supervisor Mode Access Prevention
+PAGE1GB         *       Supports 1 GB large pages
+PAE             *       Supports > 32-bit physical addresses
+PAT             *       Supports Page Attribute Table
+PSE             *       Supports 4 MB pages
+PSE36           *       Supports > 32-bit address 4 MB pages
+PGE             *       Supports global bit in page tables
+SS              *       Supports bus snooping for cache operations
+VME             *       Supports Virtual-8086 mode
+RDWRFSGSBASE    -       Supports direct GS/FS base access
+
+FPU             *       Implements i387 floating point instructions
+MMX             *       Supports MMX instruction set
+MMXEXT          -       Implements AMD MMX extensions
+3DNOW           -       Supports 3DNow! instructions
+3DNOWEXT        -       Supports 3DNow! extension instructions
+SSE             *       Supports Streaming SIMD Extensions
+SSE2            *       Supports Streaming SIMD Extensions 2
+SSE3            *       Supports Streaming SIMD Extensions 3
+SSSE3           *       Supports Supplemental SIMD Extensions 3
+SSE4a           -       Supports Sreaming SIMDR Extensions 4a
+SSE4.1          *       Supports Streaming SIMD Extensions 4.1
+SSE4.2          *       Supports Streaming SIMD Extensions 4.2
+
+AES             *       Supports AES extensions
+AVX             *       Supports AVX intruction extensions
+FMA             -       Supports FMA extensions using YMM state
+MSR             *       Implements RDMSR/WRMSR instructions
+MTRR            *       Supports Memory Type Range Registers
+XSAVE           *       Supports XSAVE/XRSTOR instructions
+OSXSAVE         *       Supports XSETBV/XGETBV instructions
+RDRAND          -       Supports RDRAND instruction
+RDSEED          -       Supports RDSEED instruction
+
+CMOV            *       Supports CMOVcc instruction
+CLFSH           *       Supports CLFLUSH instruction
+CX8             *       Supports compare and exchange 8-byte instructions
+CX16            *       Supports CMPXCHG16B instruction
+BMI1            -       Supports bit manipulation extensions 1
+BMI2            -       Supports bit manipulation extensions 2
+ADX             -       Supports ADCX/ADOX instructions
+DCA             *       Supports prefetch from memory-mapped device
+F16C            -       Supports half-precision instruction
+FXSR            *       Supports FXSAVE/FXSTOR instructions
+FFXSR           -       Supports optimized FXSAVE/FSRSTOR instruction
+MONITOR         *       Supports MONITOR and MWAIT instructions
+MOVBE           -       Supports MOVBE instruction
+ERMSB           -       Supports Enhanced REP MOVSB/STOSB
+PCLULDQ         *       Supports PCLMULDQ instruction
+POPCNT          *       Supports POPCNT instruction
+LZCNT           -       Supports LZCNT instruction
+SEP             *       Supports fast system call instructions
+LAHF-SAHF       *       Supports LAHF/SAHF instructions in 64-bit mode
+HLE             -       Supports Hardware Lock Elision instructions
+RTM             -       Supports Restricted Transactional Memory instructions
+
+DE              *       Supports I/O breakpoints including CR4.DE
+DTES64          *       Can write history of 64-bit branch addresses
+DS              *       Implements memory-resident debug buffer
+DS-CPL          *       Supports Debug Store feature with CPL
+PCID            *       Supports PCIDs and settable CR4.PCIDE
+INVPCID         -       Supports INVPCID instruction
+PDCM            *       Supports Performance Capabilities MSR
+RDTSCP          *       Supports RDTSCP instruction
+TSC             *       Supports RDTSC instruction
+TSC-DEADLINE    *       Local APIC supports one-shot deadline timer
+TSC-INVARIANT   *       TSC runs at constant rate
+xTPR            *       Supports disabling task priority messages
+
+EIST            *       Supports Enhanced Intel Speedstep
+ACPI            *       Implements MSR for power management
+TM              *       Implements thermal monitor circuitry
+TM2             *       Implements Thermal Monitor 2 control
+APIC            *       Implements software-accessible local APIC
+x2APIC          *       Supports x2APIC
+
+CNXT-ID         -       L1 data cache mode adaptive or BIOS
+
+MCE             *       Supports Machine Check, INT18 and CR4.MCE
+MCA             *       Implements Machine Check Architecture
+PBE             *       Supports use of FERR#/PBE# pin
+
+PSN             -       Implements 96-bit processor serial number
+
+PREFETCHW       *       Supports PREFETCHW instruction
+
+Maximum implemented CPUID leaves: 0000000D (Basic), 80000008 (Extended).
+
+Logical to Physical Processor Map:
+*---  Physical Processor 0
+-*--  Physical Processor 1
+--*-  Physical Processor 2
+---*  Physical Processor 3
+
+Logical Processor to Socket Map:
+****  Socket 0
+
+Logical Processor to NUMA Node Map:
+****  NUMA Node 0
+
+Logical Processor to Cache Map:
+*---  Data Cache          0, Level 1,   32 KB, Assoc   8, LineSize  64
+*---  Instruction Cache   0, Level 1,   32 KB, Assoc   8, LineSize  64
+*---  Unified Cache       0, Level 2,  256 KB, Assoc   8, LineSize  64
+****  Unified Cache       1, Level 3,   10 MB, Assoc  20, LineSize  64
+-*--  Data Cache          1, Level 1,   32 KB, Assoc   8, LineSize  64
+-*--  Instruction Cache   1, Level 1,   32 KB, Assoc   8, LineSize  64
+-*--  Unified Cache       2, Level 2,  256 KB, Assoc   8, LineSize  64
+--*-  Data Cache          2, Level 1,   32 KB, Assoc   8, LineSize  64
+--*-  Instruction Cache   2, Level 1,   32 KB, Assoc   8, LineSize  64
+--*-  Unified Cache       3, Level 2,  256 KB, Assoc   8, LineSize  64
+---*  Data Cache          3, Level 1,   32 KB, Assoc   8, LineSize  64
+---*  Instruction Cache   3, Level 1,   32 KB, Assoc   8, LineSize  64
+---*  Unified Cache       4, Level 2,  256 KB, Assoc   8, LineSize  64
+
+Logical Processor to Group Map:
+****  Group 0",1404157149,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","(Oh, and as a first guess at a diagnosis: it seems suspiciously like one or more of the 30-second timeouts are expiring internal to Parsoid -- parsoid uses internal requests to the api.php of the containing wiki; if those are timing out it is likely that parsoid will take a long time to reply.  But let's double-check the speed of parserTests and underlying node to be sure.)",1404155565,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","As a first step, it would be useful to have some more information on your node.js setup, since we don't habitually test Parsoid on Windows.  Let's start with the output of 'node --version', some hardware information on the server in question (is it a virtual server?  If not, what is the CPU and clock speed and cache size), and how long 'tests/parserTests.js --quiet' takes to run.  With that we should at least narrow down the problem to node performance in general, or some quirk peculiar to how parsoid and mediawiki are interconnected.",1404155449,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","This is pretty unhelpful, yes. 45 seconds is an insanely long time to parse the page - [[en:Barack Obama]] takes less than 12 seconds to parse, so it sounds like something is wrong there.
+
+Punting to the Parsoid team to ask for advice (and they'll probably need some more information to work out why Parsoid is so slow for you).
+
+If this server is going to be used by a number of people, I'd recommend putting a caching layer in front of Parsoid and using the Parsoid PHP extension to push changes to pages into the cache so they're available instantly.",1404154589,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+Core message reuse,"VisualEditor correctly introduces visualeditor-ca-editsource, visualeditor-ca-editsource-section to change meaning of action=edit links, but it seems to reuse messages such as editsection, monobook-view-edit, vector-view-edit for its own veaction=edit links.
+https://www.mediawiki.org/wiki/Localisation#Avoid_message_reuse
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404045240,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-m24wzue25r3tbqzzunue,task_description,declined
+Core message reuse,"Change 147737 abandoned by Jforrester:
+Don't steal core's 'edit', 'create', 'editsection' by default
+
+Reason:
+Per discussion.
+
+https://gerrit.wikimedia.org/r/147737",1408990765,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"(In reply to Robin Pepermans (SPQRobin) from comment #4)
+> having yet another message and consequently having only
+> few translations.
+
+No such risk in my proposal.",1405779038,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"Change 147737 had a related patch set uploaded by Nemo bis:
+Don't steal core's 'edit', 'create', 'editsection' by default
+
+https://gerrit.wikimedia.org/r/147737",1405778351,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"(In reply to Nemo from comment #3)
+> How is linking veaction=edit not a different context than action=edit?
+
+They are on the same location and for the same function (i.e. editing). There is only a slight difference, i.e. in core it uses the normal editor while in VisualEditor obviously the visual editor. In my opinion, this does not weigh against having yet another message and consequently having only few translations. 
+
+Which makes me think, maybe we should have the ability to fall back to another message if a certain (identical but more specific) message is not translated.",1404152021,PHID-USER-th6xijvyee7wqsk7bc67,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"(In reply to Robin Pepermans (SPQRobin) from comment #2)
+> Message re-use
+> needs to be avoided when re-using them in a different context.
+
+How is linking veaction=edit not a different context than action=edit?",1404145793,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"I don't see why we would need separate messages for these. As far as I can see, they are used on the same location for the same function, so having separate messages would be unnecessary duplication imho. Message re-use needs to be avoided when re-using them in a different context.",1404145194,PHID-USER-th6xijvyee7wqsk7bc67,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"monobook-view-create and vector-view-create are also reused.
+
+As written in VisualEditor.php, we can avoid message reuse by adding the following code:
+ $wgVisualEditorTabMessages['edit'] = 'visualeditor-ca-ve-edit';
+ $wgVisualEditorTabMessages['create'] = 'visualeditor-ca-ve-create';
+ $wgVisualEditorTabMessages['editsection'] = 'visualeditor-ca-ve-edit-section';
+
+But visualeditor-ca-ve-edit, visualeditor-ca-ve-create, and visualeditor-ca-ve-edit-section are all ""VisualEditor"".",1404053114,PHID-USER-mchhpeuixutvfg7eceob,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+CirrusSearch: suggesting categories which do not exist and never did,"On it.wp, trying to add a category in VisualEditor.
+If you start typing ""Terminologia dello"", you'll be prompted to add 3 categories.
+One of them though, ""Terminologia dello sport"", doesn't exist and never did.
+(Also, no articles or templates with that name).
+
+I'm told this link could be useful:
+https://it.wikipedia.org/w/api.php?format=json&uselang=en-gb&action=query&list=allcategories&acprefix=Terminologia+dello+sport&acprop=hidden&redirects=
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404023280,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ucqemxjwxsynri4inhdj,task_description,duplicate
+CirrusSearch: suggesting categories which do not exist and never did,This is likely the same issue as {T115756}.,1478127973,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-ucqemxjwxsynri4inhdj,task_subcomment,NA
+CirrusSearch: suggesting categories which do not exist and never did,"I think you'd have to validate the ""doesn't exist and never did"" claim.  Categories are ""created"" as soon as the name of one is saved in any page.  If a redlink to that category ever existed, then the category itself was created (but not the separate description page for the category, which is what you need to turn an existing category into a bluelink).",1431561842,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ucqemxjwxsynri4inhdj,task_subcomment,NA
+CirrusSearch: suggesting categories which do not exist and never did,"I think you'd have to validate the ""doesn't exist and never did"" claim.  Categories are ""created"" as soon as the name of one is saved in any page.  If a redlink to that category ever existed, then the category itself was created (but not the separate description page for the category, which is what you need to turn an existing category into a bulling).",1431561828,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ucqemxjwxsynri4inhdj,task_subcomment,NA
+Make new multi-part transclusions always put newlines between each transclusion (default whitespace of \n),"Some tables built from complex templates assume that there will be line breaks between the templates, so that this works:
+
+{{tabletop}}
+{{tablerow}}
+{{tablerow}}
+{{tablerow}}
+{{tableend}}
+
+but this does not:
+
+{{tabletop}}{{tablerow}}{{tablerow}}{{tablerow}}{{tableend}}
+
+
+There's another problem with transclusions containing content, which can be seen by opening the transclusion at https://en.wikipedia.org/wiki/Kilt#See_also in VisualEditor.  The template lines are fine, but the ""Content"" sections must always start with a blank line, to make up for the absence of line breaks at the end of the templates.  
+
+The solution for both of these is probably the same:  Complex transclusions should always have line breaks after the templates.  I haven't been able to find any (in my quick search) that would break if this were implemented.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1404015660,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-dpxhyjkbi3yny76mtezq,task_description,resolved
+Make new multi-part transclusions always put newlines between each transclusion (default whitespace of \n),"Pretty sure this is a dupe?
+
+*** This bug has been marked as a duplicate of bug 50166 ***",1405409435,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-dpxhyjkbi3yny76mtezq,task_subcomment,NA
+Make new multi-part transclusions always put newlines between each transclusion (default whitespace of \n),"I'm not entirely certain that there aren't multi-part templates that this is the wrong call for, but in general this is certainly a sensible tactic.",1404157701,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dpxhyjkbi3yny76mtezq,task_subcomment,NA
+VisualEditor crashes if the DefaultSummaries gadget is enabled,"VisualEditor crashes when you try to save if the Defaultsummaries gadget is enabled. (https://en.wikipedia.org/wiki/MediaWiki:Gadget-defaultsummaries.js )  This is new; it used to work.
+
+Workaround:  Disable the gadget.
+
+(Might be Firefox-specific.  I haven't tested it.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403930460,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-pqxet5vnqn3mirgkweo6,task_description,invalid
+VisualEditor crashes if the DefaultSummaries gadget is enabled,"Not really a VE bug, but here you go:
+
+The gadget is using ve.init.mw.targets[0] to access the target, which isn't supposed to be a public API yet, but hey. This was removed recently and is now accessible via ve.init.mw.target.",1403970054,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pqxet5vnqn3mirgkweo6,task_subcomment,NA
+VisualEditor: deleting the text from the article and converting it to a redirect page still leaves in categories and Other Stuff,"Deleting the text from the article and converting it to a redirect page still leaves all the categories in it, as well as Other Stuff such as magic words and invisible templates.
+
+This is a regression in comparison to the source editor, where the editor could just delete everything and be sure that categories, magic words, invisible templates and everything else is gone.
+
+Just redirecting an article shouldn't necessarily remove everything, because it's actually possible that the editor wants to leave the article in a category. Some projects, including enwiki, have categories, templates etc. in redirect pages. But probably some kind of a warning should be shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403884980,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-mpoga25glxtbttk73ydj,task_description,resolved
+VisualEditor: deleting the text from the article and converting it to a redirect page still leaves in categories and Other Stuff,"
+
+*** This bug has been marked as a duplicate of bug 61858 ***",1403885598,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mpoga25glxtbttk73ydj,task_subcomment,NA
+Error saving settings: ... have cookies enabled,"Clicking Save looks OK
+
+After logging in, attempt to set beta settings. 
+
+After clicking Save, get message ""Error saving settings. Please make sure that you have cookies enabled""
+
+This causes test failures such as https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/36/testReport/(root)/VisualEditor/Going_back_from_save_screen_in_VisualEditor/
+
+This is probably a problem in core, and very likely related to the VE bug https://bugzilla.wikimedia.org/show_bug.cgi?id=65709
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65709
+
+**Attached**: {F14190}",1403825280,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-gekbe2bs7wupt3isplty,task_description,resolved
+Error saving settings: ... have cookies enabled,"Change 143799 merged by jenkins-bot:
+Revert ""Give anons tokens too""
+
+https://gerrit.wikimedia.org/r/143799",1404839875,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gekbe2bs7wupt3isplty,task_subcomment,NA
+Error saving settings: ... have cookies enabled,"Change 143799 had a related patch set uploaded by Jdlrobson:
+Revert ""Give anons tokens too""
+
+https://gerrit.wikimedia.org/r/143799",1404839773,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gekbe2bs7wupt3isplty,task_subcomment,NA
+Error saving settings: ... have cookies enabled,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/jtxt8rEw",1403825421,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gekbe2bs7wupt3isplty,task_subcomment,NA
+Error saving settings: ... have cookies enabled,"Created attachment 15756
+Error after clicking Save
+
+**Attached**: {F14191}",1403825307,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-gekbe2bs7wupt3isplty,task_subcomment,NA
+VisualEditor:  Tab order is bad in the Template dialog,"This is the same sort of problem as bug 67153 in the Save dialog.  
+
+
+Here is the incomplete tab order in Safari 6:
+
+1.  Insert > Template
+
+2.  The cursor starts in the template name field.  (It doesn't matter if you type something now.)  Tab:
+
+a) ""Add template"" button
+b)  Nothing—cursor disappears
+c) ""Apply changes"" button 
+d) ""Show options"" (visually backwards, but maybe that's okay)
+e)  Escape the template dialog into the mess described in the Safari-specific bug 67156.
+
+Not accessible:  The X-to-cancel button at the top of the dialog.
+
+
+
+Here is the even more incomplete tab order in Firefox 30:
+
+1.  Insert > Template
+
+2.  The cursor starts in the template name field.  (It doesn't matter if you type something now.)  Tab:
+
+a) the browser's URL bar
+b) the browser's search box (for search engines)
+c) who knows?  It disappears.
+d) the main Wikipedia search box 
+e) the top of the article
+f) the MediaWiki ""More"" menu (where ""Move"" hides)
+g) the icon/go button for the main Wikipedia search box
+h) the languages (gear icon) button
+i) the New template dialog (as a whole, not any useful piece of it)
+j) who knows?  It disappears again.
+k) the New template dialog (as a whole, not any useful piece of it)
+l) who knows?  It disappears again.
+m) back to the field for the template name, repeating endlessly.
+
+Where it doesn't go is:
+
+n) the Add template button
+o) the Show options button
+p) to the X at the top of the dialog box, so you can cancel adding a template and go back to editing. 
+
+
+IMO the order in all cases ought to be:
+
+a)  Start in the template name field
+b) ""Add template"" button
+c) ""Apply changes"" button 
+d) ""Show options""
+e)  X to cancel the dialog and go back to editing
+
+and nothing else (repeat endlessly, if the person keeps pressing tab).
+
+I'm willing to have C and D reversed, because it would be visually more obvious (for left-to-right languages).  However, most users won't be clicking that button, so it'd be more efficient to have it later in the tab order.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67153",1403809500,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-mpvfengewtqthcpazlj5,task_description,resolved
+VisualEditor:  Tab order is bad in the Template dialog,"@James Forrester, the tab index isn't good yet.
+
+Suppose I want to add a template with 4 parameters.
+1. Press on a textbox of the first parameter
+2. Press tab. This should move to the next parameter, but instead moves to button of info, and the next tab moves to button of delete. info and delete are less common than moving to next textbox.
+
+so instead of fill, TAB, fill, TAB... you should do fill, 3 x TAB etc",1408386229,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-mpvfengewtqthcpazlj5,task_subcomment,NA
+VisualEditor:  Tab order is bad in the Template dialog,"I'm pretty sure this was done as part of bug 66824.
+
+*** This bug has been marked as a duplicate of bug 66824 ***",1404849994,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mpvfengewtqthcpazlj5,task_subcomment,NA
+VisualEditor:  Tab order or behavior is bad in the Save dialog,"Steps to reproduce:
+
+1.  Open a page and make a change.  
+
+2.  Click the Save button.
+
+3.  Tab.  The cursor starts in the edit summary box (good) and goes to (using en.wp/Vector):
+
+a) tick box for minor edit
+b) link to the minor edit help page**
+c) tick box for watching the page
+d) three links in the licensing statement**
+e) Review your changes button
+f) Save button (inside the dialog box)
+g) the browser's URL bar
+h) the main Wikipedia search box 
+g) the Cancel button (on VisualEditor's toolbar, and it works if you press return now)
+h) the Save button (on VisualEditor's toolbar)
+i) the top of the article
+j) the slug at the top of the article, where it gets stuck forever.
+
+Where it doesn't go is:
+
+k) to the X at the top of the dialog box, so you can cancel saving and go back to editing. 
+
+
+** I'd like these links to be skipped, but (a) maybe this is controlled by a browser setting and (b) maybe my opinion is in the minority.  I'd like these to be skipped so that I can save a page without having to press tab eight times between the edit summary and the final save button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67159",1403806620,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-2pzeuibn247qiu4bfkvi,task_description,resolved
+VisualEditor:  Tab order or behavior is bad in the Save dialog,"I think this is a dupe of bug 65554, which is now fixed.
+
+*** This bug has been marked as a duplicate of bug 65554 ***",1404848147,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2pzeuibn247qiu4bfkvi,task_subcomment,NA
+VisualEditor:  Tab order or behavior is bad in the Save dialog,"Here's the tab order in Firefox 30, starting from the edit summary box in the Save dialog:
+
+a) tick box for minor edit
+b) tick box for watching the page
+c) the browser's URL bar
+d) the browser's search box (for search engines)
+e) who knows?  It disappears.
+f) the main Wikipedia search box 
+g) the top of the article
+h) the MediaWiki ""More"" menu (where ""Move"" hides)
+i) the icon/go button for the main Wikipedia search box
+j) the languages (gear icon) button
+k) the Save dialog (as a whole, not any useful piece of it)
+l) who knows?  It disappears again.
+m) back to the edit summary box, repeating endlessly.
+
+Where it doesn't go is:
+
+n) the Save button in the Save dialog,
+o) the Review your changes button in the Save dialog, or
+p) to the X at the top of the dialog box, so you can cancel saving and go back to editing. 
+
+
+IMO the order ought to be, in its entirety, for all browsers:
+
+a) tick box for minor edit
+b) tick box for watching the page
+c) the Review your changes button
+d) the Save button
+e) the X at the top of the dialog box
+f) back to the edit summary—and repeat in a loop.",1403807315,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-2pzeuibn247qiu4bfkvi,task_subcomment,NA
+VisualEditor:  Tab order or behavior is bad in the Save dialog,The above is the tab order in Safari 6.1.4 on Mac OS 10.8.5.,1403806770,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-2pzeuibn247qiu4bfkvi,task_subcomment,NA
+VisualEditor:  In which it is apparently impossible to create a redirect to [[Foo]] because the list of possible links does not scroll,"Steps to reproduce:
+
+1.  Go to Page settings to create a redirect on the English Wikipedia.
+
+2.  Type ""foo"" (an actual article—well, a redirect to an actual article about metasyntactic variables) in the field.
+
+3.  Look at the search results, which are all about football (plus one for [[Foot (length)]] and one for the US FDA).  Think, ""I must need to scroll down past all of this sports stuff""... but it doesn't scroll.
+
+
+If you click on any of these items, then your correct link to ""Foo"" gets replaced by whatever was highlighted.  
+
+It turns out that you can actually get the link to ""Foo"", by clicking on any place outside the dialog box (to make the search results go away) and then clicking on ""Apply changes"", but this is really Not Good.  To make things worse, due to bug 61861, you can't see what actually happened without either going to Review your changes or saving the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403805780,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-nuccdntq5xq6sbg2nsxr,task_description,resolved
+VisualEditor:  In which it is apparently impossible to create a redirect to [[Foo]] because the list of possible links does not scroll,"Yeah, this is bug 54361.
+
+*** This bug has been marked as a duplicate of bug 54361 ***",1406753647,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nuccdntq5xq6sbg2nsxr,task_subcomment,NA
+VisualEditor:  In which it is apparently impossible to create a redirect to [[Foo]] because the list of possible links does not scroll,"Clarification: the list of links does scroll, it's just that there's only 10(?) of them and Foo isn't among them, even though it exists. This is because MWTitleInputWidget, unlike MWLinkTargetInputWidget, does not reserve a special space for the title you typed. Instead, we assume that searching for pages whose names start with ""Foo"" will always return ""Foo"" as the first result, but that doesn't happen in practice because of a bug in the search system (I've also noticed these results being out of alphabetical order).
+
+There's a bug... somewhere where we track things that go wrong because opensearch is unhelpful.",1406577020,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nuccdntq5xq6sbg2nsxr,task_subcomment,NA
+VisualEditor: Section edit link is not appearing in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Load any page with sections in Betalabs
+
+Observed Result:
+There is no link for editing any section
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14604}",1403732280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ort3kaznvsgusca4dojy,task_description,invalid
+VisualEditor: Section edit link is not appearing in Betalabs,"Ignore this bug, this is for adding a tempalte Country Showdata in the page.",1403735184,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ort3kaznvsgusca4dojy,task_subcomment,NA
+VisualEditor: Section edit link is not appearing in Betalabs,I can't reproduce in any of four browsers tested. :-(,1403734880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ort3kaznvsgusca4dojy,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"We have an imho fundamentally broken model for inserting links. I don't know why we show the Link tool in the toolbar when there is no selected text because it's pretty much impossible.
+
+The tool is optimised for adding a link to existing text (or typing the label out first, which is unnatural for anyone who hasn't acquired it as a habit due to this bug), and for changing the link target.
+
+A few use cases:
+* Add link in list
+  - Add item item (press return after the last item or create new list)
+  - User has a page or url he wants to link to
+  - Press ""Link"" tool
+  - Type target page name or url
+  - User wants to insert link with that label, or (more likely in case of an external link) have the label be something that is not the link target.
+
+* Add link while typing text
+* Update mistake in text (e.g. text mentioning ""born in the US"" or ""born in 1955"" and the link and label of US/1955 should be another country or year).
+
+I think the frequency at which one needs to only update the link label or link target are significantly lower, but the other cases are certainly not edge cases.
+
+Here's a recording of me painfully trying to insert a link:
+http://cl.ly/3s460Q442L3S
+
+To this day I have not once been able to insert a link without running into a bug that would've discouraged me as a user.
+
+I thought I filed these as separate bugs at some point but I can't find them. Issues encountered in the video:
+
+1) Inserting a plain external link and then typing its label causes an exception (a pawn appears; see video).
+
+2) The link inspector seems to lack an intuitive way to apply the change. During the video you can see me at various points being confused and eventually pressing ""Back"" (or pressing Enter) to apply the change. Especially when inserting a new link or changing an internal link to an external link (albeit by accident) it's counter-intuitive to not see anything in the page or to continue seeing a red link when I've already selected the value from the dropdown menu.
+
+I think when the user selects the value from the dropdown menu, that's when we can apply the change (but keep the inspector open). An interface component like this one that has no ""Save"" button and implies automatic saving should either make sure the object being changed has no visual impact or make sure it is applied live (And not suddenly when clicking away / blurring the inspector)
+
+3) Adding a label (or rather, due to the lack of an input for the label, being forced to change the implied label) is unusable due to lack of text selection within the boundaries of the link (see video).
+
+4) After the link is inserted, the link text is selected in the surface (the link target in the inspector, which is still open, is also selected). It's not clear whether typing will replace the label or the link target (see video).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403713920,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-aevdvuut3fcigynuksnq,task_description,invalid
+VisualEditor: Creating a new link is unusable,"Better followed-up in specific bugs and proposed UX changes, as discussed.",1403717655,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"The link inspector has long been our most concentrated area of bugs. UX changes are coming in response to user testing, and many bug fixes are on their way as well - more are needed obviously.
+
+1. There is no universal link creation process, as every application differs here, but I believe we are not totally off base in our initial design. As usually, we have to solve this problem with the most difficult constraints imaginable. Users are meant to be able to successfully navigate through a 3x3 matrix of options: link existing text, change linked text, create new link text; link to an internal page, a fragment on the existing page or an external page; produce an explicitly labeled link, an automatically labeled link or an unlabeled (external) link. We need to map out all the use cases and come up with a process that covers this matrix elegantly.
+
+2. User testing has confirmed that, even though pressing enter, escape and clicking away all serve to apply and close, users want a button, and the back button doesn't make sense to them. The new design will do away with the back button. It will move the remove button to the bottom left and drop the confusing icon in favor of a destructive button labeled ""Remove"". On the bottom right will be a primary button labeled ""Done"", which will behave the same as pressing enter, escape or clicking away.
+
+3. We need to use the transaction staging system to update the selected content dynamically as you type, making the link appear to be internal, external, red, auto-numbered, auto-labeled, etc.
+
+4. The bug you experienced needs to be addressed, and I will see if it is resolved (or can be resolved) by my context and window refactoring work. The whole system has suffered from having a narrow entry point with too many poorly mapped forks in the road producing unreliable results with any given path at any given time.",1403717586,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,I've filed the pawn bug as bug 67088.,1403715487,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"(In reply to James Forrester from comment #2)
+> Created attachment 15744 [details]
+> Example video showing that issues are caused by having a link immediately
+> preceding the new list item
+
+This video does not follow the same steps. The link existing in the previous list item is irrelevant. You're pressing enter and clicking stuff in between which is what makes it save and work. Those are reflexes as result of hitting these bugs in the past presumably.
+
+Here's the proof:
+
+http://cl.ly/2P2h473b2A20
+
+**Attached**: {F14577}",1403715283,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"Created attachment 15744
+Example video showing that issues are caused by having a link immediately preceding the new list item
+
+**Attached**: {F14577}",1403714761,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"Regarding the pawn, that also ate the first character (see ""bc"" instead of ""abc"" appear in the recording).",1403714059,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+Toolbar alignment out of whack,"screenshot of problem
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/MediaWiki?veaction=edit
+
+**Attached**: {F14540}",1403686200,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-okhxrptvop7zaitv5gj5,task_description,resolved
+Toolbar alignment out of whack,"
+
+*** This bug has been marked as a duplicate of bug 66988 ***",1403734997,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,I had this problem in Safari 6.1.4 on Mac OS 10.8.5,1403732159,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,Safari 7,1403728943,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,*** Bug 66988 has been marked as a duplicate of this bug. ***,1403700121,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,WFM in Chrome & Firefox. What browser/version/OS are you using?,1403696124,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,"Created attachment 15733
+Another problem
+
+The second problem i sometimes see after initially loading. Interacting with the page makes the toolbar 'settle' and it's ok.
+
+Experienced it on https://www.mediawiki.org/wiki/VisualEditor?veaction=edit
+
+**Attached**: {F14541}",1403686286,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+"VisualEditor:  Section headings look like they've been removed, but they're still present when the page is saved","Why did it merge that subsection heading into the paragraph I was typing?
+
+Steps to reproduce:
+
+1.  Start editing a page with existing section headings.  Create a new paragraph above one of the section headings.
+
+2.  At some point, it looks like the ==Section heading== has accidentally been merged to the paragraph that you're typing.  It's no longer present below (just a blank line where it had been), and the text of the section heading is now (in paragraph formatting) in the paragraph you're typing.
+
+3.  Assume it's your fault (did you backspace?), and clean it up.  Replace the missing section heading.  Finish typing your paragraph, if necessary; you might have to do this a couple of times if the error recurs.
+
+4.  Save the page.
+
+5.  Check the diff, e.g., https://en.wikipedia.org/w/index.php?title=Candy_making&diff=prev&oldid=614021270
+
+6.  Ask yourself, why are there three section headings named ==Safety== in a row?
+
+
+If you don't replace the ""missing"" section heading, then everything works out:
+https://en.wikipedia.org/w/index.php?title=Candy&diff=614296008&oldid=614177828
+
+All of the attachments are from this diff.  I've only seen this in Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14503}",1403656140,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wno2xwrbywvfr44kwnto,task_description,resolved
+"VisualEditor:  Section headings look like they've been removed, but they're still present when the page is saved",Can't reproduce. Hopefully this is properly gone now. Wish we could confirm. :-(,1423675862,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wno2xwrbywvfr44kwnto,task_subcomment,NA
+"VisualEditor:  Section headings look like they've been removed, but they're still present when the page is saved","Created attachment 15723
+One of these things is not like the other
+
+**Attached**: {F14505}",1403656244,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wno2xwrbywvfr44kwnto,task_subcomment,NA
+"VisualEditor:  Section headings look like they've been removed, but they're still present when the page is saved","Created attachment 15722
+What it looked like just before I tried to save the page:  no ===Vegetarianism=== heading
+
+**Attached**: {F14504}",1403656217,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wno2xwrbywvfr44kwnto,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","I don't see the option to change the type of a parameter to ""string/line"" when I edit
+https://pt.wikipedia.org/wiki/Template:Marca_de_projeto/dados?action=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60693",1403369520,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-vjbacwfxxizwddsg34zm,task_description,resolved
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","Change 134928 merged by jenkins-bot:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1409438733,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","Change 134928 had a related patch set uploaded by Mooeypoo:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1405064955,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","Or are you referring to the change from ""string/line"" to just ""line""?
+https://gerrit.wikimedia.org/r/#/c/91623/9/spec.templatedata.json,unified
+(I can't select ""line"" either).",1403785930,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","I wasn't aware of that. In this case, there are docs to update, e.g.:
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/TemplateData/Tutorial#Completing_the_TemplateData_information",1403785873,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor",Didn't we remove those sub-types?,1403741972,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"The error is:
+
+err: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Browsertests::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Ruby::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Exec[bundle-install-/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]: Could not evaluate: Could not find command '/usr/local/rbenv/shims/bundle'
+
+---
+
+Full list of roles:
+
+  accountinfo                geshi                      parsoid                 
+  analytics                * gettingstarted             pdfhandler              
+  antispam                   globalusage                poem                    
+  antispoof                * guidedtour                 popups                  
+  apisandbox                 gwtoolset                  proofreadpage           
+  apparmor                   hadoop                     scribunto               
+  babel                      hhvm                       simple_miser            
+  betafeatures               hive                       simple_performant       
+  browsertests               https                      sitematrix              
+  centralauth                jsduck                     templatedata            
+  centralnotice              labs_initial_content       textextracts            
+  chromium                   mantle                     thumb_on_404            
+  cirrussearch               massmessage                timedmediahandler       
+  cite                     * math                       translate               
+  cldr                       mathsearch                 uls                     
+  codeeditor                 mleb                       uploadwizard            
+  commonsmetadata          * mobilefrontend             urlshortener            
+  confirmedit                multimedia                 vectorbeta              
+  doublewiki                 multimediaviewer         * visualeditor            
+  echo                       mysql                      wikidiff2               
+  education                  navigationtiming         * wikieditor              
+* eventlogging               newusermessage             wikihiero               
+  flow                       oauth                      wikilove                
+  fss                        pagedtiffhandler           wikimania_scholarships  
+  fundraising                pageimages               * wikimediaevents         
+  gadgets                    pagetriage                 wikimetrics             
+  geodata                  * parserfunctions            xhprof
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403054280,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-zom2liucvmkdzjzairgy,task_description,resolved
+VisualEditor fails to provision with rbenv error,"That solution makes perfect sense, and matches the symptoms, so I'm marking this fixed and not doing the retesting I mentioned in comment #8.",1404938920,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Change 145127 merged by jenkins-bot:
+Require git::clone before browsertests::bundle
+
+https://gerrit.wikimedia.org/r/145127",1404938483,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Change 145127 had a related patch set uploaded by BryanDavis:
+Require git::clone before browsertests::bundle
+
+https://gerrit.wikimedia.org/r/145127",1404938392,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"First try for me on a Trusty VM that had never had VE enabled before failed with:
+
+Error: Working directory '/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser' does not exist
+Error: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Browsertests::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Ruby::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Exec[bundle-install-/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/returns: change from notrun to 0 failed: Working directory '/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser' does not exist
+
+The problem for me was that browsertests::bundle doesn't require the git::clone.",1404937976,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"VisualEditor is working now on that box (after a vagrant up --provision), except there are timeouts in the browser tests.
+
+Next (when I have a chance), I'm going to try to destroy that box, and create a fresh one (but using the same Debian packages), to see if the problem manifests on a fresh build.",1404856994,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Created attachment 15845
+Fresh install on 2014-07-03
+
+It eventually failed due to not getting all the Debian packages.  I didn't try (yet) to re-provision and see if that fixed it
+
+Dan, let's decide to how to proceed Tuesday.  I will make sure I don't lose the apt-cache, so I won't have to re-download the vast majority that did succeed (or the trusty base box).
+
+**Attached**: {F13943}",1404437336,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Sure.
+
+matthew@matthew-t520: ~/Code/Wikimedia/vagrant-ruby-visualeditor/mediawiki/extensions/VisualEditor (master|✔)% git status
+# On branch master
+nothing to commit (working directory clean)
+matthew@matthew-t520: ~/Code/Wikimedia/vagrant-ruby-visualeditor/mediawiki/extensions/VisualEditor (master|✔)% git show-ref HEAD
+4be59a00c12580e24e2de673c14e082bf714ee9c refs/remotes/origin/HEAD
+matthew@matthew-t520: ~/Code/Wikimedia/vagrant-ruby-visualeditor/mediawiki/extensions/VisualEditor (master|✔)% git submodule
+ a014302f441dda5c4805d378f4ccb67bc1d5e566 lib/ve (a014302)
+
+Note, this is from a fresh MediaWiki-Vagrant VM I created (same one as comment #4), not my regular MediaWiki-Vagrant VM.",1404171075,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Can you verify the working commit of VE and its submodules? i.e. Please provide the output of `git status`, `git show-ref HEAD`, and `git submodule` under the mediawiki/extensions/VisualEditor subdirectory.",1404161980,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Created attachment 15775
+Log from fresh install of MediaWiki-Vagrant
+
+I tried with a new box, with the latest Ruby change (use distro packages), against git 99633340308c46c2d7ebc488195b2d47be0f235c, and the following roles:
+-----
+Available roles:
+
+  accountinfo              * gettingstarted             poem                    
+  analytics                  globalusage                popups                  
+  antispam                 * guidedtour                 proofreadpage           
+  antispoof                  gwtoolset                  scribunto               
+  apisandbox                 hadoop                     simple_miser            
+  apparmor                   hhvm                       simple_performant       
+  babel                      hive                       sitematrix              
+  betafeatures               https                      templatedata            
+  browsertests               jsduck                     textextracts            
+  centralauth                labs_initial_content       thumb_on_404            
+  centralnotice              mantle                     timedmediahandler       
+  chromium                   massmessage                translate               
+  cirrussearch             * math                       uls                     
+  cite                       mathsearch                 uploadwizard            
+  cldr                       mleb                       urlshortener            
+  codeeditor               * mobilefrontend             vectorbeta              
+  commonsmetadata            multimedia               * visualeditor            
+  confirmedit                multimediaviewer           wikidiff2               
+  doublewiki                 mysql                    * wikieditor              
+* echo                       navigationtiming           wikihiero               
+  education                  newusermessage             wikilove                
+* eventlogging               oauth                      wikimania_scholarships  
+* flow                       pagedtiffhandler         * wikimediaevents         
+  fss                        pageimages                 wikimetrics             
+  fundraising                pagetriage                 wikitech                
+  gadgets                  * parserfunctions            xhprof                  
+  geodata                  * parsoid                                            
+  geshi                      pdfhandler                                         
+
+Roles marked with '*' are enabled.
+Use ""vagrant enable-role"" & ""vagrant disable-role"" to customize.
+-----
+I got the attached log.  You can see that VisualEditor failed, first with:
+
+Sat Jun 28 06:17:50 +0000 2014 /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Browsertests::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Ruby::Bundle[/vagra\
+nt/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Exec[bundle-install-/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/returns (err): change from notrun to 0 failed: Workin\
+g directory '/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser' does not exist
+
+It is not the first failure (Math also failed due to bug 66807), but I'm not sure the Math failure is related.
+
+**Attached**: {F13942}",1403988909,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Matthew, Would you mind trying this again in case the fix to bug #66763 was related? Thanks!",1403902785,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Created attachment 15683
+Puppet error with VisualEditor provisioning failure
+
+Yes, it's reproducible on repeated provisioning runs.  I've attached the full log from a debug run.
+
+**Attached**: {F13941}",1403121299,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"I'm unable to repro this from a fresh VM with the given roles enabled. Do you continue to get this error after provisioning a second time?
+
+Given the sometimes tricky nature of Puppet resource dependencies, it would help greatly to have a more detailed log of the run. Can you please specify `puppet_debug: true` in your `.settings.yaml` file and provide the output or `vagrant provision` as an attachment? Thanks!",1403116140,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Wikitext: '''foo[[File:Image.jpg|thumb]]bar'''
+
+Resulting DOM: <body><b><figure><a><img /></a></figure>bar</b>
+
+Block nodes like figure aren't supposed to occur inside of inline-ish (annotation) tags like b. When confronted with this, VisualEditor alienates the image to preserve its sanity (data model consistency), so bolded images can't be edited in VE.
+
+Reported by mattk_ on IRC.
+
+$ echo ""'''foo[[File:Image.jpg|thumb]]bar'''"" | node tests/parse.js
+
+<!DOCTYPE html>
+<html prefix=""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/""><head prefix=""mwr: http://en.wikipedia.org/wiki/Special:Redirect/""><meta property=""mw:parsoidVersion"" content=""0""/><link rel=""dc:isVersionOf"" href=""//en.wikipedia.org/wiki/Main_Page""/><title></title><base href=""//en.wikipedia.org/wiki/Main_Page""/><link rel=""stylesheet"" href=""//en.wikipedia.org/w/load.php?modules=mediawiki.skinning.elements|mediawiki.skinning.content|mediawiki.skinning.interface|skins.vector.styles|site|mediawiki.skinning.content.parsoid&amp;only=styles&amp;debug=true&amp;skin=vector""/></head><body data-parsoid='{""dsr"":[0,37,0,0]}' lang=""en"" class=""mw-content-ltr mw-body-content"" dir=""ltr""><b data-parsoid='{""dsr"":[0,36,3,3]}'>foo<figure class=""mw-default-size"" typeof=""mw:Image/Thumb"" data-parsoid='{""optList"":[{""ck"":""thumbnail"",""ak"":""thumb""}],""dsr"":[6,30,2,2]}'><a href=""./File:Image.jpg"" data-parsoid='{""a"":{""href"":""./File:Image.jpg""},""sa"":{},""dsr"":[8,28,null,null]}'><img resource=""./File:Image.jpg"" src=""//upload.wikimedia.org/wikipedia/en/thumb/7/78/Image.jpg/220px-Image.jpg"" height=""30"" width=""220"" data-parsoid='{""a"":{""resource"":""./File:Image.jpg"",""height"":""30"",""width"":""220""},""sa"":{""resource"":""File:Image.jpg""}}'/></a></figure>bar</b>
+</body></html>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403043660,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5udu3lh4gaeui3owoea2,task_description,resolved
+Parsoid outputs <figure> inside of <b>,">>! In T68749#4456438, @Arlolra wrote:
+>> Let us open a fresh task since this is specifically about figure in b that was addressed.
+> 
+> Ok, but the only thing that was addressed here was T68749#702519 (similarly T65642).
+> 
+> As quoted in T68749#4452211, the output of T68749#702575 was really case dependent.
+
+Got it .. but, did you reopen to only fix the figure in block tags case or something more general? But, I think either way ... a fresh task with clear description of what needs fixing is better since some of this history is too old and stale .. especially since you will have to edit the description and title.",1532709982,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"> Let us open a fresh task since this is specifically about figure in b that was addressed.
+
+Ok, but the only thing that was addressed here was T68749#702519 (similarly T65642).
+
+As quoted in T68749#4452211, the output of T68749#702575 was really case dependent.",1532705503,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,Let us open a fresh task since this is specifically about figure in b that was addressed. You are talking about a generic html content model violation.,1532671743,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"From the commit message of https://github.com/wikimedia/parsoid/commit/d473791ea982178af7a0fe15aff5cf8e21aaa5e8
+
+> However, in T68749, there's a request/argument to avoid nesting blocks
+> in formatting tags, since VE can't handle that data model violation and
+> marks the nodes as uneditable.  In the past, we've supported that
+> inconsistently.  For example, the case in ""1. List embedded in a
+> formatting tag"" is uneditable, despite it being a popular pattern.
+> In ""2. Treebuilder fixup of formatting elt"", only one of two images was
+> editable.
+>
+> We should consider reopening T68749 and adding a pass to solve the issue
+> generally.  Note that the Parsoid output now matches Remex so any
+> changes to the DOM is explicitly introducing a difference to support
+> editing clients, and should be noted as such.",1532574872,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"(In reply to ssastry from comment #8)
+> Roan: see below .. I don't see a <b> inside the <a> tag. Can you provide the
+> wikitext where you are seeing the problem html?
+> 
+> [subbu@earth lib] echo ""'''foo[[File:Foobar.jpg|thumb|caption]]bar'''"" |
+> node parse --normalize
+> 
+> <p><b>foo</b></p>
+> <figure><a href=""File:Foobar.jpg""><img
+> src=""//upload.wikimedia.org/wikipedia/commons/3/3a/Foobar.jpg"" height=""26""
+> width=""220""/></a><figcaption><b>caption</b></figcaption></figure>
+> <p><b>bar</b></p>
+
+Sorry, I'm blind. You're right, the output is correct now.",1413322888,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Roan: see below .. I don't see a <b> inside the <a> tag. Can you provide the wikitext where you are seeing the problem html?
+
+[subbu@earth lib] echo ""'''foo[[File:Foobar.jpg|thumb|caption]]bar'''"" | node parse --normalize
+
+<p><b>foo</b></p>
+<figure><a href=""File:Foobar.jpg""><img src=""//upload.wikimedia.org/wikipedia/commons/3/3a/Foobar.jpg"" height=""26"" width=""220""/></a><figcaption><b>caption</b></figcaption></figure>
+<p><b>bar</b></p>",1413322614,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"(In reply to Gerrit Notification Bot from comment #6)
+> Change 162819 merged by jenkins-bot:
+> (Bug 66749) Fix the test for DU.isGeneratedFigure
+> 
+> https://gerrit.wikimedia.org/r/162819
+
+This makes it better, but the resulting HTML still violates the Parsoid HTML spec.
+
+Old output: <body><b>foo<figure><a><img /></a></figure>bar</b></body>
+
+New output: <body><p><b>foo</b></p><figure><a><b><img /></b></a></figure><p><b>bar</b></p></body>
+
+At least the figure isn't bolded any more, but there's still a <b> tag between the <a> and the <img> whereas according to the spec, the structure should be <figure><a><img>",1413316823,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Change 162819 merged by jenkins-bot:
+(Bug 66749) Fix the test for DU.isGeneratedFigure
+
+https://gerrit.wikimedia.org/r/162819",1411688205,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Change 162819 had a related patch set uploaded by Subramanya Sastry:
+(Bug 66749) Fix the test for DU.isGeneratedFigure
+
+https://gerrit.wikimedia.org/r/162819",1411617418,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"What Gabriel points out in comment 2 is exactly the same as bug 63642. The DOM I get from <p>'''foo[[File:Image.jpg|thumb|caption]]bar''' looks like <p><b>foo</b></p><figure><b><a><img /></a><figcaption>caption</figcaption></b></figure><p><b>bar</b></p>
+
+(In reply to C. Scott Ananian from comment #1)
+> Not sure this is a bug:
+> 
+> > div = document.createElement('div')
+> <div>​</div>​
+> > div.innerHTML=""<b><figure></figure></b>""
+> ""<b><figure></figure></b>""
+> > div.outerHTML
+> ""<div><b><figure></figure></b></div>""
+> > div.innerHTML=""<b><div></div></b>""
+> ""<b><div></div></b>""
+> > div.outerHTML
+> ""<div><b><div></div></b></div>""
+> 
+> Note that HTML5 is perfectly happy to let the block element live inside the
+> <b> tag.
+Yeah, HTML lets you do it, but I don't think it's very sensible, and VE doesn't like it. I also see no reason why the behavior should be radically different depending on whether Parsoid has decided that the text is in a paragraph or free text. In the paragraph case, the bold tag is interrupted (and reapplied inside the figure, but that's bug 63642; really it should be reapplied in the caption instead, or not at all) and the figure isn't bolded, but in the free text case the figure is bolded. Given that the distinction between free text and paragraph text is pretty arbitrary, I don't think this makes much sense.
+
+Speaking of, this paragraph vs free text stuff is also pretty broken. The following wikitext:
+
+'''foo[[File:Image.jpg|thumb|caption]]bar'''
+
+'''foo[[File:Image.jpg|thumb|caption]]bar'''
+
+produces a DOM that looks like  <body><b>foo<figure><a><img /></a></figure>bar</b>\n\n<b>foo<figure><a><img /></a></figure>bar</b></body> which is wrong: bar and foo will be on the same line but shouldn't be.",1403045057,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"(Taking the bug, since if it ends up being a real bug with our image spec, I'll fix it in Parsoid.  It appears that, to the extent this is a real bug, it's a dup of bug 63642 though.)",1403044295,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"At a minimum, we should not create output that has the figcaption inside a figure wrapped into a formatting element.
+
+Yet that's what I seem to get with this input:
+
+<p>'''foo[[File:Image.jpg|thumb|caption]]bar'''",1403044135,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Not sure this is a bug:
+
+> div = document.createElement('div')
+<div>​</div>​
+> div.innerHTML=""<b><figure></figure></b>""
+""<b><figure></figure></b>""
+> div.outerHTML
+""<div><b><figure></figure></b></div>""
+> div.innerHTML=""<b><div></div></b>""
+""<b><div></div></b>""
+> div.outerHTML
+""<div><b><div></div></b></div>""
+
+Note that HTML5 is perfectly happy to let the block element live inside the <b> tag.",1403043980,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Currently, Parsoid runs the following check to tell if an interwiki link points at the current wiki [1]:
+
+if ( interwikiInfo.prefix === env.conf.wiki.iwp.replace( /wiki/, '' ) ) {
+
+Obviously this is inadequate when the wiki name doesn't end in ""wiki"". (It's slightly unclear to me what ""iwp"" is; it claims to be an interwiki *prefix*, but some of the tests set it to ""enwiki"", so I'm assuming it's actually the DB name.)
+
+See http://parsoid.wmflabs.org/_rt/mediawikiwiki/VisualEditor:Local. Currently the first link is ""mw:WikiLink"" and the second is ""mw:ExtLink"", which is wrong. The PHP parser renders them identically as internal links.
+
+---
+[1] http://git.wikimedia.org/blob/mediawiki%2Fservices%2Fparsoid.git/18e31a06252db3813fe844b62f15248289cdf4cb/lib%2Fext.core.LinkHandler.js#L106
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403000460,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_description,resolved
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Change 155784 merged by jenkins-bot:
+Handle local interwiki links.
+
+https://gerrit.wikimedia.org/r/155784",1408986548,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Change 155784 had a related patch set uploaded by Cscott:
+WIP: handle local interwiki links.
+
+https://gerrit.wikimedia.org/r/155784",1408734995,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Ok, taking this.  It's related to bug 69909.  We should be using localinterwiki from the siteinfo.",1408733304,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Change 141276 merged by jenkins-bot:
+Expose $wgLocalInterwikis via the API
+
+https://gerrit.wikimedia.org/r/141276",1403531704,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Change 141276 had a related patch set uploaded by TTO:
+Expose $wgLocalInterwikis via the API
+
+https://gerrit.wikimedia.org/r/141276",1403414802,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,The MediaWiki API needs to expose the contents of $wgLocalInterwikis via the API's meta=siteinfo&prop=interwikimap. Then Parsoid will be able to consume that information.,1403000528,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+VisualEditor:  Typing diacritics results in stray accent marks at the top of the page in Chrome,"María typed her name in VisualEditor on a Mac:  [SHIFT] m + a + r + [OPTION] e + i + a. 
+
+She runs Chrome on a MacBook Pro with a U.S. keyboard.  The result was this:
+
+
+[top of page]
+´
+
+Lots of text here
+
+María
+
+The rest of the page
+
+[end of page]
+
+
+Using a normal keyboard shortcut to add accents to characters should not result in  stray ""´"" characters at the top of the page.
+
+See https://office.wikimedia.org/w/index.php?diff=113478&oldid=113425 for an example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402958220,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ughpsi3kiwodix5i5iuq,task_description,declined
+VisualEditor:  Typing diacritics results in stray accent marks at the top of the page in Chrome,Testing after the latest update was unable to reproduce the problem.,1403301845,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ughpsi3kiwodix5i5iuq,task_subcomment,NA
+VisualEditor:  Typing diacritics results in stray accent marks at the top of the page in Chrome,"I can't reproduce in Chrome or Safari either, in master, testing or production – possibly something odd with a system IME or similar? Provisionally marking as WORKSFORME – can María test again and confirm?",1403127698,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ughpsi3kiwodix5i5iuq,task_subcomment,NA
+VisualEditor:  Typing diacritics results in stray accent marks at the top of the page in Chrome,I can't reproduce this in Safari 6.1.4 on my Mac and haven't tried to reproduce it in Chrome.,1402958281,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ughpsi3kiwodix5i5iuq,task_subcomment,NA
+VisualEditor: Getting Error loading data from server while reviewing changes from Save dialog,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Edit a page
+3.Click on ""Save Page""
+4.Click on ""Review your changes""
+
+Observed Result:
+
+Getting Error loading data from server while reviewing changes from Save dialog 
+
+See the screenshot attached
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13711}",1402942920,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fp5nv7xkzn6llpv5rdfl,task_description,resolved
+VisualEditor: Getting Error loading data from server while reviewing changes from Save dialog,"
+
+*** This bug has been marked as a duplicate of bug 66669 ***",1402943552,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fp5nv7xkzn6llpv5rdfl,task_subcomment,NA
+VisualEditor: Getting Error loading data from server while reviewing changes from Save dialog,"Change 139879 had a related patch set uploaded by Catrope:
+Followup e48ecbc5: fix fatal error due to undefined variable
+
+https://gerrit.wikimedia.org/r/139879",1402943491,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fp5nv7xkzn6llpv5rdfl,task_subcomment,NA
+Breaking VisualEditor breaks wikitext editor,"If VisualEditor ever throws an exception, which seems to be happening a lot, this means that the editor is inaccessible unless you resize the window and refresh.
+
+When an error occurs the wikitext editor should be loaded instead.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402941240,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-xtf36l2ciogrg6tcnf6x,task_description,resolved
+Breaking VisualEditor breaks wikitext editor,"Change 143797 merged by jenkins-bot:
+If error occurs while loading VE, load source editor instead
+
+https://gerrit.wikimedia.org/r/143797",1405112206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtf36l2ciogrg6tcnf6x,task_subcomment,NA
+Breaking VisualEditor breaks wikitext editor,"Change 143797 had a related patch set uploaded by Kaldari:
+If error occurs while loading VE, load source editor instead
+
+https://gerrit.wikimedia.org/r/143797",1404347298,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtf36l2ciogrg6tcnf6x,task_subcomment,NA
+Breaking VisualEditor breaks wikitext editor,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/iIcumWus",1402941311,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xtf36l2ciogrg6tcnf6x,task_subcomment,NA
+VisualEditor:  Re-using references isn't working very well,"Incident #1:
+
+Add a reference.  Try to re-use it.  It's not in the list at all.
+
+
+Incident #2:
+
+Add a reference using the Cite tool.  Try to re-use it.  It's not in the list at all.  Add a plain <references /> block (rather than {{reflist}}).  Go back and try to re-use it.  Now it's there.
+
+
+Incident #3:
+
+Add a reference.  Try to re-use it.  Only the number (""[1]"") is present in the references list; the old refs are all listed correctly.  Cancel and go look at the new ref to make sure that it actually has contents.  Try to re-use it again.  Now the full description appears.  (Perhaps it was just being slow?  Perhaps it needed something else to trigger it?)
+
+
+(All of these happened in Firefox.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402789800,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yohnyaa6rhyxwjflhy7p,task_description,declined
+VisualEditor:  Re-using references isn't working very well,Let's leave this as worksforme unless someone can find another bug to mark it as a duplicate of.,1414810464,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yohnyaa6rhyxwjflhy7p,task_subcomment,NA
+VisualEditor:  Re-using references isn't working very well,"I don't think that these are actually three bugs:  I think they are all the same problem, which is that (what is now) Cite > Re-use did not correctly produce a list of existing citations.
+
+I believe that this was resolved a couple of months ago, in some related work.  I haven't encountered this myself or heard any complaints about it for a long while.  The correct status is probably resolved/duplicate.",1414809250,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yohnyaa6rhyxwjflhy7p,task_subcomment,NA
+VisualEditor:  Re-using references isn't working very well,Why are there three bugs in one here? Is any of this still valid? Were you trying to use templates instead of the proper references tag in #1 and #3 as well?,1414808741,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yohnyaa6rhyxwjflhy7p,task_subcomment,NA
+VisualEditor:  Make it possible to click on a link or URL that's inside a template (to open the link in another tab),"There are a lot of templates that create or display links to other pages.  It would be nice if it were possible to click on those links (to open the linked pages in another tab) while editing VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402600620,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-iueuapim3yguer55bovm,task_description,resolved
+VisualEditor:  Make it possible to click on a link or URL that's inside a template (to open the link in another tab),"
+
+*** This bug has been marked as a duplicate of bug 50966 ***",1402688065,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iueuapim3yguer55bovm,task_subcomment,NA
+"add ""Cite"", ""TemplateData"", ""ParserFunctions"" and Lua extensions for ""visualeditor"" role","References in VE do not work properly in the vagrant VM without also having the Cite extension in place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402527600,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-jozgz5cpm6v67hgjs2el,task_description,resolved
+"add ""Cite"", ""TemplateData"", ""ParserFunctions"" and Lua extensions for ""visualeditor"" role","Change 139053 merged by jenkins-bot:
+Added more depedency roles to visualeditor
+
+https://gerrit.wikimedia.org/r/139053",1402534918,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jozgz5cpm6v67hgjs2el,task_subcomment,NA
+"add ""Cite"", ""TemplateData"", ""ParserFunctions"" and Lua extensions for ""visualeditor"" role","Change 139053 had a related patch set uploaded by Dduvall:
+Added more depedency roles to visualeditor
+
+https://gerrit.wikimedia.org/r/139053",1402534455,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jozgz5cpm6v67hgjs2el,task_subcomment,NA
+"add ""Cite"", ""TemplateData"", ""ParserFunctions"" and Lua extensions for ""visualeditor"" role","
+16:12 chrismcmahon: RoanKattouw: beyond needing Cite for references in VE, is any other extension required for handling templates in VE properly?
+16:13 James_F: chrismcmahon: TemplateData.
+16:13 James_F: chrismcmahon: And Lua and ParserFunctions for most of the existing corpus of templates.
+16:13 chrismcmahon: James_F: awesome",1402528496,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-jozgz5cpm6v67hgjs2el,task_subcomment,NA
+bare wiki + VE does not handle References properly,"Use existing references disabled for page with references
+
+found in the course of enabling browser tests for the Vagrant role visualeditor: 
+
+In the mediawiki visualeditor role and also in a bare wiki having the VisualEditor extensions, references are not handled properly.  
+
+In the pure page view the existing references are not interpreted by the <references /> tag.  See screen shot. 
+
+In VE, the ""Use an existing reference"" button is disabled. See screen shot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13915}",1402527060,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_description,invalid
+bare wiki + VE does not handle References properly,I hate screen shots,1402527370,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+bare wiki + VE does not handle References properly,"gah,",1402527344,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+bare wiki + VE does not handle References properly,"(In reply to Chris McMahon from comment #1)
+> Created attachment 15632 [details]
+> ""Use existing reference"" button disabled on a page with a reference
+Nice vacation accrual stats ;)
+
+(In reply to Roan Kattouw from comment #2)
+> Did you install the Cite extension? Without it, the <ref> and <references>
+> tags don't work in read mode either.
+Additionally, you need to restart Parsoid after installing the Cite extension.
+
+**Attached**: {F13916}",1402527242,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+bare wiki + VE does not handle References properly,"Did you install the Cite extension? Without it, the <ref> and <references> tags don't work in read mode either.",1402527182,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+bare wiki + VE does not handle References properly,"Created attachment 15632
+mistake, disregard
+
+**Attached**: {F13916}",1402527107,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+VisualEditor: Footnote number is not localized while editing,"See the URL for an example.
+
+The reference numbers are not localized in languages that use non-European numbers, such as Arabic and Persian. They are localized correctly while viewing the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://fa.wikipedia.org/wiki/User:Amire80/ref-numbers",1402213680,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-cmxp5glim7b3bnu36xg4,task_description,resolved
+VisualEditor: Footnote number is not localized while editing,"
+
+*** This bug has been marked as a duplicate of bug 56240 ***",1402329599,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmxp5glim7b3bnu36xg4,task_subcomment,NA
+Javascript error when launching desktop VisualEditor (target.createSurface is not a function),"Whenever I try to launch the desktop VE, I get a JS error...
+
+In Firefox: 'target.createSurface is not a function'
+In Chrome: 'Uncaught TypeError: undefined is not a function'
+
+In both cases it comes from ve.init.mw.Target.js, line 1312:
+target.surface = target.createSurface( dmDoc );
+
+The error doesn't happen in mobile VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402081500,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-772o537nc7bdn7wry7rh,task_description,invalid
+Javascript error when launching desktop VisualEditor (target.createSurface is not a function),Nevermind. Had to update the VE submodules.,1402081615,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-772o537nc7bdn7wry7rh,task_subcomment,NA
+tracking: Flow loses session/token information,"Seen only one time:  https://wmf.ci.cloudbees.com/job/Flow-en.wikipedia.beta.wmflabs.org-linux-chrome/465/
+
+As a logged-in user, create a new topic in Flow.  Topic was saved as anonymous, even though user logged in successfully and test showed no sign of user logging out. 
+
+I want to note this because of the similarity to an intermittent issue when switching edit modes in VisualEditor, bug 65709
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+{T67709}",1401805680,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-og532unr32aprpg62cxq,task_description,invalid
+tracking: Flow loses session/token information,Closing - was seen only once & there hasn't been any new report since (and it's been open for > half a year),1418317389,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-og532unr32aprpg62cxq,task_subcomment,NA
+VisualEditor: Duplicate setting of named parameter in template removed when you edit the template in some unrelated way,"""visual editor did more than i told it to: https://en.wikipedia.org/w/index.php?title=Cameroon&diff=611127082&oldid=610427158 ""
+""hmm looks like ve actually removed a duplicate parameter when i made that edit""
+
+Seems this occurs when you edit a template in some way (e.g. adding a new parameter), if a named parameter has been set twice.
+
+Not sure if this is intended behaviour or not. Bug might be a dupe, might be in Parsoid instead of VE, or something else.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401654960,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-pbprcixeydceic4lndax,task_description,declined
+VisualEditor: Duplicate setting of named parameter in template removed when you edit the template in some unrelated way,"This is intended behaviour, yeah; we won't dirty-diff to fix broken wikitext when you edit something else, but VE will always fix up bad existing formatting when you change the item.",1401758985,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pbprcixeydceic4lndax,task_subcomment,NA
+Visual inconsistencies between OOJS and VisualEditorOverlay,"exit overlay
+
+See attachments
+
+* Different X icons used for VisualEditor close and OOUI close
+* There are vertical borders in the VE toolbar
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13867}",1401478260,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-vdyxqxqymleikvtbkkbj,task_description,invalid
+Visual inconsistencies between OOJS and VisualEditorOverlay,"**jgonera** wrote:
+
+Presently OOUI forms look completely different because of a few refactorings that happened in OOUI since that bug was reported. Visual consistency will be tackled in the new OOUI theme.",1406571087,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vdyxqxqymleikvtbkkbj,task_subcomment,NA
+Visual inconsistencies between OOJS and VisualEditorOverlay,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/MaI2stPq",1401478519,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vdyxqxqymleikvtbkkbj,task_subcomment,NA
+Visual inconsistencies between OOJS and VisualEditorOverlay,"Created attachment 15539
+Exit dialog in VE
+
+**Attached**: {F13868}",1401478299,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-vdyxqxqymleikvtbkkbj,task_subcomment,NA
+VisualEditor: Existing page shows up under New Page section inside Link Inspector in production,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page
+2.Attempt to insert a link with an existing target page such as ""Test""
+
+Observed Result :
+
+The page ""Test"" appears under the New Page section inside Link Inspector.
+See the screenshot attached
+
+Environment:
+https://en.wikipedia.org/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13800}",1401412020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pcp54qhvwgbbzskvrcsq,task_description,resolved
+VisualEditor: Existing page shows up under New Page section inside Link Inspector in production,"
+
+*** This bug has been marked as a duplicate of bug 51013 ***",1402016305,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pcp54qhvwgbbzskvrcsq,task_subcomment,NA
+"VisualEditor:  When editing a page in the Category: namespace, the contents of the category do not display upon saving","Intention:
+Change the contents of a category page (the description, not the files in it).  See https://commons.wikimedia.org/w/index.php?title=Category:Cuberdon&diff=prev&oldid=125000311
+
+Steps to Reproduce:
+1. Open the page in VisualEditor.
+2. Change the description.
+3. Save the page.
+
+Actual Results:  
+Upon savingm the description was displayed, but not the contents of the category.
+
+Expected Results:  
+You should be able to see all the images in that category, not just the text at the top of the cat page.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401407520,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-r7mvsfuq3amffbdzvceu,task_description,resolved
+"VisualEditor:  When editing a page in the Category: namespace, the contents of the category do not display upon saving","
+
+*** This bug has been marked as a duplicate of bug 64239 ***",1401408756,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r7mvsfuq3amffbdzvceu,task_subcomment,NA
+"toggle to VE makes UI spin forever, no VE, js error","on http://en.m.wikipedia.beta.wmflabs.org/ as logged-in user; set Settings mode for VE access; edit a page; toggle VisualEditor mode
+
+browser shows spinner forever
+
+javascript error is ""Error: Module not found: toggle 
+Error
+message: ""Module not found: toggle""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401203820,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-37lwji5jwrqcsuanpdky,task_description,invalid
+"toggle to VE makes UI spin forever, no VE, js error",This is bug 65823 but the JavaScript error is unrelated to that and actually bug 65838,1401233082,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-37lwji5jwrqcsuanpdky,task_subcomment,NA
+"toggle to VE makes UI spin forever, no VE, js error","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/lIGKYsRM",1401204014,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-37lwji5jwrqcsuanpdky,task_subcomment,NA
+VisualEditor introduces <nowiki> and then breaks template syntax,"https://pt.wikipedia.org/wiki/Jos%C3%A9_Antonio_Reyes?diff=38627387
+https://pt.wikipedia.org/wiki/Jos%C3%A9_Antonio_Reyes?diff=38645684
+https://pt.wikipedia.org/wiki/Jos%C3%A9_Antonio_Reyes?diff=39007919
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401103500,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ofzs6modf4yxz63ugmdy,task_description,resolved
+VisualEditor introduces <nowiki> and then breaks template syntax,This shouldn't now be happening. Long-since fixed.,1442345202,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ofzs6modf4yxz63ugmdy,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"Seasoned Catalan Wikipedia editors are finding strange diffs done by new editors using VisualEditor. See these examples:
+
+https://ca.wikipedia.org/w/index.php?title=Laocoont_o_sobre_els_l%C3%ADmits_en_la_pintura_i_poesia&diff=13401584&oldid=13401089
+
+https://ca.wikipedia.org/w/index.php?title=Joan_Francesc_Ferrer_Sicilia&curid=1102012&diff=13399985&oldid=13399856
+
+https://ca.wikipedia.org/w/index.php?title=Pere_Formiguera_i_Sala&oldid=13189613
+
+https://ca.wikipedia.org/w/index.php?title=Pere_Formiguera_i_Sala&diff=13276699&oldid=13276658
+
+We are still figuring out whether these strange edits are made on purpose or not, by humans or by some VisualEditor bug. Reporting here to check whether someone else has seen something similar elsewhere, or can shed some light.
+
+Related discussion (in Catalan)
+https://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Ajuda#Curiositat
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400848080,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-otxks6mxubirbwsvqvfv,task_description,resolved
+Hypothetical generation of strange characters at the beginning of pages,"While ca.wiki got plenty of strange characters during several weeks, that happened month ago, and the strange characters haven't been seen ever since.
+
+We might not know the cause neither the solution, but the problem seems to be Resolved.
+
+https://ca.wikipedia.org/wiki/Topic:Sb2iif7fvhy6p365",1422959784,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"While ca.wiki got plenty of strange characters during several weeks, that happened month ago, and the strange characters haven't been seen ever since.
+
+We might not know the cause neither the solution, but the problem seems to be Resolved.",1422959740,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,See also Bug 63395,1403394234,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"(In reply to Quim Gil from comment #7)
+> it includes ☃ and ♙ !
+
+These specific two icons (snowman ☃ and chess pawn ♙) are a debugging feature of VE and unrelated to the original issue reported here.  ☃ and ♙ usually means that Parsoid has encountered something confusing in the wikitext markup.",1403364579,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"This problem keeps happening regularly, e.g. https://ca.wikipedia.org/w/index.php?title=Ferran_Clavell&diff=prev&oldid=13600764
+
+The most surreal edit we have seen so far: https://ca.wikipedia.org/w/index.php?title=Ana_Zelich&diffonly=1&diff=13511465 -- it includes ☃ and ♙ !
+
+One user reported MacBook Pro amb 10.8.5 with Chrome v34.0.1847.131. He also said that he could reproduce it sometimes by typing ""wrong"" accents, e.g. accent + space. 
+
+This might be due to newbie users typing ""L´aventura"" instead of ""L'aventura"" (note the different ´ '). How to test this: at least in my International English keyboard you can type ´ by typing twice '.",1403325888,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"Just in case those users all use Firefox, https://bugzilla.mozilla.org/show_bug.cgi?id=1015433 comes to my mind, though rather unlikely.
+We really need more info on the browser(s) used....",1401296913,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"The user hasn't answered yet. However, while bug 52327 is about ""garbage"" being injected in pages, that garbage consists at least in JavaScript chunks. In this case it is really meaningless garbage. Garbage so meaningless and relatively random that I still fail to deduce where does it come from.",1401176461,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,I asked because I'm wondering if this is another case of broken browser plugins (bug 52327)...,1401157753,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"More, from more users:
+
+https://ca.wikipedia.org/w/index.php?title=Partit_dels_i_les_Comunistes_de_Catalunya&diff=prev&oldid=13430606
+
+https://ca.wikipedia.org/w/index.php?title=Purita_Campos&diff=13441743&oldid=13383289
+
+I will ask the user that replied which browser he is using.",1401143640,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,Which browsers and browser versions are involved?,1401099980,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"One of the editors, a school teacher, replied saying that he hadn't added those characters manually. We still haven't found a way to reproduce this problem.",1401014103,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Error thrown when try to create new pages in wikitext when VisualEditor is default,"Go to a page that doesn't exist.
+Click edit so that VisualEditor loads.
+Toggle to source mode.
+A JavaScript exception is thrown and the loader never clears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400686260,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-u7g6dtcwyoyjlymqpi37,task_description,resolved
+Error thrown when try to create new pages in wikitext when VisualEditor is default,"Change 135722 merged by jenkins-bot:
+Use same options for VisualEditor and Editor overlays
+
+https://gerrit.wikimedia.org/r/135722",1401302630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u7g6dtcwyoyjlymqpi37,task_subcomment,NA
+Error thrown when try to create new pages in wikitext when VisualEditor is default,"Change 135722 had a related patch set uploaded by Jdlrobson:
+Use same options for VisualEditor and Editor overlays
+
+https://gerrit.wikimedia.org/r/135722",1401234961,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u7g6dtcwyoyjlymqpi37,task_subcomment,NA
+Error thrown when try to create new pages in wikitext when VisualEditor is default,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/BGNz7shU",1400692793,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-u7g6dtcwyoyjlymqpi37,task_subcomment,NA
+503 from Parsoid in beta labs,"attempt to edit any page in http://en.wikipedia.beta.wmflabs.org/ with VisualEditor
+
+get error ""Error loading data from server: parsoidserver-http-bad-status: 503. Would you like to retry?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400619780,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-wurlwpdl3llexy7jqxw5,task_description,resolved
+503 from Parsoid in beta labs,"
+
+*** This bug has been marked as a duplicate of bug 65553 ***",1400619845,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wurlwpdl3llexy7jqxw5,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"I'm currently trying to edit Wikivoyage and nothing happens when I click edit. Very weird. hash does change...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400588160,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-hf7auwexf5hzfjlto5wz,task_description,resolved
+Edit button seems to have no effect in Wikivoyage,"Change 134410 merged by jenkins-bot:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134410",1400612157,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134411 merged by jenkins-bot:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134411",1400611800,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134411 had a related patch set uploaded by MaxSem:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134411",1400611736,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134410 had a related patch set uploaded by MaxSem:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134410",1400611707,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134405 merged by jenkins-bot:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134405",1400611536,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134405 had a related patch set uploaded by Jdlrobson:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134405",1400610990,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"
+
+*** This bug has been marked as a duplicate of bug 65509 ***",1400610714,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Could have sworn I raised this bug previously but here we go again..
+Load Article#editor/0 in alpha
+See VisualEditor.
+Switch to source editor.
+Now refresh the page using browser.
+Wikitext editor loads.
+Attempt to switch to VisualEditor.
+Fail.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400532480,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ltqykuq33aln74viml6d,task_description,resolved
+Cannot switch to VisualEditor after a reload,"Change 137731 merged by jenkins-bot:
+Show loader when switching between editors
+
+https://gerrit.wikimedia.org/r/137731",1402102067,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Change 137731 had a related patch set uploaded by Jdlrobson:
+Show loader when switching between editors
+
+https://gerrit.wikimedia.org/r/137731",1401993634,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Change 137251 abandoned by Jdlrobson:
+Show a spinner when switching between editors
+
+Reason:
+I'm going to do this another way.
+
+https://gerrit.wikimedia.org/r/137251",1401993313,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Change 137251 had a related patch set uploaded by Jdlrobson:
+Show a spinner when switching between editors
+
+https://gerrit.wikimedia.org/r/137251",1401845823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Change 136249 had a related patch set uploaded by Jdlrobson:
+WIP: have a standard way of invoking loader
+
+https://gerrit.wikimedia.org/r/136249",1401402678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Best way to simulate this... Open wikitext editor via clicking edit icon.
+Kill your web server.
+Click the toggle to VE icon.
+Nothing happens.",1401399166,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Created attachment 15464
+Double toolbar loading in VE
+
+**Attached**: {F14060}",1400856764,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Created attachment 15463
+Delay between clicking button and seeing VE
+
+**Attached**: {F14059}",1400856697,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,It's not just the spinner - just sometimes it doesn't even start loading. I'm worried this indicates some bigger kind of problem. Let me attach some videos demonstrating the behaviour I am seeing...,1400856627,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"**jgonera** wrote:
+
+I'm marking as workforsome, please raise another bug if there are problems with the spinner.",1400854714,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,On my local instance it takes 2-3 seconds for VE to load cold but the spinner appears almost instantly.,1400704098,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"I don't see any indicator whatsoever for those 5 seconds so usually click it more than once :-(
+
+
+A few times I've also seen two toolbars get created.",1400692673,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"**jgonera** wrote:
+
+It takes about half a second on my vagrant instance, but the indication (loader) should probably appear earlier.",1400692597,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"So actually I've noticed it does actually load eventually but it takes 6 seconds to do so and doesn't show a loading overlay or anything so it's not clear the click did anything...
+
+I'm guessing you guys just have super fast instances...",1400535217,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,Works for me. Tested in Firefox on latest master.,1400534635,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"**jgonera** wrote:
+
+Can't reproduce on latest master.",1400534422,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/FcXnAItk",1400532614,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+VisualEditor:  Special character inserter breaks up links to other pages,"Steps to Reproduce:
+1. Start with a link to another page, e.g., [[abc]].
+
+2. Use the special character inserter tool to add a special character, with the goal of producing something like this:  [[abc|aübc]].
+
+
+
+Actual Results:  
+Instead of [[abc|aübc]], you get [[abc|a]]ü[[abc|bc]].
+
+
+Reproducible: Always
+
+Reproduced in Firefox and Safari.  May be related to Bug 60476 about character formatting?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400521320,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jfbnqce7vgau7v3adje4,task_description,resolved
+VisualEditor:  Special character inserter breaks up links to other pages,"Yeah, merging this with bug 60476 and expanding the description there.
+
+*** This bug has been marked as a duplicate of bug 60476 ***",1400546427,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jfbnqce7vgau7v3adje4,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"I've been seeing this in the overnight runs of the browser tests in recent times. The build for VisualEditor will fail with a modal dialog that says ""Error loading data from server: readonly. The wiki is currently in read-only mode. Would you like to retry?""
+
+Here is an example from the overnight run Sunday 18 May: https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/512/testReport/(root)/VisualEditor/Edit_with_strings__outline_example_____Editing_with_%C3%84%C3%8B%C3%8F%C3%96%C3%9C___Editing_with_%C3%84%C3%8B%C3%8F%C3%96%C3%9C___/
+
+I can't think of any reason why beta labs would be in read-only mode late on a Sunday (PDT).  
+
+I suspect this may also be the cause of the occasional failure in other builds with less information, for example ""too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout)"" that we see in the MobileFrontend builds: too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/571/testReport/(root)/Check%20UI%20components/Check_existence_of_important_UI_components_on_other_pages_/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68349",1400509680,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_description,resolved
+beta labs mysteriously goes read-only overnight,"This seems to have been fixed by https://gerrit.wikimedia.org/r/#/c/149052/
+
+Thanks Sam!",1406300456,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,also see https://github.com/wikimedia/operations-mediawiki-config/commit/38990c671fd3b8d15f31a7c819e7bdd52ecef3ef,1406151403,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,Adding Sean Pringle.  This seems to be getting worse. I'd like to either update the db less often or else make it less disruptive.,1406151365,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,I saw this just now also.,1401826733,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"Antoine, would these messages be relevant?  They do not seem to happen at any particular interval but they might be correlated to the time at which Rummana saw the problem.  
+
+@deployment-bastion:/data/project/logs$ tail -f dberror.log 
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+Tue Jun 3 17:50:48 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 17:50:48 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+Tue Jun 3 19:20:48 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 19:20:48 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)",1401823647,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"Created attachment 15558
+Screenshot
+
+I have reproduced this issue today on Betalabs, attaching the screenshot
+
+**Attached**: {F14002}",1401820906,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"
+Right, and we know about the unexpected readonly status because it seems only VisualEditor displays that error in a javascript confirm modal dialog.  It might manifest in other ways that we would not see if not for the modal dialog that stops the test.",1401226061,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,FWIW VisualEditor doesn't know about <readonlytext> – it's just passing on what it gets from the API.,1401225595,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"On one SauceLab failure, it was POSTing to  ""http://en.wikipedia.beta.wmflabs.org/wiki/User:Selenium_user/firefox?vehidebetadialog=true&veaction=edit""
+
+The message:
+
+  The wiki is currently in read-only mode. Would you like to retry?
+
+Which comes from ApiBase::dieReadOnly(). That method seems to only be called when wfReadOnly() is true which is some legacy code that would let us create a file on the cluster that would disable edits entirely.
+
+There is like 0% change it is being triggered that way unless something mess with $wgReadOnly.  So most probably the i18n message is being reused by another path of code.",1401136491,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,Who could investigate this?,1401117229,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"If I recall correctly, this is something that can happen when things go sideways with the database. Not sure if that's what's going on here, but may be worth looking into.",1400627006,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,I think this is the first time I've seen the wiki read-only during the day (PDT) https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/4/testReport/(root)/Switching%20between%20wikitext%20and%20Visual%20Editor%20modes/Switch_editing_modes_via_toolbar/,1400626399,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+"VisualEditor: The ""Review changes"" button should be disabled when save dialog is locked during saving","It should be disabled/muted like we do in other cases.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400507340,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eibrrqabz54in23ld6jv,task_description,resolved
+"VisualEditor: The ""Review changes"" button should be disabled when save dialog is locked during saving","
+
+*** This bug has been marked as a duplicate of bug 65310 ***",1400507426,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eibrrqabz54in23ld6jv,task_subcomment,NA
+VisualEditor Mobile: Lock sign appearing over the Edit option on Mobile VE even if user has Beta and Experimental Mode on,"Screenshot
+
+I am getting this issue while trying to edit :https://en.m.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox
+
+I dont know how I stumbled upon it, but I can not edit my sandbox anymore with Mobile VE in any device/browser.
+
+However, if I add it to or remove it from my watchlist by tapping on star, only then the lock disappears from the edit icon and I can edit.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13821}",1400272200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6w4q2qazxtjqqz52eh5,task_description,declined
+VisualEditor Mobile: Lock sign appearing over the Edit option on Mobile VE even if user has Beta and Experimental Mode on,Probably a glitch in protection checking or something odd?,1401418027,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c6w4q2qazxtjqqz52eh5,task_subcomment,NA
+VisualEditor Mobile: Lock sign appearing over the Edit option on Mobile VE even if user has Beta and Experimental Mode on,"Works for me..
+https://en.m.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?mobileaction=alpha",1400522666,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-c6w4q2qazxtjqqz52eh5,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Load VE and switch to wikitext editor - triggers Validation error against schema MobileWebEditing: Missing property: funnel
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400195040,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-lryy7gpyx4cjl47ybghb,task_description,resolved
+EventLogging errors when switching from VisualEditor,Ignore above activity.,1401321316,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Change 135971 abandoned by Jdlrobson:
+Set funnel on VE
+
+https://gerrit.wikimedia.org/r/135971",1401321288,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Change 135971 had a related patch set uploaded by Jdlrobson:
+Set funnel on VE
+
+https://gerrit.wikimedia.org/r/135971",1401320995,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Change 134587 merged by jenkins-bot:
+Stop EventLogging errors when switching from VisualEditor to Editor
+
+https://gerrit.wikimedia.org/r/134587",1400858668,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Change 134587 had a related patch set uploaded by Jdlrobson:
+Stop EventLogging errors when switching from VisualEditor to Editor
+
+https://gerrit.wikimedia.org/r/134587",1400667848,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/NxeR9xyO",1400195109,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+VisualEditor: Opening a popupToolGroup should disable other tools,"Per the design mock-up at https://trello.com/c/xCo6uLAZ/9-5-references-dropdown-from-toolbar-styling (and a conversation with Kaity to confirm), when a user opens a popupToolGroup, all other tools in the toolbar should be disabled. Clicking off the popupToolGroup should close the popup and reactivate the other tools.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400193060,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-krpdp7rpaekkdslv6m5f,task_description,invalid
+VisualEditor: Opening a popupToolGroup should disable other tools,"After talking with Trevor and Kaity, we're going to punt this one for now.",1400272697,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-krpdp7rpaekkdslv6m5f,task_subcomment,NA
+VisualEditor not opening consistently in Firefox,"Steps to reproduce:
+
+1.  Be me, or one of several other people, but not James F.  (This step may be difficult to reproduce.  ;-)
+
+2.  Login on Firefox. 
+
+3.  Try to open an article in VisualEditor.
+
+4.  Wait.  Wait.  Wait.  Wonder why a page that pops open in Safari in less than five seconds still hasn't opened in Firefox despite the animated blue bar showing for more than 30 seconds now.
+
+5.  Wait.  Wait.  Wait.  Wonder if this is ever going to open.   
+
+6.  Give up and reload.  Maybe it works this time; maybe it doesn't.  If it doesn't, consider restarting Firefox.  That usually helps... for one article.  Then it goes back to its old behavior of occasionally opening a page, but not usually.
+
+
+I don't feel like I have a lot of useful information to give you, but this has been a problem for a couple of weeks and does not seem to be getting better.  Logging out may help, according to https://en.wikipedia.org/w/index.php?oldid=608667917#VE_does_not_start
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400181900,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gcadzjjnt6fiqkhy623y,task_description,invalid
+VisualEditor not opening consistently in Firefox,"Whatever this problem was, there are no reports of it any more, and it could not be reproduced, so I'm closing.",1513167765,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-gcadzjjnt6fiqkhy623y,task_subcomment,NA
+VisualEditor not opening consistently in Firefox,"""Storage error"" load.php:161
+""[Exception... ""Persistent storage maximum size reached""  code: ""1014"" nsresult: ""0x805303f6 (NS_ERROR_DOM_QUOTA_REACHED)""  location: ""<unknown>""]"" DOMException [NS_ERROR_DOM_QUOTA_REACHED: ""Persistent storage maximum size reached""
+code: 1014
+nsresult: 0x805303f6
+location: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20140626T181618Z:183] load.php:161
+
+""Storage error"" load.php:161
+""[Exception... ""Persistent storage maximum size reached""  code: ""1014"" nsresult: ""0x805303f6 (NS_ERROR_DOM_QUOTA_REACHED)""  location: ""<unknown>""]"" DOMException [NS_ERROR_DOM_QUOTA_REACHED: ""Persistent storage maximum size reached""
+code: 1014
+nsresult: 0x805303f6
+location: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20140626T181618Z:183]",1404176574,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gcadzjjnt6fiqkhy623y,task_subcomment,NA
+VisualEditor not opening consistently in Firefox,Are/were there any errors in the JS console at all?,1404174460,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gcadzjjnt6fiqkhy623y,task_subcomment,NA
+VisualEditor not opening consistently in Firefox,"I think this might have been solved for me, by removing one of Eran's scripts from common.js  However, another user who has reported the same problem isn't running that script.",1404173665,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gcadzjjnt6fiqkhy623y,task_subcomment,NA
+VisualEditor: The Advanced Settings opens up as a default tab for an image if that was the tab user opened for the last edited image,"Screenshot
+
+Steps to reproduced:
+
+1.Open a page with VE
+2.Insert an image and go to the advanced Settings to make some changes
+3.Apply the changes 
+4.Now insert another image and open the media settings for it
+
+Observed Result:
+Instead of starting from General Settings as default tab, it opens up the Advanced settings, moreover if you edited say the image size section of the last image, the scroll bar position for the newly added image is also at the same exact position.
+
+Test Environment:Betalabs, test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13579}",1400103600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vy4qb3tkuvo3pp2bvalh,task_description,declined
+VisualEditor: The Advanced Settings opens up as a default tab for an image if that was the tab user opened for the last edited image,Seems to have been fixed at some point.,1414094776,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vy4qb3tkuvo3pp2bvalh,task_subcomment,NA
+VisualEditor: The Advanced Settings opens up as a default tab for an image if that was the tab user opened for the last edited image,This sounds like a problem with BookletLayout. Trevor?,1400103732,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vy4qb3tkuvo3pp2bvalh,task_subcomment,NA
+Is it possible to set up VisualEditor on other skins instead of Vector skin?,"**Author:** `sean.chen`
+
+**Description:**
+hi,
+
+we are using MediaWiki for our intranet on Government of Ontario and we are amazed by the new and cool VisualEditor! And we want to set up VisualEditor while we upgrade our MediaWiki to version 1.23.x.
+
+However we need a customized skin instead of the default Vector skin. Is that possible to set up VisualEditor on a customized skin and how?
+
+thanks a lot,
+
+-Sean
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1400096640,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hebmh46ynxb5xtfcynmn,task_description,invalid
+Is it possible to set up VisualEditor on other skins instead of Vector skin?,"Also because this is for support, not an actual software issue, I have set it to resolved invalid.",1400097823,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hebmh46ynxb5xtfcynmn,task_subcomment,NA
+Is it possible to set up VisualEditor on other skins instead of Vector skin?,"Kind of relevant to this are my (WIP) notes on what VE expects of a skin, which you can find at bug 61500.",1400097722,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hebmh46ynxb5xtfcynmn,task_subcomment,NA
+Is it possible to set up VisualEditor on other skins instead of Vector skin?,"You can try setting $wgVisualEditorSupportedSkins[] = 'nameofyourskin'; in your configuration. If your skin is a derivative of one of the supported skins (vector, apex, monobook, minerva), this should come pretty close to making things work, with only a few CSS issues remaining. You can fix the CSS problems by copying and tweaking ve.init.mw.ViewPageTarget-vector.css and -vector-hd.css (or another one if your skin isn't based on Vector).
+
+Right now our skin integration is still a bit sucky. ve.init.mw.ViewPageTarget-shared.css needs to be loaded for all skins but isn't right now; I'll fix that. You also need to add your skin styles into VisualEditor.php itself (search for skinStyles), which is ugly. We'll need to work on improving that.
+
+In the meantime, feel free to pop into our IRC channel (#mediawiki-visualeditor on freenode) for interactive help.",1400097161,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hebmh46ynxb5xtfcynmn,task_subcomment,NA
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,"Steps to reproduce:
+
+1.Open a page with mobile VE
+
+Observed Result:
+
+The Cite option is appearing in the toolbar which is not supposed to be there just yet? The drop-down menu does not have any background layout.Clicking on any of the options make VE completely stuck
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400094420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_description,declined
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,This apparently was intentional. Now styled. :-),1401417868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_subcomment,NA
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,"The dropdown appears to be unstyled in the mobile skin. Also, the mobile CSS that removes all text labels everywhere is probably undesirable in this case (and seems like overkill in general; it should be a conscious choice).",1400195537,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_subcomment,NA
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,This is now appearing in production as well after today's deployment,1400191472,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_subcomment,NA
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,"Created attachment 15383
+Screenshot
+
+**Attached**: {F13527}",1400095261,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_subcomment,NA
+Raster icons missing from VE toolbar,"Toolbar with missing tool icons – undo, redo, all dropdown arrows, link, help, page notices, page options (several icons missing in the dropdowns too)
+
+If one forces VE to load with the raster icons, a bunch of them are missing.
+
+I'm not sure if this actually happens if any of the supported or greylisted browsers right now, but it blocks a fix for Opera 12 which doesn't handle elements with SVG background images and border-radius set.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14072}",1400005140,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_description,declined
+Raster icons missing from VE toolbar,"(In reply to Thiemo Mättig from comment #3)
+> (In reply to James Forrester from comment #2)
+> > We do not intend to load raster icons in VisualEditor.
+> 
+> You *do* load raster icons in VisualEditor.
+
+…
+
+> Are you planning to remove this feature?
+
+Yes, you're right, it was archaïc code we forgot to get rid of, and we should remove it. Done in gerrit 134758.",1400869128,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_subcomment,NA
+Raster icons missing from VE toolbar,"(In reply to James Forrester from comment #2)
+> We do not intend to load raster icons in VisualEditor.
+
+You *do* load raster icons in VisualEditor. Look:
+
+https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor/HEAD/modules%2Fve-mw%2Finit%2Fve.init.mw.Target.js
+https://git.wikimedia.org/tree/mediawiki%2Fextensions%2FVisualEditor/HEAD/modules%2Fve-mw%2Fui%2Fstyles
+https://git.wikimedia.org/tree/mediawiki%2Fextensions%2FVisualEditor/HEAD/modules%2Fve-mw%2Fui%2Fstyles%2Fimages%2Ficons
+
+Are you planning to remove this feature?",1400277284,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_subcomment,NA
+Raster icons missing from VE toolbar,We do not intend to load raster icons in VisualEditor.,1400009582,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_subcomment,NA
+Raster icons missing from VE toolbar,"Created attachment 15373
+Correctly rendered SVG toolbar
+
+(The Opera 12 fix I mentioned is Ieafeb9075f741fe6e2624c5c62cf2ea8138e63de.)
+
+**Attached**: {F14073}",1400005679,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_subcomment,NA
+VisualEditor: Scroll bar appears to be a bit wider on hovering over it in Firefox,"scroll bar gets wider
+
+Steps to reproduce:
+
+1.Open a page with VE in Firefox
+2.Open any drop down box which has a scroll bar in it
+3.Hover over the scroll bar
+
+Observed Result:
+The scroll bar becomes a bit wider 
+
+See the video attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13998}",1399926660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-m6ahh3o7wiecdy5522i5,task_description,invalid
+VisualEditor: Scroll bar appears to be a bit wider on hovering over it in Firefox,That's OS behaviour when it thinks you want to manually interact with the scrollbar.,1401417923,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m6ahh3o7wiecdy5522i5,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","Seen in automated tests in beta labs 11 May and 12 May (and occasionally earlier). 
+
+Browser encounters a modal dialog saying ""Error loading data from server: readonly. The wiki is currently in read-only mode. Would you like to retry?""  The wiki is almost certainly not in read-only mode. 
+
+This may not actually be a VE error, I think it's coming from line 337 of ve.init.mw.ViewPageTarget.js, but I haven't tracked it to whatever is feeding the ""read-only"" status message to VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399915500,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cqabqcw62xkqwgp5vzag,task_description,resolved
+"false ""wiki is read-only mode"" message in beta labs","It seems the main issue was the database lag that would cause MediaWiki to switch readonly.  The threshold has been raised a few months ago and I have not heard of ""beta is read only"" issues since.
+
+Assuming this bug is fixed.",1414160812,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","
+Several failed builds with this error over the last few days, this is the most recent from last night 13 May: 
+
+https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/500/",1399994801,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","There is a few errors such as:
+
+Mon May 12 5:32:25 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Mon May 12 5:32:25 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+
+
+Do you have an example of a failing build ? Will help find the exact time it happened and thus to investigate around that date/time.",1399986442,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","(11:08:16 AM) chrismcmahon: James_F:  I'm sure the read-only was not VE itself, but I do wonder if you've ever seen that msg. in VE or know what might cause it. 
+
+(11:09:16 AM) James_F: chrismcmahon: It happens locally when I lock the DB manually, and I've seen it when wikis are under high load in production due to the auto-lock.
+
+(11:09:31 AM) James_F: chrismcmahon: I believe it happens only in extremes, when master is lagging with load.
+
+(11:10:29 AM) chrismcmahon: James_F:  thanks, that's helpful, I've never seen that.  I can't imagine what would cause that kind of load in beta labs at that hour though.",1399918305,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","
+I've never seen this modal dialog or this error message under any circumstances other than when editing with VE. 
+
+I am curious as to the root cause though, I've never heard of a wiki automatically putting itself into read-only mode.",1399918007,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","Are you absolutely sure that Beta Labs wasn't catching up from too many edits? The site automatically puts itself into ""read only"" mode for a few seconds from time to time… Either way, this is a deployment-prep issue.",1399917099,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","Created attachment 15357
+read-only status modal dialog in VE
+
+**Attached**: {F13976}",1399915600,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again","Steps to Reproduce:
+1. Create a page that contains at least one image with no thumb or similar file specification, e.g., 
+
+[[File:Example.jpg|Here's an image.]]
+
+2. Open the page in VisualEditor.  
+
+3. Select the image and open the image inspector.
+
+4. Try to get out of the image inspector.
+
+Actual Results:  
+The ""Advanced settings"" pane in the image inspector has a spinning death spiral and the error message, ""Size values are invalid. Could not retrieve original file size."" 
+
+The X to close the image inspector does not respond.
+
+
+Reproducible: Always
+
+This was first reported by Magioladitis for the pdf's listed here:  https://el.wikipedia.org/w/index.php?oldid=4650532#.CE.94.CE.B9.CE.B1.CE.BB.CE.AD.CE.BE.CE.B5.CE.B9.CF.82
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399759500,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-7qyivx7mukqztl4bew6d,task_description,resolved
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again",Not exactly:  I selected it and pressed the Return key.  It has the same effect.,1399918730,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-7qyivx7mukqztl4bew6d,task_subcomment,NA
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again","Okay I just realized a huge bug: The image dialog popup/button doesn't appear (because it shouldn't yet) but double-clicking opens the media edit dialog.
+
+And since the image is inline, the dialog is not ready to handle it, the dialog then crashes.
+
+This seems to be a double-click bug; WhatamIdoing can you approve that this is how you opened the dialog?",1399914719,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-7qyivx7mukqztl4bew6d,task_subcomment,NA
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again","(In reply to Moriel Schottlender from comment #1)
+> This image is rendered as an inline image and the dialog, at the moment,
+> won't edit it at all. The editing capability for inline images is introduced
+> in the upcoming (big) change for the Image Model.
+> 
+> I've tried to reproduce the bug in both local master and in betalabs and the
+> image doesn't let me open the edit dialog (as expected)
+> 
+> See here:
+> http://en.wikipedia.beta.wmflabs.org/wiki/
+> 2014_May_11_TestImageBug?veaction=edit
+> 
+> Am I missing something?
+
+Double clicking the image opens the ""Media settings"" dialog for me.",1399914493,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-7qyivx7mukqztl4bew6d,task_subcomment,NA
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again","This image is rendered as an inline image and the dialog, at the moment, won't edit it at all. The editing capability for inline images is introduced in the upcoming (big) change for the Image Model.
+
+I've tried to reproduce the bug in both local master and in betalabs and the image doesn't let me open the edit dialog (as expected)
+
+See here: http://en.wikipedia.beta.wmflabs.org/wiki/2014_May_11_TestImageBug?veaction=edit
+
+Am I missing something?",1399914138,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-7qyivx7mukqztl4bew6d,task_subcomment,NA
+"VisualEditor:  Firefox displays new lists incorrectly, if you've just pasted the text onto the page","Steps to Reproduce:
+1. Type a few paragraphs of plain text in another document (e.g., an e-mail message with rich text turned off).
+
+2. Open VisualEditor.  Copy and paste your paragraphs into VisualEditor.
+
+3. Place your cursor in the first paragraph.  Click the list button to turn the first line (only) into a list.
+
+Actual Results:  
+The entire pasted section is indented as if it were a list (a list separated by <br>, not with a bullet in front of each paragraph).
+
+However, when you save the page, only the first paragraph has actually been turned into a list.
+
+See you at http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=92716&oldid=92715
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399489680,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-bxloupudebssszvcsfyv,task_description,declined
+"VisualEditor:  Firefox displays new lists incorrectly, if you've just pasted the text onto the page","Created attachment 15315
+Photo collage showing before-and-after difference in formatting
+
+**Attached**: {F14093}",1399492243,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-bxloupudebssszvcsfyv,task_subcomment,NA
+VisualEditor: The suggestion dropdown box gets stuck inside the transclusion dialog box in Firefox when you click on Add template button as soon as the dropdown box appears,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Type something in the textbox
+4.As soos as the suggestion dropdown box for template appears click on ""Add template"" button
+
+Observed Result:
+The first suggestion of the dropdown box gets stuck in the transclusion dialog box
+
+See the screenshot attached
+
+Browser:Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14019}",1399419540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6xcbbe4kcyhfokfy2ccf,task_description,declined
+VisualEditor: The suggestion dropdown box gets stuck inside the transclusion dialog box in Firefox when you click on Add template button as soon as the dropdown box appears,Can't reproduce,1414095454,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6xcbbe4kcyhfokfy2ccf,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,"In LocalSettings.php I enabled scary transclusions:
+$wgEnableAPI = true;
+$wgEnableWriteAPI = true;
+$wgEnableScaryTranscluding = true;
+$wgTranscludeCacheExpiry = 0;
+
+Then in a template I have this:
+{{raw:lo::{{{1}}}}}
+
+I see this in the log:
+[info][localhost:Test] starting parsing
+[warning/api][localhost:Test][oldid:306] Failed API request, 8 retries remaining.
+... and so on.
+
+If just {{raw:lo::someItem}} is on the page parsoid evaluates this OK. But when this is in a template the requests fail for some reason.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399359720,PHID-USER-6fjfcuicwjgrpuv3znmv,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_description,resolved
+Templates using interwiki transclusions fails at API request,"This works now, I do not know what have happend but works, with both prefixes I inserted in the db :)",1399660124,PHID-USER-6fjfcuicwjgrpuv3znmv,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,Can you try with {{raw:lowiki::xxx}} for prefix lo. Just a hunch.,1399579704,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,"Oh, yikes, I missed the ""interwiki"" in the subject line. Thanks for the clarification.",1399579499,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,"Sorry, {{raw:lo::xxx}} should transclude template xxx from wiki with prefix 'lo'. This is what I did:
+
+1) Create a template containing just plain text on a wiki (A).
+2) From another wiki (B), make sure you have scary transclusion enabled and the other wiki in the transclusion database.
+3) Make a template that transcludes the template from wiki A.
+4) Create a page at wiki B the template you created in step 3.",1399579335,PHID-USER-6fjfcuicwjgrpuv3znmv,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,"I'm having trouble reproducing this bug. Here's what I did:
+
+1) Create a template Template:Lo::someItem with the content: Hi
+2) Create a template Template:Another with the content: {{raw:lo::{{{1}}}}}
+3) Create a page Testing with the content: {{another|someItem}}
+
+Result on Testing is: Hi
+
+I can edit all of the above in VisualEditor.",1399578663,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+"VisualEditor:  Adding citations inside hieroglyphics, gallery, or mathematics blocks results in the inspector never closing","Intention:
+Add a citation inside (not after) a hieroglyphics block.
+
+Steps to Reproduce:
+1. Open page containing hieroglyphics.  Open hierglyphics tool.
+
+2. Open Citation tool (or Insert > Reference).  Add citation.  
+
+3. Close citation tool (""Apply changes"").
+
+
+
+Actual Results:  
+The refernce is correctly added, but the hieroglyphics inspector stays open and empty until you save the page.
+
+
+Reproducible: Always
+
+Bonus bug:
+
+Before saving page, try editing a nearby link, gallery, or math formula.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399321380,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lfivv2gwageaek5qpppw,task_description,resolved
+"VisualEditor:  Adding citations inside hieroglyphics, gallery, or mathematics blocks results in the inspector never closing","
+
+*** This bug has been marked as a duplicate of bug 56644 ***",1399333995,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lfivv2gwageaek5qpppw,task_subcomment,NA
+MathJax menus (in Math extension) are not localized into Vietnamese,"When MediaWiki's interface language is set to Vietnamese and MathJax rendering is turned on, the MathJax menus appear in English even though a Vietnamese localization is available. This issue does not occur when uselang=es etc.
+
+Steps to reproduce:
+
+1. Go to [[mw:Special:Preferences#mw-prefsection-rendering]] and turn on MathJax.
+2. Change the interface language to Vietnamese.
+3. Go to [[mw:User:Mxn/MathJax vi]] and right-click on the matrix.
+
+Expected results:
+
+The menus should all be translated, as they are at <https://github.com/mathjax/MathJax-i18n/tree/master/JSON/vi>.
+
+Actual results:
+
+All the menus are in English.
+
+Note that MathJax-i18n was missing entries in config.js for a number of languages, including Vietnamese, until very recently: <https://github.com/mathjax/MathJax-i18n/pull/1>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:Mxn/64809",1399157340,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_description,resolved
+MathJax menus (in Math extension) are not localized into Vietnamese,"**physik** wrote:
+
+OK. But it will be resolved by upgrading to MathJax 2.4. So it's the same problem
+
+%%%*** This bug has been marked as a duplicate of bug 70207 ***%%%",1413756495,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_subcomment,NA
+MathJax menus (in Math extension) are not localized into Vietnamese,"(In reply to physikerwelt from comment #2)
+> https://www.mediawiki.org/wiki/User:Mxn/64809?veaction=edit looks good for
+> me.
+
+This bug doesn't relate to VisualEditor. If I right-click on the matrix in [[mw:User:Mxn/64809]], the context menu is still in English, with items such as ""Show Math As"".",1413752347,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_subcomment,NA
+MathJax menus (in Math extension) are not localized into Vietnamese,"**physik** wrote:
+
+https://www.mediawiki.org/wiki/User:Mxn/64809?veaction=edit looks good for me.",1413748559,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_subcomment,NA
+MathJax menus (in Math extension) are not localized into Vietnamese,"As you mentioned, this is fixed upstream but not yet released -- the upcoming MathJax v2.4 will have the updated locale.",1399281849,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_subcomment,NA
+VisualEditor: Math inspector is not working in Betalabs,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert  a math function with math inspector
+
+Observed Result:
+Nothing gets added
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399055580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6cgiws4wsgspk77z65mb,task_description,declined
+VisualEditor: Math inspector is not working in Betalabs,This works for me… Maybe a caching issue?,1399079949,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6cgiws4wsgspk77z65mb,task_subcomment,NA
+"""VisualEditor language tool"" beta feature links on test2 are broken","https://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures
+
+Under ""VisualEditor language tool"", if I click discussion or information I get sent to https://test2.wikipedia.org/wiki/&lt;visualeditor-preference-experimental-info-link&gt; or https://test2.wikipedia.org/wiki/&lt;visualeditor-preference-experimental-discussion-link&gt;
+
+Localisation cache issue?
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**URL**: https://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures",1398992040,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-qjbo7xdeq7skmyh72eli,task_description,declined
+"""VisualEditor language tool"" beta feature links on test2 are broken","Links to https://www.mediawiki.org/wiki/VisualEditor/Beta_Features/Language and https://www.mediawiki.org/wiki/Talk:VisualEditor/Beta_Features/Language for me now.
+Closing as WORSKFORME (please reopen if still a problem).",1401709351,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-qjbo7xdeq7skmyh72eli,task_subcomment,NA
+VisualEditor:  You shouldn't be able to set bold or other text attributes for ref tags,"Steps to Reproduce:
+1.  Select a ref tag.
+
+2.  Click on bold in the character formatting menu.
+
+
+
+Actual Results:  
+It dutifully adds the character formatting:  <ref>Foo</ref> becomes '''<ref>Foo</ref>'''
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=91700&oldid=91692
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1398979980,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jx5wa6pf2qanvuyvggpu,task_description,invalid
+VisualEditor:  You shouldn't be able to set bold or other text attributes for ref tags,"If it's ""valid"", then why doesn't it do anything?  
+
+'''<ref>Foo</ref>''' doesn't actually produce a bold-faced [1].
+
+I see your point about (b) but you can't see the existence of the misplaced bold in VisualEditor, so I doubt that anyone would actually use it to fix it.",1399237665,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jx5wa6pf2qanvuyvggpu,task_subcomment,NA
+VisualEditor:  You shouldn't be able to set bold or other text attributes for ref tags,"Why not? This is entirely valid, and relatively common, wikitext… VE has to let you make all kinds of stupid stylistic errors, because (a) it's our job to let you do anything you can validly do in wikitext, and (b) you might want to use VE to correct such things, which stripping in VE would prevent.",1399080407,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jx5wa6pf2qanvuyvggpu,task_subcomment,NA
+VisualEditor:  You shouldn't be able to set bold or other text attributes for ref tags,"It's not just refs:  templates, hieroglyphics, galleries, math equation... Not images, though.
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=91706&oldid=91700",1398980268,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jx5wa6pf2qanvuyvggpu,task_subcomment,NA
+VisualEditor Mobile: Mobile VE is redirecting to Google while trying to save a page,"For Chrome
+
+Steps to reproduce:
+
+1.Open this link:https://test2.m.wikipedia.org/wiki/0.8863089695452125?title=0.8863089695452125&campaign=random#editor/0
+
+2.Make some edit
+
+3.Save the page
+
+Observed Result:
+
+In Chrome: The page suddenly disappears and redirects me to Google Search Page 
+In FireFox: It keeps the VE edit mode open 
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13949}",1398901080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rwiwk6z77szqe2xi53tu,task_description,resolved
+VisualEditor Mobile: Mobile VE is redirecting to Google while trying to save a page,"
+
+*** This bug has been marked as a duplicate of bug 60848 ***",1398908742,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-rwiwk6z77szqe2xi53tu,task_subcomment,NA
+VisualEditor Mobile: Mobile VE is redirecting to Google while trying to save a page,"Created attachment 15260
+for Firefox
+
+**Attached**: {F13950}",1398901148,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rwiwk6z77szqe2xi53tu,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Right now, if you switch to alpha mode and click the edit button on a page like...
+https://en.m.wikipedia.org/wiki/User_talk:Kaldari
+...you get an error since VisualEditor is disabled for that namespace on en.wiki.
+
+To fix this, we need to surface the config settings in wmgVisualEditorNamespaces on the client-side and use it in the editor loading process in editor.js.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398892320,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-aaldjasjdqcsgs4dgei6,task_description,resolved
+Don't try to load VisualEditor in namespaces where it isn't supported,"Change 132124 merged by jenkins-bot:
+Only create editor switcher from wikitext editor if VE is usable
+
+https://gerrit.wikimedia.org/r/132124",1399507171,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Change 132124 had a related patch set uploaded by Kaldari:
+Only create editor switcher from wikitext editor if VE is usable
+
+https://gerrit.wikimedia.org/r/132124",1399504025,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Change 130794 merged by jenkins-bot:
+Make sure mobile VisualEditor is only loaded when appropriate
+
+https://gerrit.wikimedia.org/r/130794",1398985053,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Change 130794 had a related patch set uploaded by Kaldari:
+Make sure mobile VisualEditor is only loaded when appropriate
+
+https://gerrit.wikimedia.org/r/130794",1398903985,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Looks like the information is already available on the client-side:
+mw.config.get( 'wgVisualEditorConfig' ).namespaces",1398893246,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/cZTY61hQ",1398892516,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+VisualEditor: Inserting Media fails when caret is not positioned after initialization,"Original bug title:
+VisualEditor: Inserting Media fails when caret is not positioned after initialization
+
+And this is how to reproduce the issue:
+* Go to https://www.mediawiki.org/wiki/Sandbox?veaction=edit
+* Confirm the ""This is our new tool ....""
+* Reload the page
+* Press ""Insert""
+* Press ""Media"" (dialog opens)
+* Click one of the images.
+
+Result:
+Mozilla Firefox:
+* POST https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 281ms]
+** http://pastebin.de/124264
+* TypeError: splice is undefined load.php:153
+** http://pastebin.de/124263
+* Nothing happens except that the dialog is closed.
+* Pressing ""Insert"" -> ""Media"" now does not open any dialog
+
+Opera Next:
+* Uncaught TypeError: Cannot read property 'apply' of undefined VM140:146
+* Nothing happens except that the dialog is closed.
+* Pressing ""Insert"" -> ""Media"" now does not open any dialog
+* Stacktrace: http://pastebin.de/124262
+
+--------------
+Expected:
+* Image inserted
+* Being able to add further images to the page
+
+--------------
+Unrelated question:
+* Why are you using FormData for this specific request?
+
+
+
+--------------
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64759",1398776460,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-rtprhlspp44bc3deup2j,task_description,resolved
+VisualEditor: Inserting Media fails when caret is not positioned after initialization,"
+
+*** This bug has been marked as a duplicate of bug 64434 ***",1399065928,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rtprhlspp44bc3deup2j,task_subcomment,NA
+VisualEditor: Have redirected links in green at the edit mode,"In VisualEditor When we are at the edit mode it doesn't show redirected internal links in green.
+
+It can be as an option in top tool box or in setting part
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398748440,PHID-USER-dswbdv7ibhsefllcqarz,PHID-TASK-r5dtguf5lpskmwirqnjk,task_description,resolved
+VisualEditor: Have redirected links in green at the edit mode,"VisualEditor is designed to look like the read mode; having redirects as green for read mode is bug 166, and making VE copy them if they change is bug 61072, so merging with that.
+
+*** This bug has been marked as a duplicate of bug 61072 ***",1401417534,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r5dtguf5lpskmwirqnjk,task_subcomment,NA
+VisualEditor:  Math formula does not display correctly if preferences are set to both TeX and MathJax,"Steps to Reproduce:
+1. Enable VisualEditor formulae editing at Special:Preferences#mw-prefsection-betafeatures.
+
+2. Change math-related preferences to:
+   * Leave it as TeX (for text browsers) (radio button; it's off by default)
+   * MathJax (experimental; best for most browsers) (tick box; it's off by default)
+
+3. Open a page like [[:w:Torque]] in VisualEditor.
+
+4. Select a math formula from the page.
+
+5. Open the math editing tool.
+
+6. Change some thing in the formula (e.g., replace ""alpha"" with ""beta"").
+
+7. Look at the mess in the new version of the math formula (the one on the page, not the TeX code in the editing tool).
+
+
+
+Reproducible: Always
+
+See screenshots here:
+
+https://en.wikipedia.org/wiki/File:Bug_with_using_VE_and_mathjax.png
+
+https://commons.wikimedia.org/wiki/File:MathJax_mess_2014-04-28_at_2.33.08_PM.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398721500,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-i2hkjs3uujagjhxf5ecx,task_description,resolved
+VisualEditor:  Math formula does not display correctly if preferences are set to both TeX and MathJax,"
+
+*** This bug has been marked as a duplicate of bug 60728 ***",1402295506,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i2hkjs3uujagjhxf5ecx,task_subcomment,NA
+VisualEditor:  Math formula does not display correctly if preferences are set to both TeX and MathJax,"The CSS problem is caused by this rule
+
+.ve-ce-protectedNode, .ve-ce-protectedNode * {
+  position: relative !important;
+  top: 0 !important;
+  left: 0 !important;
+  bottom: 0 !important;
+  right: 0 !important;
+  ...
+}
+
+MathJax makes heavy use of absolute positioning with elements like 
+
+<span style=""font-family: MathJax_Size4; position: absolute; top: -1.624em; left: 0.003em;"">⎜<span style=""display: inline-block; width: 0px; height: 3.975em;""></span></span>
+
+so the .ve-ce-protectedNode CSS overrides all the positioning creating the mess.",1398752231,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-i2hkjs3uujagjhxf5ecx,task_subcomment,NA
+VisualEditor:  Math formula does not display correctly if preferences are set to both TeX and MathJax,"See https://en.wikipedia.org/w/index.php?oldid=606239634#Problem_with_MathJax_and_visual_editor. for an analysis of CSS-related issues.  MathJax uses absolute positioning, and VisualEditor uses relative positioning.",1398721663,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-i2hkjs3uujagjhxf5ecx,task_subcomment,NA
+VisualEditor: Pressing Return at the end of the document throws  Error: Offset could not be translated to a DOM element and offset: 675,"Screenshot
+
+Steps to reproduce:
+
+
+1.Go to the last line of this page:http://en.wikipedia.beta.wmflabs.org/wiki/28thAprilChrome?veaction=edit
+
+2.Press return
+
+Observed Result:
+
+An error appears in the console:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 675 
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13655}",1398716100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j2ivwzlbwna3s5gipwur,task_description,resolved
+VisualEditor: Pressing Return at the end of the document throws  Error: Offset could not be translated to a DOM element and offset: 675,Re-checked the page and the test scenario - no errors displayed in Console; Save button works as expected. Closing the issue as resolved.,1425602082,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-j2ivwzlbwna3s5gipwur,task_subcomment,NA
+VisualEditor: Pressing Return at the end of the document throws  Error: Offset could not be translated to a DOM element and offset: 675,"After the above steps if you click on ""Save Page"" dialog box and close it.
+Then again try to click on ""Save Page"" button it does not do anything.",1398717091,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j2ivwzlbwna3s5gipwur,task_subcomment,NA
+VisualEditor: PHP Notice on undefined index,"Patch for php notice
+
+PHP Notice:  Undefined index: visualeditor-enable-language in extensions/VisualEditor/VisualEditor.hooks.php on line 402
+
+Attaching patch since I can't submit to gerrit from here.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13607}",1398698640,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-nxkrip2qpu45o4qn32qd,task_description,resolved
+VisualEditor: PHP Notice on undefined index,Fixed in gerrit 130496.,1399082873,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nxkrip2qpu45o4qn32qd,task_subcomment,NA
+VisualEditor:  Cutting and pasting an {{essay}} template (containing shortcuts) resulted in a different template displaying,"Intention:
+Move a tag from the middle of a page to the top.
+
+Steps to Reproduce:
+See https://en.wikipedia.org/w/index.php?title=User:WhatamIdoing/Sandbox_3&diff=606088818&oldid=606088072 for the (entirely correct) diff.
+
+1. Select the essay tag in the middle of the page.
+
+2. Command-X to cut it.
+
+3. Scroll to the top.  Place cursor in the slug at the top.  Command-V to paste it.
+
+
+Actual Results:  
+The template that was displayed (upon pasting) does not look like the template that was cut.  It showed a ""clean up"" broom.
+
+The changes to the wikitext (upon saving) were correct, and the template displayed correctly upon refresh (after saving).
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1398633600,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qc5trqqgz5vloi4oqng6,task_description,resolved
+VisualEditor:  Cutting and pasting an {{essay}} template (containing shortcuts) resulted in a different template displaying,"Created attachment 15227
+The essay tag (the top one) as it should have appeared upon pasting, and as it did appear after saving the page.
+
+**Attached**: {F13515}",1398633763,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qc5trqqgz5vloi4oqng6,task_subcomment,NA
+VisualEditor:  Cutting and pasting an {{essay}} template (containing shortcuts) resulted in a different template displaying,"Created attachment 15226
+The essay tag, pasted at the top.  It does not look like what I cut from the middle.
+
+**Attached**: {F13514}",1398633728,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qc5trqqgz5vloi4oqng6,task_subcomment,NA
+VisualEditor:  Cutting and pasting an {{essay}} template (containing shortcuts) resulted in a different template displaying,"Created attachment 15225
+The essay tag, as seen originally in the middle of the page
+
+**Attached**: {F13513}",1398633681,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qc5trqqgz5vloi4oqng6,task_subcomment,NA
+VisualEditor won't start - With correct config,"**Author:** `petter.viippola`
+
+**Description:**
+I've done these steps and VisualEditor still dosen't work. There seems to be a problem with loading VisualEditor. I can only edit source, the command edit isn't possible to use. I've removed all the Parsoid options.
+
+cd extensions
+git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git  
+cd VisualEditor
+git submodule update --init
+
+require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");
+
+$wgDefaultUserOptions['visualeditor-enable'] = 1;
+ 
+
+$wgHiddenPrefs[] = 'visualeditor-enable';
+
+Everything else seems to be working the wiki, with got it ad-connected. Can there be any issues regarding to that?
+
+Best regards
+Petter
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Linux
+**Platform**: PC",1398424980,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_description,declined
+VisualEditor won't start - With correct config,Did this issue get resolved? I'm tempted to mark these sorts of entries as resolved worksforme.,1414808894,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor won't start - With correct config,"**petter.viippola** wrote:
+
+We are getting some other strange errors if we try with chrome on a testclient.
+server:parsoidserver-http-curl-error: couldn't connect to host.
+
+Does this mean we have the wrong configuration in the localsettings.js file?
+
+Best regards
+Petter",1398781795,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor won't start - With correct config,"**petter.viippola** wrote:
+
+[Mon Apr 28 14:39:36 2014] [error] [client 10.1.101.39] PHP Notice:  Undefined index: visualeditor-enable-language in /var/www/mediawiki-1.22.5/extensions/VisualEditor/VisualEditor.hooks.php on line 402, referer:http://wiki.ad.xxxxxx.se/index.php?title=SpaceClaim&action=edit
+
+This is the only error we get in the httpd, error.log.
+
+Best Regards
+
+Petter",1398696608,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor won't start - With correct config,"**petter.viippola** wrote:
+
+I can look tomorrow when i get back to work.
+
+The logs dosen't give any intresseting entries about problems with loading the VisualEditor.
+There is no errors when i open a page, log in et.c. That's the strange part.
+
+We have tried with chrome/""the wrong ie8"". I noticted it wasn't supported by IE, so we tried chrome but it was the same result.
+
+Best Regards
+
+Petter",1398627888,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor won't start - With correct config,"Does VisualEditor show up on Special:Version?
+
+If no, are there entries in your PHP error logs on the server?
+
+If yes, are there errors in your JS console on your client when you open a page?
+
+(What browser are you using? Note that Internet Explorer and a number of other elderly browser versions don't work with VisualEditor yet.)",1398471355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot read property 'nodeType' of undefined appears while trying to add a newline after clicking on Edit Beta for Page Title heading,"screenshot
+
+Steps to Reproduce:
+
+1.Go to this page: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit
+
+2.Click on Edit beta for the Page Title
+
+3.Now press return after any line to add a new line in the page
+
+Observed Result:
+
+An error appears in the console:
+Uncaught TypeError: Cannot read property 'nodeType' of undefined 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&oldid=605655480
+
+**Attached**: {F13859}",1398372300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iro4l3sspq3bi2nblqmz,task_description,declined
+VisualEditor: Uncaught TypeError: Cannot read property 'nodeType' of undefined appears while trying to add a newline after clicking on Edit Beta for Page Title heading,This now works for me – deployment glitch?,1399083059,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iro4l3sspq3bi2nblqmz,task_subcomment,NA
+"VisualEditor:  ""Unknown error"" corrupts page upon saving, but saving again fixes the problems it created","Actual Results:  
+TeamGale added some citations and then saved the page.  She received an ""unknown error"" and assumed that the page did not get saved.  So she saved the page again.  Upon checking the history, she found that both attempts to save the page had resulted in a new version:
+
+https://en.wikipedia.org/w/index.php?title=Sakis_Rouvas&diff=605148987&oldid=605133988
+
+https://en.wikipedia.org/w/index.php?title=Sakis_Rouvas&diff=605149076&oldid=605148987
+
+However, the first diff removed the end of the page, including the reference secyion, external links, navboxes, succession boxes, categories, and more.  These were automagically restored when she saved the second time.
+
+
+Reproducible: Didn't try
+
+TeamGale usually edits with Firefox 28 on Windows 8.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398359400,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-227untois7bfweaz7mct,task_description,resolved
+"VisualEditor:  ""Unknown error"" corrupts page upon saving, but saving again fixes the problems it created",Provisionally marking this as 'Resolved' as no reported recurrences in two years.,1459666953,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-227untois7bfweaz7mct,task_subcomment,NA
+VisualEditor-doc-publish jobs are failing,"See for example https://integration.wikimedia.org/ci/job/mwext-VisualEditor-doc-publish/2336/console from https://gerrit.wikimedia.org/r/#/c/129372/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1398327960,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-vbe43kp33h3r5mdxnudc,task_description,resolved
+VisualEditor-doc-publish jobs are failing,Job is now passing: https://integration.wikimedia.org/ci/job/mwext-VisualEditor-doc-publish/2337/console,1398342116,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vbe43kp33h3r5mdxnudc,task_subcomment,NA
+VisualEditor-doc-publish jobs are failing,"Change 129401 merged by jenkins-bot:
+Revert ""mwext-VisualEditor-doc-publish: Simplify rsync calls""
+
+https://gerrit.wikimedia.org/r/129401",1398342097,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vbe43kp33h3r5mdxnudc,task_subcomment,NA
+VisualEditor-doc-publish jobs are failing,"Change 129401 had a related patch set uploaded by Hashar:
+Revert ""mwext-VisualEditor-doc-publish: Simplify rsync calls""
+
+https://gerrit.wikimedia.org/r/129401",1398341788,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vbe43kp33h3r5mdxnudc,task_subcomment,NA
+VisualEditor-doc-publish jobs are failing,"Caused by https://gerrit.wikimedia.org/r/#/c/125546/2/mediawiki-extensions.yaml,unified which uses a a dest dir:  $$WORKSPACE/docs/lib  :-D",1398341642,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vbe43kp33h3r5mdxnudc,task_subcomment,NA
+"VisualEditor: The default size is not getting applied on an image after clicking on ""Apply Changes""","Steps to reproduce:
+
+1.Go to this page:https://test2.wikipedia.org/w/index.php?title=22ndaprilFF&veaction=edit
+
+2.Select the image:""K"" which is now in 220x200 px size
+
+3.Now go to Advanced Settings and select the tab ""Default"" and click on ""Apply changes""
+
+Observed Result:
+It turns the image into full size 600x600 px
+
+Also,
+If you first make the image as full size, then click on default size and click on ""Apply Changes"" nothing happens
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398277140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u6jklhcw662pkjycjvtd,task_description,invalid
+"VisualEditor: The default size is not getting applied on an image after clicking on ""Apply Changes""",Agreed; basic images have a default size of full size.,1401213398,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u6jklhcw662pkjycjvtd,task_subcomment,NA
+"VisualEditor: The default size is not getting applied on an image after clicking on ""Apply Changes""","Yes, it turns the image to 600x600 because it's the image's original dimensions, which are considered ""default"" for image of the type ""basic"".
+
+This is intended behavior.",1398278613,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-u6jklhcw662pkjycjvtd,task_subcomment,NA
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Edit something
+3.Save the page
+4.Without scrolling the page, again reopen the VE for that page
+
+Observed Result:
+
+""Success! Your edit was saved"" message stays in the VE mode .
+
+See the screenshot too
+
+Test Environment: https://test2.m.wikipedia.org/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13581}",1398213660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2vhxquft7zgsd3wwscky,task_description,resolved
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","Change 130782 merged by jenkins-bot:
+Close drawers/toasts on a click event
+
+https://gerrit.wikimedia.org/r/130782",1399336225,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2vhxquft7zgsd3wwscky,task_subcomment,NA
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","Change 130782 had a related patch set uploaded by Jdlrobson:
+Close toasts on a click event
+
+https://gerrit.wikimedia.org/r/130782",1398902609,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2vhxquft7zgsd3wwscky,task_subcomment,NA
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1958",1398279610,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2vhxquft7zgsd3wwscky,task_subcomment,NA
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","We should probably dismiss this message when the user opens VE again.
+
+Sounds like this code is in MobileFrontend.",1398279558,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2vhxquft7zgsd3wwscky,task_subcomment,NA
+Not getting any result for VisualEditor media search in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Type something on the search box to search for a media
+
+
+Observed Result:
+No search results for images appears in the dialog
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13537}",1398192600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ycn3ic72wlfp37rtzxzr,task_description,resolved
+Not getting any result for VisualEditor media search in Betalabs,"(In reply to Alex Monk from comment #2)
+> Hmm... Reminds me of bug 63989
+
+No, this was a deployment issue with the Beta Labs move.",1398280580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ycn3ic72wlfp37rtzxzr,task_subcomment,NA
+Not getting any result for VisualEditor media search in Betalabs,Hmm... Reminds me of bug 63989,1398276745,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ycn3ic72wlfp37rtzxzr,task_subcomment,NA
+Not getting any result for VisualEditor media search in Betalabs,This is now fixed .I am getting search results for the media now,1398274843,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ycn3ic72wlfp37rtzxzr,task_subcomment,NA
+VisualEditor: Can't save after editing categories,"It just happened to me on both Chrome and FF, Win 7, Vector. 
+If I remove a category on it.wp, that's not considered as a change? The Save button stays grey. I need to type something and then delete it in order to be able to save my edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398173340,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6nnrbmhm34zvreojlgpl,task_description,declined
+VisualEditor: Can't save after editing categories,At least provisionally…,1406320242,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6nnrbmhm34zvreojlgpl,task_subcomment,NA
+VisualEditor: Can't save after editing categories,Can you still not reproduce this issue? Maybe this should be marked worksforme.,1406315448,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6nnrbmhm34zvreojlgpl,task_subcomment,NA
+VisualEditor: Can't save after editing categories,"Yes. Although as of now, I can't reproduce this issue, so I'm bringing it back to unconfirmed.",1398246189,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6nnrbmhm34zvreojlgpl,task_subcomment,NA
+VisualEditor: Can't save after editing categories,"Once you do type something and delete it, does the category get removed in the edit?",1398199599,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6nnrbmhm34zvreojlgpl,task_subcomment,NA
+VisualEditor: VE should have a toolbar icon for cut-copy-paste,"Right now, we have cut-copy-paste feature in VE but there is no icon for these Clipboard actions.
+It would be nice to have them on the toolbar as it is a pretty good feature with no visual indication that it exists.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398119700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wqkvsiwaq4pnd2lugivq,task_description,declined
+VisualEditor: VE should have a toolbar icon for cut-copy-paste,"WONTFIXing, but really this is CANTFIX, sadly.",1398124464,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wqkvsiwaq4pnd2lugivq,task_subcomment,NA
+VisualEditor: VE should have a toolbar icon for cut-copy-paste,Google Docs shows that message in non-Chrome browsers. In Chrome browsers it asks you to install a plugin. Basically this is impossible due to the (fairly sensible) browser security model.,1398120899,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqkvsiwaq4pnd2lugivq,task_subcomment,NA
+VisualEditor: VE should have a toolbar icon for cut-copy-paste,"Triggering a cut/copy/paste from JavaScript might be hard due to security restrictions :( . Google Docs, for instance, has cut/copy/paste actions in the edit menu, but if you try to use them you get a dialog that says ""these actions are unavailable via the Edit menu, but you can still use Ctrl+X / Ctrl+C / Ctrl+V"".
+
+We might be able to do this using execCommand though, but I don't know how well that works and how reliable it is. CC Ed because he's done a bunch of work on contentEditable copy/paste in the past so he might know more.",1398120066,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wqkvsiwaq4pnd2lugivq,task_subcomment,NA
+VisualEditor: Citation dialog does not focus correct field when adding parameter,"In the template dialog, when you add a parameter, that parameter's input field is then focused. This makes perfect sense. In the citation dialog, this doesn't happen, and instead the input field that was focused most recently is focused.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398112620,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ocb7ebf4v6bjoboovjt4,task_description,resolved
+VisualEditor: Citation dialog does not focus correct field when adding parameter,"
+
+*** This bug has been marked as a duplicate of bug 64098 ***",1398112734,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ocb7ebf4v6bjoboovjt4,task_subcomment,NA
+"VisualEditor: Cite Options dialog has ""Show Options"" button enabled when it is inside Reference Dialog box but not when they are added in Main CE or inside Media Settings dialog","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Cite> Website/Book/Newspaper/Journal 
+3.Observe that, Cite Options dialog does not have ""Show Options"" button
+4.Now open a reference dialog box and Go to Cite>Cite> Website/Book/Newspaper/Journal
+
+Observed Result:
+In this case, there is a ""Show Options"" button for Cite options
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/21staprilchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14020}",1398105780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qcrmoxueaa23emzyho3c,task_description,declined
+"VisualEditor: Cite Options dialog has ""Show Options"" button enabled when it is inside Reference Dialog box but not when they are added in Main CE or inside Media Settings dialog","This is pretty much intentional; citation templates that aren't the only thing in a reference (or aren't even in a reference) get the citation icon, but aren't ""real"" citations. For now I'm WONTFIXing this.",1398113113,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qcrmoxueaa23emzyho3c,task_subcomment,NA
+VisualEditor cut off last several characters of article text during two edits at pl.wp,"VisualEditor cut off last several characters of article text during two edits at pl.wp.
+
+https://pl.wikipedia.org/w/index.php?diff=39198236
+https://pl.wikipedia.org/w/index.php?diff=39246345
+
+These are two consecutive edits to the same article, [[pl:Lamborghini Aventador]].
+
+Content maiming → marking as 'major'.
+
+Originally reported at https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Lamborghini_Aventador_-_ko.C5.84cowe_znaki by WTM.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398083820,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6ronffn6fe4mqkisco3e,task_description,resolved
+VisualEditor cut off last several characters of article text during two edits at pl.wp,Can't reproduce. Reopen if you can.,1437686737,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-6ronffn6fe4mqkisco3e,task_subcomment,NA
+font-size in VisualEditor is smaller than view mode,"It seems typography refresh enlarged body font size but VE didn't follow this change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397885100,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ogvz5uh6cxjgnxeelh7e,task_description,resolved
+font-size in VisualEditor is smaller than view mode,"
+
+*** This bug has been marked as a duplicate of bug 63985 ***",1397903906,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-ogvz5uh6cxjgnxeelh7e,task_subcomment,NA
+VisualEditor:  Re-used references don't always match,"Intention:
+Remove a copyright violation
+
+Steps to Reproduce:
+I removed the first instance of a ref tag.  See https://en.wikipedia.org/w/index.php?title=Male_rape&diff=604793477&oldid=604792987
+
+
+Actual Results:  
+The re-used ref was ""moved"", but that had the effect of changing it, because the next instance of the same named ref had a different description.
+
+
+Reproducible: Didn't try
+
+I don't know how to solve this.  The wikitext shouldn't have been written that way in the first place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1397856060,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-d2r6gtoaqlgf6litoxhf,task_description,declined
+VisualEditor:  Re-used references don't always match,"(In reply to WhatamIdoing from comment #2)
+> There's no way for VisualEditor to know which is the ""right"" ref when two
+> refs have the same name but different content.  I've seen this occasionally,
+> and the ""mismatched"" refs sometimes have functionally the same content
+> (e.g., one with a typo or abbreviation not present in the other).
+> 
+> We could pop up an message about the error in the wikitext (which is
+> probably something that should be done by MediaWiki, not VisualEditor).  In
+> VisualEditor, we could rename the refs to force them to be separated.   Or
+> we could do nothing, and maintain bug-for-bug compatibility with Cite.php's
+> lack of internal checking.
+
+See bug 66233 for warning/stopping the user in Cite.php for this and other issues.",1402341486,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d2r6gtoaqlgf6litoxhf,task_subcomment,NA
+VisualEditor:  Re-used references don't always match,"There's no way for VisualEditor to know which is the ""right"" ref when two refs have the same name but different content.  I've seen this occasionally, and the ""mismatched"" refs sometimes have functionally the same content (e.g., one with a typo or abbreviation not present in the other).
+
+We could pop up an message about the error in the wikitext (which is probably something that should be done by MediaWiki, not VisualEditor).  In VisualEditor, we could rename the refs to force them to be separated.   Or we could do nothing, and maintain bug-for-bug compatibility with Cite.php's lack of internal checking.",1402341362,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-d2r6gtoaqlgf6litoxhf,task_subcomment,NA
+VisualEditor:  Re-used references don't always match,"I'm pretty sure this is a WONTFIX; if the wikitext is in such a broken state that it defines a reference twice, there's nothing sane that VisualEditor can really do.",1402332059,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d2r6gtoaqlgf6litoxhf,task_subcomment,NA
+VisualEditor:Wrapping is not working properly for Reference numbers in reflist as it gets overlapped by a left aligned image,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a image
+3.Add some content in the page
+4.Add some references
+5.Make the image left aligned
+6.Add a reflist in a way so that the references in that list is to the right of the image
+7.Save the page
+
+Observed result:
+
+Reference numbers in reflist are getting overlapped by the image
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13726}",1397770740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xctt6gf3mq7aojdrpzna,task_description,invalid
+VisualEditor:Wrapping is not working properly for Reference numbers in reflist as it gets overlapped by a left aligned image,"Not a VE issue, happens in read mode too.
+
+(That should be fixed though)",1401323215,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xctt6gf3mq7aojdrpzna,task_subcomment,NA
+VisualEditor: crashing when trying to save a reference?,"An IP user at sv.wp reports this (GoogleTranslated):
+In Ubuntu 10.13 crashes Firefox when I want to save a source.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux",1397642280,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lq26x5df5b2uayf5w4sb,task_description,declined
+VisualEditor: crashing when trying to save a reference?,Insufficient information to triage.,1414624719,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lq26x5df5b2uayf5w4sb,task_subcomment,NA
+"'Insert Media' in VE fails to search local repo, returns blank.","**Author:** `tech`
+
+**Description:**
+Running an up-to-date VisualEditor extension and parsoid server on mediawiki-1.22.2, when I use 'Insert Media' no matter the search term (exact filenames are no better) nothing is returned.
+
+Checking server logs and debugging client browser data shows that VE only goes as far as a call to the API 'api.php?format=json&action=query&meta=filerepoinfo' which returns:
+
+{
+  query: {
+    repos: [
+      {
+        name: ""local"",
+        displayname: null,
+        rootUrl: ""/images"",
+        local: true
+      }
+    ]
+  }
+}
+
+There are no further queries to the API after this call.
+
+I can add wikiCommons, with ""$wgUseInstantCommons = true"", which successfully searches the wikiCommons, but has no effect on local media.
+
+I can manually add media with the standard editor and the [[File:image.ext]] syntax, but if I double click a previously attached image in VE all of the fields in the media dialog box are vacant and I can't change any values or even close the dialog.
+
+A query of 'api.php?action=query&list=allimages&format=json' returns a complete set of media as expected.
+
+Further, looking at the API documentation on the server the example listed for filerepoinfo is 'api.php?action=query&meta=filerepoinfo&friprop=apiurl|name|displayname', but it returns in the warnings field: ""Unrecognized value for parameter 'friprop': apiurl"". Suggesting that perhaps a variable in LocalSettings.php is missing or inaccurate, I've looked over this several times, but don't see any glaring issues.
+
+The server in question is behind an intranet, but I'm happy to answer any questions.
+
+Thanks,
+Patrick
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux",1397627580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sizovmscvvm6rifym437,task_description,invalid
+"'Insert Media' in VE fails to search local repo, returns blank.","(In reply to Patrick King from comment #0)
+> Running an up-to-date VisualEditor extension and parsoid server on
+> mediawiki-1.22.2, when I use 'Insert Media' no matter the search term (exact
+> filenames are no better) nothing is returned.
+
+Sorry, I completely missed the bit of your question asking about MediaWiki 1.22 – for media search to work, VisualEditor requires APIs that were introduced in MediaWiki 1.23. Indeed, the code intentionally asserts that you are running the right version of MediaWiki to avoid these issues.
+
+For comparison, my local repo (running 1.24 alpha) comes out with:
+
+{
+    ""query"": {
+        ""repos"": [
+            {
+                ""name"": ""local"",
+                ""displayname"": ""devwiki"",
+                ""rootUrl"": ""/images"",
+                ""local"": true,
+                ""url"": ""/images"",
+                ""thumbUrl"": ""/images/thumb"",
+                ""initialCapital"": true,
+                ""scriptDirUrl"": ""/w"",
+                ""scriptExtension"": "".php"",
+                ""favicon"": ""http://localhost:8080/favicon.ico""
+            }
+        ]
+    }
+}
+
+Some of these extra return parts are required for VisualEditor's media search to work.
+
+
+(In reply to Patrick King from comment #2)
+> Yes, I did have it installed on the server's root (with a wiki. subdomain).
+
+Quite apart from the MediaWiki 1.22 issue, that's bug 62007 (MediaWiki installed on the server's root is an unsupported configuration by its API, apparently).",1406656996,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sizovmscvvm6rifym437,task_subcomment,NA
+"'Insert Media' in VE fails to search local repo, returns blank.","**tech** wrote:
+
+Upgraded mediawiki to 1.22.5.
+
+Installed parsoid and VisualEditor as new. 
+
+Merged basic LocalSettings.php.
+
+Uploaded a new file.
+
+File and description in Special:ListFiles.
+
+Still no change to this bug, nothing listed, no search results - only call to api is to query filerepoinfo, result as above.",1398218583,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sizovmscvvm6rifym437,task_subcomment,NA
+"'Insert Media' in VE fails to search local repo, returns blank.","**tech** wrote:
+
+Yes, I did have it installed on the server's root (with a wiki. subdomain). But I've just tested with the '/w' leading path ($wgScriptPath = ""/w"") and it's made no difference, no images are showing up even with exact filenames. 
+
+filerepoinfo query returns:
+{""query"":{""repos"":[{""name"":""local"",""displayname"":null,""rootUrl"":""/w/images"",""local"":true}]}}",1397709913,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sizovmscvvm6rifym437,task_subcomment,NA
+"'Insert Media' in VE fails to search local repo, returns blank.","Do you have your wiki installed in the server's root (i.e. corp.foo.com/index.php?title=Main_Page rather than corp.foo.com/w/index.php?title=Main_Page)?
+
+This appears to be a quite common configuration, but is explicitly advised against in MediaWiki's documentation because it doesn't work very well with MediaWiki's API and is the cause of similar issues to this for a number of people. :-(",1397670365,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sizovmscvvm6rifym437,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"After two weeks of vote we've just deliberated in favor of the Visual Editor activation for the logged users who want to tick it only: https://fr.wikinews.org/wiki/Wikinews:Prise_de_d%C3%A9cision/Installation_de_l%27%C3%A9diteur_visuel.
+
+Thank you for your work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1397257620,PHID-USER-dtdj4p6jtxbzs7trc3c6,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_description,resolved
+Enable VisualEditor on the French Wikinews users preferences,"(In reply to JackPotte from comment #5)
+> I've ticked the feature and got an error ""parsoidserver-http-bad-status:
+> 404"" on each attempt with Firefox 28.0, even after a cache reset.
+
+Sorry about that; there was a deployment issue. It should now be working for you.",1397520953,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"I've ticked the feature and got an error ""parsoidserver-http-bad-status: 404"" on each attempt with Firefox 28.0, even after a cache reset.",1397518648,PHID-USER-dtdj4p6jtxbzs7trc3c6,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,This is now done.,1397518536,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"Change 125538 merged by jenkins-bot:
+Enable VisualEditor on French Wikinews
+
+https://gerrit.wikimedia.org/r/125538",1397517103,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"(In reply to Gerrit Notification Bot from comment #1)
+> Change 125538 had a related patch set uploaded by Catrope:
+> Enable VisualEditor on French Wikinews
+> 
+> https://gerrit.wikimedia.org/r/125538
+Scheduled for deployment on Monday April 14 at 23:00 UTC (Tuesday 01:00 CEST).",1397261936,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"Change 125538 had a related patch set uploaded by Catrope:
+Enable VisualEditor on French Wikinews
+
+https://gerrit.wikimedia.org/r/125538",1397260784,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+VisualEditor: Editing a reference adds a separate extra reference in test2,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a reference 
+3.Open the reference dialog box again
+4.Add a cite web template inside it
+5.Save the reference
+
+Observed Result:
+A separate reference gets added just next to the existing reference
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397240520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-225bp5yp7locuogtr3qd,task_description,resolved
+VisualEditor: Editing a reference adds a separate extra reference in test2,"
+
+*** This bug has been marked as a duplicate of bug 63828 ***",1397244708,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-225bp5yp7locuogtr3qd,task_subcomment,NA
+VisualEditor: Editing a reference adds a separate extra reference in test2,This happens not only for adding template rather doing any change/edit on the existing reference,1397240888,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-225bp5yp7locuogtr3qd,task_subcomment,NA
+VisualEditor: Template parameters should resize on initialisation (when needed),"Intention:
+Add a new infobox using VE (from scratch)
+
+Steps to Reproduce:
+1. Go to https://sv.wikipedia.org/wiki/Anv%C3%A4ndare:Andr%C3%A9_Costa_%28WMSE%29/VEtest2?veaction=edit
+2. Enter edit-mode for the template
+3. Go to the ""medlemskap"" parameter. Click value.
+4. Go to the ""budget"" parameter. Click the value.
+
+Actual Results:  
+3. Nothing happens. You must use the down arrow to reveal hidden text.
+4. Value window re-sizes and introduces a scrollbar revealing previously hidden text.
+
+Expected Results:  
+Both cases: Window should have been re-seized on initialisation or indicated that there is more information than shown.
+First case: Window should have been re-seized or a scrollbar introduced.
+
+Reproducible: Always
+
+The main issue is that you might not ever expect that there is more information in the template value than is initially shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397215500,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-ioynhxkaq6fkwspf5nvl,task_description,duplicate
+VisualEditor: Newarticletext points to API not PAGENAME,"Intention:
+Create a new article using VE
+
+Steps to Reproduce:
+1. Go to https://en.wikipedia.org/wiki/THISISNOTANARTICLE?veaction=edit
+2. Wait for notices to load
+
+
+Actual Results:  
+All references to the pagename are changed to API (e.g. hover over search, or see the Special:Mypage/API link.
+
+Expected Results:  
+these links should point to the pagename (e.g. Special:Mypage/THISISNOTANARTICLE)
+
+Reproducible: Always
+
+This is occurs for any site using a pagename reference in MediaWiki:Newarticletext
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397210520,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-zdasmwk6nzlmwf5wx5ui,task_description,resolved
+VisualEditor: Newarticletext points to API not PAGENAME,"
+
+*** This bug has been marked as a duplicate of bug 63600 ***",1397866699,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zdasmwk6nzlmwf5wx5ui,task_subcomment,NA
+VisualEditor: Link inspector inserts plain text while trying to insert a link selecting a math formula,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a link
+3.Insert a math node right after the link
+4.Select the math formula
+5.Click on the link inspector
+6.When the link suggestions drop down appears close the inspector
+
+Observed Result:
+The link inspector inserts plain text right before the math node
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/9thapril2014?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13666}",1397154780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gkhfh2wlphtsgti7jxch,task_description,resolved
+VisualEditor: Link inspector inserts plain text while trying to insert a link selecting a math formula,"
+
+*** This bug has been marked as a duplicate of bug 56644 ***",1397757927,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gkhfh2wlphtsgti7jxch,task_subcomment,NA
+VisualEditor: Image repositioning is not working correctly when the image is inside a bock slug,"Centered wrt the slug
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image just after a block slug
+3.Now change the image position to Centre/Left and Image type to Frame
+
+Observed Result:
+
+The Image is not centered/ left aligned with respect to the page width rather with the width of the slug
+
+Try the first image on this page: https://test2.wikipedia.org/wiki/9thapril2014?veaction=edit
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13663}",1397153220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vz3x2eqhdts2i7ebivnh,task_description,invalid
+VisualEditor: Image repositioning is not working correctly when the image is inside a bock slug,"We don't slug after lists any more, and it looks like in this case you were inserting into the list, not a paragraph after it.",1423749104,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vz3x2eqhdts2i7ebivnh,task_subcomment,NA
+VisualEditor: Image repositioning is not working correctly when the image is inside a bock slug,Note: The block slug in the example page is after an indented list,1397153738,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vz3x2eqhdts2i7ebivnh,task_subcomment,NA
+"VisualEditor:  In the template dialog, the removal icon (trash can) should be visible on all items","When you open an existing template, it looks like only the first parameter can be removed.  To discover that it is possible to remove a template parameter, you must first click in that parameter's data box. 
+
+Instead, the trash icon should be visible on all items always.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1397143740,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gxyil7alpbre5j7mytzf,task_description,declined
+"VisualEditor:  In the template dialog, the removal icon (trash can) should be visible on all items","No. We considered this as part of the design, but it makes the interface far too heavy, cluttered and confusing for such an edge case task.",1397678465,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gxyil7alpbre5j7mytzf,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead","On any editable page on http://en.m.wikipedia.beta.wmflabs.org/ a logged-in user in alpha mode should invoke VisualEditor when clicking the edit icon. 
+
+Instead the user gets the normal non-VE editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397059440,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_description,resolved
+"VE does not appear when it should, get wikitext editor instead","
+
+*** This bug has been marked as a duplicate of bug 63658 ***",1397622427,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead","Change 124881 merged by jenkins-bot:
+Revert ""Only offer VisualEditor if installed and enabled""
+
+https://gerrit.wikimedia.org/r/124881",1397062618,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead",This was introduced by another patchset.,1397062586,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead","Change 124881 had a related patch set uploaded by Jdlrobson:
+Revert ""Only offer VisualEditor if installed and enabled""
+
+https://gerrit.wikimedia.org/r/124881",1397062553,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1916",1397059510,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","To replicate:
+Disable VisualEditor and load the editor. Wikitext editor loads but according to toolbar VisualEditor is available.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396979040,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_description,resolved
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","Change 126672 merged by jenkins-bot:
+Make sure VisualEditor is installed before trying to use it
+
+https://gerrit.wikimedia.org/r/126672",1397669271,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","Change 126672 had a related patch set uploaded by Kaldari:
+Make sure VisualEditor is installed before trying to use it
+
+https://gerrit.wikimedia.org/r/126672",1397667002,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","sorry Theo! I missed that. I don't follow comments on merged commits. Can you bring up your questions on bug 63736 and I'll do my best to answer them in next 24hrs!
+
+Ryan see Bug: 63736 this bug was raised after a fix for it was merged that had to be reverted :(",1397622150,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","(In reply to Ryan Kaldari from comment #2)
+
+> I can't replicate this. If I disable the VisualEditor and try to load the
+> editor in Alpha mode, the editor won't even load. It gives me an unknown
+> dependency JS error. Looking at the code in editor.js, it doesn't look like
+> it takes into account the possibility of the VisualEditor being disabled
+> (which should probably be filed as a different bug).
+
+This. x1000.
+
+I brought this up as a comment on a patch in Gerrit[1], along with a possible solution, but there were never any replies.
+
+Right now MobileFrontend editing does not work on non-VE-enabled websites... which includes my dev site :P
+
+Probably worthy of a bug...
+
+[1] https://gerrit.wikimedia.org/r/#/c/124881/",1397621037,PHID-USER-wgpse4towjiaqbzotzgo,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","I can't replicate this. If I disable the VisualEditor and try to load the editor in Alpha mode, the editor won't even load. It gives me an unknown dependency JS error. Looking at the code in editor.js, it doesn't look like it takes into account the possibility of the VisualEditor being disabled (which should probably be filed as a different bug).
+
+If you can replicate this, please post more detailed replication steps.",1397620274,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1913",1396979110,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+VisualEditor: Parse link in Newarticletext,"screenshot of VE, mozilla ff
+
+When going to
+https://en.wikipedia.org/wiki/File:Henri_Rousseau_009.jpg?veaction=edit
+VE has 1 notice telling me:
+
+""Du bist einem Link zu einer Seite gefolgt, die nicht vorhanden ist. Um diese Seite anzulegen, trage deinen Text in das untenstehende Bearbeitungsfeld ein (weitere Informationen auf der [/wiki/Help:Contents Hilfeseite]).""
+
+Note the ""[/wiki/Help:Contents Hilfeseite]"" part. I guess it should be a link.
+
+
+""Newarticletext"" seems to be the only message containing this text. And there was only one hit for ""Newarticletext"" in the VE repo:
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/797430e9efd4c773c149718ad086f51f8aa042f6/ApiVisualEditor.php#L339
+
+Indeed, the issue seems to be at the PHP side;
+POST /w/api.php
+action	visualeditor
+format	json
+paction	parse
+page	File:Henri_Rousseau_009.jpg
+
+returns the message as ""<p>Du bist einem Link zu einer [...] der [/wiki/Help:Contents Hilfeseite] [...] deines Browsers. </p>""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14035}",1396961580,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-5g5bsfyli427a7al2nvk,task_description,resolved
+VisualEditor: Parse link in Newarticletext,"
+
+*** This bug has been marked as a duplicate of bug 63600 ***",1402295035,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5g5bsfyli427a7al2nvk,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396913520,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_description,resolved
+Edit button throws errors when VisualEditor not installed,"Change 126672 merged by jenkins-bot:
+Make sure VisualEditor is installed before trying to use it
+
+https://gerrit.wikimedia.org/r/126672",1397669273,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"Change 126672 had a related patch set uploaded by Kaldari:
+Make sure VisualEditor is installed before trying to use it
+
+https://gerrit.wikimedia.org/r/126672",1397667007,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"Probably the easiest thing to do would be to just check mw.config.get( 'wgVisualEditorConfig' ). If VisualEditor isn't installed, that will return null.",1397666546,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,*** Bug 63736 has been marked as a duplicate of this bug. ***,1397622427,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,I had to revert this change... since the code is loaded asynchronously it will always return false.,1397062626,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"Change 124494 merged by jenkins-bot:
+Only offer VisualEditor if installed and enabled
+
+https://gerrit.wikimedia.org/r/124494",1396979145,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"Change 124494 had a related patch set uploaded by Jdlrobson:
+Only offer VisualEditor if installed and enabled
+
+https://gerrit.wikimedia.org/r/124494",1396913565,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+"VisualEditor: Cannot open VE in test 2 as it is throwing error: TypeError: undefined is not a function TypeError {stack: (...), message: ""undefined is not a function""}","Screenshot
+
+Steps to reproduce:
+Try to open any page with VE in test 2
+
+Observed Result:
+The following error appears and VE does not load
+TypeError: undefined is not a function TypeError {stack: (...), message: ""undefined is not a function""}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13971}",1396895520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k2eejhz2gxdoin7eo4qz,task_description,declined
+"VisualEditor: Cannot open VE in test 2 as it is throwing error: TypeError: undefined is not a function TypeError {stack: (...), message: ""undefined is not a function""}",Looks like this got fixed at some point.,1414088145,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-k2eejhz2gxdoin7eo4qz,task_subcomment,NA
+VisualEditor:  Images placed inside a <small> text block cannot be edited,"VisualEditor incorrect display of image inside <small> tags
+
+This may depend on Bug 51614 ""Tool to set/unset text as small"".
+
+Start with a page like https://en.wikipedia.org/w/index.php?oldid=603182124#Referenced_text that contains this wikitext:
+
+<small>
+[[File:Example.jpg|thumb|Caption]]
+</small>
+
+When you open the page in VisualEditor, the image ""thumb"" has a box the entire width of the screen, the image is the correct size, but centered, and you can't select (and therefore can't edit) the image.
+
+The caption's text is small, which is probably expected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13959}",1396893540,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zf5c7zmnxbn4etopqpde,task_description,resolved
+VisualEditor:  Images placed inside a <small> text block cannot be edited,"Yeah, we should fix this sooner rather than later. Sorry.
+
+*** This bug has been marked as a duplicate of bug 51614 ***",1396901647,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zf5c7zmnxbn4etopqpde,task_subcomment,NA
+VisualEditor: Edit notices widget confusingly mentions API (in plain text and/or links) when creating a new page,"See
+https://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove5?veaction=edit
+https://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE8?veaction=edit
+and https://en.wikipedia.org/wiki/User:Elitre_(WMF)/Sandbox3?veaction=edit .
+The widget behaves as if you are attempting to create the article ""API"".
+On en.wp it also provides a direct link to create Special:Mypage/API.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396884660,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kxhi7vtkl2n4fcawl2u5,task_description,resolved
+VisualEditor: Edit notices widget confusingly mentions API (in plain text and/or links) when creating a new page,"
+
+*** This bug has been marked as a duplicate of bug 63600 ***",1396887928,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kxhi7vtkl2n4fcawl2u5,task_subcomment,NA
+"incorrect ""Wikitext markup detected"" message","**Author:** `richlv`
+
+**Description:**
+visual editor from git f8d56e6804a12248b485c2d3b49d4ff0ffa7220c
+
+testcase : https://www.zabbix.org/wiki/Bugsquash_Days
+(if creating a new account, real name is mandatory)
+
+edit the page with visual editor. using the cursor keys, modify on of the event link texts :
+
+""Wikitext markup detected
+You are using VisualEditor - wikitext does not work here. Click ""Edit source"" to edit the page in wikitext mode – unsaved changes will be lost.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396874580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4lsnvnfnca247mubrvhc,task_description,declined
+"incorrect ""Wikitext markup detected"" message","Yeah, the regex can't avoid false positives without making typing very slow; instead, we plan to remove the wikitext warning in a while.",1397592475,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4lsnvnfnca247mubrvhc,task_subcomment,NA
+"incorrect ""Wikitext markup detected"" message","**richlv** wrote:
+
+hmm, this might be caused by #-number sequence in the bullet points... if so, not sure whether that can be easily solved",1396879069,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4lsnvnfnca247mubrvhc,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Object #<Object> has no method 'lookup' appears upon loading any page on test2,"Screenshot
+
+For all pages on test2 I am getting the following error upon loading and Ve does not open for that page
+
+Uncaught TypeError: Object #<Object> has no method 'lookup' 
+
+Try this page:
+https://test2.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13741}",1396653660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nzp73hbths7mtxjcxvm4,task_description,declined
+VisualEditor: Uncaught TypeError: Object #<Object> has no method 'lookup' appears upon loading any page on test2,This now WFM; possibly a gadget issue?,1401475943,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nzp73hbths7mtxjcxvm4,task_subcomment,NA
+VisualEditor: [Regression wmf21] Media selector hangs without offering save,"As a logged in user on http://en.wikipedia.beta.wmflabs.org/ edit any page. 
+
+Choose ""Insert Media""
+
+Search for something e.g. ""San Francisco""
+
+Select a media image. 
+
+Insert Media interface does nothing, but should offer a Save and then Review your changes options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396537500,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-y5chdora657t2p3e7tbs,task_description,resolved
+VisualEditor: [Regression wmf21] Media selector hangs without offering save,Verified the fix on production,1397775352,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-y5chdora657t2p3e7tbs,task_subcomment,NA
+VisualEditor: [Regression wmf21] Media selector hangs without offering save,verified the fix on mw.org,1396999374,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-y5chdora657t2p3e7tbs,task_subcomment,NA
+VisualEditor: [Regression wmf21] Media selector hangs without offering save,"This issue got fixed by :https://gerrit.wikimedia.org/r/123803
+Verified in betalabs.",1396571513,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-y5chdora657t2p3e7tbs,task_subcomment,NA
+VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs,"seen on beta labs http://en.wikipedia.beta.wmflabs.org/
+
+After clicking Edit for VisualEditor, sometimes the user waits longer than expected for the editable div to appear.  
+
+There is a default timeout of 5 seconds in the automated browser tests, and these tests are failing more and more often because the edit surface in VE takes longer than 5 seconds to appear, for a page of reasonable size.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396474500,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5ulqzr566hicsrhuontf,task_description,resolved
+VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs,"(In reply to Chris McMahon from comment #2)
+> Well, the *tests* are fixed, but it is a bit sketchy that the editable div
+> is taking so long to manifest.
+
+Beta Labs being slow isn't really a bug so much as a statement of fact…",1396478785,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ulqzr566hicsrhuontf,task_subcomment,NA
+VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs,"Well, the *tests* are fixed, but it is a bit sketchy that the editable div is taking so long to manifest.",1396478562,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5ulqzr566hicsrhuontf,task_subcomment,NA
+VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs,Fixed in gerrit 123450.,1396478369,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ulqzr566hicsrhuontf,task_subcomment,NA
+VisualEditor:  Firefox displays icons in odd places in dialog boxes,"Firefox display bug
+
+This is related to Bug 63432, about the mis-display of an icon in the media settings dialog box, and Bug 63127, about the reference box.
+
+It also displays incorrectly in template boxes (see attachment), references (the icon at ""Options"" for ""Use this group""—see bug 63127), and pretty much everything in the ""Page options"" (three bars icon) menu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63127
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63432
+
+**Attached**: {F13423}",1396460880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gf4us2lajwz7mnxt2hru,task_description,resolved
+VisualEditor:  Firefox displays icons in odd places in dialog boxes,"
+
+*** This bug has been marked as a duplicate of bug 63127 ***",1397687806,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gf4us2lajwz7mnxt2hru,task_subcomment,NA
+VisualEditor:  Media dialog box has misplaced icon in Firefox,"Firefox-only display bug
+
+If you open the image dialog box and go to ""Advanced settings"" in Firefox, the ""window"" icon next to the headline ""Positions"" is misplaced, so that it covers up the checkbox for ""Wrap content with this item"".
+
+This cannot be reproduced in Safari or Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63127
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63433
+
+**Attached**: {F13420}",1396460400,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zwurzmbrgsoaldr6hnqg,task_description,resolved
+VisualEditor:  Media dialog box has misplaced icon in Firefox,"
+
+*** This bug has been marked as a duplicate of bug 63127 ***",1397687801,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zwurzmbrgsoaldr6hnqg,task_subcomment,NA
+Parsoid giving 503s for VE in mobilefrontend on beta labs,"To replicate:
+1) Browse to http://en.m.wikipedia.beta.wmflabs.org/ in a browser window with at least one dimension > 700px
+2) Opt-in to MobileFrontend's experimental feature (main menu -> settings -> beta -> 'on' -> save; main menu -> settings -> experimental -> 'on' -> save)
+3) Browse to random article
+4) Tap/click pencil icon to edit
+
+Current behavior:
+ Receive error ""Error, can't load section""
+Expected behavrio:
+ VisualEditor interface loaded to edit article
+
+
+When looking through the network requests, you should see an API request for the VE action (something like http://en.m.wikipedia.beta.wmflabs.org/w/api.php?format=json&action=visualeditor&paction=parse&page=0.019064959779951818) with a server response of:
+'{""servedby"":""deployment-apache02"",""error"":{""code"":""parsoidserver-http-bad-status"",""info"":""503""}}'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396397280,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-ki5b25is43aulcidvmv4,task_description,resolved
+Parsoid giving 503s for VE in mobilefrontend on beta labs,"This appears to be resolved now. Dunno what changed, but it is at least working again ;)",1396461709,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-ki5b25is43aulcidvmv4,task_subcomment,NA
+VisualEditor: The hand icon remains active after opening the Media Settings dialog and Reference dialog which selects some part inside the dialog upon double clicking,"video capture of the bug
+
+Steps to reproduce:
+
+1.Open a page with VE
+
+2.Insert an image or a reference somewhere at the centre of the page for better viewing the effect of it.
+
+3.Now click on the Reference Icon or the Media Settings icon
+
+Observed Result:
+
+You will see the hand icon inside the dialog box and upon double clicking it selects some part of the dialog box.
+
+See the Video Capture attached.
+
+
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13360}",1396394400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-phnj44ch6mszxq6qpohn,task_description,resolved
+VisualEditor: The hand icon remains active after opening the Media Settings dialog and Reference dialog which selects some part inside the dialog upon double clicking,"Re-checked - non-reproducible anymore, most likely due to re-design of citation dialog/edit boxes.",1425680477,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-phnj44ch6mszxq6qpohn,task_subcomment,NA
+Parsoid crashes on request (TypeError: undefined is not a function),"**Author:** `koem`
+
+**Description:**
+Setup:
+ - Ubuntu 12.04
+ - apache2
+ - mediawiki 1.22.4
+ - parsoid master 2014-04-01 12:58 UTC
+ - nodejs 0.10.26-1chl1~precise1
+ - VisualEditor snapshot REL1_22
+
+This is the error I get when I do curl http://localhost:8000/localhost/Wiki_Test_Page or when I try to edit the page http://wiki.testwiki.com/wiki/Wiki_Test_Page as a logged in user (Popup says ""Error loading data from server: parsoidserver-http-request-error: MWHttpRequest error. Would you like to retry?"").
+
+
+  /usr/local/parsoid/api/ParsoidService.js:355
+                                        callback();
+                                        ^
+  TypeError: undefined is not a function
+    at errCB (/usr/local/parsoid/api/ParsoidService.js:355:6)
+    at /usr/local/parsoid/api/ParsoidService.js:361:12
+    at /usr/local/parsoid/lib/mediawiki.parser.environment.js:241:3
+    at setupWikiConfig (/usr/local/parsoid/lib/mediawiki.parser.environment.js:295:3)
+    at Object.processSome [as _onImmediate] (/usr/local/parsoid/lib/mediawiki.ApiRequest.js:119:17)
+    at processImmediate [as _immediateCallback] (timers.js:330:15)
+  worker 2394 died (8), restarting.
+   - worker(2425) loading...
+   - worker(2425) ready
+
+The worker crashes and is restarted immediately. Always.
+
+The Wiki is private. It worked until I imported some templates and deleted them again. But I can't imagine that this is the reason.
+
+
+LocalPreferences.php:
+
+  require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");
+  $wgVisualEditorParsoidURL = 'http://localhost:8000';
+  $wgDefaultUserOptions['visualeditor-enable'] = 1;
+  $wgHiddenPrefs[] = 'visualeditor-enable';
+  $wgVisualEditorParsoidForwardCookies = true;
+
+
+api/localpreferences.js:
+
+  exports.setup = function( parsoidConfig ) {
+        parsoidConfig.setInterwiki( 'localhost', 'http://wiki.testwiki.com/mediawiki/api.php' );
+        parsoidConfig.useSelser = true;
+  };
+
+Best,
+Karsten
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**OS**: Linux
+**Platform**: PC",1396354080,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3x6kkofcned4qcjjk6dl,task_description,declined
+Parsoid crashes on request (TypeError: undefined is not a function),"The recommended way to deal with private wikis is documented at
+
+https://www.mediawiki.org/wiki/Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis",1400704166,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-3x6kkofcned4qcjjk6dl,task_subcomment,NA
+Parsoid crashes on request (TypeError: undefined is not a function),"**koem** wrote:
+
+ok, solved it by:
+
+          if ( $_SERVER['REMOTE_ADDR'] == '127.0.0.1' ) {
+           $wgGroupPermissions['*']['read'] = true;
+           $wgGroupPermissions['*']['edit'] = true;
+          } else {
+           $wgGroupPermissions['*']['edit'] = false;
+           $wgGroupPermissions['*']['read'] = false;
+          }
+
+and in localsettings.js
+
+          parsoidConfig.setInterwiki( 'localhost', 'http://localhost/mediawiki/api.php' );
+
+please add this to the documentation",1396517054,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3x6kkofcned4qcjjk6dl,task_subcomment,NA
+Parsoid crashes on request (TypeError: undefined is not a function),"**koem** wrote:
+
+When I comment out these lines in LocalSettings.php - then it works. But then my wiki isn't private anymore ...
+
+$wgGroupPermissions['*']['createaccount'] = false;
+$wgGroupPermissions['*']['edit'] = false;
+$wgGroupPermissions['*']['read'] = false;",1396465941,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3x6kkofcned4qcjjk6dl,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**Author:** `andr55`
+
+**Description:**
+I would like the extension:variables installed.
+
+It is available at https://www.mediawiki.org/wiki/Extension:Variables
+
+It is rated as stable.
+It allows creating local variables valid only in the current page.
+
+The current use case is to define a long string to be used in over 100 templates as part of links inside a larger template page.
+This extension will help alleviate constant ongoing problems in a frequently accessed and edited page.  (Over 400 edits in the last month.)
+
+1) By using a local variable, it removes the problem of typos, very common in the page where it will be used.  As well, it will minimize the problem of broken links, as many editors avoid typing the long string necessary to create valid links.
+
+2) It keeps this string local to the only page where it will be used, thus not polluting the template namespace, and avoiding potential name conflicts with other templates.
+
+3) The variable can be defined at the beginning, with a brief description to ensure that it's use is understood, so it becomes self-documenting where it is used.
+
+4) A shorter and more useful name can be chosen than for a template, as a template name would have to avoid ambiguity with other template pages.
+
+5) In the likely case that this string needs to be changed in the future, it can be done more easily, as it will be on the page where it is used.
+
+6) Although this is for use as part of a link, it could equally be used for other cases, as presented in examples on the extension page.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1396294740,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_description,duplicate
+Please add extension:variables to allow defining variables local to the current page,It was marked as a verified duplicate of T9865 while in Bugzilla: http://bugs.wmflabs.org/show_bug.cgi?id=63324,1450841495,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"The extension was never installed, so I'm not sure why this is marked Resolved.",1450839840,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Brad Jorsch from comment #9)
+> (In reply to andré from comment #8)
+> > So you are saying that problems with the implementation of these new
+> > features interfere with this extension ?
+> 
+> It's not a problem with those features, it's a design requirement.
+> 
+> We had to deal with that requirement when creating Scribunto, too.
+
+Evidently.  And it works very well, at least on pages I've seen using it.  Such modules can be a tremendous improvement over pure templates.
+
+> > I'm assuming that all this extension does is scan the page, taking the
+> > variable definitions and replacing all instances using the defined
+> > variables, before any other parsing of the page.  The result is a page that
+> > shows no evidence of the extension.
+> 
+> I haven't checked, but I'd imagine the model is more that when the parsing
+> process calls the hook for #vardefine it sets some internal state, and when
+> it calls the hook for #var then it returns that internal state. Much like
+> how with Cite a <ref> sets some internal state and <references> uses that to
+> construct a list of references.
+
+It would be setting a value for a token, and replacing tokens with that value.  Simple text replacement, as it passes through the page.  There are some more complicated options, but they could be ignored by WP if difficult to implement.  For instance, there could be a bar to using recursion.
+
+> > Maybe there needs to be a processing priority established ?
+> 
+> Let's not add even more passes to the parser. The Parsoid folks already want
+> to do that for Cite (and do do it in Parsoid).
+
+But additional passes can be a very effective way of simplifying the problem.  Often with little or no cost in performance.
+
+> > Maybe you can explain how any problems with the new VisualEditor and Parsoid
+> > are not orthogonal to this extension ?
+> 
+> Because wikitext needs to be parsed?
+
+Logically, the simplest solution for extension:Variables is to have a priority parsing pass to itself.  Once that is done, the resulting page shows no evidence of the extension.
+If there is a relatively straight-forward way to signal the use of the extension in the page (such as a definition near the beginning of the page), the performance hit for other pages should be minimal if any.
+Maybe the parser could do an initial scan of the page to enumerate all the extensions/modules used in the page (if it doesn't already), and then do parsing passes according to an appropriate priority.  Many but not all could be done in parallel.  Extension:Variables being an obvious exception.
+It's not rocket science.  (To experienced programmers, at least.)
+
+If there is a problem with how extension:Variables is implemented, I'd be interested in writing a similar very simple equivalent, that does nothing more than act as a preprocessor, replacing one or more variables with literal text in a single pass.  In my mind that is all that most uses of such an extension would be anyway.  And it does fill a void, between templates and modules created with Scribuntu/Lua",1396375482,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"(In reply to andré from comment #8)
+> So you are saying that problems with the implementation of these new
+> features interfere with this extension ?
+
+It's not a problem with those features, it's a design requirement.
+
+We had to deal with that requirement when creating Scribunto, too.
+
+> I'm assuming that all this extension does is scan the page, taking the
+> variable definitions and replacing all instances using the defined
+> variables, before any other parsing of the page.  The result is a page that
+> shows no evidence of the extension.
+
+I haven't checked, but I'd imagine the model is more that when the parsing process calls the hook for #vardefine it sets some internal state, and when it calls the hook for #var then it returns that internal state. Much like how with Cite a <ref> sets some internal state and <references> uses that to construct a list of references.
+
+> Maybe there needs to be a processing priority established ?
+
+Let's not add even more passes to the parser. The Parsoid folks already want to do that for Cite (and do do it in Parsoid).
+
+> Maybe you can explain how any problems with the new VisualEditor and Parsoid
+> are not orthogonal to this extension ?
+
+Because wikitext needs to be parsed?
+
+> I'm not trying to distract you from solving VisualEditor problems,
+
+Not my department anyway.",1396369923,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Brad Jorsch from comment #6)
+> (In reply to andré from comment #4)
+%%%> > > *** This bug has been marked as a duplicate of bug 7865 ***%%%
+> > 
+> > Not appropriate, for a very old bug rejected for circumstances which likely
+> > have changed.
+> 
+> Circumstances have in fact changed.
+> 
+> However, they've changed such that closing this as anything other than
+> WONTFIX is even more unlikely: VisualEditor and Parsoid require the ability
+> to reparse fragments of the page and then merge the new HTML into the
+> previously-rendered HTML, meaning that new wikitext that affects other parts
+> of the page will not be added (and it's even difficult to fix bugs in Cite
+> due to this issue).
+
+So you are saying that problems with the implementation of these new features interfere with this extension ?
+I don't understand.
+ 
+I'm assuming that all this extension does is scan the page, taking the variable definitions and replacing all instances using the defined variables, before any other parsing of the page.  The result is a page that shows no evidence of the extension.
+Is there something that prevents it from processing before any other parsing ?
+Maybe there needs to be a processing priority established ?
+
+Maybe you can explain how any problems with the new VisualEditor and Parsoid are not orthogonal to this extension ?
+I haven't used VisualEditor yet as I am very comfortable with the older editor, so I'm not aware of any problems there.
+
+BTW, to facilitate the use of this extension, WP could always make some supplementary requirement such as the use of the extension be signaled by a definition at/near the beginning of the page.  Or maybe restrict it to user: space initially, for testing purposes.
+
+I'm not trying to distract you from solving VisualEditor problems, but we have a pre-existing editor which works very well, and extension:Variables is an important enhancement.",1396369181,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Andre Klapper from comment #5)
+> (In reply to andré from comment #3)
+> I don't know what this refers to, but so far it looked like the bug report
+> was about deploying an extension instead.
+
+Exactly.  I was responding to your comment #1 
+
+> > Not appropriate, for a very old bug rejected for circumstances which
+> > likely have changed.
+> 
+> Please provide proof for the ""likely"".
+
+Evidently there have been considerable changes to WP since 2006.
+As well, looking at the changelog of extension:Variables, there was a major re-write for version 2.0.0.  (It is now at 2.0.1)",1396367370,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"(In reply to andré from comment #4)
+> > *** This bug has been marked as a duplicate of bug 7865 ***
+> 
+> Not appropriate, for a very old bug rejected for circumstances which likely
+> have changed.
+
+Circumstances have in fact changed.
+
+However, they've changed such that closing this as anything other than WONTFIX is even more unlikely: VisualEditor and Parsoid require the ability to reparse fragments of the page and then merge the new HTML into the previously-rendered HTML, meaning that new wikitext that affects other parts of the page will not be added (and it's even difficult to fix bugs in Cite due to this issue).",1396357479,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"(In reply to andré from comment #3)
+I don't know what this refers to, but so far it looked like the bug report was about deploying an extension instead.
+
+> Not appropriate, for a very old bug rejected for circumstances which
+> likely have changed.
+
+Please provide proof for the ""likely"".",1396351862,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Bawolff (Brian Wolff) from comment #2)
+> This was rejected way back in the day (bug 7865). I assume the rejection
+> still stands.
+
+It is a very bad assumption that a 7 year old rejection is still valid.
+In case you hadn't noticed, both Mediawiki and extension:variables have changed since then.
+ 
+> -----
+> 
+> 2) It keeps this string local to the only page where it will be used, thus
+> not polluting the template namespace, and avoiding potential name conflicts
+> with other templates.
+> 
+> Fun fact, there are
+> 74106937111882365071085430405560261026092790186009960985252853765064
+> 40296955904 possible template names, (This is an under-estimate, I didn't
+> count most non-english letters). You could easily use
+> Template:PageNameHere/Specific_string_name, or even just make it a subpage
+> of the actual page not in the template namespace, etc. Now namespacing
+> things might be nice just generally, but we're not running out of template
+> names.
+
+Assuming a 2-letter name, that gives only 676 possibilities.
+But that is not the point.
+It is not unreasonable to assume that many short names will conflict.  Disambiguation pages don't exist for nothing.
+One advantage of variables local to a particular page is that such variables can be short, thus easier to type, without any ambiguity.  As noted above.
+
+> 
+> >It is rated as stable.
+> 
+> Just for the record, those ratings are done by the extension author. There
+> are lots of extensions marked unstable which are actually more stable than
+> the stable extensions. So the rating is pretty much meaningless. (Which
+> isn't necessarily to say anything bad about this particular extension, I
+> have no idea how stable it may or may not be)
+> 
+OK.  But note that this extension existed in 2006, and was last modified in 2011.  So it has been around for a while.  And the last 2 (recent) versions are installed on 170 sites.
+
+%%%> *** This bug has been marked as a duplicate of bug 7865 ***%%%
+
+Not appropriate, for a very old bug rejected for circumstances which likely have changed.",1396311259,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Andre Klapper from comment #1)
+> Hi André, thanks for taking the time to report this!
+> 
+> (In reply to andré from comment #0)
+> > I would like the extension:variables installed.
+> 
+> On which site? For any configuration change, a local consensus is required.
+> Could you discuss the matter on the Village pump page of your wiki to
+> confirm that this change is wanted by the community, and paste the link to
+> the discussion here?
+> 
+> Also, please see https://www.mediawiki.org/wiki/Review_queue for a checklist
+> of steps how to proceed before marking this as blocking bug 31235.
+
+Thanks for the feedback.
+The page in question is a template on the English WP.
+I've already had contact with someone on the Village pump page, who wasn't aware of this extension.
+I'll get back when I have the confirmation.",1396309935,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"This was rejected way back in the day (bug 7865). I assume the rejection still stands.
+
+-----
+
+2) It keeps this string local to the only page where it will be used, thus not polluting the template namespace, and avoiding potential name conflicts with other templates.
+
+Fun fact, there are 74106937111882365071085430405560261026092790186009960985252853765064
+40296955904 possible template names, (This is an under-estimate, I didn't count most non-english letters). You could easily use Template:PageNameHere/Specific_string_name, or even just make it a subpage of the actual page not in the template namespace, etc. Now namespacing things might be nice just generally, but we're not running out of template names.
+
+>It is rated as stable.
+
+Just for the record, those ratings are done by the extension author. There are lots of extensions marked unstable which are actually more stable than the stable extensions. So the rating is pretty much meaningless. (Which isn't necessarily to say anything bad about this particular extension, I have no idea how stable it may or may not be)
+
+*** This bug has been marked as a duplicate of bug 7865 ***",1396304859,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"Hi André, thanks for taking the time to report this!
+
+(In reply to andré from comment #0)
+> I would like the extension:variables installed.
+
+On which site? For any configuration change, a local consensus is required. Could you discuss the matter on the Village pump page of your wiki to confirm that this change is wanted by the community, and paste the link to the discussion here?
+
+Also, please see https://www.mediawiki.org/wiki/Review_queue for a checklist of steps how to proceed before marking this as blocking bug 31235.",1396304671,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+VisualEditor:  Ever-growing list of edit summary menus if using the gadget,"Steps to Reproduce:
+1.  Enable the edit-summary gadget at the English Wikipedia as described in Bug 63314.
+
+2.  Make a small change to any page.  Click ""Save"".  Notice the two drop-down menus underneath the edit summary textarea.
+
+3.  Oops, you need to make another change before you save.  Close the save dialog (e.g., press the Escape key).
+
+4.  No, that change is not important (or make another change; it doesn't matter).  Go back to 'Save'.
+
+5.  Count the number of dropdown menus present.
+
+
+
+Reproducible: Always
+
+Repeating this process several times resulted in at least four pairs of dropdown menus in Firefox before I gave up.  
+
+In Safari, I got two pairs, and then (consistently) on the third time, VisualEditor seemed to crash (whole page grays out [or ""whites out"", really], nothing happens until I hit Escape).  But after pressing Escape, everything's fine, and the process can be repeated several more times, resulting in half a dozen pairs of drop downs.  (The white/apparent crash comes back after a few more rounds, but just press Escape again and keep going.)  
+
+Saving the page was ultimately successful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396290300,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-nx2jsmtulfpacm6ytqq2,task_description,invalid
+VisualEditor:  Ever-growing list of edit summary menus if using the gadget,"Bugs with gadgets aren't tracked in Bugzilla (per community request about forking the discussion from on-wiki venues), so marking this as INVALID, sorry.",1396290695,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nx2jsmtulfpacm6ytqq2,task_subcomment,NA
+"VisualEditor:  Edit summary gadget looks like it's working, but edits are saved without edit summaries","Intention:
+Add a pre-set edit summary to an edit using a gadget.
+
+Steps to Reproduce:
+1.  Turn on the gadget at en.wp:   Preferences > Gadgets > Editing > ""Add two new dropdown boxes below the edit summary box with some useful default summaries""
+
+2. Edit any article with VisualEditor.
+
+3.  Save page.  Don't click or type anything into the edit summary box.  Just click on an item something from one of the dropdown menus added by the gadget, and then click on 'Save'.
+
+4.  Look for the edit summary in the page history.
+
+Actual Results:  
+The edit summary displays in the textarea of the save dialog, but it is not saved with the edit.
+
+If you click in the textarea after (but not before) choosing an edit summary from the dropdown menu, then the edit is saved correctly.
+
+
+Reproducible: Always
+
+Confirmed in Chrome, Safari, and Firefox on Mac and Ubuntu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396289760,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-pau2osi4bgxm7omr62y5,task_description,invalid
+"VisualEditor:  Edit summary gadget looks like it's working, but edits are saved without edit summaries","Bugs with gadgets aren't tracked in Bugzilla (per community request about forking the discussion from on-wiki venues), so marking this as INVALID, sorry.",1396290681,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pau2osi4bgxm7omr62y5,task_subcomment,NA
+"When a template is in a section title, VE consider what is on the same line after as if it was into the template","Impossible to delete this addition: https//fr.wiktionary.org/w/index.php?title=pr%C3%A9dominer&diff=prev&oldid=18065635
+
+because VE consider it as a template part: https://commons.wikimedia.org/wiki/File:VisualEditor_bug_on_fr.wikt.PNG
+
+Tested on two PCs, including one with Firefox 28.0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://fr.wiktionary.org/w/index.php?title=pr%C3%A9dominer&diff=prev&oldid=18065635",1396225140,PHID-USER-dtdj4p6jtxbzs7trc3c6,PHID-TASK-d7f46ss2k5gqniu6endn,task_description,resolved
+"When a template is in a section title, VE consider what is on the same line after as if it was into the template","The problem here is that the template ""{{S|étymologie}}"" creates a broken block object, so everything after it has to be part of the same block. (This, BTW, is horrible wikitext.)
+
+When Parsoid encounters this, it has no choice but to assume that the (mistaken) rest of the block was intended to be there, so groups it in with the template. Had the user put a newline in correctly it would have worked fine, but this isn't great. :-(
+
+What do you suggest we should do in this case?",1396292877,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d7f46ss2k5gqniu6endn,task_subcomment,NA
+Template's CSS code shows on page when editing,"picture of the bug
+
+Template's html code shows on page when editing. I don't know should we change something with our templates on fi-wiki, or is it possible to fix in VisualEditor.
+
+How to reproduce:
+1) go to https://fi.wikipedia.org/wiki/Australian_Grand_Prix_2014?veaction=edit
+2) see the 2 templates on the bottom of the page
+
+If you need more information, feel free to ask.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13012}",1396097400,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-cqmy2yutnupgu7hrfwej,task_description,invalid
+Template's CSS code shows on page when editing,Closed. Thanks for your investigating.,1396191796,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-cqmy2yutnupgu7hrfwej,task_subcomment,NA
+Template's CSS code shows on page when editing,"Hi, i think that the idea of the ""lisätyylit"" is to add css inline rules to div and stuff after that is to end css-rules and add some table attributes. However it has never worked because there is div element and not table. It also broke resulting html-code even it seemed to work.
+
+Reason why visual editor broke is the mismatching doublequotes in expanded template result (in lisätyyli param: '... both"" cellpadding=""2"" cellspacing=""5""':
+
+-- Clip --
+<div class=""NavFrame "" style="" margin: auto; background-color: #ffffff; border: 1px #aaaaaa solid; margin: 0.5em auto auto auto; width: 600px; text-align: center; font-size: 95%; clear: both;; background-color: #FFFFFF; color: #000000; width: auto;""><div class=""NavHead"" style=""display:block;text-align:center;background-color: #F3D161;"">
+-- Clip --
+
+I fixed some templates with this change and my guess that all of F1-templates can be fixed with same way: 
+- https://fi.wikipedia.org/w/index.php?title=Malline%3ABrasilian_Grand_Prix&diff=13955778&oldid=13575504
+
+However there seems to be little delay before change can be seen in visual editor after template is fixed and i could not find any way to purge visual editors cache. 
+
+If it ok for stryn i think that this bug can be closed.",1396191578,PHID-USER-pmmyhpxkzmo6lbo5bcqo,PHID-TASK-cqmy2yutnupgu7hrfwej,task_subcomment,NA
+Template's CSS code shows on page when editing,"Well, https://fi.wikipedia.org/w/index.php?title=Malline:Australian_Grand_Prix&action=edit
+
+
+| lisätyylit = ...styleinfo..."" cellpadding=""2"" cellspacing=""5""
+
+What is that, and what gave anyone the idea that that would ever work ? :D",1396099045,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-cqmy2yutnupgu7hrfwej,task_subcomment,NA
+Clicking edit in VE tablet doesn't respond instantly,"When you click the edit button the address bar changes but the editor doesn't overlay. Many a time I find myself clicking it several times.
+
+The problem stems from VisualEditor code being loaded via mw.loader.using but no LoadingOverlay being shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395967680,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-hlddr6phtisadyt4ixuj,task_description,resolved
+Clicking edit in VE tablet doesn't respond instantly,"Change 124025 merged by jenkins-bot:
+Show LoadingOverlay when loading VE
+
+https://gerrit.wikimedia.org/r/124025",1396652665,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlddr6phtisadyt4ixuj,task_subcomment,NA
+Clicking edit in VE tablet doesn't respond instantly,"Change 124025 had a related patch set uploaded by JGonera:
+Show LoadingOverlay when loading VE
+
+https://gerrit.wikimedia.org/r/124025",1396650846,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlddr6phtisadyt4ixuj,task_subcomment,NA
+Clicking edit in VE tablet doesn't respond instantly,The loader should show and the overlay should be semi transparent.,1396477288,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-hlddr6phtisadyt4ixuj,task_subcomment,NA
+Clicking edit in VE tablet doesn't respond instantly,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1817",1395967809,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hlddr6phtisadyt4ixuj,task_subcomment,NA
+"VisualEditor: When using browser zoom, image overlays (resize, edit) become too small and inaccesible","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1395894960,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-csoldbfxlq5rsqqvnrq6,task_description,declined
+"VisualEditor: When using browser zoom, image overlays (resize, edit) become too small and inaccesible","Not convinced that this is something we should fix – the whole point of browser zoom is that VE shouldn't care what the zoom level is, and should be consistent. If you zoom out to the level that things are too small, then you won't be easily able to click them. If you zoom in, they will get bigger.
+
+Unless I'm missing something?",1400695607,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-csoldbfxlq5rsqqvnrq6,task_subcomment,NA
+"Scrolling a long template parameter, then clicking causes the cursor to jump to the top of the long parameter field","Navigate here: https://www.mediawiki.org/wiki/VisualEditor:Test12
+
+Open the VisualEditor
+
+Open the template editor for the page's content — should be Template:Longformcontent
+
+Scroll to the fourth parameter text entry field.
+
+Scroll within the fourth parameter's text entry field to ""Maecenas non condimentum risus.""
+
+Click ""Maecenas non condimentum risus.""
+
+Defect: the cursor is placed at the top of the text entry field, by ""Lorem ipsum dolor""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9",1395862260,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-2rc2hldv5lyl6kgrhcon,task_description,declined
+"Scrolling a long template parameter, then clicking causes the cursor to jump to the top of the long parameter field","I think this is now fixed on production, and this ticket should be closed.",1403637258,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-2rc2hldv5lyl6kgrhcon,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Screenshot
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13208}",1395772260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v5ulk7ng472f6cnu46nx,task_description,resolved
+VisualEditor: Math inspector label is showing up as null in Betalabs,Verified the fix in test2,1395790633,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Change 120854 merged by jenkins-bot:
+Make VE math inspector title not be null
+
+https://gerrit.wikimedia.org/r/120854",1395789798,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,Verified the fix on betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Reference_numbering&veaction=edit,1395775955,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Change 120846 merged by jenkins-bot:
+Make VE math inspector title not be null
+
+https://gerrit.wikimedia.org/r/120846",1395774688,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Change 120854 had a related patch set uploaded by Jforrester:
+Make VE math inspector title not be null
+
+https://gerrit.wikimedia.org/r/120854",1395774638,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Change 120846 had a related patch set uploaded by Catrope:
+Make VE math inspector title not be null
+
+https://gerrit.wikimedia.org/r/120846",1395772554,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+use new param in VE tests to get around beta warning,"see https://gerrit.wikimedia.org/r/#/c/119217/
+
+update VisualEditor appropriately
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395703860,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-vcoxn3g74svzqfbhj3kr,task_description,resolved
+VisualEditor: save button remains greyed out in IE9 even after modifying the document,"There is something that should be triggered to change the appearance of the save button in IE that isn't being triggered.  I need to find it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395702780,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-r3yfhoreb7uextmhj5cl,task_description,resolved
+VisualEditor: save button remains greyed out in IE9 even after modifying the document,"Think this is a dupe of Bug #63039
+
+*** This bug has been marked as a duplicate of bug 63039 ***",1395784399,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-r3yfhoreb7uextmhj5cl,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image/reference
+3.Inside the reference or media dialog box insert a link/special character inserter
+4.Now hover over any button on the link inspector like close or delete button
+
+Observed Result:
+The dialog box is getting misplaced like flickering
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395687420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_description,resolved
+VisualEditor: Various things wiggle on hover in Chrome,"For completion, usage of `.oo-ui-force-gpu-composite-layer()` in v0.24.3 resolved this misbehaviour in Chrome.",1513150356,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,Reference task: {T64591},1512598507,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"
+
+*** This bug has been marked as a duplicate of bug 62591 ***",1395876216,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"Update: this is only when *animating* opacity, not when changing opacity.",1395875546,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,Updated summary: there are also smaller wiggling bugs when you hover over close buttons of popups and various other places.,1395875140,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"This turns out to be because Chrome turns some sort of hardware acceleration or whatever on or off when the opacity is not 1. When you hover over certain icons, we change the opacity from 0.8 to 1, which triggers acceleration stuff, and so everything wiggles.
+
+I'll try to come up with a minimal test case and file this bug against Chrome, but for now I'll just change all opacity: 1; rules to opacity: 0.99;",1395874826,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"This may be a particularly bad incarnation of the wiggling issue (mouse over the closing X of the edit notices popup and you'll see the text wiggle), exacerbated by the fact that this is in an iframe.
+
+I think Trevor addressed wiggliness in the template dialog using -webkit-backface-visibility: hidden;, we should try that here.",1395858796,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+"VisualEditor: When tabbing inside the template inspector, don't skip the ""Add Parameter"" option","When reaching the bottom of a list of parameters for a given template, cursor in the box of the last parameter, if you hit Tab you'll be taken directly to the ""Apply changes"" button, while some users would expect ""Add Parameter"" to be reachable then.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395675720,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-goupncgsrq626ilxi7gq,task_description,resolved
+"VisualEditor: When tabbing inside the template inspector, don't skip the ""Add Parameter"" option","I believe this was fixed with bug 65474 being completed. Sorry for getting this out of order.
+
+*** This bug has been marked as a duplicate of bug 65474 ***",1402553868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-goupncgsrq626ilxi7gq,task_subcomment,NA
+VisualEditor: Link inspector icon remains enabled in the toolbar even after closing the link inspector,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Now open a link inspector
+3.Do not insert any link, just close the link inspector by pressing ""<"" or the trash icon
+
+Observed Result:
+
+The link inspector icon is still active on the toolbar
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12885}",1395440220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sffadm7jcu5zx5bxq7pj,task_description,invalid
+VisualEditor: Link inspector icon remains enabled in the toolbar even after closing the link inspector,"This isn't a bug; the ""active"" state is intentional.",1398726819,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sffadm7jcu5zx5bxq7pj,task_subcomment,NA
+"unexpected ""session no longer valid"" in automated test","unexpected session no longer valid message
+
+Seen in some automated tests, for example https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/410/testReport/(root)/VisualEditor/Edit_with_strings__outline_example_____Editing_with_%C3%A1%C3%A9%C3%AD%C3%B3%C3%BA___Editing_with_%C3%A1%C3%A9%C3%AD%C3%B3%C3%BA___/
+
+in the span of less than 90 seconds, this test does these steps: 
+
+* start a browser (Firefox)
+* login to beta labs and navigate to an editable page
+* dismisses the beta warning
+* edits the page with a smallish string
+* click Save page
+* click This is a minor edit
+* click Review your changes
+* click Return to save form
+* edit the description of the change
+* click Save page the second time
+
+At the last step, the result shows an error message ""Warning: we could not process your edit because the session was no longer valid..."" 
+
+See screen shot.  
+
+Note in the screen shot that the user is still logged in properly at the time they receive the error message.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12866}",1395418080,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-rmjs32q5moc3ksh5b4i6,task_description,resolved
+"unexpected ""session no longer valid"" in automated test",Wasn't this the bug that was caused by the mobile test for logging the user out running in parallel?,1417482592,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rmjs32q5moc3ksh5b4i6,task_subcomment,NA
+Load charset into special characters option,"I think its great that developers add special characters option. While I would see here an improvment to load on every different wikipedia its charset, which was after the years of its ussage developed. Its not an ""extra"" of folks, its the fact that every language has some specifics (Spanish ¿, Czech „“) which are not native to keyboards. But yet when we want to have a clear and quality ecyclopedia we use them.",1395392760,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-kvfwa2nd6meb57icljm7,task_description,resolved
+Load charset into special characters option,VisualEditor has used MediaWiki core's list of characters since around March.,1438804265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kvfwa2nd6meb57icljm7,task_subcomment,NA
+VisualEditor:  Ctrl-clicking on redlinks (only) in a subpage takes you to the wrong page title,"Intention:
+Find out why [[Page]] was a redlink by opening the link in another window.
+
+Steps to Reproduce:
+1. Open a sandbox in a subpage, e.g. [[User:Example/Sandbox]]
+
+2. Add a redlink to a non-existent [[Page]].
+
+3. Ctrl-click on the redlink to open the non-existent page in another tab.
+
+4. See that the page actually opened in [[User:Example/Page]] instead of at [[Page]].
+
+
+
+Reproducible: Always
+
+This was fixed in Bug 59196 but has re-appeared for redlinks only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395336660,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-u3drbnyix6yjkcu5oyqk,task_description,resolved
+VisualEditor:  Ctrl-clicking on redlinks (only) in a subpage takes you to the wrong page title,"
+
+*** This bug has been marked as a duplicate of bug 58314 ***",1395344091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u3drbnyix6yjkcu5oyqk,task_subcomment,NA
+VisualEditor:  Redirects not found when you try to make a link (wmf18),"Intention:
+Add a link to a redirect page.
+
+Steps to Reproduce:
+1. Go to Mediawiki.org.  Open a page in VisualEditor and type some text.
+
+2. Select a word and try to link it to [[Help:Help]], an existing redirect page.
+
+
+
+Actual Results:  
+It claims that the existing page is a ""New Page""/redlink.
+
+
+Reproducible: Always
+
+This only happens at Mediawiki.org  The problem cannot be reproduced at either beta labs or at the Wikipedias, so it must be something in wmf18.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395184080,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ip33qxtt2biyhu6zcsou,task_description,resolved
+VisualEditor:  Redirects not found when you try to make a link (wmf18),"
+
+*** This bug has been marked as a duplicate of bug 54361 ***",1395185089,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ip33qxtt2biyhu6zcsou,task_subcomment,NA
+VisualEditor:  Text-oriented templates don't wrap normally,"What the page ought to look like
+
+If you have an inline template (like {{highlight}} at en.wp) with a lot of text in it, the text needs to wrap instead of behaving like a block.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13155}",1395169320,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ly47mruxj7vi65vxkzoe,task_description,resolved
+VisualEditor:  Text-oriented templates don't wrap normally,"
+
+*** This bug has been marked as a duplicate of bug 51708 ***",1395169574,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ly47mruxj7vi65vxkzoe,task_subcomment,NA
+VisualEditor:  Text-oriented templates don't wrap normally,"Created attachment 14855
+What the page actually looks like inside VisualEditor
+
+**Attached**: {F13156}",1395169368,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ly47mruxj7vi65vxkzoe,task_subcomment,NA
+VisualEditor:  Selection problems involving sfn template in Safari,"Steps to Reproduce:
+1. Using Safari, open https://en.wikipedia.org/w/index.php?oldid=600087421 and scroll to the ==Referenced text== (first) section.
+
+2. Select a sentence in the first paragraph, including at least one <ref> tag.
+
+3. Control-click on your choice of ""refs"" in the next paragraph.  (These are all {{sfn}} templates.)
+
+4.  Pretty, isn't it?
+
+Actual Results:  
+Text all over the page was selected, but not box-type templates.
+
+
+Reproducible: Sometimes
+
+Unable to reproduce in Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395103080,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ynfnvjveqi44j7uneaz3,task_description,resolved
+VisualEditor:  Selection problems involving sfn template in Safari,Seems to be long-fixed?,1417578429,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ynfnvjveqi44j7uneaz3,task_subcomment,NA
+VisualEditor:  Selection problems involving sfn template in Safari,"Created attachment 14845
+Screenshot showing strange selection pattern
+
+**Attached**: {F13075}",1395103309,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ynfnvjveqi44j7uneaz3,task_subcomment,NA
+Display the version of VisualEditor in help popup,"Would be nice to see this there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395097560,PHID-USER-b27lopawgf2h6utuuqyi,PHID-TASK-7xrtsoeeizfsiz3k6g62,task_description,resolved
+Display the version of VisualEditor in help popup,"This was done in bug 53050. Unfortunately due to bug 53972 it doesn't display in production for Wikimedia sites yet, sorry.
+
+*** This bug has been marked as a duplicate of bug 53972 ***",1395351525,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7xrtsoeeizfsiz3k6g62,task_subcomment,NA
+VisualEditor:  What you see is not the Babel box that you get,"Intention:
+Add a Babel box
+
+Steps to Reproduce:
+1. Add {{#babel:en|de-1|es-1|vo-0}} using the workaround described in bug 62750.
+
+2. Look at the results.
+
+3. Save the page.  Look at the very different results.
+
+Actual Results:  
+See the screenshot.  The first shows the left-aligned box before save; the second shows the right-aligned, colorful box after the save.
+
+Expected Results:  
+What you saw in VisualEditor would have some signficant relationship to what you saw when the page was saved.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395083220,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-67pmnsh7dhho75ccfvye,task_description,resolved
+VisualEditor:  What you see is not the Babel box that you get,Re-checked it in production - no difference in displaying {{#babel:en|de-1|es-1|vo-0}} in VE and in Read mode.,1425682420,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-67pmnsh7dhho75ccfvye,task_subcomment,NA
+VisualEditor:  What you see is not the Babel box that you get,"Created attachment 14838
+Screenshots showing radically different displays of the same content pre- and post-saving.
+
+**Attached**: {F13023}",1395083273,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-67pmnsh7dhho75ccfvye,task_subcomment,NA
+"When cutting and pasting list items, it is hard to achieve the intended formatting","If I cut items from a bulleted list and try to past them into another bulleted list, the formatting gets confusing:
+
+*Extra empty bullets get left behind when I cut.
+*The relationship between an existing list and new items I paste to the end of it can be wonky. Extra line breaks appear, and sub-bullets lost their relationship to each other, so that pressing tab to increase the level of indentation sometimes creates two bullets in a row instead of just increasing the level of indentation.
+
+See this screen recording for more details of my experience: https://commons.wikimedia.org/wiki/File:Screen_recording_of_trying_to_move_bulleted_list_items_in_VisualEditor.ogv
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395080580,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-26ap2rg73qekvvcczshf,task_description,resolved
+"When cutting and pasting list items, it is hard to achieve the intended formatting","Appears to be fixed now. If you can still reproduce, please reopen.",1429223053,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-26ap2rg73qekvvcczshf,task_subcomment,NA
+VisualEditor: Edit links are not appearing for the headings in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add some headings
+3.Save the page
+
+Observed Result:
+
+Edit links are not appearing for the headings
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13017}",1395080160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d3gqxoje5kzf5dkzzc7n,task_description,invalid
+VisualEditor: Edit links are not appearing for the headings in Betalabs,Was caused by a transcluded page that set __NOSECTIONEDIT__,1395081382,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d3gqxoje5kzf5dkzzc7n,task_subcomment,NA
+VisualEditor: Edit links are not appearing for the headings in Betalabs,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/17thMarchrome",1395080266,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d3gqxoje5kzf5dkzzc7n,task_subcomment,NA
+"Description of tags ""VisualEditor: Check"" and ""VisualEditor: Switched"" are hard to translate","In its current form I'm always wondering ""check what?"" and ""switched what?""
+
+Can't them be replaced by sentences like ""Switched from VisualEditor"" and ""Check VisualEditor errors"" or something better?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394887140,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-7knsheja5rlwn5x4ough,task_description,declined
+"Description of tags ""VisualEditor: Check"" and ""VisualEditor: Switched"" are hard to translate",=/,1400032552,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-7knsheja5rlwn5x4ough,task_subcomment,NA
+"Description of tags ""VisualEditor: Check"" and ""VisualEditor: Switched"" are hard to translate","(In reply to Helder from comment #0)
+> In its current form I'm always wondering ""check what?"" and ""switched what?""
+> 
+> Can't them be replaced by sentences like ""Switched from VisualEditor"" and
+> ""Check VisualEditor errors"" or something better?
+
+Space is at a premium where tags are involved. They occur in page histories, recent changes, watchlists, diffs, IRC feeds, and other places. Brevity is important.
+
+Also, as Alex says, if this is just fixing the qqq messages to make these clearer, this can be done at TranslateWiki.net without the need for a bug.",1400014248,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7knsheja5rlwn5x4ough,task_subcomment,NA
+"Description of tags ""VisualEditor: Check"" and ""VisualEditor: Switched"" are hard to translate",Aren't the docs supposed to clear up issues like this? Are they insufficient?,1400013182,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-7knsheja5rlwn5x4ough,task_subcomment,NA
+"VisualEditor: On opening a page that contains only a template, template is selected but you can't edit the template","Intention:
+Edit https://www.mediawiki.org/wiki/User:Quiddity_(WMF)
+
+
+Steps to Reproduce:
+1. Click on https://www.mediawiki.org/wiki/User:Quiddity_%28WMF%29?veaction=edit
+
+2. Template is selected.
+
+3. But there's no puzzle piece, and you can't edit it.
+
+
+Actual Results:  
+You can't edit the template unless you click outside the template (e.g., in the title or on a blank spot in the sidebar) first.
+
+
+Reproducible: Always
+
+See bug 62542, for inability to use cursor keys to deselect the template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394818380,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-psa6ws3eur6fpdx4wxx6,task_description,resolved
+"VisualEditor: On opening a page that contains only a template, template is selected but you can't edit the template","Merging with the more general bug 57477.
+
+*** This bug has been marked as a duplicate of bug 57477 ***",1394818952,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-psa6ws3eur6fpdx4wxx6,task_subcomment,NA
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,"See icons overlapping other elements at
+https://commons.wikimedia.org/wiki/File:Bug_EV_insertion_mod%C3%A8les_ic%C3%B4ne_d%C3%A9plac%C3%A9e.png
+https://commons.wikimedia.org/wiki/File:Bug_EV_-_insertion_mod%C3%A8les_ic%C3%B4ne_d%C3%A9plac%C3%A9e_02.png
+https://commons.wikimedia.org/wiki/File:Bug_EV_-_insertion_mod%C3%A8les_ic%C3%B4ne_d%C3%A9plac%C3%A9e_03.png
+
+You can also see this very easily through the Options menu on other sites.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394811240,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_description,duplicate
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,duplicate of bug 63127,1398377862,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_subcomment,NA
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,"Some texts on the ""page options"" menu are unreadable because there is some buttons in wrong places. At least I can't check ""redirect this page to"" checkbox because the button is on the checkbox.
+
+Sorry about my ""ASAP"" comment. It looks bad, but there's no ""ASAP"" hurry (and for the record, I've never done any patches [maybe I need to learn]).",1396206923,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_subcomment,NA
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,"So does this ""only"" look bad, or is actually some functionality broken (icon is a button which is not clickable anymore but should be, etc)?
+ 
+I'm slightly allergic to ""should do ASAP"" comments -- if things should be fixed ASAP, providing a patch helps more than adding comments about ASAP. ;))",1396206262,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_subcomment,NA
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,The same problem exists also with Firefox 28.0. Should be fixed ASAP.,1396109201,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","Clicking ""Edit"" (VisualEditor) on https://wikitech.wikimedia.org/wiki/Shell_Request/Rxy shows an error from the server about content model json being incompatible.
+
+However VisualEditor shouldn't initialise that far in the first place, we know the content model (conf.wgPageContentModel).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394654460,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_description,invalid
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","(In reply to Yaron Koren from comment #6)
+> I'm marking this as ""invalid"" - I would change the component to Semantic
+> MediaWiki, but that's not longer on Bugzilla. If you want to submit it as an
+> SMW bug, you need to go to the SMW GitHub page.
+
+Since the bug was filed it appears the page linked has been converted to actually be wikitext-based – Krinkle, can we leave this closed or do we need to raise a GitHub issue?
+
+(I note that it is actually wikitext, not JSON, content; perhaps us having a year-old version of SMW doesn't help.)",1405388498,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","I'm marking this as ""invalid"" - I would change the component to Semantic MediaWiki, but that's not longer on Bugzilla. If you want to submit it as an SMW bug, you need to go to the SMW GitHub page.",1405378673,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","Yes, Semantic Forms only provides the edit button/page - it doesn't affect the actual content page. If any SMW-related extension is causing this error, I would assume it's Semantic MediaWiki itself.",1395661352,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","(In reply to Yaron Koren from comment #3)
+> Well, ""lies"" is a strong word. :) What makes you think this problem comes
+> from Semantic Forms?
+
+
+The wiki uses Semantic MediaWiki, and this is FormEdit-able page (Special:Formedit). That's Semantic Forms, right?
+
+Or is the turning the page itself into semantic data done (json content model) done by another Semantic extension and Semantic Forms only provides the special page and edit button?",1395452387,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","Well, ""lies"" is a strong word. :) What makes you think this problem comes from Semantic Forms? Is it just the fact that the page uses a form?
+
+Also, you wrote, ""it admits its JSON"", meaning that the page really holds JSON but claims that it's holding wikitext. Isn't the problem the other way around?",1394713774,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","OutputPage.php exports:
+
+> 'wgPageContentModel' => $title->getContentModel(),",1394654727,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","Hm... Looks like a bug with Semantic MediaWiki.
+
+It is exporting mw.config wgPageContentModel = 'wikitext', and yet when you really ask it it admits its JSON.
+
+> > mw.config.get( 'wgPageContentModel' );
+> < ""wikitext""
+
+> click ""Edit""
+> < AJAX Eror
+> {
+>   .. Exception Caught: The content format json is not supported by the content model wikitext.",1394654629,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+External link with embedded comment is not shown correctly,"The first external link in the ""Further reading"" section of https://en.wikipedia.org/w/index.php?title=State_Patty%27s_Day&oldid=597985640&veaction=edit is not shown the same in VisualEditor as the PHP parser.
+
+In VE, the text shows as ""'s+Day%22&hl=en&sa=X&ei=7XQyUaeaD4LqiQL9zIHIBw&ved=0CDAQ6AEwAA#v=onepage&q=%22State%20Patty's%20Day%22&f=false Early Adulthood in a Family Context - Alan Booth - Google Books"".
+
+In a normal view (https://en.wikipedia.org/w/index.php?title=State_Patty%27s_Day&oldid=597985640), it shows as ""Early Adulthood in a Family Context - Alan Booth - Google Books"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394349000,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-rowxfowcw2djnxscevba,task_description,declined
+External link with embedded comment is not shown correctly,This appears to now work.,1398901917,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rowxfowcw2djnxscevba,task_subcomment,NA
+VisualEditor:  Template converted to span tags at Javanese Wikipedia,"https://jv.wikipedia.org/wiki/Cithakan:Lahirmati (Template:Birth and death) is converted to span tags in this edit:  https://jv.wikipedia.org/w/index.php?title=Jojon&curid=74332&diff=881686&oldid=830430
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394236920,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-33whpxom3nwt6xusuiuy,task_description,invalid
+VisualEditor:  Template converted to span tags at Javanese Wikipedia,No steps to reproduce given in the past three years.,1533062237,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-33whpxom3nwt6xusuiuy,task_subcomment,NA
+VisualEditor:Trying to add an image as a bullet list item removes the bullet but the Bullet list option remains selected in the menu,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a bullet list
+3.Insert an image as an item to the bullet list.
+
+Observed Result:
+The bullet goes away but if you place the cursor in that position the bullet list icon remains active in the menu.
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13399}",1394156280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bw6f5yfozkwjmdh33dvf,task_description,resolved
+VisualEditor: Typing into empty paragraph with inspector open creates pawn,"1. Open empty.html in SA demo
+2. Open the language inspector or the special character inspector
+3. Type, a pawn appears
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393957200,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dwxkxakygop4b2h6bkwj,task_description,resolved
+VisualEditor: Typing into empty paragraph with inspector open creates pawn,Fixed these focus/range issues a while ago.,1402834213,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dwxkxakygop4b2h6bkwj,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","The fix for bug 48418 made the assumption that {CREDITS|AUTHORS}.* files were wikitext (with the implication that wikitext bullets should precede each file), contrary to expectations.
+
+Instead, we should treat their contents as the plain text they (mostly) were until this feature was added, and merely wrap them in <pre>s for Special:Version/Credits/… etc. purposes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1393866300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4fzagmogxghtgnyhorob,task_description,resolved
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116517 merged by jenkins-bot:
+Reformat AUTHORS as wikitext
+
+https://gerrit.wikimedia.org/r/116517",1394044641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116515 merged by Mwalker:
+Special:Version: Treat AUTHORS.txt and CREDITS.txt as text, not wikitext
+
+https://gerrit.wikimedia.org/r/116515",1393873494,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116516 abandoned by Jforrester:
+Reformat AUTHORS as wikitext
+
+Reason:
+Already done in I213caa7692bdb0a.
+
+https://gerrit.wikimedia.org/r/116516",1393872025,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116517 had a related patch set uploaded by Anomie:
+Reformat AUTHORS as wikitext
+
+https://gerrit.wikimedia.org/r/116517",1393869492,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116516 had a related patch set uploaded by Anomie:
+Reformat AUTHORS as wikitext
+
+https://gerrit.wikimedia.org/r/116516",1393869483,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116515 had a related patch set uploaded by Anomie:
+Special:Version: Treat AUTHORS.txt and CREDITS.txt as text, not wikitext
+
+https://gerrit.wikimedia.org/r/116515",1393869471,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","(In reply to Brad Jorsch from comment #3)
+> (In reply to James Forrester from comment #0)
+> > Instead, we should treat their contents as the plain text they (mostly) were
+> > until this feature was added
+> 
+> I'm not sure about ""mostly"".
+> 
+> I haven't tried to account for changes since this feature was added, but
+> looking at the situation now for extensions in git, these appear to be
+> wikitext:
+> * CentralNotice/CREDITS
+> * CirrusSearch/CREDITS
+> * MultimediaViewer/AUTHORS
+> * RevisionCommentSupplement/CREDITS
+> * UniversalLanguageSelector/CREDITS
+> * UploadWizard/CREDITS
+> * Wikilog/CREDITS
+> * WikiLove/CREDITS
+> 
+> These don't:
+> * BetaFeatures/AUTHORS
+> * ContentTranslation/AUTHORS.txt
+> * EventLogging/AUTHORS
+> * Parsoid/AUTHORS.txt
+> * VisualEditor/AUTHORS.txt
+> 
+> Based on that, I'd lean towards renaming BetaFeatures/AUTHORS and
+> EventLogging/AUTHORS to have a "".txt"" extension (or just reformat them as
+> wikitext) and only apply <pre> if the file used ends in "".txt"".
+
+Works for me; have re-named the bug appropriately.",1393868488,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","(In reply to James Forrester from comment #0)
+> Instead, we should treat their contents as the plain text they (mostly) were
+> until this feature was added
+
+I'm not sure about ""mostly"".
+
+I haven't tried to account for changes since this feature was added, but looking at the situation now for extensions in git, these appear to be wikitext:
+* CentralNotice/CREDITS
+* CirrusSearch/CREDITS
+* MultimediaViewer/AUTHORS
+* RevisionCommentSupplement/CREDITS
+* UniversalLanguageSelector/CREDITS
+* UploadWizard/CREDITS
+* Wikilog/CREDITS
+* WikiLove/CREDITS
+
+These don't:
+* BetaFeatures/AUTHORS
+* ContentTranslation/AUTHORS.txt
+* EventLogging/AUTHORS
+* Parsoid/AUTHORS.txt
+* VisualEditor/AUTHORS.txt
+
+Based on that, I'd lean towards renaming BetaFeatures/AUTHORS and EventLogging/AUTHORS to have a "".txt"" extension (or just reformat them as wikitext) and only apply <pre> if the file used ends in "".txt"".",1393868233,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","(In reply to MZMcBride from comment #1)
+> This bug can probably be marked with the ""easy"" keyword, if there's
+> consensus to change the behavior.
+
+Agreed, but let's get rough consensus first.",1393866491,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","This bug can probably be marked with the ""easy"" keyword, if there's consensus to change the behavior.",1393866437,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"List of repositories that need to be updated is here:
+
+https://github.com/wikimedia/mediawiki-selenium#links
+
+Do not forget mediawiki_selenium gem.
+
+To update Ruby to version 2.1.1, locate Gemfile file, either in the root of the repository (mediawiki_selenium) or in tests/browser folder, or in /modules/ve-mw/test/browser folder (VisualEditor).
+
+The first line in the Gemfile should be changed from:
+
+#ruby=ruby-2.1.0
+
+to
+
+#ruby=ruby-2.1.1
+
+Then, Jenkins jobs that run Selenium tests should be updated. The repository is located here:
+
+https://github.com/zeljkofilipin/jenkins-job-builder-config
+
+Find all files that contain this:
+
+RUBY_VERSION=2.1.0
+
+and replace it with:
+
+RUBY_VERSION=2.1.1
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1393865280,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-lcdwdqoqbndlmqibkajx,task_description,resolved
+Upgrade Ruby to version 2.1.1,(Should've been changed back to RESOLVED FIXED over a month ago.),1407267501,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 141134 abandoned by Alex Monk:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/141134",1403359394,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 141134 had a related patch set uploaded by Inchikutty:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/141134",1403352876,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"I have pushed the changes to Cloudbees, Ruby 2.1.1 installs just fine:
+
+https://wmf.ci.cloudbees.com/job/CirrusSearch-en.wikipedia.beta.wmflabs.org-linux-firefox/42/console",1394022585,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"(In reply to Vikas from comment #16)
+> I have sent you pull request from github to Jenkins jobs. Here is the link
+> 
+> https://github.com/zeljkofilipin/jenkins-job-builder-config/pull/1
+
+Merged into master branch.",1394021890,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116705 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116705",1394017908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116704 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116704",1394017887,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116708 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116708",1394016931,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116707 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116707",1394016903,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116709 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116709",1394016829,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116710 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116710",1394016817,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116711 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116711",1394016751,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116715 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116715",1394016698,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116716 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116716",1394016653,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116522 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116522",1394016631,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116712 merged by jenkins-bot:
+[Browser tests] Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116712",1394016508,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116529 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116529",1394016387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116706 merged by jenkins-bot:
+QA: Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116706",1393975011,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116700 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1 in tests/browser
+
+https://gerrit.wikimedia.org/r/116700",1393946469,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116713 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116713",1393924515,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"I have sent you pull request from github to Jenkins jobs. Here is the link
+
+https://github.com/zeljkofilipin/jenkins-job-builder-config/pull/1",1393910405,PHID-USER-b5bosdf7b7zp3vqofbug,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116522 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116522",1393908508,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116529 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116529",1393908481,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116700 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1 in tests/browser
+
+https://gerrit.wikimedia.org/r/116700",1393908393,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116716 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116716",1393905780,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116715 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116715",1393905630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116713 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116713",1393905247,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116712 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116712",1393904603,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116711 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116711",1393904358,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116710 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116710",1393904157,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116709 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116709",1393903985,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116708 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116708",1393903761,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116707 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116707",1393903714,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116706 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116706",1393903051,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116705 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116705",1393902648,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116704 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116704",1393902256,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+VisualEditor: Cannot go to a newline after undoing a heading format and Uncaught TypeError: Cannot call method 'getModel' of null appears in the console,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Create a heading
+3.Undo creating the heading and type something in that line instead
+4.Press enter
+
+Observed Result:
+
+Uncaught TypeError: Cannot call method 'getModel' of null appears in the console and user cannot go to the next line anymore and has to cancel that session.
+
+See the screenshot attached,
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:
+https://test2.wikipedia.org/w/index.php?title=27thfebchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13193}",1393529760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k2jmjawnw4bqcn7k66fw,task_description,resolved
+VisualEditor: Cannot go to a newline after undoing a heading format and Uncaught TypeError: Cannot call method 'getModel' of null appears in the console,"I'm going to take a wild guess and claim that this is a DUPE of bug 59911, but we should verify.
+
+*** This bug has been marked as a duplicate of bug 59911 ***",1393530490,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k2jmjawnw4bqcn7k66fw,task_subcomment,NA
+VisualEditor: Cannot go to a newline after undoing a heading format and Uncaught TypeError: Cannot call method 'getModel' of null appears in the console,"It happens in FireFox too, but the error message is different there:
+TypeError: outermostNode is null
+	
+
+...unt=outerParent.getChildren().length;if(outermostNode.type==='listItem'&&outerPa...",1393529979,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k2jmjawnw4bqcn7k66fw,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist","Steps to reproduce:
+
+1.Open a page with VE which has a reflist at the end of the page
+
+2.Place your cursor at the end of the page and press enter to add a newline
+
+Observed Result:
+No newline gets added and an error appears in the console:
+
+
+Uncaught TypeError: Cannot call method 'getModel' of null load.php:268
+ve.ce.Surface.handleEnter load.php:268
+ve.ce.Surface.onDocumentKeyDown load.php:247
+proxy load.php:10
+ve.EventSequencer.onEvent load.php:21
+(anonymous function) load.php:20
+jQuery.event.dispatch load.php:45
+elemData.handle.eventHandle load.php:38
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393368000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6si76vcvgzigcakihtz4,task_description,resolved
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist",This issue got resolved with  bug 59911,1393634687,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6si76vcvgzigcakihtz4,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist","This is almost certainly the same as bug 59911; merging with that.
+
+*** This bug has been marked as a duplicate of bug 59911 ***",1393474369,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6si76vcvgzigcakihtz4,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist","**cornel.punga** wrote:
+
+I confirm it. Reproduced both steps, same error, no newline added.",1393370044,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6si76vcvgzigcakihtz4,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist","Created attachment 14682
+Screenshot
+
+**Attached**: {F12998}",1393368734,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6si76vcvgzigcakihtz4,task_subcomment,NA
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity","Hello,
+French Wikiversity need help to fixe the visual editor working on the ""recherche:"" space name.
+Thanks a lot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393274880,PHID-USER-mxwamhfxuzomk4umydpl,PHID-TASK-sdhut7ee3wusfacg3uhp,task_description,resolved
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity","Now done. If you want any further changes, happy to help!",1393289954,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sdhut7ee3wusfacg3uhp,task_subcomment,NA
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity","Change 115299 merged by jenkins-bot:
+Enable VE in the ""Recherche:"" (104) namespace for frwikiversity
+
+https://gerrit.wikimedia.org/r/115299",1393286747,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdhut7ee3wusfacg3uhp,task_subcomment,NA
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity","Change 115299 had a related patch set uploaded by Jforrester:
+Enable VE in the ""Recherche:"" (104) namespace for frwikiversity
+
+https://gerrit.wikimedia.org/r/115299",1393276836,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdhut7ee3wusfacg3uhp,task_subcomment,NA
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity",No problem. Do you also want it on the Projet / Faculté / Département namespaces?,1393275125,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sdhut7ee3wusfacg3uhp,task_subcomment,NA
+VisualEditor:  Cursor behavior inconsistent when setting redirects,"Steps to reproduce:
+
+1.  Go to Page settings to set a redirect.  
+
+2.  Skip the tick box; just click in the field and type in your page name.
+
+3.  Apply changes.
+
+4.  Change your mind.  Go back to Page settings.  Untick the checkbox.
+
+5.  Apply changes.
+
+6.  Figure out the perfect target.  Go back to Page settings.  
+
+7.  Skip the tick box, just like you dud in Step 2; just click in the field.  Why won't it let me type there now?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1393271520,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-355w7hlobmllbrlusrps,task_description,resolved
+VisualEditor:  Cursor behavior inconsistent when setting redirects,"(In reply to WhatamIdoing from comment #0)
+> 7.  Skip the tick box, just like you dud in Step 2; just click in the field.
+> Why won't it let me type there now?
+
+Because it shouldn't have let you type there initially (bug 61864), but there was a line missing from the logic.
+
+*** This bug has been marked as a duplicate of bug 61864 ***",1393272393,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-355w7hlobmllbrlusrps,task_subcomment,NA
+VisualEditor: Parameter box is too small,"picture of the box
+
+Parameter box is too small
+
+How to reproduce:
+1) go to https://en.wikipedia.org/wiki/Saint_Titus?veaction=edit
+2) click the ""multiple issues"" template on the top of the page and click ""transclusion""
+
+there is in the ""issues"" box:
+
+{{refimprove|date=December 2010}}
+{{lead too short|date=July 2013}}
+
+and I only can see a blank row and little bit of the first line of text. Boxes should be resizable/moveable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12824}",1393268700,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-2gcwk5t4olp3qx43ljc7,task_description,resolved
+VisualEditor: Parameter box is too small,"This is the same as 61289 which is already fixed and will be release to MediaWiki.org this Thursday.
+
+*** This bug has been marked as a duplicate of bug 61289 ***",1393271161,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2gcwk5t4olp3qx43ljc7,task_subcomment,NA
+"VisualEditor:  Make references visible for re-use when they're 'hidden' inside templates, e.g., list-defined refs in the reflist template","This is related to Bug 57209.
+
+List-defined references (https://en.wikipedia.org/wiki/Wikipedia:LDR#WP:LDR) are listed in the {{reflist}} template rather than in the regular text of the page. References that are defined inside the {{reflist}} are not visible when you try to re-use an existing reference.
+
+Steps to reproduce:
+
+1. Open a page that uses list-defined references with the {{reflist}} template (rather than <references></ref>).
+
+2. Go to Insert > Reference to add a new reference.  Click ""Re-use existing reference"".
+
+3. Discover that the numbers (""[1]"") and ref names are visible, but the contents are not.
+
+This problem does not exist if the non-template method is used.  This problem also exists for refs inside blockquotes, infoboxes, and other templates.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393019340,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-mw46y7ei5hcau3e3zb6y,task_description,invalid
+"VisualEditor:  Make references visible for re-use when they're 'hidden' inside templates, e.g., list-defined refs in the reflist template","Not possible without re-writing the Cite extension from scratch, which is sort-of planned but won't be done before 2015 at the earliest. Marking as ""INVALID"", but it's mostly a ""can't fix"".",1393537301,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mw46y7ei5hcau3e3zb6y,task_subcomment,NA
+VisualEditor: Gallery Highlight is not getting redrawn in correct position while changing the Heading style applied on it,"Screenshot-1
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a gallery
+3.Select the gallery and apply the formated Preformatted and observe the blue highlight box
+4.Deselect and again select the gallery
+5.Change the format to Paragraph to Heading and observe the position of the blue highlighted box
+
+Observed Result:
+The highlight box does not get reposition according to the new position of the gallery.
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/21stfebff?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13200}",1393012860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3jt32w56utgsiwksttva,task_description,resolved
+VisualEditor: Gallery Highlight is not getting redrawn in correct position while changing the Heading style applied on it,"Galleries can no longer take a paragraph style, which is correct and fixes this bug.",1402921436,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3jt32w56utgsiwksttva,task_subcomment,NA
+VisualEditor: Gallery Highlight is not getting redrawn in correct position while changing the Heading style applied on it,"Created attachment 14655
+Screenshot
+
+**Attached**: {F13201}",1393012989,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3jt32w56utgsiwksttva,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"Intention:
+Open https://en.wikipedia.org/wiki/Afroyim_v._Rusk (TFA) in VisualEditor.
+
+Steps to Reproduce:
+1. Click to the Main Page.
+2. Click to the article (https://en.wikipedia.org/wiki/Afroyim_v._Rusk)
+3. Click on ""Edit beta"".
+4. Wait a long time.
+5. Discover two copies of the entire article.
+
+Actual Results:  
+Two copies of the article appear, one above the other.  This happens in Safari 6 but not in Firefox 27; it happens only when editing the actual mainspace page, not when editing a copy in a sandbox.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392924060,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yifu433xtyd2cz6f7zjy,task_description,declined
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"(In reply to WhatamIdoing from comment #4)
+> I can't reproduce this right now.  However, the timestamp on the screenshot
+> is 10:55 a.m. PST (and it had been onscreen for a few minutes before then),
+> and I thought that the deployment was set to start about five minutes after
+> that.
+
+The new version went a little early today, apparently (but only by a few minutes – see https://wikitech.wikimedia.org/wiki/Server_Admin_Log#February_20 where ""testwiki to 1.23wmf15 and build l10n cache"" at 16:58, though the changes start a couple of minutes before the log), but there were bigger issues involving deployment today that took down all the phase0 wikis (yay). Nothing to do with VisualEditor, but might well have caused random and otherwise inexplicable issues like this.
+
+However, for enwiki changes didn't happen until 21:26, so it /shouldn't/ have been affected, so it's a bit of a mystery. :-(
+
+Marking as WORKSFORME for now.",1392940376,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"I can't reproduce this right now.  However, the timestamp on the screenshot is 10:55 a.m. PST (and it had been onscreen for a few minutes before then), and I thought that the deployment was set to start about five minutes after that.",1392936289,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"I've just loaded it 5 times (with hard refreshes) each in Chrome, Safari and Firefox, without incident – perhaps it could be an odd cacheing issue with the switch-over to the new version?
+
+Can you reproduce still?",1392924580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"I have just managed to get the article to open with a single copy, so this is intermittent.  
+
+Also, notice the absence of VisualEditor's toolbar.  The top of the attached image is the top of the browser window.",1392924214,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"Created attachment 14636
+Screenshot showing the bottom of first copy of the article and the top of the second copy.
+
+**Attached**: {F13022}",1392924108,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),"* Latest master mediawiki-core and VisualEditor
+* Edit Worksheet page
+* Open ""Options"" dialog
+
+Nothing happens, console shows:
+
+
+
+ Uncaught TypeError: undefined is not a function
+ >         this.tableOfContents = new OO.ui.FieldLayout(new OO.ui.ButtonSelectWidget({'$': this.$}).addItems([new OO.ui.ButtonOptionWidget('mwTOCForce', {'label': ve.msg('visualeditor-dialog-meta-settings-toc-force')}), new OO.ui.ButtonOptionWidget(
+ VeUiMWSettingsPage
+ ve.ui.MWMetaDialog.initialize
+ oo.EventEmitter.emit
+ (anonymous function)
+ pollExternalStylesheets
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1392864900,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hfgaosahvwicr3n3m3lj,task_description,declined
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),"[19:12]	Krinkle	Yeah, I just updated mw-core again and it works now",1392865971,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hfgaosahvwicr3n3m3lj,task_subcomment,NA
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),This works fine for me with the current MW core. Ensure you have https://gerrit.wikimedia.org/r/#/c/113508/ .,1392865953,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hfgaosahvwicr3n3m3lj,task_subcomment,NA
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),> OO.ui.FieldLayout is undefined,1392865156,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hfgaosahvwicr3n3m3lj,task_subcomment,NA
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),(Can still reproduce on VisualEditor @ 0b97870 after todays' merges),1392865011,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hfgaosahvwicr3n3m3lj,task_subcomment,NA
+VisualEditor: Redirects have ./ added to them in round-trip,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Page Settings
+3.Check the box Redirect this page to and specify the page/article to which it will redirect to.
+4.Apply changes
+5.Save the page
+6.Reopen VE for this page
+
+
+Observed Result:
+The page settings page pops up with ./ appended as prefix to the article name
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/19thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13414}",1392855420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-g6ao2orn4uf6igum3xuw,task_description,resolved
+VisualEditor: Redirects have ./ added to them in round-trip,Verified the fix in test2,1392944712,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-g6ao2orn4uf6igum3xuw,task_subcomment,NA
+VisualEditor: Redirects have ./ added to them in round-trip,"Change 114381 merged by jenkins-bot:
+Deal with ./ prefixes etc. in MWRedirectMetaItem
+
+https://gerrit.wikimedia.org/r/114381",1392860306,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g6ao2orn4uf6igum3xuw,task_subcomment,NA
+VisualEditor: Redirects have ./ added to them in round-trip,"Change 114381 had a related patch set uploaded by Catrope:
+Deal with ./ prefixes etc. in MWRedirectMetaItem
+
+https://gerrit.wikimedia.org/r/114381",1392860099,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g6ao2orn4uf6igum3xuw,task_subcomment,NA
+VisualEditor: Redirects have ./ added to them in round-trip,"(In reply to ryasmeen from comment #0)
+> Created attachment 14632 [details]
+> Screenshot
+> 
+> Steps to reproduce:
+> 
+> 
+> 1.Open a page with VE
+> 2.Go to Page Settings
+> 3.Check the box Redirect this page to and specify the page/article to which
+> it will redirect to.
+> 4.Apply changes
+> 5.Save the page
+> 6.Reopen VE for this page
+> 
+> 
+> Observed Result:
+> The page settings page pops up with
+That's a feature.
+
+> ./ appended as prefix to the article name
+>
+That's a bug :(
+
+**Attached**: {F13414}",1392856659,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-g6ao2orn4uf6igum3xuw,task_subcomment,NA
+VisualEditor: Adding content with newline in Edit source mode appears with return arrow in VE mode then placing the content in the preceding line,"Screenshot
+
+Steps to reproduce:
+
+1.Go to Edit Source mode
+2.Add a text or anything else in a newline
+3.Save the page
+4.Open the page with VE
+
+Observed Result:
+The newly added text gets merged with the previous line adding a return character between the lines.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/19thfebchrome?veaction=edit
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13402}",1392853920,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n5bah7oda2vyaqmkor4k,task_description,resolved
+VisualEditor: Adding content with newline in Edit source mode appears with return arrow in VE mode then placing the content in the preceding line,"
+
+*** This bug has been marked as a duplicate of bug 48290 ***",1393537023,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n5bah7oda2vyaqmkor4k,task_subcomment,NA
+Stop specifying the (default) size of media items in VisualEditor,"If you add ""File:Example.jpg"", without actively specifying a size, then you should get [[File:Example.jpg|thumb|Here is a caption]].  You should not get [[File:Example.jpg|thumb|220x220px|Here is a caption]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392851220,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ilhxonhqlmyxfkhaqn34,task_description,resolved
+Stop specifying the (default) size of media items in VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 61324 ***",1393447031,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ilhxonhqlmyxfkhaqn34,task_subcomment,NA
+VisualEditor: Word missing from wikilink,"During a test,
+I tried to create a wikilink to
+http://fr.wikipedia.org/wiki/Cabin_Fever:_Patient_Zero .
+What I did was writing Cabin Fever: Patient Zero,
+then selecting all the 4 words, copy/pasting that precise URL and selecting the ""red"" option in the dropdown menu as if to link to a new page.
+The result is https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve2&diff=101406090&oldid=101406077 ,
+that shows up as [Fever: Patient Zero] in view mode, while the wikicode shows the word Cabin as an existing part of the label.
+This happened on both Chrome and FF, Win7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392833640,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mbgornmacv5hvpihufw2,task_description,resolved
+VisualEditor: Word missing from wikilink,Seems to be fixed now.,1437687504,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-mbgornmacv5hvpihufw2,task_subcomment,NA
+VisualEditor: Pressing tab does not take the cursor to the next field/parameter in a template dialog box,"Steps to reproduce:
+
+
+1.Open a page in VE
+2.Go to Insert>Transclusion
+3.Search for a template like Cite Web
+4.Click on ""Add template""
+5.When all the parameters appear, insert a value in one of the parameters then press tab to go to the next parameter.
+
+Observed Result:
+Pressing tab does take user to the next tab
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/New_deep?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392774900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u54zpp3nlpyzgygilqys,task_description,resolved
+VisualEditor: Pressing tab does not take the cursor to the next field/parameter in a template dialog box,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394827111,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u54zpp3nlpyzgygilqys,task_subcomment,NA
+VisualEditor: Pressing tab does not take the cursor to the next field/parameter in a template dialog box,Verified the fix in test2 environment,1394153427,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u54zpp3nlpyzgygilqys,task_subcomment,NA
+VisualEditor: Return arrow is getting placed after every element inside Reference Dialog box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in VE
+2.Add a reference to the page
+3.Open the reference dialog box
+4.Add a text
+5.Go to the next line and then a Cite web template 
+6.Go to the next line and add a math funtion
+7.Save the page
+8.Reopen the page and open the reference dialog box
+
+Observed Result:
+After every element return arrow is getting placed.
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/18thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13281}",1392755580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iij5s3q5lqjww4xxudga,task_description,invalid
+VisualEditor: Return arrow is getting placed after every element inside Reference Dialog box,"I think this is just an artefact of ""↵"" characters being show for the <br />s put in by Parsoid…",1406754132,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iij5s3q5lqjww4xxudga,task_subcomment,NA
+VisualEditor Math plugin displayed equation becomes jumbled during and after editing if using MathJax,"Split off from bug 43058.
+
+Editing the last equation at 
+https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+
+if you actually make a change to the text of the equation the displayed equation becomes very jumbled. Any vertical positioning is lost, and text from different lines are overlaid on top of each other.
+
+This happens with Chrome on a Mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52499",1392739320,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-se5cgamgbkdgfzjnta6l,task_description,declined
+VisualEditor Math plugin displayed equation becomes jumbled during and after editing if using MathJax,MathJax will be removed T99369,1437345483,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-se5cgamgbkdgfzjnta6l,task_subcomment,NA
+VisualEditor Math plugin displayed equation becomes jumbled during and after editing if using MathJax,"The problem seems to be a clash of CSS styling. MathJax makes heavy use of position: absolute, position: relative and setting the top, and left properties eg
+
+<span style=""position: absolute; clip: rect(1.501em 1000.003em 2.347em -0.518em); top: -2.145em; left: 0.003em;"">...</span>
+
+yet this is all rendered to nothing by the CSS rule
+
+.ve-ce-protectedNode, .ve-ce-protectedNode * {
+  position: relative !important;
+  top: 0 !important;
+  left: 0 !important;
+  bottom: 0 !important;
+  right: 0 !important;
+  ...
+}
+
+If you comment out these css properties the MathJax displays OK.",1398718384,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-se5cgamgbkdgfzjnta6l,task_subcomment,NA
+VisualEditor Math plugin displayed equation becomes jumbled during and after editing if using MathJax,"Created attachment 15234
+Screenshot of garbled output
+
+This is a screenshot of the type of output obtained. You need MathJax on and image will become garbled as soon as the formula is edited with the VisualEditor formulae editing beta feature.
+
+**Attached**: {F13244}",1398717990,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-se5cgamgbkdgfzjnta6l,task_subcomment,NA
+"Messages ""symbols"", ""accents"", ""math"" in special character inserter tool not translatable","The special character inserter tool has hard-coded texts which are not translatable.
+
+There is texts ""symbols"", ""accents"" and ""math"" which are not translatable, because there is no existing MediaWiki messages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392561840,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-qe7ct72pnrg4lcr747kr,task_description,invalid
+"Messages ""symbols"", ""accents"", ""math"" in special character inserter tool not translatable","(In reply to Stryn from comment #1)
+> I guess
+> https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-
+> specialcharinspector-characterlist-insert/en is the one that needs to be
+> translated.
+
+Correct.",1392741532,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qe7ct72pnrg4lcr747kr,task_subcomment,NA
+"Messages ""symbols"", ""accents"", ""math"" in special character inserter tool not translatable","BTW I just saw https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Feedback_for_the_character_inserter/reply_%2836%29
+
+so I guess https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-specialcharinspector-characterlist-insert/en is the one that needs to be translated.",1392569902,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-qe7ct72pnrg4lcr747kr,task_subcomment,NA
+VE is unable to insert a internal reference with sub-section,"**Author:** `paulomsimoes`
+
+**Description:**
+VE is unable to insert a internal reference with sub-section. Example:
+
+[[""Wikipédia Article name""#""Section name""]], return only [[""Wikipédia Article name""]] (without redirect to section), as per [https://pt.wikipedia.org/w/index.php?title=Faculdade_Salesiana_de_Maca%C3%A9&diff=38176530&oldid=38176349|this edit].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1392505740,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xbwpkppvqworctg5ub5j,task_description,resolved
+VE is unable to insert a internal reference with sub-section,"I don't understand this bug report, sorry.
+
+It is certainly possible right now to write ""Foo#Bar"" as your target, though VisualEditor doesn't validate ""#Bar"" as being a valid section so it may be confusing…
+
+Do you mean that you would expect the link inspector to understand sections and give a better experience for that? If so, I think this is bug 50881. Provisionally merging with that one.
+
+*** This bug has been marked as a duplicate of bug 50881 ***",1401417280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xbwpkppvqworctg5ub5j,task_subcomment,NA
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","**Author:** `jhall`
+
+**Description:**
+The VisualEditor headings.feature has begun to fail[1] when run via CloudBees (but not when run locally).  Relevant Selenium log message is (example is for the ""Subheading1"" scenario, but the pattern is the same for all scenarios in this test):
+
+00:25:21.230 INFO - Executing: [find element: By.xpath: .//a[@title='^3']] at URL: /session/83a0781b-247c-4f0a-88f8-a93cef166a15/element)
+00:25:21.247 WARN - Exception thrown
+org.openqa.selenium.NoSuchElementException: Unable to locate element: {""method"":""xpath"",""selector"":"".//a[@title='^3']""}
+Command duration or timeout: 13 milliseconds
+For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
+Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16 16:11:15'
+System info: host: 'chef', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'i386', os.version: '3.2.0-56-virtual', java.version: '1.6.0_31'
+Session ID: 185a49ff-3267-43a3-ad44-3e6881cd0d43
+Driver info: org.openqa.selenium.firefox.FirefoxDriver
+Capabilities [{platform=LINUX, acceptSslCerts=true, javascriptEnabled=true, browserName=firefox, rotatable=false, locationContextEnabled=true, version=26.0, cssSelectorsEnabled=true, databaseEnabled=true, handlesAlerts=true, browserConnectionEnabled=true, nativeEvents=false, webStorageEnabled=true, applicationCacheEnabled=true, takesScreenshot=true}]
+
+The problem does not repro when the test is run on a MacBook, and the insertion of the following command into the headings_steps.rb file at appropriate points succeeds as expected:
+
+@browser.a(:xpath, "".//a[@title='^3']"").should exist
+
+Need to figure out why these test scenarios fail when run via CloudBees, since they seem to be perfectly legitimate test cases.
+
+[1] https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/327/testReport/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1392418260,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_description,resolved
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","Chris, since we are moving away from Cloudbees, do you plan to investigate this or should be close it?",1398414326,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_subcomment,NA
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","All patches merged - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?",1398408179,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_subcomment,NA
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","Change 114114 merged by jenkins-bot:
+[Browser test] Repair broken ""header"" browser test
+
+https://gerrit.wikimedia.org/r/114114",1392771414,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_subcomment,NA
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","Change 114114 had a related patch set uploaded by Jhall:
+[Browser test] Repair broken ""header"" browser test
+
+https://gerrit.wikimedia.org/r/114114",1392770355,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"screenshot
+
+Steps to reproduce
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Insert the search string ""April""
+
+Observed Result:
+
+An error appears in the console:
+Uncaught TypeError: Cannot read property '0' of undefined 
+
+and the search spinner continues indefinitely
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=14thfebchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12972}",1392407400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7ho2brlduxnhg2gejymz,task_description,resolved
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,Verified the fix on betalabs,1392939924,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"That, too, *should* be fixed with this commit.",1392431275,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"Change 113478 merged by jenkins-bot:
+Only display image info if that exists
+
+https://gerrit.wikimedia.org/r/113478",1392430497,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"There is another error appearing while I search for hoo:
+load.p...014333Z (line 583)
+TypeError: this.data.imageinfo is undefined
+
+Not Sure if it is related with this particular issue or not.",1392429573,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"Change 113478 had a related patch set uploaded by Mooeypoo:
+Only display image info if that exists
+
+https://gerrit.wikimedia.org/r/113478",1392419669,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor: All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in test 2
+
+2.Select an image
+
+3.Go to the Media Settings >Advanced Settings for that image
+
+Observed Result:
+ All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2
+
+See the screenshot attached
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/13thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12856}",1392330060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-piljwz7ejgbgmrwmptju,task_description,resolved
+VisualEditor: All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2,Verified the fix on test 2,1392406219,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-piljwz7ejgbgmrwmptju,task_subcomment,NA
+VisualEditor: All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2,"Deployment issue, now fixed.",1392405621,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-piljwz7ejgbgmrwmptju,task_subcomment,NA
+VisualEditor: Blank edit notices for admins on each page at English Wikipedia,"As an admin on en.wp, I get a blank edit notice popup on every page I edit, with a red link to the page notice. I seem to recall that this is some interaction with local site JS/CSS, and that this was fixed at some point in the past.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43013",1392322980,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ciemclcqodgd6pk6mejb,task_description,resolved
+VisualEditor: Blank edit notices for admins on each page at English Wikipedia,"Merging into bug 43013. Gah. :-(
+
+*** This bug has been marked as a duplicate of bug 43013 ***",1394490038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ciemclcqodgd6pk6mejb,task_subcomment,NA
+VisualEditor: Page Suggestions in link inspector are not appearing in FireFox on Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Create a link which has a target of existing page or a new page
+
+Observed Result:
+There is no drop down appearing with matched pages suggestion or a new page section.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:FF 25
+OS: MAC OS X 10. 8. 5
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_%28WMF%29&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13342}",1392240360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6hvjba3tuflbtzmptodb,task_description,declined
+VisualEditor: Page Suggestions in link inspector are not appearing in FireFox on Betalabs,I'm going to write this one us as a server issue.,1402550077,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6hvjba3tuflbtzmptodb,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"To reproduce:
+
+1. Go to https://en.m.wikipedia.org/wiki/ASCII in desktop Firefox.
+2. Press the pencil button to edit.
+
+Expected: The mobile editing is supposed to open.
+Observed:
+1. The editing interface doesn't open. The page stays the same.
+2. The following errors are displayed in the JS console:
+
+""Exception thrown by job.error"" (load.php:145)
+""Error: Container must be attached to the DOM"" [object Error] (load.php:145)
+
+This works in desktop Google Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392153780,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ljbacnsrtxmpcftewdk3,task_description,declined
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"(In reply to Juliusz Gonera from comment #6)
+> Also, Amir, if you're getting ""Error, can't load section."" on your local
+> instance that probably means you're trying to use VE without running Parsoid.
+
+Oh, useful to know. Thanks.",1392418256,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"**jgonera** wrote:
+
+Also, Amir, if you're getting ""Error, can't load section."" on your local instance that probably means you're trying to use VE without running Parsoid.",1392402195,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"The behavior described sounds like this was in experimental and likely an issue with VisualEditor. I am entirely unable to reproduce in FF or Chrome, in stable, beta, or alpha. I assume the issue was fixed since this was reported, so marking as WORKSFORME. Amir, please reopen if the issue is still present and let us know if you're in stable/beta/alpha.",1392401990,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"I can't reproduce in any mode, including experimental (on en.wiki or local master). Can someone verify whether or not it is still reproducable?",1392401949,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1697",1392400354,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"If I try this on my local machine on master, I get something a bit different: I don't see JS errors, but I see a notification drawer at the bottom of the page:
+""Error, can't load section.""",1392194143,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,I can reproduce this in experimental mode (not in standard or beta).,1392159139,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+VisualEditor:  Media Settings dialog always goes back to General settings if you switch windows while in Advanced settings,"Intention:
+Look up something in another window
+
+Steps to Reproduce:
+1. Open Media settings for an existing image, using Safari.
+
+2. Click on ""Advanced settings"".  Don't click inside any text field (e.g., width or height).
+
+3. Decide that you need to go to another window or browser tab for a moment, so click elsewhere.
+
+4. Go back to VisualEditor.
+
+5. Discover that the Media settings dialog has put you back in ""General settings"" again.
+
+Converse is also true:  if you put the text cursor in the ""Height"" box and then switch to ""General settings"" before leaving the page for a moment, you will be flipped back to ""Advanced settings"".
+
+
+
+Reproducible: Always
+
+Reproducible in Safari, not in Firefox.  Perhaps it's because Safari ""helpfully"" flips the box to wherever the text cursor is, and Firefox ignores it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392144240,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-olyocmpjb6k7cvxtzx7a,task_description,resolved
+VisualEditor:  Media Settings dialog always goes back to General settings if you switch windows while in Advanced settings,"
+
+*** This bug has been marked as a duplicate of bug 61062 ***",1392144760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-olyocmpjb6k7cvxtzx7a,task_subcomment,NA
+VisualEditor:Double return arrow getting added after adding Galley just before a hiero,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a special character 
+3.Add a hiero on the next line
+4.Save the page 
+5.Reopen the page, add a gallery just after the special character but before hiero
+6.Save the page
+7.Reopen the page
+
+Observed Result:
+Double arrow appears just after gallery but before hiero
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Justhiero?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13041}",1392082080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nbxtzfyyzyj53uup2gmf,task_description,resolved
+VisualEditor:Double return arrow getting added after adding Galley just before a hiero,These don't show now; I think the upstream Parsoid fixes will have helped.,1406754182,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nbxtzfyyzyj53uup2gmf,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"Steps to reproduce:
+
+1.Open the page in VE
+2.Add an image
+3.Go to Media Settings>Advanced Settings
+4.Change the image type to Thumbnail ,Frame or Border
+5.Apply the changes
+
+Observed Result:
+There is no apparent different in either of these image types when selected
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=10thFeb&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392063240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dd4n7egyr75tqjapspdy,task_description,invalid
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,Per Moriel's statement in comment 4.,1395354454,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"Turns out: This is intended behavior.
+
+Images with |frameless but no position render as inline images in both Parsoid and the PHP Parser. That is, apparently, intended, as counterintuitive as it may be.
+
+Since we can't edit inline images just yet in VE, this turns out to be a bit of a hassle (and a bug) -- but hopefully very soon we'll be able to edit inline images in the media edit dialog, which would solve the issue of having the resulting image uneditable.",1392097815,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"Okay, for some reason, when an image has |frameless but no position set, VE intercepts it as an inline image.
+
+So, when a new image is inserted, the position is set to default (no representation in the wikitext) and when we set it to ""frameless"" it results in the following wikitext:
+
+[[File:Diplopedia main page.jpg|frameless|150x150px|]]
+
+It seems that since it's missing a position, VE reads it as an inline image.",1392066596,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"Sorry little change in the steps to reproduce:
+
+1.Open the page in VE
+2.Add an image
+3.Go to Media Settings>Advanced Settings
+4.Change the image type to Frameless
+5.Save the page
+6.Reopen the editor and go the media settings again
+7.Now change the image type to Thumbnail, then frame
+
+Observed Result:
+There is no thumbnail icon getting added in the VE mode unless user saves it, and then if he changes to frameless, it also looks pretty similar to the type thumbnail because both of them has no thumbnail icon beside the caption field.
+
+Selecting border also does not make any change compared to frameless which has a separate ticket:https://bugzilla.wikimedia.org/show_bug.cgi?id=61155",1392064737,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"I can't manage to reproduce in master in both Firefox 26.0 and Chrome 32.0 under Ubuntu.
+
+A new inserted image is inserted as ""thumb"" which is what I see selected in the media edit dialog when it's opened. Changing to ""frameless"" changes the type (and changes the view properly for me) as well as changing to ""Framed"" (though that one is a bit more subtle, because the difference between them isn't too noticeable)
+
+It seems to work for me as expected in master.",1392063878,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+Insert Media only searches commons,"**Author:** `robert.labrie`
+
+**Description:**
+The VisualEditor insert media only searches commons. I have a media item called ""WOM HighLevelDesign.png"" but when searching for HighLevelDesign there are no results. Looking at the request in Firebug:
+
+Request:
+GET http://commons.wikimedia.org/w/api.php?callback=jQuery18305320913342615314_1392057641882&format=json&action=query&generator=search&gsrsearch=HighLevelDesign&gsrnamespace=6&gsrlimit=15&gsroffset=0&prop=imageinfo&iiprop=dimensions%7Curl&iiurlheight=150 HTTP/1.1
+Host: commons.wikimedia.org
+User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0
+Accept: */*
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate
+Referer: http://opsdocs.carnival.com/index.php?title=Main_Page&veaction=edit
+Connection: keep-alive
+
+Response:
+HTTP/1.1 200 OK
+Via: 1.1 varnish, 1.1 varnish, 1.1 CCLPRDINFTMG3
+Connection: Keep-Alive
+Proxy-Connection: Keep-Alive
+Content-Length: 110
+Age: 0
+Date: Mon, 10 Feb 2014 19:33:02 GMT
+Content-Type: text/javascript; charset=utf-8
+Server: Apache
+Accept-Ranges: bytes
+X-Powered-By: PHP/5.3.10-1ubuntu3.9+wmf1
+x-content-type-options: nosniff
+Cache-Control: private
+x-frame-options: SAMEORIGIN
+Vary: Accept-Encoding,X-Forwarded-Proto
+X-Vary-Options: Accept-Encoding;list-contains=gzip,X-Forwarded-Proto,Cookie;string-contains=commonswikiToken;string-contains=commonswikiLoggedOut;string-contains=forceHTTPS;string-contains=commonswikiSession;string-contains=centralauth_Token;string-contains=centralauth_Session;string-contains=centralauth_LoggedOut;string-contains=mf_useformat;string-contains=stopMobileRedirect
+X-Varnish: 2999015801, 4264856558
+X-Cache: cp1055 miss (0), cp1052 frontend miss (0)
+
+
+jQuery18305320913342615314_1392057641882({""query"":{""searchinfo"":{""totalhits"":0,""suggestion"":""Hauserdesign""}}})
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392060960,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-irielkewu77v4z4a3hlm,task_description,invalid
+Insert Media only searches commons,This issue seems to be address with open task T188236,1717447423,PHID-USER-3baphe4xso6l4kkryqex,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,"Marking as INVALID; this isn't a bug in VisualEditor, but an artefact of the (not very good) search system in MediaWiki (and a continuing issue even with CirrusSearch).",1392774395,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,Can you also add a direct link to the image?,1392148110,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,"I've CC'd Nik Everitt, our CirrusSearch guru, to see if he can provide any insight.",1392147662,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,"After a bit of testing and fiddling around, there seems to be an issue with the API call itself and its response. 
+
+The API returns a list of matches by complete words, and it seems that it considers the suffix as a word as well.
+
+So, in my local wiki I have an image ""image of space.jpg"". 
+
+API calls:
+
+&gsrsearch=space.jpg --> 1 match
+&gsrsearch=space --> 0 matches
+&gsrsearch=image --> 1 matches
+&gsrsearch=from --> 0 matches
+&gsrsearch=image+from --> 1 match
+&gsrsearch=image+from+space --> 0 matches
+
+I am not sure if this is because of the specific query we use to search images or if this is an artefact of the API itself. 
+
+I'm conducting further research.
+
+Robert, if you have time to test this, try to see if you get the image you are looking for when typing ""HighLevelDesign.png"" or ""WOM"". Are you getting the local image on those searches?",1392146448,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,"**robert.labrie** wrote:
+
+After cleaning my cache and setting $wgUseInstantCommons  = false; the result is now as follows:
+
+GET /api.php?format=json&action=query&meta=filerepoinfo HTTP/1.1
+Host: opsdocs.carnival.com
+User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0
+Accept: application/json, text/javascript, */*; q=0.01
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate
+X-Requested-With: XMLHttpRequest
+Referer: http://opsdocs.carnival.com/index.php?title=Main_Page&veaction=edit
+Cookie: wikidb796_session=86334fa21b8c09bd7c07958bdc0ac86e; wikidb796UserID=2; wikidb796UserName=CARNIVAL%5Crobertla; wikidb796Token=ceb473edd15eddf81147a6c9f583acf3; website#lang=en
+Connection: keep-alive
+
+
+HTTP/1.1 200 OK
+Cache-Control: private
+Content-Type: application/json; charset=utf-8
+Vary: Accept-Encoding
+Server: Microsoft-IIS/8.0
+X-Powered-By: PHP/5.3.24
+x-content-type-options: nosniff
+x-frame-options: DENY
+Persistent-Auth: true
+Date: Mon, 10 Feb 2014 19:55:15 GMT
+Content-Length: 198
+
+{""query"":{""repos"":[{""name"":""local"",""displayname"":null,""rootUrl"":""/images"",""local"":true,""url"":""/images"",""thumbUrl"":""/images/thumb"",""initialCapital"":true,""scriptDirUrl"":"""",""scriptExtension"":"".php""}]}}",1392062660,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+VisualEditor: Text in Insert menu and in Option menu displays differently,"This happens with Monobook (I tried this with Chrome on fr. and it.wp).
+The text in the Option menu is in a larger and different font than the one under Insert.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392060360,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6754fqjnk5hw4q6cz6zc,task_description,declined
+VisualEditor: Gallery remains highlighted even after clicking elsewhere in the page,"Screenshot
+
+Steps to reproduce:
+1.Open a page with Ve
+2.Select a gallery
+3.Open the gallery inspector 
+4.Click else where in the page to close the inspector
+
+Observed Result:
+The gallery remains highlighted in the page though it is not selected and link inspector is not appearing on the gallery
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12831}",1391816040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ximodnbmrouyqq5tnhwi,task_description,resolved
+VisualEditor: Gallery remains highlighted even after clicking elsewhere in the page,Appears to have been fixed a while ago.,1402921625,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ximodnbmrouyqq5tnhwi,task_subcomment,NA
+VisualEditor:  Odd removal of table inside an image caption,"Actual Results:  
+VisualEditor loses most of the table.
+
+
+Reproducible: Couldn't Reproduce
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Misl&diff=594020475&oldid=593707943
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49942",1391814720,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zmktchjngp5bwq3bloha,task_description,declined
+VisualEditor:  Odd removal of table inside an image caption,Probably a browser bug or flakiness.,1415883136,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zmktchjngp5bwq3bloha,task_subcomment,NA
+MathJax equations are centered,"MathJax has started centering displayed equations. For example
+https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:WikiProject_Mathematics&curid=148395&diff=594391082&oldid=594388357
+the display equation is centered. Previously they were aligned left.
+
+Looking at the generated the code we see 
+<div class=""MathJax_Display"" role=""textbox"" aria-readonly=""true"" style=""text-align: center;"">
+  <span class=""MathJax"" id=""MathJax-Element-2-Frame"" style=""""> ...
+  </span>
+</div>
+
+the centering is in the code rather than in a style sheet.
+
+Aligning equations to the left is the desirable format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391801640,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_description,resolved
+MathJax equations are centered,"**physik** wrote:
+
+I could not find any centered equations anymore. Please reopen in case I missed something.",1413758059,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+nageh: Form a client-side perspective this approach is perfectly fine. However, after discussions wiht Gabriel, I'm convinced that there are good (technical) reasons that tag extension should be functionally dependend from their input and not from their context.
+On the other hand this means that the math extension can not decide if the input was :<math or just <math because the : context is hidden.
+The only workable solution is to add an aditional parameter to the math tag.",1396866864,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"(In reply to nageh from comment #27)
+> See, this is what sets me up. ""It's a heuristic written specifically for
+> MediaWiki's math extension."" Bullshit! The heuristic was written
+> specifically for my mathJax user script to cleverly tell apart inline math
+> (where indices of large operators are ordered horizontally) from display
+> math (where indices are stacked). This was actually all explained in bug
+> 35188. And display math has always been left-aligned with my script.
+
+Nageh: I'm not sure what is your intention, but your complaints do not sound very constructive. The comment you state seems to be from Peter Krautzberger so you should ask him directly. But in my opinion, he is just saying that this heuristic is not part of the MathJax code and didn't mean to accuse you of anything. Honestly, I really don't understand why you are getting nervous for that.",1396865303,PHID-USER-5oxfu3gkolxxzkcx3e5n,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**mal.malego** wrote:
+
+See, this is what sets me up. ""It's a heuristic written specifically for MediaWiki's math extension."" Bullshit! The heuristic was written specifically for my mathJax user script to cleverly tell apart inline math (where indices of large operators are ordered horizontally) from display math (where indices are stacked). This was actually all explained in bug 35188. And display math has always been left-aligned with my script.",1396863634,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Change 119010 merged by TheDJ:
+Fix MathJax centers equations
+
+https://gerrit.wikimedia.org/r/119010",1396822113,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Just to add a further complication. 
+
+Bug 37938 is about support for definition lists in VE. As you all know Wikitext plays fast and loose with these transforming : into <dd>. VE being pretty strict with its html does not play nicely with these. I recently found a tricky bug where its difficult to add text after a maths equation 
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_2#Trying_to_add_a_line_after_an_equation
+
+Quite what VE's long term plan for using : as indentation I'm not quite so sure on. 
+
+As to ""heuristic is unwanted by the community"". I think this refers to poll at
+https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Mathematics#Should_display_equations_be_centered.3F
+which was closed at ""Consensus is overwhelmingly in favour of left alignment."". The heuristic was mentioned a little in the discussion. I don't think many really understood what heuristic was about so we can't really conclude what the community  thinks of the idea.",1396821057,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"So to be more accurate, I believe the real issue is that the heuristic forced MathJax's ""display mode"". But because this ""display mode"" does not exist (yet) in MediaWiki, Nageh added this displayAlign: ""left"" config to get MediaWiki's default mode.
+
+Moritz's plan was to generalize the math modes to have, inline/display (the classical modes line in MathJax, TeX, MathML etc) and ""inline displaystyle"" (MediaWiki's default). In his branch, the displayAlign: ""left"" was removed because the display and centering/displaystyle stuff is done elsewhere in MediaWiki. However, because it was hard to get review, he only merged changes step-by-step and unfortunately displayAlign: ""left"" was removed before the whole math modes are ready... So actually the only thing necessary for 119010 was to keep this heuristic and add this config option back.
+
+But as Moritz said on the entry, he is willing to make progress on the new modes and get his work merged, not only to fix bugs. Hopefully, we will recover the desired rendering soon.",1396813759,PHID-USER-5oxfu3gkolxxzkcx3e5n,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"(In reply to nageh from comment #22)
+> And I still don't understand why the ""heuristic is unwanted by the
+> community"" according to the comment in the source file. I thought this was
+> only about that display equations should be left-aligned (which they always
+> were in my code)?
+
+At some point some changes caused the heuristic to force the equation to be centered (probably because we removed displayAlign: ""left"" too early in the development) so that's probably what Moritz meant by ""unwanted by the community"". I think you should not pay too much attention to this comment (actually I believe it should be removed, it's not really useful to have it). The plan to add an explicit display attribute is exactly to avoid this kind of unexpected behaviors and inconsistencies between MathJax/mathoid/LaTeXML/texvc...",1396812806,PHID-USER-5oxfu3gkolxxzkcx3e5n,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**mal.malego** wrote:
+
+And I still don't understand why the ""heuristic is unwanted by the community"" according to the comment in the source file. I thought this was only about that display equations should be left-aligned (which they always were in my code)?",1396811845,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**mal.malego** wrote:
+
+Ha. I do get a bit sensible when I see things being discussed that have long been addressed in my code as if I hadn't done any work on it at all, and when I see comments in the git repository that seem to imply that problems were due to bugs in my code.
+As far as Moritz's efforts are concerned, I'm not exactly familiar with his works but I wish him well and encourage him.
+Peace out.",1396811301,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"(In reply to nageh from comment #19)
+> So far I have ignored all these bug reports, and it seems for good. It is
+> funny how much I am blamed here for all these bugs while clearly my code has
+> had it right from the very start. The heuristic is not about selecting
+> centered or left-aligned maths, it is about deciding the way big operators
+> are rendered. From the very first day my script had included as part of the
+> MathJax config environment
+> displayAlign: ""left""
+> It seems that all my work was in vain, as if it hadn't existed at all. Sigh,
+> I shall not read any of these comments.
+
+I'm not sure where you see that you are blamed. I think everybody recognize your efforts with client-side MathJax on MediaWiki. But if the MathJax option has never been enabled by default, there are good reasons (e.g. performance just to mention one of them). So Moritz has done an awesome work to implement server-side conversion, improves the texvc situation and more. Unfortunately, this is a big and complicate change and review has been slow. The goal is to have the traditional inline mode / display mode that we find in math documents and the default/current MediaWiki rendering ""inline displaystyle"". This handles whether the equation is centered or not and whether the displaystyle is used or not. Moritz has done several versions and branches to try to get the patch accepted and things may have been broken in the battle. Again, I don't think anyone blamed you. I'm sorry to see that you take that personally, instead of encouraging Moritz (and others)'s effort.",1396806384,PHID-USER-5oxfu3gkolxxzkcx3e5n,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**mal.malego** wrote:
+
+So far I have ignored all these bug reports, and it seems for good. It is funny how much I am blamed here for all these bugs while clearly my code has had it right from the very start. The heuristic is not about selecting centered or left-aligned maths, it is about deciding the way big operators are rendered. From the very first day my script had included as part of the MathJax config environment
+displayAlign: ""left""
+It seems that all my work was in vain, as if it hadn't existed at all. Sigh, I shall not read any of these comments.",1396805256,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+https://gerrit.wikimedia.org/r/119010 should fix the problem
+now someone has to do the code review.",1395043650,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Change 119010 had a related patch set uploaded by Physikerwelt:
+Fix MathJax centers equations
+
+https://gerrit.wikimedia.org/r/119010",1395040749,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+For me it looks as I could simply merge my patch that I have already implemented.
+However, I'd like to wait until https://bugzilla.wikimedia.org/show_bug.cgi?id=61006 is merged. Just to be sure, that noting breaks.",1393273493,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Hello,
+
+Thank you for all the work. I just want to say the consensus in the math editor community is to stop centering the equations. So, if possible, you can start fixing this bug.",1392986980,PHID-USER-kwqizcclqreml2x67det,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Just seen there is a related thread on the MathJax mailing list
+  https://groups.google.com/forum/#!topic/mathjax-users/JwE_lr-HtpQ
+Looks like there is a 
+  displayAlign: ""center""
+parameter you can set in the hub see
+  http://docs.mathjax.org/en/latest/options/hub.html
+Things get a bit tricky if we want to allow both left aligned and center aligned equations.",1392363350,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"@physikerwelt why don't you just disable the heuristic? Or as a compromise, instead of making the equation display-style, make it inline but add \displaystyle to it to get display-style layout. 
+
+Whatever comes out of the RFC could inform Math 2.0 for how to implement real display math.",1392326777,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+Are there special system stylesheets that are loaded that do not belong to the default mediawiki schema?",1392228700,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+Hi Richard Morris,
+
+I'm trying to reproduce it the well defined Vagrant development environment as described here. That I set up as described here.
+http://www.formulasearchengine.com/sites/formulasearchengine.com/files/How%20to%20review%20the%20math%20extension_0.pdf
+
+Did anyone manage to reproduce the problem with vagrant?
+It would be very interesting how the production environment differs from vagrant with regard to MathJax. I was thinking that the problem might be related to my browser cache... but I can see the problem at enwiki
+Best
+Physikerwelt",1392146813,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"DOn't know if this helps but a simple example using the MathJax content delivery network creates centered equations.
+
+<html><head>
+<script type=""text/javascript""
+  src=""http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"">
+</script>
+
+<script type=""text/javascript"">
+	MathJax.Hub.Config({
+		jax : [ ""input/TeX"", ""output/HTML-CSS"" ],
+		extensions : [ ""tex2jax.js"" ],
+		""HTML-CSS"" : {
+			scale : 150
+		},
+		tex2jax : {
+			inlineMath : [ [ '$', '$' ], [ '\\(', '\\)' ] ]
+		}
+	});
+</script>
+</head>
+<body>
+<dl>
+<dt>
+$$1 + 2 + 3 + \dots = -{1 \over 12}.$$
+</dt>
+</dl>
+</body>
+</html>
+
+The bit which sets up the centering is in
+https://github.com/mathjax/MathJax/blob/master/jax/output/HTML-CSS/config.js",1392146433,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+mh... bad news. I can not reproduce the problem locally.
+If I copy the example 
+""I use MathJax, so my view may not be typical, but there could be a problem here.
+:<math>a R b \and b R c \rightarrow a R c</math>
+Yep, it's a problem here, also.""
+from the page I get
+""<dl>
+<dd><span class=""MathJax_Preview""></span><span style="""" aria-readonly=""true"" role=""textbox"" id=""MathJax-Element-1-Frame"" ...""
+even though I was using action=purge&debug=true",1392139735,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+oups... I don't like that workaround at all.
+I think I'll force mathjax to render everything on the left side for now.",1392138483,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"An alternative temporary workaround would be to add the CSS rule somewhere in the global site wide CSS or a users common.css
+
+.MathJax_Display { text-align : left !important; } 
+
+this would align all display equations to the left without having to change any wikitext. This would eliminate the problems in comment 6 but does require a friendly admin.",1392138289,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**anmichvon-wikipedia** wrote:
+
+One possible workarround is appending &nbsp; behind the equitation.
+
+:<math>...</math> &nbsp; <!-- hard blank works around bug 61051 -->
+
+But who removes the garbage, when 61051 is fixed? 
+
+So what about a template that just delivers the hard space and can be cleanly deployed and removed by bots?
+
+:<math>...</math> {{Bugfix-61051|Don't touch, will be removed automatically if and when...}}
+
+Possible Contras:
+* Deployment by bot would produce many instances that could affect the servers load. 
+* Bug will be fixed in short time, so don't mess around that much. It just isn't worth the effort.
+* Might collide with other bot jobs involved in the migration from version 1.1 to version 2.0.
+
+Pros:
+* Workable plan to resolve the situation. 
+* No garbage left over after jobs are done, if properly in concert with other operations of the migration.
+
+User:Pyrometer (Home-Wiki: de.wikipedia.org)",1392133652,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"I've just open an RFC on the question of should display equations to be centered? As this affects multiple wiki's is is open to users from all projects.
+
+https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Mathematics#Should_display_equations_be_centered.3F",1392129744,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+Of course I would really get some feedback about this problem from the community...
+Chaning the code is easy... but getting feedback or codereview is realy hard.",1392056849,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+No Math 2.0 will have a selector to switch the style. 
+
+Currently the situation is as follows:
+The PNG mode creates a new latex document for each equation and puts $$ followed by the secured user input followed by $$ into the document body. The resulting dvi image is cropped to that the equation that was rendered centered on a page generated by latex is no longer centered. So it's not centered displaystyle.
+
+The default for Math2.0 intends to keep this layout, but also offers to alternatives ""displaystyle"" which centers equations and ""inline"" which uses the inline mode (so the layout fit's into the text).
+
+To convert the old math elements one could write a bot that transforms 
+:<math> to math elements with the displaystyle property.
+Another bot could search for html math and convert it back to math tags.
+
+I would prefer to keep that two phase approach.
+If this option is merged mathjax will behave like all other rendering modes.
+(Frédéric an me tested that.)
+
+So the centered equation in MathJax are a bug in the middle of changing from version 1.1 to version 2.0",1392056796,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"This is caused by a custom MathJax extension used in the MediaWiki Math Extension, wiki2jax, https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FMath/ff83048597fb256c2579f16ddcd982ef2ae75460/modules%2FMathJax%2Funpacked%2Fextensions%2Fwiki2jax.js. That custom extension contains a simple heuristic (part of the ConvertMath function) to identify display style equations.
+
+> Aligning equations to the left is the desirable format.
+
+IIUC that's simply due to the :<math>...</math> hack which the community adopted because the math extension lacks support for display style -- see  https://bugzilla.wikimedia.org/show_bug.cgi?id=12223. Traditionally, display-style math layout is centered.
+
+I think you opened a discussion about community preference on the WikiProject Math page, too. So perhaps it's best to wait until there's a more definitive response. 
+
+Physikerwelt will correct me, but once Math extension 2.0 is ready, the heuristic would also apply to the default image rendering.
+
+Peter.",1392055423,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,*** Bug 61139 has been marked as a duplicate of this bug. ***,1392043804,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+Ve preview header bar doesn't make sense,"What am I previewing?!
+
+In story 1625 we removed preview from VisualEditor but we left the header in place.
+https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1625
+
+This looks strange as demonstrated by attachment as nothing as being previewed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13434}",1391800260,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-3z36ic6aws767el6smak,task_description,resolved
+Ve preview header bar doesn't make sense,"Change 115550 merged by jenkins-bot:
+Change header message when saving in VE
+
+https://gerrit.wikimedia.org/r/115550",1393455887,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z36ic6aws767el6smak,task_subcomment,NA
+Ve preview header bar doesn't make sense,"Change 115550 had a related patch set uploaded by JGonera:
+Change header message when saving in VE
+
+https://gerrit.wikimedia.org/r/115550",1393374918,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z36ic6aws767el6smak,task_subcomment,NA
+Ve preview header bar doesn't make sense,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1677",1391800526,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3z36ic6aws767el6smak,task_subcomment,NA
+VisualEditor: Table of Contents is not appearing properly in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add Sub-heading 1 to sub-heading 4 
+3.Save the page
+4.Observe the table of contents
+
+Observed Result:
+The table of content is appearing without any style and  order
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan28thff
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13292}",1391722200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gokdl4kwqlwt6cmm66eh,task_description,invalid
+VisualEditor: Table of Contents is not appearing properly in Betalabs,This is due to the Typography refresh Beta Feature.,1394502330,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gokdl4kwqlwt6cmm66eh,task_subcomment,NA
+"VisualEditor: TypeError: OO.ui.IconButtonWidget is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE","Screenshot
+
+TypeError: OO.ui.IconButtonWidget  is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE
+
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13263}",1391716320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5qn7fz4uqtu624ogpnuh,task_description,declined
+"VisualEditor: TypeError: OO.ui.IconButtonWidget is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE",Think this was a deployment issue.,1396380412,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5qn7fz4uqtu624ogpnuh,task_subcomment,NA
+"VisualEditor: TypeError: OO.ui.IconButtonWidget is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE","Also, on load appearing TypeError: this.toolbarSaveButton is null",1391716534,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5qn7fz4uqtu624ogpnuh,task_subcomment,NA
+"VisualEditor: TypeError: OO.ui.IconButtonWidget is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE","This is happening in FireFox.In Chrome, it is working fine.",1391716428,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5qn7fz4uqtu624ogpnuh,task_subcomment,NA
+VisualEditor: No vertical scrollbar on insert media (Firefox),"Intention:
+Insert media file in article using Firefox
+
+Steps to Reproduce:
+0. Open up Firefox
+1. Go to https://sv.wikipedia.org/wiki/Foo?veaction=edit&uselang=en
+2. Click Insert -> Media
+3. Write ""Foo"" in search window
+4. Select image
+5. Click Insert -> Media again
+
+Actual Results:  
+After 3: Image search returns 5*3 images
+After 5: Image search returns more images accessible using the vertical scrollbar
+
+Expected Results:  
+After 3: Image search returns more images accessible using the vertical scrollbar
+
+Reproducible: Didn't try
+
+This problem becomes more severe since beginners don't realise that there are ever more than 15 possible images, meaning they can usually not find an image they previously identified on Commons.
+
+Works fine in Chrome though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391702640,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-l56rigwmq6kptg33obmi,task_description,resolved
+VisualEditor: No vertical scrollbar on insert media (Firefox),"I can no longer reproduce it so seems fixed (in Firefox or on our side).
+
+I'll close it as fixed.",1404208489,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-l56rigwmq6kptg33obmi,task_subcomment,NA
+VisualEditor: No vertical scrollbar on insert media (Firefox),"This may have been fixed.  I can't reproduce this in Firefox 30.  The first search on a random article produced more images than fit on the screen, and I could get to them with the scrollbar.",1404169558,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-l56rigwmq6kptg33obmi,task_subcomment,NA
+VisualEditor: No vertical scrollbar on insert media (Firefox),"(In reply to comment #0)
+> 
+> Reproducible: Didn't try
+> 
+Missed this on filing bug. Definitely reproducible.
+
+On a side note I'm running Firefox 26.0",1391702895,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-l56rigwmq6kptg33obmi,task_subcomment,NA
+VisualEditor: No vertical scrollbar on insert media (Firefox),"Created attachment 14509
+Screencast
+
+**Attached**: {F13230}",1391702752,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-l56rigwmq6kptg33obmi,task_subcomment,NA
+"VisualEditor: The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs","In the VE mode
+
+Steps to reproduce:
+
+1.Open the page with VE
+2.Insert a reference for a text
+3.Add the same reference again somewhere in the page
+4.Add the reflist
+5.Save the page
+
+Observed Result:
+ The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Ehat
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13133}",1391649480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gxelvauhc4ymdd6gw2ss,task_description,resolved
+"VisualEditor: The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs","This is because the Parsoid (re)implementation of Cite doesn't support the customisation of the i18n message currently – merging with that issue.
+
+*** This bug has been marked as a duplicate of bug 43235 ***",1391659693,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gxelvauhc4ymdd6gw2ss,task_subcomment,NA
+"VisualEditor: The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs","Created attachment 14500
+In the read mode
+
+**Attached**: {F13134}",1391649617,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gxelvauhc4ymdd6gw2ss,task_subcomment,NA
+Page creation in alpha with VE wonky if you tap outside of the editable area,"In alpha, navigate to a non-existent page. You should see the text 'This page doesn't exist. Why not be bold and create it?'. Tap on the pencil edit icon. A cursor should show up in the editable area. Tapping outside of the editable area makes the cursor go away. Knowing where to tap in order to get the cursor back is a bit of a mystery. Perhaps we should make the tappable area for this visible to users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391640660,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-yt7hoiqatg2twcdmiujq,task_description,declined
+Page creation in alpha with VE wonky if you tap outside of the editable area,Eh I must've been using an outdated version; I just tested again to take some screenshots and the editable area now appears very obvious. Closing as WFM.,1391728851,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-yt7hoiqatg2twcdmiujq,task_subcomment,NA
+Page creation in alpha with VE wonky if you tap outside of the editable area,"Arthur not sure I follow. Can you provide some screenshots (sadly VE is broken everywhere for me to test)?
+Are you asking for placeholder text?
+Does this differ from VisualEditor desktop experience?",1391716653,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-yt7hoiqatg2twcdmiujq,task_subcomment,NA
+Page creation in alpha with VE wonky if you tap outside of the editable area,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1673",1391640921,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yt7hoiqatg2twcdmiujq,task_subcomment,NA
+VisualEditor: Don't insert a new gallery if the user doesn't enter any contents for it,"Steps to Reproduce:
+1. Open the gallery inserter tool.
+2. Don't add any content.
+3. Discover that no matter what you do from here, it's going to add a pair of gallery tags that is difficult to select (for removal) in VisualEditor and pointless on the page.
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1391634600,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zs5e5bzcmcr4rtwmlnui,task_description,resolved
+VisualEditor: Don't insert a new gallery if the user doesn't enter any contents for it,"This was fixed a few weeks ago (though if you insert "" "" it will insert, but… there's no defeating a user intentionally breaking things).",1394677396,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zs5e5bzcmcr4rtwmlnui,task_subcomment,NA
+VisualEditor:  You should be able to cancel a gallery without adding it,"Steps to Reproduce:
+1. Click on Insert > Gallery
+2. Think ""Oops, I meant to click on Transclusion"".
+3. Try to get out of there without having a gallery added to your page.
+
+Actual Results:  
+Click the < button:  it adds a nearly invisible empty gallery.  Press the ESCape key:  it adds a nearly inisible empty gallery.  Click elsewhere:  it adds a nearly invisible empty gallery.
+
+Expected Results:  
+I expected a trash can, but I'd prefer an X of the universal ""click here to cancel"" variety.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391634360,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-62gwo3nopvq6bsrwmth7,task_description,resolved
+VisualEditor:  You should be able to cancel a gallery without adding it,"(In reply to comment #1)
+> This should probably be merged with Bug 60779.
+
+Done (and fixed, yay).
+
+*** This bug has been marked as a duplicate of bug 60779 ***",1391668703,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-62gwo3nopvq6bsrwmth7,task_subcomment,NA
+VisualEditor:  You should be able to cancel a gallery without adding it,This should probably be merged with Bug 60779.,1391634760,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-62gwo3nopvq6bsrwmth7,task_subcomment,NA
+Enabling visualeditor does not result in usable visualeditor,"Steps to reproduce:
+
+#1 $ vagrant enable-role visualeditor
+Ok. Run 'vagrant provision' to apply your changes.
+
+
+
+#2 $ vagrant list-roles
+Available roles:
+
+  analytics
+  antispam
+  apisandbox
+  betafeatures
+  browsertests
+  chromium
+  cirrussearch
+  cldr
+  codeeditor
+  commonsmetadata
+  echo
+  education
+  eventlogging
+  fundraising
+  gadgets
+  geodata
+  geshi
+  gettingstarted
+  guidedtour
+  hadoop
+  hhvm
+  hive
+  massmessage
+  math
+  mathsearch
+  mleb
+  mobilefrontend
+  multimedia
+  multimediaviewer
+  navigationtiming
+  oauth
+  parserfunctions
+  pdfhandler
+  proofreadpage
+  remote_debug
+  scribunto
+  timedmediahandler
+  uploadwizard
+* visualeditor
+  wikieditor
+  wikimetrics
+  xhprof
+
+Roles marked with '*' are enabled.
+Use ""vagrant enable-role"" & ""vagrant disable-role"" to customize.
+
+
+
+#3 $ vagrant provision
+[default] Running provisioner: puppet...
+Running Puppet with site.pp...
+info: Applying configuration version '1391614793.16f99ad'
+info: mount[files]: allowing mediawiki-vagrant access
+notice: /Stage[main]/Mediawiki::Parsoid/Package[nodejs]/ensure: ensure changed 'purged' to '0.8.2-1chl1~precise1'
+notice: /Stage[main]/Mediawiki::Parsoid/File[/etc/init/parsoid.conf]/ensure: created
+notice: /Stage[main]/Mediawiki::Parsoid/Git::Clone[mediawiki/services/parsoid/deploy]/Exec[git clone mediawiki/services/parsoid/deploy]/returns: executed successfully
+notice: /Stage[main]/Mediawiki::Parsoid/File[localsettings.js]/ensure: defined content as '{md5}11ba3cfc1124f11f4a507a56cc70d34c'
+info: /Stage[main]/Mediawiki::Parsoid/File[localsettings.js]: Scheduling refresh of Service[parsoid]
+notice: /Stage[main]/Mediawiki::Parsoid/Service[parsoid]/ensure: ensure changed 'stopped' to 'running'
+notice: /Stage[main]/Mediawiki::Parsoid/Service[parsoid]: Triggered 'refresh' from 1 events
+notice: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Git::Clone[mediawiki/extensions/VisualEditor]/Exec[git clone mediawiki/extensions/VisualEditor]/returns: executed successfully
+notice: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Mediawiki::Settings[VisualEditor]/File[/vagrant/settings.d/puppet-managed/10-VisualEditor.php]/ensure: created
+notice: Finished catalog run in 587.81 seconds
+
+
+
+#4 Go to http://127.0.0.1:8080/wiki/Main_Page
+
+
+
+#5 Error page is displayed:
+
+MediaWiki 1.23wmf2 required--this is only 1.22alpha
+
+Backtrace:
+
+#0 /vagrant/mediawiki/extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW('1.23wmf2')
+#1 [internal function]: VisualEditorHooks::onSetup()
+#2 /vagrant/mediawiki/includes/Setup.php(569): call_user_func('VisualEditorHoo...')
+#3 /vagrant/mediawiki/includes/WebStart.php(161): require_once('/vagrant/mediaw...')
+#4 /vagrant/mediawiki/index.php(55): require('/vagrant/mediaw...')
+#5 {main}
+
+
+
+#6 Looks like mediawiki-vagrant uses an old version of mediawiki (1.22alpha) and visualeditor needs version 1.23wmf2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391618640,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-usrosfs2iqiakawkjchy,task_description,declined
+Enabling visualeditor does not result in usable visualeditor,I am not sure what I did wrong the last time. I have tried again with a clean VM and visual editor works just fine.,1391693357,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-usrosfs2iqiakawkjchy,task_subcomment,NA
+Enabling visualeditor does not result in usable visualeditor,There's also a 'vagrant git-update' command now that attempts to pull all latest changes to git repos.,1391638634,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-usrosfs2iqiakawkjchy,task_subcomment,NA
+Enabling visualeditor does not result in usable visualeditor,"Thanks, I got the same advice from James_F at #wikimedia-qa. The strange thing is that I have created the vagrant vm today. Shouldn't it have the lates core then?",1391619389,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-usrosfs2iqiakawkjchy,task_subcomment,NA
+Enabling visualeditor does not result in usable visualeditor,MediaWiki-Vagrant git-clones MediaWiki core the first time you provision it and leaves it for you to manage thereafter. You can go to the mediawiki/ subdirectory and run 'git pull' to get the latest.,1391618719,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-usrosfs2iqiakawkjchy,task_subcomment,NA
+VisualEditor: template and link inspectors not working for some users at it.wp,"Might need to split this later, and/or add more details, here's what we know now from it.wp users.
+
+Not logged in user, Firefox 26.0, Windows 7 reports the following.
+*When you try to edit a template, the template inspector will look empty.
+*When you try to add a new template, the inspector won't provide any suggestions for existing ones.
+*When you try to choose an option from the 3-bars menu on the right, none will work (nothing will happen clicking on those), except for the ""Switch to wikitext"" one.
+
+User:Nnvu, Chrome ver. 32.0.1700.102 m, Windows 8.1, Vector reports having the same issues, plus:
+*When you click on a wikilink anywhere in the page, instead than getting the box to edit it, you'll be directed to the linked page (the page will even ask you if you're sure you wanna leave).
+*When you save the page, it will stay in edit mode. If you click Save again, you'll get both the save dialog and the loading bar that keeps going. (The page results correctly saved from the history, nonetheless.) 
+
+Nnvu could check the console once, and said that this message
+*event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
+appeared once the editing page was loaded, while
+*Uncaught TypeError: Object #<Object> has no method 'apiRequest' VM189:567
+is what he got while trying to type inside the template inspector.
+
+VE will work fine for him:
+*if he logs out (but while when he's logged-in, disabling all BetaFeatures, all the gadgets and even blanking .js pages won't still help);
+*if he uses FF, as a logged-in user.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391612040,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cp3g7luvxfst4ptkx7me,task_description,declined
+VisualEditor: template and link inspectors not working for some users at it.wp,This may have been due to some faulty cached code – we saw a similar issue during the aborted deployment of wmf12 to Wikipedias yesterday.,1391794669,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cp3g7luvxfst4ptkx7me,task_subcomment,NA
+VisualEditor: template and link inspectors not working for some users at it.wp,Apparently everything is back to normal now.,1391793651,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cp3g7luvxfst4ptkx7me,task_subcomment,NA
+VisualEditor: template and link inspectors not working for some users at it.wp,"I can't reproduce any of this, and other users can't as well.",1391612515,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cp3g7luvxfst4ptkx7me,task_subcomment,NA
+VisualEditor: Math Inspector icon and Link inspector icon appears together on a Math formula which has link applied on it,"Two inspector icon together over the math function
+
+Steps to produce:
+
+
+1.Open the page with VE
+2.Add a Math function such as \pi
+3.Now add a text before that such as life of pi
+4.Now select the text and the math function together
+5.Apply link on it
+6.Now select the Math function
+
+Observed Result:
+The Math inspector icon and the link inspector icon opens together over the math function.
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Test2chrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56644
+
+**Attached**: {F12944}",1391552880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-25boqjke4cijtwjgyjbt,task_description,invalid
+VisualEditor: Math Inspector icon and Link inspector icon appears together on a Math formula which has link applied on it,This is expected behaviour.,1399047303,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-25boqjke4cijtwjgyjbt,task_subcomment,NA
+VisualEditor: Blanking a page doesn't remove protection templates,"Similar to bug 52036.
+When you blank a page with VE, protection templates like
+https://en.wikipedia.org/wiki/Template:Pp-move-indef
+or
+https://en.wikipedia.org/wiki/Template:Pp-blp
+will stay.
+
+https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=593889831
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52036",1391525700,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-b2icu3jhk57jo4lbtgez,task_description,resolved
+VisualEditor: Blanking a page doesn't remove protection templates,"
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1393271673,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b2icu3jhk57jo4lbtgez,task_subcomment,NA
+VisualEditor: Blanking a page doesn't remove protection templates,"Also categories, interwikis, maybe other stuff that's not editable in the main editor. This sounds like the expected behavior to me.",1391525908,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-b2icu3jhk57jo4lbtgez,task_subcomment,NA
+VisualEditor: Math Formula appears (However does not get placed) inside gallery while opening Latex over gallery,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a gallery
+3.Select the gallery
+4.Open a Math Formula window.
+5.Type something on the editor
+
+Observed Result:
+The math function appears inside gallery .However, if you close the math inspector it will place the math function properly after the gallery not inside it.
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12825}",1391474580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6krx2nyb5rqgwoao3nrw,task_description,resolved
+VisualEditor: Math Formula appears (However does not get placed) inside gallery while opening Latex over gallery,"
+
+*** This bug has been marked as a duplicate of bug 56644 ***",1397757894,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6krx2nyb5rqgwoao3nrw,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**Author:** `jhall`
+
+**Description:**
+Per a request from James Forrester, we should create a new browser test(s) in the VisualEditor repo that will verify the availability of VisualEditor on production wikis in two categories:
+
+1) Test whether VE loads if invoked on each of the currently ~300 wikis that VisualEditor is deployed to.  This is just checking that ?veaction=edit causes a VE surface to load.
+
+2) Test whether VE's edit tab appears on the ~150 wikis to which is is deployed to as default for all users.  This is checking that the tab for VisualEditor loads for logged-out users.
+
+Some caveats regarding this new test:
+
+1)  The test should not perform any writing actions to the wiki (just loading, no saving).
+
+2) We're probably only looking for a quick verification every week or so, rather than 
+​every 12 hours (as with the existing schedule for other VE browser tests).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60842",1391469180,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-323aluzrs2vl2d7v27bc,task_description,resolved
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+Yep, this one is resolved. Job is up-and-running via CloudBees:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-production.wikimedia.org/",1392395125,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Jeff, is this resolved?",1392377851,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Change 112809 merged by jenkins-bot:
+[Browser test] Update list of prod wikis to be verified.
+
+https://gerrit.wikimedia.org/r/112809",1392157240,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Change 112809 had a related patch set uploaded by Jhall:
+[Browser test] Update list of prod wikis to be verified.
+
+https://gerrit.wikimedia.org/r/112809",1392153700,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+CloudBees/Jenkins job for this task is[1]
+
+[1] https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-production.wikimedia.org/",1392089646,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Change 111142 merged by jenkins-bot:
+[Browser test] VisualEditor availability on prod wikis
+
+https://gerrit.wikimedia.org/r/111142",1392061254,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+Re-opening since this is still work-in-progress.",1391536657,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+Setting status back to RESOLVED since I'm not quite done with this just yet...",1391479193,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Change 111142 had a related patch set uploaded by Jhall:
+[Browser test] WIP Test VisualEditor availability on production wikis
+
+https://gerrit.wikimedia.org/r/111142",1391479139,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+From James: ""The list of 300 wikis is[1] – though that contains at the bottom 4 private wikis that shouldn't be tested.""
+
+[1] http://noc.wikimedia.org/conf/highlight.php?file=visualeditor.dblist",1391473888,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Flow: archive search in page header triggers error,"screenshot of error
+
+If I have {{archives}} or {{Talk header}} in the page header area, Flow gives this error (screenshot):
+
+The error message received was: Exception Caught: ID searchbox already defined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60816
+
+**Attached**: {F13408}",1391463960,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-m2mjxjfupqonuuet4g5a,task_description,resolved
+Flow: archive search in page header triggers error,"Change 111224 merged by jenkins-bot:
+Don't error out on duplicate id's
+
+https://gerrit.wikimedia.org/r/111224",1391640389,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,"I think the ""id=searchbox"" is coming from https://www.mediawiki.org/wiki/Extension:InputBox and there are frequently more than one searchbox per page so that does need to be solved.
+
+aha! bug 11777 (Multiple inputboxes make page invalid due to repetitive similar id) I don't know if that bug needs to be poked, with this fresh example? It's been silent since Sept 2012.",1391570033,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,"Change 111224 had a related patch set uploaded by EBernhardson:
+Don't error out on duplicate id's
+
+https://gerrit.wikimedia.org/r/111224",1391537515,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,*** Bug 60816 has been marked as a duplicate of this bug. ***,1391537507,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,"Parsoid is being strict about disallowing the duplicate element IDs in HTML (bug 60816).
+
+But these templates should not be causing invalid HTML output by specifying id=searchbox twice.  Somewhere besides {{archives |search=yes}} there must be another id=searchbox; I tried adding the template wikitext to [[wp:Wikipedia_talk:Flow/Developer_test_page]] but couldn't reproduce it. Assuming that's the problem these templates should use a unique ID, maybe we can alert their authors. Any special styling or behavior they're getting should be due to classes, not an ID.
+
+For grins, you could try to add the problematic templates in VisualEditor.",1391499416,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,"Created attachment 14474
+screenshot 2
+
+After reading the error in the preview (screenshot 1), I removed the {{archives}} box, and hit save. That resulted in this: (screenshot 2)
+
+So I re-edited the header to remove {{Talk header}}. Once I hit save for that, it was still displaying the same error, until I did shift-F5 (hard-refresh).
+
+**Attached**: {F13410}",1391496922,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+VisualEditor: The Strikethrough and Underline gets overlapped for a superscript text,"screenshot
+
+Steps to reproduce:
+
+1.Open a page with Ve
+2.Select a text
+3.Apply Superscript
+4.Apply Strikethrough
+5.Apply Underline
+6.Unselect superscript  
+7.Make it superscript again (Observe that strikethrough is now below the text, this is one issue)
+8.Unselect Underline
+9.Make it underline again
+
+Observed Result
+The Strikethrough and Underline gets overlapped for a superscript text
+
+**This is a FireFox only bug.Works perfectly on Chrome**
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13396}",1391459760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lac4g5g62zrekkfygvxx,task_description,invalid
+VisualEditor: The Strikethrough and Underline gets overlapped for a superscript text,I don't believe this is anything other than Firefox being difficult…,1402294906,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lac4g5g62zrekkfygvxx,task_subcomment,NA
+"VisualEditor:  The special character inserter tool should use the full width of the toolbar, rather than a narrow floating box","The floating palette for the special character tool is annoyingly out of reach if your cursor is at the bottom of your screen.  You have to scroll down (sometimes a lot) to reach the character that you want.  It's also narrow, which limits the number of characters that can be seen at once.
+
+It should be replaced with a fixed, full-width tool that is attached to the main toolbar.  This allows more characters to be displayed at once and is always visible, no matter where you are typing.
+
+This might also be convenient way to address the problems in bug 60657.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391448240,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yurtnajxpg7fxltytwpi,task_description,resolved
+"VisualEditor:  The special character inserter tool should use the full width of the toolbar, rather than a narrow floating box","Fixed by the ""Special Characters"" insertion redesign (can be tested already on http://en.wikipedia.beta.wmflabs.org )",1425547616,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yurtnajxpg7fxltytwpi,task_subcomment,NA
+"VisualEditor:  The special character inserter tool should use the full width of the toolbar, rather than a narrow floating box","> The floating palette for the special character tool is annoyingly out of reach if your cursor is at the bottom of your screen. You have to scroll down (sometimes a lot) to reach the character that you want.
+
+@Whatamidoing-WMF: Is this still valid?
+Being at the very bottom in Firefox 36 with my cursor, trying to insert a special character the view scrolls automatically down. See screenshot:
+
+{F55250}",1425508610,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yurtnajxpg7fxltytwpi,task_subcomment,NA
+"VisualEditor:  The special character inserter tool should use the full width of the toolbar, rather than a narrow floating box",Is this still valid? What about T78038?,1421888018,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yurtnajxpg7fxltytwpi,task_subcomment,NA
+parsoidserver-http-bad-status,"http://en.m.wikipedia.beta.wmflabs.org/w/api.php?format=json&action=visualeditor&paction=parse&page=Selenium_Edit_Test
+
+Any idea why this request ends up with the response:
+{""servedby"":""deployment-apache32"",""error"":{""code"":""parsoidserver-http-bad-status"",""info"":""404""}}
+
+It prevents VisualEditor from loading on mobile...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391408100,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-btmvpbqnfpj57y5y72ua,task_description,declined
+parsoidserver-http-bad-status,"I'm closing this bug as worksforme, as the underlying API outage has since been fixed. Bug 58390 tracks the error code issue.",1391651487,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-btmvpbqnfpj57y5y72ua,task_subcomment,NA
+parsoidserver-http-bad-status,"The API issues were probably the internal LVS failure today, caused by a networking configuration error. See Mark's mail titled ""Outage report: LVS outage February 3, 2013"" on the ops list.",1391463920,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-btmvpbqnfpj57y5y72ua,task_subcomment,NA
+parsoidserver-http-bad-status,"This page loads for me: http://parsoid-lb.eqiad.wikimedia.org/itwiki/Utente%3ABaruneju%2Fsandbox2?oldid=63854985
+
+Sometimes issues in the MW API are misreported as 404s on our end, so maybe this was a transient API failure. The misleading error reporting is tracked in bug 58390.",1391455828,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-btmvpbqnfpj57y5y72ua,task_subcomment,NA
+parsoidserver-http-bad-status,"The problem is not limited to the mobile version, it also happens on the Web using both Firefox and Chrome, both Monobook and Vector.
+Example response: (on it.wiki user sandbox, but it also applies to en.wiki NS:0)
+
+{""servedby"":""mw1121"",""error"":{""code"":""parsoidserver-http-timed-out"",""info"":""http://10.2.2.29/itwiki/Utente%3ABaruneju%2Fsandbox2?oldid=63854985""}}",1391427708,PHID-USER-w7kicrzlpwfrteo6zs5p,PHID-TASK-btmvpbqnfpj57y5y72ua,task_subcomment,NA
+VisualEditor:The Image resize handler along with the blue highlighted box gets displaced while resizing the window,"Screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE which contains an image
+2.Now select the image
+3.Resize the window (Not the image)
+
+Observed Result:
+
+
+The image resize handle gets displaced
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13198}",1391208840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhochcqzfoj4bimpgiqx,task_description,resolved
+VisualEditor:The Image resize handler along with the blue highlighted box gets displaced while resizing the window,"
+
+*** This bug has been marked as a duplicate of bug 55789 ***",1394128066,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zhochcqzfoj4bimpgiqx,task_subcomment,NA
+VisualEditor - Inserting a gallery while having an image selected breaks the visual editor.,"(Tested on Firefox 26, Windows Vista)
+Steps to reproduce
+- Edit the [[Jefferson Davis County Courthouse (Mississippi)]] page using the visual editor.
+- Click the image present in the article.
+- Press ""Insert => Gallery"".
+
+The result of this is that the visual editor will break to a point where one cannot use it without entirely reloading the page. For example:
+- Pressing ""Insert => Gallery"" again yields no reaction.
+- Pressing ""Insert => Special Character"" results in a window that seems to be a hybrid of the gallery and character insertion tool.
+- Clicking any page link in the article will no longer result in the usual ""Edit Link"" popup. Using the link button on the interface will result in a hybrid version of the link window and the gallery window.
+
+Interestingly, there are no errors in Firefox's error console.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows Vista
+**Platform**: PC",1391204400,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-gtujhqzrxk5hd6l7lxu3,task_description,resolved
+VisualEditor - Inserting a gallery while having an image selected breaks the visual editor.,"(For future reference, please report only one issue per bug report. Thank you!)",1391436396,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gtujhqzrxk5hd6l7lxu3,task_subcomment,NA
+VisualEditor - Inserting a gallery while having an image selected breaks the visual editor.,"
+
+*** This bug has been marked as a duplicate of bug 60502 ***",1391204983,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gtujhqzrxk5hd6l7lxu3,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Screenshot
+
+Steps to reproduce:
+
+
+1.Create a page on Betalabs
+2.Add some content and save it
+3.Reopen the page with VE
+
+Observed Result:
+Content of some article is showing up instead of my own edited content
+
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/31st_january
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13186}",1391200560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-timuxvvj3wafz5qt6zh2,task_description,resolved
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,Verified the fix on Betalabs.,1391635700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"The puppet agent didn't seem to be running on the parsoid host in beta labs, and after starting that Parsoid was not restarted to reflect the the changes. Fixed that manually, and verified fixed at http://en.wikipedia.beta.wmflabs.org/wiki/0.6884344289426402?veaction=edit.",1391629537,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Change 111350 merged by Alexandros Kosiaris:
+Bug 60694: Make the config file path configurable
+
+https://gerrit.wikimedia.org/r/111350",1391625176,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Change 111350 had a related patch set uploaded by GWicke:
+Bug 60694: Make the config file path configurable
+
+https://gerrit.wikimedia.org/r/111350",1391553175,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,We need this on beta labs at the earliest opportunity.  I raised the importance.,1391546102,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,https://gerrit.wikimedia.org/r/#/c/110666/ creates a Debian package and makes the config file path configurable in /etc/defaults/mediawiki-parsoid. We might still want to fix this in puppet temporarily until we move to deb-based installs.,1391485605,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Another symptom of this is if you add or edit a post to a Flow board on betalabs (e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA ) and transclude a page with {{:Article name }}, it pulls in the page from enwiki.",1391478948,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"On deployment-parsoid2 in /var/log/parsoid/parsoid.log
+
+{ [Error: Cannot find module '/srv/deployment/parsoid/conf/wmf/localsettings.js'] code: 'MODULE_NOT_FOUND' }
+
+There is no conf directory but there is a file /srv/deployment/parsoid/localsettings.js which is described in puppet:
+
+ manifests/role/parsoid.pp:    file { '/srv/deployment/parsoid/localsettings.js':
+
+I introduced it on Jan 2 with https://gerrit.wikimedia.org/r/#/c/104938/
+
+
+The upstart configuration I wrote ( /etc/init/parsoid.conf ) was pointing to it but now points to ../conf/wmf/localsettings.js.
+
+So I guess the easiest path is to use an env variable such as PARSOID_CONF, set it in /etc/default/parsoid and make it vary in the puppet configuration.",1391467271,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"A bit more investigation shows that VE is sending the right oldid.
+
+I think this is caused by Parsoid not finding its config file in the deploy repo. In the production upstart config we are now passing the explicit path to a config file to parsoid, which is checked into conf/wmf/localsettings.js in the deploy repo. Beta labs might still rely on localsettings.js being in src/api, which will no longer work.
+
+I think we'll need to make the config path configurable in the upstart file, and set a different path (ideally conf/wmf-beta or the like) for betalabs.",1391464994,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Note that this could also be VE sending the wrong oldid, as that will always take precedence over the page name.",1391464443,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"This is unlikely to be related to bug 60372, as a) the oldid is sent, and b) it only happened sometimes under high request loads.
+
+This does not happen in production (running Parsoid master right now). I'm suspecting a configuration issue in betalabs.",1391456757,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,It seems to be quite easy to consistently reproduce. Just click 'random article' and then load the VisualEditor. I get the contents of a different article 100% of the time. The really weird thing is that the articles that are being loaded don't seem to even exist on Beta Labs.,1391455995,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,Does beta.wmflabs.org have latest parsoid master? Related is bug 60372 which was fixed in https://gerrit.wikimedia.org/r/#/c/110233/,1391455771,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"I noticed this today at
+http://en.m.wikipedia.beta.wmflabs.org/wiki/0.07511468210381089
+
+Whenever I load VisualEditor, it loads the allergy article instead.",1391455640,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"**jhall** wrote:
+
+I've also been seeing this behavior in beta labs today, although it's been difficult to consistently reproduce.  I've seen it much more frequently with the automated browser tests than I have with manual testing.",1391210840,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Now, Uncaught TypeError: Cannot read property 'status' of null is appearing while trying to open VE in betalabs",1391203540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+VisualEditor: Provide the character inserter everywhere that you can input text,"Intention:
+Add special characters
+
+Steps to Reproduce:
+If any of the following that happen to rely on special characters:
+
+* A template
+* A parameter name in said template
+* Data for parameter (e.g., the name of a person or place)
+* A link to another page
+* A category
+* A media item (e.g., image) that you can't find otherwise
+* An image or a caption in a image gallery
+* An edit summary
+
+then they cannot be successfully used in VisualEditor.  Probably there are uses for it in the Mathematics Formulae tool as well.  
+
+Basically, if you have a cursor for typing anything, anywhere in the entire VisualEditor interface, then you need access to the special character inserter.
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391125500,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-vod4bp3xvmjarqf6dtmz,task_description,declined
+VisualEditor: Provide the character inserter everywhere that you can input text,"Is that title better, @Jdforrester-WMF?",1425419652,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vod4bp3xvmjarqf6dtmz,task_subcomment,NA
+VisualEditor: Provide the character inserter everywhere that you can input text,"I could write it up as a whole series of bugs, if you'd like:  Make it
+possible to access VisualEditor's special character tool when adding a
+template (ie., typing the name of the template).  Make it possible to
+access VisualEditor's special character tool when filling in parameter data
+for templates.  Make it possible to access VisualEditor's special character
+tool when editing citations.  Make it possible to access VisualEditor's
+special character tool when searching for media.  Make it possible to
+access VisualEditor's special character tool when typing a file name or
+caption in a gallery.  Make it possible to access VisualEditor's special
+character tool when writing an edit summary.  Make it possible to access
+VisualEditor's special character tool when adding a category (including a
+redlink category).",1425416797,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-vod4bp3xvmjarqf6dtmz,task_subcomment,NA
+VisualEditor: Provide the character inserter everywhere that you can input text,This isn't a bug. It isn't a task. It isn't asking for anything. It doesn't have an actionable element at all.,1425416329,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vod4bp3xvmjarqf6dtmz,task_subcomment,NA
+"VisualEditor: When followed by a template, the template edit icon is appearing over an image","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Now add an image to the page
+3.Now add a template infobox-country or any other infobox template like infobox-company
+4.Save the page
+5.Open the page again.
+6.Now Select the template 
+
+Observed Result:
+
+The template edit icon is appearing over the image now
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Image_after_template
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13094}",1391122080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bxocvjff7v4vgwjuctgr,task_description,resolved
+"VisualEditor: When followed by a template, the template edit icon is appearing over an image","Think I'm going to merge this with bug 51548.
+
+*** This bug has been marked as a duplicate of bug 51548 ***",1393455560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bxocvjff7v4vgwjuctgr,task_subcomment,NA
+VisualEditor:General Settings and Advanced Settings button/text field labels are missing on Media Settings widget for test2 and mw.org,"Screenshot
+
+Steps to reproduce:
+
+1.Insert and image 
+2.Go to Media Settings
+
+Observed Result:
+
+General Settings and Advanced Settings button tags are missing on Media Settings widget
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13065}",1391112720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gwypfbeszglyxfdqtuls,task_description,declined
+VisualEditor:General Settings and Advanced Settings button/text field labels are missing on Media Settings widget for test2 and mw.org,All the labels and messages are appearing now in test2 and mediawiki,1391203627,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gwypfbeszglyxfdqtuls,task_subcomment,NA
+VisualEditor:General Settings and Advanced Settings button/text field labels are missing on Media Settings widget for test2 and mw.org,"Created attachment 14420
+Screenshot
+
+**Attached**: {F13066}",1391112912,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gwypfbeszglyxfdqtuls,task_subcomment,NA
+VisualEditor:General Settings and Advanced Settings button/text field labels are missing on Media Settings widget for test2 and mw.org,"Infact all the textbox name and heading of the advanced dialog Settings page is missing
+See the second screenshot",1391112893,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gwypfbeszglyxfdqtuls,task_subcomment,NA
+"VisualEditor: Clicking on Increase/Decrease Indentation button multiple times shows ""Confirm Navigation?"" dialog box on mediawiki.org","Screenshot attached
+
+Steps to reproduce;
+
+
+1.Open a page with VE
+2.Add a bullet list or a numbered list
+3.Keep on pressing the Add or decrease indentation  button for a bullet point 
+
+
+Observed Result:
+""Confirm Navigation?"" dialog box are showing up .
+
+See the screenshot attached.
+
+Test Environment: mw.org
+Browser: Chrome Version 26.0.1410.65 & FF25
+OS: MAC OS X 10. 8. 5 
+Page:https://www.mediawiki.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13048}",1391111220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r236onqi4kxnnfykppxk,task_description,resolved
+"VisualEditor: Clicking on Increase/Decrease Indentation button multiple times shows ""Confirm Navigation?"" dialog box on mediawiki.org",This now seems to be fixed!,1431640555,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-r236onqi4kxnnfykppxk,task_subcomment,NA
+"VisualEditor: ""Review your changes"" and ""Save Page"" button layout missing in test2","Screenshot
+
+Steps to reproduce:
+
+
+
+1.Open any page with VE in test 2
+2.Add some content and Save page
+
+Observed Result:
+""Review your changes"" and ""Save Page"" button layout missing in test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13039}",1391109780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lb4esyvemyxlbz7scvjj,task_description,declined
+"VisualEditor: ""Review your changes"" and ""Save Page"" button layout missing in test2",Not happening anymore,1391120065,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lb4esyvemyxlbz7scvjj,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"It would make sense, since all repositories (except VisualEditor) have Selenium tests already there:
+
+https://github.com/wikimedia/mediawiki-selenium#links
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391077980,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-xdef52u2xoutalmxvqxq,task_description,resolved
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Change 111998 merged by Cmcmahon:
+Moved Selenium tests from root folder of qa/browsertests repository to tests/browser folder
+
+https://gerrit.wikimedia.org/r/111998",1391789269,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Change 111997 merged by jenkins-bot:
+Moved tests from root folder to tests/browser folder
+
+https://gerrit.wikimedia.org/r/111997",1391770846,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Change 111998 had a related patch set uploaded by Zfilipin:
+Moved Selenium tests from root folder of qa/browsertests repository to tests/browser folder
+
+https://gerrit.wikimedia.org/r/111998",1391770769,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Change 111997 had a related patch set uploaded by Zfilipin:
+Moved tests from root folder to tests/browser folder
+
+https://gerrit.wikimedia.org/r/111997",1391770062,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Chris, Jeff, what do you think?
+
+It would simplify our documentation and also Jenkins job template[1].
+
+We could replace
+
+if [ -d ""${FOLDER}"" ]; then cd ${FOLDER}; fi
+
+with just
+
+cd ${FOLDER}
+
+1: https://github.com/wikimedia/mediawiki-selenium/blob/master/docs/template.md#jelly-based-transformation",1391078169,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,"Screenshot
+
+Cannot load any page on Betalabs.Getting the following error:
+
+6ca85571] /wiki/29th_January Exception from line 84 of /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php: Wikibase: Incomplete configuration: $wgWBRepoSettings[""entityNamespaces""] has to be set to an array mapping content model IDs to namespace IDs. See ExampleSettings.php for details and examples.
+
+Backtrace:
+
+#0 [internal function]: Wikibase\RepoHooks::onSetupAfterCache()
+#1 /data/project/apache/common-local/php-master/includes/Hooks.php(206): call_user_func_array(string, array)
+#2 /data/project/apache/common-local/php-master/includes/GlobalFunctions.php(3976): Hooks::run(string, array, NULL)
+#3 /data/project/apache/common-local/php-master/includes/Setup.php(520): wfRunHooks(string)
+#4 /data/project/apache/common-local/php-master/includes/WebStart.php(153): require_once(string)
+#5 /data/project/apache/common-local/php-master/index.php(46): require(string)
+#6 /data/project/apache/common-local/w/index.php(3): require(string)
+#7 {main}
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+
+**Attached**: {F12982}",1391045040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_description,resolved
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,*** Bug 60612 has been marked as a duplicate of this bug. ***,1391090756,PHID-USER-lzhljhpbm3qfphvqyill,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_subcomment,NA
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,Thanks.Verified the fix.,1391054896,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_subcomment,NA
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,"Fixed, will propagate to labs within the next 30 minutes, probably a bit earlier",1391045340,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_subcomment,NA
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,Being worked on.,1391045213,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_subcomment,NA
+VisualEditor isn't able to handle header and row templates,"The VisualEditor template editor works on infobox templates like https://en.wikipedia.org/wiki/Template:Infobox_NRHP . On templates like https://en.wikipedia.org/wiki/Template:NRHP_header and https://en.wikipedia.org/wiki/Template:NRHP_row it doesn't work (yet) probably because these templates generate tables. We have a lot of these templates in a lot of different languages, see for example https://en.wikipedia.org/wiki/Category:Monument_list_templates . It would be nice if VE could be used to edit these templates.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391033760,PHID-USER-cw4amt4ewxdze5qcjdca,PHID-TASK-covwdyeu7km7zagn5wbs,task_description,resolved
+VisualEditor isn't able to handle header and row templates,"As @Etonkovidova said, it is possible (though not user-friendly) to do this. I'm tentatively closing; if anyone has specific ideas for how to make this more user friendly, feel free to open another task.",1437692916,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-covwdyeu7km7zagn5wbs,task_subcomment,NA
+VisualEditor isn't able to handle header and row templates,"The template content(and fields) can be edited via Transclusion or in Edit Source. 
+Checked in production  {{NRHP row}} , {NRHP header}}- in VE in Transclusion box the templates can be edited.
+
+",1421455993,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-covwdyeu7km7zagn5wbs,task_subcomment,NA
+"VisualEditor: After adding an empty gallery in a list, the list continues adding bullets/numbered points even after hitting return twice","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391024460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ey2t66avbr7lh2xruo6p,task_description,invalid
+"VisualEditor: After adding an empty gallery in a list, the list continues adding bullets/numbered points even after hitting return twice",I can't reproduce this now – presumably now fixed by not allowing empty galleries.,1394488268,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ey2t66avbr7lh2xruo6p,task_subcomment,NA
+"VisualEditor: After adding an empty gallery in a list, the list continues adding bullets/numbered points even after hitting return twice","Steps to reproduce:
+
+1.Open a page with VE
+2.Add a numbered list/bullet list
+3.Add an empty gallery as an item in the list.
+4.Now place the cursor in the last bullet/numbered point
+5.Press Enter twice
+
+Observed Result:
+
+It keeps on adding new bullets or numbered points in the list even after hitting return twice.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=29th_January&veaction=edit",1391029124,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ey2t66avbr7lh2xruo6p,task_subcomment,NA
+VisualEditor:  Special character inserter behaves oddly if you don't click somewhere in the page first,"Intention:
+Add a special character.
+
+Steps to Reproduce:
+1. Open a page in VisualEditor.  Don't click anywhere in it.
+
+2. Go to Insert > Special characters to open the Special charater inserter tool.
+
+3. Click on a character (or several).
+
+Actual Results:  
+Nothing is added, but the ""Save"" button lights up.  You can't use it, though.
+
+If you click elsewhere, the tool disappears, but nothing else happens.  ""Save"" is still green, but you still can't use it.
+
+If you go back into the special character tool and add a new special character, then all the original ones appear at the start of the page, but the tool's dialog box is still open.  
+
+If you then cancel (to get rid of the box), Bad Things happen, including snowmen and partial duplication of the page.  You still can't save.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390866360,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-riotbykdtow5sbh7ljef,task_description,declined
+VisualEditor:  Special character inserter behaves oddly if you don't click somewhere in the page first,"This has now been ""fixed"" by the simple effort of making this route impossible; tools are now disabled if there isn't an active surface insertion point.",1400546311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-riotbykdtow5sbh7ljef,task_subcomment,NA
+VisualEditor: 'mozMatchesSelector' called on an object that does not implement interface when launching VE,"When launching VE in Firefox, it throws the following error:
+'mozMatchesSelector' called on an object that does not implement interface
+
+Happens on beta labs and local master.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1390864440,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-mcp3tejcciwpxx3d2tbm,task_description,declined
+VisualEditor: 'mozMatchesSelector' called on an object that does not implement interface when launching VE,Can't reproduce this now (Firefox 33.1 with Firebug)…,1415884389,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mcp3tejcciwpxx3d2tbm,task_subcomment,NA
+VisualEditor: 'mozMatchesSelector' called on an object that does not implement interface when launching VE,"Actually, it's not a JS error, but a breakpoint being triggered in Firebug.",1391542151,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-mcp3tejcciwpxx3d2tbm,task_subcomment,NA
+VisualEditor: 'mozMatchesSelector' called on an object that does not implement interface when launching VE,"Happens in Firefox 26 and latest nightly build.
+
+Although it's not that helpful for debugging, the error is thrown from line 5303 of jquery.js:
+var ret = matches.call( elem, expr );",1390945304,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-mcp3tejcciwpxx3d2tbm,task_subcomment,NA
+VisualEditor: [Regression] Save dialog no longer expands when viewing diff,"When you click ""Review your changes"" in the save dialog, it used to grow to accommodate the fact that diffs tend to be bigger than the regular save dialog contents. However, it stopped doing this a while ago.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390857780,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-f2ifd6fdj6pchv36q7fq,task_description,resolved
+VisualEditor: [Regression] Save dialog no longer expands when viewing diff,"Change 116897 merged by jenkins-bot:
+Update VE core submodule to master (ab70193)
+
+https://gerrit.wikimedia.org/r/116897",1394066191,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f2ifd6fdj6pchv36q7fq,task_subcomment,NA
+VisualEditor: [Regression] Save dialog no longer expands when viewing diff,"Change 116897 had a related patch set uploaded by Catrope:
+Update VE core submodule to 4513d9c21a9502b2fc2d9b6739c2dac0af21e03e
+
+https://gerrit.wikimedia.org/r/116897",1394059358,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f2ifd6fdj6pchv36q7fq,task_subcomment,NA
+Enable on redirects,"Redirects are normal wiki pages of main ns. So why not should allow to edit them with VisualEditor? For example in cases, I remove redirect and want edit a page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390664940,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-f3t5ledkhevthmf76bbm,task_description,resolved
+Enable on redirects,"(In reply to Juan de Vojníkov from comment #2)
+> Why you mareked it as duplicate. 
+
+Because it is the same request as bug 50878.
+
+> I can see the other bug takes care of en.w.
+
+No. https://gerrit.wikimedia.org/r/#/c/95213/ is generic. It's code in VisualEditor itself, not in server configuration.",1392637581,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-f3t5ledkhevthmf76bbm,task_subcomment,NA
+Enable on redirects,"(In reply to James Forrester from comment #1)
+> 
+%%%> *** This bug has been marked as a duplicate of bug 50878 ***%%%
+
+Why you mareked it as duplicate. I can see the other bug takes care of en.w. Here I am talking about cs.w and potetionally every other.",1392634313,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-f3t5ledkhevthmf76bbm,task_subcomment,NA
+Enable on redirects,"
+
+*** This bug has been marked as a duplicate of bug 50878 ***",1390695336,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f3t5ledkhevthmf76bbm,task_subcomment,NA
+Page rendered completely blank,"When I loaded [[mw:Mobile wikitext editing]] recently as a logged-in user, the page looked completely blank. This may be an issue in VisualEditor, I'm not sure. Purging the page fixed the issue.
+
+My suspicion is that Parsoid somehow returned blank content. Unfortunately I'm unable to reproduce this issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Mobile_wikitext_editing",1390590840,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-5qndpoaoah52uflwalmh,task_description,declined
+Page rendered completely blank,"Without a way to reproduce this or some kind of error log we can't really do anything here. There have also not been any other reports about blank pages, so closing this bug as worksforme.",1391717249,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-5qndpoaoah52uflwalmh,task_subcomment,NA
+Page rendered completely blank,"This is the Parsoid output: http://parsoid-lb.eqiad.wikimedia.org/mediawikiwiki/Mobile_wikitext_editing?oldid=889921
+
+Client-side VE issues typically result in JS errors in the browser JS console. Could you check whether that is the case?",1390785697,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-5qndpoaoah52uflwalmh,task_subcomment,NA
+Clicking the Media Settings Widget does not open the dialog,"I'm on 1.23wmf10 and the master build of both VisualEditor and Parsoid. I can insert and resize an image just fine, but clicking on the icon in the upper right performs no action. I discovered the following message:
+
+Uncaught TypeError: undefined is not a function 
+
+load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%2Cmwcore%2Cmwgalle…:344
+VeUiMediaSizeWidget load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%2Cmwcore%2Cmwgalle…:344
+ve.ui.MWMediaEditDialog.initialize load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%2Cmwcore%2Cmwgalle…:528
+oo.EventEmitter.emit load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.pl…:112
+(anonymous function) load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.pl…:125
+pollExternalStylesheets load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.pl…:124
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390582500,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-4yqfpq6tylsvui2kalk4,task_description,invalid
+Clicking the Media Settings Widget does not open the dialog,Updating to a more recent build of VisualEditor resolves this issue.,1401744326,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-4yqfpq6tylsvui2kalk4,task_subcomment,NA
+"VisualEditor:  Make {{reflist}} update with new refs as you add them, just like <references /> does","Intention:
+<References /> automatically updates as you edit a page.  The {{Reflist}} template does not.  Can the handling of the template be improved so that refs inside the {{ref list}} template also update automatically?
+
+
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1390437480,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-eee27mysfumux3ogerbm,task_description,duplicate
+"VisualEditor:  Make {{reflist}} update with new refs as you add them, just like <references /> does","This is a confusing response. {{reflist}} is used all over the place, often by preference.
+
+A blank ""wontfix"" doesn't address the reasons for this statement, and they do in fact need addressing. Are you planning to systematically remove {{reflist}}, for example? Clarification is needed on this point.",1390853772,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-eee27mysfumux3ogerbm,task_subcomment,NA
+"VisualEditor:  Make {{reflist}} update with new refs as you add them, just like <references /> does","(In reply to comment #0)
+> Intention:
+> <References /> automatically updates as you edit a page.  The {{Reflist}}
+> template does not.  Can the handling of the template be improved so that refs
+> inside the {{ref list}} template also update automatically?
+
+Unfortunately, no, we can't.
+
+This is one of the (many) reasons why we discourage people from using {{Reflist}}.",1390607802,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eee27mysfumux3ogerbm,task_subcomment,NA
+VisualEditor:The image resize handle is not appearing at the corner of the selection box around the image when it has a caption,"screenshot
+
+Steps to reproduce:
+
+1.Open a page which contains image with VE
+2.Add a large caption to the image by going to Media Settings
+3.Click on ""Apply Changes""
+4.Attempt to resize the image
+
+Observed Result:
+The image resize handle is not at the most bottom-left corner of the blue highlighted selection box around the image but at the corner of the image.
+It looks a bit odd to have it somewhere in the middle of the border when it has a large caption.
+Probably ,having it at the corner most corner will look better.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F13020}",1390423260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6yggapp3gflkqr5tutc5,task_description,declined
+VisualEditor:The image resize handle is not appearing at the corner of the selection box around the image when it has a caption,"This is correct as you are resizing the image, not the caption.",1390585818,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6yggapp3gflkqr5tutc5,task_subcomment,NA
+VisualEditor:The selected parameter gets switched upon mouse-up beyond the right panel,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a template like Cite web
+3.Select the parameter URL
+4.Add a value in this field like http://yahoo.com
+5.Now select this text from right to left
+6.Mouse up just a little beyond the borderline between left panel and right panel
+
+Observed Result:
+
+The parameter on the right panel gets switched to the next parameter which is ""Source Title""
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+Page:https://test2.wikipedia.org/w/index.php?title=22nd_january&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13019}",1390419240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mhhjk5pjhzhxuptufuod,task_description,declined
+VisualEditor:The selected parameter gets switched upon mouse-up beyond the right panel,I don't see any oddities now… marking as such.,1415054014,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mhhjk5pjhzhxuptufuod,task_subcomment,NA
+VisualEditor:The selected parameter gets switched upon mouse-up beyond the right panel,"I'm not quite sure what was happening here, but is this bug still valid?",1414884201,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mhhjk5pjhzhxuptufuod,task_subcomment,NA
+VE does not appear at all on beta labs,"Seen as of Jan 22
+
+As a logged in user, edit any page on http://en.wikipedia.beta.wmflabs.org/ with VisualEditor. 
+
+User sees the ve-init-mw-viewPageTarget-loading bars moving, but VE never arrives. 
+
+Checked in Chrome and Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1390405560,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-iu3irtpbwblnycah2bvt,task_description,resolved
+VE does not appear at all on beta labs,"VisualEditor is working for me on beta.  I noticed some files belonged to root user, I have changed back to be owned by mwdeploy:mwdeploy.  That might have caused some update issue since the update job runs as mwdeploy.",1390506391,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+VE does not appear at all on beta labs,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Is the version of VE referenced by the mediawiki/extensions meta repo?
+> 
+> http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version says it's got VE
+> 37e90c1 from yesterday – https://gerrit.wikimedia.org/r/#/c/108713/ – which
+> isn't the latest version.
+
+That is bug 49846 (VE not being automatically updated on beta) which is now fixed.",1390502272,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+VE does not appear at all on beta labs,"Antoine, is this tracked already?",1390469804,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+VE does not appear at all on beta labs,"(In reply to comment #1)
+> Is the version of VE referenced by the mediawiki/extensions meta repo?
+
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version says it's got VE 37e90c1 from yesterday – https://gerrit.wikimedia.org/r/#/c/108713/ – which isn't the latest version.",1390416458,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+VE does not appear at all on beta labs,Is the version of VE referenced by the mediawiki/extensions meta repo?,1390416280,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+Visualeditor:A Return character gets placed between two galleries placed one after another,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which has a gallery in it
+2.Add another gallery code just after the already existing one
+3.Save the page
+4.Reopen the page with VE
+
+Observed Result
+A return arrow appears between the two galleries
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page: https://test2.wikipedia.org/wiki/Thedomtest?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12925}",1390348620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vtsg5xob5vkahyr6gi7o,task_description,resolved
+Visualeditor:A Return character gets placed between two galleries placed one after another,"This also looks to have been fixed, probably by Parsoid.",1406754223,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vtsg5xob5vkahyr6gi7o,task_subcomment,NA
+VisualEditor:The gallery inspector adds a newline while opening up a gallery,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which has for example the following gallery code:
+<gallery>
+File:Joo Chiat Place.jpg|Item 1
+File:Joo Chiat Place.jpg|a link to [[Help:Contents]]
+File:Joo Chiat Place.jpg
+File:Joo Chiat Place.jpg|alt=An example image. It has flowers
+File:Joo Chiat Place.jpg| ''italic caption''
+</gallery>
+
+2.Click on the gallery and open it with the new gallery inspector
+
+Observed Result:
+There is an extra newline inserted at the beginning of gallery code inside the inspector.
+
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Thedomtest?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12923}",1390346700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-l4vjyqc363bdzzivdhbk,task_description,resolved
+VisualEditor:The gallery inspector adds a newline while opening up a gallery,"No longer occurs, probably fixed a long time ago.
+
+{F128164}",1429599901,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-l4vjyqc363bdzzivdhbk,task_subcomment,NA
+VisualEditor: Reference numbers do not display properly on fr.wp,"NemesisIII reports that when VEditing a page, existing reference numbers do not appear as ""superscripted"" as they should.
+See section ""projet"" of https://commons.wikimedia.org/wiki/File:Bug_%C3%A9diteur_visuel_affichage_appels_de_r%C3%A9f%C3%A9rence.png (from https://fr.wikipedia.org/wiki/Avenue_Foch?veaction=edit ).
+Number 3 and 4 are existing references, and they are very low. Number 5 instead is a newly added reference, which displays ok (note that this reference does not really exist in the article, it was added just to take the screenshot).
+
+According to my tests, only fr.wp seems affected. I was able to reproduce this with
+*Firefox (both Vector and Monobook)
+*Chrome (Monobook)
+*Opera (while logged out).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390305780,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xcqwgfkr43r7ohstvh74,task_description,resolved
+VisualEditor: Reference numbers do not display properly on fr.wp,"Fixed ages ago, I think.",1414624599,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xcqwgfkr43r7ohstvh74,task_subcomment,NA
+VisualEditor: Reference numbers do not display properly on fr.wp,"Updating the link, https://fr.wikipedia.org/wiki/Avenue_Foch_(Paris)?veaction=edit .",1392295643,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xcqwgfkr43r7ohstvh74,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**Author:** `llamaal_wikis`
+
+**Description:**
+Intention:
+After the conclusion of https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual on the Spanish Wikipedia, some changes to the status of VE in that project have to be implemented:
+
+1. VE should now be opt-in
+2. The ""edit"" tab should return to wikitext
+3. VE should be presented as part of Beta Features
+4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+
+Regards,
+
+LlamaAl
+
+
+
+
+Reproducible: Didn't try
+
+After the conclusion of https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual on the Spanish Wikipedia, some changes to the status of VE in that project have to be implemented:
+
+1. VE should now be opt-in
+2. The ""edit"" tab should return to wikitext
+3. VE should be presented as part of Beta Features
+4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+
+Regards,
+
+LlamaAl
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1390009560,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oap3pcoqr67a3nxmzly7,task_description,resolved
+Changes to VisualEditor on eswiki as result of vote,"
+
+*** This bug has been marked as a duplicate of bug 60188 ***",1390011045,PHID-USER-3qsavo6roa5h32xcsgng,PHID-TASK-oap3pcoqr67a3nxmzly7,task_subcomment,NA
+VisualEditor:Only a single node is appearing to drag an image to resize,"Single node
+
+Steps to reproduce:
+
+
+1.Open a page with VE which has image inside it
+2.Select the image
+
+Observed Result:
+There is just one node appearing on the bottom-left corner of the image to resize it,previously there used to four nodes to drag.
+
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/, wmf11
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13171}",1389907260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kpwswnv3ba5na6dn3pbp,task_description,invalid
+VisualEditor:Only a single node is appearing to drag an image to resize,Not a bug; intentional behaviour change. :-),1389907705,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpwswnv3ba5na6dn3pbp,task_subcomment,NA
+"VisualEditor:""Cite error: <ref> tags exist, but no <references/> tag was found ""  after adding a reference in the caption of an image although there was <references/> tag","In edit source mode
+
+Steps to reproduce:
+
+1.Open a page with VE which has some references and <references/> tag added 
+2.Add an image in the page
+3.Go to media settings and add a caption with reference inside it
+4.Save the page
+
+Observed Result:
+An error appears in the read mode :""Cite error: <ref> tags exist, but no <references/> tag was found ""
+
+Also in the resulting wikitext, the reference inside image did not get added in the <references/> section
+
+
+
+Although if you go to Edit mode the reference inside the image is correctly showing up in the <references/> tag.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://test2.wikipedia.org/wiki/Wmf11
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13149}",1389902400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v3oimjdnujt4xxuujgme,task_description,invalid
+"VisualEditor:""Cite error: <ref> tags exist, but no <references/> tag was found ""  after adding a reference in the caption of an image although there was <references/> tag","This is because the <references /> was before the <ref>.
+
+Yay MediaWiki. :-(
+
+Fixed: 
+
+https://test2.wikipedia.org/w/index.php?title=Wmf11&oldid=71790
+
+vs.
+
+https://test2.wikipedia.org/w/index.php?title=Wmf11&oldid=71598",1390022111,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3oimjdnujt4xxuujgme,task_subcomment,NA
+"VisualEditor:""Cite error: <ref> tags exist, but no <references/> tag was found ""  after adding a reference in the caption of an image although there was <references/> tag","Created attachment 14327
+In Edit mode
+
+**Attached**: {F13150}",1389902484,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v3oimjdnujt4xxuujgme,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","The i18n messages for the Toolbar insert button and the subsequent special character tree does not seem to sync with translated messages at Translatewiki. 
+For some reason French and German gives correct messages but others give English default messages.
+
+The strings are:
+visualeditor-toolbar-insert
+visualeditor-specialcharacter-button-tooltip
+visualeditor-specialcharacterinspector-title
+visualeditor-specialcharinspector-characterlist-insert
+
+Possibly related to them being marked as non-translatable on translatewiki.
+
+See annotated screenshot at:
+https://commons.wikimedia.org/wiki/File:VisualEditorBugInsert.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389894780,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-3tsgq57muuprxfvxj5ar,task_description,resolved
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","(In reply to Lokal_Profil from comment #7)
+> Whatever was done seems to have worked. Thanks (closing)
+
+Yes, that was https://gerrit.wikimedia.org/r/#/c/109420/ (+ https://gerrit.wikimedia.org/r/#/c/112650/ ).",1392983896,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable",Whatever was done seems to have worked. Thanks (closing),1392138855,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","(In reply to comment #5)
+> These translations are still not being pushed through, is there anything else
+> which might have caused this?
+> 
+> Could translations which were done whilst the messages were ""untranslatable""
+> somehow have not triggered an updated translation?
+
+Opening again as this has not gotten fixed. See e.g. https://sv.wikipedia.org/wiki/Foo?veaction=edit&uselang=sv where ""Insert"" is still displayed as well as the other messages. To the list above can be added
+
+Visualeditor-mwgalleryinspector-title",1391698958,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","These translations are still not being pushed through, is there anything else which might have caused this?
+
+Could translations which were done whilst the messages were ""untranslatable"" somehow have not triggered an updated translation?",1391432413,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","Change 109420 had a related patch set uploaded by Jforrester:
+Re-enable support for two VisualEditor related groups
+
+https://gerrit.wikimedia.org/r/109420",1390605367,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","Change 107541 abandoned by Jforrester:
+Add support for moved VisualEditor core
+
+Reason:
+Done instead in Ia580491d9b329200d3def5425d887f0062e0a1a2.
+
+https://gerrit.wikimedia.org/r/107541",1390605331,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","Change 107541 had a related patch set uploaded by Jforrester:
+Add support for moved VisualEditor core
+
+https://gerrit.wikimedia.org/r/107541",1389934286,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","Yeah, this is because TranslateWiki.Net removed tracking of VisualEditor's core messages (rather than the MW-specific ones) when the repo was split, and haven't yet added them back. Sorry about this!",1389934240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"**Author:** `swalling`
+
+**Description:**
+Screenshot on enwiki
+
+Detection of the 'edit' tab and section edit links is broken currently, probably due to https://gerrit.wikimedia.org/r/#/c/97701/ change in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F13059}",1389826140,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kts426m6tijfml3ngiqw,task_description,resolved
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107735 merged by jenkins-bot:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107735",1389831185,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107734 merged by jenkins-bot:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107734",1389831178,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107735 had a related patch set uploaded by Mattflaschen:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107735",1389827628,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107734 had a related patch set uploaded by Mattflaschen:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107734",1389827613,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107631 merged by jenkins-bot:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107631",1389826467,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107631 had a related patch set uploaded by Mattflaschen:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107631",1389826330,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Specifically, VE's isAvailable used to imply that the preference was also enabled, meaning the VE edit tab would be there.
+
+Now, isAvailable doesn't say anything about the preference. So if you have VE disabled, the tab will be missing, so it can't attach to it, and shows in the center like that.",1389826281,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Keep Going overlay overlaps with visualeditor overlay,"https://en.m.wikipedia.org/wiki/Lost_Coon_Lake?title=Lost_Coon_Lake&campaign=mobile-mainpage-keepgoing-links&mobileaction=alpha#editor/0
+
+Expected:
+The Keep Going overlay should appear below the VE overlay.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389820920,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-zjzk5xt7l23o75cnuaf2,task_description,declined
+Keep Going overlay overlaps with visualeditor overlay,Seems to have fixed itself.,1390607906,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-zjzk5xt7l23o75cnuaf2,task_subcomment,NA
+Keep Going overlay overlaps with visualeditor overlay,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1627",1389821133,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zjzk5xt7l23o75cnuaf2,task_subcomment,NA
+Incorrect wiki code when applying category,"Hi
+If I apply a category to a page using VE, it generates an incorrect code (for example %2520 instead of _ I think) and it has only one square character.
+
+Latest git of VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: http://wiki.mc128k.info/index.php/Test",1389650340,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_description,declined
+Incorrect wiki code when applying category,"Upgraded to latest git for MW, VE and Parsoid, now it works! Thanks!",1394972583,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_subcomment,NA
+Incorrect wiki code when applying category,"I'm sorry for the delay. Tried upgrading to latest and I get the same error. See the link.
+http://wiki.mc128k.info/index.php/Test",1390769648,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_subcomment,NA
+Incorrect wiki code when applying category,"Marking as ""WORKSFORME""; feel free to re-open if you have more details.",1390608352,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_subcomment,NA
+Incorrect wiki code when applying category,"Can you give some more details? It appears to be working locally, and on WMF production (see e.g. https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=885698&oldid=885622 for it working).
+
+A screenshot or copy-paste of your resultant wikitext (and ideally a dump of the HTML that got sent to Parsoid) would be hugely helpful.",1389989903,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"**Author:** `kwang`
+
+**Description:**
+If you are in the keep going campaign and you are in alpha, when you click edit you don't get VE you get the wikitext editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389403020,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rdqowzyta6j737yhntsg,task_description,resolved
+First edit in VE doesn't launch KeepGoing campaign,"Change 108990 merged by jenkins-bot:
+Make KeepGoing/toast confirmation run when editing using VE
+
+https://gerrit.wikimedia.org/r/108990",1391456992,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"Change 109436 merged by jenkins-bot:
+QA: Define expected behaviour for VisualEditor overlay for bug 59932
+
+https://gerrit.wikimedia.org/r/109436",1391200206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"Change 109436 had a related patch set uploaded by Jdlrobson:
+QA: Define expected behaviour for VisualEditor overlay for bug 59932
+
+https://gerrit.wikimedia.org/r/109436",1391196909,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"**kwang** wrote:
+
+Unable to reproduce. I think this might actually have been the portrait landscape bug and I got confused.",1390456194,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"**kwang** wrote:
+
+This was originally if I launched keep going from the main page I was unable to get visual editor to launch. But this seems to be fixed now, or I am unable to reproduce anymore.",1390441148,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"Change 108990 had a related patch set uploaded by Jdlrobson:
+Make KeepGoing run when editing using VE
+
+https://gerrit.wikimedia.org/r/108990",1390429399,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"I don't understand this bug. You can't currently enter the KeepGoing campaign via VE. Kenan could you explain what the exact problem is here?
+
+Is the request that when I edit for the first time via VisualEditor it starts the Keep Going campaign to edit?",1390428453,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1614",1389403228,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+VisualEditor:Image size is appearing differently in the tooltip in  VE compared to the set value in Edit Source mode,"Screenshot in the Edit source mode
+
+Steps to reproduce:
+
+1.Open a page with VE 
+2.Insert any image
+3.Resize the image to specific size.For example:587x687px
+4.Save the page
+5.Open the page in Edit Source mode
+
+
+Observed Result:
+The Edit source mode shows the size of the image differently as 587x411
+
+Test Environment: mw.org
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12636}",1389383700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-42yujcjufaw4amwkd6cx,task_description,invalid
+VisualEditor:Image size is appearing differently in the tooltip in  VE compared to the set value in Edit Source mode,"After checking with the Parsoid team, this isn't a bug -- Parsoid serializes a square bounding box (max sizes) which is why the wikistring is different than the actual image size (that preserves aspect ratio).",1389827322,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-42yujcjufaw4amwkd6cx,task_subcomment,NA
+VisualEditor:Image size is appearing differently in the tooltip in  VE compared to the set value in Edit Source mode,"Created attachment 14285
+Size in the tooltip of VE
+
+**Attached**: {F12637}",1389383780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-42yujcjufaw4amwkd6cx,task_subcomment,NA
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"Intention:
+If I understand it correctly, the user defines a link target for text. This seems to highlight/mark the text for that user, so if the user then enters a space as the next letter as s/he wants to continue writing, this will overwrite the marked text. Says this happens with Safari 6.1.1 and Firefox 26.0 on OS X 10.7.5 and 10.8.5 (all four combinations). Haven't tried other browsers/operating systems. 
+
+Steps to Reproduce:
+1. Tried but could not duplicate this problem in Firefox 26 or Chrome 31
+2. 
+3. 
+
+
+
+Reproducible: Couldn't Reproduce
+
+Andre says: https://bugzilla.wikimedia.org/show_bug.cgi?id=57716 item 2# feels slightly related but not exactly the same.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://sv.wikipedia.org/wiki/Wikipedia:VisualEditor/%C3%85terkoppling#L.C3.A4nkad_text_blir_markerad_och_f.C3.B6rsvinner",1389313080,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-l4uq3cbllrcxoqio4v45,task_description,declined
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"I don't know about this; this is intentional behaviour to give users the ability to do something further with their selection (often laboriously-made) if they want to, especially for those primarily using keyboard input.
+
+When you click away from the inspector, we move the cursor to where you clicked it. However, if you're using keyboard driving, you might want to adjust the item you just selected and did an action on, e.g. adding bold/etc. styling.
+
+In general, we've designed the editor so that removing the selection using the keyboard needs you to destroy the selection (type over it) or move the cursor with the cursor keys. I don't think we want to move away from this model, so I'm going to mark this as WONTFIX, but I'd be happy to discuss further if people think this is a mistake.",1390023404,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l4uq3cbllrcxoqio4v45,task_subcomment,NA
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"Thanks, NH. :) Actually, I was able to reproduce it this time! The text that was to be linked was selected or highlighted so that it could be linked. Pressing enter the first time makes the linking box/window/popup go away. Pressing enter a second time makes the newly-linked text go away. The work around is to click with cursor elsewhere on the page so as to deselect/unhighlight the text. But if this can be fixed code wise, would save everyone one additional click. HTH. :)",1389375082,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-l4uq3cbllrcxoqio4v45,task_subcomment,NA
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"**nh.wikipedia** wrote:
+
+Anna Koval got it right, but I'll clarify anyway:
+
+1) Open some page for editing.
+2) Type a word that you wish to link to another page.
+3) Press Command-K or click at the link tool button.
+4) Select or type the name of the target page and press enter twice.
+5) When you continue to type the linked word disappears.
+
+If you, at step (4), click at the ""Close"" button in the link dialog instead of using the Enter key to complete, this does not happen.",1389349207,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-l4uq3cbllrcxoqio4v45,task_subcomment,NA
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"For the records: From https://sv.wikipedia.org/wiki/Wikipedia:VisualEditor/%C3%85terkoppling#L.C3.A4nkad_text_blir_markerad_och_f.C3.B6rsvinner
+
+I cannot reproduce in Firefox 26 on Fedora Linux 20 on cs.wikipedia.org - after clicking the ""Close"" button on the left in the ""Link target"" dialog the link text is not highlighted for me.",1389316714,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-l4uq3cbllrcxoqio4v45,task_subcomment,NA
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,"In read mode
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add few images to the page
+3.Save the Page
+4.Now click on any of the newly added images 
+5.Press back button from the browser to go back to the article
+
+Observed Result:
+The images in the page gets disappeared in the readmode though opening the VE shows up all the images.
+
+Test Environment:https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Wmf10
+
+
+See the screenshots attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12534}",1389309540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_description,declined
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,Cannot reproduce it now.,1389832746,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_subcomment,NA
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,This is occurring in mw.org too for adding any image.,1389387303,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_subcomment,NA
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,"Slight modification in the steps:
+
+1.Open a page with VE
+2.Add a heading/subheading to the page
+3.Place the cursor right after the heading text
+4.Insert an image
+5.Save the page
+6.Now click on any of the newly added images 
+7.Press back button from the browser to go back to the article
+
+Observed Result:
+The newly added image and the heading is not showing up in the readmode.",1389311591,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_subcomment,NA
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,"Created attachment 14276
+In edit mode
+
+**Attached**: {F12535}",1389309582,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_subcomment,NA
+VisualEditor:Cutting the section heading along with the content under it and pasting them back moves the heading under the content,"Section heading got moved below the link of heading
+
+Steps to reproduce:
+
+1.Open a page with VE which has a section with section heading
+2.Cut the whole section with its heading
+3.Paste it back in the same position
+
+Observed Result:
+The heading of the section gets placed under the heading line with the contect
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/9th_jan?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12519}",1389296400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kbipswhiezygmb4rkkls,task_description,resolved
+Fatal error: Call to a member function matchStartAndRemove() on a non-object at Parser.php on line 3262,"[09-Jan-2014 19:32:59] Fatal error: Call to a member function matchStartAndRemove() on a non-object at /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php on line 3262
+Server: mw1149
+Method: GET
+URL: http://www.mediawiki.org/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*
+Backtrace:
+#0 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(3262): Parser::braceSubstitution()
+#1 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPFrame_DOM))
+#2 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(3147): PPFrame_DOM->expand(Object(PPNode_DOM), 0)
+#3 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(620): Parser->replaceVariables('{{ns:project}}:...')
+#4 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(4842): Parser->preprocess('{{ns:project}}:...', NULL, Object(ParserOptions))
+#5 /usr/local/apache/common-local/php-1.23wmf10/includes/cache/MessageCache.php(1002): Parser->transformMsg('{{ns:project}}:...', Object(ParserOptions), NULL)
+#6 /usr/local/apache/common-local/php-1.23wmf10/includes/Message.php(856): MessageCache->transform('{{ns:project}}:...', false, Object(Language), NULL)
+#7 /usr/local/apache/common-local/php-1.23wmf10/includes/Message.php(592): Message->transformText('{{ns:project}}:...')
+#8 /usr/local/apache/common-local/php-1.23wmf10/includes/Message.php(649): Message->toString()
+#9 /usr/local/apache/common-local/php-1.23wmf10/extensions/VisualEditor/VisualEditorDataModule.php(94): Message->text()
+#10 /usr/local/apache/common-local/php-1.23wmf10/extensions/VisualEditor/VisualEditorDataModule.php(129): VisualEditorDataModule->getMessageInfo()
+#11 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoader.php(102): VisualEditorDataModule->getMessages()
+#12 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoaderStartUpModule.php(265): ResourceLoader->preloadModuleInfo(Array, Object(ResourceLoaderContext))
+#13 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoaderStartUpModule.php(150): ResourceLoaderStartUpModule->getModifiedTime(Object(ResourceLoaderContext))
+#14 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoaderStartUpModule.php(224): ResourceLoaderStartUpModule::getModuleRegistrations(Object(ResourceLoaderContext))
+#15 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoader.php(761): ResourceLoaderStartUpModule->getScript(Object(ResourceLoaderContext))
+#16 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoader.php(516): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#17 /usr/local/apache/common-local/php-1.23wmf10/load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#18 /usr/local/apache/common-local/w/load.php(3): require('/usr/local/apac...')
+#19 {main}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389296160,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-utvzk3vp6pazzmc524i4,task_description,resolved
+Fatal error: Call to a member function matchStartAndRemove() on a non-object at Parser.php on line 3262,"Seems to be l10n cache related, but is fixed",1389298261,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-utvzk3vp6pazzmc524i4,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in duplicated section headings","Intention:
+Cut the appendices from an article (to see if they were the source of a problem), and then put them back (because they weren't)
+
+Steps to Reproduce:
+1. Select several sections from the end of an article, all the way to the end of the page.
+
+2. Command-x to cut.
+
+3. Command-v to paste.
+
+Actual Results:  
+The section headings were duplicated, but the content was not.  The result is two sets of section headings, the first of which is empty.  
+
+https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FS%26D&diff=588724359&oldid=588539903
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389227760,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-atmvlu42kr6udcjperus,task_description,resolved
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in duplicated section headings","[[https://en.wikipedia.org/w/index.php?title=User%3ANeil_P._Quinn-WMF%2FT61847&diff=657363248&oldid=657363001|Seems to work correctly now]] in Safari 8.0.3, although the copy-and-pasting does produce some significant normalization that may be a separate issue.",1429554871,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-atmvlu42kr6udcjperus,task_subcomment,NA
+VisualEditor:The <nowiki/> tag remains even after deleting spaces in between the link and re-applying a new link on it,"wikitext after step 8
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Type the following text:
+Tex ted
+3.Select this part of the text ""Tex t"" with a space in between.
+4.Now apply a link on it with command+k
+5.Save the page.
+6.Go to Edit source and observe the resulting wikitext for this is:
+[[tex t]]<nowiki/>ed
+
+7.Now reopen the page delete the space make it ""texted"" and delete the link applied.
+8.Reapply another link by selecting the whole text ""texted""
+
+Observed Result:
+The <nowiki/> tag still remains.The resulting wikitext after step 8 is:
+[[texted|text]]<nowiki/>[[texted|ed]]
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan8th&action=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12427}",1389209520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r2uo7jsfp6tf7hhh7pgx,task_description,resolved
+VisualEditor:The <nowiki/> tag remains even after deleting spaces in between the link and re-applying a new link on it,"This is because <nowiki /s> (unlike <nowiki>s) are ""meta"" items in the DOM rather than things VE can edit; merging with bug 56381.
+
+*** This bug has been marked as a duplicate of bug 56381 ***",1390023700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r2uo7jsfp6tf7hhh7pgx,task_subcomment,NA
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"When a page is loaded in portrait mode the VisualEditor is not loaded. We should get clever about when to load it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389206760,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gjdaipusi2pbcwygi4nx,task_description,resolved
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"Change 110625 merged by jenkins-bot:
+Load Tablet styles if portrait or landscape meets threshold
+
+https://gerrit.wikimedia.org/r/110625",1391454312,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gjdaipusi2pbcwygi4nx,task_subcomment,NA
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"Change 110625 had a related patch set uploaded by Jdlrobson:
+Load Tablet styles if portrait or landscape meets threshold
+
+https://gerrit.wikimedia.org/r/110625",1391201166,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gjdaipusi2pbcwygi4nx,task_subcomment,NA
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"http://googlewebmastercentral.blogspot.com/2011/03/mo-better-to-also-detect-mobile-user.html has a few ideas.
+
+Kenan suggests if the diagonal length of the screen is greater than 5.1 inches than we should assume tablet.",1390344876,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gjdaipusi2pbcwygi4nx,task_subcomment,NA
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1603",1389207028,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gjdaipusi2pbcwygi4nx,task_subcomment,NA
+Enable VisualEditor in all namespaces,"At some point VisualEditor should be enabled in the remaining namespace.
+
+I've seen a few requests for it, so this tracking bug will also provide an easy answer for why it isnt feasible now. e.g.
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(proposals)&oldid=589149415#VE_on_Wikipedia:_namespace
+",1389178800,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dahdfluva5saanqyyruw,task_description,invalid
+Enable VisualEditor in all namespaces,"(In reply to comment #0)
+> At some point VisualEditor should be enabled in the remaining namespace.
+
+{{cn}} :-)
+
+Right now I believe that VE is enabled on Wikipedias like enwiki in all namespaces except:
+
+1. the Talk namespaces;
+2. the Project namespace (Wikipedia:);
+3. the Lua namespace (Module:);
+4. the Template namespace; and
+5. the MediaWiki namespace.
+
+There are some (related) reasons for these:
+
+1. We don't ever intend for VisualEditor to be a good tool for editing signed content; the goals of a content editor with indenting and insertion do not mesh with those of a discussion editor. Instead, Flow will provide a VisualEditor surface for commenting in a proper system that makes sense. Enabling VE for talk namespaces on the WMF cluster is a WONTFIX from my point of view.
+
+2. The Project namespace contains a great deal of signed content, and so is not currently appropriate for VisualEditor per the reasoning above. Once Flow is fully up and running, switching VisualEditor on for the remaining (non-discussional) content is just a matter of flicking a switch. However, the point where Flow has replaced all Project namespace uses of signed content is probably a long way away.
+
+3. Lua code already has its own editor (quite why it has its own namespace instead of sitting as a ContentHandler object in the MediaWiki namespace like CSS and JS I don't know); VE doesn't add anything there.
+
+4. Templates are messy agglomerations of partial wikitext and lots of transclusion calls. I'm not sure VE would shine at its best here. We could enable it if you really think it would be useful (and can show community approval), though…
+
+5. Similarly, MediaWiki messages often contain messy partial wikitext (let alone partial HTML), and we are after all trying to discourage its use.
+
+
+
+On the particular ""blocking"" bugs:
+
+* bug 48429 – I don't see how this prevents VE from being deployed to further namespaces; it's mainly a problem in the content namespace (where it's already deployed), and would be in discussions (where we're not going to deploy it).
+* bug 50172 – Again, I don't see how this prevents VE from being deployed to further namespaces, given that it's mainly a problem between content, Draft and User (where it's deployed now).
+* bug 51154 – Though this would be necessary for deploying to Talk namespaces, see above.
+* bug 51899 – I don't understand how this blocks VE from being deployed to further namespaces.
+* bug 52141 – Same here.
+* bug 59229 – Yet another reason why we don't want to enable VE in discussions.
+* bug 59885 – This is currently only a super-class for bug 48429, and is not actually blocking deployment to the Draft: namespace because that happened.
+
+Consequently, I'm going to remove the dependencies and close this bug as INVALID. Happy to re-open if I'm wrong, though. :-)",1389987954,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dahdfluva5saanqyyruw,task_subcomment,NA
+"VisualEditor:""NetworkError: 404 Not Found"" appears while creating a new page with VE in FireFox 25","Screenshot
+
+Steps to reproduce:
+
+1.Attempt to create a new page with VE in FireFox 25 in any way.For example:Type this URL:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Textnew&veaction=edit
+
+Observed Result:
+
+An error appears in the console:
+
+""NetworkError: 404 Not Found - http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Textnew&veaction=edit""
+index....on=edit
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12343}",1389124080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ufqs3dhnocvsaimspsxt,task_description,declined
+"VisualEditor:""NetworkError: 404 Not Found"" appears while creating a new page with VE in FireFox 25",Not occurring anymore on test 2,1389910433,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ufqs3dhnocvsaimspsxt,task_subcomment,NA
+"VisualEditor:""NetworkError: 404 Not Found"" appears while creating a new page with VE in FireFox 25","However, the page can be created even though the error appears.",1389124265,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ufqs3dhnocvsaimspsxt,task_subcomment,NA
+"VisualEditor: "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears while opening up Categories dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the Categories Dialog box from Settings>Categories
+
+Observed Result:
+The error "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears in the console.
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan7th&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12329}",1389122820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jf4ozwjh3vlshz4bzqkm,task_description,declined
+"VisualEditor: "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears while opening up Categories dialog box",Not appearing any more .Got fixed in wmf11,1389909731,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jf4ozwjh3vlshz4bzqkm,task_subcomment,NA
+"VisualEditor: "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears while opening up Categories dialog box","Created attachment 14259
+Settings>Page Settings
+
+**Attached**: {F12330}",1389213979,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jf4ozwjh3vlshz4bzqkm,task_subcomment,NA
+"VisualEditor: "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears while opening up Categories dialog box","The error also appears when user goes to Setting>Page Settings.
+Screenshot attached",1389213930,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jf4ozwjh3vlshz4bzqkm,task_subcomment,NA
+Removing a blank == <nowiki /> == section heading leaves a <nowiki /> and produces a dirty diff,"Intention:
+Remove an empty section heading created in a previous edit (bug 59647) by VisualEditor
+
+Steps to Reproduce:
+1. Select the empty section heading
+2. Press the delete/backspace key
+
+
+Actual Results:  
+The line went away.  However, a nowiki tag remained, and the first item in the list of categories was added to the last paragraph on the page, instead of remaining on its own line.
+
+Expected Results:  
+The section heading would go away.  Zero nowiki tags would be present.  Content above and below would not get smashed into a single line.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Celebrity_branding&diff=589156903&oldid=589156664",1388854020,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-e3i52jzvuvgyt4mfbiae,task_description,resolved
+Removing a blank == <nowiki /> == section heading leaves a <nowiki /> and produces a dirty diff,"This is because <nowiki /s> (unlike <nowiki>s) are ""meta"" items in the DOM
+rather than things VE can edit; merging with bug 56381.
+
+*** This bug has been marked as a duplicate of bug 56381 ***",1390023730,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e3i52jzvuvgyt4mfbiae,task_subcomment,NA
+VE automatically cuts off certain characters,"On the page on mediawiki.org https://www.mediawiki.org/wiki/Manual:ISBN (check action=history) VisualEditor keeps removing certain characters after I try to use it to make changes to the page. An example is given at https://www.mediawiki.org/wiki/VisualEditor:Test
+
+Reproduction steps:
+1. Set up a new page using the following code
+<space><space><space><url><apostrophe>
+<newline><space><space><space>
+example text1
+
+example text2
+Where <space> is one hit of the spacebar and <url> could be any URL
+2. Modify other places in the text, such as ""example text2"".
+3. See the first character in ""example text1"" get cut off.
+4. Modify ""example text2"" again and see ""example text1"" get cut off again.
+
+Example permalink: https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&oldid=873656
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388796000,PHID-USER-uhn27l5qsridnw4vbhko,PHID-TASK-sb5pc5upei6lbqlstsbe,task_description,resolved
+VE automatically cuts off certain characters,Non-reproducible - most likely fixed.,1421790530,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-sb5pc5upei6lbqlstsbe,task_subcomment,NA
+VisualEditor:  Can't save page after simple editing,"Intention:
+Copyedit an article
+
+Steps to Reproduce:
+1. I italicized two words.  I cut two sentences (including links and one ref) and pasted them in a different place.
+2. I tried to save the page.
+
+
+Actual Results:  
+The ""Save"" button looks normal, but clicking on it does nothing.
+
+Expected Results:  
+That I could save the page.  When I re-opened the page in VisualEditor and made the same changes, it worked (https://en.wikipedia.org/w/index.php?title=Neuralgia&diff=589057635&oldid=580866827).
+
+Reproducible: Couldn't Reproduce
+
+Firefox 26
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388793420,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5i5trthg3bfis3yeyeyg,task_description,invalid
+VisualEditor:  Can't save page after simple editing,"Also, in cases like this where pressing things (buttons etc.) appear to have no affect, you should try checking the JS console for errors.",1414811783,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-5i5trthg3bfis3yeyeyg,task_subcomment,NA
+VisualEditor:  Can't save page after simple editing,"(Quoting WhatamIdoing from comment #0)
+> Reproducible: Couldn't Reproduce
+
+Invalid/worksforme from creation then...",1414811622,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-5i5trthg3bfis3yeyeyg,task_subcomment,NA
+"VisualEditor: [Regression] Checkbox ""Watch this page"" in save dialog unchecked even that page is watched","Checkbox ""Watch this page"" in save dialog unchecked even that page is watched
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388779620,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-dqr5vyv74wju5geh4nth,task_description,resolved
+"VisualEditor: [Regression] Checkbox ""Watch this page"" in save dialog unchecked even that page is watched",This was fixed in the re-write in early January; sorry for the slow triage.,1394063679,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dqr5vyv74wju5geh4nth,task_subcomment,NA
+"VisualEditor:""TypeError: response.visualeditor is undefined"" appears while opening up the dialog box for adding catagories","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in FireFox
+2.Click on the Categories button to open up the dialog box to add categories
+
+Observed Result:
+TypeError: response.visualeditor is undefined appears in the console
+
+See the screenshot attached
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/3rd_janff?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12794}",1388778720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vvjswcot4n4j42ahvoek,task_description,declined
+"VisualEditor:""TypeError: response.visualeditor is undefined"" appears while opening up the dialog box for adding catagories",Not appearing anymore.got fixed in wmf11,1389910015,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vvjswcot4n4j42ahvoek,task_subcomment,NA
+VisualEditor: edits correctly saved are missing on da.wp,"Intention:
+I used my userpage as a sandbox
+https://da.wikipedia.org/w/index.php?title=Bruger:Elitre_(WMF)&action=history,
+and the edits in which I tried to add references do not show up in the history,
+although I did manage to save them and also got the message that confirms this.
+
+(For the record, I was trying to reproduce
+https://da.wikipedia.org/w/index.php?title=F-35_Lightning_II&diff=prev&oldid=7409486
+and
+https://da.wikipedia.org/w/index.php?title=Enhedslisten&diff=prev&oldid=7414100
+, where there might be a connection between adding a reference and getting a
+duplicated infobox).
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388769060,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-uh22mktin45cgziwuwry,task_description,resolved
+VisualEditor: edits correctly saved are missing on da.wp,Alright!,1432727427,PHID-USER-vignevg3qewvdhgbbwuh,PHID-TASK-uh22mktin45cgziwuwry,task_subcomment,NA
+VisualEditor: edits correctly saved are missing on da.wp,"If you can't reproduce any longer, given how old the task is, feel free to close - it can be reopened if and when the need arises.",1432646739,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-uh22mktin45cgziwuwry,task_subcomment,NA
+VisualEditor: edits correctly saved are missing on da.wp,I can't duplicate this - adding references works fine and the edits show up in my history.,1432480626,PHID-USER-vignevg3qewvdhgbbwuh,PHID-TASK-uh22mktin45cgziwuwry,task_subcomment,NA
+VisualEditor: edits correctly saved are missing on da.wp,Reproducible: Always?,1421888114,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-uh22mktin45cgziwuwry,task_subcomment,NA
+VisualEditor:  Cutting and pasting internal links converts them to external links in Firefox,"Intention:
+Move a sentence to a diffeent place on the page.
+
+Steps to Reproduce:
+1. In Firefox, open a page containing existing [[links]] to other pages on the wiki.
+2. Cut one of them.
+3. Paste it in a different spot.
+
+Actual Results:  
+The link gets converted from [[Link]] into [http://en.wikipedia.org/wiki/Link].
+
+See https://en.wikipedia.org/w/index.php?title=User:Edgepedia/VE/S%26D&diff=588724142&oldid=588539903 and https://en.wikipedia.org/w/index.php?title=Silaum_silaus&diff=588803158&oldid=587979575  
+
+Expected Results:  
+The [[Link]] would remain an internal link.
+
+Reproducible: Sometimes
+
+One of these pages involved the {{sfn}} (shortened footnotes) template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388682000,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zwykrgbpiln6fvzmfzeo,task_description,resolved
+VisualEditor:  Cutting and pasting internal links converts them to external links in Firefox,"Merging with bug 58136.
+
+*** This bug has been marked as a duplicate of bug 58136 ***",1390024188,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zwykrgbpiln6fvzmfzeo,task_subcomment,NA
+Page redirects are not recognized by VisualEditor's link inspector,"1. Edit an article with VisualEditor
+2. Select a word for which a redirect exists (not an actual page)
+3. Click the ""link"" icon.
+
+EXPECTED
+
+Since a redirect exists, the link inspector shows the option in blue (since the link is functional). All the better if it is shown in italics, just like redirects are shown by MediaWiki in lists of pages.
+
+ACTUAL
+
+Redirects are ignored by the link inspector. They appear just as red as a missing string. This creates a lot of extra work having to search the string manually in another window.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50593
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50240",1388672340,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dvyukuw5fsuzum36qlzx,task_description,resolved
+Page redirects are not recognized by VisualEditor's link inspector,"Merging with bug 49502.
+
+*** This bug has been marked as a duplicate of bug 49502 ***",1390024134,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dvyukuw5fsuzum36qlzx,task_subcomment,NA
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","Intention:
+Click on a link within VisualEditor
+
+Steps to Reproduce:
+1. Open an existing page in a subpage (e.g., User:Example/Sandbox)
+2. Control-click on any [[link]] and copy the link
+3. Paste the link somewhere to see what it says
+
+
+Actual Results:  
+Instead of the expected link to en.wikipedia.org/wiki/Link, the user saw links to en.wikipedia.org/wiki/User:Username/Link.  When this intermittent problem was happening, then all links on the page would do it.  However, it only happened during some editing sessions/some days.
+
+
+
+Reproducible: Sometimes
+
+Firefox 26 on Windows 7, Vector skin.  Is intermittent there; could not be immediately reproduced in either Firefox or Safari on a Mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48915
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58314",1388619840,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gvtbr3mwdnel75bfmsye,task_description,resolved
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","
+
+*** This bug has been marked as a duplicate of bug 58314 ***",1395363345,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gvtbr3mwdnel75bfmsye,task_subcomment,NA
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","Change 119914 had a related patch set uploaded by Catrope:
+Hack around Parsoid's href prefixing in rendering new links
+
+https://gerrit.wikimedia.org/r/119914",1395363135,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvtbr3mwdnel75bfmsye,task_subcomment,NA
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","
+
+*** This bug has been marked as a duplicate of bug 58314 ***",1395344109,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gvtbr3mwdnel75bfmsye,task_subcomment,NA
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","The brilliant ""Codename Lisa"" has figured out how to reproduce it consistently:
+
+1. Open a user subpage.
+2. Create a new link to an article on main space, e.g. [[Link]]
+3. Control-click on the link and copy it (or open the link in a new window)
+4. Discover that the link leads to [[User:YOURUSERNAME/Link]].
+
+More interestingly:
+
+1. Open a user subpage.
+2. Create a new link to an article on main space, e.g. [[Link]].
+3. Control-click on the link and copy it (or open the link in a new window)
+4. Save the page.
+5. Re-enter edit mode.
+6. Control-click on the same link again.
+7. Discover that the link now leads to [[Link]].
+
+Expected result:
+
+In both steps 3 and 6, the article must open at [[Link]], not at [[User:Username/Link]].
+
+Actual result:
+
+In step 3, a subpage with the same {{SUBPAGENAME}} as the link name opens. Step 6 is always successful. Pre-existing links open correctly.",1388634535,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gvtbr3mwdnel75bfmsye,task_subcomment,NA
+VisualEditor:Clear formatting removes the link from a text,"Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text  
+3.Apply some formatting from the formatting menu in the toolbar for example:
+Bold/Italic/Superscript
+4.Also apply a link on the text
+5.Now from the formatting menu select the ""Clear formatting"" option
+
+Observed Result:
+
+Along with all the text formatting, the link applied on the text also gets removed.
+It is better if Clear formatting only removes the text formatting not the link applied because that is not part of text formatting options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388609640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wsp5xk3lssgxslzaamko,task_description,resolved
+VisualEditor:Clear formatting removes the link from a text,"
+
+*** This bug has been marked as a duplicate of bug 51757 ***",1390025103,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wsp5xk3lssgxslzaamko,task_subcomment,NA
+"VisualEditor:Cannot go to the next line of an article after copy-paste of an hiero as the error ""TypeError: outermostNode is null"" appears","TypeError
+
+Steps to reproduce:
+
+1.Open a page with VE which contains a hiero
+2.Copy the hiero
+3.Open another page in FireFox with VE
+4.Paste the heiro
+5.Save the page
+6.Reopen the page and Press enter to go to the next line after the hiero
+
+Observed Result:
+Cannot go to the next line of an article after copy-paste of an hiero.The following error appears in the console:
+ 
+TypeError: outermostNode is null
+
+	
+
+...documentModel,selection.from,'\n');}else{node.traverseUpstream(function(node){if...
+
+load.p...4146Z&* (line 261)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12558}",1388272560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ok75mzddmda57d6nn6kk,task_description,resolved
+"VisualEditor:Cannot go to the next line of an article after copy-paste of an hiero as the error ""TypeError: outermostNode is null"" appears",This looks like we fixed it ages ago.,1442271794,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ok75mzddmda57d6nn6kk,task_subcomment,NA
+"VisualEditor:Cannot go to the next line of an article after copy-paste of an hiero as the error ""TypeError: outermostNode is null"" appears","Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=28th_decemberff&veaction=edit",1388272698,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ok75mzddmda57d6nn6kk,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","Screenshot of the error
+
+I have got this error several times in Betalabs recently,it happens if I keep VE open for a while for a page and then do some more edit and hit the ""Save Page"" button.
+I was still logged in to the previous session when this error appeared.
+
+""TypeError :this.timings is undefined ""
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12542}",1388267400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bexcdxbi3u4bthv7sscm,task_description,resolved
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","This was caused by a call to `.this.events.track()` in a detached way, which means `this` isn't bound and `ArticleTargetEvents` members like `timings` would not be found. This has since been fixed (based on the current code), though I can't find the exact commit.",1495794415,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while",Is this still occurring?,1439321337,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","Whoops, sorry, you're right!
+
+I use Firefox 26.0 on Ubuntu 12.04 LTS.",1389280808,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","(In reply to comment #1)
+> Happens frequently in Firefox under Ubuntu too
+
+Version information welcome, in general (don't know which version of Firefox is shipped on which version of Ubuntu).",1389263927,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","Happens frequently in Firefox under Ubuntu too, I have to click the ""Save"" twice to get it to actually save.",1389223764,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Selecting the whole line
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text to apply the paragraph format ""Preformatted"".Select the text in a way so that it selects the whole line.Check the screenshot of selection to better understand.
+
+3.Now select the option preformatted from paragraph styling options
+
+Observed Result:
+The Preformatted option gets applied to the other following text/element even though they are not selected.
+
+If the selection is done such way that it spans multiple empty lines then the preformatted options gets applied to those empty lines too.
+
+See the screenshots attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/28th_december
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12538}",1388266140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vgvl47jspv2pkkjrsfci,task_description,invalid
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","The selection of the following line is different than selecting the text on the line. If you choose to select just the text, you will get the behavior you are looking for. If you select the line and it's break (or empty lines after it) then you will get the behavior you are reporting as a bug.
+
+This is not a bug, it's doing exactly what it should. However, it may be valuable to revisit how we can better communicate what is selected and how to achieve the desired result to the user.
+
+Unfortunately, we have limited control over selection because we use ContentEditable, which is provided by the browser. The selection of a line and it's break may be something we can disable, but likely there will be negative effects on user experience and browser compatibility.
+
+Marking as invalid, since this is not a bug, but a known feature. I'm happy to discuss the UX impact of this feature and possible changes that could improve the situation on a different, enhancement, bug.",1391810383,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Sorry, I think I could not explain it properly in my steps.The issue was not about applying the format on the whole line rather on an immediate following line which was not selected.
+
+For example the content of a page is as follows:
+
+The text
+another text
+
+
+
+Not selected text
+
+
+Now if you select ""the text"" and ""another text"" but stop the selection just above the line ""Not Selected text"" and apply the format, it gets applied to ""Not Selected text""
+
+So, I am reopening the bug again as it is a different issue.",1390334416,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Yes, content formatting applies to the line(s) selected, not the text selection. This is by design (rather than splitting the text). Closing as WONTFIX, but happy to discuss if someone things we should split instead.",1390022822,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Created attachment 14184
+Observed Result
+
+**Attached**: {F12541}",1388266232,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Created attachment 14183
+Selecting multiple lines
+
+**Attached**: {F12539}",1388266192,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+VisualEditor:  List formatting not applied unless there is a blank line between items,"Intention:
+Turn a list of seven single-spaced items into a properly formatted list.
+
+Steps to Reproduce:
+1. Start with a page that contains a list of items that do not have blank lines between them.
+
+2. Open VisualEditor and select all the items.
+
+3. Click the 'list' button.
+
+Actual Results:  
+Only the first item is given list formatting.
+
+If some items are double-spaced and others are not, then double-spaced items are given list formatting, and any items without a blank line above them (except the first item, which always becomes list-formatted) is left as a plain paragraph rather than being formatted as a list item.
+
+Expected Results:  
+All the items would be given list formatting.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=587947827&oldid=587947700",1388168880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lowf6tecq6p7hjj3ouia,task_description,duplicate
+VisualEditor:  List formatting not applied unless there is a blank line between items,"At https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=587948540&oldid=587948443 you can see the 'workaround'.  This wikitext:
+
+* Monday is washing day.
+Tuesday is ironing day.
+Wednesday is mending day.
+Thursday is marketing day.
+Friday is cleaning day.
+Saturday is baking day. 
+
+displays like this in view mode:
+
+* Monday is washing day.
+Tuesday is ironing day. Wednesday is mending day. Thursday is marketing day. Friday is cleaning day. Saturday is baking day. 
+
+and displays like this within VisualEditor:
+
+* Monday is washing day.
+Tuesday is ironing day.↵Wednesday is mending day.↵Thursday is marketing day.↵Friday is cleaning day.↵Saturday is baking day. 
+
+If you select the subsequent items (Tuesday through Saturday), and click the button to apply list formatting, then only the ""Tuesday"" line acquires list formatting.  This looks in VisualEditor like this:  
+
+* Monday is washing day.
+* Tuesday is ironing day.↵Wednesday is mending day.↵Thursday is marketing day.↵Friday is cleaning day.↵Saturday is baking day. 
+
+If you save and re-open, you see this:
+
+* Monday is washing day.
+* Tuesday is ironing day.
+
+Wednesday is mending day.↵Thursday is marketing day.↵Friday is cleaning day.↵Saturday is baking day. 
+
+and the wikitext is this:
+
+* Monday is washing day.
+
+* Tuesday is ironing day.
+
+Wednesday is mending day.
+Thursday is marketing day.
+Friday is cleaning day.
+Saturday is baking day. 
+
+(Notice the HTML-list-formatting-breaking unwanted blank line between Monday and Tuesday.)
+
+Selecting the ""↵"" and hitting return produces the desired list.",1388169341,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lowf6tecq6p7hjj3ouia,task_subcomment,NA
+VisualEditor:500 (Internal Server Error) appearing while creating a link on betalabs,"Steps to reproduce:
+
+1.Open the editor for a page
+2.Create a link
+
+
+Observed Result:
+There is no suggestion appearing for the link creation and also in the console the error 500 (Internal Server Error) appearing
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388081580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-upb3ctljk2bwd7r3gsy3,task_description,declined
+VisualEditor:500 (Internal Server Error) appearing while creating a link on betalabs,This issue is not appearing anymore,1388167884,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-upb3ctljk2bwd7r3gsy3,task_subcomment,NA
+VisualEditor:500 (Internal Server Error) appearing while creating a link on betalabs,"There is a similar error appearing while adding media files to the page too.
+
+The error is as following:
+GET http://en.wikipedia.beta.wmflabs.org/w/api.php?callback=jQuery1830288604790…imit=15&gsroffset=0&prop=imageinfo&iiprop=dimensions%7Curl&iiurlheight=150 500 (Internal Server Error) load.php:128",1388082003,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-upb3ctljk2bwd7r3gsy3,task_subcomment,NA
+VisualEditor:500 (Internal Server Error) appearing while creating a link on betalabs,"Created attachment 14171
+Screenshot of the error
+
+**Attached**: {F12356}",1388081695,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-upb3ctljk2bwd7r3gsy3,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"I know this could be my fault, but I checked everything and it looks like it's a bug. Please correct me if I am wrong.
+
+Whenever I click the edit button the webpage does nothing. I see from the javascript debugger that the code stops at this line:
+
+return typeof jQuery !== ""undefined"" && (!e || jQuery.event.triggered !== e.type) ? jQuery.event.dispatch.apply(eventHandle.elem, arguments) : undefined;
+
+Any clues?
+
+I checked parsoid, tried creating a new settings file with minimal options, upgraded to latest trunk version both core and visualeditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1388002080,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-rafw5v7fpv6llvfw3itz,task_description,invalid
+Edit button not working -  empty /lib folder after downloading VE extension,"(In reply to comment #8)
+> When you download the VE extension, the lib folder is empty. (well, only an
+> empty subfolder). This is the cause.
+The empty folder is a submodule. Run 'git submodule update --init' to download it, and 'git submodule update' to update it after running git pull.",1389632091,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"When you download the VE extension, the lib folder is empty. (well, only an empty subfolder). This is the cause.",1389629778,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,Is there anything relevant in the Apache error log (could be folder/file access permissions)? Or in the debug log (see https://www.mediawiki.org/wiki/Manual:How_to_debug#Setting_up_a_debug_log_file )?,1389629712,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"Screen shot of console errors
+
+**Attached**: {F12331}",1389629299,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"**sumanah** wrote:
+
+Mc128k in #mediawiki just now confirmed that s/he has tried upgrading to the latest git master of VE and the bug still occurs.",1389629233,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"Adding more infos: debugging shows many 404 errors, and the lib/ve/ folder is empty. Something went very wrong with some git merge I think.",1388443150,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"I tried installing a clean mediawiki with only VE with a local sqlite database. Same issue, not even picked my config file, made one new.",1388273711,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"It’s a private wiki, but VE should work even with readonly access (at least it worked before) by entering ?veaction=edit at the end of the URL. I tried firefox and Safari for Mac.
+
+This worked and now it doesn’t: http://wiki.mc128k.info/index.php?title=Test&veaction=edit
+
+I also noticed that if I click edit from the read tab it does nothing, if I click edit from the edit source tab it changes the URL, but nothing again.
+
+Thanks.",1388020068,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,Any link to reproduce the problem? Which browser(s) does this happen with?,1388002194,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+VisualEditor:The page alignment of the articles in betalabs is appearing more towards left,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page with editor.
+2.Add some content and image
+3.Save the page
+
+Observed Result:
+The content of the page is appearing more condensed and all the images are no more right aligned.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12290}",1387918680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-36ttyeifxhhwq5q4jnq3,task_description,resolved
+VisualEditor:The page alignment of the articles in betalabs is appearing more towards left,This was the ill-advised changes to the Typography Refresh update.,1439321255,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-36ttyeifxhhwq5q4jnq3,task_subcomment,NA
+VisualEditor:The page alignment of the articles in betalabs is appearing more towards left,This is happening on test2 too for both Chrome and FireFox,1390429043,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-36ttyeifxhhwq5q4jnq3,task_subcomment,NA
+VisualEditor:The page alignment of the articles in betalabs is appearing more towards left,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/Link_to_catapult",1387918821,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-36ttyeifxhhwq5q4jnq3,task_subcomment,NA
+VisualEditor:Betalabs is not loading properly in Chrome 26.0.1410.65,"screenshot
+
+I was trying to open some page on betalabs , it appears that none of the resources are loading properly.
+
+Getting some errors like following while attempting to login:
+Failed to load resource https://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=…m%7Cskins.common.interface%7Cskins.vector.styles&only=styles&skin=vector&*
+Failed to load resource https://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*
+Failed to load resource https://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*
+Failed to load resource https://upload.beta.wmflabs.org/wikipedia/en/b/bc/Wiki.png
+Failed to load resource https://bits.beta.wmflabs.org/static-master/skins/vector/images/search-ltr.png?303-4
+Failed to load resource https://bits.beta.wmflabs.org/images/wikimedia-button.png
+Failed to load resource https://bits.beta.wmflabs.org/static-master/skins/common/images/poweredby_mediawiki_88x31.png
+
+Please see the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12273}",1387905720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qcobbntfbebu2v6aryi,task_description,resolved
+VisualEditor:Betalabs is not loading properly in Chrome 26.0.1410.65,"Beta bits cluster issues, now fixed.",1390025257,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7qcobbntfbebu2v6aryi,task_subcomment,NA
+VisualEditor:Betalabs is not loading properly in Chrome 26.0.1410.65,"Before facing this issue , I was prompted with warning of server's certificate not trusted, after proceeding anyway its using https protocol to load the pages.",1387906203,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qcobbntfbebu2v6aryi,task_subcomment,NA
+VisualEditor:Betalabs is not loading properly in Chrome 26.0.1410.65,"The page I tried to open was: https://en.wikipedia.beta.wmflabs.org/wiki/Link_to_catapult
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5",1387905798,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qcobbntfbebu2v6aryi,task_subcomment,NA
+VisualEditor:  Clicking on parameters in the reference dialog box selects the wrong parameter,"Intention:
+Add a citation template
+
+Steps to Reproduce:
+1. Choose Insert > Reference
+
+2. Choose Insert > Transclusion
+
+3. Type ""Cite web"" into the box. Hit return twice.
+
+4. Click ""URL access date"" to add that parameter to the list. Cursor jumped back to ""Add parameter"" (not unreasonable; you might want to add lots of parameters before filling any of them in).
+
+5. Click ""URL access date"", which is now the first item in the left-hand column's list of parameters, so I can add today's date to my reference. Cursor jumped back to ""Add parameter"" (definitely unreasonable).
+
+6. Repeat that step as many times as you feel like.
+
+7. Give up and click on the second parameter, which is ""Source title"". Cursor jumped to the parameter box for ""URL access date"".
+
+8. Click on the third parameter in the list, which is ""URL"". Cursor jumped to the parameter box for ""Source title"". The only way to fill in any information for the last parameter in the list is to scroll down the list in the right-hand column.
+
+9. Read the article on [[:en:Fencepost error]].  
+
+
+
+Expected Results:  
+That clicking on the second parameter would actually take me to the second parameter, not to the first one.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1387846800,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rfypkehjlixpt65ao4mm,task_description,resolved
+VisualEditor:  Clicking on parameters in the reference dialog box selects the wrong parameter,This was fixed in gerrit 99749.,1390023047,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rfypkehjlixpt65ao4mm,task_subcomment,NA
+"VisualEditor:After deleting a reference list along with reference, the order of the first reference does not get deleted in FireFox 25","Selecting the reference with reference list
+
+Steps to reproduce:
+
+1.Open a page which has reference and reference list with VE on FireFox25
+2.Select the reference and the reference list and press delete
+3.Save the page
+
+Observed Result:
+
+In Edit mode the order (1.) remains in the page.However, in the read mode the order will not appear.In edit source mode , there is a # appearing.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/The_title
+
+The wikitext of the page before deleting:
+reference<ref>refererence</ref>
+<references />
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12253}",1387839660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-slqzyalxfqafkznbvky4,task_description,declined
+"VisualEditor:After deleting a reference list along with reference, the order of the first reference does not get deleted in FireFox 25","Unfortunately closing this Phabricator task as no further information has been provided. If anyone can still reproduce in a recent browser version, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks!",1589143295,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-slqzyalxfqafkznbvky4,task_subcomment,NA
+"VisualEditor:After deleting a reference list along with reference, the order of the first reference does not get deleted in FireFox 25",Is this still occurring?,1439321198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-slqzyalxfqafkznbvky4,task_subcomment,NA
+VisualEditor: A lock icon is appearing in all references for a reference list in Firefox in test2,"screenshot of the lock icon appearing
+
+Steps to reproduce:
+
+1.Open the editor for a page which contains some references and a reference list
+
+2.Copy the references and the reference list and paste into anothe rVE
+
+3.Save the page
+
+Observed Result:
+
+A lock icon is appearing beside the reference for a reference list in FireFox in test2 
+Page:https://test2.wikipedia.org/wiki/23rdtemplatepaste
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12241}",1387833720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nhlyafdpxr6icar37fw4,task_description,invalid
+VisualEditor: A lock icon is appearing in all references for a reference list in Firefox in test2,This is because the links are to HTTPS sites.,1401472953,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nhlyafdpxr6icar37fw4,task_subcomment,NA
+VisualEditor:Cannot create a new page using VE on FireFox25 in test2,"the screenshot of the error
+
+Steps to reproduce:
+
+1.Open the editor for a existing VE
+2.Create a link to a new page
+3.Click on the link to open that new page in the same or a new tab
+4.Click on the Create button
+
+Observed Result:
+
+Ve does not load,An error is shown on the console:
+TypeError: list[firingIndex] is undefined
+	
+
+....split(core_rspace),function(_,flag){object[flag]=true;});return object;}jQuery....
+
+load.p...025514Z (line 12)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12227}",1387830960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2yxmskm3croyyjfnp4wh,task_description,declined
+VisualEditor:Cannot create a new page using VE on FireFox25 in test2,"Yes,it happens for every page including new page when I switch from wikitext editor to VE.
+But yes, it does not happen when I visit the page in read mode first by typing the address to go to the link directly",1387835318,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2yxmskm3croyyjfnp4wh,task_subcomment,NA
+VisualEditor:Cannot create a new page using VE on FireFox25 in test2,I cannot reproduce this in quick testing (FF 25.0.1/Mac 10.9.1) – is this on every new page when transitioning from the wikitext editor to VE? Does it happen if you visit the page first in read mode? What about if you go directly to the link by typing in the address by hand?,1387834060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2yxmskm3croyyjfnp4wh,task_subcomment,NA
+VisualEditor:Image is appearing as link after copy paste from another VE in FireFox,"Screenshot
+
+Steps to reproduce:
+
+1.Open the Editor for a page which contains an image with FireFox
+
+2.Copy the image and paste it into another VE
+
+3.Save the page.
+
+Observed Result:
+After copy paste before saving it appears as an uneditable object in VE .After saving the image appears as a link in the page as follows:
+
+In read mode and Edit mode: 
+
+link=https://test2.wikipedia.org/wiki/File:158869_at_Truro.JPG|200x200px
+
+In Edit Source mode:[[undefined|link=https://test2.wikipedia.org/wiki/File:158869_at_Truro.JPG|200x200px]]
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also:**
+{T78026}
+
+**Attached**: {F12212}",1387825020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jsdvuoacpjes6iw6v4vx,task_description,resolved
+VisualEditor:Image is appearing as link after copy paste from another VE in FireFox,This has probably been fixed for a while.,1426872997,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jsdvuoacpjes6iw6v4vx,task_subcomment,NA
+VisualEditor:Image is appearing as link after copy paste from another VE in FireFox,This is occurring in mw.org now,1389381557,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jsdvuoacpjes6iw6v4vx,task_subcomment,NA
+VisualEditor:Image is appearing as link after copy paste from another VE in FireFox,"Created attachment 14161
+Before Saving
+
+**Attached**: {F12213}",1387825068,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jsdvuoacpjes6iw6v4vx,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"In http://en.wikipedia.beta.wmflabs.org/
+Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387819560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-patmtmusp6dirpvlwuru,task_description,resolved
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"
+
+*** This bug has been marked as a duplicate of bug 58897 ***",1387841449,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"This was an artifact of today's issue with database connections, resolved after restarting apaches on beta",1387838675,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,The issue is not happening now.,1387838546,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"okay will verify it, once bug 58897 gets resolved.",1387821592,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"On the few times when bug 58897 isn't having an effect so I can see the page, it seems to work for me right now…",1387820845,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"Created attachment 14158
+screenshot
+
+**Attached**: {F12188}",1387819632,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor: Support <code> elements for text styling.,"Support adding and removing <code> elements.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387581000,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-744uhoqz2qaraesrqoyi,task_description,resolved
+VisualEditor: Support <code> elements for text styling.,This was done in July last year.,1394480631,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-744uhoqz2qaraesrqoyi,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,"I tried to give L10n-bot the correct access rights, but failed; I've removed my attempts again. Please give L10n-bot the rights at URL so that it can merge its own submits, like in MediaWiki repos.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**URL**: https://gerrit.wikimedia.org/r/#/admin/projects/wikimedia/wikimania-scholarships,access",1387579080,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-eumorghlixcu2bg3vnve,task_description,resolved
+Allow L10n-bot to merge in several Gerrit repos,"Nothing new or different. Give Code Review / Verified / Submit to the l10n-bot group.
+
+I did it in VisualEditor/* and oojs/* so those repo hierarchies will be fine from now on.",1391531703,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,"Thanks, Chad. Can you explain what you did? This may make a future occurrence ore easy to resolve.",1391530424,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,Done.,1391529275,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,"The same issue exists for the following repos:
+* VisualEditor/VisualEditor
+* oojs/ui",1391512362,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,What's keeping this from being addressed?,1391512133,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+VisualEditor:Math functions are getting overlapped with previous line,"Screenshot
+
+Steps to reproduce:
+
+1.Open the editor for a page
+2.Add a text or a link or a numbered list
+3.Copy a math formula from another VE
+4.Paste it into the next line after step 2
+5.Save the page
+
+Observed Result:
+The math formula is  getting merged with the previous element
+
+Please check :http://en.wikipedia.beta.wmflabs.org/wiki/Mathpaste20th
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12767}",1387576980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p7dsmh4gtfhvebckg5yk,task_description,declined
+VisualEditor:Math functions are getting overlapped with previous line,Not occurring anymore.Changing the status to Resolved-WorksforMe,1389047494,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p7dsmh4gtfhvebckg5yk,task_subcomment,NA
+VisualEditor:Math functions are getting overlapped with previous line,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.6
+OS:MAC OS X 10.8.5",1387577171,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p7dsmh4gtfhvebckg5yk,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Steps to reproduce:
+
+1.Open the editor
+2.Create a numbered list with 4 items.For example:
+# item 1
+# item 2
+# item 3
+# item 4
+
+3.Now place the cursor at the end of item 2 and press enter
+4.Add a new item 3( it gets added properly)
+5.Now place the cursor just before item 1 and press enter to move it to the next line 
+6.Type a new item1 in first line
+7.Delete the new item
+
+Observed Result:
+
+The order  (1.) does not get deleted.In read mode the list appears like this:
+ 
+ 1.
+ 2. item 1
+ 3. item 2
+ 4. new item 3
+ 5. new item 4
+ 6. item 3
+ 7. item 4 
+
+After saving, in read mode the list appears as follows:
+
+1.item 1
+2.item 2
+3.new item 3
+4.new item 4
+5.item 3
+6.item 4
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387567980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_description,declined
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"I think that this is ""expected"" behaviour (blank <li>s don't show in read mode, but do in wikitext and VE), confusingly.",1394504624,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Created attachment 14151
+In read mode
+
+**Attached**: {F12756}",1387568343,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Created attachment 14150
+In VE edit mode
+
+**Attached**: {F12755}",1387568299,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Created attachment 14149
+In edit source mode
+
+**Attached**: {F12754}",1387568252,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Test Environment:https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Another_page20th",1387568172,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","**Author:** `jhall`
+
+**Description:**
+When it is feeling uncooperative, SauceLabs will report test results like this from a Chrome/Linux test of some or other aspect of Visual Editor:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/222/testReport/(root)/VisualEditor%20general%20text%20markup%20features/VisualEditor_general_markup__outline_example_____Underline____u_This_is_a_new_line__u____/
+
+The browser response at the time of the failure was this helpful message:
+
+https://saucelabs.com/jobs/58b6d51fe48b4eaf845939c1f3d6de20/0005screenshot.png
+
+The Selenium log captured by SauceLabs reports:
+
+[22.414][FINE]:     Command received (/session/7a6fd70f2bc2c63555f62ec29cc9d507/element) with params {
+   ""using"": ""xpath"",
+   ""value"": "".//span[contains(concat(' ', @class, ' '), ' oo-ui-iconedElement-icon oo-ui-icon-text-style ')]""
+}
+
+[22.414][FINER]:    Waiting for all views to stop loading...
+[22.414][FINER]:    Done waiting for all views to stop loading
+[22.447][FINER]:    Waiting for all views to stop loading...
+[22.447][FINER]:    Done waiting for all views to stop loading
+[22.447][WARNING]:  Command finished (/session/7a6fd70f2bc2c63555f62ec29cc9d507/element) with response {
+   ""sessionId"": ""7a6fd70f2bc2c63555f62ec29cc9d507"",
+   ""status"": 7,
+   ""value"": {
+      ""message"": ""The element could not be found""
+   }
+}
+
+…while the Sauce Log records several HTTP 500 conditions similar to this (I will attach the complete Sauce Log to this bug):
+
+    {
+        ""HTTPStatus"": 500, 
+        ""between_commands"": 0.0773019790649414, 
+        ""duration"": 0.036900997161865234, 
+        ""in_video_timeline"": 19.80928897857666, 
+        ""method"": ""POST"", 
+        ""path"": ""element"", 
+        ""request"": {
+            ""using"": ""xpath"", 
+            ""value"": "".//span[contains(concat(' ', @class, ' '), ' oo-ui-iconedElement-icon oo-ui-icon-text-style ')]""
+        }, 
+        ""result"": {
+            ""message"": ""The element could not be found""
+        }, 
+        ""screenshot"": null, 
+        ""statusCode"": 7
+    },
+
+Need to investigate and figure out what is going on here...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387566480,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oypbzk3jpzff5cgsiva7,task_description,invalid
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","**jhall** wrote:
+
+Changing bug status since task in still WIP.",1388083932,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oypbzk3jpzff5cgsiva7,task_subcomment,NA
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","Change 103058 abandoned by Jhall:
+[Browser test] WIP Add session teardown steps
+
+Reason:
+Abandoning this change after a pairing session with Chris McMahon, since we settled on change #103566 as a better solution for the root problem.
+
+https://gerrit.wikimedia.org/r/103058",1387907723,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oypbzk3jpzff5cgsiva7,task_subcomment,NA
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","Change 103058 had a related patch set uploaded by Jhall:
+[Browser test] Add session teardowns steps
+
+https://gerrit.wikimedia.org/r/103058",1387580211,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oypbzk3jpzff5cgsiva7,task_subcomment,NA
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","**jhall** wrote:
+
+Complete Sauce Log
+
+**Attached**: {F12749}",1387566540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oypbzk3jpzff5cgsiva7,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"On fr.wp,
+NemesisIII usually copy/pastes titles of articles in the reference dialog.
+This led to this diff, https://fr.wikipedia.org/w/index.php?title=France_Roche&diff=prev&oldid=99244364, where the newly added link is among equal signs, as if its style was ""Page title"" rather than ""Paragraph"".
+
+When I tried to replicate this behavior,
+I got a slightly different result https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve&diff=99382715&oldid=99382337.
+Reference #2 is now... definitely different from the others (waaay bigger), and certainly not standard as it should be.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387465680,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_description,resolved
+VisualEditor: Reference dialog retains style of copy/pasted contents,"I've [[https://fr.wikipedia.org/w/index.php?title=Utilisateur%3ANeil_P._Quinn-WMF%2FTestcase%2FT60689&diff=114195603&oldid=114195075|tested this]] again using headlines from three different news sites, and the reference dialog now seems to correctly strip all rich formatting. Closing.",1429553616,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"I've [[https://fr.wikipedia.org/w/index.php?title=Utilisateur%3ANeil_P._Quinn-WMF%2FTestcase%2FT60689&diff=114195603&oldid=114195075|tested this]] again using headlines from three different news sites, and the reference dialog seems to correctly strip all rich formatting. Closing.",1429553604,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"NicoV, this bug is entirely about the reference dialog, so what you should do for refs is the only thing that we're talking about here.  So if ""manuals of style usually say that external links should not be in the text of the article, but as references"", then we SHOULD retain these links in the refs.",1392400957,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"Problem with this is and other design decisions in VE is that the exception is privileged over the most common situation.
+
+In most cases, you really don't want the formatting to be copied over like that when you're copying something from an external website:
+* italic, bold: probably ok
+* links: probably usually ok (and this is not really true, because manuals of style usually say that external links should not be in the text of the article, but as references or in an ""external links"" section)
+* everything else: usually not ok (I would say 99%), and even when it seems ok, it's not really a good idea. Why? Take the example of a different language: the notion should be kept in the end, but all wikis I know have defined a {{lang}} template to do that and discourage the use of <span lang=""xxx"">. And this is true for many things: even the links/italics/bold for a reference are usually handled by a template like {{cite web}} to have a consistent look&feel in wikipedia.
+
+Copying from an other page of wikipedia is an other subject: for this, copying the full wikimarkup would be usually good.",1392397248,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"There are good reasons to retain basic character formatting (e.g., italics) and linked URLs (e.g., the equivalent of [http://my.source.org Reliable Title]).  
+
+I suppose that font might be useful, if it has the effect of switching to a different language.  I'm just not sure that we'll encounter that.  <span lang=""jv-java""> of course should not get dropped, and LTR/RTL switches are critical.  Imagine a ref including both Arabic and a European language without this feature.",1392396305,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"(In reply to NicoV from comment #3)
+Precisely.",1392383608,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"I think keeping the formatting of a non-wiki contents is not really a good thing: every wiki has its own manual of style, to have a consistent look and feel in articles. There's almost no chance at all that a non-wiki contents will be formatted following the manual of style of the wiki.
+There's seldom use to keep font family, font size, color, ... from an external contents.",1392380611,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"I'm pretty sure it's working as intended, but I am not sure if it's helpful that it allows changing style to text (given it's a reference), and if there's a way to prevent that, because changing style to the single reference when you add it is not possible now.",1387482271,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"This may be a case of 'working as designed':  Rich copying and pasting means that the style of the copied/pasted contents is retained.  This is a new feature, so users are surprised by this.  We don't want to break formatting for references:  titles should remain italicized, journal volumes should remain bolded, etc.  However, perhaps it would be possible to set the contents of all refs to ""Paragraph""?",1387481601,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,"Steps to reproduce:
+
+1.Open the editor
+2.Add a Hieroglyphic
+3.When the cursor moves to the next line , add a heading and save the page
+
+Observed Result:
+The heading bar appears above the hiero where as the section edit options appear where the text of heading appears.The text styling for the heading changes to paragraph format.
+
+The wikitext resulting from these actions is:
+== <hiero>A
+</hiero>heading following hiero ==
+
+Found in:http://en.wikipedia.beta.wmflabs.org/wiki/Nonexist
+Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387400760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s6y4w7kahlei5ddylfmn,task_description,resolved
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,I can't reproduce this on Firefox 70.0b5 or Chrome 76.0.3809.132 on macOS 10.14.6.,1568144619,PHID-USER-cbjanejnwkkrbnj77d2d,PHID-TASK-s6y4w7kahlei5ddylfmn,task_subcomment,NA
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,Is this still occurring?,1439321145,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s6y4w7kahlei5ddylfmn,task_subcomment,NA
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,After adding the heading the cursor jumps to the beginning of the text in the first line of the document,1387486595,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s6y4w7kahlei5ddylfmn,task_subcomment,NA
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,"Created attachment 14131
+screenshot
+
+**Attached**: {F12544}",1387400975,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s6y4w7kahlei5ddylfmn,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"Esperanto commonly uses some special characters.  The ""x-method"" of entering them (cx -> ĉ, gx -> ĝ, hx -> ĥ, jx -> ĵ, sx -> ŝ, ux -> ŭ (and the capital letters)) is already implemented in the Universal Language Selector and other MediaWiki software at https://doc.wikimedia.org/mediawiki-core/master/php/html/LanguageEo_8php_source.html launguages/classes/LanguageEO.php  
+
+VisualEditor should support the same method.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1387394340,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-y5w7khnzvllsehcslsmd,task_description,resolved
+VisualEditor:  Support x-method of entering special characters for Esperanto,"This is a duplicate of bug 49569.
+
+*** This bug has been marked as a duplicate of bug 49569 ***",1389025443,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"Ok I've confirmed that the ULS IME *doesn't* seem to work in current VE deployment.
+
+(This has replaced, or should replace, the old save-time transform...)
+
+James, is there a general issue with ULS IMEs working/not working in VE? Have we run into this issue for other languages? What can we do to help it work? Do we have to adapt the IME to work in VE particularly? Or is there currently no way for any of the ULS IMEs to work?",1389022794,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"Now on eo.wiki does not work such post-save transformation, see https://eo.wikipedia.org/w/index.php?title=Uzanto:KuBOT/provejo&diff=5371450&oldid=5333431 (should appear ""eĥoŝanĝo ĉiuĵaŭde"" both in page and in the edit summary).
+
+If ULS IME stuff just work it would be great - even another transform methods for Esperanto, already included in ULS, would work.",1387995512,PHID-USER-mld2htwndnaw3bpuiot3,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,Shouldn't the existing ULS IME stuff just work? Or does every one require custom support in VE?,1387479234,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"(In reply to comment #1)
+> What is this method? How does it work? It looks just like a basic post-save
+> transform - if so, that should already work with VisualEditor…
+
+It's an input method in jquery.ime. https://github.com/wikimedia/jquery.ime/blob/master/rules/eo/eo-x.js",1387407128,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"What is this method? How does it work? It looks just like a basic post-save transform - if so, that should already work with VisualEditor…",1387400330,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+Italic text should not contain trailing spaces,"In VisualEditor, enter
+
+   one[space][Ctrl-I]two[space][Ctrl-I]three
+
+This will result in wiki text 
+
+   one ''two ''three
+
+but clearly
+
+   one ''two'' three
+
+was intended. I don't think a trailing (or leading?) space in italic/bold wikitext is ever appropriate.
+
+The fixed Bug 33108 is similar but deals with selected text.
+
+<editorial>
+I believe some of the hostility towards VE in the Wikipedia community results from issues like this: editors with long watchlists feel they have to clean up after many such VE edits.
+</editorial>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387321380,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-c3ineb5mdwoziw4jeqdo,task_description,resolved
+Italic text should not contain trailing spaces,"Merging with bug 52037.
+
+*** This bug has been marked as a duplicate of bug 52037 ***",1394501799,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c3ineb5mdwoziw4jeqdo,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","Right now we've a BetaFeatures component – https://bugzilla.wikimedia.org/buglist.cgi?component=BetaFeatures&product=MediaWiki%20extensions&list_id=259910 – but no single place to put bug reports about features that use BetaFeatures.
+
+Some of these have components of their own (e.g. MediaViewer) or even products (e.g. VisualEditor), but others don't (and probably won't).
+
+Right now, there's nowhere to raise a bug about e.g. Typography refresh that won't muddy up the bugs about BetaFeatures itself, as opposed to things that use it.
+
+Suggestions on better naming welcome. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387317120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_description,declined
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product",If features could provide preferred bug links that would be more useful.. Personally I just want to use talk pages for both of my features. I ignore the VectorBeta component. With respect to typography it's just not stable enough to warrant bugzilla bugs.,1387386327,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","The primary organization structure of Bugzilla is products and components which are mostly based on code repositories or code areas.
+
+(In reply to comment #6)
+> 1) People should not be expected to know from which extension beta features
+> come from so in the current scenario various bugs will be filed incorrectly.
+
+I'm happy to edit the BetaFeatures component description in Bugzilla to link to a wikipage that explains which beta feature is called how. https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures has links to ""Information"" and ""Discussion"" so you're free to add a link to corresponding Bugzilla components on the Information page. Or using the Bugzilla parameter of the {{Extension}} template.
+
+> Now I am seeing a flood of bugs filed under mobile from problems experienced
+> in the Beta Features environment field.
+
+Example bugs welcome so I can investigate plus if there are patterns I should improve documentation.",1387385235,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","Please reconsider or at least rethink the problem as there is a real problem here in my opinion.
+
+From my perspective:
+1) People should not be expected to know from which extension beta features come from so in the current scenario various bugs will be filed incorrectly.
+2) Beta features don't always plan to graduate to stable so are lower priority then the extensions that house them. For example - nearby pages is part of MobileFrontend.
+The purpose of the experiment was to explore whether such a feature was useful in desktop. If it is, it will need MediaWiki UI and a massive rewrite before being pushed to desktop.
+
+Now I am seeing a flood of bugs filed under mobile from problems experienced in the Beta Features environment field. These tend to not be helpful as I'm aware the code has issues when run in desktop.
+
+I would like some way of keeping these bugs separate from what I see as real bugs. I am very close to wanting to kill this beta feature because of this noise as I feel the bugs are intruding on the mobile teams core work which would be a huge shame. Please dont make me do this...",1387382627,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","(In reply to comment #1)
+> All BetaFeatures are currently parts of some extension, so the bugs should
+> probably be filed in the extensions, no?
+
+Yes. If extensions are missing I should create them (bug 58616, bug 58617, etc).",1387331868,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","So… we should just throw them in ""General"" and hope they get worked on? Lovely. :-(",1387318880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","Yeah, agreed with MatmaRex, this seems mighty silly. If anything, it wouldn't go under the Extensions product, because you're talking about something that *isn't* an extension, it's either only part of one or some sort of weird core betafeature.",1387317365,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","(In reply to comment #0)
+> Right now, there's nowhere to raise a bug about e.g. Typography refresh that
+> won't muddy up the bugs about BetaFeatures itself, as opposed to things that
+> use it.
+
+Those should be filed against VectorBeta. Though, supposedly those styles are actually in core, so the bugs should be filed in core?
+
+(In reply to comment #1)
+> All BetaFeatures are currently parts of some extension, so the bugs should
+> probably be filed in the extensions, no?
+
+I agree.",1387317365,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","All BetaFeatures are currently parts of some extension, so the bugs should probably be filed in the extensions, no?",1387317239,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"VisualEditor: can't submit/press ""save page"" button using return key","When I tab through the various input controls and highlight the ""save page"" button in VisualEditor, I can't seem to use the return key to submit the form/press the button. I'll upload a screenshot momentarily.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387246920,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-h5arfbwysxbybm7hujkv,task_description,resolved
+"VisualEditor: can't submit/press ""save page"" button using return key","Up-merging to the upstream issue.
+
+*** This bug has been marked as a duplicate of bug 62337 ***",1396380391,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h5arfbwysxbybm7hujkv,task_subcomment,NA
+"VisualEditor: can't submit/press ""save page"" button using return key","Created attachment 14117
+VisualEditor on mediawiki.org with ""save page"" button highlighted, 2013-12-16
+
+**Attached**: {F12370}",1387247043,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-h5arfbwysxbybm7hujkv,task_subcomment,NA
+VisualEditor: copying and pasting header results in non-breaking space being inserted,"Input text ([[mw:VisualEditor:What A]]):
+
+---
+=== test ===
+what is '''this''' i don't ''even''
+---
+
+I copy and paste this text from [[mw:VisualEditor:What A]] to [[mw:VisualEditor:What B]] and I end up with largely the same result, except an invisible non-breaking space is inserted before ""test"". If you view the HTML page source of [[mw:VisualEditor:What B]], it's trivial to spot:
+
+---
+<span class=""mw-headline"" id="".C2.A0test"">&#160;test</span>
+---
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387246800,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ki5ndhcsugxw2thwlhd4,task_description,resolved
+"VisualEditor: link inspector appears next to page title, pointing to what is an uneditable area of the page","1. Go to a non-existent page and edit it with VE
+2. Click to the right of the article title
+3. Click the link icon on the toolbar
+
+The link inspector appears next to the page title, pointing to what is an uneditable area of the page.
+
+Link creation works correctly, despite the incorrect location of the inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1387190940,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-crf7s6bmhldwret6sy4u,task_description,resolved
+"VisualEditor: link inspector appears next to page title, pointing to what is an uneditable area of the page",Seems to work correctly now.,1398733687,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-crf7s6bmhldwret6sy4u,task_subcomment,NA
+Adding diatrics to letters in defaultsort causes VisualEditor to belive the page was not changed.,"I ran into an issue with VisualEditor, when I tried to replace an letter with an diatric letter in defaultsort. VisualEditor would not activate the ""Save page"" button, making me unable to save the change. Also, I noticed, that if I would add some random letters to the page, after the defaultsort change, VisualEditor would still not activate the ""Save page"" button.
+
+Here is one of three nearly indentical tests where I found this issue. The other two where to test whether the bug was reproducable.
+# Change [[:is:Flokkur:Stjórnmál í Sádí-Arabíu]]
+# Open the More settings panel, and choose Page settings.
+# Sort the page as ""Sádí-Arabíu"" (without the hyphens).
+# Click apply changes
+# Notice that the ""Save page"" button does not activate.
+
+Expected behaviour: Should allow me to save the page, when changing an letter to an diatric letter. Adding text afterwards definatly should allow me to save the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387060200,PHID-USER-zrsacwdcrbgp2u32d5pr,PHID-TASK-lcm5zsufp2kobbnnphbv,task_description,declined
+Adding diatrics to letters in defaultsort causes VisualEditor to belive the page was not changed.,"I can no longer reproduce this bug.
+
+Closed as worksforme.",1388782680,PHID-USER-zrsacwdcrbgp2u32d5pr,PHID-TASK-lcm5zsufp2kobbnnphbv,task_subcomment,NA
+"VisualEditor:  Cursor misplaced while editing.  I click here, and it types over there.","Intention:
+Copyedit a sentence.  I clicked after the word ""elbow"" to add another phrase.
+
+
+Actual Results:  
+It typed my words in the middle of a sentence four lines lower.  The diff was correct, but did not include several of the last changes I made (e.g., adding paragraph breaks).  Also, in cutting and pasting another paragraph, the ref's contents were removed.
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387058460,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yht56d7rk34lqhlubcge,task_description,resolved
+"VisualEditor:  Cursor misplaced while editing.  I click here, and it types over there.",Seems to [[https://en.wikipedia.org/w/index.php?title=User%3ANeil_P._Quinn-WMF%2FTestcase%2FT60493&diff=657353327&oldid=657353041|work correctly now]]. Closing.,1429551450,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-yht56d7rk34lqhlubcge,task_subcomment,NA
+"VisualEditor:  Cursor misplaced while editing.  I click here, and it types over there.",The diff (what ended up being saved) is at https://en.wikipedia.org/w/index.php?title=Diffuse_large_B-cell_lymphoma&diff=586098843&oldid=582235478,1387058957,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yht56d7rk34lqhlubcge,task_subcomment,NA
+"VisualEditor:  Cursor misplaced while editing.  I click here, and it types over there.","Created attachment 14098
+Screenshot of the article after encountering the problem, but before saving
+
+Four places are marked in the image:
+
+(1) I split the paragraph as shown here, but this line break did not get saved.
+
+(2) I clicked above the '2' and started typing after ""elbow"".  The next few words should have been ""or a surgically implanted port"".  The words ""or a sur"" were visible on the screen at the time I saved, but did not appear in the diff.
+
+(3) The highlighted (blue) spot is where VisualEditor tried to put part of these words.  I have just 'undone' the addition of the text in the wrong paragraph.
+
+(4) The first thing I did in this article was to cut text out of the ==Treatment== section and use it to create a separate ==Research== section.  Ref #30 turned into <sup>[30]</sup> when I did this.  In addition to losing the refs, it may have added line breaks; they do not appear in the original wikitext, but I had to remove several before saving.
+
+The number of lines in between where I clicked to type at (2) and where it tried to put the words at (3) is approximately the same number of lines as what was moved to (4).
+
+**Attached**: {F12250}",1387058914,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yht56d7rk34lqhlubcge,task_subcomment,NA
+"""Edit"" tab not change to ""View source"" with protected template subpage","""Edit"" tab not change to ""Vew source"" with protected template subpage, see https://commons.wikimedia.org/wiki/Template:Delete/layout
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://commons.wikimedia.org/wiki/Template:Delete/layout",1386959040,PHID-USER-b27lopawgf2h6utuuqyi,PHID-TASK-eo43z5xddf6sg3om7sem,task_description,resolved
+"""Edit"" tab not change to ""View source"" with protected template subpage","So this is actually a duplicate report of a different, much older one :)
+
+*** This bug has been marked as a duplicate of bug 11700 ***",1386959666,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eo43z5xddf6sg3om7sem,task_subcomment,NA
+"""Edit"" tab not change to ""View source"" with protected template subpage","Actually, that was too quick. This also affects core with VisualEditor disabled. Sorry.",1386959536,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eo43z5xddf6sg3om7sem,task_subcomment,NA
+"""Edit"" tab not change to ""View source"" with protected template subpage","
+
+*** This bug has been marked as a duplicate of bug 53893 ***",1386959355,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eo43z5xddf6sg3om7sem,task_subcomment,NA
+"VisualEditor: Copying a template from one page to another: render is correct, but template is gone.","Let's copy the relatively simple {{irc}} template from 
+
+https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-12-04
+
+to
+
+https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-12-18
+
+1. Open both pages in Edit mode.
+
+2. Copy ""#wikimedia-meetbotconnect"" from one page and paste it in the other.
+
+EXPECTED
+
+The template is copied as i to the destination page.
+
+ACTUALLY
+
+If selecting only the text generated by the template, Ctrl-C seems to be not enough. Ctrl-V in the other page will still paste whatever you hadd in your clipboard before.
+
+If selecting the text of the template plus some extra text, then Ctrl-C does copy something, and Ctrl-V does paste a visually equivalent text.
+
+However, when checking the wikitext source of the page one can see that the original template has been rendered as HTML.
+
+See https://www.mediawiki.org/w/index.php?title=Architecture_meetings%2FRFC_review_2013-12-18&diff=841813&oldid=838192
+
+If this is part of a secret, long-term Parsoid plan to convert all template instances to HTML, fine. However, if this is not the intended behavior...  ;)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386889980,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-zdphbo6gq23bo6llwwdp,task_description,declined
+"VisualEditor: Copying a template from one page to another: render is correct, but template is gone.",I can no longer reproduce this in Firefox.  It's been months since the last time I remember seeing this.,1415246826,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zdphbo6gq23bo6llwwdp,task_subcomment,NA
+"VisualEditor: Copying a template from one page to another: render is correct, but template is gone.",Can't reproduce this issue...,1414868700,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-zdphbo6gq23bo6llwwdp,task_subcomment,NA
+"VisualEditor: Copying a template from one page to another: render is correct, but template is gone.","https://en.wikipedia.org/w/index.php?title=User:Edgepedia/VE/S%26D&diff=588724142&oldid=588539903 (Command-F to search for ""Commons"") shows the same kind of problem, except that the result doesn't look right.  The image is missing, the box is missing, and the text is on the left rather than on the right.  The appendices are duplicated in that diff, so you can see both what's wrong (the first set of ==External links==) and what it ought to do (the very bottom of the page).",1389226703,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zdphbo6gq23bo6llwwdp,task_subcomment,NA
+browsertests: triggers for Flow,"The browser tests for Flow should be triggered by Gerrit just like it
+is already the case for ULS (bug 52120) or going to be for VisualEditor (bug 53691).
+
+The tests need to be carefully filtered out since they are expecting content or
+behavior which are not to be found on a freshly installed wiki.
+
+CC QA
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1386869640,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-omucxcdp6ujh4xt2zaue,task_description,declined
+browsertests: triggers for Flow,We are not going to trigger browser tests on patch submission for now.  It is not that trivial to setup.,1408458857,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,Resetting ticket status as patch was merged,1398408670,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,Nice! I retriggered the job and it took screenshots for the failures: https://integration.wikimedia.org/ci/job/mwext-browsertests-Flow-phantomjs/6/,1394028087,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"As far as I can see[1], Flow is now using mediawiki_selenium 0.2.7, so screen shots should be taken.
+
+1: https://github.com/wikimedia/mediawiki-extensions-Flow/blob/master/tests/browser/Gemfile.lock#L25",1394023970,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"Antoine, do you still need help with this?",1394023662,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,( and one can trigger a run manually using the lame tutorial at https://www.mediawiki.org/wiki/Continuous_integration/Tutorials/Trigger_a_job_manually ),1393868310,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"I got Cirrus Search tests working with Nik and I am close to finish the integration of the VisualEditor tests.
+
+I triggered a run of the Flow browsertests this morning and they are failing: https://integration.wikimedia.org/ci/job/mwext-browsertests-Flow-phantomjs/5/ I havent investigated though.
+
+Cucumber HTML report is https://integration.wikimedia.org/ci/job/mwext-browsertests-Flow-phantomjs/5/artifact/log/report.html
+
+
+The screenshots are not taken because the repository uses mediawiki_selenium (0.2.2), should use 0.2.3 to let us specify the screenshot destination.",1393868264,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"Change 112874 merged by jenkins-bot:
+Tag browser tests with @clean
+
+https://gerrit.wikimedia.org/r/112874",1392402237,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"Change 112874 had a related patch set uploaded by Hashar:
+Tag browser tests with @clean
+
+https://gerrit.wikimedia.org/r/112874",1392204282,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,*** Bug 61219 has been marked as a duplicate of this bug. ***,1392204148,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"**Author:** `littlesandra88`
+
+**Description:**
+For private wiki's that requires login
+
+$wgGroupPermissions['*']['createaccount'] = false;
+$wgGroupPermissions['*']['edit'] = false;
+$wgGroupPermissions['*']['read'] = false;
+
+I get this from nodejs
+
+Stack trace: AccessDeniedError: Your wiki requires a logged-in account to access the API.
+
+when I do
+
+lynx  http://localhost:8000/localhost/x
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386867540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_description,declined
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"Yes, that should work unless things have changed in VE land in the meantime.",1397865528,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"**littlesandra88** wrote:
+
+Very interesting. I would like to try that.
+
+Based on https://www.mediawiki.org/wiki/Talk:Parsoid#More_private_wiki_trouble would it be correct that all I have to do is adding
+
+$wgVisualEditorParsoidPrefix = 'localhost'; 
+$wgVisualEditorParsoidForwardCookies = true;
+
+and then it should work?",1397859889,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"Parsoid forwards cookies to the API and disables caching if a cookie is set. The VisualEditor extension for example supports forwarding cookies to Parsoid for private wikis, see their settings.
+
+Parsoid should not have access to sensitive information like passwords. In the longer term we'll probably add support for time-limited signed token forwarding once MediaWiki in general gains support for that.",1397847902,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"**littlesandra88** wrote:
+
+If your wiki requires login, then the wiki api.php page, which parsoid needs, also requires login. There is no way to specify a username+password to parsoid so it can access this page. That is what you see in the error message.
+
+To fix this, I guess a dummy account have to be made in MediaWiki, and then the username+password needs to be entered somewhere in parsoid config files.",1392763486,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"The behavior looks correct to me.
+
+Can you be more specific about where you see a problem here?",1392750973,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+VisualEditor: Copying a section throws undefined error,"Safari 7:
+
+https://www.mediawiki.org/wiki/Communication?veaction=edit
+
+Copy from under H1, including template up to just before the Chat header. I get:
+[Error] TypeError: 'undefined' is not an object (evaluating 'delete children[i].values[attribute]')
+	removeAttributeRecursive (load.php, line 20)
+	removeAttributeRecursive (load.php, line 20)
+	removeAttributeRecursive (load.php, line 20)
+	removeAttributeRecursive (load.php, line 20)
+	removeHtmlAttribute (load.php, line 20)
+	getClonedElement (load.php, line 202)
+	cloneElements (load.php, line 170)
+	onCopy (load.php, line 292)
+	proxy (load.php, line 10)
+	dispatch (load.php, line 45)
+	eventHandle (load.php, line 38)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386842820,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-hqe3vfy7ixkkhkavdrmm,task_description,declined
+VisualEditor: Copying a section throws undefined error,This appears to now work for me; sorry for the epically slow triage.,1414452147,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hqe3vfy7ixkkhkavdrmm,task_subcomment,NA
+VisualEditor: Pasting a template throws undefined getModel error,"[Error] TypeError: 'undefined' is not an object (evaluating '$node.data('view').getModel')
+	getOffsetFromTextNode (load.php, line 244)
+	getOffset (load.php, line 244)
+	getRange (load.php, line 248)
+	pollOnceInternal (load.php, line 319)
+	pollOnce (load.php, line 319)
+	documentOnBlur (load.php, line 287)
+	proxy (load.php, line 10)
+	focus
+	afterPaste (load.php, line 299)
+	(anonymous function) (load.php, line 294)
+	proxy (load.php, line 10)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386842700,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-kfrktikcnijejv2ssua3,task_description,resolved
+VisualEditor: Pasting a template throws undefined getModel error,"Does this bug mean ""you can copy stuff, but nothing happens when you try to paste it""?",1426706269,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kfrktikcnijejv2ssua3,task_subcomment,NA
+VisualEditor: Pasting a template throws undefined getModel error,"I haven't seen this problem for a long time, so we should probably close it.",1424377866,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-kfrktikcnijejv2ssua3,task_subcomment,NA
+VisualEditor: Pasting a template throws undefined getModel error,"I can't reproduce this now (Mac OS X 10.9 / Safari 7.0.2) – can you, or should we mark as WORKSFORME?",1394222678,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kfrktikcnijejv2ssua3,task_subcomment,NA
+VisualEditor: Pasting a template throws undefined getModel error,"I have trouble reproducing this one, but I think it sometimes happens if you delete something in a surface and then try to copy something else in that surface. Or if you select a block in the destination and then do a paste replace.
+
+Safari 7",1386842818,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-kfrktikcnijejv2ssua3,task_subcomment,NA
+VisualEditor: undefined error during copy,"I selected all VE content from: ""It is important to make"", up to ""Mediawiki-l mailinglist thread ""mysql5 binary schema"" 25.03.2009""
+
+I could pinpoint it to trying to copying the Header ""scripts"" and the warning template that follows it.
+
+[Error] TypeError: 'undefined' is not an object (evaluating 'delete children[i].values[attribute]')
+	removeAttributeRecursive (load.php, line 20)
+	removeAttributeRecursive (load.php, line 20)
+	removeHtmlAttribute (load.php, line 20)
+	getClonedElement (load.php, line 202)
+	cloneElements (load.php, line 170)
+	onCopy (load.php, line 292)
+	proxy (load.php, line 10)
+	dispatch (load.php, line 45)
+	eventHandle (load.php, line 38)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki?veaction=edit",1386840240,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-37pnzuvt2mm7zi2opamc,task_description,resolved
+VisualEditor: undefined error during copy,"Can't reproduce any more. We did a lot of changes to Select-All in the intervening period, which probably fixed it.",1428526886,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-37pnzuvt2mm7zi2opamc,task_subcomment,NA
+VisualEditor: undefined error during copy,"On Safari 7 btw:
+
+I have a slight suspicion thrown Undefined errors like these during copy might also be responsible for the broken internal links that are pasted: [[https://www.mediawiki.org/wiki/Manual:Restoring_a_wiki_from_backup|Manual:Restoring a wiki from backup]]",1386840770,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-37pnzuvt2mm7zi2opamc,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,"screenshot
+
+Steps to reproduce:
+
+1.Open the editor
+2.Insert an image
+
+Observed Result:
+An error appears:
+Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function api.php:1
+
+see the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11996}",1386807960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n7jievcoinoyg7mcltce,task_description,resolved
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,"This is actually still happening. It is a race condition that we can't do anything about and isn't actually affecting anything. It's just a weird warning that jQuery's callback system emits due to <script> limitations.
+
+See bug 59604 for more information.
+
+*** This bug has been marked as a duplicate of bug 59604 ***",1406740632,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,Not happening anymore on betalabs with Chrome and FF with MAC OS X 10.8.5,1388777702,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,This is again happening and the image inserted us appearing as a file link.See the screenshot attached.,1388689872,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,"Created attachment 14215
+Screenshot
+
+**Attached**: {F11997}",1388689847,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Pagelink11thdecember?veaction=edit",1386808174,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+"Investigate ""Selenium::WebDriver::Error::WebDriverError"" issues with Chrome via SauceLabs","**Author:** `jhall`
+
+**Description:**
+This seems to be happening somewhat regularly with Visual Editor jobs run in the ""Linux Firefox"" environment via CloudBees SauceLabs:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/203/testReport/(root)/VisualEditor%20Indent,%20Outdent/check_indent_and_outdent_enable_and_disable__outline_example_____Bullets___enabled___disabled___/
+
+Error message reported from SauceLabs is:
+
+unexpected response, code=404, content-type=""text/plain""
+ERROR Job 68d1926e89f24b24a35272766e190eb5 is not in progress. It may have recently finished, or experienced an error. You can learn more at https://saucelabs.com/jobs/68d1926e89f24b24a35272766e190eb5 (Selenium::WebDriver::Error::WebDriverError)
+./features/step_definitions/bullets_steps.rb:34:in `/^I click Bullets$/'
+features/indent_outdent.feature:11:in `When I click <control>'
+
+Looking at the Selenium log captured via SauceLabs, we may discover:
+
+[22.744][FINER]: Waiting for all views to stop loading...
+559[22.745][FINER]: Done waiting for all views to stop loading
+560[23.567][FINER]: Waiting for all views to stop loading...
+561[23.625][FINER]: Done waiting for all views to stop loading
+562[23.625][WARNING]: AfterExecuteCommand failed: Chrome did not respond to 'WaitForAllTabsToStopLoading'. Elapsed time was 57 ms.
+563[23.625][FINE]: Command finished (/session/78a6e87ee7f7d38f694da3813857645f/url) with response {
+564 ""sessionId"": ""78a6e87ee7f7d38f694da3813857645f"",
+565 ""status"": 0,
+566 ""value"": {
+567
+568 }
+569}
+
+The same test runs without errors on a local Linux machine with Firefox.  From the Selenium log on SauceLabs, we discover the following configuration info:
+
+43[3.622][FINE]: Command received (/session/78a6e87ee7f7d38f694da3813857645f)
+44[3.622][FINE]: Command finished (/session/78a6e87ee7f7d38f694da3813857645f) with response {
+45 ""sessionId"": ""78a6e87ee7f7d38f694da3813857645f"",
+46 ""status"": 0,
+47 ""value"": {
+48 ""acceptSslCerts"": false,
+49 ""applicationCacheEnabled"": false,
+50 ""browserConnectionEnabled"": false,
+51 ""browserName"": ""chrome"",
+52 ""chrome.chromedriverVersion"": ""26.0.1383.0"",
+53 ""cssSelectorsEnabled"": true,
+54 ""databaseEnabled"": false,
+55 ""handlesAlerts"": true,
+56 ""javascriptEnabled"": true,
+57 ""locationContextEnabled"": false,
+58 ""nativeEvents"": true,
+59 ""platform"": ""linux"",
+60 ""rotatable"": false,
+61 ""takesScreenshot"": true,
+62 ""version"": ""28.0.1500.95"",
+63 ""webStorageEnabled"": true
+64 }
+65}
+
+The 'WaitForAllTabsToStopLoading' issue seems to be a long-resolved issue with chromedriver (see http://code.google.com/p/selenium/issues/detail?id=2996), so why is this still happening when these test run via CloudBees/SauceLabs?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386807660,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dujs2kys4ubjpcmrausf,task_description,resolved
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"Bug 41193 VisualEditor: Support copy and paste from other VE instances (surfaces) is now closed as FIXED yet a fully working cut and paste is not.
+Some of the bits of copy and paste still not working are documented at http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=585650020&oldid=585645740
+
+#External links? {{Tick}} This seems usually to work (not completely the same, but near enough). Mind you, external links in templates go completely haywire though... 
+#Internal links? {{Cross}} I took one line from [https://www.mediawiki.org/wiki/Manual:FAQ?veaction=edit FAQ], ""where do I donwload MediaWiki?"". One single line, that's all. [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840546] Most other examples below contain further cases of internal links gone wrong
+#References? {{Cross}} I tried to copy [https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki?veaction=edit] (the whole page), to get a page with a reference (not common on Mediawiki). The result is baffling but amusing[https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840568]. If you go to the reference at the bottom of that page, and click the ""arrow"" at the left (taking you up to the place in the same page where that reference is used, no?) then suddenly you end at the original page, in VE edit mode! 
+#List bullets? {{Cross}} [https://www.mediawiki.org/wiki/Files_and_licenses_concept?veaction=edit], section Display, gives [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840576] Note how multiple lines from the original are squashed together in the copy
+#Images? {{Cross}} I found an image in [https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design?veaction=edit], section Code, Status: but the result [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840580] has no image, as part of the syntax is lacking...
+#Templates? {{Cross}} I tried copying the template from [https://www.mediawiki.org/wiki/Communication?veaction=edit here, on the right]: the result is [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840544]. Something simpler? <nowiki>{{Note}}</nowiki> changes into <nowiki><span class=""""><span class=""""></span></span><span class=""""> </span>'''Note'''<span class="""">:</span></nowiki> [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840555]
+#Tables? {{Cross}} Taken from [https://www.mediawiki.org/wiki/Manual:Code?veaction=edit], but the result is not quite the same [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840555], not the contents (yuk) nor the layout. 
+#Code? {{Cross}} I tried to copy the code from [https://www.mediawiki.org/wiki/Manual:FAQ?veaction=edit FAQ], section ""How do I add extra namespaces?"", but the result [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840549] is not quite the same as the original, and looking at the actual code underneath makes this even more obvious
+#Further bugs? {{Cross}}, e.g. the sudden appearance of (actually quite nice) clouds as section headers[https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840559]
+#Further bugs part 2? {{Cross}} But extremely funny! No idea what happened here, but I tried to copy a section from [https://www.mediawiki.org/wiki/Download?veaction=edit], section ""Development releases"", and nothing more. The amazing result, starting from an empty page, is [https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=840564&oldid=840563]. Don't ask me where that template at the bottom left comes from, I didn't ask for it!
+#Further bugs part 3? {{Cross}}, again funny, perhaps the same as the one above: From [https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design?veaction=edit] I copy the short sentence <nowiki>see the {{git file|project=mediawiki/core|file=resources/mediawiki.ui/sourcefiles|sourcefiles}} subdirectory.</nowiki> (shown here in wikitext format, but everything here is copied using VE only!), which looks originally like ""see the resources/mediawiki.ui/sourcefiles subdirectory"". The end result of this one sentence? [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840587] Don't you love it? 
+#Further bugs part 4? {{Cross}} If I want to copy [https://www.mediawiki.org/wiki/Flow_Portal/Design/FAQ?veaction=edit Flow Portal/Design/FAQ], I can't. I can't paste it into my sandbox, and if I paste it in multiple parts, I can't save it (the save button doesn't work).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386801180,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-z5fquxt3pmfidowhr5a7,task_description,invalid
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"Derk-Jan Hartman has responded on wiki http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=585724128&oldid=585724057
+so it looks like some of the work of splitting has been done.
+
+2. I suspect this might be caused by JS errors being thrown because of a copy action on the originating surface. All following copy actions from the source surface (even small ones) might then become corrupted I suspect. bug 58379
+3. Probably the same problem as 2
+4. I was not able to reproduce this: [28]
+5. I was not able to reproduce this: [29]
+6. I was not fully able to reproduce this, but there seems to be in issue in the paragraph following the template. bug 58384
+7. This seems to be because this table also doesn't render properly in the original surface to begin with. bug 58387
+8. I was not able to reproduce this [30], but again, if 2. occurred in the original source surface before your action, then this might cause that I guess. Also it seems that the syntax highlight classes are not dynamically loaded when you paste this content into the target. I reported this as bug 58388
+9. Clouds seem to be the result of pasting something over existing content. bug 58389
+10. not able to reproduce this yet.",1386850954,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-z5fquxt3pmfidowhr5a7,task_subcomment,NA
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"SO to recap: Filing issues is definitely welcome (though only one problem per report), and if I have enough time later today I might try to split this into separate reports. It's not that bug reports aren't welcome, it's that they need to be one issue per report (which is more work for reporters, I know :-/  ).",1386849413,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-z5fquxt3pmfidowhr5a7,task_subcomment,NA
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"Sorry, but this bug report is not handable so I am closing it as INVALID (which does not refer to the bugs you mention, but to this report itself). 
+Please see https://www.mediawiki.org/wiki/How_to_report_a_bug",1386839759,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-z5fquxt3pmfidowhr5a7,task_subcomment,NA
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"Please re-submit this as individual bugs, as you have been asked before. As it is, it's unactionable.",1386801304,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z5fquxt3pmfidowhr5a7,task_subcomment,NA
+VisualEditor:Newline cannot be entered after copy pasting a text from another VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open the editor
+2.Copy a text or a link 
+3.Paste it into another VE
+4.Press enter
+
+Observed Result:
+Newline cannot be entered in the other VE where the text was pasted into .
+
+It is giving an error :
+
+Resource interpreted as Font but transferred with MIME type application/font-woff: ""http://bits.beta.wmflabs.org/static-master/extensions/UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.woff?version=20131205"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12813}",1386797160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-l6tkqmvanqkkeexo642z,task_description,declined
+VisualEditor:Newline cannot be entered after copy pasting a text from another VE,"I cant reproduce this one either now .I think it got fixed somehow because now the cursor is moving to the next line automatically, after pasting a text into another VE.",1386962329,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-l6tkqmvanqkkeexo642z,task_subcomment,NA
+VisualEditor:Newline cannot be entered after copy pasting a text from another VE,The error you're showing looks like an unrelated warning. I can't reproduce the newline bug either.,1386931658,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-l6tkqmvanqkkeexo642z,task_subcomment,NA
+VisualEditor:Newline cannot be entered after copy pasting a text from another VE,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=11th_december&veaction=edit",1386797349,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-l6tkqmvanqkkeexo642z,task_subcomment,NA
+Fatal exception of type MWException,"**Author:** `littlesandra88`
+
+**Description:**
+After having upgraded from mw1.19 til mw1.22 I
+
+cd extensions
+git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git
+
+and added
+
+require_once ""$IP/extensions/VisualEditor/VisualEditor.php"";
+$wgDefaultUserOptions['visualeditor-enable'] = 1;
+$wgHiddenPrefs[] = 'visualeditor-enable';
+
+to LocalSettings.php as described at
+
+http://www.mediawiki.org/wiki/Extension:VisualEditor
+
+When I visit the wiki I get in the browser
+
+[da26e58f] 2013-12-11 13:28:05: Fatal exception of type MWException
+
+Using CentOS6 64bit
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal",1386769680,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_description,invalid
+Fatal exception of type MWException,"As that's support, could you please raise this in https://www.mediawiki.org/wiki/Project:Support_desk ? Thanks for your understanding!",1386777909,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"**littlesandra88** wrote:
+
+I would prefer to stay at mw1.22 and use an older visual editor, but finding the last git commit that broke mw1.22 is probably not easy.
+
+When I look at the git snapshots I don't see anything in the extensions/.
+
+Can you explain what I have to do to get all the files that makes up a full mw?",1386777827,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"So yeah, VisualEditor is rather experimental and needs non-released versions to work. You can download either 1.23alpha (aka git master) via git or at https://toolserver.org/~krinkle/mwSnapshots/snapshots/mediawiki-core/mediawiki-latest.tar.gz , or the wmf/1.23wmf2 branch (or some other wmf branch greater than 1.23wmf2) via git. These are of course experimental versions of MediaWiki, so it may not be as stable.
+
+You could also try downloading an earlier version of VisualEditor, if one is available.
+
+---
+
+Closing bug as INVALID since this isn't really a MW bug.",1386776520,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"**littlesandra88** wrote:
+
+Very useful variable =)
+
+Does the following make sense?
+
+[df264ef0] / Exception from line 3078 of /var/www/mediawiki-1.22.0/includes/GlobalFunctions.php: MediaWiki 1.23wmf2 required--this is only 1.22.0
+
+Backtrace:
+
+#0 /var/www/mediawiki-1.22.0/extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW(string)
+#1 [internal function]: VisualEditorHooks::onSetup()
+#2 /var/www/mediawiki-1.22.0/includes/Setup.php(592): call_user_func(string)
+#3 /var/www/mediawiki-1.22.0/includes/WebStart.php(153): require_once(string)
+#4 /var/www/mediawiki-1.22.0/index.php(46): require(string)
+#5 {main}",1386776241,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"(In reply to comment #2)
+> to LocalSettings.php. Should I do more?
+
+$wgShowExceptionDetails",1386775580,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"**littlesandra88** wrote:
+
+Hmmm. Do you know which commit that broke mw1.22 comparability? Because then I could just ""git checkout"" that version.
+
+I don't see any extra debug info in the browser of httpd log by adding
+
+error_reporting( -1 );
+ini_set( 'display_errors', 1 );
+
+to LocalSettings.php. Should I do more?",1386772600,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"(In reply to comment #0)
+> After having upgraded from mw1.19 til mw1.22 I
+> cd extensions
+> git clone
+> https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git
+
+So you cloned git master of VisualEditor?
+
+VisualEditor git master requires MW 1.23 - see https://www.mediawiki.org/wiki/Extension:VisualEditor
+
+> [da26e58f] 2013-12-11 13:28:05: Fatal exception of type MWException
+
+See https://www.mediawiki.org/wiki/Manual:How_to_debug",1386771546,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Visual Editor UI should display MediaWiki:Edittools,"**Author:** `William915`
+
+**Description:**
+For Cantonese Wikipedia, MediaWiki:edittools is quite a useful tool to insert special characters used solely in Cantonese and not in Mandarin. It would be really helpful if it is shown in the interface of VisualEditor as well. I am not sure whether other wikis have similar requests for this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1386760620,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ecndqfmm5tbhzjqkbox5,task_description,resolved
+Visual Editor UI should display MediaWiki:Edittools,"I think that this should be merged into bug 38029, though there are issues there (which I'll comment on).
+
+*** This bug has been marked as a duplicate of bug 38029 ***",1387220238,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ecndqfmm5tbhzjqkbox5,task_subcomment,NA
+Visual Editor UI should display MediaWiki:Edittools,"This relates to bug 50296 (which implements an alternative to MediaWiki:edittools) which is fixed, but not yet deployed. And slightly to bug 38029, because the new implementation does not actually reuse those same characters.",1386767275,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ecndqfmm5tbhzjqkbox5,task_subcomment,NA
+Visual Editor UI should display MediaWiki:Edittools,"This is about https://zh-yue.wikipedia.org/wiki/MediaWiki:Edittools ?
+
+So I enabled 即見編輯 (Visual Editor) on https://zh-yue.wikipedia.org/wiki/Special:%E5%96%9C%E5%A5%BD%E8%A8%AD%E5%AE%9A#mw-prefsection-betafeatures .
+
+But comparing VE (編輯) and classical editing (改原碼) I'd love to know *where* you would display MediaWiki:edittools because there is no textfield anymore?",1386766352,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ecndqfmm5tbhzjqkbox5,task_subcomment,NA
+VisualEditor:Error contacting parsoid server error occurring while saving a page on betalabs,"Screenshot of the error
+
+Error contacting parsoid server error occurring while saving or editing a page on betalabs
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12611}",1386625380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-72io3l35lrubzg5lhtmy,task_description,declined
+VisualEditor:Error contacting parsoid server error occurring while saving a page on betalabs,This was probably a Beta Labs configuration/load issue; closing.,1395881797,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-72io3l35lrubzg5lhtmy,task_subcomment,NA
+VisualEditor:Error contacting parsoid server error occurring while saving a page on betalabs,"Getting error ""Error loading data from server: parsoidserver-http-bad-status: 503. Would you like to retry?""
+
+after clicking on Edit beta on this page:
+http://en.wikipedia.beta.wmflabs.org/wiki/Paste",1386625771,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-72io3l35lrubzg5lhtmy,task_subcomment,NA
+VisualEditor:Error contacting parsoid server error occurring while saving a page on betalabs,"Created attachment 14040
+Screenshot of the error
+
+**Attached**: {F12612}",1386625448,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-72io3l35lrubzg5lhtmy,task_subcomment,NA
+"VisualEditor:""Apply changes""  on the transclusion dialog box and ""Save Page"" button on the page remains active even though there is no change on the transclusion dialog box","Screenshot of the error
+
+Steps to reproduce:
+
+1.Open the Editor.
+2.Open the transclusion dialog.
+3.Click on the trash icon on the right
+4.Click on ""Apply Changes""
+5.Click on Save Pages
+6.Click on ""Review your changes""
+
+Observed Result:
+
+Although there is no change in the template dialog box, the ""Apply changes"" button in the transclusion dialog box remains active.
+After clicking on ""Review your changes"" it says: 
+""Could not start the review because your revision matches the latest version of this page""
+
+See the scrrenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12587}",1386618540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fsd7k5bgeeg76dzbdwqt,task_description,resolved
+"VisualEditor:""Apply changes""  on the transclusion dialog box and ""Save Page"" button on the page remains active even though there is no change on the transclusion dialog box","Merging into 55976.
+
+*** This bug has been marked as a duplicate of bug 55976 ***",1416357284,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsd7k5bgeeg76dzbdwqt,task_subcomment,NA
+"VisualEditor:""Apply changes""  on the transclusion dialog box and ""Save Page"" button on the page remains active even though there is no change on the transclusion dialog box","Created attachment 14037
+Apply changes button remains active
+
+**Attached**: {F12588}",1386618623,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fsd7k5bgeeg76dzbdwqt,task_subcomment,NA
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,"Steps to Reproduce:
+From Deryck at mw:VisualEditor/Feedback:
+
+Suppose I have:
+
+A foobar B
+C foobar D
+E foobar F
+== foobarbaz ==
+foobar
+
+* When I hit delete at B, the paragraph break is removed correctly, but the cursor jumps to the beginning of the previous paragraph (A).
+* When I hit delete at D, the paragraph break is also removed correctly, but the cursor jumps to or the right-hand side margin of the paragraph before that (to the right of B).
+* Sometimes the paragraph break is removed, and the first letter of the next paragraph is moved to the beginning of the previous paragraph (can't figure out the conditions of this, only observed it once and can't replicate it).
+* When I hit delete at F (just before a section header), the section header disappears... this might be the correct behaviour, but sadly hitting Ctrl+Z does not restore the section header.
+
+
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386614340,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4oyxxjh4jqregv7p7irk,task_description,resolved
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,The original issue(s) appear(s) to be fixed. The issue spotted by Tilman has been filed as bug 67985.,1405341696,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4oyxxjh4jqregv7p7irk,task_subcomment,NA
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,"Another example:
+
+In https://en.wikipedia.org/w/index.php?oldid=616866203&veaction=edit , place the cursor left of ""F"" in the word ""Former"" in the first paragrah, and hit the delete key. The ""F"" is deleted correctly, but the cursor jumps two to the left (between ""s"" and ""."").
+
+Reproduced in Firefox and Chromium under Ubuntu 14.04.",1405311380,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-4oyxxjh4jqregv7p7irk,task_subcomment,NA
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,"Similar, scary things happen at fr.wp, as reported by VEditors there.
+
+Just a few examples:
+0. Try to VEdit https://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove .
+1. Hit Del right next to ""blabla"".
+2. Notice the cursor is now on the top left margin of the page.
+3. Hit any key, say ""w"". I now have two more lines in my section, the first with a ""b"" on it, the second with a ""w"".
+4. Wait for some seconds. Watch as a ""b"" gets magically added to the header title.
+
+0. VEdit the page again.
+1. Hit Del right next to ""Hawker Siddeley Andover"".
+2. Hit any key, say ""w"". Watch as a pawn appears on the previous line, and both the letter and the pawn multiply after a few seconds.",1388048560,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-4oyxxjh4jqregv7p7irk,task_subcomment,NA
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,"The sequence above was performed on Firefox on Win7.
+
+---------------
+
+I've tried reproducing this on Firefox 25 on Ubuntu 12.04. Errors occur at all 3 locations for which errors have been described:
+
+The position of the cursor after hitting delete is unpredictable (read: Deryck has seen a few different outcomes and doesn't have enough time to exhaust all the possibilities); occasionally it even goes to the correct place.
+
+The ""eating up"" of the next (sometimes even previous) paragraph only occurs if you start inserting text immediately after hitting delete. If you click anywhere in the textbox or hit the arrow keys on the keyboard, no text is corrupted.
+
+Hitting Ctrl+Z after these errors yields unpredictable behaviour (same meaning of ""unpredictable"").",1386628058,PHID-USER-axuerq3wmxtfm6tav6bu,PHID-TASK-4oyxxjh4jqregv7p7irk,task_subcomment,NA
+Attempt to copy/paste some content blocks leads to JavaScript error,"If I copy from
+https://www.mediawiki.org/w/index.php?title=Wikimedia_Engineering/2013-14_Goals&veaction=edit
+
+to https://www.mediawiki.org/w/index.php?title=User:Eloquence/CP_tests&veaction=edit after clearing it
+
+and select the first section (from start to ""new opportunities."" including the navigation template), I get a JavaScript error 
+
+Uncaught TypeError: Cannot call method 'getType' of undefined  
+
+on the console, and VisualEditor becomes unresponsive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386573480,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-sb4u7diaqxhpd6losrrl,task_description,declined
+Attempt to copy/paste some content blocks leads to JavaScript error,"I think that this, too, was fixed by Ed as part of his suite of fixes for template copying; marking as WORKSFORME. Again, sorry for slow triage.",1394489980,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sb4u7diaqxhpd6losrrl,task_subcomment,NA
+"""Transclusion"" is not a good description for the button which inserts ""templates""","How is a new user supposed to know the meaning of ""Transclusion""?
+
+This should be replaced by something easier to understand such as ""Template"". It should also be easier to translate....
+
+The term is used on these messages:
+	'visualeditor-dialog-transclusion-title' => 'Transclusion',
+	'visualeditor-dialogbutton-transclusion-tooltip' => 'Transclusion',
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386436620,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-qd7qmbfus3ten7z3kj22,task_description,resolved
+"""Transclusion"" is not a good description for the button which inserts ""templates""","
+
+*** This bug has been marked as a duplicate of bug 55434 ***",1393525848,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qd7qmbfus3ten7z3kj22,task_subcomment,NA
+"""Transclusion"" is not a good description for the button which inserts ""templates""","BTW: I reported this after a comment on Portuguese Wikipedia:
+https://pt.wikipedia.org/wiki/WP:Esplanada/an%C3%BAncios?oldid=37579154#Predefini.C3.A7.C3.A3o_para_o_Dicion.C3.A1rio_Cravo_Albin",1386438135,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-qd7qmbfus3ten7z3kj22,task_subcomment,NA
+VisualEditor:Link inspector UI gets broken pressing Command+K to modify a link right after inserting it.,"Broken UI 1
+
+Steps to reproduce:
+
+1.Open the Editor
+2.Add a text and select it
+3.Press command+k to add link onto the text
+4.Again press command+k to modify it
+ 
+
+Observed Result:
+
+The link inspector UI gets broken 
+
+See the screenshots attached
+
+Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/The_link?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12374}",1386367440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6kcc6zwg5etjn2shtwsu,task_description,declined
+VisualEditor:Link inspector UI gets broken pressing Command+K to modify a link right after inserting it.,This issue got fixed.Not occurring anymore.,1389911909,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6kcc6zwg5etjn2shtwsu,task_subcomment,NA
+VisualEditor:Link inspector UI gets broken pressing Command+K to modify a link right after inserting it.,Clicking on the Link icon on the link also does that,1386367740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6kcc6zwg5etjn2shtwsu,task_subcomment,NA
+VisualEditor:Link inspector UI gets broken pressing Command+K to modify a link right after inserting it.,"Created attachment 14017
+Broken UI 2
+
+**Attached**: {F12375}",1386367495,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6kcc6zwg5etjn2shtwsu,task_subcomment,NA
+VisualEditor:Applying a special character insertion while selecting an image deletes the image,"Steps to  reproduce:
+
+1.Open the editor.
+2.Select an image
+3.Open the More>Special Character window
+
+
+Observed Result:
+The image gets deleted
+
+Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=6th_december&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386363900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wh2szim422wwxdw436uf,task_description,invalid
+VisualEditor:Applying a special character insertion while selecting an image deletes the image,This is intentional. Closing as INVALID.,1395355275,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wh2szim422wwxdw436uf,task_subcomment,NA
+VisualEditor:Applying a special character insertion while selecting an image deletes the image,"The behavior is different when the same action is done with Latex or Hieroglyphics which has been described in a separate issue:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58045",1387299843,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wh2szim422wwxdw436uf,task_subcomment,NA
+VisualEditor:Applying a special character insertion while selecting an image deletes the image,"sorry there are two more steps to the repro adding it here.
+
+4.Select any special character
+
+The special character does get added on the first line of the page
+but the image gets deleted.",1386364204,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wh2szim422wwxdw436uf,task_subcomment,NA
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,"Empty hiero tags
+
+Steps to reproduce:
+
+1.Open the editor
+2.Open the hiero insertion tool
+3.Now without closing it open another dialog box for example:Click on Latex/Special Characters/Reference etc.
+4.Close the second window
+5.Save the page
+
+Observed Result:
+The hiero insertion tool is also getting closed after step 4 but if you go to edit source you will see empty hiero tags 
+Now if you log out and press the back button on the browser and try editing the page as anonymous user , there are yellow bordered boxes saying ""Sorry this element can only be edited in source mode now"", on the positions where empty hiero tags are added
+
+See the screenshots attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12355}",1386361620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i2lmjhrkpsur4lev23mc,task_description,resolved
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,"Cannot reproduce.
+
+1. I go to https://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Aklapper&veaction=edit in Firefox 76.
+2. I click ""Insert > Hieroglyphs"" in the menubar. 
+3. Get a dialog.
+4. Click on ""Insert > Images and Media""
+5. Close second window.
+6. ""Publish changes"" is greyed out, hence cannot save page.
+
+Not happening anymore; neither after not closing the second window but entering something.",1590839983,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-i2lmjhrkpsur4lev23mc,task_subcomment,NA
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,Is this still occurring?,1439321171,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i2lmjhrkpsur4lev23mc,task_subcomment,NA
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,"(In reply to comment #1)
+> Created attachment 14012 [details]
+> yellow bordered boxes
+
+I see one tooltip (singular) saying ""Sorry, this element can only be edited in source mode for now."" I assume that's what you mean...
+
+**Attached**: {F12357}",1386373590,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-i2lmjhrkpsur4lev23mc,task_subcomment,NA
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,"Created attachment 14012
+yellow bordered boxes
+
+**Attached**: {F12357}",1386361742,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i2lmjhrkpsur4lev23mc,task_subcomment,NA
+VisualEditor:The special character insertion tool does not open up if the cursor is placed after a link,"screenshot
+
+Steps to reproduce:
+
+1.Open the Editor
+2.Add a link
+3.Place the cursor just after that link position
+4.Go to More>Special Characters
+
+Observed Result:
+The special character insertion tool does not open up
+
+See the screenshot attached
+
+Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=6th_december&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12351}",1386359820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6hhndn43mfdn55mwrsk5,task_description,declined
+VisualEditor:The special character insertion tool does not open up if the cursor is placed after a link,Cannot reproduce it now on betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Page_create&veaction=edit,1387231972,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6hhndn43mfdn55mwrsk5,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**Author:** `jhall`
+
+**Description:**
+Per a request from James F, we should start to expand the selection of environments (OS and browser combinations) that Visual Editor automated tests run via CloudBees.  
+
+For example, add a ""Internet Explorer 10 on Windows 8"" test, and related variations that CloudBees/SauceLabs can accommodate.
+
+Per Chris M, a good way to get started is to copy the existing ""Selenium"" template in CloudBees and figure out what we need to do to add Windows into the mix.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386357000,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_description,resolved
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,Yes.,1403988707,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"Can this be closed? We have this job now, for example:
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-windows_xp-firefox-sauce/",1403988505,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"Jeff, where are the jobs configured? I do not see them anywhere. This is where I have looked:
+
+https://github.com/zeljkofilipin/jenkins-job-builder-config
+https://gerrit.wikimedia.org/r/#/admin/projects/integration/jenkins-job-builder-config
+
+Did you create the jobs manually?",1393856730,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+Tests have been setup in CloudBees at the following locations:
+
+1) Chrome on Windows XP: https://wmf.ci.cloudbees.com/view/ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-windows_xp-chrome/
+2) Firefox on Windows XP: https://wmf.ci.cloudbees.com/view/ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-windows_xp-firefox/",1393392418,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"Change 110980 abandoned by Jhall:
+Adding new priority Windows browser tests for VisualEditor.
+
+Reason:
+Abandoning this change per a discussion between Chris, Željko and myself.  We have decided to implement new (browser + OS) combinations for use with SauceLabs via environment variable values rather than via hard-coded amendments to the mediawiki-selenium gem itself.
+
+https://gerrit.wikimedia.org/r/110980",1391707791,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+Setting bug status back to resolved since the 110980 Gerrit patch is a first step only; if that change works out well, we can add additional (browser + OS) combinations to work towards eventually resolving this bug.",1391456839,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"Change 110980 had a related patch set uploaded by Jhall:
+Adding new priority Windows browser tests for VisualEditor.
+
+https://gerrit.wikimedia.org/r/110980",1391456698,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+Per a chat with Rummana, the priority test environments to add (via CloudBees and Sauce Labs) are:
+
+1) Chrome on Windows XP
+2) Firefox on Windows XP",1391455649,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"(In reply to comment #3)
+> #2 The entire config folder will soon(tm) be moved to mediawiki-selenium
+> gem[2]. We should probably rename config.yml to browsers.yml (since it no
+> longer has any other information, only browsers) and expand the number of
+> combinations, like Wikibase has already done[3]
+
+config.yml is now moved to mediawiki-selenium gem. Feel free to expand the number of browser/OS combinations in the gem.",1390996603,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+(In reply to comment #3)
+> #1 I would hesitate to add more Jenkins jobs until existing ones[1] are rock
+> solid (meaning there were no failures in a week or so).
+> 
+> #2 The entire config folder will soon(tm) be moved to mediawiki-selenium
+> gem[2]. We should probably rename config.yml to browsers.yml (since it no
+> longer has any other information, only browsers) and expand the number of
+> combinations, like Wikibase has already done[3]
+> 
+> 1: https://wmf.ci.cloudbees.com/view/r-ve/
+> 2: https://gerrit.wikimedia.org/r/#/c/90560
+> 3:
+> https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/tests/
+> browser/config/browsers.yml
+
+Thanks Željko - I agree with both of your points, especially #1, which is an ongoing problem area (which I am working on!)",1386721860,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"#1 I would hesitate to add more Jenkins jobs until existing ones[1] are rock solid (meaning there were no failures in a week or so).
+
+#2 The entire config folder will soon(tm) be moved to mediawiki-selenium gem[2]. We should probably rename config.yml to browsers.yml (since it no longer has any other information, only browsers) and expand the number of combinations, like Wikibase has already done[3]
+
+1: https://wmf.ci.cloudbees.com/view/r-ve/
+2: https://gerrit.wikimedia.org/r/#/c/90560
+3: https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/tests/browser/config/browsers.yml",1386703629,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+In addition to the new template in CloudBees, I think we'll need to expand the config.yml file in the VisualEditor repo:
+
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/master/modules/ve-mw/test/browser/config/config.yml
+
+For example, our existing ""firefox"" profile is hard-coded to Firefox version 23 on Linux, so we'll need to add more entries for Firefox on Windows 8, etc.",1386366626,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+Created a new test template to mess around with:
+
+https://wmf.ci.cloudbees.com/template/81889c2c-ef15-4fad-b39b-8256eb9e841a/",1386362913,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"When ve-activated class is set on the body, it would be lovely to deactivate this feature as it's rather irritating. Think it's Shift+cursor or Ctrl+Shift+cursor or something similar?
+
+--------------------------
+**Version**: master
+**Severity**: normal",1386356220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qpfa44mctjexoxkqo5hy,task_description,resolved
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"We backported this fix to 1.23wmf6, so mediawiki.org and all sister sites should be fixed now.",1386720882,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"Change 100611 merged by MarkTraceur:
+Move clearInterface things to mw.LightboxInterface
+
+https://gerrit.wikimedia.org/r/100611",1386720390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"Change 100611 had a related patch set uploaded by MarkTraceur:
+Move clearInterface things to mw.LightboxInterface
+
+https://gerrit.wikimedia.org/r/100611",1386702965,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,Bam. Done. Thanks.,1386639709,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"Change 99722 merged by jenkins-bot:
+Move clearInterface things to mw.LightboxInterface
+
+https://gerrit.wikimedia.org/r/99722",1386639680,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"Change 99722 had a related patch set uploaded by MarkTraceur:
+Move clearInterface things to mw.LightboxInterface
+
+https://gerrit.wikimedia.org/r/99722",1386360971,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,This may be because we don't clear keydown listener events on closing the viewer. Patch incomiiiiing,1386356424,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+"VisualEditor:Cite error for no {{reflist}} template shows up,when references are added after the reflist in the article","Screenshot of the error
+
+Steps to reproduce:
+
+1.Open the Editor
+2.Add a reference to a line
+3.Add a references list
+4.Now add someother lines after the reflist with references
+5.Save the page
+
+Observed Result:
+The following error appears where as there is already a reflist.
+
+Cite error: There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page).
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12198}",1386272940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c5hksu6p5uhmhvzh64ht,task_description,duplicate
+"VisualEditor:Cite error for no {{reflist}} template shows up,when references are added after the reflist in the article","
+
+*** This bug has been marked as a duplicate of bug 54906 ***",1393541417,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c5hksu6p5uhmhvzh64ht,task_subcomment,NA
+"VisualEditor:Cite error for no {{reflist}} template shows up,when references are added after the reflist in the article","
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:
+https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/testinfobox",1386273019,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c5hksu6p5uhmhvzh64ht,task_subcomment,NA
+VisualEditor:Pressing shift+Right arrow on a newly created page in VE opens up images/logos from media commons,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on Create beta
+2.Press Shift+Right arrow
+
+Observed Result:
+Some images/logos from media commons opens up with image viewer in VE.
+
+See the screenshot attached.
+
+Following errors are found:
+Uncaught TypeError: Cannot read property 'pages' of undefined
+XMLHttpRequest cannot load http://commons.wikimedia.org/w/api.php?action=query&format=json&list=users&ususers=Mike%2Elifeguard&usprop=gender. Origin http://en.wikipedia.beta.wmflabs.org is not allowed by Access-Control-Allow-Origin. /w/index.php?title=Rys&veaction=edit#mediaviewer/File:Wikibooks-logo.svg/1:1
+Uncaught TypeError: Cannot read property 'pages' of undefined
+XMLHttpRequest cannot load http://commons.wikimedia.org/w/api.php?action=query&format=json&list=users&ususers=-xfi-&usprop=gender. Origin http://en.wikipedia.beta.wmflabs.org is not allowed by Access-Control-Allow-Origin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12098}",1386191040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qxsrbiw7op5y6y6inavq,task_description,resolved
+VisualEditor:Pressing shift+Right arrow on a newly created page in VE opens up images/logos from media commons,I think this was fixed a while ago with fixes to MediaViewer.,1395355311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qxsrbiw7op5y6y6inavq,task_subcomment,NA
+VisualEditor:Pressing shift+Right arrow on a newly created page in VE opens up images/logos from media commons,Pressing just right arrow is now bringing up those logos,1386197120,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qxsrbiw7op5y6y6inavq,task_subcomment,NA
+VisualEditor:Pressing shift+Right arrow on a newly created page in VE opens up images/logos from media commons,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5",1386191147,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qxsrbiw7op5y6y6inavq,task_subcomment,NA
+VisualEditor:Experiencing extreme slow response for all actions in VE in Betalabs,"Currently, while saving a page or when a link insertion too; searches for matching page it is taking longer than usual time in Betalabs.
+
+I am not facing it any other environment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386188280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mbub4crzlrqq6sng5lzq,task_description,declined
+VisualEditor:Experiencing extreme slow response for all actions in VE in Betalabs,I think this was due to the Labs cluster being DDoSed; marking as WORKSFORME as that's been cleared up.,1386356657,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mbub4crzlrqq6sng5lzq,task_subcomment,NA
+BetaFeatures: All icons must have RTL versions,"Beta features have icons to represent them at Special:Preferences.
+
+They usually show a schematic representation of a MediaWiki page with a logo in the top left corner, and this of course means that they should be flipped for RTL languages.
+
+Some of them are trivial - just a horizontal flip.
+
+Some of them are less trivial - for example, in the one for the VisualEditor formula editing I flipped the image and then flipped the Sigma icon inside it so it would still look like Σ and not flipped.
+
+Some of them are even less trivial, for example the icons for the font style experiments. It shows the Latin letter A, and it's weird to show a Latin letter in the beginning of a right-to-left text. Luckily, there are only two major right-to-left scripts, so I made one icon for Hebrew and one for Arabic.
+
+Some relevant sample commits by myself, already merged:
+* https://gerrit.wikimedia.org/r/#/c/94379/
+* https://gerrit.wikimedia.org/r/#/c/94269/
+* https://gerrit.wikimedia.org/r/#/c/94423/
+
+On this commit Jon and Juliusz complained that the image should be re-saved with a smaller size and less metadata:
+* https://gerrit.wikimedia.org/r/#/c/98159/
+
+The SVGs from the previous merged commits may have to be re-done as well.
+
+Any future beta features should have RTL-compatible icons from the start, preferably done by professional designers.
+
+See some more details here:
+https://www.mediawiki.org/wiki/Design_best_practices#Right-to-left_languages
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386162480,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-nng5pyk5o4ztbazvqymy,task_description,resolved
+BetaFeatures: All icons must have RTL versions,"Done by Amir. In future, it's the PM's job (i.e. my job for now) to make sure this is done before deployment.",1387320035,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nng5pyk5o4ztbazvqymy,task_subcomment,NA
+VisualEditor: the {{phpi}} template in mediawiki.org is not showing any content while editing in VE,"Try editing https://www.mediawiki.org/wiki/User:Amire80/phpi in VE.
+
+The template's content doesn't show when editing in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386151980,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-2mttdczw7itqtq7orbyc,task_description,declined
+VisualEditor: the {{phpi}} template in mediawiki.org is not showing any content while editing in VE,"(In reply to Alex Monk from comment #1)
+> Works for me.
+
+For me too. Probably got fixed at some point. Thanks for testing.",1400009090,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-2mttdczw7itqtq7orbyc,task_subcomment,NA
+VisualEditor: the {{phpi}} template in mediawiki.org is not showing any content while editing in VE,Works for me.,1400008936,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2mttdczw7itqtq7orbyc,task_subcomment,NA
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,"Screenshot
+
+I am getting pawn while typing fast on some pages on betalabs sometimes.
+It is not always reproducible.
+I will update the bug if i find any steps to reproduce.
+
+See the screenshots attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12011}",1386113580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_description,declined
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,These issues seem now to be fixed.,1406598559,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_subcomment,NA
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,"Got following error while this was happening:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 93
+Uncaught Error: Offset could not be translated to a DOM element and offset: 169",1386114426,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_subcomment,NA
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,"Created attachment 13973
+screenshot of pawns
+
+**Attached**: {F12012}",1386113733,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_subcomment,NA
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example 
+
+http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386113706,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_subcomment,NA
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","**Author:** `Wikifram`
+
+**Description:**
+Currently, bugs about Flow are shelved under Mediawiki extensions, unlike e.g. VisualEditor or less important things like QRpedia. Considering the probable serious influx of Flow bugs in the near future, I would propose that it gets its own ""level"", so that e.g. in the search box it is selectable (I mean that if you select ""search bugs"" on the left side, under ""Product"", you should be able to choose ""Flow"" directly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386068580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_description,declined
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","**Wikifram** wrote:
+
+Yeah, sorry about my earlier remark, I was pissed off at a WMF representative (for a oomment made at Mediawiki, not on Bugzilla) and your comment came for me at the wrong time. I shouldn't have replied so strongly. I still think it isn't user friendly to not have it separately, but I appreciate that you try to make it easier for everyone involved anyway.",1386105307,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_subcomment,NA
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","I wouldn't translate it to that, however Bugzilla is primarily a tool for developers and tech-savvy users (though I try to make it more user-friendly, e.g. by the guided bug entry form which is now linked from the very top of https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia since yesterday).
+
+If you don't feel comfortable on https://bugzilla.gnome.org/enter_bug.cgi and don't know that Flow is a ""MediaWiki extension"" (and can be found under that product), http://www.mediawiki.org/wiki/Extension:Flow and especially https://www.mediawiki.org/wiki/Flow_Portal#Contact_and_links provide links how to provide feedback and also where exactly to find and create new bug reports or feature requests. 
+
+Furthermore, once Flow has seen wider deployment, I expect the Flow team and involved Communication folks to set up similar Feedback channels like for VisualEditor at https://en.wikipedia.org/wiki/WP:VE/F which do not necessarily require to interact with Bugzilla.",1386090165,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_subcomment,NA
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","**Wikifram** wrote:
+
+So, translated, ""fuck everyone wanting to find something, Bugzilla is not for you""? Very user-friendly reply. What's the advantage of keeping Flow buried among the other extensions like ""AbsenteeLandlord"", ""Desysop"", and so on? I hope yu will reconsider once you get lots of Flow bugs here, which will probably be soon.",1386082709,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_subcomment,NA
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","Flow is technically speaking an extension, and Bugzilla's taxomony is not primarily based on visibility. 
+(However there have been exceptions from rules, e.g. when the codebase is rather complex and requires subcomponents, like in case of VisualEditor.)",1386069221,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_subcomment,NA
+VisualEditor:Reloading the page in read mode opens up the editor,"Steps to reproduce:
+
+1.Click on the Edit beta button
+2.Switch to Edit Source
+3.Switch back to VE
+4.Click on Cancel
+5.Reload the page
+
+
+Observed Result:
+Even after cancelling the edit, in the URL ""&veaction=edit"" still remains appended , therefore after reloading the page, VE opens up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386028260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gqb7b73hwnhh6qxsaoee,task_description,resolved
+VisualEditor:Reloading the page in read mode opens up the editor,"
+
+*** This bug has been marked as a duplicate of bug 57901 ***",1386035934,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqb7b73hwnhh6qxsaoee,task_subcomment,NA
+VisualEditor:Reloading the page in read mode opens up the editor,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Groel&veaction=edit",1386028361,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gqb7b73hwnhh6qxsaoee,task_subcomment,NA
+Jenkins: Install node-csslint,"Also, set up initial jobs for projects that already use csslint in their local-dev Gruntfile (oojs-ui and visualeditor at the moment).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1386027300,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-poin5yyszgpyi25gk3je,task_description,resolved
+Jenkins: Install node-csslint,"(In reply to comment #5)
+> Does that also lint less or is there a extra tool?
+
+No, we don't yet use cssslint in mediawiki-core (current code doesn't pass) and neither does it validate LESS in any way.",1390847473,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"This has been installed, deployed and is now also actively used by various projects.
+
+In the main 'test' pipelines, however, this is no longer used as we have since migrated to using npm-test (from package.json) directly by installing it in a virtual machine in labs and executing it as specified by the source repository (instead of the install provided by Jenkins).",1390847427,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,Does that also lint less or is there a extra tool?,1386359787,PHID-USER-qaoxfiqu6bxhd5ehlwhc,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"Change 98868 merged by Krinkle:
+Create macro for csslint and use in oojs-ui and VisualEditor
+
+https://gerrit.wikimedia.org/r/98868",1386099008,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"Change 98868 had a related patch set uploaded by Krinkle:
+Create macro for csslint and use in oojs-ui and VisualEditor
+
+https://gerrit.wikimedia.org/r/98868",1386098003,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"Change 98722 merged by jenkins-bot:
+Install Grunt plugin for csslint
+
+https://gerrit.wikimedia.org/r/98722",1386028242,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"Change 98722 had a related patch set uploaded by Krinkle:
+Install Grunt plugin for csslint
+
+https://gerrit.wikimedia.org/r/98722",1386027315,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Type something on the first line
+3.Place the cursor at the beginning of the line and insert a template ""Bronze Age""
+4.Save the page
+5.Reopen the editor
+6.Click on More>Reference and add a reference
+7.Type something on the CE
+8.Click on Save Page
+
+Observed Result:
+The Save page loader continues for indefinite amount of time.
+The following errors are found in the developers tool:
+
+Uncaught TypeError: Cannot call method 'apply' of undefined load.php:2
+Uncaught Error: Unbalanced input passed to document load.php:109
+Uncaught TypeError: Cannot read property 'keyedNodes' of undefined load.php:201
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12768}",1386026340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-34urcguvs6tsm3wpvxu2,task_description,resolved
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"I can't reproduce this, so I assume it is fixed. Please reopen if reproduction of the bug is achieved.",1498128539,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,This is so old I wonder if it still happens?,1498124461,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"I encountered a very similar bug two days ago at https://en.wikipedia.org/w/index.php?title=San_Francisco%E2%80%93Oakland_Bay_Bridge&oldid=650099835&veaction=edit, twice (once when clicking the Save button, and then after starting anew and clicking ""Switch to source editing"" in the Hamburger menu. In both cases, nothing happened after the click except console error messages, and consequently I wasn't able to save my edit).
+
+I wasn't able to reproduce it again, but I remember that the edit involved deleting the first reference and replacing it with a different one, using a citation template where I added an additional (non-default) parameter and then deleted it again in the template editor.
+
+This was in Chrome on a MacBook. Unfortunately I lost the JavaScipt console's output due to an unrelated crash, but I remember that it contained the word ""unbalanced"" just like in the original bug report here.",1426549953,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Could not reproduce on https://en.wikipedia.org/w/index.php?title=User%3AAKlapper_%28WMF%29%2FSandbox%2FT88306&diff=649905376&oldid=649903809 following exactly the steps in T59898#645389 in Firefox 36. 
+
+Is this still an issue, 15 months later? Setting task status to ""Stalled"".",1425509190,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Now The Save Page button does not work after the following steps:
+1.Click on the Edit button
+2.Type something on the first line
+3.Place the cursor at the beginning of the line and insert an image 
+4.Save the page
+5.Reopen the editor
+6.Press Delete twice
+7.Type something 
+8.Click the button ""save page""
+
+Following error appears:
+Uncaught Error: Unbalanced data: looking for closing /mwBlockImage load.php:150",1386111388,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,I can't reproduce now - perhaps due to fixing bug 57654?,1386110555,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Another way to reproduce it:
+After step 5 just click on ""Delete"" and click the button ""Save"".
+
+The following error appear this time:
+
+
+Uncaught Error: Unbalanced set of replace operations found load.php:65
+Uncaught Error: Unbalanced data: looking for closing /mwBlockImage load.php:146",1386029262,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,This issue can be reproduced with images too instead of template.,1386029179,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/infinite_save?veaction=edit",1386026454,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The link icon appears on the template while attempting to apply a format on the article,"Screenshot
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button for a page
+2.Type something with a link on the main page
+3.Add a template for example:Bronze Age
+4.Save the page
+5.Reopen the editor
+
+Observed Result:
+
+1. Opening the editor selects/highlights the template,but if user attempts to press delete it deletes the first line gets deleted
+
+2.If user clicks on the numbered list or bullet list icon from the toolbar a link icon appears on the template
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12499}",1385850960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wodgydx2ln55w6eo4p32,task_description,resolved
+VisualEditor:The link icon appears on the template while attempting to apply a format on the article,"Possibly maybe this is now fixed? I couldn't reproduce, but I may have been doing it wrongly.",1402553504,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wodgydx2ln55w6eo4p32,task_subcomment,NA
+VisualEditor:The link icon appears on the template while attempting to apply a format on the article,"Slight modification on steps to reproduce:
+
+3.When you add a template place your cursor at the beginning of the first line which contains a link.",1385852486,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wodgydx2ln55w6eo4p32,task_subcomment,NA
+VisualEditor:The link icon appears on the template while attempting to apply a format on the article,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit",1385851038,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wodgydx2ln55w6eo4p32,task_subcomment,NA
+VisualEditor:The format of the text does not change if the cursor is at the end of the text though the options are highlighted in the menu,"screenshot
+
+Steps to reproduce:
+
+1.Place the cursor at the end of the text or in the beginning or in the middle of a text
+2.Now select any or all of the options from More>Computer Code/Strikethrough/Underline/Superscript/Subscript
+
+Observed Result:
+
+Observe that all the options are highlighted in the menu bar but the text format does not change accordingly.If the format of the text is not suppose to change, providing way to disable to the highlight will be better
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12445}",1385763600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ibwc5pqjlv3hmwafkxsy,task_description,resolved
+VisualEditor:The format of the text does not change if the cursor is at the end of the text though the options are highlighted in the menu,"It looks like a formatting button like ""subscript"" is highlighted if a character typed in the cursor's current location would have that formatting. This seems like a sensible behavior.",1437700804,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-ibwc5pqjlv3hmwafkxsy,task_subcomment,NA
+VisualEditor:The format of the text does not change if the cursor is at the end of the text though the options are highlighted in the menu,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/pawn?veaction=edit",1385763638,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ibwc5pqjlv3hmwafkxsy,task_subcomment,NA
+VisualEditor:Deleting an image inside a image settings and reverting it back makes the editor unresponsive,"Steps to reproduce:
+
+1.Click on the Edit button for a page
+2.Insert a image in the page
+3.Go to the media settings and add another image as caption
+4.Save the page
+5.Reopen the editor .
+6.Open the image settings and delete the image as caption.
+7.Undo the action
+8.Click on the media settings button for the image that is as caption
+
+Observed result:
+A media settings dialog box appears with no content but it cannot be crossed out .Also the ""apply changes"" button does not work therefore editor becomes unresponsive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385757300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mrrmkqrflbgdrpb2xbtx,task_description,declined
+VisualEditor:Deleting an image inside a image settings and reverting it back makes the editor unresponsive,Looks like this got fixed at some point.,1414869201,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mrrmkqrflbgdrpb2xbtx,task_subcomment,NA
+VisualEditor:Deleting an image inside a image settings and reverting it back makes the editor unresponsive,"Test Environment: production
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/cancelled_edit_then_create_page&veaction=edit",1385757340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mrrmkqrflbgdrpb2xbtx,task_subcomment,NA
+VisualEditor:  Bare URLs of the [http://example.com] format cannot be edited,"Intention:
+Add a label to [http://example.com/]
+
+Steps to Reproduce:
+1. Open the page in VisualEditor
+2. Click on the link (which displays as ""[1]"")
+
+
+Actual Results:  
+Nothing.  It is not possible to edit the link.  If opened manually, the link inspector is empty.
+
+Expected Results:  
+1. That the link icon would display when the link was selected.
+2. That the link inspector would show the URL.
+3. That a label could be added (to create [http://example.com Example.com])
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385755140,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-awob47g62om2eeegot3r,task_description,resolved
+VisualEditor:  Bare URLs of the [http://example.com] format cannot be edited,"
+
+*** This bug has been marked as a duplicate of bug 53505 ***",1386000770,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-awob47g62om2eeegot3r,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears inside a media item's caption while user is typing in the page","Steps to reproduce:
+
+1.Click on the edit button for a page where you have some images on the right of the page
+
+2.Type something as the first line
+3.Delete the first line by pressing backspace
+4.When it deletes the first character of the line ,pressing backspace again still keeps the cursor in the main page
+5.Now type something
+
+
+Observed Result:
+Though the cursor is in the main page,a pawn appears inside the caption of the image at the right.
+
+A pawn will appear in the main document for the following steps:
+5. if after step 4 , user presses backspace again 
+6.While the image at the right is highlighted press the Right arrow > from the keyboard
+7.When the cursor comes to the main article type something
+
+A Pawn appears in the main document.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385688600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6t2ellqdwuvd5rouaqmf,task_description,resolved
+"VisualEditor: Pawn (""♙"") appears inside a media item's caption while user is typing in the page","Possibly got fixed by https://bugzilla.wikimedia.org/show_bug.cgi?id=57927
+Cannot reproduce it now.",1387229483,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6t2ellqdwuvd5rouaqmf,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears inside a media item's caption while user is typing in the page","Created attachment 13930
+Screenshot
+
+**Attached**: {F12417}",1385688823,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6t2ellqdwuvd5rouaqmf,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears inside a media item's caption while user is typing in the page","Test Environment: production
+Browser: Chrome Version FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/cancelled_edit_then_create_page&veaction=edit",1385688711,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6t2ellqdwuvd5rouaqmf,task_subcomment,NA
+VisualEditor:Clicking on reference does not bring up the reference add dialog for a specific case in production,"Steps to reproduce:
+
+1.Click on the edit button for a page where you have a image on the right of the page which has another image as caption
+
+2.Type something as the first line
+3.Delete the first line by pressing backspace
+4.When it deletes the first character of the line ,pressing backspace again still keeps the cursor in the main page
+5.Now add a reference to the empty space,which gets added to the caption of the image at the right.
+6.Now type something on the second line and add a reference
+
+Observed Result:
+
+The dialog box for adding reference does not appear anymore.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385676300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-euq7ddmd6rhlinex2kpe,task_description,resolved
+VisualEditor:Clicking on reference does not bring up the reference add dialog for a specific case in production,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/noref?veaction=edit",1385676383,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-euq7ddmd6rhlinex2kpe,task_subcomment,NA
+VisualEditor:Pawn (♙) appears in Media Settings when there is another media added in the caption,"Screenshot of the pawn
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Add an image in the caption of that media.
+3.Type a text in the caption
+4.Delete the text by pressing the backspace
+5.When the cursor reaches the image at the right,Press the right arrow to go back to the initial position of the deleted text.
+6.Type something again at that position.
+
+Observed Result:
+A Pawn (♙) appears in the Media Setting
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12405}",1385673960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3rb6x5qzoi77sgsqzncr,task_description,resolved
+VisualEditor:Pawn (♙) appears in Media Settings when there is another media added in the caption,This appears to be long-fixed.,1406598618,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3rb6x5qzoi77sgsqzncr,task_subcomment,NA
+VisualEditor:Pawn (♙) appears in Media Settings when there is another media added in the caption,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5
+Example Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/test_field&veaction=edit",1385674053,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3rb6x5qzoi77sgsqzncr,task_subcomment,NA
+VisualEditor: Improve link inspector to address usability issues,"There's currently two user experience issues that I think need to be addressed soon.
+
+1. Creating (or, more precisely, inserting) a new link.
+
+When creating a new link, there is no intuitive way to assign it a label until you decide to close the link inspector at which point the link target text appears as the link label.
+
+
+2. Editing the label of an existing link.
+
+When editing the label one has to manually ensure all of the link text is selected and replaced. In doing so it is almost impossible not to accidentally delete the link.
+
+Given ""foo <a>bar</a> baz"", selecting ""bar"" manually and typing will replace it with a text node. So essentially the only way to change is to do it in two arbitrary halves.
+
+Additionally, even if selecting and replacing would work, selecting an entire external link (e.g. right after insertion and the url becoming the label) can be quite difficult since URLs tend to contain one or more word-boundaries (that is word-boundaries from the perspective from double-click make-word-selected features that browsers provide).
+
+2b. Anti-pattern: Ambiguous focus, unable to overwrite text
+
+When clicking on the link the ""right"" way, it opens the inspector at which point the entire link label is nicely selected (even if the link spans multiple space-separated words or things like urls that contain word-boundary characters), but it seems hard to retain this selection as any action outside the inspector collapses the selection (maybe impossible, at least I couldn't).
+
+This also makes it hard to fully delete a link. The unlink feature (or clear-formatting) leaves the text. So one would have to carefully make a selection that spans the entire link label and remove that.
+
+---
+
+
+Note, there's currently a few open bugs for technical problems (not UX problems) that might require a (whether or not temporary) solution to the above UX issues as they currently happen due to certain actions not being expected by the code. In fixing those, we most likely have to come up with some way to handle this.
+
+For example: (bug  56976) Pawn appears when clicking into the label after creating a link
+
+When creating a new link and clicking (conceptually ""back"") in the document
+where the cursor was from the link inspector, a pawn appears. This happens because right now links have no label until you close the inspector. So when creating a new link, the cursor position remains empty the entire time. When eventually manually closing the inspector (or clicking anywhere other than the current paragraph) the empty (internal pawn) placeholder label is replaced with the text of the link target.
+
+The immediate fix would be to do the expansion earlier (or even live while the user is working on the link target), however that still leaves a smell of UX issue #2 afterwards.
+
+
+--
+
+Summary of issues:
+
+* It is impossible to select a link label (selecting it also selects the open/close tag, which means typing over it removes the link). To change a label, one has to enter the new label inside the old (e.g. in the middle of it), and strip away the outer halves of the old label.
+
+* It is hard to provide a label for a new link as one has to close the inspector first.
+
+* It is hard to delete a link (as an object that is, unlinking text is easy) as one can't focus it. And the auto-selection when opening the inspector always disappears when returning to the document from the inspector.
+
+Possible solutions:
+
+* Implement a new user interface concept in the content editable surface that would allow a cursor (and selection) to fully cover an annotation whilst not covering the open/close of the annotation. This would enable one to select (and replace) the label of a link.
+
+* Add the link label as an additional field to the link inspector.
+
+* (or; maybe) turn the link into a focusable node and have it no longer be an annotation. This naturally comes with complications, but may be for the best.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385657880,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xoirrjdhitvqz5v3riwf,task_description,resolved
+VisualEditor: Improve link inspector to address usability issues,"
+
+*** This bug has been marked as a duplicate of bug 48789 ***",1395197341,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xoirrjdhitvqz5v3riwf,task_subcomment,NA
+puppet config of Parsoid localsettings breaks in labs-vagrant,"Parsoid doesn't work when you add the visualeditor role in Labs-Vagrant setup,
+clients get 404 errors. After tweaking parsoid to log the actual error (bug 57694), /var/log/upstart/parsoid.log contains
+
+  Stack trace: DoesNotExistError: Page Fetch failure for null : Error: Invalid URI
+  ""undef/w/api.php?format=json&action=query&meta=siteinfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensiontags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols""
+
+Obviously undef/w/api.php is going to give 404.
+
+The bad URL path arises because puppet/manifests/roles.pp sets $server_url to 'undef' if forwarded_port isn't set, and it somehow isn't set in labs-vagrant. puppet/modules/mediawiki/templates/parsoid.localsettings.js.erb propagates this to /srv/parsoid/js/api/localsettings.js which contains 
+  parsoidConfig.setInterwiki( 'localhost', 'undef/w/api.php' )
+
+(Erik Bernhardson figured all this out!)
+
+One fix is to not set $server_url to undef. Patch coming.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385606640,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-pgc3jemya3dsi32iivp4,task_description,resolved
+puppet config of Parsoid localsettings breaks in labs-vagrant,Thanks for the detailed report and the patch.,1385609666,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-pgc3jemya3dsi32iivp4,task_subcomment,NA
+puppet config of Parsoid localsettings breaks in labs-vagrant,"Change 98060 merged by Ori.livneh:
+Set $server_url to something other than undef
+
+https://gerrit.wikimedia.org/r/98060",1385609634,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pgc3jemya3dsi32iivp4,task_subcomment,NA
+puppet config of Parsoid localsettings breaks in labs-vagrant,"Change 98060 had a related patch set uploaded by Spage:
+Set $server_url to something other than undef
+
+https://gerrit.wikimedia.org/r/98060",1385608993,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pgc3jemya3dsi32iivp4,task_subcomment,NA
+VisualEditor:Reflist is appearing as bullet list if while inserting reflist the cursor is at the end of an empty bulleted item,"Screenshot
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Type a text with reference in the page
+3.Make it a bulleted list by selecting the option from toolbar.
+4.Press Enter to entry the second item on the list but leave it blank 
+5.Now click on More>References list to add a reflist to the page
+6.Save the page
+
+Observed Result:
+
+The reflist is appearing as bulleted list
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12350}",1385596680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kwxuse4ccvh4vqlns2jq,task_description,resolved
+VisualEditor:Reflist is appearing as bullet list if while inserting reflist the cursor is at the end of an empty bulleted item,Seems to work correctly now.,1437700987,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-kwxuse4ccvh4vqlns2jq,task_subcomment,NA
+VisualEditor:Reflist is appearing as bullet list if while inserting reflist the cursor is at the end of an empty bulleted item,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/testlive",1385596774,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kwxuse4ccvh4vqlns2jq,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting the preceding text of a reference icon,"Screenshot of the pawn
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Add a reference to a text
+3.Select the reference icon
+4.Press left arrow key to move the cursor to the left of the icon
+5.Now delete all of the text on the left of the icon by pressing backspace button
+
+Observed Result:
+
+A pawn ♙ appears right next to the reference icon.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12224}",1385509080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dmyb42alfmzpnf6hhtbk,task_description,resolved
+VisualEditor: Pawn ♙ appears after deleting the preceding text of a reference icon,This looks fixed to me. Not sure exactly when.,1406598426,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dmyb42alfmzpnf6hhtbk,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting the preceding text of a reference icon,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page: https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox",1385509144,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dmyb42alfmzpnf6hhtbk,task_subcomment,NA
+VisualEditor: Link is not getting added when the clear formatting is used while the link inspector was open,"Steps to reproduce:
+
+1.Create the Edit button
+2.Select a text
+3.Open the link inspector
+4.Click on the clear formatting icon from the toolbar
+5.While the link inspector is still open select the first matching page
+6.Apply the link
+
+Observed Result:
+The link did not get applied.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385488740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uhuzwsa5ueu5efipt6sv,task_description,declined
+VisualEditor: Link is not getting added when the clear formatting is used while the link inspector was open,"We now close the inspector when you click into the toolbar, which essentially fixes the underlying issue.",1402550186,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhuzwsa5ueu5efipt6sv,task_subcomment,NA
+VisualEditor: Link is not getting added when the clear formatting is used while the link inspector was open,I would suggest to close the inspector as user clicks on clear formatting,1385492198,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uhuzwsa5ueu5efipt6sv,task_subcomment,NA
+VisualEditor: Link is not getting added when the clear formatting is used while the link inspector was open,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page: Try applying the link to page ""link"" to the text link on this page:
+https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test_field?venotify=created",1385488871,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uhuzwsa5ueu5efipt6sv,task_subcomment,NA
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"The reference for the main page
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Add a reference to a text
+3.In the reference dialog add an image
+4.Also type some text into that reference box (for example ""The content"" in this case.)
+5.Now select the image
+6.Go to Media Settings
+7.Now add a reference to that image
+8.Type anything for this second reference box
+9.Apply changes in all three dialog boxes
+10.Save the changes 
+11.Reopen the editor
+12.Select the reference [1]
+13.Open the reference dialog box
+
+Observed Result:
+The text ""The content"" appears as a template with a highlighted blue box around it.Now click on the [1] reference on the image by going to the media settings of the image.
+It opens the same content for the first reference and it keeps on opening the same window as you repeatedly do it for all the reference windows appears.
+
+Expected Result:
+The reference on the main page and the reference on the image should be different content.But since the reference in image [1] is pointing to the same [1] for the article ,this issue arises.
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58270
+
+**Attached**: {F12091}",1385427060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sbvwivlalvusgjwp5ire,task_description,resolved
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"Re-checked - seems that the contents of all ""nested"" references are displayed correctly. No repeatedly open windows appear. 
+
+Marking as resolved.",1423527553,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-sbvwivlalvusgjwp5ire,task_subcomment,NA
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test_copy_and_paste?veaction=edit
+
+Click on the [1] reference of this page.",1385427311,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sbvwivlalvusgjwp5ire,task_subcomment,NA
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"Created attachment 13908
+Opening the same dialog box unlimited times
+
+**Attached**: {F12093}",1385427248,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sbvwivlalvusgjwp5ire,task_subcomment,NA
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"Created attachment 13907
+How it appears after step 13
+
+**Attached**: {F12092}",1385427205,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sbvwivlalvusgjwp5ire,task_subcomment,NA
+VisualEditor:When the cursor is in the middle of a text the formatting (Bold/Italic/No format) does not work properly,"Steps to reproduce:
+
+1.Click on the Edit button
+2. Place the cursor in the middle of a text, for example between u and r of ""cursor""
+3.Try different heading format and bullet or numbered list option:all of them work
+4.But try formatting to Bold/Italic/No format: it does not work but the buttons are selected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385409600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ggvevjnwwlcst5xdmmsn,task_description,invalid
+VisualEditor:When the cursor is in the middle of a text the formatting (Bold/Italic/No format) does not work properly,"That's supposed to do nothing initially, then when you start typing, the text you type will be bold/italic/whatever.",1414138312,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ggvevjnwwlcst5xdmmsn,task_subcomment,NA
+VisualEditor:When the cursor is in the middle of a text the formatting (Bold/Italic/No format) does not work properly,"Test Environment: test2
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://test2.wikipedia.org/w/index.php?title=Testing2511&veaction=edit",1385409685,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ggvevjnwwlcst5xdmmsn,task_subcomment,NA
+VisualEditor:Attempting to delete a template at the beginning of an article deletes the whole paragraph following it,"Steps to reproduce:
+
+1.Click on the ""Edit"" button for a page in production
+2.At the beginning of the article place a template
+3.Write a paragraph following that template.
+4.Save the page
+5.Reopen the page in Edit mode
+
+Observed Result:
+The template gets selected(blue highlight appears) automatically.However the template icon does not appear to edit the template rather a four sided drag icon appears on it.
+Now if you press the delete button while the template is selected ,the following paragraph gets deleted.Pressing undo does not get it back on the page.User have to cancel this edit session and restart again to by pass the issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385408580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-q2lm2rmvtrop4xotxxnt,task_description,resolved
+VisualEditor:Attempting to delete a template at the beginning of an article deletes the whole paragraph following it,This now [[https://en.wikipedia.org/w/index.php?title=User%3ARYasmeen_%28WMF%29%2Ftemplate_at_the_beginning&type=revision&diff=663104473&oldid=583275067|works correctly]]! ,1432052899,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-q2lm2rmvtrop4xotxxnt,task_subcomment,NA
+VisualEditor:Attempting to delete a template at the beginning of an article deletes the whole paragraph following it,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/template_at_the_beginning",1385408648,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-q2lm2rmvtrop4xotxxnt,task_subcomment,NA
+VisualEditor: [Regression?] Cursor appears misplaced after hitting Enter twice in a list,"This is where the cursor shows up in the text
+
+Might be related to https://bugzilla.wikimedia.org/show_bug.cgi?id=41064, or not.
+
+1. Reach https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=583262564 .
+2. Put the cursor after the last reference.
+3. Hit Enter once. A new bullet is correctly added.
+4. Hit Enter again.
+
+Possible outcomes:
+1) see screenshot: the cursor blinks between two lines, on the word ""cognitive"" (observed in Chrome, Vector/Monobook);
+2) the cursor is attached to the top right corner of the picture of Emily Deschanel (Firefox, Vector);
+3) the cursor is nowhere in sight (Firefox, Monobook).
+
+Notice that if you repeat the procedure at this point, it will work in Chrome, it will still fail in FF.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7
+**Platform**: PC
+
+**Attached**: {F12043}",1385404860,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-22g4ckg3k3byisqvwxiy,task_description,resolved
+VisualEditor: [Regression?] Cursor appears misplaced after hitting Enter twice in a list,"This was fixed a couple of weeks ago in the HandleEnter re-write work, I think.",1395360338,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-22g4ckg3k3byisqvwxiy,task_subcomment,NA
+VisualEditor: [Regression?] Cursor appears misplaced after hitting Enter twice in a list,"(Sorry, please read, ""it will work in Firefox, it will still fail in Chrome"".)",1385405084,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-22g4ckg3k3byisqvwxiy,task_subcomment,NA
+"VisualEditor: If a link that doesn't have a pipe is changed, the link target remains","Consider that you have an internal wiki link that doesn't use a pipe, for example ""[[Danzig]]"". If you edit the page in VE and change the text from ""Danzig"" to ""Gdańsk"" without using the link inspector the result will be ""[[Danzig|Gdańsk]]"". See the history of https://en.wikipedia.org/wiki/User:Amire80/links-nopipe .
+
+It is not obvious to the user what is happening - does the target or does it not? The users may want to achieve one result or the other in different cases. My own hunch is that users will more frequently want to change the target as well, although that is just a guess.
+
+If we have a reason to think that one behavior is far more common than the other, then it should be the default. If we are not sure, than some more indication about the target will be useful. The only ways to be sure before saving are to check the diff to open the link inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54947",1385296620,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-m7leu4xitl3lklt5rrdg,task_description,duplicate
+"VisualEditor: If a link that doesn't have a pipe is changed, the link target remains","
+
+*** This bug has been marked as a duplicate of bug 54947 ***",1400106756,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m7leu4xitl3lklt5rrdg,task_subcomment,NA
+"VisualEditor: If a link that doesn't have a pipe is changed, the link target remains","(In reply to Amir E. Aharoni from comment #0)
+> Consider that you have an internal wiki link that doesn't use a pipe, for
+> example ""[[Danzig]]"". If you edit the page in VE and change the text from
+> ""Danzig"" to ""Gdańsk"" without using the link inspector the result will be
+> ""[[Danzig|Gdańsk]]"".
+
+I get the opposite of this ([[Gdańsk|Danzig]]), but this bug still feels valid to me.",1400106672,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-m7leu4xitl3lklt5rrdg,task_subcomment,NA
+"VisualEditor: If a link that doesn't have a pipe is changed, the link target remains","... Just an explanation for my guess: In the source editor changing [[Nasik]] to [[Nashik]] requires the adding one 'h'. In the current version of VisualEditor it requires adding one 'h', opening the link editor and adding the 'h' there, too.",1385368772,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-m7leu4xitl3lklt5rrdg,task_subcomment,NA
+VisualEditor:A Return character appears when a text is followed by <math> code,"screenshot
+
+Steps to reproduce:
+
+1.Create a page
+2.Type something
+3.From the ""Edit Source"" option add the following after the text:
+<math>\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}
+
+
+</math>
+
+4.Save the page
+5.Click on Edit-beta again
+
+
+Observed Result:
+A Return character appears after the text in edit mode
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12681}",1385162100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hxm7dylzsr7cb36xgt4j,task_description,resolved
+VisualEditor:A Return character appears when a text is followed by <math> code,"
+
+*** This bug has been marked as a duplicate of bug 48290 ***",1415882814,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hxm7dylzsr7cb36xgt4j,task_subcomment,NA
+VisualEditor:A Return character appears when a text is followed by <math> code,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/text_then_math?veaction=edit",1385162188,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hxm7dylzsr7cb36xgt4j,task_subcomment,NA
+VisualEditor:After adding a reference the cursor jumps to the beginning of the first line of the page,"Steps to reproduce:
+
+1.Create a page with a long content first
+
+2.Towards the end add references
+
+Observed Result:
+
+Every time user adds a reference it takes him to the beginning of the article making him scroll down all the way down to get to where he was adding a reference
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385149560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b2the5znff3yi5iqewab,task_description,resolved
+VisualEditor:After adding a reference the cursor jumps to the beginning of the first line of the page,"
+
+*** This bug has been marked as a duplicate of bug 58090 ***",1386805579,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b2the5znff3yi5iqewab,task_subcomment,NA
+VisualEditor:After adding a reference the cursor jumps to the beginning of the first line of the page,Related to 57271?,1385406168,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-b2the5znff3yi5iqewab,task_subcomment,NA
+VisualEditor:After adding a reference the cursor jumps to the beginning of the first line of the page,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:
+https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/ref_not_editable",1385149578,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b2the5znff3yi5iqewab,task_subcomment,NA
+VisualEditor: unnamed links can not be edited,"The two links at the end of the third line are external unnamed links.
+VE does not allow editing them.
+The markup guide for en.wp says these links are ""Only used within article body
+for footnotes"", but of course they might be used also outside ns0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Elitre_%28WMF%29/sandbox&veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57418
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57420",1385123880,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-tjb4bkjfszkwoz7qktjo,task_description,resolved
+VisualEditor: unnamed links can not be edited,"Merging with bug 53505.
+
+*** This bug has been marked as a duplicate of bug 53505 ***",1385489060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tjb4bkjfszkwoz7qktjo,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,"Go to :https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/table_test
+
+See that in the VE mode and Edit source mode the reference list is showing up but in Read mode there is no reference list.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385077680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kgksabqabkax4kkg7izy,task_description,declined
+VisualEditor:References list does not appear when it follows a table in a page.,Seems to be because there are two reference list invocations on the page. The fact that the read mode only displays the first seems to be by design.,1437707657,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,Changing the summary to a more generalized one: References list does not appear when it follows a table in a page.,1385078540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,"Found the  the steps to reproduce:
+
+1.Create a page
+2.Add some references
+3.Add a table into it with the following from the edit source mode:
+{| border=""2""
+|+ [[my table]]
+
+|-
+|
+# first cell<ref>reference</ref>
+|
+# [[second cell]]
+|
+* third cell
+|-
+|1[[File:Tibouchina urvilleana flower ja.jpg|thumb|150x150px|{{Like resume}}]]
+|2{{Like}}
+|3<references />
+
+|}
+
+4.Add references list at the end of the page
+5.Save the page
+
+Observed Result:
+The references list does not appear in the view mode.",1385078395,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,"Created attachment 13870
+In the read mode
+
+**Attached**: {F12503}",1385077817,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,"Created attachment 13869
+In the VE mode
+
+**Attached**: {F12502}",1385077727,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+"VisualEditor:VE renders a table with border=""0"" as border=""1""","In read mode
+
+Steps to reproduce:
+
+1.Click on the Edit source.
+
+2. Type the following:
+
+table test title
+
+{| border=""0""
+|+ my table
+
+|-
+|first cell 
+|second cell 
+|third cell
+|-
+|1
+|2
+|3
+
+|}
+
+3.Save the page
+4.View the page in read mode
+5.Open the page in VE mode.
+
+Observed Result:
+There is not border for the table in read mode but when you open the page in VE mode it renders the table with a border=1.
+
+See he screenshots attached.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/table_test
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12479}",1385062260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-twgftigrpz6uckwjelnt,task_description,resolved
+"VisualEditor:VE renders a table with border=""0"" as border=""1""","
+
+*** This bug has been marked as a duplicate of bug 57295 ***",1385123360,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-twgftigrpz6uckwjelnt,task_subcomment,NA
+"VisualEditor:VE renders a table with border=""0"" as border=""1""","Created attachment 13864
+In VE mode
+
+**Attached**: {F12480}",1385062312,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-twgftigrpz6uckwjelnt,task_subcomment,NA
+VisualEditor:References resulting from repeated citation cannot be edited in the VE mode  after changing the ref name from :0,"Steps to reproduce:
+
+1.Click on the Edit mode
+2.Add a reference 
+3.Add the same reference 5 times in that page
+4.Save the page
+5.Go to Edit Source
+
+Observed Result:
+I think, due to repeated citation of the same reference with no defined name ,a name with value (:0) is added to the <ref> tags for all the references that is using the same reference
+
+But, if user intends to change the name of the original reference to a more meaningful name for future reference purpose he might do the following steps
+
+6. Change the name value from "":0"" to ""bbc"" for the first references
+7.Close the editor 
+8.Click on Edit now.
+9.Hover over other references which were using same references
+
+Observed Result:
+A message shows up this reference cannot be edited in the VE ,can only be edited in edit source mode.
+
+Can this message be more precise to point where the problem is?For example in the read mode it says ""Invalid <ref> tag; no text was provided for refs named :0""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385059320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lhb7q2iod46plkygoni4,task_description,resolved
+VisualEditor:References resulting from repeated citation cannot be edited in the VE mode  after changing the ref name from :0,"Not VE-specific, but a larger issue with how Cite.php ""works"" (hint: it doesn't).
+
+*** This bug has been marked as a duplicate of bug 18103 ***",1398114542,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lhb7q2iod46plkygoni4,task_subcomment,NA
+VisualEditor:References resulting from repeated citation cannot be edited in the VE mode  after changing the ref name from :0,"Created attachment 13861
+Screenshot of the error
+
+**Attached**: {F12468}",1385059523,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lhb7q2iod46plkygoni4,task_subcomment,NA
+Enhance hooks.rb in mediawiki-selenium gem to warn when BROWSER_LABEL is undefined,"**Author:** `jhall`
+
+**Description:**
+This is a follow-up to this recent change to the VisualEditor browser tests:
+
+https://gerrit.wikimedia.org/r/#/c/96793/
+
+Since a user may neglect to explicitly export a value for the BROWSER_LABEL environment variable, it might be a good idea to enhance hooks.rb for the mediawiki-selenium RubyGem to add a warning where that value is undefined.  
+
+The danger is that where the BROWSER_LABEL value is undefined, individual tests will not target the intended wiki pages, since those pages are expected to have the BROWSER_LABEL string included in the page URL.
+
+The hooks.rb file already issues similar warnings for the MEDIAWIKI_USER and MEDIAWIKI_PASSWORD variables in the ""Before('@login')"" method:
+
+https://github.com/wikimedia/mediawiki-selenium/blob/master/lib/mediawiki/selenium/hooks.rb
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385059020,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rutprbjwmdkgbr5b3uoo,task_description,invalid
+Enhance hooks.rb in mediawiki-selenium gem to warn when BROWSER_LABEL is undefined,"**jhall** wrote:
+
+This task is invalid now that warnings for undefined BROWSER, PLATFORM and VERSION environment variable values have been added to env.rb in the most recent versions of the mediawiki_selenium Rubygem, so closing this ticket as INVALID.",1393019466,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rutprbjwmdkgbr5b3uoo,task_subcomment,NA
+VisualEditor: Pawn appears near copy/pasted template,"This happens in FF (both skins).
+1. https://fr.wikipedia.org/wiki/Utilisateur:Elitre_%28WMF%29/Prove?veaction=edit
+2. reach the Sources section.
+3. copy the (en) template and paste it before ""Franca C"".
+4. hit space.
+
+A pawn appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385049060,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nbvnewtd4mrfr4a4ytce,task_description,resolved
+VisualEditor: Pawn appears near copy/pasted template,This appears to be long-fixed.,1406598703,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nbvnewtd4mrfr4a4ytce,task_subcomment,NA
+VisualEditor: Pawn appears near copy/pasted template,https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_(WMF)/Prove&oldid=98530979,1390240856,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nbvnewtd4mrfr4a4ytce,task_subcomment,NA
+[Regression?] VisualEditor: Still get a pawn when select-all->replace in Firefox,"Intention:
+I want to blank a page, and add new contents.
+
+Steps to Reproduce:
+Since this does not seem to happen on each page, I'll add the steps I followed to reproduce it.
+
+1. VEdit https://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE with Firefox and Monobook. 
+2. Right-click, select all, delete.
+3. Click to re-gain focus.
+4. Type something. A pawn will appear.
+5. Review your changes. Notice that not all of the contents were actually deleted after #2. Also notice that some or all of your newly added text might be missing. 
+6. Save the page. Your text (most or all of it) shouldn't be there. What you have are random chunks of old text. And your pawn :)
+
+
+
+Actual Results:  
+While reproducing, the following also occurred to me:
+1. After blanking, a weird cursor (like an arrow pointing up) appeared at the beginning of the line. After typing for a while, Back Space and the keyboard navigation arrows wouldn't work. 
+2. When VEditing the page created after #6, blanking it and then clicking on a line to make the cursor appear resulted in fragments of words appearing. If I tried to type, I'd also get rapidly multiplying pawns.
+(All these behaviors are not new to me.)   
+
+Expected Results:  
+I expected the page to be really blank, and pawn-less :)
+
+Reproducible: Sometimes
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42404",1385044860,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-32bj4xsfxzl66kfabfpq,task_description,resolved
+[Regression?] VisualEditor: Still get a pawn when select-all->replace in Firefox,"Up-merging to bug 64917 (whoops)
+
+*** This bug has been marked as a duplicate of bug 64917 ***",1399642730,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-32bj4xsfxzl66kfabfpq,task_subcomment,NA
+[Regression?] VisualEditor: Still get a pawn when select-all->replace in Firefox,"Original report at en.wp:
+<<If I go to Plato, enter VE, right click, select all, and then press some letter or number, a pawn will appear. Also, if I review changes, there is still material left is the ""your text"" section. Firefox 25.0.1; Windows 7 Professional SP1 64-bit; Monobook skin. --Atethnekos>>.",1385045081,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-32bj4xsfxzl66kfabfpq,task_subcomment,NA
+VisualEditor: Save page button does not work if user includes reflist template while there is already reference list,"Steps to reproduce:
+
+1.Click on the edit button
+2.Add some content in the page
+2.Add some references in the page
+3.Add references list from More>References list.
+4.Now Go to More>Transclusion
+5.Add the template reflist
+6.Click on the ""Save Page"" button
+
+Observed Result:
+The save page button does not work ,user had to cancel this edit session and re-work again on the editor
+
+There is no js error for this in the console.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/reference_list_and_reflist_both?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384989060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-prrrskdzk7yoo3hn4dt2,task_description,resolved
+VisualEditor: Save page button does not work if user includes reflist template while there is already reference list,"It is possible to save correctly now. It's still //not// possible to have a page display more than one `<references />` block for the same ref group, but that seems to be by design.",1437707348,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-prrrskdzk7yoo3hn4dt2,task_subcomment,NA
+VisualEditor: Save page button does not work if user includes reflist template while there is already reference list,I think its better if either we do not permit them to include both and explicitly notify them or both gets added properly.,1384989788,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-prrrskdzk7yoo3hn4dt2,task_subcomment,NA
+VisualEditor: Save page button does not work if user includes reflist template while there is already reference list,"However the issue is not same when user does the vice versa.That is, if he had reflist template before and adds again a references list it does get added in the page.But,the later one does not show up in the read mode but on VE edit mode and on edit source mode where both the {{Reflist}} and <references /> are present",1384989303,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-prrrskdzk7yoo3hn4dt2,task_subcomment,NA
+VisualEditor:Cannot save the content of a page after an idle time on the open editor,"Steps to reproduce:
+
+1.Open the VE editor for a page.
+2.Make some edit
+3.Leave the editor open for a long time (more than an hour)
+4.Come back after that idle time and click the button ""Save Page""
+
+
+Observed Result:
+The content does not get saved.Shows a js error in the console
+
+Uncaught TypeError: Cannot read property 'saveRetries' of undefined
+(anonymous function)
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+(anonymous function)
+fire load.php:12
+self.fireWith load.php:14
+done load.php:119
+callback
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384970580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ooqyq4axuutnv7pchwcb,task_description,resolved
+VisualEditor:Cannot save the content of a page after an idle time on the open editor,This [[https://en.wikipedia.org/w/index.php?title=User%3ANeil_P._Quinn-WMF%2Fsandbox&type=revision&diff=662373500&oldid=662187275|now seems to work]]!,1431646757,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-ooqyq4axuutnv7pchwcb,task_subcomment,NA
+VisualEditor:Cannot save the content of a page after an idle time on the open editor,"I am curious about how different this is from the common behavior with the wikitext editor, which will usually display a message like ""Sorry! We could not process your edit due to a loss of session data. Please try again. If it still doesn't work, try logging out and logging back in."" (not sure if this is the actual one though) and which ""fixes"" itself if you just retry to save.",1385402139,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ooqyq4axuutnv7pchwcb,task_subcomment,NA
+VisualEditor:Cannot save the content of a page after an idle time on the open editor,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test_reference",1384970640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ooqyq4axuutnv7pchwcb,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,"While testing on production , I found that when I select a specific template all the related parameters show up on the dialog box.
+However, in test 2 and beta I do not see any related parameter to select.
+Can those parameters be included on these environment, so that the testing can be done on it in these environment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384970040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ufkgro7khm6qaqk6mboe,task_description,invalid
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,Manual importing of the TemplateData is needed for this.,1394502019,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,"I might be missing something obvious here but,
+the last change to the Taxobox template on test 2 was made 7 years ago, I think, so even if it worked properly, and I didn't test this, I think it's missing TemplateData (https://www.mediawiki.org/wiki/VisualEditor/Portal/TemplateData ).
+If you want to use the same templates you use on en.wp, for example,
+you'd need to import them and their documentation, I guess.",1385399847,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,An example page for editing taxobox could be :https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/table_test?veaction=edit,1385071956,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,"What would be a link to edit e.g. taxobox with VE ""on production""?",1385067331,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,"I tried the following templates:
+reflist
+citeweb
+taxobox",1384970190,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the edit button
+2.Add several references in the page
+3.Add a template reflist onto it.
+4.Insert an image
+5.Go to the Media Settings for that image and add a reference and also add the template reflist to the image
+6.Save the page
+
+Observed Result:
+
+The reflist that was created for the page disappears and the error appears ""Cite error: There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page)""
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12295}",1384913460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-32vbq6qkhx3wngjcnodn,task_description,duplicate
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"(Cool, I never used that template more than once on a page. Now I know it can be done :) https://en.wikipedia.org/wiki/Template:Reflist#Multiple_uses )",1385419366,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"
+
+https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/reflist_on_a_image
+(In reply to comment #2)
+> Some more issues with this action:
+> 
+> 1. After adding a reflist to the image the whole order of the references in
+> that page gets messed up.
+> 
+> The reference to the image becomes reference with footnote [1] and in the
+> page
+> the order of the reference got changed from [1],[2],[3]  to [2],[3],[4].
+> and the reference of the image gets modified to the [1] reference of the
+> document. 
+> 
+> 
+> 
+> 2. Now if you switch to edit source, you will see since the reference in the
+> image is taking the value of first reference of the document as a repetitive
+> reference, the [1] reference of the document gets assigned with ref name=
+> "":1"" 
+> 
+> But still there is another on the page:Cite error: The named reference :1 was
+> invoked but never defined (see the help page).",1384915850,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Created attachment 13844
+flower.com got changed to facebook.com
+
+**Attached**: {F12298}",1384915704,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Created attachment 13843
+the changed order
+
+**Attached**: {F12297}",1384915617,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Created attachment 13842
+The initial order
+
+**Attached**: {F12296}",1384915579,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Some more issues with this action:
+
+1. After adding a reflist to the image the whole order of the references in that page gets messed up.
+
+The reference to the image becomes reference with footnote [1] and in the page the order of the reference got changed from [1],[2],[3]  to [2],[3],[4].
+and the reference of the image gets modified to the [1] reference of the document. 
+
+
+
+2. Now if you switch to edit source, you will see since the reference in the image is taking the value of first reference of the document as a repetitive reference, the [1] reference of the document gets assigned with ref name= "":1"" 
+
+But still there is another on the page:Cite error: The named reference :1 was invoked but never defined (see the help page).",1384915131,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/reference_on_a_image,1384913965,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+export REUSE_BROWSER for 4 VisualEditor tests in Jenkins builds,"As of today we have four tests that use the @make_selectable_line and @edit_user_page hooks, and that pass with or without the REUSE_BROWSER env variable.  
+
+I suggest we set that env variable REUSE_BROWSER=true for 
+
+bullets.feature
+indent_outdent.feature
+headings.feature
+general_markup.feature
+
+This will save a significant amount of time for each of the four VE builds, since the four tests will log in only four times per build instead of a total of twenty-one times without REUSE_BROWSER=true. 
+
+Note that setting REUSE_BROWSER=true does not affect our ability to analyze test failures.  For example, see the failure messages below for a run of the bullets test: 
+
+----
+
+timed out after 10 seconds (Watir::Wait::TimeoutError)
+./features/step_definitions/bullets_steps.rb:26:in `block (2 levels) in <top (required)>'
+./features/step_definitions/bullets_steps.rb:25:in `/^a \# is added in front of input string in the diff view$/'
+features/bullets.feature:8:in `Then a <character> is added in front of input string in the diff view'
+
+timed out after 10 seconds (Watir::Wait::TimeoutError)
+./features/step_definitions/bullets_steps.rb:39:in `block (2 levels) in <top (required)>'
+./features/step_definitions/bullets_steps.rb:38:in `/^a \* is added in front of input string in the diff view$/'
+features/bullets.feature:8:in `Then a <character> is added in front of input string in the diff view'
+
+timed out after 10 seconds (Watir::Wait::TimeoutError)
+./features/step_definitions/bullets_steps.rb:52:in `block (2 levels) in <top (required)>'
+./features/step_definitions/bullets_steps.rb:51:in `/^a \#\# is added in front of input string in the diff view$/'
+features/bullets.feature:21:in `Then a <character> is added in front of input string in the diff view'
+
+timed out after 10 seconds (Watir::Wait::TimeoutError)
+./features/step_definitions/bullets_steps.rb:61:in `block (2 levels) in <top (required)>'
+./features/step_definitions/bullets_steps.rb:60:in `/^a \*\* is added in front of input string in the diff view$/'
+features/bullets.feature:21:in `Then a <character> is added in front of input string in the diff view'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384899720,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-6hbiyaynilweesovh3xs,task_description,declined
+export REUSE_BROWSER for 4 VisualEditor tests in Jenkins builds,As far as I remember we have agreed this will not be implemented. Please reopen if I misunderstood.,1386000360,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-6hbiyaynilweesovh3xs,task_subcomment,NA
+export REUSE_BROWSER for 4 VisualEditor tests in Jenkins builds,"I am **strongly against** reusing browsers between scenarios, for various reasons. If speed is our problem, we should run the tests in parallel.",1384950098,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-6hbiyaynilweesovh3xs,task_subcomment,NA
+"VisualEditor:""Cannot open another window while another one is active"" error appears while attempting to save the page after deleting the transclusion ""reflist""","Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the edit button
+2.Add few references to the page
+3.Go to more>Transclusion
+4.Add the template reflist
+5.Delete this template
+6.An icon still appears for that template click on it
+7.When the dialog for that template appears cross it out.
+8.Click the button ""Save Page""
+
+Observed Result:
+The Save page button does not work.User cannot save the edit made so far on the page. It requires to cancel the edit and reopen the editor.
+
+The js error that appears on the console is:
+Uncaught Error: Cannot open another window while another one is active
+
+See the screensshot attached
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/test_reference?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12289}",1384897440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-plwpcaqphz3xxe7n4naa,task_description,declined
+"VisualEditor:""Cannot open another window while another one is active"" error appears while attempting to save the page after deleting the transclusion ""reflist""",Think this was fixed in the re-work of how we attach to transclusions? WFM in my testing.,1393528386,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-plwpcaqphz3xxe7n4naa,task_subcomment,NA
+"VisualEditor:""Cannot open another window while another one is active"" error appears while attempting to save the page after deleting the transclusion ""reflist""",*** Bug 57204 has been marked as a duplicate of this bug. ***,1393528338,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-plwpcaqphz3xxe7n4naa,task_subcomment,NA
+"VisualEditor:""Cannot open another window while another one is active"" error appears while attempting to save the page after deleting the transclusion ""reflist""",Possibly a duplicate of bug 57204?,1385419740,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-plwpcaqphz3xxe7n4naa,task_subcomment,NA
+"VisualEditor:Template ""reflist"" does not get added immediately on the page","No indication if there is any reflist added or not
+
+Steps to reproduce:
+
+1.Click  on the edit button
+2.Add few references to the page
+3.Now click on the More>Transclusion
+4.Select the template ""reflist"" and add it to the page
+
+Observed Result:
+The reflist template does not get added rather an icon for the template shows up on the page.
+If you move your cursor that icon disappears too making user confused whether they have added any reflist or not.
+
+See the screenshots attached.
+
+Test Environment: Production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/test_reference?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12287}",1384895040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5wto4e4bokkzs7zmbjod,task_description,duplicate
+"VisualEditor:Template ""reflist"" does not get added immediately on the page","Well, so much for not using the dedicated References list button :p
+
+Now seriously:
+with my PC/Win 7 and Chrome (both skins), I can't even see the template icon.
+Under FF instead I see it, and at its left there's this character ^ in grey.
+In both cases, the blinking cursor is now at the top of the page:
+if I type something, the text will be added on that line (in Chrome) or where the Reflist is supposed to be (in FF: the icon is now gone).",1385405980,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5wto4e4bokkzs7zmbjod,task_subcomment,NA
+"VisualEditor:Template ""reflist"" does not get added immediately on the page","Created attachment 13837
+template icon
+
+**Attached**: {F12288}",1384895082,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5wto4e4bokkzs7zmbjod,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the edit button
+2.Select a text or place your cursor in a blank space
+3.Go to More>Latex/hieroglyphics option
+
+Observed Result:
+None of the inspectors open up .More over ,in one attempt they opened overlapping with each other and after that I could not close any of them.I had to cancel my editing and reopen the editor to get rid of them
+
+It gives the following script error in the console:
+Uncaught TypeError: Cannot read property '$element' of null
+
+
+
+see the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12278}",1384891380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_description,resolved
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,This is fixed and verified too.,1386025050,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"(In reply to comment #5)
+> should this block the next deployment?
+
+James: ping?",1385980317,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"
+should this block the next deployment?",1385503659,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"In production the behavior is more annoying, as it opens the Latex inspector after a while and then it keeps opening everytime I select a text.And it does not go away by changing the focus/ crossing out the dialog.User have to cancel the edit and then re-open the editor.",1385490596,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,It is my understanding that this is related to James' second answer at https://www.mediawiki.org/wiki/Talk:VisualEditor/Beta_Features/Formulae#Bugs_&_compatibility_issues.,1385401860,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"Some more insight to the case where it opened.
+
+1.Keep the firbug or developers tool closed
+2.Click on Latex and/or hieroglyphics option
+3.Open the firebug/developer tool
+
+Observed Result:
+
+Both the inspectors open overlapping with each other.However if you type something inside it and try to close it , it does not let you do that",1385058457,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Test Page:https://test2.wikipedia.org/w/index.php?title=Verify_56274&veaction=edit",1384891692,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:Quickly switching between Read and Edit tab gives a JS error,"Steps to reproduce:
+
+1.Click the button Edit
+2.Quickly switch to read tab and again switch back to edit button
+
+Observed Result:
+An error appears in the console
+Uncaught TypeError: Cannot call method 'getModel' of null load.php:37
+ve.init.mw.ViewPageTarget.updateToolbarSaveButtonState load.php:37
+(anonymous function) load.php:43
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+(anonymous function)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384887120,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xs35ywfjwn7iygqwhlqh,task_description,resolved
+VisualEditor:Quickly switching between Read and Edit tab gives a JS error,"
+
+*** This bug has been marked as a duplicate of bug 51546 ***",1395360091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xs35ywfjwn7iygqwhlqh,task_subcomment,NA
+VisualEditor:Quickly switching between Read and Edit tab gives a JS error,"Also got these error once :
+
+Uncaught RangeError: ""Maximum call stack size exceeded""
+
+Uncaught TypeError:Object #<Object> has no method 'abort'",1384887846,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xs35ywfjwn7iygqwhlqh,task_subcomment,NA
+VisualEditor:Quickly switching between Read and Edit tab gives a JS error,"Test Environment:Production
+Test Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/test_reference?veaction=edit
+OS:MAC OS X 10.8.5
+Browser:Chrome 26.0.1410.65",1384887208,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xs35ywfjwn7iygqwhlqh,task_subcomment,NA
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","Intention:
+Edit a page containing a gallery.  The gallery contains <ref> citations.
+
+Steps to Reproduce:
+1. Open the page in VisualEditor.
+2. Notice the big red errors inside each gallery that contains a <ref> citation.
+
+
+Actual Results:  
+Big red errors are present at the bottom of each gallery that contains a <ref> citation.  Depending on whether the ref is part of a group, these are the two errors I saw:
+
+There are <ref group=$1> tags on this page, but the references will not show without a {{reflist|group=$1}} template (see the help page).
+
+There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page).
+
+
+Expected Results:  
+That VisualEditor would not produce an error.  (There were proper {{reflist}} templates at the bottom of the page.)
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384817640,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-htmipabmc3qfaiznrebo,task_description,resolved
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","This has been fixed, sort of:  Instead of a big red error, it now puts a references block at the end of the gallery (re-starting the numbering, and including only refs from the gallery).",1414857389,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-htmipabmc3qfaiznrebo,task_subcomment,NA
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","I don't think this is valid any more, is it?",1414811249,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-htmipabmc3qfaiznrebo,task_subcomment,NA
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","Also, as seen by editing https://en.wikipedia.org/w/index.php?oldid=596381198 you cannot re-use any references that are within a gallery block.",1392925622,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-htmipabmc3qfaiznrebo,task_subcomment,NA
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","If you change a caption in the gallery so that it contains a {{reflist}}, then VisualEditor displays the citations within the gallery (under the green can't-edit-this hash), and this error is not present.",1384817743,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-htmipabmc3qfaiznrebo,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"Trying to type a word in brackets might lead to the disappearing of the opening brackets, no wikitext warning appears and no nowikis are added.
+
+Happened to me twice in sandboxes,
+see https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/tests&oldid=185158 and https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=62542564&oldid=62363821 ;
+it didn't happen in https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=582254513&oldid=581339890 and I also don't seem able to get this bug while VEditing ns0.
+All tests under Chrome and Vector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53856",1384805580,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eja43n7xny5lbdanmj4p,task_description,declined
+VisualEditor: opening square brackets can sometimes disappear,"Also happening at https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=203117 when trying to add a new point under ""simpler"".",1414156189,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"Happening again.
+In https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_(WMF)/Prove2&oldid=108482122 I tried to start a new line precisely under the first one (the one ending in ""sdas"") with a word in brackets to see if it triggered the warning.
+After typing the opening square brackets, these disappear when I start typing a word.",1414155292,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,Closing provisionally as WORKSFORME.,1394677011,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,Is this still occurring?,1393642241,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,I still can. VE hates me :(,1385498718,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,I can't reproduce at https://en.wikipedia.org/wiki/User:Elitre_(WMF)/sandbox?veaction=edit&useskin=monobook with a hard-refresh. :-(,1385496350,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"It doesn't happen in FF, but it's still there if I switch to Monobook in Chrome.",1385122698,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"Sorry :/
+Chrome, Vector, Win7:
+
+https://en.wikipedia.org/wiki/User:Elitre_(WMF)/sandbox?veaction=edit
+Cursor right under the sandbox template and above the article text,
+I start typing brackets and they disappear.",1385122418,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"I guess we'll never know, since right now it seems to work again just fine. Good for us.",1384880909,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,I can't reproduce this after a few dozen tries. Can you give more details about how it happens? Is it on new pages only? Existing pages? Existing pages when you're editing an old revision? At the start of the document? Everywhere? Etc.,1384841983,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"Yeah, it's probably Chrome.",1384814747,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"I've been unable to replicate this in Mac OS 10.7.5/Safari 6/Vector or in Mac OS 10.7.5/Firefox 25.0.1/Vector, in either userspace or the mainspace.",1384813672,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"Environment:test 2
+SamplePage:
+OS:MAC OS X 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384797420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_description,resolved
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),*** Bug 57194 has been marked as a duplicate of this bug. ***,1385420317,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"Verified this issue.
+Created a separate ticket for idle time issue:https://bugzilla.wikimedia.org/show_bug.cgi?id=57314",1384970683,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"(In reply to comment #11)
+> After the fix,I am not getting that error message.
+> However, after keeping the editor for a long time and then attempting to save
+> the content gives the following js error.
+> 
+> Uncaught TypeError: Cannot read property 'saveRetries' of undefined
+> (anonymous function)
+> fire load.php:12
+> self.fireWith load.php:14
+> self.fire load.php:14
+> (anonymous function)
+> fire load.php:12
+> self.fireWith load.php:14
+> done load.php:119
+> callback
+> 
+> Assuming it as a separate issue?
+
+Yes, that's distinct; marking this as FIXED, but please re-open if it re-occurs.",1384841530,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"After keeping the editor open for long time*(In reply to comment #11)
+> After the fix,I am not getting that error message.
+> However, after keeping the editor for a long time and then attempting to save
+> the content gives the following js error.
+> 
+> Uncaught TypeError: Cannot read property 'saveRetries' of undefined
+> (anonymous function)
+> fire load.php:12
+> self.fireWith load.php:14
+> self.fire load.php:14
+> (anonymous function)
+> fire load.php:12
+> self.fireWith load.php:14
+> done load.php:119
+> callback
+> 
+> Assuming it as a separate issue?",1384833671,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"After the fix,I am not getting that error message.
+However, after keeping the editor for a long time and then attempting to save the content gives the following js error.
+
+Uncaught TypeError: Cannot read property 'saveRetries' of undefined
+(anonymous function)
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+(anonymous function)
+fire load.php:12
+self.fireWith load.php:14
+done load.php:119
+callback
+
+Assuming it as a separate issue?",1384833601,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),I just got this error on production too.,1384817063,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"I got the Parsoid server message as well a few minutes ago on that page.
+Then I tried again (from Opera, unlogged, then from FF and Chrome while logged in) and it just saved. :/",1384816838,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"To the best of my knowledge, test2 and mediawiki.org are using the production Parsoid instance.  Please let us know if that is not the case.",1384816794,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"That might be a different issue, possibly with the parsoid service setup used by test2. AFAIK it is not using the Parsoid production cluster. The QA folks have been working on this recently and would know more.",1384816272,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),Happened again on test2 . No errors in the JS console.On the dialog box there was a message:Error: Error contacting the Parsoid server,1384814682,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),I am not getting this issue anymore.The new page creation and content saving both are working now.,1384812957,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),Any errors in the JS console?,1384812600,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),Sample Page: https://test2.wikipedia.org/w/index.php?title=Verify_56274&veaction=edit,1384798456,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"Created attachment 13825
+Screenshot of the error
+
+**Attached**: {F12136}",1384798087,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"Steps to reproduce:
+
+1.Attempt to modify any content on any page in test2 environment .
+2.Click the Save button 
+
+Observed Result:
+The spinner for saving continues for a long time but the content does not get saved .And ""An error occurred"" message appeared on the dialogue box
+See the screenshot attached
+
+Browser:Chrome Version 26.0.1410.65
+and FF 25",1384797670,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor:Add the tags to wikitext detection regex to show wikimarkup warning,"When a tag <ref> is inserted in visual editor it shows a wikitext warning to user but there are few more tags which I think will be good to be added to the wikitext detection regex such as 
+<s>
+<math>
+<poem>
+
+None of them triggers wikitext warning right now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384562700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qgpnwx66d3gjnes6vhh6,task_description,declined
+VisualEditor:Add the tags to wikitext detection regex to show wikimarkup warning,WONTFIX. The test is not intended to catch every possible mistaken attempted insertion of HTML or wikitext.,1384841786,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qgpnwx66d3gjnes6vhh6,task_subcomment,NA
+"VisualEditor:""ULS: Unknown language doi. ULS: Unknown language fonipa"" appears upon typing the on the ""Search Box""","Steps to reproduce:
+
+1.Load any page on test2
+2.Take your cursor to the ""Search Box"" and attempt to type something in it.
+3.Observe Console>Errors from Developer tool
+
+Observed Result :
+ULS: Unknown language doi.
+ULS: Unknown language fonipa
+
+Appears on this section.
+
+Note:The selected language is English in this case
+
+Not sure if it is expected or not.Close the bug if it is not an issue. 
+
+Test Environment:
+Browser:Chrome 26.0.1410.65
+OS:MAC OS 10.8.5
+Test Page:https://test2.wikipedia.org/wiki/Verify_56274
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384558620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iuv45mcdfmqdyf3lof4l,task_description,resolved
+"VisualEditor:""ULS: Unknown language doi. ULS: Unknown language fonipa"" appears upon typing the on the ""Search Box""","Not related to VisualEditor itself, ULS spams this to the console on every page everywhere.
+
+*** This bug has been marked as a duplicate of bug 45047 ***",1384558760,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-iuv45mcdfmqdyf3lof4l,task_subcomment,NA
+clean up obsolete VE API dependency,"AIUI, Flow no longer uses VE's API to convert from/to wikitext/html, it posts API requests to Parsoid's URL if its available.
+
+I think this means:
+* Hooks.php onSetupAfterCache() is obsolete, (and has been since we occupied namespaces?!),
+* Flow should have its own parameters $wgFlowParsoidURL, $wgFlowParsoidPrefix, $wgFlowParsoidTimeout which in comments can default to the $wgVisualEditor* values.
+* Clean up obsolete comments in ParsoidUtils.php
+
+This will make it clearer that Flow can work with Parsoid even if the VisualEditor extension isn't installed.
+
+(Is the Parsoid extension even required on MediaWiki servers in a cluster arrangement where only one machine runs the Parsoid nodejs service?)  I guess yes in order to ""trigger Parsoid cache updates"".)
+
+--------------------------
+**Version**: master
+**Severity**: minor",1384545240,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-uftjcaqg7wftryrkpsp5,task_description,resolved
+clean up obsolete VE API dependency,"Change 95605 merged by jenkins-bot:
+(bug 57111)  clean up obsolete VE API dependency
+
+https://gerrit.wikimedia.org/r/95605",1384888882,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uftjcaqg7wftryrkpsp5,task_subcomment,NA
+clean up obsolete VE API dependency,"Change 95605 had a related patch set uploaded by Matthias Mullie:
+(bug 57111)  clean up obsolete VE API dependency
+
+https://gerrit.wikimedia.org/r/95605",1384875148,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uftjcaqg7wftryrkpsp5,task_subcomment,NA
+clean up obsolete VE API dependency,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/470, but people from the community are welcome to contribute here and in Gerrit.",1384761811,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-uftjcaqg7wftryrkpsp5,task_subcomment,NA
+clean up obsolete VE API dependency,"Coincidentally, I had been working on that yesterday: https://gerrit.wikimedia.org/r/#/c/95605/
+
+onSetupAfterCache still needs to be removed in there, though.",1384593024,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-uftjcaqg7wftryrkpsp5,task_subcomment,NA
+VisualEditor:Edit|Edit Source links are appearing on a blank heading,"edit/edit source option on blank space
+
+Steps to reproduce:
+
+1.Click on the Edit button for a page
+2.Select the option sub-heading 1 in a blank space
+3.Click the button ""Save Page""
+
+Observed Result:
+The Edit/Edit Source link appears in the blank space
+
+Browser:Chrome
+Page:Any
+Environment:test 2
+
+see the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12697}",1384382100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6grklf7gpa6ipg5o6y3,task_description,resolved
+VisualEditor:Edit|Edit Source links are appearing on a blank heading,This now seems to be fixed (on test2 using Chrome).,1431471672,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-c6grklf7gpa6ipg5o6y3,task_subcomment,NA
+"When changing image type, the type is added to the wikitext instead of replacing the old one","This came up while working on the new Media dialog in VisualEditor. When changing a block image type, for instance from 'thumb' to 'frameless', the new type is added onto the wikitext instead of replacing the old type tag.
+
+Original wikitext:
+[[File:image.png|thumb|right|caption goes here|466x466px]]
+
+After changing the type of the image to frameless (including all style changes and type attribute) the resulting post-save wikitext is this:
+
+[[File:image.png|thumb|right|caption goes here|466x466px|frameless]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384290060,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-tzaqvebpmuva7a34ejvl,task_description,resolved
+"When changing image type, the type is added to the wikitext instead of replacing the old one","
+
+*** This bug has been marked as a duplicate of bug 48665 ***",1384299690,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-tzaqvebpmuva7a34ejvl,task_subcomment,NA
+Changing image alignment attribute adds the alignment instead of replacing it in wikitext,"This came up while working on the new media dialog in VisualEditor. When there's a change in an image align attribute, the resulting wikitext adds the new alignment keyword instead of replacing the original.
+
+Initial wikitext:
+[[File:image.png|thumb|right|caption goes here|466x466px]]
+
+After changing the image to right alignment (removing tright and replacing with tleft, and replacing the align attribute in the image object) -- the resulting wikitext post save is this:
+
+[[File:image.png|thumb|right|caption goes here|466x466px|left]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384289880,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-6jr33finz32lgguug7oy,task_description,resolved
+Changing image alignment attribute adds the alignment instead of replacing it in wikitext,"
+
+*** This bug has been marked as a duplicate of bug 48665 ***",1384299493,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-6jr33finz32lgguug7oy,task_subcomment,NA
+"VisualEditor: Template is not deselected when ""clicking out"" of it in certain circumstances","1. Edit [[mw:Manual:$wgEdititis]] in VE
+2. Click the ""Language"" template at the bottom, to select it
+3. Click in the blank space to the right of the word ""places""
+
+Notice that the template is (correctly) deselected.
+
+4. Do steps 2 and 3 again
+
+The template is not deselected this time. Even though the cursor is flashing in the right place (implying deselection), any typing will overwrite the template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1384236840,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-t4dsq6rpgyk5vhbxgywu,task_description,declined
+"VisualEditor: Template is not deselected when ""clicking out"" of it in certain circumstances","Doesn't matter, seems to work now.",1393633116,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-t4dsq6rpgyk5vhbxgywu,task_subcomment,NA
+"VisualEditor: Template is not deselected when ""clicking out"" of it in certain circumstances",Seems to work for me now. Setting unconfirmed so a VE team member can check and confirm.,1390548745,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-t4dsq6rpgyk5vhbxgywu,task_subcomment,NA
+Offer help or descripition for parameters,"It would be nice to offer informative description of each parameter when filling it, to know what to fill. Some paremetr names, are not clear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**Whiteboard**: aklapper-moreinfo",1384164660,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-uhsm2u4fy2r57ifl5now,task_description,invalid
+Offer help or descripition for parameters,"This is what the TemplateData system is for. If you fill in a <templatedata> block for the template in question, VisualEditor will show the descriptions you want.",1384842688,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhsm2u4fy2r57ifl5now,task_subcomment,NA
+Offer help or descripition for parameters,"[""would be nice"" => please set the ""severity"" field to ""enhancement""]
+
+(In reply to comment #0)
+> It would be nice to offer informative description of each parameter when
+> filling it, to know what to fill. 
+
+What are exact steps that would allow me to reproduce this problem?
+
+> Some paremetr names, are not clear.
+
+Which exact parameter names do you refer to?",1384181509,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-uhsm2u4fy2r57ifl5now,task_subcomment,NA
+"on an existing course page ""Create source"" is used instead of ""Edit source"" in the tab at the top","On an existing course page ""Create source"" is used instead of ""Edit source"" in the tab at the top of the page. For an example, see https://en.wikipedia.org/wiki/Education_Program:University_of_Michigan/CHEM_540_%28Fall_2013%29
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384017120,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-drnulywmv5gyytjha22k,task_description,resolved
+"on an existing course page ""Create source"" is used instead of ""Edit source"" in the tab at the top","Just noting here now that this is still problematic. I'll comment on the VE bug, too. Appreciate any efforts to fix it. :)",1396986331,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-drnulywmv5gyytjha22k,task_subcomment,NA
+"on an existing course page ""Create source"" is used instead of ""Edit source"" in the tab at the top","I filed this against the VisualEditor. I'm marking it as a duplicate, but adding Andrew Green to the cc in case he can see a good way of fixing it from within the EducationProgram extension.
+
+*** This bug has been marked as a duplicate of bug 53477 ***",1384096303,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-drnulywmv5gyytjha22k,task_subcomment,NA
+VisualEditor: JS parse error appears while enabling few gadgets for editors,"Steps to reproduce:
+
+1.Go to Preferences>Gadgets
+2.Enable few gadgets.I tried enabling all the gadgets under ""improved navigation"" , Interface : Editing and uploads and Interface:Files and Categories
+
+3.Now load the editor
+
+Observed Result:
+The following js error appears:
+
+Error: JavaScript parse error: Parse error: Illegal token in file 'MediaWiki:Gadget-popups.js' on line 1221 Error {} load.php:145
+log load.php:145
+runScript load.php:154
+checkCssHandles load.php:155
+(anonymous function) load.php:155
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+addEmbeddedCSS load.php:149
+(anonymous function)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383945720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6t3k4ac3wbqeudiatuwg,task_description,invalid
+VisualEditor: JS parse error appears while enabling few gadgets for editors,"https://test2.wikipedia.org/w/index.php?title=MediaWiki:Gadget-popups.js&action=history is from Feb 2012.
+
+Line 1221 is:
+	/*@if (@_jscript_version >= 5)
+
+https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-popups.js&action=history for example is from Nov 2013 (but also contains that line).
+
+Hence wondering if it's a ""real"" problem or just an ancient .js file on test2.",1384111250,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6t3k4ac3wbqeudiatuwg,task_subcomment,NA
+VisualEditor: JS parse error appears while enabling few gadgets for editors,It was found in test2 environment,1383946204,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6t3k4ac3wbqeudiatuwg,task_subcomment,NA
+VisualEditor: JS parse error appears while enabling few gadgets for editors,That sounds like a bug in the popups gadget. Which wiki was this on?,1383946148,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6t3k4ac3wbqeudiatuwg,task_subcomment,NA
+"VisualEditor: Subscript and Superscript applied on same text, making it placed somewhere in the middle of the preceding text","Superscript and Subscript
+
+Steps to reproduced:
+
+1.Click on the ""Edit"" button
+2.Type a text X
+3.Now type ""2"" and make it a superscript
+4.Select the text 2 and make it subscript
+
+Observed Result:
+The text ""2"" now appears somewhere in the middle of the preceding text X which neither superscript nor subscript.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12152}",1383939000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jruyips3fse6ym3bsadi,task_description,resolved
+"VisualEditor: Subscript and Superscript applied on same text, making it placed somewhere in the middle of the preceding text","Previously WONTFIXed. I'll reopen the original bug.
+
+*** This bug has been marked as a duplicate of bug 53330 ***",1384111137,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jruyips3fse6ym3bsadi,task_subcomment,NA
+VisualEditor: The table of content is not showing up until user adds sub-heading 3,"Steps to reproduce:
+
+1.Click on the Edit button
+2.Add a Heading to the page
+3.Now add a sub-heading 1
+4.Add a sub-heading 2 
+5.Click on ""Save Page""
+
+Observed Result:
+The table of contents does not appear.Now if the user adds sub-heading 3, the table of contents show up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383936780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5cydsdjiqddokog4ej2b,task_description,invalid
+VisualEditor: The table of content is not showing up until user adds sub-heading 3,This is MediaWiki native behaviour.,1383936861,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5cydsdjiqddokog4ej2b,task_subcomment,NA
+VisualEditor: Wiki markup and weird characters show up in the view mode while applying link to a text with reference,"Wiki markup and weird text
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Type a text and add a reference to it
+3.Select the text with the reference and apply link to it by clicking on link icon or pressing command+k
+4.Click on ""Save Page""
+
+Observed Result:
+Some weird text along with wiki markup shows up in the editor,
+
+See the screenshot attached.
+
+Page:Any
+Environment:Betalabs and test 2
+Browser:Chrome Version 26.0.1410.65 and firefox 20
+Reproducible :Yes
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12085}",1383869820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-z4ctrxtxswdyl3z2vpsi,task_description,resolved
+VisualEditor: Wiki markup and weird characters show up in the view mode while applying link to a text with reference,"Hi ryasmeen. 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 56250 ***",1383870381,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-z4ctrxtxswdyl3z2vpsi,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=580632339#Space_between_.22:.22_and_characters_count_increase
+
+Looks like this could potentially be the xhtml serializer converting &nbsp; to a nonbreaking space unicode char?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383851100,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_description,resolved
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 101292 merged by GWicke:
+(Bug 56733) Fixed bug serialization template args containing "" : ""
+
+https://gerrit.wikimedia.org/r/101292",1386964670,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 101259 merged by GWicke:
+Merge ""(Bug 56733) Fixed bug serialization template args containing "" : """"
+
+https://gerrit.wikimedia.org/r/101259",1386964668,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 101292 had a related patch set uploaded by GWicke:
+(Bug 56733) Fixed bug serialization template args containing "" : ""
+
+https://gerrit.wikimedia.org/r/101292",1386964478,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 101259 had a related patch set uploaded by GWicke:
+Merge ""(Bug 56733) Fixed bug serialization template args containing "" : """"
+
+https://gerrit.wikimedia.org/r/101259",1386964410,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?",Now deployed and tested fixed @ https://fr.wikipedia.org/w/index.php?title=Utilisateur%3ASsastry%2FSandbox&diff=98462286&oldid=98462267,1384808941,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 95301 merged by jenkins-bot:
+(Bug 56733) Fixed bug serialization template args containing "" : ""
+
+https://gerrit.wikimedia.org/r/95301",1384394433,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 95301 had a related patch set uploaded by Subramanya Sastry:
+(Bug 56733) Fixed bug serialization template args containing "" : ""
+
+https://gerrit.wikimedia.org/r/95301",1384385444,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?",This is caused by the template arg escaping code. Fix coming along with test case.,1384384772,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+Drop-down menu in VisualEditor toolbar causes alternating horizontal scroll bars in dropdown and page,"As seen on mediawiki.org (running 1.23wmf2 (020fe63)) in Firefox 24.
+
+When editing in VisualEditor, the first time I click on the menu icon, the dropdown is slightly too small and a horizontal scroll bar appears inside the dropdown.
+
+The next time I click on the icon, the dropdown's width can accommodate the text and there is no scrollbar in the dropdown itself, but a horizontal scrollbar appears at the page level to accommodate the dropdown's extra width.
+
+Then, rinse and repeat: every other time, there's a scroll bar in the dropdown, and the next one there is one at the bottom of the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383820920,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-dbzugsxj63hxmjo7guoe,task_description,declined
+Drop-down menu in VisualEditor toolbar causes alternating horizontal scroll bars in dropdown and page,I can't reproduce; do you have a screenshot?,1402331915,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dbzugsxj63hxmjo7guoe,task_subcomment,NA
+Bugzilla: Set up product for OOJS and OOJS UI,"OOJS components:
+
+- General
+  The core utilities and unsorted issues.
+
+- EventEmitter
+
+- Registry
+  Registries and factories.
+
+
+Import from:
+https://github.com/trevorparscal/oojs/issues
+
+OOJS UI components:
+
+- General
+  The base classes (Dialog, Frame, Window etc.) and unsorted issues.
+
+- Elements
+  OO.ui.Element and subclasses.
+
+- Layouts
+  OO.ui.Layout and subclasses.
+
+- Tools
+  OO.ui.Tool, ToolGroup and subclasses.
+
+- Widgets
+  OO.ui.Widget and subclasses.
+
+No existing issue tracker (we'll gradually move over issues from VisualEditor and MediaWiki core as needed).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1383779220,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-djxrtouulbirtmeqhyvj,task_description,resolved
+Bugzilla: Set up product for OOJS and OOJS UI,"Per James, I've renamed the products from OOJS and OOJS UI to OOjs and OOjs UI.
+
+Sorry if this breaks anyone's permalinks. Better now than later now that the component is still fresh.",1386276878,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-djxrtouulbirtmeqhyvj,task_subcomment,NA
+Bugzilla: Set up product for OOJS and OOJS UI,"I've created a wiki page:
+ https://www.mediawiki.org/wiki/OOJS
+
+And added a link to it in the product description:
+
+ https://bugzilla.wikimedia.org/describecomponents.cgi?product=OOJS
+
+See wiki page for more information.
+
+Also, note this is all in early migration right now. Things will get clearer as things settle.",1384302859,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-djxrtouulbirtmeqhyvj,task_subcomment,NA
+Bugzilla: Set up product for OOJS and OOJS UI,"As a triager I have no idea what ""Library for working with objects"" might mean, where this is located in the stack, and how to identify tickets that should be moved to the new products. 
+Is there a wikipage covering OOJS? 
+Will https://github.com/trevorparscal/oojs/issues remain the canonical code base or will this / has this been moved to Wikimedia Git?",1383818300,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-djxrtouulbirtmeqhyvj,task_subcomment,NA
+Bugzilla: Set up product for OOJS and OOJS UI,Created the products and some of the components.,1383784953,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-djxrtouulbirtmeqhyvj,task_subcomment,NA
+VisualEditor: Categories are not being added instantly unless user refreshes the browser,"Steps to reproduce:
+
+1.Click on te Edit-beta button
+2.Click on the ""Settings"" button and go to ""Categories"" section
+3.Add a new category
+4.Click on the button ""Apply Changes""
+5.Now click on ""Save Page""
+
+Observed Result:
+The newly added category is not showing up at the end of the page unless user refreshes it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383765060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zkjur77n4a4fhw75q46a,task_description,resolved
+VisualEditor: Categories are not being added instantly unless user refreshes the browser,"Merge this with bug 48560.
+
+*** This bug has been marked as a duplicate of bug 48560 ***",1383767137,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zkjur77n4a4fhw75q46a,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter","The first letter goes to the newline
+
+Steps to Reproduce:
+
+1.Click on the Edit button in firefox
+2.Go to More>Reference
+3.Type something to add as a reference 
+
+Observed Result:
+In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56274
+
+**Attached**: {F12795}",1383694380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ztcqreqfln2w4zvztfod,task_description,resolved
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter","Unsetting ""VERIFIED""; we don't generally use that, and setting it will hide it from people's saved searches.",1384856051,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter","Verified for any page on https://test2.wikipedia.org/ with FireFox 25 using MAC OS X 10.8.5
+Example test page:  https://test2.wikipedia.org/wiki/Verify_56274",1384540116,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter",Verified in betalabs with firefox 25*,1384389969,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter",Looks like this issue got fixed .Verified in betalabs with FireFox,1384389854,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter",This is also happening now while creating a new page in firefox 20.,1383868284,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter","added a See Also, I think this is more of the cursor RETURN/BACKSPACE problem",1383694695,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+VisualEditor: The text is going out of the border of the page for a lengthy content in math inspector,"Text going out of border
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Now from the toolbar click on More>LaTeX
+3.In the dialog box for LaTeX enter a long equation. For Example:
+
+
+\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}
+
+4.Save the page
+
+Observed Result:
+The text is going out of the border of the page for a lengthy content in math inspector
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12792}",1383692400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nw7eq5nisvhi4vmqmjnf,task_description,invalid
+VisualEditor: The text is going out of the border of the page for a lengthy content in math inspector,"This is ultimately up to the control of the user, and so not really a ""bug"".",1415882765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nw7eq5nisvhi4vmqmjnf,task_subcomment,NA
+VisualEditor: The <ref> and <references/> tags are showing up in the view mode [https://gerrit.wikimedia.org/r/#/c/92595],"tags on view mode
+
+Steps to reproduce:
+1.Click on the Edit button
+2.Add a reference to the page
+3.Add a reference list at the end of the page.
+5.Click the button ""Save"" button
+
+
+
+Observed Result:
+The <ref> and <reference/> tags are showing up in the view mode
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12783}",1383683040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-66xp2mmqcy647pdvgm4x,task_description,invalid
+VisualEditor: The <ref> and <references/> tags are showing up in the view mode [https://gerrit.wikimedia.org/r/#/c/92595],Fault due to local lack of the Cite extension; fixed.,1383684301,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-66xp2mmqcy647pdvgm4x,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"Currently en.wikipedia.beta.wmflabs.org runs master of VisualEditor and a manually-synced version of Parsoid that is the same as production. This is great for testing VE as to whether it's good to deploy into production, and had served us reasonably well so far.
+
+We can't just run Parsoid as master, because (a) Parsoid master is occasionally not compatible with VisualEditor master for days or even weeks at a time as the APIs change, and (b) unless Parsoid is going to be pushed live at the same time as VisualEditor (and split into a het-deploy situation for the cluster's wmfX vs. wmfX+1 deployment) we wouldn't know if VE and Parsoid were truly OK to go out.
+
+However, bug 56583 showed that we also need to test master (and ideally also current production) of VisualEditor against *master* of Parsoid, in Labs, for automated browser testing and so on before any code goes live.
+
+Do we need en.wikipedia.beta.wmflabs.org to have en-Parsoid-master-VE-master.wikipedia.beta.wmflabs.org and en-Parsoid-master-VE-prod.wikipedia.beta.wmflabs.org duplicates? (Eww.)
+
+Also, are there other teams who need their multiple independent components and cross-dependencies? Wikidata, perhaps?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383672540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_description,invalid
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"I'm not sure I agree this bug is INVALID; we still can't reliably test master of VisualEditor against production of Parsoid or vice versa; instead, we test master of VisualEditor against master of Parsoid in Beta, and production VisualEditor against production Parsoid in production, and hope that we don't get into one of those situations again where one assumes things about the other…",1401746274,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"(In reply to comment #1)
+> In https://gerrit.wikimedia.org/r/#/c/93939/ I made the beta autoupdater to
+> run
+> `npm install` under common/php-master/extensions/Parsoid/js
+> 
+> Regardless, the parsoid instance is deployment-parsoid2     and runs its own
+> copy of the code under /srv/deployment/parsoid . So it is still being updated
+> manually by whoever has access on it.
+
+Copied that to:
+
+Bug 57233 - beta: Parsoid should continuously deploy master branch",1384852049,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"What we could potentially do in Jenkins:
+
+Whenever a change is send on VisualEditor, we could somehow boot up two Parsoid instances running master and production versions then run the VisualEditor tests against each of them.
+
+Similarly, whenever a change is send to Parasoid, we could create an instance of it and run VisualEditor tests from master and production versions.
+
+That should help both team figuring out potential issues and regressions.
+
+
+We never achieved such integration tests on any project yet. Ideally we would use labs to boot up instances that would contains all the required dependencies and run the tests there.  The infrastructure is not ready yet :-/",1383759070,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"Usually Parsoid master will work fine with VE. DOM spec changes have not been frequent in the past, and will get even less frequent over time. Empirically, the main source of issues has been a lack of integration testing rather than existing functionality breaking because of incompatibilities.
+
+So if we could only set up one version for now I'd prioritize testing against master over testing against an older version of Parsoid, in particular if that is not updated automatically. Much of the VE integration testing is also still manual at this point, which makes focusing on the most likely source of errors even more important.",1383758687,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,*** Bug 56670 has been marked as a duplicate of this bug. ***,1383756706,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,For the sake of clarification: I am open to any solution :),1383755770,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"In https://gerrit.wikimedia.org/r/#/c/93939/ I made the beta autoupdater to run `npm install` under common/php-master/extensions/Parsoid/js
+
+Regardless, the parsoid instance is deployment-parsoid2	 and runs its own copy of the code under /srv/deployment/parsoid . So it is still being updated manually by whoever has access on it.
+
+
+The whole point of beta is to test the tips of master branches from all extensions.  That let us catch potential issue before all those tips are aggregated in a wmf branch.   To prevent new code from being executed, we use feature switching ($wgFeatureXXX = false) that still let us deploy the code and enable it selectively later on.
+
+That being said, I think it would make sense to run VisualEditor and Parsoid on the tip of master. That would probably help you detect possible breakage when deploying.",1383755721,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+Interface message visualeditor-mweditmodesource-title is missing in English for 1.23wmf2,"Noticed on mediawiki.org, in the VisualEditor toolbar, Menu icon, last item: <visualeditor-mweditmodesource-title>. 
+
+Special:Version says mw.o is currently running 1.23wmf2 (88c7b3f).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383655680,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-bawhmiorm2ucu6th36wp,task_description,declined
+Interface message visualeditor-mweditmodesource-title is missing in English for 1.23wmf2,Working now.,1383821933,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bawhmiorm2ucu6th36wp,task_subcomment,NA
+Interface message visualeditor-mweditmodesource-title is missing in English for 1.23wmf2,On further inspection looks like a deployment / server-side caching issue. Definitely nothing wrong with the code though.,1383670006,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-bawhmiorm2ucu6th36wp,task_subcomment,NA
+Interface message visualeditor-mweditmodesource-title is missing in English for 1.23wmf2,Sounds like a caching issue with ResourceLoader.,1383669434,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-bawhmiorm2ucu6th36wp,task_subcomment,NA
+"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE","Error message
+
+Steps to reproduce:
+Click on the edit button
+
+Observed Result:
+""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12683}",1383598080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-72rziu6fsgfsmc5bjdnx,task_description,resolved
+"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE","Fallout from fixing bug 56583. Should be okay now.
+
+*** This bug has been marked as a duplicate of bug 56583 ***",1383598243,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-72rziu6fsgfsmc5bjdnx,task_subcomment,NA
+Can drag and drop non-editable elements from outside the VE surface area,"Video made by en user Atethnekos
+
+As illustrated in the attached video, VE's drag and drop function has some odd quirks in Firefox.  One can select items from below the VE surface, such as the MediaWiki logo or the licensing disclaimer text, and drag them into the VE surface.  These items can only be added to the last line of an article.  Items seem to be added as bulleted items, increasing indent with each addition.
+
+Tested on FF 24 Win 7 with Monobook, duplicated with FF 24 and Mac OS 10.6
+
+Could not duplicate using Chrome on the above Mac OS - may be a Firefox issue.
+
+Described here:https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_12#Moving_links_on_the_page_from_outside_the_VE_surface_into_the_VE_surface
+
+And here:https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Drag_and_drop_redux
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12668}",1383594960,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-hec6fvmphtw5a6pgaa64,task_description,declined
+Can drag and drop non-editable elements from outside the VE surface area,"I confirm that it does not happen for me as well - I seem to be able to drag and drop items, but after I do that nothing changes, and as a matter of fact VE won't prompt me to save. In wikitext mode instead one can actually drag and drop stuff.",1403544337,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hec6fvmphtw5a6pgaa64,task_subcomment,NA
+Can drag and drop non-editable elements from outside the VE surface area,Can't reproduce in FF.,1403008759,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hec6fvmphtw5a6pgaa64,task_subcomment,NA
+VisualEditor: Don't pre-annotate text for superscript and subscript,"All in superscript/subscript format
+
+Steps to reproduce:
+-Type a text x
+-Select it and make to to superscript
+-Now type 1 before x (1x) and both the letters are in superscript format
+-Now type ""/"" between these two letters (1/x) and all three letters are in superscript format
+-Now keep on typing anything before or after (1/x) all the letters are in superscript format.
+-Press ""Enter"" to go to new line
+ 
+Observed Result:
+Now the letter x and all other letters after that are in superscript format
+
+Expected Result:
+Unless selected as superscript/subscript all the texts typed before or after it should be in normal text format.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12661}",1383593280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2a2cr676hxaynicchkxu,task_description,declined
+VisualEditor: Don't pre-annotate text for superscript and subscript,"The pre-annotation described here is intentional behaviour, and used for all text styles (with some special logic for links); we could not do it for some, but I think that that would be too confusing.",1394483008,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2a2cr676hxaynicchkxu,task_subcomment,NA
+reasoning about javascript loading and test failures,"abnormal load.php requests
+
+this is essentially the same problem as shown with UploadWizard in https://bugzilla.wikimedia.org/show_bug.cgi?id=56483
+
+When run in the Sauce Labs environment, tests for VisualEditor for Chrome display many many calls to ResourceLoader that are not shown in normal operation, nor in a browser test in a local environment.  
+
+At least some of these calls to load.php fail with javascript errors, thus causing VE to fail and the test to fail.  
+
+One recent example is shown at https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/117/testReport/junit/(root)/VisualEditor%20Links/Enter_non_existing_link/
+
+Here we see two distinct calls for the same code at ext.echo.alert, the second of which fails, see screen shot.  In detail, the first call succeeds, the second fails:
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.echo.alert%2Cbase%2Cdesktop%2Coverlay&skin=vector&version=20131021T193233Z&*
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.echo.alert%2Cbase%2Cdesktop%2Coverlay&skin=vector&version=20131021T193233Z&*
+Uncaught SyntaxError: Unexpected token ILLEGAL 
+
+Also in this particular run of the test find VE loading up code for ArticleFeedback and for Gadget code for DelAutoDropdown.  VE loading gadget code in normal operation has been documented, see screen shot for invisible_iframe
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56483
+
+**Attached**: {F12626}",1383579480,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-xdv6gb57qioudhzewlqo,task_description,declined
+reasoning about javascript loading and test failures,This is no longer happening.,1384870912,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-xdv6gb57qioudhzewlqo,task_subcomment,NA
+reasoning about javascript loading and test failures,"Unless you can reproduce this outside of SauceLabs, I'm inclined to believe this is simply Chrome in SauceLabs being broken.",1383701818,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xdv6gb57qioudhzewlqo,task_subcomment,NA
+reasoning about javascript loading and test failures,"
+here is an example of a test for Flow on Chrome that repeats the same GET twice for VE code.  the first succeeds, the second gives an error: 
+
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cdata%2Cicons-vector%2Cstandalone%7Cext.visualEditor.viewPageTarget.icons-vector%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20131102T010844Z&*
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cdata%2Cicons-vector%2Cstandalone%7Cext.visualEditor.viewPageTarget.icons-vector%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20131102T010844Z&*
+Uncaught SyntaxError: Unexpected end of input
+
+Ref:  https://saucelabs.com/jobs/e0b3ed7901a14cfdb56b745c6938c12d",1383665196,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-xdv6gb57qioudhzewlqo,task_subcomment,NA
+reasoning about javascript loading and test failures,"Created attachment 13691
+gadget code in VE in normal operation
+
+**Attached**: {F12627}",1383579532,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-xdv6gb57qioudhzewlqo,task_subcomment,NA
+messages don't resolve in standalone VisualEditor,"Standalone VisualEditor shows all messages as the raw [visualeditor-message] strings in tooltips and in general button strings. 
+
+""Format"" dropdown, for example, has 
+[visualedit-rformatdropdown-format-paragraph]
+[visualedit-rformatdropdown-format-heading2]
+[visualedit-rformatdropdown-format-heading3]
+etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383414840,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-rzowuuc23degrhsrsjvb,task_description,resolved
+messages don't resolve in standalone VisualEditor,Yes,1383721313,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rzowuuc23degrhsrsjvb,task_subcomment,NA
+messages don't resolve in standalone VisualEditor,Does https://gerrit.wikimedia.org/r/#/c/93480/ fix this?,1383701956,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rzowuuc23degrhsrsjvb,task_subcomment,NA
+VE button is disable on testwiki,"On test.wikipedia.org I enabled VisualEditor through Beta Features.
+Visiting a page, display:none is applied to the VE edit button (li#ca-ve-edit). This css is at the header of the page.
+
+Since no button is shown, how anyone can use VE?
+Am I missing something?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383382320,PHID-USER-e7gwd3ou5ocdumo42srg,PHID-TASK-sgia5xvzrqql7odhc5nl,task_description,resolved
+VE button is disable on testwiki,"(In reply to comment #2)
+> https://test.wikipedia.org/w/index.php?title=MediaWiki:Common.
+> js&diff=184444&oldid=183093
+
+That was a test config for en.wiki that wanted it I believe, Mz should be fine with you commenting it out.",1383393079,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-sgia5xvzrqql7odhc5nl,task_subcomment,NA
+VE button is disable on testwiki,https://test.wikipedia.org/w/index.php?title=MediaWiki:Common.js&diff=184444&oldid=183093,1383392774,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-sgia5xvzrqql7odhc5nl,task_subcomment,NA
+VE button is disable on testwiki,"The button is disabled through js at MediaWiki:Common.js...
+
+It should be removed since people are asked to test it.",1383383030,PHID-USER-e7gwd3ou5ocdumo42srg,PHID-TASK-sgia5xvzrqql7odhc5nl,task_subcomment,NA
+Parsoid: [REGRESSION] content attribute missing from defaultsort tags,"Before https://gerrit.wikimedia.org/r/#/c/90449 :
+
+<meta property=""mw:PageProp/categorydefaultsort"" content=""Page, Main"" data-parsoid='{""src"":""{{DEFAULTSORT:Page, Main}}"",""dsr"":[1800,1826,null,null]}'/>
+
+After:
+
+<meta property=""mw:PageProp/categorydefaultsort"" data-parsoid='{""src"":""{{DEFAULTSORT:Page, Main}}"",""a"":{""content"":null},""sa"":{""content"":""Page, Main""},""dsr"":[1800,1826,null,null]}'/>
+
+This breaks editing of defaultsort in VisualEditor for obvious reasons, but it also triggers a failure mode in VisualEditor where missing content attributes aren't expected and are normalized to content=""null"", triggering corruption warnings and changing {{DEFAULTSORT:Foo}} to {{DEFAULTSORT:null}}. I'll fix that in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383337560,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5hxk5ete5tb4osa6g3ma,task_description,resolved
+Parsoid: [REGRESSION] content attribute missing from defaultsort tags,"Change 93108 merged by jenkins-bot:
+Bug 56489: Allow content attribute on parsoid-generated meta tokens
+
+https://gerrit.wikimedia.org/r/93108",1383342509,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5hxk5ete5tb4osa6g3ma,task_subcomment,NA
+Parsoid: [REGRESSION] content attribute missing from defaultsort tags,"Change 93108 had a related patch set uploaded by GWicke:
+Bug 56489: Allow content attribute on parsoid-generated meta tokens
+
+https://gerrit.wikimedia.org/r/93108",1383341411,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5hxk5ete5tb4osa6g3ma,task_subcomment,NA
+"VisualEditor: <ooui-toolbar-more> tag is showing up instead of ""More"" text in the toolbar in test2 environment","<ooui-toolbar-more> tag
+
+Steps to reproduce:
+
+-Click on the Edit button on a page in test 2 environment
+-Observe the toolbar
+
+Observed Result:
+
+<ooui-toolbar-more> tag is showing up instead of ""More"" text in the toolbar in test2 environment
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12443}",1383334620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qgb5fgt6vmjtfvknn43z,task_description,resolved
+"VisualEditor: <ooui-toolbar-more> tag is showing up instead of ""More"" text in the toolbar in test2 environment","Unsetting ""VERIFIED""; we don't generally use that, and setting it will hide it from people's saved searches.",1384856040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qgb5fgt6vmjtfvknn43z,task_subcomment,NA
+"VisualEditor: <ooui-toolbar-more> tag is showing up instead of ""More"" text in the toolbar in test2 environment","Cant find this issue in test2 now. Therefore, changing the status to resolved.",1383345126,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qgb5fgt6vmjtfvknn43z,task_subcomment,NA
+"VisualEditor: ""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment","""Error:Database query error ""
+
+Steps to reproduce:
+-Click on the Edit-beta button
+-Type anything to made some changes in the CE
+-Click on the Save button 
+
+Observed Result:
+""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment.
+
+However,attempting to save the content for the second time is saving the content.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12442}",1383334260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kimy5ztgryvb4j5fhi5i,task_description,resolved
+"VisualEditor: ""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment","Unsetting ""VERIFIED""; we don't generally use that, and setting it will hide it from people's saved searches.",1384856027,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kimy5ztgryvb4j5fhi5i,task_subcomment,NA
+"VisualEditor: ""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment","Yes, now it looks fixed.Can not reproduce it anymore.",1383335670,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kimy5ztgryvb4j5fhi5i,task_subcomment,NA
+"VisualEditor: ""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment",Try again? I've just fixed a database error that might actually be related,1383335394,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-kimy5ztgryvb4j5fhi5i,task_subcomment,NA
+reasoning about javascript loading and test failures,"WIP: 
+
+I am seeing a number of failures in the Selenium tests when running for Chrome. The failures seem to be caused by many calls to ResourceLoader, many repeated, many seemingly unnecessary, and some of these calls fail.  Other calls to other unexpected sources are also evident, this is just a single example.  
+
+Each failed test shows a different set of calls to load.php.  Here is one example:
+
+A normal load of UW on beta commons has 2 calls for two jquery things, one for the spinner and one for ULS. See screen shot. 
+
+But a failed automated test shows multiple repeated calls for jquery.ui.button. See screen shot. https://saucelabs.com/jobs/8fd3f6a483db46da9c4cfbbdcf7d2449
+
+A reference to jquery.ui.button is found only one place in all of the UploadWizard source code, line 473 of UploadWizardHooks.php.  It seem to be a dependency for ext.uploadWizard.campaign
+
+What causes UploadWizard to make multiple calls for a jquery feature jquery.ui.button that it would not normally need?
+
+Under what circumstances would this happen to a normal user?
+
+When UW makes these multiple calls, it seems that what is returned from some of those calls is corrupt, possibly truncated, since the errors tend to be 'Uncaught SyntaxError: Unexpected token ILLEGAL' and similar. 
+
+I think VisualEditor has a similar problem, possibly indicated in https://bugzilla.wikimedia.org/show_bug.cgi?id=55801 (see screen shot there)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56567",1383333720,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ccs2prus5tuvbhududhj,task_description,declined
+reasoning about javascript loading and test failures,no longer happening as of about Nov 15,1384870964,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ccs2prus5tuvbhududhj,task_subcomment,NA
+reasoning about javascript loading and test failures,"Created attachment 13659
+too many calls to load.php
+
+**Attached**: {F12435}",1383333823,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ccs2prus5tuvbhududhj,task_subcomment,NA
+reasoning about javascript loading and test failures,"Created attachment 13658
+normal operation
+
+**Attached**: {F12434}",1383333792,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ccs2prus5tuvbhududhj,task_subcomment,NA
+VisualEditor:Show the link to a missing page as a red link as it shows in the dialog,"Steps to reproduce:
+-Click on the button Edit-beta
+-Type a text to insert the link
+-Click on the link icon from the toolbar or press ctrl+k or command+k
+-Now select a new page which is not yet created
+-Save the content
+
+Expected Result:
+The link to a missing page should be shown as a red link as it shows in the dialog
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383264480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zvbelbjtso7n2rf7unpl,task_description,resolved
+VisualEditor:Show the link to a missing page as a red link as it shows in the dialog,"Merging this with bug 37901, which covers this and a little more.
+
+*** This bug has been marked as a duplicate of bug 37901 ***",1383277462,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvbelbjtso7n2rf7unpl,task_subcomment,NA
+VisualEditor: Show suggested links' status with an indicator during auto-suggest,"A link status indicator (red link, redirect, etc.)
+during autosuggest would be great, as long as it fires asynchronously
+and the user isn't blocked on actions while it's loading.
+[Suggested by Erik Moeller]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383256380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-445qwg6xrym7xzuyvyec,task_description,resolved
+VisualEditor: Show suggested links' status with an indicator during auto-suggest,"We did this using sections instead of icons, but marking as FIXED anyway.",1395359396,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-445qwg6xrym7xzuyvyec,task_subcomment,NA
+"central notice banner has js error, causes bogus test failures","URLs such as the following examples appear in several browser tests and cause intermittent test failures in browsers other than Firefox, for example for UploadWizard on beta commons and for AFTv5 on beta enwiki: 
+
+http://bits.beta.wmflabs.org/commons.wikimedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin.clearcookie%7Cext.uls.i18n%2Cime%2Cinit%2Cinterface%2Clanguagenames%2Cpreferences%2Cwebfonts%7Cext.uls.webfonts.repository%7Cjquery.client%2Ccookie%2CdelayedBind%2Ci18n%2CjStorage%2Cjson%2CmwExtension%2Ctipsy%2Culs%2Cwebfonts%7Cjquery.uls.data%2Cgrid%7Cmediawiki.Uri%2Capi%2Cnotify%2Cuser%2Cutil%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cskins.vector.js%7Cwikibase.client.init&skin=vector&version=20131026T061711Z&*
+view data
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin%7Cext.uls.i18n%2Cime%2Cinit%2Cinterface%2Clanguagenames%2Cpreferences%2Cwebfonts%7Cext.uls.webfonts.repository%7Cext.visualEditor.viewPageTarget.init%7Cext.wikimediaShopLink.core%7Cjquery.byteLength%2Cclient%2Ccookie%2CdelayedBind%2Ci18n%2CjStorage%2Cjson%2CmwExtension%2Ctipsy%2Culs%2Cwebfonts%7Cjquery.uls.data%2Cgrid%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.language.data%2Cinit%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cskins.vector.js%7Cwikibase.client.init%2Cnolanglinks&skin=vector&version=20131031T104306Z&*
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383230520,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-dgtigim34wqholkwxjpw,task_description,declined
+"central notice banner has js error, causes bogus test failures",I guess that issue has been fixed somehow. If it is still causing browser tests to choke please reopen.,1391375202,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dgtigim34wqholkwxjpw,task_subcomment,NA
+"central notice banner has js error, causes bogus test failures","the errors seen are: 
+
+javascript error: Uncaught SyntaxError: Unexpected token ILLEGAL
+
+javascript error: Uncaught SyntaxError: Unexpected end of input",1383230746,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-dgtigim34wqholkwxjpw,task_subcomment,NA
+"VisualEditor: Two adjacent paragraphs made lists in separate actions are made into two lists, not one list with two items","Wrongly ordered list
+
+Steps to reproduce:
+
+-Click on the ""Edit"" button of the Visual Editor.
+-Have multiple lines to be listed in a Numbered list.
+For Example:
+Item One
+Item Two
+-Now select the first line ""Item One"" and click on the icon of ""Numbered list"" to number this item
+-Now again select the both lines ""Item One"" and ""Item Two""
+-Click on the icon of ""Numbered List""
+
+Observed Result:
+Both the lines are now numbered with order 1 like following:
+
+1.Item One
+1.Item Two
+
+Expected Result:
+The numbered list should maintain the continuous order if selected a previously ordered line like following:
+
+1.Item One
+2.Item Two
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12117}",1383079200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-y4pcs6u7xh3tw5y7ea4f,task_description,declined
+"VisualEditor: Two adjacent paragraphs made lists in separate actions are made into two lists, not one list with two items",This is intentional behaviour; re-titling and marking WONTFIX.,1394504425,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y4pcs6u7xh3tw5y7ea4f,task_subcomment,NA
+VisualEditor: Do mass DM round trip testing with Wikipedia content,"Like, Parsoid's round-trip testing, we should do DM round-trip testing with content from Wikipedia. dirtydiffbot does this to some extent, but it tests the Parsoid output rather than the DM output and it uses the UI, which is hacky. We should have a proper service that just tests the DM HTML output is clean, which requires a test runner for that purpose in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383070560,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hl7fehn5dewfavdk36so,task_description,resolved
+VisualEditor: Do mass DM round trip testing with Wikipedia content,"
+
+*** This bug has been marked as a duplicate of bug 50513 ***",1393640838,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hl7fehn5dewfavdk36so,task_subcomment,NA
+VisualEditor: Controls stop working when browser window is small,"click Edit/beta, nothing happens at this size
+
+this seems to manifest in several ways: 
+
+* 'Edit/beta' link stops working, see screen shot
+* Indent/outdent buttons disappear, see screen shot
+* possibly more
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12066}",1383056100,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-gsqvj57elluda2nmu55f,task_description,resolved
+VisualEditor: Controls stop working when browser window is small,AFAICT this is now fixed.,1404168962,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gsqvj57elluda2nmu55f,task_subcomment,NA
+VisualEditor: Controls stop working when browser window is small,"I tried to reproduce this on my end using FireFox and Chrome browser and what I observed is re-sizing the window distorts the visual editor toolbar placement, which was making Indent/Outdent and other buttons hide behind the search box sometimes.
+
+But ""Edit/beta"" button was working fine in my browser.
+
+See the screenshot attached",1383090520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gsqvj57elluda2nmu55f,task_subcomment,NA
+VisualEditor: Controls stop working when browser window is small,"Created attachment 13626
+resize window
+
+**Attached**: {F12068}",1383090459,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gsqvj57elluda2nmu55f,task_subcomment,NA
+VisualEditor: Controls stop working when browser window is small,"Created attachment 13614
+indent/outdent controls not loaded in page at this size
+
+**Attached**: {F12067}",1383056197,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-gsqvj57elluda2nmu55f,task_subcomment,NA
+VisualEditor: Hitting Enter in a block slug does not create a new line,"Try to VEdit
+https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=578251398
+or
+https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&oldid=62136875 .
+
+Place your cursor at the bottom of the page.
+
+Hit Enter.
+
+Expected result: a new line is created.
+Actual outcome: nothing happens.
+
+Please note that this works fine if instead you type something, and hit Enter after doing so.
+
+It happens on both FF and Chrome with both Vector or Monobook.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382960700,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-43dibnfvzllm4nbj6ga3,task_description,invalid
+VisualEditor: Hitting Enter in a block slug does not create a new line,"This is because the cursor in these documents is in a block slug, and so VisualEditor stops you from creating pointless blank lines that won't be saved. Marking as INVALID, but this should (hopefully) be made much clearer with the proposed changes to block slugs to make them more obviously special.",1393983083,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-43dibnfvzllm4nbj6ga3,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"I do not know how to check if this is already happening or not. This is the list of repositories that currently contain Ruby code:
+
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/selenium
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/CirrusSearch
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Flow
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/MobileFrontend
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Translate
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/TwnMainPage
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/UniversalLanguageSelector
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/VisualEditor
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Wikibase
+https://gerrit.wikimedia.org/r/#/admin/projects/qa/browsertests
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382704500,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-imfh6gg55vyil5deeyj5,task_description,resolved
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"  mwext-VisualEditor-ruby1.9.3lint: SUCCESS
+  mwext-Wikibase-ruby1.9.3lint: SUCCESS
+
+\O/
+
+Thank you :-]",1382708537,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91867 merged by jenkins-bot:
+trigger rubylint for VisualEditor and Wikibase
+
+https://gerrit.wikimedia.org/r/91867",1382708377,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91867 had a related patch set uploaded by Hashar:
+trigger rubylint for VisualEditor and Wikibase
+
+https://gerrit.wikimedia.org/r/91867",1382708347,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"  mwext-CirrusSearch-ruby1.9.3lint: SUCCESS
+  mwext-Flow-ruby1.9.3lint: SUCCESS
+  mwext-Translate-ruby1.9.3lint: SUCCESS
+  mwext-TwnMainPage-ruby1.9.3lint: SUCCESS
+
+I forgot the VisualEditor and Wikibase triggers :(",1382708255,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91862 merged by jenkins-bot:
+ruby1.9.3 lint jobs for some repositories
+
+https://gerrit.wikimedia.org/r/91862",1382707581,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91862 had a related patch set uploaded by Hashar:
+ruby1.9.3 lint jobs for some repositories
+
+https://gerrit.wikimedia.org/r/91862",1382707520,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91853 merged by jenkins-bot:
+ruby1.9.3 lint jobs for some repositories
+
+https://gerrit.wikimedia.org/r/91853",1382707232,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91853 had a related patch set uploaded by Zfilipin:
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code
+
+https://gerrit.wikimedia.org/r/91853",1382705512,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"The rest:
+
+CirrusSearch
+Flow
+Translate
+TwnMainPage
+VisualEditor
+Wikibase",1382705372,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"[2:39p] hashar:
+the current jobs are:
+mediawiki-selenium-ruby1.9.3lint
+mwext-MobileFrontend-ruby1.9.3lint
+mwext-UniversalLanguageSelector-ruby1.9.3lint
+qa-browsertests-ruby1.9.3lint",1382704967,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Looks like this is the repo:
+
+https://gerrit.wikimedia.org/r/#/admin/projects/integration/jenkins-job-builder-config
+
+and this is example:
+
+https://gerrit.wikimedia.org/r/#/c/57730/2/mediawiki-extensions.yaml",1382704722,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Set up Code Climate for all repositories that have Ruby code,"We have Code Climate set up for several repositories. Set it up for all repositories with Ruby code.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382690400,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-xjqjhle7et4eysgadisw,task_description,resolved
+Set up Code Climate for all repositories that have Ruby code,"Change 91830 merged by jenkins-bot:
+Set up Code Climate for all repositories that have Ruby code
+
+https://gerrit.wikimedia.org/r/91830",1382692753,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xjqjhle7et4eysgadisw,task_subcomment,NA
+Set up Code Climate for all repositories that have Ruby code,"Change 91830 had a related patch set uploaded by Zfilipin:
+Set up Code Climate for all repositories that have Ruby code
+
+https://gerrit.wikimedia.org/r/91830",1382692577,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xjqjhle7et4eysgadisw,task_subcomment,NA
+Set up Code Climate for all repositories that have Ruby code,"Existing:
+
+https://codeclimate.com/github/wikimedia/qa-browsertests
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-MobileFrontend
+
+New:
+
+https://codeclimate.com/github/wikimedia/mediawiki-selenium
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-CirrusSearch
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-Flow
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-Translate
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-TwnMainPage
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-VisualEditor
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-Wikibase",1382691589,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-xjqjhle7et4eysgadisw,task_subcomment,NA
+qa/browsertests log in twice,"probably the new ruby gem.  see the video at 
+
+https://wmf.ci.cloudbees.com/job/browsertests-en.wikipedia.beta.wmflabs.org-windows-internet_explorer_10/248/testReport/junit/(root)/Page/Move_existing_page_dialog/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382641860,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-m5ly62fnpxkni7on4d5x,task_description,resolved
+qa/browsertests log in twice,"Change 91876 merged by jenkins-bot:
+[browser test] Workaround for the problem when Cucumber hook executes twice
+
+https://gerrit.wikimedia.org/r/91876",1382716505,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+qa/browsertests log in twice,"Change 91881 merged by Zfilipin:
+no need to log in twice
+
+https://gerrit.wikimedia.org/r/91881",1382716387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+qa/browsertests log in twice,"Change 91881 had a related patch set uploaded by Zfilipin:
+no need to log in twice
+
+https://gerrit.wikimedia.org/r/91881",1382715683,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+qa/browsertests log in twice,"Change 91876 had a related patch set uploaded by Zfilipin:
+[browser test] Workaround for the problem when Cucumber hook executes twice
+
+https://gerrit.wikimedia.org/r/91876",1382714776,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+qa/browsertests log in twice,"There is a problem with running hooks twice.
+
+See:
+
+https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/107/testReport/(root)/VisualEditor%20Headings/Cycle_through_headings_values__outline_example_____Paragraph_____Editing____/",1382712122,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+Fail on trying to target a person with a message,"2013-10-23 - 13:04:35  <marktraceur> !e VisualEditor | Svetlana
+2013-10-23 - 13:04:36  <wm-bot> Svetlana: https://www.mediawiki.org/wiki/Extension:VisualEditor_%7c_Svetlana
+
+It captured the "" | Svetlana"" part. That's very annoying.
+
+The message is currently https://www.mediawiki.org/wiki/Extension:$wiki_encoded_* - maybe that's wrong?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382559120,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-ya3ww47fwcb2aqeuzqly,task_description,resolved
+Fail on trying to target a person with a message,"
+
+*** This bug has been marked as a duplicate of bug 51259 ***",1382559178,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-ya3ww47fwcb2aqeuzqly,task_subcomment,NA
+Enable VisualEditor for the Portal and Book namespaces on enwiki,"Following on from bug 48430 and bug 56000.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382460120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-waufzrnebrjzcfjas3t4,task_description,resolved
+Enable VisualEditor for the Portal and Book namespaces on enwiki,Now done.,1382640853,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-waufzrnebrjzcfjas3t4,task_subcomment,NA
+Enable VisualEditor for the Portal and Book namespaces on enwiki,"Change 91198 merged by jenkins-bot:
+enwiki: Enable VisualEditor for Portal: and Book:
+
+https://gerrit.wikimedia.org/r/91198",1382640825,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-waufzrnebrjzcfjas3t4,task_subcomment,NA
+Enable VisualEditor for the Portal and Book namespaces on enwiki,"Change 91198 had a related patch set uploaded by Jforrester:
+enwiki: Enable VisualEditor for Portal: and Book:
+
+https://gerrit.wikimedia.org/r/91198",1382460198,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-waufzrnebrjzcfjas3t4,task_subcomment,NA
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,"As requested at https://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Ajuda#Editor_visual_a_Viquiprojecte
+
+Please enable VisualEditor in ca.wikipedia.org at the ""Viquiprojecte"" namespace.
+
+Having it enabled in ""Portal"" wold be useful as well.
+
+Currently VE is available also to anonymous users in the Main namespace at ca.wiki. The same behavior can be applied to these other namespaces. Thank you!
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1382459760,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_description,resolved
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,And deployed. It works. Thank you!,1382724903,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_subcomment,NA
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,Now done.,1382640836,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_subcomment,NA
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,"Change 91197 merged by jenkins-bot:
+cawiki: Enable VisualEditor for Portal: and Viquiprojecte:
+
+https://gerrit.wikimedia.org/r/91197",1382640724,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_subcomment,NA
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,"Change 91197 had a related patch set uploaded by Jforrester:
+cawiki: Enable VisualEditor for Portal: and Viquiprojecte:
+
+https://gerrit.wikimedia.org/r/91197",1382460289,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*","VE works well-enough for pages that aren't signed, except for ones where the pages rely on fiddly or partial wikitext munging, like the Template and MediaWiki namespaces. Consequently, we should be OK to enable VE in a larger number of namespaces, rather than just NS_MAIN and NS_USER:
+
+* NS_FILE	
+* NS_HELP	
+* NS_CATEGORY
+* wgContentNamespaces generally?
+
+Part of the fun are things like the portal namespace which is defined per-wiki.
+
+See also bug 55792 for comments about enabling VE in all namespaces, and why I think that's a bad idea.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382372460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_description,resolved
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*",Now done.,1382640790,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*","Change 90923 merged by jenkins-bot:
+Enable VisualEditor for NS_FILE, NS_HELP, NS_CATEGORY
+
+https://gerrit.wikimedia.org/r/90923",1382640276,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*","(In reply to comment #2)
+> How well does VisualEditor handle the non-editable portions of File and
+> Category pages? Do they just disappear when VE is invoked?
+
+Those aren't on the page, they're just composited on in read mode. See for example https://www.mediawiki.org/wiki/Category:Requests_for_comment or https://www.mediawiki.org/wiki/File:2013-08-21_Flow_prototype.png to take two pages at random from MWwiki.",1382455942,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*",How well does VisualEditor handle the non-editable portions of File and Category pages? Do they just disappear when VE is invoked?,1382433130,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*","Change 90923 had a related patch set uploaded by Jforrester:
+Enable VisualEditor for NS_FILE, NS_HELP, NS_CATEGORY
+
+https://gerrit.wikimedia.org/r/90923",1382373282,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"VisualEditor: Page fragment parsing not interpreting raw citation template inserted into a ""content"" block correctly","Intention:  To copy a reference (copied from en.wp's article on [[Vanilla]]), using the ""+"" system within the transclusion editor into another article (Simple English's [[Vanilla]]).
+
+
+Expectation:  That the ref dialog box would display the citation correctly.
+
+
+Steps to reproduce:
+
+1)  Click the menu item to insert a reference.
+
+2)  Click the transclusion item to insert a template.
+
+3)  Click the ""+"" and the ""[ ]"" to insert 'content' rather than individual parameters.
+
+4)  Paste in the citation template, copied out of the English Wikipedia.  The citation template entered was:
+{{cite web | title = FAO's Statistical Database - FAOSTAT | year = 2011 | url = http://faostat3.fao.org}}
+
+5)  Click ""Apply changes"".
+
+
+Result:
+
+See https://commons.wikimedia.org/wiki/File:VisualEditor_Oct_2013_ref_dialog_box_with_oddly_formatted_citation_template.png
+
+It should have displayed within the reference dialog box as:
+
+""FAO's Statistical Database - FAOSTAT"". 2011.
+
+with the first part being the link.  Instead, it added a second copy of the URL at the end:
+
+""FAO's Statistical Database - FAOSTAT"". 2011.  http://faostat3.fao.org/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382051580,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-xbuo4fcnx4oupw7ol2me,task_description,resolved
+"VisualEditor: Page fragment parsing not interpreting raw citation template inserted into a ""content"" block correctly",Fixed a while ago; sorry for slow triage.,1398113380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xbuo4fcnx4oupw7ol2me,task_subcomment,NA
+"VisualEditor: Page fragment parsing not interpreting raw citation template inserted into a ""content"" block correctly",Bug 59154 seems related.,1388857771,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xbuo4fcnx4oupw7ol2me,task_subcomment,NA
+Customize Jenkins email notifications,"Could we use the same subject heading for these emails so they grouped
+into one thread? e.g. QA Report and move the current subject into the
+email body itself?
+
+Currently I am getting lots of mails in the form:
+Build failed in Jenkins: MobileFrontend-en.m.wikipedia.org-linux-firefox #97
+
+and it is very hard to group and filter them.
+
+As a result I tend to ignore them due to too much noise which is bad :).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**Whiteboard**: gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks
+**URL**: https://www.google-melange.com/gci/task/view/google/gci2013/5243150582939648",1381984200,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ytppcpdbs2adftajp5tt,task_description,resolved
+Customize Jenkins email notifications,"I have another way to resolve.
+
+I can generate an HTML file and send it as an email body.
+
+
+```
+Changing email body programmatically is possible now.
+
+You can go to Manage Jenkins > Configure System and set Default Content as
+           ${FILE,path=""email-body.html""}​​​​​​​
+
+           under Extended E-mail Notification area.
+
+
+Now, you just have to generate email-body.html file programmatically directly under your workspace root.
+
+Also, make sure that default content type is set to HTML.
+```
+
+src: https://softwaretestingboard.com/qna/2205/modify-email-subject-jenkins-using-automated-script-written",1499262343,PHID-USER-3clat6h5vxkg6w4ifzdn,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Change 106513 merged by Cmcmahon:
+Use new e-mail template
+
+https://gerrit.wikimedia.org/r/106513",1389290678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Change 106513 had a related patch set uploaded by Zfilipin:
+Use new e-mail template
+
+https://gerrit.wikimedia.org/r/106513",1389286652,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Change 103114 merged by Cmcmahon:
+Add jenkins email template for better email notifications
+
+https://gerrit.wikimedia.org/r/103114",1387812580,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Change 103114 had a related patch set uploaded by Sn1per:
+Add jenkins email template for better email notifications
+
+https://gerrit.wikimedia.org/r/103114",1387650250,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 14048
+after
+
+**Attached**: {F11948}",1386685401,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 14047
+before
+
+**Attached**: {F11947}",1386685379,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"As far as I am concerned, this bug is resolved. If you need more/less information in Jenkins e-mail notification, leave a comment. See attached e-mail for ""before"" and ""after"".",1386685353,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Asked cloudbees to upload the template:
+
+https://cloudbees.zendesk.com/requests/14940",1386681939,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"(In reply to comment #15)
+> Created attachment 13967 [details]
+> First version of jenkins template ready for testing
+> 
+> 1. To use this template, place it under $JENKINS_HOME/email-templates/
+> 2. make sure email-ext plugin is installed
+> 3. Under the job config for post-build actions, remove ""email notification""
+> and
+> add ""editable email notification""
+> 4. Change default content type to html
+> 5. Change body to ${SCRIPT, template=""wikimedia-jenkins.template-1""}
+> 6. Optional - change the subject using the token references; here is the one
+> i
+> used: ${PROJECT_NAME} ${BUILD_NUMBER} - ${BUILD_STATUS}
+> 7. Set the recipients, etc.
+> 8. Open Advanced Settings... and there you can change when an email
+> notification is triggered.
+
+If you want the subject to be constant for one build, make the subject just ${PROJECT_NAME}
+
+//attachment wikimedia-jenkins-1.template ignored as obsolete//",1386434031,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"(In reply to comment #26)
+> If you would like to continue working on the template (making it look more
+> like
+> Jenkins web page) I will create another task.
+
+Sure, I would definitely like to finish up this template.",1386371967,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Final email template (for now)
+
+**Attached**: {F11946}",1386371916,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey, the last e-mail that I got from your local Jenkins looked good to me! Please upload the template here so I can test it with our Jenkins and if it works I will close the task.
+
+If you would like to continue working on the template (making it look more like Jenkins web page) I will create another task.
+
+If you would like to work on something else, we have plenty of tasks.",1386330549,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"(In reply to comment #24)
+> Created attachment 13990 [details]
+> how e-mail notification after failed test should look like
+
+Do you want the entire table there in the email?  Right now I have the notifications working with everything and it looks pretty close to the jenkins build page.
+
+**Attached**: {F11945}",1386292055,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 13990
+how e-mail notification after failed test should look like
+
+**Attached**: {F11945}",1386256542,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey,
+
+see attached file on how an e-mail notification after failed test should look like. It is generated by this test:
+
+https://geofbot.ci.cloudbees.com/job/test2/lastCompletedBuild/testReport/",1386256508,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"I forgot to say, now you can test e-mail notifications using your jobs. If you have any questions, let me know.",1386195152,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 13979
+e-mail notification with failed tests
+
+**Attached**: {F11944}",1386166633,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey,
+
+I did not want to mess up existing job (test), so I have created another one (test2). Short documentation on how to set up a job to run tests is available[1]. I have cloned browsertests[2] repository and the job runs tests from login.feature[3] file. I will attach e-mail that was sent after the job failed.
+
+1: https://github.com/wikimedia/mediawiki-selenium/blob/master/docs/job.md
+2: https://github.com/wikimedia/qa-browsertests
+3: https://github.com/wikimedia/qa-browsertests/blob/master/features/login.feature",1386166601,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Example html 3
+
+The example html for template 1.1
+
+//attachment progress3.html ignored as obsolete//",1386125139,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Template v1.1
+
+Better version with some bugs ironed out
+
+Would be nice if someone tested out the ""tests"" part of it because I don't have tests set up for my local jenkins build.
+
+//attachment wikimedia-jenkins.template ignored as obsolete//",1386124914,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Example html 2
+
+I don't have tests set up on my jenkins, so unfortunately I couldn't test that aspect of the template
+
+I replaced all of the LAN image references with a cloudbees link so they would work, but the links to the build will be broken.
+
+//attachment progress2.html ignored as obsolete//",1386107476,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey, can you attach an example e-mail, so we can see if the template does what we need?",1386080408,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"First version of jenkins template ready for testing
+
+1. To use this template, place it under $JENKINS_HOME/email-templates/
+2. make sure email-ext plugin is installed
+3. Under the job config for post-build actions, remove ""email notification"" and add ""editable email notification""
+4. Change default content type to html
+5. Change body to ${SCRIPT, template=""wikimedia-jenkins.template-1""}
+6. Optional - change the subject using the token references; here is the one i used: ${PROJECT_NAME} ${BUILD_NUMBER} - ${BUILD_STATUS}
+7. Set the recipients, etc.
+8. Open Advanced Settings... and there you can change when an email notification is triggered.
+
+//attachment wikimedia-jenkins-1.template ignored as obsolete//",1386046436,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Progress on email-ext customization
+
+//attachment progress1.html ignored as obsolete//",1385856189,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey, feel free to attach the e-mail to this bug, or to send it to me, so I could take a look.",1385821722,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Progress!
+
+I managed to extract the first line of console output to find who started the job.  It took a lot of guesswork (I have never coded in Groovy before, especially not within a HTML :P)",1385782467,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey, this might be the problematic part: ""Have your Jenkins administrator place the script inside JENKINS_HOME\email-templates."" (from plugin documentation[1]).
+
+You should contact cloudbees support and ask how to do it.
+
+1: https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin",1385740730,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,Cloudbees URL: https://geofbot.ci.cloudbees.com/job/test/,1385735855,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Hi Geoffrey and welcome!
+
+For future reference, if you get stuck you can ask questions here, at #wikimedia-qa freenode IRC channel or at QA mailing list[1].
+
+To answer your question, start with either installing Jenkins[2] on your local machine or create a free account at a hosted Jenkins service, like Cloudbees[3].
+
+When you have a test Jenkins instance, create a few jobs and start sending e-mail notifications to your e-mail.
+
+Then install the plugin[4] Jeff has suggested and try changing the e-mail notifications so they look more like this report[5].
+
+If you get stuck, or if you have any questions, let us know.
+
+1: https://lists.wikimedia.org/mailman/listinfo/qa
+2: http://jenkins-ci.org/
+3: http://www.cloudbees.com/
+4: https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
+5: https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/164/",1385580760,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Hey, I'm GEOFBOT from GCI!  I think I'll try out this task, but I have no clue how to start out.  Where should I start out?",1385572655,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"(In reply to comment #6)
+> From what I understand, the people would like the e-mail notification to look
+> similar to this page:
+> 
+> https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.
+> wmflabs.org-linux-chrome/164/
+
+Yeah, that would be *much* more useful. It would also be nice to still get the recent changes that were checked in like in the current mail, eg:
+
+Changes:
+
+[roan.kattouw] Share code between conflict resolution and the edit source
+switch
+
+[roan.kattouw] Don't build out save dialog when initializing editor
+
+[roan.kattouw] Use InputWidget facilities in byte limit counter
+
+[krinklemail] Remove the toolbar tracker
+
+And if they could provide links to changesets gerrit, that would be even better :)
+
+It would also be good if there was a direct link provided to the build in jenkins.",1385498734,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"From what I understand, the people would like the e-mail notification to look similar to this page:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/164/",1385490092,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"If you do not have an e-mail client, this is how an e-mail notification for a failed Jenkins job looks like:
+
+
+
+From: jenkins-no-reply@cloudbees.com 
+To:  
+Date: Tue, 26 Nov 2013 19:02:57 +0100 
+Subject: Build failed in Jenkins: VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox #172 
+ 
+See <https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/172/changes>
+
+Changes:
+
+[roan.kattouw] Share code between conflict resolution and the edit source switch
+
+[roan.kattouw] Don't build out save dialog when initializing editor
+
+[roan.kattouw] Use InputWidget facilities in byte limit counter
+
+[krinklemail] Remove the toolbar tracker
+
+------------------------------------------
+Started by user Chris Mcmahon
+Building remotely on s-e4476767 in workspace <https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/ws/>
+Cloning the remote Git repository
+Cloning repository https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor
+git --version
+git version 1.7.11.7
+Checking out Revision 07464e20a535fe1efdbd7f8e862ff8f7b3825722 (origin/master)
+[VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox] $ /bin/sh -xe /tmp/hudson495896231200628031.sh
++ export MEDIAWIKI_USER=Selenium_user
++ MEDIAWIKI_USER=Selenium_user
++ export MEDIAWIKI_PASSWORD_VARIABLE=MEDIAWIKI_PASSWORD_SELENIUM_USER_WMFLABS_ORG
++ MEDIAWIKI_PASSWORD_VARIABLE=MEDIAWIKI_PASSWORD_SELENIUM_USER_WMFLABS_ORG
++ export BROWSER_LABEL=firefox
++ BROWSER_LABEL=firefox
++ export MEDIAWIKI_URL=http://en.wikipedia.beta.wmflabs.org/wiki/
++ MEDIAWIKI_URL=http://en.wikipedia.beta.wmflabs.org/wiki/
++ curl -s -o use-ruby https://repository-cloudbees.forge.cloudbees.com/distributions/ci-addons/ruby/use-ruby
++ RUBY_VERSION=2.0.0-p247
++ source ./use-ruby
+++ [[ -z 2.0.0-p247 ]]
+++ ruby187='1.8.7-*'
+++ [[ 2.0.0-p247 == 1.8.7-* ]]
+++ BASE=/scratch/jenkins/addons
+++ mkdir -p /scratch/jenkins/addons
+++ '[' '!' -f /scratch/jenkins/addons/use.sh ']'
+++ wget -q -P /scratch/jenkins/addons https://repository-cloudbees.forge.cloudbees.com/distributions/ci-addons/lib/use.sh
+++ . /scratch/jenkins/addons/use.sh
+++ mkdir -p /scratch/jenkins/addons/ruby
++++ addon_architecture
++++ uname -m
+++ ruby_name=ruby-2.0.0-p247-x86_64
+++ '[' '!' -f /scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64.tar.bz2 ']'
++++ addon_platform
+++++ head -n 1
+++++ cat /etc/issue
++++ issue='Fedora release 17 (Beefy Miracle)'
++++ fedora_regex='Fedora release 17*'
++++ [[ Fedora release 17 (Beefy Miracle) == Fedora release 17* ]]
++++ echo fc17
++++ return
+++ wget -q -P /scratch/jenkins/addons/ruby https://repository-cloudbees.forge.cloudbees.com/distributions/ci-addons/ruby/fc17/ruby-2.0.0-p247-x86_64.tar.bz2
+++ '[' '!' -f /scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64/bin/ruby ']'
+++ tar xjf /scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64.tar.bz2 -C /scratch/jenkins/addons/ruby
+++ export RUBY_HOME=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64
+++ RUBY_HOME=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64
+++ export PATH=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64/bin:/opt/jdk/latest/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/opt/maven/latest/bin:/opt/ant/latest/bin:/opt/android/android-sdk-linux/tools:/opt/gradle/latest/bin:/home/jenkins/bin:/opt/jdk/jdk.latest/bin
+++ PATH=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64/bin:/opt/jdk/latest/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/opt/maven/latest/bin:/opt/ant/latest/bin:/opt/android/android-sdk-linux/tools:/opt/gradle/latest/bin:/home/jenkins/bin:/opt/jdk/jdk.latest/bin
+++ unset GEM_PATH
+++ unset GEM_HOME
+++ unset BUNDLE_PATH
++ gem install bundler --no-ri --no-rdoc
+Successfully installed bundler-1.3.5
+1 gem installed
++ '[' -d modules/ve-mw/test/browser/ ']'
++ cd modules/ve-mw/test/browser/
++ bundle install
+Fetching gem metadata from https://rubygems.org/..........
+Fetching gem metadata from https://rubygems.org/..
+Installing builder (3.2.2) 
+Installing ffi (1.9.3) 
+Installing childprocess (0.3.9) 
+Installing diff-lcs (1.2.4) 
+Installing multi_json (1.8.2) 
+Installing gherkin (2.12.2) 
+Installing multi_test (0.0.2) 
+Installing cucumber (1.3.8) 
+Installing i18n (0.6.5) 
+Installing faker (1.2.0) 
+Installing yml_reader (0.2) 
+Installing data_magic (0.16.1) 
+Installing json (1.8.1) 
+Installing net-http-persistent (2.9) 
+Installing page_navigation (0.9) 
+Installing rubyzip (1.0.0) 
+Installing websocket (1.0.7) 
+Installing selenium-webdriver (2.37.0) 
+Installing watir-webdriver (0.6.4) 
+Installing page-object (0.9.3) 
+Installing mime-types (2.0) 
+Installing rest-client (1.6.7) 
+Installing rspec-expectations (2.14.3) 
+Installing syntax (1.0.0) 
+Installing mediawiki-selenium (0.1.12) 
+Using bundler (1.3.5) 
+Your bundle is complete!
+Use `bundle show [gemname]` to see where a bundled gem is installed.
++ bundle exec cucumber --verbose --profile ci --tags @en.wikipedia.beta.wmflabs.org
+Code:
+  * features/support/env.rb
+  * features/support/hooks.rb
+  * features/support/modules/url_module.rb
+  * features/support/pages/cursor_test_page.rb
+  * features/support/pages/login_page.rb
+  * features/support/pages/visual_editor_page.rb
+  * features/step_definitions/bullets_steps.rb
+  * features/step_definitions/common_steps.rb
+  * features/step_definitions/cursor_steps.rb
+  * features/step_definitions/general_markup_steps.rb
+  * features/step_definitions/headings_steps.rb
+  * features/step_definitions/links_steps.rb
+  * features/step_definitions/references_steps.rb
+  * features/step_definitions/shared_steps.rb
+  * features/step_definitions/transclusion_steps.rb
+
+Features:
+  * features/bullets.feature
+  * features/edit_utf8_logged_in.feature
+  * features/general_markup.feature
+  * features/headings.feature
+  * features/indent_outdent.feature
+  * features/links.feature
+  * features/references.feature
+  * features/transclusion.feature
+Parsing feature files took 0m0.111s
+
+Build step 'Execute shell' marked build as failure
+Recording test results",1385489908,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 13911
+typical Jenkins report
+
+**Attached**: {F11943}",1385489783,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,This is how a typical Jenkins report looks like (see attached file).,1385489700,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"**jhall** wrote:
+
+I used this plugin in a previous job and found it to be very flexible (among other things, it provides for customized e-mail subject strings):
+
+https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin",1385484207,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,We should find a Jenkins plugin that should allow us to customize e-mail notification messages. The default messages are not really useful.,1382419361,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"Seen in Chrome and not Firefox: 
+
+Sometimes initiating a VE session can take on the order of 3X the normal time (or possibly more).  This is a UX issue and also causes significant intermittent browser test failures in Chrome version 30.  Here are 10 runs of a script[*] that times how long it takes to bring up and dismiss the ""Welcome..."" iframe:
+
+2.194106
+2.187554
+2.222601
+2.226447
+2.369503
+2.182237
+7.639938 *
+2.335375
+2.397571
+2.271333
+
+This is on a fast connection.  The performance issue is exacerbated on a slow connection.
+
+Speculation as to the root cause: 
+
+* The ""Welcome..."" iframe is actually the second iframe in the page.  The first, much larger iframe in the page is invisible and is a complete copy of the base VisualEditor UI.  It could be that loading both iframes could cause intermittent performance problems. 
+
+* (Note that the invisible first iframe on the page not only contains an entire VE UI, but may also contain gadget code like HotCat or ProveIt sourced from other places like bits, see screen shot and Bug 55759.)
+
+[*] The meat of the little Ruby timer script is: 
+
+#CLICK EDIT
+b.a(:title => /Edit this page with VisualEditor/).when_present.click
+#SAVE START TIME
+welcome_start_time = Time.now
+#CLICK CLOSE ON THE WELCOME IFRAME WHEN IT BECOMES CLICKABLE
+b.frame(:index => 1).a(:title => 'Close').when_present.click
+#SAVE END TIME
+welcome_end_time = Time.now
+welcome_load_time = welcome_end_time - welcome_start_time
+puts welcome_load_time.to_s
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381945440,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5zskngbxk4z3y36fzvyt,task_description,invalid
+significant intermittent performance problem in Chrome,"probably not, closing.",1383846541,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"I don't know what significant intermittent performance problem you are observing in Chrome, but I am fairly confident that this is not related to ProveIt, or any other gadget.",1383842467,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"Gadgets are not and never were loaded in our iframes.
+
+The only thing related to gadgets being applied in iframes is their stylesheets. And this is not an explicit action, but a result of the stylesheet link established between the parent and child frame to ensure content looks the same.
+
+Afaik this should not have any significant impact in performance as 1) these styles are loaded in the same request as other styles, 2) the exact same request has been fired and cached already in the parent frame, and as such is pretty much guaranteed to be 304 cached if not already.
+
+Also, in non-debug mode, most stylesheets actually become <style> tags which are cloned to the iframe without any intermittent load.php request (be it a 304 or not).",1383842402,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"I also don't see a reason to load gadgets in the VE frames.  Since it's same-origin, gadgets can reach into the iframe if needed.  E.g.
+
+$( $( '.ve-ui-frame' )[0].contentDocument ).find( '.ve-ui-labeledElement-label' )",1382744657,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"Created attachment 13511
+contents of the invisible iframe
+
+**Attached**: {F12750}",1381945594,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+Bogus phpcs failure in VisualEditor,"https://integration.wikimedia.org/ci/job/mwext-VisualEditor-phpcs-HEAD/1561/console is a bogus failure. The error messages are:
+
+14:41:05 FILE: ...orkspace/mwext-VisualEditor-phpcs-HEAD/maintenance/makeStaticLoader.php
+14:41:05 --------------------------------------------------------------------------------
+14:41:05 FOUND 2 ERROR(S) AFFECTING 2 LINE(S)
+14:41:05 --------------------------------------------------------------------------------
+14:41:05  78 | ERROR | Expected 1 space before ""?""; 3 found
+14:41:05     |       | (Squiz.WhiteSpace.OperatorSpacing.SpacingBefore)
+14:41:05  80 | ERROR | Expected 1 space before "":""; 3 found
+14:41:05     |       | (Squiz.WhiteSpace.OperatorSpacing.SpacingBefore)
+14:41:05 --------------------------------------------------------------------------------
+
+The source code doesn't have 3 spaces before the ?, only a bunch of tabs), but it does have a comment on the preceding line each time. Maybe that's what's confusing phpcs?
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1381502640,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-x2bemat6dbvj4qacn3ja,task_description,declined
+Bogus phpcs failure in VisualEditor,"Looking at the code, the phpcs failure seemed correct, the ternary operators should be at end of line.",1383048850,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-x2bemat6dbvj4qacn3ja,task_subcomment,NA
+Bogus phpcs failure in VisualEditor,Filing this because it will eventually block https://gerrit.wikimedia.org/r/#/c/88896/ once that commit has been cleaned up and reviewed.,1381502717,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-x2bemat6dbvj4qacn3ja,task_subcomment,NA
+Edit conflict: Review your changes performs different as Save page,"**Author:** `felix`
+
+**Description:**
+* Edit one section with VE
+*:Example diff:
+*:+ VEtext
+
+* Provoke edit conflict in another section
+*:Example diff:
+*:+ ConflictText
+
+* Click ""Review your changes"" in VE
+
+* Diff shows
+** the changes made in VE
+** the changes of the edit conflict as reverted (!)
+*:Example diff:
+*:+ VEtext
+*:- ConflictText
+
+* Click ""Save page""
+** Both edits are successfully merged
+*:Example diff:
+*:+ VEtext
+*:+ ConflictText
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55392",1381488000,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bytfsofa3wltd64urfvv,task_description,declined
+Edit conflict: Review your changes performs different as Save page,This is the same behaviour as the wikitext editor - what would you instead suggest VisualEditor (and the wikitext editor) do?,1384846589,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bytfsofa3wltd64urfvv,task_subcomment,NA
+VisualEditor: VE edit button shown on talk pages with titles starting with a full stop (period),"On talk pages that have titles starting with a full stop (period) such as [[talk:.mp]] and [[it:Discussione:.uk]] the button to launch VE is shown despite not being enabled in that namespace. Clicking on it gives the following error message:
+
+Error loading data from server: novenamespace: VisualEditor is not enabled in namespace 1. Would you like to retry?
+
+(incidentally this message is not translated for it.wp)
+
+Possibly this bug has the same cause as bug 55493
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55493",1381282140,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hibjkpd4gxjy4lfkuxhu,task_description,resolved
+VisualEditor: VE edit button shown on talk pages with titles starting with a full stop (period),"We fixed this just this week (this is also bug 38081 - if the page starts with a '.', mw:Title fails and so the code to suppress VE doesn't work), and will be deploying it to MediaWiki.org on Thursday (10 October); assuming that all goes well, it will hit the English Wikipedia next Thursday (17 October).
+
+*** This bug has been marked as a duplicate of bug 38081 ***",1381286891,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hibjkpd4gxjy4lfkuxhu,task_subcomment,NA
+VisualEditor: Does not load on pages with titles starting with a full stop (period),"At least in Firefox 24 on Linux (not tested in other systems) VisualEditor does not load on main namespace pages whose titles begin with a full stop (period). The URL changes and the page reloads but remains in view mode.
+
+Tested at [[.mp]], [[.uk]], [[.300]] and [[.300 Remington American Magnum]] at en.wp and at the .uk articles at it.wp, de.wp, fr.wp and es.wp
+
+The bug does not manifest in other namespaces, e.g. [[User:Thryduulf/.100]] and [[User:.anaconda]] load correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55494",1381281660,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k23jbc4tij5lhe6eeo73,task_description,resolved
+VisualEditor: Does not load on pages with titles starting with a full stop (period),"We fixed this just this week (this is bug 38081), and will be deploying it to MediaWiki.org on Thursday (10 October); assuming that all goes well, it will hit the English Wikipedia next Thursday (17 October).
+
+*** This bug has been marked as a duplicate of bug 38081 ***",1381286833,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k23jbc4tij5lhe6eeo73,task_subcomment,NA
+"VisualEditor: dropdown menus only completely visible at top of page, and disappear lower down page in Vector skin","TeamGale reports:
+
+""while I was getting more down to the page, the drop down menus were getting ""shorter"" and sometimes disappear at the very end. I tried it to many pages to see if it was happening everywhere and it does. I don't know exactly how to describe it that's why I took screencaps from the page. All three are from the same page, in different height. See how the drop down menu of ""more"" can be seen entirely at the top of the page and how it gradually disappear as I get closer to the bottom. It's really weird!! The same thing happens when I am trying to add a wiki link in the article's text and to be honest, that's how I notice the gradually disappearing.""
+
+The screenshot is at [[File:Drop Down Menus.jpg]]
+
+I can reproduce this in Firefox 24 on Linux when using the vector skin, but not when using Monobook. 
+
+Trying to add a link after the end of the first paragraph I get no suggestions when my window is not maximised. Even when it is maximised it has completely disappeared by the end of the page. 
+
+What seems to matter is where the view is, not where the cursor is.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1381012260,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4tqy4h2htavrdjo2k36n,task_description,resolved
+"VisualEditor: dropdown menus only completely visible at top of page, and disappear lower down page in Vector skin","
+
+*** This bug has been marked as a duplicate of bug 55343 ***",1381080286,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4tqy4h2htavrdjo2k36n,task_subcomment,NA
+"VisualEditor: dropdown menus only completely visible at top of page, and disappear lower down page in Vector skin",See also bug 55343,1381056057,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-4tqy4h2htavrdjo2k36n,task_subcomment,NA
+"VisualEditor: dropdown menus only completely visible at top of page, and disappear lower down page in Vector skin","TeamGale didn't give their system details with this report, but from another report of theirs they are most likely using the latest Firefox on Windows 8.",1381012355,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4tqy4h2htavrdjo2k36n,task_subcomment,NA
+[Regression] mediawiki.Title: jQuery.byteLength undefined,"Login at http://en.wikipedia.beta.wmflabs.org/ with VE enabled. 
+
+Click edit on any page to invoke VE.
+
+Page reloads, VE is not invoked. 
+
+Javascript errors: 
+
+Exception thrown by ext.visualEditor.viewPageTarget.init: Object function (selector,context){return new jQuery.fn.init(selector,context,rootjQuery);} has no method 'byteLength' load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151
+TypeError
+ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151
+Exception thrown by ext.gettingstarted.openTask: Object function (selector,context){return new jQuery.fn.init(selector,context,rootjQuery);} has no method 'byteLength' load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151
+TypeError
+ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: critical",1380899400,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-w7zawrtzky3vftelryka,task_description,resolved
+[Regression] mediawiki.Title: jQuery.byteLength undefined,"Change 87593 merged by jenkins-bot:
+mw.Title: Add missing dependency on jquery.byteLength
+
+https://gerrit.wikimedia.org/r/87593",1380906444,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w7zawrtzky3vftelryka,task_subcomment,NA
+[Regression] mediawiki.Title: jQuery.byteLength undefined,"Change 87593 had a related patch set uploaded by Krinkle:
+mw.Title: Add missing dependency on jquery.byteLength
+
+https://gerrit.wikimedia.org/r/87593",1380905932,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w7zawrtzky3vftelryka,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"User report:
+<<[...] The new one (for me at least, perhaps it already existed): when I edit a page in Beta (my sandbox, or a main space page), I get next to the page title two pale blue links, ""edit source / edit beta"", which bring me to the section editing for the lead. I don't get these pale links for other sections, only next to the title. I can't remember these being there, and I can't see the use for them (and if they have a use, they would probably be wanted for other sections as well). Fram (talk) 12:01, 4 October 2013 (UTC) >>
+
+He uses FF 24, I can't reproduce but we have a screenshot at 
+https://en.wikipedia.org/wiki/File:VE_error_Fram_1.jpg .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1380894960,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-u6bt2ddckctrby5sscwl,task_description,invalid
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"(In reply to comment #5)
+> I submitted a step towards potentially fixing this and other editsection and
+> VE-related bugs at https://gerrit.wikimedia.org/r/#/c/87627/ (after recent
+> discussion at [[WP:VPT]]).
+
+Thanks!",1381266111,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,I submitted a step towards potentially fixing this and other editsection and VE-related bugs at https://gerrit.wikimedia.org/r/#/c/87627/ (after recent discussion at [[WP:VPT]]).,1381266063,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"This is caused by the ""Add an [edit] link for the lead section of a page"" gadget on enwiki.
+
+As normal, because gadgets' bugs aren't tracked on Bugzilla, I'm marking this as INVALID, but please do contact the author of the gadget and ask them to fix it. :-(",1381264538,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"Fram, the original reporter, has confirmed that he uses Vector so it does seem to be skin-specific.",1381138526,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"I can confirm that I see this in Firefox 24/Linux/Monobook. I don't see it when using Vector skin. I don't have access to other browsers/systems to test on.
+
+Test page: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575760261",1380909771,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"<<Note that I only get this when the page has at least one section header. Pages without section headers don't have this behaviour. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 14:12, 4 October 2013 (UTC)>>",1380896005,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"```
++----------------------+------+------+-------------+-----------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| dbname               | lang | name | family      | url                               | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |
++----------------------+------+------+-------------+-----------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| bat_smgwiki          | en   | NULL | wikipedia   | http://bat_smg.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| be_x_oldwiki         | en   | NULL | wikipedia   | http://be_x_old.wikipedia.org     |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| cbk_zamwiki          | en   | NULL | wikipedia   | http://cbk_zam.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| centralauth          | en   | NULL | centralauth | NULL                              |    1 | s7.labsdb |         0 |        0 |               0 |                0 |            0 |
+| fiu_vrowiki          | en   | NULL | wikipedia   | http://fiu_vro.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| map_bmswiki          | en   | NULL | wikipedia   | http://map_bms.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| nds_nlwiki           | en   | NULL | wikipedia   | http://nds_nl.wikipedia.org       |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| roa_rupwiki          | en   | NULL | wikipedia   | http://roa_rup.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| roa_rupwiktionary    | en   | NULL | wiktionary  | http://roa_rup.wiktionary.org     |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| roa_tarawiki         | en   | NULL | wikipedia   | http://roa_tara.wikipedia.org     |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| vewikimedia          | en   | NULL | wikimedia   | http://ve.wikimedia.org           |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_classicalwiki     | en   | NULL | wikipedia   | http://zh_classical.wikipedia.org |    1 | s3.labsdb |         0 |        0 |               1 |                1 |            1 |
+| zh_min_nanwiki       | en   | NULL | wikipedia   | http://zh_min_nan.wikipedia.org   |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| zh_min_nanwikibooks  | en   | NULL | wikibooks   | http://zh_min_nan.wikibooks.org   |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_min_nanwikiquote  | en   | NULL | wikiquote   | http://zh_min_nan.wikiquote.org   |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_min_nanwikisource | en   | NULL | wikisource  | http://zh_min_nan.wikisource.org  |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_min_nanwiktionary | en   | NULL | wiktionary  | http://zh_min_nan.wiktionary.org  |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_yuewiki           | en   | NULL | wikipedia   | http://zh_yue.wikipedia.org       |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
++----------------------+------+------+-------------+-----------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+```
+
+For the wikis reported above lang is 'en', name in NULL and URL is wrong (maybe this is the reason for the other missing information). For example isn't http://roa_tara.wikipedia.org but http://roa-tara.wikipedia.org
+
+For all the wikis, 'size' column is always 1. This information can be get from:
+* site_stats.ss_good_articles table of replica db, or
+* API /w/api.php?action=query&meta=siteinfo&format=json&siprop=statistics under ""articles""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48626",1380879960,PHID-USER-6ji4nw2pi3dgjy7tgmhp,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_description,resolved
+Missing or wrong information in meta_p.wiki table,">>! In T56962#1051546, @jayvdb wrote:
+> Is T69476 part of the scope of this task?
+
+No, that should be handled there.
+
+Regarding the `size` column, looking at `maintain-replicas.pl` showed that it should not be `1` for all wikis, so I filed T90084 for that.
+
+I close this task as its original bug has been fixed.",1424404841,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,Is T69476 part of the scope of this task?,1424384247,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"At the moment, there are two wikis apart from `centralauth` that have `name` set to `NULL`:
+
+```
+MariaDB [enwiki_p]> SELECT * FROM meta_p.wiki WHERE name IS NULL;
++-------------+------+------+-------------+------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| dbname      | lang | name | family      | url                          | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |
++-------------+------+------+-------------+------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| qualitywiki | en   | NULL | special     | http://quality.wikimedia.org |    1 | s3.labsdb |         1 |        1 |               0 |                0 |            0 |
+| centralauth | en   | NULL | centralauth | NULL                         |    1 | s7.labsdb |         0 |        0 |               0 |                0 |            0 |
+| ukwikimedia | en   | NULL | wikimedia   | http://uk.wikimedia.org      |    1 | s3.labsdb |         1 |        1 |               0 |                0 |            0 |
++-------------+------+------+-------------+------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+3 rows in set (0.00 sec)
+
+MariaDB [enwiki_p]>
+```
+
+As these are closed wikis I assume that is correct?
+
+Also, there are no wikis with `size` not being `1`:
+
+```
+MariaDB [enwiki_p]> SELECT size, COUNT(*) FROM meta_p.wiki GROUP BY size;
++------+----------+
+| size | COUNT(*) |
++------+----------+
+|    1 |      858 |
++------+----------+
+1 row in set (0.00 sec)
+
+MariaDB [enwiki_p]>
+```
+
+Is this column important to you, @Pietrodn?  Otherwise I'd propose to resolve this task as the main issues seem to have been fixed.",1424287734,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"Change 160945 merged by coren:
+Labs: Fix generation of meta_p.meta
+
+https://gerrit.wikimedia.org/r/160945",1410954296,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"Change 160945 had a related patch set uploaded by coren:
+Labs: Fix generation of meta_p.meta
+
+https://gerrit.wikimedia.org/r/160945",1410954204,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,Now the problem seems to be fixed.,1410954159,PHID-USER-bxdsl6dwnf4xk47wrlkc,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"The meta_p.wiki tables now contains only one row: centralauth.
+
+MariaDB [meta_p]> select * from wiki;
++-------------+------+------+-------------+------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| dbname      | lang | name | family      | url  | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |
++-------------+------+------+-------------+------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| centralauth | en   | NULL | centralauth | NULL |    1 | s7.labsdb |         0 |        0 |               0 |                0 |            0 |
++-------------+------+------+-------------+------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+1 row in set (0.00 sec)",1410936827,PHID-USER-bxdsl6dwnf4xk47wrlkc,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,There was a typo that prevented the size column from being properly set.  Fixed since.,1399342402,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"(In reply to comment #3)
+> (In reply to comment #2)
+> > Also 'is_closed' column is always 0, for all the wikis.
+> 
+> That would be because we do not currently replicate any closed wikis.  :-)
+Ah, ok! Alright :)
+
+> For the other values, things should have been corrected now.  Please check?
+Now it seems ok, except for the 'size' column, is always 1 yet.",1381333801,PHID-USER-6ji4nw2pi3dgjy7tgmhp,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"(In reply to comment #2)
+> Also 'is_closed' column is always 0, for all the wikis.
+
+That would be because we do not currently replicate any closed wikis.  :-)
+
+For the other values, things should have been corrected now.  Please check?",1381326903,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"Also 'is_closed' column is always 0, for all the wikis.",1381326150,PHID-USER-6ji4nw2pi3dgjy7tgmhp,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"Yes, the URL being incorrect is likely the cause of the other errors.  Looking into it.",1380892195,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+"VisualEditor: Marathi/Devanagari: When using jquery.IME, type a word and press space bar = eliminates typed text immediately Typed content disappear while pressing Spacebar","I am using Malayalam Inscript2 IME of ULS for typing in Malayalam Wikipedia. Problem is described here:
+
+1. Open an article from ml.wikipedia (for eg. https://ml.wikipedia.org/wiki/%E0%B4%B8%E0%B5%82%E0%B4%AB%E0%B4%BF )
+2. Edit a section using VE
+3. Add a new line at the end of the section and type a word using ULS IME
+4. Press Spacebar, the typed word disappears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows 7
+**Platform**: PC
+**URL**: http://ml.wikipedia.org",1380877560,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-xkeqdnpvwm2mnuk2p4kq,task_description,duplicate
+"VisualEditor: Marathi/Devanagari: When using jquery.IME, type a word and press space bar = eliminates typed text immediately Typed content disappear while pressing Spacebar","Pretty sure that this is the same issue as bug 53700 - merging.
+
+*** This bug has been marked as a duplicate of bug 53700 ***",1381270703,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xkeqdnpvwm2mnuk2p4kq,task_subcomment,NA
+Editing refs in image descriptions,"As demonstrable in the last image inserted in:
+
+https://de.wikipedia.org/wiki/Tetrahedran
+
+refs inserted in the description of media, here 1), can't be edited. Report:
+
+https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=123123395#Einzelnachweise_in_Bildunterschriften
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380842100,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-bnfed45fsdr7ijiu7iy4,task_description,resolved
+Editing refs in image descriptions,"Happily this is already fixed in the code that just went to MediaWiki.org today, and will be available on dewiki (and elsewhere) in a week's time. Merging with bug 50459.
+
+*** This bug has been marked as a duplicate of bug 50459 ***",1380844957,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bnfed45fsdr7ijiu7iy4,task_subcomment,NA
+Newly inserted templates / transclusions are not floated,"example of the non-float
+
+Reproduced on Windows 7 and Mac OSX 10.8.5 — when a new template is added to an article it does not follow float:right. However, on page save and a re-entry of the VE it is properly floated.
+
+See the attached screenshot. This really breaks the WYSIWYG nature of the VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12578}",1380745680,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-jyvhhwmshuq26opbmerd,task_description,resolved
+Newly inserted templates / transclusions are not floated,"I'm merging this with bug 49784 - agreed that it's a real product fail.
+
+*** This bug has been marked as a duplicate of bug 49784 ***",1380746310,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jyvhhwmshuq26opbmerd,task_subcomment,NA
+"VisualEditor: Create a ""hamburger""-icon (☰) drop down menu for toolbar items which aren't editing tools","Such as:
+* Page settings
+* Help/about/version
+* Switch to source editing
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380708480,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-huguj37vwbp5tlmsngzb,task_description,invalid
+"VisualEditor: Create a ""hamburger""-icon (☰) drop down menu for toolbar items which aren't editing tools","(In reply to comment #0)
+> Such as:
+> * Page settings
+> * Help/about/version
+> * Switch to source editing
+
+Err… this was already done by Trevor many months ago. See https://commons.wikimedia.org/wiki/File:VisualEditor_-_Icon_-_Menu.svg for the version on Commons, let alone the version in the repo…
+
+(In reply to comment #1)
+> https://en.wikipedia.org/wiki/%E2%98%B0
+> 
+> Is using Qián (☰) going to cause problems with Chinese language UI's, or will
+> it require browsers to download additional fonts in order to render it?
+
+No, we're not using a character, we'll use an SVG icon like the rest of the interface.",1380731297,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-huguj37vwbp5tlmsngzb,task_subcomment,NA
+"VisualEditor: Create a ""hamburger""-icon (☰) drop down menu for toolbar items which aren't editing tools","https://en.wikipedia.org/wiki/%E2%98%B0
+
+Is using Qián (☰) going to cause problems with Chinese language UI's, or will it require browsers to download additional fonts in order to render it?",1380731074,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-huguj37vwbp5tlmsngzb,task_subcomment,NA
+Edit tab titles are not consistent,"Edit tab titles are not consistent (on hu.wikipedia):
+
+- If I am logged out, I see tab title ""visualeditor-ca-editsource"", and it opens the source edit page.
+- If I am logged in, and I have opt-outed from VisualEditor, then I see ""vector-view-edit"", and it opens the source edit page.
+- If I am logged in, and I have VisualEditor enabled (default), then I see ""vector-view-edit"", which opens the visual edit page, and also ""visualeditor-ca-editsource"", which opens the source edit page.
+
+Some user on hu.wikipedia complained, that the same ""vector-view-edit"" meant source edit 2 days ago, and it now means visual edit, which is confusing. So we would like to rename both tabs, to be clear for everyone: we want to create a ""Visual edit"" and a ""Source edit"" tab, with the same text for everyone. But this structure makes impossible to set translation according to this, because opt-outed users se the same text for source edit as non-opt-outed users for visual edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380704760,PHID-USER-hfilh4urx5vchfwani3k,PHID-TASK-4iunqtmz3u4jccn23ct7,task_description,resolved
+Edit tab titles are not consistent,"This is intentional - for a week, we deploy VisualEditor for logged-in users before we deploy it for logged-out users. This will be fixed for huwiki on Monday when VisualEditor is enabled by default for logged-out users too. Sorry for the disruption.
+
+*** This bug has been marked as a duplicate of bug 49999 ***",1380835091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4iunqtmz3u4jccn23ct7,task_subcomment,NA
+Delete VisualEditor/core repo,"http://git.wikimedia.org/summary/?r=VisualEditor/core.git
+
+Seems unneeded.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: minor",1380590700,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ar7o222adkj6yo6s5o5w,task_description,declined
+Delete VisualEditor/core repo,"We're about to fill it with content. So… no, please don't.",1380591667,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ar7o222adkj6yo6s5o5w,task_subcomment,NA
+When editing using VisualEditor I see the '♙' character at every newline,"Hi
+Just like the title, if I edit the body of the text, at every newline it enters an ♙ character, and I have to manually delete every time (by writig, going back and deleting).
+
+Also there are many other special characters displayed, like arrows for tab and return. Don't know if it's the same issue.
+
+The wiki is hosted on a CentOS 6.4 box, running latest versions of apache and PHP, under a virtualhost. The client is an OSX 10.9 computer.
+
+Please tell me if you need any additional information.
+
+Thank you.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: Macintosh",1380546240,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-qdobmgita3aclomioanb,task_description,resolved
+When editing using VisualEditor I see the '♙' character at every newline,"Hi there,
+
+This is a break we introduced on Friday, sorry - a fix is now in gerrit 86685 and will be merged in the next few minutes. Up-merging this with bug 54791 reported by our QA team. Thanks for the bug report!
+
+(In reply to comment #0)
+> Also there are many other special characters displayed, like arrows for tab
+> and return. Don't know if it's the same issue.
+
+That's not - this is intentional as a means to differentiate different kinds of whitespace (which show up differently to the user in wikitext, but would otherwise look the same in HTML).
+
+*** This bug has been marked as a duplicate of bug 54791 ***",1380559441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qdobmgita3aclomioanb,task_subcomment,NA
+Images are slow to update in the search index,"Inserting media with VE
+
+Sometimes I cant add image, because it doesnt display. This time at https://cs.wikipedia.org/wiki/Seznam_památných_stromů_v_okrese_Rokycany
+
+adding File:Kařízský dub, pohled.jpg with FF 23.0.1
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**Whiteboard**: cirrus-fixed
+
+**Attached**: {F12341}",1380515400,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_description,resolved
+Images are slow to update in the search index,"
+
+*** This bug has been marked as a duplicate of bug 52782 ***",1382572188,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_subcomment,NA
+Images are slow to update in the search index,"(In reply to comment #2)
+> Doesnt work still to me. Thats why I am opening it again. Once you will
+> update search, lets talk about clossing.
+
+This has nothing to do with VisualEditor; re-assigning.",1382370812,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_subcomment,NA
+Images are slow to update in the search index,"Doesnt work still to me. Thats why I am opening it again. Once you will update search, lets talk about clossing.",1382173897,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_subcomment,NA
+Images are slow to update in the search index,This is because the old search system is slow to update (it now works for me). Happily the new search system (which is coming hopefully soon). Sorry. :-(,1380834938,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_subcomment,NA
+Dragging elements to the end of the page should make a new empty line appear,"When you want to drag an element to the very bottom of the content editable area, the last position available for the cursor is the end of the last sentence. 
+
+Usually you want to place elements not at the end of a line, but right after, in a new line. The behavior expected would be to see a new empty line appearing when you drag an element until the end of a page, and the possibility to drop your element in that empty line.
+
+Tested with the {{Languages}} template at https://www.mediawiki.org/wiki/Groups 
+
+The last cursor position possible is at the end of the sentence: ""... to create your MediaWiki group."" Dropping the template after the last dot puts it at the end of the page, in a new line. The end result is correct, but the behavior is unituitive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51666",1380427800,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-hy35new7rxofajvvqivl,task_description,resolved
+Dragging elements to the end of the page should make a new empty line appear,"(In reply to comment #0)
+> When you want to drag an element to the very bottom of the content editable
+> area, the last position available for the cursor is the end of the last
+> sentence. 
+> 
+> Usually you want to place elements not at the end of a line, but right after,
+> in a new line. The behavior expected would be to see a new empty line
+> appearing when you drag an element until the end of a page, and the
+> possibility to drop your element in that empty line.
+
+Merging this with bug 51666 which I've re-titled.
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > Note also that for me, on
+> > [https://www.mediawiki.org/wiki/Communication?veaction=edit], the ""other
+> > languages"" template at the top is not even visible in VE mode... This is
+> > probably a separate bug though.
+> 
+> Possibly it is or is related to bug 50284
+
+No, this is because of the code inside the ""other languages"" template making assumptions which are true for read mode but not for VisualEditor - I think this is an artefact of bug 50172 and a few other issues.
+
+*** This bug has been marked as a duplicate of bug 51666 ***",1381246558,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hy35new7rxofajvvqivl,task_subcomment,NA
+Dragging elements to the end of the page should make a new empty line appear,"(In reply to comment #1)
+> Note also that for me, on
+> [https://www.mediawiki.org/wiki/Communication?veaction=edit], the ""other
+> languages"" template at the top is not even visible in VE mode... This is
+> probably a separate bug though.
+
+Possibly it is or is related to bug 50284",1381227927,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hy35new7rxofajvvqivl,task_subcomment,NA
+Dragging elements to the end of the page should make a new empty line appear,"**Wikifram** wrote:
+
+Only now noticed this. For me, dropping the template after the last dot was not even possible. I could drop it before the last dot, but not after, so for me it was not simply unintuitive, it was wrong. But now, this has been solved apparently, whether by a new VE version or by a Firefox update I don't know. 
+
+Note also that for me, on [https://www.mediawiki.org/wiki/Communication?veaction=edit], the ""other languages"" template at the top is not even visible in VE mode... This is probably a separate bug though.",1381225378,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hy35new7rxofajvvqivl,task_subcomment,NA
+VisualEditor opt-in preference disappears,"As user Selenium_user on beta labs enwiki, I have set my preference to opt-in to VisualEditor several times, but the preference then gets reset to default (opt-in not set) after a period of some hours.  
+
+This causes failures in the browser tests and I wonder if it is a risk in the production environment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1380234840,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-owimzdmbcsatfp52eoa7,task_description,resolved
+VisualEditor opt-in preference disappears,"
+The fix is to not do a global reset of preferences for the shared test user. :-) 
+
+We will have the ULS tests create a user of their own.",1380642094,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"Great!    Now got to find a fix, ideally the VE feature should set the optin preference.  I am not sure whether you have support for that already.
+
+And sorry for the delay investigating this issue :/",1380588185,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"
+ULS tests are doing it: 
+
+
+tests/browser/features/support/pages/reset_preferences.rb 
+Last indexed a month ago
+1
+2
+3
+4
+class ResetPreferencesPage
+	include PageObject
+	include URL
+	page_url URL.url('Special:Preferences/reset')
+Ruby
+tests/browser/features/step_definitions/common_steps.rb 
+Last indexed 4 days ago
+59
+60
+61
+After('@reset-preferences-after') do |scenario|
+	visit(ResetPreferencesPage)
+	on(ResetPreferencesPage).submit_element.click",1380586091,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"
+this really should not be happening for any test: 
+
+0.2789   6.0M  Start request POST /wiki/Special:Preferences/reset
+
+thanks for pointing that out.",1380585639,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"What led me to suspect it is:
+
+0.2789   6.0M  Start request POST /wiki/Special:Preferences/reset
+HOST: commons.wikimedia.beta.wmflabs.org
+HTTP HEADERS:
+X-REAL-IP: ....  # Some IP address at saucelabs
+X-FORWARDED-PROTO: https
+...
+REFERER: https://commons.wikimedia.beta.wmflabs.org/wiki/Special:Preferences/reset
+COOKIE: ...centralauth_User=Selenium+user .... commonswikiUserName=Selenium+user...
+
+
+See also ""Update how VisualEditor's experimental config works""  https://gerrit.wikimedia.org/r/#/c/84433/  which got deployed on beta on Sep 18th.
+
+
+hashar@deployment-bastion:~$ mwscript eval.php --wiki=enwiki
+> return $wgDefaultUserOptions['visualeditor-enable'] ;
+0
+>
+$
+
+
+So you could add an exception in CommonSettings-labs.php or InitialiseSettings-labs.php to override that value for beta and make sure VE is always opted in.",1380585248,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"I am wondering, isn't it that the default is to disable the opt-in preference on enwiki now?   Thus if the Selenium test rest the user preference, it would end up opting out of VE :(
+
+Can you try in your test to explicitly set the user preference?",1380584760,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,VisualEditor opt-in preference unset again overnight PDT Sept 27.,1380557168,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"
+I have just enabled VE manually in beta labs for Selenium_user. I suspect it will become disabled soon. 
+
+Is it possible that the automatic run of update.php (or whatever updates the db) would un-set that preference?",1380292740,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"The Selenium_user on enwiki has the following preferences right now:
+
+[""visualeditor-enable""]=> int(0)
+[""visualeditor-enable-experimental""]=>  int(1)
+[""visualeditor-betatempdisable""]=> int(0)
+
+So VE is actually disabled.
+
+Maybe some test is disabling the option while other set it?   Tests relying on VE should probably set the user preference through the API before the test run.",1380262166,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor: (silently) renumbering references,"Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 :
+<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>
+
+The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:
+<<About half of the 18 references I typed into the article on Homesickness disappeared between yesterday and today. I was certain to follow the Save Changes procedure, but many different references reverted to the same single reference. [...] Same bug today. In VE, I placed the cursor in the text, chose ""Reference"" from the ""More"" menu, added a reference, (It appeared as it should with the appropriate numerical superscript), Saved the work, returned to check the page...references disappeared from the list. - Window 8, Chrome >>.
+
+TeamGale adds:
+<<Hello...I have the same problem [...]. I didn't realized that it happened while I was editing. I only saw it when I saved the article and the number of the references had decreased. This https://en.wikipedia.org/w/index.php?title=Michael_Giannatos&diff=next&oldid=573583391 is the change I was doing when it happened. Could it be related to editing a table with beta? Probably not since I don't see any table on Christopher Thurber's article. After I re-added the references and the new table, every time I click ""edit beta"" the refs are gone! Before I even do any change! Basically I can't use beta at all on this article! I don't have any issues using the source but, if it's something simple that can be done with beta, I prefer to do it with it. But I can't. Just wanted to say that this is happening to other articles as well. And it's possible to happen and people don't see it. That would be a problem to a long article with lots of references... Mozilla 21, Windows 8.>>
+
+TeamGale again:
+<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] 
+Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>>
+
+I think I saw this renumbering issue at it.wp as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380214860,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gjqblxpe4th4o7zcpret,task_description,resolved
+VisualEditor: (silently) renumbering references,"Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry!
+
+*** This bug has been marked as a duplicate of bug 54341 ***",1380220185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gjqblxpe4th4o7zcpret,task_subcomment,NA
+VisualEditor: Section-editing lands user at wrong URL post-save,"After successfully section-editing <https://en.wikipedia.org/w/index.php?title=Black_Mail_%281973_film%29&section=2&veaction=edit> using VisualEditor, I land at <https://en.wikipedia.org/w/index.php?title=Black_Mail_%281973_film%29&section=2>.
+
+This shouldn't happen. &section=2 doesn't do anything with the implicit &action=view.
+
+Possibly related to bug 53089.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380209340,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-xrx5soggiup6jgpqpzkt,task_description,resolved
+VisualEditor: Section-editing lands user at wrong URL post-save,"
+
+*** This bug has been marked as a duplicate of bug 53089 ***",1392058252,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xrx5soggiup6jgpqpzkt,task_subcomment,NA
+"VisualEditor: Right half of toolbar disappears when image caption on first line contains ""page "" followed by any string","When an image caption on the first line of a page contains the string ""page "" (including the trailing space) followed by any text the right half of the VisualEditor toolbar disappears (everything right of ""more""). This includes the save button so edits cannot be saved (hence the ""major"" severity)
+
+This is likely related to either bug 54379 (same symptoms) or bug 53312 (same trigger).
+
+Comments on the VE/F report at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=574608525#Odd_one suggest this might be restricted to FireFox.
+
+Minimal test: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=574608905
+Real-world example: https://en.wikipedia.org/w/index.php?title=Clarke,_Irwin_%26_Company&oldid=574526057
+
+To reproduce:
+1. Create a page with any image on the first line of page
+2. Give the image a caption containing the string ""page "" (including the trailing space) followed by any text.
+3. Save the page
+4. Load the page in VE and observe the right half of the editing toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53312
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54379",1380206280,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kvr63y5we4pdqpvagdka,task_description,resolved
+"VisualEditor: Right half of toolbar disappears when image caption on first line contains ""page "" followed by any string","As far as I can tell this was fixed when bug 53312 was fixed (and for the same reason).
+
+*** This bug has been marked as a duplicate of bug 53312 ***",1393531206,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kvr63y5we4pdqpvagdka,task_subcomment,NA
+"VisualEditor: Right half of toolbar disappears when image caption on first line contains ""page "" followed by any string","Can't reproduce on Chrome, looks like Ff issue.",1380222773,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-kvr63y5we4pdqpvagdka,task_subcomment,NA
+"VisualEditor: Right half of toolbar disappears when image caption on first line contains ""page "" followed by any string","There may be regression involved with this: The toolbar presented properly with the ""page "" string included in the first line for several VE edits over August and September, then the problem was observed Sept. 25.  No change in machine, OS, or browser at the time.",1380216001,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-kvr63y5we4pdqpvagdka,task_subcomment,NA
+wikitech.wikimedia.org needs to have VE enabled,"'coz I likes it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380197400,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-pv364hftdbapyxednn7m,task_description,invalid
+wikitech.wikimedia.org needs to have VE enabled,"(In reply to comment #2)
+> So there was ' Enable VisualEditor (only in the main and user namespaces)'
+> and
+> ' Temporarily disable VisualEditor while it is in beta' in preferences, and
+> they were both unchecked.
+Hah, I wasn't aware it was possible to have both preferences visible at once. That's probably a bug. Either way, you need to both have the ""enable"" box checked and have the ""disable"" box unchecked.",1380248015,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pv364hftdbapyxednn7m,task_subcomment,NA
+wikitech.wikimedia.org needs to have VE enabled,"So there was ' Enable VisualEditor (only in the main and user namespaces)' and ' Temporarily disable VisualEditor while it is in beta' in preferences, and they were both unchecked.",1380247009,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-pv364hftdbapyxednn7m,task_subcomment,NA
+wikitech.wikimedia.org needs to have VE enabled,It already does...,1380217469,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-pv364hftdbapyxednn7m,task_subcomment,NA
+"VisualEditor: Linux font stack sometimes lies about font width, leading to odd wrapping of text in format menu","subhead shows ""2"" in the wrong place
+
+seen in Firefox not in Chrome:  
+
+choose some text and pick a headings format.  Subheads with numbers show the number below the selectbox.  see screen shot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12017}",1380146220,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-tchh23qe4nddxeojdetp,task_description,resolved
+"VisualEditor: Linux font stack sometimes lies about font width, leading to odd wrapping of text in format menu",This was the Linux-wrong-width-of-fonts bug that was fixed a few months ago.,1399644958,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tchh23qe4nddxeojdetp,task_subcomment,NA
+"VisualEditor: Linux font stack sometimes lies about font width, leading to odd wrapping of text in format menu","Created attachment 13378
+shows '3' in the wrong place
+
+**Attached**: {F12018}",1380146299,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-tchh23qe4nddxeojdetp,task_subcomment,NA
+update other repos to qa/browsertests practices,"visualeditor browser tests don't use MEDIAWIKI_PASSWORD, they still use secret.yaml.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380120060,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-xaefdkhei34lxghlfb26,task_description,resolved
+update other repos to qa/browsertests practices,"
+
+*** This bug has been marked as a duplicate of bug 53579 ***",1381410415,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-xaefdkhei34lxghlfb26,task_subcomment,NA
+VisualEditor: Aborting the insertion of a formula should not insert any content,"If you click to use LaTeX, the ""math editor"" option, you cannot cancel or escape out of input.  VisualEditor adds the <math></math> tags regardless and this can only be removed by saving and going to source.
+
+Ideally, a cancel [X] or keyboard options should work to remove this.
+
+https://www.mediawiki.org/w/index.php?title=User:Keegan_(WMF)/sandbox&action=history
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380089700,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-bj5auvkiqa4ukpb3i76l,task_description,resolved
+VisualEditor: Aborting the insertion of a formula should not insert any content,This was fixed a long time ago; sorry for the slow triage.,1394480263,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bj5auvkiqa4ukpb3i76l,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Sikuli ( http://www.sikuli.org ) is a tool for testing desktop interactions, such as mouse clicks and keyboard typing.
+
+This tool is needed for testing typing in different languages, because the usual WebDriver tests are not able to generate proper keyboard events that completely emulate typing in advanced input methods for Japanese, Chinese and Indic scripts. We have many bugs in this area in the VisualEditor (e.g. Bug 52716), so we need proper regression testing.
+
+This week I worked with Željko in the WMF office and we built a prototype test that uses Sikuli to test typing in Japanese:
+https://gerrit.wikimedia.org/r/#/c/83966/
+
+This works on Željko's laptop. The next step is to get it working on the virtual clients that run our continuous integration tests.
+
+Thank you!
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1379701560,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dxtpzjislp3ykzi64aen,task_description,declined
+Add Sikuli to the machines that run browser tests,"You can also find other people discussing using Sikuli with xvfb, e.g. https://github.com/jatalahd/SikuliRobotLibrary/wiki/Hints-and-Tips",1425618435,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,">>! In T56393#1087507, @zeljkofilipin wrote:
+> @Mattflaschen the last time I have checked sikuli web page, it explicitly said running headless is not supported. Maybe something changed in the meantime.
+
+I think it depends on how you define ""headless"".  Sometimes it means ""without anything related to Xorg whatsoever"", but oftentimes it just means ""without a normal X server installation and associated drivers"" or ""without a physical monitor/physical video card"".
+
+https://answers.launchpad.net/sikuli/+question/248704#comment-1 is quite clear that he got it working on Amazon Web Services (presumably Elastic Compute Cloud) and Jenkins.  This is pretty similar to our setup, except we use OpenStack instead of AWS (of course there are other differences, but there doesn't seem to be any unsolvable issue).
+
+[xvfb](https://en.wikipedia.org/wiki/Xvfb) ([Jenkins plugin](https://wiki.jenkins-ci.org/display/JENKINS/Xvfb+Plugin)) is an established tool for this, so the Launchpad comment makes sense.",1425618258,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"@Mattflaschen the last time I have checked sikuli web page, it explicitly said running headless is not supported. Maybe something changed in the meantime.",1425459423,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Did anyone investigate using it headless with Xvfb?  People have gotten this working with Linux and Jenkins (see for example https://answers.launchpad.net/sikuli/+question/248704#comment-1 ).  Their setup differs, but it shows a fully automated headless installation can work.",1425442579,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 165204 merged by Dzahn:
+contint: Sikuli is no longer used anywhere
+
+https://gerrit.wikimedia.org/r/165204",1412969442,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 165204 had a related patch set uploaded by Zfilipin:
+contint: Sikuli is no longer used anywhere
+
+https://gerrit.wikimedia.org/r/165204",1412692379,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 83966 abandoned by Zfilipin:
+[WIP] [BrowserTest] Testing typing in VisualEditor
+
+Reason:
+Sikuli is not the way to go. We will investigate another tool.
+
+https://gerrit.wikimedia.org/r/83966",1406638159,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,Resolving. See comment #9 for details. Please reopen if you think Sikuli is the way to go.,1403988818,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"After further investigation with Amir today, looks like Sikuli does not work with headless machines: ""The system running Sikuli scripts or any apps using SikuliX features must have a real screen connected. So called headless systems are not supported (Java restriction).""
+
+1: http://www.sikulix.com/quickstart.html",1396537515,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"No, it is not really active yet.",1390743741,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Amir, this patch was merged, can this be closed?",1390743366,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 102141 merged by ArielGlenn:
+contint: install libsikuli-script-java for browser tests
+
+https://gerrit.wikimedia.org/r/102141",1387290472,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"I have deployed the package libsikuli-script-java on the integration-selenium-driver.pmtpa.wmflabs instance.  The script is available as /usr/bin/sikuli
+
+Could you craft a simple change that would attempt to run a single browser test using sikuli ?",1387290113,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 102141 had a related patch set uploaded by Hashar:
+contint: install libsikuli-script-java for browser tests
+
+https://gerrit.wikimedia.org/r/102141",1387289655,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Good news: sikuli has been packaged for Debian/Ubuntu. There is a package libsikuli-script-java which seems to provide the needed material:
+
+http://packages.ubuntu.com/precise/all/libsikuli-script-java/filelist
+
+I have no clue how to launch the tests though. Maybe we just have to use /usr/bin/sikuli ?",1387289374,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 83966 had a related patch set uploaded by Zfilipin:
+[WIP] [Browser test] Testing typing in VisualEditor
+
+https://gerrit.wikimedia.org/r/83966",1387288509,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,Moving from CI to QA,1379709008,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+VisualEditor: Behaviour of <pre> tags,"VE allows editing text between <pre>...</pre> tags.
+That is, you seem to be able, for example, to add working wikilinks and references. Once you save though, everything is rendered as wikicode, as in [[France]] and <ref>France</ref>, and of course is not clickable.
+Thryduulf argues that ""VE shouldn't show it as working if it won't work after saving"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379694480,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6las75m7yq6t6y42jony,task_description,invalid
+VisualEditor: Behaviour of <pre> tags,"Content that is pre-formatted is not wrapped in <pre> tags but with space-indented-preformatting, which does work with wikitext structures.",1415881409,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6las75m7yq6t6y42jony,task_subcomment,NA
+VisualEditor: Some templates with images show full size images on Swedish Wikipedia,"In some templates (e.g. Template:Infobox fornminne) on Swedish Wikipedia, the image in it is shown in full size when you enter VE. 
+
+Article: https://sv.wikipedia.org/wiki/S%C3%B6dermanlands_runinskrifter_305
+Screencast: https://dl.dropboxusercontent.com/u/8363895/out-8.ogv
+
+It does not behave like that for all templates though. In an article with Template:Kommunfakta is seems to work fine. E.g. https://sv.wikipedia.org/wiki/Botkyrka_kommun
+
+Behaviour is observed from two different users and in both Firefox and Chromium.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1379671920,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-um6o7aq2fxsloslxu5y5,task_description,resolved
+VisualEditor: Some templates with images show full size images on Swedish Wikipedia,"Given the above comment and lack of further reports, I'm marking this as a duplicate of bug 51628
+
+*** This bug has been marked as a duplicate of bug 51628 ***",1380930193,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-um6o7aq2fxsloslxu5y5,task_subcomment,NA
+VisualEditor: Some templates with images show full size images on Swedish Wikipedia,"Yes probably, I did did this change: 
+
+https://sv.wikipedia.org/w/index.php?title=Mall:Infobox_fornminne&diff=prev&oldid=23823659
+
+and now it seems to behave correctly in articles using that template. If I find the same error on other articles, I'll try to se if this is it first.",1380026528,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-um6o7aq2fxsloslxu5y5,task_subcomment,NA
+VisualEditor: Some templates with images show full size images on Swedish Wikipedia,"Could this be bug 51628? i.e. an image size being specified as e.g. ""250px"" in a field that is expecting e.g. ""250""
+
+It seems very likely but I can't read the Swedish source code to check.",1380024894,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-um6o7aq2fxsloslxu5y5,task_subcomment,NA
+VisualEditor: Consistency when restoring a page,"<<[...] When you edit an old version of a page, you get the ""save page"" at the top of the page, but a ""restore page"" button instead of the ""save page"" button at the edit summary page, even if you have made changes in the older version (and thus aren't simply restoring it). Why we have two different buttons (save and restore), when we have only one name otherwise, isn't clear. Beneath the ""restore page "" button, the small text says ""By clicking the ""save page"" button, you agree..."". It doesn't indicate what I agree to by clicking the ""restore page"" button though... Fram (talk) 14:08, 19 September 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379602800,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-yofovlast3zou4zon7j5,task_description,declined
+VisualEditor: Consistency when restoring a page,Reminding the user that they are editing from an old version and restoring it (with any changes they have made) over the top of the current version of the page is intentional. WONTFIXing.,1383767339,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yofovlast3zou4zon7j5,task_subcomment,NA
+VisualEditor: blue template overlay overlaps other page elements,"Try clicking the commons template in https://pl.wikipedia.org/wiki/Omega_Centauri?veaction=edit for an example. This bug appeared a while back, and seems to have regressed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50970",1379555760,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-n4ayvtd5iz5jguzeqtvl,task_description,resolved
+VisualEditor: blue template overlay overlaps other page elements,"
+
+*** This bug has been marked as a duplicate of bug 51933 ***",1402294829,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n4ayvtd5iz5jguzeqtvl,task_subcomment,NA
+VisualEditor: blue template overlay overlaps other page elements,This is because we wrap generated content in a div for ease of replacement. Arguably we shouldn't.,1379696782,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-n4ayvtd5iz5jguzeqtvl,task_subcomment,NA
+VisualEditor: Media items are inserted after selection and do not replace them,"**Author:** `renukaalurkar`
+
+**Description:**
+1)Log into http://en.wikipedia.beta.wmflabs.org
+2)Go to your user page
+3)Click on Edit beta tab
+4)Click on More
+5)Click Media
+6)Enter santa claus, select a image from the selection of images
+7)Select the image(the image is displayed in light blue)
+8)Again click on More, then Media and select another image.
+
+Expected:The original/old image should be replaced by the new image.
+Observed: The new image is added and the original image is also displayed.
+
+Another observation: Also, suppose there are 4 images Image1, Image2, Image3, Image4 one below the other. If Image2 is selected and I try to replace it with a new image, the new image appears in the place of Image3(instead of Image2).
+
+Observed on Firefox and Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51033",1379530500,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ql37zwei7lw6idcpnjvx,task_description,declined
+VisualEditor: Media items are inserted after selection and do not replace them,"Yes, confirming that this is intentional; closing as ""WONTFIX"". I agree that changing in line with bug 51033 would make more sense.",1380657485,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ql37zwei7lw6idcpnjvx,task_subcomment,NA
+VisualEditor: Media items are inserted after selection and do not replace them,"I can confirm this is the current behaviour, and that both points are due to the same reason: new images are inserted immediately after a selected image.
+
+However I'm not sure that this behaviour is incorrect though as it is consistent with what happens when a user inserts media or a template with text selected (the template/media is inserted after the selection rather than overwriting it) - see bug 52460.
+
+There is an open request for the media settings dialog to allow an image to be easily changed though (bug 51033), which I think is a better way to handle this.",1380657191,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ql37zwei7lw6idcpnjvx,task_subcomment,NA
+VisualEditor: Adding bold/italics to spaces before/after a word results in ugly wikitext,"Which is something like '' this '' as opposed to something like ''that''. Of course this is also true for the source editor, but since the wikilink tool already gets rid of spaces at the beginning or at the end of a word, I wanted to make sure this can/should also be done when just formatting it (and it's being requested).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379509800,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mlek6l25jsi4523n6c4x,task_description,resolved
+VisualEditor: Adding bold/italics to spaces before/after a word results in ugly wikitext,"This will be fixed by bug 52037.
+
+*** This bug has been marked as a duplicate of bug 52037 ***",1383767551,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mlek6l25jsi4523n6c4x,task_subcomment,NA
+VisualEditor: Adding bold/italics to spaces before/after a word results in ugly wikitext,"User Steven at fr.wp asks that VE somehow recognizes and avoids that formatting is applied to spaces, since this results in ugly wikitext.
+He suggests that spaces get highlighted so that people can easily recognize them; they might become black (when ""bold"" is applied) or grey (when ""italics"" is applied).",1382971506,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mlek6l25jsi4523n6c4x,task_subcomment,NA
+VisualEditor: prevent creating internal links with no displayed text or warn this is happening,"It is not easy, but you can create an empty wikilink with VE, https://en.wikipedia.org/w/index.php?title=Ascending_cholangitis&curid=5544827&diff=572776141&oldid=566427601 (I was able to reproduce that somehow, I think I just added the link to an empty space).
+I can't imagine a situation where this is desirable or useful, please correct me if I am wrong.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379502900,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dfnjvi4ebxg4qf7ygljp,task_description,resolved
+VisualEditor: prevent creating internal links with no displayed text or warn this is happening,"Merging with bug 37835.
+
+*** This bug has been marked as a duplicate of bug 37835 ***",1380072033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dfnjvi4ebxg4qf7ygljp,task_subcomment,NA
+visible parsoid HTML in existing Flow content on toro,"I updated Flow, Parsoid, and VisualEditor on toro. Adding a new post worked fine and brought up VE (after a long delay during which the text area should probably be locked) and I could WYSIWYG. \o/
+
+But existing summary and some posts on http://toro.wmflabs.org/wiki/Special:Flow/Sandbox_2 that have images and links in them show stuff like
+  <a rel=""mw:WikiLink"" href="".//Subpage"" data-parsoid=""{""stx"":""simple"",""a"":{""href"":"".//Subpage""},""sa"":{""href"":""/Subpage""},""dsr"":[89,101,2,2]}"">
+
+suggesting Flow is having problems figuring out Parsoid HTML content.
+
+I had set $wgFlowUseParsoid=true, now I think obsolete. I tried setting $wgFlowContentFormat='html', didn't seem to change behavior.
+
+Firebug reported some XHR errors, possibly from some VE API call, but now not.
+
+If the issue is existing content doesn't render right, this is fine to mark WONTFIX. We haven't promised data compatibility yet.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1379482140,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-qjg3q7wq3q3awr64hcmy,task_description,resolved
+visible parsoid HTML in existing Flow content on toro,"(In reply to comment #2)
+> This is due to us previously not tracking what kind of content was stored in
+> the field.
+Yup, flow_revision rev_flags had just 'utf-8'.
+
+> UPDATE flow_revision set rev_flags = CONCAT(rev_flags, ',html' ) WHERE
+> rev_flags NOT LIKE '%html%' and rev_flags NOT LIKE '%wikitext%';
+
+It worked! (now Toro has other errors...)",1379545289,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-qjg3q7wq3q3awr64hcmy,task_subcomment,NA
+visible parsoid HTML in existing Flow content on toro,"This is due to us previously not tracking what kind of content was stored in the field.  We now store a value of either 'html' or 'wikitext' in the content flags of the revision.  Not highly efficient, but the following query would fix the issue:
+
+
+UPDATE flow_revision set rev_flags = CONCAT(rev_flags, ',html' ) WHERE rev_flags NOT LIKE '%html%' and rev_flags NOT LIKE '%wikitext%';
+
+Untested, but should work.  Not sure if its worthwhile to build out the proper maintenance script to migrate.",1379515263,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-qjg3q7wq3q3awr64hcmy,task_subcomment,NA
+visible parsoid HTML in existing Flow content on toro,Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/185,1379483847,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-qjg3q7wq3q3awr64hcmy,task_subcomment,NA
+VisualEditor: Dimensions of small images are lost in rendering,"Images that have thumbnail sizes that are larger than the original should be rendered at the specified size, not the size of the original.
+
+MediaWiki core does this, but somewhere between MediaWiki/Parsoid/VisualEditor the specified dimensions are lost.
+
+
+For example, on https://www.mediawiki.org/wiki/VisualEditor/Team there are various uses of [[File:Wikimedia_Foundation_office_camera_shy.png]] (of which the full size is 140px). The thumbnail size on that page is 150px, and when viewing the page normally it is rendered at 150px (browser scales up from 140px non-thumb url), but when editing in VisualEditor the node has a width attribtue of 140 instead of 150.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379390340,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-bd72y7iiei67kbxti76b,task_description,resolved
+VisualEditor: Dimensions of small images are lost in rendering,Re-checked on https://www.mediawiki.org/wiki/VisualEditor/Team - seems to be fixed.,1415912062,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-bd72y7iiei67kbxti76b,task_subcomment,NA
+VisualEditor: Dimensions of small images are lost in rendering,Fixed in 2013.,1415881118,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bd72y7iiei67kbxti76b,task_subcomment,NA
+Cant edit as logged in,"Using FF 23.0.1 and Google Chrome 29.0.1547.66 m. Try edit w:en:Ondine's curse from a section #Treatment and prognosis. When logged the page shows to be in process, but never allowes editing. Why I log of editing via VE is possible within seconds.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1379362020,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-sj7ezonvgeb3be62737a,task_description,invalid
+Cant edit as logged in,"OK, thank you.",1379399232,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-sj7ezonvgeb3be62737a,task_subcomment,NA
+Cant edit as logged in,"This sounds like you have a gadget or user script that is breaking VisualEditor - I can make an edit successfully: https://en.wikipedia.org/w/index.php?title=Ondine%27s_curse&diff=573233549&oldid=565577837
+
+If you disable your scripts and gadgets one-by-one you should be able to discover which one causes the problem, which will allow you to notify the author that their code is broken and needs to be fixed.
+
+Marking as ""INVALID"" as gadgets are not tracked in Bugzilla but on-wiki. Sorry for the disruption - if you need a developer to explain to the offending gadget's author how to fix their code, please direct the author to us in IRC at #mediawiki-visualeditor, on e-mail or here on Bugzilla.",1379376765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sj7ezonvgeb3be62737a,task_subcomment,NA
+Cant edit as logged in,"Sorry for mispeling. ""When I log off...""",1379362130,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-sj7ezonvgeb3be62737a,task_subcomment,NA
+VisualEditor: Edit summary field loses focus when pasting (Firefox),"When pasting some text into the edit summary box in Firefox 23 (via Ctrl+V or context menu), the paste occurs, but the edit summary box loses focus.
+
+Possibly related to bug 53632??
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378792920,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-pdpn7hvlculri4ccy42t,task_description,resolved
+VisualEditor: Edit summary field loses focus when pasting (Firefox),"Now that the edit summary is in its own window, this bug has gone away. I don't know whether the plan is to eventually return to the edit confirmation flyout - if so this bug may well reappear.",1393634141,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-pdpn7hvlculri4ccy42t,task_subcomment,NA
+Templates and tables {{infobox ship begin}},"This is going to give you a headache
+
+{{Infobox ship begin}}
+http://en.wikipedia.org/wiki/Template:Infobox_ship_begin
+is used in 26840 pages. I provides styling for tables used to make infoboxes relating to ships. It is used like
+
+{|{{Infobox ship begin}}
+{{Infobox ship image
+|Ship image=[[File:Whydah-model.jpg|300px]]
+|Ship caption=The ''Whydah Gally'' (1716–1717)
+}}
+{{Infobox Ship Career
+...
+}}
+|-
+|Commanded by:
+|Cap't. [[Lawrence Prince]]
+...
+|}
+
+The template transcludes {{WPMILHIST Infobox style}} which provides CSS styling
+class=""infobox {{#if:{{{2|}}}|{{{2}}}}}"" style=""float: right; clear: right; width: 315px; border-spacing: 2px; text-align: left; font-size: 90%;""
+So the table start tag and its styling are separate.
+
+Unsurprisingly VE fails to edit pages with this template correctly. The following was reported at 
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=572065469
+
+Open the article in the visual editor, e.g. by visiting https://en.wikipedia.org/wiki/Whydah_Gally?veaction=edit
+Observe the article now leads with the out-of-place text 
+ <nowiki>class=""infobox "" style=""float: right; clear: right; width: 315px; border-spacing: 2px; text-align: left; font-size: 90%;""</nowiki>
+try to click ""save page"" but note that it is not active
+make a trivial change so that ""save page"" is active.  Click it
+Click ""review your changes"", not that it says that
+<nowiki>{{Italic title}}{|{{Infobox ship begin}}</nowiki>
+was replaced with
+<nowiki>{{Italic title}}{{Infobox ship begin}}
+{|{{Infobox ship begin}}</nowiki>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378673760,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-lxnv4tg7oifuczocddhi,task_description,resolved
+Templates and tables {{infobox ship begin}},"
+
+*** This bug has been marked as a duplicate of bug 53139 ***",1386015391,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-lxnv4tg7oifuczocddhi,task_subcomment,NA
+Templates and tables {{infobox ship begin}},"Thanks for filing the report. We should have a fix for the edit corruption bug soon (it will be fixed as part of a patch that Arlo is working on). More later on the other parts of the bug, once we discuss how to handle this.",1378861053,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-lxnv4tg7oifuczocddhi,task_subcomment,NA
+VisualEditor: Disallow media items in other media items' captions,"This is a strange edit, where a new editor inserted an image in the image description of an existing image. A bug or something that should be able to be done? 
+
+https://sv.wikipedia.org/w/index.php?title=Dry_Martini&diff=prev&oldid=23709630
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378584900,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-zomjkczfpnrvxzpe4yzr,task_description,invalid
+VisualEditor: Disallow media items in other media items' captions,"Yeah, this is valid (if odd) wikitext, and so VisualEditor supports it.",1383759108,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zomjkczfpnrvxzpe4yzr,task_subcomment,NA
+VisualEditor: Disallow media items in other media items' captions,"I can't think where off the top of my head, but I have seen small inline images in image descriptions at en.wp before. I think it was being used as a key for the main image or something like that.
+
+It's not common, but its the sort of thing that could be useful on occasion.",1379685701,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-zomjkczfpnrvxzpe4yzr,task_subcomment,NA
+"When editing an infobox, the labels are sorted alphabetically and not in the original order","**Author:** `lionel.allorge`
+
+**Description:**
+In an infobox, items are in a certain logical order, for exemple, the image item and the caption are next to each other but the VisualEditor sort them alphabetically making it more difficult to find them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1378551060,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hesseird5ugq7qigg32p,task_description,resolved
+"When editing an infobox, the labels are sorted alphabetically and not in the original order","Indeed, this is not optimal. I'm marking this as a duplicate of bug 51930 which offers a way to sort this. Unfortunately that depends on bug 53608 which is presently not assigned to anyone to work on.
+
+*** This bug has been marked as a duplicate of bug 51930 ***",1380655447,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hesseird5ugq7qigg32p,task_subcomment,NA
+AssessmentBar gadget clashes with VisualEditor edit surface,"Bug pic
+
+Should this happen or shouldn't it?
+Btw, steps:
+1*  Install AssessmentBar from https://en.wikipedia.org/wiki/User:YuviPanda/AssessmentBar
+2* Go to an article.
+3* Go down to a picture or find the infobox.
+4* Click on the picture or infobox (when it's halfway through the AssessmentBar) and it will highlight the AssessmentBar (treating it like a picture or an infobox) AND/OR Click on the part of the AssessmentBar where the picture or infobox is getting highlighted and the infobox or picture will get selected instead of the AssessmentBar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11559}",1378540620,PHID-USER-wel3wo6tppcxgnrthxls,PHID-TASK-djpv4d2tw7he7bcaiwgo,task_description,invalid
+AssessmentBar gadget clashes with VisualEditor edit surface,"Thanks.
+As we don't track specific gadgets in Bugzilla this should likely be reported under https://en.wikipedia.org/wiki/User_talk:YuviPanda/AssessmentBar instead.
+
+Closing as INVALID because Bugzilla is not the right place to follow up on user scripts, not because there is no bug that should get fixed.",1378918457,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-djpv4d2tw7he7bcaiwgo,task_subcomment,NA
+AssessmentBar gadget clashes with VisualEditor edit surface,"Moving out of VisualEditor; in general, gadgets have to be made to work with VisualEditor and not the other way around.",1378914055,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-djpv4d2tw7he7bcaiwgo,task_subcomment,NA
+AssessmentBar gadget clashes with VisualEditor edit surface,CC'ing Yuvi as this covers AssessmentBar,1378909636,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-djpv4d2tw7he7bcaiwgo,task_subcomment,NA
+VisualEditor: weird behavior with double square brackets,"Try to start a line with a wikilinked word as you might do in the source editor.
+
+1) Typing the opening double square brackets will not trigger the no-markup warning.
+2) The opening brackets will immediately disappear, the closing ones will stay.
+3) When you reach the second closing bracket, VE will also add another one on the following line. (If instead of moving to step 4 you use the keyboard arrows around the word, you will not be able anymore to type something outside the brackets, and will need your mouse to place yourself outside of them).
+4) Keep typing something instead, then press Enter: whatever you added is automatically copied to the next line, while the ""third"" square bracket is furtherly moved onto the next line.
+5) Now add the brackets to an already existing word, correctly triggering the warning. Save anyway.
+6) Review the changes. The brackets that triggered the warning did not trigger the nowiki tags as well. An opening one and a closing one are gone, and what is left is weird anyway. (This can also be triggered before saving by hitting Back Space, but I can't say where).
+The brackets that we added in the first place are all gone, the duplicated text is gone as well, just a lonely closing bracket stands still.
+
+https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=61362482&oldid=61361463
+
+Reminds me of https://bugzilla.wikimedia.org/show_bug.cgi?id=53079, actually.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57207",1378482300,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ktfyzhjkb3urubsydtou,task_description,declined
+VisualEditor: weird behavior with double square brackets,"I think this may have been a cacheing error? I can't reproduce, but it feels a lot like bug 53079, yes.",1383759476,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ktfyzhjkb3urubsydtou,task_subcomment,NA
+"VisualEditor: Editor changed a parameter in a template, but the parameter was removed when they clicked ""Apply Changes""","A user at it.wp reports that he could not successfully replace a picture with this edit https://it.wikipedia.org/w/index.php?title=Castello_di_Serravalle_%28Bosa%29&diff=61339995&oldid=61339964, although he managed to do so on other occasions, so he knows how it works.
+He just replaced Bosa Castle.jpg with Veduta del Castello.JPG, and correctly previewed the latter.
+But upon saving, the pic was gone - the field is empty. He tried again later, and managed to reproduce this behavior.
+Other users, including me, are not able to reproduce this.
+He's using Chrome with Snow Leopard. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62366",1378478400,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-53pjjq3mogcsnoshnrpu,task_description,declined
+"VisualEditor: Editor changed a parameter in a template, but the parameter was removed when they clicked ""Apply Changes""","I can't quite understand this bug report - the user edited the template, changed the parameter for the image name, but when they applied the changes, the parameter was removed (and so no image)?
+
+I'm going to mark as WORKSFORME, but please re-open if anyone can reproduce.",1383758872,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-53pjjq3mogcsnoshnrpu,task_subcomment,NA
+"VisualEditor: Wikitext warning not triggered by <references />, <i>, etc.","en.wp user Fram reports:
+""When I add something that VE decides needs ""nowiki"", it usually gives the warning ""Wikitext markup detected"". However, when I add <references/> to the bottom of a page, he wraps it in ""nowiki""s, but no warning appears (while it does work with e.g. {{reflist}})""
+
+My testing at https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox2&diff=571756019&oldid=570197356 shows that <i> and <small> also get nowikied without triggering the warning.
+
+<!-- --> neither triggers the warning nor gets nowikied. I am about to start a discussion about whether that is desired or not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56213",1378458780,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5usozn6lenkcoenzeuyk,task_description,declined
+"VisualEditor: Wikitext warning not triggered by <references />, <i>, etc.","This is intentional; adding a complete set of wikitext detection would be very burdensome (i.e. slow VE down for users) without adding a lot of value.
+
+People who know complex things like HTML or advanced wikitext like <references /> will quickly learn that it doesn't work; this functionality is an aide-memoire for  newbies and rare users.
+
+Marking as WONTFIX, but happy to discuss.",1383758460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5usozn6lenkcoenzeuyk,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),"The German template for quotes:
+
+https://de.wikipedia.org/wiki/Vorlage:Zitat
+
+eats refs, or rather their display at the end of the article, if the refs are inserted in it & the article is loaded in VE. Example articles:
+
+https://de.wikipedia.org/wiki/Arvo_P%C3%A4rt -> ref 5 & 8
+
+https://de.wikipedia.org/wiki/The_Rolling_Stones -> 26, 123-125
+
+https://de.wikipedia.org/wiki/Chick_Corea -> ref 12
+
+Report:
+
+https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=122231626#Einzelnachweise_am_Artikelende_werden_im_VE_nicht_angezeigt
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50474",1378330980,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_description,resolved
+De.WP's quote template eats refs (or gets eaten),"Merging this with bug 50474 which I have managed to determine that this is the same as that.
+
+*** This bug has been marked as a duplicate of bug 50474 ***",1383003781,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),"Updates:
+
+Rolling Stones: The section Discografie
+
+https://de.wikipedia.org/wiki/The_Rolling_Stones#Diskografie
+
+includes another article inserted as template:
+
+https://de.wikipedia.org/wiki/The_Rolling_Stones/Disko-_und_Videografie
+
+However, the article isn't displayed in full but only relevant parts, picked by  onlyinclude-tags.
+
+Shine a Light: The issue not included in a template is caused by something VE apparently can't handle in spelling out the ref name but Wikicode can: ""_"" vs "" "":
+
+https://de.wikipedia.org/w/index.php?title=Shine_a_Light&diff=prev&oldid=122747897
+
+The other two are eaten by the template, i.e. the same source is also referred to in refs outside the template and VE simply doesn't count the template-inserted refs.",1380840894,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),This looks like a side effect of the underlying problem in bug 50474.,1380552169,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),"Chances are this issue is systemic; three more examples:
+
+1) Info box for movie articles:
+
+https://de.wikipedia.org/wiki/Vorlage:Infobox_Film
+
+includes three refs in 
+
+https://de.wikipedia.org/wiki/Shine_a_Light
+
+and they all get eaten if the entry is loaded in VE.
+
+2) Info box for corporate entities:
+
+https://de.wikipedia.org/wiki/Vorlage:Infobox_Unternehmen
+
+see the first four refs in 
+
+https://de.wikipedia.org/wiki/Sony
+
+3) https://de.wikipedia.org/wiki/Vorlage:Infobox_Chemikalie
+
+eats the two included refs in:
+
+https://de.wikipedia.org/wiki/Magnesiumcarbonat",1378501325,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),"from the report:
+
+* a) {{<ref>source a</ref>}} -> eats ref completely
+
+in all other reported cases:
+
+* b) {<ref>source b</ref>} 
+* c) {{<ref>source c</ref>
+* d) {<ref>source d</ref> 
+* e) {{<ref>source a</ref>}.
+
+VE tells the user once ""This is Wikitext"" but then carries on; see test page:
+
+https://de.wikipedia.org/w/index.php?title=Benutzerin:Miss-Sophie/Spielwiese&oldid=122231700",1378331713,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+VisualEditor: Corruption: Leading whitespace removed from pre block,"See https://en.wikipedia.org/w/index.php?title=Epigram_%28programming_language%29&oldid=567048374&veaction=edit and click ""save"" (note that save box warns about corruption) and then ""view changes"" (ignoring the changes I have since made). The pre block has been corrupted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1378330500,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-wf4d3yulifq7pdamnvpv,task_description,resolved
+VisualEditor: Corruption: Leading whitespace removed from pre block,"
+
+*** This bug has been marked as a duplicate of bug 54083 ***",1379613849,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wf4d3yulifq7pdamnvpv,task_subcomment,NA
+Request for edit summary preview,"A De.WP user suggested to include a preview for the edit summary. Report:
+
+https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=122207411#Vorschau_f.C3.BCr_Zusammenfassung_und_Quellen
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378253700,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-uro44a5vqso2sy7u2arn,task_description,resolved
+Request for edit summary preview,"
+
+*** This bug has been marked as a duplicate of bug 42139 ***",1380545659,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uro44a5vqso2sy7u2arn,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"See https://it.wikipedia.org/w/index.php?title=Bisanzio_Lupis&diff=61160806&oldid=51778070 .
+
+When creating a section for references and adding the relevant tag,
+it will suppress the Related Articles section - just the heading, not the content.
+
+I reproduced it easily in my sandbox by just adding the contents that you can see in the diff above.
+Note that it is not related to the reference being added in the same edit; here for instance https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=61285258&oldid=61285224 it was added previously.
+
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378206960,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_description,resolved
+VisualEditor: adding section for references will suppress the Related Articles one,Making resolved instead because it probably //was// a problem in 2013 :),1438627770,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,Making resolved instead because it probably //was// a problem in 2013.,1438627757,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"Yup, can't reproduce this one.",1425653133,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"Closing task as declined as per last two comments as nobody managed to reproduce.
+
+Please reopen if this problem still happens and provide an URL/link to an example. Thanks!",1425487289,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"> When creating a section for references and adding the relevant tag,
+
+What I tried:
+Write the text ""Notes"" right above ""Voci correlate"", mark that text, choose ""Heading"" from the formatting dropdown, then add a reference via ""Cite > Basic"" somewhere in the text, then click below the ""Notes"" heading and choose ""Insert > References list"" in VE.
+
+No issues either. Let's close this soon if noone can reproduce (already set to Stalled status).",1424366202,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"I've attempted to reproduce the two test cases in a sandbox on the Italian Wikipedia. In both cases ([[https://it.wikipedia.org/w/index.php?title=Utente:Neil_P._Quinn/test&diff=prev&oldid=70691767|full]] and [[https://it.wikipedia.org/w/index.php?title=Utente:Neil_P._Quinn/test&diff=next&oldid=70691826|reduced]]), adding the section heading and references list worked correctly.",1423081747,PHID-USER-cbjanejnwkkrbnj77d2d,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: Wikitext warning triggered without adding wikitext,"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.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378050300,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dusvcxcsy7gqikdevzgn,task_description,resolved
+VisualEditor: Wikitext warning triggered without adding wikitext,"
+
+*** This bug has been marked as a duplicate of bug 51751 ***",1378458424,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dusvcxcsy7gqikdevzgn,task_subcomment,NA
+"VisualEditor: Show and make editable <nowiki>, </nowiki> and <nowiki /> tags","There is discussion at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=571087443#nowiki_tags about using the edit filter to block edits adding the <nowiki /> tag in mainspace. However it was pointed out that ""the user probably has no way to know what they need to fix in order to resubmit their edit.  They can't find the nowiki tag, as it is invisible.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49806
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49603",1378049580,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-brld2i7xjlh2vp4m2jxn,task_description,declined
+"VisualEditor: Show and make editable <nowiki>, </nowiki> and <nowiki /> tags","WONTFIXing this bug instead:
+
+<nowiki> is fundamentally an artefact of wikitext that users should be (blissfully) unaware of, and Parsoid should ""just make work"" as needed. Right now this is generally true, and it will get better, not worse, in the future, so this is not needed (which is good, because VisualEditor has no way of knowing whilst a user is editing whether Parsoid will decide to put a <nowiki> in).",1390023864,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-brld2i7xjlh2vp4m2jxn,task_subcomment,NA
+"VisualEditor: Show and make editable <nowiki>, </nowiki> and <nowiki /> tags","Gah, sorry, wrong bug.",1390023748,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-brld2i7xjlh2vp4m2jxn,task_subcomment,NA
+"VisualEditor: Show and make editable <nowiki>, </nowiki> and <nowiki /> tags","This is because <nowiki /s> (unlike <nowiki>s) are ""meta"" items in the DOM rather than things VE can edit; merging with bug 56381.
+
+*** This bug has been marked as a duplicate of bug 56381 ***",1390023708,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-brld2i7xjlh2vp4m2jxn,task_subcomment,NA
+text duplicated when following an image,"In some odd circumstances the text immediately following an image is duplicated. You can see the effect in
+http://en.wikipedia.org/w/index.php?title=Danny_Nalliah&oldid=570830443&veaction=edit
+where the text '''Daniel (Danny) Nalliah''' is duplicated. 
+
+To make things more confusing it does not occur for every revision 
+http://en.wikipedia.org/w/index.php?title=Danny_Nalliah&oldid=570591483&veaction=edit
+works fine.
+
+To make things thoughly weird in this revision in my sandbox
+http://en.wikipedia.org/w/index.php?title=User:Salix_alba/sandbox&oldid=570839025
+the text '''Daniel (Danny) Nalliah''' does not appear. Yet it magically appear in VE
+http://en.wikipedia.org/w/index.php?title=User:Salix_alba/sandbox&direction=prev&oldid=570839025&veaction=edit
+
+This issues is discussed at 
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Still_looks_like_VE_Feedback_to_me
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378023300,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-keti3xueyglzi4p4spht,task_description,declined
+text duplicated when following an image,"Cannot reproduce the problem either with the given links and Firefox 35...
+Assuming that this has magically fixed itself.
+Hence closing this ticket as DECLINED as no-one else could reproduce so far, unfortunately.
+
+@SalixAlba: If you can still reproduce this problem, please provide browser information. (Also, testing with the browser and having add-ons / extensions disabled or such might be welcome.)",1423705265,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-keti3xueyglzi4p4spht,task_subcomment,NA
+text duplicated when following an image,Cannot reproduce. Was this fixed at some point?,1421888484,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-keti3xueyglzi4p4spht,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"I cannot paste text into the edit summary with Ctrl+V or right click and paste when I use Chromium Version 28.0.1500.71 Ubuntu 13.04 (28.0.1500.71-0ubuntu1.13.04.1). Nothing happens. It works fine in FireFox though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377976740,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_description,resolved
+VisualEditor: Cannot paste into edit summary in Chromium,"Now that the edit summary is in its own window, this bug has gone away. I don't know whether the plan is to eventually return to the edit confirmation flyout - if so this bug may well reappear.",1393634250,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"en.wp user ToE further reports:
+Upon upgrading to Google Chrome: 29.0.1547.76 (Official Build 223446) m, JavaScript V8 3.19.18.23, paste into edit summary works properly.",1380030184,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"en.wp user ToE reports:
+[this bug] also applies to Google Chrome, version ""29.0.1547.66 (Official Build 220848) m"", JavaScript V8 3.19.18.19, running on Windows 7 Home Premium, Service Pack 1. Paste into edit summary works fine on the same machine in Firefox version 23.0.1.",1379878291,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"I'm observing the exact same problem in the same Chromium version on Ubuntu 13.04 (no error messages in the JavaScript console, works fine in Firefox).",1379211478,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"**eliashedberg** wrote:
+
+I had the same (or a similar) problem in Chrome 29.0.1547.62 under Mac OS X 10.6.8: when pasting the string ""Lavoslav Ružička"" into the edit summary the page behind the summary jumped down and back up (or the other way around) but there was no text inserted into the edit summary.
+
+I can recreate the failed paste action in the edit summary of my sandbox, but the text behind the edit summary doesn’t move (potentially because that article is too short).
+
+I can recreate the failed paste action with other strings too (in Chrome), i.e. no pasting works, no matter what string I try to paste.
+
+In Firefox, pasting into the edit summary works fine (Firefox 23.0.1, also under OS X 10.6.8).",1378189372,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"Hm, how do I find the browser's error console? If it's F12 and Console, then no, no messages there. 
+
+I noticed that if the page I was editing is not scrolled to the top, when I try to paste, it behaves as if I press arrow up.",1378154905,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,Is there any kind of output in the browser's error console when you try?,1378119003,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+Delete tests from browsertests repository that are moved to other repositories,"We have moved ULS and VisualEditor tests to their repositories. Delete the code from browsertests repository.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377862680,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_description,resolved
+Delete tests from browsertests repository that are moved to other repositories,"Reopening until we decide if search.feature file should:
+
+- stay in browsertests repo
+- be moved to CirrusSearch repo
+- be deleted",1381823392,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_subcomment,NA
+Delete tests from browsertests repository that are moved to other repositories,"Change 88992 merged by Cmcmahon:
+Flow tests are moved to Flow repository
+
+https://gerrit.wikimedia.org/r/88992",1381420151,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_subcomment,NA
+Delete tests from browsertests repository that are moved to other repositories,"Chris, did we move all tests from browsertests repository to relevant repositories? Should this bug be resolved?
+
+The only remaining feature file that I see in browsertests repository that should be either deleted or moved to CirrusSearch repository is search.feature. Or, should we leave it in browsertests repository?",1381416666,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_subcomment,NA
+Delete tests from browsertests repository that are moved to other repositories,"Change 88992 had a related patch set uploaded by Zfilipin:
+Flow tests are moved to Flow repository
+
+https://gerrit.wikimedia.org/r/88992",1381416355,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_subcomment,NA
+Figure out how to reuse common test code between repositories,"At the moment we have similar setup code for browser tests in 6 repositories:
+
+https://github.com/wikimedia/qa-browsertests
+https://github.com/wikimedia/mediawiki-extensions-CirrusSearch
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend
+https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor
+https://github.com/wikimedia/mediawiki-extensions-Wikibase
+
+Figure out a way how to reduce code duplication. We should probably create a Ruby gem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377862440,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ma7ogjs2kvk66wshe44k,task_description,resolved
+Figure out how to reuse common test code between repositories,"
+
+*** This bug has been marked as a duplicate of bug 53579 ***",1381410774,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ma7ogjs2kvk66wshe44k,task_subcomment,NA
+Update readme file so it contains links to all repositories with Selenium tests,"README.md[1] file has information about Selenium tests in
+
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend
+
+Add links to:
+
+https://github.com/wikimedia/mediawiki-extensions-CirrusSearch
+https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor
+https://github.com/wikimedia/mediawiki-extensions-Wikibase
+
+1: https://github.com/wikimedia/qa-browsertests/blob/master/README.md
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377862320,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-dhqbmbptdf76io4mrpls,task_description,resolved
+Update readme file so it contains links to all repositories with Selenium tests,"Change 90562 merged by jenkins-bot:
+Relevant links
+
+https://gerrit.wikimedia.org/r/90562",1382362818,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dhqbmbptdf76io4mrpls,task_subcomment,NA
+Update readme file so it contains links to all repositories with Selenium tests,"Change 90562 had a related patch set uploaded by Zfilipin:
+Relevant links
+
+https://gerrit.wikimedia.org/r/90562",1382112246,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dhqbmbptdf76io4mrpls,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,".ruby-gemset and .ruby-version should be removed and RVM setup should be moved to Gemfile[1].
+
+Repositories that are doing it right:
+https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor
+
+Repositories that should be updated:
+
+https://github.com/wikimedia/mediawiki-extensions-CirrusSearch
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend
+https://github.com/wikimedia/mediawiki-extensions-Wikibase
+https://github.com/wikimedia/qa-browsertests
+
+1: https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector/blob/master/tests/browser/Gemfile#L1-L2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377861960,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-uvse6kpckod47zira6mk,task_description,resolved
+Make sure all repositories have the latest version of shared code,All repositories that have Selenium tests in Ruby now use mediawiki-selenium gem.,1382729080,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87552 merged by jenkins-bot:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87552",1382713394,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87581 merged by jenkins-bot:
+[browser test] Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87581",1382546758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87563 merged by jenkins-bot:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87563",1382546616,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87125 merged by Cmcmahon:
+Moving code used in multiple repositores to a Ruby gem
+
+https://gerrit.wikimedia.org/r/87125",1382363305,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 90560 had a related patch set uploaded by Zfilipin:
+WIP Moved confing files from qa/browsertests repository
+
+https://gerrit.wikimedia.org/r/90560",1382111650,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 90559 had a related patch set uploaded by Zfilipin:
+WIP Moved config files to mediawiki/selenium repository
+
+https://gerrit.wikimedia.org/r/90559",1382111624,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 88010 merged by Tobias Gritschacher:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/88010",1381745570,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,*** Bug 53581 has been marked as a duplicate of this bug. ***,1381410774,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,*** Bug 54600 has been marked as a duplicate of this bug. ***,1381410415,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 88010 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/88010",1381134855,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87158 merged by jenkins-bot:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87158",1380988261,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87542 merged by jenkins-bot:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87542",1380987438,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87581 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87581",1380901487,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87563 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87563",1380896472,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87552 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87552",1380892900,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87542 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87542",1380888245,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,For more information see http://lists.wikimedia.org/pipermail/qa/2013-October/000509.html,1380805607,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87158 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87158",1380730588,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87125 had a related patch set uploaded by Zfilipin:
+Moving code used in multiple repositores to a Ruby gem
+
+https://gerrit.wikimedia.org/r/87125",1380723813,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 86838 merged by jenkins-bot:
+Updated ULS repository to the latest version of shared test files
+
+https://gerrit.wikimedia.org/r/86838",1380645048,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 86845 merged by Cmcmahon:
+Updated the repository to the latest version of shared test files
+
+https://gerrit.wikimedia.org/r/86845",1380644856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 86845 had a related patch set uploaded by Zfilipin:
+Updated the repository to the latest version of shared test files
+
+https://gerrit.wikimedia.org/r/86845",1380630502,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 86838 had a related patch set uploaded by Zfilipin:
+Updated ULS repository to the latest version of shared test files
+
+https://gerrit.wikimedia.org/r/86838",1380628011,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82039 merged by Tobias Gritschacher:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82039",1378124036,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82035 merged by jenkins-bot:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82035",1377987180,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82034 merged by jenkins-bot:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82034",1377987114,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82033 merged by Cmcmahon:
+Removed unused Rake Ruby gem
+
+https://gerrit.wikimedia.org/r/82033",1377987032,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82032 merged by Cmcmahon:
+Removed unused HTML Cucumber formatter
+
+https://gerrit.wikimedia.org/r/82032",1377986999,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82039 had a related patch set uploaded by Zfilipin:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82039",1377896220,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82035 had a related patch set uploaded by Zfilipin:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82035",1377894902,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82034 had a related patch set uploaded by Zfilipin:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82034",1377894425,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82033 had a related patch set uploaded by Zfilipin:
+Removed unused Rake Ruby gem
+
+https://gerrit.wikimedia.org/r/82033",1377893822,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82032 had a related patch set uploaded by Zfilipin:
+Removed unused HTML Cucumber formatter
+
+https://gerrit.wikimedia.org/r/82032",1377893504,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 81929 merged by Cmcmahon:
+Updating shared code to the latest version
+
+https://gerrit.wikimedia.org/r/81929",1377883705,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 81929 had a related patch set uploaded by Zfilipin:
+Updating shared code to the latest version
+
+https://gerrit.wikimedia.org/r/81929",1377871196,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"All repositories:
+
+https://github.com/wikimedia/qa-browsertests
+https://github.com/wikimedia/mediawiki-extensions-CirrusSearch
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend
+https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor
+https://github.com/wikimedia/mediawiki-extensions-Wikibase
+
+Files to update:
+
+config/config.yml
+config/cucumber.yml
+features/support/env.rb
+features/support/sauce.rb
+Gemfile
+Gemfile.lock
+README.md",1377870317,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Send e-mail notification to relevant people after jenkins job is completed,"Who gets e-mail notification is documented in jobs.md[1]. At the moment Chris and I get notification for all jobs. Michelle is added for MobileFrontend, Rachel and James for VisualEditor.
+
+Nik Everett should be notified for CirrusSearch, Amir and Niklas for UniversalLanguageSelector.
+
+1: https://github.com/wikimedia/qa-browsertests/blob/master/docs/jobs.md
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377861600,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-skm7yk65ve7ofcodlrqs,task_description,resolved
+Send e-mail notification to relevant people after jenkins job is completed,"Change 88998 merged by Cmcmahon:
+Updated Jobs and documentation who gets e-mail notification when a Jenkins job fails
+
+https://gerrit.wikimedia.org/r/88998",1381846904,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-skm7yk65ve7ofcodlrqs,task_subcomment,NA
+Send e-mail notification to relevant people after jenkins job is completed,"Change 88998 had a related patch set uploaded by Zfilipin:
+Updated Jobs and documentation who gets e-mail notification when a Jenkins job fails
+
+https://gerrit.wikimedia.org/r/88998",1381417453,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-skm7yk65ve7ofcodlrqs,task_subcomment,NA
+VisualEditor: Images after template are shielded and uneditable in RTL,"I could not replicate this in LTR wikis (en.wiki or MediaWiki.org) but I suspect this is not so much ltr/rtl but floating behavior of the templates and images.
+
+See example here:
+https://he.wikipedia.org/wiki/%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%D7%AA:Mooeypoo/%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99/%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_%D7%95%D7%9E%D7%A9%D7%97%D7%A7%D7%99%D7%9D?veaction=edit
+
+The top two images are regular images (not templates) - they are perfectly editable if you remove the template at the top. They got their shielded status after I inserted that template.
+
+Steps to reproduce:
+1. Edit a page
+2. Insert some image (or more) to top
+3. Save page
+4. Edit again, insert template ""{{עליות}}"" just above the images. 
+5. Save.
+6. Edit again. Observe: The images jumped to the left (wrong float side) and are now uneditable. 
+7. Interesting fact: Remove the template and save, then go back into the editor and the images are still uneditable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377795900,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-jjwaxnsw7nonpkj5w5ug,task_description,resolved
+VisualEditor: Images after template are shielded and uneditable in RTL,This seems to be fixed now with the change of images and the way we render shields.,1406316798,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-jjwaxnsw7nonpkj5w5ug,task_subcomment,NA
+VisualEditor: Images after template are shielded and uneditable in RTL,Correction: images jump to the *right* (wrong floating side in RTL wikis) not left. Apparently my sense of directions needs its own bug report.,1377796057,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-jjwaxnsw7nonpkj5w5ug,task_subcomment,NA
+VisualEditor: broken reference tag swaps sections when VEditing,"If you open https://fr.wikipedia.org/w/index.php?title=Anna_Mouglalis&oldid=95468238&veaction=edit you'll notice a weird order of paragraphs. This is due to an extra space in the ref tag for the second reference. VE might probably autocorrect similar situations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377784560,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-m5whhh35h7fkdpaca77l,task_description,resolved
+VisualEditor: broken reference tag swaps sections when VEditing,"
+
+*** This bug has been marked as a duplicate of bug 52430 ***",1377786212,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-m5whhh35h7fkdpaca77l,task_subcomment,NA
+VisualEditor: Parameters in RTL can be duplicated in the transclusion dialog,"To reproduce:
+
+1. Go to this page: https://he.wikipedia.org/wiki/%D7%90%D7%9C%D7%9B%D7%A1%D7%A0%D7%93%D7%A8_%D7%94%D7%92%D7%93%D7%95%D7%9C
+2. Edit the infobox at the left side. 
+3. Behold! Some parameters appear both at the left panel (used) and also on the right panel (unused). Specific example, look for the parameters ""בן זוג"" and ""בת זוג"" 
+4. If you click the parameter ""בת זוג"" for example, on the left side (the used one) you will see data. If you click the one on the right side, it appears with empty textbox as if it's new.
+5. Click on the right side (as if to add param again) on ""בת זוג"" 
+6. Click again and again -- the parameter will keep being added to the list on the left in duplicates.
+
+And if the page is saved, the parameter is now completely removed.
+
+
+This has happened specifically in the hewiki but might be related to more than just RTL.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377741840,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-cbkpykct3waf2q7jincj,task_description,declined
+VisualEditor: Parameters in RTL can be duplicated in the transclusion dialog,"This works for me on hewiki and local on rtl settings. If anyone discovers this anew, please reopen.",1380749912,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-cbkpykct3waf2q7jincj,task_subcomment,NA
+VisualEditor: Parameters in RTL can be duplicated in the transclusion dialog,This seems to be fixed now.,1379704380,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-cbkpykct3waf2q7jincj,task_subcomment,NA
+VisualEditor: Link insertion dialog should preserve the case of the initial character,"Currently whenever a user enters a link when no text is selected the first character of the displayed link is always capitalised. This is often incorrect, e.g. in the middle of a sentence or for articles like [[iPhone]] or [[grep]].
+
+Especially until bug 50678 is fixed, correcting this is not at easy or intuitive.
+
+So, at least until bug 48789 and bug 50945 are fixed and the display text is settable in the dialog, and probably beyond that, it would be best if the displayed link used the same case as the search term entered. i.e.
+
+User entry ->  wikitext equivalent of desired output
+Green   ->  [[Green]]
+green   ->  [[green]]
+iPad    ->  [[iPad]]
+HAMmer  ->  [[Hammer]]
+london  ->  [[london]]
+
+Yes, this will result in some wrong captialisations, but no more than at present and will only be temporary (as noted above)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50678
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50745",1377720300,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hvan6ykhuzyhtye5e56x,task_description,resolved
+VisualEditor: Link insertion dialog should preserve the case of the initial character,"
+
+*** This bug has been marked as a duplicate of bug 50452 ***",1377802569,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hvan6ykhuzyhtye5e56x,task_subcomment,NA
+Right-click on newly linked page in VisualEditor opens invalid URL in new tab,"This is somewhat related to bug 50321.
+
+Steps to reproduce:
+
+1. Open your own sandbox/userpage (not a page in the mainspace) in VisualEditor.
+2. Add a link to a word (""xxx"").
+3. Control-click/right-click/command-click the new link to open the link in a new tab or new window.
+4. Discover that VisualEditor has sent you to an invalid URL:  http://en.wikipedia.org/w/Xxx or http://en.wikipedia.org/wiki/User:Whatamidoing_(WMF)/Xxx
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377715320,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lz4m6zadc7gusnegkxep,task_description,resolved
+Right-click on newly linked page in VisualEditor opens invalid URL in new tab,"This is bug 48915 although the bug title ""VisualEditor: Respect Parsoid's <base>"" describes the solution not the effect so I'm not surprised you didn't find it.
+
+*** This bug has been marked as a duplicate of bug 48915 ***",1377718799,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-lz4m6zadc7gusnegkxep,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,"Requested by James Forrester at QA mailing list:
+
+http://lists.wikimedia.org/pipermail/qa/2013-August/000339.html
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377688440,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_description,resolved
+Move VisualEditor Selenium test to VisualEditor repository,"Change 81486 merged by jenkins-bot:
+Moved VisualEditor Selenium tests from browsertests repository
+
+https://gerrit.wikimedia.org/r/81486",1377721181,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,"Change 81490 merged by Cmcmahon:
+Added support for running VisualEditor tests to Jenkins job template
+
+https://gerrit.wikimedia.org/r/81490",1377720850,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,"Change 81490 had a related patch set uploaded by Zfilipin:
+Added support for running VisualEditor to Jenkins job template
+
+https://gerrit.wikimedia.org/r/81490",1377696235,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,Resolved in https://gerrit.wikimedia.org/r/#/c/81486/,1377695195,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,"Change 81486 had a related patch set uploaded by Zfilipin:
+Moved VisualEditor Selenium tests from browsertests repository
+
+https://gerrit.wikimedia.org/r/81486",1377694989,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Show edit summary after clicking save,"**Author:** `molly.white5`
+
+**Description:**
+Only show the edit summary input box after the user clicks ""save"" (sort of like in the VisualEditor).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377659100,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-q6pz6kygm2rnc3zs7geb,task_description,declined
+Show edit summary after clicking save,"**molly.white5** wrote:
+
+See above comment.",1382039786,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-q6pz6kygm2rnc3zs7geb,task_subcomment,NA
+Show edit summary after clicking save,"**mr.heat** wrote:
+
+(In reply to comment #0)
+> Only show the edit summary input box after the user clicks ""save""
+
+But clicking ""save"" leaves the editor and reloads the page. If the edit summary is hidden and only shown after you clicked ""save"" you will see it only for a fraction of a second and not be able to enter anything.
+
+I guess you are suggesting to block the first click on the ""save"" button. First click shows the edit summary. Second click saves. I don't think this is useful for two main reasons:
+
+1. I want to be able to type something in the summary field while I'm still editing. Hiding the field removes this feature. I can't use it when I want. It forces me to remember everything I did and recap it in the end. This will lead to more empty and less descriptive summary lines.
+
+2. If I click a button labeled ""save"" I expect it to save and not to do something completely different. If you want to have this as an opt-in feature you can use the existing ""Prompt me when entering a blank edit summary"" setting or check my script [[de:User talk:TMg/forceEditSummary.js]]. Both do not hide the edit summary but block the ""save"" button one time if you forgot to enter a summary. The setting is server-side, my script is client-side and therefor a lot faster.
+
+I suggest to close this as ""works as expected"".",1382020847,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-q6pz6kygm2rnc3zs7geb,task_subcomment,NA
+VisualEditor: Media should be easily replaceable,"At the moment there doesn't appear to be a way to replace media - that is, to click on a media element, and select a different piece of media for that element. That's not a big deal at the moment, but we're going to move to a world where media settings are more complex - where alignment can be specified, referencing can be specified and permitted, so on and so forth.
+
+The result of this is that media elements will have a lot of data associated with them - media it's pretty hard to type out again if you find that the image (or video, or...whatever) needs to be replaced. It would be good to have a way of replacing images without losing the associated caption, size and alignment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377621000,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dhmvhapysnb7mmzkzrmc,task_description,resolved
+VisualEditor: Media should be easily replaceable,"I *knew* it's gotta be a dupe. ;)
+
+*** This bug has been marked as a duplicate of bug 51033 ***",1377621974,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dhmvhapysnb7mmzkzrmc,task_subcomment,NA
+Search and replace feature needed,"We need a search-and-replace feature in VisualEditor. This seacrh box should also support ULS
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377447840,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-5k5rt6qbkoyx3ta4vs6h,task_description,resolved
+Search and replace feature needed,"Hi Pavanaja. 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 48368 ***",1377460908,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5k5rt6qbkoyx3ta4vs6h,task_subcomment,NA
+Inserting and editing tables,"There should be a facility in VisualEditor for creating new table or edit an existing table
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377447540,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-lfg46f7cy7mmetnq3hpg,task_description,resolved
+Inserting and editing tables,"Indeed there should be such a feature, and one has been requested at bug 52181 so I'm marking this as a duplicate.
+
+*** This bug has been marked as a duplicate of bug 52181 ***",1377528014,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-lfg46f7cy7mmetnq3hpg,task_subcomment,NA
+Inserting and editing tables,"[New feature => setting the ""Severity"" field to ""enhancement"". 
+Feel free to do so yourself when filing a report.]",1377460978,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lfg46f7cy7mmetnq3hpg,task_subcomment,NA
+VisualEditor: inconsistency when reviewing changes after a null edit,"User report:
+<<So I put a space and then a backspace.  Go to save, review changes to check and make sure it is a null edit, then it goes to this ""processing"" dialogue but then it shows ""Could not start the review because your revision matches the latest version of this page.""  So then I press the little back link on the dialogue, but it just goes back to the processing dialogue.  If the page is small, the processing is really quick, so before I can even press back again, it goes back to the ""Could not start"" warning message.  Even if I do manage to press the back a second time quickly, it will only stay at the save dialogue for a split second and then again bring me to the warning message, although ''then'' pressing back does take me to the save dialogue securely.  FF 23.0.1 Win7.>>
+
+I managed to reproduce this on Chrome as well, so which is the intended left button behaviour?
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377426720,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-inp4lb4bxjfhduddc4ri,task_description,resolved
+VisualEditor: inconsistency when reviewing changes after a null edit,"
+
+*** This bug has been marked as a duplicate of bug 53313 ***",1377426954,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-inp4lb4bxjfhduddc4ri,task_subcomment,NA
+VE does not finish initialization on KOWP,"**Author:** `ryuch`
+
+**Description:**
+VE not can be enabled by options in preferences for beta testing.
+When I click 'edit' on an article, the progress bar appear but does not finish initialization.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377353520,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z2y2nxnb7rd7vpntvfza,task_description,resolved
+VE does not finish initialization on KOWP,"This bug appears to be fixed as I can see VE edits happening in the recentchanges feed.
+
+https://ko.wikipedia.org/wiki/special:recentchanges?days=30&tagfilter=visualeditor",1380703487,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-z2y2nxnb7rd7vpntvfza,task_subcomment,NA
+VE does not finish initialization on KOWP,"**ryuch** wrote:
+
+Sorry, a critical typo I sent. 
+VE ""now"" can be enabled by options in preferences for beta testing.",1377353651,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z2y2nxnb7rd7vpntvfza,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"cucumber features/visual_editor_anon.feature:5 # Scenario: Basic edit fails 
+because VisualEditor these days shows an introductory disclaimer:
+
+  This is our new, easier way to edit. It's still in beta,
+  which means you might find parts of the page you can't edit...
+and so it fails with
+  expected ""You are not currently logged in. 
+which isn't visible until you dismiss the popup.
+
+I think the same explains a
+  timed out after 5 seconds, Element was not visible in 5 seconds
+that I'm getting in the similar
+cucumber features/visual_editor_logged_in.feature:5 # Scenario: Basic edit
+after applying gerrit 80709.
+
+The popup is in a div containing an iframe containing more divs until class=""ve-ui-mwBetaWelcomeDialog-content"", and then tests have to click outside it to dismiss it; and some day it will go away.
+
+Instead it seems better to set the ve-beta-welcome-dialog cookie to 1 upon visiting the site, which will turn off this disclaimer dialog.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1377334920,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_description,resolved
+VisualEditor tests fail due to introductory beta disclaimer popup,fixed,1382983457,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"Chris, this is fixed, right? Is there anything left here to do? Should we close the bug?",1381411550,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"Honestly, I would rather that VE behave the same on beta, test2wiki, and production. Preferably at more or less the same time.",1377806202,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"(In reply to comment #5)
+> Should this be closed since 80709 is merged into master?
+No, that's a different problem breaking VE tests.
+
+Please can you change the VE tests to have an
+    If there is an introductory welcome message
+      then dismiss it
+stanza?",1377805386,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,Should this be closed since 80709 is merged into master?,1377780987,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"(In reply to comment #3)
+> Why is VE using an iframe for this?  (and using iframes in general?)
+For the welcome message, we don't technically need to use an iframe. In that case we just use an iframe because all of our other dialogs use iframes.
+
+In general, we use iframes for dialogs and inspectors because we need to be able to have two selections at the same time. For instance, when you inspect a link, the link is selected, but you also have a cursor in the text field in the inspector. Because you can only have one selection in any given HTML document, we need the edit surface and the text field to be in different documents, and so we put the text field (along with most of the rest of the inspector) in an iframe.
+
+Dialogs use iframes for similar reasons: when the user interacts with UI elements in the dialog, that needs to not affect their selection in the edit surface. The welcome dialog doesn't have any elements that can steal the focus or selection so it's not an issue there, but since it uses the generic dialog code it's automatically in an iframe.",1377568185,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"When it shows up on test2 and/or beta I'll dismiss it in the test. 
+
+Why is VE using an iframe for this?  (and using iframes in general?)",1377554145,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,Also note that the beta welcome message will be rolled out to all wikis soon.,1377553601,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"
+I've been running these tests against test2wiki, which doesn't have that problem.  https://gerrit.wikimedia.org/r/#/c/80709/ should make it possible to run these against beta labs now that VE seems to be deployed there reliably",1377553370,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+"VisualEditor: add a wikilink to tags, the final inequality sign (>) is lost","User report following:
+<<If I start with a blank page, type in ""<br>"", select the entire text, press the link icon, select say ""France"" as the link, upon exiting the link dialog I am left with a link to [[France]] but the anchor is shortened to ""<b"".</nowiki>  I don't get any ""Wikitext markup detected"" warning. >>
+This is true for other tags as well (I tried with <b>).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377286560,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6fqslp7awofcsqlxxg2u,task_description,declined
+"VisualEditor: add a wikilink to tags, the final inequality sign (>) is lost",This was fixed ages ago; sorry for not mentioning it here. (Please re-open if you can reproduce.),1397676516,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6fqslp7awofcsqlxxg2u,task_subcomment,NA
+"VisualEditor: add a wikilink to tags, the final inequality sign (>) is lost","(Sorry, that </nowiki> shouldn't be there, of course.)",1377286725,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6fqslp7awofcsqlxxg2u,task_subcomment,NA
+VisualEditor is inserting greater than signs (>),"While I was fixing a simple grammatical error, VE threw in a > sign at the start of a template further down the page thus breaking the template.
+
+https://en.wikipedia.org/w/index.php?title=Tesla_Model_S&diff=next&oldid=569876875
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377279060,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-rnr44j25me5v5afzc5we,task_description,declined
+VisualEditor is inserting greater than signs (>),"I /believe/ that this was a Parsoid selser bug, long-since fixed; marking as WORKSFORME for now.",1394480185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rnr44j25me5v5afzc5we,task_subcomment,NA
+VisualEditor: Unable to use save button using keyboard,"If I focus on the save button using [tab] from textarea, [enter] don’t save the page.
+
+Apparently the focus goes on the <div role=""button""> while the click event is listened on the span.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377270420,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_description,resolved
+VisualEditor: Unable to use save button using keyboard,"No, this bug as filed was indeed a duplicate of bug 51918. There's the subsequently-filed bug 62337 which tracks your comment.
+
+*** This bug has been marked as a duplicate of bug 51918 ***",1398102157,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_subcomment,NA
+VisualEditor: Unable to use save button using keyboard,"I'm reopening this rather than creating a new one, because it's not exactly a problem with the tab order.
+
+Here's how to reproduce this:  Open the Save dialog.  Type your edit summary.  Press the tab key seven times.  Everything tabs beautifully, in exactly the order I wish for.  Really:  Bug 51918 is resolved as far as I'm concerned.  The problem is not the tab ORDER.  
+
+The problem is that when I have successfully tabbed to the Save button, the Save button is BROKEN.  The Save button is selected.  There is a lovely blue box around it.  But it refuses to actually save the page when you press return.  It just sits there until, having pressed return twenty or thirty times, gone away in the hope that the server is just being slow, come back and hit the return key another dozen times or so, you finally conclude that it is not actually possible to save the page without taking your hands off the keyboard.  
+
+That's the problem:  ""Unable to use save button using keyboard"".  No amount of rearranging the deck chairs, I mean the tab order, is going to solve this problem.  The button itself is broken, not the tab order.
+
+The tick boxes for ""Minor edit"" and ""Watch this page"" can be tabbed to and toggled with the spacebar.  The links to the GFDL and other license stuff can be tabbed to and opened by pressing return.  But the ""Review your changes"" and ""Save"" buttons are broken.  There is no way to ""click"" those buttons without actually using a mouse/trackpad.",1398102028,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_subcomment,NA
+VisualEditor: Unable to use save button using keyboard,"Merging with bug 51918.
+
+*** This bug has been marked as a duplicate of bug 51918 ***",1378247189,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_subcomment,NA
+VisualEditor: Unable to use save button using keyboard,"**swalling** wrote:
+
+I also have this issue in Chrome 29 on OSX. Tabbing to Save page then hitting Enter does nada.",1378168841,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_subcomment,NA
+VisualEditor: Changing the first letter of wikilinked words is difficult,"Seems I had written about it in an unrelated bug, sorry. This happens on itwp: in order to do this
+http://it.wikipedia.org/w/index.php?title=DNasi_attivata_da_caspasi&diff=60101664&oldid=60089990
+I had to delete the word and link it back again. Our guidelines about style
+require pages in that section to appear with the capital letter, so we need to be able to fix that easily.
+
+It is also reported on en.wp, the user states <<When trying to correct a lower-case letter to a capital letter at the beginning of a link, I deleted the lower-case letter and found I couldn't type a capital letter and have it become part of the link, nor could I seem to extend the link over the capital. Eventually, I typed the capital after the lower-case letter and then deleted the lower-case letter. It might be good to have some way to extend a link over adjoining letters/words/text. Mount Flatten (talk) 05:31, 22 August 2013 (UTC) >>
+Thanks.
+
+ps. Might be related to https://bugzilla.wikimedia.org/show_bug.cgi?id=50745 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50745",1377174060,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kecuajpgt5rzhwm6db3u,task_description,resolved
+VisualEditor: Changing the first letter of wikilinked words is difficult,"
+
+*** This bug has been marked as a duplicate of bug 50678 ***",1377445650,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kecuajpgt5rzhwm6db3u,task_subcomment,NA
+VisualEditor: Changing the first letter of wikilinked words is difficult,*** Bug 53193 has been marked as a duplicate of this bug. ***,1377279290,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kecuajpgt5rzhwm6db3u,task_subcomment,NA
+VisualEditor: Changing the first letter of wikilinked words is difficult,pps. Also to https://bugzilla.wikimedia.org/show_bug.cgi?id=53193 .,1377186898,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kecuajpgt5rzhwm6db3u,task_subcomment,NA
+VisualEditor: can't fix a broken template since this will result invisible,"See http://en.wikipedia.org/w/index.php?title=User:Christian75/sandbox2&oldid=569697466 .
+If you edit the page with VE you won't see the broken template at all.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377164100,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lpapd5tkeo4vhxavi7m5,task_description,declined
+VisualEditor: can't fix a broken template since this will result invisible,"Essentially the problem here is ""broken wikitext produces confusion""; there's not really anything that we can do except encourage people to use VisualEditor rather than wikitext where such errors are possible.",1397676723,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lpapd5tkeo4vhxavi7m5,task_subcomment,NA
+"VisualEditor: Need way to insert templates that set both key and value for a parameter into a template invocation, like {{subst:DATE}}","Currently there is no way to use {{subst:DATE}} in a template invocation in VisualEditor. If you try to paste it into the value of a date field, it won't work because you get
+
+|date = date=August 2013
+
+which won't parse.
+
+VisualEditor should actually set the date automatically, always, for such templates (e.g. refimprove).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52345",1377157620,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-in5fzrgdn5o7nk5vzdej,task_description,declined
+"VisualEditor: Need way to insert templates that set both key and value for a parameter into a template invocation, like {{subst:DATE}}","Yes(In reply to comment #0)
+> Currently there is no way to use {{subst:DATE}} in a template invocation in
+> VisualEditor. If you try to paste it into the value of a date field, it won't
+> work because you get
+> 
+> |date = date=August 2013
+> 
+> which won't parse.
+
+Yes. This is by design; templates that are designed around wikitext's structure won't work in general for editing. Note that ""{{subst:CURRENTDAY}} {{subst:CURRENTMONTHNAME}}"" works fine; auto-inserting this would solve the problem.
+
+> VisualEditor should actually set the date automatically, always, for such
+> templates (e.g. refimprove).
+
+I agree; that is bug 51428 (and its corresponding implementation in VisualEditor).",1377904404,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-in5fzrgdn5o7nk5vzdej,task_subcomment,NA
+VisualEditor: Links from a subpage are not rendered correctly in the editing surface,"If I add an unprefixed link to [[Main Page]] on
+
+https://www.mediawiki.org/wiki/Wikimedia_Engineering/WMF_Tech_Days_2013
+
+using VisualEditor, the link points to [[Wikimedia Engineering/Main Page]] when previewed in VisualEditor (by right-clicking and opening in a new tab). ""Review changes"" suggests that the correct link will be added when saving the page, so this issue may be limited to the editing surface.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377130800,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-wnlasenua7iwnzhgajgz,task_description,resolved
+VisualEditor: Links from a subpage are not rendered correctly in the editing surface,"
+
+*** This bug has been marked as a duplicate of bug 48915 ***",1377727533,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wnlasenua7iwnzhgajgz,task_subcomment,NA
+VisualEditor: nowiki when trying to edit an external link in references,"On de.WP, a user tried to replace an outdated link within an existing ref via VE and ran into a nowiki. 
+
+diff:
+
+http://de.wikipedia.org/w/index.php?title=Kin-dsa-dsa%21&diff=121506430&oldid=117367043
+
+report:
+
+http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121759646#nowiki_bei_unbeschriftetem_Link
+
+I could reproduce that; the previous is showing it prior to saving, too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377124920,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-6fktzxq6di35ahdf6gf4,task_description,resolved
+VisualEditor: nowiki when trying to edit an external link in references,"(In reply to Amir E. Aharoni from comment #2)
+> I cannot reproduce this with the current version of the article, which has
+> similar content.
+
+I can confirm that I could previously reproduce and this is now fixed; not quite sure where or when.
+
+> When trying to edit the old version of the article I get a strange result: I
+> don't see the external links in the reference editor at all.
+
+Yeah; that's very odd. Have filed bug 71652.",1412470303,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6fktzxq6di35ahdf6gf4,task_subcomment,NA
+VisualEditor: nowiki when trying to edit an external link in references,"I cannot reproduce this with the current version of the article, which has similar content.
+
+When trying to edit the old version of the article I get a strange result: I don't see the external links in the reference editor at all.",1412445538,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6fktzxq6di35ahdf6gf4,task_subcomment,NA
+VisualEditor: nowiki when trying to edit an external link in references,"Confirmed
+
+Steps to reproduce:
+1. https://de.wikipedia.org/w/index.php?title=Kin-dsa-dsa!&oldid=117367043&veaction=edit
+2. open the ref dialog for the last ref in the first paragraph of section 'Video'
+3. open link dialog for the first external link
+4. replace http://kinocenter.rsuh.ru/Dan2.htm with http://wayback.archive.org/web/20080603185657/http://kinocenter.rsuh.ru/Dan2.htm
+
+Expected results:
+Only the URL changes
+
+Actual results:
+<nowiki>[1]</nowiki> is inserted
+
+Reproduced on a much smaller test case here:
+https://de.wikipedia.org/w/index.php?title=Benutzer:John_Vandenberg/test&diff=123052743&oldid=123052686",1380638685,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-6fktzxq6di35ahdf6gf4,task_subcomment,NA
+Cannot enter multiple authors in cite web template,"When I add a reference and add a template of type ""cite web"" in the reference, the template only allows me to enter a single author last name and a single author first name. To enter multiple authors I'm supposed to use the attributes ""last1, first1 through last9, first9 for up to nine authors"", but VisualEditor doesn't seem to offer the possibility of adding these attributes.
+
+There is an ""others"" field, but this is only supposed to be used for people who are neither authors nor editors, e.g. illustrators.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1377110520,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-oeqdjrsyoun6qoc3mib4,task_description,invalid
+Cannot enter multiple authors in cite web template,"This is a failing in the TemplateData that has been written for the template - it seems that the author of the template's hinting didn't bother to put in last1-9 or first1-9.
+
+However, despite the lack of hinting, you can enter these in VisualEditor (just manually type in 'first1' as a parameter, add it, set a value, repeat for 'last1', and so on for each additional author). It's very laborious, which is why this should be fixed in the template's TemplateData, but not an issue with VisualEditor.",1377114222,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oeqdjrsyoun6qoc3mib4,task_subcomment,NA
+VisualEditor: Removal of template when adding reference list,"Screencast
+
+When trying to add a new section and a reference list an existing template (defaultsort) gets removed, see screencast attachment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11699}",1377029340,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-dit32vs3thukzudalngg,task_description,resolved
+VisualEditor: Removal of template when adding reference list,Cannot reproduce. This must have been fixed at some point. I wonder if it was a Parsoid issue...,1416183797,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dit32vs3thukzudalngg,task_subcomment,NA
+VisualEditor: Removal of template when adding reference list,Does this still happen?,1414811151,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dit32vs3thukzudalngg,task_subcomment,NA
+"""edit lead section"" link incorrectly points to second section","**Author:** `sumanah`
+
+**Description:**
+On mediawiki.org, I have enabled the ""Add an [edit] link for the lead section of a page"" gadget and the ""Enable section editing via [edit] links"" Preference (in the Editing tab).
+
+If I go to a wiki page on mediawiki.org and click ""edit"" or ""edit source"" next to the title of an article (e.g., on https://www.mediawiki.org/wiki/Wikimedia_Labs ), then the VisualEditor link correctly thinks I want section 0, the lead section:
+
+https://www.mediawiki.org/w/index.php?title=Wikimedia_Labs&veaction=edit&section=0
+
+but the ""edit source"" link thinks I want section #1 and thus brings me to edit the ""Background"" section:
+
+https://www.mediawiki.org/w/index.php?title=Wikimedia_Labs&action=edit&section=1
+
+This may be a problem with the gadget rather than with VE, but it only started recently, so I think it might be a VE-related issue.  (I have looked at Bug 51030 - ""Edit link for lead section no longer works"" which sounds sort of separate.)  I shall also mention this bug in the talk page of the relevant gadget.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376623920,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bid73jyquzumwcuffblp,task_description,invalid
+"""edit lead section"" link incorrectly points to second section",Definitely a problem with the gadget.,1376668133,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-bid73jyquzumwcuffblp,task_subcomment,NA
+"VisualEditor: ""Error: Unknown error"" when creating page on test2wiki","**Author:** `sumanah`
+
+**Description:**
+close-up of error message and greyed button
+
+1. Try to use the VE to create a page at https://test2.wikipedia.org (while logged in, if that makes a difference).
+
+2. Click ""Save page"" button.
+
+The ""Save page"" button greys out and ""Error: Unknown error"" shows up to its left.  The user assumes that the page has not been saved.  But it has been created, e.g., https://test2.wikipedia.org/wiki/Kim_Stanley_Robinson .
+
+By the way, if the user reacts to the error by clicking Review changes and then getting back to Save, everything works fine.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11279}",1376614380,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aphzv5yajhoubslqbzir,task_description,resolved
+"VisualEditor: ""Error: Unknown error"" when creating page on test2wiki","I think this was due to a bug in the save dialog that we fixed last month; closing. If it re-occurs, please re-open this bug so we can fix this issue too.",1383015953,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aphzv5yajhoubslqbzir,task_subcomment,NA
+"VisualEditor: ""Error: Unknown error"" when creating page on test2wiki","**sumanah** wrote:
+
+Also, as you can see in https://test2.wikipedia.org/wiki/Special:Contributions/Sharihareswara_%28WMF%29 and (for instance) https://test2.wikipedia.org/w/index.php?title=Kim_Stanley_Robinson&oldid=57690 , those creation edits don't get the ""VisualEditor"" tag.",1376676868,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aphzv5yajhoubslqbzir,task_subcomment,NA
+"VisualEditor: Edit summary length counter ""hidden"" on it.wp","This does not affect Firefox, from what I saw - I used Chrome.
+I'd add a screenshot but it is really just as the summary says, 
+the number is there and it is working but you can not see it because the equivalent for ""Watch this page"", which is ""Aggiungi agli osservati speciali"", overlaps it (only the last word, of course).
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376489160,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-z73kr2qs67okpafmzjog,task_description,resolved
+"VisualEditor: Edit summary length counter ""hidden"" on it.wp",This was I think fixed some time ago. Sorry for the very slow triage.,1394501931,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z73kr2qs67okpafmzjog,task_subcomment,NA
+End of transcluded page not/incorrectly detected,"Screenshot 1
+
+https://de.wikipedia.org/wiki/Knebel transcludes https://de.wikipedia.org/wiki/Konrad_Knebel
+
+Only 2 lines are transcluded but the VisualEditor does not detect the end of the transclusion, see screenshot 1.
+
+The other 3 lines are handled as content of this ""template"", see screeshot 2.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Knebel
+
+**Attached**: {F11960}",1376417640,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-es2flh3nsdngj3dxtuxi,task_description,resolved
+End of transcluded page not/incorrectly detected,"
+
+*** This bug has been marked as a duplicate of bug 51119 ***",1376639350,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-es2flh3nsdngj3dxtuxi,task_subcomment,NA
+End of transcluded page not/incorrectly detected,"Created attachment 13094
+Screenshot 2
+
+**Attached**: {F11961}",1376417681,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-es2flh3nsdngj3dxtuxi,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"Input in VisualEditor and Output after saving (+ Parsoid Server output)
+
+MediaWiki:
+1.22alpha (ffa9b0a) 19:02, 11. Aug. 2013
+
+VisualEditor (Version 0.1.0)(0e76b1b)20:01, 11. Aug. 2013
+
+ParsoidServer:
+commit 808cc39c81df83daaec458c81edbd126fd1dd19a
+Author: Subramanya Sastry <ssastry@wikimedia.org>
+Date:   Mon Aug 12 16:15:24 2013 -0500
+
+
+Adding more than one empty line isn't possible in the VisualEditor extension. Is this a desired behaviour?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11917}",1376401560,PHID-USER-26asvhtv4jalaeeuigbm,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_description,declined
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"Multiple sequential blank paragraphs are collapsed to one by design (we provide an HTML editor, not a desktop publishing system).",1397676105,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"Still happening with the following VE-commit
+
+commit c98a964d5f8495f0d16af9229abbeb0449042d1e
+Merge: 3d01a5b e7aed52
+Author: jenkins-bot <jenkins-bot@gerrit.wikimedia.org>
+Date:   Wed Sep 18 01:11:46 2013 +0000
+Merge ""Fix check for preformatted when stripping whitespace""
+
+Browser: Chrome 29.0.1547.66 m W764bit",1379658982,PHID-USER-26asvhtv4jalaeeuigbm,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,Confirmed this is still happening on en.wp (wmf 15) and mediawiki.org (wmf 16),1378425096,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"I've tested it with the VisualEditor on the official mediawiki-page. Here it works: Im able to enter more than one line break. Can you guys reproduce my problem with my version?
+
+I updated my VE to the latest master-branch-commit: 
+
+commit 2c4e9d832374f095d3fa9d43b845ac7c7083aeb4
+Merge: c84c47a 7673a39
+Author: jenkins-bot <jenkins-bot@gerrit.wikimedia.org>
+Date:   Wed Aug 14 22:00:12 2013 +0000
+Merge ""Support previews and concurrent updates in ce.GeneratedContentNode""
+
+Browser-Information: Chrome on Windows 7 64bit 28.0.1500.95 
+
+>>> Still the same problem.",1376631319,PHID-USER-26asvhtv4jalaeeuigbm,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"Sounds like VE, as we'll produce empty lines fr p/br content just fine. Moving to VE.",1376612281,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,Is this a question about the VE interface (in which case you should either file this against the VE component OR show up on IRC and ask on #mediawiki-visualeditor) or the wikitext that is generated?,1376407363,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: support article layouts,"Pages started with a copy/paste of layouts (i.e. http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Football/Players ) are very, very common. VE does not seem to support this right now, making VE a very secondary choice to create articles. Probably related to https://bugzilla.wikimedia.org/show_bug.cgi?id=33105 , please feel free to mark this as a dupe if needed. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376387040,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-svug2yxishcvki3vxn4q,task_description,resolved
+VisualEditor: support article layouts,"I'm going to merge this with bug 52091, which would fix the issue (you could copy-and-paste from the read HTML without needing to do anything special).
+
+*** This bug has been marked as a duplicate of bug 52091 ***",1383280378,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-svug2yxishcvki3vxn4q,task_subcomment,NA
+VisualEditor: reusing existing reference generates duplicate references,"All the references adding in this edit: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=568232613&oldid=568231803 were added using the ""use existing reference"" option. 
+
+It seems that only when I added the same reference on the same line (trying to reproduce a different bug) did it reuse the existing ref rather than creating a duplicate one.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376326380,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xsaz6kvx37q5kaxfiw5l,task_description,invalid
+VisualEditor: reusing existing reference generates duplicate references,"I'm not sure I understand this bug report – surely it's obvious that if you re-use a reference, we need to modify the original reference to have a name (if it doesn't already have one) so we can re-use it? That's how MediaWiki's referencing system works. Please re-open if I've missed something.",1401473395,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xsaz6kvx37q5kaxfiw5l,task_subcomment,NA
+VisualEditor: reusing existing reference generates duplicate references,user Biosthmors at en.wp reports that this bug is frustrating his efforts to recruit a campus ambassador because they are getting so frustrated at trying to get VE to do what it claims it will do.,1378727138,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xsaz6kvx37q5kaxfiw5l,task_subcomment,NA
+"VisualEditor: ""existing references"" in the references dialog not identifying references","See https://pl.wikipedia.org/w/index.php?title=Wikipedysta:G%C5%BCdacz/brudnopis&oldid=37221362&veaction=edit for an example; only one citation appears as insertable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376287140,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-wwlsmm4fnvqjdssb7g4d,task_description,resolved
+"VisualEditor: ""existing references"" in the references dialog not identifying references","
+
+*** This bug has been marked as a duplicate of bug 50474 ***",1402332002,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wwlsmm4fnvqjdssb7g4d,task_subcomment,NA
+VisualEditor: Cannot backspace in Edit Summary window after reviewing changes,"**Author:** `hagurganus`
+
+**Description:**
+When typing an edit summary in the Edit Summary window, I was unable to backspace. It seemed to let me highlight and _replace_ text, but even then, I could not highlight and hit the backspace key to _remove_ the text, I had to highlight and hit spacebar to simply enter a space, etc.
+
+It could be that this is intentional, but I highly doubt this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1376249940,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vis7xnmoa7ngc2i4ds2i,task_description,resolved
+VisualEditor: Cannot backspace in Edit Summary window after reviewing changes,"I believe that this is the same as bug 50722, yes.
+
+*** This bug has been marked as a duplicate of bug 50722 ***",1377833584,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vis7xnmoa7ngc2i4ds2i,task_subcomment,NA
+VisualEditor: Cannot backspace in Edit Summary window after reviewing changes,I think this is likely to be bug 50722?,1377449242,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-vis7xnmoa7ngc2i4ds2i,task_subcomment,NA
+VisualEditor: Cannot backspace in Edit Summary window after reviewing changes,"I've been encountering this for a while and just worked out how to reproduce this:
+
+1. Edit a page in VE
+2. Enter an edit summary (doesn't matter what) but don't save
+3. Review your changes.
+4. Return to editing the page without saving (e.g. using the ^ button). It doesn't matter if you make any more changes or not.
+5. Click save page again
+
+Expected behaviour
+* The edit summary input box works like a normal text entry field
+
+Actual behaviour
+* The delete, backspace and cursor keys do not work.
+* Text can only be selected using the mouse
+* Selected text can be removed by overwriting, by ""delete"" or ""cut"" from the RMB menu, or by using the ctrl+x shortcut to cut.
+
+This bug was originally reported on Safari/MacOS X, I encountered it using Firefox 23/Linux",1376475552,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-vis7xnmoa7ngc2i4ds2i,task_subcomment,NA
+"VisualEditor: After ""wikimarkup"" popup, save button temporarily does not work","An editor reports that he lost his work when an extensive edit unexpectedly triggered the ""wikimarkup"" popup and - after he dismissed it - the ""save"" button became unresponsive. The button appeared as normal but did not react to being selected.
+
+He was using Windows 7 and Firefox.
+
+I reproduced this using Windows 7 and Chrome (didn't matter if I removed the wikimarkup or not), and on further investigation found that the ""save"" button will respond as expected after a delay.
+
+The issue, of course, is that if this editor aborted his edit because he thought the system would not save, others are likely to think that as well.
+
+Not sure if anything can be done to make the save button immediately responsive or to figure out why it wouldn't be or to make it apparent to editors that the option to ""save"" will return.
+
+The conversation can be found here:
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=567809017#Wikitext_error_message
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376050200,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-avc3fsxulmn56uqgbsy6,task_description,resolved
+"VisualEditor: After ""wikimarkup"" popup, save button temporarily does not work","Is this still occurring? I think we've fixed it, so am marking as FIXED, but would prefer to get confirmation.",1383015225,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-avc3fsxulmn56uqgbsy6,task_subcomment,NA
+"VisualEditor: After ""wikimarkup"" popup, save button temporarily does not work","en.wp user GermanJoe reports a probably related problem:
+
+After dismissing the wikitext warning the ""upper third and right corner"" of the save and cancel buttons are not clickable."" and that ""Those partial locks are only released, after you clear your browser cache (stopping VE is not enough) ""
+
+GermanJoe was using Windows XP, FF 22, vector.js and a 1280 x 1024 resolution for test. He did not experience the problem in 800x600 resolution.
+
+Elitre was able to reproduce this and added that ""this behavior changes if you zoom in or out (that is, if the buttons get bigger or smaller)""
+
+I reproduce this using Monobook in Firefox 23 on Linux, but zooming the page did not result in changed behaviour for me.",1376141839,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-avc3fsxulmn56uqgbsy6,task_subcomment,NA
+VisualEditor: don't display all tools by default to new editors,"en.wp user Ruud Koot suggests that certain tools, such as underline and font colour (bug 52645) that are not normally wanted/needed in articles shouldn't be available to new editors.
+
+Personally I think everything should be available (this avoids the need for new classes of editor permissions) but just not shown by default. What is shown/not shown by default needs to be configurable on-wiki per wiki (and possibly per namespace).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49617",1375957260,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-vemzxauwwwilvulip65t,task_description,invalid
+VisualEditor: don't display all tools by default to new editors,This has been somewhat overtaken by changes to the toolbar; closing as INVALID.,1383015740,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vemzxauwwwilvulip65t,task_subcomment,NA
+Parsoid or VisualEditor:  __NOTOC__ sometimes replaced by copy of categories,"en.wp user Ruud Koot reports that occasionally he gets "" weird, random and unexplainable corruptions of wikitext on save"" when using the VisualEditor.
+
+The only example he gives is ""e.g., a __NOTOC__ being replaced with a copy of the categories""
+
+Bug 48231 might have something to do with this, but I confess to not understanding all the technical language there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375955220,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ssrgubmui6ycz46f7lkd,task_description,declined
+Parsoid or VisualEditor:  __NOTOC__ sometimes replaced by copy of categories,"Never mind.  I found it here.  https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=prev&oldid=567395325 .. No diffs there.  
+
+Looks like his experiments here are at least 3 weeks old.  https://en.wikipedia.org/w/index.php?title=User:Ruud_Koot/Computer_science/Lambda_calculus&action=history
+
+Lot of things have been fixed in the last couple weeks including instances of wikitext getting duplicated.  But 48231 is not related to this.  I am going to close this ticket for now.  We can open new bugs against specific bad diffs when we encounter them.
+
+Thanks for your diligent work in reporting bugs!",1376086189,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ssrgubmui6ycz46f7lkd,task_subcomment,NA
+Parsoid or VisualEditor:  __NOTOC__ sometimes replaced by copy of categories,Can you point me to his bug report (was this on the feedback page)?  It would be easier to debug with a diff if you have easy access to one.,1376085510,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ssrgubmui6ycz46f7lkd,task_subcomment,NA
+VisualEditor: saving fails silently for some large edits,"en.wp user Ruud Koot reports:
+
+""Occasionally, after a medium-sized editing session, the visual editor will silently refuse to save my edits. When clicking the save button the progress bar appears, disappears, and you stay in editing mode, with no new revision appended to the history. Trying again sometimes resolves the problem, sometimes it requires edit operations to be done in a different order or be broken up into smaller increments, saving in-between."" 
+
+He also asks, ""Do you keep any statistics on how often an editor presses the save button versus how many times this actually results in a new revision being saved?""
+
+Bug 51423 might be related.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51243",1375954440,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4hux64flsouxqgjibleh,task_description,declined
+VisualEditor: saving fails silently for some large edits,No subsequent reports or steps to fix; marking as WORKSFORME.,1406598295,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4hux64flsouxqgjibleh,task_subcomment,NA
+VisualEditor: saving fails silently for some large edits,Sorry that possibly related issue is bug 51243,1375954749,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4hux64flsouxqgjibleh,task_subcomment,NA
+VisualEditor: Bulleted bullets and bulleted headers produced; can't save,"en.wp user Ruud Koot reports:
+""When performing structural editing tasks (i.e. things which are slight more complex than changing typos or adding a sentence in the middle of an existing paragraph) it is very easy to get the editor into some weird state where it is impossible to get out of other than aborting the edit session and trying again more carefully. This includes things like introducing ""bulleted headers"" and ""bulleted bullets"", which cannot possibly be represented as wikitext.""
+
+He notes that ""Copying and pasting around text and editing pages with tables [is a] fairly reliable method"" to reproduce it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375953840,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xyg7preywhwlpczuaps6,task_description,declined
+VisualEditor: Bulleted bullets and bulleted headers produced; can't save,">>! In T54639#1091705, @Thryduulf wrote:
+> I don't see a need to keep this open any longer, if something similar is reported again a more specific bug can be opened. 
+
+Thank you for the quick reply! Sounds reasonible, closing as declined (as we cannot reproduce anymore).",1425633241,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xyg7preywhwlpczuaps6,task_subcomment,NA
+VisualEditor: Bulleted bullets and bulleted headers produced; can't save,"I don't recall this error, and I too can't reproduce anything now using Firefox 30.  Given that it's been ~18 months since the report, it's likely this has been fixed by some other update in the meanwhile.
+
+I don't see a need to keep this open any longer, if something similar is reported again a more specific bug can be opened. ",1425549798,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xyg7preywhwlpczuaps6,task_subcomment,NA
+VisualEditor: Bulleted bullets and bulleted headers produced; can't save,"Hi @Thryduulf! Sorry that nobody has taken a look at this report yet and given feedback.
+
+I tried copying bullets around on https://en.wikipedia.org/wiki/User:AKlapper_%28WMF%29/Sandbox?veaction=edit but could not reproduce anything weird in Firefox 36 on Fedora 21.
+
+Are there any specific steps to reproduce these problems, or edits / diffs that could be linked to? Any specific browser involved?
+
+Setting task status to STALLED for the time being; please reset task status once there are clearer steps to reproduce. Thanks!",1425487218,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xyg7preywhwlpczuaps6,task_subcomment,NA
+VisualEditor: Difficult to get a blank line when the page starts with a bulleted list,"If a page starts with a bulleted list, there's no way to put the cursor ""in front of"" the list styling.  If you want to add a non-list paragraph, you have to make a new, blank first bullet item and then remove the list formatting from the paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52032",1375918560,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gwksqe4mofbzkamj67mf,task_description,invalid
+VisualEditor: Difficult to get a blank line when the page starts with a bulleted list,"Seems to be resolved - checked on the page https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575308394. 
+The text is easily added on a new line before the first bullet.",1420846571,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-gwksqe4mofbzkamj67mf,task_subcomment,NA
+VisualEditor: Difficult to get a blank line when the page starts with a bulleted list,"Sorry, that last line should reference bug 52032.",1380645177,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gwksqe4mofbzkamj67mf,task_subcomment,NA
+VisualEditor: Difficult to get a blank line when the page starts with a bulleted list,"To reproduce:
+1: Load a page in VE that starts with a bulleted list e.g. https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575308394
+2: Try to add text before the first bullet.
+
+It is possible that fix for bug 52302 might also resolve this issue.",1380645144,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gwksqe4mofbzkamj67mf,task_subcomment,NA
+VisualEditor: Edit notices don't scroll,"Today's Featured Article edit notice displayed in Firefox 22/Linux/Monobook on a 481px high window
+
+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).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51755
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52667
+
+**Attached**: {F11480}",1375860960,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-i6f5p5xjfmxdo6ubzpmu,task_description,resolved
+VisualEditor: Edit notices don't scroll,"
+
+*** This bug has been marked as a duplicate of bug 50885 ***",1377446690,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-i6f5p5xjfmxdo6ubzpmu,task_subcomment,NA
+VisualEditor: Edit notices don't scroll,"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.",1375951466,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-i6f5p5xjfmxdo6ubzpmu,task_subcomment,NA
+"Wikimedia editors aren't automatically enrolled in Bugzilla, reducing VE bug reporting","**Author:** `gnu`
+
+**Description:**
+The unusually buggy deployment of the VisualEditor has caused large numbers of English Wikipedia editors to have bugs to report.  But the process of reporting bugs is a cumbersome many-step process -- starting with a requirement to ""log in"" using a credential that most editors do not have.
+
+The rest of the Wikipedia universe uses a universal login system in which you log in with the same username and password to everything, and it all works together.  Somehow Bugzilla didn't get integrated with that.
+
+So instead anyone with a bug report for Visual Editor -- assuming they can even find Bugzilla, perhaps from a comment in an RFC about disabling the Visual Editor, as I found it -- then has to get through the ""New User"" process, which includes providing an email address, checking mail at that address, and accessing a URL which then demands that a new password be created and remembered.
+This step should be avoided for logged-in Wikipedia users.
+
+I'm sure that many, many Visual Editor bugs are noticed by editors, but are never reported due to the pain of the reporting process.  This shortage of bug reports may serve the political purposes of the WMF in attempting to ram the new editor down the throats of the community, but it is not a good management practice, nor will it result in eliminating the bugs that make the Visual Editor too troublesome for naive use at this point.
+
+(The remaining process of bug reporting is also cumbersome and complex -- but 
+in this bug report I have no suggestions on how to fix that.)
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1375844100,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ud6rksuxulevqjsfqs6h,task_description,resolved
+"Wikimedia editors aren't automatically enrolled in Bugzilla, reducing VE bug reporting","(In reply to comment #0)
+> The rest of the Wikipedia universe uses a universal login system in which you
+> log in with the same username and password to everything, and it all works
+> together.  Somehow Bugzilla didn't get integrated with that.
+
+That's bug 14487. If you don't want to create a Bugzilla account you can report issues at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback .
+
+*** This bug has been marked as a duplicate of bug 14487 ***",1375847060,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ud6rksuxulevqjsfqs6h,task_subcomment,NA
+"VisualEditor: Label for beta notice/menu should use mixed case not all caps (""Beta"" not ""BETA"")","From en.wp user Cryptic C62:
+The beta button on the toolbar ""should not be labelled ""Beta"", not ""BETA"". The latter looks like it might be a mysterious acronym. ""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375820700,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rvrst7lvd6twcpeipdkt,task_description,invalid
+"VisualEditor: Label for beta notice/menu should use mixed case not all caps (""Beta"" not ""BETA"")","This label no longer exists, but instead is just the help ""(?)"" icon.",1393528505,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rvrst7lvd6twcpeipdkt,task_subcomment,NA
+"VisualEditor: Label for beta notice/menu should use mixed case not all caps (""Beta"" not ""BETA"")","(In reply to comment #1)
+> Can I work on this bug? I know it has been assigned to someone but looks like
+> nothing has happened here for sometime.
+
+It looks like that's the default assignee for bugs in this component. In general it should be fine to do these.",1390957191,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rvrst7lvd6twcpeipdkt,task_subcomment,NA
+"VisualEditor: Label for beta notice/menu should use mixed case not all caps (""Beta"" not ""BETA"")","**aravikn** wrote:
+
+Can I work on this bug? I know it has been assigned to someone but looks like nothing has happened here for sometime.",1390221344,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rvrst7lvd6twcpeipdkt,task_subcomment,NA
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"Where articles use the {{ref}} and  {{note}} pair of templates to generate footnotes, e.g. [[List of highest points of Canadian provinces and territories]], it is impossible to edit the contents of the notes in VisualEditor.
+
+The {{ref}} template is editable in the transclusion editor, and works as expected.
+
+The {{note}}-generated notes are apparently one block. No transclusion icon or indication of uneditablility (green stripes) appears on mouseover or when the block is clicked. 
+
+If a link in the notes is clicked it functions as a link would in read mode- ie. the link is followed and you leave the page. VE gives no warning about unsaved edits (although Firefox does).
+
+If the backlink to the location of the {{ref}} template is clicked it functions as above - i.e. it loads the page in read mode at the position of the note, exactly as if you had followed a link to that anchor from any other page on the internet.
+
+It is possible to select the block when selecting content before and after the block, although no indication is given that it has been selected. Once selected it is possible to apply bold/italic formatting to the block and other selected text using the B/I buttons, but it is not then possible to remove it using these buttons while the note block is selected. It is possible to remove bold/italic using the clear format button. The clear format button does not remove any links in the notes block, but does remove links from any other text selected at the same time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1375800120,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_description,declined
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"Cite.php is designed a certain (bad) way. It has issues, and we will replace it at some point, but the way to fix its issues is not to make horrible hacks in wikitext using loopholes over-looked when the code was written to try to re-design in.
+
+This is one of those cases, and is not sanely supportable in VisualEditor, so I'm going to mark this as WONTFIX.",1393541169,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_subcomment,NA
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"cklim: Not sure what your random HTML and image posted here has to do ""VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system"".
+Please file a separate ticket as this seems unrelated to this bug report.",1393068100,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_subcomment,NA
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"**cklim074** wrote:
+
+<head><meta content=""width=device-width; height=device-height;"" name=""viewport""><link href=""resource://gre/res/ImageDocument.css"" rel=""stylesheet""><link href=""resource://gre/res/TopLevelImageDocument.css"" rel=""stylesheet""><link href=""chrome://global/skin/media/TopLevelImageDocument.css"" rel=""stylesheet""><title>attachment.cgi (PNG Image, 1247&nbsp;×&nbsp;669 pixels)</title></head><body><img class=""decoded overflowing"" alt=""http://bug-attachment.wikimedia.org/attachment.cgi?id=14163"" src=""http://bug-attachment.wikimedia.org/attachment.cgi?id=14163""></body>",1393041491,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_subcomment,NA
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"**cklim074** wrote:
+
+<head><meta content=""width=device-width; height=device-height;"" name=""viewport""><link href=""resource://gre/res/ImageDocument.css"" rel=""stylesheet""><link href=""resource://gre/res/TopLevelImageDocument.
+
+<head><meta content=""width=device-width; height=device-height;"" name=""viewport""><link href=""resource://gre/res/ImageDocument.css"" rel=""stylesheet""><link href=""resource://gre/res/TopLevelImageDocument.css"" rel=""stylesheet""><link href=""chrome://global/skin/media/TopLevelImageDocument.css"" rel=""stylesheet""><title>attachment.cgi (PNG Image, 1247&nbsp;×&nbsp;669 pixels)</title></head><body><img class=""decoded overflowing"" alt=""http://bug-attachment.wikimedia.org/attachment.cgi?id=14163"" src=""http://bug-attachment.wikimedia.org/attachment.cgi?id=14163""></body>
+
+**Attached**: {F11426}",1393041446,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_subcomment,NA
+VisualEditor: Don't wait indefinitely for gadget servers that are not responding,"When a user has installed a gadget that relies on data from an external server, VisualEditor appears to wait indefinitely for that server to respond. Normally this is OK, but when that server is down VE will apparently wait forever (or at least longer than the 5 minutes I was prepared to wait) for a response.
+
+The source editor appears to give up after a wile (2 minutes?), and loads as if the gadget was not called. VE should exhibit this behaviour too.
+
+Tested with the HAPPI gadget ([[User:EpochFail/HAPPI]]). As of 21:52 UTC 05 August 2013 that gadget depends on a server at wikipedia.grouplens.org that is not responding
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375739580,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-brb5wektguex52kczga7,task_description,invalid
+VisualEditor: Don't wait indefinitely for gadget servers that are not responding,"Surely this is the responsibility of the gadget's author?
+
+Also, not sure if the wikitext editor executes poorly-responding gadgets, or it's just apparent happenstance. Either way, 120 seconds is about an order of magnitude too high.
+
+Sorry for very slow triage.",1390419026,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-brb5wektguex52kczga7,task_subcomment,NA
+VisualEditor or Parsoid: inserted HTML code instead of Wikilink,"At line 42 of https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&diff=567254040&oldid=566841354 attempting replace what appeared to be an empty image caption with ""The [[Sun]]"" (using ctrl+k for the link, no wikicode) resulted in the insertion instead of:
+The <a style=""white-space:nowrap"" data-mw=""{&quot;target&quot;:{&quot;wt&quot;:&quot;val&quot;,&quot;href&quot;:&quot;../Template:Val&quot;},&quot;params&quot;:{&quot;1&quot;:{&quot;wt&quot;:&quot;4.6&quot;},&quot;ul&quot;:{&quot;wt&quot;:&quot;byr&quot;}},&quot;i&quot;:0}"" rel=""mw:WikiLink"" href=""Sun"">Sun</a>
+
+The images were left over from testing for Bug 52341 and so that bug may be related.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375709160,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4xuz3vb5yze6xii6usyj,task_description,declined
+VisualEditor or Parsoid: inserted HTML code instead of Wikilink,I'm pretty sure this was a horrible artefact of a nasty bug we fixed back in September; provisionally marking as WORKSFORME. Sorry for the ludicrously-slow triage.,1401418799,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4xuz3vb5yze6xii6usyj,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"visual editor easily doubles mouse clicks and key presses. this can be seen, amongst others, on section editing, saving, adding a reference. to avoid bug reports in the line of ""please remove one mouse click while creating a reference"" create a (visual) design guideline mandatory to follow for all developers to minimize mouse clicks and key presses, and maximise screen estate available for editing/viewing the article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375607280,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-kvdgcfvnalphobirayqv,task_description,declined
+VisualEditor: Create a design guideline to minimize clicks and key presses,"Again: This won't be handled in Bugzilla, however pointing to a better place where to discuss would be very good.  Playing the ""I know it's the wrong place but still I want to discuss it here"" card isn't much better either though. :)
+
+Please don't reopen as a sign of disagreement. Thanks.",1376561195,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"james, let me reopen this one please. there is a big difference between ""it is our intention"" (whoever ""our"" is) and a crystal clear guideline having as primary target:
+* minimize clicks and key presses
+* response time <3 sec
+this would make it so much easier for new developers as well. and so much easier for testers to point out that something is against the goal. 
+
+as i tried to point out above with examples, people were and still are allowed to increase key presses and mouse-clicks considerable compared to the existing solution. i tried to look for design documents or mail references on some tech list to find a justification for this, but could not find one. 
+
+you as a software developer surely know that nothing is more expensive than fixing a design bug. and nothing is more expensive than finding a bug late. just to take an arbitrary url to support this: http://blog.bootstraptoday.com/2011/12/25/early-detection-of-bugs-can-save-up-to-22-billion-yearly/ 
+
+so, please do not play the ""a good thing but not the right place"" card. which then ends up nowhere. you can close the ticket if you either create this guideline, or successfully have a (public verifyable) decision in whatever place you consider right for a decision like this.",1376539525,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"Of course, this is already our intention. There is nothing to ""create"".
+
+Bugzilla is not really the right place to suggest user experience improvements like this - though walk-through data like you've given is hugely valuable, and if you have more I would love for you to share it.",1376521216,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"for bug48429, section editing, i tried VE at https://en.wikipedia.org/wiki/Jos%C3%A9_Mourinho. to repeat the clicks and key presses here:
+* 1 click and 15 secs to edit
+* 1 click to make go a away a note (see attachment)
+* 1 click to edit summary
+* 1 click and 20 secs to review changes
+* 1 click to return to save form
+* 1 click and 40 secs to save
+* 5* pg down to go to the section just edited
+
+while text editor sections can be edited with:
+* 1 click and 2 secs to open
+* 1 click and 2 secs to preview
+* 1 pg-down to find the save button (could be avoided by re-placing the button)
+* 1 click and 10 secs to save
+
+old is ideally 3 clicks, new is 6 clicks + 5 key presses.
+
+but, there are other cases as well. to add a category with hotcat is one click and a key press to confirm. It auto-corrects even the spelling to upper case. VE takes 8 clicks, a refresh, and scrolling down, if i counted correctly.",1375774987,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"Which exact problem do you see with the current situation, that made you file this bug report?",1375620096,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+De.WP experiences wired edit labels on conversation pages,"Currently, De.WP talk, user talk, Wikipedia, Wikipedia talk..pages show for the last section not [Edit source] as En/Es/xy.WP do but [Add section / Edit source code / Add section] (Abschnitt hinzufügen Quelltext bearbeiten Abschnitt hinzfügen). It neither breaks anything technically as far as I can tell right now nor does it mix in VE interface but, where ever it might come from, it should be fixed asap
+
+http://de.wikipedia.org/w/index.php?title=Diskussion:Immanuel_Kant&oldid=120880638
+
+http://de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:JEissfeldt_(WMF)&oldid=120853192#VisualEditor_.2A_Projektseiten
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1375491060,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-33n5y7ewqlbefwxwacox,task_description,invalid
+De.WP experiences wired edit labels on conversation pages,"This is an issue with a script at [[de:MediaWiki:Common.js]].
+
+In the section ""erzeuge einen ""Neuen Abschnitt""-Link an der letzten Überschrift"", replace ""$( 'span.mw-editsection:last a' )"" with ""$( 'span.mw-editsection:last a:last' )"". That should be enough to fix it.",1375492148,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-33n5y7ewqlbefwxwacox,task_subcomment,NA
+Blacklist category for excluding pages from VisualEditor,"It would be helpful to be able to selectively disable VisualEditor (we should to indicate to a user who'd otherwise see VisualEditor that it is disabled, to reduce confusion). This would enable users to shield pages where VisualEditor/Parsoid cause roundtrip issues.
+
+A hidden blacklist category could be included in a page or template to achieve the desired effect, and could be used by developers to prioritize roundtripping issues.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375487760,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-qpvwyqg5nibzkozzdov5,task_description,resolved
+Blacklist category for excluding pages from VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 52141 ***",1375488138,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-qpvwyqg5nibzkozzdov5,task_subcomment,NA
+VisualEditor: Image thumbnails that don't specify size should render at the wiki-default size,"If one opens the VE editing interface, the user experience in relation to image formats varies significantly. The report: 
+
+http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121153156#Bilder_werden_im_VE_kleiner_angezeigt
+
+has several examples with different browsers like 
+
+FF 22 / Win 7: edgewise images smaller; rest bigger.
+Chrome 28 / Win 7: all significantly smaller.
+
+See also screenshots in perma link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375487460,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-7bui5nacoyzpq7m5e4vx,task_description,resolved
+VisualEditor: Image thumbnails that don't specify size should render at the wiki-default size,"Merging with bug 47804.
+
+*** This bug has been marked as a duplicate of bug 47804 ***",1380666480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7bui5nacoyzpq7m5e4vx,task_subcomment,NA
+VisualEditor: Image thumbnails that don't specify size should render at the wiki-default size,"When viewing a page, images that are specified as [[File:Foo.jpg|thumb|Caption]] render as 220px wide (en.wp)/180px wide (de.wp), regardless of dimensions or aspect ratio.
+
+In visual editor, images specified the same way render so as not to exceed 190px wide by 212px high. 
+
+This means that images can appear at very different sizes in the VE editing surface to how they appear on the rendered page. This is especially true for very tall images.
+
+Example to better illustrate this, compare the two views of this page
+View mode: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575350620 
+VE edit mode: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575350620&veaction=edit",1380666087,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7bui5nacoyzpq7m5e4vx,task_subcomment,NA
+VisualEditor: uneditable table lines displayed wrong,"The displayed table (Firefox 22/Ubuntu)
+
+See [[fr:Special:redirect/revision/95505705#Pr.C3.A9sidents_de_l.27universit.C3.A9]]
+
+The 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 <tr> is wrapped in a <span>. Not really WYSIWYG…
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11257}",1375486440,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-ocna2wajo3o5voxuppid,task_description,resolved
+VisualEditor: uneditable table lines displayed wrong,"Yes, merging with bug 50607.
+
+*** This bug has been marked as a duplicate of bug 50607 ***",1385374740,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ocna2wajo3o5voxuppid,task_subcomment,NA
+VisualEditor: uneditable table lines displayed wrong,I think this might be a duplicate of bug 50607,1378374678,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ocna2wajo3o5voxuppid,task_subcomment,NA
+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 <ref></ref> 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",1375473900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tvsxq36upc6ipnvhxpyk,task_description,resolved
+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.",1377862353,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-tvsxq36upc6ipnvhxpyk,task_subcomment,NA
+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.",1377820107,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tvsxq36upc6ipnvhxpyk,task_subcomment,NA
+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 ***",1377819444,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tvsxq36upc6ipnvhxpyk,task_subcomment,NA
+"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",1375462920,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wedvkdl2s27csm5sxz7t,task_description,resolved
+"VisualEditor: if the title page starts with a dot, VE won't load","
+
+*** This bug has been marked as a duplicate of bug 51308 ***",1375464734,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-wedvkdl2s27csm5sxz7t,task_subcomment,NA
+"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).",1375463353,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wedvkdl2s27csm5sxz7t,task_subcomment,NA
+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}",1375403700,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-klrivpj5pu4qmrhtcgbi,task_description,resolved
+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 ***",1375991502,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-klrivpj5pu4qmrhtcgbi,task_subcomment,NA
+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 <td>.
+
+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",1375401360,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-dpkxtqdack6wacscxvhg,task_description,resolved
+VisualEditor: {{clr}} prevents user from editing content,"
+
+*** This bug has been marked as a duplicate of bug 50551 ***",1395360523,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dpkxtqdack6wacscxvhg,task_subcomment,NA
+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.",1378423467,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dpkxtqdack6wacscxvhg,task_subcomment,NA
+"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",1375391460,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gbm6kyiyozz73ztd6xzq,task_description,resolved
+"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 ***",1375391536,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gbm6kyiyozz73ztd6xzq,task_subcomment,NA
+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:
+
+> <selected>
+> 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
+> </selected>
+> \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 <selected>NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar.
+> h2.References
+> references.
+> \n
+> \n
+> h2.External</selected> 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 <selected>NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar.</selected>
+> h2.References
+> references.
+> \n
+> \n
+> h2.External links
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375381560,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-idjdigelfjcuvhcx24zy,task_description,resolved
+VisualEditor: Undoing a larger cut restores selection incorrectly,This was fixed in the selection re-writes.,1385398843,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-idjdigelfjcuvhcx24zy,task_subcomment,NA
+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}",1375345320,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_description,duplicate
+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 ***",1386112687,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+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.",1379849577,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+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!",1375486433,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+Stray bullet points around template and strange editing around them,Reproduced in Chrome 28 and Opera 12.16.,1375394665,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+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]] <span style=""font-size:.95em;font-weight:bold;color:#555;"">(engelska)</span>
+*",1375345880,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+Stray bullet points around template and strange editing around them,This is probably a ContentEditable problem.,1375345435,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+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",1375319220,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-vs6adtg7gilhg5r2g74x,task_description,resolved
+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 ***",1375319436,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vs6adtg7gilhg5r2g74x,task_subcomment,NA
+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:
+
+ <div class=""do-not-make-smaller refsection references-column-count references-1column"">
+ <references />
+ </div>
+
+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",1375232040,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qwinndvqnthzbul47nb3,task_description,declined
+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).,1393528114,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qwinndvqnthzbul47nb3,task_subcomment,NA
+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?",1378424053,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qwinndvqnthzbul47nb3,task_subcomment,NA
+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}",1375213740,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-ifh6gryuu6hee6pcadvb,task_description,invalid
+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.",1415880871,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ifh6gryuu6hee6pcadvb,task_subcomment,NA
+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}",1385522381,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ifh6gryuu6hee6pcadvb,task_subcomment,NA
+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",1380645842,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ifh6gryuu6hee6pcadvb,task_subcomment,NA
+VisualEditor: Following links in image captions that have a large <font size=> 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 <font size=12>, 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. <font size=12>text with a [[link]]</font>.
+
+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}",1375209840,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aowfgq4eh3wcjsqyftty,task_description,resolved
+VisualEditor: Following links in image captions that have a large <font size=> 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 ***",1385396898,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aowfgq4eh3wcjsqyftty,task_subcomment,NA
+VisualEditor: Following links in image captions that have a large <font size=> 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.,1375227469,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aowfgq4eh3wcjsqyftty,task_subcomment,NA
+VisualEditor: Following links in image captions that have a large <font size=> 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.",1375210111,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aowfgq4eh3wcjsqyftty,task_subcomment,NA
+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",1375182720,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_description,declined
+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.",1384945365,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.
+
+:-)",1384871317,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.",1384864881,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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 :)",1383834351,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.",1383293007,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.",1383292738,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.",1383282685,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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).",1382972546,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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 )",1377514974,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+VisualEditor should be themeable by the user with custom CSS,"Gryllida adds,
+<<To be quite honest, the first thing that I see wrong in the visual editor is the black-and-white style of icons, similar to what Google products uses. It is not 1980s when everything was black-and-white, nor it is 1990s when people used 256-color icons; it is 2013. [...] I believe it is important for accessibility to at least let users choose from a set of themes for the VisualEditor toolbar, if not alter the default theme.>>",1377427418,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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}",1375179540,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-juxrg4k7aci5xpwlvsaq,task_description,resolved
+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 ***",1376325366,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-juxrg4k7aci5xpwlvsaq,task_subcomment,NA
+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",1375176300,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-vbh2rbaxi3v4g2vosvk6,task_description,resolved
+Parsoid or VisualEditor: nowiki added around space following HTML comment,"
+
+*** This bug has been marked as a duplicate of bug 50758 ***",1375199871,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-vbh2rbaxi3v4g2vosvk6,task_subcomment,NA
+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",1375169040,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-poqv6admiczpvguuyu43,task_description,declined
+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.",1385396737,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-poqv6admiczpvguuyu43,task_subcomment,NA
+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.",1375263838,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-poqv6admiczpvguuyu43,task_subcomment,NA
+Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,"Labeled Section Transclusion (<section begin=""2012-07-monthly""/>Text here<section end=""2012-07-monthly""/>) 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",1375142220,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-2i2pvcby76cfowf624hh,task_description,resolved
+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 <section> 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 ***",1376428165,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+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.",1375203999,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,whoops. misfire.,1375203841,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,"
+
+*** This bug has been marked as a duplicate of bug 51462 ***",1375203763,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+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. :-)",1375143543,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+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,1375142308,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+"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}",1375142160,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xvbh6q43vypy6tjr3wjo,task_description,resolved
+"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 ***",1376073139,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xvbh6q43vypy6tjr3wjo,task_subcomment,NA
+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",1375138020,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-zg6asep6oadhz6pkrf4o,task_description,declined
+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.",1375141752,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zg6asep6oadhz6pkrf4o,task_subcomment,NA
+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",1375136040,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-yokifd7zmqwcieiz3iiy,task_description,resolved
+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 ***",1385384185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yokifd7zmqwcieiz3iiy,task_subcomment,NA
+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",1375130640,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ahjlajk3zasbqo4br4bs,task_description,resolved
+VisualEditor: template substituted in,This was a recurring Parsoid bug which is now fixed; closing. Sorry for slow triage.,1385395969,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ahjlajk3zasbqo4br4bs,task_subcomment,NA
+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",1375105920,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-d4phvcwb6pak5wn2vbdh,task_description,resolved
+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 ***",1383282089,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d4phvcwb6pak5wn2vbdh,task_subcomment,NA
+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.",1375133339,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-d4phvcwb6pak5wn2vbdh,task_subcomment,NA
+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",1375088700,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-etdxsdkmhg4aoyrvdmmw,task_description,resolved
+reference clipboard errors,"
+
+*** This bug has been marked as a duplicate of bug 49396 ***",1375134084,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-etdxsdkmhg4aoyrvdmmw,task_subcomment,NA
+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}",1375057440,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wgr5qefyrk6vxixqgywz,task_description,resolved
+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 ***",1380221526,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wgr5qefyrk6vxixqgywz,task_subcomment,NA
+VisualEditor: Toolbar should fit on landscape iPad (and average non-maximised windows in general),Same as bug 51000?,1380219240,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-wgr5qefyrk6vxixqgywz,task_subcomment,NA
+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}",1380219110,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-wgr5qefyrk6vxixqgywz,task_subcomment,NA
+"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",1375037280,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_description,declined
+"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"":""<p>x</p>\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.",1384198086,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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.",1384198025,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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"":""<p>x</p>\n\n""}}",1384196822,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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.",1384196302,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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.",1375141400,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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) {
+    ...
+  }",1375047772,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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",1375045603,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+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",1374988380,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-nuh252st2e54ff56mbpe,task_description,declined
+VisualEditor doesn't confirm closing window,Yeah I can confirm as well. Not sure when it started working again.,1390434737,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-nuh252st2e54ff56mbpe,task_subcomment,NA
+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?""",1390418026,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-nuh252st2e54ff56mbpe,task_subcomment,NA
+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.",1390417310,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nuh252st2e54ff56mbpe,task_subcomment,NA
+"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",1374947400,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-t6h3rucl4ojovdzxkq66,task_description,resolved
+"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 ***%%%",1375381691,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-t6h3rucl4ojovdzxkq66,task_subcomment,NA
+"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:
+
+<p data-parsoid=""{&quot;dsr&quot;:[0,45,0,0]}"" class=""ve-ce-branchNode"">
+<span class=""ve-ce-branchNode-slug ve-ce-branchNode-inlineSlug"">&#65279;</span></p>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374877260,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-3ew3gilga74djx2te24b,task_description,resolved
+"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 ***",1375199198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ew3gilga74djx2te24b,task_subcomment,NA
+"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",1374905359,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-3ew3gilga74djx2te24b,task_subcomment,NA
+"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.",1374880550,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-3ew3gilga74djx2te24b,task_subcomment,NA
+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 <br clear=all> was duplicated minus the leading <
+
+Possibly related to bug 51304?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374877200,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-oqjy24dqtbqambra54dm,task_description,declined
+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.",1379848985,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oqjy24dqtbqambra54dm,task_subcomment,NA
+VisualEditor or Parsoid: Breaks and partially duplicates html tag,"Given the proximity of the image, im guessing this is bug 52107.",1375737774,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-oqjy24dqtbqambra54dm,task_subcomment,NA
+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",1374873360,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-jwf46mqjltex4ny7fpad,task_description,invalid
+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?)",1385398255,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jwf46mqjltex4ny7fpad,task_subcomment,NA
+VisualEditor - EditIntro is incorrectly linked in the monobook skin.,Confirming problem exists.  The fix probably needs to be made at [[MediaWiki:Common.js]],1374907792,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jwf46mqjltex4ny7fpad,task_subcomment,NA
+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",1374862080,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mx57agjpr44kackrkfz2,task_description,declined
+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.",1379847739,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mx57agjpr44kackrkfz2,task_subcomment,NA
+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",1375107801,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-mx57agjpr44kackrkfz2,task_subcomment,NA
+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.",1374903910,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-mx57agjpr44kackrkfz2,task_subcomment,NA
+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.",1374892576,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-mx57agjpr44kackrkfz2,task_subcomment,NA
+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/<i>foo<\/i>/g;"" | node parse --html2wt
+[[Foo|'''foo''']]
+
+[subbu@earth lib] echo ""[[Foo|'foo']]"" | node parse | sed ""s/foo/<b>foo<\/b>/g;"" | node parse --html2wt
+[[Foo|''''foo'''']]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374857700,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-pxbsw644f45j6giahmh5,task_description,resolved
+Missing nowiki escaping when single quotes wrap new i/b tags,Deployed and tested in production.,1375305913,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+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",1375108318,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+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",1375070667,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+Missing nowiki escaping when single quotes wrap new i/b tags,"Change 76162 merged by jenkins-bot:
+(Bug 52103) <nowiki/> escape when single quotes wrap new i/b tags
+
+https://gerrit.wikimedia.org/r/76162",1374946378,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+Missing nowiki escaping when single quotes wrap new i/b tags,"Change 76162 had a related patch set uploaded by Subramanya Sastry:
+(Bug 52103) <nowiki/> escape when single quotes wrap new i/b tags
+
+https://gerrit.wikimedia.org/r/76162",1374870985,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+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",1374837420,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-inyop7q4zxzxlulleamf,task_description,declined
+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.",1385996565,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-inyop7q4zxzxlulleamf,task_subcomment,NA
+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).",1385396429,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inyop7q4zxzxlulleamf,task_subcomment,NA
+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.",1375183728,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-inyop7q4zxzxlulleamf,task_subcomment,NA
+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"".",1374838260,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-inyop7q4zxzxlulleamf,task_subcomment,NA
+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 <ref> tag, but about template that add the <ref> 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 <ref> 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",1374825720,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-olrhjl5ydsytkfv6yzoo,task_description,resolved
+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 ***",1374880234,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-olrhjl5ydsytkfv6yzoo,task_subcomment,NA
+"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 <nowiki><Tab></nowiki> 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",1374817380,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-3d44p7lu3ycz3cvuwxqd,task_description,resolved
+"Wrong tab-order on the ""Edit summary"" window","
+
+*** This bug has been marked as a duplicate of bug 51918 ***",1374880815,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3d44p7lu3ycz3cvuwxqd,task_subcomment,NA
+"Wrong tab-order on the ""Edit summary"" window","
+
+*** This bug has been marked as a duplicate of bug 50047 ***",1374818679,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-3d44p7lu3ycz3cvuwxqd,task_subcomment,NA
+VisualEditor: only a part of word is linked and <nowiki/> 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, <nowiki/> 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",1374778680,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-yvfkvibbvk27rfmuao7p,task_description,declined
+VisualEditor: only a part of word is linked and <nowiki/> 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.",1374797030,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yvfkvibbvk27rfmuao7p,task_subcomment,NA
+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",1374770400,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ijjtl5hsv4igmy4k6sej,task_description,resolved
+VisualEditor: blanking a page doesn't remove comments,"
+
+*** This bug has been marked as a duplicate of bug 49603 ***",1393271493,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ijjtl5hsv4igmy4k6sej,task_subcomment,NA
+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 .",1391511752,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ijjtl5hsv4igmy4k6sej,task_subcomment,NA
+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",1374765240,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-tghru467viza4owq4m3v,task_description,resolved
+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 ***",1395357259,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tghru467viza4owq4m3v,task_subcomment,NA
+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==<nowiki>{{template}}</nowiki>"" 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.",1378037641,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-tghru467viza4owq4m3v,task_subcomment,NA
+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",1374763800,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fcytooow3nd5c6cwcwl6,task_description,resolved
+TemplateData should allow specifying default values for parameters,"
+
+*** This bug has been marked as a duplicate of bug 51428 ***",1375183466,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fcytooow3nd5c6cwcwl6,task_subcomment,NA
+"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}",1374709260,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mcleu5c4oborex7k7xit,task_description,resolved
+"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.",1377190936,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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.",1377190457,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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&section=3",1374771991,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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.",1374744764,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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.",1374744542,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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?",1374740581,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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",1374697260,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-s2gl74yfgu2t3qm3jv3q,task_description,resolved
+"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.,1385395164,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s2gl74yfgu2t3qm3jv3q,task_subcomment,NA
+"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",1374686580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fyok2cjpctqiorpfldvp,task_description,invalid
+"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)",1376065760,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fyok2cjpctqiorpfldvp,task_subcomment,NA
+"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?",1374704563,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-fyok2cjpctqiorpfldvp,task_subcomment,NA
+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",1374684900,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_description,resolved
+VisualEditor: can't remove missing image,"
+
+*** This bug has been marked as a duplicate of bug 50788 ***",1377623981,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+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.",1376309716,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+VisualEditor: can't remove missing image,I actually moved the above comment to https://bugzilla.wikimedia.org/show_bug.cgi?id=52575 . Thanks.,1375790933,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+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!),1375704777,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+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]]",1374705106,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> 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 
+
+:<nowiki>...in common with the Classes <a href=tel:313 / 314 / 315"">313 / 314 / 315</a> / 507 / 508 units.</nowiki>
+
+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",1374669600,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hekxaxmddcora46opa6e,task_description,invalid
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> 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.,1374690787,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-hekxaxmddcora46opa6e,task_subcomment,NA
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> and refused to save,"Just for reference, the original reporter subsequently noted that they use Ipad IOS6 with Safari",1374683186,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hekxaxmddcora46opa6e,task_subcomment,NA
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> 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).",1374680186,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hekxaxmddcora46opa6e,task_subcomment,NA
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> and refused to save,This may be a VE issue if you are seeing a-href showing up in wikitext on serialization.,1374678107,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-hekxaxmddcora46opa6e,task_subcomment,NA
+VisualEditor: <nowiki> tags not deleted when surrounding element or text is deleted,"User Atethnekos at en.wp reports:
+""If in the source code there is <<nowwiki/>blockquote>, and in VE I select ""<blockquote>"" and delete it, when I save the <nowiki/> 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",1374661620,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-wg4if5a5jfs6ciuoa7x3,task_description,resolved
+VisualEditor: <nowiki> 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 ***",1374879593,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wg4if5a5jfs6ciuoa7x3,task_subcomment,NA
+VisualEditor: Deleting last use of reference should remove the entry from <references>..</references>,"This is related to Bug 51741, which is about adding support for <references>...</references>
+
+If the page already has <references>..</references>, and the last use of a named reference is removed, the entry inside <references>..</references> 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: <ref> tag with name ""rockspot_1"" defined in <references> is not used in prior text.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374657660,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dbgv7dfw47acis2f72rd,task_description,resolved
+VisualEditor: Deleting last use of reference should remove the entry from <references>..</references>,This was done some time ago; sorry for the slow triage.,1385395008,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dbgv7dfw47acis2f72rd,task_subcomment,NA
+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",1374642420,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-53dxg6rsj6uqcm45wss5,task_description,resolved
+VisualEditor: Retain newlines between parameters in transclusion invocations,This was fixed some time ago; sorry for the slow triage.,1385397595,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-53dxg6rsj6uqcm45wss5,task_subcomment,NA
+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",1374979926,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-53dxg6rsj6uqcm45wss5,task_subcomment,NA
+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",1374609540,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-horg3ds56xoznfv445i2,task_description,invalid
+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.",1385382898,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-horg3ds56xoznfv445i2,task_subcomment,NA
+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}",1374608640,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fl755yo3ekdckavdhb4b,task_description,invalid
+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.,1389677471,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+VisualEditor: Inserting media dialog has no confirmation button,Sorry for confirming; the UI design should be a separate bug.,1374706420,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+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.",1374703705,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+VisualEditor: Inserting media dialog has no confirmation button,Bug/enhancement reported as bug 51911.,1374614627,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+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.",1374613964,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+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.,1374608768,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+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",1374588720,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-4r4lbhkxqhogotfzas57,task_description,resolved
+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.",1385394193,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4r4lbhkxqhogotfzas57,task_subcomment,NA
+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",1374583260,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-fz3rgh4ljjpvwe3terlp,task_description,declined
+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.",1390607728,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fz3rgh4ljjpvwe3terlp,task_subcomment,NA
+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?",1374592005,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fz3rgh4ljjpvwe3terlp,task_subcomment,NA
+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",1374573300,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-w26cnf2uzn6whhzpd4p5,task_description,declined
+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).",1408666032,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-w26cnf2uzn6whhzpd4p5,task_subcomment,NA
+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.,1408597771,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-w26cnf2uzn6whhzpd4p5,task_subcomment,NA
+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.],1378939553,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-w26cnf2uzn6whhzpd4p5,task_subcomment,NA
+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",1374524640,PHID-USER-fgzcdbj3je3ksnhufo47,PHID-TASK-fgo5ntod4pt7hex3reuf,task_description,resolved
+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.,1385395314,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fgo5ntod4pt7hex3reuf,task_subcomment,NA
+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",1374518520,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ibvdz6zkyuw2mud34vwr,task_description,resolved
+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 ***",1374645680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ibvdz6zkyuw2mud34vwr,task_subcomment,NA
+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.",1374522496,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ibvdz6zkyuw2mud34vwr,task_subcomment,NA
+Long lines in <pre> blocks don't cause page formatting to extend right. The html page is extended massively further than needed,"Long <pre> blocks rendered in Firefox 22 on Xubuntu Linux. Monobook skin.
+
+When <pre> blocks contain lines longer than the width of the page, the <pre> 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}",1374516900,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-o6hvv37kdmfpbrbf7mjf,task_description,resolved
+Long lines in <pre> 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 ***",1374526756,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-o6hvv37kdmfpbrbf7mjf,task_subcomment,NA
+Long lines in <pre> 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.",1374518559,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-o6hvv37kdmfpbrbf7mjf,task_subcomment,NA
+Long lines in <pre> 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.,1374517626,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-o6hvv37kdmfpbrbf7mjf,task_subcomment,NA
+"Removing a heading is hard, leaving ==<nowiki/>== 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.
+
+==<nowiki/>==
+
+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",1374514920,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-veppenlnczvh4hbbxwsw,task_description,resolved
+"Removing a heading is hard, leaving ==<nowiki/>== or turning the next paragraph into a heading","
+
+*** This bug has been marked as a duplicate of bug 50100 ***",1374609807,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-veppenlnczvh4hbbxwsw,task_subcomment,NA
+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",1374512940,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bsoljznx4zww5csa3zth,task_description,declined
+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).",1385392185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bsoljznx4zww5csa3zth,task_subcomment,NA
+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}",1374512940,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-tvk7p5y33xg5evlkkbgh,task_description,resolved
+VisualEditor renderizes the image a lot bigger than it should,"
+
+*** This bug has been marked as a duplicate of bug 51628 ***",1374548109,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tvk7p5y33xg5evlkkbgh,task_subcomment,NA
+VisualEditor renderizes the image a lot bigger than it should,"Parsoid keeps the code as is:
+http://parsoid.wmflabs.org/_rt/pt/?oldid=36476193",1374513396,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-tvk7p5y33xg5evlkkbgh,task_subcomment,NA
+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]]",1374513316,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-tvk7p5y33xg5evlkkbgh,task_subcomment,NA
+"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",1374511320,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_description,resolved
+"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).",1394528224,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+"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. ***,1394503905,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+"VisualEditor: When window is narrowed, article title can display over the top of the toolbar",This was fixed by Trevor in January.,1394477948,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+"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.",1374519760,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+"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.",1374512088,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+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",1374498600,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-2ub5t2oupkp4z4qo32ce,task_description,resolved
+Transclusion editor: remove template creates blank dialog,"
+
+*** This bug has been marked as a duplicate of bug 50281 ***",1374702151,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-2ub5t2oupkp4z4qo32ce,task_subcomment,NA
+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""",1374701365,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-2ub5t2oupkp4z4qo32ce,task_subcomment,NA
+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.",1374696871,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-2ub5t2oupkp4z4qo32ce,task_subcomment,NA
+"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}",1374495480,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-4itryfnmayohwwozkuws,task_description,resolved
+"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.",1375726508,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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",1375725903,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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",1375204451,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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.",1375202187,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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.",1375202101,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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),1375147278,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+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",1374495000,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-calntit5bgsnncojx237,task_description,resolved
+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 ***",1374854170,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-calntit5bgsnncojx237,task_subcomment,NA
+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.",1374853627,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-calntit5bgsnncojx237,task_subcomment,NA
+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}",1374481140,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-kuzyc5hs4c2r4b2fex4f,task_description,resolved
+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",1374513446,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kuzyc5hs4c2r4b2fex4f,task_subcomment,NA
+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 ***",1374489509,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kuzyc5hs4c2r4b2fex4f,task_subcomment,NA
+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",1374487397,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kuzyc5hs4c2r4b2fex4f,task_subcomment,NA
+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",1374470760,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-ayjpiyllgpwjsso4fzvt,task_description,resolved
+TemplateData for redirected templates,"
+
+*** This bug has been marked as a duplicate of bug 50964 ***",1374641783,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ayjpiyllgpwjsso4fzvt,task_subcomment,NA
+TemplateData for redirected templates,Discussed at http://en.wikipedia.org/wiki/Wikipedia_talk:VisualEditor/TemplateData#What_about_redirected_templates,1374471289,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-ayjpiyllgpwjsso4fzvt,task_subcomment,NA
+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",1374415800,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-m2dyfyycv5j7jnwg3sup,task_description,resolved
+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.",1385392734,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2dyfyycv5j7jnwg3sup,task_subcomment,NA
+"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",1374349320,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-ydxhivupzag4qu4llhwx,task_description,declined
+"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.",1395355910,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ydxhivupzag4qu4llhwx,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'info' of undefined"" (when saving the page)",Which article did this occur on?,1374367709,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ydxhivupzag4qu4llhwx,task_subcomment,NA
+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",1374343560,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gkasmmcbpikhl6gq6kg5,task_description,resolved
+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.,1395356968,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gkasmmcbpikhl6gq6kg5,task_subcomment,NA
+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).",1386820754,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-gkasmmcbpikhl6gq6kg5,task_subcomment,NA
+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",1374334080,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-z7k6ld4qvfzn2ify7im6,task_description,resolved
+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.,1385391924,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z7k6ld4qvfzn2ify7im6,task_subcomment,NA
+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",1374306840,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-ltt3irfuuufns7tetoc3,task_description,resolved
+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 ***",1390416862,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ltt3irfuuufns7tetoc3,task_subcomment,NA
+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",1374285720,PHID-USER-3ampiwske4lc434cm6ot,PHID-TASK-ebhdb6qns6ottyytmzfa,task_description,resolved
+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",1374507519,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ebhdb6qns6ottyytmzfa,task_subcomment,NA
+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",1374506856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ebhdb6qns6ottyytmzfa,task_subcomment,NA
+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",1374267420,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-s4chuo432xmbozeyirll,task_description,resolved
+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 ***",1377833797,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s4chuo432xmbozeyirll,task_subcomment,NA
+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",1374229860,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-ydbji5fefbbeiocpl24u,task_description,resolved
+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.,1385392298,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ydbji5fefbbeiocpl24u,task_subcomment,NA
+VisualEditor: Rearranging transclusions breaks the ability to select parameters.,Also happens on Linux.,1374477983,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ydbji5fefbbeiocpl24u,task_subcomment,NA
+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"".",1374231992,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-ydbji5fefbbeiocpl24u,task_subcomment,NA
+"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",1374203640,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z2agxnwfy52lvo6yjxrd,task_description,resolved
+"VisualEditor: Relabel buttons in ""cancel editing"" confirmation dialog","Merging with bug 50955.
+
+*** This bug has been marked as a duplicate of bug 50955 ***",1374267909,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z2agxnwfy52lvo6yjxrd,task_subcomment,NA
+"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.",1374212616,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-z2agxnwfy52lvo6yjxrd,task_subcomment,NA
+"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",1374199860,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-3qhhrxr2wofxfssyycod,task_description,declined
+"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.,1385392053,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3qhhrxr2wofxfssyycod,task_subcomment,NA
+"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",1374162180,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-2maqvichtgrs77o35tls,task_description,resolved
+"VisualEditor: ""Leave Feedback"" link greyed out; might confuse users",This design was fixed some time ago but I forgot to tag this bug; sorry!,1385386362,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2maqvichtgrs77o35tls,task_subcomment,NA
+"""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",1374162000,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-pbxss6r2sg7qfrxykect,task_description,resolved
+"""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 ***",1374162111,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pbxss6r2sg7qfrxykect,task_subcomment,NA
+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",1374088140,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-tgo7euxf3cnwhcvmwsfs,task_description,resolved
+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 ***",1395354371,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tgo7euxf3cnwhcvmwsfs,task_subcomment,NA
+"VisualEditor: <nowiki> 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 <nowiki> tags around it (correct according to apparent design, incorrect according to desired behaviour). 
+
+However, it also added <nowiki> 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",1374081420,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rorj54kzrfz5yajplzy6,task_description,resolved
+"VisualEditor: <nowiki> 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.,1375199810,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rorj54kzrfz5yajplzy6,task_subcomment,NA
+"VisualEditor: <nowiki> 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.",1374081808,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rorj54kzrfz5yajplzy6,task_subcomment,NA
+"VisualEditor: <nowiki> tags added to all markup in paragraph, including pre-existing","Sorry, typo in that last line. It should refer to Bug 50569 comment 5",1374081645,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rorj54kzrfz5yajplzy6,task_subcomment,NA
+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",1374070440,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-lc76yoxati6qqmlqel6x,task_description,resolved
+Can't save,"
+
+%%%*** This bug has been marked as a duplicate of bug 50284 ***%%%",1374071458,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-lc76yoxati6qqmlqel6x,task_subcomment,NA
+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.",1374071358,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-lc76yoxati6qqmlqel6x,task_subcomment,NA
+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",1374065040,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-jo6lx3im2dnf4fgrh2cy,task_description,resolved
+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 ***",1374679397,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jo6lx3im2dnf4fgrh2cy,task_subcomment,NA
+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]]",1374678668,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jo6lx3im2dnf4fgrh2cy,task_subcomment,NA
+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",1374064500,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-nuhotkfh44rday75ra54,task_description,resolved
+VisualEditor: Tab key moves focus between citations; doesn't indent text as expected,"
+
+*** This bug has been marked as a duplicate of bug 48010 ***",1395359458,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nuhotkfh44rday75ra54,task_subcomment,NA
+"VisualEditor: Inserting whitespace in front of a paragraph shouldn't convert the paragraph to a preformatted block, but also shouldn't leave unneeded <nowiki>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",1374063600,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-tpc6ler6znj3xz2beohn,task_description,resolved
+"VisualEditor: Inserting whitespace in front of a paragraph shouldn't convert the paragraph to a preformatted block, but also shouldn't leave unneeded <nowiki>s",This was fixed in July; sorry for the slow triage.,1385386267,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tpc6ler6znj3xz2beohn,task_subcomment,NA
+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:
+<pre>
+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]#
+</pre>
+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",1374048060,PHID-USER-qrnoqj2szt6knvcqvaxt,PHID-TASK-eril5tvgiad53f3rcpft,task_description,declined
+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.",1374051736,PHID-USER-qrnoqj2szt6knvcqvaxt,PHID-TASK-eril5tvgiad53f3rcpft,task_subcomment,NA
+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.",1374048262,PHID-USER-qrnoqj2szt6knvcqvaxt,PHID-TASK-eril5tvgiad53f3rcpft,task_subcomment,NA
+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.",1374048167,PHID-USER-qrnoqj2szt6knvcqvaxt,PHID-TASK-eril5tvgiad53f3rcpft,task_subcomment,NA
+&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",1374012540,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-tlf237apfkoioeofs5ec,task_description,declined
+&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.",1382132925,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-tlf237apfkoioeofs5ec,task_subcomment,NA
+&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.",1382132880,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tlf237apfkoioeofs5ec,task_subcomment,NA
+&veaction= as a second parameter works on enwiki but not zhwiki,I cant reproduce this now.,1382132030,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-tlf237apfkoioeofs5ec,task_subcomment,NA
+"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",1373999220,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-djoqnd37pa6rtsa7b2iv,task_description,invalid
+"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.",1385374579,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-djoqnd37pa6rtsa7b2iv,task_subcomment,NA
+"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.",1380534380,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-djoqnd37pa6rtsa7b2iv,task_subcomment,NA
+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}",1373997420,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-w2eu52oilk4spsdpzeoa,task_description,resolved
+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 ***",1379788309,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-w2eu52oilk4spsdpzeoa,task_subcomment,NA
+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",1377775284,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-w2eu52oilk4spsdpzeoa,task_subcomment,NA
+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?),1377769124,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-w2eu52oilk4spsdpzeoa,task_subcomment,NA
+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",1373996400,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-d36xqpcmqmrkpqcgucpb,task_description,resolved
+VisualEditor: Category adding interface is hard to find,"
+
+*** This bug has been marked as a duplicate of bug 51153 ***",1374010099,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-d36xqpcmqmrkpqcgucpb,task_subcomment,NA
+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.",1374005371,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-d36xqpcmqmrkpqcgucpb,task_subcomment,NA
+"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",1373983800,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pskrxedevzwi6wzlhh27,task_description,declined
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'end' of null""",Provisionally closing as WORKSFORME.,1385386303,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pskrxedevzwi6wzlhh27,task_subcomment,NA
+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 <a>link</a>
+ Select link (has to be done manually (tedious and error prone) 
+ > Some [selection]<a>link</a>[/selection]""
+ Type ""hello"".
+ > Some <a>h</a>ello.
+
+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 ""<a>first char</a>other chars"" case.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48463",1373981640,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hqvxg56nlg2toykqmhmk,task_description,duplicate
+VisualEditor: Link inspector should make it easier to change the label,"
+
+*** This bug has been marked as a duplicate of bug 53973 ***",1395196870,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+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.",1391535731,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+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.",1378925410,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+VisualEditor: Link inspector should make it easier to change the label,I think this duplicates Bug 50945,1375181384,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+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.",1374009514,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+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}",1373959140,PHID-USER-34ciubbmtvmsgh53t6hb,PHID-TASK-rl6e4brnawmfpf74jcdj,task_description,resolved
+Syndicated feeds of Watchlists include non-existent edits,This seems fixed now for me.,1395065589,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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.",1383507823,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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...",1374562249,PHID-USER-34ciubbmtvmsgh53t6hb,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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)",1374557457,PHID-USER-34ciubbmtvmsgh53t6hb,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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:",1373960032,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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.",1373959528,PHID-USER-34ciubbmtvmsgh53t6hb,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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",1373950620,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-nkmn6tlxg6fzvqjixjiw,task_description,resolved
+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 ***",1377278955,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nkmn6tlxg6fzvqjixjiw,task_subcomment,NA
+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.",1377248899,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nkmn6tlxg6fzvqjixjiw,task_subcomment,NA
+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.",1377222218,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nkmn6tlxg6fzvqjixjiw,task_subcomment,NA
+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",1373937720,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-euerogqwtdmzt7fjkkmb,task_description,resolved
+Blanking last section of page corrupts heading,"
+
+%%%*** This bug has been marked as a duplicate of bug 50100 ***%%%",1373938090,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-euerogqwtdmzt7fjkkmb,task_subcomment,NA
+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",1373929020,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-h3r2wuw2m4pdrb5ixf7h,task_description,resolved
+color picker,"
+
+*** This bug has been marked as a duplicate of bug 52645 ***",1376120681,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h3r2wuw2m4pdrb5ixf7h,task_subcomment,NA
+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",1373917620,PHID-USER-dswbdv7ibhsefllcqarz,PHID-TASK-a465jbds23gplxffpkqu,task_description,resolved
+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 ***",1373926494,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-a465jbds23gplxffpkqu,task_subcomment,NA
+VisualEditor: spurious parentheses added,"See https://en.wikipedia.org/w/index.php?title=Wormshill&diff=564367057&oldid=557770558 for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373900400,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-nanbji3vohfklohczwir,task_description,declined
+VisualEditor: spurious parentheses added,"This is caused by an unbalanced <blockquote> 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.",1385386705,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nanbji3vohfklohczwir,task_subcomment,NA
+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",1373899320,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ipxn4a5xggbelogecqff,task_description,declined
+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.",1374456028,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ipxn4a5xggbelogecqff,task_subcomment,NA
+504 timeout with Parsoid service,See http://www.mediawiki.org/wiki/MediaWiki_on_IRC for information on IRC.,1373927829,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ipxn4a5xggbelogecqff,task_subcomment,NA
+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.,1373901602,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ipxn4a5xggbelogecqff,task_subcomment,NA
+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",1373895180,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-pi2tzunhpx5y7ayoea2g,task_description,resolved
+VisualEditor: Edit this Page button ignores &oldid=prev parameter.,This seems to now be fixed. Please re-open if you think I'm wrong!,1385387326,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pi2tzunhpx5y7ayoea2g,task_subcomment,NA
+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.",1374477548,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-pi2tzunhpx5y7ayoea2g,task_subcomment,NA
+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",1373886720,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-6syee5vbnlo6bygtishg,task_description,invalid
+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.",1378122078,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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 ?",1376729948,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+Add ULS language setting dialogue box in VisualEditor page settings,Mahitgar: Could you please answer comment 5?,1376399379,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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.",1374496050,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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?,1374494932,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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.,1374075062,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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}",1373969905,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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.",1373893663,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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",1373885880,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-avk6xwxd7jsix4gwqxoe,task_description,resolved
+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 ***",1373968970,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-avk6xwxd7jsix4gwqxoe,task_subcomment,NA
+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}",1373956157,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-avk6xwxd7jsix4gwqxoe,task_subcomment,NA
+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.",1373893817,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-avk6xwxd7jsix4gwqxoe,task_subcomment,NA
+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",1373878680,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-6vh7i45cbz7znphxlsf6,task_description,resolved
+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 ***",1373932279,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6vh7i45cbz7znphxlsf6,task_subcomment,NA
+VisualEditor: Automatically add title of the section to edit summary,"**ignatzmice.wiki** wrote:
+
+I agree with Michael, this would be very useful.",1373891958,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6vh7i45cbz7znphxlsf6,task_subcomment,NA
+"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}",1373871600,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vlaiyo2akniolmqe5tq6,task_description,resolved
+"VisualEditor: double-clicking ""create reference"" generates a quasi-broken ref form.",This has been fixed since July; sorry for slow update.,1385383559,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vlaiyo2akniolmqe5tq6,task_subcomment,NA
+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",1373869620,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-aljzsqmks2kf5dymrk45,task_description,resolved
+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.,1385383181,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aljzsqmks2kf5dymrk45,task_subcomment,NA
+VisualEditor: Applying a transclusion that only contains content brackets breaks the edit toolbar.,*** Bug 51437 has been marked as a duplicate of this bug. ***,1374545947,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-aljzsqmks2kf5dymrk45,task_subcomment,NA
+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",1373847540,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-favvfitkxvyu4vmy3ump,task_description,resolved
+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.,1385384432,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-favvfitkxvyu4vmy3ump,task_subcomment,NA
+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",1373780340,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-fldsdjwnv5jvqc2iam55,task_description,duplicate
+Allow wikitext e.g. links to documentation in templatedata,"
+
+*** This bug has been marked as a duplicate of bug 50656 ***",1375191068,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fldsdjwnv5jvqc2iam55,task_subcomment,NA
+Allow wikitext e.g. links to documentation in templatedata,*** Bug 50656 has been marked as a duplicate of this bug. ***,1375187353,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-fldsdjwnv5jvqc2iam55,task_subcomment,NA
+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 <code> tag to all better distinguishing of '' (two apostrophes for italic markup) and "" (double quote) by rendering them in a monospace font.",1373787877,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fldsdjwnv5jvqc2iam55,task_subcomment,NA
+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",1373700600,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ykvbtj26wyleuw4bnbjh,task_description,resolved
+VisualEditor: External link missing in template due to linkname with ampersand in it,confirmed,1385420773,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ykvbtj26wyleuw4bnbjh,task_subcomment,NA
+VisualEditor: External link missing in template due to linkname with ampersand in it,I think this has been subsequently fixed - can you confirm?,1385386971,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ykvbtj26wyleuw4bnbjh,task_subcomment,NA
+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",1373649540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-de6dmorszoddddclnd4y,task_description,invalid
+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",1373652658,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-de6dmorszoddddclnd4y,task_subcomment,NA
+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",1373652398,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-de6dmorszoddddclnd4y,task_subcomment,NA
+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",1373645640,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-yz6cpenppcreusg72zvt,task_description,resolved
+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 <meta typeof=""mw:Placeholder"" data-parsoid=""…""> 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 ***",1373646127,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yz6cpenppcreusg72zvt,task_subcomment,NA
+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",1373645936,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-yz6cpenppcreusg72zvt,task_subcomment,NA
+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",1373610900,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-hrdmmz7wdsz3xmnhvpp2,task_description,resolved
+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 ***",1374459959,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-hrdmmz7wdsz3xmnhvpp2,task_subcomment,NA
+VisualEditor: Cut and Pasting a section that contains an image truncates all the sections formatting after pasting it.,Confirming your example.,1374459355,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-hrdmmz7wdsz3xmnhvpp2,task_subcomment,NA
+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,1373883205,PHID-USER-lumvg23bxmfbvekr2fbo,PHID-TASK-hrdmmz7wdsz3xmnhvpp2,task_subcomment,NA
+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",1373577600,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-jakyw4q5ktlmqgd4sv3v,task_description,declined
+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.",1373599184,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jakyw4q5ktlmqgd4sv3v,task_subcomment,NA
+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,1373577841,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jakyw4q5ktlmqgd4sv3v,task_subcomment,NA
+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.
+<br>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",1373569320,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-mruibaiz5kt46pzezn7l,task_description,resolved
+Template rearranging itself,This was the Parsoid complex templates / VisualEditor dirtying edits bug that got fixed months ago; sorry for the very slow triage.,1390416930,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mruibaiz5kt46pzezn7l,task_subcomment,NA
+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",1373566080,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-mgnru2nwxtufpuc6lqyx,task_description,resolved
+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 ***",1385382810,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mgnru2nwxtufpuc6lqyx,task_subcomment,NA
+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,1373568433,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-mgnru2nwxtufpuc6lqyx,task_subcomment,NA
+"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",1373562300,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-hn23baiwxuaicjnc3ue4,task_description,resolved
+"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.,1385380627,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hn23baiwxuaicjnc3ue4,task_subcomment,NA
+"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",1373555340,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-umxktvxo76lzoeghwqxz,task_description,resolved
+"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","**kwwilliams** wrote:
+
+It's 51150.",1374272928,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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",1374272740,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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.",1374272519,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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 ***",1374271260,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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.,1374270992,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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 ***%%%",1374270889,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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.",1374270607,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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).",1374252996,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+<nowiki/> 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",1373553780,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-htn2o6dmt6ze2hhaf537,task_description,invalid
+<nowiki/> added to wikilinks,"If the user selects ""diesel generator"" (i.e., misses the 's'), the resultant HTML would be
+
+  <a href=foo>diesel generator</a>s 
+
+The correct wikitext version of this is indeed
+
+  [[diesel generator]]<nowiki />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.",1373567309,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-htn2o6dmt6ze2hhaf537,task_subcomment,NA
+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",1373546700,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_description,resolved
+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 ***",1374079614,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_subcomment,NA
+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).",1373548204,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_subcomment,NA
+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.",1373547099,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_subcomment,NA
+VisualEditor: blanking an article and starting from scratch causes malformations,"Screenshot
+
+**Attached**: {F11062}",1373546784,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_subcomment,NA
+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",1373538900,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gonbe6svndpp6xg5nn7w,task_description,resolved
+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 ***",1377527402,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gonbe6svndpp6xg5nn7w,task_subcomment,NA
+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.,1374487773,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gonbe6svndpp6xg5nn7w,task_subcomment,NA
+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).",1373578518,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gonbe6svndpp6xg5nn7w,task_subcomment,NA
+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",1373509140,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-maorft5oyfrh3mtkgplv,task_description,duplicate
+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.",1385386774,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-maorft5oyfrh3mtkgplv,task_subcomment,NA
+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.",1374229995,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-maorft5oyfrh3mtkgplv,task_subcomment,NA
+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?",1374010319,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-maorft5oyfrh3mtkgplv,task_subcomment,NA
+VisualEditor: Category interface is hard to find,*** Bug 51452 has been marked as a duplicate of this bug. ***,1374010099,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-maorft5oyfrh3mtkgplv,task_subcomment,NA
+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",1373485620,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-zt2vp3ws2fthuoczhtcs,task_description,declined
+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.,1397677941,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zt2vp3ws2fthuoczhtcs,task_subcomment,NA
+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)",1377444558,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-zt2vp3ws2fthuoczhtcs,task_subcomment,NA
+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,<ref>[null http:///www.icmacabre.blogspot.com]</ref>
+
+----
+
+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",1373484720,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-zvpdqkuywxev3x3oy6sk,task_description,resolved
+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.",1385382685,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvpdqkuywxev3x3oy6sk,task_subcomment,NA
+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",1373481780,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-fc6sg7pcqin3kmtv4x57,task_description,resolved
+VisualEditor: Removing template & Adding content breaks editor,"Bug 51340 is essentially the same issue, and both are now fixed I believe.",1385387104,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fc6sg7pcqin3kmtv4x57,task_subcomment,NA
+"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",1373479140,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bypr3rbgyguddodinker,task_description,resolved
+"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 ***",1373480869,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bypr3rbgyguddodinker,task_subcomment,NA
+"VisualEditor: Review changes should show the edit summary, if one has been provided.",I think this duplicates bug 42139,1373479854,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bypr3rbgyguddodinker,task_subcomment,NA
+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",1373474880,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_description,duplicate
+Transcluded pages quasi-template eats into subsequent entry,Opened Parsoid bug 53368 for the issues described in comment #12 above.,1377549211,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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 <ul> 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.",1377219256,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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.",1377216081,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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.",1376663796,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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).",1376663213,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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.",1376662900,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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?",1376661657,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+Transcluded pages quasi-template eats into subsequent entry,*** Bug 52814 has been marked as a duplicate of this bug. ***,1376639350,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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.,1376620889,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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 <ul> 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.",1376618254,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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')
+;
+```",1432542616,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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')
+;
+```",1432542425,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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')
+;",1374649444,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+Transcluded pages quasi-template eats into subsequent entry,"Relevant wikitext excerpt:
+
+| {{:Christian Delius}}
+| <!-- Änderungen bitte dort vornehmen, siehe unterhalb des Bearbeitungsfensters -->
+| * [[Christina Rau]], geb. Delius (* 1956), deutsche Politologin
+
+Yeah, this is because the HTML comment and <li> in the wikitext below the template insert themselves into the implicit <ul> 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).",1374645296,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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",1374539843,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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",1373450100,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rzacfnoggbzshwb2qnc6,task_description,resolved
+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 ***",1373480408,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rzacfnoggbzshwb2qnc6,task_subcomment,NA
+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",1373430900,PHID-USER-kc6qx3zohjybu3nzffu3,PHID-TASK-cj43kd2u4kzkuq6rlhnu,task_description,invalid
+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 <div>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.",1373724208,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cj43kd2u4kzkuq6rlhnu,task_subcomment,NA
+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.",1373693982,PHID-USER-kc6qx3zohjybu3nzffu3,PHID-TASK-cj43kd2u4kzkuq6rlhnu,task_subcomment,NA
+Editing adds JavaScript,"From a quick Google, this is a faulty browser plugin of some kind, FoxLingoJs.",1373521024,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cj43kd2u4kzkuq6rlhnu,task_subcomment,NA
+"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}",1373411220,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4lztgmjyrotthez4ft5,task_description,resolved
+"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 ***",1373411601,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4lztgmjyrotthez4ft5,task_subcomment,NA
+Adding a {{cn}} template causes VisualEditor to silently add <nowiki>..</nowiki> 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 <nowiki> issues on bugzilla
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373406240,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eedu2jxaz76eztsst6ep,task_description,invalid
+Adding a {{cn}} template causes VisualEditor to silently add <nowiki>..</nowiki> 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.",1373409131,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eedu2jxaz76eztsst6ep,task_subcomment,NA
+Adding a {{cn}} template causes VisualEditor to silently add <nowiki>..</nowiki> 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.",1373406615,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eedu2jxaz76eztsst6ep,task_subcomment,NA
+VisualEditor: Link input field identifiers in DOM are bogus,"corrupt <class> identifier in DOM for Link
+
+see screenshot
+
+what is this ""class""?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11753}",1373398680,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-dhjt3sejejdufp3ya2co,task_description,invalid
+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.",1375221769,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-dhjt3sejejdufp3ya2co,task_subcomment,NA
+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",1373395500,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-weyb3zctidhjrppnilwj,task_description,resolved
+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 ***",1385381556,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-weyb3zctidhjrppnilwj,task_subcomment,NA
+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!",1373401725,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-weyb3zctidhjrppnilwj,task_subcomment,NA
+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",1373392500,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-2j6ctllml6qqxhzmqlmr,task_description,resolved
+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 ***",1394501875,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2j6ctllml6qqxhzmqlmr,task_subcomment,NA
+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]]",1379885198,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-2j6ctllml6qqxhzmqlmr,task_subcomment,NA
+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",1377447358,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-2j6ctllml6qqxhzmqlmr,task_subcomment,NA
+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}",1373385480,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6uqz7k3i6hhy6r5mf4qh,task_description,resolved
+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 ***",1385381652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6uqz7k3i6hhy6r5mf4qh,task_subcomment,NA
+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",1373365380,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_description,resolved
+VisualEditor: adding spaces?,"This seems to be bug 48570
+
+*** This bug has been marked as a duplicate of bug 48570 ***",1379455266,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+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.",1379007082,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+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.",1374254808,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+VisualEditor: adding spaces?,Talking about spaces: https://en.wikipedia.org/w/index.php?title=Genie_%28feral_child%29&diff=564429158&oldid=564425048,1374227956,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+VisualEditor: adding spaces?,"Same thing here after ""équipes"": http://fr.wikipedia.org/w/index.php?title=Mafia_%28jeu%29&diff=94892395&oldid=91395852",1373626132,PHID-USER-mapumhlp3gw5qefhvafn,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+"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",1373361000,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-karzxpqg6fmjzovu77r7,task_description,resolved
+"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 ***",1373504485,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-karzxpqg6fmjzovu77r7,task_subcomment,NA
+"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.",1373364187,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-karzxpqg6fmjzovu77r7,task_subcomment,NA
+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",1373359380,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-3ngsdaq55c6cqyub75es,task_description,resolved
+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.",1383004078,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ngsdaq55c6cqyub75es,task_subcomment,NA
+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,1375808870,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-3ngsdaq55c6cqyub75es,task_subcomment,NA
+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.",1375121749,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-3ngsdaq55c6cqyub75es,task_subcomment,NA
+VisualEditor: Template dialog crushing parameters together and nowiking links,"Some broken browser extension sometimes adds lots of  <a class=""ktg6us78hf8vdu7"" href=""javascript:void(0)"">...</a> 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 <a class=""ktg6us78hf8vdu7"" href=""javascript:void(0)""><a class=""ktg6us78hf8vdu7"" href=""javascript:void(0)"">video</a></a> gaming|1990]]
+| products       = [[Crash Bandicoot|''Crash Bandicoot'' series]] (2002-2004) (2013- )<br>[[Skylanders|''Skylanders'' series]] (2011-2013)0)"">Guitar</a></a> Hero|''Guitar Hero'' series]] (2007–2010) 
+...
+}}
+
+Into
+{{Infobox company
+|<nowiki>1990]]</nowiki>
+|''Guitar Hero''<nowiki> series]] (2007–2010) </nowiki>
+...
+| foundation     = <nowiki>[[1990 in video gaming</nowiki>
+| products       = [[Crash Bandicoot|''Crash Bandicoot'' series]] (2002-2004) (2013- )<br>[[Skylanders|''Skylanders'' series]] (2011-2013) Guitar Hero
+...
+}}
+splitting the foundation and product parameters.",1373361466,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-3ngsdaq55c6cqyub75es,task_subcomment,NA
+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",1373330760,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-yvxmfw4svpxfoy2mq3xe,task_description,resolved
+VisualEditor: Template highlight is sometimes misplaced in the reference inspector,"
+
+*** This bug has been marked as a duplicate of bug 50913 ***",1373351191,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-yvxmfw4svpxfoy2mq3xe,task_subcomment,NA
+"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",1373324220,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-atyu2v5fwwehteymmmkf,task_description,duplicate
+"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 ***",1373472822,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-atyu2v5fwwehteymmmkf,task_subcomment,NA
+"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)",See also gerrit change 70564.,1373469016,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-atyu2v5fwwehteymmmkf,task_subcomment,NA
+"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/",1373325997,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-atyu2v5fwwehteymmmkf,task_subcomment,NA
+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",1373316060,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_description,resolved
+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 ***",1377831826,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+Selecting text does not work,Selecting text works at the page you provided but drag and drop does not work.,1373317925,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+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",1373317893,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+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 <translate> tags, it must be disabled on these pages. Thank you.",1373317502,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+Selecting text does not work,"It seems related to the <translate> tag, try it on another page like https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet",1373316358,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+Selecting text does not work,"As selecting text is a basic operation, bumping to a major issue.",1373316165,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+Selecting text does not work,FF 22,1373316086,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+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",1373315640,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-ovg5r2xmn4fehf7ofjhg,task_description,declined
+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.",1373363951,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-ovg5r2xmn4fehf7ofjhg,task_subcomment,NA
+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.",1373363212,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ovg5r2xmn4fehf7ofjhg,task_subcomment,NA
+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",1373314500,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-bhshtaaxwx36iiznlkm2,task_description,resolved
+Redlinks show up as bluelinks in VisualEditor mode,"
+
+*** This bug has been marked as a duplicate of bug 37901 ***",1373353929,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bhshtaaxwx36iiznlkm2,task_subcomment,NA
+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",1373297700,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-b3kpqkztod52q3bqpgcc,task_description,resolved
+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 ***",1373851066,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b3kpqkztod52q3bqpgcc,task_subcomment,NA
+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",1373241540,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-754mi2navz4pvonnspxh,task_description,declined
+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.",1385381445,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-754mi2navz4pvonnspxh,task_subcomment,NA
+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}",1373233920,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-njvhn6axgtv4xkldtkx2,task_description,resolved
+VisualEditor: Template editor turns links into [[link|name]] in CE,"
+
+*** This bug has been marked as a duplicate of bug 50801 ***",1373354186,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-njvhn6axgtv4xkldtkx2,task_subcomment,NA
+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",1373233620,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ovfsitu3qtht2esmfi2s,task_description,resolved
+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 ***",1375717235,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ovfsitu3qtht2esmfi2s,task_subcomment,NA
+VisualEditor: The anchor for the template editor can easily become invisible,Is this the same as bug 49922?,1374487466,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ovfsitu3qtht2esmfi2s,task_subcomment,NA
+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",1373232480,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-qrgadp2mt3qhvw2auoa4,task_description,resolved
+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 ***",1377814666,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qrgadp2mt3qhvw2auoa4,task_subcomment,NA
+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.",1373232552,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-qrgadp2mt3qhvw2auoa4,task_subcomment,NA
+Nested <nowiki>s considered harmful,"Sometimes Parsoid will wrap a <nowiki> around an existing <nowiki>; 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",1373055060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_description,resolved
+Nested <nowiki>s considered harmful,*** Bug 50724 has been marked as a duplicate of this bug. ***,1373637242,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+Nested <nowiki>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",1373473754,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+Nested <nowiki>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",1373470917,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+Nested <nowiki>s considered harmful,"Change 72230 merged by jenkins-bot:
+(Bug 50835) Dont nowiki escape already escaped template params
+
+https://gerrit.wikimedia.org/r/72230",1373307265,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+Nested <nowiki>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",1373065523,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+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",1373053920,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-wob6rhplaqtaaqqwjmgd,task_description,resolved
+VisualEditor: edits fail on hitting the abuse filter (with a cryptic error message),"
+
+*** This bug has been marked as a duplicate of bug 50472 ***",1373054299,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-wob6rhplaqtaaqqwjmgd,task_subcomment,NA
+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",1373048100,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-gqozvzrj5ka3lgyouwvn,task_description,resolved
+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 ***",1373077734,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqozvzrj5ka3lgyouwvn,task_subcomment,NA
+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",1373026620,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_description,declined
+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 ""<p><br>"".
+
+Closing as worksforme. Please open a bug against VE if you have trouble with focusing or deleting the <br>.",1376618868,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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 <br> and so shown in VisualEditor as a ""↵"" and can be removed in-line.)",1373854399,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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",1373145121,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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.",1373102850,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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 ***",1373046915,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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",1372966680,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-6yatmdhnokanuospfimc,task_description,resolved
+VisualEditor: VE's determination of image size should hook into user preferences,Related to bug 47804 too.,1372967030,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-6yatmdhnokanuospfimc,task_subcomment,NA
+VisualEditor: VE's determination of image size should hook into user preferences,"
+
+*** This bug has been marked as a duplicate of bug 50379 ***",1372966971,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-6yatmdhnokanuospfimc,task_subcomment,NA
+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",1372954140,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-rlgq63dcwusayyjqcpor,task_description,invalid
+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. :-)",1372956245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rlgq63dcwusayyjqcpor,task_subcomment,NA
+"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",1372942020,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-5oldmu57nfk4gdllhb7z,task_description,declined
+"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.",1383280851,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5oldmu57nfk4gdllhb7z,task_subcomment,NA
+"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. :)",1372949758,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5oldmu57nfk4gdllhb7z,task_subcomment,NA
+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",1372937460,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-qrcwbd4n7nqvsvfbykcb,task_description,resolved
+VisualEditor: Template inspector's parameter display causes smushing,"
+
+%%%*** This bug has been marked as a duplicate of bug 50728 ***%%%",1372937527,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-qrcwbd4n7nqvsvfbykcb,task_subcomment,NA
+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",1372937340,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ltzaf5hgb6yn3qi7gdwt,task_description,resolved
+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 ***",1373556875,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ltzaf5hgb6yn3qi7gdwt,task_subcomment,NA
+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.",1373556265,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-ltzaf5hgb6yn3qi7gdwt,task_subcomment,NA
+<nowiki> added to existing <nowiki> 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 <nowiki> tags around existing <nowiki> content (in this case the ""|"" symbol in the title of a cited website) inside a template inside a reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372923600,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-w3w62aq46ybywp76vzom,task_description,resolved
+<nowiki> added to existing <nowiki> content,"
+
+*** This bug has been marked as a duplicate of bug 50835 ***",1373637242,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w3w62aq46ybywp76vzom,task_subcomment,NA
+<nowiki> added to existing <nowiki> content,"Other example:
+http://en.wikipedia.org/w/index.php?title=Beximco&diff=562685500&oldid=562676888",1372955926,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-w3w62aq46ybywp76vzom,task_subcomment,NA
+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",1372897260,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-xjgn5e55ct4mrwoaox2n,task_description,resolved
+VisualEditor: alt text?,"
+
+*** This bug has been marked as a duplicate of bug 38129 ***",1372900959,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xjgn5e55ct4mrwoaox2n,task_subcomment,NA
+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",1372875720,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-q6dmhbtud5dlan7xkm5f,task_description,resolved
+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.",1376511764,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-q6dmhbtud5dlan7xkm5f,task_subcomment,NA
+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.",1374460614,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-q6dmhbtud5dlan7xkm5f,task_subcomment,NA
+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",1372869900,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-ygke3aatutel76h64y5d,task_description,resolved
+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.,1385378094,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ygke3aatutel76h64y5d,task_subcomment,NA
+VisualEditor: Inherited category becomes explicitly invoked,Another example: https://fr.wikipedia.org/w/index.php?diff=94601807,1374255950,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-ygke3aatutel76h64y5d,task_subcomment,NA
+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",1372847760,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6tpy6ex557ljdilowdac,task_description,invalid
+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.)",1372853500,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+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.,1372853464,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+Section 0 (lede) editing does not offer VisualEditor,Can someone point me to the code that is building the VE edit section links ?,1372853398,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+Section 0 (lede) editing does not offer VisualEditor,"**wikipedia** wrote:
+
+Forwarded to:
+
+  http://en.wikipedia.org/wiki/User_talk:TheDJ#edittop.js:_VisualEditor",1372848588,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+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.",1372848358,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+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.",1372848234,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+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",1372842180,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gpv7ztvo3m727pmopcq7,task_description,resolved
+VisualEditor: image resizing causing implosion,"[17:29] <Excirial> 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] <Technical_13> Resolved fixed?
+[17:30] <Technical_13> !b 50651
+[17:30] <wm-bot> https://bugzilla.wikimedia.org/50651
+[17:30] <Excirial> Yes, confirmed that the problem no longer occurs.
+[17:30] <Technical_13> Kk",1373578420,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-gpv7ztvo3m727pmopcq7,task_subcomment,NA
+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 <https://test.wikipedia.org> momentarily.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1372833600,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-zr2hewhivqrgrbnvcapd,task_description,resolved
+Unify post-edit notifications on Wikimedia wikis,"**swalling** wrote:
+
+The current plan is to convert VE to use the same notification style as Extension:PostEdit previously did, now that it's been fully migrated to core (bug 48276)
+
+%%%*** This bug has been marked as a duplicate of bug 39632 ***%%%",1372834231,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zr2hewhivqrgrbnvcapd,task_subcomment,NA
+Unify post-edit notifications on Wikimedia wikis,"Created attachment 12739
+Post-edit notification using wikitext (source) editor on test.wikipedia.org
+
+**Attached**: {F11760}",1372833795,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-zr2hewhivqrgrbnvcapd,task_subcomment,NA
+Unify post-edit notifications on Wikimedia wikis,"Created attachment 12738
+Post-edit notification using VisualEditor on test.wikipedia.org, 2013-07-03
+
+**Attached**: {F11759}",1372833765,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-zr2hewhivqrgrbnvcapd,task_subcomment,NA
+VisualEditor: Still dirty refs?,"There seem to be several dirty ref sections in this diff:
+
+https://en.wikipedia.org/w/index.php?title=God_of_War_%28series%29&diff=prev&oldid=562631132
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372827600,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-odieilz34gnzoz67vumw,task_description,resolved
+VisualEditor: Still dirty refs?,"
+
+*** This bug has been marked as a duplicate of bug 48570 ***",1379613746,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-odieilz34gnzoz67vumw,task_subcomment,NA
+VisualEditor: Transclusion dialog does not handle missing parameter name,"To reproduce
+
+1. Click puzzle piece
+2. Type cn ([[Template:cn]] redirecting to [[Template:Citation needed]])
+3. Press enter twice.
+
+(I was experimenting see if there is a quick way to get out of the template dialog; this would be useful for templates like Template:cn that are commonly added without parameters).
+
+4. Type 'foo'
+5. Click 'Apply changes'
+6. It shows 'Template:Fooifsubst'
+7. Code is generated as '{{Cn| = foo}'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372810140,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-u7bebesywdz3nbtymuyr,task_description,resolved
+VisualEditor: Transclusion dialog does not handle missing parameter name,This was fixed quite some time ago; many apologies for being so slow to reply.,1385375541,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u7bebesywdz3nbtymuyr,task_subcomment,NA
+VisualEditor: Transclusion dialog does not handle missing parameter name,"Upon re-opening it, though, it shows part_0/.",1372811272,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-u7bebesywdz3nbtymuyr,task_subcomment,NA
+VisualEditor: Transclusion dialog does not handle missing parameter name,I forgot to add: It shows part_1/ on the left where the parameter names go.,1372810279,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-u7bebesywdz3nbtymuyr,task_subcomment,NA
+"VisualEditor ""leave BETA"" dialogue jumps around, making leave hard/impossible","**Author:** `wikipedia`
+
+**Description:**
+To reproduce:
+
+1. http://en.wikipedia.org/wiki/High_Speed_2?veaction=edit&vesection=6
+2. Wait, hopefully the VisualEditor loads, and does not hang
+3. Click ""BETA""
+4. Click Leave.
+5. Try to type in this dialogue box
+
+What happens:
+
+6. The window scrolls around with each and every keypress.
+7. The Leave BETA dialogue is very hard to complete.
+
+What should happen:
+
+6. The window should not scroll
+7. The process of leaving should be easy and reliable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372794540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3nmcqmdcnvrslmvnpgyx,task_description,resolved
+"VisualEditor ""leave BETA"" dialogue jumps around, making leave hard/impossible","Sorry about this bug; we fixed it a few days ago and deployed it to the servers - merging with that report.
+
+*** This bug has been marked as a duplicate of bug 50538 ***",1373152861,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3nmcqmdcnvrslmvnpgyx,task_subcomment,NA
+"VisualEditor ""leave BETA"" dialogue jumps around, making leave hard/impossible","**wikipedia** wrote:
+
+Video of VisualEditor jumping around while typing in Leave dialogue.
+
+Third attempt at video attachment of issue (failed on creation).  Truncated with 'dd if=visual-editor-madness.ogv of=visual-editor-madness-10240kB.ogv bs=1k count=9999'
+
+**Attached**: {F11691}",1372795186,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3nmcqmdcnvrslmvnpgyx,task_subcomment,NA
+Editing sections one at a time results in editing old revisions,"When editing a section with VisualEditor the page loads and saves just fine.  However, if you next edit a different section *without refreshing the page*, VisualEditor does not recognize the version of the page you just saved as what you are editing and loads the last revision and warns you that you are editing an old revision.  This occurs in Chrome and Firefox using Windows 7 as I've tested it.
+
+From https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Editing_section_results_in_dirty_page_cache_--_have_to_reload_page_before_doing_additional_edits
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372788540,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-nptn4dym6znmjhge2meh,task_description,resolved
+Editing sections one at a time results in editing old revisions,"This is a really irritating bug, yes; sorry about this - merging with the wider report at bug 50441.
+
+*** This bug has been marked as a duplicate of bug 50441 ***",1373155391,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nptn4dym6znmjhge2meh,task_subcomment,NA
+Editing sections one at a time results in editing old revisions,"New editors are likely to edit a page, save it, have an afterthought, see this message, and panic. It just keeps on happening: experienced editors know the work-round (hit ""refresh"").
+
+Until the problem is fixed, could the error message in that pink box be amended to include ""Please click ""Cancel"" to close the editor, then reload/refresh the page, then try again. We apologise for this temporary problem and are working on a solution.""?",1372922278,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-nptn4dym6znmjhge2meh,task_subcomment,NA
+Editing sections one at a time results in editing old revisions,"It's not just after section editing: see many reports on feedback page. I edit a page in VE, save page, have an afterthought, reopen in VE, get told it's an old revision. Then cancel VE, refresh page, reopen VE, no problem. But shouldn't need to do that refresh.",1372840608,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-nptn4dym6znmjhge2meh,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?","Not sure if this is possible, but a user raises concerns about the behavior of VE opening the whole page for editing instead of editing specific sections, given that it increases the load time.
+
+See:
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562566677#edit_one_section_only
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372783680,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-3mzdvk7doccla2cgipwj,task_description,resolved
+"Can ""edit section"" be restricted to only open the single section?","Looks like it, yes!
+
+%%%*** This bug has been marked as a duplicate of bug 48429 ***%%%",1372793232,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?",Is this a dupe of bug 48429?,1372791768,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?","It also means that more bandwidth is consumed than the user asked for, which could be a problem in some cases (particularly on slow connections).
+
+On busy pages it is likely to lead to more edit conflicts, due to increased load times and encouragement to edit multiple sections.",1372791083,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?","Note that this constitutes the interface basically lying about what it's going to do, hence its disconcerting nature.",1372789295,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?","**wikipedia** wrote:
+
+To reproduce:
+
+1. Visit a page, eg. http://en.wikipedia.org/wiki/High_Speed_2#Legal_challenges
+2. Hover over the section ""[ edit ]""
+3. Expands to ""[ edit | edit source ]"" (both with equivalent URLs)
+4. Observe that the link is: http://en.wikipedia.org/wiki/High_Speed_2?veaction=edit&vesection=6
+5. Click the link.
+
+What happens:
+
+6. The page jumps
+7. The page freezes
+8. The page is partially whited-out
+9. (If it happens to complete loading).  A massive toolbar obscures where the cursor was.
+
+What should happen:
+
+6. The page should remain exactly where it was, it should not move
+7. The page should remain interactive
+8. The page should remain readable
+9. The editor (visual or textedit) should correspond to only that section.",1372784238,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+VisualEditor: warn on markup.,"Similar to bugs 50093 and 50527; users need to be warned when they're using markup in the VE. This is a source of a pretty large amount of corruption on enwiki, and I'm not sure how sustainable the community's patience for that is.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372768500,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k3ijb4t7vtqm2fvl7dqa,task_description,resolved
+VisualEditor: warn on markup.,"
+
+%%%*** This bug has been marked as a duplicate of bug 49820 ***%%%",1372859187,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k3ijb4t7vtqm2fvl7dqa,task_subcomment,NA
+VisualEditor: warn on markup.,I strongly advise that this be made pretty high-priority (See above).,1372782236,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k3ijb4t7vtqm2fvl7dqa,task_subcomment,NA
+Infobox template shows HTML,"**Author:** `warnckew`
+
+**Description:**
+Screenshot showing infobox DIV HTML code
+
+Launching VisualEditor to edit http://en.wikipedia.org/w/index.php?title=United_Nations_Security_Council_Resolution_1693&oldid=541044487 makes the heading of the infobox show some unexpected HTML contents, as shown in the attached browser screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11621}",1372759800,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-u4b7k3vc55d23eoi7lfv,task_description,resolved
+Infobox template shows HTML,"This is the same as bug 50366 - merging with that one.
+
+*** This bug has been marked as a duplicate of bug 50366 ***",1372781074,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u4b7k3vc55d23eoi7lfv,task_subcomment,NA
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,"I have noticed an unexpected behavior while tesing Visual Editor with Malayalam Wikipedia. Describing the steps below:-
+
+1. Added the following text on a page
+
+ഡിസ്രയേലി
+
+2. When pressing a backspace immediately after the above text, it becomes
+
+ഡസരയ
+
+ie. many characters in between the original text disappeared. The expected result was ഡിസ്രയേ
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows 7
+**Platform**: PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50507",1372759140,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_description,declined
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,Now the problem has been solved. You may mark this bug as resolved.,1374044144,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,"(In reply to comment #1)
+> @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",1373267447,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+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.",1373135312,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,Browser was Firefox 22.,1373134659,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,@vssun: Any specific browser? Can't reproduce it in Chrome.,1373134158,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+"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",1372746900,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-zu3q7ugqbcdtlalzbdir,task_description,resolved
+"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 ***",1372747009,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zu3q7ugqbcdtlalzbdir,task_subcomment,NA
+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",1372741440,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-c67owxdoizewmtq2qqq2,task_description,resolved
+VisualEditor: Likely round-trip failure involving categories and transclusion content on [[Michala Petri]],"
+
+*** This bug has been marked as a duplicate of bug 50120 ***",1373484208,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-c67owxdoizewmtq2qqq2,task_subcomment,NA
+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",1372742420,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-c67owxdoizewmtq2qqq2,task_subcomment,NA
+"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",1372740840,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-xzt7v3b2ore2q4iogeui,task_description,resolved
+"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.,1374878989,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xzt7v3b2ore2q4iogeui,task_subcomment,NA
+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",1372737300,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-i5l4tj3jbqlfjjgj2xtx,task_description,resolved
+VisualEditor: Likely ref / transclusion round-trip failure,Fixed in Roan's DOM dirtying fixes drive in July.,1385375352,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i5l4tj3jbqlfjjgj2xtx,task_subcomment,NA
+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?",1373928755,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-i5l4tj3jbqlfjjgj2xtx,task_subcomment,NA
+VisualEditor: Likely ref / transclusion round-trip failure,Only difference is the removal of two spaces after equals signs.,1373894262,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-i5l4tj3jbqlfjjgj2xtx,task_subcomment,NA
+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",1372723860,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5jyjadx572ehzjtstm2i,task_description,resolved
+VisualEditor: Feedback form moves and jerks the screen around,*** Bug 50533 has been marked as a duplicate of this bug. ***,1385375230,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+VisualEditor: Feedback form moves and jerks the screen around,*** Bug 50602 has been marked as a duplicate of this bug. ***,1373152861,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+VisualEditor: Feedback form moves and jerks the screen around,Sorry about this bug; we've fixed this and just deployed it live.,1372894536,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+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",1372890609,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+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",1372874494,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+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.",1372834749,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+VisualEditor: Feedback form moves and jerks the screen around,This sounds really unhelpful; sorry about this.,1372726074,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+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 <input> 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",1372716720,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-gm7mlj7ylnonhtpcmhmc,task_description,resolved
+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",1375115733,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gm7mlj7ylnonhtpcmhmc,task_subcomment,NA
+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",1373190428,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gm7mlj7ylnonhtpcmhmc,task_subcomment,NA
+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';",1373020498,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-gm7mlj7ylnonhtpcmhmc,task_subcomment,NA
+Tagging articles using old markup on VE,"I note that if an editor uses old markup in VE (like [[link]]), it gets enclosed in <nowiki> 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",1372715580,PHID-USER-65pjzcmoby2fsgzdrfjq,PHID-TASK-tndk34qrdqsecj3chsun,task_description,declined
+Tagging articles using old markup on VE,"**nykevin.norris** wrote:
+
+Removing self from CC.  Tired of spam.  Bug is dead, people.",1375295445,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375295294,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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!",1375293668,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375290243,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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?",1375287296,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375286688,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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).",1375259183,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375257056,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.""",1375214654,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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 <nowiki> 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.",1375209327,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375203199,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+Tagging articles using old markup on VE,"(In reply to comment #10)
+> (In reply to comment #7)
+> > Adding a <nowiki> 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? :-)",1375203157,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+Tagging articles using old markup on VE,"**kwwilliams** wrote:
+
+(In reply to comment #7)
+> Adding a <nowiki> 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.",1375202701,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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 <nowiki> 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...",1375202572,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375202406,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+Tagging articles using old markup on VE,"**nykevin.norris** wrote:
+
+Adding a <nowiki> 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.",1375201973,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375201659,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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 <nowiki> 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.",1375200134,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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",1373826928,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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",1373475389,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1372941268,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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",1372870715,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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",1372714740,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-i6cv3vliogwuderqbjnw,task_description,invalid
+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.",1374878756,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i6cv3vliogwuderqbjnw,task_subcomment,NA
+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.,1372714830,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i6cv3vliogwuderqbjnw,task_subcomment,NA
+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",1372712700,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-y2smkmxkc74umzi22ziq,task_description,resolved
+Ghost references in VisualEditor?,"Yes, same issue as bug 50380.
+
+*** This bug has been marked as a duplicate of bug 50380 ***",1385375005,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y2smkmxkc74umzi22ziq,task_subcomment,NA
+Ghost references in VisualEditor?,"I cant reproduce this using the example given.
+
+It looks like this may be a dup of bug 50380.",1373758575,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-y2smkmxkc74umzi22ziq,task_subcomment,NA
+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",1372711380,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-devcsvnwd5brcea5luka,task_description,resolved
+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 ***",1374079583,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-devcsvnwd5brcea5luka,task_subcomment,NA
+VisualEditor: Deleting all content removes input marker,Is this the same as Bug 50947 and/or Bug 51169?,1374077413,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-devcsvnwd5brcea5luka,task_subcomment,NA
+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",1372699740,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-p2n3tks426uods6v37cf,task_description,declined
+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.,1373996005,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-p2n3tks426uods6v37cf,task_subcomment,NA
+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}",1372613820,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-wf4a2uikjvfox37upsq3,task_description,declined
+VisualEditor: thick line appearing,"Created attachment 13766
+No thick line
+
+**Attached**: {F11386}",1384204317,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wf4a2uikjvfox37upsq3,task_subcomment,NA
+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.",1384204280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wf4a2uikjvfox37upsq3,task_subcomment,NA
+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}",1372613700,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yaappft5pc7quebc2sf7,task_description,resolved
+VisualEditor: Text wrongly being given pre-formatted format,Fixed for some time due to changes in Parsoid. Sorry for the slowness of updating.,1385374964,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yaappft5pc7quebc2sf7,task_subcomment,NA
+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",1372612740,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-4i77geu65qzvj7wexwob,task_description,resolved
+VisualEditor: Links created in the userspace are treated as links to subpages,"
+
+*** This bug has been marked as a duplicate of bug 48915 ***",1377445192,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4i77geu65qzvj7wexwob,task_subcomment,NA
+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",1372608360,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-my7qaki5z5rpjdhjrelx,task_description,resolved
+VisualEditor: Error saving data to server: Failed request: error.,"Performance issue, fixed some time ago; sorry for slowness in replying.",1385375109,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-my7qaki5z5rpjdhjrelx,task_subcomment,NA
+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",1372757474,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-my7qaki5z5rpjdhjrelx,task_subcomment,NA
+"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",1372595400,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-tb4dfoj5ivzds3d5vjbf,task_description,resolved
+"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 ***",1373852659,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tb4dfoj5ivzds3d5vjbf,task_subcomment,NA
+"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)",1373239841,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-tb4dfoj5ivzds3d5vjbf,task_subcomment,NA
+"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)",1372978408,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-tb4dfoj5ivzds3d5vjbf,task_subcomment,NA
+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}",1372595100,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-adbbasada34enlaaq6ns,task_description,resolved
+VisualEditor: Insert media dialog is borked,"
+
+*** This bug has been marked as a duplicate of bug 50471 ***",1372620610,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-adbbasada34enlaaq6ns,task_subcomment,NA
+"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 (&#124; -> <nowiki>|</nowiki>) in a section of the page I didn't edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372548840,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-qzi73sz5voocgvogf6kk,task_description,resolved
+"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…,1385380712,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qzi73sz5voocgvogf6kk,task_subcomment,NA
+Preserve wiki link href with ././ prefix,"The following HTML does not seem to properly round-trip through VE:
+
+<p><a rel=""mw:WikiLink"" href=""././Foo"">./Foo</a></p>
+
+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",1372526940,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-q22fxzgily436ad4iq5g,task_description,declined
+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",1372920044,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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.,1372887258,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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.",1372882310,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+Preserve wiki link href with ././ prefix,"It worked at http://en.wikipedia.org/wiki/User:Catrope/Shrek?veaction=edit though, so closing as working.",1372880388,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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",1372821570,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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",1372527319,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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",1372513920,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-mystbxhb36nxyv6pxcfr,task_description,resolved
+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 ***",1373407947,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mystbxhb36nxyv6pxcfr,task_subcomment,NA
+Feature request: permit copy-paste of templates from history,"I believe Maggie means copying the VisualEditor representation of a template, not copying wikitext.",1373407882,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-mystbxhb36nxyv6pxcfr,task_subcomment,NA
+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 <nowiki> 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.",1372805568,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-mystbxhb36nxyv6pxcfr,task_subcomment,NA
+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",1372507500,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-dwm6neygnm5atdz5p2ls,task_description,resolved
+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.",1384945237,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dwm6neygnm5atdz5p2ls,task_subcomment,NA
+VisualEditor: Backspace from header line into empty paragraph changes header format into paragraph,"Sorry: I should have said ""Backspace"", not ""Delete"".",1372508092,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-dwm6neygnm5atdz5p2ls,task_subcomment,NA
+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 <anonymous function: ve.copyDomElements>(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 <anonymous function: ve.copyDomElements>(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 <anonymous function: ve.ce.GeneratedContentNode.prototype.onUpdate>() 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 <anonymous function: ve.Factory.prototype.create>(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 <anonymous function: ve.ce.BranchNode.prototype.onSplice>(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 [<span...>, <dl...>] on Firefox. Since `index` is not undefined, this would indicate some sort of an internal inconsistency.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372507500,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_description,resolved
+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",1372556851,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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",1372510944,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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.,1372509962,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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.",1372509277,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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.",1372508815,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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.",1372508473,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+"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",1372498200,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jp6ugl4t75zwxp4yb5dw,task_description,resolved
+"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 ***",1372500786,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-jp6ugl4t75zwxp4yb5dw,task_subcomment,NA
+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",1372436400,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-fxdptzpzjvmxdqfbxpig,task_description,resolved
+VisualEditor: massively duplicating references on render,*** Bug 50521 has been marked as a duplicate of this bug. ***,1385375005,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fxdptzpzjvmxdqfbxpig,task_subcomment,NA
+VisualEditor: massively duplicating references on render,Fixed a few months ago; sorry for late reply.,1383410182,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fxdptzpzjvmxdqfbxpig,task_subcomment,NA
+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)",1373758524,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-fxdptzpzjvmxdqfbxpig,task_subcomment,NA
+"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}",1372416960,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-rlct7v5aitn3wet7l6e6,task_description,resolved
+"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 ***",1372417299,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-rlct7v5aitn3wet7l6e6,task_subcomment,NA
+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}",1372414740,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-cbgrzxh5jpcsxgl5p5xy,task_description,resolved
+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 ***",1372690696,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cbgrzxh5jpcsxgl5p5xy,task_subcomment,NA
+"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",1372414500,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-smzjavkfcebgjqkdtqrx,task_description,resolved
+"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 ***",1373663953,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-smzjavkfcebgjqkdtqrx,task_subcomment,NA
+"VisualEditor: Can't drag and drop transclusions, text, references","While for text there's 49981 open, itwp users also request this for templates.",1373663530,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-smzjavkfcebgjqkdtqrx,task_subcomment,NA
+VisualEditor throws <nowiki> 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 <nowiki> tags like this:
+
+<nowiki>[Square brackets]</nowiki>
+
+<nowiki>[...]</nowiki>
+
+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 <nowiki> tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T54268}",1372374900,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-trv3cartgmv24xouxumz,task_description,resolved
+VisualEditor throws <nowiki> 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.",1372777003,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-trv3cartgmv24xouxumz,task_subcomment,NA
+VisualEditor throws <nowiki> 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.",1372756630,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-trv3cartgmv24xouxumz,task_subcomment,NA
+VisualEditor throws <nowiki> 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.",1372748767,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-trv3cartgmv24xouxumz,task_subcomment,NA
+VisualEditor throws <nowiki> 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.,1372744432,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-trv3cartgmv24xouxumz,task_subcomment,NA
+VisualEditor: Cutting the text of a header leaves a blank header line behind,"Fairly self-explanatory.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372359060,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-lorkde4zqpoazowbiim6,task_description,resolved
+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 ***",1373154763,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lorkde4zqpoazowbiim6,task_subcomment,NA
+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?",1372853616,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-lorkde4zqpoazowbiim6,task_subcomment,NA
+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",1372358460,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ymkat6i32jrdnouhpmiw,task_description,invalid
+VisualEditor: edit link on the history page needs updating,"How very strange. Slightly slower loading time giving a false impression, probably; thanks :).",1372364368,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ymkat6i32jrdnouhpmiw,task_subcomment,NA
+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. :-)",1372364187,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ymkat6i32jrdnouhpmiw,task_subcomment,NA
+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}",1372348860,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-vthqyhkr4mcwanonthu2,task_description,resolved
+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}",1373854867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vthqyhkr4mcwanonthu2,task_subcomment,NA
+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}",1372346160,PHID-USER-az3b22hiqzlaov5l2efk,PHID-TASK-mfexrt4v3gjwo4jczoeu,task_description,resolved
+ULS doesn't work while using VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 49569 ***",1372351064,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-mfexrt4v3gjwo4jczoeu,task_subcomment,NA
+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",1372344540,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bklb3mjjhzmtwofxaf4c,task_description,resolved
+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 ***",1373852602,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bklb3mjjhzmtwofxaf4c,task_subcomment,NA
+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 <ref>Jones (2003) p.23</ref> 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",1372337880,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-3b3ojih2e7wkq7l3upwi,task_description,resolved
+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 ***",1373851094,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3b3ojih2e7wkq7l3upwi,task_subcomment,NA
+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",1372331040,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-o7g3xrsatafdlookojvh,task_description,resolved
+VisualEditor: Page settings dialog adds categories with [[:Category:xyz]] syntax,"This was a Parsoid bug, since fixed.",1372435698,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-o7g3xrsatafdlookojvh,task_subcomment,NA
+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}",1372329960,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-6a4gkdcnicitblhp6cug,task_description,resolved
+VisualEditor: Toolbar obscures save dialog when scrolled down the page,"
+
+*** This bug has been marked as a duplicate of bug 50324 ***",1372387036,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-6a4gkdcnicitblhp6cug,task_subcomment,NA
+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",1372301820,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mgc6io5oxbkpzoctvybg,task_description,resolved
+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 ***",1373520752,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mgc6io5oxbkpzoctvybg,task_subcomment,NA
+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",1372280520,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-ytqjgzoe2nidan525q6p,task_description,resolved
+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 ***",1372284454,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ytqjgzoe2nidan525q6p,task_subcomment,NA
+Unwanted Removal of text formatting,Duplicated here: http://test.wikipedia.org/w/index.php?title=VisualEditor%3ATestingGrounds&diff=174932&oldid=174931,1372283768,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-ytqjgzoe2nidan525q6p,task_subcomment,NA
+'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",1372269540,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-44radwd6pkgnkplpyiul,task_description,invalid
+'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.",1372270000,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-44radwd6pkgnkplpyiul,task_subcomment,NA
+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",1372269480,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-th6xciyktmum2yvdvsqy,task_description,declined
+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?",1404150917,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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.",1383053606,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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.",1378387791,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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)?",1378357656,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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.",1378356625,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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.",1378356406,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+screen doesn't work from within 'become',"According to <https://wiki.toolserver.org/view/Multi-maintainer_projects#Using_screen>, 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?",1378355120,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+screen doesn't work from within 'become',"Then you almost certainly* remember incorrectly.  Screen can only operate on the terminal you are connected to (obviously), and that is necessarily owned by the user you have logged in with.
+
+Chances are this scenario (start a screen session /after/ having switched to another user) would have been less common on toolserver since most people ran only as their login user except for the infrequent multi-maintainer project -- which all projects are in Tool Labs.
+
+* (I say almost here because it /is/ possible to set screen suid to root; but that's on the same list as ""chmod 777 your home"", ""set your password to '1234'"", or ""allow telnet"" -- something a user might find convenient but a sysadmin should be fired for).",1378354665,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+screen doesn't work from within 'become',"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
+Cannot open your terminal '/dev/pts/50' - please check.
+
+I kept getting this. I checked <https://wikitech.wikimedia.org/wiki/Screen> 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.",1378349685,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+screen doesn't work from within 'become',"That's a limitation on how screen functions (i.e., it needs to have ownership of the terminal, which only the actual login process grants); sudo cannot circumvent this as it does not alter tty permissions.
+
+While it's a little annoying, the workaround you describe provides full functionality during interactive sessions (and it bears reminding here that tools should not be running interactive processes in detached screen sessions in any case).",1372269706,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+VisualEditor: Dialogs won't open after adding a template at the end of the page,"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.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372263600,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-alyz2tg2s4hlxhbv3yqa,task_description,resolved
+VisualEditor: Dialogs won't open after adding a template at the end of the page,"(In reply to comment #1)
+> (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 ***",1372271165,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-alyz2tg2s4hlxhbv3yqa,task_subcomment,NA
+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.",1372269533,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-alyz2tg2s4hlxhbv3yqa,task_subcomment,NA
+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",1372252500,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bcsg2progke55h2rhst6,task_description,resolved
+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.",1372864641,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bcsg2progke55h2rhst6,task_subcomment,NA
+VisualEditor not working due to unflushed ResourceLoader cache?,I assume this is obsolete now?,1372846999,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bcsg2progke55h2rhst6,task_subcomment,NA
+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.)",1372266477,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bcsg2progke55h2rhst6,task_subcomment,NA
+VisualEditor: Extra bullet point before template containing bulleted list,"VE rendering of [[WUEC#External_links]] does not match MW rendering.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372230840,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-7ma6pcpqiiyq3gvijprg,task_description,invalid
+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).",1372295480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7ma6pcpqiiyq3gvijprg,task_subcomment,NA
+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}",1372228380,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-sgceljbbtlgbbpr3bdfh,task_description,resolved
+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 ***",1373164008,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sgceljbbtlgbbpr3bdfh,task_subcomment,NA
+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}",1372227660,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-z2wr7yxi5vylreuzml56,task_description,resolved
+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.",1373163131,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z2wr7yxi5vylreuzml56,task_subcomment,NA
+VisualEditor: Image size parameter with spaces is ignored,"See [[testwiki:VisualEditor:Little or big]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372216200,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-6xivramwe724jwphgukh,task_description,resolved
+VisualEditor: Image size parameter with spaces is ignored,"
+
+*** This bug has been marked as a duplicate of bug 49696 ***",1372216311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6xivramwe724jwphgukh,task_subcomment,NA
+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",1372206060,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-q3v5q4q6bifjgxghffaq,task_description,resolved
+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 |
++---------------------+----------+",1374273514,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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.",1374090128,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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"";",1373589867,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+Logging broken for GettingStarted (page-save-success logged as page-impression),*** Bug 51208 has been marked as a duplicate of this bug. ***,1373589755,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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.",1372823275,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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",1372822882,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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",1372740115,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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].",1372739582,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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.",1372275305,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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. ;)",1372268511,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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.",1372208974,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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",1372172160,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-txtftm3ohgrpjqzazgnp,task_description,resolved
+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 ***",1373162765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-txtftm3ohgrpjqzazgnp,task_subcomment,NA
+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",1372159200,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-yllnjqjrkuliux5dxtws,task_description,resolved
+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 ***",1373162663,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yllnjqjrkuliux5dxtws,task_subcomment,NA
+"<nowiki> tags added to (valid) list in a template parameter, corrupting them","In general,
+
+{{foo
+bar = 
+* 1
+* 2
+* 3
+}}
+
+… is RT'ing to 
+
+{{foo
+bar = <nowiki>* 1
+* 2
+* 3</nowiki>
+}}
+
+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",1372125540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bfsjo6ol2jmfu3gdf4ch,task_description,resolved
+"<nowiki> tags added to (valid) list in a template parameter, corrupting them","
+
+*** This bug has been marked as a duplicate of bug 50144 ***",1372127067,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bfsjo6ol2jmfu3gdf4ch,task_subcomment,NA
+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",1372121400,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-tn6apoz6stp2eozgwscp,task_description,resolved
+Missing root git config file when cloning,[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.],1378939564,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tn6apoz6stp2eozgwscp,task_subcomment,NA
+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.",1373095093,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-tn6apoz6stp2eozgwscp,task_subcomment,NA
+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",1372480935,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tn6apoz6stp2eozgwscp,task_subcomment,NA
+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.",1372474317,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-tn6apoz6stp2eozgwscp,task_subcomment,NA
+"Images: Frameless images should not emit the ""caption"" as a <figcaption> 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 <figcaption> 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 <figcaption>s for these as part of bug 50113, but Parsoid should fix these in due course.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372119780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dyhspvuz6dvlmjei7r7v,task_description,invalid
+"Images: Frameless images should not emit the ""caption"" as a <figcaption> 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],1372934057,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyhspvuz6dvlmjei7r7v,task_subcomment,NA
+"Images: Frameless images should not emit the ""caption"" as a <figcaption> even when it's set",This is by design. See http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images for documentation and rationales.,1372121678,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dyhspvuz6dvlmjei7r7v,task_subcomment,NA
+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",1372095840,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dgi4ucdvhwjzbauoa7td,task_description,resolved
+VisualEditor adding spurious pipe separators to image syntax,"
+
+*** This bug has been marked as a duplicate of bug 50012 ***",1372096490,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dgi4ucdvhwjzbauoa7td,task_subcomment,NA
+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.",1372095892,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dgi4ucdvhwjzbauoa7td,task_subcomment,NA
+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<ref>{{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}}</ref>
+
+to...
+
+* Winner, Magenta Foundation award<ref>{{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}}</ref>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372088640,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_description,invalid
+VisualEditor template parameter normalization results in dirty diffs,"Closing ""bugs"" which consist of multiple issues.",1373163467,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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,1372107875,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Ivan_Tan&curid=39767321&diff=561408770&oldid=561406619,1372104798,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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.",1372104345,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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",1372104272,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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,1372102659,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Kamelot&curid=1161493&diff=561402036&oldid=560661945,1372102018,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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 ***",1372101714,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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,1372100288,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Dan_Penteado&curid=13006822&diff=561396894&oldid=561392351,1372099355,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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,1372099302,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=MTV&curid=18856&diff=561395466&oldid=561389102,1372098643,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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",1372098386,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Wild_Pack&curid=29143457&diff=561394555&oldid=561394449,1372098360,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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",1372096583,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,"
+
+*** This bug has been marked as a duplicate of bug 50066 ***",1372091701,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor ref weirdness,"https://en.wikipedia.org/w/index.php?title=Laura_Pannack&diff=561336738&oldid=557984097
+
+<ref name=""telegraph""/> --> <ref name=""telegraph""></ref>
+
+Weird.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372088340,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jvpgelxqydhjqfkhkgas,task_description,resolved
+VisualEditor ref weirdness,https://en.wikipedia.org/w/index.php?title=Save_Rock_and_Roll&curid=38419944&diff=561416388&oldid=561387755,1372107851,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jvpgelxqydhjqfkhkgas,task_subcomment,NA
+VisualEditor ref weirdness,https://en.wikipedia.org/w/index.php?title=Daniel_Kahneman&curid=165492&diff=561411461&oldid=560179630,1372106999,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jvpgelxqydhjqfkhkgas,task_subcomment,NA
+VisualEditor ref weirdness,"
+
+*** This bug has been marked as a duplicate of bug 50066 ***",1372091672,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jvpgelxqydhjqfkhkgas,task_subcomment,NA
+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",1372086060,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dmz6g3cracqeyd3hxrar,task_description,invalid
+VisualEditor spurious attribute normalization (resulting in dirty diffs),"Closing ""bugs"" which consist of multiple issues.",1373163469,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dmz6g3cracqeyd3hxrar,task_subcomment,NA
+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",1372097247,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dmz6g3cracqeyd3hxrar,task_subcomment,NA
+VisualEditor spurious attribute normalization (resulting in dirty diffs),"
+
+*** This bug has been marked as a duplicate of bug 50066 ***",1372091521,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dmz6g3cracqeyd3hxrar,task_subcomment,NA
+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",1372085520,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-4c7jfgdvdgsa7tz3aom4,task_description,resolved
+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 ***",1372091385,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4c7jfgdvdgsa7tz3aom4,task_subcomment,NA
+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<len;
+        i++){
+
+I tried to get a better output using debug=true, but this seems to totally break VE (in IE10 at least).
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F11482}",1372059000,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-efd5wnljemqy75ubgwoi,task_description,resolved
+VisualEditor: Impossible to review or save changes in IE10,"This is bug 49187 (and yes, it's critical, hence we've re-blacklisted IE until we can get this fixed). :-(
+
+(IE has a hard limit on how many scripts it will take for a given page; debug=true suspends ResourceLoader, meaning all ~200 VE files come individually - along with the dozens of non-VE MW scripts - which IE ignores after the first ten or so, breaking everything. This is a known IE-is-terrible bug.)
+
+*** This bug has been marked as a duplicate of bug 49187 ***",1372084871,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-efd5wnljemqy75ubgwoi,task_subcomment,NA
+VisualEditor: Impossible to review or save changes in IE10,It's also impossible to save the page; same script error occurs. Upping to critical.,1372059463,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-efd5wnljemqy75ubgwoi,task_subcomment,NA
+VisualEditor: still making unrelated modifications,"See https://en.wikipedia.org/w/index.php?title=Royal_Lancaster_Infirmary&diff=561254127&oldid=560972172 for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372037520,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jazdgxdcnzvf2vvkoqay,task_description,resolved
+VisualEditor: still making unrelated modifications,This is still happening: https://en.wikipedia.org/w/index.php?title=Genie_%28feral_child%29&diff=564429158&oldid=564425048 Can you please check? Thanks.,1373984013,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jazdgxdcnzvf2vvkoqay,task_subcomment,NA
+VisualEditor: still making unrelated modifications,"This particular one is (entirely cryptically) bug 50066, which is going to be fixed in the next few minutes and deployed tomorrow morning PDT.
+
+*** This bug has been marked as a duplicate of bug 50066 ***",1372039230,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jazdgxdcnzvf2vvkoqay,task_subcomment,NA
+"VisualEditor: ""read"" version after save page not picking up on category removals","If a user hits edit, removes a category and saves, the read-only article they're then presented with still includes the old category - or at least, does on https://en.wikipedia.org/wiki/Sumali
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372034880,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ndrderb5cpy5obe7r7so,task_description,resolved
+"VisualEditor: ""read"" version after save page not picking up on category removals","
+
+*** This bug has been marked as a duplicate of bug 48560 ***",1372036218,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ndrderb5cpy5obe7r7so,task_subcomment,NA
+VisualEditor saves HTML instead of wikitext,"In the following edit, VE saved the internal page representation instead of the wikitext:
+
+https://nl.wikipedia.org/w/index.php?title=Eurosong&diff=prev&oldid=38007082
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371986640,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-2nhg6abdnwgx5uutzfus,task_description,resolved
+VisualEditor saves HTML instead of wikitext,"This was due to the caches being mis-configured; really sorry about this issue.
+
+*** This bug has been marked as a duplicate of bug 49577 ***",1372004983,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2nhg6abdnwgx5uutzfus,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,"When viewing [[testwiki:Visualeditor_image_captions]] in VE, the images cannot be seen. They are still ""known"" though - they don't vanish on save.
+
+(My testing of this issue led to the filing of bug 50008, but the issue there seems to have gone away now. However, this one is still showing up for me, so I think this is a separate bug.
+
+Please close this bug if it turns out to have fixed itself.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371972060,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-k4lzd6fndz3snhg24las,task_description,resolved
+Images turned into mw:Placeholder in certain cases,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934068,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,"
+
+*** This bug has been marked as a duplicate of bug 48900 ***",1372104211,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,Related: Bug 48900,1372006246,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,*** Bug 50008 has been marked as a duplicate of this bug. ***,1372003922,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,"This is because Parsoid is converting the images to placeholders for some reason: http://parsoid.wmflabs.org/mw/User:Catrope/Bug_50035
+
+Moving to Parsoid",1371972510,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Jenkins: Provide build status images,"Assuming we do not yet have something like this, it'd be awesome if this Jenkins plugin could be installed:
+
+https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin
+
+I want to be able to embed such a build status image on some website.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1371912840,PHID-USER-mye6umixnhfo7lhpgzmj,PHID-TASK-fa3dg2ag3ccgjplogzop,task_description,resolved
+Jenkins: Provide build status images,"I have installed the plugin and restarted Jenkins. Please try it out, if it does not work simply reopen this bug :)",1372235730,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-fa3dg2ag3ccgjplogzop,task_subcomment,NA
+Jenkins: Provide build status images,"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:
+
+
+Configured Pipeline Manager postmerge
+Events:
+  <EventFilter types: change-merged>
+Projects:
+  mediawiki/extensions/VisualEditor
+    <Job mwext-VisualEditor-doc-publish> ^master$
+  operations/mediawiki-config
+    <Job beta-mediawiki-config-update> ^master$ 
+  test/mediawiki
+    <Job test-mediawiki-docgen>
+  analytics/wikistats
+    <Job analytics-wikistats>
+  analytics/udp-filters
+    <Job analytics-udp-filters>
+  operations/puppet
+    <Job operations-puppet-doc>
+  analytics/webstatscollector
+    <Job analytics-webstatscollector>
+  analytics/libanon
+    <Job analytics-libanon>
+  mediawiki/extensions/Parsoid
+    <Job parsoid-regressions>
+  mediawiki/core
+    <Job mediawiki-core-jslint> (?!REL1_19)^(\.jshint|.*\.(js|json)$)
+    <Job mediawiki-core-lint>
+    <Job mediawiki-core-jsduck-publish> ^(REL1_21|master)$^.*\.(js|json)$
+    <Job mediawiki-core-regression-master> ^master$
+    <Job mediawiki-core-regression-REL1_19> ^REL1_19$
+    <Job mediawiki-core-regression-REL1_20> ^REL1_20$
+    <Job mediawiki-core-regression-REL1_21> ^REL1_21
+    <Job mediawiki-core-regression-phpcs-HEAD>
+    <Job mediawiki-core-doxygen-publish>   
+  mediawiki/extensions/Math
+    <Job beta-recompile-math-texvc>
+  integration/docroot
+    <Job integration-docroot-deploy> ^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.",1372012020,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-fa3dg2ag3ccgjplogzop,task_subcomment,NA
+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.",1371986909,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fa3dg2ag3ccgjplogzop,task_subcomment,NA
+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.",1371986368,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fa3dg2ag3ccgjplogzop,task_subcomment,NA
+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",1371911220,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-ljxem5cmodalpwa72kg4,task_description,invalid
+Parametr adds =,"But anyway, thx for explanation and sorry for disturbing!",1373174465,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-ljxem5cmodalpwa72kg4,task_subcomment,NA
+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""?",1373174438,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-ljxem5cmodalpwa72kg4,task_subcomment,NA
+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 (<visualeditor-parameter-input-placeholder>) 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. :-(",1373161574,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ljxem5cmodalpwa72kg4,task_subcomment,NA
+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",1371898920,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-wvgg7vhdge7chox3fyjo,task_description,resolved
+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 ***",1371969869,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wvgg7vhdge7chox3fyjo,task_subcomment,NA
+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",1371855780,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-c3wbsdob4ioii2vvg62w,task_description,resolved
+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 ***",1371855868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c3wbsdob4ioii2vvg62w,task_subcomment,NA
+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",1371854820,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-7ahnfikr3ud3nwuglytr,task_description,resolved
+VisualEditor: Insecure image links on https,"
+
+*** This bug has been marked as a duplicate of bug 43015 ***",1371855005,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7ahnfikr3ud3nwuglytr,task_subcomment,NA
+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}",1371825480,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-wzimuyoyzpmwzhvmicic,task_description,invalid
+VisualEditor: not functioning on it.wiki,"Cool; marking as resolved. I'd suggest speaking to the QE author quickfast, then :D.",1371828173,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-wzimuyoyzpmwzhvmicic,task_subcomment,NA
+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",1371827387,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wzimuyoyzpmwzhvmicic,task_subcomment,NA
+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.",1371825766,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wzimuyoyzpmwzhvmicic,task_subcomment,NA
+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",1371805320,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-btez3p46ypsfjdbg3yny,task_description,resolved
+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 ***",1371827708,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-btez3p46ypsfjdbg3yny,task_subcomment,NA
+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",1371798000,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-gd5v26ccraeduoxxlbju,task_description,resolved
+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],1372934049,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gd5v26ccraeduoxxlbju,task_subcomment,NA
+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 ***",1371829646,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gd5v26ccraeduoxxlbju,task_subcomment,NA
+VisualEditor translates templates into Uzbek language,Looks like a Parsoid caching issue: bug 49411 again?,1371812835,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-gd5v26ccraeduoxxlbju,task_subcomment,NA
+"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}",1371771480,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pfavb4dwppjl5cul5xfr,task_description,resolved
+"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 ***",1371771658,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-pfavb4dwppjl5cul5xfr,task_subcomment,NA
+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",1371748800,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_description,resolved
+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],1372933999,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_subcomment,NA
+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 ***",1371769152,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_subcomment,NA
+Parsoid: full sized images are displayed regardless of a |pictured parameter,"Aha,",1371751846,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_subcomment,NA
+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.",1371751628,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_subcomment,NA
+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",1371738780,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-gt3d3w3roul5snkreii4,task_description,resolved
+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 ***",1371774369,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gt3d3w3roul5snkreii4,task_subcomment,NA
+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",1371654120,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-cttjkncimnkmzpg2rgta,task_description,resolved
+Existing image inclusions are duplicated and truncated by VisualEditor,"This is 49729.
+
+*** This bug has been marked as a duplicate of bug 49729 ***",1371721408,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cttjkncimnkmzpg2rgta,task_subcomment,NA
+Existing image inclusions are duplicated and truncated by VisualEditor,"(sorry, just saw the first edit.)",1371659331,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cttjkncimnkmzpg2rgta,task_subcomment,NA
+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,1371659142,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cttjkncimnkmzpg2rgta,task_subcomment,NA
+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",1371645900,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-u5v4rso2epl4jpiezw4u,task_description,resolved
+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],1372934053,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-u5v4rso2epl4jpiezw4u,task_subcomment,NA
+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 ***",1371660571,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u5v4rso2epl4jpiezw4u,task_subcomment,NA
+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",1371633600,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-b7f2axjx5q6kogc6seqp,task_description,declined
+VisualEditor: IE8 support,Great! Thanks.,1371658981,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+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)",1371658853,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+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"".",1371657906,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+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.",1371656351,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+VisualEditor: IE8 support,That's an en_INTERNET idiom. Do you want me to sic the internationalisation team on you? Cuz I will.,1371650531,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+VisualEditor: IE8 support,Kill it with fire!,1371650457,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+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",1371612300,PHID-USER-ixwg3kf22idjy7x4ncxf,PHID-TASK-2mi7knu2wbwwklhttype,task_description,resolved
+VisualEditor: Insert media create link to undefined,"Same thing?
+
+*** This bug has been marked as a duplicate of bug 49596 ***",1371627753,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-2mi7knu2wbwwklhttype,task_subcomment,NA
+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}",1371584640,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-54g2ow3ld3vtvnaijiwz,task_description,resolved
+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 ***",1373155495,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-54g2ow3ld3vtvnaijiwz,task_subcomment,NA
+"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",1371574560,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-kybodyavmyonstmof6sr,task_description,resolved
+"VisualEditor: VE providing unasked-for removal of ""duplicate"" formatting","
+
+%%%*** This bug has been marked as a duplicate of bug 49755 ***%%%",1371574643,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-kybodyavmyonstmof6sr,task_subcomment,NA
+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|<nowiki>foo=bar</nowiki>|baz}}. However, ""foo=bar"" and ""<nowiki>foo=bar</nowiki>"" 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",1371545100,PHID-USER-rjtk3h6l2quifuajiime,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_description,resolved
+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",1373416635,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_subcomment,NA
+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",1373415473,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_subcomment,NA
+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<nowiki>=</nowiki>foo}}.",1373403587,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_subcomment,NA
+Parsoid uses nowiki tags for positional template parameters with '='s rather than just explicitly declaring them,See also bug 49743.,1371552288,PHID-USER-rjtk3h6l2quifuajiime,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_subcomment,NA
+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}",1371532800,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-xfgiug37am4goz3ewbs4,task_description,resolved
+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 ***",1372015399,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xfgiug37am4goz3ewbs4,task_subcomment,NA
+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",1371524400,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-gpu6rhupzadk44q3zvmd,task_description,declined
+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.",1371527182,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gpu6rhupzadk44q3zvmd,task_subcomment,NA
+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...",1371525193,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-gpu6rhupzadk44q3zvmd,task_subcomment,NA
+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).",1371524702,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gpu6rhupzadk44q3zvmd,task_subcomment,NA
+VisualEditor: Possible to insert empty DEFAULTSORT,"Go to <https://test.wikipedia.org/wiki/IPod?veaction=edit>.
+
+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",1371514380,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-fz5qvkff7hb32uaxnpl7,task_description,resolved
+VisualEditor: Possible to insert empty DEFAULTSORT,Merged and will be deployed very soon.,1371845552,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fz5qvkff7hb32uaxnpl7,task_subcomment,NA
+VisualEditor: Possible to insert empty DEFAULTSORT,Related URL: https://gerrit.wikimedia.org/r/69850 (Gerrit Change Ie3caaf4811f87911444462f83d511c0cc46c0716),1371811734,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fz5qvkff7hb32uaxnpl7,task_subcomment,NA
+Special:Contributions lists spurious AFT entries and takes 20 more seconds to load,"The URL was served for me in 22.766 s and contain spurious entries (without visualeditor tag) like
+    21:47, 17 June 2013 . . (0)‎ . . Feedback: Wikipedia:File Upload Wizard . . DenakiPanos70 (talk) 
+
+This practically equivalent search was served in 1.645 s: <https://en.wikipedia.org/w/index.php?limit=500&tagfilter=visualeditor&title=Special%3AContributions&contribs=newbie&target=&namespace=8&nsInvert=1&tagfilter=visualeditor&year=2013&month=-1>
+
+--------------------------
+**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",1371500220,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-uubavjgv7r236ouenxi3,task_description,resolved
+Special:Contributions lists spurious AFT entries and takes 20 more seconds to load,Merged.,1371566599,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-uubavjgv7r236ouenxi3,task_subcomment,NA
+Special:Contributions lists spurious AFT entries and takes 20 more seconds to load,https://gerrit.wikimedia.org/r/#/c/69152/ & https://gerrit.wikimedia.org/r/#/c/69153/ should fix this.,1371549103,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-uubavjgv7r236ouenxi3,task_subcomment,NA
+Can not create references on some pages,"**Author:** `rachelqa99`
+
+**Description:**
+On this page, we cannot create a reference:   https://www.mediawiki.org/wiki/User:Cmcmahon%28WMF%29/references_bug
+
+We can create a reference on this page: https://www.mediawiki.org/wiki/User:Rachel99/VisualEditor_Feature_Test_Charter/refs_demo
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371490500,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_description,invalid
+Can not create references on some pages,"Chris, it's possible that we accidentally fixed the bug? We updated to master yesterday afternoon, though I don't think we were doing anything in this area.",1371572897,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_subcomment,NA
+Can not create references on some pages,"This seems to have been an anomaly. A strange anomaly because Rachel and I both were unable to create a reference on this page.  Upon clicking ""Apply changes"" in the Reference UI, nothing at all appeared on the page. Now it does.",1371570816,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_subcomment,NA
+Can not create references on some pages,Maybe you want bug 45132.,1371524288,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_subcomment,NA
+Can not create references on some pages,Works for me: https://www.mediawiki.org/w/index.php?title=User:Cmcmahon(WMF)/references_bug&diff=712793&oldid=712613 . Am I missing something?,1371524221,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_subcomment,NA
+Edit with VisualEditor duplicates content with subst'd version of the content,"A user reported this edit
+<https://pt.wikipedia.org/w/index.php?title=CMM_-_Canal_Meninos_e_Meninas&diff=36129698&oldid=36129686>, 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",1371485940,PHID-USER-vyidforzdhnrsoweujao,PHID-TASK-amav3irppf34v275xo4q,task_description,resolved
+Edit with VisualEditor duplicates content with subst'd version of the content,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934032,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-amav3irppf34v275xo4q,task_subcomment,NA
+Edit with VisualEditor duplicates content with subst'd version of the content,"This is now fixed in production - really sorry about this bug. If it happens again, please re-open this.",1371515540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-amav3irppf34v275xo4q,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> 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",1371470220,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-xbihpnurfxbt3vghqoxr,task_description,invalid
+"VisualEditor: Tables with a faulty <tr> 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 <tr> 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.",1371497885,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> at their end display it, confusing users","(In reply to comment #4)
+> This is a Parsoid bug. The PHP parser does not generate a <tr> for this
+> wikitext, and Parsoid does.
+
+Does the PHP parser create it but it then gets tidied away?",1371497466,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> at their end display it, confusing users","This is a Parsoid bug. The PHP parser does not generate a <tr> for this wikitext, and Parsoid does.",1371497353,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> 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. :-(",1371497109,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> 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 |}...,1371497019,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> 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 
+
+  |-
+  | <content>
+  |-
+  |}
+
+… 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.",1371496639,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+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",1371468780,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ss2itizzzz4vdy6z2bwv,task_description,resolved
+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 ***",1371510441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ss2itizzzz4vdy6z2bwv,task_subcomment,NA
+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",1371466320,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k4uqhsrhnkkuz3d2z6l6,task_description,resolved
+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],1372934078,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k4uqhsrhnkkuz3d2z6l6,task_subcomment,NA
+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 <nowiki>s around wiki-able elements of tables is also, I believe, fixed in production.
+
+<nowiki>s around wikitext are, of course, intentional.",1371671665,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k4uqhsrhnkkuz3d2z6l6,task_subcomment,NA
+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,1371475258,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k4uqhsrhnkkuz3d2z6l6,task_subcomment,NA
+VisualEditor: Unexpected padding,"See the tabs on https://en.wikipedia.org/wiki/User:Panpog1 for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371466080,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jzepbqpzu7s7bfg4k2ua,task_description,resolved
+VisualEditor: Unexpected padding,Fixed.,1372015377,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jzepbqpzu7s7bfg4k2ua,task_subcomment,NA
+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",1371403200,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6tdi4t2hiwd4kw4wdp3k,task_description,resolved
+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 ***",1371409196,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-6tdi4t2hiwd4kw4wdp3k,task_subcomment,NA
+UniversalLanguageSelector Does not work with VisualEditor,"**bellayet** wrote:
+
+ULS Input tool is not supporting VisualEditor.",1371405203,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6tdi4t2hiwd4kw4wdp3k,task_subcomment,NA
+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",1371382800,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-5ezr4schgjcznl2chb3p,task_description,declined
+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?",1371422998,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.",1371420335,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.",1371416756,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.",1371415303,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.,1371415095,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+VisualEditor bugzilla component should be under MediaWiki extensions,...and Bugzilla bugs should be filed under Bugzilla. Moving.,1371408158,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.",1371408122,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+"""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",1371315060,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-oz4sidkwsjedlisknc5h,task_description,invalid
+"""Use the wikitext editor for editing sections while VisualEditor is in beta"" should be default",Thanks. I like the chosen solution.,1372542001,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-oz4sidkwsjedlisknc5h,task_subcomment,NA
+"""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).",1372279685,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oz4sidkwsjedlisknc5h,task_subcomment,NA
+"""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.",1372129450,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oz4sidkwsjedlisknc5h,task_subcomment,NA
+Implement the same EventLogging of page edits in wikitext editor as in VisualEditor for comparison purposes,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371231960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tmvxleqap5uqab7s5tju,task_description,resolved
+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.",1371507422,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tmvxleqap5uqab7s5tju,task_subcomment,NA
+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).",1371233136,PHID-USER-qb5aoo443n6fezsozhv4,PHID-TASK-tmvxleqap5uqab7s5tju,task_subcomment,NA
+Configure VisualEditor for section edit links to go to VisualEditor by default,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371155460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c4vkf2igh4ozkrhmdcdd,task_description,invalid
+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.,1371161579,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c4vkf2igh4ozkrhmdcdd,task_subcomment,NA
+VisualEditor: Switch over to handle mw:WikiLink/Interwiki,"Currently links with mw:WikiLink/Interwiki get alienated
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371150540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ruct6x62hxyefsmpylp6,task_description,resolved
+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 ***",1371150585,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ruct6x62hxyefsmpylp6,task_subcomment,NA
+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",1371145680,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-aujnfu5wgjys4i7m3tqa,task_description,resolved
+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 ***",1371153385,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aujnfu5wgjys4i7m3tqa,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) 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 <Gallery></Gallery>
+
+Anything following the opening <Gallery> 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",1371125760,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-7xdz6csv454jmjt43l3k,task_description,resolved
+Extension tags starting with a capital (<Gallery>) 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],1372934067,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) seem to confuse the parser,https://gerrit.wikimedia.org/r/68727 (Gerrit Change I288f6ec9e4117ce58e2f445e73868937be1654af) | change APPROVED and MERGED [by jenkins-bot],1371249813,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) seem to confuse the parser,Related URL: https://gerrit.wikimedia.org/r/68727 (Gerrit Change I288f6ec9e4117ce58e2f445e73868937be1654af),1371238814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) seem to confuse the parser,*** Bug 49579 has been marked as a duplicate of this bug. ***,1371225610,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) 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?)",1371135498,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+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",1371117420,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ku4zjzbgxbemhv6sicxc,task_description,resolved
+VisualEditor: Mass of extraneous quot and amp marks,"I think that we've fixed this bug, but if it recurs please re-open.",1372014851,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ku4zjzbgxbemhv6sicxc,task_subcomment,NA
+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",1371058200,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-j57p7ueywyekpmhxkqes,task_description,resolved
+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 ***",1380609083,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-j57p7ueywyekpmhxkqes,task_subcomment,NA
+VisualEditor: Add the ability to drag highlighted text around with the mouse,Neat! Thanks :),1371058632,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-j57p7ueywyekpmhxkqes,task_subcomment,NA
+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 ***",1371058332,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j57p7ueywyekpmhxkqes,task_subcomment,NA
+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",1371027000,PHID-USER-vyidforzdhnrsoweujao,PHID-TASK-ajsfntti2ybnqjqeqxfs,task_description,resolved
+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 ***",1371049016,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ajsfntti2ybnqjqeqxfs,task_subcomment,NA
+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",1370906580,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-bumkxu7r6tdc2iyjok4e,task_description,resolved
+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.",1372762967,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-bumkxu7r6tdc2iyjok4e,task_subcomment,NA
+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.",1371227753,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-bumkxu7r6tdc2iyjok4e,task_subcomment,NA
+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}",1370856240,PHID-USER-ixwg3kf22idjy7x4ncxf,PHID-TASK-wdm6ddtjkbpjvqclln2i,task_description,resolved
+VisualEditor: Linking to an image results in the image being loaded,"
+
+*** This bug has been marked as a duplicate of bug 48387 ***",1370883912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdm6ddtjkbpjvqclln2i,task_subcomment,NA
+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",1370689740,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-n7737xkjqezrnwwaava3,task_description,resolved
+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 ***",1370840639,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n7737xkjqezrnwwaava3,task_subcomment,NA
+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",1370270880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f22y5n2hutfcuixay276,task_description,resolved
+Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;,Done on 2013-06-06.,1370741026,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f22y5n2hutfcuixay276,task_subcomment,NA
+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.",1370288193,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f22y5n2hutfcuixay276,task_subcomment,NA
+Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;,And the test and MW.org wikis.,1370286285,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f22y5n2hutfcuixay276,task_subcomment,NA
+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",1369745520,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_description,resolved
+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 ***",1374227951,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+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""'.",1371841158,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+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.",1371066634,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+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.",1369937612,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+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.",1369755874,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+"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",1369114380,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6nrh4cee4ez6cwykweo5,task_description,resolved
+"VisualEditor misrepresents linked files as embedded inline, when editing","
+
+*** This bug has been marked as a duplicate of bug 48387 ***",1369114571,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6nrh4cee4ez6cwykweo5,task_subcomment,NA
+"VisualEditor misrepresents linked files as embedded inline, when editing","**swalling** wrote:
+
+Screenshot of markup
+
+**Attached**: {F10438}",1369114456,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6nrh4cee4ez6cwykweo5,task_subcomment,NA
+"VisualEditor misrepresents linked files as embedded inline, when editing","**swalling** wrote:
+
+Edit mode, with incorrect thumbnails
+
+**Attached**: {F10437}",1369114431,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6nrh4cee4ez6cwykweo5,task_subcomment,NA
+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",1369078800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4ottk5yqyncneqh7goju,task_description,resolved
+Enable section-editing on 'beta' profile of VisualEditor deployments,Done today.,1371169125,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4ottk5yqyncneqh7goju,task_subcomment,NA
+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",1369067700,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-q6etjfxib3te52jrdbqh,task_description,resolved
+MediaWiki:Visualeditor-feedback-link doesn't use wiki language,"
+
+*** This bug has been marked as a duplicate of bug 47730 ***",1369068249,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q6etjfxib3te52jrdbqh,task_subcomment,NA
+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}",1368849600,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-f54j3i3yobgyvswaikfo,task_description,resolved
+VisualEditor expanding image links,"
+
+*** This bug has been marked as a duplicate of bug 48387 ***",1368979809,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f54j3i3yobgyvswaikfo,task_subcomment,NA
+"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",1368746160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a6xscw7mjvhcbwgufh5y,task_description,invalid
+"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.,1368747382,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a6xscw7mjvhcbwgufh5y,task_subcomment,NA
+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",1368684120,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-zfww4nd7axazvbfkd7qj,task_description,invalid
+List looks like it has extra empty lines,"Oh, I see, my bad, I should have checked the wikicode! :-)",1369104667,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-zfww4nd7axazvbfkd7qj,task_subcomment,NA
+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<ref name=""statinfo.biz""/> (2003)
+> *21 Sweden	 	639,000<ref name=""statinfo.biz""/> (2004)
+> 
+> *22 Ukraine	 	562,000<ref name=""statinfo.biz""/> (1995)
+> *23 France	 	544,000<ref name=""statinfo.biz""/> (2003)
+> *24 Australia	 	423,000<ref name=""statinfo.biz""/> (1995)
+> 
+> *25	Portugal	 	399,000<ref name=""statinfo.biz""/>	(2004)	
+> *26	Bulgaria	 	353,000<ref name=""statinfo.biz""/>	(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. :-))",1369080566,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zfww4nd7axazvbfkd7qj,task_subcomment,NA
+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",1368662520,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-a6lxhzu2xrx5tgje6umc,task_description,declined
+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.",1368662919,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a6lxhzu2xrx5tgje6umc,task_subcomment,NA
+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",1368583740,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-h57f3cph7qycjnbwjvnw,task_description,resolved
+VisualEditor: Can not paste new link anchor,"**jiabao.foss** wrote:
+
+That's very nice of you! I would love to investigate this bug.",1368805529,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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.",1368771998,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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. :)",1368767327,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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 ***",1368726943,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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.",1368725524,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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.",1368684779,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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}",1368565440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-apdnw6jklub4mtqzckmn,task_description,resolved
+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 ***",1368569378,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-apdnw6jklub4mtqzckmn,task_subcomment,NA
+VisualEditor link tool incorrectly shows a red link,"VisualEditor link dialog box incorrectly showing red text, 2013-05-13
+
+Go to <https://www.mediawiki.org/wiki/Sysadmin_hub>. 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}",1368500280,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-zpvndgxny4i6jsgnxaga,task_description,resolved
+VisualEditor link tool incorrectly shows a red link,"Also reported by Timo; given work us underway, DUPEing up rather than down.
+
+*** This bug has been marked as a duplicate of bug 48476 ***",1368720868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zpvndgxny4i6jsgnxaga,task_subcomment,NA
+"""visualeditor-diff-nochanges"" exposed on mediawiki.org","VisualEditor message key exposed on mediawiki.org, 2013-05-13
+
+URL: <https://www.mediawiki.org/wiki/MobileFrontend/Photo_upload/Analysis>
+
+Error: see attached screenshot
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10756}",1368497760,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-uuriwo6q3mdhjyt6egwi,task_description,resolved
+"""visualeditor-diff-nochanges"" exposed on mediawiki.org",Now fixed.,1368545353,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uuriwo6q3mdhjyt6egwi,task_subcomment,NA
+"""visualeditor-diff-nochanges"" exposed on mediawiki.org",Looks like <visualeditor-diff-nochanges> is not in MW.org's message file; need to do a message purge?,1368500743,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uuriwo6q3mdhjyt6egwi,task_subcomment,NA
+"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",1368150660,PHID-USER-gibrlx54k2riiuit5paf,PHID-TASK-tstjv3noyoaah6bfdmns,task_description,resolved
+"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 ***",1368150918,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tstjv3noyoaah6bfdmns,task_subcomment,NA
+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",1367872680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_description,resolved
+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],1372934001,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+Parsoid: HTML comment with immediately following table has newline split removed,Fixed in production.,1367944050,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+Parsoid: HTML comment with immediately following table has newline split removed,Related URL: https://gerrit.wikimedia.org/r/62546 (Gerrit Change If16dda01058715acee8df347b2b9c4da84609113),1367884917,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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?,1367877227,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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).",1367876908,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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?",1367876730,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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.",1367876593,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+Parsoid: HTML comment with immediately following table has newline split removed,Can you link to the original report?,1367876265,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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.",1367874446,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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",1367873178,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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.:
+
+<b>Bold on load text</b><b>added text</b>
+
+Which Parsoid converts to
+
+'''Bold on load text''''''added text'''
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367774100,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hc26warwwz5ylqujc3td,task_description,resolved
+VisualEditor: Adjacent annotations which are equal by name but not reference do not serialise correctly.,Merged into master.,1367871652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hc26warwwz5ylqujc3td,task_subcomment,NA
+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),1367782652,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hc26warwwz5ylqujc3td,task_subcomment,NA
+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 </span> and </table> got added automatically.
+
+Where's that ""partial serialization"" mentioned before?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367290980,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-slnchzhtiw4uoxg47vla,task_description,resolved
+VisualEditor: Extra tags got inserted causing infobox layout to be broken,"The main part of this bug (the extra </span> and </table>) 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 ***",1367545048,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-slnchzhtiw4uoxg47vla,task_subcomment,NA
+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",1367215380,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-r75ffyh3qiqooawo44eb,task_description,declined
+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.",1367544785,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r75ffyh3qiqooawo44eb,task_subcomment,NA
+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",1367205180,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_description,resolved
+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 ***",1367268091,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_subcomment,NA
+RTL Support for VisualEditor,"I'll tentatively reopen it and mark it as blocking 33126 instead.
+Not sure though, maybe James knows. :)",1367231596,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_subcomment,NA
+RTL Support for VisualEditor,It's a bug for tracking a GSoC proposal. I think that it should be reopened.,1367228877,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_subcomment,NA
+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 ***",1367228662,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_subcomment,NA
+[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",1367047080,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ul25dgz4nyeridoqmsqg,task_description,resolved
+[VisualEditor] CSS and JS pages should only be editable using the source editor,"
+
+*** This bug has been marked as a duplicate of bug 47456 ***",1367097296,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ul25dgz4nyeridoqmsqg,task_subcomment,NA
+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",1367013780,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-a56uzvltsvz2gw6egtar,task_description,invalid
+Feedback is broken,"Not actually broken, see bug 42974.",1367222196,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-a56uzvltsvz2gw6egtar,task_subcomment,NA
+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",1367008080,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-exyn4bfiq2igip2xy6r4,task_description,declined
+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.",1367019704,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-exyn4bfiq2igip2xy6r4,task_subcomment,NA
+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).,1367009441,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-exyn4bfiq2igip2xy6r4,task_subcomment,NA
+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",1366719660,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ajr6uvwq3l2hdzyqjden,task_description,resolved
+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 ***",1366741802,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ajr6uvwq3l2hdzyqjden,task_subcomment,NA
+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}",1366719765,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ajr6uvwq3l2hdzyqjden,task_subcomment,NA
+"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",1366388640,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ob7cxxrhd6d3aeazrujm,task_description,resolved
+"VisualEditor: Dirty diffs with FF, but not in Chrome on pages with citations","
+
+*** This bug has been marked as a duplicate of bug 47417 ***",1366391720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ob7cxxrhd6d3aeazrujm,task_subcomment,NA
+"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",1366388836,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ob7cxxrhd6d3aeazrujm,task_subcomment,NA
+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",1366058760,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-vav3ssxyt7puz6mth7ck,task_description,resolved
+VisualEditor: Problem with placing cursor inside slug (inline|block) with mouse,Fixed here: https://gerrit.wikimedia.org/r/#/c/59199/,1366059192,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-vav3ssxyt7puz6mth7ck,task_subcomment,NA
+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",1364916660,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ryyonehlcnqdc46zjg2w,task_description,resolved
+VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,Now fixed.,1366142624,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,Related URL: https://gerrit.wikimedia.org/r/58868 (Gerrit Change I6b2700d65476c4d34ba4a01a88382d7af8e736fb),1365765433,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,Actually Ed is still working on it.,1365029413,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+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/,1365024583,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+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",1364916742,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+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",1364433480,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4q75ixwk7yvcayzud2qd,task_description,resolved
+VisualEditor: Allow nodes to handle their own children,Done in https://gerrit.wikimedia.org/r/#/c/58645/ and related commits.,1366130702,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4q75ixwk7yvcayzud2qd,task_subcomment,NA
+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",1364167560,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-sk3uspo3yfsnwm2o672b,task_description,resolved
+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 ***",1364167729,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sk3uspo3yfsnwm2o672b,task_subcomment,NA
+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",1364163180,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-jhlniwxu2ykuroltxk3l,task_description,declined
+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],1372934009,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364231575,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364231508,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364231440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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 :)",1364231169,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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?",1364229706,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364228786,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364227272,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364165114,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+"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",1364127180,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-6vicxrcuqmyqgizvbnop,task_description,resolved
+"Just added single character, but at review all content is replaced","
+
+*** This bug has been marked as a duplicate of bug 43103 ***",1364127463,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-6vicxrcuqmyqgizvbnop,task_subcomment,NA
+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",1364126940,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-l2eaq3bdozrt2dgpbncq,task_description,resolved
+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 ***",1364164432,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l2eaq3bdozrt2dgpbncq,task_subcomment,NA
+VisualEditor: store annotations in a document-wide index/value store and serialize as integer indexes,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363693320,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-e7xy2ghygeqe5vvk7vir,task_description,resolved
+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),1363819486,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-e7xy2ghygeqe5vvk7vir,task_subcomment,NA
+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",1363693508,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-e7xy2ghygeqe5vvk7vir,task_subcomment,NA
+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/",1363637880,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_description,declined
+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.",1375350900,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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.",1372186269,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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?",1372185965,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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.",1363805065,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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.",1363803636,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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}",1361749260,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mq355eomr24cmluqc7dh,task_description,resolved
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],A reasonable resolution of this issue. :),1361832255,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+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 <pre>. 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.",1361831946,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+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:
+
+<table>
+<tr>
+<td>
+  a</td>
+<td>
+ b
+</td>
+</tr>
+</table>
+
+""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.",1361826274,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],"This might be a bug in https://gerrit.wikimedia.org/r/#/c/32405/ or a regression.  The <pre> is coming from an #if parser function which should not have as per that commit message.
+
+Will investigate.",1361822814,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Created attachment 11841
+HTML of {{disambiguation}} from Parsoid
+
+The main problem is the presence of a <pre> that shouldn't be there.
+
+**Attached**: {F10465}",1361749531,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Created attachment 11840
+Screenshot of {{disambiguation}} from Parsoid
+
+**Attached**: {F10464}",1361749431,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Created attachment 11839
+HTML of {{disambiguation}} on [[Loco]] at en.wikipedia.org
+
+**Attached**: {F10463}",1361749373,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+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",1360879800,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2lufxleaemvynes2b2da,task_description,declined
+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.",1360889187,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2lufxleaemvynes2b2da,task_subcomment,NA
+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].<anonymous> (/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].<anonymous> (/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",1360784520,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xtyrp3i5752jen7uoe6m,task_description,invalid
+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],1372934041,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xtyrp3i5752jen7uoe6m,task_subcomment,NA
+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.",1360785028,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xtyrp3i5752jen7uoe6m,task_subcomment,NA
+VisualEditor: VE chokes on unexpected redirect response from Parsoid,"**Author:** `phil`
+
+**Description:**
+I created a page using the normal editor that was
+
+
+<gallery>
+File:Example.jpg|Caption1
+#REDIRECT [[Target page name]]
+</gallery>
+
+
+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",1360730040,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2aj3mfax5n7tlrsztfhy,task_description,resolved
+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.",1362769118,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2aj3mfax5n7tlrsztfhy,task_subcomment,NA
+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",1360785321,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2aj3mfax5n7tlrsztfhy,task_subcomment,NA
+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).",1360783589,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2aj3mfax5n7tlrsztfhy,task_subcomment,NA
+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",1360462980,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aqea5euyvi5ekuwq3kig,task_description,resolved
+VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,Now merged.,1360976726,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aqea5euyvi5ekuwq3kig,task_subcomment,NA
+VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,"Whoops, not yet merged.",1360613606,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aqea5euyvi5ekuwq3kig,task_subcomment,NA
+VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,Merged.,1360612923,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-aqea5euyvi5ekuwq3kig,task_subcomment,NA
+VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,Patch in: https://gerrit.wikimedia.org/r/48491,1360612133,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-aqea5euyvi5ekuwq3kig,task_subcomment,NA
+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",1360297620,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hiumuha3tc6xqypqt2lz,task_description,resolved
+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 ***",1360376842,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hiumuha3tc6xqypqt2lz,task_subcomment,NA
+VisualEditor: What Heading levels are offered should flex based,"Created attachment 11760
+Screenshot showing H1 to H6 in VisualEditor mode
+
+**Attached**: {F11017}",1360376691,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hiumuha3tc6xqypqt2lz,task_subcomment,NA
+VisualEditor: What Heading levels are offered should flex based,"Created attachment 11759
+Screenshot showing H1 to H6 in read mode
+
+**Attached**: {F11015}",1360376669,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hiumuha3tc6xqypqt2lz,task_subcomment,NA
+Parsoid: Linktrails should get a <nowiki /> 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}",1360296540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nsc6gcp3vvg4tvl6tyfb,task_description,resolved
+Parsoid: Linktrails should get a <nowiki /> added on serialisation,"Ah, couldn't find the bug; thanks, Gabriel.
+
+*** This bug has been marked as a duplicate of bug 33091 ***",1360704683,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nsc6gcp3vvg4tvl6tyfb,task_subcomment,NA
+Parsoid: Linktrails should get a <nowiki /> added on serialisation,"To me it seems that the VE should produce a DOM including the space: 
+
+<a href=""foo"">bar</a> 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.",1360704397,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-nsc6gcp3vvg4tvl6tyfb,task_subcomment,NA
+Parsoid: Linktrails should get a <nowiki /> added on serialisation,"This appears to be a problem in Parsoid.
+
+In VisualEditor the user has (effectively) created <a href=""foo"">bar</a>baz; it is unexpectedly converted into [[foo|bar]]baz instead of [[foo|bar]]<nowiki />baz, hence the confusion.
+
+Gabriel, thoughts?",1360703129,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nsc6gcp3vvg4tvl6tyfb,task_subcomment,NA
+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",1360091400,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-xpyddbk7oe25b7f7bpp3,task_description,resolved
+VisualEditor: Opening link inspector without selection in stand alone instance throws error.,Now merged.,1360105358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xpyddbk7oe25b7f7bpp3,task_subcomment,NA
+VisualEditor: Opening link inspector without selection in stand alone instance throws error.,Patched in https://gerrit.wikimedia.org/r/#/c/47615/,1360094494,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-xpyddbk7oe25b7f7bpp3,task_subcomment,NA
+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 <nowiki> 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 <nowiki> tags up to the formatted character and leaves the rest of the line alone
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10444}",1359487500,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cke5acua2kmqpq2rtiv4,task_description,declined
+VisualEditor: Unexpected behavior when line starts with space,"... but when you save "" le'''''adi'''''ing space"" in the wikitext editor, you get <pre>le'''''adi'''''ing space</pre>, not <p> le'''''adi'''''ing space</p>. The <nowiki> tags are necessary to get the latter, which is what the VE user actually typed.
+
+Closing as WONTFIX.",1360208015,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+VisualEditor: Unexpected behavior when line starts with space,"Created attachment 11719
+normal editor vs. VE on save
+
+**Attached**: {F10447}",1359744124,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+VisualEditor: Unexpected behavior when line starts with space,"Created attachment 11718
+normal editor vs. VE preview
+
+**Attached**: {F10446}",1359744087,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+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 <nowiki> tags to this string.  VE adds <nowiki> tags. 
+
+The normal editor does not save the text with <nowiki> tags.  VE saves the text with <nowiki> tags. 
+
+It may be that VE adds <nowiki> tags by design, but they seem unnecessary.  Again, I could be wrong.",1359744005,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+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 <P> Foo</P> 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?",1359682189,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+VisualEditor: Unexpected behavior when line starts with space,look what happens in the regular editor.  I think VE is doing something really strange here.,1359671085,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+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 <nowiki> elements?,1359669739,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+VisualEditor: Unexpected behavior when line starts with space,"Created attachment 11706
+nowiki tags with formatted text
+
+**Attached**: {F10445}",1359487603,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+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",1359038700,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gf44zknlabktvyuiobnc,task_description,resolved
+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 ***",1360207511,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gf44zknlabktvyuiobnc,task_subcomment,NA
+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 :)",1359450666,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gf44zknlabktvyuiobnc,task_subcomment,NA
+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",1358094720,PHID-USER-37d2msujvpp2rippbzoq,PHID-TASK-fmsq2a44unt5qvw7fvjz,task_description,declined
+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.",1425405042,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fmsq2a44unt5qvw7fvjz,task_subcomment,NA
+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",1409587205,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fmsq2a44unt5qvw7fvjz,task_subcomment,NA
+"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",1357860900,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-cek4b33i7kzn3d5tir7d,task_description,resolved
+"VisualEditor: Make link inspector aware of annotations, rather than just target strings",Made it to master for the 2013-01-16 branch.,1358388388,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cek4b33i7kzn3d5tir7d,task_subcomment,NA
+"VisualEditor: Make link inspector aware of annotations, rather than just target strings",Addressed in gerrit 43028.,1357861248,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cek4b33i7kzn3d5tir7d,task_subcomment,NA
+"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",1357052100,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v5mejtdved3hadzpnblg,task_description,invalid
+"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://' );",1357704294,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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!",1357349661,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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",1357346134,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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?",1357308806,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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?",1357125626,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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?",1357116244,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+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",1356608820,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-bbwwebnria5w3khcdb2z,task_description,resolved
+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 ***",1356713507,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-bbwwebnria5w3khcdb2z,task_subcomment,NA
+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",1356551700,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-d3f2ddd27saapnkqzblp,task_description,resolved
+Removing link trail doesn't affect the output,Finally squashed in https://gerrit.wikimedia.org/r/#/c/43985/.,1358213523,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-d3f2ddd27saapnkqzblp,task_subcomment,NA
+Removing link trail doesn't affect the output,Change I126116de should fix this.,1356634590,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-d3f2ddd27saapnkqzblp,task_subcomment,NA
+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.",1356553785,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-d3f2ddd27saapnkqzblp,task_subcomment,NA
+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",1356106320,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6tdn24gf46lji7yqfvl2,task_description,invalid
+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.,1356106907,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6tdn24gf46lji7yqfvl2,task_subcomment,NA
+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",1355898660,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-jtaql5mrtvhb43vajwv3,task_description,resolved
+VisualEditor: Tooltip broken on outdent button,Thanks for the report.  This was patched in. https://gerrit.wikimedia.org/r/#/c/38810/,1355942170,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-jtaql5mrtvhb43vajwv3,task_subcomment,NA
+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 <hiero> 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 <hiero> 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",1355479740,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-ttm23g3exfsgbjvupqdx,task_description,resolved
+Reporter missing in IRC announcement of new issue,"
+
+*** This bug has been marked as a duplicate of bug 42774 ***",1355479865,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ttm23g3exfsgbjvupqdx,task_subcomment,NA
+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",1355414040,PHID-USER-wel3wo6tppcxgnrthxls,PHID-TASK-i3kcektvabsqugyb5tzv,task_description,declined
+VisualEditor never loads,Wth?! Why does it take so much time to load. But then it atlast worked.,1355415643,PHID-USER-wel3wo6tppcxgnrthxls,PHID-TASK-i3kcektvabsqugyb5tzv,task_subcomment,NA
+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",1355398980,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-ux4izidb7xrrwhvej2xp,task_description,declined
+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.",1355445344,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-ux4izidb7xrrwhvej2xp,task_subcomment,NA
+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.",1355443086,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ux4izidb7xrrwhvej2xp,task_subcomment,NA
+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.)",1355436686,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-ux4izidb7xrrwhvej2xp,task_subcomment,NA
+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.",1355435276,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ux4izidb7xrrwhvej2xp,task_subcomment,NA
+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",1355386260,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-ly2xm7tz73tvksvhmtyz,task_description,resolved
+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.,1357678696,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ly2xm7tz73tvksvhmtyz,task_subcomment,NA
+VisualEditor: Things are sometimes alienated as block when they should be inline,https://gerrit.wikimedia.org/r/39846,1356175107,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ly2xm7tz73tvksvhmtyz,task_subcomment,NA
+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 <div> 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 <div class=""ve-ce-alienBlock""> or <span class=""ve-ce-alienInline""> 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.",1355389006,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ly2xm7tz73tvksvhmtyz,task_subcomment,NA
+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}",1355378640,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kvsbzknbe6m5oydwjk6y,task_description,resolved
+VisualEditor: Escape from LinkAnnotation editor closes annotation editor but leaves suggestion box floating,"
+
+%%%*** This bug has been marked as a duplicate of bug 43051 ***%%%",1355425528,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-kvsbzknbe6m5oydwjk6y,task_subcomment,NA
+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",1355358660,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-ton3dd6uf2z3sfe3n2k3,task_description,resolved
+VisualEditor: Suggestion tool fails to close when escaping out of context menu.,Add to deployment milestone.,1357594470,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ton3dd6uf2z3sfe3n2k3,task_subcomment,NA
+VisualEditor: Suggestion tool fails to close when escaping out of context menu.,%%%*** Bug 43055 has been marked as a duplicate of this bug. ***%%%,1355425528,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-ton3dd6uf2z3sfe3n2k3,task_subcomment,NA
+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",1355360183,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-ton3dd6uf2z3sfe3n2k3,task_subcomment,NA
+"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",1355344680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gax37c3j4qvaskyhk55t,task_description,resolved
+"VisualEditor: For initial deployment, do not over-ride edit-section links",This appears to have missed the deploy-train; moving.,1357578100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gax37c3j4qvaskyhk55t,task_subcomment,NA
+"VisualEditor: For initial deployment, do not over-ride edit-section links",Now merged into master.,1355829010,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gax37c3j4qvaskyhk55t,task_subcomment,NA
+"VisualEditor: For initial deployment, do not over-ride edit-section links",Fixed by https://gerrit.wikimedia.org/r/#/c/38451/,1355804868,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gax37c3j4qvaskyhk55t,task_subcomment,NA
+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",1355342280,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-uqidpcw3y4xgb5ynjwev,task_description,resolved
+VisualEditor: Undo just after load of the editor causes JS error.,"Also happens for redo.
+Patched in: https://gerrit.wikimedia.org/r/#/c/38349/",1355342889,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-uqidpcw3y4xgb5ynjwev,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,"Seen on the VE-editing interface of https://www.mediawiki.org/wiki/VisualEditor:Test
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355292540,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-3ytipv46bzm44jpqmwoq,task_description,resolved
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,Add to deployment milestone.,1357594496,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,Working for me now after a hard refresh.,1355341256,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,"The messages are certainly in the i18n file, it probably just needs a l10n cache rebuild. Doing that now.",1355336196,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> 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",1355331834,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> 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.",1355327793,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,"Also messages in that dialog, like <visualeditor-savedialog-title-review>, <visualeditor-savedialog-title-review-wrong>, <visualeditor-savedialog-title-review-good> etc",1355297902,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+"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",1355189160,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-ivhyp5yplrphnwughsqu,task_description,resolved
+"VisualEditor: While using link inspector, transaction hangs and page eventually explodes.",Fixed in https://gerrit.wikimedia.org/r/#/c/38004/,1355191424,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-ivhyp5yplrphnwughsqu,task_subcomment,NA
+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",1355175300,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-hydd4sggtsrxlgqhafqc,task_description,resolved
+VisualEditor: Inspector doesn't open properly,*** Bug 37856 has been marked as a duplicate of this bug. ***,1355350453,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hydd4sggtsrxlgqhafqc,task_subcomment,NA
+VisualEditor: Inspector doesn't open properly,Fixed in gerrit 37945.,1355176593,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hydd4sggtsrxlgqhafqc,task_subcomment,NA
+VisualEditor: Re-enable the feedback tool for deployment,"Point to [[Project:VisualEditor/Feedback]] for now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355171460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6k6omehrnjj3d64g3xkp,task_description,resolved
+VisualEditor: Re-enable the feedback tool for deployment,See also https://gerrit.wikimedia.org/r/#/c/32700/ for usage.,1355175058,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6k6omehrnjj3d64g3xkp,task_subcomment,NA
+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",1355168340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qsgzi7766f5xj7zdn6hb,task_description,resolved
+VisualEditor: Toolbar tooltips should also suggest key-commands,"Now merged, will go out in 2013-02-04 release cycle.",1358469697,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qsgzi7766f5xj7zdn6hb,task_subcomment,NA
+VisualEditor: Toolbar tooltips should also suggest key-commands,Patched in https://gerrit.wikimedia.org/r/#/c/44347/,1358375049,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-qsgzi7766f5xj7zdn6hb,task_subcomment,NA
+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",1354930620,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qype6jzcuqvgj55crv3,task_description,resolved
+VisualEditor: Notifications should not use db-variant of page titles,"(In reply to comment #1)
+> Change-Id: Ie84168cd2509a17c180c6143a87a18ae8bbb3d0a
+Merged.",1354942098,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2qype6jzcuqvgj55crv3,task_subcomment,NA
+VisualEditor: Notifications should not use db-variant of page titles,Change-Id: Ie84168cd2509a17c180c6143a87a18ae8bbb3d0a,1354930713,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qype6jzcuqvgj55crv3,task_subcomment,NA
+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",1354926720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu7m2pj54l427crmnupd,task_description,resolved
+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"".",1359516361,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu7m2pj54l427crmnupd,task_subcomment,NA
+VisualEditor: Support Internet Explorer,Please see Bug 41233,1359065649,PHID-USER-wi7txqp5ld5ze33dx7am,PHID-TASK-mu7m2pj54l427crmnupd,task_subcomment,NA
+VisualEditor: Support Internet Explorer,"Argh, ignore that; an at-least partial fix in gerrit 37592.",1354926991,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu7m2pj54l427crmnupd,task_subcomment,NA
+VisualEditor: Support Internet Explorer,Attempted fixes in gerrit 37566 and gerrit 37570.,1354926882,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu7m2pj54l427crmnupd,task_subcomment,NA
+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",1354920600,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-jvbmuzupmyildaswp3ax,task_description,resolved
+VisualEditor: Create a link at the beginning of the document throws rangy error,Related URL: https://gerrit.wikimedia.org/r/69707 (Gerrit Change I8bcdea0f7a6951216bf8368865d23ef6246880ea),1371753492,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jvbmuzupmyildaswp3ax,task_subcomment,NA
+VisualEditor: Create a link at the beginning of the document throws rangy error,Fix in gerrit 37603,1354931366,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jvbmuzupmyildaswp3ax,task_subcomment,NA
+"VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354771560,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-75c273bypsftlyrbr3cc,task_description,resolved
+"VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language",Merged.,1354832652,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-75c273bypsftlyrbr3cc,task_subcomment,NA
+"VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language",Change-Id: I84fee641162cdeed290092e56fb0e1d2562d833d,1354771693,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-75c273bypsftlyrbr3cc,task_subcomment,NA
+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",1354596300,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vr2jeooanda24ls5knww,task_description,resolved
+VisualEditor: ext.visualEditor.specialMessages module cache invalidation broken,Now merged into master.,1354654432,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vr2jeooanda24ls5knww,task_subcomment,NA
+VisualEditor: ext.visualEditor.specialMessages module cache invalidation broken,Change-Id: I7f26b47e9467e850c08b9c217c4f1098590de109,1354607956,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vr2jeooanda24ls5knww,task_subcomment,NA
+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",1353963360,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-yjkqv35zcxvtirgx56ds,task_description,resolved
+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.",1354028484,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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",1354015514,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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.",1354001228,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),https://gerrit.wikimedia.org/r/#/c/35327/,1353972830,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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",1353970599,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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}",1353970120,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),Caused by https://gerrit.wikimedia.org/r/#/c/31330/,1353969954,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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",1353969228,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+VisualEditor: Temporarily add IE to blacklist for December release as CE support is currently insufficient,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1353529620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-drb6zxeswawnaqold54q,task_description,resolved
+VisualEditor: Temporarily add IE to blacklist for December release as CE support is currently insufficient,https://gerrit.wikimedia.org/r/#/c/34584/,1353530010,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-drb6zxeswawnaqold54q,task_subcomment,NA
+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",1352940180,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qyxlhx72vvvsjxiz5mxk,task_description,resolved
+VisualEditor: i18n for alien tooltip,Fixed in gerrit 33851,1353113705,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qyxlhx72vvvsjxiz5mxk,task_subcomment,NA
+VisualEditor: i18n for alien tooltip,"Also it's VisualEditor not ""Visual Editor"". :-)",1352940362,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qyxlhx72vvvsjxiz5mxk,task_subcomment,NA
+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",1352938800,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gcvicv5c5il3dfwvq4z6,task_description,resolved
+VisualEditor: Change markers don't propagate when generated paragraphs are unwrapped,"
+
+*** This bug has been marked as a duplicate of bug 41947 ***",1353108588,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gcvicv5c5il3dfwvq4z6,task_subcomment,NA
+[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",1352931660,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-btqaquo52pvsfg5ytjrc,task_description,resolved
+[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],1372934046,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-btqaquo52pvsfg5ytjrc,task_subcomment,NA
+[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 ***",1352932611,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-btqaquo52pvsfg5ytjrc,task_subcomment,NA
+[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.",1352931990,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-btqaquo52pvsfg5ytjrc,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"At the moment, prepending to lists is not obvious. I think most people would try to do it by pressing enter on the preceding line to create a new paragraph, then pressing the make (bulleted) list button.
+
+For some reason, this creates a list at the caret, but retains the blank paragraph afterwards (so you have list-para-list). Okay, so now you try to delete the para, but you can only deletes too much, for example merging the last list item on the first list with the first list item on the second list. In fact, pressing enter now works, but in any case the process is rather confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1352551740,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-54zoeovhyceutq4h2rxj,task_description,declined
+VisualEditor: Prepending to lists difficult,"Hmm, yes. I can certainly understand the case with (pre-existing) lists. But witness that neither of the two other editors mentioned put a slug (or indeed anything else) between the two adjoining lists created when one inserts a paragraph before a list and then presses the listify icon.
+
+(For Word, it would make no sense for them to because it's not two adjoining lists, just two adjoining list items; for GDoCs they just don't.)",1353757540,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"The ""weird blank paragraph"" is what a ""slug"" - a place in the editing interface where the user can insert some content. It needs to be there so that users can successfully place content between blocks, but it isn't an entire line (depending on your User Agent) - once you start entering content, it expands to be the same size as a ""real"" paragraph, however.
+
+An example of this is nested lists - in MediaWiki you can jump straight down to a second level of lists, but in HTML editing you still need to give the user some way to edit the list they're not in. This is why this wikitext:
+
+Hello
+** There
+
+... produces this in the VisualEditor:
+
+Hello
+* 
+** There
+
+... the middle ""line"" is a ""slug"" that will disappear once you save, but if you need to insert text that's where you can go.
+
+We're considering coming up with a little icon, perhaps a little like the cursor character, to make it clear that it's an insertion point rather than an actual blank line, but we're at early days yet.",1353723400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,Any thoughts James on preventing the creation of that weird blank paragraph?,1353368318,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"Okay, right, figured it out. It's the randomly inserted blank paragraph that's annoying me. Even GDocs doesn't do that (it assumes you've got two lists next to each other); moreover, it's not the same behaviour as when you've got a paragraph next.",1352938178,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Firstly, I disagree with you about what users will expect. Behaviour in most
+> > visual editors, notably including Google Docs and Microsoft Word, is that you
+> > cannot prepend to a list other than by splitting the first item 
+> 
+> I believe going to a preceding paragraph and clicking the ""make list"" button
+> also prepends to a list in Word.
+
+Yeah; we may want to ape this, but it's a lot of work for relatively little benefit and I think we can punt it to a later date - see bug 42115.
+
+> Google Doc's list handling is different,
+> admittedly. I'm having trouble reminding myself of what annoyed me about the
+> VE's current response (""Error loading data from server: Invalid response from
+> server"") though -- so it could have been something relatively minor that just
+> bugged me for a while.
+
+Yes, sorry, we're midst-deploy right now, hence errors. Give us five minutes. :-)",1352935201,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,s/a preceding paragraph/the preceding paragraph (line)/,1352935050,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"(In reply to comment #1)
+> Firstly, I disagree with you about what users will expect. Behaviour in most
+> visual editors, notably including Google Docs and Microsoft Word, is that you
+> cannot prepend to a list other than by splitting the first item 
+
+I believe going to a preceding paragraph and clicking the ""make list"" button also prepends to a list in Word. Google Doc's list handling is different, admittedly. I'm having trouble reminding myself of what annoyed me about the VE's current response (""Error loading data from server: Invalid response from server"") though -- so it could have been something relatively minor that just bugged me for a while.",1352934930,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"Firstly, I disagree with you about what users will expect. Behaviour in most visual editors, notably including Google Docs and Microsoft Word, is that you cannot prepend to a list other than by splitting the first item (i.e., by placing the cursor between the first bullet or enumerator and the start of the content on the first list item, and pressing 'Return').
+
+If you follow your instructions, you're creating a second, separate list before the original list, and then wanting the software to magically know that you want them merged, which is somewhat complex behaviour that we don't currently support well, so we should create a bug for that. However, I'm inclined to close this as a WONTFIX. Thoughts?",1352930949,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Restore lost Change Markers,"In the change-markers2 branch, we have some trouble.
+
+In a list item, there will be a <p> tag with change markers if I edit the content of the <li>. Roan decided to destroy those, and so did I. The change markers should instead be propagated to the <li>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352509140,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-bxfy5lj3p2kmooagyw4k,task_description,resolved
+VisualEditor: Restore lost Change Markers,*** Bug 42120 has been marked as a duplicate of this bug. ***,1353108588,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bxfy5lj3p2kmooagyw4k,task_subcomment,NA
+VisualEditor: Restore lost Change Markers,https://gerrit.wikimedia.org/r/33840,1353107651,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bxfy5lj3p2kmooagyw4k,task_subcomment,NA
+"VisualEditor: Post-uirewrite, list button does not behave as expected","
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1352499300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bzfy62f6eeawy7qsikz2,task_description,resolved
+"VisualEditor: Post-uirewrite, list button does not behave as expected",https://gerrit.wikimedia.org/r/32664,1352499455,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bzfy62f6eeawy7qsikz2,task_subcomment,NA
+VisualEditor: Overflow and background messed up in save dialog workflow,"Screenshot
+
+See screenshot. Legal text is floating loose, and the heading in the toolbar is overlapping the buttons.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9759}",1352465220,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-r3cecfzae44mq2jgxqtv,task_description,resolved
+VisualEditor: Overflow and background messed up in save dialog workflow,//**content hidden as private in Bugzilla**//,1353103492,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-r3cecfzae44mq2jgxqtv,task_subcomment,NA
+VisualEditor: Overflow and background messed up in save dialog workflow,Confirmed on master.,1352466731,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-r3cecfzae44mq2jgxqtv,task_subcomment,NA
+VisualEditor: Overflow and background messed up in save dialog workflow,As well as the arrow in the save button.,1352466157,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-r3cecfzae44mq2jgxqtv,task_subcomment,NA
+VisualEditor: Overflow and background messed up in save dialog workflow,This was fixed in https://gerrit.wikimedia.org/r/#/c/31868/,1352465630,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-r3cecfzae44mq2jgxqtv,task_subcomment,NA
+VisualEditor: Parsoid is sent text outside of any node for the first line of a new article,"Steps to repro:
+
+1. Open new page in VE.
+
+2. Click on first line, enter text, enter newline, enter more text.
+
+3. Click save.
+
+Expected behavior: Two paragraphs.
+
+Actual behavior: One paragraph with a single line break where there should be two.
+
+Tested locally and found that Parsoid's web service gets the DOM as something like ""First line<p>Second line</p>"", which it can't handle correctly (the fix breaks many other parser tests).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352420400,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-j4syqnzwdunhoucwx6o6,task_description,resolved
+VisualEditor: Parsoid is sent text outside of any node for the first line of a new article,"
+
+*** This bug has been marked as a duplicate of bug 42121 ***",1353133977,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j4syqnzwdunhoucwx6o6,task_subcomment,NA
+VisualEditor: Parsoid is sent text outside of any node for the first line of a new article,"Fixed by Roan in between filing and now - Parsoid now receives ""<p data-parsoid=""{&quot;dsr&quot;:[0,23]}"">First line</p><p data-parsoid=""{&quot;dsr&quot;:[0,23]}"">Second line</p>"".",1353133921,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j4syqnzwdunhoucwx6o6,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"Parsoid currently wraps the first newline in a <pre> in <span typeof=""mw:Placeholder""> , see also bug 41725 where I reported a bug in this behavior. Because of the way this interacts with VisualEditor, I would like Parsoid to drop this wrapping altogether. The reason for mw:Placeholder wrapping is supposed to be to protect things from VE, but we don't need it here and it's actually causing problems.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351978800,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_description,resolved
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"The right kind of protection is removed in https://gerrit.wikimedia.org/r/#/c/32003/. We had to perform some tricks to preserve the newline after the opening pre tag in the treebuilder. The HTML spec makes that newline optional, so it seems that DOM implementations are free to discard it and still be compliant with the spec. This might or might not bite you.",1352225021,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"The pre protection, that is.",1352160813,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"Ooops, sorry- read that too fast on Friday and just acted based on that distant memory today ;) The protection is back now. Will see about removing the protection later.",1352160799,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"(In reply to comment #1)
+> Great that you are handling <br> now ;) Removed the protection in
+> https://gerrit.wikimedia.org/r/#/c/31958/.
+I wasn't talking about <br>s at all, I was talking about the first newline in a <pre>.",1352160113,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,Great that you are handling <br> now ;) Removed the protection in https://gerrit.wikimedia.org/r/#/c/31958/.,1352154328,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+VisualEditor: Deal with mw:Placeholder span wrapping the first newline in a <pre>,"To distinguish between <pre>Foo</pre> and <pre>\nFoo</pre>, Parsoid gives us HTML like <pre><span typeof=""mw:Placeholder"">\n</span>Foo</pre> for the latter. We don't currently have any special handling for this placeholder in VE, so it shows up as an inline alien.
+
+I'm asking the Parsoid team to remove it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351915500,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rq2tsnu6ypd4j65ev7c2,task_description,resolved
+VisualEditor: Deal with mw:Placeholder span wrapping the first newline in a <pre>,"Parsoid removed this behavior as requested, and with https://gerrit.wikimedia.org/r/#/c/32260/ the editor now handles <pre>s correctly.",1352492571,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rq2tsnu6ypd4j65ev7c2,task_subcomment,NA
+VisualEditor: z-index problems in Monobook,"Screenshot of messed-up Monobook integration in Chrome
+
+The VE integration in Monobook is messed up, see screenshot. The toolbar is positioned too high, obscuring the content actions tab bar, except for the edit tab which protrudes through the toolbar. The toolbar is also off to the left a bit. The font size in the edit area is way too small, and the font size in the save dialog is way too big.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10131}",1351914420,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_description,resolved
+VisualEditor: z-index problems in Monobook,I'm going to remark this as closed - this breakage is bug 50652 which I believe we've just fixed.,1372893825,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_subcomment,NA
+VisualEditor: z-index problems in Monobook,"(In reply to comment #2)
+> Hope I'm not stepping on any toes by reopening, but this still seems to be an
+> issue. 
+> 
+> See http://i.imgur.com/h8SOdGB.png and more drastically
+> http://i.imgur.com/maUlOMv.png (the latter is when resizing the window to be
+> moderately smaller).
+Renamed bug to be applicable to these screenshots.",1372892844,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_subcomment,NA
+VisualEditor: z-index problems in Monobook,"**KilliondudeWP** wrote:
+
+Hope I'm not stepping on any toes by reopening, but this still seems to be an issue. 
+
+See http://i.imgur.com/h8SOdGB.png and more drastically http://i.imgur.com/maUlOMv.png (the latter is when resizing the window to be moderately smaller).",1372892746,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_subcomment,NA
+VisualEditor: z-index problems in Monobook,"Most of these issues were actually due to me messing up my Common.css, sorry :(
+
+Trevor fixed the remaining problems in https://gerrit.wikimedia.org/r/#/c/31943/",1352155670,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_subcomment,NA
+VisualEditor: Newlines in <pre> render wrongly,"Given the following wikitext:
+
+
+<pre>
+Foo
+Bar
+Baz
+Quux
+</pre>
+
+the CE rendering I get is a pre with Foo↵Bar↵Baz↵Quux , rather than a pre with actual line breaks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351912620,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-e52bbyzcqb4xr73axz3g,task_description,resolved
+VisualEditor: Newlines in <pre> render wrongly,Fixed by Roan some time ago.,1354155736,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e52bbyzcqb4xr73axz3g,task_subcomment,NA
+VisualEditor: Converting format across 2 lists with paragraphs in between fails,"1. Create a list, 2 paragraphs and then another list
+2. Select from inside the first list to inside the second list
+3. Change the format to Heading 2 using the toolbar
+4. See errors in the console
+
+This is to do with a bug in the ve.FormatAction class's convert function.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351282140,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jqy4wf5ol4o3dp66hs7r,task_description,resolved
+VisualEditor: Converting format across 2 lists with paragraphs in between fails,https://gerrit.wikimedia.org/r/#/c/30295/,1351290052,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jqy4wf5ol4o3dp66hs7r,task_subcomment,NA
+VisualEditor: Emptying paragraph in Firefox with backspace adds <br _moz_dirty>,"**Author:** `orbit`
+
+**Description:**
+Firefox naturally leaves a <br _moz_dirty> when the contents of a paragraph has been deleted. There are 2 cases, deleting text in a paragraph and deleting text in a paragraph in a list item.
+
+In the case of a paragraph NOT within a list item, the DOM is:
+<p><br _moz_dirty></p>. ve.ce.TextNode onUpdate cleans the parent, removing the <br>. 
+
+In the case of a paragraph WITHIN a list item, the DOM is:
+<li><p></p><br _moz_dirty></li>. Cleaning the parent doesn't remove the br, but parent.parent does. Maybe this needs to traverse up to the highest splittable node? 
+
+In both cases the focus does not return to the slug because the surface is locked, preventing showSelection (this is in the onChange method).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350672600,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cchu7wayqp2w3m4ikxkf,task_description,resolved
+VisualEditor: Emptying paragraph in Firefox with backspace adds <br _moz_dirty>,Fixed here: https://gerrit.wikimedia.org/r/#/c/37162/,1354755521,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-cchu7wayqp2w3m4ikxkf,task_subcomment,NA
+VisualEditor: Emptying paragraph in Firefox with backspace adds <br _moz_dirty>,I already found a few slightly different ways to solve this problem. After I will choose the best one I will update this ticket and send it for review to gerrit.,1351107837,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-cchu7wayqp2w3m4ikxkf,task_subcomment,NA
+VisualEditor: First 'space' in Firefox strands previous content in DIV outside of P element in new document,"Go to a non-existent document and press 'Create'
+
+1) Press a
+   Expect: ""a"" in a <P> element
+   Get: ""a"" in a <P> element
+2) Press <space>
+   Expect: ""a "" in a <P> element
+   Get: ""a"" in the document <DIV> followed by a newline, then "" "" in a <P> element
+3) Press b
+   Expect: ""a b"" in a <P> element
+   Get: ""a"" in the document <DIV> followed by a newline, then "" b"" in a <P> element
+4) Press <enter>
+   Expect: ""a b"" in a <P> element; a newline; then a <P> with a slug <SPAN>
+   Get: "" b"" in a <P> element; a newline; a <P> with a slug <SPAN>; another newline; then ""a"" in the document <DIV>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350582840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zkqsllah4f32kfkyu6pq,task_description,resolved
+VisualEditor: First 'space' in Firefox strands previous content in DIV outside of P element in new document,"**orbit** wrote:
+
+This has been fixed by Inez's ""Is there data"" change:
+https://gerrit.wikimedia.org/r/#/c/28463/",1350583392,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zkqsllah4f32kfkyu6pq,task_subcomment,NA
+VisualEditor: Deleting selection does not delete selected list bullet,"1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press: a b Enter c d
+3) Make ""cd"" a list item
+4) Press Delete
+
+
+Expected:
+
+ad
+
+
+Actual:
+
+a
+
+・ d
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350553800,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-raetvmzuudiefybcm2if,task_description,declined
+VisualEditor: Deleting selection does not delete selected list bullet,"**orbit** wrote:
+
+Ah yeah, this is as expected. We're not currently handling adoption of list items into paragraphs. This type of selection + delete will work from a paragraph into another paragraph or a paragraph into heading, but just not for lists yet.",1350672888,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-raetvmzuudiefybcm2if,task_subcomment,NA
+VisualEditor: Deleting selection does not delete selected list bullet,"Sorry I forgot a step!
+
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press: a b Enter c d
+3) Make ""cd"" a list item
+3) With the mouse, select b and c
+4) Press Delete",1350614576,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-raetvmzuudiefybcm2if,task_subcomment,NA
+VisualEditor: Deleting selection does not delete selected list bullet,"**orbit** wrote:
+
+Where is your cursor when you press Delete? I can't think of any circumstance where a single press of Delete should remove 2 characters (ABCD -> AD) as you expected. Also, what browser are you using?",1350587124,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-raetvmzuudiefybcm2if,task_subcomment,NA
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,"The available actions in the link dialog are 3 icon-only buttons (see attachment):
+- ""no parking"" symbol
+- check symbol
+- cross symbol
+
+The difference between ""no parking"" and ""cross"" is not obvious.
+I had to try each to see which one means cancel and which one means ""remove link"".
+
+My point is: Tooltips would be useful here.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350546360,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_description,resolved
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,Merged,1354758675,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_subcomment,NA
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,"Added tooltips to inspector controls.
+Patched in https://gerrit.wikimedia.org/r/37171
+
+Awaiting review.",1354756810,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_subcomment,NA
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,Confirmed as missing.,1350580682,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_subcomment,NA
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,"Created attachment 11204
+screenshot
+
+**Attached**: {F9914}",1350546392,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_subcomment,NA
+VisualEditor: Firefox is not displaying cursor in slugs,"**Author:** `orbit`
+
+**Description:**
+Steps to reproduce:
+Place cursor at the end of a paragraph.
+Hit ""Enter"" to create a new paragraph.
+Cursor is not shown in the new paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350496140,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cvrmtrl6akf6grx2t2dt,task_description,resolved
+VisualEditor: Firefox is not displaying cursor in slugs,Fixed in https://gerrit.wikimedia.org/r/#/c/28401/,1350502148,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-cvrmtrl6akf6grx2t2dt,task_subcomment,NA
+CTRL-X does not remove selected text,"Steps:
+1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Select a word or character
+3) Press CTRL-X or select ""Cut"" in the context menu
+4) Text is copied, but not removed
+
+It guess many Wikimedia editors use cut-paste to reorder information, so it seems like a rather important feature to have.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Linux
+**Platform**: PC",1350437460,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-7oxigo4kmioch62jccio,task_description,resolved
+CTRL-X does not remove selected text,"**orbit** wrote:
+
+I found what's happening. This is now fixed but not yet released.",1350455700,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7oxigo4kmioch62jccio,task_subcomment,NA
+CTRL-X does not remove selected text,"**orbit** wrote:
+
+Yeah, it definitely is. I'll look into what happened with our cut support.",1350451005,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7oxigo4kmioch62jccio,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,"Steps:
+1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press: a Enter b Enter c Enter d Enter (that creates 4 paragraphs, each containing a single letter)
+3) With the mouse, select b and c
+4) Press Delete
+5) Wild pawn appears ♙
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=41067",1350379140,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-rw22m4geg4i4wedyx35p,task_description,resolved
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,"Verified.
+
+Test procedure: per comment 5, reporter retested the issue and can't reproduce the bug again.",1350454390,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,I (reporter) confirm it is fixed.,1350451754,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,"**orbit** wrote:
+
+This has been fixed and released to mediawiki.org.",1350450594,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,That's a Firefox issue only.,1350414414,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,"Same with ""Backspace"" instead of ""Delete"" at step 4.",1350379334,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,[ Confirming bug. See also bug 41067. ],1350379291,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,"1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Put your cursor anywhere in the text
+3) Press CTRL+A to select everything
+4) Press Delete
+5) PROBLEM: Nothing happens. No content is removed.
+
+Pressing Backspace instead of Delete works, though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350378600,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-cv2eddejijgeuiyzx5iv,task_description,resolved
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,Fixed here: https://gerrit.wikimedia.org/r/#/c/28790/,1350692324,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-cv2eddejijgeuiyzx5iv,task_subcomment,NA
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,"Okay, thank you to have rechecked.
+
+I guess we should settle on ""Unconsistent behavior selecting all then deleting content"".
+
+[ Confirming bug. ]",1350392100,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-cv2eddejijgeuiyzx5iv,task_subcomment,NA
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,"@Dereckson:
+I just re-tried and you are right.
+I changed the bug's title but can't change the description unfortunately.
+Backspace has the exact same problem, contrarily to what my description was saying.",1350379777,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-cv2eddejijgeuiyzx5iv,task_subcomment,NA
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,"Can't confirm the bug.
+
+I've a different behavior with Firefox 15.0.1: All the content is deleted except a sentence (currently ""Also, there strange chess symbols appear...."").",1350379388,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-cv2eddejijgeuiyzx5iv,task_subcomment,NA
+VisualEditor: Backspace does not work after removing all content,"1) Go to http://www.mediawiki.org/wiki/Special:VisualEditorSandbox with Firefox
+2) Put your cursor anywhere in the text
+3) Press CTRL-A (or select all text with the mouse)
+4) Press ""Backspace"". All content disappears.
+5) Type ""a"".
+6) Press ""Backspace"". Problem: ""a"" is not removed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350378480,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-4ygvi66vjgjggrrbm2gv,task_description,resolved
+VisualEditor: Backspace does not work after removing all content,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306609,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4ygvi66vjgjggrrbm2gv,task_subcomment,NA
+VisualEditor: Backspace does not work after removing all content,Now fixed in master.,1354217422,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4ygvi66vjgjggrrbm2gv,task_subcomment,NA
+VisualEditor: Backspace does not work after removing all content,"Confirmed on Mac/Firefox too (no issue on Chrome, Safari)",1350403427,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4ygvi66vjgjggrrbm2gv,task_subcomment,NA
+VisualEditor: Backspace in list: deleted character re-appears,"Steps:
+0) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+1) Between two simple text paragraph, insert a new paragraph by pressing ""Enter"".
+2) Click the ""bullet list"" button.
+3) Type ""a"".
+4) Press ""Backspace"". ""a"" is removed, and the next paragraph moves down a bit.
+5) Press ""Backspace"" again.
+6) The ""a"" reappears.
+
+Problems: The move at step 4 and the miracle at step 6.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1350376200,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-esphifhyt57uf6xcfxuh,task_description,resolved
+VisualEditor: Backspace in list: deleted character re-appears,Confirmed the fix in betalabs and test2.,1414444876,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-esphifhyt57uf6xcfxuh,task_subcomment,NA
+VisualEditor: Backspace in list: deleted character re-appears,"**orbit** wrote:
+
+Just leaving a note: This is a Firefox problem where the browser adds a <br _moz_dirty /> within the list item:
+<li>
+  <p></p>
+  <br _moz_dirty/>
+</li>",1350669002,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-esphifhyt57uf6xcfxuh,task_subcomment,NA
+VisualEditor: Backspace in list: deleted character re-appears,"**orbit** wrote:
+
+Yep, this is verified. We should have a fix soon.",1350591670,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-esphifhyt57uf6xcfxuh,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,"Steps:
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Click at the end of any list item
+3) Press Enter
+4) As expected, a new line is created in the list
+5) PROBLEM: This cursor blinks at the beginning of the previous line (the one in which the cursor was before pressing Enter
+6) When I begin typing, the text appears in the new line, so I guess the ""real cursor"" is actually at the right place, but its visualisation is misplaced.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350361740,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-bwuzjaia5wetefisy2ta,task_description,resolved
+VisualEditor: Cursor appears misplaced after adding item to list,I (original reporter) confirm the fix.,1351564499,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,Fixed by this changeset: https://gerrit.wikimedia.org/r/#/c/28401/,1350604430,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,"I think I know what's the issue, please keep assigned to me.",1350414315,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,Assigning to Christian given his heroic work on this last night.,1350402366,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,"**orbit** wrote:
+
+Appears to be a Firefox thing (this is a note to myself for later).",1350377911,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,"About step 5:
+Also, it only blinks once.
+In some cases it does not blink at all (invisible), but that is a different problem.",1350361928,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: SHIFT-LEFT deletes text in lists,"Steps to reproduce:
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press ""Edit""
+3) Click at the end of any item in a list
+4) Press SHIFT and LEFT, maintaining them pressed for a while
+
+Expected behavior: Text is selected
+Actual behavior: Text is deleted, leaving only some fragments near the bullets
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1350356940,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-2z4m5xpg5gzvx6kbldfe,task_description,resolved
+VisualEditor: SHIFT-LEFT deletes text in lists,"I (original reporter) I confirm the fix, great work :-)",1350437137,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-2z4m5xpg5gzvx6kbldfe,task_subcomment,NA
+VisualEditor: SHIFT-LEFT deletes text in lists,"**orbit** wrote:
+
+This is happening in Firefox and has been fixed. The patch should appear on mediawiki.org 10/16.",1350377650,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2z4m5xpg5gzvx6kbldfe,task_subcomment,NA
+VisualEditor: Pasting text doesn't work,"I'm testing on mediawiki.org but am creating a bug report since these haven't been mentioned before so I don't believe they've been fixed in git.
+
+If I try to paste some text in the editor, the paragraphs in it get stuck together, and it gets '↵' character inserted periodically, at places not corresponding to any line breaks in the text. Example:
+
+If you want your user to be able to configure your extension, you'll ↵need to provide one or more configuration variables. It is a good idea ↵to give those variables a unique name. They should also follow MediaWiki↵ naming conventions
+
+This happens both with pasting with Ctrl+v and with mouse. Firefox 16.0.1 on Windows XP SP 2.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350339660,PHID-USER-asiusr6cw73okn35tobw,PHID-TASK-47tdq27eh5j4qgr4lw5p,task_description,resolved
+VisualEditor: Pasting text doesn't work,"**orbit** wrote:
+
+Thanks for the additional detail. I found the problem and have committed a fix (https://gerrit.wikimedia.org/r/#/c/28628/). 
+
+Since we don't have a HTML -> Linear Model converter, copy and paste from external sources will paste as plain text only, so the 3 paragraphs will end up collapsed. This is as-expected. There is another enhancement request (https://bugzilla.wikimedia.org/show_bug.cgi?id=33105) to better support pasting from external sources.",1350601375,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-47tdq27eh5j4qgr4lw5p,task_subcomment,NA
+VisualEditor: Pasting text doesn't work,"I am copying the first three paragraphs from http://www.mediawiki.org/wiki/Manual:Developing_extensions#Making_your_extension_user_configurable (starting with ""If you want your user to be able to configure"" and ending with ""configuration variables in your installation notes."") I am pasting by clicking in VisualEditor at the end of ""answers to many of your questions."" paragraph and pressing Ctrl+V.
+
+If I paste the text in a text editor, and then copy that text and paste it in the VisualEditor, the paragraphs are merged together (with an empty string) but the '↵' character does not appear.
+
+This also happens with Firefox 11.0 on Ubuntu 10.10. It does not happen with Opera 11.50 on Ubuntu 10.10.",1350459248,PHID-USER-asiusr6cw73okn35tobw,PHID-TASK-47tdq27eh5j4qgr4lw5p,task_subcomment,NA
+VisualEditor: Pasting text doesn't work,"**orbit** wrote:
+
+I can't reproduce this on Firefox. Can you give me more details about the type of content you're pasting and where you're pasting it? For example, ""I'm copying a couple paragraphs from a normal HTML page and pasting it into a headline in the Visual Editor"".",1350450930,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-47tdq27eh5j4qgr4lw5p,task_subcomment,NA
+There's no way to specify the directionality of a paragraph,"In MediaWiki pages it is frequently required to write a paragraph in a different
+language, and possibly also with different directionality. For example, a
+quotation in English in an article in the Hebrew Wikipedia.
+
+With the plain wikitext editor this can be achieved using HTML, for example
+<div lang=""en"" dir=""ltr"">. In some Wikipedias there are templates that do
+this.
+
+There must be a way to do this using the VE GUI. For example, the user can
+select the text in a different language, open a dialog with ""Paragraph language
+properties"" and select ""Language: English"" and ""Directionality: Left-to-right"".
+
+For reference and further details:
+https://www.mediawiki.org/wiki/VisualEditor/Bidirectional_text_requirements
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350148320,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-lldcsju4qcxyd4jmidkt,task_description,resolved
+There's no way to specify the directionality of a paragraph,"
+
+*** This bug has been marked as a duplicate of bug 41009 ***",1350158076,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lldcsju4qcxyd4jmidkt,task_subcomment,NA
+VisualEditor: Disabled toolbar Buttons should not respond to clicks,"screenshot of the problem
+
+When you click a button that is disabled, it still gives you the visual feedback of being pressed.
+
+The screenshot shows me clicking the ""reduce indent level"" button while it is disabled. Note the shadow border that is added when you click it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9583}",1350045780,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-n7gptyps7udhncfic5rt,task_description,resolved
+VisualEditor: Disabled toolbar Buttons should not respond to clicks,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306613,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n7gptyps7udhncfic5rt,task_subcomment,NA
+wikibugs-l@ does not follow all products/components,"Not sure how the exact scope of wikibugs-l@ is defined (which products/components it is expected to cover) and what the expectations of people watching wikibugs-l@ in Bugzilla are, but wikibugs-l@ is NOT subscribed to ALL components/products.
+
+After spending 20min of investigating:
+
+Product level:
+To get bugmail for any changes in the products Cortado, Datasets, Huggle, mwEmbed, Parsoid, (Security,) VisualEditor, the only chance is to follow the default assignee listed on https://bugzilla.wikimedia.org/describecomponents.cgi . But that also means receiving all other bugmail created by her/him no matter which product the changes were made in.
+
+Components level:
+Several components in the ""MediaWiki extensions"" product that don't have the Default Assignee set to wikibugs-l@ do not always have wikibugs-l@ at least in the default CC list.
+Same for ""VIAF"" and ""WM-Bot"" components in the ""Tools"" product.
+Same for ""lucene-search-2"" and ""Prototype server"" components in the ""Wikimedia"" product.
+Same for ""bots"" in ""Wikimedia Labs"".
+
+
+(Fixing bug 37105 would be a different approach to solve part of the problem.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350032400,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gxlesrzwrsipkfsxba4o,task_description,resolved
+wikibugs-l@ does not follow all products/components,"(In reply to comment #2)
+> You do realise that it was already setup as a Global Watcher in the email
+> config?
+
+Then something's broken. I do not get all bugmail always.
+
+I watch wikibugs-l@, I just commented on bug 22816, I didn't receive bugmail, because wikibugs-l@ is default assignee for that component, but that specific report had a non-default assignee. That means wikibugs-l@lists.wikimedia.org must still also be set as default CC to trigger bugmail.",1353163615,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gxlesrzwrsipkfsxba4o,task_subcomment,NA
+wikibugs-l@ does not follow all products/components,"Darrn, of course I didn't (plus I had the vague feeling of missing out on some bugmail). That address was in the default CC of quite some components, but I shouldn't assume that people clean up duplications. :)",1350049808,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gxlesrzwrsipkfsxba4o,task_subcomment,NA
+wikibugs-l@ does not follow all products/components,You do realise that it was already setup as a Global Watcher in the email config?,1350048728,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-gxlesrzwrsipkfsxba4o,task_subcomment,NA
+wikibugs-l@ does not follow all products/components,Fixed. Now wikibugs-l@ should really report ALL changes to ANY bug reports (except for Security and deprecated products that are not open to new reports).,1350036846,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gxlesrzwrsipkfsxba4o,task_subcomment,NA
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new","Right now the ""This is a [minor edit]"" text in the save dialog tries to take the user to a new page in the current context, prompting them to abandon their changes (or not leave). This is sub-optimal. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1349379660,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jykflci4lybdcwkdegx7,task_description,resolved
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new",Note which milestone this met.,1355171026,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jykflci4lybdcwkdegx7,task_subcomment,NA
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new",Merged.,1354758513,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jykflci4lybdcwkdegx7,task_subcomment,NA
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new",Changed to target=_blank,1354752982,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-jykflci4lybdcwkdegx7,task_subcomment,NA
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new","Funny enough, in the current edit mode the minor edit link takes you away from editing.   AFAIK, the taget attribute cannot be added to a link wikitext.  Solution is to open the minor edit page in a new tab by setting target: _new with jQuery.
+
+Patch in https://gerrit.wikimedia.org/r/37154",1354751276,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-jykflci4lybdcwkdegx7,task_subcomment,NA
+VisualEditor: Inline switching of styling mode does not correctly updating typed text when @EOL,"This is a bug in the functionality implemented for bug 33140
+
+Platform: Safari 6, Mac Mountain Lion
+
+Insert cursor after the . of the Note in the lede of the VisualEditor:Test page (end of line).
+
+Now press ctrl-b
+type: text is in bold
+Press ctrl-b again
+type: new text is STILL in bold, but should be non-bold
+Press ctrl-b again
+type: The previous block is rerendered to be non-bold and the new text is rendered as bold.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1349371140,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-zlrtgjuxyb4v4l2qepry,task_description,declined
+VisualEditor: Inline switching of styling mode does not correctly updating typed text when @EOL,"**orbit** wrote:
+
+I can't reproduce this. Additional work has been done on insertAnnotations, so this was likely only a bug for a day or so. Please re-open and provide more information if I'm incorrect.",1350000478,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zlrtgjuxyb4v4l2qepry,task_subcomment,NA
+VisualEditor: Selection is wrongly restored on undo,"Steps to re-create:
+* Go to a new page, insert the word ""Fascinating""
+* Select it (double-click, click-drag or select-all)
+* Press a list button, and then undo
+
+What happens: The word ""Fascinating"" de-lists; the selection is set to ""scinati"".
+ 
+What should happen: The word ""Fascinating"" de-lists; the selection is set to ""Fascinating"".
+ 
+* Again, press a list button, and then undo
+
+What happens: The word ""Fascinating"" de-lists; the selection is set to ""ina"".
+ 
+What should happen: The word ""Fascinating"" de-lists; the selection is set to ""scinati"".
+ 
+* Again, press a list button, and then undo
+
+What happens: The word ""Fascinating"" de-lists; the selection appears to have disappeared.
+ 
+What should happen: The word ""Fascinating"" de-lists; the selection is set to ""ina"".
+
+Etc. :-) 
+
+Rob suggested that it was likely an issue in Transaction Builder?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348700340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dzuii7n6goxb7ffjhlad,task_description,resolved
+VisualEditor: Selection is wrongly restored on undo,Noting bugs closed in the 2012-10-15 release.,1351534203,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dzuii7n6goxb7ffjhlad,task_subcomment,NA
+VisualEditor: Selection is wrongly restored on undo,Fixed in latest deployment.,1350326683,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dzuii7n6goxb7ffjhlad,task_subcomment,NA
+labs-nfs1 full again,"[ve-roundtrip2] ~ $ sudo du -sh /home/ori
+16M	/home/ori
+[ve-roundtrip2] ~ $ sudo df -h /home/ori
+Filesystem                               Size  Used Avail Use% Mounted on
+labs-nfs1:/export/home/visualeditor/ori   18G   17G     0 100% /home/ori
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348169460,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-rwdzpvdya3fyeweyik45,task_description,resolved
+labs-nfs1 full again,We cleaned up some space. I'm going to be moving this to gluster soon.,1348180945,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-rwdzpvdya3fyeweyik45,task_subcomment,NA
+VisualEditor: Creating a link over-writes any existing annotations on the text,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348000500,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qwmhk54ep4zitmtvbaik,task_description,resolved
+VisualEditor: Creating a link over-writes any existing annotations on the text,Regression fixed in https://gerrit.wikimedia.org/r/24643,1348271354,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-qwmhk54ep4zitmtvbaik,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"Assuming we implement bug 39558. That means the counter in the corner of the save dialog will be decreasing more than 1 per character on average.
+
+English users will likely not notice it as quickly, but € (EURO SYMBOL) for instance is 3 bytes. And in foreign languages it will be more common entirely.
+
+Right now the counter has no unit, which would be confusing (the natural expectation is to assume character count). We can add a unit word ""# bytes"" instead. But I'm not sure that is an improvement, do we want to face users with that?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=4715",1346892540,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7vr2tsadkbk7lzyzolas,task_description,resolved
+VisualEditor: Edit summary length counter confusing when in bytes,Merged and to be deployed in wmf12 train.,1347900984,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"(In reply to comment #2)
+> Appending "" bytes"" seems like a reasonable compromise here (though the i18n
+> will be fun).
+
+I've -1-ed the patch mentioned in comment 3 for not being understandable to users. We should provide them with a reasonable indication of how many more characters they can insert.
+
+Is it possible to do something with the average number of bytes per character for what's already been typed, and give an indication like ""~n characters remaining""?
+
+P.s. issue should be closed when patch is merged, not when it's submitted.",1347392907,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"Went with bytes for the time being.  Will change when core bug fixed.
+Patched in https://gerrit.wikimedia.org/r/23451",1347392179,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"Appending "" bytes"" seems like a reasonable compromise here (though the i18n will be fun).",1346949530,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"Note that this is a consequence of bug 4715. Right now we just cut off the comment if it is too long; adding a confusing, but correct counter helps a lot.
+
+Now to the question: I think adding the word ""bytes"" would help, since (a) some people know what a byte is and (b) even those who don't and see that the counter differs from a character counter may realize that ""bytes"" can mean something else. They probably don't assume it is a character counter if there is an unknown term behind the number and so they have less expectation and get less confused if the counter differs from their expectation.",1346919604,PHID-USER-j27ofmod3h6tzafsujyq,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"Submitting the form on Enter in the current UI goes against all expectations.
+
+It is hardcoded in the javascript to override the default behavior (browsers are actually quite sane in this case and know not to auto-submit from a textarea because that's bad).
+
+Either make it not a text area or make it not submit on Enter.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52133",1346892300,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-khmajutgdejtygs4iuzr,task_description,resolved
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"(In reply to comment #5)
+> Maybe, maybe not. Either way, that's a separate request.
+> [...]
+> If you want, file a separate ticket to turn it into a single-line text input.
+
+bug 52133",1374903726,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"(In reply to comment #4)
+> Do we really need a textarea?
+> 
+> Newlines are not shown in page history.
+
+Maybe, maybe not. Either way, that's a separate request.
+
+Besides, when it is a text input Enter will submit the form automatically (browser behavior) which is good. So this change had to be made either way. If you want, file a separate ticket to turn it into a single-line text input.
+
+Note that textarea provides another thing besides multi-line: wrapping.
+
+It is much nicer to type a long line in a textarea then a flat input because there is no need to use the horrible scrubbing behavior that browsers have (select-dragging or keyboard arrows only). I've encountered numerous times during usability studies that a user thought the begin of the input was lost when it was no longer visible (there is no visual indication that it is still there, e.g. scroll or whatever). Or that the end was lost (when they focus another element, other elements scroll back to the begin).",1347383752,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"Do we really need a textarea?
+
+Newlines are not shown in page history.",1347381643,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"No, previously it was a text input.
+Patched in https://gerrit.wikimedia.org/r/23422",1347381271,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"(In reply to comment #1)
+> Actually, this is exactly the current behaviour of the edit summary box; see
+> bug 38042 and bug 38735 (the last one submitted by you :-)).
+
+Interesting. Was it a textarea back then?",1347374675,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"Actually, this is exactly the current behaviour of the edit summary box; see bug 38042 and bug 38735 (the last one submitted by you :-)).",1346948784,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: By-word selection fails when mouse moves,"Word-by-word text selection by mouse fails as soon as the user moves the mouse.
+
+Examples: If a user double clicks on ""Lorem"" in a ""Lorem ipsum"" string and then moves the mouse to, say, after the letter ""p"", the selected text becomes just ""Lorem ip"", rather than the entirety of both words. If a user double clicks on a word, it becomes entirely highlighted, but if the mouse is moved, the only parts highlighted are the letters between the beginning of the word and the cursor.
+
+The expected behavior is that after the user double clicks, the selection expands/shrinks only word-by-word, with the original selected word always highlighted.
+
+Tested on Chrome on Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1346752740,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-wkopxt22hpjopb4jwgk3,task_description,resolved
+VisualEditor: By-word selection fails when mouse moves,"**orbit** wrote:
+
+This is fixed due to the selection changes from Inez.",1350001255,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wkopxt22hpjopb4jwgk3,task_subcomment,NA
+VisualEditor: By-word selection fails when mouse moves,"**orbit** wrote:
+
+To clarify the steps to reproduce, a user must click-release-click-hold and move the mouse.",1348875034,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wkopxt22hpjopb4jwgk3,task_subcomment,NA
+VisualEditor: UI restores #toc as inline-block instead of table,"Bug in action
+
+When pressing Edit in VE mode, and then aborting (e.g. Parsoid is not running and the page is restored) the table of contents becomes an inline block which looks rather odd.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9671}",1346200560,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_description,resolved
+VisualEditor: UI restores #toc as inline-block instead of table,Fixed in I57532e556eafe783c8638b25fce502a158597c97.,1346830749,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_subcomment,NA
+VisualEditor: UI restores #toc as inline-block instead of table,"@TrevorParscal: .ve-init-mw-viewPageTarget-pageToc uses inline-block, why?",1346239596,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_subcomment,NA
+VisualEditor: UI restores #toc as inline-block instead of table,"(In reply to comment #1)
+> [ Adding design keyword. ]
+
+Why? This is just a javascript issue, there is no design question. It should look like it does on regular page views.",1346239381,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_subcomment,NA
+VisualEditor: UI restores #toc as inline-block instead of table,[ Adding design keyword. ],1346237488,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_subcomment,NA
+"VisualEditor: Annotate the DOM to indicate on round-trip what's changed, so Parsoid can do partial serialisation","Per request of Parsoid team. Not sure if this is already a bug? Apologies if so. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345851360,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z2cdsxjpkxttsbnu4d2x,task_description,resolved
+"VisualEditor: Annotate the DOM to indicate on round-trip what's changed, so Parsoid can do partial serialisation",https://gerrit.wikimedia.org/r/#/c/31990/,1352492599,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-z2cdsxjpkxttsbnu4d2x,task_subcomment,NA
+VisualEditor: DOM out of sync with data model when typing next to a link,"Reproduce by placing cursor just to the right of a link.  Start typing.  Force the node to re-render by changing the formatting to a heading. OR just save the page.  Notice that the new text is now part of the link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345766400,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-h6kkxvcriuqwp7klykw2,task_description,resolved
+VisualEditor: DOM out of sync with data model when typing next to a link,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306612,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h6kkxvcriuqwp7klykw2,task_subcomment,NA
+VisualEditor: DOM out of sync with data model when typing next to a link,This was fixed when I changed how pre-annotations work.,1354217099,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-h6kkxvcriuqwp7klykw2,task_subcomment,NA
+VisualEditor: Link inspector should abridge completion results so users can distinguish multiple very long similar titles,"Proposal is to automatically put the ellipsis in the middle rather than at the end of the string.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345748940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nepuoz3eghdbacybz47v,task_description,resolved
+VisualEditor: Link inspector should abridge completion results so users can distinguish multiple very long similar titles,Already fixed in master.,1347302279,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nepuoz3eghdbacybz47v,task_subcomment,NA
+VisualEditor: Link inspector should abridge completion results so users can distinguish multiple very long similar titles,"I agree, I've been seeing this in other places as well. I can't recall where I saw it but I was using my iPod touch and saw some autocompletion list use ellipsis in the middle and thought it was brilliant.
+
+When using long titles the beginning will be the same, especially knowing that our list will be in alphabetical order (as opposed to search rank or whatever, which is what a search engine's suggestions would/could be) it is very likely and worth optimizing for.
+
+Sounds like a good feature to implement in the jquery.autoEllipsis plugin we maintain in MediaWiki.",1345821017,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nepuoz3eghdbacybz47v,task_subcomment,NA
+Comments break splitting of paragraphs,"See http://parsoid.wmflabs.org/_rt/mw/VisualEditor:Test , and note how ""many of your questions"" and ""Note: The Edit button"" are on the same line, while they're really supposed to be in separate paragraphs.
+
+Basically, what's going on here is that the wikitext:
+
+Foo
+<!-- Comment -->
+
+Bar
+
+is turned into this HTML:
+<p>Foo
+<!-- Comment -->
+
+Bar</p>
+
+while really the correct output is this:
+<p>Foo</p>
+<!-- Comment -->
+
+<p>Bar</p>
+
+This results in the page rendering as ""Foo Bar"" rather than ""Foo [paragraph break] Bar"", and of course that means the way the editor renders it and lets you edit it is wrong as well.
+
+What's maybe even scarier is that this round-trips ""correctly"", i.e. the wikitext->HTML conversion is wrong, but then the HTML->wikitext conversion is wrong in exactly the reverse way, and that causes it to round-trip. I suspect this is because of the presence of the newlines in the HTML, but that's also a bug: ideally the serializer shouldn't convert a single <p> to wikitext representing multiple paragraphs, regardless of newlines (this is very unlikely to be a practical problem for VE though).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345593360,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-g6mdoxrevyqbrazocz2q,task_description,resolved
+Comments break splitting of paragraphs,"Fixed in https://gerrit.wikimedia.org/r/#/c/24502/3
+Also, added a test to mediawiki/core parserTests.txt",1348260388,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-g6mdoxrevyqbrazocz2q,task_subcomment,NA
+VisualEditor: Select all then replace causes first character to be swallowed in Heading mode,"To reproduce:
+
+Go to a blank VisualEditor page, click edit, change entry mode to Heading 1 (or whichever Heading mode), select all (Ctrl-A or Cmd-A), type in 'Abc'.
+
+The 'A' will appear, then be replaced by the 'b'; the 'c' appears normally.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345502760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpx6sqi7fes7jlx6flt4,task_description,resolved
+VisualEditor: Select all then replace causes first character to be swallowed in Heading mode,"**orbit** wrote:
+
+
+
+%%%*** This bug has been marked as a duplicate of bug 39465 ***%%%",1345502985,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kpx6sqi7fes7jlx6flt4,task_subcomment,NA
+VisualEditor: Annotated content stripped from an LI on save,"See: https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=574056&oldid=574055
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1345492260,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nhi52laxjrwxyxxoh46r,task_description,resolved
+VisualEditor: Annotated content stripped from an LI on save,Already fixed in master.,1347302507,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nhi52laxjrwxyxxoh46r,task_subcomment,NA
+VisualEditor: Annotated content stripped from an LI on save,Submitted a fix in https://gerrit.wikimedia.org/r/20818,1345493741,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nhi52laxjrwxyxxoh46r,task_subcomment,NA
+VisualEditor: Link inspector should cache completion results,"If I type ""T"", then ""Te"", then press backspace, the link inspector will request suggestions for ""T"" for the second time. Instead, it should cache these results.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345484760,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-r2i2uzlqlwknth3ox5rg,task_description,resolved
+VisualEditor: Link inspector should cache completion results,Fixed in https://gerrit.wikimedia.org/r/#/c/20915/,1345571007,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-r2i2uzlqlwknth3ox5rg,task_subcomment,NA
+VisualEditor: Selecting all text and typing causes first typed character to be deleted,"To reproduce:
+
+1. Select all text in document (ctrl/cmd+a)
+2. Start typing a word
+3. Notice that the first character of the word disappears
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345239480,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-nnvtoxoopp6h7zbzqq7s,task_description,resolved
+VisualEditor: Selecting all text and typing causes first typed character to be deleted,"**orbit** wrote:
+
+This is fixed due to the work that Inez has done with slug replacement.",1350001011,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnvtoxoopp6h7zbzqq7s,task_subcomment,NA
+VisualEditor: Selecting all text and typing causes first typed character to be deleted,"**orbit** wrote:
+
+%%%*** Bug 39517 has been marked as a duplicate of this bug. ***%%%",1345502985,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnvtoxoopp6h7zbzqq7s,task_subcomment,NA
+VisualEditor: Selection issues re-write,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344882780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rh7iz42inbmpgpuz2l7u,task_description,resolved
+VisualEditor: Selection issues re-write,[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343641,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rh7iz42inbmpgpuz2l7u,task_subcomment,NA
+VisualEditor: Selection issues re-write,Selection re-write is now complete; closing this as now done.,1354812178,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rh7iz42inbmpgpuz2l7u,task_subcomment,NA
+VisualEditor: JS error after saving document,"Open a document in the editor, change something, then save it. The following JS error appears in my console after saving:
+
+TypeError: $editorDocument.children("".ve-ce-branchNode:last"").offset() is null
+[Break On This Error] 	
+
+$editorDocument.children( '.ve-ce-branchNode:last' ).offset().top
+
+ve.Surface.js (line 184)
+
+
+Observed in Firefox 14.0.1.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344637500,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bodj4j2hdcdjgi2sbtmy,task_description,resolved
+VisualEditor: JS error after saving document,"No longer occurs in either Firefox or Chrome. Given how much we've re-written this code, not surprising, really. :-) Marking as fixed.",1354812033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bodj4j2hdcdjgi2sbtmy,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"Go to http://localhost:8000/_rtform/ and enter ""<br>""; it'll round-trip to ""<br />""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344466200,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_description,resolved
+Self-closing tags without trailing slash do not round-trip correctly,"Closing this bug for now, semantically insignificant whitespace is tracked by bug 39564.",1345656284,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"We need clean diffs, but there are different ways to get them, with different cost/benefit ratios. Tracking all semantically insignificant whitespace in rt information looks like a sure way to add a lot of bloat. Selective serialization of modified DOM parts on the other hand seems to offer a better cost/benefit ratio.
+
+The only downside of selective serialization I see is that it adds a burden on clients to mark modified parts of the DOM.",1345649522,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"This insignificant whitespace issue is broader than self-closing tags.  Worth closing this ticket and opening a new one to discuss that.
+
+For example, try this:
+
+""<div    style='color:red;'>foo</div>""
+
+The excess white space is lost.  While I am inclined to dismiss this issues as insignificant and as a case where dirty diffs are acceptable, I am also sensing the tension in the air around WMF projects.  So, maybe this is not such an insignificant issue after all.  Using selective serialization, we can for sure address all these newline, whitespace, etc. issues, and it is worth discussing how soon we should enable that.  As Gabriel noted, it will also eliminate a lot of the wikitext state we carry around in the DOM.
+
+But, the serializer also ought to be complete in and of itself, and so this question will rear its head in that context again.
+
+My personal inclination is to ignore this issue because supporting this consistently will mean essentially recognizing non-normalized-whitespace/newline scenarios and carrying diff-state in the DOM.  But, we will probably be doing this only to satisfy a requirement of perfect round-tripping which IMO is unreasonable/unrealistic.
+
+This might be one issue where it is worth bringing in the editor community into the discussion so we can make a more reasonable decision that everying can be happy with.",1345648752,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"We generally don't try to preserve insignificant whitespace inside HTML tags yet, and it is debatable if this would be worth it. The main reason for going to the length we currently do for full-serialization round-tripping is to simplify our own testing (so that we can use a simple text diff). In the longer term, selective serialization based on the editor's change annotations should provide the better bang for the buck. We might well remove some of the elaborate round-trip information we currently collect once that is enabled and a way to systematically ignore some rt differences is found.",1345599858,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"This is not quite fixed yet, because now ""<br />"" round-trips to ""<br/>"", see http://parsoid.wmflabs.org/_rt/mw/VisualEditor:Roadmap",1345593703,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"Boom, merged. Gettin' it done.",1344965167,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,Complete list of void elements submitted for review in https://gerrit.wikimedia.org/r/18697. Verified to preserve slash for hr as well.,1344636623,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"'img' tags are not normally allowed in wikitext, and are stripped out by the sanitizer. 'hr' tags should be allowed, just need to be added to the list of empty tags.",1344632214,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"This fix was merged, but there were notes about '<hr>' and '<img>' as well. I tried to get those to work, but something happens to '<img>' tags before they get to the serializer, and I'm not entirely sure where.",1344628975,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,Fix pushed for review in https://gerrit.wikimedia.org/r/#/c/18202/,1344471929,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+VisualEditor: Round-tripping of double apostrophes causes them to be interpreted as wikitext,"Repro:
+
+1. Go to http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&action=edit&oldid=569294 , save, then edit it with VE
+2. Insert '' in the word ""link"", save. diff: http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&diff=569295&oldid=569294
+3. Edit it with VE again, select ""li''nk"", and make it italic, save. diff: http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&diff=next&oldid=569295
+4. So many unexpected quotes
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1344201240,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-3vh3dwgpiyxwl4qobayn,task_description,resolved
+VisualEditor: Round-tripping of double apostrophes causes them to be interpreted as wikitext,"This is fixed in production in that it doesn't introduce the excess quotes any more, see https://www.mediawiki.org/w/index.php?title=VisualEditor%3ABug39058&diff=571888&oldid=571887 . It still adds <span> tags though, but that's fixed on master.
+
+On my localhost, the diff I get is as follows, and I think that's perfectly reasonable:
+
+− '''This is a te<nowiki>''</nowiki>st page for bug 35058.'''
++ '''This is a ''te<nowiki>''</nowiki>st'' page for bug 35058.'''",1344908105,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3vh3dwgpiyxwl4qobayn,task_subcomment,NA
+Parsoid does not handle urlencoded interwiki prefixes correctly,"http://localhost:8000/localhost:VisualEditor:Foo works and parses VisualEditor:Foo on localhost
+
+http://localhost:8000/localhost:VisualEditor%3AFoo works too
+
+http://localhost:8000/localhost%3AVisualEditor%3A Foo does not work, it doesn't recognize the interwiki prefix, falls back to the default interwiki (mw:), and tries to parse [[mw:Localhost:VisualEditor:Foo]].
+
+Debugging shows that in the ""Regular article parsing"" callback on line 397, req.params is set to [ undefined, 'localhost:VisualEditor:Lists' ], whereas if the colons aren't urlencoded it's [ 'localhost', 'VisualEditor:Lists' ]. It looks like app.get()'s regex mode isn't processing urlencoded characters correctly even though it does unescape the matches before putting them in req.params.
+
+This is obviously a blocker for making VisualEditor always use an interwiki prefix.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343793720,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jzxawxvcg5luenehopjn,task_description,resolved
+Parsoid does not handle urlencoded interwiki prefixes correctly,Mass-moving bugs into the new 'Parsoid' product.,1344281149,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jzxawxvcg5luenehopjn,task_subcomment,NA
+Parsoid does not handle urlencoded interwiki prefixes correctly,I don't really see the need to urlencode the colon since it is plain ASCII (browsers don't do so evidently). I have added support for this nevertheless since it was easy to do: https://gerrit.wikimedia.org/r/#/c/17331/,1343853258,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jzxawxvcg5luenehopjn,task_subcomment,NA
+VisualEditor: UserAgent blacklisting (using jQuery.client?),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1343672940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hlm32lc3bwvjx3khjhox,task_description,resolved
+VisualEditor: UserAgent blacklisting (using jQuery.client?),"Resolved in I6ebb3f7a7d56d395e5fe5c7c9129b606f97aeaab
+
+Use ?vewhitelist to activate it on blacklisted browsers. This is superior to using debug mode because it can be used to diagnose problems that occur in and out of debug mode.",1345671208,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-hlm32lc3bwvjx3khjhox,task_subcomment,NA
+VisualEditor: UserAgent blacklisting (using jQuery.client?),Proposal that if debug=true then suspend this so that you can test in any browser.,1343673005,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hlm32lc3bwvjx3khjhox,task_subcomment,NA
+"VisualEditor: ""edit source"" link on oldid=foo should pass on the revision in the GET when going to action=edit, even though veaction=edit doesn't support it yet.","Right now we can't use VE on an old-id page due to Parsoid lacking the feature yet, but we could at least make the edit-source link work when users are looking at an old revision. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343424780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ybjzemdynryfg4brsgpi,task_description,resolved
+"VisualEditor: ""edit source"" link on oldid=foo should pass on the revision in the GET when going to action=edit, even though veaction=edit doesn't support it yet.","
+
+*** This bug has been marked as a duplicate of bug 38125 ***",1343674164,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ybjzemdynryfg4brsgpi,task_subcomment,NA
+VisualEditor: round-trip inline styles,"Input:
+
+This is an <span style=""background: red; color: white; font-weight: bold;"">Inline element</span>.
+
+This sentence contains '''wikitext bold''' and <b>html bold</b>, <strong>html strong</strong> and <span style=""font-weight: bold;"">inline style bold</span>.
+
+Output:
+
+This is an <span>Inline element</span>.
+
+This sentence contains '''wikitext bold''' and '''html bold''', <strong>html strong</strong> and <span>inline style bold</span>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343347860,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-od4vkgjhilutsh6eoi2o,task_description,resolved
+VisualEditor: round-trip inline styles,This was fixed last week in https://gerrit.wikimedia.org/r/#/c/18421,1345054334,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-od4vkgjhilutsh6eoi2o,task_subcomment,NA
+VisualEditor: round-trip inline styles,"This is a DM problem, attributes for text style annotations are not currently preserved. Will be fixed in my annotation API rewrite that I'm starting now.",1343348008,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-od4vkgjhilutsh6eoi2o,task_subcomment,NA
+VisualEditor: Round-trip <b> should not become '''syntax''',"Can not reproduce on parsoid.wmflabs.org but not sure which version runs where, so reporting as reminder to confirm that it is fixed once deployed on MediaWiki.org as well.
+
+Input:
+This sentence contains '''wikitext bold''' and <b>html bold</b>, <strong>html strong</strong>.
+
+Output:
+This sentence contains '''wikitext bold''' and '''html bold''', <strong>html strong</strong>.
+
+
+Example: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ADoom&diff=565804&oldid=565802
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=38738",1343347800,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-sofl3tiyrxpjkqmu6grn,task_description,resolved
+VisualEditor: Round-trip <b> should not become '''syntax''',"(In reply to comment #1)
+> This is a data model problem: Parsoid is giving us round-trip attributes but
+> the converter isn't preserving them. Same root cause as bug 38738
+Fixed, see bug 38738",1345054496,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sofl3tiyrxpjkqmu6grn,task_subcomment,NA
+VisualEditor: Round-trip <b> should not become '''syntax''',This is a data model problem: Parsoid is giving us round-trip attributes but the converter isn't preserving them. Same root cause as bug 38738,1343347978,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sofl3tiyrxpjkqmu6grn,task_subcomment,NA
+VisualEditor: Modify the Parsoid <-> DM converter to handle newlines properly,"* New lines after headlines are being stripped
+* New lines after lists are being stripped
+* New lines after tables are being stripped
+* New lines after <gallery> tags are being stripped
+
+
+Example: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ADoom&diff=565804&oldid=565802
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343347620,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lrcob3z2uqlumi23wzcg,task_description,resolved
+VisualEditor: Modify the Parsoid <-> DM converter to handle newlines properly,This was done a while ago. The main commits were https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=commit;h=63e6702c523614786f75f3ab2b4a1ddcc67b44c7 and https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=commit;h=452c759914aa29c6e7974f17c4bba63a9f010c9c,1347302350,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lrcob3z2uqlumi23wzcg,task_subcomment,NA
+VisualEditor: Modify the Parsoid <-> DM converter to handle newlines properly,"Gabriel, Trevor and I are gonna come up with a plan for newlines next week. Will need some Parsoid tweaks and DM changes.",1343347827,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lrcob3z2uqlumi23wzcg,task_subcomment,NA
+VisualEditor: Pressing Enter/Return in the edit summary input field should trigger submission,"As the title says. Tried on MediaWiki.org
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343347500,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-okkhp45bypa46o6v5bzh,task_description,resolved
+VisualEditor: Pressing Enter/Return in the edit summary input field should trigger submission,"
+
+*** This bug has been marked as a duplicate of bug 38042 ***",1343347540,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-okkhp45bypa46o6v5bzh,task_subcomment,NA
+VisualEditor: Table roundtripping is completely tripped up,"Several issues:
+
+* Ghost <nowiki></nowiki> tag pairs appearing
+
+* Syntax being normalized
+
+ 1)
+  ! foo !! bar !! baz
+  becomes
+  ! foo
+  ! bar
+  ! baz
+
+  Both are the same but should roundtrip if possible.
+
+ 2)
+  Row separators
+  {|
+  |-
+  ! foo
+  |-
+  | bar
+  |-
+  |}
+  becomes:
+
+  {|
+  ! foo
+  |-
+  | bar
+  |}
+
+  Although the first and last separator (|-) are optional, they should roundtrip
+  if possible.
+
+ 3) Syntax being broken due to new line insertion
+  ! foo !! bar !! baz
+  becomes:
+  ! foo
+  !! bar
+  !! baz
+
+  This is not just syntax appearance, this is actually broken. Because of the new lines, the output of 3) is actually difference, because it will display the second exclamation mark of each heading.
+
+
+
+Example: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ADoom&diff=565804&oldid=565802
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343347320,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hpovu36fcfgevlvacc57,task_description,resolved
+VisualEditor: Table roundtripping is completely tripped up,"Whatever caused this, it's fixed now. I just edited the VisualEditor:Doom page, which still has the same table on it, and the diff isn't dirty.",1352492777,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hpovu36fcfgevlvacc57,task_subcomment,NA
+VisualEditor: Table roundtripping is completely tripped up,This round-trips just fine when tested at http://parsoid.wmflabs.org/_rtform/. Looks like a known VE data model issue which causes round-trip attributes to be lost. Same root issue as bug 38738.,1343349837,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-hpovu36fcfgevlvacc57,task_subcomment,NA
+[Regression] VisualEditor: Down arrow in the inspector icon is mis-aligned.,"Due to the change[1] to arrow-down.png recently, the inspector icon was broken. The padding inside the image is very specific for the drop-down menu. The inspector-triggering icon however, does not need this padding and is mis-aligned as a result of that.
+
+
+[1] Change: Ib09a2a20b1 | https://gerrit.wikimedia.org/r/16218
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343176200,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4dujg5dey76ud6rkyyfy,task_description,resolved
+[Regression] VisualEditor: Down arrow in the inspector icon is mis-aligned.,Fixed in https://gerrit.wikimedia.org/r/16590,1343180029,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-4dujg5dey76ud6rkyyfy,task_subcomment,NA
+VisualEditor: User should be able to select text in the save dialog.,"The user-select: none; style from the ve-toolbar is cascading down into the save dialog, causing issues.
+
+Steps to reproduce:
+* View https://www.mediawiki.org/wiki/VisualEditor:Test
+* Change some text
+* Press ""Save page""
+
+Unexpected result:
+Users can't select/highlight any text inside the Save page dialog. In Chrome users can at least still select text inside the input field, though in Firefox it applies to form elements as well.
+
+If possible, the easiest fix would be to override user-select inside this save dialog and undo the ""none"" value. But its possible that that isn't possible (just like like display: block; doesn't do anything if an ancestor is display: none;).
+
+Otherwise it may have the be re-arranged to not be inside an element with class ve-toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343174820,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cxydx5rlo2r5gmbuelnf,task_description,resolved
+VisualEditor: User should be able to select text in the save dialog.,"There are issues in Firefox with overriding user-select properties.  Fix involves attaching the save dialog to the toolbar wrapper rather the toolbar itself.
+
+Patch in https://gerrit.wikimedia.org/r/16760",1343329073,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-cxydx5rlo2r5gmbuelnf,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"Screenshot of the white box overlapping regular text while using the editor
+
+From time time to time a white square appears in the editor, overlaying/masking part of the text.
+
+It can appear both when clicking/typing, as well as when selecting text. In the latter case it is even more visible due to the blue selection being interrupted by the box.
+
+Debugging tells me it is the idle iframe idling in the bushes, pretending to be hidden.
+
+Steps to reproduce:
+* Open https://www.mediawiki.org/wiki/VisualEditor:Test in Chrome 20 (Mac)
+* Switch to ""Edit"" mode
+* Select a word in the editor
+* Bolden it
+* Click ""Save Page""
+
+Unexpected result:
+* White box appears where the word was selected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9946}",1343172780,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4q4qvm4gto65caiusmb3,task_description,resolved
+VisualEditor: White box syndrome strikes back!,"Correction, when inspecting the iframe in the DOM, it is blue.   The issue has seemed to have vanished as Trevor and I were unable to reproduce it. 
+
+Set height and width to 0 for good measure.
+https://gerrit.wikimedia.org/r/21205",1345747417,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,It's blue this time!! I'll take a shot at it.,1345739767,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"I made an attempt to resolve it, but it caused the same old issue in FireFox as always.
+
+I7a69bac66c66ca1c0910f4adfda9a37cdac6f030",1345673987,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"The box ain't white this time, but it's stealing my clicks!",1345673925,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"I am still unable to reproduce this in Chrome 20 and 22.
+Though, hopefully is fixed by setting visibility hidden.
+Patched in https://gerrit.wikimedia.org/r/16663.",1343245501,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"Though the iframe has width: 0; height: 0;, Chrome does not allow
+zero-dimensioning an iframe.
+
+Firefox has issues with display: none; (doesn't load it until it is in the
+flow).
+
+Initial testing shows that visibility: hidden; may be an outcome. Because that
+makes it part of the flow, without being visible. Add that to the fact that it
+is absolutely positioned, and it is basically not in the flow at all.",1343173105,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"Created attachment 10886
+Screenshot of the white box overlapping selected text in the editor
+
+**Attached**: {F9947}",1343172827,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: Bold and Italic UI buttons need to be internationalisable,"The Bold and Italic buttons say ""B"" and ""I"". Some languages can have different letters there; for example, Italian has ""G"" and ""C"" and German has ""F"" and ""K"".
+
+The corresponding buttons in the WikiEditor extension can be localized, but not in Visual Editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342883880,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-lj5fifjrup6bhxud572h,task_description,resolved
+VisualEditor: Bold and Italic UI buttons need to be internationalisable,Now merged into master.,1359765195,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lj5fifjrup6bhxud572h,task_subcomment,NA
+VisualEditor: Bold and Italic UI buttons need to be internationalisable,Fixed in gerrit 46863.,1359759302,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lj5fifjrup6bhxud572h,task_subcomment,NA
+VisualEditor: Bold and Italic UI buttons need to be internationalisable,"Assigning to current milestone, as it's been sitting around for five months untouched at this point.",1357601193,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lj5fifjrup6bhxud572h,task_subcomment,NA
+"VisualEditor: ""Undo"" and ""Redo"" buttons must be flipped for RTL environments","""Undo"" and ""Redo"" buttons must be flipped for RTL environments. Undo must point right and Redo must point left.
+
+The same images can be used, but they must be swapped.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342869480,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ss7w322z7ikgu5wkin5c,task_description,resolved
+"VisualEditor: ""Undo"" and ""Redo"" buttons must be flipped for RTL environments",Patch in https://gerrit.wikimedia.org/r/#/c/23478/,1347407456,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-ss7w322z7ikgu5wkin5c,task_subcomment,NA
+"VisualEditor: ""Bulleted list"" and ""Numbered list"" buttons in the editing toolbar must be reversed in RTL wikis","This bug is almost the same as Bug 28544 in WikiEditor :)
+
+The buttons ""Bulleted list"" and ""Numbered list"" must be mirrored in RTL wikis.
+
+The numbers in ""Numbered list"" in languages he, yi, arc and dv should look like
+regular Western numbers - not mirrored.
+
+In languages written in the Arabic alphabet (ar, fa, ur, ps, mzn etc.)
+[[Eastern Arabic numerals]] can be written there, but maybe Western numbers
+are OK, too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342869360,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dbjwk2354ghy4uqtyvgu,task_description,resolved
+"VisualEditor: ""Bulleted list"" and ""Numbered list"" buttons in the editing toolbar must be reversed in RTL wikis",Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306606,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dbjwk2354ghy4uqtyvgu,task_subcomment,NA
+"VisualEditor: ""Bulleted list"" and ""Numbered list"" buttons in the editing toolbar must be reversed in RTL wikis",This was resolved a while ago when the icons were redone.,1354216837,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-dbjwk2354ghy4uqtyvgu,task_subcomment,NA
+VisualEditor: down arrow in drop-down menu in RTL interface overlaps with the text,"Configure the user language to be Hebrew. Try to edit a page. The down arrow in format selection drop-down menu will overlap with the text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342866000,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-eftf2krwbij53usp7qbq,task_description,resolved
+VisualEditor: down arrow in drop-down menu in RTL interface overlaps with the text,Fixed in https://gerrit.wikimedia.org/r/#/c/16590/,1343346049,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-eftf2krwbij53usp7qbq,task_subcomment,NA
+VisualEditor: down arrow in drop-down menu in RTL interface overlaps with the text,Attempted to fix at https://gerrit.wikimedia.org/r/#/c/16218/ .,1342867057,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-eftf2krwbij53usp7qbq,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret","Ctrl+{Delete,Backspace} should delete a word right, left of the caret; Option+{Delete,Backspace} on Mac.
+
+Currently deletes a character right, left of the caret.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1342570860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ar46xe5css6dnxzqbtde,task_description,resolved
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret","The(In reply to comment #4)
+> It doesn't work in RTL.
+
+Bug 48912 is this bug for RTL; this has been closed for a year as done.",1369782887,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret",It doesn't work in RTL.,1369777371,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret","**orbit** wrote:
+
+This has been fixed. We're no longer programmatically handling delete and backspace keypresses. Now, we let the browser do its thing and we observe what's changed and compose an accurate transaction to the data model. The exception is at node boundaries (pressing backspace at the beginning of a paragraph, for example) which are still handled programmatically.",1345486426,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret","As with bug 38000, this feature must be left to the browser as much as possible. Some browsers delete the space after the word, some don't; some delete the punctuation after the word, some don't; in some languages the meaning of ""word"" is very surprising to people who speak English; in RTL languages ""right"" is the previous word and not the next; etc. We should just leave the behavior to which the users are accustomed in their favorite browsers.
+
+See https://www.mediawiki.org/wiki/VisualEditor/Internationalization_requirements .",1342868975,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret",Assigning to Christian as he's requested for all key-binding tickets.,1342570929,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,"I found that neither the global block nor the blacklisting of this title  prevented a globally-blocked proxy from creating http://www.mediawiki.org/w/index.php?title=VisualEditor:Modern_Apizza&action=edit&redlink=1.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1341867660,PHID-USER-wqc7ciyvfzunj3l2tvjt,PHID-TASK-jka67woodw5fn6qicshn,task_description,resolved
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306604,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jka67woodw5fn6qicshn,task_subcomment,NA
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,Fixed in gerrit 31889,1354218618,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jka67woodw5fn6qicshn,task_subcomment,NA
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,De-prioritising (as will be fixed when we properly deploy anyway).,1347302563,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jka67woodw5fn6qicshn,task_subcomment,NA
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,"This will naturally resolve itself when we lift the namespace-specific restrictions on editing the Wikitext and can use the editing API instead of going through the back door, as we do now.
+
+This is related to bug 37844 - in that these will both be resolved in the same way.",1345672064,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jka67woodw5fn6qicshn,task_subcomment,NA
+Selecting all text causes JS error in Firefox,"If I edit any page in Firefox 13 and select all text (using Ctrl+A), I get the following error:
+
+end is undefined
+http://localhost/w/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js
+Line 849
+rangyRange.setEnd( end.node, end.offset );
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux",1341519180,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3rsluniow7ulmwxctugw,task_description,resolved
+Selecting all text causes JS error in Firefox,"
+
+*** This bug has been marked as a duplicate of bug 38037 ***",1341519459,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3rsluniow7ulmwxctugw,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","From user submission. Uses same design argot as iOS. Perhaps confusing for non-iOS situations?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340916840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-etughy4urwl7bhwydk2t,task_description,resolved
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content",This is now how CE works; not sure when we altered behaviour to 'fix' it.,1360095133,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","Brion: Agreed.  IF anything we should surpress our context icon in IOS.  Perhaps invent our own tool there as well, though it seems it may get a bit cluttered.",1341617516,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","If we suppressed the default popup (assuming that's possible), then you'd be unable to copy/cut/paste text.
+
+That.... sounds bad. :)",1340920380,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","I imagine we'd want to suppress iOS's in-built behaviour if that happened (or suppress ours and magically work with it, somehow - using a generic mobile interface like PhoneGap, so we don't endlessly code for mobile? To discuss at a proper design meeting!",1340917997,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","A potential problem here is overlapping with the system's own buttons. When you select on iOS, you get a little popup menu offering copy/cut/paste.
+
+We already overlap our arrow with the iOS selection handle (bug 37874), so make sure we don't go from one overlap to another. :)",1340917068,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+VisualEditor: 'Enter' key does not submit edit from save dialog,"My muscle memory really, REALLY wants to hit enter after typing a summary, but it does nothing. Have to go to the mouse and find the button manually. Eww!
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340912820,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-3edkedybbeebfer2rcap,task_description,resolved
+VisualEditor: 'Enter' key does not submit edit from save dialog,Fixed in https://gerrit.wikimedia.org/r/16782,1343341015,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-3edkedybbeebfer2rcap,task_subcomment,NA
+VisualEditor: 'Enter' key does not submit edit from save dialog,":) same as bug 38042
+
+*** This bug has been marked as a duplicate of bug 38042 ***",1340916283,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-3edkedybbeebfer2rcap,task_subcomment,NA
+VisualEditor: doesn't trigger in IE 9 (Internet Explorer 9),"Tested on Windows 7 SP1 w/ IE 9...
+
+Edit tab just gives me the classic edit page...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340910600,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-etsrlkklzald7ybkqh3u,task_description,declined
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,"Possibly harmless but worrying.
+
+Steps to repro:
+* go to https://www.mediawiki.org/wiki/VisualEditor:Test?debug=true
+* hit edit
+* click in the article
+* ctrl+a (cmd+a on mac) to select all
+
+Expected:
+* all text of article should be selected
+
+Actual:
+* all text of article is selected
+* AND there's an error in the JS console: ""end is undefined""
+ve.ce.Surface.js (line 832)
+rangyRange.setEnd( end.node, end.offset );
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/VisualEditor:Test?debug=true",1340909880,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-h7ssc4ozwop6qczla4rr,task_description,declined
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,"**orbit** wrote:
+
+It doesn't look like this is happening any longer. Lots of changes that may have fixed this have rolled out since July.",1350377414,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,"(In reply to comment #0)
+> Possibly harmless
+
+It actually is harmful, and I suggest raising priority.
+
+Steps to reproduce:
+1) Go to http://www.mediawiki.org/wiki/Special:VisualEditorSandbox with Firefox
+2) Press CTRL-A (or select all text with the mouse)
+3) Press CTRL-X to cut all this text. The text disappears.
+4) Press CTRL-V to reinsert the text.
+
+PROBLEM: One can enter text, but not new lines. Pressing ""Enter"" does not have
+any effect.
+
+Tested on Ubuntu 2012.04, Firefox 13.0.1
+
+Tip to take with a grain of salt: I have seen some problems with UNDO when selecting everything or even everything but last character, but I can't reproduce, so don't mind. If I find something reproducible I will let you know.",1341541738,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,*** Bug 38207 has been marked as a duplicate of this bug. ***,1341519459,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,I can reproduce this in Firefox 13. Does not happen in Chrome.,1341519450,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,Tested in Firefox 12.0 on Ubuntu 12.04 and 16 nightly on Mac OS X 10.7.4,1340910011,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: Tooltips for formatting menu are broken,"From user feedback. They seem to be unescaped, too - ""&lt;visualeditor-formatdropdown-tooltip&gt;"" etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1340834040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rataorpnc6452rqcpgfh,task_description,resolved
+VisualEditor: Tooltips for formatting menu are broken,"Thank you James.
+Fixed in https://gerrit.wikimedia.org/r/14599",1341617408,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-rataorpnc6452rqcpgfh,task_subcomment,NA
+VisualEditor: Tooltips for formatting menu are broken,"Occurs in Chrome/Mac and Safari/Mac, but not Firefox/Mac.
+
+Resultant HTML:
+
+<div class=""es-tool es-toolbarDropdownTool es-toolbarDropdownTool-format"" title=""&lt;visualeditor-formatdropdown-tooltip&gt;"">
+
+&lt;visualeditor-formatdropdown-tooltip&gt;
+
+(individual entries don't have tooltips assigned)
+
+Presumably this is meant to use [[MediaWiki:Visualeditor-formatdropdown-tooltip]] which is unititialised on MW.org - but setting it to something doesn't fix the problem:
+
+http://www.mediawiki.org/wiki/MediaWiki:Visualeditor-formatdropdown-tooltip
+
+From perusing the code I think it's in the messages array but missing from the i18n file, and not called by modules/ve/ui/tools/ve.ui.FormatDropdownTool.js, but it's got beyond my patience when rooting around with nano. :-)",1340926358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rataorpnc6452rqcpgfh,task_subcomment,NA
+VisualEditor: Tooltips for formatting menu are broken,I don't see this in Firefox 13/Linux either in the deployment on mediawiki.org or locally. Any details on when/where this happens?,1340904447,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-rataorpnc6452rqcpgfh,task_subcomment,NA
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,"If in a link inspector or in the edit summary, pressing Page Up, Page Down, Home or End works in that box but also triggers the main edit space to move to the top or bottom. It needs to ignore if it's not got the caret. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340833800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d66zsm26kiowezoool57,task_description,declined
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,"**orbit** wrote:
+
+Okay, I looked more closely at this bug an understand it better. We're not doing any sort of processing of those keys, so the browser is doing what the browser naturally does. I use a Macbook Air and Chrome most of the time and for moving my cursor around a textarea (including the one that I'm typing in now), I use Command + [up, down, left, right] for jumping to the first char, last char, beginning of line, and end of line. I plugged in an external keyboard with proper page up, page down, home, and end keys and was able to reproduce the described behavior. Trevor and I just spoke about this and we don't think we should try to override the browser's handling of this. A ""fix"" may have other user experience consequences.
+
+Please reopen if you think I'm misunderstanding something.",1350690378,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d66zsm26kiowezoool57,task_subcomment,NA
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,"**orbit** wrote:
+
+This is probably fixed now, but I'll have to test in the morning when I have a keyboard with these buttons properly.",1350377009,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d66zsm26kiowezoool57,task_subcomment,NA
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,"Indeed - the problem as described seems only to happen in Safari and Chrome for me; in Firefox, instead the characters do nothing (pressing ""Home"" when in revision description box should move caret to before first character).",1340922316,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d66zsm26kiowezoool57,task_subcomment,NA
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,Can't reproduce in Firefox 13.0/Linux.,1340902371,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-d66zsm26kiowezoool57,task_subcomment,NA
+VisualEditor: Design of save button should make it more prominent,"From user request. ""Big Red Button"" requested, but we might want to consider within a wider design discussion. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340833380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l7c73muvr5qk2q5p42wr,task_description,resolved
+VisualEditor: Design of save button should make it more prominent,Various changes have been made in Ib1711f49af8929be12796aecdea49467b726856e which address this issue.,1347303896,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-l7c73muvr5qk2q5p42wr,task_subcomment,NA
+VisualEditor: Link inspector button in toolbar should let users create a link without any text selected,"From user request. Possibly insert the name of the target automatically? So a link to [[foo]] will be entered as <a href=foo>foo</a>?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340832780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-urg73yoypnuiks7zst4o,task_description,resolved
+VisualEditor: Link inspector button in toolbar should let users create a link without any text selected,"
+
+*** This bug has been marked as a duplicate of bug 33141 ***",1340833038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-urg73yoypnuiks7zst4o,task_subcomment,NA
+"VisualEditor: Ctrl + {left,right} arrow should skip a word left or right (Apple + ... on Mac OS X)","From user request. There are other keybinding feature requests; possibly worth documenting all the ones we respect?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340830740,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-53mqogsdiodyzah24cx5,task_description,resolved
+"VisualEditor: Ctrl + {left,right} arrow should skip a word left or right (Apple + ... on Mac OS X)","**orbit** wrote:
+
+This is fixed now. The cursor moves natively unless some conditions are met (inside a slug or moving farther than 1 offset).",1349998405,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-53mqogsdiodyzah24cx5,task_subcomment,NA
+"VisualEditor: Ctrl + {left,right} arrow should skip a word left or right (Apple + ... on Mac OS X)","This is one of those things that should be left to the browser as much as possible.
+
+If it is implemented inside the VE, there will be no end to surprises. Different browsers have subtle differences in the behavior of this feature, and users who use it often and are accustomed to the behavior in their favorite browser won't like the VE implementation, whatever it will be. There are also numerous surprises in the i18n side - the different direction of movement in RTL environments, word-boundary algorithms in Thai, and many, many more.
+
+See https://www.mediawiki.org/wiki/VisualEditor/Internationalization_requirements .",1342868297,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-53mqogsdiodyzah24cx5,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","Steps to reproduce:
+1) Go to http://www.mediawiki.org/wiki/Special:VisualEditorSandbox
+2) Press CTRL-A (or select all text with the mouse)
+3) Press CTRL-X to cut all this text. The text disappears.
+4) Press CTRL-V to reinsert the text.
+
+PROBLEM1: Text is not reinserted, the page stays blank.
+PROBLEM2: One can enter text, but not new lines. Pressing ""Enter"" does not have any effect.
+
+Tested on Ubuntu 2012.04, Firefox 13.0.1
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1340770860,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-obhstlqgs73vks43hy74,task_description,resolved
+"VisualEditor: Cut all text, re-paste it: broken editor","(In reply to comment #6)
+> > Problem #2 is a Firefox-specific selection issue, so I'm filing a separate bug for that and closing this one as fixed.
+> 
+> Roan, could you please tell us the identifier of the new bug report you
+> created?
+
+Sorry, meant to do that but forgot. I filed bug 38207 for it and later found it was a duplicate of bug 38037.",1341540598,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","> Problem #2 is a Firefox-specific selection issue, so I'm filing a separate bug for that and closing this one as fixed.
+
+Roan, could you please tell us the identifier of the new bug report you created?",1341540453,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","(In reply to comment #4)
+> This looks like a bug in fixupInsertion. When the entire contents is cut, only
+> paragraph and /paragraph are in the documentModel. Pasting more than 2
+> paragraphs will error. 
+> 
+This fixupInsertion issue is fixed in https://gerrit.wikimedia.org/r/14398 . This fixes problem #1, which occurred in all browsers. Problem #2 is a Firefox-specific selection issue, so I'm filing a separate bug for that and closing this one as fixed.",1341518416,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","**orbit** wrote:
+
+This looks like a bug in fixupInsertion. When the entire contents is cut, only paragraph and /paragraph are in the documentModel. Pasting more than 2 paragraphs will error. 
+
+Steps to reproduce:
+1) Create a document with 3 simple paragraphs.
+2) Ctl-A
+3) Ctl-X
+4) Ctl-V",1341264805,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","The component below does not have this bug:
+http://html5demos.com/contenteditable/",1340926239,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor",Confirm problem 1 (but not 2) on Chrome 19/Mac and both problems on Firefox 13/Mac.,1340836052,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","On Ubuntu 2012.04, Chromium 18.0.1025.151: Only PROBLEM1 occurs, PROBLEM2 does not occur.",1340771015,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: Macintosh",1340709300,PHID-USER-fgzcdbj3je3ksnhufo47,PHID-TASK-zlt7qdys5zthrlly644p,task_description,resolved
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari","This should be fixed now, as part of the fix for Ime.",1350414720,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari",I think I know what is the issue. Will be fixed together with adding support for IME.,1342551105,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari",Confirmed that I get the above odd behaviour using keyboard-shortcuts to create diacritics on Mac using Chrome and Safari (but not using Firefox).,1340730365,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari","Other behavior:
+* When entered as the first character on a newline, a duplicate line below it with that one character is created
+* Occasionally when a combo is made (e.g., ˆ+ a + r) when the second non-combo character is typed, the combination itself (here â) is deleted.",1340710556,PHID-USER-fgzcdbj3je3ksnhufo47,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari","Examples: typing ""ând"" at the end of a line often causes one of the following:
+* a floating linebreak at the cursor (one which can't be easily deleted, not sure what's happening underneath)
+* a character 4-5 characters to the left of the cursor to *change*.  
+** example changes: from one lowercase letter to another.  from one letter to an uppercase B.  
+
+The above is not 100% reproducible; some of the above happens at least 1 in 3 times I typed this just now; I'm trying to reproduce more specifically.  
+
+[Using Chrome on Mac OS X]",1340709453,PHID-USER-fgzcdbj3je3ksnhufo47,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+VisualEditor: DM support for nested lists,"As discussed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340654160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-byaxrg34aq533rbmohda,task_description,resolved
+"VisualEditor: XYZ:Foo links round-trip surprisingly e.g. Categories, Images/Files, ….","As discussed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340653980,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aypymh3waspkktjfjzyq,task_description,resolved
+"VisualEditor: XYZ:Foo links round-trip surprisingly e.g. Categories, Images/Files, ….",Fixed in https://gerrit.wikimedia.org/r/#/c/14605/,1341637505,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-aypymh3waspkktjfjzyq,task_subcomment,NA
+"VisualEditor: Trim whitespace on headings, list items, other node types","As discussed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340653920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pz4hu5kupf3cy6rgi2hl,task_description,resolved
+"VisualEditor: Trim whitespace on headings, list items, other node types","Done in https://gerrit.wikimedia.org/r/#/c/18711/ , commit message explains what this feature is about.",1345485423,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pz4hu5kupf3cy6rgi2hl,task_subcomment,NA
+"VisualEditor: Trim whitespace on headings, list items, other node types","Note -- ""as discussed"" isn't very clear; I presume some discussion was had somewhere by someone, and can only hope that the assignee of the bug understands what this means. In future please summarize the discussion in the bug, thanks. :)",1340904774,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-pz4hu5kupf3cy6rgi2hl,task_subcomment,NA
+"VisualEditor: Placing the cursor (by clicking or through the cursor keys) into sub-lists breaks - it ""flashes"" in, but then disappears (is no longer drawn anywhere) and cannot be used (e.g. shift-left or etc. doesn't work).","(From the casual list on the wiki.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340569500,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k2ubvggwznutod3v37na,task_description,resolved
+"VisualEditor: Placing the cursor (by clicking or through the cursor keys) into sub-lists breaks - it ""flashes"" in, but then disappears (is no longer drawn anywhere) and cannot be used (e.g. shift-left or etc. doesn't work).",This works now.,1343097980,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-k2ubvggwznutod3v37na,task_subcomment,NA
+"VisualEditor: Placing the cursor (by clicking or through the cursor keys) into sub-lists breaks - it ""flashes"" in, but then disappears (is no longer drawn anywhere) and cannot be used (e.g. shift-left or etc. doesn't work).","Add to ""VE-deploy-2012-07-09"" milestone per this morning's meeting.",1341266205,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k2ubvggwznutod3v37na,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,"(From the casual list on the wiki.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340569500,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_description,resolved
+VisualEditor: Indent and outdent buttons do not exist,I see them now :) . Fixed in today's deployment.,1343097650,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,"Add to ""VE-deploy-2012-07-09"" milestone per this morning's meeting.",1341266196,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,"Changing summary from ""do not work"" to ""do not exist"" then. :)",1340913272,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,... but you will. :-),1340653953,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,I don't see any indent/outdent buttons...,1340651426,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Unlisting should unlist all list levels,"(From the casual list on the wiki.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340569440,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7hymyhokel2tmuz42xo3,task_description,resolved
+VisualEditor: Unlisting should unlist all list levels,"https://gerrit.wikimedia.org/r/#/c/32664/ fixes the previous functionality, which was to unlist the selected list and its child lists. Unlisting of parent lists was never implemented, but I see you've filed other bugs for that now (including bug 41935), so closing this one.",1352596148,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7hymyhokel2tmuz42xo3,task_subcomment,NA
+VisualEditor: Unlisting should unlist all list levels,"Functionality appears to have been lost - now unlisting only unlists at the most-deeply-nested list, and has no effect on lists further up the tree.",1352482289,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7hymyhokel2tmuz42xo3,task_subcomment,NA
+VisualEditor: Unlisting should unlist all list levels,Implemented in https://gerrit.wikimedia.org/r/#/c/16680/,1343260936,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7hymyhokel2tmuz42xo3,task_subcomment,NA
+VisualEditor: Unlisting should unlist all list levels,"Add to ""VE-deploy-2012-07-09"" milestone per this morning's meeting.",1341266188,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7hymyhokel2tmuz42xo3,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,"From MW.org report:
+
+Links should probably have a title="""". I naturally hover over links to see their target. I wanted to see if the target was correct and I had to fiddle with the link editor just to see something that should have been easily available.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340569140,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utdxlw7pghyukf2ujhmo,task_description,resolved
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,Now merged; will be deployed as part of the 2013-01-16 release cycle.,1357678591,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,Patched in: https://gerrit.wikimedia.org/r/38636,1355436725,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,[REGRESSION] This was fixed but now is not (probably in UI-rewrite). Would be nice to fix.,1355435259,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,"Fixed in gerrit 21208 - left unclosed by accident, I think. (?)",1353134829,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,"Created attachment 11068
+Screenshot illustrating problem
+
+Illustration of problem attached.
+
+**Attached**: {F9394}",1346774776,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,Resolved in I1a1cfd70c222dd1d686b46cd702edf2e9d0e5bae,1345749594,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to preview the diff of the changes made,"(Depends on us working out what diffing revisions should look like now.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340569020,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hcc3ucc2gxwo6jb557m7,task_description,resolved
+VisualEditor: Provide a way to preview the diff of the changes made,"
+
+*** This bug has been marked as a duplicate of bug 37931 ***",1345669770,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-hcc3ucc2gxwo6jb557m7,task_subcomment,NA
+VisualEditor: Edit window scrolls to top of page after paste,"iOS 5.1 simulator on Mac OS X
+
+After pasting text into the document, the view is scrolled up to the top of the page. This is a bit distracting if you're somewhere further down in the document. :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340473080,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_description,resolved
+VisualEditor: Edit window scrolls to top of page after paste,Note which milestone this met.,1355171016,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_subcomment,NA
+VisualEditor: Edit window scrolls to top of page after paste,Fixed in gerrit 37575.,1354928052,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_subcomment,NA
+VisualEditor: Edit window scrolls to top of page after paste,"This was also happening in Chrome and Firefox on desktop.
+
+http://cl.ly/image/0B443D3x1Y2T",1354920770,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_subcomment,NA
+VisualEditor: Edit window scrolls to top of page after paste,"Moving to ""Mobile"" component.",1354811631,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_subcomment,NA
+VisualEditor: toolbar mispositioned on iPad,"Screenshot of iPad simulator
+
+The toolbar is slightly mispositioned on iPad, tested in iPad simulator on Mac OS X as my iPad isn't handy.
+
+Seems to be slightly up and to the left of where it should be. Screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9308}",1340472060,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-dutiulezx3dwzyt4n3jd,task_description,resolved
+VisualEditor: toolbar mispositioned on iPad,"In the following commit, toolbar detaching mechanism has been disabled on mobile devices.  Floating logic has been improved with boundaries and a bottom position. 
+https://gerrit.wikimedia.org/r/#/c/14072/
+
+There is talk of creating a mobile friendly toolbar but that is a potential feature request that has yet to be designed.",1343668655,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-dutiulezx3dwzyt4n3jd,task_subcomment,NA
+VisualEditor: toolbar mispositioned on iPad,"Also doesn't seem to follow viewport properly....
+
+At some point in my testing the toolbar switched to fixed-position following the viewport, but it won't re-dock when scrolling to the top of the page.",1340473346,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-dutiulezx3dwzyt4n3jd,task_subcomment,NA
+"VisualEditor: Window-close prompt thinks I'm returning to view mode, and displays two warnings rather than one.","Tested in Safari 5.1.7.
+
+Steps to repro:
+* open https://www.mediawiki.org/wiki/VisualEditor:Welcome
+* hit 'edit'
+* close tab
+
+A prompt comes up:
+
+  https://www.mediawiki.org
+  Are you sure you want to leave this page?
+  Are you sure you want to go back to view mode without saving first?
+  [Stay on page] [Leave page]
+
+The ""Are you sure you want to go back to view mode without saving first?"" presumably comes from our code. This makes sense only if I were clicking on the 'read' tab link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340470920,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-k3ogdcpxt3y5m7tvnsj2,task_description,declined
+"VisualEditor: Window-close prompt thinks I'm returning to view mode, and displays two warnings rather than one.",I can't reproduce this - but that might be because this was a side-effect of something that has since been changed.,1345748822,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-k3ogdcpxt3y5m7tvnsj2,task_subcomment,NA
+"VisualEditor: Window-close prompt thinks I'm returning to view mode, and displays two warnings rather than one.",Moving from UI to Integration module.,1340564817,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k3ogdcpxt3y5m7tvnsj2,task_subcomment,NA
+"VisualEditor: Add inline editing after each link, accessed by hide/unhide icon","Suggestion: after each link add a little icon which, when clicked, adds a directly editable inline element containing the link destination. No need to go to the top, no no modal popup dialog which has to separately confirmed... The inline link destination should not require closing to accept, it should just be a part of the text and changes to it are naturally saved together with all other text when the page is being saved.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340418720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qc2hzb2zgpy4pqax7p6j,task_description,invalid
+"VisualEditor: Add inline editing after each link, accessed by hide/unhide icon",This is now not compatible with how the UX has developed; closing.,1360204987,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qc2hzb2zgpy4pqax7p6j,task_subcomment,NA
+"VisualEditor: Add inline editing after each link, accessed by hide/unhide icon","Changed title by jforrester from ""Add inspector accessor icon after each link for easier editing"" to ""Add inline editing after each link, accessed by hide/unhide icon"". The main part of my original proposal is not the accessor icon, but allow editors to optionally see and edit the link destination directly after the link text, without the need to open a modal dialogue box and memorize the link destination afterwards, potentially for multiple links.",1340539721,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-qc2hzb2zgpy4pqax7p6j,task_subcomment,NA
+"VisualEditor: Unexpected behaviour of list editing - what level should the buttons operate, and is it consistent?","From https://www.mediawiki.org/w/index.php?title=Thread:VisualEditor_talk:Welcome/Editing_numbered_Lists_is_broken&lqt_method=thread_history
+
+Click on one item in a three element numbered list and click on the numbered list button -> all three elements become unnumbered. Click again -> only the first element becomes numbered.
+Mark all three and click -> you sometimes get three elements in a numbered list, sometimes three numbered lists, each starting with number 1. Could not figure out when I get what...
+When I mark three fresh, non numbered, non-bulleted lines, it seems generally to work becoming a three part numbered list. Although clicking again (which changing selection focus) on the button to undo here never works. That is: all three 1 to 3 selected, click on numbered list button to unnumber does not work, going to the first element click same button, unnumbers all.
+Having three line of unnumbered text where the second element is a bulleted list item, select, click numbered list (expecting to have a nested bullet within a numbered list) does not work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340418540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vnz2yl4fdnpwhagmzdlo,task_description,declined
+"VisualEditor: Unexpected behaviour of list editing - what level should the buttons operate, and is it consistent?","This appears now to be fixed in current behaviour (part 1 of the issue is intended, the rest seems fixed).",1352481732,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vnz2yl4fdnpwhagmzdlo,task_subcomment,NA
+VisualEditor: Nested lists (tracking bug),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340413620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jnj6pwbdr63nh5prebtr,task_description,resolved
+VisualEditor: Nested lists (tracking bug),"Add to ""VE-deploy-2012-07-09"" milestone per this morning's meeting.",1341266220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jnj6pwbdr63nh5prebtr,task_subcomment,NA
+VisualEditor: JS error on load in IE 10,"Seen in my JS console during loading in IE 10 on Windows 8 Release Preview:
+
+SCRIPT5007: Unable to get property 'to' of undefined or null reference
+ve.ui.Context.js, line 120 character 2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340405460,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-yl7i3kirybrkgyab56tk,task_description,resolved
+VisualEditor: JS error on load in IE 10,Confirmed fixed in newly-deployed version.,1350327505,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yl7i3kirybrkgyab56tk,task_subcomment,NA
+VisualEditor: JS error on load in IE 10,"I haven't been able to reproduce this in IE10.  Though, this same error happens randomly in all browsers.  I suspect it to be related to a recently closed context icon bug.  Though, I'm failing to find it since I marked it as resolved.",1341616538,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-yl7i3kirybrkgyab56tk,task_subcomment,NA
+VisualEditor: JS error on load in IE 10,"Line is:
+
+  if (selection.to > selection.from) {
+
+in Context.PositionIcon ...",1340405718,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-yl7i3kirybrkgyab56tk,task_subcomment,NA
+VisualEditor: Mouse selection very unreliable in Internet Explorer 10,"Testing on Windows 8 Release Preview running in VirtualBox.
+
+Click to set caret position and click-and-drag to select text don't seem to work reliably in IE 10. Tested both in desktop and Metro mode.
+
+Mouse activity can be seen in mouseover and mousedown text decoration/coloring on links, but ... most of the time the caret doesn't move / selection doesn't change.
+
+Occasionally one gets through, it's not clear how/why.
+
+Note that selection with arrow keys+shift works fine.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340404680,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-ilakhjhigyp4sxfadq5q,task_description,declined
+VisualEditor: Mouse selection very unreliable in Internet Explorer 10,"**orbit** wrote:
+
+This isn't reproducible, but a lot has changed since this bug was reported. The only problem I've noticed is the location of the context menu. I'll open a new bug for that.",1350690829,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ilakhjhigyp4sxfadq5q,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","For mobile, tablets and laptops with high-resolution displays we'll want double-resolution or SVG versions of the icons served. Attached screenshot taken in Firefox 16 nightly with acceleration disabled on MacBook Pro Retina. Looks about the same in Safari.
+
+The current icons appear to be PNG, with a PSD source file that's at low resolution. If the layers are vector shapes this should be easy to convert to high-resolution, but I don't have Photoshop on this machine to double-check.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340401080,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-a2g47wnz3wqen23fp6b7,task_description,resolved
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","The problem with always using SVG is that at lower DPI the rendering quality is inferior. In most browsers the pixel boundaries are off a bit here and there, making the icons look fuzzy. I think using raster graphics for icons will some day be antiquated, but we aren't there yet.",1347310446,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",Broke out follow-up issue to bug 40140.,1347307985,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","(In reply to comment #7)
+> This sounds like a UserAgent problem. Isn't the UA meant to handle this?
+
+Nope, no information available in the UA for this.
+
+(In reply to comment #8)
+> What about when you have the browser spanning between a low and high DPI
+> screen? We can only depend on devicePixelRatio.
+
+If you're spanning over low and high DPI screens on Mac OS X, the window gets assigned the density of whichever window it has the greatest area on. Eg, either you get 1.0 scale and it's pixelated on the high-res screen, or you get 2.0 scale and it's scaled down on the low-res screen.
+
+The trick is that window.devicePixelRatio may change over time -- it's a property, not a constant. I think you get a window.onresize event when switching ratios, but I'll have to double-check that.
+
+> I think this is closed until there's a better way to detect this.
+
+Yeah it's good enough for now, but I'll file a separate bug as a reminder for later if we find a cleaner way.
+
+The simplest full fix would be to always use SVG when SVG is supported in the browser -- this would also fix it for Internet Explorer 10, which doesn't support devicePixelRatio but has support for higher-resolution screens in Windows 8.",1347307314,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","What about when you have the browser spanning between a low and high DPI screen? We can only depend on devicePixelRatio.
+
+I think this is closed until there's a better way to detect this.",1347304194,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",This sounds like a UserAgent problem. Isn't the UA meant to handle this?,1347304100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","Hmm.
+
+Actually there's a minor issue: if starting the editing on a low-resolution screen and then switching to high-resolution (by moving the window across screens or changing the screen resolution) we still are stuck with the low-resolution bitmap icons.",1347303656,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","Looks awesome in Safari and Chrome on MacBook Pro with Retina display, thanks guys! :D
+
+(Proper rendering on Firefox will come in future... upstream issues there still but it'll come.)",1347303562,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",Fixed in https://gerrit.wikimedia.org/r/#/c/22113/,1347302633,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",Moving to UI component,1340404205,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",Mass-moving items into VisualEditor product,1340402721,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","Created attachment 10782
+Screenshot on  Retina MacBook Pro
+
+**Attached**: {F9551}",1340401162,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+Delete at end of document causes JS error,"As discussed. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340400480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_description,resolved
+Delete at end of document causes JS error,"I borked that commit - this one is clean:
+
+https://gerrit.wikimedia.org/r/#/c/13177/",1340815105,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_subcomment,NA
+Delete at end of document causes JS error,"**orbit** wrote:
+
+This has been fixed in:
+https://gerrit.wikimedia.org/r/12974
+Will be released soon.",1340668774,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_subcomment,NA
+Delete at end of document causes JS error,"Mass-move out of ""General"" to ""ContentEditable"".",1340415378,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_subcomment,NA
+Delete at end of document causes JS error,Mass-moving items into VisualEditor product,1340402769,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,"The current VisualEditor interface has a prominent ""Save page"" button, but no ""Cancel"" button. It would be nice if there were a clear exit strategy in the interface.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340393700,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_description,resolved
+VisualEditor: Interface should have an obvious way to get back to reading mode,Now merged into master.,1354750533,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,"Added cancel button to VisualEditor MediaWiki Integration.
+Patched in https://gerrit.wikimedia.org/r/#/c/36934/
+
+Awaiting review.",1354667827,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,"(In reply to comment #3)
+> Perhaps the browser Back button could be harnessed for this purpose, by
+> changing the actual URL without reloading the page (like Facebook does when
+> browsing photos, for instance) or even just the anchor?
+
+You should file this as a separate bug (if one doesn't exist already). :-)",1340501803,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,"Perhaps the browser Back button could be harnessed for this purpose, by changing the actual URL without reloading the page (like Facebook does when browsing photos, for instance) or even just the anchor?
+
+But yes, I agree that a clearer way of ""cancelling"" needs to be given within the actual interface, in addition to the Back button.",1340500453,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,Trevor - thoughts on this as intended behaviour?,1340413229,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,Mass-moving items into VisualEditor product,1340402727,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"Based on some testing on MediaWiki.org, page protection and the abuse filter do not work - page protection does not change the ability of all non-blocked users to edit the page and abuse filter does not pick up any edits generated by the visual editor.
+
+I believe that the underlying problem is that using the visual editor is not a named action that can be restricted or filtered at the moment. If it was, then it would be possible to assign it to $wgRestrictionTypes and it would be possible for the abuse filter to log it (though the abuse filter does need the addition of some variables or other modification to accept visual editor edits).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340391180,PHID-USER-wqc7ciyvfzunj3l2tvjt,PHID-TASK-2kfniuyxuldpuiatpfod,task_description,resolved
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306607,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,Fixed in gerrit 31889,1354218776,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,This was fixed when Roan changed to use the normal edit API rather than bypassing it internally.,1354216989,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"This will naturally resolve itself when we lift the namespace-specific restrictions on editing the Wikitext and can use the editing API instead of going through the back door, as we do now.
+
+This is related to bug 38268 - in that these will both be resolved in the same way.",1345672049,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"Two things:
+1.How would an abuse log entry look like? I can't think of anything other than 'Example (talk|contribs) triggered filter 16, performing the action ""usevisualeditor"" on VisualEditor:Welcome' (etc.).
+2.What about page protection?",1340422207,PHID-USER-wqc7ciyvfzunj3l2tvjt,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"AbuseFilter *should* see them, because to do otherwise is insane. That it doesn't is the bug. :)",1340420631,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"AbuseFilter does not see them, because I tested some VE edits against my experimental filter but edits made by the VE did not get caught.
+
+The 'usevisualeditor' permission would only be a temp solution to the current situation where page protection can't cover it. The other way is to require the 'edit' permission but then that wouldn't suffice in our current scheme of having only admins edit the wikitext directly.",1340417825,PHID-USER-wqc7ciyvfzunj3l2tvjt,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"I would not recommend creating a 'usevisualeditor' permission. Rather, permission checks and the usual edit activity paths should be used. AbuseFilter *should* see VE edits exactly the same as edits made through the traditional editing UI or the API.",1340416947,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,Mass-moving items into VisualEditor product,1340402735,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"I created a blank page at <https://www.mediawiki.org/wiki/VisualEditor:Hello_there>. When I try to edit the page using the VisualEditor extension, I receive the following error: ""Error loading data from server: No HTML content in response from server. Would you like to retry?""
+
+I imagine this is a safety check somewhere in the code that needs to be tweaked. If page_len == 0, it isn't always an error. Sometimes a blank page is just a blank page. ;-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340390820,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_description,resolved
+VisualEditor: Throws error when trying to edit blank (but existing) page,"Resolved in gerrit.
+
+Change-Id: I8857d39e1a20080c8419c6165be2b5ad0cdbacd2",1351287039,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"(In reply to comment #1)
+> That blank page shouldn't have been possible to create in the first place.
+You can easily create a blank page by first creating a page with content, then blanking it.
+
+(In reply to comment #4)
+> Parsoid does handle zero length content -- it returns a zero length HTML
+> response. Right now, VisualEditor extension expects a non-zero HTML response
+> and returns an error if not (line 18 of ApiVisualEditor.php).  This can be
+> verified at this url:
+> https://www.mediawiki.org/w/api.php?action=ve-parsoid&paction=parse&page=VisualEditor%3AHello_there&format=json
+> (for other pages, the result is success with a valid parsed string).
+Thanks Subbu, that's exactly what was going on. Fix submitted in https://gerrit.wikimedia.org/r/30281 .
+
+> So,
+> either ApiVisualEditor.php has to handle a zero-length response as a valid
+> response, and we need a different way to signal errors from Parsoid, or Parsoid
+> has to always return a non-zero response.   My hunch is that as long as Parsoid
+> returns a 200 OK, ApiVisualEditor accept a zero-length response as a valid
+> response (and if necessary, have sanity checks somewhere -- a non-zero length
+> body should not return a zero-length response, maybe).  Error conditions from
+> Parsoid could be signaled with a different HTTP response code maybe (offhand,
+> 503 is one option). At this time, I am not sure what the right solution is, but
+> hopefully this will help figure out what that might be.
+I verified that nonexistent pages give me a 404, so I think this is fine. I haven't checked other error conditions because they're nontrivial to reproduce, but as long as Parsoid only returns a 2xx status code when it's actually delivering parsed content and uses 4xx/5xx for errors, I'll be fine.",1351285526,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,Moving to DM if we're happy with current Parsoid behaviour - to discuss?,1340565870,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"Actually, I meant 500, not 503.",1340430020,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"Parsoid does handle zero length content -- it returns a zero length HTML response. Right now, VisualEditor extension expects a non-zero HTML response and returns an error if not (line 18 of ApiVisualEditor.php).  This can be verified at this url: https://www.mediawiki.org/w/api.php?action=ve-parsoid&paction=parse&page=VisualEditor%3AHello_there&format=json (for other pages, the result is success with a valid parsed string).  So, either ApiVisualEditor.php has to handle a zero-length response as a valid response, and we need a different way to signal errors from Parsoid, or Parsoid has to always return a non-zero response.   My hunch is that as long as Parsoid returns a 200 OK, ApiVisualEditor accept a zero-length response as a valid response (and if necessary, have sanity checks somewhere -- a non-zero length body should not return a zero-length response, maybe).  Error conditions from Parsoid could be signaled with a different HTTP response code maybe (offhand, 503 is one option). At this time, I am not sure what the right solution is, but hopefully this will help figure out what that might be.",1340428385,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,Mass-moving items into VisualEditor product,1340402745,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"(In reply to comment #1)
+> That blank page shouldn't have been possible to create in the first place.
+
+Heh, well I originally created the page as the brand new account I was using to test VisualEditor didn't have the createpage right (for whatever reason).
+
+To be clear, this bug is not about VisualEditor creating a blank page. This bug is about VisualEditor throwing an error when the page length is 0 bytes and the user attempts to edit the page using the VisualEditor interface. <https://www.mediawiki.org/wiki/VisualEditor:Blank_page> is another test case.
+
+For discussion regarding whether MediaWiki should allow users to create blank pages, you want bug 12621. :-)",1340401108,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,That blank page shouldn't have been possible to create in the first place.,1340390983,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"If I input <nowiki>a</nowiki> in VE, save the page, then go back to the editor, text is broken in VE there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340390460,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-clc63qvmswgkzbw33tkq,task_description,resolved
+VisualEditor: Improperly escapes <nowiki>,[Parsoid component reorg by merging CPP/* tickets into General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934305,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,Now merged.,1344447584,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,Fix submitted in https://gerrit.wikimedia.org/r/17921.,1344298000,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"So to be entirely clear:
+
+$ echo ""&lt;nowiki&gt;a&lt;/nowiki&gt;"" | node parse.js --html2wt
+
+actual
+<nowiki>&lt;nowiki&gt;</nowiki>a<nowiki>&lt;/nowiki&gt;</nowiki>
+
+expected
+## &lt;nowiki&gt;a&lt;/nowiki&gt;
+
+The problem is pretty clearly in mw.WikitextSerializer.js, near line 152, in the function wrapNonTextTokens. The serializer escapes any instances of <\/?nowiki> with its HTML-entitied counterpart, then wraps it in <nowiki>. I don't know why right now.
+
+`git blame` seems to think Gabriel would know :)",1344295746,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,Hmm- seems as if I made a mistake while testing this. There might be a Parsoid bug after all.,1344294838,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"<nowiki> is invalid HTML. The DOM representation of nowiki is <span typeof=""mw:Nowiki"">, which round-trips ok. Not sure if the VE handles this properly right now.
+
+<nowiki> in a DOM text node (&lt;nowiki&gt; when entered in the HTML -> wikitext test form) properly serializes to &lt;nowiki&gt;.
+
+Please test round-trip stuff on http://parsoid.wmflabs.org/ if possible ;)",1344294424,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"Oh, never mind.  I got it wrong.  So, the input is not what I tested against.  The text to test is ""&lt;nowiki&gt;a&lt;/nowiki&gt;",1344291499,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"Cannot replicate this either at http://parsoid.wmflabs.org/_html/ or on my CLI (excess newlines trimmed below) with the current HEAD.
+
+------------------
+[subbu@earth lib] echo ""<nowiki>a</nowiki>"" | node parse.js --html2wt 
+<nowiki>a</nowiki>
+
+[subbu@earth lib] echo ""<nowiki>a</nowiki>"" | node parse.js --html2wt | node parse.js
+<p><span typeof=""mw:Nowiki"" data-parsoid=""{&quot;tsr&quot;:[0,8],&quot;bsp&quot;:[0,18]}"">a</span></p>
+
+[subbu@earth lib] echo ""<nowiki>a</nowiki>"" | node parse.js --html2wt | node parse.js | node parse.js --html2wt
+<nowiki>a</nowiki>
+
+--------------------
+
+Either VE is using an older Parsoid version -- or something else is broken.",1344291251,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"Actually a Parsoid bug, moving.",1344290870,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,I would expect as wikitext: &lt;nowiki&gt;a&lt;/nowiki&gt;,1340417145,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"Input HTML: <nowiki>a</nowiki>
+
+Actual output wikitext after RT: <nowiki>&lt;nowiki&gt;</nowiki>a<nowiki>&lt;/nowiki&gt;</nowiki>
+
+Expected wikitext: ???",1340412863,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,Mass-moving items into VisualEditor product,1340402750,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+"VisualEditor: Shift-Page {Up,Down} selection only works upwards","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340388180,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxb522dezlpdexpuwpqh,task_description,declined
+"VisualEditor: Shift-Page {Up,Down} selection only works upwards","**orbit** wrote:
+
+This was probably true at one point, but the work that I've done with native key handling looks to have fixed this.",1350000249,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mxb522dezlpdexpuwpqh,task_subcomment,NA
+"VisualEditor: Shift-Page {Up,Down} selection only works upwards",Mass-moving items into VisualEditor product,1340402752,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxb522dezlpdexpuwpqh,task_subcomment,NA
+"VisualEditor: Shift-Page {Up,Down} selection only works upwards","(In reply to comment #0)
+> 
+
+Please don't do this. Bug summaries often change over time. The bug description (comment 0) should be useful.",1340394886,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-mxb522dezlpdexpuwpqh,task_subcomment,NA
+VisualEditor: Shift-cursor selection downwards switches to upwards selection once you use Up or Right arrow,"Place the caret. Press Shift and then a downwards selection key (i.e. Down or Right arrow). As expected, you move the caret downwards correctly using either key. 
+
+However, after some text is selected, pressing Up or Left causes the caret to move to the start of the selection to expand (rather than allowing the leading edge of the selection to be reduced). All further shift-cursor key presses (Up/Down/Left/Right) only change the position of the earlier part of the selection, and you can no-longer select as desired.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340388060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-anbufyvs4yecgr5utuge,task_description,resolved
+VisualEditor: Shift-cursor selection downwards switches to upwards selection once you use Up or Right arrow,"**orbit** wrote:
+
+This is fixed now due to native cursor handling.",1350000874,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-anbufyvs4yecgr5utuge,task_subcomment,NA
+VisualEditor: Shift-cursor selection downwards switches to upwards selection once you use Up or Right arrow,Mass-moving items into VisualEditor product,1340402778,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-anbufyvs4yecgr5utuge,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"See https://www.mediawiki.org/w/index.php?title=VisualEditor:BugLinkSelection&action=history
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340341920,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uccw7yqukr3actwcyct3,task_description,resolved
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #13)
+> Yes, thank you, that was very helpful. I've no idea how the hell anyone is
+> supposed to know that (beyond reading your comment here on this bug).
+Yeah, I apologize for the poor discoverability of this information :(
+
+> It'd be
+> nice if http://wikitech.wikimedia.org/view/Software_deployments and
+> https://www.mediawiki.org/wiki/MediaWiki_1.20/Roadmap noted this. Is this only
+> for VisualEditor or are all Wikimedia extensions updated every two weeks now?
+All WMF extensions are updated from master every two weeks, same as core. Some WMF-maintained extensions have additional deployment windows scheduled to accelerate deployments, but everything is on the two-weekly deployment train. If people want their deployments to be slower, we tell them to keep their code out of master until it's ready.",1344536745,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #12)
+> (In reply to comment #7)
+> > Hmm, perhaps VisualEditor should have some kind of exposure of a version number
+> > or last deployment date? Given the frequent deployments and code changes, I
+> > think it'd be helpful for testing and bug-filing. I'm not sure if
+> > Special:Version covers this already. Perhaps a separate bug is needed?
+> > 
+> Special:Version lists the git hash of the deployed version, which isn't perfect
+> (and was out of date until just now). There is also a version number there
+> which is currently just set to 0.1, I suppose we could start using that field,
+> either by incrementing it each time or by using something like 0.1-20120806.
+
+It'd certainly be nice for debugging, yes. I was thinking about some kind of user preference or URL parameter or something that would add an HTML comment with useful debug info in it. I can imagine a few data points being helpful, but particularly VisualEditor version number, so people don't end up chasing down bugs that were fixed a week ago.
+
+> Anyway, as for deployment frequency: not counting the fixup deployments that
+> occurred yesterday because various things were broken, there is only one VE
+> deployment every two weeks, on the first Monday of every deployment cycle. The
+> most recent deployment was last Monday (Aug 6), the next one will be on Aug 20,
+> then two weeks after that, etc. This is because our code comes along for the
+> ride with the 1.20wmf* deployments (see
+> https://www.mediawiki.org/wiki/MediaWiki_1.20/Roadmap for the schedule) and the
+> only wiki where VE is currently deployed (mw.org) is part of phase 0, which
+> occurs on the first Monday.
+> 
+> Hope that clears things up a bit.
+
+Yes, thank you, that was very helpful. I've no idea how the hell anyone is supposed to know that (beyond reading your comment here on this bug). It'd be nice if http://wikitech.wikimedia.org/view/Software_deployments and https://www.mediawiki.org/wiki/MediaWiki_1.20/Roadmap noted this. Is this only for VisualEditor or are all Wikimedia extensions updated every two weeks now?",1344463399,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #7)
+> Hmm, perhaps VisualEditor should have some kind of exposure of a version number
+> or last deployment date? Given the frequent deployments and code changes, I
+> think it'd be helpful for testing and bug-filing. I'm not sure if
+> Special:Version covers this already. Perhaps a separate bug is needed?
+> 
+Special:Version lists the git hash of the deployed version, which isn't perfect (and was out of date until just now). There is also a version number there which is currently just set to 0.1, I suppose we could start using that field, either by incrementing it each time or by using something like 0.1-20120806.
+
+Anyway, as for deployment frequency: not counting the fixup deployments that occurred yesterday because various things were broken, there is only one VE deployment every two weeks, on the first Monday of every deployment cycle. The most recent deployment was last Monday (Aug 6), the next one will be on Aug 20, then two weeks after that, etc. This is because our code comes along for the ride with the 1.20wmf* deployments (see https://www.mediawiki.org/wiki/MediaWiki_1.20/Roadmap for the schedule) and the only wiki where VE is currently deployed (mw.org) is part of phase 0, which occurs on the first Monday.
+
+Hope that clears things up a bit.",1344439874,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #5)
+> No. :-) Per http://wikitech.wikimedia.org/view/Software_deployments#Ongoing it
+> is scheduled to happen from 19 minutes' time, for up to three hours. Remarking
+> as resolved.
+
+I looked at <http://wikitech.wikimedia.org/view/Software_deployments#Ongoing> and its associated page history and I have no idea what this comment is referring to. There's no mention of VisualEditor on that page. The only mention of VisualEditor I can find is at <http://wikitech.wikimedia.org/view/Software_deployments/2012_archive> in an entry dated June 21.",1344393140,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #9)
+> Max - This bug is already explicitly tagged against a release milestone (this
+> last Monday's), as you'd see if you looked. :-)
+
+James, I saw the bug filer not being able to verify that the bug was fixed. That's more than enough to mark it as reopened. Start meeting your deployment schedule and provide a way to measure which version of VisualEditor is deployed (in addition to, you know, fixing the actual reported bug) and then you can comment about what I did or did not notice.",1344392173,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"Max - This bug is already explicitly tagged against a release milestone (this last Monday's), as you'd see if you looked. :-)
+
+Liangent - This is fixed and 'in live' as of yesterday, but unfortunately you won't be able to tell as bug 39111 has broken the link inspector entirely (sorry, we should have tested this before deployment). Will live-patch in the next few hours, at which point I'll ping back on this bug.",1344376920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #7)
+> Re-opening this bug for now. Until the bug filer can verify that the bug has
+> been fixed, it doesn't make much sense to mark it as such. We don't really use
+> ""verified"" in our current Bugzilla workflow, though perhaps we ought to in the
+> future.
+
+Some of us are using it, see bug 39040.",1344376044,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #6)
+> (In reply to comment #5)
+>> No. :-) Per http://wikitech.wikimedia.org/view/Software_deployments#Ongoing it
+>> is scheduled to happen from 19 minutes' time, for up to three hours. Remarking
+>> as resolved.
+> 
+> Is it deployed now so I can re-test these bugs?
+
+Hmm, perhaps VisualEditor should have some kind of exposure of a version number or last deployment date? Given the frequent deployments and code changes, I think it'd be helpful for testing and bug-filing. I'm not sure if Special:Version covers this already. Perhaps a separate bug is needed?
+
+Re-opening this bug for now. Until the bug filer can verify that the bug has been fixed, it doesn't make much sense to mark it as such. We don't really use ""verified"" in our current Bugzilla workflow, though perhaps we ought to in the future.",1344375713,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #5)
+> No. :-) Per http://wikitech.wikimedia.org/view/Software_deployments#Ongoing it
+> is scheduled to happen from 19 minutes' time, for up to three hours. Remarking
+> as resolved.
+
+Is it deployed now so I can re-test these bugs?",1344371737,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"No. :-) Per http://wikitech.wikimedia.org/view/Software_deployments#Ongoing it is scheduled to happen from 19 minutes' time, for up to three hours. Remarking as resolved.",1344274949,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"Ouch, did the deployment take place?",1344273953,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,Not fixed: https://www.mediawiki.org/w/index.php?title=VisualEditor:BugLinkSelection&diff=569584&oldid=569582,1344273914,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,Fixed and included in August 6th deployment.,1343672405,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,Mass-moving items into VisualEditor product,1340402747,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box","In ""Save page"" dialog, the content of message <minoredit> is not parsed and raw wikitext is displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340341320,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_description,resolved
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Confirmed that this is due to a local browser cache. Re-marking as fixed.,1344881831,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Where are you seeing this? This is working for me both on localhost and mw.org,1344541358,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box","Created attachment 10946
+Screenshot of raw wikitext for minor edit in save dialog
+
+**Attached**: {F9508}",1344485877,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",It's back.,1344485828,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Now deployed.,1343175512,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",minoredit fixed in https://gerrit.wikimedia.org/r/#/c/14603/,1341637400,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Also the watchthis message (Watch this page),1340431216,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Also other elements of the interface?,1340405611,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Mass-moving items into VisualEditor product,1340402730,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,"== section ==
+
+# number      <cursor pops up here>
+# number
+<enter>
+<enter>
+
+== <when you type, the cursor pops down here and starts editing> section ==
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340318220,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-7piycxpmx56ohmyj2zuk,task_description,declined
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,"**orbit** wrote:
+
+I wasn't able to reproduce in Chrome on Mac or Windows. We had some earlier problems with exiting lists after double-enter, so maybe this bug was reported then.",1341267913,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7piycxpmx56ohmyj2zuk,task_subcomment,NA
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,Mass-moving items into VisualEditor product,1340402778,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7piycxpmx56ohmyj2zuk,task_subcomment,NA
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,"I take that back, it's in Chrome 19.",1340318316,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-7piycxpmx56ohmyj2zuk,task_subcomment,NA
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,This is in Firefox 13.0.1,1340318274,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-7piycxpmx56ohmyj2zuk,task_subcomment,NA
+VisualEditor has broken delete behavior on end-of-file,"* Move cursor to last line of the page.
+* Delete till all subsequent empty lines are removed.
+* The next delete will remove the first character of the line and subsequent deletes delete larger chunks of text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340317440,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ryivokqumebwl4y5m3ua,task_description,resolved
+VisualEditor has broken delete behavior on end-of-file,"**orbit** wrote:
+
+Yep, this is a duplicate of 37813, which is now fixed.
+
+%%%*** This bug has been marked as a duplicate of bug 37813 ***%%%",1341267573,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ryivokqumebwl4y5m3ua,task_subcomment,NA
+VisualEditor has broken delete behavior on end-of-file,Mass-moving items into VisualEditor product,1340402773,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ryivokqumebwl4y5m3ua,task_subcomment,NA
+VisualEditor has broken delete behavior on end-of-file,Is this bug related to bug 37813?,1340396450,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ryivokqumebwl4y5m3ua,task_subcomment,NA
+VisualEditor has broken delete behavior on end-of-file,"Confirmed.
+
+When I press delete to remove the last character of the last line, I get:
+----
+Uncaught TypeError: Cannot read property 'node' of undefined ve.ce.Surface.js:847
+ve.ce.Surface.showSelection ve.ce.Surface.js:847
+ve.ce.Surface.onChange ve.ce.Surface.js:588
+jQuery.extend.proxy.proxy load.php:816
+ve.EventEmitter.emit ve.EventEmitter.js:33
+ve.dm.Surface.change ve.dm.Surface.js:88
+ve.ce.Surface.handleDelete ve.ce.Surface.js:753
+ve.ce.Surface.onKeyDown ve.ce.Surface.js:194
+jQuery.extend.proxy.proxy load.php:816
+jQuery.event.dispatch load.php:3332
+jQuery.event.add.elemData.handle.eventHandle
+----
+using Google Chrome 19.0.1084.56 on
+https://www.mediawiki.org/wiki/VisualEditor:Sandbox?debug=1
+
+Then, the cursor jumps to the beginning of the line. Subsequent delete will start removing the first characters.",1340334551,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ryivokqumebwl4y5m3ua,task_subcomment,NA
+VisualEditor: Text added to line below cursor,"Steps to reproduce:
+
+* Create a bunch of empty lines by hitting enter key
+* Move cursor up to the 1st/2nd empty line and start typing -- the first couple chars are inserted on the line below
+
+Can also reproduce this in other ways:
+* delete to end of line, enter a bunch of empty lines, move cursor to one of the middle empty lines and start typing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340316960,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-kpq3munittovusy35opj,task_description,declined
+VisualEditor: Text added to line below cursor,"**orbit** wrote:
+
+This probably was the case a while ago, but Inez has done a ton of work with typing in slugs. This isn't a problem any longer.",1350000047,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kpq3munittovusy35opj,task_subcomment,NA
+VisualEditor: Text added to line below cursor,Mass-moving items into VisualEditor product,1340402760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpq3munittovusy35opj,task_subcomment,NA
+VisualEditor: Lost text after deleting to/from EOF,"Steps to reproduce this on VE:
+
+* delete text to (or from) end of file using either backspace or delete key
+* type text and hit the return key,
+* the typed text is lost
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=37815",1340316720,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_description,resolved
+VisualEditor: Lost text after deleting to/from EOF,"**orbit** wrote:
+
+%%%*** Bug 37815 has been marked as a duplicate of this bug. ***%%%",1341267573,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_subcomment,NA
+VisualEditor: Lost text after deleting to/from EOF,"**orbit** wrote:
+
+This was fixed a little while ago, but was dropped due to a screwy merge. The fix has been recommitted:
+https://gerrit.wikimedia.org/r/13955",1341267341,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_subcomment,NA
+VisualEditor: Lost text after deleting to/from EOF,Re-assigning.,1341267286,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_subcomment,NA
+VisualEditor: Lost text after deleting to/from EOF,Mass-moving items into VisualEditor product,1340402734,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_subcomment,NA
+"VisualEditor: editing toolbar float trigger also triggers contextView icon, although there is no context to act on","When the editing toolbar trigger is triggered (either floating or defloating the editing toolbar), it also triggers the contextView icon to appear wherever the text cursor is, even if no text is selected. And of course you can't use any of the contextView tools while no text is selected. Once this occurs, subsequent interaction with the page is inconsistent. For example if you try to reposition the cursor it jumps back to the old location as soon as you start typing. Verified in Firefox and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1340315820,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ysuesdqax3nucpqxzzrl,task_description,resolved
+"VisualEditor: editing toolbar float trigger also triggers contextView icon, although there is no context to act on",Fixed in https://gerrit.wikimedia.org/r/13913,1341258696,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-ysuesdqax3nucpqxzzrl,task_subcomment,NA
+"VisualEditor: editing toolbar float trigger also triggers contextView icon, although there is no context to act on",Mass-moving items into VisualEditor product,1340402718,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ysuesdqax3nucpqxzzrl,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"**Author:** `dbaran`
+
+**Description:**
+Browser = Chrome 19.0.1084.56
+
+Clickstream:
+
+--used formatting toolbar to select bullet
+--entered single word
+--changed focus from browser to different window (skype I think)
+--changed focus back to browser by mousing back to bullet list
+--hit enter
+--nothing happened.  cursor didn't move.  
+
+
+I can reproduce consistently by typing in another window, then coming back to browser, and cursor will be stuck.  However if I perform some action in another tab of the browser, when I return to the tab in which I'm editing, the cursor works, although it requires hitting enter more than once.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7
+**Platform**: PC
+**URL**: https://internal.wikia-inc.com/wiki/New_Visual_Editor 	",1340314980,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gztnciutz4zkajephs5s,task_description,resolved
+VisualEditor: bullet list breaking after changing window focus,"**orbit** wrote:
+
+I committed some fixes for handling at the end of the document, which likely fixed this bug. I'm following the clickstream exactly and am unable to reproduce the problem. Daniel also showed me this bug on his computer, so I have a very good understanding of what the bug looked like.",1341002667,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,Reassigning per Christian's request.,1341002609,PHID-USER-p5svl2m3pqm6jjgznnhz,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,Mass-moving items into VisualEditor product,1340402715,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"**dbaran** wrote:
+
+No problemo.  Here's the errors with line numbers, and a detailed description of the actions I took:
+
+--loaded editor, placed cursor at end of bullet item (the word ""traffic"" at the very end of the article)
+--clicked away to skype, clicked back to browser with cursor still at end of list item, hit enter.  following error resulted:
+
+Uncaught TypeError: Cannot read property 'node' of undefined ve.ce.Surface.js:848
+
+hit enter again, and cursor moved down to beginning of next line, no bullet added.  hit backspace to return to previous line, following error resulted:
+
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.dm.Document.js:429
+
+Hit enter again, and cursor didn't move, following error resulted:
+
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.ce.Document.js:21
+
+hit enter a few more times, no cursor movement, and the following same errors:
+
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.ce.Document.js:21
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.ce.Document.js:21
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.ce.Document.js:21",1340316338,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"Sorry, I should have told you this earlier: could you please set ?debug=true at the end of the URL and try again? That should assign the real line numbers to the errors.",1340315636,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"**dbaran** wrote:
+
+right, should have done the the first time.  Errors as follows:
+
+Uncaught TypeError: Cannot read property 'node' of undefined bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:202
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:141
+2Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:179
+Uncaught TypeError: Cannot read property 'node' of undefined bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:202
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:141
+11Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:179
+Uncaught TypeError: Cannot read property 'node' of undefined bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:202
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:141
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:179",1340315455,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"Can you see any JS errors in the debugging console? To access this in Chrome, right-click anywhere on the page, selecting ""Inspect element"", then in the inspector that pops up at the bottom of the window go to the ""Console"" tab. If you see any error messages appear there, please post them here.",1340315147,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+"Hit Enter at the end of a heading, blinking cursor disappears","**Author:** `sumanah`
+
+**Description:**
+Cursor should show up where the red circle indicates
+
+I went to https://www.mediawiki.org/wiki/VisualEditor:Test , hit Edit, clicked just at the end of a heading (got a blinking cursor), and hit Enter. A newline appeared, but there was no blinking cursor to indicate where I was; the cursor had disappeared.
+
+I can replicate this.  Firefox 11.0, Firebug is off, Ubuntu 11.10.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9494}",1340314620,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nfo3xiyndruo5aeqves4,task_description,resolved
+"Hit Enter at the end of a heading, blinking cursor disappears",Noting bugs closed in the 2012-10-15 release.,1351534183,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nfo3xiyndruo5aeqves4,task_subcomment,NA
+"Hit Enter at the end of a heading, blinking cursor disappears",Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341823,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nfo3xiyndruo5aeqves4,task_subcomment,NA
+"Hit Enter at the end of a heading, blinking cursor disappears",Fixed in https://gerrit.wikimedia.org/r/12541,1340315734,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nfo3xiyndruo5aeqves4,task_subcomment,NA
+VisualEditor freaks out on <span>,"After I vandalised the test page with[1], trying to edit this page resulted in ""renderers[annotation.type] is undefined""
+
+var openAnnotations = function( annotations ) {
+    var out = '',
+        annotation;
+    for ( var hash in annotations ) {
+        annotation = annotations[hash];
+        out += typeof renderers[annotation.type].open === 'function' ? <-- here
+            renderers[annotation.type].open( annotation.data ) :
+            renderers[annotation.type].open;
+        hashStack.push( hash );
+        annotationStack[hash] = annotation;
+    }
+
+
+----
+[1] https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=552553&oldid=552537
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340314080,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-rjxemhifa3x2566jx3he,task_description,resolved
+VisualEditor freaks out on <span>,Noting bugs closed in the 2012-10-15 release.,1351534191,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rjxemhifa3x2566jx3he,task_subcomment,NA
+VisualEditor freaks out on <span>,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341837,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rjxemhifa3x2566jx3he,task_subcomment,NA
+VisualEditor freaks out on <span>,"Fixed in https://gerrit.wikimedia.org/r/12539 , pending review in Gerrit.",1340315424,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rjxemhifa3x2566jx3he,task_subcomment,NA
+VisualEditor freaks out on <span>,"Yeah, this is because span is listed as an annotation but has no renderer defined. Fixing.",1340314167,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rjxemhifa3x2566jx3he,task_subcomment,NA
+Backspace deletes more than one character on newly-added text,"If you type in something new using VisualEditor, and then you press the backspace key, you end up deleting all of what you wrote plus the character immediately before. This seems to delete about 3-5 characters at a time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340310360,PHID-USER-wqc7ciyvfzunj3l2tvjt,PHID-TASK-tdi5kkh4rg6wvf7cam7m,task_description,resolved
+Backspace deletes more than one character on newly-added text,"**orbit** wrote:
+
+I don't think this is actually about newly-added text, but rather deleting text after you'd switched windows and then came back to the editor. There was a bug in which event handling was bound twice, causing the double backspace problem. Fixed and will release soon.
+https://gerrit.wikimedia.org/r/#/c/12701/",1340404706,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tdi5kkh4rg6wvf7cam7m,task_subcomment,NA
+Backspace deletes more than one character on newly-added text,Mass-moving items into VisualEditor product,1340402759,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tdi5kkh4rg6wvf7cam7m,task_subcomment,NA
+Backspace deletes more than one character on newly-added text,Confirmed in Chrome on Mac OS X too.,1340389821,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tdi5kkh4rg6wvf7cam7m,task_subcomment,NA
+VisualEditor: Link box should suggest page titles,"The input box used to select target pages for links should display suggestions for pages, like WikiEditor's ""Insert link"" dialog box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1339495020,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-6qteafzaet5hssww25zp,task_description,resolved
+VisualEditor: Link box should suggest page titles,Fixed in https://gerrit.wikimedia.org/r/#/c/19784/,1345486519,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6qteafzaet5hssww25zp,task_subcomment,NA
+VisualEditor: Link box should suggest page titles,Standardise title.,1341257320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6qteafzaet5hssww25zp,task_subcomment,NA
+VisualEditor: Link box should suggest page titles,Mass-moving items into VisualEditor product,1340402775,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6qteafzaet5hssww25zp,task_subcomment,NA
+VisualEditor: Link box should suggest page titles,Bug 33053 is related.,1340333248,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-6qteafzaet5hssww25zp,task_subcomment,NA
+VisualEditor: npm dependencies,"New file to track npm dependencies
+
+This patch will make it simpler to install node module dependencies.  When the package.json file exists, running ""npm install"" with no arguments will create a directory ""node_modules"" and fetch dependencies.
+
+There are some related improvements to be made, such as editing the Makefile to point NODE_PATH to this directory.  Actually, I don't know what the recommended practice is here--seems like this should be in node's default require path.
+
+My focus was on running the tests, not sure about how to reuse this file for server configuration.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F9216}",1332324240,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-kil3chqyjneigkvf34lu,task_description,resolved
+VisualEditor: npm dependencies,Mass-moving bugs into the new 'Parsoid' product.,1344281146,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,"**wicke** wrote:
+
+Merged a while ago.",1340471199,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,Assuming this is for Gabriel,1340403596,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,Mass-moving items into VisualEditor product,1340402729,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,"What's the status of this bug?
+
+And can someone please clarify the bug summary? I have no idea what ""npm dependencies"" means.",1340396178,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,"**sumanah** wrote:
+
+Thanks for the patch, Adam! I've added keywords to indicate that this patch awaits code review.",1332356041,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"**Author:** `rahuldeshmukh101`
+
+**Description:**
+Is it possible to make Extension:Semantic Forms available on mr.wikipedia .
+
+If so please enable it for mr wiki.
+
+Thanks
+
+Rahul Deshmukh
+
+User:rahuldeshmukh101
+Admin mr.wikipedia
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1331345460,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6goh2k74apor363cgxbh,task_description,declined
+Enable Semantic Forms on mrwiki,"(In reply to comment #9)
+> RESOLVED INVALID: Author does not seem think this extension should be reviewed
+> for deployment, and I am not aware of any community consensus for this change.
+
+I would call that a wontfix...",1343163065,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"RESOLVED INVALID: Author does not seem think this extension should be reviewed for deployment, and I am not aware of any community consensus for this change.",1343163005,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"**rahuldeshmukh101** wrote:
+
+So what is the direction for next action from my side ?",1339117448,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,As I just wrote on the similar request for the Czech Wikipedia: I think the combination of the upcoming VisualEditor and Wikidata projects make this request obsolete - I don't believe there's any chance that Wikipedia will ever use Semantic Forms. (Unfortunately.),1339084567,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,So apparently the extension is not reviewed and labsconsole isn't in the cluster which is why it can have the extension. Added extension author to the CC list.,1339082215,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,I see Semantic Forms is deployed on labsconsole. Does that mean it's deployable elsewhere now? And is there consensus for this to be deployed on mrwiki?,1339078434,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"**rahuldeshmukh101** wrote:
+
+That I will put for opinion immediately. - Rahul",1331451811,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,Also needs community consensus.,1331354493,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"**rahuldeshmukh101** wrote:
+
+Please do the needful - Rahul",1331354390,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,Extension requires review before deployment can occur. It is currently not in a deployable state for wikimedia projects,1331347729,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,"Since incorrect date entry causes unnecessary work for other users, or new users to receive bot or user corrections, generally providing a negative experience, especially for new users. Additionally until fixed, this leads to inconsistencies in data. 
+
+Correcting these automatically, either at input time or post edit see — http://momentjs.com/",1415519616,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-j3ofm67egbuxxvm3t7el,task_description,invalid
+Polish : Date entry in citations should be automatically reformatted to community norms ,">>! In T1186#1006024, @Krenair wrote:
+> Which community's norms? Is this a Citoid thing? A VisualEditor thing?
+
+(Or Cite?)
+
+This still needs an answer.",1475422832,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,">>! In T1186#1006024, @Krenair wrote:
+> Which community's norms? Is this a Citoid thing? A VisualEditor thing?",1422906231,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,Other aspects of VE are site/language specific. I don't see why this would be significantly different. ,1422690738,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,Which community's norms? Is this a Citoid thing? A VisualEditor thing?,1422688635,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,Which Polish community norms? Is this a Citoid thing? A VisualEditor thing?,1422688546,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,"I didn't say it was easy, but I'm pretty sure its possible…",1421438873,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,"If I get this bug right, it's anything but easy...
+
+Also adding something like momentjs and having it run over the wikitext entered by users (how?) and then correcting invalid dates could be controversial as we never did something like that before.",1421434183,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+"VisualEditor / General project should be imported as simply ""VisualEditor""","It's just a catch-all component, and isn't needed.",1414164555,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_description,declined
+"VisualEditor / General project should be imported as simply ""VisualEditor""",">>! In T856#14542, @Qgil wrote:
+> Well, if there is a better decision we have still time to change it. What agreement are you referring to? That task got just too long with too many topics mixed.
+
+I was going by T43#641 and related comments, and didn't see T43#653 and later comments. Happy to stand by T43#653 and then change it afterwards.",1414171154,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_subcomment,NA
+"VisualEditor / General project should be imported as simply ""VisualEditor""","Well, if there is a better decision we have still time to change it. What agreement are you referring to? That task got just too long with too many topics mixed.",1414169492,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_subcomment,NA
+"VisualEditor / General project should be imported as simply ""VisualEditor""",">>! In T856#14469, @Qgil wrote:
+> The script applies common rules for everybody, as it was defined in {T43}.
+> 
+> I agree that ""VisualEditor"" is better. However, project owners can just apply changes like this after the migration. You will be able to fine tune the names of your projects, following the [[ https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Name | naming guidelines ]], or proposing improvements to the guidelines.
+
+Oh. After I thought that we had all agreed on what would be done in that task, the decision got reversed. :-( No wonder I was confused.",1414166779,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_subcomment,NA
+"VisualEditor / General project should be imported as simply ""VisualEditor""","The script applies common rules for everybody, as it was defined in {T43}.
+
+I agree that ""VisualEditor"" is better. However, project owners can just apply changes like this after the migration. You will be able to fine tune the names of your projects, following the [[ https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Name | naming guidelines ]], or proposing improvements to the guidelines.",1414165658,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","As a logged in user with beta access to VisualEditor using MobileFrontend, edit a new page on beta labs, e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Apsidufapodifuasdf or some such. 
+
+Click the pencil icon to edit the page.  I think this should bring up VE, but brings up wikitext editor instead. 
+
+From the gear menu, click Edit to invoke VE
+
+Again from the gear menu, click Edit source. 
+
+VE fails to disappear. Wikitext editor does not appear. No VE controls like Bold/Italic/Link etc. function at this point. 
+
+This is the failure at https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/455/testReport/(root)/VisualEditor%20Mobile/Switch_from_VisualEditor_to_source_editor/
+
+",1419890230,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-m7dvl6wigpdkychmqdou,task_description,resolved
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing",Verified in en.wiki,1421362417,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Thanks. VE on mobile is apparently still broken, tracked as T85897.",1420510122,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Change 182943 merged by Aude:
+Fix naming issue to restore ability to switch between editors
+
+[[https://gerrit.wikimedia.org/r/182943]]",1420505903,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Change 182943 had a related patch set uploaded (by Kaldari):
+Fix naming issue to restore ability to switch between editors
+
+[[https://gerrit.wikimedia.org/r/182943]]
+
+#patch-for-review",1420497926,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing",This probably needs some swift backporting to wmf13?,1420475395,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing",Verified in betalabs.  test2 still have problems with switching between Edit and Edit source.,1419985114,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Change 182113 merged by jenkins-bot:
+Fix naming issue to restore ability to switch between editors
+
+[[https://gerrit.wikimedia.org/r/182113]]",1419978869,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Change 182113 had a related patch set uploaded (by Jdlrobson):
+Fix naming issue to restore ability to switch between editors
+
+[[https://gerrit.wikimedia.org/r/182113]]
+
+#patch-for-review",1419895828,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","The following error is displayed: 
+Uncaught TypeError: boolean is not a functionload.php?debug=false&lang=en&modules=mobile.abusefilter|mobile.editor.common%2Coverlay&skin=minerva…:8 Overlay.extend.hideload.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cmwcore|mobile.editor.ve|oojs-ui&skin=m…:624 EditorOverlayBase.extend.hideVM367:16 Class.extend._hideOverlayVM367:17 Class.extend.replaceCurrentload.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cmwcore|mobile.editor.ve|oojs-ui&skin=m…:625 (anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:45 fireload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:46 self.fireWithload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:47 deferred.(anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:168 mw.loader.usingload.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cmwcore|mobile.editor.ve|oojs-ui&skin=m…:625 EditorOverlayBase.extend.switchToSourceEditorload.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cmwcore|mobile.editor.ve|oojs-ui&skin=m…:624 (anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:65 jQuery.event.dispatchload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:60 elemData.handle",1419891872,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+Uncaught TypeError when strating mobile VisualEditor,"ve.ui.Toolbar.js:224 Uncaught TypeError: Cannot read property 'triggerListener' of undefined
+
+Example: https://m.mediawiki.org/wiki/MediaWiki_1.25/Roadmap?debug=true#/editor/0",1419625243,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-mi6bk4kxywbgiufipreu,task_description,duplicate
+VisualEditor not loading in el.wikipedia,VisualEditor is not loading in el.wikipedia since yesterday.,1419072099,PHID-USER-e7gwd3ou5ocdumo42srg,PHID-TASK-u6ckhkexjtiftpwrkmpc,task_description,invalid
+VisualEditor not loading in el.wikipedia,Checked VE for el.wikipedia in production.,1419294837,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-u6ckhkexjtiftpwrkmpc,task_subcomment,NA
+VisualEditor not loading in el.wikipedia,Resolved by  [[https://el.wikipedia.org/w/index.php?title=MediaWiki:Common.js&diff=4979660&oldid=4917315|removing some code from Mediawiki:Common.js]] (although it was there for ages without problems).,1419079272,PHID-USER-e7gwd3ou5ocdumo42srg,PHID-TASK-u6ckhkexjtiftpwrkmpc,task_subcomment,NA
+Editing breaks and edit button does nothing after switching from VE to wikitext editor,"
+As a logged-in user with access to VisualEditor visit any page e.g http://en.m.wikipedia.beta.wmflabs.org/w/index.php?title=Selenium_Test_Edit
+
+Click Edit to bring up VE
+
+From the gear menu select Edit source
+
+No wikitext editor appears, but there is an edit icon on the page.
+
+Click the edit icon. It does nothing. ",1418926603,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5asnk76tj5m575vlprx3,task_description,duplicate
+VisualEditor broken for MobileFrontend,"Broken since 11 December. 
+
+As a logged in user with access to VE, attempt to edit any page.  See a spinner. 
+
+Javascript error shown in Chromium is ""TypeError: Illegal invocation TypeError: Illegal invocation ""
+
+",1418766721,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-3bmha7jwdg75jxh75rnj,task_description,resolved
+VisualEditor broken for MobileFrontend,verified the fix in en.wiki,1421362793,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,VE works in Mobile betalabs/test2. ,1420763452,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 182993 merged by Catrope:
+Update setupToolbar signature in mobile target
+
+[[https://gerrit.wikimedia.org/r/182993]]",1420560800,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 182993 had a related patch set uploaded (by Alex Monk):
+Update setupToolbar signature in mobile target
+
+[[https://gerrit.wikimedia.org/r/182993]]
+
+#patch-for-review",1420515801,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 181005 merged by MaxSem:
+Update VE and MF for T78710
+
+[[https://gerrit.wikimedia.org/r/181005]]",1418950655,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 181005 had a related patch set uploaded (by Jforrester):
+Update VE and MF for T78710
+
+[[https://gerrit.wikimedia.org/r/181005]]
+
+#patch-for-review",1418947774,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 180700 merged by jenkins-bot:
+Fix Ia6bf604c: Update another caller to ve.init.mw.Target
+
+[[https://gerrit.wikimedia.org/r/180700]]",1418947643,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 180701 merged by jenkins-bot:
+Followup Ia6bf604c, I431a9025: Update way VE target is constructed
+
+[[https://gerrit.wikimedia.org/r/180701]]",1418947639,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Parsoid was stalled to a version from October 28th :-(  Thanks to Krenair, Roan and Kartik we get it back to the latest version :-]",1418923498,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"(All the many different problems with Parsoid now seem to be fixed, thanks to @hashar)",1418911812,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"(Or at least, as well as the desktop version, which just returns a Parsoid error.)",1418902314,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,it should now work.,1418902160,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 180759 merged by jenkins-bot:
+Update setupToolbar signature in mobile target
+
+[[https://gerrit.wikimedia.org/r/180759]]",1418902072,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,(https://gerrit.wikimedia.org/r/180690 happened while Gerrit was down.),1418902069,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 180759 had a related patch set uploaded (by Alex Monk):
+Update setupToolbar signature in mobile target
+
+[[https://gerrit.wikimedia.org/r/180759]]
+
+#patch-for-review",1418901934,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Beta labs, sorry.",1418828869,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Production or beta labs?
+",1418779266,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Have triage sessions. Regarding topic, stakeholders and key developers, this will focus on VisualEditor and be on a weekly basis, and volunteers are very welcome:
+
+See Task 86867 for ""VisualEditor Q3 Release Criteria"".
+See https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=645421507#VisualEditor_News_2015.E2.80.94.231 for announcement.
+
+See https://www.mediawiki.org/wiki/Bug_management/Meeting_preparations for more information
+
+First bugday with Phabricator instead of Bugzilla.
+
+Potentially related Team-Practices tasks:
+* https://phabricator.wikimedia.org/T88325 - ""Whole team chat with Damon RE burndown chart expectations""
+* https://phabricator.wikimedia.org/T88328 - ""Feasibility study for using Phab for burndown charts""
+* https://phabricator.wikimedia.org/T88365 - ""Burndown chart training and support - VE release support with Editing Team""
+",1418751245,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lerurhal64ijhdssrwjz,task_description,resolved
+Have public bug day / triage sessions in February 2015 about VE,">>! In T78684#1049659, @Qgil wrote:
+> Should we consider setting the beginning of the sprint on Feb 1?
+
+According to James' answer in T89715: No. :)",1424354515,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"https://phabricator.wikimedia.org/project/sprint/view/1015/ With this fix and the Sprint upgrade, this page looks great now!
+
+@Jdforrester-WMF, why there is not visible progress during the whole month of January? Should we consider setting the beginning of the sprint on Feb 1?
+
+I'm being picky with this page because (as @damons explained at the MW Dev Summit) a burndown chart is a key communication tool, and I think we can push this page in all our VE sprint communications (also to editors etc). I guess people will wonder ""what happened in January?"", and this is why I'm asking.",1424352781,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,">>! In T78684#1046995, @Christopher wrote:
+> Also, I suspect that if for the  § VisualEditor Q3 Blockers project, if the ""Complete"" column is renamed to ""Done"" then all previous moves to this column will show on the burndown chart.
+
+[[ https://phabricator.wikimedia.org/project/sprint/view/1015/ | Done ]], thanks.",1424280700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Also, I suspect that if for the  § VisualEditor Q3 Blockers project, if the ""Complete"" column is renamed to ""Done"" then all previous moves to this column will show on the burndown chart.",1424280231,PHID-USER-lltif2drabccdkwhet7x,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"This is expected since the switch from Maniphest Status to Column Position.  To show progress in a Sprint, the normal workflow is to move the task to the ""Done"" column on the board.  This then deducts the points from ""Points Remaining"".  
+
+As mentioned in T88328, there are currently 4 static column ""type"" constants, ""Backlog"", ""Doing"", ""Review"" and ""Done"" that are recommended for the Sprint extension.   Teams are encouraged, but not required, to use these column names.  Future implementation may allow the possibility of user-defined names that map to these types, and perhaps additional column types.",1424279112,PHID-USER-lltif2drabccdkwhet7x,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Just a side question: is it normal that the ""remaining points"" line is not burning down at https://phabricator.wikimedia.org/project/sprint/view/1015/ ?
+
+CCing @christopher just in case.",1424278223,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"I'm not sure whether {T88198} is a pure blocker of this task, but there is a relationship.",1423474310,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Ok, I'm now convinced that we don't need to use an additional task for this process. Just keep in mind that not everybody will be able to follow at the same path, and some users might want to voice their opinions constructively in channels other than the phone call meeting. Let's be understanding and let's bring their relevant opinions to the triage meetings, as opposed to i.e. limiting ourselves to remind people about the official process.
+
+I'm pretty sure you were already planning to do this, but since we are running this type of process for the first time, I prefer to write this down somewhere.  :)",1423473152,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"I don't know. 
+In theory folks that unfortunately skipped communicating with product/project maintainers could already add the ""real"" Q3 project anyway without making sure that their addition is helpful from a ""let's get the stuff out"" maintainer prospective. 
+
+Folks could try to convince maintainers on IRC why some task is important enough before adding the task. 
+Or in the task itself. I'm not sure if that tag in addition to the comment itself would really help us (well, it might if noone reads all the incoming comments on all the VE tasks, to be honest). It might be yet another list that's as diverse as the list of all open tasks when it comes to importance; it might also be a way to get helpful feedback from folks that have good judgement what's important now - really hard for me to judge VE's community.",1423177662,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"@Jdforrester-WMF, when chatting with @aklapper about the VE weekly calls, I suggested the possibility of offering a temporary #VE-Q3-candidate tag of sorts to users willing to propose a specific task for the mega-sprint. The reason being that defending a proposal in English and in front of an unseen/unknown crowd during a synchronous phone call might deter some users. Even if a user plans to do so, being able to mark a task as candidate, explaining in the comments why, sounds like a good way to have a more productive meeting.
+
+What do you think?",1423035891,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Next triage should be targetting VisualEditor I guess.
+
+Notes to myself: https://phabricator.wikimedia.org/tag/%C2%A7_visualeditor_q3/ seems to be the current quarter (Using 'Q3' and no year and no description was not totally obvious though). [[ https://phabricator.wikimedia.org/sprint/board/1015/ | Workboard ]]; [[ https://phabricator.wikimedia.org/sprint/view/1015/ | Burndown chart ]] (not too readable).
+
+Generally speaking, there are currently 1152 open tickets in the umbrella VE project (which is automatically added for any subproject tasks). Also see the [[ https://phabricator.wikimedia.org/maniphest/report/project/ | Distribution of priorities of open tickets ]] (search for ""VisualEditor"").",1422300136,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Combine API requests required to load VE,"When I load VE on [[en:Gosford]], the following API requests are made:
+
+- 3x action=query&prop=imageinfo
+- 1x action=query&prop=info
+- 1x action=visualeditor&paction=parse (also see {T87553})
+
+For a total of five API requests. Couldn't the VisualEditor API module expose an endpoint that combines this metadata into a single response?",1418709771,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-umbcx7pdcw56w7fx2jhf,task_description,resolved
+Combine API requests required to load VE,"Change 193026 had a related patch set uploaded (by Jforrester):
+[WIP] Factor out loading code into TargetLoader
+
+[[https://gerrit.wikimedia.org/r/193026]]
+",1425330751,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-umbcx7pdcw56w7fx2jhf,task_subcomment,NA
+Combine API requests required to load VE,Also it's worth mentioning that only the action=visualeditor request blocks loading VE (which is reasonable because it delivers the Parsoid HTML). The prop=info and imageinfo requests do not block loading.,1418727693,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-umbcx7pdcw56w7fx2jhf,task_subcomment,NA
+Combine API requests required to load VE,"This is a duplicate of several tickets, and should probably become a tracking ticket. I'll find them and make them all subtasks of this one.",1418725652,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-umbcx7pdcw56w7fx2jhf,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Clicking on ""Advanced"" search and changing the default namespaces to search and clicking search returns:
+
+``` lines=10
+""Exception thrown by mediawiki.special.search"" load.php:150
+""TypeError: this.form is null"" TypeError: this.form is null
+Stack trace:
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:2:185
+jQuery.event.dispatch@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:65:771
+jQuery.event.add/elemData.handle@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:60:313
+jQuery.event.trigger@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:64:460
+.trigger/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:75:425
+.each@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:5:216
+jQuery.prototype.each@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:2:215
+.trigger@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:75:404
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:2:130
+jQuery.Callbacks/fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:44:928
+jQuery.Callbacks/self.add@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:45:488
+jQuery.fn.ready@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:48:879
+jQuery.fn.init@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:41:68
+jQuery@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:1:637
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:1:84
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:1:1
+runScript@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:160:473
+execute/</checkCssHandles@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:160:958
+execute/</cssHandle/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:161:96
+jQuery.Callbacks/fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:44:928
+jQuery.Callbacks/self.fireWith@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:46:258
+jQuery.Callbacks/self.fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:46:301
+addEmbeddedCSS@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:155:871
+execute@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:161:552
+mw.loader</<.implement@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:168:145
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:42:29
+.globalEval/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:4:655
+.globalEval@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:4:621
+mw.loader</<.work@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:164:68
+request@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:162:258
+mw.loader</<.load@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:169:720
+@https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=mw.util.addPortletLink&fulltext=Search:248:1
+```",1418658101,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-zooes6fkunmcss2rmnar,task_description,resolved
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Indeed, the click event was getting unbound, because local site JS was rewriting some `.innerHTML` properties (which has the side-effect of killing everything that's not in initial HTML, like event handlers and inputted form field values). I removed one line: https://zh.wiktionary.org/w/index.php?title=MediaWiki:Common.js&diff=prev&oldid=4074338 and it seems to be working. If any other sites have the same problem, doing this will probably help them too.",1421434986,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,I believe its 100% js but I dunno - I just know I'm like a bull in a china shop with browser debugging.,1421422486,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Hmm, wondering who could investigate the JS part then... any idea?",1421420621,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Unassigning to myself as I can't figure it out and Javascript isn't my forte.  It looks like the click event is getting unbound from the button after its creation.  This returns undefined:
+$._data($('#mw-search-toggleall')[0], 'events')
+on the wikis that don't work.",1421420555,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,The all/none buttons still work on zhwikipedia but do not on zhwikibooks or zhwiktionary.....,1421418940,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Also - its clicking the buttons that is broken.  Clicking on the check boxes still seems to work.,1421418747,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Reopened - it is indeed broken on zhwiktionary but not enwiktionary.  No idea why yet.,1421418691,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#981797, @Aklapper wrote:
+> @Liuxinyu970226: Can you provide a link / steps to reproduce please?
+
+Try ""全选 (all)"" & ""全不选 (none)"" at:
+* https://zh.wiktionary.org/w/index.php?title=Special:搜索&search=asdfg&fulltext=搜索&profile=advanced
+* https://zh.wikibooks.org/w/index.php?title=Special:搜索&search=asdfg&fulltext=搜索&profile=advanced",1421416049,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,@Liuxinyu970226: Can you provide a link / steps to reproduce please?,1421415812,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Can't work again on zhwiktionary and zhwikibooks, who can help them.",1421371291,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Can't work again on zhwiktionary and zhwikibooks,1421371261,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#931954, @Liuxinyu970226 wrote:
+> @Nikerabbit: Keeps on translatewiki, u know.
+
+OK now tsw fixed too.",1419687072,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"@Nikerabbit: Keeps on translatewiki, u know.",1418894001,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Verified on mw.org,1418832951,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Change 180319 merged by jenkins-bot:
+Move advanced search inputs back into the form
+
+[[https://gerrit.wikimedia.org/r/180319]]",1418832552,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"
+
+>>! In T78553#852344, @Krinkle wrote:
+> This isn't just causing a user scripts or extensions to throw an exception due to elements not existing in javascript land. The core feature itself is also plain broken.
+> 
+> 1. https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=formsGadgetConfig&fulltext=Search
+> 2. Tick/untick any namespace checkboxes.
+> 3. Press ""Search""
+> 
+> Expected: Search results now include different results and namespace selection is there as the user submitted it
+> 
+> Actual: The checkboxes not being part of the `<form>` means they're not submitted and completely ignored by the server. The advanced search is completely non-functional.
+
+Thanks for making that clear.  I didn't do a good job of documenting how broken it was.  I took a stab at it in https://phabricator.wikimedia.org/T78553#849773 but wasn't super clear.  The change to fix it is scheduled to by SWATed tonight.",1418782122,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"This isn't just causing a user scripts or extensions to throw an exception due to elements not existing in javascript land. The core feature itself is also plain broken.
+
+1. https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=formsGadgetConfig&fulltext=Search
+2. Tick/untick any namespace checkboxes.
+3. Press ""Search""
+
+Expected: Search results now include different results and namespace selection is there as the user submitted it
+
+Actual: The checkboxes not being part of the `<form>` means they're not submitted and completely ignored by the server. The advanced search is completely non-functional.",1418781672,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"This isn't just causing a user script exception due to elements not existing. The core feature is also plain broken.
+
+1. https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=formsGadgetConfig&fulltext=Search
+2. Tick/untick any namespace checkboxes.
+3. Press ""Search""
+
+Expected: Search results now include different results and namespace selection is there as the user submitted it
+
+Actual: The checkboxes not being part of the `<form>` means they're not submitted and completely ignored by the server. The advanced search is completely non-functional.",1418781623,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Evening swat deployment scheduled: https://wikitech.wikimedia.org/w/index.php?title=Deployments&oldid=138343,1418768313,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Change 180319 had a related patch set uploaded (by Robmoen):
+Move advanced search inputs back into the form
+
+[[https://gerrit.wikimedia.org/r/180319]]
+
+#patch-for-review",1418767649,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Change 180237 merged by jenkins-bot:
+Move advanced search inputs back into the form
+
+[[https://gerrit.wikimedia.org/r/180237]]",1418762135,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,,1418758615,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,,1418758578,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Change 180237 had a related patch set uploaded (by Robmoen):
+Move advanced search inputs back into the form
+
+[[https://gerrit.wikimedia.org/r/180237]]
+
+#patch-for-review",1418758535,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Awesome!  Can you link it here?  We can certainly SWAT it tomorrow morning or this afternoon if we can get it reviewed ASAP.,1418758475,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#851447, @Manybubbles wrote:
+> Do they have to be logged in?  Not that it really matters.  Is it something you can fix in an hour or two?  If so we should just fix it I think
+
+Agreed.  I have identified a fix.",1418757869,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Do they have to be logged in?  Not that it really matters.  Is it something you can fix in an hour or two?  If so we should just fix it I think,1418757680,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#850699, @Manybubbles wrote:
+> Reassigning to rmoen as its very likely related to Ic6ec29817ab7deadc6bc7125f8b4cd16686baa04.  I don't want to just revert his work because it looks like it has some value.  If he isn't able to pick this up in a few hours I will just revert it so we can have advanced search back.
+
+The breaking change should be reverted as turns out it breaks the entire advanced search form for logged in users.  However, I have an easy fix for all of this.",1418757817,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#850699, @Manybubbles wrote:
+> Reassigning to rmoen as its very likely related to Ic6ec29817ab7deadc6bc7125f8b4cd16686baa04.  I don't want to just revert his work because it looks like it has some value.  If he isn't able to pick this up in a few hours I will just revert it so we can have advanced search back.
+
+The breaking change should be reverted as turns out it breaks the entire advanced search form for logged in users.  ",1418757629,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Reassigning to rmoen as its very likely related to Ic6ec29817ab7deadc6bc7125f8b4cd16686baa04.  I don't want to just revert his work because it looks like it has some value.  If he isn't able to pick this up in a few hours I will just revert it so we can have advanced search back.,1418744783,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,I'm going to grab this.  I'm not particularly well qualified for it so if a Javascript expert wants it feel free to trump me.  I just think it needs looking at sooner rather than later.,1418743413,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"NOTE: In case it matters; excerpt from the recently merged duplicate T78636
+
+**Confirmed** ... reproduced behavior on both __www.MediaWiki.org__ and __test2.wikipedia.org__ `[1.25wmf12 (1d22bb3)]` at the moment.
+
+I could not reproduce this behavior (selecting //none// or //all// executes as expected) on __en.wikipedia.org__ or __en.wikisource.org__ `[1.25wmf11 (038c7a8)]` however.",1418740716,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"> The check all/none buttons do nothing. If I check or uncheck any of the namespace check boxes and then hit search to refine my search, the checkboxes revert to default and my results do not change.
+
+I see that too.",1418696238,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"There are no specific steps, just loading the page brings up that error.  Okay, I refresh the page with my console open and my Network, JS, and Security logs checked and I get:
+
+``` lines=15
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 580ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 470ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 528ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 522ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 561ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 634ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 675ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 683ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 761ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 752ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 889ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 787ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 1840ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 861ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 892ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 2545ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 134ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 281ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 255ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 293ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 377ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 258ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.lib.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralAuth/modules/ext.centralauth.centralautologin.clearcookie.js [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 102ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 124ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/lib/ve/src/ve.js [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/lib/ve/src/ve.track.js [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.byteLength.js [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.client.js [HTTP/1.1 200 OK 176ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery/jquery.cookie.js [HTTP/1.1 200 OK 149ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.css [HTTP/1.1 200 OK 148ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.js [HTTP/1.1 200 OK 212ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.mwExtension.js [HTTP/1.1 200 OK 147ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.accessKeyLabel.js [HTTP/1.1 200 OK 156ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.tabIndex.js [HTTP/1.1 200 OK 203ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery/jquery.ba-throttle-debounce.js [HTTP/1.1 200 OK 265ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 611ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery.tipsy/jquery.tipsy.js [HTTP/1.1 200 OK 283ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.notify.js [HTTP/1.1 200 OK 226ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.util.js [HTTP/1.1 200 OK 314ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.js [HTTP/1.1 200 OK 273ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.Title.js [HTTP/1.1 200 OK 348ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.Uri.js [HTTP/1.1 200 OK 388ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/EventLogging/modules/ext.eventLogging.core.js [HTTP/1.1 200 OK 354ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.css [HTTP/1.1 200 OK 349ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.init.js [HTTP/1.1 200 OK 383ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.init.js [HTTP/1.1 200 OK 439ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 457ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.legacy/wikibits.js [HTTP/1.1 200 OK 426ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.legacy/ajax.js [HTTP/1.1 200 OK 444ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 502ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 522ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.libs/CLDRPluralRuleParser.js [HTTP/1.1 200 OK 496ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.cldr.js [HTTP/1.1 200 OK 506ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.js [HTTP/1.1 200 OK 511ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.numbers.js [HTTP/1.1 200 OK 587ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.fallback.js [HTTP/1.1 200 OK 583ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.jqueryMsg.js [HTTP/1.1 200 OK 733ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.startup.js [HTTP/1.1 200 OK 586ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 615ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/collapsibleTabs.js [HTTP/1.1 200 OK 648ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/vector.js [HTTP/1.1 200 OK 657ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 712ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.user.js [HTTP/1.1 200 OK 657ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VectorBeta/resources/compactPersonalBar/trackClick.js [HTTP/1.1 200 OK 668ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VectorBeta/resources/compactPersonalBar/defaultTracking.js [HTTP/1.1 200 OK 741ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/modules/ve-mw/init/styles/ve.init.mw.ViewPageTarget.init.css [HTTP/1.1 200 OK 741ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js [HTTP/1.1 200 OK 873ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.preferences.js [HTTP/1.1 200 OK 744ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.webfonts.js [HTTP/1.1 200 OK 767ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.interface.js [HTTP/1.1 200 OK 795ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/120px-Foo.jpg [HTTP/1.1 200 OK 584ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Foo.svg/120px-Foo.svg.png [HTTP/1.1 200 OK 583ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/f/f5/Foo_2.png/120px-Foo_2.png [HTTP/1.1 200 OK 665ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/43/Foo_1.jpg/120px-Foo_1.jpg [HTTP/1.1 200 OK 751ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/8/8e/Mei_Foo_Sun_Chuen_Map.svg/120px-Mei_Foo_Sun_Chuen_Map.svg.png [HTTP/1.1 200 OK 662ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/48/Foo_Fighters_acoustic.jpg/120px-Foo_Fighters_acoustic.jpg [HTTP/1.1 200 OK 663ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/49/Foo_Fighters.jpg/120px-Foo_Fighters.jpg [HTTP/1.1 200 OK 932ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/Foo_1.png/120px-Foo_1.png [HTTP/1.1 200 OK 895ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/6/6b/Jane_McGonigal%2C_Foo_Camp.jpg/102px-Jane_McGonigal%2C_Foo_Camp.jpg [HTTP/1.1 200 OK 888ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/d/d8/Foo_Fighters_%28Logo%29.png/120px-Foo_Fighters_%28Logo%29.png [HTTP/1.1 200 OK 890ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/e/e3/Jane_McGonigal_Foo_Camp_2008.jpg/120px-Jane_McGonigal_Foo_Camp_2008.jpg [HTTP/1.1 200 OK 902ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/5/56/Mei_Foo_exit_A.jpeg/120px-Mei_Foo_exit_A.jpeg [HTTP/1.1 200 OK 884ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/e/e8/The_view_of_Mei_Foo_Skatepark_From_Entrance.jpeg/120px-The_view_of_Mei_Foo_Skatepark_From_Entrance.jpeg [HTTP/1.1 200 OK 442ms]
+GET https://bits.wikimedia.org/images/wikimedia-button.png [HTTP/1.1 200 OK 244ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/assets/poweredby_mediawiki_88x31.png [HTTP/1.1 200 OK 564ms]
+GET https://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png [HTTP/1.1 200 OK 544ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 242ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 98ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 1657ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 484ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 537ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 434ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.js [HTTP/1.1 200 OK 318ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/css/jquery.ime.css [HTTP/1.1 200 OK 316ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/jquery.ime.js [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.data.js [HTTP/1.1 200 OK 391ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.grid.css [HTTP/1.1 200 OK 372ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.messagestore.js [HTTP/1.1 200 OK 722ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.data.utils.js [HTTP/1.1 200 OK 727ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.core.css [HTTP/1.1 200 OK 645ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.theme.css [HTTP/1.1 200 OK 651ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.core.js [HTTP/1.1 200 OK 648ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.position.js [HTTP/1.1 200 OK 716ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.widget.js [HTTP/1.1 200 OK 721ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.parser.js [HTTP/1.1 200 OK 174ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.button.css [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.button.js [HTTP/1.1 200 OK 172ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.mouse.js [HTTP/1.1 200 OK 108ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/EventLogging/modules/ext.eventLogging.subscriber.js [HTTP/1.1 200 OK 59ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 113ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 102ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 117ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 104ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 232ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 168ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 120ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 173ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 219ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 213ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.sendBeacon.js [HTTP/1.1 200 OK 164ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.pt.css [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.deprecate.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.statsd.js [HTTP/1.1 200 OK 91ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.checkboxShiftClick.js [HTTP/1.1 200 OK 90ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.getAttrs.js [HTTP/1.1 200 OK 94ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.hidpi.js [HTTP/1.1 200 OK 117ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.highlightText.js [HTTP/1.1 200 OK 123ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.makeCollapsible.css [HTTP/1.1 200 OK 136ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.makeCollapsible.js [HTTP/1.1 200 OK 199ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.mw-jump.js [HTTP/1.1 200 OK 147ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.placeholder.js [HTTP/1.1 200 OK 149ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.action/mediawiki.action.view.rightClickEdit.js [HTTP/1.1 200 OK 167ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.watch.js [HTTP/1.1 200 OK 152ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.special/mediawiki.special.search.css [HTTP/1.1 200 OK 173ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.special/mediawiki.special.search.js [HTTP/1.1 200 OK 180ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 275ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 237ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 2994ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 250ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 307ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 651ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 414ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.emitter.js [HTTP/1.1 200 OK 269ms]
+GET https://commons.wikimedia.org/w/index.php [HTTP/1.1 200 OK 1076ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/images/icon-language.svg [HTTP/1.1 200 OK 655ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 931ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.draggable.js [HTTP/1.1 200 OK 873ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.resizable.css [HTTP/1.1 200 OK 338ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.resizable.js [HTTP/1.1 200 OK 867ms]
+TypeError: this.form is null mediawiki.special.search.js:53
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.hidpi.js [HTTP/1.1 200 OK 89ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.suggestions.css [HTTP/1.1 200 OK 96ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.suggestions.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.ready.js [HTTP/1.1 200 OK 86ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.watch.ajax.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.eventlogger.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.language.js [HTTP/1.1 200 OK 442ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/NavigationTiming/modules/ext.navigationTiming.js [HTTP/1.1 200 OK 432ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.searchSuggest.css [HTTP/1.1 200 OK 59ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.searchSuggest.js [HTTP/1.1 200 OK 60ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 145ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.dialog.css [HTTP/1.1 200 OK 69ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.dialog.js [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/NavigationTiming/modules/ext.navigationTiming.HHVM.js [HTTP/1.1 200 OK 63ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.i18n.js [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.css [HTTP/1.1 200 OK 63ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.lcd.css [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.core.js [HTTP/1.1 200 OK 213ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 138ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 112ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.lcd.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 96ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/base/ext.echo.base.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.languagefilter.js [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/overlay/ext.echo.overlay.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.regionfilter.js [HTTP/1.1 200 OK 61ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/overlay/ext.echo.overlay.init.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.mediawiki.js [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.ime.js [HTTP/1.1 200 OK 60ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 140ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/images/ime-active.svg [HTTP/1.1 200 OK 202ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/images/tick.svg [HTTP/1.1 200 OK 200ms]
+GET https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 210ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.buttons.css [HTTP/1.1 200 OK 60ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.languagesettings.css [HTTP/1.1 200 OK 61ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.languagesettings.js [HTTP/1.1 200 OK 64ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.parse.js [HTTP/1.1 200 OK 62ms]
+POST https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 2427ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.displaysettings.css [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.displaysettings.js [HTTP/1.1 200 OK 127ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.inputsettings.css [HTTP/1.1 200 OK 76ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.inputsettings.js [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/images/close.svg [HTTP/1.1 200 OK 298ms]
+```
+
+The check all/none buttons do nothing.  If I check or uncheck any of the namespace check boxes and then hit search to refine my search, the checkboxes revert to default and my results do not change.",1418671562,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"There are no specific steps, just loading the page brings up that error.  Okay, I refresh the page with my console open and my Network, JS, and Security logs checked and I get:
+
+```
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 580ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 470ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 528ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 522ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 561ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 634ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 675ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 683ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 761ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 752ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 889ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 787ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 1840ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 861ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 892ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 2545ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 134ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 281ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 255ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 293ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 377ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 258ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.lib.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralAuth/modules/ext.centralauth.centralautologin.clearcookie.js [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 102ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 124ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/lib/ve/src/ve.js [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/lib/ve/src/ve.track.js [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.byteLength.js [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.client.js [HTTP/1.1 200 OK 176ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery/jquery.cookie.js [HTTP/1.1 200 OK 149ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.css [HTTP/1.1 200 OK 148ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.js [HTTP/1.1 200 OK 212ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.mwExtension.js [HTTP/1.1 200 OK 147ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.accessKeyLabel.js [HTTP/1.1 200 OK 156ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.tabIndex.js [HTTP/1.1 200 OK 203ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery/jquery.ba-throttle-debounce.js [HTTP/1.1 200 OK 265ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 611ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery.tipsy/jquery.tipsy.js [HTTP/1.1 200 OK 283ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.notify.js [HTTP/1.1 200 OK 226ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.util.js [HTTP/1.1 200 OK 314ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.js [HTTP/1.1 200 OK 273ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.Title.js [HTTP/1.1 200 OK 348ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.Uri.js [HTTP/1.1 200 OK 388ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/EventLogging/modules/ext.eventLogging.core.js [HTTP/1.1 200 OK 354ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.css [HTTP/1.1 200 OK 349ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.init.js [HTTP/1.1 200 OK 383ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.init.js [HTTP/1.1 200 OK 439ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 457ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.legacy/wikibits.js [HTTP/1.1 200 OK 426ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.legacy/ajax.js [HTTP/1.1 200 OK 444ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 502ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 522ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.libs/CLDRPluralRuleParser.js [HTTP/1.1 200 OK 496ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.cldr.js [HTTP/1.1 200 OK 506ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.js [HTTP/1.1 200 OK 511ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.numbers.js [HTTP/1.1 200 OK 587ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.fallback.js [HTTP/1.1 200 OK 583ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.jqueryMsg.js [HTTP/1.1 200 OK 733ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.startup.js [HTTP/1.1 200 OK 586ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 615ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/collapsibleTabs.js [HTTP/1.1 200 OK 648ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/vector.js [HTTP/1.1 200 OK 657ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 712ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.user.js [HTTP/1.1 200 OK 657ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VectorBeta/resources/compactPersonalBar/trackClick.js [HTTP/1.1 200 OK 668ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VectorBeta/resources/compactPersonalBar/defaultTracking.js [HTTP/1.1 200 OK 741ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/modules/ve-mw/init/styles/ve.init.mw.ViewPageTarget.init.css [HTTP/1.1 200 OK 741ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js [HTTP/1.1 200 OK 873ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.preferences.js [HTTP/1.1 200 OK 744ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.webfonts.js [HTTP/1.1 200 OK 767ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.interface.js [HTTP/1.1 200 OK 795ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/120px-Foo.jpg [HTTP/1.1 200 OK 584ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Foo.svg/120px-Foo.svg.png [HTTP/1.1 200 OK 583ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/f/f5/Foo_2.png/120px-Foo_2.png [HTTP/1.1 200 OK 665ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/43/Foo_1.jpg/120px-Foo_1.jpg [HTTP/1.1 200 OK 751ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/8/8e/Mei_Foo_Sun_Chuen_Map.svg/120px-Mei_Foo_Sun_Chuen_Map.svg.png [HTTP/1.1 200 OK 662ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/48/Foo_Fighters_acoustic.jpg/120px-Foo_Fighters_acoustic.jpg [HTTP/1.1 200 OK 663ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/49/Foo_Fighters.jpg/120px-Foo_Fighters.jpg [HTTP/1.1 200 OK 932ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/Foo_1.png/120px-Foo_1.png [HTTP/1.1 200 OK 895ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/6/6b/Jane_McGonigal%2C_Foo_Camp.jpg/102px-Jane_McGonigal%2C_Foo_Camp.jpg [HTTP/1.1 200 OK 888ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/d/d8/Foo_Fighters_%28Logo%29.png/120px-Foo_Fighters_%28Logo%29.png [HTTP/1.1 200 OK 890ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/e/e3/Jane_McGonigal_Foo_Camp_2008.jpg/120px-Jane_McGonigal_Foo_Camp_2008.jpg [HTTP/1.1 200 OK 902ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/5/56/Mei_Foo_exit_A.jpeg/120px-Mei_Foo_exit_A.jpeg [HTTP/1.1 200 OK 884ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/e/e8/The_view_of_Mei_Foo_Skatepark_From_Entrance.jpeg/120px-The_view_of_Mei_Foo_Skatepark_From_Entrance.jpeg [HTTP/1.1 200 OK 442ms]
+GET https://bits.wikimedia.org/images/wikimedia-button.png [HTTP/1.1 200 OK 244ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/assets/poweredby_mediawiki_88x31.png [HTTP/1.1 200 OK 564ms]
+GET https://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png [HTTP/1.1 200 OK 544ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 242ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 98ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 1657ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 484ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 537ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 434ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.js [HTTP/1.1 200 OK 318ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/css/jquery.ime.css [HTTP/1.1 200 OK 316ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/jquery.ime.js [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.data.js [HTTP/1.1 200 OK 391ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.grid.css [HTTP/1.1 200 OK 372ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.messagestore.js [HTTP/1.1 200 OK 722ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.data.utils.js [HTTP/1.1 200 OK 727ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.core.css [HTTP/1.1 200 OK 645ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.theme.css [HTTP/1.1 200 OK 651ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.core.js [HTTP/1.1 200 OK 648ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.position.js [HTTP/1.1 200 OK 716ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.widget.js [HTTP/1.1 200 OK 721ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.parser.js [HTTP/1.1 200 OK 174ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.button.css [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.button.js [HTTP/1.1 200 OK 172ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.mouse.js [HTTP/1.1 200 OK 108ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/EventLogging/modules/ext.eventLogging.subscriber.js [HTTP/1.1 200 OK 59ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 113ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 102ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 117ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 104ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 232ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 168ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 120ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 173ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 219ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 213ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.sendBeacon.js [HTTP/1.1 200 OK 164ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.pt.css [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.deprecate.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.statsd.js [HTTP/1.1 200 OK 91ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.checkboxShiftClick.js [HTTP/1.1 200 OK 90ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.getAttrs.js [HTTP/1.1 200 OK 94ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.hidpi.js [HTTP/1.1 200 OK 117ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.highlightText.js [HTTP/1.1 200 OK 123ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.makeCollapsible.css [HTTP/1.1 200 OK 136ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.makeCollapsible.js [HTTP/1.1 200 OK 199ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.mw-jump.js [HTTP/1.1 200 OK 147ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.placeholder.js [HTTP/1.1 200 OK 149ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.action/mediawiki.action.view.rightClickEdit.js [HTTP/1.1 200 OK 167ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.watch.js [HTTP/1.1 200 OK 152ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.special/mediawiki.special.search.css [HTTP/1.1 200 OK 173ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.special/mediawiki.special.search.js [HTTP/1.1 200 OK 180ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 275ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 237ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 2994ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 250ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 307ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 651ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 414ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.emitter.js [HTTP/1.1 200 OK 269ms]
+GET https://commons.wikimedia.org/w/index.php [HTTP/1.1 200 OK 1076ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/images/icon-language.svg [HTTP/1.1 200 OK 655ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 931ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.draggable.js [HTTP/1.1 200 OK 873ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.resizable.css [HTTP/1.1 200 OK 338ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.resizable.js [HTTP/1.1 200 OK 867ms]
+TypeError: this.form is null mediawiki.special.search.js:53
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.hidpi.js [HTTP/1.1 200 OK 89ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.suggestions.css [HTTP/1.1 200 OK 96ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.suggestions.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.ready.js [HTTP/1.1 200 OK 86ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.watch.ajax.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.eventlogger.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.language.js [HTTP/1.1 200 OK 442ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/NavigationTiming/modules/ext.navigationTiming.js [HTTP/1.1 200 OK 432ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.searchSuggest.css [HTTP/1.1 200 OK 59ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.searchSuggest.js [HTTP/1.1 200 OK 60ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 145ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.dialog.css [HTTP/1.1 200 OK 69ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.dialog.js [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/NavigationTiming/modules/ext.navigationTiming.HHVM.js [HTTP/1.1 200 OK 63ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.i18n.js [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.css [HTTP/1.1 200 OK 63ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.lcd.css [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.core.js [HTTP/1.1 200 OK 213ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 138ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 112ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.lcd.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 96ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/base/ext.echo.base.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.languagefilter.js [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/overlay/ext.echo.overlay.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.regionfilter.js [HTTP/1.1 200 OK 61ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/overlay/ext.echo.overlay.init.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.mediawiki.js [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.ime.js [HTTP/1.1 200 OK 60ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 140ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/images/ime-active.svg [HTTP/1.1 200 OK 202ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/images/tick.svg [HTTP/1.1 200 OK 200ms]
+GET https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 210ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.buttons.css [HTTP/1.1 200 OK 60ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.languagesettings.css [HTTP/1.1 200 OK 61ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.languagesettings.js [HTTP/1.1 200 OK 64ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.parse.js [HTTP/1.1 200 OK 62ms]
+POST https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 2427ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.displaysettings.css [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.displaysettings.js [HTTP/1.1 200 OK 127ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.inputsettings.css [HTTP/1.1 200 OK 76ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.inputsettings.js [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/images/close.svg [HTTP/1.1 200 OK 298ms]
+```
+
+The check all/none buttons do nothing.  If I check or uncheck any of the namespace check boxes and then hit search to refine my search, the checkboxes revert to default and my results do not change.",1418670812,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"I simply cannot get see any stacktrace rendered in my browser - I get 1076 results for your link and nothing that makes it look like something really important is broken here. Could you elaborate?
+
+I can confirm that there's error output in the browser console, triggered by this line:
+  this.form.method = this.checked ? 'post' : 'get';
+from https://git.wikimedia.org/history/mediawiki%2Fcore.git/HEAD/resources%2Fsrc%2Fmediawiki.special%2Fmediawiki.special.search.js which hasn't seen recent changes.",1418669421,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+
+  lang= javascript, lines=10
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418671396,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+lang= javascript, lines=10
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418671347,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+lines=10
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+...
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418671289,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+lines=10
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418671261,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418665273,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"> Clicking on ""Advanced"" search and changing the default namespaces to search and clicking search returns:
+
+Please provide //exact// steps to reproduce. I cannot reproduce the problem using https://www.mediawiki.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced but the steps are simply too vague. Using &debug=true is also very welcome.",1418663601,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors","Recently, there has been a rapid increase in errors like:
+
+```
+Sorry! This site is experiencing technical difficulties.
+
+Try waiting a few minutes and reloading.
+
+(Cannot contact the database server: Too many connections (208.80.154.18))
+```
+
+This happens not only when I open dozens of wikitech pages, but also when I reload single pages afterwards.",1418544923,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-6welbf6ni6cfb2mlnvar,task_description,resolved
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors","This has stopped happening now that wikitech is on silver, safely away from puppet's vandalism.",1424571360,PHID-USER-22bsa5u75jz3ci3wnplu,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors","… and they come from the Puppet extension, so that's fine.  I think the problem lies in the interface MediaWiki/MySQL.  7 hits/11 s shouldn't bring a wiki down; perhaps some connection pool not set up or something like that?
+
+(@yuvipanda: BTW, totally forgot: Congrats! :-))",1418642169,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors",All the Hiera hits are from the puppetmaster,1418631203,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors",Most likely the issue here is that the main cluster robots.txt is more tolerant of crawlers than wikitech can afford to be.  I'll investigate how to make a site-local robots.txt (or bug bryan to do so).,1418608223,PHID-USER-22bsa5u75jz3ci3wnplu,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors","Looks like we're getting crawled.
+
+208.80.154.18 - - [15/Dec/2014:01:40:57 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=ids&titles=Hiera:Video HTTP/1.1"" 200 5064 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+208.80.154.18 - - [15/Dec/2014:01:40:57 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=content&titles=Hiera:Video HTTP/1.1"" 200 666 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+208.80.154.18 - - [15/Dec/2014:01:41:00 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=ids&titles=Hiera:Oxygenguide HTTP/1.1"" 200 5064 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+208.80.154.18 - - [15/Dec/2014:01:41:00 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=content&titles=Hiera:Oxygenguide HTTP/1.1"" 200 666 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+68.180.228.125 - - [15/Dec/2014:01:41:01 +0000] ""GET /wiki/Special:PrefixIndex/User:OccultZone/ HTTP/1.1"" 500 5485 ""-"" ""Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)""
+208.80.154.14 - - [15/Dec/2014:01:41:10 +0000] ""GET / HTTP/1.1"" 302 457 ""-"" ""check_http/v1.4.15 (nagios-plugins 1.4.15)""
+208.80.154.18 - - [15/Dec/2014:01:41:10 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=ids&titles=Hiera:Visualeditor HTTP/1.1"" 200 5064 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+2",1418607697,PHID-USER-22bsa5u75jz3ci3wnplu,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Turns out Flow is a great tool for newbies compared to free-form wikitext. Well, at least until the point where they need to create a link or they want to add some basic formatting. Especially if the newbies are defaulting to VisualEditor, they might have difficulties posting anything other than plaintext and full URLs.
+
+{F21334 size=full}
+
+Trimming the selection was discussed, and discovered to be both subjectively-desirable and technically-complicated. Newcomers will eventually have an alternative VE interface, to satisfy the requests for a less complicated set of buttons. So, please implement the full/default WikiEditor toolbar.
+
+Further notes at {T90052}
+
+See also: {T93243}",1418336289,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-monj46bisauzpolgauzi,task_description,resolved
+Wikitext editing toolbar for Flow,"Solved by {T155861}. 
+Concerning advanced toolbar, that's now covered by {T93243} while both editors are based on the same toolbar.",1523032235,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,,1505324640,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,,1505305235,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I'm retitling this task, due to the recent work on the VE toolbar in {T93243}",1464882800,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,Some thoughts raised during Collaboration team's offsite concerning VE toolbar for Flow have been added to {T93243}.,1464134744,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,[[https://fr.wikipedia.org/wiki/Sujet:T32v2yjule0ssfq7 | New feedback concerning the lack of toolbars]]. I hope we will be able to address that problem soon.,1462181068,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1747890, @Pginer-WMF wrote:
+>> Create a minima a way to personalize VE and wikitext toolbars with a gadget would be a good idea.
+> 
+> Adding media is a reasonable usecase for conversations. We consider providing support for it from the beginning but the decision was postponed until VE would be able to support an uploading process (and not just reusing existing images from commons).
+
+That will be done very soon, next week iirc. ({T40030})
+ 
+> As the image upload workflow gets supported inside VE,  Flow would adopt those powers too (at least for the rich text view where VE is used). If I recall correctly, exposing the ""insert media"" icon is just a simple configuration change.
+
+There is two different requests from communities : 
+- add images on a conversation
+- add smileys/kittens/whatever on a conversation ([[https://www.mediawiki.org/w/index.php?title=Topic:Smsn1ofyp04kqxle&topic_showPostId=snovfwyo3tasvyou#flow-post-snovfwyo3tasvyou | usual tools  ]] on a chat)
+
+And there is still the following needs:
+- add a toolbar to wikitext
+- personalize the toolbars (I would love to have my personal pre-written messages when I answer on the fr help desk)",1462180984,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1747890, @Pginer-WMF wrote:
+>> Create a minima a way to personalize VE and wikitext toolbars with a gadget would be a good idea.
+> 
+> Adding media is a reasonable usecase for conversations. We consider providing support for it from the beginning but the decision was postponed until VE would be able to support an uploading process (and not just reusing existing images from commons).
+
+That will be done very soon, next week iirc. ({T40030})
+ 
+> As the image upload workflow gets supported inside VE,  Flow would adopt those powers too (at least for the rich text view where VE is used). If I recall correctly, exposing the ""insert media"" icon is just a simple configuration change.
+
+There is two different requests from communities : 
+- add images on a conversation
+- add smileys/kittens/whatever on a conversation ([[ https://www.mediawiki.org/w/index.php?title=Topic:Smsn1ofyp04kqxle&topic_showPostId=snovfwyo3tasvyou#flow-post-snovfwyo3tasvyou | usual tools  ]]on a chat)
+
+And there is still the following needs:
+- add a toolbar to wikitext
+- personalize the toolbars (I would love to have my personal pre-written messages when I answer on the fr help desk)",1445606259,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"> Create a minima a way to personalize VE and wikitext toolbars with a gadget would be a good idea.
+
+Adding media is a reasonable usecase for conversations. We consider providing support for it from the beginning but the decision was postponed until VE would be able to support an uploading process (and not just reusing existing images from commons).
+
+As the image upload workflow gets supported inside VE,  Flow would adopt those powers too (at least for the rich text view where VE is used). If I recall correctly, exposing the ""insert media"" icon is just a simple configuration change.
+",1445605062,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"A user [[ https://fr.wikipedia.org/w/index.php?title=Sujet:Sqsccaf41ercbdaq&topic_showPostId=sqtsyrdrdzk309os#flow-post-sqtsyrdrdzk309os | complains ]] about she can't post pictures of kittens on a conversation. We definitely need to do something. For kittens.
+
+Create //a minima// a way to personalize VE and wikitext toolbars with a gadget would be a good idea. I know, there is always risks of abuses (thousand of buttons) but this did not happen with wikitext editing toolbar afak.",1445604231,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"On [[ https://fr.wikipedia.org/w/index.php?title=Sujet:Sox3xbkro37l4fta&topic_showPostId=sox3xblgm25yjf9q#flow-post-sox3xblgm25yjf9q | this feedback ]], a user asks to have personalized buttons on the toolbar (#3), and a way to add templates (#8).",1442303722,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,See also https://www.mediawiki.org/wiki/Topic:Smsn1ofyp04kqxle.,1440514581,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,Shouldn't this be resolved?,1440464281,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"In ru.wiki we definitely ourselves will add some buttons for wikitext. (https://ru.wikipedia.org/wiki/Википедия:Викификатор , https://ru.wikipedia.org/wiki/Википедия:Гаджеты/Упрощение_ссылок ) Something for these buttons ""it was necessary already yesterday"".",1428190160,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1115277, @DannyH wrote:
+> I added new screenshots from the prototype to T90764.
+> 
+> I have a question about the Mentions modal: If there are a lot of users who have posted on the thread, does it get a scroll bar? 
+
+Yes.  Try typing Assoc into the link inspector to get an idea.  Ours probably won't be a truncated list, though.
+
+I've created {T92588} to track this specifically.",1426206978,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I added new screenshots from the prototype to T90764.
+
+I have a question about the Mentions modal: If there are a lot of users who have posted on the thread, does it get a scroll bar? ",1426202773,PHID-USER-37czexl6ekrvcmp2tyqq,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"> - Inspector (the one you see when you click the link icon)
+We can start using this. I can create a mockup to illustrate the dialog in that format.",1426178885,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1099845, @Pginer-WMF wrote:
+> For the mention dialog (check mockups below), I would recommend the following:
+> - Show the dialog in-line with the text. When the user clicks on the mention icon, the dialog is shown where the text cursor is. This makes the user feel that she is manipulating the content directly since the information is in a single place.
+
+We decided it will use an inspector, at least initially.
+
+> - Initially, provide as the auto-suggestion values the users that participate in the current conversation or sub-conversation, or the frequently mentioned by the user (or any other criteria that can anticipate the user action and it is easy to implement).
+
+Auto-complete will use all authors in the current topic.",1426178846,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"VE basically has two types of dialogs:
+
+* Inspector (the one you see when you click the link icon)
+* Dialog (e.g. Insert->Template)
+
+For now, I think we should stick to one of these two, for both maintainability and visual consistency.  The closer one (but not that close) is inspector.",1425948264,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I also put together some of the mockups we mentioned for the first version [[ http://pauginer.github.io/prototypes/flow/editor/index.html | in this prototype ]]. Only basic transition between modes are supported, don't expect to actually turn text into bold.",1425903324,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"For the mention dialog (check mockups below), I would recommend the following:
+- Show the dialog in-line with the text. When the user clicks on the mention icon, the dialog is shown where the text cursor is. This makes the user feel that she is manipulating the content directly since the information is in a single place.
+- Initially, provide as the auto-suggestion values the users that participate in the current conversation or sub-conversation, or the frequently mentioned by the user (or any other criteria that can anticipate the user action and it is easy to implement).
+- As the user types, auto-suggestions will show users with the given username (if possible, it would be great to be flexible in the search to typos and preferred names if those are available). The first selection will be highlighted (following the standard style for list selection).
+- If the user is not found, some text will indicate so.
+- An option to close the dialog is provided.
+- The dialog can be controlled with the keyboard. The user can type @ and the dialog will open for the user to just type the user name and hit enter to insert the first selection from the list. We may want to not interfere with the use of ""@"" as a valid character. For that we may want to (a) make sure that the ""@"" happens in a valid context (after a space, text beginning, or non-word character) to avoid it appearing when users type an email for example; and (b) close the panel if the user types a space after having pressed ""@"", which would just result in adding the ""@"" character. the ""esc""key will close the dialog.
+- Most of the time the mention action will be triggered without a selected text,but if there is a text selection, we may want to use that text for the user search when the panel is opened. In this scenario, if the operation is cancelled, the user text should not be destroyed.
+
+
+
+{F65305}
+
+{F65534}
+
+{F65307}",1425901972,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Pau, I think the only mockup that we still need is the mentions modal... Am I forgetting anything?
+
+",1425603473,PHID-USER-37czexl6ekrvcmp2tyqq,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"We talked about this in the design meeting this morning, and decided on a plan for v1. 
+
+We need to get a simple v1 of the VE toolbar out soon, in order to roll out on a couple of languages that are excited about trying out Flow. 
+
+So v1 will have:
+
+* Bold/Italics (with a menu offering the two choices)
+* Link (with the same VE modal)
+* Mention (with a new modal)
+* Toggle to wikitext / VE
+
+There are several pieces that we definitely want to include, but not in the v1: Lists, something that helps with Code/Pre/Nowiki/Blockquote (tbd), and Insert media. (Insert media would be especially helpful if it includes an upload picture function, so that people could upload screenshots when they're asking for help.) ",1425603391,PHID-USER-37czexl6ekrvcmp2tyqq,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"The idea is for the different controls to behave like they do on the VE toolbar (preferably using the same components, just adjusting how prominent they are shown according to our context). For the case of the text format action, a drop-down like the one used by VE will be shown:
+
+{F53362}
+
+
+Regarding which controls to use, some thoughts:
+- Regarding the ""code"" and ""nowiki"", I wonder if we can have a unified ""quote"" action to cover most of the usecases (refer to portions of wikicode, source code, or specific parts of a comment someone previously said).
+- We may consider lists and inserting media to be under the ""more"" section. For example, in the current conversation in Phabricator they are used frequently and, although it cannot be generalised, I wonder if they may be used more in the wiki context if they were easily accessible.
+- I think it is ok to start with fewer controls and iterate on adding new ones.
+
+With the controls mentioned above, the expanded ""more"" menu can either expand in-place the advanced controls or be a regular dropdown menu (the later may be easier to support initially, but if menu items grow, or we want to better support repetitive use the former is preferred):
+
+{F53387}
+
+{F53373}",1425375273,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"if anyone is going to write 'yet another toolbar', can someone please make sure to really think stuff through ? I'm counting:
+
+1: Old toolbar (that community doesn't want to get rid off, yet we do)
+2: WikiEditor toolbar (that we prefer over old, but is also a bit over designed and old style JS)
+3: VE toolbar (OOjs UI, but not yet finished)
+4: Mobile Editing versions of VE toolbar.
+5: and now Flow
+
+Will the Math extension soon require 4 modules to provide a math insertion button to all editors types ?
+We have things like textSelection, confirmCloseWindow, live preview and stash. All that stuff comes into play, and any new wikitext editor work we do should recognize that and along the way should try to improve and consolidate.
+
+Similarly:
+```
+Enhancing WikiEditor for normal pages is completely outside the scope of this bug.
+```
+But please do account for the many ways in which it is FAILING users.",1425377996,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"if anyone is going to write 'yet another toolbar', can someone please make sure to really think stuff true ? I'm counting:
+
+1: Old toolbar (that community doesn't want to get rid off, yet we do)
+2: WikiEditor toolbar (that we prefer over old, but is also a bit over designed and old style JS)
+3: VE toolbar (OOjs UI, but not yet finished)
+4: Mobile Editing versions of VE toolbar.
+5: and now Flow
+
+Will the Math extension soon require 4 modules to provide a math insertion button to all editors types ?
+We have things like textSelection, confirmCloseWindow, live preview and stash. All that stuff comes into play, and any new wikitext editor work we do should recognize that and along the way should try to improve and consolidate.
+
+Similarly:
+```
+Enhancing WikiEditor for normal pages is completely outside the scope of this bug.
+```
+But please do account for the many ways in which it is FAILING users.",1425372893,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"+1 to the idea of starting with a subset of the current VE toolbar for articles.
+
++1 to the idea of enabling in the Flow VE buttons the same UX as the full ED version.",1425364714,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Based on these example threads, and our goal to rollout further at mediawikiwiki, and He7d3r's comment above, and my own experience, I still strongly advocate for having `<code>` and `<nowiki>` tags available and planned from the start (in a dropdown menu).
+
+* https://ca.wikipedia.org/wiki/Topic:Sbk26yv6cpcxxm87
+* https://ca.wikipedia.org/wiki/Topic:Sbi6jrldf94ea8nt
+* https://ca.wikipedia.org/wiki/Topic:Sa23rwtl0w12e4sk
+* https://ca.wikipedia.org/wiki/Topic:S8h1yv4n7yfm4fmi
+* https://ca.wikipedia.org/wiki/Topic:S8adbxrruu971vyd
+* https://fr.wikipedia.org/wiki/Sujet:Sb3nxhhm4wdodaez
+* https://fr.wikipedia.org/wiki/Sujet:Sabk082dkr6rat37
+* https://fr.wikipedia.org/wiki/Sujet:Sb3m5set5zkob0rj
+* https://fr.wikipedia.org/wiki/Sujet:Sbceer9529lnk66g
+Being able to //discuss// wikimarkup, is crucial to so many of the places we want to deploy to.",1425349109,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Link should be exactly the same as VE once you click it, both for a consistent user experience and so we don't have to implement a new link widget (with autocomplete, etc.)",1425346213,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I talked to James about toolbar use in VE -- they don't currently have tracking on which buttons get used the most. But he gave me his gut instinct on it, which I think is good enough for a first pass. 
+
+He said that for discussions, the most used tools are: Links, Mentions, and Bold/Italics. 
+
+(For article content, he'd also include Citations, Templates & Media, but these aren't as important for discussions.)
+
+I think we can go with Pau's mockups for a first version of a VE/Flow toolbar. We can even take out the ellipsis/more menu, and just have these controls:
+
+* Bold/Italics
+* Link
+* Mention
+* switch to wikitext
+
+This will be better than not having one, and we can find out what else people need from there. 
+
+Pau, we'll need mockups that show what happens when you click on those buttons. I'm assuming Bold/Italics has a dropdown menu. Would Link and Mention have little modal boxes? 
+
+{F34174}
+{F34176}
+{F52902}",1425343610,PHID-USER-37czexl6ekrvcmp2tyqq,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1061982, @Pginer-WMF wrote:
+> 
+> @GOIII, so for the specific case of discussions in Wikisource, is there any specific kind of content that would be useful to get help from a rich text editor to deal with in converstions?
+> 
+> I tried to look for some complex scenarios based on current use but [[ https://en.wikisource.org/wiki/Talk:The_Metamorphosis | in the example I found ]] formatting needs seemed basic (user mentions, lists, and links). Do you know of some examples of current (or potential) uses of more advanced formatting?
+
+@Pginer-WMF - Boy, finding something in NS-1 (the talkspace for the main namespace) that would benefit from //Flow// is not likely to exist. Again, Wikisource's mainspace output follows the premise of ''reproducing an original publication as faithfully as possible"" so there is little left to question where long or ongoing talk page discussions are likely needed to take place.
+
+Still, we do have continuous ""action"" in the Village Pump equivalent, [[https://en.wikisource.org/wiki/Wikisource:Scriptorium| Scriptorium]], that might benefit from using //Flow//. Debate traffic also exists for certain Help: and Template: namespace pages every so often, but nowhere near approaching the typical Wikipedia article's talkpage traffic or timeframe.
+
+I'll keep looking for other possible examples in mind but I wouldn't bet on anything more substantial coming to light beyond those already mentioned.",1425073820,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"> Flow is pretty and (I guess) helpful for ongoing or complex discussions; we just don't have as many instances of this as Wikipedia seems to have. Sure, making it standard provides easier maintenance across all wikis but it won't add much ""value"" to our project if any at all.
+
+ @GOIII, so for the specific case of discussions in Wikisource, is there any specific kind of content that would be useful to get help from a rich text editor to deal with in converstions?
+
+I tried to look for some complex scenarios based on current use but [[ https://en.wikisource.org/wiki/Talk:The_Metamorphosis | in the example I found ]] formatting needs seemed basic (user mentions, lists, and links). Do you know of some examples of current (or potential) uses of more advanced formatting?",1424776115,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1060761, @Quiddity wrote:
+>>>! In T78346#1038829, @GOIII wrote:
+>> So until we either actively poll for as much or implement & advertise those ""enhancements"" to accurately gauge User: preference, etc., we're just making decisions based in conjecture & assumptions more so than in reality and facts.
+> 
+> The Design Research team did some investigation into editing tools. I believe they're still compiling the results, but here are the links for watchlisting: https://www.mediawiki.org/wiki/Design/Research#Editing
+
+My point exactly - ""they"" limited their concerns, polling and decision to a single project (Wikipedia) -- which has a certain scope and a specific mission -- both of which translate to almost the complete opposites as far as Wikisource is concerned (a //different// project with a //different// scope and a //different// mission). 
+
+Wikipedia is an ongoing collaborative endeavor that expects both mainspace presentations and non-mainspace discussions to always be in a state of perpetual flux to some degree thanks to it's inherent nature where new developments = addition of new sources to support new content = new points of contentions to work through.
+
+Wikisource, on the other hand, shares little with Wikipedia beyond also being an ongoing collaborative endeavor. Our mainspace end products are suppose to be static by design and as a result our non-mainspace discussions are mostly style guide/formatting/bug/enhancement related in nature.
+
+What does this mean? In a nutshell (a few examples-wise), this means...
+# Nobody here gives a crap about citation tools et. al anywhere near the degree to which Wikipedians do - we primarily deal with static footnotes found in the original fixed content of a specific edition of a copyright free publication. So -- while the two //feel// similar at first glance -- they are not in practice nor purpose.
+# Thanks to the nature of the works being reproduced and hosted on WS, our needs for image manipulation and presentation make things like Media Viewer completely useless.
+# Flow is pretty and (I guess) helpful for ongoing or complex discussions; we just don't have as many instances of this as Wikipedia seems to have. Sure, making it standard provides easier maintenance across all wikis but it won't add much ""value"" to our project if any at all.
+# We don't attract the temp newbie contributor types in any comparable numbers nor are they likely to need toolbar dialog crutches to facilitate contributions. What prevents folks by us to break out of their specific favorites into ""new"" works is an easier way to customize tools to specific works & not so much the repetitive WP-like tasks. 
+# ... and I could go on ad nausea
+
+The point -- as it relates to the issue of editing/toolbars in general and development overall -- is ""we"" basically continue to have no say in these matters; if an editing feature or a contribution aspect is not Wikipedia- or Commons- centric, the editing needs of other projects will, at best, be an add-in, a work around or some other afterthought -- //if ""we"" are lucky, that is//. The [[https://www.mediawiki.org/wiki/Editing_Tasks_Survey|Editing Tasks Survey]] mentioned is but another example of this....
+
+> ... Based on the above criterion, we queried our internal data-bases for **English Wikipedia users** and found 9316 users to contact.
+
+Doesn't seem like anything ""good-for-Wikisource"" can from decision making based on polling like that does it?
+",1424735529,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1060761, @Quiddity wrote:
+>>>! In T78346#1038829, @GOIII wrote:
+>> So until we either actively poll for as much or implement & advertise those ""enhancements"" to accurately gauge User: preference, etc., we're just making decisions based in conjecture & assumptions more so than in reality and facts.
+> 
+> The Design Research team did some investigation into editing tools. I believe they're still compiling the results, but here are the links for watchlisting: https://www.mediawiki.org/wiki/Design/Research#Editing
+
+My point exactly - ""they"" limited their concerns, polling and decision to a single project (Wikipedia) -- which has a certain scope and a specific mission -- both of which translate to almost the complete opposites as far as Wikisource is concerned (a //different// project with a //different// scope and a //different// mission). 
+
+Wikipedia is an ongoing collaborative endeavor that expects both mainspace presentations and non-mainspace discussions to always be in a state of perpetual flux to some degree thanks to it's inherent nature where new developments = addition of new sources to support new content = new points of contentions to work through.
+
+Wikisource, on the other hand, shares little with Wikipedia beyond also being an ongoing collaborative endeavor. Our mainspace end products are suppose to be static by design and as a result our non-mainspace discussions are mostly style guide/formatting/bug/enhancement related in nature.
+
+What does this mean? In a nutshell (a few examples-wise), this means...
+# Nobody here gives a crap about citation tools et. al anywhere near the degree to which Wikipedians do - we primarily deal with static footnotes found in the original fixed content of a specific edition of a copyright free publication. So -- while the two //feel// similar at first glance -- they are not in practice nor purpose.
+# Thanks to the nature of the works being reproduced and hosted on WS, our needs for image manipulation and presentation make things like Media Viewer completely useless.
+# Flow is pretty and (I guess) helpful for ongoing or complex discussions; we just don't have as many instances of this as Wikipedia seems to have. Sure, making it standard provides easier maintenance across all wikis but it won't add much ""value"" to our project if any at all.
+# We don't attract the temp newbie contributor types in any comparable numbers nor are they likely to need toolbar dialog crutches to facilitate contributions. What prevents folks by us to break out of their specific favorites into ""new"" works is an easier way to customize tools to specific works & not so much the repetitive WP-like tasks. 
+# ... and I could go on ad nausea
+
+The point -- as it relates to the issue of editing/toolbars in general and development overall -- is ""we"" basically continue to have no say in these matters; if an feature aspect is not Wikipedia- or Commons- centric, it will at best be an add-in, a work around or some other afterthought if ""we"" are lucky. The [[https://www.mediawiki.org/wiki/Editing_Tasks_Survey|Editing Tasks Survey]] mentioned is but another example of this....
+
+> ... Based on the above criterion, we queried our internal data-bases for **English Wikipedia users** and found 9316 users to contact.
+
+Doesn't seem like anything ""good-for-Wikisource"" can from decision making based on polling like that does it?
+",1424735342,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1038829, @GOIII wrote:
+> So until we either actively poll for as much or implement & advertise those ""enhancements"" to accurately gauge User: preference, etc., we're just making decisions based in conjecture & assumptions more so than in reality and facts.
+
+The Design Research team did some investigation into editing tools. I believe they're still compiling the results, but here are the links for watchlisting: https://www.mediawiki.org/wiki/Design/Research#Editing",1424731958,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1038747, @Mattflaschen wrote:
+> Note: Enhancing WikiEditor for normal pages is completely outside the scope of this bug.
+
+Then don't select the next course of action based solely on that mwgrep's results.
+
+Folks aren't using WikiEditor in some meaningful number just because of the lack in the ease of customization compared to the //Classic// toolbar followed by some other meaningful number for the inability to prevent the generation of WikiEditor's current defaults.
+
+So until we either actively poll for as much or implement & advertise those ""enhancements"" to accurately gauge User: preference, etc., we're just making decisions based in conjecture & assumptions more so than in reality and facts.",1423892360,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1026966, @Quiddity wrote:
+> Separately, I know there is some amount of local customization of the WikiEditor Toolbar buttons (both individually, and at the wiki-level), but I'm not sure how widespread the individual customizations are, nor how to find out, beyond searching for ""addToToolbar"" at each wiki in user-space and mediawiki-space. Any suggestions?
+
+mwgrep can answer this question for WMF production.  It allows searching for CSS and JS in the User, MediaWiki, or Module namespaces (one at a time).
+
+>>! In T78346#1033515, @GOIII wrote:
+> Make the current //WikiEditor// defaults an option or User pref with a far more simply way to customize it for individuals and I guarantee you the ""opting-in"" of the //Classic// toolbar would drop off drastically.
+
+Note: Enhancing WikiEditor for normal pages is completely outside the scope of this bug.",1423886182,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1026966, @Quiddity wrote:
+> ...
+> Separately, I know there is some amount of local customization of the WikiEditor Toolbar buttons (both individually, and at the wiki-level), but I'm not sure how widespread the individual customizations are, nor how to find out, beyond searching for ""addToToolbar"" at each wiki in user-space and mediawiki-space. Any suggestions?
+
+IMHO, you'd be doing yourself an injustice if you try to make decisions or draw up plans based on a tally of the ""current"" numbers or try to apply a ""strict"" accounting rationale in order to reliably ascertain something like that.
+
+Speaking entirely from the perspective of an Admin primarily focused on the needs and wants of en.wikisource contributors, a vast majority were not entirely thrilled with the //Classic// toolbar to begin with.... but the ease of customizing it to specific needs still makes it near & dear to just about anyone with any decent amount contributing time under their belts even today. And its not entirely true when folks were never ""sold"" on what the //WikiEditor// initiative(s) promised either.
+
+Most folks by me tried //WikiEditor// when it came off the beta status and immediately hated what they a.) were being forced to load as the ""defaults"" closely followed by b.) the convoluted process needed just to add customizations to make a.) somewhat bearable. Take those two points and add-in the fact the ProofreadPage extension made life with //WikiEditor// more problematic as time went by and the exodus back to using the //Classic// toolbar is not hard to understand.
+
+So its not that [my] people //won't// or //don't// utilize //WikiEditor// because it ""sucks"" or something but because -- at its core -- its specifically designed for the never-to-appear-again-in-the-numbers-they-once-did newbie or occasional Wikipedia-geared contributor with Wikipedia-like needs (not the deal-breaker however). What everybody agrees on as the major roadblock is the forcing of 'crap' as defaults nobody will ever use in addition to the inability to remove said defaults nor the customization of buttons & such without jumping through a billion hoops most non-techie types just won't deal with.
+
+Make the current //WikiEditor// defaults an option or User pref with a far more simply way to customize it for individuals and I guarantee you the ""opting-in"" of the //Classic// toolbar would drop off drastically.
+",1423713968,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"On talk pages, I believe these are the custom buttons I use the most:
+> <code>test</code>
+> <nowiki>test</nowiki>
+> <syntaxhighlight lang=""javascript"" enclose=""none"">test</syntaxhighlight>
+> <span style=""color: #000; background: #E99;""></span>
+> <pre>test</pre>
+(mainly because I usually help with technical problems in the wikis I use) and for content pages,
+> <math>test</math>
+which was removed in 2009 by the usability initiative
+https://usability.wikimedia.org/wiki/Talk:Releases/Acai#Math",1423566520,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1017880, @He7d3r wrote:
+> I miss my custom buttons in the edit toolbar.
+> See also:
+> * {T23692}
+
+I installed 3 of your scripts to test: https://meta.wikimedia.org/w/index.php?title=User:Quiddity_%28WMF%29/global.js&diff=11213986&oldid=10917385
+And took these screenshots: http://imgur.com/a/na16D#0
+
+Are there any use-cases here that might be widely applicable to an entire wiki, or even to all wikis as a default Flow feature? Or perhaps a global-template (if/when those arrive) ?
+
+Separately, I know there is some amount of local customization of the WikiEditor Toolbar buttons (both individually, and at the wiki-level), but I'm not sure how widespread the individual customizations are, nor how to find out, beyond searching for ""addToToolbar"" at each wiki in user-space and mediawiki-space. Any suggestions?",1423536220,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I miss my custom buttons in the edit toolbar.
+See also:
+* {T23692}",1423143413,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"We're going to work on this as part of turning on VE for Flow. 
+
+The current spike card is T88182 : Define and estimate work for Minimum Viable Product of VisualEditor in Flow (spike)",1423090263,PHID-USER-37czexl6ekrvcmp2tyqq,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"We're going to work on this as part of turning on VE for Flow. 
+
+The current spike card is T88182",1423090207,PHID-USER-37czexl6ekrvcmp2tyqq,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Since people are already talking about VE, I expanded the scope of the task somewhat (""WikiEditor"" is the wikitext toolbar shown in production).  This is in the idea/design stage, so it's okay to cover both technologies in the same task for now.",1422944651,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Since people are already talking about VE, I expanded the scope of the task somewhat (""WikiEditor"" is the wikitext toolbar shown in production).  This is in the idea/design stage, so it's okay to cover both technologies in the same card for now.",1422944638,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1010433, @Pginer-WMF wrote:
+> Regarding the second comment, I think you are right and we could avoid the whole mode switching if VE supported wikitext input.
+
+Currently, VE mostly just warns you about this (""Wikitext markup detected"")
+
+Even if VE supported certain obvious wikitext examples (actually, it does for certain very limited cases like the * list keyboard shortcut), it's never going to support the full power of wikitext.  That would require a *third* full-featured wikitext parser, in addition to the PHP MW parser and Parsoid, with the added complication that the source text is part rich text, part wikitext.
+
+I think mode switching is a better choice.  We can make the mode switch control normally subtle, then become obvious if you start typing wikitext (VE already has logic to detect this, as noted above).",1422942621,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"@Jaredzimmerman-WMF regarding the first comment, I think we need a general framework to deal with actions attached to input fields. I was thinking on distributing actions on the left and configuration on the right where the input method menu could fit.
+
+Regarding the second comment, I think you are right and we could avoid the whole mode switching if VE supported wikitext input.",1422929636,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Two things…
+
+I think its smart to have WYSIWYG as the default, but we'd talked in the past about having the bottom right corner reserved for IME tools, we should decide on the merit of having that be the WTE/VE switch vs access to IME, especially if we want IME to be a standard component on input fields. 
+
+One thing that I've been asking for forever was the ability for VE to detect wikitext input and parse it on the fly to convert to rich text, not to increase scope but this might be an ideal use case for this, rather than manually switching between modes. ",1422908982,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Discussing this with Pau -- we'll have to define the set of controls that we'll expose. We'll look at current use on talk pages, and also talk with some of the people who are currently using Flow (or will be using it soon). 
+
+Today's hypothesis for what we think are important:
+* Links 
+* Mentions
+* Lists?
+* Add image?
+
+Not sure about Bold/Italics/Underline. 
+
+Whatever we decide on, we'll have to use event logging to see if people are using the ""More"" section to access other controls. 
+
+All of this WIP.",1422907976,PHID-USER-37czexl6ekrvcmp2tyqq,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"For the contest of Flow, I think styling controls should be less prominent than the user message, and consider the specific needs in the context of Flow. That may imply to hide some controls and show new ones (e.g., user mentioning).
+
+I created a mockup showing these ideas, but more research is needed to determine the specific actions to show:
+{F34174}
+
+The above was done assuming rich text editing as the default mode and making it possible to switch to wikitext for advanced users. I didn't include a specific toolbar for wikitext in the mockups but it would be possible to keep the same tools if we really think that they are needed in that mode. This is illustrated below:
+{F34176}",1422903281,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#844010, @Qgil wrote:
+> But, but, but... 
+
+On a second thought, I'm happy with the solution that can land faster. At the end, this is an interim situation while VisualEditor integration in Flow comes. On that day, we will have most likely two main types of Flow users: those defaulting consistently to VE and those defaulting consistently to wikitext. If both have the tools they want, both will be happy.",1418466425,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843120, @Quiddity wrote:
+> Personally, I'd like to have the entire existing WikiEditor toolbar in Flow, with 1 exception.[1]
+> I often need special characters, or `<nowiki>` tags, or to insert an image, or create a table, or add a citation for discussion.{F20913}
+> 
+> [1] The //only// element I think we'd want to remove, is the signature button. And that should be removed when the toolbar is shown on articles anyway, so double benefit if we solve it!
+> 
+> Can we add that to WikiEditor, somehow?
+
+//My repeated solution -->// ... all we need to do is add...
+
+		'filters': [ 'body.ns-talk' ],
+
+... to the 'signature' button's entry in...
+
+		jquery.wikiEditor.toolbar.config.js
+
+... and you're done. The same approach is used for the 'reference' button btw (see [[https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FWikiEditor/HEAD/modules%2Fjquery.wikiEditor.toolbar.config.js#L170 | that same .js file]] if you don't believe me).
+
+This way, all talk pages will automatically generate the 'signature' button while solving the immediate issue of how to stop its generation in the ns-0 and other Subject-space namespaces.
+If it was up to me, I'd at least thrown in the Project: namespace (like for Village Pump) along with all the talkspaces...
+
+		'filters': [ 'body.ns-talk, body.ns-4' ],
+
+... The above should be the common sense ""default"" setting. And I suspect all the  other ""hide WikiEditor type of fixes"" floating about would not be affected no matter what this 'filters' setting might be set to - no?",1418432048,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843064, @Mattflaschen wrote:
+> If OOJS-UI (the UI library used by VE) rolled out everywhere (to e.g. WikiEditor) this consideration would no longer apply
+
+We're on it. Not in the next few weeks, though.",1418423358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"But, but, but... Flow is about simplicity for everybody, and for increasing the participation of newcomers in discussions. <ref> in comments? Tables? Really? I'd rather bet on a very simple setup that solves 90% of the formatting used 90% of the times by 90% of the users. Then the ""Help"" link explains how to type all the rest. ",1418380297,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843120, @Quiddity wrote:
+> [1] The //only// element I think we'd want to remove, is the signature button. And that should be removed when the toolbar is shown on articles anyway, so double benefit if we solve it!
+
+See T42972. Seems like it ought an easy bug to resolve, but not so.",1418360651,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Personally, I'd like to have the entire existing WikiEditor toolbar in Flow, with 1 exception.[1]
+I often need special characters, or `<nowiki>` tags, or to insert an image, or create a table, or add a citation for discussion.{F20913}
+
+[1] The //only// element I think we'd want to remove, is the signature button. And that should be removed when the toolbar is shown on articles anyway, so double benefit if we solve it!
+
+(Note, the CharInsert (special character section //under// the editing window) uses this code, to remove the signature button, when we're editing mainspace. 
+`{{#ifeq:{{NAMESPACE}}|{{ns:0}}||'''Sign your posts on talk pages:''' <nowiki>~~~~</nowiki> &nbsp;}}` at https://en.wikipedia.org/w/index.php?title=MediaWiki:Edittools&diff=559635127&oldid=558019716
+Can we add that to WikiEditor, somehow?",1418342597,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843064, @Mattflaschen wrote:
+> It would make more sense to use the WikiEditor icons.
+
+I disagree, because Flow design and VE design fit, while the old toolbar icons will look really old there, and what matters is the impression we cause to new users, but.... this is not a battle I will pick.  :)
+
+In any case the icons are available. It is a matter of deciding which options would survive the pruning (I just added a proposal to the description) and reuse them. There is basically no need for asset creation.",1418340570,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843053, @Qgil wrote:
+> There is no lack of existing design assets. Why not just removing the VE toolbar icons that are superfluous in the context of discussions? See M26
+
+As of now, using the VE toolbar (or a subset of it) for wikitext would be very confusing.  Looking at your mockup, it strongly makes me think I'm using VisualEditor (the only odd man out is the Preview button).
+
+It would make more sense to use the WikiEditor icons.  If OOJS-UI (the UI library used by VE) rolled out everywhere (to e.g. WikiEditor) this consideration would no longer apply (but at that point we'd want another way to visually hint to people whether they're using wikitext or VE).",1418339741,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,There is no lack of existing design assets. Why not just removing the VE toolbar icons that are superfluous in the context of discussions? See M26,1418339394,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,There is no lack of existing design assets. Why not just removing the VE options that are superfluous in the context of discussions? See M26,1418339336,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"adding design, as we had previously talked about adding the default toolbar and it was considered too cluttered and confusing.  Something less confusing would need to be designed.",1418336842,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"Steps to reproduce:
+
+1.Open a page with VE
+2.Place a cursor after a text like ""sub-heading 1""
+3.Open the link inspector
+
+Observe that the character 1 is not getting selected and the link inspector is opening at the end of the line
+
+{F20734}
+",1418251189,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_description,resolved
+Wordbreak detection is faulty for selection starting just down-page of a single character,Verified the fix in Betalabs and test2,1427330396,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"Change 197661 merged by jenkins-bot:
+[BREAKING CHANGE] Use Unicode character class to calculate word expansions
+
+[[https://gerrit.wikimedia.org/r/197661]]",1426727791,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"Change 197661 had a related patch set uploaded (by Divec):
+WIP: BREAKING CHANGE: Use unicode character class to calculate word expansions
+
+[[https://gerrit.wikimedia.org/r/197661]]
+",1426698338,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"UnicodeJS change was released in v0.1.3, which is now in VisualEditor core master following https://gerrit.wikimedia.org/r/188729 – what's next?",1423103268,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"The word break calculation is correct:
+
+|Sub| |heading| |1|
+
+But our word expansion logic avoids wrapping single length ranges due to the following cases:
+
+|Double| | |Space|
+
+|中|國|人|",1421340158,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"I spoke to David about this issue, there is definitely something off about how we account for word boundary and wordbreaks.",1420845176,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,Message 'visualeditor-find-and-replace-regular-expression' missing.,1418237110,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-baxx2wdr226fyxswg265,task_description,resolved
+Message 'visualeditor-find-and-replace-regular-expression' missing,We should really be consuming modules.json from core to avoid problems like this,1422061033,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Change 178883 merged by jenkins-bot:
+Follow-up I4e38607d8: Register <visualeditor-find-and-replace-regular-expression>
+
+[[https://gerrit.wikimedia.org/r/178883]]",1418238206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Change 178881 merged by jenkins-bot:
+Follow-up I4e38607d8: Register <visualeditor-find-and-replace-regular-expression>
+
+[[https://gerrit.wikimedia.org/r/178881]]",1418238111,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Change 178883 had a related patch set uploaded (by Jforrester):
+Follow-up I4e38607d8: Register <visualeditor-find-and-replace-regular-expression>
+
+[[https://gerrit.wikimedia.org/r/178883]]
+
+#patch-for-review",1418238017,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Change 178881 had a related patch set uploaded (by Jforrester):
+Follow-up I4e38607d8: Register <visualeditor-find-and-replace-regular-expression>
+
+[[https://gerrit.wikimedia.org/r/178881]]
+
+#patch-for-review",1418237509,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Bah, probably my screw-up.",1418237371,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+"Chinese table contents are lost when saving in VisualEditor, unless the first letter is in the Latin alphabet","[[ https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&offset=20141127161632#Input_Chinese_to_table_will_disappear_when_saving_unless_start_with_an_English_alphabet.__51109 | Original report ]] by Cwlin0416 on 27 November 2014:
+
+Input Chinese to table will disappear when saving unless start with an English alphabet.
+
+If i just type Chinese into table, it can't be saved, if i start with an English alphabet, the problem is solved.
+
+",1418190225,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ktvckajg62tqaio3n4gv,task_description,resolved
+"Chinese table contents are lost when saving in VisualEditor, unless the first letter is in the Latin alphabet","The problem was originally spotted in Google Chrome while using Traditional Chinese.
+
+The user says (at 16:48 UTC on 11 December) that it was fixed with the recent update.  From Elena's testing, it sounds like we should re-confirm this.",1418412422,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ktvckajg62tqaio3n4gv,task_subcomment,NA
+"Chinese table contents are lost when saving in VisualEditor, unless the first letter is in the Latin alphabet","Confirmed on https://zh.wikipedia.org/ - typed Cangjie(on Mac) in tables is not saved.
+
+Tried  in betalabs and test2(wmf12)  the typed text in tables is saved as well as  everywhere else.",1418252142,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ktvckajg62tqaio3n4gv,task_subcomment,NA
+"Vertical alignment of the ""add template"" button and the search box is incorrect in template dialog in VisualEditor when using the OOjs UI MediaWiki theme","See screenshot:
+
+{F20272}",1418156342,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-675e74bf6yv4vzpihvax,task_description,resolved
+"Vertical alignment of the ""add template"" button and the search box is incorrect in template dialog in VisualEditor when using the OOjs UI MediaWiki theme","Change 179339 merged by jenkins-bot:
+TextInputWidget: Set vertical-align: middle, like buttons
+
+[[https://gerrit.wikimedia.org/r/179339]]",1418413007,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-675e74bf6yv4vzpihvax,task_subcomment,NA
+"Vertical alignment of the ""add template"" button and the search box is incorrect in template dialog in VisualEditor when using the OOjs UI MediaWiki theme","Above patch fixes this:
+
+{F20933}",1418347242,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-675e74bf6yv4vzpihvax,task_subcomment,NA
+"Vertical alignment of the ""add template"" button and the search box is incorrect in template dialog in VisualEditor when using the OOjs UI MediaWiki theme","Change 179339 had a related patch set uploaded (by Bartosz Dziewoński):
+TextInputWidget: Set vertical-align: middle, like buttons
+
+[[https://gerrit.wikimedia.org/r/179339]]
+
+#patch-for-review",1418339505,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-675e74bf6yv4vzpihvax,task_subcomment,NA
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,"See screenshot:
+
+{F20262}",1418156052,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cm26etfhdyviprbpebfm,task_description,resolved
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,"Change 179193 merged by jenkins-bot:
+MediaWiki theme: Use gray instead of blue for select and highlight
+
+[[https://gerrit.wikimedia.org/r/179193]]",1418332756,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cm26etfhdyviprbpebfm,task_subcomment,NA
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,"Change 179193 had a related patch set uploaded (by Trevor Parscal):
+Use gray instead of blue for select and highlight
+
+[[https://gerrit.wikimedia.org/r/179193]]
+
+#patch-for-review",1418331144,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cm26etfhdyviprbpebfm,task_subcomment,NA
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,Eww. Oh well.,1418254890,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cm26etfhdyviprbpebfm,task_subcomment,NA
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,"See T78032, I think the MediaWiki theme calls for light gray for highlighted and a medium gray for selected.",1418166945,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-cm26etfhdyviprbpebfm,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"See screenshot:
+
+{F20257}",1418155912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ywadwhslnfchsbahscag,task_description,resolved
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"Change 179518 merged by jenkins-bot:
+MediaWiki theme: Make button sizes match Apex
+
+[[https://gerrit.wikimedia.org/r/179518]]",1418411301,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"Change 179518 had a related patch set uploaded (by Jforrester):
+MediaWiki theme: Make button sizes match Apex
+
+[[https://gerrit.wikimedia.org/r/179518]]
+
+#patch-for-review",1418411091,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"The clipping depends on zoom level, so probably Chromium rendering bug.",1418405798,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,I'm pretty sure that's by design. The task for figuring out what to do with the massive buttons is T78169.,1418251037,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"No clipping for me in Chrome of FF, but the thing that really stands out is the massive difference in height between buttons and textboxes. That needs to get fixed.",1418236631,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"See screenshot:
+
+{F20257}",1418155886,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63zjaemkihhdn67rqs2l,task_description,resolved
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"Change 179545 merged by jenkins-bot:
+ButtonGroupWidget: Remove weird margin-bottom: -1px; from theme styles
+
+[[https://gerrit.wikimedia.org/r/179545]]",1418762865,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,https://gerrit.wikimedia.org/r/#/c/179545/,1418416810,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,This also affects the Apex theme.,1418416546,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"Change 179339 merged by jenkins-bot:
+TextInputWidget: Set vertical-align: middle, like buttons
+
+[[https://gerrit.wikimedia.org/r/179339]]",1418413007,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,Not fixed. I'm going to declare this not a blocker to switching.,1418412612,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"Above patch doesn't seem to fix the issue at hand:
+
+{F20931}",1418347245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"I am not sure if the patch fixes the issue here, because I've somehow broken all the styles for the search-and-replace ""pulldown"" locally. Let's retest this after pulling all recent fixes through.",1418339584,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"Change 179339 had a related patch set uploaded (by Bartosz Dziewoński):
+TextInputWidget: Set vertical-align: middle, like buttons
+
+[[https://gerrit.wikimedia.org/r/179339]]
+
+#patch-for-review",1418339506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"We'd need to upstream this functionality into OOUI, as the input widget padding varies from skin to skin.",1418236814,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","See screenshot:
+
+{F20244}",1418155549,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-426ekcmockyid64cqfva,task_description,resolved
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179343 abandoned by Trevor Parscal:
+[WIP] Apex theme: Fix box-sizing for inputs
+
+Reason:
+Didn't live up to my expectations. In that... It didn't work at all.
+
+[[https://gerrit.wikimedia.org/r/179343]]",1418412481,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-426ekcmockyid64cqfva,task_subcomment,NA
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179355 merged by jenkins-bot:
+MediaWiki theme: Improve search widget styling
+
+[[https://gerrit.wikimedia.org/r/179355]]",1418411795,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-426ekcmockyid64cqfva,task_subcomment,NA
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179355 had a related patch set uploaded (by Jforrester):
+Improve search widget styling in MediaWiki theme
+
+[[https://gerrit.wikimedia.org/r/179355]]
+
+#patch-for-review",1418345062,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-426ekcmockyid64cqfva,task_subcomment,NA
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179343 had a related patch set uploaded (by Trevor Parscal):
+[WIP] Fix box-sizing for inputs
+
+[[https://gerrit.wikimedia.org/r/179343]]
+
+#patch-for-review",1418341325,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-426ekcmockyid64cqfva,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","See screenshot:
+
+{F20244}",1418155514,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_description,resolved
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179343 abandoned by Trevor Parscal:
+[WIP] Apex theme: Fix box-sizing for inputs
+
+Reason:
+Didn't live up to my expectations. In that... It didn't work at all.
+
+[[https://gerrit.wikimedia.org/r/179343]]",1418412482,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179355 merged by jenkins-bot:
+MediaWiki theme: Improve search widget styling
+
+[[https://gerrit.wikimedia.org/r/179355]]",1418411796,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","With the ""Improve search widget styling"" patch, this looks better but not ideal: {F20921}
+
+Adding the ""Fix box-sizing for inputs"" patch doesn't change the display: {F20923}
+
+For context, the current Apex display in master/OOUI 0.4.0: {F20925}",1418346030,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179355 had a related patch set uploaded (by Jforrester):
+Improve search widget styling in MediaWiki theme
+
+[[https://gerrit.wikimedia.org/r/179355]]
+
+#patch-for-review",1418345063,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179343 had a related patch set uploaded (by Trevor Parscal):
+[WIP] Fix box-sizing for inputs
+
+[[https://gerrit.wikimedia.org/r/179343]]
+
+#patch-for-review",1418341324,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","See screenshot:
+
+{F20244}",1418155481,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cidep33c4c5o3tej2ipd,task_description,resolved
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 178717 merged by jenkins-bot:
+ve.ui.MWParameter*: Use the destructive flag for all four remove buttons
+
+[[https://gerrit.wikimedia.org/r/178717]]",1418177075,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cidep33c4c5o3tej2ipd,task_subcomment,NA
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme",">>! In T78033#835291, @TrevorParscal wrote:
+> Gosh that looks terrible. I don't know that the style guide actually demands this, because these are secondary actions and should thus be quieter.
+
+Yeah, but consistency…",1418169765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cidep33c4c5o3tej2ipd,task_subcomment,NA
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 178717 had a related patch set uploaded (by Jforrester):
+ve.ui.MWParameter*: Use the destructive flag for all four remove buttons
+
+[[https://gerrit.wikimedia.org/r/178717]]
+
+#patch-for-review",1418169760,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cidep33c4c5o3tej2ipd,task_subcomment,NA
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Gosh that looks terrible. I don't know that the style guide actually demands this, because these are secondary actions and should thus be quieter.",1418166758,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-cidep33c4c5o3tej2ipd,task_subcomment,NA
+Per-site configuration for enabling Media Viewer,"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 //
+
+== Narrative ==
+
+As a development team, we can enable Media Viewer by default on a few pilot sites, so that we can try it out in a limited release before deploying it everywhere.
+
+== Acceptance Criteria ==
+
+Add a site configuration option with which Media Viewer can be enabled for every user (including non-logged-in) on a few pilot wikis(e.g. Commons, French, Hungarian, Korean)
+ * Configure Beta Features so that when Media Viewer is enabled, it does not show up as a beta option anymore
+ * We can adapt the code used by VisualEditor for the same purpose
+ * After we've tested the feature on a few wikis, we may want to gradually increase the number of sites -- or enable it everywhere, based on community feedback.
+
+
+== Related Bugs ==
+
+== Related Stories ==
+
+== Related Changesets ==
+
+
+
+ [[https://gerrit.wikimedia.org/r/117374 | https://gerrit.wikimedia.org/r/117374]] ",1418056781,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-6hephrfe43g3sajiaspv,task_description,resolved
+Per-site configuration for enabling Media Viewer,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 | mingle]] on 2014-03-27 at 21:15:30, @Tgr wrote:
+
+https://gerrit.wikimedia.org/r/#/c/121526/",1418056789,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-6hephrfe43g3sajiaspv,task_subcomment,NA
+Per-site configuration for enabling Media Viewer,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 | mingle]] on 2014-03-07 at 02:08:31, @MarkTraceur wrote:
+
+https://gerrit.wikimedia.org/r/117374",1418056787,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-6hephrfe43g3sajiaspv,task_subcomment,NA
+Per-site configuration for enabling Media Viewer,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 | mingle]] on 2014-02-27 at 19:42:03, @Tgr wrote:
+
+I'll make this one into the server-side ticket and the other one into the client-side one.",1418056786,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-6hephrfe43g3sajiaspv,task_subcomment,NA
+Per-site configuration for enabling Media Viewer,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 | mingle]] on 2014-02-27 at 18:09:16, @MarkTraceur wrote:
+
+Should be merged with  [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/263 | #263]] ",1418056784,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-6hephrfe43g3sajiaspv,task_subcomment,NA
+VisualEditor Opt-In for BetaFeatures,"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/43 //
+
+== Narrative ==
+
+As a user, I want the option to enable Visual Editor, if it is not available by default on this site.
+
+== Acceptance Criteria ==
+
+Some sites require user opt-in for the VisualEditor (the English and German Wikipedias in particular aren't ready yet to make this feature available by default). So we would like to make the basic version of VisualEditor available as a prominent BetaFeature -- but for those sites only. For example, we could handle this issue by having a site whitelist/blacklist for each beta feature -- or there may also be other technical solutions that work just as effectively to achieve the same results.
+
+See more feature requirements here:
+
+ [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] 
+
+
+
+
+
+== Related Bugs ==
+
+== Related Stories ==",1418054265,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-v2ol64y3mialrzwjykor,task_description,resolved
+VisualEditor Opt-In for BetaFeatures,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/43 | mingle]] on 2013-10-11 at 18:00:20, @MarkTraceur wrote:
+
+https://gerrit.wikimedia.org/r/78795",1418054267,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-v2ol64y3mialrzwjykor,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,AFAICT this hasn't been done yet?,1417898198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ie5f4kyk73zuc2topaj7,task_description,resolved
+Expose the production citoid service publicly so we can start switching scripts over to use it,My guess it the problem was T133830 or similar.,1461837156,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Er, I added the above commit 1,5 years ago.. not sure what just happened here...",1461825954,PHID-USER-xwxce3kpvsv54t735g7q,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,Thank you everyone. :-),1422075147,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Change 184904 merged by Alexandros Kosiaris:
+Re-use Parsoid Varnishes for citoid too
+
+[[https://gerrit.wikimedia.org/r/184904]]",1422056327,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Change 184904 had a related patch set uploaded (by Jforrester):
+Re-use Parsoid Varnishes for citoid too
+
+[[https://gerrit.wikimedia.org/r/184904]]
+
+#patch-for-review",1421252997,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Change 178419 abandoned by Catrope:
+Expose citoid through misc-web
+
+Reason:
+Forgot to abandon this. Gabriel said he'd work on caching infra for the entire services cluster, which they need for RESTbase, but which Citoid would then also use once it's done.
+
+[[https://gerrit.wikimedia.org/r/178419]]",1418914800,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Citoid !== Cite, they're totally different.
+
+However, Gabriel said he would work on setting up a services Varnish thing as part of setting up RESTbase, and Citoid could hitch a ride on that. So this ticket should have been marked as blocked on services, instead it was marked as blocked on ops by mistake.
+
+Under normal circumstances I would have attended SoS yesterday and would have known to file this correctly, but I wasn't able to make it.",1418914576,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Hello,
+
+So I am a bit unclear on this and the two tasks listed as blocked (T62768 and T67540) did not make it any more clear for me. So here's the question:
+
+We want citoid to be publicly available as an endpoint so that Cite and VisualEditor to directly query it, right ?
+
+I assume, Cite is this: http://www.mediawiki.org/wiki/Extension:Cite in which case I am wondering why a Mediawiki Extension can not query an internal endpoint (namely citoid.svc.eqiad.wmnet). I am not at all familiar with Cite so it might be javascript, served by Cite, that runs on the user's browser that does the querying at which point what this ticket asks make sense.
+
+Same thing goes for VisualEditor, I just want to clarify what/who will be doing the endpoint query. Is the situation different than Cite ? And if yes, how ? 
+
+As as side note and since I mentioned javascript, what about same origin policy ? Will that end up being a problem ?",1418914466,PHID-USER-xwxce3kpvsv54t735g7q,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Change 178419 had a related patch set uploaded (by Catrope):
+Expose citoid through misc-web
+
+[[https://gerrit.wikimedia.org/r/178419]]
+
+#patch-for-review",1418095569,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+"Show the VisualEditor toolbar/editor chrome as soon as VE scripts are loaded, rather than blocking on waiting for the content to load",,1417558133,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-snvwps4elfr6ehb3bg2z,task_description,resolved
+"Show the VisualEditor toolbar/editor chrome as soon as VE scripts are loaded, rather than blocking on waiting for the content to load","Change 192072 merged by jenkins-bot:
+Show the toolbar as soon as the target has been activated
+
+[[https://gerrit.wikimedia.org/r/192072]]",1425295969,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-snvwps4elfr6ehb3bg2z,task_subcomment,NA
+"Show the VisualEditor toolbar/editor chrome as soon as VE scripts are loaded, rather than blocking on waiting for the content to load","Change 192072 had a related patch set uploaded (by Esanders):
+Show the toolbar as soon as the target has been activated
+
+[[https://gerrit.wikimedia.org/r/192072]]
+
+#patch-for-review",1424515634,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-snvwps4elfr6ehb3bg2z,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"The Page options menu, which appears when the ""hamburger"" button is clicked, goes off-screen in RTL wikis.
+
+Screenshot with wrong display in Hebrew:
+https://commons.wikimedia.org/wiki/File:VisualEditorBug2a.png
+{F168546}
+
+Screenshot with correct display in English:
+https://commons.wikimedia.org/wiki/File:VisualEditorBug2b.png
+{F168548}
+
+(I have a vague recollection that I reported it once, but I cannot find it now. If somebody does find it, please mark this one as a dupe.)",1417531699,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_description,resolved
+VisualEditor page options menu goes off-screen in RTL wikis,My fix for this caused part of T98506.,1432467767,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Change 179581 merged by jenkins-bot:
+ClippableElement: Handle clipping with left edge
+
+[[https://gerrit.wikimedia.org/r/179581]]",1418762928,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Change 179565 abandoned by Amire80:
+Add noflip to oo-ui-popupToolGroup-left and -right
+
+Reason:
+Done better in I0c2d9800a1c0bdbe523c978307546ec205202681 .
+
+[[https://gerrit.wikimedia.org/r/179565]]",1418431819,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Change 179581 had a related patch set uploaded (by Bartosz Dziewoński):
+[WIP] ClippableElement: Handle clipping with left edge
+
+[[https://gerrit.wikimedia.org/r/179581]]
+
+#patch-for-review",1418431572,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"The real issue is that ClippableElement doesn't handle clipping with the left edge of browser window, only with the right edge.",1418430091,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Setting appropriate left and right values for oo-ui-popupToolGroup-left and oo-ui-popupToolGroup-right by adding noflip seems to fix the issue, but because I'm not an experienced oojs-ui dev, this needs review.
+
+For now I fixed this locally in he.wikipedia by adding:
+
+```
+.oo-ui-popupToolGroup-left > .oo-ui-toolGroup-tools {
+	left: 0;
+	right: auto;
+}
+```",1418426437,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Change 179565 had a related patch set uploaded (by Amire80):
+Add noflip to oo-ui-popupToolGroup-left and -right
+
+[[https://gerrit.wikimedia.org/r/179565]]
+
+#patch-for-review",1418424391,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+Support legal requirements about publishing,"**Context**
+
+Adjust the publishing UI to meet the legal requirements for attribution.
+
+**Narrative**
+
+As a user, I can be informed about the terms under which my content gets published, so that I can just ignore them but no potential legal concerns are raised.  
+
+**Acceptance Criteria**
+
+  # When the user starts a translation, legal text is provided in the new panel dialog as shown in the design notes:
+  ## The legal text is similar to the one appearing in the wikitext editor (those links should point to the same place).
+  ## The only difference is that the ""By pressing the 'X' button"" part should match the name of the button in the UI for all languages
+  # We need to solve the case of users building a URL to access the translation view and thus bypassing the legal agreement, here is how we'll do that:
+  ## For users that started a translation (and have been exposed to the legal terms already) we should let them get into he translation at any time without any additional interruption.
+  ## For users that try to access the translation view directly for an article they have not explicitly started before, instead of directing them to the Translation view, they will be directed to the Translation Dashboard. There, the new translation dialog will be open and they will be able to start the translation with a single click (after reading the legal terms, as we all usually do).
+  # Read the acceptance criteria 1 again, and realise that this affects not only the ""new translation dialog"" but any entry point. Go and fix it for the red link entry point, and remember for future entry points to either (a) link to the Dashboard with the new translation fields pre-filled or (b) show the legal terms, or you may go to jail.
+
+**Design notes**
+
+The new translation dialog should incorporate the legal text, and we need to make sure that users are exposed at leas once (and prefereably only once) to it:
+
+{F17019}
+
+
+When a user tries to access another user's draft:
+- The draft content becomes non-interactive and translucent (opacity: 0.5) to indicate it is ""disabled"".
+- Publish button and saving indicator are hidden.
+- A dialog is shown in the warning area (view mockup below). It provides (a) a link to the translation author page, (b) a link to start a new translation (will go to the dashboard with the ""new translation"" dialog open and the fields pre-filled), (c) the legal text (note that the name of the button mentioned should match the current UI) and (d) a button to continue.
+- If the user continues, the above described elements would disappear and the user would be allowed to edit the draft.
+
+{F17098}",1417153277,PHID-USER-ttw4tpoosxc4pbmskrla,PHID-TASK-4res6cs3y6litn77e77o,task_description,resolved
+Support legal requirements about publishing,"Change 181863 merged by jenkins-bot:
+Change the cookie name for valid translation workflow
+
+[[https://gerrit.wikimedia.org/r/181863]]",1419593378,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 181863 had a related patch set uploaded (by Santhosh):
+Change the cookie name for valid translation workflow
+
+[[https://gerrit.wikimedia.org/r/181863]]
+
+#patch-for-review",1419588453,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 179105 merged by jenkins-bot:
+Make sure translator see license text even if use manually created URL
+
+[[https://gerrit.wikimedia.org/r/179105]]",1419252073,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"I adjusted the styling for the red interlanguage links dialog ([[ https://gerrit.wikimedia.org/r/#/c/179489/ | patchset]]) and the new translation dialog on the dashboard ([[https://gerrit.wikimedia.org/r/#/c/179498/ | patchset]]). 
+
+Screenshots:
+{F21011}
+{F21017}",1418407355,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"I adjusted the styling for the red interlanguage links dialog [[ https://gerrit.wikimedia.org/r/#/c/179489/ | patchset]]) and the new translation dialog on the dashboard ([[https://gerrit.wikimedia.org/r/#/c/179498/ | patchset]]). 
+
+Screenshots:
+{F21011}
+{F21017}",1418407345,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"I adjusted the styling for the red interlanguage links dialog ([[ URL | at ]] [[ https://gerrit.wikimedia.org/r/#/c/179489/ | patchset]]) and the new translation dialog on the dashboard ([[https://gerrit.wikimedia.org/r/#/c/179498/ | patchset]]). 
+
+Screenshots:
+{F21011}
+{F21017}",1418407332,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"I adjusted the styling for the red interlanguage links dialog at https://gerrit.wikimedia.org/r/#/c/179489/
+
+Screenshot:
+{F21011}",1418404447,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,Screenshot of CX dashboard with source selector automatically opened and prefilled with URL parameters {F20775},1418292534,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 179105 had a related patch set uploaded (by Santhosh):
+Make sure translator see license text even if use manually created URL
+
+[[https://gerrit.wikimedia.org/r/179105]]
+
+#patch-for-review",1418292390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"> publishing only happens in the regular editor (the Translation View in this case).
+
+""Translation view"" doesn't sound like the regular editor.
+
+P.s.: Confirmed, it's not. Commented on that at https://www.mediawiki.org/wiki/Talk:Content_translation/Translation_view",1417616976,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"> publishing only happens in the regular editor (the Translation View in this case).
+
+""Translation view"" doesn't sound like the regular editor.",1417614467,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 176327 merged by jenkins-bot:
+Add the license agreement text to new translation entry points
+
+[[https://gerrit.wikimedia.org/r/176327]]",1417528352,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,@Nemo_bis: publishing only happens in the regular editor (the Translation View in this case). The purpose of this is to show the legal terms at the beginning of the process so that users can focus on translating on the Translation View without additional legal text or confirmation steps when publishing.,1417175486,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"This would be easier if ""publishing"" only happened in the regular editor: see for instance how VisualEditor sends you to action=edit (actually action=submit) when commuting an edit.",1417165968,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,New translation dialog with legal agreement: {F17064},1417165583,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 176327 had a related patch set uploaded (by Santhosh):
+Add the license agreement text to new translation dialog
+
+[[https://gerrit.wikimedia.org/r/176327]]
+
+#patch-for-review",1417164197,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+VisualEditor not updating in beta labs,"As of this writing, http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version says beta labs is running a 20-hour old version of VE, and that seems to be accurate given that there are a few bugs that are fixed in master but not in beta.",1417039011,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kok6e7cmusz47p2lyu46,task_description,resolved
+VisualEditor not updating in beta labs,"Seems there was some transient error that prevented Gerrit to merge the bot change automatically. Apparently due to some merge conflict.  I am not sure what went wrong but that is definitely fixed.
+
+The last bot change is https://gerrit.wikimedia.org/r/#/c/176867/ which updates the VisualEditor submodule in mediawiki/extensions.git to 6c4c340
+
+I have pulled the repo and did `git submodule update --init VisualEditor`, that points to the same commit 6c4c340.",1417552368,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+VisualEditor not updating in beta labs,"Seems the script python I wrote to update the VisualEditor repo is no more working / choking on something.  I haven't noticed this task until it has be pointed to me during the Releng weekly checkin.
+
+The related Jenkins job is `mwext-VisualEditor-sync-gerrit`  one might want to look at it to see what is happening and hopefully fix it.
+
+
+If it is quite tonight at home, I *might* be able to look at this issue.",1417542650,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+VisualEditor not updating in beta labs,"The commit on Beta Labs has now moved to d20cc324…; however, for ~ 24 hours 9dad03819… has been the latest merged commit. The Jenkins views on code updates to Beta Labs looks fine (notwithstanding https://integration.wikimedia.org/ci/view/Beta/job/beta-scap-eqiad/31718/console which happened much later). Odd.",1417229051,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+VisualEditor not updating in beta labs,"info-extensions-VisualEditor.json says:
+
+```
+{
+  ""head"": ""a14f88d80eec331a94cfdfc50da800c8fbc68ef3"",
+  ""remoteURL"": ""https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git"", 
+  ""branch"": ""a14f88d80eec331a94cfdfc50da800c8fbc68ef3"", 
+  ""headCommitDate"": ""1417037864"", 
+  ""headSHA1"": ""a14f88d80eec331a94cfdfc50da800c8fbc68ef3"", 
+  ""@directory"": ""/srv/mediawiki-staging/php-master/extensions/VisualEditor""
+}
+```",1417040928,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+VisualEditor not updating in beta labs,deployment-bastion:/srv/mediawiki-staging/php-master/extensions/VisualEditor is at git hash a14f88d which seems to match https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FVisualEditor and https://github.com/wikimedia/mediawiki-extensions-VisualEditor/commits/master,1417040089,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"We are getting ready to integrate Parsoid with RESTBase. This task tracks our progress and what's left to do.
+
+Generally, we need a way to communicate multiple mime entities both in POST requests to Parsoid, and in responses from Parsoid back to RESTBase. We could use [RFC 2387](https://tools.ietf.org/html/rfc2387) or [RFC 2388](https://www.ietf.org/rfc/rfc2388.txt), but this seems to be a bit cumbersome especially for the response part. Instead, we can just use a simple JSON encoding with a structure that's otherwise basically identical to MIME.
+
+The downside of using JSON is possibly efficiency (quite a bit more escaping going on, especially for HTML-in-JSON). However, we could address that later by optionally using a binary encoding like [msgpack](http://msgpack.org/) without changing the message structure itself.
+
+Another option to consider would be to flatten the structure by using names like `original.html`. This would make it easy to encode the same message as `multipart/related`.
+
+== Implementation notes ==
+
+- Parsoid: Slightly simpler format done & deployed. Needs to be updated to indicate the mime types as documented above.
+- RESTBase: Prototype implementation.
+  - should pass to Parsoid:
+    - previous revision's HTML + data-parsoid OnEdit
+    - current revision's HTML + data-parsoid OnDependencyChange
+- Parsoid WIP implementation: https://gerrit.wikimedia.org/r/#/c/165685/
+- RESTBase to be done
+",1416964657,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_description,resolved
+RESTBase / Parsoid integration - waiting for parsoid deploy,Resolved by Parsoid deploy yesterday.,1424194514,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Latest iteration of the RESTBase transform API: https://github.com/wikimedia/restbase/pull/173
+
+Testing revealed an issue with selser, possibly on the Parsoid side: T89411",1423784954,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,See https://github.com/wikimedia/restbase/blob/master/specs/mediawiki/v1/content.yaml for the content API v1 spec in development.,1423596265,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,This task is getting rather unwieldy.  I'm going to split it up into better-digestible subtasks.,1422989107,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Notes from conversation with @gwicke:
+
+* We don't want the client to pass in `original` -- RESTBase will always find that on its own (e.g. from storage)
+* We don't need to allow the client to specify the content type //yet//
+* Assume client is always using the latest spec for whichever Content-Type they're using
+* Client //might// know the specific Content-Type, but we shouldn't break if we can fallback to a functioning default",1422922493,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, your example is from the Parsoid v2 API, while the RESTBase transform API can just use flat posts. We make the assumption that the transform API does not need to deal with mis-matches in the posted content, as the use cases this is intended for (VE, edit widgets etc) aren't long-running & don't involve storage.
+
+`multipart/form-data` does support per-field content-type headers, but by default those are not set afaik.",1422920885,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"It's from the discussion above:
+
+{F34542}",1422919943,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, is there a use case for this? The discussion about multipart/form-data is about the RESTBase API, not the Parsoid v2 API.",1422919683,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"What is the multipart/form-data counterpart to the following application/json?
+
+```
+{
+    ""html"": {
+        ""headers"": {
+            ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+        },
+        ""body"": ""<html>The modified HTML</html>""
+    },
+    ""original"": {
+        ""revid"": 12345,
+        ""wikitext"": {
+            ""headers"": {
+                ""content-type"": ""text/plain;profile=mediawiki.org/specs/wikitext/1.0.0""
+            },
+            ""body"": ""the original wikitext""
+        },
+        ""html"": {
+            ""headers"": {
+                ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+            },
+            ""body"": ""the original HTML""
+        },
+        ""data-parsoid"": {
+            ""headers"": {
+                ""content-type"": ""application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1""
+            },
+            ""body"": {
+                ""ids"": {}
+            }
+        }
+    }
+}
+```
+
+
+Should each multipart field contain JSON?  For example:
+
+```--------------------------d0f6b49b1b041887
+Content-Disposition: form-data; name=""html""; filename=""html""
+Content-Type: application/json
+
+{
+    ""headers"": {
+        ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+    },
+    ""body"": ""<html>The modified HTML</html>""
+}
+
+--------------------------d0f6b49b1b041887
+Content-Disposition: form-data; name=""original""; filename=""original""
+Content-Type: application/json
+
+{
+    ""revid"": 12345,
+    ""wikitext"": {
+        ""headers"": {
+            ""content-type"": ""text/plain;profile=mediawiki.org/specs/wikitext/1.0.0""
+        },
+        ""body"": ""the original wikitext""
+    },
+    ""html"": {
+        ""headers"": {
+            ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+        },
+        ""body"": ""the original HTML""
+    },
+    ""data-parsoid"": {
+        ""headers"": {
+            ""content-type"": ""application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1""
+        },
+        ""body"": {
+            ""ids"": {}
+        }
+    }
+}
+
+--------------------------d0f6b49b1b041887--
+```
+",1422919149,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,This is what Parsoid uses: https://github.com/wikimedia/parsoid/blob/master/lib/mediawiki.ApiRequest.js#L224,1422657845,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Great, thanks!",1422657813,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#1005304, @Jdouglas wrote:
+> Can you point me to the docs on how to get Wikitext from the MW API?
+
+[action=raw](https://www.mediawiki.org/wiki/Manual:Parameters_to_index.php#Raw) ought to help",1422657749,PHID-USER-hxwwywcyzpooynxuo7a2,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> The other missing bit is that we currently don't actually fetch wikitext from the MW API. We need to do so (and perhaps store it) for proper html2wt support.
+
+Can you point me to the docs on how to get Wikitext from the MW API?",1422657577,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#980780, @Jdouglas wrote:
+> * accept a `multipart/form-data` body rather than JSON
+
+We could also accept both.
+
+The other missing bit is that we currently don't actually fetch wikitext from the MW API. We need to do so (and perhaps store it) for proper html2wt support.",1422137549,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Ok, so it sounds like we need only augment the `POST /{domain}/v1/transform/<html|wt>/to/html` endpoint to:
+
+* allow an optional `bodyOnly` field
+* accept a `multipart/form-data` body rather than JSON
+
+Sound right?",1421362618,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, I think we need to always request the full HTML from Parsoid, so that our storage has the full version. If bodyOnly was requested in the POST, then we should probably pluck out the body with a regexp in restbase.
+
+Regarding `multipart/form-data` vs. `application/json`: Should we promote the former for the transform API?",1421362232,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, I think we need to always request the full HTML from Parsoid, so that our storage has the full version. If bodyOnly was requested in the POST, then we should probably pluck out the body with a regexp in restbase.
+
+Regarding `multipart/form-data` vs. `application/json`: Should we promote the former for now?",1421362215,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#976719, @Jdouglas wrote:
+>> test whether the original content was indeed passed to parsoid
+> 
+> @gwicke For specification purposes, can you define ""original"" in this context?
+> 
+> Does it always mean ""penultimate"" with respect to the state of the wiki behind `{domain}`?
+
+On second thought, does it mean ""the revision for which new changes are being submitted""?",1421361979,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Does the following look correct?
+
+**User -> RESTBase:**
+
+```
+{
+  method: 'post',
+  uri: '/{domain}/v1/transform/<html|wt>/to/html',
+  headers: {
+    'content-type': 'application/json',
+  },
+  body: {
+    content: 'Hello, world!',
+    bodyOnly: true,
+  },
+}
+```
+
+**RESTBase -> Parsoid:**
+
+```
+{
+  method: 'post',
+  uri: 'http://parsoid-lb.eqiad.wikimedia.org/{domain}/FAKE_PAGE_NAME',
+  headers: {
+    'content-type': 'application/x-www-form-urlencoded',
+  },
+  body: '$BODY',
+}
+```
+
+
+Where `$BODY` is the form-urlencoded representation of:
+
+```
+{
+  oldid: 123, // optional
+  html: 'Hello, world!',
+  body: true, // optional
+}
+```",1421360972,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Does the following look correct?
+
+**User -> RESTBase:**
+
+```
+{
+  method: 'post',
+  uri: '/{domain}/v1/transform/<html|wt>/to/html',
+  headers: {
+    'content-type': 'application/json',
+  },
+  body: {
+    content: 'Hello, world!',
+    bodyOnly: true,
+  },
+}
+```
+
+**RESTBase -> Parsoid:**
+
+```
+{
+  method: 'post',
+  uri: 'http://parsoid-lb.eqiad.wikimedia.org/{domain}/{page}',
+  headers: {
+    'content-type': 'application/x-www-form-urlencoded',
+  },
+  body: '$BODY',
+}
+```
+
+
+Where `$BODY` is the form-urlencoded representation of:
+
+```
+{
+  oldid: 123, // optional
+  html: 'Hello, world!',
+  body: true, // optional
+}
+```",1421360786,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#977393, @Jdouglas wrote:
+>> Anyone want to do a final check of the tests to verify they cover the scope of this task?
+> 
+> We're not quite there yet.  The [[ https://www.mediawiki.org/wiki/Parsoid/API | Parsoid API ]] accepts a `body` flag that reduces the scope of the response.
+> 
+> @GWicke do you know who is using this feature?  
+
+AFAIK this is currently used by Flow, likely also VE.
+
+> Is it something RESTBase should provide via its own API?
+
+Yes. We talked about supporting a plain POST body with the html/wt in 'content' and optional other fields like a 'bodyOnly' boolean. I would vote for using this option in the transform API, as it is easy enough and more efficient for binary content when using `multipart/form-data` encoding. We can always add JSON as an option later.",1421275798,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> Anyone want to do a final check of the tests to verify they cover the scope of this task?
+
+We're not quite there yet.  The [[ https://www.mediawiki.org/wiki/Parsoid/API | Parsoid API ]] accepts a `body` flag that reduces the scope of the response.
+
+@GWicke do you know who is using this feature?  Is it something RESTBase should provide via its own API?  If so, how will it effect storage?  We might not want to store the `body.innerHTML`, but instead store the entire content.  The drawback to this is that we'll have to replicate some of the same DOM parsing that Parsoid currently handles to be able to subset the content on demand.",1421272316,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> test whether the original content was indeed passed to parsoid
+
+@gwicke For specification purposes, can you define ""original"" in this context?
+
+Does it always mean ""penultimate"" with respect to the state of the wiki behind `{domain}`?",1421260909,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,Strictly speaking https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/ondemand.js#L87 does not really test whether the original content was indeed passed to parsoid. Maybe we could let parsoid emit a header if it received the original properly. We could then assert that header in the response.,1421170310,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I think we're pretty close to marking this one as done.  Anyone want to do a final check of the tests to verify they cover the scope of this task?
+
+//On-demand generation of HTML and data-parsoid://
+
+https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/ondemand.js
+
+//html2wt conversion support://
+
+https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/transform.js",1421107926,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I think we're pretty close to ready to close this task.  Anyone want to do a final check of the tests to verify they cover the scope of this task?
+
+//On-demand generation of HTML and data-parsoid://
+
+https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/ondemand.js
+
+//html2wt conversion support://
+
+https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/transform.js",1421107412,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"The transform endpoint is now functioning: https://github.com/wikimedia/restbase/pull/98
+
+After #98, is there anything else needed for T75955?
+
+Answer: yes: https://coveralls.io/files/412841510#L93",1420502909,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"The transform endpoint is now functioning: https://github.com/wikimedia/restbase/pull/98
+
+After #98, is there anything else needed for T75955?",1420499740,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,The transform endpoint is now functioning: https://github.com/wikimedia/restbase/pull/98,1420499685,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Oh, my mistake.  The new patch already supports `POST parsoid/v2/{domain}/wt`.",1419981101,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, basically title and oldid are optional, so both `POST parsoid/v2/{domain}/wt/{title}` and `POST parsoid/v2/{domain}/wt` should work. If the request without title doesn't work in parsoid right now, then we could work around it by inventing one like 'Main_Page' for now. IIRC that's what Parsoid used to do as well if the title is missing.
+
+Edit: Parsoid [uses the configured mainpage for the wiki](https://github.com/wikimedia/parsoid/blob/1f43a268b70cf4a91b4e982e328e9dbfd0889f96/lib/mediawiki.parser.environment.js#L248), which happens to be 'Main Page' for enwiki, but differs for other languages.",1419981080,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, basically title and oldid are optional, so both `POST parsoid/v2/{domain}/wt/{title}` and `POST parsoid/v2/{domain}/wt` should work. If the request without title doesn't work in parsoid right now, then we could work around it by inventing one like 'Main_Page' for now. IIRC that's what Parsoid used to do as well if the title is missing.",1419980835,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"When there's no title or revision, i.e. `POST /{domain}/v1/transform/html/to/wt`, what should be the Parsoid request URL?
+
+`POST parsoid/v2/{domain}/wt/{title}/{oldid}`
+
+Parsoid appears to allow gibberish:
+
+`POST parsoid/v2/{domain}/wt/___NOT_A_REAL_TITLE_1231___/`
+
+Should we designate a special placeholder title?  Or should we update Parsoid to respond to `POST parsoid/v2/{domain}/wt`?",1419980679,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"When there's no title or revision, i.e. `POST /{domain}/v1/transform/html/to/wt`, what should be the Parsoid request URL?
+
+`POST parsoid/v2/{domain}/wt/{title}/{oldid}`",1419980564,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,{icon thumbs-up},1419966615,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: I think we can always wrap things into a full request on the restbase end, and just add the latest configured parsoid mime type if we didn't receive any from the client. So we can perhaps just strike this as a parsoid requirement.",1419967245,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: I think we can always wrap things into the a full request on the restbase end, and just add the latest configured parsoid mime type if we didn't receive any from the client. So we can perhaps just strike this as a parsoid requirement.",1419966212,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: I think we can always wrap things into the a full request on the restbase end, and just add the latest configured parsoid mime type if we didn't receive any from the client.",1419966184,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@gwicke:
+
+> If the modified html is just a string, then Parsoid is expected to assume that it's in the latest html version.
+
+Does this refer to a POST to //parsoid/v2/{domain}/wt/{title}/{oldid}// with a request body containing raw HTML?",1419965826,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@gwicke:
+
+> If the modified html is just a string, then Parsoid is expected to assume that it's in the latest html version.If the modified html is just a string, then Parsoid is expected to assume that it's in the latest html version.
+
+Does this refer to a POST to //parsoid/v2/{domain}/wt/{title}/{oldid}// with a request body containing raw HTML?",1419965809,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,See proposed tests here: https://github.com/wikimedia/restbase/pull/98,1419900797,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Change 165685 merged by Jdouglas:
+API v2 parsing and serialization routes
+
+[[https://gerrit.wikimedia.org/r/165685]]",1419898786,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: To be fair, JSON schema validation is not usually happening for free just by having stronger typing.",1419896272,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Understandable, considering we're operating without a type system. :]",1419896146,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,@jdouglas I think validation is fairly embryonic at this point. Definitely agreed on 400 being better than 500.,1419895777,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,Gotcha. Does Parsoid have any infrastructure for validation? A 400 with a reason might be more informative to an erroneous client than a 500 with an obscure es6-shim stack trace.,1419895327,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: Passing in data-parsoid without ids in the body could be considered a bug in the client worth highlighting. If that passed unnoticed, the result would likely be wikitext corruption in edits, which would make many people unhappy. If we send the 'original' object, then it should contain both html *and* a valid data-parsoid attribute, both from storage. 
+
+Parsoid also needs to support html2wt conversion without the 'original' object (for new page creation for example). That might be a simpler mode to test for the first iteration.",1419894921,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Here's the source of the problem: https://github.com/wikimedia/parsoid/blob/04721c235f9cc6d4ffdca8418e73d602aecfebba/lib/mediawiki.DOMUtils.js#L1963
+
+Would it be better to allow for an id-less body?
+
+e.g.
+
+```
+Object.keys( dp.ids || {} ).forEach(function ( key ) {
+```",1419890893,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"This works for `wt` when I replace `""body"": {}"" with the following:
+
+```
+        ""body"": {
+            ""counter"": 1,
+            ""ids"": {
+                ""mwAA"": {
+                    ""dsr"": [
+                        0,
+                        949,
+                        0,
+                        0
+                    ]
+                },
+                ""mwAQ"": {
+                    ""dsr"": [
+                        928,
+                        949,
+                        0,
+                        0
+                    ]
+                }
+            }
+        }
+```
+
+EDIT: The key is having `body.ids` -- at least `""body"": { ""ids"": {} }`",1419890072,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"This works for `wt` when I replace `""body"": {}"" with the following:
+
+```
+        ""body"": {
+            ""counter"": 1,
+            ""ids"": {
+                ""mwAA"": {
+                    ""dsr"": [
+                        0,
+                        949,
+                        0,
+                        0
+                    ]
+                },
+                ""mwAQ"": {
+                    ""dsr"": [
+                        928,
+                        949,
+                        0,
+                        0
+                    ]
+                }
+            }
+        }
+```
+
+The key is having `body.ids` -- at least `""body"": { ""ids"": {} }`",1419890060,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"This works for `wt` when I replace `""body"": {}"" with the following:
+
+```
+        ""body"": {
+            ""counter"": 1,
+            ""ids"": {
+                ""mwAA"": {
+                    ""dsr"": [
+                        0,
+                        949,
+                        0,
+                        0
+                    ]
+                },
+                ""mwAQ"": {
+                    ""dsr"": [
+                        928,
+                        949,
+                        0,
+                        0
+                    ]
+                }
+            }
+        }
+```",1419889456,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"This appears to work for `pagebundle` in place of `wt`.
+
+```
+curl -s -H ""Content-Type: application/json"" -X POST -d @T75955.json localhost:8000/v2/en.wikipedia.org/pagebundle/Main_Page/1
+```
+
+```
+{
+    ""data-parsoid"": {
+        ""body"": {
+            ""counter"": 1,
+            ""ids"": {
+                ""mwAA"": {
+                    ""dsr"": [
+                        0,
+                        949,
+                        0,
+                        0
+                    ]
+                },
+                ""mwAQ"": {
+                    ""dsr"": [
+                        928,
+                        949,
+                        0,
+                        0
+                    ]
+                }
+            }
+        },
+        ""headers"": {
+            ""content-type"": ""application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1""
+        }
+    },
+    ""html"": {
+        ""body"": ""<!DOCTYPE html>\n<html prefix=\""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/\"" about=\""http://en.wikipedia.org/wiki/Special:Redirect/revision/12345\""><head prefix=\""mwr: http://en.wikipedia.org/wiki/Special:Redirect/\""><meta property=\""mw:articleNamespace\"" content=\""0\""/><link rel=\""dc:replaces\"" resource=\""mwr:revision/12342\""/><meta property=\""dc:modified\"" content=\""2002-02-16T19:00:49.000Z\""/><meta about=\""mwr:user/0\"" property=\""dc:title\"" content=\""210.55.230.17\""/><link rel=\""dc:contributor\"" resource=\""mwr:user/0\""/><meta property=\""mw:revisionSHA1\"" content=\""1ec7fece702a00b9d99c0e848eea8c524d12fe3f\""/><meta property=\""dc:description\"" content=\""*\""/><meta property=\""mw:parsoidVersion\"" content=\""0\""/><link rel=\""dc:isVersionOf\"" href=\""//en.wikipedia.org/wiki/Main_Page\""/><title>Main_Page</title><base href=\""//en.wikipedia.org/wiki/\""/><link rel=\""stylesheet\"" href=\""//en.wikipedia.org/w/load.php?modules=mediawiki.legacy.commonPrint,shared|mediawiki.skinning.elements|mediawiki.skinning.content|mediawiki.skinning.interface|skins.vector.styles|site|mediawiki.skinning.content.parsoid&amp;only=styles&amp;debug=true&amp;skin=vector\""/></head><body id=\""mwAA\"" lang=\""en\"" class=\""mw-content-ltr sitedir-ltr ltr mw-body mw-body-content mediawiki\"" dir=\""ltr\""><p id=\""mwAQ\"">the original wikitext</p></body></html>"",
+        ""headers"": {
+            ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+        }
+    }
+}
+```",1419887881,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I converted the `POST parsoid/v2/{domain}/wt/{title}/{oldid}` example above to a JSON file, and attempted to run it locally, but something went wrong:
+
+
+```
+$ curl -H ""Content-Type: application/json"" -X POST -d @T75955.json localhost:8000/v2/en.wikipedia.org/wt/Main_Page/1
+Cannot call method on undefined
+TypeError: Cannot call method on undefined
+    at Object.ES.CheckObjectCoercible (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:152:17)
+    at Object.ES.ToObject (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:164:26)
+    at Function.Object.keys (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:905:38)
+    at Object.DU.applyDataParsoid (/home/jdouglas/code/parsoid/lib/mediawiki.DOMUtils.js:1958:10)
+    at Promise.then.timeout.then.apiUtils.jsonResponse.wikitext.headers.content-type (/home/jdouglas/code/parsoid/api/routes.js:275:7)
+    at /home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1220:20
+    at Object._onImmediate (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1177:28)
+    at processImmediate [as _immediateCallback] (timers.js:345:15)
+```
+
+Any debugging pointers?
+
+{F25608}
+
+EDIT: It works if I s/wt/html/g in the URL.",1419887417,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I converted the `POST parsoid/v2/{domain}/wt/{title}/{oldid}` example above to a JSON file, and attempted to run it locally, but something went wrong:
+
+
+```
+$ curl -H ""Content-Type: application/json"" -X POST -d @T75955.json localhost:8000/v2/en.wikipedia.org/wt/Main_Page/1
+Cannot call method on undefined
+TypeError: Cannot call method on undefined
+    at Object.ES.CheckObjectCoercible (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:152:17)
+    at Object.ES.ToObject (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:164:26)
+    at Function.Object.keys (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:905:38)
+    at Object.DU.applyDataParsoid (/home/jdouglas/code/parsoid/lib/mediawiki.DOMUtils.js:1958:10)
+    at Promise.then.timeout.then.apiUtils.jsonResponse.wikitext.headers.content-type (/home/jdouglas/code/parsoid/api/routes.js:275:7)
+    at /home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1220:20
+    at Object._onImmediate (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1177:28)
+    at processImmediate [as _immediateCallback] (timers.js:345:15)
+```
+
+Any debugging pointers?
+
+{F25608}",1419887280,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I converted the `POST parsoid/v2/{domain}/wt/{title}/{oldid}` example above to a JSON file, and attempted to run it locally, but something went wrong:
+
+
+```
+$ curl -H ""Content-Type: application/json"" -X POST -d @T75955.json localhost:8000/v2/en.wikipedia.org/wt/Main_Page/1
+Cannot call method on undefined
+TypeError: Cannot call method on undefined
+    at Object.ES.CheckObjectCoercible (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:152:17)
+    at Object.ES.ToObject (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:164:26)
+    at Function.Object.keys (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:905:38)
+    at Object.DU.applyDataParsoid (/home/jdouglas/code/parsoid/lib/mediawiki.DOMUtils.js:1958:10)
+    at Promise.then.timeout.then.apiUtils.jsonResponse.wikitext.headers.content-type (/home/jdouglas/code/parsoid/api/routes.js:275:7)
+    at /home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1220:20
+    at Object._onImmediate (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1177:28)
+    at processImmediate [as _immediateCallback] (timers.js:345:15)
+```
+
+Any debugging pointers?",1419887206,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: Yes, that should work. See https://www.mediawiki.org/wiki/Parsoid/Setup#Manual_installation_on_Linux_or_Mac_OS_X
+
+Basic summary:
+
+```
+# clone parsoid
+git clone ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid
+
+cd parsoid
+
+# check out the patch with the git commandline shown in gerrit:
+git fetch ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid refs/changes/85/165685/13 && git checkout FETCH_HEAD
+npm install
+
+node api/server
+```
+
+This should bring up parsoid locally. The wikipedia domains are all configured by default.",1419886351,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: Yes, that should work. See https://www.mediawiki.org/wiki/Parsoid/Setup#Manual_installation_on_Linux_or_Mac_OS_X
+
+Basic summary:
+
+```
+# clone parsoid
+git clone ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid
+
+cd parsoid
+
+# check out with the git commandline shown in gerrit:
+git fetch ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid refs/changes/85/165685/13 && git checkout FETCH_HEAD
+npm install
+
+node api/server
+```
+
+This should bring up parsoid locally. The wikipedia domains are all configured by default.",1419886292,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: Yes, that should work. See https://www.mediawiki.org/wiki/Parsoid/Setup#Manual_installation_on_Linux_or_Mac_OS_X
+
+Basic summary:
+
+```bash
+# clone parsoid
+git clone ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid
+
+cd parsoid
+
+# check out with the git commandline shown in gerrit:
+git fetch ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid refs/changes/85/165685/13 && git checkout FETCH_HEAD
+npm install
+
+node api/server
+```
+
+This should bring up parsoid locally. The wikipedia domains are all configured by default.",1419886278,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Is it feasible to run this Parsoid patch in my local dev environment so that I can develop against it?
+
+EDIT: I found instructions [[ https://github.com/wikimedia/cassandra-codec/pull/9#issuecomment-68279450 | here ]].",1419886395,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Is it feasible to run this Parsoid patch in my local dev environment so that I can develop against it?
+
+EDIT: I found instructions [[ https://github.com/wikimedia/cassandra-codec/pull/9#issuecomment-68279450 | here ]].
+```",1419886375,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,Is it feasible to run this Parsoid patch in my local dev environment so that I can develop against it?,1419885989,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,Is it feasible to run this patch in my local dev environment so that I can develop against it?,1419885973,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,I updated the patch with that.,1419295340,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@arlolra: See my review there.
+
+As you noted in your response, we also need a way to request more targeted updates. This includes the current wt2html updates (re-render templates or re-render images), but we should use a mechanism that can also cover more refined requests in the future: 
+
+- re-sanitization of HTML / upgrade of HTML spec
+- update of transclusions affected by certain templates only
+- update of specific images only
+
+A key in the request seems to make most sense. Perhaps something like this?
+
+```
+{
+   update: {
+      templates: true,
+      images: false,
+      spec: true
+   },
+   original: { ... }
+}
+```
+
+Not all of these need to be set all the time, only the actually requested updates could be set to a truish value. In the future, we could add an object value with finer-grained options instead to support targeted template / image updates.",1419281047,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> Do you mean html2wt or wt2html in the issue summary?
+
+wt2html
+
+> It reuses template expansions or images, depending which of the two triggered the update. The reason for the update is relayed in an x-parsoid header currently.
+
+I was thinking it only did that with the `previous` revision data but I guess it's both then
+https://gerrit.wikimedia.org/r/#/c/165685/12/api/routes.js
+
+can you review https://gerrit.wikimedia.org/r/#/c/165685/ when you get a chance?",1419274370,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#937200, @Arlolra wrote:
+> @Gwicke: In the example responses from Parsoid, you'll showing the pagebundle but the route examples say `/html/`.
+
+Do you mean html2wt or wt2html in the issue summary?
+
+>> For a no-cache request, RESTBase instead first checks whether the *current* revision is found in storage. If it is, it sends the data for that in the original key:
+> 
+> what, if anything, does Parsoid do with the `original` data.
+
+It reuses template expansions or images, depending which of the two triggered the update. The reason for the update is relayed in an x-parsoid header currently.",1419273092,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#937200, @Arlolra wrote:
+> @Gwicke: In the example responses from Parsoid, you'll showing the pagebundle but the route examples say `/html/`.
+
+Do you mean html2wt or wt2html in the issue summary?
+
+>> For a no-cache request, RESTBase instead first checks whether the *current* revision is found in storage. If it is, it sends the data for that in the original key:
+> 
+> what, if anything, does Parsoid do with the `original` data.
+
+It reuses template expansions or images, depending which of the two triggered the update. The reasion for the update is relayed in an x-parsoid header currently.",1419273071,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> what, if anything, does Parsoid do with the original data.
+
+if the original data contains the wikitext source, then parsoid won't have to fetch it. I'll assume you meant that",1419046452,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@Gwicke: In the example responses from Parsoid, you'll showing the pagebundle but the route examples say `/html/`.
+
+Also, in the cache scenario (wt2html), we try to reuse the expansions from the previous revision, as in,
+https://gerrit.wikimedia.org/r/#/c/165685/10/api/routes.js
+
+but, for no-cache,
+
+> For a no-cache request, RESTBase instead first checks whether the *current* revision is found in storage. If it is, it sends the data for that in the original key:
+
+what, if anything, does Parsoid do with the `original` data.",1419027930,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Makes sense, thanks!",1418949597,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#934492, @Jdouglas wrote: 
+> 1. What does `original` mean -- is it the penultimate revision of the content in question?  Is it the first revision of the content?  What's the context of originality?
+
+'original' means the data for the edit revision the edit was based on (if title and oldid is specified, and if we had that in restbase).
+
+> 1. Why is so much data being sent to Parsoid?  Does Parsoid need two HTML representations, plus a wikitext representation, plus a data-parsoid representation?  Or does this example show the different options for the types of source data?
+
+Parsoid does a lot of clever tricks to keep the conversion clean and make it fast. One is to diff the modified HTML against the original & using the original wikitext for portions of the DOM that weren't modified (based on offset information similar to a source map from data-parsoid). The predecessor revision is used to speed up parsing of new versions by plucking out some bits of content (template expansions, image thumbs) & reusing them without going off and generating them from scratch using the PHP API.
+
+> 1. What is the minimum request that could be sent to Parsoid through this endpoint?
+> 
+> My goal is to be able to document this API , part of which means defining the schemas for the requests and responses, so it will help me to understand exactly what's going on.
+
+We could only send the modified content, but then diffs will be dirty and the performance will suffer.",1418949428,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@gwicke Can you break down the request described above?
+
+```
+POST parsoid/v2/{domain}/{title}/wt
+
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: '<html>The modified HTML</html>'
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+
+I have several questions, most of which are probably due to my lack of knowledge about how Parsoid works.
+
+1. What does `original` mean -- is it the penultimate revision of the content in question?  Is it the first revision of the content?  What's the context of originality?
+1. Why is so much data being sent to Parsoid?  Does Parsoid need two HTML representations, plus a wikitext representation, plus a data-parsoid representation?  Or does this example show the different options for the types of source data?
+1. What is the minimum request that could be sent to Parsoid through this endpoint?
+
+My goal is to be able to document this API , part of which means defining the schemas for the requests and responses, so it will help me to understand exactly what's going on.",1418949159,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Right now these POST requests are completely ephemeral.
+
+We *could* eventually consider caching some responses based a request hash for a limited time (and return that hash in some header), so that the result could be dereferenced shortly later using just the hash. That could be handy for features like VisualEditor's speculative html2wt conversion, which is currently implemented using custom memcached logic. But that's really not needed in the first iteration IMHO.",1418947862,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@Jdouglas I think it would have to be ephemeral. You could hash the content to create an identifier but if it contained a template or whatnot, it wouldn't be clear when that needs expunging.",1418946004,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"If the optional title is omitted, does that mean the converted data is ephemeral, or would we want to generate some kind of identifier so that the content can be stored for future access?",1418945157,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Re POST requests, I think we could perhaps use the following:
+
+- html2wt without selser: `POST /v2/{domain}/wt/{title}` (title optional)
+- html2wt with selser: `POST /v2/{domain}/wt/{title}/{oldid}`
+- html2html or wt2html: `POST /v2/{domain}/html/{title}/{oldid}` (title and oldid optional)",1418944107,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#853672, @Jdouglas wrote:
+>> html2wt conversion support
+>> 
+>> Request to RESTBase: POST /v1/{domain}/transform/html/to/wt
+>>
+>> RESTBase retrieves the original html, wikitext & data-parsoid from storage & POSTs it to Parsoid:
+>>
+>> POST parsoid/v2/{domain}/{title}/wt
+> 
+> How does RESTBase determine the title of the content?
+
+@jdouglas, @arlolra: good question. Maybe flipping the order would actually make more sense for Parsoid? It would still provide a list of formats, and it does not require knowledge of the oldid.
+
+Example: `POST parsoid/v2/{domain}/wt/{title}`
+
+Alternatively, we could figure everything but the domain out by POSTing to `/v2/{domain}/`.",1418855954,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#853672, @Jdouglas wrote:
+>> html2wt conversion support
+>> 
+>> Request to RESTBase: POST /v1/{domain}/transform/html/to/wt
+>>
+>> RESTBase retrieves the original html, wikitext & data-parsoid from storage & POSTs it to Parsoid:
+>>
+>> POST parsoid/v2/{domain}/{title}/wt
+> 
+> How does RESTBase determine the title of the content?
+
+@jdouglas, @arlolra: good question. Maybe flipping the order would actually make more sense for Parsoid? It would still provide a list of formats, and it does not require knowledge of the oldid.",1418855783,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> html2wt conversion support
+> 
+> Request to RESTBase: POST /v1/{domain}/transform/html/to/wt
+>
+> RESTBase retrieves the original html, wikitext & data-parsoid from storage & POSTs it to Parsoid:
+>
+> POST parsoid/v2/{domain}/{title}/wt
+
+How does RESTBase determine the title of the content?",1418837594,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"If the title isn't provided, what do we supply in the POST to Parsoid?
+
+> POST parsoid/v2/{domain}/{title}/wt
+
+Or would there be a different URL for arbitrary html conversion in Parsoid?",1418320854,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#842132, @Jdouglas wrote:
+> In the //html2wt conversion support// section, how do we identify the article that the user wants to convert?  Should we add a //{title}// to the url?
+
+Since it's a POST anyway, we could also just ask for an optional `title` and `revision` in the post data. That way the same URL will work for random HTML (which is not associated with any particular page / revision), and for edits to existing content.",1418320408,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"In the //html2wt conversion support// section, how do we identify the article that the user wants to convert?  Should we add a //{title}// to the url?
+
+> Request to RESTBase: POST /v1/{domain}/transform/html/to/wt",1418319272,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: We could add a 'version' property which has the link to the spec version, which we can then prefix with text/html and application/json to get a complete mime type for each respective bit. On the way back we'll then need to undo that. When we re-sanitize HTML, we'll also need to update the version numbers on data-mw and data-parsoid, even if those weren't actually changed in any way. Or, alternatively, we could use the maximum version for a combined version as you propose when sending the different bits of content back to Parsoid.
+
+This is all more complexity than I'd like to have. It would really be simpler if you could just give us a complete mime type for each bit of content, the same way you would set it when asked for one of those formats only (for non-pagebundle formats). We can then set that mime type in responses to clients asking for HTML, and send it back to you later, without having to track special details about the parsoid version scheme.",1418283852,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: We could add a 'version' property which has the link to the spec version, which we can then prefix with text/html and application/json to get a complete mime type for each respective bit. On the way back we'll then need to undo that. When we re-sanitize HTML, we'll also need to update the version numbers on data-mw and data-parsoid, even if those weren't actually changed in any way. Or, alternatively, we could use the maximum version for a combined version as you propose when sending the different bits of content back to Parsoid.
+
+This is all more complexity than I'd like to have. It would really be simpler if you could just give me a complete mime type for each bit of content. I can then set that mime type in responses to clients asking for HTML, and send it back to you later, without having to track special details about the parsoid version scheme.",1418283716,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: We could add a 'version' property which has the link to the spec version, which we can then prefix with text/html and application/json for the respective bits. We'll also need to indicate the mime type in mixed content we send to parsoid, for each part. To me as a user it's actually simpler if you just give me a complete mime type for each bit of content. I can then just send that back to you later, without knowing much about custom mime type massaging etc.",1418283201,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: We could add a 'version' property which has the link to the spec version, which we can then prefix with text/html and application/json for the respective bits. We'll also need to send that in stuff we send to parsoid, for each part. To me as a user it's actually simpler if you just give me a complete mime type for each bit of content. I can then just send that back to you later, without knowing much about custom mime type massaging etc.",1418283152,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Right, we need to know the version number, but, I was just wondering if it needs to be part of every resource in the v2 page bundle, i.e. you can add a html-version property to the v2 page bundle, for example.",1418280934,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: When we load some old HTML from storage, we need to know
+
+1) whether this HTML needs to be re-sanitized after discovering that sanitization issue in the Parsoid version that emitted DOM spec 1.0.0, and
+2) whether we need to update the HTML to actually work in current clients like VE. This is both purely in RESTBase.
+
+If Parsoid is going to use (and likely update / re-sanitize) old HTML, it also needs to know which assumptions it can make based on the version. It might well elect to throw away any old HTML before version X, but without knowing the version you can't make that decision easily.
+
+So far we ducked these issues by not storing any HTML, and clearing the entire cache when we made major changes. We won't be able to do this with storage in the longer term.",1418280783,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Sorry I couldn't look at this earlier. 
+
+But, one obvious comment right away is that wikitext doesn't have a ""spec"" really and there is no real versioning as far as I know. Secondly, I don't see a real use case where Parsoid would be able to take different HTML versions (for old and modified) and then use that for serialization. Parsoid may regenerate the old HTML for the new HTML spec and/or fall back to full serialization in that scenario.
+
+I also don't see a scenario where a client (like VE, Flow, etc) is going to take an old version of HTML, edit it and generate a new version of the HTML. So, I think from the scenario of editing clients, the HTML version is going to be preserved. All version bumps in HTML are likely going to happen entirely in Parsoid land on the wt2html pipeline.
+
+So, is this more richer representation really useful? I personally prefer a simpler representation. But, I haven't thought through this fully. Perhaps something worth a discussion on IRC so I understand this better.
+
+
+
+
+",1418279281,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#833765, @Jdouglas wrote:
+> Makes sense to me.  I like the idea of including spec versions in the content types.  Is there a central repository of specs I can peruse?
+
+Not yet, but we should start building it up, even if it isn't exposed in the advertised location yet.
+
+> Would this framing structure extend to other types of content, such as binary data?
+
+Yes. We can use `'transfer-encoding': 'base64'` in the headers.",1418143691,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#833765, @Jdouglas wrote:
+> Makes sense to me.  I like the idea of including spec versions in the content types.  Is there a central repository of specs I can peruse?
+
+Not yet, but we should start building it up, even if it isn't exposed in the advertised location yet.
+
+> Would this framing structure extend to other types of content, such as binary data?
+
+Yes. We can use 'transfer-encoding': 'base64' in the headers.",1418143674,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Makes sense to me.  I like the idea of including spec versions in the content types.  Is there a central repository of specs I can peruse?
+
+Would this framing structure extend to other types of content, such as binary data?",1418143556,PHID-USER-2aknafvxpqtbnnzpvtno,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. On the way back, we should indicate to Parsoid which version of HTML, wikitext or data-parsoid we are passing it, so that Parsoid can interpret it correctly. This is especially important when editing old revisions.
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multipart/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+Similarly, the v2 wt2html API would indicate the content type of each component in its response, which restbase will then store & return to the client.
+
+@arlolra, @parsoid, @jdouglas: Does this makes sense to you?",1418078655,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. On the way back, we should indicate to Parsoid which version of HTML, wikitext or data-parsoid we are passing it, so that Parsoid can interpret it correctly. This is especially important when editing old revisions.
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multipart/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+Similarly, the v2 wt2html API would indicate the content type of each component in its response, which restbase will then store & return to the client.
+
+Does this makes sense to you?",1418078438,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. On the way back, we should indicate to Parsoid which version of HTML, wikitext or data-parsoid we are passing it, so that Parsoid can interpret it correctly. This is especially important when editing old revisions.
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multipart/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+
+Does this makes sense to you?",1418078370,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. On the way back, we should indicate to Parsoid which version of HTML, wikitext or data-parsoid we are passing it, so that Parsoid can interpret it correctly. This is especially important when editing old revisions.
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multi-part/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+
+Does this makes sense to you?",1418078321,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. 
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multi-part/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+
+Does this makes sense to you?",1418077997,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Change 165685 had a related patch set uploaded (by Arlolra):
+Add v2 serialization route
+
+[[https://gerrit.wikimedia.org/r/165685]]
+
+#patch-for-review",1417051016,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+Rename MediaWiki release tags,"In BugZilla, the MediaWiki product had milestones like ""1.1 release"", ""1.20.x release"" and ""1.25.0 release"" etc.
+
+Individual MediaWiki extensions didn't have such a milestone, but we did have shared ones for extensions like ""MW 1.18 version"", ""MW 1.14 version"".
+
+To avoid clashing with other project's release tags (see also T75899), we should rename the MediaWiki core ones to include ""MediaWiki"" or ""MW"".
+
+While at it I'd like to propose merging the ones formerly for extensions to be the same (e.g. merge ""1.24.0 release"" and ""MW 1.24 version"" into ""MediaWiki-1.24"" or something like that.",1416944367,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_description,resolved
+Rename MediaWiki release tags,"Thanks for raising these very valid and convincing points and for your patience.
+
+I have added ""MW-""prefixes. They are slightly less discoverable as I didn't want more stuff cluttering the projects dropdown when you enter ""MediaWiki"" plus as the dropdown does not support colors yet (there is some upstream ticket about this), people might think that they describe the version they are running instead of the version the bug should get fixed for.
+
+See https://phabricator.wikimedia.org/project/query/all/?after=MW for a list.
+
+Ironically that prefix we had also used for extension target milestones in Bugzilla too, so there were also disabled ""MW-1.18-version"" style projects. I have renamed those to ""MW-extension-1.18-version"" style to have less confusion in project dropdowns.
+
+All in all, it's a bit more confusing than I had naively anticipated. I am sorry for that.
+
+Closing as resolved.",1421156230,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,This issue doesn't seem resolved.,1420694018,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#960085, @Legoktm wrote:
+> I agree with Krinkle and fbstj that the projects should be MediaWiki specific. Basically, there should be one project for a MediaWiki 2.0 Release and another for a Pywikibot 2.0 Release.
+
++1",1420661455,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I agree with Krinkle and fbstj that the projects should be MediaWiki specific. Basically, there should be one project for a MediaWiki 2.0 Release and another for a Pywikibot 2.0 Release.",1420653182,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"So if I understand correctly you're recommending we consider version milestones as ""accidentally"" indexed and browsable through Phabricator as projects.
+
+Thus we'd have to disregard all features related to it (members, watchers, workboards, archiving, edit permissions, change feeds, ..).
+
+Because if you'd archive v2.0 when Project A's v2.0 is finished, that says nothing about a Project B still at v1.9 that will have a v2.0 next year. (e.g. like Firefox 30 and Chrome 30, you'd have to abandon all features related to individual projects and treat them as individual-meaningless correlation keywords instead).
+
+That seems like a big waste and compromise in overall usability of Phabricator (the link on task pages to e.g. [1.24 release](https://phabricator.wikimedia.org/tag/1.24-release/) would only be confusing for users as it'd provide a meaningless feed of unrelated projects). All only to try and gain what? Smaller number of projects overall?
+
+I'm not saying we should have separate version milestones for MediaWiki Core and MediaWiki extensions that follow the same release versioning. It makes perfect sense to share one ""MW 1.25 release"" between those (as I originally recommended which is what prompted this whole thread). Those would use additional filters in searches for e.g. ""MediaWiki"" when interested in that one project. (E.g. the Cite extension doesn't have its own release process, it just follows MediaWiki). But I'm talking about projects not directly following MediaWiki's release process. E.g. OOjs, VisualEditor, CDB, and all other projects we have.",1420647097,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"So if I understand correctly you're recommending we consider version milestones as ""accidentally"" indexed and browsable through Phabricator as projects.
+
+Thus we'd have to disregard all features related to it (members, watchers, workboards, archiving, edit permissions, change feeds, ..).
+
+Because if you'd archive v2.0 when Project A's v2.0 is finished, that says nothing about a Project B still at v1.9 that will have a v2.0 next year. (e.g. like Firefox 30 and Chrome 30, you'd have to abandon all features related to individual projects and treat them as individual-meaningless correlation keywords instead).
+
+That seems like a big waste and compromise in overall usability of Phabricator (the link on task pages to e.g. [1.24 release](https://phabricator.wikimedia.org/tag/1.24-release/) would only be confusing for users as it'd provide a meaningless feed of unrelated projects). All only to try and gain what? Smaller number of projects overall?
+
+I'm not saying we should have separate version milestones for MediaWiki Core and MediaWiki extensions that follow the same release versioning. It makes perfect same to share one ""MW 1.25 release"" between those and use ""MediaWiki"" as additional filter in searches when only interested in one project. (E.g. the Cite extension doesn't have its own release process, it just follows MediaWiki). But I'm talking about projects not directly following MediaWiki's release process. E.g. OOjs, VisualEditor, CDB, and all other projects we have.",1420646702,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I disagree as I do not see the problem of ""clashing"" once you can explicitly search for //MediaWiki core tasks only// with that generic milestone. So with the given arguments I currently don't (yet?) see a need to identify that the generic 1.25 milestone tag should specifically refer to MediaWiki releases only.
+If there are other projects forced to adopt some pattern, I'm happy to get aware of these projects and discuss why `v1.2.3-release` is better for them instead of `1.2.3-release`.",1420645688,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#959250, @Aklapper wrote:
+> I'm afraid that I don't understand the last two comments and I need a more concrete example of an existing problem. (In short: if you don't want non-MediaWiki results in your search results, don't put non-MediaWiki projects into your search criteria. [..]
+
+I'm sorry but this is rather frustrating. What don't you understand? This has got nothing to do with search results. I'll try and repeat myself one more time in verbose bullet points.
+
+* All Phabricator projects share a common global namespace. They're not like nested directories. Associating umbrellla or parent projects does not change this (it'll always be `project/1.25-release`, it doesn't nest like `project/mediawiki/1.25-release`, the umbrella is just meta-data, not part of the identifier).
+* A `1.2.3-release` pattern is too generic as it doesn't specify what project it is about and can't be adopted as Phabricator convention in general as it would clash with other projects. It assumes MediaWiki core it the only project we have. We have in fact about 100 others.
+* Other projects are already forced to adopt a different pattern. Maybe they'll use a different generic pattern (arms racing for every variation you can think of). E.g. Project A might use `v1.2.3-release` (prefix ""v""), Project B might use `Release 1.2.3` (the word ""Release""), project C might use `ProjectC-v1.2.3`. All variations that either try to fight MediaWiki's version numbers or come up with their own non-generic pattern.
+* Therefore, let's agree on a non-generic pattern to use for all projects (e.g. `ProductName-v1.2.3` seems sensible).
+* Now use that for MediaWiki as well (keeping the old names as additional-hashtag aliases for back-compat).",1420645438,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#959250, @Aklapper wrote:
+> I'm afraid that I don't understand the last two comments and I need a more concrete example of an existing problem. (In short: if you don't want non-MediaWiki results in your search results, don't put non-MediaWiki projects into your search criteria. [..]
+
+I'm sorry but this is rather frustrating. What don't you understand? This has got nothing to do with search results.I'll try and repeat myself one more time in verbose bullet points.
+
+* All Phabricator projects share a common global namespace. They're not like nested directories. Associating umbrellla or parent projects does not change this (it'll always be `project/1.25-release`, it doesn't nest like `project/mediawiki/1.25-release`, the umbrella is just meta-data, not part of the identifier).
+* A `1.2.3-release` pattern is too generic as it doesn't specify what project it is about and can't be adopted as Phabricator convention in general as it would clash with other projects. It assumes MediaWiki core it the only project we have. We have in fact about 100 others.
+* Other projects are already forced to adopt a different pattern. Maybe they'll use a different generic pattern (arms racing for every variation you can think of). E.g. Project A might use `v1.2.3-release` (prefix ""v""), Project B might use `Release 1.2.3` (the word ""Release""), project C might use `ProjectC-v1.2.3`. All variations that either try to fight MediaWiki's version numbers or come up with their own non-generic pattern.
+* Therefore, let's agree on a non-generic pattern to use for all projects (e.g. `ProductName-v1.2.3` seems sensible).
+* Now use that for MediaWiki as well (keeping the old names as additional-hashtag aliases for back-compat).",1420645417,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#959250, @Aklapper wrote:
+> I'm afraid that I don't understand the last two comments and I need a more concrete example of an existing problem. (In short: if you don't want non-MediaWiki results in your search results, don't put non-MediaWiki projects into your search criteria. There's no forcing to needless variation as any project can request creating new projects, and there's no forcing to adopt prefixes as there are no prefixes currently.)
+> 
+> I'm closing this ticket as resolved. Which still allows adding followup comments.
+
+I'm sorry but this is rather frustrating. What don't you understand? I'll try and repeat myself one more time in verbose bullet points.
+
+* All Phabricator projects share a common global namespace. They're not like nested directories. Associating umbrellla or parent projects does not change this (it'll always be `project/1.25-release`, it doesn't nest like `project/mediawiki/1.25-release`, the umbrella is just meta-data, not part of the identifier).
+* A `1.2.3-release` pattern is too generic as it doesn't specify what project it is about and can't be adopted as Phabricator convention in general as it would clash with other projects. It assumes MediaWiki core it the only project we have. We have in fact about 100 others.
+* Other projects are already forced to adopt a different pattern. Maybe they'll use a different generic pattern (arms racing for every variation you can think of). E.g. Project A might use `v1.2.3-release` (prefix ""v""), Project B might use `Release 1.2.3` (the word ""Release""), project C might use `ProjectC-v1.2.3`. All variations that either try to fight MediaWiki's version numbers or come up with their own non-generic pattern.
+* Therefore, let's agree on a non-generic pattern to use for all projects (e.g. `ProductName-v1.2.3` seems sensible).
+* Now use that for MediaWiki as well (keeping the old names as additional-hashtag aliases for back-compat).",1420645376,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"Ahh yeah, my problem can be solved by either doing `MediaWiki + version number` tags or doing `version number + not MediaWiki` tags (querying 'not in 'MediaWiki tag')
+
+EDIT: after further comments, I would still support prefixing rather than multi-tagging",1421060103,PHID-USER-tqvzwasywo4a7bnuwuz4,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"Ahh yeah, my problem can be solved by either doing `MediaWiki + version number` tags or doing `version number + not MediaWiki` tags (querying 'not in 'MediaWiki tag')",1420641663,PHID-USER-tqvzwasywo4a7bnuwuz4,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I'm afraid that I don't understand the last two comments and I need a more concrete example of an existing problem. (In short: if you don't want non-MediaWiki results in your search results, don't put non-MediaWiki projects into your search criteria. There's no forcing to needless variation as any project can request creating new projects, and there's no forcing to adopt prefixes as there are no prefixes currently.)
+
+I'm closing this ticket as resolved. Which still allows adding followup comments.",1420636340,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,But what about when there is a task/bug which involves one of these tags (targeting it for a particular release) and another piece of software/library/etc which is targeted too?,1420474319,PHID-USER-tqvzwasywo4a7bnuwuz4,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#955248, @Aklapper wrote:
+> It is not too generic once we've fixed T76942.
+
+Association or hierarchy does not equal containment. Even when Phabricator supports parent project associations (umbrellas), they're still in a shared global namespace and are bound to clash with other software projects. Forcing projects other than MediaWiki them to either adopt needless variation (e.g. v123 instead of 123-release), or adopt the same kind of prefixes I'm proposing for MediaWiki release tags.",1420474318,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,It is not too generic once we've fixed T76942.,1420473965,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#952762, @Aklapper wrote:
+> Urgh. So I wasn't aware that Phabricator doesn't support mentioning hash tags starting with a number. :(
+
+Phabricator support aside, ""1.24 release"" is too generic. Let's rename them to include ""MW"" (or ""MediaWiki"")?",1420461867,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"Urgh. So I wasn't aware that Phabricator doesn't support mentioning hash tags starting with a number. :(
+However, when is that important? I'd expect people to edit the Projects when setting a milestone, not mention those exact milestone names in a comment instead.
+
+Regarding an umbrella MediaWiki project, that's covered in T76942.
+
+I've dropped the .x and .0 suffixes from those milestone projects still active. Active projects left are:
+* 1.19-release
+* 1.23-release
+* 1.24-release
+* 1.25-release
+* In the list view: https://phabricator.wikimedia.org/project/query/all/?after=1
+
+So from my point of view we are done here.",1420223124,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,+1 to dropping the point release suffixes.,1419026463,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,I also support dropping and also prefixing with MW as there's more than just mediawiki that might require versions at some point,1419022372,PHID-USER-tqvzwasywo4a7bnuwuz4,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I'd drop the suffixes indeed. And also rename to mention ""MW"" or ""MediaWiki"" (with old name as additional hash-tag for back-compat and redirect). This to be less generic, and also because Phabricator doesn't support mentioning hash tags starting with a number.",1419021398,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,Left here: Drop the .x or .0 prefixes?,1419020839,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"<tl;dr>: We now have [[ https://phabricator.wikimedia.org/project/query/active/?after=1 | four active ""Target Milestone"" release projects ]] in Phabricator left, regarding the MW core (and to some extend MW extensions) world:
+* 1.19.x release
+* 1.23.x release
+* 1.24.0 release
+* 1.25.0 release
+
+------
+
+Way too long version for transparency (had to write this down anyway as this stuff can get confusing if I don't concentrate):
+
+I've archived the past projects #1.23.0_release , #1.22.x_release, #1.22.0_release, #1.21.x_release, #1.21.0_release, #1.20.x_release, #1.20.0_release, #1.19.0_release, #1.18.x_release, #1.18.0_release (which somehow don't get autolinked here, sigh).
+
+In the meantime, @Legoktm had archived the  #MW_1.24_version and #MW_1.23_version projects (use for extensions before) and changed their (open and closed) tasks' TM projects to the generic TM projects #1.24.0_release ( we don't have a 1.24.x_release project) and #1.23.0_release (.0, which is archived now, but there were no open tasks anyway).
+
+I archived #MW_1.22_version which was empty. In general the use of these target milestones in Bugzilla seems to have declined over the versions
+
+I batch-edited those tasks having MW_1.99_version tags set to have 1.99.x_release tags now.
+
+Then I archived #MW_1.19_version to #MW_1.21_version.",1419020731,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,Happy for us to go ahead with this.,1418402033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"If we have a decision, I volunteer with the renaming itself. For some reason blocked tasks T75994 and T78140 bother me more than they should whenever I see them in backlogs.  :)",1418377495,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I also think that one MediaWiki 1.47 target milestone is better than two. While a minority knows which one should be used where, the majority get puzzled whenever find the double 1.47.
+
+I'm for applying the single tag for a single version, and then deal with the problems retrieving the right information, i.e. by sharing a saved search somewhere public for ""All MediaWiki core tasks tagged for 1.47"".",1418217664,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#808898, @Aklapper wrote:
+>So ""MediaWiki-1.47.0-release"" and ""MediaWiki-1.47.x-release"" (literally, replace ""47"" by your favorite number though)?
+
+Whether we should have only ""MediaWiki-1.47"", or ""MediaWiki-1.47.0"" and ""MediaWiki-1.47.x"", is a separate from this task. But, personally, I think we should only have ""MediaWiki-1.47"". These tags are milestones, release targets. Not the version a bug report relates to, or whether a fix should be backported. I always found the `.x` ones strange in the milestones for MediaWiki core when we used BugZilla.",1417908876,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#793597, @Jdforrester-WMF wrote:
+>>>! In T75916#792822, @Qgil wrote:
+>>>>! In T75916#789084, @Jdforrester-WMF wrote: 
+>>> Well, the union search of ""MediaWiki"" project &&
+>> 
+>> A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+> 
+> Oh, I assumed that the MW team were going to fix this the way we have for VisualEditor, Parsoid, Multimedia… are they not?
+> 
+
+I'd really like us to tag every single MediaWiki core bug with a [MediaWiki] project. The various subprojects (-Database, -UnitTests, etc) would be generalized to not be MW-core specific.
+
+So for a MediaWiki database bug you'd tag it with [MediaWiki] and [Database].
+
+This would also allow us to do things like [CirrusSearch] [UnitTests].
+
+But really this should be its own task.",1417743542,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I'm happy with this, for one. Let's do it.",1417660839,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"> A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+
+Thanks for the better wording; that is the one single reason why I wrote ""cross-pollution"" here, as long as subprojects in https://secure.phabricator.com/T3670 aren't available...
+
+If adding (currently) 30 projects (all those previous components of MediaWiki core in Bugzilla) to a search query to get only get MediaWiki core tasks with that milestone isn't considered a huge hassle (do it once for that target milestone, save the custom query for yourself or share the search query URL on some wikipage) I'm definitely in for making the naming scheme between extensions and core for target milestones consistent.
+
+I assume we still want to distinguish ""1.47.0"" (which would cover potentially everything that was fixed in all those 1.46wmfXY versions and hence included in the 1.47.0 tarball) from ""1.47.x"" (to mark stuff that should be fixed or has been fixed in 1.27.x tarball releases //after// the initial 1.47.0 release and has required backporting from 1.48wmfXY branches or git master)?
+
+So ""MediaWiki-1.47.0-release"" and ""MediaWiki-1.47.x-release"" (literally, replace ""47"" by your favorite number though)?",1417651989,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"A venturous summary of this discussion could be:
+
+* Valid Tags for past, present, and future MediaWiki releases: #MW-1.24.x, #MW-1.24.0, #MW-1.24.1...
+* Valid Tags for past, present, and future MediaWiki weekly snapshots: WMF-deploy-2014-11-26-(1.25wmf10)...
+
+These tags are equally applicable to core, extensions, and anything else.",1417509059,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#787907, @Aklapper wrote:
+> I'm not convinced to give those MediaWiki extensions Target Milestones the same name though as that would cross-pollute when searching in all those MediaWiki-* projects we have now so I' rather go with some ""MW-1.24.x-series"" or such. 
+
+I think this is biased towards MediaWiki core. You'd need to create milestones for every extension, skin and other MediaWiki-related project that doesn't have its own release/versioning scheme. That seems like a waste. Using #MW_1.24_version (as we're already doing for extensions, one has to intersect with the relevant project) seems simple enough.
+
+For projects with lots of sub projects (e.g. things formerly having their own BugZilla product, like MediaWiki core and VisualEditor) would use an umbrella project.
+
+At the moment that involves manual double-tagging (though a triager would have queries to find untagged issues to clean up). But there's to be intent in upstream Phabricator to embrace umbrella projects as a native concept (e.g. projects being in a hierarchy where they're visible and queryable via their parents). – https://secure.phabricator.com/T3670",1417201138,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#792822, @Qgil wrote:
+>>>! In T75916#789084, @Jdforrester-WMF wrote: 
+>> Well, the union search of ""MediaWiki"" project &&
+> 
+> A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+
+Oh, I assumed that the MW team were going to fix this the way we have for VisualEditor, Parsoid, Multimedia… are they not?
+
+> What is clear is that the current cohabitation of #1.24.0-release and #mw_1.24_version is confusing. As a bug reporter or even as a casual extension developer, how am I supposed to know which one to use?
+
+I agree we should fix this by only having one.
+
+> PS: also, I wonder why #1.24.0_release or #1.24.0-release won't render a proper label.
+
+Maybe projects' hashtags can't start with a number to get auto-linked?",1417199157,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#789084, @Jdforrester-WMF wrote: 
+> Well, the union search of ""MediaWiki"" project &&
+
+A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+
+What is clear is that the current cohabitation of #1.24.0-release and #mw_1.24_version is confusing. As a bug reporter or even as a casual extension developer, how am I supposed to know which one to use?
+
+PS: also, I wonder why #1.24.0_release or #1.24.0-release won't render a proper label.
+",1417163048,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#789084, @Jdforrester-WMF wrote: 
+> Well, the union search of ""MediaWiki"" project &&
+
+A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+
+What is clear is that the current cohabitation of #1.24.0-release and #mw_1.24_version is confusing. As a bug reporter or even as a casual extension developer, how am I supposed to know which one to use?
+
+PS: also, I wonder why #1.24.0_release or #1.24.0_release won't render a proper label.
+",1417163033,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#787907, @Aklapper wrote:
+> I strongly support renaming the generic MediaWiki Target Milestones.
+> I'm not convinced to give those MediaWiki extensions Target Milestones the same name though as that would cross-pollute when searching in all those MediaWiki-* projects we have now so I' rather go with some ""MW-1.24.x-series"" or such. 
+> There is also a small (maybe neglectable?) differentiation between ""must fix in MW core for the 1.25.0 tarball release"" vs. ""should fix in this MW extension at some point in the branch corresponding to MW core 1.25.x releases"".
+
+Well, the union search of ""MediaWiki"" project && ""MediaWiki-release-1.18"" release tag won't contain any extension items (and v.v.) – is that not suitable? This is what we're doing with ""WMF-deploy-2014-11-26_(MW1.25wmf10)"".",1417031970,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"> Individual MediaWiki extensions didn't have such a milestone, but we did have shared ones for extensions like ""MW 1.18 version"", ""MW 1.14 version"".
+What was the purpose of those milestones? Where they for things that should be backported or for planning (""hope to get this done by then"")?
+
+@Aklapper: can you update the description of {T100} with the summary of what we did/planned (or point to a wiki page that describes it). That should probably be the place we work from to solve this issue.",1417026417,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I strongly support renaming the generic MediaWiki Target Milestones.
+I'm not convinced to give those MediaWiki extensions Target Milestones the same name though as that would cross-pollute when searching in all those MediaWiki-* projects we have now so I' rather go with some ""MW-1.24.x-series"" or such. 
+There is also a small (maybe neglectable?) differentiation between ""must fix in MW core for the 1.25.0 tarball release"" vs. ""should fix in this MW extension at some point in the branch corresponding to MW core 1.25.x releases"".",1417006148,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"You say ""release tags"", I CC @greg and @Jdforrester-WMF.",1416992053,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"(Starting today, I'm moving all the tasks related to new/renamed projects to #Project-Creators because the Phabricator backlog is getting really big)",1416948852,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+"Create remaining VisualEditor projects and migrate ""tracking"" tasks into the relevant projects","We're scrapping tracking bugs
+
+* All VE projects' descriptions should have ""Reminder: All VisualEditor-related tasks should be tagged with #VisualEditor as well, for tracking, triage and management purposes."" appended.
+* All projects are regular (briefcase) type.
+
+| Project | Description | Task it replaces
+| #VisualEditor-Performance | Performance issues with #VisualEditor. | T51685 |
+| #VisualEditor-CopyPaste | Copy paste issues with #VisualEditor. | T35105 |
+| #VisualEditor-InterfaceLanguage | Multi-lingual interface (i18n, l10n, RTL) issues with #VisualEditor. | N/A |
+| #VisualEditor-Links | Link editing in #VisualEditor (not #VisualEditor-MediaWiki specific). | N/A |
+| #VisualEditor-Media | Media editing in #VisualEditor (not #VisualEditor-MediaWiki specific). | N/A |
+| #VisualEditor-MediaWiki-Plugins | Performance issues with #VisualEditor. | T48803 |
+
+
+Merge into existing projects:
+
+| Tracker | Projects |
+| T68083 | #VisualEditor, #VisualEditor-ContentEditable |
+| T69690 | #VisualEditor, #VisualEditor-MediaWiki-Media |
+| T67955 | #VisualEditor, #VisualEditor-EditingTools |
+| T72372 | #VisualEditor, #VisualEditor-MediaWiki-Mobile, #Browser_Support_Google_Android |
+| T49780 | #VisualEditor, #VisualEditor-EditingTools |
+| T52781 | #VisualEditor, #VisualEditor-Initialisation |
+| T54327 | #VisualEditor, #VisualEditor-Initialisation |
+| T50789 | #VisualEditor, #VisualEditor-MediaWiki-Links |
+| T55604 | #VisualEditor, #VisualEditor-MediaWiki-Templates |
+| T53792 | #VisualEditor, #VisualEditor-ContentLanguage |
+| T35126 | #VisualEditor, #VisualEditor-ContentLanguage |
+| T35077 | #VisualEditor, #VisualEditor-ContentLanguage |
+| T41596 | #VisualEditor, #VisualEditor-Tables |
+| T39870 | #VisualEditor, #VisualEditor-MediaWiki-Media |",1416938037,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ufggm4c7s4fufhtimjv,task_description,resolved
+"Create remaining VisualEditor projects and migrate ""tracking"" tasks into the relevant projects",Now complete.,1422425192,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ufggm4c7s4fufhtimjv,task_subcomment,NA
+[Regression pre-wmf10] VisualEditor does not load on beta labs,"Errors: 
+
+""Exception thrown by papaparse"" load.php:161
+""TypeError: document.getElementById(...) is null""
+
+""Exception thrown by user callback"" load.php:161
+""TypeError: mw.log.warning is not a function""",1416929762,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-mgagqv36esykujdeqdd6,task_description,resolved
+[Regression pre-wmf10] VisualEditor does not load on beta labs,Verified in Betalabs,1416956566,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mgagqv36esykujdeqdd6,task_subcomment,NA
+[Regression pre-wmf10] VisualEditor does not load on beta labs,"Change 175862 merged by jenkins-bot:
+Disable papaparse because it breaks everything
+
+[[https://gerrit.wikimedia.org/r/175862]]",1416952927,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mgagqv36esykujdeqdd6,task_subcomment,NA
+[Regression pre-wmf10] VisualEditor does not load on beta labs,"Change 175862 had a related patch set uploaded (by Catrope):
+Disable papaparse because it breaks everything
+
+[[https://gerrit.wikimedia.org/r/175862]]
+
+#patch-for-review",1416952218,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mgagqv36esykujdeqdd6,task_subcomment,NA
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,"my bot found maiwiki at meta_p and tried to start running queries, but this fails.
+
+name value must be 'Wikipedia' but name is currently a char sequenze repeating hex E0A4B5
+```
+MariaDB [(none)]> select *, hex(name) from meta_p.wiki where dbname like 'mai%';
++---------+------+------------+-----------+--------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+--------------------------------------------------------------+
+| dbname  | lang | name       | family    | url                      | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |                                                    hex(name) | 
++---------+------+------------+-----------+--------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+--------------------------------------------------------------+
+| maiwiki | mai  | ?????????? | wikipedia | http://mai.wikipedia.org |    1 | s3.labsdb |         0 |        1 |               0 |                1 |            1 | E0A4B5E0A4BFE0A495E0A4BFE0A4AAE0A4BFE0A4A1E0A4BFE0A4AFE0A4BE |
++---------+------+------------+-----------+--------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+--------------------------------------------------------------+
+1 row in set (0.00 sec)
+```
+maiwiki.labsdb missing in /etc/hosts
+```
+$ mysql -hmaiwiki.labsdb
+ERROR 2005 (HY000): Unknown MySQL server host 'maiwiki.labsdb' (0)
+```
+",1416916519,PHID-USER-rbcxdzszrm6s4izt67kj,PHID-TASK-hc57wasluvhgws762zjc,task_description,resolved
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,The hosts files have been updated accross tools.,1416937163,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-hc57wasluvhgws762zjc,task_subcomment,NA
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,"Ok, but the dns problem still exists:
+
+```
+tools.merlbot@tools-dev:~/lists/qs$ mysql -hmaiwiki.labsdb
+ERROR 2005 (HY000): Unknown MySQL server host 'maiwiki.labsdb' (0)
+
+```",1416933249,PHID-USER-rbcxdzszrm6s4izt67kj,PHID-TASK-hc57wasluvhgws762zjc,task_subcomment,NA
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,"The data of the meta table is mostly filled by the maintain-replicas script from API queries to the actual wiki proper; what I see when I query the table manually is 'विकिपिडिया' which is, as far as I can tell, the correct name for the project in that language.  The value in hexadecimal is also correct; it /appears/ to repeat itself because those are Unicode codepoints are on a high codepoint plane and the utf8 encoding has a long prefix for every character.  Notice:
+
+E0A4**B5**E0A4**BF**E0A4**95**...
+
+In other words, this works as designed.  You may want to use 'family' if you want to test for Wikipedia-ness rather than 'name' which is meant for display to endusers.  This is true even in European languages since, for example, frwiki would have 'Wikipédia' (note the accent) in the name column.
+",1416930210,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-hc57wasluvhgws762zjc,task_subcomment,NA
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,"The data of the meta table is mostly filled by the maintain-replicas script from API queries to the actual wiki proper; what I see when I query the table manually is 'विकिपिडिया' which is, as far as I can tell, the correct name for the project in that language.  The value in hexadecimal is also correct; it /appears/ to repeat itself because those are Unicode codepoints are on a high codepoint plane and the utf8 encoding has a long prefix for every character.  Notice:
+
+E0A4**B5**E0A4**BF**E0A4**95**...
+
+In other words, this works as designed.  You may want to use 'family' if you want to test for Wikipedia-ness rather than 'name' which is meant for display to endusers.  This is true even in European languages since, for example, frwiki would have 'Wikipédia' (not the accent) in the name column.
+",1416930114,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-hc57wasluvhgws762zjc,task_subcomment,NA
+Combine imageinfo requests on load,"1. Go to http://en.wikipedia.org/wiki/Barack_Obama as a logged-in user in Chrome
+2. Open the inspector, go to the network panel, click the filter icon and select ""XHR""
+3. Click Edit beta
+4. Observe lots of POST /w/api.php requests, one for each image
+
+We should combine these requests rather than doing a separate one for each image.",1416886111,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kcbyh6alaid3ganxbdh7,task_description,resolved
+Combine imageinfo requests on load,"Change 716268 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Remove redundant initialization from LinkCache%%%
+https://gerrit.wikimedia.org/r/716268",1630656376,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"Change 716268 had a related patch set uploaded (by Thiemo Kreuz (WMDE); author: Thiemo Kreuz (WMDE)):
+%%%[mediawiki/extensions/VisualEditor@master] Remove redundant initialization from LinkCache%%%
+https://gerrit.wikimedia.org/r/716268",1630583660,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"Change 180228 merged by jenkins-bot:
+Combine imageinfo requests
+
+[[https://gerrit.wikimedia.org/r/180228]]",1422905521,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"There are two Parsoid bug/feature requests that prevent us from eliminating the API calls:
+
+1. We need the original dimensions and image type of the image. If Parsoid can give it to us in the data that will solve the issue.
+2. Right now, Parsoid hard-codes the image default size to 220, which is the enwiki size default. That, however, is not the default of all wikis (and definitely not standalone) so we have to resize the image. This requires us to get the original dimensions and file type (since many resize rules depend on whether the image is bitmap or drawing) which leads to API requests.
+
+If #1 is solved, we shouldn't need an API request on load for existing images.",1422904203,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"I don't think that batching imageinfo requests goes quite far enough. I'd like to eliminate this API request from the critical path.
+
+Let's assume that every image whose file name matches /\.svg/ is type=DRAWING type and that all other images are bitmaps. Although not guaranteed to be reliable, in practice this heuristic will almost always be correct. We should only attempt to validate our guess with an API request when the user attempts to resize the image. (This may mean that we have to scale the image back down after allowing the user to scale it up. Such cases should be exceedingly rare, however.)
+
+The original dimensions of bitmap images should ideally be part of the paction=parse response from the API. We could also include them in the MediaWiki read HTML as data-* attributes. (This approach would take 30 days to propagate fully, but I think that's OK.)",1422854751,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"Change 180228 had a related patch set uploaded (by Alex Monk):
+[WIP] Combine imageinfo requests by setting up a new class like LinkCache to request them all centrally
+
+[[https://gerrit.wikimedia.org/r/180228]]
+
+#patch-for-review",1418761684,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Open up the wikitext editor and attempt to switch to VE. It no longer works. Clicking has no effect and you remain on the wikitext editor.
+
+On Chrome and Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1416483000,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_description,resolved
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Change 176052 merged by Catrope:
+Followup 142a44e: fix path names to MobileContextItemWidget.{js,css}
+
+[[https://gerrit.wikimedia.org/r/176052]]",1417045961,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),Verified the fix in Betalabs and test2,1417042711,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Change 176052 had a related patch set uploaded (by Catrope):
+Followup 142a44e: fix path names to MobileContextItemWidget.{js,css}
+
+[[https://gerrit.wikimedia.org/r/176052]]
+
+#patch-for-review",1417034259,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Still failing in wmf9, now because our fix used MobileContextOptionWidget instead of MobileContextItemWidget",1417034244,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),Checked the fix in betalabs - switching between Editor and Edit source works.,1416521838,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),Fixed in master; backport scheduled for this evening's SWAT.,1416515441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"**gerritadmin** wrote:
+
+Change 174779 merged by jenkins-bot:
+Follow-up I7eb0d0e: ve.ui.MobileContext.css doesn't exist any more, Toto
+
+https://gerrit.wikimedia.org/r/174779",1416512973,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"**gerritadmin** wrote:
+
+Change 174779 had a related patch set uploaded by Jforrester:
+Follow-up I7eb0d0e: ve.ui.MobileContext.css doesn't exist any more, Toto
+
+https://gerrit.wikimedia.org/r/174779",1416512799,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Issue seems to be in VisualEditor
+exception 'MWException' with message 'ResourceLoaderFileModule::readStyleFile: style file not found: ""/srv/mediawiki/php-master/extensions/VisualEditor/lib/ve/src/ui/styles/ve.ui.MobileContext.css""' in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoaderFileModule.php:902
+Stack trace:
+
+See http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core.mobile%7Cext.visualEditor.mediawiki.mobile%7Cext.visualEditor.mobileViewTarget%7Cmobile.editor.ve&skin=minerva&version=20141120T011929Z&*",1416490761,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),I'm investigating this. I know what's happening but not why.,1416490395,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/AbulO05q",1416483313,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN","See e.g. https://fr.wikipedia.org/?diff=109114947
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415995140,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mi4dx3mxevunni7ssqg3,task_description,resolved
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN",Verified the fix in test2.,1416443478,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN",Verified the fix in beta.,1416009547,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN",To go out in Monday's SWAT.,1416006013,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN","Change 173363 merged by jenkins-bot:
+Restore original rowspan/colspan rather than normalizing or overwriting with NaN
+
+https://gerrit.wikimedia.org/r/173363",1416004630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN","It turned out there were two corruption problems: colspan=""02"" was normalized to colspan=""2"", and colspan=""2 garbage"" was normalized to colspan=""NaN"". The patch fixes both.",1415999232,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN","Change 173363 had a related patch set uploaded by Catrope:
+Restore original rowspan/colspan rather than normalizing or overwriting with NaN
+
+https://gerrit.wikimedia.org/r/173363",1415999100,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+VisualEditor: shortcut(Ctrl+1) for Page Title does not work on Mac,"Betalabs and test2
+
+In VE on Mac click Ctrl+1 which should insert Page Title - nothing happens. 
+
+All other shortcuts - Ctrl+0,2-7 - work.
+
+
+Ctrl+1 works in IE 11.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: Macintosh",1415837760,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-mvlq3qqfqqmazl5ytcnb,task_description,invalid
+VisualEditor: shortcut(Ctrl+1) for Page Title does not work on Mac,"So, it was actually set as one of your shortcuts as we have seen yesterday.Changing Status back to Resolved Invalid.",1416431095,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mvlq3qqfqqmazl5ytcnb,task_subcomment,NA
+VisualEditor: shortcut(Ctrl+1) for Page Title does not work on Mac," Ctrl+1 does not work in any of browsers on my Mac - Safari7, Chrome, and FF 38. 
+
+And I did not see any shortcuts assigned to Ctrl+1 in my System preferences.",1415923607,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-mvlq3qqfqqmazl5ytcnb,task_subcomment,NA
+VisualEditor: shortcut(Ctrl+1) for Page Title does not work on Mac,"Works for me in Safari 8, Chrome 38 and Firefox 33. What browser were you using?",1415879355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mvlq3qqfqqmazl5ytcnb,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","screenshot
+
+Environment- beta
+
+1> Select Insert -> Template 
+2> In the resulting add a template dialog the button is labeled ""Hide Options"".See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14839}",1415647980,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-xliej5372d5wtuol7oum,task_description,resolved
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""",Checked in production.,1416436863,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""",Verified the fix in test2,1415822579,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","Was a regression in wmf7, fix has been cherry-picked and deployed.",1415665803,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","**gerritadmin** wrote:
+
+Change 172329 merged by jenkins-bot:
+Followup a86d824: fix reference to this in foreach callback
+
+https://gerrit.wikimedia.org/r/172329",1415663196,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""",Verified the fix in betalabs.,1415657268,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","**gerritadmin** wrote:
+
+Change 172329 had a related patch set uploaded by Catrope:
+Followup a86d824: fix reference to this in foreach callback
+
+https://gerrit.wikimedia.org/r/172329",1415651859,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","**gerritadmin** wrote:
+
+Change 172320 merged by jenkins-bot:
+Followup a86d824: fix reference to this in foreach callback
+
+https://gerrit.wikimedia.org/r/172320",1415651367,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","**gerritadmin** wrote:
+
+Change 172320 had a related patch set uploaded by Catrope:
+Followup a86d824: fix stupid stupid logic inversion
+
+https://gerrit.wikimedia.org/r/172320",1415650039,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","Good finding! 
+
+It's in betalabs only. test2 and production display 'Show options' button.",1415648733,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,"If I open https://en.wikipedia.org/wiki/James_Braid_(surgeon)?veaction=edit in Chrome 38, the viewport initially jumps to the bottom of the page (the references list). If I press a cursor key, I'm back at the top. If I reload the page, the problem is not reproducible. Cannot reproduce in Firefox either.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415562720,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-vdncadf63tpumxtunpkp,task_description,resolved
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,Verified in Chrome 38.,1417047518,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,Scheduled for SWAT later today.,1415902195,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,"**gerritadmin** wrote:
+
+Change 172983 merged by jenkins-bot:
+Initialize context's $element as hidden
+
+https://gerrit.wikimedia.org/r/172983",1415901665,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,"**gerritadmin** wrote:
+
+Change 172983 had a related patch set uploaded by Esanders:
+Initialize context's $element as hidden
+
+https://gerrit.wikimedia.org/r/172983",1415885146,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,Note that I am able to reproduce the incorrect scroll position in Chrome in a private browser window.,1415656961,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,"Chrome remembers a scroll position on the page - if a a content at the bottom of the page was viewed/edited, and Back/Forward buttons then were used, loading the same page again will display the last scroll position. 
+
+So far, I could not see that anything was stored in cookies.",1415651930,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"This is due to the fix applied in https://gerrit.wikimedia.org/r/#/c/170280/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415376420,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-l2puvf36mj2rean2tzju,task_description,resolved
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,Verified in test2 and production.,1416434299,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,Also fixed in test2 now.,1415665724,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,Verified the fix in betalabs.,1415657861,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"Change 172298 merged by jenkins-bot:
+Fix craziness in template dialog focusing
+
+https://gerrit.wikimedia.org/r/172298",1415651790,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"Change 172298 had a related patch set uploaded by Jforrester:
+Fix craziness in template dialog focusing
+
+https://gerrit.wikimedia.org/r/172298",1415644160,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"Change 171997 merged by jenkins-bot:
+Fix craziness in template dialog focusing
+
+https://gerrit.wikimedia.org/r/171997",1415408098,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"Change 171997 had a related patch set uploaded by Catrope:
+Fix craziness in template dialog focusing
+
+https://gerrit.wikimedia.org/r/171997",1415407374,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"When I click on the ""Bin"" icon to delete an empty parameter from a template, the system doesn't delete it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415368440,PHID-USER-j3xqvy6nbc2vdqsijned,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_description,resolved
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,Verified in production.,1415915601,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"Confirmed, it works on itwiki (Chrome; VEctor; Win 8.1)",1415867009,PHID-USER-j3xqvy6nbc2vdqsijned,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,Verified in Betalabs and test2.,1415824909,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,Fix was backported to wmf7 and deployed.,1415666118,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"**gerritadmin** wrote:
+
+Change 172446 merged by jenkins-bot:
+Followup a054a75: don't reintroduce removed template parameters
+
+https://gerrit.wikimedia.org/r/172446",1415664001,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"**gerritadmin** wrote:
+
+Change 172446 had a related patch set uploaded by Catrope:
+Followup a054a75: don't reintroduce removed template parameters
+
+https://gerrit.wikimedia.org/r/172446",1415663907,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"**gerritadmin** wrote:
+
+Change 172317 merged by jenkins-bot:
+Followup a054a75: don't reintroduce removed template parameters
+
+https://gerrit.wikimedia.org/r/172317",1415652271,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"**gerritadmin** wrote:
+
+Change 172317 had a related patch set uploaded by Catrope:
+Followup a054a75: don't reintroduce removed template parameters
+
+https://gerrit.wikimedia.org/r/172317",1415649897,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,Did we break something when we re-wrote the template parameter fixing code last week?,1415620424,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"Can confirm in Chrome and FF. What happens is that clicking on the bin makes the field disappear in the dialog, but when you save it's still in the template, as if you hadn't changed anything.",1415386564,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"Could not confirm - tried both mentioned links - [https://it.wikipedia.org/wiki/Atletica_leggera_ai_Giochi_della_XXV_Olimpiade_-_100_metri_ostacoli] and[https://it.wikipedia.org/w/index.php?title=Utente%3ANnvu%2FSandbox1&diff=69043230&oldid=69043213] 
+ any field(empty or not) can be deleted.",1415386192,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,I got no error.,1415370569,PHID-USER-j3xqvy6nbc2vdqsijned,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"Ok, on both of those templates I was able to delete the missing fields while using Chrome on Ubuntu. 
+
+You could try opening up the javascript console in Chrome (Ctrl+Shift+J) and seeing if any errors appear when you try to use the bin button.",1415370322,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"I tried to delete the field on [https://it.wikipedia.org/wiki/Atletica_leggera_ai_Giochi_della_XXV_Olimpiade_-_100_metri_ostacoli this page] with Chrome and Firefox, but I couldn't delete any field. 
+
+In [https://it.wikipedia.org/w/index.php?title=Utente%3ANnvu%2FSandbox1&diff=69043230&oldid=69043213 this edit] I tried to delete the field ""successivo"" (which is not a required field) and I couldn't delete it.",1415369636,PHID-USER-j3xqvy6nbc2vdqsijned,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"I'm unable to duplicate this on master. I tried emptying the field and then deleting it, which worked. I also tried adding an empty field in wikitext, saving, and then opening it up in VE. I was able to delete the parameter then too. 
+
+Do you have any more details that might help us duplicate? Do you have a particular diff where this was happening?",1415369032,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"Steps to reproduce:
+
+1.Open any of the following dialog:
+Basic Reference/Citation/Reference list/Page Settings
+
+2.Start typing
+
+Observe that , the text that you are typing is appearing on CE, as the cursor is active there instead of inside the dialog
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415309880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jc73aooy3axdug4ckbsa,task_description,resolved
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Verified the fix in production,1416446266,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Verified the fix in test2,1415822390,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Verified the fix in test2,1415822383,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Fix was cherry-picked to wmf7 and deployed.,1415665846,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Verified the fix in Betalabs,1415657473,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171882 merged by jenkins-bot:
+Remove and restore selection for non-isolated dialogs
+
+https://gerrit.wikimedia.org/r/171882",1415618199,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171882 had a related patch set uploaded by Catrope:
+Remove and restore selection for non-isolated dialogs
+
+https://gerrit.wikimedia.org/r/171882",1415388759,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171852 merged by jenkins-bot:
+Remove and restore selection for non-isolated dialogs
+
+https://gerrit.wikimedia.org/r/171852",1415383198,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171852 had a related patch set uploaded by Esanders:
+Remove and restore selection for non-isolated dialogs
+
+https://gerrit.wikimedia.org/r/171852",1415381304,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"This is still happening for all other dialogs(Page Settings,References List,Citation) except Basic Reference dialog in test2",1415321190,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Going out in 16:00 SWAT.,1415315016,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171757 merged by jenkins-bot:
+Fix non-linear selection handling in ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/171757",1415314342,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171757 had a related patch set uploaded by Catrope:
+Fix non-linear selection handling in ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/171757",1415314184,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171734 merged by jenkins-bot:
+Fix non-linear selection handling in ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/171734",1415314121,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171734 had a related patch set uploaded by Catrope:
+Fix non-linear selection handling in ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/171734",1415311719,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"Dragging images to table
+
+1. In VE insert a table(do not enter anything in the table).
+2. Inser->Media-> select and insert any image outside the table.
+3. Select the inserted image and drag it to the table - make sure that the insertion indication(an underscore) is displayed outside of the table,  on the right side. 
+
+Drop the table  - the table becomes separated in two parts. The attached screenshot shows the result of several attempts of the described scenario
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14885}",1415146800,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5oa3p2m62q7vlwtaworj,task_description,resolved
+VisualEditor: Drag-and-drop an inserted image slices a table,Verified the fix in production.,1416434473,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,Confirmed in Betalabs and test2.,1415823224,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,Bug 73318 was created about drag-and-drop block images issue.,1415813377,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"(In reply to etonkovidova from comment #3)
+> Created attachment 17066 [details]
+> Dragging images to table
+> 
+> I added a screen recording  - kind of tricky to reproduce, however,
+> something can be(or should be) done about the issue?
+
+Ah, that's of block images; inline images now work fine.
+
+I'm minded to say that we won't try to fix block images here; at least, let's put that into a different bug?
+
+**Attached**: {F14887}",1415809490,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"Created attachment 17066
+Dragging images to table
+
+I added a screen recording  - kind of tricky to reproduce, however, something can be(or should be) done about the issue?
+
+**Attached**: {F14887}",1415320024,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"Change 171271 merged by jenkins-bot:
+Replace block drop logic with isAllowedChildNodeType check
+
+https://gerrit.wikimedia.org/r/171271",1415218723,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"Change 171271 had a related patch set uploaded by Esanders:
+Replace block drop logic with isAllowedChildNodeType check
+
+https://gerrit.wikimedia.org/r/171271",1415200246,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,"Steps to reproduce:
+
+1.Select a text
+2.Press command+k
+3.When the link inspector opens , place the cursor inside the textbox which already has the selected text as link target name
+
+Observed Result:
+Link suggestions are not appearing after placing the cursor inside it.
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415126640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,Verified the fix in production,1415834510,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,Verified the fix in test2,1415228177,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,Verified the fix in Betalabs,1415146695,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,"Change 171006 merged by jenkins-bot:
+Populate LookupInputWidget on mousedown too
+
+https://gerrit.wikimedia.org/r/171006",1415140368,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,"Change 171006 had a related patch set uploaded by Catrope:
+Populate LookupInputWidget on mousedown too
+
+https://gerrit.wikimedia.org/r/171006",1415129507,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox,"Steps:
+1. In Firefox, enable ""Preferences > Advanced > General > Browsing > Check my spelling as I type""
+2. On an empty line (slug), write ""occurence""
+3. Observe wiggly red line; right click and change it to ""occurrence""
+4. Observe explosion
+
+Possibly a unicorning issue?
+
+
+Working steps:
+
+1. On an empty line (slug), write ""Foo occurence"" or ""occurence bar""
+2. Observe wiggly red line; right click and change it to ""occurrence""
+3. Observe non-explosion
+
+(i.e., it works fine if there's any other content in the content node)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415058420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kyyxvxidfguxqxef3flo,task_description,resolved
+VisualEditor: Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox,"Re-checcked (Mac FF 34.0.5)
+
+- production
+- test2
+- betalbs
+
+The issue is not presented anymore.  Closing the bug as Resolved.
+
+",1423854619,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-kyyxvxidfguxqxef3flo,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox,"Cannot reproduce on https://cs.wikipedia.org/wiki/Wikipedista:AKlapper_%28WMF%29/Sandbox?veaction=edit with Firefox 35 on Fedora 21, given the steps above. 
+Only one insertion/string replacement (as expected); no output in browser console.
+
+Is this still an issue? If so, which FF version on which platform?",1423690686,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kyyxvxidfguxqxef3flo,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox,"This sounds similar to T65462 in Chrome, which has insertions, deletions, and corruptions.",1418191658,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kyyxvxidfguxqxef3flo,task_subcomment,NA
+Fix nowiki heuristics for quotes,"See https://fr.wikipedia.org/w/index.php?title=Univers_cin%C3%A9matographique_Marvel&curid=5796605&diff=108676945&oldid=108668984 for a particularly bad sequence of nowikis.
+
+We should examine this and NicoV's suggestions below and see what is realistic / feasible. But, at least a couple of back-to-back nowikis should be avoidable.
+
+NicoV says (on https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=631914857#Unnecessary_succession_of_nowiki)
+
+-----
+    There are 4 sets of nowiki tags:
+
+        The first one is a combination of an opening tag and a closing tag <nowiki>...</nowiki>.
+        The second one is a self-closing nowiki tag <nowiki/> (just after the previous set) : it's totally useless, and brings nothing except more complexity to the wikitext
+        The third one is a self-closing nowiki tag <nowiki/> (just before the next set) : same remark as above
+        The fourth one is a combination of an opening tag and a closing tag <nowiki>...</nowiki>.
+
+    My report is that 2 sets are completely useless (first and second are redundant; third and fourth are redundant).
+    Of course, there's also the problem reported many times, a long time ago, that if nowiki are added they should be added only around the part that needs them not around a whole part of a sentence, but it was not the main issue I was reporting. For this, as it already been said so many times, my preferred methods (in order):
+
+        Use {{'}} (it should be possible to configure VE on each wiki to know if there's such a template, that's what I'm doing for example in WPCleaner's configuration)
+        Use '<nowiki/>'' (nowiki between the single quote and the italic formatting)
+        Use <nowiki>'</nowiki>'' (nowiki around the single quote)
+-----
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414811340,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4tywejgljpprmmm7tbbh,task_description,resolved
+Fix nowiki heuristics for quotes,A whole bunch of fixes landed in production yesterday which should improve this situation.,1420556920,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4tywejgljpprmmm7tbbh,task_subcomment,NA
+Fix nowiki heuristics for quotes,"I may not be able to get this done quickly enough -- I have an updated version up now, which eliminates the excess nowikis in this example by consolidating all heuristics in once place, but it might require more smarts. In this new version, it will insert a <nowiki/> whenever it sees a quote-char as the preceding/next sibling or first/last child of a I/B element in the DOM. That said, because of selective serializer, this might only kick in when new quotes are needed in those positions.
+
+Still have to figure out some improvements to the heuristics .. but given the context-sensitive nature of quote-parsing where stuff at the end of line can change parse behavior earlier in the line, these might be elusive. 
+
+I am going to be travelling and so cannot get to this again before next week.",1415391133,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4tywejgljpprmmm7tbbh,task_subcomment,NA
+Fix nowiki heuristics for quotes,"**gerritadmin** wrote:
+
+Change 171154 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 72844): Fixes to quote nowiki protection in selser mode.
+
+https://gerrit.wikimedia.org/r/171154",1415145234,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4tywejgljpprmmm7tbbh,task_subcomment,NA
+Fix nowiki heuristics for quotes,"This seems to be selser-specific.
+
+This below is what selser generates:
+[subbu@earth lib] node parse --selser --html2wt --oldtextfile /tmp/quote.wt --oldhtmlfile /tmp/old.html < /tmp/new.html
+*<nowiki> MARVEL Studios et ABC prépare cinq séries '</nowiki><nowiki/>''Netflix Original''<nowiki/><nowiki>'de </nowiki>[[Film de super-héros|super-héros]] pour [[Netflix]]. La diffusion de ces séries s'étalera sur plusieurs années : ''[[Daredevil (série télévisée)|Daredevil]]'' sera la première, puis ''Jessica Jones'', ''Iron Fist'' et enfin ''Luke Cage''.
+
+This below is what the full serializer generates:
+[subbu@earth lib] node parse --html2wt < /tmp/new.html
+* MARVEL Studios et ABC prépare cinq séries '<nowiki/>''Netflix Original''<nowiki/>'de [[Film de super-héros|super-héros]] pour [[Netflix]]. La diffusion de ces séries s'étalera sur plusieurs années : ''[[Daredevil (série télévisée)|Daredevil]]'' sera la première, puis ''Jessica Jones'', ''Iron Fist'' et enfin ''Luke Cage''.",1415143333,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4tywejgljpprmmm7tbbh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,"Page settings box opacity issue
+
+found in test2 and betalabs
+
+Steps to reproduce: 
+
+1. In VE - click on Page options icon. 
+2. Select Page settings->click in the check box 'Redirect this page to'
+3. Start typing 'Something' (no quotes)
+4. At some point of typing(or after you type 'Something' and then start to delete it a letter by letter) - a drop-down list of suggestions appears partially displaying underlying options for 'Show the Table of Contents' options. Look at the attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15193}",1414790040,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,Verified in production.,1415834937,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,Verified the fix in betalabs and test2.,1415222688,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,"**gerritadmin** wrote:
+
+Change 170508 merged by jenkins-bot:
+Pass $overlay to redirectTargetInput in MWSettingsPage
+
+https://gerrit.wikimedia.org/r/170508",1415039888,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,"**gerritadmin** wrote:
+
+Change 170508 had a related patch set uploaded by Alex Monk:
+Pass $overlay to redirectTargetInput in MWSettingsPage
+
+https://gerrit.wikimedia.org/r/170508",1414817472,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_subcomment,NA
+Put table cell editing controls in the context of the cell/selection so they aren't so hard to find,"screenshot
+
+(On beta.wmflabs) I had a very hard time finding the table editing menus for Merge cell. I knew they were available, but assumed they would be part of the normal attached-to-the-table menu system.
+
+I also didn't notice the ""Content cell"" menu appear until it was pointed out to me.
+
+I think it would be more intuitive, to put those controls next to the elements I'm changing, as shown in the mockups at https://www.mediawiki.org/wiki/VisualEditor/Design/Table_editor#Version_2
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14988}",1414694280,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-iezltl5j2pc2evrnk2x6,task_description,duplicate
+Put table cell editing controls in the context of the cell/selection so they aren't so hard to find,"{F17789}
+
+{F17790}
+
+Designs for including a menu in context.",1417470106,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-iezltl5j2pc2evrnk2x6,task_subcomment,NA
+Put table cell editing controls in the context of the cell/selection so they aren't so hard to find,"Yeah, I agree. Over-riding the formatting menu is clever but entirely non-obvious, and completely breaks the VE design rule about only disabling, not changing, controls between contexts.",1414694536,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iezltl5j2pc2evrnk2x6,task_subcomment,NA
+VisualEditor: Please let me drop the cursor into the table caption if it exists. Please?,"See e.g. the table in section 0 of the link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/User:Jdforrester_(WMF)/Sandbox?veaction=edit",1414624080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hsyburiakp2zdvz34qoh,task_description,resolved
+VisualEditor: Please let me drop the cursor into the table caption if it exists. Please?,Verified in production.,1416422920,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-hsyburiakp2zdvz34qoh,task_subcomment,NA
+VisualEditor: Please let me drop the cursor into the table caption if it exists. Please?,"Verified the fix in betalabs and test2(FF, Safari, Chrome).",1415227772,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-hsyburiakp2zdvz34qoh,task_subcomment,NA
+VisualEditor: Please let me drop the cursor into the table caption if it exists. Please?,Thanks!,1415040528,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hsyburiakp2zdvz34qoh,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"1. Open VE on a page that contains a focusable node
+2. Click out of the surface so it's blurred and the toolbar tools are greyed out (selection is a ve.dm.NullSelection)
+3. Try to select a focusable node by clicking on it
+4. Nothing happens
+5. Click to drop the cursor in some normal text
+6. Repeat #3, observe that it works now
+
+This also causes bug 72719: double-clicking focusable nodes fires their double-click handler and opens the associated dialog, but the selection is still null, so the dialogs don't open with the right context.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1414623540,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2iqe4d6ln6247lyafirs,task_description,resolved
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,Verified the fix in test2 and production (en.wiki),1415062309,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 170370 merged by jenkins-bot:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/170370",1414792644,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 170371 merged by jenkins-bot:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/170371",1414792639,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 170371 had a related patch set uploaded by Catrope:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/170371",1414780008,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 170370 had a related patch set uploaded by Catrope:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/170370",1414779989,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,Verified the fix in Betalabs,1414703162,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 169966 merged by jenkins-bot:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/169966",1414660282,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 169966 had a related patch set uploaded by Catrope:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/169966",1414627126,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"Screenshot
+
+There is an extra space appearing at the top of the toolbar inside VE
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14781}",1414608180,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_description,resolved
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,Verified the fix in production,1415835121,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,Verified the fix in Betalabs and test2,1414702821,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"**gerritadmin** wrote:
+
+Change 169861 merged by jenkins-bot:
+Hide page status indicators even if they aren't :visible
+
+https://gerrit.wikimedia.org/r/169861",1414623733,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"**gerritadmin** wrote:
+
+Change 169860 merged by jenkins-bot:
+Hide page status indicators even if they aren't :visible
+
+https://gerrit.wikimedia.org/r/169860",1414616343,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"**gerritadmin** wrote:
+
+Change 169861 had a related patch set uploaded by Jforrester:
+Hide page status indicators even if they aren't :visible
+
+https://gerrit.wikimedia.org/r/169861",1414616050,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"**gerritadmin** wrote:
+
+Change 169860 had a related patch set uploaded by Bartosz Dziewoński:
+Hide page status indicators even if they aren't :visible
+
+https://gerrit.wikimedia.org/r/169860",1414615976,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"(In reply to Bartosz Dziewoński from comment #2)
+> Butbutbut wasn't that supposed to be fixed with c81ed82f?
+
+Apparently it didn't work.",1414609009,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,Butbutbut wasn't that supposed to be fixed with c81ed82f?,1414608754,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"This is because of the mw-indicators div. It's empty if there are no indicators, but the fact that it floats right and the VE toolbar then has clear: both; seems to make it take up space somehow.
+
+Even if an empty indicators div doesn't take up space: if there are indicators, where do we put them in VE mode?",1414608616,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+"VisualEditor: Deleting from a paragraph-terminating node to a paragraph-terminating node (?) is throwing ""Unbalanced set of replace operations found""","Reproduce:
+
+1. go to https://fi.wikipedia.org/wiki/User:Stryn/VE?veaction=edit
+2. highlight all texts from the end of ""This is just a test.[1]"" to end of ""Visuaalinen muokkain.[2]"" and press backspace button or delete or whatever and nothing happens - VE just gets stuck.
+3. you can't save the page nor switch to wikitext editor even if you have made changes to the page.
+
+If you highlight text from ""This is just a test.[1]"" to ""This is not."" it's working as it should. So probably the problem is with the references.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72640",1414442040,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-pgkoq2ygryfod5gjbheg,task_description,resolved
+"VisualEditor: Deleting from a paragraph-terminating node to a paragraph-terminating node (?) is throwing ""Unbalanced set of replace operations found""","Confirmed in test2 and on https://fi.wikipedia.org/wiki/User:Stryn/VE?veaction=edit.
+
+On the page https://fi.wikipedia.org...  - there are many Uncaught Error: ve.dm.Document.getBranchNodeFromOffset(): offset 39 is out of bounds etc.
+
+
+In test2: type four lines of text on four separate lines.
+
+- Add reference to the end of the first line
+- add another reference to the end of the second line
+- leave the third line as it is
+- re-use the first reference and add it to the end of the fourth line
+
+
+Start highlighting the text and try to delete it with 'Delete' button. 
+FF displays: 
+Error: Unbalanced set of replace operations found load.php:316
+TypeError: currentNode.children[(nao.offset - 1)] is undefined load.php:479
+Error: Unbalanced input passed to document.
+
+After several attempts of highlighting and deleting - the page becomes unresponsive - I can place cursor but cannot move it with arrow or Enter buttons; cannot Save, cannot switch to Read mode(TypeError: data[i] is undefined).",1415056388,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-pgkoq2ygryfod5gjbheg,task_subcomment,NA
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,"screenshot of the console error
+
+Environment- test2,production,beta
+
+1>In a blank page, open the link inspector,type in some text in the link input box and keep the inspector open.
+2> While the inspector is open ,click on to add a bullet/numbered list.
+3> JS  console error “Uncaught Error: offset -1 out of bounds” and the inspector remains open.See screenshot.
+
+Clicking on Done or Remove does not close the inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72494
+
+**Attached**: {F15103}",1414419600,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_description,resolved
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,Verified in production.,1416423181,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_subcomment,NA
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,Verified the fix in betalbs and test2.,1415232212,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_subcomment,NA
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,"Change 170855 merged by jenkins-bot:
+Protect against offset=-1 in insertContent()
+
+https://gerrit.wikimedia.org/r/170855",1415129377,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_subcomment,NA
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,"Change 170855 had a related patch set uploaded by Catrope:
+Protect against offset=-1 in insertContent()
+
+https://gerrit.wikimedia.org/r/170855",1415055527,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"I don't seem to be able to trigger the warning with anything on any production wiki today.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414156020,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_description,resolved
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Verified in production, betalabs, and test2.",1415381886,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168620 merged by jenkins-bot:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168620",1414449072,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168619 merged by jenkins-bot:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168619",1414449036,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168620 had a related patch set uploaded by Catrope:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168620",1414171681,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168608 merged by jenkins-bot:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168608",1414171667,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168619 had a related patch set uploaded by Catrope:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168619",1414171662,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168608 had a related patch set uploaded by Alex Monk:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168608",1414167506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor:  Opening a very large complex transclusion sometimes hangs in Firefox,"Firefox with the wrong box
+
+Steps to reproduce:
+
+1.  Open [[William Shakespeare]] in VisualEditor. 
+
+2.  Scroll to the ==References== section and select the contents (a complex transclusion).
+
+3.  Try to open it so you can edit it.
+
+
+This hangs in Firefox 32 with this error message:
+
+Warning:  Unresponsive script
+
+A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.
+
+Script: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141016T200718Z:89
+
+
+It opens correctly (but slowly) in Chrome and Safari, and sometimes in Firefox, too.  When it fails to open correctly, then it displays the contents in the wrong dialog box (see attachment).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15370}",1414016880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zsenbwls7ebypri26j7n,task_description,duplicate
+VisualEditor:  Opening a very large complex transclusion sometimes hangs in Firefox,Is this the same problem as {T71799}?,1426445245,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zsenbwls7ebypri26j7n,task_subcomment,NA
+Actually run MediaWiki-VisualEditor's tests for MWHeadingNode / MWPreformattedNode,"Right now we have a hack in ve.test.utils.js that reregisters the core versions of HeadingNode and PreformattedNode to ensure MWHeadingNode and MWPreformattedNode aren't used, because using them would break the VE core tests when run in VE-MW.
+
+This is horrible, because it makes us unable to test specific behavior in the MW nodes. For instance, https://gerrit.wikimedia.org/r/#/c/162310/3 fails its own tests because those tests use HeadingNode rather than MWHeadingNode, even though the tests in question were clearly designed to use MWHeadingNode.
+
+We should come up with a way that MW nodes can be not registered for code tests, but be registered for MW tests.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414016460,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qmfoshrg3djlltdfiuev,task_description,resolved
+Actually run MediaWiki-VisualEditor's tests for MWHeadingNode / MWPreformattedNode,"Change 191036 merged by jenkins-bot:
+Add tests for MW node variants (heading/table/pre)
+
+[[https://gerrit.wikimedia.org/r/191036]]",1424199001,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qmfoshrg3djlltdfiuev,task_subcomment,NA
+Actually run MediaWiki-VisualEditor's tests for MWHeadingNode / MWPreformattedNode,"Change 191036 had a related patch set uploaded (by Esanders):
+Add tests for MW node variants (heading/table/pre)
+
+[[https://gerrit.wikimedia.org/r/191036]]
+
+#patch-for-review",1424178367,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qmfoshrg3djlltdfiuev,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"IE11 test2 and betalabs
+
+Steps to reproduce: 
+
+1. Open VE-> try to insert a link(via a shortcut or by clicking on the option) - the box(class=""oo-ui-window-isolated oo-ui-ltr"" ) shows up and disappears momentarily.
+
+2. Editing links - presents the same problem 
+
+Debugger complains about load.php ""Unable to get property 'from' of undefined or null reference' rangeSelection is undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1414014960,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-frawcbm336hvwpzabjlz,task_description,resolved
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"The previous comment was filed as a separate bug: 73154
+
+Besides bug 73154 - the fix re-verified in betalbs/test2/en wiki.",1415390965,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"IE11: Using a shortcut Ctrl+K to insert a link consistently gives the following message twice :
+
+DOM7009: Unable to decode image at URL: 'data:image/gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA'.  File: gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA",1415310607,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"Verified in test2 and production(en.wikipedia.org)
+
+- inserting a link with a menu option - OK
+- editing an existing link wiht a menu option - OK
+- insert a link with the shortcut - Ctrl+K - the link inspector opens and closes momentarily",1414514256,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169228 merged by jenkins-bot:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169228",1414446820,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169228 had a related patch set uploaded by Catrope:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169228",1414446705,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169224 merged by jenkins-bot:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169224",1414446221,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169221 merged by jenkins-bot:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169221",1414446134,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169224 had a related patch set uploaded by Jforrester:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169224",1414446057,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169221 had a related patch set uploaded by Catrope:
+Make link inspector not close itself in IE. Again.
+
+https://gerrit.wikimedia.org/r/169221",1414444852,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"Affecting IE10 as well, as per fi.wp report.",1414409027,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Select any template
+4.Click on ""Show Options""
+
+
+Observed Result:
+There is no advanced option showing up on the left panel.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15057}",1413838440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_description,resolved
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content",Verified the fix in production,1414614075,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content",Verified the fix in test2,1414102963,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content",Verified the fix in Betalabs,1414000340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content","**gerritadmin** wrote:
+
+Change 167973 merged by jenkins-bot:
+GridLayout: Set dimensions.visibility = '' again if we have a height and a width
+
+https://gerrit.wikimedia.org/r/167973",1413933451,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content","**gerritadmin** wrote:
+
+Change 167973 had a related patch set uploaded by Alex Monk:
+GridLayout: Set dimensions.visibility = '' again if we have a height and a width
+
+https://gerrit.wikimedia.org/r/167973",1413931019,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content",Caused by Gerrit change 166191,1413930885,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Steps to reproduce:
+
+1.  Open a page and go to Page options > Categories.
+
+2.  (Add a category if none exist.)  Edit a category to add a sort key.
+
+3.  Save page.
+
+4.  Check diff:  no sort key was added.  :-(  
+
+
+Confirmed in Firefox 32 and Safari 6.2 on Macs and Windows, so it's probably happening everywhere.
+
+This doesn't seem to be bug 48555.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413506580,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_description,resolved
+VisualEditor: [Regression] Adding category sort keys no longer working,Verified the fix in production,1414627937,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Verified in betalabs, test2, and wikimedia - e.g. a Category gets added as [[Category:Cat2|Sort_added]]",1414432683,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Change 167876 merged by jenkins-bot:
+CategoryPopupWidget: Track popup hiding again so sortkey changes are applied
+
+https://gerrit.wikimedia.org/r/167876",1413936802,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Change 167877 merged by jenkins-bot:
+PopupWidget: Remove references to 'show' and 'hide' events
+
+https://gerrit.wikimedia.org/r/167877",1413933624,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Change 167877 had a related patch set uploaded by Alex Monk:
+PopupWidget: Remove references to 'show' and 'hide' events
+
+https://gerrit.wikimedia.org/r/167877",1413919349,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Change 167876 had a related patch set uploaded by Alex Monk:
+CategoryPopupWidget: Track popup hiding again so sortkey changes are applied
+
+https://gerrit.wikimedia.org/r/167876",1413919252,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Steps to reproduce:
+
+1.  Open a page in Firefox (my version is 32).
+
+2.  Select some text.
+
+3.  Press Ctrl-X or Command-X.
+
+4.  Notice that nothing happened.
+
+
+Paste (Ctrl-V) might be working intermittently, but you have to copy rather than cut the text to do that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1413504300,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_description,resolved
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Re-verified in Chrome, FF, IE11, and Safari - cut/copy/paste look fine.",1415321607,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"(In reply to etonkovidova from comment #8)
+> Safari(1.25wmf6 (295d963) - when text is pasted, the page scrolls up
+> momentarily. Otherwise, cut/paste seems to be working correctly in
+> Safari(wmf6).
+> 
+> FF and Chrome do not display this ""scroll-up"" behavior
+
+This is bug 71728.",1415052959,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Safari(1.25wmf6 (295d963) - when text is pasted, the page scrolls up momentarily. Otherwise, cut/paste seems to be working correctly in Safari(wmf6).
+
+FF and Chrome do not display this ""scroll-up"" behavior",1415048669,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"In case this needs to be re-opened in the futre:  
+
+I can't cut text in Safari today.  I'm going to assume that this is fixed in the next release, because it happens at en.wp but not at Beta Labs or MediaWiki.org  Consequently, this Firefox-specific bug might not actually be Firefox-specific.",1414176075,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Safari does not handle Paste smoothly - when some text is pasted, the page swiftly(but noticeably) scrolls to the top and back to the place when the text is pasted.",1414104409,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,Confirmed - the issue is fixed in test2 (wmf5).,1414103937,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,Confirmed the fix(es) on Betalabs.,1413925382,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"(In reply to Ed Sanders from comment #2)
+> Fixed after various copy/paste related patches
+> https://gerrit.wikimedia.org/r/#/q/status:merged+project:VisualEditor/
+> VisualEditor+branch:master+topic:copy-fix,n,z
+> 
+> Works on beta labs, but apparently hasn't been deployed yet. Wasn't this
+> supposed to be backported?
+
+Backports due on Monday morning.",1413654656,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Fixed after various copy/paste related patches https://gerrit.wikimedia.org/r/#/q/status:merged+project:VisualEditor/VisualEditor+branch:master+topic:copy-fix,n,z
+
+Works on beta labs, but apparently hasn't been deployed yet. Wasn't this supposed to be backported?",1413654562,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"This is a serious issue. I actually managed to get the program to start deleting whole sections of text with this bug.
+
+Steps to reproduce: 
+1. Select some text
+2. Ctrl-x
+3. Ctrl-v at a different location. The cursor should (shouldn't, but it does) go to the top of the page, above everything else.
+4. Right-click at a different location and click ""paste"". Should (n't) have pasted the text at the top of the page.
+6. Select this stray text, right click, and press delete (use the mouse, not keyboard).
+7. Watch the article get randomly deleted in completely unpredictable ways.
+
+I tried this on multiple articles and got wacky behaviour both times. Browser: Firefox 33.0.",1413639663,PHID-USER-uku6gl4xeqbtbrcbr5ig,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: Selection starting on a tooled item (e.g. link) always shows the context menu,"Start a selection inside a link and drag to outside it. The context menu never disappears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413494100,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xkj5bkkwqzmcktj6whgq,task_description,resolved
+VisualEditor: Selection starting on a tooled item (e.g. link) always shows the context menu,"**gerritadmin** wrote:
+
+Change 167217 merged by jenkins-bot:
+Fix contextChange events from annotations
+
+https://gerrit.wikimedia.org/r/167217",1413573845,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xkj5bkkwqzmcktj6whgq,task_subcomment,NA
+VisualEditor: Selection starting on a tooled item (e.g. link) always shows the context menu,"**gerritadmin** wrote:
+
+Change 167217 had a related patch set uploaded by Jforrester:
+Fix contextChange events from annotations
+
+https://gerrit.wikimedia.org/r/167217",1413562026,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xkj5bkkwqzmcktj6whgq,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open Cite>Book or Cite>Journal
+3.Place the cursor inside the Title field
+
+Observed Result:
+
+A weird red border is surrounding the textfield instead of light blue highlight
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15258}",1413408120,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ue6vedmhhpltifawbjjw,task_description,resolved
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,Verified the fix in production,1414613579,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,Verified the fix in test2,1414103222,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,Verified the fix in Betalabs,1413833974,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"**gerritadmin** wrote:
+
+Change 167334 merged by jenkins-bot:
+Only validate required template params after blur
+
+https://gerrit.wikimedia.org/r/167334",1413587953,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"**gerritadmin** wrote:
+
+Change 167334 had a related patch set uploaded by Jforrester:
+Only validate required template params after blur
+
+https://gerrit.wikimedia.org/r/167334",1413585703,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"**gerritadmin** wrote:
+
+Change 167226 merged by jenkins-bot:
+Only validate required template params after blur
+
+https://gerrit.wikimedia.org/r/167226",1413581302,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"**gerritadmin** wrote:
+
+Change 167226 had a related patch set uploaded by Alex Monk:
+Only validate required template params after blur
+
+https://gerrit.wikimedia.org/r/167226",1413564956,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"Looks like a regression from the ""highlight invalid text inputs"" change.",1413408288,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a bullet or numbered list
+3.Keep on adding indentation to the list to create slugs
+4.Place your cursor inside the slug to add an item to the list
+Observed Result:
+It throws error in the console:TypeError: Cannot read property 'getSelection' of null
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15252}",1413406020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6suiiraatmj5yc6h6pe5,task_description,resolved
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""",Verified the fix in production,1414101312,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""",Verified the fix in test2,1413504112,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""",Verified the fix in Betalabs,1413423273,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""","**gerritadmin** wrote:
+
+Change 166884 merged by jenkins-bot:
+Followup 2432cbf: add recursion guard to updateSlug
+
+https://gerrit.wikimedia.org/r/166884",1413410379,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""","**gerritadmin** wrote:
+
+Change 166884 had a related patch set uploaded by Catrope:
+Followup 2432cbf: add recursion guard to updateSlug
+
+https://gerrit.wikimedia.org/r/166884",1413408204,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""","Rephrasing the bug its not only for slugs created from the list but rather a generic issue for all kind of slugs.It happens if you place your cursor in a slug and then place your cursor anywhere in the page which follows the slug.
+If you place your cursor somehwere above the slug , you wont get the error.",1413406392,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Current pipeline uses the global wmfgrunt slave-script:
+* [/bin/wmfgrunt](https://github.com/wikimedia/integration-jenkins/blob/0b85d48e60/bin/wmfgrunt)
+* [/tools/Gruntfile.js](https://github.com/wikimedia/integration-jenkins/blob/0b85d48e60/tools/Gruntfile.js)
+
+Fetch integration-jenkins.git to test it. As dependencies are pre-compiled and committed to git for Ubuntu Precise, on other platforms, first `cd ./tools; rm -rf node_modules` and `npm install` to provide for your system's architecture.
+
+It's invoked from this macro: https://github.com/wikimedia/integration-config/blob/0b85d48e60/jjb/macro.yaml#L344
+
+
+For many reasons, we should migrate from grunt-contrib-qunit to Karma, and use Chromium and/or Firefox as browser instead of PhantomJS:
+* Performance. Chromium is faster.
+* Accuracy.  PhantomJS is not a browser we support. Its layout and JavaScript engine and version thereof are irrelevant. It's based on a port from an old Safari build. Aside from being old it's also customised and under various abstraction layers. Ideally we'd run in multiple browsers, but even one would be a great start. PhantomJS does support nice features most browsers can't or wont implement, but those are not features we need to run unit tests. We want a real browser.
+* Ability. While testing fallback behaviour is important, many new browser features are unavailable in PhantomJS. This is actively making it impossible to run tests against modern code such as from OOjs UI and VisualEditor that don't support Safari 4 or 5.
+
+https://github.com/karma-runner/karma
+https://github.com/karma-runner/karma-chrome-launcher
+https://github.com/karma-runner/karma-qunit
+https://github.com/karma-runner/grunt-karma
+
+This is already being used by OOjs, OOjs UI and VisualEditor standalone. This task is about migrating the pipeline for projects that rely on running in a MediaWiki context. This brings many complexities due to registering and loading of scripts. As well as migrating the bootstrapping code to support Ubuntu Trusty and labs instances (as opposed to prod slavs running Precise).",1413326580,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_description,resolved
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Sorry for the noise, but after all the nagging I also wanted to thank for this great improvement. I can now easily run the QUnit tests headlessly without having to clone `integration/jenkins`, it supports two browsers we actually support, and it's so fast: Down from 33 seconds to 18 seconds in Chromium and 23 seconds in Firefox. Awesome!",1427112789,PHID-USER-m2zne2efu3rgmre73nl7,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"More issues I had when running `grunt karma:main` locally:
+
+* I had to pass `MW_SERVER` and `MW_SCRIPT_PATH` (which makes sense), but it's a) not documented anywhere and b) the error message is not helpful at all.
+* In `karma-qunit` (`lib/adapter.js`), `QUnit.load` and `QUnit.start` are executed (which is fine), and they try to set `QUnit.config.autostart` to `false`, but that doesn't work somehow in my setup. Instead, `QUnit.config.autostart` is `undefined` right before `QUnit.load` is called, and thus QUnit fails on trying to `start()` twice. I had to patch it locally to set `autostart` to `false` directly before calling `load`.",1427112177,PHID-USER-m2zne2efu3rgmre73nl7,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"The reported number of tests ran differs widely between running QUnit manually in the browser and running it via Karma. For example, [some recent mediawiki-core-qunit run](https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/38693/console) reports `Executed 259 of 259`, while [this run from last Thursday](https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/38575/console) said `1576 assertions passed`. I suppose `karma-qunit` counts tests, while `Special:JavaScriptTest/qunit` counts assertions? Even if that is the explanation, it should be mentioned somewhere.",1427111764,PHID-USER-m2zne2efu3rgmre73nl7,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198293 merged by jenkins-bot:
+mwext-{name}-qunit: To hhvm/karma/chromium from zend/php53/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198293]]",1426893093,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198293 had a related patch set uploaded (by Krinkle):
+mwext-{name}-qunit: To hhvm/karma/chromium from zend/php53/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198293]]
+",1426892796,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198257 merged by jenkins-bot:
+mwext-VisualEditor-qunit: To trusty/karma/chromium from precise/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198257]]",1426876782,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198257 had a related patch set uploaded (by Krinkle):
+mwext-VisualEditor-qunit: To trusty/karma/chromium from precise/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198257]]
+",1426873737,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198210 merged by jenkins-bot:
+mediawiki-core-qunit: To trusty/hhvm/mysql/chrome from precise/zend/sqlite/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198210]]",1426871791,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198210 had a related patch set uploaded (by Krinkle):
+Update mwcore-qunit to trusty/hhvm/mysql/chrome from precise/zend/sqlite/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198210]]
+",1426849570,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 186934 merged by jenkins-bot:
+Add qunit-karma macro and various *-qunit-karma jobs
+
+[[https://gerrit.wikimedia.org/r/186934]]",1422598807,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 187638 merged by jenkins-bot:
+mediawiki-core-qunit: Migrate to simplified mw-set-env-qunit.sh
+
+[[https://gerrit.wikimedia.org/r/187638]]",1422591931,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"First passing build using local Karma and Chromium!
+https://integration.wikimedia.org/ci/job/mediawiki-core-qunit-karma/5/console",1422583906,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 186934 had a related patch set uploaded (by Krinkle):
+[WIP] Add qunit-karma macro and mediawiki-core-qunit-karma job
+
+[[https://gerrit.wikimedia.org/r/186934]]
+
+#patch-for-review",1422583844,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 187638 had a related patch set uploaded (by Krinkle):
+mediawiki-core-qunit: Migrate to simplified mw-set-env-qunit.sh
+
+[[https://gerrit.wikimedia.org/r/187638]]
+
+#patch-for-review",1422583792,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 173512 merged by coren:
+contint: Add tmpfs mount in jenkins-deploy homedir for labs slaves
+
+[[https://gerrit.wikimedia.org/r/173512]]",1420558950,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 178551 merged by jenkins-bot:
+SpecialJavaScriptTest: Add export feature
+
+[[https://gerrit.wikimedia.org/r/178551]]",1420481309,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 178551 had a related patch set uploaded (by Krinkle):
+SpecialJavaScriptTest: Add export feature
+
+[[https://gerrit.wikimedia.org/r/178551]]
+
+#patch-for-review",1420480792,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),,1418757151,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),,1418757143,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 173529 merged by jenkins-bot:
+Migrate mediawiki/qunit jobs from production slaves to labs
+
+[[https://gerrit.wikimedia.org/r/173529]]",1417375509,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),">>! In T74063#787333, @Krinkle wrote:
+> Blocked on https://gerrit.wikimedia.org/r/#/c/175949/ which removes the test that was leaking jQuery animations.
+
+This has been merged.
+
+>>! In T74063#765974, gerritadmin wrote:
+> 
+> Change [173529](https://gerrit.wikimedia.org/r/173529) in `integration/config` by Krinkle:
+>> Migrate mediawiki/qunit jobs from production slaves to labs
+>>
+>> Change-Id: I69c4d6db114e2960c76ac01c4b255b7fb7bf8962
+
+This change has been deployed to Jenkins. The QUnit jobs now install MediaWiki on a labs slave and also run PhantomJS there.",1417375446,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),Blocked on https://gerrit.wikimedia.org/r/#/c/175949/ which removes the test that was leaking jQuery animations.,1416982781,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 173529 had a related patch set uploaded by Krinkle:
+Migrate mediawiki/qunit jobs from production slaves to labs
+
+https://gerrit.wikimedia.org/r/173529",1416072839,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Tested a few in labs, and are now running fine. The compared runs in labs are an N+1 run since the first one involve zuul-cloner cloning mediawiki-core.
+
+--
+
+on gallium in 1m18s:
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/12309/
+
+on integration-slave1003 in 1m34s:
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/12365/
+
+--
+
+on gallium in 1m23s:
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/12362/
+
+on integration-slave1003 in 1m31s:
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/12366/
+
+--
+
+on gallium in 29s:
+https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/32092/
+
+on integration-slave1003 in 32s:
+https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/32094/",1416072792,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"The sqlite installer auto-detects presence of a tmpfs mount in $HOME via mw-set-env:
+
+ https://github.com/wikimedia/integration-jenkins/blob/8abc7b6/bin/mw-set-env.sh#L19
+
+I've mounted tmpfs drive in the $HOME of jenkins-deploy on the integration slaves
+
+ https://gerrit.wikimedia.org/r/173511
+ https://gerrit.wikimedia.org/r/173512",1416068611,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 173512 had a related patch set uploaded by Krinkle:
+[WIP] contint: Add tmpfs mount in jenkins-deploy homedir for labs slaves
+
+https://gerrit.wikimedia.org/r/173512",1416060464,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"I've copied one of the qunit2 jobs to a static directory on integration-slave1008 and proxied it through ssh to my local Chrome to use Dev Tools to investigate the QUnit failures.
+
+They are indeed timing out, on load.php requests. Some of which are taking over 12 seconds (the QUnit timeout for an individual test is 10 seconds, defined in our testrunner.js in mediawiki-core:/tests/qunit/data).
+
+The main slowdown is the database layer. Increasing the timeout to 30 seconds made it work, but we don't want our tests to be that slow. I'll first try to match production speed more, and we could resort to increasing the timeout otherwise.
+
+Will add a tmpfs to the integration slaves and make Jenkins use that when appropriate.",1416057491,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Step 1: Move qunit from prod/precise to labs/trusty.
+Step 1a: Refactor puppet for localhost/qunit and apply to labs.
+Step 1b: Refactor puppet for mediawiki testing and apply to labs (sqlite, php5-cli, imagemagic, etc.)
+Step 2: Change integration/jenkins:bin/wmfgrunt to use Karma instead of Grunt-contrib-qunit/grunt-lib-phantomjs
+
+localhost/qunit:
+* https://gerrit.wikimedia.org/r/#/c/170792/
+* https://gerrit.wikimedia.org/r/#/c/168630/
+* https://gerrit.wikimedia.org/r/#/c/168631/
+
+Looks like the qunit test doesn't pass in labs. Some seeminly-random API calls are failing.
+
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit2/6/console",1415204108,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 168631 had a related patch set uploaded by Krinkle:
+[WIP] contint: Apply contint::qunit_localhost to labs slaves
+
+https://gerrit.wikimedia.org/r/168631",1415203966,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add some categories
+3.Try to open the context menu for it
+
+Observed Result:
+Observe that the context menu is appearing far towards left side of the dialog box and it is not closing when you navigate to other options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15142}",1413318120,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cq5xz34jat667ipldw3m,task_description,resolved
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,*** Bug 71999 has been marked as a duplicate of this bug. ***,1413817416,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,Verified the fix in production,1413504648,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,Verified the fix in Betalabs and test2,1413392117,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166709 merged by jenkins-bot:
+Put category popups in the inner overlay for now
+
+https://gerrit.wikimedia.org/r/166709",1413334092,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,SWATting in the morning.,1413333864,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166709 had a related patch set uploaded by Jforrester:
+Put category popups in the inner overlay for now
+
+https://gerrit.wikimedia.org/r/166709",1413333760,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166701 merged by jenkins-bot:
+Put category popups in the inner overlay for now
+
+https://gerrit.wikimedia.org/r/166701",1413332269,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166701 had a related patch set uploaded by Catrope:
+Put category popups in the inner overlay for now
+
+https://gerrit.wikimedia.org/r/166701",1413331489,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166279 had a related patch set uploaded by Catrope:
+Correctly place CategoryPopupWidget in LTR and RTL
+
+https://gerrit.wikimedia.org/r/166279",1413318325,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+"VisualEditor:  New and changed citations display with blank lines before and after the citation in <references />, if using citation templates","Steps to reproduce:
+
+1.  Open a page containing the <references /> block (so you can see what happens as you change citations).
+
+2.  Create a new citation or edit an existing one, using a citation template (e.g., Cite web) in the Cite menu.
+
+3.  See a blank line displayed before and after the citation.  
+
+This can be reproduced in Safari 6.2 and Firefox 32 on Mac OS 10.8.5.  It happens with Marielle's script for Citoid and with manually completed citation templates. cannot be reproduced by adding text to the Basic citation dialog (although it can be reproduced by using the Cite menu within the Basic citation dialog).
+
+This is a display-only problem.  When the page is saved, everything is normal (e.g., https://en.wikipedia.org/w/index.php?diff=629488479&oldid=629487984).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1413234900,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-hhyxloh7waxmrcuezybh,task_description,resolved
+"VisualEditor:  New and changed citations display with blank lines before and after the citation in <references />, if using citation templates",I can't reproduce this (any more?).,1414013635,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hhyxloh7waxmrcuezybh,task_subcomment,NA
+"VisualEditor:  New and changed citations display with blank lines before and after the citation in <references />, if using citation templates",Is this caused by our recent changes to how references are evaluated?,1413915263,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hhyxloh7waxmrcuezybh,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"Reported at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Irrelevant_tags , quoting below:
+
+> Why would [this edit](http://en.wikipedia.org/w/index.php?title=M.R._Organisation_Limited&curid=44080416&diff=629153289&oldid=629153016) get tagged with copyright violation template removed and speedy deletion template removed if the edit did not remove the templates? Is this a bug in the tags system? The user used HHVM and VisualEditor, is this relevant? 109.79.177.119 09:43, 11 October 2014 (UTC)
+
+(The page in question has unfortunately been deleted since, but the data is still there, just hidden.)
+
+I did some quick investigating:
+
+* If you review the page history a bit (which I managed to do before
+  it was deleted), the two templates were indeed removed at a point
+  (and that was correctly tagged) and then restored, with the next
+  edit being tagged incorrectly.
+* You can examine the logic that led to that edit being tagged at
+  [[Special:AbuseFilter/examine/log/10945503]] – if you look at the
+  row described as ""Unified diff of changes made by edit"", you can see
+  that AbuseFilter really thinks these tags were removed in that edit
+  (although they were not).
+
+--------------------------
+**URL**: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29/Archive_131#Irrelevant_tags
+**See Also**:
+* {T74329}",1413023760,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_description,resolved
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"This bug has been fixed and the fix will be deployed to Wikimedia wikis this week, with MediaWiki version 1.27.0-wmf.21, per https://www.mediawiki.org/wiki/MediaWiki_1.27/Roadmap.",1460198078,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"Change 282100 merged by jenkins-bot:
+Avoid crippled APIEditBeforeSave hook, use new features of EditFilterMergedContent instead
+
+[[https://gerrit.wikimedia.org/r/282100]]",1460165183,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,This proved easier to fix than I expected thanks to @tstarling's wonderful work in 09a5febb7b024c0b6585141bb05cba13a642f3eb.,1460010075,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"Change 282100 had a related patch set uploaded (by Bartosz Dziewoński):
+Avoid crippled APIEditBeforeSave hook, use new features of EditFilterMergedContent instead
+
+[[https://gerrit.wikimedia.org/r/282100]]
+",1460009891,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,I suppose no one else is going to work on this.,1459974657,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"> Any chance of a fix?
+
+Any contributed patches are welcome to speed up progress here. 
+See https://www.mediawiki.org/wiki/Developer_access and https://www.mediawiki.org/wiki/Gerrit/Tutorial for more information.",1454939914,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,https://en.wikipedia.org/wiki/WP:Village_pump_%28technical%29?oldid=694005525#Edit_filter_problem,1449409097,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,This came up on the English Wikipedia again this week. Any chance of a fix? It seems like a pretty big issue that we are sometimes tagging and disallowing entirely the wrong edits.,1449066003,PHID-USER-ksxcfwf6vvnfvopbps4h,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"@He7d3r Hunm, well. At least the cause of this bug was identified, but the solutin does not seem to be simple...",1440343817,PHID-USER-fhga6fel7wefoxau7gvo,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"As far as I can see, they are the same thing;",1440341623,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"@He7d3r This bug is the cause of the problem related in  T100530, right?",1440340212,PHID-USER-fhga6fel7wefoxau7gvo,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"From the duplicated bug:
+
+>On
+>https://pt.wikipedia.org/wiki/Special:AbuseLog?wpSearchUser=189.5.174.202&wpSearchFilter=1&wpSearchTitle=Lygia+Moura+Rassi&uselang=en
+>we have two logs:
+>>* 13:39, 27 May 2015: 189.5.174.202 (Talk | block) triggered filter 1, performing the action ""edit"" on Lygia Moura Rassi. >Actions taken: Tag; Filter description: Remoção de proposta de eliminação (details | examine | diff)
+>>* 13:39, 27 May 2015: 189.5.174.202 (Talk | block) triggered filter 1, performing the action ""edit"" on Lygia Moura Rassi. Actions taken: Warn; Filter description: Remoção de proposta de eliminação (details | examine)
+>
+>For some reason AbuseFilter is using the same wikitext for both attempts to save the page. This is wrong! In fact, after the user received the warning, he fixed the issue and submitted the edit again, but the filter was triggered a second time, as if the user used the same wikitext twice. 
+>
+>Originally reported on
+>https://pt.wikipedia.org/wiki/WP:Filtro_de_edi%C3%A7%C3%B5es/1#Falsos_positivos",1440339986,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"I have found the cause: The problem is that edits through API (that is the difference, @Catrope [re your comment](https://phabricator.wikimedia.org/T99000#1283126)) pass through the AbuseFilter //twice//: The first time, via the `onAPIEditBeforeSave` hook, the second time via the `onEditFilterMergedContent` hook. Only the second hooks gets the post-merged content.
+
+And, because AbuseFilter makes sure it processes every edit only once, it sets `editAlreadyFiltered` in `filterEdit` and on every subsequent hook call for the same edit it just returns without further processing. It means AbuseFilter sees and processes the pre-merged content in `onAPIEditBeforeSave`, and ignores the post-merged content in `onEditFilterMergedContent`.
+
+You could check this by adding `unset($context->getTitle()->editAlreadyFiltered);` at the end of `onAPIEditBeforeSave` – the filter will run correctly the second time and see the postmerged content, however, the edit will be noted twice in the abuse log, so this is (obviously) not a correct solution.
+
+I’d think the correct solution would be to make a variant of `APIEditBeforeSave` hook which would include the post-merged text and AbuseFilter would then switch to that new hook. Maybe. (Or, some voodoo with making sure `APIEditBeforeSave` is read-only, immutable test-this-edit, saving nothing into the abuse log, and //not// setting the `editAlreadyFiltered` flag. But that could be a bit brittle, I guess.)",1431699235,PHID-USER-7clmfrlb7fwuko4jdjbs,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"@Oriodrim: Yep, I guessed the same in the linked dupe, AbuseFilter seems to see the pre-automerged version of edits from VisualEditor.",1431548624,PHID-USER-7clmfrlb7fwuko4jdjbs,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,readding VisualEditor: was removed without explanation and the correlation seems obvious.,1431548574,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"I found how to reproduce this bug, at least in some cases. If you edit a page with VisualEditor and an automatic merge happens when you submit (i.e. someone submits a change between the moment you click ""edit"" and the moment you press ""submit""), then AbuseFilter sees the revision before the merge.
+",1417074693,PHID-USER-5h57zgttfaaarfvo4g6s,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,added VE Project as it's mentioned here and for all edits in merged T76063,1417033481,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"Here is another example on Portuguese Wikipedia:
+https://pt.wikipedia.org/wiki/Special:AbuseFilter/examine/log/1898713?uselang=en
+https://pt.wikipedia.org/w/index.php?diff=40613438&uselang=en
+The string ""{{ESR2|"" is in ""removed_lines"" but not in ""added_lines"". However, it should not be in the ""removed_lines"", because it is still in the new revision:
+https://pt.wikipedia.org/w/index.php?title=Zats_Boy&action=edit&oldid=40613438
+
+This was reported on
+https://pt.wikipedia.org/wiki/WP:CP?oldid=40613984#Falso_positivo_na_etiqueta",1416009035,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,(Adding 'hhvm' keyword just in case it's related to that.),1413030041,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,Also: https://en.wikipedia.org/wiki/Special:AbuseLog?wpSearchUser=&wpSearchFilter=224&wpSearchTitle=M.R.+Organisation+Limited,1413023915,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link icon is missing in from the toolbar,"Screenshot
+
+Link inspector icon in the toolbar seems to be missing in 
+https://en.m.wikipedia.org/
+
+However, it is appearing in test2 and Betalabs.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14753}",1412900640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iykzkw3bnfenwugca5ap,task_description,resolved
+VisualEditor Mobile: [Regression] Link icon is missing in from the toolbar,"Argh, yes, this was fixed in wmf3 I believe.",1413917906,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iykzkw3bnfenwugca5ap,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link icon is missing in from the toolbar,Which browser? Link icon appears to be showing for me...,1413916039,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-iykzkw3bnfenwugca5ap,task_subcomment,NA
+VisualEditor: Bring back the edit summary byte counter in the save dialog,"It's ve-ui-mwSaveDialog-editSummary-count in MWSaveDialog, but there are several issues with it:
+
+* It should be stored in a variable, not searched for using jQuery .find() every time
+* It should be modified with methods on OO.ui.LabelWidget, not jQuery .text()
+* It should actually be visible
+
+I don't know why it's being hidden, but display: none; is set on it, so maybe .hide() is called somewhere?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412800080,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5xquomxdtu6ifmyxtnyo,task_description,resolved
+VisualEditor: Bring back the edit summary byte counter in the save dialog,"**gerritadmin** wrote:
+
+Change 165871 merged by jenkins-bot:
+Bringing back the edit summary byte counter in the save dialog
+
+https://gerrit.wikimedia.org/r/165871",1412890189,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5xquomxdtu6ifmyxtnyo,task_subcomment,NA
+VisualEditor: Bring back the edit summary byte counter in the save dialog,"**gerritadmin** wrote:
+
+Change 165871 had a related patch set uploaded by SuchetaG:
+Bringing back the edit summary byte counter in the save dialog
+
+https://gerrit.wikimedia.org/r/165871",1412888072,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5xquomxdtu6ifmyxtnyo,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a new image
+3.Open the media settings dialog again
+4.Click on ""Choose a different image"" button
+5.Select a different image
+6.Click on ""Apply Changes"" button
+
+Observed Result:
+
+User gets stuck inside Media Settings dialog.Cannot close the dialog anymore
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15264}",1412798520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ywep5k7o4fxifohcgdas,task_description,resolved
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,Verified the fix in production,1413502689,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ywep5k7o4fxifohcgdas,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,Verified the fix in test2,1412895852,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ywep5k7o4fxifohcgdas,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,Verified the fix in Betalabs,1412805547,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ywep5k7o4fxifohcgdas,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,Fall-out from selection rewrite; fixed by Roan.,1412799699,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ywep5k7o4fxifohcgdas,task_subcomment,NA
+"VisualEditor: [Regression wmf3] For every Math expression, it is not appearing on CE when its gets evaluated for the first time","Screenshot
+
+Steps to reproduce:
+
+1.Open a new page with VE
+2.Go to Insert>Formula
+3.Insert ""\pi""
+
+Observe that, nothing appears on CE. But if you save the page or review your changes , you will see it actually got added in the page .
+
+If you reopen the page after saving, and try again adding the same math expression it will appear immediately.
+
+But if you try adding a different math expression or modify the existing math function , say for example: make ""\pi"" to ""\sqrt\pi"", it wont render on CE again. 
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71852
+
+**Attached**: {F15254}",1412797500,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-upmf46g433ncdqqvf7jl,task_description,resolved
+"VisualEditor: [Regression wmf3] For every Math expression, it is not appearing on CE when its gets evaluated for the first time","Verified the fix in Betalabs, test2 and en.wiki",1413836720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-upmf46g433ncdqqvf7jl,task_subcomment,NA
+"VisualEditor: [Regression wmf3] For every Math expression, it is not appearing on CE when its gets evaluated for the first time",Now appears to work in production. Success.,1413836449,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upmf46g433ncdqqvf7jl,task_subcomment,NA
+"VisualEditor: [Regression wmf3] For every Math expression, it is not appearing on CE when its gets evaluated for the first time",Probably the same cause as bug 71852.,1413820239,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upmf46g433ncdqqvf7jl,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,"demonstration from office-wiki
+
+When typing at the end of a line of an item in a bulleted list some character are duplicated or appear on the wrong line, delete/backspace behaves erratically.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+//attachment VE character insertion.m4v ignored as private//",1412796180,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_description,resolved
+VisualEditor: Extra characters being inserted when typing in bulleted lists,"This is the exact bug that https://gerrit.wikimedia.org/r/#/c/164514/ was designed to fix; Rachel F showed me the exact same thing the day before I wrote it. I don't think it ever got cherry-picked, but it should be on mediawiki.org some time later today as part of wmf3. We may need to cherry-pick it to wmf2.",1412844289,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,"yes just reproduced on mediawiki.org too on this page:https://www.mediawiki.org/wiki/User:RYasmeen_(WMF)?veaction=edit
+
+However, it does not happen in any other test wikis",1412814383,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,I didn't test on multiple platforms but I'm on Chrome 38.0.2125.101 beta / OS X 10.9,1412811711,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,I certainly didn't get a warm feeling while it was happening.,1412811665,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,This sounds bad.,1412811094,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert Cite>Website/News/Journal etc
+
+Observed Result:
+All citation notes are getting added as basic reference, opening them opens the basic reference dialog instead of the citation dialog.
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412795940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_description,resolved
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,Verified the fix in production,1413502870,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,Verified the fix in test2,1412895717,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,Verified the fix in Betalabs,1412805709,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,(Core pull-through not yet merged but otherwise fixed.),1412799291,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Change 165593 merged by jenkins-bot:
+Followup b8d8a5b: pass selections, not ranges, to SurfaceFragment#clone
+
+https://gerrit.wikimedia.org/r/165593",1412798773,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Change 165592 merged by jenkins-bot:
+Followup b8d8a5b: pass selections, not ranges, to SurfaceFragment#clone
+
+https://gerrit.wikimedia.org/r/165592",1412798655,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Change 165593 had a related patch set uploaded by Catrope:
+Followup b8d8a5b: pass selections, not ranges, to SurfaceFragment#clone
+
+https://gerrit.wikimedia.org/r/165593",1412798229,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Change 165592 had a related patch set uploaded by Catrope:
+Followup b8d8a5b: pass selections, not ranges, to SurfaceFragment#clone
+
+https://gerrit.wikimedia.org/r/165592",1412798180,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"This is happening because the references inserted by the citation dialog are empty, they don't have a template in them like they should.",1412796753,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Created attachment 16719
+Screenshot
+
+**Attached**: {F15243}",1412796632,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,"But not only when typing fast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412793540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4o73zjiapudkgirgztfc,task_description,resolved
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,Verified the fix in production,1413503004,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,Verified the fix for double-typing issue in test2,1412895685,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,The issue of double-typing of characters is resolved but the cursor is still appearing on readmode after saving the page.,1412805823,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,"Change 165537 merged by jenkins-bot:
+Followup b8d8a5b: fix stray check for !selection
+
+https://gerrit.wikimedia.org/r/165537",1412795872,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,"Change 165537 had a related patch set uploaded by Catrope:
+Followup b8d8a5b: fix stray check for !selection
+
+https://gerrit.wikimedia.org/r/165537",1412795302,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,"Also, after saving a page or discarding an edit, the cursor appears on the Read Mode which could be a related issue, if not will file a separate bug later.",1412793830,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","While trying to login to betalabs i get ""404 file Not Found Error"" after clicking the Log In button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412783520,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-vi6faapr4iunjpanknxn,task_description,resolved
+"""404 file Not Found Error"" when logging into betalabs","Another example of why beta shouldn't have a diverged apache config from production.
+
+Docroot paths fixed in https://gerrit.wikimedia.org/r/165649
+
+Puppet force run on deployment-mediawiki0[1-3], apache and hhvm restarted.
+
+WFM now :)",1412807704,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs",http://login.wikimedia.beta.wmflabs.org/ is entirely down.  Normally there is a whole wiki there (albeit one normally used only for login).,1412804669,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","Raising priority (and changed summary) since most Flow browser tests are failing.
+
+Login through the API may be working.",1412804545,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","I can confirm comment 3, same outcome here, simply because http://login.wikimedia.beta.wmflabs.org/wiki/Special:CentralLogin/start does not exist.
+
+This feels unrelated to VE, hence correcting product/component.",1412800930,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","(In reply to Ritu Swain from comment #2)
+> > Also, URLs to reproduce the problem are welcome.
+
+I followed this link http://en.wikipedia.beta.wmflabs.org/wiki/User:Swainr?veaction=edit
+
+and clicked on Log in.After entering id and password in the page when I click on log in button it takes me to this page
+http://login.wikimedia.beta.wmflabs.org/wiki/Special:CentralLogin/
+> start?token=bbdd420df13bbf427dba8b3a38d6f947 .",1412797839,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","> Also, URLs to reproduce the problem are welcome.
+http://login.wikimedia.beta.wmflabs.org/wiki/Special:CentralLogin/start?token=bbdd420df13bbf427dba8b3a38d6f947",1412795851,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","How is that problem related to VisualEditor (which you set as a product here)? 
+I don't see VisualEditor mentioned in your steps to reproduce?
+Also, URLs to reproduce the problem are welcome.",1412793242,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,"1. Open https://www.mediawiki.org/wiki/QA/Selenium_Workshop in latest stable Chrome.
+2. Click ""Edit""
+3. Put cursor in the first paragraph, insert a single character.
+
+Expected:
+
+Save button enables, allowing the user to save the page.
+
+Actual:
+
+Save button stays disable, user is unable to save the edit.
+
+No exceptions or warnings on the dev console.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412655300,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-c62cwehj54km2p5gebox,task_description,resolved
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,This appears to now be fixed in wmf3.,1413819814,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,Only happens on first click.,1412697829,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,Works for me in latest Chrome,1412697476,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,"This works fine if the first cursor position is in the Header, or before the first character of the paragraph. Very complex behaviour…",1412697301,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,Could this be fixed by https://gerrit.wikimedia.org/r/164514 ?,1412667718,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,"It seems the model is consistently one character behind. When I worked-round the bug in comment #0 by backspacing over my new character and typing it again, and then changing another word on the page, clicking Save page and reviewing my change showed only the first word change in the wikitext diff.",1412655396,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,"See https://office.wikimedia.org/w/index.php?diff=118847&oldid=118846
+
+Steps to reproduce:
+
+1.  Start with a paragraph that says ""Foo '''bar''' baz blah blah"".
+
+2.  Cut paragraph.
+
+3.  Paste paragraph elsewhere.
+
+4.  Notice that it now says """"Foo '''bar'''baz blah blah"" (i.e., minus one space immediately after the word in bold-face formatting).
+
+This also happened with <mark> formatting.
+
+This edit was made in Safari 6 on Mac OS 10.8.5.  I was not immediately able to reproduce this in Firefox 32.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412625180,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-fielr75hawu6al7yvwgb,task_description,resolved
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,Verified the fix in betalabs and test2.,1416264850,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,"Change 173256 merged by jenkins-bot:
+Safari copy-paste fix
+
+https://gerrit.wikimedia.org/r/173256",1416256303,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,"Change 173256 had a related patch set uploaded by Esanders:
+Safari copy-paste fix
+
+https://gerrit.wikimedia.org/r/173256",1416231976,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,*** Bug 73333 has been marked as a duplicate of this bug. ***,1415898350,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,*** Bug 72901 has been marked as a duplicate of this bug. ***,1415063629,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"* Insert a reference (Cite > Basic)
+* Insert an MWLink node (Ctrl + K > http://www.amazon.com)
+
+Observe magic zero-width node. Converting to an annotation makes it work fine.
+
+Same happens in media caption dialogs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412470080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_description,resolved
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"Change 167335 merged by jenkins-bot:
+Apply mw-body-content styles to SurfaceWidget
+
+https://gerrit.wikimedia.org/r/167335",1413587949,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"Change 167335 had a related patch set uploaded by Jforrester:
+Apply mw-body-content styles to SurfaceWidget
+
+https://gerrit.wikimedia.org/r/167335",1413586492,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,Verified the fix on test2.,1413577145,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"Change 166918 merged by jenkins-bot:
+Apply mw-body-content styles to SurfaceWidget
+
+https://gerrit.wikimedia.org/r/166918",1413420147,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"Change 166918 had a related patch set uploaded by Trevor Parscal:
+Apply mw-body-content styles to SurfaceWidget
+
+https://gerrit.wikimedia.org/r/166918",1413417420,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"This is because the CSS for these link nodes (and pretty much everything else from Parsoid CSS) is scoped to .mw-body-content, a class that we set on the main ce.Surface but not on surfaces inside of dialogs.
+
+I tried applying mw-body-content to the surface in the dialog, and that does cause the link node to appear, but it also messes up the font size. Someone with a better understanding of our various layers of font size manipulation (coughtrevorcough) should look at this.",1412495721,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: The comment icon is repeatedly selected and deselected with the keyboard,"When selecting text with the keyboard (Shift-arrow), starting the selection range in adjacency to a comment icon repeatedly selects and deselects the icon. Starting the selection not in adjacency to the icon works as expected.
+
+If this is hard to understand, see this page:
+https://en.wikipedia.org/wiki/User:Amire80/comment
+
+It has detailed instructions to reproduce.
+
+This is broken in both LTR and RTL. RTL test page:
+https://he.wikipedia.org/wiki/%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%D7%AA:Amire80/ve-comment-selection
+
+Thanks to David Chan for helping with minimizing the test case :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/User:Amire80/comment",1412249460,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-bonyuszkfft3v3iimug2,task_description,resolved
+VisualEditor: The comment icon is repeatedly selected and deselected with the keyboard,This should have been resolved with the switch to native cursoring that goes out in wmf17. Please say if not.,1423676254,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bonyuszkfft3v3iimug2,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page","Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden appears while trying to save a page in Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1412186460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fv2akybq3ywgtzliagz5,task_description,resolved
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page",Verified the fix in production,1412888804,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page",Verified the fix in test2,1412292717,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page",Verified the fix in Betalabs,1412202398,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page","**gerritadmin** wrote:
+
+Change 164122 merged by jenkins-bot:
+Fix syntax error in mittoHidden selector
+
+https://gerrit.wikimedia.org/r/164122",1412197138,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page","**gerritadmin** wrote:
+
+Change 164122 had a related patch set uploaded by Catrope:
+Fix syntax error in mittoHidden selector
+
+https://gerrit.wikimedia.org/r/164122",1412186692,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","Environment- test2
+
+1> In VE, open Basic citation dialog and enter any citation(book,news,Web or Journal). For ex- enter a book citation.
+2> Now while the citation is still highlighted select Insert  -> Template.Notice the Add a Template window does not open , instead it opens the Cite Book dialog.
+
+But if you enter a book citation in the CE and while it is still highlighted try to open the Template dialog(Insert  -> Template) . Notice the Add a Template dialog opens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412006940,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ttqllxkghaqgjfflgrdp,task_description,resolved
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","Thank you once again :), will keep that in mind.",1412100712,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to Ritu Swain from comment #7)
+> (In reply to James Forrester from comment #6)
+> > (In reply to Ritu Swain from comment #5)
+> > > I checked with a clear history.It still does not open the ""Add a Template""
+> > > dialog ,when a  book citation is highlighted in Basic reference dialog.
+> > > 
+> > > Instead it opens the Cite Book dialog.
+> > 
+> > Oh, right, you weren't talking about the other bug in this report. Yes,
+> > opening any of the dialogs when you've selected that item (selecting a
+> > template and clicking the template button; an image and the media button; a
+> > reference and the reference button) will always open the item for editing
+> > rather than insert a new one, by design. Sorry for the confusion.
+> 
+> Thank you, i got it now. 
+> 
+> But when i try the above steps in the Content Editor or the Editor in the
+> Media Settings Caption.
+> 
+> For ex- 
+> 1> click on cite -> book and insert a book citation.
+> 2> Now while the citation is still highlighted select Insert  ->
+> Template.Notice the Add a Template modal opens , and not the Cite Book
+> dialog.
+> 
+> If this is how it is supposed to behave in different editors, then please
+> ignore this issue.
+
+It is. When you insert ""Cite > Book"" in the editor, it inserts a citation – a reference with a template inside it. When you try this inside a reference, it cleverly inserts the template, not a reference inside a reference (which isn't allowed). It's a little confusing, clearly. :-(",1412099011,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to James Forrester from comment #6)
+> (In reply to Ritu Swain from comment #5)
+> > I checked with a clear history.It still does not open the ""Add a Template""
+> > dialog ,when a  book citation is highlighted in Basic reference dialog.
+> > 
+> > Instead it opens the Cite Book dialog.
+> 
+> Oh, right, you weren't talking about the other bug in this report. Yes,
+> opening any of the dialogs when you've selected that item (selecting a
+> template and clicking the template button; an image and the media button; a
+> reference and the reference button) will always open the item for editing
+> rather than insert a new one, by design. Sorry for the confusion.
+
+Thank you, i got it now. 
+
+But when i try the above steps in the Content Editor or the Editor in the Media Settings Caption.
+
+For ex- 
+1> click on cite -> book and insert a book citation.
+2> Now while the citation is still highlighted select Insert  -> Template.Notice the Add a Template modal opens , and not the Cite Book dialog.
+
+If this is how it is supposed to behave in different editors, then please ignore this issue.",1412097130,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to Ritu Swain from comment #5)
+> I checked with a clear history.It still does not open the ""Add a Template""
+> dialog ,when a  book citation is highlighted in Basic reference dialog.
+> 
+> Instead it opens the Cite Book dialog.
+
+Oh, right, you weren't talking about the other bug in this report. Yes, opening any of the dialogs when you've selected that item (selecting a template and clicking the template button; an image and the media button; a reference and the reference button) will always open the item for editing rather than insert a new one, by design. Sorry for the confusion.",1412096168,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to James Forrester from comment #4)
+>
+> 
+> 
+
+I checked with a clear history.It still does not open the ""Add a Template"" dialog ,when a  book citation is highlighted in Basic reference dialog.
+
+Instead it opens the Cite Book dialog.",1412096017,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","I can't; have you refreshed?
+
+The citation template now opens as expected.",1412095049,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to James Forrester from comment #2)
+> I believe this has now been fixed and backported as part of the fix for bug
+> 71418.
+
+I can still reproduce it, in both test2 and beta.",1412089237,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference",I believe this has now been fixed and backported as part of the fix for bug 71418.,1412040334,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference",http://youtu.be/sy91ReXk_f4,1412007273,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"1. Open VisualEditor
+2. Find or create a paragraph with a link followed by some non-linked text
+3. Inspect the link
+4. While the link inspector is open, click to drop the cursor in the non-linked text
+
+The link inspector does not close, and instead moves to follow your selection.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71151",1411770300,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_description,resolved
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,Verified the fix in test2 and production,1412367524,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,Merged into master and deployed to wmf1.,1412090473,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"Change 163852 merged by jenkins-bot:
+Followup b149390: fix dm.Surface's concept of ""selectedNode"" to match SurfaceFragment's
+
+https://gerrit.wikimedia.org/r/163852",1412086657,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"Change 163852 had a related patch set uploaded by Jforrester:
+Followup b149390: fix dm.Surface's concept of ""selectedNode"" to match SurfaceFragment's
+
+https://gerrit.wikimedia.org/r/163852",1412086525,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"Change 163783 merged by jenkins-bot:
+Followup b149390: fix dm.Surface's concept of ""selectedNode"" to match SurfaceFragment's
+
+https://gerrit.wikimedia.org/r/163783",1412084885,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"Change 163783 had a related patch set uploaded by Catrope:
+Followup b149390: fix dm.Surface's concept of ""selectedNode"" to match SurfaceFragment's
+
+https://gerrit.wikimedia.org/r/163783",1412037373,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"(In reply to Bartosz Dziewoński from comment #2)
+> Related? Bug 71151.
+
+Yes, absolutely. While investigating this, I wished I had ""git bisect concerning"" in addition to ""good"" and ""bad"". At first, nothing was wrong, then the flicker started happening, and now it doesn't close at all.
+
+I think this happened because Ed changed the context to reposition itself directly from events emitted by the surface. The surface also emits a contextChange event that causes the context to realize that it should close (or did; this bug is about that event not being emitted any more), but that event listener is debounced, so we close the context after moving it.",1411779222,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,Related? Bug 71151.,1411779053,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"This broke in https://gerrit.wikimedia.org/r/#/c/162495/ , which made it so contextChange is no longer emitted when the selection moves from inside a link to outside a link.",1411771797,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order","See https://office.wikimedia.org/w/index.php?diff=118520&oldid=118519
+
+This was all supposed to be on one line, essentially changing ===One=== to ===One and two===  It displays almost correctly, the equivalent of:
+
+===One and two===
+a
+
+but saves completely wrong:
+
+===One===
+ndtwoa
+
+
+James F has a screenshot in e-mail.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411756740,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qwganlrulofurpdkcbyf,task_description,resolved
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order",This is almost certainly a duplicate of the bug that was fixed by https://gerrit.wikimedia.org/r/#/c/164514/,1415656063,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qwganlrulofurpdkcbyf,task_subcomment,NA
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order",Checked Safari/Chrome - cannot reproduce.,1415655941,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-qwganlrulofurpdkcbyf,task_subcomment,NA
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order",Looks like the issue we had in Safari selections that Ed fixed a couple of weeks ago?,1415046514,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qwganlrulofurpdkcbyf,task_subcomment,NA
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order",Can't reproduce this issue...,1414802772,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qwganlrulofurpdkcbyf,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"We have isValid() functions for similar inputs, but not this one, so it's possible to try to create a redirect to ""|"" (which Parsoid turns into MediaWiki:Badtitle).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411586340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-62x4lmlf5c4o37ouorno,task_description,resolved
+VisualEditor: TitleInputWidget should validate inputs,"(In reply to etonkovidova from comment #8)
+> test2 has the same validation that is in betalabs: 
+> 
+> - cannot add Talk: as a template - 'Add template' is disabled
+> - cannot add a template or a  category with |(a pipe), < and > chars
+> - if 'Page settings' redirection has aforementioned  symbols -
+> MediaWiki:Badtitletext is displayed.  Does it need some improvement?
+
+That sounds like it covers all our needs.",1415229764,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"test2 has the same validation that is in betalabs: 
+
+- cannot add Talk: as a template - 'Add template' is disabled
+- cannot add a template or a  category with |(a pipe), < and > chars
+- if 'Page settings' redirection has aforementioned  symbols - MediaWiki:Badtitletext is displayed.  Does it need some improvement?",1415229722,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"Change 169623 merged by jenkins-bot:
+Introducing isValid() in MWTitileInputWidget
+
+https://gerrit.wikimedia.org/r/169623",1414606526,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"Change 169623 had a related patch set uploaded by SuchetaG:
+Introducing isValid() in MWTitileInputWidget
+
+https://gerrit.wikimedia.org/r/169623",1414539689,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,This is scarily close to what I filed bug 72468 about. While filing it I was thinking that an isValid() implementation should also be provided. I'll add that to that bug.,1414115463,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"(In reply to James Forrester from comment #3)
+> (In reply to Alex Monk from comment #1)
+> > Currently the redirect section of the page settings dialog and the template
+> > placeholder page use MWTitleInputWidget.
+> > 
+> > The template placeholder page can be fixed with a simple change from value
+> > === '' to !mw.Title.newFromText( value ) in
+> > MWTemplatePlaceholderPage#onTemplateInputChange. It will no longer allow you
+> > to add a template with an invalid name. No need for isValid here.
+> 
+> What happens when you use a parser function or a magic word?
+
+I imagine it would break. So let's not do that.
+
+> > As for the redirect settings, that seems more difficult. I don't think we
+> > should just silently ignore the value if it was set to an invalid title...
+> > And I don't think we should disable the apply button either.
+> 
+> We show ""invalid title"" for link searches; presumably that's evaluated
+> server-side?
+
+That is shown when the page does not seem to exist (based on the search results) and we get a false-y value from mw.Title.newFromText on the given title.",1413317234,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"(In reply to Alex Monk from comment #1)
+> Currently the redirect section of the page settings dialog and the template
+> placeholder page use MWTitleInputWidget.
+> 
+> The template placeholder page can be fixed with a simple change from value
+> === '' to !mw.Title.newFromText( value ) in
+> MWTemplatePlaceholderPage#onTemplateInputChange. It will no longer allow you
+> to add a template with an invalid name. No need for isValid here.
+
+What happens when you use a parser function or a magic word?
+
+> As for the redirect settings, that seems more difficult. I don't think we
+> should just silently ignore the value if it was set to an invalid title...
+> And I don't think we should disable the apply button either.
+
+We show ""invalid title"" for link searches; presumably that's evaluated server-side?",1412803664,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,Bump.,1412718616,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"Currently the redirect section of the page settings dialog and the template placeholder page use MWTitleInputWidget.
+
+The template placeholder page can be fixed with a simple change from value === '' to !mw.Title.newFromText( value ) in MWTemplatePlaceholderPage#onTemplateInputChange. It will no longer allow you to add a template with an invalid name. No need for isValid here.
+
+As for the redirect settings, that seems more difficult. I don't think we should just silently ignore the value if it was set to an invalid title... And I don't think we should disable the apply button either.",1411602589,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+API XHR requests from mediawiki do not transmit cookies when editing,"Looking at the network traffic from visiting a page on enwiki, I saw that when editing a page (both with VE enabled and without it) a few GET requests get performed to API, like in example:
+
+https://en.wikipedia.org/w/api.php?format=json&uselang=en&action=visualeditor&paction=parse&page=Moravian-Silesian_Region
+
+these requests go out as XHR requests and my browser does not attach any cookie to the request. Of course, this means that any cookie-based test we might want to perform (like using HHVM) will not work as expected.
+
+This would effectively block us from testing hhvm on the API cluster.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1411540440,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-zxwfb74rzwpzfsgbjyzv,task_description,invalid
+API XHR requests from mediawiki do not transmit cookies when editing,"Upon further analysis; this happened because of a bug in a chromium adblocking extension I was using, which blocked cookies in GET requests to api based on a regex I must have added years ago. Disabling the adblocking extension effectively sent the cookies correctly.",1411571347,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-zxwfb74rzwpzfsgbjyzv,task_subcomment,NA
+API XHR requests from mediawiki do not transmit cookies when editing,"I cannot reproduce this. According to Firebug the cookies are being included in XHR requests to the API when I visit enwiki pages, including the request to https://en.wikipedia.org/w/api.php?format=json&uselang=en&action=visualeditor&paction=parse&page=Moravian-Silesian_Region if I enable the VE beta feature and then attempt to edit that page using VE.
+
+Further, I'd expect we'd have had many more bug reports if this were a widespread problem, since lacking cookies in the API requests would cause the VE edits to be performed as an IP.
+
+My browser is Iceweasel 32.0 (which is Debian's rebranded version of Firefox 32.0). While it shouldn't matter for this particular case, I have ""Accept third-party cookies"" set to ""Always"".
+
+
+At any rate, this certainly isn't an API bug since the API has no control over whether the client sends any cookies. I'm going to tentatively reassign it to ""JavaScript"".",1411569490,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-zxwfb74rzwpzfsgbjyzv,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,"No UI
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the link inspector/math inspector for an existing link
+3.Close the inspector by clicking on ""Done"" button or you can keep the inspector open
+4.Now scroll down the page so that the inspector goes outside the current surface
+5.Now click somewhere else in the document
+6.Now go back and reopen the previous inspector
+
+Observed Result:
+There is no UI for the inspector,if you try inspecting some other inspector on the current viewport that will also appear without any UI.
+
+for link inspector if you switch tab and come back to VE, the link inspector will have only the link target suggestions inside it .
+
+Environment: Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14854}",1411428360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mypudm3323akv2drcpva,task_description,resolved
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,Verified the fix in Production,1412283585,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,Verified the backport in test2,1411667828,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,Verified the fix in Betalabs,1411592274,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,"**gerritadmin** wrote:
+
+Change 162474 merged by jenkins-bot:
+Re-clip popups after resizing them
+
+https://gerrit.wikimedia.org/r/162474",1411509800,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,"**gerritadmin** wrote:
+
+Change 162474 had a related patch set uploaded by Catrope:
+Re-clip popups after resizing them
+
+https://gerrit.wikimedia.org/r/162474",1411508273,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,"Created attachment 16543
+Link inspector
+
+**Attached**: {F14856}",1411428435,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","video capture of the bug
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open any inspector-Link/Math/Special Character for any existing node
+3.Now while the inspector is open, place the cursor any where else in the document
+
+
+Observed Result:
+The inspector closes and flickers in the new position.
+
+See the video capture attached
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71373
+
+**Attached**: {F14852}",1411426740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wfdurzh7jsda4trl4dsh,task_description,declined
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",I'm now not getting any flickering in Beta Labs or production. Fixed?,1421176141,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","I am still getting this issue in Betalabs.
+
+{F20118}",1418081747,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",Not seeing any flicker in master.,1418050687,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","Nope, still happening in en.wiki,test2 and Betalabs",1413832164,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","Nope, still happening in en.wiki,test2 and Betalabs",1413832159,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",This appears to now be fixed (testing on enwiki); can we confirm and close?,1413820149,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","It's now worse, see bug 71373. I speculated about why this bug happens in bug 71373 comment 3.",1411779985,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",Nope this is still happening.I guess it has something to do with the code change in https://gerrit.wikimedia.org/r/#/c/160034/,1411591661,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",Possibly now fixed?,1411588926,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert a citation/a comment/math node
+3.Now place your cursor at the beginning of the node that you just added
+4.Drag the selection vertically, you will be able to do the selection over the next lines
+5.Now again place the cursor at the beginning of the node added in step 2
+6.Select the line of the node horizontally and then try to drag the selection vertically
+
+Observed Result:
+The selection stops at the focusable node and does not get extended towards the next lines.
+
+Environment:Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411418760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7cay56sblrqfurqj5hno,task_description,resolved
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,Verified the fix in production,1412888686,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7cay56sblrqfurqj5hno,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,Verified the fix in test2,1412361272,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7cay56sblrqfurqj5hno,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,"**gerritadmin** wrote:
+
+Change 162904 merged by jenkins-bot:
+Don't perform focus node native selection trick while dragging
+
+https://gerrit.wikimedia.org/r/162904",1411682242,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7cay56sblrqfurqj5hno,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,"**gerritadmin** wrote:
+
+Change 162904 had a related patch set uploaded by Esanders:
+Don't perform focus node native selection trick while dragging
+
+https://gerrit.wikimedia.org/r/162904",1411660287,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7cay56sblrqfurqj5hno,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Formula
+3.Attempt to insert ""\pi"" inside the inspector
+
+Observed Result:
+As soon as you type \ in the inspector , it closes and tries to parse that \ and shows error ""Failed to parse (lexing error)""
+
+
+Environment:Betalabs
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1411413300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szea6r75prmyfpghqu7p,task_description,resolved
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Verified the fix in test2 and Betalabs,1413830221,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Moving back to ""FIXED"" and re-using bug 72136.",1413481348,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,*** Bug 72136 has been marked as a duplicate of this bug. ***,1413481134,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"But the difference is, this time it does not try to parse each time a character is inserted , just closes the inspector",1413422439,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,This started happening within last couple of hours,1413422340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Verified the fix in production,1412283461,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Verified the fix in test2,1411684245,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Verified the fix in Betalabs,1411591230,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Change 162495 merged by jenkins-bot:
+Calculate selected node on change and emit contextChange
+
+https://gerrit.wikimedia.org/r/162495",1411521450,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Change 162473 abandoned by Bartosz Dziewoński:
+ve.ui.Context: Prevent context changes during opening/closing inspectors better
+
+Reason:
+Ed probably knows better.
+
+https://gerrit.wikimedia.org/r/162473",1411513209,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Change 162495 had a related patch set uploaded by Esanders:
+Calculate selected node on change and emit contextChange
+
+https://gerrit.wikimedia.org/r/162495",1411512763,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Change 162473 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ui.Context: Prevent context changes during opening/closing inspectors better
+
+https://gerrit.wikimedia.org/r/162473",1411507822,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,(The cause is probably 49a239b4b68719dc59bacf79e5186aceca881c58.),1411427135,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"After dm.Surface emits 'contextChange', ve.ui.Context#afterContextChange thinks that the inspector should be closed, because `selectedNode !== this.lastSelectedNode` (this.lastSelectedNode is null). I spent way too much time debugging this and I still don't know why that happens. It worries me somewhat that `selectedNode` is a paragraph node rather than mwMath node.",1411424695,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Focus issue?,1411420860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,It only closes when you're inserting a new formula. Editing existing ones doesn't have this problem.,1411420549,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+[Regression] Jenkins: SQLite database is often locked causing queries to fail,"https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/11566/
+
+Artifact: mw-debug-www.log
+
+DatabaseBase::query: Writes done: REPLACE INTO objectcache (keyname,value,exptime) VALUES ('X')
+SQL ERROR (ignored): database is locked
+..
+
+
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR: database is locked
+..
+
+
+MessageBlobStore::insertMessageBlob failed to update DB: exception 'DBQueryError' with message 'A database error has occurred. Did you forget to run maintenance/update.php after upgrading?  See: https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script
+Query: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('en','jquery.ui.button','{}','20140919182152')
+Function: MessageBlobStore::insertMessageBlob/single-row
+Error: 5 database is locked
+
+
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: REPLACE INTO objectcache (keyname,value,exptime) VALUES ('X')
+SQL ERROR (ignored): database is locked
+..
+
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+...
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major",1411151220,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4sadouseu6almebfar54,task_description,duplicate
+[Regression] Jenkins: SQLite database is often locked causing queries to fail,"I don't think MediaWiki manages SQLite lock and concurrency at all.
+
+In this case, it seems two different Apache PHP threads are attempting to update the message cache.   For CI purposes, maybe we want to repopulate the message cache in the DB or skip it entirely to use the good old messages PHP files.",1411380617,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-4sadouseu6almebfar54,task_subcomment,NA
+Dates replaced by [[MediaWiki:Badtitletext]],"https://ast.wikipedia.org/w/index.php?title=Peligru_Mariellu&diff=747158&oldid=747157
+
+shows 1922 being replaced by [[MediaWiki:Badtitletext]].
+
+https://ast.wikipedia.org/w/index.php?title=Peligru_Mariellu&diff=747160&oldid=747159
+
+shows ""sieglu XX"" being replaced by [[MediaWiki:Badtitletext]].
+
+Nothing is known about the user's browser, skin, or OS.  It appears that the editor wrote this article at the Spanish Wikipedia, pasted the wikitext code into VisualEditor, and was trying to translate it into Asturian and correct the resulting nowiki mess when this happened.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411065120,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wicmfrektsx4wuuuhcwq,task_description,resolved
+Dates replaced by [[MediaWiki:Badtitletext]],"Without knowing anything more about what HTML parsoid got, this is hard to reproduce, so for now, I am going to presume this is an instance of the yet to be fixed T72960 (or the now fixed T72894) and close this. Please reopen if you have any additional information that can help.",1422986051,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-wicmfrektsx4wuuuhcwq,task_subcomment,NA
+Dates replaced by [[MediaWiki:Badtitletext]],"This may be a duplicate of bug 70960 if the user did insert a ""./"" in the link content part. Otherwise, it may be another instance of bug 70894. But leaving this open for now in case we can figure out more about what the user typed there in the links.",1411066072,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-wicmfrektsx4wuuuhcwq,task_subcomment,NA
+"VisualEditor: Overlay doesn't close, elements aren't clickable when copying dir=""auto"" values","1. Open any article
+2. Select the article title (firstHeading), copy, open the page settings, and set the default sort, and apply.
+3. try to click any element - it fails.
+
+Inspect element tells you there is ""ve-ui-overlay-global ve-ui-overlay"" over all...
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1410725100,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-qhmfjyurm2j53vu5lrbp,task_description,resolved
+"VisualEditor: Overlay doesn't close, elements aren't clickable when copying dir=""auto"" values",Fixed as part of the fixes for 70731.,1412359187,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qhmfjyurm2j53vu5lrbp,task_subcomment,NA
+"VisualEditor: [Regression wmf21] Cannot open any inspector, throwing error ""Uncaught TypeError: Cannot read property 'top' of undefined""","Steps to reproduce:
+
+1.Open a page with VE
+2.Try to open Link/Math/Language/Special Character inspector
+
+Observed Result:
+None of them opens and in the console it shows the following error:
+
+Uncaught TypeError: Cannot read property 'top' of undefined 
+
+Environment:test2.betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70770
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70768",1410551280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d4t2kxc6dwgul6wss43q,task_description,resolved
+"VisualEditor: [Regression wmf21] Cannot open any inspector, throwing error ""Uncaught TypeError: Cannot read property 'top' of undefined""",Verified the fix in production,1411683755,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d4t2kxc6dwgul6wss43q,task_subcomment,NA
+"VisualEditor: [Regression wmf21] Cannot open any inspector, throwing error ""Uncaught TypeError: Cannot read property 'top' of undefined""",Verified the fix in test2,1410823806,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d4t2kxc6dwgul6wss43q,task_subcomment,NA
+"VisualEditor: [Regression wmf21] Cannot open any inspector, throwing error ""Uncaught TypeError: Cannot read property 'top' of undefined""",Verified the fix in Betalabs.,1410559740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d4t2kxc6dwgul6wss43q,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"Environment- test2, beta
+
+1> open VE, I get JS console error as “Uncaught TypeError: Cannot read property 'top' of undefined” in Chrome.
+
+
+In FF the error is TypeError: rect is undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70782
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70768",1410526980,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ppbj4smgqgqx5ararami,task_description,resolved
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,Verified the fix in production,1411683636,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,Verified the fix in test2,1410823823,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,Verified the fix in Betalabs,1410559714,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"**gerritadmin** wrote:
+
+Change 160082 merged by jenkins-bot:
+ve.getStartAndEndRects returns null for empty rect lists
+
+https://gerrit.wikimedia.org/r/160082",1410559654,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"**gerritadmin** wrote:
+
+Change 160082 had a related patch set uploaded by Jforrester:
+ve.getStartAndEndRects returns null for empty rect lists
+
+https://gerrit.wikimedia.org/r/160082",1410553231,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"**gerritadmin** wrote:
+
+Change 160076 merged by jenkins-bot:
+ve.getStartAndEndRects returns null for empty rect lists
+
+https://gerrit.wikimedia.org/r/160076",1410552540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"**gerritadmin** wrote:
+
+Change 160076 had a related patch set uploaded by Catrope:
+ve.getStartAndEndRects returns null for empty rect lists
+
+https://gerrit.wikimedia.org/r/160076",1410552315,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"(In reply to Rummana Yasmeen from comment #4)
+> RoanKattouw, Try opening a new page with VE, you will get this error.
+
+Yup, that does the trick. Thanks.",1410550162,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"RoanKattouw, Try opening a new page with VE, you will get this error.",1410550034,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"I can't reproduce this, neither logged in nor logged out, neither on test2 nor on beta labs, using Chrome.",1410549264,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"(In reply to Roan Kattouw from comment #1)
+> I can't reproduce this on test2. Does it happen when logged out as well?
+
+yes, it happens irrespective of my login status.",1410549010,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,I can't reproduce this on test2. Does it happen when logged out as well?,1410543569,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"I haven't tried to reproduce this.  
+
+I copied a page title from Meta and pasted it into VisualEditor on another wiki.  The text was set to =Page title= and highlighted in very pale blue, with a dashed line underneath, so I set it to Paragraph (that worked) and went to the character formatting menu to clear the formatting.  The 'Language' item was highlighted, so I chose that.
+
+The first time, the dialog box that popped up was tiny.  It was barely big enough to display the ""done"" button, which was overlapping with an odd ""$1 AUTO"" string in gray text.
+
+The second time, the dialog box looked normal, but 'Remove' didn't actually remove anything.  'Clear formatting' also doesn't remove anything.  
+
+Then the box got stuck open.  It would go away if I highlighted text, but 'Done' didn't close it and clicking outside it didn't close it.
+
+I was able to keep editing and to save the page when I was finished, but it produced <span dir=""auto""> tags, which I didn't want.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410461100,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-hqizdzws5eagirsav5rw,task_description,resolved
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"**gerritadmin** wrote:
+
+Change 160096 merged by jenkins-bot:
+(Kind of) fix treatment of strange dir values
+
+https://gerrit.wikimedia.org/r/160096",1410558535,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"**gerritadmin** wrote:
+
+Change 160098 merged by jenkins-bot:
+Don't return undefined in ve.init.mw.Platform#getLanguageName
+
+https://gerrit.wikimedia.org/r/160098",1410558397,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"**gerritadmin** wrote:
+
+Change 160098 had a related patch set uploaded by Catrope:
+Don't return undefined in ve.init.mw.Platform#getLanguageName
+
+https://gerrit.wikimedia.org/r/160098",1410558252,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"**gerritadmin** wrote:
+
+Change 160096 had a related patch set uploaded by Catrope:
+(Kind of) fix treatment of strange dir values
+
+https://gerrit.wikimedia.org/r/160096",1410557636,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"It looks like page titles (at least on meta, possibly elsewhere) are wrapped in <span dir=""auto"">, which is recognized as a language annotation (because it has a dir attribute) but doesn't work very well once it's considered a language annotation (because it has no lang attribute). I'll poke at this. Earlier, Amir reported a problem with pages containing <span dir=""rtl""> tags (also no lang attribute) so maybe this is semi-related.",1410464181,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,"link inspector
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Open a link inspector for any link
+3.Tap on the text box to bring up the link target suggestions
+
+Observed Result:
+Link target suggestion drop down are appearing cut off to a small size.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14991}",1410379500,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-poy4sfkajyxaov7ad2nl,task_description,resolved
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,Verified the fix in production for desktop and mobile iOS,1411681425,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-poy4sfkajyxaov7ad2nl,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,"Yes, this one got fixed in wmf 22.Marking it as fixed.",1411596190,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-poy4sfkajyxaov7ad2nl,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,"Created attachment 16476
+desktop
+
+**Attached**: {F14993}",1410817251,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-poy4sfkajyxaov7ad2nl,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,"Created attachment 16475
+In desktop
+
+**Attached**: {F14992}",1410817198,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-poy4sfkajyxaov7ad2nl,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),"screenshot1
+
+Environment-test2,beta, production.
+
+1> open a page in VE, add a Basic citation.
+2>Click to add Basic citation again ,in the modal click on “Use an Existing Reference “.Select the citation that you just added.
+3>In the editor pane, delete all the citations.
+4> Select  to add Basic citation again. In the modal notice the “Use an Existing Reference “ button is  still active, although there are no citations to add to. Click on it and it opens a blank Reference modal.
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14787}",1410278760,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_description,resolved
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),Verified the fix in production,1411071391,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),Verified the fix in test2,1410553948,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),(Opened bug 70640 for that),1410308555,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),"This bug is about a very specific way to break the existing disabling of a different button. What you propose makes sense but it's not in scope here. I'll take a look into doing it anyway, but I'm going to re-close this bug.",1410307712,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),The Re-Use option in the Cite menu from the toolbar still remains enabled when there is no reference in the article.,1410306971,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),"**gerritadmin** wrote:
+
+Change 159423 merged by jenkins-bot:
+Properly mark reference search index as empty when setting internal list
+
+https://gerrit.wikimedia.org/r/159423",1410305209,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),Nice.,1410305119,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),"**gerritadmin** wrote:
+
+Change 159423 had a related patch set uploaded by Alex Monk:
+Properly mark reference search index as empty when setting internal list
+
+https://gerrit.wikimedia.org/r/159423",1410304462,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","In Safari, Go to Insert>Media, try to enter something in the search box.
+you will get the following error in the console and wont be able to place your cursor in to the search box:
+
+
+api.php:1TypeError: 'undefined' is not a function (evaluating 'jQuery111102360369882080704_1410208128038({""warnings"":{""main"":{""*"":""Unrecognized parameter: 'uselang'""}},""query"":{""searchinfo"":{""totalhits"":0}}})')
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1410208200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhkhxz7oi6kric5dekys,task_description,resolved
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that",Verified the fix in production,1411683480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that",Verified the fix in test2,1410824448,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that",Verified the fix in Betalabs,1410821352,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","**gerritadmin** wrote:
+
+Change 160503 merged by jenkins-bot:
+Work around position: fixed; bug in Safari
+
+https://gerrit.wikimedia.org/r/160503",1410809008,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","**gerritadmin** wrote:
+
+Change 160503 had a related patch set uploaded by Catrope:
+Work around position: fixed; bug in Safari
+
+https://gerrit.wikimedia.org/r/160503",1410808890,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","This issue happens when you scroll down the page a bit and try adding reference/citation/media.
+
+This happens everywhere: Betalabs, test2, production.",1410806053,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","This is happening for all citation dialogs, basic reference dialog, transclusion dialog, reference list dialog, Page Settings dialog.
+
+Environment:Betalabs",1410212007,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,"Screenshot
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=Help:Extension:GlobalCssJs&veaction=edit
+
+**Attached**: {F14684}",1410197220,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-hsklb2fted77hcl6jkir,task_description,resolved
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,Verified the fix in production,1411071242,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,Verified the fix in test2,1410553903,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,"Yes.
+
+*** This bug has been marked as a duplicate of bug 70423 ***",1410198175,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,Isn't this bug 70423?,1410198066,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,Probably related to similar link inspector behaviour?,1410197987,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"**Author:** `yaukasin`
+
+**Description:**
+zh-yue wikipedia does not load the stylesheets properly. When I view the source HTML code, I discover that there are many garbage stylesheets which would return error 404.
+
+Below is the code after the line <link rel=""canonical"" href=""......""> in zh-yue wikipedia 
+
+=============================================================
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.gadget.internalLinkHelper-altcolor&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.uls.nojs&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.visualEditor.viewPageTarget.noscript&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.wikihiero&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.legacy.commonPrint&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.legacy.shared&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.skinning.interface&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.ui.button&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=skins.vector.styles&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=wikibase.client.init&amp;only=styles&amp;skin=vector&amp;*"" />
+=============================================================
+
+
+Below is the code after the line <link rel=""canonical"" href=""......""> in en wikipedia for comparison 
+
+=============================================================
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&amp;lang=en&amp;modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cfeatured-articles-links%2CrefToolbar%2Cteahouse%7Cext.rtlcite%2Cwikihiero%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles%7Cwikibase.client.init&amp;only=styles&amp;skin=vector&amp;*"" />
+=============================================================
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major",1410180900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kinrik6hswrtg2xxwohw,task_description,resolved
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"Thanks for the quick investigation and fixing, Giuseppe!",1410204055,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"the patch has solved the problem, and now the page loads correctly.",1410199718,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"A patch for the problem has been created:
+
+https://gerrit.wikimedia.org/r/#/c/159080/",1410194886,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"While on varnish the url
+
+https://bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector&*
+
+returns 404, the same url without the final parameter returns correctly 200:
+
+https://bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector
+
+
+I confirmed that both urls, when properly translated, are answered with a 200 OK (and the same content) by the backend:
+
+https://zh-yue.wikipedia.org/w/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector
+ * 200 OK 26761
+https://zh-yue.wikipedia.org/w/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector&*
+ * 200 OK 26761
+
+So this seems to be an issue at the varnish layer.
+
+I'll update the ticket as I find out more.",1410188539,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"Thanks for taking the time to report this!
+
+I went to https://zh-yue.wikipedia.org/wiki/%E9%A0%AD%E7%89%88?debug=true and using the ""Network"" tab of Firefox' developer tools there are a few 404s for HTML/CSS stuff from bits, like
+
+https://bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector&* which is a 404.
+
+Replacing lang=yue by lang=zh-yue works.
+
+According to Operations mailing list there were issues with Bits which started on Friday around 16:33 UTC due to a serialisation of requests for one specific uncacheable URL which was extremely slow to render and piled up requests, but that should have been sorted out / worked around. I'll ask on the list.",1410186906,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Image
+3.Try to type in a caption
+
+Observed Result:
+
+
+The text gets copied again in the text line and a pawn follows it.Also if you try to edit the caption of an existing image in a page , it is almost impossible to type in.
+
+Enviornment:Betalabs
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15068}",1409943240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ovmfajyzbve3uus6gktf,task_description,resolved
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,Verified the fix in production,1411080858,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,Verified the fix in test2,1410554134,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,Verified the fix in Betalabs,1409961065,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,"**gerritadmin** wrote:
+
+Change 158797 merged by jenkins-bot:
+Followup cb86c4f: fix call to renamed setChanged() function
+
+https://gerrit.wikimedia.org/r/158797",1409955776,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,"**gerritadmin** wrote:
+
+Change 158797 had a related patch set uploaded by Catrope:
+Followup cb86c4f: fix call to renamed setChanged() function
+
+https://gerrit.wikimedia.org/r/158797",1409953884,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,"Screenshot
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15012}",1409878200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_description,resolved
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,Verified the fix in production,1411071931,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,Verified the fix in test2,1410554069,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,Verified the fix in Betalabs,1410377689,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,Fixed in https://gerrit.wikimedia.org/r/#/c/159243/,1410374292,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"See https://en.wikipedia.org/wiki/File:VisualEditorTableCopyBugScreenshot.jpg for what the editor selected.  See https://en.wikipedia.org/wiki/File:VisualEditorTableCopyBugScreenshot2.jpg (top) for what he got when he pasted it into the new place.
+
+This was found on Chrome and Windows 7.
+
+Also, if he used Ctrl-X to cut the table, he was unable to save his changes.  Clicking on the Save button did nothing after that point.  Ctrl-C to copy the table did not disable the Save button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409791740,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5nl2agli3yogyhbgab57,task_description,resolved
+Deleting from an empty paragraph to the end of an inline node throws an exception,Re-checked with 1.25wmf24 (32a0b3f). The fix works reasonably well - just make sure that the table is selected along with some text.  ,1428009677,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,In test2: selecting the above table and paste it will insert  the following symbol.☢,1427474126,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Verified in beta - for general cases it's fixed: tables can be copy/cut, the table format is preserved - and Save button is properly activated and functioning. 
+
+However, in the issue refers to  **the particular table example**( https://en.wikipedia.org/w/index.php?oldid=624091874 ) due to <ref name=""Tuck_U""></ref> will throw a lot of hiccups:
+``` {| class=""wikitable"" style=""font-size: 10pt; line-height: 11pt; margin-left: 2em; text-align: center; float: right""
+! 
+!
+Winter
+!
+<nowiki> </nowiki>Spring 
+!
+Summer 
+!
+Autumn 
+!
+Winter
+|-
+!
+1937
+| 
+| 
+| 
+| 
+| bgcolor=""#ccffff"" |1
+|-
+!
+1938
+| 
+| bgcolor=""#ccffff"" |2 
+| bgcolor=""#ccffff"" |3 
+| bgcolor=""#ccffff"" |4 
+| bgcolor=""#ccffff"" |5
+|-
+!
+1939
+| 
+| bgcolor=""#ccffff"" |6 
+| bgcolor=""#ccffff"" |7 
+| bgcolor=""#ccffff"" |8 
+| bgcolor=""#ccffff"" |9
+|-
+!
+1940
+| 
+| bgcolor=""#ccffff"" |10 
+| bgcolor=""#ccffff"" |11 
+| bgcolor=""#ccffff"" |12 
+|
+|-
+!
+1941
+| bgcolor=""#ccffff"" |13 
+| bgcolor=""#ccffff"" |14 
+| 
+| bgcolor=""#ccffff"" |15 
+|
+|-
+!
+1942
+| 
+| bgcolor=""#ccffff"" |16 
+| 
+| 
+|
+|-
+| colspan=""6"" style=""font-size: 8pt; text-align:left"" |Issues of ''Tales of Wonder'', showing issue number.
+Walter Gillings was editor throughout.<ref name=""Tuck_U""></ref>
+|}
+<br>
+
+``` 
+
+Try to select, copy, and cut the above table: 
+Uncaught Error: Offset could not be translated to a DOM element...
+Uncaught TypeError: Cannot read property 'isWrapped' of null...
+Uncaught Error: offset was inside a handlesOwnChildren...
+Uncaught Error: Invalid retain length, cannot retain backwards:...
+",1426703976,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Change 158662 merged by jenkins-bot:
+Fix unbalanced transaction when removing to/from the edge of an inline node
+
+[[https://gerrit.wikimedia.org/r/158662]]",1426180649,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Change 158662 had a related patch set uploaded (by Catrope):
+WIP Failing test case
+
+[[https://gerrit.wikimedia.org/r/158662]]
+",1426164999,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"**gerritadmin** wrote:
+
+Change 158662 had a related patch set uploaded by Esanders:
+WIP Failing test case
+
+https://gerrit.wikimedia.org/r/158662",1409943300,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Minimal failure case in core to trigger the unbalanced delete which is causing this to happen:
+
+<p></p>
+<p>a<span rel=""ve:Alien"">b</span></p>
+
+Select from the empty paragraph to after the b (range 1,6) and delete.",1409942098,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"The problem appears after the cutting, not after the pasting.  Also, it's usually possible to switch to source editing.  Consequently, this is only a lost-work bug for most people (anyone who doesn't know about or doesn't try switching to source.)",1409936955,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Update:
+
+To make this work, you have to select the table (just its own cells), without any text before and after.
+
+If you select more than the table (text + table + more text), then the table formatting appears to be correct when pasted in VisualEditor, but isn't actually correct when it's saved.  See https://en.wikipedia.org/w/index.php?oldid=624091874 for the saved version, and compare it to the same table in previous versions.  
+
+In addition to not being able to save after cutting and pasting, it's not possible to switch to source code editing.",1409875504,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,"Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text
+3.Press commann+K
+
+
+Observed Result:
+Link inspector flickers and applies the link text as link target without showing any link target names.
+
+Environment:Betalabs
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1409766540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a6d7zyzurpoea557wxot,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,Verified the fix in Production,1410545647,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,Verified the fix in test2,1409871338,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,Verified the fix in Betalabs,1409856880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,"Change 158269 merged by jenkins-bot:
+Only focus the paste target if focusedNode has changed
+
+https://gerrit.wikimedia.org/r/158269",1409789018,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,"Change 158269 had a related patch set uploaded by Esanders:
+Only focus the paste target if focusedNode has changed
+
+https://gerrit.wikimedia.org/r/158269",1409785018,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,Regression from https://gerrit.wikimedia.org/r/#/c/157199/,1409771041,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"The message https://translatewiki.net/wiki/MediaWiki:Visualeditor-dialog-action-insert/he was translated on August 21, but still doesn't appear in the Hebrew Wikipedia: https://he.wikipedia.org/wiki/MediaWiki:Visualeditor-dialog-action-insert .
+
+IRC:
+James_F	aharoni: Yeah, I've been looking at this.
+James_F	aharoni: It looks like the i18n job for VE-core hasn't run for a while.
+James_F	aharoni: I fixed it in If68193e7c3c78beeeb47975dc63ebaaec21448f3 and it worked… maybe that didn't stick?
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1409598060,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7fusp4t2k553x5ynkjxt,task_description,resolved
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"(In reply to Amir E. Aharoni from comment #3)
+> The message that triggered this bug was imported successfully, so I guess
+> that it's fixed now
+
+And it still is.
+
+(In reply to Niklas Laxström from comment #4)
+> extensions//Parsoid/php/i18n/en.
+> json in
+
+That's not VisualEditor and it's caused by 9b986c9cb0169918d41e146096d4d73c3aca58f0
+Sent https://gerrit.wikimedia.org/r/162548 / I0bf1db4b8 (19edff5a)",1411540312,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,So REOPENED?,1411538585,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"This has been going since August 14th so there is something broken still:
+PHP Warning:  filemtime(): stat failed for /resources/projects/mediawiki-extensions/extensions//Parsoid/php/i18n/en.json in /www/translatewiki.net/w/extensions/Translate/utils/MessageGroupCache.php on line 196",1411538516,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"The message that triggered this bug was imported successfully, so I guess that it's fixed now, but I don't know what caused or what fixed it.",1411537716,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"Is this still a problem? If so, can someone (Niklas/Amir/?) on this bug help point out where the problem might be?",1411514972,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"A better link to see that the translation is not updated:
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%99%D7%95%D7%97%D7%93%3A%D7%94%D7%95%D7%93%D7%A2%D7%95%D7%AA+%D7%94%D7%9E%D7%A2%D7%A8%D7%9B%D7%AA&prefix=Visualeditor-dialog-action-insert&filter=all&lang=he&limit=50",1409598873,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+VisualEditor: Attempting to set an invalid range on undo,"1. Open a page with some content (a few paragraphs)
+2. Select all and delete
+3. Insert a math node
+4. Press undo
+
+You'll get an exception as selectionBefore in the undo stack is still the range of the whole original document, but your document should be empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409318940,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gc45eius7aytam2rlpth,task_description,resolved
+VisualEditor: Attempting to set an invalid range on undo,"**gerritadmin** wrote:
+
+Change 157149 merged by jenkins-bot:
+Track selectionBefore in staging transactions
+
+https://gerrit.wikimedia.org/r/157149",1409336800,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gc45eius7aytam2rlpth,task_subcomment,NA
+VisualEditor: Attempting to set an invalid range on undo,"**gerritadmin** wrote:
+
+Change 157149 had a related patch set uploaded by Esanders:
+Track selectionBefore in staging transactions
+
+https://gerrit.wikimedia.org/r/157149",1409330992,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gc45eius7aytam2rlpth,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,"Screenshot
+
+the following error is appearing in the console while trying to open Math inspector:
+
+Uncaught TypeError: Cannot read property 'length' of null
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14629}",1408999440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x72zymsnartka42zou7j,task_description,resolved
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,Verified the fix in production,1409865451,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,Verified the fix in test2,1409261109,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,Verified the fix in Betalabs,1409075778,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,"This was fixed by https://gerrit.wikimedia.org/r/#/c/155831/ , don't know why it hasn't deployed to beta labs yet.",1409071611,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,This is still occurring in Betalabs while trying to open math inspector in an empty line.,1409013117,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,Now appears to work for me – deployment issue?,1409011001,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media and insert an image
+3.Reopen the media settings dialog and change the image position to left/centre
+
+Observed Result:
+The following error appears in the con sole:
+Uncaught TypeError: Cannot read property 'length' of null 
+
+User gets stuck inside Media Settings dialog as it none of the button is working to escape from it.
+
+
+Environment:Betalabs
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408997580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_description,resolved
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,Verified the fix in production,1409865244,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,Verified the fix in test2,1409261969,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,Verified the fix in Betalabs,1409075454,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,"Change 156192 merged by jenkins-bot:
+Followup bbff57b, 8c71904: use getter for availableTools, again
+
+https://gerrit.wikimedia.org/r/156192",1409002854,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,"Change 156192 had a related patch set uploaded by Mooeypoo:
+Validate availableTools before loop in Context's 'hasInspector'
+
+https://gerrit.wikimedia.org/r/156192",1409002079,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"In MWLinkTargetInputWidget and other places, we perform API requests that give us exactly the kind of information (existence, redirect status, etc.) that goes into ve.init.mw.LinkCache, but we don't write it to the link cache. We should do that, so we can save ourselves some API requests.
+
+Right now, when you make a link, we do another API request to check if the link should be blue or red, even if the link target came from a suggestion list and we already know it should be blue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408688640,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-goezj3fhvn2phuamifjy,task_description,resolved
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 159623 merged by jenkins-bot:
+Refactor a bunch of CategoryInputWidget code, tear out dead/broken redirect handling that should be rewritten
+
+https://gerrit.wikimedia.org/r/159623",1410920005,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 159623 had a related patch set uploaded by Alex Monk:
+Refactor a bunch of CategoryInputWidget code, tear out dead/broken redirect handling that should be rewritten
+
+https://gerrit.wikimedia.org/r/159623",1410387449,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Now just waiting for category existence checking, I believe?",1410376367,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 159418 merged by jenkins-bot:
+Update LinkCache in MWTitleInputWidget
+
+https://gerrit.wikimedia.org/r/159418",1410376147,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 159418 had a related patch set uploaded by Alex Monk:
+Update LinkCache in MWTitleInputWidget
+
+https://gerrit.wikimedia.org/r/159418",1410302500,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"(In reply to James Forrester from comment #3)
+> Do we want to do this from MWTitleInputWidget and MWCategoryInputWidget?
+
+Re-opening after discussing with Roan.",1410055508,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,Do we want to do this from MWTitleInputWidget and MWCategoryInputWidget?,1409266825,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 156955 merged by jenkins-bot:
+In LinkTargetInputWidget, put existence status into LinkCache
+
+https://gerrit.wikimedia.org/r/156955",1409264225,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 156955 had a related patch set uploaded by Alex Monk:
+In LinkTargetInputWidget, put existence status into LinkCache
+
+https://gerrit.wikimedia.org/r/156955",1409260214,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Return of the whitespace bunny-hopping bug,"This mess:
+
+[[Help:Installing Japanese character sets|<span class=""t_nihongo_icon"" style=""color: #00e; font: bold 80% sans-serif; text-decoration: none; padding: 0 .1em;"">?</span>]]) [[Category:Articles containing Japanese-language text]]
+
+was added in https://en.wikipedia.org/w/index.php?curid=31216768&diff=621842944&oldid=600210359
+
+to produce this:
+
+;Track & road events<ref name=""JAAF20120611"">[http://www.jaaf.or.jp/fan/news/2012/20120611.html {{Nihongo||ロンドンオリンピック トラック・フィールド種目・競歩種目の日本代表選手|The Japanese national team of Track & Field and Race Walk at the 2012 Olympic Games}}][[Help:Installing Japanese character sets|<span class=""t_nihongo_icon"" style=""color: #00e; font: bold 80% sans-serif; text-decoration: none; padding: 0 .1em;"">?</span>]]) [[Category:Articles containing Japanese-language text]]{{ja icon}}. Japan Association of Athletics Federations (2012-06-11). Retrieved 19 June 2012.</ref>
+
+The editor says s/he didn't edit this line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69876",1408640880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-htx2um5fnyusay6ynwua,task_description,resolved
+VisualEditor: Return of the whitespace bunny-hopping bug,"**gerritadmin** wrote:
+
+Change 155634 merged by jenkins-bot:
+Fix the newline bunny-hop bug harder
+
+https://gerrit.wikimedia.org/r/155634",1409133591,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-htx2um5fnyusay6ynwua,task_subcomment,NA
+VisualEditor: Return of the whitespace bunny-hopping bug,"(In reply to Gerrit Notification Bot from comment #2)
+> Change 155634 had a related patch set uploaded by Catrope:
+> Fix the newline bunny-hop bug harder
+> 
+> https://gerrit.wikimedia.org/r/155634
+
+This addresses the VE part of the bug. With this patch, VE will no longer corrupt whitespace around categories and the like (I've been seeing this a bunch in needcheck diffs, so that should fix those too). This will prevent Parsoid from corrupting the reference on this page, *unless* you edit it, in which case it'll still get messed up. I'll file a Parsoid bug for that.",1408655661,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-htx2um5fnyusay6ynwua,task_subcomment,NA
+VisualEditor: Return of the whitespace bunny-hopping bug,"**gerritadmin** wrote:
+
+Change 155634 had a related patch set uploaded by Catrope:
+Fix the newline bunny-hop bug harder
+
+https://gerrit.wikimedia.org/r/155634",1408654740,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-htx2um5fnyusay6ynwua,task_subcomment,NA
+VisualEditor: Return of the whitespace bunny-hopping bug,"Ugh, I found the cause, it's another whitespace bunny-hop bug.
+
+This whole mess is made because we have something like )[category] <span> and it gets turned into ) [category]<span> . The space jumps to the other side of the category.
+
+Additionally, there's a template leakage bug in Parsoid here. That parenthesis, category, space and span tag should have been marked as template-generated content but aren't. This means that if you try to edit this reference, Parsoid will make a big mess of it. As long as you don't edit it, it'll be fine, but the space jump bug in VE causes it to be edited.",1408650606,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-htx2um5fnyusay6ynwua,task_subcomment,NA
+Regression: Nested citations broken,"From https://bugzilla.wikimedia.org/show_bug.cgi?id=50749#c2
+
+Look at [[Otto I]].  It has 63 references, including ref #18 (""Thompson"") from explanatory footnote [d].  This ref doesn't appear in VisualEditor.
+
+http://en.wikipedia.org/wiki/Otto_I%2C_Holy_Roman_Emperor?oldid=621934593
+http://parsoid.wmflabs.org/enwiki/Otto_I%2C_Holy_Roman_Emperor?oldid=621934593
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408586580,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-t2avilcwnjfjpdywdken,task_description,resolved
+Regression: Nested citations broken,Now deployed. Please reopen if necessary.,1408997647,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-t2avilcwnjfjpdywdken,task_subcomment,NA
+Regression: Nested citations broken,"Change 155661 merged by jenkins-bot:
+(Bug 69827): Supported nested <ref> tags once more
+
+https://gerrit.wikimedia.org/r/155661",1408731167,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t2avilcwnjfjpdywdken,task_subcomment,NA
+Regression: Nested citations broken,"Change 155661 had a related patch set uploaded by Subramanya Sastry:
+(Bug 69827): Supported nested <ref> tags once more
+
+https://gerrit.wikimedia.org/r/155661",1408663367,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t2avilcwnjfjpdywdken,task_subcomment,NA
+Regression: Nested citations broken,This broke in https://gerrit.wikimedia.org/r/#/c/143362/,1408637619,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-t2avilcwnjfjpdywdken,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","I'm not sure why, but wgBetaFeaturesFeatures is incomplete on my local MediaWiki-Vagrant install.
+
+In the actual preferences UI, I see the following BetaFeatures:
+
+* Hovercards
+* Compact personal bar
+* Fixed header
+* VisualEditor
+* VisualEditor language tool
+
+But wgBetaFeaturesFeatures is only:
+
+{ popups: null, visualeditor-enable-language: null }
+
+That in turn means that these are the only ones looped over in betafeatures.js, which means other features don't have the JavaScript/browser blacklist processing.
+
+This bug affects production as well.
+
+Side note, you can use:
+
+.client-js .mw-ui-feature-requirements-javascript {
+  display: none;
+}
+
+for a simpler way to do the JS-hiding, but that doesn't address the underlying problem.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70371",1408581780,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-7336trfcokkmlnznz5wa,task_description,resolved
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","(In reply to Matthew Flaschen from comment #0)
+> Side note, you can use:
+> 
+> .client-js .mw-ui-feature-requirements-javascript {
+>   display: none;
+> }
+> 
+> for a simpler way to do the JS-hiding, but that doesn't address the
+> underlying problem.
+
+Done in https://gerrit.wikimedia.org/r/161690",1411238274,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","Underlying issue is only fixed by James's patch, but Seb35's patch has already fixed the display for the beta features I tested.",1411237957,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","**gerritadmin** wrote:
+
+Change 159538 merged by jenkins-bot:
+Populate $features even if there aren't any requirements
+
+https://gerrit.wikimedia.org/r/159538",1411237819,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","Ah, sorry. I meant https://gerrit.wikimedia.org/r/160213.",1411170587,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences",https://gerrit.wikimedia.org/r/161629 should have resolved this bug. Is it confirmed?,1411170445,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","This bug is a consequence of bug 70814, see https://bugzilla.wikimedia.org/show_bug.cgi?id=70814#c5 : the fix there correctly populates the wgBetaFeaturesFeatures array. (I make this bug depend of bug 70814, but it is similar to a duplicate.)",1411082291,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","**gerritadmin** wrote:
+
+Change 159538 had a related patch set uploaded by Jforrester:
+Populate $features even if there aren't any requirements
+
+https://gerrit.wikimedia.org/r/159538",1410379499,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox","Alt+Shift+F is shortcut for search box (very useful to validate a name of article...)
+
+Pressing Alt+Shift+F when the cursor is in the begining of article or in the dummy paragraph (slug) will cause a white pawn ♙ to appear. 
+
+(appears in https://he.wikipedia.org/wiki/%D7%90%D7%99%D7%9C%D7%9F_%D7%9E%D7%9C%D7%9B%D7%90?veaction=edit)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408566780,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-awpfthjrjritxkhujr46,task_description,resolved
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox",Fixed.,1421282422,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-awpfthjrjritxkhujr46,task_subcomment,NA
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox",(But can in Firefox.),1415813716,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-awpfthjrjritxkhujr46,task_subcomment,NA
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox",Cannot reproduce on Chrome...,1415813626,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-awpfthjrjritxkhujr46,task_subcomment,NA
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox",With which browser(s) was this tested?,1408571861,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-awpfthjrjritxkhujr46,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"Observed on iPad. Steps to repro:
+
+1. Go into VE edit mode on an article and enter the link inspector
+2. Use browser back to exit the link inspector
+
+Expected: you get a message asking if you want to abandon changes and get taken back to the content if you say yes
+
+Actual: no message about abandoning changes, and you're taken to the top of the page but can't scroll below the fold
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408143420,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_description,resolved
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,Verified the fix in production,1409866242,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,Verified the fix in Betalabs and test2,1409346227,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**jgonera** wrote:
+
+All patches merged, marking as fixed.",1409163492,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**gerritadmin** wrote:
+
+Change 155668 merged by jenkins-bot:
+Destroy WindowManagers in Context and Surface destructors
+
+https://gerrit.wikimedia.org/r/155668",1408665316,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**gerritadmin** wrote:
+
+Change 155668 had a related patch set uploaded by Catrope:
+Destroy WindowManagers in Context and Surface destructors
+
+https://gerrit.wikimedia.org/r/155668",1408665201,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**gerritadmin** wrote:
+
+Change 155657 merged by jenkins-bot:
+Remove global overlay classes when destroying MobileSurface
+
+https://gerrit.wikimedia.org/r/155657",1408664697,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**gerritadmin** wrote:
+
+Change 155657 had a related patch set uploaded by JGonera:
+Remove global overlay classes when destroying MobileSurface
+
+https://gerrit.wikimedia.org/r/155657",1408662224,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"(In reply to Juliusz Gonera from comment #3)
+> I thought it could be easily fixed by adding this.inspectors.clearWindows()
+I haven't reported this in Bugzilla yet, but I discovered yesterday that clearWindows() is completely broken. It will only clean up the current window (i.e. the one that's currently open), and it won't touch any others.
+
+> in ve.ui.Context.prototype.destroy, but unfortunately that results in:
+> 
+> ""Uncaught TypeError: Cannot read property 'getComputedStyle' of undefined ""
+> 
+> This happens when WindowManager invokes OO.ui.Window.prototype.hold. I
+> suspect it's because everything in WindowManager is async/delayed (to
+> accommodate for animations), so DOM nodes no longer exist when WindowManager
+> tries to tear windows down.
+Yeah that sounds likely. Maybe WindowManager needs a destroy function that destroys everything immediately? I also don't really understand why WindowManager not cleaning up is causing problems if the WindowManager's DOM element is removed.",1408575498,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**jgonera** wrote:
+
+This actually seems to be a VE/OOUI bug. The problem lies in WindowManager not cleaning up after itself.
+
+I thought it could be easily fixed by adding this.inspectors.clearWindows() in ve.ui.Context.prototype.destroy, but unfortunately that results in:
+
+""Uncaught TypeError: Cannot read property 'getComputedStyle' of undefined ""
+
+This happens when WindowManager invokes OO.ui.Window.prototype.hold. I suspect it's because everything in WindowManager is async/delayed (to accommodate for animations), so DOM nodes no longer exist when WindowManager tries to tear windows down.",1408575332,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/kzlyuZku",1408143915,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/ttlYWwkt",1408143613,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"I copied part of a header from one page on se.wikimedia and pasted in an already started header on another page. After my paste the symbol ☀ was added:
+
+https://se.wikimedia.org/w/index.php?title=Projekt%3AWikidata_2014%2FAns%C3%B6kan_till_Vinnova&diff=34844&oldid=34843
+
+(Page I copied from: https://se.wikimedia.org/wiki/Projekt:Offentligkonst.se_2014/Ans%C3%B6kan_till_Vinnova )
+
+I used Google Chrome Version 35.0.1916.153 on Ubuntu 14.04.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408095180,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-k7nxqqgjeodo2osblgev,task_description,resolved
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"**gerritadmin** wrote:
+
+Change 154407 merged by jenkins-bot:
+Ignore whitespace when generating paste context
+
+https://gerrit.wikimedia.org/r/154407",1408299616,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"**gerritadmin** wrote:
+
+Change 154407 had a related patch set uploaded by Esanders:
+Ignore whitespace when generating paste context
+
+https://gerrit.wikimedia.org/r/154407",1408198388,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,This happens when pasting into any node with inner whitespace in it's Parsoid HTML (e.g. <h2> Foo </h2>),1408198195,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"Nevermind, managed to reproduce.",1408196413,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"Can you give more detailed steps to reproduce. Did you copy from read mode, or from VE? Where exactly did you select, and where exactly did you paste?",1408196281,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","screenshot
+
+environment- test2, production, beta
+
+1> open page in VE, insert a comment.
+2> Open to edit the comment.
+3>Now click on the Text Style Menu and select  any style, for ex-Page Title or the Heading style.
+4> Notice the edit comment dialog turns blank.Please see screenshot.
+
+same behavior found in FF.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14201}",1407444600,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gynefzcsmqruipthvy7i,task_description,resolved
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".",Odd.,1418323355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","This seems fixed now. Cannot Reproduce it anymore.
+Also see [[ https://phabricator.wikimedia.org/T78308 | T78308 ]]",1418315428,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","In addition to my previous comment: the edit comment pop-up box changes its display(the comment that being edited is still displayed, not blanked out).",1413918002,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","Confirmed test2, Betalabs, production (FF, Chrome). The error is displayed as the following: 
+
+Uncaught Error: Cannot set attributes on closing element VM86:325
+ve.dm.Transaction.newFromAttributeChangesVM86:325

+(anonymous function)VM86:699

+(anonymous function)VM86:45

+OO.ui.Process.executeVM86:45

+OO.ui.Window.teardownVM86:31

+(anonymous function)",1413847966,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","Issue is reproducible and is related to Bug 70888.Please ses ""Screenshot 1.25wmf2"".",1412608380,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","Created attachment 16678
+Screenshot 1.25wmf2
+
+**Attached**: {F14202}",1412608303,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".",JS Console error- Uncaught TypeError:Cannot Read Property 'getSurface of null'.,1407446633,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,".
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1407261180,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mkys274ty5zb7zz3ixqh,task_description,resolved
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156494 merged by Catrope:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156494",1409102193,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156493 merged by jenkins-bot:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156493",1409102065,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156494 had a related patch set uploaded by Catrope:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156494",1409101958,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156493 had a related patch set uploaded by Catrope:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156493",1409101860,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156491 merged by jenkins-bot:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156491",1409101726,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156491 had a related patch set uploaded by Jforrester:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156491",1409101616,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**See also**
+* {T52512}
+* {T56140}",1407256980,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-i7jndqttvnweqczobiov,task_description,resolved
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","(In reply to JAn Dudík from comment #10)
+> really fixed?
+> https://cs.wikipedia.org/w/index.php?title=%C5%A0ablona:Infobox_-
+> _s%C3%ADdlo&diff=11940098&oldid=11761581
+
+It will be deployed to cswiki in a few hours…",1414081207,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","really fixed?
+https://cs.wikipedia.org/w/index.php?title=%C5%A0ablona:Infobox_-_s%C3%ADdlo&diff=11940098&oldid=11761581",1414068773,PHID-USER-wwnv7nzuscfuc2xfjwbq,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","Change 165908 merged by jenkins-bot:
+Add <noinclude> tags to new <templatedata> strings
+
+https://gerrit.wikimedia.org/r/165908",1412899303,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","Change 165908 had a related patch set uploaded by Mooeypoo:
+Add <noinclude> tags to new <templatedata> strings
+
+https://gerrit.wikimedia.org/r/165908",1412893139,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","(In reply to Alex Monk from comment #2)
+> Well how would we distinguish a documentation subpage from a ""proper""
+> template page?
+
+
+If the title has a ""/"" in it assume that it's OK to put in without <noinclude>s?",1412872641,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","This has caused a few problems on the en wiki. As I discuss at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=prev&oldid=628346583 it affected over 100 article space pages as anons and newer users have used the button and created template data blocks outside of <noinclude> tags. This then gets transcluded into main space articles. 
+
+Examples include
+ http://en.wikipedia.org/w/index.phptitle=Template:Roman_Catholic_Cathedrals_in_Great_Britain_and_Ireland&diff=prev&oldid=626352880 
+
+ http://en.wikipedia.org/w/index.php?title=Template:Punknews&diff=prev&oldid=628254485
+
+ http://en.wikipedia.org/w/index.phptitle=Template:List_of_Philippine_seas&diff=prev&oldid=625635816 
+
+ http://en.wikipedia.org/w/index.phptitle=Template:ABC_Mindanao&diff=prev&oldid=622140533 
+
+A list of page affect is at
+http://en.wikipedia.org/w/index.php?title=Wikipedia:TemplateData/List&oldid=628258871
+I've fixed all the current boken templates.",1412679935,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","I assume that the system would be essentially like this:
+
+* If the TemplateData is being added to Template:Foo, then add noinclude tags around it.
+* If the TemplateData is being added to Template:Foo/subpage, then check the name of the subpage.
+** If $local-variable is set, amd the subpage matches the local variable, then skip the noinclude tags.
+** If $local-variable is not set, and the subpage is $mw-default-subpage (which should be set to ""/doc""), then skip the noinclude tags.
+** Otherwise, assume the subpage is a real template and add noinclude tags.
+
+This means that the way it would work on some future Swahili Wikia is ""the local sysops would set the local variable"".  At the Swahili Wikipedia, local admins would set it to /hati (their preferred page name).
+
+If local sysops did not define the variable, and also didn't use the default subpage name, and someone added TemplateData to a documentation page that the extension treated as a real template, then it would get an ""extra"" set of noinclude tags (one that it adds and one that the doc page's transclusion adds).  I'm not sure that this would harm anything at all, but it's preseumably something to test.",1407276842,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","(In reply to WhatamIdoing from comment #3)
+> Otherwise, I think we'd have to make assumptions based on the page name. 
+> Different wikis use different names, but most use /doc (and/or one other
+> variant), and I've not yet seen an actual template subpage using those names.
+
+Okay, how do you plan for this to work on the ... Swahili Wikia? (if such a thing exists)",1407267571,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","It's possible that TemplateData could be noinclude'd no matter what. (Would nested noinclude tags cause problems?) 
+
+Otherwise, I think we'd have to make assumptions based on the page name.  Different wikis use different names, but most use /doc (and/or one other variant), and I've not yet seen an actual template subpage using those names.",1407262741,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","Well how would we distinguish a documentation subpage from a ""proper"" template page?",1407258044,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags",Maybe. I'd rather we just fix bug 54140 instead.,1407257674,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Go to the end of a line
+3.Press return to go the next line and click on link inspector or comment icon from the toolbar
+
+Observed Result:
+The link inspector and the comment box opens at the end of the previous line
+After adding a link or a comment it appears on the next line though.
+
+
+See the screenshot attached
+
+Environment:Betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14434}",1407184260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_description,resolved
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Got fixed with Ed's selection re-write I believe? I have not seen it happening recently too.Marking as fixed,1413931552,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Can't reproduce...,1413926325,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","(In reply to Rummana Yasmeen from comment #14)
+> This is again happening for both link inspector and comment box in Betalabs",1410816528,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",This is again happening for comment box in Betalabs,1410809568,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",*Verified the fix in production*,1410545461,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Verified the fix in Betalabs,1410545428,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Verified the fix in test2,1409872169,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Verified the fix in betalabs,1409856383,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Change 157868 merged by jenkins-bot:
+Don't use three different coordinate systems in getSelectionRect()
+
+https://gerrit.wikimedia.org/r/157868",1409789022,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Change 157868 had a related patch set uploaded by Catrope:
+Don't use three different coordinate systems in getSelectionRect()
+
+https://gerrit.wikimedia.org/r/157868",1409687356,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Created attachment 16282
+Screenshot
+
+This is still happening,the inspectors are now opening not at the end of previous line, but somewhere along the preceding 4/5 lines 
+
+See the screenshot attached, where I tried to add a link inside the bullet list and it appears at some position in page title.
+
+**Attached**: {F14435}",1409077912,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Change 155619 merged by jenkins-bot:
+Fallback to node position when getting selection rectangle
+
+https://gerrit.wikimedia.org/r/155619",1408652773,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Change 155619 had a related patch set uploaded by Esanders:
+Fallback to node position when getting selection rectangle
+
+https://gerrit.wikimedia.org/r/155619",1408651574,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Yeah, selection is going very wonky here.",1407953415,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Language inspector also behaves in the same way,1407355267,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Right Alex :) This bug is not for mobile VE but for desktop. Sorry about that!,1407262535,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","(In reply to Rummana Yasmeen from comment #0)
+> Created attachment 16137 [details]
+> Screenshot
+> 
+> Steps to reproduce:
+> 
+> 1.Open a page with mobile VE
+
+That screenshot does not appear to be from a mobile device...
+
+**Attached**: {F14434}",1407253023,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: In Betalabs,Media search is extremely slow, some images are not appearing and the progress bar keeps on moving infinitely","Screenshot
+
+Steps to reproduce:
+
+1.Open any page with VE
+2.Go to Insert>Media
+
+Observe that ,the progress bar is active on the text field and never stops
+If you retype the search string, the search results comes up but very slowly, some of the images are not even loading completely inside the dialog box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14212}",1406919000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wawq2es6xnwknziib6yf,task_description,resolved
+"VisualEditor: In Betalabs,Media search is extremely slow, some images are not appearing and the progress bar keeps on moving infinitely",Seems fine now.,1420843166,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wawq2es6xnwknziib6yf,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Happening on Betalabs and test2
+
+Cannot open the new comment box
+
+Getting following error in the console:
+TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406849160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k7yzoaid7tne2jeioxrh,task_description,resolved
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor",Verified the fix in production,1408654128,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor",Verified the fix in test2,1407275534,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor",*** Bug 69012 has been marked as a duplicate of this bug. ***,1406921057,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor",This was backported and deployed just now.,1406854389,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Change 150990 merged by jenkins-bot:
+Followup 23a949844: fix typo in class name for WhitespacePreservingInputWidget
+
+https://gerrit.wikimedia.org/r/150990",1406850776,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Change 150990 had a related patch set uploaded by Catrope:
+Followup 23a949844: fix typo in class name for WhitespacePreservingInputWidget
+
+https://gerrit.wikimedia.org/r/150990",1406850648,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Change 150989 merged by jenkins-bot:
+Followup 23a949844: fix typo in class name for WhitespacePreservingInputWidget
+
+https://gerrit.wikimedia.org/r/150989",1406850506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Change 150989 had a related patch set uploaded by Catrope:
+Followup 23a949844: fix typo in class name for WhitespacePreservingInputWidget
+
+https://gerrit.wikimedia.org/r/150989",1406850179,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+VisualEditor: Link inspector sets wrong title when clicking suggestion,"On enwiki:
+
+* Inspect an existing link
+* Type ""N"" in the text box
+* Click ""North America"" in the suggestions list
+* Click Done
+* Observe that the link now points to ""North American B-25 Mitchell""
+
+What seems to happen is:
+* you click North America
+* the textbox is changed to North America
+* a new suggestions list opens, with ""North America"" as the second item and ""North American B-25 Mitchell"" as the first
+* this closes again, setting the annotation to NAB25M while keeping the text as NA
+* when you click Done, the annotation is what's saved, not the text
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406829240,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ggojb6ctli2epykmy6k6,task_description,duplicate
+VisualEditor: Link inspector sets wrong title when clicking suggestion,"Still a dupe of bug 65343 :-)
+
+*** This bug has been marked as a duplicate of bug 65343 ***",1408668143,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ggojb6ctli2epykmy6k6,task_subcomment,NA
+VisualEditor: Link inspector sets wrong title when clicking suggestion,"Change 155673 had a related patch set uploaded by Trevor Parscal:
+Select the correct annotation in MWLinkTargetInputWidget
+
+https://gerrit.wikimedia.org/r/155673",1408666157,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ggojb6ctli2epykmy6k6,task_subcomment,NA
+VisualEditor: Link inspector sets wrong title when clicking suggestion,"
+
+*** This bug has been marked as a duplicate of bug 65343 ***",1408666007,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ggojb6ctli2epykmy6k6,task_subcomment,NA
+"VisualEditor: Triggering context on link after defocus throws ""TypeError: Cannot read property 'isCollapsed' of null""","1. Click on a link to show the context menu.
+2. Right click on the description of the link in the context menu (eg. name of page the link points to).
+3. Choose ""Inspect element"" which will defocus the page.
+4. Click on the link again, thus putting the cursor back in the page; somewhere in the linked word.
+
+After the context menu re-appears, a callback from AnnotagionInspector run via a OO.ui.Process throws:
+
+Uncaught TypeError: Cannot read property 'isCollapsed' of null 
+> ve.ui.AnnotationInspector.prototype.getSetupProcess = function () {
+>   ..
+>   .. fragment.getRange().isCollapsed()
+ (anonymous function) ve.ui.AnnotationInspector.js:159
+ (anonymous function) oojs-ui.js:3030
+ (anonymous function)
+ jQuery.extend.Deferred
+ promise.then
+ OO.ui.Process.execute oojs-ui.js:3067
+ OO.ui.Window.setup oojs-ui.js:1902
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406807880,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4fwj3nkikf5qqbm775b,task_description,declined
+"VisualEditor: Triggering context on link after defocus throws ""TypeError: Cannot read property 'isCollapsed' of null""",Can't reproduce.,1411594541,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4fwj3nkikf5qqbm775b,task_subcomment,NA
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","Shows that redirect page Save page (=Uložit stránku) is gray
+
+In this case, I am adding a template to the redirect page (delete template), but I cannot safe it. The safe button stay gray (attachment).
+
+Steps to reproduce this bug (Windows Vista, FF 31.0):
+1) open https://cs.wikipedia.org/w/index.php?title=Cristina_Fern%C3%A1ndez_de_Kirchner&redirect=no
+2) click on Edit
+3) Cencel options
+4) Insert > Template > Smazat (Add more information: 1; randoom text) > Insert template
+5) Save page = but you cannot!
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14552}",1406789640,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-5frqhlvurysfjreie4jc,task_description,resolved
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","Change 150772 merged by jenkins-bot:
+ve.ui.MWMetaDialog: Really *ALWAYS* return to normal tracking behavior
+
+https://gerrit.wikimedia.org/r/150772",1406793089,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5frqhlvurysfjreie4jc,task_subcomment,NA
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","Change 150772 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ui.MWMetaDialog: Really *ALWAYS* return to normal tracking behavior
+
+https://gerrit.wikimedia.org/r/150772",1406791818,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5frqhlvurysfjreie4jc,task_subcomment,NA
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","It gets better: the state of the 'Save' button stops being updated always when you open the ""Options"" dialog and cancel it instead of applying.",1406791707,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5frqhlvurysfjreie4jc,task_subcomment,NA
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","Indeed.
+
+In step 4), it also suffices to just input any text – the ""Save"" button doesn't become enabled.
+
+However, if in step 3) you click ""Apply changes"" rather than ""Cancel"", everything works correctly.",1406790437,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5frqhlvurysfjreie4jc,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,"If an exception occurs while processing a transaction, we should roll it back safely, so the converter will still work and the user can still save or bail to source mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406768880,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_description,resolved
+Make VisualEditor transaction processing exception-safe,"Change 195361 merged by jenkins-bot:
+Make transaction processing exception-safe
+
+[[https://gerrit.wikimedia.org/r/195361]]",1426005844,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,"Change 195361 had a related patch set uploaded (by Catrope):
+Make transaction processing exception-safe
+
+[[https://gerrit.wikimedia.org/r/195361]]
+",1425933123,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,Operations are now queued but exceptions aren't caught yet.,1408586978,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,"Change 152776 merged by jenkins-bot:
+Queue up annotation changes to make operations safer
+
+https://gerrit.wikimedia.org/r/152776",1408586301,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,"Change 152776 had a related patch set uploaded by Jforrester:
+Queue up annotation changes to make operations safer
+
+https://gerrit.wikimedia.org/r/152776",1407796877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+VisualEditor: MWReferenceSearchWidget should only build the index if there isn't one or if it was built against a different version of the internal list,"Right now we build it blindly every time, which is inefficient. Can we listen to the internal list or get its hash or something so that we don't have to re-build except if a reference is added, removed or altered?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406766720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ihbbvcuqsgulvmjyinx7,task_description,resolved
+VisualEditor: MWReferenceSearchWidget should only build the index if there isn't one or if it was built against a different version of the internal list,"Change 151234 merged by jenkins-bot:
+Only build reference search index when it's been changed
+
+https://gerrit.wikimedia.org/r/151234",1408586168,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ihbbvcuqsgulvmjyinx7,task_subcomment,NA
+VisualEditor: MWReferenceSearchWidget should only build the index if there isn't one or if it was built against a different version of the internal list,"Change 151234 had a related patch set uploaded by Alex Monk:
+Only build reference search index when it's been changed
+
+https://gerrit.wikimedia.org/r/151234",1406932894,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ihbbvcuqsgulvmjyinx7,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add a reference (Basic/Citation)
+3.Check Re-use existing reference dialog (The reference appears in the dialog though the reference name is missing which is a different bug:https://bugzilla.wikimedia.org/show_bug.cgi?id=67342)
+4.Now add some citation/basic references 
+5.Check re-use existing reference dialog again
+
+Observed Result:
+Except the first one , none of the newly added references are appearing in the use existing dialog
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67342
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68582",1406743800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lhmoss6srr2f2jmg2mip,task_description,resolved
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,Verified the fix in production,1408048491,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,Verified the fix in test2,1407192079,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,"Change 150711 merged by jenkins-bot:
+Follow-up I569098: Rebuild reference list when reopening as it can change
+
+https://gerrit.wikimedia.org/r/150711",1406767181,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,"Change 150711 had a related patch set uploaded by Alex Monk:
+Don't refuse to rebuild reference list when reopening re-using existing citation widget
+
+https://gerrit.wikimedia.org/r/150711",1406758069,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,"Could it be that the list of references in the ""Use existing"" panel is just never cleared?",1406747192,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Place the cursor somewhere at the top of the page
+3.When the cursor is active on Ce and the keyboard is open, try scrolling down the page
+
+Observe dResult:
+Scrolling does not work
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406678220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aimwlbodlnjas75xvos2,task_description,resolved
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,Verified the fix for original issue in production.,1409866102,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"This seems to still be broken-ish due to bug 68832, which means you can't scroll all the way up to reveal the toolbar, but scrolling down works.
+
+Closing this one, we'll track the remaining problems over at bug 68832.",1409163669,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,This issue did not get resolved with the revert,1406765731,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"**jgonera** wrote:
+
+Should be fixed by https://gerrit.wikimedia.org/r/#/c/150719/",1406761757,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"This is happening now but following a different steps to reproduce:
+1.Open a page with Mobile VE
+2.Open link inspector
+3.Click on the ""Done"" button
+4.Once you are back to CE, tap on it to activate the cursor
+5.Now try scrolling up/down
+
+The scrolling wont work",1406753749,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"Reopening it again,since I just reproduced it.",1406752883,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,Beta Labs gremlins.,1406748295,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,This is also happening while scrolling down the link suggestions inside link inspector.,1406679123,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"This is an apparent separate bug discovered in the course of bug 67805.
+
+Niklas suggested, ""LC issue is possibly caused by incorrect fallback merging, because L10nupdate contains update for ru, but not for uk (because the translation is already up to date for uk):""
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67805
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70686",1406604120,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-x6dj767aouujxepwm3oj,task_description,resolved
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"I think it's safe to mark this fixed now, although we still have to force-update all the l10n caches to make sure brokenness doesn't stay cached somewhere. Reedy says on IRC that he'll do that once he finishes the train deploy that's going on right now.",1409854129,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158423 merged by jenkins-bot:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158423",1409853304,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158421 merged by jenkins-bot:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158421",1409853199,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158422 merged by jenkins-bot:
+Use new LocalisationCacheRecacheFallback hook
+
+https://gerrit.wikimedia.org/r/158422",1409852370,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158423 had a related patch set uploaded by Reedy:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158423",1409852101,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158422 had a related patch set uploaded by Reedy:
+Use new LocalisationCacheRecacheFallback hook
+
+https://gerrit.wikimedia.org/r/158422",1409852064,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158421 had a related patch set uploaded by Reedy:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158421",1409852045,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),Now theoretically FIXED (once the code is deployed)?,1409851766,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158146 merged by jenkins-bot:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158146",1409850946,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158147 merged by jenkins-bot:
+Use new LocalisationCacheRecacheFallback hook
+
+https://gerrit.wikimedia.org/r/158147",1409842361,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"The problem is over-optimization: in LocalisationUpdate you're storing only the changed messages for each language, but that's causing problems when the current language doesn't have a change but a fallback language does. We've had this bug before, and it was worked around in r104041.
+
+Rather than doing the same thing as r104041 again and having this recur again the next time someone tries to optimize things, let's really fix it: LocalisationUpdate needs a hook to call for each fallback before it's merged into the final array, rather than one hook after we've already lost the information as to which language each message came from. But to do that, we have to rearrange the processing in LocalisationCache so it accumulates the data for each fallback language",1409768324,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158147 had a related patch set uploaded by Anomie:
+Use new LocalisationCacheRecacheFallback hook
+
+https://gerrit.wikimedia.org/r/158147",1409768303,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158146 had a related patch set uploaded by Anomie:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158146",1409768287,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"(In reply to Nemo from comment #5)
+> https://git.wikimedia.org/blob/mediawiki%2Ftools%2Fscap.git/HEAD/
+> bin%2FrefreshCdbJsonFiles (authors Bryan and Antoine, AFAICS).
+
+Yeah, I asked them. They said they didn't know anything about the actual generation of the json stuff.
+
+(In reply to Niklas Laxström from comment #6)
+> To clarify, are we talking about the json created by LocalisationUpdate
+> (which are then included in the CDB files by LocalisationCache), or the json
+> files created from the CDB files by the deployment scripts for efficient
+> syncing?
+
+There's two different json files? I'm glad I asked for help: I didn't know that it generated json files for the updated messages, then built cdbs, then generated more json files from the cdbs, and then generated cdbs again from the json files.
+
+I was referring to the json files that are created from the cdbs and then used to recreate the cdbs. Now that I know better how things work, I'm digging further into it.",1409755181,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"To clarify, are we talking about the json created by LocalisationUpdate (which are then included in the CDB files by LocalisationCache), or the json files created from the CDB files by the deployment scripts for efficient syncing?",1409722719,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"(In reply to Brad Jorsch from comment #4)
+> point to
+> who knows anything about the json-generating code.
+
+https://git.wikimedia.org/blob/mediawiki%2Ftools%2Fscap.git/HEAD/bin%2FrefreshCdbJsonFiles (authors Bryan and Antoine, AFAICS).",1409721483,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"(In reply to Greg Grossmeier from comment #3)
+> Niklas: Can you give any pointers to Brad to help him get up to speed on
+> this?
+
+More specifically, I tracked the problem down as far as ""the .json files are wrong"". When I asked around, you were the only person anyone could point to who knows anything about the json-generating code. Where do I find this code? If it's not going to be obvious, how generally does that code work? Is there a known way to run just the json-generator and output files to some temporary directory?",1409696180,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),Niklas: Can you give any pointers to Brad to help him get up to speed on this?,1409693137,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"(In reply to Brad Jorsch from comment #1)
+> So the problem seems to be in the (new JSON-based) l10nupdate process.
+
+Moving to ""Deployment systems""; feel free to move back.",1406714586,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Further detail from bug 67805: ""I tracked that one as far as observing that the json file for uk that the cdb file gets built from has ""Править вики-текст"" as the value for messages:visualeditor-ca-editsource rather than ""Редагувати код"".""
+
+So the problem seems to be in the (new JSON-based) l10nupdate process.",1406633212,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","screenshot
+
+Environment- test2
+
+Steps-
+1>1> Open a blank page in VE and type in some text.
+2>At the end of the text insert a comment.
+3>Click on the Comment , to open the comment edit dialog.
+4> Now while the cursor is still in the comment edit dialog , click to insert a Template.
+5> As you start typing, add any template from the list that shows likely matches. For Example -select the “Bar” template.
+6>Type in Field name and insert the template.
+7>Notice the template does get added and then a snowman like character gets triggered after it.
+
+Behavior found in Chrome,FF and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14172}",1406561340,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-aezkk3hojhat5t2zwuar,task_description,resolved
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","In FF, the highlight seems to mask the comment icon.See screenshot_FF.",1406919511,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Created attachment 16120
+screenshot_FF
+
+**Attached**: {F14173}",1406919391,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.",Issue fixed in beta and test2,1406751259,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.",Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660968,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659011,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658995,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658725,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656776,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646170,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646101,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645965,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645939,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645501,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645467,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630082,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594988,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 149920 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406573312,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","confirmed in betalabs. Try the template ""Bar chart""",1406562568,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"If a paragraph contains a template, and VisualEditor is used to insert two characters somewhere after the template, and the second character is deleted with backspace, then the first character will be replaced by another character that is duplicated from several positions before that character.
+
+To reproduce, go to 
+
+https://en.wikipedia.org/w/index.php?title=User:AxelBoldt/Sandbox&oldid=618813650&veaction=edit
+
+and change the word ""Italian"" in the first sentence to ""Itaxxlian"", then delete the second x. Result: ""Itatlian"", where the second ""t"" results from duplication of the first ""t"". 
+
+This is a consequence of the IPA template earlier in the paragraph. The test file also contains a paragraph without template, where the bug does not occur, and a paragraph with a convert template, where the bug does occur.
+
+Wikipedia is at MW 1.24wmf15 and I'm on Windows 7 running Chrome 36.0.1985.125 m.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406552880,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_description,resolved
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660962,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),*** Bug 68789 has been marked as a duplicate of this bug. ***,1406659236,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658990,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658737,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656754,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646179,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646103,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645963,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645919,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645495,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645487,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630079,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594979,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 149920 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406573584,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"The effect seems to occur whenever you insert two or more characters in a paragraph after a template and then delete any one of them. The inserted characters do not have to be contiguous. The distance between first inserted character and duplicated character depends on the template.
+
+I believe VE internally uses the length of the unexpanded template where it should use the length of the expanded template.",1406567960,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Yeah, this looks a bit like bug 67862 but less severe.",1406566263,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),Maybe related: bug 67862?,1406553462,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+"VisualEditor: Remove media or templates, page loses focus","Take any article long enough to notice the effect (i.e. Cake on en.wp).
+Delete any of the pics at the bottom of the article.
+Notice the focus jumps back at the top.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58038
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68589",1406531520,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sz5lbvh7j7kau3kukcw2,task_description,resolved
+"VisualEditor: Remove media or templates, page loses focus","Change 151400 merged by jenkins-bot:
+Set selection before focusing document
+
+https://gerrit.wikimedia.org/r/151400",1407065073,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sz5lbvh7j7kau3kukcw2,task_subcomment,NA
+"VisualEditor: Remove media or templates, page loses focus","Change 151400 had a related patch set uploaded by Jforrester:
+Set selection before focusing document
+
+https://gerrit.wikimedia.org/r/151400",1407064970,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sz5lbvh7j7kau3kukcw2,task_subcomment,NA
+"VisualEditor: Remove media or templates, page loses focus","It also happens with templates, so I'm guessing this is probably worrying but maybe a duplicate.",1406542869,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sz5lbvh7j7kau3kukcw2,task_subcomment,NA
+VisualEditor: Weird behavior around a wikilink,"1) VEdit https://fr.wikipedia.org/wiki/Marie_Coutant?veaction=edit .
+
+2) Reach the end of the second paragraph, find the word Métivier.
+
+3) Start typing right before the ""M"" or after the ""r"". Pawns appear and random letters can appear in the word. Click on the word again, and watch letters and pawns multiply.
+
+4) Abandon the edit, go back to step 1 and 2.
+
+5) Add an ""h"" after the ""t"": Méthivier.
+
+6) Enter the link tool and click Supprimer to suppress the link.
+
+7) Notice the ""h"" has become an ""é"": Météivier. This is just an example, you can get different results adding other letters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406451840,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-y5us6kajeyeryt5odbuu,task_description,resolved
+VisualEditor: Weird behavior around a wikilink,I think this was caused by the pawning/snowmen issue that we fixed and pushed to production yesterday.,1406754678,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y5us6kajeyeryt5odbuu,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"1. Create a document with two paragraphs, and make both of them entirely bold
+2. Put the cursor at the beginning of the first paragraph, and type a character. This character will be bold
+3. Put the cursor at the beginning of the second paragraph, and type a character. This character will not be bold
+
+#2 and #3 should be consistent. In fact, #2 *only* happens at the very start of the document, #3 happens everywhere else.
+
+The reason this is broken is that the code computing the new insertionAnnotations in ve.dm.Surface#setSelection by pulling from the left does not take paragraph boundaries into account at all. In case #3, it tries to pull from the left across the paragraph boundary, but because getAnnotationsFromOffset() doesn't work the way it thinks it does (the offset at the end of the first paragraph is a content offset, but getting its annotations returns an empty set) that doesn't work, and so text inserted at the beginning of this paragraph is not annotated. However, at the very start, the getRelativeContentOffset() call that computes the offset to the left bounces back and returns the offset to the right instead (1), so left === right, and we end up pulling from the right and bolding the inserted text.
+
+So really, the code is trying to achieve the wrong behavior (#2), but in most cases that breaks and we end up with the right behavior (#3). So the correct behavior is achieved completely by accident, except in one edge case where the code successfully achieves the wrong behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406337660,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ijstbrdms7lza5yyddte,task_description,resolved
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 155260 merged by jenkins-bot:
+Fix check for left/right annotations
+
+https://gerrit.wikimedia.org/r/155260",1408557331,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 150378 abandoned by Catrope:
+Fix pulling of annotations when typing at the beginning of the document
+
+Reason:
+https://gerrit.wikimedia.org/r/155260 fixes this bug
+
+https://gerrit.wikimedia.org/r/150378",1408557179,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 155260 had a related patch set uploaded by Catrope:
+Fix check for left/right annotations
+
+https://gerrit.wikimedia.org/r/155260",1408557160,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 150378 had a related patch set uploaded by Alex Monk:
+[WIP] Fix pulling of annotations when typing at the beginning of the document
+
+https://gerrit.wikimedia.org/r/150378",1406665375,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 150120 abandoned by Alex Monk:
+Fix pulling of annotations when inserting new character at start of document
+
+Reason:
+Breaks other things.
+
+https://gerrit.wikimedia.org/r/150120",1406665080,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 150120 had a related patch set uploaded by Alex Monk:
+Fix pulling of annotations when inserting new character at start of document
+
+https://gerrit.wikimedia.org/r/150120",1406598969,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+"VisualEditor: Putting cursor after reference list throws ""offset was inside a handlesOwnChildren node"" error","Steps:
+
+1. Open http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+2. Scroll to bottom
+3. Place cursor in slug between gallery and references list
+4. Cursor right twice
+
+Expected outcome: Cursor ends up in slug at end of the page after the references list
+
+Actual outcome: Error thrown: ""offset was inside a handlesOwnChildren node""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit",1406321880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zwrntrbhezfc6nqksazy,task_description,resolved
+"VisualEditor: Putting cursor after reference list throws ""offset was inside a handlesOwnChildren node"" error","Change 155260 merged by jenkins-bot:
+Fix check for left/right annotations
+
+https://gerrit.wikimedia.org/r/155260",1408557334,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zwrntrbhezfc6nqksazy,task_subcomment,NA
+"VisualEditor: Putting cursor after reference list throws ""offset was inside a handlesOwnChildren node"" error","Change 155260 had a related patch set uploaded by Esanders:
+Fix check for left/right annotations
+
+https://gerrit.wikimedia.org/r/155260",1408542960,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zwrntrbhezfc6nqksazy,task_subcomment,NA
+"VisualEditor: Putting cursor after reference list throws ""offset was inside a handlesOwnChildren node"" error","This doesn't seem to be related to focusable nodes or the end of the document. All you need to do is put the cursor in a block slug after a references list.
+
+Suppose the references list is at (23,25). What happens is this:
+* setSelection (25,25) is called
+* It tries to compute insertion annotations by pulling from the left
+* It does so by calling getNearestContentOffset( 24, -1 )
+* Two stack levels deeper, getRelativeOffset() notices that 24 is inside of a handlesOwnChildren node and throws an exception
+
+Questions:
+* Why is reference list a handlesOwnChildren node? Is it because <ref> can be nested inside of <references>?
+* Why do we do offset-1 here? There is a Math.max() to guard against ending up at -1, but this bug uncovers another reason why subtracting one from an offset is dangerous and should ideally never be done",1406575296,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zwrntrbhezfc6nqksazy,task_subcomment,NA
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,"VE get stucks when saving settings
+
+How to reproduce:
+1) click ""Options"" and then ""cancel""
+2) click ""Advanced settings"" and then ""apply changes""
+
+After this it gets stuck. It's ""applying changes"" even if you didn't do any changes. You must reload the page to make your changes again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406298300,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-xlnqf77fujlvuvwewshn,task_description,resolved
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,"Yes, this is fixed in wmf15 (as on MediaWiki.org right now) but not in wmf14 (on enwiki etc.).",1406307422,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xlnqf77fujlvuvwewshn,task_subcomment,NA
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,I think Ed fixed this in Gerrit change 148671,1406302133,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-xlnqf77fujlvuvwewshn,task_subcomment,NA
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,"(In reply to Alex Monk from comment #1)
+> Can't reproduce this issue.
+> 
+> Stryn, do you get an error in the JS console when this happens?
+
+Yup, with Firefox and Chrome
+
+Firefox gives:
+TypeError: bindings[i] is undefined load.php:608
+
+and Chrome:
+Uncaught TypeError: Cannot read property 'context' of undefined VM51:8oo.EventEmitter.disconnect VM51:8ve.ui.MWCategoriesPage.teardown VM53:224(anonymous function) VM53:229(anonymous function) VM51:42OO.ui.Process.execute VM51:43OO.ui.Dialog.executeAction VM51:33OO.ui.ProcessDialog.executeAction VM51:74OO.ui.Dialog.onActionClick VM51:31oo.EventEmitter.emit VM51:7oo.EventEmitter.emit VM51:7OO.ui.ButtonWidget.onClick VM51:102proxy load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20140724T1…:6jQuery.event.dispatch load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20140724T1…:65elemData.handle",1406302013,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-xlnqf77fujlvuvwewshn,task_subcomment,NA
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,"Can't reproduce this issue.
+
+Stryn, do you get an error in the JS console when this happens?",1406298858,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-xlnqf77fujlvuvwewshn,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","screenshot
+
+Test Environment-test2 and betalabs
+Steps-
+1> open a blank page in VE.
+2>type some text and at the end of the last character (could be a space after the text or the last character in the text itself) insert a comment.
+3>Now click to move the cursor after the comment, this closes the comment dialog too.
+4> Insert a whitespace.I cannot see the cursor at this point.
+5> click on the page again and the cursor appears before the start of the line. 
+6>Hit the spacebar and then press backspace key. A pawn appears next to the comment. Please see screenshot_chrome.
+
+In Safari-
+Try the same steps and at step#6 I get the WebKit2WebProcess.exe  dialog saying “WebKit2WebProcess.exe has encountered a problem and needs to close.”. After I click to send the error report and I get logged out of my account. 
+
+In FF 31- no issues were found when whitespace was inserted after a comment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14311}",1406242920,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-yz4c2eic4amw552h2kwd,task_description,resolved
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","(In reply to James Forrester from comment #9)
+> (In reply to Ritu Swain from comment #8)
+> > thank you. just for future.. this is not the right forum ..
+> 
+> No problem. :-)
+> 
+> > but how can i find the  release version of beta?
+> 
+> Unhelpfully, it's not present of beta (because it doesn't exist yet), but
+> the specific version of VisualEditor can be found inside VE itself:
+> 
+> If you go to a page and enter VisualEditor, click on the help menu – ""(?)""
+> in the toolbar on the right (left if RTL). The version hash will be at the
+> bottom of the menu.
+> 
+> mediawiki.org is currently running ""Version ce427f4 18:49, 29 July 2014"".
+> 
+> en.wikipedia.beta.wmflabs.org is currently running ""Version 3dd63f7 20:00,
+> 30 July 2014"".
+> 
+> > if a bug is not reproducible in beta , but it is in test2 , then can it be
+> > called fixed?
+> 
+> Normally, as long as we think it's actually fixed. Sometimes other changes
+> can have ripple effects, but sometimes it's caused by the local wiki's
+> configuration (or something else), so it's not a perfect call each time,
+> sadly.
+
+thank you :)",1406755410,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","(In reply to Ritu Swain from comment #8)
+> thank you. just for future.. this is not the right forum ..
+
+No problem. :-)
+
+> but how can i find the  release version of beta?
+
+Unhelpfully, it's not present of beta (because it doesn't exist yet), but the specific version of VisualEditor can be found inside VE itself:
+
+If you go to a page and enter VisualEditor, click on the help menu – ""(?)"" in the toolbar on the right (left if RTL). The version hash will be at the bottom of the menu.
+
+mediawiki.org is currently running ""Version ce427f4 18:49, 29 July 2014"".
+
+en.wikipedia.beta.wmflabs.org is currently running ""Version 3dd63f7 20:00, 30 July 2014"".
+
+> if a bug is not reproducible in beta , but it is in test2 , then can it be
+> called fixed?
+
+Normally, as long as we think it's actually fixed. Sometimes other changes can have ripple effects, but sometimes it's caused by the local wiki's configuration (or something else), so it's not a perfect call each time, sadly.",1406752805,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","thank you. just for future.. this is not the right forum .. but how can i find the  release version of beta?
+
+if a bug is not reproducible in beta , but it is in test2 , then can it be called fixed?",1406750788,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","Sorry, yes, I meant wmf16. My apologies!",1406749936,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","(In reply to James Forrester from comment #5)
+> Sounds like it was fixed in wmf15 then.
+
+a bit confused, i can reproduce it in test2 with the release version  1.24wmf15 (148011a).",1406749890,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.",Sounds like it was fixed in wmf15 then.,1406653811,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","(In reply to Alex Monk from comment #3)
+> I can't reproduce this now, Roan couldn't either. Ritu, does this still
+> happen for you?
+
+I can reproduce it in test2 , but not in beta.",1406652638,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","I can't reproduce this now, Roan couldn't either. Ritu, does this still happen for you?",1406579105,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.",Confirmed,1406314736,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","did a fresh install of Safari, still getting WebKit2WebProcess.exe message.",1406260958,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Page Settings option>Categories
+3.Try to add categories 
+
+Observed Result:
+After typing into a category name, it getting added twice and trying again throws error:
+
+TypeError: categoryItem is undefined 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14192}",1406155680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hixyotclnt74wvydoglc,task_description,resolved
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Verified the fix in production,1408653602,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Verified the fix in test2,1408051414,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Hmm, I can't either. Marking it as fixed.",1407349730,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",And I can't reproduce it on deployment-prep any more. Rummana?,1407323599,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Also, I am getting a different error this time while closing the dialog second time:
+Uncaught TypeError: Cannot read property 'disconnect' of undefined",1407276641,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Can now successfully reproduce on deployment-prep, but not my local wiki...",1407273736,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",This is still happening on Betalabs,1407267273,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Silly Gerrit.,1407262706,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Change 151088 merged by jenkins-bot:
+Tear down meta dialog pages when cancelling
+
+https://gerrit.wikimedia.org/r/151088",1407262656,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","The patch is not even merged yet, assuming the bug was closed by mistake.",1407261384,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Change 151088 had a related patch set uploaded by Alex Monk:
+Tear down meta dialog pages when cancelling
+
+https://gerrit.wikimedia.org/r/151088",1406904459,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Reproduced it today following these steps
+
+1.Open a page with VE
+2.Go to Page Settings option>Categories
+3.Type a category name in the text field
+4.When the drop down box appears, close the dialog
+5.Again, reopen the Page Settings option>Categories
+6.Now select a category from the drop down box
+
+Observed Result:
+
+It gets added twice,if you cancel the dialog box again it will throw the error:
+TypeError: categoryItem is undefined 
+
+If you reopen the Page Settings option>Categories, you will get stuck inside it.",1406850704,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Seems to be working again. Probably a deployment gremlin. Again. :-(,1406320458,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Can't reproduce...,1406314616,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+Upgrade gerrit to 2.12,"Please upgrade gerrit to 2.12.
+
+Following plugins needs to be tested and fixed in the new version (and blocks an upgrade):
+
+```
+its-phabricator	2.8.1	Enabled
+its-phabricator-from-bugzilla	2.8.1	Enabled
+github-create-1.0-rc0	1.0-rc0	Enabled
+deleteproject	2.8.1	Enabled
+```
+
+Release notes for 2.12 are at https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.12.html
+
+--------------------------
+See Also: T65847",1405777980,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_description,resolved
+Upgrade gerrit to 2.12,"Change 300815 abandoned by Chad:
+TESTING STUFF
+
+Reason:
+Yay stuff works now.
+
+[[https://gerrit.wikimedia.org/r/300815]]",1469459058,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300815 had a related patch set uploaded (by Chad):
+TESTING STUFF
+
+[[https://gerrit.wikimedia.org/r/300815]]
+",1469458877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"```
+2016-07-25
+
+    03:26 hashar: scandium: migrating zuul-merger repos from lead to gerrit.wikimedia.org: find /srv/ssd/zuul/git -path '*/.git/config' -print -execdir sed -i -e 's/lead.wikimedia.org/gerrit.wikimedia.org/' config \;
+    02:03 ostriches: gerrit: reindexing lucene now that we have new data. searches/dashboards may look a tad weird for a bit
+    01:53 hashar: starting Zuul
+    01:51 mutante: restarted grrrit-wm
+    01:39 ostriches: lead: turning puppet back on, here we go
+    01:38 jynus: m2 replication on db2011 stopped, master binlog pos: db1020-bin.000968:1013334195
+    01:37 hashar: scandium: restarted zuul-merger
+    01:36 ostriches: ytterbium: Stopped puppet, stopped gerrit process.
+    01:34 mutante: switched gerrit-new to gerrit in DNS
+    01:30 ostriches: lead: stopped puppet for a few minutes
+    01:17 hashar: scandium: migrating zuul-merger repos to lead find /srv/ssd/zuul/git -path '*/.git/config' -print -execdir sed -i -e 's/ytterbium.wikimedia.org/lead.wikimedia.org/' config \;
+    01:10 hashar: stopping CI
+    01:09 jynus: reviewdb backup finished, available on db1020:/srv/tmp/2016-07-25_00-54-31/
+    01:02 ostriches: rsyncing latest git data from ytterbium to lead
+    00:57 mutante: manually deleted reviewer-counts cron from gerrit2 user, runs as root and puppet does not remove crons unless ensure=>absent
+    00:55 jynus: starting hot backup of db1020's reviewdb
+```",1469428542,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"2016-07-25
+
+    03:26 hashar: scandium: migrating zuul-merger repos from lead to gerrit.wikimedia.org: find /srv/ssd/zuul/git -path '*/.git/config' -print -execdir sed -i -e 's/lead.wikimedia.org/gerrit.wikimedia.org/' config \;
+
+    02:03 ostriches: gerrit: reindexing lucene now that we have new data. searches/dashboards may look a tad weird for a bit
+    01:53 hashar: starting Zuul
+    01:51 mutante: restarted grrrit-wm
+    01:39 ostriches: lead: turning puppet back on, here we go
+    01:38 jynus: m2 replication on db2011 stopped, master binlog pos: db1020-bin.000968:1013334195
+    01:37 hashar: scandium: restarted zuul-merger
+    01:36 ostriches: ytterbium: Stopped puppet, stopped gerrit process.
+    01:34 mutante: switched gerrit-new to gerrit in DNS
+    01:30 ostriches: lead: stopped puppet for a few minutes
+    01:17 hashar: scandium: migrating zuul-merger repos to lead find /srv/ssd/zuul/git -path '*/.git/config' -print -execdir sed -i -e 's/ytterbium.wikimedia.org/lead.wikimedia.org/' config \;
+    01:10 hashar: stopping CI
+    01:09 jynus: reviewdb backup finished, available on db1020:/srv/tmp/2016-07-25_00-54-31/
+    01:02 ostriches: rsyncing latest git data from ytterbium to lead
+    00:57 mutante: manually deleted reviewer-counts cron from gerrit2 user, runs as root and puppet does not remove crons unless ensure=>absent
+    00:55 jynus: starting hot backup of db1020's reviewdb",1469428480,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300660 abandoned by Dzahn:
+switch gerrit-new to gerrit
+
+Reason:
+duplicate of https://gerrit.wikimedia.org/r/#/c/299007/
+
+[[https://gerrit.wikimedia.org/r/300660]]",1469222038,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300660 had a related patch set uploaded (by Dzahn):
+switch gerrit-new to gerrit
+
+[[https://gerrit.wikimedia.org/r/300660]]
+",1469221691,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300657 merged by Dzahn:
+gerrit: lower TTLs to 600
+
+[[https://gerrit.wikimedia.org/r/300657]]",1469221452,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300657 had a related patch set uploaded (by Dzahn):
+gerrit: lower TTLs to 600
+
+[[https://gerrit.wikimedia.org/r/300657]]
+",1469220934,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"> Yeah I know these hours weren't ideal for you, but I'm pretty sure from our testing that things will be ok. And ""broken CI"" is a condition for rolling things back.
+
+There is never a good time.  I should be to make a personal arrangement to show up without waking up the whole house!",1469118627,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2483146, @hashar wrote:
+> We would want to keep the ssh host fingerprint for the Gerrit embedded SSH daemon.  If it changes bunch of bots will stop until manually accepted.
+> 
+
+This has been done. I'll get it done in puppet too so we don't miss it next time.
+
+> 1am-4am UTC turns to 3am-7am CET, I can't reasonably work from home at those hours. not much opportunity until 6:30am UTC at best.
+> 
+> Then it is very low traffic at those hours, so I guess we can afford to have CI potentially broken somehow for a few hours.
+
+Yeah I know these hours weren't ideal for you, but I'm pretty sure from our testing that things will be ok. And ""broken CI"" is a condition for rolling things back.",1469109627,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"We would want to keep the ssh host fingerprint for the Gerrit embedded SSH daemon.  If it changes bunch of bots will stop until manually accepted.
+
+1am-4am UTC turns to 3am-7am CET, I can't reasonably work from home at those hours. not much opportunity until 6:30am UTC at best.
+
+Then it is very low traffic at those hours, so I guess we can afford to have CI potentially broken somehow for a few hours.",1469097294,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,@demon Sounds sane! :) Thanks for your work and the work of any other one involved so far :),1469083795,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Sounds good to me. I can be there Sunday night Pacific time. ,1469058840,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+# Decide/announce a window (ASAP, no time is good though)
+# Stop puppet on `lead`
+# Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+4) Run puppet one last time on `ytterbium`, stop puppet, stop Gerrit processes
+# Do a last snapshot of the Gerrit database, in case we have to roll back
+# Enable & run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing), Gerrit will restart) 
+# Run puppet for zuul nodes (restart zuul w/ new config)
+# Verify installation
+# Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+# Stop puppet on lead, turn off gerrit
+# Restore database to snapshat that we did prior to downtime
+# Revert puppet/DNS change from above ^^
+# Restart puppet and gerrit on `ytterbium` and `lead`
+# Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056818,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+# Decide/announce a window (ASAP, no time is good though)
+# Stop puppet on `lead`
+# Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+4) Run puppet one last time on `ytterbium`, stop puppet, stop Gerrit processes
+# Do a last snapshot of the Gerrit database, in case we have to roll back
+# Enable & run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing), Gerrit will restart) 
+# Run puppet for zuul nodes (restart zuul w/ new config)
+# Verify installation
+# Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056661,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+3) Run puppet one last time on `ytterbium`, stop puppet, stop Gerrit processes
+4) Do a last snapshot of the Gerrit database, in case we have to roll back
+6) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing), gerrit will restart
+7) Run puppet for zuul nodes (restart zuul w/ new config)
+9) Verify installation
+9) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056574,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+3) Run puppet one last time on `ytterbium`, stop puppet on, stop Gerrit processes
+4) Do a last snapshot of the Gerrit database, in case we have to roll back
+6) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing), gerrit will restart
+7) Run puppet for zuul nodes (restart zuul w/ new config)
+9) Verify installation
+9) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056558,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Run puppet for zuul nodes (restart zuul w/ new config)
+7) Verify installation
+8) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056243,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Run puppet for zuul nodes, restart
+7) Verify installation
+8) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056222,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Upgrade zuul, restart
+7) Verify installation
+8) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469054311,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"@MoritzMuehlenhoff Gerrit should show a little orange bubble near the ""Parent(s)"" section of the commit information, which indicates, that the parent isn't the latest one (which normally allows you to rebase). See this example:
+{F4271015}
+
+Merge conflicts (the current ""Can merge: No"" section), btw., is now a string with a red font in the change information box:
+{F4271027}",1468445225,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2456703, @demon wrote:
+>>>! In T70271#2456522, @AlexMonk-WMF wrote:
+>> I don't think the VE backport submodule update issue has been fixed :/
+>> I made https://gerrit-new.wikimedia.org/r/#/c/298010/ but it doesn't look like the submodule update showed up against mediawiki/core.git's wmf/1.28.0-wmf.1 branch
+> 
+> It probably will require a manual fix in the database where the old registration took place. Check with `gsql`?
+
+```gerrit> select * from submodule_subscriptions where submodule_path like '%VisualEditor%' and submodule_branch_name = 'refs/heads/wmf/1.28.0-wmf.1';
+ submodule_project_name | submodule_branch_name       | super_project_project_name | super_project_branch_name   | submodule_path
+ -----------------------+-----------------------------+----------------------------+-----------------------------+------------------------
+ VisualEditor           | refs/heads/wmf/1.28.0-wmf.1 | mediawiki/core             | refs/heads/wmf/1.28.0-wmf.1 | extensions/VisualEditor
+(1 row; 18 ms)```",1468423995,PHID-USER-mvx4x7ywk2flsaku2dbk,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"The old gerrit version only showed the ""Rebase"" button if the patch was in need of the rebase, while on gerrit-new the option is always displayed. If that's configurable it would be nice to revert to the old behaviour (since it makes it more obvious whether a patch needs to be rebased before merging)",1468418080,PHID-USER-abszjqutasfjxgagymds,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"@demon hi, I noticed that it dosent show the links to phabricator from the changes or from project pages.
+
+And it seems zuul is not testing in gerrit-new.
+
+And it the performance has really increased, loads instantly for me on a 80mbps connection from BT.",1468400541,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2456476, @AlexMonk-WMF wrote:
+> I've been messing around with gerrit-new. On the projects list, a lot appear to be duplicated under the 'git/' prefix?
+
+Looks like a mistake on-disk from my part from when we were doing replication of repositories via rsync. Deleted the git/* ones.",1468387574,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2456522, @AlexMonk-WMF wrote:
+> I don't think the VE backport submodule update issue has been fixed :/
+> I made https://gerrit-new.wikimedia.org/r/#/c/298010/ but it doesn't look like the submodule update showed up against mediawiki/core.git's wmf/1.28.0-wmf.1 branch
+
+It probably will require a manual fix in the database where the old registration took place. Check with `gsql`?",1468387417,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"I don't think the VE backport submodule update issue has been fixed :/
+I made https://gerrit-new.wikimedia.org/r/#/c/298010/ but it doesn't look like the submodule update showed up against mediawiki/core.git's wmf/1.28.0-wmf.1 branch",1468376670,PHID-USER-mvx4x7ywk2flsaku2dbk,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"I've been messing around with gerrit-new. On the projects list, a lot appear to be duplicated under the 'git/' prefix?",1468374689,PHID-USER-mvx4x7ywk2flsaku2dbk,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 298041 merged by Dzahn:
+gerrit: make Apache config compatible with 2.4
+
+[[https://gerrit.wikimedia.org/r/298041]]",1468274630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 298041 had a related patch set uploaded (by Dzahn):
+gerrit: make Apache config compatible with 2.4
+
+[[https://gerrit.wikimedia.org/r/298041]]
+",1468271973,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Paladox spoke to hashar after the comment above and the user does not have to be created (?),1468270190,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"The user jenkins-bot will need to be created in lead 
+
+https://github.com/wikimedia/operations-puppet/blob/30ffadcb6d8e6925affd55958981dce8c2c448d9/modules/role/manifests/zuul/configuration.pp#L8",1468267164,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"We need to update 
+
+https://github.com/wikimedia/operations-puppet/blob/30ffadcb6d8e6925affd55958981dce8c2c448d9/modules/role/manifests/zuul/configuration.pp#L8
+
+and 
+
+https://github.com/wikimedia/operations-puppet/blob/30ffadcb6d8e6925affd55958981dce8c2c448d9/modules/contint/manifests/firewall.pp#L60",1468262620,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,We need to update https://github.com/wikimedia/operations-puppet/blob/30ffadcb6d8e6925affd55958981dce8c2c448d9/modules/role/manifests/zuul/configuration.pp#L8,1468262418,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Also the zuul seems to work perfectly with gerrit 2.12 (no lost in connection or ssh connection) It seems to me that may have been a bug in gerrit 2.8.,1468253923,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"@hashar Ive been testing zuul, jenkins and gerrit 2.12 and it works. See 
+
+* https://gerrit-zuul.wmflabs.org/
+
+* https://gerrit-jenkins.wmflabs.org/
+
+* https://gerrit-test.wmflabs.org/
+",1468253816,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Ive been testing zuul, jenkins and gerrit 2.12 and it works. See 
+
+* https://gerrit-zuul.wmflabs.org/
+
+* https://gerrit-jenkins.wmflabs.org/
+
+* https://gerrit-test.wmflabs.org/
+",1468253807,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"The upgrade of Gerrit definitely has an impact on Zuul.
+
+The version we run is based on upstream 66c8e52 which is:
+* from early December 2015 (7 months ago)
+* when they were still running Gerrit 2.8.4
+* before a massive refactoring of how Zuul connects to Gerrit
+
+I tried to upgrade Zuul further but a mysteriously issue happened related to the Zuul / Gerrit ssh connection: T137525 . I haven't managed to reproduce it locally or on labs though :-(
+
+OpenStack has (since December) switched to Gerrit 2.11.x + patches and I haven't looked at Zuul code whether there are changes that are needed. They will most probably be based on massive refactoring that we still do not have in our version.
+
+
+The, maybe the Zuul version will just work with Gerrit 2.12.  If `stream-events` hasn't changed and the `review` command is still compatible, we might be just fine.
+
+
+----------
+
+As part of the migration we also have to:
+* update various Zuul related bits that points to ytterbium
+* most probably manually change the remote URL of zuul-merger repos on scandium in /srv/ssd/zuul/git
+
+
+----
+
+Also I think the old change screen is gone and that is going to cause major havoc  and complains for sure. So wanna communicate about that user facing change ahead of time.
+
+
+",1468250598,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Re timing:
+I guess email Ops list with the plan, ask for a volunteer for Sunday (offer $drinks), if someone replies before tomorrow (Saturday) when Chad wake up then he should send out the announcement that we'll do the Sunday maintenance window.",1468017013,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Tested the upgrade path today using copies of production data (Sql and Git) and the 2.12.2 package we built for Jessie. It went well. Couple of more tests this afternoon and then it looks like we can run the upgrade ASAP. Workflow will be:
+
+1) Decide/announce a window
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet manifest to new server `lead`
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Stop puppet on `lead` until (7) is done to keep Gerrit from being brought up just yet
+7) Run the reindexing process on new `lead`, will take about 45-60m from testing.
+8) Re-enable puppet so systemd can take over running gerrit
+9) Verify installation
+10) Point DNS from ytterbium to `lead`
+
+The whole process, ideally, should only take about an hour to an hour and a half based on my testing. I want to give myself 3 hours in case. This is highly disruptive so needs to be announced widely, but soon (as in days, not weeks). I'm almost thinking this weekend since less disruption than on a workday...
+
+I will need a root user on hand to take the snapshot and merge puppet changes (which can all be staged beforehand). @Dzahn has been super helpful so far, but I know @jcrespo is the DBA.",1468368567,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Tested the upgrade path today using copies of production data (Sql and Git) and the 2.12.2 package we built for Jessie. It went well. Couple of more tests this afternoon and then it looks like we can run the upgrade ASAP. Workflow will be:
+
+1) Decide/announce a window
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet manifest to new server `lead`
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Stop puppet on `lead` until (7) is done to keep Gerrit from being brought up just yet
+7) Run the reindexing process on new `lead`, will take about 30-45m from testing.
+8) Re-enable puppet so systemd can take over running gerrit
+9) Verify installation
+10) Point DNS from ytterbium to `lead`
+
+The whole process, ideally, should only take about an hour to an hour and a half based on my testing. I want to give myself 3 hours in case. This is highly disruptive so needs to be announced widely, but soon (as in days, not weeks). I'm almost thinking this weekend since less disruption than on a workday...
+
+I will need a root user on hand to take the snapshot and merge puppet changes (which can all be staged beforehand). @Dzahn has been super helpful so far, but I know @jcrespo is the DBA.",1468014014,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Another feature/bug in 2.11 (and with it in 2.12, too) would be a fix for:
+https://bugs.chromium.org/p/gerrit/issues/detail?id=1207
+
+Yes... on a german keyboard you can't use the shortkeys for next/previous file in the diff view, which isn't really great  :(",1465317098,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"@demon Hi, any news here? :) Is it possible to have a look at a test instance running the newer Gerrit version?",1462873310,PHID-USER-m2zne2efu3rgmre73nl7,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"I don't think, that such a hidden feature, especially because it isn't mentioned in the changelog and only available by adding a query to the url, is something which could be named as a ""near"" feature we've after upgrading :)",1459536003,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"There's polygerrit, gerrit said next version but built into gerrit to test at moment. Once updated to gerrit 2.12 add this to your url ?polygerrit=1 the new design is really nice.",1459474099,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,I guess ops may like https://code.google.com/p/gerrit/issues/detail?id=3293,1457627783,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2107030, @siebrand wrote:
+> Is there any way to find out if this will or won't be scheduled?
+
+When I have a firm date/time for switching to the new machine & version I'll let everyone know. Right now I'm getting the box prepped and testing the new version.",1457624570,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,I believe that they have a setup a new server and that will use gerrit 2.12  they will be switching soon I think. I may be wrong.,1457622881,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Is there any way to find out if this will or won't be scheduled?,1457622008,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Gerrit 2.12 includes support for signed pushes now which some users on Wikipedia use.
+
+Release notes at https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.12.html",1451238766,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Maybe create a test site with gerrit and test weather upgrading gerrit will cause zuul and jenkins too break.,1449169909,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"OpenStack is upgrading to 2.11 on Dec 16th (from 2.8.4+).  They already wanted to upgrade a couple weeks ago but cancelled it, maybe because it was not working properly.
+
+No idea whether 2.12 will work.
+
+Upgrade of Gerrit usually have side effect with Zuul.",1449169117,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Yes and plus makes it really easy to edit in browser. Some users like using the gerrit tool provided by Wikimedia to upload there patches with this update they can do it from gerrit supper easy.,1449165846,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Although Phabricator is the glorious future, we should upgrade Gerrit at least for stability + security improvements if nothing else. 2.12 is basically ready to go, testing it now.",1449163362,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Gerrit 2.11.1 has been released doesent show it on its front page but in the release notes it does. Please visit https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.1.html which I think fixed the problem that blocked us from upgrading.,1434123615,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,And delete project can be downloaded at https://ci.gerritforge.com/view/Plugins-stable-2.11/job/Plugin_delete-project_stable-2.11/ and already compiled to works with gerrit 2.11.,1433349752,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,And includes more features and no longer uses google to generate charts.,1433349700,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,If you doint want to compile gitblit use this https://ci.gerritforge.com/job/Plugin_gitblit_stable-2.11/ which is already complied and works for me. ,1433349554,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Me too.,1433271785,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"It's been a while since I looked at upstream…
+
+* Keyboards shortcuts in diff view all work correctly again, so do long lines; unified diff is back, as well as prefs. There's an inline button to leave a comment when you select text; no one is going to miss double-clicking (you can effectively triple-click now). There is literally no reason not to prefer the new diff view now. https://gerrit-review.googlesource.com/#/c/68292/1/gerrit-server/src/main/java/com/google/gerrit/server/config/GerritGlobalModule.java
+* Automated comments (bots, new patchsets) in change view are collapsed by default.
+* ""Size"" column in changes lists! *drools* https://gerrit-review.googlesource.com/#/q/status:open
+* ""Conflicts with"" pane! ""Merge conflict"" status in changes lists!
+
+so much awesome
+
+seriously
+
+can we update already plz?",1433271106,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,And improvements to list of projects because it doesent show all of projects In one list it now puts them on different pages. ,1433270051,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Yes get them to look at that is better.,1433269947,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Or they can just [[ https://gerrit-review.googlesource.com/#/c/68304/ | look at upstream ]].,1433269286,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,I doint mean the current new screen in gerrit on Wikimedia. Wikimedia could set up a test gerrit server with the new screen and get feedback since they wont upgrade unless the majority like it. And when they moved bug software from bugzilla to phabricator that was a big user ajust ment. so the same can be applied here.,1433267433,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Note that the new screen in 2.11 is said to have received much improvement, so asking users based on the current new screen makes no sense.",1433266117,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Yep. Since that would be a breaking change I suggest to create a feedback online and ask users to say would they like the new change screen or not. And say the improvements it would have if we upgrade.,1433263209,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"That release seems to include the patch QChrist identified as missing and according to my reading of the source it will ship with jgit 4.0.0.201505050340-m2. If that works for openstack...
+
+Then the only thing remaining we identified is living with the old ChangeScreen being gone.",1433252884,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Hi 2.11.1 release notes at https://gerrit.googlesource.com/gerrit/+/refs/heads/stable-2.11/ReleaseNotes/ReleaseNotes-2.11.1.txt looks like they may have fixed performance bug.,1433244298,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1296359, @Paladox wrote:
+> we could upgrade to latest 2.8.x release
+
+...which isn't handled in this task (now i feel like a parrot o.O) - See {T65847}.",1432048476,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Hi yes we could upgrade to latest 2.8.x release which would includes fixes.,1432048325,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1285022, @Paladox wrote:
+> Hi what about upgrading to 2.8.6.1
+
+Not handled in this task. - See T65847.",1432029435,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,And then once 2.11 is fixed. then disccuss about upgrading since it removes the old screen which everyone is used too.,1431619328,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,2.10 should be the version we upgrade to since it still has the old change screen but not default you would have to set it default and you can now customise the my page,1431619274,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,or 2.9 or 2.10. Note 2.9 onwards the bugzilla plugin uses the new its-bugzilla instead of old plugin and plugins list are now shown.,1431618933,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Hi what about upgrading to 2.8.6.1 since it is a minor upgrade from 2.8.1 to 2.8.6.1 and in preparation for if people are in favour of upgrading to 2.11 when the bug is fixed.,1431618480,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,That definitively sounds like a blocker (i assume we have a comparable traffic in our gerrit-instance).,1431508397,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1281258, @QChris wrote:
+> I guess @hashar was instead refering to the post about gerrit complaining about corrupt pack files. See also https://groups.google.com/forum/#!topic/repo-discuss/CYYoHfDxCfA
+
+Yup that is the one I wanted to refer to sorry. OpenStack definitely want to upgrade so I am sure they will push to get it fixed (or fix it themselves).
+",1431507203,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1280109, @Paladox wrote:
+> I believe they fixed problem but haven't released a new version of gerrit for 2.11 with the fix they only released it with 2.10. Please see https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.10.4.html
+
+The fix you mentioned is for [[https://code.google.com/p/gerrit/issues/detail?id=3300|Gerrit Issue 3300]]. That was the bug for the performance degradation in 2.10.
+
+I guess @hashar was instead refering to the post about gerrit complaining about corrupt pack files. See also https://groups.google.com/forum/#!topic/repo-discuss/CYYoHfDxCfA",1431473496,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,I believe they fixed problem but haven't released a new version of gerrit for 2.11 with the fix they only released it with 2.10. Please see https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.10.4.html,1431447902,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"For what is worth, OpenStack has upgraded from Gerrit 2.8 to 2.11 and had to revert due to JGit issue.
+
+Revert announce with some details is: http://lists.openstack.org/pipermail/openstack-infra/2015-May/002750.html
+
+Jeremy Stanley (fungi) and James E. Blair (jeblair) can be reached on IRC in #openstack-infra (or one can mail them).",1431447230,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,This extension its-phabricator has been fixed and is now compatible with 2.11 whereas I am not sure about its-phabricator-from-bugzilla since I carnt find source code.,1431355030,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1271255, @QChris wrote:
+> Not sure about `github-create` ... is the code for that anywhere in the open?
+
+No, that's my secret sauce. I have to make sure I still have the code even.",1431098694,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1271255, @QChris wrote:
+> * 'Generate HTTP Password' is gone. I know that at least a few people used this at WMF.
+
+https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.html#remove-generate-http-password-capability reads:
+> Remove the Generate HTTP Password capability.
+>
+> The Generate HTTP Password capability has been removed to close a security vulnerability. Now only administrators are allowed to generate and delete other users' http passwords via the REST or SSH interface.
+>
+> It is encouraged to clean up your project.config settings after upgrading.
+
+This reads as if the ability for users except admins to do that for other users is gone, but users are still able to do that for themselves. ( https://android-review.googlesource.com/ is on 2.11 but integrated with Google Account so that one can still use the feature there possibly doesn't mean anything for our setup. )",1431090189,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1269328, @demon wrote:
+> `its-phabricator-*` ones are mission-critical and must be upgraded and functioning. `github-create` primarily affects me and @qchris but would be nice to still have working. `deleteproject` we don't maintain but will have to rebuild. The remaining 4 are all bundled and should Just Work.
+
+I can handle the `its-*` ones. Sure.
+
+`delete-project` we can grab for example from http://builds.quelltextlich.at/gerrit/nightly/stable-2.11/2015-05-07/index.html#delete-project.jar to spare us manual building. (It currently builds, and can be loaded, but I have not tested whether or not it's working).
+
+Not sure about `github-create` ... is the code for that anywhere in the open?
+
+(I am sure people will also ask for Luca's github plugin to get nice and easy Pull-Reuest handling. There have been some authentication issues in that plugin lately ... not sure if that is currently in a working state or not).
+
+But I think there are other deal-breakers (this list need not be exhaustive):
+* In 2.11, our current default ChangeScreen is gone. Forcing people to use the new ChangeScreen and only to tell them to again cange to Differential in a few months(?). I'd consider that a no-go.
+* In 2.11, the same Mina SSHD is used that is somewhat suspected by users to cause issues for 2.10.3.1. Debugging Mina SSHD is no fun. I had to do that twice. I don't want to do it again, just because we cannot downgrade and (maybe) 2.11's Mina SSHD causes issues.
+*  The released 2.11 war lacks https://gerrit-review.googlesource.com/#/c/67490/1 which fixes mouse grab issues, and I'd consider it important.
+* One person reported running out of heap after upgrading to 2.11. The reporter got it under controll by running garbage collection on their repos. But since downgrading again is somewhat not an option and some of our repos are big, one need to double-check and make sure that this does not bite us ... or if it bites wmf's gerrit, one needs to at least check that gc can reliably mitigate it for wmf.
+* 'Generate HTTP Password' is gone. I know that at least a few people used this at WMF.
+
+All in all ... I am not sure if now is the right time to upgrade to a 2.11 version. A few weeks down the road (and maybe after a new release in the 2.11 series), the middle three items go away. But the dropping of the our current default ChangeScreen will stay. People would get forced to use the New ChangeScreen.",1431048060,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Hi here is link for updates for its-phabrictor https://gerrit.googlesource.com/plugins/its-phabricator/+/master,1431040464,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1269328, @demon wrote:
+> We currently have the following plugins:
+
+I added them (the ones need an update/test) to the task description :)",1431015224,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"We currently have the following plugins:
+```
+commit-message-length-validator	v2.8.1	Enabled
+deleteproject	2.8.1	Enabled
+download-commands	v2.8.1	Enabled
+github-create-1.0-rc0	1.0-rc0	Enabled
+its-phabricator	2.8.1	Enabled
+its-phabricator-from-bugzilla	2.8.1	Enabled
+replication	v2.8.1	Enabled
+reviewnotes	v2.8.1	Enabled
+```
+`its-phabricator-*` ones are mission-critical and must be upgraded and functioning. `github-create` primarily affects me and @qchris but would be nice to still have working. `deleteproject` we don't maintain but will have to rebuild. The remaining 4 are all bundled and should Just Work.",1431014698,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"[08:59:05] <^d> Somebody convince qchris to redo the plugins and I'll do it :p
+
+@qchris, are you up for that? :)",1431014428,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,+1. I still have hope that there is someone who can do this and who doesn't hate Gerrit so much as to not touch it with a stick.,1431005789,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T65847#1268664, @Nemo_bis wrote:
+> The request for 2.11 should be moved to T70271. This report is for requesting a minor version upgrade within 2.8.x.
+
+Then this task should be reopened.",1431005769,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Moving some offtopic discussion from the other report:
+
+>>! In T65847#1268528, @Florian wrote:
+> Gerrit [[ https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.html | release 2.11 ]] adds another really really useful feature, [[ https://gerrit-documentation.storage.googleapis.com/Documentation/2.11/user-inline-edit.html | inline editing ]], which allows you to create changes within the browser without cloning the repo or checkout the change itself. I know, that we're planing to migrate gerrit to phabricators Differential, but it would be a very nice and (like i said) useful feature in gerrit, which (as far as i know) doesn't exist in Differential at the moment (see {T409}, and it seems, see the discussion on the upstream task, that this feature will not arrive in Differential in the next time). In my point of view it would be a step backwards if Gerrit now (after a long long time of user wishes, i think) get's a web based editor and we move to Differential, which doesn't support this feature and doesn't has the plan to implement it.
+> 
+> Another point is, that i don't see a real roadmap for the migration (i read some tasks and haven't found one to implement a testing environment to show the code-review process, which wasn't resolved so far and was planned for last xyear september iirc, but i doesn't find it again :/). So, should we re-consider to upgrade gerrit? That would make it possible to resolve {T71445}.
+> 
+> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default, see for information https://gerrit-review.googlesource.com/Documentation/user-review-ui.html.
+
+
+
+>>! In T65847#1268589, @matmarex wrote:
+>> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default
+> 
+> Good, it's already way better than the old one in the ancient beta version we're running, and I heard that the issues it has got ironed out. I'd also love if the upgrade (any upgrade) happened.
+
+
+
+>>! In T65847#1268589, @matmarex wrote:
+>> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default
+> 
+> Good, it's already way better than the old one in the ancient beta version we're running, and I heard that the issues it has got ironed out. I'd also love if the upgrade (any upgrade) happened.
+
+
+
+>>! In T65847#1268606, @Florian wrote:
+>>>! In T65847#1268584, @JanZerebecki wrote:
+>> I'd like the upgrade to 2.11 to be reconsidered. But it is also a question of finding someone who does the work. So lets first find someone to do the work of upgrading to 2.8.6.1.
+> 
+> Not really needed, we're already using gerrit release 2.8.x (2.8.1), which would allow us to directly upgrade to 2.11, see https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.html
+> 
+> (let's adjust the title of this task to ""Upgrade gerrit"", because it seems, that we are currently not really sure, _if_ we can/should/want upgrade gerrit at all :))
+> 
+> 
+> 
+>>>! In T65847#1268589, @matmarex wrote:
+>>> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default
+>> 
+>> Good, it's already way better than the old one in the ancient beta version we're running, and I heard that the issues it has got ironed out. I'd also love if the upgrade (any upgrade) happened.
+> 
+> +1, i tested it locally and it's a big improvement, still a ""new"" thing, but you find all needed things very fast :)
+
+",1431005224,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"(In reply to christian from comment #6)
+> Since people asked for more reasons, why to not upgrade:
+
+Thanks, that's useful. None of these points applies to 2.8.x upgrades (bug 63847), correct?",1415268588,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Since people asked for more reasons, why to not upgrade:
+
+* Search backend gets switched. And the first test I made with it some time back
+  were not super solid. That might have changed in the meantime, and the old
+  (=current) search system has it's warts too, but we know them, and can live
+  with them. No hidden dangers there.
+
+* At first glance, it seems there are database schema changes. Those typically
+  make it hard to downgrade if something goes wrong. So the upgrade would need
+  good preparation. We cannot “just try it out”.
+
+* We'd need new plugins, since part of the functionality that was in core before
+  got put into separate plugins.
+
+* We'd need to rebuild our bugzilla integration.",1405891941,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"So if it's just some new random features with questionable gain in our usecase, I will close this as WILL NOT FIX.",1405797393,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,It also has a new plugin for bugzilla.,1405791360,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Well the new design that is an option in the current version of gerrit on wikimedia is a part of the new design but they also redesigned it complete in 2.9. It also includes a new side by side diff and also Fix truncated long lines in new side-by-side diff screen.,1405791299,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Gerrit 2.9 includes the new change screen which is worse. That's a reason not to upgrade.
+
+Plus we're planning a Phabricator migration soon-ish. What's to gain?",1405788661,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"I don't consider ""please upgrade some software to some latest version"" very useful if there are not 1) very good reasons to do this 2) urgently.
+Your list above does not provide any good reasons.",1405782365,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","We get ""Unknown error"" (not internationalised) when saving on officewiki.
+
+This is because the response object given to ve.init.mw.Target.onSave is actually a jqXhr(?) object here for some reason, which has an error function. The data we actually want is in the responseJSON property of this, and we can also get it via .done( ... ).
+
+This stuff comes through tryWithPreparedCacheKey and the way it fits together with everything else wasn't very clear here (lots of chaining deferreds etc.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405716000,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jt6qre2zwuzp7bltugkt,task_description,resolved
+"VisualEditor: ""Unknown error"" on saving on officewiki","I fixed it up in the remaining places:
+```commonswiki         MediaWiki:LAPI.js
+dewikiversity       MediaWiki:LAPI.js
+enwiki              MediaWiki:LAPI.js
+fawiki              MediaWiki:LAPI.js
+huwiki              MediaWiki:LAPI.js
+huwikiquote         MediaWiki:LAPI.js
+kawiki              MediaWiki:LAPI.js
+mlwiki              MediaWiki:LAPI.js
+nnwiki              MediaWiki:LAPI.js
+rowiki              MediaWiki:LAPI.js
+ruwikibooks         MediaWiki:LAPI.js
+srwikibooks         MediaWiki:Common.js/Core.js
+svwiki              MediaWiki:LAPI.js
+zhwiki              MediaWiki:LAPI.js```",1425670493,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki",">>! In T70235#719892, @Krenair wrote:
+> So that last srwikibooks entry appears to be in an unused file... Roan, can you release and upstream the LAPI.js changes to the other wikis? I don't think I can do it (I'd have to do it as staff, but my global editinterface is personal, so...).
+
+Sorry for the extreme delay: https://eo.wikipedia.org/w/index.php?title=MediaWiki:LAPI.js&diff=prev&oldid=5628789",1425668478,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","So that last srwikibooks entry appears to be in an unused file... Roan, can you release and upstream the LAPI.js changes to the other wikis? I don't think I can do it (I'd have to do it as staff, but my global editinterface is personal, so...).",1407160072,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki",https://dpaste.de/JS7k/raw courtesy of legoktm is an mwgrep of all of the redefinitions of bind on the cluster. Yay.,1407059571,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","This was caused by local JS overwriting Function.prototype.bind with a broken polyfill that ignores additional parameters rather than passing them to the bound function.
+
+We were using something like onSave.bind( this, doc, saveData ) which should have resulted in a call like onSave( doc, saveData, responseData, statusText, jqXHR ) but the broken polyfill dropped doc and saveData, causing the remaining arguments to be shifted two places to the left. Then when we check if responseData.error is defined, we're really looking at jqXHR.error, which is in fact a method on the jqXHR object, so it's always defined and we always believe there is an error, even if there isn't one. But of course we can't find an error code or error text because we're looking in the wrong place, so we say ""Unknown error"". In fact, we would say that even if there was an error, because the error data got shifted over into the doc parameter, which we don't look at.
+
+https://office.wikimedia.org/w/index.php?title=MediaWiki:LAPI.js&diff=115901&oldid=24064 fixes the unconditional overwrite so Function.prototype.bind isn't overwritten if it's already present. This check was already being done for everything else that the script polyfills.
+
+https://office.wikimedia.org/w/index.php?title=MediaWiki%3ALAPI.js&diff=115904&oldid=115902 fixes the polyfill to correctly pass additional parameters along.",1407034283,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki",Mis-fire.,1406147366,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","Change 148757 had a related patch set uploaded by Catrope:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148757",1406146930,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","officewiki is important, actually",1406139217,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","Does not affect other private wikis (checked otrswiki, collabwiki), not major/high priority.",1405717579,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Screenshot
+
+1.Open a page with VE in FF
+2.Click on Link inspector icon 
+3.The inspector does not open up
+4.Now again click on the link tool on the toolbar
+
+Observed Result:
+The link inspector opens up with distorted UI and the following error appears in the console
+
+TypeError: manager.opening is null
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14196}",1405707060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_description,resolved
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI",Verified the fix in production,1407189770,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI",Verified the fix in Betalabs and the backport on test2,1406161145,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Change 148770 merged by jenkins-bot:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148770",1406153427,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Change 148770 had a related patch set uploaded by Jforrester:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148770",1406148486,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Change 148757 merged by jenkins-bot:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148757",1406148399,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Change 148757 had a related patch set uploaded by Catrope:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148757",1406147238,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","This is also happening for Language inspector,math inspector,special character.
+Its not that they are not opening on the first attempt, it takes too long to open it , so when I tried to open them second time , it throws that error and appears in broken way.",1405708610,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned","Screenshot
+
+Open language inspector in betalabs and observe the brokenness
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14642}",1405620240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6qda63lpaymzom6tbttz,task_description,resolved
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned",Verified the fix in production en.wiki,1406318938,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned",Verified the fix in test2,1405719538,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned",Verified the fix in test2,1405719533,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned",Fixed in gerrit 147179; will pull through and back-port.,1405624867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned","Also , Special Character inspector has its UI distorted.Are they related?",1405620557,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+VisualEditor: PopupToolGroup item not 'ticked' after changing,"1. Place the cursor in a paragraph and change it to a heading the the popup tool
+2. Open the popup tool again and observe that nothing is selected (with a tick)
+3. Change the context (click in another paragraph/heading, then back)
+4. Open the popup tool, the correct item is now selected
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405615500,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yjzj5bv5ffrnllxzssak,task_description,resolved
+VisualEditor: PopupToolGroup item not 'ticked' after changing,Fixed in gerrit 4b874d42206e988844367eccacb9503fe6c3ddb5.,1406060277,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yjzj5bv5ffrnllxzssak,task_subcomment,NA
+VisualEditor: PopupToolGroup item not 'ticked' after changing,"This may well be a oojsui bug, tbd.",1405615571,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yjzj5bv5ffrnllxzssak,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"When I have created an article in the hebrew version of wikipedia, ☃ symbol replicated.
+
+The operations I did:
+1. I copied an tamplate from another article.
+2. I edited it's fields by the visual editor.
+3. I started to write text in bold.
+4. I changed the text state to normal.
+5. The symbol ☃ started to replicate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68151",1405587840,PHID-USER-em3l7mquu7qcck24eqq5,PHID-TASK-ygqki32oghxhcc37oyhf,task_description,resolved
+VisualEditor: ☃ symbol replicates when creating an article with a template,Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660949,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659002,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658987,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658731,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646181,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646098,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645954,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645924,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645480,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645472,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,*** Bug 68148 has been marked as a duplicate of this bug. ***,1406601182,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594983,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make an edit 
+3.Click on the ""Save Page""
+4.While the saving is in progress,keep on clicking on the ""Save Page"" button on the Save dialog
+
+Observed Result:
+The following error appears in the console:
+
+Uncaught TypeError: Cannot read property '$saveOptions' of null
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14424}",1405459560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_description,resolved
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""",Verified the fix in production,1407187444,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""",Verified the fix in test2,1406327297,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""",Verified the fix in Betalabs,1406159736,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""",Going to mark as FIXED but please re-open if there's an issue.,1406083201,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Does this still happen? I was able to replicate it on deployment-prep at the time (not on my local machine, as I said), but now I can't...
+
+I get ""Uncaught TypeError: Cannot read property 'getModel' of null"" when trying to load VE after it's been saved (again, only on deployment-prep, not my local machine), but that seems unrelated.",1405632802,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","I can reproduce both the UI as well as the logic problem.
+
+Both the ""Review your changes"" and the ""Save page"" buttons in the save dialog remain clickable.
+
+Their apparent state looks clickable, their response to clicking is appeared pressed, and the result is the event handler firing internally.
+
+The exception usually doesn't happen until after the first save attempt has finished and the view goes back to ""read"" mode, but it does throw:
+
+ve.init.mw.ViewPageTarget.prototype.onSave = function ( ..  ) {
+	if ( !this.pageExists || this.restoring ) {
+		..
+	} else {
+		if ( mw.page.watch && mw.page.watch.updateWatchLink ) {
+			watchChecked = this.saveDialog.$saveOptions
+.. ^",1405561718,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","I don't think that fixed it, unfortunately. But I can't reproduce this error locally.",1405545623,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Change 146810 merged by jenkins-bot:
+Don't allow document save if we're already tearing down the surface
+
+https://gerrit.wikimedia.org/r/146810",1405543526,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Change 146810 had a related patch set uploaded by Alex Monk:
+Don't allow document save if we're already tearing down the surface
+
+https://gerrit.wikimedia.org/r/146810",1405529649,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Seems that I can only get ""Uncaught TypeError: Cannot read property 'messages' of null "" on my local machine",1405527697,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,"Steps to reproduce:
+
+1.Open a page with VE
+2.Make an edit to the page
+3.Click on the ""Cancel"" button next to ""Save Page""
+
+Observed Result:
+Nothing happens, the confirmation dialog box does not appear neither it lets user close VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405457520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xbka5x6ezizjtfccyclk,task_description,resolved
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,Verified the fix in production en.wiki,1406318542,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,Verified the fix in test2,1405720234,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,Verified the fix in Betalabs,1405556318,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,"Change 146639 merged by jenkins-bot:
+Make a message dialog for cancelling VE
+
+https://gerrit.wikimedia.org/r/146639",1405543530,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,"Change 146639 had a related patch set uploaded by Alex Monk:
+Make a message dialog for cancelling VE
+
+https://gerrit.wikimedia.org/r/146639",1405465411,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,"Screenshot
+
+Steps to reproduce:
+
+1.Select a math node/ a reference/image /open any inspector
+2.Scroll down the page
+
+Observed Result:
+The highlights, context menus and inspectors everything is appearing over the toolbar
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14413}",1405455840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-izo3tiafzfdz4gvztvz5,task_description,resolved
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,Verified the fix in production en.wiki,1406318442,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,Verified the fix in production en.wiki,1406318428,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,Verified the fix in test2,1405721309,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,"Change 146981 merged by jenkins-bot:
+Update VE core submodule to master (8bb3848)
+
+https://gerrit.wikimedia.org/r/146981",1405554705,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,"Change 146981 had a related patch set uploaded by Jforrester:
+Update VE core submodule to master (8bb3848)
+
+https://gerrit.wikimedia.org/r/146981",1405553286,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,"Screenshot
+
+The Link inspector in mobile became completely broken and unusable after new windows refactor change
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14399}",1405453020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j2fbmrbwc2pv3om246qs,task_description,resolved
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,Verified the fix in production en.wiki,1406317240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j2fbmrbwc2pv3om246qs,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,Verified the fix in test2,1405723887,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j2fbmrbwc2pv3om246qs,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,"Change 146296 merged by jenkins-bot:
+Get OOUI working with mobile again
+
+https://gerrit.wikimedia.org/r/146296",1405548473,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j2fbmrbwc2pv3om246qs,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,"Change 146296 had a related patch set uploaded by Jforrester:
+[WIP] Get OOUI working with mobile again
+
+https://gerrit.wikimedia.org/r/146296",1405456924,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j2fbmrbwc2pv3om246qs,task_subcomment,NA
+VisualEditor Mobile: Context menu for Math is still appearing in Mobile VE,"Tapping on a math node is still bringing up the context menu on top of the page,letting user to open math inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405378440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dexoxhnm6p7r5tl42o5j,task_description,declined
+"OOjs UI: When the text in buttons in confirmation dialogs is too long, some of the buttons may overflow, breaking the dialog","Example with cyrillic text where one button overflows.
+
+When the dialog to switch from VisualEditor to wikicode edition is shown, its dimensions are sufficient to show all the buttons when the interface text is in English. However, in fr, crh-Cyrl and possibly in other languages, the text on the buttons is longer, and the buttons can fall and flow over the edge of the dialog (overflow). This makes it impossible to read the text on them.
+
+This issue is best described by the screenshot attached to this message, and by the subsequent screenshots.
+
+To reproduce:
+
+- Browse to this URL: https://en.wikipedia.org/w/index.php?title=User:Rastus_Vernon/VisualEditor_Sandbox&veaction=edit&uselang=fr.
+- Open the VisualEditor menu.
+- Click “Passer à l'édition de code”.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14277}",1405374540,PHID-USER-2rwkb3az6uklfhh5aqw5,PHID-TASK-htrpa3kqlb6jcmk4geh7,task_description,resolved
+"OOjs UI: When the text in buttons in confirmation dialogs is too long, some of the buttons may overflow, breaking the dialog",Happily we just fixed this in gerrit 139550 which means the buttons on ConfirmationDialogs will automatically re-order and re-size based on the length of the label.,1405375780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-htrpa3kqlb6jcmk4geh7,task_subcomment,NA
+"OOjs UI: When the text in buttons in confirmation dialogs is too long, some of the buttons may overflow, breaking the dialog","Created attachment 15937
+Example of the expected behavior, in English, for comparison.
+
+**Attached**: {F14281}",1405374648,PHID-USER-2rwkb3az6uklfhh5aqw5,PHID-TASK-htrpa3kqlb6jcmk4geh7,task_subcomment,NA
+"OOjs UI: When the text in buttons in confirmation dialogs is too long, some of the buttons may overflow, breaking the dialog","Created attachment 15936
+Example with French text where two buttons overflow.
+
+**Attached**: {F14278}",1405374619,PHID-USER-2rwkb3az6uklfhh5aqw5,PHID-TASK-htrpa3kqlb6jcmk4geh7,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Based on feedback and test by French Wikipedians, which we always thank.
+
+An editor reported getting a snowman here https://fr.wikipedia.org/w/index.php?title=Lucien_Dayle&diff=next&oldid=105411841 when all he did was removing a comma (Chrome, Mac OS X).
+I wasn't able to reproduce https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve2&diff=105432197&oldid=105432184 .
+
+Then another user created a sandbox with similar templates in it and I tested there as well; https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AZebulon84%2FBrouillon&diff=105432505&oldid=105431985 the snowman showed up in the exact place where I had added a comma.
+
+In another case instead https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AZebulon84%2FBrouillon&diff=105432576&oldid=105432561 the letter ""e"" shows up where I had put the comma. The user had previously replaced the template {{e}} with <sup> tags (https://fr.wikipedia.org/w/index.php?title=Utilisateur:Zebulon84/Brouillon&diff=prev&oldid=105422272 ).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405353120,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_description,resolved
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660943,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659005,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658984,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658734,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656765,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646173,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646092,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645959,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645934,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645493,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645477,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,*** Bug 68124 has been marked as a duplicate of this bug. ***,1406598882,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594974,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 149920 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406573578,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Note from Jay8g:
+
+In this edit [https://en.wikipedia.org/w/index.php?title=Hong_Kong_International_Airport&diff=618742880&oldid=618629367], I got a snowman after rearranging (copy and paste) a sentence with {{convert}}. This did not show up in VE itself, and appeared in place of the comma that I had actually added (and that had displayed in VE).
+
+This seems to be the same problem.",1406568378,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Comments from Erica on another bug:
+
+> 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.
+> 
+> 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 .",1406341582,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Down-page of {{IPA-es}} backspace behaviour is very broken,"**Author:** `and1eternal1`
+
+**Description:**
+When typing, inserting templates, hitting ""backspace"", and possibly more actions, the cursor moves two characters left after every action. Obviously, this makes editing nearly impossible.
+
+Confirmed and repeatable on: https://en.wikipedia.org/wiki/Corcovado_Volcano?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405097400,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-grrxbpfjnax5tx6mcpya,task_description,resolved
+VisualEditor: Down-page of {{IPA-es}} backspace behaviour is very broken,*** Bug 67933 has been marked as a duplicate of this bug. ***,1406319801,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-grrxbpfjnax5tx6mcpya,task_subcomment,NA
+VisualEditor: Down-page of {{IPA-es}} backspace behaviour is very broken,Fixed by the fix for bug 67432.,1405967290,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-grrxbpfjnax5tx6mcpya,task_subcomment,NA
+VisualEditor: Down-page of {{IPA-es}} backspace behaviour is very broken,"Interesting. It looks like the template IPA-es is causing this. If you delete the template, everything works fine.",1405097625,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-grrxbpfjnax5tx6mcpya,task_subcomment,NA
+Local versions of system messages are ignored,"Yesterday a user reported on the Italian Wikipedia that several Mediawiki messages which have a local version there are being ignored (I guess the system is showing the original message available at Translatewiki, but can't check since that site is currently down). This doesn't seem to be targeting one product only.
+
+Examples:
+The button to launch the new TemplateData editor says ""Gestisci documentazione template"" (you can check at the top left of https://it.wikipedia.org/w/index.php?title=Template:Cassetto/man&action=edit ). It should read ""Gestisci TemplateData"" instead, as per https://it.wikipedia.org/wiki/MediaWiki:Templatedata-editbutton .
+
+Or see Table 1 at https://it.wikipedia.org/wiki/Discussioni_utente:Rotpunkt#Messaggi_che_non_funzionano . The link says ""Comprimi""/""Espandi"", but the correct messages, linked a few lines above the table, should actually be ""Nascondi""/""Mostra"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68781",1405001760,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7y5kuddivdzl45gvwj6r,task_description,resolved
+Local versions of system messages are ignored,"(In reply to Matthew Flaschen from comment #37)
+> > And is ""II) Localisation cache returns ru when uk exists"" still a problem?
+> 
+> No one has identified a fix, so I would assume yes (even if the symptoms are
+> not exposed right now).
+> 
+> Filed as bug 68781.
+
+Thanks. CLosing this ticket about I) as FIXED as II) is handled there now.",1406713731,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Andre Klapper from comment #36)
+> (In reply to Andre Klapper from comment #35)
+> > NickK: Is this still a problem on Ukrainian Wikimedia sites?
+> 
+> And is ""II) Localisation cache returns ru when uk exists"" still a problem?
+
+No one has identified a fix, so I would assume yes (even if the symptoms are not exposed right now).
+
+Filed as bug 68781.",1406604188,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Andre Klapper from comment #35)
+> NickK: Is this still a problem on Ukrainian Wikimedia sites?
+
+And is ""II) Localisation cache returns ru when uk exists"" still a problem?",1406228586,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,NickK: Is this still a problem on Ukrainian Wikimedia sites?,1405614622,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,Lorenzo: Please create a separate ticket. This is offtopic.,1405597405,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Niklas Laxström from comment #32)
+> (In reply to Lorenzo Marconi from comment #31)
+> > Hello. On it.wiki we had changed the shortcut for the button ""Show preview""
+> 
+> This is separate issue and the cause is that ""-"" means that the message is
+> disabled and thus ""-"" cannot be used as an accesskey.
+
+Excuse me for the OT, but why it doesn't work only since a few days?",1405528698,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Lorenzo Marconi from comment #31)
+> Hello. On it.wiki we had changed the shortcut for the button ""Show preview""
+
+This is separate issue and the cause is that ""-"" means that the message is disabled and thus ""-"" cannot be used as an accesskey.",1405523552,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Hello. On it.wiki we had changed the shortcut for the button ""Show preview"" from alt+shift+v to alt+shift+- (see it:MediaWiki:Accesskey-diff). That shortcut doesn't work for a few days (or weeks, dunno). Since I thought that problem had been solved (comment #27), it may be related to this bug or not?",1405522811,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Nemo from comment #29)
+> Does the nutcracker issue completely explain findings I-II in comment 9? If
+> there are further underlying causes or possible improvements, separate bug
+> reports would be very useful once this one about the specific incident is
+> closed.
+
+Finding I, yes. Probably not finding II.
+
+I tracked that one as far as observing that the json file for uk that the cdb file gets built from has ""Править вики-текст"" as the value for messages:visualeditor-ca-editsource rather than ""Редагувати код"". That seems to be a separate issue from this one, and so should have its own bug report if it doesn't already.",1405436644,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Does the nutcracker issue completely explain findings I-II in comment 9? If there are further underlying causes or possible improvements, separate bug reports would be very useful once this one about the specific incident is closed.",1405434677,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Do the ResourceLoader caches need to be flushed to take care of any lingering issues? The entries in msg_resource with mr_timestamp less than 20140715002850 (based on comment 24) and mr_blob != '{}' are potentially problematic.
+
+At a quick look, this might apply to the following languages on wikis still on 1.24wmf12: ak af aln am ang anp arc ary as ast avk bbc bcl bg bi bo br brh ch ceb chr chy cr cps crh crh-latn cu dv dz ee en en-ca en-gb eu ext fj fo fy ga gom-latn got grc gu gv ha haw hi hif hif-latn hil hy ie ig ik ike-cans ike-latn ilo io iu jam jbo ka kab kbd kbd-cyrl kg khw ki km kri krj ks ks-arab ks-deva ku ku-latn kw ky la lfn lg li lo loz lrc lt lus lzh mai mdf mi mn mr my na ne new niu nl nl-informal nov nrm nso nv ny oc om or pag pam pap pi pih pnb pnt prg ps rif rm roa-tara rup rw sa sat sc sco sd sdc se sei sgs sh shi si sm sma sn so sq srn ss st sw te tet tg tg-cyrl tg-latn ti tk tl tly tn to tokipona tpi tru ts tt-latn tw ug ug-arab ug-latn ur uz ve vls vo war xh xmf yo yue zea zu. Other languages (except maybe uselang hacks) should have been updated already by the l10nupdate run at 02:00 UTC this morning.
+
+It looks like all languages on 1.24wmf13 wikis should have been updated by the l10nupdate run at 02:00 UTC this morning. This afternoon's update of non-Wikipedias to wmf13 should fix them too, BTW.",1405433305,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,It. and de.wp look fine though.,1405418946,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,Not sure if I should've actually closed it...,1405418010,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"reedy@tin:~$ mwscript eval.php itwiki
+> var_dump( MessageCache::singleton()->load( 'it' ) );
+bool(true)
+
+>",1405417968,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,<jgage> andre__: nutcracker is now updated on tin,1405384130,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"[01:09:35] <Reedy> I suspect it just hasn't had nutcracker updated on it
+[01:09:40] <Reedy> tin
+[01:09:41] <Reedy> nobody   23483  0.0  0.0  18732  1704 ?        Sl   Apr25   8:59 /usr/local/bin/nutcracker -m 65536 -a 127.0.0.1 -c /usr/local/apache/common-local/wmf-config/twemproxy-eqiad.yaml
+[01:09:46] <Reedy> mw1017
+[01:09:47] <Reedy> 112      14857  0.1  0.0  21652  2144 ?        Ssl  Jul07  13:11 /usr/sbin/nutcracker --mbuf-size=65536 --stats-port=22223
+[01:10:04] -*- jgage takes a look
+[01:10:10] <Reedy> Yeah
+[01:10:15] <Reedy> tin still is on ""twemproxy""
+[01:10:20] <Reedy> apaches are on ""nutcracker""",1405383049,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Ok, I think this is it. Turning on logging gives this from tin:
+
+ > var_dump( MessageCache::singleton()->load( 'it' ) );
+ [memcached] get(itwiki:messages:it:hash)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:hash"" on server ""127.0.0.1:11212"": CONNECTION FAILURE
+ [memcached] get(itwiki:messages:it)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] add(itwiki:messages:it:status)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:status"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] get(itwiki:messages:it:status)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:status"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] add(itwiki:messages:it:lock)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:lock"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] set(itwiki:test)
+ [memcached-serious] Memcached error for key ""itwiki:test"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] delete(itwiki:messages:it:lock)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:lock"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] get(itwiki:messages:it)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] add(itwiki:messages:it:status)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:status"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ MessageCache::load: Loading it... global cache is empty, waited for other thread to complete, global cache is empty, could not acquire status key., loading FAILED - cache is disabled
+ bool(false)
+
+I think at this point we need to get an ops person involved.",1405373573,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"More information: Something is screwy on tin, which is where the cache flush is run.
+
+This command:
+
+ wfMessage( 'collapsible-collapse' )->inLanguage( 'it' )->plain()
+
+returns ""nascondi"" on terbium (and presumably other servers) but ""Comprimi"" on tin.",1405373034,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Certainly RL cache clearing: after the fix above, I reset the timestamp on the new row and re-ran the RL cache clearer (refreshMessageBlobs.php in WikimediaMaintenance) on itwiki. And it's re-broken.",1405371839,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Yeah, when we ran into this with a VE message a few days ago, I checked this. wfMessage( $msg )->plain() returned the correct version, but mw.msg( msg ) did not.",1405371051,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"As a test, I removed the database row for ResourceLoader's message cache for jquery.makeCollapsible for Italian on itwiki. And upon reload, it started serving the correct messages for that expand/collapse example.
+
+Which makes me suspect even more that the RL cache clearing is broken.",1405370820,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Are there any examples where the incorrect message is being displayed in the served HTML, rather than being served via ResourceLoader for use in JavaScript? I'm suspecting not, since I can open https://it.wikipedia.org/wiki/Discussioni_utente:Rotpunkt#Messaggi_che_non_funzionano and add ""{{int:Collapsible-expand}} {{int:Collapsible-collapse}}"" and see the correct messages despite the JS-added link in the table being wrong.
+
+That makes me suspect either RL's message cache isn't being cleared properly, or else something in it is broken such that it's not picking up the customized messages.",1405370300,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Re-adjusting importance fields. I'd say this constitutes a ""major loss of functionality"", and definitely should not take ""one to six months"" to fix.",1405367857,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Please not that this bug is critically important for Ukrainian: the message affected (VE Edit tab) is a prominent one, and the fallback displayed (Russian despite both local and global translations being correct) is very badly received by the community (to the point that some people suggest disabling VE).",1405367707,PHID-USER-2nmvdoea7rwpw6ql3ydo,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"In case this wasn't clear enough, this is affecting several wikis, including large ones like the French or the German WP.",1405330739,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"In reply to Niklas Laxström from comment #12)
+Understood. Thanks.",1405194762,PHID-USER-auec42hjrvg4pumgrmut,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Володимир Ф from comment #11)
+> Maybe first space in this message in database causes error?
+
+That is just how MessageCache::loadFromDB presents them internally. There is no space in front of that message in the database.",1405194451,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,">   string(28) "" Редагувати код""
+or ""Редагувати код""?
+Maybe first space in this message in database causes error?",1405193134,PHID-USER-auec42hjrvg4pumgrmut,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Niklas Laxström from comment #9)
+> III) (bonus) Unicode does not work on eval.php at WMF
+> For III) It would be nice for someone to file a separate bug.
+
+Done, see bug 67924",1405176012,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"I have made multiple observations:
+1) Typing unicode to mwscript eval.php does not work in WMF
+2) This particular message has existed in uk.json since April
+3) Other messages in the same file seem to work on random testing
+4) MessageCache thinks the message does not exist:
+mwscript maintenance/eval.php --wiki=ukwiki
+> var_dump( MessageCache::singleton()->getMsgFromNamespace( 'Visualeditor-ca-editsource', 'uk' ) );
+bool(false)
+
+Because of 1) I was not able to test whether calling MessageCache::replace would have fixed that.
+
+5) MessageCache can find the message if instructed manually to load messages directly from the database:
+mwscript maintenance/eval.php --wiki=ukwiki
+var_dump( MessageCache::singleton()->loadFromDB( 'uk' ) );
+  ..
+  [""Visualeditor-ca-editsource""]=>
+  string(28) "" Редагувати код""
+  ..
+
+6) Localisation cache returns the ru version:
+> var_dump( $wgLang->getLocalisationCache()->getSubItem( 'uk', 'messages', 'visualeditor-ca-editsource' ) );
+string(33) ""Править викитекст""
+
+7) I cannot reproduce this issue locally
+
+8) LC issue is possibly caused by incorrect fallback merging, because L10nupdate contains update for ru, but not for uk (because the translation is already up to date for uk):
+nikerabbit@tin:/var/lib/l10nupdate/cache-1.24wmf12$ grep visualeditor-ca-editsource *-ru.* *-uk.*
+Binary file l10n_cache-ru.cdb matches
+l10nupdate-ru.json:    ""visualeditor-ca-editsource"": ""\u041f\u0440\u0430\u0432\u0438\u0442\u044c \u0432\u0438\u043a\u0438\u0442\u0435\u043a\u0441\u0442"",
+l10nupdate-ru.json:    ""visualeditor-ca-editsource-section"": ""\u043f\u0440\u0430\u0432\u0438\u0442\u044c \u0432\u0438\u043a\u0438\u0442\u0435\u043a\u0441\u0442"",
+Binary file l10n_cache-uk.cdb matches
+
+9) Something fishy with message cache:
+mwscript maintenance/eval.php --wiki=ukwiki
+> var_dump( MessageCache::singleton() );
+object(MessageCache)#108 (8) {
+  ...
+  [""mDisable"":protected]=>
+  bool(false)
+  ..
+}
+
+mwscript maintenance/eval.php --wiki=ukwiki
+> var_dump( MessageCache::singleton()->getAllMessageKeys( 'uk' ) );
+NULL
+> var_dump( MessageCache::singleton()->load( 'uk' ) );
+bool(true)
+
+> var_dump( MessageCache::singleton() );
+object(MessageCache)#108 (8) {
+  [""mCache"":protected]=>
+  bool(false)
+  [""mDisable"":protected]=>
+  bool(true)
+  ..
+  [""mLoadedLanguages"":protected]=>
+  array(0) {
+  }
+  ..
+}
+
+
+My conclusions so far are that there seems to be at least two separate issues here:
+I) MessageCache is failing to load its cache
+II) Localisation cache returns ru when uk exists
+III) (bonus) Unicode does not work on eval.php at WMF
+
+For I) I would like other people to inspect why that is happening.
+For II) My observation in 8 is a good starting point for my investigations for someone else while I continue my vacation. This might be specific to the way WMF runs l10n update.
+For III) It would be nice for someone to file a separate bug.",1405159197,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,Updated importance fields per https://mediawiki.org/wiki/Bugzilla/Fields#Priority,1405148176,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Doesn't fit the definition of ""critical"", AFAICS.
+
+Did someone try rebuilding the l10n cache? Were there changed to the LocalisationUpdate or deploy scripts in the last few days? Did someone inspect their logs?",1405147928,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,*** Bug 67911 has been marked as a duplicate of this bug. ***,1405130110,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Yes, this is pretty bad.
+
+Amir/Niklas: Can you take a look into this ASAP?",1405126522,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Escalating as this is now active on Ukranian Wikipedia too – https://uk.wikipedia.org/wiki/MediaWiki:Visualeditor-ca-editsource is correct but instead the Russian version, ""Править викитекст"" is showing in production.",1405125930,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"When I open this link in a private browsing window:
+
+https://it.wikipedia.org/w/index.php?title=Template:Cassetto/man&action=edit&uselang=it
+
+I see the default, non-customized button label for TemplateData, but I see the local, custom message for https://it.wikipedia.org/wiki/MediaWiki:Anoneditwarning",1405004992,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,It is indeed the original CDB translation (see https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FTemplateData.git/7136f55975d1f275e1c42fb0ad722c00e3ec5d82/i18n%2Fit.json).,1405002604,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"The original can be checked in the i18n directory of the source repo, e.g. https://git.wikimedia.org/tree/mediawiki%2Fcore.git/HEAD/languages%2Fi18n
+(Or in Special:AllMessages *if* it works.)
+
+Important note, Rotpunkt said this started happening between the 8th and the 9th, dates when no new MediaWiki version was deployed on it.wiki AFAICS.",1405002310,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,"I don't see the option to add Cite/References in Mobile Ve anymore in any mode .Is it switched off intentionally?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404862020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gyvrffyluoyvwurby4pu,task_description,resolved
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,Verified the fix in production en.wiki,1406317420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gyvrffyluoyvwurby4pu,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,Verified the fix in test2,1405723303,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gyvrffyluoyvwurby4pu,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,"Change 146962 merged by jenkins-bot:
+Enable mwreference, mwtransclusion modules on all targets including mobile
+
+https://gerrit.wikimedia.org/r/146962",1405550583,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gyvrffyluoyvwurby4pu,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,"Change 146962 had a related patch set uploaded by Jforrester:
+Enable mwreference, mwtransclusion modules on all targets including mobile
+
+https://gerrit.wikimedia.org/r/146962",1405550402,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gyvrffyluoyvwurby4pu,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Inspired by comments at various wikis and at bug 63389:
+pretty much what the summary says.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63389",1404763440,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_description,resolved
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 163029 merged by jenkins-bot:
+Let help link target be locally over-ridden; default to the MW help page
+
+https://gerrit.wikimedia.org/r/163029",1413914032,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 163029 had a related patch set uploaded by Jforrester:
+Let help link target be locally over-ridden; default to the MW help page
+
+https://gerrit.wikimedia.org/r/163029",1411680434,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,Looks like it is. Thanks!,1411670233,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,Have pointed it to https://www.mediawiki.org/wiki/Help:TemplateData instead – hope that's OK.,1411668181,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"James, if the link can't point to the local help page for each wiki, please redirect it to https://www.mediawiki.org/wiki/VisualEditor/Portal/TemplateData .",1411156930,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 134928 merged by jenkins-bot:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1409438730,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 134928 had a related patch set uploaded by Jforrester:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1409437169,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 134928 had a related patch set uploaded by Mooeypoo:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1406664777,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector","Steps to reproduce:
+
+1.Open a page with VE
+2.Open the language inspector
+3.Now Open the language selector dialog
+4.Select any language or just close the dialog
+
+Observed Result:
+The following error appears in the console:
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds
+
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404756540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cjhmjbqvl2impaei6gum,task_description,resolved
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector",Verified the fix in production en.wiki,1406316738,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector",Verified the fix in test2,1405724138,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector",Verified the fix in Betalabs,1405545794,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector","Yeah, fixed probably by Trevor's re-write of windows.",1405439083,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector",Appears to be fixed in master.,1405426136,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+VisualEditor: Snowmen appearing for some reason,"https://pt.wikipedia.org/w/index.php?diff=39208742
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404736800,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-fj2r7bnjbarkjkyc42pf,task_description,resolved
+VisualEditor: Snowmen appearing for some reason,"Merging with bug 57884 then.
+
+*** This bug has been marked as a duplicate of bug 57884 ***",1404767562,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fj2r7bnjbarkjkyc42pf,task_subcomment,NA
+VisualEditor: Snowmen appearing for some reason,Not really. I found that page by chance (while playing the Wikidata Game).,1404764786,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-fj2r7bnjbarkjkyc42pf,task_subcomment,NA
+VisualEditor: Snowmen appearing for some reason,Any reproduction steps? :-(,1404762943,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fj2r7bnjbarkjkyc42pf,task_subcomment,NA
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,"See at http://en.wikipedia.beta.wmflabs.org/wiki/0.37197036937123?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404562920,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vebbfxury34xj3qnszdg,task_description,resolved
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,"Change 816703 had a related patch set uploaded (by Xqt; author: Xqt):
+%%%[pywikibot/core@master] [BUGFIX] Add localized ""archive"" variables to archivebot.py%%%
+https://gerrit.wikimedia.org/r/816703",1658737382,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vebbfxury34xj3qnszdg,task_subcomment,NA
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,"Change 144136 merged by jenkins-bot:
+Fixes to getRelativeOffset and getRelativeRange
+
+https://gerrit.wikimedia.org/r/144136",1405445152,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vebbfxury34xj3qnszdg,task_subcomment,NA
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,"Change 144136 had a related patch set uploaded by Esanders:
+Fixes to getRelativeOffset and getRelativeRange
+
+https://gerrit.wikimedia.org/r/144136",1405019105,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vebbfxury34xj3qnszdg,task_subcomment,NA
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,Also pressing left in the first slug takes you forward.,1404563023,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vebbfxury34xj3qnszdg,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,"Currently Hovercards just takes the title attribute and uses that value as the article that it wants to preview.
+
+This does not handle many types of links, nor is not very reliable in combination with image links.
+
+Hovering an image like: [[File:S can.gif|18px|link=Cancer (astrology)|Cancer]] Will show you the article 'Cancer' instead of 'Cancer (astrology)' for instance, because inline images set their link title attribute to the caption.
+
+
+A link interpreter is also much more flexible and would be able to identify, different types of links.
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1404379320,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-dbp5fnytgn27ydme3c6e,task_description,resolved
+Hovercards: Use a link interpreter instead of title attribute,"As @ricordisamoa points out, we did switch to using a link interpreter when @wctaiwan fixed {T93605}. ",1444923799,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,">>! In T69466#1691123, @Ricordisamoa wrote:
+> I'm not aware of any steps that could be made to improve the status quo without needing Parsoid
+
+BTW, according to [[ //www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Wiki_links | spec ]], Parsoid does nothing to make parsing the title easier, in fact here's what VisualEditor does:
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/867c63e9b235968f2a9f92c75b483b719b222609/modules/ve-mw/dm/annotations/ve.dm.MWInternalLinkAnnotation.js#L92",1443649219,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,">>! In T69466#1690148, @Jdlrobson wrote:
+> Thanks for the clarification @Ricordisamoa but still `href` is not ideal. Can you update the title/description accordingly?
+
+I'm not aware of any steps that could be made to improve the status quo without needing Parsoid (which would be very bad for small wikis) or T40598.
+And after all, the current mechanism is kind of a link interpreter already.",1443648123,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,Thanks for the clarification @Ricordisamoa but still `href` is not ideal. Can you update the title/description accordingly?,1443634812,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,">>! In T69466#1681893, @Jdlrobson wrote:
+> To obtain the title of the page associated with the wiki link it relies on the title attribute, which is sometimes accurate.
+
+Wrong. It has been relying on href since https://gerrit.wikimedia.org/r/199694.",1443580273,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,"So my interpretation of this is:
+Hovercards hijacks wiki links and gives a preview of the pages they refer to to save clicks to them.
+To obtain the title of the page associated with the wiki link it relies on the title attribute, which is sometimes accurate.
+My question is, does Parsoid mark up links so that it is clear which page title they relate to?
+",1443461847,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,">>! In T69466#1681157, @Jdlrobson wrote:
+> @ssastry I assume this is something Parsoid solves? If we used Parsoid as the main parser would this be given for free? 
+
+I don't fully understand how hovercards work, but from the description, it looks like it relies on the title attribute? Right now, Parsoid doesn't set the title attribute for images.
+
+But, the description / title also says ""link intepreter"" and I don't know what that means either.
+
+So, need more specifics about what hovercards needs to function properly and we can talk more if Parsoid can support that out of the box.
+",1443461723,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,@ssastry I assume this is something Parsoid solves? If we used Parsoid as the main parser would this be given for free? ,1443454894,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,@ssastry I assume this is something Parsoid solves? If we switched Hovercards to use a Parsoid based service would this solve this problem?,1443454824,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged","Screenshot
+
+1.Open a page with VE
+2.Select an image
+3.Click on the ""Change Image"" button
+4.It will take you back to the Media Search dialog box
+
+
+Observed Result:
+Observe that,the ""Apply Changes"" button is enabled on the search dialog box
+Clicking on that will not have any effect.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14223}",1404346260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iu3lzoun25ro22ahnfsl,task_description,resolved
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged",Verified the fix in production,1405028848,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iu3lzoun25ro22ahnfsl,task_subcomment,NA
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged",Verified the fix in test2,1404422235,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iu3lzoun25ro22ahnfsl,task_subcomment,NA
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged","Change 143749 merged by jenkins-bot:
+UX Improvements to the Media Dialog
+
+https://gerrit.wikimedia.org/r/143749",1404350085,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iu3lzoun25ro22ahnfsl,task_subcomment,NA
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged","Change 143749 had a related patch set uploaded by Jforrester:
+UX Improvements to the Media Dialog
+
+https://gerrit.wikimedia.org/r/143749",1404348184,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iu3lzoun25ro22ahnfsl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Type a text
+3.Select the text
+4.Open the link inspector to apply link on it
+5.Type something inside the link inspector
+
+Observed Result:
+No link suggestions are appearing in the link inspector.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14198}",1404334680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7mhhjati7jq7vehinugh,task_description,resolved
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,Verified the fix in Betalabs,1411066338,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Change 161150 merged by jenkins-bot:
+Followup 6c862e8: position before AND after showing in TextInputMenuWidget
+
+https://gerrit.wikimedia.org/r/161150",1411002301,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Change 161150 had a related patch set uploaded by Catrope:
+Followup 6c862e8: position before AND after showing in TextInputMenuWidget
+
+https://gerrit.wikimedia.org/r/161150",1411001944,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,This got broken again apparently in last few hours.,1410999140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,Verified the fix in production,1405028895,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,Verified the fix in test2,1404421697,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,Verified the fix in Betalabs,1404409597,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Change 143782 merged by jenkins-bot:
+Followup 96ff968: use this.$element after it's initialized, not before
+
+https://gerrit.wikimedia.org/r/143782",1404341858,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Change 143782 had a related patch set uploaded by Catrope:
+Followup 96ff968: use this.$element after it's initialized, not before
+
+https://gerrit.wikimedia.org/r/143782",1404341374,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor Mobile: references context selection is wonky,"It's pretty much impossible to open the references context toolbar to edit an existing reference.
+
+Steps to reproduce:
+
+1. Open an article in VE editing mode on an iPad
+2. Tap on any reference footnote in the body of the article – sometimes the reference context toolbar appears, sometimes it doesn't, and sometimes it appears for a second and scrolls away.
+3. If you've managed to get the reference context toolbar to appear, tap it – sometimes it takes you to the link inspector, and sometimes it takes you to a new blank citation form
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67390
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67637",1404329700,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-ffazj5r46gg74oi7gacd,task_description,resolved
+VisualEditor Mobile: references context selection is wonky,Looks like this is now fixed thanks to Juliusz's new context menu changes.,1406747326,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ffazj5r46gg74oi7gacd,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"Copied from my Russian Wikipedia talk page:
+
+After reference VE added symbol ""♙"".
+
+sample for https://ru.wikipedia.org/w/index.php?title=Гёрлфренд&oldid=58928673&veaction=edit
+
+find ref№3 -> ""к подруге.[3]""
+click after the dot -> ""к подруге.|[3]""
+delete the dot with backspace  back  ->""к подруге|[3]""
+press en:Arrow keys  →  two times ->""к подруге[3]|""
+press key dot  .  ->
+expected that will be shown the symbol ""."" -> ""к подруге[3].|""
+but it shows the symbol ""♙"" ->""к подруге[3]♙|""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404328260,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-vggdj3oaoiimjl76co4b,task_description,resolved
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"Change 145346 merged by jenkins-bot:
+Make sure the document is focused when setting a selection
+
+https://gerrit.wikimedia.org/r/145346",1405383662,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,Upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1037004,1405008743,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"Change 145346 had a related patch set uploaded by Esanders:
+Make sure the document is focused when setting a selection
+
+https://gerrit.wikimedia.org/r/145346",1405007554,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,Monitoring document.activeElement (the currently focussed element) it's apparent that simply setting a selection on the document (back from the paste target) doesn't changed the focussed element. This means you can move your cursor in one textbox and type in another. What the hell Firefox...,1405006352,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"This happens just by typing anything after an inline focusable node after cursoring off it (nothing to do with deletion). If the node is at the end of a paragraph you get a pawn, but if it isn't you get equally broken behaviour with the cursor not moving properly.",1404942081,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"(In reply to Elitre from comment #2)
+> If this happens in FF, can it be related to bug 54917?
+
+Doesn't look like it; this was caused by insertion, not cursoring.",1404760957,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"If this happens in FF, can it be related to bug 54917?",1404738178,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,Sounds like a VE issue. Moving there.,1404328383,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media and select any image after searching
+
+Observed Result:
+When the Media settings dialog pop-up, observe that all the icons for the tabs General Settings, Advanced Settings and the headings Caption,Alternative text, Position,Image Type, Image Size etc are missing
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14179}",1404325620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-erh6pdj44sgbbysd6pck,task_description,resolved
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,Verified the fix in production,1405028578,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-erh6pdj44sgbbysd6pck,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,Verified the fix in betalabs and test2,1404769312,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-erh6pdj44sgbbysd6pck,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,Almost certainly a Beta Labs problem of the moment.,1404331449,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-erh6pdj44sgbbysd6pck,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,"This is also happening for Basic reference, cite news , cite journal and reference list dialog as well.",1404326088,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-erh6pdj44sgbbysd6pck,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the semi-highlight is still happening on selection of a node when there is no text cursor activation upon opening a page on Mobile VE","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Do not place your cursor anywhere on CE but try to select a node 
+Observed Result:
+The semi-highlight of lighter shade appears over the node and tapping on it for the second time selects it with darker highlight.
+
+It might get resolved with :https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+
+Still I am filing it as a separate issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+
+**Attached**: {F14690}",1404249300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cwv4uf7sks54skkmccyq,task_description,resolved
+"VisualEditor Mobile: In iOS Safari, the semi-highlight is still happening on selection of a node when there is no text cursor activation upon opening a page on Mobile VE",Verified the fix in production,1405626233,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cwv4uf7sks54skkmccyq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the semi-highlight is still happening on selection of a node when there is no text cursor activation upon opening a page on Mobile VE","This is not happening anymore,Checked in Betalabs and test2 .
+Marking it as fixed",1404780385,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cwv4uf7sks54skkmccyq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, after adding a link, the cursor still blinks on CE in the position where it was appearing inside the search box for link inspector","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE in iOS Safari
+2.Select a text
+3.Click on the link icon from the toolbar
+4.Type a link target page inside link inspector and apply it
+
+Observed Result:
+The cursor that was appearing inside the search box of a link inspector remains on the screen appearing over the title of the page
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14689}",1404245460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hzeisownarrcldmlrur4,task_description,resolved
+"VisualEditor Mobile: In iOS Safari, after adding a link, the cursor still blinks on CE in the position where it was appearing inside the search box for link inspector",Verified the fix in production en.wiki,1406318823,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hzeisownarrcldmlrur4,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, after adding a link, the cursor still blinks on CE in the position where it was appearing inside the search box for link inspector",Verified the fix in test2,1405719892,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hzeisownarrcldmlrur4,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, after adding a link, the cursor still blinks on CE in the position where it was appearing inside the search box for link inspector",Fixed by Trevor's mobile styling work.,1405558544,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hzeisownarrcldmlrur4,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Type a template name such as ""Cite Web""
+
+Observed Result:
+In the template suggestion drop dwon box all template names are appearing with a prefix ""Template:""
+
+See the screenshot attached
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14680}",1404242520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_description,resolved
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box",Verified the fix in production,1405028961,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box",Verified the fix in test2,1404421631,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box",Verified the fix in Betalabs,1404409700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box","Change 143685 merged by jenkins-bot:
+Try some more to handle template namespace properly
+
+https://gerrit.wikimedia.org/r/143685",1404350629,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box","Change 143685 had a related patch set uploaded by Alex Monk:
+Try some more to handle template namespace properly
+
+https://gerrit.wikimedia.org/r/143685",1404330111,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Writing https://gerrit.wikimedia.org/r/143322 , I realized that the `ve.ce.isShortcutKey( e )` check in ve.ce.Surface (which rejects every keypress event where Ctrl or Cmd is pressed) sometimes prevent legit keypresses from being handled.
+
+To reproduce (in any browser):
+
+* Place cursor on an empty line.
+* Input 'ą' ([[ą]]). This is accomplished by pressing AltGr+a (right Alt+a, Alt+Ctrl+a) when using the ""Polish (Programmers)"" keyboard layout on Windows 7 (this is the default layout for Polish).
+* Type in something else. The 'ą' disappears, because it was never handled by ve.ce, only by native contenteditable element.
+
+I only tested this on Windows 7, but I believe other operating systems all use the same method. Other letters with diacritics from the [[Polish alphabet]] are input in the same way (AltGr + base key), we have nine of them.
+
+On Windows 7 you can enable this keyboard layout by typing ""keyboard layout"" into the Start menu, choosing ""Change keyboards…"" and adding the input method.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404226500,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2fo2vepgfvoop6cua3yb,task_description,resolved
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),Proper fixed!,1419338125,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Change 181174 merged by jenkins-bot:
+ve.ce: Remove hacks from Surface#onDocumentKeyPress; add related IME test
+
+[[https://gerrit.wikimedia.org/r/181174]]",1419335362,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Change 181173 merged by jenkins-bot:
+imetests: Add a regression test for Polish keyboard input
+
+[[https://gerrit.wikimedia.org/r/181173]]",1419335358,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Change 181174 had a related patch set uploaded (by Bartosz Dziewoński):
+ve.ce: Remove hacks from Surface#onDocumentKeyPress, add related IME test
+
+[[https://gerrit.wikimedia.org/r/181174]]
+
+#patch-for-review",1419026959,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Change 181173 had a related patch set uploaded (by Bartosz Dziewoński):
+imetests: Add a regression test for Polish keyboard input
+
+[[https://gerrit.wikimedia.org/r/181173]]
+
+#patch-for-review",1419026957,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),Let's do that.,1419026098,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),Yes! See fakeIMETests. Please use the script to generate a previously-failing test case so we lock this in. :-),1419021276,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"This no longer happens. Just for the kicks I bisected and found that the commit that fixed the bug is 40101e42a4544768ac624ef2b4da0e7d44b69b65 (https://gerrit.wikimedia.org/r/#/c/151046/).
+
+I wonder if we could have a browser test to prevent this from regressing? (It was fixed accidentally, could be broken accidentally again.)
+
+I also wonder if we need the checks in `ve.ce.Surface.prototype.onDocumentKeyPress` at all anymore? Removing them doesn't seem to cause the issue they're supposed to prevent (""Unexpected content deletion when selection is not collapsed and the user presses, for example, the Home key (Firefox fires 'keypress' for it)"").",1419020102,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Hmph, we can't kill this code yet. It's not just to prevent pawning, it's also to prevent the selection from being deleted when you press a shortcut key. We'll need David's next project (prepare-observe-fixup) to be done before we can get rid of this, I think.",1413940427,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),I can still reproduce on betalabs.,1413746460,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"(In reply to Roan Kattouw from comment #2)
+> (In reply to James Forrester from comment #1)
+> > Is this now fixed, given that we've killed pawns?
+> 
+> We haven't quite killed them yet, the chimera commit does that.
+
+But we should make sure that that commit also kills this logic; which right now I'm not sure that it does.",1413329653,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"(In reply to James Forrester from comment #1)
+> Is this now fixed, given that we've killed pawns?
+
+We haven't quite killed them yet, the chimera commit does that.",1413329628,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Is this now fixed, given that we've killed pawns?",1413329572,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a reference
+3.Go to the option Use an existing reference
+
+Observed Result:
+In the dialog for using an existing reference, the reference name for the reference just added is missing just the reference number appears inside the bracket.
+Opening it for the second time brings up the reference name
+
+See the screenshot attached
+
+Environment:http://en.m.wikipedia.beta.wmflabs.org/
+Both on Desktop browser and iOS Device
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68869
+
+**Attached**: {F14576}",1404175680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-povdwehsnsp3g7l76hmb,task_description,resolved
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time",Verified the fix in production for both desktop and mobile,1408046784,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time",Verified the fix in test2,1407192494,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time",Should be solved.,1406765032,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time","Change 150736 merged by jenkins-bot:
+Don't clone internal item node element used for references in re-use citation dialog
+
+https://gerrit.wikimedia.org/r/150736",1406764794,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time","Change 150736 had a related patch set uploaded by Alex Monk:
+Don't clone internal item node element used for references in re-use citation dialog
+
+https://gerrit.wikimedia.org/r/150736",1406764576,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time","This is happening in desktop as well , not when you add Basic reference but cite references.",1406677463,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"**Author:** `oliver.buchtala`
+
+**Description:**
+Probably a matter of taste, but we find the embedded control not too appealing.
+In our case (a block equation) the button to open the inspector is typically below. However, when the element is growing (2+ lines), it is suddenly on the right-hand side.
+
+It would be great if there was a way to control that and override the present behavior if desired.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404139740,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hiqmkuftu6tynmzgz27e,task_description,resolved
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"
+
+*** This bug has been marked as a duplicate of bug 66542 ***",1408710950,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"The original request was about optional disabling embedding, but this I suppose ""fixes"" the issue (though really that was bug 66542).",1404248899,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"Change 143393 merged by jenkins-bot:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/143393",1404247814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"Change 143393 had a related patch set uploaded by Esanders:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/143393",1404245015,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"It would be nice to keep it consistent, although for a live-updating node it would certainly make sense to keep the context menu out of the way (at least when it is open).",1404232676,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor Mobile: Focusable nodes can't be deleted,"(Chrome mobile)
+Clicking on a focusable node doesn't bring up the keyboard so there is no access to the backspace key. Even if you click on text then the focusable node, the backspace key doesn't work.
+
+Regardless a mobile user would expect to have a separate control for deleting focusable nodes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403981520,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ulr4ihyno7bftkrdq7gf,task_description,resolved
+VisualEditor Mobile: Focusable nodes can't be deleted,"Same problem as on iOS. Merging.
+
+*** This bug has been marked as a duplicate of bug 60110 ***",1407064915,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ulr4ihyno7bftkrdq7gf,task_subcomment,NA
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it","The same node sometimes is deleted and sometimes isn't. Appears to apply to block and inline nodes alike. Can't work out exact reproduction steps. Race condition?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403829360,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ewm6busofenduqisc4ug,task_description,resolved
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it","Change 142527 merged by jenkins-bot:
+Always refocus the paste target when a node is selected
+
+https://gerrit.wikimedia.org/r/142527",1403889430,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ewm6busofenduqisc4ug,task_subcomment,NA
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it","Change 142527 had a related patch set uploaded by Esanders:
+Always refocus the paste target when a node is selected
+
+https://gerrit.wikimedia.org/r/142527",1403878950,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ewm6busofenduqisc4ug,task_subcomment,NA
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it",I can reproduce by clicking directly from one node to another. Looks like a focus issue.,1403862835,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ewm6busofenduqisc4ug,task_subcomment,NA
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it","Definitely no clean repro - comes and goes as you click on templates. But once it stops working in a session, it seems to stop for good.",1403830621,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ewm6busofenduqisc4ug,task_subcomment,NA
+VisualEditor: Typing when a focusable node is selected should do nothing,"Correct outcome:
+
+* Select an inline image (or a reference or alien or…).
+* Press ""a"".
+
+Observe that the reference has been deleted, and an 'a' is in its place.
+
+
+Bad outcome;
+
+* Select a block image (or block template or…).
+* Press ""a"".
+
+Observe that the block image has not been deleted, and the 'a' is not in its place (and no transaction has occurred).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403829240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zjrtgmgipdtxr4pdqjch,task_description,resolved
+VisualEditor: Typing when a focusable node is selected should do nothing,"Change 146808 merged by jenkins-bot:
+Prevent deletion of focusable nodes by typing
+
+https://gerrit.wikimedia.org/r/146808",1405551075,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zjrtgmgipdtxr4pdqjch,task_subcomment,NA
+VisualEditor: Typing when a focusable node is selected should do nothing,"Change 146808 had a related patch set uploaded by Esanders:
+Prevent deletion of focusable nodes by typing
+
+https://gerrit.wikimedia.org/r/146808",1405529411,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zjrtgmgipdtxr4pdqjch,task_subcomment,NA
+VisualEditor: Typing when a focusable node is selected should do nothing,"Real world comparison:
+* Open/Libre office: typing while selecting an image does nothing
+* Google docs: typing replaces the image
+
+I think it's a rare workflow where you select a block image and want to replace it with a paragraph, and if you really do you can just press backspace/delete. We have taken other measures to prevent the accidental deletion of focusable nodes elsewhere (e.g. adjacent backspace only selects) so this seems like a logical extension.",1405529394,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zjrtgmgipdtxr4pdqjch,task_subcomment,NA
+VisualEditor: Double-click should not open items that shouldn't be opened,"References defined inside a {{reflist}} aren't editable – but double-click now opens the reference dialog (to empty content).
+
+I imagine this happens for a few things.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403829060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utovzemiq3m7agsxe4zz,task_description,resolved
+VisualEditor: Double-click should not open items that shouldn't be opened,"Change 143352 merged by jenkins-bot:
+Hide context tools when the model they match isn't ""inspectable""
+
+https://gerrit.wikimedia.org/r/143352",1404249479,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-utovzemiq3m7agsxe4zz,task_subcomment,NA
+VisualEditor: Double-click should not open items that shouldn't be opened,"Change 143352 had a related patch set uploaded by Esanders:
+Hide context tools when the model they match isn't ""inspectable""
+
+https://gerrit.wikimedia.org/r/143352",1404234623,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-utovzemiq3m7agsxe4zz,task_subcomment,NA
+VisualEditor: Double-click should not open items that shouldn't be opened,"(In reply to Ed Sanders from comment #1)
+> Link to an example?
+
+First reference on https://en.wikipedia.org/wiki/Anne_Dallas_Dudley?veaction=edit – appears to be an issue with references more generally, and affects the context too. Bother.",1403987115,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utovzemiq3m7agsxe4zz,task_subcomment,NA
+VisualEditor: Double-click should not open items that shouldn't be opened,Link to an example?,1403968584,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-utovzemiq3m7agsxe4zz,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"I have tried running the unit tests with both Echo and Math installed and ends up with a database error:
+
+```
+$ ls -1 extensions
+Echo
+Math
+README
+```
+
+```
+$ cd tests/phpunit
+$ php phpunit.php --tap --testsuite extensions
+not ok 588 - Error: MathDatabaseTest::testCreateTable
+A database query error has occurred.
+Query: DELETE FROM unittest_math
+Function: MediaWikiTestCase::resetDB
+Error: 1 no such table: unittest_math
+
+
+---
+
+#0 /core/includes/db/Database.php(1134): DatabaseBase->reportQueryError('no such table: ...', 1, 'DELETE FROM uni...', 'MediaWikiTestCa...', false)
+#1 /core/includes/db/Database.php(2919): DatabaseBase->query('DELETE FROM uni...', 'MediaWikiTestCa...')
+#2 /core/tests/phpunit/MediaWikiTestCase.php(572): DatabaseBase->delete('math', '*', 'MediaWikiTestCa...')
+#3 /core/tests/phpunit/MediaWikiTestCase.php(138): MediaWikiTestCase->resetDB()
+#4 /pear/PHPUnit/Framework/TestSuite.php(775): MediaWikiTestCase->run(Object(PHPUnit_Framework_TestResult))
+#5 /pear/PHPUnit/Framework/TestSuite.php(745): PHPUnit_Framework_TestSuite->runTest(Object(MathDatabaseTest), Object(PHPUnit_Framework_TestResult))
+#6 /pear/PHPUnit/Framework/TestSuite.php(705): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)
+#7 /pear/PHPUnit/Framework/TestSuite.php(705): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)
+#8 /pear/PHPUnit/Framework/TestSuite.php(705): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)
+#9 /pear/PHPUnit/TextUI/TestRunner.php(349): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)
+#10 /pear/PHPUnit/TextUI/Command.php(176): PHPUnit_TextUI_TestRunner->doRun(Object(PHPUnit_Framework_TestSuite), Array)
+#11 /core/tests/phpunit/MediaWikiPHPUnitCommand.php(42): PHPUnit_TextUI_Command->run(Array, true)
+#12 /core/tests/phpunit/phpunit.php(160): MediaWikiPHPUnitCommand::main()
+#13 {main}
+```
+
+
+Also the Math extension seems to be running the updater in the test.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403805420,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_description,resolved
+Math tests dies when run with the Echo extensions,"This original problem reported seems to be fixed now.
+Hoever, there is another unrelated error
+```
+ok 948 - ResourcesTest::testStyleMedia with data set #13 ('skins.vector.styles', 'screen and (min-width: 982px)', 'screen-hd.less', stdClass Object (...))
+ok 949 - ResourcesTest::testIllegalDependencies
+not ok 950 - Failure: ResourcesTest::testMissingDependencies
+  ---
+  message: 'The module ''ext.visualEditor.mwcore'' required by ''ext.math.visualEditor'' must exist'
+  severity: fail
+  ...
+not ok 951 - Error: ResourcesTest::testUnsatisfiableDependencies
+ok 952 - ResourcesTest::testMediaWikiTestCaseParentSetupCalled
+```",1420904055,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"This original problem reported seems to be fixed now.
+However changing the order or inclusion in the way that math is included before echo leads to the following error
+```
+ok 948 - ResourcesTest::testStyleMedia with data set #13 ('skins.vector.styles', 'screen and (min-width: 982px)', 'screen-hd.less', stdClass Object (...))
+ok 949 - ResourcesTest::testIllegalDependencies
+not ok 950 - Failure: ResourcesTest::testMissingDependencies
+  ---
+  message: 'The module ''ext.visualEditor.mwcore'' required by ''ext.math.visualEditor'' must exist'
+  severity: fail
+  ...
+not ok 951 - Error: ResourcesTest::testUnsatisfiableDependencies
+ok 952 - ResourcesTest::testMediaWikiTestCaseParentSetupCalled
+```
+And the number of tests that were executed reduces from 1818 to 1547",1420902798,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Would need to be tried again, it might have been fixed.",1420837178,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"**physik** wrote:
+
+This Bug is not related to the math extension.
+My experience is the following
+At first I could reproduce a similar error as reported in the bug report. But the error indicated that database access related to the echo extension caused the error.
+To investigate further I changed the order in the Localsettings.php an loaded Math before echo.
+I wanted to reproduce exactly the problem that you had reported before. But no error occurred. After switching the order back the error did not come back.
+AS a result I think the error is not related to the Math extension, rather to the sqllite db backend. Especially given the fact that the error does not occur with mysql",1406420211,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,*** Bug 68628 has been marked as a duplicate of this bug. ***,1406408729,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Still the same error with latest master of Math Echo and core:
+
+not ok 588 - Error: MathDatabaseTest::testCreateTable
+A database query error has occurred.
+Query: DELETE FROM unittest_math
+Function: MediaWikiTestCase::resetDB
+Error: 1 no such table: unittest_math",1406274723,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Antoine, is it fine for you now?",1406247567,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Change 142739 merged by jenkins-bot:
+Fix MathDatabaseTest
+
+https://gerrit.wikimedia.org/r/142739",1405042641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,Sure! See comment 1. Install a stock MediaWiki core with extensions Echo and Math.  That should trigger the issue.,1404145580,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"**physik** wrote:
+
+does the problem disappear if you disable the Echo module?
+Are those tests using sqlite?",1404140080,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,We really need tests to pass when all wmf extensions are installed together. That is preventing us from progression toward the HHVM migrating. Raising priority to High.,1404137324,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Change 142739 had a related patch set uploaded by Physikerwelt:
+Fix MathDatabaseTest
+
+https://gerrit.wikimedia.org/r/142739",1403907884,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"I did ran update.php
+
+A slightly more complicated test I ran in Jenkins is:
+
+https://integration.wikimedia.org/ci/job/mediawiki-core-extensions-integration/38/consoleFull
+
+
+It clones a bunch of extensions, load their entry points then run install.php and then update.php
+
+ 00:01:04.861 Creating math table ...done.
+
+
+The dberror:
+
+ Thu Jun 26 16:15:01 UTC 2014	gallium	build38-unittest_	MediaWikiTestCase::resetDB		1	no such table: unittest_math	DELETE FROM unittest_math",1403898654,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"**physik** wrote:
+
+did you run update.php before?
+As far as I understand the database tests copy the schema with and prefix the tables with untitest. If there is no math table in the base schema no table will be created in the copied unittest schema.
+The database test tries to delete the test schema and creates a new one.
+We should either improve the error message or ignore the missing math table in the  main database. I don't know which option is better?",1403887803,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"tests/MathDatabaseTest.php has:
+
+ public function testCreateTable() {
+  ...
+  $dbu->doUpdates( array( ""extensions"" ) );
+  ...
+
+among other. Commenting out the function let us continue the test suite.",1403805649,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+VisualEditor: Cursor is appearing in the read mode in Firefox after canceling the edit in VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in FireFox
+2.Without editing just click on ""Cancel"" button 
+
+Observed Result:
+The cursor is still appearing at the end of the page in read mode.
+
+See the screenshot attached
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14619}",1403739000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zvw4nqatdijriyfaposh,task_description,resolved
+VisualEditor: Cursor is appearing in the read mode in Firefox after canceling the edit in VE,I think we fixed this a long time ago (and then it recurred and we fixed that one too).,1416794925,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvw4nqatdijriyfaposh,task_subcomment,NA
+VisualEditor: Cursor is appearing in the read mode in Firefox after canceling the edit in VE,"This is happening in production now, so environment is not just Betalabs now.",1403892554,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zvw4nqatdijriyfaposh,task_subcomment,NA
+VisualEditor: [Regression] Pawn appears when inserting a link (no preselected text) and implicitly exiting from the inspector,"(from bug 67086)
+
+1. Press ""Link"" tool.
+2. Enter a link target (url or page name).
+3. Select the url or page name from the suggestions.
+- Notice that the surface still shows your blinking cursor with no link or text
+4. Click back into the surface and type text.
+
+Expected behaviour:
+
+The link becomes a pre-annotation and the entered text the label.
+Or, alternatively, the link autosaves and inserts itself and my text appears after the link.
+
+Actual behaviour:
+
+* First character is eaten.
+* Link is inserted.
+* First character of link is unlinked.
+* Pawn appears.
+* Second and further characters inserted will remove the link and insert plain text
+
+See http://cl.ly/3s460Q442L3S
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68590",1403714880,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fxbpehdnotnzwpki3qwo,task_description,resolved
+VisualEditor: [Regression] Pawn appears when inserting a link (no preselected text) and implicitly exiting from the inspector,"No longer an issue (Trevor-rewrite probably), but bug 68590 is a related problem.",1406324569,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fxbpehdnotnzwpki3qwo,task_subcomment,NA
+VisualEditor: [Regression] Pawn appears when inserting a link (no preselected text) and implicitly exiting from the inspector,"(In reply to Krinkle from comment #1)
+> Reduced test case video of only the steps for this bug (without existing
+> links before the list item):
+> 
+> http://cl.ly/2P2h473b2A20
+
+Dead link.
+
+Also, on step 3, my cursor is in the target box... Not the surface. Is this still valid with the window rewrite and everything?",1406322886,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-fxbpehdnotnzwpki3qwo,task_subcomment,NA
+VisualEditor: [Regression] Pawn appears when inserting a link (no preselected text) and implicitly exiting from the inspector,"Reduced test case video of only the steps for this bug (without existing links before the list item):
+
+http://cl.ly/2P2h473b2A20",1403715527,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fxbpehdnotnzwpki3qwo,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"Screenshot-1
+
+Steps to reproduce:
+
+1.Open a page with safari in any iOS device which contains image in it
+2.Now tap on the image to select it
+
+Observed Result:
+The highlight for the image is appearing much below the image 
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65326
+
+**Attached**: {F14511}",1403656560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dzlegd43ozkumznabj4b,task_description,resolved
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,Verified the fix in production,1405023725,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,Verified the fix in test2,1404777720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,Verified the fix in Betalabs.,1404160997,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"The highlight for images appearing in wrong position is now fixed ! :)
+However the tapping on link or image redirecting to the link target or image file page and second tap on reference closing the VE is still there.Therefore, I suppose the following bugs are not related:
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65326
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67002",1403894488,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"Change 142260 merged by jenkins-bot:
+FocusableNode: Use getClientRects()[0] instead of getBoundingClientRect()
+
+https://gerrit.wikimedia.org/r/142260",1403801793,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"Change 142260 had a related patch set uploaded by Esanders:
+Use getClientRects()[0] instead of getBoundingClientRect()
+
+https://gerrit.wikimedia.org/r/142260",1403798307,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,Want to write up a bug report for Apple?,1403791790,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,In every browser except iOS7 getClientRects is relative to the viewport. In iOS7 it is relative to document. Thanks Apple.,1403791536,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"Created attachment 15726
+Screenshot-2
+
+**Attached**: {F14512}",1403656610,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor: Highlight for multi-line inline template only applies to the first line of it,"It's easiest to understand this from the screenshot.  This is a display bug.
+
+Steps to reproduce:
+
+1.  Open a page containing a (long-ish) citation dialog.
+
+2.  Select the ref and go to Insert > References.
+
+3.  Select the citation template (e.g., to copy it).
+
+4.  Ask yourself, ""Why is only the first line of this template being selected?  Why is the cite tag in the middle instead of underneath the template?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14508}",1403656440,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-o6vqpx64l4l5tkaovklh,task_description,resolved
+VisualEditor: Highlight for multi-line inline template only applies to the first line of it,Works on beta labs.,1403696576,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o6vqpx64l4l5tkaovklh,task_subcomment,NA
+VisualEditor: Highlight for multi-line inline template only applies to the first line of it,"
+
+*** This bug has been marked as a duplicate of bug 52339 ***",1403696547,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o6vqpx64l4l5tkaovklh,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","https://www.mediawiki.org/wiki/VisualEditor:Test1234?veaction=edit
+
+Dragging the image on this page on Chrome Version 35.0.1916.153 on Mac OSX 10.9.3 does not relocate the image. The ""shadow"" and magic line appear as expected, but when the click is released the image does not move.
+
+The entire interaction works properly for me on latest Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1403632800,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_description,resolved
+"VisualEditor: On Chrome, new relocatable node does not work",Verified the fix in test2,1403909760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","Change 141949 merged by jenkins-bot:
+Cache block drop position data before setTimeout
+
+https://gerrit.wikimedia.org/r/141949",1403720170,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","Change 141949 had a related patch set uploaded by Esanders:
+Cache block drop position data before setTimeout
+
+https://gerrit.wikimedia.org/r/141949",1403700044,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","Update to my earlier comment. It's working for me on Firefox 30, Mac OSX 10.9.3",1403640324,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work",Works for me in Chrome 34 but broken for me in Firefox 30 (both on Ubuntu 14.04),1403639914,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","**kirkburn** wrote:
+
+https://www.mediawiki.org/wiki/VisualEditor:Test1234?veaction=edit
+
+Similarly, the interaction is not working for me on Chrome 35.0.1916.153 m on Windows 8.1 - I see the shadow and magic line, but nothing happens on mouseup.
+
+However, unlike Trevor, it is also not working for me in pre-release Firefox - on Firefox Aurora 32.0a2 (19-06-14), on Windows 8.1. No effect on mouseup.",1403633991,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"**Author:** `jgonera`
+
+**Description:**
+As mentioned in bug 66999 references require two taps on iOS Safari. Often, the first tap results in a lighter ""semi-selection"" appearing a bit below the actual reference. When that happens, second tap on the reference suddenly closes the editor (first video).
+
+The editor doesn't crash though, somehow cancel action is triggered. If you have unsaved changes, you'll see a dialog asking you if you want to abandon the edit (second video).
+
+Tested and recorder in iOS Safari 7.1.1. Does not happen on Chrome for Android.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66999
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65326",1403559480,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2o3jcx26svgc5z7twzye,task_description,resolved
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Verified the fix in production,1405023646,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Verified the fix in test2,1404778996,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Verified the fix in Betalabs,1404160135,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"This seems to got fixed by:
+
+Select highlights on touchend event
+
+https://gerrit.wikimedia.org/r/142839",1404160121,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"Ok, the behavior got slightly changed here, it wont close the VE now if your second tap on the same reference follows right after your first tap
+
+To reproduce it now you need to first tap on a reference say [1], then tap on another reference [2], then go back and tap [1].Now it will close the VE .",1403914344,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"For images, second tap on it opens up the image which might also be the effect of this same bug.",1403895522,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"This bug did not get fixed by :
+
+Use getClientRects()[0] instead of getBoundingClientRect()
+
+https://gerrit.wikimedia.org/r/142260",1403894552,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Probably (?) fixed by the fix to bug 67063.,1403806273,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Pushing to Ed because it appears to be a shield/highlight issue.,1403573089,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"**jgonera** wrote:
+
+Editor shows confirmation dialog
+
+**Attached**: {F14382}",1403559531,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"**jgonera** wrote:
+
+Editor closes
+
+**Attached**: {F14376}",1403559512,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"**Author:** `jgonera`
+
+**Description:**
+Double tap required
+
+If you open VE on mobile and want to edit an existing reference, you need to tap it twice. This is really hard, especially given that the tap target is quite small (which is a separate issue).
+
+Tested and recorder in iOS Safari 7.1.1. Does not happen on Chrome for Android (just a single tap needed there).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65326
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67002
+
+**Attached**: {F14364}",1403558880,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rsuk24lv6ttcz4hpew66,task_description,resolved
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Verified the fix in production,1405023590,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Verified the fix in test2,1404779121,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Verified the fix in Betalabs.,1404160006,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"Change 142839 merged by jenkins-bot:
+Select highlights on touchend event
+
+https://gerrit.wikimedia.org/r/142839",1404152414,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"Change 142839 had a related patch set uploaded by Esanders:
+Select highlights on touchend event
+
+https://gerrit.wikimedia.org/r/142839",1403992540,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"This bug did not get resolved by Ed's fix.
+
+The issue here is, the first tap is showing a lighter highlight which is equivalent to the hover effect in the desktop and for the second tap it is actually selecting that node.
+
+This is why, even if you have selected a reference (with two tap) , you can still semi-select another node (with lighter highlight)at the same time  
+
+For mobile, it should require one single tap to select any reference/image etc.",1403895969,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Looks like it's fixed by bug 67063's fix.,1403806238,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"(In reply to Ed Sanders from comment #3)
+> Isn't this fixed then (comment 1)?
+
+… no?
+
+Comment 1 says that the context being useless (""the tap target is quite small"") is  fixed by some other patches and you should ignore.
+
+Comment 0 is mostly about ""If you open VE on mobile and want to edit an existing reference, you need to tap it twice."" which remains a bug.",1403656022,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Isn't this fixed then (comment 1)?,1403624172,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Pushing to Ed because it appears to be a shield/highlight issue.,1403573091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"**jgonera** wrote:
+
+Ignore wrong positioning of mobile context (second toolbar), it's fixed now. To actually see the context though you need those patches:
+https://gerrit.wikimedia.org/r/#/c/141085/
+https://gerrit.wikimedia.org/r/#/c/141087/",1403560673,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Type a template name with matching suggestion in the text box
+
+Observed Result:
+There are no suggestions for template appearing in the dialog
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14341}",1403548200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rpfc6ad3ojppedslirip,task_description,resolved
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,Verified in production (en.wiki),1404767078,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rpfc6ad3ojppedslirip,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,Verified in test2,1403907204,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rpfc6ad3ojppedslirip,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,This is fixed now.,1403639996,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rpfc6ad3ojppedslirip,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,*** Bug 66981 has been marked as a duplicate of this bug. ***,1403550337,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rpfc6ad3ojppedslirip,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","1. Edit [[mw:API:Meta]] in VisualEditor
+2. Select the ""MediaWiki version 1.8"" template
+
+A popup appears showing the template's correct name (""MW 1.8"").
+
+3. Open the transclusion editor for the template
+
+VE thinks it is editing a template called ""MW 1"".
+
+Also note that when you try to insert a template with a period in its name, like ""MW 1.8"", you get a whole lot of suggestions for ""MW 1"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403416680,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-tth52wedfhhza5omlooc,task_description,resolved
+"VisualEditor: When editing a template, the title is truncated at first dot (period)",Should be fixed now.,1403827141,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","Change 142372 merged by jenkins-bot:
+Don't remove 'extension' from template names
+
+https://gerrit.wikimedia.org/r/142372",1403826426,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","Change 142372 had a related patch set uploaded by Alex Monk:
+Don't remove 'extension' from template names
+
+https://gerrit.wikimedia.org/r/142372",1403811538,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","Yeah, I worked that out soon after moving the bug.
+
+Still, I wonder if the documentation should be improved for those methods.",1403804486,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","btw, This is a compatibility/legacy left-over from when mw.Title was part of UploadWizard and they got dibs on the more intuitive name ""getNameText"". Unfortunately this mistake was not uncovered until after it was merged in mediawiki-core and released in an LTS.",1403804456,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","getNameText() explicitly leaves out any faux extension. That's by design. To get the page title, use getMainText.
+
+
+https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.Title-method-getNameText",1403804231,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","Yep.
+
+mw.Title.newFromText( 'Template:Asd.com' ).getNameText()
+""Asd""",1403804143,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)",I blame mwTitle. Because it's always at fault.,1403741920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"Until Parsoid removes metadata, large articles are going to consist of several megabytes of data (en:Barack_Obama = 3.4MiB). As browsers doesn't provide any mechanism for compressing post data, this is takes about 20s to upload on a typical 1Mbps up ADSL line.
+
+Using a JS implementation of deflate, we could achieve 80-90% compression in a few hundred ms on a decent machine: http://jsperf.com/js-deflate
+
+A couple of considerations with performing such a complex calculation in pure JS:
+
+* Really bad JS engines or slow devices (old browsers, IE, mobile) may offer to little to overall speed benefit. We may want to detect these cases by user agent or performance profiling.
+* The compression function will be synchronous and lock browser interaction. On slower machines this may give the appearance of crashing, or with memory leaks may actually crash. If this proves to be a significant problem we could look into encoding in chunks of 100k at a time so we could at least provide progress, and maybe improve memory usage (at the cost of overall compression).
+
+--------------------------
+
+**See Also**:
+* {T61659}
+* {T61660}
+* {T66171}",1403358000,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_description,resolved
+VisualEditor: Compress POST data in the client,"Change 141678 merged by jenkins-bot:
+Compress HTML data with deflate before POSTing
+
+https://gerrit.wikimedia.org/r/141678",1404171798,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"(In reply to Ed Sanders from comment #0)
+> * The compression function will be synchronous and lock browser interaction.
+
+You could look at doing it asynchronously in the background, with a Web Worker (i.e. thread) (https://developer.mozilla.org/en-US/docs/Web/API/Worker), in supported browsers (IE 10+, and Firefox/Chrome/Safari/Opera going back pretty far).",1403908962,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,*** Bug 59659 has been marked as a duplicate of this bug. ***,1403735953,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"There are a number of things we can do to avoid this heavy payload:
+* Section editing
+* Separating Parsoid metadata
+* Sending differential linmod data using a server-side converter
+
+None of these are ready or close to being ready yet, and 20s to save a page is fairly significant problem in the present that compression can mitigate.",1403623965,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"Change 141678 had a related patch set uploaded by Esanders:
+Compress HTML data with deflate before POSTing
+
+https://gerrit.wikimedia.org/r/141678",1403614511,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"Supporting section editing (bug 48429), and submitting only modified section to the server, might be a better way to increase performance.",1403358178,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,"Screenshot
+
+Formula icon is missing in the Insert menu
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14131}",1403295660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cn7ribouyrqugmfcsow6,task_description,resolved
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,Verified in production (en.wiki),1404766986,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,Verified in test2,1403907529,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,Works in Betalabs too now.,1403569456,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,"Definitely works in master, must be a deployment issue.",1403352413,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,Did the registration in the Math extension not work?,1403296660,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image
+3.Open the Media Settings dialog for the image
+4.Go to Advanced Settings tab
+5.Click on ""Make full size""
+
+Observed Result:
+It switches to the Custom tab and keeps the size value as default instead of making it full size.
+
+Environment:Betalabs,test2, en.wiki
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403221860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_description,resolved
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix in production,1405625779,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix in test2,1405036608,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix in Betalabs,1404865261,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 144637 merged by jenkins-bot:
+Apply 'original size' to images
+
+https://gerrit.wikimedia.org/r/144637",1404842132,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 144638 merged by jenkins-bot:
+Apply 'original size' to images and enable apply button in ve-MW
+
+https://gerrit.wikimedia.org/r/144638",1404842120,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 144638 had a related patch set uploaded by Mooeypoo:
+Apply 'original size' to images and enable apply button in ve-MW
+
+https://gerrit.wikimedia.org/r/144638",1404798315,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 144637 had a related patch set uploaded by Mooeypoo:
+Apply 'original size' to images
+
+https://gerrit.wikimedia.org/r/144637",1404798130,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Its changing the size value in the dialog but after clicking on ""Apply Changes"" button it is not making it full size.So, reopening it .",1404764938,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix on test2,1404152879,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Backported to wmf11 and working great.,1404144107,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 142855 merged by jenkins-bot:
+Update VisualEditor to Iba4e6b32
+
+https://gerrit.wikimedia.org/r/142855",1404142302,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 142855 had a related patch set uploaded by Jforrester:
+Update VisualEditor to Iba4e6b32
+
+https://gerrit.wikimedia.org/r/142855",1404001396,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","We need to backport the fix for this one,it did not make it to test2.",1403903163,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix in betalabs,1403902903,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 142171 merged by jenkins-bot:
+Correctly update full size in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/142171",1403745466,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 142171 had a related patch set uploaded by Mooeypoo:
+Correctly update full size in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/142171",1403743468,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a cite option/references/formula/image
+
+Observed Result:
+Observe that the,context menus are appearing for these items for a second and then suddenly disappears right after adding
+
+Environment: Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403201760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ssdjpviwo7nog652sz63,task_description,resolved
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified the fix in production (en.wiki),1404767443,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified the fix in test2,1403903577,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified the fix in Betalabs.,1403743096,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified the fix in Betalabs.,1403743096,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,"Change 141940 merged by jenkins-bot:
+Revert ""Accessibility: Restore element focus when a window closes""
+
+https://gerrit.wikimedia.org/r/141940",1403719157,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,"Change 141940 had a related patch set uploaded by Esanders:
+Revert ""Accessibility: Restore element focus when a window closes""
+
+https://gerrit.wikimedia.org/r/141940",1403698053,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,"Updated MW core and it broke, must be an OOJS regression.",1403697005,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified working in master.,1403696873,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"On English Wikipedia, tabbing in the citation dialog is broken.  To reproduce:
+
+1. Edit an article with VE.
+2. Choose 'News' from the Cite menu.
+3. Click the first field.
+4. Tab to try to get to the next field.
+
+Focus goes to a help icon, and even tabbing repeatedly will not get it to leave that icon.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65554",1403155500,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-l57zuo7fpi4s3unocju2,task_description,resolved
+VisualEditor: Fix tabindexes in the citation dialog,*** Bug 67159 has been marked as a duplicate of this bug. ***,1404849994,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,Well that's at least a workaround. I wonder if this might be an upstream bug...,1404152426,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Change 142718 merged by jenkins-bot:
+Set tabindex for template dialog info/remove buttons on parent <div> rather than <a>
+
+https://gerrit.wikimedia.org/r/142718",1404152289,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Change 142718 had a related patch set uploaded by Alex Monk:
+Set tabindex for template dialog info/remove buttons on parent <div> rather than <a>
+
+https://gerrit.wikimedia.org/r/142718",1403902432,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Weird... I can replicate this in Firefox, but not Chrome.
+
+I tried copying the inner HTML out of the dialog iframe and into a separate file - it worked there.
+I also tried moving the tabindex attribute from the <a>s to their parent <div>s... That seems to work. Not sure why.
+
+(I've been testing with any template which has TemplateData, btw - not specifically Cite stuff)",1403902374,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Created attachment 15765
+Tabbing issue in Firefox
+
+I can still reproduce it.  I should have said, I tested in Iceweasel/Firefox 30.0 on Debian Wheezy.
+
+I'm attaching a video.  It shows how I got there, and that it tabs to the help icon.  I tab multiple times and it sticks, though you can't see that in the video.
+
+**Attached**: {F14064}",1403896446,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Actually:
+
+* in Firefox, the tabbing doesn't take you to the help icon (or delete icon), only in Chrome (instead it takes you to the next field);
+* in neither can you tab to the ""add field"" button;
+* when the add field panel opens your cursor doesn't open in the search field;
+* when in the add field search box tabbing doesn't take you to the field options.
+
+However, yeah, I can't replicate the original report – Matt, can you clarify?",1403218376,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"It's supposed to go to the help icon (that was Gerrit change 137152 - bug 65474), but 'tabbing repeatedly will not get it to leave that icon' is WFM",1403199839,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Attempt to insert a formula or a hiero with the inspectors
+
+Observed Result:
+The math inspector jumps to the beginning of the article then comes back to the right position where it was intended to open
+
+For hiero, it gets stuck at that position.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14045}",1403128380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_description,resolved
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,Verified the fix in production (en.wiki),1404767262,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,Verified in test2,1403906704,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,"Fixed for Math inspector.Will check for Heiro later, when it is available",1403906645,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,Verified the fix in Betalabs,1403742731,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,"Change 141985 merged by jenkins-bot:
+Render a placeholder when extension contents are empty
+
+https://gerrit.wikimedia.org/r/141985",1403732447,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,"Change 141985 had a related patch set uploaded by Esanders:
+Render a placeholder when extension contents are empty
+
+https://gerrit.wikimedia.org/r/141985",1403712087,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: [Regression pre-wmf10] Save fails with fatal error,"as a logged in user on any page in http://en.wikipedia.beta.wmflabs.org/
+
+edit a page and attempt to save.
+
+Save your changes interface shows ""Error: unknown error""
+
+fatal.log shows 
+
+[2014-06-18 16:18:37] Fatal error: Call to a member function getDisplayTitle() on a non-object at /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditorEdit.php on line 120
+Server: deployment-apache01
+Method: POST
+URL: http://en.wikipedia.beta.wmflabs.org/w/api.php
+Cookie: enwiki-gettingStartedUserId=kJSYCjZCvJa3o9xl48ODXiGk1DaduG2m; centralauth_LoggedOut=1402329725; ve-beta-welcome-dialog=1; optin=beta; centralnotice_bucket=0-4.2; edittoolscharsubset=0; GeoIP=US:Tucson:32.2217:-110.9265:v4; uls-previous-languages=%5B%22en%22%5D; mediaWiki.user.sessionId=2vKzOP6dVykMZfazhyIC7OKY5jkC0O3t; enwikiUserID=54; enwikiUserName=Cmcmahon; enwikiSession=29dd771993d2f54b0eb86b9ccc4e85df; centralauth_User=Cmcmahon; centralauth_Session=caf75694c6a3d741ef094fac43c50f47
+Backtrace:
+#0 /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditorEdit.php(120): ApiVisualEditorEdit::execute()
+#1 /srv/common-local/php-master/includes/api/ApiMain.php(908): ApiVisualEditorEdit->execute()
+#2 /srv/common-local/php-master/includes/api/ApiMain.php(363): ApiMain->executeAction()
+#3 /srv/common-local/php-master/includes/api/ApiMain.php(334): ApiMain->executeActionWithErrorHandling()
+#4 /srv/common-local/php-master/api.php(85): ApiMain->execute()
+#5 /srv/common-local/w/api.php(3): require('/srv/common-loc...')
+#6 {main}
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66717",1403108460,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5uojpr32nnknnwpwsv2v,task_description,resolved
+VisualEditor: [Regression pre-wmf10] Save fails with fatal error,"Change 140558 merged by jenkins-bot:
+Revert ""Update displaytitle on save""
+
+https://gerrit.wikimedia.org/r/140558",1403123018,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5uojpr32nnknnwpwsv2v,task_subcomment,NA
+VisualEditor: [Regression pre-wmf10] Save fails with fatal error,"Change 140558 had a related patch set uploaded by Catrope:
+Revert ""Update displaytitle on save""
+
+https://gerrit.wikimedia.org/r/140558",1403122809,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5uojpr32nnknnwpwsv2v,task_subcomment,NA
+VisualEditor Mobile: There's no way to apply heading/etc. paragraph formatting,"There's no way to apply heading styles.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403098140,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-54wl37knbm4fkiq6mgrc,task_description,duplicate
+VisualEditor Mobile: There's no way to apply heading/etc. paragraph formatting,"Yeah, this was intentionally left out of the MVP.",1406600551,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-54wl37knbm4fkiq6mgrc,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE 
+2.Type a text in CE
+3.Select that text
+4.Click on Link inspector icon from the toolbar
+
+Observed Result:
+The link inspector dialog opens but there is no suggestion for link target, also the text selected should appear in the text field inside link inspector, which is not happening as well
+
+Device: Nexus 7(Android 4.4.2)
+Environment:Betalabs
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13913}",1403045460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-citqfhmyoebglw4grn67,task_description,resolved
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Verified the fix in production en.wiki for iOS only, for Android there is a different issue, where the link text is not appearing inside the link inspector,   so cannot follow the exact steps to reproduce to check it there.",1406316076,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Verified the fix in test2 with iOS and Android.,1405725535,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Verified the fix in Betalabs with Android as well,1404335511,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Verified the fix in Betalabs with iOS,1404333288,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Yay deployment.,1404331548,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Possibly a deploy issue.,1404329806,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Still happening on Betalabs,1404323802,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Change 143524 merged by jenkins-bot:
+Use globalOverlay as the contextOverlay in MobileContext
+
+https://gerrit.wikimedia.org/r/143524",1404260533,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Change 143524 had a related patch set uploaded by Catrope:
+Use globalOverlay as the contextOverlay in MobileContext
+
+https://gerrit.wikimedia.org/r/143524",1404260391,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Found the steps.
+This happens every second attempt on adding a link where the keyboard gets hidden after adding the first link in CE
+
+So the steps are:
+
+1.Open a page with mobile VE 
+2.Type a text in CE
+3.Select that text
+4.Click on Link inspector icon from the toolbar
+5.Select a suggestion that appears in the dropdown box
+6.After this link gets added successfully, hide the keyboard
+7.Again type a new text and try to add a link to it from the link inspector
+
+Observed Result:
+No link suggestions appear, cannot close the link inspector.",1404170568,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"I am getting this issue intermittently now. Surely the behavior got changed/improved which is why it is not reproducible anymore in a straight forward way.
+
+I will see if I can find any consistent step that ensures this issue to happen.",1404169704,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"This is not android specific issue, its happening for iOS as well.
+Also, it has gone to production now.So, the environment is not just Betalabs now :(",1403736136,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in Firefox
+2.Go to Insert>Language
+3.Close the language inspector without making any change
+
+Observed Result:
+An error appears in the console:
+TypeError: sel.nativeSelection is null
+
+See the screenshot attached
+
+Environment:test2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13853}",1403030700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_description,resolved
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null",Verified the fix in production,1403901923,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null",Verified the fix in test2,1403303156,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","After re-deployment , it is now fixed :)",1403223776,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Note: doesn't appear in Beta Labs for some reason, but does in production.",1403216138,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Indeed, not working. Sigh.",1403216004,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null",It's still not working on test2.,1403204522,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Actually yes, just a deployment issue.",1403202333,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null",Apparently not. :-(,1403199532,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Change 140426 merged by jenkins-bot:
+Catch rangy exception thrown in FF
+
+https://gerrit.wikimedia.org/r/140426",1403114816,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Change 140426 had a related patch set uploaded by Catrope:
+Catch rangy exception thrown in FF
+
+https://gerrit.wikimedia.org/r/140426",1403114678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Change 140326 merged by jenkins-bot:
+Catch rangy exception thrown in FF
+
+https://gerrit.wikimedia.org/r/140326",1403114345,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Change 140326 had a related patch set uploaded by Esanders:
+Catch rangy exception thrown in FF
+
+https://gerrit.wikimedia.org/r/140326",1403085768,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"on https://www.mediawiki.org/wiki/Extension:Gadgets and edit throws following error:
+TypeError: title is null
+https://bits.wikimedia.org/static-1.24wmf9/resources/src/mediawiki/mediawiki.Title.js
+Line 123
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403017560,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_description,resolved
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Change 145055 merged by jenkins-bot:
+MWTemplatePage: Account for template.title being null
+
+https://gerrit.wikimedia.org/r/145055",1405000743,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Change 145055 had a related patch set uploaded by Krinkle:
+MWTemplatePage: Account for template.title being null
+
+https://gerrit.wikimedia.org/r/145055",1404936548,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Yep. It used to throw 
+> Uncaught TypeError: title is null
+
+It now fails earlier because the code changed. Namely on 
+
+> Uncaught TypeError: Cannot read property 'replace' of null",1404935289,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"I wanted to open a new bug, but here is still one :) Actually i become the message:
+Uncaught TypeError: Cannot read property 'replace' of null
+
+fyi :)",1404566086,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"(In reply to Gabriel Wicke from comment #3)
+> Simple test case: {{{{echo|echo}}|foo}}
+> 
+> The Parsoid output looks correct to me.
+
+Thanks!
+
+
+Ed – I guess in these cases we should just detect that it's an invalid title somehow and mark the template as uneditable?",1403140768,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Hmm, actually there is an issue in the Parsoid output for this test case, but it's not likely to be related to this bug.
+
+{{{{echo|echo}}|foo}}
+
+data-mw looks good, but the string 'foo' is missing in the span for some reason.
+
+<span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""{{echo|echo}}""},""params"":{""1"":{""wt"":""foo""}},""i"":0}}]}'></span>
+
+Reported in bug 66820.",1403139914,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Simple test case: {{{{echo|echo}}|foo}}
+
+The Parsoid output looks correct to me.",1403139652,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"(In reply to Ed Sanders from comment #1)
+> Looks like we don't support evaluated template names:
+> {{ {{TNTN:Extension}}
+>   |...
+> }}
+> 
+> Not sure if this a VE or Parsoid problem.
+
+Feels like this template should have been ExpandedAttrs'ed by Parsoid?",1403139279,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Looks like we don't support evaluated template names:
+{{ {{TNTN:Extension}}
+  |...
+}}
+
+Not sure if this a VE or Parsoid problem.",1403091885,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","VE editable div remains after Save
+
+As a logged in user on beta labs http://en.wikipedia.beta.wmflabs.org/
+
+Edit any page and Save
+
+User can continue to type in the saved page in a VE documentNode div
+
+See screen shot
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66792
+
+**Attached**: {F13826}",1403013420,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_description,declined
+"VisualEditor: Page remains ""editable"" after saving","(In reply to Alex Monk from comment #5)
+> How did you guys reproduce this before the revert (outside of
+> deployment-prep)?
+
+We didn't.",1403132251,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving",How did you guys reproduce this before the revert (outside of deployment-prep)?,1403125095,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","I fixed the server errors, and now I can't reproduce this.",1403124705,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","(In reply to Gerrit Notification Bot from comment #2)
+> Change 140558 had a related patch set uploaded by Catrope:
+> Revert ""Update displaytitle on save""
+> 
+> https://gerrit.wikimedia.org/r/140558
+
+This was unrelated we think.",1403123495,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","Change 140558 had a related patch set uploaded by Catrope:
+Revert ""Update displaytitle on save""
+
+https://gerrit.wikimedia.org/r/140558",1403122804,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","Getting server errors on beta, but can't reproduce in master.",1403092625,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in Firefox
+2.Go to Insert>Language
+3.Close the language inspector without making any change
+4.Click on ""Save Page""
+
+Observed Result:
+After step 3 you get the error: TypeError: sel.nativeSelection is null
+After saving there is another error in the console:
+TypeError: this.debugBar is null
+
+If you had categories add on this page, they move to the top of the page
+The context menu for Language Inspector is still open in read mode
+Try to reopen VE , clicking on Edit button, VE does not open.
+
+Environment: test2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13751}",1402957200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_description,resolved
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that",Verified the fix in production(en.wiki),1403299599,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Ignore my last comment, added the comment on wrong bug",1403199681,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that",The backport did not work in test2,1403199544,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that",Verified the fix in Betalabs,1403030047,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","(In reply to ryasmeen from comment #5)
+> Sorry, the language inspector throwing ""TypeError:sel.nativeSelection is
+> null""-
+> this is in both test2 and betalabs,but not the issue with tearing down the
+> debug bar.
+> Initially I thought both of them are related.I am opening a different bug
+> for that one.
+
+OK, thanks.",1403029978,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Sorry, the language inspector throwing ""TypeError:sel.nativeSelection is null""-
+this is in both test2 and betalabs,but not the issue with tearing down the debug bar.
+Initially I thought both of them are related.I am opening a different bug for that one.",1403029902,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that",Are you sure this is a fault for test2? The code this follows up wasn't present for wmf9 unless I'm missing something.,1403028723,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Change 140039 merged by jenkins-bot:
+Followup 00af434: only tear down debug bar if it exists
+
+https://gerrit.wikimedia.org/r/140039",1403025580,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Change 140039 had a related patch set uploaded by Catrope:
+Followup 00af434: only tear down debug bar if it exists
+
+https://gerrit.wikimedia.org/r/140039",1402959281,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","The second error: TypeError: this.debugBar is null
+appears after selecting any language from the language selector",1402958330,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox","Steps to reproduce:
+
+1.Open a pag with VE
+2.Insert a Heiro
+3.While the cursor is at the end of hiero, hit return to go the next line
+
+
+Observed Result:
+Error: Inserted data is trying to close the root node (at index 0) appears and cannot go to the next line
+
+Environment:
+
+Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402956420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5z56coxja6r5rbey633o,task_description,resolved
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox",Looks like it is now.,1412360025,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5z56coxja6r5rbey633o,task_subcomment,NA
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox",This is not yet fixed in Betalabs.,1403202317,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5z56coxja6r5rbey633o,task_subcomment,NA
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox","Change 140345 merged by jenkins-bot:
+Prevent getOffset from return an offset inside a content node
+
+https://gerrit.wikimedia.org/r/140345",1403114249,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5z56coxja6r5rbey633o,task_subcomment,NA
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox","Change 140345 had a related patch set uploaded by Esanders:
+Prevent getOffset from return an offset inside a content node
+
+https://gerrit.wikimedia.org/r/140345",1403096730,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5z56coxja6r5rbey633o,task_subcomment,NA
+"VisualEditor: Scrolling for &vesection=N works correctly except for N=0, where it scrolls to the bottom of the document","When a page is opened in the wikitext editor with section=0, the top of the page is presented for editing The is the desired and expected behavior:
+
+https://en.wikipedia.org/w/index.php?title=Armadillo&action=edit&section=0
+
+However, VisualEditor does not do this when vesection=0 is opened up for editing. The cursor is placed at the top of the page, but the screen scrolls down to the bottom of the page. The expected behavior is that the scree stay at the top of the window:
+
+https://en.wikipedia.org/w/index.php?title=Armadillo&veaction=edit&vesection=0
+
+This does not occur when using section=0:
+
+https://en.wikipedia.org/w/index.php?title=Armadillo&veaction=edit&section=0
+
+This is particularly important to the Russian Wikipedia, where they regularly use edit&section=0 links and it's easy to wind up with vesection=0.
+
+Here's the report on my ru.wp talk page, with ru.wp links:
+https://ru.wikipedia.org/w/index.php?title=%D0%9E%D0%B1%D1%81%D1%83%D0%B6%D0%B4%D0%B5%D0%BD%D0%B8%D0%B5_%D1%83%D1%87%D0%B0%D1%81%D1%82%D0%BD%D0%B8%D0%BA%D0%B0:Keegan_(WMF)&oldid=prev&diff=63662618
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402939800,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-fyybkik3jnrz25mdbjea,task_description,resolved
+"VisualEditor: Scrolling for &vesection=N works correctly except for N=0, where it scrolls to the bottom of the document","Change 141977 merged by jenkins-bot:
+Don't try to change offset for vesection=0
+
+https://gerrit.wikimedia.org/r/141977",1403715366,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fyybkik3jnrz25mdbjea,task_subcomment,NA
+"VisualEditor: Scrolling for &vesection=N works correctly except for N=0, where it scrolls to the bottom of the document","Change 141977 had a related patch set uploaded by Esanders:
+Don't try to change offset for vesection=0
+
+https://gerrit.wikimedia.org/r/141977",1403710849,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fyybkik3jnrz25mdbjea,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,"On any page at http://en.wikipedia.beta.wmflabs.org/ 
+
+Make an edit
+
+Click Review your changes
+
+User sees a modal dialog saying ""Error loading data from server: error.""
+
+
+fatal log shows
+
+[2014-06-16 14:57:25] Fatal error: Call to a member function get() on a non-object at /srv/common-local/php-master/includes/api/ApiQueryRevisions.php on line 629
+Server: deployment-apache02
+Method: POST
+URL: http://en.wikipedia.beta.wmflabs.org/w/api.php
+Cookie: enwiki-gettingStartedUserId=kJSYCjZCvJa3o9xl48ODXiGk1DaduG2m; centralnotice_bucket=1-4.2; centralauth_LoggedOut=1402329725; ve-beta-welcome-dialog=1; edittoolscharsubset=0; optin=beta; GeoIP=US:Tucson:32.2217:-110.9265:v4; uls-previous-languages=%5B%22en%22%5D; mediaWiki.user.sessionId=y0AhKxKUggdcyUd7KMOLw6Bx8JuBJTqT; enwikiUserID=54; enwikiUserName=Cmcmahon; enwikiSession=090850308740c4e1214d05399aa6d221; centralauth_User=Cmcmahon; centralauth_Session=d47cf247a4d3ea1081576f3520609ffe
+Backtrace:
+#0 /srv/common-local/php-master/includes/api/ApiQueryRevisions.php(629): ApiQueryRevisions::extractRowInfo()
+#1 /srv/common-local/php-master/includes/api/ApiQueryRevisions.php(402): ApiQueryRevisions->extractRowInfo(Object(stdClass))
+#2 /srv/common-local/php-master/includes/api/ApiQuery.php(282): ApiQueryRevisions->execute()
+#3 /srv/common-local/php-master/includes/api/ApiMain.php(908): ApiQuery->execute()
+#4 /srv/common-local/php-master/includes/api/ApiMain.php(332): ApiMain->executeAction()
+#5 /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditor.php(230): ApiMain->execute()
+#6 /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditor.php(501): ApiVisualEditor->diffWikitext(Object(Title), 'Starting a new ...')
+#7 /srv/common-local/php-master/includes/api/ApiMain.php(908): ApiVisualEditor->execute()
+#8 /srv/common-local/php-master/includes/api/ApiMain.php(363): ApiMain->executeAction()
+#9 /srv/common-local/php-master/includes/api/ApiMain.php(334): ApiMain->executeActionWithErrorHandling()
+#10 /srv/common-local/php-master/api.php(85): ApiMain->execute()
+#11 /srv/common-local/w/api.php(3): require('/srv/common-loc...')
+#12 {main}
+[2014-06-16 14:57:25]
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402930860,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-upajxn6r42b5mvgdvg4u,task_description,resolved
+[Regression pre-wmf10] Review your changes throws fatal error,Verified the fix in Betalabs,1402955700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,"Change 139879 merged by jenkins-bot:
+Followup e48ecbc5: fix fatal error due to undefined variable
+
+https://gerrit.wikimedia.org/r/139879",1402944298,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,"Change 139879 had a related patch set uploaded by Catrope:
+Followup e48ecbc5: fix fatal error due to undefined variable
+
+https://gerrit.wikimedia.org/r/139879",1402943560,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,*** Bug 66681 has been marked as a duplicate of this bug. ***,1402943552,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,I am seeing this error modal dialog also intermittently on test2wiki (and presumably mediawiki.org) when switching modes from VE to wikitext editor.,1402941380,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,"
+Note: saving changes works correctly",1402930897,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+VisualEditor: Keyboard events not detected after selecting a focusable node with the mouse,"1. Click on an image
+2. Press delete
+
+Nothing happens
+
+Contrast with focussing an image by keyboard navigation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402836420,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3xmwgu22clys4qnwhvfj,task_description,resolved
+VisualEditor: Keyboard events not detected after selecting a focusable node with the mouse,"Change 139679 merged by jenkins-bot:
+Defer focusableNode selection fix until after native selection change
+
+https://gerrit.wikimedia.org/r/139679",1403054361,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3xmwgu22clys4qnwhvfj,task_subcomment,NA
+VisualEditor: Keyboard events not detected after selecting a focusable node with the mouse,"Change 139679 had a related patch set uploaded by Esanders:
+Defer focusableNode selection fix until after native selection change
+
+https://gerrit.wikimedia.org/r/139679",1402836725,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3xmwgu22clys4qnwhvfj,task_subcomment,NA
+VisualEditor: Image CE HTML should match Parsoid,"When converting between block and inline images we hide the <figcaption> with CSS instead of removing it from the DOM tree. We need to preserve the caption in case the user converts from inline back to block, but this can be done in the model.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402736640,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g6ern4m4ctxikpozgnha,task_description,resolved
+VisualEditor: Image CE HTML should match Parsoid,"Current Parsoid HTML:
+
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb"" data-parsoid=""…"">
+	<a href=""./File:Smokeycover.jpg"" data-parsoid=""…"">
+		<img resource=""./File:Smokeycover.jpg"" src=""//upload.wikimedia.org/wikipedia/en/thumb/7/73/Smokeycover.jpg/170px-Smokeycover.jpg"" height=""237"" width=""170"" data-parsoid=""…"">
+	</a>
+	<figcaption data-parsoid=""…"">
+		<a rel=""mw:WikiLink"" href=""./Smokey_Stover"" title=""Smokey Stover"" data-parsoid=""…"">Smokey Stover</a><!-- no italics, character’s name --> driving a ""foomobile"", with <i data-parsoid=""…"">phoo</i> visible on the front
+	</figcaption>
+</figure>
+
+
+Current VE HTML:
+
+<figure class=""ve-ce-mwBlockImageNode ve-ce-mwBlockImageNode-type-thumb mw-default-size ve-ce-branchNode ve-ce-mwBlockImageNode-borderwrap mw-halign-right ve-ce-focusableNode"" typeof=""mw:Image/Thumb"" contenteditable=""false"" style=""width: 172px; height: auto;"">
+	<a class=""image"" href=""https://en.wikipedia.org/wiki/File:Smokeycover.jpg"">
+		<img src=""//upload.wikimedia.org/wikipedia/en/thumb/7/73/Smokeycover.jpg/170px-Smokeycover.jpg"" class=""ve-ce-mwBlockImageNode-thumbimage"" style=""width: 170px; height: 237px;"">
+	</a>
+	<figcaption class=""ve-ce-branchNode"">
+		<div class=""magnify""><a class=""internal""></a></div>
+		<p class=""ve-ce-paragraphNode ve-ce-generated-wrapper ve-ce-branchNode"">
+			<a class=""ve-ce-linkAnnotation ve-ce-mwInternalLinkAnnotation new"" href=""http://en.wikipedia.beta.wmflabs.org/wiki/Smokey%20Stover"" title=""Smokey Stover"">Smokey Stover</a><span class=""ve-ce-leafNode ve-ce-commentNode oo-ui-indicatedElement-indicator oo-ui-indicator-alert oo-ui-indicatedElement ve-ce-focusableNode"" contenteditable=""false""> </span>&nbsp;driving a ""foomobile"", with <i class=""ve-ce-textStyleAnnotation ve-ce-italicAnnotation"">phoo</i> visible on the front
+		</p>
+	</figcaption>
+</figure>
+
+The only structural difference is the ""<div class=""magnify""><a class=""internal""></a></div>"" which Parsoid is missing (and will go away soon enough anyway). Deeming this to be fixed.",1409254775,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g6ern4m4ctxikpozgnha,task_subcomment,NA
+VisualEditor: Image CE HTML should match Parsoid,What's left to do here?,1408662539,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g6ern4m4ctxikpozgnha,task_subcomment,NA
+VisualEditor: Image CE HTML should match Parsoid,"Discussion from Gerrit:
+
+Mooeypoo		Jun 13 8:25 PM
+
+<figcaption> isn't destroyed and/or is recreated each time an image type changes, so it has to be hidden for the block image types that don't support it, like frameless and basic.
+But yes, it could be added to the CSS instead, hiding the figcaption for the block image types that don't support it. 
+I'm not sure it should be generalized for Parsoid's use, though, since the Parsoid output for the figcaption is always correct (so, no caption for images that don't support it). We keep the caption in VE to let the user be able to change the images back and forth and retain the information in the caption even if the type changed.
+
+Esanders		Jun 13 8:29 PM
+
+If it's not supposed to be in the tree when it's not in use, why don't we destroy it completely and recreate it when it's needed again?
+
+Mooeypoo		Jun 13 8:40 PM
+
+Because the caption information is taken from <figcaption> and we want to retain it for (A) if the user regrets their type choice and edits again to another type that supports the caption (make sure that the caption isn't lost) and (B) so it won't be removed from the wikitext.
+There's a tech debt to fix the way caption works in general, especially in light of VE allowing the switch from block to inline and the existence of alternate text (which gets the value of the caption if it exists) but right now it's on hold for a little bit waiting for the new Media Edit dialog redesign.
+
+Esanders		Jun 13 8:43 PM
+
+If we need to preserve the caption that should be done in the model, not the view.
+
+Mooeypoo		Jun 13 8:48 PM
+
+Yes, and it also must be preserved in wikitext, so the <figcaption> must be sent to parsoid in certain cases. And the caption surface in the editor should be selectively disabled and enabled, and exchange its information with the alt-text in a way that the user understands where and why things are replaced.
+Hence the tech debt.
+
+GWicke		Jun 13 9:36 PM
+
+Also see https://gerrit.wikimedia.org/r/#/c/139473/. There should be no need to manually hide the caption with inline CSS. Inline images have no caption in the DOM, as that can for example break a surrounding paragraph in case the caption contains a paragraph.",1402736738,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g6ern4m4ctxikpozgnha,task_subcomment,NA
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,"* Move your cursor anywhere in the document, don't select anything.
+* Open the link inspector
+* Set target anywhere
+* Click back to document in the same position
+* Press any key
+* New character is shown, but is highlighted. If you undo and then redo, a pawn character appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68590",1402600500,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-e754krtqrkmtvi55a5wr,task_description,resolved
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,"Yeah, I'm going to declare this one also fixed in the re-write. The block slug issue is… interesting, and may deserve its own bug, but I'll comment on bug 68590.",1406324798,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e754krtqrkmtvi55a5wr,task_subcomment,NA
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,"Doesn't seem to happen anymore. Although we do now have bug 68590, which is pretty much these same steps but with another undo instead of redo at the end. Not sure about Roan's comment.",1406323339,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-e754krtqrkmtvi55a5wr,task_subcomment,NA
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,Sometimes I've managed to get this to create a pawn character at the same time as making the highlighted text. Appears to be to do with the target text.,1402600750,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-e754krtqrkmtvi55a5wr,task_subcomment,NA
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,"Additionally, if you put your cursor in a block slug, open the link inspector in creation mode, and click back into the surface in the same place, the link inspector doesn't close. Then when you start typing, the same behavior as in comment 0 appears.",1402600664,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-e754krtqrkmtvi55a5wr,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"After a fresh installation of MW 1.23 (from the tarball), adding VisualEditor and configuring parsoid, the ""Edit"" (or ""Create"") link of any page is not working.
+
+I am not the only one having this problem: https://www.mediawiki.org/wiki/Extension_talk:VisualEditor#Can_not_get_VisualEditor_extension_for_MediaWiki_REL1_23_working_on_freshly_installed_system_44018
+
+What I saw when I checked with FireBug:
+* In an old (1.22) installation clicking ""Edit"" results in a POST-request with action=visualeditor&paction=parse&page=Main_Page&format=json as its content.
+* In the new installation no request is visible in FireBug when clicking on ""Edit"".
+
+One more finding: It seems to work in 1.23alpha. I used wikiapiary to search for sites using VisualEditor and found e.g. this one: http://techwiki.umbel.org/index.php/Special:Version where it works...
+
+Some more investigation:
+using the Poster-extension of Firefox to manually POST 
+""action=visualeditor&paction=parse&page=Main_Page&format=json"" (application/x-www-form-urlencoded) to .../api.php
+returns good looking content of type ""application/json; charset=utf-8"" (see attachment ""visualeditor_postresponse.json"").
+
+But the JS-compoments of VisualEditor are not displaying anything!
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402562460,PHID-USER-3x5zfm7iedaghxnnelco,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_description,resolved
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"(In reply to Tony Mach from comment #10)
+> Ok, VisualEditor is now running on my system!
+> 
+> And I found the problem:
+> 
+> If you download the VisualEditor via the web-interface at
+> http://git.wikimedia.org/branches/mediawiki%2Fextensions%2FVisualEditor.git
+> then you will *NOT* get any submodules, like e.g. lib/ve/. 
+> 
+> The problem is, that web-interface for git at git.wikimedia.org can not
+> handle git submodules. If you download an archive of VisualEditor (e.g.
+> REL1_23) then lib/ve will be missing. If you try to access a submodule like
+> lib/ve, then the web-interface will give you an error message.
+> 
+> If you download VisualEditor via
+> https://www.mediawiki.org/wiki/Special:ExtensionDistributor/VisualEditor
+> then everything is fine.
+> 
+> If you manually download VisualEditor via git commandline, and do a ""git
+> submodule update --init"" afterwards, then everything is fine.
+
+Yeah, the instructions say this pretty clearly, though I see you've now gone rather over-board in saying this several times in big boxes. :-)
+
+> What is really annoying was the lack or error-messages.
+
+Yeah; we should raise an issue with MediaWiki core about the lack of user-visible errors, though gerrit 155177 will at least make it more obvious for VisualEditor users in future.",1408636513,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"**bugzilla.wikimedia.org** wrote:
+
+Ok, VisualEditor is now running on my system!
+
+And I found the problem:
+
+If you download the VisualEditor via the web-interface at http://git.wikimedia.org/branches/mediawiki%2Fextensions%2FVisualEditor.git then you will *NOT* get any submodules, like e.g. lib/ve/. 
+
+The problem is, that web-interface for git at git.wikimedia.org can not handle git submodules. If you download an archive of VisualEditor (e.g. REL1_23) then lib/ve will be missing. If you try to access a submodule like lib/ve, then the web-interface will give you an error message.
+
+If you download VisualEditor via https://www.mediawiki.org/wiki/Special:ExtensionDistributor/VisualEditor then everything is fine.
+
+If you manually download VisualEditor via git commandline, and do a ""git submodule update --init"" afterwards, then everything is fine.
+
+What is really annoying was the lack or error-messages.",1408621745,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,Please explain how you installed VE and its dependencies and which exact guide you followed; might be better to ask/discuss on IRC in #mediawiki-visualeditor or https://www.mediawiki.org/wiki/Talk:VisualEditor or https://www.mediawiki.org/wiki/Extension_talk:VisualEditor,1408620475,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"**bugzilla.wikimedia.org** wrote:
+
+D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/ is missing on my system!!! There is only jquery.uls ...
+
+Where do I get the ve lib? Why don't I have the ve lib?",1408616873,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"**bugzilla.wikimedia.org** wrote:
+
+Oh, one more thing I just found, when I manually do the GET /mediawiki/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cmediawiki%2CviewPageTarget%7Cext.visualEditor.core.desktop%7Cjquery.visibleText%7Cmediawiki.api.edit%7Cmediawiki.feedback%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20140820T142325Z&* then I get the following (snipped at the end):
+
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/modules/ve/ve.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/modules/ve/ve.Range.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/modules/ve/ui/ve.ui.DesktopSurface.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/lib/jquery/jquery.visibleText.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/lib/rangy/rangy-core-1.3.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/modules/unicodejs/unicodejs.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+mw.loader.implement(""ext.visualEditor.mediawiki"",function($,jQuery){ve.init.mw={'targets':[]};(function() ...",1408616570,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"**bugzilla.wikimedia.org** wrote:
+
+I have a similar (same?) problem: VisualEditor does not load when clicking on the ""edit"" tab.
+
+This is the setup I use:
+
+- Windows 7
+- XAMPP win32-1.8.3-4-VC11
+- MediaWiki (tried both REL1_23 and 1.24wmf17)
+- VisualEditor (tried 1.23wmf22, 1.23wmf21, 1.24wmf17)
+
+I tried it both with Firefox 31 and Google Chrome 36 - in both, the VisualEditor does not load from my server. (VisualEditor loads fine for example from wikimedia.org in both browsers)
+
+I think my Parsoid is running fine. When I access port 8000, I get access to my parsoid installation, and it seems to parse html and wikicode just fine.
+
+I tried using VisualEditor-refs_heads_wmf_1.23wmf22 and VisualEditor-refs_heads_wmf_1.23wmf21 - no change, VisualEditor does not load.
+
+I tried using Mediawiki core-refs_heads_wmf_1.24wmf17 with VisualEditor refs_heads_wmf_1.24wmf17 - no change, VisualEditor does not load.
+
+I do not get any error message. The access log does not show much. 
+
+Loading the main page:
+127.0.0.1 - - [21/Aug/2014:12:11:24 +0200] ""GET /mediawiki/index.php/Main_Page HTTP/1.1"" 304 - ""-"" ""Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0""
+
+127.0.0.1 - - [21/Aug/2014:12:11:25 +0200] ""GET /mediawiki/load.php?debug=false&lang=en&modules=ext.visualEditor.viewPageTarget.noscript%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles&only=styles&skin=vector&* HTTP/1.1"" 304 - ""http://127.0.0.1/mediawiki/index.php/Main_Page"" ""Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0""
+
+127.0.0.1 - - [21/Aug/2014:12:11:25 +0200] ""GET /mediawiki/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&* HTTP/1.1"" 304 - ""http://127.0.0.1/mediawiki/index.php/Main_Page"" ""Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0""
+
+Then pressing on the edit tab:
+
+127.0.0.1 - - [21/Aug/2014:12:12:19 +0200] ""GET /mediawiki/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cmediawiki%2CviewPageTarget%7Cext.visualEditor.core.desktop%7Cjquery.visibleText%7Cmediawiki.api.edit%7Cmediawiki.feedback%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20140820T142325Z&* HTTP/1.1"" 304 - ""http://127.0.0.1/mediawiki/index.php/Main_Page"" ""Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0""
+
+Are there any debug-output, logfiles, or something like that I can access or activate? I have no idea why VisualEditor does not load, and I do not know where to look. Can this be a firewall problem? Has anybody any idea?",1408616164,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"I've updated REL1_23 to just simply use 1.23wmf22 instead, which should fix the incompatibility. Sorry about this.",1403633787,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"Relevant commits that were in wmf/1.23wmf22 but not in REL1_23 yet:
+
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/compare/REL1_23...wmf/1.23wmf22
+
+https://github.com/wikimedia/VisualEditor/compare/55a5cdc047...b3e5759654
+
+I reckon one or more of those should be backported.",1403603952,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"Hello Kevin,
+
+thank you for the confirmation and the additional information!
+
+Switching to the git-Version of VisualEditor and using branch wmf/1.23wmf22 did indeed make it work for me as well!
+
+But I do not want to use this work-around in a production environment without anyone in the know confirming it's the way to go...",1403602007,PHID-USER-3x5zfm7iedaghxnnelco,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"I can confirm this bug.  It is throwing the following JS exception:
+
+Exception thrown by ext.visualEditor.core
+Error: constructor must be a function, cannot be a undefined
+
+The exception gets throwing trying to call:
+
+ve.ui.windowFactory.register( OO.ui.ConfirmationDialog );
+
+From line 22 of lib/modules/ve/ui/ve.ui.js
+
+The problem goes away if I switch from branch REL1_23 to wmf/1.23wmf22 (and run git submodule update).",1403568663,PHID-USER-5yr7uedvkbhzdccm6hy2,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"Created attachment 15635
+Response of POST to api.php
+
+**Attached**: {F13953}",1402562535,PHID-USER-3x5zfm7iedaghxnnelco,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"Right now they're not, which is irritating when I'm writing about how VE supports the functionality. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402552140,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_description,resolved
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"Change 140194 merged by jenkins-bot:
+(Bug 66514) Fix bug in nowiki-escaping of magic words
+
+https://gerrit.wikimedia.org/r/140194",1403212063,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"Change 140194 had a related patch set uploaded by Subramanya Sastry:
+(Bug 66514) Fix bug in nowiki-escaping of magic words
+
+https://gerrit.wikimedia.org/r/140194",1403035222,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"[subbu@earth lib] echo ""Fails when not in <b>sol context</b> __TOC__"" | node parse --html2wt --trace wt-escape
+[wt-esc]       | EWT: ""Fails when not in ""
+[wt-esc]       | ---No-checks needed---
+[wt-esc]       | EWT: ""sol context""
+[wt-esc]       | ---No-checks needed---
+[wt-esc]       | EWT: "" __TOC__""
+[wt-esc]       | SOL: false "" __TOC__""
+[wt-esc]       | ---Not-SOL and safe---
+Fails when not in '''sol context''' __TOC__
+[subbu@earth lib] echo ""Works when node is in sol context __TOC__"" | node parse --html2wt --trace wt-escape
+[wt-esc]       | EWT: ""Works when node is in sol context __TOC__""
+[wt-esc]       | SOL: true ""Works when node is in sol context __TOC__""
+[wt-esc]       | nl: true :text= ""Works when node is in sol context __TOC__""
+[wt-esc]       | T: ""Works when node is in sol context ""
+[wt-esc]       | T: {""type"":""SelfclosingTagTk"",""name"":""behavior-switch"",""attribs"":[{""k"":""word"",""v"":""__TOC__""}],""dataAttribs"":{""tsr"":[34,41],""src"":""__TOC__""}}
+[wt-esc]       | ---Found WT tokens---
+Works when node is in sol context <nowiki>__TOC__</nowiki>",1403029746,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"[subbu@earth lib] echo ""<b>__TOC__</b>"" | node parse --html2wt
+'''__TOC__'''
+[subbu@earth lib] echo ""<foobar>__DISAMBIG__</foobar>"" | node parse --html2wt
+<foobar>__DISAMBIG__</foobar>",1403029498,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"See e.g. https://www.mediawiki.org/w/index.php?title=VisualEditor/status&diff=prev&oldid=1034135 for an insertion without <nowiki>s, or https://www.mediawiki.org/w/index.php?title=VisualEditor:Bug_66514&oldid=1039124 for a more minimal test.
+
+The problem appears to be that <code>__Foo__</code> stops __Foo__ being recognised.",1403029182,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"See https://en.wikipedia.org/w/index.php?title=User%3ASsastry%2FVE_Test&diff=613314757&oldid=584723202
+
+and also this:
+
+[subbu@earth lib] echo ""This is a test of __DISAMBIG__ getting nowikied"" | node parse --html2wt
+This is a test of <nowiki>__DISAMBIG__</nowiki> getting nowikied",1403028853,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+VisualEditor: Work out whether removing repositionOnly parameter in DesktopContext.update() was a good idea,"It's unused now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402532640,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fk7j2az3j3ks52n4wvg5,task_description,resolved
+VisualEditor: Work out whether removing repositionOnly parameter in DesktopContext.update() was a good idea,Done in gerrit 141089.,1405375988,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fk7j2az3j3ks52n4wvg5,task_subcomment,NA
+VisualEditor: Work out whether removing repositionOnly parameter in DesktopContext.update() was a good idea,Fair point. Whoops. :-) Relabelling.,1402533549,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fk7j2az3j3ks52n4wvg5,task_subcomment,NA
+VisualEditor: Work out whether removing repositionOnly parameter in DesktopContext.update() was a good idea,"We still need to 1) get Trevor to look at whether it actually needs to die and 2) update callers, including ones which pass the parameter through",1402533498,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fk7j2az3j3ks52n4wvg5,task_subcomment,NA
+VisualEditor: Swapping an existing reference scrolls viewport to top,"* Create two references, one above the fold and one below
+* Scroll down to the one below the fold, inspect it, and use the ""Use existing reference"" feature to swap it out for the first one
+* The page is now scrolled to the top
+
+I think this might be because we delete and reinsert the reference?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65882",1402442100,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qwu6tsfyuvic4ungwofd,task_description,resolved
+VisualEditor: Swapping an existing reference scrolls viewport to top,Verified the fix in test2 and Betalabs.,1403557211,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qwu6tsfyuvic4ungwofd,task_subcomment,NA
+VisualEditor: Swapping an existing reference scrolls viewport to top,It is indeed fixed. Thanks Ed!,1403060858,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qwu6tsfyuvic4ungwofd,task_subcomment,NA
+VisualEditor: Swapping an existing reference scrolls viewport to top,May have been fixed by https://gerrit.wikimedia.org/r/#/c/138833/ ?,1402829459,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qwu6tsfyuvic4ungwofd,task_subcomment,NA
+VisualEditor: GeneratedContentNode rerenders with double-escaped HTML entities,"* Create a page with <syntaxhighlight lang=""javascript"">foo && bar</syntaxhighlight>
+* Open the page in VE
+* Inspect the syntaxhighlight block and change bar to baz
+* Observe &amp;&amp; instead of && in the preview
+
+Saving the change doesn't double-encode the ampersands though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402436820,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-riqtlu6jga2olfkc3ozl,task_description,resolved
+VisualEditor: GeneratedContentNode rerenders with double-escaped HTML entities,"
+
+*** This bug has been marked as a duplicate of bug 60332 ***",1404435630,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-riqtlu6jga2olfkc3ozl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in VE with Firefox
+2.Add a link or reference
+3.Select the node
+4.When the context menu appears, hover over it
+
+Observed Result:
+Its not highlighting the entire context menu, but some part of it
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13767}",1402426980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7nid5fuef63kkolvi3n,task_description,resolved
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,Verified the fix in production (en.wiki),1403300850,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7nid5fuef63kkolvi3n,task_subcomment,NA
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,Verified the fix in test2 running wmf9,1402696734,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7nid5fuef63kkolvi3n,task_subcomment,NA
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,Verified the fix in Betalabs,1402595959,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7nid5fuef63kkolvi3n,task_subcomment,NA
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,Fixed by gerrit 138906.,1402527451,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w7nid5fuef63kkolvi3n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"QUnit is complaining whenever I try and +2 code and it is preventing merges from happened e.g. https://gerrit.wikimedia.org/r/#/c/138375/ https://integration.wikimedia.org/ci/job/mwext-MobileFrontend-qunit/6228/console
+
+After talking to Antoine we think it might be a side effect of the warnings produced by: https://gerrit.wikimedia.org/r/#/c/135429/
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402417680,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_description,resolved
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138682 merged by jenkins-bot:
+Revert ""Revert ""Officially deprecate skin autodiscovery""""
+
+https://gerrit.wikimedia.org/r/138682",1402880758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138648 merged by Krinkle:
+defaults: Make values for 'wipe-workspace' and 'clean' explicit
+
+https://gerrit.wikimedia.org/r/138648",1402493269,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138682 had a related patch set uploaded by Bartosz Dziewoński:
+Revert ""Revert ""Officially deprecate skin autodiscovery""""
+
+https://gerrit.wikimedia.org/r/138682",1402432729,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),Thank you!,1402432689,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Confirmed fix by seeing that old files in skins/* are gone in workspaces on gallium, and confirmed again by touching a file `krinkle.txt` and confirming it was gone the next build.",1402427639,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138657 merged by jenkins-bot:
+mw-core-get: Clean workspace first
+
+https://gerrit.wikimedia.org/r/138657",1402426240,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138657 had a related patch set uploaded by Krinkle:
+mw-core-get: Clean workspace first
+
+https://gerrit.wikimedia.org/r/138657",1402425832,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138648 had a related patch set uploaded by Krinkle:
+defaults: Make values for 'wipe-workspace' and 'clean' explicit
+
+https://gerrit.wikimedia.org/r/138648",1402423802,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"(In reply to Krinkle from comment #7)
+> Taking mwext-VisualEditor-qunit as a usecase there's a couple facts:
+> 
+> 1) As being a repo not having the target git repo (VE) at its root, it has
+> git:clean:false and git:wipe:true (defaults), see 'use-zuul-for-mw-ext' in
+> jenkins-job-builder-config and confirmed on
+> https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/configure
+> (expand the Advanced sections)
+> 
+> * [ ] Clean after checkout [_]
+>       (runs `git clean`)
+> * [x] Wipe out workspace before build
+> 
+> 
+> 2) Looking at an example build:
+>   
+> https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/10021/
+> consoleFull
+>    - Wiping out workspace first.
+>    - Cloning repository
+> git://zuul.eqiad.wmnet/mediawiki/extensions/VisualEditor
+>    - /srv/deployment/integration/slave-scripts/bin/mw-core-get.sh master
+> 
+>    In that order.
+> 
+> 3) Even if this wouldn't happen, I think it's fine to use full wipe instead
+> of git-clean since all these run on the local system and should be able to
+> use hardlinks during the cloning (for the extension repo), and for mwcore we
+> use archive from a central repo /srv/ssd/gerrit/mediawiki/core.git so its'
+> fine to wipe the workspace of the extension repo)
+> 
+> 4) Confirmed by running mkdir ~/test; export WORKSPACE=~/test;
+> /srv/ssd/gerrit/mediawiki/core.git master; that the central git repo is not
+> dirty, the old files and skin directories are not in there.
+> 
+> 
+> So then why do we have RELEASE-NOTES-1.22 and skins/Modern.php in
+> mwext-VisualEditor-qunit workspace still?
+
+
+Looks like the real underlying bug is that the 'non-git' wipe option we have (the one that fully removes the work tree and will require a new git-clone on each build, the option we actually *are* using for extensions jobs) that wipe option (not git-clean) still restricts itself to where the git-clone will be. It doesn't wipe the workspace, it wipes workspace/{basedir}.",1402423463,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),Let's get this issue fixed now so we can work towards merging Bartosz's patch again.,1402422859,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138626 merged by jenkins-bot:
+Revert ""Officially deprecate skin autodiscovery""
+
+https://gerrit.wikimedia.org/r/138626",1402421790,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),I went ahead and merged Jon's revert so that mobile and VE development are not blocked.,1402421764,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Rephrasing bug summary. For the record, this only affects files that have actually landed in master. We do clean out files from proposed patches properly, this bug is specifically due to and related to fetching of latest master within extensions.",1402421541,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Taking mwext-VisualEditor-qunit as a usecase there's a couple facts:
+
+1) As being a repo not having the target git repo (VE) at its root, it has git:clean:false and git:wipe:true (defaults), see 'use-zuul-for-mw-ext' in jenkins-job-builder-config and confirmed on https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/configure (expand the Advanced sections)
+
+* [ ] Clean after checkout [_]
+      (runs `git clean`)
+* [x] Wipe out workspace before build
+
+
+2) Looking at an example build:
+   https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/10021/consoleFull
+   - Wiping out workspace first.
+   - Cloning repository git://zuul.eqiad.wmnet/mediawiki/extensions/VisualEditor
+   - /srv/deployment/integration/slave-scripts/bin/mw-core-get.sh master
+
+   In that order.
+
+3) Even if this wouldn't happen, I think it's fine to use full wipe instead of git-clean since all these run on the local system and should be able to use hardlinks during the cloning (for the extension repo), and for mwcore we use archive from a central repo /srv/ssd/gerrit/mediawiki/core.git so its' fine to wipe the workspace of the extension repo)
+
+4) Confirmed by running mkdir ~/test; export WORKSPACE=~/test; /srv/ssd/gerrit/mediawiki/core.git master; that the central git repo is not dirty, the old files and skin directories are not in there.
+
+
+So then why do we have RELEASE-NOTES-1.22 and skins/Modern.php in mwext-VisualEditor-qunit workspace still?",1402421458,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),Sorry Kunal :-(  And you have no idea how much it piss me off to have to revert such a patch from core :-(,1402419275,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"(In reply to Antoine ""hashar"" Musso from comment #2)
+> The reason is that since mediawiki/core.git is so huge to clone, we are
+> using git archive to grab a snapshot of MediaWiki in the Jenkins job
+> workspace.  A side effect is that files removed from the repository are not
+> removed from the workspace.
+
+Uck :/
+
+(In reply to Antoine ""hashar"" Musso from comment #4)
+> We could clean up the /skins/ directory in all workspaces potentially, but I
+> can't remember whether the same job could use a REL1_*** codebase which
+> would bring back the skins.
+
+Lets do that for now. People shouldn't be backporting stuff to REL branches in the near future, which gives us a little more time to fix jenkins to delete files properly.",1402419039,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"We could clean up the /skins/ directory in all workspaces potentially, but I can't remember whether the same job could use a REL1_*** codebase which would bring back the skins.",1402418671,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138626 had a related patch set uploaded by Hashar:
+Revert ""Officially deprecate skin autodiscovery""
+
+https://gerrit.wikimedia.org/r/138626",1402418534,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"https://gerrit.wikimedia.org/r/#/c/135429/ added a warning message whenever an old skin is found under Mediawiki /skins/ . The skins have been removed from core but are still present in Jenkins workspace.
+
+The reason is that since mediawiki/core.git is so huge to clone, we are using git archive to grab a snapshot of MediaWiki in the Jenkins job workspace.  A side effect is that files removed from the repository are not removed from the workspace.
+
+
+A potential way to solve it would be to have mediawiki core in a dedicated directory which we would be able to delete recursively before taking a snapshot with git archive.  From there we could symlink extensions from their dedicated directories under mediawiki /extensions/ .
+
+I also have an ongoing project to clone multiple repositories which might let us solve the issue.
+
+Meanwhile my recommendation is to revert the deprecation patch ( https://gerrit.wikimedia.org/r/#/c/135429/ ) until CI has catched up and ensure MediaWiki code base is clean in the Jenkins workspaces.",1402418470,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"(In reply to Jon from comment #0)
+
+> https://integration.wikimedia.org/ci/job/mwext-MobileFrontend-qunit/6228/
+
+Since Modern is no longer in core, why is it in the skins directory?",1402418375,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page","I have been getting this issue since this morning, I think this has something to do with changing image size when the size of an image gets adjusted or changed.
+I do not have the exact steps to reproduce for now.But it happened this one time when I changed the thumbnail left aligned image to centre float.
+
+This is the page where you will see the image on which I made the change and getting the edit conflict error :
+http://en.wikipedia.beta.wmflabs.org/wiki/9thjunechrome?veaction=edit
+
+We had encountered similar kind of issue quiet a while ago, which was fixed:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62172
+
+I am not sure, if the same cause is behind the bug or not
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402357800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2kxlh36d7ae4apn7vxff,task_description,resolved
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page",Verified the fix in production (en.wiki),1403300322,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page",Verified the fix in test2 running wmf 9,1402703931,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page",Verified the fix in Betalabs,1402424943,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page","Change 138521 merged by jenkins-bot:
+Followup bd49f97: prevent MWExtensionNodes from having children
+
+https://gerrit.wikimedia.org/r/138521",1402362445,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page","Change 138521 had a related patch set uploaded by Catrope:
+Followup bd49f97: prevent MWExtensionNodes from having children
+
+https://gerrit.wikimedia.org/r/138521",1402362192,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page","There is a very weird issue, probably introduced by Ed's extension nodes rewrite. Any extension node's children get duplicated on the way back to Parsoid: a hieroglyphs <table> gets two <tbody>s, a gallery <ul> contains all of its <li>s twice, etc.",1402361189,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+ResourceLoader: Modules should be able to specify dependencies evaluated at run-time,"Sometimes modules have dependencies that can't be determined until runtime; most obviously, code that requires shims for browser functionality that may be missing on a few clients.
+
+It would be great if instead of static dependencies, modules could specify dependencies that are evaluated at run-time and only loaded if needed.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56341",1402342020,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bkunv6kbite7pb74lhap,task_description,resolved
+ResourceLoader: Modules should be able to specify dependencies evaluated at run-time,"Change 135085 merged by jenkins-bot:
+resourceloader: Implement ""skip function"" feature
+
+https://gerrit.wikimedia.org/r/135085",1402546093,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bkunv6kbite7pb74lhap,task_subcomment,NA
+ResourceLoader: Modules should be able to specify dependencies evaluated at run-time,"Per discussion between Roan and me we're taking this use case as a story rather than a specific call to implementation.
+
+We won't be adding a feature to conditionally declare something as a dependency. So the following will not be the how it is used:
+
+visualeditor.dependencies = [es5]
+->
+visualeditor.dependencies = function (deps) {
+  if ( browser doesn't support es5 ) {
+    deps.push( es5);
+  }
+};
+
+
+Instead we're going to take it the other way around and have the condition be on the target module (e.g. es5.js instead of visualeditor).
+
+visualeditor.dependencies = [es5]
+es5.skip = function () {
+  return browser supports es5;
+};
+
+This way will result in much less duplication, and feels more semantically correct because it doesn't make sense for an application to have a dependency that can change. Modules are supposed to be a canonical representation of an interface, not a specific implementation, skin, language or file. Either the module to provide it or it doesn't. Instead visualeditor (or indeed, oojs) would declare it needs the thing that es5-shim.js provides. And es5-shim can decide to forego fetching of any actual files if it detects the environment has it already (either by native or another polyfill).
+
+This will make the experience for developers much easier (no need to duplicate if -conditions for es5 all over the place) and practically removes any possibility of abusing this feature for implementing any bad ideas.",1402343478,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-bkunv6kbite7pb74lhap,task_subcomment,NA
+ResourceLoader: Modules should be able to specify dependencies evaluated at run-time,"Change 135085 had a related patch set uploaded by Jforrester:
+[WIP] resourceloader: Implement ""skip function"" feature
+
+https://gerrit.wikimedia.org/r/135085",1402342072,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bkunv6kbite7pb74lhap,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","**Author:** `vojtech.dostal`
+
+**Description:**
+A student of Education program at Czech Wikipedia noticed that she cannot resize an image which is inserted as a frame. It is well possible to adjust the size in the preview mode, but saving it does not produce appropriately resized image frame. 
+
+
+see image under heading ""Půdorys"" at:
+https://cs.wikipedia.org/wiki/Kostel_Nanebevzet%C3%AD_Panny_Marie_%28Charvatce%29
+
+Thank you
+Vojtěch Dostál
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402266840,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jwcd6eadytsw2au77emm,task_description,resolved
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Change 138388 merged by jenkins-bot:
+Disable the size widget for 'frame' images
+
+https://gerrit.wikimedia.org/r/138388",1402426284,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Scratch my last remark. There is still a technical debt (that is being taken care of) about default vs. custom size but the issue in this case is that we don't follow the wikitext rules properly. 
+
+Frame images ignore size specification. 
+See wikitext documentation here: https://www.mediawiki.org/wiki/Help:Images#Size_and_frame",1402339903,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Change 138388 had a related patch set uploaded by Mooeypoo:
+Disable the size widget for 'frame' images
+
+https://gerrit.wikimedia.org/r/138388",1402339760,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Yes, after a bit of analysis, I believe there's a problem with the way the scalable object analyzes default vs custom values. I'm working on refactoring the way that works; we have a tech debt about this, too, I believe.",1402331038,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Thanks for this bug; it seems like a regression(?!) in MediaWiki. Moriel, can you confirm?",1402294292,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Change the Image type from Thumbnail to Frameless/Basic
+
+Observed Result:
+
+The checkbox for wrap option gets unchecked but the alignment tabs are still active
+
+See the screenshot attached
+
+This is happening in Betalabs but not on test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13997}",1402095420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qs2qv3kzzffml4p5gons,task_description,resolved
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",Verified the fix in production (en.wiki),1403300650,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",Verified the fix in test2 running wmf 9,1402700452,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",Verified the fix,1402520085,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",I REALLY mean gerrit 138663,1402518821,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",I mean gerrit 80d1240,1402518795,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",Fixed in 80d1240,1402518784,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression] ""manual subst"" hack doesn't work any more","It's not really possible to subst MediaWiki templates in VE yet (bug 49904). According to James F., it should be possible to write ""subst:Foo"" when inserting the template with some caveats.
+
+This doesn't seem to work at the time. For example, writing ""subst:Clarify"" in the English Wikipedia, shows the string ""{{subst:Clarify}}"", but as a template with a highlight. When the page is saved, the template {{Clarify|date=June 2014}} is inserted - not substed.
+
+From IRC:
+
+aharoni: Is there a way to do a subst to a template in VE?
+James_F: aharoni: Ish.
+James_F: aharoni: To add a template called ""Foo"", instead tell it to insert subst:Foo"".
+James_F: aharoni: But it doesn't get the TemplateData (so it's pretty icky).
+James_F: aharoni: There's a bug asking for an actual checkbox.
+[...]
+aharoni: James_F: about that subst thing: It doesn't seem to work. It inserts a literal {{subst:Foo}}.
+James_F: aharoni: Huh. That's a regression, then. :-(
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49904",1402089360,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-g4sg72aye2nbqzjdh3gd,task_description,invalid
+"VisualEditor: [Regression] ""manual subst"" hack doesn't work any more",Aha. Anti-subst tech? Whatever next?,1402171502,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g4sg72aye2nbqzjdh3gd,task_subcomment,NA
+"VisualEditor: [Regression] ""manual subst"" hack doesn't work any more","I can't replicate this bug. But I think this is actually invalid.
+
+This 'Clarify' template on enwiki uses some clever 'Unsubst' lua module hack to deliberately break subst - take a look at the source. Also notice how that 'date' parameter appeared from nowhere?
+
+I tested this out using the normal editor (just added '{{subst:Clarify}}'): https://en.wikipedia.org/w/index.php?title=User:Krenair/sandbox&diff=611955311&oldid=492366611
+
+If I try any other non-Unsubst template, it's fine. For example, I added 'subst:Cite web' from VE: https://en.wikipedia.org/w/index.php?title=User:Krenair/sandbox&diff=611955603&oldid=611955311",1402153458,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-g4sg72aye2nbqzjdh3gd,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page","Screenshot
+
+Steps to reproduce:
+
+1.Open any page with VE in Firefox or Chrome
+
+2.Make an Edit
+
+3.Click on ""Switch to source editing""
+
+Observed Result:
+It does not open the wikitext editor for the page, rather a message appears at the op of the page: 
+Some parts of the edit form did not reach the server; double-check that your edits are intact and try again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13873}",1402013460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytqk243gnjxzenhu2jo7,task_description,resolved
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",Verified the fix in production(en.wiki),1403299864,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",Verified the fix in test2 running wmf9,1402705356,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",Verified the fix in Betalabs,1402084693,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",Fixed by the fix for bug 66168.,1402084650,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",This is happening even for a new page where no edit has been done yet :(,1402014082,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,"Obviously it'd also be nice if fatals didn't happen, but I have less faith that that is possible in shorter time…
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402012080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-chatnkffcac2ryz34vhn,task_description,resolved
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,"Change 200649 merged by jenkins-bot:
+Don't break the editor if paste handling fails
+
+[[https://gerrit.wikimedia.org/r/200649]]",1427756404,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,"Change 200649 had a related patch set uploaded (by Catrope):
+Don't break the editor if paste handling fails
+
+[[https://gerrit.wikimedia.org/r/200649]]
+",1427743719,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,"Mostly seems to be caused by elements it doesn't recognise (? like <section>), especially when copying bits of tables and other structures from non-MediaWiki sources (e.g. Google Docs, Bugzilla or other places). Lots of different mystical errors as well about e.g. refusing to insert a closing tag that hasn't been opened.",1402512088,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,Need an example so I know where to put the try/catch.,1402507964,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,*** Bug 64009 has been marked as a duplicate of this bug. ***,1402505914,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Screenshot
+
+Steps to reproduce:
+
+1.Open any page in Betalabs or test2 with VE in Firefox
+
+2.Make an edit
+
+3.Save the page
+
+4.Reopen the page
+
+Observed Result:
+
+In the console the following error appears:
+
+
+TypeError: this.documentView is null
+
+Also, another issue that is happening is, after editing if you try to switch to edit source mode, it is not opening the wikitext editor.Rather showing a message:
+Some parts of the edit form did not reach the server; double-check that your edits are intact and try again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13849}",1402006920,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lekklfuupduztoemlst2,task_description,resolved
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox",Verified the fix in production en.wiki,1403118845,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox",Not yet fixed in en.wiki,1402619049,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Change 139207 merged by Catrope:
+*Actual* death and/or *actual* destruction
+
+https://gerrit.wikimedia.org/r/139207",1402608657,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Change 139207 had a related patch set uploaded by Catrope:
+*Actual* death and/or *actual* destruction
+
+https://gerrit.wikimedia.org/r/139207",1402608199,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox",This is happening in production.Didn't we backport it?,1402607600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox",Verified the fix in Betalabs,1402354186,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","(In reply to Ed Sanders from comment #8)
+> MW hasn't had a core update since this was merged.
+> 
+> FYI: If there isn't a commit called 'Update VE core submodule to master'
+> above a core commit you are testing on this page:
+> 
+> https://gerrit.wikimedia.org/r/#/q/is:watched+status:merged,n,z
+> 
+For that link to work, you need to be logged in and be watching the right projects :)
+
+More portable link: https://gerrit.wikimedia.org/r/#/q/status:merged+AND+%28+project:mediawiki/extensions/VisualEditor+OR+project:VisualEditor/VisualEditor+%29,n,z",1402346604,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","MW hasn't had a core update since this was merged.
+
+FYI: If there isn't a commit called 'Update VE core submodule to master' above a core commit you are testing on this page:
+
+https://gerrit.wikimedia.org/r/#/q/is:watched+status:merged,n,z
+
+it won't be in MW yet.",1402346453,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","This is still happening in Firefox for Betalabs, So reopening it",1402345997,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Change 138014 merged by jenkins-bot:
+*Actual* death and/or *actual* destruction
+
+https://gerrit.wikimedia.org/r/138014",1402146215,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Change 138014 had a related patch set uploaded by Catrope:
+*Actual* death and/or *actual* destruction
+
+https://gerrit.wikimedia.org/r/138014",1402085007,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","The error from comment 2 happens because the old destroyed surface is getting blurred, and DesktopContext is responding to that.
+
+The fundamental issue is this.fragment.select(); in the teardown process of ve.ui.Dialog, which runs 200ms after the save dialog closes, at which point the surface is already hidden and lots of stuff goes wrong.
+
+Beside that, though, we should be much more aggressive about destroying things properly. And also audit things we do after a delay like this (so potentially anything in a setup/teardown process) because the user might have deactivated the editor in the meantime.",1402016517,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","The ""Switching to edit source mode not opening the wikitext editor"" issue is happening in Chrome as well, however the error found for Firefox in not appearing for Chrome, so I am taking this issue to a different bug, assuming it is not related.",1402013045,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Also getting this error now:
+
+Error: Range error: Range is no longer valid after DOM mutation ([WrappedRange(""link"":0, ""link"":4)])
+after applying link to the text ""link""",1402010177,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","This seems to be happening because, somehow, the old torn-down ce.Surface gets a focus event, calls this.surfaceObserver.startTimerLoop(), but this explodes because the SurfaceObserver has been detached already and its .documentView is null.
+
+We should make sure we properly destroy the old surface.",1402007173,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"<nowiki> tags appear when editing on the Hebrew Wikipedia:
+
+Examples:
+https://he.wikipedia.org/w/index.php?title=%D7%99%D7%A8%D7%95%D7%9F_%D7%9E%D7%A8%D7%92%D7%95%D7%9C%D7%99%D7%9F&curid=1154717&diff=15542199&oldid=15542181
+
+https://he.wikipedia.org/w/index.php?title=%D7%99%D7%A8%D7%95%D7%9F_%D7%9E%D7%A8%D7%92%D7%95%D7%9C%D7%99%D7%9F&curid=1154717&diff=15542199&oldid=15542181
+
+https://he.wikipedia.org/w/index.php?title=HOT&diff=15542428&oldid=15528284
+
+From the given examples, it seems to be related to editing internal links?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1401996780,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_description,declined
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"Corruption bugs are handled independently on a case-by-case basis; nothing in this list indicates that the <nowiki> issue is specifically related to Hebrew or RTL.
+
+Space in the beginning of paragraphs is followed up in this bug: https://bugzilla.wikimedia.org/show_bug.cgi?id=66628
+
+Transforming a star into bullet point (in the beginning of a line) is followed in this bug report: https://bugzilla.wikimedia.org/show_bug.cgi?id=51408
+
+The rest seem to be errors in typing wikitext.",1412539179,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_subcomment,NA
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"After further analysis, here are the results:
+
+Most of the nowiki problems seem to happen due to typing wikitext in the editor. For instance, typing ''word'' or '''word''' instead of marking the word as italics or bold, or typing literal == which VE then marks as =<nowiki/>= to prevent wikitext'ifying the result.
+
+There are, however, some typing issues we could work on to make the experience easier on users:
+
+1. Users typing a space at the beginning of a paragraph; this seems to be a mistake most of the time. Since a space at the beginning of a paragraph in wikitext transforms the paragraph to a <pre>, VE adds a <nowiki /> tag after it. It might be better if we strip those spaces when we save the page.
+
+2. Users sometimes add list items by typing the literal * at the beginning of a line. While this is wikitext function (so VE wraps it with <nowiki>) it actually might make sense to try and transform any * at the beginning of lines to new bullet points; this is a the behavior that LibreOffice and Word are following, so it might be reasonable to have VE follow suit.
+
+There are very few <nowiki> tags that I saw that are actual corruption. A new one that was reported recently on hewiki might show a problem with reading the wikitext headings wrong, so upon deleting the heading all that's left are == which VE marks with =<nowiki>= (see here: https://he.wikipedia.org/w/index.php?title=%D7%A9%D7%95%D7%9C%D7%97%D7%9F&diff=15566083&oldid=154101 ) 
+
+Some, like this one, seem to show a problem with existing <nowiki> tags that then get ""worse"" after edit: https://en.wikipedia.org/w/index.php?title=Rathmore,_County_Kildare&curid=43246971&diff=618885701&oldid=618885287
+
+We might want to consider marking any existing <nowiki>, perhaps?
+
+In any case, these seem to be fairly uncommon and we should treat them on a case to case basis.",1408373441,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_subcomment,NA
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"This seems to also happen in the English wikipedia with quotes and asterix characters.
+
+Examples:
+
+https://en.wikipedia.org/w/index.php?title=Scar_(The_Lion_King)&curid=30258014&diff=619292425&oldid=619246147
+
+https://en.wikipedia.org/w/index.php?title=Scar_(The_Lion_King)&curid=30258014&diff=619165895&oldid=619158383
+
+https://en.wikipedia.org/w/index.php?title=Ravi_Babu&curid=24981592&diff=618944152&oldid=611211776
+
+https://en.wikipedia.org/w/index.php?title=Adoni&curid=2329629&diff=618931054&oldid=618930241
+
+https://en.wikipedia.org/w/index.php?title=Mia_Freedman&curid=10942134&diff=618755773&oldid=618669491
+
+(Several <nowiki> tags right after quotes)
+https://en.wikipedia.org/w/index.php?title=Rathmore,_County_Kildare&curid=43246971&diff=618885701&oldid=618885287
+
+(Around an asterix)
+https://en.wikipedia.org/w/index.php?title=Tulluru&curid=6910687&diff=618802171&oldid=618802085",1406838421,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_subcomment,NA
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"I've gone through articles that had 'nowiki' and VisualEditor tags in hewiki to try and find the common error, and as far as I can see, 90% of the errors involve quotes ("") and the others are * and |
+
+Examples:
+
+https://he.wikipedia.org/w/index.php?title=%D7%A2%D7%95%D7%A4%D7%A8_%D7%A2%D7%99%D7%A0%D7%99&curid=309950&diff=15774877&oldid=15774872
+
+https://he.wikipedia.org/w/index.php?title=%D7%94%D7%90%D7%A8%D7%99_%D7%A4%D7%95%D7%98%D7%A8_%D7%95%D7%90%D7%95%D7%A6%D7%A8%D7%95%D7%AA_%D7%94%D7%9E%D7%95%D7%95%D7%AA_(%D7%A1%D7%A8%D7%98)&curid=794595&diff=15773383&oldid=15733742
+
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%95%D7%A2%D7%A6%D7%AA_%D7%94%D7%AA%D7%9C%D7%9E%D7%99%D7%93%D7%99%D7%9D_%D7%95%D7%94%D7%A0%D7%95%D7%A2%D7%A8_%D7%94%D7%90%D7%A8%D7%A6%D7%99%D7%AA&curid=73014&diff=15770323&oldid=15756104
+
+https://he.wikipedia.org/w/index.php?title=%D7%90%D7%9C%D7%99_%D7%A4%D7%99%D7%A0%D7%99%D7%A9&curid=144088&diff=15769264&oldid=15724086
+
+https://he.wikipedia.org/w/index.php?title=%D7%93%D7%95%D7%A7%D7%98%D7%95%D7%A8_%D7%94%D7%95_-_%D7%9E%D7%A4%D7%9C%D7%A6%D7%95%D7%AA&curid=1085331&diff=15768361&oldid=15766030
+
+https://he.wikipedia.org/w/index.php?title=%D7%A1%D7%A8%D7%98_%D7%90%D7%A8%D7%91%D7%A2-%D7%9E%D7%9E%D7%93&curid=1156586&diff=15764947&oldid=15051822
+
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A0%D7%97%D7%9D_%D7%A4%D7%A8%D7%95%D7%A9&curid=33000&diff=15764545&oldid=15571348
+
+https://he.wikipedia.org/w/index.php?title=%D7%A2%D7%95%D7%9E%D7%A8_%D7%93%D7%9E%D7%90%D7%A8%D7%99&curid=908862&diff=15763688&oldid=15763681
+
+https://he.wikipedia.org/w/index.php?title=%D7%A2%D7%93_%D7%A2%D7%A6%D7%9D_%D7%94%D7%99%D7%95%D7%9D_%D7%94%D7%96%D7%94_(%D7%A1%D7%93%D7%A8%D7%AA_%D7%98%D7%9C%D7%95%D7%95%D7%99%D7%96%D7%99%D7%94)&curid=1016962&diff=15762484&oldid=15762481
+
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%91%D7%A6%D7%A2_%D7%A6%D7%95%D7%A7_%D7%90%D7%99%D7%AA%D7%9F&curid=1201545&diff=15761499&oldid=15761352
+
+
+This might be an issue of bad character escaping or encoding.",1406835764,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_subcomment,NA
+"VisualEditor: Fields are case sensitive in citation dialog, allowing duplicates of the same field","Two URL fields visible.
+
+The citation dialog field selector is case sensitive. This allows the same field to be added multiple times as long as it's a different case. This results in a ""multiple <field>"" error when the citation is inserted because the fields are treated as case insensitive. 
+
+This issue could organically come up if a citation was added using wikitext and then another user inspected the citation in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F13823}",1401993720,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-67wxtc4ozjdd24rgjf7t,task_description,invalid
+"VisualEditor: Fields are case sensitive in citation dialog, allowing duplicates of the same field","Not a VE bug :). Turns out this was actually because ""URL,"" which is an accepted alias of ""url"" by module:citation/cs1, wasn't in the templatedata as an alias. This is probably true of a LOT of the other identifiers as well. I fixed this for url on en wiki for the ""big 4"" but this might also be an issue with other identifiers that are commonly capitalised as well, and probably on any template that is based on this module.",1408273027,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-67wxtc4ozjdd24rgjf7t,task_subcomment,NA
+"VisualEditor: Fields are case sensitive in citation dialog, allowing duplicates of the same field","Created attachment 15574
+Two fields error
+
+**Attached**: {F13824}",1401994034,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-67wxtc4ozjdd24rgjf7t,task_subcomment,NA
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"See comments on https://gerrit.wikimedia.org/r/#/c/136981
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401925620,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wiosc4sy22tsxnhzhxot,task_description,resolved
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"Change 138500 merged by jenkins-bot:
+Initialize 'default' size properly in media edit dialog
+
+https://gerrit.wikimedia.org/r/138500",1402425709,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wiosc4sy22tsxnhzhxot,task_subcomment,NA
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"Change 138497 merged by jenkins-bot:
+Reorganize initialization of default size in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/138497",1402423004,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wiosc4sy22tsxnhzhxot,task_subcomment,NA
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"Change 138500 had a related patch set uploaded by Mooeypoo:
+Initialize 'default' size properly in media edit dialog
+
+https://gerrit.wikimedia.org/r/138500",1402357224,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wiosc4sy22tsxnhzhxot,task_subcomment,NA
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"Change 138497 had a related patch set uploaded by Mooeypoo:
+Reorganize initialization of default size in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/138497",1402356867,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wiosc4sy22tsxnhzhxot,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"VE does not seem to accept the following link:
+
+https://graphite.wikimedia.org/render/?width=588&height=310&_salt=1401910888.742&from=00%3A00_20140513&until=23%3A59_20140604&target=frontend.navtiming.totalPageLoadTime.desktop.authenticated.median&target=frontend.navtiming.totalPageLoadTime.desktop.anonymous.median
+
+Instead, it reverts to the highlighted text as the link target.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66139",1401911520,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_description,resolved
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"Change 138016 merged by jenkins-bot:
+Don't send invalid titles from the link inspector to the API
+
+https://gerrit.wikimedia.org/r/138016",1402102911,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"Change 138016 had a related patch set uploaded by Alex Monk:
+Don't sent invalid titles from the link inspector to the API
+
+https://gerrit.wikimedia.org/r/138016",1402085103,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"External URLs can be valid titles, we just want to ignore invalid titles (i.e. things over 255 characters).",1402081951,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"The HTTP 400 error we get comes with an error: {""code"":""request_too_long"",""info"":""Prefix search request was longer longer than the maximum allowed length. (267 > 255)""}
+
+This is sent by CirrusSearch. Which explains why some wikis don't have this issue.",1402080736,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),I can replicate this on mediawiki.org but not en.wikipedia.org or my local dev wiki.,1402011942,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"This is two separate bugs – we shouldn't be sending these to the API anyway, but we also should cope with the 400 error, which I've made into bug 66139.",1401914590,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"This shows up in the JS console:
+
+Failed to load resource: the server responded with a status of 400 (Bad Request) https://www.mediawiki.org/w/api.php?format=json&action=query&generator=pref…edian&gpsnamespace=0&prop=info%7Cpageprops&ppprop=disambiguation&redirect=",1401912829,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),Browser: Chromium 35.0.1916.114 Debian Linux,1401911579,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: isMsie doesn't catch MSIE 11+,"So odd behaviour untested in MSIE11 for CE isn't done differently…
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401835080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-adgbuexuqgrstkyhiwax,task_description,resolved
+VisualEditor: isMsie doesn't catch MSIE 11+,Fixed by Roan by the simple expediency of deleting this function.,1409099544,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-adgbuexuqgrstkyhiwax,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null","Screenshot
+
+Steps to reproduce:
+
+1.Open a page
+2.Open a link inspector
+3.Click on the Add label link
+
+Observed Result:
+TypeError: this.linkNode is null shows up in the console and cannot close the link inspector afterwards.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14090}",1401738360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_description,resolved
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null",Verified the fix in test2,1402343639,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null",Verified the fix in Betalabs,1401747819,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null","Change 136899 merged by jenkins-bot:
+Remove link node inspector from insert menu
+
+https://gerrit.wikimedia.org/r/136899",1401743256,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null","Change 136899 had a related patch set uploaded by Catrope:
+Remove link node inspector from insert menu
+
+https://gerrit.wikimedia.org/r/136899",1401743022,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","To reproduce:
+1. Edit an article in the Hebrew Wikipedia.
+2. Click Insert (הוספה) -> Reference (הערת שוליים).
+Observed: The ""Cite"" item in the toolbar is in English.
+There seems to be a message for it - visualeditor-toolbar-cite-label, and it was translated to Hebrew on May 12 and exported to the code, but it doesn't appear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1401723360,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_description,resolved
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs",Cherry-picks going out tomorrow.,1401927706,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136782 merged by jenkins-bot:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136782",1401924179,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136783 merged by jenkins-bot:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136783",1401924146,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136783 had a related patch set uploaded by Jforrester:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136783",1401730842,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136782 had a related patch set uploaded by Jforrester:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136782",1401730828,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136767 merged by jenkins-bot:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136767",1401730718,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136767 had a related patch set uploaded by Amire80:
+Use the message visualeditor-toolbar-cite-label correctly
+
+https://gerrit.wikimedia.org/r/136767",1401727586,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+VisualEditor: Add reference (footnote) dialog is LTR in RTL wikis,"To reproduce:
+1. Edit an article in the Hebrew Wikipedia.
+2. Click Insert (הוספה) -> Reference (הערת שוליים).
+Observe: The contenteditable div for writing the footnote text is forced to dir=""ltr"".
+Expected: It must be in the direction of the wiki - dir=""rtl"", or simply without the dir, and inherit the direction.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401722160,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-g37btpr3pykwbk3ho5jh,task_description,resolved
+VisualEditor: Add reference (footnote) dialog is LTR in RTL wikis,This seems to be fixed now with the new reference/cite system.,1406316915,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-g37btpr3pykwbk3ho5jh,task_subcomment,NA
+VisualEditor: adding a new link shows the target of the previously-added link for a few moments in the link inspector,"To reproduce:
+
+1. Edit an article with the words Dog and Cat.
+2. Select the word ""Dog"". Press Ctrl-K and add an internal link to Dog.
+3. Select the word ""Cat"".
+4. Press Ctrl-K.
+
+Observe: In the auto-suggestions, ""Dog"" appears for a few moments before it is replaced by ""Cat"".
+Expected: Linking to ""Dog"" is irrelevant here. The previous target and auto-suggestions shouldn't be reused here.
+
+I find this rather disruptive because I want to use the link inspector for its primary purpose of adding links quickly, and this actually delays me by a few seconds. What's worse is that if I'm not careful, I can add a link with the wrong target.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401699120,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-m3mxko4zbo6nl2kgz2by,task_description,resolved
+VisualEditor: adding a new link shows the target of the previously-added link for a few moments in the link inspector,"Change 138113 merged by jenkins-bot:
+[BREAKING CHANGE] Update OOjs UI to v0.1.0-pre (9f4f250f88) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138113",1402533081,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m3mxko4zbo6nl2kgz2by,task_subcomment,NA
+VisualEditor: adding a new link shows the target of the previously-added link for a few moments in the link inspector,"Change 138113 had a related patch set uploaded by Jforrester:
+[BREAKING CHANGE] Window process cleanup
+
+https://gerrit.wikimedia.org/r/138113",1402353749,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m3mxko4zbo6nl2kgz2by,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,"Steps to reproduce;
+
+1.Open a page 
+2.Open the reference dialog 
+3.Click on use existing reference or just simply close it
+
+Observed Result:
+TypeError: sel.nativeSelection is null aappears in the console
+
+Environment:test 2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1401431160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dtf7e3athicgtegt5jra,task_description,resolved
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,Verified the fix in en.wiki running wmf8,1402685315,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,Verified the fix in test2,1402344115,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,Verified the fix in Betalabs,1401491594,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,"Change 136451 merged by jenkins-bot:
+Cleanup createSurface methods
+
+https://gerrit.wikimedia.org/r/136451",1401484639,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,"Change 136451 had a related patch set uploaded by Jforrester:
+Cleanup createSurface methods
+
+https://gerrit.wikimedia.org/r/136451",1401482937,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,Almost certainly the same cause as bug 65934,1401480027,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,This is also happening while closing Media Settings dialog in Firefox,1401433112,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,"Screenshot
+
+Steps to reproduce
+
+1.Open a page
+2.Go to Insert>Reference
+3.Type in a text as reference
+
+Observed Result:
+Each letters are getting added in each line , ends with a pawn then the text appears.The following error appears in the console:
+
+Error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds
+
+After clicking on ""Insert Reference"":
+
+TypeError: sel.nativeSelection is null
+
+After saving the page:
+TypeError: elem.ownerDocument.defaultView is null
+
+This issue is happening on Firefox only.
+
+Environmen:test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13820}",1401430500,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7xd4p7fhhty3seeornpc,task_description,resolved
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,Verified the fix in en.wiki running wmf8,1402685106,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,Verified the fix in test2,1402344699,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,Verified the fix in Betalabs,1401491568,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,"Change 136451 merged by jenkins-bot:
+Cleanup createSurface methods
+
+https://gerrit.wikimedia.org/r/136451",1401484642,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,"Change 136451 had a related patch set uploaded by Jforrester:
+Cleanup createSurface methods
+
+https://gerrit.wikimedia.org/r/136451",1401482932,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,Caused by https://gerrit.wikimedia.org/r/#/c/135012/ being a breaking change but not marked as such. Will be fixed once https://gerrit.wikimedia.org/r/#/c/135014 is merged.,1401479343,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"James's suggestion: never split a paragraph with a block image. It's not at all obvious what happened, especially if the image is floated right. Instead, we should put the image at the beginning of the paragraph. This would apply when inserting an image, converting an inline image to a block image, and when drag-and-dropping an image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51666",1401320100,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-f45ircs47t3ihtnmxal3,task_description,resolved
+VisualEditor: Only insert block images at the start of a paragraph,"Please discuss Tech News issues by going to Tech News (e.g. Talk page) and not to a VE bug report in Bugzilla. General questions like at the end of comment 5, even if you might consider image maps somehow related to block images in general, should better go to IRC or mailing lists. Thanks.",1403364381,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"(In reply to James Forrester from comment #4)
+
+See Bug 66896 (general RFE plus a real bug)
+
+For allowing max-height and general improvement to client-side (and text-friendly) image rescaling which should also be frienfly with the current (broken) Mobile view.",1403315507,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"- It is a bug of the Tech News that incorrectly says it applies to all images.
+- This is in our control (Tech News can be fixed to say it applies only to ""block images"", i.e. images with left/right/center/thumb parameters, and not to other inline images; notably the many emoticon images used in may places in the middle of paragraphs: these images must not be constrained to be only at the start of paragraphs, when inserted or modified with the VisualEditor! Asian users will immediately think that the change is undesirable if they think they can't use their emojis without a supporting font !)",1403315174,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"(In reply to Philippe Verdy from comment #5)
+> So the current Tech News needs correction.
+
+Our submissions to Tech News are generally re-written to be ""simpler"" and wrong. This is not (a) a bug and (b) within our control.
+
+The rest of this is not germane for this bug; please take discussion to a venue for proper discussion, like MediaWiki.org or a mailing list.",1403313393,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"So the current Tech News needs correction.
+The expressions ""block image"" is ambiguous, at first reading I wondered who was right.
+
+Yes having client-side image resizing with just the addition of support of custom CSS for images would be a bonus.
+
+I know this works because this is already visible and used on the Mobile view even if it works with ""max-width:100%"" (used with the ""box-model"" quirk that should have never been used in its specific stylesheet, and which is absolutely not needed)
+
+It also works best with the support of ""image sets"" (now enabled by default in MediaWiki that can lists several thumbnail sizes, at resolutions 1x, 1.5x and 2x; but it could also add 0.5x and 0.75x for best results, letting browsers select the best interpolations depending on screen resolution and/or zoom mode; and ideally, the image sets for SVG images could also list the native SVG format for the best quality needed for images replacing complex text)
+
+----
+
+For now the current Tech News for this week (referencing this bug) needs fixing as it is interpreted as meaning all images.
+
+And what you call a ""block image"" is in MediaWiki an [[image:]] or [[file:]] with ""left"" or ""right"" floating-mode attribute, or ""center"", or ""thumb(nail)"" (your terminology is strange, because in HTML images are always inline by default, and even MediaWiki keeps them inline by placing the generated <img> element, possibly surrounded by an <a> element, within a block element).
+
+----
+
+Also, what is happening to image maps in the VisualEditor ? (they are also inline by default, and probably should be resizable by the client)",1403311665,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"(In reply to Philippe Verdy from comment #3)
+> What is happening to **inline** images (sometimes used to replace some text
+> which is hard to render, such as letters with stacked diacritics rarely
+> supported in fonts, where the word is instead rendered using an SVG image,
+> or small icons, when they are not inserted by using a custom template?
+
+Nothing. This bug is only about block images, as it says.
+
+> OK there's a problem with inline images because they cannot be easily
+> dimensionned according to the current font size and positioned according to
+> the line-height and specific baseline of some scripts, and they cannot match
+> other font styles. But they are still needed in some cases because it is not
+> possible to build custom fonts in pages without support of page-level CSS,
+> or scoped CSS (it is impossible with inline CSS in element style attributes
+> that don't have selectors).
+> 
+> ----
+> 
+> Note that it should be possible to rescale an inline SVG image to fit in the
+> 1.6em line-height using CSS ""max-height:1.6em"" in the <img> HTML element,
+> but MediaWiki still does not support setting any ""style="" attribute in
+> [[File:name]] or [[Image:name]].
+> 
+> You can see the effect of client-side image rescaling in the Mobile view of
+> our wikis: it uses ""max-width:100% !important"" (in addition to other really
+> dirty quirks such as changing the ""box-model:"" of almost all elements to
+> ""border-box"" inherited from old ""IE quirks mode"", rather than the standard
+> ""content-box"", breaking lots of layouts, even though the mobile view has
+> never been meant to be used with old version of IE; but meant to be used
+> with standard HTML! Someone shoud rework the Mobile view to remove this
+> dirty quirk that breaks lots of layouts as it applies to ALL spans and
+> blocks, forcing many templates to manually set the ""content-box:content-box""
+> everywhere and dewikifying lists with ol/ul + li or dl + dt/dd...).
+> 
+> With the support client-side image rescaling (support of ""max-height:"" style
+> in wiki-images), inline images are safe in the middle of a paragraph (for
+> now they are supported provided that template specify small heights, below
+> 20px).
+
+
+This feels like a MediaWiki bug (""Please let me size text-inline images to automatically be line-height"") – do you want to create one?",1403308771,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"What is happening to **inline** images (sometimes used to replace some text which is hard to render, such as letters with stacked diacritics rarely supported in fonts, where the word is instead rendered using an SVG image, or small icons, when they are not inserted by using a custom template?
+
+OK there's a problem with inline images because they cannot be easily dimensionned according to the current font size and positioned according to the line-height and specific baseline of some scripts, and they cannot match other font styles. But they are still needed in some cases because it is not possible to build custom fonts in pages without support of page-level CSS, or scoped CSS (it is impossible with inline CSS in element style attributes that don't have selectors).
+
+----
+
+Note that it should be possible to rescale an inline SVG image to fit in the 1.6em line-height using CSS ""max-height:1.6em"" in the <img> HTML element, but MediaWiki still does not support setting any ""style="" attribute in [[File:name]] or [[Image:name]].
+
+You can see the effect of client-side image rescaling in the Mobile view of our wikis: it uses ""max-width:100% !important"" (in addition to other really dirty quirks such as changing the ""box-model:"" of almost all elements to ""border-box"" inherited from old ""IE quirks mode"", rather than the standard ""content-box"", breaking lots of layouts, even though the mobile view has never been meant to be used with old version of IE; but meant to be used with standard HTML! Someone shoud rework the Mobile view to remove this dirty quirk that breaks lots of layouts as it applies to ALL spans and blocks, forcing many templates to manually set the ""content-box:content-box"" everywhere and dewikifying lists with ol/ul + li or dl + dt/dd...).
+
+With the support client-side image rescaling (support of ""max-height:"" style in wiki-images), inline images are safe in the middle of a paragraph (for now they are supported provided that template specify small heights, below 20px).",1403307572,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"Change 140037 merged by jenkins-bot:
+Insert images at the start of paragraphs
+
+https://gerrit.wikimedia.org/r/140037",1403134828,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"Change 140037 had a related patch set uploaded by Mooeypoo:
+Insert images at the start of paragraphs
+
+https://gerrit.wikimedia.org/r/140037",1402958320,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Viewport scrolls to top after drag-and-dropping image,"Go to a page with an image that's below the fold (i.e. you have to scroll down to see it). Drag it and drop it in a position that's also below the fold.
+
+The viewport scrolls up to the top, scrolling the image out of view :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62420
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66462",1401319920,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-34u5syhh5mqyo7rcvvfm,task_description,resolved
+VisualEditor: Viewport scrolls to top after drag-and-dropping image,"Change 138833 merged by jenkins-bot:
+Don't refocus the document in onModelSelect
+
+https://gerrit.wikimedia.org/r/138833",1402534639,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-34u5syhh5mqyo7rcvvfm,task_subcomment,NA
+VisualEditor: Viewport scrolls to top after drag-and-dropping image,"Change 138833 had a related patch set uploaded by Esanders:
+Don't refocus the document in onModelSelect
+
+https://gerrit.wikimedia.org/r/138833",1402502781,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-34u5syhh5mqyo7rcvvfm,task_subcomment,NA
+"VisualEditor: Cannot go to the next line of an article after inserting a special character in a block slug and ""TypeError: Inserted data is trying to close the root node (at index 0)"" appears","Screenshot
+
+Steps to reproduce:
+
+1.Open this page with VE:http://en.wikipedia.beta.wmflabs.org/wiki/28thmayff?veaction=edit
+
+2.Insert a special character in the block slug just on top of the last image in the page
+
+3.Press enter to go to the next line
+
+Observed Result:
+Cannot go to the next line, the following error appears:
+
+Error: Inserted data is trying to close the root node (at index 0)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13657}",1401309240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hzfx6auxygw63xeggrj6,task_description,resolved
+"VisualEditor: Cannot go to the next line of an article after inserting a special character in a block slug and ""TypeError: Inserted data is trying to close the root node (at index 0)"" appears",Appears to work now.,1423749786,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hzfx6auxygw63xeggrj6,task_subcomment,NA
+"VisualEditor: Cannot go to the next line of an article after inserting a special character in a block slug and ""TypeError: Inserted data is trying to close the root node (at index 0)"" appears",Yay for things in block slugs. :-(,1402525358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hzfx6auxygw63xeggrj6,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Since a few days, there are reports of the version dropdown being empty even though the branches exist. This makes it impossible to download extensions from ExtensionDistributor.
+
+https://www.mediawiki.org/wiki/Thread:Extension_talk:CirrusSearch/CirrusSearch_download
+https://www.mediawiki.org/wiki/Thread:Project:Current_issues/Can%27t_download_extensions
+
+--------------------------
+**Version**: master
+**Severity**: major",1401283020,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ypgoy4zxc5bctzwefulz,task_description,resolved
+ExtensionDistributor: Some extensions have no versions available for download,"We're no longer using github at all, so this should no longer be an issue.",1406830858,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"I203d635b2a5e42197913d7d8b7cd8da083dd8981 was also merged, which will provide negative cache entries when a branch doesn't exist, which should make this a lot better in the short term.
+
+After discussing with ^d and James_F, we're going to stop using github and instead use a labs setup I created (ex: http://extdist.wmflabs.org/?version=REL1_23&ext=VisualEditor) which will make it so we don't need to worry about ratelimiting at all.",1405544184,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Change 146386 merged by jenkins-bot:
+Allow making API requests as an authenticated user
+
+https://gerrit.wikimedia.org/r/146386",1405544032,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Change 146394 merged by jenkins-bot:
+Display an error if no branches are found
+
+https://gerrit.wikimedia.org/r/146394",1405543516,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Change 146394 had a related patch set uploaded by Florianschmidtwelzow:
+Display an error if no branches are found
+
+https://gerrit.wikimedia.org/r/146394",1405411159,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Change 146386 had a related patch set uploaded by Legoktm:
+Allow making API requests as an authenticated user
+
+https://gerrit.wikimedia.org/r/146386",1405402706,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"legoktm@terbium:~$ curl --proxy url-downloader.wikimedia.org:8080 -i https://api.github.com/repos/wikimedia/mediawiki-extensions-MassMessage/tarball/REL1_23
+
+X-RateLimit-Limit: 60
+X-RateLimit-Remaining: 0
+
+and the content body:
+
+{
+  ""message"": ""API rate limit exceeded for <ip>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)"",
+  ""documentation_url"": ""https://developer.github.com/v3/#rate-limiting""
+}",1405400739,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Are we being hit by github's ratelimiting? (I don't know if we have a special exemption or anything...)
+
+Via eval.php:
+
+> $httpOptions = array( 'followRedirects' => false );
+
+> $httpOptions['proxy'] = $wgExtDistProxy;
+
+> $req = MWHttpRequest::factory(""https://api.github.com/rate_limit"", $httpOptions);
+
+> var_dump($req->getContent());
+string(177) ""{""resources"":{""core"":{""limit"":60,""remaining"":0,""reset"":1405398906},""search"":{""limit"":10,""remaining"":10,""reset"":1405396979}},""rate"":{""limit"":60,""remaining"":0,""reset"":1405398906}}""",1405397710,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,Seems to be somewhat random. Versions appearing and disappearing regardless of their branches existing.,1405372877,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"These extensions shows an empty dropdown here and seem to have RELX_XX branches:
+* https://www.mediawiki.org/wiki/Special:ExtensionDistributor/LoopFunctions
+* https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FLoopFunctions
+
+* https://www.mediawiki.org/wiki/Special:ExtensionDistributor/MediaFunctions
+* https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FMediaFunctions
+
+* https://www.mediawiki.org/wiki/Special:ExtensionDistributor/AbuseFilter
+* https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FInterwiki
+
+And I guess some more...",1405342596,PHID-USER-e7a5lnjpgncgdxknmdxb,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"I confirm this, while the extensions has RELX_XX branches: https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FNonlinear",1405342016,PHID-USER-e7a5lnjpgncgdxknmdxb,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Created attachment 15932
+Example extension Nonlinear
+
+https://www.mediawiki.org/wiki/Special:ExtensionDistributor/Nonlinear
+
+This extension actually doesn't work for me.
+
+**Attached**: {F13612}",1405341875,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Works here also, couldn't find any extension where ExtensionDistributor fails. Btw, is that URL in this bugs' settings really needed?",1405340765,PHID-USER-e7a5lnjpgncgdxknmdxb,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Hmm, now it works for me, too :/",1405340412,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"(In reply to Florian from comment #11)
+> One more example:
+> https://www.mediawiki.org/wiki/Special:ExtensionDistributor/
+> ExtensionDistributor
+> 
+> (It's ExtensionDistributor itself)
+
+Works for me at this moment",1405339399,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"One more example:
+https://www.mediawiki.org/wiki/Special:ExtensionDistributor/ExtensionDistributor
+
+(It's ExtensionDistributor itself)
+
+And there are some RELX_XX branches:
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/ExtensionDistributor,branches",1405322657,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Oh, yeah, i thought there was one, will create it, thanks :) i will look into some extensions i remember tomorrow, when i'm at pc again.",1405026386,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"(In reply to Florian from comment #8)
+> One example that doesn't work:
+> 
+> https://www.mediawiki.org/wiki/Special:ExtensionDistributor/GoogleLogin
+
+That one has an explanation. It doesn't have any REL1_XX branch [1]
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FGoogleLogin.git
+
+ED shouldn't be listed in the extension's page",1405025635,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"One example that doesn't work:
+
+https://www.mediawiki.org/wiki/Special:ExtensionDistributor/GoogleLogin",1405025304,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"I've checked all extensions linked in comments from this bug and all of them list 1.23 and older in their dropdown. It's still an issue?
+
+Note that some extensions weren't properly branched for 1.23, downloading an old (and probably incompatible) version, but that's bug 64157",1405024985,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Hmm, now i have now list of versions, too, on some Extensions :/",1404384584,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Created attachment 15498
+branches exist
+
+Hmm, anything i do false :?
+
+Now i have tested with FF, Chrome and Android/HTC Stock Browser
+
+**Attached**: {F13611}",1401288938,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Problem does also exist for downloading Oversight (is that extension even downloadable?), see https://www.mediawiki.org/wiki/Special:ExtensionDistributor/Oversight. Status can be changed to CONFIRMED.",1401286059,PHID-USER-e7a5lnjpgncgdxknmdxb,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"https://www.mediawiki.org/wiki/Special:ExtensionDistributor/MaintenanceShell (original report) does have empty dropdown for me, how common is this? How are they picked?",1401283956,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"I see 1.22 and master for CirrusSearch. Giving me https://codeload.github.com/wikimedia/mediawiki-extensions-CirrusSearch/legacy.tar.gz/REL1_22 to download
+
+There is no 1.23, but that isn't setup in CommonSettings.php",1401283327,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"-> https://www.mediawiki.org/wiki/Special:ExtensionDistributor/CirrusSearch
+I see a master and 1.22 branch :/
+
+-> https://www.mediawiki.org/wiki/Special:ExtensionDistributor?extdist_extension=AbuseFilter
+Abuse Filter all branches up from 1.19 :) Tested with Firefox 17.0.1 ESR and Google Chrome 34.0.1847.116m",1401283273,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,"Error: Unknown dependency: mediawiki.skinning.content.parsoid Error {stack: (...), message: ""Unknown dependency: mediawiki.skinning.content.parsoid""} load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:160
+
+logload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:160
+handlePendingload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:169
+runScriptload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:170
+checkCssHandlesload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:171
+(anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:171
+fireload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:44
+self.fireWithload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:46
+self.fireload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:46
+addEmbeddedCSSload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:166
+(anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:165
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1401211500,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-zvmwksybywvrfm2uti2u,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,Should now be fixed.,1401219438,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,"Change 135606 merged by jenkins-bot:
+Enable mediawiki.skinning.content.parsoid on Mobile target too
+
+https://gerrit.wikimedia.org/r/135606",1401217520,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,"Change 135606 had a related patch set uploaded by Jforrester:
+Enable mediawiki.skinning.content.parsoid on Mobile target too
+
+https://gerrit.wikimedia.org/r/135606",1401216207,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,Aha. I'm a complete fool; my apologies. Fix inbound.,1401216189,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,See also bug 64607,1401212465,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,It's not invalid. This is on beta labs which mirrors production. It sounds like Parsoid is declaring a module that has not been set to the mobile target. We had this exact issue before with another RL module.,1401212427,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,mediawiki.skinning.content.parsoid is provided by MW-core as of Wednesday – see gerrit 130770.,1401212212,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,Sounds like you just didn't install the Parsoid *extension* when it became required (used to be optional).,1401211947,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","No manual repro or network trace so far, this is for tracking
+
+VE loses user token: 
+https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/9/testReport/(root)/VisualEditor%20multi-edit%20workflow/Make_multiple_edits_to_the_same_article/
+
+VE logs user out:
+https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/12/testReport/junit/(root)/Switching%20between%20wikitext%20and%20Visual%20Editor%20modes/Switch_editing_modes_via_toolbar/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65710
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66076
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67171",1400887020,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_description,resolved
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures",Handled this by better managing test users. There was a rogue test logging out. ,1423259488,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Given this is a duplicate of non-VE bugs, it's clearly a MediaWiki issue that the Editing team haven't been able to track down. :-( Moving.",1404153510,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures",*** Bug 62583 has been marked as a duplicate of this bug. ***,1404138675,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Created attachment 15686
+Something went wrong... session no longer valid
+
+Slightly different manifestation of error message for this issue.
+
+**Attached**: {F13886}",1403208502,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures",also still getting this in automated tests launched from WMF Jenkins (not Cloudbees) for example https://saucelabs.com/tests/5c4697a6618543708b7a59382e9813f6,1402341824,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Created attachment 15608
+Screenshot
+
+**Attached**: {F13885}",1402338060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Created attachment 15607
+Screenshot
+
+I reproduced this issue, after clicking on Switch to edit source and then again coming back to VE,I tried to save the page from VE.
+It showed an error: there might be an edit conflict in the save dialog and then I got logged out
+
+See the screenshots attached
+
+**Attached**: {F13882}",1402338036,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures",Now seen in Chrome also https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/535/,1401466027,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","I should have said: 
+
+Note: a close look at the screencast of the logout instance shows the logout happens instantly upon clicking Edit source for logged-in user while the user is in VisualEditor.",1400888911,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Note: a close look at the screencast of the logout instance shows the logout happens instantly upon clicking Edit source for logged-in user.  
+
+In attempting to recreate the problem I encountered Bug 65710.  
+
+Since the beta warning is controlled by a cookie, these issues may be related.",1400887564,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>References list
+3.Observe the animation that happens when you open it.
+
+Observed Result:
+In both Chrome and Firefox , there is a bit of irregular animation when you try to open the reference list for the first time
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400885220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-emgwmnazcg2mnjqwuy34,task_description,resolved
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,Verified the fix in production (en.wiki),1403300744,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,Verified the fix in test2 running wmf9,1402697182,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,"Change 138114 merged by jenkins-bot:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,"Change 138114 had a related patch set uploaded by Jforrester:
+[BREAKING CHANGE] Window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402353853,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,"It's simultaneously opening (animating from 0.5 scaling factor to 1.0) and animating from normal size to small size, that's why it looks weird.",1401303106,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: PageTriage UI appears after save,"PageTriage shown after saving edit.
+
+I've seen this a few times, but this is the first time I've been in a position to take a screen shot.  
+
+After saving an edit in VE, the PageTriage pager UI exists on the saved page.  See screen shot.
+
+Note: the page is still viable at http://en.wikipedia.beta.wmflabs.org/wiki/Special:NewPagesFeed
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13852}",1400884440,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-cgd7gfh5limbmfzyuqbj,task_description,resolved
+VisualEditor: PageTriage UI appears after save,"Change 135587 merged by jenkins-bot:
+Follow-up I7b49a6dd0: Fix page curation bar reappearing after VE closes
+
+https://gerrit.wikimedia.org/r/135587",1401319645,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cgd7gfh5limbmfzyuqbj,task_subcomment,NA
+VisualEditor: PageTriage UI appears after save,"Change 135587 had a related patch set uploaded by Alex Monk:
+Fix page curation bar appearing after VE closes for some users
+
+https://gerrit.wikimedia.org/r/135587",1401209848,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cgd7gfh5limbmfzyuqbj,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Insert>Reference
+3.Type something in the text box
+4.Click on ""Insert Reference""
+5.Again re-open that reference
+6.Delete the content inside the text field
+
+Observed Result:
+issue 1: The ""Use an existing reference"" button remains enabled when user has entered something in the textbox (step 3), it should be disabled as soon as user enters types something in the field.
+
+issue 2:After clicking on ""insert reference"" , when user reopens that reference, there is no ""Use an existing reference"" button in the reference dialog box (step5), the button should appear there but as ""Disabled""
+
+Once user deletes the content inside the text field (step 6), the button should again re-anabled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400868360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_description,resolved
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it",Verified the fix in production(en.wiki),1403299959,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it",Verified the fix in test2 running wmf 9,1402705124,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it",Verified the fix in Betalabs,1402348021,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Change 136599 merged by jenkins-bot:
+MWReferenceDialog: Allow swapping of existing references for others
+
+https://gerrit.wikimedia.org/r/136599",1402102521,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Change 136599 had a related patch set uploaded by Alex Monk:
+Allow swapping of existing references for others.
+
+https://gerrit.wikimedia.org/r/136599",1401564246,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","(In reply to ryasmeen from comment #4)
+> When I will delete the content of that already added reference, it should
+> re-enable that button.
+
+This bit is being dealt with already in Gerrit change 136505",1401562796,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","The issue 2 stated above in the bug report is still there:
+
+When I reopen an already added reference , there should be ""Use an existing reference"" button in that dialog but disabled , right now the button is not there at all.
+
+When I will delete the content of that already added reference, it should re-enable that button.",1401499329,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Change 136443 merged by jenkins-bot:
+""Use an existing reference"" in the reference dialog should be disabled when there is content
+
+https://gerrit.wikimedia.org/r/136443",1401488795,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Change 136443 had a related patch set uploaded by Alex Monk:
+""Use an existing reference"" in the reference dialog should be disabled when there is content
+
+https://gerrit.wikimedia.org/r/136443",1401480442,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","James says it should disable when the surface is not empty and re-enable when empty, and also appear for existing references.",1401303220,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a left aligned thumbnail and Frame image, unchecking the wrapping option moves it to the right side of the page","Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image
+3.Make it Thumbnail or Frame
+4.Make it left aligned
+5.Now uncheck the wrap option 
+6.Click on ""Apply Changes""
+
+Observed Result:
+
+The image gets moved to the right side of the page
+
+
+Environment : Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400715360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gcxpqprlky5p3csmakeu,task_description,resolved
+"VisualEditor: [Regression wmf6] For a left aligned thumbnail and Frame image, unchecking the wrapping option moves it to the right side of the page",Verified the fix in production,1402086527,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gcxpqprlky5p3csmakeu,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a left aligned thumbnail and Frame image, unchecking the wrapping option moves it to the right side of the page",Verified the fix in test2,1401496888,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gcxpqprlky5p3csmakeu,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a left aligned thumbnail and Frame image, unchecking the wrapping option moves it to the right side of the page",Verified the fix on Betalabs,1401212247,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gcxpqprlky5p3csmakeu,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Steps to reproduce:
+
+1.Open a oage with VE
+2.Insert an image
+3.Make it right aligned and framless
+4.Hover over it
+
+Observed Result:
+It throws the following error:
+Uncaught TypeError: Cannot read property 'getSurface' of null
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400714160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-goldr7i773st4wqcjxev,task_description,resolved
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Change 134363 merged by jenkins-bot:
+[BREAKING CHANGE] Merge ProtectedNode into FocusableNode
+
+https://gerrit.wikimedia.org/r/134363",1402442351,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,Verified the fix in production.,1402091164,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,Verified the fix in Betalabs and test 2,1400808287,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,Still fixed.,1400800772,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Change 134363 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Merge protected node into focusable node
+
+https://gerrit.wikimedia.org/r/134363",1400797623,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,Fixed and backport going out in SWAT.,1400795905,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Change 134363 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Merge protected node into focusable node
+
+https://gerrit.wikimedia.org/r/134363",1400770552,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Created attachment 15455
+Screenshot
+
+**Attached**: {F13647}",1400738209,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"It also happens for the following case:
+
+1. Change alignment of any image
+2. Delete the image
+3. Observe that, the phantom of the image is still there after deleting the image
+4.Now hover over the phantom
+
+Observed Result:
+As soon as you delete the image the error: Cannot read property 'getSurface' of null appears, also everytime you hover over the phantom , you will get this same error.
+
+See the screenshot attached",1400738183,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image of any type
+3.Now uncheck the wrapping option
+4.Click on ""Apply Changes""
+5.Open the media settings dialog box again
+
+Observed Result:
+The wrap option is getting checked again
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400713740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_description,resolved
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,Verified the fix in production,1402088566,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,Verified the fix in test2,1401397894,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,Verified the fix in Betalabs,1401318840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,"Provisionally, fixed in gerrit 135699.",1401318622,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,This should be resolved now following the change of default alignment pt II,1401317043,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,This is still happening on Betalabs,1401224236,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,This should be resolved now following the change of default alignment.,1401213663,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size","screenshot
+
+Steps to reproduce:
+
+1.Go to this page: http://en.wikipedia.beta.wmflabs.org/wiki/21stmaychrome?veaction=edit
+
+2.Open the Media settings>Advanced Settings dialog for the first image
+
+3.Click on Custom tab for the image
+
+4.Once you get the size values are invalid, click on default tab
+
+Observed Result:
+
+The fields for default size gets empty , switching back to custom also shows empty fields and the ""MAke full size"" button gets disabled
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13636}",1400713080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zjnwbcq6vujt355a3rpo,task_description,resolved
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size",Verified the fix in Betalabs,1401314050,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zjnwbcq6vujt355a3rpo,task_subcomment,NA
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size","Change 135832 merged by jenkins-bot:
+Decode URL encoding in resource attriute for images
+
+https://gerrit.wikimedia.org/r/135832",1401311084,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zjnwbcq6vujt355a3rpo,task_subcomment,NA
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size","Change 135832 had a related patch set uploaded by Catrope:
+Decode URL encoding in resource attriute for images
+
+https://gerrit.wikimedia.org/r/135832",1401305034,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zjnwbcq6vujt355a3rpo,task_subcomment,NA
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size",This is because the image in question is the feared Image With A Question Mark of Doom. Moriel is looking at it.,1401303580,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zjnwbcq6vujt355a3rpo,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it frameless/basic
+4.Change the alignment to Left
+5.Now try to change the alignment to Right
+6.Click on ""Apply changes""
+
+Observed Result:
+The alignment is still set as left , not moving it to Right
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400698800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d77ihdd6l74pyicsh6os,task_description,resolved
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Verified the fix in production,1402087318,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Verified the fix in test2,1401495524,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Verified the fix in Betalabs,1401315459,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,"Change 135167 merged by jenkins-bot:
+Followup dd1c7f7fd7: fix LESSification errors in Parsoid styles
+
+https://gerrit.wikimedia.org/r/135167",1400901128,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,"Change 135167 had a related patch set uploaded by Catrope:
+Followup dd1c7f7fd7: fix LESSification errors in Parsoid styles
+
+https://gerrit.wikimedia.org/r/135167",1400900653,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,This is happening for all image types now.Not just Frameless and Basic,1400891735,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Reopening since I can still reproduce this issue for both the image types in Betalabs.,1400706744,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Marking as such.,1400705022,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,The latest fix (https://gerrit.wikimedia.org/r/#/c/134660/) should fix this too (tested on master),1400703639,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Clean up the mess I made in https://gerrit.wikimedia.org/r/134546
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400638440,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-scuorfdmgzjdphugjbmh,task_description,resolved
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Change 134621 merged by jenkins-bot:
+Clean up interaction with confirmation dialog
+
+https://gerrit.wikimedia.org/r/134621",1401494095,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-scuorfdmgzjdphugjbmh,task_subcomment,NA
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Change 134620 merged by jenkins-bot:
+[BREAKING CHANGE] Emit a single event from confirmation dialog
+
+https://gerrit.wikimedia.org/r/134620",1401492000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-scuorfdmgzjdphugjbmh,task_subcomment,NA
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Change 134621 had a related patch set uploaded by Alex Monk:
+Clean up interaction with confirmation dialog
+
+https://gerrit.wikimedia.org/r/134621",1400686854,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-scuorfdmgzjdphugjbmh,task_subcomment,NA
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Change 134620 had a related patch set uploaded by Alex Monk:
+Emit a single 'done' event from confirmation dialog instead of 'ok' and 'cancel'
+
+https://gerrit.wikimedia.org/r/134620",1400686764,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-scuorfdmgzjdphugjbmh,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Screenshot
+
+Steps to reproduce:
+
+1. Insert a frameless-left aligned image 
+2.Save the page
+3.Reopen the page
+4.Open the Media Settings dialog for the image
+
+
+Observed Result:
+There is no text field for the caption,Cannot close the Media Settings dialog box.
+The following error appears in the console:
+TypeError: node.getCaptionNode is not a function
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13542}",1400632140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_description,resolved
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears",Verified the fix in production,1401392205,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears",Verified the fix in test2,1400809157,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears",Verified the fix in Betalabs,1400700825,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","(In reply to Roan Kattouw from comment #4)
+> Well, you can most certainly trust node.getType() to tell you if calling
+> node.getCaptionNode() will cause it to explode or not, and you apparently
+> can't trust imgModel.getImageNodeType() in this case ;)
+Yes, fallbacks should be included. I think the current (merged) commit dealt with that, I hope no more bugs will come with it, but I'll go over the code to verify.
+
+> Yup, that sounds reasonable. However, we'd also have to define what happens
+> when we inspect a node whose type appears to be ""wrong""; we probably
+> shouldn't change its type if the user didn't change any of the flags. OTOH,
+> this just shouldn't happen.
+
+That would be a problem, though -- how would we know that the type is wrong? It's not like the user consciously chooses inline vs block. The inline/block type is defined by seemingly arbitrary flags. They're not completely arbitrary, which is good, but they're also not entirely intuitive either. The only way to know for sure is through the tests in the getImageNodeType. It just has to be verified to follow the right conditions.
+
+In this case, I had a typo in there, and from my tests so far this *should* be true for all the cases I tested, but I am slightly concerned we may be missing things with wikitext, or that if new types are added we will have to adjust as well.",1400649158,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Change 134554 merged by jenkins-bot:
+Fix MWImageModel's getImageNodeType()
+
+https://gerrit.wikimedia.org/r/134554",1400645312,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Change 134554 had a related patch set uploaded by Mooeypoo:
+Fix MWImageModel's getImageNodeType()
+
+https://gerrit.wikimedia.org/r/134554",1400644951,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","(In reply to Moriel Schottlender from comment #3)
+> Most times, we can't trust the node.getType() because changes in the model
+> changes the node's type -- that's what the model's test was for.
+> 
+Well, you can most certainly trust node.getType() to tell you if calling node.getCaptionNode() will cause it to explode or not, and you apparently can't trust imgModel.getImageNodeType() in this case ;)
+
+> It should, however, not lie or make mistakes. This is going to be somewhat
+> complex, since wikitext's way of transforming between inline/block can be
+> extremely arbitrary-looking.
+> 
+Yeah, it should be improved, but if it makes mistakes the consequences shouldn't be /this/ bad.
+
+> One more thing that we could do, however, is use node.getType() whenever
+> that *can* be trusted. This means that on loading the node (like in this
+> bug) the node's type can be used, and same with after inserting a new node.
+> 
+Yes, exactly.
+
+> In the other cases, though (like checking whether we're going to change a
+> node type or just change the attributes) the node.getType() won't help us,
+> we'll have to use a custom test inside the model to check.
+Yup, that sounds reasonable. However, we'd also have to define what happens when we inspect a node whose type appears to be ""wrong""; we probably shouldn't change its type if the user didn't change any of the flags. OTOH, this just shouldn't happen.",1400643505,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Most times, we can't trust the node.getType() because changes in the model changes the node's type -- that's what the model's test was for.
+
+It should, however, not lie or make mistakes. This is going to be somewhat complex, since wikitext's way of transforming between inline/block can be extremely arbitrary-looking.
+
+One more thing that we could do, however, is use node.getType() whenever that *can* be trusted. This means that on loading the node (like in this bug) the node's type can be used, and same with after inserting a new node.
+
+In the other cases, though (like checking whether we're going to change a node type or just change the attributes) the node.getType() won't help us, we'll have to use a custom test inside the model to check.",1400643101,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","This happens because imgModel.getImageNodeType() returns 'mwBlockImage', but the actual node is an inline image.
+
+So 1) we shouldn't base decisions on what to do with the node object on the image model's opinion of what class the node should be, 2) that opinion should be used in very very few places, everywhere else we should be using node.getType() and 3) the image model's opinion should not be wrong :)",1400639573,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Example page 1: The first image on:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_%28WMF%29&veaction=edit
+
+Example Page 2: The first image on:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=20thmaychrome&veaction=edit",1400632439,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Steps to reproduce:
+
+1.Open a page with VE 
+2.Insert an image 
+3.Change the Image type to ""Frame""
+4.Click on ""Apply changes""
+5.Reopen the media settings dialog
+
+Observed Result:
+Though the image is on the right , the alignment is set to Left on the Media Settings dialog, and if you click on ""Apply Changes"" button now, it will move the image to left
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400626920,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x74esizqbmiiw7nhiogh,task_description,resolved
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",Verified the fix in en.wiki running wmf 8,1402687364,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",Verified the fix in test2,1402342746,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",Verified the fix in Betalabs,1401928680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 136971 merged by jenkins-bot:
+Adjust default alignment when switching from inline to block
+
+https://gerrit.wikimedia.org/r/136971",1401921428,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 136971 had a related patch set uploaded by Mooeypoo:
+Adjust default alignment when switching from inline to block
+
+https://gerrit.wikimedia.org/r/136971",1401769554,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","This issue still happening but the behavior got slightly changed.Previouslt after changing the alignment of any image types to ""Left"" and then reopening the Media Settings dialog was setting the alignment as ""Right"" , even though it was still on the left.Now the same issue happens but you need to save the page first after changing the alignment to left and then reopen the media settings dialog to see it.
+
+So the new steps to reproduce is:
+
+1.Insert any type of image
+2.Change the alignment to left
+3.Click on ""Apply Changes""
+4.Click on ""Save Page""
+5.Reopen the page
+6.Reopen the Media Settings dialog>Advanced Settings
+
+Observed Result:
+The alignment tab is set to ""Right""",1401398771,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 135699 merged by jenkins-bot:
+Another default alignment fix to MWImageModel
+
+https://gerrit.wikimedia.org/r/135699",1401315123,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 135699 had a related patch set uploaded by Mooeypoo:
+Another default alignment fix to MWImageModel
+
+https://gerrit.wikimedia.org/r/135699",1401311231,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",This is happening for all image types now in Betalabs.,1401225328,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Yes, that's intended. This happens to images that have default alignment; default in a block image is opposite the text direction (""right"" in ltr) and default for inline images, which is what the basic change does, is with text direction (""left"" in ltr).
+
+This is intended.",1400705854,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Right now, when you add an image and make it basic and select Right alignment, it moves it to the left and sets alignment as ""Left"".",1400705274,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 134660 merged by jenkins-bot:
+Don't update image model twice
+
+https://gerrit.wikimedia.org/r/134660",1400700237,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 134660 had a related patch set uploaded by Mooeypoo:
+Don't update image model twice
+
+https://gerrit.wikimedia.org/r/134660",1400697863,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",This issue is still occurring for image type Basic.,1400696553,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","The issue of default alignment between inline and block is more complex than I initially thought. I made an additional fix to this behavior in this commit https://gerrit.wikimedia.org/r/#/c/134554/ (which is merged now)
+
+This should fix the current bug as well (it did on my tests locally, but please verify)
+
+I hope no more default-alignment problems pop up.",1400652437,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",The same issue appears when you change the Image type to Basic too,1400628181,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make an edit
+3.Click on ""Switch to source editing ""
+4.Click on ""No, cancel""
+5.Now click on the ""Cancel"" button of the editor 
+6.Click on ""Continue Editing""
+7.Now again go to """"Switch to source editing ""
+8.This time click on ""Yes, switch""
+
+Observed Result:
+It does not switch to edit source mode and throws the following errors in the console:
+
+
+Uncaught TypeError: Cannot read property 'css' of null and 
+Uncaught TypeError: Cannot read property 'each' of null 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13495}",1400622660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-42zzbjl2eh4mv5xecel6,task_description,resolved
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,Verified the fix in production.,1401392334,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,Verified the fix on test 2,1400808693,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,Verified the fix in Betalabs,1400701590,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"Change 134546 merged by jenkins-bot:
+Unbind confirm dialog handlers after either of the events fires once
+
+https://gerrit.wikimedia.org/r/134546",1400680518,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"Change 134546 had a related patch set uploaded by Catrope:
+Unbind confirm dialog handlers after either of the events fires once
+
+https://gerrit.wikimedia.org/r/134546",1400638427,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"(In reply to Roan Kattouw from comment #1)
+> Holy crap this is an obscure bug. Steps 3 and 4 (switching to source mode
+> the first time) can be skipped, but other than that every step is necessary.
+> 
+As Rummana points out, the second error (with 'each') does not occur if you skip those steps, so there's something else going on too. There's some code in ViewPageTarget that gets run after this.$checkboxes has been cleared.
+
+On second inspection, there's a lot more going on. For instance, the 'ok' handler executes twice, and so we attempt to serialize twice.",1400638052,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"Holy crap this is an obscure bug. Steps 3 and 4 (switching to source mode the first time) can be skipped, but other than that every step is necessary.
+
+This happens because the switch to source mode button and the cancel button share the same instance of the confirmation dialog. When you click OK in the source mode one, the cancel button code is still listening to the 'ok' event; we need to disconnect that on cancel.
+
+Perhaps it would be nicer if these two were combined into one event so we could use .once() and not have to unbind explicitly.",1400625140,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,"Bug 50047 and bug 51918 have regressed for Firefox – possibly as a result of Ed's changes to how the buttons work? Yay for Firefox and its attitude to tab indexes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66824",1400619540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lgy5g6voka2ep73yf275,task_description,resolved
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,*** Bug 67153 has been marked as a duplicate of this bug. ***,1404848147,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,Well that's at least a workaround. I wonder if this might be an upstream bug...,1404152488,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,"Change 143055 merged by jenkins-bot:
+Set tabindex on button <div> instead of <a>
+
+https://gerrit.wikimedia.org/r/143055",1404152364,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,"Change 143055 had a related patch set uploaded by Alex Monk:
+Set tabindex on button <div> instead of <a>
+
+https://gerrit.wikimedia.org/r/143055",1404148906,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,"So adding this.reviewButton.$element.attr( 'tabindex', '0' ).find( 'a' ).removeAttr( 'tabindex' ); fixed this... Wtf firefox?",1404147725,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,Looks like the same issue as bug 66824,1404147095,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the link inspector : insert [http://yahoo.com]
+3.Apply the link
+4.Save the page
+
+Observed Result:
+The link appears inside VE with single brackets around it: [http://yahoo.com]
+And when you save the page, the unicode for the ending single bracket appears at the end of the link as a part of that link:[http://yahoo.com&#x5D;
+
+Expected Result:
+The link inspector should say to user that it is an invalid external link format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13473}",1400614080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vdj2elhgawonhfvz6sns,task_description,resolved
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"Change 139128 merged by jenkins-bot:
+Wrap external URL protocols regex in brackets.
+
+https://gerrit.wikimedia.org/r/139128",1402592717,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,I don't think so. I think things including the wgUrlProtocols regex should be dealing with this issue themselves.,1402590530,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,Do we need to upstream a fix for wgUrlProtocols?,1402590080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"Change 139128 had a related patch set uploaded by Alex Monk:
+Wrap external URL protocols regex in brackets.
+
+https://gerrit.wikimedia.org/r/139128",1402589216,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"Currently, the regex looks something like this (based on wgUrlProtocols):
+
+/^bitcoin\:|ftp\:\/\/|ftps\:\/\/|geo\:|git\:\/\/|gopher\:\/\/|http\:\/\/|https\:\/\/|irc\:\/\/|ircs\:\/\/|magnet\:|mailto\:|mms\:\/\/|news\:|nntp\:\/\/|redis\:\/\/|sftp\:\/\/|sip\:|sips\:|sms\:|ssh\:\/\/|svn\:\/\/|tel\:|telnet\:\/\/|urn\:|worldwind\:\/\/|xmpp\:|\/\//
+
+Notice the '^' is only against 'bitcoin' and not any other protocol? Yeah I think we need to wrap everything after the '^' in brackets.",1402589191,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,Is our regex not anchored to the start of the string somehow?,1402549443,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"
+note that the wikitext for the saved string reads: 
+
+&#x5Dhttp://yahoo.com&#x5D;",1400615575,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Language
+3.Now click on ""Find Language"" button
+
+Observed Result:
+
+The language selector dialog box takes a long time to load, approx. 15 secs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66124",1400540520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2riepmcawlf54gdgu2o,task_description,resolved
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,Verified the fix in production (en.wiki),1403300505,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,Verified the fix in test2 running wmf 9,1402704938,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,Verified the fix in Betalabs,1402354271,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Change 137741 merged by jenkins-bot:
+GroupElement: Improve performance by avoiding .add() overhead
+
+https://gerrit.wikimedia.org/r/137741",1402349469,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Change 137736 merged by jenkins-bot:
+Use this.$() in LanguageResultWidget#highlightQuery
+
+https://gerrit.wikimedia.org/r/137736",1402041593,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"These two patches get it down to 780ms on my computer. This breaks down in about 520ms for opening the dialog (including constructing all of the language entries), and 260ms for displaying the ""search result"" for an empty search bar. The latter is repeated every time you empty the search bar (press backspace when one character is left), which is noticeably laggy. That mostly has to do with the search query highlighting code (that's about 200ms of it), which needs to be optimized further. The dialog opening is also a bit slower than I'd like, but at least isn't as critical as responding quickly when the user presses backspace.
+
+To be fair, without these patches, it's 520ms for opening the dialog (unchanged), and 14 seconds to display an empty search result (12 seconds for adding results, 2 seconds for highlighting), so this is already a pretty good improvement :)",1402008214,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Change 137741 had a related patch set uploaded by Catrope:
+Fix GroupElement performance
+
+https://gerrit.wikimedia.org/r/137741",1401997608,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Change 137736 had a related patch set uploaded by Catrope:
+Use this.$() in LanguageResultWidget#highlightQuery
+
+https://gerrit.wikimedia.org/r/137736",1401995364,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"(Additional information from the duplicate bug)
+
+The slowness also means the user can click somewhere on the screen to close the language inspector while the language list loads; it seems to allow the user to choose a language, but since the inspector is already closed, the chosen language isn't updated properly.",1401898887,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,*** Bug 66124 has been marked as a duplicate of this bug. ***,1401898213,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"In Firefox, it is comparatively faster than Chrome",1400540731,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Category autocompletion is broken in RTL wikis,"a screenshot with the problem
+
+To reproduce:
+
+1. Edit an article in the Hebrew Wikipedia using VE.
+2. Go to the categories dialog.
+3. Start typing a category name.
+
+Expected: autocompletion list appears under the input box.
+Actual: autocompletion list appears to the side of the input box.
+
+See screenshot.
+
+This is similar to Bug 51490.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13994}",1400505240,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dnopciwdieirbov75q2y,task_description,resolved
+VisualEditor: Category autocompletion is broken in RTL wikis,"Change 138041 merged by jenkins-bot:
+Correct TextInputMenuWidget position for RTL
+
+https://gerrit.wikimedia.org/r/138041",1402098125,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dnopciwdieirbov75q2y,task_subcomment,NA
+VisualEditor: Category autocompletion is broken in RTL wikis,"Change 138041 had a related patch set uploaded by Mooeypoo:
+[wip] Correct TextInputMenuWidget position for RTL
+
+https://gerrit.wikimedia.org/r/138041",1402089868,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dnopciwdieirbov75q2y,task_subcomment,NA
+VisualEditor: Save dialog's request for checkboxes should respect the uselang param,"There is content in pt-BR after setting ""uselang=en""
+
+See the screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13936}",1400420160,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ftg6xmbgjlpqhszufc2t,task_description,resolved
+VisualEditor: Save dialog's request for checkboxes should respect the uselang param,"Change 138407 merged by jenkins-bot:
+Send language when making API requests
+
+https://gerrit.wikimedia.org/r/138407",1402347137,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftg6xmbgjlpqhszufc2t,task_subcomment,NA
+VisualEditor: Save dialog's request for checkboxes should respect the uselang param,"Change 138407 had a related patch set uploaded by Alex Monk:
+Send language when making API requests
+
+https://gerrit.wikimedia.org/r/138407",1402343419,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftg6xmbgjlpqhszufc2t,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,"ve.ce.Surface uses $.browser to do paste special casing; replace or remove this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400259180,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pemezhinhwcmsjmxrgcv,task_description,resolved
+VisualEditor: Remove use of jQuery.browser,"Change 136036 merged by jenkins-bot:
+Remove last jQuery.browser uses with temporary ve.isMsie hack
+
+https://gerrit.wikimedia.org/r/136036",1401390951,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,Thanks Ed!,1401390896,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,"Change 136036 had a related patch set uploaded by Krinkle:
+Remove last jQuery.browser uses with temporary ve.isMsie hack
+
+https://gerrit.wikimedia.org/r/136036",1401380354,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,Still one use in ve.ce.Surface.,1401380304,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,"Change 132431 merged by jenkins-bot:
+Remove IE check (and possible compatibility) from beforepaste/paste event switch
+
+https://gerrit.wikimedia.org/r/132431",1400895485,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,"Change 132431 had a related patch set uploaded by Jforrester:
+[WIP] Remove IE check from beforepaste/paste event switch
+
+https://gerrit.wikimedia.org/r/132431",1400259251,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+OOjs UI: Need a way to add a non-functional label to the top of a popupToolGroup (within the popup),"See design mock-up at https://trello.com/c/xCo6uLAZ/9-5-references-dropdown-from-toolbar-styling.
+
+Right now, I can give a popupToolGroup a label by using the 'label' param in a toolbarGroup definition:
+{
+    'label': 'Cite',
+    'type': 'list',
+    'icon': 'reference',
+    'title': OO.ui.deferMsg( 'visualeditor-toolbar-cite-label' ),
+    'include': [ { 'group': 'cite' } ]
+}
+
+However, this puts the label above the popup (in the popupToolGroup-handle) rather than within the popup itself (as needed by the design linked to above).
+
+I can imagine two different ways of providing this functionality:
+
+1. Add a new type of param for toolbarGroups called something like 'inner-label'
+
+2. Allow creating non-functional labels from the on-wiki group definition, for example:
+[
+    { ""label"": ""cite"" },
+    { ""name"": ""web"", ""icon"": ""ref-cite-web"", ""template"": ""Cite web"" },
+    { ""name"": ""book"", ""icon"": ""ref-cite-book"", ""template"": ""Cite book"" },
+    { ""name"": ""news"", ""icon"": ""ref-cite-news"", ""template"": ""Cite news"" },
+    { ""name"": ""journal"", ""icon"": ""ref-cite-journal"", ""template"": ""Cite journal"" }
+]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400194680,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-lpehn2gbooedlcmnbnt4,task_description,resolved
+OOjs UI: Need a way to add a non-functional label to the top of a popupToolGroup (within the popup),Fixed by https://gerrit.wikimedia.org/r/#/c/134237/,1402081686,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-lpehn2gbooedlcmnbnt4,task_subcomment,NA
+OOjs UI: Need a way to add a non-functional label to the top of a popupToolGroup (within the popup),I would recommend option 1.,1400274032,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-lpehn2gbooedlcmnbnt4,task_subcomment,NA
+OOjs UI: Need a way to add a non-functional label to the top of a popupToolGroup (within the popup),After discussing with Trevor we decided the best way to implement this would be to have a parameter like 'label-position' which controls where the label appears.,1400273880,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-lpehn2gbooedlcmnbnt4,task_subcomment,NA
+VisualEditor: Transclusion content blocks don't auto-expand in Firefox,"Probably the same issue as we had for parameter fields?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400178360,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cxvk42p4teyvew3duhd3,task_description,duplicate
+VisualEditor: Blue link / red link logic should descend into links inside generated content nodes,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400178120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zfbsov36z6srqhbwgabt,task_description,resolved
+VisualEditor: Blue link / red link logic should descend into links inside generated content nodes,"Bah.
+
+*** This bug has been marked as a duplicate of bug 65353 ***",1400178184,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zfbsov36z6srqhbwgabt,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"Redlinks are displayed as blue links in templates inside the VisualEditor
+
+
+https://en.wikipedia.org/wiki/Javier_Payo?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400177400,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-4sbnoqmt6akkxouhu25v,task_description,resolved
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"(In reply to Alex Monk from comment #7)
+> Well, it was you who changed this bug from being about just templates to
+> being about ""generated content nodes (e.g. templates)""... We can just make
+> it about templates only again if you want.
+
+Created that as bug 71900.",1412891280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"Well, it was you who changed this bug from being about just templates to being about ""generated content nodes (e.g. templates)""... We can just make it about templates only again if you want.",1412791547,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"(In reply to Alex Monk from comment #5)
+> Transclusion nodes are not the only generated content nodes
+
+They are, however, almost exclusively the GCNs with wikitext links in them. Do we actually care about <easytimeline> blocks?",1412791246,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,Transclusion nodes are not the only generated content nodes,1412787503,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"Change 165240 merged by jenkins-bot:
+Apply link styling logic to transclusion nodes
+
+https://gerrit.wikimedia.org/r/165240",1412778604,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"Change 165240 had a related patch set uploaded by Alex Monk:
+Apply link styling logic to transclusion nodes
+
+https://gerrit.wikimedia.org/r/165240",1412712151,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"We used to parse template content with action=parse from the PHP parser which naturally contained <a class=""new"">.
+
+Nowadays we use Parsoid for the generated fragments as well, but this meant we lost the natural classes MediaWiki provided.
+
+The mw.LinkCache logic should extend to the nodes inside generated content.
+
+I think right now this isn't done because we use the same DOM for both the DM and the CE of generated content nodes, but, just as we do for practically everything else, it shouldn't be an issue to have our copy in CE be different from the copy in DM (thus not having to worry about needing to strip any classes when saving back to Parsoid).",1411593819,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,*** Bug 65355 has been marked as a duplicate of this bug. ***,1400178184,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: On saving a page in the File: namespace the file preview is not reshown (until reload),"After saving an edit in the file namespace the big thumbnail of the file is not shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400164080,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-fclmxs3oedf5jio2gq6g,task_description,resolved
+VisualEditor: On saving a page in the File: namespace the file preview is not reshown (until reload),"Change 133897 merged by jenkins-bot:
+On file pages, only replace the (local) image description when saving
+
+https://gerrit.wikimedia.org/r/133897",1400521871,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fclmxs3oedf5jio2gq6g,task_subcomment,NA
+VisualEditor: On saving a page in the File: namespace the file preview is not reshown (until reload),"Change 133897 had a related patch set uploaded by Alex Monk:
+On file pages, only replace the (local) image description when saving
+
+https://gerrit.wikimedia.org/r/133897",1400346229,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fclmxs3oedf5jio2gq6g,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"1. Edit some text (e.g the -> foo)
+1. Edit existing link (e.g. on [[mw:VisualEditor]], link to ""Parsoid"")
+2. Enter text that makes up part of a title (e.g. ""ResourceLoade"", note, the missing ""r"" at the end)
+3. Select ""ResourceLoader"" from the suggestions
+   (due to a bug in our search engine, this is the second suggestion, not the first:
+   [ > ResourceLoade                                 ]
+     - ResourceLoader/JavaScript Deprecations
+     - ResourceLoader
+     - ResourceLoader/Version 1 Design Specification
+
+4. Observe that the suggestions close after selecting an item, and the text field now contains ""ResourceLoader"". Do not press enter or click anywhere.
+
+5. Press Save Page
+
+Video: http://cl.ly/11431q402d3A
+
+Expected:
+
+* Diff shows ""the -> foo"", and ""Parsoid -> ResourceLoader"".
+
+
+Actual:
+
+* Diff shows ""the -> foo"".
+
+Because:
+
+We both selected a value from the suggestions and then blurred the inspector by clicking ""Save page"". Either of those actions ought to save the value into the model, but doing both certainly should.
+
+There are two weird things about this:
+
+* Changing step 4 and pressing Enter there instead of Save page, makes it save correctly.
+
+So it seems that we just don't save properly on selection or blurring and require one of Escape-key, Enter-key, Back-button or focussing surface (instead of blurring inspector / focussing anything in the main window, e.g. toolbar / save button as well, not just surface).
+
+* Changing step 2/3 to type ""ResourceLoader"" straight up, and not pressing Enter or clicking anywhere before clicking Save page also works. 
+
+So it seems that merely changing focus from input field to save page can be enough to have it saved. Maybe we have an exception for onkeyup/onchange and select is bypassing that?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1400155260,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j7kkjkivstfcbdtgopcv,task_description,resolved
+VisualEditor: Link inspector ignores selected value,*** Bug 68934 has been marked as a duplicate of this bug. ***,1408668143,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Change 155673 merged by jenkins-bot:
+Select the correct annotation in MWLinkTargetInputWidget
+
+https://gerrit.wikimedia.org/r/155673",1408666534,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Change 155673 had a related patch set uploaded by Catrope:
+Select the correct annotation in MWLinkTargetInputWidget
+
+https://gerrit.wikimedia.org/r/155673",1408666195,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,*** Bug 68934 has been marked as a duplicate of this bug. ***,1408666007,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Following the steps exactly as per comment #0 still exhibits this bug exactly.
+
+I can reproduce it locally on latest master by making a link to User:Root when typing ""User:Ro"" where the suggestions are [ ""User:Root/common.js"", ""User:Root"" ].",1403713144,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Change 138114 merged by jenkins-bot:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533850,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Change 138114 had a related patch set uploaded by Catrope:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533460,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"Steps to reproduce:
+
+1.Open a page with VE that has link inside it.
+2.Tap on any link 
+
+Observed Result:
+The browser page gets redirected to the link target page
+
+Test Environment: https://en.m.wikipedia.org/
+Device: iPad Mini
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66999
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67002
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67063",1400114400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dpdpa5liabymg7w2g4yy,task_description,resolved
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Verified the fix in production,1405026344,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Verified the fix in test2,1404774327,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Verified the fix in Betalabs,1404261101,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"Change 143152 merged by jenkins-bot:
+Prevent iOS Safari from following links
+
+https://gerrit.wikimedia.org/r/143152",1404243362,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"Change 143152 had a related patch set uploaded by Esanders:
+Prevent iOS Safari from following links
+
+https://gerrit.wikimedia.org/r/143152",1404162008,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"(In reply to Ed Sanders from comment #8)
+> We don't even have event listeners on links at the moment but we might have to
+> add some as a work around
+
+Eww. If we do, let's keep it as local as possible (mobile-only, for instance).",1404160763,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Links don't have any custom highlights (and shields no longer exist) so this must just be a CE bug in iOS (should be filed upstream if possible). We don't even have event listeners on links at the moment but we might have to add some as a work around,1404160696,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,did not get*,1403895079,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"This bug did not resolved by :
+
+FocusableNode: Use getClientRects()[0] instead of getBoundingClientRect()
+
+https://gerrit.wikimedia.org/r/142260",1403895048,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"**jgonera** wrote:
+
+%%%*** Bug 66559 has been marked as a duplicate of this bug. ***%%%",1403652268,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Pushing to Ed because it appears to be a shield/highlight issue.,1403573090,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"**jgonera** wrote:
+
+Jon has never worked on this bug.",1403560880,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"**jgonera** wrote:
+
+Link is followed (kind of)
+
+**Attached**: {F13597}",1403559841,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"**jgonera** wrote:
+
+This bug happens on any iOS Safari probably. The link doesn't seem to go to the destination in some cases (in my dev instance it goes to 127.0.0.1 even though I loaded the page from an external IP).
+
+More importantly, this seems to be happening only when the keyboard is hidden (contenteditable is not focused). See attached video.
+
+I tested it on iOS 7.1.1. It doesn't happen on Chrome for Android.",1403559813,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor: Use $.when() rather than sourceCount in MediaSearchWidget,"See inline comment on https://gerrit.wikimedia.org/r/#/c/133050/1/modules/ve-mw/ui/widgets/ve.ui.MWMediaSearchWidget.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400108760,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-b73qbgwpj2jg4avkkdnb,task_description,resolved
+VisualEditor: Use $.when() rather than sourceCount in MediaSearchWidget,"Change 150001 merged by jenkins-bot:
+Use $.when() in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/150001",1406787242,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b73qbgwpj2jg4avkkdnb,task_subcomment,NA
+VisualEditor: Use $.when() rather than sourceCount in MediaSearchWidget,"Change 150001 had a related patch set uploaded by Mooeypoo:
+Use to $.when() in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/150001",1406575990,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b73qbgwpj2jg4avkkdnb,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Go to this page:http://en.wikipedia.beta.wmflabs.org/wiki/14thmaychrome?veaction=edit
+2.Select the image on the page
+3.Go to Media Settings>Advanced Settings>Image Size
+4.Change the tab from Default to custom or Custom to Default
+
+Observed Result:
+
+The ""Make full size"" button remains disabled for the image
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13562}",1400101140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_description,resolved
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,Verified the fix in production,1400794773,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,Verified the fix in test2,1400268218,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,Verified the fix in Betalabs,1400202274,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,"Change 133384 merged by jenkins-bot:
+Revert ""Cache image scalable promises by filename""
+
+https://gerrit.wikimedia.org/r/133384",1400108201,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,"Change 133384 had a related patch set uploaded by Catrope:
+Revert ""Cache image scalable promises by filename""
+
+https://gerrit.wikimedia.org/r/133384",1400108090,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,It seems likely that this is due to cache pollution of the promise cache introduced in https://gerrit.wikimedia.org/r/#/c/132207/4/modules/ve-mw/dm/nodes/ve.dm.MWImageNode.js . The bug only happens when saving then reopening the editor in the same session without navigating away.,1400107759,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,"Found the steps to reproduce:
+
+1.Insert any image
+2.Go to Media Settings>Advanced Settings
+3.Select Custom tab and change the values
+4.Apply changes
+5.Save the page
+6.Reopen the page
+7.Go to the Media Settings>Advanced Settings of that image again
+
+Observed Result:
+The ""Make full size"" button became disabled ,switching tabs/changing values again does not make it enabled anymore.",1400106941,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,"Screenshot
+
+Steps to reproduce:
+
+1.Go to this page:http://en.wikipedia.beta.wmflabs.org/wiki/12thmayff?veaction=edit
+
+2.Select the first image on the page: Dau_ho_thoi_Ho.png
+
+3.Make any edit on the image's caption field
+
+4.Click on ""Apply Changes""
+
+Observed Result:
+
+The Media Settings dialog does not get closed , the edit does not get saved
+
+The following error appears in the console:
+
+
+TypeError: originalDimensions is undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13995}",1399925160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_description,resolved
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,Verified the fix in production,1400794643,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,Verified the fix in test2,1400269461,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,Verified the fix in Betalabs,1400014154,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,"Change 133123 merged by jenkins-bot:
+Make sure originalDimensions are available before use
+
+https://gerrit.wikimedia.org/r/133123",1400011867,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,"Change 133123 had a related patch set uploaded by Mooeypoo:
+Make sure originalDimensions are available before use
+
+https://gerrit.wikimedia.org/r/133123",1400010908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,For Chrome the error appearing is a bit different:Uncaught TypeError: Cannot read property 'width' of undefined,1399932675,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,"The following steps ensure reproducing the issue for all images:
+
+1.Insert a new image in a page and save the page
+2.Reopen the page and go to the Advanced Settings of the image
+3.Click on custom tab and click on Apply Changes
+4.Save the page
+5.Reopen the page and again go the Advanced Settings of the image
+6.Click on Default tab and click on Apply changes
+
+You will see the error and get stuck inside the media settings dialog box",1399928696,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"Earlier today, the toolbar in VisualEditor stopped displaying ""Cite"" on the new citation tool, and instead started displaying ""<visualeditor-toolbar-cite-label>"".  
+
+For me, it displayed correctly until I changed languages to qqx to check something else; when I went back, it was broken.  For James F, it was displaying correctly until he logged out.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66543",1399917120,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-xph2545wogpg3ilxwqvv,task_description,duplicate
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"(In reply to Antoine ""hashar"" Musso from comment #4)
+> I tried to reproduce the issue with:
+> 
+>  eaction=edit&uselang=en
+>  eaction=edit&uselang=qqx
+>  eaction=edit
+> 
+> The Cite label in the toolbar was back to normal.
+
+Indeed; a null edit to the message page brought it back into the l10n cache.
+
+> Could it be that whenever that new Cite function got added the l10n cache
+> did not get regenerated?   Without a way to reproduce it there is not much
+> we can do unfortunately.
+
+No. It was added in 1.23wmf20. It is very unlikely that the l10n cache having suddenly broken on Monday night was caused by a deploy two months ago. :-)",1399997338,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"I tried to reproduce the issue with:
+
+ eaction=edit&uselang=en
+ eaction=edit&uselang=qqx
+ eaction=edit
+
+The Cite label in the toolbar was back to normal.
+
+
+Could it be that whenever that new Cite function got added the l10n cache did not get regenerated?   Without a way to reproduce it there is not much we can do unfortunately.",1399986128,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"(In reply to Andre Klapper from comment #2)
+> Only in VisualEditor strings, or also other places been seen?
+
+So far I've only seen it for this particular VE-related message, but the fun thing with deployment bugs is you never know…",1399927904,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"Only in VisualEditor strings, or also other places been seen?",1399923681,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"As a note, it was fixed by me making a null edit to [[MediaWiki:visualeditor-toolbar-cite-label]]. Apparently the same breakage (in pl rather than en) was experienced on plwiki earlier as well.",1399917463,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+VisualEditor: Automatically place cursor in edit summary field,"TeamGale doesn't recall that in order to fill the edit summary field you need to click on that first - if she doesn't, the text she's typing, although the dialog is visible, ends up in the article instead (FF29, Win8).
+
+If I hit Save changes in any of my browsers (Chrome, FF and Opera) and don't click on the dialog, nothing happens if I keep typing.
+However I believe that if it is technically possible, the extra click shouldn't happen, there are no other places where the cursor should end up, and editors seeing it flashing might be encouraged to use the field a little more.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64521",1399906920,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kvdc2sbtbd6agc4wdbbt,task_description,resolved
+VisualEditor: Automatically place cursor in edit summary field,*** Bug 64521 has been marked as a duplicate of this bug. ***,1401996489,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kvdc2sbtbd6agc4wdbbt,task_subcomment,NA
+VisualEditor: Automatically place cursor in edit summary field,"Change 134108 merged by jenkins-bot:
+Initialise save panel on 'ready' so focus works
+
+https://gerrit.wikimedia.org/r/134108",1400521769,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kvdc2sbtbd6agc4wdbbt,task_subcomment,NA
+VisualEditor: Automatically place cursor in edit summary field,"Change 134108 had a related patch set uploaded by Esanders:
+Initialise save panel on 'ready' so focus works
+
+https://gerrit.wikimedia.org/r/134108",1400516649,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kvdc2sbtbd6agc4wdbbt,task_subcomment,NA
+VisualEditor Mobile: Cannot save any page on production after an edit with mobile VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open any page with Mobile VE 
+2.Make some Edit
+3.Attempt to save the page
+
+Observed Result:
+The Page cannot be saved, the spinner does not go away from the page.
+The following error appears in the console:
+TypeError: s is undefined
+	
+
+...unction(s){return s.replace(/['""<>&]/g,escapeCallback);},element:function(name,a...
+
+load.p...203716Z (line 168)
+
+See the screenshot attached
+
+Found on this page: https://en.m.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13680}",1399673700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oz5jjuc4evheyckkxa75,task_description,resolved
+VisualEditor Mobile: Cannot save any page on production after an edit with mobile VE,This issue got fixed after the wmf 4 deployment to production.Marking as fixed and verified .,1400191988,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oz5jjuc4evheyckkxa75,task_subcomment,NA
+VisualEditor Mobile: Cannot save any page on production after an edit with mobile VE,It works on beta labs so I would suspect that this is an issue that got caught and will be fixed in next deployment... unless beta labs and enwiki differ in any way?,1400090712,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-oz5jjuc4evheyckkxa75,task_subcomment,NA
+VisualEditor Mobile: Cannot save any page on production after an edit with mobile VE,"In chrome,the error that appears in the console while saving a page is:
+
+
+Uncaught TypeError: Cannot read property 'replace' of undefined 
+
+However,if you refresh the page , you will see the edit does get saved on the page",1399938958,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oz5jjuc4evheyckkxa75,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,"in ve.ce.Surface we the following line:
+
+ if ( $.browser.msie === true && e.which === 229 ) {
+
+Give we haven't tested IE in so longer I suspect this might not work anymore, but if it does, we need another way to detect that this hack is needed as $.browser is deprecated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399649400,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cxvaopbhevdikka45q3y,task_description,resolved
+VisualEditor: IME detection should not use useragent sniffing,Was fixed by https://gerrit.wikimedia.org/r/#/c/141457 .,1414059000,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,"Rephrasing to be the bug David wants to work on in general.
+
+For the literal usage of $.browser, see bug 65404.",1401380341,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,Bumping priority as this needs to be done very soon…,1401380159,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,It needs to not use $.browser within 2 weeks tops.,1400512997,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,"I'm in the process of stripping these checks out anyway, because the inIme checks cannot be made realiable. Does this need removing immediately? If so I can submit a smaller patch that does this.",1400512916,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+"VisualEditor: Link icon in menu shown as ""selected"" (but only if link was created this session?)","Screenshot showing link vs. formula icon to highlight difference
+
+It's possible to get a link inspector icon shown as ""selected"" in the inspector menu, which is… confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14013}",1399416300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dobpoqvld4np3b5yv3hj,task_description,resolved
+"VisualEditor: Link icon in menu shown as ""selected"" (but only if link was created this session?)",This was fixed a while ago with the new context.,1406756218,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dobpoqvld4np3b5yv3hj,task_subcomment,NA
+VisualEditor: CTRL+A in Firefox creates a selection starting at 0 and ending after the document node,"Selections at non-content offsets are bad, e.g. pressing delete will throw an exception.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399324080,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rj2zoft2yh74cpk6h2y7,task_description,resolved
+VisualEditor: CTRL+A in Firefox creates a selection starting at 0 and ending after the document node,*** Bug 57355 has been marked as a duplicate of this bug. ***,1399642730,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rj2zoft2yh74cpk6h2y7,task_subcomment,NA
+VisualEditor: CTRL+A in Firefox creates a selection starting at 0 and ending after the document node,"Change 131688 merged by jenkins-bot:
+Special case for deleting the entire document
+
+https://gerrit.wikimedia.org/r/131688",1399626382,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rj2zoft2yh74cpk6h2y7,task_subcomment,NA
+VisualEditor: CTRL+A in Firefox creates a selection starting at 0 and ending after the document node,"Change 131688 had a related patch set uploaded by Esanders:
+Special case for deleting the entire document
+
+https://gerrit.wikimedia.org/r/131688",1399379110,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rj2zoft2yh74cpk6h2y7,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Type something to search a media file
+
+Observed Result:
+When the search results appear observe that there is an extra empty column appearing at the right end in the search result dialog box.
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64808
+
+**Attached**: {F13839}",1399314000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zwqtfztcfyrexovbyarr,task_description,resolved
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row",Verified the fix in en.wiki running wmf8,1402685612,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row",Verified the fix in Betalabs and test2,1402343157,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Change 136314 merged by jenkins-bot:
+Change padding on media search results so we can display 4 results on a row with a scrollbar
+
+https://gerrit.wikimedia.org/r/136314",1401925013,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Change 136314 had a related patch set uploaded by Alex Monk:
+Change padding on media search results so we can display 4 results on a row with a scrollbar
+
+https://gerrit.wikimedia.org/r/136314",1401456799,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row",Re-phrasing title based on feedback from Roan.,1401401408,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","This is still happening for me, when I always have scroll bar showing on MAC OS",1399331340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Change 131516 merged by jenkins-bot:
+Remove unnecessary space in footless dialog
+
+https://gerrit.wikimedia.org/r/131516",1399315979,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Change 131516 had a related patch set uploaded by JGonera:
+Remove unnecessary space in footless dialog
+
+https://gerrit.wikimedia.org/r/131516",1399315766,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"**Author:** `b.coughlan2`
+
+**Description:**
+Tested on MW 1.22.6 with stable snapshot of VisualEditor, but looking at the master branches I'm quite sure that this still applies.
+
+Steps to reproduce
+==================
+
+1. Set wiki to have read access only for users:
+
+   $wgGroupPermissions['*']['read'] = false;
+   $wgGroupPermissions['user']['read'] = true;
+
+   Note that if testing on local environment, you will have to first open VE with the 'Edit' button, so that Parsoid is not locked out by this configuration.
+
+2. Open the 'Media' button in the VE toolbar and search for something.
+3. The AJAX request will return 'readapidenied', because it won't recognise the user credentials.
+
+
+Cause
+=====
+
+ve.ui.MWMediaSearchWidget.js makes a JSONP request to the localhost. However, MediaWiki's ApiMain.php:180 (https://git.wikimedia.org/blob/mediawiki%2Fcore.git/9db61c9ab58b11b639a1f95916b37b57530ec674/includes%2Fapi%2FApiMain.php#L180) will remove user credentials from JSONP requests for security reasons. Therefore, the user is treated as not being logged in and the 'readapidenied' message is returned.
+
+
+
+Solution
+========
+
+There is already a TODO here from Trevor Parschal bf268e82:
+
+    // TODO: Only use JSON-P for cross-domain.
+    // jQuery has this logic built-in (if url is not same-origin ..)
+    // but isn't working for some reason.
+
+However, I can't see anything in the jQuery $.ajax docs that says it will switch from JSONP to JSON for same-origin requests.
+
+So if it's not automatic, the obvious fix is to add a function that checks for same-origin in the Javascript. But since this issue is hard to debug and may occur again for other extension developers, I think it would be better to patch the MW core so that it only strips user credentials for cross-origin JSONP requests ApiMain.php:180. 
+
+I didn't want to make a patch for this without checking about the security implications, and also to ask if there is an existing utility function in MediaWiki which checks if a request is same-origin?  
+
+
+Workaround
+==========
+
+If you are only searching the private wiki and no external sources, a temporary workaround is to change ""'datatype': 'jsonp'"" to ""'datatype': 'json'""  in ve.ui.MWMediaSearchWidget.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399207560,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-reknxycmtl2gxva75ktp,task_description,resolved
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 223853 merged by jenkins-bot:
+MWMediaResourceProvider: Use exist instead of bool check on API values
+
+[[https://gerrit.wikimedia.org/r/223853]]",1436466919,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 223853 had a related patch set uploaded (by Jforrester):
+MWMediaResourceProvider: Use exist instead of bool check on API values
+
+[[https://gerrit.wikimedia.org/r/223853]]
+",1436466679,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),Thanks!,1434050858,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"* https://gerrit.wikimedia.org/r/217444 (branch master): #mw1.26wmf10
+",1434042133,PHID-USER-n4kveqwjjlpsb6ydn73h,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 217444 merged by jenkins-bot:
+MWMediaResourceProvider: Use exist instead of bool check on API values
+
+[[https://gerrit.wikimedia.org/r/217444]]",1434040562,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),This bug has popped up again because the check of config.local is wrong.,1433983523,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 217444 had a related patch set uploaded (by MarkAHershberger):
+Fix check of JSON return value
+
+[[https://gerrit.wikimedia.org/r/217444]]
+",1433983507,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 150054 merged by jenkins-bot:
+MWMediaSearchWidget: Use json/jsonp for local/foreign api respectively
+
+https://gerrit.wikimedia.org/r/150054",1406740424,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 150054 had a related patch set uploaded by Mooeypoo:
+Switch between json/jsonp for local/remote api search
+
+https://gerrit.wikimedia.org/r/150054",1406585034,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),*** Bug 68141 has been marked as a duplicate of this bug. ***,1406584368,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"(In reply to Krinkle from comment #7)
+> (In reply to Barry Coughlan from comment #2)
+> > The crossDomain logic will switch between the 'script' and 'xhr' transports,
+> > but both requests will still have be JSONP and have the callback parameter.
+> > 
+> > See here: http://jsfiddle.net/yvzSL/228/
+> > 
+> > In your developer tools console you can see that the local request uses XHR,
+> > but it is still a JSONP request over XHR. I have read through the $.ajax
+> > docs a number of times now and I see no indication that it should behave
+> > otherwise.
+> 
+> That example is broken. The first request is is malformed. ""json jsonp"" is
+> not a valid dataType. This value is invalid and unsupported. It seems to
+> default to a script tag instead, but as you can see the callback in that
+> code never fires. Here's a forked version of that example where I added
+> number ""1"" and ""2"". You'll find that ""DONE 1"" never appears.
+> 
+> http://jsfiddle.net/L5PtK/
+
+To clarify, I know dataType supports multiple values, but that's for converting the response (e.g. xml over jsonp). But you can't convert the actual data from json to jsonp or from json to jsonp (unless an API would embed javascript inside json or something like that).
+
+As for VisualEditor, it should use json when contacting the local API. and jsonp when contacting any foreign API (whether on the same domain or not).
+
+There is logic for this in jQuery that automatically switches from ""json"" to ""jsonp"" for cross domain urls.
+
+However that doesn't trigger the way I expected. It makes the assumption that 1) you should only make 'json' requests to APIs on the same domain or with CORS authentication set up. Then if a browser doesn't support CORS it will use script  with JSONP instead of XHR. So it functions like a fallback for browsers not supporting CORS, *not* as a convenience to switch to JSONP automatically for any cross domain url.
+
+jquery.js
+> if ( !options.crossDomain || support.cors ) {",1406583039,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"(In reply to Barry Coughlan from comment #2)
+> The crossDomain logic will switch between the 'script' and 'xhr' transports,
+> but both requests will still have be JSONP and have the callback parameter.
+> 
+> See here: http://jsfiddle.net/yvzSL/228/
+> 
+> In your developer tools console you can see that the local request uses XHR,
+> but it is still a JSONP request over XHR. I have read through the $.ajax
+> docs a number of times now and I see no indication that it should behave
+> otherwise.
+
+That example is broken. The first request is is malformed. ""json jsonp"" is not a valid dataType. This value is invalid and unsupported. It seems to default to a script tag instead, but as you can see the callback in that code never fires. Here's a forked version of that example where I added number ""1"" and ""2"". You'll find that ""DONE 1"" never appears.
+
+http://jsfiddle.net/L5PtK/",1406582208,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"(In reply to Krinkle from comment #5)
+> [callback] is only applied when the ""jsonp"" transport is activated (builds
+> on top of the ""script"" transport).
+> 
+> And the ""json"" dataType only activates ""json"" in case of crossDomain.
+> 
+
+I mean, the ""json"" dataType only activates ""jsonp"" in case of crossDomain.",1406582085,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"(In reply to Barry Coughlan from comment #2)
+> The crossDomain logic will switch between the 'script' and 'xhr' transports,
+> but both requests will still have be JSONP and have the callback parameter.
+> 
+> See here: http://jsfiddle.net/yvzSL/228/
+> 
+> In your developer tools console you can see that the local request uses XHR,
+> but it is still a JSONP request over XHR. I have read through the $.ajax
+> docs a number of times now and I see no indication that it should behave
+> otherwise.
+
+You read wrong. &callback= (or rather s.jsonpCallback) is only applied when the ""jsonp"" transport is activated (builds on top of the ""script"" transport).
+
+And the ""json"" dataType only activates ""json"" in case of crossDomain.
+
+Making a plain api request to a non-crossdomain url does NOT result in a callback parameter. Instead it results in a plain JSON response that is parsed by JSON.parse, no callback or javascript execution comes into play.
+
+MediaWiki core uses $.ajax in this in many places. For example mediawiki.user.js[1] uses it to fetch user rights and groups information from the API. This behaviour has been this way for quite a while.
+
+Like I said, if VisualEditor and/or your wiki is doing it differently, there is most likely a bug in the code invoking $.ajax.
+
+
+[1] https://github.com/wikimedia/mediawiki-core/blob/08c17086e1/resources/src/mediawiki/mediawiki.user.js#L27-L41",1406582007,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"I ran into the same problem myself my private wiki (1.23 and the REL1_23 branch of VE)
+
+What are the security implications if I make the workaround change mentioned above? I have a foreign API configured, but it's one I control.
+
+Thanks!
+--Ryan",1403031941,PHID-USER-evwol34rsld7viokxokd,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"**b.coughlan2** wrote:
+
+I did some more re-thinking about this.
+
+I examined the jQuery code and the 'crossDomain' attribute is just for selecting the transport (XMLHttpRequest or <script> tag). It does not select data types (json/jsonp), i.e. if the datatype is 'jsonp' and the request is local, you will get a 'jsonp' request with a 'callback' parameter over XMLHttpRequest. The MW core will assume that any request with a 'callback' parameter is from another domain, and will treat the request as unauthenticated.
+
+MW core needs a better way to detect if a request is really cross-origin. The solution is CORS, but this is not supported in a standard way on IE9 (http://caniuse.com/cors). The most ""correct"" fix would be to change the MW core to use CORS to detect cross-origin requests, but this might break plugins relying on the API in IE<=9, so it would be a risky fix until IE9 is no longer a concern for anyone.
+
+I'm now convinced that the simplest fix for now is to add some logic in the VisualEditor JS to detect if the request will be local, based on the target URL of the request. Then use the 'json' datatype if it is local, and the 'jsonp' datatype if not. Here is jQuery's logic for checking that: https://github.com/jquery/jquery/blob/master/src/ajax.js#L518
+
+Note that I tried this out by implementing custom prefilters/transports for jQuery (to leverage the crossDomain code already present), but this approach is hacky and a dead end.",1401770496,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"**b.coughlan2** wrote:
+
+The crossDomain logic will switch between the 'script' and 'xhr' transports, but both requests will still have be JSONP and have the callback parameter.
+
+See here: http://jsfiddle.net/yvzSL/228/
+
+In your developer tools console you can see that the local request uses XHR, but it is still a JSONP request over XHR. I have read through the $.ajax docs a number of times now and I see no indication that it should behave otherwise.",1399374421,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"There is most certainly logic in $.ajax to switch between xhr/json and script/jsonp. This has been in jQuery for many years.
+
+The reason it isn't working might be related to the usage of protocol-relative urls, or the presence of CORS support.
+
+To cite the relevant parts:
+
+	// A cross-domain request is in order when url parts mismatch
+	if ( s.crossDomain == null ) {
+		parts = rurl.exec( s.url.toLowerCase() );
+		s.crossDomain = !!( parts[ 1 ] !== ajaxLocParts[ 1 ] || .. );
+	}
+	..
+	jQuery.ajaxTransport( ""script"", function(s) {
+		// This transport only deals with cross domain requests
+		if ( s.crossDomain ) {
+			..
+		}
+	});
+	..
+	if ( xhrSupported ) { jQuery.ajaxTransport(function( s ) {
+		if ( !s.crossDomain .. ) {
+			return { send: function() {
+				var xhr = s.xhr();
+				..
+	..
+
+Anyway, no work around is needed. It is a well-known feature of $.ajax, we just need to start using it. And if it isn't working, find out what we're doing wrong on our end.",1399244614,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: Get rid of div wrapping in template rendering,"Div wrapping of rendered templates causes problems, especially when the template generates something like a <tr>. We should try to get rid of this wrapping and instead put shields and what not directly in the tag itself.
+
+Potential issues:
+* may not work for all tags
+* may not work for inline tags
+* won't work for non-tag things (text nodes, comments)
+* tricky for multi-sibling templates
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399091520,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2caghp6wplr54d3wekly,task_description,resolved
+VisualEditor: Get rid of div wrapping in template rendering,Fixed by Ed in https://gerrit.wikimedia.org/r/#/c/140439/,1404350131,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2caghp6wplr54d3wekly,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier","Right now there's a noticeable delay; we can speed up user experience at the expense of resources.
+",1399072260,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-parbfhdkrfhhceyjfyzf,task_description,declined
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",I think this is something we could do after the page has finished loading...,1427320035,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",Slowing down load isn't something we're interested.,1426880111,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier","Unassigning for now. Already working with Roan on TargetLoader, {T91715}, and the blockers under {T74063}.",1426622432,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",I started looking into this and found that MWTransclusionModel#fetchRequestDone actually wants to handle all sorts of data about normalisation and redirects and things which a current ApiResponseCache system (as part of the above link) would not provide (as it's not part of the data.query.pages part of the response). Waiting for @Catrope's input.,1422654417,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",I started looking into this and found that MWTransclusionModel#fetchRequestDone actually wants to handle all sorts of data about normalisation and redirects and things which a current ApiResponseCache system (as part of the above link) would not provide (as it's not part of the data.query.pages part of the response).,1422572392,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",I started looking into this and found that MWTransclusionModel#fetchRequestDone actually wants to handle all sorts of data about normalisation and redirects and things which a proper ApiResponseCache system would not provide (as it's not part of the data.query.pages part of the response).,1422572367,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",Might be something that could take advantage of code in https://gerrit.wikimedia.org/r/#/c/180228/,1422049468,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",(Needs performance investigation.),1400138507,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",Also pre-load the templates configured for the cite tools.,1399317199,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open a reference dialog box or Media Settings for an image
+3.Try open any of the inspectors:Math/Hiero/Special Character
+
+Observed Result:
+All inspector appearing with broken UI
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13474}",1399055460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-twukwcdq55v7wby6qwvx,task_description,resolved
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"(In reply to Rummana Yasmeen from comment #11)
+> Ah I see, Sorry we didnt know that before the fix, opening a different one
+> and tagging that against this week's target milestone.
+
+No worries. :-)",1416276547,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Ah I see, Sorry we didnt know that before the fix, opening a different one and tagging that against this week's target milestone.",1416275702,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"This bug didn't recur, it was a new bug with a totally different cause. Let's not confuse things by claiming we fixed the same bug. :-)",1416271003,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Change 173977 merged by jenkins-bot:
+Followup ca6a16f: use parent selector both for hiding and showing windows
+
+https://gerrit.wikimedia.org/r/173977",1416262354,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Change 173977 had a related patch set uploaded by Catrope:
+Followup ca6a16f: use parent selector both for hiding and showing windows
+
+https://gerrit.wikimedia.org/r/173977",1416261348,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Created attachment 17116
+screenshot,  showing blank link inspector
+
+**Attached**: {F13475}",1415891464,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Reopen this issue.
+In test2 and beta only.
+
+steps-
+
+1> open the link/math/comment/special characters/ inspectors in Media Settings -> caption sub-editor or the References sub-editor. The inspectors are blank with no UI.
+
+Also see Bug 68130 https://bugzilla.wikimedia.org/show_bug.cgi?id=68130.",1415891307,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified in production,1400188644,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified the fix in test2,1400023054,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified the fix on Betalabs,1399074288,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Change 131112 merged by jenkins-bot:
+Fix regression in frame style scoping
+
+https://gerrit.wikimedia.org/r/131112",1399057262,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Change 131112 had a related patch set uploaded by Catrope:
+Fix regression in frame style scoping
+
+https://gerrit.wikimedia.org/r/131112",1399057200,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+OOjs UI: Auto-disabled tool group still responds to clicks,"* Go to the tools demo
+* Click ""auto-disabling list""
+* Click ""click to disable this tool""
+* ""auto-disabling list"" now appears greyed out
+* Click ""auto-disabling list""
+* An active effect appears, even though the dropdown is disabled and you can't interact with it at all
+
+Other disabled toolgroups don't have this problem, it's only the one that gets disabled dynamically.
+
+This causes a bug in VisualEditor as well: click out of the editor (this disables most tools and auto-disables the Insert toolgroup), then click Insert. An active effect appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64601",1399055100,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2glncnsws774p5ae225r,task_description,resolved
+OOjs UI: Auto-disabled tool group still responds to clicks,"(In reply to Rainer Rillke @commons.wikimedia from comment #2)
+> Is this a duplicate of Bug 64601 ?
+
+No; bug 64434.",1399065942,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2glncnsws774p5ae225r,task_subcomment,NA
+OOjs UI: Auto-disabled tool group still responds to clicks,"Change 131120 merged by jenkins-bot:
+Use .isDisabled() instead of .disabled to support inheriting
+
+https://gerrit.wikimedia.org/r/131120",1399059823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2glncnsws774p5ae225r,task_subcomment,NA
+OOjs UI: Auto-disabled tool group still responds to clicks,Is this a duplicate of Bug 64601 ?,1399059282,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-2glncnsws774p5ae225r,task_subcomment,NA
+OOjs UI: Auto-disabled tool group still responds to clicks,"Change 131120 had a related patch set uploaded by Trevor Parscal:
+Use .isDisabled() instead of .disabled to support inheriting
+
+https://gerrit.wikimedia.org/r/131120",1399058825,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2glncnsws774p5ae225r,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"In some cases, MediaWikiModuleStore can be quite large (over 1 MB). This can lead to local storage becoming full and causing random problems like T66716. According to https://support.mozilla.org/en-US/questions/963825 Firefox shares local storage space across all hosts on a single domain name, so this may be especially problematic for Firefox.
+
+In theory, this shouldn't be an issue since people should always have some sort of fall-back behavior if there are problems with local storage, but in the interests of defensive programming, perhaps we should put a cap on the maximum size of MediaWikiModuleStore.
+
+--------------------------
+**See Also**:
+* {T66716} (bug 64716)
+* {T67566} (bug 65566)
+
+**Upstream**;
+* <https://bugzilla.mozilla.org/show_bug.cgi?id=1064466>",1398981300,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ena4hp3pzrqznsrbns76,task_description,resolved
+mw.loader.store should not occupy all of localStorage,">>! In T66721#7865568, @AlexisJazz wrote:
+> I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/.
+>
+> At the same time, enwiki doesn't seem to be affected.
+
+This means that the changes from this ticket, made some 5-7 years ago, are fortunately still working as expected. We do not use the defragmented module cache in environments where we know localStorage quotas would be shared.
+
+While not a ""cause"", the reason you are seeing this console warning today and not before, is because something is storing large values in localStorage. That is most likely `mw.loader.store` indeed, which was recently re-enabled in Firefox as per T235852, after we learned and confirmed emperically that the shared quotas indeed are no longer a thing in Firefox. Thus allowing the same savings from the defragmented module cache, that people using Safari- and Chromium-based browsers have been enjoying all these years ([documentation](https://www.mediawiki.org/wiki/ResourceLoader/Architecture#Store)).
+
+> JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+This is measuring the uncompressed size of the (minified) CSS and JS code downloaded during your browsing session so far (including from previous pageviews; limited to 1 copy of any given module bundle by name; old versions or variants for other lang/skin contexts are automatically discarded).
+
+1.4MB is not a particularly large number in that regard. Note that nothing about this feature is incurring additional cost in terms of what you download. Quite the opposite.
+
+Features like MediaViewer are not new. They were there before and are there now. Previously, this was stored in the HTTP cache by URL key. They are now stored in a defragmented fashion in the module cache.
+
+By doing this, your browser is able to make optimal use of this cache, allowing it to re-use part of something you downloaded on a previous pageview, and re-use it on this one. This has the impact that as a Firefox user, you are now downloading a drastically lower amount of bytes from the network on a typical pageview, and storing essentially only 1 copy. Saving bandwidth cost, saving disk space, and saving time.
+
+> 
+> JSON.stringify( window.localStorage ).length is 3281.
+> 
+> Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+No. As part of ensuring the cache plays nice with other features and gadgets that make use of cookies and localStorage, mw.loader automatically removes its portion from localStorage if it is full. You probably just missed the window during which this was briefly stored and then no longer.
+
+I suspect you might have additional features enabled that I don't, or have built up caches over a longer period of time. For me in Firefox (my main browser) on test.wikipedia. That's okay, automatically clearing unused code is part of the cycle. It'll start paying off again starting on the next pageview.
+
+```
+JSON.stringify( mw.loader.store ).length
+//> 811398 (0.8MB)
+JSON.stringify( window.localStorage ).length
+//> 847312 (0.8MB)
+```
+
+> I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Extraordinary claims require extraordinary evidence.
+
+Note, I don't think it's extraordinary //in general// that a volunteer would write good code. On the contrary, I'm sure your code is fine, and in fact many extensions we deploy or host as gadgets are maintained by volunteers and often quite to a standard that is as good or above average, including in following performance guidenance.
+
+However your particular claim is obviously meant to suggest that our software somehow is inefficient, which is factually inaccurate by almost every imaginable metric. Wikipedia.org is and remains one of the best performing sites in the world, in any category. That's no small feat.
+
+> Is this task why I'm seeing this error? Is this really resolved?
+
+I believe it remains resolved. The warning you saw (not an uncaught error) in the developer console, is a rare but entirely expected and harmless side-effect of the system working as intended, as has it has been for other browsers over the past 7 years.
+
+This warning may appear on 1 single pageview once a month or so, possibly more regularly if you engage with many different and large frontend features in a short period of time. If you see it on every page view, or if it has any observable negative effect on functionality by a gadget or user script, or on network/bandwidth use; please create a task as that would be an important issue to address.",1650400355,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#7865568, @AlexisJazz wrote:
+> I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/.
+>
+> At the same time, enwiki doesn't seem to be affected.
+
+This means that the changes from this ticket, made some 5-7 years ago, are fortunately still working as expected. We do not use the defragmented module cache in environments where we know localStorage quotas would be shared.
+
+While not a ""cause"", the reason you are seeing this console warning today and not before, is because something is storing large values in localStorage. That is most likely `mw.loader.store` indeed, which was recently re-enabled in Firefox as per T235852, after we learned and confirmed emperically that the shared quotas indeed are no longer a thing in Firefox. Thus allowing the same savings from the defragmented module cache, that people using Safari- and Chromium-based browsers have been enjoying all these years ([documentation](https://www.mediawiki.org/wiki/ResourceLoader/Architecture#Store)).
+
+> JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+This is measuring the uncompressed size of the (minified) CSS and JS code downloaded during your browsing session so far (including from previous pageviews; limited to 1 copy of any given module bundle by name; old versions or variants for other lang/skin contexts are automatically discarded).
+
+1.4MB is not a particularly large number in that regard. Note that nothing about this feature is incurring additional cost in terms of what you download. Quite the opposite.
+
+Features like MediaViewer are not new. They were there before and are there now. Previously, this was stored in the HTTP cache by URL key. They are now stored in a defragmented fashion in the module cache.
+
+By doing this, your browser is able to make optimal use of this cache, allowing it to re-use part of something you downloaded on a previous pageview, and re-use it on this one. This has the impact that as a Firefox user, you are now downloading a drastically lower amount of bytes from the network on a typical pageview, and storing essentially only 1 copy. Saving bandwidth cost, saving disk space, and saving time.
+
+> 
+> JSON.stringify( window.localStorage ).length is 3281.
+> 
+> Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+No. As part of ensuring the cache plays nice with other features and gadgets that make use of cookies and localStorage, mw.loader automatically removes its portion from localStorage if it is full. You probably just missed the window during which this was briefly stored and then no longer.
+
+I suspect you might have additional features enabled that I don't, or have built up caches over a longer period of time. For me in Firefox (my main browser) on test.wikipedia. That's okay, automatically clearing unused code is part of the cycle. It'll start paying off again starting on the next pageview.
+
+```
+JSON.stringify( mw.loader.store ).length
+//> 811398 (0.8MB)
+JSON.stringify( window.localStorage ).length
+//> 847312 (0.8MB)
+```
+
+> I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Extraordinary claims require extraordinary evidence.
+
+Note, I don't think it's extraordinary //in general// that a volunteer would write good code. On the contrary, I'm sure your code is fine, and in fact many extensions we deploy or host as gadgets are maintained by volunteers and often quite to a standard that is as good or above average, including in following performance guidenance.
+
+However your particular claim is obviously meant to suggest that our software somehow is inefficient, which is factually inaccurate by almost every imaginable metric. Wikipedia.org is and remains one of the best performing sites in the world, in any category. That's no small feat.
+
+> Is this task why I'm seeing this error? Is this really resolved?
+
+I believe it remains resolved. The warning you saw (not an uncaught error) in the developer console, is a rare but entirely expected and harmless side-effect of the system working as intended, has it has been for other browsers over the past 7 years. This may pop up once a month or so, possibly more regularly if you engage with many large frontend features in a short period of time. If you see it on every page view, or if it has any observable negative effect on functionality by a gadget or user script, or on network/bandwidth use; please create a task as that would be an important issue to address.",1650400091,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#7865568, @AlexisJazz wrote:
+> I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/.
+>
+> At the same time, enwiki doesn't seem to be affected.
+
+This means that the changes from this ticket, made some 5-7 years ago, are fortunately still working as expected. We do not use the defragmented module cache in environments where we know localStorage quotas would be shared.
+
+While not a ""cause"", the reason you are seeing this console warning today and not before, is because something is storing large values in localStorage. That is most likely `mw.loader.store` indeed, which was recently re-enabled in Firefox as per T235852, after we learned and confirmed emperically that the shared quotas indeed are no longer a thing in Firefox. Thus allowing the same savings from the defragmented module cache, that people using Safari- and Chromium-based browsers have been enjoying all these years.
+
+> JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+This is measuring the uncompressed size of the (minified) CSS and JS code downloaded during your browsing session so far (including from previous pageviews; limited to 1 copy of any given module bundle by name; old versions or variants for other lang/skin contexts are automatically discarded).
+
+1.4MB is not a particularly large number in that regard. Note that nothing about this feature is incurring additional cost in terms of what you download. Quite the opposite.
+
+Features like MediaViewer are not new. They were there before and are there now. Previously, this was stored in the HTTP cache by URL key. They are now stored in a defragmented fashion in the module cache.
+
+By doing this, your browser is able to make optimal use of this cache, allowing it to re-use part of something you downloaded on a previous pageview, and re-use it on this one. This has the impact that as a Firefox user, you are now downloading a drastically lower amount of bytes from the network on a typical pageview, and storing essentially only 1 copy. Saving bandwidth cost, saving disk space, and saving time.
+
+> 
+> JSON.stringify( window.localStorage ).length is 3281.
+> 
+> Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+No. As part of ensuring the cache plays nice with other features and gadgets that make use of cookies and localStorage, mw.loader automatically removes its portion from localStorage if it is full. You probably just missed the window during which this was briefly stored and then no longer.
+
+I suspect you might have additional features enabled that I don't, or have built up caches over a longer period of time. For me in Firefox (my main browser) on test.wikipedia. That's okay, automatically clearing unused code is part of the cycle. It'll start paying off again starting on the next pageview.
+
+```
+JSON.stringify( mw.loader.store ).length
+//> 811398 (0.8MB)
+JSON.stringify( window.localStorage ).length
+//> 847312 (0.8MB)
+```
+
+> I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Extraordinary claims require extraordinary evidence.
+
+Note, I don't think it's extraordinary //in general// that a volunteer would write good code. On the contrary, I'm sure your code is fine, and in fact many extensions we deploy or host as gadgets are maintained by volunteers and often quite to a standard that is as good or above average, including in following performance guidenance.
+
+However your particular claim is obviously meant to suggest that our software somehow is inefficient, which is factually inaccurate by almost every imaginable metric. Wikipedia.org is and remains one of the best performing sites in the world, in any category. That's no small feat.
+
+> Is this task why I'm seeing this error? Is this really resolved?
+
+I believe it remains resolved. The warning you saw (not an uncaught error) in the developer console, is a rare but entirely expected and harmless side-effect of the system working as intended, has it has been for other browsers over the past 7 years. This may pop up once a month or so, possibly more regularly if you engage with many large frontend features in a short period of time. If you see it on every page view, or if it has any observable negative effect on functionality by a gadget or user script, or on network/bandwidth use; please create a task as that would be an important issue to address.",1650400059,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#7865568, @AlexisJazz wrote:
+> I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/.
+>
+> At the same time, enwiki doesn't seem to be affected.
+
+This means that the changes from this ticket, made some 5-7 years ago, are fortunately still working as expected. We do not use the defragmented module cache in environments where we know localStorage quotas would be shared.
+
+While not a ""cause"", the reason you are seeing this console warning today and not before, is because something is storing large values in localStorage. That is most likely `mw.loader.store` indeed, which was recently re-enabled in Firefox as per T235852, after we learned and confirmed emperically that the shared quotas indeed are no longer an issue in Firefox. Thus allowing the same savings from the defragmented module cache, that people using Safari- and Chromium-based browsers have been enjoying all these years.
+
+> JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+This is measuring the uncompressed size of the (minified) CSS and JS code downloaded during your browsing session so far (including from previous pageviews; limited to 1 copy of any given module bundle by name; old versions or variants for other lang/skin contexts are automatically discarded).
+
+1.4MB is not a particularly large number in that regard. Note that nothing about this feature is incurring additional cost in terms of what you download. Quite the opposite.
+
+Features like MediaViewer are not new. They were there before and are there now. Previously, this was stored in the HTTP cache by URL key. They are now stored in a defragmented fashion in the module cache.
+
+By doing this, your browser is able to make optimal use of this cache, allowing it to re-use part of something you downloaded on a previous pageview, and re-use it on this one. This has the impact that as a Firefox user, you are now downloading a drastically lower amount of bytes from the network on a typical pageview, and storing essentially only 1 copy. Saving bandwidth cost, saving disk space, and saving time.
+
+> 
+> JSON.stringify( window.localStorage ).length is 3281.
+> 
+> Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+No. As part of ensuring the cache plays nice with other features and gadgets that make use of cookies and localStorage, mw.loader automatically removes its portion from localStorage if it is full. You probably just missed the window during which this was briefly stored and then no longer.
+
+I suspect you might have additional features enabled that I don't, or have built up caches over a longer period of time. For me in Firefox (my main browser) on test.wikipedia. That's okay, automatically clearing unused code is part of the cycle. It'll start paying off again starting on the next pageview.
+
+```
+JSON.stringify( mw.loader.store ).length
+//> 811398 (0.8MB)
+JSON.stringify( window.localStorage ).length
+//> 847312 (0.8MB)
+```
+
+> I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Extraordinary claims require extraordinary evidence.
+
+Note, I don't think it's extraordinary //in general// that a volunteer would write good code. On the contrary, I'm sure your code is fine, and in fact many extensions we deploy or host as gadgets are maintained by volunteers and often quite to a standard that is as good or above average, including in following performance guidenance.
+
+However your particular claim is obviously meant to suggest that our software somehow is inefficient, which is factually inaccurate by almost every imaginable metric. Wikipedia.org is and remains one of the best performing sites in the world, in any category. That's no small feat.
+
+> Is this task why I'm seeing this error? Is this really resolved?
+
+I believe it remains resolved. The warning you saw (not an uncaught error) in the developer console, is a rare but entirely expected and harmless side-effect of the system working as intended, has it has been for other browsers over the past 7 years. This may pop up once a month or so, possibly more regularly if you engage with many large frontend features in a short period of time. If you see it on every page view, or if it has any observable negative effect on functionality by a gadget or user script, or on network/bandwidth use; please create a task as that would be an important issue to address.",1650399979,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/. At the same time, enwiki doesn't seem to be affected.
+
+JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+JSON.stringify( window.localStorage ).length is 3281.
+
+Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+Sometimes I worry if my userscript is efficient enough. Then I see numbers like 1.4MB and I'm confident again that no matter how bad, I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Is this task why I'm seeing this error? Is this really resolved?",1650395373,PHID-USER-fstzz5dgooacghhxvdbs,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/. At the same time, enwiki doesn't seem to be affected.
+
+JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+JSON.stringify( window.localStorage ).length is 3281.
+
+Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+Sometimes I worry if my userscript is efficient enough. Then I see numbers like these and I'm confident again that no matter how bad, I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Is this task why I'm seeing this error? Is this really resolved?",1650395347,PHID-USER-fstzz5dgooacghhxvdbs,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 776261 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] resourceloader: Enable mw.loader.store in Firefox%%%
+https://gerrit.wikimedia.org/r/776261",1648851599,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 776261 had a related patch set uploaded (by Krinkle; author: Krinkle):
+%%%[mediawiki/core@master] resourceloader: Enable mw.loader.store in Firefox%%%
+https://gerrit.wikimedia.org/r/776261",1648849582,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Thank you, would you mind creating a new task for that?",1571338055,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"This issue seems to be resolved in Firefox 69 and apparently the quota is now per origin. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1064466#c18
+
+So maybe we can start thinking about enabling local storage for Firefox again? At least dependent on the Firefox version number in the user agent?",1571317115,PHID-USER-6wbaay22g6ffupyt3pxo,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Are you seeing that error in Firefox? That shouldn't be possible because MediaWiki self-disables the `mw.loader.store` functionality on all Firefox versions. And upon viewing a page, any previous use of it is also proactively cleared. The `flushWrites` code should not be reachable. If you find that it is being reached in Firefox, please file a separate task and we'll investigate to make sure it remains off.
+
+As for Chrome, there shouldn't be a course of action needed. The system is meant to be self-correcting. The errors you're seeing are ""caught"", that means the MediaWiki code did not crash or stop unexpectedly. The code prints the caught error to the developer console as a ""warning"" so that when developers investigate other issues, they also know this particular condition was reached. Are you finding any loss of functionality in Chrome?
+
+The main problem found in this task was due to multiple wikis storing their modules under the same quota in Firefox. That is not something we can control. More-over, the browser also does not provide a way to let module storage expire from wikis not recently visited. For this reason, we have decided to disable this performance feature in Firefox. In Chrome this should not be a problem given that Chrome sets the quota at the full domain level (not the parent domain).
+
+I noticed in your example that you might be experiencing problems from serving multiple MediaWiki installations from the same domain under different directories. If that is the case and you intend to also offer multiple installations this way in production, I recommend `$wgResourceLoaderStorageEnabled = false;`.
+
+Alternatively, if this is only for local development, run `localStorage.clear();` from the console to clear the storage used by previous/other wiki installations.",1537632521,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"> As for the issue reported in this task, it's been resolved. In theory, it will always be 
+
+So, what is the appropriate course of action? Given that I'm seeing an elevated level (for FF and Chrome) of:
+
+```
+Exception in store-localstorage-update:
+:8080/mw-31-00-elastic/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=0xnodom:177 QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value of 'MediaWikiModuleStore:mw-31-00-elastic' exceeded the quota. DOMException: Failed to execute 'setItem' on 'Storage': Setting the value of 'MediaWikiModuleStore:mw-31-00-elastic' exceeded the quota.
+    at flushWrites (http://127.0.0.1:8080/mw-31-00-elastic/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=0xnodom:175:212)
+logError @ :8080/mw-31-00-elastic/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=0xnodom:177
+```",1537625422,PHID-USER-ldehclaehsvglrqxywsj,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Replied at T85923#2471543 as it seems about a key disappearing, not a key being unable to be set.
+
+As for the issue reported in this task, it's been resolved. In theory, it will always be possible for the storage quota to be reached, at which points random keys will fail to be set. (This is true for cookies as well.)
+
+Task T101732 tracks moving the module cache to a different interface for that reason.",1468861106,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Replied at T85923#2471543 as it seems about a key disappearing, not a key being unable to be set.
+
+As for the issue reported in this task, it's been resolved. In theory, it will always be possible for the storage quota to be reached, at which points random keys will fail to be set. (This is true for cookies as well.)
+
+Task T101732 tracks moving the module cache into a different interface for that reason.",1468861098,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"From {T85923}: `wgMediaViewerOnClick` apparently cannot be reliably saved to local storage; used space (as per `encodeURIComponent(JSON.stringify(localStorage)).length`) is 2600025, quota is (per [[https://arty.name/localstorage.html|this test]]) somewhere between 2600000 and 2700000. The browser is Safari. May be related, although 2600025 is 0b1001111010110001011001 which does not seem like something that would be very close to a quota limit.",1468857408,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,No reports for over a month; closing.,1458258992,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 269625 merged by jenkins-bot:
+resourceloader: Disable localStorage cache on FF, Opera
+
+[[https://gerrit.wikimedia.org/r/269625]]",1455119961,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 269625 had a related patch set uploaded (by Ori.livneh):
+ResourceLoader: disable localStorage cache on FF, Opera
+
+[[https://gerrit.wikimedia.org/r/269625]]
+",1455093316,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Ok. I have been in denial about this long enough, I suppose. Let's start by disabling it completely in Firefox and Opera. I am still interested in more reports, because it will help determine where we go from there.",1455092112,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,I still get this on every page view using Firefox 44.,1454965195,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I continue to get this error on every page view using Opera 12 (obviously, since you only blacklisted Firefox).",1454962821,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Has anyone encountered any bugs since {7787a85d5c6f} went out, just under a month ago?",1454961269,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Nothing has changed here since 2014 -- it was a mistake to enable this feature on Firefox at the time, and it is a mistake to enable it now with a 30KB per-module limit. On my browser at the moment, MediaWikiModuleStore:enwiki is using 655KB, which is hardly an improvement from when the bug was first reported. You only need to visit 7 or 8 wikis to exhaust the quota.
+
+I don't think a <250ms performance improvement justifies randomly breaking the many extensions which use localStorage. 
+
+mediawiki.js will keep writing module caches until it hits the quota and fails. The functionality of the site after such a failure depends on how much of the quota is left -- effectively the remainder of the division, 5MB modulo the per-wiki module store size. An unlucky combination could leave a user unable to dismiss dialog boxes or to choose a preferred language.
+
+Some extensions try localStorage first, and fall back to a cookie if it fails. But the MW core does not provide a convenient interface for this, leaving each extension to implement it separately.",1454308136,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 263417 merged by jenkins-bot:
+Module storage: set stricter storage quotas on Firefox
+
+[[https://gerrit.wikimedia.org/r/263417]]",1452570602,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 263417 had a related patch set uploaded (by Ori.livneh):
+Module storage: set stricter storage quotas on Firefox
+
+[[https://gerrit.wikimedia.org/r/263417]]
+",1452545806,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"FYI, i had an issue fixed in WikEd, which was throwing exceptions all over the place, because it wasn't expecting a full localStorage.
+
+That's the problem with this issue. it's infectious....",1442262617,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Generally yes, regardless of this bug, even. localStorage likes to throw
+exceptions. (For example, apparently it will be defined but throw exception
+on access on Firefox if you disable it in browser settings.)",1441733763,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I assume anyone who wants to use `localStorage` is supposed to use `try`/`catch` on every attempt to save a value so that unrelated scripts are still executed? E.g.:
+https://pt.wikipedia.org/wiki/MediaWiki:Gadget-fastbuttons.js?diff=43318591
+https://meta.wikimedia.org/w/index.php?diff=13512749&oldid=13462279&diffonly=1
+https://github.com/brion/MediaWiki-MobileSidebar/pull/5/files?w=1",1441720355,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I assume anyone who wants to use `localStorage` is supposed to use `try`/`catch` on every attempt to save a value? E.g.:
+https://pt.wikipedia.org/wiki/MediaWiki:Gadget-fastbuttons.js?diff=43318591
+https://meta.wikimedia.org/w/index.php?diff=13512749&oldid=13462279&diffonly=1
+https://github.com/brion/MediaWiki-MobileSidebar/pull/5/files?w=1",1441720309,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I assume anyone who wants to use `localStorage` is supposed to use try/catch on every attempt to save a value? E.g.:
+https://pt.wikipedia.org/wiki/MediaWiki:Gadget-fastbuttons.js?diff=43318591
+https://meta.wikimedia.org/w/index.php?diff=13512749&oldid=13462279&diffonly=1
+https://github.com/brion/MediaWiki-MobileSidebar/pull/5/files?w=1",1441720294,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Interesting and thanks for the counter-example.
+I've taked to @ori about T96155 and the plan is for me to make this code use the new frontend api. When that's in place we could potentially be a bit more clever about what we are allowed to store e.g. limit number of bytes we allow saving for.
+
+Given that MobileFrontend/Gather are only using this storage mechanism to decide whether to show onboarding tutorials for new features, mostly targeting readers who are not editing or newbies, if localStorage is exhausted not showing these things is not the end of the world.
+",1439570818,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T96155#1539605, @matmarex wrote:
+>>>! In T96155#1528593, @Jdlrobson wrote:
+>> Yup. I recognise this is an issue but I am saying that this issue mostly impacts power users (especially on Firefox). I'm yet to see this on the mobile site, where gadgets and user scripts are currently not available nor used.
+> 
+>Eh, I don't think that it mostly impact power users, it can impact even occasional editors too.
+> 
+>As an example:
+>* Visit https://pl.wikipedia.org/wiki/Ostatnia_droga_Temeraire%27a, which is a pretty generic article on the Polish Wikipedia, as anonymous user. Run `JSON.stringify( mw.loader.store ).length` to see how much data ResourceLoader puts in localStorage (this is 707573 for me on first page load).
+>* Open the MediaViewer, which is not a power-user feature. The length increases to 923750.
+>* Open the VisualEditor, which is not a power-user feature either. The length increases to 2008078.
+> 
+>This is already 2 MB, and this is just one wiki and an anonymous user (I'm not sure how the browsers calculate the limit, but if anything, this is less than the number of bytes actually stored). Visit another wiki (say, the same article in English, if you're not satisfied with the content in Polish and speak two languages) and this doubles. Log in (which gets you features like Echo and lets you enable some gadgets or beta features), or visit a third wiki, and you're quickly over the 5 MB limit.
+
+",1439560126,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1418743, @Jdlrobson wrote:
+> Could we use ServiceWorker for this now (see T101731) ?
+
+Yes. We created T101732 last month.",1435784972,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Could we use ServiceWorker for this now (see T101731) ?
+",1435784898,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1411737, @ori wrote:
+>>>! In T66721#1411731, @SamB wrote:
+>> So, um, any tips on how to manually clean up the MediaWikiModuleStore keys from all of the wikipedias on Firefox/Iceweasel, including 31.7.0esr as included in Debian Jessie?
+> 
+> It should not be possible to fill it up now that the patch above has been pushed. You must have gotten into some weird state. Clear localStorage (either by nuking your browser history or by using https://addons.mozilla.org/en-US/firefox/addon/volatile-storage/?src=cb-dl-updated) and see if the problem recurs.
+
+Hmm, I'm still a bit nervous about nuking localStorage entirely, though that certainly would be less tedious than visiting every Wikipedia I've ever loaded in this bowser (including mobile versions) one-by-one and clearing the relevant key from the JS console... (though, that might not be so bad if I used a greasemonkey script to do the actual cleanup for each wiki).
+
+Anyway, this:
+
+>>! In T66721#1340094, @gerritbot wrote:
+> Change 216014 merged by jenkins-bot:
+> mw.loader.store: decline to store items > 100 kB
+> 
+> [[https://gerrit.wikimedia.org/r/216014]]
+
+... doesn't sound very promising to me.  Just because it only stores items < 100 kB does *not* prevent it from storing many such items, which could add up to a lot of usage on a single Wiki; factor in the fact that subdomains share quota on Firefox, and you could still easily hit 5 MiB, no?",1435671555,PHID-USER-3bnjvlq3zbpzzxdh4g4g,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"That extension does not seems to be enough, since I still get this on every page on Portuguese Wikipedia using Firefox 38.0:
+> ""Exception in store-localstorage-update:"" load.php:177:752
+> ""NS_ERROR_DOM_QUOTA_REACHED: Persistent storage maximum size reached"" DOMException [NS_ERROR_DOM_QUOTA_REACHED: ""Persistent storage maximum size reached""
+> code: 1014
+> nsresult: 0x805303f6
+> location: https://pt.wikipedia.org/w/load.php?debug=false&lang=pt&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=CZ6SC%2Fzc:175] load.php:177:790
+> log() load.php:177
+> handler() load.php:155
+> jQuery.Callbacks/fire() load.php:45
+> jQuery.Callbacks/self.fireWith() load.php:46
+> jQuery.Callbacks/self.fire() load.php:46
+> mw.track() load.php:155
+> flush() load.php:175
+and running
+> localStorage.clear();
+in the console doesn't help either.",1435661170,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1411731, @SamB wrote:
+> So, um, any tips on how to manually clean up the MediaWikiModuleStore keys from all of the wikipedias on Firefox/Iceweasel, including 31.7.0esr as included in Debian Jessie?
+
+It should not be possible to fill it up now that the patch above has been pushed. You must have gotten into some weird state. Clear localStorage (either by nuking your browser history or by using https://addons.mozilla.org/en-US/firefox/addon/volatile-storage/?src=cb-dl-updated) and see if the problem recurs.",1435614205,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"So, um, any tips on how to manually clean up the MediaWikiModuleStore keys from all of the wikipedias on Firefox/Iceweasel, including 31.7.0esr as included in Debian Jessie?",1435614036,PHID-USER-3bnjvlq3zbpzzxdh4g4g,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1340106, @matmarex wrote:
+> While the last patch may be helpful, it still does not prevent the cache from taking up all available localStorage space.
+
+Especially on Firefox, where e.g. all of the Wikipedias are sharing quota.  (There are a lot of Wikipedias, and there are reasons someone might look at quite a lot of them.)
+
+Also, to clean up after this, you'll need to do something like what's described at <https://bugzilla.mozilla.org/show_bug.cgi?id=1064466#c11>: have a path on each wiki that will clean up the storage, and also a way to open an iframe to that path on *every* wiki for a given domain ...",1435599957,PHID-USER-3bnjvlq3zbpzzxdh4g4g,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"On the topic of using IndexedDB for module store, beware that there is an important difference with localStorage.
+
+localStorage, while having a lower quota by default (~ 5MB), doesn't have a way to expand that quota. Which means when it's full, the API returns a failure code but nothing is shown the user.
+
+IndexedDB, while having a higher quota by default (~ 10-50MB), has a way of extending the quota. It's not clear to me what happens when you reach the quota. It appears that browsers default to asking the user to expand the quota.
+
+For the purpose of caching modules, and for Wikipedia in general, I don't think we should ever allow that to happen. So we may have to somehow manually poll the aggregate size of database to prevent the browser from asking the user any such question.
+
+See http://www.html5rocks.com/en/tutorials/offline/quota-research/
+{F177107}",1433880982,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"On the topic of using IndexedDB for module store, beware that there is an important difference with localStorage.
+
+localStorage, while having a lower quota by default (~ 5MB), doesn't have a way to expand that quota. Which means when it's full, the API returns a failure code but nothing is shown the user.
+
+IndexedDB, while having a higher quota by default (~ 10-50MB), has a way of extending the quota. It's not clear to me what happens when you reach the quota. It appears that browsers default to asking the user to expand the quota.
+
+For the purpose of caching modules, and for Wikipedia in general, I don't think we should ever allow that to happen. So we may have to somehow manually poll the aggregate size of database to prevent the browser from asking the user any such question.",1433880942,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"* https://gerrit.wikimedia.org/r/216014 (branch master): #mw1.26, #mw1.26wmf9
+",1433469636,PHID-USER-n4kveqwjjlpsb6ydn73h,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"While the last patch may be helpful, it still does not prevent the cache from taking up all available localStorage space.",1433468829,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 216014 merged by jenkins-bot:
+mw.loader.store: decline to store items > 100 kB
+
+[[https://gerrit.wikimedia.org/r/216014]]",1433468548,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 216014 had a related patch set uploaded (by Ori.livneh):
+mw.loader.store: decline to store items > 100 kB
+
+[[https://gerrit.wikimedia.org/r/216014]]
+",1433463569,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1339632, @kaldari wrote:
+> @Mattflaschen The last two solutions sound sensible. Do you have any idea how much that might reduce the average size of the cache by?
+
+On a primed cache on enwiki, the top modules by size for me are:
+
+| Module | Size |
+|--------|------|
+| ext.visualEditor.core | 624 kB |
+| oojs-ui | 179 kB |
+| oojs-ui.styles.icons | 132 kB |
+| oojs-ui.styles | 90 kB |
+| mmv.ui.canvasButtons | 71 kB |
+| ext.visualEditor.mwmeta | 67 kB |
+| jquery.ui.core | 66 kB |
+| ext.visualEditor.mwtransclusion | 65 kB |
+| ext.visualEditor.mwimage | 65 kB |
+| oojs-ui.styles.icons-editing-advanced | 58 kB |
+| ext.visualEditor.mwcore | 52 kB |
+| jquery.ime | 50 kB |
+| moment | 48 kB |
+| mmv.ui.metadataPanel | 47 kB |
+| unicodejs | 46 kB |
+| ext.visualEditor.icons | 45 kB |
+| jquery.chosen | 42 kB |
+| jquery.uls | 37 kB |
+| ext.visualEditor.mediawiki | 35 kB |
+| jquery.uls.data | 33 kB |",1433461898,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"""Assigned To: None"" and ""Priority: High"" are at odds with each other. @ori, are you planning to work on this?",1433461535,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"@Mattflaschen The last two solutions sound sensible. Do you have any idea how much that might reduce the average size of the cache by? Blacklisting Firefox might be good as a last resort, but I would favor trying other solutions first.",1433461107,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Yesterday, we talked on IRC about a few possibilities:
+
+* Blacklisting Firefox (only seems to be an issue due to how it calculates quotas)
+* Blacklisting certain large modules
+* Only storing modules that are needed at page load",1433442846,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"BTW at some point I played with a promise wrapper lib for indexedDB: https://gerrit.wikimedia.org/r/#/c/157818/
+Might be useful if one wants to implement this ticket.",1430294125,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#974945, @Mattflaschen wrote:
+> @Ori plans to look into IndexedDB (which has very different quota rules) as a solution.
+
+Is there a status update about this?",1426484011,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Happened to me too.  A thought occurs: could this be related to the repeated reports during the massive fundraiser in December of dismissed banners coming back? (i.e. because the hide was not remembered, as Kaldari suggested above?)",1423603851,PHID-USER-qsj6mtmeexjxulfje7ie,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,@Ori plans to look into IndexedDB (which has very different quota rules) as a solution.,1421195890,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#946527, @Technical13 wrote:
+> Apparently I had 1,772,879 characters in localStorage on test.wikipedia.org.  Since this is so large, I've been unable to find a pastebin to paste it all to.
+
+There's no need to paste it.  We're aware of (most of, at least) the contents, and the underlying causes.",1421194351,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Apparently I had 1,772,879 characters in localStorage on test.wikipedia.org.  Since this is so large, I've been unable to find a pastebin to paste it all to.",1419818317,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"```
+""NS_ERROR_DOM_QUOTA_REACHED: Persistent storage maximum size reached"" DOMException
+[
+   NS_ERROR_DOM_QUOTA_REACHED: ""Persistent storage maximum size reached""
+   code: 1014
+   nsresult: 0x805303f6
+   location: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141217T214024Z:173
+]
+```
+on my `Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0` system indicates this is still a problem?",1419815416,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 176628 merged by jenkins-bot:
+resourceloader: Clear module storage if disabled by configuration
+
+[[https://gerrit.wikimedia.org/r/176628]]",1417491543,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I think we should turn $wgResourceLoaderStorageEnabled off for the WMF cluster (it's already off by default in DefaultSettings.php) for now.
+
+>>! In T66721#795821, @tstarling wrote:
+> I don't think localStorage can be used as a cache for large objects if there is no way for us to implement an LRU policy.
+
+There is a way, but not if we use localStorage directly.  To solve this issue, I think we should ban direct use of localStorage, and require using a wrapper library that implements some kind of expiration (and also require expirations actually be used when setting).  jStorage (already in core) implements time to live/max-age (as does Storer.js, used by Flow).  Least recently used might be good for some kinds of data as an alternative to TTL, but I don't know if any of the libraries we currently use have it.",1417490159,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Actually the VE thing was disabled 18 months ago, but it will live on in my browser forever. The reason I saw an exception when I activated VisualEditor is because activating VE increased the module storage size to about 1.8MB.",1417416863,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 176628 had a related patch set uploaded (by Tim Starling):
+Clear module storage if it is disabled by configuration
+
+[[https://gerrit.wikimedia.org/r/176628]]
+
+#patch-for-review",1417414290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Actually, disabling the code is not enough -- localStorage has no expiry, so everyone's browser will stay broken until we explicitly clean up these old entries.",1417413196,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"This is the first thing I saw on opening my web console on Wikipedia today -- localStorage exceptions from VisualEditor due to quota exhaustion, apparently due to module storage. I guess it should be reverted, or at least disabled on Firefox, if it can't be managed without breaking localStorage for everyone.
+
+I don't think localStorage can be used as a cache for large objects if there is no way for us to implement an LRU policy.
+
+%%%
+sqlite> select sum(length(value))+sum(length(key)) from webappsstore2 where scope like 'gro.aidepikiw.%' and key like 'MediaWikiModuleStore%';
+3731546
+sqlite> select sum(length(value))+sum(length(key)) from webappsstore2 where scope like 'gro.aidepikiw.%' and key like 've-%';
+535604
+%%%
+
+The VE thing will probably need to be removed or reduced as well.",1417412948,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,Filed an upstream bug against Firefox at https://bugzilla.mozilla.org/show_bug.cgi?id=1064466,1410203795,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Michael M.: That sounds like a good idea, but doesn't solve the underlying issue of this bug (that mw.loader.store takes up too much of localStorage).",1410202490,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"What about this approach?
+1. Before saving a module to localStorage try to save a string of 20 KB* there.
+2. If this fails, don't save the module in localStorage.
+3. If it succeeds, try to save the module.
+4. Whether or not putting the module in localStorage succeeds, remove the string from step 1.
+
+This will make sure that the modules never will occupy the last 20 KB* of localStorage.
+
+*) 20 KB is just the first number that came to my mind. Feel free to replace it with any other reasonable number. I have several user scripts that make use of localStorage, they take up 3 KB, but I know users who use them more heavily than me, they probably end up at about 10 KB or more.",1409558108,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,Ori: Could you reply to comment 6 please if you have some ideas?,1409519861,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Ori: Any thoughts on this? It's still a significant problem, especially for Firefox users.",1408647522,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"(In reply to Krinkle from comment #4)
+> mw.loader.store falls back to fetching from the server. However other
+> features that actually use localStorage in a more visible way will lose data
+> in a much worse way (e.g. users unable to store drafts, or a ""hide"" button
+> not being remembered etc.)
+
+Yep, as you can see from bug 65566 (thanks for marking that as a see also), we've already had to switch to cookies for a feature due to this issue.",1406254533,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Raising priority as this will likely become increasingly more problematic as wikis and extensions register more modules and users enable more features.
+
+mw.loader.store falls back to fetching from the server. However other features that actually use localStorage in a more visible way will lose data in a much worse way (e.g. users unable to store drafts, or a ""hide"" button not being remembered etc.)",1405456170,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,*** Bug 65364 has been marked as a duplicate of this bug. ***,1405455430,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"(In reply to Ryan Kaldari from comment #1)
+> Any thoughts on this? This bug makes using Wikipedia very annoying for me.
+> Surely I can't be the only person that cares about this.
+
+This document explains how to clear localStorage:
+
+https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Storage#Storage_location_and_clearing_the_data
+
+You can also up the quota via about:config. Search for ""dom.storage.default_quota"" option. Its value is in kilobytes.
+
+I'm not suggesting that these are adequate resolutions for this bug -- they're just workarounds. I want to try something like what DJ is proposing in <https://bugzilla.wikimedia.org/show_bug.cgi?id=65364#c3>.",1400638400,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,Any thoughts on this? This bug makes using Wikipedia very annoying for me. Surely I can't be the only person that cares about this.,1400176516,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"Running JavaScript profiling on both desktop and mobile the majority of time is spent in jQuery.extend.css - the majority of which seems to be caused by ve.ce.ProtectedNode.prototype.onProtectedSetup
+
+On mobile this seems to be even more severe.
+
+In desktop 7.9% of execution time to load VisualEditor was spent in jQuery.extend.css - this was the most heavy function. In mobile it was also the most heavy - however in mobile a whopping 23.76% of time was spent in jQuery.extend.css
+
+Stubbing out the contents of the foreach loop 
+this.$element.add( this.$element.find( '*' ) ).each( function () {
+
+seems to remedy this problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51202",1398970740,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-em74gqq6yx5on4mj77dz,task_description,resolved
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"Based on the work that Ed did, I'm going to mark this as closed.",1404866154,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"Additional fixes made for the 2014-05-15 release – but not sure what counts as ""fixing"" this bug. Jon, could you re-test?",1400145400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"https://gerrit.wikimedia.org/r/130823 (for bug 52499) should make this perform a bit better as well, by 1) reducing the number of elements protectedNode CSS is applied to and 2) targeting them with a class rather than a star selector: .ve-ce-protectedNode * is an expensive selector just like .header > *:nth-child(3)",1399071192,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"I went deeper down the rabbit hole... 
+
+Removing all button styling drops this by 23.76% to 16.4%
+It drops to 8.6% with removal of 'skins.minerva.chrome.styles', 8.6% when I drop the use of ui.less
+
+Both the stylings for buttons and ui.less use last-child, nth-child, first-child, not selectors. These seem to be the major pain point.
+
+See bug 64719.",1398980755,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"Specifically it is a style or styles in one of these modules:
+http://localhost.alpha/w/load.php?debug=false&lang=en&modules=mediawiki.ui.button%7Cmobile.pagelist.styles%7Cmobile.styles.beta%7Cskins.minerva.chrome.styles%7Cskins.minerva.content.styles%7Cskins.minerva.drawers.styles&only=styles&skin=minerva&target=mobile&*
+
+
+It drops to 8% with their removal.",1398977725,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"So I tried removing #content element - no visible difference.
+Killing our stylesheets - visible difference (drops 1.59%).
+
+This must be linked to causing reflows, that are more expensive in the Minerva skin.",1398977336,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,We have a lot more DOM nodes in mobile - 2 times the number of DOM nodes in an article. In desktop they replace the page rather than create an overlay..,1398976699,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"**jgonera** wrote:
+
+The question is, why is this more of a problem with mobile skin than with Vector?",1398976459,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"There may be ways to improve this in the short term, but what we really need to do is experiment with using an SVG overlay.",1398975000,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,The majority of time is spent in looking up the float property but importNode is also a relatively big performance hog here,1398971621,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs","Steps to reproduce:
+
+1.Open a page 
+2.Add few references
+3.Now Go to Insert>Reference>Use an Existing Reference 
+4.Select one of the existing references
+
+
+Observed Result:
+
+The selected reference does not get added in the page and the ""Save Page"" remains disabled
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/30thAprilChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398884040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-psuzyfjtumeoqqoapj7r,task_description,resolved
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs",Verified the fix on production,1400011514,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs",Verified the fix on test2,1399078263,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs",Verified the fix in Betalabs,1398895110,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs","Change 130734 merged by jenkins-bot:
+Make inserting existing references work again
+
+https://gerrit.wikimedia.org/r/130734",1398893606,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs","Change 130734 had a related patch set uploaded by Jforrester:
+Make inserting existing references work again
+
+https://gerrit.wikimedia.org/r/130734",1398892280,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs","Also, if you have added a reference list on that session before attempting to add an existing reference,the ""Save Page"" button becomes enabled but if you go to the Review your changes section there is no entry for adding <references> there.
+
+After clicking on ""Save Page"" , you will see the reference list did not get added in the page , but you open VE , you will the reference list",1398884383,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+VisualEditor: Clean up Monobook-specific mess in ViewPageTarget init code,"In particular, see comments on https://gerrit.wikimedia.org/r/#/c/130085/
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398881280,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-izisrqmjp3trkjaifdin,task_description,resolved
+VisualEditor: Clean up Monobook-specific mess in ViewPageTarget init code,Fixed in gerrit 130717.,1398891382,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-izisrqmjp3trkjaifdin,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Go to Insert>Template
+
+Observed Result:
+
+Observe that, in the header of the dialog box , instead of text ""Transclusion"" ,""Null"" is appearing
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13912}",1398881220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftzt37epboyseb3ggnxl,task_description,resolved
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box",Verified the fix in production,1400011801,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftzt37epboyseb3ggnxl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box",Verified the fix in Betalabs and Test2,1399070765,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftzt37epboyseb3ggnxl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box","Change 130749 merged by jenkins-bot:
+Bring the transclusion title back to life
+
+https://gerrit.wikimedia.org/r/130749",1398896883,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftzt37epboyseb3ggnxl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box","Change 130749 had a related patch set uploaded by Jforrester:
+Bring the transclusion title back to life
+
+https://gerrit.wikimedia.org/r/130749",1398894082,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ftzt37epboyseb3ggnxl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""","Larger reference dialog
+
+Reference list dialog box is appearing much larger in size like the previous design that we had.
+
+See the two screenshots attached and compare
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13908}",1398880260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tp3if73tgdh5us2okcnt,task_description,resolved
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""",Verified the fix in production,1400012042,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""",Verified the fix in test2,1399067283,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""",Verified the fix in Betalabs,1398967868,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""","Change 130796 merged by jenkins-bot:
+Make reference list dialog small again
+
+https://gerrit.wikimedia.org/r/130796",1398908760,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""","Change 130796 had a related patch set uploaded by Catrope:
+Make reference list dialog small again
+
+https://gerrit.wikimedia.org/r/130796",1398906371,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""","Created attachment 15253
+Reference list dialog box in production and test2
+
+**Attached**: {F13909}",1398880317,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: For formulae (and some other nodes?), inspection trigger region is a single line, not the whole block","The region you need to move the mouse over to get the inspector to popup.
+
+Using the math editor beta feature. The region you need to position the mouse over the get the inspector icon to come up is quite small. Ideally it should be the whole size of the image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50791
+
+**Attached**: {F13812}",1398807600,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-pwym3hscyxiqlzuo6ffh,task_description,resolved
+"VisualEditor: For formulae (and some other nodes?), inspection trigger region is a single line, not the whole block",*** Bug 50776 has been marked as a duplicate of this bug. ***,1412589972,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pwym3hscyxiqlzuo6ffh,task_subcomment,NA
+"VisualEditor: For formulae (and some other nodes?), inspection trigger region is a single line, not the whole block",The bug as reported (formula click areas)  is fixed now. It was probably fixed by https://gerrit.wikimedia.org/r/#/c/139805/,1412588736,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pwym3hscyxiqlzuo6ffh,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Screenshot of view and edit mode side-by-side
+
+Ever since the typography update, the content looks malformed in the editor.
+
+This is because the way the typography change in Vector was implemented, used rather specific selectors that cannot apply to VisualEditor's surface and thus it cascades in ways it wasn't supposed to.
+
+The content line-height is squished, and the font size is too small.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13719}",1398772380,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jx5rpwyz5z3myik43die,task_description,resolved
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,Verified the fix on production,1399072889,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,Verified the fix on Betalabs and test2,1399070699,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130745 merged by Catrope:
+mw.ViewPageTarget: Move .mw-body-content down to .ve-ce-surface
+
+https://gerrit.wikimedia.org/r/130745",1398899098,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130745 had a related patch set uploaded by Catrope:
+mw.ViewPageTarget: Move .mw-body-content down to .ve-ce-surface
+
+https://gerrit.wikimedia.org/r/130745",1398893379,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130541 merged by jenkins-bot:
+mw.ViewPageTarget: Move .mw-body-content down to .ve-ce-surface
+
+https://gerrit.wikimedia.org/r/130541",1398892611,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"(In reply to Krinkle from comment #7)
+> Yeah, we fixed the page content font-size and line-height, but now those
+> changes incorrectly apply to our overlays as well. This causes all our
+> inspectors to have messed up line-heights and recursively smaller font-sizes
+> inside e.g. link inspector suggestions and the context menu cursor.
+
+https://gerrit.wikimedia.org/r/130541 addresses this.",1398889325,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Yeah, we fixed the page content font-size and line-height, but now those changes incorrectly apply to our overlays as well. This causes all our inspectors to have messed up line-heights and recursively smaller font-sizes inside e.g. link inspector suggestions and the context menu cursor.",1398889312,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130541 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Move .mw-body-content down to .ve-ce-surface
+
+https://gerrit.wikimedia.org/r/130541",1398818521,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,Still some mess here.,1398815688,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130507 merged by jenkins-bot:
+mw.ViewPageTarget: Use .mw-body-content for content styling
+
+https://gerrit.wikimedia.org/r/130507",1398813965,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 129567 merged by jenkins-bot:
+mw.ViewPageTarget: Use .mw-body-content for content styling
+
+https://gerrit.wikimedia.org/r/129567",1398810355,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130507 had a related patch set uploaded by Jforrester:
+mw.ViewPageTarget: Use .mw-body-content for content styling
+
+https://gerrit.wikimedia.org/r/130507",1398810240,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 129567 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Use .mw-content for content styling
+
+https://gerrit.wikimedia.org/r/129567",1398772850,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor:  Edit summary typed into the article instead of the Save dialog in Firefox,"Intention:
+Save a page.
+
+Steps to Reproduce:
+1. Rearrange a lot of text.
+
+2. Click the save button.
+
+3. Start typing the edit summary.
+
+Actual Results:  
+The edit summary appeared where I'd last been typing in the article, rather than in the Save dialog.
+
+I tried to reproduce it once, with no success.
+
+
+Reproducible: Couldn't Reproduce
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65222",1398648360,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-vugz2ayag65wyaecr7ve,task_description,resolved
+VisualEditor:  Edit summary typed into the article instead of the Save dialog in Firefox,"On reflection, I'm going to assume that this was caused by bug 65222 which is now resolved and so up-merging with that.
+
+*** This bug has been marked as a duplicate of bug 65222 ***",1401996489,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vugz2ayag65wyaecr7ve,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Formula
+3.Without closing the Math Inspector keep on pressing tab
+
+Observed Result:
+An error appears in the console:
+
+Uncaught  TypeError: Cannot read property 'start' of null
+
+See the screenshot attached
+
+Test Environment: https://en.wikipedia.org
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14000}",1398461400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_description,resolved
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,Verified the fix in production,1400011581,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,Verified the fix on test2,1399078153,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,Verified the fix on Betalabs,1398895353,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,"Change 129851 merged by jenkins-bot:
+Clear the focusedNode when the document is blurred
+
+https://gerrit.wikimedia.org/r/129851",1398469849,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,"Pressing tab actually blurs the surface, but blurring the surface doesn't clear the focusedNode highlighting, so I'm fixing that first.",1398468542,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error","Steps to Reproduce:
+1. Open any page in VisualEditor.
+
+2. Go to Insert > Reference to add a reference.  Do NOT click inside the reference box.
+
+3. Go to Insert > Template to add a template.
+
+
+
+Actual Results:  
+You can't add a template, you can't exit the dialog, you can't do anything except close the browser tab and lose all of your work.
+
+
+Reproducible: Always
+
+This cannot be reproduced in Safari.  This cannot be reproduced if you first click inside the reference box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398443040,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_description,resolved
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Verified the fix in production,1400012136,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Verified the fix on test2,1399405833,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error","(In reply to Rainer Rillke @commons.wikimedia from comment #4)
+> Where is the gerrit change?
+
+https://gerrit.wikimedia.org/r/#/c/129806/ makes sure the tools correctly initialize as disabled if the initial selection is null
+
+https://gerrit.wikimedia.org/r/#/c/130262/ makes sure the selection isn't 0,0 the second time you open the reference dialog",1399067016,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Where is the gerrit change?,1399066128,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",*** Bug 64601 has been marked as a duplicate of this bug. ***,1399065928,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Verified the fix in Betalabs,1398896444,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Fixed in the Firefox-selection change Ed wrote.,1398889785,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398377400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j4en6ingifxpa67vre45,task_description,resolved
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,Moved to a different bug.,1412802831,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,This is again happening on Betalabs,1412738904,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,Verified the fix in production,1399067933,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,Verified the fix in test2,1399067406,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Change 130804 merged by Catrope:
+Always fix up selection after ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/130804",1398907814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Change 130804 had a related patch set uploaded by Catrope:
+Always fix up selection after ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/130804",1398907631,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,Verified the fix in Betalabs with Firefox 27.0.1,1398889730,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Change 130262 merged by jenkins-bot:
+Always fix up selection after ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/130262",1398731458,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Change 130262 had a related patch set uploaded by Esanders:
+Always fix up selection on after ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/130262",1398730973,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Reference
+3.Type something fast inside the reference dialog box
+
+Observed Result:
+The first character of the text moves to the next line in reference dialog box
+
+Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5",1398377638,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Created attachment 15208
+Screenshot
+
+**Attached**: {F13881}",1398377616,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression wmf2] Loading spinner appears in the Media Settings dialog while loading it for the first time,"screenshot of the loading spinner
+
+There is a loading spinner appears on the Media Settings dialog box when I try to load it for the first time in a page.
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13831}",1398364020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vfdslw5rczsnlnpgu752,task_description,invalid
+VisualEditor: [Regression wmf2] Loading spinner appears in the Media Settings dialog while loading it for the first time,Expected behaviour.,1398365417,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vfdslw5rczsnlnpgu752,task_subcomment,NA
+VisualEditor: Snowmen inserted (or other bad breakage) with certain easy combinations of actions/keys that move the cursor out of the document,"<Krenair> Move the cursor to the end of a line before the start of a new section header, delete, enter, enter, up, delete, type a random character.
+<James_F> Backwards delete or forwards delete?
+<Krenair> Um. The delete next to 'Home' and 'End'
+<Krenair> not backspace
+<James_F> Forwards, then. :-)
+<James_F> Whee, snowmen.
+<James_F> I blame edsanders.
+<Krenair> observed on http://en.wikipedia.org/wiki/Hippeastrum_calyptratum, depending on what random character you try (I hit 'f'), stuff breaks in a difficult to explain but quite obvious
+<Krenair> especially if you do it twice to the same document
+<James_F> So the first thing that happens is that the cursor ends up outside of the document.
+<James_F> Which is Bad™.
+<James_F> Everything breaking after this is non-deterministic, but definitely also Bad™.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398297840,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qamxjhmoqqas27inzryu,task_description,resolved
+VisualEditor: Snowmen inserted (or other bad breakage) with certain easy combinations of actions/keys that move the cursor out of the document,"Change 129371 merged by jenkins-bot:
+Re-render selection after deleting
+
+https://gerrit.wikimedia.org/r/129371",1398310207,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qamxjhmoqqas27inzryu,task_subcomment,NA
+VisualEditor: Snowmen inserted (or other bad breakage) with certain easy combinations of actions/keys that move the cursor out of the document,"Change 129371 had a related patch set uploaded by Catrope:
+Rerender selection after deleting.
+
+https://gerrit.wikimedia.org/r/129371",1398310077,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qamxjhmoqqas27inzryu,task_subcomment,NA
+VisualEditor: Snowmen inserted (or other bad breakage) with certain easy combinations of actions/keys that move the cursor out of the document,"If you put the cursor at the end of a paragraph and press Delete, the cursor will go to the top left corner of the surface (range (0,0)). However, if the next thing after the cursor is not a paragraph (but e.g. a heading) this doesn't happen.
+
+Once the cursor is at (0,0) and you start typing, things break completely.",1398309644,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qamxjhmoqqas27inzryu,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in FireFox
+2.Go to Insert>Template
+3.Type something in the textbox to search for templates
+4.Now without selecting anything from the dropdown box, click on ""Add template""
+
+Observed Result:
+The dropbox for the search results gets sticked to the template dialog box 
+If you click on Show options button or just close the template dialog box and reopen again, it still stays
+
+
+This problem also exists for the search result dropbox for Redirect Target Page and Categories 
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13701}",1398295380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ousahplumt5sf7vusapd,task_description,resolved
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open",Verified in production,1400188852,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open",Verified the fix in test2,1400017549,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Change 131608 merged by jenkins-bot:
+Make autoFocus default to true
+
+https://gerrit.wikimedia.org/r/131608",1399324046,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Change 131608 had a related patch set uploaded by Catrope:
+Make autoFocus default to true.
+
+https://gerrit.wikimedia.org/r/131608",1399323887,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","For template, if you click on add template button quickly as soon as the dropbox appears you will be able to reproduce it.
+For Redirect Page and Categories, it can be reproduced in pretty straightforward way",1399076093,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open",This is still occurring in Betalabs and test2,1399068171,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Change 130767 merged by jenkins-bot:
+Auto-choose selected item when adding a template
+
+https://gerrit.wikimedia.org/r/130767",1398903238,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Change 130767 had a related patch set uploaded by Catrope:
+Auto-choose selected item when adding a template
+
+https://gerrit.wikimedia.org/r/130767",1398903085,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Created attachment 15189
+Redirect page
+
+**Attached**: {F13704}",1398295534,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Created attachment 15188
+category
+
+**Attached**: {F13702}",1398295457,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"<Krenair> The issue I get after adding ConfirmEdit to my wiki is ""Error: Unknown error"" when saving >_>
+<Krenair> {""visualeditoredit"":{""result"":""error"",""edit"":{""captcha"":{""type"":""simple"",""mime"":""text/plain"",""id"":""586723432"",""question"":""24+8""},""result"":""Failure""}}}
+<James_F> Hmm.
+<James_F> That kind of CAPTCHA isn't supported yet.
+<Krenair> meh. thought it would be something like that
+<James_F> You'd need to add it to the save dialog's logic.
+[...]
+<James_F> Krenair: It's worth adding support, feel free to make a bug (I don't have a list of CAPTCHA methods to support).
+
+I think at least Simple, Math, and Questy. Currently it looks like Fancy is supported though I haven't tested it
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398290340,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-upntlx7j3bdz3r52gesp,task_description,resolved
+VisualEditor: Add support for more types of ConfirmEdit captcha,From Alex: Yes.,1398978897,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"QuestyCaptcha and MathCaptcha both done too.
+
+Is Fancy sufficiently supported that we can close this?",1398893679,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"Change 129570 merged by jenkins-bot:
+Support QuestyCaptcha and (kind of) MathCaptcha
+
+https://gerrit.wikimedia.org/r/129570",1398893646,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"Change 129570 had a related patch set uploaded by Jforrester:
+Support QuestyCaptcha and (kind of) MathCaptcha
+
+https://gerrit.wikimedia.org/r/129570",1398372212,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"Change 129315 merged by jenkins-bot:
+Add support for SimpleCaptcha
+
+https://gerrit.wikimedia.org/r/129315",1398301771,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,Simple done. :-),1398301709,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"Change 129315 had a related patch set uploaded by Alex Monk:
+Add support for SimpleCaptcha
+
+https://gerrit.wikimedia.org/r/129315",1398292000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Screenshot
+
+I tried to save which was open for a long time (probably ~3-4 hrs)and got the following error in the console which stopped me from saving the edited content:
+
+Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13580}",1398210960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_description,resolved
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while",Verified the fix in production,1399052386,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while",Verified the fix in test2,1398990077,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Change 129326 merged by Catrope:
+Unbreak badtoken recovery on mobile
+
+https://gerrit.wikimedia.org/r/129326",1398295542,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Change 129326 had a related patch set uploaded by Catrope:
+Unbreak badtoken recovery on mobile
+
+https://gerrit.wikimedia.org/r/129326",1398295516,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Change 129243 merged by jenkins-bot:
+Unbreak badtoken recovery on mobile
+
+https://gerrit.wikimedia.org/r/129243",1398283165,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Change 129243 had a related patch set uploaded by Catrope:
+Unbreak badtoken recovery on mobile
+
+https://gerrit.wikimedia.org/r/129243",1398281605,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while",This looks like a bug in ve.init.mw.Target :(,1398279478,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+VisualEditor: [Regression] Can't remove annotation,"I challenge you!
+VEdit https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&oldid=65498176.
+Make the first line bold. Then un-bold it. I don't manage to.
+Win7, Vector, Chrome/FF.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398174780,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7xyquvj6hhetuc547oo3,task_description,resolved
+VisualEditor: [Regression] Can't remove annotation,"Change 129074 merged by jenkins-bot:
+Look for comparable annotations when toggling
+
+https://gerrit.wikimedia.org/r/129074",1398298640,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7xyquvj6hhetuc547oo3,task_subcomment,NA
+VisualEditor: [Regression] Can't remove annotation,"Change 129074 had a related patch set uploaded by Esanders:
+Look for comparable annotations when toggling
+
+https://gerrit.wikimedia.org/r/129074",1398210011,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7xyquvj6hhetuc547oo3,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"Before applying the changes
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Cite>Website/Book/Newspaper/Journal
+3.Add some optional parameters from the parameter list 
+4.Also add the parameter URL as an optional parameter
+5.Apply changes
+
+Observed Result:
+Observe that, before applying changes the parameter URL does not have a trash icon beside but the other optional parameter does.But, after applying the changes , the trash icon does appear for the parameter URL but not for the other one.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/21staprilchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14025}",1398108060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ntqqbxxddzdo7yltukgf,task_description,resolved
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"Change 129344 merged by jenkins-bot:
+Make citation dialog display like transclusion dialog in single mode
+
+https://gerrit.wikimedia.org/r/129344",1398301797,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"Change 129344 had a related patch set uploaded by Trevor Parscal:
+Make citation dialog display like transclusion dialog in single mode
+
+https://gerrit.wikimedia.org/r/129344",1398299815,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"This is only broken in the citation inspector, it works fine in the template inspector.",1398112544,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"It seems that the logic here is that:
+* When creating a new citation, none of the default parameters can be removed
+* When inspecting an existing citation, only the first (topmost) parameter can be removed
+* After adding a new parameter, only that parameter can be removed",1398112378,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"Created attachment 15151
+After applying changes
+
+**Attached**: {F14026}",1398108328,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Current extension repositories have REL1_23 branch, but it was created when REL1_22 was created too, so basically it's outdated.
+
+Examples:
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FCite.git
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FImageMap.git
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FCheckUser.git
+
+They have REL1_23 updated as of 22-10-2013
+
+I've only found one exception, though:
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FWidgets.git
+
+
+One particular change introduced on 1.23 release was the migration from PHP to JSON files for i18n. I think all the extensions were migrated to JSON files in master, but REL1_23 still doesn't have that change.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67270",1398010200,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-crppoo23swkvxppmtyyo,task_description,resolved
+Update branches in mediawiki/extensions/* for REL1_23,"Thanks @hashar!
+
+`defaultbranch` has since been removed from `.gitreview` (so now it submits to the upstream branch by default), so this is not an ongoing problem.",1485543614,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,thanks!,1485532627,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"For Bundled extensions:
+
+for ext in Cite ConfirmEdit Gadgets ImageMap InputBox Interwiki LocalisationUpdate Nuke ParserFunctions PdfHandler Poem Renameuser SpamBlacklist SyntaxHighlight_GeSHi TitleBlacklist WikiEditor; do echo -n ""$ext ""; git -C $ext show REL1_23:.gitreview|grep defaultbranch; done;
+
+|Cite | defaultbranch=master
+|ConfirmEdit | defaultbranch=REL1_23
+|Gadgets | defaultbranch=master
+|ImageMap | defaultbranch=master
+|InputBox | defaultbranch=master
+|Interwiki | defaultbranch=master
+|LocalisationUpdate | defaultbranch=master
+|Nuke | defaultbranch=master
+|ParserFunctions | defaultbranch=master
+|PdfHandler | defaultbranch=master
+|Poem | defaultbranch=master
+|Renameuser | defaultbranch=master
+|SpamBlacklist | defaultbranch=master
+|SyntaxHighlight_GeSHi | defaultbranch=master
+|TitleBlacklist | defaultbranch=master
+|WikiEditor | defaultbranch=master
+
+Fixed them all.
+
+I also fixed extensions that had recent changes.
+
+So it is mostly done. Given the traffic on `REL1_23` I don't think it is worth fixing all the rest.
+",1485514996,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334546 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334546]]",1485514960,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334546 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334546]]
+",1485514957,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334545 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334545]]",1485514911,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334545 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334545]]
+",1485514908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334544 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334544]]",1485514859,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334544 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334544]]
+",1485514856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334543 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334543]]",1485514822,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334543 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334543]]
+",1485514819,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334542 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334542]]",1485514791,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334542 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334542]]
+",1485514780,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334540 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334540]]",1485514699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334539 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334539]]",1485514697,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334538 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334538]]",1485514694,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334537 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334537]]",1485514692,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334536 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334536]]",1485514690,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334535 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334535]]",1485514688,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334534 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334534]]",1485514686,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334533 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334533]]",1485514684,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334532 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334532]]",1485514682,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334531 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334531]]",1485514680,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334530 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334530]]",1485514678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334529 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334529]]",1485514676,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334528 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334528]]",1485514674,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334527 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334527]]",1485514671,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334526 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334526]]",1485514669,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334540 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334540]]
+",1485514248,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334539 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334539]]
+",1485514245,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334538 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334538]]
+",1485514242,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334537 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334537]]
+",1485514239,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334536 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334536]]
+",1485514235,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334535 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334535]]
+",1485514232,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334534 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334534]]
+",1485514230,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334533 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334533]]
+",1485514227,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334532 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334532]]
+",1485514224,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334531 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334531]]
+",1485514221,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334530 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334530]]
+",1485514218,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334529 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334529]]
+",1485514215,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334528 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334528]]
+",1485514211,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334527 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334527]]
+",1485514209,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334526 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334526]]
+",1485514206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"The initial requests was to bump MediaWiki extensions REL1_23 branches and I guess all the bump that were required have been done quite quickly. So that is essentially done.
+
+
+The task apparently was left open to update `.gitreview` files. From July 2014 comment:
+
+>>! In T66157#704385, @Tgr wrote:
+> Not sure, if this is a bug in the one-off update process, or something that is generally not handled when creating new versions of extensions, but the .gitreview file in the root extension folder should have defaultbranch=REL1_23 but it has defaultbranch=master instead. (I have run into this in MultimediaViewer and UploadWizard; I assume it's the same for all others.)
+
+I checked extensions from mediawiki/extensions.git with:
+
+   git submodule foreach 'git show origin/REL1_23:.gitreview|grep defaultbranch||:'
+
+A wide range of them still have a .gitreview file with `defaultbranch=master`
+
+
+Looking in Gerrit for [[ https://gerrit.wikimedia.org/r/#/q/branch:REL1_23+project:%255Emediawiki/extensions/.*+NOT+project:%255Emediawiki/extensions/BlueSpice.* | branch:REL1_23 project:^mediawiki/extensions/.* NOT project:^mediawiki/extensions/BlueSpice.* ]] there are a few repo still active. And the .gitreview files are wrong :(
+
+
+",1485513144,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"On my radar, but unsure of exact situation anymore. @MarkAHershberger can you give an update on this task?",1465936763,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Moving this into RelEng's orbit more clearly; however, I imagine this isn't going to get done given it's been two years, and can just be closed as Declined or somesuch?",1465833665,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,I'll use this one.,1412864239,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"hexmode:
+> Are you going to use this bug to track that or open a new one?",1412767995,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Mark A. Hershberger from comment #28)
+> (In reply to Tisza Gergő from comment #27)
+> > Not sure, if this is a bug in the one-off update process, or something that
+> > is generally not handled when creating new versions of extensions, but the
+> > .gitreview file in the root extension folder should have
+> > defaultbranch=REL1_23 but it has defaultbranch=master instead. (I have run
+> > into this in MultimediaViewer and UploadWizard; I assume it's the same for
+> > all others.)
+> 
+> This is something we should update our branching script to take care of.
+
+Are you going to use this bug to track that or open a new one? Just don't want this to be lost in the aether...",1411592480,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Tisza Gergő from comment #27)
+> Not sure, if this is a bug in the one-off update process, or something that
+> is generally not handled when creating new versions of extensions, but the
+> .gitreview file in the root extension folder should have
+> defaultbranch=REL1_23 but it has defaultbranch=master instead. (I have run
+> into this in MultimediaViewer and UploadWizard; I assume it's the same for
+> all others.)
+
+This is something we should update our branching script to take care of.",1411409718,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Not sure, if this is a bug in the one-off update process, or something that is generally not handled when creating new versions of extensions, but the .gitreview file in the root extension folder should have defaultbranch=REL1_23 but it has defaultbranch=master instead. (I have run into this in MultimediaViewer and UploadWizard; I assume it's the same for all others.)",1406140429,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Fixed the ones in Comment 19.  Emailed a couple of q's to developers about the right revision to use, but it should be fixed now.",1404535834,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,*** Bug 67270 has been marked as a duplicate of this bug. ***,1404240941,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,The upload wizard case is fixed by https://gerrit.wikimedia.org/r/141586,1403562681,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Mark A. Hershberger from comment #16)
+> After looking through the bugs with fixes for UW, I found the following
+> three that seem like good candidates for backports:
+> 
+> Bug #54750 - UploadWizard allows two different files with same name at same
+> time
+> Bug #64067 - Pg Support
+> Bug #65406 - Flikr support
+
+Agreed, these are good candidates for backport. None of them are critical though.
+
+> Without more information, it is impossible to tell if fixing these will
+> address comment #12:
+> > UploadWizard is also affected by this, and as a result it is completely
+> > broken on 1.23.
+
+That would be addressed by moving all the missing commits (between 2013-10-24 and 2014-04-10) into REL1_23. Specifically, UW is broken because this commit from 2013 December is missing:
+http://git.wikimedia.org/commit/mediawiki%2Fextensions%2FUploadWizard/8bd13ac4317f48336f90a39723d142628eb906e9",1403417575,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Mark A. Hershberger from comment #21)
+> Others, like WikimediaMessages, suffer from the problem of
+> d373fd87b17bfb67f6616011ec1faa2531e58878 -- where the committer ""This, that
+> and the other"" made a commit indicating ""Update for release of MW 1.23""
+> without merging it with REL1_23 or requesting a backport.
+
+I don't think that patch needs to be backported, as the change is only relevant to mediawikiwiki, which is on 1.24wmfX by now.
+
+Since WikimediaMessages is a WMF-only extension I don't understand why it needs release branches in the first place.",1403406168,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Looks like UW -- and others branched before April 22 -- would benefit from a bit of work.
+
+Others, like WikimediaMessages, suffer from the problem of d373fd87b17bfb67f6616011ec1faa2531e58878 -- where the committer ""This, that and the other"" made a commit indicating ""Update for release of MW 1.23"" without merging it with REL1_23 or requesting a backport.",1403401254,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Number of extensions with last commit on REL1_23 that was in April and the message was ""Localisation updates from http://translatewiki.net."" or ""Update i18n shim"": 470
+
+The extensions on comment #19 all had the last message ""Localisation updates..."" except for SyntaxHighight_GeSHi and TwnMainPage.
+
+
+Remaining extensions:
+
+BlueSpiceExtensions REL1_23 57ae783 Tue Apr 8 11:20:14 2014 +0200 Fix spelling: occurred
+CategoryTree REL1_23 c7333ea Fri Jun 6 11:44:02 2014 +0200 Register CategoryTreeMagic from global scope instead of setup
+Collection REL1_23 bf7c4b9 Thu Apr 24 20:52:39 2014 +0100 Fatal error: Unsupported operand types in Collection.body.php
+ConfirmAccount REL1_23 e4f00be Tue Apr 22 15:09:02 2014 +0000 Add support for request account link
+ConfirmEdit REL1_23 0c63352 Mon Apr 7 19:25:45 2014 +0200 SimpleCaptcha: Move the equals sign inside the <label/>
+DPLforum REL1_23 01211c5 Fri Jun 6 17:32:19 2014 +0300 Fix DPLforum b0rkage.
+DataTransfer REL1_23 24f7782 Tue Jun 17 14:00:56 2014 +0200 Fix incorrect path in $wgMessagesDirs
+Disambiguator REL1_23 cf11744 Fri May 9 19:04:52 2014 +0100 Fix table prefixing in SpecialDisambiguationPages
+Math REL1_23 d0e998f Wed Apr 16 19:39:10 2014 -0700 Simplify VE inspector code by extending new MWLiveExtensionInspector
+MobileFrontend REL1_23 984e276 Mon May 12 14:29:25 2014 -0700 Fix XSS in section handling
+Nuke REL1_23 ba618ff Thu Jun 5 14:17:17 2014 +0100 chmod -x Nuke.alias.php Nuke_body.php Nuke.hooks.php Nuke.i18n.php Nuke.php SpecialNuke.php
+NumberFormat REL1_23 70be63c Mon Jun 16 21:13:13 2014 +0600 fix bug with negative numbers (version 0.8.0)
+PagedTiffHandler REL1_23 1e2be08 Tue Apr 22 09:34:03 2014 +0200 mark method visibleMetadataFields as public
+ProofreadPage REL1_23 86fa295 Tue Apr 15 21:01:56 2014 +0200 Fills $params to recursive calls of preloadTransform
+VisualEditor REL1_23 82dc0cb Wed May 21 09:33:19 2014 -0700 [browser test] Dismiss new confirm dialog
+Wikibase REL1_23 d2ed0cc Mon Apr 14 21:13:23 2014 +0000 Merge ""Add documentation for badgeItems setting on repo""",1403400384,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Extensions that look like they were branched on Oct 24:
+
+SolrStore REL1_23 5dabd1e Thu Oct 24 20:50:10 2013 +0000
+SpamBlacklist REL1_23 d6bd4c1 Thu Oct 24 20:50:16 2013 +0000
+SphinxSearch REL1_23 4a24249 Thu Oct 24 20:50:22 2013 +0000
+SubPageList REL1_23 a68966d Thu Oct 24 20:50:26 2013 +0000
+Sudo REL1_23 98bd893 Thu Oct 24 20:50:33 2013 +0000
+SyntaxHighlight_GeSHi REL1_23 2f064f4 Thu Oct 24 05:51:03 2013 +0000
+TemplateData REL1_23 26dacfc Thu Oct 24 20:50:37 2013 +0000
+TemplateSandbox REL1_23 1e880cc Thu Oct 24 20:50:40 2013 +0000
+Thanks REL1_23 22333e0 Thu Oct 24 20:50:46 2013 +0000
+ThrottleOverride REL1_23 e122ac6 Thu Oct 24 20:50:50 2013 +0000
+TimedMediaHandler REL1_23 7bd2b47 Thu Oct 24 20:50:54 2013 +0000
+Translate REL1_23 dfee4f4 Thu Oct 24 20:51:04 2013 +0000
+TranslateSvg REL1_23 5d30452 Thu Oct 24 20:51:11 2013 +0000
+TranslationNotifications REL1_23 5537a12 Thu Oct 24 20:51:18 2013 +0000
+TwnMainPage REL1_23 016ea86 Thu Oct 24 21:19:02 2013 +0000
+TwoFactorAuthentication REL1_23 e2fb0cc Thu Oct 24 20:51:31 2013 +0000
+UploadWizard REL1_23 9b39bd9 Thu Oct 24 20:51:37 2013 +0000
+Validator REL1_23 3c3997a Thu Oct 24 20:51:44 2013 +0000",1403399010,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Created attachment 15695
+differences between bundled version of spamblacklist in 1.22 and 1.23
+
+I only see l10n diffs for the bundled versions of SpamBlacklist, but they aren't the same.
+
+$ git log -1 --pretty=format:""%h%x09%an%x09%ad"" origin/REL1_23
+d6bd4c1 Translation updater bot Thu Oct 24 20:50:16 2013 +0000
+$ git log -1 --pretty=format:""%h%x09%an%x09%ad"" origin/REL1_22
+f91ad56 Translation updater bot Tue Oct 22 19:21:30 2013 +0000
+
+So, year, not the right place for a branch, but not the same thing. No clue yet why this happened.
+
+**Attached**: {F13932}",1403385148,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"non-l10n changes in UploadWizard since it was branched: https://gerrit.wikimedia.org/r/#/q/status:merged+project:mediawiki/extensions/UploadWizard+branch:master+-owner:L10n-bot,n,z",1403383468,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(Missed a couple of lines for the above script bit:
+  rel123=`git log -1 --oneline origin/REL1_23 2>&1`
+  rel122=`git log -1 --oneline origin/REL1_22 2>&1`
+)
+
+UploadWizard was branched on 2014-Apr-14.  Some bugs (bug #47161, bug #53245, bug #40147, bug #64908, bug #63921, bug #64067, bug #64883 and others below) were addressed with patches but no indication was made that a backport should be considered.
+
+After looking through the bugs with fixes for UW, I found the following three that seem like good candidates for backports:
+
+Bug #54750 - UploadWizard allows two different files with same name at same time
+Bug #64067 - Pg Support
+Bug #65406 - Flikr support
+
+Without more information, it is impossible to tell if fixing these will address comment #12:
+> UploadWizard is also affected by this, and as a result it is completely
+> broken on 1.23.",1403383066,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Comment on attachment 15693
+Submodules under extensions w/o commits for 1.23
+
+The following script was used to create this file:
+
+ lines=`git log --oneline --before 2014-04-10 --after 2013-10-10 | wc -l`
+ branch123=`git branch -a | grep origin/REL1_23 | wc -l`
+ branch122=`git branch -a | grep origin/REL1_22 | wc -l`
+ echo REL1_23: $branch123 REL1_22 $branch122 lines $lines
+ if [ ""$lines"" -eq ""0"" -a ""$rel123"" == ""$rel122"" ]; then
+    echo REL1_23 == REL1_22 for $ext
+    echo $ext >> /tmp/122=123
+ fi",1403381195,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Created attachment 15693
+Submodules under extensions w/o commits for 1.23
+
+This file was generated by using an up-to-date extensions checkout (with updates submodules) and listing those submodules without any commit between 2014-04-10 (when REL1_23 was created) and 2013-10-10 (~when REL1_22 was created).  This will help determine when REL1_22 should be the same as REL1_23.
+
+**Attached**: {F13931}",1403381064,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Greg / hexmode / Markus:  Will anybody fix this? It's been open for two months and creates followup issues, confusion, brokenness (bug 66866).",1403264281,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"UploadWizard is also affected by this, and as a result it is completely broken on 1.23.",1403123732,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"It looks like some extensions including SyntaxHighlight_GeSHi and SpamBlacklist were not fixed, and as a result the 1.22 versions of these two extensions are in the 1.23.0 tarball.",1402006976,PHID-USER-7ggbl2sm3bxckkmp6uw3,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,Wrote a script to remove the faulty REL1_23 branches (since I couldn't just push a new one).  Should all be fixed now.,1398103255,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,Fixed BlueSpiceFoundation,1398093136,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Fixed those in comment #0, looking for more problems.",1398092244,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"It looks like some of the problem is confusion between gerrit and gitblit.  For example, https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FSemanticMediaWiki.git shows REL1_23 on 2013-10-24.
+
+A fresh checkout from gerrit, though, shows the last commit on REL1_23 to be 26923ba5d306b24afe3e8d71f3f065139fd593c6 on 2014-04-14.
+
+Hmmm, and part of what I'm running into here is caching.  Opening the branch listing in a new browser shows what I expect.
+
+Another part of the problem is that I did initially make a mistake of branching the wrong code.  When I discovered that I got a pointer from Chad on how to fix the problem.  Evidently, though, this happened in more places than I realized.",1398091152,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Like I say, ProofreadPage was massively out of date too. Now fixed though",1398090274,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #0)
+> One particular change introduced on 1.23 release was the migration from PHP
+> to JSON files for i18n. I think all the extensions were migrated to JSON
+> files in master, but REL1_23 still doesn't have that change.
+
+Any extensions that have i18n files will need to be updated, but some, like Auth_remoteuser, are fine as is.
+
+Thank you for pointing out this problem before the release!",1398089169,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Mark A. Hershberger from comment #3)
+> That is, the dates you see on the branch page are the dates of the last
+> commit on that branch, not when the branch was made.
+> 
+> I created most of these REL1_23 branches last week.
+
+That doesn't seem right. As I said in comment #0, a lot of extensions were changed to have i18n messages in JSON files instead of PHP, and that was done weeks before REL1_23 was branched on master (it's in REL1_23 in core). But REL1_23 on the extensions I've linked as example doesn't include this change, among others that were merged on master after October 2013.
+
+I've manually checked some of those extensions, downloading from git for that branch name and they aren't migrated, while if I switch to master they have the new JSON files.",1398088401,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"If you look at Auth_remoteuser (https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FAuth_remoteuser.git), you'll see that REL1_21, REL1_22, and REL1_23 were all apparently branched when REL1_20 was created.
+
+From this I conclude that there were no changes on master between the time that REL1_20 was created and when REL1_23 was created.  And the history seems to confirm this: https://git.wikimedia.org/log/mediawiki%2Fextensions%2FAuth_remoteuser.git/refs%2Fheads%2Fmaster
+
+That is, the dates you see on the branch page are the dates of the last commit on that branch, not when the branch was made.
+
+I created most of these REL1_23 branches last week.",1398087801,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"I fixed ProofreadPage by having Chad enable force push, and pushing to update the remote REL1_23 branch.
+
+
+Why were the REL1_23 branches created at the branching point of REL1_22? :/",1398084051,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"While we're on it, could please whoever is in charge of releasing new MediaWiki versions, add also a note to check extension branches to the steps to create a new release? Every major release since we're on git have the same problem!! (usually REL1_XX branch is not created when the new release is done in core)
+
+See also bug 48837",1398010764,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+VisualEditor: Deleting a paragraph separator and subsequently typing any character messes up the page,"Steps to reproduce:
+
+1. Go to (say) https://en.wikipedia.org/w/index.php?title=Visual_editor&veaction=edit
+
+2. Place the cursor after the end of a paragraph (e.g. after the full stop in ""editors are."")
+
+3. Hit the delete key to merge the paragraph with the subsequent one.
+
+4. Type any character (a letter, blank, etc.)
+
+Result: Chaos ;) - large swaths of text are deleted, and (apparently) random characters appear near the beginning of the page.
+
+Reproduced in Chromium (Version 33.0.1750.152) and Firefox (28.0).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62333",1397889240,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-wbcmbobk54vghobxtvq5,task_description,resolved
+VisualEditor: Deleting a paragraph separator and subsequently typing any character messes up the page,"Yes, works for me too now in Chromium and Firefox.",1402354099,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-wbcmbobk54vghobxtvq5,task_subcomment,NA
+VisualEditor: Deleting a paragraph separator and subsequently typing any character messes up the page,"Works for me, probably resolved at some point in the last couple of months.",1402312928,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wbcmbobk54vghobxtvq5,task_subcomment,NA
+VisualEditor: [Regression] Citation dialog does not focus correct field when adding a new parameter,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a Cite option like Cite Website/Cite Journal
+3.Add some value for a parameter
+4.Click on ""Add Parameter""
+5.Select a parameter
+
+Observed Result:
+
+The cursor instead of moving to the new parameter, stays at the last edited parameter box
+
+
+Test Environment:  http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397846160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5yohjyriweszqbp34vz6,task_description,resolved
+VisualEditor: [Regression] Citation dialog does not focus correct field when adding a new parameter,Verified the fix on production,1400011923,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5yohjyriweszqbp34vz6,task_subcomment,NA
+VisualEditor: [Regression] Citation dialog does not focus correct field when adding a new parameter,Verified the fix on Betalabs,1399069800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5yohjyriweszqbp34vz6,task_subcomment,NA
+VisualEditor: [Regression] Citation dialog does not focus correct field when adding a new parameter,*** Bug 64201 has been marked as a duplicate of this bug. ***,1398112734,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5yohjyriweszqbp34vz6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a citation or a reference
+
+Observed Result:
+The cursor jumps to the beginning of the document 
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397693880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yarhuzhed4wqvpw62gpb,task_description,resolved
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,Verified the fix in production (en.wiki),1404767619,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"So, this issue did get re-introduced in wmf 10, and then got somehow resolved in wmf 11, Because I am getting it in production running wmf 10 but not on test2 running wmf 11.
+Therefore , I am changing the target milestone accordingly.",1403897953,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"(In reply to Ed Sanders from comment #9)
+> Works in master.
+
+Doesn't work in Beta Labs, which is running master AFAICT.",1403291952,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,Works in master. Deployment issue?,1403291406,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,This bug has been reborn in wmf 10,1403289668,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,Verified on betalabs for Cite options too,1398189179,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,Verified by adding template in test2,1398124127,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Change 127698 merged by Catrope:
+Add focusing state flag to ce.Surface when programatically focusing
+
+https://gerrit.wikimedia.org/r/127698",1398119444,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Change 127698 had a related patch set uploaded by Catrope:
+Add focusing state flag to ce.Surface when programatically focusing
+
+https://gerrit.wikimedia.org/r/127698",1398109444,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Change 127136 merged by jenkins-bot:
+Add focusing state flag to ce.Surface when programatically focusing
+
+https://gerrit.wikimedia.org/r/127136",1398107342,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Change 127136 had a related patch set uploaded by Esanders:
+Add focusing state flag to ce.Surface when programatically focusing
+
+https://gerrit.wikimedia.org/r/127136",1397764749,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,This happens after adding a template too.,1397759470,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open any page with mobile VE
+2.Add a text
+3.Save the page 
+4.Reopen the page
+5.Go to the next line of the text you added in step 2
+6.Start typing something
+
+Observed Result:
+The following error appears in the console
+
+Uncaught TypeError: Cannot read property 'nextSibling' of undefined
+
+See the screenshot attached
+
+Test Environment:http://en.m.wikipedia.beta.wmflabs.org/
+Page:http://en.m.wikipedia.beta.wmflabs.org/wiki/0.4040571254571662?title=0.4040571254571662&campaign=random#editor/0
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13635}",1397686200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atiq5mebijzmzfpmqye2,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,Verified the fix in: https://en.m.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/Sandbox,1398379043,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,Verified the fix on test2,1398127291,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 127380 merged by jenkins-bot:
+Also destroy target when exiting without saving changes
+
+https://gerrit.wikimedia.org/r/127380",1398120865,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 127380 had a related patch set uploaded by Jforrester:
+Also destroy target when exiting without saving changes
+
+https://gerrit.wikimedia.org/r/127380",1397859900,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 127364 merged by jenkins-bot:
+Also destroy target when exiting without saving changes
+
+https://gerrit.wikimedia.org/r/127364",1397856078,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 127364 had a related patch set uploaded by Catrope:
+Also destroy target when exiting without saving changes
+
+https://gerrit.wikimedia.org/r/127364",1397853717,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 126881 merged by jenkins-bot:
+Destroy the VE target after saving
+
+https://gerrit.wikimedia.org/r/126881",1397695959,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 126881 had a related patch set uploaded by Catrope:
+Destroy the VE target after saving
+
+https://gerrit.wikimedia.org/r/126881",1397694773,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,"Screenshot
+
+Steps to reproduce:'
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Click on ""Show options""
+
+Observed Result
+The template icon and the trash icon is overlapping with ""Add template"" button
+The NEw template heading is appearing below the textbox
+
+Try to add a content/parameter its broken for them too
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13598}",1397677140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_description,resolved
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,Verified the fix on production,1398385885,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,verified the fix on test 2,1397862572,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,Verified the fix on Betalabs,1397759374,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,"Change 126869 merged by jenkins-bot:
+Followup 099f26ec: fix $content in FieldsetLayout
+
+https://gerrit.wikimedia.org/r/126869",1397698884,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,"Change 126869 had a related patch set uploaded by Catrope:
+Followup 099f26ec: fix $content in FieldsetLayout
+
+https://gerrit.wikimedia.org/r/126869",1397690635,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,"Created attachment 15121
+parameter textbox
+
+**Attached**: {F13599}",1397677210,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: Copy-Paste of a block of HTML disables all further copy-paste of anything: FF28 on Linux,"* Open https://www.mediawiki.org/w/index.php?title=Parsoid/Deployments&oldid=959448&veaction=edit
+* Copy the section starting @ ""Monday, April 14, 2014 around 1pm PST : Deployed fba548cb"" including the list upto the next section
+* Try pasting it -- nothing gets pasted.
+* Now try copy-pasting othe things (even simple strings) .. everything fails.
+
+Can consistently reproduce this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397671800,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-u7s5e2g4bwlbc7qkpfjc,task_description,resolved
+VisualEditor: Copy-Paste of a block of HTML disables all further copy-paste of anything: FF28 on Linux,"It's almost certainly because the copy-paste code fatals on come content currently, and doesn't bring itself back; up-merging into bug 66229 which asks for this to be fixed.
+
+*** This bug has been marked as a duplicate of bug 66229 ***",1402505914,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u7s5e2g4bwlbc7qkpfjc,task_subcomment,NA
+VisualEditor: Copy-Paste of a block of HTML disables all further copy-paste of anything: FF28 on Linux,Works for me.,1402501178,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-u7s5e2g4bwlbc7qkpfjc,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","**Author:** `swalling`
+
+**Description:**
+VE's edit surface has a body font size of 0.8em (equals 13px) which mismatches with the new default body font size (0.875em, which translates to 14px on Chrome and Firefox on most systems). The same is true for line-height, which is now 1.6em for body content. 
+
+We should make sure the two are consistent. The body font stack and heading settings do get translated to VE edit mode correctly, so we're close. :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63540",1397610060,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dkzwbg45silmhmsouxdk,task_description,resolved
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 130481 merged by jenkins-bot:
+vector: Apply content text style via .mw-body-content instead of #bodyContent
+
+https://gerrit.wikimedia.org/r/130481",1398813972,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)",Will back-port to wmf2 at least.,1398804515,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 130481 had a related patch set uploaded by Jforrester:
+vector: Apply content text style via .mw-body-content instead of #bodyContent
+
+https://gerrit.wikimedia.org/r/130481",1398804386,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 129563 merged by jenkins-bot:
+vector: Apply content text style via .mw-body-content instead of #bodyContent
+
+https://gerrit.wikimedia.org/r/129563",1398804366,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 129563 had a related patch set uploaded by Krinkle:
+Make new styles target .mw-content instead of #bodyContent
+
+https://gerrit.wikimedia.org/r/129563",1398772993,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","I'm not quite sure about the pre-typograpy-refresh situation, but it shouldn't be to different from the curent.
+
+Here's the situation now . We have #mw-head-base (tabs and personal links) and #content (#firstHeading, #bodyContent, #catlinks and everything in between). Both have a base fontsize of 1em and left-margin of 10/11em. They need to match, no matter what, to align the tabs with the content part of the page.
+
+Fontsize isn't actually set until deep inside the various parts:
+#p-personal li {font-size: 0.75em;},
+div.portal div.body ul li {font-size: 0.75em;},
+div.vectorTabs li a {font-size: 0.8em;},
+and in #bodyContent {font-size: 0.875em;}
+
+The rest of the Vector layout relies on the base fontsize of 1em. If you must have 0.875em for #content, then the entire structure needs to be revised. So I don't know is VE can match the current situation, that would be the easiest way.",1398373392,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 129567 had a related patch set uploaded by Trevor Parscal:
+Use .mw-content for content styling
+
+https://gerrit.wikimedia.org/r/129567",1398371500,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","(In reply to Erwin Dokter from comment #5)
+> Just discovered that setting the 0.875em fontsize to #content instead of
+> #bodyContent messes with the layout of the entire page; the navigation bar
+> relies on the fontsize of #content to be 1em, otherwise it collapses.
+> 
+> To compensate, the left margin of #content would have to be modified from
+> 10/11em to 11.43/12.57em. That seems quite an unsightly hack with a
+> potential for alignment issues due to rounding errors.
+> 
+> Just so you know.
+
+Suggests that we should probably revisit the margins a little, but yes. :-(
+
+Can we get this fixed urgently? It's a quite disruptive regression for VisualEditor users.",1398363133,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Just discovered that setting the 0.875em fontsize to #content instead of #bodyContent messes with the layout of the entire page; the navigation bar relies on the fontsize of #content to be 1em, otherwise it collapses.
+
+To compensate, the left margin of #content would have to be modified from 10/11em to 11.43/12.57em. That seems quite an unsightly hack with a potential for alignment issues due to rounding errors.
+
+Just so you know.",1398275444,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","(In reply to Erwin Dokter from comment #2)
+> Both @body-line-height and @body-font-size are already applied to
+> #bodyContent (see bug 63731). Don't you mean they should be moved to
+> div#content instead, where everything else is defined?
+
+Sorry, yes. Corrected title.",1398114948,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)",*** Bug 64124 has been marked as a duplicate of this bug. ***,1397903906,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Both @body-line-height and @body-font-size are already applied to #bodyContent (see bug 63731). Don't you mean they should be moved to div#content instead, where everything else is defined?",1397903077,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","As discussed, we should apply the styling to bodyContent to affect other parts of the page like siteSub, contentSub, printfooter, catlinks, and also VE edit surface etc.",1397845166,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to page options
+3.Select Page Settings
+4.Go to Page options again
+5.Select Advanced Settings from the menu
+
+Observed Result:
+It navigates to the tab that was last opened but not to Advanced Settings
+
+Test Environment: https://test2.wikipedia.org/ and v
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1397608920,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oucacwo66k2ybwrotr5f,task_description,resolved
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,Verified the fix on production,1398386242,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,Verified the fix on test2,1397865593,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,Verified the fix on Betalabs,1397675730,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,"Change 126187 merged by jenkins-bot:
+Fix name of advanced settings page in open command
+
+https://gerrit.wikimedia.org/r/126187",1397617052,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,"Change 126187 had a related patch set uploaded by Alex Monk:
+Fix name of advanced settings page in open command
+
+https://gerrit.wikimedia.org/r/126187",1397610673,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Pull in Parsoid's new styling module so we don't need to duplicate locally,"Per bug 51245 Parsoid now has the start of a CSS module – gerrit 124785 – which we should pull into VE. Once we've done that we can start upstreaming a lot of our local CSS hacks into Parsoid and save the effort. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60017
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51245",1397606880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-msf2quw2wlciqweodnnt,task_description,resolved
+VisualEditor: Pull in Parsoid's new styling module so we don't need to duplicate locally,"Change 129810 merged by jenkins-bot:
+Pull in Parsoid's new styling module
+
+https://gerrit.wikimedia.org/r/129810",1398714784,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-msf2quw2wlciqweodnnt,task_subcomment,NA
+VisualEditor: Pull in Parsoid's new styling module so we don't need to duplicate locally,"Change 129810 had a related patch set uploaded by Jforrester:
+Pull in Parsoid's new styling module
+
+https://gerrit.wikimedia.org/r/129810",1398456948,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-msf2quw2wlciqweodnnt,task_subcomment,NA
+VisualEditor: Pull in Parsoid's new styling module so we don't need to duplicate locally,"So I think we need to:
+* Start depending on the Parsoid extension. (At the moment it's optional and improves performance.) James says this will break Vagrant installations.
+* Mark the VE RL module as depending on Parsoid's.",1397781167,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-msf2quw2wlciqweodnnt,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,"Intention:
+See if I could reproduce Alex's bug.  I could.
+
+Steps to Reproduce:
+1. Click http://en.wikipedia.beta.wmflabs.org/wiki/User:Whatamidoing_(WMF)/Sandbox?veaction=edit or open another page in VisualEditor.
+
+2. Click outside the main editing area.  For example, highlight part of the page title, or put the cursor in the search box.
+
+3. While your cursor is still outside the editing area, click the page options menu (three bars icon) and choose any item.  For example, choose ""Categories"".  (Perhaps you just used the search box to figure out how to spell the name of the category you're interested in adding, and that's why your cursor is in the search box.)
+
+Actual Results:  
+Nothing happens.  ""Switch to source editing"" is the only menu item that produces a response.
+
+Expected Results:  
+Normal editing behavior.  It doesn't matter where my cursor is placed for these items, so they shouldn't care.
+
+Reproducible: Always
+
+Confirmed in Safari 6 and Firefox 28 on Mac OS 10.8.5, and assumed to affect everything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63954",1397582280,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qvq2zj4itka6fwjddhwh,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1398380561,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,Verified the fix in test2,1397866304,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,Presuming that this is now FIXED.,1397600481,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,"Change 126058 merged by jenkins-bot:
+Use document direction when a fragment has a null range
+
+https://gerrit.wikimedia.org/r/126058",1397592134,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,"Change 126058 had a related patch set uploaded by Trevor Parscal:
+Use document direction when a fragment has a null range
+
+https://gerrit.wikimedia.org/r/126058",1397589656,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,CCing Roan - James mentioned earlier that he was working on something like this yesterday.,1397587203,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,"I found this on Chrome 33 on Ubuntu 13.10.
+
+Error if you try to open something like Page settings (or most other items on that list):
+Uncaught TypeError: Cannot read property 'start' of null
+ve.Document.selectNodes
+ve.ce.Document.getDirectionFromRange
+ve.ui.DialogAction.open
+ve.ui.Surface.execute
+ve.ui.Command.execute
+ve.ui.Tool.onSelect
+OO.ui.ToolGroup.onMouseUp
+OO.ui.PopupToolGroup.onMouseUp
+proxy
+jQuery.event.dispatch
+elemData.handle.eventHandle
+
+Error if you try to type in the main text editing area:
+Uncaught TypeError: Cannot call method 'isCollapsed' of null
+ve.ce.Surface.handleInsertion
+ve.ce.Surface.onDocumentKeyPress
+proxy
+ve.EventSequencer.onEvent
+(anonymous function)
+jQuery.event.dispatch
+elemData.handle.eventHandle",1397587114,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Reference
+3.Type something inside the reference dialog box
+
+Observed Result:
+As soon as you type the first word the first letter diappears.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397501340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_description,resolved
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Now , it does not look broken .Hence, marking it as Fixed.",1398889897,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,I am again getting this issue in Chrome in Betalabs.,1398884750,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,verified the fix in production for Chrome,1398378180,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 129323 merged by Catrope:
+Prevent SurfaceWidgets from focussing themselves
+
+https://gerrit.wikimedia.org/r/129323",1398295506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 129323 had a related patch set uploaded by Catrope:
+Prevent SurfaceWidgets from focussing themselves
+
+https://gerrit.wikimedia.org/r/129323",1398294927,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 129081 merged by jenkins-bot:
+Prevent SurfaceWidgets from focussing themselves
+
+https://gerrit.wikimedia.org/r/129081",1398283780,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 129081 had a related patch set uploaded by Esanders:
+Prevent SurfaceWidgets from focussing themselves
+
+https://gerrit.wikimedia.org/r/129081",1398212352,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Also the following errors appear on the console while trying to delete the texts inside the reference dialog box:
+TypeError: startNode is null
+Error: Unbalanced set of replace operations found
+Error: ve.dm.Document.getNodeFromOffset(): offset 3 is out of bounds",1398207479,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"For FireFox, I am getting this problem in a slightly different manner:
+Instead of getting missing the first letter of the first word you type inside reference dialog box , goes to the next line.",1398207135,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,Verified the fix in test2,1397865275,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,Verified the fix for the caption field in the Media Settings dialog in Betalabs,1397689160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 126855 merged by jenkins-bot:
+Also focus surface in media edit dialog
+
+https://gerrit.wikimedia.org/r/126855",1397686636,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 126855 had a related patch set uploaded by Catrope:
+Also focus surface in media edit dialog
+
+https://gerrit.wikimedia.org/r/126855",1397686418,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,This is now happening for the caption field inside Media Settings,1397681517,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,Verified the fix on Betalabs,1397678723,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 125911 merged by jenkins-bot:
+Focus the surface in the reference dialog after it opens
+
+https://gerrit.wikimedia.org/r/125911",1397674853,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 125911 had a related patch set uploaded by Catrope:
+Focus the surface in the reference dialog after it opens
+
+https://gerrit.wikimedia.org/r/125911",1397518093,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,With the reversion this should now be working again?,1397507631,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Correction:
+Observed Result:
+
+As soon as user types the first word, the first letter of it disappears.",1397501449,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression] Clicking out of inspector jumps selection back to inspected text,"If you click out of an inspector into some other text, it used to be that the cursor went to that text and stayed there, but now it jumps back to the text that was being inspected. I suspect this may have something to do with changes to ve.ui.DesktopContext. There seems to be a delay so maybe something's happening from a setTimeout( ..., 200 ) after the closing animation?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397496840,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bd4dgg3belnvzk5644rb,task_description,resolved
+VisualEditor: [Regression] Clicking out of inspector jumps selection back to inspected text,"Change 127805 merged by jenkins-bot:
+Prevent annotation inspector from updating selection if using DesktopContext#hide
+
+https://gerrit.wikimedia.org/r/127805",1398123996,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bd4dgg3belnvzk5644rb,task_subcomment,NA
+VisualEditor: [Regression] Clicking out of inspector jumps selection back to inspected text,"Change 127805 had a related patch set uploaded by Esanders:
+Prevent annotation inspector for updating selection if using DesktopContext#hide
+
+https://gerrit.wikimedia.org/r/127805",1398117872,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bd4dgg3belnvzk5644rb,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert a reference
+3.Type in something in the reference dialog box
+4.Save the page
+5.Reopen the page
+6.Open the reference
+
+
+Observed Result:
+There is no content in the reference dialog box
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1397239320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sfzqgeaol3scscbd2imq,task_description,resolved
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,Verified the fix on productionhttps://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1398386363,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,Verified the fix on test2,1397519598,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,"Change 125431 merged by jenkins-bot:
+Update VE core submodule to latest master (74353d9)
+
+https://gerrit.wikimedia.org/r/125431",1397517601,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,Verified the fix in Betalabs,1397505551,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,"Change 125431 had a related patch set uploaded by Jforrester:
+Update VE core submodule to latest master (74353d9)
+
+https://gerrit.wikimedia.org/r/125431",1397244788,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,*** Bug 63829 has been marked as a duplicate of this bug. ***,1397244708,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Try to open math inspector on betalabs:
+The following error appears on the console and the math function does not open up
+
+Uncaught TypeError: Cannot call method 'getModel' of undefined VM2690:273
+ve.ui.MWMathInspector.setup VM2690:273
+(anonymous function) VM2688:23
+proxy load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:10
+listenerWrapper VM2688:6
+oo.EventEmitter.emit VM2688:7
+(anonymous function) VM2688:20
+pollExternalStylesheets
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397156220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hl2jx7woen5yuyiqirv4,task_description,resolved
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 129623 merged by jenkins-bot:
+Update VE implementation to use model-only inspectors
+
+https://gerrit.wikimedia.org/r/129623",1398384517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 129623 had a related patch set uploaded by Jforrester:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/129623",1398384394,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,Verified the fix on production with Chrome and FF,1398378457,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,Verified the fix on test2,1398196713,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 126909 merged by jenkins-bot:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/126909",1397703693,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 126909 had a related patch set uploaded by Catrope:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/126909",1397703494,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,Verified the fix in Betalabs,1397693209,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 125933 merged by jenkins-bot:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/125933",1397604310,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 125933 had a related patch set uploaded by Esanders:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/125933",1397526851,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: Icons render weirdly in IE10,"how the ...
+
+In my Windows 7 VMWare machine the icons render strangely in the toolbar.  Image attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7
+
+**Attached**: {F13606}",1397082960,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-2falvdljg7ldqp2rj3l5,task_description,declined
+VisualEditor: Icons render weirdly in IE10,"I have, however, seen a number of interesting rendering problems in IE11. It seems like their hardware acceleration sometimes chokes on gradients or transitions or whatever it is that we do that it doesn't like, and you'll get things like black boxes or iframes being transparent while they should be opaque, or buttons appearing to be flat when they shouldn't be.",1409961040,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2falvdljg7ldqp2rj3l5,task_subcomment,NA
+VisualEditor: Icons render weirdly in IE10,Works fine for me in IE10.,1409960965,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2falvdljg7ldqp2rj3l5,task_subcomment,NA
+VisualEditor: [Regression] Back button in ?veaction=edit changes address bar but doesn't alter page state,"Forking from bug 43844. Not good.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1397067840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cpq7rrq57bxr73nzx4zb,task_description,resolved
+VisualEditor: [Regression] Back button in ?veaction=edit changes address bar but doesn't alter page state,"Change 125745 merged by jenkins-bot:
+Always replace state with VE tag when loading
+
+https://gerrit.wikimedia.org/r/125745",1397674211,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpq7rrq57bxr73nzx4zb,task_subcomment,NA
+VisualEditor: [Regression] Back button in ?veaction=edit changes address bar but doesn't alter page state,"Change 125745 had a related patch set uploaded by Alex Monk:
+Always replace state with VE tag when loading
+
+https://gerrit.wikimedia.org/r/125745",1397492637,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpq7rrq57bxr73nzx4zb,task_subcomment,NA
+VisualEditor: [Regression] Back button in ?veaction=edit changes address bar but doesn't alter page state,I think this is caused by Gerrit change 118357,1397083170,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cpq7rrq57bxr73nzx4zb,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"On http://parsoid.wmflabs.org/enwiki/User:Tamravidhir?oldid=603142295 , I see two images that look like:
+
+<figure><small><a href=""...""><img src=""..."" /></a><figcaption>Caption text</figcaption></small></figure>
+
+You can find them by opening that link in a browser and typing document.querySelectorAll('figure>small') in a console, then clicking on the result (Firebug) or right-clicking the result and choosing ""Reveal in elements panel"" (Chrome).
+
+Putting a <small> inside a <figure> tag but wrapped around a <figcaption> tag is a violation of the image spec (in addition to just being insane), which causes VisualEditor to get very confused and corrupt the image, which causes Parsoid to output [[undefined|NaNxNaNpx|right|link=]], see https://en.wikipedia.org/w/index.php?title=User:Tamravidhir&diff=603142575&oldid=603142295 . This is reminiscent of bug 62805 (NaNxNaNpx).
+
+The wikitext that triggers this is fairly complicated, and I haven't been able to isolate a test case locally. It seems to be something like:
+
+* '''Text'''
+<small>
+[[File:Foo|right|200px|Caption]]
+
+Text
+
+[[File:Foo|right|200px|Caption]]
+</small>
+* '''Text'''
+<small>
+etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1396894380,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_description,resolved
+Parsoid outputs <small> as child of <figure>,This is now fixed and will be deployed on Monday. Please reopen if you see this not fixed in production.,1438291859,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Change 215058 had a related patch set uploaded (by Subramanya Sastry):
+T65642: Additional scenarios dealing with treebuilder fixup
+
+[[https://gerrit.wikimedia.org/r/215058]]
+",1433177043,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"That patch also fixes your example from Comment 14:
+
+[subbu@earth lib] echo ""<small>[[File:Foo.jpg|right|300px]]</small>"" | node parse.js --wt2wt
+<small>[[File:Foo.jpg|right|300px]]</small>
+
+Okay, will revive it and try to get a resolution on it soon enough. I need to study behavior on more convoluted test cases and see what Tidy does and what we do now and see if I can fold that into this patch.",1413323636,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"(In reply to ssastry from comment #15)
+> Any thoughts about https://gerrit.wikimedia.org/r/#/c/162816/?
+
+I don't understand the patch very well, but the changes to the test cases look promising.",1413317924,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,Any thoughts about https://gerrit.wikimedia.org/r/#/c/162816/?,1413317657,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"This is still causing problems. See https://ru.wikipedia.org/?diff=66125825 for instance.
+
+$ echo ""<small>[[File:Foo.jpg|right|300px]]</small>"" | node tests/parse.js --wt2wt
+
+<small>[[File:Foo.jpg|right|300px|link=]]
+
+This seems to happen because of something similar to what I described in bug 66749 comment 7: there is a <small> inside a <figure>, which violates Parsoid's HTML spec, and causes a round-trip failure. Additionally, there's a frivolous <p><small></small></p> before and <p></p> after the image.",1413317084,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"See bug 66749 which appears to be a dup?
+
+Also, the WTS side of this ( https://gerrit.wikimedia.org/r/129818 ) never got finished/merged.",1403044473,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,Will close this .. Please reopen if this is not fixed post deploy tomorrow.,1399417225,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,This will be deployed on Wednesday.,1399298483,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Change 130109 merged by jenkins-bot:
+(Bug 63642): Cleanup treebuilder fixup of formatting elts.
+
+https://gerrit.wikimedia.org/r/130109",1399281146,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Change 130109 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 63642): Cleanup treebuilder fixup of formatting elts.
+
+https://gerrit.wikimedia.org/r/130109",1398706638,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Change 129818 had a related patch set uploaded by Cscott:
+WIP: WTS: Handle tag fixup that floats inside <figure>.
+
+https://gerrit.wikimedia.org/r/129818",1398458344,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"For the WTS case, it's probably sufficient to tweak the code that looks for the various bits of <figure> and ensure it skips over any extraneous <small>/<b>/<i>/<s>/<u> as direct children of <figure>.  That part wouldn't require a separate fixup pass.",1398455284,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Firefox fixes this up as follows:
+
+> div=document.createElement('div')
+> div.innerHTML = ""<p><small></p><figure><figcaption>foo</figcaption></figure</small>""
+> div.outerHTML
+""<div><p><small></small></p><figure><figcaption><small>foo</small></figcaption></figure></div>""
+
+But:
+> div.innerHTML = ""<p><small></p><figure><a href='xxx'><img></a><figcaption>foo</figcaption></figure></small>""
+> div.outerHTML
+""<div><p><small></small></p><figure><small><a href=""xxx""><img></a><figcaption>foo</figcaption></small></figure></div>""
+
+So it seems to be the <a> tag in particular which causes the treebuilder to resurface the <small> tag.  The same thing happens if <small> is <b> or <i> or <s> or <u>, but not <a>:
+
+> div.innerHTML = ""<p><a href=yyy></p><figure><a href='xxx'><img></a><figcaption>foo</figcaption></figure></a>""
+> div.outerHTML
+""<div><p><a href=""yyy""></a></p><figure><a href=""xxx""><img></a><figcaption>foo</figcaption></figure></div>""
+
+We might be able to handle this with a focused post-processing step which looks for <small>/<b>/<i>/<s>/<u> as the direct child of a <figure> and hoists the formatting safely inside the <figcaption>.  In theory we should have a similar check in WTS in case we get invalid HTML as input.",1397490798,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Reports from Roan on IRC:
+
+* Not very common, but seen on a few user pages.
+* This corrupts wikitext on save in pages where it is seen.
+* Community liasion wants this fixed in some fashion.
+* More important to protect content than provide editability.
+
+If possible, we should probably wrap such images with uneditable protection (mw:Placeholder) and deal with the larger issue later.",1397240855,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"node parse --trace html --dump dom:post-builder reveals that Parsoid generates a <p><small></p><figure>..</figure></small> (imagine them to be html tokens input to the HTML5 treebuilder) which the treebuilder helpfully fixes up to <p><small></small></p><figure><small>..</small></figure>
+
+But, the odd thing is that the tree builder does this only when this is nested inside the table. Not sure if that is a feature or a bug. To be tested in Firefox and Chrome.
+
+Replace <small> with <b>/<i>/.. and you see the same behavior. But, I think this is the same class of bugs around formatting tags wrapping certain kind of block tags and getting fixed up by HTML5 parsing semantics. In the case of unclosed tags, we have bug reports where a <s> or a <ul> formatting tag continues to the rest of the document (bug 50536, bug 57196). I am recording this info here for now. Unclear what the exact solution is for this here, but clearly, we need a generic solution for misnested formatting tags.",1396976815,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Reduced test case: Every newline in there is important to reproduce this.
+```
+{|
+|
+<small>
+[[File:Foo.jpg|right|Test]]
+</small>
+|}
+```",1433172542,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Reduced test case: Every newline in there is important to reproduce this.
+
+{|
+|
+<small>
+[[File:Foo.jpg|right|Test]]
+</small>
+|}",1396898674,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"(02:34:55 PM) RoanKattouw: This structure is in a table cell BTW
+(02:35:00 PM) RoanKattouw: It's like the 104th child of a <td>
+(02:35:08 PM) RoanKattouw: Mismatched tags seems plausible
+(02:35:15 PM) RoanKattouw: There's a +</div> elsewhere in the dirty diff",1396895764,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"I'm fairly certain that LinkHandler never outputs <small>, so my guess is that this is a foster-parenting bug.",1396895657,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,"**Author:** `richlv`
+
+**Description:**
+visual editor from git f8d56e6804a12248b485c2d3b49d4ff0ffa7220c
+
+opera 12.16 on linux.
+
+in the save form, minor edit & watching checkboxes can not be marked
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1396874100,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ovk5omihhahdt4qfvph7,task_description,declined
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,Not reproducible and no response from bug reporter :(,1410805662,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,"Can not reproduce using Opera 12.17 on Windows 7, on the page from comment 3. Clicking on both the checkboxes and their labels works as expected, checking the box.",1399407547,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,Not good.,1399404848,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,"**richlv** wrote:
+
+for the record, this still does not work for me at https://www.mediawiki.org/w/index.php?title=VisualEditor&veaction=edit - but i'll wait for 1.23 to be out before complaining more about it :)",1399403916,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,"**richlv** wrote:
+
+sorry, with ve currently not working with 1.22, i'll have to wait for the release of 1.23 to test this again",1399403311,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,It seems to work OK for me now – can you confirm?,1399307251,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"QUnit tests for jquery.makeCollapsible are often failing on Jenkins. I've seen this at least three times in the last week or so, most recently on https://gerrit.wikimedia.org/r/#/c/124051/ . Every time the failure was within the jquery.makeCollapsible tests (but I'm not entirely sure if on the same exact test).
+
+This might be related to the fake timers being used in them.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: major",1396723500,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-f627kqg22t3exoned4d4,task_description,resolved
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 145479 abandoned by Mattflaschen:
+Fix spurious QUnit failures related to fake timers
+
+Reason:
+I'm okay with throwing an error (which is already merged), rather than having the test runner work to clean it up.  The important thing is the test author/maintainer has a clear indication of the problem, which allows them to easily fix it.
+
+https://gerrit.wikimedia.org/r/145479",1405115464,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"I disabled the GuidedTour GUI that was triggering this during tests (1e37db808e1f9cc8daffb61e4303ce53d701e25a).  Krinkle's b90c69cdf70ae55a7ae608b074893d140d0a96b6 (""QUnit: Detect unfinished jQuery effects or ajax requests in teardown"") has been merged to core, which should detect similar issues in the future.
+
+I will abandon the other patch, since if isolation deficiencies (e.g. running effects queue) are fully detected and error'ed, the runner doesn't need to enforce that isolation.",1405115134,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 143481 abandoned by Krinkle:
+Use QUnit.asyncTest even for fake timers, to fix spurious failures
+
+Reason:
+See Ibada489a58295
+
+https://gerrit.wikimedia.org/r/143481",1405091263,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 145487 merged by jenkins-bot:
+Don't actually show guiders in unit tests
+
+https://gerrit.wikimedia.org/r/145487",1405086064,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"(In reply to Krinkle from comment #25)
+> Also, this really should've been a separate bug. The bug as reported was
+> fixed and affected core.
+
+The original symptoms appeared very close (not just ""it's something with timers and animations"", but specifically jquery.makeCollapsible).
+
+I didn't dive deeper to figure out the underlying interactions until later.",1405055330,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 145487 had a related patch set uploaded by Mattflaschen:
+Don't actually show guiders in unit tests
+
+https://gerrit.wikimedia.org/r/145487",1405045006,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Also, this really should've been a separate bug. The bug as reported was fixed and affected core. This looks similar (it's something with timers and animations), but a different exception is thrown, different unit tests are failing, and it's only affecting extensions (doesn't mean the bug isn;t in core, but it's a separate bug).
+
+This isn't a ""something is wrong with qunit and timers"" tracking bug.",1405043223,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"You were right, I didn't need to make it async.
+
+Side note, the SinonJS docs imply that useFakeTimers() uses the current date by default.  Unfortunately (this would have fixed half of my patch), this is not true, so I submitted a patch for those docs at https://github.com/sinonjs/sinon-docs/pull/2 .",1405040133,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 145479 had a related patch set uploaded by Mattflaschen:
+Fix spurious QUnit failures related to fake timers
+
+https://gerrit.wikimedia.org/r/145479",1405039965,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Turning the tests from sync to async in core is the functional equivalent of removing the assertion ""test framework works as expected"". It's like boldly removing unit tests or parser tests because when executed with a certain extension, they no longer match expected behaviour.
+
+I can reproduce this consistently but only with those extensions installed. With plenty of other extensions installed it works fine. I don't see anything obvious this extension that might cause it, but that wasn't the case earlier this year either and eventually we did find the problem there too.
+
+After static analysis yielded nothing, I turned to removing code locally until you find out what's causing it. Maybe it'll turn out to be a trigger that calls back into mediawiki-core, maybe not. But the surface layer triggering it isn't in core.",1404392948,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Doesn't look like we have a GettingStarted example yet, so:
+
+https://integration.wikimedia.org/ci/job/mwext-GettingStarted-qunit/58/consoleFull
+
+(Jul 3, 2014 12:13:51 AM per https://integration.wikimedia.org/ci/job/mwext-GettingStarted-qunit/58/)
+
+Seems to be the same set.  Again, jquery.color is the first error.
+
+If it affects any other extensions, please add.",1404350428,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"(In reply to Krinkle from comment #19)
+> Considering it is only affecting tests related to asynchronous Date
+> manipulation, I suspect one or more of the extensions the Growth team
+> maintains is interfering with that interface.
+
+I'm not sure what you mean by ""asynchronous Date manipulation"".  Sinon's fake timer methods are synchronous, AFAICT, just a simulation where you advance the clock manually.
+
+As far as the actual code (jquery.color.js and jquery.makeCollapsible.js), they are both using .promise (https://api.jquery.com/promise/) to monitor completed actions in the fx queue.
+
+GuidedTour (one of the extensions this bug affects) does not have any asynchronous tests, nor does GettingStarted.  Although we use setTimeout, we certainly don't do anything weird like redefining it.
+
+EventLogging (one of our dependencies) does use asynchronous tests, but we're hardly the only extension to use EventLogging.  (Note, EventLogging is not a Growth extension).  I don't know if any extensions with QUnit tests use EventLogging, but I suspect they do.
+
+If you see a bug (or unexpected interaction) which we can fix in a Growth extension, let us know.
+
+However, practically speaking, we should focus on getting this bug fixed.  My next step (as mentioned on Gerrit) will be to try use PhantomJS's remote debugging to step through and find exactly what's happening.",1404258173,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Considering it is only affecting tests related to asynchronous Date manipulation, I suspect one or more of the extensions the Growth team maintains is interfering with that interface.
+
+That was the case a few months back as well (that time it was an infrastructure library inside Grunt/Jenkins causing it).
+
+I can't reproduce this in MediaWiki core or any of the other extensions I can find. The test for MediaWiki core alone or those run for extensions such as VisualEditor and other projects are all consistently passing.",1404250281,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 143481 had a related patch set uploaded by Mattflaschen:
+Use QUnit.asyncTest even for fake timers, to fix spurious failures
+
+https://gerrit.wikimedia.org/r/143481",1404249272,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Actually, the first failure (at least sometimes, such as 220 mentioned above) is jquery.color.
+
+From the full log (https://integration.wikimedia.org/ci/job/mwext-GuidedTour-qunit/220/consoleFull) (without full it shows the tail):
+
+19:08:06 jquery.color - animate...ERROR
+19:08:06 >> Message: Expected 1 assertions, but 0 were run",1404246668,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,This is really problematic… https://gerrit.wikimedia.org/r/#/c/137837/,1403791471,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"I'm going to work on this as well, since it's a recurring problem affecting the Growth team.",1402791966,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Hm.. will give it another look. Although I doubt it's a bug in core.,1400784106,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,This is an old report. Been fixed a while ago.,1400784066,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Krinkle/Antoine: can you take a look please.,1400783594,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Someone really needs to take a look at this.  It is causing major friction in the continuous integration pipeline due to spurious failures.,1400783083,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"It's recurred.  See https://integration.wikimedia.org/ci/job/mwext-GuidedTour-qunit/220/console .  It's from about 6 hours ago.
+
+It's causing spurious failures in GuidedTour (likely other extensions too).  E.g.:
+
+19:08:11 >> Message: after expanding: contentItem is visible
+19:08:11 >> Actual: false
+19:08:11 >> Expected: true",1399426741,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"This was resolved after the following upgrades were made:
+
+
+* [jenkins] Update wmfgrunt dependencies to newer upstream versions 
+  - grunt-contrib-qunit from v0.2.0 to v0.4.0
+  - phantomjs from v1.8.1 to v1.9.7
+  https://gerrit.wikimedia.org/r/#/c/125052/
+
+* [mediawiki-core] Update QUnit from v1.11.0 to v1.14.0 
+  https://gerrit.wikimedia.org/r/#/c/125533/
+
+The latter is what made the false failures go away, so presumably the changes in those QUnit releases fixed it (possibly the changes in v1.12.0 and v1.14.0 that cache setTimeout and clearTimeout to protect against mocks).",1397754931,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"The internal time out is 30 seconds.
+
+It hanging for more than 30 seconds is new, that didn't happen until today.
+
+Both that 30s timeout and the 360min timeout should not be triggered because the tests aren't actually taking more than < 10-20 seconds to run. Something is causing it to get stuck or in some kind of loop...",1397243450,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"mediawiki-core-qunit is now sometime stuck. I killed a few jobs earlier today that ran for multiple hours.
+
+Just killed  https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/19068/console which was running for 10 minutes.
+
+Might want to add adjust the timeout of jobs to something more reasonable than the current 360 minutes.",1397222682,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Somewhat interestingly, the job sometimes hangs for real.
+
+From <https://gerrit.wikimedia.org/r/#/c/125370/>: ""https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/19052/console : ABORTED in 5h 51m 36s""",1397221920,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"This has nothing to do with a time limit of any kind. The qunit tests run quicker than ever and have recently been sped  up a lot further by getting rid of slow animations and http calls to the server etc.
+
+This is failing because for some reason QUnit unexpectedly dies at which point PhantomJS never gets the 'end' event callback and thus times out. It does not time out because the tests are too long or anything.",1396898145,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,*** Bug 63647 has been marked as a duplicate of this bug. ***,1396898036,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Warning: PhantomJS timed out, possibly due to a missing QUnit start() call.\x07 Use --force to continue
+
+On https://gerrit.wikimedia.org/r/#/c/124366/ and some more of my changes from last days
+
+Possible regression from gerrit 117153
+
+Please have a look into this tests. Thanks.",1396894390,PHID-USER-qaoxfiqu6bxhd5ehlwhc,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Again: https://gerrit.wikimedia.org/r/#/c/124302/,1396866763,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Another example from today: https://gerrit.wikimedia.org/r/#/c/123804/,1396723834,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+VisualEditor: [Regression wmf21] Caption field is not appearing for any image in Betalabs and throwing error TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection',"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert a media
+3.Open the media Settings for the image
+
+Observed Result:
+The caption field is missing in the media settings dialog box .Also in the console the following error appears:
+
+Uncaught TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection'
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63544
+
+**Attached**: {F13747}",1396658520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-44p2piogq6pows7eriqb,task_description,resolved
+VisualEditor: [Regression wmf21] Caption field is not appearing for any image in Betalabs and throwing error TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection',Verified the fix in production,1397776336,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-44p2piogq6pows7eriqb,task_subcomment,NA
+VisualEditor: [Regression wmf21] Caption field is not appearing for any image in Betalabs and throwing error TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection',Verified the fix on mw.org,1396998463,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-44p2piogq6pows7eriqb,task_subcomment,NA
+VisualEditor: [Regression wmf21] Caption field is not appearing for any image in Betalabs and throwing error TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection',"This issue got fixed with this commit:
+https://gerrit.wikimedia.org/r/124381
+
+Verified the fix in Betalabs",1396911073,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-44p2piogq6pows7eriqb,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Reported by users and repro'd in beta labs
+
+Log in and edit any page with VE at http://en.wikipedia.beta.wmflabs.org/
+
+From the hamburger list select ""Switch to source editing""
+
+Nothing happens.  In the javascript console find the error 
+
+
+Uncaught Error: OO.ui.Tool.onSelect not implemented in this subclass:function VeUiMWEditModeSourceTool(toolGroup,config){ve.ui.MWEditModeTool.call(this,toolGroup,config);}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396562520,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-hrckm6oxmmkaoroohbia,task_description,resolved
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Verified the fix in production:
+https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox",1397775464,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error",Verified the fix in mw.org,1396999325,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123825 merged by jenkins-bot:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123825",1396913445,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error",Verified the fix on Betalabs: http://en.wikipedia.beta.wmflabs.org/wiki/Regression3rdaprilchrome,1396634053,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123825 had a related patch set uploaded by Jforrester:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123825",1396577458,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123806 merged by jenkins-bot:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123806",1396570050,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123806 had a related patch set uploaded by Alex Monk:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123806",1396569871,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123806 had a related patch set uploaded by Alex Monk:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123806",1396569524,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error",also repro'd on test2wiki,1396563407,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome,"Video showing issue
+
+Chrome Version 33.0.1750.152
+
+1. Access spelling suggestion from right click menu
+2. characters begin to be deleted (video attached)
+or
+3. Page content becomes corrupted, strange character insertions, loss of formatting. (image attached)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50822
+
+**Attached**: {F13521}",1396505280,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-m5xgrnjz6bps3ib55cr7,task_description,resolved
+VisualEditor: Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome,"Agreed, we've fixed this.",1423876215,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m5xgrnjz6bps3ib55cr7,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome,"Could not reproduce the problem on https://cs.wikipedia.org/wiki/Wikipedista:Malyacko/Sandbox?veaction=edit with Chrome 40 on Fedora 21.
+Could not reproduce either by randomly trying on https://en.wikipedia.org/w/index.php?title=Kintsugi&veaction=edit
+Only one insertion/string replacement (as expected).
+
+Is this still an issue nowadays?",1423691064,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-m5xgrnjz6bps3ib55cr7,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome,"Created attachment 15013
+random character insertion and lack of formatting.
+
+**Attached**: {F13522}",1396505336,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-m5xgrnjz6bps3ib55cr7,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Screenshot
+
+Steps to reproduce:
+
+1.Select an image
+2.Click on Cite> Website/Book/Newspaper/Journal 
+
+Observed Result:
+It throws an error: Uncaught TypeError: Object #<VeDmMWBlockImageNode> has no method 'getInternalItem' 
+
+and VE gets stuck at this point, as you cannot close that dialog anymore
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Pageoffseterror?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13484}",1396479120,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_description,resolved
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,Verified the fix on Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Test63452?veaction=edit,1396644715,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Works for me now, both locally and on beta labs.",1396637383,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"After the fix, now the Cite dialogs does not open at all after selecting any image or any other mentioned nodes.
+Therefore reopening the bug and changing the title of the bug .",1396483936,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Change 123124 merged by jenkins-bot:
+Correctly insert or update citations based on template option
+
+https://gerrit.wikimedia.org/r/123124",1396482307,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Change 123124 had a related patch set uploaded by Catrope:
+Correctly insert or update citations based on template option
+
+https://gerrit.wikimedia.org/r/123124",1396481925,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Should be resolved by I34a5a2da576247f4046da45f742bccc3cec22c5a
+
+Specifically, the error is caused by calling getInternalItem on the node without checking if it's a ve.dm.MWReferenceNode. This patchset introduces an instanceof check.",1396481233,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,It happens if you select a gallery/Math formula/template/reflist and then try to open any of the cite options,1396479463,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","Intention:
+Correct the spelling of a word
+
+Steps to Reproduce:
+1. Open a page in Chrome.
+
+2. Pick a word that Chrome believes is misspelled.
+
+3. Right-click to correct the spelling.
+
+4. Save the page and check the diff.
+
+Actual Results:  
+Trying to change ""Minories"" to ""Minorities"" resulted in the missing ""ti"" being added at the very top of the page, rather than in the proper place.  (See http://en.wikipedia.org/w/index.php?title=User:Edgepedia/sandbox1&diff=next&oldid=602158018)
+
+
+
+Reproducible: Didn't try
+
+This may be related to Bug 50822 or Bug 59748.  
+
+Reported in Chrome Version 33.0.1750.154 m on Windows 7 using Vector.  Cannot be reproduced in Safari 6 (although there are other spelling problems in Safari.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50822",1396392120,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6ylcfxjs56sonur5wvhg,task_description,resolved
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","In that case, marking as FIXED in that release. Unsatisfying, but…",1409011116,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","According to a post on frwiki VE feedback page:
+
+If you look at abuse filter 216, problem stopped to happen on June 19th, just after 1.24wmf9 being deployed, so probably a bug fixed in this release (in UTC+2 for Paris):
+14h38 - 128.179.139.136
+15h08 - 91.183.82.40
+16h26 - 92.94.142.126 (not save)
+19h00 - 195.101.137.28
+19h22 - 195.101.137.28
+20h35 - 87.90.125.24
+20h35 - 90.32.27.10
+21h12 - 41.189.42.250
+23h07 - 1.24wmf9 on WP:fr [2]
+
+[1] https://fr.wikipedia.org/w/index.php?title=Spécial:Journal_du_filtre_antiabus&wpSearchFilter=216
+[2] https://wikitech.wikimedia.org/wiki/Server_admin_log",1408998580,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","This was happening in new versions of chrome as recently as a month ago, I can no longer reproduce.",1408989710,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","Might this be caused by ancient versions of Firefox/Chrome caused in part by some config of frwiki, or a bug in their dictionary app, or something?",1408987394,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome",Can't reproduce in FF or Chrome...,1408986548,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","It's still happening, several times a day on frwiki. If you need examples, there's an abuse filter set in place in frwiki that catches some of the problems
+
+https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Journal_du_filtre_antiabus&wpSearchFilter=216",1400838863,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome",Just a note that this is still happening: https://www.mediawiki.org/w/index.php?diff=prev&oldid=997038,1399533054,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","This is also an active bug for Firefox users, tested on FF 28.  Same steps to reproduce as above, same result (the corrected characters are added to both the word highlighted by the spellchecker, and the top of the document)
+
+Note: the unwanted text can be removed with the ""Undo"" button. However, you can't ""Undo"" your spelling correction, undo goes grey after the first action)",1398191119,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome",*** Bug 63652 has been marked as a duplicate of this bug. ***,1398186720,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+
+2.Insert a link
+
+3.Now add a space and then a text next to it
+
+4.Now delete the space and concatenate the text with the exiting link
+
+5.Select the previous link and the text together
+
+6.Re-apply the link 
+
+
+Observed Result:
+The new link does not get applied and ""Save Page"" button remains disabled 
+
+
+
+See the screenshot attached
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/1staprilChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13327}",1396377540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_description,resolved
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Change 125019 merged by jenkins-bot:
+Fix covering annotations logic
+
+https://gerrit.wikimedia.org/r/125019",1397084815,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Change 125019 had a related patch set uploaded by Esanders:
+Fix covering annotations logic
+
+https://gerrit.wikimedia.org/r/125019",1397084657,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"The fix is not working for the following cases:
+
+Case 1:
+
+Steps to reproduce:
+
+1.Open a page with VE
+
+2.Insert a link where the target is an existing page
+
+3.Now add a space and then a text next to it
+
+4.Save the page
+
+5.Reopen the page
+
+6.Now delete the space
+
+7.Select the previous link and the text together
+
+8.Re-apply the link where the link target is a new page
+
+
+Case 2:
+
+Steps to reproduce:
+
+1.Open a page with VE
+
+2.Insert a link where the link target is a new page
+
+3.Now add a space and then a text next to it
+
+4.Save the page
+
+5.Reopen the page
+
+6.Now delete the space
+
+7.Select the previous link and the text together
+
+8.Re-apply the link where the link target is a different new page
+
+Case 3:
+
+1.Open a page with VE
+
+2.Insert a link where the target is a new page
+
+3.Now add a space and then a text next to it
+
+4.Save the page
+
+5.Reopen the page
+
+6.Now delete the space
+
+7.Select the previous link and the text together
+
+8.Re-apply the link where the link target is an exiting page
+
+In all the above three cases , the link does not get applied to the concatenated text",1397074188,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"I can still reproduce it on Betalabs.So, reopening it.",1397000509,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Change 124006 merged by jenkins-bot:
+Apply annotations to partially annotated selections
+
+https://gerrit.wikimedia.org/r/124006",1396656835,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Change 124006 had a related patch set uploaded by Esanders:
+Apply annotations to partially annotated selections
+
+https://gerrit.wikimedia.org/r/124006",1396644843,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,This happens even if you dont delete the space and just select both the link and the text and then re-apply a new link.,1396557465,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"So the problem is:
+
+If you select text that is partially linked and partially not linked (in this specific case, the first part is linked and the second part isn't), then open the link inspector, we inspect the existing link but don't extend the link. If you then close the inspector without changing the target, nothing happens, but if you close the inspector with a changed target, the link is extended.
+
+So I guess that on opening the link inspector, we should aggressively extend the link?",1396482878,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a Cite Web or Cite Book
+3.Click on Show options to get the advanced widget
+
+
+Observed Result:
+Parameter icons inside transclusion dialog are overlapping with the parameter name
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13392}",1395880020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mdr37i6dfciuquwfrsiu,task_description,resolved
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,Verified the fix in betalabs and test2,1395964846,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mdr37i6dfciuquwfrsiu,task_subcomment,NA
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,Should now be fixed in production too.,1395962516,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mdr37i6dfciuquwfrsiu,task_subcomment,NA
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,"Change 121417 merged by jenkins-bot:
+Move padding rules for OutlineItemWidget from core to skins.
+
+https://gerrit.wikimedia.org/r/121417",1395945674,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mdr37i6dfciuquwfrsiu,task_subcomment,NA
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,"Change 121417 had a related patch set uploaded by Catrope:
+Move padding rules for OutlineItemWidget from core to skins.
+
+https://gerrit.wikimedia.org/r/121417",1395943196,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mdr37i6dfciuquwfrsiu,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Screenshot
+
+Steps to reproduce:
+
+1.Create a page with VE
+2.Add a bullet list
+3.Add few items
+4.Now change the list to numbered list
+5.The cursor gets shifted to the start of the document
+6.Now type something
+
+Observed Result:
+Everything starts to behave weirdly .It starts to add text everywhere at the beginning of the page.The list disappears.
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Checkcursorbullet&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13373}",1395876240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pquph4y6rgkckbyn7rza,task_description,resolved
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,Verified the fix in production,1397177893,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,Verified the fix on mediawiki.org,1396990720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,Verified the fix on Betalabs,1396547285,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Change 123488 merged by jenkins-bot:
+Restore selection after ListAction too
+
+https://gerrit.wikimedia.org/r/123488",1396483527,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Change 123488 had a related patch set uploaded by Catrope:
+Restore selection after ListAction too
+
+https://gerrit.wikimedia.org/r/123488",1396483402,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Created attachment 14999
+snowman!!
+
+**Attached**: {F13374}",1396391384,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Also, got the following error one time and the snowman while typing after changing the bullet list to numbered list:
+Uncaught Error: Invalid retain length, cannot retain backwards:-1",1396391363,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"The errors that appears in the console are:
+Uncaught Error: Unbalanced set of replace operations found
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 26 is out of bounds",1395876416,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: Update newarticletext usage for added parameter,"https://gerrit.wikimedia.org/r/#/c/83221/ added a parameter to newarticletext, but VE doesn't pass it, so now when you try to use VE on a nonexistent page with vanilla messages (enwiki's newarticletext message doesn't use $1) you see a raw $1 in the edit notice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395868740,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ih4n4564yrxr2ygatq7s,task_description,resolved
+VisualEditor: Update newarticletext usage for added parameter,"Change 121251 merged by jenkins-bot:
+Update use of newarticletext for added parameter
+
+https://gerrit.wikimedia.org/r/121251",1395871245,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ih4n4564yrxr2ygatq7s,task_subcomment,NA
+VisualEditor: Update newarticletext usage for added parameter,"Change 121251 had a related patch set uploaded by Alex Monk:
+Update use of newarticletext for added parameter
+
+https://gerrit.wikimedia.org/r/121251",1395869962,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ih4n4564yrxr2ygatq7s,task_subcomment,NA
+VisualEditor: Cannot close the Media Settings dialog as the error Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode' appears in the console,"screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Open the math inspector
+3.Keep it open
+4.Insert an image
+5.Select the image
+6.Click on undo 
+7.Click on the media settings icon that is still appearing at the right corner of the page
+
+Observed Result:
+
+The Media Settings dialog box appears with empty caption field .An error appears in the console: 
+Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode'
+
+Also, you will not be able to close the Media Settings dialog box and will get stuck at this step.
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13323}",1395860460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xskmm57u4y7kf62syw5f,task_description,resolved
+VisualEditor: Cannot close the Media Settings dialog as the error Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode' appears in the console,"Yes, Checked in production,appears to be fixed.",1401474803,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xskmm57u4y7kf62syw5f,task_subcomment,NA
+VisualEditor: Cannot close the Media Settings dialog as the error Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode' appears in the console,I believe that this is now fixed – please confirm.,1401472140,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xskmm57u4y7kf62syw5f,task_subcomment,NA
+VisualEditor: Cannot close the Media Settings dialog as the error Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode' appears in the console,"This seems to be because MediaEditDialog is launched for an MWMathNode, which shouldn't be possible. Assigned to Trevor as the fact that we even got here is a bug in the tools system.
+
+MediaEditDialog also shouldn't crash in this case, but Moriel is already going to merge the insertion and edit dialogs, so that should take care of that issue.",1395872280,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xskmm57u4y7kf62syw5f,task_subcomment,NA
+VisualEditor: Citation tool matching should also match templates with whitespace before the first parameter,"The citation tool recongizes a citation template that starts like this:
+
+<ref>{{cite web|url= 
+
+It does not recognize one that starts like this:
+
+<ref>{{cite web |url=
+
+The only difference is the (very common) addition of a space before the parameter.  It should understand both of these.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395859680,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4yo52lx6x7wj5lym5xlc,task_description,resolved
+VisualEditor: Citation tool matching should also match templates with whitespace before the first parameter,I fixed this in https://gerrit.wikimedia.org/r/#/c/132725/ without realizing it.,1400095463,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4yo52lx6x7wj5lym5xlc,task_subcomment,NA
+"VisualEditor: [Regression] Firefox displaying icons in odd places in dialog boxes (reference, media, template, …)","Intention:
+Edit an existing reference
+
+Steps to Reproduce:
+1. Open any article containing an existing citation in Firefox.  (I can't reproduce this in Safari.)
+
+2. Open an existing reference.
+
+3. Look at the ""Options"" area.
+
+Actual Results:  
+The icon overlaps with the text.  See screenshot.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63433
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63432",1395858900,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-7gxc6q7whoodm3jmk5bv,task_description,resolved
+"VisualEditor: [Regression] Firefox displaying icons in odd places in dialog boxes (reference, media, template, …)",*** Bug 63433 has been marked as a duplicate of this bug. ***,1397687806,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7gxc6q7whoodm3jmk5bv,task_subcomment,NA
+"VisualEditor: [Regression] Firefox displaying icons in odd places in dialog boxes (reference, media, template, …)",*** Bug 63432 has been marked as a duplicate of this bug. ***,1397687801,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7gxc6q7whoodm3jmk5bv,task_subcomment,NA
+"VisualEditor: [Regression] Firefox displaying icons in odd places in dialog boxes (reference, media, template, …)","Created attachment 14915
+Screenshot showing misaligned icon and labels
+
+**Attached**: {F13315}",1395858984,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-7gxc6q7whoodm3jmk5bv,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Click on  Insert> Formula
+3.Insert a formula inside then delete it 
+
+Observed Result:
+An empty selection box appears
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13248}",1395793260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7uw3xey4tqnzlnmyclap,task_description,resolved
+VisualEditor: An empty selection box is appearing while inserting a math formula,Verified the fix in production,1397177151,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"As per Ed, the initial empty selection box appearing on opening Math inspector is not related with this issue.So creating a separate bug for it and closing this one.",1397172262,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"This bug is partially fixed, the empty selection box is still appearing when you first open the Math Inspector.",1397089704,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,Verified the fix on Betalabs and test2,1397088241,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"Change 122602 merged by Physikerwelt:
+Emit rerender on math node if Tex image is not present
+
+https://gerrit.wikimedia.org/r/122602",1396349720,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"Change 122602 had a related patch set uploaded by Esanders:
+Emit rerender on math node if Tex image is not present
+
+https://gerrit.wikimedia.org/r/122602",1396307311,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+"VisualEditor: Close inspectors when the user clicks on the toolbar (e.g. on ""Save Page"") so it's clear that it has applied to the document","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a gallery or a Link inspector
+3.Edit something and close the inspector, this will make the save page button disabled
+
+4.Now again reopen that inspector and make further changes but do not close the inspectors .
+
+5.Click on the already active ""Save Page"" button
+
+Observed Result:
+The modified content of step 4 also gets saved even though user did not close the inspector to save it.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/24thmarchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395706620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-un4nilv22yoifhx5muc5,task_description,resolved
+"VisualEditor: Close inspectors when the user clicks on the toolbar (e.g. on ""Save Page"") so it's clear that it has applied to the document","
+
+*** This bug has been marked as a duplicate of bug 51439 ***",1401996119,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-un4nilv22yoifhx5muc5,task_subcomment,NA
+"VisualEditor: Close inspectors when the user clicks on the toolbar (e.g. on ""Save Page"") so it's clear that it has applied to the document",This is intended behavior but should be made clearer to the user. Perhaps clicking the save button should close the inspector? Or clicking anywhere in the surface+toolbar should close the inspector?,1395858638,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-un4nilv22yoifhx5muc5,task_subcomment,NA
+VisualEditor: Cite options are appearing as empty dialog on a new empty page for some time,"Screenshot
+
+Steps to reproduce:
+
+1.Open a new page with VE
+2.On this empty page select any option under Cite 
+
+Observed Result:
+
+The dialog box for cite options are appearing as empty dialog box 
+After a long time , the required parameters for Cite options appear
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Another24Marchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F13128}",1395702600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pe2hcgpuqebuelkuegcp,task_description,resolved
+VisualEditor: Cite options are appearing as empty dialog on a new empty page for some time,"It shouldn't be very long (but that's a different issue), but we've now fixed this by adding a loading animation to dialogs",1401418651,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pe2hcgpuqebuelkuegcp,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).","Without any required parameters
+
+Steps to reproduce:
+
+
+1,Open a page with VE
+2.Insert a reference
+3.Open the reference dialog box select any option under Cite (Website/Book/Newspaper/Journal)
+
+Observe Result:
+None of the required parameters are showing up , in all cases the dialog to add a transclusion comes up.
+
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Another24Marchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13118}",1395701400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_description,resolved
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).","Change 121266 merged by jenkins-bot:
+Make cite transclusion tools actually work
+
+https://gerrit.wikimedia.org/r/121266",1395874136,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).","Change 121266 had a related patch set uploaded by Catrope:
+Make cite transclusion tools actually work
+
+https://gerrit.wikimedia.org/r/121266",1395873726,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).",It is not related with Beta Labs being slow yesterday.I can still reproduce it.,1395771627,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).",This was caused by Beta Labs melting; now working again. Ish.,1395702237,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).","Created attachment 14898
+how it appears on CE with the required parameters
+
+**Attached**: {F13119}",1395701531,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Uncaught TypeError: Cannot read property 'keyedNodes' of undefined  appears while adding a reference in the page and makes VE unresponsive,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a reference
+
+Observed Result:
+
+Uncaught TypeError: Cannot read property 'keyedNodes' of undefined appears in the console and VE gets unresponsive
+
+See the screenshot attached.
+ 
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13105}",1395697140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-z6u74sout6eqjchhlbja,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Uncaught TypeError: Cannot read property 'keyedNodes' of undefined  appears while adding a reference in the page and makes VE unresponsive,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Another24Marchrome?venotify=created,1395703011,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-z6u74sout6eqjchhlbja,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Uncaught TypeError: Cannot read property 'keyedNodes' of undefined  appears while adding a reference in the page and makes VE unresponsive,"Change 120613 merged by jenkins-bot:
+Update reference's internal item after inserting reference
+
+https://gerrit.wikimedia.org/r/120613",1395699599,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-z6u74sout6eqjchhlbja,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Uncaught TypeError: Cannot read property 'keyedNodes' of undefined  appears while adding a reference in the page and makes VE unresponsive,"Change 120613 had a related patch set uploaded by Catrope:
+Update reference's internal item after inserting reference
+
+https://gerrit.wikimedia.org/r/120613",1395698783,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-z6u74sout6eqjchhlbja,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Screenshot
+
+Steps to reproduce:
+
+Just open the Keyboard shortcut page
+
+Observed Result: See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13057}",1395683880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Change 357808 had a related patch set uploaded (by Pmiazga; owner: Pmiazga):
+[mediawiki/extensions/Popups@master] Handle Restbase HTML response
+
+[[https://gerrit.wikimedia.org/r/357808]]
+",1496928668,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/26thmarChrome?veaction=edit,1395940894,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Change 121264 merged by jenkins-bot:
+Bring CommandHelpDialog CSS back
+
+https://gerrit.wikimedia.org/r/121264",1395873586,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Change 121264 had a related patch set uploaded by Catrope:
+Bring CommandHelpDialog CSS back
+
+https://gerrit.wikimedia.org/r/121264",1395873164,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Some CSS paths changed, maybe that's what broke this.",1395858843,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a text
+3.Try to Save the page
+
+
+Observed Result:
+An error appears : Uncaught TypeError: Cannot call method 'teardown' of undefined
+The page seems to be in readmode but the cursor still appears on the page
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Toc_issue
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12876}",1395424800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dwllxtwbn3l46wpsweqk,task_description,resolved
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs",Verified the fix in betalabs,1395439734,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","Change 120070 merged by jenkins-bot:
+Fix a typo that causes crashes when using the wrong symbol for mwTocWidget
+
+https://gerrit.wikimedia.org/r/120070",1395434096,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","Change 120070 had a related patch set uploaded by Jforrester:
+Fix a typo that causes crashes when using the wrong symbol for mwTocWidget
+
+https://gerrit.wikimedia.org/r/120070",1395433999,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","Oops... I meant:
+
+if ( this.surface.mwTocWidget ) {
+    this.surface.mwTocWidget.teardown();
+}",1395425086,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","This error has to do with code that looks like this:
+
+if ( this.surface.mwTocWidget ) {
+    this.mwTocWidget.teardown();
+}
+
+which needs to be rewritten to look like:
+
+
+if ( this.surface.mwTocWidget ) {
+    this.mwTocWidget.surface.teardown();
+}",1395425048,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"This will alert us to things going wrong quickly. Hopefully. (Yes, there's a risk of noise, but there should be 0 of these, anyway.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395281460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sg62navkedep4loydypt,task_description,resolved
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"(In reply to Elitre from comment #7)
+> The tag vepawns, i.e. :
+> https://en.wikipedia.org/w/index.php?title=Special:
+> RecentChanges&tagfilter=vepawns .
+
+That's not done by VisualEditor; these must be a local AbuseFilter written by the community…",1406750919,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"The tag vepawns, i.e. : https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=vepawns .",1406750846,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,What filter?,1406740869,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"@Alex, that filter doesn't seem to be catching anything, I have no idea if it's still functional or not, that's why I asked.",1406736985,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"Went with approach #3, it's a python script run under the 'wm-ve-needcheck-reporter' service user in tool labs. Cron set up to run every day at 16:30 (UTC).
+
+(In reply to Elitre from comment #3)
+> Should vepawns edits be tracked as well?
+Perhaps we should have a separate bug for this - it sounds like a good idea to mark edits which add new pawn characters to the page as needcheck",1406140592,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,Should vepawns edits be tracked as well?,1395393174,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"As I said in IRC, option 3 seems sanest to me, but that's not really my call as I'm not the one that'll write it. :-)",1395350006,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"The CVNBot software used for #cvn-sw, #cvn-commons, #cvn-meta etc. can't provide this because of limitations in the source feed, irc.wikimedia.org, which doesn't expose revision change tags.
+
+Looks like realistically the fast way to make this happen is probably a little nodejs project ran from tool labs that polls wikis using one of these approaches:
+
+1) Socket to irc.wikimedia.org, join all channels, filter for lines that look like edits/page creations (any line that includes a url with rcid), extract rcid from url, make API request and retrieve change tags.
+
+Pros:
+ - Only one socket for events.
+ - No API polling.
+
+Cons: 
+ - It's friggin IRC
+ - Still requires an API request, looots of them (one for every edit/newpage across all of Wikimedia). Could be done in batches when implementing it with a short local delay/buffer before outputting it, but still a ton of requests.
+
+1b) Alternative: Like #1a, but do the changetag retrieval via SQL query to labsdb instead of API request.
+
+Pros:
+ - Only one socket for events.
+ - No API polling.
+ - No API requests at all.
+Cons:
+ - dbreplag might cause problems.
+
+
+2) Have the app generate a list of API entry points for all Wikimedia wikis (using either operations/mediawiki-config data or using centralauth/sitematrix API), and poll all these periodically for action=recentchanges, taking care to ensure we don't miss edits (lower query is faster/cheaper, but means if there is more than limit N number of edits since the last query, you miss out).
+
+Pros:
+ - Edit information included in main event stream (ApiRecentChanges).
+
+Cons:
+ - API polling.
+ - One API request for each wiki, at an interval.
+ - Not missing events is going to be hard.
+
+3) Have the app fetch a list of wikis from labsdb.meta.wiki, open 1 connection for each db shard, and start polling recentchanges for each wiki (using WHERE query to find everything since the last poll, potentially LIMIT still to keep things rate limited)
+
+Pros:
+ - Edit information included in main event stream (recentchanges table).
+ - Only a few sockets needed (7 or 8) to be able to query all 100s of wikis.
+ - No API polling.
+ - No API requests at all.
+
+Cons:
+ - Slight delay due to dbreplag to labs, but we don't use anything else so it's consistent should the app should be blind to it.",1395283265,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor:  Template tabbing is odd in Firefox (loses focus between parameters?),"Intention:
+Tab through the fields in a pre-existing infobox
+
+Steps to Reproduce:
+1. In Firefox 27, open a page that contains an infobox.
+
+2. The cursor is (should be) in the first parameter, which should light up with a blue border.  Press the tab key. 
+
+3. Where is the cursor now?
+
+4. Repeat.
+
+
+Bonus:  When you get nearly to the end of the template, use the mouse or arrow keys to click back in the first parameter.  Press tab.  The cursor should be in parameter #2, but sometimes it goes to the parameter after your pre-click location.
+
+Actual Results:  
+You sometimes have to tab twice to get from parameter #1 to parameter #2.  If you do, then select-all from the keyboard will select the TemplateData descriptions.
+
+
+Reproducible: Sometimes
+
+I was unable to reproduce this in Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395248040,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-p6ts7vep3e6p2gds2ktg,task_description,resolved
+VisualEditor:  Template tabbing is odd in Firefox (loses focus between parameters?),"Change 125894 merged by jenkins-bot:
+Only blur inputs within booklet pages when moving away
+
+https://gerrit.wikimedia.org/r/125894",1397670710,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6ts7vep3e6p2gds2ktg,task_subcomment,NA
+VisualEditor:  Template tabbing is odd in Firefox (loses focus between parameters?),"Change 125894 had a related patch set uploaded by Trevor Parscal:
+Only blur inputs within booklet pages when moving away
+
+https://gerrit.wikimedia.org/r/125894",1397515572,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6ts7vep3e6p2gds2ktg,task_subcomment,NA
+VisualEditor:  Template tabbing is odd in Firefox (loses focus between parameters?),This is probably Firefox not respecting tab-index: -1; or something. Eurgh.,1395281211,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6ts7vep3e6p2gds2ktg,task_subcomment,NA
+"VisualEditor: <a rel=""mw:WikiLink"" href=""Foo"" ></a> shouldn't ever be sent to Parsoid.","From bug 50945#c3
+
+| However my testing showed that this was not reliable and sometimes resulted
+| in odd wikicode, e.g. [[Ecuador|<nowiki/>]][[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
+
+<p><a rel=""mw:WikiLink"" href=""./Ecuador"" ></a><a rel=""mw:WikiLink"" href=""./Egypt"">E</a><a rel=""mw:WikiLink"" href=""./Egypt"">gypt</a></p>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395196560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nazqhnyfc7ftcgefkuwk,task_description,resolved
+"VisualEditor: <a rel=""mw:WikiLink"" href=""Foo"" ></a> shouldn't ever be sent to Parsoid.",We /believe/ that this may have been fixed this week; provisionally closing as such.,1395196643,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nazqhnyfc7ftcgefkuwk,task_subcomment,NA
+VisualEditor: Link inspector doesn't save changes when closing while XHR is pending,"Introduce artificial delays in your API modules (sleep(2); at the top of ApiOpenSearch::execute() and ApiQueryInfo::execute(); alternatively, you can try this in production if you're quick enough), then perform the following steps quickly:
+
+1. Inspect an existing link
+2. Change its target
+3. Before the API request completes, close the link inspector by clicking out or clicking the back arrow
+4. Inspect the link again
+
+Expected: new target shows in inspector
+Actual: old target shows
+
+With the keyboard it's even weirder:
+
+1. Inspect an existing link
+2. Type ""foo"". Wait for the API request to come back and display suggestions
+3. Type ""bar"" at the end (so you now have ""foobar""), then quickly (before the API call comes back) press Enter.
+4. Expected: inspector closes. Actual: input value is reset to ""foo""
+(At least if you press Enter again, ""foo"" is actually saved.)
+
+You can work around this and still reproduce the first bug:
+
+1. Inspect an existing link
+2. Type ""foo""
+3. If a suggestion box is displayed (perhaps because ""f"" was in cache, or because the previous value was in cache), press Esc to dismiss it
+4. Press Enter, the inspector closes
+5. Inspect the link again
+
+Expected: ""foo""
+Actual: previous value
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395195780,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ccf5hssmynovsc2eeyi7,task_description,resolved
+VisualEditor: Link inspector doesn't save changes when closing while XHR is pending,This looks like it's now been fixed. I think.,1402548960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ccf5hssmynovsc2eeyi7,task_subcomment,NA
+VisualEditor: setResizableHandlesSizeAndPosition() shouldn't measure things on every keypress,"In afterDocumentKeyPress, setResizableHandlesSizeAndPosition() is called and measures and repositions all ResizableNode resize handles, even though they're not even visible. This is wasteful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395188760,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mjjjlepmev2tbtsh3jxb,task_description,resolved
+VisualEditor: setResizableHandlesSizeAndPosition() shouldn't measure things on every keypress,Fixed in gerrit Ia6cf8de0da0.,1412610753,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mjjjlepmev2tbtsh3jxb,task_subcomment,NA
+VisualEditor: setResizableHandlesSizeAndPosition() shouldn't measure things on every keypress,This was fixed at some point. setResizableHandlesSizeAndPosition() is now attached to the 'position' event on focus and detached on blur.,1412588928,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mjjjlepmev2tbtsh3jxb,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'update' of null"" and inserts empty formula","The error
+
+Steps to reproduce:
+
+
+1.Open a page with VE which has slug in it
+2.Place your cursor in the slug and open the math inspector
+3.Now type something inside the math inspector
+
+
+Observed Issue 1: 
+It throws an error:
+Cannot call method 'update' of null
+
+And if you insert the math function and save the page and then go to edit source , you will see an empty math rag has also been added to the page
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_(WMF)&action=edit
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58286
+
+**Attached**: {F13147}",1395166680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b4n4vtsivb5tsumyakxy,task_description,resolved
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'update' of null"" and inserts empty formula","
+
+*** This bug has been marked as a duplicate of bug 58286 ***",1397704103,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b4n4vtsivb5tsumyakxy,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'update' of null"" and inserts empty formula",Confirming still occurring.,1397692741,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b4n4vtsivb5tsumyakxy,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'update' of null"" and inserts empty formula","Created attachment 14851
+The empty math tag
+
+**Attached**: {F13148}",1395166732,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b4n4vtsivb5tsumyakxy,task_subcomment,NA
+VisualEditor: [Regression] Long target names no longer get shortened in the link inspector,"Steps to reproduce:
+
+- go to http://en.wikipedia.beta.wmflabs.org/wiki/Snail
+- edit the page with visual editor
+- highlight text ""animal""
+- click Hyperlink tool
+- paste http://en.wikipedia.beta.wmflabs.org/wiki/Animal into Hyperlink tool
+- the link goes out of Hyperlink tool box (see attached screen shot)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395164040,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-54nochcknohar22gmhks,task_description,resolved
+VisualEditor: [Regression] Long target names no longer get shortened in the link inspector,"Oh, yeah, we fixed this in the inspector styling tweaks in April, I think.",1401468546,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-54nochcknohar22gmhks,task_subcomment,NA
+VisualEditor: [Regression] Long target names no longer get shortened in the link inspector,Works for me. Did this get fixed at some point since this bug was filed?,1401449578,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-54nochcknohar22gmhks,task_subcomment,NA
+VisualEditor: [Regression] Long target names no longer get shortened in the link inspector,"Created attachment 14849
+hyperlink tool
+
+**Attached**: {F13143}",1395164089,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-54nochcknohar22gmhks,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the link inspector 
+3.Now enter something invalid for link inspector , for example: File:Joo Chiat Place.jpg|Item 1
+
+Observed Result:
+
+An error message appears for invalid page title , the style of the error message should be much more apparent like red 
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13049}",1395097740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-um7czp26rhb3rg5y7ylt,task_description,resolved
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,Nice!,1416266975,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"All patches mentioned in this report were merged or abandoned - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?",1416053635,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Change 150297 merged by jenkins-bot:
+MWLinkTargetInputWidget: Add styles for invalid link titles
+
+https://gerrit.wikimedia.org/r/150297",1406832737,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Change 150297 had a related patch set uploaded by Palerdot:
+Fixed Bug 62761, added invalid link title style.
+
+https://gerrit.wikimedia.org/r/150297",1406831831,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Comment on attachment 16097
+Screenshot of Fix for Bug 62761
+
+The color in the screenshot is red. I have changed the color to #d45353 to match the other warning elements in the mediawiki page.",1406661753,PHID-USER-or5bjqrmvxl6rczurt2w,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Screenshot of Fix for Bug 62761
+
+This is the screenshot of the fix I have made for the bug 62761. The gerrit patch link is https://gerrit.wikimedia.org/r/#/c/150297/
+
+**Attached**: {F13050}",1406661578,PHID-USER-or5bjqrmvxl6rczurt2w,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"I have made a fix to this bug. The gerrit patchset link is https://gerrit.wikimedia.org/r/#/c/150297/
+
+Things done:
+A new CSS File 
+'ve.ui.MWLinkTargetInputWidget.css' is added to the path 'VisualEditor/modules/ve-mw/ui/styles/widgets'. Warning text style is added to the class '.ve-ui-mwLinkTargetInputWidget-warning' in this file. The CSS File is included in the style resources in the file 'VisualEditor.php'. Tested in latest stable firefox, chrome in Ubuntu 14.04.
+
+Please review the changes. I'm new to open source contribution, So let me know if I have done the fix to the bug in the right way. Thanks.",1406661456,PHID-USER-or5bjqrmvxl6rczurt2w,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Change 150297 had a related patch set uploaded by Palerdot:
+Fixed Bug 62761, added invalid link title style.
+
+https://gerrit.wikimedia.org/r/150297",1406661128,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: Drag and drop inserted the relocatable node image marker as a data:image/gif;base64 string,"I don't know how the user did that, but take a look at this edit:
+https://pt.wikipedia.org/wiki/Esporte_Clube_Pelotas?diff=38422037
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395063660,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-27yzqmhzbjs5rne5s34q,task_description,declined
+VisualEditor: Drag and drop inserted the relocatable node image marker as a data:image/gif;base64 string,I can't replicate; I've not seen any other reports like this; and we re-wrote this system last week. Provisionally I'm going to mark as WFM.,1404421306,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-27yzqmhzbjs5rne5s34q,task_subcomment,NA
+VisualEditor: Drag and drop inserted the relocatable node image marker as a data:image/gif;base64 string,"That's the relocatable node image marker, so it's a  drag & drop bug.",1395065812,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-27yzqmhzbjs5rne5s34q,task_subcomment,NA
+VisualEditor: The message that appears while adding a template with no description should use the readable form of template name,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Transclusion
+3.Insert a template that does not have any description.
+4.For example: Country showdata for betalabs
+
+Observed Result:
+A message comes up :You are adding the ""Country_showdata"" template to this page. It doesn't yet have a description, but there might be some information on the template's page.
+
+In this message , the template name used should be in more readable form that is with underscores: Country showdata
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_(WMF)?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F12888}",1394836500,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vi756jr6zyy2qwagomlc,task_description,resolved
+VisualEditor: The message that appears while adding a template with no description should use the readable form of template name,This appears to have been fixed in Gerrit change 132723 by Bartosz,1401475141,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vi756jr6zyy2qwagomlc,task_subcomment,NA
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Place the cursor in a slug
+3.Press tab
+
+Observed Result:
+An error appears in the console:
+Uncaught TypeError: Cannot call method 'getParent' of null
+ve.Document.getCoveredSiblingGroups
+ve.ui.IndentationAction.increase
+ve.ui.Surface.execute
+ve.ui.Command.execute
+ve.ui.Surface.execute
+ve.ce.Surface.onDocumentKeyDown
+proxy load.php:10
+ve.EventSequencer.onEvent
+(anonymous function)
+jQuery.event.dispatch load.php:45
+elemData.handle.eventHandle
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12844}",1394827800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_description,resolved
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item",Verified the fix on test2:https://test2.wikipedia.org/wiki/Wmf19?veaction=edit,1395356950,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_subcomment,NA
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item",Verified the fix on Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_(WMF)?veaction=edit,1395083360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_subcomment,NA
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item","Change 119045 merged by jenkins-bot:
+Don't try to return the document in getCoveredNodes
+
+https://gerrit.wikimedia.org/r/119045",1395076238,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_subcomment,NA
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item","Change 119045 had a related patch set uploaded by Esanders:
+Don't try to return the document in getCoveredNodes
+
+https://gerrit.wikimedia.org/r/119045",1395064673,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_subcomment,NA
+VisualEditor: Inspector flickers and flashes continuously when resizing window,"When resizing the window with an inspector open, it continuously flickers and flashes blank, sometimes making a slow, fast or partial fade in/out, others when you let go of the resize handle it does a bunch of flashes in burst (as if they were queued up).
+
+Screen capture: http://cl.ly/0g2F0q2D3p1D
+
+Seems to relate to code that adds/removes the ""oo-ui-popupWidget-transitioning"" class.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394758800,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xudydyain6z66hfd3b4j,task_description,resolved
+VisualEditor: Inspector flickers and flashes continuously when resizing window,Fixed a couple of weeks ago by Trevor.,1397763968,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xudydyain6z66hfd3b4j,task_subcomment,NA
+VisualEditor: Inspector flickers and flashes continuously when resizing window,"(In reply to Krinkle from comment #0)
+> Screen capture: http://cl.ly/0g2F0q2D3p1D
+
+This also exposes bug 55789, though these flashes are not caused or related to (absence of) the logic to reposition the overlay elements themselves.",1394758898,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xudydyain6z66hfd3b4j,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Seen often in browser tests run locally and on Cloudbees, this happens: 
+
+
+* default status of Beta toggle is OFF
+* click Beta toggle to ON
+* click Save
+
+* get error: ""Error saving settings. Please make sure that you have cookies enabled""
+
+* Beta toggle goes back to OFF
+* test fails
+
+
+I have not yet triggered this manually. (but I haven't tried that hard either)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394741760,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_description,resolved
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Change 126873 merged by jenkins-bot:
+Use core token handling
+
+https://gerrit.wikimedia.org/r/126873",1397692239,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Change 126873 had a related patch set uploaded by Jdlrobson:
+Use core token handling
+
+https://gerrit.wikimedia.org/r/126873",1397691972,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Jon from comment #64)
+> We deep dived this issue again and concluded we should remove getMobileToken
+> in favour of user->getToken
+> 
+> Chris says that soon anonymous editors will get a unique token when that is
+> called.
+
+Out of curiosity, is there a timeline for this?
+
+> In mean time there is a CSRF risk to anons using Special:MobileOptions but
+> we decided since risk was low we can live with this.
+
+This makes sense to me since this would only be an issue for anons. I'm ok with it so long as Chris S is OK with it.",1397689915,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"We deep dived this issue again and concluded we should remove getMobileToken in favour of user->getToken
+
+Chris says that soon anonymous editors will get a unique token when that is called.
+
+In mean time there is a CSRF risk to anons using Special:MobileOptions but we decided since risk was low we can live with this.",1397683593,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"The test for ""Keep Going"" registers a new account but also triggers the token-mismatch problem: https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/493/testReport/(root)/Encourage%20new%20users%20to%20Keep%20Going/I_see_a_KeepGoing_message_after_completing_my_VisualEditor_edit/",1397490104,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"For reference, history:  http://git.wikimedia.org/history/mediawiki%2Fextensions%2FMobileFrontend/f7180dc297b958a27920a88348db27104eaf10e5/includes%2FMobileContext.php;jsessionid=7rk483w9yc4w15fi1z5t8bd05
+
+and change to MobileContext: 
+
+http://git.wikimedia.org/blobdiff/mediawiki%2Fextensions%2FMobileFrontend/27e463c35c202607fe3023fc020c76ef41c13cd8/includes%2FMobileContext.php",1397252836,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,There have been 8708 hits to this error in the last 30 days on our production wikis.,1397252475,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,The problematic function seems to be MobileContext::getMobileToken,1397148129,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"So this problem seems to only happen when the user is anonymous...
+It seems that $this->getRequest()->getSessionData( 'wsMobileToken' ) is returning null which results in a new session getting setup on submitting the form which results in invalidation of the form.
+
+Don't understand this code well enough to know if this is misbehaving and if it is why.",1397148092,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+Jon updated the editor_ve.feature test today, but I cannot get a clean run of the test on beta labs.  
+
+In every case one token seems to persist longer than it should, on the order of 15+ seconds.  I was tailing mobile.log for three successive unsuccessful runs of that test and got these results: 
+
+2014-04-09 22:04:34 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 0784e6702ac5df67d042c4a7969165bd - expected 0a84ee38edc0905b86d3620bd12765e9
+2014-04-09 22:05:36 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 738fbdc0987c5b31cef77ae5e08aa9fb - expected a041b5f2632ef617d1b92681456d8866
+2014-04-09 22:05:53 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 738fbdc0987c5b31cef77ae5e08aa9fb - expected a041b5f2632ef617d1b92681456d8866
+
+
+2014-04-09 22:08:13 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received b9547af8f118ad0bca2834777d62ba1c - expected 29d3774af72c2a0e6f0768092480c982
+2014-04-09 22:08:31 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received b9547af8f118ad0bca2834777d62ba1c - expected 29d3774af72c2a0e6f0768092480c982
+2014-04-09 22:09:42 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received c6c71ff97b5a448c78f3e85aa27e343d - expected 3a78d9b84bb3873f503baf7d0e41b4cc
+
+2014-04-09 22:11:14 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 1ec21965b2c0eb6dcfd6a01ef1c4eacc - expected 520e7ebbfa9f0449d3ebc0c79e350911
+2014-04-09 22:11:31 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 1ec21965b2c0eb6dcfd6a01ef1c4eacc - expected 520e7ebbfa9f0449d3ebc0c79e350911
+2014-04-09 22:12:38 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 9ce4d541e91887bed12a76e988f90965 - expected 467de8a293b2a6de7a6fef0905660b46",1397081944,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+I set the editor_ve.feature test to log in with a different user anyway and generated the following errors in the second run of the test on my local host: 
+
+2014-04-02 17:52:34 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 60fa1ffd7c4273c5c1e5ceeb7d44cfd2 - expected 361fda81efd0e50f37234db4384ee64e
+2014-04-02 17:53:35 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 60cd4c3b308cac220e7a8629b0427056 - expected 34a28952e608764e4452a5b73b80175e
+2014-04-02 17:53:50 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 60cd4c3b308cac220e7a8629b0427056 - expected 34a28952e608764e4452a5b73b80175e
+
+
+Is it of interest that the last two errors have exactly the same mismatched tokens 15 seconds apart?",1396461473,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+These tests manipulate the ON/OFF toggle settings before logging in, and each browser starts with a fresh profile on every run of every scenario.  Username should be immaterial.",1396460912,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Thanks Chris, that narrows down the problem significantly.
+
+Can you rerun the tests with a different (or new) username, so we can rule out that this is a race condition with multiple tests using the same user account, or something is corrupted in the session cache?
+
+I ran the tests from the office from my linux box, and the test (whenever they finally ran) passed without any errors. So it seems like there is either something about the user that you're using, or the network lag affecting a race condition.",1396458859,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+From the log in beta labs on eqiad just now: 
+
+-04-02 07:46:39 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received cb9248cad0ffc2d5886f2322ac58c2f9 - expected ff97fcfc9650819e3788b20c26680d6b
+2014-04-02 14:36:50 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received b6752dcbd18953383d871c531d620f4c - expected a3e842905af2f624cb4511345978fdc4",1396452907,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,https://gerrit.wikimedia.org/r/121879 added logging of token details to mobile.log,1396294028,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Thanks Chris. That confirms that this is different from what Jeremy posted, since his had a Location header come back from the POST request, whereas yours showed the form with the <div class=""error"">Error saving settings. Please make sure that you have cookies enabled.</div>.
+
+The only codepath that sets wsMobileToken seems pretty safe, and since the Set-Cookie with enwikiSession is returned with the form, that seems pretty safe.
+
+Could someone add a logging statement just after the token check to see what value MediaWiki thinks the mobile token is supposed to be?",1396032229,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Created attachment 14959
+WireShark capture of error conversation
+
+
+This should be the entire conversation containing the POST to MobileOptions that causes the token error. 
+
+(I happen to have another Ubuntu laptop.  After 90 OS upgrades, installing RVM and installing Wireshark, I was able to capture the traffic on a repro of the error.)
+
+**Attached**: {F13407}",1396026559,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"chris steipp, it's however worth noting that we've been unable to replicate this with the above steps on OS X",1396021309,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+Chris Steipp: 
+
+Pretty reliable repo for me has been to run the editor_ve.feature test, and the second Scenario fails with the error almost every time.  Watch the browser as the test runs to see the red error message appear before the ON/OFF toggle switches back to OFF:
+
+$ export MEDIAWIKI_URL=http://en.m.wikipedia.beta.wmflabs.org/wiki/
+$ export MEDIAWIKI_USER=USER
+$ export MEDIAWIKI_PASSWORD=PASSWORD
+
+:~/MobileFrontend/tests/browser$ bundle exec cucumber features/editor_ve.feature 
+@chrome @en.m.wikipedia.beta.wmflabs.org @firefox @login @test2.m.wikipedia.org
+Feature: VisualEditor
+
+  Background:                               # features/editor_ve.feature:4
+    Given I am in alpha mode                # features/step_definitions/common_steps.rb:77
+    And I am logged into the mobile website # features/step_definitions/common_steps.rb:10
+
+  Scenario: Switch from VisualEditor to source editor               # features/editor_ve.feature:8
+    Given I am on the ""Selenium Edit Test"" page                     # features/step_definitions/common_steps.rb:88
+    And I click the edit button                                     # features/step_definitions/editor_steps.rb:7
+    And I see the VisualEditor overlay                              # features/step_definitions/editor_ve_steps.rb:9
+    And The VisualEditor overlay has an editor mode switcher button # features/step_definitions/editor_ve_steps.rb:29
+    And I click the editor mode switcher button                     # features/step_definitions/editor_steps.rb:32
+    When I click the source editor button                           # features/step_definitions/editor_steps.rb:36
+    Then I see the wikitext editor overlay                          # features/step_definitions/editor_steps.rb:11
+
+  Scenario: Ensure we load the correct section # features/editor_ve.feature:17
+    Given I am in alpha mode                # features/step_definitions/common_steps.rb:77
+      timed out after 5 seconds, waiting for {:class=>""mw-mf-settings-off"", :tag_name=>""span""} to become present (Watir::Wait::TimeoutError)
+      ./features/step_definitions/common_steps.rb:82:in `block (3 levels) in <top (required)>'
+      ./features/step_definitions/common_steps.rb:81:in `block (2 levels) in <top (required)>'
+      ./features/step_definitions/common_steps.rb:78:in `/^I am in alpha mode$/'
+      features/editor_ve.feature:5:in `Given I am in alpha mode'",1396019125,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Jon from comment #46)
+> This is now the main source of our failing test builds (the last 3 builds
+> failed solely because of this issue)
+> 
+> Thanks for all the attention being given here.
+> 
+> I wonder if in the mean time we should alter Special:MobileOptions to use a
+> preference for logged in users rather than a cookie - this would be a way of
+> getting around the failures and would be a useful user facing feature - opt
+> in once, get beta/alpha everywhere...
+
+We would still have the same problem - at least in terms of setting the preference. In order to use that form, we need to set the CSRF token which requires the session/cookie. So when the form was submitted to set the preference, you would get stuck with the same behavior. I suppose though once the preference were set, the issue would be moot. It could be a stopgap measure... just as I think running the tests against FF/Chrome in OSX rather than linux/windows would be.",1395981689,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Is anyone able to reproduce this in the office yet? If so, I'm happy to work on this in person tomorrow. Or if someone can walk me through the steps to reproduce, I can attempt from a couple of installs I have.",1395980907,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"This is now the main source of our failing test builds (the last 3 builds failed solely because of this issue)
+
+Thanks for all the attention being given here.
+
+I wonder if in the mean time we should alter Special:MobileOptions to use a preference for logged in users rather than a cookie - this would be a way of getting around the failures and would be a useful user facing feature - opt in once, get beta/alpha everywhere...",1395968165,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Chris, in the meantime, can we point the saucelabs test to not use Linux, perhaps to use FF/Chrome in OS X since we haven't been able to replicate the issue there?",1395966051,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"CSteipp, Wireshark is killing my poor underspec'd laptop.  I spent a couple hours on this, but I cannot even get the test to complete or my wlan interface to stay functional with WireShark running.",1395950220,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Chris, can you do ""follow TCP Stream"" and screenshot the result? I'd like to confirm that you're NOT seeing a Location header returned in the result of that call.",1395941837,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"The screen shot above I think shows the token-mismatch problem on the POST.  
+
+However, the test itself behaves strangely on my local machine with WireShark running so I may have done this incorrectly",1395941530,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Created attachment 14943
+token mismatch on POST shown in WireShark on Linux
+
+**Attached**: {F13406}",1395941378,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Jeremy L Grajales from comment #39)
+> Created attachment 14914 [details]
+> (Partial) Wireshark capture of editor_ve test
+> 
+> [attachments]
+> I captured the test with Wireshark.
+> The POST is obviously the first packet in the log.
+> I find the same behavior as Chris does in Windows Firefox.
+
+So in both Chris'es headers and Jeremy's pcap, there is a session cookie being sent. So that's good.
+
+What I'm confused on is that Jeremy's pcap shows the POST to /wiki/Special:MobileOptions, and you see coming back a Location: http://en.m.wikipedia.beta.wmflabs.org/wiki/Main_Page header, which means that the inequality check in SpecialMobileOptions.php (line 208) was NOT true (i.e., the token parameter matched getMobileToken()), otherwise a form would have been returned.
+
+Is the pcap not showing the issue? Or is this not a token issue?
+
+**Attached**: {F13405}",1395939417,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(Partial) Wireshark capture of editor_ve test
+
+[attachments]
+I captured the test with Wireshark.
+The POST is obviously the first packet in the log.
+I find the same behavior as Chris does in Windows Firefox.
+
+**Attached**: {F13405}",1395848237,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+Requested by Chris Steipp, Request headers and stuff pulled from the Network tab in Firefox after incurring the token error (I also have the entire response that contains the error message if you need it): 
+
+request header: 
+
+Host: en.m.wikipedia.beta.wmflabs.org
+User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0
+Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate
+Referer: http://en.m.wikipedia.beta.wmflabs.org/wiki/Special:MobileOptions?useformat=mobile
+Cookie: centralnotice_bucket=1-4.2; mf_useformat=true; enwikiSession=ed4a7df6517c9aa79ce5231905291c84
+Connection: keep-alive
+
+request body: 
+
+Content-Type: application/x-www-form-urlencoded
+Content-Length: 87
+enableImages=on&enableBeta=on&token=b9a06d2beb98ed9b35acded20a41e9fb&returnto=Main+Page
+
+timings: 
+Waiting 892 ms
+Receiving 3 ms",1395846103,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Arthur Richards from comment #36)
+> Chris, any luck dumping those headers? I'm increasingly curious to see
+> what's going on there.
+
+What headers are you looking for at what point?
+I'd like to see it on my end to see if the Windows reproduction diverges any further from the original bug.",1395838452,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Chris McMahon from comment #27)
+> I chatted with Chris Steipp about this a bit: 
+> 
+> (03:53:51 PM) csteipp: So yeah, either the user doesn't have a session,
+> wsMobileToken in the session is getting overwritten, or the form isn't
+> correctly sending the token
+> 
+> <Antoine restarts all the caches on beta labs>
+> 
+> (04:06:19 PM) csteipp: chrismcmahon: Yeah, times out for me. So the thing is
+> to narrow down which of those 3 is happening. A header capture of a failure
+> would help determine that.
+> 
+> I'll look into getting those headers with WireShark or something.
+
+Chris, any luck dumping those headers? I'm increasingly curious to see what's going on there.",1395798413,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Change 120959 abandoned by Jdlrobson:
+See if sleeping helps avoid token issues on Special:MobileOptions
+
+Reason:
+Thanks to Jeremy L Grajales we can confirm this doesn't have any effect. Back to drawing board.
+
+https://gerrit.wikimedia.org/r/120959",1395790500,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Gerrit Notification Bot from comment #32)
+> Change 120959 had a related patch set uploaded by Jdlrobson:
+> See if sleeping helps avoid token issues on Special:MobileOptions
+> 
+> https://gerrit.wikimedia.org/r/120959
+I get the same behavior as before with the patch using Firefox on Windows.",1395790308,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Gerrit Notification Bot from comment #32)
+> Change 120959 had a related patch set uploaded by Jdlrobson:
+> See if sleeping helps avoid token issues on Special:MobileOptions
+> 
+> https://gerrit.wikimedia.org/r/120959
+I get the same behavior as before with the patch using Firefox on Windows.",1395790286,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Change 120959 had a related patch set uploaded by Jdlrobson:
+See if sleeping helps avoid token issues on Special:MobileOptions
+
+https://gerrit.wikimedia.org/r/120959",1395788208,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Jon from comment #30)
+> If the opt into alpha happens after login does this resolve the issue? I
+> wonder if it's something particularly strange with opting in whilst
+> anonymous...
+
+Don't you mean the opt into beta?
+And this is something I thought of before.
+I tried this manually, and anon or logged-in works fine.
+
+Not sure about running an automated test. But I do not have enough experience editing tests to attempt this fix you suggest. If someone could show me how to do it, I'd love to try it out. But someone else would probably have the chance to do it before I got the chance to learn how to.",1395777013,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,If the opt into alpha happens after login does this resolve the issue? I wonder if it's something particularly strange with opting in whilst anonymous...,1395769112,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Jon from comment #9)
+> If someone can help me get Chrome driver setup maybe I can find a way around
+> this... does delaying the opt in event with a wait help at all Chris?
+
+I also added a ""sleep 5"" below line 79 in common_steps.rb to see if that would resolve anything. Not sure if that is what you were suggesting to do. 
+
+But
+(In reply to Jeremy L Grajales from comment #28)
+adding that delay didn't change any of the previous results on Firefox (Windows).
+
+(In reply to Chris McMahon from comment #27)
+> (03:53:51 PM) csteipp: So yeah, either the user doesn't have a session,
+> wsMobileToken in the session is getting overwritten, or the form isn't
+> correctly sending the token
+
+I think this is heading in the right direction. My only objection to this is that when I attempt to reproduce this manually, everything works fine. This seems like a test handling error and not a session issue. Wouldn't a session issue affect all tests manual/automated?",1395767717,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+I tested this on Firefox (Windows).
+http://pastebin.com/yi9FGPVU
+
+Seems to reproduce the  same issue.
+Although, I'm not sure.
+
+Visually:
+The browser gets to the settings page. 
+Toggles beta switch ON.
+Saves settings.
+And when the page refreshes, the beta button is toggled to OFF.
+
+
+No obvious HTML errors are displayed as reported previously (ie. red text in the browser warning of disabled cookies).",1395764647,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+I chatted with Chris Steipp about this a bit: 
+
+(03:53:51 PM) csteipp: So yeah, either the user doesn't have a session, wsMobileToken in the session is getting overwritten, or the form isn't correctly sending the token
+
+<Antoine restarts all the caches on beta labs>
+
+(04:06:19 PM) csteipp: chrismcmahon: Yeah, times out for me. So the thing is to narrow down which of those 3 is happening. A header capture of a failure would help determine that.
+
+I'll look into getting those headers with WireShark or something.",1395702840,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Arthur Richards from comment #23)
+> I agree with Max, in this case a race condition doesn't make sense due to
+> the nature of PHP. However, it is conceivable that there are occasional
+> hiccups/something going wrong with session storage on the cluster. If that
+> were the case though, I would expect we would hear about more things like
+> this happening - that said, it is probably worth checking into since this
+> has been persistent and we have not been able to adequately explain it
+> otherwise.
+
+
+After chatting a bit with Chris today, I wonder if the problem is related to the platform and/or platform/browser combo. The jobs on sauce labs run in FF/Chrome on Linux - and when Chris tests locally he does so with a Linux box. AFAIK everyone else who has not been able to replicate this problem has been testing from a Mac.",1395696574,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Jeremy if you (In reply to Jeremy L Grajales from comment #24)
+> Is there anything I could do to attempt to replicate this on my end?
+
+Thanks Jeremy - if you don't have it set up already, the first thing to do would be to get MediaWiki and MobileFrontend setup and working. You would also need to install a few other extensions - ConfirmEdit (enable FancyCaptcha), GeoData, Echo, PageImages, VisualEditor (and get parsoid installed/running as well).
+
+Then, you'd need to get your browser testing environment set up (https://www.mediawiki.org/wiki/Quality_Assurance/Browser_testing/Running_tests), and be sure to follow MobileFrontend-specific instructions in MobileFrontend/tests/browser/README.mediawiki
+
+If you run into any problems, let us know and we can probably help you out. If you join #wikimedia-mobile on IRC (Freenode), you can usually get support faster than via Bugzilla.",1395696459,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+Is there anything I could do to attempt to replicate this on my end?",1395691908,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I agree with Max, in this case a race condition doesn't make sense due to the nature of PHP. However, it is conceivable that there are occasional hiccups/something going wrong with session storage on the cluster. If that were the case though, I would expect we would hear about more things like this happening - that said, it is probably worth checking into since this has been persistent and we have not been able to adequately explain it otherwise.",1395423730,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+I think the fact that this is passing anywhere is an environment issue.  
+
+Same error happened twice in Firefox in the build just hours ago: https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/438/",1395423484,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"As stated before, I really thing this is an environment issue. Chris what else might be different in your setup to us?",1395423372,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Chris, these are synchronous operations, it's really hard to do stufff in parallel in PHP:) So no race condition.",1395423052,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+Seems like a race condition in lines 204-208 of SpecialMobileOptions.php in submitSettingsForm. 
+
+As I read this: 
+
+* submitSettingsForm calls out to do ""$context = MobileContext::singleton();"" and also ""$request = $this->getRequest();""
+
+** both of these must take time
+
+* then the code immediately compares tokens with ""if ( $request->getVal( 'token' ) != $context->getMobileToken() )""  
+
+It seems to me like submitSettingForm should wait for both $request and $context to complete before comparing values obtained from those operations.",1395420073,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,Yep but still unable to replicate this bug in any way either locally or on beta labs...,1395327687,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Jon from comment #9)
+> If someone can help me get Chrome driver setup maybe I can find a way around
+> this... does delaying the opt in event with a wait help at all Chris?
+
+Jon, did you manage to get chromedriver working on your machine?",1395322601,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"and here is the same problem in Firefox, so it is not only Chrome:  https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/430/testReport/(root)/VisualEditor/Toolbar_VisualEditor/",1395174074,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"ChromeDriver (v2.9.248304)
+
+but that has nothing to do with the problem.",1395172006,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I understand - I can see this in the browser test screencast but I'm not seeing this so your environment must be setup slightly different to mine?
+
+What version of Chrome Driver are you using?",1395169983,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Created attachment 14852
+error saving settings
+
+**Attached**: {F13404}",1395168954,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I understand but I ran exactly the same test 6 times and can't replicate this. This always passes for me.
+
+What version of Chrome Driver are you using?",1395168564,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I got the problem the first time I ran, on the second scenario: 
+
+$ bundle exec cucumber features/editor_ve.feature 
+@en.m.wikipedia.beta.wmflabs.org @login @test2.m.wikipedia.org
+Feature: VisualEditor
+
+  Scenario: Toolbar VisualEditor                      # features/editor_ve.feature:4
+    Given I am in alpha mode                          # features/step_definitions/common_steps.rb:77
+    And I am logged into the mobile website           # features/step_definitions/common_steps.rb:10
+    And I am on the ""Selenium Edit Test"" page         # features/step_definitions/common_steps.rb:88
+    When I click the edit button                      # features/step_definitions/editor_steps.rb:7
+    Then I see the VisualEditor overlay               # features/step_definitions/editor_ve_steps.rb:9
+    And I see a toolbar in the overlay header         # features/step_definitions/editor_ve_steps.rb:17
+    And The VisualEditor toolbar has a bold button    # features/step_definitions/editor_ve_steps.rb:21
+    And The VisualEditor toolbar has an italic button # features/step_definitions/editor_ve_steps.rb:25
+
+  Scenario: I can edit a page using VisualEditor # features/editor_ve.feature:14
+    Given I am in alpha mode                     # features/step_definitions/common_steps.rb:77
+      timed out after 5 seconds, waiting for {:class=>""mw-mf-settings-off"", :tag_name=>""span""} to become present (Watir::Wait::TimeoutError)
+      ./features/step_definitions/common_steps.rb:82:in `block (3 levels) in <top (required)>'
+      ./features/step_definitions/common_steps.rb:81:in `block (2 levels) in <top (required)>'
+      ./features/step_definitions/common_steps.rb:78:in `/^I am in alpha mode$/'
+      features/editor_ve.feature:15:in `Given I am in alpha mode'
+
+<snip>
+
+$ date
+Tue Mar 18 11:35:44 MST 2014
+
+
+And in the browser I can clearly see the red error message ""Error saving settings. Please make sure that you have cookies enabled""",1395167909,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I have run this 6 times locally against beta labs with the latest ChromeDriver (v2.9.248307) and all passed.
+
+I'm still not sure what's going on here.",1395167488,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,If someone can help me get Chrome driver setup maybe I can find a way around this... does delaying the opt in event with a wait help at all Chris?,1395164025,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+To the extent that it is an issue with Selenium, the speed of the test between clicking the ""ON"" toggle and the ""Save"" button is probably triggering a race condition that is difficult to trigger manually.
+
+But if I run ""editor_ve.feature"" with the ""Given I am in alpha mode"" step 3 times on my local environment pointed to beta labs, I'll get the error 1 or 2 times.",1394841922,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,I wonder if it's possibly an issue with Selenium? This is not something I've been able to repro either and certainly not something I've experienced locally or in production.,1394833538,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Max, for me when I run the browser test ""editor_ve.feature"" (or any test with the step ""Given I am in alpha mode"") against beta labs,  I see the ""Error saving settings. Please make sure that you have cookies enabled"" pretty often, but not always.",1394821396,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Chris, how do I repro this problem locally?",1394820350,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I've not been able to replicate this issue myself. However if there is a bug it's going to be in getMobileToken - the only time when this error should happen is if the token in the settings form differs from the result of getMobileToken
+
+Max any ideas to why this might happen?",1394756027,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"As I said originally, this is pretty easy to repro locally, it is not just Cloudbees builds.",1394751630,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,This looks like an issue on Cloudbees. The error shows only when cookies are disabled. Are we able to say with 100% certainty Cloudbees is not doing something funky?,1394751417,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1770",1394742012,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"After moving the image
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a thumbnail image
+3.Move the image from Right to left
+4.Again move the image from right to left
+
+Observed Result:
+Moving the image from Left to Right or Right to Left changes the size of the image in the VE mode
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Test_62581?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13293}",1394663460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ptgqr6zojc4enjvswwud,task_description,resolved
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754456,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Change 118601 merged by jenkins-bot:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118601",1394752330,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Change 118427 merged by jenkins-bot:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118427",1394744965,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Change 118601 had a related patch set uploaded by Catrope:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118601",1394744857,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Change 118427 had a related patch set uploaded by Mooeypoo:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118427",1394683653,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Created attachment 14797
+Before moving the image
+
+**Attached**: {F13294}",1394663634,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: Selection after deleting block focusablenode (e.g. image) is weird,"1. Edit a document containing a block image
+2. Click on the block image
+3. Press delete
+4. The selection looks odd
+
+Inspection of the DM selection shows that it now covers [/paragraph, paragraph].
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394658780,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-evpea5eipr52hejululr,task_description,resolved
+VisualEditor: Selection after deleting block focusablenode (e.g. image) is weird,This looks OK now… assuming that Ed fixed it. Go Ed.,1407064881,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-evpea5eipr52hejululr,task_subcomment,NA
+VisualEditor: Up and down cursor keys don't let you cursor from a focusable node into a slug,"Intention:
+Edit https://www.mediawiki.org/wiki/Sandbox
+
+Steps to Reproduce:
+1. Click on https://www.mediawiki.org/wiki/Sandbox?veaction=edit
+
+2. Press down arrow key.  Nothing happens.
+
+3. Press up arrow key.  Nothing happens.
+
+4.  Huh, how do I get off this template?
+
+Actual Results:  
+Left and right arrow keys take me to the slugs on either side, so why don't up and down arrow keys do the same?
+
+In my brief testing, this doesn't happen if there is an infobox and text on the page.  https://www.mediawiki.org/wiki/Sandbox is the only page that I'm sure it always happens on.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://www.mediawiki.org/wiki/Sandbox?veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57477",1394560560,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-vytwuphk2slvp4di2jdx,task_description,duplicate
+VisualEditor: Up and down cursor keys don't let you cursor from a focusable node into a slug,"**oliver.buchtala** wrote:
+
+It happened that I ran over that issue while debugging. Here some details that may help:
+
+The problem is, that after focussing 've.ce.Surface.onModelSelect()' runs into a case which seems to be dedicated to pasting situations:
+
+  ...
+  if ( next ) {
+    rangySel = rangy.getSelection( this.getElementDocument() );
+    if ( !ve.contains( this.$pasteTarget[0], rangySel.anchorNode, true ) ) {
+      ...
+    }
+  ...
+
+After that the window selection is on the paste element which will make the next up/down do nothing, but leaving the navigation to the CE.
+
+HTH,
+
+Oliver",1402581005,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vytwuphk2slvp4di2jdx,task_subcomment,NA
+VisualEditor: Link input widget sometimes picks wrong link target,"Use the VisualEditor to edit an article on mediawiki.org, enter the word ""bugzilla"" and turn it into a link (highlight, Ctrl-K). The link input widget proposes a list of link targets, starting with ""bugzilla"" (checked), ""Bugzilla/Notes/4198"" and ""Bugzilla"". Click on the third one (""Bugzilla""). With quick eyes, you will notice that ""Bugzilla/Notes/4198"" is checked instead, but the list disappears immediately and the target box contains the string ""Bugzilla"". It appears as if the desired ""Bugzilla"" had been accepted as link target. Close the link input widget and preview your changes: ""Bugzilla/Notes/4198"" is used as link target.
+
+Another instance:
+
+Go to https://en.wikipedia.org/wiki/War?veaction=edit and turn the word ""integral"" in the second paragraph into a link. The link input widget proposes a list of link targets, starting with ""integral"" (checked), ""Integral domain"" and ""Integral"". Click on the third one (""Integral""). With quick eyes, you will notice that ""Integral domain"" is checked instead, but the list disappears immediately. It then appears as if the desired ""Integral"" had been accepted as link target. Close the link input widget and preview your changes: ""Integral domain"" is used as link target.
+
+It's likely that these cases won't be reproducible for long since the suggested target list is highly dependent on the respective wiki's current set of articles.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394469360,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-qbcdetoo7qm4jdonkcjz,task_description,resolved
+VisualEditor: Link input widget sometimes picks wrong link target,Fixed as part of the general link inspector work this week.,1402551024,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qbcdetoo7qm4jdonkcjz,task_subcomment,NA
+VisualEditor: Edit notices widget should clip correctly and have a max height,"https://he.wikipedia.org/wiki/%D7%9E%D7%93%D7%99%D7%94_%D7%95%D7%99%D7%A7Sandbox?veaction=edit as an anon yields to edit notices which together are way taller than the screen, which produces really weird behavior where you can't scroll to reach the bottom part of the edit notices.
+
+Either the edit notices widget should be a ClippableElement, or it should have a max height and scroll beyond that (or both).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394231940,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-inzxqv53pmck5ixn7m3p,task_description,resolved
+VisualEditor: Edit notices widget should clip correctly and have a max height,"
+
+*** This bug has been marked as a duplicate of bug 50885 ***",1397067550,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inzxqv53pmck5ixn7m3p,task_subcomment,NA
+VisualEditor: Edit notices widget should clip correctly and have a max height,See also https://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove5?veaction=edit or https://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE8?veaction=edit for more examples. (And bug 63631 for a related bug.),1396885303,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-inzxqv53pmck5ixn7m3p,task_subcomment,NA
+VisualEditor: Edit notices widget should clip correctly and have a max height,"This bug doesn't really address the root issues here, which are that:
+* In some instances the edit notice box just needs to be wider if there's that much content to display.
+* We don't provide a way of proving VE-specific edit notices. Most notices are wrapped in coloured-margined-padded boxes which is unnecessary with our UI.",1394287105,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-inzxqv53pmck5ixn7m3p,task_subcomment,NA
+VisualEditor: Edit notices widget should clip correctly and have a max height,I prefer both.,1394233160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inzxqv53pmck5ixn7m3p,task_subcomment,NA
+"VisualEditor: The ""Insert reference"" button remains enabled in the reference dialog even if it is empty","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Reference
+3.Click on ""Apply Changes"" without inserting any content for the reference
+
+Observed Result:
+The empty reference gets added in the page and after saving it shows the error message:Cite error: Invalid <ref> tag; refs with no content must have a name; see the help page ().
+
+Expected Result:
+
+The ""Apply Changes"" button should remain disabled unless user enters any content for the reference 
+
+See the screenshot attached.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+http://en.wikipedia.beta.wmflabs.org/wiki/7thmarchrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12857}",1394219880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kxnh5pjmlmwxifaxh7ms,task_description,resolved
+"VisualEditor: The ""Insert reference"" button remains enabled in the reference dialog even if it is empty","
+
+*** This bug has been marked as a duplicate of bug 52182 ***",1401479536,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-kxnh5pjmlmwxifaxh7ms,task_subcomment,NA
+"VisualEditor: Backwards cursoring of an image inside an image's caption selects the sub-image, not the main image (and then breaks nastily)","Intention:
+Delete an image.
+
+Steps to Reproduce:
+1. Click on http://en.wikipedia.beta.wmflabs.org/w/index.php?oldid=82527&veaction=edit
+
+2. Place cursor inside the ==Referenced text== section heading.
+
+3. Press the forward arrow key a few times.  At the end of the line, you'll select the entire image-and-image-containing-caption block.  Forward-arrow once more, and you'll end up in the first paragraph.  (This is all expected behavior.) 
+
+4. If necessary, place your cursor in the first sentence after the ==Referenced text== section heading.
+
+5.  Press the back arrow key a few times.  This selects only the image that is inside the caption, not the entire two-image block.  You can remove the second image or change the caption for the first image (only) while your cursor is there.  If you keep back-arrowing, you'll eventually select the whole block, and then end up in the ==Referenced text== section heading. 
+
+
+Expected Results:  
+I expected forward- and backward- arrows to produce the same results.
+
+I like the ""backward"" result better.  Why not make it possible to edit captions simply by placing the cursor in the caption (either by clicking the caption [instead of the image] or with the keyboard)?
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394217540,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ykbhhmjodoocwvhdre4y,task_description,resolved
+"VisualEditor: Backwards cursoring of an image inside an image's caption selects the sub-image, not the main image (and then breaks nastily)",This was fixed a while ago by Ed's selection/node work.,1413329674,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ykbhhmjodoocwvhdre4y,task_subcomment,NA
+"If VisualEditor is open, it should be considered 'alreadyediting'","We deliberately don't show a CTA if they're already editing.  However, this is broken if they're editing with VE.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1394158500,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-uxy2xvq5jbknz67fn7wg,task_description,resolved
+"If VisualEditor is open, it should be considered 'alreadyediting'","Change 131315 merged by jenkins-bot:
+Don't show CTA on signup if user is editing with VE
+
+https://gerrit.wikimedia.org/r/131315",1399314680,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uxy2xvq5jbknz67fn7wg,task_subcomment,NA
+"If VisualEditor is open, it should be considered 'alreadyediting'","Change 131315 had a related patch set uploaded by Mattflaschen:
+Don't show CTA on signup if user is editing with VE
+
+https://gerrit.wikimedia.org/r/131315",1399170048,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uxy2xvq5jbknz67fn7wg,task_subcomment,NA
+"If VisualEditor is open, it should be considered 'alreadyediting'","This blocks the signup CTA experiment (https://trello.com/c/MaqpJE5f/405-create-pre-edit-anonymous-editor-signup-invitation-guided-tour), since it creates a very bad experience for people who click 'signup and edit' (the GettingStarted CTA stays open even when VE is fully loaded).",1399168603,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-uxy2xvq5jbknz67fn7wg,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image which has an full size less than the default size for example: http://en.wikipedia.beta.wmflabs.org/wiki/File:FS_barnstar.png
+It has a full size of 111x107 px which is less than the default size 220x212 px
+
+3.Now if you switch to set to custom size , it will show Size values are invalid as it is larger than the full size.
+
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Betachrome5th?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13258}",1394065020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_description,resolved
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",Verified the fix in production,1401392799,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",verified the fix in test2,1400808583,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Yes, I checked it with those images on Betalabs and looks like it got fixed with https://gerrit.wikimedia.org/r/#/c/120808/",1400702196,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Provisionally marking as FIXED, then. :-)",1400701822,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Just tested this again with the new MWImageModel, and it seems this bug is fixed.
+
+I tested on both Ló_heraldika.png and FS_barnstar.png with quick changes to the size (as before). Works properly for me in labs.",1400653179,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","This is still happening:
+
+Getting the error message ""Size values are invalid"" when I switch to custom from default tab.Also, also the default size is appearing as 220x245 px where as the full size of the image is 71x79 px (smaller than the default size)",1399573147,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","I can't replicate on master with the same image [[File:Ló_heraldika.png|thumb]]
+
+It appears in the proper size, which is much smaller than the default.",1397679865,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",This bug is happening again now in Betalabs and test2 for the image File:Ló_heraldika.png,1397517934,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",Verified the fix in production: https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1395350378,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",Verified the fix on test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394846409,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",Verified the fix on :http://en.wikipedia.beta.wmflabs.org/w/index.php?title=12thmarchchrome&veaction=edit,1394649138,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Change 118231 merged by jenkins-bot:
+Deal with images whose size is smalled than default
+
+https://gerrit.wikimedia.org/r/118231",1394647852,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Change 118231 had a related patch set uploaded by Mooeypoo:
+Deal with images whose size is smalled than default
+
+https://gerrit.wikimedia.org/r/118231",1394593813,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","I can still reproduce this bug for the same image on that page when I switch from ""Set to default size"" to ""Set Custom Size""",1394582178,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Change 117161 merged by jenkins-bot:
+Enforce width-only default size only on larger images
+
+https://gerrit.wikimedia.org/r/117161",1394487125,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Change 117161 had a related patch set uploaded by Mooeypoo:
+Enforce width-only default size only on larger images
+
+https://gerrit.wikimedia.org/r/117161",1394082122,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor:  Too many draggable image resizing handlers for frameless, frame, and basic images (thumbnails working as intended)","VisualEditor screenshot, showing number of image resizing handles in frameless vs thumb
+
+May be related to bug 62139.
+
+1.  Open a right-aligned image in VisualEditor.  Set to ""thumb"".  Count image resizing handlers (answer:  1).
+
+2.  Change image to ""frameless"".  Count image resizing handlers (answer:  4).
+
+I believe this also happens in ""frame"" and ""basic"", but it's a little hard to tell because of another bug (that sets them to full size).
+
+It would make more sense to only have one handle for this situation.  Two (on the two lower corners) might make sense for centered images.  Probably nothing should have a handle on the top corners.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13223}",1394057940,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-27nmtsor6eimhr5y7et3,task_description,resolved
+"VisualEditor:  Too many draggable image resizing handlers for frameless, frame, and basic images (thumbnails working as intended)","
+
+*** This bug has been marked as a duplicate of bug 61968 ***",1404850803,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-27nmtsor6eimhr5y7et3,task_subcomment,NA
+"VisualEditor:  Too many draggable image resizing handlers for frameless, frame, and basic images (thumbnails working as intended)","So, this seems to still happen in beta labs, but it's seems to be fixed in master.",1395082050,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-27nmtsor6eimhr5y7et3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Wikitext code:  [[File:Hedrick (1921) - Bartlett.jpg|thumb|Caption]]
+
+Original image dimensions:  920 × 1,216 pixels.
+
+VisualEditor says:  166.32302405498282 × 220 pixels.
+
+
+Please round to whole numbers of pixels.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394056320,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-surzsdxcrbzuyzqvftoa,task_description,resolved
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Change 117161 merged by jenkins-bot:
+Enforce width-only default size only on larger images
+
+https://gerrit.wikimedia.org/r/117161",1394487128,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Change 117161 had a related patch set uploaded by Mooeypoo:
+Enforce width-only default size only on larger images
+
+https://gerrit.wikimedia.org/r/117161",1394083233,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Apologies, I mean this fix: https://gerrit.wikimedia.org/r/#/c/117161/
+
+(Added Math.round() in the default size conversion in the dm)",1394083079,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"I still can't manage to replicate the bug on master or on betalabs, but in any case, height calculations are rounded in this patch: https://gerrit.wikimedia.org/r/#/c/117144/
+
+This should fix instances of this bug.",1394082965,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"I can't manage to replicate this, not even in betalabs.
+
+http://en.wikipedia.beta.wmflabs.org/wiki/User:Mooeypoo/Test?veaction=edit
+
+I get 166x220 in the media size widget...",1394060254,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Created attachment 14746
+Screen shot of VisualEditor's image dialog, under advanced settings
+
+**Attached**: {F13209}",1394056431,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Now select the image and delete it
+4.Go to the next line by pressing enter
+
+Observed Result:
+
+
+The following error appears in the console:
+
+
+Uncaught TypeError: Cannot call method 'getChildren' of null 
+Uncaught TypeError: Cannot call method 'getChildren' of null load.php:269
+ve.ce.Surface.handleEnter load.php:269
+ve.ce.Surface.onDocumentKeyDown load.php:247
+proxy load.php:10
+ve.EventSequencer.onEvent load.php:21
+(anonymous function) load.php:20
+jQuery.event.dispatch load.php:45
+elemData.handle.eventHandle
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13081}",1393974060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhrtjoratrgaaikgkpse,task_description,resolved
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1395350472,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,Verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394846255,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=12thmarchchrome&veaction=edit,1394661636,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,"Change 118340 merged by jenkins-bot:
+Fix JS error when pressing Enter with selection across multiple paragraphs
+
+https://gerrit.wikimedia.org/r/118340",1394656820,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,"Change 118340 had a related patch set uploaded by Catrope:
+Fix JS error when pressing Enter with selection across multiple paragrahps
+
+https://gerrit.wikimedia.org/r/118340",1394653745,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+"VisualEditor: Link inspector dirties links, causes dirty diffs for links with underscores","Edit a page with wikitext [[User:Trevor_Parscal|Trevor Parscal]] ([[User talk:Trevor_Parscal|talk]]). Inspect the second link (""talk""), wait for the suggestions to load, then click out of the inspector. The save button activates. Click the save button and review the diff, and you'll see that the underscore in the link target went away.
+
+Looking at the DM transaction history, the link was replaced with a newly generated annotation that doesn't have htmlAttributes and doesn't have origTitle or any of the orig* attributes.
+
+For whatever reason, this bug doesn't happen for the first link. Maybe it's because only the second link has a namespace prefix that contains a space?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:Catrope/Bug_62229",1393966320,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jluksfszdh7gv4yindcl,task_description,resolved
+"VisualEditor: Link inspector dirties links, causes dirty diffs for links with underscores","AFAICT this is now fixed, thanks be to Parsoid.",1400719999,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jluksfszdh7gv4yindcl,task_subcomment,NA
+"VisualEditor: Link inspector dirties links, causes dirty diffs for links with underscores",Is there anything for VE to do here or will it Just Work™ once Parsoid updates the production service?,1400541259,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jluksfszdh7gv4yindcl,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Now type something and open a link inspector over it
+
+Observed Result:
+
+The ""New Page"" and ""Matching Pages"" messages are not greyed out inside Link Inspector rather appearing in a more apparent style
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13045}",1393963860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eadbguwqy532rvgz6odb,task_description,resolved
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing",Verified the fix on :https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394833642,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing",verified the fix on test2,1394149517,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing",Verified the fix in Betalabs,1394139348,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing","Change 117132 merged by jenkins-bot:
+Rename OO.ui.MenuSectonItemWidget.less to the right name
+
+https://gerrit.wikimedia.org/r/117132",1394068429,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing","Change 117132 had a related patch set uploaded by Catrope:
+Rename OO.ui.MenuSectonItemWidget.less to the right name
+
+https://gerrit.wikimedia.org/r/117132",1394068172,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"For the serialization of new transclusions we'd like to have information about the preferred formatting from TemplateData:
+
+* all parameters on a single line vs. one parameter per line
+* (possibly) preferred order of parameters by key
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393951920,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4gefxwl7us64nltukoon,task_description,duplicate
+TemplateData: Provide information about preferred formatting of transclusions,Is this a dupe of T64147 ?,1445254014,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"BTW  -Question about the ""real-world"" use: I think that block  (non-inline) templates are infobox and (almost) only infobox?  if so, we can use this as heuristic for creating a bot to fill the format field in all existing templates quite easily.",1444763318,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"Change 243138 had a related patch set uploaded (by Eranroz):
+Introducing template format
+
+[[https://gerrit.wikimedia.org/r/243138]]
+",1443782340,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"Though admittedly this is really minor issue, it has a huge impact on whether VisualEditor is accepted by power users or not. Because of this issue it is actually frowned upon to create biographies with VE in de.wikipedia, users have been told already to use the normal source code editor instead.",1442564519,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,">>! In T64217#1188824, @Schnark wrote:
+> Proper formatting actually requires more information than just single line vs. one parameter per line
+
+Yes, and we are not going to implement that. We aren't going to give the community tools to enact their epic, pointless wikitext style edit wars with each other through config settings.",1442514746,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"Proper formatting actually requires more information than just single line vs. one parameter per line:
+
+* Whitespace before pipe: For templates that should have one parameter per line this will be `""\n""`, for single line templates it can be the empty string or just a space.
+* Whitespace after pipe: In most cases either an empty string or just a space.
+* Whitespace before equal sign: This may vary widely: Empty string, one space, many spaces (depending on the length of the parameter name, to align the equal signs).
+* Whitespace after equal sign: In most cases either an empty string or just a space. But this may depend on whether the parameter has a value or not, i.e. it should be possible to have a space after the equal sign iff the value isn't empty.
+
+One important example is [[https://de.wikipedia.org/wiki/Vorlage:Personendaten|Vorlage:Personendaten (de.wikipedia)]], which provides meta-data about persons (it predates Wikidata but still fits our needs much better and thus is still actively used): To make parsing these data as easy as possible the whitespace used in the template transclusion should follow exactly the documentation. This means: When somebody uses VE to insert this template, another user //will// make [[https://de.wikipedia.org/w/index.php?title=Nazira_Abdula&curid=8786932&diff=140583554&oldid=140583398|an edit]] just to remove the spaces. So it should be possible to tell VE just not to insert them in the beginning.",1428481519,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,*** Bug 63813 has been marked as a duplicate of this bug. ***,1404840904,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"(In reply to Gabriel Wicke from comment #0)
+> For the serialization of new transclusions we'd like to have information
+> about the preferred formatting from TemplateData:
+> 
+> * all parameters on a single line vs. one parameter per line
+
+Sounds sensible.
+
+> * (possibly) preferred order of parameters by key
+
+This is already done for display purposes; I imagine we should just re-use the same order?",1393952155,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Screenshot
+
+Steps to reproduce:
+
+Yet Unknown.I am getting it by following no specific steps.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12939}",1393890420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_description,resolved
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula",Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox,1394757925,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Change 117445 merged by jenkins-bot:
+Work around DOM corruption for default-sized images
+
+https://gerrit.wikimedia.org/r/117445",1394222986,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Change 117445 had a related patch set uploaded by Catrope:
+Work around DOM corruption for default-sized images
+
+https://gerrit.wikimedia.org/r/117445",1394217795,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula",verified the fix on test2,1394152716,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula",Verified the fix on betalabs  on this page: http://en.wikipedia.beta.wmflabs.org/wiki/Editcorrupted,1394150170,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Change 117144 merged by jenkins-bot:
+Work around DOM corruption for default-sized images
+
+https://gerrit.wikimedia.org/r/117144",1394071813,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Change 117144 had a related patch set uploaded by Catrope:
+Work around DOM corruption for default-sized images
+
+https://gerrit.wikimedia.org/r/117144",1394070337,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","This is not because of galleries of formulas, but because of Moriel's fixes for default images sizes in the DM. So it manifests only for images with default size.
+
+The corruption occurs because the default image size fixes overwrite Parsoid's width/height (which is reasonable) but then also send the overwritten values back to Parsoid (which is not reasonable). We should store the original values and send those back in the HTML unless the user changed something.
+
+Additionally, the default size fixes are causing us to incorrectly size images whose original size is less than 220px. An 16x16px icon, for instance, is 16x16 even though the default bounding box is 220, because default sizing never grows an image above its original size. In this case Parsoid's width/height are actually correct, but we overwrite that with the default size, and so 16x16px icons end up rendering as 220x220px in VE and look horribly pixelated.",1394062687,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Confirmed on http://en.wikipedia.beta.wmflabs.org/wiki/Editcorrupted?veaction=edit with not actual corruption, but can't reproduce locally.",1393944051,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Steps to reproduce:  (found later )
+
+1.Open a page with VE
+2.Add a formula or a gallery
+3.Save the page
+
+Observed Result:
+ ""Your edit may have been corrupted – please review before saving"" appears on the save dialog box",1393896082,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+[Regression]: VisualEditor broken on private wikis,"#1 Go to https://office.wikimedia.org/wiki/HR_Corner/Massage_Signups#Standby_list
+#2 Click edit
+
+Notice how you get a 'Error loading data from server: parsoidserver-http-curl-error: Couldn't resolve host 'HR_Corner%2FMassage_Signups'
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1393887000,PHID-USER-qmantxp3p7omhisp3qgq,PHID-TASK-ax47g3ki5ssd7peuji3p,task_description,resolved
+[Regression]: VisualEditor broken on private wikis,"Change 116792 merged by jenkins-bot:
+Really actually fix VE on private wikis
+
+https://gerrit.wikimedia.org/r/116792",1393965485,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ax47g3ki5ssd7peuji3p,task_subcomment,NA
+[Regression]: VisualEditor broken on private wikis,"Change 116792 had a related patch set uploaded by Catrope:
+Really actually fix VE on private wikis
+
+https://gerrit.wikimedia.org/r/116792",1393965285,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ax47g3ki5ssd7peuji3p,task_subcomment,NA
+[Regression]: VisualEditor broken on private wikis,"Change 116662 merged by jenkins-bot:
+Fix VisualEditor/Parsoid on private wikis
+
+https://gerrit.wikimedia.org/r/116662",1393892507,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ax47g3ki5ssd7peuji3p,task_subcomment,NA
+[Regression]: VisualEditor broken on private wikis,"Change 116662 had a related patch set uploaded by Catrope:
+Fix VisualEditor/Parsoid on private wikis
+
+https://gerrit.wikimedia.org/r/116662",1393887842,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ax47g3ki5ssd7peuji3p,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Options>Categories
+3.Try to add a category to the page
+
+Observed Result:
+Cannot place the cursor in the Add a category text box and cannot add a category
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/Newpage3rdfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F12924}",1393880460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_description,resolved
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,Verified the fix in test2,1394229704,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,Verified the fix in Betalabs,1393960326,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,Fixed in OOjs UI; will be pulled into master for MW-core later today.,1393889696,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"Change 116664 merged by jenkins-bot:
+Allow focusing of inputs in booklet layouts without continuous pages
+
+https://gerrit.wikimedia.org/r/116664",1393889517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"Change 116664 had a related patch set uploaded by Trevor Parscal:
+Allow focusing of inputs in booklet layouts without continuous pages
+
+https://gerrit.wikimedia.org/r/116664",1393889272,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"(In reply to James Forrester from comment #2)
+> Roan suggests that it may be caused by Ed's blur of surface on dialog open.
+I was wrong, it was the autofocusing of pages feature in oojs-ui, which didn't properly respect the config setting that disables it (plus had other issues). Fix inbound from Trevor.",1393889208,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,Roan suggests that it may be caused by Ed's blur of surface on dialog open.,1393881213,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"This seems to repeat for all input boxes inside Dialogs. It happens also for alternate text in Media Edit dialog and in the MediaSizeWidget in the same dialog.
+
+The values change properly through the automatic changes (by selecting different options) but the textboxes do not get focused and seem to be non responsive.",1393881062,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon","1. ""frame"" thinks you can set a size other than original size, you can't
+2. changing from ""thumbnail"" to ""frame"" doesn't hide the zoom icon
+3. changing from ""thumbnail"" or ""frame"" to border doesn't collapse the border
+4. ""border"" images come up as inline so can't be edited, even though you can convert to border from a block image
+
+I'm concerned we're merging features before they're ready. We should consider rolling back features that don't fully work yet at is looks like there's a lot still to do.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393851360,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-p4neoppdlgxnyyv67555,task_description,resolved
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon","Change 117928 merged by jenkins-bot:
+Show/hide the magnify button on type change
+
+https://gerrit.wikimedia.org/r/117928",1394485746,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon","Change 117928 had a related patch set uploaded by Mooeypoo:
+Show/hide the magnify button on type change
+
+https://gerrit.wikimedia.org/r/117928",1394484702,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon","(In reply to Ed Sanders from comment #0)
+> 1. ""frame"" thinks you can set a size other than original size, you can't
+
+Fixed.
+
+
+> 2. changing from ""thumbnail"" to ""frame"" doesn't hide the zoom icon
+
+Not fixed.
+
+> 3. changing from ""thumbnail"" or ""frame"" to border doesn't collapse the border
+
+Fixed.
+
+> 4. ""border"" images come up as inline so can't be edited, even though you can
+> convert to border from a block image
+
+Fixed.
+
+(In reply to Ed Sanders from comment #1)
+> 5. Opening the media dialog editor on a frameless centred image
+> ([[File:Example.jpg|200px|center]]) throws an exception (Cannot call method
+> 'getData' of null ve.ui.MWMediaEditDialog.js:329)
+
+Fixed.
+
+=> Re-titling.",1394082321,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon",I believe at least some of these are done in gerrit 115939.,1393867663,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon",5. Opening the media dialog editor on a frameless centred image ([[File:Example.jpg|200px|center]]) throws an exception (Cannot call method 'getData' of null ve.ui.MWMediaEditDialog.js:329),1393853079,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Create a heading
+3.Undo creating the heading and type something in that line instead
+4.Press enter
+
+Observed Result:
+Uncaught Error: Inserted data is trying to close the root node (at index 0) is appearing in the console.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Test62015&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13363}",1393636920,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h653ah4yfpixu3lyftgq,task_description,resolved
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,Verified the fix in production: https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394827288,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,Verified the fix in test2 environment,1394153181,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,Verified the fix in Betalabs,1394068269,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,"Change 116754 merged by jenkins-bot:
+Store previous range in breakpoint for undo
+
+https://gerrit.wikimedia.org/r/116754",1394049282,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,"Change 116754 had a related patch set uploaded by Esanders:
+Use previous breakpoint's range when undoing
+
+https://gerrit.wikimedia.org/r/116754",1393950356,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,"In standalone demo empty.html
+
+1. Turn on 'get range on change', observe [1,1]
+2. Create heading, observe [1,1]
+3. Undo, observe [2,2]
+
+Expected: Range is still [1,1] after undo",1393946176,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Steps to Reproduce:
+1. Open the page:  http://en.wikipedia.beta.wmflabs.org/w/index.php?oldid=81526&veaction=edit
+
+2. Scroll down to the image of an apple.
+
+3. Why is it barely visible?
+
+
+
+Reproducible: Always
+
+This happens in both Safari and Firefox, but only at beta.wmflabs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: http://en.wikipedia.beta.wmflabs.org/w/index.php?oldid=81526&veaction=edit",1393527000,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-dr3mdcdnc5tips2mh57g,task_description,resolved
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size",Verified the fix on : https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394833981,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size",Verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394066716,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 117123 merged by jenkins-bot:
+Force thumb and frameless images to default size in DM
+
+https://gerrit.wikimedia.org/r/117123",1394065049,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 117123 had a related patch set uploaded by Catrope:
+Force thumb and frameless images to default size in DM
+
+https://gerrit.wikimedia.org/r/117123",1394064922,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 117106 merged by jenkins-bot:
+Force thumb and frameless images to default size in DM
+
+https://gerrit.wikimedia.org/r/117106",1394064404,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 117106 had a related patch set uploaded by Catrope:
+Force thumb and frameless images to default size in DM
+
+https://gerrit.wikimedia.org/r/117106",1394061403,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size",Verified the fix in betalabs,1394050967,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046687,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 115939 had a related patch set uploaded by Jforrester:
+Add type 'none' to the media edit dialog
+
+https://gerrit.wikimedia.org/r/115939",1393536027,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Created attachment 14705
+Image display bug
+
+**Attached**: {F13189}",1393527050,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**Author:** `robert.labrie`
+
+**Description:**
+Intention:
+Add media with visual editor
+
+Steps to Reproduce:
+LocalSettings.php and wiresharks are attached. The MW search does work. I can do a partial name search for an image in the File namespace and it works. The gallery in mediawiki does not.
+
+Actual Results:  
+No images
+
+Expected Results:  
+Images
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1393522440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-feyxsootc5yehsnjglpn,task_description,invalid
+VisualEditor: Add media does not search local repo when MW is in root,This appears to be a core MW issue with unsupported hosting paths. Closing as INVALID.,1394727592,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"If you access the MediaWiki core api.php entry point directly in your browser, what do you get back?
+
+It should look like this: https://www.mediawiki.org/w/api.php
+
+If it doesn't then there is nothing VisualEditor can do as it means your server is not configured correctly to expose MediaWiki's entry points (perhaps you only whitelisted index.php?).
+
+This likely means other features are broken as well (the autocompleting of page names in the search box, the ""Watch this page"" button etc.).
+
+Serving the MediaWiki application directory from your document root is highly discouraged.  If you don't like exposing a /wiki/ path in URLs you can keep the application in /w/ but let Apache rewrite your urls from /Page_name to /w/index.php. That way you have both nice urls in the root, but still keep your application's internal files tucked away safely in /w. See https://www.mediawiki.org/wiki/Manual:Short_URL and related pages.",1394561612,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"(In reply to James Forrester from comment #6)
+> Moriel – was this what Gerrit change #112491 fixed?
+
+That change fixed another related bug, but apparently there are other remaining issues after that fix that I'm trying to understand. 
+
+I think it has to do with the fact the wiki is installed in the root directory. The media search seems to skip looking for files in the local repository.",1394492099,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,Moriel – was this what gerrit 112491 fixed?,1393640336,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**robert.labrie** wrote:
+
+Hi James,
+
+I'm not sure. What I do know is that VE never sends a search to the API. It does a filerepoinfo and that's the end of it. Whatever I type in the searchbox, nothing gets sent to the API.
+
+If you give me a sample querystring I'll change the srsearch param to match something that should be found and test it.",1393594146,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,Is this related to the issue we found (fixed?) in MediaWiki core recently about certain configurations of document root and the file search API?,1393540075,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**robert.labrie** wrote:
+
+My local settings file
+
+**Attached**: {F13178}",1393522748,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**robert.labrie** wrote:
+
+search pcap
+
+This is just proving that the search does work. Something is broken in the way VisualEditor calls the API, or in the results the API returns.
+
+**Attached**: {F13177}",1393522605,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**robert.labrie** wrote:
+
+visual editor pcap
+
+This shows the whole experience from clicking edit to clicking add media. You can see the call to API.php where it asks for repos, it gets nothing back.
+
+**Attached**: {F13176}",1393522556,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates","Right now you can re-position an inline transclusion in the same way as images, with a click-drag feature. Unfortunately this isn't set for block transclusions.
+
+This is particularly irritating for suers because when you initially insert a transclusion we assume it's inline, so let them move it, but then when they re-open the page it's now magically un-moveable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1393521720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_description,resolved
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates",I'm declaring that it was.,1408650245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates",Was this fixed by the changes to GCNs?,1404934961,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates","The problem here is not block templates, but that the CE HTML is <div wrapper><table float:right/></div>, and the relocatable marker takes it's dimensions from the <div> (which has no height).
+
+In ProtectedNode we solve this by drawing boxes around _every_ descendent. Ideally we'll come up with a better solution before we start add drag handlers to them.",1393611288,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates","Abandoned that, the test case I was using appears to be an edge case, it actually works ok.",1393607320,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates",Disable on block images for now: https://gerrit.wikimedia.org/r/#/c/116118/,1393605930,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates","Relocatable doesn't work on block elements atm. We have it enabled for block images, but it breaks.",1393605805,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image 
+3.Make it frameless
+4.Keep on resizing down the image going beyond 1x1 px.
+5.Click anywhere on the page
+
+Observed Result:
+
+The image becomes a dot size . and user can no more select or find Media Settings icon for it.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13101}",1393459860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nfrfujiczibmostmogl4,task_description,resolved
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,Sorry on:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394833482,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nfrfujiczibmostmogl4,task_subcomment,NA
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,Verified the fix in production:http://en.wikipedia.beta.wmflabs.org/wiki/Slug?veaction=edit,1394833422,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nfrfujiczibmostmogl4,task_subcomment,NA
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,Verified the fix in test2 environment.,1394153006,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nfrfujiczibmostmogl4,task_subcomment,NA
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,Verified the fix in Betalabs,1394068793,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nfrfujiczibmostmogl4,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references","Invalid input
+
+Steps to reproduce:
+
+1.Open a page with VE which has multiple references
+2.Go to Insert>Reference>Use an existing reference
+3.Now input something in the search box which will have no search result
+4.Now cross out the dialog box
+5.Again go to Insert>Reference
+
+Observed Result:
+The ""Use an existing reference"" button is disabled and it does not become enabled for the rest of the session unless user cancels the edit and reopen the page again with VE
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13055}",1393448280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_description,resolved
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references",Verified the fix in test2 :https://test2.wikipedia.org/wiki/Wmf19?veaction=edit,1395356010,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references","Change 119702 merged by jenkins-bot:
+Don't use search widget emptiness as a proxy for ""no reusable references""
+
+https://gerrit.wikimedia.org/r/119702",1395294643,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references","Change 119702 had a related patch set uploaded by Catrope:
+Don't use search widget emptiness as a proxy for ""no reusable references""
+
+https://gerrit.wikimedia.org/r/119702",1395294485,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references","Created attachment 14692
+Disabled ""Use an existing reference"" button
+
+**Attached**: {F13056}",1393448346,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_subcomment,NA
+VisualEditor: Breaking words on diacritics,"VisualEditor breaking words on diacritics
+
+A user was trying to remove the duplicated header which is on section ""Propriedades Algébricas"" of
+https://pt.wikipedia.org/wiki/Logaritmo?oldid=38172637&veaction=edit
+
+After deleting the duplicated cells, Visual Editor also removes part of a word from the previous paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://pt.wikipedia.org/w/index.php?title=Logaritmo&diff=38264880&oldid=38264877
+
+**Attached**: {F13042}",1393436040,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-pgrl2ozbdinedqyu3zhp,task_description,resolved
+VisualEditor: Breaking words on diacritics,"I suspect this had nothing to do with diacritics, but was because there was unbalanced wikitext. It looks like Parsoid outputs that particular wikitext differently now anyway. Suggest WONTFIX.",1408119118,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pgrl2ozbdinedqyu3zhp,task_subcomment,NA
+Move EventLogging component from MediaWiki extensions product to Analytics product,"Move EventLogging component from MediaWiki extensions product to Analytics product, as requested via email.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1393417560,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwug2jk4wwdhybwdo5mt,task_description,resolved
+Move EventLogging component from MediaWiki extensions product to Analytics product,"I'm still trying to adjust to VisualEditor being a product instead of a component under ""MediaWiki extensions."" Now I'll have to add a mental exception for EventLogging as well. Blergh.",1393562759,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jwug2jk4wwdhybwdo5mt,task_subcomment,NA
+Move EventLogging component from MediaWiki extensions product to Analytics product,Done.,1393419433,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwug2jk4wwdhybwdo5mt,task_subcomment,NA
+ApiQueryLogEvents STRAIGHT_JOIN queries slow,"enwiki has been seeing a bunch of slow ApiQueryLogEvents queries:
+
+SELECT /* ApiQueryLogEvents::execute */ /*! STRAIGHT_JOIN */ log_type, log_action, log_timestamp, log_deleted, log_id, page_id, log_user, log_user_text, user_name, log_namespace, log_title, log_comment, log_params FROM `logging` LEFT JOIN `user` ON ((user_id=log_user)) LEFT JOIN `page` ON ((log_namespace=page_namespace) AND (log_title=page_title)) INNER JOIN `change_tag` ON ((log_id=ct_log_id)) WHERE (log_type != 'suppress') AND ct_tag = 'Possible self promotion in userspace' ORDER BY log_timestamp DESC LIMIT 11
+
+SELECT /* ApiQueryLogEvents::execute */ /*! STRAIGHT_JOIN */ log_type, log_action, log_timestamp, log_deleted, log_namespace, log_title, ts_tags FROM `logging` LEFT JOIN `user` ON ((user_id=log_user)) LEFT JOIN `page` ON ((log_namespace=page_namespace) AND (log_title=page_title)) LEFT JOIN `tag_summary` ON ((log_id=ts_log_id)) INNER JOIN `change_tag` ON ((log_id=ct_log_id)) WHERE (log_type != 'suppress') AND ct_tag = 'VisualEditor' ORDER BY log_timestamp DESC LIMIT 11
+
+... and several other similar forms.
+
+In all cases the STRAIGHT_JOIN forces an index scan on logging.times index, or more rarely a range access on logging.type_time index. Both query plans hit tens of millions of rows and take many minutes.
+
+Removing the STRAIGHT_JOIN allows the MariaDB query optimizer to choose a plan that takes seconds. Often it includes a filesort step, but more importantly it allows ""index condition pushdown"" which makes the filesort cheap.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: major",1393296960,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-7oof4yk2z7twkxa4m44m,task_description,resolved
+ApiQueryLogEvents STRAIGHT_JOIN queries slow,"Change 115381 merged by Springle:
+Remove STRAIGHT_JOIN from ApiQueryLogEvents
+
+https://gerrit.wikimedia.org/r/115381",1393375751,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7oof4yk2z7twkxa4m44m,task_subcomment,NA
+ApiQueryLogEvents STRAIGHT_JOIN queries slow,"Change 115381 had a related patch set uploaded by Anomie:
+Remove STRAIGHT_JOIN from ApiQueryLogEvents
+
+https://gerrit.wikimedia.org/r/115381",1393340810,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7oof4yk2z7twkxa4m44m,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which contains an image
+2.Select the image
+3.Go to Insert>References List
+
+Observed Result:
+The Save page button becomes active though there is no new reflist got added.If you click on ""Review Your Changes"" on the Save Dialog box, it will say 
+""Could not start the review because your revision matches the latest version of this page""
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12904}",1393288440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_description,resolved
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active",Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1398379382,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active",Verified the fix in test2,1397867310,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active",Verified the fix on Betalabs,1397512208,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active","Change 125799 merged by jenkins-bot:
+Fix inserting references list while selecting another kind of node
+
+https://gerrit.wikimedia.org/r/125799",1397504972,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active","Change 125799 had a related patch set uploaded by Trevor Parscal:
+(Bug 61885) Inserting ref list while selecting another kind of node
+
+https://gerrit.wikimedia.org/r/125799",1397504587,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+VisualEditor:  Don't set STATICREDIRECT if there's no redirect on the page,"Steps to reproduce:
+1.  Start with a blank page.
+
+2.  Go to Page settings.
+
+3.  Tick both redirect-related boxes, but don't provide a page name.
+
+4.  Apply changes.
+
+
+Results:
+It sets __STATICREDIRECT__, which is not pointful on an otherwise blank page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61864",1393271280,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-hixhmoom5yqrm66bfq43,task_description,resolved
+VisualEditor:  Don't set STATICREDIRECT if there's no redirect on the page,"Change 115239 merged by jenkins-bot:
+Don't let the user set a static redirect flag on a non-redirect
+
+https://gerrit.wikimedia.org/r/115239",1393279753,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hixhmoom5yqrm66bfq43,task_subcomment,NA
+VisualEditor:  Don't set STATICREDIRECT if there's no redirect on the page,"Change 115239 had a related patch set uploaded by Jforrester:
+Don't let the user set a static redirect flag on a non-redirect
+
+https://gerrit.wikimedia.org/r/115239",1393272739,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hixhmoom5yqrm66bfq43,task_subcomment,NA
+VisualEditor:  Don't set STATICREDIRECT if there's no redirect on the page,Hmm. This shouldn't be possible – I think this is the same issue as bug 61864.,1393271388,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hixhmoom5yqrm66bfq43,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,"In the ""Page settings"" dialog, it says ""Redirect this page to"" and a blank field for the target name.  If you put a name in there, then it sets a redirect, even if you don't tick the checkbox.  
+
+VisualEditor should automatically tick the checkbox there if it's going to set a redirect (e.g., as soon as you start typing).  Otherwise, it looks like it's not going to redirect the page when you exit the dialog box.
+
+(Reproducing this has only been consistent if there is no redirect on the page at the start of the editing session.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61865",1393270920,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_description,resolved
+VisualEditor: Disable the redirect input field unless the checkbox is checked,verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Imageghau,1393546614,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,"Change 115237 merged by jenkins-bot:
+Disable redirect field unless the checkbox is set in setup
+
+https://gerrit.wikimedia.org/r/115237",1393279661,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,"Change 115237 had a related patch set uploaded by Jforrester:
+Disable redirect field unless the checkbox is set in setup
+
+https://gerrit.wikimedia.org/r/115237",1393272601,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,*** Bug 61866 has been marked as a duplicate of this bug. ***,1393272393,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,"The logic for this box is meant to work the other way around - that is, you can't set a redirect unless you check the box first - but a simple forgotten line made this not work in one (very frequent) case: when the page isn't a redirect and you're making it one. Whoops. :-(",1393272380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"Intention:
+Add one ref
+
+Steps to Reproduce:
+1. Opened an existing ref, copied the contents, and cancelled out of the dialog.
+
+2. Opened a new ref, pasted what I'd just copied, changed the contents slightly, and applied changes.
+
+
+Actual Results:  
+All the <ref name = whatever> tags on the page were ""corrected"".
+
+Expected Results:  
+Nothing would change in paragraphs that I didn't touch.
+
+Reproducible: Didn't try
+
+This is presumably a regression, but search couldn't find any bugs containing the word ""name"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=912199&oldid=840682",1393017180,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_description,declined
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"I, too, can't reproduce – possibly a Parsoid deployment cache artefact? Closing as WFM.",1393355731,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"I can't reproduce this today in Safari (which is what I was using at the time), either.  Perhaps it has been fixed already?  Perhaps there's something unfortunately subtle about it (e.g., must click eleven times first, only on the night before the last quarter of the Moon)?",1393355173,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"Can't reproduce using that specific revision of the page, and the same edit, either in FF or Chrome.",1393345365,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"(In reply to WhatamIdoing from comment #2)
+> https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/
+> Sandbox&diff=912199&oldid=840682
+
+Very odd. Seems to be something on that page triggering the behaviour?",1393021033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=912199&oldid=840682,1393020870,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"I tried this on MediaWiki.org, following your steps with this edit: https://www.mediawiki.org/w/index.php?title=VisualEditor:TestReferenceContents&diff=912228&oldid=768024
+
+As you can see, I couldn't reproduce. Can you give a link to a page where this happens?",1393017648,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+"VisualEditor: If the edit summary is empty, don't show a preview of it (""()"") in the Review Changes panel","Screenshot
+
+Do no Show empty summary preview: () when there is no summary in Review Changes dialog box
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13076}",1392940980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6m7f64h6b4dqidv7aoqk,task_description,resolved
+"VisualEditor: If the edit summary is empty, don't show a preview of it (""()"") in the Review Changes panel",Verified the fix in betalabs,1393277147,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6m7f64h6b4dqidv7aoqk,task_subcomment,NA
+"VisualEditor: If the edit summary is empty, don't show a preview of it (""()"") in the Review Changes panel","Change 114737 merged by jenkins-bot:
+Don't show edit summary preview if it's blank
+
+https://gerrit.wikimedia.org/r/114737",1393083591,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6m7f64h6b4dqidv7aoqk,task_subcomment,NA
+"VisualEditor: If the edit summary is empty, don't show a preview of it (""()"") in the Review Changes panel","Change 114737 had a related patch set uploaded by Alex Monk:
+Don't show edit summary preview if it's blank
+
+https://gerrit.wikimedia.org/r/114737",1392987765,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6m7f64h6b4dqidv7aoqk,task_subcomment,NA
+"VisualEditor: Copy/pasting blanks page, prevents saving","Reported on fr.wp:
+<<Here is how I did : on the page https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Ch%C3%A2teau_Rothschild_(Boulogne-Billancourt) opened with VE, ""Historique"" section, copy from ""Joseph Fleuriau d'Armenonville"" to ""évoqua brièvement le lieu."" Then paste it somewhere on the page https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Brouillon [it's a sandbox, it's ok to test there], and everything will be deleted. 
+I also noticed that a few times nothing was deleted but nothing was pasted too. [...]
+I have the same bug with FF 29 with both W7 and W8.1, and also Chrome 32 with W7. Nemesis III (me contacter), le 19 février 2014 à 19:16 (CET). >>
+
+I reproduced this as well.
+In addition, the first time it didn't blank the destination page, and the same happened on one of my sandboxes. Then one time it blanked the page, allowed me to save, I got the confirmation message but nothing was recorded (the history doesn't have signs of this).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392835080,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nn2dv56qvs3mjvm533mq,task_description,declined
+"VisualEditor: Copy/pasting blanks page, prevents saving",Can't reproduce.,1409070187,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nn2dv56qvs3mjvm533mq,task_subcomment,NA
+"VisualEditor: Copy/pasting blanks page, prevents saving","This is happening elsewhere as well.
+I was testing if you can copy/paste a reference from a VE instance on one wiki to another (from sv.wp to it.wp).
+Sometimes it takes a lot for the save dialog to appear; in other cases the action just leads to page blanking.",1395751667,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nn2dv56qvs3mjvm533mq,task_subcomment,NA
+VisualEditor: Shift-selection of a template and then typing-replacement can cause pawns in Firefox,"VEdit https://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove2?veaction=edit in Firefox.
+
+Place your cursor right below the initial template, press Shift and the Up arrow to select it, type something = pawn.
+
+NicoV, who found this, says you can also start from the line above the template, Shift + Down arrow in that case.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58675
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54917",1392821340,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-q4ectqywx354prbxw6g6,task_description,resolved
+VisualEditor: Shift-selection of a template and then typing-replacement can cause pawns in Firefox,This is fixed now.,1406598517,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q4ectqywx354prbxw6g6,task_subcomment,NA
+VisualEditor: Shift-selection of a template and then typing-replacement can cause pawns in Firefox,"Simple test case:
+{{Simple table include}}
+Foo
+
+Place the cursor before 'Foo', press up (shift not requred) and type.
+
+Interestingly if the block template is float right it works fine.",1392828352,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-q4ectqywx354prbxw6g6,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add a text with reference
+3.Add a reflist
+4.Go to the next line of the text with reference and add an image
+5.Go to the Media settings of the image and set the alignment to left(This should move the image between reference and reflist , instead it distorts the reflist position and it appears just beside the image instead of appearing below it)
+6.Save the page
+7.Reopen the page
+8.Try to the position of reflist it by pressing enter 
+
+Observed Result:
+No newline gets entered , an error appears in the console:
+Uncaught TypeError: Cannot call method 'getModel' of null 
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Anotherdeep?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13298}",1392770580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kc7quhrwey6274zbvvpw,task_description,resolved
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return",This issue got resolved with  bug 59911,1393635082,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return","The pressing-enter-in-the-slug bug is I think bug 59911, so merging with that.
+
+*** This bug has been marked as a duplicate of bug 59911 ***",1393474403,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return","I don't see anything wrong with the rendering, it looks pretty similar to the PHP parser output. The pressing-enter-in-the-slug bug is a problem though.",1392915710,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return","(In reply to ryasmeen from comment #1)
+> This is also happening when the first element of a page is image and you try
+> to press enter to go to the next line
+
+Correction: When the first element of a page is a left aligned image",1392857061,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return",This is also happening when the first element of a page is image and you try to press enter to go to the next line,1392856767,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","pawn before the link
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Create a link
+3.Type something just before the link
+4.Type something just after the link
+4.Click on ""Undo"" several times
+
+Observed Result:
+
+A pawn appears right before and after the link 
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=18thfebchrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13288}",1392762420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_description,resolved
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action",No pawns now.,1421282614,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","I'm not taking this bug either, but I can reproduce it -if I make the link in the block slug-. Which I wasn't doing when I tested this before.",1416333719,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","Created attachment 17150
+video capture of the bug
+
+See the video capture attached
+
+**Attached**: {F13290}",1416266032,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action",I just reproduced this on Chrome in Betalabs,1416265954,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","Tried again, seems fixed.",1416184177,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action",Cannot reproduce.,1415813522,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","I might be reopening the wrong bug, but this doesn't seem to be fixed.
+
+1) VEdit any article on the French Wikipedia.
+2) Type some words exactly before a wikilinked single word. (Based on my tests, it doesn't really matter if we add one word or several ones.)
+3) Undo your edit with the related keyboard shortcut or the Undo button: a pawn will appear. Undo again, the pawn might disappear, undo one more time, it appears again, etc.
+I was able to reproduce with Vector and Safari.",1410170185,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action",I think this is now fixed.,1406599124,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","Created attachment 14622
+Pawn after the link
+
+**Attached**: {F13289}",1392762479,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+VisualEditor: Moving templates down is broken,"1. Go to template dialog
+2. Insert two templates (or a template and a content item, or whatever)
+3. Click the bottom one and click the up arrow to move it up; this works
+4. Click the top one and click the down arrow; nothing happens
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392420840,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vsxmfaftb5u77hxjzrlr,task_description,resolved
+VisualEditor:  Box for alt text in the media dialog is too small,"This is related to bug 38129.
+
+The alt text box in the media dialog is only about two-thirds the width of the screen, with no possibility of wrapping/scrolling down.  Maybe eight words fit in it (two-thirds of the example given in the lead of https://en.wikipedia.org/wiki/WP:ALT).  
+
+It should be at least the normal width of the dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392317880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-2lbvzwvr2rcpaahfrzu7,task_description,resolved
+VisualEditor:  Box for alt text in the media dialog is too small,Verified the fix in test2,1392940065,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2lbvzwvr2rcpaahfrzu7,task_subcomment,NA
+VisualEditor:  Box for alt text in the media dialog is too small,"Change 114022 merged by jenkins-bot:
+Make alternate text input stretch to full width
+
+https://gerrit.wikimedia.org/r/114022",1392758254,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2lbvzwvr2rcpaahfrzu7,task_subcomment,NA
+VisualEditor:  Box for alt text in the media dialog is too small,"Change 114022 had a related patch set uploaded by Mooeypoo:
+Make alternate text input stretch to full width
+
+https://gerrit.wikimedia.org/r/114022",1392752877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2lbvzwvr2rcpaahfrzu7,task_subcomment,NA
+VisualEditor:  Don't specify the default alignment for images (in the resulting wikitext),"This is related to bug 51293, bug 61323, and the general bug 38129:
+
+The alignment options in the media dialog's advanced settings are:
+
+Left
+Center
+Right
+None
+
+It is the convention to not specify the alignment when choosing the default, mostly to avoid needless clutter in the wikitext.  If the default is right (or left), and the user chooses that default, then VisualEditor should not add ""right"" but instead should leave the alignment setting empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392315180,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6xlmfh5z7qar45y5xdva,task_description,resolved
+VisualEditor:  Don't specify the default alignment for images (in the resulting wikitext),*** Bug 61565 has been marked as a duplicate of this bug. ***,1393447031,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6xlmfh5z7qar45y5xdva,task_subcomment,NA
+VisualEditor:  Don't specify the default alignment for images (in the resulting wikitext),Done last week (I think).,1393446964,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6xlmfh5z7qar45y5xdva,task_subcomment,NA
+"VisualEditor:  Provide a button in the image dialog box's advanced settings to set ""default"" alignment for images","This is related to bug 51293 and the general bug 38129:
+
+The alignment options in the media dialog's advanced settings are:
+
+Left
+Center
+Right
+None
+
+These are the four explicit settings provided in MediaWiki.
+
+Most users, even if they click on a few buttons to consider other options, are going to want the image at the default (i.e., on the right for left-to-right languages).  It is the convention to not specify the default, mostly to avoid needless clutter in the wikitext.
+
+Most users have no idea what ""None"" does because they've never encountered it before.  They're going to think that it means ""unspecified default"", rather than left-and-clear.  
+
+It would be good to offer a ""default"" button, even though this duplicates the function of one of the existing buttons.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392315060,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-p4knbm6poo246efefsph,task_description,resolved
+"VisualEditor:  Provide a button in the image dialog box's advanced settings to set ""default"" alignment for images",Verified the fix in betalabs.,1393546976,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p4knbm6poo246efefsph,task_subcomment,NA
+"VisualEditor:  Provide a button in the image dialog box's advanced settings to set ""default"" alignment for images",*** Bug 56609 has been marked as a duplicate of this bug. ***,1393528443,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p4knbm6poo246efefsph,task_subcomment,NA
+"VisualEditor:  Provide a button in the image dialog box's advanced settings to set ""default"" alignment for images",Done in gerrit 114420.,1393446852,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p4knbm6poo246efefsph,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","Actual Results:  
+You can only see about 1.5 lines of text.  It should be tall enough to display two lines of text, even if people are using slightly larger fonts.
+
+
+Reproducible: Always
+
+Multiple complaints with screenshots:
+
+https://en.wikipedia.org/wiki/File:Euromaidan_VisualEditor_infobox.PNG
+
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_13#Multiple_issues_-_minimal_space
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60541",1392253440,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rfnk22psp766igbje5es,task_description,resolved
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","Cool, please keep no limit for the size, some template have a lot of content :
+https://fr.wikipedia.org/w/index.php?title=Espèces_du_genre_Carex&oldid=96878307&veaction=edit",1393544143,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured",*** Bug 61859 has been marked as a duplicate of this bug. ***,1393271161,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","As of gerrit 114527 parameter value boxes will now auto-size (without maximum), and when empty (or have a short value) will show as just a single line (actually ""normal size"" which is ~1.5x in height).
+
+(In reply to WhatamIdoing from comment #2)
+> Other suggestions from en.wp:
+>  
+> * At least three lines tall.
+
+I think that's too large for default; most parameter values are simple entries (e.g. a file name or an author's surname). We want filling in the fields to seem like a quick, easy thing to do, not an overwhelming prompt to write an essay. However, we could possibly bump the minimum size to larger than 1.5x, though I'd still be worried about making them too large. Note the size of the boxes in the sketch of the citation dialog by way of example: https://www.mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog#mediaviewer/File:VE-reference-dailog-design-04b.png – this change was done as part of that work. I suggest we re-visit this if it doesn't feel like it's working out very well.
+
+
+> * Scrollbars as needed.
+
+Right now they'll just grow without limit, which means if it's such an insanely large parameter value that it's larger than the dialog it will get scrollbars, but otherwise it will just grow. Maybe we could set a maximum size (10 lines? 5?) and then scroll when larger than that? Perhaps something for another bug?
+
+
+> * Ability to resize the window vertically.
+
+Which ""window""? The dialog itself, or the text box? If the latter, that's now done; if the former, I don't think that that's a reasonable outcome (because it breaks the design for mobile, limited vision users, and others with small screen sizes, and because it's Yet Another Control for users to have to understand what it does, why they'd use it, and how it works).
+
+
+> * Replace the grey area between parameters by a line (less space wasted, as
+> readable as before), don't use large padding inside the fields, reduce white
+> space between parameter name and value.
+
+The first and third of these points is also being done as part of the citation dialog work; if anything, we're probably going to increase the padding on the input boxes in line with that work, though.
+
+
+Am thus closing this bug as FIXED for now, with an adjustment to the title to reflect the design decision, and we can open further bugs for other ideas.",1393009160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","Other suggestions from en.wp:
+ 
+* At least three lines tall.
+
+* Scrollbars as needed.
+
+* Ability to resize the window vertically.
+
+* Replace the grey area between parameters by a line (less space wasted, as readable as before), don't use large padding inside the fields, reduce white space between parameter name and value.",1392750930,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","We may want to re-visit this when these boxes are rich content, but whilst as wikitext they're likely to be expansive more often than not.",1392352160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Screenshot
+
+Steps to reproduce:
+
+1.Open this page with VE:http://en.wikipedia.beta.wmflabs.org/wiki/12thfebchrome?veaction=edit
+
+2.Go to the Media Settings for the image:[[File:Dau ho thoi Ho.png]]
+
+3.Set the Width size of the image to 8000 and Apply changes (Works fine)
+
+4.Set the Width of the image to 8000000 and apply changes (Still work fine)
+
+
+5.Set the Width of the image to 80000000 and Apply changes 
+
+Observed Result:
+The image shrinks to a dot size in the VE mode
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13328}",1392233220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gczwgyrlggneqddarcum,task_description,resolved
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"This looks like it's now fixed, I think.",1404850639,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Created attachment 14785
+Reproduced on windows8-chrome
+
+**Attached**: {F13330}",1394478635,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"I can't replicate here; I set the image even up to ""800000000000000000000"" width and still it resized as ""expected"".",1394413820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Created attachment 14761
+This is how it appears in the review changes in the save dialog
+
+**Attached**: {F13329}",1394133756,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"I see this image as a huge one. There is a bug here that the context menu is hidden outside the page (should be reported separately) but I don't see this as a dot-size.
+
+Checked under Windows on Chrome version 33.0.1750.146 m and Firefox 27.0.1
+
+In both cases, I see this image as humongous, which is exactly as it appears in the ""view"" mode. 
+
+I can't manage to replicate the ""dot-image"" effect.",1394070360,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,Another page and image where I encountered this issue: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Hateres&veaction=edit,1394069805,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,I can still reproduce this issue for the image :[[File:Dau ho thoi Ho.png]] with Frame and Basic Image type,1394064287,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046682,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Change 115939 had a related patch set uploaded by Mooeypoo:
+[wip] Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1393991570,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,I can still reproduce this issue.,1393459000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Change 115307 merged by jenkins-bot:
+Limit thumbnail dimensions in media edit dialog
+
+https://gerrit.wikimedia.org/r/115307",1393447584,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Change 115307 had a related patch set uploaded by Mooeypoo:
+[wip] Limit thumbnail dimensions in media edit dialog
+
+https://gerrit.wikimedia.org/r/115307",1393279148,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"I can't replicate the exact phenomenon, but it does seem to show an issue with maximum dimensions.
+
+When I increase the size (even to the 80000000 width) I just get a humongous version of the stretched image. 
+
+I'm looking into the conditions of limiting image scale size.",1393275231,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen","Intention:
+edit Polish Wikipedia using VisualEditor
+
+Steps to Reproduce:
+1. difflink 1: https://pl.wikipedia.org/w/index.php?title=Amalowie&diff=38322555&oldid=38322515
+2. difflink 2: https://pl.wikipedia.org/w/index.php?title=Amalowie&diff=prev&oldid=38322515
+3. discussion link: https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Edytor_wizualny_psuje_przypisy
+
+Actual Results:  
+snowmen appear (see difflink 1) and text disappears or ""gets eaten""
+
+Expected Results:  
+no snowmen and text is inserted where it is wanted
+
+Reproducible: Didn't try
+
+please see bug:54712 and bug:54976 re: snowmen
+
+please see bug:51624 and bug:50286 re: backspace
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Edytor_wizualny_psuje_przypisy",1392226980,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-7l43lybihonkgrfu2q5d,task_description,declined
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen","I played around a bit with Chrome, Firefox and Opera and couldn't reproduce. Closing as WORKSFORME, but that feels bad…",1395252569,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7l43lybihonkgrfu2q5d,task_subcomment,NA
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen","I /think/ the editor replied that that problem didn't occur again since, and that he doesn't want to test further. If you want you can play with my sandbox at https://pl.wikipedia.org/wiki/Wikipedysta:Elitre_(WMF)/sandbox or just close this provisionally. Thanks.",1395239221,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7l43lybihonkgrfu2q5d,task_subcomment,NA
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen",I asked for details at pl.wp.,1395232579,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7l43lybihonkgrfu2q5d,task_subcomment,NA
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen",Difficult to do anything without steps to reproduce...,1395230444,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7l43lybihonkgrfu2q5d,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Misaligned Undo/Re-do buttons at Beta Labs
+
+The Undo/re-do buttons aren't lined up properly in the toolbar at Beta Labs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13192}",1392142980,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-thvvordl2hv7kcsai3bw,task_description,resolved
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112946 abandoned by Jforrester:
+Fix margins after they were broken in 9d988924
+
+Reason:
+Whoops, this is wmf13 only.
+
+https://gerrit.wikimedia.org/r/112946",1392239534,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112814 merged by jenkins-bot:
+Fix margins after they were broken in 9d988924
+
+https://gerrit.wikimedia.org/r/112814",1392239524,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112947 had a related patch set uploaded by Jforrester:
+Fix margins after they were broken in 9d988924
+
+https://gerrit.wikimedia.org/r/112947",1392239463,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112946 had a related patch set uploaded by Jforrester:
+Fix margins after they were broken in 9d988924
+
+https://gerrit.wikimedia.org/r/112946",1392239439,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112814 had a related patch set uploaded by Jforrester:
+Fix margins after they were broken in 9d988924
+
+https://gerrit.wikimedia.org/r/112814",1392160140,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Resolved in Ie6b47f5d1929533669118ba51202c1fccda4a0d6
+
+Basically, Liangent made a change to the padding of the content div Vector and didn't make a corresponding change to the toolbar in the VisualEditor extension.",1392156068,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: [Regression] Link inspector prevents addition of section links to existing links,"Take text. Make link to page (""Foo""). Observe wikitext. Good.
+
+Take text. Make link to page with section (""Foo#Bar""). Observe wikitext. Bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1392138660,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-evpxmbfxyief5l7gsbk6,task_description,resolved
+VisualEditor: [Regression] Link inspector prevents addition of section links to existing links,Fixed in gerrit 112898.,1392231577,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-evpxmbfxyief5l7gsbk6,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings>Advanced Settings for that image
+4.Select the option Border under Image Type
+
+Observed Result:
+There is no value/Change appears for this image type
+The resulting wikitext is:
+[[File:Wheat (flo).JPG|200x200px||left]]
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=10thFeb&action=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392064020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kuwpox6ibgr56bpzslcr,task_description,resolved
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755538,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,Verified the fix in test2,1394228977,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,Verified the fix in Betalabs,1394051975,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046685,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Change 115939 had a related patch set uploaded by Mooeypoo:
+[wip] Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1393628853,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Created attachment 14708
+Screenshot
+
+**Attached**: {F13029}",1393539331,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Still not working for me.I could still reproduce it in page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27thfebff&action=edit
+
+See the screenshot attached",1393539304,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Change 112041 merged by jenkins-bot:
+Revamp media edit dialog's position widget
+
+https://gerrit.wikimedia.org/r/112041",1392940263,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Change 112041 had a related patch set uploaded by Jforrester:
+Revamp media edit dialog's position widget
+
+https://gerrit.wikimedia.org/r/112041",1392162364,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Found the bug, the wikitext doesn't have |border even though the CE is updated.
+
+This commit seems to fix it: https://gerrit.wikimedia.org/r/#/c/112041/",1392160784,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,Cannot replicate in master in both Chrome 32 and Firefox 27 under Ubuntu.,1392155939,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Resize text in Option menu or put it on two lines if too long,"In French, the option to switch to wikitext is called ""Basculer vers la modification du code"". In Italian, it's ""Passa alla modifica sorgente"".
+In both languages the text is so long you need to slide to the right to see all of it. Is there a better way to display it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392060000,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_description,resolved
+VisualEditor: Resize text in Option menu or put it on two lines if too long,"Merging into bug 57366.
+
+*** This bug has been marked as a duplicate of bug 57366 ***",1401743910,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_subcomment,NA
+VisualEditor: Resize text in Option menu or put it on two lines if too long,"I spent a while looking into this. I gave up but here is what I found anyway
+
+First of all I tried to make it expand outwards instead of squashing against the side, and couldn't get that to work.
+
+Then I tried making the text wrap instead, found I could set the white-space CSS property on the tool title which kind of did the job, but it was not working well enough (last word of a wrapped line would overflow). I found word-break: break-word; but that only made things look worse.",1398977073,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_subcomment,NA
+VisualEditor: Resize text in Option menu or put it on two lines if too long,"I asked on fr.wp. On the Italian one, this is still the case with Monobook, but Vector displays the message just fine...",1394615953,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_subcomment,NA
+VisualEditor: Resize text in Option menu or put it on two lines if too long,Could we improve the translations to be briefer?,1394502042,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","In mobile various JavaScript and CSS modules are loaded that are not needed including OO JS UI.css (see https://gerrit.wikimedia.org/r/#/c/109940/)
+
+After talking to Trevor and Timo we agreed that it would be a good idea to refactor and break out many of VisualEditor's modules to support a much slimmer mobile version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391820360,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_description,resolved
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS",Done.,1393464256,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","Change 113488 merged by jenkins-bot:
+Split up ext.visualEditor.mwcore into smaller parts
+
+https://gerrit.wikimedia.org/r/113488",1393464108,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","Change 113487 merged by jenkins-bot:
+Split VE-MW's ve.ce.Node.css file into per-node files
+
+https://gerrit.wikimedia.org/r/113487",1392932889,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","Change 113488 had a related patch set uploaded by Jforrester:
+Split up ext.visualEditor.mwcore into smaller parts
+
+https://gerrit.wikimedia.org/r/113488",1392423592,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","Change 113487 had a related patch set uploaded by Jforrester:
+Split VE-MW's ve.ce.Node.css file into per-node files
+
+https://gerrit.wikimedia.org/r/113487",1392423585,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Link inspector ""Matching/redirect/disambiguation page"" messages should be pluralized","""visualeditor-linkinspector-suggest-matching-page"": ""Matching page"",
+""visualeditor-linkinspector-suggest-disambig-page"": ""Disambiguation page"",
+""visualeditor-linkinspector-suggest-redirect-page"": ""Redirect page""
+
+These messages should be something like {{PLURAL:$1|Matching page|Matching pages}} instead, and be passed the number of pages in the section.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391818380,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-32vq2w6nrmkqhr2ecptb,task_description,resolved
+"VisualEditor: Link inspector ""Matching/redirect/disambiguation page"" messages should be pluralized","Change 112164 merged by jenkins-bot:
+Pluralise visualeditor-linkinspector-suggest-(matching|redirect|disambig)-page
+
+https://gerrit.wikimedia.org/r/112164",1391822396,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-32vq2w6nrmkqhr2ecptb,task_subcomment,NA
+"VisualEditor: Link inspector ""Matching/redirect/disambiguation page"" messages should be pluralized","Change 112164 had a related patch set uploaded by Alex Monk:
+Pluralise visualeditor-linkinspector-suggest-(matching|redirect|disambig)-page
+
+https://gerrit.wikimedia.org/r/112164",1391819746,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-32vq2w6nrmkqhr2ecptb,task_subcomment,NA
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image
+3.Open the media settings for that image
+4.Go to Advanced Settings tab
+5.Change the image size to something different than what it is right now
+6.Click on ""Apply Changes""
+7.Reopen the Media Settings again and go to Advanced Settings panel
+
+Observed Results:
+The Size values are still reflecting the previous value unless user saves the whole page and open the panel again it stays like this.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit#cite_ref-2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391803020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-boiihq6lvygsgus2qbrt,task_description,resolved
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,Verified the fix on test2,1392253579,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-boiihq6lvygsgus2qbrt,task_subcomment,NA
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,"Change 112950 merged by jenkins-bot:
+Quick fix: image size property update
+
+https://gerrit.wikimedia.org/r/112950",1392242431,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-boiihq6lvygsgus2qbrt,task_subcomment,NA
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,"Change 113014 had a related patch set uploaded by Catrope:
+Quick fix: image size property update
+
+https://gerrit.wikimedia.org/r/113014",1392242394,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-boiihq6lvygsgus2qbrt,task_subcomment,NA
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,"Change 112950 had a related patch set uploaded by Mooeypoo:
+Fix image size property update
+
+https://gerrit.wikimedia.org/r/112950",1392239704,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-boiihq6lvygsgus2qbrt,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE which contains a image at the right
+
+2.Select the image 
+
+3.Go to the Media Settings> Advanced Settings
+
+4.Move the position of the image to center
+
+5.Select some other element or just click outside the image anywhere on the page
+
+
+Observed result:
+Cannot select any other object in the page 
+An error appears in the console:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 227
+
+See the screenshot attached.
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Ehat?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13303}",1391732220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yk5ghixsbt7pcjv7wois,task_description,resolved
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,verified the fix in test2,1392943781,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,"Change 113258 merged by jenkins-bot:
+Prevent clicks on top-most shield for centered image nodes
+
+https://gerrit.wikimedia.org/r/113258",1392854973,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,I believe that gerrit 113256 fixed part of this issue.,1392748429,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,"Change 113258 had a related patch set uploaded by Jforrester:
+Prevent clicks on top-most shield for centered image nodes
+
+https://gerrit.wikimedia.org/r/113258",1392748207,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,It happens while moving an image from Left to Right too,1391732797,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Format action applies to nodes inside handlesOwnChildren node,"1. Select a block image with caption
+2. Press the list button
+
+Expected:
+Either nothing, or a list is created above/below the image
+
+Observed:
+The caption is wrapped in a list
+
+Clearly we need to ignore nodes which are inside handlesOwnChildren nodes when applying such actions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60804",1391704140,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-p6nh7m7ljbshvwyj2lmd,task_description,resolved
+VisualEditor: Format action applies to nodes inside handlesOwnChildren node,"Change 111822 merged by jenkins-bot:
+Don't descend into handlesOwnChildren nodes in selectNodes
+
+https://gerrit.wikimedia.org/r/111822",1391803183,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6nh7m7ljbshvwyj2lmd,task_subcomment,NA
+VisualEditor: Format action applies to nodes inside handlesOwnChildren node,I'm assuming that bug 60804 the same issue.,1391708410,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6nh7m7ljbshvwyj2lmd,task_subcomment,NA
+VisualEditor: Format action applies to nodes inside handlesOwnChildren node,"Change 111822 had a related patch set uploaded by Esanders:
+Don't descend into handlesOwnChildren nodes in selectNodes
+
+https://gerrit.wikimedia.org/r/111822",1391707727,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6nh7m7ljbshvwyj2lmd,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"See 
+https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE3&diff=63988076&oldid=63988055 ,
+or https://it.wikipedia.org/w/index.php?title=Oreste_Tommasini&diff=63836558&oldid=61161898, or https://it.wikipedia.org/w/index.php?title=Frederic_William_Maitland&diff=63692381&oldid=59785358 .
+
+Reproduced with Chrome, FF, Opera (unlogged), tested with both skins.
+
+You only need to add the Template:Interprogetto to an existing page or a new one.
+Useless code like <span data-ve-ignore=""true"" about=""g0.8632714317645878""></span> is added.
+James, bug 59653, IMHO, had a similar problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60375",1391610120,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ypnibbwkhkctaw6xxskl,task_description,resolved
+VisualEditor: HTML content model constraints are sometimes violated,"Change 111518 merged by jenkins-bot:
+Only generate transclusion contents for clipboard
+
+https://gerrit.wikimedia.org/r/111518",1391641350,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"Change 111518 had a related patch set uploaded by Esanders:
+Only generate transclusion contents for clipboard
+
+https://gerrit.wikimedia.org/r/111518",1391632112,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"(In reply to comment #5)
+> Is Bug 60375 related?
+
+Looks like it.",1391630206,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,Moving it back to VE.,1391626970,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,Is Bug 60375 related?,1391626108,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,This is scenario #3 from https://www.mediawiki.org/wiki/Parsoid/DOM_notes#Efficient_re-rendering_on_edits,1391621996,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"So this is caused by new templates always being inline templates, as we don't know if they are block templates until they render. As a result the above HTML is invalid (<ul> inside a <p>) which after Parsoid fixes, means the about-grouped items are no longer siblings.",1391621604,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"This extra HTML is correctly added here for the sake of putting something meaningful into the external clipboard. data-ve-ignore tells the converter to ignore it if it's pasted into another VE instances, and about=""g[random]"" tells Parsoid to ignore it. However the about grouping appears not to be working at Parsoids end:
+
+HTML:
+<p><span about=""g1"" typeof=""mw:Transclusion"" data-mw=""{&quot;parts&quot;:[{&quot;template&quot;:{&quot;target&quot;:{&quot;href&quot;:&quot;Template:Interprogetto&quot;,&quot;wt&quot;:&quot;Interprogetto&quot;},&quot;params&quot;:{&quot;commons&quot;:{&quot;wt&quot;:&quot;cats&quot;}}}}]}"" data-ve-no-generated-contents=""true""></span><span data-ve-ignore=""true"" about=""g1""></span><ul data-ve-ignore=""true"" about=""g1"">
+<li>Foo</li>
+</ul>
+<span data-ve-ignore=""true"" about=""g1"">
+
+</span></p>
+
+Wikitext:
+{{Interprogetto|commons = cats}}
+* Foo
+
+<span data-ve-ignore=""true"" about=""g1""></span>
+
+The first about-grouped sibling is discarded, but the subsequent ul and span are not.",1391619704,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"There was a related issue beforehand – but this isn't getting copied, so I can't work out out data-ve-ignore is getting added to the HTML?",1391618697,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"link text appearing for the second time
+
+Steps to reproduce:
+
+1.Select a math function/image/gallery/hiero
+2.Now open the link inspector
+3.Insert a link (this link gets placed just before the selected element)
+4.Again select the element
+5.Open the link inserter
+6.Observe that the link title of the previous link is appearing now in the link inspector
+7.Close the link inspector.
+
+Observed Result:
+The link text title of the previous link is getting inserted just before the selected element.
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Image_then_gallery?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12936}",1391544360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-f6765ahcloqg4k3lhy2n,task_description,resolved
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Verified the fix in production,1411682155,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Verified the fix in test2,1411082475,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Verified the fix in Betalabs,1410981634,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,I can't reproduce. Probably fixed by Ed's recent cleanup of the link inspector.,1410955005,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"Never mind, I'm an idiot. It's still broken if you try to inspect the same reference with the link inspector twice in a row.",1408732836,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Confirmed fixed in master but not in wmf18.,1408732672,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,I think this is fixed now? I can't reproduce it any more...,1408690676,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Roan says the fix is to fix the pre-population of the link inspector in create mode. I think.,1406144930,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Selection's not being re-set to the actual link (of the pre-annotation stack or something odd)?,1405969347,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,This is not yet fixed.The link text is still getting added next to the previously added link,1402700275,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"Change 138114 merged by jenkins-bot:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533853,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"Change 138114 had a related patch set uploaded by Catrope:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533735,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"Created attachment 14487
+link text getting added before math function
+
+**Attached**: {F12937}",1391544477,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Images trigger creation of huge protectedNode-shields that cover the page,"Any time I try to use the mobile VisualEditor on a page that includes an image, it is not editable due to having a protectedNode-shield covering most of the page. You can see an example at:
+https://en.m.wikipedia.org/wiki/Rice_flour#editor/0
+
+The protectedNode-shield has a width of 100% and a height of 100% and it appears that each image creates a new one.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1391542860,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ark2omnqbkzm4rckjjjm,task_description,resolved
+VisualEditor: Images trigger creation of huge protectedNode-shields that cover the page,"**jgonera** wrote:
+
+Fix in https://gerrit.wikimedia.org/r/#/c/113475/",1392420075,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ark2omnqbkzm4rckjjjm,task_subcomment,NA
+VisualEditor: Images trigger creation of huge protectedNode-shields that cover the page,*** Bug 60103 has been marked as a duplicate of this bug. ***,1391647241,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ark2omnqbkzm4rckjjjm,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Intention:
+Add a gallery
+
+Steps to Reproduce:
+1. Open a page in Safari.
+
+2. Go to Insert > Gallery
+
+3. Type in the name of an image and a caption.  *Don't click or type anywhere else after this.*
+
+4. Click on the save button.
+
+5. Realize that the gallery dialog is still open, so cancel the save box.  The dialog will close and the gallery will display.
+
+6. Click on the save button again.
+
+Actual Results:  
+The gallery displays on screen, but is not present in Review Changes or when the page is saved.
+
+If you click outside the gallery dialog after typing the name, or if you click the mysterious < button, then it works as expected.
+
+Expected Results:  
+A button at the bottom of the gallery inserter that says ""Insert this gallery now"".
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67049",1391540760,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-d6fvkqxdzbk3emadetgp,task_description,resolved
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Change 112893 merged by jenkins-bot:
+Give the document focus on save dialog open to resolve inspectors
+
+https://gerrit.wikimedia.org/r/112893",1392229720,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","(In reply to comment #6)
+> 2. OOUI defers the close event of the dialog by 250ms for animation purposes,
+> after which we set up a one-time listener to surface-transact to clear the
+> serialization cache, but the transaction has already happened.
+> 
+Is there an event / method in OOUI (closing as opposed to close, maybe?) that fires before the animation? Then we could listen to that and immediately attach the event listener.",1392229631,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","1. The document is given focus, triggering events which result in the inspectors being closed, and a transaction being created which inserts the extension node.
+2. OOUI defers the close event of the dialog by 250ms for animation purposes, after which we set up a one-time listener to surface-transact to clear the serialization cache, but the transaction has already happened.
+
+Fix:
+Give the document focus before opening the save dialog to make sure it's in a more stable state.",1392214713,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Change 112893 had a related patch set uploaded by Esanders:
+Give the document focus on save dialog open to resolve inspectors
+
+https://gerrit.wikimedia.org/r/112893",1392214526,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Actually the CE and DM aren't out of sync, but the new document isn't being passed to Parsoid.",1392137057,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Yuck.
+
+Clicking out of an inspector *into the surface* causes the inspector to close, applying changes.
+
+Clicking out of an inspector *outside the surface* (such as the save dialog launcher) causes the inspector to not close; when the save dialog is closed, this also closes the inspector and ""insert"" the content into CE but NOT DM, causing them to get out of sync. Not good.",1391661572,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","More Observation: This issue happens for all other inspector for example: Math,Hiero, Link inspector.",1391547427,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Created attachment 14483
+Screenshot displaying a visible gallery, and displaying the absence of the gallery in the wikitext code
+
+**Attached**: {F12922}",1391540887,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a image
+3.Open the media settings for the image
+4.Insert a link as a caption
+5.Save the page
+6.Reopen the page and select the image
+7.Open the link inspector and type in a different a link inside it
+8.Save the page
+9.Reopen the page and the Media Settings for the image
+
+Observed Result:
+The link inside the caption got changed by the link inserter in step 7
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60969
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58045",1391480580,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dstdh5ubda4mfhlddsus,task_description,resolved
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,Verified the fix in production,1397177603,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,Verified the fix in mediawiki.org,1396992640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,"Change 123429 merged by jenkins-bot:
+Skip over handlesOwnChildren nodes in newFromAnnotation
+
+https://gerrit.wikimedia.org/r/123429",1396469415,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,"Change 123429 had a related patch set uploaded by Esanders:
+Skip over handlesOwnChildren nodes in newFromAnnotation
+
+https://gerrit.wikimedia.org/r/123429",1396469204,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,If there are multiple links inside the media caption then the link applied outside the image gets applied to all other links .,1396385672,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,"Created attachment 14472
+Screenshot of the error
+
+**Attached**: {F12832}",1391480774,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor:  It should not be possible to paste images from external websites into the references dialog,"Intention:
+Replicate a mess seen at https://pt.wikipedia.org/w/index.php?title=Esporte_Clube_Pelotas&curid=68824&diff=38075497&oldid=38075466
+
+Steps to Reproduce:
+1. Start creating a new reference.
+2. Open nytimes.com and select both some text and one small image. 
+3. Copy the selection and paste it into the ref dialog box.
+
+Actual Results:  
+In Safari, nothing pastes.  In Firefox, both text and image rich-paste into the ref dialog box, but I can't save the page.
+
+Expected Results:  
+That the image would be discarded, since it's not uploaded to the wiki.
+
+Reproducible: Sometimes
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391457300,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wkw5zbjzhfqvkpwqq4dz,task_description,resolved
+VisualEditor:  It should not be possible to paste images from external websites into the references dialog,Verified in betalabs.,1414093606,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-wkw5zbjzhfqvkpwqq4dz,task_subcomment,NA
+VisualEditor:  It should not be possible to paste images from external websites into the references dialog,"AFAICT this is now completely fixed; however, in testing this I uncovered bug 72385 which is sigh-inducing.",1414011221,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wkw5zbjzhfqvkpwqq4dz,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"**As an editor I can get paste a link or DOI into a simple form to get an auto-filled citation.**
+
+A user has their cursor in a place they would like to add a citation. 
+They click the Cite button on the toolbar. 
+An inspector opens in context, showing the title ""Cite"" a URL field, and a ""Lookup"" button.
+
+Click-through prototype http://invis.io/HR2DK2FXM
+
+**Workflow**
+{F55330}
+
+**Detail of citation inspector**
+Include line below field with link that opens the manual citation dialogue.
+{F45790}
+
+**Manual Citation Dialogue**
+First step now includes all items in the former Cite menu
+{F43867}
+
+**Errors**
+DOI error - if incorrect amount of characters entered
+{F43776}
+
+URL error - if page not found
+{F45749}
+
+Generic error
+{F45752}
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391446500,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yko76gbkbhubxt5cplo5,task_description,resolved
+Cite: Auto-filled references based on destination URL / DOI etc.,">>! In T62768#1138925, @Mvolz wrote:
+> FYI citoid does not support ISBNs yet so I edited that bit out- very surprised to find out we supported ISBNs when I read the tech bulletin on my RSS reader this morning, and it was probably because it was in the description here. 
+
+Thank you for the heads-up. I wasn't sure we'd be announcing this in Tech News, because I was confused about the status of this feature, due to last week's rushed deployment. This is why this task was marked as ""Not ready to announce"" (which does apply to Tech News). On Friday, James added the item to the newsletter, and I edited it to use simpler language; I also added the ISBN bit, based on this task's title.
+
+> @gpaumier Also, I noticed this is tagged ""not ready to announce"" yet - does that not apply to tech bulletin? If so there's still technically time to remove it because even though it ended up in my RSS reader, because publication is not technically until tomorrow. 
+
+Yes, however we can't make last-minute edits to the newsletter because that only changes the English version; translators need more time to echo the changes.
+
+Considering that:
+* the current text is inaccurate and could cause confusion if sent,
+* the current text only concerns two wikis that have already been notified of the feature,
+* and there is no urgency in sending this information,
+I've removed the Citoid item from this week's issue entirely, and added it to the list of items to announce in next week's newsletter.
+",1427122926,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Elitre, I agree. It hasn't been re-triggered for translation yet so there
+is still time to remove that link.",1427026425,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"(I find the link to the [[ https://www.mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog | design page ]] confusing. Some parts of the interface are different in production - and the last 2 screenshots on the page would show the regular Cite flow - which is not so ""connected"" to Citoid.)",1427026149,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"FYI citoid does not support ISBNs yet so I edited that bit out- very surprised to find out we supported ISBNs when I read the tech bulletin on my RSS reader this morning, and it was probably because it was in the description here. 
+
+@gpaumier Also, I noticed this is tagged ""not ready to announce"" yet - does that not apply to tech bulletin? If so there's still technically time to remove it because even though it ended up in my RSS reader, because publication is not technically until tomorrow. ",1427013644,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"FYI citoid does not support ISBNs yet so I edited that bit out- very surprised to find out we supported ISBNs when I read the tech bulletin on my RSS reader this morning, and it was probably because it was in the description here. Also, I noticed this is tagged ""not ready to announce"" yet - does that not apply to tech bulletin? If so there's still technically time to remove it because even though it ended up in my RSS reader, because publication is not technically until tomorrow. ",1427013067,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 198261 abandoned by Mooeypoo:
+Add general citations dialog
+
+Reason:
+Not needed.
+
+[[https://gerrit.wikimedia.org/r/198261]]",1426898858,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 198261 had a related patch set uploaded (by Mooeypoo):
+Add general citations dialog
+
+[[https://gerrit.wikimedia.org/r/198261]]
+",1426873551,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 197925 merged by jenkins-bot:
+Enable Citoid extension on all VisualEditor wikis
+
+[[https://gerrit.wikimedia.org/r/197925]]",1426780531,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 197925 had a related patch set uploaded (by Alex Monk):
+Enable Citoid extension on all VisualEditor wikis
+
+[[https://gerrit.wikimedia.org/r/197925]]
+",1426780007,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 197074 merged by jenkins-bot:
+Enable Citoid extension on all VisualEditor wikis
+
+[[https://gerrit.wikimedia.org/r/197074]]",1426778958,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 195802 merged by jenkins-bot:
+Redesign the citation widget in the citoid inspector
+
+[[https://gerrit.wikimedia.org/r/195802]]",1426552347,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 196645 merged by jenkins-bot:
+Add general citations dialog
+
+[[https://gerrit.wikimedia.org/r/196645]]",1426551858,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 197074 had a related patch set uploaded (by Jforrester):
+Enable Citoid extension on all VisualEditor wikis
+
+[[https://gerrit.wikimedia.org/r/197074]]
+",1426523008,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 196645 had a related patch set uploaded (by Mooeypoo):
+[wip] Add general citations dialog
+
+[[https://gerrit.wikimedia.org/r/196645]]
+",1426278790,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 195802 had a related patch set uploaded (by Mooeypoo):
+Redesign the citation widget in the citoid inspector
+
+[[https://gerrit.wikimedia.org/r/195802]]
+",1426030328,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,">>! In T62768#1094741, @Eloquence wrote:
+> Can we project a ""week of"" deployment ETA?
+
+No. Everything is backed up on {T89656} which has an unknown schedule.",1425684052,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Can we project a ""week of"" deployment ETA?",1425610555,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Hi Marielle,
+I think we should leave the user on the same screen, in case they messed up the number and want to try again. 
+We should show an error message that says something like ""We couldn't find that book"" and maybe give a hint like ""An ISBN is usually 10 or 13 digits.""
+And the user still has the option at the bottom to go to the screen to enter the citation manually.
+{F20069}",1418077680,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Hi Kaity,
+
+What should the user see if there are no results?
+
+For most urls I think it should just be the linked url, and then they can edit that, but for some identifiers (like issn, isbn) it's definitely possible there won't be anything to display at all. And we may or may not know what kind of ID it is (although we could guess?) I'm assuming it should go to this page https://www.mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog#mediaviewer/File:Magic_cite4-02.png automatically but should there be some sort of error message or something....
+
+Also it's possible that if the scraping is bad- i.e. it's just the text of the url as the title- these automatically are set as web citations, but it's possible the user will want to change the citation type from web to journal, for instance. Any thoughts on that?",1417693157,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,,1417555606,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,,1417554442,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"(In reply to WhatamIdoing from comment #0)
+> It would be convenient if the reference tool would autofill {{cite book}}
+> from a URL to books.google.com  This is done in several existing gadgets on
+> the English Wikipedia and is especially helpful for books that do not have
+> ISBNs.
+
+Czech Wikipedia could be filled from national book database. I think their API might be available to us as we were already negotiating with them. Basically every time I fill reference template and also ISBN variable I wonder, why this cant be done automaticaly as in many countries such data are available and readable for scripts.
+
+But what Ive been talking about in https://bugzilla.wikimedia.org/show_bug.cgi?id=60863
+
+was just to load some basic options and than the user should file them by values. But this proposal is even better.",1392633415,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,*** Bug 60863 has been marked as a duplicate of this bug. ***,1391708860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,This is part of bug 50768's re-written merged form; am re-splitting and using this one for the second half.,1391448623,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+VisualEditor: VE doesn't load on mobile anymore,"http://en.m.wikipedia.beta.wmflabs.org/wiki/Forty-seven_Ronin?mobileaction=alpha#editor/0
+
+Error: Container must be attached to the DOM Error {stack: (...), message: ""Container must be attached to the DOM""}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391133180,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_description,resolved
+VisualEditor: VE doesn't load on mobile anymore,"Change 110498 merged by jenkins-bot:
+Fix VE error with latest VE master
+
+https://gerrit.wikimedia.org/r/110498",1391191162,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_subcomment,NA
+VisualEditor: VE doesn't load on mobile anymore,"Change 110498 had a related patch set uploaded by JGonera:
+Fix VE error with latest VE master
+
+https://gerrit.wikimedia.org/r/110498",1391135465,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_subcomment,NA
+VisualEditor: VE doesn't load on mobile anymore,"@Juliusz: Looks like the .surface element selector here is either not finding anything at all or it is referring to something that is still detached at that point:
+
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/blob/c4264d76bc817df71c6b3631afb19be737246c52/javascripts/modules/editor/VisualEditorOverlay.js#L16
+
+It doesn't have to be fully initialised, but the target container element should however be somewhere in the document.",1391134025,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_subcomment,NA
+VisualEditor: VE doesn't load on mobile anymore,"This is exposing a pre-existing bug in mobile VE or MobileFrontend's VE integration or something in this ecosystem: you cannot initialize targets into a container that isn't already attached to the DOM. Previously, you could do this and various things regarding measurements would just break and render wrong, but now we throw an exception.",1391133988,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_subcomment,NA
+VisualEditor: Closing a Math inspector deletes the selected node/element,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Now select an image or a reference note in the Page
+3.Now Open the Gallery from Insert>Gallery
+
+Observed Result:
+
+It deletes the image and the reference note.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391023680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ddwzsz5d7gwehcqqwr6x,task_description,resolved
+VisualEditor: Closing a Math inspector deletes the selected node/element,This was fixed a while ago by Ed.,1402296411,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ddwzsz5d7gwehcqqwr6x,task_subcomment,NA
+VisualEditor: Closing a Math inspector deletes the selected node/element,And then close the Math inspector.,1391023868,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ddwzsz5d7gwehcqqwr6x,task_subcomment,NA
+VisualEditor: Closing a Math inspector deletes the selected node/element,"Sorry the third step should be ""Insert>Formula""",1391023807,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ddwzsz5d7gwehcqqwr6x,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"The CSS file modules/ve-mw/ce/styles/ve.ce.Node.css implements styling of page content. This styling should be handled by the skin, not by VisualEditor. It looks like someone already figured this out, as most of the styles include TODO notes about merging them into core styles.
+
+As the mobile team is now implementing VE with a mobile-specific skin, now would be the best time to make these fixes. Otherwise, lots of !important overrides will be necessary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390944600,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-lmv6en7m2i2nthp4bbad,task_description,resolved
+VisualEditor: Let skin variance for styling of <figures> in page content,"Change 112618 merged by jenkins-bot:
+Move some skin styling from ve.ce.Node.css to a shared skin css file
+
+https://gerrit.wikimedia.org/r/112618",1392845587,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"Change 112618 had a related patch set uploaded by Kaldari:
+Move some skin styling from ve.ce.Node.css to the skin styles
+
+https://gerrit.wikimedia.org/r/112618",1392081287,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"Talked to Roan. He definitely favors solution 2 and gave me some advice on implementing it. Apparently VE already has some skin styling in it (modules/ve-mw/init/styles/), so most of these styles should just be moved there.",1392062806,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"There are two possible solutions:
+
+1. Make VE's page DOM more similar to the normal rendered page DOM. That way VE won't have to worry about styling them as they'll be styled by existing skin styles. (This seemed to be a solution favored by Trevor.)
+
+2. Add support for some VE-specific elements to the skins, for example, figure elements. (This seemed to be a solution favored by Roan.)
+
+Probably the best solution is a combination of both. I would be happy to help with solution 2, although it would be nice to get some guidance from the VE team on what approach (or approaches) they would prefer to see (and possibly help implement).",1392061761,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"What's the solution to this issue, though? Re-write MW's skins to work with nodes? 'Cos right now they don't…
+
+""Fix MW's skin system"" is a bit of a large tangential bug.",1392060050,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text for example: ""link with wikitext""
+3.Press command+k to apply link on it
+4.Without adding anything just close the inspector.
+5.Save the page.
+6.Reopen the page in VE
+
+Observed Result:
+The wikitext for the link is appearing in Read mode and in VE
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13098}",1390511280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3dkpw6uttju4ehjxawfk,task_description,resolved
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,Verified the fix on test2 and mw.org,1391123930,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3dkpw6uttju4ehjxawfk,task_subcomment,NA
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,Verified the fix on Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Jan_27th?veaction=edit,1390862978,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3dkpw6uttju4ehjxawfk,task_subcomment,NA
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,"Change 109738 merged by jenkins-bot:
+Followup 7994eae8c2: fix MWLinkInspector breakage
+
+https://gerrit.wikimedia.org/r/109738",1390857396,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3dkpw6uttju4ehjxawfk,task_subcomment,NA
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,"Change 109738 had a related patch set uploaded by Catrope:
+Followup 7994eae8c2: fix MWLinkInspector breakage
+
+https://gerrit.wikimedia.org/r/109738",1390857192,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3dkpw6uttju4ehjxawfk,task_subcomment,NA
+VisualEditor:  Adding a template and removing a non-breaking space (nbsp) causes span tags with data-ve-ignore,"Intention:
+Add a template and remove a non-breaking space (&nbsp;) in the same line/paragraph
+
+Steps to Reproduce:
+(Order matters!)
+
+1.  Begin with a page that contains the HTML code for a non-breaking space.  Open in VisualEditor.
+
+2.  On the line that contains the nbsp, add a template (e.g., {{fact}}).  The template should be added to the same 'word' that contains the nbsp.
+
+3.  Then remove the nbsp (replace with a plain space, or just delete the whole 'word').
+
+Actual Results:  
+VisualEditor added span text like <span about=""g0.42287685585435686"" data-ve-ignore=""true""></span> when the nbsp was removed.
+
+Adding a fact template to the end of:
+
+1&nbsp;mg 2&nbsp;mg 3&nbsp;mg 4&nbsp;mg
+
+turns into:
+
+1&nbsp;mg 2&nbsp;mg 3&nbsp;mg 4 mg{{Fact}}<span data-ve-ignore=""true"" about=""g0.5170239245053381""></span>
+
+However, adding the template to ""3 mg"" and deleting the nbsp from ""2 mg"" works correctly:
+
+1&nbsp;mg 2 mg 3&nbsp;mg{{Fact}} 4&nbsp;mg
+
+
+
+
+Reproducible: Always
+
+See https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=591972176&oldid=591955710 and testing at https://en.wikipedia.org/w/index.php?title=User:Jay8g/sandbox&action=history on 23 January 2014 for many more details.
+
+Found in Firefox 26 on Windows 7 with Monobook, confirmed in Safari 6 on Mac OS 10.8.5 with Vector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60897",1390506600,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-h52lnxgvppaohab4kg6x,task_description,resolved
+VisualEditor:  Adding a template and removing a non-breaking space (nbsp) causes span tags with data-ve-ignore,"From following WhatAmIDoing's instructions, I can replicate in enwiki and it's fixed in Beta Labs; marking as FIXED.",1391668943,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h52lnxgvppaohab4kg6x,task_subcomment,NA
+VisualEditor:  Adding a template and removing a non-breaking space (nbsp) causes span tags with data-ve-ignore,"Probably a duplicate of bug 60897
+
+See if the fix there resolves this.",1391633551,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-h52lnxgvppaohab4kg6x,task_subcomment,NA
+VisualEditor:  Adding a template and removing a non-breaking space (nbsp) causes span tags with data-ve-ignore,"This also appears if you add any template after a {{convert}} template, and then remove the {{convert}} template.
+
+If there are multiple nbsp's on the same line, them it is only the removal of the nbsp that is immediately before the template that appears to trigger it.",1390581096,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-h52lnxgvppaohab4kg6x,task_subcomment,NA
+"VisualEditor:  ""Edit"" tab not appearing sometimes","Reproducible: Didn't try
+
+Two editors report that VisualEditor's ""Edit beta"" tab occcasionally does not appear on their screens.  Both were using Firefox on Windows 7.  The button reappeared upon refreshing the screen, or spontaneously reappeared the next day.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1390436160,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-xe24oejtt6ji24d5t62v,task_description,resolved
+"VisualEditor:  ""Edit"" tab not appearing sometimes","I'm presuming that this is a duplicate of bug 54706.
+
+*** This bug has been marked as a duplicate of bug 54706 ***",1397067449,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xe24oejtt6ji24d5t62v,task_subcomment,NA
+"VisualEditor:  ""Edit"" tab not appearing sometimes",It happened to one of them again.,1391037771,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-xe24oejtt6ji24d5t62v,task_subcomment,NA
+"VisualEditor:  ""Edit"" tab not appearing sometimes","Possibly a JS transmission error; without detailed information we'll never have any idea what caused it, but let's keep this open in case there are further reports.",1390442979,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xe24oejtt6ji24d5t62v,task_subcomment,NA
+importImages.php broken on cluster,"reedy@tin:/tmp/uploads$ sudo -u apache mwscript importImages.php --wiki=commonswiki --user=""Jdforrester_(WMF)"" /tmp/uploads
+Import Images
+
+Importing linux.conf.au 2014 - VisualEditor presentation.ogv...PHP Warning:  fopen(/tmp/uploads/linux.conf.au 2014 - VisualEditor presentation.ogv): failed to open stream: Permission denied in /a/common/php-1.23wmf10/includes/filebackend/SwiftFileBackend.php on line 278
+
+Warning: fopen(/tmp/uploads/linux.conf.au 2014 - VisualEditor presentation.ogv): failed to open stream: Permission denied in /a/common/php-1.23wmf10/includes/filebackend/SwiftFileBackend.php on line 278
+done.
+
+Found: 1
+Added: 1
+reedy@tin:/tmp/uploads$
+
+
+The added is a lie. The upload didn't complete, it's a 404
+
+https://upload.wikimedia.org/wikipedia/commons/e/ea/Linux.conf.au_2014_-_VisualEditor_presentation.ogv
+
+404 Not Found
+
+The resource could not be found.
+
+File not found: /v1/AUTH_mw/wikipedia-commons-local-public.ea/e/ea/Linux.conf.au_2014_-_VisualEditor_presentation.ogv
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60777",1390354860,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_description,resolved
+importImages.php broken on cluster,"Change 111116 merged by Aaron Schulz:
+Fixes and cleanups to FileOpBatch
+
+https://gerrit.wikimedia.org/r/111116",1391470291,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111115 merged by jenkins-bot:
+Use ""rb"" instead of ""rb+"" for Swift store operation handles
+
+https://gerrit.wikimedia.org/r/111115",1391469961,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 110993 merged by jenkins-bot:
+Use ""rb"" instead of ""rb+"" for Swift store operation handles
+
+https://gerrit.wikimedia.org/r/110993",1391469906,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111116 had a related patch set uploaded by Aaron Schulz:
+Fixes and cleanups to FileOpBatch
+
+https://gerrit.wikimedia.org/r/111116",1391469439,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111115 had a related patch set uploaded by Aaron Schulz:
+Use ""rb"" instead of ""rb+"" for Swift store operation handles
+
+https://gerrit.wikimedia.org/r/111115",1391469425,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111111 merged by jenkins-bot:
+Fixes and cleanups to FileOpBatch
+
+https://gerrit.wikimedia.org/r/111111",1391469371,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111111 had a related patch set uploaded by Aaron Schulz:
+Fixes and cleanups to FileOpBatch
+
+https://gerrit.wikimedia.org/r/111111",1391468881,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 110993 had a related patch set uploaded by Aaron Schulz:
+Use ""rb"" instead of ""rb+"" for Swift store operation handles
+
+https://gerrit.wikimedia.org/r/110993",1391459513,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"(In reply to comment #2)
+> I don't see any way around getting errors when trying to upload files as a
+> user
+> that can't see them. What exactly is this about?
+
+The behaviour changed at some point (I didn't have to change file permissions before). But even with read for everyone on /tmp/uploads, it doesn't work with errors.
+
+There is a related error that the uploads apparently succeed, even though they weren't imported.
+
+
+reedy@tin:/tmp/uploads$ sudo -u apache mwscript importImages.php --wiki=commonswiki --user=""Odder"" /tmp/uploads
+Import Images
+
+Importing 2014 State Of The Union Address Enhanced.webm...PHP Warning:  fopen(/tmp/uploads/2014 State Of The Union Address Enhanced.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+
+Warning: fopen(/tmp/uploads/2014 State Of The Union Address Enhanced.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+done.
+Importing 2013-10-05 President Obama's Weekly Address.webm...PHP Warning:  fopen(/tmp/uploads/2013-10-05 President Obama's Weekly Address.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+
+Warning: fopen(/tmp/uploads/2013-10-05 President Obama's Weekly Address.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+done.
+Importing 2013-10-12 President Obama's Weekly Address.webm...PHP Warning:  fopen(/tmp/uploads/2013-10-12 President Obama's Weekly Address.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+
+Warning: fopen(/tmp/uploads/2013-10-12 President Obama's Weekly Address.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+done.
+
+Found: 3
+Added: 3
+reedy@tin:/tmp/uploads$ ls -al
+total 2404792
+drwxrwxrwx  2 reedy wikidev      4096 Feb  3 18:47 .
+drwxrwxrwt 46 root  root        12288 Feb  3 18:46 ..
+-rw-rw-r--  1 reedy wikidev      1255 Feb  1 14:50 2013-10-05 President Obama's Weekly Address.txt
+-rw-rw-r--  1 reedy wikidev 163504321 Jan 27 22:13 2013-10-05 President Obama's Weekly Address.webm
+-rw-rw-r--  1 reedy wikidev      1197 Feb  1 14:52 2013-10-12 President Obama's Weekly Address.txt
+-rw-rw-r--  1 reedy wikidev 158637780 Feb  1 14:34 2013-10-12 President Obama's Weekly Address.webm
+-rw-rw-r--  1 reedy wikidev       884 Jan 31 16:26 2014 State Of The Union Address Enhanced.txt
+-rw-rw-r--  1 reedy wikidev 909068945 Jan 30 19:37 2014 State Of The Union Address Enhanced.webm
+-rw-r--r--  1 reedy wikidev 909060459 Feb  3 18:45 SOTU.tar.gz
+-rw-r--r--  1 reedy wikidev 322185685 Feb  3 18:46 WeeklyAddresses.tar.gz
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$ chmod 777 *
+reedy@tin:/tmp/uploads$ rm *.gz
+reedy@tin:/tmp/uploads$ ls -al
+total 1202392
+drwxrwxrwx  2 reedy wikidev      4096 Feb  3 18:52 .
+drwxrwxrwt 46 root  root        12288 Feb  3 18:50 ..
+-rwxrwxrwx  1 reedy wikidev      1255 Feb  1 14:50 2013-10-05 President Obama's Weekly Address.txt
+-rwxrwxrwx  1 reedy wikidev 163504321 Jan 27 22:13 2013-10-05 President Obama's Weekly Address.webm
+-rwxrwxrwx  1 reedy wikidev      1197 Feb  1 14:52 2013-10-12 President Obama's Weekly Address.txt
+-rwxrwxrwx  1 reedy wikidev 158637780 Feb  1 14:34 2013-10-12 President Obama's Weekly Address.webm
+-rwxrwxrwx  1 reedy wikidev       884 Jan 31 16:26 2014 State Of The Union Address Enhanced.txt
+-rwxrwxrwx  1 reedy wikidev 909068945 Jan 30 19:37 2014 State Of The Union Address Enhanced.webm
+reedy@tin:/tmp/uploads$ sudo -u apache mwscript importImages.php --wiki=commonswiki --user=""Odder"" /tmp/uploads
+Import Images
+
+Importing 2014 State Of The Union Address Enhanced.webm...done.
+Importing 2013-10-05 President Obama's Weekly Address.webm...done.
+Importing 2013-10-12 President Obama's Weekly Address.webm...done.
+
+Found: 3
+Added: 3
+reedy@tin:/tmp/uploads$",1391453683,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,I don't see any way around getting errors when trying to upload files as a user that can't see them. What exactly is this about?,1391211450,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"If I chmod 777 it, I can upload it :/",1390364266,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**Author:** `llamaal_wikis`
+
+**Description:**
+Intention:
+After the conclusion of https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual on the Spanish Wikipedia, some changes to the status of VE in that project have to be implemented:
+
+1. VE should now be opt-in
+2. The ""edit"" tab should return to wikitext
+3. VE should be presented as part of Beta Features
+4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+
+Regards,
+
+LlamaAl
+
+
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1390009440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_description,resolved
+Changes to VisualEditor on eswiki as result of vote,This is now done.,1392253962,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**albertojuansebastian** wrote:
+
+Thank you very much, James. If you have any doubt, ask us here or there: https://es.wikipedia.org/wiki/Wikipedia:Caf%C3%A9/Archivo/Noticias/Actual#Acuse_de_recibo. 
+
+Regards.
+_________________________________________________________________________
+And thanks, Nemo. Maybe I could convince some of my 'tech collegues' on esWikipedia to take part in the discussion there.
+
+Greetings.
+_________________________________________________________________________
+Thank you all. Albertojuanse.",1392078540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"(In reply to comment #11)
+> Finally, even if they had nothing to do with the VisualEditor, several users
+> have meant to note that more economics and human resources should be focuses
+> on
+> fixing existing problems such us the FastButtons —it was disabled weeks ago
+> because a security breach—, the cellular phone and portable devices editing
+> softwares, etc.
+
+Indeed beyond the scope of a bug: I've copied this to https://www.mediawiki.org/?diff=902629&oldid=892609 . It would be useful if those users (or other users who understand Spanish and read their comments) could elaborate/continue the discussion there, I think.",1392070089,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Understood. Thank you for the responses. I have adjusted the configuration change to correct for these issues as much as we can.
+
+I will now ask my colleagues to find a time that we can make these changes.",1392069338,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**albertojuansebastian** wrote:
+
+(In reply to comment #8)
+
+Finally, I am able to aswer the questions. Thank you for the waiting. 
+
+The talk about the answers is here (in Spanish): https://es.wikipedia.org/w/index.php?title=Wikipedia:Caf%C3%A9/Archivo/Noticias/Actual&oldid=72405348#Preguntas 
+
+The aswers can be also be read here (in English): https://es.wikipedia.org/w/index.php?title=Wikipedia:Caf%C3%A9/Archivo/Noticias/Actual&oldid=72405348#Respuestas
+
+Greetings.
+_____________________________________________________________________________
+> 1. When you say ""VE should now be opt-in"", what should happen to the accounts
+> that have been using VE? Should they be opted-in, or just left stranded
+> without
+> VisualEditor? Should the default for new accounts be to have to find
+> VisualEditor to switch it on?
+
+As a consequence of the votation, the ""opt-in"" must be disabled; and thus it will be enabled by those who want to use it. The proper announcements will be made in order that noone overlook this change.
+
+And, that is correct, the new users will have to get informed —or they will be informed if they ask for help— about the different tools available in esWikipedia, which are not less useful and important that this one: our spelling checker, the PopUps or FastButtons, etc.
+_________________________________________________________________________
+> 2. You want the labels to be ""Edit"" for wikitext and ""Editor Visual"" for
+> VisualEditor? Which way around should they go? (Right now eswiki has VE as
+> the
+> primary/first tab, but we could change it to secondary/second tab if you
+> think
+> it would be a good change. However, that would be a bit odd to do as well as
+
+Fully right, if the user enables the VE, the label ""Edit"" —""Editar""— should be the wikitext's one and the ""Editor Visual"" should be the VisualEditor one. Regarding to the labeling way once the VE is activated, the community was not asked about that in the votation; although most of the users have pronounced in favour of using the second label for ""Editor Visual"" —""Visual Editor""—. However, proceed as you see best.
+_________________________________________________________________________
+> 3. Also on the labels of the tabs, in general, we're not happy with the
+> ""beta""
+> superscript note and we were planning to get rid of it in the next few
+> weeks. I
+> don't think it makes sense for an opt-in system with two warnings about the
+> software being beta to have a third, and it doesn't work very well in Firefox
+> and some other platforms due to browser bugs.
+
+In esWikipedia, the ""beta"" superscript has never been implemented, so we ignored its flaws. Besides, when the votation was proposed there were any warning about the software being beta, so it is logical that the community would desired to implement the ""beta"" warning. Be that as it may, our desires are limited by the technical viability of those, although this ""beta"" labeling it is still desired.
+_________________________________________________________________________
+> 4. What is the plan to inform users who have been using VisualEditor as to
+> the
+> disruption? Particularly, what is the plan for anonymous editors (who can't
+> opt-in)? About 20% of edits by anonymous users have been through VisualEditor
+> to date, and this is likely to confuse them.
+
+Will be developed the same action plan that was developed when the VisualEditor was implemented, id est, it will be announce in our ""Café de noticias"" —Village pump (news)— and the guide ""Wikipedia:VisualEditor"". Besides, we all will beware in order to solve the doubts from users and help them in this issue.
+_________________________________________________________________________
+> 5. What is the plan for returning to use VisualEditor as the primary editor?
+> What changes or fixes would you like to see?
+
+When the tool have been fully finished, and the developers let us know this situation, the entire community will be asked again about this issue. At the time, if there is consensus about its implementation, it will be enabled; if not, there will be another votation about the VisualEditor. Please also note that in a votation, the ""enable"" option must reach 2/3 of the votes to be enabled.
+
+Regarding to the second question, several users are already working with the VisualEditor and they are reporting their feedback to the developers; so when it will be reported that the software has not structural flaws and that the use experience is acceptable, we will let you know. Also, there has been an interest in solving all the incompatibilities with other ""mod"" and ""opt-in"" softwares, although it is known that some of them are already fixed.
+
+Finally, even if they had nothing to do with the VisualEditor, several users have meant to note that more economics and human resources should be focuses on fixing existing problems such us the FastButtons —it was disabled weeks ago because a security breach—, the cellular phone and portable devices editing softwares, etc.
+_________________________________________________________________________",1391824184,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**albertojuansebastian** wrote:
+
+(In reply to comment #9)
+
+Indeed. We are already discussing the answers in our Café (Village pump). In fact, in a few days (2 or 3)  we will be able to give you the answers, since it seems that we are reaching consensus. Greetings.",1391521353,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Shouldn't these ""big questions"" be brought up with the entire eswiki community, rather than on Bugzilla where only the single community member who filed the bug will see?",1391514324,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Some questions and points (sorry for being slow; I've been on leave, returning next week):
+
+1. When you say ""VE should now be opt-in"", what should happen to the accounts that have been using VE? Should they be opted-in, or just left stranded without VisualEditor? Should the default for new accounts be to have to find VisualEditor to switch it on?
+
+2. You want the labels to be ""Edit"" for wikitext and ""Editor Visual"" for VisualEditor? Which way around should they go? (Right now eswiki has VE as the primary/first tab, but we could change it to secondary/second tab if you think it would be a good change. However, that would be a bit odd to do as well as the opt-in, and is more an alternative.
+
+3. Also on the labels of the tabs, in general, we're not happy with the ""beta"" superscript note and we were planning to get rid of it in the next few weeks. I don't think it makes sense for an opt-in system with two warnings about the software being beta to have a third, and it doesn't work very well in Firefox and some other platforms due to browser bugs.
+
+4. What is the plan to inform users who have been using VisualEditor as to the disruption? Particularly, what is the plan for anonymous editors (who can't opt-in)? About 20% of edits by anonymous users have been through VisualEditor to date, and this is likely to confuse them.
+
+5. What is the plan for returning to use VisualEditor as the primary editor? What changes or fixes would you like to see?",1391213693,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Change 109639 had a related patch set uploaded by TTO:
+Move VisualEditor to secondary status on eswiki
+
+https://gerrit.wikimedia.org/r/109639",1390817856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Just to explain:
+
+This request is easy, except for the desire to have the VisualEditor tab labelled ""Editor Visual <sup>BETA</sup>"". It is not currently possible to label the VisualEditor tab differently from the regular ""Edit"" tab (other than the appending of a BETA suffix), this would appear to require an alteration to the VisualEditor software itself.
+
+The remaining three points of the request can be fulfilled easily, I think.",1390706953,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**llamaal_wikis** wrote:
+
+I want to clarify something: the ""BETA"" part in the name of the Visual Editor tab should appear in small and superscript text, as shown in this diff [1].
+
+[1] https://es.wikipedia.org/w/index.php?title=Wikipedia%3AZona_de_pruebas%2F5&diff=72006555&oldid=71969129",1390172986,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**llamaal_wikis** wrote:
+
+(In reply to comment #3)
+> (In reply to comment #1)
+> > 4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+> Note that this is different from the enwiki config (the rest of the request
+> is
+> the same). On enwiki:
+> * users who have VE disabled only see one tab, labeled ""Edit"", that points to
+> the source editor
+> * for users who have VE enabled, this tab is labeled ""Edit source"" instead
+> * additionally, they have a VE tab labeled ""EditBETA""
+> * the VE tab appears after (to the right of) the source editor tab
+> 
+> For eswiki, #4 in the request asks us to implement the third bullet point
+> differently, by labeling the VE tab ""Editor VisualBETA"" rather than
+> ""EditarBETA"".
+> 
+> So what should happen to the source editor tab for users who have VE enabled?
+> Should it be labeled ""Editar código"" (as it is now, and would be with an
+> enwiki-like configuration), or as ""Editar"", or ... ? Should it appear before
+> or
+> after the source editor tab (right now it's before, with an enwiki-like
+> configuration it would be after).
+
+In the case a user enables VE, the source editor tab should remain as ""Editar"", and a new tab labeled ""Editor VisualBETA"" should appear after it.",1390011606,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"(In reply to comment #1)
+> 4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+Note that this is different from the enwiki config (the rest of the request is the same). On enwiki:
+* users who have VE disabled only see one tab, labeled ""Edit"", that points to the source editor
+* for users who have VE enabled, this tab is labeled ""Edit source"" instead
+* additionally, they have a VE tab labeled ""EditBETA""
+* the VE tab appears after (to the right of) the source editor tab
+
+For eswiki, #4 in the request asks us to implement the third bullet point differently, by labeling the VE tab ""Editor VisualBETA"" rather than ""EditarBETA"".
+
+So what should happen to the source editor tab for users who have VE enabled? Should it be labeled ""Editar código"" (as it is now, and would be with an enwiki-like configuration), or as ""Editar"", or ... ? Should it appear before or after the source editor tab (right now it's before, with an enwiki-like configuration it would be after).",1390011071,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,*** Bug 60189 has been marked as a duplicate of this bug. ***,1390011045,PHID-USER-3qsavo6roa5h32xcsgng,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**llamaal_wikis** wrote:
+
+After the conclusion of
+https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual
+on the Spanish Wikipedia, some changes to the status of VE in that project have
+to be implemented:
+
+1. VE should now be opt-in
+2. The ""edit"" tab should return to wikitext
+3. VE should be presented as part of Beta Features
+4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+
+Regards,",1390009593,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+VisualEditor: Standalone demo toolbar breaks sometimes in Chrome,"Screenshot of the bug
+
+See attached screenshot.
+
+This is because the standalone demo initializes the target into a detached DOM element, then attaches it once it's done. But you can't do that, because it causes ve.ui.Toolbar.prototype.initialize to be run before the toolbar is attached to the DOM (and generally causes initialize to be run on unattached things, which is not allowed), which means its measurements will be wrong, and so the toolbar gets right: 1840px; (width of screen) rather than width: 63px; or whatever.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13274}",1389997140,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qs4hjzccsgzpxttdtdrd,task_description,resolved
+VisualEditor: Standalone demo toolbar breaks sometimes in Chrome,"
+
+*** This bug has been marked as a duplicate of bug 59720 ***",1390864797,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qs4hjzccsgzpxttdtdrd,task_subcomment,NA
+VisualEditor messages not updated for 1.23wmf11,"Broken inspector
+
+Steps to reproduce:
+
+1.Open the VisualEditor
+2.Go to Insert menu and Settings menu
+
+Observed Result:
+<visualeditor-mwgalleryinspector-title> and <visualeditor-dialog-commands>  is appearing in the Insert menu and Settings menu respectively.
+Also selecting <visualeditor-mwgalleryinspector-title> opens up a broken gallery inspector.
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/,wmf11
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13165}",1389904560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gfsol6rwzvgp2bqtxhxa,task_description,resolved
+VisualEditor messages not updated for 1.23wmf11,Verified the fix in test2 using Chrome and FF,1389985847,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gfsol6rwzvgp2bqtxhxa,task_subcomment,NA
+VisualEditor messages not updated for 1.23wmf11,Now fixed.,1389985486,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gfsol6rwzvgp2bqtxhxa,task_subcomment,NA
+"VisualEditor: Switching insertion types for inspectable notes (e.g. hiero, formula, gallery) mid-creation breaks entertainingly","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a math function from Insert>Formula for example \pi
+3.While the added math formula is still selected go to Insert>Hiero
+4.Observe that the math function previously added is now appearing in hiero inspector.
+5.Close the inspector for hiero
+6.Save the page
+
+Observed Result:
+A hiero tag got added  in the wikitext as  <hiero>\pi</hiero>
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Wmf11&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13157}",1389903480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-43nrc2oe3kjbjeoi5weu,task_description,resolved
+"VisualEditor: Switching insertion types for inspectable notes (e.g. hiero, formula, gallery) mid-creation breaks entertainingly",Can not reproduce from my end as well.Closing the bug.,1391728232,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-43nrc2oe3kjbjeoi5weu,task_subcomment,NA
+"VisualEditor: Switching insertion types for inspectable notes (e.g. hiero, formula, gallery) mid-creation breaks entertainingly","Can't reproduce, might have been fixed by https://gerrit.wikimedia.org/r/#/c/111178/ ? Please test again.",1391717104,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-43nrc2oe3kjbjeoi5weu,task_subcomment,NA
+"VisualEditor: Switching insertion types for inspectable notes (e.g. hiero, formula, gallery) mid-creation breaks entertainingly","When you ""switch"" inspectors the content of the first inspector is inserted, but a new inspector isn't created (so the content of the first is also available for the new one).",1390021684,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-43nrc2oe3kjbjeoi5weu,task_subcomment,NA
+"VisualEditor: Selection highlighting breaks on changing selection format (cursor moves to wrong place, selection is unhighlighted but still selected)","Selecting a line of text and turning it into a header (ctrl+1) removes the selection highlighting but keeps the text selected. Additionally turning text into a header also moves the position marker to the wrong place (visually).
+
+As a result e.g. the action of creating a header then pressing enter replaces the header by an empty line.
+
+Se screencast below for procedure and illustration.
+https://www.youtube.com/watch?v=7OtpP5iS2uw
+
+Reproducible in Chrome and Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1389892740,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-j7arlw5peomdv3rolltm,task_description,resolved
+"VisualEditor: Selection highlighting breaks on changing selection format (cursor moves to wrong place, selection is unhighlighted but still selected)","
+
+*** This bug has been marked as a duplicate of bug 57552 ***",1394659271,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-j7arlw5peomdv3rolltm,task_subcomment,NA
+"VisualEditor: Loading the San Francisco article on mobile causes massive breakage, unusable editor","Oh nos!
+
+When trying to edit San Francisco with VE in mobile alpha mode all hell breaks lose.
+
+See for yourself at this URL:
+https://en.m.wikipedia.org/wiki/San_Francisco?mobileaction=alpha#editor/0
+
+and see screen for the sort of things that happen.
+
+I can't focus the textarea or make any changes. This makes me sad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13080}",1389833400,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-hjchikg52kgk75rl7yaa,task_description,resolved
+"VisualEditor: Loading the San Francisco article on mobile causes massive breakage, unusable editor",This appears to have been fixed by the changes that Juliusz and Jon made last month.,1394494444,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjchikg52kgk75rl7yaa,task_subcomment,NA
+VisualEditor:  [Regression] External rich pasting in Firefox inserting newlines again,"https://jv.wikipedia.org/w/index.php?title=Kraton_Ngayogyakarta_Hadiningrat&curid=87083&diff=879162&oldid=845799
+
+This begins with a =Level 1 heading= (perhaps the article title was copied?).  Some paragraphs are broken onto separate lines. The [[links]] are improperly converted to [[http://jv.wikipedia.org/wiki/Links]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389725880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rafcafjslpgvnetrixxn,task_description,resolved
+VisualEditor:  [Regression] External rich pasting in Firefox inserting newlines again,"Whenever we fixed this, it's certainly not a problem now.",1421282899,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rafcafjslpgvnetrixxn,task_subcomment,NA
+VisualEditor:  [Regression] External rich pasting in Firefox inserting newlines again,"The H1 is just external copy of the read HTML (and isn't a bug, just bad user behaviour).
+
+The links getting badly converted are bug 58136.
+
+However, the paragraphs getting split is a new regression in Firefox pasting behaviour. :-(",1390022523,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rafcafjslpgvnetrixxn,task_subcomment,NA
+VisualEditor:TypeError: currentDom[i].setAttribute is not a function appears while adding content from Template dialogbox,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Transclusion 
+3.Add some content and click on ""Apply changes""
+4.Click on ""Save Page""
+
+Observed Result:
+
+The ""Save Page"" button does not worl.In the console the following error appears:
+TypeError: currentDom[i].setAttribute is not a function
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Jan_13th?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12850}",1389651180,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4hrlw6tweytjl62h36,task_description,resolved
+VisualEditor:TypeError: currentDom[i].setAttribute is not a function appears while adding content from Template dialogbox,Verified the fix  in test2,1390336093,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4hrlw6tweytjl62h36,task_subcomment,NA
+VisualEditor:TypeError: currentDom[i].setAttribute is not a function appears while adding content from Template dialogbox,This should have been fixed by https://gerrit.wikimedia.org/r/#/c/107511/,1390317183,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yw4hrlw6tweytjl62h36,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which has some content
+2.Add any image from Insert>Media after going to a newline.
+3.Save the page
+4.Reopen the page
+5.Place the cursor in a new line and hit return
+
+Observed Result:
+Newline cannot be added , in the console an error appears:
+TypeError: outermostNode is null
+	
+
+...documentModel,selection.from,'\n');}else{node.traverseUpstream(function(node){if...
+
+load.p...1826Z&* (line 261)
+
+Test Environment: mw.org
+Browser: FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox_345&oldid=885285?veaction=edit
+
+**Attached**: {F12613}",1389374820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_description,resolved
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754958,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,Verified the fix in test2.,1394232814,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,Verified the fix in betalabs,1393634363,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,"Change 109693 merged by jenkins-bot:
+Fix handleEnter in nodes that don't split
+
+https://gerrit.wikimedia.org/r/109693",1393612229,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,*** Bug 62015 has been marked as a duplicate of this bug. ***,1393530490,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,*** Bug 61525 has been marked as a duplicate of this bug. ***,1393474403,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,*** Bug 61932 has been marked as a duplicate of this bug. ***,1393474369,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,"Change 109693 had a related patch set uploaded by Divec:
+WIP:Fix handleEnter when not in a splittable node
+
+https://gerrit.wikimedia.org/r/109693",1390845592,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,"Seems to be failing to handle enter when in a block slug for some reason… but only on the page re-load.
+
+Line 1675 of ve.ce.Surface.js (in handleEnter) is throwing ""TypeError: Cannot call method 'getModel' of null"" because  ""outermostNode"" is null.
+
+ncaught TypeError: Cannot call method 'getModel' of null ve.ce.Surface.js:1675",1389906213,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken","Steps to reproduce:
+
+- go to page (for example [1]) that has only this as contents: {{done}}
+- edit the page with visual editor
+- copy/paste the template
+- I was expecting the page now to contain only this text: {{done}}{{done}}
+- instead, the page text is: {{done}}{{done}}<span data-ve-ignore=""true""> </span>'''Done.'''
+- that causes ""Done."" to be displayed three times (instead of two), see screenshot[2]
+- two minute video recording reproducing the bug is available at [3]
+- Sauce Labs is pretty slow to respond, so the actions looks really really slow, the best way to view the video is to download it from [4] and play it with VLC on maximum speed (4x)
+
+1: https://test2.wikipedia.org/wiki/Done
+2: https://saucelabs.com/jobs/9dd0291def28413bb7f9ca3a9fd7e891/0001screenshot.png
+3: https://saucelabs.com/tests/9dd0291def28413bb7f9ca3a9fd7e891
+4: https://saucelabs.com/jobs/9dd0291def28413bb7f9ca3a9fd7e891/video_9dd0291def28413bb7f9ca3a9fd7e891.flv
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1389356460,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-mipnpagv42ujw7okwcjf,task_description,resolved
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken","
+
+*** This bug has been marked as a duplicate of bug 59653 ***",1389904122,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mipnpagv42ujw7okwcjf,task_subcomment,NA
+VisualEditor: Document selection should be nullable,"Despite the fact that you can have the appearance of the document being blurred and having no active selections, we will always keep the last valid range as the current selection. This is a case of the model not matching the view.
+
+The other solution (as used by Google Docs) is to always render a selection even when the document is unfocused, but as we are using native selections this may not be possible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62410",1389282420,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-23mm54valrpkfsjce3lj,task_description,resolved
+VisualEditor: Document selection should be nullable,"Change 124359 merged by jenkins-bot:
+Detect document focus properly and allow null selection in model
+
+https://gerrit.wikimedia.org/r/124359",1397261984,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,"Change 124359 had a related patch set uploaded by Esanders:
+Detect document focus properly and allow null selection in model
+
+https://gerrit.wikimedia.org/r/124359",1396892619,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,Was reverted in https://gerrit.wikimedia.org/r/123464,1396477637,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,"Change 121534 merged by jenkins-bot:
+Detect document focus properly and allow null selection in model
+
+https://gerrit.wikimedia.org/r/121534",1396394668,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,"Change 121534 had a related patch set uploaded by Esanders:
+Detect document focus properly and allow null selection in model
+
+https://gerrit.wikimedia.org/r/121534",1395956704,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,What's the status of this? Did your work on cursor selections last week relate?,1394494239,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","Intention:
+Test a bug.
+
+Steps to Reproduce:
+1. Selecting the appendices on the page https://en.wikipedia.org/w/index.php?oldid=588539903&veaction=edit
+
+2. Cut them out (Control-x), and 
+
+3. Paste them right back where they were.  
+
+
+Actual Results:  
+The indentation level for all the bulleted lists was increased.
+
+
+Reproducible: Didn't try
+
+**URL**: https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FS%26D&diff=588777573&oldid=588539903",1389228060,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uctbq2qfw5ogzgknys3a,task_description,resolved
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome",I've tested this out and it seems to work correctly now. Feel free to reopen if I've missed something.,1437603288,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","I'm convinced that most editors don't know this.  I only learned this a couple of years ago, when talking to someone with WikiProject Accessibility.
+
+https://en.wikipedia.org/wiki/Template:Glossary is only used 101 times, which is almost nothing for the English Wikipedia.  I don't believe that I've ever seen a list using it.  The normal way to make a definition list is:
+
+;Term
+:Definition
+
+or, alternatively:
+
+;Term: Definition
+
+See [[Disease]] for one of several examples I could name off the top of my head.  Both formats produce the same end result.
+
+VisualEditor does not support definition lists at all at this time.  Support is planned (see bug 37938), but it may be a while.  Whenever that happens, this problem should (hopefully) be resolved.",1412488651,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","> TLDR:  The colon does *not* actually mean ""indent"".
+
+Ok, the colon does not mean indent.  However, I have had an account on English Wikipedia for seven years, have made 50,000 edits in that time (which must include tens of thousands of colons) but this is the first I have heard of it.  We have a page (WP:INDENT) explaining how to use colons for indenting, MOS:MATH requires it for display formulae, and WP:TALK suggests that it may be disruptive to deliberately not use colons.  On none of those pages is it explained that, actually, colon does not really mean indent.
+
+I am almost certain that the vast majority of editors do not know this.  There are probably hundreds of thousands of articles that use colons.  It is simply not going to be acceptable for VE to chew up articles because it does not ""like"" the markup used by editors and established for many years.  A less disruptive way forward would be to make the colon actually mean indent.  Definition lists are usually achieved with templates.  The few that are not are going to be a much smaller number of pages that need fixing and can easily be found by extracting a list of pages from the database with semicolons in lines beginning with colons.  A semi-automated bot could then go through them.",1412442963,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","I don't understand why editors aren't allowed free use of indenting, either.  But ""free use of indenting"" is bug 4521 from eight years ago.  ""Free use of indenting"" is not ""using the second half of the markup from a definition list to sort of fake indenting, so that it looks okay on my desktop system but also so that reading the page is irritating to people using screen readers"".
+
+The colon is part of semantic markup.  Screen readers don't skip over semantic markup.  They don't just read the contents of a list.  They stop reading content and announce that there is a list, and how long the list is.  If you use a colon, then some screen readers (correctly) interpret this as being marked as a long list of definitions, so that your markup:
+
+:where,
+: ''D'' = 1/''C'' is elastance
+: ''C'' is capacitance
+: ''S'' is stiffness
+
+is read as something like ""Term with four definitions:  where, d = 1/C is elastance, c is capacitance, s is stiffness"".  Unless you really want the words ""Term with four definitions"" to be stuck in the middle of that sentence, then you should not define those four lines as being in a definition list (aka association list).
+
+If you just want visual-only indentation, then you have to set span or div tags to provide visual-only changes to the text arrangement.  As I said above, I don't know why MediaWiki doesn't have a much simpler method for letting editors provide visual intendations properly, and instead gives them a choice between screwing up accessibility or having to hand-type complicated HTML codes.  Using indentation freely been requested for at least eight years.  We have a legitimate need for this, but I don't know if we'll ever get it.
+
+
+TLDR:  The colon does *not* actually mean ""indent"".",1412359030,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","(In reply to WhatamIdoing from comment #2)
+
+> However, what's being used there as ""indentation"" isn't indentation,
+> strictly speaking; that text has been marked as the second half of a
+> term-definition pair in a definition list, which is not semantically
+> meaningful.  
+
+It wasn't so marked by me and I don't see any markup in the edit window so you would appear to mean that VE has generated markup.  Generating semantically incorrect markup and then blaming the user for the error is plainly ridiculous.  Or perhaps you mean that the colon in wiki markup does not really mean indentation?  Well, yes it does, it is used extensively all over Wikipedia (ahem, talk pages) with just that intention so by practice and precedent that is what it means.  VE needs to live with that, not garble it because it doesn't like the semantics, otherwise VE will never be ready for prime time.
+
+> where,
+> * ''D'' = 1/''C'' is elastance
+> * ''C'' is capacitance
+> * ''S'' is stiffness
+
+No, that is not a good solution.  Display maths lines are pretty universally indented for aesthetic reasons.  The definitions list following a maths display line are commonly indented as well.  Thus not indenting the ""where"" and using bullets are both not acceptable.  Bear in mind that a formula, even a display formula, can be inserted in the middle of a sentence so bullets would break the grammatical punctuation.  I can't understand this desire not to allow editors free use of indenting.  It is an editorial decision and there is no reason for VE to interfere or impose something different.  It is for the style guidelines to thrash out, not for VE to impose.",1412208518,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","The mess created here is definitely a problem.
+
+However, what's being used there as ""indentation"" isn't indentation, strictly speaking; that text has been marked as the second half of a term-definition pair in a definition list, which is not semantically meaningful.  
+
+I don't know whether VisualEditor is expected to support the presence of only half of a paired list:  maybe, because it's (mis)used a lot, but maybe not, because it shouldn't be used that way?  (That decision is someone else's problem.)  
+
+However, what's represented there like this:
+
+:where,
+: ''D'' = 1/''C'' is elastance
+: ''C'' is capacitance
+: ''S'' is stiffness
+
+
+probably ought to be (for proper semantic meaning) a standard (non-definition/non-association) list like this:
+
+where,
+* ''D'' = 1/''C'' is elastance
+* ''C'' is capacitance
+* ''S'' is stiffness
+
+(or in a similar format, but without bullet points, which is possible but not as trivial to create in wikitext).
+
+It would be nice if MediaWiki actually supported plain old indentation, similar to pressing the tab key on a typewriter, perhaps along the lines of the request in bug 4521 (from 2006), but so far that request has not been granted.",1412185441,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","I don't know if this is related, or whether it should be a new bug.  In this edit:
+
+https://en.wikipedia.org/w/index.php?title=User:Spinningspark/Work_in_progress/Mobility_analogy&diff=626824709&oldid=626823704
+
+VE adds a number of spurious indents.  The intended edit was to swap over the order of two blocks of text containing math markup.  Very frustrating that the problem could not even be fixed from within VE since indenting does not function in general.",1412132187,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"1. Open up the standalone demo /empty.html and type some text
+2. Select text from right to left, mouse up outside the surface (or even outside the window)
+3. Although the text is selected in CE pressing dump range gives a collapsed range. Formatting actions will fail too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389195120,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eri6nma5at4veawakgy2,task_description,resolved
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Verified the fix in production,1411681950,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Verified the fix in test2,1411083301,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Verified the fix in Betalabs,1410810842,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"Change 159919 merged by jenkins-bot:
+Trigger selection update on selectionchange or mousemove events
+
+https://gerrit.wikimedia.org/r/159919",1410484474,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"Change 159919 had a related patch set uploaded by Esanders:
+Trigger selection update on selectionchange or mousemove events
+
+https://gerrit.wikimedia.org/r/159919",1410475411,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"Change 159807 merged by jenkins-bot:
+Bind ve.ce.Surface#onDocumentMouseUp to the entire document on mousedown
+
+https://gerrit.wikimedia.org/r/159807",1410471475,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"Change 159807 had a related patch set uploaded by Esanders:
+Bound onDocumentMouseUp to the entire document on mousedown
+
+https://gerrit.wikimedia.org/r/159807",1410461605,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Or just stop the surface observer from being disabled. We currently have a bug whereby if you create a selection on a blurred document the SO isn't disabled so you can see the range being periodically updated as you change the selection.,1405016742,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Perhaps we should be using document.onselectionchange to update the model selection (polyfill: https://github.com/2is10/selectionchange-polyfill),1405015999,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389118200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4hd4cmhduncacfpdevsv,task_description,resolved
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,Verified the fix in test2 and mw.org,1391129224,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,Verified the fix in Betalabs,1390609554,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"I believe that this is now fixed in master (but not in Beta Labs yet). Can reproduce in wmf11 but not in master, so closing as fixed by Roan's change in gerrit 108082.",1390021348,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"Observed Result:
+1.The page *focus* automatically scrolls up
+2.If you scroll up or down a bit you will see the link inspector is broken as shown in the screenshot",1389118877,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"Created attachment 14246
+Link inspector UI is broken
+
+**Attached**: {F12306}",1389118496,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"Steps to reproduce:
+
+1.Open a page with VE which contains two or more paragraphs
+2.At the end of the page select a text
+3.Press command+K and apply a link
+
+Observed Result:
+The page fous automatically scrolls up and if you scroll down a bit you will see the link inspector is broken as shown in the screenshot.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Jan7th?veaction=edit",1389118459,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari","Intention:
+Correct the spelling of a word.
+
+Steps to Reproduce:
+1. Add some text, including a spelling error, to an article.
+2. Use Safari's built-in spellcheck to correct the spelling. 
+
+
+Actual Results:  
+The correct spelling displays on the screen.  However, if you ""review changes"", only the old, incorrect spelling is present.  Also, the correct spelling stops being displayed on the screen if you hit return to start a new paragraph or list item.
+
+Screenshot shows the display and the review changes.  Confirmed in both lists and plain paragraphs.
+
+
+Reproducible: Always
+
+Confirmed in Safari 6 on Mac OS 10.8.5 using Vector.  It's not present in Firefox 26.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50822",1389056280,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-sfrluwneg7unava7ogpl,task_description,resolved
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari",">>! In T61748#836003, @Whatamidoing-WMF wrote:
+> I think we're making some progress on this.  Today, the automatic spelling correction is visible in ""Review changes"".  If the spelling change has the net effect of removing one character, then it even appears to be handled correctly.  However, if it adds a character, then the change is not made, but an equivalent number of extra letters are repeated at the end.
+> 
+> Examples:
+> 
+> * Typing ""teh"" and auto-correcting it to ""the"" displays correctly and saves correctly.
+> * Typing ""cantalop"" and auto-correcting it to ""cantaloup"" (adding one character) is saved as ""cantalopp"" (last letter repeated; added 'u' missing).
+> * Typing ""proftabilty"" and auto-correcting it to ""profitability""(adding two characters) is saved as ""proftabiltyty"" (last two letters repeated; added two letters missing).
+
+This also appears to now be fixed. Adding and removing characters works perfectly, in all three use cases here and others I tested.",1424273920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sfrluwneg7unava7ogpl,task_subcomment,NA
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari","I think we're making some progress on this.  Today, the automatic spelling correction is visible in ""Review changes"".  If the spelling change has the net effect of removing one character, then it even appears to be handled correctly.  However, if it adds a character, then the change is not made, but an equivalent number of extra letters are repeated at the end.
+
+Examples:
+
+* Typing ""teh"" and auto-correcting it to ""the"" displays correctly and saves correctly.
+* Typing ""cantalop"" and auto-correcting it to ""cantaloup"" (adding one character) is saved as ""cantalopp"" (last letter repeated; added 'u' missing).
+* Typing ""proftabilty"" and auto-correcting it to ""profitability""(adding two characters) is saved as ""proftabiltyty"" (last two letters repeated; added two letters missing).
+",1418192661,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-sfrluwneg7unava7ogpl,task_subcomment,NA
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari",Confirmed with Safari 7 on 10.9,1389057186,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-sfrluwneg7unava7ogpl,task_subcomment,NA
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari","Created attachment 14242
+VisualEditor screenshot, showing ""Review changes"" not matching the displayed text
+
+**Attached**: {F12267}",1389056395,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-sfrluwneg7unava7ogpl,task_subcomment,NA
+VisualEditor: Use gzip compression when POSTing HTML,"Per Gabriel's report via email, when VE POSTs HTML to api.php , it should ensure that gzip compression is used for the POST body.
+
+TODO: Figure out how to actually tell the browser to do this
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388891040,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vlthdxz6gr6ej4yayl53,task_description,resolved
+VisualEditor: Use gzip compression when POSTing HTML,"
+
+*** This bug has been marked as a duplicate of bug 66914 ***",1403735953,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vlthdxz6gr6ej4yayl53,task_subcomment,NA
+VisualEditor: Use gzip compression when POSTing HTML,"This doesn't seem to be supported natively in browsers. Even the XHR2 standard doesn't include support for this. Presumably this is because POST bodies large enough that compression is desired are rare, and because clients don't know in advance whether the server will support compression.
+
+We may be able to do this using a client-side gzip implementation; I'll have to see whether that makes sense. Alternatively, it might be that the savings from fixing bug 59660 and dropping data-parsoid will suffice.",1388987872,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vlthdxz6gr6ej4yayl53,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Intention:
+Add a caption to an image without having to type out the name by hand.
+
+Steps to Reproduce:
+1. Add an image in VisualEditor (e.g., an image of a person).  Open the caption dialog.
+2. Go to another window (e.g., an article about the person) and copy a =Name= from the article title.
+3. Paste the rich text into the caption.
+
+Actual Results:  
+The pasted text retained rich formatting.  It is not possible to remove the =Heading= formatting.  Only '''text''' <s>formatting</s> can be added or removed in that dialog.  So if you copy the article title from [[George Washington]] and paste it into the caption box, then it produces this wikitext:
+
+= <span dir=""auto"">George Washington</span> =
+
+and there is no way to remove the formatting.
+
+Expected Results:  
+That either you could remove the formatting, or ideally, that the caption box would strip the unwanted formatting automagically.  There's no obvious reason why someone would need or want a ==Heading== of any level in a caption.
+
+Reproducible: Didn't try
+
+Confirmed in Safari 6 and Firefox 26
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388776980,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_description,resolved
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Closing for now, though we may make further changes about removing or allowing certain kinds of formatting in future.",1391651684,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"We mean discouraged. At the moment there's a Parsoid bug that breaks list rendering, but we can revisit that decision if users really want it. And yes, the patch will convert lists to paragraphs.",1391642942,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"What does ""disallowed"" mean?  People do put lists into refs.  See https://en.wikipedia.org/wiki/Wikipedia:Verifiability#cite_note-9 for an example.
+
+It is important that people be able to paste something that was in a list format, even if it was converted into a paragraph upon pasting.",1391634077,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Disallowed inside references: references, reference lists, lists, definition lists, tables. Headings can be pasted but are converted to paragraphs.
+
+Disallowed inside image captions: lists, definition lists, tables. Headings can be pasted but are converted to paragraphs.",1391632187,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Change 110960 merged by jenkins-bot:
+Implement surface paste rules for media/ref dialogs
+
+https://gerrit.wikimedia.org/r/110960",1391628234,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Change 110960 had a related patch set uploaded by Esanders:
+Implement surface paste rules for media/ref dialogs
+
+https://gerrit.wikimedia.org/r/110960",1391600356,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,SurfaceWidgets currently aren't even implementing the main surface's paste rules.,1391191118,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","I see now, that there is a dialog box for reference group, while in most cases, where refs are being used as citation, we dont need to fill that group. I propose than to give a tip below that dialox box saing: ""For reference list leave empty"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388573640,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_description,resolved
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","Change 114382 merged by jenkins-bot:
+Add placeholder to 'group' field in reference dialog too
+
+https://gerrit.wikimedia.org/r/114382",1392860375,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","(In reply to Alex Monk from comment #3)
+> Is there anything else to do here?
+
+Beyond also adding it to references' dialogs too (now done :-)), there's the TODO from that file:
+
+// TODO: Use a drop-down or something, and populate with existing groups instead of free-text
+
+But will split that off into a new bug (and it will require a new kind of OOjs UI widget anyway).",1392860331,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","Change 114382 had a related patch set uploaded by Jforrester:
+Add placeholder to 'group' field in reference dialog too
+
+https://gerrit.wikimedia.org/r/114382",1392860102,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty",Is there anything else to do here?,1392858295,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","Change 113684 merged by jenkins-bot:
+Show placeholder text in group input box on reference list dialog
+
+https://gerrit.wikimedia.org/r/113684",1392857039,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","Change 113684 had a related patch set uploaded by Alex Monk:
+Show ""General references"" as placeholder text in group input box on reference list insert dialog
+
+https://gerrit.wikimedia.org/r/113684",1392568946,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in FireFox which contains a reference and reference list
+For example:
+reference<ref>reference</ref>
+<references />
+2.Copy the reference and the reference list
+3.Open another page with VE in FireFox
+4.Paste the reference and the reference list
+5.Save the page
+
+Observed Result:
+The wikitext resulting from after copy-paste is:
+
+reference<span class=""reference"" id=""cite_ref-1-0"" rel=""dc:references""><sup href=""http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit#cite_note-1"">[1]</sup></span>
+#<span class="""" rel=""mw:referencedBy"">[http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit#cite_ref-1-0 ↑]</span> reference
+
+And it redirects to the source page (in this case: http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit#cite_ref-1-0) 
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Newrefff
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12746}",1388531940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d6mwrlxedpo24myhvpw5,task_description,resolved
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,Verified the fix in test2,1391130109,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan24th_ff&action=edit,1390593630,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,betalabs doesn't have this code deployed yet,1390559944,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,"Still getting this issue on Betalabs:
+
+The resulting wikitext after copying a reference and reference list from FireFox to FireFox is:
+
+reference<span class=""reference"" id=""cite_ref-1-0"" rel=""dc:references""><sup href=""http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january?veaction=edit#cite_note-1"">[1]</sup></span>
+#<span class="""" rel=""mw:referencedBy""><a href=""http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january#cite_ref-1-0"">↑</a></span> reference",1390531161,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,"Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430349,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,"Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317337,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page with VE in Chrome Browser which has references list in it 
+2.Copy the references list with the reference.For example copy the following:
+reference<ref>reference</ref>
+<references />
+3.Open another page in FireFox with VE
+4.Paste the copied reference and reference list
+5.Save the page
+
+Observed Result:
+The reference list got copied as bullet list rather than as <references/>
+
+The resulting wikitext is as follows:
+reference<sup>[1]</sup>
+# reference
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Chrome Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=31st_december&veaction=edit
+FF Page:http://en.wikipedia.beta.wmflabs.org/wiki/Newrefff
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12743}",1388527440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wuqpc2pu5uodgmseauhd,task_description,resolved
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,Verified the fix in test2,1391130429,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,Verified the fix in Betalabs.,1390593485,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,betalabs doesn't have this code deployed yet,1390559956,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,"Still getting this issue on betalabs.
+
+Copied Reference list from this page:http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january?veaction=edit
+
+
+
+Pasted on the page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Paste_reference&action=edit
+
+The resulting wikitext is:
+reference<sup>[1]</sup>
+# reference",1390530842,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,"Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430346,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,"Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317332,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in Chrome Browser with VE which has a template in it
+2.Copy the template
+3.Open another page in FirFox browser with VE
+4.Paste the copied template
+
+Observed result:
+The template does not get copied and in the console an error appears:
+TypeError: item is undefined
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/31st_decemberff?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12738}",1388526240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oupzvbwduxmp5jze2owb,task_description,resolved
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,Verified the fix in test2,1391130924,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,betalabs doesn't have this code deployed yet,1390559897,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,I can still reproduce this issue on Betalabs.,1390531607,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,"Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430355,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,"Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317327,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,"Steps to reproduce:
+
+1.Open a page with VE which has reference added to a text
+2.Copy the text with the reference 
+3.Open another page with VE in FireFox
+4.Paste the copied reference
+
+Observed Result:
+Instead of getting copied as text <ref> reference </ref>, it is getting copied as text<sup> [1] </sup>
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=30th_december_ff&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388450160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_description,resolved
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,Verified the fix in test2,1391131365,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan24th_ff&action=edit,1390593605,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,betalabs doesn't have this code deployed yet,1390559950,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,"Still getting this issue on betalabs.
+
+Copied Reference list from this
+page:http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january?veaction=edit
+
+
+
+Pasted on the
+page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Paste_reference&action=edit
+
+The resulting wikitext is:
+reference<sup>[1]</sup>
+# reference",1390530965,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,"Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430358,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,"Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317342,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF","Screenshot
+
+Steps to reproduce:
+
+1.Open the VE in Chrome browser for a page which contains image
+2.Copy the image
+3.Open another VE in FireFox browser
+4.Paste the copied image
+
+Observed Result:
+Image does not get copied.An error appears in the console:
+TypeError: item is undefined
+	
+
+...nction(){return this.getData(this.balancedRange);};ve.dm.LinearData=function VeD...
+
+load.p...2128Z&* (line 122)
+
+See the screenshot attached.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+http://en.wikipedia.beta.wmflabs.org/wiki/30th_december_ff?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12694}",1388441100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-udmrgnust5cyxf2ghvzk,task_description,resolved
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF",Verified the fix in test2,1391131595,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF",Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Jan_24th?veaction=edit,1390593751,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF",betalabs doesn't have this code deployed yet,1390559938,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF",I can still reproduce it on Betalabs,1390531301,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF","Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430352,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF","Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317322,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template","Warning in the save dialog box
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add the template Cite Web from Insert>Transclusion
+3.Save the page
+4.Reopen the page with VE
+5.Do some more edit in that page
+5.Click on ""Save Page""
+
+Observed Result:
+A warning appears in the save dialog box ""You edit may have been corrupted-Please review your changes""
+
+This error appears everytime I add this Cite Web template even though there is no apparent reason for being my edit corrupted.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12545}",1388269860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-24fbkjihpzafrhlh33na,task_description,resolved
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template","Change 115510 abandoned by Jforrester:
+[Browser test] WIP Additional Scenario for bug 59091 regression.
+
+Reason:
+Not currently being worked on AFAICT.
+
+https://gerrit.wikimedia.org/r/115510",1396279329,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-24fbkjihpzafrhlh33na,task_subcomment,NA
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template","Change 115510 had a related patch set uploaded by Jhall:
+[Browser test] WIP Addtional Scenario for bug 59091 regression.
+
+https://gerrit.wikimedia.org/r/115510",1393360356,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-24fbkjihpzafrhlh33na,task_subcomment,NA
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template",Got fixed with the fix of https://bugzilla.wikimedia.org/show_bug.cgi?id=59002,1389909929,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-24fbkjihpzafrhlh33na,task_subcomment,NA
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template","**spektre1** wrote:
+
+Tested on my private install. Any transclusion at all seems to throw it this error in the save dialog.",1389305990,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-24fbkjihpzafrhlh33na,task_subcomment,NA
+VisualEditor:Cannot Edit any page in betalabs,"Attempting to edit any page in betalabs is giving following error:
+Error loading data from server: internal_api_error_MWException: Exception Caught: Tag hook for namespace is not callable.
+
+In the console,I see the following error
+Uncaught TypeError: Cannot read property '$actions' of null
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27th_december
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1388182380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-edd62atl2rczsx2d656j,task_description,declined
+VisualEditor:Cannot Edit any page in betalabs,This issue is not happening anymore in betalabs now.I can now open any page to edit.,1388204152,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-edd62atl2rczsx2d656j,task_subcomment,NA
+VisualEditor:Cannot Edit any page in betalabs,"Error message from exception.log is: 
+
+2013-12-27 22:53:15 deployment-apache33 enwiki: [f9bc37e3] /w/api.php   Exception from line 3585 of /data/project/apache/common-local/php-master/includes/parser/Parser.php: Tag hook for namespace is not callable
+
+#0 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3333): Parser->callParserFunction(Object(PPTemplateFrame_DOM), 'NAMESPACE', Array)
+#1 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#2 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3247): PPFrame_DOM->expand(Object(PPNode_DOM))
+#3 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#4 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3483): PPFrame_DOM->expand(Object(PPNode_DOM))
+#5 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#6 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1532): PPFrame_DOM->expand(Object(DOMElement), 4)
+#7 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1540): PPTemplateFrame_DOM->getNamedArgument('group allowed')
+#8 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3947): PPTemplateFrame_DOM->getArgument('group allowed')
+#9 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1132): Parser->argSubstitution(Array, Object(PPTemplateFrame_DOM))
+#10 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3247): PPFrame_DOM->expand(Object(PPNode_DOM))
+#11 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#12 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3247): PPFrame_DOM->expand(Object(PPNode_DOM))
+#13 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#14 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3488): PPFrame_DOM->expand(Object(PPNode_DOM))
+#15 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#16 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3483): PPFrame_DOM->expand(Object(PPNode_DOM))
+#17 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPFrame_DOM))
+#18 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3150): PPFrame_DOM->expand(Object(PPNode_DOM), 0)
+#19 /data/project/apache/common-local/php-master/includes/parser/Parser.php(1212): Parser->replaceVariables('{{editnotice lo...')
+#20 /data/project/apache/common-local/php-master/includes/parser/Parser.php(395): Parser->internalParse('{{editnotice lo...')
+#21 /data/project/apache/common-local/php-master/includes/cache/MessageCache.php(1064): Parser->parse('{{editnotice lo...', Object(Title), Object(ParserOptions), true)
+#22 /data/project/apache/common-local/php-master/includes/Message.php(845): MessageCache->parse('{{editnotice lo...', NULL, true, true, Object(StubUserLang))
+#23 /data/project/apache/common-local/php-master/includes/Message.php(590): Message->parseText('{{editnotice lo...')
+#24 /data/project/apache/common-local/php-master/includes/Message.php(669): Message->toString()
+#25 /data/project/apache/common-local/php-master/includes/Title.php(4892): Message->parseAsBlock()
+#26 /data/project/apache/common-local/php-master/extensions/VisualEditor/ApiVisualEditor.php(298): Title->getEditNotices()
+#27 /data/project/apache/common-local/php-master/includes/api/ApiMain.php(862): ApiVisualEditor->execute()
+#28 /data/project/apache/common-local/php-master/includes/api/ApiMain.php(387): ApiMain->executeAction()
+#29 /data/project/apache/common-local/php-master/includes/api/ApiMain.php(358): ApiMain->executeActionWithErrorHandling()
+#30 /data/project/apache/common-local/php-master/api.php(76): ApiMain->execute()
+#31 /data/project/apache/common-local/w/api.php(3): require('/data/project/a...')
+#32 {main}",1388184890,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-edd62atl2rczsx2d656j,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open the editor for page
+2.Go to Insert>Template
+3.Search for template Cite Web
+4.Add a a value for source title field but keep the URL field empty
+5.Add the template
+6.Click the button ""Save Page""
+
+Observed Result: 
+The ""Save Page"" button does not work .In the console it is showing an error:
+Uncaught TypeError: Object [object Text] has no method 'setAttribute'
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55985
+
+**Attached**: {F12409}",1388169840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jqbci4yiint3kpdehjhn,task_description,resolved
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,Works for mw.org in Chrome now.Might be a caching issue.,1389900032,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"(In reply to comment #21)
+> This issue is verified for test2.But in mw.org I still cannot save after
+> adding
+> a template in Chrome 26.0.1410.65, however it does not show any error in the
+> console as such Uncaught TypeError: Object [object Text] has no method
+> 'setAttribute'
+> 
+> In FireFox, it works for both test 2 and mw.org.
+> 
+> Hence reopening it.If it is a separate issue please Close this one , I will
+> file a separate issue for mw.org
+
+Maybe if you refresh it will go away? Sounds most likely like a cacheing issue…",1389891174,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,Can't reproduce on mw.org. Which template did you use?,1389891018,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"This issue is verified for test2.But in mw.org I still cannot save after adding a template in Chrome 26.0.1410.65, however it does not show any error in the console as such Uncaught TypeError: Object [object Text] has no method 'setAttribute'
+
+In FireFox, it works for both test 2 and mw.org.
+
+Hence reopening it.If it is a separate issue please Close this one , I will file a separate issue for mw.org",1389845563,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,Now fixed and back-ported to production.,1389837750,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107638 merged by Catrope:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107638",1389831589,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107530 merged by Catrope:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107530",1389831578,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107640 merged by Catrope:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107640",1389831553,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107531 merged by Catrope:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107531",1389831544,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107640 had a related patch set uploaded by Catrope:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107640",1389819206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107638 had a related patch set uploaded by Catrope:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107638",1389818593,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107559 merged by jenkins-bot:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107559",1389817561,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107559 had a related patch set uploaded by Esanders:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107559",1389784095,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,data-ve-ignore showing up in converter in some cases still. Working on a fix.,1389782794,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Fix has been merged, backported and will be deployed during tomorrow's lightning deploy window (Thu Jan 16 00:00 - 00:30 UTC; Wed Jan 15 16:00 - 16:30 PST)",1389754131,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107511 merged by jenkins-bot:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107511",1389749660,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107531 had a related patch set uploaded by Catrope:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107531",1389749651,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107530 had a related patch set uploaded by Catrope:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107530",1389749596,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107511 had a related patch set uploaded by Esanders:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107511",1389743226,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,*This is happening for adding all templates on test2*,1389730479,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,This s\is happening for adding all templates on test2.,1389730436,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Adding to my previous comment: when i try to switch to wiki markup mode i get the same error. No way to save my stuff :(
+
+Here's a stack trace:
+
+Uncaught TypeError: Object [object Text] has no method 'setAttribute' 
+ve.dm.MWTransclusionNode.static.toDomElements 
+ve.dm.Converter.getDomElementsFromDataElement 
+ve.dm.Converter.getDomSubtreeFromData 
+ve.dm.MWReferenceNode.static.toDomElements 
+ve.dm.Converter.getDomElementsFromDataElement 
+ve.dm.Converter.getDomSubtreeFromData 
+ve.dm.Converter.getDomSubtreeFromModel 
+ve.dm.Converter.getDomFromModel 
+ve.init.mw.ViewPageTarget.editSource 
+ve.ui.MWEditModeSourceTool.onSelect 
+OO.ui.ToolGroup.onMouseUp 
+OO.ui.PopupToolGroup.onMouseUp 
+proxy 
+jQuery.event.dispatch 
+elemData.handle.eventHandle",1389616325,PHID-USER-no27b6dclreknhhzodyn,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"I can reproduce this problem as well. A pity, because not being able to save makes the Visual Editor, well, pretty much useless. I've changed priority to 'High' for that reason.",1389616198,PHID-USER-no27b6dclreknhhzodyn,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27th_december&veaction=edit",1388169940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor: Alt + any key in a slug introduces a pawn in Firefox on Windows,"With FireFox (compulsory) on Windows
+insert a new line then enter : Alt A (or Alt + any key)
+=> a pawn is inserted
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61538",1387409040,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-nbwk4dgm4c4qnjzg6thr,task_description,resolved
+VisualEditor: Alt + any key in a slug introduces a pawn in Firefox on Windows,Have re-tested; no issue any more.,1421282349,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nbwk4dgm4c4qnjzg6thr,task_subcomment,NA
+VisualEditor: Alt + any key in a slug introduces a pawn in Firefox on Windows,"Looks like alt+a doesn't fire a KeyPress event in Chrome whereas it does in FF. As slugs are always pawned, and there is no inserted content from alt+a we have a problem.",1387465822,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nbwk4dgm4c4qnjzg6thr,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,"VisualEditor supports the 'apex' skin, however that isn't installed on WMF projects, so users using a non-supported skin will see ""&lt;skinname-apex&gt;"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387340940,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-tudylk7ksc5zbhsewjyu,task_description,resolved
+BetaFeatures: Validate skin requirement is installed before showing it,"Sorry, page error. This comment is for bug 70814.",1410617419,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,"The current state on the Wikimedia project is without the names of the required skins. In the case it is wanted to keep the current state (for Wikimedia and/or for the master branch of BetaFeatures), this feature can be hidden with CSS, similarly to the browser requirements, by editing BetaFeatures/resources/betafeatures.less.",1410617306,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,"Change 102383 merged by jenkins-bot:
+Don't show skin names if the user can't enable them
+
+https://gerrit.wikimedia.org/r/102383",1404238799,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,*** Bug 63151 has been marked as a duplicate of this bug. ***,1395898645,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,"Change 102383 had a related patch set uploaded by Legoktm:
+Don't show skin names if the user can't enable them
+
+https://gerrit.wikimedia.org/r/102383",1387341704,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+VisualEditor:Reference is getting copied as an empty <ref/> tag,"screenshot of the error
+
+Steps to reproduce:
+
+1.Go to this page:
+
+https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/12th_december&veaction=edit
+
+2.Copy the reference and the reference list at the end of this page
+3.Paste in into another VE
+4.Save it
+
+Observed Result:
+
+The wiki text for the text copied is: 
+
+reference<ref>http://cnn.com</ref>
+<references />
+
+The wiki text on the page where it is copied to:
+reference<ref />
+<references />
+
+In Edit mode it says:
+The reference is defined in a template or other generated block and for now can
+only be edited in source mode.
+
+and the reference cannot be edited using VE
+
+
+In read mode it shows:
+
+Cite error: The opening <ref> tag is malformed
+or has a bad name (see the help page).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12112}",1386894600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sxmma4s54vfesb7w6uwo,task_description,resolved
+VisualEditor:Reference is getting copied as an empty <ref/> tag,"verified the fix in test2 with  MediaWiki 1.23wmf8 on page:
+https://test2.wikipedia.org/wiki/Another_page20th",1387559522,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sxmma4s54vfesb7w6uwo,task_subcomment,NA
+VisualEditor:Reference is getting copied as an empty <ref/> tag,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/December_16th,1387211609,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sxmma4s54vfesb7w6uwo,task_subcomment,NA
+VisualEditor:Reference is getting copied as an empty <ref/> tag,This appears to be fixed in master. Please re-open if you can reproduce on beta labs.,1387210816,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sxmma4s54vfesb7w6uwo,task_subcomment,NA
+VisualEditor: Transclusion template suggestions are no longer available,"**Author:** `jhall`
+
+**Description:**
+Seen in beta labs with these repro steps:
+
+1)  Open Visual Editor.
+2)  Select ""Transclusion"" from the ""Insert"" menu.
+3)  Type some characters in the ""New Template"" text box.
+
+In previous releases of VE, the user would get a list of template suggestions.  That list of suggestions doesn't seem to be displaying anymore :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53231",1386875760,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_description,declined
+VisualEditor: Transclusion template suggestions are no longer available,Now the template suggestions are appearing.,1388168683,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_subcomment,NA
+VisualEditor: Transclusion template suggestions are no longer available,"This is again happening on betalabs.I dont see any template suggestion appearing. 
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/26th_december?veaction=edit",1388082270,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_subcomment,NA
+VisualEditor: Transclusion template suggestions are no longer available,"**jhall** wrote:
+
+(In reply to comment #1)
+> This seems to work for me? Which browser is this in? (Tested in Mac/Chrome 31
+> and Mac/Firefox 25.)
+
+Hmmm… this does now seem to be working in beta labs with Chrome, Firefox, and Safari on Mac OS.  I successfully get transclusion template suggestions for the letters C, N, T, and W.  My favorite suggestion so far is ""Noble Pipe"".  Not sure what that is, but it's a great name for a transclusion template.
+
+I'll update the automated browser test to search by one of the letters indicated above (rather than by ""S"", which doesn't currently return any suggestions).",1387296859,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_subcomment,NA
+VisualEditor: Transclusion template suggestions are no longer available,This seems to work for me? Which browser is this in? (Tested in Mac/Chrome 31 and Mac/Firefox 25.),1387245213,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Screenshot inside reference
+
+We have changed the toolbar design to have all the formatting under one button A (underlined) and all other options to add elements under Insert option.
+
+But if you open up the Media Settings or a Reference the toolbar that appears there does not conform with the new design.
+It will better to have a consistent design everywhere the toolbar is used.
+
+See the screemshots attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12060}",1386874140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i73bqleta3mxkalcjer2,task_description,resolved
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit,1386965991,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,Now being deployed on wmf7.,1386890427,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Change 101047 merged by Catrope:
+Use the same new toolbar for media and reference dialogs
+
+https://gerrit.wikimedia.org/r/101047",1386890178,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Change 101039 merged by jenkins-bot:
+Use the same new toolbar for media and reference dialogs
+
+https://gerrit.wikimedia.org/r/101039",1386876744,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Change 101047 had a related patch set uploaded by Jforrester:
+Use the same new toolbar for media and reference dialogs
+
+https://gerrit.wikimedia.org/r/101047",1386876707,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Change 101039 had a related patch set uploaded by Jforrester:
+Use the same new toolbar for media and reference dialogs
+
+https://gerrit.wikimedia.org/r/101039",1386876171,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Created attachment 14073
+toolbar inside media settings
+
+**Attached**: {F12061}",1386874279,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: Clouds are added at the end of a paste,"A could sometimes suddenly appears. As well as 'left over sections' it seems.
+
+https://www.mediawiki.org/w/index.php?title=User:TheDJ/sandbox&oldid=841359
+
+I think this was due to ""select all"" cmd-A, then cmd-v paste over the old content.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386844260,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-npjjopn76exjm4ew3cxf,task_description,resolved
+VisualEditor: Clouds are added at the end of a paste,I believe we fixed this bug with the CE select-all change that Ed worked on two months ago.,1402508824,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-npjjopn76exjm4ew3cxf,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Steps to reproduce:
+
+
+1.Open the editor for a page which contains link
+
+2.Copy it.
+
+3.Paste it into a new line 
+
+4.Save it
+
+Observed Result:
+The link is getting merged on to the end of the previous line
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386790440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_description,resolved
+VisualEditor: CE adds linebreaks when pasting into empty lines,*The fix for the original issue has been verified in test 2 with mediawiki 1.23wmf8*,1387484260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"The original issue of this bug has been verified in test 2 with MediaWiki 1.23wmf8 
+on page:https://test2.wikipedia.org/wiki/19th_december",1387484077,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,This is a new bug and something to do with Parsoid and Selser. Filed as bug 58695.,1387471583,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"After these steps if you try copying a math function or a link on the third line of Page B , it will also get merged with the two merged links",1387470527,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Sorry, here are the detailed steps: 
+
+1.Create a page ""A"" with three links in three consecutive lines.
+2.Create another page ""B"" where you will copy these links to.
+3.Copy the first and second link to ""B""
+4.Save it.
+5.Reopen the editor.
+6.Now copy the third link and paste it to the third line of ""B""
+7.Save it.
+
+Observed Result:
+The second and the third link in page B is getting merged.
+
+Example Pages:
+
+A:http://en.wikipedia.beta.wmflabs.org/wiki/19th_december_source?veaction=edit
+B:http://en.wikipedia.beta.wmflabs.org/wiki/19th_destination",1387468526,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,Works for me in Chrome and Firefox. Please provide detailed instructions if you can reproduce.,1387466105,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"I am still getting the issue of two links getting merged in one line after pressing enter after pasting the first link:
+http://en.wikipedia.beta.wmflabs.org/wiki/December_17th",1387310733,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Change 101905 merged by jenkins-bot:
+Strip trailing linebreaks on paste due to Chrome bug
+
+https://gerrit.wikimedia.org/r/101905",1387306391,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Change 101905 had a related patch set uploaded by Esanders:
+Strip trailing linebreaks on paste due to Chrome bug
+
+https://gerrit.wikimedia.org/r/101905",1387218312,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,This latest version of the bug is known issue with CE in Chrome when pasting into a newline.,1387214118,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Modification in steps to reproduce:
+
+1.Open the editor 
+2.Copy a link or a text
+3.Paste it into another VE
+4.Observed that the cursor is automatically to the next line though you have not pressed Enter/return
+5.Now paste the link or the text again in that position without pressing enter
+6.Save the page
+
+Observed Result:
+The texts or the links are getting merged in the same line",1387210853,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,The issue of link getting merged is still reproducible in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/December_16th,1387209664,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Another issue which I think might be related with this, if not I will file separate bug:
+
+Steps to reproduce:
+
+
+1.Open the editor for a page 
+
+2.Copy a text
+
+3.Paste it into another page
+
+4.Copy an image and paste it onto the next line
+
+Observed Result:
+The image does not gets pasted in the other VE.",1386794603,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Modification in steps to reproduce:
+
+step 3 :paste it into a newline on another page or VE",1386793274,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Created attachment 14062
+Screenshot
+
+**Attached**: {F12812}",1386791724,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=11th_december",1386790517,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Steps to reproduce:
+
+1.Open the Editor.
+2.Place the cursor inside a word or text but do not select anything
+3.Press command+c
+4.Now go to another page and do command+v (Nothing is getting copied, which is okay as per the fix given in https://bugzilla.wikimedia.org/show_bug.cgi?id=58138)
+5.But now select anything from the source page by selecting it
+6.Press command+c
+7.Press command+V onto the other page where you were pasting.
+
+Observed Result:
+Nothing gets copied
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386788820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kq6jtegqhbf7n3nonedr,task_description,resolved
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,Pushed to wmf6.,1386808461,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Change 100915 merged by jenkins-bot:
+Move resetting of paste state variables to after afterPaste
+
+https://gerrit.wikimedia.org/r/100915",1386803574,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Change 100915 had a related patch set uploaded by Jforrester:
+Move resetting of paste state variables to after afterPaste
+
+https://gerrit.wikimedia.org/r/100915",1386799598,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,Verified on betalabs,1386796268,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Change 100827 merged by jenkins-bot:
+Move resetting of paste state variables to after afterPaste
+
+https://gerrit.wikimedia.org/r/100827",1386790134,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Change 100827 had a related patch set uploaded by Esanders:
+Move resetting of paste state variables to after afterPaste
+
+https://gerrit.wikimedia.org/r/100827",1386789819,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Test Environment:betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5",1386788905,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+Special:ExtensionDistributor/VisualEditor not picking up REL1_22,"Maybe some new config has to be added for it to consider REL1_22 as a valid branch to download?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386779400,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-6rfydyjylk7nntzf43tk,task_description,resolved
+Special:ExtensionDistributor/VisualEditor not picking up REL1_22,"Change 100799 merged by jenkins-bot:
+Add REL1_22 to ExtensionDistributor branches
+
+https://gerrit.wikimedia.org/r/100799",1386780385,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6rfydyjylk7nntzf43tk,task_subcomment,NA
+Special:ExtensionDistributor/VisualEditor not picking up REL1_22,"Change 100799 had a related patch set uploaded by Reedy:
+Add REL1_22 to ExtensionDistributor branches
+
+https://gerrit.wikimedia.org/r/100799",1386780267,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6rfydyjylk7nntzf43tk,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Safari 7
+
+Copy on https://www.mediawiki.org/wiki/VisualEditor?veaction=edit
+
+From and including the header Timeline, up to the paragraph before ""Notes"" headline (including the table).
+
+Past in an empty surface:
+
+[Error] TypeError: 'undefined' is not an object (evaluating 'source.clone')
+	copy (undefined, line 3)
+	getClonedElement
+	fixupInsertion
+	fixupInsertion
+	newFromDocumentInsertion
+	afterPaste
+	proxy (load.php, line 10)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386752340,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-3vfkchuyvemtkqdiybsv,task_description,resolved
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,Pushed to wmf6.,1386808472,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Change 100916 merged by jenkins-bot:
+Allow tables to contain captions!
+
+https://gerrit.wikimedia.org/r/100916",1386803625,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Change 100916 had a related patch set uploaded by Jforrester:
+Allow tables to contain captions!
+
+https://gerrit.wikimedia.org/r/100916",1386799611,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Change 100792 merged by jenkins-bot:
+Allow tables to contain captions!
+
+https://gerrit.wikimedia.org/r/100792",1386786079,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Change 100792 had a related patch set uploaded by Esanders:
+Allow tables to contain captions!
+
+https://gerrit.wikimedia.org/r/100792",1386776728,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,Part of this appears to be caused by table captions. Investigating.,1386775890,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"More detail: the problem is caused by ContentEditable (surprise). When you paste a table into an empty paragraph, the paragraph is *completely* deleted, which the paste context comparer can't currently deal with.",1386774900,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,The problem here is that fixUpInsertion is deciding you can't put a table in a paragraph but not resolving properly.,1386774787,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Typing between text and a reference produces a pawn in Firefox,"This came from the Hebrew Wikipedia feedback page, I could not replicate it in the English Wikipedia
+
+It seems to happen only in Firefox.
+
+
+To reproduce -
+
+1. Go to this sample page: https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Nurick/%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_-_%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99&oldid=14834614&veaction=edit
+
+2. Put the cursor a couple of character to the left of the word ""יפן"" (third paragraph, the word with the reference attached)
+
+3. Move the cursor so it is between the word and the reference.
+
+4. Add a period.
+
+Watch a pawn appear.
+
+* Firefox 25.0.1 on Windows and on Ubuntu
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386748620,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-fbvcimq5q66ajybncb7c,task_description,resolved
+VisualEditor: Typing between text and a reference produces a pawn in Firefox,This appears to be now fixed. I think.,1406596147,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fbvcimq5q66ajybncb7c,task_subcomment,NA
+VisualEditor: Typing between text and a reference produces a pawn in Firefox,*** Bug 67620 has been marked as a duplicate of this bug. ***,1404763355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fbvcimq5q66ajybncb7c,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki","This is an interesting feedback comment that came from the Hebrew Wikipedia and I managed to also replicate in the English Wikipedia. 
+
+Steps to replicate:
+
+1. Go to a Sandbox page under a username. For example, this page https://en.wikipedia.org/w/index.php?title=User:Mooeypoo/Sandbox&veaction=edit
+
+2. Mark one of the words and add an existing page to link to it. For instance, I marked 'some' and chose the link to ""Somerset"".
+
+3. Inspect the link while still in VisualEditor - the link is under the user namespace, so in my example, the link is now ""https://en.wikipedia.org/wiki/User:Mooeypoo/Somerset""
+
+4. Save the page.
+
+5. After save, the link seems fine (points to https://en.wikipedia.org/wiki/Somerset as it should).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59196",1386745260,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-yavg34kffrrjkowzgnkc,task_description,resolved
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki","Change 119914 merged by jenkins-bot:
+Hack around Parsoid's href prefixing in rendering new links
+
+https://gerrit.wikimedia.org/r/119914",1395874565,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki",*** Bug 59196 has been marked as a duplicate of this bug. ***,1395363345,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki","Change 119914 had a related patch set uploaded by Jforrester:
+Hack around Parsoid's href prefixing in rendering new links
+
+https://gerrit.wikimedia.org/r/119914",1395363291,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki",*** Bug 59196 has been marked as a duplicate of this bug. ***,1395344109,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki",*** Bug 62877 has been marked as a duplicate of this bug. ***,1395344091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"Broken UI
+
+Steps to reproduce:
+
+
+1.Open the editor 
+2.create a link
+3.Save the page
+4.Re-open the editor.
+5.Select the link to modify it
+
+Observed Result:
+
+Link inspector is not opening.Coming back from some other window opens it but the UI is totally broken
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12763}",1386721860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eoqysm7gglrd73chhak6,task_description,resolved
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,verified on test2:https://test2.wikipedia.org/w/index.php?title=13th_december&veaction=edit,1386982947,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,verified in betalabs.,1386805068,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"Change 100828 merged by jenkins-bot:
+Followup 5d7673eb: still adjust width/height when positioning fails
+
+https://gerrit.wikimedia.org/r/100828",1386792229,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"Change 100828 had a related patch set uploaded by Catrope:
+Followup 5d7673eb: still adjust width/height when positioning fails
+
+https://gerrit.wikimedia.org/r/100828",1386790070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"yes, i can still reproduce it .",1386787011,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,Can you still reproduce this? It works for me.,1386786919,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"
+Test Environment:betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example:http://en.wikipedia.beta.wmflabs.org/wiki/Latex?veaction=edit",1386722053,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"Created attachment 14053
+No link inspector opening up
+
+**Attached**: {F12764}",1386721962,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","screenshot of the error and empty Latex window
+
+Steps to reproduce:
+
+1.Add a bullet list
+2.Add a template as a bulleted item
+3.Save the page and reopen the editor
+4.Go to the next line of the bulleted list (get rid of bullets by pressing return twice)
+
+5.Click on More>Latex
+
+Observed Result:
+
+The latex window is opening up at the right end, where the template is placed.
+
+6.Then if you change the focus by clicking somewhere on the page outside the latex window
+
+Observed Result:
+
+A blank Latex windows is opening up and a uncaught type error appears Uncaught TypeError: Cannot call method 'getOuterRange' of null 
+
+If you save the page and go to edit source , you will see empty <math> tag is getting placed
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62797
+
+**Attached**: {F12725}",1386706860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yd7ochttyhijjxl6b2jj,task_description,resolved
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",Verified the fix in production,1398988255,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",Verified the fix in test2,1398898767,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Change 129622 merged by jenkins-bot:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/129622",1398384371,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Change 129622 had a related patch set uploaded by Jforrester:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/129622",1398384255,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",Verified the fix on Betalabs,1397855570,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Change 126900 merged by jenkins-bot:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/126900",1397845433,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Change 126900 had a related patch set uploaded by Esanders:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/126900",1397780751,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",This code as of gerrit 126900 is moving back into VE's repo where it needs to be fixed.,1397705234,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",*** Bug 62797 has been marked as a duplicate of this bug. ***,1397704103,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","This happens because ve.ui.MWMathInspector.prototype.setup assumes that after calling insertContent() to insert a math node, the selection will cover the math node exactly. But in a block slug, that's not true, because fixupInsertion will have amended the insertion to wrap the math node in a paragraph. Then when the selection does not precisely cover a FocusableNode, focusedNode will be null.",1387229637,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Modification in steps to reproduce:
+
+4.There is an empty bullet place cursor there and then go to More>Latex
+
+It can also be reproduced by adding image in step 2.",1386719531,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Created attachment 14050
+emtpy <math> tags
+
+**Attached**: {F12726}",1386707070,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"E.g. copying the disclaimer from my staff page https://www.mediawiki.org/wiki/User:Jdforrester_%28WMF%29 takes:
+
+<p><b>Disclaimer:</b> Although I work for the Wikimedia Foundation, contributions under this account do not necessarily represent the actions or views of the Foundation unless expressly stated otherwise. For example, edits to articles or uploads of other media are done in my individual, personal capacity unless otherwise stated.</p>
+
+… and turns it into the wikitext:
+
+'''Disclaimer:'''
+<nowiki> </nowiki>Although I work for the Wikimedia Foundation, contributions under this
+account do not necessarily represent the actions or views of the
+Foundation unless expressly stated otherwise. For example, edits to
+articles or uploads of other media are done in my individual, personal
+capacity unless otherwise stated.
+
+… (with the newlines showing before saving; not a Parsoid bug).
+
+No new lines added when doing a plain paste.",1386702300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f4tvdtjt3vze2yti62aa,task_description,resolved
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"Change 100614 merged by Catrope:
+Fix paste sequence in Firefox
+
+https://gerrit.wikimedia.org/r/100614",1386720865,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f4tvdtjt3vze2yti62aa,task_subcomment,NA
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"Change 100613 merged by jenkins-bot:
+Fix paste sequence in Firefox
+
+https://gerrit.wikimedia.org/r/100613",1386703730,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f4tvdtjt3vze2yti62aa,task_subcomment,NA
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"Change 100614 had a related patch set uploaded by Jforrester:
+Fix paste sequence in Firefox
+
+https://gerrit.wikimedia.org/r/100614",1386703720,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f4tvdtjt3vze2yti62aa,task_subcomment,NA
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"Change 100613 had a related patch set uploaded by Esanders:
+Fix paste sequence in Firefox
+
+https://gerrit.wikimedia.org/r/100613",1386703041,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f4tvdtjt3vze2yti62aa,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"Failed to read file: exception 'Exception' with message 'Expected open tag, whitespace, or variable., got T_STRING ('array_map')' in /a/common/php-1.23wmf6/extensions/LocalisationUpdate/QuickArrayReader.php:135
+Stack trace:
+#0 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/QuickArrayReader.php(119): QuickArrayReader->except(Array, 'open tag, white...')
+#1 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(528): QuickArrayReader->__construct('<?php $messages...')
+#2 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(313): LocalisationUpdate::parsePHP('$messages = arr...', 'messages')
+#3 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(435): LocalisationUpdate::loadFilesToCompare('VisualEditor', '/var/lib/l10nup...', '/a/common/php-1...', false, false)
+#4 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(153): LocalisationUpdate::compareExtensionFiles('VisualEditor', '/var/lib/l10nup...', '/a/common/php-1...', false)
+#5 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(113): LocalisationUpdate::updateExtensionMessages('/a/common/php-1...', 'VisualEditor', false, '/var/lib/l10nup...')
+#6 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/update.php(34): LocalisationUpdate::updateMessages(Array)
+#7 /a/common/multiversion/MWScript.php(97): require_once('/a/common/php-1...')
+#8 {main}
+Failed to parse /var/lib/l10nupdate/mediawiki/extensions/VisualEditor/VisualEditor.i18n.php
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386642780,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-y4bnpd7zbos4ftiaptko,task_description,resolved
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"(In reply to Amir E. Aharoni from comment #6)
+> Is this fixed now?
+
+I believe it will be fixed by gerrit 119944 when that is merged and deployed.",1395520301,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,Is this fixed now?,1395519881,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"Please see https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/LocalisationUpdate+branch:json-rewrite,n,z",1394795013,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,This issue is tracked in mingle at https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/3897,1387482123,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"(In reply to comment #2)
+> Change 100527 merged by jenkins-bot:
+> Revert ""Shim for VisualEditor.i18n.php that reads JSON blobs""
+> 
+> https://gerrit.wikimedia.org/r/100527
+This has been reintroduced, because despite the scary-looking exception, it didn't actually break LU for anything other than VE.",1386721977,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"Change 100527 merged by jenkins-bot:
+Revert ""Shim for VisualEditor.i18n.php that reads JSON blobs""
+
+https://gerrit.wikimedia.org/r/100527",1386643458,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"Change 100527 had a related patch set uploaded by Jforrester:
+Revert ""Shim for VisualEditor.i18n.php that reads JSON blobs""
+
+https://gerrit.wikimedia.org/r/100527",1386643286,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+"VisualEditor: On load, don't select a node if it's the first thing in the document","Ed,
+
+Think you were working on this before? Would be lovely to finally get this fixed…
+
+J.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57477",1386641760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nesgwricmarnjfu5yju5,task_description,resolved
+"VisualEditor: On load, don't select a node if it's the first thing in the document",Verified the fix on test2,1389906629,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nesgwricmarnjfu5yju5,task_subcomment,NA
+"VisualEditor: On load, don't select a node if it's the first thing in the document","Change 106707 merged by jenkins-bot:
+Move initial selection to first content offset
+
+https://gerrit.wikimedia.org/r/106707",1389641452,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nesgwricmarnjfu5yju5,task_subcomment,NA
+"VisualEditor: On load, don't select a node if it's the first thing in the document","Change 106707 had a related patch set uploaded by Esanders:
+Move initial selection to first content offset
+
+https://gerrit.wikimedia.org/r/106707",1389367335,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nesgwricmarnjfu5yju5,task_subcomment,NA
+"VisualEditor: On load, don't select a node if it's the first thing in the document",Any update on this? It's a significant UX issue.,1387305115,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-nesgwricmarnjfu5yju5,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"The Errors
+
+Steps to reproduce:
+
+1.Open an editor which has a text with reference and the reflist
+For example:
+
+text with reference[1]
+↑ ref
+
+2.Try to paste it into a different page
+
+Observed Result:
+Uncaught TypeError: Cannot read property 'length' of undefined appears and nothing gets pasted.
+
+However the ""Save Page"" button is active and clicking on that gives the error:
+Uncaught TypeError: Cannot call method 'getRange' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12622}",1386630120,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-unomzqtpqw6kv6noyrev,task_description,resolved
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,Yes please. Give steps with wikitext to reproduce.,1386894085,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Checked the fix in production.The issue specified in this bug is fixed.Reference is getting pasted with reference list and the subsequent elements are getting copy-pasted properly.But still there is a problem with pasting reference :(
+
+The reference is getting copied as an empty <ref/> tags and on edit mode it says 
+The reference is defined in a template or other generated block and for now can only be edited in source mode.
+
+In read mode: There is an error:Cite error: The opening <ref> tag is malformed or has a bad name (see the help page).
+
+Should I create a different issue ticket for that?",1386893689,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,Now being deployed on wmf6 and wmf7.,1386890311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101133 merged by Catrope:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101133",1386890076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101134 merged by Catrope:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101134",1386890063,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101134 had a related patch set uploaded by Catrope:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101134",1386890036,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101131 merged by jenkins-bot:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101131",1386890024,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101133 had a related patch set uploaded by Catrope:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101133",1386890020,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101131 had a related patch set uploaded by Esanders:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101131",1386889396,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"In production, go to this page :https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/12th_december&veaction=edit
+
+Copy the last reference along with reference list and try to paste it into another page.
+And after that nothing can be copied into the other VE",1386888679,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"I am escalating this issue, because it is now reproducible in production:https://en.wikipedia.org/wiki/ and after this action copy-paste does not work from one VE to another.",1386887125,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page with reference and reflist: :http://en.wikipedia.beta.wmflabs.org/wiki/Bold?veaction=edit",1386630288,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Table format in destination page
+
+Steps to reproduce:
+
+1.Open the editor.
+2.Copy a template with a parameter which has a value and paste it into a different page
+3.Copy a template which does not have any parameter  and paste it into a different page
+4.Copy a template with a parameter which does not have any value.
+
+
+Observed Result:
+
+
+1.All the template copied are getting pasted as a table
+2.If you switch to the edit source you will see :
+
+the template copied in step 2 has a table format
+the template copied in step 3 is getting pasted in an empty template wikitext format:{|
+!
+|}
+
+the template copied in step 4 is getting pasted in a template wikitext format with the page name inside it:{|
+!Copy
+|}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12618}",1386629040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nm5utpa7p43ribr4hikq,task_description,resolved
+VisualEditor: Template is getting pasted as a table while doing copy-paste,verified in production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/13th_december,1386983673,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,(And back-ported to wmf6.),1386810383,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Change 100943 merged by Catrope:
+Fix issues with copy-pasting MWTransclusionNodes
+
+https://gerrit.wikimedia.org/r/100943",1386809823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Change 100943 had a related patch set uploaded by Catrope:
+Fix issues with copy-pasting MWTransclusionNodes
+
+https://gerrit.wikimedia.org/r/100943",1386809812,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Change 100775 merged by jenkins-bot:
+Fix issues with copy-pasting MWTransclusionNodes
+
+https://gerrit.wikimedia.org/r/100775",1386809136,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Change 100775 had a related patch set uploaded by Esanders:
+Fix issues with copy-pasting MWTransclusionNodes
+
+https://gerrit.wikimedia.org/r/100775",1386759929,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"For an example
+if you go to this page :http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Paste
+
+I have copied three templates from http://en.wikipedia.beta.wmflabs.org/wiki/Copy
+and they are having these issues.",1386709164,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,Can you give a more specific example. The templates I'm testing on copy and paste okay.,1386707443,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Created attachment 14043
+tooltip and yellow bordered box
+
+**Attached**: {F12620}",1386629528,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"After pasting a template, which has parameter with no value, it does not let user to edit that template on the edit mode.
+and shows a tooltip ""Sorry this element can be edited in source mode now"" with yellow bordered box.
+
+See the screenshot attached",1386629488,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Created attachment 14042
+The edit source section for the destination page
+
+**Attached**: {F12619}",1386629195,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,"screenshot
+
+Steps to reproduce:
+
+1.Open the editor for a page
+2.Place a link to a page
+3.Rename the link text to something different than the destination page name
+4.Save the page
+5.Now copy this link and paste it to another page
+6.Save the second page
+
+Observed Result:
+In the read mode of the second page the wikitext for the link is showing up
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12566}",1386614460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-in4rh3odis5atqwtca5u,task_description,resolved
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,"OK, will mark as FIXED.",1386973700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-in4rh3odis5atqwtca5u,task_subcomment,NA
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,"I cannot reproduce it either now.But, this was a different issue than bug 58136",1386973640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-in4rh3odis5atqwtca5u,task_subcomment,NA
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,I can't reproduce now - is this the same as bug 58136?,1386973295,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-in4rh3odis5atqwtca5u,task_subcomment,NA
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/wiki/Linker",1386614564,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-in4rh3odis5atqwtca5u,task_subcomment,NA
+VisualEditor: Copied/pasted wiki links are prefixed with ./,"See: https://www.mediawiki.org/w/index.php?title=User:Eloquence/CP_tests&oldid=838815
+
+Copied from:
+https://www.mediawiki.org/w/index.php?title=VisualEditor:Welcome&oldid=799120
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386573000,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-4qiopkau6hjwndo32zi6,task_description,resolved
+VisualEditor: Copied/pasted wiki links are prefixed with ./,This was fixed in Ed's series of fixes to rich copy and paste in (I think) the same week this was filed; sorry for the very slow triage.,1394489459,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qiopkau6hjwndo32zi6,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","screenshot of the icon
+
+Steps to reproduce:
+
+1.Open the editor for an article
+2.Place your cursor any position of a link and press command+c.
+3.Open another page and press command+v
+
+Observed:
+ An icon ☁ appears on the second page.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58136
+
+**Attached**: {F12394}",1386377460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hratsjfcabvp22ykev47,task_description,resolved
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too",verified the fix on test2:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/13th_december?veaction=edit,1386983801,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too",Verified in Betalabs,1386787483,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Change 100605 merged by Catrope:
+Check the selection has collapsed after pasting
+
+https://gerrit.wikimedia.org/r/100605",1386720891,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Change 100605 had a related patch set uploaded by Jforrester:
+Check the selection has collapsed after pasting
+
+https://gerrit.wikimedia.org/r/100605",1386700920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Change 100578 merged by jenkins-bot:
+Check the selection has collapsed after pasting
+
+https://gerrit.wikimedia.org/r/100578",1386694996,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Change 100578 had a related patch set uploaded by Esanders:
+Check the selection has collapsed after pasting
+
+https://gerrit.wikimedia.org/r/100578",1386690762,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Ignore that, only works if the cursor is placed on a blank line.",1386675839,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too",Can't reproduce in Chrome 30 on OSX.,1386675792,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Linker?veaction=edit",1386377561,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"**Author:** `Wikifram`
+
+**Description:**
+Version 2013-12-05 (MW 1.23wmf6), implemented at MediaWiki, now for the first time tested apparently (by me)... When you add a reference, the cursor is again positioned at the top of the article, no matter where you insert the reference. The focus (the part you actually see) of the page is where you added the reference, but when you start typing, you are actually adding text to the top of the page. This is confusing as hell. 
+
+The same applies when adding a template, but not with media.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1386320580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_description,resolved
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,*** Bug 57034 has been marked as a duplicate of this bug. ***,1394659143,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,Verified on betalabs,1386805619,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,*** Bug 57438 has been marked as a duplicate of this bug. ***,1386805579,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"A fix for this for wmf6 is going out in about 4 minutes' time; fixing it for wmf5 would involve back-porting half of wmf6, and is too risky. Sorry for the disruption.",1386633441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"Change 100496 merged by jenkins-bot:
+Don't move the cursor to the top of the page after closing a dialog
+
+https://gerrit.wikimedia.org/r/100496",1386632906,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"Change 100490 merged by jenkins-bot:
+Don't move the cursor to the top of the page after closing a dialog
+
+https://gerrit.wikimedia.org/r/100490",1386631280,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"Change 100496 had a related patch set uploaded by Jforrester:
+Don't move the cursor to the top of the page after closing a dialog
+
+https://gerrit.wikimedia.org/r/100496",1386631235,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"Change 100490 had a related patch set uploaded by Catrope:
+Don't move the cursor to the top of the page when closing a dialog
+
+https://gerrit.wikimedia.org/r/100490",1386628831,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,This is actually present in 1.23wmf5 as well.,1386582487,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,*** Bug 58194 has been marked as a duplicate of this bug. ***,1386572578,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","**Author:** `Wikifram`
+
+**Description:**
+Have you ''really'' implemented a new version at MediaWiki that scrolls to the ''bottom'' of the page when opened in VE? Was this intentional or (if I'm allowed to say this) just something that should have been obvious with the most basic test, but somehow wasn't noticed? FF25, W7, nothing fancy or unusual. And no, this didn't happen in earlier versions, and doesn't happen when I use VE on enwiki...
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386319980,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uzu755zs7nfkcf7hr26i,task_description,resolved
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox",A fix for this is going out in about 4 minutes' time. Sorry for the disruption.,1386633345,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","Change 99785 merged by jenkins-bot:
+mw.Target: Fix document focus scroll bug
+
+https://gerrit.wikimedia.org/r/99785",1386633010,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","Change 99785 had a related patch set uploaded by Jforrester:
+mw.Target: Fix document focus scroll bug
+
+https://gerrit.wikimedia.org/r/99785",1386375914,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","Change 99718 merged by jenkins-bot:
+mw.Target: Fix document focus scroll bug
+
+https://gerrit.wikimedia.org/r/99718",1386366052,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","Change 99718 had a related patch set uploaded by Krinkle:
+mw.Target: Fix document focus scroll bug
+
+https://gerrit.wikimedia.org/r/99718",1386361397,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox",Confirming with Firefox 25 on Fedora 20 on mediawiki.org.,1386334403,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","**Wikifram** wrote:
+
+Note that the ''cursor'' is at the top, but the part of the page you view (if the page is longer than the screen) is the bottom, so your cursor isn't even visible when you start typing... If it had been intentional, I suppose that the cursor would have been at the bottom as well (still useless, but at least consistent).",1386320191,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Steps to reproduce:
+
+1.Open any article on VE
+2.Add a bullet list
+3.Try to add an image as a bulleted item of that list ( the image goes to the right side but keep it like that)
+4.Save the page
+5.Reopen the editor
+6.Now go to position where empty bullet list is.
+7.Now try to remove it by clicking ob bullet list icon from the toolbar
+
+Observed Result:
+The Editor become completely unresponsive
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386284160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhbaybf77c2fnawhs7mp,task_description,resolved
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,Verified the fix in Betalabs,1393888539,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,Cannot verify this issue for:https://bugzilla.wikimedia.org/show_bug.cgi?id=62022,1393538488,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Change 115402 merged by jenkins-bot:
+Add special case to de-indentation for slugs in listItems
+
+https://gerrit.wikimedia.org/r/115402",1393445614,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Change 115385 merged by jenkins-bot:
+Check indentation was successful before trying again
+
+https://gerrit.wikimedia.org/r/115385",1393445540,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Change 115402 had a related patch set uploaded by Esanders:
+Add special case to de-indentation for slugs in listItems
+
+https://gerrit.wikimedia.org/r/115402",1393349283,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,Above patch prevents infinite loop. Need to investigate why indentation is failing.,1393343694,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Change 115385 had a related patch set uploaded by Esanders:
+Check indentation was successful before trying again
+
+https://gerrit.wikimedia.org/r/115385",1393343480,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Also occurs (same STR) with the wikitext
+
+* {{infobox}}
+
+on testwiki.",1387191429,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Created attachment 13998
+Screenshot
+
+**Attached**: {F12233}",1386284405,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Infact it makes the browser page unresponsive.I could not close the browser window even until it showed an error to kill page in Chrome and stop script in FF.
+
+See the screenshot attached.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/unresponsive?veaction=edit
+
+In this page, Go to the last bullet and click on Bullet icon from toolbar to reproduce.",1386284358,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Infact it makes the browser page unresponsive.I could not close the browser window even until it showed an error to kill page in Chrome and stop script in FF.
+
+See the screenshot attached.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/unresponsive?veaction=edit
+
+In this page, Go to the last bullet and click on Bullet icon from toolbar to reproduce.",1386284348,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"Screenshot
+
+Button UI is missing in production for Link/Undo/Redo/Cancel formatting 
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12207}",1386277320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_description,resolved
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,Verified in Production,1386282991,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"Deployment issue fixed by touching the OOjs UI file in wmf5:
+
+https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&diff=91382&oldid=91381",1386282831,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"I am not seeing any UI of the following buttons in production:
+Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings",1386277676,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"Created attachment 13997
+Screenshot of the UI missing in More option
+
+**Attached**: {F12208}",1386277555,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/windows8?veaction=edit",1386277408,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Steps to reproduce:
+
+There are several issues in this bug.I tried to document all of them chronologically in one issue for convenience.
+
+
+1.click on the Edit button
+2.click on the bullet list icon.
+3.Click on tab to add indentation to the list for several times.
+4.Now press Enter/Return
+5.It deletes the bullets, where as pressing delete does not do that.
+6.After deleting all the bullets by pressing return it goes to the next line 
+7.Again add bulleted list with indentation on the first line
+8.Now this time if you press Enter it goes to the next line but does not add next bullet.
+9.Now go to the end of the first line and press enter, this time the next bullet gets added.
+10.Now try adding indentation to the second item , it does not work
+11.Delete the bullet and repeat the action again,this time it will add indentation.
+12.Now if you save the page , you will see there is no bullets in the read mode
+13.If you try to delete all the content by selecting with mouse pad, it gives the error:
+""Uncaught Error:Invalid start offset:-1""
+
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page where in the read mode there is no bullets but in the edit mode they appear:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/New_bullet
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386192540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h43bnjrvp2e4ey2244ee,task_description,resolved
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Looks like this was done as part of the ""handle enter"" re-write.",1395442089,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Giving steps to reproduce again:
+
+1.Open a completely new page with VE
+2.Add a text
+3.Click on Bullet list icon from the toolbar
+4.Add indentation to that line
+5.Go to the next line (Adds a second bullet)
+6.Add indentation to this second bullet line too
+7.Go back to the first bullet point and delete the text
+8.Go back to end of the second empty bullet point
+9.Press Delete(this will bring all the bullet points in one line)
+
+After this step you will get the error:Uncaught TypeError: Cannot call method 'getOffset' of null 
+
+If you press Delete again it will show error Uncaught Error: Invalid start offset: -1",1391727442,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","I can't reproduce this problem as written (Chrome here too), but there is some funkiness related to being able to split some mutli-depth bullet list items oddly.",1391662904,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Created attachment 14234
+Reproduced on 6th Jan
+
+**Attached**: {F12102}",1389030036,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Yes , I can still reproduce it.Attaching the screenshot.
+Are you getting the error:Uncaught TypeError: Cannot call method 'getOffset' of null ?",1389029763,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list",I've reproduced the steps in the video but I don't get an exception. Can you try again with the latest code.,1389028954,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Created attachment 14088
+video capture of the bug
+
+**Attached**: {F12101}",1386957303,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Steps 1-7 are as expected. I don't understand step 8, as after 7 there is only one double-indented bullet item.",1386932229,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Another way to reproduce the error ""Uncaught Error:Invalid start offset:-1""
+
+1.Open the editor
+2.Add a text 
+3.Go the next line add a bullet list with a text
+4.Add indentation to that item
+5.Press enter go to the next line then add indentation to the second empty bullet item
+6.Press enter to go to the next line
+7.It actually takes the cursor to the end of first bulleted item
+8.Press delete until all the bullets comes in the same line.
+9.The cursor then moves to the end of the first line of step 2
+10.Delete that text
+11.Now place your cursor at the end of series bullets press delete to delete it
+
+A. you will get the error:Uncaught TypeError: Cannot call method 'getOffset' of null
+
+B. If you again press delete , you will get ""Uncaught Error:Invalid start offset:-1""
+
+C. if you press undo then redo, you will get ""Uncaught Error: Unbalanced input passed to document""
+
+D. if you attempt to save the page, you will get ""Uncaught TypeError: Cannot set property 'lastOuterPost' of null""",1386373019,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"Screenshot of the error
+
+Steps to reproduce:
+
+Still Unknown.Will update once I get it.
+
+Mostly it occurred to me when I reload an open editor after an idle time or switch from Edit Source to VE it does not the editor and shows the following error:
+
+
+TypeError:Cannot read property 'Element' of undefined >TypeError
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12080}",1386178920,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atznnv7miiw6xcbyzewl,task_description,resolved
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,verified the fix in production.,1386880418,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,Verified the fix on betalabs:http://en.wikipedia.beta.wmflabs.org/,1386266416,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,One way it is always reproducible is: while creating a new page switch to Create-Beta.,1386185048,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,Somehow OO.ui becomes undefined. I have no idea why.,1386184360,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"Created attachment 13984
+Screenshot of the error
+
+**Attached**: {F12082}",1386183665,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"From VE, switched to Edit source then again switching back to VE gave this error this time and VE did not load
+
+Uncaught TypeError: Cannot read property 'Element' of undefined
+VeUiSurface
+(anonymous function)",1386183642,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"Created attachment 13983
+Screenshot of the error
+
+**Attached**: {F12081}",1386179425,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"The environment in my previous comment will be betalabs.
+
+The error occured again while creating a new page on Betalabs.
+
+ypeError: Cannot read property 'Element' of undefined TypeError {} load.php:145
+log load.php:145
+runScript load.php:154
+checkCssHandles load.php:155
+(anonymous function) load.php:155
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+addEmbeddedCSS load.php:149
+(anonymous function) load.php:149",1386179386,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit",1386179015,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+Pre-fetch VisualEditor modules to improve load speed,"First impressions count! You can make the initial experience of loading VE substantially faster by prefetching the modules on a standard article page if the DOM isn't busy.
+
+What I have in mind is something like this:
+
+    $( window ).load( function () {
+        if ( !mw.loader.store.enabled ) {
+            return;
+        }
+
+        setTimeout( function () {
+            var modules = [
+                'ext.visualEditor.base',
+                'ext.visualEditor.core'
+                'ext.visualEditor.data',
+                'ext.visualEditor.icons-vector',
+                'ext.visualEditor.mediawiki',
+                'ext.visualEditor.viewPageTarget',
+                'ext.visualEditor.viewPageTarget.icons-vector',
+            ]
+
+            mw.loader.using( modules.filter( function ( module ) {
+                var key = mw.loader.store.getModuleKey( module );
+                return key in mw.loader.store.items;
+            } ) );
+
+        }, 0 );
+    } );
+
+
+You'd need to ensure that the modules don't execute automatically somehow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1386109920,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-7xlzuxk3ore4kep2xn5u,task_description,declined
+Pre-fetch VisualEditor modules to improve load speed,"I'll challenge my own contention from 2013:
+> You can make the initial experience of loading VE substantially faster 
+
+Probably not. For all but the slowest of connections, VE load time is dominated by the cost of fetching the Parsoid DOM, building the linear model, and then building the ContentEditable DOM from the linear model. The cost of retrieving the JavaScript and CSS is negligible in comparison.
+
+This may or may not be worth doing, but in the absence of good data, there is no strong case for doing this work, so I'm closing this for now.",1442609143,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-7xlzuxk3ore4kep2xn5u,task_subcomment,NA
+Pre-fetch VisualEditor modules to improve load speed,Roan says there should be some infrastructure in RL to do this.,1422664786,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-7xlzuxk3ore4kep2xn5u,task_subcomment,NA
+Pre-fetch VisualEditor modules to improve load speed,"It's fine for them to execute automatically, nothing happens until .activate() is invoked.",1386110539,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7xlzuxk3ore4kep2xn5u,task_subcomment,NA
+VisualEditor: Paragraphs merged into image captions by backspace,"Wiktext:
+[[File:Image.jpg|thumb|Foo]]
+Bar
+
+Place the cursor the the left of 'B' and press backspace
+
+Expected: Image is focused
+Result: 'Bar' is moved into the image caption
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386086400,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-izzgctdjakrtomfnsa2n,task_description,resolved
+VisualEditor: Paragraphs merged into image captions by backspace,verified in betalabs,1386808249,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-izzgctdjakrtomfnsa2n,task_subcomment,NA
+VisualEditor: Paragraphs merged into image captions by backspace,"Change 99419 merged by jenkins-bot:
+Prevent content selections ending up inside handlesOwnChildren nodes
+
+https://gerrit.wikimedia.org/r/99419",1386266565,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-izzgctdjakrtomfnsa2n,task_subcomment,NA
+VisualEditor: Paragraphs merged into image captions by backspace,"Change 99419 had a related patch set uploaded by Esanders:
+Prevent content selections ending up inside handlesOwnChildren nodes
+
+https://gerrit.wikimedia.org/r/99419",1386261968,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-izzgctdjakrtomfnsa2n,task_subcomment,NA
+VisualEditor: Cache key is not cleared when surface is torn down,"1. Open VE on a page
+2. Make a change
+3. Go into save dialog, review diff
+4. Close save dialog without saving
+5. Click Read tab, click through warning that you'll lose your changes
+6. Click Edit tab to open VE again
+7. Make a change that's very different from #2
+8. Go into save dialog, review diff
+9. Observe that the diff displayed is for #2, not #7
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386033660,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-o2njh75t3ulqqtpvzcjc,task_description,resolved
+VisualEditor: Cache key is not cleared when surface is torn down,"Change 98752 merged by jenkins-bot:
+Clear cache key when deactivating target
+
+https://gerrit.wikimedia.org/r/98752",1386095070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o2njh75t3ulqqtpvzcjc,task_subcomment,NA
+VisualEditor: Cache key is not cleared when surface is torn down,"Change 98752 had a related patch set uploaded by Catrope:
+Clear cache key when deactivating target
+
+https://gerrit.wikimedia.org/r/98752",1386039187,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o2njh75t3ulqqtpvzcjc,task_subcomment,NA
+VisualEditor: Snowmen being created (no reproduction steps),"On fr.wp at least a couple of edits were noticed that generated snowmen:
+
+https://fr.wikipedia.org/w/index.php?title=D%C3%A9sir_mim%C3%A9tique&diff=98365348&oldid=96841726
+and https://fr.wikipedia.org/w/index.php?title=Andromaque&diff=98765089&oldid=97860409 (a vandalism).
+
+The snowman appears in the word ""français(e)"" (so it's possibly related to the ç character?).
+
+No other details available - the first editor didn't provide them, and the other was a vandal.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386018180,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-s6jclbzflvjqvzupxbrv,task_description,resolved
+VisualEditor: Snowmen being created (no reproduction steps),I believe that we fixed the last of the snowmen issues (ha!) with the re-write last week; I've not been able to reproduce these edits at all now. Provisionally marking as FIXED.,1407061838,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s6jclbzflvjqvzupxbrv,task_subcomment,NA
+VisualEditor: Snowmen being created (no reproduction steps),*** Bug 67591 has been marked as a duplicate of this bug. ***,1404767562,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s6jclbzflvjqvzupxbrv,task_subcomment,NA
+VisualEditor: Snowmen being created (no reproduction steps),"Here's another odd set of snowmen, this time at the Javanese Wikipedia.  
+
+https://jv.wikipedia.org/w/index.php?title=Igor_Stravinsky&curid=73209&diff=881366&oldid=830233
+
+The edit was inappropriate (poor English replacing Javanese) and was reverted.",1393356467,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-s6jclbzflvjqvzupxbrv,task_subcomment,NA
+VisualEditor: Snowmen being created (no reproduction steps),"About the first case, where an external link was added and a <br> tag can also be observed, User:Drongou notes that it is ""utterly incomprehensible. It's impossible to add a <br> vith VE, and VE itself does not seem to generate it. It must have come from copy/paste (snowmen are typical of failed copy/paste). Really strange, (one would rather expect a <br />): all the inclusions of <br> should be checked.""
+
+I roughly translated his words. I didn't notice that before - he's right that adding <br> by hand in VE would produce nowiki tags, which are not there.",1386020602,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-s6jclbzflvjqvzupxbrv,task_subcomment,NA
+Flow: API module issues,"For action=flow:
+* The ""flowaction"" parameter lacks a description.
+* The ""page"" parameter lacks a description.
+* The ""flowaction"" parameter does not list available actions.
+* The ""params"" parameter is poorly documented. Passing a json blob of ""params"" is rather awful. I might rather see a setup where ""flowaction"" selects a submodule, along the lines of how action=query works, so these parameters could actually be documented in api.php.
+* getExamples() should be properly implemented.
+* getHelpUrls() should be implemented.
+* I'm assuming at least some of the possible flowactions are write actions. isWriteMode() should therefore return true.
+* I note that ApiBase is already a ContextSource, so there is no need for $this->getContext()->getUser() instead of just $this->getUser().
+* I see you're setting ""_element"" directly. Use ApiResult's method to handle that instead, please. The same goes if you're setting ""*"" directly anywhere.
+* I see that sometimes the ""result"" element in the result will be an associative array and sometimes it will be the string ""error"". I'd rather see a ""status"" element of some sort that is always a string and have ""result"" always be an associative array when it is present.
+* I see you have a ""doRenderer"" protected method that is never actually called.
+
+For list=flow:
+* The link returned by getHelpUrls() does not actually document this API module.
+* The ""flowaction"" parameter does not list available actions.
+* Same criticisms of the ""params"" blob as above.
+* You are setting ""_element"" directly instead of using ApiResult's methods.
+* You should be checking the return from ApiResult's addValue method and properly handling failure.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1385566620,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_description,resolved
+Flow: API module issues,"Marking as fixed, the issues in comment 0 were fixed, and it supports autogenerated documentation.
+
+What's still missing is the on-wiki documentation, that's bug 58361.",1405325549,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to Brad Jorsch from comment #0)
+
+> For list=flow:
+> * The link returned by getHelpUrls() does not actually document this API
+> module.
+
+I had removed this earlier, but I'll make sure to add it in once the parameters are finalized.
+
+> * The ""flowaction"" parameter does not list available actions.
+
+Removed in I73347cb3b0a8cf35881691f50e70be10d10571b8 because it's pointless.
+
+> * Same criticisms of the ""params"" blob as above.
+
+After looking through all the JS that call this, they're either options to control the result format, like ""contentFormat"": ""wikitext"", or they're a post-id. I'll turn this into 2-3 more parameters to the API module directly.
+
+> * You are setting ""_element"" directly instead of using ApiResult's methods.
+
+Note to self that this needs to be fixed in all implementations of Block::renderAPI as well.
+
+> * You should be checking the return from ApiResult's addValue method and
+> properly handling failure.
+
+From the documentation, addValue will return false if the data is too big. We'll need some kind of continuation parameter...I'm not exactly sure how Flow handles that internally.
+
+https://gerrit.wikimedia.org/r/#/q/project:mediawiki/extensions/Flow+topic:flow-api,n,z",1396424928,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"action=flow looks much better!
+
+list=flow still needs work though, so reopening.",1396015870,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"Change 107411 merged by jenkins-bot:
+API: Revamp action=flow
+
+https://gerrit.wikimedia.org/r/107411",1396001572,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"This bug is marked as ""PATCH_TO_REVIEW"", but the patch in question is marked as work in progress (""[WIP]"").  For clarity, I'm moving this back out to ""assigned"", since I understand that Kunal is working on it.",1393010611,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"> (In reply to comment #21)
+Alex Z., what do you and others want from a Flow API?  How can we best collaborate on it?  A Flow board makes API requests for all in-page updates, so Flow heavily exercises its API while we implement Brad Jorsch's feedback, but I'm concerned about what we overlook. I filed bug 60808 and bug 60809, but I'm just guessing.
+
+Erik Bernhardson posted https://en.wikipedia.org/wiki/Wikipedia:Bot_owners%27_noticeboard#New_extension:_Flow , so that's another venue. I mentioned these bugs there.
+
+I've created https://www.mediawiki.org/wiki/Flow/Architecture/API with links to these, and empty sections awaiting use cases. I'll try to keep it updated.
+
+Thanks everyone.",1391493384,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #21)
+> So, to expand: I fully believe that the community should be factored into the
+> decision-making process, directly and indirectly - but factored in is very
+> different from being a trump card. If the argument is ""there will be people
+> who
+> look at the API and think it's Us Doing The VisualEditor All Over Again"",
+
+I'm looking at this and thinking, ""Oh, no, it's them doing WikiEditor all over again,"" where a product is deployed to wikis before the API is properly documented or becomes stable, and bot/script developers practically have to reverse engineer it in order to update all of their code in time.
+
+I mean, you're at the point of field testing it in production, but there apparently isn't even a specification for how the real API will work, let alone a place where the people who will be using it might actually be able to make some input.",1391486589,PHID-USER-xab2aohgotczcynszcm2,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #24)
+> (In reply to comment #23)
+> > Easily. Just include the necessary text in the string returned from the
+> > module's getDescription() method.
+> 
+> Sorry, more meant ""Can the team please do this soon, or say why not?"" :)
+
+https://gerrit.wikimedia.org/r/#/c/110967/ should address that.",1391449078,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #23)
+> Easily. Just include the necessary text in the string returned from the
+> module's getDescription() method.
+
+Sorry, more meant ""Can the team please do this soon, or say why not?"" :)",1391211062,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #22)
+> So, back on topic...
+> 
+> From Brian on bug 60178 comment 28:
+> ""I would think the appropriate thing to do (If we must do this) is to
+> include a
+> note in the auto-generated api documentation.""
+> 
+> Can this be done
+
+Easily. Just include the necessary text in the string returned from the module's getDescription() method.",1391207891,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"So, back on topic...
+
+From Brian on bug 60178 comment 28:
+""I would think the appropriate thing to do (If we must do this) is to include a note in the auto-generated api documentation.""
+
+Can this be done, or explain why not? I still think a note to BAG or similar is good in addition, personally.",1391203609,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #19)
+> (In reply to comment #9)
+> 
+> > Possibly. There are some community members who would find a way to take
+> > offence to ""how is your day going?"". I don't particularly think we should base
+> > our decisions around pandering to them.
+> 
+> This is unacceptable attitude, Oliver. You in particular should know better
+> than that.
+
+Sorry, I should be clearer; the 'them' is 'the sort of people who would find a way to take offence...'
+
+So, to expand: I fully believe that the community should be factored into the decision-making process, directly and indirectly - but factored in is very different from being a trump card. If the argument is ""there will be people who look at the API and think it's Us Doing The VisualEditor All Over Again"", that's a bad argument, and the sort of people who would jump from 'the minimum viable product is not perfect' to 'everything is going to be terrible forever' are not people I am particularly interested in basing our decisions on, because anyone who _makes_ that cognitive leap is clearly not approaching things rationally, and so it becomes very hard to actually compromise with them - if compromising with them is actually worthwhile in the first place.",1391199755,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #13)
+> Personally I find impersonal communication methods like bugzilla a passive
+> aggressive way to air issues without actually talking to anyone directly.
+
+I'm severely confused. After reading comment 0 out of the blue, I expected comment 1 to start like this: ""Great Brad, thanks for your thorough review of our API module! It's very useful when someone helps us learn more about/do better with some specialised areas of the code rather than let us alone hitting against a wall"". And then a conversation to clarify the various actionable items and to log them properly in atomic bugs or cards.",1391199542,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #9)
+
+> Possibly. There are some community members who would find a way to take
+> offence to ""how is your day going?"". I don't particularly think we should base
+> our decisions around pandering to them.
+
+This is unacceptable attitude, Oliver. You in particular should know better than that.",1391197935,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(Off-topic, like the rest of the last 6 or so comments, but, I wanted to publicly say: Sorry for my tone. We'll work together on addressing this bug.)",1391192912,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #15)
+> (In reply to comment #14)
+> > Bugzilla is how one files bugs against a product--sorry you don't like it.
+> > The
+> > nice thing is it's asynchronous so if someone is in a different timezone they
+> > can easily report issues without waiting for you to be around :)
+> 
+> Bugzilla is an excellent way to track bugs, but for solving problems nothing
+> beats communicating with a human being in real time.  The foundation uses
+> real
+> time communication within teams extensively to organize and ensure the work
+> they want to get done happens.  Embrace the most effective forms of
+> communication you can.
+> 
+> Lucky for those in other timezones, we have team members in 2 american
+> timezones, europe and australia.
+
+The point is simply: there was a bug report by a respected member of the platform team (whether or not you knew he was the point person for the API); please respond to bug reports. People are busy and reviewing a lot of people's code and can't be on point to track everyone down all the time (seriously, if Platform had to do that, we'd never get anything else done).
+
+Please take some initiative and review your bugzilla tickets and ask for clarification where needed.",1390931011,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #15)
+> (In reply to comment #14)
+> > Bugzilla is how one files bugs against a product--sorry you don't like it.
+> > The
+> > nice thing is it's asynchronous so if someone is in a different timezone they
+> > can easily report issues without waiting for you to be around :)
+> 
+> Bugzilla is an excellent way to track bugs, but for solving problems nothing
+> beats communicating with a human being in real time.
+
+Indeed. But it's also good to file bugs because people are imperfect and can forget conversations they have :)
+
+> The foundation uses
+> real
+> time communication within teams extensively to organize and ensure the work
+> they want to get done happens.  Embrace the most effective forms of
+> communication you can.
+> 
+
+I know how the Foundation works...I work here too ;-)
+
+Is real time communication awesome? Sure. Is finding someone on IRC to chat about your problem sometimes faster than a bug? Absolutely.
+
+But you said:
+
+(In reply to comment #13)
+> Personally I find impersonal communication methods like bugzilla a passive
+> aggressive way to air issues without actually talking to anyone directly.  If
+> you had come into our irc room months ago and xommunicated in real time I
+> guarantee this bug would be in a different state.
+
+Regardless of your personal opinions about Bugzilla, it's where we file bugs about
+our software--all of it. It's completely reasonable to expect people to file bugs here, and they should be treated with just as much interest and care as things tracked in Mingle, Trello, or reported to the IRC ether.",1390930989,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #14)
+> Bugzilla is how one files bugs against a product--sorry you don't like it.
+> The
+> nice thing is it's asynchronous so if someone is in a different timezone they
+> can easily report issues without waiting for you to be around :)
+
+Bugzilla is an excellent way to track bugs, but for solving problems nothing beats communicating with a human being in real time.  The foundation uses real time communication within teams extensively to organize and ensure the work they want to get done happens.  Embrace the most effective forms of communication you can.
+
+Lucky for those in other timezones, we have team members in 2 american timezones, europe and australia.",1390930483,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #13)
+> (In reply to comment #12)
+> > (In reply to comment #10)
+> > > (In reply to comment #7)
+> > > > In the future, let's not rely on passive Bugzilla communication
+> > > > around things you feel are serious blockers; let's just talk to each other
+> > > > directly
+> > > 
+> > > In that case please document outcome as a comment in Bugzilla, so community
+> > > members can also be aware and provide input if they were not physically
+> > > around
+> > > in your office.
+> > 
+> > Personally, I find bugzilla works as well as email and IRC doesn't seem like
+> > it
+> > would have been that much of an improvement here.
+> > 
+> > No one besides me is around my office. ;)
+> 
+> Personally I find impersonal communication methods like bugzilla a passive
+> aggressive way to air issues without actually talking to anyone directly.  If
+> you had come into our irc room months ago and xommunicated in real time I
+> guarantee this bug would be in a different state.
+
+Bugzilla is how one files bugs against a product--sorry you don't like it. The nice thing is it's asynchronous so if someone is in a different timezone they can easily report issues without waiting for you to be around :)",1390929404,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #12)
+> (In reply to comment #10)
+> > (In reply to comment #7)
+> > > In the future, let's not rely on passive Bugzilla communication
+> > > around things you feel are serious blockers; let's just talk to each other
+> > > directly
+> > 
+> > In that case please document outcome as a comment in Bugzilla, so community
+> > members can also be aware and provide input if they were not physically
+> > around
+> > in your office.
+> 
+> Personally, I find bugzilla works as well as email and IRC doesn't seem like
+> it
+> would have been that much of an improvement here.
+> 
+> No one besides me is around my office. ;)
+
+Personally I find impersonal communication methods like bugzilla a passive aggressive way to air issues without actually talking to anyone directly.  If you had come into our irc room months ago and xommunicated in real time I guarantee this bug would be in a different state.",1390927052,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #10)
+> (In reply to comment #7)
+> > In the future, let's not rely on passive Bugzilla communication
+> > around things you feel are serious blockers; let's just talk to each other
+> > directly
+> 
+> In that case please document outcome as a comment in Bugzilla, so community
+> members can also be aware and provide input if they were not physically
+> around
+> in your office.
+
+Personally, I find bugzilla works as well as email and IRC doesn't seem like it would have been that much of an improvement here.
+
+No one besides me is around my office. ;)",1390862653,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #10)
+> (In reply to comment #7)
+> > In the future, let's not rely on passive Bugzilla communication
+> > around things you feel are serious blockers; let's just talk to each other
+> > directly
+> 
+> In that case please document outcome as a comment in Bugzilla, so community
+> members can also be aware and provide input if they were not physically
+> around
+> in your office.
+
+I think that's what Maryana just said she'd do. Indeed, it's what she just did :).",1390859479,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #7)
+> In the future, let's not rely on passive Bugzilla communication
+> around things you feel are serious blockers; let's just talk to each other
+> directly
+
+In that case please document outcome as a comment in Bugzilla, so community members can also be aware and provide input if they were not physically around in your office.",1390858246,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #8)
+> (In reply to comment #7)
+> > Putting Flow out there on a couple of real discussion spaces
+> > is
+> > the only way we're going to be able to get actionable feedback on the design
+> > and UI side. The sooner we start receiving this kind of feedback, the sooner
+> > we
+> > can prioritize our work on all the outstanding bugs, enhancements and feature
+> > requests, so we get the right features to the right users at the right time.
+> 
+> That sounds like the same reasoning they used when deploying VE to enwiki
+> with
+> known bugs unfixed. I think we all know how well *that* went.
+> 
+> I realize the proposed deployment of Flow to enwiki is somewhat different
+> since
+> it's a deployment to two rather out-of-the-way talk pages rather than being
+> enabled by default for everyone. But on the other hand, it's also that much
+> less likely to give you the sort of feedback you're hoping for. And certain
+> vocal community members will be on the defensive given the recent VE
+> situation,
+> ready to blast ""the WMF"" for doing the ""same"" thing again.
+> 
+Possibly. There are some community members who would find a way to take offence to ""how is your day going?"". I don't particularly think we should base our decisions around pandering to them.
+> 
+> (In reply to comment #7)
+> > I understand that your priorities as a platform engineer fall toward making
+> > sure our API is robust and well-documented.
+> 
+> I also want to avoid causing our volunteer community members to develop
+> towards
+> an API with known major flaws by pushing it on a production site before it's
+> ready. The test wikis and mediawiki.org, while in production, are still test
+> sites.",1390857650,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #7)
+> Putting Flow out there on a couple of real discussion spaces
+> is
+> the only way we're going to be able to get actionable feedback on the design
+> and UI side. The sooner we start receiving this kind of feedback, the sooner
+> we
+> can prioritize our work on all the outstanding bugs, enhancements and feature
+> requests, so we get the right features to the right users at the right time.
+
+That sounds like the same reasoning they used when deploying VE to enwiki with known bugs unfixed. I think we all know how well *that* went.
+
+I realize the proposed deployment of Flow to enwiki is somewhat different since it's a deployment to two rather out-of-the-way talk pages rather than being enabled by default for everyone. But on the other hand, it's also that much less likely to give you the sort of feedback you're hoping for. And certain vocal community members will be on the defensive given the recent VE situation, ready to blast ""the WMF"" for doing the ""same"" thing again.
+
+
+(In reply to comment #7)
+> I understand that your priorities as a platform engineer fall toward making
+> sure our API is robust and well-documented.
+
+I also want to avoid causing our volunteer community members to develop towards an API with known major flaws by pushing it on a production site before it's ready. The test wikis and mediawiki.org, while in production, are still test sites.",1390855001,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"Brad,
+
+We've chosen our first deployment to English Wikipedia with care. The reason Flow is only going live on the 2 discussion pages in question (Wikipedia_talk:Wikiproject_Breakfast and Wikipedia_talk:Wikiproject_Hampshire) is that those pages have zero bot activity, and relatively light human traffic, for that matter, skewing largely power user (e.g. no clueless n00bs who need to get smacked around by Cluebot). In my capacity as product owner, I felt completely comfortable deploying a beta trial of experimental software with an incomplete API to two pages where an API wouldn't be critically necessary for vital workflows, with the understanding that the next step after this deployment would be to reach out to bot operators, invite them to test aggressively on a developer test page, and work with them to make the API fulfill their needs. I apologize for not communicating all of this to you explicitly sooner; frankly, it was hard for me to ascertain whether this particular bug was more or less high-priority than your critiques of our use of whitespace. In the future, let's not rely on passive Bugzilla communication around things you feel are serious blockers; let's just talk to each other directly -- I don't bite :)
+
+I understand that your priorities as a platform engineer fall toward making sure our API is robust and well-documented. But please keep in mind that this project also involves significant design and UI components that are just as critical to the success of the overall mission (to replace talk pages entirely and create more universally-usable, stable software tools for all the processes they support). Putting Flow out there on a couple of real discussion spaces is the only way we're going to be able to get actionable feedback on the design and UI side. The sooner we start receiving this kind of feedback, the sooner we can prioritize our work on all the outstanding bugs, enhancements and feature requests, so we get the right features to the right users at the right time.",1390852535,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"Change 107411 had a related patch set uploaded by Legoktm:
+[WIP] Revamp API
+
+https://gerrit.wikimedia.org/r/107411",1390799392,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,Flow team: This was reported in November with pretty clear concerns. Brad is the current point of reason/arbitration for the API. Can you give a response to this as well? (On BZ not Mingle ;) ).,1390799329,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #3)
+> (In reply to comment #0)
+> > * The link returned by getHelpUrls() does not actually document this API
+> > module.
+> 
+> Removed in https://gerrit.wikimedia.org/r/#/c/102030/
+
+Good to get rid of the bad link. But list=flow does need a valid implementation of getHelpUrls(). I expect you already are aware of this, but the obvious bears stating.",1387292443,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #0)
+> * I note that ApiBase is already a ContextSource, so there is no need for
+> $this->getContext()->getUser() instead of just $this->getUser().
+
+https://gerrit.wikimedia.org/r/#/c/102046/
+
+> * The link returned by getHelpUrls() does not actually document this API
+> module.
+
+Removed in https://gerrit.wikimedia.org/r/#/c/102030/",1387240689,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"Marking as high priority, it gets much harder to change the API once something is deployed...",1386807456,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"**bingle-admin** wrote:
+
+The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/532, but people from the community are welcome to contribute here and in Gerrit.",1385566935,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,"Steps to reproduce:
+* Click on an image before a text node. The image will be marked as selected.
+* Press rightarrow to cursor next to the text.
+* Start typing. The text will be inserted backwards.
+
+Cause:
+After cursoring off the image, the selection is in the text node (and the cursor is flashing), but the focus is not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54917",1385483520,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-vxauebeaoyvfqdythyzt,task_description,resolved
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,"Change 97750 merged by jenkins-bot:
+Fix moving over an image with the arrow keys in Firefox
+
+https://gerrit.wikimedia.org/r/97750",1385495488,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vxauebeaoyvfqdythyzt,task_subcomment,NA
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,"Change 97750 had a related patch set uploaded by Catrope:
+Fix moving over an image with the arrow keys in Firefox
+
+https://gerrit.wikimedia.org/r/97750",1385485733,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vxauebeaoyvfqdythyzt,task_subcomment,NA
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,*** Bug 57347 has been marked as a duplicate of this bug. ***,1385484604,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vxauebeaoyvfqdythyzt,task_subcomment,NA
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,"Change 97750 had a related patch set uploaded by Divec:
+Fix post-image selection bug
+
+https://gerrit.wikimedia.org/r/97750",1385483662,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vxauebeaoyvfqdythyzt,task_subcomment,NA
+VisualEditor: Annotate body tag or #content tag when in edit mode with class,"Other modules (and gadgets) should be able to hide their interfaces when VisualEditor is opened - for example the Nearby pages BetaFeature (https://www.mediawiki.org/wiki/Beta_Features/Nearby_Pages) creates a blue button in the top right.
+
+Ideally this feature should be able to know when it is in edit mode and hide itself.
+
+Maybe abusing the action-edit / action-view classes would be useful here?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385409780,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ralatlcjdkp2pb5sjaiy,task_description,resolved
+VisualEditor: Annotate body tag or #content tag when in edit mode with class,"Change 97702 merged by jenkins-bot:
+mw.ViewPageTarget: Use ve-activated class on the html element
+
+https://gerrit.wikimedia.org/r/97702",1385506336,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ralatlcjdkp2pb5sjaiy,task_subcomment,NA
+VisualEditor: Annotate body tag or #content tag when in edit mode with class,"Change 97702 had a related patch set uploaded by Robmoen:
+Toggle veaction-edit class on the body of the view page
+
+https://gerrit.wikimedia.org/r/97702",1385460063,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ralatlcjdkp2pb5sjaiy,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"Screenshot
+
+Steps to reproduce:
+
+1.Click on the Edit button in a page
+2.Select a text by dragging with mouse control.
+3.Change the heading format of the text to any format for example:heading/paragraph etc.
+
+Observed Result:
+The cursor moves to a position which is the middle of the first and second line of the page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58998
+
+**Attached**: {F12046}",1385407560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_description,resolved
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,*** Bug 60139 has been marked as a duplicate of this bug. ***,1394659271,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27thfebchrome&veaction=edit,1393533723,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"Change 115759 merged by jenkins-bot:
+Restore focus after node-destroying actions
+
+https://gerrit.wikimedia.org/r/115759",1393452937,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"Change 115759 had a related patch set uploaded by Esanders:
+Restore focus after node-destroying actions
+
+https://gerrit.wikimedia.org/r/115759",1393452124,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"This issue is still happening however I am changing the steps and observed result as follows:
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select any text with keyboard/mouse control/double click
+3.Change the heading format of the section to any format, for example:Preformatted/Sub-heading 1 etc.
+
+Observed Result:
+The cursor jumps to the beginning of the page.Now Type something on the first line or apply a format on the first line say ""Page title"", it actually adds the text in the text position of step 2 replacing replacing its previous content and style.",1393364053,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/ref_not_editable?veaction=edit",1385407634,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: MWExtensionInspector does not take directionality from context when creating,"https://gerrit.wikimedia.org/r/#/c/96984/ adds a workaround for the fact that getting the directionality from the FocusedNode doesn't work if there is no node focused (i.e. in creation mode), but it doesn't add any alternative logic for getting the directionality. We should look at the context in the CE tree somehow and figure out what directionality to use. Right now it just defaults to the UI directionality.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385125260,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-aljnlx2ibmppm5ov7vo7,task_description,resolved
+VisualEditor: MWExtensionInspector does not take directionality from context when creating,"Change 101125 merged by jenkins-bot:
+Add a getDirectionFromRange Method to ve.ce.Document
+
+https://gerrit.wikimedia.org/r/101125",1386966265,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aljnlx2ibmppm5ov7vo7,task_subcomment,NA
+VisualEditor: MWExtensionInspector does not take directionality from context when creating,"Change 101125 had a related patch set uploaded by Mooeypoo:
+Add a getDirectionFromRange Method to ve.ce.Document
+
+https://gerrit.wikimedia.org/r/101125",1386886808,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aljnlx2ibmppm5ov7vo7,task_subcomment,NA
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,"At the end of the first paragraph there is reference #1.
+If you scroll to the reference list, it will look empty.
+
+Actually, the reference, which can be edited, contains an unnamed link. 
+The markup guide for en.wp says these links are ""Only used within article body
+for footnotes"", so it makes sense that VE should display them correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Elitre_%28WMF%29/sandbox&veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57419",1385124180,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-j3t4kswoyrigddha43ep,task_description,resolved
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,"Change 97037 merged by jenkins-bot:
+Also apply autonumbering CSS to links in generated content
+
+https://gerrit.wikimedia.org/r/97037",1385496806,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j3t4kswoyrigddha43ep,task_subcomment,NA
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,*** Bug 57209 has been marked as a duplicate of this bug. ***,1385374223,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j3t4kswoyrigddha43ep,task_subcomment,NA
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,"This happened because the numbered link was generated by a template (indirectly in this case: it was in the references list which was in turn generated by {{reflist}}), and the CSS we use to do the numbering didn't account for numbered links in templates.",1385140816,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-j3t4kswoyrigddha43ep,task_subcomment,NA
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,"Change 97037 had a related patch set uploaded by Catrope:
+Also apply autonumbering CSS to links in generated content
+
+https://gerrit.wikimedia.org/r/97037",1385140090,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j3t4kswoyrigddha43ep,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,"**Author:** `swalling`
+
+**Description:**
+Screenshot from mediawiki.org
+
+The box that appears on hover around dropdown menu items overlaps with the text for the ""Switch to source editor"" option. (See attachment)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12471}",1385060520,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-t37b6rskig2gygqauzqe,task_description,resolved
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,Verified the fix in Production,1410545528,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 69707 has been marked as a duplicate of this bug. ***,1409892989,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,Verified the fix in Betalabs and test2,1409876520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,This bug got fixed with this change commit:https://gerrit.wikimedia.org/r/#/c/157295/,1409876443,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 70316 has been marked as a duplicate of this bug. ***,1409767558,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,"Created attachment 16280
+Screenshot of problem on master.
+
+It's worse now that the ""Cancel"" button is gone. The menu is even narrower now and more items are cut off. And the ""Switch to source text"" item is now actually cropped instead of just partially hanging outside the container.
+
+**Attached**: {F12472}",1409072441,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 69808 has been marked as a duplicate of this bug. ***,1408570728,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,"I believe this blocks bug 67340 (or at least, this being fixed would be useful there).",1406763651,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,@Krinkle: Ping. Any progress on this?,1406671445,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,Bumping priority now that the loss of the Cancel button makes this more acute.,1406320862,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 68483 has been marked as a duplicate of this bug. ***,1406156548,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 61149 has been marked as a duplicate of this bug. ***,1401743910,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,Merging in bug 61149 to this.,1401743896,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,"**Author:** `Wikifram`
+
+**Description:**
+There are a number of bugs about pawns and/or reverse typing, many of them ""resolved fixed"". But it is clear that in many circumstances, on different wikiversions, pawn characters and reverse typing still occur. 
+
+See [[en:Wikipedia:VisualEditor/Feedback#Line with template, pawn]] (and the linked sections on fr-wiki as well) for an explanation of some scenarios when this occurs. This has, in various guises, been reported since the first deployment of VE, and none of the fixes seem to have been permanent or fundamental. Can this please be tackled?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1385030100,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-q5yeocuc7uzle4efdhw5,task_description,resolved
+VisualEditor: Pawning and reversed typing in Firefox,"Re-merged with bug 57600, as slightly distinct from bug 54917.
+
+*** This bug has been marked as a duplicate of bug 57600 ***",1385484604,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,"Merging into bug 54917 which is the same, yes.
+
+*** This bug has been marked as a duplicate of bug 54917 ***",1385472098,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,Possibly a dupe of https://bugzilla.wikimedia.org/show_bug.cgi?id=54917?,1385194254,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,"The above was related to templates (that is, a weird behavior when templates are selected and then deselected via keyboard arrows). The opposite happens when dealing with references.
+
+1. https://en.wikipedia.org/wiki/Selan_%28Dungeons_%26_Dragons%29?veaction=edit
+2. Put your cursor right after the first reference number ([1]).
+3. Arrow left.
+4. Arrow left.
+5. Start typing.
+
+You are typing backwards.
+
+Also:
+
+1. and 2. as above.
+3. Arrow left.
+4. Arrow right.
+5. Start typing.
+
+A pawn appears.",1385046939,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,"In short (and partially reusing Fram's words).
+This happens in FF, in both MB and Vector.
+
+1. VEdit https://en.wikipedia.org/wiki/Selan_(Dungeons_%26_Dragons) .
+2. Put your cursor at the start of the text (i.e. before ""In the..."").
+3. Arrow left.
+4. Arrow left.
+5. Start typing.
+
+A pawn appears. 
+
+Also:
+
+1. and 2. as above.
+3. Arrow left.
+4. Arrow right (nothing happens; a bug in its own right?)
+5. Arrow right.
+6. Start typing.
+
+You are typing backwards.",1385046376,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Change event reaction order,"The current event reaction order means that many IMEs including jQuery.IME and a number of Windows built-in input methods don't work in VE; we should change it to something that does – needs investigation as to what order is right.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1384939680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pdqwezif4yyehpz3pomy,task_description,resolved
+VisualEditor: Change event reaction order,"IME support has improved markedly due to incrementally revamped event logic. Significant milestones included:
+
+https://gerrit.wikimedia.org/r/86688 - Selection change debounce
+https://gerrit.wikimedia.org/r/91786 - Fixup selection after rerender
+https://gerrit.wikimedia.org/r/105231 - Reduce refreshes
+https://gerrit.wikimedia.org/r/125937 - Unicorns
+https://gerrit.wikimedia.org/r/166188 - Poll refactor
+https://gerrit.wikimedia.org/r/179530 - Stable selections
+https://gerrit.wikimedia.org/r/177946 - Native left/rightarrow
+
+The basic way VE handles events is probably right now, given all the constraints of the browser environment and all the features of unicode/individual scripts that must be supported. Any unresolved dependent bugs can now be given a more specific diagnosis :-)",1424368837,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-pdqwezif4yyehpz3pomy,task_subcomment,NA
+VisualEditor: [Regression] References created in media item captions no longer appear in reference lists,"Regression of bug 52427.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384844400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vcjosxhcqmpzxbjafscg,task_description,resolved
+VisualEditor: [Regression] References created in media item captions no longer appear in reference lists,Looks like this got fixed at some point because it works for me.,1413925579,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vcjosxhcqmpzxbjafscg,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"Intention:
+Copyedit a page
+
+Steps to Reproduce:
+1. Open a page with pre-existing content.
+2. Type or change some of the text (I was adding a new first line).
+3. Select and cut (⌘ Command+x) some pre-existing text (I cut mine from the end of the third line).
+4. Notice that what you typed on the first line has been undone.
+5. Paste what you cut (in my case, at the end of the first line).
+6. Notice that what you typed on the first line has been redone.
+
+
+
+Expected Results:  
+That text would not magically disappear and reappear.
+
+Reproducible: Always
+
+I experienced this on office.wikipedia.org using Safari 6 on Mac OS 10.7.5.  It was confirmed at en.wikipedia.org using Vector/Chrome 30/Windows 7, with the additional discoveries that:
+
+If you type your new first line all in one go (so that 'undo' would remove the whole first line), the first character of the new line remains present.
+
+The undone text only reappears if you paste your cut text onto the line with the now-missing text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58724",1384818060,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-b5q6raassymzwkebamu6,task_description,resolved
+VisualEditor:  Cutting text undoes previous typing,Fixed at the same time as bug 58724.,1409345286,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"My computer is brand new, no custom shortcuts. Maybe VE is using a keyboard shortcut hack to make undo possible.",1408644567,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"Whether it's impossible or not, it happens every time I use Command-X in Safari after closing a tab.  It only happens if ""Undo closed tab"" is listed in Safari's Edit menu as the action for undo/Command-Z.  It's bug 58724.",1408639497,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"(In reply to Mc128k from comment #1)
+> I have a similar issue that makes Safari reopen a closed tab, same with
+> cmd-x.
+> It doesn't happen immediately and in all cases though.
+
+I'm pretty sure it's impossible for VisualEditor to cause a browser to re-open a tab; you probably have a keyboard mapping clash or something similar?",1408637240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"I have a similar issue that makes Safari reopen a closed tab, same with cmd-x.
+It doesn't happen immediately and in all cases though.",1408613391,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor: First character added to a blank dialog entry box (reference or caption) is mis-placed and never makes it into DM in Firefox,"With Vector in FF.
+Try to add a caption to an image:
+the words will be splitted on multiple lines, with the first letter being automatically placed on the second line, the other letters on the first one, and no ability to fix this.
+
+I understand that https://bugzilla.wikimedia.org/show_bug.cgi?id=38129 is coming but I thought I'd file this anyway.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384811940,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-56jj32rdepjfe2dxapzo,task_description,resolved
+VisualEditor: First character added to a blank dialog entry box (reference or caption) is mis-placed and never makes it into DM in Firefox,"This was fixed last week as part of our fix-up of how windows works, happily (or, at least, I think so – I can replicate on enwiki but not on MediaWiki.org).",1384923911,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-56jj32rdepjfe2dxapzo,task_subcomment,NA
+VisualEditor: First character added to a blank dialog entry box (reference or caption) is mis-placed and never makes it into DM in Firefox,It is.,1384815472,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-56jj32rdepjfe2dxapzo,task_subcomment,NA
+VisualEditor: First character added to a blank dialog entry box (reference or caption) is mis-placed and never makes it into DM in Firefox,"This is probably specific to Firefox.  I'm able to replicate this in Firefox 25 on a Mac, but not Safari 6.",1384815007,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-56jj32rdepjfe2dxapzo,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,"On desktop, as soon as the visual editor is loaded, the cursor is activated at the beginning of the page content. This doesn't happen in the mobile version.
+
+Clicking on the page content after the editor has loaded then has inconsistent behavior between browsers. In Firefox, clicking anywhere in the page content inserts the cursor at the beginning of the content. In Webkit browsers, it inserts the cursor at the click location.
+
+I believe that fixing the first problem will also fix the second problem in for free.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67389
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67390
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67399",1384765200,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-zcneabl26r5jk4uera2i,task_description,invalid
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,According to Juliusz this is on purpose as tablets require an actual tap to activate the virtual keyboard.,1405637552,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,"This is caused by code in MF, line 152 of VisualEditorOverlay.js:
+
+// for some reason the first time contenteditables are focused, focus
+// event doesn't fire if we don't blur them first
+this.$( '[contenteditable]' ).blur();
+
+The code was added to fix bug 61240.",1405200891,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,"(In reply to Ryan Kaldari from comment #2)
+> We would like to have this fixed before we push mobile VE to stable if
+> possible. Any update on it?
+
+… no? Bugs in VE/Mobile have been awaiting triage and action by the Mobile since this was agreed in 2012. We can have a look at it now, though.",1403728238,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,We would like to have this fixed before we push mobile VE to stable if possible. Any update on it?,1403728165,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,This is in reference to Rob's prototype mobile visual editor. https://gerrit.wikimedia.org/r/#/c/93916/,1384842065,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+Allow links in Flow topic titles,"When a topic title includes an internal link, the title should render as a working link in the topic header.
+
+This will use the edit summary parser.
+
+Examples: 
+The topic title is [[Foo]] -- it will render as Foo -- a link to the article page Foo.
+The topic title is [[Foo|Bar]] -- it will render as Bar -- a link to the article page Foo.
+~~The topic title is [http://foo.com Foo] -- it will render as Foo -- an external link to foo.com.~~ (We decided to use the edit summary parser, which does not support this.)
+
+NOTE #1: For posts, replies and edits to a post/reply -- in watchlist, recent changes and contributions, there will be a blue link that says Foo -- but this will NOT be a link to the article page Foo. It will be a link to the Topic:UUID. See screenshots below. 
+
+NOTE #2: In topic history, board history, watchlist, recent changes and contributions, when there is a change to the topic summary, or moderation actions, the topic title will be rendered as Foo, no link. 
+For example: created topic summary on Foo
+
+**Topic heading -- this should be a working link**
+{F250640}
+
+**Contributions** -- 
+For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+For editing the topic summary, the link should render as the title, not linked.
+
+{F250665}
+
+**Recent changes** --
+For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+For editing the topic summary, the link should render as the title, not linked.
+
+{F250670}
+
+**Watchlist** --
+For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+For editing the topic summary, the link should render as the title, not linked.
+
+{F250675}
+
+{F250677}
+
+**Board and Topic history** --
+For both post/reply/edit and editing the topic summary, the link should render as the title, not linked.
+
+{F250682}
+
+{F250686}
+
+See {T115910}.
+
+---
+
+previous version of the ticket: 
+
+Flow: Wikitext formatting (such as [[links]] and ''italics'') doesn't work in topic titles
+
+When you create a new Flow thread, there's a ""topic"" field. This topic field is analogous to the ""subject"" field in a wikitext talk page. The topic field currently cannot support wikitext.
+
+Example: http://ee-flow.wmflabs.org/w/index.php?title=Sandbox&workflow=0509a3b2518b34dffb6efa163e68c4ac&action=view
+
+Topic input: ""here's a new [[topic]]""
+
+Expected behavior: ""[[topic]]"" becomes an internal hyperlink
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: http://ee-flow.wmflabs.org/w/index.php?title=Sandbox&workflow=0509a3b2518b34dffb6efa163e68c4ac&action=view
+**See Also**:
+* {T23445}
+* {T59950}
+* Tech News posts to LQT pages converted to Flow: https://www.mediawiki.org/wiki/Topic:Siez4a3hsji86cay
+
+https://trello.com/c/bj3IZSE5/190-limited-wikitext-formatting-in-topic-titles",1384740180,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_description,resolved
+Allow links in Flow topic titles,">>! In T59153#1822120, @Etonkovidova wrote:
+> 4)
+>>Watchlist --
+>> For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+>> For editing the topic summary, the link should render as the title, not linked.
+> 
+> {F2993084}
+
+That looks like a bug: those brackets should not appear. I've filed {T120329} for this, so we can close this bug.",1449191233,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(This will be announced in Tech News the week after next, as there's no MediaWiki deployment next week.)",1448451190,PHID-USER-go2ym6ta2zn6ofdsrqnx,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Filed as a separate issue {T119537}
+
+- Have a title with a link in it
+- scroll up - the link exposes html code: 
+{F2993105}",1448388712,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Not sure if it's big enough to be in a separate issue: 
+
+- Have a title with a link in it
+- scroll up - the link exposes html code: 
+{F2993105}",1448062036,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Checked in betalabs according to specs. Please check below
+Talk:ET19 - the link in the title and in the Summary - [[Talk:ET1|ET1]] 
+1)
+> Topic heading -- this should be a working link
+ 
+{F2992994}
+
+2) The links to the topic ET1 are rendered as for the Recent changes - see below
+> Contributions -
+> For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+> For editing the topic summary, the link should render as the title, not linked.
+
+{F2993008}
+
+3) 
+>Recent changes --
+>For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+>For editing the topic summary, the link should render as the title, not linked.
+
+{F2993045}
+
+4)
+>Watchlist --
+> For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+> For editing the topic summary, the link should render as the title, not linked.
+
+{F2993084}
+
+5)  Links are in the right place - checked.
+>Board and Topic history --
+> For both post/reply/edit and editing the topic summary, the link should render as the title, not linked.
+
+{F2993093}",1448061939,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Change 243066 merged by jenkins-bot:
+Add support for edit summary formatting in topic titles
+
+[[https://gerrit.wikimedia.org/r/243066]]",1447893298,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,See {T115910}.,1445280425,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Change 243066 had a related patch set uploaded (by Mattflaschen):
+WIP: Add support for edit summary formatting in topic titles
+
+[[https://gerrit.wikimedia.org/r/243066]]
+",1443744293,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,">>! In T59153#1439920, @Mattflaschen wrote:
+> We discussed the possibility of using the same subset the edit summary parser allows.
+
+That would be the least. You've already broken many topic titles:
+https://www.mediawiki.org/wiki/Talk:MediaWiki_Stakeholders%27_Group",1436983178,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,We discussed the possibility of using the same subset the edit summary parser allows.,1436403629,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"@DannyH https://trello.com/c/bj3IZSE5/190-limited-wikitext-formatting-in-topic-titles
+> We shouldn't do wikitext in topic titles -- titles will be used in log pages like contributions, watchlist, etc.
+Many wikis use titles with wikitext ""==[[PageInTitle]]==""  and special log pages showing simply ""PageInTitle"" and links [[ SomePage#PageInTitle ]] work fine. Why this can not further work so?
+
+",1434636335,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,Well it's very cool that at least one users and also users of languages who don't use formatting at all would survive. But as there are still lots of users who are not covered by that array I'd rather have wikimarkup allowed in there. We are not to force people to change their talk page editing style or even make them drop some features their language allows...,1431762837,PHID-USER-sscimmfqgfuh4pe2kfyw,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Mmmm... Page titles don't have wikitext formatting either and we survive. I never missed '''', [[]] or {{}} in page titles, although I wish I could write something <span lang=""en"" dir=""ltr"">(What's the Story?) Morning Glory</span> and <span lang=""en"" dir=""ltr"">C++</span> in a title of the respective Hebrew Wikipedia articles. But still, I survive (with {{DISPLAYTITLE}}).
+
+MediaWiki section headings can have links, and people do use them, but I have no idea why, because it is ugly, unnecessary, and untappable on mobile. This could probably be fixed in MobileFrontend, but I'd just disallow them. Italics could be useful in section headings, for book titles and such, but I could live with that, too. (DYK: It's specific to English and some other languages written in the Latin alphabet. Some languages don't actually use italics. And guess what, they survive.)
+
+And I could certainly survive without wiki syntax in Flow topic titles.",1427921803,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,Previous comments are from 2013. This task should be higher priority now.,1427517668,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Links in headers are definitely needed in final product! Links are often used on ""specialty pages"" like image workshops or administrators noticeboards to quickly give a link to the file/user in question (which/whom the whole topic is about).",1385597285,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #7)
+
+Thanks for the clarifications. :-)",1384920560,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #6)
+> (In reply to comment #5)
+> > With wikitext, it's sort of all or nothing; it would be a huge pain to
+> > disallow all wikitext except, say, italics. Of course, if anybody out there
+> > thinks it's easy, patches welcome ;)
+> 
+> This bug tracker keeps bugs open if patches are welcome. We'll just adjust
+> the
+> importance/priority to lowest/enhancement, I suppose.
+> 
+> For what it's worth, we implement partial parsers in weird places. Consider
+> edit summaries, which auto-link internal links, but don't auto-link external
+> links and magic links and don't allow formatting such as bold or italics. Not
+> that we really should continue this practice of creating new partial
+> parsers...
+> but it's certainly not unprecedented.
+> 
+> > Since this is just the MVP, I think it makes sense to keep things simple for
+> > now and just keep titles in plaintext.
+> 
+> The most valuable player? Sorry, I don't know what ""MVP"" means.
+> 
+""Minimum viable product"". Basically it's designed to be just complete enough that we can show it off without it falling over. An example would be Page Curation, where we deployed in a really, really unfinished form and then developed where people could see it.
+
+(actually, page curation is not the best example since it broke blocking for ~20 minutes, somehow. But.)
+
+Title linking may (heck, probably will) be necessary for the finished thing, but it's not necessary for the ""demo model""; while it'd be nice to have, I would rather we made the features we do have work.
+
+> > If there's a demonstrable need to have wikitext in titles that outweighs all
+> > the cons, it's something we can easily change.
+> 
+> Having watched the train wreck that was VisualEditor's deployment, I can that
+> it's often small 'features' like this that can potentially be a very big deal
+> to a wiki and its workflows. If you look at a process such as [[WP:RFPP]],
+> you
+> can see a half-dozen links in many headers, each of which correspond to
+> discrete units of work. I think attempting to de-wikify the topic title may
+> result in a lot of annoyed users.
+
+I agree it'll be a big deal, but this is the MVP; if there's a need, we can build it into the next release.",1384883007,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #5)
+> With wikitext, it's sort of all or nothing; it would be a huge pain to
+> disallow all wikitext except, say, italics. Of course, if anybody out there
+> thinks it's easy, patches welcome ;)
+
+This bug tracker keeps bugs open if patches are welcome. We'll just adjust the importance/priority to lowest/enhancement, I suppose.
+
+For what it's worth, we implement partial parsers in weird places. Consider edit summaries, which auto-link internal links, but don't auto-link external links and magic links and don't allow formatting such as bold or italics. Not that we really should continue this practice of creating new partial parsers... but it's certainly not unprecedented.
+
+> Since this is just the MVP, I think it makes sense to keep things simple for
+> now and just keep titles in plaintext.
+
+The most valuable player? Sorry, I don't know what ""MVP"" means.
+
+> If there's a demonstrable need to have wikitext in titles that outweighs all
+> the cons, it's something we can easily change.
+
+Having watched the train wreck that was VisualEditor's deployment, I can that it's often small 'features' like this that can potentially be a very big deal to a wiki and its workflows. If you look at a process such as [[WP:RFPP]], you can see a half-dozen links in many headers, each of which correspond to discrete units of work. I think attempting to de-wikify the topic title may result in a lot of annoyed users.",1384831495,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"With wikitext, it's sort of all or nothing; it would be a huge pain to disallow all wikitext except, say, italics. Of course, if anybody out there thinks it's easy, patches welcome ;)
+
+Since this is just the MVP, I think it makes sense to keep things simple for now and just keep titles in plaintext. If there's a demonstrable need to have wikitext in titles that outweighs all the cons, it's something we can easily change.",1384813132,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/471, but people from the community are welcome to contribute here and in Gerrit.",1384761822,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #1)
+> Wikitext is purposefully Plain text only. 
+
+s/Wikitext is/Topic-titles are/
+Sorry.
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > *Other?
+> > ** Is there any other wikitext that topic titles might need?
+> 
+> Magic words, covered by a separate bug. External links. Bold. Probably a
+> million other pieces of formatting.
+
+Bold is never (?) needed in topic titles. Unless there are foreign language projects that require it?
+
+External links will presumably follow whatever decision we arrive at with internal wikilinks.
+
+I'll ask the team to give more details, and potentially reconsider certain aspects (particularly italics).",1384745567,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #1)
+> ** Links generally shouldn't be in headers, because the bolded text makes it
+> harder for some people to see that the link is there.
+
+When I look at [[WP:AN]] and [[WP:AN/I]], I see many headers that contain links. When I look at [[User talk:Quiddity]] ([[Special:Permalink/581983546]]), I see headers containing italics and links. What are you talking about?
+ 
+> ** Plus it's generally counter to the (Enwiki) styleguides [[WP:LINKSTYLE]]
+> and [[WP:Header]].
+
+I'm not sure what you're talking about here. The style guidelines you're linking to obviously apply only to content, not to discussions. Flow is specifically focused on discussions (non-content). Your links seem completely irrelevant.
+
+> *Other?
+> ** Is there any other wikitext that topic titles might need?
+
+Magic words, covered by a separate bug. External links. Bold. Probably a million other pieces of formatting.",1384744852,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Wikitext is purposefully Plain text only. IIRC, these are the reasons why:
+
+*Links: 
+** Links generally shouldn't be in headers, because the bolded text makes it harder for some people to see that the link is there.
+** Plus it's generally counter to the (Enwiki) styleguides [[WP:LINKSTYLE]] and [[WP:Header]]. (Although, do any other projects make a standard practice of including links in section headers?)
+** Also ""editors who have their preferences set to edit sections by clicking on the header will not be able to click these links"" - [[Help:Section#Section_linking]]   (Although this might not apply to Flow)
+** Flow currently uses most of the topic-title as a clickable area to trigger the topic-collapse. This would conflict with wikilinks.
+
+*Italics:
+** I agree that this should be allowed. We need italics for proper formatting of things like media titles, court cases, etc, in Enwiki. ([[WP:ITALICS]])
+
+*Other?
+** Is there any other wikitext that topic titles might need?",1384744398,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"This isn't a VE bug but ...
+With google translate and chrome when you choose ""always translate"" and then hide the translate bar, the look and feel is really WP:en or WP:yourlanguage
+
+When you choose to contribute with VisualEditor, everything is translated : text, button, message but the little ""search"" in the research box.
+
+Then contributions in different language appear on WP:fr ex : https://fr.wikipedia.org/w/index.php?title=Acrosport&diff=prev&oldid=98352033
+
+A little change in text saves the all translated bloc.
+
+Maybe, the VE edit button should be block with a warning message or the text display for edition should block google translate (I don't know if it's possible) like textarea does.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Whiteboard**: aklapper-moreinfo",1384560300,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-u7nbiznggvbdhjsuerpt,task_description,resolved
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Change 200746 merged by jenkins-bot:
+Add class=""notranslate"" to prevent Chrome from translating the CE DOM
+
+[[https://gerrit.wikimedia.org/r/200746]]",1427750736,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Change 200746 had a related patch set uploaded (by Catrope):
+Add class=""notranslate"" to prevent Chrome from translating the CE DOM
+
+[[https://gerrit.wikimedia.org/r/200746]]
+",1427750311,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Roan's found a way to get Google Translate to be suppressed, which is awesome.",1427749597,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"BTW, I send feedback to Google Translate, requesting they ignore contenteditable areas. Probably not gonna make a difference, but you never know.",1427745864,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"I've nominated this task to Q3 blockers as it keeps damaging articles on frwiki, and I highly doubt that the snowmen are really added by google translate.
+
+https://fr.wikipedia.org/w/index.php?title=Ben_Bocquelet&diff=113382413&oldid=113108176
+https://fr.wikipedia.org/w/index.php?title=Jake_le_chien&diff=113382267&oldid=113253474
+https://fr.wikipedia.org/w/index.php?title=Miss_Rainicorne&diff=prev&oldid=113234436
+",1427744844,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"According to Drongou, this ""google problem"" would also explain that in the following edit, snowmen were added by VE to the text.
+I doubt that google translate adds snowmen to its translation, and its a recurrent problem with VE.
+
+https://fr.wikipedia.org/w/index.php?title=Touche_pas_%C3%A0_mon_pote&curid=5972689&diff=111575789&oldid=110714100",1423142463,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Unfortunately the only way to fix this is to add:
+
+  <meta name=""google"" content=""notranslate"" />
+
+to the <head> of every Wikipedia page, which is undesirable (not least because it would disable translate.google.com requests of the page, too). - See https://support.google.com/webmasters/answer/79812?hl=en
+
+I think the duty lies with Google to fix Chrome to not translate contentEditable elements. There doesn't appear to be anything we can do at Wikimedia to fix this.
+
+Marking as INVALID.",1384842276,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"With Chrome
+
+Go on a wiki with a language different of the language choosen in Chrome parameter
+
+For example, if Chrome language is english go on WP:fr
+
+For a registred account change the language in wiki preference to the language of the wiki (here français) because the button in english will block the chrome translate banner or do it on IP.
+
+Go on a WP:fr page
+The chrome translate banner appears; choose always translate and close the banner (not compulsory but better for the look and feel) 
+
+Go on VE (modifier button)
+
+Select the first word (just one word) of any paragraph. Do copy/paste. (copy the word on himself) Then save
+
+Then you get a paragraph in english in a french article.
+
+Because it's difficult to change a Chrome for french to a Chrome for english (Chrome doesn't want to forget he's in a french environment), I've done it on WP:en (in reverse, it will be difficult for you to do it on WP:en) https://en.wikipedia.org/w/index.php?title=User%3ADrongou%2FBug57124&diff=582266868&oldid=582266664",1384812313,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Hi Drongou, 
+thanks for taking the time to report this!
+
+Please describe the actual problem, the expected outcome, and the exact steps to reproduce so somebody else could follow these steps. Also see https://www.mediawiki.org/wiki/How_to_report_a_bug . Thanks in advance!",1384785920,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+VisualEditor: SurfaceObserver sets selection to start of document after closing reference dialog in Chrome,"1. Edit an existing reference or insert a new one
+2. When the dialog is closed, the reference is selected and a callout is displayed
+3. 200ms later the selection moves to the start of the document
+
+Somehow, for some reason, SurfaceObserver is ""fixing"" the selection here.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384381260,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qt6vdckmcwpnahubzp3f,task_description,resolved
+VisualEditor: SurfaceObserver sets selection to start of document after closing reference dialog in Chrome,"
+
+*** This bug has been marked as a duplicate of bug 58090 ***",1394659143,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qt6vdckmcwpnahubzp3f,task_subcomment,NA
+VisualEditor: SurfaceObserver sets selection to start of document after closing reference dialog in Chrome,"Happens on Chromium 25 but not on Firefox 24 (on my Ubuntu system).
+
+When the reference is inserted, the CE cursor gets reset to the start (as always happens with a ContentEditable when you change the content). But then the CE cursor updates the DM cursor, whereas it should happen the other way round.
+
+Evidence: Make SurfaceObserver.pollOnceInternal into a no-op, then right-cursor to a word and click Reference, Insert Reference. Then the CE cursor gets reset to the start of the document, whereas the DM cursor is still in the place where the reference appears.",1384396011,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-qt6vdckmcwpnahubzp3f,task_subcomment,NA
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,"reference icon after the selected text
+
+Steps to reproduce:
+
+1.Click on the edit button for a blank page
+2.Type a text on the first line
+3.Now type another text on the second line
+4.Add a template
+5.Select the second text in a way that it also selects the template
+6.Click on More>Reference 
+7.Add a reference
+
+
+[Note] This might not be the exact steps to reproduce , I am trying to figure out the correct steps.I will update the steps once I am sure.Still filing it to keep track.
+
+Observed Result:
+The reference note gets added in the middle of the template and the second line in a blank line.After that the editor gets unresponsive
+
+Also sometimes the reference icon gets added at the beginning of the first line
+
+See the screenshot attached.
+
+Browser:Chrome 26
+Environment:test 2
+OS: MAC OS X 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12555}",1384305720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_description,resolved
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,I cannot reproduce this bug anymore This got fixed couple of weeks ago.,1398451857,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_subcomment,NA
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,"Created attachment 13790
+case where reference gets added at the beginning of the text
+
+**Attached**: {F12557}",1384372015,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_subcomment,NA
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,"Confirming the steps to reproduce.
+Also, attaching the screenshots where a reference gets added at the beginning of the text",1384371955,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_subcomment,NA
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,"Created attachment 13781
+Reference icon being added at the beginning of the text
+
+**Attached**: {F12556}",1384305800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"I thought it was Opera's fault,
+but tested this again today and it's not related to the browser you're using.
+It appears that when you edit as an unregistered user (on wikis which allow you to...) you'll always get an Edit conflict page when you try to save after you switched to wikitext.
+Tested on multiple wikis on both ns0 and ns2.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56767",1383991740,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_description,resolved
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,I think this is fixed now. If you notice any issues with it (easiest way to test right now is on beta) please reopen,1396640124,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Change 123795 merged by jenkins-bot:
+Fix order of start and base timestamps when switching to the wikitext editor
+
+https://gerrit.wikimedia.org/r/123795",1396639920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Change 123795 had a related patch set uploaded by Alex Monk:
+Fix order of start and base timestamps when switching to the wikitext editor
+
+https://gerrit.wikimedia.org/r/123795",1396562980,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,Some of my confusion on this bug was caused by some extra ways MediaWiki can resolve edit conflicts which I hadn't properly taken into account when testing. It looks like swapping those values fixes this bug. Assigning this to me and bumping the milestone forward.,1396562790,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"So I think that:
+* A conflict is always detected when having switched from VE
+* Said conflict is suppressed when Revision::userWasLastToEdit is run for a logged in user, but if they're anonymous then it's not suppressed.",1396031922,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"I suspect this might have something to do with this code in ve.init.mw.Target.js:
+
+>'wpStarttime': this.baseTimeStamp,
+>'wpEdittime': this.startTimeStamp,
+
+Which seems a bit backwards to me...",1395963311,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Reported again on it.wp, I verified it on my sandbox there (http://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE?veaction=edit); I got the warning, then tried to save anyway, I apparently managed to but nothing appears in the history.",1389136587,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Change 95730 merged by jenkins-bot:
+Share code between conflict resolution and the edit source switch
+
+https://gerrit.wikimedia.org/r/95730",1385462537,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Change 95730 had a related patch set uploaded by Catrope:
+Share code between conflict resolution and the edit source switch
+
+https://gerrit.wikimedia.org/r/95730",1384754242,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,(I wonder if https://bugzilla.wikimedia.org/show_bug.cgi?id=56849 is related?),1384205663,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: Indent and list-related icons' direction should depend on content dir and not GUI dir,"Right now, CSSJanus flips toolbar icons by their definitions, so an icon indent-ltr would automatically turn to indent-rtl when user GUI is set to RTL.
+
+However, the indent and list-related buttons don't depend on user GUI language but rather on the content language. If editing English content, the icon for ""increase indent"" should point from left to the right regardless of user GUI language, and the icon for ""decrease indent"" should point the other way.
+
+For a quick demo, see:
+https://www.mediawiki.org/wiki/User:Mooeypoo/IndentDemo?veaction=edit&setlang=he
+(Wiki language is English/LTR and GUI is Hebrew/RTL)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383965220,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-733eiwtp5o2tjyz7twh7,task_description,resolved
+VisualEditor: Indent and list-related icons' direction should depend on content dir and not GUI dir,This is fixed with this patch https://gerrit.wikimedia.org/r/#/c/95560/,1386782895,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-733eiwtp5o2tjyz7twh7,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"We would like to revert the fix for bug 39617.  That bug should have been fixed via the 'whitespace' CSS property.
+
+The 'fix' to bug 39617 caused Parsoid to begin creating dirty diffs (and failing its test suite) -- see https://gerrit.wikimedia.org/r/92978
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=39617",1383947760,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gays66miu6qia6yucqn2,task_description,resolved
+Newlines after </li> cause dirty diffs with Parsoid,This has since been fixed in core.,1404842267,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Change 94443 abandoned by Cscott:
+Revert ""Have list items occupy their own line"".
+
+Reason:
+Abandoned in favor of Ib7aa9449bbd994cb23b83b3f23cff944b1cddadf
+
+https://gerrit.wikimedia.org/r/94443",1402679936,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Change 134380 merged by jenkins-bot:
+Update list item newline handling to follow Parsoid's model
+
+https://gerrit.wikimedia.org/r/134380",1402337597,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Bartosz Dziewoński from comment #26)
+> (In reply to Gabriel Wicke from comment #25)
+> > PHP + tidy inserts newlines in the first case too, which is broken.
+> 
+> I'm pretty sure that this is the case only if Tidy is enabled, and that kind
+> of behavior is one of the many reasons why I want to kill it. (I really do
+> not know why no one from the Parsoid team shares my sentiment about this.)
+
+Believe me, we want to kill it just as much as you do. And we have been working hard on it for 2+ years now.",1400604941,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Change 134380 had a related patch set uploaded by GWicke:
+Update list item newline handling to follow Parsoid's model
+
+https://gerrit.wikimedia.org/r/134380",1400602936,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Gabriel Wicke from comment #25)
+> PHP + tidy inserts newlines in the first case too, which is broken.
+
+I'm pretty sure that this is the case only if Tidy is enabled, and that kind of behavior is one of the many reasons why I want to kill it. (I really do not know why no one from the Parsoid team shares my sentiment about this.)",1393027687,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Parsoid does not insert newlines where there are none:
+
+<ul><li>foo</li><li>bar</li></ul>
+
+in wikitext becomes 
+
+<ul><li>foo</li><li>bar</li></ul>
+
+It does preserve newlines from wikitext though:
+
+* foo 
+* bar
+* baz
+
+in wikitext becomes
+
+<ul><li> foo</li>
+<li> bar</li>
+<li> baz</li></ul>
+
+PHP + tidy inserts newlines in the first case too, which is broken.",1393026536,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Sorry, but it isn't. The *old* PHP parser output is:
+
+<ul><li>a
+</li><li>b
+</li><li>c
+</li></ul>
+
+No linebreak *between* list items. Parsoid goes (if I understand above correctly):
+
+<ul><li>a</li>
+<li>b</li>
+<li>c</li></ul>
+
+I want the PHP parser to behave the smae.",1392995324,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Erwin Dokter from comment #22)
+> Ah, so it is only the *tests* that are affected. I think I understand now.
+
+Not just tests. See part (2) in Comment 16.
+
+> Still my question remains: can I make the parser make a clean break *only*
+> between </li> and <li> (as that is the core issue affecting nowrap), without
+> any linebreak before or after <ul> and </ul>?
+
+That is already the case since wikitext has newlines between list items. See below for Parsoid's output.
+
+[subbu@earth tests] echo ""*a\n*b\n*c"" | node parse
+<body data-parsoid='{""dsr"":[0,9,0,0]}'><ul data-parsoid='{""dsr"":[0,8,0,0]}'><li data-parsoid='{""dsr"":[0,2,1,0]}'>a</li>
+<li data-parsoid='{""dsr"":[3,5,1,0]}'>b</li>
+<li data-parsoid='{""dsr"":[6,8,1,0]}'>c</li></ul>
+</body>",1392963187,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Ah, so it is only the *tests* that are affected. I think I understand now.
+
+Still my question remains: can I make the parser make a clean break *only* between </li> and <li> (as that is the core issue affecting nowrap), without any linebreak before or after <ul> and </ul>?",1392940301,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Erwin Dokter from comment #20)
+> OK, this discussion is not going to end in the next couple of hundred years,
+> partly because I will never understand what is really going on. 
+
+Do you want to pop onto IRC (#mediawiki-parsoid) sometime and chat with us about this? We can then post the summary here after that. It might be simpler to figure this out in a more interactive discussion than is possible via bugzilla comments. I am going to be signing off for the day shortly, but the IRC channel is usually active between 9 am PST - 4 pm PST when most of us are around.
+
+> I still
+> don't know where parsoid is getting its HTML from. Can't be from the browser
+> DOM; that has gone through Tidy. 
+
+No, Parsoid generates the HTML as I indicated in Comment 16. In the case of Visual Editor use, VE then sends that HTML (alongwith any user edits) to Parsoid to convert back to wikitext.
+
+Since Parsoid HTML will replace PHP parser HTML at some point in the foreseeable future (this year possibly), if anything requires these newlines to be present for functionality, Parsoid will also have to add them and that is what we are complaining about so far.",1392939729,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"OK, this discussion is not going to end in the next couple of hundred years, partly because I will never understand what is really going on. I still don't know where parsoid is getting its HTML from. Can't be from the browser DOM; that has gone through Tidy. 
+
+Revert the patch.
+
+I just want the parser (as long as it lasts) to emit some sanely formatted lists, just as it outputs sanely formatted tables. Is that too much to ask?
+
+If I can make the parser to make a clean break *only* between </li> and <li>, without any linebreak before or after <ul> and </ul>, would that make parsoid happy?",1392937940,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Erwin Dokter from comment #18)
+> * block level elements (including list itema) must be terminated with e
+> newline
+> * all other (inline) elements should not
+> 
+> Would that ease the situation?
+
+This would in fact complicate the situation. We don't insert newlines in HTML where there were none in the original wikitext. This preserves the semantics independent of the CSS whitespace styling (remember that 'pre' is a possible value) and helps us to round-trip wikitext correctly without introducing spurious newlines.
+
+As discussed in bug 39617, the newlines don't seem to be necessary any more now that the nowrap requirement is gone. Taking into account the cost they have for Parsoid development, I'd recommend removing the code that inserts them from the PHP parser.",1392936264,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Re: ""a\n\n*b""
+
+I don't understand where the extra newline comes from, as the parser outputs only one. Regardless... perhaps we need to go about this another way.
+
+There should be a simple set of rules that govern how parser and parsoid interact, for example:
+
+* block level elements (including list itema) must be terminated with e newline
+* all other (inline) elements should not
+
+Would that ease the situation?",1392930092,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Erwin Dokter from comment #15)
+
+> I can't help but feel that this issue is a major blocker for any parser
+> improvement in the future, so I want to understand exactly where the problem
+> exists and come up with a solution that will prevent such issues in the
+> future.
+
+This is not a general blocker. Parser changes can be done and have been done, but changes have to be considered carefully since there are a lot of dependent users, and that is what you are seeing here in this bug report discussion.",1392928973,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Parsoid converts wikitext to HTML and back. Tidy does not enter the picture at all in the Parsoid pipeline.
+
+There are two separate issues:
+
+1. Parsoid uses the same set of PHP parser tests to make sure that Parsoid generates HTML that doesn't break existing wikitext. It uses PHP HTML to serialize back to wikitext. The extra newline that PHP parser emits introduces extra newlines in wikitext. ""a\n\n*b"" instead of ""a\n*b"". So, the extra newline is a ""dirty diff"". This now obscures our regular testing because we blacklist these failing tests and then try to compare changes in HTML output. So, not entirely unworkable, but requires greater diligence to monitor regressions during development. Ideally, we wouldn't have these failures. Alternatively, we have to fix Parsoid's HTML to wikitext conversion to ignore the extra newlines when they come from the parser's insertion rather than from source -- that means extra bookkeeping.
+
+2. If you want Parsoid HTML to have the same CSS semantics like PHP HTML, Parsoid would also have to start adding these newlines after <ul> and before </ul>. These extra newline characters would now have to be accounted for in the DSR calculations (DSR maps a range to wikitext source to a DOM subtree, ex: wikitext substring [3,9] generate <p>foobar</p> HTML) which is also additional bookkeeping. DSR calculations has been carefully tweaked to account for every single character of wikitext so that Parsoid can faithfully output original wikitext on unedited portions of the HTML. So, Parsoid would have to ignore the extra inserted newlines in its calculations. Without accounting for them, Parsoid will generate different wikitext on conversion which manifests as ""dirty diffs"". Again, all of this extra bookkeeping can be done.
+
+But, if we can avoid the extra newlines, the extra work can be avoided.",1392928746,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"I also have a problem understanding 'dirty diffs'. Where does parsoid get its HTML from? I thought it converted wikitext to HTML and then back. So how does the parser even come into play? Is Tidy also involved? Sorry to ask al this, but I simply need a basic understanding of parsoid.
+
+FYI, the nowrap has been completely removed from hlist, so there are no CSS hacks to deal with. But any locally applied nowrap may cause errors, so the linebreaks must remain.
+
+I can't help but feel that this issue is a major blocker for any parser improvement in the future, so I want to understand exactly where the problem exists and come up with a solution that will prevent such issues in the future.",1392897145,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,That is a scoping problem; Tidy should simply not touch anything that comes out of GeSHi (pre & code). This is simply two external extentions clashing.,1384007212,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Just to guide the discussion, let's try to keep this bug concentrated on the parsertest regressions in Parsoid and other extensions, and possible fixes for that.  Discussion of the hlist issue and the CSS fix (or lack thereof) goes over on bug 39617.
+
+Since most of the discussion has already happened on bug 39617, I'd say that, if in doubt, let's continue the discussion there.  I'm just trying to prevent the discussion from being scattered across gerrit and a bunch of different bugzilla items, and people's good points being lost in the shuffle. (In particular, I'm going to copy comment 10 over to bug 39617.)",1384007129,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to comment #11)
+> (In reply to bug 39617 comment #27)
+> > The Tidy bug is what caused hlists to work in the first place, according to
+> > what you're saying :)
+> 
+> Why is that even considered a bug? list items are block level elements, and
+> as such, should be on their own line per unwritten code style conventions.
+
+Tidy's overzealous newline insertion has caused problems in the past already, see bug 260 (which is still open only because of the same Tidy issue) and bug 38800 (which is basically what Gabriel reported).",1384005116,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to comment bug:39617#27)
+> The Tidy bug is what caused hlists to work in the first place, according to
+> what you're saying :)
+
+Why is that even considered a bug? list items are block level elements, and as such, should be on their own line per unwritten code style conventions.",1384004546,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"https://test.wikipedia.org/wiki/MediaWiki:Common.css contain current CSS for hlist.
+https://test.wikipedia.org/wiki/User:Edokter/sandbox contains the test cases.
+
+Any suggested changes will break one or more testcases.",1384004374,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to comment #8)
+> Unless you come up with a working CSS solution (which I doubt you will), I
+> insist my patch be reinstated and Parsoid be fixed instead.
+
+(Just a note that the patch was not reverted, but a revert has been submitted for review / consideration.)
+
+Is there a demo of hlist set up somewhere? Or a list of things it does, and a list of cases it supports? Any of these things would be very useful here.",1384000050,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Oh for crying...! Please provide a COMPLETE working set of CSS for horizontal lists that supposedly fixes all the bugs I have spent TWO YEARS trying to fix! I have tested EVERY scenario, including inline-block, which breaks nested lists in *ALL* browsers.
+
+Unless you come up with a working CSS solution (which I doubt you will), I insist my patch be reinstated and Parsoid be fixed instead.",1383992105,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to comment #5)
+> I've already seen the patch and sadly it is not telling me anything. What
+> does
+> a ""dirty diff"" mean here? A dirty diff during after editing a page with
+> VisualEditor? Because that's the only significant definition I know.
+
+Parsoid is failing the parser tests in html2wt and html2html mode since the same parser tests are used by core and Parsoid. I blacklisted the failures for now. But this blacklisting is not ideal since we have to be a bit more careful about failures in the future when inspecting changes.
+
+That aside, if VE and Parsoid emits the same HTML that the core parser does for lists (emitting newlines around <ul> tags), then we have to deal with it.",1383953982,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Also, see https://gerrit.wikimedia.org/r/#/c/93626/ where I started messing with Parsoid to prevent these dirty diffs, but it seems a lot more pain than worth it currently -- it is mostly a distraction from other critical issues that I just left it in WIP stage. This wont be an issue in production necessarily right now, but if the CSS fix is not employed, then Parsoid will also have to emit the same kind of HTML that the core php parser emits and then this could be an issue in production with occasional dirty diffs without this WIP patch being worked out to completion. So, seems like a lot of pain for unclear benefit.",1383953825,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"I've already seen the patch and sadly it is not telling me anything. What does a ""dirty diff"" mean here? A dirty diff during after editing a page with VisualEditor? Because that's the only significant definition I know.",1383953741,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Matma(In reply to comment #3)
+> Why does this cause dirty diffs? Can I get a link to such diff?
+
+See the gerrit patch cscott linked to in the bug description (https://bugzilla.wikimedia.org/show_bug.cgi?id=56809#c0)",1383953535,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,Why does this cause dirty diffs? Can I get a link to such diff?,1383952668,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,https://bugzilla.wikimedia.org/show_bug.cgi?id=39617#c18 demonstrates a css fix. Related comment is https://bugzilla.wikimedia.org/show_bug.cgi?id=39617#c17,1383950334,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Change 94443 had a related patch set uploaded by Cscott:
+Revert ""Have list items occupy their own line""
+
+https://gerrit.wikimedia.org/r/94443",1383949214,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Misplaced
+
+Steps to reproduce
+
+1. Click on the Edit button for an article or click on the media icon on a image
+2. Type something
+3. Go to some other window of your browser
+4.Come back to the editor after few minutes (approx. 5-10 minutes)
+5.Now select the text and click on the link icon 
+
+Observed Result:
+The link inspector appears broken or misplaced 
+
+
+
+Browser:Chrome
+Environment:test2
+Page:Any
+Reproducible: Mostly  
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12157}",1383942000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_description,declined
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,This appears to now be fixed FWICS; closing as such.,1398720912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,Other inspectors (e.g. MWExtensionInspector) are affected as well.,1394745744,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Created attachment 14014
+reproduced on 6th december
+
+**Attached**: {F12162}",1386366426,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Reproduced it again on Betalabs:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=6th_december&veaction=edit
+
+See the screenshot attached",1386366371,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,This issue is fixed now and verified on betalabs,1386115278,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,should this have blocked deployment?,1385503716,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Yes, the issue reported here is now appearing in production/Live environment for any page.
+
+(In reply to comment #5)
+> (In reply to comment #4)
+> > Now it is live.
+> 
+> ????  You mean the problem in this bug report is deployed to production
+> servers
+> now, or how to interpret that comment?",1385404312,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"(In reply to comment #4)
+> Now it is live.
+
+????  You mean the problem in this bug report is deployed to production servers now, or how to interpret that comment?",1385133843,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,Now it is live.,1385073357,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Created attachment 13742
+Broken UI 2
+
+**Attached**: {F12161}",1383942104,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Created attachment 13741
+Broken UI
+
+**Attached**: {F12160}",1383942074,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Created attachment 13740
+Broken
+
+**Attached**: {F12159}",1383942046,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,"Currently, if I go to https://www.mediawiki.org/wiki/User:Amire80/ve-poem and edit it using VE, I can edit the content of the <poem> tag. If my UI language is Hebrew, then the <textarea> for editing the poem is RTL. I would expect it to be LTR.
+
+Ideally the default direction for the <textarea> that this feature should be the direction of the surrounding text. If it's hard to get, then the direction of the page's content will probably suffice. (Currently it will be the same as the content language of the wiki, but it may change some day when we finally introduce page language.)
+
+There can also be some tags for which the default direction must be different, such as <source>, but that's an issue for a separate bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383920040,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-kuprsa4m7ibn5pvxkone,task_description,resolved
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,"Change 94375 merged by jenkins-bot:
+MWExtensionInspector input direction based on content
+
+https://gerrit.wikimedia.org/r/94375",1383939000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kuprsa4m7ibn5pvxkone,task_subcomment,NA
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,"Change 94375 had a related patch set uploaded by Mooeypoo:
+MWExtensionInspector input direction based on content
+
+https://gerrit.wikimedia.org/r/94375",1383926174,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kuprsa4m7ibn5pvxkone,task_subcomment,NA
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,Related: Bug 56780.,1383920880,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-kuprsa4m7ibn5pvxkone,task_subcomment,NA
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,"From IRC:
+
+<mooeypoo>	what do you mean ""must correspond to surrounding content direction?
+<mooeypoo>	of the <poem> ?
+<mooeypoo>	so, it should be content direction rather than GUI direction?
+<aharoni>	mooeypoo: It definitely shouldn't be the GUI direction. It has nothing to do with it.
+<mooeypoo>	nods
+<aharoni>	The direction of the inspector's GUI should be the GUI direction,
+<aharoni>	but the textarea needs the direction of the content.
+<mooeypoo>	yeah
+<mooeypoo>	makes sense, just wanted to make sure
+<aharoni>	Ideally, if the wiki is in English, but it's a <poem> tag inside <div lang=""fa"" dir=""rtl"">, then the textarea should be rtl.",1383920584,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-kuprsa4m7ibn5pvxkone,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"There are 2 users at least (Fram and myself)
+reporting that the new option does not seem to work when using FF (in our case, version 25).
+I tried to VEdit my sandboxes in several languages.
+You can use https://it.wikipedia.org/wiki/Utente:Elitre/Sandbox?veaction=edit if you need to.
+After you click on the Switch button, and click OK on the warning message, the surfaces is ""grayed out"", and just stays that way without actually switching.
+Please notice you can still VEdit at this time, and even save.
+The chosen skin instead does not seem to matter (it didn't work for me with any of them).
+
+In Fram's words:
+<< I get the ""you are about to change"" message, but then the VE page gets ""bleached"" out, as if an opaque glass is put in front of it, and nothing further happens. I can still use the toolbox at this time, and can edit the article in VE, but it doesn't have the normal look.>>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56835",1383909600,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_description,resolved
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94595 abandoned by Jforrester:
+Fix edit source switch in Firefox
+
+Reason:
+Not done.
+
+https://gerrit.wikimedia.org/r/94595",1384864407,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94594 abandoned by Jforrester:
+Fix edit source switch in Firefox
+
+Reason:
+Not done.
+
+https://gerrit.wikimedia.org/r/94594",1384864394,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94595 had a related patch set uploaded by Jforrester:
+Fix edit source switch in Firefox
+
+https://gerrit.wikimedia.org/r/94595",1384069041,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94594 had a related patch set uploaded by Jforrester:
+Fix edit source switch in Firefox
+
+https://gerrit.wikimedia.org/r/94594",1384069020,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94498 merged by jenkins-bot:
+Fix edit source switch in Firefox
+
+https://gerrit.wikimedia.org/r/94498",1384047723,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94498 had a related patch set uploaded by Esanders:
+Fix edit source switch in Firefox
+
+https://gerrit.wikimedia.org/r/94498",1384001125,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"(Your wish is my command.
+See 56835 now, turns out it had nothing to do with Opera after all.)",1383991856,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Dropping the Opera issue, as that appears unrelated. Open as a different bug?",1383948094,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"FYI, I tried to VEdit a few sandboxes while unlogged with Opera.
+After switching to wikitext, when I try to save changes I always get an ""edit conflict"" notice. It will save if I re-add my text, but clearly this is not optimal :)",1383912386,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"beta commons localStorage nearly full
+
+seen on beta labs while logged in as Selenium_user
+seen in Chrome/Chromium, not checked in Firefox (yet)
+
+consistent behavior seen:  
+initial load of VisualEditor in beta enwiki sets localStorage to 3.5MB
+initial load of UploadWizard in beta commons sets localStorage to 2.5MB
+
+routine navigation to pages like 
+* wikitext editor
+* Flow e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA
+* Special:NewPagesFeed
+* etc
+
+continues to fill localStorage until it maxes out.
+
+inconsistent behavior: 
+
+I do not have a consistent repro to max out localStorage.  at first I thought that repeatedly hitting shift-reload/cancel on a ?veaction=edit page did it, but on my second attempt I was unable to max out localStorage that way
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56778
+
+**Attached**: {F12036}",1383847740,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_description,duplicate
+localStorage nearly or totally filled with routine operation,"(In reply to comment #9)
+> (In reply to comment #8)
+> > (In reply to comment #7)
+> > > My suspicion is that the mtimes of modules is being continuously changed
+> > > because of the way [beta] is set up.
+> > 
+> > Doesn't appear to be the case. I hacked up a quick script to check:
+> > <https://gist.github.com/atdt/7359920>. No changes were merged to master
+> > while
+> > I tested, though; still interested to know what happens then.
+> 
+> And BTW, if you do find config differences between beta enwiki and prod,
+> please
+> let me know.  I have other intermittent/unreproduceable performance problems
+> with Chrome (not Firefox) there that are becoming quite frustrating, seen in
+> particular in VE and UploadWizard.  I worry that these problems exist in
+> production but are so flaky that they are not reported.
+
+modules are updating pretty frequently on beta. 20 mins' worth here: <https://gist.github.com/atdt/7359920#file-rl-mon-log>. I'm running it again now *with* timestamps.",1383852748,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"(In reply to comment #8)
+> (In reply to comment #7)
+> > My suspicion is that the mtimes of modules is being continuously changed
+> > because of the way [beta] is set up.
+> 
+> Doesn't appear to be the case. I hacked up a quick script to check:
+> <https://gist.github.com/atdt/7359920>. No changes were merged to master
+> while
+> I tested, though; still interested to know what happens then.
+
+And BTW, if you do find config differences between beta enwiki and prod, please let me know.  I have other intermittent/unreproduceable performance problems with Chrome (not Firefox) there that are becoming quite frustrating, seen in particular in VE and UploadWizard.  I worry that these problems exist in production but are so flaky that they are not reported.",1383850834,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"(In reply to comment #7)
+> My suspicion is that the mtimes of modules is being continuously changed
+> because of the way [beta] is set up.
+
+Doesn't appear to be the case. I hacked up a quick script to check: <https://gist.github.com/atdt/7359920>. No changes were merged to master while I tested, though; still interested to know what happens then.",1383850574,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"Several points:
+- Can you isolate the size of the module storage? You can check it by running mw.loader.inspect('store') in a JavaScript console. (See 'totalSize' column).
+- Pruning old modules from the cache is deferred until the page / DOM is quiescent. What happens if you just let the page load and hang out for 5-10 seconds?
+- Is this reproducible outside the beta cluster? My suspicion is that the mtimes of modules is being continuously changed because of the way it is set up. Haven't investigated yet, but the way to check would be to load the startup module and compare module versions across reloads.",1383849242,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"Well, the limit can be worked around… 
+
+""Introducing the HTML5 Hard Disk Filler™ API"" http://feross.org/fill-disk/
+
+:P",1383848898,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"So apparently the only way to find the limit is to keep adding data until you fill it up. Awesome.
+
+http://dev-test.nemikor.com/web-storage/support-test/
+
+^ looks like a frequent limit is 5MB, which in some browsers means 2.5M *UTF-16 code points*. That's going to be pretty tight for the amount of code we want to store. :(",1383848334,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"(In reply to comment #3)
+> Can we determine the limits of available localStorage in some consistent way?
+
+I believe it is per-browser.  Empirically I found that my Chromium allows 5MB while my Chrome allows 10MB. 
+
+See http://arty.name/localstorage.html (warning: fills up your local storage upon loading the page and gives you a status message when done)",1383848242,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,Can we determine the limits of available localStorage in some consistent way?,1383847924,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"Comment on attachment 13721
+beta commons localStorage nearly full
+
+I meant beta enwiki for this attachment",1383847860,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"Created attachment 13722
+beta commons localStorage after loading UploadWizard
+
+**Attached**: {F12037}",1383847809,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"For some reason, the 'keydown' event is being unbound when the suggestions popup appears, so the function is never firing. However, it seems like they shouldn't be listening to keydown anyway because they only care about when the enter key is pressed and that event is already available on the input as the 'enter' event (from OO.ui.TextInputWidget).
+
+With love from the Wikia development team.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1383782580,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_description,declined
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"(In reply to Krinkle from comment #4)
+> There is still a tech debt here though, we should use OOjs UI's ""enter"" event 
+> (instead of manually binding keypress
+
+Done in Ia47bc8976f22dfe7e3a6fb6068dc4b6e03a3357b.",1412973553,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"Nevermind. They all work fine now. There is still a tech debt here though, we should use OOjs UI's ""enter"" event (instead of manually binding keypress and looking for keyCode=13), but it works fine.",1412973234,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"The handler from MWCategoryWidget is working fine. However, here is the code I used for comment #2
+
+In ve/ui/MWCategoryWidget.js:
+
+	this.input.$input.on( 'keypress', function () {
+		console.log( ['MWCategoryWidget', 'MWCategoryInputWidget', '$input', 'keypress'] );
+	} );
+	this.input.on( 'enter', function () {
+		console.log( ['MWCategoryWidget', 'MWCategoryInputWidget', 'enter'] );
+	} );
+
+And the 'enter' event never fired. Because there is still a mystery here. The event bound by OO.ui.TextInputWidget on $input for 'keypress' (which fires 'enter') disappears somehow.
+
+Putting the same logger in there makes it never fire.",1412972772,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"Created attachment 16743
+Screenshot of bug not happening.
+
+I can't reproduce this. When typing in the input, I see all keydowns happening as they should. From the key codes in the screenshot:
+* [shift]
+* E
+* x
+* a
+* m
+* p
+* l
+* e
+* [enter]
+
+**Attached**: {F12000}",1412971168,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"<Krenair> Krinkle, http://imgur.com/a39IuMk - that's handlers, handlers.length, handleObj
+<Krenair> Immediately after handlers.push( handleObj ); in jquery.event.add
+
+handlers.push( handleObj );
+if ( types.indexOf( 'keydown' ) !== -1 ) {
+	console.log( handlers );
+	console.log( handlers.length );
+	console.log( handleObj );
+}",1404762874,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor in Flow: CE arrives much later than controls,"this may be more appropriate to assign to VisualEditor than Flow:
+
+in a fresh instance of the Chrome browser, log in and go to page http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA 
+
+* click Start a new topic
+* watch the spinner as VisualEditor loads up
+* when the spinner stops and the editor controls are visible, attempt to type in the ContentEditable surface
+
+* only some seconds after the spinner stops and the controls appear is it possible to place the cursor in the CE surface and begin typing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383754500,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-hic2xcoiiq7ialvw5olf,task_description,invalid
+VisualEditor in Flow: CE arrives much later than controls,"(In reply to comment #3)
+> (In reply to comment #2)
+> > Flow no longer supports VE
+> 
+> Eep!
+
+Clarification; the model as deployed on production intentionally does not support VE until we have some breathing room for it ;p",1387247486,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-hic2xcoiiq7ialvw5olf,task_subcomment,NA
+VisualEditor in Flow: CE arrives much later than controls,"(In reply to comment #2)
+> Flow no longer supports VE
+
+Eep!",1387247422,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hic2xcoiiq7ialvw5olf,task_subcomment,NA
+VisualEditor in Flow: CE arrives much later than controls,Flow no longer supports VE,1386881313,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-hic2xcoiiq7ialvw5olf,task_subcomment,NA
+VisualEditor in Flow: CE arrives much later than controls,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/409, but people from the community are welcome to contribute here and in Gerrit.",1383805182,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-hic2xcoiiq7ialvw5olf,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"Link inspector and Math inspector together
+
+Steps to reproduce:
+
+1.Click on the Edit beta
+2.Add a media such as image
+3.Now open the Math inspector from More>Latex
+
+Observed Result:
+The Math inspector does not open,Now if you click on link both the inspectors open together.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12805}",1383698100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_description,resolved
+VisualEditor: Math inspector does not check type of node it's inspecting,Verified the fix on production,1398988169,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,Verified the fix on test2,1398898856,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,Verified the fix on Betalabs,1398114293,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,Fixed in gerrit 125933.,1397694799,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"Created attachment 15126
+Errors and blank inspector
+
+**Attached**: {F12806}",1397691900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"It also throws the following errors and the math inspector gets completely blank.:
+Uncaught TypeError: Cannot call method 'getAttribute' of null VM977:417
+Uncaught TypeError: Cannot call method 'getOuterRange' of null",1397691870,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"Both issues caused by the math inspector not checking that what it's inspecting is really a math node, changing summary.",1383700342,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"(In reply to comment #1)
+> I couldn't reproduce the double inspector offhand.
+I can now:
+1. Insert an image
+2. Unselect and reselect the image so just the image is selected
+3. Open the math inspector. It attempts to inspect the image and crashes
+4. Post-crash, you get the double inspector thing",1383700292,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"At least one issue here is that MWExtensionInspector and MWMathInspector don't check that this.focusedNode is actually of the right type before doing things, so the math inspector will happily inspect references etc.
+
+I couldn't reproduce the double inspector offhand.",1383700014,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+Move OOjs and OOjs-UI to their own repos,"Currently OOjs is mastered in github(!) and OOjs-UI within VisualEditor; instead, they should be in their own repos so that other projects can re-use them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383587220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sffy2i74xcwn56xygl5s,task_description,resolved
+Move OOjs and OOjs-UI to their own repos,This is now done.,1383932971,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sffy2i74xcwn56xygl5s,task_subcomment,NA
+Move OOjs and OOjs-UI to their own repos,"Change 94264 merged by jenkins-bot:
+Move files from modules/oojs-ui to the repository root
+
+https://gerrit.wikimedia.org/r/94264",1383932049,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sffy2i74xcwn56xygl5s,task_subcomment,NA
+Move OOjs and OOjs-UI to their own repos,"Change 94264 had a related patch set uploaded by Jforrester:
+Move files from modules/oojs-ui to the repository root
+
+https://gerrit.wikimedia.org/r/94264",1383931993,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sffy2i74xcwn56xygl5s,task_subcomment,NA
+Provide a mechanism to transclude/include translatable templates,"If a template is made translatable, {{template}} no longer works as expected. While this is hard to fix, Translate extension should provide out of the box the functionality of https://www.mediawiki.org/wiki/Template:Translatable_template.",1383283200,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ux7txrspzgavrsg33265,task_description,duplicate
+Provide a mechanism to transclude/include translatable templates,Of course I should have checked whether such tasks exists before doing changes...,1458719733,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-ux7txrspzgavrsg33265,task_subcomment,NA
+Provide a mechanism to transclude/include translatable templates,"I am going to repuspose this task. This might change when support for VisualEditor is added. In the mean time the recommended way is to use templates such as https://www.mediawiki.org/wiki/Template:Translatable_template
+
+Translate extension should provide such facility out of the box, or at least make it easier than copying that template (which requires Lua).",1458719110,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-ux7txrspzgavrsg33265,task_subcomment,NA
+Provide a mechanism to transclude/include translatable templates,"This has never been supported. Bug 48891 might change that, but I'm desperately needing help from people being able to hack the parser.",1383300585,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-ux7txrspzgavrsg33265,task_subcomment,NA
+Provide a mechanism to transclude/include translatable templates,"I meant
+
+2. Transclude page A in Page B. Sorry.",1383283298,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ux7txrspzgavrsg33265,task_subcomment,NA
+Image alt attribute resolves without alt= in wikitext,"This is related to bug #48924 and came up while working on VE's new media dialog.
+
+Symptoms :
+1. Parsoid seems to ignore adding an alt attribute to an image that had no alt attribute previously -- the image still has no alt attribute post-save, even though the DM/CE in VisualEditor were both updated properly.
+
+2. When the alt string in 'alt=something' is changed, the resulting wikitext post-save is produced without the 'alt='
+
+So, an original wikitext:
+
+[[File:Someimage.png|thumb|265x265px|some caption|right|alt=some alternate text]]
+
+After editing the alt property in VE, the wikitext post-save becomes:
+
+[[File:Someimage.png|thumb|265x265px|some caption|right|some alternate edited text]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383174540,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-vyjwvfkazlz4xdouhxqh,task_description,resolved
+Image alt attribute resolves without alt= in wikitext,"Change 103082 merged by jenkins-bot:
+Edited image attributes should override data-parsoid value.
+
+https://gerrit.wikimedia.org/r/103082",1389141626,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vyjwvfkazlz4xdouhxqh,task_subcomment,NA
+Image alt attribute resolves without alt= in wikitext,"Change 103082 had a related patch set uploaded by Cscott:
+Edited image attributes should override data-parsoid value.
+
+https://gerrit.wikimedia.org/r/103082",1387811327,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vyjwvfkazlz4xdouhxqh,task_subcomment,NA
+"VisualEditor: When cursor ends up outside of a content branch node, move it back into one","Document:
+
+ h2> Foo
+ p> Lorem ipsum.
+ h2> Bar
+ p> Bla bla bla.
+
+Steps:
+
+* Put cursor in the first heading between ""F"" and ""oo"".
+* Change text style to paragraph (via menu or or use ctrl-0).
+* Observe cursor going wild (disappears in Firefox, appears outside the document in the margin in Chrome, bug 50442)
+* Type 3 characters (""a"", ""b"", ""c"")
+
+Firefox result:
+
+3 new paragraph appear.
+
+ p> o [new]
+ p> o [new]
+ p> a [new]
+ p> Foo
+ p> Lorem ipsum.
+
+And more on every subsequent keystroke. It seems to have copied this ""o"" from ""Foo"" somehow. And ""b"" and ""c"" never appear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1383076620,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-aiigjvy5vmwd6y2u2ole,task_description,resolved
+"VisualEditor: When cursor ends up outside of a content branch node, move it back into one",I believe that this was fixed by Ed's Firefox CE re-write.,1399418779,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aiigjvy5vmwd6y2u2ole,task_subcomment,NA
+"VisualEditor: When cursor ends up outside of a content branch node, move it back into one",*** Bug 56338 has been marked as a duplicate of this bug. ***,1386028032,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aiigjvy5vmwd6y2u2ole,task_subcomment,NA
+VisualEditor: Changing text formatting dislodges the text cursor,"Screenshot of problem.
+
+1. Put cursor in a heading.
+2. Change text style to paragraph (or use ctrl-0).
+3. Observe the cursor is now outside the content area in the document margin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12115}",1383076200,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-htxalzptwgauyfiuzj3f,task_description,resolved
+VisualEditor: Changing text formatting dislodges the text cursor,"
+
+*** This bug has been marked as a duplicate of bug 56340 ***",1386028032,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-htxalzptwgauyfiuzj3f,task_subcomment,NA
+VisualEditor: Text formatting menu issues,"The text style menu has major issues. For all intends and purposes I declare it completely broken. Tracking them here in case they're related.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383076080,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5qityf526pfz6qwd7svp,task_description,invalid
+VisualEditor: Text formatting menu issues,Not needed for one bug.,1386028091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5qityf526pfz6qwd7svp,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,"page after typing one character
+
+seen in Firefox not Chrome in master as of Oct 28
+
+Edit any page on http://en.wikipedia.beta.wmflabs.org
+
+When VE manifests, type any character
+
+Existing text of page jumps down one line, as if VE has inserted a RETURN command upon typing in the page. 
+
+Seen only in Firefox, not Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56642
+
+**Attached**: {F12001}",1382992380,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-catfculfgyiwykiyu7uj,task_description,resolved
+VisualEditor: Unexpected RETURN character upon first editing a page,"Unsetting ""VERIFIED""; we don't generally use that, and setting it will hide it from people's saved searches.",1384856020,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,"Verified for on https://test2.wikipedia.org/ with FireFox 25 on MAC OS X 10.8.5
+Example test page:https://test2.wikipedia.org/wiki/Verify_56274",1384539917,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,Verified in for any page on http://en.wikipedia.beta.wmflabs.org,1384453796,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,Looks like this issue got fixed.Verified in betalabs with FF 25.,1384390061,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,"Reproduced this bug FireFox.Also observed that , in FireFox upon clicking on the Edit-beta the value of the heading pull down menu is blank instead of the format the existing text have as soon as a character is entered and the existing line goes to the next line, the ""Paragraph"" value appears in the heading drop down.
+
+However, the case is different for chrome , the value of the heading drop down for the existing line appears as soon as user clicks on Edit-beta and this bug does not occur there.",1383156544,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,"note that this action also seems to incorporate a BACKSPACE action as well, since the cursor ends on the same vertical axis as it begins",1383060777,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,"**Author:** `Wikifram`
+
+**Description:**
+This test edit[https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=809490&oldid=795427]: all I did was add [[Test]] at the end of the sentence (to check basic nowiki functionality in the new release 23). However, VE started moving the nowikis around, and now the ref, which was in the old diff a nice ""1"", is now a strange string, ""UNIQ74171d8572aa65a1-nowiki-00000018-QINU1UNIQ74171d8572aa65a1-nowiki-00000019-QINU"". This will probably be a rare occurrence, so not urgent in that regard, but it may be indicative of other problems.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382974020,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3et3rxfdnnlv6panz53k,task_description,resolved
+VisualEditor: Prevent application of link annotations to references,"Change 96238 merged by jenkins-bot:
+Prevent link-annotating MWReferences
+
+https://gerrit.wikimedia.org/r/96238",1384858902,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,"Change 96238 had a related patch set uploaded by Esanders:
+Prevent link-annotating MWReferences
+
+https://gerrit.wikimedia.org/r/96238",1384858734,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,"Otherwise, output is ill-defined (UNIQ bug) and not good for users.
+
+(Thought there was an existing bug, but couldn't find it.)",1384857259,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,*** Bug 56751 has been marked as a duplicate of this bug. ***,1383870381,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,"**Wikifram** wrote:
+
+Note that when you open the page in VE mode, it again displays the ref correctly. Strange... 
+
+Note also that a much simpler version, a link with a ref in the link, has the same behaviour, so the ""nowikis"" are probably only a distraction and this may more serious than I first thought...[https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=809494&oldid=809493]",1382974276,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Vertical keyboard selection (shift+up/down cursor) over a node type boundary gives unexpected results in Firefox,"**Author:** `Wikifram`
+
+**Description:**
+I had entered this at enwiki VisualEditor/Feedback, but got no response. Apparently no bug for this has been filed, even though it is quite serious. All links are for pages on enwiki. 
+
+I'm trying to select one template, but get unexpected results. If you go to [[Karl Popper]], put the cursor at the start of the header ""Backdrop to his thought"", and use the left side ""caps arrow"" plus the up-arrow from the four direction arrows (to select the line above it), the first time you do this, your cursor disappears. The second time, you select everything including half a line of the paragraph ''above'' the ""philosophy"" section header, the philosophy section header, and the ""main"" template. This is rather unexpected. 
+
+Similarly, only using the ""up"" arrow, starting again at the same place: first time, the cursor seems to disappear (looking more closely, it stands at the right side of the infobox, at the height of the ""main article"" template. Using it again movs it to the middle of the last line of the previous paragraph, skipping the template and the ""philosophy"" section header. 
+
+The reverse is even worse. Starting from the paragraph above the ""philosophy"" header and using the ""down"" arrow, your cursor moves to the end of the ""philosophy"" header (good!); using ""down"" again, it moves to the right of the infobox (at the same line as the ""main article"" template) (not good, perhaps acceptable); using down again, and again, and again, does absoluetly nothing anymore... 
+
+Stranger and stranger: going from the ""philosophy"" header using the right button works like a charm. If you then start using the ""up"" arrow though, you are no longer scrollong inside the text, but yo uare scrolling the whole webpage instead... I stopped testing after this, having had more than enough of this!
+
+Basically, the use of arrows in VE shows some very bizarre behaviour and should be thoroughly tested and bugfixed. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 15:02, 25 October 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51957",1382972940,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-iu6hbgjioqo5cvt23aal,task_description,resolved
+VisualEditor: Vertical keyboard selection (shift+up/down cursor) over a node type boundary gives unexpected results in Firefox,"As far as I can tell these were solved when we switched up/down behaviour with regard to browser-native selections. There are some issues in this area, but this ticket doesn't capture them.",1420844427,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iu6hbgjioqo5cvt23aal,task_subcomment,NA
+VisualEditor: Vertical keyboard selection (shift+up/down cursor) over a node type boundary gives unexpected results in Firefox,"1) I can reproduce the odd two-step up-arrow selection bug in Firefox, but not in Chrome. I couldnt quickly see that bug raised.
+
+2) Likewise the down-arrow selection problem is also Firefox only, and appears to be bug 51957
+
+3) The arrow-page-scroll-down bug is also Firefox only. I couldnt find a bug for it, but it is similar to bug 53420",1383177503,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-iu6hbgjioqo5cvt23aal,task_subcomment,NA
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Perceived performance could be substantially improved by having VisualEditor optimistically request serialization of the DOM as soon as the user hits ""Save page"". If the user ends up canceling the save, the serialized DOM would be discarded.
+
+Users that take a few seconds to write the edit summary before confirming the save would experience near-instant saves this way.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55979",1382470140,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_description,resolved
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Change 93934 merged by jenkins-bot:
+Use serialization cache in MW integration
+
+https://gerrit.wikimedia.org/r/93934",1385139189,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_subcomment,NA
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Change 93109 merged by jenkins-bot:
+Implement serialization cache in VisualEditor API
+
+https://gerrit.wikimedia.org/r/93109",1385138385,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_subcomment,NA
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Change 93934 had a related patch set uploaded by Catrope:
+[WIP] Use serialization cache in MW integration
+
+https://gerrit.wikimedia.org/r/93934",1383727786,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_subcomment,NA
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Change 93109 had a related patch set uploaded by Catrope:
+Implement serialization cache in VisualEditor API
+
+https://gerrit.wikimedia.org/r/93109",1383341741,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_subcomment,NA
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Previewing a page and then saving it without further modifications should result in one serialization request being made to Parsoid, not two. The serialized DOM generated in course of responding to the preview request should be re-used when saving whenever VisualEditor can determine that no modifications intervene these two operations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56011",1382397660,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-4e57g4ptze3lbabyzrzu,task_description,resolved
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Change 93934 merged by jenkins-bot:
+Use serialization cache in MW integration
+
+https://gerrit.wikimedia.org/r/93934",1385139192,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4e57g4ptze3lbabyzrzu,task_subcomment,NA
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Change 93109 merged by jenkins-bot:
+Implement serialization cache in VisualEditor API
+
+https://gerrit.wikimedia.org/r/93109",1385138382,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4e57g4ptze3lbabyzrzu,task_subcomment,NA
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Change 93934 had a related patch set uploaded by Catrope:
+[WIP] Use serialization cache in MW integration
+
+https://gerrit.wikimedia.org/r/93934",1383727790,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4e57g4ptze3lbabyzrzu,task_subcomment,NA
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Change 93109 had a related patch set uploaded by Catrope:
+Implement serialization cache in VisualEditor API
+
+https://gerrit.wikimedia.org/r/93109",1383341746,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4e57g4ptze3lbabyzrzu,task_subcomment,NA
+VisualEditor: An empty edit notice is appearing at every page,"An empty edit notice is now appearing on any page.
+
+Tested on Firefox and Safari
+
+https://en.wikipedia.org/wiki/LibreOffice?veaction=edit
+https://en.wikipedia.org/wiki/Maxi_single?veaction=edit
+https://en.wikipedia.org/wiki/Northeim?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1382307480,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-hha36vju233upi7kw3se,task_description,resolved
+VisualEditor: An empty edit notice is appearing at every page,"Only a problem for sysops – a regression in bug 43013's fix.
+
+*** This bug has been marked as a duplicate of bug 43013 ***",1394495869,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hha36vju233upi7kw3se,task_subcomment,NA
+VisualEditor: An empty edit notice is appearing at every page,"On pages that do have a notice displayed (e.g. those that are semi-protected) the empty page notice is noted as a second message, but one that it is impossible to view. 
+
+Firefox 24.0/Monobook/Linux observed at [[Tycho Brahe]]",1382877359,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hha36vju233upi7kw3se,task_subcomment,NA
+VisualEditor: An empty edit notice is appearing at every page,Also confirmed on Chrome.,1382308295,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-hha36vju233upi7kw3se,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it","Intention:  Add a parameter to a template.
+
+
+Expectation:  That the cursor would automatically be present in the ""Add parameter"" text field (where it says ""Parameter name""), so we could just start typing without having to reach for the mouse.
+
+
+Steps to reproduce and results:
+
+1)  Add or open any template.
+
+2)  Start typing the name of a parameter.
+
+3)  Discover that you are no longer able to just start typing the name, but must first reach for the mouse or trackpad, and then click to put the cursor inside the only possible place where you might be typing on that screen.
+
+
+This was reported as a new and undesirable behavior with MediaWiki version 1.22wmf21, by a user who normally uses Firefox 24, Windows 8 and Vector skin and confirmed in Safari 6 on a Mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382221620,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_description,resolved
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it",Works for me!  Thanks.,1407176685,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it","Change 148233 merged by jenkins-bot:
+Auto-open ""Add parameter"" part of template dialog when tabbed to or opening with no required/suggested params
+
+https://gerrit.wikimedia.org/r/148233",1406072263,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it","Should be done now. WhatamIdoing, feel free to reopen this if you disagree",1406072223,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it","Change 148233 had a related patch set uploaded by Alex Monk:
+Auto-open ""Add parameter"" part of template dialog when tabbed to or opening with no required/suggested params
+
+https://gerrit.wikimedia.org/r/148233",1405977031,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it",Changing this bug slightly to fit the current situation with tab indexes.,1405973106,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When a template is completely empty, it is invisible in CE","This bug came about from a misspelled parameter in a template on hewiki. The template returned a completely empty result when the required parameter was invalid, and there was no place to hover above the template and access the transclusion icon to change or remove it.
+
+To replicate:
+* Go to https://he.wikipedia.org/wiki/%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%D7%AA:Mooeypoo/%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99/%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_%D7%95%D7%9E%D7%A9%D7%97%D7%A7%D7%99%D7%9D?veaction=edit
+* Click on transclusion, and add the template ""ערך מורחב""
+* Add parameter with the name ""1""
+* Add value to the parameter (invalid value) - ""[[blah]]""
+* Apply and click anywhere else on the document to clear the selection - the template vanished. However, it was added to the wikitext and is in the page after save, but there's no way to access it from VisualEditor and remove it (or edit it)
+
+I have an idea on how to solve that, but I am not sure if the issue isn't deeper.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381957920,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-r3eqg73n7uhflvgw7eg3,task_description,resolved
+"VisualEditor: When a template is completely empty, it is invisible in CE","Change 90210 merged by jenkins-bot:
+Add a placeholder into an empty transclusion
+
+https://gerrit.wikimedia.org/r/90210",1382982138,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r3eqg73n7uhflvgw7eg3,task_subcomment,NA
+"VisualEditor: When a template is completely empty, it is invisible in CE","Change 90210 had a related patch set uploaded by Catrope:
+Adding a placeholder into an empty transclusion
+
+https://gerrit.wikimedia.org/r/90210",1381962383,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r3eqg73n7uhflvgw7eg3,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize","If you have a right-floating image, select it by clicking on it, then make the window wider on the right-hand size, the image moves to the right but the highlight doesn't. Same goes for resize handles etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55787",1381931100,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_description,resolved
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize",At least the first part of this is done.,1402446907,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize","Change 134363 merged by jenkins-bot:
+[BREAKING CHANGE] Merge ProtectedNode into FocusableNode
+
+https://gerrit.wikimedia.org/r/134363",1402442357,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize","Change 134363 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Merge protected node into focusable node
+
+https://gerrit.wikimedia.org/r/134363",1400695942,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize","The video capture for bug 62632 shows this effect:
+ http://cl.ly/0g2F0q2D3p1D",1394758925,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize",*** Bug 60701 has been marked as a duplicate of this bug. ***,1394128066,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'clearMessage'
+
+Appears to be thrown by line 792 of modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.js: 'this.clearMessage( 'captcha' );'.
+
+Seen on MediaWiki.org after trying to solve a Captcha, in the process of saving an edit to <https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team/Quarterly_review%2C_October_2013>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381818480,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-omdhcpi6if5gftpy7523,task_description,resolved
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""",Now cherry-picked to live.,1381879688,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Change 89794 merged by jenkins-bot:
+'clearMessage' is a method of MWSaveDialog, not ViewPageTarget
+
+https://gerrit.wikimedia.org/r/89794",1381878154,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Change 89794 had a related patch set uploaded by Catrope:
+'clearMessage' is a method of MWSaveDialog, not ViewPageTarget
+
+https://gerrit.wikimedia.org/r/89794",1381834894,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Change 89773 merged by jenkins-bot:
+'clearMessage' is a method of MWSaveDialog, not ViewPageTarget
+
+https://gerrit.wikimedia.org/r/89773",1381834542,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Change 89773 had a related patch set uploaded by Krinkle:
+'clearMessage' is a method of MWSaveDialog, not ViewPageTarget
+
+https://gerrit.wikimedia.org/r/89773",1381834425,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Cause an exception from something with call_user_func in its stack.
+
+For example, if you use wfUseMW( '2000.0' ); inside VisualEditor::onSetup (wgExtensionFunctions), you get:
+
+
+
+Notice: Undefined index: file in /includes/Exception.php on line 725
+Notice: Undefined index: line in /includes/Exception.php on line 725
+Notice: Undefined index: file in /includes/Exception.php on line 725
+Notice: Undefined index: line in /includes/Exception.php on line 725
+
+MediaWiki 2000.0 required--this is only 1.22alpha
+
+Backtrace:
+
+#0 /extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW('1.229wmf11')
+#1 (): VisualEditorHooks::onSetup()
+#2 /includes/Setup.php(592): call_user_func('VisualEditorHooks::onSetup')
+#3 /includes/WebStart.php(153): require_once('/includes/Setup.php')
+#4 /index.php(46): require('/includes/WebStart.php')
+#5 {main}
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal",1381515180,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ebmnnccanbjpovnhy3nw,task_description,resolved
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Change 90067 abandoned by Dereckson:
+Fixes stacktrace output when an internal function is called.
+
+Reason:
+As the information isn't pertinent to the exception position.
+
+https://gerrit.wikimedia.org/r/90067",1382948111,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)",*** Bug 55479 has been marked as a duplicate of this bug. ***,1381881831,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Change 90067 had a related patch set uploaded by Dereckson:
+Fixes stacktrace output when an internal function is called.
+
+https://gerrit.wikimedia.org/r/90067",1381881576,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)",*** Bug 55479 has been marked as a duplicate of this bug. ***,1381880536,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Change 89243 merged by jenkins-bot:
+exception: Account for $call['file'] and $call['line'] being unset
+
+https://gerrit.wikimedia.org/r/89243",1381517453,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","(In reply to comment #0)
+> Notice: Undefined index: file in /includes/Exception.php on line 725
+> Notice: Undefined index: line in /includes/Exception.php on line 725
+> Notice: Undefined index: file in /includes/Exception.php on line 725
+> Notice: Undefined index: line in /includes/Exception.php on line 725
+> 
+> MediaWiki 2000.0 required--this is only 1.22alpha
+> 
+> Backtrace:
+> 
+> #0 /extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW('1.229wmf11')
+> #1 (): VisualEditorHooks::onSetup()
+> #2 /includes/Setup.php(592): call_user_func('VisualEditorHooks::onSetup')
+> #3 /includes/WebStart.php(153): require_once('/includes/Setup.php')
+> #4 /index.php(46): require('/includes/WebStart.php')
+> #5 {main}
+
+
+New output after the patch:
+
+#0 /extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW('1.229wmf11')
+#1 {internal}: VisualEditorHooks::onSetup()
+#2 /includes/Setup.php(592): call_user_func('VisualEditorHooks::onSetup')
+#3 /includes/WebStart.php(153): require_once('/includes/Setup.php')
+#4 /index.php(46): require('/includes/WebStart.php')
+#5 {main}",1381515709,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Change 89243 had a related patch set uploaded by Krinkle:
+exception: Account for $call['file'] and $call['line'] being unset
+
+https://gerrit.wikimedia.org/r/89243",1381515507,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Upstream bug:
+
+https://bugs.php.net/bug.php?id=64987",1381515247,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,"Problems:
+* The dm.Surface constructor initializes the selection at (1,1) because (0,0) is not a selection we can render in most documents
+* ui.Surface.initialize has the following code:
+// By re-asserting the current selection and forcing a poll we force selection to be something
+// reasonable - otherwise in Firefox, the initial selection is (0,0), causing bug 42277
+this.model.getFragment().select();
+this.view.surfaceObserver.pollOnce();
+* However, when VE loses focus then regains focus, we don't restore the selection
+
+Issues caused:
+* Selections of (1,1) don't play nice with documents that start with a FocusableNode
+* The fact that ui.Surface.initialize reasserts the selection means that VisualEditor focuses itself on initialization, which Flow is now having to work around
+* When ULS blurs then refocuses VE during its initialization, the selection jumps back to the top
+
+What we should really be doing:
+* Initialize the selection at the first content offset (this is 1 for most documents, but will be different for documents that start with a FocusableNode)
+* Get rid of the model->view->model circular synchronization in ui.Surface.initialize and fix whatever problems it fixed differently
+* Restore selection on focus
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381324560,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_description,resolved
+VisualEditor: Get rid of selection rendering on init,"(In reply to Roan Kattouw from comment #4)
+> (In reply to Ed Sanders from comment #3)
+> > I certainly addressed point 1 of Roan's list of actions, he may want to
+> > follow up on 2 & 3.
+> I did 3 a while ago. As for 2, I don't know how current that is, let me take
+> a look.
+Nope, 2 seems to be gone. So this bug is fixed completely then.",1393456056,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,"(In reply to Ed Sanders from comment #3)
+> I certainly addressed point 1 of Roan's list of actions, he may want to
+> follow up on 2 & 3.
+I did 3 a while ago. As for 2, I don't know how current that is, let me take a look.",1393455953,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,"I certainly addressed point 1 of Roan's list of actions, he may want to follow up on 2 & 3.",1391716824,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,This was fixed some time ago by Ed.,1391663171,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,"Is this the bug that causes templates to be pre-selected upon loading the editor?
+
+Is this the bug that is resolved when the editor just places the cursor (""collapsed"" selection) at the visual start of the document (e.g. not selecting the first template or character, but before it, blinking on the top left).",1383075174,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Right now we emit both 'live' and 'setup'/'teardown' , and some classes listen to 'live' while others use 'setup'/'teardown'. We should converge on using setup/teardown and remove live.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381315200,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pbmmp535m2nwlycrbccu,task_description,resolved
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Change 144634 merged by jenkins-bot:
+Deprecate 'live' event in favor of 'setup' and 'teardown' in MW
+
+https://gerrit.wikimedia.org/r/144634",1406072200,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pbmmp535m2nwlycrbccu,task_subcomment,NA
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Change 144586 merged by jenkins-bot:
+Deprecate 'live' event in favor of 'setup' and 'teardown'
+
+https://gerrit.wikimedia.org/r/144586",1406072089,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pbmmp535m2nwlycrbccu,task_subcomment,NA
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Change 144634 had a related patch set uploaded by Mooeypoo:
+Deprecate 'live' event in favor of 'setup' and 'teardown' in MW
+
+https://gerrit.wikimedia.org/r/144634",1404794231,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pbmmp535m2nwlycrbccu,task_subcomment,NA
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Change 144586 had a related patch set uploaded by Mooeypoo:
+Deprecate 'live' event in favor of 'setup' and 'teardown'
+
+https://gerrit.wikimedia.org/r/144586",1404769146,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pbmmp535m2nwlycrbccu,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"Tested on both the Italian and the English Wikipedia a few days ago;
+Reach the bottom of any page: the link inspector does not present the
+list of options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55343",1381236120,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_description,resolved
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"I believe that this is now fixed, at least as far as I can tell.",1402549384,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"Yup, I can reproduce this now. It looks like in some cases, the selection dropdown isn't shown properly, it retains display:none; and height:0; (but the suggestions are there, I can see them in the DOM inspector). I think this may have to do with the unreliable behavior of nested .show() calls in jQuery in Firefox: I've observed that sometimes, calling .show() on a container doesn't immediately cause its children to evaluate as visible, which means that calling .show() on those children is a no-op because .show() refuses to touch things whose parent is hidden. The height:0 is likely due to trying to measure a hidden element.
+
+CC Trevor.",1381243824,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"Roan: right now in that page, if I click on ""California"", I get a ""page found"" text and two arrows which allow me to scroll a list of alternatives (which do not look handy since they only allow to preview one line at a time).
+A few lines below, if I click on ""architettura moderna"", I don't get alternatives.
+If I write somewhere, say, ""USA"" and try to make it a link, that will work, but I still don't get to decide which page the link should point at.
+In FF, it doesn't work with Vector. It's both browser and skin specific, for me.",1381243086,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"I can confirm this bug on en.wp, but not on nn.wp or mediawiki.org",1381241141,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"I tried reproducing this on http://it.wikipedia.org/wiki/San_Francisco in both Firefox and Chrome, but both editing existing links and adding new links works for me.",1381236525,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"(Please scratch the bottom of the page part, it doesn't work anywhere).",1381236267,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Filing this since subbu wanted to take a closer look (""Yes, VE/Parsoid shouldn't be making dirty diffs -- and these kind of dirty diffs is an exception rather than the rule. This is a bug.""):
+
+<<VE seems to make unnecessary changes. I wouldn't mind so much if it always helped to maintain the layout of invisible elements, but normally it just screws them (like infoboxes, or position of templates), without any effect on the rendered page but with a less easily readable wikitext editing window.
+What I notice now though are totally unnecessary and hard to explain changes to ref names. For some reason, VE decides that all ref names need to be in quotes, which is not true at all and doesn't help one bit. It also decides that between the final quote and the forward slash, there needs to be a space. All this has no effect on the rendered page, and doesn't make the wikitext page any easier (or harder) to read, so why does VE bother doing this, which only helps to make diffs a lot longer.
+Take a look at e.g. [10]: can you easily see if any significant change has been made, and what that may be?
+First difference; <ref name=""globsec-arjun""/> becomes 
+<ref name=""globsec-arjun"" /> Further: <ref name=nomorearjuns> becomes <ref name=""nomorearjuns"">
+and so on. I have not found the actual significant difference between the old and new version. What is the purpose and benefit of this? If VE would always make the ""invisible"" layout clearer and better, fine, but VE doesn't care one bit about wikitext layout, so I don't get this useless editing. Fram (talk) 09:27, 7 October 2013 (UTC)>>
+
+https://en.wikipedia.org/w/index.php?title=Arjun_%28tank%29&curid=7648336&diff=576092971&oldid=575064244
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381222380,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_description,resolved
+Quotes and whitespace normalized in unedited <ref> tags,"Closing this task since there is nothing much more to be done here since we cannot protect against varnish cache failures -- these should be a fairly rare occurrence. Once we move to RESTbase, this should not happen anymore.",1418854972,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,This is still happening regularly.  Another example is at  https://en.wikipedia.org/w/index.php?diff=629369061,1413311064,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Another one, found while looking at diffs after the deploy of d51e64097:
+https://fr.wikipedia.org/w/index.php?title=Cendrillon_(Disney)&curid=3040885&diff=105440424&oldid=104520814",1405370096,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Here's another diff that is probably the same bug:
+
+https://en.wikipedia.org/w/index.php?title=Rights&curid=51490&diff=603988349&oldid=601154438
+
+In this one, an oddly named-but-unnamed ref tag (<ref name="""">) has its whitespace normalized.",1398219709,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"This is just a note that Bug 64197, merged here, is about {{sfn}} templates, which sort of are and sort of aren't ref tags.  See https://en.wikipedia.org/w/index.php?title=Jack_Parsons_%28rocket_engineer%29&diff=604788783&oldid=604787564",1398135489,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,*** Bug 64162 has been marked as a duplicate of this bug. ***,1398116545,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,*** Bug 64197 has been marked as a duplicate of this bug. ***,1398116521,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+I've reopened this, since it appears that this still happens: [https://en.wikipedia.org/w/index.php?title=Triceratops&curid=54410&diff=584366006&oldid=584365568]",1386082882,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"I believe this was fixed by 67fca5bdc7 and 923c79102a.
+
+These test cases from comments above now round-trip fine:
+
+* comment #1: https://en.wikipedia.org/wiki/User:Gwicke/Test/Arjun_%28tank%29
+* comment #4: https://en.wikipedia.org/wiki/User:Gwicke/Test/Wrestler
+* comment #8: https://en.wikipedia.org/wiki/User:Gwicke/Test/Gray_wolf
+
+Please reopen if this problem still exists.",1386032944,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,The diff in comment #10 might have been caused by an unrelated issue with one of the Varnish caches in production.,1384823693,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"This last diff seems to have happened in the context of some error the editor encountered. Recording here for further debugging.
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=581952520#Error:Unknown_error",1384788280,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+Still happened on the 16th: [https://en.wikipedia.org/w/index.php?title=KLM&diff=581951122&oldid=581950935]",1384762981,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Yes, those were probably from cache misses. We deployed newer code y'day that should eliminate these unrelated normalizations in most cases (barring bugs). 
+
+Note however that if a <ref> is edited, Parsoid will still normalize the quotes and whitespace in the attributes of the edited ref.
+
+Let us wait for a week to see if we still see unrelaed normalizations and if not, close this as resolved.",1384476665,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+Not just the quotes, also the additional spaces: [https://en.wikipedia.org/w/index.php?title=Gray_wolf&curid=33702&diff=581450926&oldid=581450732] I can't judge whether this is fixed on most pages or not, but it certainly seems to happen quite reguilarly still.",1384334252,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+...still happens apparently: [https://en.wikipedia.org/w/index.php?title=New_%28album%29&diff=581113730&oldid=581109664] (noted by another editor on [[en:WP:VEF]])",1384264390,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"New code has been deployed with a bunch of fixes related to cache misses that would cause Parsoid to run the regular serializer on the entire dom. This should fix this issue on most pages. 
+
+We'll also make some fixes to minimize dirty diffs even when there is a cache miss -- we've identified some improvements we could make to the DOM diff algorithm.",1383892788,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,The new code I mentioned in #c3 hasn't been deployed to production yet. Will update this ticket when that happens.,1383836080,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+It seems that quotes are still being added to ref tags as of today: [https://en.wikipedia.org/w/index.php?title=Sting_%28wrestler%29&curid=655575&diff=580574777&oldid=580516764]",1383827570,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Gabriel and I now think this happened when Parsoid incurred a cache miss for the HTML (rare) and also suffered a timeout on reparsing (possible on large pages since we had a timeout of 16 sec). But, a couple commits today should address this and further reduce the likelihood of selser not getting triggered on the edit.
+
+The relevant commits are:
+
+1. https://gerrit.wikimedia.org/r/#/c/93896/ (increases cache timeout to 60 sec)
+2. https://gerrit.wikimedia.org/r/#/c/93902/ (improves parse time when selser suffers a cache miss fetching original HTML).",1383716659,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,This seems to be related to bugs in selser (Parsoid) when a cache URL is set. I've set a cache URL locally and will investigate.,1383702057,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Yup, that's a bug. VE should not be normalizing <ref name=""globsec-arjun""/> to <ref name=""globsec-arjun"" /> nor should it be normalizing <ref name=nomorearjuns> to <ref name=""nomorearjuns"">.
+
+Since the revision wasn't tagged with the visualeditor-check tag, VE didn't detect any corruption on its end, which makes me suspect that this is a Parsoid bug.",1381222931,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+mediawiki.notification: div#mw-notification-area remains visible and steals events after dismissing notification,"1. Trigger a notification
+2. Click on the notification to dismiss it
+3. The notification area (<div id=""mw-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.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381220760,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-trd3quxv62oo47pm6dey,task_description,resolved
+mediawiki.notification: div#mw-notification-area remains visible and steals events after dismissing notification,"Wrong bug, sorry
+
+*** This bug has been marked as a duplicate of bug 52659 ***",1409942617,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-trd3quxv62oo47pm6dey,task_subcomment,NA
+mediawiki.notification: div#mw-notification-area remains visible and steals events after dismissing notification,"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",1409942562,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trd3quxv62oo47pm6dey,task_subcomment,NA
+mediawiki.notification: div#mw-notification-area remains visible and steals events after dismissing notification,"All you VE guys really should start looking through bugs that are already reported instead of adding more copies.
+
+*** This bug has been marked as a duplicate of bug 52659 ***",1381254044,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-trd3quxv62oo47pm6dey,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"1. Edit a page with VisualEditor.
+2. Copy a line of text.
+
+Sometimes it just copies the line to the clipboard without generating any move of the content (expected behavior). But sometimes just by typing ctrl-C with text selected you will see a jump of the page.
+
+I haven't found the pattern, but it looks like doing this close to the end of long pages makes it easier to reproduce.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381170060,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-pkufios4crste37qzbra,task_description,declined
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,Can't reproduce any of the issues described in this bug.,1409070789,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"Using *any* means of copying text is making the ctrl/cmd key cause a page to jump up, not just ctrl-c/cmd-c, in Firefox. Right-click and select ""Copy"" and the same thing happens to the ctrl/cmd key. I cannot replicate this in Chrome.
+
+Using Firefox 30:
+1. Open any article of reasonable length to edit in VisualEditor, let's say 
+https://en.wikipedia.org/wiki/Cat?veaction=edit
+2. Scroll down to the middle of the article, select any portion of text, and copy it by either ctrl-c/cmd-c *or* right-clicking on the section with the mouse and selecting copy, without using a keyboard shortcut at all.
+3. Now press your control or command key while the selected text is still highlighted. It now functions as an ""up"" button.
+4. Deselect the text that you have copied and function returns to the control/command.",1404773952,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"Well, the problem also encountered on this page: 
+https://cs.wikipedia.org/wiki/Seznam_lid%C3%AD%2C_kte%C5%99%C3%AD_byli_zabiti_b%C4%9Bhem_Euromajdanu
+
+E.g. when copy&pasting ""."" between rows it also jumps. Problem confirmed in:
+*FF 27 safe mode
+*FF 27.0.1
+*FF 27.0.1 logged of
+
+In Google Chrome 33.0.1750.117 m it jumps and paste sometimes and just once. In IE 7 VE doesnt work at all.",1393311981,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"OK I tried FF 27 and safe mode and I have discovered that problem comes when there are empty list items in undordered list. E.g. If I have:
+
+
+*M. auricantha R.T. Craig
+*M. auritricha R.T. Craig
+*
+*
+*M. canelensis R.T. Craig
+*M. hertrichiana R.T. Craig
+*M. lindsayi R.T. Craig
+
+And I select whatever string on that page and type CTRL+C it ""jumps""
+
+Note: to produce empty li is just place cursor on the end of second item and hit several times enter (in this case 2 times).",1392634145,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,Can't reproduce in FF 26. What exact text did you select? Can someone else confirm?,1391609196,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"I am reopening this bug as I am obscuring such behaviour again in FF 26.0 at this page:
+https://cs.wikipedia.org/wiki/Mammillaria_standleyi
+
+Way to reproduce:
+*Select an item in the unsorted list
+*hit CTRL+C
+
+You will see a jump up and down of the page, which is pretty unconfortable during editing.",1391590240,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"Yes, fixed in gerrit 106185 (made avaiable in MW-VE in gerrit change 106731). Marking as such.",1390321343,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"I think Roan put in a fix this a while back, can he confirm?",1390316651,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Opening the drop-down for a category in the page settings > category pane can cause a category entry to be duplicated,"Fram reports:
+<<Having looked a bit more at categories, I encountered another strange phenomenon. On Opel Laubfrosch https://en.wikipedia.org/wiki/Opel_Laubfrosch, which has a lot of categories, the order of the cats on the page settings tab changes. Initially I get 8 categories, from ""Opel vehicles"" to ""compact cars"". But when I e.g. click on the drop down button next to 1920s automobiles, and then click again in the ""categories"" window (to close the drop down without any changes), I get 10 cats instead of 8, and in a different order. ""Vehicles introduced in 1924"" and ""Sedans"" are doubled (explaining the increase from 8 to 10), and the 3rd one is now no longer ""1920s automobiles"" but ""1930s automobiles""... This can go on for quite a while, with the occasional disappearance of a cat as well apparently (normally the last one). Things start to break down, with the page settings then no longer working, or it being no longer possible to add a cat, and so on.>>
+
+I can confirm what he says, and this bug does not look browser or skin specific.
+VE will let you save in a situation where you have these cats duplicated, and a ""saved edit"" message will also pop-up, but there will be no trace of the edit in the history. Plain removal of all the categories works fine instead: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2Fsandbox&diff=576123603&oldid=576122965 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381145460,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-vtu44ya7j43gvaddcjhx,task_description,resolved
+VisualEditor: Opening the drop-down for a category in the page settings > category pane can cause a category entry to be duplicated,"Yeah, I think so.",1408096666,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vtu44ya7j43gvaddcjhx,task_subcomment,NA
+VisualEditor: Opening the drop-down for a category in the page settings > category pane can cause a category entry to be duplicated,Didn't we fix a bug like this recently? Is this still valid?,1408087302,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vtu44ya7j43gvaddcjhx,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Erik Moeller: ""
+I agree with previous commenters that this is likely to be at the cause of a
+lot of the accidental infobox deletions and such. I understand it's a tricky
+issue, but the current behavior is extremely confusing from the user's point of
+view, so we need to look at some viable solutions. 
+
+Recapping the simple case: User is on what they perceive to be an unnecessary
+newline, presses delete to make the visual layout match the expected layout. A
+separate object (in the case of the infobox, right-aligned on the other side of
+the screen) suddenly disappears. This is very surprising and counter-intuitive
+behavior.
+
+Why don't we just suppress the delete key when pressing it would delete the
+object the slug is associated with? In some alternative editors like Google
+Docs, it is actually not possible to nuke the entire document by just pressing
+down the delete key at the top of the page -- it will stop before certain
+objects. I've never had any problems as a result.
+
+That seems like the simplest solution to me and does not require a redesign of
+the slugs.
+""
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1380963660,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nhj52cwstgebwydn6v4r,task_description,resolved
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","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.
+
+This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion.
+
+(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'? I will also copy to bug 55336.",1405114280,PHID-USER-mcyovqjor52nj3se4lq7,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","I'm confirming on http://en.wikipedia.beta.wmflabs.org/wiki/Greg_and_Karen_DeSanto as a test case that this is working as intended. I would encourage others who care about this issue to try as well (note you'll need to login and enable VE, just as you do on en.wp, since Beta has the same config).
+
+One small UX issue I'm noticing is that you can't consistently cursor away from the focusable nodes, which is somewhat exacerbated now that they're more frequently selected as you delete/backspace through content. I suggest tracking that as a separate bug, if it isn't one already.",1381344021,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Change 87666 merged by jenkins-bot:
+Prevent deletion of FocusableNodes from a collapsed selection
+
+https://gerrit.wikimedia.org/r/87666",1381339368,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Yes, anything you can select with a single click (focusable). We could restrict it to non-inline elements but I think it's useful for inline too.",1381297066,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Will this also cause citations and similar inline nodes to be first selected, rather than deleted, when you press backspace or delete next to them? I'm not saying that would necessarily be wrong behavior (I think it could actually be helpful), but just wanted to clarify.",1381286850,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Change 87666 had a related patch set uploaded by Esanders:
+Prevent deletion of FocusableNodes from a collapsed selection
+
+https://gerrit.wikimedia.org/r/87666",1380969114,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","I agree, although I would say instead of suppressing the delete/backspace key, it should cause the adjacent FocusableNode (e.g. Infobox) to become focused, so that a second keypress actually deletes it. This shouldn't be too difficult to achieve.",1380963832,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+VisualEditor: Pawn appears near deleted reference in Firefox,"https://en.wikipedia.org/wiki/Konami_code?veaction=edit , in Firefox.
+Locate the sequence of references [5][6][7][8].
+Delete one of them (not the first one), hit Space, a pawn appears. 
+Easter egg *in* Konami Code!
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54712",1380898980,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-h7awbzyfjip5gjfxifz2,task_description,resolved
+VisualEditor: Pawn appears near deleted reference in Firefox,This too is fixed now.,1406599319,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h7awbzyfjip5gjfxifz2,task_subcomment,NA
+VisualEditor: Pawn appears near deleted reference in Firefox,"James, if it's a dupe, it's still not working.",1380971910,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-h7awbzyfjip5gjfxifz2,task_subcomment,NA
+VisualEditor: Pawn appears near deleted reference in Firefox,"This is actually the same (really terrible) bug as bug 54712, which is thankfully now fixed; merging.
+
+Thanks for reporting it!
+
+*** This bug has been marked as a duplicate of bug 54712 ***",1380936671,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h7awbzyfjip5gjfxifz2,task_subcomment,NA
+VisualEditor: Outer whitespace of first/last node in document not validated,"Because we don't store the inner whitespace of the document, we can't validate the outer whitespace its first/last children.
+
+1. Create document with wikitext:
+==Heading==
+Foo
+2. Delete 'Heading' and the empty line
+3. You now have:
+[{'type':'paragraph', 'internal': {'whitepsace': ['\n']}}, 'F' ....
+in the DM
+4. This serialises to
+\n
+Foo
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380880140,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xooewvbyzadgfzwpxeqt,task_description,resolved
+VisualEditor: Outer whitespace of first/last node in document not validated,"Change 92885 merged by jenkins-bot:
+Store inner whitespace of the body and compare it on conversion
+
+https://gerrit.wikimedia.org/r/92885",1384944306,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xooewvbyzadgfzwpxeqt,task_subcomment,NA
+VisualEditor: Outer whitespace of first/last node in document not validated,"Change 92885 had a related patch set uploaded by Esanders:
+Store inner whitespace of the body and compare it on conversion
+
+https://gerrit.wikimedia.org/r/92885",1383234851,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xooewvbyzadgfzwpxeqt,task_subcomment,NA
+VisualEditor: Outer whitespace of first/last node in document not validated,"**Wikifram** wrote:
+
+Translation for those looking to file a similar bug but no so well-versed in code-speak :-): 
+
+When you have a blank line at the start of an article, before the text of the lead, it is impossible in VE to remove this line or lines. See e.g. [https://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=575706125&oldid=575706080]",1380880521,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xooewvbyzadgfzwpxeqt,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"See test case below. For some reason the <pre> inside the <blockquote> and the p-tag before the blockquote (all of those conditions are necessary to reproduce the bug) is causing the content after the blockquote to not be wrapped in p-tags. See output below. Probably some edge case in the paragraph-wrapping code. 
+
+Based on bug report here:
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=575631753#VE_removing_paragraph_gaps
+
+[subbu@earth lib] cat /tmp/x
+a
+
+<blockquote><pre>
+b
+</pre></blockquote>
+
+c
+
+d
+[subbu@earth lib] node parse < /tmp/x
+<body data-parsoid='{""dsr"":[0,49,0,0]}'><p data-parsoid='{""dsr"":[0,1,0,0]}'>a</p>
+
+<blockquote data-parsoid='{""stx"":""html"",""dsr"":[3,42,12,13]}'><pre data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""strippedNL"":""\n"",""dsr"":[15,29,5,0]}'>
+
+b
+&lt;/pre&gt;</pre></blockquote>
+
+c
+
+d
+</body>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380841560,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-6sni25mbjuiipuy7iv24,task_description,resolved
+Unhandled <pre> tokenizing scenarios in tokenizer,"Change 87632 abandoned by Subramanya Sastry:
+(Bug 54946) Fixed unhandled <pre> tokenizing scenarios
+
+Reason:
+Old and rusty and I am not going to look at this as I originally thought.
+
+https://gerrit.wikimedia.org/r/87632",1400883820,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"Change 92469 merged by jenkins-bot:
+Bug 54946: Alternative solution for <pre> tokenization
+
+https://gerrit.wikimedia.org/r/92469",1383266080,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"Change 92469 had a related patch set uploaded by GWicke:
+WIP Bug 54946: Alternative solution for <pre> tokenization
+
+https://gerrit.wikimedia.org/r/92469",1383007333,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"Change 87632 had a related patch set uploaded by Subramanya Sastry:
+(Bug 54946) Fix unhandle <pre> tokenizing scenarios
+
+https://gerrit.wikimedia.org/r/87632",1380924024,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"This is actually a tokenizer bug. The closing </pre> is not being recognized as an end-tag when a HTML <pre> follows another literal HTML tag on the same line.
+
+Relevent snippet of output for: ""a\n\n<span><pre>\nb\n</pre></span>""
+...
+<span data-parsoid='{""stx"":""html"",""dsr"":[3,28,5,6]}'><pre data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""strippedNL"":""\n"",""dsr"":[8,22,5,0]}'>
+
+b
+&lt;/pre&gt;</pre></span>
+...",1380904499,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"Changing that to ""<blockquote><pre> b </pre></blockquote>"" does not trigger the bug. So, p-tags before blockquote and HTML-pre in blockquote with content on new line puts the p-wrapper in a state where p-tags are not added.",1380841845,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them","De.WP's ref templates interact unhelpfully with VE/Parsoid, resulting in unwanted insertion of ""<ref name="":0"">""; examples:
+
+https://de.wikipedia.org/w/index.php?title=Titl%C3%A1&diff=prev&oldid=122939538
+
+template: https://de.wikipedia.org/wiki/Vorlage:Internetquelle
+
+https://de.wikipedia.org/w/index.php?title=Die_letzte_Vorstellung&diff=prev&oldid=123020177
+
+template: https://de.wikipedia.org/wiki/Vorlage:Der_Spiegel
+
+It also results in having the display of the ref being moved into another ref. This is different from the other issue debated in 53777
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1380837600,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-j7lyujcbs6zaatnh7kya,task_description,declined
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them",Closing unless and until this is shown to still be a problem.,1402003070,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-j7lyujcbs6zaatnh7kya,task_subcomment,NA
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them",Can you provide steps to reproduce?,1391717290,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-j7lyujcbs6zaatnh7kya,task_subcomment,NA
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them","(In reply to comment #1)
+> I'm not sure I understand what the issue is here? Re-used references are
+> getting a name automatically added ("":0"") so that they can be re-used…
+> 
+> Or are they not edits that are intentionally re-using a reference?
+
+First case: The ""Südtiroler Wochenmagazin"" ref eats the newly inserted ref ""ServusTV"", causing a fix:
+
+https://de.wikipedia.org/w/index.php?title=Titl%C3%A1&diff=123114172&oldid=122939538
+
+Second case: The Der Spiegel ref in the second diff doesn't appear in the ref section at the end of the article but gets eaten up by the Die Zeit ref; causing this edit:
+
+https://de.wikipedia.org/w/index.php?title=Die_letzte_Vorstellung&diff=next&oldid=123020177",1380838667,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-j7lyujcbs6zaatnh7kya,task_subcomment,NA
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them","I'm not sure I understand what the issue is here? Re-used references are getting a name automatically added ("":0"") so that they can be re-used…
+
+Or are they not edits that are intentionally re-using a reference?",1380837724,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j7lyujcbs6zaatnh7kya,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"(Second browser-specific - Firefox - bug I file today after 54322).
+It was reported by Fram at en.wp, quickest way to duplicate:
+<<cursor in front of ref, use the ""back arrow"" on your keyboard once (so the ref number gets ""blue""), and type.>>
+
+https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=575562298&oldid=575557792 (with a snowman as well).
+
+More ways:
+<<Type some text, add a ref, remove the ref using backspace, then change your mind and use the ""undo"" arrow of VE. No, change your mind again and use the ""undo"" arrow once more, again removing the ref. Now type. Notice anything strange? Yep, I'm typing backwards. https://en.wikipedia.org/w/index.php?title=User:Fram/sandbox&oldid=575553019
+[...]
+Other tests produced the snowmen, or the insertion of huge chunks of text by VE. https://en.wikipedia.org/wiki/In_My_Dreams_%28Emmylou_Harris_song%29?veaction=edit
+[...]
+Easy way to check the ""backwards typing"": go to https://en.wikipedia.org/wiki/In_My_Dreams_%28Emmylou_Harris_song%29?veaction=edit , put the cursor after ref 1, backspace, undo arrow, type.>>
+
+TeamGale adds:
+<<I tried to reproduce it because I was curious and it's a really weird bug! Although when I put my cursor at the end of the ""backwards typing"" and clicked space, I could type straight again! TeamGale 10:03, 3 October 2013 (UTC)>>
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57600
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61538",1380799920,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-c4mfirb7unow74hkyrys,task_description,resolved
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"Now fixed again, hopefully for good.",1406599273,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,*** Bug 57347 has been marked as a duplicate of this bug. ***,1385472098,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"Still being reported: yesterday, on fr.wp.",1382438555,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"Can now replicate; yes, this is very worrying.",1380909491,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"/me shouts :D
+Still happening with Firefox.",1380881622,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"**Wikifram** wrote:
+
+Not a duplicate and/or not resolved. Please just test whatever has been described before closing bugs, there are too many that need to be reopened. [https://en.wikipedia.org/w/index.php?title=In_My_Dreams_%28Emmylou_Harris_song%29&diff=575692625&oldid=565930941]",1380869618,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"I /think/ this is the same as bug 54712 which we're working on right now and will rush out a live patch - merging the bugs. If it proves otherwise, please shout
+
+*** This bug has been marked as a duplicate of bug 54712 ***",1380835733,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: JavaScript crashes if an invalid keyword is used on an image,"To reproduce, go to the URL ([[User:Amire80/ve-invalid-image-keyword]]). Notice that the save button doesn't appear in the toolbar. The JS console shows the following error:
+
+[15:59:08.469] Error: Offset could not be translated to a DOM element and offset: 3
+
+The reason for this is the invalid keyword ""no_such_keyword"" that I used on the image.
+
+A better behavior would be to show the user some kind of a warning about the wrong keyword, rather than throwing a JS error and crashing.
+
+This bug was discovered by User:Nurick in the Hebrew Wikipedia.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/User:Amire80/ve-invalid-image-keyword?veaction=edit",1380754920,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-tjmyy26tm4c7ectpe3s2,task_description,resolved
+VisualEditor: JavaScript crashes if an invalid keyword is used on an image,"This seems to have occurred because we tried to put the selection inside the image caption, which then caused an error. For whatever reason, this doesn't seem to be happening any more; opening your test page in VE doesn't reproduce the error now.",1388915037,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tjmyy26tm4c7ectpe3s2,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"The Paragraph style tool in toolbar is not working in Firefox most of the time.
+
+Steps to reproduce
+1. https://www.mediawiki.org/wiki/special:random
+2. Active VE (Click 'Edit')
+3. Place cursor on normal text
+
+Expected results:
+The paragraph style selector should change to 'Paragraph'
+
+Actual results (in Firefox 24/linux):
+9 out of 10 times, nothing changes.  The tool does not work at all.  Changing style doesnt work.
+
+This doesnt happen on enwp.
+
+In debug=true mode, the paragraph selector nearly always changes to Paragraph, but sometimes it then doesnt change to Heading if the cursor is moved to a Heading and changing the style doesnt work.
+
+There is nothing in the JS console to suggest what might be the problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1380688320,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_description,declined
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"Can't reproduce either; that's four devs (on various environments) unable to reproduce today, so I'm going to claim that this is fixed.",1393466785,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"Just for good measure, also tested extended-support release which is Firefox 24.3; seems ok there too. Either specific conditions need to trigger this which we aren't hitting, or it's gotten fixed...",1393466680,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,I'm no longer able to reproduce this in Firefox 27.0.1 or Firefox 30 nightly.,1393466075,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"(In reply to comment #2)
+> I believe that this is a regression of sorts:
+> 
+> Behavior 1: 2 click, works
+> 
+> 1. Click tool to open menu
+> 2. Move mouse to item you want to select
+> 3. Click to select item
+>..
+> Can you confirm that Behavior 1 works?
+
+yes, that works.
+ 
+> The only difference between browsers seems to be that on Chrome clicking and
+> dragging doesn't highlight items as you drag over them, but in Firefox it
+> does,
+> which is probably why you were expecting the menu to select the item using
+> click and drag on that browser.
+
+My steps to reproduce dont include any clicking, let alone dragging.  You can reproduce this bug using the only they keyboard.",1380757247,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"I believe that this is a regression of sorts:
+
+Behavior 1: 2 click, works
+
+1. Click tool to open menu
+2. Move mouse to item you want to select
+3. Click to select item
+
+Behavior 2: Click and drag, broken since recent refactor of toolbar
+
+1. Press mouse button down on tool to open menu
+2. Move mouse to item you want to select
+3. Release mouse button to select item
+
+I can confirm that Behavior 2 is broken.
+
+Can you confirm that Behavior 1 works?
+
+The only difference between browsers seems to be that on Chrome clicking and dragging doesn't highlight items as you drag over them, but in Firefox it does, which is probably why you were expecting the menu to select the item using click and drag on that browser.",1380738253,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"Confirmed in Firefox 24 on Mac OS X 10.8.5 -- I had it work once, then not work several times after reloading. Something funky!",1380731980,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+"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",1380573780,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-i27oymi2g7hoildczlee,task_description,resolved
+"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 ***",1380833625,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i27oymi2g7hoildczlee,task_subcomment,NA
+"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.,1380619133,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-i27oymi2g7hoildczlee,task_subcomment,NA
+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",1380325500,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l6lohkvjqdbjrls5sdjz,task_description,resolved
+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 ***",1381157444,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-l6lohkvjqdbjrls5sdjz,task_subcomment,NA
+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",1380324960,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-w6mmcf4y43jmqe4tziga,task_description,resolved
+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",1380557187,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380557130,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380556379,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380556359,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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.",1380481649,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380474667,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380474550,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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?,1380327448,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380326923,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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.",1380325143,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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}",1380310020,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-lj6h46r7rjyl6me5nb7h,task_description,resolved
+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.",1380325542,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lj6h46r7rjyl6me5nb7h,task_subcomment,NA
+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.",1380318521,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-lj6h46r7rjyl6me5nb7h,task_subcomment,NA
+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.",1380311805,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lj6h46r7rjyl6me5nb7h,task_subcomment,NA
+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}",1380295680,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-22klbikg4fmxw7aotqvi,task_description,declined
+VisualEditor: Sometimes the edit link for VE does not appear,No recent reports.,1408096458,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+VisualEditor: Sometimes the edit link for VE does not appear,"Have you seen this issue recently? If not, this could probably be closed...",1408062252,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+VisualEditor: Sometimes the edit link for VE does not appear,*** Bug 60359 has been marked as a duplicate of this bug. ***,1397067449,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+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",1384870240,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+VisualEditor: Sometimes the edit link for VE does not appear,"Created attachment 13393
+Edit link for VE missing in manual operation
+
+**Attached**: {F12180}",1380295721,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+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",1380244140,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ipv73kunpojcr76x2cb7,task_description,resolved
+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",1382541620,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ipv73kunpojcr76x2cb7,task_subcomment,NA
+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",1382383496,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ipv73kunpojcr76x2cb7,task_subcomment,NA
+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.",1380324587,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ipv73kunpojcr76x2cb7,task_subcomment,NA
+VisualEditor: Rendering of <source> MWExtensionNode is empty after the user edits it,"1. Create a page with <source lang=""JavaScript"">some content here</source>
+2. Edit the page in VE. Note that the <source> tag renders correctly
+3. Use the alien tag inspector to edit the contents of the <source> tag
+4. The <source> tag rerenders as an empty block
+
+This is because the HTML <source> tag is self-closing and cannot have any content. This leads to strange situations like:
+
+>>> extensionNode[0]
+<source lang=​""JavaScript"">​whee​</source>​
+>>> extensionNode[0].outerHTML
+""<source lang=""JavaScript""></source>""
+
+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",1380066060,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-k77k35tkwkjkzeravyd3,task_description,resolved
+VisualEditor: Rendering of <source> 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",1385924792,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k77k35tkwkjkzeravyd3,task_subcomment,NA
+VisualEditor: Rendering of <source> 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",1385919115,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k77k35tkwkjkzeravyd3,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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",1379834280,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-v44q2sk65tk423gk2wgc,task_description,resolved
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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).",1381323957,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","(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.",1381245792,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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",1381244614,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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",1381175418,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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 ***",1380836921,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","More from Red Fiona:
+<<If the page already has references, it either doesn't add the reference at all, on this page (https://en.wikipedia.org/w/index.php?title=Vladimir_Gojkovi%C4%87&diff=575208071&oldid=551414203)
+, or adds it as the second reference when it's not really the second reference (https://en.wikipedia.org/w/index.php?title=Nataliya_Pyhyda&diff=575209107&oldid=568886402) .>>",1380645202,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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!!",1380378760,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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}",1379834599,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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}",1379834387,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+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",1379806800,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-trziv3xjwkvokcwfszqm,task_description,resolved
+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",1380668740,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380668726,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,Merged into master; we'll back-port and deploy tomorrow.,1380594405,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380594325,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380594312,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380594298,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380589982,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,*** Bug 54722 has been marked as a duplicate of this bug. ***,1380326222,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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.,1380201051,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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.,1379996431,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1379720640,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-zoji45q564z2zd5mmomf,task_description,resolved
+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.,1386031966,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zoji45q564z2zd5mmomf,task_subcomment,NA
+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]",1379716620,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_description,resolved
+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.",1394719478,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+Parsoid jobs are not dequeued fast enough during heavy editing activity,Can we close this bug now? I believe this has been fixed.,1385464680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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",1380741132,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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. :-(",1380581906,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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",1380575437,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.),1380569455,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.,1380568465,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.,1380568375,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1380568025,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+Parsoid jobs are not dequeued fast enough during heavy editing activity,"Created attachment 13412
+Screenshot to accompany comment 3
+
+**Attached**: {F11775}",1380567824,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379977861,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379920225,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?",1379919819,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379919581,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?,1379919308,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?",1379919266,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379918396,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379916365,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379909439,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379899091,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379897340,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?",1379896974,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379880448,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379835104,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379834310,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379792185,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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""?",1379789440,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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).",1379788021,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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).",1379787771,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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}",1379780486,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+Parsoid jobs are not dequeued fast enough during heavy editing activity,"Created attachment 13342
+Screenshot to accompany comment 2
+
+**Attached**: {F11772}",1379780363,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379774099,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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...",1379755583,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379754279,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?",1379751042,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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'"".",1379717174,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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)",1379716743,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+"VisualEditor: Right half of toolbar disappears when <center> or <div align=""center""> appears in image on first line of page","When a page has an image on the first line and the image caption contains a <center> tag or a <div align=""...""> 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, <p align=""center""> 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",1379688840,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fl7p4f543bjhpoylmcxl,task_description,resolved
+"VisualEditor: Right half of toolbar disappears when <center> or <div align=""center""> appears in image on first line of page","This was fixed some time ago, I believe; sorry for the very slow triage.",1393531314,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fl7p4f543bjhpoylmcxl,task_subcomment,NA
+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",1379685180,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rjymkq6lc7hubjand5ea,task_description,resolved
+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",1379977305,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rjymkq6lc7hubjand5ea,task_subcomment,NA
+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",1379688103,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rjymkq6lc7hubjand5ea,task_subcomment,NA
+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",1379607000,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-zlvsszagknsbory2w3zc,task_description,resolved
+VisualEditor: Surface isn't updated properly for Language annotations,This was fixed in gerrit 90957.,1382644915,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zlvsszagknsbory2w3zc,task_subcomment,NA
+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.",1379642223,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-zlvsszagknsbory2w3zc,task_subcomment,NA
+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]]<nowiki />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",1379605860,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aaouxso4nhg5xgscmdmm,task_description,resolved
+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",1380583290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"btw, the <nowiki/> is inserted by Parsoid to make sure the document we have (<a>Foo/a>ish<a>?</a>) is translated properly into what the PHP parser understands as by default the PHP parser treats ""<a> + adjecent text"" as a shortcut to extend the lable (e.g. [[book]]s becomes <a href=""book"">books</a>).",1380283588,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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",1380277908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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.",1380065635,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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.]] .",1379618394,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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.",1379616875,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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.)",1379615722,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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]]<nowiki />ish[[Wikipedia|?]]
+
+(In reply to comment #1)
+> I think you mean bug 51442
+
+I do. Dyslexia strikes again :(",1379606657,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,I think you mean bug 51442,1379606464,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Firefox,"Current VisualEditor-Version:
+commit c98a964d5f8495f0d16af9229abbeb0449042d1e
+Merge: 3d01a5b e7aed52
+Author: jenkins-bot <jenkins-bot@gerrit.wikimedia.org>
+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",1379594760,PHID-USER-26asvhtv4jalaeeuigbm,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_description,resolved
+VisualEditor: [Regression] Page settings dialog broken in Firefox,Have split the new failure into bug 54928 and am re-closing this one.,1380823394,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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",1380823156,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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.",1380822772,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Firefox,"Confirmed:
+
+* Working on latest master locally (Chrome).
+* Broken on mediawik.org (Chrome).",1380818645,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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:
+<<Just wanted to ask...how can we add categories with VE? In the past I could do it by clicking on ""Page settings"" but now when I click on it nothing happens! Is there somewhere else a button that adds categories? I searched everywhere but I can't find it. If it's still on the ""Page settings"" then something is not working right... Thanks TeamGale 09:54, 3 October 2013 (UTC)>>
+
+Fram tested as well:
+
+<<Tested this. FIrst click on ""page settings"" gives no results. Second click opens the page setting window. But I can't do anything there.>>
+
+I can confirm that the second click just launches an empty window, with only the ""categories"" label text on the left column.
+
+<<Actually this one with the categories is happening for a while for me. Just when I first found it I was in a hurry and couldn't leave a feedback. Then I totally forgot about it till now that I needed to use it again. It's weird that no one else mentioned it here before though.
+Elitre, I don't know if it's a cache problem but I'll try to clean my cache again and re-test it. But the ""after a few attempts"" is still not right for me. Shouldn't this happening in the first attempt? TeamGale 10:12, 3 October 2013 (UTC)
+Update: Nop, still happening the same for me even if I clean cache, cookies etc... TeamGale 10:20, 3 October 2013 (UTC)
+Hmm...it seems to be only a Mozilla issue. I just tried it with Mozilla on Greek WP and it still doesn't work. But when I tested it on Google, it was working just fine. TeamGale 11:00, 3 October 2013 (UTC)>>",1380799304,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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.",1380001984,PHID-USER-26asvhtv4jalaeeuigbm,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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",1379963945,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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",1379959272,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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,",1379595471,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+"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",1379589060,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-equ6rehqzaorfkk3nuw5,task_description,resolved
+"VisualEditor: A pawn appears when undoing ""select transclusion and replace with text""","This is now fixed, AFAICS. Marking as such.",1380844698,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-equ6rehqzaorfkk3nuw5,task_subcomment,NA
+VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,"From en.wp.
+
+John Broughton: <<So there is now a new toolbar, and - bizarrely - the icons for media, reference, reference list, and transclusion '''are no longer visible'''. They are now under the ""More"" menu.
+Okay, one could argue that these four are, somehow, ''advanced'' editing options (no matter how critical they are to editing articles). But I'd love to hear from someone as to why Bold and Italic (the first in particular ''rarely'' used in articles) still have icons visible on the toolbar, while five other formatting options are now under ""More"". It really, really would have been better to have a ""Format text"" drop-down menu that had all seven text formatting options on it, and to leave the media, reference, reference list, and transclusion icons where they were, visible on the toolbar. Or, worst case, leave them under the ""More"" menu [one more click, and thus one less reason for experienced editors to use VE, because this '''makes it more cumbersome to use''' those four things]; at least then they wouldn't be paired with formatting options with which they have little in common. [...] (And don't even get me started on the ''sequence'' within the new ""More"" drop-down menu - apparently the ''least'' important choices are at the ''top'' because that's the way that ''no one else'' does drop-down menus, so obviously everyone else is wrong?!?)>>
+
+Andrew Davidson: <<Bold formatting is not rarely used.  It is used in all articles right at the beginning to emphasise the name of the topic and any synonyms.  But this usage is quite specialised and subject to the conventions of our manual of style.  The VE should understand this.  Either the use of bold text should be handled by a style sheet/template/wizard approach to article creation.  Or the appearance of the bold option in the toolbar should be context sensitive so that it only appears when editing the lead of an article and warnings appears if it seems to be used incorrectly. >>
+
+Salix alba: <<One problem I get is the toolbar frequently splits into two lines. If my browser less than 1100 pixels then the toolbar wraps leaving lots of white space which could be usefully filled. I'd be happier either with single line with more drop downs or two full lines, just not empty space.
+I guess different editors will want different things on a toolbar. Doing inline maths you would want italics, sub, and sup to be easily added plus greek symbols eiπ. Other editors will have different requirements. Tooltips would be handy to get shortcuts for each action, (no I will not read the help page). The wikitext editor's toolbar manages to make a lot of things easily accessible.>>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379510460,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-agsyhe563ga6xlci4yds,task_description,resolved
+VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,I did this in wmf7.,1389667077,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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 .",1379693737,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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",1379599183,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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.",1379527718,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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.",1379523614,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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?",1379517590,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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`.
+",1379372820,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_description,resolved
+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.,1487640775,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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]]",1456599605,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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]]
+",1456598697,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1456598688,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,P2680,1456539439,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,Got this locally on MediaWiki-Vagrant.,1456539379,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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 (<https://gerrit.wikimedia.org/r/#/c/102557/>) and @TStarling at that time wanted the message to stay until the underlying bug was fixed.",1452556121,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,@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.,1452554163,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,">>! 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.",1441317606,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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}
+```",1441308367,PHID-USER-e7a5lnjpgncgdxknmdxb,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1433168184,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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]]",1421437119,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1416277543,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1416276389,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1416275630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1406922819,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1387492413,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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,1387401105,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385052270,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1385043099,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385041071,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1385038063,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385032746,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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}",1385032556,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1385023044,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1385022091,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385004900,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385004767,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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,1384994015,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1384295661,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1384277258,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1384246201,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.,1379397762,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+"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 <templatedata /> 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}",1379223360,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-n7t7uv2o256io5ck73dn,task_description,open
+"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.",1685509112,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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}",1685508575,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1685263240,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1685257840,PHID-USER-3imz37uve2wfuuub5eq6,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1684947002,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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",1684667542,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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).",1684664576,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.,1684658990,PHID-USER-c4xszutxtrvtj73h3rns,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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 <templatedata> will be dynamically generated during the parse time, and is available to every language/every wiki.",1545340062,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1545295664,PHID-USER-3imz37uve2wfuuub5eq6,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.
+
+",1545275829,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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,1502648392,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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 ##<templatedata>## approach needs to be supported, too.
+",1526399860,PHID-USER-3imz37uve2wfuuub5eq6,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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 ##<templatedata>## approach needs to be supported, too.
+",1490880640,PHID-USER-3imz37uve2wfuuub5eq6,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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…",1452893325,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.,1401208356,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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",1398702686,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1379512241,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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 ?,1379497097,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+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
+<html><head><title>Error generating thumbnail</title></head>
+<body>
+<h1>Error generating thumbnail</h1>
+<p>
+Error creating thumbnail:
+</p>
+<!-- http://commons.wikimedia.org/w/thumb_handler.php/f/fb/USMC-05934.jpg/400px-USMC-05934.jpg -->
+<!-- mw1154 -->
+</body>
+</html>
+
+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 <img>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",1378941420,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5ts3ggpcjypmoohi32ft,task_description,resolved
+Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"[02:06:08] <Reedy> Can someone depool mw1154 from the image scaler cluster?
+[02:06:20] <paravoid> what's wrong with it?
+[02:07:40] <Reedy> It's seemingly generating a lot more errors (by a factor of 2 or so) than any of the other scalers
+[02:07:41] <Reedy> https://bugzilla.wikimedia.org/show_bug.cgi?id=54045
+[02:08:32] <paravoid> root@mw1154:~# ls /sys/fs/cgroup/memory/mediawiki/job
+[02:08:33] <paravoid> ls: cannot access /sys/fs/cgroup/memory/mediawiki/job: No such file or directory
+[02:08:35] <paravoid> blergh
+[02:09:01] <paravoid> fixed
+[02:09:58] <Reedy> is that's what's up with it?
+[02:10:05] <paravoid> yes, fixed
+[02:10:09] <Reedy> awesome
+[02:10:10] <Reedy> thanks",1379553025,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1379552717,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,Ganglia graphs suggest so (mw1154 has less activity) but I haven't specificly tested.,1379552393,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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),1379547506,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,Could this server be taken out of rotation until the issue is resolved?,1379546704,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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 <img> 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",1379391380,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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)",1379373885,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,*** Bug 54188 has been marked as a duplicate of this bug. ***,1379373403,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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.",1378958845,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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).",1378950740,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378943525,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378943170,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378942177,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378941699,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378941647,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+"[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",1378771740,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_description,resolved
+"[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",1404843771,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Yay, thanks Bryan.",1404841358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1404837730,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1403864865,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1403810584,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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'.",1403805154,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.,1403743208,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.",1400529133,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.,1399426964,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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""
+      }
+    }",1399420245,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.",1399410121,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1399399638,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1399334206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1398832805,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1398806849,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.,1398716142,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1398200919,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.",1398197371,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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)?,1398195477,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1398191798,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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. ***,1395351525,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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. ***,1392411945,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.",1392334367,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1378775517,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+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",1378584660,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-uycqr5h5vgduf55buvs4,task_description,resolved
+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!",1404820885,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',<3,1404820538,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',The fix has been deployed at gerrit.wikimedia.org.,1404805916,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1404338417,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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!",1404309484,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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;",1404293518,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1404292325,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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!,1404290440,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1404244147,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1404228694,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1403876110,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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 <gerrit> -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",1403176280,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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 :-(",1403175765,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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/",1402965592,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Today again: https://gerrit.wikimedia.org/r/#/c/139047/,1402587645,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1402531001,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1402521845,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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"" :/",1392577169,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1391696645,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1389609979,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Is this related: https://gerrit.wikimedia.org/r/#/c/107036/ ?,1389538078,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1387292272,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1387290809,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',*** Bug 57483 has been marked as a duplicate of this bug. ***,1387290750,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1381404334,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1381388510,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',(Worked for me when I tried again),1380186401,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1380186331,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Still seeing this error randomly.,1379791842,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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=",1378769029,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1378764890,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',We retained the same key for exactly this reason...,1378611129,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1378504020,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_description,resolved
+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)",1384542962,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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.",1384509314,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+Review and deploy BetaFeatures extension,Why is this bug marked fixed?,1384493719,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+Review and deploy BetaFeatures extension,Ready to deploy.,1383178559,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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!!!!",1382980087,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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.",1380139390,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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",1379978838,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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).",1379703244,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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",1378507279,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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",1378444620,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-gendcsutkyq5czjdhhzy,task_description,resolved
+Commit missing from mediawiki/exentions/MassMessage repo,"
+
+*** This bug has been marked as a duplicate of bug 53841 ***",1378697343,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378504584,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378499305,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378498136,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378494665,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.  =(,1378494584,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378490942,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378483919,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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",1378461586,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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",1378345920,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-djr6oferphbxqbgynsnj,task_description,resolved
+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!",1381270319,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+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",1379609001,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+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!",1378942957,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+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",1378477476,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+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).",1378373175,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change,"Sorry 
+*7 Save button does not get enabled",1378345999,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+[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.",1378338120,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_description,open
+[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. ",1686825388,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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",1682009947,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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",1682009851,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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"".",1536338087,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[EPIC] Use Parsoid HTML for all page views,Tagging this for the Web and Infrastructure teams.,1531152561,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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!",1453313802,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1446806999,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1446061348,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1446031849,PHID-USER-hxwwywcyzpooynxuo7a2,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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?",1446031440,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1443905863,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1443474280,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1425275795,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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?",1424285507,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[EPIC] Use Parsoid HTML for all page views,*** Bug 53780 has been marked as a duplicate of this bug. ***,1378338206,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+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",1378310460,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-sudk6gs3gu276aszhg6w,task_description,resolved
+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!",1381270232,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sudk6gs3gu276aszhg6w,task_subcomment,NA
+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",1379660392,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-sudk6gs3gu276aszhg6w,task_subcomment,NA
+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!",1378943075,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-sudk6gs3gu276aszhg6w,task_subcomment,NA
+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.,1378310693,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-sudk6gs3gu276aszhg6w,task_subcomment,NA
+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",1378309560,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-r65cbq4ixbupvjwfesjt,task_description,resolved
+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",1385506396,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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",1384940647,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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!",1381270119,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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",1379657853,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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!",1378943063,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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",1378300380,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bl2j543fwlnzihaohpzu,task_description,resolved
+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.",1399419475,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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.",1381625305,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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. """,1378382011,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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.",1378302842,PHID-USER-qlrpm27qlsmjh2pg65bg,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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),1378300544,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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",1378218960,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-kxfoifw5vn4mx32v4nnk,task_description,resolved
+run VE browser tests in vagrant,Closing since this looks like it has been fixed to me. Please reopen if needed.,1386002609,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-kxfoifw5vn4mx32v4nnk,task_subcomment,NA
+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=<value>
+7. export MEDIAWIKI_USER=<value>
+8. export MEDIAWIKI_PASSWORD=<value>
+9. export PATH=$PATH:/home/vagrant/.gem/ruby/1.9.1/gems/cucumber-1.3.8/bin 
+10. bundle exec cucumber <value>",1384965154,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kxfoifw5vn4mx32v4nnk,task_subcomment,NA
+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",1378156860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wn3s7fg7p7dky4txupqd,task_description,resolved
+browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Basic test is merged and in place, so marking this bug resolved.",1392915139,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Change 111890 merged by jenkins-bot:
+[Browser test] Headless browser test(s)
+
+https://gerrit.wikimedia.org/r/111890",1392914962,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1392028920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1391719839,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1391650517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1391120795,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1391105926,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1391013095,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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}",1389822544,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Changing bug status since task in still WIP.",1388083976,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1387556100,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1387493238,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Created attachment 14138
+ve phantomjs
+
+**Attached**: {F11111}",1387468358,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Created attachment 14137
+ve ff
+
+**Attached**: {F11109}",1387468337,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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).",1387468303,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.)",1387389239,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1387388081,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Created attachment 14130
+phantomjs screen shot
+
+**Attached**: {F11108}",1387386995,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,Looks like phantomjs is blacklisted (or not whitelisted). There is no visual editor edit option (see screen shot).,1387386945,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1387327633,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1386979767,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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}",1386956370,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Created attachment 14080
+phantomjs screen shot
+
+**Attached**: {F11105}",1386926023,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1386925978,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1386893033,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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 :-)",1386847077,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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).",1386811597,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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)",1386798514,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1386779767,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Assigning to myself per an e-mail thread with Antoine, Chris, and Željko.",1386701650,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1378126200,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-l4bd6ekvg2ifcspk72da,task_description,invalid
+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.",1381269899,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l4bd6ekvg2ifcspk72da,task_subcomment,NA
+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.",1380647038,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-l4bd6ekvg2ifcspk72da,task_subcomment,NA
+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",1380442542,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-l4bd6ekvg2ifcspk72da,task_subcomment,NA
+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",1378013580,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-dvolbemwppvolpsqeen5,task_description,resolved
+VisualEditor: Removing formatting from part of a link causes a snowman,This was fixed two weeks ago; sorry for the slowness in replying.,1380838919,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dvolbemwppvolpsqeen5,task_subcomment,NA
+"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",1377807780,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-tes2snxxrdfko3p2bzft,task_description,resolved
+"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",1377813415,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tes2snxxrdfko3p2bzft,task_subcomment,NA
+"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",1377812789,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tes2snxxrdfko3p2bzft,task_subcomment,NA
+"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)",1377812736,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-tes2snxxrdfko3p2bzft,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> block with the experimental generic editor leads to brokenness because the attributes get blanked,"**Author:** `wojciech.r`
+
+**Description:**
+When I edit existing content in <source> 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",1377796560,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ikc6bitfegyn4srxsl45,task_description,resolved
+VisualEditor: Editing a <syntaxhighlight> 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.",1377958953,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> 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",1377909844,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> 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.,1377906465,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> block with the experimental generic editor leads to brokenness because the attributes get blanked,Related bug 53614,1377906431,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> 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",1377905362,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Pressing up while next to an inline image throws an exception,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377729540,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qgxcekjgfnhxpyipqdms,task_description,resolved
+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",1377732790,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qgxcekjgfnhxpyipqdms,task_subcomment,NA
+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",1377732192,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qgxcekjgfnhxpyipqdms,task_subcomment,NA
+"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",1377700800,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-4lk6qpiuan7kbk6fch54,task_description,resolved
+"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...",1397734119,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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!",1397732911,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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",1397705933,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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…",1397246077,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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. :)",1397245474,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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...",1397243067,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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).",1397241093,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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",1397151063,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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).,1396995419,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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?",1396986708,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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. :)",1396986438,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages",*** Bug 56844 has been marked as a duplicate of this bug. ***,1384096303,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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.",1378409168,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+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",1377652560,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-5jzwlml42c5fglrwtkfi,task_description,resolved
+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",1378261353,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5jzwlml42c5fglrwtkfi,task_subcomment,NA
+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",1377870978,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5jzwlml42c5fglrwtkfi,task_subcomment,NA
+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",1377652320,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bcaoiws3nuti2nsjkjz3,task_description,resolved
+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",1378261355,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bcaoiws3nuti2nsjkjz3,task_subcomment,NA
+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",1377870974,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bcaoiws3nuti2nsjkjz3,task_subcomment,NA
+"VisualEditor: Style Parsoid's <figure>s to look like MediaWiki's <div class=""thumb"">s rather than replacing them","Right now VisualEditor transforms the HTML Parsoid gives us (which is nicely-structured <figure>s) into the mess of <div>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 <div>s with known classes (and Parsoid's HTML has no <div>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",1377645300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w64szlorn34djdoon7kx,task_description,resolved
+"VisualEditor: Style Parsoid's <figure>s to look like MediaWiki's <div class=""thumb"">s rather than replacing them","Change 93417 merged by jenkins-bot:
+Render CE MWBlockImageNodes as styled <figure>s
+
+https://gerrit.wikimedia.org/r/93417",1386874034,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w64szlorn34djdoon7kx,task_subcomment,NA
+"VisualEditor: Style Parsoid's <figure>s to look like MediaWiki's <div class=""thumb"">s rather than replacing them","Change 93417 had a related patch set uploaded by Jforrester:
+Render CE MWBlockImageNodes as styled <figure>s
+
+https://gerrit.wikimedia.org/r/93417",1386213845,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w64szlorn34djdoon7kx,task_subcomment,NA
+"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",1377627060,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ibe45dq6vmicfsr4xdu7,task_description,open
+"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",1659473886,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ibe45dq6vmicfsr4xdu7,task_subcomment,NA
+"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.",1659377186,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-ibe45dq6vmicfsr4xdu7,task_subcomment,NA
+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",1377562620,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-cp6otuehw4hsidnwe5aw,task_description,resolved
+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. 
+
+",1421687542,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-cp6otuehw4hsidnwe5aw,task_subcomment,NA
+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. ",1421454194,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-cp6otuehw4hsidnwe5aw,task_subcomment,NA
+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",1377553200,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-uypsqiix32ng3uny23mo,task_description,resolved
+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",1378923308,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uypsqiix32ng3uny23mo,task_subcomment,NA
+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",1378548150,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uypsqiix32ng3uny23mo,task_subcomment,NA
+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",1377547260,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-epab3bnrysrclgspz74p,task_description,resolved
+VisualEditor: getNearestCorrectOffset doesn't ignore internal lists,"ElementLinearData#getRelativeOffset now checks for handlesOwnChildren, which prevents this from being an issue.",1397775737,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-epab3bnrysrclgspz74p,task_subcomment,NA
+VisualEditor: getNearestCorrectOffset doesn't ignore internal lists,May have been ameliorated by https://gerrit.wikimedia.org/r/98515,1385996866,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-epab3bnrysrclgspz74p,task_subcomment,NA
+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",1377547080,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-bzqqgbtatyk37hok3eeg,task_description,resolved
+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",1377800766,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bzqqgbtatyk37hok3eeg,task_subcomment,NA
+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",1377643119,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bzqqgbtatyk37hok3eeg,task_subcomment,NA
+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",1377545880,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7n32t2g7qmarlr4ehelo,task_description,resolved
+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",1377800814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7n32t2g7qmarlr4ehelo,task_subcomment,NA
+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",1377545917,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7n32t2g7qmarlr4ehelo,task_subcomment,NA
+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",1377545460,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dtn35n72ll6dpl3csge6,task_description,resolved
+VisualEditor: Document loses focus after cutting a FocusableNode,Fixed in master; will be deployed on Thursday as part of the regular push.,1377634940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dtn35n72ll6dpl3csge6,task_subcomment,NA
+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",1377634904,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dtn35n72ll6dpl3csge6,task_subcomment,NA
+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",1377545794,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dtn35n72ll6dpl3csge6,task_subcomment,NA
+VisualEditor: Document loses focus after cutting a FocusableNode,https://gerrit.wikimedia.org/r/#/c/81027/ fixes,1377545735,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dtn35n72ll6dpl3csge6,task_subcomment,NA
+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}",1377540900,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-si6erwgobtecdd3semnx,task_description,resolved
+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.",1377657008,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+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,1377638934,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+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.",1377638844,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+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).",1377633524,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13176
+example 3
+
+**Attached**: {F11316}",1377541077,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13175
+example 3
+
+**Attached**: {F11315}",1377541052,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13174
+example 2
+
+**Attached**: {F11312}",1377541029,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13173
+example 2
+
+**Attached**: {F11311}",1377541006,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13172
+example 1
+
+**Attached**: {F11310}",1377540983,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> 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",1377527760,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-2537ayvqomhm6aw6be77,task_description,resolved
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> tag in the wikitext,Fixed in master; will be deployed on Thursday as part of the regular push.,1377649422,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2537ayvqomhm6aw6be77,task_subcomment,NA
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> 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",1377649390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2537ayvqomhm6aw6be77,task_subcomment,NA
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> 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",1377649253,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2537ayvqomhm6aw6be77,task_subcomment,NA
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> 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",1377621200,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-2537ayvqomhm6aw6be77,task_subcomment,NA
+"Don't allow nested <ref>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 <ref> tag (e.g., a bibliographic citation) inside another <ref> 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",1377373500,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-tht33qexrstttffqqdac,task_description,resolved
+"Don't allow nested <ref>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.",1378762753,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-tht33qexrstttffqqdac,task_subcomment,NA
+"Don't allow nested <ref>s, because Cite.php doesn't","(In reply to comment #0)
+> Adding a <ref> tag (e.g., a bibliographic citation) inside another <ref> 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?",1377510119,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tht33qexrstttffqqdac,task_subcomment,NA
+"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",1377252120,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-5rnk4jk4usyomimnhvgw,task_description,resolved
+"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,1386984972,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",Verified in Betalabs,1386824907,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"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.,1386821195,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",okay but I checked it on Betalabs.,1386810610,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"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.",1386810532,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",I am still seeing label Latex instead of Formula,1386810322,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"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",1386803523,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"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",1386383633,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing","I'm minded to just call it ""Formula"". Thoughts?",1385494999,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+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 (&amp;lt;nowiki&amp;gt;, or does just plain &lt;/nowiki&gt; 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 </nowiki> tag '''here'''.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377197160,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-q5vutkamr63367rd7zxs,task_description,resolved
+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",1402416475,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q5vutkamr63367rd7zxs,task_subcomment,NA
+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",1401935637,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q5vutkamr63367rd7zxs,task_subcomment,NA
+Nowiki tag not properly escaped when combined with other wiki markup,"This is a Parsoid serializer bug:
+
+[subbu@earth tests] echo '* &lt;/nowiki&gt; tag' | node parse --html2wt
+<nowiki>* </nowiki></nowiki> tag",1377208818,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-q5vutkamr63367rd7zxs,task_subcomment,NA
+"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",1377184320,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-jr5ycdlwcecuxieizpcv,task_description,resolved
+"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",1395076819,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"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",1395073111,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"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.,1379005591,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"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.",1377295726,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"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.",1377282757,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"Slugs are created inside empty table rows, creating pawns if used",Pawns are firmly VE territory. Moving to the VisualEditor product.,1377186019,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"VisualEditor: Blank page, list, [enter] lose cursor","<<If I edit a blank page, press on the number list or bullet list icon and then press enter, the page remains blank but I have no cursor. Then other strange things start to happen. Pressing the link icon does not seem to do anything. I can press some icons (transclusion, references, etc) and they will appear, but if I then exit it, pressing it again or any other icon does nothing. Undo works though. FF 23.0.1 Win7. --Atethnekos (Discussion, Contributions) 21:27, 21 August 2013 (UTC) >>
+
+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",1377164400,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-l56nfzkytddrozusk6lo,task_description,resolved
+"VisualEditor: Blank page, list, [enter] lose cursor",This was fixed a long while ago.,1394678478,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l56nfzkytddrozusk6lo,task_subcomment,NA
+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",1377087600,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-oupbsd5554xmfpbxxxyj,task_description,resolved
+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",1379981366,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oupbsd5554xmfpbxxxyj,task_subcomment,NA
+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",1379981363,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oupbsd5554xmfpbxxxyj,task_subcomment,NA
+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",1379613881,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oupbsd5554xmfpbxxxyj,task_subcomment,NA
+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",1379613876,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oupbsd5554xmfpbxxxyj,task_subcomment,NA
+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",1377068880,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gnj6uia6j4dqknm3pggn,task_description,resolved
+Implement non-linear transitions,"Change 116228 merged by jenkins-bot:
+Refactor and add non-linear tours, with tests
+
+https://gerrit.wikimedia.org/r/116228",1402332991,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gnj6uia6j4dqknm3pggn,task_subcomment,NA
+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",1395186275,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gnj6uia6j4dqknm3pggn,task_subcomment,NA
+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",1376955360,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ii6rhmjn7erj375xgev6,task_description,resolved
+VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),*** Bug 53317 has been marked as a duplicate of this bug. ***,1379576014,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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",1377642670,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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.,1377602894,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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",1377602821,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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 <h1> 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?",1377592907,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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",1377542371,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"<<First, I noticed a strange behavior where anything I typed at the end of that third line, if I then hit enter, it would be duplicated in the fourth line, and my cursor would move to the fifth (blank) line. I then took a look at the wikitext generated by VE, and it looked odd, so I copied it into a wikitext editor, and got a rather different looking result than VE was showing. Also, upon saving with VE, I got this result, which is the same as copying into wikitext editor, but not what VE was showing me. Chris857 (talk) 20:54, 25 August 2013 (UTC) >>
+
+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.",1377524357,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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.",1377524032,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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.",1376955601,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+about=null entries on <figure> 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]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 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",1376945880,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_description,resolved
+about=null entries on <figure> elements (because of dom-fragment reuse),I am marking this resolved. Haven't seen any reports about this in a while.,1389799516,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> elements (because of dom-fragment reuse),Is this still happening in production?,1386109794,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> elements (because of dom-fragment reuse),https://gerrit.wikimedia.org/r/#/c/83216/ fixes the dsr inconsistency warnings  reported in this bug.,1379553778,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> elements (because of dom-fragment reuse),"Sorry, I linked the wrong bug which is how you got the email ;-) .. fixing it.",1378333227,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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"" :)",1378333119,PHID-USER-vbyvvtbztxaeuaxelxx4,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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.",1378332012,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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.",1378331190,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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",1378326748,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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",1378323821,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> elements (because of dom-fragment reuse),"One more example:
+
+https://it.wikipedia.org/w/index.php?title=Dalmine&diff=61238476&oldid=61238456",1378225470,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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 <figure> tags with about=null",1377276929,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+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",1376939940,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-oplpiaxofrtlrt3axphq,task_description,resolved
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"
+
+*** This bug has been marked as a duplicate of bug 45240 ***",1377348845,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-oplpiaxofrtlrt3axphq,task_subcomment,NA
+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",1376930160,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_description,resolved
+VisualEditor: Expose build number,FYI - This might be removed in {T119750},1448666920,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+VisualEditor: Expose build number,"Change 84334 merged by jenkins-bot:
+Hide version info if not available
+
+https://gerrit.wikimedia.org/r/84334",1379466654,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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",1379346926,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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.",1379107432,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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).",1379107220,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+VisualEditor: Expose build number,"Change 81877 merged by jenkins-bot:
+Expose version information in the client
+
+https://gerrit.wikimedia.org/r/81877",1377888800,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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",1377817078,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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}",1376928720,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qsixjppbefsch6bho32b,task_description,resolved
+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",1377019844,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsixjppbefsch6bho32b,task_subcomment,NA
+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",1376928825,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsixjppbefsch6bho32b,task_subcomment,NA
+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",1376863380,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-uwxs5htjvrwhn73aykjk,task_description,resolved
+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.",1378958990,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uwxs5htjvrwhn73aykjk,task_subcomment,NA
+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!",1378943150,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-uwxs5htjvrwhn73aykjk,task_subcomment,NA
+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?",1376949133,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uwxs5htjvrwhn73aykjk,task_subcomment,NA
+"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 <click>, and I have the arrow pointer.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376814420,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-j5vjfdev7u6pvuctl7bs,task_description,declined
+"VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing","Still can't reproduce, unfortunately. :-(",1406756283,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j5vjfdev7u6pvuctl7bs,task_subcomment,NA
+"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",1376816801,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-j5vjfdev7u6pvuctl7bs,task_subcomment,NA
+"VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing","Created attachment 13119
+screenshot, I lied
+
+**Attached**: {F11406}",1376814590,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-j5vjfdev7u6pvuctl7bs,task_subcomment,NA
+"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 <return> 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}",1376813040,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-4rr6da3rjeo7zsqa7vfz,task_description,declined
+"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. :-(",1377831473,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rr6da3rjeo7zsqa7vfz,task_subcomment,NA
+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:
+
+<table><tr title=""{{echo|foo}}""></tr></table>
+
+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 '<div title=""{{echo|foo}}"">{{echo|</div>}}' | 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",1376628000,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cxh6tjsfd6x3hseyrbib,task_description,resolved
+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.",1386110602,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cxh6tjsfd6x3hseyrbib,task_subcomment,NA
+Move info about template-affected attributes from meta tags into data-mw,Meta tags in foster-parentable positions aren't really an issue anymore.,1380306722,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-cxh6tjsfd6x3hseyrbib,task_subcomment,NA
+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}",1376490900,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bdoqslcxagfk2qftlhdb,task_description,resolved
+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",1391808827,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bdoqslcxagfk2qftlhdb,task_subcomment,NA
+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",1391358454,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bdoqslcxagfk2qftlhdb,task_subcomment,NA
+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].",1391358288,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-bdoqslcxagfk2qftlhdb,task_subcomment,NA
+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",1376488380,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4hkjv2ath5m5txk2nfy2,task_description,resolved
+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",1376509523,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4hkjv2ath5m5txk2nfy2,task_subcomment,NA
+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",1376491490,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4hkjv2ath5m5txk2nfy2,task_subcomment,NA
+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
+<meta charset='utf-8'><p data-parsoid ...</p><br class=""Apple-interchange-newline"">
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52770",1376343780,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-5nevglmngclvgx6tccw2,task_description,resolved
+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.),1381158661,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5nevglmngclvgx6tccw2,task_subcomment,NA
+VisualEditor: Pasting block level elements can lose annotations,Can't reproduce.,1381156961,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5nevglmngclvgx6tccw2,task_subcomment,NA
+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",1376320140,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-66ginvgnolmwprgt3cuj,task_description,resolved
+VisualEditor: Edit to a template somehow removing equals signs in markup?,AFAICT this is fixed; no recurrences in months have been reported.,1421281940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-66ginvgnolmwprgt3cuj,task_subcomment,NA
+VisualEditor: Edit to a template somehow removing equals signs in markup?,Aha; sorry :).,1376321896,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-66ginvgnolmwprgt3cuj,task_subcomment,NA
+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",1376320887,PHID-USER-5c526sthsodab4l3hur6,PHID-TASK-66ginvgnolmwprgt3cuj,task_subcomment,NA
+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 <jenkins-bot@gerrit.wikimedia.org>
+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}",1376317860,PHID-USER-26asvhtv4jalaeeuigbm,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_description,resolved
+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",1376424244,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_subcomment,NA
+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",1376342314,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_subcomment,NA
+Regression: Wikitext for new lists has unnecessary newlines after bullets,git bisect shows that c0de1d5839430e9fde79ff4195caf6841baab0d3 is the culprit.  Will investigate and fix.,1376341085,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_subcomment,NA
+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 ""<ul><li><p>a</p></li></ul>"" | node parse --html2wt
+Incompatible constraints 1: LI P { a: { min: 0, max: 0 }, b: { min: 1, max: 2 }, min: 0, max: 0 }
+* 
+a",1376340885,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_subcomment,NA
+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",1376299800,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-o5baaacr6iodckukah5p,task_description,resolved
+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 ***",1377814470,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o5baaacr6iodckukah5p,task_subcomment,NA
+VisualEditor: Add a keyboard shortcut to trigger Save dialog,"> Ctrl+Shift+S
+
+Sorry, I meant Alt+Shift+S",1376299882,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-o5baaacr6iodckukah5p,task_subcomment,NA
+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",1376191500,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_description,resolved
+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!",1377202396,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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",1377164931,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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",1377027656,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,"Patch has been reverted due to other issues, sadly.",1376960981,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,Doesn't seem to be happening any more.,1376937358,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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).",1376922530,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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.",1376585969,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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",1376179080,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_description,resolved
+Enable Echo / Notifications on se.wikimedia.org,Seems like this wiki was included in the last roll-out.,1382727600,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_subcomment,NA
+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.",1376514498,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_subcomment,NA
+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 ...",1376513998,PHID-USER-dbudsaorcqut7sg3vvbi,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_subcomment,NA
+Enable Echo / Notifications on se.wikimedia.org,"I don't think Echo is under general deployment yet.
+
+CC'ing Fabrice",1376185892,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_subcomment,NA
+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",1376107740,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7ldpzjc4tuyxvsjssopj,task_description,resolved
+VisualEditor: Register each VE experimental feature individually with the BetaFeatures extension,Done in gerrit 91108.,1383280071,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7ldpzjc4tuyxvsjssopj,task_subcomment,NA
+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",1378918492,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7ldpzjc4tuyxvsjssopj,task_subcomment,NA
+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",1376287586,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7ldpzjc4tuyxvsjssopj,task_subcomment,NA
+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",1376050440,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fbqhcge4qrnba67okcqc,task_description,resolved
+VisualEditor: Link suggestions list should vertically scroll if there's insufficient room for them on-screen,"No, it was in error. Sorry!",1393635105,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fbqhcge4qrnba67okcqc,task_subcomment,NA
+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?",1393633971,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-fbqhcge4qrnba67okcqc,task_subcomment,NA
+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.,1393632732,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fbqhcge4qrnba67okcqc,task_subcomment,NA
+[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}",1375990260,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_description,resolved
+[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",1409943658,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,*** Bug 55457 has been marked as a duplicate of this bug. ***,1409942617,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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",1409942585,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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",1393344878,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,Rephrasing bug title as it was cut-off.,1392115165,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Thanks, Bartosz.",1390506925,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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",1390506812,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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.",1390506798,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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.,1390406732,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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)?",1387200972,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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)?",1385396423,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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.",1381622838,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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?",1381257412,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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,1381257077,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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 (<div id=""mw-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.",1381256567,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,*** Bug 55457 has been marked as a duplicate of this bug. ***,1381254044,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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.",1376072941,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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}",1375991155,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+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 '<h2>Life and career</h2>' to '<h2>Life and careeer</h2>'
+$ 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<BR>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.<ref>{{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]]}}</ref> 
+-| 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'''<ref>[http://www.mlive.com/entertainment/saginaw/index.ssf/2008/08/ravensymone_steps_out_of_chara.html]</ref>, (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]]''<!-- Per http://www.imdb.com/name/nm0712368/filmoseries#tt0086687 her first episode of ""A Different World"" was Nov. 2, 1989, while her first Cosby Show episode was Sept 21, 1989. --> 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]].<ref>[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.</ref> 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.<ref name=""billboard.com"">[{{BillboardURLbyName|artist=raven-symoné|chart=Billboard 200}} Raven-Symoné]. Billboard.com. Retrieved 2012-05-19.</ref> 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,<ref name=""GKSAT"">[http://blog.vh1.com/2012-12-02/and-the-1-greatest-kid-star-of-all-time-is/ Greatest Kid Star Of All Time]</ref> and ranked number one on ''Loop21''{{'s}} ""10 Richest Black Actresses Under 40"" list.<ref name=""RBAU40"">[http://www.loop21.com/entertainment/10-richest-black-actresses-under-40 10 Richest Black Actresses Under 40]</ref>
+ 
+-==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]] <ref>http://www.tv.com/people/raven-symone/</ref><ref>http://xfinity.comcast.net/slideshow/entertainment-aachildactors/3/</ref><ref>http://ethnicelebs.com/raven-symone</ref><ref name=""imdb"">http://www.imdb.com/name/nm0712368/bio</ref><ref>http://www.nndb.com/people/017/000103705/</ref> and [[Native Americans in the United States|Native American]] ancestry.<ref name=""imdb"" /> At age three, her family moved to [[Ossining (village), New York|Ossining, New York]] where she attended Park School.<ref name=""birthplace"">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.</ref><ref>[http://ftp.rootsweb.com/pub/usgenweb/la/winn/bios/sym1569.txt Rootsweb.com]{{Dead link|date=May 2010}}</ref> 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",1375953720,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-s4knko26mc6rjznucnmu,task_description,resolved
+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.,1377029359,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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.",1376528533,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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",1375981137,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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",1375978007,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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.",1375976525,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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.",1375974012,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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",1375847280,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kpx3x3zovypfoultwmwq,task_description,resolved
+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 ***",1377808859,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1377808647,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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. ***,1377808418,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376142164,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376106189,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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!",1376075501,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376074801,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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).",1376074522,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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}",1376074189,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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}",1376073840,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376073813,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376073316,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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?",1375847955,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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",1375737000,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-puu746mglczm4q4dlq2x,task_description,resolved
+VisualEditor: Dragging mouse clicks VE buttons upon release,"I cant reproduce any combination supported on Linux, or Firefox/Windows/monobook.",1380610142,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-puu746mglczm4q4dlq2x,task_subcomment,NA
+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",1380546794,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-puu746mglczm4q4dlq2x,task_subcomment,NA
+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.",1375794161,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-puu746mglczm4q4dlq2x,task_subcomment,NA
+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.",1375737768,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-puu746mglczm4q4dlq2x,task_subcomment,NA
+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",1375635660,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_description,resolved
+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",1411778780,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+VisualEditor: Inspectors should not display below visible page area,"(This only affects inspectors, and they're a VE feature; moving.)",1411777234,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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",1411771949,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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",1411766928,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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",1411759324,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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?).,1405377923,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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",1375600380,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-qi4sreqcffmkf7rnalbq,task_description,resolved
+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",1392856750,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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",1392748395,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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.",1392403289,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+VisualEditor: Cannot apply annotations to link in specific case in Firefox,Can't reproduce in FF 27. Can someone else?,1392390005,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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.",1390418119,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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).",1375600824,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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",1375562940,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_description,resolved
+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.",1377557411,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+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?",1377527169,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+VisualEditor: Top bar not staying at top,Will the fix of Bug 52441 (awaiting deployment) also solve this?,1375991784,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+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.",1375606053,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+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.",1375604655,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+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",1375529520,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qmrrjmfnasuu75b532kc,task_description,resolved
+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",1398959330,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qmrrjmfnasuu75b532kc,task_subcomment,NA
+VisualEditor: Protected node css with * selector breaks some template layouts,"Created attachment 15263
+Screenshot of problem and patched version
+
+**Attached**: {F11282}",1398959289,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qmrrjmfnasuu75b532kc,task_subcomment,NA
+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",1398947768,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qmrrjmfnasuu75b532kc,task_subcomment,NA
+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",1375489200,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-ov7pqqy7izua2omo6knh,task_description,resolved
+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.,1376930015,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ov7pqqy7izua2omo6knh,task_subcomment,NA
+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?,1376929509,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ov7pqqy7izua2omo6knh,task_subcomment,NA
+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 <references />)? If so then this could be related to bug 52371,1376256998,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ov7pqqy7izua2omo6knh,task_subcomment,NA
+"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",1375482780,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-sveofxpb25owm56vn52q,task_description,resolved
+"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",1375492758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sveofxpb25owm56vn52q,task_subcomment,NA
+"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",1375482953,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sveofxpb25owm56vn52q,task_subcomment,NA
+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",1375473840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-acmmw5etc6s3hnjsoagh,task_description,resolved
+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",1376023354,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-acmmw5etc6s3hnjsoagh,task_subcomment,NA
+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",1376021746,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-acmmw5etc6s3hnjsoagh,task_subcomment,NA
+VisualEditor: Data model should be able to default between equivalent annotations,code/tt duplicate of bug 52352,1375543016,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-acmmw5etc6s3hnjsoagh,task_subcomment,NA
+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",1375473480,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dixea6aehlzjvgpfccvz,task_description,resolved
+Update tours for new edit tab selectors,"Change 78026 merged by jenkins-bot:
+Update VE section edit selector
+
+https://gerrit.wikimedia.org/r/78026",1376526350,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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",1375865592,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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",1375477475,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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",1375477081,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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.",1375474521,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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",1375472100,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-vzoa67je6467j364n6nw,task_description,resolved
+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.",1375487279,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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.",1375486752,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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.",1375485996,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+VisualEditor:  User guide should open in a new tab/window,"Now fixed in the code; next scheduled deployment is not until 15 August, however. :-(",1375474715,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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",1375473897,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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",1375473255,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+VisualEditor:  User guide should open in a new tab/window,Marking as high priority like similar bug 52093,1375472396,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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",1375460760,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-v2iurekb2mj5nlfaied2,task_description,resolved
+VisualEditor: Media insertion dialog should display a message if no media is found for the given search,Verified in production,1400794526,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+VisualEditor: Media insertion dialog should display a message if no media is found for the given search,Verified the fix in Betalabs,1400537169,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400535869,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400282641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400282181,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400280097,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Created attachment 15419
+Screenshot
+
+**Attached**: {F11195}",1400268429,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400268400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400109025,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1399963305,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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.",1391711753,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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. ***,1391659253,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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"").",1376588485,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1375459440,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bpmyhnrfcuvcbkkh3dqm,task_description,resolved
+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",1378335605,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bpmyhnrfcuvcbkkh3dqm,task_subcomment,NA
+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",1378240685,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bpmyhnrfcuvcbkkh3dqm,task_subcomment,NA
+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",1375424760,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5butgjmyg5i25tvyzxlh,task_description,resolved
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52739 has been marked as a duplicate of this bug. ***,1376521783,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52789 has been marked as a duplicate of this bug. ***,1376476088,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52433 has been marked as a duplicate of this bug. ***,1375991502,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52326 has been marked as a duplicate of this bug. ***,1375936189,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,"Now fixed in the code; next scheduled deployment is not until 15 August,
+however. :-(",1375475301,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+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",1375439587,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+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",1375429015,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+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.",1375428640,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+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",1375398120,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_description,resolved
+VisualEditor: references in image captions are not included in reflists,"Re-setting as FIXED, and have raised the regression as bug 57228.",1384844452,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+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)>>.",1384812491,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+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",1375469746,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+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",1375461230,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+VisualEditor: references in image captions are not included in reflists,"**kwwilliams** wrote:
+
+52300 may also be related.",1375399091,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+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",1375343460,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-svgbuubly7i37677eqfj,task_description,resolved
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"
+
+*** This bug has been marked as a duplicate of bug 50822 ***",1398187598,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-svgbuubly7i37677eqfj,task_subcomment,NA
+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.",1375672513,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-svgbuubly7i37677eqfj,task_subcomment,NA
+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",1375328880,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ycfuexv2jknnm72vmgj2,task_description,resolved
+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.",1375423690,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ycfuexv2jknnm72vmgj2,task_subcomment,NA
+"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",1375306080,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-rk7rg7s3j76gm4lymrcv,task_description,resolved
+"VisualEditor (and possibly other beta tools) need an exposed, easy-to-use on/off switch",BetaFeatures is in place for this now.,1392032698,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rk7rg7s3j76gm4lymrcv,task_subcomment,NA
+"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",1375314628,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-rk7rg7s3j76gm4lymrcv,task_subcomment,NA
+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 <tt> ... </tt> 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}",1375299180,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-27y3ao6udiwcetvc5juo,task_description,resolved
+VisualEditor: Selection highlighting breaks if an inline alien wraps,*** Bug 67062 has been marked as a duplicate of this bug. ***,1403696547,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+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",1402962749,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+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",1402915741,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+VisualEditor: Selection highlighting breaks if an inline alien wraps,"Created attachment 13036
+wrapped inline alien: incorrect highlighting in firefox
+
+**Attached**: {F11840}",1375300000,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+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//",1375299322,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+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}",1375281660,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7gsk7m3csraunlup7tpi,task_description,resolved
+VisualEditor: Toolbar overlaps top of page links,"I guess https://bugzilla.wikimedia.org/show_bug.cgi?id=52433 is a duplicate then?
+Thanks.",1375957512,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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 ***",1375936189,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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",1375860454,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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.",1375560255,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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]]",1375291142,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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",1375192200,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-nirzuutzqnx7m4wim5ej,task_description,resolved
+VisualEditor: Localised tag description should link to content language documentation page,Fixed; we'll deploy this later today.,1375216402,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+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",1375216159,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+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",1375213768,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+VisualEditor: Localised tag description should link to content language documentation page,This was caused by gerrit 75559 - will partially-revert.,1375213677,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+VisualEditor: Localised tag description should link to content language documentation page,Right. It should probably be [[{{MediaWiki:visualeditor-descriptionpagelink}}|VisualEditor]].,1375213343,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+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",1375212767,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+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",1375186860,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-jtms4kp7m57ptk6ccdpu,task_description,resolved
+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.",1378248030,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jtms4kp7m57ptk6ccdpu,task_subcomment,NA
+VisualEditor: Editing a pasted template alters copy buffer. Displayed result differs from saved result.,This appears to be fixed in master.,1378232623,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jtms4kp7m57ptk6ccdpu,task_subcomment,NA
+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"".",1376043644,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-jtms4kp7m57ptk6ccdpu,task_subcomment,NA
+"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",1375145700,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-alab5hdzxtgqi3cu2eqm,task_description,resolved
+"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/,1377888175,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-alab5hdzxtgqi3cu2eqm,task_subcomment,NA
+"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.",1375145903,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-alab5hdzxtgqi3cu2eqm,task_subcomment,NA
+"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}",1375145846,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-alab5hdzxtgqi3cu2eqm,task_subcomment,NA
+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",1375125960,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-rqtkbfxffdpbdagffzia,task_description,resolved
+VisualEditor: categories being duplicated,Going out in a little while.,1375223654,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+VisualEditor: categories being duplicated,"Change 76665 merged by jenkins-bot:
+Don't duplicate categories when unlisting
+
+https://gerrit.wikimedia.org/r/76665",1375223085,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+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",1375143043,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+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.",1375141989,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+VisualEditor: categories being duplicated,http://youtu.be/1rmp5rTDPOM,1375127596,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+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",1375117380,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-uxrs32aphojxiommp53x,task_description,resolved
+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.",1377824944,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+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",1377597258,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+VisualEditor: VE will not save multiple consecutive references,*** Bug 52269 has been marked as a duplicate of this bug. ***,1376325366,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+VisualEditor: VE will not save multiple consecutive references,Fixed and will get deployed in a little while.,1375222413,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+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",1375222340,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+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",1375221066,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+VisualEditor: VE will not save multiple consecutive references,"This happens because we send Parsoid something like
+
+<span about=""undefined"" typeof=""mw:Extension/ref"" data-mw=""...""></span><span about=""undefined"" typeof=""mw:Extension/ref"" data-mw=""...""></span>
+
+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 :)",1375218845,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+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",1375013460,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_description,resolved
+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",1395164666,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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",1395148872,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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.",1385423957,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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 ***",1385398575,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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!",1375092200,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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",1375009500,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_description,resolved
+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.",1402837149,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),Bumping; this is happening 100% of the time now.,1394224211,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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?",1383600380,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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?",1383586954,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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.",1376489457,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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,1376488978,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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}",1376488730,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),"**jonathan_haas** wrote:
+
+I still can (FF23). Just managed on first try.",1376488379,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),Can't reproduce in Chrome or FF,1376488242,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),This is possibly bug 51532,1375059258,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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.,1375049196,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+"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",1375007700,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2klcawe4zbxemkcjvd56,task_description,resolved
+"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.,1415230310,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns",Done in gerrit 159310 and related stack.,1414522013,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"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.",1381788601,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns",*** Bug 53325 has been marked as a duplicate of this bug. ***,1377528014,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns","Ok, will move it elsewhere. Thanks.",1375954624,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns","**jonathan_haas** wrote:
+
+(In reply to comment #2)
+> <<I was editing my userpage with VE today, and I noticed that, in the part
+> 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.",1375954522,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns","<<I was editing my userpage with VE today, and I noticed that, in the part 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 ).",1375954013,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns",I couldnt find another bug for creating tables.,1375049900,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"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//",1374996540,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-q3emmq6fhgusggcncftz,task_description,resolved
+"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.,1384857530,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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…,1384842507,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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}",1384698145,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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.",1381187062,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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",1381186920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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. ***,1380833625,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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",1378325649,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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//",1378325442,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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. ***,1377815261,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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//",1375061595,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+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",1374993900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_description,resolved
+VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,Confirmed now fixed.,1404955719,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,WFM in Firefox,1404940599,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+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).",1403140941,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+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",1403077926,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,Was fixed by something Ed did a while ago.,1402003336,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+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",1377077317,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,Reproduced.,1375050259,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+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",1374967920,PHID-USER-2rwkb3az6uklfhh5aqw5,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_description,resolved
+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.",1384881631,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+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",1384837089,PHID-USER-qlrpm27qlsmjh2pg65bg,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+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.),1384809283,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+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.",1378073148,PHID-USER-qlrpm27qlsmjh2pg65bg,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+VisualEditor: [Regression] Reference list not being updated during editing session,"Confirmed.  Use existing reference shows original references, before they were modified.",1375051990,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+"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",1374966180,PHID-USER-2rwkb3az6uklfhh5aqw5,PHID-TASK-ehj46yftpulklnhzc5nl,task_description,resolved
+"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. ***,1385374664,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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.",1377019526,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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",1377019484,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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",1377019336,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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.",1376611609,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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",1376554077,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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.",1375231690,PHID-USER-2rwkb3az6uklfhh5aqw5,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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?",1375052081,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+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)
+<ref>[http://www.koreatimes.co.kr/ (The Korea Times)][http://www.koreatimes.co.kr/www/news/nation/nation_view.asp?newsIdx=5635&categoryCode=115 <!-- Bot generated title -->]</ref>
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1374878820,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-jhcapgyaxz3ow5vafpun,task_description,resolved
+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.",1406598194,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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.",1403909628,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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",1403905782,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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",1403299185,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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|Bar<!--Baz-->Quux]] and change the link target, you'll split the link: [[Foo2|Bar]][[Foo|<!--Baz-->]][[Foo2|Quux]] (that's also what happened here)
+* If you have Foo<!--Bar-->Baz, it renders as ""FooBar"". If you then make that italic, you'll get ''Foo''<!--Bar-->''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()",1403149757,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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",1374875220,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_description,resolved
+browsertests: triggers for ULS,The job got fixed yesterday and browser tests are passing right now. It is not blocking changes yet though.,1386338190,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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.",1385574363,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+browsertests: triggers for ULS,"Change 97741 merged by jenkins-bot:
+ULS browsertests on check pipeline
+
+https://gerrit.wikimedia.org/r/97741",1385477743,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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",1385477681,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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.",1385412598,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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/",1385379817,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+browsertests: triggers for ULS,Moving this under Continuous Integration radar.,1380112899,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+browsertests: triggers for ULS,Have added bug 53691 for the same for the VisualEditor repo.,1378156956,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+browsertests: triggers for ULS,What about running the tests on patch submission?,1377877531,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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/",1377860181,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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",1374869820,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_description,resolved
+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.,1376621406,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+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",1376621086,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+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",1376488129,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),It's obviusly inviting you to play chess :),1376487625,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),I've reproduced a few of these permutations.,1374905493,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+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}",1374867180,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-7cagldmd3jobcif24ufn,task_description,declined
+VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),This appears to now be fixed - marking as WORKSFORME.,1394224334,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),I can't reproduce this.,1383172136,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+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?,1374879833,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+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.",1374870395,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+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?",1374867555,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+VisualEditor: Write newFromDocumentReplace so editing document slices is simple,"
+--------------------------
+**Version**: unspecified
+**Severity**: major",1374855900,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_description,resolved
+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",1380228356,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_subcomment,NA
+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",1380145599,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_subcomment,NA
+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",1379533053,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_subcomment,NA
+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",1374855973,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_subcomment,NA
+"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",1374846180,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-kcmkos4wcsglqvinne4e,task_description,resolved
+"VisualEditor: Make the ""wikitext"" link of the popup open in a new window",This is now done and we'll get it deployed soon.,1375203313,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kcmkos4wcsglqvinne4e,task_subcomment,NA
+"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",1375201479,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kcmkos4wcsglqvinne4e,task_subcomment,NA
+"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",1375189915,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kcmkos4wcsglqvinne4e,task_subcomment,NA
+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}",1374810540,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-v4wsjl2yostcro6yfl5m,task_description,resolved
+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.",1460010223,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,*** Bug 52895 has been marked as a duplicate of this bug. ***,1377001419,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,*** Bug 52062 has been marked as a duplicate of this bug. ***,1376490819,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+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",1375288239,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,"See also:
+* [[Wikipedia talk:Edit filter#Abusefilter bug on mobile version]]",1375279646,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+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",1374839212,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+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.",1374837132,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,Hoo suspects that this is a problem with VisualEditor. Copying a few folks accordingly.,1374832035,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,"Marius, can you take a look at these? Chris is on vacation right now.",1374810663,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+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",1374810629,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+"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",1374764040,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rlrxpsau6vww7ypqckon,task_description,resolved
+"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",1411174708,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rlrxpsau6vww7ypqckon,task_subcomment,NA
+"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",1411171994,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rlrxpsau6vww7ypqckon,task_subcomment,NA
+"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.",1376122157,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rlrxpsau6vww7ypqckon,task_subcomment,NA
+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",1374729120,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_description,resolved
+VisualEditor: floating toolbar causes scrolling of large pages to be very slow,Merged and deployed.,1375232987,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+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",1375223509,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+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",1375072077,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+VisualEditor: floating toolbar causes scrolling of large pages to be very slow,https://gerrit.wikimedia.org/r/#/c/76241/,1375057326,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+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? :-)
+
+<Krinkle> 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
+<Krinkle> most notably the fact that floating calculation for ve toolbar calls offset() each time
+<Krinkle> which is a repaint for something that is unlikely to ever change
+<Krinkle> I realised it when I was doing mwnotify but never remembered to fix it in VE",1374730873,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+VisualEditor: floating toolbar causes scrolling of large pages to be very slow,@Krinkle: How are you going to fix this? :-),1374730687,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+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",1374728460,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-bd27gm56r2au6k3ieg34,task_description,resolved
+VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,Merged and deployed.,1375233739,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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",1374887599,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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",1374880443,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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.,1374854401,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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",1374853391,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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",1374849799,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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.",1374802942,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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]",1374801722,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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 ;)",1374797517,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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?",1374793855,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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]	<RoanKattouw> 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?",1374793262,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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.",1374733149,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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().",1374731780,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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",1374711420,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_description,resolved
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> with log entry,"Change 119204 merged by jenkins-bot:
+Show blockedtext message in edit notices
+
+https://gerrit.wikimedia.org/r/119204",1395874946,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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",1395091521,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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.",1395077371,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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.",1395076588,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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?",1392078894,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> with log entry,"Created attachment 12954
+What a blocked user sees immediately they the source editor loads
+
+**Attached**: {F11061}",1374711764,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> with log entry,"Created attachment 12953
+What a blocked user sees when they try to save an edit in VE
+
+**Attached**: {F11060}",1374711656,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+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",1374710220,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_description,resolved
+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",1377889947,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+VisualEditor: Can't re-use a reference belonging to non-default group,Now fixed in master and will be deployed next week.,1377889863,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+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",1377885714,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+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",1377885380,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+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.",1377881801,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+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",1374709740,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-a2p56mvfah4kifyqy327,task_description,resolved
+VisualEditor: Saving fails silently for some blocked users,This was fixed in the fix for bug 52004.,1396032185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a2p56mvfah4kifyqy327,task_subcomment,NA
+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",1374742787,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-a2p56mvfah4kifyqy327,task_subcomment,NA
+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",1374704160,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_description,resolved
+VisualEditor: Thumb images are missing appropriate CSS classes,Now fixed in master and will be deployed in a few minutes' time.,1374793893,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_subcomment,NA
+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",1374792604,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_subcomment,NA
+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",1374705671,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_subcomment,NA
+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",1374705278,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_subcomment,NA
+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}",1374695580,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-ph24e22ltq2s3oztatem,task_description,resolved
+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.",1383848723,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+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",1383813525,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+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.",1383785800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+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 (?),1380836632,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+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.,1380534678,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+"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",1374694260,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_description,resolved
+"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.,1374700983,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_subcomment,NA
+"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",1374700767,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_subcomment,NA
+"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",1374699991,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_subcomment,NA
+"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",1374694774,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_subcomment,NA
+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",1374691440,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_description,duplicate
+VisualEditor: Clicking the hyper link button twice breaks the button.,"
+
+*** This bug has been marked as a duplicate of bug 51404 ***",1383173187,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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""",1374864536,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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.",1374863634,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+VisualEditor: Clicking the hyper link button twice breaks the button.,I was able to reproduce following the steps in comment 3.,1374704173,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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}",1374703953,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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.",1374703277,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+VisualEditor: Clicking the hyper link button twice breaks the button.,"Error screenshot.
+
+**Attached**: {F11890}",1374702882,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+VisualEditor: Clicking the hyper link button twice breaks the button.,I can't reproduce this. Do you see any errors in your JS console?,1374691632,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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 &rlm; 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",1374686820,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-wfbovalkwufxdqplhata,task_description,resolved
+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.",1407753932,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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?",1407753368,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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
+> <span
+> 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 <onlyve>. This solution may be useful for other cases of
+> ""invisible
+> templates"".
+
+I love this proposal.",1383831673,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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 <span dir="""">...
+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 <onlyve>. This solution may be useful for other cases of ""invisible templates"".",1383679171,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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?",1383676142,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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.",1383642046,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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.,1374686999,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, 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' <new line> '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",1374664140,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-zc6v32lm5ytpux3undwt,task_description,resolved
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, 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.",1399418661,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zc6v32lm5ytpux3undwt,task_subcomment,NA
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, etc), leading to corruption, and prevents down arrow button navigation","In addition to <gallery>, 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.",1381624406,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-zc6v32lm5ytpux3undwt,task_subcomment,NA
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, 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.",1374680740,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zc6v32lm5ytpux3undwt,task_subcomment,NA
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, 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'",1374667755,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-zc6v32lm5ytpux3undwt,task_subcomment,NA
+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}",1374655380,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-2siqskyqqgqcynauvs72,task_description,resolved
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,Both of the examples linked to work now.,1405201146,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,Partially mitigated by the above but I believe not fixed. Resetting.,1402533482,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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",1402525633,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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",1402321080,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,*** Bug 54301 has been marked as a duplicate of this bug. ***,1402294829,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,*** Bug 50970 has been marked as a duplicate of this bug. ***,1402294818,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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 .,1377775199,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,"*overlapping blocks, or templates, or whatever, you understood me :)",1377699148,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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.",1377698588,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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",1374630480,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_description,resolved
+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.)",1400621292,PHID-USER-n2ftvsjm34tosq65gpve,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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.",1400619950,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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?)",1400615811,PHID-USER-n2ftvsjm34tosq65gpve,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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. ***,1398102157,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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.",1381187048,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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",1381186917,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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",1378325620,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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. ***,1378247189,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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.""",1376643209,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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)",1375435729,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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. ***,1374880815,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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 ***",1374630794,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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.",1374630602,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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",1374622800,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-zrcmecxwpnqso5zyiauu,task_description,resolved
+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.,1375297527,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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.",1375126356,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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.""""",1374878013,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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.",1374632435,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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.",1374623153,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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",1374604560,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jxtza5wxkt3lvc2yga75,task_description,resolved
+VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog,Now fixed in master.,1374779912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jxtza5wxkt3lvc2yga75,task_subcomment,NA
+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",1374776211,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jxtza5wxkt3lvc2yga75,task_subcomment,NA
+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",1374756861,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jxtza5wxkt3lvc2yga75,task_subcomment,NA
+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]].",1374683040,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jxtza5wxkt3lvc2yga75,task_subcomment,NA
+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",1374589920,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-sqexirvlnm7n526sp3a3,task_description,resolved
+VisualEditor: Language templates replaced by snowmen at Japanese Wikipedia,I think that this was finally fixed in Roan's great re-working of snowmen.,1407061575,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sqexirvlnm7n526sp3a3,task_subcomment,NA
+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",1375214101,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-sqexirvlnm7n526sp3a3,task_subcomment,NA
+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",1375075266,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-sqexirvlnm7n526sp3a3,task_subcomment,NA
+"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",1374568080,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_description,resolved
+"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",1374625642,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+"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",1374621278,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+"VisualEditor: By default, images should not set the alignment",*** Bug 51295 has been marked as a duplicate of this bug. ***,1374619928,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+"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",1374588399,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+"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?,1374588063,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+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",1374514020,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-lui5vpla74335t6r63nr,task_description,resolved
+VisualEditor: Autocompletion for template names doesn't work in RTL,"Done and will be deployed tomorrow. Thanks, Moriel!",1374634378,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lui5vpla74335t6r63nr,task_subcomment,NA
+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",1374518346,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-lui5vpla74335t6r63nr,task_subcomment,NA
+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}",1374510180,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-kjhdlfcx4jhz24dn5jl5,task_description,resolved
+VisualEditor: Location of the inspector menu is wrong for floated content in RTL wikis,Merged and will go out tomorrow.,1374637806,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kjhdlfcx4jhz24dn5jl5,task_subcomment,NA
+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",1374637503,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kjhdlfcx4jhz24dn5jl5,task_subcomment,NA
+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",1374526607,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kjhdlfcx4jhz24dn5jl5,task_subcomment,NA
+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",1374316620,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jvkszokywziqndkikfj4,task_description,resolved
+VisualEditor: [Regression] Dialog panels not scrollable,Done and will be deployed tomorrow.,1374634358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+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",1374605866,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,*** Bug 51810 has been marked as a duplicate of this bug. ***,1374497316,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,Patch by Rillke from bug 51793: https://gerrit.wikimedia.org/r/75083,1374489637,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,*** Bug 51793 has been marked as a duplicate of this bug. ***,1374489509,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,*** Bug 51671 has been marked as a duplicate of this bug. ***,1374331143,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+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",1374319290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,Caused by 8409d16f0f2392cea321aa3d8d6bc692f3f04f27,1374318944,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+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}",1374308460,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-jd5jq4oxcix7nauaawh2,task_description,resolved
+TemplateData: Create an editor for template data (in the wikitext editor),Follow-up in 60158.,1391795279,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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}",1391198497,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.  :)",1391189938,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1391186065,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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",1391177736,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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",1390823433,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+TemplateData: Create an editor for template data (in the wikitext editor),"No, this is the GUI we developed hidden behind $wgTemplateDataUseGUI.",1390431656,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.  :)",1390336136,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1389806818,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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",1386784147,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1375139849,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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",1374777939,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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}",1374776275,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+TemplateData: Create an editor for template data (in the wikitext editor),"Created attachment 12957
+Screenshot of http://tools.wikimedia.pl/~mlazowik/templatedata/
+
+**Attached**: {F11376}",1374775628,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1374510028,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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 <templatedata> 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 <templatedata/> 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",1374495793,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1374489651,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+TemplateData: Create an editor for template data (in the wikitext editor),Tool = something at least as good as the TemplateDataEditor linked above.,1374489443,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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. :)",1374486973,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+"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<br>1"" wraps correctly
+
+""Long text
+1""
+""Long text<br>"" and
+""Long text<br>
+<!--hidden-->"" 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",1374266280,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hbtmtpgjefyo637ujihd,task_description,resolved
+"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",1403047632,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+"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",1402916033,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+"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?",1402837289,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+"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. ***,1395169574,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+"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. ***,1394223928,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+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",1374237180,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lskwjin7vud63rd4ruhi,task_description,declined
+VisualEditor: unlinking via linking tool triggers weird behaviors,"Worksforus, at it.wp. Will re-open if necessary.",1380650852,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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.",1380631760,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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).",1375039918,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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.",1374656653,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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!",1374644511,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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}",1374227460,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-y2l4ooxqksxji4wptopd,task_description,resolved
+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?",1378119303,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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.",1377959027,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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",1377910117,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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",1377901233,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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.""",1374423427,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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}",1374179880,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7rwifffi3m7nv3vjbxms,task_description,resolved
+VisualEditor: Saving fails silently when the database is locked,Fixed and will get deployed in a few minutes' time.,1374676801,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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",1374676554,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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",1374658384,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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?",1374182584,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+VisualEditor: Saving fails silently when the database is locked,"**kwang** wrote:
+
+error while editing source code.
+
+**Attached**: {F11179}",1374180001,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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.",1374179974,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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",1374128220,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-p5bbvutzsk36zk6seh2n,task_description,resolved
+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",1385506388,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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",1384946968,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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.,1381269307,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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.",1378943326,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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.",1374128971,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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.",1374089160,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_description,resolved
+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]]",1426626118,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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]]
+",1426622545,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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]]",1426388603,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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).",1430162161,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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).",1426382771,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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]]
+",1425330752,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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",1374074040,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-usa4c4in3z4ffsufnkoi,task_description,resolved
+VisualEditor: Reverse selections break copy paste functionality,Now merged; will go out with next push.,1377195467,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-usa4c4in3z4ffsufnkoi,task_subcomment,NA
+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",1377195266,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-usa4c4in3z4ffsufnkoi,task_subcomment,NA
+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",1377120336,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-usa4c4in3z4ffsufnkoi,task_subcomment,NA
+VisualEditor: Reverse selections break copy paste functionality,I can confirm this is still happening in Firefox 23/linux,1376732778,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-usa4c4in3z4ffsufnkoi,task_subcomment,NA
+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",1374065460,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-u4mzdxdhi5v6xlyw7zkb,task_description,resolved
+VisualEditor: CTRL+Z occasionally inserts a pawn,I believe these issues are now fixed.,1406599341,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u4mzdxdhi5v6xlyw7zkb,task_subcomment,NA
+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.",1379617320,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-u4mzdxdhi5v6xlyw7zkb,task_subcomment,NA
+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,1374065788,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-u4mzdxdhi5v6xlyw7zkb,task_subcomment,NA
+"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}",1374062040,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rygkkourrlt3am2ziugg,task_description,resolved
+"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.",1449517807,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-rygkkourrlt3am2ziugg,task_subcomment,NA
+"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?).",1401474051,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rygkkourrlt3am2ziugg,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Error: Offset could not be translated to a DOM element and offset: 2409""",Confirmed still happening.,1385386045,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rygkkourrlt3am2ziugg,task_subcomment,NA
+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",1374059640,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_description,resolved
+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.",1383848681,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_subcomment,NA
+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",1383813641,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_subcomment,NA
+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.",1383784994,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_subcomment,NA
+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",1374094589,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_subcomment,NA
+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",1374057840,PHID-USER-5tluooawvjfhtqywnxag,PHID-TASK-qpzhi34lem7nwd6nbsu5,task_description,resolved
+VisualEditor: Too many clicks needed to dismiss inlink editor,This is now merged and will be deployed later.,1375304932,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qpzhi34lem7nwd6nbsu5,task_subcomment,NA
+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",1375304095,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qpzhi34lem7nwd6nbsu5,task_subcomment,NA
+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",1375222020,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qpzhi34lem7nwd6nbsu5,task_subcomment,NA
+"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",1374037140,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hju3hugjlttehugtvu7d,task_description,resolved
+"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.,1383284035,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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",1378291458,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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.",1378127567,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","Now merged and will go out with the next production push, probably tomorrow.",1375145540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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",1375145481,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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",1375143259,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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.,1375139344,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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 + \?",1375071949,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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)",1375071593,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+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",1374029760,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vbuyxcfsri4ye35bdcvl,task_description,resolved
+VisualEditor: Reduce event rapid fire in CE,Yes.,1384939424,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vbuyxcfsri4ye35bdcvl,task_subcomment,NA
+VisualEditor: Reduce event rapid fire in CE,Can we now deem this to have been done?,1381347404,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vbuyxcfsri4ye35bdcvl,task_subcomment,NA
+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",1374009180,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-vs2q4kkygajmjexkudzc,task_description,resolved
+VisualEditor: Typing in Devanagari puts vowels in unexpected places,master looks good to me. Thanks!,1377206151,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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!",1377202382,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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",1377164925,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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",1377027648,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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.",1376935627,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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",1374007020,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-cfoc7zk5vj22ygiycyil,task_description,resolved
+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",1385506391,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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",1384946958,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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.,1381269293,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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.",1374161590,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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.",1374132914,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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.",1374131873,PHID-USER-i5at67w766dqxs6ncxam,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+VisualEditor: Backspace deletes combined character clusters together with diacritics,"Could this be a dupe of -
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49233  ?",1374125163,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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",1374001860,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_description,resolved
+VisualEditor: Don't extend links over wordbreaks,*** Bug 51531 has been marked as a duplicate of this bug. ***,1374679397,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_subcomment,NA
+VisualEditor: Don't extend links over wordbreaks,Fixed and will get deployed in a few minutes.,1374677110,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_subcomment,NA
+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",1374677027,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_subcomment,NA
+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",1374076760,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_subcomment,NA
+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}",1374001560,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_description,resolved
+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.",1377800127,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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.",1377772919,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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 .",1377770479,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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. :-(",1375475243,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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",1375470233,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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 <pre> elements but we should be aware that this is broken, because any element can have white-space:pre attached to it, e.g.
+
+<span style=""white-space:pre"">    Foo</span>
+
+Will now normalise to
+
+<span style=""white-space:pre"">Foo</span>
+
+Long term we should look into just warning the user.",1375449067,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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",1375443506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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
+> 
+> <nowiki> </nowiki>Foo
+> 
+> (previously <nowiki> Foo</nowiki>)
+> 
+> This is the correct behaviour.
+
+Also, with gerrit 76223 VisualEditor users can now edit through <nowiki>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.",1375208057,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,*** Bug 52252 has been marked as a duplicate of this bug. ***,1375203763,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"With bug 50841 we now convert 
+
+[space]Foo
+
+to
+
+<nowiki> </nowiki>Foo
+
+(previously <nowiki> Foo</nowiki>)
+
+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?)",1375201550,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,*** Bug 51509 has been marked as a duplicate of this bug. ***,1374168615,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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 <pre>-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 &nbsp; or if nowikis are acceptable, the spaces can be left alone.  In either case, this kind of edits should hopefully be rare.",1374006352,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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.",1374005921,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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,1374001895,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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",1374000660,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-q5qzozhueiwufmgr5jwq,task_description,resolved
+VisualEditor: Show the <newarticletext> message when creating a new article,Fixed and will get deployed in a few minutes.,1374676711,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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",1374676401,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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",1374659039,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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",1374605847,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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.",1374535182,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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.",1374507374,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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).",1374302681,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+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",1373981940,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eto6zg3t57jsyeutf64w,task_description,resolved
+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.",1408734627,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eto6zg3t57jsyeutf64w,task_subcomment,NA
+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.",1408687329,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eto6zg3t57jsyeutf64w,task_subcomment,NA
+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. ***,1401996119,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eto6zg3t57jsyeutf64w,task_subcomment,NA
+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)",1373982044,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eto6zg3t57jsyeutf64w,task_subcomment,NA
+"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",1373936940,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_description,resolved
+"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.,1375304939,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_subcomment,NA
+"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",1375304098,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_subcomment,NA
+"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. ***,1375303309,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_subcomment,NA
+"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",1375222005,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_subcomment,NA
+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",1373927820,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-5pkp6kncu5pzdahrd6qn,task_description,resolved
+VisualEditor: Transclusion dialog should prevent adding identically-named parameters (and aliases),"I'm going to assume ""yes"" given testing.",1406062458,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pkp6kncu5pzdahrd6qn,task_subcomment,NA
+VisualEditor: Transclusion dialog should prevent adding identically-named parameters (and aliases),Works for me... Has this been fixed since it was reported?,1405980543,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-5pkp6kncu5pzdahrd6qn,task_subcomment,NA
+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",1373927580,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dke6zkvtno2ooulod6bw,task_description,resolved
+VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,*** Bug 51984 has been marked as a duplicate of this bug. ***,1383173187,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,This is now merged and will be deployed later.,1375304925,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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",1375304091,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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",1375222010,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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'.",1374998678,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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.",1374444476,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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.,1374342895,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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.",1374148846,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"Created attachment 12854
+Screenshot of problem
+
+**Attached**: {F11587}",1373927653,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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.",1373927630,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+"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}",1373926620,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6s22kiygdurpmwpk3lqs,task_description,resolved
+"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property",We will deploy this fix today.,1373987077,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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",1373945021,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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.",1373930726,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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.",1373930605,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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",1373929226,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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).",1373928926,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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,1373928143,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","Sometimes 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.",1373910060,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-eddbh3tcvexylixr6tiy,task_description,open
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","we should distinguish between visualeditor and templatedata.
+templatedata provides a syntax to describe the template behavior, and is used not just by visualeditor, but other tools too.
+
+whatever VE decides to do with ""illegal"" values is an interesting question, but TD itself should allow distinction between ""suggested values"" and ""legal values"", because the template syntax itself makes this distinction.  VE can ignore this distinction or not, but TD should provide this information.
+
+suggestedvalues serves templates that use {{#switch, and there are several different behaviors when param value is not present as one of the options: 
+  - the switch may have #default, which does something useful - IOW, an ""unsuggested"" value is still legal
+  - it can have no #default, practically ignoring the value
+  - the #default can trigger an error.
+
+TD syntax should allow better description of the behavior, so, e.g., ""template linting"" tools can detect and flag pages where a template with ""suggested values"" is used with ""unsuggested"" value: it can be an error worth flagging (2nd and 3rd cases above, where suggested values really means legal values), and not flag it for parameters whose behavior match the 1st case. 
+
+this is not a theoretical/hypothetical issue - such tools exist, and are used on several projects (see, e.g., Module:ParamValidator on hewiki and yiwiki).
+
+peace.",1641663466,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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 :)",1615828425,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","This can most certainly be closed via {T271825}. While it's not 100% the same, it should be sufficient to resolve the relevant use case.",1615826667,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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.",1582479107,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","A suggestion from https://www.mediawiki.org/wiki/Topic:Ve06hyihctm4p86n is to allow labels different from the actual value. It can be stored for example with:
+```lang=json
+""params"": {
+	""key"": {
+		""type"": ...,
+		""values"": [
+			{""label"": ..., ""value"": ...},
+			...
+		]
+	}
+}
+```
+Maybe plain strings should also be allowed for convenience, which could be transformed by the extension to
+```lang=json
+{""label"": null, ""value"": ...}
+```
+form. (I’d also suggest to always display the actual value in addition to the label, but that’s up to the consumers, of course.)",1577874176,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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]]",1532906726,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","Is this still on the docket? It's vital. Is there some other way of specifying valid string values in TemplateData (TD)? If not, that would appear to be a large oversight if TD is supposed to help users easily interact with template params",1510282456,PHID-USER-ruf4kh5stzv33ntxol2w,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)",It would also be useful to be able to use a set of possible values provided by some template/module.,1509551476,PHID-USER-6xgsmxxl62mgxypce6oa,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","That's something which would be extremely useful.
+
+I'm currently working on a proposal for ease Wikitionary contribution through templatedata. Such a feature would for example allow to select word category (verb, adjective…). ",1509222111,PHID-USER-6xgsmxxl62mgxypce6oa,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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]]",1483653112,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","Change 263655 had a related patch set uploaded (by Alex Monk):
+[WIP] Add a parameter key to limit possible valid values to a given set
+
+[[https://gerrit.wikimedia.org/r/263655]]
+",1452629730,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)",">>! In T53375#564935, @Krinkle wrote:
+>  params: {
+>   ""key"": {
+>     ""type"": ...
+>     ""values"": [ .. ]
+
+Seems a good way of specifying it, +1",1429186483,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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.",1612418862,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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.",1427614715,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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.",1400616112,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)",*** Bug 52754 has been marked as a duplicate of this bug. ***,1377830925,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","(In reply to comment #2)
+> Ping @TrevorParscal.
+> 
+> Since wikitext template editing will always be possible, we can't (yet?)
+> enforce values in VisualEditor. We can only suggest.
+> 
+> E.g. if a template parameter ""foo"" is specified as values: ['a', 'b']. and
+> wikitext has {{echo|foo=x}}, we need to provide a way to edit that, while
+> still
+> being able to set it to a or b.
+
+The ""normal"" way is a drop-down with the target of the drop-down being a free-entry text field that suggests entries (but does not block other entries).",1377657781,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)",*** Bug 50760 has been marked as a duplicate of this bug. ***,1377559681,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","Ping @TrevorParscal.
+
+Since wikitext template editing will always be possible, we can't (yet?) enforce values in VisualEditor. We can only suggest.
+
+E.g. if a template parameter ""foo"" is specified as values: ['a', 'b']. and wikitext has {{echo|foo=x}}, we need to provide a way to edit that, while still being able to set it to a or b.",1377559666,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","See ""bug 50760 - Support suggested values"" which is quite similar.
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50760",1373968381,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+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
+",1373840940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67oipsmostyhug2737rz,task_description,resolved
+VisualEditor: Set i18n toolbar icons for bold/italics,This is now done; we'll deploy this within the hour.,1373918452,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67oipsmostyhug2737rz,task_subcomment,NA
+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",1373918327,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-67oipsmostyhug2737rz,task_subcomment,NA
+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",1373916753,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-67oipsmostyhug2737rz,task_subcomment,NA
+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",1373810580,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-faltfztxkqc5daxcntnx,task_description,resolved
+VisualEditor: Handle 'meta' templates better,Additional issue with empty HTML elements produced by templates (which are used for metadata) in bug 52551.,1375720301,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,Fixed and will get deployed in a few minutes.,1374676752,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,"Change 75331 merged by jenkins-bot:
+Handle meta-only transclusions as meta items
+
+https://gerrit.wikimedia.org/r/75331",1374676162,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,"I marked this as a dup of bug 49806, not dup of 51420.",1374604232,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+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",1374586930,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+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.,1374586909,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,"
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1374447614,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,Another example given on WP:VEF is {{Link FA}},1374135248,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+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.",1374135077,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+"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",1373764920,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sm4xza7t5teplcefqzij,task_description,resolved
+"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.,1421282222,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+"VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues",Very odd corruption; assigning.,1373816884,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+"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",1373800417,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+"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.",1373765414,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+"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.]",1373765293,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+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",1373723400,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-lufoybqaultvloukxdjz,task_description,resolved
+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",1391655762,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+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",1389677127,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+VisualEditor: Set image alignment in the media dialog,"It's not a problem with right-to-left languages ;)
+
+Removing the tracking bug.",1373915285,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+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",1373897055,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+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",1373896912,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+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.",1373883475,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+"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",1373723100,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_description,resolved
+"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 ***",1403005130,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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.,1401418955,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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. ***,1401418881,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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?,1387304036,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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.""",1375444170,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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. ***,1375298515,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+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",1373672640,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-5am5k4waw47kga4kfuau,task_description,invalid
+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.,1399324087,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5am5k4waw47kga4kfuau,task_subcomment,NA
+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.",1373681941,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-5am5k4waw47kga4kfuau,task_subcomment,NA
+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.",1373680362,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-5am5k4waw47kga4kfuau,task_subcomment,NA
+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",1373656680,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_description,resolved
+tag_summary missing records,That was bug 52077. Closing this.,1382126117,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,"Whatever is causing that (maybe just a misconfigured local filter?), it's most likely not related to this bug.",1374793514,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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).",1374793105,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1374065627,PHID-USER-fuj45iylbizjg3yhehjt,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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",1374038167,PHID-USER-fuj45iylbizjg3yhehjt,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1374013186,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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...,1374009940,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1373998200,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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...",1373998082,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1373924036,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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).",1373909518,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1373887905,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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""
+  <tag>visualeditor</tag>
+  
+  rcid=""590032703"" timestamp=""2013-07-12T00:33:31Z"" 
+  <tag>mobile edit</tag>
+
+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.",1373677187,PHID-USER-fuj45iylbizjg3yhehjt,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,"**swalling** wrote:
+
+Just checked this on-wiki as well. Seems fixed.",1373672247,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,enwiki.tag_summary rebuild is complete.,1373671971,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1373667429,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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",1373662814,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,Was it determined if any other databases apart from en.wp's one were affected?,1373662581,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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)",1373662298,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,"Only seems to affect en.wp right now (works correctly on pl.wp and mw.org, for example).",1373656951,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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",1373632740,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-sojoibzwruxvdv55tvoj,task_description,resolved
+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",1373662141,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sojoibzwruxvdv55tvoj,task_subcomment,NA
+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",1373637959,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sojoibzwruxvdv55tvoj,task_subcomment,NA
+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.",1373637707,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sojoibzwruxvdv55tvoj,task_subcomment,NA
+VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''<sub>''bar''</sub> -> ''foo<sub>bar</sub>''),"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",1373632620,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vq64xxj3d54xo3daemjh,task_description,resolved
+VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''<sub>''bar''</sub> -> ''foo<sub>bar</sub>''),"
+
+*** This bug has been marked as a duplicate of bug 49873 ***",1373711757,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vq64xxj3d54xo3daemjh,task_subcomment,NA
+VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''<sub>''bar''</sub> -> ''foo<sub>bar</sub>''),Also https://en.wikipedia.org/w/index.php?title=Frobenius_solution_to_the_hypergeometric_equation&curid=16407499&diff=563915886&oldid=561013687,1373632675,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vq64xxj3d54xo3daemjh,task_subcomment,NA
+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",1373598840,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-toxebubahyyw4rmtx4vj,task_description,resolved
+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",1395164023,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-toxebubahyyw4rmtx4vj,task_subcomment,NA
+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",1395094433,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-toxebubahyyw4rmtx4vj,task_subcomment,NA
+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",1373533020,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_description,declined
+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.",1374675988,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"major->minor, so it isnt red anymore.",1374650680,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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)",1374644987,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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. :-)",1374643164,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,Resolved-Fixed -> Resolved->Invalid.  What the?!,1374642996,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,Now resolved; thanks all :).,1374601920,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1374595261,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1374588009,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1374338671,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1374309537,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1373537154,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) 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
+<div class=""reflist references-small"" style><references /></div>
+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",1373499540,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-re6qm3cualjp5dczcmlc,task_description,resolved
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) 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).",1383140692,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) into wikitext,I can't reproduce this now using a simple test case.  Has it still been happening on pt.wp?,1383133476,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) into wikitext,"This happened again:
+https://pt.wikipedia.org/wiki/Haroldo_Palo_Jr.?diff=36430552",1374085008,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) 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.",1373760927,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) 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]]:
+> 
+> <h2 style=""cursor:help"" title=""Esta seção não é editável por razões técnicas.
+> Edite a página toda em vez disso."">Referências</h2>
+> <div class=""reflist references-small"" style=""""><references
+> group=""""></references></div>
+> 
+> 
+> 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 <h2>).",1373658096,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) into wikitext,"I don't know if this is relevant, but the same code ""{{referências}}"" expands to something different on [[pt:special:ExpandTemplates]]:
+
+<h2 style=""cursor:help"" title=""Esta seção não é editável por razões técnicas. Edite a página toda em vez disso."">Referências</h2>
+<div class=""reflist references-small"" style=""""><references group=""""></references></div>
+
+
+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",1373500632,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+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",1373498580,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_description,resolved
+VisualEditor: Double-click on a parameter in the selection menu should insert it,*** Bug 51165 has been marked as a duplicate of this bug. ***,1377527402,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_subcomment,NA
+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.",1373932741,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_subcomment,NA
+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",1373932430,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_subcomment,NA
+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",1373922497,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_subcomment,NA
+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",1373495580,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ft4ssckvycvjlzjy3fax,task_description,resolved
+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. ***,1373928303,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,Fixed and merged.,1373926253,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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",1373926221,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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",1373925628,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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",1373499407,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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.",1373498121,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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 &#9817).  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.",1373498038,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+"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",1373485740,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-nilflssh5x72tinfk7a6,task_description,resolved
+"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.",1394073325,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nilflssh5x72tinfk7a6,task_subcomment,NA
+"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).",1375325511,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nilflssh5x72tinfk7a6,task_subcomment,NA
+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",1373468880,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qjailuyl4kenb2ytqa5a,task_description,resolved
+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 ***",1373928303,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qjailuyl4kenb2ytqa5a,task_subcomment,NA
+"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",1373408400,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-sby6wjdxcouq3g5mq67p,task_description,resolved
+"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.,1373421287,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+"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",1373421247,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+"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",1373412771,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+"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",1373410794,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+"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",1373409417,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+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",1373366640,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-l2askobdymn34t55t5lm,task_description,resolved
+VisualEditor: Resizing an image without an explicit size doesn't work,"
+
+*** This bug has been marked as a duplicate of bug 50645 ***",1374106684,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l2askobdymn34t55t5lm,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Attaching screenshot...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373337720,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_description,resolved
+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",1390877338,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+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",1390853505,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,*** Bug 52205 has been marked as a duplicate of this bug. ***,1380221526,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,Same as bug 52205?,1380219226,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+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.",1373337951,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Created attachment 12794
+<h1> protrudes into wrapped toolbar in non-HD stylesheet
+
+**Attached**: {F11631}",1373337835,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Created attachment 12793
+Wrapping toolbar correctly pushes down <h1> in HD stylesheet
+
+**Attached**: {F11630}",1373337806,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+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",1373307420,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-it7sgrllp5k6su66uukw,task_description,resolved
+TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,Per report. ;-),1402013615,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Confirmed fixed in 1.24wmf7, yay :-)",1402012066,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1400886803,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1400866371,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1400865643,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1400865567,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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.",1400864330,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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?,1399842534,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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.",1395417398,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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.",1380898648,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1380867107,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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}} }} ).",1374776002,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1374641826,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,*** Bug 51791 has been marked as a duplicate of this bug. ***,1374641783,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1373297880,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-mip6kupgxcxydyy26dwa,task_description,resolved
+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",1380474885,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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 <p> 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.",1380309457,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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",1380309327,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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.",1380214427,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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),1379886743,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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.",1376330120,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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. ***,1375199198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,Looking into it now.,1374627567,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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",1374082150,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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. ***,1374079615,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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. ***,1374079583,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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.",1373444097,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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?,1373421989,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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",1373295960,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-uxowmsznm5ykbiez7tm2,task_description,resolved
+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.",1403727795,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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.",1403715476,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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.",1395196799,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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 .",1391011992,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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.",1377807543,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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, ]]<nowiki/>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.",1374080214,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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|<nowiki/>]][[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",1373870516,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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'.",1373850602,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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""?",1373319371,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+Extension tags are not nowiki escaped during serialization.,"Typing certain tag based code into VE such as:
+
+<math>1+2=3</math>
+<ref>Hi</ref>
+
+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",1373295960,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-7rcg5rkjl6kyyl4elbfa,task_description,resolved
+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",1373307982,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7rcg5rkjl6kyyl4elbfa,task_subcomment,NA
+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",1373301144,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7rcg5rkjl6kyyl4elbfa,task_subcomment,NA
+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",1373238780,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-ur6l6l2ezqzug2nab347,task_description,resolved
+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.,1375298816,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ur6l6l2ezqzug2nab347,task_subcomment,NA
+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.",1373351277,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ur6l6l2ezqzug2nab347,task_subcomment,NA
+VisualEditor: Selection highlight for templates/etc. mis-placed,*** Bug 50991 has been marked as a duplicate of this bug. ***,1373351191,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ur6l6l2ezqzug2nab347,task_subcomment,NA
+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",1373232900,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-z5vtizhnd7zq6vobiqci,task_description,resolved
+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",1377734475,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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. ***,1377187521,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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.,1376519672,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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",1376519264,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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?",1376517055,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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.",1376507435,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,confirmed on Arch linux with FF 22.,1373233082,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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",1373232060,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-kt3assypvj632tuitmf6,task_description,resolved
+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",1391915675,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kt3assypvj632tuitmf6,task_subcomment,NA
+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}",1373206260,PHID-USER-ixwg3kf22idjy7x4ncxf,PHID-TASK-vgr63prhj7eik7b2qkwd,task_description,resolved
+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",1383255765,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vgr63prhj7eik7b2qkwd,task_subcomment,NA
+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",1383180900,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vgr63prhj7eik7b2qkwd,task_subcomment,NA
+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}",1373209810,PHID-USER-ixwg3kf22idjy7x4ncxf,PHID-TASK-vgr63prhj7eik7b2qkwd,task_subcomment,NA
+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}",1373208580,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-vgr63prhj7eik7b2qkwd,task_subcomment,NA
+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",1373101500,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-he62ku3noedhtzp55bhf,task_description,resolved
+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.,1415382971,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-he62ku3noedhtzp55bhf,task_subcomment,NA
+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.",1414104265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-he62ku3noedhtzp55bhf,task_subcomment,NA
+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}",1378792955,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-he62ku3noedhtzp55bhf,task_subcomment,NA
+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",1373091660,PHID-USER-yif6nz5uhka5cnltixpc,PHID-TASK-ofaluihol767l3yg5fjw,task_description,resolved
+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 ***",1373145698,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ofaluihol767l3yg5fjw,task_subcomment,NA
+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.",1373145158,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ofaluihol767l3yg5fjw,task_subcomment,NA
+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.",1373093279,PHID-USER-yif6nz5uhka5cnltixpc,PHID-TASK-ofaluihol767l3yg5fjw,task_subcomment,NA
+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 </p><img></img><p> rather than just the image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373080620,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4v36rjb5p4c3fhjflpoq,task_description,invalid
+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?).,1377894433,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4v36rjb5p4c3fhjflpoq,task_subcomment,NA
+VisualEditor: Inspecting image immediately after inserting it causes exception,*** Bug 51863 has been marked as a duplicate of this bug. ***,1374624697,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-4v36rjb5p4c3fhjflpoq,task_subcomment,NA
+"<nowiki> 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:
+
+<p>Hello my [[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].</p>
+
+… turns into:
+
+<p>Hello my <nowiki>[[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].</nowiki></p>
+
+… whereas ideally it should be minimal rather than maximal:
+
+<p>Hello my <nowiki>[[</nowiki>name<nowiki>]]</nowiki> is Julian and I live in the city of Rochester, New York with my friend Sandy; we write <nowiki>[[</nowiki>books<nowiki>]]</nowiki>.</p>
+
+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",1373063340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qf4vt6acq5wtvvlwympv,task_description,resolved
+"<nowiki> 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.",1374182135,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)",This will likely be deployed later today.,1374181853,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1374181486,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1374033113,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1373426923,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1373411404,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1373395088,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki>-{ }-</nowiki> 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.",1373395037,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki>-{ }-</nowiki> 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...",1373390406,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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).",1373390310,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki>[[foo]]</nowiki>.  ""Closely occurring"" will be heuristic based, say within X chars.",1373388769,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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]] ==> &#91;&#91;Foo&#93;&#93;
+> 
+> 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.",1373388668,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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...",1373344988,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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]] ==> &#91;&#91;Foo&#93;&#93;
+
+and the like.  Am I missing something that makes this problematic?",1373343101,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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?",1373340138,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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
+
+- <nowiki>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</nowiki>
+
+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.",1373064929,PHID-USER-fuj45iylbizjg3yhehjt,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki>..</nowiki> 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.",1373064668,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki> on ""normal"" text disabled language conversion on it too; we may want to <nowiki> wikitext meta characters only.",1373064371,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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.",1373064090,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+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 ) {
+	$( '<style>' , {type: 'text/css', rel: 'stylesheet' } )
+	.text( css )
+	.appendTo ('head' );
+}
+
+// really no need to return anything: the single callsite ignores 
+// the return value anyway. anywho, you can prepend ""return"" 
+// to make it behave more like existing code if you really want to...
+
+
+peace.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=563037747#Heavy_Javascript_load_after_loading_some_articles.
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49935
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51073",1373056800,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j7v3ex7edi7dypukus5m,task_description,resolved
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #21)
+> It's resolved technically, 
+
+Closing this one then,
+
+> but we want to write proper documentation and
+> tests
+> for the fix. Assigning to myself.
+
+and split this to bug 54364, to clarify status.",1379659587,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"What's the progress on this, Amir?",1375774753,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"It's resolved technically, but we want to write proper documentation and tests for the fix. Assigning to myself.",1374249445,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Why is this still open?
+as far as i can see, the patch solved the issue. is there any report about any more problems here? 
+is anyone expected to do anything more regarding this issue? 
+if it's not closed now, is there any chance of this getting closed ever?
+
+peace.",1374249308,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"What about using .eachAsync (https://git.wikimedia.org/blob/mediawiki%2Fcore.git/HEAD/resources%2Fjquery%2Fjquery.async.js) instead of the .each loop over $( '*[lang], [style], [class]' ) ? Perhaps this is not the solution for this bug, but for bug 49935, but I'm not going to read through all those comments, and I think the .eachAsync is worth a try.",1373615617,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,*** Bug 51070 has been marked as a duplicate of this bug. ***,1373495384,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"The above patch makes the webfonts code about 4x faster in my testing. While it is an improvement, it does not completely remove the problem. To go further we need to reconsider the logic instead of just optimizing the current code.
+
+This patch is already on beta labs, can be tested for example in http://en.wikipedia.beta.wmflabs.org/wiki/Barack_Obama and is planned for deployment around 1800 UTC today.",1373472779,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Change 72967 merged by jenkins-bot:
+Update jquery.webfonts from upstream
+
+https://gerrit.wikimedia.org/r/72967",1373471100,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Change 72967 had a related patch set uploaded by Amire80:
+Update jquery.webfonts from upstream
+
+https://gerrit.wikimedia.org/r/72967",1373470044,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #9)
+> SpeedyGonsales: This bug report is specifically and only about ""Loading a
+> page
+> which requires many fonts causes high CPU load"". If you want to generally
+> talk
+> about ""preferences for new things"" or what MediaWiki should be, please do
+> that
+> on some forum or Village Pump. Thanks for your understanding.
+
+it is unfortunate that ""some forum or village pump"" where the people responsible for the content of wikimedia deployment are actually listening, does not exist.
+
+there is another bug on bugzilla ( bug 46306 ), requesting/demanding a kill switch for ULS. this bug was closed with ""resolved/wontfix"".
+
+yet another open bug ( bug 51070 ) is requesting/demanding to disable ULS on enwiki. this one was not closed with ""wontfix"", but could have been just as well.
+
+so complaining about these demands/requests spilling into other bug reports is somewhat unfair, IMO.
+
+peace.",1373462060,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Just a note that the Language Engineering team responsible for ULS will be holding an office hour later today, at 17:00 UTC on
+#wikimedia-office (on Freenode): http://www.mail-archive.com/wikitech-l@lists.wikimedia.org/msg69718.html",1373455470,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,Also reported at pl.wp: https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#Ostrze.C5.BCenie:_Skrypt_nie_odpowiada,1373454616,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Eduard: I can understand frustration, but no need for rhetorical questions, plus ""I wasn't heard in the right place, so I tried again in some other, wrong place"" is not a good argument.
+Tools (like bugtrackers, mailing lists, Gerrit) serve purposes and have dedicated audiences. Bugzilla is a technical bugtracker for bug reports that refer to specific codebases. It's not for meta-level discussions on development policies, plus from experience in other open source projects I can assure you that the more comments unrelated to a bug there are in bug reports, the more devs will (understandably) also start ignoring bugmail and bug reports. I assume that's not wanted by anybody, and that's why I explained how to avoid that.",1373452499,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Since one is ignored ""on some forum or Village Pump"" (*) one tries other ways to voice one's opinion. Is it surprising that people then try it on Bugzilla where one has at least slight chances a dev will peek at one's message an comment on them?
+
+* e.g. http://www.mediawiki.org/wiki/Thread:Talk:Universal_Language_Selector/Disabling_ULS or http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#.22Opt_out.22_of_VE_needed_under_preferences",1373448080,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #8)
+
+SpeedyGonsales: This bug report is specifically and only about ""Loading a page which requires many fonts causes high CPU load"". If you want to generally talk about ""preferences for new things"" or what MediaWiki should be, please do that on some forum or Village Pump. Thanks for your understanding.",1373447177,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"If you ask me having ""disable switch"" (""kill switch"") in user preferences is a
+must for almost any new things in MediaWiki UI.
+
+If we are unable to alter closed OS (e.g. Windows or Mac) but are able to alter 
+open source one (Linux), MediaWiki should be smart and offer ""disable switches"" 
+for new things. ULS is a good idea, but the same way I like to have ""kill 
+switch"" for VisualEditor :) (""Remove VisualEditor from the user interface"" in Gadgets), I agree there should be one for ULS, period.",1373439569,PHID-USER-3hahyxmftu2sew3v6v6w,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #5)
+> ULS contains quite a lot of new JavaScript and CSS code, so it is reasonable
+> to
+> expect that a close scrutiny of the code will reveal some measure of
+> duplicate
+> work and various other performance problems. It's good that you've dug into
+> the
+> code and pinpointed some specific problems, but please be less adversarial.
+> Measuring and optimizing client-side performance is hard enough to do when
+> you
+> aren't under attack; calling a developer's code ""asinine"" or ""disgusting"" is
+> not likely to make it any easier.
+
+you are correct that my style is/was a bit abrasive, and for this i apologize. however, the ULS team demonstrated pretty bad behavior of its own: please review the way Siebard responded on bug 49935 .
+in addition, turning it on on many wikis before cleaning the very serious performance issues (and causing browsers to freeze _is_ very serious issue), and then arguing that this thing should not have a disable switch in user preference is just wrong.
+
+peace.",1373437720,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"i think you missed the main point: when we call ""load"" with a font family such that this.getCSS() returns false (e.g. ""sans-serif"" on my browser), we do not cache the result. calling getCSS() is orders of magnitude more expensive than the search, regardless of whether the search is done the right way (through hash) or the wrong way (through $.inArray).
+
+as to profiling: the real test is to have ~20 entries in the font table (like in [[en:Japan]]), and then measure how long does it take to look for a font _which is not in the list_, which is what happens today, thanks to the problem mentioned above. you'll see that the search takes significantly longer than it should.
+
+still, the main problem is not the inefficient search, but rather calling getCSS thousands (or tens of thousands - depends on the page content) of times instead of once per each font family present on the page.
+
+as to why we call ""load"" so many times: easy. set a breakpoint, and follow the call stack upward until you'll find the call that's inside an .each() loop.
+
+
+peace.",1373437177,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #1)
+> 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.
+
+I've only noted a single repaint in Chrome Dev Tools on https://en.wikipedia.org/wiki/Tower_of_babel, and I'm not sure yet if it's attributable to ULS. But any form of DOM access is expensive, so the recommendation above is entirely sound.
+
+> the function ""load"" is also asinine, and can cause a high load:
+> 
+> it has two problems: one of them is using $.inArray() to test whether this
+> fontface was already loaded: this means linear search on the array every
+> single time
+
+Hash tables lookups are worse than linear searches for arrays of this size due to the cost of computing the hash and the relatively poorer locality. (In fact, modern JS engines don't even implement property lookups as hash tables, but I figure that was what you had in mind when you recommended hasOwnProperty instead of $.inArray).
+
+https://en.wikipedia.org/wiki/Tower_of_babel has four fontFamilies: ""Amiri"", ""Akkadian"", ""AbyssinicaSIL"", and ""CharisSIL"". I used this to profile object vs. array lookup:
+
+> var myArray = [""Amiri"", ""Akkadian"", ""AbyssinicaSIL"", ""CharisSIL""];
+> console.time('$.inArray'); for(var i = 0; i < 10000; i++) $.inArray('abc', myArray); console.timeEnd('$.inArray');
+$.inArray: 18.029ms
+> var myObj = {""Amiri"": null, ""Akkadian"": null, ""AbyssinicaSIL"": null, ""CharisSIL"": null};
+> console.time('hasOwnProperty'); for(var i = 0; i < 10000; i++) myObj.hasOwnProperty('abc'); console.timeEnd('hasOwnProperty');
+hasOwnProperty: 13.161ms
+
+The difference per call works out to just under half of one millionth of a second, certainly not enough to warrant calling either approach 'asinine'. I am running a recent build of Chromium, but I'd wager the difference even for older browsers would not cross the threshold of significance.
+
+It is a bit bizarre that load() has to be called 877 times on that page, though. That should be investigated.
+
+ULS contains quite a lot of new JavaScript and CSS code, so it is reasonable to expect that a close scrutiny of the code will reveal some measure of duplicate work and various other performance problems. It's good that you've dug into the code and pinpointed some specific problems, but please be less adversarial. Measuring and optimizing client-side performance is hard enough to do when you aren't under attack; calling a developer's code ""asinine"" or ""disgusting"" is not likely to make it any easier.",1373414464,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"I've requested ULS be disabled, this has taken too long, it's annoying ppl without reason.
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51070",1373404117,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Why was this set back to UNCONFIRMED?  Lots of people have experienced this, and kipod has even identified the fix.",1373267032,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"P.S: i used ""abnormal"" to signify that getCSS() returnd false, when called with this font family and variant ""normal"". i do not think this is a good name - maybe ""empty"" of ""builtin"" or something similar will be better, as long as one can be confident it's not a valid fontFamily name. it has to eveluate as boolean true, though, so you can;t use false or empty string.
+
+alternatively, false can work, as long as you modify the first line to
+
+if ( this.fonts.hasOwnProperty( fontFamily ) )
+
+so the thing becomes
+
+load: function( fontFamily ) {
+    if ( this.fonts.hasOwnProperty( fontFamily ) )
+        return this.fonts[fontFamily];
+    var styleString = this.getCSS( fontFamily, 'normal' );
+    if ( styleString ) {
+        injectCSS( styleString );
+        return this.fonts[fontFamily] = true;
+    }
+    return this.fonts[fontFamily] = false;
+}
+
+(for brevity, assign and return on one line - don't do it in real life).
+
+peace.",1373059269,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"the function ""load"" is also asinine, and can cause a high load:
+
+it has two problems: one of them is using $.inArray() to test whether this fontface was already loaded: this means linear search on the array every single time (that is, for every single html element with either ""lang"", ""style"" or ""class"" attributes on the page!), and for pages with large number of elements, this can be significant. whats more, there is no reason not to add the font family to the list even when it's not found, to save us some work with future elements with same font family.
+
+even worse, when getCSS() returns ""false"" (which it does for 99% of the elemnts, e.g. when fontFamily is sans-serif), we don't mark this font family as ""tested"", so when we find the next element with sans-serif, we do all this work again.
+
+from performance POV, this is atrocious.
+
+
+here is a better version of load() - 100% untested.
+
+load: function( fontFamily ) {
+	if ( this.fonts[fontFamily] ) 
+		return this.fonts[fontFamily] != ""abnormal""; 
+// does the font have ""normal"" face?
+
+	var styleString = this.getCSS( fontFamily, 'normal' );
+	if ( styleString ) {
+		injectCSS( styleString );
+		this.fonts[fontFamily] = true;
+		return true;
+	}
+	// Font does not have ""normal"" face.
+	this.fonts[fontFamily] = ""abnormal"";
+	return false;
+}
+
+
+note that ""this.fonts"" here is an object rather than an array (to save the linear searches), so it should be initialized to  {} rather than [].
+
+peace.",1373058592,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"If a user hits the spam blacklist they VE responds merely by informing them ""Error: Invalid error code"". This is...not helpful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1373053740,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_description,resolved
+VisualEditor: Add support for spam blacklist errors in save dialog,Fixed and will be going out in a few minutes.,1374016034,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"Change 73964 merged by jenkins-bot:
+mw.ViewPageTarget: Add support for spam blacklist
+
+https://gerrit.wikimedia.org/r/73964",1374015128,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"Though I knew that the SpamBlacklist has logic in place for returning multiple urls (bug 30332, Ia951d5795c5cedb) it didn't seem to work.
+
+Apparently it does work now. I can't consistently reproduce it only giving one. I'll presume it was an error on my part or an edge case in the regex SpamBlacklist is using and complex wikitext as input.
+
+I've amended the patch set to display multiple urls separated by comma if there is more than one.",1374010951,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"Change 73964 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Add support for spam blacklist
+
+https://gerrit.wikimedia.org/r/73964",1373983650,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"So we get the matched url from the API. Ideally we'd get a usable message as well.
+
+Given the following sample (and latest mediawiki/core and SpamBlacklist configured with [[m:Spam_blacklist]])
+
+
+* [http://cl.ly/foo/?bar=%22%3Equ%3Cb%3Eu%3C%2Fb%3Ex%3Ca%20href%3D%22 d]
+* [http://fidosoft.de fidosoft]
+
+index.php?action=submit gives the following:
+
+> The text you wanted to save was blocked by the spam filter. This is probably caused by a link to a blacklisted external site.
+> The following text is what triggered our spam filter: http://fidosoft.de and http://cl.ly
+
+These are constructed in EditPage::spamPageWithContent by the ""spamprotectiontext"" and ""spamprotectionmatch"" messages respectively, which are actually in mediawiki core. The latter message takes $1 as parameter and EditPage.php sets that to the result of Language::listToText( Array ).
+
+The API gives:
+
+        ""edit"": {
+            ""spamblacklist"": ""http://cl.ly"",
+            ""result"": ""Failure""
+        }
+
+For some reason it isn't getting the second url? The SpamBlacklist API hook looks like it is doing `implode( '|', Array )` but aside from an array being nicer than a pipe-separated list, we're not getting either. Only the first url is returned.
+
+So either:
+
+1) SpamBlacklist needs to provide a processed message
+
+or:
+
+* SpamBlacklist needs to provide both urls, not just the first (I tested latest master, SpamBlacklist@3390081e4c6). Though this bug should be fixed either way, if we don't get a processed message, needing both is a blocker.
+* We'll load these 2 core messages as part of ve.init.mw.ViewPageTarget
+* We'll need an equivalent of Language::listToText in core mediawiki.language.js (though I suppose join(', ')  could do meanwhile).",1373983097,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"**joedecker** wrote:
+
+Sounds like y'all have screen shots, but for those of us playing the home game, when I press ""Save Page"" on a blacklist-blocked edit, that window (with the edit summary, etc.) stays up, and ""Error: Unknown error"" appears below the edit summary box, to the left of and slightly higher than the Review your edits/Save page buttons--the latter inactive.
+
+MacOSX/Chrome 28.0.1500.71, tested with an examiner.com URL at [[Chad Griffin]] with an incognito window/logged out.",1373952568,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"Created attachment 12821
+Developer console dump
+
+A very helpful user in #wikipedia-en-help gave me this screenshot of what we get back from the API when TitleBlacklist rejects an edit.
+
+**Attached**: {F11276}",1373495540,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,*** Bug 51139 has been marked as a duplicate of this bug. ***,1373495139,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"Quote: Using Firefox 19.0.2 on Windows Vista, editing Relativity Media. Find ""subsidairies"", right-click, select ""subsidiaries"". The word appears changed, but the ""Save"" button is not activated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63462
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63395
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59748",1373050560,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_description,resolved
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"As far as I can tell, these issues have all been fixed now. However, there's bug 72929 which I've opened for a new issue that's developed in the past few weeks.",1415058499,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"I have issues with this locally as well (Iceweasel/Firefox 24.4.0 with VE 3b3a66763ade397b857e35efe8990ac217e5d54c , in debug mode.
+
+In my case, when I try correct the word, it does change in that spot (fixing the misspelling), and the save button enables.  However, the change also appears at the beginning of the document. In this case the required spelling fix was adding an 'r' (occurence. to occurrence), so an 'r' ended up at the beginning of the ContentEditable.
+
+However, in Review Changes (and the actual save), it then drops the original correction, and *only* puts the wrong edit at the beginning.",1399014057,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"Tried to duplicate this with FF 28 on a variety of typos on different pages.  Ran into Bug 63395 a lot, but was able to save after using FF autocorrect to alter the typo text. (On a side note, hilariously, FF autocorrect suggests that ""autocorrect"" should be changed to ""autocrat"":))",1398191795,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,*** Bug 52372 has been marked as a duplicate of this bug. ***,1398187598,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"No i don't know, it's a report from the VE/Feedback page.",1373157962,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,(Assigning to me absent confirmation that this problem is reproducible.),1373157358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"(In reply to comment #0)
+> Quote: Using Firefox 19.0.2 on Windows Vista, editing Relativity Media. Find
+> ""subsidairies"", right-click, select ""subsidiaries"". The word appears changed,
+> but the ""Save"" button is not activated.
+
+Odd. I get the save dialog activated on making a spelling-correction changes in both Chrome and Firefox, including on that particular word in that particular page. Saved example: https://en.wikipedia.org/w/index.php?title=Relativity_Media&diff=563012676&oldid=559815961
+
+Is the user using a non-standard way of doing the spell-correcting, do you know?",1373052311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Template inspector before closing
+
+Wikilinks like [[Foo|Bar]] are shown expanded in template inspector after closing it, see screenshots. 
+
+Steps to reproduce:
+
+1. Edit a template which has wikilinks like [[Foo|Bar]] as a parameter value
+2. Close the template inspector, with or w/o changes does not matter.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/VRB_H_2/3
+
+**Attached**: {F11204}",1373030040,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-js6dahlv3jujgj6b2lzv,task_description,resolved
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"We've now fixed this in master, and will back-port to production.",1373559177,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Change 73173 merged by jenkins-bot:
+Prevent escaping of piped links in wikitext parameters
+
+https://gerrit.wikimedia.org/r/73173",1373558760,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Change 73173 had a related patch set uploaded by Esanders:
+Piped links in wikitext parameters getting escaped
+
+https://gerrit.wikimedia.org/r/73173",1373553974,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,This is a wikitext escaping bug in VE,1373553234,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Screenshot of different phases:
+
+http://cl.ly/image/1X0I281n1n0G
+1) PHP rendering on Read
+2) VE initial rendering after Edit
+3) VE rendering after opening Template dialog and making no changes and clicking Apply changes
+
+Dirty diff: http://cl.ly/image/241h1I3T1d2d",1373547246,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"It doesn't show in the diff, it only shown in the live rendering in VisualEditor.",1373547049,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,Can you create a broken diff on that article for me?,1373546964,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"As can I, hence the duplicate bugs. Firefox 22, Windows 7.",1373544903,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"(In reply to comment #4)
+> Can't reproduce this at the example URL.
+
+I can still reproduce it :-(",1373544652,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,Can't reproduce this at the example URL.,1373543860,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,*** Bug 51014 has been marked as a duplicate of this bug. ***,1373521095,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,*** Bug 50909 has been marked as a duplicate of this bug. ***,1373354186,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Created attachment 12761
+Template inspector after closing
+
+**Attached**: {F11205}",1373030118,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Break lines for TemplateData description in template inspector,"Screenshot
+
+The text of the TemplateData description should have an line break (wrap into span and style per CSS?) in the template inspector.
+
+Longer descriptions flows out of the template inspector box, see screenshot.
+
+Related: Bug 50656 - Parse wikicode and/or HTML in interface text
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11203}",1373028960,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-6tlgztl4hagkm2r7xhiz,task_description,resolved
+VisualEditor: Break lines for TemplateData description in template inspector,"This is now fixed in master and will be deployed soon, probably tomorrow.",1373420952,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6tlgztl4hagkm2r7xhiz,task_subcomment,NA
+VisualEditor: Break lines for TemplateData description in template inspector,"Change 72863 merged by jenkins-bot:
+Make parameter search widget have a horizontal limit
+
+https://gerrit.wikimedia.org/r/72863",1373420566,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6tlgztl4hagkm2r7xhiz,task_subcomment,NA
+VisualEditor: Break lines for TemplateData description in template inspector,"Change 72863 had a related patch set uploaded by Trevor Parscal:
+Make parameter search widget have a horizontal limit
+
+https://gerrit.wikimedia.org/r/72863",1373415980,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6tlgztl4hagkm2r7xhiz,task_subcomment,NA
+VisualEditor: Add close icon to page notices fly-out,"At the moment the only way to close a page notice is to click on the interface element that launches them - which feels somewhat counterintuitive. Could we have a little close button in the notices themselves?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373028000,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-p53a3hhm2h3bhitmo2np,task_description,resolved
+VisualEditor: Add close icon to page notices fly-out,We did this as part of the fixes to the toolbar.,1383279877,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p53a3hhm2h3bhitmo2np,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"This happened on MediaWiki, he.wiki and en.wiki on Chrome.
+
+Open some article for editing (preferably a long one so the effect is seen)
+add some text in the middle or end, mark it and make it a ""Heading"". 
+
+Observed result: The text turns into a heading, but the entire edit section scrolls up to the top of the page. This is especially annoying when the page is long and when the edit is done in the middle.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1373007960,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_description,resolved
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),This is now fixed by the above commit; we'll get it deployed soon. Sorry for the disruption.,1373414274,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"Change 72768 merged by jenkins-bot:
+Affordances for MenuWidget to be optionally focusable.
+
+https://gerrit.wikimedia.org/r/72768",1373413453,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"Change 72768 had a related patch set uploaded by Robmoen:
+Affordances for MenuWidget to be optionally focusable.
+
+https://gerrit.wikimedia.org/r/72768",1373400275,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),*** Bug 50860 has been marked as a duplicate of this bug. ***,1373157160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"Confirmed in Chrome, Safari and not in Firefox, for whatever reason.",1373048007,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"I just checked the editor on Firefox 22.0, and it does not scroll there (works as expected). The bug seems to be in Chrome only. 
+
+If it helps, that's the UserAgent for my Chrome browser:
+
+ Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36",1373009332,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+"VisualEditor: Move “add parameter” button to alongside the search field, not below the results list, so it can be found","**Author:** `turingt`
+
+**Description:**
+At the Transclusion dialog, after a click or double-click on the chosen parameter, nothing happens. Is the user expected to click on the ""Add parameter"" label at the top? To press Enter? To read the user guide for instruction on how  ? None of these steps help.
+
+This is a usability bug - the actual button is hidden below the fold, at the end of a very long list that is not intended to be scrolled through, and thus hard to discover. The button should be always visible in the dialog - otherwise, the dialog becomes unusable with long lists of parameters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372974060,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mlttagm5jcb3oqt5j734,task_description,resolved
+"VisualEditor: Move “add parameter” button to alongside the search field, not below the results list, so it can be found","This issue is now fixed (or, rather, the button is no longer needed), as we've gone instead with single-click-to-insert, which will be deployed in the next few minutes.",1373932787,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mlttagm5jcb3oqt5j734,task_subcomment,NA
+"VisualEditor: Move “add parameter” button to alongside the search field, not below the results list, so it can be found","Change 73865 merged by jenkins-bot:
+Single-click insertion
+
+https://gerrit.wikimedia.org/r/73865",1373932432,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlttagm5jcb3oqt5j734,task_subcomment,NA
+"VisualEditor: Move “add parameter” button to alongside the search field, not below the results list, so it can be found","Change 73865 had a related patch set uploaded by Trevor Parscal:
+Single-click insertion
+
+https://gerrit.wikimedia.org/r/73865",1373922494,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mlttagm5jcb3oqt5j734,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Especially when a template has many parameters;
+scrolling until you find the actual button to add them,
+having to add them one by one and having to do so by clicking each time on the name of the template itself to get to the list again, it's confusing users.
+There's already a bug about mandatory parameters not being enforced; I am not sure of the behaviour related to the order of the parameters, but it would be great if the editor could keep them in the same order they're being chosen with. Thanks :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372970700,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_description,invalid
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)",There is no longer such a button (as of a week ago).,1374257794,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Created attachment 12830
+Screenshot of how it used to be
+
+Note that though this is how it was. It was also true that when the text in the input field was very long (like, very very long, as long as the dialog is wide) the button would jump to *below* the parameter list (as opposed to directly below the input field or just stay where it was).
+
+
+I propose that we either keep the current behaviour of the input field having a fixed width, but making sure that width is without the width of the ""Add"" button so that that one always stays where it should be (similar to having the ""Go"" button of a search field next to the input and not at the bottom of a variable-length and scrollable list of results).
+
+Alternatively we could bring back the dynamic-width behaviour but when we'd still need to make sure it doesn't go wider than the width allotted to keep the button on the same line as well.
+
+**Attached**: {F11129}",1373539291,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Created attachment 12829
+Screenshot of the problem (current version)
+
+No add button anywhere in sight, users are likely to be blocked indefinitely with no ability to add any parameters.
+
+**Attached**: {F11128}",1373539077,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Though I don't know for sure, I think this is a recent regression. the button used to be where it should be (next to the input field). However at that time the input field width was also dynamic (widening as you type). I suspect Trevor ""fixed"" that odd overflow bug by moving the bottom out of the visible form area but probably tested it only with a small template where it was still in sight.
+
+Adding screenshots for clarity.",1373538997,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)",Works for me. Can we twiddle with the prioritisation and criticality? This is a big workflow to have practically broken.,1373538953,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","We're getting various reports of this kind, let's try and keep them somewhat focussed on a single tangible thing. If you don't mind I'll turn this into:
+
+The ""Add parameter"" confirmation button should be next to the input field
+
+  .. not at the bottom of the page after a potential long list of paramaters one has to scroll through to even discover the button.",1373538890,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)",We really need a fix on this. I just tried to add a template (cite web) and was so confused I had to reach out to Timo and Guillaume to work out how in the hells you add a parameter. It's...tremendously counterintuitive on any template with more than 5 params.,1373538824,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Agreed. This is what I was going to add into a new feature request:
+
+---------
+
+In the current version of the template editor, the user needs to select a parameter, click ""Add parameter"", enter the value, go back, and rinse and repeat for all the other parameters.
+
+There are at least two issues with this workflow:
+
+* For templates with a long list of parameters, the ""Add parameter"" button is hidden at the end of the list, so it's not obvious what to do after selecting a parameter
+*: Possible solution: Give each parameter a button that adds it to the left column (like a green ""+"" sign, or something)
+
+* If the user needs/wants to add many parameters, the process can be quite long.
+*: Possible solution: Add an ""Add all parameters"" button, and possibly an ""Add all required parameters"" button as well.",1373034592,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"The existing editing interface stores data on hidden categories, and on the templates in use. This is not displayed in the existing VE - it seems like the sort of thing the page settings page might be good for.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372964580,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-2avh7ag4txo4yazyqwg3,task_description,resolved
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"Maybe we could show these a bit more clear in the dialog, but closing for now.",1393467412,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"Change 113464 merged by jenkins-bot:
+Mark hidden categories as different in the meta-data dialog
+
+https://gerrit.wikimedia.org/r/113464",1393467180,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"Change 113464 had a related patch set uploaded by Alex Monk:
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display
+
+https://gerrit.wikimedia.org/r/113464",1392414019,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"(In reply to Alex Monk from comment #4)
+> Am I right in thinking that the category data comes from Parsoid? If so then
+> it might be useful to include whether the category is hidden or not there?
+
+Okay so after discussion with James and Gabriel on IRC, for now I'm going to query the API when the category dialog loads to get this information. Later to be replaced by a general CSS cache API query (see bug 37901).",1392400602,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,Am I right in thinking that the category data comes from Parsoid? If so then it might be useful to include whether the category is hidden or not there?,1392168563,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,Re-wording to be less confusing. Sorry!,1392062209,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,I think I'm missing something here - it appears that I can see hidden categories and add hidden categories to pages using the categories tool. Is this bug still valid?,1391984557,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"""A late answer to the question of whether there are hidden categories that are actually embedded in articles instead of templates: YES. For instance Category:Year of birth missing (living people) is directly embedded into some tens of thousands of them""",1373212682,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: broken <table> syntax causes VE to inject additional <table> html,"In this case, https://en.wikipedia.org/w/index.php?title=Long_Island&diff=562848384&oldid=562113547 - oh dear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372954980,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-44thcl26amo7hsho63fi,task_description,resolved
+VisualEditor: broken <table> syntax causes VE to inject additional <table> html,"
+
+*** This bug has been marked as a duplicate of bug 51217 ***",1374329698,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-44thcl26amo7hsho63fi,task_subcomment,NA
+VisualEditor: broken <table> syntax causes VE to inject additional <table> html,"A minor change in a completely unrelated part of the article causes a copy of the broken table to be injected into the article, and a '<tr' (no closing >) is also included.  Upping priority/importance as it should at least ignore elements it doesnt properly understand.  The <table> was not so broken that the wikitext up to the </table> should have been ignored.
+
+I am able to reproduce the '<tr' being added [[testwiki:User:John_Vandenberg/Table_test]], but in my test the table wasnt copied.
+
+After fixing the syntax on enwp, the problem goes away.
+
+https://en.wikipedia.org/w/index.php?title=Long_Island&action=history&offset=201307180315&limit=3",1374117478,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-44thcl26amo7hsho63fi,task_subcomment,NA
+VisualEditor: Incorrectly displaying nested references,"Copied from English Wikipedia:
+
+A similar bug was reported as #49536 , but closed as fixed a while ago. Article Otto I has a reference (""ref"") to ""Thompson"" (numbered #11 in old edit mode) inside an explanatory footnote ""efn"". The notes are generated below the article using ""notelist"". Ref 11 Thompson is not included in the reflist of VE, but shown in regular read mode. Just compare the reference lists in read and in VE edit mode to see the difference. GermanJoe (talk) 13:03, 4 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51289
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52398",1372948260,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-6255kvv4aihzvptanmel,task_description,resolved
+VisualEditor: Incorrectly displaying nested references,Filed a bug against Parsoid: see bug 69827,1408586751,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-6255kvv4aihzvptanmel,task_subcomment,NA
+VisualEditor: Incorrectly displaying nested references,"Look at [[Otto I]].  It has 63 references, including ref #18 (""Thompson"") from explanatory footnote [d].  This ref doesn't appear in VisualEditor.",1408406807,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6255kvv4aihzvptanmel,task_subcomment,NA
+VisualEditor: Incorrectly displaying nested references,I believe that this now has been fixed - compare https://en.wikipedia.org/wiki/Otto_I%2C_Holy_Roman_Emperor with https://en.wikipedia.org/wiki/Otto_I%2C_Holy_Roman_Emperor?veaction=edit to see the reference lists being the same in both cases. Sorry for the slow response.,1375383334,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6255kvv4aihzvptanmel,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60358",1372947300,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_description,resolved
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Verified the fix in production,1411682658,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Verified the fix in test2,1411081594,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Verified the fix to show confirmation dialog when trying to insert/edit a template with one or more missing required parameters,1410991738,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"There are still some remaining improvements (as always), but the thrust of this bug is now done.",1410982793,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Change 156559 merged by jenkins-bot:
+Get confirmation when trying to insert/edit template/citation with required parameters missing
+
+https://gerrit.wikimedia.org/r/156559",1410982430,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Change 156559 had a related patch set uploaded by Alex Monk:
+Get confirmation when trying to insert template with required parameters missing
+
+https://gerrit.wikimedia.org/r/156559",1409154385,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,We're also going to require the user to confirm when they try to insert a template with required parameters missing.,1409154296,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.
+
+I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter.
+
+So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor.
+
+(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.)
+
+At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.
+
+And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"(In reply to Alex Monk from comment #14)
+> Is there anything left here to do that isn't bug 60358?
+
+I believe that that will complete this.",1408762442,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Is there anything left here to do that isn't bug 60358?,1408757255,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"I haven't tested required/optional fields in depth, but some casual tests suggest that currently
+
+* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates.
+
+* Required field aren't still enforced, nor there is any warning when they are left empty.
+
+My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",1386641485,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters.
+
+It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". 
+
+As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",1374454542,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Not enforcing mandatory params is a bug in either design or implementation.,1374447401,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. 
+
+More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis.
+
+In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Indeed, I gave up doing this for the Portuguese version for now:
+https://pt.wikipedia.org/wiki/Template:Info/Taxonomia?uselang=en",1373922302,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template
+and  John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". 
+
+I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. 
+
+BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,English Wikipedian Joe Decker recommends indicating required parameters perhaps with the standard red asterisk.,1373565271,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,%%%*** Bug 51186 has been marked as a duplicate of this bug. ***%%%,1373565194,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Change 73136 merged by jenkins-bot:
+Auto-add required params for user added templates
+
+https://gerrit.wikimedia.org/r/73136",1373560433,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Leaving at ""recommend"" for now since we can't fully ensure that requiring all parameters is consistently the desired behavior.",1373507848,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"(In reply to comment #2)
+> Change 73136 had a related patch set uploaded by Jforrester:
+> Auto-add required params for user added templates
+> 
+> https://gerrit.wikimedia.org/r/73136
+
+This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want).
+
+Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",1373503365,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Change 73136 had a related patch set uploaded by Jforrester:
+Auto-add required params for user added templates
+
+https://gerrit.wikimedia.org/r/73136",1373503236,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Indeed, this seems like a low hanging fruit improvement - when inserting a new template, having all the required fields immediately be ready for use would significantly speed up template completion.",1373354062,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),"http://en.wikipedia.org/wiki/File:VisualEditor_-_Cite_template_layout_issue_%28TemplateData%29.png
+
+Tested on Firefox 22, Mono skin:
+
+'''Steps to reproduce'''
+* Open any random page in the visual editor.
+* Add a new template - use Cite Web for this.
+
+The output will be akin to the screenshot added. Some the template parameters end up next to each other, and are thus offscreen. Even if that is not the case the description will often be to long to be displayed. Would be nice if those ended up on a new line if that occurred.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372928700,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-k2f6cmw4o3bualf2yl72,task_description,resolved
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),"I believe that this should now be fixed; marking as such. If you can reproduce, please re-open.",1373503064,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),"We believe that this is caused by a caching issue; a big change to how the CSS for dialogs is loaded is coming in this afternoon's deployment that (hopefully) will remove these issues, so I won't close this right now, but it seems likely that we will have fixed this by the end of today. Sorry for the disruption.",1373484976,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),I can repro in FF20 (in Vector too) but not in Chrome 28.,1373358083,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),Also happening in chrome.,1373357244,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),%%%*** Bug 50738 has been marked as a duplicate of this bug. ***%%%,1372937527,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+Save action doesn't handle abort hooks very elegantly,"When your edit trips the blacklist or an editfilter, you get a very technical and uninformative message.
+
+The edit filter causes:  ""Error: The notification you tried to make was aborted by an extension hook"" to show in the 'save' dialog.
+
+The URL blacklist:  ""Invalid code error"" apparently.
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562806113#Blocked_sites
+
+Since this is quite common for newbs to trip, it should be handled better.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**URL**: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562806113#Blocked_sites",1372928040,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-pb7leo6kictiruq53qyh,task_description,resolved
+Save action doesn't handle abort hooks very elegantly,"* AbuseFilter is bug 50472; resolved fixed, and will be deployed tomorrow.
+* SpamBlacklist is bug 50826; resolved fixed, and deployed yesterday.
+
+Marking this as a dupe of 50472.
+
+*** This bug has been marked as a duplicate of bug 50472 ***",1374112342,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pb7leo6kictiruq53qyh,task_subcomment,NA
+Save action doesn't handle abort hooks very elegantly,"Bumping priority & importance as proper integration with abusefilter must be a blocker, I would think, as rules are being written to prevent VE edits that are destructive to Wikipedia content.",1374101269,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-pb7leo6kictiruq53qyh,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),"This broke during yesterdays deploy. Now shows <accesskey-ca-editsource> and no key is set. I think Timo fixed it already, but the fix might not have been deployed yet.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372926360,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_description,resolved
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),*** Bug 50817 has been marked as a duplicate of this bug. ***,1373077734,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),Merged into master; we hope to deploy this soon.,1373051656,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),"Change 72068 merged by jenkins-bot:
+mw.ViewPageTarget.init: Add missing ""accesskey-ca-editsource"" message
+
+https://gerrit.wikimedia.org/r/72068",1373048824,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),"Change 72068 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget.init: Add missing ""accesskey-ca-editsource"" message
+
+https://gerrit.wikimedia.org/r/72068",1373004195,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),Confirmed.,1372970464,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Steps to reproduce:
+
+* Navigate to [[Mariposa botnet]] and edit the page in the visual editor.
+* Make any textual change - just add ""Test"" somewhere for example.
+* click ""Save Page""
+* Adding a reason doesn't matter. Just click to close the save page popup.
+* Immediately open it again (Don't click anywhere else)
+* Try to add a text as the reason, then press backspace or delete what you just added.
+
+For some reason delete and backspace won't work anymore. My guess is that the backspace is send to the editing canvas instead of the textbox - try the following steps as well:
+
+* (Do all the steps from the first section)
+* Press ""Review Your changes"".
+* Wait for the review to load, then press ""Return To Save"", and close the resulting form.
+* Now click the search block (In mono) and enter a random search criteria.
+* Once entered, try to remove it again.
+
+What happens for me: Entering data in the search box works fine, but pressing backspace somehow causes text to be removed from the article, instead of the search box i was just typing in.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49569",1372923300,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-uxrck24is2ussi4ctgr2,task_description,resolved
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"The (re)fix for this is now merged and will be deployed on Thursday 10 October to MediaWiki.org, and to Wikipedias on Thursday 17 October.",1381187020,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Change 81876 merged by jenkins-bot:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1381186911,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"At bug 53332 comment 0 Elias Hedberg notes that he encountered this bug while using Chrome 29.0.1547.57 running in OS X 10.6.8
+
+Previously this seems only to have been encountered in Firefox. Will that affect the pending patch at all?",1379954053,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,*** Bug 53332 has been marked as a duplicate of this bug. ***,1379953641,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"BeroBurns at en.wp today reported experiencing this bug:
+""The save form does not allow for a keyboard backspace or to highlight text using Shift+Arrows. The only way to edit your description of the changes is to highlight the words you wish to replace with the mouse and retype.""
+
+I personally haven't encountered it since my comment above though.
+
+What is the current state, it's had a patch waiting for review nearly 20 days and is still targetted for the release a month ago yesterday?",1379924128,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Change 81876 had a related patch set uploaded by Jforrester:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1378325627,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"I do have popups, hotcat and section edit link for the lead section installed. Plus a couple of other things a conversation on the feedback page the other day established as being on by default.
+
+I tried to reproduce this when logged out, and couldn't.
+I then logged back in and tried to reproduce it and again I couldn't, even with no changes to gadgets. I didn't try to replicate the exact edit I made though.
+
+Earlier on today was the first time in a while I had experienced it though, which suggests to me that there is probably something more complicated behind when this happens and when it doesn't. I'll do some more detailed testing when I next get time, as it's too perplexing for 1:30am!",1377909365,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"(In reply to comment #12)
+> (In reply to comment #11)
+> > 
+> > With what browser?
+> 
+> I encountered it using Firefox 23 on linux, Tathbelin didn't note it in their
+> report but I'll ask.
+> 
+> Sorry
+
+OK, well, it works fine for me on enwiki right now in Firefox 23 on Mac and on Linux (doing the ^, the <, the Esc and the ""return to save form"" ways of bailing). This is perplexing. Do you have some odd gadgets loaded - does it still occur if you switch all gadgets off?",1377908358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"(In reply to comment #11)
+> 
+> With what browser?
+
+I encountered it using Firefox 23 on linux, Tathbelin didn't note it in their report but I'll ask.
+
+Sorry",1377906476,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"(In reply to comment #9)
+> I've just experienced this in my sandbox making this edit:
+> https://en.wikipedia.org/w/index.
+> php?title=User%3AThryduulf%2Fsandbox&diff=570859913&oldid=570858997
+> (testing for bug 52399)
+> 
+> In this case the series of actions was:
+> 1. Make some edits
+> 2. Review changes
+> 3. Return to editing surface (I can't remember whether I went direct using ^
+> or via the save form using <)
+> 4. make some more edits
+> 5. add an edit summary
+> 6. review changes
+> 7. return to save orm
+> 8. attempt to amend edit summary, but encounter this bug
+
+With what browser?",1377899641,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Nearly simultaneously with my writing the above comment, en.wp user Tathbelin reported on the VE feedback page:
+
+""I had the Problem that while I was writing my Change Summary after editing the page I wasn't able to delete what I had previously written i.e. couldn't use delete or backspace.""
+
+The edit in question was likely https://en.wikipedia.org/w/index.php?title=Henning_Wehn&diff=570856495&oldid=565884244",1377898123,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"I've just experienced this in my sandbox making this edit:
+https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=570859913&oldid=570858997 (testing for bug 52399)
+
+In this case the series of actions was:
+1. Make some edits
+2. Review changes
+3. Return to editing surface (I can't remember whether I went direct using ^ or via the save form using <)
+4. make some more edits
+5. add an edit summary
+6. review changes
+7. return to save orm
+8. attempt to amend edit summary, but encounter this bug",1377896367,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"I believe that this is now fixed, having followed Chris's very helpful steps to reproduce in bug 52733 comment 1 - tested in Safari, Chrome and Firefox latest on Mac just now against wmf14 as deployed on the Wikipedias right now. Marking as such.
+
+If you can re-produce, please feel free to re-open.",1377833711,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,*** Bug 52733 has been marked as a duplicate of this bug. ***,1377833584,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,I updated the summary per comment 5.,1373434182,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,I think there is no connection with ULS for this bug. The bug exists at ml.wikipedia where no ULS is installed at present.,1373424566,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"As per comment 2 and comment 3, changing the component back to VE.",1373263596,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"(In reply to comment #2)
+> Open the the dialog for entering reason? It disappears after I click ""Save
+> Page"". How do I open it again?
+
+A bit more precise:
+0) Navigate to [[Mariposa botnet]] and edit the page in the visual editor.
+1) Make any textual change - just add ""Test"" somewhere for example.
+2) Click ""Save Page""
+3) Now, the save page box titled ""Save your changes"" should pop up.
+4) Close that box by clicking the ^ icon in the top right of that box.
+
+Now, you should be where you started at step 2
+
+5) Repeat steps 2 and 3
+6) Try to add a text as the reason, then press backspace to delete what you just
+added.",1373203660,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"By default input method from ULS is disabled in en.wikipedia.org. ie by default it does not do anything on textareas.
+
+Even if it is enabled, there is no input method for English except IPA which optional. 
+
+So in the case of the above bug, before mapping it to ULS component, please tell us whether input method was activated from the cog icon in the languages menu. Also let us know whether you were using IPA.
+
+If this is not the case, the component is not ULS.
+
+(In reply to comment #0)
+> Steps to reproduce:
+> 
+> * Navigate to [[Mariposa botnet]] and edit the page in the visual editor.
+> * Make any textual change - just add ""Test"" somewhere for example.
+> * click ""Save Page""
+> * Adding a reason doesn't matter. Just click to close the save page popup.
+> * Immediately open it again (Don't click anywhere else)
+
+Open the the dialog for entering reason? It disappears after I click ""Save Page"". How do I open it again?",1373199167,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Yes, this is a really horrible problem that we've narrowed-down to be related to ULS's munging of <textarea>s in Firefox (and possibly other browsers?). Referring to them.",1373159168,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,"(Tested on Firefox 22, Monobook skin)
+
+Steps to reproduce
+
+- Go to the ""The Damned Thing (short story)"" page and edit it with the visual editor.
+- Go to the ""Gothic elements"" selection, and select all the text from ""Gothic elements"" (Header) to ""inadequate."" (Last word of the section). This should also select the image.
+- Click and drag the entire section, and drop it of before the ""Analysis"" section (Just drop it right before the A in that word, make sure the text entry | is displayed. The image itself will be gone. But for the fun part: Click anywhere on the editing canvas text.
+
+Suddenly, your entire input screen will be white. What seems to happen is that the image is blanked (Replaced by a white square) and plastered full size all over the page. You can try to drag it away, but each time you try it will replace itself over the pages content.
+
+https://en.wikipedia.org/wiki/File:Visual_Editor_-_Giant_White_Image.png contains a screenshot of the problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50643",1372922700,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-a2cttzysu3oh2p7i6yls,task_description,resolved
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,"Chris: Good catch, thanks for finding that!
+
+*** This bug has been marked as a duplicate of bug 50643 ***",1375772188,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-a2cttzysu3oh2p7i6yls,task_subcomment,NA
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,I think this duplicates bug 50643,1375716716,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-a2cttzysu3oh2p7i6yls,task_subcomment,NA
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,"Drag and drop is disabled for only text content, however drag and drop is allowed (in monobook) when an image and something else are selected, and the result is nasty.",1374476411,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-a2cttzysu3oh2p7i6yls,task_subcomment,NA
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,"Drag and drop should be disabled, but cant find the bug for it.
+
+I cant reproduce the problem at the mentioned page on Firefox 22 (Win or Linux) using Vector, but goodness me I can reproduce this when I use monobook skin.
+
+https://en.wikipedia.org/wiki/The_Damned_Thing_%28short_story%29?veaction=edit
+
+(page hasnt changed since the bug was raised :/)",1374475185,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-a2cttzysu3oh2p7i6yls,task_subcomment,NA
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,"Note that this is not the same as bug 50715. Though they behave the same from the user point of view, bug 50715 is for a case where aliases are not in play.
+
+e.g. given our Unsigned template with parameter ""user"", ""timestamp"" and aliases ""1"" and ""2"" respectively.
+
+Having added ""mw.log('addParameterSearch-select', name, names);"" to ve.ui.MWTransclusionDialog#getTemplatePage in the select event handler of the addParameterSearch object; editing the following invocations:
+
+ case {{Unsigned|Foo|April 1}}
+ case {{Unsigned|1=Foo|2=April 1}}
+    typing ""1""
+    >  addParameterSearch-select null [""1"", ""2""]
+    >  addParameterSearch-select ""user"" [""1"", ""2""]
+    > ""Add"" is enabled
+    typing ""user""
+    >  addParameterSearch-select null [""1"", ""2""]
+    >  addParameterSearch-select ""user"" [""1"", ""2""]
+    > ""Add"" is enabled
+
+ case {{Unsigned|user=Foo|timestamp=April 1}}
+    typing ""1""
+    >  addParameterSearch-select null [""date"", ""user""]
+    >  addParameterSearch-select 1 [""date"", ""user""]
+    > ""Add"" is enabled
+    typing ""user""
+    >  addParameterSearch-select null [""date"", ""user""]
+    >  addParameterSearch-select null [""date"", ""user""] 
+    > ""Add"" is disabled
+
+The latter case actually works as expected, although it is odd that the value given to the select callback is null and not ""user"" and that the button is already disabled (probably by the select widget?).
+
+Also weird that the callback is constantly triggered twice, once for null and once for the actual value.
+
+Anyway, the solution is to resolve the names to their alias origins before doing the names.indexOf( name ) check.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372913640,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xwzbnkc2eempknw62ukj,task_description,resolved
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,This is now fixed in master and we will push to production very soon. Sorry for the inconvenience.,1373497400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xwzbnkc2eempknw62ukj,task_subcomment,NA
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,"Change 73010 merged by jenkins-bot:
+Retain original param names and ignore leading/trailing whitespace
+
+https://gerrit.wikimedia.org/r/73010",1373497076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xwzbnkc2eempknw62ukj,task_subcomment,NA
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,"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",1373483212,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xwzbnkc2eempknw62ukj,task_subcomment,NA
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,Working on this.,1372913735,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xwzbnkc2eempknw62ukj,task_subcomment,NA
+VisualEditor: Binding of section edit link should not be deferred to after document is loaded,"Split from bug 50540 which is entirely different. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372883340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j2nulhpv4byjb3fgfm3a,task_description,resolved
+VisualEditor: Binding of section edit link should not be deferred to after document is loaded,This was done as part of the changed integration at the beginning of the month.,1376520602,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j2nulhpv4byjb3fgfm3a,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Copying from English Wikipedia:
+
+Okay, this one is probably quite tricky: When editing the source code, if an edit conflict arises, you can simply hit the back button, copy the code, and paste it into the updated version. However, with the Visual Editor, this is no longer possible. The content goes away, so you have to re-add it all, which is a huge pain if it involves references and other templates.--¿3family6 contribs 18:25, 3 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47779
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52519
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56465",1372878900,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-x7aj5blwrrol3b4wt6un,task_description,resolved
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,*** Bug 52950 has been marked as a duplicate of this bug. ***,1393526106,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Just noting that this was broken in Firefox for a few weeks after launch due to bug 56767, which has now been fixed, and I have disabled my switch editor.",1387332793,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,verified in betalabs env,1383337965,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Change 83049 merged by jenkins-bot:
+Button tool to switch to edit source with changes
+
+https://gerrit.wikimedia.org/r/83049",1383241787,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Change 92913 merged by Catrope:
+Button tool to switch to edit source with changes
+
+https://gerrit.wikimedia.org/r/92913",1383241777,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Change 92913 had a related patch set uploaded by Catrope:
+Button tool to switch to edit source with changes
+
+https://gerrit.wikimedia.org/r/92913",1383241700,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"The patch was -2'd pending a rewrite of the toolbar. Although the button works, we have no sensible place to put it until those changes are finished. At the time that was supposed to be a few days, so apologies for the delay, but that work is nearly complete now.",1380708262,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"btw I found this was requested back in April 2013
+
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_04#London_Underground_article
+
+my hack has been broken by some change in the VE product, and the deployment of this fix has now been delayed one month. Siebrand gave the patch a +1 a week ago. What is next for this to be committed and go live?",1380680609,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Change 83049 had a related patch set uploaded by Esanders:
+Button tool to switch to edit source with changes
+
+https://gerrit.wikimedia.org/r/83049",1378428058,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"It isnt that tricky.  Here is a prototype.
+
+https://en.wikipedia.org/wiki/User:John_Vandenberg/switch_editor
+
+The UI could be improved.",1374791298,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,Also this would be useful to allow people to save unfinished changes for later completion.,1373308518,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"The ability to salvage incomplete edits could have other usefulness.
+
+Copying from English Wikipedia:
+
+I can attest to that, I have done the same thing and so due to inactivity the 'invalid token' message is appearing. No idea what to do, currently my tab is still open containing my edits which cannot be saved, I don't want to start over (quite a bit of work here), any suggestions? Copy-pasting to a text editor is not an option since I did mainly lot of linking and minor fixes. -Ugog Nizdast (talk) 10:04, 3 July 2013 (UTC)",1372944038,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+"VisualEditor: ""Undo"" of image resizing causes wonky displacement","From English Wikipedia:
+
+'''Steps to reproduce:'''
+* Edit the [[Vogrie House]] article in the visual editor.
+* Resize the image. Larger or smaller doesn't matter.
+* Press either CTRL + Z, or undo the edit using the undo button. 
+
+Instead of undoing the edit, it suddenly enlarges the image object. The image is placed in the center of the screen, and the object itself even overlaps the main navigation in the Mono interface. Of course as always: Firefox 22 used to test this. [[User:Excirial|<font color=""191970"">'''Excirial''']]</font><sup> ([[User talk:Excirial|<font color=""FF8C00"">Contact me</font>]],[[Special:Contributions/Excirial|<font color=""FF8C00"">Contribs</font>]])</sup> 18:03, 3 July 2013 (UTC)
+
+See screenshot:
+http://en.wikipedia.org/wiki/File:VisualEditor_-_Undoing_a_resize_issue.png
+
+I tried on Chrome on a Mac, and it didn't work there, either, but instead shoved the image to the left of the screen
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372875420,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-vpsb5oulcmbkksi2sshi,task_description,resolved
+"VisualEditor: ""Undo"" of image resizing causes wonky displacement","We've now fixed this, and deployed it; sorry for the issue.",1372901775,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vpsb5oulcmbkksi2sshi,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,"In https://en.wikipedia.org/w/index.php?title=List_of_socialist_countries&curid=7252916&diff=562675715&oldid=562675131
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372853220,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-u7msjuo24hkzquuc5w2p,task_description,resolved
+VisualEditor: Miscellaneous additions of nowiki tags,"(In reply to comment #4)
+> Has the fix been rolled out to svwp?
+
+It has.
+
+> Because I just got a similar error where
+> the nowiki was added far from where I was doing my actual changes:
+> 
+> http://sv.wikipedia.org/w/index.
+> php?title=Stockholm_Arlanda_Airport&diff=22544469&oldid=22428046
+
+I believe that that is actually a different bug here, with Parsoid being overly keen to add <nowiki>, rather than this motley collection of other kinds of <nowiki> issues. :-(",1373841311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,"Has the fix been rolled out to svwp? Because I just got a similar error where the nowiki was added far from where I was doing my actual changes:
+
+http://sv.wikipedia.org/w/index.php?title=Stockholm_Arlanda_Airport&diff=22544469&oldid=22428046",1373831819,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,"First one: This is NOTABUG. User has selected/inserted the wrong text if they didn't want this - see bug 51173.
+
+Second one: Definitely a bug, and one which I believe we have now fixed with the changes to how <nowiki>s are applied in Parsoid.
+
+Third one: Same as two - appears now to be fixed. Sorry for the inconvenience. :-(
+
+Fourth one: This is NOTABUG. User has created a paragraph with some leading whitespace, which means Parsoid needs to do something to stop it turning into a preformatted block. The solution is inelegant (we don't need to select the entire paragraph to stop this), but that is bug 50841.",1373638390,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,"Here are two more in case it helps with diagnosis:
+
+https://fr.wikipedia.org/w/index.php?diff=94682339
+
+https://en.wikipedia.org/w/index.php?diff=562790609",1372941123,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,Again at https://en.wikipedia.org/w/index.php?title=Beximco&curid=1725818&diff=562676888&oldid=561183206 (possibly related?),1372853999,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: VE interface overlapping with main WP interface in monobook w/ small resolutions,"See https://en.wikipedia.org/wiki/File:Visual_Editor_-_Overlapping_issue.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372843980,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-n27a25omdfur3socqod5,task_description,resolved
+VisualEditor: VE interface overlapping with main WP interface in monobook w/ small resolutions,Deployed and confirmed as fixed.,1372893914,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n27a25omdfur3socqod5,task_subcomment,NA
+VisualEditor: VE interface overlapping with main WP interface in monobook w/ small resolutions,I think that this was fixed in gerrit 70851 - we'll be deploying it later today.,1372867380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n27a25omdfur3socqod5,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,"What it says on the tin; if you resize an image, it with reports ""this isn't a change, can't save"" or saves and silently doesn't do anything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372840560,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-l36v7qffhro3qiv5v3ya,task_description,resolved
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,Moved to bug 61270,1392223392,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,"I'm not sure if this is the same issue, but as reported on English Wikipedia and tested by myself, using the image resizer to ""Make full size"" resulted in either a notice that no change had been made or a silent failure to save.
+
+This was tested on FF26, W7 and Chrome 32.0.1700.107 m, W7. 
+
+The reporting editor concludes that ""These new settings, for what they are worth, only work if the image already has a size indication (200px, 250px*250px, whatever), not when it only has a 'thumb' indication. Sadly, the latter is the default and by far most common situation.""
+
+He also questions the purpose of ""Make full size"", but I'll report that separately. 
+
+See: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=595141503#Advanced_image_settings.3F_More_VisualEditor_rubbish.",1392214363,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,*** Bug 51026 has been marked as a duplicate of this bug. ***,1374106684,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,Fixed and will be going out in a few minutes.,1374015979,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,"Change 73965 merged by jenkins-bot:
+Create MWResizeableNode mixin to control defaultSize flag
+
+https://gerrit.wikimedia.org/r/73965",1374015086,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,"Change 73965 had a related patch set uploaded by Esanders:
+Create MWResizeableNode mixin to control defaultSize flag
+
+https://gerrit.wikimedia.org/r/73965",1373983741,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+Space inserted before link after single-character deletion,"From https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE_adding_spaces.2C_messing_with_citation_access-dates:
+
+I noticed something odd when using VisualEditor. I decided to use it when snooping around for various ""it's"" typos, for removing apostrophes seemed/is faster with VE than the old fashioned way. However, some of my edits seem to have done more than take out apostrophes. Seven times today ([http://en.wikipedia.org/w/index.php?title=Highcroft_Racing&diff=prev&oldid=562630195] [http://en.wikipedia.org/w/index.php?title=So_Emotional&diff=prev&oldid=562630132] [http://en.wikipedia.org/w/index.php?title=1988_in_British_television&diff=prev&oldid=562629968] [http://en.wikipedia.org/w/index.php?title=Olmaliq_FK&diff=prev&oldid=562629768] [http://en.wikipedia.org/w/index.php?title=FC_Jazz&diff=prev&oldid=562629613] [http://en.wikipedia.org/w/index.php?title=Brian_McDaniel&diff=prev&oldid=562629235] [http://en.wikipedia.org/w/index.php?title=Highlights_(band)&diff=prev&oldid=562629182]), VE added an extra space in a random place in the article (if it's hard to tell, on the last one it added the space right after ""its""). And then it altered references on [http://en.wikipedia.org/w/index.php?title=God_of_War_(series)&diff=prev&oldid=562631132 another], including changing access-dates. I don't think that's supposed to happen... [[User:Greengreengreenred|<font color=""#014421"">Green</font>]][[User talk:Greengreengreenred|<font color=""#50C878"">green</font>]][[Special:Contribs/Greengreengreenred|<font color=""#66FF00"">green</font>]]<font color=""red"">red</font> 02:25, 3 July 2013 (UTC)
+
+
+Might be a Parsoid bug based on selser tracing. There seems to be only a single space both in the original and the edited HTML.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372821780,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-iqdlibipj4aozqzz2www,task_description,resolved
+Space inserted before link after single-character deletion,"Change 71757 merged by jenkins-bot:
+Bug 50636: Don't extrapolate DSR on change
+
+https://gerrit.wikimedia.org/r/71757",1372829298,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,The space issue will be fixed with the above patch. The accessdate diff (http://en.wikipedia.org/w/index.php?title=God_of_War_(series)&diff=prev&oldid=562631132) is bug 50637.,1372828667,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,"Change 71757 had a related patch set uploaded by GWicke:
+Bug 50636: Don't extrapolate DSR on change
+
+https://gerrit.wikimedia.org/r/71757",1372825446,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,"In the accessdate example, the old markup is bad (duplicate accessdate); the second one apparently wins, which makes sense.  However, there don't seem to be any actual changes in that paragraph, so it ideally shouldn't be affected at all.",1372824675,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,"Offhand, without having investigated this, it seems like a DSR issue.",1372822249,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,"Relevant part of the selser trace (note the extra space):
+
+SS: "", an experimental racing car. The car was designed to reduce aerodynamic drag dramatically allowing for quicker straight and cornering speeds while using half as much power and half as much weight. Despite skepticism over the project, the DeltaWing made its debut at the ""
+SS: "" ""
+SS: ""[[2012 24 Hours of Le Mans]]""",1372822048,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+VisualEditor: Split mw.ViewPageTarget init from integration handling,"This doesn't mean that all of the integration needs to be independent (save dialog etc.) just the initialisation.
+
+It used to be that the integration was only initialisation (instantiate the editor with the html document to edit, basically only up to a dozen lines of code) but it has become much more than that.
+
+We need to separate integration and initialisation (initialisation will be part of the platform specific integration, but code-wise it should be the tip of the pyramid, not the bottom), so that our MediaWiki initialisation should be completely isolated so we can load it from the <head> and it will do only 2 things:
+
+1) Browser compatibility test (bug 50608)
+   - May depend on jQuery and a few plugins
+   - May not depend on any VE classes since those may break in our subset
+     of supported browsers (compared to MediaWiki/jQuery)
+
+   (if passed)
+2) Perform our changes to the interface to avoid flash of ""pre-init"" state
+   - Edit tab (bug 50542)
+   - Edit section links (bug 50540)
+   - Handle setup/teardown of VE from either clicking an ""Edit"" link
+     or by url query.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50677",1372800600,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rwwvww3qvgi4ff4ivkf7,task_description,resolved
+VisualEditor: Split mw.ViewPageTarget init from integration handling,This is now fixed (and deployed).,1372894223,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rwwvww3qvgi4ff4ivkf7,task_subcomment,NA
+VisualEditor: Split mw.ViewPageTarget init from integration handling,"Change 71929 merged by jenkins-bot:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372894020,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rwwvww3qvgi4ff4ivkf7,task_subcomment,NA
+VisualEditor: Split mw.ViewPageTarget init from integration handling,"Change 71929 had a related patch set uploaded by Krinkle:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372889781,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rwwvww3qvgi4ff4ivkf7,task_subcomment,NA
+VisualEditor: Browser compatibility test should not be done in the middle of init after (pre)loading all of core,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372798800,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pt2yvsftiewkmjm3j2nx,task_description,resolved
+VisualEditor: Browser compatibility test should not be done in the middle of init after (pre)loading all of core,This is now fixed (and deployed).,1372894193,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pt2yvsftiewkmjm3j2nx,task_subcomment,NA
+VisualEditor: Browser compatibility test should not be done in the middle of init after (pre)loading all of core,"Change 71929 merged by jenkins-bot:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372894014,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pt2yvsftiewkmjm3j2nx,task_subcomment,NA
+VisualEditor: Browser compatibility test should not be done in the middle of init after (pre)loading all of core,"Change 71929 had a related patch set uploaded by Krinkle:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372889784,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pt2yvsftiewkmjm3j2nx,task_subcomment,NA
+VisualEditor: Language links do not take namespace into account,"Check page settings for https://en.wikipedia.org/wiki/User:John_of_Reading?veaction=edit - it's probably not necessary to have language linking for userspace, but if we're going to do it the ability to distinguish sandboxes from articles would be good.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372756200,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-l5hcose5p2erl7wolwnd,task_description,resolved
+VisualEditor: Language links do not take namespace into account,"
+
+*** This bug has been marked as a duplicate of bug 49226 ***",1381266333,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5hcose5p2erl7wolwnd,task_subcomment,NA
+VisualEditor: Page notices overlap dialogs,"**Author:** `Thehelpfulonewiki`
+
+**Description:**
+Page notice overlaps the close button on page settings
+
+I tried to edit Barack Obama using the Visual Editor. The page notice came up - which is fine - but then I clicked on the page settings without dimissing the page notice and wasn't able to dismiss the page notice. The page notice covers the close button so the only button I could press is ""apply changes"" to causes the page settings window to go away, allowing me to hide the page notice.
+
+I was told in #-visualeditor that you can click anywhere in the notice itself to dismiss it - something I didn't even consider doing because that's not standard behaviour for notifications (considering Facebook and even Echo). Please can we make the page notice dismissable by clicking on the ""1 notice"" area, even if you've got the page settings window up?
+
+See attached screenshot for an illustration of the problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49059
+
+**Attached**: {F11576}",1372730460,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-geudhodnzjlx4dkfmnsc,task_description,resolved
+VisualEditor: Page notices overlap dialogs,This problem is still reproducible with the link editor dialog.,1373940337,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-geudhodnzjlx4dkfmnsc,task_subcomment,NA
+VisualEditor: Page notices overlap dialogs,"This has now been fixed by Rob; marking as such. I hope we can deploy this to production soon, possibly tomorrow.",1372809200,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-geudhodnzjlx4dkfmnsc,task_subcomment,NA
+"VisualEditor: ""[edit | edit source]"" appears jumbled in RTL wiki with LTR interface","Inside an RTL wiki, if you set your interface to English (or any other LTR language) you will see that the '[edit | edit source]' links are jumbled.
+
+(Example: https://he.wikipedia.org/wiki/%D7%A4%D7%99%D7%96%D7%99%D7%A7%D7%94 - use English interface)
+
+This is probably again a case of bidi isolation. I can take a look at the code.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372726200,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-2q5s3rnh3ragcm43w2pm,task_description,resolved
+"VisualEditor: ""[edit | edit source]"" appears jumbled in RTL wiki with LTR interface",Merged and will go out with the next deployment.,1372781960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2q5s3rnh3ragcm43w2pm,task_subcomment,NA
+"VisualEditor: ""[edit | edit source]"" appears jumbled in RTL wiki with LTR interface","Change 71568 merged by jenkins-bot:
+Fix for edit links, RTL wikis with LTR interface
+
+https://gerrit.wikimedia.org/r/71568",1372781877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2q5s3rnh3ragcm43w2pm,task_subcomment,NA
+"VisualEditor: ""[edit | edit source]"" appears jumbled in RTL wiki with LTR interface","Change 71568 had a related patch set uploaded by Mooeypoo:
+Fix for edit links, RTL wikis with LTR interface
+
+https://gerrit.wikimedia.org/r/71568",1372728163,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2q5s3rnh3ragcm43w2pm,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"The ""Edit source"" tab loads/renders a little bit after the ""Edit"" tab, sometimes more noticeably so, sometimes less. Relatedly, clicking the ""Edit"" tab very early on sometimes invokes the wikitext editor. 
+
+It would be preferable for both tabs to be rendered simultaneously with the correct default behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372725780,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-l5ckh63ssiggmz3slrqg,task_description,resolved
+VisualEditor: Tab layout should be done from a top-loading module,"This is now done, and deployed.",1375423118,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"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",1375414262,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"(In reply to comment #10)
+> Change 71929 merged by jenkins-bot:
+> Split off setup from the rest of mw.ViewPageTarget
+> 
+> https://gerrit.wikimedia.org/r/71929
+This introduces a top-loading module, but still does the tab layout from document ready, which means there's probably still is a flash. What we should really do is change the HTML from PHP, per comment 8.",1372894234,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Change 71929 merged by jenkins-bot:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372894017,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Change 71929 had a related patch set uploaded by Krinkle:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372889786,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Ideally we'd alter the HTML using a PHP hook, then have a top-loading module that just conditionally adds some CSS to make the HTML generated by the PHP hook display correctly. That should allow us to get rid of the flashing tab behavior.",1372883412,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"(In reply to comment #6)
+> Shouldn't blacklisting occur much earlier (before actually messing around
+> with any buttons at all?). Before having done *anything* actually?
+> 
+> I'm hoping for a definite answer by James (or another dev involved).
+
+Yes; that's bug 50608. We're re-working a whole bunch of items around the initialisation and integration code for VisualEditor right now - bug 50612 tracks that.",1372883259,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Shouldn't blacklisting occur much earlier (before actually messing around with any buttons at all?). Before having done *anything* actually?
+
+I'm hoping for a definite answer by James (or another dev involved).",1372860735,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"**pinkampersand.wikimedia** wrote:
+
+(In reply to comment #4)
+
+> What do you mean by ""we display:none the former if the user doesn't pass the
+> blacklist code""? What is the ""blacklist code""?
+
+I believe James is referring to the part of VE that checks a user's browser and compares it against a ""blacklist"" of non-supported browsers. ""display:none""-ing the VE edit tab thereby stops people from using VE if their browser's not going to let them.
+
+One of y'all devs can correct me if I'm wrong here.",1372852109,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Sounds good. This could also fix bug 50402 at the same time I think?
+
+What do you mean by ""we display:none the former if the user doesn't pass the blacklist code""? What is the ""blacklist code""?",1372819046,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Re-titling slightly per discussion; the suggestion is now:
+
+* VisualEditor (?in PHP for efficiency/simplicity) hooks into the page before display
+* On this hook,
+** we add the VE edit tab (""edit"")
+** we switch out the WT edit tab with a new label and tool-tip (""edit source"")
+** we display:none the former if the user doesn't pass the blacklist code",1372817658,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"No, this bug is about the tabs at the top of the page (Read/Edit/Edit source), while bug 50540 is about the section-level edit links.",1372729158,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,Should this be merged in some way with Bug 50540?,1372729099,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","A long-standing editor feels that the delay before the ""edit source"" option in sections disadvantages those who wish to bypass VE. Is it possible to have the ""edit source"" link visible always?
+
+See:
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562471642#Very_slow_and_featureless
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56337",1372724940,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-em7qpd4h4h3xgy2ceara,task_description,resolved
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",As per https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/August_2013_update this has been fixed.,1375464355,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #50)
+
+> That RFC can provide guidance, but there are issues of ends versus means.
+
+Exactly. The ""end"" of testing Visual Editor should not include the ""means"" of having it used by the unwary. The only people using VE at this point should be people that are completely aware that they are testing in addition to editing. We can't rely that new accounts have seen some previous notice, or that anonymous editors have seen any notice at all. The only way to ensure that people are aware that it is a beta editor is in the button text itself.",1375301804,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #49)
+> The only mention of the warning that it is beta came in the ""Oppose"" section.
+> The very fact that two of the only three oppose votes mention placing the
+> warning after VE has been invoked makes it clear that people commenting are
+> commenting in the context that the *button* should warn people that it's
+> beta.
+
+That RFC can provide guidance, but there are issues of ends versus means. Changing the section edit links to read ""beta"" would be a bad idea both for the English Wikipedia and for VisualEditor generally.
+
+As suggested in comment 46, the exact wording should be customizable by editing the relevant MediaWiki message pages on-wiki. This bug should focus on removing the animation altogether and providing a sane default behavior for VisualEditor.",1375301077,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #47)
+> (In reply to comment #45)
+> > I would suggest that we go with
+> > 
+> > [beta editor | stable editor] 
+> 
+> No. That RFC (linked in comment 45) ... suggests better advertising that
+> VisualEditor is beta software. 
+
+It specifically asks about the ""user interface"", not the advertising.
+
+(In reply to comment #48)
+
+> 
+> ,,, we don't need to point out that it's beta in the
+> section edit links (it would just be more annoying). 
+
+I suggest that you go back and read that section. The question is explicit. 
+
+Answer 1: The ""edit"" button should explicitly say ""beta editor"" 
+Answer 4: Please label that Edit button more clearly as the way to the Beta version.
+Answer 7: Indeed, per Kww (i.e. per answer 1)
+Answer 17: per User:Kww (again, per answer 1)
+Answer 26: There is no reason the ""edit"" button shouldn't mention the fact it's using VE
+Answer  28: Per kww (i.e. per answer 1)
+Answer 34: Per kww
+Answer 39: Label ""Edit for beta or worse"" (just kidding). Perhaps label as ""Edit slow"" or ""Edit risky"" or such
+
+All the remaining supports were in the context of actually changing the *button text*, even if the question said ""user interface"".
+
+The only mention of the warning that it is beta came in the ""Oppose"" section. The very fact that two of the only three oppose votes mention placing the warning after VE has been invoked makes it clear that people commenting are commenting in the context that the *button* should warn people that it's beta.",1375300376,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #46)
+> [visual edit (beta) | source edit] would be better but not optimal I don't
+> think. [edit | edit visually (beta)] is the most compact that I can come up
+> with, but I'm not claiming that as perfect.
+
+As stated in comment 47, we don't need to point out that it's beta in the section edit links (it would just be more annoying). We can advertise that VisualEditor is beta software in the VisualEditor interface itself (i.e., ?veaction=edit).",1375299134,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #45)
+> I would suggest that we go with
+> 
+> [beta editor | stable editor] 
+
+No. That RFC (linked in comment 45) is specific to one wiki and doesn't suggest using [beta editor | stable editor], it suggests better advertising that VisualEditor is beta software. This request should be filed as a separate bug (and cross-referenced with [[Wikipedia:VisualEditor/Improvements]]).",1375299017,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","I don't think [beta editor | stable editor] is good as it doesn't tell you what the functional difference between them is. We probably also want to stick with ""edit"" rather than ""editor"" (verb rather than noun). 
+
+[visual edit (beta) | source edit] would be better but not optimal I don't think. 
+[edit | edit visually (beta)] is the most compact that I can come up with, but I'm not claiming that as perfect. If one of them is labelled simply ""edit"" that should be listed first (regardless of which one it is).
+
+Allowing the titles to be set by a MediaWiki: namespace page would be ideal, but that is a different request and I can't remember if it has a bug or not.",1375298923,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #44)
+> This needs to be fixed as soon as possible. Compounded annoyance is a very
+> bad
+> thing.
+> 
+> Let's go with [edit | edit source] for now.
+
+Based on the results so far at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Default_State_RFC#Question_4:_Should_the_user_interface_explicitly_warn_editors_that_pressing_the_.22edit.22_button_is_using_beta_software.3F I would suggest that we go with
+
+[beta editor | stable editor] 
+
+or there will be more calls that WMF is not paying attention to the preferences of the Wikipedia community",1375298212,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","This needs to be fixed as soon as possible. Compounded annoyance is a very bad thing.
+
+Let's go with [edit | edit source] for now.",1375296805,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**lecotegougdelaforce** wrote:
+
+Two more comments, after reading the discussion pointed by comment 30 : 
+
+- this argument from Nick White needs emphasizing : ""I don't think two small edit links by section headings constitute clutter. Rather it emphasises *the* key
+thing about wikipedia, that editing is encouraged.""
+
+- the cluttering invoked to justify the hovering solution is actually an argument *against* the hovering : in any case when you hover the link the second option appears, so at one moment the same text will be visible anyway, and actually the hovering is adding a level of cluttering, blinking (including additional blinking when the hovering occurs without the user wanting to edit the section).",1375278214,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**lecotegougdelaforce** wrote:
+
+Glad to see this report already exists.
+
+The idea of having text for VE editing and an icon for standard editing is *wrong* : you can't have two different methods (namely text and image) for advertising two options of a single choice, it's an aberration in terms of user interface (I'm no expert though), it's completely counter-intuitive.  Furthermore people use to associate text *with* image (caption), which makes it even more counter-intuitive.
+
+As far as I'm concerned, I'd be satisfied if we could just switch the default editing method.  That is, I don't want to use VE as a standard, but an advertisement saying it may be useful in certain situations, so I'd prefer to keep it at the hand in case I want to give it a try.  However, I want the default editing action to be the standard editing.  That is, I want the first ""modify"" link to open the standard editor, and the link enabled by the hovering to be the VE.  Therefore, a simple ""default editor = standard/VE"" in the preferences would be enough for me.
+
+However I understand the reading issue mentioned in comment 25, so I'd prefer if the hovering was completely disabled and both links always present (possibly with the option to hide one or both in the preferences).
+
+Furthermore, I'm strongly for the idea to give the user the choice of his editor.  And when I say ""user"", I also mean ""new user"".  Not all users are WYSIWYGers, and though people seem (and they're probably right) to think that the standard editor may frighten some new users, hiding the standard editor by default may as well repel some new users.
+
+Therefore the best solution in my opinion would be to simply disable the hovering and keeping both links, with the possibility to hide one or both in the preferences.  The argument that it's too many links is absurd : on a webpage there are links everywhere, internet users are used to ignore them.  It's even more true for WP where almost half of words are links…",1375277119,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #40 by kwwilliams@kwwilliams.com)
+
+I was assuming of course that the visual editor was working well. I think that the visual editor should be turned off for anonymous IP users until it is working well. 
+
+The VE should have true section editing (instead of whole-page editing as it does now) before IP users are allowed to use the VE. 
+
+The VE also needs to be able to add references well before it is enabled again for IP users.",1375120403,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #39)
+> (In reply to comment #38 by Chris McKenna)
+> 
+> I think completely new users would be more confused by having to choose
+> between
+> 2 edit links in text format. We want to encourage them to try the WYSIWYG
+> visual editor first. 
+> 
+Why would you want to do that? Wouldn't it be better to steer them to the working editor if you need to ""steer"" them at all?
+
+The navigation needs to remain *neutral*.",1375113009,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #38 by Chris McKenna)
+
+I think completely new users would be more confused by having to choose between 2 edit links in text format. We want to encourage them to try the WYSIWYG visual editor first. 
+
+If there is one link and one icon they see the VE ""edit"" link and so they click it to edit. Nothing could be simpler up to that point. 
+
+Then they type in some text, and maybe add bold and italic via VE. So far, it is very simple, and exactly like their email composition.  
+
+My Google Mail ""compose"" link goes directly to the WYSIWYG editor. So should the ""edit"" link in Wikipedia. 
+
+Google Mail offers a ""plain text mode"" in an unlabeled dropdown menu at the bottom right of the compose window. 
+
+We don't want to make wikitext source editing difficult to access, and so an icon is direct access. But we won't confuse completely new users by having two openly-labeled ""edit"" links.",1375091920,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","It's not about aesthetics (that's the reason we have the hover) it's about usability. 
+
+One icon and one link would not likely slow me down considerably, but it would seriously impact new users and those who are not as computer savvy as the people who comment here. UIs need to consistent and accessible. There are two editors, and they need to be accessed in the same way. One icon and one link is guaranteed to cause confusion and it will require active thought far longer than two of the same (blame human psychology).
+
+Take a look at the user interfaces of all the websites and programs you use, and look at the ones you don't regularly use because you can do the same easier elsewhere. Notice how all the ones you think of as good are clear, intuitive and internally consistent. This is not a coincidence.",1375058688,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #35 by Chris McKenna)
+
+You said the following concerning why you want consistency:
+
+> Because there are two ways to do the same job (edit the page) the ways of
+> doing this need to look the same. 
+
+...
+
+> As explained above, ""clutter"" is very significantly less important than
+> consistency. If we need it to say ""edit"" at least once then we need two text
+> links. If two text links are two cluttered then we need two icons.
+
+I still do not see how one edit link being text, and one being an icon would slow down your editing in any way. It sounds more like an esthetic preference.  
+
+You like things in order. My room is probably a lot messier than yours. ;)
+
+I think many options should be put in user preferences. The more the better as far as I am concerned. More happy editors means more editing gets done.",1375047003,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Just to point out the importance of this bug:
+
+I just deactivated VisualEditor for this exact reason. I hate the hovering, and I'm mis-clicking regularly because of the VE replacing my well known ""Edit"" button. Since it is know activated also in my Homewiki (dewiki) I can't stand it any longer. Goodby VE!
+
+Actually I *tried* to give it a chance (I did not deactivate it up to now, although there are many possibilities around how to do it!), but the agressive way the VE is replacing UI links is just not acceptable.",1375018892,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #34)
+> Chris McKenna said that a text link and an icon link were ""a nightmare from a
+> usability perspective"". 
+> 
+Yes, because they are inconsistent. 
+
+> You are saying ""it's about consistency"". Something can be completely usable
+> and
+> not be consistent. Why is consistency important to you? I do not see the
+> need. 
+Because there are two ways to do the same job (edit the page) the ways of doing this need to look the same. 
+
+> According to your logic, we should delete the watchlist star icon because it
+> is
+> inconsistent with the text links at the top of pages. 
+
+The watchlist star is irrelevant to this discussion. It does not offer an alternative interface to achieve the same job as one of the text links. Completely different situation
+  
+> An icon avoids clutter on section header lines. We still need ""edit"" as text
+> at
+> least once, since that is what makes Wikipedia what it is; the encyclopedia
+> that anybody can *edit*.
+
+As explained above, ""clutter"" is very significantly less important than consistency. If we need it to say ""edit"" at least once then we need two text links. If two text links are two cluttered then we need two icons.",1374997623,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #33 by Eduard Braun)
+> It's not about ""being difficult"" it's about consistency!
+> 
+> We have two equivalent ways of editing an article, therefore there should be
+> two equivalent buttons.
+> 
+> Either both of them should be textual links or both of them should be icons.
+
+Chris McKenna said that a text link and an icon link were ""a nightmare from a usability perspective"". 
+
+You are saying ""it's about consistency"". Something can be completely usable and not be consistent. Why is consistency important to you? I do not see the need. 
+
+According to your logic, we should delete the watchlist star icon because it is inconsistent with the text links at the top of pages. I believe the watchlist star icon was partially implemented as a way to save space at the top of pages, and to avoid having dropdown menus in smaller screens. 
+
+The star icon allowed the viewing of Wikipedia pages at smaller screen widths before the dropdown menus showed up at the top. 
+
+With edit links we are trying to avoid dropdowns, hover, and hidden edit links. 
+
+An icon avoids clutter on section header lines. We still need ""edit"" as text at least once, since that is what makes Wikipedia what it is; the encyclopedia that anybody can *edit*.",1374980634,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","It's not about ""being difficult"" it's about consistency!
+
+We have two equivalent ways of editing an article, therefore there should be two equivalent buttons.
+
+Either both of them should be textual links or both of them should be icons.
+
+None of them should be hidden by default.",1374973998,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #31 by Chris McKenna)
+
+I don't understand. How is it difficult to click a static icon that is there all the time (without having to go through any hovering)? There is a star icon at the top of almost every Wikipedia page for adding or removing a page from one's watchlist. 
+
+If clicking an icon to get to the source wikitext editor is a nightmare, then how is making both links icons (as you suggest) better. I agree that the icon for the source wikitext editor should have alt text and tooltip. I should have stated that to begin with, but I assumed that would be done, just as it is for the watchlist star at the top of the page.",1374973136,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #30)
+> I think the least cluttered longterm solution for them might be
+> an
+> ""edit"" link for the visual editor, and an icon for the source wikitext
+> editor.
+
+Least cluttered perhaps, but a nightmare from a usability perspective. Either make both an icon (with alt text and tooltip) or both text links. Usability is far more important than avoiding a tiny bit of clutter.",1374926926,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #26 by Erik Moeller)
+> I agree we need to revisit this, Richard. We'll kick around some options, but
+> we won't be able to get a new interface out before next week at the earliest.
+
+I see that this is being discussed here: 
+*http://lists.wikimedia.org/pipermail/design/2013-July/subject.html 
+
+I note that in this message 
+http://lists.wikimedia.org/pipermail/design/2013-July/000804.html 
+you agree with Trevor Parscal: ""The hover effect is easy to drop - if we are all willing to take the hit on the clutter."" 
+
+I agree with you on this: ""If we want experienced users to test it every once in a while, give feedback on how it can be made better, and have them see the improvements, finding a solution that poses the least burden on them will give us the biggest win.""
+
+It needs to be emphasized that there are many experienced users who edit anonymously (IP edits). They will not be able to go to preferences to choose other options. I think both hover and dropdown will irritate those experienced IP editors. I think the least cluttered longterm solution for them might be an ""edit"" link for the visual editor, and an icon for the source wikitext editor.",1374891994,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #24)
+
+> My first thought is that you are putting a lot of effort into preserving an
+> option that doesn't work. The first and easiest step is to remove the button
+> for editing sections using the source editor until you actually have a source
+> editor that can edit sections. Similarly, your preference scheme seems OK,
+> but
+> the default should be ""Edit sections as wikitext"", at least until you
+> actually
+> have a source editor that can edit sections.
+> 
+
+Sleepiness had obviously hit. Replace with 
+
+My first thought is that you are putting a lot of effort into preserving an
+option that doesn't work. The first and easiest step is to remove the button
+for editing sections using the visual editor until you actually have a visual editor that can edit sections. Similarly, your preference scheme seems OK, but
+the default should be ""Edit sections as wikitext"", at least until you
+actually have a visual editor that can edit sections.
+
+While sleepiness had hit, the point remains valid: since Visual Editor doesn't work for sections, there's no reason to damage the user interface by pretending to support it.",1374849031,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","What about my suggestion in comment 15? I still think this would be a workable solution resolving most of the controversy around section edit links.
+
+The proposed setting whether to prefer VE or the WikiEditor could also be used to relabel the buttons to improve the workflow for everybody:
+* ""Edit"" for the edit button using the preferred editor
+* ""Edit Source"" or ""Visual Edit"" for the second button
+
+This way a simple ""Edit"" button would be the default way to edit an article, regardless of which editor the user prefers, while the other option was around for special use cases.",1374837475,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #24)
+> The first and easiest step is to remove the button
+> for editing sections using the source editor until you actually have a source
+> editor that can edit sections.
+
+To clarify, ""source"" is one of the terms VisualEditor uses for wikitext.  So, the wikitext/source section editor has not changed (other than the label).",1374829183,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","I agree we need to revisit this, Richard. We'll kick around some options, but we won't be able to get a new interface out before next week at the earliest.",1374819700,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Discussed again at [[Wikipedia:VisualEditor/Feedback#Edit Source is upsetting. When reading is upsetting]]
+
+I think this comment highlights the problem for readers, not just editors or power users, presumably this is effecting IP readers as well:
+
+It is VERY unpleaseant for me to read with the new feature. When I pass the mouse over the edi button, appears a new button saying edit source. I know these things are great for editors. But they are really distracting because one scrolls the mouse accidentally, in all the horizontal white stripe, i mean one scrolls the mouse over any place at the same height of the screen that Edit button, then Wild Edit source button appears. This is horrible. Please, make it harder to find. This distracts the eye a lot, i'm tottally serious. Plase, don't take this for a joke, i'm serious, the editors may have another way to do that, for example clicking on a small STATIC button for visual editing, that would be GREAT! Thank youSantropedro1",1374818730,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #13)
+
+> Section editing links
+> (x) Hybrid edit / edit source links [default]
+> ( ) Edit sections via VisualEditor
+> ( ) Edit sections as wikitext
+> ( ) Disable section editing
+> 
+> ...
+> 
+> We don't love the [ edit ] [ edit source ] static links, because it feels
+> cluttered and not the kind of user experience that we want to support.
+> 
+> Thoughts? If either of these feels like a reasonable path forward, we can
+> re-use this bug to track it, or start a new one.
+
+My first thought is that you are putting a lot of effort into preserving an option that doesn't work. The first and easiest step is to remove the button for editing sections using the source editor until you actually have a source editor that can edit sections. Similarly, your preference scheme seems OK, but the default should be ""Edit sections as wikitext"", at least until you actually have a source editor that can edit sections.
+
+My second thought is that for any choice that presents both, the animated is far worse, and probably gets worse for anyone that uses an interface with a long word that means ""edit"". When I see a page, it has little buttons labeled ""bewerken"" next to each section header, and as I'm moving my cursor there, it suddenly animates and ""brontext bewerken"" slides out to the side (which is strange, because my main button for editing source is labeled ""bron bewerken""). Not surprisingly, I'm accustomed to having the thing I'm aiming for not purposely jump out of the way once I try to get there. I'd prefer getting a popup and having to click twice to having the thing I'm aiming for run away. Of course, I can try to remember to aim 3 cm to the right of the button and click *there*, but that is really an odd UI.
+
+In terms of the VE feature that makes me curse every time it occurs, it's accidentally launching VE because the thing I was aiming for ran away while I was aiming for it.",1374814202,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #13 by Erik Moeller)
+
+> We don't love the [ edit ] [ edit source ] static links, because it feels
+> cluttered and not the kind of user experience that we want to support.
+
+If provided as a preference then it is not clutter, at least to that user. 
+
+If you don't provide this as a baked-in MediaWiki preference in the edit tab of preferences, then probably all Wikipedias in all languages, and all MediaWiki installations outside the Wikimedia world will provide buggy gadgets to provide the 2 static links. 
+
+For example; the buggy CSS hack described here:
+*[[Wikipedia:Village pump (technical)/Archive 114]] - see section ""Removing the animation from 'edit source' section links on Visual Editor"".
+
+Is it not a thousand times better for it to be a fully-maintained, baked-in preference that will not constantly become buggy after various MediaWiki updates?",1374541092,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**turingt** wrote:
+
+> 
+> We don't love the [ edit ] [ edit source ] static links, because it feels
+> cluttered and not the kind of user experience that we want to support.
+> 
+> Thoughts? If either of these feels like a reasonable path forward, we can
+> re-use this bug to track it, or start a new one.
+
+You seem to be under the impression that [ edit ] [ edit source ] dynamic links that appear and disappear on hover feel ''less'' clutter, but that's not the case.
+
+The least possible clutter that support both editors is to show shorter links, and make them static:
+
+[ edit | source ]
+
+or maybe get rid of the square brackets - they don't look at all necessary if both links are always visible:
+
+Edit | source
+
+See? No clutter at all, and more functional for all users regardless of their javascript or pointing device availability.",1374356199,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #20)
+> Are you sure the single link was the VE one?
+> 
+> I've seen some occasional cases where only the wikitext section links showed
+> (this is also the default, e.g. if you have JavaScript disabled), but I can't
+> recall one where only the VE section links showed, since the hover code has
+> been setup.
+
+It probably was a link to Source Editor, but when 'edit' could go to VE or SE, such confusion and concern results.  On mobiles, it's not possible to see what the link is without pressing it.",1374304107,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Are you sure the single link was the VE one?
+
+I've seen some occasional cases where only the wikitext section links showed (this is also the default, e.g. if you have JavaScript disabled), but I can't recall one where only the VE section links showed, since the hover code has been setup.",1373928461,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","A user on the English Wikipedia has today commented that the hover links are not always displaying when the system is being slow or unresponsive (their local system or the WMF servers). This obviously means that section editing in the classic editor is not available when its small footprint would be most beneficial
+
+For reference they included their technical specs:
+Downstream 20 Mb/s; Safari 6.0.5; Mac OS 10.8.4; 2.7 GHz Intel Core i7 (64-bit); 8 GB 1333 MHz DDR3; Flash 11.8.800.94; Java 1.6.0_51.",1373832913,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","I'd prefer just showing them always, too (they can then be easily be hidden separately with CSS if necessary). But others prefer how it is done now (see Erik Möller's concerns in comment 13).
+
+That's why I proposed a *prefer*ence here.
+
+Anyway, if we should decide against a preference, showing them always is the way to go, because the current hovering effects are a nightmare for both, accessibility and customizeability.",1373551894,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**gigs** wrote:
+
+Eduard Braun's preferences proposal would work to solve all the use cases, but I don't see how this is superior to just always showing both links, with a preference for reverting to the old behavior (which already exists).
+
+Users will quickly adjust to clicking on their preferred mode, if both are always shown.",1373551134,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",Custom CSS workaround available at https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=563794311#Removing_the_animation_from_.22edit_source.22_section_links_on_Visual_Editor,1373539008,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","However this will be solved: Put thought in it!
+I could imagine, that this decision will determine whether people will be disabling/hiding VE or keep using it along with the Wikitext editor.
+
+A proposal from my side which might be a better fit from a user's point of view:
+
+1) One setting (radio button) that determines which editor the user prefers for normal tasks (e.g. whether ""edit"" or ""edit source"" is shown first in toolbar or whether ""edit"" or ""edit source"" is shown as section edit link while the other one is shown on hover only)
+(o) Prefer VisualEditor
+( ) Prefer Wikitext Editor
+
+2) One setting (radio button) to control how edit section links are handled
+(o) show preferred edit link, show the other one on hover
+( ) always show both edit section links
+    ([edit|edit source] or the other way round depending on 1)
+( ) only show preferred edit section link, don't show the other one at all.
+( ) no edit section links at all",1373509125,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #13)
+> We've been kicking around the section editing behavior a fair bit, and we
+> recognize the need for more flexibility, in part because the mouseover
+> interface doesn't translate well to touch-based user interfaces. (We also
+> recognize that section-editing in VisualEditor overall is still a bit of a
+> crutch, but that's a larger discussion.)
+
+The two issues I'm seeing from users are that:
+
+A. some editors are annoyed by the animation, particularly when scrolling or trying to target a specific link with a mouse quickly (or when using a touchscreen device, as you note); and
+
+B. some editors are annoyed by VisualEditor generally and would simply like to disable/hide all traces of it.
+
+> What James and I would like to suggest here is a multi-way pref:
+> 
+> Section editing links
+> (x) Hybrid edit / edit source links [default]
+> ( ) Edit sections via VisualEditor
+> ( ) Edit sections as wikitext
+> ( ) Disable section editing
+> 
+> The section editing feature is already disable-able, so we could just merge
+> the pref.
+
+This proposed solution solves problem A (the animation/hover issue) for the non-default case (not really helpful...), while inhibiting users who want both links but without any animation/hover. Not great. For problem B, it mitigates the impact of VisualEditor slightly (though users are still left with two tabs at the top of the page and probably slower load times as a result of VisualEditor).
+
+> If folks think that's too much, we could just have a single
+> 
+> [ ] Support section editing via VisualEditor 
+> 
+> checkbox as this point, enabled by default, which turns on or off the hybrid
+> mode.
+
+This proposed solution doesn't solve problem A (animation/hover) and doesn't solve problem B (VisualEditor being enabled at all).
+
+I'm not sure either proposed (compromise) solution is better than the current situation. However, there's already an existing user preference to disable VisualEditor that was inexplicably removed. It's difficult to tell how many editors are having problem A or are having problem B, but re-adding a user preference to disable VisualEditor would solve problem B for sure and largely solve problem A (for those who find problem A to be a problem...).",1373505406,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","We've been kicking around the section editing behavior a fair bit, and we recognize the need for more flexibility, in part because the mouseover interface doesn't translate well to touch-based user interfaces. (We also recognize that section-editing in VisualEditor overall is still a bit of a crutch, but that's a larger discussion.)
+
+What James and I would like to suggest here is a multi-way pref:
+
+Section editing links
+(x) Hybrid edit / edit source links [default]
+( ) Edit sections via VisualEditor
+( ) Edit sections as wikitext
+( ) Disable section editing
+
+The section editing feature is already disable-able, so we could just merge the pref.
+
+Having three modes may seem like overkill at this stage but James feels that having an option for VisualEditor specifically at least puts a flag in the ground that we want to continue to improve section editing usability.
+
+If folks think that's too much, we could just have a single
+
+[ ] Support section editing via VisualEditor 
+
+checkbox as this point, enabled by default, which turns on or off the hybrid mode.
+
+We don't love the [ edit ] [ edit source ] static links, because it feels cluttered and not the kind of user experience that we want to support.
+
+Thoughts? If either of these feels like a reasonable path forward, we can re-use this bug to track it, or start a new one.",1373503336,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","I misspoke. The only VE gadget now in preferences is this one: ""Remove VisualEditor from the user interface."" 
+
+But my point is that each language version of Wikipedia should not have to create gadgets to provide VE options to its editors. 
+
+Some preferences need to be provided in all MediaWiki installations. Or at least all Wikimedia installations of MediaWiki. For example:
+*Display both ""edit"" and ""edit source"" links for sections without hover.
+*Remove VisualEditor from the user interface (VE still loads, but it can not be used).
+
+The first preference will mean that far fewer people will use the second preference. And the 2 preferences should be together so that people can see why they should choose the first preference over the other. The reason being that since VE still loads, one saves no load time by blocking access to using VE.",1373171885,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","There is no way this should be ""Lowest"" in importance. Moved up to ""Normal"". I would change enhancement to ""normal"" also, but developers still seem dead set against making the choice dead simple and easy; or as one recent commenter wrote: ""I am talking about giving editors easy way to choose the way they want to edit wikipedia."" This is a common request. 
+
+This needs to be a baked-in option in the edit tab of preferences. Not an ad hoc addon gadget as it is now in English Wikipedia. At least then registered editors can keep editing most efficiently. Choosing instantly between visual editor and source editor as the need arises. Registered editors do twice as many edits each month as anomymous IP editors. See chart:
+[[File:Anonymous, registered, and bot edits. English Wikipedia timeline by percent of edits.png]]
+
+So if you can't get it right for anonymous editors, at least allow registered editors to get it right with an option.",1373171236,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**gigs** wrote:
+
+It's difficult to focus without clicking on a touchscreen as well.",1373150662,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #7)
+> It seems no one has pointed out that pads and phones and touchscreens usually
+> can't ""hover"".  Hover stuff should pretty much never be a necessary part of
+> any web UI.
+
+It's not a necessary part.  First, the 'edit source' link at the top does not require any hover.  Second, the same thing occurs ('edit source' section link is shown) when you focus on the 'edit' section link (onfocus).",1373148915,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","This should be a priority and not just an enhancement. To think that future versions of MediaWiki will be crippled longterm by this incredibly buggy and slow visual editor is very discouraging. 
+
+At the very least there needs to be a preference for direct ""edit"" and ""edit source"" links built in to MediaWiki preferences on the edit tab of preferences. MediaWiki installations should not need a ""gadget"" preference added for this by each webmaster of every MediaWiki installation. 
+
+The hidden link to ""edit source"" is slowing down many editors. For more info and other options: 
+
+[[Wikipedia:VisualEditor/Feedback/Archive_2013_07#Edit_and_edit_source_links_so_confusing_I_had_to_disable_Visual_Editor_in_preferences]]
+
+[[Wikipedia:VisualEditor/Feedback/Archive_2013_07#Note_the_many_unhappy_people_who_do_not_see_the_HIDDEN_.22edit_source.22_link]]
+
+A thread linked in a previous comment (comment 1) has been archived:
+[[Wikipedia:VisualEditor/Feedback/Archive_2013_07#How_to_disable.3F]]
+
+There have been many more comments requesting a direct link to ""edit source"" on each section. See:
+[[Wikipedia:VisualEditor/Feedback]] and its archives.
+
+Slowing down the many editors who will continue to need source editing to edit complex things more easily is a really dumb idea. What is the logic? That you will irritate and trick editors into using the visual editor? That they will click the ""edit"" link instead of the ""edit source"" by being tricked? It is extremely irritating to have to spend extra time to get to source editing. You will not lack in bug reports by providing direct links to ""edit source"". 
+
+For help on putting links in Bugzilla threads:
+[[WP:Bugzilla]]",1373094343,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**gigs** wrote:
+
+It seems no one has pointed out that pads and phones and touchscreens usually can't ""hover"".  Hover stuff should pretty much never be a necessary part of any web UI.",1373091895,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",Clarifying.,1372801897,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","@Krinkle: I think the change of the summary is wrong.
+
+This is (from what I get from the comments, the discussions linked are a little less clear I'm afraid) not about section ""edit source"" links being loaded with delay (although this would be an issue, too).
+It's about having to hover over the ""edit"" link to be able to see the ""edit source link"". They should both be directly accessible (without hovering and visibility changes).",1372801493,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",This is (besides bug 50542) one of the main reasons a seamless coexistence of VisualEditor and Wikitext editor is *not* possible at this time (as intended by the WMF).,1372799152,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Note that this request is being repeated a lot, including by people who are unhappy that mousing over causes words to pop up, which they say disrupts reading the page. They would prefer the words be always visible to avoid this.",1372767720,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",This was proposed before and even had a rejected patch by me: I13bbb954.,1372725359,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Sorry - wrong section.
+
+See:
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562471375#How_to_disable.3F",1372725043,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"A firefox 5.0 user is reporting that blacklisting simply isn't working - they're seeing the VE, broken. Their response to ""are you spoofing user headers"" was along the lines of ""what the heck is that?"" which answers that question.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372719060,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-otwsyh65xhzuochbdcrh,task_description,resolved
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,This is now deployed.,1372727423,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"Change 71554 merged by jenkins-bot:
+Blacklist Firefox <= 10 per reports that it's broken
+
+https://gerrit.wikimedia.org/r/71554",1372723165,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"(In reply to comment #6)
+> I re-checked FF10 on Windows 7:  whether editing a whole page or a section
+> of a page FF10 presents the loading... bars but never presents the editor
+
+OK, we'll blacklist Firefox 10 and under per the above patch; will see if we can do a quick deploy today to avoid user confusion.",1372721478,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,I re-checked FF10 on Windows 7:  whether editing a whole page or a section of a page FF10 presents the loading... bars but never presents the editor,1372721333,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"Change 71554 had a related patch set uploaded by Jforrester:
+Blacklist Firefox <= 10 per reports that it's broken
+
+https://gerrit.wikimedia.org/r/71554",1372721244,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"(In reply to comment #3)
+> Tried FF 5, 9, and 10, VE ""Edit"" links are available in all of them along
+> with
+> ""Edit source"" links.  In each case VE only displays the loading bars and does
+> not present any usable interface.
+
+We've had a user swear blind that everything works fine in FF 10. Clearly they misled us. :-(",1372721101,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"Tried FF 5, 9, and 10, VE ""Edit"" links are available in all of them along with ""Edit source"" links.  In each case VE only displays the loading bars and does not present any usable interface.",1372719656,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"Wait, so non-whitelisted browsers are let through? Is this documented anywhere?
+
+I'd suggest anything not whitelisted be blacklisted, frankly. We've got firefoxes 5, 9 and 10 producing substantial problems.",1372719459,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"We don't blacklist Firefox 5. We currently blacklist:
+
+* MSIE <= 10
+* Android <= 3
+* Blackberry
+* Opera
+
+We whitelist:
+* Firefox >= 11
+* Iceweasel >= 10
+* Safari >= 5
+* Chrome >= 19
+
+All other browsers are let through, with a warning.
+
+Does this mean we should blacklist Firefox 5.0?",1372719336,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"**Author:** `rachelqa99`
+
+**Description:**
+enter erroneous text for existing reference
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:Rachel99/testing_070113?veaction=edit
+
+**Attached**: {F11502}",1372712580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5mroix5k2facuxaaopyg,task_description,resolved
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,On review this was specifically fixed by the changes to how the references list was constructed; marking as such.,1380559887,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"I can't reproduce this either. Time for a close as ""worksforme""?",1380546929,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"Created attachment 12928
+screenshot of dialog
+
+I can't reproduce this; maybe the UI has been fixed?
+
+Attached is the list I see.  Typing 'ux' in the input box removes references that dont match the string 'ux'.  Typing 'sys' reduces the list to one reference that does match the box.
+
+**Attached**: {F11504}",1374557703,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"**rachelqa99** wrote:
+
+first reference is picked when erroneous text typed in
+
+**Attached**: {F11503}",1372712993,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"**rachelqa99** wrote:
+
+I have references that already exist. I want to reuse one of them. I choose reference bookmark icon.  It lists all current references under use current reference.  It is unclear what to type here.  If I type in erroneous text, it seems to let me insert it, and it chooses the first reference [ users 1].  It does not check to see if text corresponds to existing reference.
+Need directions on what to type for a existing reference, or how to choose existing reference.",1372712923,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"I suspect this may be related to an existing bug, but if so I can't figure out how to find it.
+
+Looking at the very bottom change on http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562259398, we see the first in a series of edits where editing elsewhere adds duplicated characters to a template that I don't believe is being edited directly. (Further duplication occurred in these edits to the same page: http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562359846, http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562363670, http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562363840)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372695120,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-4vsqha4nxg6sirme3ghc,task_description,resolved
+VisualEditor: Duplicating text in template on unrelated edit,I *believe* that this is now fixed - marking as such. Please re-open if you find it happening again.,1383006754,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,Guillaume: This is a Parsoid bug (which I was able to reproduce). This current bug seems like a generic placeholder bug. I created bug 53429 in parsoid so we can identify more specifically what went wrong. You can add yourself to that bug if you wish.,1377639799,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"In this edit, a table was duplicated (but it wasn't in a template):
+
+https://fr.wikipedia.org/w/index.php?&diff=96159772
+
+Is it the same issue or should I open a separate bug report?",1377594995,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,Can someone check and see if https://bugzilla.wikimedia.org/show_bug.cgi?id=52618 should better be marked as a duplicate of this? Thanks!,1375957426,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"(In reply to comment #3)
+> en.wp user reports that adding a single hyphen to a page trigged this bug to
+> remove part of an infbox and duplicate other templates in the middle of a
+> category.
+> 
+> https://en.wikipedia.org/w/index.
+> php?title=IBM_Personal_Computer&diff=567356453&oldid=566275349
+
+The table at the end was not closed. I [https://en.wikipedia.org/w/index.php?title=IBM_Personal_Computer&diff=567437920&oldid=567357722 fixed it (for consistency's sake, I used the s-end template)] and VE edits and saves should not introduce dupes on this.",1375817388,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"I think this diff from fr.wp is another example?
+https://fr.wikipedia.org/w/index.php?title=Gen%C3%A8ve&diff=95604102&oldid=95601955",1375804621,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"en.wp user reports that adding a single hyphen to a page trigged this bug to remove part of an infbox and duplicate other templates in the middle of a category.
+
+https://en.wikipedia.org/w/index.php?title=IBM_Personal_Computer&diff=567356453&oldid=566275349",1375801774,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"This looks like the same issue, yes.",1375377912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"Could this bug be responsible for these edits where one templates was duplicated and the other apparently duplicated and substed in the middle of a category link?
+
+https://en.wikipedia.org/w/index.php?title=Ford_Figo&diff=566719977&oldid=566176664
+https://en.wikipedia.org/w/index.php?title=Ford_Figo&diff=next&oldid=566719977",1375370248,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Screenshot of list indent problem
+
+If I add indent to any list item, it breaks. 
+
+The indented line gets moved to the end of the previous line.
+
+The live-changes looks as it is working properly, but the edit-diff (preview your changes) always shows it as broken. (See attachment)
+
+Confirmed with:
+* Firefox and Chrome,
+* with ordered and un-ordered list items, 
+* with items added to the middle of a list, and to the end of a list,
+* and with both new items added to a list, and existing items given increased indent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F11420}",1372641600,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-fn66at2vne5i62qo6jnn,task_description,resolved
+VisualEditor: Likely invalid HTML emitted for list items,"Change 71395 merged by jenkins-bot:
+Bug 50483: Make sure nested list serialization is newline-insensitive
+
+https://gerrit.wikimedia.org/r/71395",1372708410,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Change 71395 had a related patch set uploaded by GWicke:
+Bug 50483: Make sure nested list serialization is newline-insensitive
+
+https://gerrit.wikimedia.org/r/71395",1372706751,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,This is not a new bug.  This has been around for a long time.  I went back to commits almost 3 months back and tested.,1372704536,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Looks like Parsoid serializer is newline sensitive in this case:
+
+$ echo '<ol><li>Foo\n<ol><li>Bar</li></ol></li></ol>' | node parse.js --html2wt
+#Foo
+##Bar",1372704376,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"$ echo '<ol><li>Foo<ol><li>Bar</li></ol></li></ol>' | node js/tests/parse.js  --html2wt 
+#Foo##Bar",1372704023,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"I'm guessing that VE emits the wrong HTML here, so reassigning to VE. Please move to Parsoid again if the VE HTML is sane.",1372703188,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Also:
+echo '<ol><li>foo</li><li>bar</li></ol>' | node parse --html2wt
+#foo
+#bar",1372694554,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Cannot reproduce:
+
+echo -e '#foo\n#bar' | node parse --wt2wt
+#foo
+#bar
+
+Can you provide the HTML the VE sends?",1372694100,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"This appears to be a (new?) bug in Parsoid - 
+
+# Foo
+# Bar
+
+-> 
+
+# Foo## Bar
+
+rather than
+
+# Foo
+## Bar
+
+Unless we're breaking something in VisualEditor somehow?",1372691714,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"As per http://www.mediawiki.org/wiki/Help_talk:VisualEditor/User_guide#Discoverability .
+Might be handy, since we're pretty much beginners with it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372621440,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-pcueszubfgitqkx3f2bv,task_description,resolved
+VisualEditor: Add a link to the User Guide to the interface,This has been done and will go out later today.,1372703974,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"Change 71376 merged by jenkins-bot:
+Add user guide link to beta icon drop down
+
+https://gerrit.wikimedia.org/r/71376",1372703622,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"Change 71376 had a related patch set uploaded by Jforrester:
+Add user guide link to beta icon drop down
+
+https://gerrit.wikimedia.org/r/71376",1372699824,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"That sounds good. The link should probably be something like [[mw:Special:MyLanguage/Help:VisualEditor/User guide]] and live in a MediaWiki: interface message, so that wikis can customize it to link to a local page.
+
+My feeling is that the link to the user guide should persist even after we're out of the beta, but we can discuss this then.",1372679384,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"Possibly add the help icon to the ""beta"" label, and have it as an option in the menu?",1372627245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"[Forked from the more general 50350.]
+
+Currently when AbuseFilter blocks an edit made with VE, the only response we can display is:
+
+| The modification you tried to make was aborted by an extension hook
+
+When bug 32216 is done - AbuseFilter is changed to use the APIEditBeforeSave hook - we can display this significantly more nicely.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372618620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xz7of2bozktz6cktgsun,task_description,resolved
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Then I suspect the problem is an extension of bug 50058, which will be fixed in time. If so, it's probably not worth prioritising as a new bug (or reopening this one) since abusefilter triggerers are likely to be new users, ergo on vector.",1374265703,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+Of course I use Monobook, Oliver.",1374265556,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Are you, by any chance, on monobook?",1374264793,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+Tested this, now that it is deployed, and have to say that while it the change came close to being a solution, it isn't quite there. The edit-filter notice produced when using the standard editor is large, easy to read, and quite clear. The edit-filter noticed produced when using VE is tiny, uses an infinitesimal font, and is extremely difficult to read.",1374264704,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"enhancement->major, as this is an integration bug.",1374185775,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,*** Bug 50727 has been marked as a duplicate of this bug. ***,1374112342,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,Warnings will now show (once we deploy).,1374090444,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Change 74102 merged by jenkins-bot:
+mw.ViewPageTarget: Show AbuseFilter warning in save dialog
+
+https://gerrit.wikimedia.org/r/74102",1374087934,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Change 74102 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Show AbuseFilter warning in save dialog
+
+https://gerrit.wikimedia.org/r/74102",1374023516,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,Marked as blocked by 51403 in AbuseFilter.,1373928234,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Change 73877 merged by jenkins-bot:
+mw.ViewPageTarget: Surface error messages from core edit api
+
+https://gerrit.wikimedia.org/r/73877",1373927436,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+Just in case it's important to the fix, the message returned by the abuse filter is free format and generally contains templates and other markup.",1373926866,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"(In reply to comment #8)
+> Change 73877 had a related patch set uploaded by Krinkle:
+> mw.ViewPageTarget: Surface error messages from core edit api
+> 
+> https://gerrit.wikimedia.org/r/73877
+
+This is not yet sufficient since we should be surfacing the
+warning associated with the filter (or the abusefilter-warning
+message by default). The most significant part we're missing
+right now is:
+* Localization
+* The fact that (at least for some filters) they can submit
+  the edit by just trying again.
+
+This is currently blocked by the AbuseFilter not sending the parsed version of the triggered warning through the API (see http://cl.ly/image/1E2r1J2U3K0v, I'm getting raw wikitext instead of HTML).
+
+And perhaps (though less important) we could also use a boolean property to distinguish between filters that are warnings that can be bypassed by trying again and filters which prevent the user from saving.",1373926321,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Change 73877 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Surface error messages from core edit api
+
+https://gerrit.wikimedia.org/r/73877",1373926266,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,*** Bug 51139 has been marked as a duplicate of this bug. ***,1373495105,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"(In reply to comment #5)
+> Has this actually been deployed?
+
+No.
+
+> I just tested, and the error message has changed (it now reads ""invalid
+> error code"", while it used to read ""Error: the notification you have made
+> was aborted by an extension hook"").
+
+That's almost certainly caused by the ""fixing"" of bug 32216, which changes what we need to integrate with.",1373401097,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+Has this actually been deployed? I just tested, and the error message has changed (it now reads ""invalid error code"", while it used to read ""Error: the notification you have made was aborted by an extension hook""). If that was the fix, I think it's pretty obvious that it's incomplete, as it still isn't displaying the warning from the edit filter.",1373385258,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,*** Bug 50828 has been marked as a duplicate of this bug. ***,1373054299,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"(In reply to comment #2)
+> I strongly, strongly object to the categorization of this as an
+> ""enhancement"".
+
+""Enhancement"" does not mean ""not going to be done soon""; it merely means that this is not a feature that's meant to be currently working, but instead, a feature we'd like to add.
+
+This feature in particular is on our immediate work list, and hopefully will be done in the next week or so.",1372952430,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+I strongly, strongly object to the categorization of this as an ""enhancement"". This is a basic feature that needs to be addressed. There aren't many edit filters that block edits, but when an editor trips one of the ones that does, its important that he have an idea as to what to fix. There's no place for an editor to even begin looking to find out what is happening and what it is about his edit that is causing it to fail. It's not really even obvious from the message that it's a content issue.",1372952091,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,*** Bug 50719 has been marked as a duplicate of this bug. ***,1372921240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Newest CSS not showing up in production for some users (so reference editor not correctly formatted),"Screenshot
+
+See screenshot. Firefox 21.0, Windows XP. As well as misplacing the toolbar it's also hiding the 'create new source' on articles with lots of sources.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11391}",1372617600,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-3yckz2spdz6vwpvvlsja,task_description,resolved
+VisualEditor: Newest CSS not showing up in production for some users (so reference editor not correctly formatted),Roan fixed this in his mega-CSS-rewrite.,1373852943,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3yckz2spdz6vwpvvlsja,task_subcomment,NA
+VisualEditor: Newest CSS not showing up in production for some users (so reference editor not correctly formatted),*** Bug 50455 has been marked as a duplicate of this bug. ***,1372620610,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3yckz2spdz6vwpvvlsja,task_subcomment,NA
+VisualEditor: Newest CSS not showing up in production for some users (so reference editor not correctly formatted),"Renamed (aka, I hate ResourceLoader's caching, some times :-().",1372620482,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3yckz2spdz6vwpvvlsja,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,"The formatting icons of the VisualEditor toolbar are currently ""B"" for bold, ""I"" for italics, the chain for links and the remove icon to clear formatting.
+
+This series of icon seems to indicate that links are a kind of formatting. However; ""Clear formatting"" doesn't affect links; it only removes bold and italics.
+
+Either links *are* a kind of formatting, and the ""Clear formatting"" action should remove them, or they aren't, and the Link icon shouldn't stand in the middle of icons that add and clear formatting. The current order and behavior are confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372600920,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-xid2rg44chmbsuqujmzr,task_description,resolved
+VisualEditor: Clear annotations icon no longer clearing link annotations,Fixed and will go out in a few minutes.,1373930966,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,"Change 73896 merged by jenkins-bot:
+Compare annotations by name only when clearing/toggling
+
+https://gerrit.wikimedia.org/r/73896",1373930577,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,"Change 73896 had a related patch set uploaded by Esanders:
+Compare annotations by name only when clearing/toggling
+
+https://gerrit.wikimedia.org/r/73896",1373929632,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,*** Bug 51018 has been marked as a duplicate of this bug. ***,1373504485,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,This is a regression; it used to work fine - relabelling as such.,1372611822,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,"It is currently not possible to add a reference to an image/media caption, nor to edit existing ones.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52427
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49657",1372597320,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_description,resolved
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,*** Bug 54949 has been marked as a duplicate of this bug. ***,1380844957,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,This was completed as part of the NewFromDocumentReplace work that Roan did last week.,1380835418,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,"Changing this to reflect that now references do appear in the toolbar for media items, but can't be inserted or edited (and the list of existing references to insert is blank - suggests something's pointed at the wrong document/etc.?).",1379657377,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,"bug 51992 comment 0 :
+http://en.wikipedia.org/wiki/User:Kww/fileref is about as simple of a testcase
+as I could develop. Given this structure:
+
+[[File:Red Wine Glass.jpg|thumb|upright|A ""large"" (250&nbsp;ml) glass of
+12%&nbsp;ABV red wine has about three units of alcohol. A ""medium""
+(175&nbsp;ml) glass, such as the one shown, has about two units.<ref> Even
+though the sizes of wine glasses are defined in UK law, the terms ""large"",
+""medium"", ""standard"" etc are not defined in law.</ref>]]
+
+
+There's no way to edit the reference.
+
+----------------
+bug 51992 comment 1 :
+Simpler illustration, still in http://en.wikipedia.org/wiki/User:Kww/fileref
+
+I don't think it's possible to edit that pesky footnote.
+[[File:Red Wine Glass.jpg|thumb|upright|description<ref>pesky footnote</ref>]]
+
+{{reflist}}",1374702671,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,*** Bug 51992 has been marked as a duplicate of this bug. ***,1374702531,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Screenshot1
+
+There are, I think, some UI improvements to be made to the reference editor - User:Popcornduff gets credit for these :).
+
+When you first open the reference editor, you're presented with something like screenshot 1, which asks you ""What do you want to reference?"" If the user is coming to try and add a new reference, this is highly confusing - the first UI element they're presented with prompts them to put time into a series of actions that cannot possibly end with them finding what they want. The cue also doesn't make clear to any user what the search bar is actually doing - filtering existing references. It seems like the blurb here might need changing to align it with what the search bar actually does; ""search existing references on this page""?
+
+If you click ""create new source"", absolutely nothing happens - it's a highlightable element, and after a bit you can puzzle out that it unlocks ""create reference"", but it's not immediately clear. Still, you end up with it highlighted (see screenshot2). The blurb in ""insert reference"" is rather confusing; what am I inserting? I'm here to /add/ a new reference, I haven't written it out yet. My suggestion would be to have ""create new source"" take you straight to the source creation interface using a one-click mechanism, rather than having it free up ""insert no references"".
+
+Still, you click it, and you get to screenshot3, of a window tagged ""reference content"". Quoth the user, ""Is it reference the verb - am I referencing content here? Or am I giving content to the reference?
+
+What is the Options heading all about, and what does ""Use this group"" mean?
+
+I have a little window here to type into. I'm not sure what to type. Do I just write out my reference in Wikimarkup and click ""Apply changes""? Or do I write them out as if I'm writing a list of references at the end of an essay?
+
+At this point I'm really disappointed. I was hoping to be given a complete list of individual fields to fill out - a box for author, a box for date, a box for date accessed, a box for the title, a box for the URL, and so on - and have this generate the reference nicely for me. Instead, I seem to have the old system in a confusing UI.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51848
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53590
+
+**Attached**: {F11364}",1372596600,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-b74srkob65ougmewgpvd,task_description,resolved
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows",This was resolved with the new citation system released last month.,1401472375,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows",*** Bug 51184 has been marked as a duplicate of this bug. ***,1377831014,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","(In reply to comment #8)
+> The ""what do you want to reference?"" field, which exists solely to filter
+> through existing references, still displays if there are zero existing
+> references.
+
+This sounds like bug 51848",1377597887,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","At en.wp user:Risker reports on feedback she received running an editathon. Relevant to this bug is:
+
+To a person, they all said that VE was *more* difficult to use than wikitext, especially with respect to references. Now, they had all had reinforced to them the importance of referencing factual information, so they were all trying to include references. They pointed out that at least with the wikitext editor, they could pull up templates that were complete and they didn't have to try to figure out the parameters. They were using mostly printed sources, not websites, so there was no URL to use as a quick-and-dirty reference insertion.",1377597769,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Change 74191 merged by jenkins-bot:
+Reference dialog commingling
+
+https://gerrit.wikimedia.org/r/74191",1374183562,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Change 74191 had a related patch set uploaded by Jforrester:
+Reference dialog commingling
+
+https://gerrit.wikimedia.org/r/74191",1374182072,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","The ""what do you want to reference?"" field, which exists solely to filter through existing references, still displays if there are zero existing references.",1372858754,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Yes, I think the ""wiki-specific workflows"" is key.  On wikis (including English Wikipedia) that use:
+
+<ref>{{some template|firstparam=a}}</ref>
+
+with a few key some templates, it's worth allowing a simplified flow for those (while still providing the full flexibility of arbitrary references and arbitrary templates where needed).
+
+Within a template, it's also verbose due to the screen layout.  E.g. I would consider keeping parameter name and value on the same screen (for named parameters), and making it easy to add the next parameter without going up to the root.  The latter can be done without the former.
+
+I'd recommend trying ProveIt (https://en.wikipedia.org/wiki/User:ProveIt_GT) on English Wikipedia if you haven't.  I don't expect you to take the same approach we did (and don't look at the ""parser"").  The reference browsing part also probably doesn't apply, but the add mode in particular shows how the GUI can be streamlined when it doesn't attempt to be fully general.",1372829687,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Please don't roll this out to everyone until this is fixed, as until it is there is going to be a lot of cleanup work needed. I agree with those above who say this might mean less references. I quickly disabled it the first time I tried to create a new citation.",1372761439,PHID-USER-wqo7db5tur74g52lu64y,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","**gwaw_2003** wrote:
+
+I'd have to agree with PamD above. If anything, just steal the RefToolbar code, and make it work with VE as a temporary fix for enwp. This cannot be rolled out to new editors the way it is, or we'll have a ton of ""well I hated how the references worked so I stopped trying to use them at all"" edits from new editors.",1372728086,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Thanks for these comments; obviously the references system is a work in progress and we had already planned to undertake (at least most of) these improvements, but we hadn't had the time to write it down in bugzilla - will use this to track those improvements now.",1372691404,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Please look at how RefToolbar behaves (I choose whether my ref is a website, book, etc; I get offered a set of useful boxes into which to input the data; I click on ""Preview citation"" to see that it looks OK; I click on ""Add citation"". Job done.), and give this sort of useful guidance to editors adding references in VE.",1372691060,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Screenshot3
+
+**Attached**: {F11366}",1372596695,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Screenshot2
+
+**Attached**: {F11365}",1372596681,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","When adding a new link to an existing page, the text is automatically capitalized, even if the user entered the text in lowercase. Many links don't need to be capitalized, so users shouldn't have to clean up after VisualEditor decides to capitalize them.
+
+Note that when you're adding a new link to a page that doesn't exist, the inserted link preserves the capitalization that was entered by the user (which is the expected behavior)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50945
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50678
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50745
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53566",1372587540,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_description,resolved
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","The above changes behaviour if the user types in the entire anchor in a different case (e.g. iPhone vs. IPhone), which is I think sufficient to close this bug for now; different ways of suggesting links might want to come off the outcome of bug 53566. (It will be deployed to the cluster from Thursday 5 September, and to Wikipedias on Thursday 12 September).",1378254877,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Change 82054 merged by jenkins-bot:
+Offer the typed text as a link suggestion if the page is valid
+
+https://gerrit.wikimedia.org/r/82054",1378254752,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Change 82054 had a related patch set uploaded by Esanders:
+Offer the typed text as a link suggestion if the page is valid
+
+https://gerrit.wikimedia.org/r/82054",1377900648,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","(In reply to comment #9)
+> I think creating a bug for
+> MediaWiki having page-level meta-data about the correct display of a page's
+> title would be great, yes.
+
+Done, see bug 53566",1377811932,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","(In reply to comment #8)
+> Until that happens I think we should preserve the case of the input, as even
+> if that isn't what people want it is easily possible to change and pretty
+> intuitive how to do it - ie, type ""foo"" get ""[[foo]]"" but wanted ""[[Foo]]"",
+> all you need to do is type ""Foo"" instead. The current behaviour means you get
+> ""[[Foo]]"" regardless of what you want or do.
+
+Possible, but a bit messy when writing certain articles like BLPs where most link targets will be proper nouns.
+
+> The only other thing I can think of is for VE to read and respect things like
+> {{lowercase title}}. Once it does that then it should also respect things
+> like {{correct title}} for a default display text, and we should probably
+> create a {{Proper noun title}} for titles that should always be capitalised by
+> default.
+>
+> Or rather than using templates we could move the title information into page
+> metadata. I have no idea whether any of this is practical, but if it is I
+> guess it would be better as one or maybe two separate bugs.
+
+Yes, certainly for this to be used in VisualEditor it would need to be a proper feature and not one hacked into a template; I think creating a bug for MediaWiki having page-level meta-data about the correct display of a page's title would be great, yes.",1377808735,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","The best thing, as noted at 48789, is for there to be two input boxes - one for the link target and one for the displayed text. 
+Until that happens I think we should preserve the case of the input, as even if that isn't what people want it is easily possible to change and pretty intuitive how to do it - ie, type ""foo"" get ""[[foo]]"" but wanted ""[[Foo]]"", all you need to do is type ""Foo"" instead. The current behaviour means you get ""[[Foo]]"" regardless of what you want or do.
+
+When the second input box is added then we should use the case as input as the default. 
+
+The only other thing I can think of is for VE to read and respect things like {{lowercase title}}. Once it does that then it should also respect things like {{correct title}} for a default display text, and we should probably create a {{Proper noun title}} for titles that should always be capitalised by default. Or rather than using templates we could move the title information into page metadata. I have no idea whether any of this is practical, but if it is I guess it would be better as one or maybe two separate bugs.",1377804697,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Clarifying what this is in the title:
+
+| New link annotations' anchors get their first character capitalised, even if you didn't want that
+
+->
+
+| When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors
+
+The problem is in the link suggester (it's the same behaviour in category and template selection, except that those always capitalise the first character so no-one cares.
+
+When you trigger the link inspector on no selection and type in ""foo"", you are given suggestions like:
+
+* Foo
+* Foobar
+* Fooian
+
+Selecting any of these picks not just the target, but also the text of that target as the anchor (good) and the capitalisation of that target (less good).
+
+However, if I've typed ""foo"", did I definitely want [[foo]] rather than [[Foo]]? Should we show both [[Foo]] and [[foo]] options in the list if you type in ""foo"", but only [[Foo]] if you type in ""Foo""?",1377803059,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","From bug 53495:
+Currently whenever a user enters a link when no text is selected the first
+character of the displayed link is always capitalised. This is often incorrect,
+e.g. in the middle of a sentence or for articles like [[iPhone]] or [[grep]].
+
+Especially until bug 50678 is fixed, correcting this is not at easy or
+intuitive.
+
+So, at least until bug 48789 and bug 50945 are fixed and the display text is
+settable in the dialog, and probably beyond that, it would be best if the
+displayed link used the same case as the search term entered. i.e.
+
+User entry ->  wikitext equivalent of desired output
+Green   ->  [[Green]]
+green   ->  [[green]]
+iPad    ->  [[iPad]]
+HAMmer  ->  [[Hammer]]
+london  ->  [[london]]
+
+Yes, this will result in some wrong captialisations, but no more than at
+present and will only be temporary (as noted above)",1377802682,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors",*** Bug 53495 has been marked as a duplicate of this bug. ***,1377802569,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","(In reply to comment #3)
+> Are you talking about:
+> 1. Ctrl+K
+> 2. Type a lcase work
+> 3. Press enter twice
+
+Yes. For step 3, it also happens when you click on a suggestion.",1377594263,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Are you talking about:
+1. Ctrl+K
+2. Type a lcase work
+3. Press enter twice
+
+because that's the only way I can reproduce, and after the first press of enter it shows you that it has capitalised the word due to autocomplete?",1377558575,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Yes, I can still reproduce it. Note that I'm talking about the behavior when you enter Ctrl+K and type text, not the behavior when you add a link to existing text.",1377175898,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Is this still happening, Guillaume? I can't reproduce it.",1377173293,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+VisualEditor: Link inspector in a slug can select content in the previous or following paragraphs,"If the cursor is in a slug and you press the link button, the selection jumps to the nearest content - which crosses out of the local <p> and into the <p> beforehand or afterwards (whoops).
+
+Link inspector should detect that it is in a slug and not attempt to mangle the selection with nearestContentOffset, but just trigger with a 'blank' selection.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52256",1372572900,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rxqaxhgvcsfou4tzboet,task_description,resolved
+VisualEditor: Link inspector in a slug can select content in the previous or following paragraphs,This was fixed by gerrit 81437.,1377888669,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rxqaxhgvcsfou4tzboet,task_subcomment,NA
+VisualEditor: Link inspector in a slug can select content in the previous or following paragraphs,"As a follow-up, if you have <start of document> <block slug> <block slug> <block slug> <block slug> <p> in a document, and have the cursor in the second slug, pressing Ctrl+K will move the selection to the top of the document and put the contents there (whee); in the third or fourth, to the first word of the <p>. Not great.",1372573764,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rxqaxhgvcsfou4tzboet,task_subcomment,NA
+VisualEditor: References with duplicated content are normalised away,"If you have a page like:
+
+<ref name=""foo"">Foo</ref> ...... <ref name=""foo"">Foo</ref>
+
+VE will normalize this to:
+
+<ref name=""foo"">Foo</ref> ...... <ref name=""foo"" />
+
+The contents of the second <ref> tag are obviously ignored, but we should round-trip their existence correctly.
+
+
+http://tools.wmflabs.org/visualeditor/dirtydiffs/2013-06-30_00-52/Genetic_history_of_the_Iberian_Peninsula.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372567200,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2ttmyole76xyfw5lxpgw,task_description,resolved
+VisualEditor: References with duplicated content are normalised away,This was fixed in gerrit 71275 by Roan.,1372705872,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2ttmyole76xyfw5lxpgw,task_subcomment,NA
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,"After having saved a template on a page, and edit it again, template data for the template is visible, but any parameter used is not showing templatedata, even though it displayed it correctly when I created the template
+
+test I made on beta was {{test|name = hello}}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372554600,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_description,resolved
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,"Think we have subsequently fixed this, probably as part of the re-write of the transclusion dialog/TemplateData link in July; marking as such. Please re-open if it recurs.",1384200108,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_subcomment,NA
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,Can't reproduce this bug.,1384198743,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_subcomment,NA
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,"When I make a new template entry and open the template before I've saved the page, it looks like following:
+http://i.imgur.com/HxaU7F1.png
+
+But after having saved the page, and enter template edit again, I'm getting following:
+http://i.imgur.com/VPROUwb.png",1372596044,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_subcomment,NA
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,"(In reply to comment #0)
+> After having saved a template on a page
+
+By a template, you mean a template transclusion or the template itself?
+
+
+> and edit it again, template data for
+> the template is visible, but any parameter used is not showing templatedata,
+
+So when you edit the tranclusion with VisualEditor template data for the template is visible but not for the parameters? What does that mean?
+
+You say it is visible for the template but not for the parameters. So what is visible then?
+
+> even though it displayed it correctly when I created the template
+
+Displayed what?",1372557963,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"After I added the <templatedata> to [[pt:Template:Referências]], I opened a page in which it is used, setting ""uselang=pt"" and ""uselang=pt-br"" in the URL:
+1) https://pt.wikipedia.org/wiki/Arte?veaction=edit&uselang=pt
+2) https://pt.wikipedia.org/wiki/Arte?veaction=edit&uselang=pt-br
+In the first case, when I opened the Transclusion dialog (by clicking in the references section, where the template is used) the template description was shown (as expected). Typing one of the template parameters, I also get its label normally.
+
+On the other hand, for the second link the user language (pt-br) was different from the content language (pt) and the user see no description and no labels.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50888",1372534860,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-uydrcj3p2rhxycgc65tn,task_description,resolved
+TemplateData: Process language fallback and conversion server-side,"Change 87724 merged by jenkins-bot:
+Implement getInterfaceTextInLanguage and use API and Parser
+
+https://gerrit.wikimedia.org/r/87724",1381172101,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"Change 87724 had a related patch set uploaded by Krinkle:
+Implement getIntefaceTextInLanguage and use API and Parser
+
+https://gerrit.wikimedia.org/r/87724",1381078137,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #14)
+> Oh. I assumed the jQuery.i18n (or one of the other JS, MW-independent tools
+> that the Language Engineering team have built) would have this built in. Is
+> that not the case?
+
+I can't say there isn't one but I've never heard of this.
+
+BTW I also want a similar one on server side.",1374922596,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #17)
+> Also, this way we can provide good values for languages that don't exactly
+> fallback but use a language converter. Which is also something that could
+> potentially be done client side, but I don't see that happening just yet.
+
+Which isn't really doable currently I guess; or it requires delivery of huge conversion tables (for Chinese).",1374920975,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"Also, this way we can provide good values for languages that don't exactly fallback but use a language converter. Which is also something that could potentially be done client side, but I don't see that happening just yet.",1374863198,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"For now this is up to the client side to handle, which realistically means it won't be handled (current language > en > nothing).
+
+
+For the future I intend to have the templatedata API take a parameter for language code and resolve it on the server side. For three reasons:
+
+* On wikis where there is more than 1 language commonly used (which is the whole point of this bug and where it is relevant, since if there is only 1 language, the wiki author can just specify { ""description"": ""Text."" } without lang-codes)..., on those wikis there will be more than 1 language defined. This will result in a large blob of JSON being transferred to e.g. VisualEditor for each template which is quite a lot of data.
+
+* Even so, it would then still require the client-side to have knowledge of all of this and process it. Which involves a lot of language data being send to the client, a lot of translations being sent to the client, and the then client having to do all the computation for it. We can solve this the same way we solved it in ResourceLoader; We'll still cache it, but fragment it by language code based on request context.",1374863078,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #8)
+> (In reply to comment #6)
+> > So I'm not too Wikidata-savvy, but it seems this patch might be useful (if
+> > it's
+> > not, ignore me and carry on):
+> > 
+> > https://gerrit.wikimedia.org/r/72867
+> > 
+> > Right now there is no way to determine the real language of a message from
+> > the
+> > CDB cache. That patch changes this.
+> 
+> Not really. Labels and descriptions in TemplateData are stored in some JSON
+> blob in a customized format, rather than normal messages.
+
+Gotcha. Carry on. Sorry I couldn't help.",1374862510,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #13)
+> (In reply to comment #12)
+> > (In reply to comment #11)
+> > > (In reply to comment #9)
+> > > > I don't think that's a good outcome. If there isn't a description in your
+> > > > language (in this case, pt), we shouldn't magically tell you that we've given
+> > > > you a message in a different language (we don't do this for the MW messages
+> > > > framework, for instance).
+> > > 
+> > > BTW this comment means WONTFIXing this whole bug.
+> > 
+> > Why?
+> > 
+> > This is just me saying that I don't think that instead of ""Chien"", if it
+> > doesn't exist in French we should give users ""Dog -- OMG We gave you this
+> > message in English even though you asked for it in French!"", which feels
+> > significant over-kill.
+> 
+> Then I guess your point is that pt-br and pt are more similar, so falling
+> back from pt to pt-br is acceptable, while fr and en are not this case.
+
+Yes.
+
+> However technically pt-br and pt have the same relationship as fr and en,
+> or we'll have to compose some language similarity table ourselves, and manage
+> to resolve many edge cases (eg. dialects).
+
+Oh. I assumed the jQuery.i18n (or one of the other JS, MW-independent tools that the Language Engineering team have built) would have this built in. Is that not the case?",1374862470,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #12)
+> (In reply to comment #11)
+> > (In reply to comment #9)
+> > > I don't think that's a good outcome. If there isn't a description in your
+> > > language (in this case, pt), we shouldn't magically tell you that we've given
+> > > you a message in a different language (we don't do this for the MW messages
+> > > framework, for instance).
+> > 
+> > BTW this comment means WONTFIXing this whole bug.
+> 
+> Why?
+> 
+> This is just me saying that I don't think that instead of ""Chien"", if it
+> doesn't exist in French we should give users ""Dog -- OMG We gave you this
+> message in English even though you asked for it in French!"", which feels
+> significant over-kill.
+
+Then I guess your point is that pt-br and pt are more similar, so falling back from pt to pt-br is acceptable, while fr and en are not this case. However technically pt-br and pt have the same relationship as fr and en, or we'll have to compose some language similarity table ourselves, and manage to resolve many edge cases (eg. dialects).",1374859742,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #11)
+> (In reply to comment #9)
+> > I don't think that's a good outcome. If there isn't a description in your
+> > language (in this case, pt), we shouldn't magically tell you that we've given
+> > you a message in a different language (we don't do this for the MW messages
+> > framework, for instance).
+> 
+> BTW this comment means WONTFIXing this whole bug.
+
+Why?
+
+This is just me saying that I don't think that instead of ""Chien"", if it doesn't exist in French we should give users ""Dog -- OMG We gave you this message in English even though you asked for it in French!"", which feels significant over-kill.",1374858682,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #9)
+> I don't think that's a good outcome. If there isn't a description in your
+> language (in this case, pt), we shouldn't magically tell you that we've given
+> you a message in a different language (we don't do this for the MW messages
+> framework, for instance).
+
+BTW this comment means WONTFIXing this whole bug.",1374858103,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #9)
+> (In reply to comment #7)
+> > (In reply to comment #5)
+> > > Fine technically - I think users would be upset and confused.
+> > 
+> > So you'll need to prepare for some interface design to tell users that ""Some
+> > text written in English"" and ""Some other text written in Spanish"" lines are
+> > not in pt.
+> 
+> Why couldn't the TemplateData just be written in the users's language?
+
+You can't expect all templatedata blocks to have labels in all hundreds of languages which MediaWiki supports.
+
+> > And the format of JSON needs to be modified to include this info.
+> 
+> I don't think that's a good outcome. If there isn't a description in your
+> language (in this case, pt), we shouldn't magically tell you that we've given
+> you a message in a different language (we don't do this for the MW messages
+> framework, for instance).
+
+We do so in Wikibase, if the user indicates that they can read another language -- in our implementation it checks {{#babel: }} currently but some global preferences here will be nice of course.",1374858004,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #7)
+> (In reply to comment #5)
+> > Fine technically - I think users would be upset and confused.
+> 
+> So you'll need to prepare for some interface design to tell users that ""Some
+> text written in English"" and ""Some other text written in Spanish"" lines are
+> not in pt.
+
+Why couldn't the TemplateData just be written in the users's language?
+
+> And the format of JSON needs to be modified to include this info.
+
+I don't think that's a good outcome. If there isn't a description in your language (in this case, pt), we shouldn't magically tell you that we've given you a message in a different language (we don't do this for the MW messages framework, for instance).",1374857740,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #6)
+> So I'm not too Wikidata-savvy, but it seems this patch might be useful (if
+> it's
+> not, ignore me and carry on):
+> 
+> https://gerrit.wikimedia.org/r/72867
+> 
+> Right now there is no way to determine the real language of a message from
+> the
+> CDB cache. That patch changes this.
+
+Not really. Labels and descriptions in TemplateData are stored in some JSON blob in a customized format, rather than normal messages.",1374856941,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #5)
+> Fine technically - I think users would be upset and confused.
+
+So you'll need to prepare for some interface design to tell users that ""Some text written in English"" and ""Some other text written in Spanish"" lines are not in pt.
+
+And the format of JSON needs to be modified to include this info. Like:
+
+{
+    ""pages"": {
+        ""1467239"": {
+            ""title"": ""Predefini\u00e7\u00e3o:Refer\u00eancias"",
+            ""description"": {
+                ""pt"": { ""value"": ""Some text written in English"", ""language"": ""en"" }
+            },
+            ""params"": {
+                ""t\u00edtulo"": {
+                    ""label"": {
+                        ""pt"": { ""value"": ""Some other text written in Spanish"", ""language"": ""es"" }
+                    },
+                    ...
+            }
+            ...
+     }
+}",1374856866,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"So I'm not too Wikidata-savvy, but it seems this patch might be useful (if it's not, ignore me and carry on):
+
+https://gerrit.wikimedia.org/r/72867
+
+Right now there is no way to determine the real language of a message from the CDB cache. That patch changes this.",1374856762,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #4)
+> (In reply to comment #2)
+> > API call should ideally specify the fall-back language chain and return just
+> > one set for clients (so the weight is on the server).
+> 
+> Do we care about the real language info of a label.
+
+We don't, but users on multi-lingual wikis will if we send them 1 MiB of descriptions of a template when they only care about 2 KiB worth of the contents. :-)
+
+> That is, is this fine?
+> 
+> {
+>     ""pages"": {
+>         ""1467239"": {
+>             ""title"": ""Predefini\u00e7\u00e3o:Refer\u00eancias"",
+>             ""description"": {
+>                 ""pt"": ""Some text written in English""
+>             },
+>             ""params"": {
+>                 ""t\u00edtulo"": {
+>                     ""label"": {
+>                         ""pt"": ""Some other text written in Spanish""
+>                     },
+>                     ...
+>             }
+>             ...
+>      }
+> }
+
+Fine technically - I think users would be upset and confused.",1374856587,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #2)
+> API call should ideally specify the fall-back language chain and return just
+> one set for clients (so the weight is on the server).
+
+Do we care about the real language info of a label.
+
+That is, is this fine?
+
+{
+    ""pages"": {
+        ""1467239"": {
+            ""title"": ""Predefini\u00e7\u00e3o:Refer\u00eancias"",
+            ""description"": {
+                ""pt"": ""Some text written in English""
+            },
+            ""params"": {
+                ""t\u00edtulo"": {
+                    ""label"": {
+                        ""pt"": ""Some other text written in Spanish""
+                    },
+                    ...
+            }
+            ...
+     }
+}",1374856405,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"Falling back to (LanguageConverter)-converted labels is needed too.
+
+It seems my LanguageFallbackChain and related classes (currently in Wikibase) is useful here again.",1374150699,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,API call should ideally specify the fall-back language chain and return just one set for clients (so the weight is on the server).,1372535404,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"For the record, the data returned by the API has all the information, but it is in the ""pt"" properties:
+https://pt.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Predefini%C3%A7%C3%A3o%3Arefer%C3%AAncias
+E.g.:
+{
+    ""pages"": {
+        ""1467239"": {
+            ""title"": ""Predefini\u00e7\u00e3o:Refer\u00eancias"",
+            ""description"": {
+                ""pt"": ""Produz o t\u00edtulo da se\u00e7\u00e3o de refer\u00eancias e impede que seja edit\u00e1vel""
+            },
+            ""params"": {
+                ""t\u00edtulo"": {
+                    ""label"": {
+                        ""pt"": ""T\u00edtulo da se\u00e7\u00e3o""
+                    },
+                    ...
+            }
+            ...
+     }
+}",1372535216,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"VE is missing the red ""semi-protected page"" box seen at
+http://en.wikipedia.org/w/index.php?title=Muscle&action=edit and probably also the equivalent one for administrators on fully protected pages.
+
+They should be displayed as a ""notice"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51215",1372489200,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ndmy33qu6brquwrr27nw,task_description,resolved
+VisualEditor: Protected page warning messages are missing,This is now fixed in master and we will push to production very soon. Sorry for the inconvenience.,1373497562,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"Change 73022 merged by jenkins-bot:
+Add protected & semiprotected notices to api.
+
+https://gerrit.wikimedia.org/r/73022",1373497150,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"Change 73022 had a related patch set uploaded by Robmoen:
+Add protected & semiprotected notices to api.
+
+https://gerrit.wikimedia.org/r/73022",1373487840,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"(In reply to comment #3)
+> The edit box of a protected page also uses a pick background.  That is
+> missing
+> from VE.
+
+No, this is enwiki's local CSS: [[MediaWiki:Group-sysop.css]] needs to be updated. I will file an edit request.",1372914263,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,The edit box of a protected page also uses a pick background.  That is missing from VE.,1372913884,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"This also applies to things like BLP warnings, mind; non-page-specific warnings generally seem to get cut off.",1372751625,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"In sequencing, this should probably be above everything except the not-applicable anon warning (so anon warning > protected > editing old > page notices). Maybe we need a more formal ordering?",1372614070,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+<span> floats out of a table(?),"Possibly related to Bug 49892, VE is inserting random <span> parameters.  
+
+See:
+https://en.wikipedia.org/w/index.php?title=Ruger_P_series&diff=next&oldid=560801075
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372450980,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-fmgdk7zrdnkog3djzdrc,task_description,resolved
+<span> floats out of a table(?),"That diff is from before we deployed the fix in 49892.  And, the oldid html is probably coming from the cache.  So, once cache is purged, this should go away.  Closing this.  Please reopen if still an issue.",1373061530,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fmgdk7zrdnkog3djzdrc,task_subcomment,NA
+<span> floats out of a table(?),"I can reproduce this against current production VisualEditor/Parsoid on that oldid but not the current id. I'm presuming that this is a Parsoid bug, but not sure of the severity.",1373057068,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fmgdk7zrdnkog3djzdrc,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"On a CAPTCHA-triggering edit, VE does not display the CAPTCHA, instead showing an alert:
+
+Error saving data to server: Failed request: error.
+
+Marking critical, because VE is in use by 50% of new users at enwiki, none of whom are now able to add external links for sourcing purposes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372413660,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-lsxohsnqwom7fu46vsrm,task_description,resolved
+VisualEditor: Edits triggering CAPTCHA cannot be saved,[[mw:Thread:Extension talk:VisualEditor/VE and ConfirmEdit]],1395111940,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,This is now fixed in master and will be deployed on Monday.,1372582072,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"Change 71160 merged by jenkins-bot:
+mw: Implement support for ConfirmEdit and FancyCaptcha
+
+https://gerrit.wikimedia.org/r/71160",1372563855,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"Change 71160 had a related patch set uploaded by Krinkle:
+mw: Implement support for ConfirmEdit and FancyCaptcha
+
+https://gerrit.wikimedia.org/r/71160",1372537638,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"Right now the handling of any error results the following alert:
+
+> Error saving data to server: Failed request: {api.result}.
+
+The only variable we use is the result code, not the error code. And though the error code varies (badtoken, hookabort, needcaptcha) the result is always ""error"".
+
+Fortunately (at least) the ConfirmEdit extension, and specifically the FancyCaptcha variant (which Wikimedia uses) does provide an API and exposes the following through the EditPage/ApiEdit/ApiVisualEditor result:
+
+{
+    ""visualeditor"": {
+        ""result"": ""error"",
+        ""edit"": {
+            ""captcha"": {
+                ""type"": ""image"",
+                ""mime"": ""image/png"",
+                ""id"": ""626590462"",
+                ""url"": ""//alpha.wikipedia.krinkle.dev/w/index.php?title=Special:Captcha/image&wpCaptchaId=fa4e388ad7""
+            },
+            ""result"": ""Failure""
+        }
+    }
+}
+
+So it looks like we can use this to build the UI for it.",1372458780,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"This depends on MediaWiki making the CAPTCHAs available through an API, which I believe is currently not done. Timo to comment.",1372450760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"(In reply to comment #0)
+> Error saving data to server: Failed request: error.
+
+The same error is also seen when triggering the spam blacklist.",1372422758,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"When attempting an edit that is disallowed by AbuseFilter, you get a browser alert:
+
+Error saving data to server: Unsuccessful request: The modification you tried to make was aborted by an extension hook.
+
+Instead, VE should show a less cryptic message specific to AbuseFilter.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372407600,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-yhjioiu5qdrnau76umcl,task_description,resolved
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,This has now been done and will go out today.,1372703938,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"Change 71293 merged by jenkins-bot:
+mw.ViewPageTarget: Show save errors in save dialog instead of alert
+
+https://gerrit.wikimedia.org/r/71293",1372703904,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"Given that AbuseFilter (but not others) depend on bug 32216, I'm moving that part to a new bug, bug 50472; the rest of this bug will be done today.",1372618721,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"AbuseFilter, wgSpamRegex (core), TitleBlacklist, SpamBlacklist, ..",1372617952,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"Change 71293 had a related patch set uploaded by Krinkle:
+(DRAFT) mw.ViewPageTarget: Show unrecoverable/unknown save errors in dialog instead of alert
+
+https://gerrit.wikimedia.org/r/71293",1372617672,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VE does not support typing in Kannada,"VE's behaviour is not as expected when I invoke my own IME for entering Kannada text. If I press Enter after typing some text, it creates a blank line above the current line rather than below the line. Some conjuncts also get dissociated and show sthe constituent Unicode character instead of the conjuncts. I am using Windows 8 and Firefox (ver 21). I tried using the built-in IME as well as Baraa IME. in both cases I could not use the VE for typing in Kannada.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372403160,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-2qe7sdslfntthznnkcbt,task_description,resolved
+VE does not support typing in Kannada,"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!",1377202358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"Change 80080 merged by jenkins-bot:
+Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",1377164912,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"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",1377027669,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"Hi, thanks for your help.
+
+I think the issue may be resolved by the following patch: https://gerrit.wikimedia.org/r/#/c/79451 . Or at least, the problems may be different now. I'm not sure it's working correctly with the ""Kannada inscript (m17n)"" ibus input method on Ubuntu+firefox, but it would be good for a Kannada reader to verify this!",1376936950,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"VE Kannada screen shot after pressing spacebar
+
+**Attached**: {F11104}",1373357251,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"VE Kannada screen shot before pressing spacebar
+
+**Attached**: {F11103}",1373357196,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"(In reply to comment #5)
+> I am not sure if the VE has been improved. But now I am able to type in
+> Kannada
+> if I use the Windows built-in IME as well as the Indic IME2 developed by
+> Microsoft-India. But the Baraha IME is still giving problems. I am waiting
+> for
+> the ULS to be enabled in VE.
+
+This was somewhat prematured comment. When I thoroughly tested I found some bugs in built-in IME as well as Indian IME2 also. It does render properly initially, but when I press space bar, the display gets spoiled. I will add the screeenshots.",1373356552,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,I am not sure if the VE has been improved. But now I am able to type in Kannada if I use the Windows built-in IME as well as the Indic IME2 developed by Microsoft-India. But the Baraha IME is still giving problems. I am waiting for the ULS to be enabled in VE.,1373353002,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,I treid the built-in IME of Windows 8 as well as a thrid party IME called Baraha.,1372417654,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"Thanks for taking the time to report this and testing VE!
+What are the exact steps to reproduce this?
+
+I tried:
+1. Make sure to be logged in on http://kn.wikipedia.org/
+2. Make sure that on http://kn.wikipedia.org/wiki/%E0%B2%B5%E0%B2%BF%E0%B2%B6%E0%B3%87%E0%B2%B7:Preferences?uselang=en#mw-prefsection-editing > ""Beta features >  Enable VisualEditor (only in the main and user namespaces)"" is enabled.
+3. Go to a random article like http://kn.wikipedia.org/wiki/ಔಷಧೀಯ_ರಸಾಯನಶಾಸ್ತ್ರ?veaction=edit
+4. I can confirm that keyboard cursor in on top of text, but I can type (Firefox 18).
+
+5. Click the cog next to ""ಇತರ ಭಾಷೆಗಳು"" (In other languages) and choose ""Input settings"".
+6. ""Input methods for ಕನ್ನಡ"" says ""Use native keyboard"".
+
+So here I have several options.
+
+Could you confirm/correct the above steps, and explain which ""built-in IME"" you exactly tried?",1372414516,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"VE screenshot just after pressing Enter key
+
+**Attached**: {F11102}",1372413796,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"VE screenshot just before pressing Enter key
+
+**Attached**: {F11101}",1372413758,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears","As Rob spotted, we should (re-)place the cursor in the block.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372384440,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jidkdocy777f7fa4pk3t,task_description,resolved
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears",Merged and will be deployed shortly.,1372706749,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jidkdocy777f7fa4pk3t,task_subcomment,NA
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears","Change 71388 merged by jenkins-bot:
+Restore focus to documentNode on convert
+
+https://gerrit.wikimedia.org/r/71388",1372706703,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jidkdocy777f7fa4pk3t,task_subcomment,NA
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears","Change 71388 had a related patch set uploaded by Robmoen:
+Restore focus to documentNode on convert
+
+https://gerrit.wikimedia.org/r/71388",1372705249,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jidkdocy777f7fa4pk3t,task_subcomment,NA
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears","On a note about this at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Cursor_disappears, I tested - I don't have the issue in Chrome (the cursor remains), but it is evidently still disappearing in Firefox. Just an FYI. :)",1372595247,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-jidkdocy777f7fa4pk3t,task_subcomment,NA
+VisualEditor: Category leaks out of transclusion when round-tripped through VE,"Example diff:
+
+https://en.wikipedia.org/w/index.php?title=FC_Dila_Gori&curid=6581323&diff=561887535&oldid=561367008
+
+Works in Parsoid:
+
+echo '{{commons category}}' | node parse --wt2wt
+{{commons category}}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50120",1372375380,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cc4653x6b7o5qyh3ddoy,task_description,resolved
+VisualEditor: Category leaks out of transclusion when round-tripped through VE,This was fixed by the fix for bug 50120. The DOM produced by the {{commons category}} template is very similar to the persondata template.,1373500548,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cc4653x6b7o5qyh3ddoy,task_subcomment,NA
+VisualEditor: Category leaks out of transclusion when round-tripped through VE,"Looks like a link element that is also encapsulated is not properly handled by VE:
+
+<link rel=""mw:WikiLink/Category"" href=""./Category:Commons_category_without_a_link_on_Wikidata"" data-parsoid='{""stx"":""simple"",""a"":{""href"":""./Category:Commons_category_without_a_link_on_Wikidata""},""sa"":{""href"":""Category:Commons category without a link on Wikidata""}}' about=""#mwt1"">",1373485070,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cc4653x6b7o5qyh3ddoy,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),"Screenshot
+
+Screenshot - FireFox 21.0, Mac OS X 10.6.8
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11044}",1372368720,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-q4tev2wggvrevxlx57l3,task_description,resolved
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),"Yes, this was fixed but the deployment was temporarily rolled-back until ~ 13:40 UTC today.",1372446220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),Maybe it's fixed but not out yet? http://it.wikipedia.org/wiki/File:Schermata_2013-06-28_alle_15.15.44.png on it.wiki this afternoon.,1372444061,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),*** Bug 50364 has been marked as a duplicate of this bug. ***,1372417299,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),*** Bug 50276 has been marked as a duplicate of this bug. ***,1372387036,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),Fixed and will be going out in the next few minutes.,1372380458,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),"Change 70786 merged by jenkins-bot:
+Fix bug where the floating toolbar was on top of the save dialog
+
+https://gerrit.wikimedia.org/r/70786",1372378996,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),"Change 70786 had a related patch set uploaded by Jforrester:
+Fix bug where the floating toolbar was on top of the save dialog
+
+https://gerrit.wikimedia.org/r/70786",1372373151,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"The VisualEditor doesn't currently have a mechanism for inserting special characters - while a lot of them are unnecessary (`~~~~` for example), things like en and emdashes can be quite important for content.
+
+**See Also**: {T13130}",1372349160,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_description,resolved
+VisualEditor: Provide a character insertion tool,"(In reply to comment #36)
+> 1: no one knows them/uses them
+
+Well, that disscutalbe, but I tend to think the same. No one knows them, because you dont need to know them for normal sw use.
+
+> So some ideas:
+> 1: Educate the user: Add a 'more characters' link in the insert symbol
+> editor,
+> that detects OS of user and links to a page explaining how to access this
+> panel
+> on his OS.
+
+Why to make it more difficult for users. We want them to attract to Wikipedia and we wont do do the environment as easy as possible. Our goal is not to educate them further things.",1387303644,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Change 90940 merged by jenkins-bot:
+Insert special character tool
+
+https://gerrit.wikimedia.org/r/90940",1386312904,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"""Educating"" the user strikes me as a sign of failure for a supposedly ""easier"" UI. The ""harder"" UI has it right there, after all.",1385650860,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"> Just for reference: Either I didn't read all the comments well enough or nobody
+> quite mentioned the fact that all modern desktop operating environments have a
+> built-in a Character Map tool: Windows (with pretty full Unicode since NT 4),
+> Gnome, KDE, and Mac OSX (called ""Character viewer"").
+
+On Mountain Lion, it's even simpler. (Straight in the edit menu, ctrl-cmd-space).
+
+I mentioned it, but the problem is indeed:
+1: no one knows them/uses them
+2: there is no trigger in HTML5/JS to open the panel
+
+So some ideas:
+1: Educate the user: Add a 'more characters' link in the insert symbol editor, that detects OS of user and links to a page explaining how to access this panel on his OS.
+2: Lobby HTML5 WG to expose these panels to JS",1385650141,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #34)
+> At present, however, there is no way to enter non-keyboard characters unless
+> you're much more familiar with your operating system
+Well, how doest it come, there is no way? What about to load character box available for editing on some wikies in MonoBook?
+
+> At present, however, there is no way to enter non-keyboard characters unless
+> you're much more familiar with your operating system than almost any user is.
+Do you have any statistic for this statment? I would say that most of the users are not familiar with that. But I should include it is my point of view.",1385284629,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Juan - I think that would quite definitely require actual usability lab testing. As would many of the suggestions in this bug.
+
+At present, however, there is no way to enter non-keyboard characters unless you're much more familiar with your operating system than almost any user is. So doing nothing isn't really an option either.",1383688795,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #32)
+> (In reply to comment #31)
+> > Just for reference: Either I didn't read all the comments well enough or
+> > nobody quite mentioned the fact that all modern desktop operating
+> > environments have a built-in a Character Map tool: Windows (with pretty
+> > full Unicode since NT 4), Gnome, KDE, and Mac OSX (called ""Character
+> > viewer"").
+> 
+> I said this, but everyone said it wasn't sufficient for them. :-(
+
+Lets say it differenty. Visual Editor Team was made to remove obstacles in editing, to simplify the work of Wikipedia contributors. Even there are voices, that it is a wrong way and newbies should study wikitext WFM goes the way of its goal. To offer all human knowledge to give to everybody. Our aim here is to collect the knowledge of all people. Logically higher amount of obstacles reduces the number of Wikipedians. Our aim is not to push newbies to study wikitext, internal policies or typography. Our aim is to harvest their knoledge. Thus in the new trend we are removing obstacles. So if not as a default, what about as an option to define your own characters (this was always possible in wp)? Than we can tell newbies, look here we place &ndash; - its not present in VE default, but you can install an extension to your VE.",1383688524,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #31)
+> Just for reference: Either I didn't read all the comments well enough or
+> nobody quite mentioned the fact that all modern desktop operating
+> environments have a built-in a Character Map tool: Windows (with pretty
+> full Unicode since NT 4), Gnome, KDE, and Mac OSX (called ""Character
+> viewer"").
+
+I said this, but everyone said it wasn't sufficient for them. :-(
+
+> 2. It may be easier to insert at least some characters using the keyboard
+> layout provided with ULS. It is disabled now in VE because of some bugs (can
+> anybody help me with the numbers?), but these can be fixed, of course. If we
+> know which characters are really needed (see point 1 above), we can very
+> easily add them to the keyboard layouts.
+
+Possibly. The main problem is that ""ULS"" is about twenty different tools, and some of them don't work in VisualEditor (yet). I doesn't seem possible to enable some of them and not others, however.",1383674338,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Just for reference: Either I didn't read all the comments well enough or nobody quite mentioned the fact that all modern desktop operating environments have a built-in a Character Map tool: Windows (with pretty full Unicode since NT 4), Gnome, KDE, and Mac OSX (called ""Character viewer"").
+
+That said, I am very well aware of the fact that pretty much nobody but me actually uses it. A very surprising number of people, however, do use the character insertion tool in their word processors. The one in Microsoft Word is not very different from Windows' Character Map, which in my mind makes it redundant, but apparently I'm special.
+
+Anyway, yes - a character insertion tool should be there.
+
+But, two points:
+
+1. There's one already in Vector, and it's quite good. It can be used for research - which characters are used most frequently in which project. Adding statistics for this is quite easy now with EventLogging.
+
+2. It may be easier to insert at least some characters using the keyboard layout provided with ULS. It is disabled now in VE because of some bugs (can anybody help me with the numbers?), but these can be fixed, of course. If we know which characters are really needed (see point 1 above), we can very easily add them to the keyboard layouts.",1383663006,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Well, when creating Featured or Quality articles we (on cs.wp) looks to have them correct from typograpical point of wiev. The problem is that Czech keyboard doesnt include all characters needed, as it includes other characters, which are not native to English. The most common missing characters would be *, #, &ndash;, &nbsp;. So if not all it would be nice to have in VE or nearby the table with some most used characters. E.g. list items are present in English keyboard, while &ndash; suprisingly not.",1383640351,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #27)
+> If this selection tool is ever provided, please make sure users have an
+> option not to load it at all (see bug 11130 for this problem in the context
+> of MediaWiki:Edittools)
+
+It's very unlikely that we'll start adding per-user preferences to switch things like this on and off (some VE version of bug 9754); that's a very complex and confusing thing to allow.
+
+Note BTW that bug 11130 is complaining about assuming users have JS (already known inside VE), lack of ability to cache (fixed by VE's nature), and taking up lots of screen estate (fixed by how we'll do this); I don't think it's a direct comparison. I'd also note that bug 11130 hasn't been done despite it being filed 6 years ago, which strongly suggests that it's not a priority.",1383411270,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Change 90940 had a related patch set uploaded by Jforrester:
+[WIP] Insert special character tool
+
+https://gerrit.wikimedia.org/r/90940",1383409609,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"If this selection tool is ever provided, please make sure users have an option not to load it at all (see bug 11130 for this problem in the context of MediaWiki:Edittools)",1383125351,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**eleriygarregwen** wrote:
+
+When I proposed a whole collection of sequences of characters to put into the ULS input method for Welsh, which uses a lot of diacritics, the comment from CYWP was that it would be a lot of work to memorise these character sequences, and it is not easy to find out about the ULS input methods.
+
+The bar of characters under the edit box is very easy to understand, just by looking at it, and having a go. Almost no-one needs a help page on how to use it. Once you know what it does, there is nothing to memorise, and nothing to forget. Since simplicity is the aim with VisualEditor (to encourage new users), the bar of characters wins over anything more complicated, in my opinion.",1383083841,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"I agree with James Forrester's comment #0. Character input in particular languages should be possible, but through the universal language selector, and in all text inputs on the website.
+
+I think the ideal way to handle en dashes and em dashes would be to make ""--"" be replaced by the wikitext parser by an en dash (–), ""---"" by an em dash (—) and ""----"" by an horizontal bar (―). The current horizontal rule syntax would become ""-----"" (it would require one more hyphen-minus because the current one would be taken by the horizontal bar character). There would therefore become part of the syntax. DokuWiki does this for en dashes and em dashes (https://www.dokuwiki.org/wiki:syntax#text_to_html_conversions), but not the others.
+
+As I mentioned, this is what I think would be the ideal way to handle it. Practically, this is impossible because these sequences are already used in many pages for other purposes. An acceptable solution would, I believe, be to make the editor recognize those sequences and replace them automatically by the corresponding character. This would be reasonable in the VisualEditor and would be more efficient than putting a bar of characters under the edit box and hoping beginners will use it to insert dashes. However, since the sequence ""--"" is used in signatures on talk pages and possibly for other things in wikitext, it may be preferable to avoid doing these replacements in the source editor.
+
+It might be a good idea to add sequences of characters for producing similar characters. As long as the sequences are well chosen, problems should not arise frequently, and this could reduce considerably the typographical burden put on beginners.",1382936493,PHID-USER-2rwkb3az6uklfhh5aqw5,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**lebo.beland** wrote:
+
+I didn't read the whole thread,  but I suggest to look at including Mediawiki:Edittools in the Visual Editor. For many projects, this include the special characters and useful stuff specific to each project.
+
+Thanks,",1382929831,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,*** Bug 55496 has been marked as a duplicate of this bug. ***,1381329553,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Czech editors have compiled a list of characters they find are vital for their day-to-day editing. From https://cs.wikipedia.org/wiki/Diskuse_k_Wikipedii:VisualEditor
+
+
+
+Output	Name	                                Entity	Decimal
+ 	nobreak space	                        &nbsp;	&#160;
+ 	thin space	                        &thinsp;	 
+„	curly quotation marks begin (99)	&bdquo;	&#8222;
+“	curly quotation marks end (66)	        &ldquo;	&#8220;
+‚	simple curly quotation marks begin	&sbquo;	&#8218;
+‘	simple curly quotation marks end	&lsquo;	&#8216;
+–	n-dash	                                &ndash;	&#8211;
+×	times	                                &times;	&#215;
+
+In particular, both kinds of quotation marks (we are very particular about those, like the French about theirs) could be insertable either one by one or in pairs, like so: „“ and ‚‘.
+In general, easy access to inserting those characters would be a very desirable feature for Czech editors – and even better would be the MS Word functionality that automatically converts minuses into n-dashes and ""English quotation marks"" into „Czech quotation marks“. Best, Littledogboy (diskuse) 1. 10. 2013, 11:35 (UTC)
+Important: Although I've listed their codes, we usually enter n-dash and curly quotation marks NOT as html entities, but simply like so „–“ (Alt-0132, Alt-0150, Alt-0147 – yes, I am a robot). Littledogboy (diskuse) 1. 10. 2013, 11:51 (UTC)",1380652688,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"The other problem is that with VE having no source mode as yet, I can't even resort to HTML entities.",1380018347,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Further to comment 18 and comment 19 a big use case of the character insertion toolbar is to insert characters one does not frequently use.
+
+Utilities like an external character map are very inefficient because it disrupts the work flow, requires you to find the character you want, and copy and paste the character you need. It also replaces whatever else you had in the clipboard previously that you may still need.
+
+Dead keys are useful only if you know that they exist, know how to set them up (they are not enabled by default on most US and UK systems at least), and know the combinations required to input the character you want. I have a much better memory for things like that than many people, and while I know ones like é, Ŵ, ß, ° and ö, characters like ř, Đ and ố I don't. As far as I know, characters in other scripts like д, ζ, ب ,ש, are not producible using deadkey combinations.
+
+Input methods are a very heavy weight solution to inputting characters not found natively on one's keyboard. They always require setting up in advance for each script (and some script/language combinations I think) and learning how to produce each desired character. I only use this method for IPA because I did a lot of work with pronunciations at Wiktionary and that required learning that to produce /ˌbʌɡˈzɪlə/ I need to type /%bVg""zIl@/ - hardly something we can expect a casual editor to learn.  
+
+One of the primary goals of VisualEditor is to reduce the barrier to contributing to Wikimedia projects, not having a character insertion tool is rather contradictory to this.",1380018097,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"I need to point out the irony of developing an editing interface with the good faith but technically challenged user in mind, and then expecting them to know how to use their browser/operating system to insert an emdash (a character not present on the standard English keyboard, but used over a million times on English Wikipedia). Given the target group for this extension, this isn't a low-priority enhancement, it is core functionality. In fact, the existing editorial base uses the edit tools almost exclusively over their browser/operating system, and I suspect many of them (including me) have no idea how to do use the latter.",1379917317,PHID-USER-yif6nz5uhka5cnltixpc,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Yep. When you need to add an accented character, you need to add an accented character. This is a quite definitely missing facility.",1379690527,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Another request today for [[MediaWiki:Edittools]] or an equivalent to be available in VE.
+
+I second comment 8 and comment 10 - this is one of the features of the source editor that editors really miss.",1379686473,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Sorry Lloffiwr, my bad: I thought that Welshp WP had somehow made that set of characters already available with VisualEditor as well.",1377688397,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**eleriygarregwen** wrote:
+
+""Lloffiwr, can you link to this workaround?"" - Sorry I don't know what you are asking me to do.
+
+With regard to using our own edit tools, that would be very good. It is very simple to just click on one of a number of characters sitting on a toolbar right next to the editor. You don't have to remember key combinations, there is no need to look up a help page and learn how to insert characters. The character toolbar's purpose in the normal editor is obvious and it is ready to use for all users (you don't have to enable a special keyboard as you would with the ULS).
+
+By the way, in the ""save"" dialog of the VisualEditor on CYWP, we see an image of our short character toolbar, but have no way of actually using it! I, an experienced editor, was very confused by this; the new editors for whom this tool is designed are likely to be completely floored by it.",1377641765,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Lloffiwr, can you link to this workaround? I tried enabling VE on your wiki but that was not enough, should I also enable some gadget maybe? 
+James, until this or other IME issues are not solved, isn't there a way to let these wikis use their very own edit tools, i.e. http://pms.wikipedia.org/wiki/MediaWiki:Edittools ?",1377258190,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**eleriygarregwen** wrote:
+
+To make life easy on the Welsh Wikipedia, we have added a short character set consisting only of the most commonly used special characters immediately below the edit window. We have also added a more comprehensive set of special characters further down below the edit window. I think it would be useful to add the full character set to VisualEditor as standard, but also to allow each Wikipedia to add its own special character set via an optional message.",1375136279,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,This is among the most important missing features for dewp.,1375019373,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**eleriygarregwen** wrote:
+
+Another example of a language whose users make heavy use of the character insertion tool underneath the old edit window is Welsh (cy). Some of us work with keyboards which have been specially adapted to easily type the diacritics needed (including ŵ and ŷ) but not all hardware devices have this software loaded. This means that the VisualEditor is very difficult to use for some users, making training sessions for new users (some with, some without the diacritics software) difficult to conduct using VisualEditor.",1374356830,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Agreed with comment 8. The special characters insertion tool in WikiEditor is very convenient when editing articles about topics that involve other scripts or diacritics. Not providing such a tool in VisualEditor would seriously reduce VE's usefulness, and would certainly provide a compelling reason to use the source editor much more often than otherwise necessary.",1374264181,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"BTW, if we ever do get another symbol picker, please make it share it's table with WikiEditor, limiting the places where we need to maintain these chars. (We already have 3 [WikiEditor extension, MediaWiki:Edittools, MediaWiki:Edittools.js])",1374264087,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"""Character insertion is, in general, the responsibility of your browser/operating system""
+
+Yes and no. Yes, your computer is capable of inserting loads of characters. No, it is not always reachable.
+
+At least, I know of no operating system + browser combination, where I can put my cursor in a text area and bring up a symbol picker from the menu or a toolbar. (Unlike spellchecking).",1374263950,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,*** Bug 51120 has been marked as a duplicate of this bug. ***,1374263430,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"http://en.wikipedia.org/wiki/File:VE_modified_ui_suggestion.png shows one user's suggestion.  
+
+See http://en.wikipedia.org/w/index.php?oldid=564286664#Thoughts_about_UI_improvements for the discussion.",1373843965,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"There was a similar request on Portuguese Wikipedia[1]. A user wanted to use the kind of tool we see in the screenshot [2].
+
+
+[1] https://pt.wikipedia.org/wiki/WP:Editor_Visual/Coment%C3%A1rios?oldid=36280987&uselang=en#Adi.C3.A7.C3.A3o_de_caracteres_especial_no_Visual_editor
+[2] http://postimg.org/image/mwbyn96gn/",1372773901,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,Nonbreaking spaces would be helpful as well.,1372736869,PHID-USER-jdkjcyuluyy456zxyufo,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,We've had another comment re: emdashes here:http://en.wikipedia.org/w/index.php?title=Wikipedia_talk:VisualEditor&curid=37920680&diff=562488469&oldid=562482174,1372735991,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Well, I'm sat on my windows machine here and can't see any way to type an emdash, for example :/",1372356235,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #0)
+> The VisualEditor doesn't currently have a mechanism for inserting special
+> characters - while a lot of them are unnecessary (~~~~ for example), things
+> like en and emdashes can be quite important for content.
+
+Character insertion is, in general, the responsibility of your browser/operating system (same as spell check, IME and other general editing tools). Where your local OS fails, we have a 'standard' of providing general tools to let you get OS-level tools (most notably, ULS), rather than one-off ""insert a bunch of random characters"" micro-tools.
+
+MediaWiki has given people tools to insert random characters primarily because they do special things, and we've given up on users being able to magically know them (like ~~~~ or {{DEFAULTSORT:}}). They're all examples of system design failure. The fact that we have extended the metaphor to give ""helpful"" characters that users can trivially type themselves isn't a great reason to create it from scratch.
+
+I'm not dead-set against this, but it feels like a clunky failure. :-(",1372355885,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Backspace at the beginning of a line before an image inserts the succeeding text as a thumbnail caption,"Screenshot
+
+See the screenshot; before and after the backspace, respectively.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51624
+
+**Attached**: {F11902}",1372341120,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-kum7spdwx5xdoe73t4u5,task_description,resolved
+VisualEditor: Backspace at the beginning of a line before an image inserts the succeeding text as a thumbnail caption,This was fixed months ago; sorry for not spotting this bug report until now.,1384944160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kum7spdwx5xdoe73t4u5,task_subcomment,NA
+VisualEditor: Backspace at the beginning of a line before an image inserts the succeeding text as a thumbnail caption,This is the same issue as Bug 51624 that was originally reported as happening with table cells and then extended to include image captions. I'm not sure which should me marked as duplicate of the other,1374599258,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kum7spdwx5xdoe73t4u5,task_subcomment,NA
+VisualEditor: Template/Image node shields should not not appear on top of the toolbar,"Screenshot
+
+See screenshot. The template inspector overlaps not only the document (that would be good - see 50241) - but the toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11898}",1372339980,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-7u4x4gvkmazindkefefh,task_description,resolved
+VisualEditor: Template/Image node shields should not not appear on top of the toolbar,This would have been fixed this time last week with the general z-index re-write; sorry for only getting to this now.,1373519669,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7u4x4gvkmazindkefefh,task_subcomment,NA
+VisualEditor: Template/Image node shields should not not appear on top of the toolbar,Another complaint about this - the editor was using Google Chrome 28.0.1500.63 on Ubuntu 13.04.,1372793827,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-7u4x4gvkmazindkefefh,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","Not sure if this should be filed under VisualEditor or Translate.
+
+When clicking the ""edit source"" button on a translation or a page that uses the Translate extension, it isn't possible to edit the wikitext directly; instead, the user is told to use the Translate extension to change the content.
+
+When clicking the ""edit"" button on a translation of a page that uses the Translate extension, it's possible to edit the text with VisualEditor. At first, I thought this was a feature, and that changes would be propagated to the Translate extension, until I tried to save the page and got the following error:
+
+Error saving data to server: Unsuccessful request: Unknown error: ""tpt-target-page"".
+
+If VisualEditor can't be used to edit those pages, it probably shouldn't lead users to believe it can :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48891
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61218",1372338540,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_description,resolved
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","Change 119427 merged by jenkins-bot:
+Disable VisualEditor on Page Translation output pages
+
+https://gerrit.wikimedia.org/r/119427",1395268059,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","Change 119427 had a related patch set uploaded by Jforrester:
+Disable VisualEditor on Page Translation output pages
+
+https://gerrit.wikimedia.org/r/119427",1395190355,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","(In reply to comment #9)
+> I just VEdited a page on mw.org (Communication) and it seemed to work (beyond
+> the translate tags showing up).
+
+Nope, the error happens when you try to edit a translation, not the source page :) e.g. try to edit Communication/it",1380618535,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",I just VEdited a page on mw.org (Communication) and it seemed to work (beyond the translate tags showing up).,1380277979,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",I assume VE checks whether the page is editable somewhere? I wonder if changing the hook in Translate from getUserPermissionsErrorsExpensive to getUserPermissionsErrors would solve this? Would have to make sure that the hook is efficient then.,1374942941,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","Presumably there is a simple check we can do for whether the page is under the protection of the Translate extension, so we can do
+
+if (
+  …
+  if <Translate extension installed> && !<page is Translate-protected>
+  …
+) { <do not load> }
+
+… in the code in ViewPageTarget init?",1374858968,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",*** Bug 51805 has been marked as a duplicate of this bug. ***,1374854170,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",*** Bug 51931 has been marked as a duplicate of this bug. ***,1374703814,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","e.g.
+https://www.mediawiki.org/wiki/Communication/hu?veaction=edit",1374310653,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",%%%*** Bug 51534 has been marked as a duplicate of this bug. ***%%%,1374071458,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","I tested this on mediawiki.org following a report on the English Wikipedia, but instead of getting an error VisualEditor just silently refused to save the page - the progress bar appeared for a typical amount of time then I was back to the save dialog as if I hadn't pressed save. Lather, rinse, repeat.",1374003370,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",Just a note to say that this keeps happening. Thanks!,1373956496,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+VisualEditor: VE eats away the end of </ref>}} templates,"It has happened to me several times that after a simple edition VisualEditor or Parsoid breaks the ""</ref>}}"" at the end of a reference template. I still don't know which is the pattern, but at least this time I realized it:
+
+http://ca.wikipedia.org/w/index.php?title=El_Chornaler&diff=11962426&oldid=11962407
+
+Other times a second editor had to come after me fixing the broken template. In the preview before saving everything looks fine.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372313340,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oqhko7t4wfln3rpauqc5,task_description,resolved
+VisualEditor: VE eats away the end of </ref>}} templates,I can't reproduce it either. Let's say it's fixed.,1375941682,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oqhko7t4wfln3rpauqc5,task_subcomment,NA
+VisualEditor: VE eats away the end of </ref>}} templates,I can't now reproduce this - is it still occurring?,1375486975,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oqhko7t4wfln3rpauqc5,task_subcomment,NA
+extension Campaigns (and some others?) not current,"http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version shows extension Campaigns not updated since 12 June, but should be current as of https://gerrit.wikimedia.org/r/#/c/69841/ at least.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372283340,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-erpehiwtm4uj5znmo2et,task_description,resolved
+extension Campaigns (and some others?) not current,"(In reply to comment #4)
+Yes. I made a trivial update to Campaigns, and after merging to master it was on http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version within minutes.",1372377246,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+extension Campaigns (and some others?) not current,Well Campaigns is still broken right now.  I guess it will be up to date whenever a commit is merged in that repository,1372350405,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+extension Campaigns (and some others?) not current,"A bunch of them were broken.
+
+Fixed in https://gerrit.wikimedia.org/r/#/c/70834/.",1372349281,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+extension Campaigns (and some others?) not current,And see bug 49846 mediawiki/extensions.git does not update VisualEditor,1372348373,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+extension Campaigns (and some others?) not current,I guess it is misconfigured on Gerrit side (see bug 49906).,1372348270,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"if an article starts with 
+==Foo==
+Bar Baz Fizz Buzz
+
+It is impossible to remove ==Foo== without having the paragraph take on the h2 markup
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372276980,PHID-USER-n27daagbl3wqf3ghr4nk,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_description,resolved
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"**Wikifram** wrote:
+
+(ec) Yeah, I'm a bit frustrated by the number of errors in that status update, and the apparent lack of possibilities to correct these (even as an addendum or some such) and lack of care about this among the people responsible for this. Not your fault though. Thanks for filing that bug.",1380880306,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,Filed as bug 54964,1380880152,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"Steady on, they're similar bugs and easy to confuse.
+
+The case you describe at the end does sound like a separate bug.",1380879819,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"**Wikifram** wrote:
+
+(In reply to comment #10)
+> You're confusing this with bug 50100.
+
+Not my mistake though, this was reported like this in the VisualEditor weekly update - 2013-09-26 (MW 1.22wmf19) by Jdforrester:
+
+""Blanking the contents of a heading, pre-formatted block or other formatting block now deletes the block rather than leaving it empty, which is consistent with how OpenOffice and Google Docs behave (bug 50254)."" 
+
+I noted that what the VE status report describes is ''not'' fixed, and followed the link number given in the VE status report. If this bug is about something else than what the VE status report described, then this is just one more in the already long list of things wrong with that status report (for which it is apparently ""impossible"" to write an update or correction in any way, shape or form). 
+
+Anyway, you still get the behaviour as described: Go to the first word you want to keep (after the initial header), and use backspace to remove the header: your next paragraph now becomes the header. Only when you first empty the header (leaving the line beneath it), and then go to the text and use backspace, is it possible to remove a starting header without converting the following text into a header. I wouldn't call this ""solved"", perhaps ""somewhat improved"" assuming that the latter possibility / workaround didn't work in the past. (I note that you only go to the start of the heading, and then select ""downwards"" instead of ""sideways""; deleting the header like this works as well)
+
+Note also that if yu eventually get rid of that header, it seems to be impossible to remove a first empty line from an article: [https://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=575703425&oldid=575703070]. Probably needs a different bug (or already exists), but not really optimal either.",1380878361,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,You're confusing this with bug 50100.,1380876577,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"**Wikifram** wrote:
+
+Nice that this is solved, except that it isn't. I had already noted that at MediaWiki, it still blanks the header (but doesn't add nowiki). Tested today at enwiki, and sadly, even worse, again a nowiki was added inside the header instead of removing the empty header: [https://en.wikipedia.org/w/index.php?title=Robbers_Cave_State_Park&diff=575691345&oldid=558376701]
+
+Has this patch ever worked anywhere? Diff?",1380869071,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"Change 85673 merged by jenkins-bot:
+Delete empty nodes instead of merging into them
+
+https://gerrit.wikimedia.org/r/85673",1380047332,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,The delete-when-empty-merge-otherwise behaviour implemented by the patch above is also used by OO/LO & Google docs.,1379946372,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"Change 85673 had a related patch set uploaded by Esanders:
+Delete empty nodes instead of merging into them
+
+https://gerrit.wikimedia.org/r/85673",1379946235,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,This is a separate issue to bug 51829 (now bug 50100).,1379946203,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"It happens to me always, even if the heading is in the middle of the page.",1374826649,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"They definitely seem related, with the distinction that this but has the problem that there is no slug (am I using the lingo right) on the line above the first header if the header is the first element of the page. Merge however you feel is most useful.",1374524826,PHID-USER-n27daagbl3wqf3ghr4nk,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"Actually, this bug looks to be a subset of Bug 51829 is this best merged or that bug better split?",1374518185,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"As a workaround, it is possible to convert the header to paragraph text and then delete it. That is no better though than deleting and then converting the changed text back to a paragraph.",1374517963,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Yet another dirty-DOM on basic templates,"Link shows a diff made post-deploy doing (what happened to be white-space only) normalisation in two templates (that weren't touched). :-(
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=Pgeezy&curid=38061582&diff=561709972&oldid=561568473",1372274040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjnunyjomlrvhkq4oiqo,task_description,resolved
+VisualEditor: Yet another dirty-DOM on basic templates,After today's deployment this now appears to have been fixed. Marking as such.,1373518136,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjnunyjomlrvhkq4oiqo,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"I want to get rid of jobs on the master instance and have them all on slaves.  Master is currently gallium.wikimedia.org which also have a slave installed on it and named 'gallium'.
+
+This is a tracking bug.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1372254540,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vvu5ucedidqohifits2s,task_description,resolved
+Jenkins: migrate all jobs from master to slaves,[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343629,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,Marked master has being down.  People should use the 'gallium' slave to tie jobs to that server or they could use a label.,1373287838,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://integration.wikimedia.org/ci/computer/(master)/
+
+Master (the master Jenkins node)
+Projects tied to master
+None
+
+\O/
+
+I guess we can now remove master as an executor.",1373031852,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,Reduced number of executor on master from 4 to 2.  There are only the qunit jobs left there (bug 50231).,1372425380,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://gerrit.wikimedia.org/r/71006 migrated the wikibase jobs:
+
+mwext-Wikibase-client-tests
+mwext-Wikibase-repo-tests",1372422296,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://gerrit.wikimedia.org/r/#/c/71000/ migrates mediawiki regression jobs
+
+mediawiki-core-regression-REL1_19
+mediawiki-core-regression-REL1_20
+mediawiki-core-regression-REL1_21
+mediawiki-core-regression-master",1372415240,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://gerrit.wikimedia.org/r/#/c/70999/ migrates some doc jobs:
+
+
+mediawiki-core-doxygen-publish
+mediawiki-core-jsduck-publish
+mwext-VisualEditor-doc-publish
+operations-puppet-doc (bug 50233)",1372413785,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://gerrit.wikimedia.org/r/#/c/70917/ updated jobs:
+
+mediawiki-core-phpunit-api
+mediawiki-core-phpunit-databaseless
+mediawiki-core-phpunit-misc
+mediawiki-core-phpunit-parser",1372366694,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,List of tied jobs is available at https://integration.wikimedia.org/ci/computer/(master)/  That list needs to shrink to 0 elements.,1372254654,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","e.g. ""menuitem"" for options in our select widgets.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372205340,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u2ls26f436dp4ls4xqnj,task_description,resolved
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate",Looks fine from my POV.,1406079764,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","Anything left to do here, Timo/James?",1406066234,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","Change 148253 merged by jenkins-bot:
+Add role attribute to a few widgets
+
+https://gerrit.wikimedia.org/r/148253",1406065761,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","Change 148253 had a related patch set uploaded by Alex Monk:
+Add role attribute to a few widgets
+
+https://gerrit.wikimedia.org/r/148253",1405981742,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","Most of this has already been done in OOUI, I think.",1405702134,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"**Author:** `swalling`
+
+**Description:**
+This tour step should only be shown in read mode.
+
+When starting the guided tour via the ""Show help"" help button with GettingStarted, guided tours thinks I am in read mode and displays broken steps, rather than skipping to the appropriate editing steps.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11708}",1372184520,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-x646ub2izdkijgiiwrz2,task_description,resolved
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"Change 72682 merged by jenkins-bot:
+Add tour for VisualEditor
+
+https://gerrit.wikimedia.org/r/72682",1374178920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"Change 72677 merged by Ori.livneh:
+Add support for VisualEditor
+
+https://gerrit.wikimedia.org/r/72677",1374165359,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"**swalling** wrote:
+
+(In reply to comment #5)
+> I fixed the issue where step 1 was shown when clicked ""Show help"" while in VE
+> editor, on a page with an ambox.  That's on toro for testing.
+
+Tested and working for me on toro. Once the patches are merged I think we can call this one fixed.",1374017584,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"I fixed the issue where step 1 was shown when clicked ""Show help"" while in VE editor, on a page with an ambox.  That's on toro for testing.",1373361751,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"This should be fixed by https://gerrit.wikimedia.org/r/#/c/72677/ and https://gerrit.wikimedia.org/r/#/c/72682/, pending review.",1373340182,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"Change 72682 had a related patch set uploaded by Mattflaschen:
+Add tour for VisualEditor
+
+https://gerrit.wikimedia.org/r/72682",1373340111,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"Change 72677 had a related patch set uploaded by Mattflaschen:
+Add support for VisualEditor.
+
+https://gerrit.wikimedia.org/r/72677",1373339962,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"**swalling** wrote:
+
+Note: this only happens if the user clicks ""Show help"" after editing in VE mode. Otherwise, the tour progresses normally. The easiest solution in the interim may be to ensure that we don't show the Getting Started toolbar in VE edit mode, like we do for wikitext editing.",1372184775,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"**Author:** `p.selitskas`
+
+**Description:**
+Dash-to-underscore conversion is frucked up yet again?
+
+When ""Edit"" is clicked, an API request is issued with params:
+action:visualeditor
+paction:parse
+page:Новая_зямля
+oldid:1630719
+token:[screened]
+format:json
+
+Response: {""servedby"":""mw1141"",""error"":{""code"":""parsoidserver-http-bad-status"",""info"":""404""}}
+
+VE works at be.wikipedia.org, but it doesn't work at be-x-old.wikipedia.org, bat-smg.wikipedia.org, and maybe other sites with dash in the site ID.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372164300,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lfvhcf2i2gcieggk662j,task_description,resolved
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"**p.selitskas** wrote:
+
+(In reply to comment #3)
+> I have fixed this in the Parsoid config.
+
+Can you publish the link to the change in Gerrit (if it is publicly available), just for my interest?
+
+Thanks for fixing, btw.",1372287816,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lfvhcf2i2gcieggk662j,task_subcomment,NA
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"(In reply to comment #2)
+> (In reply to comment #1)
+> > Roan - is this a config issue at our end or something else?
+> > 
+> > http://titanium.wikimedia.org/be-x-oldwiki/Галоўная_старонка?oldid=1535753
+> > and
+> > http://parsoid.wmflabs.org/be-x-old/Галоўная_старонка?oldid=1535753 both work
+> > fine for me, but in VE
+> > https://be-x-old.wikipedia.org/wiki/
+> > Галоўная_старонка?oldid=1535753&veaction=edit
+> > does indeed 404.
+> 
+> I think it's a config issue.
+> 
+> CommonSettings.php on line 1890 says:
+> $wgVisualEditorParsoidPrefix = $wgDBname;
+> 
+> DB names are written with underscores instead of dashes. Conversion '_'->'-'
+> should be performed here.
+> 
+Turns out we did actually have the DB names mapped correctly, but to the wrong URLs. We had stuff like:
+
+'map_bmswiki': 'http://map_bms.wikipedia.org/w/api.php',
+
+which is wrong, we need URLs with dashes.
+
+I have fixed this in the Parsoid config.",1372215518,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lfvhcf2i2gcieggk662j,task_subcomment,NA
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"**p.selitskas** wrote:
+
+(In reply to comment #1)
+> Roan - is this a config issue at our end or something else?
+> 
+> http://titanium.wikimedia.org/be-x-oldwiki/Галоўная_старонка?oldid=1535753
+> and
+> http://parsoid.wmflabs.org/be-x-old/Галоўная_старонка?oldid=1535753 both work
+> fine for me, but in VE
+> https://be-x-old.wikipedia.org/wiki/
+> Галоўная_старонка?oldid=1535753&veaction=edit
+> does indeed 404.
+
+I think it's a config issue.
+
+CommonSettings.php on line 1890 says:
+$wgVisualEditorParsoidPrefix = $wgDBname;
+
+DB names are written with underscores instead of dashes. Conversion '_'->'-' should be performed here.
+
+This is a typical error in WMF configs. I used to run against it even in MediaWiki core.",1372179812,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lfvhcf2i2gcieggk662j,task_subcomment,NA
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"Roan - is this a config issue at our end or something else?
+
+http://titanium.wikimedia.org/be-x-oldwiki/Галоўная_старонка?oldid=1535753 and http://parsoid.wmflabs.org/be-x-old/Галоўная_старонка?oldid=1535753 both work fine for me, but in VE https://be-x-old.wikipedia.org/wiki/Галоўная_старонка?oldid=1535753&veaction=edit does indeed 404.",1372172991,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfvhcf2i2gcieggk662j,task_subcomment,NA
+"VisualEditor: Attempting to de-bold a selection causes text to become ""extra-bold""","1. Edit [[mw:VisualEditor:Sfioj]] in VE
+2. Make a selection such as
+
+     These [words are] very bold
+or 
+     These wor[ds are ve]ry bold
+
+3. Click the ""Bold"" button on the toolbar
+
+The selected text goes extra-bold, in Firefox 21. 
+
+I should mention that in my case, the font is Arial, which has an extra bold ""Arial-Black"" variant.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372162080,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-j223oppi3t252tmumwbg,task_description,resolved
+"VisualEditor: Attempting to de-bold a selection causes text to become ""extra-bold""",*** Bug 52189 has been marked as a duplicate of this bug. ***,1385398575,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j223oppi3t252tmumwbg,task_subcomment,NA
+"VisualEditor: Attempting to de-bold a selection causes text to become ""extra-bold""",Patched and merged: https://gerrit.wikimedia.org/r/#/c/70434/,1372190547,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-j223oppi3t252tmumwbg,task_subcomment,NA
+"VisualEditor: Attempting to de-bold a selection causes text to become ""extra-bold""","There is a related problem with italic: try the same STR on the second line of the Sfoij page, using the ""italic"" toolbar button instead of ""bold"". But I think it is the same issue.",1372162241,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-j223oppi3t252tmumwbg,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,"Groups of consecutive images are alienated under certain circumstances. 
+
+It might have something to do with the wikilinks in the image caption, however I really just have to throw you some testcases:
+
+---
+(1) Works fine:
+http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493135&veaction=edit
+
+(2) Similar, but doesn't work:
+http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493351&veaction=edit
+
+(3) All three groups uneditable, even the group that is identical to (1) above:
+http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493252&veaction=edit
+
+(4) One group fine, the other alienated:
+http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493194&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372155360,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cohcqit7cjc474qs3bul,task_description,resolved
+VisualEditor: Groups of images are alienated under certain circumstances,See bug 51039.,1373422404,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,"(In reply to comment #3)
+> (In reply to comment #1)
+> > Do they work for you too?
+> 
+> Sorry, yes the testcases do all work now.
+
+Yay. Marking as fixed. :-)",1372298506,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,"(In reply to comment #1)
+> Do they work for you too?
+
+Sorry, yes the testcases do all work now.",1372225473,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,Could you check [[History of Delta Air Lines#1960s_and_1970s]]?,1372225448,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,"(In reply to comment #0)
+> Groups of consecutive images are alienated under certain circumstances. 
+> 
+> It might have something to do with the wikilinks in the image caption,
+> however
+> I really just have to throw you some testcases:
+> 
+> ---
+> (1) Works fine:
+> http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/
+> sandbox/VE2&oldid=561493135&veaction=edit
+> 
+> (2) Similar, but doesn't work:
+> http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/
+> sandbox/VE2&oldid=561493351&veaction=edit
+> 
+> (3) All three groups uneditable, even the group that is identical to (1)
+> above:
+> http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/
+> sandbox/VE2&oldid=561493252&veaction=edit
+> 
+> (4) One group fine, the other alienated:
+> http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/
+> sandbox/VE2&oldid=561493194&veaction=edit
+
+These now all work for me - we've updated Parsoid (and purged the cached versions to avoid corruption from old things), which is (I think) the cause of these issues. Do they work for you too?",1372221560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"http://it.wikipedia.org/wiki/Utente:Syrio/Bozzoli, we tried changing the author's name in ref.6 to ""abbé Paul Guérin"". VE allows editing it, but after clicking twice on Apply Changes, the former name is still displayed and the page can not be saved as the button does not work. (Also, it does not allow us to re-try immediately or to edit other references, you need to reload the page for that). So I did a dummy edit to plain text, and I was allowed to save then, but the result http://it.wikipedia.org/w/index.php?title=Utente%3ASyrio%2FBozzoli&diff=59659908&oldid=59651683 has nothing to do with poor abbé Guérin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372150800,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jgkllstpxv33sn72mt5f,task_description,resolved
+VisualEditor: VE won't let user save after editing a reference,"(In reply to comment #4)
+> You are right, it works now. Can this be due to people adding TemplateData to
+> that template?
+
+It's possible that TemplateData would mean that it was difficult to edit, yes; sorry. :-(
+
+> Since we're here, I attached the screenshot of what happens when
+> you try and edit it with Vector. You need to reach and click the light blue
+> bar in order to change something in that line. It works, though.
+
+Argh, yes, that's bug 49818 which I thought we had fixed; is this problem still happnening for you? :-(",1373417844,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"(Sorry, that was meant to be ""with Vector on Chrome"", it's ok on FF).",1373308926,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"You are right, it works now. Can this be due to people adding TemplateData to that template? Since we're here, I attached the screenshot of what happens when you try and edit it with Vector. You need to reach and click the light blue bar in order to change something in that line. It works, though.",1373308703,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"Created attachment 12788
+Reference editing window
+
+**Attached**: {F11670}",1373308463,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"[Sorry, can't check before tomorrow. Thanks.]",1373229247,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"[Sorry for being so late in replying to this bug!]
+
+Can this still be reproduced? If so, in what browser? I can edit the reference fine in Firefox and Chrome.
+
+(When you edit a reference, VisualEditor goes off and asks for the reference list to be re-created; temporarily, while that is happening, the original form remains shown in the reference list. However, this behaviour should be very quick, and should not prevent the user from editing.)",1373162537,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"Screenshot
+
+Image dialog shows thumbnails twice, see screenshots.
+
+Maybe 1 from local wiki and 1 from Commons, which are most of the times identical?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11660}",1372146180,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_description,resolved
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),This was fixed and deployed on Thursday.,1373763691,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"Change 73190 merged by jenkins-bot:
+Normalize image titles in cache to prevent duplicates.
+
+https://gerrit.wikimedia.org/r/73190",1373578658,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"Change 73190 had a related patch set uploaded by Robmoen:
+Normalize image titles in cache to prevent duplicates.
+
+https://gerrit.wikimedia.org/r/73190",1373562735,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),^^ You are correct.  this is happening because we are getting results from both namespaces.  File and Fichier in this case.,1373499189,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"(In reply to comment #2)
+> I can't reproduce this in Forefix 21.
+
+Oh, sorry, I see you were on frwiki. This doesn't happen on enwiki or mediawikiwiki, but I can reproduce it on frwiki and dewiki.
+
+Perhaps VE doesn't know about localised names for the ""File"" namespace. That's just a guess.",1372153753,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),I can't reproduce this in Forefix 21.,1372153025,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"Created attachment 12632
+Screenshot
+
+**Attached**: {F11661}",1372146249,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,"**Author:** `brassratgirl`
+
+**Description:**
+See this diff: 
+https://en.wikipedia.org/w/index.php?title=Uganda&diff=561452947&oldid=560332103
+
+adding a sentence to the lede section saved properly, but also had unwanted behavior of cutting off the first letter of the first word of a random paragraph in a later section (removed 'l' from ""Lake Kyoga"" under 'geography'). 
+
+Firefox 21.0 on Ubuntu 12.04.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372128420,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z4n2utsm2obyfevr5eud,task_description,resolved
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,I believe we have now fixed this; please re-open if it recurs.,1373056082,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,Can't reproduce in master yet.,1372175257,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,"**brassratgirl** wrote:
+
+Tried editing another, later section in the same article and got this: 
+https://en.wikipedia.org/w/index.php?title=Uganda&diff=561456536&oldid=561456189
+
+the changes I intended to make were made (added a link, copyediting) but spaces around template dates were added (more normalization) and the same initial letter (the 'l' of lake) and bracket from the same image file were removed. VisEd *really* doesn't like something about that paragraph!",1372130068,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,"(In reply to comment #1)
+> Also added some quotes to refnames
+
+That's ""just"" normalisation, which we can fix (by making sure that what we send Parsoid is exactly the same, so it leaves it alone); see bug 50071.
+
+> and removed a bracket from an image link later on.
+
+Yeah, this is very not good, and really hard to understand how it happens. Roan, thoughts?",1372129295,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,"**brassratgirl** wrote:
+
+Also added some quotes to refnames and removed a bracket from an image link later on.",1372128699,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Indentation toolbar buttons should not be enabled by default,"They're currently enabled on page load. Even when dismissing the notice and clicking around in the first paragraph it stays.
+
+It finally disables itself after a node change (e.g. click the second paragraph and then back).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44083",1372115880,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_description,resolved
+VisualEditor: Indentation toolbar buttons should not be enabled by default,This has been fixed and will be deployed very soon.,1372381096,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_subcomment,NA
+VisualEditor: Indentation toolbar buttons should not be enabled by default,"Change 70936 merged by jenkins-bot:
+Init surface after toolbar is setup vs. before.
+
+https://gerrit.wikimedia.org/r/70936",1372375419,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_subcomment,NA
+VisualEditor: Indentation toolbar buttons should not be enabled by default,"Change 70936 had a related patch set uploaded by Robmoen:
+Init surface after toolbar is setup vs. before.
+
+https://gerrit.wikimedia.org/r/70936",1372375072,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_subcomment,NA
+VisualEditor: Indentation toolbar buttons should not be enabled by default,"From conversation earlier today:
+
+It may be possible to hack the button to be disabled by default, but that would introduce the opposite bug where the indention tool would be disabled instead of enabled in a document that starts with a list, requiring the user to move out of the list and back in to be able to indent.
+
+Basically we should make sure that our hooks that make the button enabled/disabled on node focus change also trigger when initially focussing the first node in the document (instead of only from the second node focus onwards).",1372143779,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_subcomment,NA
+VisualEditor: Doing anything in a slug after an internal node throws an error,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372109460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tbvrdwvxvbqqobem3szn,task_description,resolved
+VisualEditor: Doing anything in a slug after an internal node throws an error,This should now be fixed.,1372113370,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tbvrdwvxvbqqobem3szn,task_subcomment,NA
+VisualEditor: Doing anything in a slug after an internal node throws an error,Related URL: https://gerrit.wikimedia.org/r/70333 (Gerrit Change I3818ebe9816e7d781233f087b15694bf7ba12965),1372112447,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tbvrdwvxvbqqobem3szn,task_subcomment,NA
+VisualEditor: Doing anything in a slug after an internal node throws an error,This is caused by CE placing a slug after internal nodes.  Fix in progress.,1372112372,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-tbvrdwvxvbqqobem3szn,task_subcomment,NA
+VisualEditor: Doing anything in a slug after an internal node throws an error,"Stack error:
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 73 ve.ce.Document.js:187
+ve.ce.Document.getNodeAndOffset ve.ce.Document.js:187
+ve.ce.Surface.showSelection ve.ce.Surface.js:1289
+ve.ce.Surface.onChange ve.ce.Surface.js:739
+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.MWReferenceDialog.onClose ve.ui.MWReferenceDialog.js:197
+ve.ui.Window.close ve.ui.Window.js:332
+(anonymous function) ve.ui.Dialog.js:118
+proxy",1372109556,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-tbvrdwvxvbqqobem3szn,task_subcomment,NA
+VisualEditor: HTML comment not removed from user pasting (? from external source),"https://en.wikipedia.org/w/index.php?title=Richard_Ned_Lebow&diff=561410032&oldid=545013166
+
+Perhaps unrelated to VisualEditor?
+
+<!-- /* Font Definitions */@font-face	{font-family:""Courier New"";	panose-1:2 7 3 9 2 2 5 2 4 4;	mso-font-charset:0;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:-536859905 -1073711037 9 0 511 0;}@font-face	{font-family:Times;	panose-1:2 0 5 0 0 0 0 0 0 0;	mso-font-charset:0;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:3 0 0 0 1 0;}@font-face	{font-family:Wingdings;	panose-1:5 0 0 0 0 0 0 0 0 0;	mso-font-charset:2;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:0 268435456 0 0 -2147483648 0;}@font-face	{font-family:""ＭＳ 明朝"";	mso-font-charset:78;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:-536870145 1791491579 18 0 131231 0;}@font-face	{font-family:""Cambria Math"";	panose-1:2 4 5 3 5 4 6 3 2 4;	mso-font-charset:0;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:-536870145 1107305727 0 0 415 0;} /* Style Definitions */p.MsoNormal, li.MsoNormal, div.MsoNormal	{mso-style-unhide:no;	mso-style-qformat:yes;	mso-style-parent:"""";	margin:0in;	margin-bottom:.0001pt;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph	{mso-style-priority:34;	mso-style-unhide:no;	mso-style-qformat:yes;	margin-top:0in;	margin-right:0in;	margin-bottom:0in;	margin-left:.5in;	margin-bottom:.0001pt;	mso-add-space:auto;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst	{mso-style-priority:34;	mso-style-unhide:no;	mso-style-qformat:yes;	mso-style-type:export-only;	margin-top:0in;	margin-right:0in;	margin-bottom:0in;	margin-left:.5in;	margin-bottom:.0001pt;	mso-add-space:auto;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle	{mso-style-priority:34;	mso-style-unhide:no;	mso-style-qformat:yes;	mso-style-type:export-only;	margin-top:0in;	margin-right:0in;	margin-bottom:0in;	margin-left:.5in;	margin-bottom:.0001pt;	mso-add-space:auto;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast	{mso-style-priority:34;	mso-style-unhide:no;	mso-style-qformat:yes;	mso-style-type:export-only;	margin-top:0in;	margin-right:0in;	margin-bottom:0in;	margin-left:.5in;	margin-bottom:.0001pt;	mso-add-space:auto;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}.MsoChpDefault	{mso-style-type:export-only;	mso-default-props:yes;	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}@page WordSection1	{size:8.5in 11.0in;	margin:1.0in 1.25in 1.0in 1.25in;	mso-header-margin:.5in;	mso-footer-margin:.5in;	mso-paper-source:0;}div.WordSection1	{page:WordSection1;} /* List Definitions */@list l0	{mso-list-id:85738127;	mso-list-type:hybrid;	mso-list-template-ids:1894403420 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}@list l0:level1	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Symbol;}@list l0:level2	{mso-level-number-format:bullet;	mso-level-text:o;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:""Courier New"";	mso-bidi-font-family:""Times New Roman"";}@list l0:level3	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Wingdings;}@list l0:level4	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Symbol;}@list l0:level5	{mso-level-number-format:bullet;	mso-level-text:o;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:""Courier New"";	mso-bidi-font-family:""Times New Roman"";}@list l0:level6	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Wingdings;}@list l0:level7	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Symbol;}@list l0:level8	{mso-level-number-format:bullet;	mso-level-text:o;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:""Courier New"";	mso-bidi-font-family:""Times New Roman"";}@list l0:level9	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Wingdings;}ol	{margin-bottom:0in;}ul	{margin-bottom:0in;}-->
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372105380,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-sdadbdxs63vkmq4vqjom,task_description,resolved
+VisualEditor: HTML comment not removed from user pasting (? from external source),"Change 86664 merged by jenkins-bot:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1385500071,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdadbdxs63vkmq4vqjom,task_subcomment,NA
+VisualEditor: HTML comment not removed from user pasting (? from external source),Rich paste will strip all metadata and so should solve this issue.,1381157634,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sdadbdxs63vkmq4vqjom,task_subcomment,NA
+VisualEditor: HTML comment not removed from user pasting (? from external source),"Change 86664 had a related patch set uploaded by Esanders:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1381157515,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdadbdxs63vkmq4vqjom,task_subcomment,NA
+VisualEditor: HTML comment not removed from user pasting (? from external source),"Bizarre indeed; presumably this is from a copy-and-paste and the ""give me only the plain text"" request to the browser is being ignored?",1372112566,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sdadbdxs63vkmq4vqjom,task_subcomment,NA
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text","* Go here http://en.wikipedia.org/w/index.php?title=User:ESanders_(WMF)/Sandbox&oldid=561403721&veaction=edit
+* Select from the end of the image to inside the link
+* Observe you now have a link inspector positioned over the image.
+Bonus:
+* Use the inspector to edit the link
+* Review your changes, the image has been killed, and the link as gone a bit crazy
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372102800,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-isqwpxpplzad6mrvzuhz,task_description,resolved
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text",Fixed. Will go out in next push.,1377195359,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-isqwpxpplzad6mrvzuhz,task_subcomment,NA
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text","Change 79919 merged by jenkins-bot:
+getAnnotationsFromRange should only ignore non-content data
+
+https://gerrit.wikimedia.org/r/79919",1377195128,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-isqwpxpplzad6mrvzuhz,task_subcomment,NA
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text",'Bonus' section has been filed here: https://bugzilla.wikimedia.org/show_bug.cgi?id=53151,1377090118,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-isqwpxpplzad6mrvzuhz,task_subcomment,NA
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text","Change 79919 had a related patch set uploaded by Esanders:
+getAnnotationsFromRange should only ingnore non-content data
+
+https://gerrit.wikimedia.org/r/79919",1376944734,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-isqwpxpplzad6mrvzuhz,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"Screenshot of the problem in the serialization
+
+I think this is caused by Parsoid trying to preserver/re-add whitespace when round-tripping.
+
+Steps to reproduce issue:
+* Create a page like the default MediaWiki main page:
+
+<<<MW
+'''MediaWiki has been successfully installed.'''
+
+Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki sandbox software. 12
+
+== Getting started ==
+* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
+* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
+* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
+* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]
+MW;
+
+* Edit it with VisualEditor
+* Put the cursor before ""MediaWiki release mailing list"" and select back until before the first character of the heading ""Getting started"".
+* Press backspace. You're now left with 2 of 4 items in the list and an empty heading.
+* Again, out the cursor before ""MediaWiki release mailing list"" and delete until you're behind ""software. 12"". You're now left with ""MediaWiki release mailing list"" in the paragraph and a list with 1 item.
+* Save page -> Review changes (Screenshot attached)
+
+It inserts a lot of new lines.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11588}",1372101840,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_description,resolved
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,Please reopen if this an issue in Parsoid.,1372370405,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"There was a typo.  It should read:  "".... where there are *NONE* ....""",1372111668,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"This seems to be a bug in the diff interface in mediawiki.  There are no extra newlines in the wikitext source as indicated by the diff.  The diff incorrectly signals newlines where there are now.
+
+Steps to reproduce:
+
+* Do everything as Krinkle says
+* Actually save the page.
+* Look at the new wikitext source and look at what the diff tells you.
+
+I am leaving this bug open so others can verify independently.",1372111612,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"(In reply to comment #2)
+> Krinkle: Could you provide a dump of VE's input and output DOM?
+
+Given the steps to reproduce the bug from comment 0, I get the following:
+
+> doc = ve.instances[0].model.documentModel;
+> d = ve.createDocumentFromHtml( ve.init.mw.targets[0].originalHtml );
+> d2 = ve.dm.converter.getDomFromData( doc.getFullData(), doc.getStore(), doc.getInternalList() );
+> copy( d.body.innerHTML );
+
+<p data-parsoid=""{&quot;dsr&quot;:[0,48,0,0]}""><b data-parsoid=""{&quot;dsr&quot;:[0,48,3,3]}"">MediaWiki has been successfully installed.</b></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[50,171,0,0]}"">Consult the <a rel=""mw:ExtLink"" href=""//meta.wikimedia.org/wiki/Help:Contents"" data-parsoid=""{&quot;targetOff&quot;:103,&quot;dsr&quot;:[62,116,41,1]}"">User's Guide</a> for information on using the wiki sandbox software. 12</p>
+
+<h2 data-parsoid=""{&quot;dsr&quot;:[173,194,2,2]}""> Getting started </h2>
+<ul data-parsoid=""{&quot;dsr&quot;:[195,535,0,0]}""><li data-parsoid=""{&quot;dsr&quot;:[195,281,1,0]}""> <a rel=""mw:ExtLink"" href=""//www.mediawiki.org/wiki/Manual:Configuration_settings"" data-parsoid=""{&quot;targetOff&quot;:253,&quot;dsr&quot;:[197,281,56,1]}"">Configuration settings list</a></li>
+<li data-parsoid=""{&quot;dsr&quot;:[282,335,1,0]}""> <a rel=""mw:ExtLink"" href=""//www.mediawiki.org/wiki/Manual:FAQ"" data-parsoid=""{&quot;targetOff&quot;:321,&quot;dsr&quot;:[284,335,37,1]}"">MediaWiki FAQ</a></li>
+<li data-parsoid=""{&quot;dsr&quot;:[336,434,1,0]}""> <a rel=""mw:ExtLink"" href=""https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce"" data-parsoid=""{&quot;targetOff&quot;:403,&quot;dsr&quot;:[338,434,65,1]}"">MediaWiki release mailing list</a></li>
+<li data-parsoid=""{&quot;dsr&quot;:[435,535,1,0]}""> <a rel=""mw:ExtLink"" href=""//www.mediawiki.org/wiki/Localisation#Translation_resources"" data-parsoid=""{&quot;targetOff&quot;:498,&quot;dsr&quot;:[437,535,61,1]}"">Localise MediaWiki for your language</a></li></ul>
+
+> copy( d2.body.innerHTML );
+
+<p data-parsoid=""{&quot;dsr&quot;:[0,48,0,0]}""><b data-parsoid=""{&quot;dsr&quot;:[0,48,3,3]}"">MediaWiki has been successfully installed.</b></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[50,171,0,0]}"">Consult the <a href=""//meta.wikimedia.org/wiki/Help:Contents"" rel=""mw:ExtLink"" data-parsoid=""{&quot;targetOff&quot;:103,&quot;dsr&quot;:[62,116,41,1]}"">User's Guide</a> for information on using the wiki sandbox software. 12<a href=""https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce"" rel=""mw:ExtLink"" data-parsoid=""{&quot;targetOff&quot;:403,&quot;dsr&quot;:[338,434,65,1]}"">MediaWiki release mailing list</a></p><ul data-parsoid=""{&quot;dsr&quot;:[195,535,0,0]}""><li data-parsoid=""{&quot;dsr&quot;:[435,535,1,0]}""> <a href=""//www.mediawiki.org/wiki/Localisation#Translation_resources"" rel=""mw:ExtLink"" data-parsoid=""{&quot;targetOff&quot;:498,&quot;dsr&quot;:[437,535,61,1]}"">Localise MediaWiki for your language</a></li></ul>",1372108572,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,Krinkle: Could you provide a dump of VE's input and output DOM?,1372104921,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"Subbu, could this be caused by e90e40c26cd8?",1372103979,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+VisualEditor: First character after a </pre> is lost on round-trip,"I edited a large page on meta (1.22wmf7) in VE. All seemed fine but review showed VE had removed the first character following several closing </pre> tags. It also removed a few characters within a <source> tag.
+
+Here's the diff showing the removal, it's self-explanatory.  <https://www.mediawiki.org/w/index.php?title=Extension%3AEventLogging%2FGuide&diff=716359&oldid=704840>.  I will restore the characters by hand.
+I'm using Firefox 21.0 on Kubuntu 13.04.
+
+I tried editing the same document again and this time VE removed more characters from the source tag, added a space after a <pre>. Hmm. I'm setting to critical as it's recoverable data loss, but maybe it's intermittent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372098360,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ay5qiidktmoux2bli72a,task_description,resolved
+VisualEditor: First character after a </pre> is lost on round-trip,"Here is another example:
+https://www.mediawiki.org/w/index.php?title=Gerrit/Tutorial&diff=717045",1372510492,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ay5qiidktmoux2bli72a,task_subcomment,NA
+VisualEditor: First character after a </pre> is lost on round-trip,"(In reply to comment #2)
+> Can't reproduce in master.
+
+Neither can I, in production or master. I'm going to close this as fixed, but please re-open if it recurs.",1372355490,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ay5qiidktmoux2bli72a,task_subcomment,NA
+VisualEditor: First character after a </pre> is lost on round-trip,"Can't reproduce in master.
+
+An issue I am seeing is code inside <source> and <syntaxhighligh> blocks are losing their linebreaks. Might want to file a bug if we aren't aware of that.
+
+Editing inside source is now bug 50224",1372250776,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ay5qiidktmoux2bli72a,task_subcomment,NA
+VisualEditor: First character after a </pre> is lost on round-trip,"Making this primarily about the first character after a </pre> getting lost on round-trip; I'm not sure how you were able to edit inside a <source> tag, though, so that needs exploring too if it recurs.",1372113996,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ay5qiidktmoux2bli72a,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"From http://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Problem_with_using_shift%2B
+
+""Hi. I have been using the visual editor for a while on ar Wikipedia, it is very nice and smooth for fast edits. However, I am facing a very strange problem when I need to add some Arabic diacritics known as tashkil; when I press shift+diacritic button (like x, e, or z) the letter I pressed starts to repeat itself endlessly, and it can only be stopped by refreshing the page and wasting the work I have did. Any thoughts?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50631",1372087860,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-pg6duwir2q65ub4iepr6,task_description,resolved
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"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!",1377202348,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"Change 80080 merged by jenkins-bot:
+Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",1377164920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"**aaddira** wrote:
+
+Thank you. I have tested all possible diacritics on Arabic Wikipedia and everything is working great. Good job!",1377037457,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"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",1377027676,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"I think this may be resolved by the following patch:
+https://gerrit.wikimedia.org/r/#/c/79451 . It fixes similar bugs in other scripts with similar properties.
+
+If it's still broken, is it possible to give a specific example of:
+
+1. A piece of Arabic text where VisualEditor fails
+2. The keystrokes required to enter the text
+3. The incorrect output observed in VisualEditor
+4. The OS, browser and input method used.
+
+Thanks!",1376936389,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"(In reply to comment #2)
+> Thanks James - first bug report.
+
+No worries. :-) Welcome to the party.",1372090765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,Thanks James - first bug report.,1372090521,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"Bumping priority, moving module, assigning, slight rewording; note that we can't fix things in the past (;-)), so setting to next week's deployment deadline.",1372090412,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: HTML comments being removed inside templates,"https://en.wikipedia.org/w/index.php?title=Jason_Bateman&curid=685922&diff=561337061&oldid=559944750
+
+https://en.wikipedia.org/w/index.php?title=David_Stewart_(photographer)&curid=24365669&diff=561336970&oldid=529664374
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372086120,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_description,resolved
+VisualEditor: HTML comments being removed inside templates,"Confirmed that this indeed now fixed, now that everyone's caches have rotated.",1373851510,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_subcomment,NA
+VisualEditor: HTML comments being removed inside templates,"comment 1 is an example that is not fixed by bug 50071, and im still seeing the problem occur.
+
+https://en.wikipedia.org/w/index.php?title=Republic_of_Texas&diff=562971813&oldid=562786837",1373029845,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_subcomment,NA
+VisualEditor: HTML comments being removed inside templates,"
+
+*** This bug has been marked as a duplicate of bug 50071 ***",1372113547,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_subcomment,NA
+VisualEditor: HTML comments being removed inside templates,https://en.wikipedia.org/w/index.php?title=Paul_Evans_(footballer_born_1973)&curid=15575267&diff=561390930&oldid=561390588,1372096563,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_subcomment,NA
+"VisualEditor: Templates' phantoms can overlap the toolbar, hindering saving/etc.","Screenshot
+
+See screenshot; this is still happening as of [timestamp of this bug]. The VE interprets a click on 'save page' to be an attempt to interact with the infobox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49059
+
+**Attached**: {F11515}",1372081680,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-zhyimecjptsrsi7gj65o,task_description,resolved
+"VisualEditor: Templates' phantoms can overlap the toolbar, hindering saving/etc.","**orbit** wrote:
+
+This is fixed now in master.",1372205712,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zhyimecjptsrsi7gj65o,task_subcomment,NA
+"VisualEditor: Templates' phantoms can overlap the toolbar, hindering saving/etc.","Created attachment 12625
+Screenshot of blue phantom overlapping save dialog using VisualEditor on the English Wikipedia, 2013-06-24
+
+Confirmed.
+
+**Attached**: {F11517}",1372100654,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-zhyimecjptsrsi7gj65o,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,"Compare the references section of https://en.wikipedia.org/wiki/A_Slight_at_the_Opera in read and edit mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52371",1372080180,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gww3sadaua5hd4aa5mxy,task_description,resolved
+VisualEditor: Reflist sometimes not fully being populated,"No, this bug was fixed; I think that that's a different issue. Splitting.",1375381775,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,%%%*** Bug 52371 has been marked as a duplicate of this bug. ***%%%,1375381498,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,Reopening; see bug 52371 for an example of this still happening.,1375381485,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,This was fixed in the re-working of references last week; marking as fixed.,1375381274,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,"I can't reproduce this using the example above now, even looking at the version that was live when the comment was left. I see four references in both read and edit modes.",1375340495,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Lag when selecting complex templates (especially in big pages),"(from bug 49922 comment 1)
+
+VE is slow at selecting templates and transclusions in big pages.
+
+For example: [[World War II]]:
+
+ - attempt to select infobox by clicking on it: takes ~3 seconds in 
+   Firefox 21 and Chrome 27, with no visual indication that anything
+   is happening during the wait
+
+ - attempt to select the reflist by clicking on it: just hangs in Firefox
+   and Chrome, never actually seems to happen
+
+This either needs to be sped up, or fail more gracefully.
+
+In IE10, this is not such a problem \o/ - lag is actually less, and the reflist can be selected (takes about 22 seconds).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372048320,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_description,resolved
+VisualEditor: Lag when selecting complex templates (especially in big pages),"This is an old report that I think is now closable (but performance is of course an on-going concern).
+
+For these particular concerns, we've recently fixed a number of performance issues germane to these:
+
+* Selection of the template, and opening the dialog, takes much less than a
+  second now for me (I'd call it instant, roughly).
+* Loading the second reflist is much quicker too (the first one was already near-instant).
+
+(Note that these fixes should hit production later today.)
+
+Consequently, I'm marking this as ""FIXED"", though there's always going to be more to do.",1406824618,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_subcomment,NA
+VisualEditor: Lag when selecting complex templates (especially in big pages),"Created attachment 13765
+beyond the selected reflist
+
+**Attached**: {F11475}",1384199300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_subcomment,NA
+VisualEditor: Lag when selecting complex templates (especially in big pages),"Created attachment 13764
+Above the reflist
+
+**Attached**: {F11474}",1384199261,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_subcomment,NA
+VisualEditor: Lag when selecting complex templates (especially in big pages),"Experienced the lag in selecting both the info box and reflist on that page in chrome Version 26.0.1410.65 and firefox 20 (MAC OS X version 10.8.5)
+
+However, did not experience the hang while selecting the reflist in either of the browsers.
+
+Also,while selecting the reflist , the blue selection box progresses beyond the reflist selected in both sides.
+
+See the screenshots attached.",1384199216,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_subcomment,NA
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed","See the unexpected changes at https://en.wikipedia.org/w/index.php?title=Thomson_Airways&diff=561270595&oldid=561268927
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372037280,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-4gxgm32h47ktjmsohfhi,task_description,resolved
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed",Fixed and will go out in about an hour.,1372089793,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4gxgm32h47ktjmsohfhi,task_subcomment,NA
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed",Related URL: https://gerrit.wikimedia.org/r/70133 (Gerrit Change Ib13bb206c49b1f5b186e40632a5c109def0f042e),1372069539,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4gxgm32h47ktjmsohfhi,task_subcomment,NA
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed",Data model issue.,1372042733,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4gxgm32h47ktjmsohfhi,task_subcomment,NA
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed","When a page contains two identical templates right next to each other, VE removes one of them. 
+
+Try editing [[User:This, that and the other/sandbox/VE5]] in VE, for example.",1372039711,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-4gxgm32h47ktjmsohfhi,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","Screenshot
+
+See screenshot. What am I meant to be paying attention to?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11451}",1372035900,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-wnsljgens4avgolp5rah,task_description,resolved
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack",This has indeed be fixed by the above on-wiki change; closing.,1373037205,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","(In reply to comment #9)
+> .ve-init-mw-viewPageTarget-toolbar-editNotices-notice .editnotice-redlink {
+> display: none !important; }
+> 
+> I'd recommend the community adds this to [[MediaWiki:Group-sysop.css]]
+
+Actually, add it to [[MediaWiki:Common.css]] below "".sysop-show { display: none"" because we want it to apply to non-sysops who made this visible in their user css as well. It won't affect anything else.",1372814858,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","I agree that it isn't obvious whether the community does or doesn't want this information on the edit page. However I also want to emphasise that this is hidden by default, and thanks to our logic that strips out fake notices that have no visible content, they are hidden for the vast majority of users.
+
+If this ""Page notice"" redlink is visible, it is because the user has styles in their state (either from [[MediaWiki:Group-sysop.css]] or their user stylesheet) that make "".editnotice-redlink"" or "".show-sysops"" visible (the element in the edit notice has both classes).
+
+So one could argue showing it is the right thing to do, for they want to see it. Why would they want to see it on the edit page but not in VisualEditor? Likely because they don't use it that much in the first place, but it is more intruding in VisualEditor because notices pop up from the editor.
+
+Anyway, to hide in visualeditor without hiding it else where, you can use the following line of CSS:
+
+.ve-init-mw-viewPageTarget-toolbar-editNotices-notice .editnotice-redlink { display: none !important; }
+
+I'd recommend the community adds this to [[MediaWiki:Group-sysop.css]] right below the rules for  "".show-sysop { display: block !important; }"" and the like.
+
+Note that we can't use ve-ui-toolbar, we can only use ""ve-init-mw-viewPageTarget-toolbar-editNotices-notice"" because the other elements aren't in the notice's element tree until *after* it is already in the VE DOM, and hiding it after that will merely make the link invisible, the notice container will still be there.",1372814249,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","(In reply to comment #6)
+> There isn't much we can do. If the community insists it is useful to have
+> placeholder edit notices when there is no editnotice that allows opt-in users
+> to create them from a red link, then this is exactly what they want, is it
+> not?
+> 
+> It shows that on EditPage as well (except in there, they are less visible as
+> actual notices but appear as part of the page).
+
+I disagree that the consensus that the enwiki community achieved for having this edit notice in wikitext editor (a consensus which I have disagreed for years, but there you go) transfers to consensus that they want it displaying in VisualEditor.
+
+As a quick hack, we could sniff for the edit notice having class=""editnotice-redlink"" on it and killing that notice from the array. It's horrible, but it will stop the problem until we fix it properly.",1372813340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","Last I checked, we're part of the community.",1372806658,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","I fixed most of these last year by supporting client-side ""hidden"" notices as non-existent through the hasVisibleText logic I wrote.
+
+These used to trigger a notice for all users, now it only triggers a notice for users that have css in their state that makes these red links visible (I think this is limited to MediaWiki:Group-sysop.css by default +  anyone else who likes to have it as well).
+
+There isn't much we can do. If the community insists it is useful to have placeholder edit notices when there is no editnotice that allows opt-in users to create them from a red link, then this is exactly what they want, is it not?
+
+It shows that on EditPage as well (except in there, they are less visible as actual notices but appear as part of the page).",1372801246,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","This really should be solved on en.wp, not in VE.",1372784144,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","I'd recommend prioritizing this very highly, it's a rather negative experience.",1372784020,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack",*** Bug 50531 has been marked as a duplicate of this bug. ***,1372727149,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","(In reply to comment #1)
+> (In reply to comment #0)
+> > Created attachment 12619 [details]
+> > Screenshot
+> > 
+> > See screenshot. What am I meant to be paying attention to?
+> 
+> That enwiki's community, in its wisdom, wants you to see that you can add a
+> page notice to every page, because you're +sysop. It doesn't appear for
+> non-sysops. If they want to commit to adding a class to it that we suppress
+> and reduce the count by one, we're happy to do that.
+
+Looking into this, it seems like we can use class=""editnotice-redlink"" to select and suppress these (including reducing the count by one). Handing to Timo to implement.
+
+**Attached**: {F11451}",1372172066,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","(In reply to comment #0)
+> Created attachment 12619 [details]
+> Screenshot
+> 
+> See screenshot. What am I meant to be paying attention to?
+
+That enwiki's community, in its wisdom, wants you to see that you can add a page notice to every page, because you're +sysop. It doesn't appear for non-sysops. If they want to commit to adding a class to it that we suppress and reduce the count by one, we're happy to do that.
+
+**Attached**: {F11451}",1372036133,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"Click after the line ""Saptaitey Chiranjeevinaha[citation needed]"" on https://en.wikipedia.org/wiki/Chiranjivi and BANG! And the text is gone.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372035720,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_description,resolved
+VisualEditor: Deletion into a DL from a block slug breaks,Fixed and will go out in an hour.,1374186072,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"Change 73952 merged by jenkins-bot:
+Handle backspace correctly when in a slugs
+
+https://gerrit.wikimedia.org/r/73952",1374186006,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"Change 73952 had a related patch set uploaded by Esanders:
+Handle backspace correctly when in a root slug
+
+https://gerrit.wikimedia.org/r/73952",1373975739,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"(In reply to comment #4)
+> Yes; you need to backspace over the DL from the block slug underneath it to
+> trigger.
+Yeah, that breaks it. For some reason handleDelete() tries to process *two* transactions: one successfully removes the entire <dl>, and the second tries to reinsert part of it but in the middle of a paragraph, presumably because it computed the wrong offset somehow (failing to adjust for the first transaction, maybe)?",1373658227,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,Yes; you need to backspace over the DL from the block slug underneath it to trigger.,1373502736,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"I can't reproduce this any more, can anyone else?",1373500564,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"DefinitionListNode shouldn't have getAnnotatedHtml, it's not inside a content branch. Did we screw up the DM such that a definition list ended up inside a paragraph?",1373499822,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"Yuck. Thrown error is:
+
+  Uncaught TypeError: Object #<VeCeDefinitionListNode> has no method 'getAnnotatedHtml' 
+
+Sounds like we didn't update the CE nodes for DLs.",1373163018,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,"See https://en.wikipedia.org/w/index.php?title=Beautiful_%28Mariah_Carey_song%29&diff=561243294&oldid=561242578
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372034760,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_description,resolved
+VisualEditor: HTML comments being removed inside references,Fixed and will be going out today.,1372210324,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,Related URL: https://gerrit.wikimedia.org/r/70469 (Gerrit Change I5a844e2e0655bc1db152b3805718324ca0bb04df),1372189640,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,*** Bug 50102 has been marked as a duplicate of this bug. ***,1372113547,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,"s/templates/references/ gah, sorry",1372108420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,Now appearing outside of templates; https://en.wikipedia.org/w/index.php?title=Lichens_%28musician%29&curid=16561703&diff=561390034&oldid=556766679,1372097824,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,"Roan, can you tell how we're dirtying the DOM such that Parsoid changes these at all?",1372036818,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,"See https://en.wikipedia.org/w/index.php?title=Riddler&diff=561149660&oldid=561096940
+
+The user reports they were nowhere near the infobox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50147
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50129",1372034400,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-67esakdk26er4uxasrc3,task_description,resolved
+VisualEditor: Nowiki-ing inside templates' parameters,This is now fixed and pushed live; sorry for the failure.,1372218685,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,*** Bug 50129 has been marked as a duplicate of this bug. ***,1372127871,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,Bug 50147 is the underlying problem in Parsoid; this bug is for fixing the dirty-DOMing that makes Parsoid trigger on the templates.,1372125589,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,"Other examples of nowiki insertion:
+
+http://en.wikipedia.org/w/index.php?title=Glenn_Greenwald&diff=561437483&oldid=561434741
+
+https://en.wikipedia.org/w/index.php?title=Schuylar_Oordt&diff=561438828&oldid=561406705",1372122627,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,"Roan, can you tell how we're dirtying the DOM such that Parsoid changes these at all?",1372036412,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"See https://en.wikipedia.org/w/index.php?title=Port_of_Hull&diff=561131671&oldid=561056099 - an attempt to enter a dash led to bolding vanishing. Not sure what's going on there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372033860,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-5cf6g72rzkft37gbritr,task_description,resolved
+Parsoid: selser drops last three apostrophes in '''''foo''''',https://gerrit.wikimedia.org/r/70768 (Gerrit Change I69bda7db141a3302cee6ece5af5ffdc57e748d89) | change APPROVED and MERGED [by jenkins-bot],1372291023,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',Related URL: https://gerrit.wikimedia.org/r/70768 (Gerrit Change I69bda7db141a3302cee6ece5af5ffdc57e748d89),1372287578,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',Related URL: https://gerrit.wikimedia.org/r/70768 (Gerrit Change I69bda7db141a3302cee6ece5af5ffdc57e748d89),1372287575,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',*** Bug 50258 has been marked as a duplicate of this bug. ***,1372284454,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"I can't reproduce the dirtying of the paragraph locally. If I make a null change, I get a null diff. If I change anything outside the bold+italic text, I get the bad diff.
+
+There are some dirtying issues with the code that was in production at the time, and still one left for which the fix is not deployed. That said, the minimal test case for this ( https://en.wikipedia.org/w/index.php?title=User:JohnCD/VEtest5&diff=next&oldid=561489465 ) does have a neighboring change.",1372218541,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"Here are actually two bugs:
+
+1) a VE bug that causes that paragraph to be dirtied
+2) a Parsoid bug that does not round-trip the bolding properly when using selser on bold elements
+
+Should I open a separate bug for VisualEditor, or do you have one for this already?",1372218203,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"This turns out to be a Parsoid bug:
+
+$ echo ""Foo '''''bar''''' baz"" > wt
+$ node parse.js --wt2html < wt | tee html
+<body><p data-parsoid='{""dsr"":[0,21,0,0]}'>Foo <i data-parsoid='{""dsr"":[4,14,2,2]}'><b data-parsoid='{""autoInsertedEnd"":true,""dsr"":[6,12,3,0]}'>bar</b></i> baz</p>
+</body>
+$ sed 's/baz/baaz/g' < html | tee html2
+<body><p data-parsoid='{""dsr"":[0,21,0,0]}'>Foo <i data-parsoid='{""dsr"":[4,14,2,2]}'><b data-parsoid='{""autoInsertedEnd"":true,""dsr"":[6,12,3,0]}'>bar</b></i> baaz</p>
+</body>
+$ node parse.js --html2wt --selser --oldtextfile wt --oldhtmlfile html < html2
+Foo '''''bar'' baaz
+
+Note that this doesn't break if there is no DOM change (i.e. if you pipe in html rather than html2 in the last step), and it also doesn't break if selser is disabled (i.e. if you omit --selser in the last step).",1372217410,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',We've seen this come up a number of times in our testing; I haven't investigated this one yet.,1372215813,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"Roan, can you tell how we're dirtying the DOM such that Parsoid changes these at all?",1372037116,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,"Currently we don't and cause major headaches for Parsoid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372028700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-spoxch2h3fjmkmu6pdme,task_description,resolved
+VisualEditor: Preserve ordering inside data-mw elements,"**ignatzmice.wiki** wrote:
+
+Apparently bug 50080 is a duplicate of this bug. However, that bug is still showing up: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=564509171#VE_totally_screwing_up",1373983343,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50108 has been marked as a duplicate of this bug. ***,1372101714,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50108 has been marked as a duplicate of this bug. ***,1372091701,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50106 has been marked as a duplicate of this bug. ***,1372091672,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50101 has been marked as a duplicate of this bug. ***,1372091521,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50099 has been marked as a duplicate of this bug. ***,1372091385,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50080 has been marked as a duplicate of this bug. ***,1372039230,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,Related URL: https://gerrit.wikimedia.org/r/70109 (Gerrit Change If0a5bcc67d3a172de0e8839cfda11efacfbf36ff),1372032121,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Metadata is not annotated,"Which causes this dirty diff:
+
+'''Foo<!--bar-->baz'''
+
+=>
+
+'''Foo'''<!--bar-->'''baz'''
+
+Of course annotating un-deletable metadata means if 'Foobaz' is erased you will be left with:
+
+'''<!--bar-->'''
+
+but that's less of a problem, and could be fixed by Parsoid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372009920,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rghqg5jcqisid4tfv5hr,task_description,resolved
+VisualEditor: Metadata is not annotated,Related URL: https://gerrit.wikimedia.org/r/70061 (Gerrit Change I40da3d5e8e987571195142304b1a853e177e36ff),1372010156,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rghqg5jcqisid4tfv5hr,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Screenshot
+
+See the screenshot; it appears in Monobook on enwiki and mediawiki.org as of the latest release. Kiiinda a problem.
+
+(the other interstitials there - review your changes/save page - are also shrunk).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11418}",1372005660,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_description,resolved
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write",Now fixed in master and will be deployed in a few minutes' time.,1374793868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Change 75814 merged by jenkins-bot:
+Fix font size for overlays in Monobook
+
+https://gerrit.wikimedia.org/r/75814",1374791926,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","I'd add that even on en.wp Monobook is used by many (at least if I read correctly  http://en.wikipedia.org/wiki/Wikipedia:Database_reports/User_preferences#Skin ).
+I had quite a few complaints about this now at it.wp, so it would really great if we managed to fix this ASAP. Thanks!
+
+(confl. by Gerrit: fixed now?)",1374708007,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Change 75814 had a related patch set uploaded by Esanders:
+Fix font size for overlays in Monobook
+
+https://gerrit.wikimedia.org/r/75814",1374707619,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","**mrkmg90** wrote:
+
+Review changes popup
+
+The review changes popup also has the same sizing issues...
+
+My eyes strain so hard trying to read the lines!
+
+**Attached**: {F11419}",1374501653,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","(In reply to comment #6)
+> Can I suggest that the title of this bug is changed to something more
+> meaningful?  If the words ""edit summary"" were included there would probably
+> be fewer duplicatates reported.
+
+Done.",1373807253,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Can I suggest that the title of this bug is changed to something more meaningful?  If the words ""edit summary"" were included there would probably be fewer duplicatates reported.",1373807116,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write",*** Bug 51315 has been marked as a duplicate of this bug. ***,1373805517,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write",*** Bug 51034 has been marked as a duplicate of this bug. ***,1373442406,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","You could add a CSS rule that uses the same technique for the dialog.
+
+Setting a simple relative font size (0.7em or something like that) makes it impossible to set the browser's default size to something sensible, as 0.7 * something sensible is usually too small. The non-linear nature of keyword scaling gives a good compromise between honoring a browser's font size and providing sane defaults despite 16px browser defaults.
+
+So if there are other JS-free solutions to this issue these days then that would be great.",1372103906,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","This is due to Monobook's ""interesting"" way of resetting the font-size to a consistent value cross-browser. It sets the <body> font-size to x-small, and then turn it back up to regular size with ""font-size: 127%;"" from their globalWrapper div.
+
+Due to this odd construct, any new elements attached to the <body> have an exceptionally small font size.
+
+Short of hardcoding a larger font-size for the overlay wrappers in Monobook or appending to #globalWrapper in monobook (which might cause others bugs due to not being in the <body> directly) - short of that this is a tough one to get right. Ideally core would fix this in Monobook by using the same font-size technique used by Vector.
+
+In Monobook's author's defence (Gabriel), the browsers we had to support when Monobook was being developed made it quite difficult to do right so this was probably the best way to do it at the time – but we no longer need to worry about IE5.5, IE4-for-Mac, Opera<7 etc.",1372027547,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Timo, what have you wrought?! ;-)",1372005848,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"You can't tab from the edit summary box to the ""Save page"" button, or the reference inspector to the ""Apply changes"" button, etc.
+
+This is important for accessibility. Currently, there is no way to confirm the action using only the keyboard.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50897",1371984240,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_description,resolved
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Hmm, yeah, this has regressed for Firefox. Yay for browser bugs. Will follow-up on bug 51918.",1400619419,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Enwiki, Firefox nightly on Mac. But does seem to work on office with Chrome.",1400616530,PHID-USER-n2ftvsjm34tosq65gpve,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"I can on enwiki, MediaWiki.org and Beta Labs – where are you having this issue?",1400616057,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"This appears to be broken again- can't tab to ""save page"" in the current release. Prefer to reopen this bug or file a new one?",1400615746,PHID-USER-n2ftvsjm34tosq65gpve,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,This bug is fixed. Will use bug 51918 to track changes to tab order instead.,1374880834,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,*** Bug 52080 has been marked as a duplicate of this bug. ***,1374818679,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"The current tab order is pants, and is not what was requested in comment 1 or comment 5.
+
+From the edit summary box, the tab order is now:
+1. the link ""minor edit"" beside the 'minor edit' checkbox.
+2. ""Save Page"" button
+3. ""Review your changes"" button
+Then three tabs for the links in the footer of this windows.
+
+Tabbing to the _link_ ""minor edit"" is a bug in the current implementation.
+
+Unless there is a good reason to do otherwise, the tab order should be the same as the source editor (muscle memory).  See also bug 51918 for a tab order request.",1374818669,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,Fixed and will get deployed in a few minutes.,1374677090,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Change 75594 merged by jenkins-bot:
+Make ButtonWidgets more accessible
+
+https://gerrit.wikimedia.org/r/75594",1374676838,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Patch above should fix original bug. Issue of tabbing from surface to 'Save page' is also partly fixed, but because of DOM order you have to shift+tab. If we want to switch these round, please open a new bug.",1374673879,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Change 75594 had a related patch set uploaded by Esanders:
+Makes ButtonWidgets more accessible
+
+https://gerrit.wikimedia.org/r/75594",1374673699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"There seem to be two distinct requests:
+
+* getting from the editing ""surface area"" to the edit summary input (with a tab key?)
+
+* getting from the edit summary input to the save page or review changes buttons (with a tab key)",1374631796,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"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.",1374631714,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,*** Bug 51918 has been marked as a duplicate of this bug. ***,1374630794,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,*** Bug 51913 has been marked as a duplicate of this bug. ***,1374624457,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"It's not really an enhancement, since it is preventing proper accessibility. But so long as it is looked at and fixed, that's what really matters :)",1373244830,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"attr( { role: 'button', tabIndex: 0 } ) and add return keypress events to all of them.
+
+Also dialogs should have role = dialog and buttons that pop up dialogs should have  aria-haspopup",1373229137,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371982260,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-batdg3q5jwk7z4eeddgg,task_description,declined
+VisualEditor: Right-click in IE10 causes deletion of the selected content,Totally conceivable that we fixed this in the past 15 months with the thousands of other changes (3683 since this point by my count). Marking as WORKSFORME.,1409959799,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,I can't reproduce this in IE10.,1409958482,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,"(In reply to This, that and the other (TTO) from comment #2)
+> Does not occur in IE11. Has an official decision been made on whether to
+> support IE <= 10?
+
+The ambition is to support IE9 and up; IE10 doesn't add much compared to IE9, but is probably a necessary stepping-stone. If it turns out to be too much work, we'll abandon efforts, but for now, yes, this is on the worklist.",1409441520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,Does not occur in IE11. Has an official decision been made on whether to support IE <= 10?,1409383011,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,(Does this also apply to the first comment here? :) ),1377104512,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Transclusion editor broken in IE10 (stack overflow),"In IE10, any attempt to open the transclusion editor leads to a stack overflow. 
+
+In the dev console I get this:
+
+--- 
+SCRIPT28: Out of stack space 
+load.php, line 46 character 700 [this location is different every time]
+
+SCRIPT5: Access is denied.
+load.php, line 305 character 273
+
+SCRIPT5: Access is denied.
+load.php, line 305 character 273
+
+SCRIPT5: Access is denied.
+load.php, line 305 character 273 
+[... ad infinitum]
+
+SCRIPT2343: Stack overflow at line: 46 [different every time]
+
+SCRIPT5: Access is denied.
+load.php, line 305 character 273
+---
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371982020,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-2go6ew7f46vsl6ngyy7w,task_description,resolved
+VisualEditor: Transclusion editor broken in IE10 (stack overflow),This doesn't happen in IE10 with master.,1409958003,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2go6ew7f46vsl6ngyy7w,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"1. Use Chrome 27 to edit [[Pancytopenia#External links]] in VE
+2. Try to cut the {{Commons category}} template (using Ctrl+X/Cmd+X or right click/Cut)
+
+The browser tab crashes.
+
+Seen on Windows and Mac.
+
+No idea how to find any debugging info about the crash.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371979920,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-6doqtsezbhohs5na7asr,task_description,resolved
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,Fixed in master; will be deployed on Thursday as part of the regular push.,1377632908,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"Change 81280 merged by jenkins-bot:
+Don't render <meta>/<link>/<style> tags in GeneratedContentNode
+
+https://gerrit.wikimedia.org/r/81280",1377628116,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"Change 81280 had a related patch set uploaded by Catrope:
+Don't render <meta>/<link>/<style> tags in GeneratedContentNode
+
+https://gerrit.wikimedia.org/r/81280",1377627560,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"Since <link> and <style> don't render in a useful way in the DOM (if they would ever be in wikitext, they'd be exported to VE as generated content or some other special thing that we can visualise and edit through an inspector or dialog)..
+
+It is fixed in Chromium 30.
+
+Updated summary to mention Chromium, not Chrome. This is likely affecting Opera 15 as well, for example.
+
+Since we don't want to 2 weeks for this to land in stable, and we can safely strip these out before we render them in CE in the first place, let's do that.",1375420043,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I think this is the patch that fixed it in Chrome 30:
+
+https://codereview.chromium.org/14995014
+https://trac.webkit.org/changeset/150402
+
+Which would mean that this is the upstream bug: 
+
+http://code.google.com/p/chromium/issues/detail?id=177470
+https://bugs.webkit.org/show_bug.cgi?id=116479",1375417683,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"(In reply to comment #13)
+> @Tim: Which chromium version is the stacktrace from?
+
+It's the Ubuntu package version 28.0.1500.71-0ubuntu1.12.04.1",1375395098,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I can still reproduce this on https://en.wikipedia.org/wiki/Pancytopenia?veaction=edit#External_links with Chrome 28 (stable channel).
+
+However when testing on Chrome 30 (dev channel), I can no longer reproduce this.
+
+Confirmed that removing the [
+<link rel=​""mw:​WikiLink/​Category"" href=​""./​Category:​Commons_category_without_a_link_on_Wikidata"" data-parsoid=​""{""stx"":​""simple"",""a"":​{""href"":​""./​Category:​Commons_category_without_a_link_on_Wikidata""}​,""sa"":​{""href"":​""Category:​Commons category without a link on Wikidata""}​}​"" about=​""#mwt7"">​
+] tag from the {{commonscat}} template before cutting, prevents the crash.
+
+
+@Tim: Which chromium version is the stacktrace from?
+
+Filed upstream: https://code.google.com/p/chromium/issues/detail?id=267059",1375386614,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I'll try to isolate this to produce a minimal test case, see how we can work around it in VE, and report it to the Chrome people. It's not acceptable for a browser to segfault even on invalid HTML.",1375373236,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,The node variable in frame 3 of my backtrace is indeed a <link> element.,1375349187,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"It seems that this bug has to do with link html tag.
+
+In both examples (Pancytopenia and Lumpectomy) if I delete <link> node (using debug tools) from inside (in second example it is not a direct child) of the node to cut then when I'm cutting it browser tab does not crash anymore.
+
+Based on the w3c documentation it seems to me that we are using link tag incorrectly - value of attribute ""rel"" should be one of the values listed here http://www.w3schools.com/tags/tag_link.asp but in our case it is ""mw:WikiLink/Category"".
+
+In case of templates in VE we are simply rendering HTMLDOM that we are getting from Parsoid, so fixing it in Parsoid (not using link tag incorrectly) should solve this problem. (I'm making some assumptions here - it should be verified first in some sort of isolation - jsfiddle.)
+
+For now as a quick fix we can strip all link nodes when we are rendering template in the VE.",1375342206,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I think this is probably the most important bug in VE at the moment, and it's sad to see no progress being made on it, so I got a backtrace from stock Chromium in Ubuntu 12.04:
+
+Program received signal SIGSEGV, Segmentation fault.
+[Switching to Thread 0x7fffcd87e700 (LWP 2767)]
+WebCore::AppendNodeCommand::AppendNodeCommand (this=0x14b6f1e5eea0, parent=..., node=...)
+    at third_party/WebKit/Source/core/editing/AppendNodeCommand.cpp:39
+39	third_party/WebKit/Source/core/editing/AppendNodeCommand.cpp: No such file or directory.
+(gdb) bt
+#0  WebCore::AppendNodeCommand::AppendNodeCommand (this=0x14b6f1e5eea0, parent=..., node=...)
+    at third_party/WebKit/Source/core/editing/AppendNodeCommand.cpp:39
+#1  0x000055555752af66 in create (node=..., parent=...)
+    at third_party/WebKit/Source/core/editing/AppendNodeCommand.h:37
+#2  WebCore::CompositeEditCommand::appendNode (this=0x14b6f44c0800, node=..., parent=...)
+    at third_party/WebKit/Source/core/editing/CompositeEditCommand.cpp:372
+#3  0x0000555557535512 in WebCore::DeleteSelectionCommand::makeStylingElementsDirectChildrenOfEditableRootToPreventStyleLoss (this=0x14b6f44c0800) at third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp:431
+#4  0x0000555557538582 in WebCore::DeleteSelectionCommand::handleGeneralDelete (this=0x14b6f44c0800)
+    at third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp:445
+#5  0x000055555753a2e5 in WebCore::DeleteSelectionCommand::doApply (this=0x14b6f44c0800)
+    at third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp:836
+#6  0x00005555575273d2 in WebCore::CompositeEditCommand::apply (this=0x14b6f44c0800)
+    at third_party/WebKit/Source/core/editing/CompositeEditCommand.cpp:202
+#7  0x000055555725c6f4 in deleteSelectionWithSmartDelete (smartDelete=false, this=<optimized out>)
+    at third_party/WebKit/Source/core/editing/Editor.cpp:340
+#8  WebCore::Editor::deleteSelectionWithSmartDelete (this=<optimized out>, smartDelete=false)
+    at third_party/WebKit/Source/core/editing/Editor.cpp:335
+#9  0x000055555726498a in WebCore::Editor::cut (this=0x14b6f2019180)
+    at third_party/WebKit/Source/core/editing/Editor.cpp:982
+#10 0x000055555726c08f in executeCut (frame=0x14b6f2d5cc00, source=<optimized out>)
+    at third_party/WebKit/Source/core/editing/EditorCommand.cpp:301
+#11 WebCore::executeCut (frame=0x14b6f2d5cc00, source=<optimized out>)
+    at third_party/WebKit/Source/core/editing/EditorCommand.cpp:297
+#12 0x00005555569cd7ee in WebKit::WebFrameImpl::executeCommand (this=0x14b6f2d7ca80, name=..., value=...)
+    at third_party/WebKit/Source/WebKit/chromium/src/WebFrameImpl.cpp:1243
+#13 0x00005555583d50e1 in content::RenderViewImpl::handleCurrentKeyboardEvent (this=<optimized out>)
+    at content/renderer/render_view_impl.cc:2201
+#14 0x0000555556a155ba in WebKit::EditorClientImpl::handleKeyboardEvent (this=0x14b6f2bd45a0, evt=0x14b6f379f700)
+    at third_party/WebKit/Source/WebKit/chromium/src/EditorClientImpl.cpp:643
+#15 0x00005555573f9d13 in WebCore::EventHandler::defaultKeyboardEventHandler (this=0x14b6f1464c80, 
+    event=0x14b6f379f700) at third_party/WebKit/Source/core/page/EventHandler.cpp:3121
+#16 0x0000555556acdad8 in WebCore::Node::defaultEventHandler (this=0x14b6f40364e0, event=0x14b6f379f700)
+    at third_party/WebKit/Source/core/dom/Node.cpp:2546
+---Type <return> to continue, or q <return> to quit---
+#17 0x0000555556b13822 in dispatchEventPostProcess (preDispatchEventHandlerResult=0x0, this=0x7fffcd87bdb0)
+    at third_party/WebKit/Source/core/dom/EventDispatcher.cpp:208
+#18 WebCore::EventDispatcher::dispatch (this=0x7fffcd87bdb0)
+    at third_party/WebKit/Source/core/dom/EventDispatcher.cpp:127
+#19 0x0000555556b1337e in WebCore::EventDispatcher::dispatchEvent (node=<optimized out>, mediator=...)
+    at third_party/WebKit/Source/core/dom/EventDispatcher.cpp:56
+#20 0x0000555556ace21b in WebCore::Node::dispatchEvent (this=0x14b6f40364e0, event=...)
+    at third_party/WebKit/Source/core/dom/Node.cpp:2426
+#21 0x0000555556abd15d in WebCore::EventTarget::dispatchEvent (this=0x14b6f40364e0, event=..., ec=<optimized out>)
+    at third_party/WebKit/Source/core/dom/EventTarget.cpp:148
+#22 0x00005555573fc181 in WebCore::EventHandler::keyEvent (this=0x14b6f1464c80, initialKeyEvent=...)
+    at third_party/WebKit/Source/core/page/EventHandler.cpp:3006
+#23 0x00005555569f3ccb in WebKit::WebViewImpl::handleKeyEvent (this=0x14b6f2bd4500, event=...)
+    at third_party/WebKit/Source/WebKit/chromium/src/WebViewImpl.cpp:987
+#24 0x00005555569f743b in WebKit::WebViewImpl::handleInputEvent (this=0x14b6f2bd4500, inputEvent=...)
+    at third_party/WebKit/Source/WebKit/chromium/src/WebViewImpl.cpp:2024
+#25 0x00005555583f92b3 in content::RenderWidget::OnHandleInputEvent (this=0x14b6f2b41000, 
+    input_event=0x14b6f38f7898, is_keyboard_shortcut=true) at content/renderer/render_widget.cc:756
+#26 0x00005555583f7c5e in DispatchToMethod<content::RenderWidget, void (content::RenderWidget::*)(WebKit::WebInputEvent const*, bool), WebKit::WebInputEvent const*, bool> (method=<optimized out>, obj=0x14b6f2b41000, arg=...)
+    at ./base/tuple.h:553
+#27 Dispatch<content::RenderWidget, content::RenderWidget, void (content::RenderWidget::*)(WebKit::WebInputEvent const*, bool)> (func=
+    (void (content::RenderWidget::*)(content::RenderWidget * const, const WebKit::WebInputEvent *, bool)) 0x5555583f90e0 <content::RenderWidget::OnHandleInputEvent(WebKit::WebInputEvent const*, bool)>, obj=0x14b6f2b41000, msg=
+    0x14b6f38d9f88, sender=<optimized out>) at ./content/common/input_messages.h:39
+#28 content::RenderWidget::OnMessageReceived (this=0x14b6f2b41000, message=...)
+    at content/renderer/render_widget.cc:311
+#29 0x00005555583ed784 in content::RenderViewImpl::OnMessageReceived (this=0x14b6f2b41000, message=...)
+    at content/renderer/render_view_impl.cc:1124
+#30 0x00005555566c8fa8 in content::MessageRouter::RouteMessage (this=<optimized out>, msg=...)
+    at content/common/message_router.cc:49
+#31 0x0000555556651a8b in OnMessageReceived (msg=..., this=0x14b6f14bcb88) at content/common/child_thread.cc:271
+#32 content::ChildThread::OnMessageReceived (this=0x14b6f14bcb88, msg=...) at content/common/child_thread.cc:236
+---Type <return> to continue, or q <return> to quit---
+#33 0x00005555566280ba in IPC::ChannelProxy::Context::OnDispatchMessage (this=0x14b6f14bde00, message=...)
+    at ipc/ipc_channel_proxy.cc:261
+#34 0x0000555556296fae in Run (this=0x7fffcd87d958) at ./base/callback.h:396
+#35 base::MessageLoop::RunTask (this=0x7fffcd87da50, pending_task=...) at base/message_loop.cc:484
+#36 0x000055555629a70b in base::MessageLoop::DeferOrRunPendingTask (this=0x7fffcd87da50, pending_task=...)
+    at base/message_loop.cc:496
+#37 0x000055555629ad13 in DoWork (this=<optimized out>) at base/message_loop.cc:688
+#38 base::MessageLoop::DoWork (this=0x7fffcd87da50) at base/message_loop.cc:667
+#39 0x000055555629b459 in base::MessagePumpDefault::Run (this=0x14b6f149b7e0, delegate=0x7fffcd87da50)
+    at base/message_pump_default.cc:29
+#40 0x00005555562aa202 in base::RunLoop::Run (this=0x7fffcd87da10) at base/run_loop.cc:45
+#41 0x0000555556296444 in base::MessageLoop::Run (this=<optimized out>) at base/message_loop.cc:321
+#42 0x00005555562bb330 in base::Thread::ThreadMain (this=0x14b6f14a45a0) at base/threading/thread.cc:197
+#43 0x00005555562b8001 in base::(anonymous namespace)::ThreadFunc (params=0x14b6f0a23650)
+    at base/threading/platform_thread_posix.cc:95
+#44 0x00007ffff3df9e9a in start_thread (arg=0x7fffcd87e700) at pthread_create.c:308
+#45 0x00007ffff1ef0ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
+#46 0x0000000000000000 in ?? ()
+(gdb) info locals
+No locals.
+(gdb) up
+#1  0x000055555752af66 in create (node=..., parent=...)
+    at third_party/WebKit/Source/core/editing/AppendNodeCommand.h:37
+37	third_party/WebKit/Source/core/editing/AppendNodeCommand.h: No such file or directory.
+(gdb) info locals
+No locals.
+(gdb) up
+#2  WebCore::CompositeEditCommand::appendNode (this=0x14b6f44c0800, node=..., parent=...)
+    at third_party/WebKit/Source/core/editing/CompositeEditCommand.cpp:372
+372	third_party/WebKit/Source/core/editing/CompositeEditCommand.cpp: No such file or directory.
+(gdb) info locals
+No locals.
+(gdb) up
+#3  0x0000555557535512 in WebCore::DeleteSelectionCommand::makeStylingElementsDirectChildrenOfEditableRootToPreventStyleLoss (this=0x14b6f44c0800) at third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp:431
+431	third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp: No such file or directory.
+(gdb) info locals
+rootEditableElement = {m_ptr = 0x0}
+nextNode = {m_ptr = 0x14b6f3107ee0}
+range = {m_ptr = 0x14b6f3e7f980}
+node = {m_ptr = 0x14b6f2d83180}",1375340841,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I experienced this on [[Narayana_Gosain_Temple]] which cutting '==References==\n{{reflist}}\n"", which may have also cut ""{{coord missing|Odisha}}"" which follows it.",1374545513,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"**ajc11123** wrote:
+
+I experience the same bug on Chrome 28.  Chrome crashes (displaying its characteristic ""Aw snap"" error page) when I try to cut certain templates, notably {{citation needed}}, {{who}}, and other in-line templates.  This does not happen with copying.  In addition, I could not reproduce the bug in my own userspace, only in article space.",1374110009,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"This also happens on Chrome 28 with reference blocks, looks like. Not sure if the same problem - try cutting the ref block on https://en.wikipedia.org/wiki/Lumpectomy",1374082463,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"It seems when I put a breakpoint in onCut and onCopy and step through slowly, it doesn't crash.",1374070133,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I don't think I manage to remove templates only with CTRL-X, but if I select some text along and then try to cut, Chrome's tab will crash as well.",1373664045,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"**bi.llybob** wrote:
+
+Also crashes when I try to cut multiple templates in Chrome. For example, if I select the two hatnotes at the top of https://en.wikipedia.org/wiki/Mauritius",1373171102,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"**bi.llybob** wrote:
+
+(Chrome 27, Windows) I can't seem to text-select the template, and don't see ""Cut"" on the right-click menu when the cursor is over the template. However, I do get an error tone when I select the template and press Ctrl-X.",1373171014,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"The content makes its way into the clipboard, but yes, I can reproduce.",1372006216,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+Parsoid: External links are double encoded,"Intended edit (ve-edit + fixup):
+
+https://www.mediawiki.org/w/index.php?title=Wikimedia_technical_search&diff=715707&oldid=715705
+
+-  [https://github.com/search?l=&q=wgWellFormedXml+%40wikimedia Search]
++  [https://github.com/search?l=&q=ResourceLoader+%40wikimedia Search]
+
+Actual edit saved by Parsoid/VisualEditor:
+
+
+https://www.mediawiki.org/w/index.php?title=Wikimedia_technical_search&diff=715706&oldid=715705
+
+-  [https://github.com/search?l=&q=wgWellFormedXml+%40wikimedia Search]
++  [https://github.com/search?l=&q=ResourceLoader+%2540wikimedia Search]
+
+
+Note how the % got encoded to %25.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371979620,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_description,resolved
+Parsoid: External links are double encoded,"We might later want to prettify the percent encoding. Basically decode everything but some vital percent-encoded values ([%? ], probably more). But for now this is fixed.",1372442702,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_subcomment,NA
+Parsoid: External links are double encoded,"Change 71082 merged by jenkins-bot:
+Bug 50042: Don't percent-encode modified external link hrefs
+
+https://gerrit.wikimedia.org/r/71082",1372442139,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_subcomment,NA
+Parsoid: External links are double encoded,"Change 71082 had a related patch set uploaded by GWicke:
+Bug 50042: Don't percent-encode modified external link hrefs
+
+https://gerrit.wikimedia.org/r/71082",1372441280,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_subcomment,NA
+Parsoid: External links are double encoded,"Looks like a Parsoid bug. Works fine when data-parsoid is present, but for new annotations URLs are encoded.
+
+<a rel=""mw:ExtLink"" href=""https://github.com/search?l=&amp;q=ResourceLoader+%40wikimedia"">Search</a>
+
+serialises to:
+
+[https://github.com/search?l=&q=ResourceLoader+%2540wikimedia Search]",1372252496,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_subcomment,NA
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"Screenshot
+
+I am unable to insert a media with a given file name from Commons.
+
+Neither
+
+File:Kölnisches Stadtmuseum - 125 x gekauft - geschenkt - gestiftet-1120.jpg
+
+nor
+
+Kölnisches Stadtmuseum - 125 x gekauft - geschenkt - gestiftet-1120.jpg
+
+is accepted (and any other file name)
+
+The ""insert media"" button is still inactive, see screenhot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11348}",1371909840,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-3nquleh2aykawirbt4st,task_description,declined
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"Unable to replicate this bug in CirrusSearch. As we're in the process of migrating from Lucene to CirrusSearch, I'm marking this bug as RESOLVED WONTFIX.",1392141824,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-3nquleh2aykawirbt4st,task_subcomment,NA
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"Searching without the dashes finds the document.  Looks like -XXX excludes all matches with XXX.  I'd advise removing the dashes, at least for now.",1376493859,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-3nquleh2aykawirbt4st,task_subcomment,NA
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"Still an issue. Trying to add [[Commons:File:Kölner Dom - Abbau südöstliches Gerüst Nordturm-2933.jpg]] to [[de:Traverse (mechanischer Träger)]].
+
+This is really annoying. Makes testing the VE impossible :-(",1374756848,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-3nquleh2aykawirbt4st,task_subcomment,NA
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"This is… exceptionally odd. VisualEditor is just using the built-in search system from the cluster, and as you can see your image doesn't come up with that (or several sub-strings of that) as the search string:
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=K%C3%B6lnisches%20Stadtmuseum%20-%20125%20x%20gekauft%20-%20geschenkt%20-%20gestiftet-1120.jpg&fulltext=Search&profile=images&redirs=1
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=K%C3%B6lnisches%20Stadtmuseum%20-%20125%20x%20gekauft%20-%20geschenkt%20-%20gestiftet-1120&fulltext=Search&profile=images&redirs=1
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=K%C3%B6lnisches%20Stadtmuseum%20-%20125%20x%20gekauft%20-%20geschenkt%20-%20gestiftet-1120&fulltext=Search&profile=images&redirs=1
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=geschenkt%20-%20gestiftet-1120&fulltext=Search&profile=images&redirs=1
+
+Interestingly, it does come up under:
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=gestiftet-1120&fulltext=Search&profile=images&redirs=1",1373156554,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3nquleh2aykawirbt4st,task_subcomment,NA
+"VisualEditor: Consecutive images align incorrectly in ""edit"" mode and cannot be modified","See, for example, https://en.wikipedia.org/wiki/Kaveri_River
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371896520,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-isttvrxbjpvgt5itwu5n,task_description,resolved
+"VisualEditor: Consecutive images align incorrectly in ""edit"" mode and cannot be modified","This is a very odd bug that appears to be due to an old mis-cached version of the Parsoid result (it was marking each of the images as about=""null""); we've flushed the caches, and it no longer appears AFAICT. Please re-open if it recurs.",1371972536,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-isttvrxbjpvgt5itwu5n,task_subcomment,NA
+VisualEditor: Thumbnailed images without descriptions get pipes added on edit,"Compare https://en.wikipedia.org/w/index.php?title=User:Edgepedia/sandbox3&diff=prev&oldid=560957268 to https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2Fsandbox3&diff=560957359&oldid=560957268
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371895500,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mnsdqy6zrnvlm2uqkhcw,task_description,resolved
+VisualEditor: Thumbnailed images without descriptions get pipes added on edit,"Fixed (I think) in gerrit 70357 which we've just deployed - if we get a repeat, please re-open.",1372124850,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mnsdqy6zrnvlm2uqkhcw,task_subcomment,NA
+VisualEditor: Thumbnailed images without descriptions get pipes added on edit,*** Bug 50116 has been marked as a duplicate of this bug. ***,1372096490,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mnsdqy6zrnvlm2uqkhcw,task_subcomment,NA
+VisualEditor: Thumbnailed images without descriptions get pipes added on edit,"Inez is already working on this, but I don't think we have a bug for it?",1372017842,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mnsdqy6zrnvlm2uqkhcw,task_subcomment,NA
+Images not displayed in latest VE deployment,"I hope this is a false alarm... but it seems to be real.
+
+Compare [[Locomotive]] (images visible - en is currently on 1.22wmf7) with [[testwiki:VisualEditor:Locomotive]] (no images - test is on 1.22wmf8).
+
+Seen on Firefox latest and Chrome latest.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1371887280,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ffl4fedejvxwcxttjfil,task_description,resolved
+Images not displayed in latest VE deployment,"Aha, I can now reproduce on that link - and looking at the HTML we get back from Parsoid, the first image comes back as
+
+<meta typeof=""mw:Placeholder"" data-parsoid='{""src"":""[[File:Net.jpg|thumb]]"",""optList"":[{""ck"":""thumbnail"",""ak"":""thumb""}],""dsr"":[0,22,null,null]}'>
+
+… and so VisualEditor dutifully doesn't display an image. Marking as a duplicate of the Parsoid bug, even though that is higher-numbered. Sorry about this. :-(
+
+*** This bug has been marked as a duplicate of bug 50035 ***",1372003922,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ffl4fedejvxwcxttjfil,task_subcomment,NA
+Images not displayed in latest VE deployment,"It seems to be mostly working again, although I couldn't see any images just a few hours ago. 
+
+I still can't see the first image on [[testwiki:Net]]. This just may be the Parsoid cache though.",1371970998,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ffl4fedejvxwcxttjfil,task_subcomment,NA
+Images not displayed in latest VE deployment,"(In reply to comment #1)
+> … with what browser …
+
+And, of course, you told me that. Sorry! :-( Can't reproduce on latest master or in latest push of wmf8.",1371970401,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ffl4fedejvxwcxttjfil,task_subcomment,NA
+Images not displayed in latest VE deployment,"I'm afraid I can't reproduce this - was this a transient issue, or do you still get it, and if so, with what browser, and are there any error messages on the console?",1371970022,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ffl4fedejvxwcxttjfil,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Currently scheduled for w/c 15 July. It's anticipated that this will not be possible for some wikis due to failings in VisualEditor and/or Parsoid; exact list to be determined closer to the time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51792
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33126
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33077
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52202",1371860160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_description,resolved
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","(In reply to comment #14)
+> (In reply to comment #13)
+> > The patch was committed and merged (but the notification bot incorrectly
+> > reset the status), so I'm setting this back to FIXED again as the original
+> > request that this bug report is about (see subject line) has been fulfilled.
+> 
+> I'm not sure the original request (""top 15"" Wikipedias) has been fulfilled,
+> but I'm also not sure that's still the goal. I'll leave this bug to James to
+> sort out.
+
+Re-titled for clarity. I feel that this is closed.",1375125139,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Change 76199 merged by jenkins-bot:
+Enable anonymous use of VisualEditor on es/fr/he/it/pl/ru/sv
+
+https://gerrit.wikimedia.org/r/76199",1375115804,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","(In reply to comment #13)
+> The patch was committed and merged (but the notification bot incorrectly
+> reset the status), so I'm setting this back to FIXED again as the original
+> request that this bug report is about (see subject line) has been fulfilled.
+
+I'm not sure the original request (""top 15"" Wikipedias) has been fulfilled, but I'm also not sure that's still the goal. I'll leave this bug to James to sort out.",1375115210,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","The patch was committed and merged (but the notification bot incorrectly reset the status), so I'm setting this back to FIXED again as the original request that this bug report is about (see subject line) has been fulfiled.
+Note that this is not any kind of statement refering to bug 52202, it's just to reflect the current situation. For the German Wikipedia deployment, please refer to bug 52202 instead. Thanks!",1375105856,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","**wikipedia** wrote:
+
+(In reply to comment #11)
+> They more than likely mean all the major bugs that cause issues with editing
+> (eg: dirty diffs, randomly inserting pawns to name two)
+
+Exactly, thank you for clarification.",1375089579,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","(In reply to comment #10)
+> (In reply to comment #8)
+> > 3) VE to be opt-in only until all bugs are fixed: 430 votes (!)
+> 
+> Personal opinion: I am not aware of a single software that is proven to be
+> completely bug-free. This is an impossible requirement that cannot be
+> fulfiled.
+
+They more than likely mean all the major bugs that cause issues with editing (eg: dirty diffs, randomly inserting pawns to name two)",1375085597,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","(In reply to comment #8)
+> 3) VE to be opt-in only until all bugs are fixed: 430 votes (!)
+
+Personal opinion: I am not aware of a single software that is proven to be completely bug-free. This is an impossible requirement that cannot be fulfiled.",1375085393,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)",bug 52202 has been created based on the German Wikipedia poll.,1375058081,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","**wikipedia** wrote:
+
+In the quick poll (see #7) the results at the moment are as following:
+
+1) enabeling VE as default for all users: 21 votes
+2) VE as default for logged-in users: 6 votes
+3) VE to be opt-in only until all bugs are fixed: 430 votes (!)
+4) enabeling VE under another link name (suggestion was ""Visual Editor (beta)"" instead of ""Bearbeiten"" (""edit"")): 31 votes
+
+According to this large majority of users who oppose defaulting VE by tomorrow, I hereby ask you to put VE back to opt-in for logged-in users until the most important bugs are fixed. Thank you.",1375045061,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","the German wikipedia just started a quick poll over the weekend to at least postpone this activation for anonymous users on monday:
+
+https://de.wikipedia.org/wiki/Wikipedia:Umfragen/VisualEditor_Opt-in
+
+the poll has currently also a option for the previous state where VE was Opt-in for users instead of Opt-out if this is still possible.
+
+It would be appreciated to take the outcome on monday into account and postpone this activation for dewiki if desired.",1374879438,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)",It's unclear whether the German Wikipedia wants this: <http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070807.html>.,1374874055,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Change 76199 had a related patch set uploaded by Jforrester:
+Enable anonymous use of VisualEditor on de/es/fr/he/it/pl/ru/sv
+
+https://gerrit.wikimedia.org/r/76199",1374873719,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)",This is now done.,1374685783,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Change 75543 merged by jenkins-bot:
+VisualEditor into beta on de/es/fr/he/it/pl/ru/svwiki for logged-in only
+
+https://gerrit.wikimedia.org/r/75543",1374685596,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Change 75543 had a related patch set uploaded by Jforrester:
+VisualEditor into beta on de/es/fr/he/it/pl/ru/svwiki
+
+https://gerrit.wikimedia.org/r/75543",1374631008,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","According to [[meta:Tech/News/2013/30]] the list is:
+German  (de), 
+Spanish (es), 
+French  (fr), 
+Hebrew  (he) - RTL, 
+Italian (it), 
+Dutch   (nl), 
+Polish  (pl), 
+Russian (ru) and 
+Swedish (sv).",1374489687,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Currently scheduled for w/c 1 July.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371860100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-algalgsjyyisq2anwhms,task_description,resolved
+Enable VisualEditor by default for all users of the English Wikipedia,This is now complete.,1373921229,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Change 73852 merged by jenkins-bot:
+Stop the prevention of anons getting VisualEditor for enwiki
+
+https://gerrit.wikimedia.org/r/73852",1373921102,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Change 73852 had a related patch set uploaded by Jforrester:
+Stop the prevention of anons getting VisualEditor for enwiki
+
+https://gerrit.wikimedia.org/r/73852",1373917817,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Now done for logged-in users. Will be done for the rest next week, assuming all is well.",1372715482,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Change 71261 merged by jenkins-bot:
+Enable VisualEditor for all logged-in users (but not anons) on enwiki
+
+https://gerrit.wikimedia.org/r/71261",1372714320,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Change 71261 had a related patch set uploaded by Jforrester:
+Enable VisualEditor for all logged-in users of the English Wikipedia
+
+https://gerrit.wikimedia.org/r/71261",1372561707,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,… with 'all users' (logged in and otherwise) for w/c 8 July.,1371860183,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor experimental mode on test* wikis as well as MW.org and Beta Labs,"After spending some time with VE in our various test environments, it would be convenient to have all features available in VE available in all of our test environments.  Right now it is possible to create citations in mediawiki.org but not in test2wiki, and VE in beta labs is not usable at all. 
+
+test2wiki gives us a production wiki where it is possible to make destructive or nonsense edits that are not welcome on mediawiki.org
+
+beta labs gives us an environment to test possibly risky merged changes that are not yet deployed
+
+Enabling all of VE features in all test environments would be useful for testing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49703",1371827040,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-kd62lmqw7ntjvcrqwhvx,task_description,resolved
+Enable VisualEditor experimental mode on test* wikis as well as MW.org and Beta Labs,"Change 70440 abandoned by Cmcmahon:
+Enable VE experimental mode on test2wiki per Bug 49963
+
+Reason:
+overtaken by history
+
+https://gerrit.wikimedia.org/r/70440",1372864721,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kd62lmqw7ntjvcrqwhvx,task_subcomment,NA
+Enable VisualEditor experimental mode on test* wikis as well as MW.org and Beta Labs,"VE seems to be working correctly now in beta labs, test2wiki, and mw.o
+
+Please re-open if you find otherwise.",1372377535,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-kd62lmqw7ntjvcrqwhvx,task_subcomment,NA
+Enable VisualEditor experimental mode on test* wikis as well as MW.org and Beta Labs,Related URL: https://gerrit.wikimedia.org/r/70440 (Gerrit Change I72b68e3e0db86eb5372cd303223ef8f81111271c),1372177710,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kd62lmqw7ntjvcrqwhvx,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"When editing a page which has an image with table data in its caption, the table is dropped (only its closing tab is kept). The rest of the caption is dropped as well.
+
+Test edit: https://hu.wikipedia.org/w/index.php?title=Vall%C3%A1s&diff=13696305&oldid=13696296
+
+You don't need to interact with the image in any way for this to happen, just edit the page, change anything and save.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://hu.wikipedia.org/wiki/Vall%C3%A1s?oldid=13696307
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61064",1371799080,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_description,resolved
+Images: wikitext tables inside image captions are lost,"Change 107172 merged by Subramanya Sastry:
+(Bug 49942) Tables can show up in image captions
+
+https://gerrit.wikimedia.org/r/107172",1389647113,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"Change 107172 had a related patch set uploaded by Subramanya Sastry:
+(Bug 49942) Tables can show up in captions
+
+https://gerrit.wikimedia.org/r/107172",1389631306,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934084,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"(In reply to comment #3)
+> (In reply to comment #2)
+> > If this image is not modified by the user it should still round-trip
+> > correctly,
+> > but on modification the table would be lost.
+> 
+> The table is lost even if the user does not interact with the image in any
+> way.
+>
+> See [[hu:Vallás]] - the image caption gets garbled as soon as you open the
+> article for editing.
+
+The corruption even if you don't touch it is a bug in VisualEditor related to munging the captions of images, which we're fixing today; sorry for that.",1372114586,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"(In reply to comment #2)
+> If this image is not modified by the user it should still round-trip
+> correctly,
+> but on modification the table would be lost.
+
+The table is lost even if the user does not interact with the image in any way. See [[hu:Vallás]] - the image caption gets garbled as soon as you open the article for editing.",1372114062,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"This is a tokenizer issue. The table is not tokenized as such, likely because syntax stops prevent a pipe from being matched.
+
+If this image is not modified by the user it should still round-trip correctly, but on modification the table would be lost.",1372105294,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"Horrible, relatively-rare case for Parsoid, is the use of wikitext tables inside image captions. Currently, the following wikitext:
+
+[Start]
+[[Image:Foo.jpg|thumb|200px|This is an example image thumbnail caption with a table
+
+{|
+! Foo !! Bar
+|-
+| Foo1 || Bar1
+|-
+| Foo2 || Bar2
+|}
+
+… and some more text.]]
+[End]
+
+… turns into the following output from Parsoid:
+
+[Start]
+<figure typeof=""mw:Image/Thumb"" data-parsoid=""…"">
+  <a href=""./File:Foo.jpg"" data-parsoid=""…"">
+    <img resource=""./File:Foo.jpg"" src=""http://upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/200px-Foo.jpg""
+      height=""131"" width=""200"" data-parsoid=""…"">
+  </a>
+  <figcaption class=""mw-figcaption"" data-parsoid=""…"">}
+
+… and some more text.
+  </figcaption>
+</figure>
+[End]
+
+… whereas nominally it should be (generated using an HTML table rather than a wikitext one, which seems to work fine without DOM diffs from VE end):
+
+[Start]
+<figure typeof=""mw:Image/Thumb"" data-parsoid=""…"">
+  <a href=""./File:Foo.jpg"" data-parsoid=""…"">
+    <img resource=""./File:Foo.jpg"" src=""http://upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/200px-Foo.jpg""
+      height=""131"" width=""200"" data-parsoid=""…"">
+  </a>
+  <figcaption class=""mw-figcaption"" data-parsoid=""…"">This is an example image thumbnail caption with a table
+
+    <table data-parsoid=""…"">
+      <tbody data-parsoid=""…"">
+        <tr data-parsoid=""…"">
+          <th data-parsoid=""…"">Foo</th>
+           <th data-parsoid=""…"">Bar</th>
+        </tr>
+        <tr data-parsoid=""…"">
+          <td data-parsoid=""…"">Foo1</td>
+          <td data-parsoid=""…"">Bar1</td>
+        </tr>
+        <tr data-parsoid=""…"">
+          <td data-parsoid=""…"">Foo2</td>
+          <td data-parsoid=""…"">Bar2</td>
+        </tr>
+      </tbody>
+    </table>
+
+… and some more text.
+  </figcaption>
+</figure>
+[End]",1371999975,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"1. In VE, highlight some text and open the link inspector
+2. Type some characters into the textbox, but quickly click out of the link inspector before the autocomplete dropdown appears
+
+The dropdown appears in the top-left corner of the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371798960,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_description,resolved
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,Not completely fixed; see bug 51415.,1373936995,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,Fixed and will go out soon.,1373413695,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"Change 72849 merged by jenkins-bot:
+Be sure lookupMenu input is focused before showing
+
+https://gerrit.wikimedia.org/r/72849",1373412773,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"(Cite bug 51077 comment #0)
+> Created attachment bug 51077 12810 [details]
+> 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).",1373411632,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,*** Bug 51077 has been marked as a duplicate of this bug. ***,1373411601,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"Change 72849 had a related patch set uploaded by Robmoen:
+Be sure lookupMenu input is focused before showing inputMenu.
+
+https://gerrit.wikimedia.org/r/72849",1373408156,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"(This happens particularly often on Opera for me, by the way. I haven't yet investigated the issue.)",1373331336,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"I am raising the severity on this, because it is not just a display bug, but also causes the intended link target to be ignored -- if the user confirms the link with enter, only the link title is used and the link target is quietly discarded.",1373331185,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,Confirmed. This also happens if you type too quickly and press enter.,1372893436,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"1. Go to [[mw:VisualEditor:TTO]] and edit in VE
+2. Double-click on a link in order to select it, or drag-select the whole link
+3. Type a new link text
+
+Only the first character you type remains linked, instead of the whole text you type.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371793260,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_description,resolved
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"With bug 51463 closed, this is now complete. Marking as fixed.",1374771607,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,See bug 51463,1374001912,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"(In reply to comment #5)
+> That's all well and good, but now if my document ends in a link (a common
+> case if I link the last thing I typed) I can't put plain text after it, which
+> is the very reason we disabled trailing annotations for links in the first
+> place...
+
+You can - you just need to press the ""clear annotations"" button, or press return to get a new context with no pre-annotations. However, yes, these suck for discoverability. I think not-extending-over-whitespace is the best solution, though it's fiddly and difficult to support.",1373992527,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"That's all well and good, but now if my document ends in a link (a common case if I link the last thing I typed) I can't put plain text after it, which is the very reason we disabled trailing annotations for links in the first place...",1373992120,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"Change 73902 merged by jenkins-bot:
+Continue links
+
+https://gerrit.wikimedia.org/r/73902",1373934716,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"Change 73902 had a related patch set uploaded by Catrope:
+Continue links
+
+https://gerrit.wikimedia.org/r/73902",1373931509,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"I agree that this behaviour is not great for users; we should reverse the decision to abandon ""pre-annotation"" (that is, if you're typing, we'll apply the same formatting as the character immediately before the one you've just typed in the same paragraph) for links.
+
+Our concern was that having links always extent would be more tiresome for editors, which I still agree with, and that extending but not over whitespace would be confusing, which I think is arguable, but the current behaviour is worse.",1373155708,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"A related problem is, when you change only the first character of a link, that first letter is no longer part of the link. For example, if you change [[edinburgh]] to [[Edinburgh]], it becomes E[[dinburgh]].",1372852867,PHID-USER-6hxjlzg5h4uzsyxbsm43,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+"VisualEditor: Clicking outside the ""Describe what you changed"" box locks it","Steps to replicate:
+
+(1)Click ""Edit"" and make some change
+(2)Click ""Save page"". The cursor is now blinking in the ""Describe what you changed"" box.
+(3)Click on another dialogue box, such as the WP search box. The cursor now blinks there.
+(4) Click back into ""Describe what you changed"". Bupkis.
+
+Chrome 27.0.1453.116, Firefox 21.0, Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371789780,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-h5i7cqn2z7j4vdb2bioo,task_description,resolved
+"VisualEditor: Clicking outside the ""Describe what you changed"" box locks it",Bug fixed,1372006698,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-h5i7cqn2z7j4vdb2bioo,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"See screenshot, which is of https://en.wikipedia.org/wiki/Craig_Short - Firefox 21.0, Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371789480,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-5pskpoilrrm4nns4zugy,task_description,resolved
+VisualEditor: Floated templates rendering oddly and overlapping text,Follow up:  https://en.wikipedia.org/wiki/Leo_Strauss?veaction=edit is still screwed up.,1384288678,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,Shall do.,1372613847,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"(In reply to comment #18)
+> Unless the patch hasn't been deployed yet, I guess.
+
+It hasn't. Deployed on Monday alongside the config change. Not sure if the example in comment 17 will be entirely fixed by it though - please check after release?",1372613728,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Unless the patch hasn't been deployed yet, I guess.",1372613000,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Crud
+
+It doesn't :(. See new screenshot.
+
+**Attached**: {F11120}",1372612962,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,*** Bug 50416 has been marked as a duplicate of this bug. ***,1372500786,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"The above patch fixes this bug, we believe. Marking as such.",1372463194,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Change 71109 merged by jenkins-bot:
+Stop floated transclusions floating out of themselves
+
+https://gerrit.wikimedia.org/r/71109",1372463162,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Change 71109 had a related patch set uploaded by Jforrester:
+Set renderHtmlAttributes to false, for both block and inline transclusions
+
+https://gerrit.wikimedia.org/r/71109",1372450916,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,*** Bug 50381 has been marked as a duplicate of this bug. ***,1372440083,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,+another example: https://en.wikipedia.org/wiki/Aranath?veaction=edit,1372440078,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"For some reason wrapper in which we put transclusions/templates gets HTML attributes of the transclusion/template carried over - including CSS classes - that should not happen, and wasn't happening in the past.
+
+I will investigate it, however adding Roan to this ticket, it seems like it is his area.",1372428523,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Screenshot
+
+This is likely a blocker for any beta rollout on Monday. I've attached a screenshot to show how bad it can get, and why :/.
+
+**Attached**: {F11119}",1372415006,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"(In reply to comment #4)
+> I thinks it depends on the skin: Monobook might be causing this.
+
+That's a different bug - created bug 50057.
+
+This is about CE's rendering of floated templates - I've attached some example screenshots to demonstrate.",1372005661,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12614
+what the template does look like when selected
+
+**Attached**: {F11118}",1372005619,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12613
+what the template does look like (once in VE)
+
+**Attached**: {F11117}",1372005597,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12612
+what the template should look like (read mode)
+
+**Attached**: {F11116}",1372005566,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,I thinks it depends on the skin: Monobook might be causing this.,1371986282,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"I don't think I can see your attachment, Oliver, but I think the bug may have to do with to these sshots, which both refer to adding a link: in the first one, the recycle bin can barely be seen as it gets hidden, the second one shows the link icon not being displayed as a square. Looks like this can happen both with Chrome and Firefox.",1371986068,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12609
+not displaying properly
+
+//attachment link icon not square.jpg ignored as obsolete//",1371985872,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12608
+not displaying properly
+
+//attachment overlapping recycle bin.jpg ignored as obsolete//",1371985844,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+imageinfo API returns incorrect data,"In this call http://en.wikipedia.org/w/api.php?action=query&prop=imageinfo&titles=File%3APowderfinger-My_Happiness-23s.ogg&iiprop=size%7Curl&iiurlwidth=200 it returns thumbwidth=""1913"" thumbheight=""-1"" as a size of an thumb, which is completly wrong.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1371774060,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-dvy6cixcc2nxje733xv6,task_description,resolved
+imageinfo API returns incorrect data,"This backport is now live; as such, marking this bug as fixed.",1372722142,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,"Change 71393 merged by Catrope:
+Clean up transform dimension height handling
+
+https://gerrit.wikimedia.org/r/71393",1372706216,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,"Change 71393 had a related patch set uploaded by Catrope:
+Clean up transform dimension height handling
+
+https://gerrit.wikimedia.org/r/71393",1372706194,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,"(In reply to comment #2)
+> Related URL: https://gerrit.wikimedia.org/r/69869 (Gerrit Change
+> Ide7208394f8495f5b143cbba215d4645598f1a50)
+
+This has been merged, and went out with wmf9. However, given that wmf8 is on the servers for an extra week and it makes really not-nice behaviour in VisualEditor, we probably want to back-port this.",1372581138,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,Related URL: https://gerrit.wikimedia.org/r/69869 (Gerrit Change Ide7208394f8495f5b143cbba215d4645598f1a50),1371829144,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,"There are actually two bugs going on here.
+
+First, TimedMediaHandler isn't normalizing dimensions for audio files, which means that the height=-1 being passed to indicate ""don't limit by height"" is being misinterpreted.
+
+And second, TimedMediaHandler is using an incorrect calculation when the height is the limiting factor on the thumbnail dimensions, leading to the width of 1913. The same happens if you pass something like iiurlwidth=220&iiurlheight=10.
+
+Since both of these are in TimedMediaHandler, I'm going to reassign this there. I'll also submit a patch momentarily.",1371829089,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+VisualEditor: Miscellaneous <span> tags added,"See https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FMet&diff=560772671&oldid=560563847 for example; I have no idea why (problem with the template itself?)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371748980,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jm7w3nmu4dvvbq4cevqz,task_description,resolved
+VisualEditor: Miscellaneous <span> tags added,"I believe we have fixed this bug; if it recurs, please re-open.",1373056128,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jm7w3nmu4dvvbq4cevqz,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Two users have reported on this. 
+
+See:
+http://en.wikipedia.org/w/index.php?title=User:AussieLegend/Vandals_etc&diff=prev&oldid=560719781
+
+And:
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Font_colors_in_signatures_changed
+
+I realize that this is probably tied into other behavior, but I lack code-fu to determine what. :)
+
+Maggie
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42803",1371732540,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-fhtlyq5kho6tpsip3niy,task_description,resolved
+VisualEditor: <span> annotations next to each other aren't necessarily the same,Merged and will go out tomorrow.,1373852393,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Change 73523 merged by jenkins-bot:
+HACK: Don't merge adjacent annotations from Parsoid
+
+https://gerrit.wikimedia.org/r/73523",1373852315,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,*** Bug 51234 has been marked as a duplicate of this bug. ***,1373711757,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Change 73523 had a related patch set uploaded by Esanders:
+HACK: Don't merge adjacent annotations from Parsoid
+
+https://gerrit.wikimedia.org/r/73523",1373664173,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Adding Parsoid bug 42803 as a dependency. We do add nowiki between most cases of adjacent quotes to ensure at least correctness, but the markup will indeed not be optimal.",1373643542,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,*** Bug 50291 has been marked as a duplicate of this bug. ***,1373632745,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"All we need to do is turn off similar annotation comparisons in VE completely, but Parsoid is not ready for that yet, for example adding new bold text next to Parsoid-generated bold text would create:
+
+<b data=parsoid="""">Old bold text</b><b>New bold text from VE</b>
+
+which Parsoid should obviously merge to:
+
+'''Old bold textNew bold text from VE'''
+
+but doesn't yet.
+
+Once this is all handled correctly, we can turn off similar annotation comparisons and the two bolds in <b>Foo</b><b>Bar</b> will no longer be merged (as they have will have different data-parsoid's). Of course Parsoid will not want to merge them either so that will factor into their logic.",1373632309,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"(In reply to comment #6)
+> I still see annotation merging on this test case:
+> 
+> http://www.mediawiki.org/wiki/User:GWicke/TestDoubleFormatting?veaction=edit
+> 
+> Steps to reproduce:
+> 
+> * append a char to 'baz'
+> * preview the change
+> 
+> Result: The bold ranges are merged, leading to a dirty diff
+> Expected result: no merging and no dirty diff
+That should be the only remaining annotation merging issue. I've been meaning to file a bug about it but I keep forgetting.
+
+Ed, we need to preserve the difference between <b>Foo</b><b>Bar</b> and <b>FooBar</b> somehow. Feel free to hit me up on IRC if you want to talk about how we should do that.",1373576556,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"I still see annotation merging on this test case:
+
+http://www.mediawiki.org/wiki/User:GWicke/TestDoubleFormatting?veaction=edit
+
+Steps to reproduce:
+
+* append a char to 'baz'
+* preview the change
+
+Result: The bold ranges are merged, leading to a dirty diff
+Expected result: no merging and no dirty diff",1373575903,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Several of these issues are actually on the VE side, so reopening.",1372735042,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"
+
+*** This bug has been marked as a duplicate of bug 48194 ***",1371814259,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"
+
+*** This bug has been marked as a duplicate of bug 42803 ***",1371813989,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"This is the same as bug 49478. We are dependent on it being in Parsoid first, otherwise we would reintroduce bug 48110.",1371812377,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"In this case:
+
+  <span style=""color:green;"">Aussie</span><span style=""color:gold;"">Legend</span>
+
+… is being simplified by DM into:
+
+  <span style=""color:green;"">AussieLegend</span>
+
+… which, unsurprisingly, Parsoid assumes means we wanted to combine them. :-)",1371773903,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,"Click ""add template"", then ""apply changes"" without adding a template (or add one, then remove it.
+
+Expected wikitext: none
+
+Actual wikitext: <span property=""mw:PageProp/noindex"" data-mw=""{&quot;parts&quot;:[]}""></span>
+
+We're clearly putting in a placeholder that we don't delete if the block is empty; because we don't display content blocks that don't render in read, you can't see these, which sucks and lets users do The Wrong Thing(tm).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371699420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-crkiryzxavcthffyf5za,task_description,resolved
+VisualEditor: Blank transclusion block doesn't get converted into blankness,"
+
+*** This bug has been marked as a duplicate of bug 49831 ***",1371744867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-crkiryzxavcthffyf5za,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","Something's gone wrong with our PHP parser re-render call; on re-render of block templates only, you get {{template call|param}} rather than nice lovely HTML. Presumably something to do with our hack yesterday? Plzfixkthxbai.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371699120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w3m2d62g427w2i6vbyd4,task_description,resolved
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","(In reply to comment #7)
+> I'm not sure if this is the same bug, but English Wikipedia users report that
+> when editing an infobox piped wikilinks display as [[word|word]] rather than
+> as it will appear on save. It saves correctly.
+> 
+> I managed to replicate this. If this should be split off into another bug,
+> sorry!
+
+That's bug 50801 which we're working on right now; re-closing this one. No worries. :-)",1373555274,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","I'm not sure if this is the same bug, but English Wikipedia users report that when editing an infobox piped wikilinks display as [[word|word]] rather than as it will appear on save. It saves correctly.
+
+I managed to replicate this. If this should be split off into another bug, sorry!",1373555086,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)",*** Bug 50361 has been marked as a duplicate of this bug. ***,1372690696,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)",*** Bug 50328 has been marked as a duplicate of this bug. ***,1372373510,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)",This should now be fixed and we will push it out this afternoon.,1372370057,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","Change 70865 merged by jenkins-bot:
+Fix escapeParams in transclusions to not escape other transclusions
+
+https://gerrit.wikimedia.org/r/70865",1372368607,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","Change 70865 had a related patch set uploaded by Esanders:
+Fix escapeParams in transclusions to not escape other transclusions
+
+https://gerrit.wikimedia.org/r/70865",1372360560,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)",*** Bug 49730 has been marked as a duplicate of this bug. ***,1372015399,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+VisualEditor: Phantoms are not relative to the surface content,"Reproduce:
+
+1. Open page with a protected node
+2. Click edit (visual editor)
+3. Quickly mouse over the protected node (while VE loads)
+4. See that the editor has slid the content down but the phantom is rendered under the mouse
+
+Perhaps the local overlay should be a peer of the documentNode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371696840,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-eepem2ziuzvmflw5gpqj,task_description,resolved
+VisualEditor: Phantoms are not relative to the surface content,Merged and will go out in the next few minutes.,1372210873,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eepem2ziuzvmflw5gpqj,task_subcomment,NA
+VisualEditor: Phantoms are not relative to the surface content,Didn't investigate yet but able to reproduce.,1371699532,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-eepem2ziuzvmflw5gpqj,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","Reported initially in bug 49596:
+
+ptwiki (""direita,right""): https://pt.wikipedia.org/w/index.php?&diff=36119075
+
+plwiki (""prawo,right""): https://pl.wikipedia.org/w/index.php?diff=36790309
+
+This feels like a Parsoid issue (VisualEditor doesn't know about localisations of these terms :-)) but Inez can tell us more details.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371690720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ipvexqb24ep4dnkhsnif,task_description,resolved
+"Images: Image insertion uses both the English and the localised syntax for ""right""",[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934016,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""",https://gerrit.wikimedia.org/r/70343 (Gerrit Change I9717e9d4b3b79cc9e583fb74e3537fbb5112a7bf) | change APPROVED and MERGED [by jenkins-bot],1372115880,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""",Related URL: https://gerrit.wikimedia.org/r/70343 (Gerrit Change I9717e9d4b3b79cc9e583fb74e3537fbb5112a7bf),1372114620,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","AFAIC, there is nothing wrong in using the localized version. The problem is to use both.",1371815473,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","These magic words are translateable at (for example for Polish) http://translatewiki.net/w/i.php?language=pl&module=words&title=Special%3AAdvancedTranslate - the entry for ""right"" says ""prawo, right"", which means both ""prawo"" and ""right"" are accepted and mean the canonical ""right"".
+
+This looks as if Parsoid was calling (implicitly?) .toString() on an array of these terms instead of taking its first entry: ['prawo', 'right'].toString() == 'prawo,right'.",1371714512,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","**winne2i** wrote:
+
+(I also mentioned ""/ramka/ means /frame/"" but I suppose ""ramka"" would be localised ""thumb""…?)",1371705767,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","**winne2i** wrote:
+
+It's not a
+ (localised 'thumb'),right
+this is
+ (localised 'right'),right
+as I mentioned in bug 49596 comment 6.",1371705686,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""",Correct - it is a Parsoid bug. Somehow it is similar to https://bugzilla.wikimedia.org/show_bug.cgi?id=48665 but definitely not a duplicate.,1371699745,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers","Whenever you think that you've fixed that damn script, you suddenly realize there's something else that's still wrong.
+
+
+Testing the fix for bug 49758, looking at its results:
+
+Created reports per component:
+VisualEditor           General                       33
+MediaWiki extensions   UniversalLanguageSelector     27
+VisualEditor           Editing Tools                 25
+VisualEditor           MediaWiki integration         12
+Wikimedia              Bugzilla                      11
+
+Created reports per product:
+MediaWiki                     43 
+Wikimedia                     45 
+MediaWiki extensions          104
+Security                      3  
+Tools                         5  
+
+it is clear that the ""product"" list does not list those products with the **highest** number of new tickets in the last week.
+
+This can be also seen on
+https://bugzilla.wikimedia.org/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfield=[Bug+creation]&chfieldvalue=&chfieldfrom=-7d&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap
+
+which right now lists these top 5 products:
+
+MediaWiki extensions  104
+VisualEditor          95
+MediaWiki             48
+Wikimedia             47
+Parsoid               23
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1371682740,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_description,resolved
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers",Deployed.,1372340940,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_subcomment,NA
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers","Shizzle, /me blind. ""ORDER BY foo DESC"" is teh win!",1371711921,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_subcomment,NA
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers",Related URL: https://gerrit.wikimedia.org/r/69629 (Gerrit Change Iecdc7439463f58be272cf0b73f662ac91d0b061b),1371711788,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_subcomment,NA
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers","Looking back at the very first revision of operations/puppet/templates/misc/bugzilla_report.php it already says:
+
+getBugsPerProduct() uses
+SELECT name, count(*) FROM bugs
+but
+getBugsPerComponent() uses
+SELECT name, count(*) as total FROM bugs
+
+That's the only difference I can spot in the query designs.",1371687352,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_subcomment,NA
+VisualEditor: TemplateSpecModel should expand aliases,"TemplateSpecModel currently doesn't expand aliases, so if it knows something as ""foo"" with an alias of ""1"" and the dialog asks about ""1"", it returns nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371671820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xszasferpgmq6tda243w,task_description,resolved
+VisualEditor: TemplateSpecModel should expand aliases,"See https://www.mediawiki.org/wiki/Extension:TemplateData#Defining_a_TemplateData_block
+
+Example:
+
+{
+  params: {
+    image: {
+      label: 'File name',
+      ...,
+      aliases: ['1', 'Image', 'Filename', .. ]
+    }
+  }
+}",1374680706,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xszasferpgmq6tda243w,task_subcomment,NA
+VisualEditor: TemplateSpecModel should expand aliases,"More a question that a bug. How do you specify an alias using templateData? There are lots of examples which use alternate capitalisation for parameters. For example {{Infobox World Heritage Site}}
+http://en.wikipedia.org/wiki/Template:Infobox_World_Heritage_Site
+uses both 'Image' and 'image' to specify an image. To specify both makes the documentation clumsy. An alias would be ideal.
+
+Also {{Quote}}}
+http://en.wikipedia.org/wiki/Template:Quote
+can be given in two forms, either positional:
+{{quote|phrase|person|source}} 
+or named:
+{{quote|text=phrase|sign=person|source=source}}
+Currently both are documented but it would be nicer to use aliases.",1374679695,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-xszasferpgmq6tda243w,task_subcomment,NA
+VisualEditor: TemplateSpecModel should expand aliases,Related URL: https://gerrit.wikimedia.org/r/70111 (Gerrit Change I37ec0e152df905844ac58ed1834fca29dccb4eec),1372033560,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xszasferpgmq6tda243w,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,"Using Chrome27.0.1453.110 m
+Replicated on Firefox 21.0
+
+Attempting to remove a template using the puzzle piece and ""remove"" function seems to succeed but leaves behind the following code:
+<span data-mw=""{&quot;parts&quot;:[]}"" class=""metadata plainlinks ambox ambox-style ambox-Orphan"" style></span>
+
+See:
+http://en.wikipedia.org/w/index.php?title=Cocking-cloth&diff=560630933&oldid=324780702
+
+and 
+http://en.wikipedia.org/w/index.php?title=Cocking-cloth&diff=560631541&oldid=560631467
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371661680,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_description,resolved
+VisualEditor: Blank transclusion block doesn't get converted into blankness,*** Bug 49970 has been marked as a duplicate of this bug. ***,1371844137,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,Merged and will be going out with next push.,1371748525,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,Related URL: https://gerrit.wikimedia.org/r/69686 (Gerrit Change Ic5d4fbf73f3d1be9cf877bc8b98096de9e98991a),1371745439,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,*** Bug 49855 has been marked as a duplicate of this bug. ***,1371744867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,*** Bug 49835 has been marked as a duplicate of this bug. ***,1371728132,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","When a user inserts [[links]] or {{templates}}, VisualEditor automatically wraps them into <nowiki> tags. Experienced contributors who are very used to using this syntax sometimes add it inadvertently.
+
+It would be a nice touch to show an unobtrusive warning to remind users that they need to use VisualEditor's menu to insert links, templates & other wikisyntax. LiquidThreads does this well when users insert their signature manually with ~~~ into their post
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50527
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50601",1371651600,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_description,resolved
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","The issue that caused this to be reopened (bug 52093) has been fixed and will be deployed soon; consequently, reclosing this.",1375203346,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Change 76701 merged by jenkins-bot:
+Set links in wikitext warning to load in new window
+
+https://gerrit.wikimedia.org/r/76701",1375201474,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #27)
+...
+> 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.
+
+Reported on bug 52093.",1375189962,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #27)
+> If it's not one thing, it's another ...
+
+Welcome to software development.",1375180789,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Change 76701 had a related patch set uploaded by Esanders:
+Set links in wikitext warning to load in new window
+
+https://gerrit.wikimedia.org/r/76701",1375180094,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","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.",1374794028,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #24)
+> The continued flow of markup errors shown by
+> http://en.wikipedia.org/w/index.php?title=Special:AbuseLog&wpSearchFilter=550
+> is a pretty good indication that the warning either isn't obtrusive enough or
+> clear enough. We're still seeing about 20 articles an hour corrupted because
+> of
+> this.
+> 
+
+there was a problem with the message (it opened at top of page instead of top of screen), because of bug 50870. since this bug is fixed, the message will become more effective (afaik, this fix was deployed on July 22).
+
+personally, i think that the right solution is outlined in bug 51897. however, ATM 51897 is marked as ""low"". if you think like i do, maybe you should lobby to bump up the priority of 51897.
+
+
+peace.",1374792947,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Another possibility: provide a side by side view of the two options the user has, and ask for confirmation:
+https://en.wikipedia.org/w/index.php?oldid=564535137#bug49820",1373995371,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**kwwilliams** wrote:
+
+The continued flow of markup errors shown by http://en.wikipedia.org/w/index.php?title=Special:AbuseLog&wpSearchFilter=550 is a pretty good indication that the warning either isn't obtrusive enough or clear enough. We're still seeing about 20 articles an hour corrupted because of this.
+
+I think this really needs a positive checkoff dialog, and the article shouldn't be saved until the editor has agreed that he really wants strings of brackets and pipes in his text. Having these in legitimately is an extremely rare case, especially for a novice editor. I'd block the edit with the edit filter if I could, but VE isn't able to display edit filter messages properly.",1373993008,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #19)
+> Depends on bug 51432
+
+This was already reported as bug 50870, adjusting.",1373982306,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**ignatzmice.wiki** wrote:
+
+(In reply to comment #21)
+> What about having the balloon (https://github.com/wikimedia/jquery-tipsy ?)
+> pointing exactly to the position where the wikitext was found?
+
+That might work pretty well too, especially if the balloon is a prominently ""warning"" color (as suggested somewhere by someone). I personally would be in favor of a big in-your-face notification, but I accept that not everyone will.",1373980188,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",What about having the balloon (https://github.com/wikimedia/jquery-tipsy ?) pointing exactly to the position where the wikitext was found?,1373979657,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**ignatzmice.wiki** wrote:
+
+(In reply to comment #18)
+> Created MW bug for position fixed. Due to the possibility of false positives,
+> having a blocking confirmation box may be too obtrusive.
+
+I dunno. I don't see a lot of false positives coming out of Filter 550. If you're really concerned, there could be a setting in the VE prefs to turn it off. (I definitely would NOT want a ""don't show again"" in the popup itself—too easy to get rid of it without clearly understanding what it means.)",1373973971,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",Depends on bug 51432,1373973173,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Created MW bug for position fixed. Due to the possibility of false positives, having a blocking confirmation box may be too obtrusive.",1373973112,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",Actually this is a general problem with jsMessages is general. They should be placed at a fixed position on the page.,1373956593,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Wikitext_warning_probably_won.27t_be_seen_by_most_editors for some more detailed info on pieces of it.,1373951338,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",I'm reopening this as it seems to be the best place. There is definitely an issue with the warning being only on top and so you really don't have to be scrolled down that much before you don't see the warning.,1373951190,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**ignatzmice.wiki** wrote:
+
+The little box is not nearly obtrusive enough. It should be a popup (like the ""are you sure you want to thank this user?"" popup) that says the same thing as the warning, but requires confirmation (even a sole ""OK"" button would be fine, so long as it actually disrupts the editor's typing).",1373950172,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Just tried this out - seems to be an issue.  If you are scrolled down far enough on an article, the warning is never seen.  It's tied to the top of the page. You can go all the way through the save process and only see the message once the new version loads.  I suspect this might be reducing the effectiveness of the notice.  (FF 22, OS 10.6.8)",1373949582,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",Feature to do this is now merged and will be deployed tomorrow.,1373855518,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Change 73569 merged by jenkins-bot:
+Warn users when they are typing wikitext
+
+https://gerrit.wikimedia.org/r/73569",1373855446,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Change 73569 had a related patch set uploaded by Catrope:
+Warn users when they are typing wikitext
+
+https://gerrit.wikimedia.org/r/73569",1373854895,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**ignatzmice.wiki** wrote:
+
+(In reply to comment #7)
+> (In reply to comment #6)
+> > A permanently dismissible first-use reminder may be sufficient. I suggest we
+> > try that and see if it significantly reduces incidents of wikitext insertion.
+> > See bug 50601 for discussion.
+> 
+> Habits die hard. When you've been entering wikitext manually for the past 12
+> years, it's _really_ hard to change your habits. I really doubt a ""first-use
+> reminder"" will be enough.
+
+Yes, this. I recognized the problem first time I did it, and it still happens.",1373844634,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #4)
+> I have already suggested bug 50527 as a possible solution to this problem. An
+> automatic tag and then manual correction would be a simple-to-implement
+> interim
+> measure, if not long term.
+
+Bug 50527 proposes that the edit go through, WITHOUT warning the editor of his/her mistake; instead, the edit summary gets a tag showing that a problem exists with the *completed* edit. Given that the software can detect this error, it makes more sense to give the editor who made the mistake a chance to fix it *before* the edit is completed - ideally, not to allow the edit to be completed with the error intact within in. That way, (a) the editor is more likely not to make the mistake again, and (b) if the editor who made the mistake fixes it before finalizing his/her edit, there is no need for a second (corrective) edit (and no need for someone to be monitoring recent changes for the tag proposed in bug 50527).",1373662680,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #6)
+> A permanently dismissible first-use reminder may be sufficient. I suggest we
+> try that and see if it significantly reduces incidents of wikitext insertion.
+> See bug 50601 for discussion.
+
+Habits die hard. When you've been entering wikitext manually for the past 12 years, it's _really_ hard to change your habits. I really doubt a ""first-use reminder"" will be enough; I still expect people to add [[ inside VisualEditor in 5 years. All drivers learn what the speed limits are before they get their driving license, but there are still speed limit signs on the roads :)
+
+A guided tour is indeed a great idea, but _in addition_ to an always-shown-when-wikitext-is-detected warning, not as a replacement, imho.",1373656626,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",A permanently dismissible first-use reminder may be sufficient. I suggest we try that and see if it significantly reduces incidents of wikitext insertion. See bug 50601 for discussion.,1372986202,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",And bug 50093 for an alternative [[ suggestion.,1372878170,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","I have already suggested bug 50527 as a possible solution to this problem. An automatic tag and then manual correction would be a simple-to-implement interim measure, if not long term.",1372862368,PHID-USER-65pjzcmoby2fsgzdrfjq,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",%%%*** Bug 50581 has been marked as a duplicate of this bug. ***%%%,1372859187,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","""What Chris said"". I'd like to know the rationale for the priority rating on this; it's the biggest source of article corruption.",1372844611,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",Why is this marked low priority? It is causing problems on the live wiki with people unable to figure out why their edit has not worked - the VE hides the nowiki tags it has inserted so its impossible to determine the cause unless one knows about this feature (which I've not seen in documentation) or uses the misnamed edit source.,1372844039,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"screenshot
+
+When selecting some templates in VisualEditor, a blue rectangle appears in the top left corner of the browser's window, and disappears when the template is unselected.
+
+Encountered on https://en.wikipedia.org/wiki/User:Jdforrester_%28WMF%29/Sandbox?veaction=edit (see screenshot)
+
+Firefox 21.0 on openSUSE 12.3
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50074
+
+**Attached**: {F11783}",1371649560,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-sidkh5inlhdkyygqassz,task_description,resolved
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,Appears resolved.,1373536056,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"(In reply to comment #7)
+> As noted by JamesF in 50161, this still occurs (Vector, Chrome, Win 7).
+> Screenshot while editing ref. #6 in
+> http://it.wikipedia.org/wiki/Utente:Syrio/Bozzoli , you need to click at
+> least
+> a few times on the sentence before the puzzle piece pops up. It will allow
+> you
+> to edit the reference and save the page as usual. It might be worth noting
+> that
+> the page features a page title and a magic word. Thanks.
+
+I now can't reproduce this - can you check too? (We did a new release today which should have fixed this for good.)",1373512100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"As noted by JamesF in 50161, this still occurs (Vector, Chrome, Win 7).
+Screenshot while editing ref. #6 in http://it.wikipedia.org/wiki/Utente:Syrio/Bozzoli , you need to click at least a few times on the sentence before the puzzle piece pops up. It will allow you to edit the reference and save the page as usual. It might be worth noting that the page features a page title and a magic word. Thanks.",1373440558,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"Created attachment 12812
+Light blue bar issue still occurring
+
+**Attached**: {F11784}",1373440247,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,Fixed and will go out in the next release.,1372461348,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"Change 71118 merged by jenkins-bot:
+Don't draw highlights over hidden elements.
+
+https://gerrit.wikimedia.org/r/71118",1372458730,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"Change 71118 had a related patch set uploaded by Robmoen:
+Don't draw highlights over hidden elements.
+
+https://gerrit.wikimedia.org/r/71118",1372452480,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"Confirmed, happens in firefox and chrome.",1372118693,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,%%%*** Bug 50074 has been marked as a duplicate of this bug. ***%%%,1372118661,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Image dialog shows <visualeditor-dialog-media-content-section> instead of actual message,"Encountered on: https://en.wikipedia.org/wiki/Westplex?veaction=edit
+Firefox 21.0 on openSuse 12.3
+
+When opening the ""Media settings"" overlay by clicking the icon on the image, the title shows <visualeditor-dialog-media-content-section> instead of what I assume should be the actual system message.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1371649140,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-n7i2eetsofstfrmijiw5,task_description,resolved
+VisualEditor: Image dialog shows <visualeditor-dialog-media-content-section> instead of actual message,Fixed by gerrit 69497 which we will try to get pushed today.,1371657503,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n7i2eetsofstfrmijiw5,task_subcomment,NA
+VisualEditor: Pressing escape should close a dialog,"Like we do with the link inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371644280,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ovbuk7vqve57dhhhvnh7,task_description,resolved
+VisualEditor: Pressing escape should close a dialog,This fix will be pushed to production later this afternoon; closing as such.,1372378620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ovbuk7vqve57dhhhvnh7,task_subcomment,NA
+VisualEditor: Pressing escape should close a dialog,"Change 70946 merged by jenkins-bot:
+Close dialogs on escape
+
+https://gerrit.wikimedia.org/r/70946",1372378238,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ovbuk7vqve57dhhhvnh7,task_subcomment,NA
+VisualEditor: Pressing escape should close a dialog,"Change 70946 had a related patch set uploaded by Trevor Parscal:
+Close dialogs on escape
+
+https://gerrit.wikimedia.org/r/70946",1372377665,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ovbuk7vqve57dhhhvnh7,task_subcomment,NA
+VisualEditor: Image corruption edits - garbled text inserted into image description,"See, for example, http://en.wikipedia.org/w/index.php?title=Audie_Murphy&diff=560382883&oldid=560374610 - the line ""ad a private-pilot license and"" (image description) is clearly being taken from the article text ""had a private-pilot license and a reported 8, 000 hours of flying time"", but I have no idea how.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371640500,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-rjfwlifxsqzej72hvwal,task_description,resolved
+VisualEditor: Image corruption edits - garbled text inserted into image description,These were fixed by Inez's new code from Thursday.,1372016417,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rjfwlifxsqzej72hvwal,task_subcomment,NA
+VisualEditor: Image corruption edits - garbled text inserted into image description,"**molly.white5** wrote:
+
+A user just came to IRC asking about this same issue. The user had made this edit: http://en.wikipedia.org/w/index.php?title=Harry_Belafonte&diff=560738876&oldid=560738222
+
+The user had only intended to make the changes that appear between lines 98 and 108; all of the other changes appear to be a product of this bug.
+
+The same issue occurred for the user in http://en.wikipedia.org/w/index.php?title=Harry_Belafonte&diff=560737462&oldid=560717280.",1371737760,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rjfwlifxsqzej72hvwal,task_subcomment,NA
+VisualEditor: Some template dialog loading attempts fail with 'TypeError',"Steps to reproduce:
+
+1) Visit https://en.wikipedia.org/wiki/Deliciosamente_amoral?veaction=edit
+
+2) Attempt to manipulate the contents of the infobox by clicking the puzzle piece icon associated with it.
+
+Expected behavior:
+
+Infobox parameters should be editable.
+
+Actual behavior:
+
+Template editor invocation fails with the following error on the console:
+
+Uncaught TypeError: Cannot read property 'description' of undefined 
+
+Chrome/Ubuntu
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49493",1371614460,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ic77u5udy3nvxbsnznrc,task_description,resolved
+VisualEditor: Some template dialog loading attempts fail with 'TypeError',"Yes, this is a dupe of bug 49493; sorry!
+
+*** This bug has been marked as a duplicate of bug 49493 ***",1371748994,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ic77u5udy3nvxbsnznrc,task_subcomment,NA
+VisualEditor: Some template dialog loading attempts fail with 'TypeError',"This might be linked to bug 49493 - Timo, any quick thoughts?",1371614781,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ic77u5udy3nvxbsnznrc,task_subcomment,NA
+VisualEditor: Inspector menu appears with blank entry in Firefox,"Example screenshot of the issue
+
+In the given link, for reference 7's template; only in Firefox - works fine in Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=VisualEditor:TestReferenceContents&oldid=713075
+
+**Attached**: {F11716}",1371594720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xu4scnfjjp674hs6ehjl,task_description,resolved
+VisualEditor: Inspector menu appears with blank entry in Firefox,Patched and merged: https://gerrit.wikimedia.org/r/#/c/70119/,1372190121,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-xu4scnfjjp674hs6ehjl,task_subcomment,NA
+VisualEditor: Pawn appears when Cmd-C over a selected inline image in Firefox,"https://en.wikipedia.org/wiki/List_of_highways_numbered_147?veaction=edit
+
+I selected an inline image in the editor (in itself strange, because it doesn't seem you can edit it). I then hit cmd-c, and the inline image was replaced by the pawn char.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371579000,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-eiikdpgxia5svismvu44,task_description,resolved
+VisualEditor: Pawn appears when Cmd-C over a selected inline image in Firefox,Fixed (I think) in gerrit 69503 which we will deploy this afternoon.,1371680649,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eiikdpgxia5svismvu44,task_subcomment,NA
+VisualEditor: Pawn appears when Cmd-C over a selected inline image in Firefox,"Actually, Safari 6 for me.",1371649398,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-eiikdpgxia5svismvu44,task_subcomment,NA
+VisualEditor: Pawn appears when Cmd-C over a selected inline image in Firefox,"Yet again, a Firefox bug. *sighs*
+
+(Editing images will be possible very very soon. :-))",1371580229,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eiikdpgxia5svismvu44,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","<b><b>Foo</b></b> == <b>Foo</b> so it's not /so/ bad if VE corrects it (but it's still a bit dirty, but <small><small>Foo</small></small> != <small>Foo</small> (and the same with <big> and <sup> and …)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=User:JohnCD/draft&diff=560430675&oldid=560430611",1371574560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_description,resolved
+"VisualEditor: Nested identical annotations can be additive, not just identical",Now fixed.,1373503078,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical",Fixed on the VisualEditor side; the Parsoid upstream issue in Domino is patched but not yet released. Not marking as fixed until that's done.,1373318742,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","Change 72133 merged by jenkins-bot:
+Make all annotations additive
+
+https://gerrit.wikimedia.org/r/72133",1373313118,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","Change 72133 had a related patch set uploaded by Esanders:
+Make all annotations additive
+
+https://gerrit.wikimedia.org/r/72133",1373055582,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","(In reply to comment #4)
+> The fix sets big/small/sup/sub to be additive.
+> 
+> Arguably we should make all annotations additive, as you could add
+> 'style=""font-size:110%""' to anything, although I haven't thought through how
+> this might affect the toolbar interactions yet.
+
++1. This will also avoid dirty diffs on such content.",1372801723,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","Change 71716 merged by jenkins-bot:
+Allow annotations to be additive
+
+https://gerrit.wikimedia.org/r/71716",1372797972,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","The fix sets big/small/sup/sub to be additive.
+
+Arguably we should make all annotations additive, as you could add 'style=""font-size:110%""' to anything, although I haven't thought through how this might affect the toolbar interactions yet.",1372797053,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","Change 71716 had a related patch set uploaded by Esanders:
+Allow annotations to be additive
+
+https://gerrit.wikimedia.org/r/71716",1372796724,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical",This causes round-trip failures.,1372723619,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical",%%%*** Bug 49756 has been marked as a duplicate of this bug. ***%%%,1371574644,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+VisualEditor: Support creation/editing of references using an existing ref-name,"The reference editor allows me to group references, and allows me to include a ref name parameter to make them reusable, but has no way of actually calling that ref name.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371535560,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_description,resolved
+VisualEditor: Support creation/editing of references using an existing ref-name,"This feature is now written and merged, and will be going out in a few minutes.",1372382660,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_subcomment,NA
+VisualEditor: Support creation/editing of references using an existing ref-name,"Change 70364 merged by jenkins-bot:
+Reference insertion, new and existing
+
+https://gerrit.wikimedia.org/r/70364",1372382035,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_subcomment,NA
+VisualEditor: Support creation/editing of references using an existing ref-name,"... this is already what's meant to happen with master; it seems that it's broken a little in this regard, so we'll need to fix.",1371573652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_subcomment,NA
+VisualEditor: Support creation/editing of references using an existing ref-name,"Proposing for July 4 milestone (alt. July 11). This is imho not a nice-to-have but a requirement since re-using of references is quite common and without it, it would seem incomplete.
+
+The ability to create such references or turn existing ones into it may be less important than the ability to edit such references (e.g. a <select> with all ref-names available on this page).",1371540715,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B","Screenshot
+
+See associated character; italics in the reference editing interface causes a pawn to appear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11627}",1371533160,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-v4v3wychksw2n5sabckt,task_description,resolved
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B",*** Bug 49877 has been marked as a duplicate of this bug. ***,1371774369,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B",*** Bug 49888 has been marked as a duplicate of this bug. ***,1371773590,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B",Fixed in gerrit 69503 which we will deploy this afternoon.,1371680618,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B","Actually, neither the console nor firebug show any errors.
+
+It is an italicised or bolded pawn, however, so we can confirm that works.",1371634405,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B","Please check your browser's JS console, there should be an error message that appears there at the same time that the pawns appear in the editor.",1371602813,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B",Also adding a pawn on bolding.,1371534835,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+VisualEditor: Template inspector removing characters from header,"See associated screenshot; an attempt to add 'foo' to the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371532980,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ukps7g4li7inap7lxq46,task_description,resolved
+VisualEditor: Template inspector removing characters from header,This is an artefact of a Parsoid serialisation bug that has now been fixed.,1371657198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ukps7g4li7inap7lxq46,task_subcomment,NA
+VisualEditor: Template inspector removing characters from header,"Screenshot
+
+**Attached**: {F11626}",1371533000,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ukps7g4li7inap7lxq46,task_subcomment,NA
+VisualEditor: Prevent headings in reference sub-editor dialogs,"**Author:** `rachelqa99`
+
+**Description:**
+Make a reference, then type text into Name content, and change format to Heading 5 or Heading 3.  When you save the file, you see the wikitext displayed for the heading format. 
+
+See page: https://www.mediawiki.org/wiki/User:Rachel99/testing_edit_source
+
+On the bottom of the page, it looks like that.
+
+    ↑ ===test===
+    ↑ =====Book reference=====
+    ↑ ===footnote text===
+    ↑ =====test5=====
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371500340,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-563eb2ikcrhdth26zmqs,task_description,resolved
+VisualEditor: Prevent headings in reference sub-editor dialogs,Merged and will be deployed very soon.,1371845722,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-563eb2ikcrhdth26zmqs,task_subcomment,NA
+VisualEditor: Prevent headings in reference sub-editor dialogs,Related URL: https://gerrit.wikimedia.org/r/69867 (Gerrit Change Ic823a90398dafca1caf8fa4142d98133ab661d7c),1371828262,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-563eb2ikcrhdth26zmqs,task_subcomment,NA
+VisualEditor: Prevent headings in reference sub-editor dialogs,"Yes, this is a definite issue - there's a wider bug about the technical functionality, bug 49657, but this is a specific example we need to do (and so soon).",1371506764,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-563eb2ikcrhdth26zmqs,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,"on beta labs only, not seen in mediawiki.org: 
+
+On any article e.g. http://en.wikipedia.beta.wmflabs.org/wiki/0.0924627428112147 
+
+Click Edit to invoke VE
+
+Page content is a different article.  In the case of http://en.wikipedia.beta.wmflabs.org/wiki/0.0924627428112147 I see the content for an article on ""TAT-1""
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49963",1371486720,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_description,resolved
+VisualEditor link to Parsoid broken in beta labs deployment?,This was fixed yesterday by Roan.,1372390935,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,Related URL: https://gerrit.wikimedia.org/r/70582 (Gerrit Change Iacc9e88ec83e9037abe9ace53deccafcf68a6bbb),1372215640,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,"This is my fault, I broke this in https://gerrit.wikimedia.org/r/#/c/68133/ . We should revert that change and figure out a way to keep deployment-parsoid2 up-to-date.",1372215604,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,"Created attachment 12594
+modal upon review or save
+
+**Attached**: {F11548}",1371760280,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,"This still happens after upgrading VE to the latest version, with error saying ""invalid token"", see screen shot",1371760230,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","Alongside the ""minor"" and ""watch"" checkboxes in the save dialog, for pages with FlaggedRevs switched on and outstanding unaccepted revisions, add a checkbox to ""accept pending revisions"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50852",1371485400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyh6rgmh65nrcg5ssati,task_description,resolved
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog",Merged and will get deployed in a few hours' time.,1374649658,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","Change 75555 merged by jenkins-bot:
+Render check boxes from EditPage
+
+https://gerrit.wikimedia.org/r/75555",1374649652,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","Change 75555 had a related patch set uploaded by Catrope:
+Render check boxes from EditPage
+
+https://gerrit.wikimedia.org/r/75555",1374648415,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog",*** Bug 51833 has been marked as a duplicate of this bug. ***,1374645680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #6)
+> I note this has been posted as an enhancement; however, as flagged revisions
+> are applied to *all* pages in article space on certain Wikipedias (de and ru
+> in particular) I'd urge that this be resolved prior to introducing VisualEditor
+> to those projects. For them, the absence of this would be more than the minor
+> inconvenience it is on English Wikipedia, where PC is applied to a very small
+> number of pages and could be switched to semi-protection if really needed.
+
+Absolutely.",1374081153,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #0)
+> Alongside the ""minor"" and ""watch"" checkboxes in the save dialog, for pages
+> with
+> FlaggedRevs switched on and outstanding unaccepted revisions, add a checkbox
+> to
+> ""accept pending revisions"".
+
+I note this has been posted as an enhancement; however, as flagged revisions are applied to *all* pages in article space on certain Wikipedias (de and ru in particular) I'd urge that this be resolved prior to introducing VisualEditor to those projects.  For them, the absence of this would be more than the minor inconvenience it is on English Wikipedia, where PC is applied to a very small number of pages and could be switched to semi-protection if really needed.",1374080923,PHID-USER-yif6nz5uhka5cnltixpc,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #4)
+> (In reply to comment #2)
+> > Just as an addition to this: I'm not sure if just the checkbox is what is
+> > needed. The current work flow has a whole separate page because we need to
+> > show the diff involved for the review. I imagine that can be done without
+> > going to a new page but either way they should be able to review the diff
+> > (and preferably leave a comment like you can in the review page now) before
+> > checking any kind of approve box since they become somewhat responsible for
+> > those edits.
+> 
+> Yes, indeed; I was imagining:
+> 
+> * on load, an alert in the edit notices saying ""You will need to accept the
+> outstanding changes before saving"" (or whatever the current message is) -
+> possibly with a link to the below?
+> * on entering the save dialog, the save button will be disabled with another
+> copy of the ""You will need to accept the outstanding changes before saving""
+> text (in the same place as the edit conflict / CAPTCHA / DOM corruption
+> warnings)
+> * in the line of buttons (""Save page"", ""Review your changes"") there should
+> be a
+> third button, ""Review outstanding changes"", which on click pops up the diff
+> of
+> outstanding changes, with a text box for the optional review comment and an
+> ""accept these changes"" button that takes you back to the save dialog, now
+> with
+> the save button enabled.
+> 
+> Feels a little clunky, though - perhaps we could make the process in-line
+> with
+> the edit summary message?
+
+Since this is going to need to be fully in javascript for VisualEditor, and the interface for this in FlaggedRevisions is already mostly in javascript (a small bit is done server-side through EditPage hooks), I recommend we not duplicate all of this logic and API handling for:
+* ""advertise you are reviewing this""
+* API handling ""leave comments""
+ ""get the diff against the latest stable version""
+* ""mark as reviewed"" 
+* etc.
+
+And instead depend on the logic being in FlaggedRevisions in a re-usable way that we can just call from within VisualEditor.
+
+Ideally they would also make their styling more pretty so that we can actually re-use it. Alternatively they'll have to make the logic re-usable separate from the UI as the current UI is not going to fit in (not just visually foreign to VisualEditor or usable interfaces in general, but also technically due to the DOM structure and layout properties).",1374008109,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #2)
+> Just as an addition to this: I'm not sure if just the checkbox is what is
+> needed. The current work flow has a whole separate page because we need to
+> show the diff involved for the review. I imagine that can be done without
+> going to a new page but either way they should be able to review the diff
+> (and preferably leave a comment like you can in the review page now) before
+> checking any kind of approve box since they become somewhat responsible for
+> those edits.
+
+Yes, indeed; I was imagining:
+
+* on load, an alert in the edit notices saying ""You will need to accept the outstanding changes before saving"" (or whatever the current message is) - possibly with a link to the below?
+* on entering the save dialog, the save button will be disabled with another copy of the ""You will need to accept the outstanding changes before saving"" text (in the same place as the edit conflict / CAPTCHA / DOM corruption warnings)
+* in the line of buttons (""Save page"", ""Review your changes"") there should be a third button, ""Review outstanding changes"", which on click pops up the diff of outstanding changes, with a text box for the optional review comment and an ""accept these changes"" button that takes you back to the save dialog, now with the save button enabled.
+
+Feels a little clunky, though - perhaps we could make the process in-line with the edit summary message?",1373149022,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #0)
+> Alongside the ""minor"" and ""watch"" checkboxes in the save dialog, for pages
+> with
+> FlaggedRevs switched on and outstanding unaccepted revisions, add a checkbox
+> to
+> ""accept pending revisions"".
+
+I don't find that an acceptable solution, because there is a requirement that reviewers actually review the edit they are accepting; they cannot do that if they're just ticking a box.  
+
+See https://commons.wikimedia.org/wiki/File:Cropped_edit_source_admin_edit_with_existing_PC.png for what the screen looks like using Edit Source.  Note that the diff includes ALL unreviewed changes.",1373148387,PHID-USER-yif6nz5uhka5cnltixpc,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog",Just as an addition to this: I'm not sure if just the checkbox is what is needed. The current work flow has a whole separate page because we need to show the diff involved for the review. I imagine that can be done without going to a new page but either way they should be able to review the diff (and preferably leave a comment like you can in the review page now) before checking any kind of approve box since they become somewhat responsible for those edits.,1373147476,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog",*** Bug 50852 has been marked as a duplicate of this bug. ***,1373145699,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+VisualEditor: Templates (incorrectly) expanded,"https://en.wikipedia.org/wiki/Template:Contradictory, on https://en.wikipedia.org/wiki/Necessity - in the VisualEditor it displays as [<span title=""This text contradicts text in the article ""Necessity in English law"" (3 May 2011)"">contradictory]. Reproduced in Chrome 27/Safari 6.0.5 on a Mac, Firefox 21.0 on Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371469920,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-nbmggedatdejjopgumhd,task_description,resolved
+VisualEditor: Templates (incorrectly) expanded,"I changed the Contradict-inline template and that fixes this problem.
+
+https://en.wikipedia.org/w/index.php?title=Template%3AContradict-inline&diff=560522227&oldid=471439681",1371596252,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-nbmggedatdejjopgumhd,task_subcomment,NA
+VisualEditor: Templates (incorrectly) expanded,"This amounts to accepting <span title=""""foo"""">bar</span> as a valid span-tag. Ugh! The PHP parser seems to accept this quite fine.  Parsoid would have to perform the same magic.
+
+See http://en.wikipedia.org/w/index.php?title=Wikipedia:Sandbox&oldid=560521020
+
+Hover over the two foos and see the difference. PHP parser drops the title attribute 'bar' on the first foo since it is ofcourse a bug.
+
+Seems like a reasonable fix the Fix templat -- but I assume Fix is used in a lot of places and fixing the callers would be a lot of work ... so, we may need some ugly hack in Parsoid to support this.",1371595653,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-nbmggedatdejjopgumhd,task_subcomment,NA
+VisualEditor: Templates (incorrectly) expanded,"Reduced test case: {{Fix|text=foo|title=""bar""}}
+
+It is the quotes around ""baz"" that trips up Parsoid (probably the tokenizer).  Investigating more.",1371595194,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-nbmggedatdejjopgumhd,task_subcomment,NA
+VisualEditor: Templates (incorrectly) expanded,This is actually [[Template:Contradict-inline]] that appears broken in Parsoid - see http://parsoid.wmflabs.org/en/Template:Contradict-inline - shunting over.,1371513710,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nbmggedatdejjopgumhd,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size","See https://en.wikipedia.org/wiki/Hermann_M%C3%BCller_%28politician%29 for example; found in Chrome 27 on a Mac. In Safari 6.0.5 it displays differently (a large space appears, rather than a missing icon signifier) but is still broken. Not replicatable in Firefox 21.0/Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://parsoid.wmflabs.org/en/Hermann%20M%C3%BCller%20(politician)",1371469740,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_description,duplicate
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size","The original bug was rendering of [[:Media:Hermann Müller.ogg]].
+
+The rendering of [[File:Hermann Müller.ogg]]/[[File:La_Marseillaise.ogg]] is a different problem, as that renders as a player in source editor.  There are some underlying problems in Parsiod and even the mw API if I am understanding bug 49896 correctly.",1374915779,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size","Seems to me, this is still buggy !
+
+Have tried the following code at http://parsoid.wmflabs.org/_rtform/:
+[[File:La_Marseillaise.ogg]]
+
+This gives:
+<img resource=""./File:La_Marseillaise.ogg"" src=""//upload.wikimedia.org/wikipedia/commons/3/30/La_Marseillaise.ogg"" data-parsoid=""{&quot;a&quot;:{&quot;resource&quot;:&quot;./File:La_Marseillaise.ogg&quot;},&quot;sa&quot;:{&quot;resource&quot;:&quot;File:La_Marseillaise.ogg&quot;}}"" width=""200"">",1373452147,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size",[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934039,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size",This is now fixed in production for Parsoid (and so for VisualEditor). Sorry for the bug!,1371519787,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size","It's inserting a thumbnail image at fixed 200px width.
+
+<img resource=""./File:Hermann_Müller.ogg"" src=""http://upload.wikimedia.org/wikipedia/commons/d/d3/Hermann_M%C3%BCller.ogg"" width=""200"" data-parsoid=""{&quot;a&quot;:{&quot;resource&quot;:&quot;./File:Hermann_Müller.ogg&quot;},&quot;sa&quot;:{&quot;resource&quot;:&quot;:File:Hermann Müller.ogg&quot;}}"">",1371475842,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Bug title may be a bit confusing; essentially, a user has suggested that the VE auto-convert wikimarkup entered ''into'' the VE, on save. The use case is users who keep typing [[link]], basically.
+
+My feelings on this are mixed; I think it's perfectly possible that this would be useful, but it sounds like a ton of work and it's also perfectly possible that, once we go live, muscle memory will adapt and there'll be no point to this. For now, sticking it in as a potential future enhancement.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49820
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51899
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47779",1371468300,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gmfhmaeyushutcy45y6x,task_description,declined
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to Amalthea from comment #40)
+> I really don't get why you're fighting this so hard.
+
+It should be obvious by now that VE's development has been made an ideological matter. This feature request involves some degree of the ""old way"" of doing things, thus is forbidden.",1400618098,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"I'll clarify that ""it shouldn't happen"" means just that it is not useful/desirable to have it IMHO, or at least I can't think of a situation where it would be.",1380723401,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"48891 and 53974 cover that specific problem. The wikimarkup warning is just a warning, it does not stop you from doing anything. 
+As for [[[[this situation]]]], of course it shouldn't happen. I can't recall the bug number though, right now, and since a quick search did not seem successful, I'll come back on that later.",1380722782,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Wikifram** wrote:
+
+What I mean is that you start with wikimarkup visible in the VE editing mode. When you add something (''not'' wikimarkup) inside such wikimarkup, you get the wikimarkup notice at the top right; but on saving, the existing wikimarkup remains. [https://www.mediawiki.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandboxVE&diff=794444&oldid=794415]
+
+So my questions are; why is the existing wikimarkup accepted and displayed here, why is it recognised by the wikimarkup detection error, but why is it then not changed on saving? 
+
+This behaviour may give a clue as to how wikimarkup can be accepted in VE after all (but then again, perhaps not), but it certainly is baffling me.",1380722209,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Hi there, I don't think I see your VEdit there. I did https://www.mediawiki.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandboxVE&diff=794415&oldid=794413 and https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=575429594&oldid=575429509 instead, nowikis are added as the only expected outcome. Which conversion should have happened when VEditing? Thanks.",1380717126,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Wikifram** wrote:
+
+Can someone explain why [https://www.mediawiki.org/wiki/Communication?veaction=edit this page] seems to accept wikitext markup, even in VE mode? On saving, it gives the ""nowiki"" warning, but it doesn't actually convert the existing ""[["" and ""]]"" into wikitext. A very strange page in VE mode, that one.",1380715761,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Amalthea.wikimedia** wrote:
+
+(In reply to comment #39)
+> [...] this bug is - by definition of the product - a WONTFIX.
+
+James, this is simply not true. See comment #36 about auto formatting logic in other visual word processors.
+I really don't get why you're fighting this so hard.",1377849879,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #10)
+> Marking as WONTFIX per my earlier comments and Erik's.
+
+… again. Bug 51897 is indeed different; my apologies for merging it based on my reading of the bug as filed. However, this bug is - by definition of the product - a WONTFIX.",1377819704,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"user John Broughton at en.wp comments:
+""Rather than focus on improving [the warning about entering wikitext], a better direction to go would be for VE to be able to convert wikitext to its equivalent in VE. Thus if one typed [[New York City]], for example, VE would convert that to its format for an internal link. This is fairly straight-forward, programming-wise: after VE adds a closing nowiki tag for some text, it would examine it for conversion possibilities: external link? internal link? footnote? template?""",1376340113,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #22)
+> 
+> If accidental insertion of wikitext is still an issue, we should focus on
+> other
+> ways to mitigate that issue.
+
+2 things: 
+1) it's not an ""if"", and i do not think you guys should wait for the community to prove it to you. you should go hunt for it, so you can see for yourselves that it *is* an issue (hint: look for edits with ""visualeditor"" tag that added <nowiki>: approximately 100% of those represent the problems. you have to tools to actually measure it across all projects where VE is enabled by default).
+2) ""focus on other ways to mitigate that issue"": how about solving bug 51897, instead of marking it ""low"" and basically ignoring it? this *is* exactly ""other ways to mitigate that issue"". 
+or ,alternatively, find a better way to solve it: right now, it seems the team is saying ""we'll focus on other ways to mitigate the issue"", but they do not actually mean it: what other ways? who is working on it? what do they do? where is the ""focus""?
+what you guys are doing today does not look very much like ""focus"" - it looks much more like ignoring the issue and hoping the problem will go away by itself.
+
+
+
+(In reply to comment #18)
+> Sorry, but this is not something we'll ever do, as I explained in comment 9.
+> It's not simply a matter of prioritization - it's a matter of ensuring we can
+> provide a user experience that's not modeled on markup, but on best user
+> experience practices. As James said, we provide keyboard shortcuts, and will
+> provide other user interfaces optimized for markup. But parsing markup within
+> the visual editing context is completely off the table.
+
+this is nothing more and nothing less than saying ""it's so because i said so"". 
+you made a bad decision. that's something that happened in life to (almost) all of us. the problem is not so much this bad decision - the problem your refusal to accept that it was a bad decision, and you insistence that it was a good decision, in face of all the evidence.
+
+
+The reason i am writing this is because nowhere can i find any indication that the VE team actually changed its mind or at least decided to reconsider. 
+it is very much possible that the team actually *did* decide to reconsider, and i just missed it. if this is the case, please be graceful and ignore my rant.
+
+peace.",1375729537,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Amalthea.wikimedia** wrote:
+
+Erik:
+
+(In reply to comment #18)
+> it's a matter of ensuring we can provide a user experience that's not modeled
+> on markup, but on best user experience practices.
+
+I don't think that was the suggestion above?
+
+Word processors have long supported text-based auto formatting logic, and they certainly aren't focusing on underlying markup. For example, to this day, you can *bold* and _italicize_ text in OpenOffice Writer and Microsoft Word by using the traditional markup, or define numbered and bulleted lists simply by starting the first item with ""* "", ""- "", or ""1. "".
+
+Adding auto-formatting logic does not impair the goals of the visual editor: defining a link via square brackets won't be the obvious way, and it will likely not be advertised anywhere except possibly in some settings page. It can be helpful without taking anything away from the vision.",1375614123,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Wikifram** wrote:
+
+Note that this question is included in the large [[Wikipedia:VisualEditor/Default State RFC]] on the en.wikipedia, as question 5. The current tally, for what's it worth, is 28 supporting and 22 opposing, but with many conditional comments on both sides (""yes for X but no for Y""). Many of the opposes are ""no, because this is a WYSIWYG"", but in reality, of course, this isn't a wysiwyg but a hybrid anyway... (you still need to know wikimarkup to do a lot of things in the new editor in mainspace as well)",1375426633,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Wikifram** wrote:
+
+Erik Moeller, do you have any idea how many hours are spent on correcting these ""nowikis"" every day? Do you, on the other hand, have any data on how many ""correct"" nowiki tags are added? Is there any reason why what should be a no-brainer (not per se an easy one technically, but a no-brainer from the should-be-done point-of-view) improvement is so drastically rejected? 
+
+Have any of you considered that, as of now, new editors using only VE and only editing the mainspace still need to know the [[ ]] syntax anyway? A simple example: on the English wikipedia, I opened [[HKBK College of Engineering]] with the VE, and clicked on the infobox. Click on a parameter, e.g. city, and what you are confronted with is [[Bangalore]]. So new editors ''need'' to use it in the infobox, but are ''not allowed'' to use it in the article text, and this is supposed to be an improvement why? 
+
+What is actually the reason (apart from perhaps ""technical difficulty"") that square brackets are no longer allowed as an alternative method of creating wikilinks? No one is asking to disable the VE wikilinking methods, but no one seems to understand the insistence of the WMF on disallowing the square brackets method either.",1375350281,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #31)
+> I think that James' marking your bug as a duplicate was likely caused by his
+> misunderstanding your request. He is part of the VE team but I have met him
+> at Wikimeets a few times and I can assure you he is human.
+
+
+the last line makes me think that maybe some of my comments can be read in a way that does not fully match the spirit in which they were written.
+
+although i have criticism, especially toward the perceived attitude of VE team towards their user base, i never meant to say or hint any of them is a bad person or less than brilliant developer.
+
+as i already said in this thread, i think VE itself is a great thing, we want it, we need it, and we want it to succeed. 
+
+hope that heated and less-than-polite things said in this (and maybe other) discussions will not be taken as attacks - it is/was never the intention to attack anyone.
+
+peace.",1374758978,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #28)
+Thank you for clarifying the two requests, Chris. That was super-helpful. :-)
+
+(In reply to comment #29)
+> maybe instead of coming here, what i should have done is to reopen and remove
+> the ""duplicate"" designation. 
+
+My apologies, kipod. Thank you for patiently putting up with me. Indeed, I think bug 51897 is not a duplicate of this bug. My comments were strictly related to the original request here on bug 49686.
+
+I don't know what the VisualEditor team's view is on your request at bug 51897, so I'm going to go ahead and un-dupe bug 51897 now. Bug 51897 may also eventually be marked resolved/wontfix, but it doesn't seem to be within the scope of this bug, so it should be handled separately.",1374721119,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"I think that James' marking your bug as a duplicate was likely caused by his misunderstanding your request. He is part of the VE team but I have met him at Wikimeets a few times and I can assure you he is human.
+
+As for Bug 51899, yes that is a perfect match. Thank you.",1374712742,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"oh, and what you describe as ""the ideal solution"", sounds a lot like bug 51899 to me.
+
+peace.",1374709297,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"i think you are correct stating that these two ""definitions"" of the enhancement request are not identical.
+however, i came here to bug you guys with ""my"" definition of the request after Forrester closed  bug 51897 with ""duplicate"". the bug he closed listed my request exactly.
+maybe instead of coming here, what i should have done is to reopen and remove the ""duplicate"" designation. 
+
+my guess is that it wouldn't make a huge difference - the team would have closed it as ""WONTFIX"" instead of closing it as ""DUPLICATE"". i took them on their word about these two request being one and the same - maybe it was a mistake. (afaik, Forrester is part of VE team).
+
+as to ""[["" being ambiguous: i did not dive deeply into it, and did not conduct extensive tests, but i think that typing ""[["" anywhere on the page will cause VE to jump the ""wikicode detected"" popup. as a wikicode, ""[["" is not ambiguous at all, i think. it means ""start internal link here"".
+
+
+peace.",1374709091,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"There are at least two separate requests here. They are related in that they both want to change the current behaviour of the two character sequence ""[["" in VisualEditor but they want to change it in incompatible ways. 
+
+Kipod is asking for the key sequence [[ to be treated the same as the key sequence ctrl+k. It is not asking for, nor would it require any changes to rendering. For the purposes of this comment I'll refer to this as ""Kipod's request""
+
+MZMcBride is commenting the original request which was for the sequence [[link]] to be parsed (either at save or on the fly) as if it were a link added using the link inspector. For the purposes of this comment I'll refer to this as the ""original request"".
+
+The two are not the same and the past few posts have seen people talking past each other. 
+
+I can see the merits of the original request but I can also see where the VE team are coming from. The desire stems from people wanting the best of both worlds - they want to be able to have the structure and layout of the visual editor with the low-level control they are used to in the source editor all in one place. Long term something like this really ought to be possible, but I don't think this is the way. Rather there should be some way for the visual editor to include non-visual blobs that it sends to the parser as is without doing anything to it (other than word wrapping in the editing window); and some way for the editor to mark the start and end of such blobs. This is not what the original request is asking for though.
+
+Kipod's request is something that imho should not be included as a default, as while [[word]] or [[short phrase]] are unlikely to be anything other than links, [[ on it's own is far more ambiguous and there is more scope for the desired action to be something other than inputting a link. Rather there should either be a built-in method for users to define their own shortcuts or a simple way (an API?) for a gadget that allows users to reliably define their own shortcuts to have the same effect without needing to be rewritten every time VE or some other mediawiki component is updated. 
+
+I recommend that if anyone wants further discussion on either request that the bugs are unmerged.",1374707128,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"i still do not think you understood the request. 
+it's not about transforming [[Foo]] to a link, it's about not getting [[Foo]] into the page in the first place: as soon as the user types ""[["", the ""[["" should be removed from the page and interpreted as <Ctrl>+K.
+
+
+as to your questions about File:Foo.jpg or Category:Foo: what does VE do today when someone presses <Ctrl>+K and then feeds ""File:Foo.jpg"" or ""Category:Foo"" ?
+whatever it does today, this is what i expect it to do when someone types ""[["" and then feeds in the link form ""File:Foo.jpg"" or ""Category:Foo"".
+
+
+> (In reply to comment #25)
+> ......
+> And, of course, a certain percentage of users will want to actually include
+> brackets (""["" and ""]"") in their edits. How do they undo the magical
+> transformation?
+> 
+
+these are just straw arguments. 
+there are many many many things one can't do now using VE. it will not at all be so bad if the extremely rare case of having to add ""[["" to the page within ""nowiki"" tags will be one of them. 
+definitely much much better than current situation, where hundreds of edits with ""[["" enclosed inside ""nowiki"" tags are added to enwiki daily, when the editors actually intended to add a link (i did not count them myself - this is what i'm led to believe based on reports of editors who actually clean this mess).
+
+peace.",1374702684,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #25)
+> what we ask (at least, this is what i asked - see bug 51897, which was marked
+> as duplicate of this one) is that when the user types ""[["", VE will remove
+> the ""[["" from the page, and behave as if the user typed <Ctrl>+K, i.e. open
+> the ""Link"" form.
+
+Yep, I think everyone commenting on this bug understands the request. :-)
+
+The problem is, as stated, computers aren't very good at reading minds or understanding context. You want to support ""[["" magically transforming into a VisualEditor link. This is certainly possible to implement, but then you naturally have to support:
+
+* [[foo]]
+* [[foo]]s
+* [[foo|bar]]
+* [[w:foo]]
+* [[w:foo|]]
+* [[w:en:foo (bar)|]]
+* [[WP:FOO]]
+
+When a user types ""[[File:foo.png]]"", do they really mean they want a link to the file or do they really mean they want to include the file?
+
+What about ""[[Category:foo]]""? It's often trivial for humans to understand what we mean or to understand what other humans mean, but computers... not so much.
+
+Once we add support for [[]] magically transforming into a link, does that mean we also have to support magic words such as {{DEFAULTSORT:}}, __NOTOC__, and so on? What about ParserFunctions such as {{#time:}} and {{#if:}}?
+
+And, of course, a certain percentage of users will want to actually include brackets (""["" and ""]"") in their edits. How do they undo the magical transformation?
+
+Down this path, madness lies, I promise.
+
+> easy to do, simple, and does not go against any principle in UI design,
+> except sheer stubbornness of the VE team.
+
+The VE team has certainly exhibited some stubbornness. But I personally agree with their decision here.
+
+> unfortunately i am not able at this time to provide a patch, but 92.24% of
+> the code is already in place - just find where VE jumps the popup, and do
+> something useful instead.
+
+A patch to VisualEditor or to MediaWiki will not be accepted. However, users are welcome to create JavaScript gadgets, personal JavaScript subpages, client-side scripts (think Greasemonkey), or even implement site-wide JavaScript with appropriate community consultation and consensus.",1374701180,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"i am not sure you understand the precise nature of this request, so let me elaborate:
+
+what we ask (at least, this is what i asked - see bug 51897, which was marked as duplicate of this one) is that when the user types ""[["", VE will remove the ""[["" from the page, and behave as if the user typed <Ctrl>+K, i.e. open the ""Link"" form.
+
+simple and easy, VE already recognizes that the user typed ""[["" - all we ask is that instead of jumping less-than-useful-and-often-out-of-screen popup, VE will do something good and useful for the community, for society, and for humanity.
+
+in the same way, when the user types ""{{"", remove it from the page and behave as if she clicked on the puzzle piece, instead of jumping the less-than-useful popup.
+
+easy to do, simple, and does not go against any principle in UI design, except sheer stubbornness of the VE team.
+
+unfortunately i am not able at this time to provide a patch, but 92.24% of the code is already in place - just find where VE jumps the popup, and do something useful instead.
+
+peace.",1374690348,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #23)
+> well, in all this products, when i misspell a word, the thing silently and
+> valiantly just fix my mistake, instead of shouting at me[1]. 
+> generally, this is known as ""Auto correct"" (sometimes also [[DWIM]]: ""Do
+> What I Mean"").
+> 
+> [...]
+> 
+> when you recognize that the user did something they did not mean to do, such
+> as mispelling a word (in M$ word) or typing [[Something something]] in VE,
+> just Do What the User Meant.
+
+Computers can't read minds and they monumentally struggle with understanding context. When I type ""subst"" into OS X (as in template substitution), it autocorrects to ""subset"" because surely that's what I meant, right?
+
+I completely agree with you that [[muscle memory]] here is an issue. And I completely agree that we need to find ways to make linking as painless as possible in VisualEditor (we're not there yet). But part of meeting user expectations is to take input (such as ""[[foo]]"", which displays as ""[[foo]]"" in VisualEditor) and output it as the user saw it in the editor.
+
+These type of magical transformations won't be supported in VisualEditor and I think that's a reasonable position to take. However, it should be completely possible to create a JavaScript gadget that can enhance the user experience for those who have a deep understanding of the difference between source editing and visual editing and who would like a hybrid option. I'd pursue this. :-)",1374689458,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"please look above: in comment 15, Forrester did some namedropping: ""Microsoft
+Word, OpenOffice, Google Docs, Apple Pages and more"".
+
+well, in all this products, when i misspell a word, the thing silently and valiantly just fix my mistake, instead of shouting at me[1]. 
+generally, this is known as ""Auto correct"" (sometimes also [[DWIM]]: ""Do What I Mean"").
+
+if really you use these products as your role model, please pick the good stuff, not the crappy stuff. who cares if the shortcut for ""link"" is <Ctrl>+K or <Ctrl>+L ?
+
+why can't you adopt the real valuable features from them instead of the completely anecdotal ones?
+
+when you recognize that the user did something they did not mean to do, such as mispelling a word (in M$ word) or typing [[Something something]] in VE, just Do What the User Meant.
+
+
+peace.
+
+
+[1] i cheated - i am not actually sure if it's really ""in all those products"". i know it's in most of them.",1374688603,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"We're listening, but in this case we're saying no, and that decision is final. We can elaborate a bit more on the why if that helps, but parsing wikitext in VisualEditor is absolutely not going to happen.
+
+If accidental insertion of wikitext is still an issue, we should focus on other ways to mitigate that issue.",1374687843,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #17)
+> So, let's calm down here.
+> 
+> We're not ""pissing on"" anyone; 
+
+yes you are.
+if you look at the different wikis, and if you search here with ""product=visualeditor"" and ""search word=nowiki"", you will find that one of the main complaints of editors in many projects (specifically enwiki and nlwiki), is the fact that users type ""[[something something]]"", and VE wraps it with ""nowiki"". this is clearly not what the editor meant to do
+
+true, VE also jumps a popup message telling the editor ""this is probably not what you meant"", but there are two issues with that:
+1) because of unrelated bug, this popup message is usually not even seen by the editor.
+2) if the thing is cleaver enough to know that this is not what i meant, why can't it just Do the Right Thing (tm) ? (answer: of course it can, but the team decided to WONTFIX it).
+
+
+this attitude of VE team - pissing on and pissing off the user base at the same time, already caused the editors in nlwiki to vote not to activate it in the planned date (and they can do it - you guys removed the switch - we can bring it back through common.js or through gadgets, and we can also make it ""default"". is a fight with the user base really what you need right now?).
+
+
+why does it seem, with this and other bugs (specifically, insisting on hiding the preference to disable VE), that the VE team made a conscious (or maybe  unconscious) decision to ignore the community and shun it?
+what does the VE team expect to accomplish this way?
+
+
+we want VE and we like VE, but you guys should do a better job listening to us when we tell you where it hurts.
+
+peace.",1374687528,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Thank you very much for the clarification, Erik. I was just about to ask, following comment 17, whether this was truly a wontfix (i.e., patches will not be accepted) or whether it was simply a very low priority. :-)",1374683131,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"""other user interfaces optimized for markup"" -> ""other user interfaces optimized for completing actions quickly in VisualEditor that are fast to do in markup""",1374682618,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Sorry, but this is not something we'll ever do, as I explained in comment 9. It's not simply a matter of prioritization - it's a matter of ensuring we can provide a user experience that's not modeled on markup, but on best user experience practices. As James said, we provide keyboard shortcuts, and will provide other user interfaces optimized for markup. But parsing markup within the visual editing context is completely off the table.",1374682548,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"So, let's calm down here.
+
+We're not ""pissing on"" anyone; we're choosing to prioritise. Right now the devs have got a lot of open bugs for the VisualEditor - things that actively /don't work/. They've got a lot of features still to build, and a lot of expectations about the project. Personally, I'm incredibly impressed with the speed of change and the patches that have been submitted so far - it's a fantastic workrate. But that doesn't change the fact that there's still a lot to do.
+
+Now: we /can/ have wikitext converted to VE-compatible elements. But there are a few costs. First: from my conversations with the developers, I understand that doing it on the fly would slow the VE down very substantially. You'd have to automatically parse and re-render the page. Second: if they work on this, there's a lot of stuff that is going to get pushed back.
+
+We have a VisualEditor. It's great, it's miles better than anything else produced to do this job in MediaWiki, but it still needs a lot of work and still has a lot of active bugs - problems parsing content, problems rendering content. If enhancements such as this (which would certainly be nice) are worked on, active breakage will take a back seat: those areas where it simply doesn't have features will take a back seat. I'm not comfortable with saying that we rate ""being able to type markup into the VisualEditor"" higher than ""being able to manipulate tables"".
+
+As you note, the source editor is still available in all namespaces. Users who are actively prioritising familiarity with syntax, and their muscle memory, are welcome to use it. It's not going away. In the meantime, the VE development process should be focused on making it work full stop, not making it work for the users who are highly comfortable with source editing. That's nice, and it's something I'd love to see, but it's not going to happen if actual bugs aren't fixed first.",1374681807,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #15)
+> If you want an ""accelerator key"" for making links, use the standard one:
+> Ctrl +
+> K (or Cmd + K if you're on a Mac). This is the same shortcut as in Microsoft
+> Word, OpenOffice, Google Docs, Apple Pages and more.
+
+and ""[["" is the same one as used by tens of thousands of wikipedia editors.
+it's not even ""a thing of the past"" - source editor remains the only editor in many name spaces, and is still available in _all_ of them.
+
+pissing on your user base is not a good way to handle software projects.
+
+peace.",1374681409,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"If you want an ""accelerator key"" for making links, use the standard one: Ctrl + K (or Cmd + K if you're on a Mac). This is the same shortcut as in Microsoft Word, OpenOffice, Google Docs, Apple Pages and more.",1374679580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**turingt** wrote:
+
+For what it's worth, I find that ""[["" is a very good accelerator key - mainly because it's already known and remembered by a huge portion of your user base, myself included.
+
+And Erik, wikitext is still awesome today - it's the only known way to allow users to create semantic-enhanced content. The VisualEditor is good for laying out formatted text on a page, but the relations between concepts placed at different pages are better created by adding tags (links, categories, templates...) to the content. The current VE interface mostly hides those tags and requires handling complex dialogs to introduce or edit them, which makes it less convenient for introducing semantics than wikitext. That's why people is requesting smoother and seamless ways to switch between the VE and the source editor.",1374678026,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"based on:
+
+bug 51554
+bug 51944
+bug 51462
+bug 50527
+
+and a dozen or so more (as seen here:
+https://bugzilla.wikimedia.org/buglist.cgi?query_format=specific&order=relevance%20desc&bug_status=__open__&product=VisualEditor&content=nowiki&list_id=219956
+
+
+i changed this one to ""reopen"" and marked it ""high"".
+
+peace.",1374671097,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,*** Bug 51897 has been marked as a duplicate of this bug. ***,1374639183,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**nrp** wrote:
+
+WTG guys, piss off the user base even more with a WONTFIX on a no-brainer...",1374599335,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,Marking as WONTFIX per my earlier comments and Erik's.,1373002882,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Indeed, I think we should close this as WONTFIX. We should improve any efficiency or discoverability issues in VisualEditor, and help give users experienced with wikitext clues to not accidentally insert it in VisualEditor. See bug 50601 for one potential approach to the latter problem.
+
+Wiki markup was an awesome in invention in 1995, helping users not have to type HTML in order to format documents. But that doesn't mean the most efficient conceivable user experience in 2013 ought to be bound to the same design principles. (Nor should we blindly copy existing point and click interfaces -- for navigating the complexity of templates and such, we may have to come with some truly novel interfaces.)",1372986063,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #7)
+> (In reply to comment #6)
+> > > (2) it requires the use of a mouse to add a link. :-(
+> > 
+> > Not true, as discussed; I don't use the mouse to add links with VE (Ctrl+K
+> > plus keyboard-based selection, as in other editors).
+> 
+> Ah, right. I vaguely remember that cmd-K controls the hyperlink functionality
+> in Microsoft Office products. I have no idea how anyone would glean this from
+> VisualEditor.
+
+Hover over the button; the tooltip tells you the keyboard shortcut. :-)",1372016154,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #6)
+>> (2) it requires the use of a mouse to add a link. :-(
+> 
+> Not true, as discussed; I don't use the mouse to add links with VE (Ctrl+K
+> plus keyboard-based selection, as in other editors).
+
+Ah, right. I vaguely remember that cmd-K controls the hyperlink functionality in Microsoft Office products. I have no idea how anyone would glean this from VisualEditor.",1372016115,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #5)
+> (In reply to comment #4)
+> > I'm ambivalent about whether we would ever let this go live, given how
+> > complicated it would make editing for people that don't know wikitext -
+> > consequently, marking as lowest priority for now.
+> 
+> You and I discussed this idea at some point (thanks for filing this as a bug,
+> Oliver). The current issues I'm seeing with VisualEditor are that:
+> 
+> (1) it's much more time-consuming to add a link (i.e., typing ""[[]]"" is quick
+> while finding and using the link dialog box is slow, especially multiple
+> times); and
+> 
+> (2) it requires the use of a mouse to add a link. :-(
+
+Not true, as discussed; I don't use the mouse to add links with VE (Ctrl+K plus keyboard-based selection, as in other editors).
+
+> Perhaps we need a ""I'm old school"" checkbox somewhere in VisualEditor. ;-)
+
+If users are sufficiently new-school that they can't remember Ctrl+K I don't think there's much hope for them. :-)",1372015941,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #4)
+> I'm ambivalent about whether we would ever let this go live, given how
+> complicated it would make editing for people that don't know wikitext -
+> consequently, marking as lowest priority for now.
+
+You and I discussed this idea at some point (thanks for filing this as a bug, Oliver). The current issues I'm seeing with VisualEditor are that:
+
+(1) it's much more time-consuming to add a link (i.e., typing ""[[]]"" is quick while finding and using the link dialog box is slow, especially multiple times); and
+
+(2) it requires the use of a mouse to add a link. :-(
+
+Adjusting VisualEditor to interpret [[]] as a link would be a nice enhancement, though I see the danger in heading down this road.
+
+Perhaps we need a ""I'm old school"" checkbox somewhere in VisualEditor. ;-)",1372015712,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"I'm ambivalent about whether we would ever let this go live, given how complicated it would make editing for people that don't know wikitext - consequently, marking as lowest priority for now.",1372015077,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Another possibility I mentioned in bug 49820 is to display a warning of some sorts to remind people that wikicode isn't supported (similar to how LiquidThreads reminds users who insert ~~~~ that their signature will be automatically inserted). Automagical conversion might be better, but a warning could be a good first step.",1371929384,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Sorry, just clarifying, this wasn't intended to happen ""on save"". This should probably happen as soon as (e.g.) the ]] is typed after a link, à la AutoCorrect.",1371721105,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #0)
+> a user has suggested
+
+This was me. Here's my comment from [[Wikipedia:VisualEditor/Feedback]]:
+
+> If you look through many of the comments on this page (in some cases you 
+> need to read between the lines), you will see that people are trying to 
+> create a wikilink in VisualEditor using [[ ]] wikitext syntax. I am 
+> suggesting that, to accommodate these users, a sort of autocorrect be 
+> implemented, so that when [[ ]] links are entered, they are automagically 
+> converted into proper VE-style links
+
+As well as a helpful ""transition"" feature from wikitext to VE, it might also be useful in the long run as a shortcut for power users, since keystrokes are generally faster than mouse interaction.
+
+Probably a lower priority enhancement though :)",1371523456,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: Some template combinations make text not editable,"On Swedish Wikipedia, we have quite a few bot generated articles (some hundreds of thousands) like this one: https://sv.wikipedia.org/wiki/Macrothemis_ultima
+
+When in editing mode, somehow the first line of text cannot be edited. 
+
+If an article has a second line, it is possible to edit that one (but still not the first line), e.g. https://sv.wikipedia.org/wiki/Lepidosaphes_lithocarpi
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371462960,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-zgrdvieu55b7ilh6yt3l,task_description,resolved
+VisualEditor: Some template combinations make text not editable,Sorry for the disruption; glad we fixed it for you.,1371825507,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zgrdvieu55b7ilh6yt3l,task_subcomment,NA
+VisualEditor: Some template combinations make text not editable,"No, I cannot reproduce it anymore. The update must have taken care of it!",1371538774,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-zgrdvieu55b7ilh6yt3l,task_subcomment,NA
+VisualEditor: Some template combinations make text not editable,"I cannot reproduce this, but we did just update production to the latest code - do you still get this effect?
+
+If so, what browser/OS are you using? Is it possible to do a quick screencast video of how it doesn't work, and attach it to this bug? Thanks!",1371520067,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zgrdvieu55b7ilh6yt3l,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"[From bug 48429 comment 18]
+
+| It would be ideal to have section-edit links for [edit] and [edit source].
+| ie.
+|   Sandbox [edit]
+| replaced with:
+|   Sandbox [edit] [edit source]
+| 
+| I believe this would prevent a LOT of complaints in the short term, and it
+| would permit a lot of us to continue being active beta testers
+| (section-editing is my most frequent type of edit), that it should be High
+| priority, if at all possible. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48429
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49621
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47779
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56337",1371430320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_description,resolved
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Saying it is fixed does not make it fixed. The link is hidden, and so I don't consider it ""displayed"" as per the current title of this bugzilla thread: ""VisualEditor: Display a link to both VE and wikitext editor on every section header"".
+
+And you did not address my points. I don't want to start another Bugzilla thread, and have to repeat everything there that was written here. Several people in this thread pointed out their dislike of multi-stage processes to be able to click an ""edit source"" link. 
+
+I am concerned about anonymous editors. I know at some point it is likely an option will be provided in preferences to provide registered editors with a direct ""edit source"" link and/or clickable icon (maybe with explanatory tooltip).
+
+But unless a direct ""edit source"" and/or clickable icon link is provided to anonymous editors, then some anonymous editors will edit less. Just like I edited less today, and almost quit editing altogether for the day, due to my annoyance with this multi-stage method, and the many times I messed up.
+
+The point of the visual editor is to get people to edit more, not less. It should not get in the way of editing. It should aid editing. 
+
+Wikia refused to provide registered editors an option to put the source editor tab on top of the visual editor tab. So people had to do a multi-stage process for every single edit in order to get to the source editor. Click edit, then wait tediously for visual editor to load, then click the source tab. For every edit... So many, if not most, regular editors disabled the visual editor in preferences. Feedback and bug reports lessened, especially the best feedback from the best editors. 
+
+Similar to here now. I have to use a multi-stage process to get to the source editor. Aim at ""edit"" link or the line it is on, mouse over that ""edit"" link or line, aim better if necessary, wait for ""edit source"" link to show up, move mouse over to that link, click. Many times I accidentally, or by habit, click the edit link, and then have to click the back button, and start over. So I have to disable the Visual Editor. 
+
+Here is a possible icon method. ""Edit source"" tooltip can show up after mousing over the icon. And the small icon can have a transparent left and right border that makes the area wider for mousing over. So people will have no problem understanding that the icon is an ""edit source"" link. The visible part of the icon will be small, similar in size to the watchlist star at the top of pages. But the clickable part would extend to the left and right a bit to allow easier clicking.",1372374914,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"This matter is fixed. If you want to suggest additional/alternative implementations, please open a new feature request, not re-open a closed one.",1372362973,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Edit and edit source links so confusing I had to disable Visual Editor in preferences today. So you have lost another beta tester. A good one too since I have written many comments and bug reports about VE here and on the Wikipedia feedback page.
+
+I disabled Visual Editor (VE) in preferences today due to constantly clicking the ""edit"" link instead of the ""edit source"" link. I am talking about section editing.
+
+The source editing link only shows up after unintuitively mousing over the edit link and so I am constantly clicking the wrong link. 
+
+I almost always prefer editing with the source editor since I make frequent edits to tables, images, navboxes, templates, and reference formatting. All at a deep level of formatting, placement, refactoring, etc.. I am very fast in the source editor, and VE only edits partially and poorly at deeper levels, if at all.  
+
+It would be better to use an icon for the ""edit source"" links for sections. For ideas:
+*[[commons:User:Timeshifter/Sandbox 10]]
+*[[commons:Category:Square brackets]]
+*[[commons:Category:MediaWiki brackets]]
+
+""edit source"" can show up after mousing over the icon. That is much more intuitive. I did not notice the ""edit source"" link at all for awhile, since I was rapidly clicking the edit link. 
+
+This could drive away many editors. Anonymous editors especially. They have no ability to fix the problem by turning off visual editor in preferences. Many anonymous editors just do not like to log in, and are very used to editing in source editor. Some will be very irritated by the confusing clicking and mousing, just like me.",1372360425,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"**swalling** wrote:
+
+(In reply to comment #22)
+> I was doing my volunteering editing at http://ca.wikipedia.org when all of a
+> sudden I realized the new section double-editing links... 
+> 
+> Well done! I'm glad about everything I said against them, but it is true that
+> I'm also glad about your implementation. A good bridge indeed.
+
+
++1. If we have to live with both edit/edit source for now, this is a pretty elegant implementation.",1372313035,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,Huge thanks. This looks and acts wonderfully.  A good mix of minimal-visuals and maximal-options. Much <3,1372312986,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"I was doing my volunteering editing at http://ca.wikipedia.org when all of a sudden I realized the new section double-editing links... 
+
+Well done! I'm glad about everything I said against them, but it is true that I'm also glad about your implementation. A good bridge indeed.",1372312829,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"This was done in gerrit 69984 which is now merged and will go out this afternoon. Thanks, MatmaRex!",1372279613,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,*** Bug 49950 has been marked as a duplicate of this bug. ***,1371827708,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Edit. Edit source [[]].
+
+Edit. [[]].
+
+-----------------
+
+Edit source [[]]. - At the top of the page. This should be one link covering both the text and the icon. 
+
+That way people are introduced to the shortcut icon for ""edit source"". One possibility: [[]]
+
+Headers will have just the shortcut icon link for ""edit source"": [[]]
+
+Some possibilities for the icon are found here:
+*[[commons:User:Timeshifter/Sandbox 10]]
+
+The graphics lab can quickly produce different icons and variations: 
+*[[Wikipedia:Graphics Lab]]
+*[[Wikipedia:Graphics Lab/Illustration workshop]]",1371747210,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Using an arrow is unintuitive and confusing (no indication what the arrow is actually for; can cause the user to expect the word next to it to be the label for the dropdown, not a separate option entirely especially given the way such arrows operate elsewhere in the skin; results in an extra step/click for something that really might as well be right there; etc). Also doesn't make sense when there are only two options anyway. Just do what James said at the beginning and put in two links.
+
+Later they can stick the edit source option into a tab or something in VE itself, but for now there is no reason to overcomplicate things elsewhere. 
+
+Good:
+
+Sandbox [edit] [edit source]",1371743257,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #7)
+> (In reply to comment #6)
+> > I like this idea.  It would be nice if it worked for at least Monobook (in
+> > addition to Vector).
+> 
+> Completely agree. Not sure quite whether this treatment is suitable for
+> Monobook or whether we should invent a different one there?
+
+The section edit links look the same in all skins, this shouldn't look bad. Monobook already has some Vector-y bits tacked on top and this would be just a small icon.
+
+
+(In reply to comment #10)
+> There are also a lot of section edits on most large articles, sometimes in
+> close succession. I think we should be really cautious about enabling
+> multi-level controls and options on something this ubiquitous on a single
+> page.
+
+I'm afraid this doesn't support your argument :)
+
+Only showing one link will prevent users from editing sections of wikitext until they learn to disable the option (or just disable VE entirely), which has been my point all along. Wikitext section editing is the ""default"" mode of operation for many users (at a quick glance at recent changes, around 30-50% of en.wp edits are section edits) and it'd be awful for VE to make it unaccessible.",1371543971,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"I like these bracket icons for the edit source links on headers: 
+[[commons:User:Timeshifter/Sandbox 10]]",1371529452,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #14)
+> The only other short options would be [edit (source)] or [edit (code)], but
+> they're not perfect.
+
+The main problem with that route (which I should have listed, sorry) is that though ""Edit (source)"" works OK in English, it's not a safe expectation for non-English languages to be able to split the actions into two call-to-action labels, one of which is a left sub-string of the first, sadly. Also, it's a bit clunky.",1371527558,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"I agree with James and Matthew on this. 
+
+A preferences toggle, is for things you want to change permanently. 
+
+Whereas this is an instance where I might use VE-section-edit, and use source-section-edit, many times each day, for many months to come.
+
+I really like the arrow-dropdown idea. The cog idea is also good, but would be my second choice. 
+
+The only other short options would be [edit (source)] or [edit (code)], but they're not perfect.",1371521986,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #11)
+> (In reply to comment #8)
+> > Personally I think one of these two are the only viable options. The dropdown
+> > arrow or cog is too much unnecessary choice.
+> 
+> I was assuming if you just click 'edit', it would do the same thing as
+> clicking 'edit' up top (i.e. VE for those users with VE enabled).  Only if 
+> you click the arrow would you see the choice.
+
+Yes, that's exactly our plan - sorry if this wasn't clear. It's available, but not intrusive, and if you click the word ""edit"" link you'll end up in VE at that section.",1371521707,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #11)
+> I was assuming if you just click 'edit', it would do the same thing as
+> clicking 'edit' up top (i.e. VE for those users with VE enabled).  Only if you 
+> click the arrow would you see the choice.
+
+If we do want to avoid the drop-down for non-power users, one idea is to have the preference be like this (possible default shown)
+
+[✓] Show VisualEditor section link
+[ ] Show wikitext section link
+
+You could check either, both (in which case you get some control for choosing, possibly the drop-down), or neither (no section links, which is already an option).",1371521678,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #8)
+> Personally I think one of these two are the only viable options. The dropdown
+> arrow or cog is too much unnecessary choice.
+
+I was assuming if you just click 'edit', it would do the same thing as clicking 'edit' up top (i.e. VE for those users with VE enabled).  Only if you click the arrow would you see the choice.
+
+> Most new editors will appreciate defaulting to VE, and
+> for power users who need edit source, this is where having a preference to 
+> change your default to edit source would come in handy (a preference I am 
+> guessing would free us up to also move ""Edit source"" at the top of the page in 
+> to a dropdown).
+
+As a power user, I agree with James.  Having both available on every section greatly increases the odds I'll continue to test VE when possible (and report bugs), while using wikitext when I know I have to.  Having power users opt out for all VE section edits is not conducive to that.",1371521421,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"**swalling** wrote:
+
+(In reply to comment #9)
+> (In reply to comment #8)
+> > > * ""[edit]"" going to one place unless you've got a preference in which case it
+> > > goes to another is… confusing
+> > > 
+> > > * ""[edit]"" OR ""[edit source]"" if you've got a preference is a bit messy, but
+> > > not that bad
+> > 
+> > Personally I think one of these two are the only viable options. The dropdown
+> > arrow or cog is too much unnecessary choice. The point of section edit links
+> > is to enable speedy editing of single sections, so introducing a dropdown is
+> > overloading things. Most new editors will appreciate defaulting to VE, and
+> > for power users who need edit source, this is where having a preference to
+> > change your default to edit source would come in handy (a preference I am
+> > guessing would free us up to also move ""Edit source"" at the top of the page in
+> > to a dropdown).
+> 
+> I disagree. I would say that, as an axiom, preferences are bad; they add
+> complexity for coders (expensive), bug testers (irritating) and most
+> importantly users (alienating).
+> 
+> In this case, we would also lose momentum as many power users might early-on
+> opt out of VisualEditor for section edits, and so never use it as much as
+> we'd
+> hope. We would lose their input, their bug reports and most importantly their
+> enculturation for new users of this being the 'right' way to edit. We don't
+> want another Vector roll-out disaster on our hands; ever day that Monobook
+> remains on the servers is another notch on that failure yardstick. :-(
+
+On the other hand, you potentially distract and confuse the heck out of new users by presenting a dropdown to edit source when they were about click edit. The conceptual difference between ""edit"" and ""edit source"" is not crystal clear to people who don't know the differences between VE and wikitext up front. 
+
+There are also a lot of section edits on most large articles, sometimes in close succession. I think we should be really cautious about enabling multi-level controls and options on something this ubiquitous on a single page.",1371521332,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #8)
+> > * ""[edit]"" going to one place unless you've got a preference in which case it
+> > goes to another is… confusing
+> > 
+> > * ""[edit]"" OR ""[edit source]"" if you've got a preference is a bit messy, but
+> > not that bad
+> 
+> Personally I think one of these two are the only viable options. The dropdown
+> arrow or cog is too much unnecessary choice. The point of section edit links
+> is to enable speedy editing of single sections, so introducing a dropdown is
+> overloading things. Most new editors will appreciate defaulting to VE, and
+> for power users who need edit source, this is where having a preference to
+> change your default to edit source would come in handy (a preference I am
+> guessing would free us up to also move ""Edit source"" at the top of the page in
+> to a dropdown).
+
+I disagree. I would say that, as an axiom, preferences are bad; they add complexity for coders (expensive), bug testers (irritating) and most importantly users (alienating).
+
+In this case, we would also lose momentum as many power users might early-on opt out of VisualEditor for section edits, and so never use it as much as we'd hope. We would lose their input, their bug reports and most importantly their enculturation for new users of this being the 'right' way to edit. We don't want another Vector roll-out disaster on our hands; ever day that Monobook remains on the servers is another notch on that failure yardstick. :-(",1371520516,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"**swalling** wrote:
+
+
+> * ""[edit]"" going to one place unless you've got a preference in which case it
+> goes to another is… confusing
+> 
+> * ""[edit]"" OR ""[edit source]"" if you've got a preference is a bit messy, but
+> not that bad
+
+Personally I think one of these two are the only viable options. The dropdown arrow or cog is too much unnecessary choice. The point of section edit links is to enable speedy editing of single sections, so introducing a dropdown is overloading things. Most new editors will appreciate defaulting to VE, and for power users who need edit source, this is where having a preference to change your default to edit source would come in handy (a preference I am guessing would free us up to also move ""Edit source"" at the top of the page in to a dropdown).",1371520133,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #6)
+> I like this idea.  It would be nice if it worked for at least Monobook (in
+> addition to Vector).
+
+Completely agree. Not sure quite whether this treatment is suitable for Monobook or whether we should invent a different one there?",1371519315,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,I like this idea.  It would be nice if it worked for at least Monobook (in addition to Vector).,1371516381,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Having discussed, we think we've found a design that's consistent with other usage: instead of having ""[edit | edit source]"" or ""[edit ⚙]"", we will have ""[edit ▾]"" with the down-arrow expanding to a menu (in the same way that Vector does) for ""edit source""). This is still easily accessible for users and open for all users, not just those with a preference, but does not take lots of screen estate (problem with the first possibility), and is easily discoverable (second possibility).",1371515280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #3)
+> I like ""[edit ⚙]"" more - what do you think? MatmaRex discussed this with me
+> last night.
+
+So if you click 'edit', it always goes to VE, and if you click ⚙ (first time I saw the 'gear' character, but good usage), it always goes to wikitext?
+
+That seems reasonable if the wikitext target is big enough that it's not frustrating to click.",1371499202,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #2)
+> There is much discussion at bug 48429 about the need for both types of edit
+> links on every header. 
+> 
+> What might also work is an ""edit"" link (for VisualEditor) and an icon that
+> when
+> clicked will take one to the source editor for that section. The icon would
+> have a popup tooltip that says ""edit source"". It would show up when the mouse
+> cursor is run over the icon.
+
+My concern with this area is three fold:
+
+* ""[edit] [edit source]"" is a huge amount of extra chrome/clutter to enable for all users
+
+* ""[edit]"" going to one place unless you've got a preference in which case it goes to another is… confusing
+
+* ""[edit]"" OR ""[edit source]"" if you've got a preference is a bit messy, but not that bad
+
+I like ""[edit ⚙]"" more - what do you think? MatmaRex discussed this with me last night.",1371498837,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"There is much discussion at bug 48429 about the need for both types of edit links on every header. 
+
+What might also work is an ""edit"" link (for VisualEditor) and an icon that when clicked will take one to the source editor for that section. The icon would have a popup tooltip that says ""edit source"". It would show up when the mouse cursor is run over the icon.",1371472595,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"See comment 23 and 24, at Bug 48429 wherein Bartosz Dziewoński has submitted a patch to Gerrit.
+
+(""https://gerrit.wikimedia.org/r/68868 (Gerrit Change
+I13bbb9549c999bb7301bbcf530706a813184425d)"")
+
+If his patch isn't accepted, then I would again urge High Priority for an alternative fix.",1371431206,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,"In general, ""everything"" is allowed (text; annotations; inline and block images; headings; lists; HTML blocks; entities; transclusions; references; etc.), except for:
+
+Image captions
+-> No lists
+
+References
+-> No references (but transclusions of {{#tag:ref|text}} get around this for one level as an out ref; eww)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50459",1371422340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-osst63lnijz6dlmc57xi,task_description,resolved
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,This was completed by the toolbar re-write that was merged for the 12 September release; moving bug 50459 from a blocker (which was wrong anyway) to a see-also.,1379657458,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-osst63lnijz6dlmc57xi,task_subcomment,NA
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,"The references dialog has no references button already. Not sure about image captions as their broken on my local copy, but the code is there to specify the toolbar for each dialog.",1371816425,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-osst63lnijz6dlmc57xi,task_subcomment,NA
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,"Re references: yeah, that struck me as highly likely to confuse people (and highly unnecessary) when I saw it.",1371535012,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-osst63lnijz6dlmc57xi,task_subcomment,NA
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,"Examples for captions:
+
+https://www.mediawiki.org/wiki/VisualEditor:TestImageCaptions
+
+Examples for references:
+
+https://www.mediawiki.org/wiki/VisualEditor:TestReferenceContents",1371422391,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-osst63lnijz6dlmc57xi,task_subcomment,NA
+Show change tags on edit diff views,"From bug 49602 comment 0:
+
+| 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).
+
+This is said request for a core change for this to be possible. :-)
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1371419460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-acs2ekfum76g27vb7duj,task_description,resolved
+Show change tags on edit diff views,"
+
+%%%*** This bug has been marked as a duplicate of bug 25824 ***%%%",1373019604,PHID-USER-lptfllsuhn22a4praqqo,PHID-TASK-acs2ekfum76g27vb7duj,task_subcomment,NA
+VisualEditor: Make some way to display display-less content (e.g. silent transclusions like {{lowercase title}}),"https://en.wikipedia.org/wiki/User:%C3%8F%C2%BF%C2%BD?veaction=edit
+
+If a template has no output (such as <https://en.wikipedia.org/wiki/Template:Lowercase_title>), it has no visible output and becomes very easy to silently remove using VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49667",1371357660,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-uoptaiss5vhdq32dkswe,task_description,resolved
+VisualEditor: Make some way to display display-less content (e.g. silent transclusions like {{lowercase title}}),"(In reply to comment #2)
+> Is this the same as bug 49806? (I know that's newer but it has a lot more
+> discussion)
+
+It is indeed; merged.
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1374086311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uoptaiss5vhdq32dkswe,task_subcomment,NA
+VisualEditor: Make some way to display display-less content (e.g. silent transclusions like {{lowercase title}}),Is this the same as bug 49806? (I know that's newer but it has a lot more discussion),1374084075,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-uoptaiss5vhdq32dkswe,task_subcomment,NA
+VisualEditor: Make some way to display display-less content (e.g. silent transclusions like {{lowercase title}}),"I don't see how this is an enhancement request. It's trivial to accidentally remove a template that has no output, resulting in damage to the page (irreversible damage in the context of using only VisualEditor).",1371441632,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-uoptaiss5vhdq32dkswe,task_subcomment,NA
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,"https://en.wikipedia.org/wiki/Digital_Forensics_XML?veaction=edit
+
+I went there, I changed a header from h3 to h2 by selecting the header and using the drop-down menu. When I click ""Page settings"" and then close the dialog box without making any changes, my change to the header is inexplicably lost.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371355920,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-zuh52jc2toouqelcucf4,task_description,resolved
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,Merged and will go out with wmf8.,1371584527,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zuh52jc2toouqelcucf4,task_subcomment,NA
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,Related URL: https://gerrit.wikimedia.org/r/69316 (Gerrit Change Ieb2e9e361afe057af93c4d374acc85df58bfb4c3),1371571111,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zuh52jc2toouqelcucf4,task_subcomment,NA
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,"Not quite, it's just doing it without checking if a new breakpoint was actually added.",1371571069,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zuh52jc2toouqelcucf4,task_subcomment,NA
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,"This looks like the code to ""undo changes made in the dialog when they don't apply them"" is doing that once too often.",1371431146,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zuh52jc2toouqelcucf4,task_subcomment,NA
+VisualEditor: mw:Placeholder issue,"If there are 2 blank lines (line breaks) then the paragraph immediately after is uneditable (green striped overlay).
+
+Confirm here: http://en.wikipedia.org/w/index.php?title=User:Quiddity/sandbox&oldid=560048320
+
+and see thread here: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Paragraph_editing_disabled.3F.3F.3F
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371319260,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-oe6mridn2bnwc6ynf3en,task_description,resolved
+VisualEditor: mw:Placeholder issue,This now works; you won't get blank lines causing the next line to be unable to be edited. Thanks for the bug report!,1371516882,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oe6mridn2bnwc6ynf3en,task_subcomment,NA
+VisualEditor: mw:Placeholder issue,This (and similar issues if you have an HTML comment on a paragraph double-line  before some content) is caused by bug 47403; I won't mark this as a duplicate of that one because we're still trying to get a comment as to what will break in VE if Parsoid reverts the hack that causes this.,1371425386,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oe6mridn2bnwc6ynf3en,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"VisualEditor should display HTML comments, which are often used as notes or warnings to other editors.  It would be nice if they were editable too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49608
+https://bugzilla.wikimedia.org/show_bug.cgi?id=46440
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49806
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53659",1371261360,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nvkr7m44ao53f5uftwjr,task_description,resolved
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Change 140773 merged by jenkins-bot:
+[BREAKING CHANGE] Show comments inline to the user
+
+https://gerrit.wikimedia.org/r/140773",1406160260,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Change 140773 had a related patch set uploaded by Jforrester:
+[WIP] Show comments inline to the user
+
+https://gerrit.wikimedia.org/r/140773",1403205835,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),*** Bug 52036 has been marked as a duplicate of this bug. ***,1393271493,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),*** Bug 51732 has been marked as a duplicate of this bug. ***,1390416862,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(And of course, this means comments can not be easily deleted right now, in case they display obsolete information, for example.)",1379933298,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"It should go without saying, but another consequence of this, beyond the comment being ignored, is that it can easily be misplaced, ending up in places where it does not belong and it does not make much sense, as user:Fram points out at en.wp today.",1379932587,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"I've just discovered that, at present at least, <!-- blah --> does not get nowikied so html comments are creatable in VE but not visible once saved so this functionality really very useful yet.
+Other HTML tags do get nowikied so this behaviour may subsequently change - see [[Wikipedia:VisualEditor/Feedback#HTML comments not nowikied - should they be?]]",1378460438,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Like Pam I think it is best that these notices are visible and in-your-face so there is no doubt that you have seen them. Hover also causes issues on touch screen devices I think.
+
+One thing that would be possible would be for there to be an icon associated with the comment that collapsed it to get a more WYSIWYG view (and then expanded it again on a subsequent click). The default display would be shown. I guess that custom css/js to have them hidden by default would be possible if people wanted, but I don't suggest the devs do anything other than make it possible for users to write this. I don't know how difficult any of this would be to program though.
+
+On the issue of rendering, I know that some comments contain links, for example from [[Patrick Stewart]]: <!--Do not change this to KBE, see [[Knight Bachelor]]-->
+Obviously this is shown like any other link in the source editor, but it makes it clear that it is a link to an article and people with navpopups can select it and get a preview of the link. If VE could parse links (and I guess external links) then that would be a nice to have.",1377774240,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #18)
+> I agree with James Forrester that this should be done in stages, and that the
+> first stage would be to ""show comments and let them be deleted.
+> 
+> In terms of isolating hidden (aka ""invisible"") comments, the logic is pretty
+> much the same as for templates, except easier: look for <!-- as the left
+> boundary, then look for --> as the right boundary. Treat the result as a
+> block
+> that can be deleted or moved.
+> 
+> Looking at https://en.wikipedia.org/wiki/Help:Hidden_text , it's not clear
+> that
+> text within an invisible comment is essentially nowikied, but that is in fact
+> the case, because - by definition - the text can't be seen in either read or
+> preview mode. From a programming viewpoint, this means that even if, for
+> example, there is an http link within the comment, or a reference - both
+> quite
+> possible - no rendering is needed: all text should be treated as text, NOT
+> interpreted.
+> 
+Of the two options I would be much happier with (1): in many circumstances these comments need to be obvious to the naive editor, who will not necessarily have the savvy or curiosity to hover over an icon. Please display these comments clearly on screen for all editors, at the point in the article where they have been inserted: different font on coloured background sounds good.
+
+> What the person doing the edit sees is really the critical question. It seems
+> to me that there are two options:
+> 
+> (1) Display as a text, mixed in with regular text, but in a different color
+> font and background color. This is what is done with templates. Regarding the
+> color: Hidden comments are typically warnings/notices to editors, so perhaps
+> yellow? The font/coloring will, ideally, make it clear that the text is not
+> part of the article. 
+> 
+> (2) Treat like a comment in Excel - put a character (I suggested a warning
+> icon
+> - see http://findicons.com/search/warning; in yellow) into the visible text
+> that, when a person hovers on the icon, displays the hidden/invisible text.
+> While this is less visible to editors, in some sense - they have to hover to
+> read - it's more visible in the sense that hidden comments, in wikitext
+> editing
+> mode, are in the same font as everything else, and thus less likely to be
+> noticed than a bright yellow warning icon.
+> 
+> Option (2) lends itself nicely to the second phase mentioned by James: Here
+> there would be an icon on the toolbar, for adding a new comment. In addition,
+> if a person hovers over an existing comment, then an editing icon appears
+> nearby, which allows the person to edit the comment or to delete it [via
+> trashcan icon].",1377758963,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #18)
+> In terms of isolating hidden (aka ""invisible"") comments, the logic is pretty
+> much the same as for templates, except easier: look for <!-- as the left
+> boundary, then look for --> as the right boundary. Treat the result as a
+> block that can be deleted or moved.
+
+The parsing part is solved.  Comments are already preserved (as HTML comments) in the Parsoid DOM.",1377752273,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"I agree with James Forrester that this should be done in stages, and that the first stage would be to ""show comments and let them be deleted.
+
+In terms of isolating hidden (aka ""invisible"") comments, the logic is pretty much the same as for templates, except easier: look for <!-- as the left boundary, then look for --> as the right boundary. Treat the result as a block that can be deleted or moved.
+
+Looking at https://en.wikipedia.org/wiki/Help:Hidden_text , it's not clear that text within an invisible comment is essentially nowikied, but that is in fact the case, because - by definition - the text can't be seen in either read or preview mode. From a programming viewpoint, this means that even if, for example, there is an http link within the comment, or a reference - both quite possible - no rendering is needed: all text should be treated as text, NOT interpreted.
+
+What the person doing the edit sees is really the critical question. It seems to me that there are two options:
+
+(1) Display as a text, mixed in with regular text, but in a different color font and background color. This is what is done with templates. Regarding the color: Hidden comments are typically warnings/notices to editors, so perhaps yellow? The font/coloring will, ideally, make it clear that the text is not part of the article. 
+
+(2) Treat like a comment in Excel - put a character (I suggested a warning icon - see http://findicons.com/search/warning; in yellow) into the visible text that, when a person hovers on the icon, displays the hidden/invisible text. While this is less visible to editors, in some sense - they have to hover to read - it's more visible in the sense that hidden comments, in wikitext editing mode, are in the same font as everything else, and thus less likely to be noticed than a bright yellow warning icon.
+
+Option (2) lends itself nicely to the second phase mentioned by James: Here there would be an icon on the toolbar, for adding a new comment. In addition, if a person hovers over an existing comment, then an editing icon appears nearby, which allows the person to edit the comment or to delete it [via trashcan icon].",1377735584,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"resetting priority to high. I didn't intend to change it and didn't realise I had, sorry.",1377724382,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"John Broughton suggests as a first step that hidden comments could very easily be made visible but not editable. He suggests putting the comments in a different colour, possibly white on black, to distinguish them from regular content.
+
+Obviously being able to edit hidden comments is needed functionality too, but that is less urgent than displaying them.",1377724285,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"It has been reported on en.wp today that a user of VE was:
+[..] continually making changes to articles contrary to comments in the wikisource (''two examples of such comments being ""<!-- DO NOT CHANGE THIS NATIONALITY WITHOUT DISCUSSION ON TALK PAGE -->""  and ""<!-- This is, as Wikipedia guidelines suggest, as he self-identifies and by long-term consensus -->"")
+
+This bug is already marked as high priority and has been for over 2 months. It really needs to be fixed before much longer.",1377721939,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"**ignatzmice.wiki** wrote:
+
+Bump. https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=567981801",1376162739,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Another example: http://en.wikipedia.org/w/index.php?title=Jacques_Lacan&diff=566246717&oldid=561090875 We are getting multiple reports about this specific issue, so thanks for your attention on this.",1375547447,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Example of edit where displaying the hidden comment would have been very useful (because the edit goes against what is stated in the comment) :
+http://en.wikipedia.org/w/index.php?title=List_of_English-language_book_publishing_companies&curid=746089&diff=564359255&oldid=563535930",1373895474,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Is there any progress or movement on this? Specifically, will hidden comments at least be displayed by the Monday deployment?",1373875721,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #9)
+> (In reply to comment #8)
+> > I don't think it was officially decided.  Most likely, it will be wikitext
+> > first, but that could change if the VE API is ready.
+> 
+> I don't know what you mean by ""the VE API"", let alone it being ""ready"". :-)
+> 
+> We negotiate with people to build whatever hooks they need (and we felt were
+> justified) in the normal way. However, a commenting system like this feels
+> more like core VE work than a plugin
+
+Okay, based on that, I think it makes sense not to use VE for the inline comment prototype.",1371498950,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #8)
+> I don't think it was officially decided.  Most likely, it will be wikitext
+> first, but that could change if the VE API is ready.
+
+I don't know what you mean by ""the VE API"", let alone it being ""ready"". :-)
+
+We negotiate with people to build whatever hooks they need (and we felt were justified) in the normal way. However, a commenting system like this feels more like core VE work than a plugin (so it wouldn't be a matter of hooks available for code in general); it'd sit well with the planned real-time collaborative editing functionality we're building in the new financial year, for which a chat/comment-like tool would be wanted.",1371429119,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"I don't think it was officially decided.  Most likely, it will be wikitext first, but that could change if the VE API is ready.",1371426788,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #6)
+> (In reply to comment #5)
+> >The second phase might be postponed indefinitely if the ""co-ment"" work comes to something. A treatment for in-line comments will be needed; possibly just a span of some kind. Will look at this.
+> 
+> I'm mentoring that (along with Tyler).  I don't think Richa's looked yet at
+> integrating with VE.  But it's still early. If you think the VE API is mature
+> enough that it integration is feasible, you can suggest that at bug 46440.
+
+I know - see your own comment at bug 46440 comment 13 :-) - but I thought that the proposal was to build this for wikitext editor and then we'd take on porting it over to VE once it was done?",1371425605,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #5)
+>The second phase might be postponed indefinitely if the ""co-ment"" work comes to something. A treatment for in-line comments will be needed; possibly just a span of some kind. Will look at this.
+
+I'm mentoring that (along with Tyler).  I don't think Richa's looked yet at integrating with VE.  But it's still early. If you think the VE API is mature enough that it integration is feasible, you can suggest that at bug 46440.",1371424966,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #4)
+> Quiddity, yeah, I know, I just filed that (bug 49608).
+
+For clarity, that's a problem with HTML comments in transclusions rather than in general, which does still work. Sorry. :-(
+
+We'd probably need to do this enhancement in stages - first, show comments and let them be deleted; later, make them editable and creatable. The second phase might be postponed indefinitely if the ""co-ment"" work comes to something. A treatment for in-line comments will be needed; possibly just a span of some kind. Will look at this.",1371420628,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Quiddity, yeah, I know, I just filed that (bug 49608).",1371265691,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"That bug isn't fixed then (or was re-broken), because Hidden Comments are being deleted when we save.
+
+(This problem is now worse, because it is now only noticeable if we opt to ""Review your changes"" before saving.)
+
+See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Removal_of_comments_in_Infobox
+and test with adding text anywhere in the article http://en.wikipedia.org/wiki/Bleak_House for example. It always removes the comments from the infobox.
+
+There are additional threads on that page mentioning the same thing.",1371265603,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),I don't think so.  That one's just about preventing them from being silently removed on save.  This is about actually displaying them to the editor.,1371264951,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"I think this is a duplicate of Bug 42124 ?
+
+It doesn't specifically mention HTML or Hidden, so I'm not positive.",1371264902,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Swallowing of empty text annotations leads to dirty diffs and unexpected Parsoid normalisation,"VisualEditor caused this dirty diff (https://en.wikipedia.org/w/index.php?title=List_of_South_Korean_idol_groups_%282010s%29&diff=559356009&oldid=559228059) when editing a table.  Note the removal of the empty small elements, and the change to the align syntax.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371258600,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-r3xcog5g6murfqlx2fpo,task_description,resolved
+VisualEditor: Swallowing of empty text annotations leads to dirty diffs and unexpected Parsoid normalisation,"(In reply to comment #0)
+> VisualEditor caused this dirty diff
+> (https://en.wikipedia.org/w/index.
+> php?title=List_of_South_Korean_idol_groups_%282010s%29&diff=559356009&oldid=5
+> 59228059)
+> when editing a table.  Note the removal of the empty small elements, and the
+> change to the align syntax.
+
+The removal of empty text annotations has been fixed as of wmf7 (gerrit 68213 and gerrit 68190), which is now deployed a week early on enwiki to fix this and other issues - sorry about that. This will stop ""the removal of the empty small elements"", and consequently the changes to the table syntax that Parsoid does on lines that aren't otherwise changed.
+
+The non-semantic syntactical change of the HTML syntax is, I believe intentionally  done by Parsoid to normalise the wikitext; it is only done on lines of wikitext that are changed anyway by user action (unless there's a bug in VisualEditor which causes the contents of the HTML to change unexpectedly, as was the case here).
+
+Consequently marking as ""fixed"".",1371419290,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r3xcog5g6murfqlx2fpo,task_subcomment,NA
+VisualEditor: Revive Inez's way of doing sub-surfaces,"Per Roan - ""we were initially going to use this for references and captions, and then chose to use separate documents instead, but this is not compatible with the collaborative editing work; a VE instance should be able to collaborate with another instance on the same page, although I suppose there was some stuff about limiting the scope successfully as well"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371181800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s72q22vgyujmcogxkisx,task_description,declined
+VisualEditor: Revive Inez's way of doing sub-surfaces,Instead we're going to go with sub-documents directly.,1416360265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s72q22vgyujmcogxkisx,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,"Clicking the section edit link into VE has three minor issues:
+
+* The cursor is positioned at the start of the heading of that section; it should probably go to the start of the next element straight after the section (in most cases, a paragraph)
+* The page doesn't actually scroll to the correct area; ideally the page should be deliberately scrolled to that section (as it happens, you normally end up on roughly the right part because the page is already scrolled, but there are cases where VE pages are lengthier or shorter than PHP pages and so this can't be relied upon).
+* The toolbar only appears once you scroll (because it's triggered on page movement, and the page doesn't move at first to get to the section because it's already there) - this means that it suddenly pops into view a bit too late.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371180060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zptqvqstkrfianknvktj,task_description,resolved
+VisualEditor: Section edit link behaviour tweaks,"Both changes merged, so marking as fixed.",1372109901,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,#3 in your list is fixed by #2,1372102079,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,^^^ Moves cursor to next non-heading,1372101985,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,Related URL: https://gerrit.wikimedia.org/r/70238 (Gerrit Change I6fcc463aeeae40278f5caf04ae251c8ecfe65472),1372101813,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,^^^ Fixes scroll,1372100335,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,Related URL: https://gerrit.wikimedia.org/r/70229 (Gerrit Change I3a57e64f54289a3263814b4fbfe00c63de4a490b),1372100128,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: CSS broken in RTL,"We have plans to use ResourceLoader which will fix a lot of this, but noting it here.
+
+Most obviously, the toolbar has two sections which in LRT appear as ABCDE  1234; in RTL they should be 4321  EDCBA, but instead appear as EDCBA  4321. Also issues in dialogs etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371155280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o4e72bpfvnzueqs77k5k,task_description,resolved
+VisualEditor: CSS broken in RTL,"(In reply to comment #2)
+> This is fixed in general by the introduction of Roan and Trevor's css-frame
+> fixes, and the popup menu fixes (in TextMenuWidget) - and I think that the
+> rest would likely result in spot-fixes, like the ones with the transclusion
+> editor.
+> 
+> Also, as far as I could see, the toolbar bug was fixed as well.
+> 
+> I think we can close this bug and rely on the main BIDI/RTL tracking bug to
+> continue work on any individual bugs as they happen.
+
+OK, done.",1374592563,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o4e72bpfvnzueqs77k5k,task_subcomment,NA
+VisualEditor: CSS broken in RTL,"This is fixed in general by the introduction of Roan and Trevor's css-frame fixes, and the popup menu fixes (in TextMenuWidget) - and I think that the rest would likely result in spot-fixes, like the ones with the transclusion editor.
+
+Also, as far as I could see, the toolbar bug was fixed as well.
+
+I think we can close this bug and rely on the main BIDI/RTL tracking bug to continue work on any individual bugs as they happen.",1374592211,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-o4e72bpfvnzueqs77k5k,task_subcomment,NA
+VisualEditor: CSS broken in RTL,"I went through the Link Inspector CSS issue and it gave me an insight into what may be happening here. 
+
+Using CSSJanus will probably help 90% of this problem, but it might not completely solve it. A lot of the position settings are inline, calculated dynamically and inserted into the element itself. I'm not entirely sure CSSJanus knows how to deal with those. We may have to split the calculation up into RTL and LTR positions, or find some other solution to the popups that are calculated dynamically.",1371575347,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-o4e72bpfvnzueqs77k5k,task_subcomment,NA
+VisualEditor: Incorrectly handling nested reference tags (blocked by Parsoid),"This is a particular problem with 'note' sections, and references used as notes; they commonly include citations for their statements, and you end up with markup that looks like <ref> some text here <ref> a citation for that text</ref></ref>
+
+The VE is for some reason displaying it as a citation template, ""some text here"", a second citation template and a random </ref> tag. See note 1 in https://en.wikipedia.org/wiki/Fomitiporia_ellipsoidea for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371143340,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-comswpptjs3uwf7ztbnb,task_description,resolved
+VisualEditor: Incorrectly handling nested reference tags (blocked by Parsoid),"This is now ""fixed"" (but we may want to make it a nicer experience in the future).",1371782246,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-comswpptjs3uwf7ztbnb,task_subcomment,NA
+VisualEditor: Incorrectly handling nested reference tags (blocked by Parsoid),"This is because Parsoid doesn't support the ""#tag:ref"" hack to let you do multi-level references (which were explicitly not allowed because of the insanity this creates :-)).
+
+Creating a secondary bug (VE currently assumes you can't have nested references, which is indeed what Parsoid gives us), bug 49555. Once Parsoid supports this, we'll need to check that we correctly handle this from a UX perspective (amongst other things).",1371168461,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-comswpptjs3uwf7ztbnb,task_subcomment,NA
+VisualEditor: Dropdown text style menu overlaps with other interface elements,"See https://upload.wikimedia.org/wikipedia/en/8/8f/Visual_editor_pulldown_menu_problem.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371122520,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mu7u3eco45xxsfwg4vhq,task_description,resolved
+VisualEditor: Dropdown text style menu overlaps with other interface elements,This was fixed in the re-write of the toolbar two weeks ago; sorry for not updating until now.,1372007755,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mu7u3eco45xxsfwg4vhq,task_subcomment,NA
+VisualEditor: Dropdown text style menu overlaps with other interface elements,"(In IE9, I'd note).",1371122580,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mu7u3eco45xxsfwg4vhq,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","Have a link [[Foo]] which is a redirect to [[Foobar]].
+
+Inspect link; it will suggest:
+
+New pages
+  Foo
+Existing pages
+  Foobar
+
+This is because ""Foo"" does not come back in the list of pages you can link to - which is filtered to remove redirects - but we should special-case the existing link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50240",1371075060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdmjeut7byvwilwzjfyv,task_description,declined
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","AFAICT this underlying bug was fixed in October; the issue that MediaWiki's search system sometimes comes back with bad results from time to time (falsely claiming that short titles don't exist) is distinct, as part of bug 54361.",1395441844,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","Another couple of examples I found:
+I write Indian religion, select the two words and try to add the relevant link; it doesn't recognize the page as an existing redirect, while it lists Indian religions as ""matching page"".
+Same story for Tafkap; in this case, a couple of all caps variants are listed as redirects.
+In these cases the ""click in the text field"" trick didn't work.",1394543448,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","There are a bunch of bugs about this, so I'm pretty sure I'm adding my comment to the wrong one :D
+Anyway, it is possible that the inspector does not recognize immediately a page as an existing redirect. See https://en.wikipedia.org/wiki/File:VE_wrong_link_state_in_link_editor.png .
+https://en.wikipedia.org/wiki/New_York_Kennedy is a valid redirect page.
+Unfortunately this is not easy to reproduce. 
+(I never managed to do it by just typing New York Kennedy and then wikiling those words, anyway.)
+I sometimes managed to reproduce by selecting a completely random word (or even more than one), clicking on the chain icon, writing New York Kennedy in the dialog. Every time though it does correct itself if, after observing the same result from the screenshot above, you click again in the text field, so the page will correctly appear as a blue link listed as a redirect.",1394541885,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",James couldn't either so RESOLVED WORKSFORME,1391312264,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",I can't reproduce this bug.,1391312206,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","Many redirects exist because they respond to expected (simplified) alternative names, plurals, synonyms, non-complete names of people and places, and popular uses in general. It is likely that these popular uses are also used in articles. When selecting a word, the difference between VE recognizing or not these redirects is important:
+
+* If the redirect is recognized and the destination page is shown, most editors will understand the difference and will choose the complete name.
+
+* If the redirect is not shown then you can be a lazy editor and insert the link (having no idea whether it will result in a red or blue link), you can avoid the link altogether just in case, or you can be a good editor (as I try to be), open a new tab, and search that term only to find that many times such term is a known redirect.
+
+Do the latter 20 times in a long article and you will come to this bug report as I did. I found this to be a big nuisance in real editing. (with the side benefit that I tested Cirrus Search more and I even found a bug, thanks to these deviations caused by VE)
+
+PS: or simply show the redirects in italics, as they are already displayed in some MediaWiki lists.",1390032494,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",*** Bug 59208 has been marked as a duplicate of this bug. ***,1390024134,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","I'd say the desired behavior would be that the link inspector show the existing redirect in different way (such as blue but with a parenthetical note that this is a redirect).
+
+In most cases, the link to the target article is the preferred link choice, but in many cases the redirect is also valid. For cases where the redirect points to a subsection, the redirect is probably the preferred link most of the time.",1377278376,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",*** Bug 50274 has been marked as a duplicate of this bug. ***,1373519588,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","In my local copy, the redirect URL is not filtered out, but I did notice another bug in that code: https://gerrit.wikimedia.org/r/69871",1371830218,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",*** Bug 49540 has been marked as a duplicate of this bug. ***,1371153385,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+VisualEditor: Capitalisation does not register as a change,"If someone capitalises a character(see https://en.wikipedia.org/w/index.php?title=Founder_effect&diff=559607253&oldid=558757694 for example) the VisualEditor does not recognise it as an alteration to page text and rejects their edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371063300,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-clapsacnmffdpmc6uic3,task_description,resolved
+VisualEditor: Capitalisation does not register as a change,"Filed 53210 for my last comment which I see it now, it was unrelated.",1377174192,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-clapsacnmffdpmc6uic3,task_subcomment,NA
+VisualEditor: Capitalisation does not register as a change,It is actually being reported now on itwp: in order to do this http://it.wikipedia.org/w/index.php?title=DNasi_attivata_da_caspasi&diff=60101664&oldid=60089990 I had to delete the word and link it back again. Our guidelines about style require pages in that section to appear with the capital letter. I'll also add a link to https://bugzilla.wikimedia.org/show_bug.cgi?id=50452 which looks related. Thanks.,1373719943,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-clapsacnmffdpmc6uic3,task_subcomment,NA
+VisualEditor: Capitalisation does not register as a change,Ed's fix on Friday corrected this; sorry for the bug. Now live in production.,1372015558,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-clapsacnmffdpmc6uic3,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,"Screenshot
+
+See associated screenshot - this is for https://www.mediawiki.org/wiki/Template:Extension
+
+When clicking the inspector icon, the window opens up but remains entirely blank and happily sits there like it for minutes* at a time. More worryingly, if I follow the normal workflow for a broken element (hit the X, make it go away, try and open it again) the inspector refuses to open at all, not just for that template but for other elements on the page.
+
+*I gave up waiting; it may load, eventually, or never load.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49797
+
+**Attached**: {F11051}",1371060840,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_description,resolved
+VisualEditor: Transclusion inspector blank on opening some templates,*** Bug 50016 has been marked as a duplicate of this bug. ***,1371969869,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,*** Bug 49958 has been marked as a duplicate of this bug. ***,1371832175,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,Related URL: https://gerrit.wikimedia.org/r/69806 (Gerrit Change I0b661744d0388345561897c9631f15e691737031),1371766188,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,*** Bug 49797 has been marked as a duplicate of this bug. ***,1371748994,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,*** Bug 49862 has been marked as a duplicate of this bug. ***,1371745099,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,"I found this as well. Here are the steps to reproduce:
+
+1. Open up [[mw.VisualEditor:Template test]] in edit mode.
+2. Click on any template, then click on the icon to open the template inspector.
+3. Click on the cross in the top-right-hand corner to close it.
+4. Click on the template inspector icon for the same template again. (It appears to still be there from the first time it was clicked.) This time the inspector appears blank.
+5. Click on the cross in the top-right-hand corner to close it again.
+6. Now, clicking on the template icon for any template on the page will have no effect (i.e. the template inspector doesn't load at all).",1371541325,PHID-USER-rjtk3h6l2quifuajiime,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,"Never loads. Trevor, is it selecting the wrong thing, so can't fetch it, or selecting the right thing, but can't fetch it for some other reason?",1371248265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Some block objects when selected not triggering the inspector menu (no template/image icon),"Screenshot
+
+Screenshot attached - from https://www.mediawiki.org/wiki/Extension:Syntax_Highlighting
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F11040}",1371059580,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mgaib3olu55b5fa25dcw,task_description,resolved
+VisualEditor: Some block objects when selected not triggering the inspector menu (no template/image icon),Marking as fixed.,1372037973,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mgaib3olu55b5fa25dcw,task_subcomment,NA
+VisualEditor: Save dialog should not preserve history when opening a second time,"1. Make a change and press save
+2. close the save dialog (^)
+3. Press save again
+
+Note there is now a back button (<) which does nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371048240,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nqjwrvv7obmoxabd6boz,task_description,resolved
+VisualEditor: Save dialog should not preserve history when opening a second time,Related URL: https://gerrit.wikimedia.org/r/70113 (Gerrit Change I297a7d1458e5a1c33b9dcb85272fe5f40893dd88),1372034145,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nqjwrvv7obmoxabd6boz,task_subcomment,NA
+VisualEditor: Bad HTML when link seems to have been edited,"From a bug report in /mnt/bugs on parsoid.wmflabs.org.
+
+The edited HTML snippet in question looks like this:
+
+""<a href=""./Turkish_sparrow"" rel=""mw:WikiLink"" data-parsoid='{""a"":{""href"":""./Turkish_sparrow""},""sa"":{""href"":""Turkish sparrow""},""stx"":""simple"",""dsr"":[92,111,2,2]}'><a href=""American%20sparrow"" rel=""mw:WikiLink"">American sparrow</a></a>""
+
+The editor may tried to edit a link from Turkish -> American sparrow
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370981400,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4g3tuqan3yhuka5pdfba,task_description,resolved
+VisualEditor: Bad HTML when link seems to have been edited,Speculatively marking as fixed; please re-open if it recurs.,1372215957,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4g3tuqan3yhuka5pdfba,task_subcomment,NA
+VisualEditor: Bad HTML when link seems to have been edited,I think this is one of the bugs that has been fixed by https://gerrit.wikimedia.org/r/70434,1372215765,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4g3tuqan3yhuka5pdfba,task_subcomment,NA
+VisualEditor: Bad HTML when link seems to have been edited,"Another instance from /mnt/bugs/2013-06-11T19:33:15.924Z-VPN_blocking (on enwp)
+
+<a rel=""mw:WikiLink"" href=""protocol%20tunnel""><a rel=""mw:WikiLink"" href=""protocol%20tunnellng"">protocol tunnell</a></a><a rel=""mw:WikiLink"" href=""protocol%20tunnellng"">ing</a>",1371055575,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4g3tuqan3yhuka5pdfba,task_subcomment,NA
+VisualEditor: Bad HTML when link seems to have been edited,From: /mnt/bugs/2013-06-10T19:18:14.190Z-Golden-Crowned_Sparrow (editing done on mediawiki.wikimedia.org).,1370981817,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4g3tuqan3yhuka5pdfba,task_subcomment,NA
+VisualEditor: Surface should be able to inherit commands and toolbar from other surface,"Right now, we have to do the following in ve.ui.MWReferenceDialog and ve.ui.MWMediaDialog to set up the sub-editor's surface correctly:
+
+this.referenceSurface.addCommands( ve.init.mw.ViewPageTarget.static.surfaceCommands );
+
+Instead of accessing ve.init.mw (and assuming all surfaces with MW*Dialogs will be instantiated by ve.init.mw.ViewPageTarget), we should just be able to say ""initialize this new surface based on this existing surface"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1370964780,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-uk5g2utei5kls5xo2fer,task_description,resolved
+VisualEditor: Surface should be able to inherit commands and toolbar from other surface,"Not just inherit, but also block from inheritance for specific instantiations (e.g. the caption of an image inside a reference can't take a reference - bug 58270).",1386877772,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uk5g2utei5kls5xo2fer,task_subcomment,NA
+VisualEditor: Surface should be able to inherit commands and toolbar from other surface,"Stylesheets should be inherited as well (and be loaded by the surface rather than the dialog) so we don't have to do things like
+
+ve.ui.MWReferenceDialog.static.addLocalStylesheets( [
+	've.ce.Node.css',
+	've.ce.Surface.css',
+	've.ui.Surface.css',
+	've.ui.Context.css',
+	've.ui.Tool.css',
+	've.ui.Toolbar.css'
+] );",1370964956,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-uk5g2utei5kls5xo2fer,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","**Author:** `swalling`
+
+**Description:**
+When attempting to remove an entire section with an h2 header, removing the text of the header does not remove the line separator underneath the header. 
+
+Additionally, one additional delete/backspace action deleted the entire preceding section, and it seems from the resulting content that I merely blanked the header but the wikitext for it remains.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370932440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d25o2mdf4mdptqcqy2de,task_description,declined
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)",AFAICT this is now fixed - marking as WORKSFORME. Please re-open if it recurs.,1386029219,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","Change 70949 had a related patch set uploaded by Inez:
+(bug 49424) Add empty lines before/after new block level images
+
+https://gerrit.wikimedia.org/r/70949",1372379464,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)",Could someone provide step by step instruction how to reproduce this problem?,1372371000,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)",The latter; my apologies for not reading correctly! :),1371242772,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","The first part of this bug is a duplicate of bug 49452 (""Whitespace-only headings should be collapsed to (blank) paragraphs""), so re-purposing to be about the deletion issue.
+
+@Steven - could you give more details about this bug with deletion magically hiding large blocks of text but not deleting them - was it in Chrome/Mac? Does it happen reliably (and can you reproduce now) or is it occasional?
+
+@Oliver - is the ""this"" that users have seen the deletion causing a paragraph to no longer appear but still be there, or the heading-not-being-fully-deleted issue?",1371242518,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","This has also been reported by other users, and is something I observed in the usertesting videos we did, too.",1371126627,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","**swalling** wrote:
+
+Result
+
+Note empty header
+
+**Attached**: {F11801}",1370932504,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","**swalling** wrote:
+
+Diff
+
+**Attached**: {F11799}",1370932479,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+VisualEditor: Activation of a selected block which is the first content not possible,"You can select it but the inspector menu doesn't trigger. Works fine if there's any content before the block.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370912820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ws46dvvtpsd7zfz4gkae,task_description,resolved
+VisualEditor: Activation of a selected block which is the first content not possible,Now fixed and will be put into production very soon.,1371844292,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ws46dvvtpsd7zfz4gkae,task_subcomment,NA
+VisualEditor: Activation of a selected block which is the first content not possible,Related URL: https://gerrit.wikimedia.org/r/69707 (Gerrit Change I8bcdea0f7a6951216bf8368865d23ef6246880ea),1371753495,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ws46dvvtpsd7zfz4gkae,task_subcomment,NA
+VisualEditor: Activation of a selected block which is the first content not possible,"Happens if it's a block or floated template, or an inline or floated (thumb) image. Doesn't happen on an inline template or an inline-block template.",1371746901,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ws46dvvtpsd7zfz4gkae,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,"Editing a page in a Hebrew wiki (possibly also in other RTL languages), adding a link does not show the popup. The word automatically becomes a wiki-link, no option to change the destination or make it an external link.
+
+The link seems to work well in English wikis.
+
+Tested on both my local install with the latest VE (VE-wmf6+) and on the hebrew wikipedia (VE-wmf5) and on both Firefox and Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1370904180,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ze4pocno64vkraksutzp,task_description,resolved
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,"Change 69281 abandoned by Mooeypoo:
+[WIP] Link surface fix for RTL
+
+Reason:
+Fixed in master.
+
+https://gerrit.wikimedia.org/r/69281",1373484938,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,This works for me and seems to work in the hebrew wikipedia. Can be marked as resolved.,1373001408,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,Give Moriel the credit given that she's done all the work on this bug so far - we'll try to get the patch properly reviewed so we can (hopefully?) merge and deploy it very soon.,1372001761,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,"I've been working on a fix for this but I may need some help with an issue.
+
+The position definition had to be changed in RTL, as it is hard-coded (calculated by the location of the word/selection.) That was completed successfully and the link surface appears correctly below the marked word in both LTR and RTL. 
+
+However, I am running into problems setting up the proper ""right"" dynamically-calculated value for the sub-popup TextInputMenuWidget, and my attempts to play around with left/right and windowWidths has failed. It appears ""almost right"" (a little to the left, a little to the right, skewed, etc) and I think I may be missing a property.
+
+I wonder if there is a possibility to get the ""right"" value of the link surface (that appears correctly) to implement it in the TextInputMenuWidget without having to call the element specifically.
+
+The fix below is still work in progress (Don't Merge!) but it should be completely fixed if I manage to figure out the position of the TextInputMenuWidget.",1371535364,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,Related URL: https://gerrit.wikimedia.org/r/69281 (Gerrit Change I312610ca630a8f75f1a0778e97f227f35a003b41),1371534862,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,And the opposite is also true: The inspector is visible in the Hebrew Wikipedia if the interface language is English.,1371315442,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,"This also happens in the English wikipedia when the user interface is set to any rtl language.
+
+I tested with ?uselang=he ?uselang=ar and ?uselang=fa",1371058014,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"Screenshot of VisualEditor on the English Wikipedia
+
+I'm not even really sure how to explain this. I'll just include a screenshot.
+
+I went to <https://en.wikipedia.org/wiki/Ready,_Willing_and_Able_(Daron_Norwood_song)> and clicked ""edit this page"". This is what appeared.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11769}",1370897160,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_description,resolved
+Parsoid sometimes loads content from another wiki,I am assuming this is not an issue any more given that we have had no reports after launch.  The launch should have caused a lot of corruptions if this bug had been around.  Closing.,1373560843,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934035,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,Please let us know if there are any new cases.,1372463719,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"Still happening - PamD reports that {{User sandbox}} on enwiki displayed in Japanese and gave the wrong user name (Apparently she's now User:Ichiro Kikuchi). It's stopped, but...worrying.",1372082680,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,https://gerrit.wikimedia.org/r/69905 (Gerrit Change I495c294a5dbafadac133c0b377b576d297ca529d) | change APPROVED and MERGED [by jenkins-bot],1371845667,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,Related URL: https://gerrit.wikimedia.org/r/69905 (Gerrit Change I495c294a5dbafadac133c0b377b576d297ca529d),1371845423,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,https://gerrit.wikimedia.org/r/69880 (Gerrit Change I52abbc10e5fe6a6b9d97ef6d842943809c8f6d6d) | change APPROVED and MERGED [by jenkins-bot],1371834699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,Related URL: https://gerrit.wikimedia.org/r/69880 (Gerrit Change I52abbc10e5fe6a6b9d97ef6d842943809c8f6d6d),1371834091,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,*** Bug 49939 has been marked as a duplicate of this bug. ***,1371829646,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,New report: But 49939,1371829621,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,Since there are no new reports it seems that this bug has been fixed by our config clean-up. Please reopen if you encounter this bug again.,1371774436,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,I think this is now fixed.,1371774406,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,*** Bug 49687 has been marked as a duplicate of this bug. ***,1371510441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,We deployed a few clean-ups to our wiki configuration handling recently which might have improved the handling of API errors when retrieving the per-wiki config fails. Has this bug been seen in the wild recently?,1371510235,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"We've seen a bunch of reports of content from different wikis showing up, usually German content (plus one case of Russian, and now one of French apparently). Moving this to Parsoid.",1371172273,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"Happened for me on pl.wp earlier today, too, with ""Vorlage"" as well. I didn't make a screenshot and I don't remember the aricle, sorry.",1371171596,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"Created attachment 12510
+Screenshot of VisualEditor on the English Wikipedia being all weird
+
+""Vorlage""? Blergh.
+
+My suspicion is Parsoid cache pollution.
+
+**Attached**: {F11771}",1370899423,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"In attachment 12508, we can see that instead of the templates being shown with a green striped area atop them, there is ""Modèle:Infobox Single↵"", ""Modèle:Lari White↵↵↵↵↵"" and ""Modèle:1990s-country-song-stub"".
+
+I'm not sure what language this is (French, maybe?), but my account is set to use English and the site is supposed to be in English.",1370897328,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Create a document:
+
+Foo <ref>Bar</ref> Baz
+<references />
+
+=>
+
+Foo [1] Baz
+1. Bar
+
+
+==Test==
+1. Select and copy from '[' to ']' (no whitespace)
+2. Try to paste
+3. Note you now just have plain text [1]
+4. Note also if you make a larger selection (e.g. from 'o' to 'B'), copy/paste works fine.
+
+This might be to do with whitespace truncation, and probably applies to other inline nodes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52271
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54410",1370888760,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_description,resolved
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"No, this was and remains fixed. Test in Chrome or Firefox, for example.",1415030920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"I think this is still occurring (https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox&diff=68973564&oldid=68973535 ).
+I'm using Safari, and I don't know if this is related to Bug 70143.",1415020432,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Change 83222 merged by jenkins-bot:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",1378923314,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Change 83222 had a related patch set uploaded by Esanders:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",1378548154,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"This is still broken in FF, see bug 53375",1377643048,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,Fixed in master; will be deployed on Thursday as part of the regular push.,1377634922,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Change 80301 merged by jenkins-bot:
+Copy-paste data fixes
+
+https://gerrit.wikimedia.org/r/80301",1377634864,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Change 80301 had a related patch set uploaded by Jforrester:
+Copy-paste data fixes
+
+https://gerrit.wikimedia.org/r/80301",1377546588,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,https://gerrit.wikimedia.org/r/#/c/80301/ fixes,1377544792,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,Note this behaviour also occurs with templates,1376695565,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,*** Bug 52212 has been marked as a duplicate of this bug. ***,1375134084,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"**bi.llybob** wrote:
+
+Note that, at least in Chrome, whitespace is <i>not</t> enough to count as additional text.",1373170390,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,*** Bug 50594 has been marked as a duplicate of this bug. ***,1372794209,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Restoring oldids broken,"On attempting to edit and restore an oldid, everything works fine (oldid contents appear, diff shows correct wikitext change, etc.) but on save VE appears to send the wrong page version (presumably the 'newer' version that's meant to be replaced?) to MW so nothing gets saved.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1370882100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-465skcravcf5ewxwsyd2,task_description,resolved
+VisualEditor: Restoring oldids broken,Merged and will go out with next deployment.,1371588446,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Restoring oldids broken,Related URL: https://gerrit.wikimedia.org/r/69344 (Gerrit Change Icacaa5101386e52309278c8d9871ca1193aa86a9),1371583097,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Restoring oldids broken,Ed is exactly right. EditPage appears to set basetimestamp this way as well.,1371576196,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Restoring oldids broken,"I can reproduce it. Tellingly, if you make a change and then press save you get an edit conflict. I suspect the problem is we are providing the timestamp of the version you choose to edit as the 'basetimestamp' which I don't think is right. When you hit save the API thinks all the versions ahead of the version you're editing were created since you loaded the page (hence the edit conflict scenario).
+
+I think 'basetimestamp' should always be populated with the timestamp of 'cur', regardless of which version you are editing, but would like confirmation from someone who knows the MW API better.",1371573224,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Restoring oldids broken,I can't reproduce this bug. I'll keep the assignment to Ed but it looks like this has been resolved in the mean time.,1371511602,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Inspector buttons appear above save dialog,"1. Focus a node which triggers an inspector icon
+2. Hit save
+3. http://i.imgur.com/5YPyQL5.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49275
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49059",1370781420,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dbpbmbo7zjpy256zvcs6,task_description,resolved
+VisualEditor: Inspector buttons appear above save dialog,Merged and will go out later today.,1371766472,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dbpbmbo7zjpy256zvcs6,task_subcomment,NA
+VisualEditor: Inspector buttons appear above save dialog,Related URL: https://gerrit.wikimedia.org/r/69614 (Gerrit Change I2fbc4c8af943f1b096b8912191924961405d5c47),1371688630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbpbmbo7zjpy256zvcs6,task_subcomment,NA
+VisualEditor: Inspector buttons appear above save dialog,Probably related: http://i.imgur.com/E5SFyv0.png,1370902428,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dbpbmbo7zjpy256zvcs6,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"Because we want to be able to make certain properties non-cloneable, e.g. in ve.dm.MWReferenceNode.prototype.getClonedElement we strip 'contentsUsed'.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370612580,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_description,resolved
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,Fixed and will go live in a few minutes.,1372379856,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"Change 70913 merged by jenkins-bot:
+Invoke getClonedElement() on each element on copy
+
+https://gerrit.wikimedia.org/r/70913",1372372301,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"""We should verify...""",1372366801,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"We should very that copy/pasting a named reference with contents, doesn't copy the contents.",1372366747,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"Change 70913 had a related patch set uploaded by Catrope:
+Invoke getClonedElement() on each element on copy
+
+https://gerrit.wikimedia.org/r/70913",1372365026,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Review dialog obfuscated by phantoms,"Screenshot of VisualEditor on the English Wikipedia using the Monobook skin, 2013-06-06
+
+VisualEditor's review dialog box can be obfuscated by the green striped area from restricted areas of a page. This is when using Monobook, at least. Maybe Vector too, I don't know. I've attached a screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11508}",1370571600,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ypcnrwup72gw33jiae5x,task_description,resolved
+VisualEditor: Review dialog obfuscated by phantoms,"We solved this specific issue as part of the minor re-work of the save dialog, but see bug 50096 and bug 49059.",1372084364,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ypcnrwup72gw33jiae5x,task_subcomment,NA
+VisualEditor: Review dialog obfuscated by phantoms,"Yes, this is a mess; phantoms' z-index is higher than the review panel (which is bad), and trigger when the mouse moves over them even though you're in a ""different"" interface component. This would be solved by switching to the new dialogs (as they're iframes), but we don't have time for that.",1370622142,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ypcnrwup72gw33jiae5x,task_subcomment,NA
+VisualEditor: Images loaded over HTTP unconditionally,"https://en.wikipedia.org/wiki/Jeffrey_Chiesa?veaction=edit
+
+When I go here currently, I get HTTPS warnings.
+
+---
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/5/5f/New_Jersey_Attorne…effrey_S_Chiesa.jpg/144px-New_Jersey_Attorney_General_Jeffrey_S_Chiesa.jpg.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/f/f0/Seal_of_the_United_States_Senate.svg/80px-Seal_of_the_United_States_Senate.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/8/8d/Seal_of_New_Jersey.svg/90px-Seal_of_New_Jersey.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/9/92/Flag_of_New_Jersey.svg/75px-Flag_of_New_Jersey.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/5/5f/New_Jersey_Attorne…effrey_S_Chiesa.jpg/144px-New_Jersey_Attorney_General_Jeffrey_S_Chiesa.jpg.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/f/f0/Seal_of_the_United_States_Senate.svg/80px-Seal_of_the_United_States_Senate.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/8/8d/Seal_of_New_Jersey.svg/90px-Seal_of_New_Jersey.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/9/92/Flag_of_New_Jersey.svg/75px-Flag_of_New_Jersey.svg.png.
+ Jeffrey_Chiesa:1
+---
+
+action=view is fine (no console warnings). When I go to veaction=edit, the console fills with warnings. It looks like VisualEditor is loading thumbnails unconditionally through HTTP. This should be changed to be protocol-relative.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/wiki/Jeffrey_Chiesa?veaction=edit",1370571480,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hljkwvij7ri6zsnlv4ny,task_description,resolved
+VisualEditor: Images loaded over HTTP unconditionally,"
+
+*** This bug has been marked as a duplicate of bug 43015 ***",1371576350,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hljkwvij7ri6zsnlv4ny,task_subcomment,NA
+VisualEditor: Images loaded over HTTP unconditionally,"This is odd - I thought this was fixed, but I can reproduce on enwiki but not on MW.org.
+
+I think this may be fixed by the new image code the Inez has written (which is still 'experimental' and so not available in production except for MW.org). Will check with him and update you.",1370621859,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hljkwvij7ri6zsnlv4ny,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","**Author:** `swalling`
+
+**Description:**
+Screenshot
+
+In attempting to test (as anon) on the MediaWiki.org sandbox, the page header template overlaps the diff and save functions, preventing me from saving my edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49361
+
+**Attached**: {F11481}",1370553900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-io3sncftadpkbmrqampw,task_description,resolved
+"VisualEditor: Phantoms appear above the save dialog, preventing saving",Merged and will go out later today.,1371766465,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving",Related URL: https://gerrit.wikimedia.org/r/69614 (Gerrit Change I2fbc4c8af943f1b096b8912191924961405d5c47),1371688627,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","Just a note that this also happens with editable elements like images, as their blue overlay extends on top of the VE menu bar.",1371652418,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","Instead of an arms race between z-index, the much easier solution would be to ensure the DOM structure of these two elements are nested properly so that their natural order is correct. z-index can be used to adjust display, but it is not capable (by design) to transcend the relative DOM position.
+
+I haven't tested the following so this exact example could be wrong, but generally it means that in the following sample:
+
+ <div style=""position: relative;"" id=""foo""> </div> 
+ <div style=""position: relative;"" id=""bar""> </div> 
+
+
+Naturally #bar will be on top of #foo as it comes later in the DOM. Though #foo and #bar can be interchanged at the root (through their common parent), any child of #bar will always be on top of any child of #foo.
+
+So not only is DOM ordering easier to manage (due to not having to worry about conflicting numbers), in some cases it is the only way.
+
+I'll see what the easier way to fix this is, we can perfect it later if suboptimal.",1370850847,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","And I had a similar issue attempting to save a page with an (uneditable) InfoBox on the right hand side. Luckily a simple workaround for the moment is to scroll down!
+
+Obviously the proper solution is to ensure the zorder of the ""Review your changes"" and ""Save your changes""/""Report a problem"" is above the ""phantoms"".",1370776701,PHID-USER-fgul5wwrgbtdpd5fved3,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","Whoops, thanks for the spot, Steven!",1370554710,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Add a temporary option to have section edit links go to wikitext editor, not VisualEditor","Necessary for beta rollout. Wording needs to be smithed carefully to ensure that it's clear that this is a temporary option.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1370536440,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a7khjsiws3kuhgw3dtj5,task_description,resolved
+"VisualEditor: Add a temporary option to have section edit links go to wikitext editor, not VisualEditor",Done and deployed.,1371161777,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a7khjsiws3kuhgw3dtj5,task_subcomment,NA
+"VisualEditor: Add a temporary option to have section edit links go to wikitext editor, not VisualEditor",Related URL: https://gerrit.wikimedia.org/r/68569 (Gerrit Change I5ce7ea8c1e47e8243b619fc61aa957f767d22b48),1371161078,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a7khjsiws3kuhgw3dtj5,task_subcomment,NA
+VisualEditor: [Regression] Arrow keying around multibyte unicode characters fails after an inline node,"For example in the second line of the multibyte.html test file in the standalone demo (after '<tt>香港</tt>' [Hong Kong])
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370520480,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vtupkd2hzxpp7w3fyltw,task_description,resolved
+VisualEditor: [Regression] Arrow keying around multibyte unicode characters fails after an inline node,Above fixed is merged and will go out with wmf7 from Thursday.,1370969172,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vtupkd2hzxpp7w3fyltw,task_subcomment,NA
+VisualEditor: [Regression] Arrow keying around multibyte unicode characters fails after an inline node,Related URL: https://gerrit.wikimedia.org/r/67971 (Gerrit Change Iff1dfb90130685bb710821f8386cfa2f296f2f95),1370954363,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vtupkd2hzxpp7w3fyltw,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Visual Editor doesn't behave correctly when editing and adding text with combining diacritics.
+
+For example insert the text ""ɛ́"" (ɛ is character U+025B, combining acute is U+0301).
+When the cursor is behind ""ɛ́"":
+- pushing the left arrow doesn't move the cursor
+- adding text like ""ɛ́abcdef"" is fine but:
+  - pushing backspace gives ""ɛ́abcda"" instead of expected ""ɛ́abcde""
+  - pushing return ives ""ɛ́abcde\na""
+
+Some languages require combining diacritics, many keyboard layouts allow their input or user can insert them by copying and pasting from somewhere else.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51472",1370504280,PHID-USER-i5at67w766dqxs6ncxam,PHID-TASK-3tfgena4tsev5hzwqh7g,task_description,resolved
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"(In reply to comment #10)
+> I believe this is related (or a dupe?) of this:
+> https://bugzilla.wikimedia.org/show_bug.cgi?id=51472
+
+Related but not a dupe, I think; adding a see-also.",1374157250,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,I believe this is related (or a dupe?) of this: https://bugzilla.wikimedia.org/show_bug.cgi?id=51472,1374125073,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Great! It works as it should now.
+Thanks a lot!",1374124846,PHID-USER-i5at67w766dqxs6ncxam,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,Now fixed and will be deployed very soon; sorry for this.,1371844259,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,Related URL: https://gerrit.wikimedia.org/r/69814 (Gerrit Change If9c0860e2fe7b01eb0b27aae67c671062799a0fa),1371771158,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Yes, this is still reproduceable on Chrome and Firefox on Ubuntu, Chrome, Firefox and Safari on OS X, Chrome, Firefox, IE on Windows 8.
+The steps I tried on http://en.wikipedia.org/wiki/User:ESanders_(WMF)/Sandbox are :
+- move cursor to end of ""ɛ́abcdef""
+- type g
+- press return
+result: ""ɛ́abcdeff"" and new line instead of expected ""ɛ́abcdefg"" and new line.",1371444604,PHID-USER-i5at67w766dqxs6ncxam,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Denis, can you still reproduce (and if so, where and with what browser/system)?",1371162059,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Can't reproduce in master or live, except for a bug where if I select all then paste an exception is thrown (but that is unrelated).
+
+
+See:
+http://en.wikipedia.org/wiki/User:ESanders_(WMF)/Sandbox",1371159350,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,Reopening and assigning.,1371154520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Yes this is still reproduceable on en.wikipedia.org or fr.wikipedia.org as well as www.mediawiki.org. I guess ""on the cluster everywhere as of yesterday"" means the bug 48630 is fixed so this is not a duplicate.
+Or is there a specific place I should try to reproduce the bug on where this has been fixed?
+
+Quickly looking at bug 48630 it seems the behaviour described here is different, although the solution to 48630 might fix this one, just not the current solution.
+
+Furthermore there are other broken behaviours.
+- In some situations the line following ""ɛ́"" would just be duplicated every unknown time interval until the input cursor is moved.
+- If the ""ɛ́"" is in the middle of a line, some following characters are duplicated each interval with or without the combining diacritic on them.
+- If inputing two base characters with each a combining character, an unexpected next line return is produce when finishing the sequence.
+- When moving the cursor past the base character with the combining character, the cursor jumps to the next line even if there are still characters on the current (actually now previous) line.",1370582711,PHID-USER-i5at67w766dqxs6ncxam,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"This appears to be a duplicate of an already-fixed bug (bug 48630), which is live on the cluster everywhere as of yesterday. Can you reproduce this now, and if so, on what wiki? Support for graphemes like this is important for us, as you can imagine, and it's worrying to hear that it's not working?
+
+*** This bug has been marked as a duplicate of bug 48630 ***",1370531722,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,"grey text, no diff appears after Review and save
+
+Seen in IE9 and below, works OK in FF and Chrome: 
+
+Make an edit with VE
+Click Review and save
+
+Page text is greyed out; no diff appears; Review and save button remains clickable; user cannot complete edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11329}",1370450340,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-wgabwxsulvcboqwjus4t,task_description,resolved
+VisualEditor: IE9/10 incompatibilities with saving process,This is working for me now: I saved https://www.mediawiki.org/w/index.php?title=User:Catrope%2FSandbox&diff=1137641&oldid=740030 in IE10.,1409958443,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,*a user,1377104818,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,"An user reports:
+<<I just got a Edit beta tab on The Adventure of the Reigate Squire, even though I'm in IE 10. What's weirder is that this is the only page where I've seen a VE tab. Also, I can't make any edits with it: I changed a few words in one sentence and added an edit summary, but the thing's just hanging there. I got a message of Warning: Your edit may have been corrupted – please review before saving. However, I've been unable to find anything corrupt, even though I reviewed everything that I'd done. Nothing of WP:EF came up, either. 2001:18E8:2:1020:202A:8DD6:6403:B77 (talk) 16:25, 21 August 2013 (UTC)
+
+After several minutes of fruitless waiting, I gave up and reloaded the page. I then tried to add Category:Reigate and Banstead to the article (it's where the story is set), but after typing an edit summary of ""Add category"", I was forced to see that it's just been hanging there again. 2001:18E8:2:1020:202A:8DD6:6403:B77 (talk) 16:30, 21 August 2013 (UTC) >>
+
+Is this due to some tests or deployment sanity checks? Thanks.",1377104779,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,*** Bug 50086 has been marked as a duplicate of this bug. ***,1372084871,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,Relabelling; this is a blocker to IE9/10 use.,1372037486,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,IE10 exhibits the same behaviour.,1372032122,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,Related URL: https://gerrit.wikimedia.org/r/70108 (Gerrit Change I2ee2e33c89cac58863c9911fc3ad250c72a46206),1372031261,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,"I can consistently reproduce:
+
+* Saving the page results in an uncaught exception ""Permissions denied"" originating from ve.bind -> $.proxy -> line ""proxy = function () { return fn.apply( ..""
+  Presumably this is caused by IE9 (undocumented?) non-standard security model
+  that rejects certain interaction between functions originating from different
+  http requests (regardless of the origin, e.g. in this case they're both from
+  load.php on the local wiki, no CDN involved)
+
+* Generating a diff (""Review changes"") has a silent failure, no notification
+  is emitted that allows us to hide the spinner or display an error message.",1372031200,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,IE8 and below aren't supported at all (and you shouldn't ever manage to get to use VE with them); assigning.,1370534281,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: Arrow keying off end of throws an exception,"* Move cursor to start/end of document
+* Press left (start) or right (end)
+* An exception is thrown by handleLeftOrRightArrowKey
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370295780,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-b63g5k3ztoignbyr5s5w,task_description,resolved
+VisualEditor: Arrow keying off end of throws an exception,Apparently fixed by gerrit 66322.,1370297945,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b63g5k3ztoignbyr5s5w,task_subcomment,NA
+"VisualEditor: Attribute order preservation is hopeless, get rid of it","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369928220,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wynzwypqafg7laiqaomg,task_description,resolved
+"VisualEditor: Attribute order preservation is hopeless, get rid of it",Related URL: https://gerrit.wikimedia.org/r/68618 (Gerrit Change I1463d06db4900083dd4c565292bbabef09194b43),1371192190,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wynzwypqafg7laiqaomg,task_subcomment,NA
+"VisualEditor: Attribute order preservation is hopeless, get rid of it","It works fine in Chrome, but Firefox does not preserve the order in the attributes array:
+
+
+>>> var div = document.createElement('div')
+undefined
+>>> div.innerHTML='<a href=""foo"" data-parsoid=""bar""></a>';
+""<a href=""foo"" data-parsoid=""bar""></a>""
+>>> div.children[0]
+<a data-parsoid=""bar"" href=""foo"">
+>>> div.children[0].attributes
+[data-parsoid=""bar"", href=""foo""]",1369928377,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wynzwypqafg7laiqaomg,task_subcomment,NA
+VisualEditor: Add support for multi character grapheme clusters in UnicodeJS,"So that we can correctly calculate boundaries in unicode.wordbreak.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1369926300,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vocovg5zyvqjxex3mwtr,task_description,resolved
+VisualEditor: Add support for multi character grapheme clusters in UnicodeJS,Basic support added. Leaving open to work on full grapheme boundary detection.,1370531840,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vocovg5zyvqjxex3mwtr,task_subcomment,NA
+VisualEditor: Add support for multi character grapheme clusters in UnicodeJS,"This is fixed in the above commit, which is merged and will go out with wmf6.",1369932362,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vocovg5zyvqjxex3mwtr,task_subcomment,NA
+VisualEditor: Add support for multi character grapheme clusters in UnicodeJS,Related URL: https://gerrit.wikimedia.org/r/66123 (Gerrit Change I202b98199d2780534d1e02519b72579ba796f08f),1369928399,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vocovg5zyvqjxex3mwtr,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Currently we don't -> lots of broken imagery in /w/index.php etc. entry points.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59196",1369779540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_description,resolved
+VisualEditor: Respect Parsoid's <base>,"Change 90952 merged by jenkins-bot:
+Render resolved URLs for href and src attributes in CE
+
+https://gerrit.wikimedia.org/r/90952",1382986517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Change 86065 merged by jenkins-bot:
+Resolve rendered URLs according to the provided <base>
+
+https://gerrit.wikimedia.org/r/86065",1382985176,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Change 90952 had a related patch set uploaded by Catrope:
+Render resolved URLs for href and src attributes in CE
+
+https://gerrit.wikimedia.org/r/90952",1382383425,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"(In reply to comment #13)
+> Change 86065 had a related patch set uploaded by Catrope:
+> Resolve rendered URLs according to the provided <base>
+> 
+> https://gerrit.wikimedia.org/r/86065
+This addresses the most common symptoms of this bug. It fixes rendering of link targets for internal links (at least on initial rendering; the href attribute doesn't update correctly when the link is edited), and it fixes href and src attributes of things inside of generated content nodes (templates, mostly).
+
+While the change in Gerrit fixes href/src attribute rendering for uneditable href/src attributes, we still have to do something for models that manage their own href/src and edit it, or generate it from another editable attribute.
+
+ve.dm.LinkAnnotation, ve.dm.MWExternalLinkAnnotation: href attribute is edited directly; in practice MWExternalLinkAnnotation is a full URL and LinkAnnotation isn't used in the MW integration, but we should still fix them.
+
+ve.dm.MWInternalLinkAnnotation: Generates href based on title attribute, which can be edited. Links that came directly from Parsoid now render correctly due to a hack (see bug 51487), but edited links don't render correctly.
+
+ve.dm.ImageNode, ve.dm.MWInlineImageNode, ve.dm.MWBlockImageNode: src attribute is edited directly; in practice, the MW ones use full URLs (the user doesn't edit the src directly, and the UI widget gets full URLs from the API) and ImageNode isn't used in the MW integration, but we should still fix them.
+
+ve.dm.MWCategoryMetaItem, ve.dm.MWLanguageMetaItem: these manage hrefs that can be edited, but they're never rendered and always absolute, so we don't really care",1380241433,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Change 86065 had a related patch set uploaded by Catrope:
+Resolve rendered URLs according to the provided <base>
+
+https://gerrit.wikimedia.org/r/86065",1380161671,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 53190 has been marked as a duplicate of this bug. ***,1377727533,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Fun fact: this is the most often duped VE bug ever, and it's in the top 30 of most often duped open bugs on our entire bugzilla, alongside classics such as bug 738 or bug 156. https://bugzilla.wikimedia.org/duplicates.cgi",1377727467,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 53491 has been marked as a duplicate of this bug. ***,1377718799,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 50466 has been marked as a duplicate of this bug. ***,1377445192,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,Also reported today at it.wp (this was the result https://it.wikipedia.org/w/Tsonga_%28popolazione%29 ). Thanks.,1375819931,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"To hopefully help people find this bug, here is the description from bug 51122 ""link targets assumed to be same namespace when opened with ctrl+click"" updated to reflect that it now happens with all links, not just those in image captions:
+
+When opening a link from the editing interface using ctrl+click (or ""open in a new tab"" from the right button menu) the link target is assumed to be in the same namespace as the currently edited page.
+
+For example a link to [[Bridgnorth Cliff Railway]] from the page [[User:Thryduulf/sandbox]] is opened as [[User:Thryduulf/Bridgnorth Cliff Railway]]. A link to [[User:Thryduulf/sandbox2]] on the same page opens [[User:Thryduulf/User%3AThryduulf%2Fsandbox2]]. A link to that sandbox page
+from a page in the article namespace opens as [[User%3AThryduulf%2Fsandbox2]], but this does get you to the correct page.",1375706105,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Come on guys, this is ""high major"" since May.",1375705817,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 51122 has been marked as a duplicate of this bug. ***,1375705754,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 51585 has been marked as a duplicate of this bug. ***,1375705742,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 50764 has been marked as a duplicate of this bug. ***,1372984971,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 50216 has been marked as a duplicate of this bug. ***,1372270074,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Timo says we can get the browser to do the resolution by getting the .href and .src properties in the original Parsoid document, so all we need to do is figure out which attributes are affected. I can think of href and src, are there others?",1369780004,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+"VisualEditor: {Ctrl,Option}+{Delete,Backspace} doesn't delete a word in an RTL wiki","Pressing Ctrl-Backspace deletes a word in a <textarea> in Firefox. It works the same way in VisualEditor when the wiki's language is English, but if it's Hebrew, it only deletes one character.
+
+A GWT testing scenario for this would be something like this:
+
+Given $wgLanguageCode is 'he'
+        And I am editing an article
+        And I wrote 'אחת שתיים שלוש'
+When I press Ctrl-Backspace
+Then the remaining text is 'אחת שתיים '
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369777380,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-xrh4kcflnord5zllknj6,task_description,resolved
+"VisualEditor: {Ctrl,Option}+{Delete,Backspace} doesn't delete a word in an RTL wiki","According to my test, this was fixed, and the behavior is as predicted on my local install. It doesn't work properly in the VE that exists in he.wikipedia, so whatever was done is new.
+
+The fact this works without fixes is incredibly weird, since the handleDelete() function uses offsets, and those are supposed to be opposite between Hebrew and English. I'm checking into potential causes, but as far as I've seen, Inez' re-implemented code works.
+
+Amir, if you can verify this works on your local installation, that'll be helpful. I am a bit concerned about this since it doesn't make sense (it *shouldn't* work) and I am concerned that it doesn't work on he.wiki. I want to verify it isn't some local fluke before we close this bug as resolved.",1371511847,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-xrh4kcflnord5zllknj6,task_subcomment,NA
+"VisualEditor: {Ctrl,Option}+{Delete,Backspace} doesn't delete a word in an RTL wiki","This will (should?) get fixed when Inez does the re-write of this area, but assigning to Moriel to bug him and make sure he does it right. :-)",1369782783,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xrh4kcflnord5zllknj6,task_subcomment,NA
+VisualEditor: Cursor before first character of heading and hitting Enter advances cursor one position,"Place the cursor at the first position of some heading (before the heading's first character). Hit Enter. As expected, an empty line appears before the heading, but the cursor is unexpectedly advanced by one position and is now located *after* the heading's first character.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369603080,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-leu57abgm2tb4hkx7knq,task_description,resolved
+VisualEditor: Cursor before first character of heading and hitting Enter advances cursor one position,*** Bug 50168 has been marked as a duplicate of this bug. ***,1373162663,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-leu57abgm2tb4hkx7knq,task_subcomment,NA
+VisualEditor: Cursor before first character of heading and hitting Enter advances cursor one position,This was fixed and is now deployed.,1372901377,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-leu57abgm2tb4hkx7knq,task_subcomment,NA
+VisualEditor: Block-level media items' placement is incorrect (no clear after thumbs),"Open the VisualEditor on the page https://en.wikipedia.org/wiki/Battle_of_Paris_(1814) . The two images are placed side by side between the lead paragraph and the infobox; they should be placed below the infobox. 
+
+It appears that the VisualEditor generally arranges two images horizontally rather than vertically, unlike the wikitext renderer.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369599780,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-s4cphi53nj54xruaarhy,task_description,resolved
+VisualEditor: Block-level media items' placement is incorrect (no clear after thumbs),This is now fixed in master and will go live from tomorrow.,1371083774,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s4cphi53nj54xruaarhy,task_subcomment,NA
+VisualEditor: Block-level media items' placement is incorrect (no clear after thumbs),*** Bug 49010 has been marked as a duplicate of this bug. ***,1370635551,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s4cphi53nj54xruaarhy,task_subcomment,NA
+VisualEditor: Block-level media items' placement is incorrect (no clear after thumbs),"This is because we haven't been rewriting the image HTML to be like the normal display mode; this is now done for thumbs (you can see it as experimental code on MediaWiki.org) and mostly done for inline images, and will be deployed next week.",1370634398,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s4cphi53nj54xruaarhy,task_subcomment,NA
+VisualEditor: List langlinks (readonly) in the meta-data dialog,"This is to make the categories pane less lonely; we will want to do this 'properly' (writable) later, though this is… challenging given the Wikidata complexities.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369497420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7stkkrpd65tx5rjkp4fg,task_description,resolved
+VisualEditor: List langlinks (readonly) in the meta-data dialog,Related URL: https://gerrit.wikimedia.org/r/67245 (Gerrit Change I897da1cf06c79ee40e29fb632d09cddb57144ada),1370518722,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7stkkrpd65tx5rjkp4fg,task_subcomment,NA
+VisualEditor: List langlinks (readonly) in the meta-data dialog,Now merged and will go out with wmf6.,1370489154,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7stkkrpd65tx5rjkp4fg,task_subcomment,NA
+VisualEditor: List langlinks (readonly) in the meta-data dialog,This is being done in gerrit 65432.,1370462536,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7stkkrpd65tx5rjkp4fg,task_subcomment,NA
+VisualEditor: Content is LTR even when the page language is RTL,"This is using Firefox under Ubuntu 13.x:
+
+
+The problem:
+If the wiki is RTL (Hebrew, for instance), start editing an empty page. The caret appears on the left side and the typing is done LTR.
+
+
+I did a quick check, and noticed that there is a class added to the content box - ""ve-ui-surface mw-content-ltr"" even when the page language is rtl (defined in the <html dir=""rtl""..>
+
+I found this addition in the ve.init.mw.ViewPageTarget line 786:
+this.surface.$.addClass( 'mw-content-' + mw.config.get( 'wgVisualEditor' ).pageLanguageDir );
+
+In my system this produced ""mw-content-ltr"" despite the fact the page language was Hebrew and the html direction was defined as rtl. 
+
+However, I then tried to forcefully change it to rtl, just to test, and while the class appeared correctly (mw-content-rtl), the direction of the typed text was still LTR. It remained LTR when I changed the language to English.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux",1369379280,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-bs4iwunmzd4mvfoqwfmx,task_description,declined
+VisualEditor: Content is LTR even when the page language is RTL,As agreed.,1369782964,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bs4iwunmzd4mvfoqwfmx,task_subcomment,NA
+VisualEditor: Content is LTR even when the page language is RTL,"(In reply to comment #1)
+> Okay, I figured out the problem, but this isn't precisely a bug and it
+> depends
+> on what you want the behavior to be.
+> 
+> First off, the issue seemed to be that the definition of the page language
+> was
+> always LTR in VE, regardless of what language I was using. Even when my page
+> was Hebrew/RTL, VE's config showed it as english/ltr. That was quite
+> frustrating, I was starting to think the problem is that the hooks page reads
+> the language too early (which made no sense, really, since all other
+> extensions
+> read it the same way) 
+> 
+> Not so. Here's the issue:
+> 
+> I didn't notice that when I switched languages in MediaWiki, I did that
+> through
+> my own user preferences (since I was going frequently from English to Hebrew
+> and back for testing). That meant that the *page* and global language was
+> indeed English, and so VE read the global/page language *correctly* as
+> EN/LTR.
+> 
+> So, while I was working in my own rtl preferences, VE corrected me by
+> injecting
+> LTR in there, and switching my marker to the left. 
+> 
+> When I changed the global settings of my wiki to hebrew, it all worked out
+> perfectly again, and all is well.
+> 
+> So now a question for you guys -- this seems to be a decent behavior (though
+> maybe for the sake of users it may be nice to say it somewhere?) -- however,
+> there *is* an option to read the user language instead of the global language
+> in the VisualEditor.hooks.php page, by using the $context->getLanguage()
+> method
+> instead of the currently used $out->getTitle()->getPageLanguage()
+> 
+> That would mean that the direction of the marker will be defined by the
+> *user*
+> defined language rather than by the page- or wiki-defined language
+> direction. 
+> 
+> I can think of reasons this can be good, but I can also think of reasons this
+> can be bad. I am not sure which is better. On one hand, the page probably
+> defines the proper language, and the user language is mostly for the GUI, but
+> on the other, if the user language is RTL, we usually expect the marker to
+> follow suit.
+> 
+> Whatever is decided, this will definitely affect any and all RTL buttons
+> (direction changes for paragraphs/page/etc) and the marker movement (whose
+> bug
+> I was going to look at next.
+> 
+> Should it stay with page language, or switch to user language when deciding
+> marker direction in VE?
+
+I think that the behaviour is as intended - language of content is a wiki-level not user-level decision. This means that if your interface is in RTL but the content is LTR (or vice versa) the buttons need to work in the content context, not the user language, yes. Do they currently not?",1369387531,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bs4iwunmzd4mvfoqwfmx,task_subcomment,NA
+VisualEditor: Content is LTR even when the page language is RTL,"Okay, I figured out the problem, but this isn't precisely a bug and it depends on what you want the behavior to be.
+
+First off, the issue seemed to be that the definition of the page language was always LTR in VE, regardless of what language I was using. Even when my page was Hebrew/RTL, VE's config showed it as english/ltr. That was quite frustrating, I was starting to think the problem is that the hooks page reads the language too early (which made no sense, really, since all other extensions read it the same way) 
+
+Not so. Here's the issue:
+
+I didn't notice that when I switched languages in MediaWiki, I did that through my own user preferences (since I was going frequently from English to Hebrew and back for testing). That meant that the *page* and global language was indeed English, and so VE read the global/page language *correctly* as EN/LTR.
+
+So, while I was working in my own rtl preferences, VE corrected me by injecting LTR in there, and switching my marker to the left. 
+
+When I changed the global settings of my wiki to hebrew, it all worked out perfectly again, and all is well.
+
+So now a question for you guys -- this seems to be a decent behavior (though maybe for the sake of users it may be nice to say it somewhere?) -- however, there *is* an option to read the user language instead of the global language in the VisualEditor.hooks.php page, by using the $context->getLanguage() method instead of the currently used $out->getTitle()->getPageLanguage()
+
+That would mean that the direction of the marker will be defined by the *user* defined language rather than by the page- or wiki-defined language direction. 
+
+I can think of reasons this can be good, but I can also think of reasons this can be bad. I am not sure which is better. On one hand, the page probably defines the proper language, and the user language is mostly for the GUI, but on the other, if the user language is RTL, we usually expect the marker to follow suit.
+
+Whatever is decided, this will definitely affect any and all RTL buttons (direction changes for paragraphs/page/etc) and the marker movement (whose bug I was going to look at next.
+
+Should it stay with page language, or switch to user language when deciding marker direction in VE?",1369387045,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-bs4iwunmzd4mvfoqwfmx,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"Select an inline node (e.g. an inline image) on it's own (i.e. no whitespace either side of it), and trying to copy will throw an exception (ve.dm.Document.js:786 selection[0].range is undefined)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368892860,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_description,resolved
+VisualEditor: Selecting and copying one node throws an exception,Fixed in master; will be deployed on Thursday as part of the regular push.,1377634914,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"Change 80301 merged by jenkins-bot:
+Copy-paste data fixes
+
+https://gerrit.wikimedia.org/r/80301",1377634861,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"Change 80301 had a related patch set uploaded by Jforrester:
+Copy-paste data fixes
+
+https://gerrit.wikimedia.org/r/80301",1377546583,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,https://gerrit.wikimedia.org/r/#/c/80301/ fixes,1377544788,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"Nope, ignore comment 5, it adds the linebreaks no matter which way the selection is generated. Similar outcome but apparently independent.",1374074350,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,The second half of comment 4 might be bug 51538,1374074228,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"No exception now, it just fails to copy at all if you select a focusable node.
+
+In what looks like a separate bug, if you select around a focusable node, pasting creates a new paragraph, e.g.
+
+Foo ""Bar [1] Baz"" Quux
+
+copy range marked with double quotes ([1] is a reference) then paste in the middle of Qu_ux and you get:
+
+Foo Bar [1] Baz Qu
+Bar [1] Baz
+ux
+
+instead of
+
+Foo Bar [1] Baz QuBar [1] Bazux",1373993120,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,I can't reproduce this now in Chrome or Firefox…,1373336346,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"@Ed, @Christian: In which browsers are you guys able to confirm it?",1372710956,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"**orbit** wrote:
+
+ooh... that's true.",1371773691,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Edit triggered repeated inserts of existing text with snowman,"I used VE in Firefox 21.0 on Ubuntu to edit https://www.mediawiki.org/wiki/Backporting_Fixes . I changed a few headings, then pressed Enter between a heading and a numbered list below it to insert a new line (not sure if the caret was on the end of the heading or the start of the first item, I'm not sure if I started typing.
+
+VE began inserting the first sentence of the numbered list but with its link changed to two snowmen, about 15 times. Every time I clicked it would prepend some more.  Even scrolling would trigger this.
+
+Before, the document contained
+
+== WMF Cluster Backports ==
+# Make sure there is a bug registered in [[mw:Bugzilla|Bugzilla]] for the issue.
+
+I couldn't edit the document, but VE's review and save button worked fine. The new document showed as
+
+== ==
+# Make sure there is a bug registered in ☃☃ for the issue.Make sure there is a bug registered in ☃☃ for the issue. <repeated 269 more times>Make sure there is a bug registered in [[mw:Bugzilla|Bugzilla]] for the issue.
+
+I don't know what happened to the heading, I didn't blank it out. I might have attempted a cut and paste, maybe that's what's going haywire, though I'm pretty sure the last thing I did was pressed Enter to add a sentence after the heading.
+
+I assume this is an Easter egg in the VE codebase: if you manipulate the document near an exhortation to file a bug, Parsoid detects it and repeats the phrase, with snow people 8-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368826620,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-lyuwrgvbcgimricw6omw,task_description,resolved
+VisualEditor: Edit triggered repeated inserts of existing text with snowman,"I /believe/ that we fixed this (rather worrying bug) last week with some changes on the CE side; if it recurs, please re-open!",1371147355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lyuwrgvbcgimricw6omw,task_subcomment,NA
+Spaces added before colons and links in some cases,"See https://fr.wikipedia.org/w/index.php?title=COE&diff=prev&oldid=93166267 for example.
+
+I only removed the link, but VisualEditor added a space before the colons.
+
+Another example: https://fr.wikipedia.org/w/index.php?title=MSS&diff=prev&oldid=93166411
+
+There was already two spaces, but VisualEditor added a third.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51024",1368776580,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-dlmzlny66znupvw7flge,task_description,resolved
+Spaces added before colons and links in some cases,"According to a cs.wp editor such changes are intentional, so possibly no need to investigate further. Thanks.",1423674753,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"(Sorry if I'm adding to the wrong task, I think a more relevant one was closed as dupe of this one. I haven't heard from cs.wp yet but it looks like there are [[ https://cs.wikipedia.org/w/index.php?title=Speci%C3%A1ln%C3%AD:Z%C3%A1znam_filtr%C5%AF_zneu%C5%BEit%C3%AD&wpSearchFilter=69 | too many occurrences ]] to be the case, IMHO).",1423496314,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,@Elitre: This doesn't look like space before colons or links .. Could they be null edits / edit undos that might have left behind spaces in VE that Parsoid is preserving?,1423494381,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Can it be this is happening again? At cs.wp [[ https://cs.wikipedia.org/wiki/Speciáln%C3%AD:Filtry_zneužit%C3%AD/69 | they are filtering ]] edits adding extra spaces, like [[ https://cs.wikipedia.org/w/index.php?title=Románská_architektura&diff=prev&oldid=12201516 | this ]] or [[ https://cs.wikipedia.org/w/index.php?title=Ptakopysk&diff=prev&oldid=12204327 | this ]] (I haven't much info ATM).",1423328803,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Change 84701 merged by jenkins-bot:
+(Bug 48570) Fix subtle selser bug handling separator-only nodes
+
+https://gerrit.wikimedia.org/r/84701",1379696165,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,*** Bug 50637 has been marked as a duplicate of this bug. ***,1379613746,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Change 84701 had a related patch set uploaded by Subramanya Sastry:
+(Bug 48570) Fix subtle selser bug handling separator-only nodes
+
+https://gerrit.wikimedia.org/r/84701",1379466252,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Confirmed on simple test case. Investigating.
+---------------------------------------
+
+[subbu@earth tests] echo ""foo : bar"" > /tmp/wt
+[subbu@earth tests] node parse < /tmp/wt > /tmp/old.html
+[subbu@earth tests] cat /tmp/old.html | sed 's/bar/bars/g;' > /tmp/new.html
+[subbu@earth tests] node parse --html2wt --selser --oldtextfile /tmp/wt --oldhtmlfile /tmp/old.html < /tmp/new.html
+foo  : bars",1379461368,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,Bug 51024 has several more examples of this bug occurring if anyone is looking for them.,1379455350,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,*** Bug 51024 has been marked as a duplicate of this bug. ***,1379455266,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,See also bug 51024,1379448597,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Still present: see https://fr.wikipedia.org/w/index.php?title=Julot,_l%27Apache&diff=96678299&oldid=95213076 for example.",1379252830,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"This looks like 1. a Parsoid issue, 2. fixed in master. Reassigning to Parsoid to confirm.",1376931075,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Ignore last comment, should be: Could the fix to bug 52035 be related to this?",1375442806,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,Could the fix to bug 2035 be related to this?,1375442771,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"It's not just ' either, also seen when removing - and "" in my sandbox https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=566841354&oldid=566840716
+
+spaces were added before internal and external links, except in the first instance where a space was added before a colon instead.",1375442619,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"We unfortunately can:
+http://en.wikipedia.org/w/index.php?title=Little_Mosque_on_the_Prairie&diff=prev&oldid=566820635
+
+It seems to be triggered by removal of '.
+Another user verified this (not actually saving, only preview mode) in http://en.wikipedia.org/wiki/Indian_Bank , removing the ' after ""Binny&Co"" would cause a whitespace to be added right before the next wikilink.",1375441882,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"(In reply to comment #0)
+> See https://fr.wikipedia.org/w/index.php?title=COE&diff=prev&oldid=93166267
+> for example.
+> 
+> I only removed the link, but VisualEditor added a space before the colons.
+> 
+> Another example:
+> https://fr.wikipedia.org/w/index.php?title=MSS&diff=prev&oldid=93166411
+> 
+> There was already two spaces, but VisualEditor added a third.
+
+These have been now fixed - sorry for the difficulty.
+
+(In reply to comment #1)
+> The same happens when you edit the first word of a sequence ""word + word +
+> wikilink"", it will add an unnecessary space before the link. Examples,
+> http://it.wikipedia.org/w/index.php?title=Amazon.
+> com&diff=prev&oldid=59604951 - 
+> http://it.wikipedia.org/w/index.php?title=Google&diff=59622535&oldid=59377529
+> (<<talmente popolare ch in  [[lingua inglese|inglese]] >>).
+> This last one is a deliberate vandalism from me to check the issue, I later
+> rollbacked.
+
+I *think* this is also fixed but I'm not absolutely sure; please re-open if you can still reproduce this.",1372017555,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"The same happens when you edit the first word of a sequence ""word + word + wikilink"", it will add an unnecessary space before the link. Examples,
+http://it.wikipedia.org/w/index.php?title=Amazon.com&diff=prev&oldid=59604951 - 
+http://it.wikipedia.org/w/index.php?title=Google&diff=59622535&oldid=59377529 (<<talmente popolare ch in  [[lingua inglese|inglese]] >>).
+This last one is a deliberate vandalism from me to check the issue, I later rollbacked.",1371983634,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368753300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_description,resolved
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"Change 81876 merged by jenkins-bot:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1381186926,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"Change 81876 had a related patch set uploaded by Jforrester:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1378325639,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,*** Bug 50903 has been marked as a duplicate of this bug. ***,1377814666,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"Removing from a milestone; as discussed, we're not going to have time to get to this before next week, and the EventLogging integration needs to be done RSN.",1370566097,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"Setting milestone to 2013-06-27 since it is marked as blocker for ""Beta"" (2013-07). It may be moved to an earlier milestone as we see fit. But no later than 06-27. Setting it since I use milestone to sort ""My bugs"".",1370298479,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,Trevor has some thoughts about this. :-),1368753519,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,"Not sure how to reproduce, but I get two items in the ""Matching categories"" section; I can only move to the top one, and pressing down doesn't work (but pointer-highlighting and selection does).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1368749160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_description,resolved
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,Now fixed by Trevor.,1371002039,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,Related URL: https://gerrit.wikimedia.org/r/68130 (Gerrit Change If48e001b92c217bee0a35b6da41d1c1ff0e3271c),1371001969,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,"(In reply to comment #3)
+> I can't reproduce this on master.
+
+But I can. :-(
+
+Requires two extant (on page and in wiki) categories which start with the same character sequence (I have ""DoG and ""DooooG"")
+
+On suggesting 'd', I get:
+
+New category
+  d
+Move this category here
+Matching categories     <--- This should not be here at all
+  DoG                   <--- This should be in the ""Move this category here"" block
+  DooooG                <--- This should also be in ""Move this category here""",1371000702,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,I can't reproduce this on master.,1370978406,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,Seemingly not; Trevor investigating.,1369407946,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,Now fixed in master.,1369404163,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1368747960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-koardc3to3cjpsgjsemv,task_description,resolved
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,Related URL: https://gerrit.wikimedia.org/r/65314 (Gerrit Change Ie87a3c7dde2f29c3898c08d4cade5c0ba2f937dd),1369420191,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-koardc3to3cjpsgjsemv,task_subcomment,NA
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,Merged and will go out in wmf5.,1369416082,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-koardc3to3cjpsgjsemv,task_subcomment,NA
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,Related URL: https://gerrit.wikimedia.org/r/65303 (Gerrit Change Ibf63329a53bcd8043d46315239c19be4e681a18a),1369410443,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-koardc3to3cjpsgjsemv,task_subcomment,NA
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,"We will also want to kill the non-Category panels (or populate them, if you're feeling sprint-y).",1368748032,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-koardc3to3cjpsgjsemv,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"Do we need to trigger a re-render of the catlinks div? Can we?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52403",1368747000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2astjxmuxt2yyso6g3kb,task_description,resolved
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,Verified the fix on test 2,1389901362,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"Change 107036 merged by jenkins-bot:
+Update categories HTML on page save
+
+https://gerrit.wikimedia.org/r/107036",1389638149,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"Change 107036 had a related patch set uploaded by Esanders:
+Update categories HTML on page save
+
+https://gerrit.wikimedia.org/r/107036",1389536961,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,*** Bug 57924 has been marked as a duplicate of this bug. ***,1386089449,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"Note that the categories on the page are not refreshed even after multiple VE sessions.  i.e. VE add category -> save -> VE add category -> save : results in a page that _displays_ only the categories at the beginning of the process.
+
+Categories added via templates are also not displayed.",1384389210,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,*** Bug 56683 has been marked as a duplicate of this bug. ***,1383767137,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,*** Bug 50737 has been marked as a duplicate of this bug. ***,1373556875,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,*** Bug 50072 has been marked as a duplicate of this bug. ***,1372036218,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"It depends on what we get back from the server.
+
+If we get back something that is compatible with what api.php?action=parse gives (prop.categorieshtml, from Skin::getCategories), which is what live preview in core uses as well, then we can just update it by replacing the old with the new html.
+
+If we can't get that, we'll have to re-implement Skin::getCategories in javascript. However I'd like to avoid that since it is skin-specific (skins can do all kinds of weird stuff to it, hard to predict. Ideally this would fall under the parts of the page output (like mw-content-text, htmlhead and script loader) that has a fixed html layout that skins can't alter the html itself of (it has enough css hooks to style anyway they like, they shouldn't need to modify the html). But that's not the reality.
+
+--
+
+Oh wait, this isn't from the server (not MediaWiki, not Parsoid). I mean, it shouldn't. This is reflected live when editing the document. We'll have to do it in javascript somehow I'm afraid.",1370851294,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Clicking link button while link inspector is already open throws error,"The button should probably not do anything if the inspector is already open.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368737040,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-7d3wwwbypeipgqn42o5c,task_description,resolved
+VisualEditor: Clicking link button while link inspector is already open throws error,Merged and will go out with wmf5.,1369256685,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7d3wwwbypeipgqn42o5c,task_subcomment,NA
+VisualEditor: Clicking link button while link inspector is already open throws error,Related URL: https://gerrit.wikimedia.org/r/64818 (Gerrit Change Ia97b6e3d862e02f5c55cac3f490fd8f26052027a),1369150090,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7d3wwwbypeipgqn42o5c,task_subcomment,NA
+VisualEditor: Image resize handles persist on close,"If the image has focus when you click back on the 'Read' tab, the four circles stay on the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368698040,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2nyantno3ds7ohrifauv,task_description,resolved
+VisualEditor: Image resize handles persist on close,Merged and will go out with wmf5.,1369454138,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2nyantno3ds7ohrifauv,task_subcomment,NA
+VisualEditor: Image resize handles persist on close,Related URL: https://gerrit.wikimedia.org/r/64917 (Gerrit Change I807a0f32d3d1eb490456d887f7bf867bdb896df4),1369220160,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2nyantno3ds7ohrifauv,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,"Once it exists being the relevant part. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368662820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_description,resolved
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,"Change 127362 merged by jenkins-bot:
+Use Parsoid API for action=parsefragment
+
+https://gerrit.wikimedia.org/r/127362",1397866425,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,"Change 127362 had a related patch set uploaded by Esanders:
+Use Parsoid API for action=parsefragment
+
+https://gerrit.wikimedia.org/r/127362",1397852463,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,Does the API actually exist yet?,1397845488,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,This should be done sooner rather than later.,1394493707,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,*** Bug 62516 has been marked as a duplicate of this bug. ***,1394493657,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,https://www.mediawiki.org/wiki/Parsoid#The_Parsoid_web_API has the API docs.,1386358351,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,More detail please?,1386336562,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,Not going to make beta at this rate.,1371780475,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,"In ve.init.mw.ViewPageTarget.prototype.tearDownToolbar, this.toolbar is undefined if the editor hasn't finished loading.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368653280,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-f3bksoxide4n4n2plcfg,task_description,resolved
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,Merged; will go out with wmf5.,1368885093,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f3bksoxide4n4n2plcfg,task_subcomment,NA
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,Related URL: https://gerrit.wikimedia.org/r/64333 (Gerrit Change Ide5def0e983bab49108b40008fc170957c7fc2a2),1368809326,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f3bksoxide4n4n2plcfg,task_subcomment,NA
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,"Actually, this is distinct.",1368655857,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f3bksoxide4n4n2plcfg,task_subcomment,NA
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,"
+
+*** This bug has been marked as a duplicate of bug 47813 ***",1368654670,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f3bksoxide4n4n2plcfg,task_subcomment,NA
+VisualEditor: MWLinkTargetInputWidget should grok case sensitivity of suggested page title vs. the inputed text,"Screenshot of problem
+
+Scenario:
+* Document contains "" ... esams ... ""
+* Wiki has a page called ""Esams"".
+* Wiki does not have case-sensitive first character in the main namespace.
+* Select ""esams"" and turn it into a link
+* UI shows:
+  [ esams            ]
+  New page:
+    <redlink> esams
+  Matching page:
+    Esams
+    Esams cluster
+    Esams patches
+
+That first redlink is incorrect, it should show the same as when the input is ""Esams"" (with capital E), namely no ""redlink"" since the first match is in fact the input.
+
+It needs to account for the $wgCapitalLinkOverrides and $wgCapitalLinkOverrides configuration etc. This is abstracted in PHP by MWNamespace::isCapitalized, which is exposed in javascript as 'wgCaseSensitiveNamespaces' in mw.config.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F10838}",1368573360,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ukhmjz446wmy32ws4rzz,task_description,resolved
+VisualEditor: MWLinkTargetInputWidget should grok case sensitivity of suggested page title vs. the inputed text,Related URL: https://gerrit.wikimedia.org/r/64867 (Gerrit Change I66f5fc56554984af58d6223dc6cd76b3ab9940bd),1369174848,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ukhmjz446wmy32ws4rzz,task_subcomment,NA
+VisualEditor: MWLinkTargetInputWidget should grok case sensitivity of suggested page title vs. the inputed text,"Basically any normalisation causes this bug.
+
+also things like user:krinkle -> User:Krinkle, and localized namespaces and alias namespaces (Image>File).",1369174621,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ukhmjz446wmy32ws4rzz,task_subcomment,NA
+VisualEditor: MWLinkTargetInputWidget should grok case sensitivity of suggested page title vs. the inputed text,*** Bug 48433 has been marked as a duplicate of this bug. ***,1368720868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ukhmjz446wmy32ws4rzz,task_subcomment,NA
+VisualEditor: Heading on a slug is created on the wrong line in Firefox,"1 Go to a page with several paragraphs. Edit with VisualEditor.
+
+2. Place cursor at the end of paragraph N and press Enter to create a new line. See the cursor blinking in a new line after paragraph N.
+
+3. Select ""Heading 2"" in the dropdown menu.
+
+EXPECTED
+
+A Heading 2 line appears at the end of paragraph N.
+
+
+ACTUAL OUTCOME
+
+A Heading 2 line appears at the end of paragraph N-1.
+
+
+As a matter of fact I find no way to place the header where I want, unless going to the end of paragraph N+1 only to trick the bug. Selecting an existing line and trying to make a header out of it doesn't seem to work either (but this is probably a different bug).
+
+Happens at least in mediawiki.org with Firefox 22.0a2 (2013-05-07).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368554100,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-frnef4dwspf2gymmanpq,task_description,resolved
+VisualEditor: Heading on a slug is created on the wrong line in Firefox,"(In reply to comment #2)
+> Yes, this works now. Thank you!
+> 
+> Just a little usability detail: after selecting the type of heading there is
+> no
+> cursor blinking. You can type and characters will appear where expected, but
+> of
+> course our old friend cursor-blinking is missed.
+
+Yes; Rob noticed this too, and is working on it - just created bug 50338 to track.",1372384505,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-frnef4dwspf2gymmanpq,task_subcomment,NA
+VisualEditor: Heading on a slug is created on the wrong line in Firefox,"Yes, this works now. Thank you!
+
+Just a little usability detail: after selecting the type of heading there is no cursor blinking. You can type and characters will appear where expected, but of course our old friend cursor-blinking is missed.",1372375315,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-frnef4dwspf2gymmanpq,task_subcomment,NA
+VisualEditor: Heading on a slug is created on the wrong line in Firefox,I believe we've fixed this now in production - please re-open if it recurs.,1372371426,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-frnef4dwspf2gymmanpq,task_subcomment,NA
+VisualEditor: Remove alpha notice,"When I go to use the VisualEditor (e.g., <https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals> --> click ""edit""), there's a bothersome notice every time the VisualEditor form loads about how it's the alpha version of the tool. There's no way to dismiss the notice and it gets a bit grating after a while.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1368496800,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_description,resolved
+VisualEditor: Remove alpha notice,Merged and will go out with wmf7 tomorrow.,1371057658,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_subcomment,NA
+VisualEditor: Remove alpha notice,Related URL: https://gerrit.wikimedia.org/r/68128 (Gerrit Change I725beec4e76dadfb1ccca873758f8f37b7f58a73),1370999898,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_subcomment,NA
+VisualEditor: Remove alpha notice,Change-Id: Ie289c39b963072e8a20aa29926dee1d199b6e4e8,1370298333,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_subcomment,NA
+VisualEditor: Remove alpha notice,"To do just before the ""alpha"" becomes a ""beta"".",1368497309,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_subcomment,NA
+VisualEditor: Pre-beta needs (tracker),"Tracker for the bugs/enhancements that should be done for the beta.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368493800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tzlbyq77mfgatrefsaj3,task_description,invalid
+VisualEditor: Pre-beta needs (tracker),[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343629,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tzlbyq77mfgatrefsaj3,task_subcomment,NA
+VisualEditor: Pre-beta needs (tracker),Bugs tracking bugs that track bugs aren't hugely useful; let's kill this one.,1393640096,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tzlbyq77mfgatrefsaj3,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,"[[:File:SpecialPage_Filter_JS.png]]
+
+is being converted to:
+
+<a rel=""mw:Image"" href=""../File:SpecialPage_Filter_JS.png"" data-parsoid=""{&quot;tsr&quot;:[21446,21481],&quot;src&quot;:&quot;[[:File:SpecialPage Filter JS.png]]&quot;,&quot;dsr&quot;:[21446,21481,null,null]}""><img src=""../Special:FilePath/SpecialPage_Filter_JS.png?width=200"" alt=""SpecialPage_Filter_JS.png"" width=""200"" style=""vertical-align: middle;"" data-parsoid=""{}""></a>
+
+It should be an <a> without the <img> inside it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://parsoid.wmflabs.org/mw/User:Dantman/Code_Ideas",1368389040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_description,resolved
+Images: Image links are interpreted as image inclusions,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934030,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,*** Bug 49891 has been marked as a duplicate of this bug. ***,1371769152,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,Fixed by https://gerrit.wikimedia.org/r/#/c/69612/.,1371764117,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,"(In reply to comment #2)
+> This affects VisualEditor on the English Wikipedia.
+
+I'm adding bug 48426 as a blocker.",1370921421,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,*** Bug 49384 has been marked as a duplicate of this bug. ***,1370883912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,*** Bug 48669 has been marked as a duplicate of this bug. ***,1369114571,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,This affects VisualEditor on the English Wikipedia.,1368981137,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,*** Bug 48596 has been marked as a duplicate of this bug. ***,1368979809,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+VisualEditor: Whitespace preservation for auto-links not working sometimes(?),"Putting this in DM because it seems the most likely suspect.
+
+Original bug occurred on enwiki (text in the test stolen from there). This feels like a bit of bug 43543 - which was fixed?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=VisualEditor:TestAutolinks&diff=688670&oldid=688669",1368315240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-miessklckuwapsejbpw4,task_description,resolved
+VisualEditor: Whitespace preservation for auto-links not working sometimes(?),"Confirmed as fixed in master.
+
+*** This bug has been marked as a duplicate of bug 43543 ***",1368379914,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-miessklckuwapsejbpw4,task_subcomment,NA
+VisualEditor: Can't delete-merge two paragraphs together if the first one ends with an inline-alien,"This was happening with <ref>s, but it looks like it'll be an issue with an paragraph that ends with an inline alien:
+
+| Foo.<ref>Ref</ref>
+| Bar.
+
+Backspace with the cursor to the left of the 'B', or delete with the cursor to the right of the <ref> block, has no effect.
+
+The problem with <ref>s will go away(?) when that node handler code is enabled, but is this a wider issue?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368313200,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lyjnjxdzskobjhrp4tgf,task_description,resolved
+VisualEditor: Can't delete-merge two paragraphs together if the first one ends with an inline-alien,This seems to be not an issue anymore - since I rewrote handleDelete method.,1372369220,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-lyjnjxdzskobjhrp4tgf,task_subcomment,NA
+VisualEditor: Re-factor key detection to be more robust and not occasionally break/pawn in Firefox,"Inez has some ideas about how to do this, so marking to him for now. Would be nice to document here /home/ we want to do this so someone can pick it up at some point. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1368215940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6w7ima76rbpczpaozizw,task_description,resolved
+VisualEditor: Re-factor key detection to be more robust and not occasionally break/pawn in Firefox,Now merged and will go out with wmf8 from Thursday 20 June.,1371180920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6w7ima76rbpczpaozizw,task_subcomment,NA
+VisualEditor: Re-factor key detection to be more robust and not occasionally break/pawn in Firefox,https://gerrit.wikimedia.org/r/68296 (Gerrit Change Ie00becf1162f145134f006b0b4514ba874de9c43) | change APPROVED and MERGED [by jenkins-bot],1371180886,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6w7ima76rbpczpaozizw,task_subcomment,NA
+VisualEditor: Re-factor key detection to be more robust and not occasionally break/pawn in Firefox,Related URL: https://gerrit.wikimedia.org/r/68296 (Gerrit Change Ie00becf1162f145134f006b0b4514ba874de9c43),1371074644,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6w7ima76rbpczpaozizw,task_subcomment,NA
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,"Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
+Put the cursor somewhere in the text.
+Type ""Enter"" 2 times.
+Type ""Up"".
+Type a
+Type Enter
+Type b
+Type Up
+Type Left
+Press Shift and hold it
+Type Down
+
+Expected: selection of 1 line
+Actually: selection of 2 lines
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368090660,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_description,resolved
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,Fixed in the above.,1372465847,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_subcomment,NA
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,"Change 71143 merged by jenkins-bot:
+Firefox misplaces cursor when moving between lines
+
+https://gerrit.wikimedia.org/r/71143",1372465519,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_subcomment,NA
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,"Change 71143 had a related patch set uploaded by Christian:
+Firefox misplaces cursor when moving between lines
+
+https://gerrit.wikimedia.org/r/71143",1372459066,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_subcomment,NA
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,Can confirm in Firefox (and not in Chrome); it sometimes occurs upwards as well as downwards.,1368130754,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_subcomment,NA
+VisualEditor: Tab in a slug in Firefox causes a pawn character to be inserted,"Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
+Put the cursor somewhere in the text.
+Type ""Enter"" 2 times.
+Type ""Up"".
+Type ""Tab""
+
+Wild pawn appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368090300,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-7v5fwi2od2mzskuipoyb,task_description,resolved
+VisualEditor: Tab in a slug in Firefox causes a pawn character to be inserted,"This is a duplicate of bug 48022 which was fixed for wmf4 (so should now work beautifully on enwiki). Sorry for the delayed response.
+
+*** This bug has been marked as a duplicate of bug 48022 ***",1369093388,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7v5fwi2od2mzskuipoyb,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,"Examining with user what browser/etc. to investigate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: http://en.wikipedia.org/w/index.php?title=Indo-Pakistani_War_of_1965&diff=prev&oldid=552704403",1367950620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vqvckkamqnznu7z5ud6j,task_description,resolved
+VisualEditor: Dirty diffs causing some citations to be duplicated,"On review, this is already fixed in master and will be deployed (as part of wmf4) to the English Wikipedia on 20 May.",1368803220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,"(In reply to comment #4)
+> To me it looks like the VE is dropping a link (with template encapsulation
+> info) near '165 Pakistan tanks' when editing
+> http://en.wikipedia.org/w/index.php?title=Indo-
+> Pakistani_War_of_1965&oldid=551447483.
+> So it looks like a VE bug to me. Can you verify?
+That bug is fixed in the most recent VE release, which is live on mw.org but hasn't hit enwiki yet. Compare https://en.wikipedia.org/wiki/User:Catrope/India-Pakistan and https://www.mediawiki.org/wiki/User:Catrope/India-Pakistan .",1368773561,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,To me it looks like the VE is dropping a link (with template encapsulation info) near '165 Pakistan tanks' when editing http://en.wikipedia.org/w/index.php?title=Indo-Pakistani_War_of_1965&oldid=551447483. So it looks like a VE bug to me. Can you verify?,1368724692,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,Can you provide us with a test case and verify that the DOM change looks sane?,1368720633,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,"Gabriel - As far as I can tell, this bug is coming from Parsoid rather than VisualEditor - can you confirm? I can replicate in VE and Parsoid master locally.",1368720428,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,"There was a Parsoid bug to this effect earlier, maybe it came back?",1367950671,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Typing at the end of linked causes DM and CE to get out of sync,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367866920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zzjrcgydauwz7h5g6ufd,task_description,resolved
+VisualEditor: Typing at the end of linked causes DM and CE to get out of sync,Trevor's commit has been merged; assigning to Inez for the IE-specific fixes to come.,1367886453,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zzjrcgydauwz7h5g6ufd,task_subcomment,NA
+VisualEditor: Typing at the end of linked causes DM and CE to get out of sync,Related URL: https://gerrit.wikimedia.org/r/62481 (Gerrit Change I5f279b06b098960be7bd4ad3f5e6f74b67e31d1a),1367870942,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zzjrcgydauwz7h5g6ufd,task_subcomment,NA
+VisualEditor: Typing at the end of linked causes DM and CE to get out of sync,"This doesn't happen in IE.
+
+1. Place the cursor at the end of a link.
+2. Type some text
+3. See that the text doesn't appear to be linked, but the link inspector option is available
+
+Short term solution as decided by Trevor, Inez and James: Make links not auto-extend in the model, and fix IE so it doesn't auto-extend in the view (to make it work like other browsers).",1367867552,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-zzjrcgydauwz7h5g6ufd,task_subcomment,NA
+VisualEditor: Unexpected non-pawn characters appear after CTRL-B and CTRL-I,"unexpected untyped characters
+
+Upon loading page in VE: 
+
+Click CTRL-B and type some characters; 
+click CTRL-I and type some characters; 
+
+* often but not always reproducible, seen in Chrome/OSX, also reported in IE and FF: upon typing after ctrl-B or ctrl-I for ""bold"" or ""italic"", characters appear that have not been entered.  see screen shot
+
+* possibly related, seen but not reproducible:  some combination of actions will cause VE to type a string into a page over and over and over without any action on the part of the user.  I'll file a new bug if I can figure out how to repron that behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11070}",1367863980,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-zoij2t4he6jsr6wfqjde,task_description,resolved
+VisualEditor: Unexpected non-pawn characters appear after CTRL-B and CTRL-I,I believe we fixed this with the new insertion logic last week. Please re-open if you can reproduce still.,1371781126,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zoij2t4he6jsr6wfqjde,task_subcomment,NA
+VisualEditor: Unexpected non-pawn characters appear after CTRL-B and CTRL-I,@James: Feel free to assign to me.,1367864226,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-zoij2t4he6jsr6wfqjde,task_subcomment,NA
+VisualEditor: Pre-annotations not working in spans,"From this bug report on parsoid.wmflabs.org: /mnt/bugs/2013-05-04T01:11:28.439Z-Style_guide%252FAssets_and_gallery
+
+""I typed some text in this paragraph that is styled as a span italic, and VE decided to close and reopen the span on either side of the link. I think that happened before I made the text a link. (This is User:S Page (WMF) here.)""
+
+Relevant diff line below:
+
+− 	
+:<span style=""font-style: italic;"">See Also: [[Commons:Category:MediaWiki style guide]]</span>
+
++ 	
+:<span style=""font-style: italic;"">See also: </span>[[Wikimedia Foundation Design/Agora Icon Set]] and<span style=""font-style: italic;""> [[Commons:Category:MediaWiki style guide]]</span>
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1367852460,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_description,resolved
+VisualEditor: Pre-annotations not working in spans,"(In reply to comment #3)
+> Can you explain more clearly how this is still broken? What do you mean by
+> pre-annotation?
+
+On re-testing, this comes down to copy-and-paste inserted content not continuing the existing annotations of the styles into which it had been inserted. Marking as such.
+
+*** This bug has been marked as a duplicate of bug 48720 ***",1369247921,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_subcomment,NA
+VisualEditor: Pre-annotations not working in spans,Can you explain more clearly how this is still broken? What do you mean by pre-annotation?,1369221776,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_subcomment,NA
+VisualEditor: Pre-annotations not working in spans,"OK, we've fixed the secondary issues I was having; have narrowed down the original bug to pre-annotations not being applied to the insertion of text into this context - changing this to suit.",1368719960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_subcomment,NA
+VisualEditor: Pre-annotations not working in spans,"I think that this partially interacts was a bug that Ed found independently - bug 48110 (now fixed in master). I do not get the span adjusted, but instead get:
+
+:<span style=""font-style: italic;"">See Also: <a href=""Wikimedia_Foundation_Design%2FAgora_Icon_Set"" rel=""mw:WikiLink"">Wikimedia Foundation Design/Agora Icon Set</a> and [[Commons:Category:MediaWiki style guide|<nowiki/>]]<a href=""Commons%3ACategory%3AMediaWiki"" rel=""mw:WikiLink"">Commons:Category:MediaWiki</a> style guide</span>
+
+... which is a total mess.",1367876474,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_subcomment,NA
+VisualEditor: [Regression] Link insertion annotation makes it difficult to add plain text after a link,"If you add a link to the last word in your paragraph (quite common I'd imagine if you're in the middle of typing a sentence), the insertion annotation behaviour makes any text typed after the link part of that link - which in most cases is not what you meant to do.
+
+Insertion annotations make sense for text style annotations, but not link annotations. This is what Google Docs & LibreOffice do aswell.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367794320,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hwpwpa3athddhod7xlp4,task_description,resolved
+VisualEditor: [Regression] Link insertion annotation makes it difficult to add plain text after a link,Fixed by https://gerrit.wikimedia.org/r/#/c/62481/,1368373764,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hwpwpa3athddhod7xlp4,task_subcomment,NA
+VisualEditor: [Regression] Link insertion annotation makes it difficult to add plain text after a link,"This is a regression - it used to be that there were two types of annotations - one (bold/italics/etc.) would pre-annotate over word breaks, and the other wouldn't. I believe that the code to do this used to sit in CE - has it been removed, or is it not working somehow?",1367808687,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hwpwpa3athddhod7xlp4,task_subcomment,NA
+"VisualEditor: Access keys - leave Ctrl+Option+e for the (newly-relabelled) ""edit source"" tab; Add Ctrl+Option+v for the VisualEditor ""edit"" tab","Currently we steal all the things on action=edit for veaction=edit (so Ctrl-Option-e goes to VisualEditor, leaving nothing for the wikitext editor). We should add a new one - Ctrl-Option-s (for *s*ource) - though that's used for save in the wikitext editor, which is a bit odd. Ideas?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1367769060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhuq2co3arbcvjn3js5m,task_description,resolved
+"VisualEditor: Access keys - leave Ctrl+Option+e for the (newly-relabelled) ""edit source"" tab; Add Ctrl+Option+v for the VisualEditor ""edit"" tab",Fixed in master.,1368232252,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhuq2co3arbcvjn3js5m,task_subcomment,NA
+"VisualEditor: Access keys - leave Ctrl+Option+e for the (newly-relabelled) ""edit source"" tab; Add Ctrl+Option+v for the VisualEditor ""edit"" tab",Related URL: https://gerrit.wikimedia.org/r/63231 (Gerrit Change I598177bc75ed84dea35952a3b2b1b2111aac89b2),1368223225,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uhuq2co3arbcvjn3js5m,task_subcomment,NA
+"VisualEditor: Access keys - leave Ctrl+Option+e for the (newly-relabelled) ""edit source"" tab; Add Ctrl+Option+v for the VisualEditor ""edit"" tab","Change of plans:
+* Leave -e for the wikitext editor tab
+* Add -v for the VisualEditor tab",1368209183,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhuq2co3arbcvjn3js5m,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"I changed a link here: http://sv.wikipedia.org/w/index.php?title=Intellektuell_s%C3%A4rbeg%C3%A5vning&diff=21539781&oldid=21539483
+
+In the VisualEditor interface, the word ""Känsla"" is showed with a lower case k, but when you are looking at the article, or source it is K.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367618160,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_description,resolved
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"(In reply to comment #4)
+> As we're generating the correct HTML surely this is just a Parsoid bug, not a
+> VE bug.
+
+Yeah, point.
+
+*** This bug has been marked as a duplicate of bug 48477 ***",1368631481,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"As we're generating the correct HTML surely this is just a Parsoid bug, not a VE bug.",1368628645,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],Depends on a Parsoid regression being fixed.,1368574562,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"I just hit the same again.
+
+* Text ""foo"".
+* Link it, page ""Foo"" exists.
+* Close link editor.
+* Page shows ""text <a href=""./Foo"">foo</a> text"".
+* Saving turns it into [[Foo]], thus ignoring the case of the label.",1368573811,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"Thank y(In reply to comment #0)
+> I changed a link here:
+>
+> http://sv.wikipedia.org/w/index.php?diff=21539781&oldid=21539483
+> 
+> In the VisualEditor interface, the word ""Känsla"" is showed with a lower case
+> k, but when you are looking at the article, or source it is K.
+
+Thank you for your bug report, Jan! Hope to get this fixed soon.",1367895881,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Pawn characters created when moving cursors around inline images in Firefox,"All the pawns
+
+See attached image, basically the idea is that indenting or de-indenting a list item will cause there to be a pawn in the list item. Also, when I used the arrow keys to navigate past some images, it put pawns next to the images.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10767}",1367532360,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-sw2uw4ekzaqwybdqmbq6,task_description,resolved
+VisualEditor: Pawn characters created when moving cursors around inline images in Firefox,This is now fixed in wmf4 (which is the current in-production version); marking as such.,1369098863,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sw2uw4ekzaqwybdqmbq6,task_subcomment,NA
+VisualEditor: Pawn characters created when moving cursors around inline images in Firefox,"Nothing about the list or indenting, just the cursor keys trigger it (Firefox only).",1367545948,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sw2uw4ekzaqwybdqmbq6,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",The order should be Edit then Edit tab. Looks like a hard-coded left somewhere?,1367527740,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_description,resolved
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381217 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.init.mw.DesktopArticleTarget: Fix the code to reorder tabs
+
+[[https://gerrit.wikimedia.org/r/381217]]
+",1506613751,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381217 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.init.mw.DesktopArticleTarget: Fix the code to reorder tabs
+
+[[https://gerrit.wikimedia.org/r/381217]]
+",1506606897,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","After trying to verify the fix during the SWAT deployment, I found out that this entire feature (fixing up the tab order if wgVisualEditorTabPosition was changed and we're seeing cached HTML with the tabs in wrong order) is actually entirely broken and just does nothing. The deployment was essentially a no-op. This is actually convenient because had it worked, it would have been messing up the tabs.",1506606636,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AV7ItYHmF4fsM4DBdIoK} [2017-09-28T13:38:12Z] <zfilipin@tin> Synchronized php-1.31.0-wmf.1/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.DesktopArticleTarget.init.js: SWAT: [[gerrit:381210|ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector (T50017)]] (duration: 00m 50s)",1506605892,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381210 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@wmf/1.31.0-wmf.1] ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector
+
+[[https://gerrit.wikimedia.org/r/381210]]
+",1506604497,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381210 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@wmf/1.31.0-wmf.1] ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector
+
+[[https://gerrit.wikimedia.org/r/381210]]
+",1506602050,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381167 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector
+
+[[https://gerrit.wikimedia.org/r/381167]]
+",1506589079,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",(This will need to be backported to 1.31.0-wmf.1.),1506577515,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381167 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector
+
+[[https://gerrit.wikimedia.org/r/381167]]
+",1506576918,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","With the underlying issue T48947 being fixed, our workaround is now unnecessary and in fact reintroduces this issue. We should remove it.",1506576890,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",*** Bug 47684 has been marked as a duplicate of this bug. ***,1368639099,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",Merged into master.,1368232328,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",Related URL: https://gerrit.wikimedia.org/r/63153 (Gerrit Change Ie1214b08450aefed893739a2b862cb1e9b23a2ef),1368210908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","This is caused by bug 46947 – the HTML order of tabs is reversed, then reversed again in the CSS...",1367527956,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,"There are probably two solutions - make it work - or disable list buttons while in block slug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367431680,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-ht3d5xeklsjuq5qulguj,task_description,resolved
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,Fixed and will be deployed later today.,1372704235,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,"Change 71353 merged by jenkins-bot:
+Allow creating lists in block slugs
+
+https://gerrit.wikimedia.org/r/71353",1372704109,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,"Change 71353 had a related patch set uploaded by Jforrester:
+(bug 47947) Allow creating lists while selection is collapsed and in block slug
+
+https://gerrit.wikimedia.org/r/71353",1372691992,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,"Change 71353 had a related patch set uploaded by Inez:
+(bug 47947) Allow creating lists while selection is collapsed and in block slug
+
+https://gerrit.wikimedia.org/r/71353",1372689599,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,*** Bug 50242 has been marked as a duplicate of this bug. ***,1372271165,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,Make it work is better. :-),1367545095,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: heading removal adds ♙,"The user was trying to edit http://de.wikipedia.org/w/index.php?title=Reiniger,_Gebbert_%26_Schall&direction=prev&oldid=117917379 to remove the first heading but keep the image. The result was http://de.wikipedia.org/w/index.php?title=Reiniger,_Gebbert_%26_Schall&direction=next&oldid=103767568 and the didn't manage to do it without adding the ♙.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367427120,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_description,resolved
+VisualEditor: heading removal adds ♙,I think our changes related to pawns also has fixed this bug; marking as closed.,1368548559,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,"Sorry, yes. It's Firefox (20.0.1, Windows 7).
+
+Steps to reproduce according to user:
+* open http://de.wikipedia.org/w/index.php?title=Reiniger,_Gebbert_%26_Schall&oldid=103767568
+* edit with VisualEditor
+* select first heading ""Aufbau und Expansion des Unternehmens""
+* remove using del-key
+* ♙ appears",1368536309,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,Lydia: Any response on that?,1368216819,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,I asked at http://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Alpha2013-04#Absatzmarker_.28.E2.99.99.29,1367511693,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,I think it might be the FF specific bug for which we already have fix (but it is not released yet).,1367434380,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,Could you provide steps to reproduce (I tried and I can't) and information about browser/OS?,1367430685,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: Support <div> blocks,"This just means supporting their use, not being able to set their parameters, but will de-alienate a large amount of content for trivial work at our end. The parameter setting/editing will need to come later.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1367371680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-erliezrdqnohfykefn5r,task_description,resolved
+VisualEditor: Support <div> blocks,Merged; will go out with wmf4.,1367372802,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-erliezrdqnohfykefn5r,task_subcomment,NA
+VisualEditor: Support <div> blocks,"(In reply to comment #1)
+> Feel free to assign it to me.
+
+Too late, already written the code. :-)",1367372023,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-erliezrdqnohfykefn5r,task_subcomment,NA
+VisualEditor: Support <div> blocks,Related URL: https://gerrit.wikimedia.org/r/61737 (Gerrit Change I794927a881082e0113c0ce8ee8f1d908b0960899),1367371959,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-erliezrdqnohfykefn5r,task_subcomment,NA
+VisualEditor: Support <div> blocks,Feel free to assign it to me.,1367371782,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-erliezrdqnohfykefn5r,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","Screenshot of LQT thread with </div> in title
+
+Should be treated the same as regular page titles: Escape everything.
+
+
+Or, if we want to keep wikitext parsing (e.g. for wikilinks, sometimes done in section headings), then parse as inline block (not allowing any block level elements like <div> or <table>) and make sure open/close tags match (run Tidy).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://www.mediawiki.org/wiki/Thread:Project:Support_desk/visible_html_on_pages%3A
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=31244
+https://bugzilla.wikimedia.org/show_bug.cgi?id=29564
+
+**Attached**: {F10533}",1367340180,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_description,invalid
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true",[We don't use Tidy anymore](https://www.mediawiki.org/wiki/Parsing/Replacing_Tidy) since 2016,1644958499,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","Suggest decline this task, such problem are mostly from PHP which is a bit more #upstream ed",1553220752,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","Suggest decline this task, such problem are mostly from PHP which is a bit more #upstream-ed",1553220744,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","LiquidThreads has been replaced by #Flow on all Wikimedia production wikis (except one, which will be done soon). It is no longer under active development or maintenance, so I'm re-classifying all open LQT tasks as ""Lowest"" priority.",1470353645,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","A similar problem in a topic named ""Handling <pre><ref></pre> with trailing slash does not work correctly"":
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Handling_ref_with_trailing_slash_does_not_work_correctly",1413467796,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true",This is one of the many places with poor or inconsistent escaping in LQT.,1377841711,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","(In reply to comment #1)
+> @Krenair: You change the summary to include ""with wgUseTidy = true;"" Are you
+> saying that when Tidy is disabled this bug does not happen?
+
+
+Yes. I have to add that to my configuration to replicate this bug.",1367358730,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","@Krenair: You change the summary to include ""with wgUseTidy = true;"" Are you saying that when Tidy is disabled this bug does not happen?
+
+Seems more like the opposite?",1367355713,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+VisualEditor: Blanked page content in edit mode using Firefox,"VisualEditor (50e8693)
+Parsoid (ba0b080)
+MW: 1.22/wmf2 (814f75e)
+
+While editing a page in Firefox 20.0, the existing page content is blank in the editor.
+
+The issues seems to be an issue with Firefox only, as Chrome and Safari work as expected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**OS**: Mac OS X 10.7
+**Platform**: Macintosh",1367254380,PHID-USER-evwol34rsld7viokxokd,PHID-TASK-njwlhw4yezfqfiviad2b,task_description,resolved
+VisualEditor: Blanked page content in edit mode using Firefox,We have identified this bug and fixed it in live (for mediawiki.org - other wikis will be going out in the next few days); sorry for the difficulty.,1367288171,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-njwlhw4yezfqfiviad2b,task_subcomment,NA
+VisualEditor: Blanked page content in edit mode using Firefox,"Is this on the Wikimedia cluster or locally? If on the cluster, is it on all pages or just one or two?",1367275473,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-njwlhw4yezfqfiviad2b,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,"VE error when not completely loaded
+
+on any page editable by VE:
+
+invoke VE
+immediately click Preferences or other live link
+
+an alert appears saying ""Error loading data from server: error. Would you like to retry?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10400}",1367196780,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-s7xxo6pqgoai7qxiqran,task_description,resolved
+VisualEditor: Clicking away before VE loads completely throws JS error,Merged; will go out with wmf5.,1368885099,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,Related URL: https://gerrit.wikimedia.org/r/64333 (Gerrit Change Ide5def0e983bab49108b40008fc170957c7fc2a2),1368809323,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,"Actually, this looks like a different bug (but in the same loop).",1368655903,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,"From Ed's comment:
+
+In ve.init.mw.ViewPageTarget.prototype.tearDownToolbar, this.toolbar is
+undefined if the editor hasn't finished loading.",1368654683,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,*** Bug 48520 has been marked as a duplicate of this bug. ***,1368654670,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,"Hi,
+
+The problem is that when I have created a bullet list in Visual Editor and try to erase back the text using Backspaces, the numbers or bullet points don't delete even if I have deleted the whole text. Here is a trivial demonstration :
+
+1. Hello1
+2. Hello2
+3. Hello3
+
+Now when I try to delete it from the Hello3 using backspaces, all the text upto first bullet is deleted, but those bullet points are left as it is. 
+
+1.
+
+2.
+
+3.
+
+
+Images:
+
+https://docs.google.com/file/d/0B3eGCB261PalaDhqa1ZhcmFPUk0/edit?usp=sharing
+https://docs.google.com/file/d/0B3eGCB261PalbndsZEFSdXpEZGM/edit?usp=sharing
+
+Tested on Firefox 20.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367169780,PHID-USER-d3oiyxwdmebcjszfff7w,PHID-TASK-4rlrewbrchltpzty4e37,task_description,resolved
+VisualEditor: Backspace over lists doesn't delete the LIs,And now fixed in wmf4.,1368565464,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,This is now broken again in master. :-(,1368211380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,*** Bug 48293 has been marked as a duplicate of this bug. ***,1368129697,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,Wmf4 which will begin deployment on 13 May. :-),1367373980,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,"Fixed here: https://gerrit.wikimedia.org/r/61520
+It is not released yet, James, can you put appropriate milestone tag?",1367359540,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,Thanks for the bug report; I can confirm in Chrome and Safari as well.,1367170322,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Add button to WikiEditor and VisualEditor for switching back and forth.
+
+* Only shown if in WE you have VE enabled (otherwise don't show)
+* If no changes, switch immediately
+* If there are changes, prompt the user (with the same OOUI message dialog we use in VE) whether to switch with or without their changes",1367087280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrfiavqqnofzrlok2ea7,task_description,resolved
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 250965 merged by jenkins-bot:
+Target init: Add edit mode switch icons to VE and WE toolbars
+
+[[https://gerrit.wikimedia.org/r/250965]]",1446648058,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 250965 had a related patch set uploaded (by Jforrester):
+Target init: Add edit mode switch icons to VE and WE toolbars
+
+[[https://gerrit.wikimedia.org/r/250965]]
+",1446646795,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 250939 merged by jenkins-bot:
+Target init: Add edit mode switch icons to VE and WE toolbars
+
+[[https://gerrit.wikimedia.org/r/250939]]",1446646490,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"More prominent VE switcher:
+{F2913511}
+
+WikiEditor switcher (top right):
+{F2913515}",1446632107,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 250939 had a related patch set uploaded (by Esanders):
+Target init: Add edit mode switch icons to VE and WE toolbars
+
+[[https://gerrit.wikimedia.org/r/250939]]
+",1446631989,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 245593 merged by jenkins-bot:
+Allow switching from wikitext to VE
+
+[[https://gerrit.wikimedia.org/r/245593]]",1446506314,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 245593 had a related patch set uploaded (by Alex Monk):
+[WIP][POC][DONOTMERGE] Allow switching from wikitext to VE
+
+[[https://gerrit.wikimedia.org/r/245593]]
+",1444684486,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,">>! In T49779#1172521, @Jdforrester-WMF wrote:
+>>>! In T49779#1172511, @Krenair wrote:
+>> We should talk to #Parsoid to work out what dependencies this has from them, if any
+> 
+> It's mostly a RESTbase dependency, at this point.
+
+Perhaps we should make a separate task for the RESTbase/Parsoid dependencies here.",1435777029,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,This would be a great enhancement!,1431055639,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,">>! In T49779#1172511, @Krenair wrote:
+> We should talk to #Parsoid to work out what dependencies this has from them, if any
+
+It's mostly a RESTbase dependency, at this point.",1427931868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"We should talk to #Parsoid to work out what dependencies this has from them, if any",1427931774,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to Alex Monk from comment #17)
+> So with the resolution of bug 50687, this is effectively ""Provide a way for
+> the user to switch from the wikitext source editor to VisualEditor, keeping
+> changes but not saving"", right?
+
+Yes, as I understand it.  Adding that direction would then allow bidirectional switching.",1407181934,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"So with the resolution of bug 50687, this is effectively ""Provide a way for the user to switch from the wikitext source editor to VisualEditor, keeping changes but not saving"", right? Or have I misunderstood?",1407032261,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Sweedish Wikipedians including User:Jan Ainali and User:FrankieF are discussing/requesting an enhancement to VisualEditor here [1] and translate the thread as follows:
+
+""What we are missing is way to easily switch between wikitext and VE without saving or loosing stuff. Just like you can in Wordpress between the WYSIWYG and HTML editor."" 
+
+[1]
+https://sv.wikipedia.org/wiki/Wikipedia:VisualEditor/%C3%85terkoppling#Saknade_funktioner_i_Redig.l.C3.A4get",1381789003,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #14)
+> (In reply to comment #13)
+> > (In reply to comment #12)
+> > > This functionality was requested back in December 2011 in bug 33124.
+> > 
+> > No? The diff view of the wikitext is not even a read-only view of the entire
+> > document's wikitext, let alone an editable one? Also, quickly editing the
+> > diff
+> > in a pop-over window is fundamentally different paradigm from having a proper
+> > wikitext editor available to all users at all times, and being able to switch
+> > back and forth, which is what this bug requests.
+> 
+> From what I remember about the feature which existed in the prototype which
+> motivated the request made on bug 33124, it actually displayed the entire
+> document's wikitext (not just the diff).
+
+Oh, yes, you are right. My apologies.
+
+This means that that bug is even further from ""this functionality"", however.",1381334205,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #13)
+> (In reply to comment #12)
+> > This functionality was requested back in December 2011 in bug 33124.
+> 
+> No? The diff view of the wikitext is not even a read-only view of the entire
+> document's wikitext, let alone an editable one? Also, quickly editing the
+> diff
+> in a pop-over window is fundamentally different paradigm from having a proper
+> wikitext editor available to all users at all times, and being able to switch
+> back and forth, which is what this bug requests.
+
+From what I remember about the feature which existed in the prototype which motivated the request made on bug 33124, it actually displayed the entire document's wikitext (not just the diff).",1381333880,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #12)
+> This functionality was requested back in December 2011 in bug 33124.
+
+No? The diff view of the wikitext is not even a read-only view of the entire document's wikitext, let alone an editable one? Also, quickly editing the diff in a pop-over window is fundamentally different paradigm from having a proper wikitext editor available to all users at all times, and being able to switch back and forth, which is what this bug requests.",1381329923,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,This functionality was requested back in December 2011 in bug T35124.,1434266616,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,This functionality was requested back in December 2011 in bug 33124.,1381301841,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #10)
+> Im not immediately inclined to work on SE->VE, as that could facilitate
+> people
+> playing games with the wikitext in order to put dodgy entries into the
+> 'VisualEditor' tagged edit list, which would be impossible to debug.
+
+That could be mitigated with an editfilter or some other indication that an editor had used both modes. Whether such would be possible or desirable is another matter",1375211326,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"I have built a script which switches from VE to SE.
+https://en.wikipedia.org/wiki/User:John_Vandenberg/switch_editor
+
+I havent looked at whether the API and VE codebase can support switching from SE back to VE, but it seems like JS could obtain rendered HTML (action=parse?) and load it into VE.
+
+Im not immediately inclined to work on SE->VE, as that could facilitate people playing games with the wikitext in order to put dodgy entries into the 'VisualEditor' tagged edit list, which would be impossible to debug.",1374296995,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,*** Bug 50698 has been marked as a duplicate of this bug. ***,1373855340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #7)
+> See also:
+> * [[Thread:VisualEditor/Feedback/ Side-by-side view (no more?)]]
+
+Helder. I corrected the link (I hope):
+* [[mw:Thread:VisualEditor/Feedback/ Side-by-side view (no more?)]]
+
+See: [[WP:Bugzilla]] and the section currently titled ""Links from within Bugzilla"".
+
+Hey Helder. Maybe you can develop a preview mode for Bugzilla? :) Bugzilla needs a ""preview"" mode:
+*https://bugzilla.mozilla.org/show_bug.cgi?id=40896",1372983348,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"See also:
+* [[Thread:VisualEditor/Feedback/ Side-by-side view (no more?)]]
+* Old demo with side-by-side view:
+http://blog.wikimedia.org/2011/12/13/help-test-the-first-visual-editor-developer-prototype/visual-editor-demo-2/",1372878442,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,Adding 'source' to subject line to make this easier to search.,1372787226,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,*** Bug 49986 has been marked as a duplicate of this bug. ***,1371855868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"**winne2i** wrote:
+
+I'm asking again if this is very difficult to achieve this by adding (even temporarily!) a regular Preview button, which will allow us to see the source code of already changed content? As I said before we can already see diffs so seeing a preview should be quite easy IMO.
+
+As far as refs are concerned – I agree that's very important. But let me notice that introducing such Preview button would allow to add references in that later step (editing the source code). That would be a great instant (but somewhat temporary) solution for both problems. Then one may work on pretty way of adding refs.
+
+Doesn't it sound good? :)",1371556666,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #2)
+> Just pointing out that this is very frequently requested by enwiki users at
+> [[Wikipedia:VisualEditor/Feedback]]. 
+> 
+> I know bug priority is technically up to the developers, but just letting you
+> know that a lot of people want this.
+
+We understand, and I really want to be able to provide this, but in the choice between this and being able to add references (say) we have to prioritise. However, I'm going to see if we can try to get it done in the next few weeks. Sorry for not being able to make a firm commitment.",1371521807,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Just pointing out that this is very frequently requested by enwiki users at [[Wikipedia:VisualEditor/Feedback]]. 
+
+I know bug priority is technically up to the developers, but just letting you know that a lot of people want this.",1371521045,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"**winne2i** wrote:
+
+To me that doesn't seem to be compliacted to acheive. The way could be to add a button which opens regular Preview (with wikitext editing).
+We already can see the diff, so adding regular preview should not be difficult.
+
+And this can be a big convenience because it's easier to edit in VE but we still can't edit/insert some elements like templates.",1369048522,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+"VisualEditor: Edit vs. edit source tab split not preserved across action=history, action=edit, Special:Undelete, …","Right now you get | Edit | Edit source | on read and on VE edit (which are the same thing) but nowhere else, which is confusing.
+
+(Whilst we're at it, logs, diff view pages, and probably a few dozen others have edit links which will need to be replaced or augmented.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367086560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zcmfiyirjhsjlqbiehnf,task_description,resolved
+"VisualEditor: Edit vs. edit source tab split not preserved across action=history, action=edit, Special:Undelete, …",This was fixed by Ed in his commit last week.,1367860149,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zcmfiyirjhsjlqbiehnf,task_subcomment,NA
+"VisualEditor: Edit vs. edit source tab split not preserved across action=history, action=edit, Special:Undelete, …","Once we're deployed for all users, we could simply replace the ""Edit"" message with ""Edit source"" in core which would manage the first half; we'd still need to add the (VE) ""Edit"" tab to these extra places (and the other stuff like ""(edit)"" links in diff views).",1367097655,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zcmfiyirjhsjlqbiehnf,task_subcomment,NA
+"VisualEditor: Edit vs. edit source tab split not preserved across action=history, action=edit, Special:Undelete, …","Setting ""High"" for action=edit; the others can be fixed, I guess.",1367086643,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zcmfiyirjhsjlqbiehnf,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"In [[en:User:Yamaha5/sandbox]] I tested it for Farsi every thing was OK except <div dir=""rtl""><div> which cause the test disable. in fa.wiki because of mixture of farsi and english or LTR Math formulas we use direction inside the text so it will cause problem for RTL languages
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367020500,PHID-USER-dswbdv7ibhsefllcqarz,PHID-TASK-yygcicr6m5mpgdgpjccs,task_description,resolved
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 95051 merged by jenkins-bot:
+MediaWiki language inspector updates
+
+https://gerrit.wikimedia.org/r/95051",1390007205,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 95051 had a related patch set uploaded by Jforrester:
+MediaWiki language inspector updates
+
+https://gerrit.wikimedia.org/r/95051",1390006945,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,Splitting the block level items into bug 60187.,1390006865,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"The main work is merged. Some designs tweaks are still needed, but now language for <span>s can be set.",1375256723,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 72634 merged by jenkins-bot:
+Language Inspector UI
+
+https://gerrit.wikimedia.org/r/72634",1375254898,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 72634 had a related patch set uploaded by Mooeypoo:
+Language Inspector UI
+
+https://gerrit.wikimedia.org/r/72634",1374630395,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 70560 merged by jenkins-bot:
+Language Inspector: CE / DM
+
+https://gerrit.wikimedia.org/r/70560",1373483622,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 70560 had a related patch set uploaded by Mooeypoo:
+Language Inspector: CE / DM
+
+https://gerrit.wikimedia.org/r/70560",1373482614,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,*** Bug 41009 has been marked as a duplicate of this bug. ***,1373002468,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"(In reply to comment #5)
+> Oy, I mean Bug 41009. Both speak of the same features that the Language
+> Inspector will attempt to solve.
+
+Given that this is more advanced in discussion, I'll up-merge that into this.",1373002441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Oy, I mean Bug 41009. Both speak of the same features that the Language Inspector will attempt to solve.",1372987705,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,I think this is a dupe of Bug 47759,1372987615,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Work on this has began, we will be using <span lang='xx' dir='yyy'> tags to start with and add functionality for broader usages in the future.",1372962330,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"This would be a task for a language inspector, presumably? Marking as an enhancement - this might be something for Moriel if she is going to be working with us on language support.",1367293379,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Clarification: the bug report is about text within <div dir=""rtl""></div> being alienated. I'm not sure how we can intelligently not alienate text with such a direction override.",1367275242,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"Ubuntu/Firefox
+Go to http://en.wikipedia.org/wiki/Alfresco_%28software%29
+At the end of a line, add a space and remove it
+Click ""Save""
+No changes should have happen, but there actually are changes, in the infobox:
+
+| caption = Alfresco Share / Repository Browser <br/> (Community Edition)
+became
+| caption =Alfresco Share / Repository Browser <br></table> (Community Edition)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366964340,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-hk3rab5lb2jvryjrgppj,task_description,resolved
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"(In reply to comment #10)
+> http://en.wikipedia.org/wiki/Anne_Hendershott still shows the same symptoms.
+> Is
+> this fix not yet deployed?
+
+Sorry, the meaning of ""VE-deploy-2013-05-13"" is meant to be pretty clear, but evidently isn't! It'll go out with 1.22wmf4, so on the English Wikipedia on 20 May.",1367901947,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,http://en.wikipedia.org/wiki/Anne_Hendershott still shows the same symptoms. Is this fix not yet deployed?,1367897162,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,We're now three bugs fixed into this stack. Closing. Others should be opened as other bugs.,1367871544,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,Related URL: https://gerrit.wikimedia.org/r/61919 (Gerrit Change I42daaf142e548e5b221ff0a52df0ad24ec6a4fd0),1367449312,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"I tested the following 4 pages and am recording my findings here.  Once we go through the other pages, we should close this bug and create new bugs where necessary.
+
+On the following two pages, I can reproduce in Firefox, but the edit is clean in Chrome.  So, this is definitely Firefox specific, not sure if it is JQuery-related or something else.
+
+* http://en.wikipedia.org/wiki/Timeline_of_portable_computers
+* http://en.wikipedia.org/wiki/Neritina_rubricata
+
+On the following two pages, I can reproduce the spurious diffs in both Firefox and Chrome even though I didn't edit the relevant areas. I haven't looked at the diffs yet.  So, this is quite likely some kind of whitespace change in the DOM that VE sends Parsoid.
+
+* http://en.wikipedia.org/wiki/Timeline_of_portable_computers -- It appears that the table is being marked as edited even though I didn't edit the table.
+
+* http://en.wikipedia.org/wiki/Anne_Hendershott -- the list is being marked as edited because of some whitespace normalization when VE loads/saves the DOM.",1367075006,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"(In reply to comment #4)
+> Do you mean all of the problem mentioned on this page are due to this bug?
+
+Please open separate bug tickets for each bug in future. :-)",1366994200,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,I believe the whitespace changes are a separate issue. Reopening so that those don't get lost.,1366992962,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"Do you mean all of the problem mentioned on this page are due to this bug?
+Cheers!
+Nicolas",1366992621,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"This is an instance of the jQuery bug 47737 - marking as a duplicate.
+
+*** This bug has been marked as a duplicate of bug 47737 ***",1366992520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"http://en.wikipedia.org/wiki/Anne_Hendershott
+http://ja.wikipedia.org/wiki/BMW_801
+On the contrary, here spaces got inserted.
+
+http://en.wikipedia.org/wiki/List_of_Mexican_telenovelas
+* ''[[Mañana Es Para Siempre]]-''Tomorrow Is Forever''
+becomes
+* ''[[Mañana Es Para Siempre]]-''Tomorrow Is Forever
+
+http://en.wikipedia.org/wiki/Sonic_the_Hedgehog_Vocal_Traxx:_Several_Wills
+http://ja.wikipedia.org/wiki/%E6%9C%A8%E6%A2%A8%E3%82%AC%E3%82%A4%E3%83%89%E3%83%BB%E9%80%B1%E6%9C%AB%E3%81%AE%E9%81%94%E4%BA%BA
+http://ja.wikipedia.org/wiki/%E3%82%A4%E3%83%B3%E3%83%89%E3%82%B7%E3%83%A5%E3%83%A2%E3%82%AF%E3%82%B6%E3%83%A1
+<br/> becomes <br></table>
+
+http://en.wikipedia.org/wiki/Barunga,_Northern_Territory
+| pop = 282 (2006 Census)<ref name=Census2006Y />
+becomes
+| pop =282 (2006 Census)<ref name=Census2006Y ></span>
+
+http://en.wikipedia.org/wiki/Aerial_toll_house
+whole references are duplicated
+
+etc... using http://en.wikipedia.org/wiki/Special:Random and http://ja.wikipedia.org/wiki/%E7%89%B9%E5%88%A5:%E3%81%8A%E3%81%BE%E3%81%8B%E3%81%9B%E8%A1%A8%E7%A4%BA about half of the articles don't roundtrip.",1366966146,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"Other faulty roundtrips:
+
+http://en.wikipedia.org/wiki/Neritina_rubricata
+Removes space at end of line
+
+http://en.wikipedia.org/wiki/Timeline_of_portable_computers
+--> || becomes -->||
+
+Should I continue reporting space removals like these 2 ones?
+Or are these spaces removed on purpose?",1366964740,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Edit an article
+Press down your keyboard's SHIFT key
+While maintaining SHIFT pressed, press the RIGHT key a few times
+
+EXPECTED: Characters are selected
+ACTUALLY: Characters are deleted
+
+Ubuntu/Firefox
+
+Looks like https://bugzilla.wikimedia.org/show_bug.cgi?id=41062 which had been fixed in October.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366963620,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-czooq62xjeisscbrllhg,task_description,resolved
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"(In reply to comment #8)
+> Still actin' crazy: firefox 20.0, linux.  I hard-refreshed just in case.
+
+You may have hard-refreshed, but you didn't wait for the deployment train which was only three hours ago. :-) Sorry for not mentioning that it's ""fixed pending deploy"" (it'd be great if Bugzilla had that as a status).
+
+Can confirm that it's now fixed in live in Firefox 20.0/Mac.",1367286853,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,This bug is currently fixed in master. It is going to be live on Wikipedia by Wednesday next week. In the meantime it is possible to test on mediawiki.org. However currently (for another 2-3 hours) VE on mediawiki.org is completly broken for FF.,1367281288,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"It would be worthwhile to mention the bug 47795 here, with similar nature of problem.",1367223121,PHID-USER-d3oiyxwdmebcjszfff7w,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Sorry, comment #10 has been split off into bug 47817.",1367217111,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Okay, the turd was a separate bug:
+
+1. Edit a page with an unordered list.
+
+2. Delete all the text on the last line.
+
+3. Press the <delete key>. The bullet should be erased.  Instead, it will remain and the cursor will move to the end of the previous line.
+
+4. down-arrow
+
+5. down-arrow off of the empty line.
+
+Turd appears in the empty line.
+
+6. I did something else with the arrow keys, all of the document's lines were erased (not all part of the <ul>), and the undo buffer could not step backwards.  Aaaa, will reproduce later.",1367216836,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Confirmed. It still doesn't work in Firefox 20.0. Shift+Selection Keys isn't working in normal way. When up or down keys are pressed, the text is selected for the first time, but pressing them for second time gets the selected text deleted.",1367216493,PHID-USER-d3oiyxwdmebcjszfff7w,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Still actin' crazy: firefox 20.0, linux.  I hard-refreshed just in case.
+
+In fact, I had some text highlighted and tried to use <ctrl>-<shift>-left to extend the selection.  My text was deleted, plus a character or two, and then a freakin snail character appeared.  I have yet to find the unicode for that.  It wasn't 1F40C, OMG it was 1f4a9 I was just about to say it looked more like a turd than snail.",1367215830,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,And /now/ it's fixed. :-),1367010986,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,https://gerrit.wikimedia.org/r/61055 (Gerrit Change I1aff295a0958b75697c4d362e0d6095283f37fe8) | change APPROVED and MERGED [by jenkins-bot],1367010696,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Just for my sanity, marking as unfixed until it's merged.",1367010554,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,Fixed in here: https://gerrit.wikimedia.org/r/#/c/61055/,1367004734,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,Related URL: https://gerrit.wikimedia.org/r/61055 (Gerrit Change I1aff295a0958b75697c4d362e0d6095283f37fe8),1367004696,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Confirmed, will work on it.",1366997433,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,Confirm that this occurs in Firefox but not in Chrome.,1366996702,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,"Steps to reproduce:
+
+1. Open http://en.wikipedia.org/wiki/CMIS
+2. Press Edit
+3. Press your keyboard's Down key
+4. Wild pawn ♙ appears
+
+Also reproduced on http://ja.wikipedia.org/wiki/%E3%83%95%E3%83%AB%E3%83%BC%E3%83%AB%E3%83%BB%E3%83%89%E3%83%BB%E3%82%BB%E3%83%AB
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366963320,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-3whynfwz7dddsiybr7nr,task_description,resolved
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,Fixed in here: https://gerrit.wikimedia.org/r/#/c/61055/,1367004998,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-3whynfwz7dddsiybr7nr,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,"Confirmed, will work on it.",1366997922,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-3whynfwz7dddsiybr7nr,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,"Reproduced on Firefox 20 on OS X 10.8. 
+
+
+Following error reported in console when pressing down key.
+
+[19:49:36.737] TypeError: this.storeIndexes.slice is not a function @ http://bits.wikimedia.org/ja.wikipedia.org/load.php?debug=false&lang=zh-hans&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Crangy%7Cunicodejs.wordbreak&skin=vector&version=20130426T114825Z&*:48
+
+
+
+Reproduced even when everything is in English:
+
+https://zh.wikipedia.org/w/index.php?title=User:Bencmq-test/2&diff=26351189&oldid=26351184
+
+
+No issue on Chrome or Safari. I took the liberty of marking it as FireFox only.",1366978000,PHID-USER-hoj4lurwi6bejyjy5qlp,PHID-TASK-3whynfwz7dddsiybr7nr,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,"If you keep the Down key pressed, the caret will travel down, dumping a pawn at the end of some paragraphs.
+I am not sure how pawn leaving is decided: For the same paragraph of the same article, sometimes a pawn is dumped and sometimes not.",1366967706,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-3whynfwz7dddsiybr7nr,task_subcomment,NA
+VisualEditor: Hard-coded strings in ve.ui.MWLinkTargetInputWidget.prototype.populateMenu,"From user report:
+
+'externalLink', { '$$': menu$$, 'label': 'External link' }
+'newPage', { '$$': menu$$, 'label': 'New page' }
+'matchingPages', { '$$': menu$$, 'label': 'Matching page' }
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366955760,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-fa5biiyjbod7exipkpqs,task_description,resolved
+VisualEditor: Hard-coded strings in ve.ui.MWLinkTargetInputWidget.prototype.populateMenu,In the end fixed by gerrit 60700 just to be confusing; now merged and will be deployed in the Monday deploy train.,1367019435,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fa5biiyjbod7exipkpqs,task_subcomment,NA
+VisualEditor: Hard-coded strings in ve.ui.MWLinkTargetInputWidget.prototype.populateMenu,Fixed by gerrit 61035. Thanks for the catch!,1366996007,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fa5biiyjbod7exipkpqs,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Matanya/%D7%90%D7%A8%D7%92%D7%96_%D7%97%D7%95%D7%9C_2&diff=14076208&oldid=14076205
+
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Matanya/%D7%90%D7%A8%D7%92%D7%96_%D7%97%D7%95%D7%9C_2&diff=14076218&oldid=14076208
+
+(Others.)
+
+User says they get this when switching he/en and back again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366933140,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p24deoao7z7cqo3jfmi7,task_description,declined
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"I cannot reproduce it any more (Firefox 22, Fedora 18). Marking WORKSFORME, but reopen if it still happens.",1373221327,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"Steps to reproduce:
+
+1) open https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Matanya/%D7%90%D7%A8%D7%92%D7%96_%D7%97%D7%95%D7%9C_2&diff=14076208&oldid=14076205
+
+in VE mode.
+
+2) open a new line and go to the beginning of the line. switch for he to en or vice versa on your keyboard.
+
+3) you have a pawn. 
+
+tested on firefox 21 on ubuntu 13.04",1369123443,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),Ping to Amir / matanya for steps to reproduce.,1369093796,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),I still can't reproduce this one. Can I get step-by-step instruction please?,1368216144,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"I don't think this is a dupe of bug 41067 - pawns appearing can have lots of causes (all bugs, but not necessarily the same bug).",1367274946,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"
+
+*** This bug has been marked as a duplicate of bug 41067 ***",1367254472,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"Firefox 20 on ubuntu 13.04 too. 
+
+Didn't see any error in the JS console.",1367254368,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),I saw it in Firefox 20 on Fedora 18.,1366969520,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),Also - it would be very valuable to know if there are any errors in JS console.,1366934353,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),Any information about web browser and OS?,1366934083,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,"EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366932300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_description,resolved
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,Merged and will go out with wmf5 on 27 May.,1369409008,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,Related URL: https://gerrit.wikimedia.org/r/65291 (Gerrit Change I216cdd68014173aa65cad42ddd3d870334be9ead),1369406998,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,"(In reply to comment #2)
+> EditPage uses msg: editingold[1].
+> 
+> [1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en
+
+Ah, yes, whoops. Good catch.",1369256829,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,"EditPage uses msg: editingold[1].
+
+[1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en",1369244923,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,This looks to be <Revision-info>. :-),1367275878,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+"VisualEditor: After saving a page, the VisualEditor tab points at the oldid content not the new one","Edit a page in VE, press save; enter VE again.
+
+What should happen: You edit the newly-updated page.
+
+What does happen: You edit the content of the page before you updated it (and VE doesn't know it's doing this).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1366932180,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-25426wyep677h7baqpvx,task_description,resolved
+"VisualEditor: After saving a page, the VisualEditor tab points at the oldid content not the new one",*** Bug 48395 has been marked as a duplicate of this bug. ***,1368643696,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-25426wyep677h7baqpvx,task_subcomment,NA
+"VisualEditor: After saving a page, the VisualEditor tab points at the oldid content not the new one","
+
+*** This bug has been marked as a duplicate of bug 47420 ***",1367614840,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-25426wyep677h7baqpvx,task_subcomment,NA
+"VisualEditor: After saving a page, the VisualEditor tab points at the oldid content not the new one",*** Bug 48021 has been marked as a duplicate of this bug. ***,1367530293,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-25426wyep677h7baqpvx,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,"The VE becomes active on .js and .css pages in the user namespace, even though it is not capable of handling this content type.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/wiki/User:TheDJ/common.js",1366469700,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-mw76lciqtgo7k33dnexw,task_description,resolved
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,*** Bug 48471 has been marked as a duplicate of this bug. ***,1368569378,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,Merged by Catrope.,1368463148,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,Gerrit change 63341,1368307015,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,*** Bug 47768 has been marked as a duplicate of this bug. ***,1367097296,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,"Yup, we should expand this more generally to all things that have a different ContentHandler type. We already depend on MW 1.21 in general, so I guess(?) this shouldn't be too much of a problem.",1366470309,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab doesn't become 'active'","If in a page you click 'Edit source', the tab does not receive the 'selected' styling/class as it is supposed to.
+
+This was confirmed with Safari 6 mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1366463880,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_description,resolved
+"VisualEditor: ""Edit source"" tab doesn't become 'active'",*** Bug 48316 has been marked as a duplicate of this bug. ***,1368150918,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab doesn't become 'active'",Now merged and will go live with wmf4.,1367602843,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab doesn't become 'active'",Related URL: https://gerrit.wikimedia.org/r/62145 (Gerrit Change Ic2d42bb3034be25f388b587a00c3f523cfcc163c),1367583532,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab doesn't become 'active'","Pretty sure I made this work a couple of weeks ago, but it might have been broken by the more recent changes to this code.",1366998791,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_subcomment,NA
+VisualEditor: data-parsoid attribute sometimes not preserved properly,"a </table> tag is sometimes inserted into data-parsoid when set on a table element, for example in the 'Infobox settlement' at http://en.wikipedia.org/wiki/Beale_Township,_Juniata_County,_Pennsylvania.
+
+Original data-parsoid (part of):
+Beale Township,<br/>Pennsylvania\n
+
+VE output (editedHtml):
+Beale Township,<br></table>Pennsylvania\n
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366407120,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-coiafysv5fwnb2coli72,task_description,resolved
+VisualEditor: data-parsoid attribute sometimes not preserved properly,"
+
+*** This bug has been marked as a duplicate of bug 47417 ***",1366992022,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-coiafysv5fwnb2coli72,task_subcomment,NA
+VisualEditor: Deleting to/from a blank lines fails,"If you have lines like so:
+
+| A
+| B
+| 
+| C
+
+Deleting backwards from up-page of C, or from within the blank line above C, causes the cursor to move (as expected) but no deletion.
+
+Deleting forwards from down-page of B, of from within the blank line below B, causes the cursor to stay (as expected) but no deletion.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366397400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-na7hdsgn5rcikyp6dgpv,task_description,resolved
+VisualEditor: Deleting to/from a blank lines fails,This is now fixed with the deletion re-write.,1371781860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-na7hdsgn5rcikyp6dgpv,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"(a) open a page in VE and edit it
+(b) save in VE 
+(c) reopen the same page right away in VE
+
+The previous version (rather than saved version) is fetched.  I looked at POST params in chrome and looks like revision id (oldid) being sent is of the older version rather than the saved version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366393860,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-l3samzhuiftku6aijqqt,task_description,resolved
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"(In reply to comment #11)
+> That is bug 50441.
+
+Yes; sorry! :-)",1373061922,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,That is bug 50441.,1373061758,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,Re-closing; new breakage is being tracked as bug 47420.,1373061639,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"This bug was closed as fixed on May 3 but I am still seeing this behavior on mediawiki.org. The second edit after saving loads the previous version of the page, not the current version. A warning ""You are editing an out-of-date revision of this page"" appears, but that doesn't help.",1373015887,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,*** Bug 48021 has been marked as a duplicate of this bug. ***,1367614853,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,*** Bug 47682 has been marked as a duplicate of this bug. ***,1367614840,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,Now merged and will go into wmf4.,1367602814,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,Related URL: https://gerrit.wikimedia.org/r/62168 (Gerrit Change I12ce27c8dc57f7aa753bcf5840635d5fea6b4e80),1367601065,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"(In reply to comment #3)
+> The JSON we get back after a save only contains the plain html and some
+> timestamps. In order for us to update this.oldid we'll need Parsoid to tell
+> us what it is, I think.
+
+Parsoid doesn't know; it's VisualEditor.php which does the actual saving to the DB.",1367595038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"The JSON we get back after a save only contains the plain html and some timestamps. In order for us to update this.oldid we'll need Parsoid to tell us what it is, I think.",1367578702,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,This is because we don't update this.oldid after saving.,1366998865,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"Feels like we need to properly review how the integration around oldids works, given the number of issues. :-(",1366395770,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","See https://en.wikipedia.org/w/index.php?title=User:Fluffernutter/Kinne&diff=551148728&oldid=551148307
+
+To investigate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366387680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_description,resolved
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>",This is an instance of the jQuery bug 47737 - marking as FIXED (in the specific instance) but we need a wider fix.,1366992579,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>",*** Bug 47430 has been marked as a duplicate of this bug. ***,1366992022,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","(In reply to comment #7)
+> (In reply to comment #6)
+> > This is a bug in jQuery. To reproduce:
+> 
+> That confirms my suspicion. The bug appeared first after you started using it
+> to avoid dropping figure elements.
+Yup, which is why we can't just go back, because that would break <caption> elements again.
+
+Filed upstream as http://bugs.jquery.com/ticket/13821",1366906990,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","The reason this doesn't happen in Chrome is because Chrome normalizes < to &lt; in attribute values in .innerHTML. Firefox doesn't do this and gives us the original < as originally provided by Parsoid.
+
+The presence of these <> then triggers a jQuery regex looking for self-closing tags:
+
+/<(?!area|br|col|embed|hr|img|input|link|meta|param)(([\w:]+)[^>]*)\/>/gi
+
+...which believes our span (!) is self-closing because it starts with <span and contains /> later, so it helpfully ""fixes"" our HTML and replaces the /> with </span>",1366906954,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","Ed's quick hack is now merged, but we still need to fix this - upstream bug in jQuery or just a work around?",1366906093,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","(In reply to comment #6)
+> This is a bug in jQuery. To reproduce:
+
+That confirms my suspicion. The bug appeared first after you started using it to avoid dropping figure elements.",1366904572,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","This is a bug in jQuery. To reproduce:
+
+>>> $( '<div>' ).html( '<span data-parsoid=""{&quot;src&quot;:&quot;<ref name=\&quot;Foo\&quot; />&quot;,&quot;tsr&quot;:[32,50],&quot;dsr&quot;:[32,50,null,null]}"">' ).html();
+
+""<span data-parsoid=""{&quot;src&quot;:&quot;<ref name=&quot;Foo&quot; ></span>&quot;,&quot;tsr&quot;:[32,50],&quot;dsr&quot;:[32,50,null,null]}""></span>""",1366904257,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","This is what I see using wget, FF, and the parse.js in the shell:
+
+<span id=""cite_ref-rfc3092-1-0"" class=""reference"" about=""#mwt5"" typeof=""mw:Object/Ext/Ref"" data-parsoid='{""src"":""<ref name=\""rfc3092\"" />"",""tsr"":[416,438],""dsr"":[416,438,null,null]}'><a href=""#cite_note-rfc3092-1"" data-parsoid=""{}"">[1]</a></span><meta typeof=""mw:Ext/Ref/Marker"" about=""#mwt5"" group="""" name=""rfc3092"" content="""" skiplinkback=""0"" data-parsoid='{""tsr"":[416,438],""selfClose"":true,""src"":""<ref name=\""rfc3092\"" />"",""dsr"":[416,438,22,0]}'>
+
+Make sure you are not looking at a pretty-printed inspect tool. Either use innerHTML (which will use non-smart quoting) or the actual page source (ctrl-u in Firefox).
+
+From what I see Firefox parses our HTML just fine on the way in, with the entire JSON string being parsed as the attribute value. Do you actually see a parsing difference on the way in resulting in a different DOM?
+
+Changing the title back, as I am pretty sure this is not a bug on our end.",1366902121,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","The problem appears to be with the output from Parsoid with regard to <ref> tags not being escaped.
+
+To give http://parsoid.wmflabs.org/en/Foobar as an example, in Chrome this looks fine:
+
+<span id=""cite_ref-rfc3092-1-0"" class=""reference"" about=""#mwt5"" typeof=""mw:Object/Ext/Ref"" data-parsoid=""{&quot;src&quot;:&quot;<ref name=\&quot;rfc3092\&quot; />;&quot;,&quot;tsr&quot;:[416,438],&quot;dsr&quot;:[416,438,null,null]}""><a href=""#cite_note-rfc3092-1"" data-parsoid=""{}"">[1]</a></span>
+<meta typeof=""mw:Ext/Ref/Marker"" about=""#mwt5"" group="""" name=""rfc3092"" content="""" skiplinkback=""0"" data-parsoid=""{&quot;tsr&quot;:[416,438],&quot;selfClose&quot;:true,&quot;src&quot;:&quot;&lt;ref name=\&quot;rfc3092\&quot; /&gt;&quot;,&quot;dsr&quot;:[416,438,22,0]}"">
+
+
+... but in Firefox the browser presumably doesn't like the un-escaped ""<ref name=... />"" in the attribute of the <span> and so it does this:
+
+<span id=""cite_ref-rfc3092-1-0"" class=""reference"" about=""#mwt5"" data-parsoid=""{""src"":""<ref name=\""rfc3092\"" />"",""tsr"":[416,438],""dsr"":[416,438,null,null]}"" typeof=""mw:Object/Ext/Ref""></span>
+<meta typeof=""mw:Ext/Ref/Marker"" about=""#mwt5"" group="""" name=""rfc3092"" content="""" skiplinkback=""0"" data-parsoid=""{""tsr"":[416,438],""selfClose"":true,""src"":""<ref name=\""rfc3092\"" />"",""dsr"":[416,438,22,0]}""></meta>
+
+I.e., closing the <span> early and throwing away the contents. Note that the following meta is also fragile as it contains unescaped JSON as well.
+
+The result of this is that <ref name=""…"" /> is wrongly expanded to <ref name=""…"" ></span> and so corrupted on save by Firefox users.",1366898909,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>",Related URL: https://gerrit.wikimedia.org/r/60840 (Gerrit Change Ib6a0cfb880e769f28b42c9fa63ddc1abc75c399d),1366898453,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>",*** Bug 47419 has been marked as a duplicate of this bug. ***,1366391720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","This seems to be Firefox specific.  I am seeing this on a lot of pages in Firefox, but not in Chrome.  Gabriel can reproduce as well.",1366388687,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"[TUX] Cannot confirm outdated translation on ""page"" view","Screenshot of the problem
+
+On the ""page"" view, when an outdated translation is opened, the editor shows a disabled ""save translation"" as the main action.
+
+It should show an enabled ""Confirm translation"" button instead (as it is the case for the ""list"" view).
+
+I found the bug on outdated translations at https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-visualeditor&language=ca&filter=&action=page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10395}",1366356360,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-4ifg7mkk6tb64fjj6xsp,task_description,resolved
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,"Ordinarily there's an accesskey (e.g. alt+shift+E in Firefox) on the ""Edit"" tab in Vector. The accesskey is made known to the user through a tooltip. VisualEditor eliminates this accesskey and tooltip, and adds a new ""Edit source"" tab without an accesskey or tooltip. 
+
+Ideally both the ""Edit"" and ""Edit source"" tab should have accesskeys and tooltips to allow quick switching between the modes for power users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366355400,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-app5etuemqiwaqysxa3i,task_description,resolved
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,Code is now merged and will go out on Thursday.,1366745664,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-app5etuemqiwaqysxa3i,task_subcomment,NA
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,"Change-Id: If598552fac639da645a8b1273c5fc6028695fcc1
+
+> @@ -777,10 +778,10 @@ ve.init.mw.ViewPageTarget.prototype.setupSkinTabs
+>  			this.veEditUri,
+> -			$caEdit.text(),
+> +			$caEditA.text(),
+>  			$caEdit.attr( 'id' ),
+> -			$caEdit.attr( 'title' ),
+> -			$caEdit.attr( 'accesskey' ),
+> +			$caEditA.attr( 'title' ),
+> +			$caEditA.attr( 'accesskey' ),
+>  			caVeEditSource
+>  		);
+>  	}",1366618061,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-app5etuemqiwaqysxa3i,task_subcomment,NA
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,Related URL: https://gerrit.wikimedia.org/r/60241 (Gerrit Change If598552fac639da645a8b1273c5fc6028695fcc1),1366617728,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-app5etuemqiwaqysxa3i,task_subcomment,NA
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,"When mw.ViewPageTarget has its tabLayout in ""replace"" mode (where it replaces the regular Edit tab with a VE-version and adds an Edit source tab) the code explicitly copies over the label, tooltip and accesskey.
+
+It appears this isn't working anymore. I worked a week ago. The code hasn't changed so it looks like something else has broken it.
+
+Moving bug to Integration (perhaps the component should be renamed to ""MediaWiki integration"")",1366362135,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-app5etuemqiwaqysxa3i,task_subcomment,NA
+VisualEditor: Double-click to overwrrite is broken,"1. Open http://ve-change-marking.instance-proxy.wmflabs.org/wiki/Test
+2. Double-click a word and type a single-char
+   (you see that the selected word continues to show in the interface after the char you typed)
+3. Look at review-and-save.
+4. The word has actually been deleted => the interface is not updated as it should
+
+(4) causes the user (=me in this case) to repeatedly try and delete that word and is instead deleting newer words which will all show up in the diff without realizing that they are being deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366326300,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-qwln7sdc2jjjjhdroshx,task_description,resolved
+VisualEditor: Double-click to overwrrite is broken,Inez fixed this.  Possibly https://gerrit.wikimedia.org/r/#/c/59965/,1366340774,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-qwln7sdc2jjjjhdroshx,task_subcomment,NA
+VisualEditor: Double-click to overwrrite is broken,What browser/version are you using? I cannot reproduce in Chrome/Mac or Firefox/Mac - see http://ve-change-marking.instance-proxy.wmflabs.org/srv/mediawiki/index.php?title=Test&diff=45&oldid=44 for a successful run. (Or maybe the code got fixed between the report and my looking at it?),1366331132,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qwln7sdc2jjjjhdroshx,task_subcomment,NA
+VisualEditor: Round-tripping failure - Extra newline added at end of body,"When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366312920,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-akpipntp36njlfgkew56,task_description,resolved
+VisualEditor: Round-tripping failure - Extra newline added at end of body,"(In reply to comment #3)
+> This might be fixed by bug 48344.
+It most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine). Closing this bug unless and until someone can get a newline to show up again.",1368557767,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-akpipntp36njlfgkew56,task_subcomment,NA
+VisualEditor: Round-tripping failure - Extra newline added at end of body,This might be fixed by bug 48344.,1368552325,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-akpipntp36njlfgkew56,task_subcomment,NA
+VisualEditor: Round-tripping failure - Extra newline added at end of body,"Eh, disregard that link- belongs to bug 47419.",1366388820,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-akpipntp36njlfgkew56,task_subcomment,NA
+VisualEditor: Round-tripping failure - Extra newline added at end of body,Example edit: https://en.wikipedia.org/w/index.php?title=User:Fluffernutter/Kinne&curid=37842561&diff=551148728&oldid=551148307,1366388778,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-akpipntp36njlfgkew56,task_subcomment,NA
+VisualEditor: Lazy-update SurfaceFragment,"For performance reasons, we should lazy-update SurfaceFragments rather than updating them through a transact event handler.
+
+The performance problem occurs when you create a bunch of fragments, then throw them away. The fragments are never actually destroyed, if only because the surface still has references to them because of the event binding. The discarded fragments continue to receive events about transactions and update themselves in response, but no one is using them any more.
+
+Instead, I propose the following:
+
+* The surface should have an ordered array of [transaction, direction] pairs that tracks everything that has ever been applied. This is not the same as the undo/redo stacks: this particular array is append-only
+* Every SurfaceFragment has a property indicating which transaction (by index in the big array) is the last one that it knows about
+* SurfaceFragments do not listen for transact events
+* Instead, every time getRange() is called, the fragment asks the surface whether there are new transactions (with indices greater than the stored index), and if so it translates its range for them
+** For this to work, all internal uses of this.range need to be changed to this.getRange()
+
+This'll make the fragment lazy-update its range, and we won't spend any time updating fragments that aren't being used.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366245060,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-g5zcpdywgfveewvgyndn,task_description,resolved
+VisualEditor: Lazy-update SurfaceFragment,Now merged.,1366656030,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g5zcpdywgfveewvgyndn,task_subcomment,NA
+VisualEditor: Lazy-update SurfaceFragment,Related URL: https://gerrit.wikimedia.org/r/60256 (Gerrit Change I9e9818da1baa8319a3002f6d74fd1aad6732a8f5),1366630459,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g5zcpdywgfveewvgyndn,task_subcomment,NA
+VisualEditor: Lazy-update SurfaceFragment,Trevor is adding a bunch of .destroy() calls to SurfaceFragment uses to mitigate the problem. These should be removed once this is implemented.,1366245134,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-g5zcpdywgfveewvgyndn,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"In advance of fixing bug 47328 (which will probably be after the July release), we need to prevent the broken behaviour outlined by C. Scott in bug 47328 comment 1 - so just refuse to load on a page which is a redirect?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47328",1366224540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yop2zgg7fofkoppm6y4x,task_description,resolved
+VisualEditor: Refuse to load for pages which are redirects,Merged; will go out with wmf5.,1368884901,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,Related URL: https://gerrit.wikimedia.org/r/64275 (Gerrit Change I68836156c35c796aa2156c382992b0c105ae34cf),1368789913,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"(In reply to comment #3)
+> It seems like it would be trivial to check whether the page is a redirect and
+> simply disable VisualEditor if so. I'm adding the ""easy"" keyword to this bug.
+
+It gets a bit trickier if the page does not yet exist, though.",1368665165,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"It seems like it would be trivial to check whether the page is a redirect and simply disable VisualEditor if so. I'm adding the ""easy"" keyword to this bug.",1368574217,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"(In reply to comment #1)
+> For me, if you tried to edit a redirect page, it loads with the redirected
+> page.
+
+Yes, this is current behaviour from Parsoid that will be fixed by fixing bug 47328, but that will leave users with a very confusing blank page. That is why I made this bug. :-)",1366384860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"**dayuloli** wrote:
+
+For me, if you tried to edit a redirect page, it loads with the redirected page.",1366371378,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+"VisualEditor: Fix ""Report problem"" button, broken by IVStore change","In ve.init.mw.Target.prototype.reportProblem, we pass an HTMLDocument to getDataFromDom(), but this function now takes two parameters, with the IVStore coming first, so it fatals with ""doc is undefined"".
+
+In addition to passing in a store, we'll also need to expand the returned data before transmitting it, per bug 47318.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366215060,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-66lb2jf7kuruqajpygry,task_description,resolved
+"VisualEditor: Fix ""Report problem"" button, broken by IVStore change",This is now merged.,1366652317,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-66lb2jf7kuruqajpygry,task_subcomment,NA
+"VisualEditor: Fix ""Report problem"" button, broken by IVStore change",Related URL: https://gerrit.wikimedia.org/r/59642 (Gerrit Change I761523d22e51ac560e37ae991d01a6b84224ca40),1366216629,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-66lb2jf7kuruqajpygry,task_subcomment,NA
+VisualEditor: Provide a way to expand data using an IVStore for transmission over the wire,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366214880,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-u4ghwr7nh5cniopiuid3,task_description,resolved
+VisualEditor: Provide a way to expand data using an IVStore for transmission over the wire,Related URL: https://gerrit.wikimedia.org/r/60925 (Gerrit Change I4819cf06d1bd0ae4f8b896052e278ca75c9551bf),1366925797,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u4ghwr7nh5cniopiuid3,task_subcomment,NA
+VisualEditor: html/* attributes shouldn't be cloned when cloning elements,"We're cloning html/data-parsoid which Subbu tells me messes with selser correctness
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366155600,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-p6hdrbkwl7jmyhc7wdyj,task_description,resolved
+VisualEditor: html/* attributes shouldn't be cloned when cloning elements,This is now merged.,1366652364,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6hdrbkwl7jmyhc7wdyj,task_subcomment,NA
+VisualEditor: html/* attributes shouldn't be cloned when cloning elements,Related URL: https://gerrit.wikimedia.org/r/59836 (Gerrit Change I428becf95c70d0ed8af5b0c408e3966dc47fd8c3),1366300913,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6hdrbkwl7jmyhc7wdyj,task_subcomment,NA
+VisualEditor: html/* attributes shouldn't be cloned when cloning elements,"Roan clarified on IRC that this is not happening right now, but about and typeof attributes should not be cloned either. Just adding here to track info. in one place.",1366155988,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-p6hdrbkwl7jmyhc7wdyj,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"To give an example:
+mediawiki.page.ready.js runs on mobile (it specifies targets=>mobile) however attempts to lazy load the tablesorter plugin which is not available on mobile (it specifies targets=>desktop)
+
+This currently throws an exception.
+
+Avoiding a bike shedding conversation about whether jquery.tablesorter should be available on mobile, it is wrong to make the assumption that a module will always be available.
+
+Expected: Instead of seeing an exception I would like to allow the user to handle the error themselves - allowing optional modules to die silently.
+
+e.g.
+mw.loader.using( 'jquery.tablesorter', function () {
+	$sortableTables.tablesorter();
+}, function( e ) {
+throw e;
+});
+
+or 
+mw.loader.using( 'jquery.tablesorter' ).done( function () {
+	$sortableTables.tablesorter();
+});
+
+Another example of this being a problem is on the edit page which asumes mediawiki.action.edit is available:
+
+mw.loader.using(""mediawiki.action.edit""
+
+Currently there is a hack in MobileFrontend to get around this [1]
+
+
+[1] https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/MobileFrontend.git;a=blob;f=includes/skins/SkinMobile.php;h=27ab4ef44fc138566bbf3e1ab32cd5af20daf246;hb=HEAD#l241
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal",1366152300,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-foy2pwxdiqiuemtnxzak,task_description,declined
+mw.loader.using should not throw an exception when an optional module doesn't exist,"I'll tentatively close this, then, to have less stuff seemingly blocking the release.",1383254422,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"I am happy for someone to agree with Krinle and close this as WONTFIX
+The mobile skin doesn't load mediawiki.page.ready now since we introduced Skin::getDefaultModules so the original problem isn't a problem.
+
+If someone really wants to load something optionally they can use a try / catch",1383252679,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"Is this blocking the release, and if yes, why has nobody done anything about it? I sympathise with Krinkle's comment 7.",1383248523,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"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.",1380208136,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"This is now less of a problem in mobile as we have reduced the possibility of this happening to only situations where a module has been renamed/typed incorrectly/ is not available due to being in mobile mode rather than desktop. The tablesorter exception is no longer called.
+
+My main worry about this is that since ResourceLoader concatenates code one module failing can prevent the execution of another module. This seems wrong. I can understand an entire module from throwing an exception and not executing but stopping all javascript from executing seems wrong.
+
+I really don't understand the need for an exception under all circumstances. Could we not default the error handler to throwing an exception to at least allow developers to override it. For example a gadget might want to do something with a module if it's available but fail silently if it's not so it can be used on as many wiki's as possible that may or may not have the module it does something with)
+
+// module 1
+mw.loader.using( 'foobar', function() {
+} );
+
+// module 2
+(function(){ alert( 4 ); })()
+
+On a similar subject it would be great to see mw.loader.using return a jQuery.deferred object.",1370024390,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,See bug 47882 to discuss my side note about mediawiki.page.ready - please leave discussion on this bug simply about behaviour for when a module doesn't exist.,1367334019,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"jQuery.tablesorter seems to be an optional dependency - the code is loaded in the client only on pages which need it (otherwise the 'mediawiki.page.ready' resource loader module would specify it as a hard dependency in its dependencies)
+
+If jquery.tablesorter was listed in the module manifest [1] for mediawiki.page.ready I could understand it throwing an exception when mediawiki.page.ready uses it - but it is /NOT/ thus the code in mediawiki.page.ready is making a bad assumption that that module exists and is available. In this case it is an optional module (otherwise it would be in the module manifest of a module that /has/ been knowingly added to the page) and the page will survive without it. I am sure however in other cases an exception might make more sense e.g. mw.using( 'mediawiki.modulethatwasrenamed' ). I don't know the resource loader code well enough but it seems it would be useful to distinguish between modules that do not exist and modules that have the wrong target.
+
+On a side note mediawiki.page.ready doesn't look very useful to mobile - input placeholders are not really a problem on modern mobile browsers, we don't use the collapsible code, as this bug reveals the tablesorter isn't expected to work, access keys are useless on mobile and CheckboxShiftClick - I have no idea what that is but doesn't sound very mobile friendly. For our particular problem we should probably simply disable this module on the mobile site - yet it seems to be needed for qunit (wtf)?! [2]
+
+[1]
+'mediawiki.page.ready' => array(
+		'scripts' => 'resources/mediawiki.page/mediawiki.page.ready.js',
+		'dependencies' => array(
+			'jquery.checkboxShiftClick',
+			'jquery.makeCollapsible',
+			'jquery.placeholder',
+			'jquery.mw-jump',
+			'mediawiki.util',
+		),
+		'targets' => array( 'desktop', 'mobile' ),
+	),
+
+
+Krinkle I disagree that we should enable jquery.tablesorter on mobile and we certainly shouldn't do it 'simply' - but that's another bug/discussion (see my comments on bug 47858) - let's not discuss that here.
+
+
+[2] Change-Id: I84e0512590de9ff2dbdf519d983a0c1c2d007194",1367333875,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"For the curious, you can find the problematic behavior exemplified on:
+https://en.m.wikipedia.org/wiki/Wikipedia:Sortable_table",1367281374,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"**jgonera** wrote:
+
+Krinkle, I agree. If we deprecate the error callback, then throwing an error is OK. But let's make it consistent.
+
+Also, Jon, this particular mediawiki.action.edit case will become less important to us because we can, and hopefully soon will, provide our own custom edit form, instead of the one generated by EditPage.php.",1367280531,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"(In reply to comment #5)
+> That change should go out during next Tuesday's regular deployment
+
+For the deployment I think it is more feasible to simply enable jquery.tablesorter on mobile. We can decide whether to surpress error reporting on missing dependencies later.",1367280280,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"I'm not convinced that this should be solved by suppressing the exception and turning it into an optional callback.
+
+When a dependency is specified in the module manifest that doesn't exist[1], we throw. This is currently the case and (afaik) acceptable behaviour because it is a fatal problem. The code must not be attempted to run without that other module.
+
+When a dependency is specified inline at runtime (wrapping the code in a function) which doesn't exist, we throw. I don't see why that would be any different.
+
+Yes, mw.loader.using has an error callback. But aside from this being almost never used (I haven't seen it in use, ever), it is unlikely that an implementation would be anything other than throwing an error. The module ought to be there.
+
+When a module is added to the page by an extension or by core, it is with the intention to make something happen on that page. If that module is unable to load its code, that should throw.
+
+ext.wikiLove.init, ext.articleFeedback.init, VisualEditor, mediawiki.page.ready. All of these load modules after a check or event. They should not be loaded on the page if their dependencies are not available, and loading it anyway should throw.
+
+I'd recommend: Look at this error and fix it.
+
+In this case it means a module is loaded on mobile but one of its dependencies is not yet compatible with mobile. That means it (=jquery.tablesorter) should either be made compatible, or the containing module removed from mobile for the mean while (=mediawiki.page.ready). This isn't my own idea, I've seen this happen before with various other modules and I'm merely suggesting we act the same.
+
+This error is good, because without it you wouldn't have known that we made a mistake and forgot one of the dependencies of mediawiki.page.ready when you enabled it on mobile. This is how we found them before as well, except before they were server-side dependencies and now they're inline.
+
+
+Having said that, I'd like a view from Roan and/or Trevor on this as well. Personally I'd like to keep this exception and instead deprecate the error callback.
+
+
+[1] Exist as in, in the current execution. Because since the 'target' property was created a module can exist in general, but be invisible to the current request context based on the 'target' parameter, thus making any errors related to it somewhat ambiguous (not visible in this target vs. module not existing in general - very different problems).",1367280136,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,Re-opening. Please don't mark bug fixed until they are approved and landed in master.,1367278982,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,That change should go out during next Tuesday's regular deployment,1367012844,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,Related URL: https://gerrit.wikimedia.org/r/60346 (Gerrit Change Ic2f81b725acac2086178e33033f10c4c80ae1573),1366670776,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"Well it's more a historic problem. If a module has been added via out->addModules previously requesting a module vs mw.loader.using was unlikely to throw an exception.
+
+Now with the targets property this becomes more muddled.. a module may or may not be there - it's at the mercy of the current target.
+
+My suggestion is to alter the implementation mw.loader.using so instead of throwing an error it accepts an error callback or even better is rewritten to return a deferred object.
+
+It should be up to the developer to throw an exception.",1366352302,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"**jgonera** wrote:
+
+So what is the problem exactly? How the proposed solutions fix it? Why wouldn't the developer do:
+
+try {
+    mw.loader.using( ...
+} catch ( e ) {
+    ...
+}",1366328222,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"""allow the user to handle the error themselves"" should read ""allow the developer to handle the error themselves""",1366152465,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+VisualEditor: ve.getHash custom hashes are double-hashed,"Our current setup for custom hashing objects to to give them a method .getHash() which looks like this:
+
+T.prototype.getHash = function () {
+  var someSubsetOfT = // code here
+  return ve.getHash( someSubsetOfT );
+}
+
+and to invoke we use
+
+ ve.getHash( instanceOfT );
+
+However ve.getHash( instanceOfT ) === ve.getHash( ve.getHash( someSubsetOfT ) )
+which isn't really what we want.
+
+One solution would be to rename getHash to getHashableObject (or something) and have it return just someSubsetOfT directly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1365087000,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-kdifvxztyisvsjamslc7,task_description,resolved
+VisualEditor: ve.getHash custom hashes are double-hashed,"Reopened for 58241, but now that is done am closing again.",1365506219,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-kdifvxztyisvsjamslc7,task_subcomment,NA
+VisualEditor: ve.getHash custom hashes are double-hashed,"Ed, did you re-open because there's more to do, or because Jenkins dying meant the changes weren't merged? :-)",1365469450,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kdifvxztyisvsjamslc7,task_subcomment,NA
+VisualEditor: ve.getHash custom hashes are double-hashed,Related URL: https://gerrit.wikimedia.org/r/58241 (Gerrit Change I6a9b42facd97fbf49042d3a082121ec93659b9f1),1365463023,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kdifvxztyisvsjamslc7,task_subcomment,NA
+VisualEditor: ve.getHash custom hashes are double-hashed,Related URL: https://gerrit.wikimedia.org/r/58235 (Gerrit Change If11071d4b04a01e25102ffb57240882f650ee10d),1365460226,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kdifvxztyisvsjamslc7,task_subcomment,NA
+VisualEditor: Inserting two paragraphs inside another paragraph results in the original paragraphs being separated by a blank paragraph,"e.g. inserting <p>c</p><p>d</p> into <p>ab</p> between a and b results in
+
+<p>a</p><p>c</p><p></p><p>d</p><p>b</p>
+
+This is because fixUpInsertion fixes c & d separately and after inserting c (by closing out a) it decides to re-open the paragraph it closed (sensible), but the d comes along as splits that new paragraph (not sensible), resulting in a blank paragraph between the two.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364923620,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yqzsqc62wfjcfr3spvjk,task_description,resolved
+VisualEditor: Inserting two paragraphs inside another paragraph results in the original paragraphs being separated by a blank paragraph,NB: this bug is not restricted to paragraphs,1364923756,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yqzsqc62wfjcfr3spvjk,task_subcomment,NA
+VisualEditor: Inserting two paragraphs inside another paragraph results in the original paragraphs being separated by a blank paragraph,https://gerrit.wikimedia.org/r/#/c/55791/,1364923669,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yqzsqc62wfjcfr3spvjk,task_subcomment,NA
+VisualEditor: Inserting content at start/end of paragraph leaves leading/trailing empty paragraph,"e.g. inserting a <p>Bar</p> into <p>Foo</p> after the last 'o' results in:
+
+<p>Foo</p><p>Bar</p><p></p>
+
+The original paragraph is split, then the Bar is inserted, then the paragraph is reopened again.
+
+Or in transaction terms:
+
+insert: '<p>Bar</p>'
+
+coverts to
+
+insert: </p><p>Bar</p><p>'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364923440,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-oohwmpwpyrfuvog4u4ox,task_description,resolved
+VisualEditor: Inserting content at start/end of paragraph leaves leading/trailing empty paragraph,Gerrit 61048 is now merged; marking as fixed - will go out in Monday's deploy train.,1367020450,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oohwmpwpyrfuvog4u4ox,task_subcomment,NA
+VisualEditor: Inserting content at start/end of paragraph leaves leading/trailing empty paragraph,For some reason the bug isn't reporting this: https://gerrit.wikimedia.org/r/#/c/61048/ addresses this and is waiting for jenkins-bot to merge it.,1367016710,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-oohwmpwpyrfuvog4u4ox,task_subcomment,NA
+"VisualEditor: Store rendered html of MW aliens in index-value store, hashed on parameters","This is in preparation for performing transactions on templates and having to update the html asynchronously.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364316180,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pxkrw7ecjvb7q433anxa,task_description,resolved
+"VisualEditor: Store rendered html of MW aliens in index-value store, hashed on parameters",This has been done in https://gerrit.wikimedia.org/r/#/c/57326/,1366130654,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pxkrw7ecjvb7q433anxa,task_subcomment,NA
+VisualEditor: Create meta item for defaultsort,"If Parsoid has a meta thing for defaultsort that is
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363989120,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4o3l42xhur3szmao22jr,task_description,resolved
+VisualEditor: Create meta item for defaultsort,This is now merged.,1367275094,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4o3l42xhur3szmao22jr,task_subcomment,NA
+VisualEditor: Create meta item for defaultsort,Related URL: https://gerrit.wikimedia.org/r/61374 (Gerrit Change I604a79c25e5b0315f7e6437da657977b0efa77db),1367246090,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4o3l42xhur3szmao22jr,task_subcomment,NA
+VisualEditor: Create meta item for defaultsort,"Now defined as:
+
+  {{DEFAULTSORT:foo}}
+
+->
+
+  <meta property=""mw:PageProp/categorydefaultsort"" content=""foo"">
+
+From https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Category_default_sort_key
+
+[Parsoid does not yet support editing of these items.]",1366665947,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4o3l42xhur3szmao22jr,task_subcomment,NA
+VisualEditor: Over-eager link inspector suggestion tool inhibits linking,"I am just trying at w:en:Vojníkov hyperlink from ""Louka"" to ""Louka (village)"". The actual link is incorrect. Using VisualEditor and FF 19.0 or G Chrome 25.0.1364.152 m. If I start to type ""Louka"" it adds ""Loukas Vyntra"" automaticaly. If I use backspace it allows me to delete ""Vyntra"" and when I delete ""s"" of ""Loukas"", it adds again ""Loukas Vyntra"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362608460,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-xbcm5bbrtpu22jkr7ofg,task_description,resolved
+VisualEditor: Over-eager link inspector suggestion tool inhibits linking,Confirming that this is now fixed. Sorry for the delay in responding.,1367548440,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xbcm5bbrtpu22jkr7ofg,task_subcomment,NA
+VisualEditor: Over-eager link inspector suggestion tool inhibits linking,Thanks for the report; this is a known issue - I think we've fixed it but it's not yet pushed to live - throwing to Trevor to confirm.,1362617782,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xbcm5bbrtpu22jkr7ofg,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,"VisualEditor should be deployed to the Hebrew Wikipedia as soon as possible. I did some basic testing on my machine, and I see that it's more or less as functional as it is on the English - basic formatting works, and even basic RTL is correct.
+
+Obviously, there are many RTL issues to test there. I am doing such testing myself every now and then, but letting more people test will be far more beneficial.
+
+Of course, I am talking about a dark launch at this point - it should only be available to users who specifically request it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1362513780,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-p6aosiypctjfd3m7mled,task_description,resolved
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,"\ס/
+
+Thank you!",1366913248,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,This is now deployed to hewiki (and 13 others).,1366909636,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,Related URL: https://gerrit.wikimedia.org/r/60293 (Gerrit Change Ic9ee32df65ee9d885bf19a1592e1e8e3a8d54db0),1366652184,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,This is now scheduled for 2013-04-25.,1366396701,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,"This is very high priority for us (for hewiki and all the others of course), but as Roan says it's blocking on a version of Parsoid that we can deploy that will work with non-English wikis - see bug 43332 for details.",1362520790,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,"I support this, but I will make one observation. The version of Parsoid that's running in production is fairly old (2012-12-12 or thereabouts), so if there's anything in Parsoid that Hebrew depends on that was added after mid-December, it won't be live yet.
+
+We can't upgrade Parsoid right now because the Parsoid team is rewriting the serializer and master is too broken to deploy right now. We'll probably make a deployment attempt within the next two weeks, but until then, we'll keep running this ancient (but apparently stable, for English at least) version of Parsoid.",1362514401,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"**Author:** `afeldman`
+
+**Description:**
+The FORCE INDEX provided in this query results in a /much/ slower query plan than without.  This is the case with both MySQL 5.1-facebook, and MariaDB 5.5, so it should just be removed.
+
+Query:
+
+SELECT /* IndexPager::buildQueryInfo (contributions page unfiltered) user */  rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,user_name,page_namespace,page_title,page_is_new,page_latest,page_is_redirect,page_len,ts_tags  FROM `revision` FORCE INDEX (user_timestamp) INNER JOIN `page` ON ((page_id = rev_page)) LEFT JOIN `user` ON ((rev_user != 0) AND (user_id = rev_user)) LEFT JOIN `user_groups` ON ((ug_user = rev_user) AND  ug_group = 'bot') LEFT JOIN `tag_summary` ON ((ts_rev_id=rev_id))  WHERE (rev_user >18370655) AND (ug_group IS NULL) AND ((rev_deleted & 4) = 0) AND (rev_timestamp<'20130301192103')  ORDER BY rev_timestamp DESC LIMIT 51;
+
+Times of the query as above:
+
+production enwiki master - mysql 5.1-facebook:  51 rows in set (7 min 23.03 sec) 
+mariadb 5.5.29:  51 rows in set (1.29 sec)
+
+Times with the FORCE INDEX (user_timestamp) removed
+production enwiki master - mysql 5.1-facebook:  51 rows in set (0.26 sec)
+mariadb 5.5.29:  51 rows in set (0.20 sec)
+
+The EXPLAIN without the FORCE INDEX looks worse on 5.1 without than with, based on number of rows examined, but it avoids a filesort.  It looks better without the FORCE INDEX on mariadb than mysql 5.1 with or without.  In both cases, rev_timestamp is used instead of user_timestamp.
+
+--------------------------
+**Version**: 1.21.x
+**Severity**: normal",1362175380,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3dsaxavgxklzocfpg2pl,task_description,resolved
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"I think this reappeared, but given the age of this ticket, I will open a new one (probably not related to the original issue anymore).",1520352668,PHID-USER-gzd4fguky5ixnvz46fvu,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,Presumed fixed.,1386216223,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Change 96228 merged by jenkins-bot:
+remove specific FORCE INDEX clauses causing trouble
+
+https://gerrit.wikimedia.org/r/96228",1384883673,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Change 96228 had a related patch set uploaded by Aaron Schulz:
+remove specific FORCE INDEX clauses causing trouble, bug 45619
+
+https://gerrit.wikimedia.org/r/96228",1384883143,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Change 96228 had a related patch set uploaded by Springle:
+remove specific FORCE INDEX clauses causing trouble, bug 45619
+
+https://gerrit.wikimedia.org/r/96228",1384855075,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Not entirely sure why I was CCed on this, but...
+
+Regarding the FORCE INDEX (user_timestamp) in comment 0, that appears to be coming from includes/specials/SpecialContributions.php, ContribsPager::getUserCond() and ContribsPager::getQueryInfo(). git archeology finds that this force index was added way back in 2005, r9796.
+
+Regarding the FORCE INDEX (change_tag_tag_id) in comment 3, that's coming from ChangeTags::modifyDisplayQuery(), added in r49068 with a comment ""fix tag filtering by adding a FORCE INDEX to the relevant queries"". There's also forcing of that index in API modules that do the same sort of thing added in r58399, which refers to bug 22032, which makes it sound like r49068 was fixing some issue where a bad query was bringing down the site. Since I have no idea of the background on that and the problematic queries don't seem to be mentioned in the change summaries, I'm CCing some of the people involved in those revisions.",1378484433,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Found another example of this with a slightly different query form:
+
+SELECT /* IndexPager::buildQueryInfo (contributions page unfiltered) 14.0.143.195 */ rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,user_name,page_namespace,page_title,page_is_new,page_latest,page_is_redirect,page_len,ts_tags FROM `revision` INNER JOIN `page` ON ((page_id = rev_page)) LEFT JOIN `user` ON ((rev_user != 0) AND (user_id = rev_user)) LEFT JOIN `tag_summary` ON ((ts_rev_id=rev_id)) INNER JOIN `change_tag` FORCE INDEX (change_tag_tag_id) ON ((ct_rev_id=rev_id)) WHERE rev_user = '3030741' AND ((rev_deleted & 4) = 0) AND ct_tag = 'visualeditor' ORDER BY rev_timestamp DESC LIMIT 51;
+
+On enwiki, forcing the index hits ~900000 rows with a temp table and filesort. Without the force: ~50000 rows, no temp table or filesort.
+
+Both 5.1 and 5.5 EXPLAIN look the same, so removing this FORCE on change_tag_tag_id would also be a win across the board.",1377847274,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Bump. These queries forcing user_timestamp are running for 5+ minutes on slaves for several of the bigger WMF wikis.
+
+Multiple identical copies running simultaneously too, presumably when clients assume slow == failure and blindly retry.
+
+Re comment 2: Example would be good. Best to review EXPLAIN output for one forcing usertext_timestamp. It might be a completely different story.",1377745498,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"(In reply to comment #0)
+> The EXPLAIN without the FORCE INDEX looks worse on 5.1 without than with,
+> based
+> on number of rows examined, but it avoids a filesort.  It looks better
+> without
+> the FORCE INDEX on mariadb than mysql 5.1 with or without.  In both cases,
+> rev_timestamp is used instead of user_timestamp.
+
+	function getIndexField() {
+		return 'rev_timestamp';
+	}
+
+
+
+There is also code using usertext_timestamp:
+
+			if ( $uid ) {
+				$condition['rev_user'] = $uid;
+				$index = 'user_timestamp';
+			} else {
+				$condition['rev_user_text'] = $this->target;
+				$index = 'usertext_timestamp';
+			}
+
+
+CREATE INDEX /*i*/user_timestamp ON /*_*/revision (rev_user,rev_timestamp);
+CREATE INDEX /*i*/usertext_timestamp ON /*_*/revision (rev_user_text,rev_timestamp);
+
+
+I guess we should remove the force index for that one too?",1362175775,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+VisualEditor: 'generated' property should not be preserved when unwrapping,"When we unwrap lists, we currently preserve the internal 'generated' property on paragraphs inside those lists, but we really shouldn't. The fact that we don't currently clear this when unwrapping results in the following serious bug:
+
+1. Create a page with the following content
+Foo
+Bar
+* Baz
+* Quux
+* Whee
+Yay
+2. Open the page in VE
+3. Select across the three list items and click the list button to unlist them
+4. VE now shows five paragraphs
+5. Click ""Review and save"" and observe the diff.
+
+Expected diff: the asterisk and space before ""Baz"", ""Quux"" and ""Whee"" are removed.
+
+Actual diff: the second line becomes ""BarBazQuuxWhee"", followed by three blank lines, then ""Yay"".
+
+This happens because the converter unwraps paragraphs with the 'internal': { 'generated': 'wrapper' } property, even if these paragraphs now appear in a different context and even if there are multiple such paragraphs adjacent to each other.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362090720,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dh3tjq2uz3nbefcu74t6,task_description,resolved
+VisualEditor: 'generated' property should not be preserved when unwrapping,Code now merged.,1363139748,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dh3tjq2uz3nbefcu74t6,task_subcomment,NA
+VisualEditor: 'generated' property should not be preserved when unwrapping,https://gerrit.wikimedia.org/r/#/c/52046/,1362414620,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dh3tjq2uz3nbefcu74t6,task_subcomment,NA
+VisualEditor: You cannot create pre-formatted blocks spanning multiple lines,"1. Create a document ""First line.Second line""
+2. Select this text and insert a newline between the '.' and the 'S' (currently, using the Enter key).
+
+Expected result: a single <pre> block with a single newline after the full stop, converting to "" First line.\n Second line"" in wikitext. Note that this is trivially-obvious on MW Vector due to the ""border: 1px dashed #2f6fab;"".
+
+Actual result: two separated <pre> blocks (with a slug between them), converting to "" First line.\n\n Second line"" in wikitext.
+
+I presume that we'll want to retain Enter as a break-me-out-of-this-context newline, and use Shift-Enter to allow insertion of the above.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361768160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iadcnxx6h6rf3uwphvzc,task_description,resolved
+VisualEditor: You cannot create pre-formatted blocks spanning multiple lines,"**orbit** wrote:
+
+Fixed here: https://gerrit.wikimedia.org/r/#/c/50862/",1361841038,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-iadcnxx6h6rf3uwphvzc,task_subcomment,NA
+VisualEditor: Split out MediaWiki-specific dm stuff into a separate directory,"Stuff like ve.dm.MWInternalLinkAnnotation , ve.dm.modelRegistry.registerExtensionSpecificType( /^mw:/ ), etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1361572320,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3jc7jvjjcdtgrshlnq7r,task_description,resolved
+VisualEditor: Split out MediaWiki-specific dm stuff into a separate directory,Fixed as part of a larger move in https://gerrit.wikimedia.org/r/71755,1372875174,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3jc7jvjjcdtgrshlnq7r,task_subcomment,NA
+VisualEditor: Split out MediaWiki-specific dm stuff into a separate directory,"Roan, is this now closeable?",1367548264,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3jc7jvjjcdtgrshlnq7r,task_subcomment,NA
+VisualEditor: Split out MediaWiki-specific dm stuff into a separate directory,"Some more MW specific nodes:
+https://gerrit.wikimedia.org/r/#/c/51621/",1362185032,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3jc7jvjjcdtgrshlnq7r,task_subcomment,NA
+VisualEditor: Editing in a section causes changes elsewhere to be deleted (Parsoid selser bug?),"Changes made in screen
+
+Issues of editing when making changes in a section of https://en.wikipedia.org/wiki/William_Francis_Magie - probably Parsoid selser issue. JDF to re-check when new Parsoid deployed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10305}",1361474460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lemidsivs6ktavbh7gts,task_description,resolved
+VisualEditor: Editing in a section causes changes elsewhere to be deleted (Parsoid selser bug?),"This is now fixed given the Parsoid update, yay.",1366396637,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lemidsivs6ktavbh7gts,task_subcomment,NA
+VisualEditor: Editing in a section causes changes elsewhere to be deleted (Parsoid selser bug?),"Created attachment 11825
+Diff coming back with only changed area
+
+**Attached**: {F10306}",1361474511,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lemidsivs6ktavbh7gts,task_subcomment,NA
+VisualEditor: Create isolate method in SurfaceFragement,"The method should isolate a selection of siblings from the siblings either side of it by creating close/open tags with either side of it where necessary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361474340,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zbiughyq34hw6tacnlnj,task_description,resolved
+VisualEditor: Create isolate method in SurfaceFragement,This code was merged.,1363280996,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zbiughyq34hw6tacnlnj,task_subcomment,NA
+VisualEditor: Create isolate method in SurfaceFragement,https://gerrit.wikimedia.org/r/#/c/50199/,1361564493,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zbiughyq34hw6tacnlnj,task_subcomment,NA
+VisualEditor: Remove all code related to change markers,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1360974360,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-njupimbksvxhw4nnmsfy,task_description,resolved
+VisualEditor: Remove all code related to change markers,This is now merged.,1367527194,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-njupimbksvxhw4nnmsfy,task_subcomment,NA
+VisualEditor: Remove all code related to change markers,Public documentation at http://www.mediawiki.org/wiki/VisualEditor/Change_markers should be deleted or marked as deprecated once this has been merged.,1361228878,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-njupimbksvxhw4nnmsfy,task_subcomment,NA
+VisualEditor: Remove all code related to change markers,https://gerrit.wikimedia.org/r/#/c/49363/,1360975640,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-njupimbksvxhw4nnmsfy,task_subcomment,NA
+VisualEditor: Support transactions on metadata,"In order to implement a category editor, we'll need to be able to process transactions on metadata.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1360890960,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-266a7gondg6gygyomb2r,task_description,resolved
+VisualEditor: Support transactions on metadata,https://gerrit.wikimedia.org/r/#/c/49182/,1360891883,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-266a7gondg6gygyomb2r,task_subcomment,NA
+VisualEditor: Wikitext preview doesn't refresh in new page creation mode,"1. Load a new (i.e. not currently existing) page into VE
+2. Type some text
+3. Click ""Review and save"". The corresponding wikitext appears in a flyout
+4. Close the flyout using the up arrow
+5. Change the text in the editor
+6. Click ""Review and save"" again.
+
+The flyout that appears in #6 will display the same wikitext as in #3, even though you changed the document. The diff flyout handles this correctly (i.e. it caches the old diff until you change something), but the serialization flyout for new page creation never clears its cache.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1360878660,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tqdmz6elwsrngx5orrvl,task_description,resolved
+VisualEditor: Wikitext preview doesn't refresh in new page creation mode,"
+
+*** This bug has been marked as a duplicate of bug 44446 ***",1360878886,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqdmz6elwsrngx5orrvl,task_subcomment,NA
+VisualEditor: Parsoid selective serialisation failure when deleting an LI (artefact of old version of Parsoid?),"**Author:** `phil`
+
+**Description:**
+shows the result after a save with 'friend' being duplicated
+
+Text was several lines long
+Placed cursor at start of last line
+Pressed delete to move the line up to the same line as the second to last
+Saved
+The last line has not been deleted and it also present on the second to last
+
+Screenshot attached
+This
+is
+the
+end
+my
+friend
+
+- put cursor at start of friend and pressed delete and then added a space
+
+Screenshot shows the result, 'friend' is now in twice
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10875}",1360124400,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jnxq7ir4c6munsrkbn2f,task_description,resolved
+VisualEditor: Parsoid selective serialisation failure when deleting an LI (artefact of old version of Parsoid?),This is now fixed given the Parsoid update. Sorry for the delay.,1366396569,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jnxq7ir4c6munsrkbn2f,task_subcomment,NA
+VisualEditor: Parsoid selective serialisation failure when deleting an LI (artefact of old version of Parsoid?),"Thanks for this, report Phil; I can confirm the issue.
+
+It is probably due to us running quite an old version of Parsoid on the live service; we need to update it to a newer version (which has been delayed for other before I can determine if we still have action to take here).",1360210562,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jnxq7ir4c6munsrkbn2f,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"**Author:** `phil`
+
+**Description:**
+Page after cut and paste of 'a b c' only showing the 'a'
+
+Created a simple file
+a
+b
+c
+
+Copied all the text, placed the cursor after the 'c' and pasted it
+The 'a' from the copy was pasted, the 'b' and 'c' were lost
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10869}",1360122240,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_description,resolved
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),This is now fixed given the Parsoid update. Sorry for the delay.,1366396479,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"Ah, right. This is, I think, a Parsoid-related bug, which should get fixed when the new version of Parsoid can be deployed; assigning to myself for review when we get that out.",1361403605,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"**orbit** wrote:
+
+I think this is a serialization bug. The linear model shows the full data after paste:  
+[
+Object
+, ""a"", 
+Object
+, 
+Object
+, ""b"", 
+Object
+, 
+Object
+, ""c"", ""a"", 
+Object
+, 
+Object
+, ""b"", 
+Object
+, 
+Object
+, ""c"", 
+Object
+]
+but it's not correctly saving. Testing here: http://www.mediawiki.org/wiki/VisualEditor:CopyPaste",1361401270,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"**phil** wrote:
+
+This was Safari/Mac - I have just tried it on Chrome/Mac and was able to reproduce
+
+Just to confirm the steps
+a
+b
+c
+
+Save this - this is 3 separate lines
+Edit
+Copy all the text, paste after the 'c'",1360210696,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"Phil, what browser were you using? I'm afraid I cannot reproduce on Chrome/Mac or Safari/Mac; Firefox has wider issues (that mean I can't copy-and-paste anything; to follow-up).",1360210375,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Screenshot
+
+When edited in VisualEditor, the following table:
+
+```
+{| class=""wikitable""
+|- 
+! Header
+|-
+| {{Yes}}
+|}
+```
+... shows the following string in place of the {{Yes}} template:
+
+style=""background: #90ff90; color: black; vertical-align: middle; text-align: center; "" class=""table-yes""|Yes
+
+See screenshot.
+Live at http://en.wikipedia.org/wiki/User:Nicolas1981/Sandbox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50589
+
+**Attached**: {F10493}",1359530280,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-jer6pedsydbmctp5xlhb,task_description,resolved
+Template creating CSS in a table's cell does not come through,"Change 76861 abandoned by Subramanya Sastry:
+WIP: first draft of td reparse.
+
+Reason:
+Not required anymore. A DOM-based solution is already merged and in production.
+
+https://gerrit.wikimedia.org/r/76861",1386964245,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,Minor niggle: The caches are not yet cleared as we don't have the rights to do so. Cached pages will only update to the correct rendering after that has happened.,1377187050,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"(In reply to comment #31)
+> (In reply to comment #19)
+> > Scott, is the glitch with the certification tables at
+> > http://en.wikipedia.org/w/index.
+> > php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> > another effect of 50589, this bug, or should I open a new bug report for it?
+> 
+> That was bug 50589, which is now fixed.
+
+Correction: It was very similar to 50589, but not quite the same.
+
+In other news about this bug, https://gerrit.wikimedia.org/r/#/c/79943/ is now deployed, which covers the vast majority of cases including the ones mentioned here. Closing as fixed.",1377186266,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"(In reply to comment #19)
+> Scott, is the glitch with the certification tables at
+> http://en.wikipedia.org/w/index.
+> php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> another effect of 50589, this bug, or should I open a new bug report for it?
+
+That was bug 50589, which is now fixed.",1377035994,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,The DOM handler is now ready for review in https://gerrit.wikimedia.org/r/#/c/79943/.,1377032382,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,I'm working on a DOM-based handler for this. Re-assigning the bug to myself.,1376945009,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Parsoid support for this and a related table parsing issue is tracked in bug 50603, and should be ready in the next weeks.",1375651884,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #26)
+> On the enwiki-20130102-pages-articles-multistream.xml.bz2 dump, there are:
+>  13,057,082 articles, of which
+
+That looks like all namespaces, not just articles.
+
+>  11,877 (0.091%) have some use of [[Template:Table_cell_templates]], and
+>  1,875 (0.014%) have a non-trivial use (ie, the preceding character is not
+> |).
+
+That sounds about right. As a percentage of our most frequently edited articles, I suspect the percentage is much higher, though. The primary use is in award tables, and while the millions of articles about ghost towns, obscure shellfish, and asteroids tend not to discuss awards, while the ones about modern music, television, and films frequently do.",1375230977,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"On the enwiki-20130102-pages-articles-multistream.xml.bz2 dump, there are:
+ 13,057,082 articles, of which
+ 11,877 (0.091%) have some use of [[Template:Table_cell_templates]], and
+ 1,875 (0.014%) have a non-trivial use (ie, the preceding character is not |).",1375230080,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76861 had a related patch set uploaded by Cscott:
+WIP: first draft of td reparse.
+
+https://gerrit.wikimedia.org/r/76861",1375228678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #23)
+> (In reply to comment #22)
+> > (In reply to comment #19)
+> > > Scott, is the glitch with the certification tables at
+> > > http://en.wikipedia.org/w/index.
+> > > php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> > > another effect of 50589, this bug, or should I open a new bug report for it?
+> > 
+> > No, this is bug 52254 (which Roan already opened based on your report).
+> 
+> 52254 is relative to the incorrect italicization and bolding in the lead. It
+> does not cover the corrupted certification table (near the bottom), which is
+> another case of a template creating table markup which is displayed
+> incorrectly.
+
+Opened https://bugzilla.wikimedia.org/show_bug.cgi?id=52296 
+
+The more I play with it, the more it feels like a third related bug. It's clearly not 50589 because Parsoid can't parse it correctly, but I don't think it's a duplicate of this one, either.",1375219011,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #22)
+> (In reply to comment #19)
+> > Scott, is the glitch with the certification tables at
+> > http://en.wikipedia.org/w/index.
+> > php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> > another effect of 50589, this bug, or should I open a new bug report for it?
+> 
+> No, this is bug 52254 (which Roan already opened based on your report).
+
+52254 is relative to the incorrect italicization and bolding in the lead. It does not cover the corrupted certification table (near the bottom), which is another case of a template creating table markup which is displayed incorrectly.",1375213651,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"(In reply to comment #19)
+> Scott, is the glitch with the certification tables at
+> http://en.wikipedia.org/w/index.
+> php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> another effect of 50589, this bug, or should I open a new bug report for it?
+
+No, this is bug 52254 (which Roan already opened based on your report).",1375212812,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76758 merged by jenkins-bot:
+Add new parserTests for table cell attributes coming from templates.
+
+https://gerrit.wikimedia.org/r/76758",1375212224,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76758 had a related patch set uploaded by Cscott:
+Add new parserTests for table cell attributes coming from templates.
+
+https://gerrit.wikimedia.org/r/76758",1375211044,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+Scott, is the glitch with the certification tables at http://en.wikipedia.org/w/index.php?title=Metallica_%28album%29&oldid=566196578&veaction=edit another effect of 50589, this bug, or should I open a new bug report for it?",1375200034,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,rewritten in a more-or-less straightforward manner.,1375196456,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Having looked into it a bit, I agree that the current bug is related to bug 50589.  However, bug 50589 *should* work -- the template is still well structured, it is just generating content for more than one table cell.  This bug, on the other hand, has a template which spans structural boundaries in the HTML.  For example:
+
+{|
+|align=center {{table_attribs}}
+|}
+
+where {{table_attribs}} expands to 'style=""color: red""|Foo'.  This wants to generate something like the following HTML:
+<table><tr>
+<td align=""center"" style=""color: red""> Foo
+</td></tr></table>
+
+Note that the <td> and some of its attributes come from the article text, and the rest of the attributes come from the template. I might be able to hack this through Parsoid, but VE will probably never be able to edit the result.  (Imagine how you'd present the table cell editing UI for something like this.) So the bot approach should probably be used to clean up constructs like these, to something like:
+
+{|
+{{table_attribs|align=center}}
+|}
+
+Now the template is well-structured in the resulting html.
+
+My current approach is to attempt to get these cases parsed by parsoid, resulting in uneditable-but-visually-correct output.  We will still want a bot to rewrite the templates so to make them editable in the articles using them.
+
+As MZMcBridge correctly guessed, I'm currently running a grep over an enwiki dump to figure out exactly how many articles use table cell templates.  It's not done running yet so I don't have exact statistics, but the short answer is, ""a lot"".  So far nothing that can't be",1375196416,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #15)
+> (In reply to comment #12)
+> > Bots that modify existing articles to bypass bugs in Parsoid should be off
+> > the table as a solution.
+> 
+> [[Hard cases make bad law]]. :-)
+> 
+> As a general rule, Parsoid should be handle wikitext in the wild. However, we
+> need more information about the prevalence of these constructs on Wikimedia
+> wikis and the amount of work required to properly handle them before we can
+> make any real decisions here. Scott's Gerrit change #76626 seems to be a step
+> in the right direction.
+
+I'm more an adherent to the concept that rigorous adherence to fundamental principles always pays off in the long run, and ""Parsoid should handle all wikitext currently in existence in English Wikipedia"" strikes me as one of those fundamentals.
+
+I'm concerned by the existence of this one and its interplay with 50589. It appears that Parsoid and VE made some assumptions about how templates, wikimarkup, and tables would interact that aren't true.
+
+Take a look at the certification table in http://en.wikipedia.org/w/index.php?title=Metallica_%28album%29&oldid=566196578&veaction=edit for example. There's something going on in http://en.wikipedia.org/wiki/Template:Certification_Table_Top or http://en.wikipedia.org/wiki/Template:Certification_Table_Entry that's causing more weirdness. I don't know if that's this one, 50589, or yet another related bug.",1375138733,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"(In reply to comment #12)
+> Bots that modify existing articles to bypass bugs in Parsoid should be off
+> the table as a solution.
+
+[[Hard cases make bad law]]. :-)
+
+As a general rule, Parsoid should be handle wikitext in the wild. However, we need more information about the prevalence of these constructs on Wikimedia wikis and the amount of work required to properly handle them before we can make any real decisions here. Scott's Gerrit changeset 76626 seems to be a step in the right direction.",1375134893,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76626 merged by jenkins-bot:
+Add 2 more dumpGrepper patterns to get a handle on bug 44498.
+
+https://gerrit.wikimedia.org/r/76626",1375132104,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76626 had a related patch set uploaded by Cscott:
+Add 2 more dumpGrepper patterns to get a handle on bug 44498.
+
+https://gerrit.wikimedia.org/r/76626",1375131923,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #11)
+> We are definitely not trying to make life harder for editors.  We are just
+> trying to figure out the best solution going forward.
+
+The best solution going forward is to repair Parsoid. While I agree that we can do things with wikitext that no sane person would *want* to, there's no way to prevent us from doing so, and VE cannot fail based on things that work fine in the standard editor.
+
+Bots that modify existing articles to bypass bugs in Parsoid should be off the table as a solution.",1375126397,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"We are definitely not trying to make life harder for editors.  We are just trying to figure out the best solution going forward.
+
+Visual editing is a HTML-based operation, and HTML has structural semantics.  Longer-term, it would make for a better and simpler software and editing interface if templates generated entire html elements instead of part of elements (which these templates do).  We are just trying to reconcile wikitext structural information with HTML structural information with a view towards the long-term.
+
+While we definitely welcome participation and support of existing template/bot authors here, we are definitely not planning to offload this job of writing bots or updating pages onto editors.
+
+All that said, resolving this issue might well involve a temporary interim fix and a strategy for a longer-term resolution that moves wikitext and templates towards a more cleaner solution that is more aligned with HTML DOM semantics.",1375125861,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+Why would we change the contents of articles to match something that Parsoid likes instead of repairing Parsoid? 
+
+The specification of Parsoid surely must have included a spec that all templates and wikitext syntax in widespread use in English wikipedia needed to be handled properly. Since Parsoid doesn't meet that requirement, repair Parsoid.",1375124914,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"From an email thread with Subbu & C.Scott:
+
+Subbu writes:
+
+Gabriel and I started discussing this the week before he headed out on vacation ... we'll continue once he is back ... we might either have to hack or use other tricks to support these templates.  A bot pass (https://bugzilla.wikimedia.org/show_bug.cgi?id=50547) is one idea we've considered (first fix up the templates, and then use a bot to go and fix pages that use the templates).
+
+---
+I asked:
+
+If we wanted to improve the markup of these templates so they can be more sanely parsed, what instructions would we provide?
+
+---
+Subbu responds:
+
+Instead of generating just style attributes of a table cell, make the ""|"" char part of the template.  So, the templates should produce a styled-cell rather than just the cell-style. And, that also means that the pages that use these should not have ""|"" char before the transclusion -- but we may be able to work around by recognizing that pattern (I say that without working through the details).
+
+So, instead of (old wikitext):
+{|
+| {{yes}}
+|}
+
+they would have to code this as:
+{|
+{{yes}}
+|}
+
+Looks like there are quite a few of these here: https://en.wikipedia.org/wiki/Template:Table_cell_templates  I haven't investigated all the various ways these templates are used, but at first pass, I think that approach should fix the problem.
+
+---
+
+C.Scott responds:
+
+It's probably worth bringing the VE team into this discussion.  I
+think that VE would probably struggle trying to edit table cell(s)
+generated with a template containing a style + cell contents in this
+fashion and/or have difficulty processing whatever markup we decide
+Parsoid ""should"" generate for this case.  My intuition is that fixing
+the templates to include the leading vertical bar, so that the
+template is clearly a cell, not part-of-a-cell, is a better long-term
+solution for editing (Parsoid+VE).  It seems like a bot to make this
+change could be implemented + deployed relatively quickly, although I
+haven't actually written a bot before, maybe there are community or
+other factors limiting the speed at which bot edits are made?
+ --scott
+ps. who'd be interested in writing said bot, because he's never done
+that before, although I suspect it would be best farmed off to someone
+who's done this sort of thing before.
+
+And also adds:
+
+Note that there are some anomalous usages, for example:
+
+! {{yes}}
+| rowspan=2 {{n/a}}
+
+The first case would have to be {{yes|type=header}} and the second
+something like {{n/a|rowspan=2}}, both with additional changes to the
+table cell template.  In other words, the issue isn't just that the
+style and cell content boundary is spanned, it's that some of the
+style comes from outside the template and some comes from inside.
+
+I still think a bot might be the best long-term fix, but it's not
+entirely straightforward.  If we were to fix it inside parsoid, we'd
+have to introduce something like an ""open style context"", probably
+buffering the style information and spitting it out only after we've
+seen the style context closed.  It would still be an ""interesting""
+editing challenge in VE -- some of the table style information would
+be editable, some would come from the template (and be editable only
+inside the template editor?).
+ --scott",1375122625,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Bumping up the importance, per comment 7.",1374874237,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+This one as well: http://en.wikipedia.org/w/index.php?title=List_of_Big_Time_Rush_episodes&diff=prev&oldid=565906957
+
+This really isn't a ""low importance"" bug by any stretch of the imagination. It affects most discographies, most television episode lists, and most award lists.",1374858786,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,Could aftereffects of this be responsible for the nightmare at https://en.wikipedia.org/w/index.php?title=Bosnia_and_Herzegovina_in_the_Eurovision_Song_Contest&diff=565659865&oldid=565498623 ?,1374704447,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,*** Bug 50366 has been marked as a duplicate of this bug. ***,1374455443,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"There are many templates in this set.
+https://en.wikipedia.org/wiki/Template:Table_cell_templates
+
+And the most commonly used ones are copied to other languages.  See the interwikis for {{Yes}}
+https://en.wikipedia.org/wiki/Template:Yes",1374454995,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,*** Bug 50772 has been marked as a duplicate of this bug. ***,1374454764,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"This will be hard to support, as the nested template produces part of the table cell syntax plus the table cell content. Moving the pipe starting the table cell into the template would avoid this issue as the template would then expand to a self-contained table cell with content.
+
+Are there other templates following this pattern apart from Yes (and probably No)?",1360210956,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"This is a Parsoid bug; couldn't find the master with which to mark as dupe (sorry, Gabriel!).",1360209226,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"diff about to delete existing text
+
+I've seen this a few times and I think this is the simplest reproduction. 
+
+Start with a page that has a line of text ""this text should be preserved but is not""
+
+In VE, position the cursor at the front of the line and move it two spaces down. 
+
+Move the cursor back to the top of the page. 
+
+Type a new line ""totally different stuff""
+
+Save.  Note the incorrect diff. The string ""this text should be preserved but is not"" has been deleted erroneously upon save.  
+
+Repeat the operation but this time use strings that share words, like ""this text should be preserved"" and ""this text is new""
+
+The behavior is the same, the old text is erroneously deleted, but the diff seems to have intertwined the two strings, keeping their common elements.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Cmcmahon(WMF)&oldid=535559576
+
+**Attached**: {F10454}",1359488700,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_description,resolved
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"This is now fixed given the Parsoid update. Sorry for the delay! (Note that there is a distinct error that this has just thrown up, yayfuntimes.)",1366396947,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11741
+'text should be preserved' is not
+
+real screen shot from real computer, my apologies
+
+**Attached**: {F10457}",1360210415,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11740
+text with string that will be deleted before save
+
+real screen shot from real computer
+
+**Attached**: {F10456}",1360210348,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,This looks to be a Parsoid bug (and is highly dependent on the rest of the page's content); will re-visit when Parsoid is updated before progressing.,1360208728,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"The content of attachment 11709 has been deleted by
+    James Forrester <jforrester@wikimedia.org>
+who provided the following reason:
+
+Not intended to be on Bugzilla?
+
+The token used to delete this attachment was generated at 2013-02-07 03:38:14 UTC.",1360208305,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"The content of attachment 11710 has been deleted by
+    James Forrester <jforrester@wikimedia.org>
+without providing any reason.
+
+The token used to delete this attachment was generated at 2013-02-07 03:36:53 UTC.",1360208263,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"(In reply to comment #2)
+> Created attachment 11709 [details]
+> preview of page before save has correct text
+
+(In reply to comment #3)
+> Created attachment 11710 [details]
+> saved page, existing text deleted erroneously
+Ahm.... these are pictures of deer. Just sayin'.
+
+//attachment 2012-12-30 11.02.48.jpg ignored as obsolete//",1360208240,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11710
+saved page, existing text deleted erroneously
+
+//attachment 2013-01-13 15.01.28.jpg ignored as obsolete//",1359488894,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11709
+preview of page before save has correct text
+
+//attachment 2012-12-30 11.02.48.jpg ignored as obsolete//",1359488849,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11708
+better view of intertwined strings
+
+**Attached**: {F10455}",1359488791,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"Go to a new page. Enter some content. Press review-and-save. Observe diff. Press the ""leave this context"" button (""^""). Change the content. Press review-and-save again. Observe diff.
+
+Expectation: The diff shows the changes against the new content.
+Reality: The diff shows the changes against the original content (not re-done).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1359415380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_description,resolved
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"Code now merged; thanks, Timo! Will go out in next branch.",1368043283,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,Related URL: https://gerrit.wikimedia.org/r/62847 (Gerrit Change I9eddebbdf9294ee3d46286bdf1b157e00252d300),1368037459,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"The comments above are wrong. Actual timeline:
+
+# Page load, enter text
+     ve.Surface/Model/on/transact
+     onSurfaceModelTransact Clear the diff html
+     ve.Surface/Model/on/transact
+(2x) ve.Surface/Model/on/transact
+# Press ""Review and save""
+# Close dialog
+# Enter more text
+(3x) ve.Surface/Model/on/transact
+# Press ""Review and save""
+# Close dialog",1366839502,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"Using the following debug calls:
+
+diff --git a/modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js b/modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js
+index 859d4f8..cee2505 100644
+--- a/modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js
++++ b/modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js
+@@ -390,6 +390,7 @@ ve.init.mw.ViewPageTarget.prototype.onSaveError = function ( jqXHR, status ) {
+  * @param {string} diffHtml
+  */
+ ve.init.mw.ViewPageTarget.prototype.onShowChanges = function ( diffHtml ) {
++       mw.log( 'onShowChanges', 'Invalidate the diff (by calling proxiedOnSurfaceModelTransact) on transact event' );
+        // Invalidate the diff on next change
+        this.surface.getModel().on( 'transact', this.proxiedOnSurfaceModelTransact );
+ 
+@@ -562,6 +563,7 @@ ve.init.mw.ViewPageTarget.prototype.onToolbarFeedbackToolClick = function () {
+  * @param {ve.dm.Transaction} tx Processed transaction
+  */
+ ve.init.mw.ViewPageTarget.prototype.onSurfaceModelTransact = function () {
++       mw.log( 'onSurfaceModelTransact', 'Clear the diff html' );
+        // Clear the diff
+        this.$saveDialog
+                .find( '.ve-init-mw-viewPageTarget-saveDialog-slide-review .ve-init-mw-viewPageTarget-saveDialog-viewer' )
+@@ -691,6 +693,9 @@ ve.init.mw.ViewPageTarget.prototype.setUpSurface = function ( doc ) {
+        this.surface = new ve.Surface( this, doc, this.surfaceOptions );
+        this.surface.getContext().hide();
+        this.$document = this.surface.$.find( '.ve-ce-documentNode' );
++       this.surface.getModel().on( 'transact', function () {
++               mw.log( 've.Surface/Model/on/transact' );
++       } );
+        this.surface.getModel().on( 'transact', this.proxiedOnSurfaceModelTransact );
+        this.surface.getModel().on( 'history', this.proxiedOnSurfaceModelHistory );
+        // Transplant the toolbar
+
+
+I've determined that the ""transact"" event does indeed continue to be emitted. But onSurfaceModelTransact only gets called once. It is not being rebound:
+
+
+ # Page load, enter text
+ ve.Surface/Model/on/transact load.php:11256
+ # Press ""Review and save""
+ onSurfaceModelTransact Clear the diff html load.php:11256
+ # Close dialog
+ # Enter more text
+ ve.Surface/Model/on/transact load.php:11256
+ ve.Surface/Model/on/transact load.php:11256
+ # Press ""Review and save""
+ # Close dialog
+ # Enter more lots more text
+ (14x) ve.Surface/Model/on/transact  load.php:11256",1366839306,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"(In reply to comment #3)
+> (In reply to comment #2)
+> > Which I assume means ve.dm.Surface for some reason didn't emit any - or
+> > mw.ViewPageTarget is binding it wrong, but that looks fine to me.
+> > 
+> > @Roan, any ideas?
+>
+> I'm pretty sure ve.dm.Surface emits the events correctly. You can check this
+> by
+> placing a breakpoint on the line where Surface calls this.emit().
+> 
+> It's possible there's a bug in EventEmitter with detaching and reattaching
+> though.
+
+Hm.. could be. All I know is that the attached callback didn't get fired.",1363989548,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"(In reply to comment #2)
+> Which I assume means ve.dm.Surface for some reason didn't emit any - or
+> mw.ViewPageTarget is binding it wrong, but that looks fine to me.
+> 
+> @Roan, any ideas?
+I'm pretty sure ve.dm.Surface emits the events correctly. You can check this by placing a breakpoint on the line where Surface calls this.emit().
+
+It's possible there's a bug in EventEmitter with detaching and reattaching though.",1363287954,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"Confirmed and hunt down.
+
+From what I can see the problem may be in ve.dm.Surface not emitting any 'transact' events.
+
+Adding a log() call in ve.init.mw.ViewPageTarget.prototype.onSurfaceModelTransact, shows me the following.
+
+* When entering the first characters on a new page it is called.
+  The callback then properly unbinds itself after the first call.
+* Go to ""Review and save""
+  Now it binds the event again, so that it is notified of the first
+  change (if ever) when the dialog is closed.
+  This happens in ve.init.mw.ViewPageTarget.prototype.onShowChanges
+* Close the dialog
+* Altering the document again
+
+> the method is not called
+
+Which I assume means ve.dm.Surface for some reason didn't emit any - or mw.ViewPageTarget is binding it wrong, but that looks fine to me.
+
+@Roan, any ideas?",1361815269,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,*** Bug 45021 has been marked as a duplicate of this bug. ***,1360878886,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,"For the forthcoming Template Inspector to work, we will need a way to ""hint"" for the Inspector how the parameters of the VE should be used - we're intending for now for this to be a template-hinting extension that allows editors to specify in the wikitext source what the parameters are called and how they should be used, akin to the Template documentation template on Commons.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1359413640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_description,resolved
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,"This is now deployed to all wikis. Closing.
+
+(In reply to comment #5)
+> (In reply to comment #4)
+> > We should get this deployed everywhere this coming week.
+> 
+> I'd like see to a working demo of this feature and expanded documentation at
+> [[mw:Extension:TemplateData]] before this is deployed elsewhere.
+
+I've made some quick updates, but you're right, it does need proper documentation.",1369075541,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,"(In reply to comment #4)
+> We should get this deployed everywhere this coming week.
+
+I'd like see to a working demo of this feature and expanded documentation at [[mw:Extension:TemplateData]] before this is deployed elsewhere.",1369069065,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,We should get this deployed everywhere this coming week.,1368767092,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,Live on mw.org and testwiki now.,1367277258,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,I will need to review and deploy this soonish.,1363988695,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,"Initial code in gerrit 49840 which is now merged.
+
+To come - review, deployment and usage.",1363288858,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"empty review pane, should show heading markup for non-Latin string
+
+Using a string like ""āæǣ"" or special characters like ""☺☻♥♦""
+
+Highlight the string in VE
+Choose ""Heading 1""
+
+VE displays the string larger, as expected
+
+Click ""Review and save""""
+
+Note that review pane is empty, see screen shot. 
+Click ""Looks good to me"" and finish saving. 
+
+The non-Latin string has not been affected and the Heading not been applied. 
+
+Note that normal ASCII latin strings work fine. 
+Also note that the regular editor applies the Heading markup to non-latin strings correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Cmcmahon(WMF)&oldid=535414434
+
+**Attached**: {F10377}",1359412320,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-piflhuji3l6moqmh3nbj,task_description,resolved
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"The underlying issue (with Parsoid) has been resolved with the new version of Parsoid finally running on the cluster; marking as FIXED.
+
+[I have forked comment 6 into bug 47436.]",1366414342,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"**guanhao7** wrote:
+
+I found it is impossible to use Sogou Input or other Input software to type Chinese with this tool.
+
+You may download a Sogou Input(which is the most popular one in china, on the Windows） to test it.
+
+Here is the download link: http://download.ime.sogou.com/sogou_pinyin_65f.exe?st=lTJ11fWyCsrUkj6oWiGI_Q&e=1359462829&fn=sogou_pinyin_65f.exe",1359463674,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,This would make a nice automated browser regression test,1359423892,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"OK, interesting. This is actually a quite complicated bug, and is not actually correctly-named.
+
+The problem appears to be the '[http://barbarbar bar]' beforehand - if you remove this, the diff magically ""works"" - BUT it fails to show the '[http://barbarbar bar]' being removed, and indeed puts it after the header too, with another paragraph of 'āæǣ'. The diff is the behaviour that results from the save, even though this isn't a fair representation of the document model (the '[http://barbarbar bar]' is removed from the DM).
+
+RK: this feels like a Parsoid bug (or two?), but might be on our side related to SelSer? - can you confirm before we sling it at them?",1359422565,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,Also repro'd on Chrome/Linux,1359417612,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"
+Chrome, OSX, enwiki. I can reproduce this reliably on my User page on enwiki.",1359417285,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"Afraid I can't reproduce this (it works fine for me with Firefox, Safari and Chrome from here - I get as-expected diffs, which also then save appropriately) - what wiki / version of the software was this on, and with what browser?",1359415631,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Handle Parsoid error messages and codes sanely,"VE gets some error codes and messages from Parsoid, but not a lot. I'm expanding that a little bit in a new patch [0], and it would be cool if VE could handle the errors I've added.
+
+401: Unauthorized: Should be handled as a user-visible error. Usually this means that the API isn't readable by anonymous users, but could be later used for something else. The text of the HTTP response has details about the error, so showing that to the user might be an OK solution.
+
+404: Not found: Usually means that we couldn't find anything for the article you're trying to parse or serialize. This shouldn't usually happen, but when it does, it *probably* means that the interwiki isn't set properly. Maybe hint that the user should compare their localsettings.js file to the example.
+
+500: Server error: This is a catch-all, but we'll send as much information as we can in the text of the HTTP response. Showing the user the text would go a long way towards more useful bug reports (I currently see roughly 4 suggested duplicates that have roughly the same summary....differentiating them might be helpful)
+
+These are all implemented in js/lib/mediawiki.ApiRequest.js in functions that inherit from the native Error object, so you can read it if you don't want to take my word for it.
+
+We could implement other error codes as we see cases that require them, but these are the big three. And of course 200 is the main success code.
+
+We might also be able to use some of the 3xx codes to represent redirects, but I'm not sure it would be totally useful. File a bug against Parsoid if it would be :)
+
+[0] https://gerrit.wikimedia.org/r/45794
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43147",1359142560,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-ocokyzlkygrkgdcs4rdx,task_description,resolved
+VisualEditor: Handle Parsoid error messages and codes sanely,"Marking this as done as the code's been committed; we may want to review in future (e.g. i18n of the error messages), but Gabriel has indicated that that entire area of code will be removed anyway, so marking as closed for now.",1362522586,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ocokyzlkygrkgdcs4rdx,task_subcomment,NA
+VisualEditor: Handle Parsoid error messages and codes sanely,"(In reply to comment #1)
+> Code in Gerrit change #52249
+
+This patch passes through the error messages from Parsoid to the existing error alert in VE. Mark's comment talks about providing suggestions based on the error code. Although maybe this could be done by Parsoid.
+
+This change should at least provide users with more specific errors for filing bugs.",1362505236,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ocokyzlkygrkgdcs4rdx,task_subcomment,NA
+VisualEditor: Handle Parsoid error messages and codes sanely,Code in gerrit 52249,1362504750,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ocokyzlkygrkgdcs4rdx,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"See http://inimino.org/~inimino/blog/javascript_cset for some work in this area.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1358469000,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_description,resolved
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"Like this: https://gerrit.wikimedia.org/r/#/c/54480 (well, apart from non-BMP characters...)",1363625285,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"The Unicode standard has a fair amount to say on the matter. Ideally we would implement their standard.
+
+http://www.unicode.org/reports/tr29/#Word_Boundaries",1363433728,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"As an incremental improvement I've expanded the letters and numbers groups to their Unicode categories: https://gerrit.wikimedia.org/r/#/c/53583/
+We still need to think about which punctuation categories to add.",1363195148,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"If you're going to do lexicon-based word boundary detection in Chinese, maybe you could use a word list stored in a client-side Bloom Filter. 
+
+I don't know if it's as much of a problem in Japanese; you could probably use (?<=\P{Han})(?=\p{Han}) as a good start (i.e. there is a word break be.",1363192283,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,To begin with a patch to add some test structure and fix what we have already: https://gerrit.wikimedia.org/r/#/c/53564,1363182596,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,http://xregexp.com/ has unicode character class support. We may be able to pick out the data we need from it instead of using the whole library.,1363178581,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,Acutually Chinese & Japanese don't have any word boundaries at all. The only way to detect them is with a dictionary. We'll need a special case for these languages so we don't end up selecting entire sentences.,1363176312,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"Bit of clarification:
+
+When the user clicks the link button in the toolbar and they haven't selected any text, we expand the selection in both directions from the cursor position and select the word the cursor is in, make that a link, then show the link inspector. The code that expands the selection to a full word is in ve.dm.SurfaceFragment, and apparently treats non-ASCII characters as word boundaries. The practical bug that this leads to is that if you put the cursor in the middle of ""Möckernbrücke"" (or ""égalité"", if you prefer French) and click the link button, only ""ckernbr"" (or ""galit"", respectively) will be selected and linkified. Obviously this is a problem for i18n in languages using an extended Latin alphabet like German, French and Polish, but it's a total nightmare for non-Latin languages like Russian, Hebrew and Japanese.",1363054412,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+"VisualEditor: Insertion tools (link inspector, media inserter, reference, reference list, …) don't work in slugs","Related to bug 44083
+
+Because there is not yet a paragraph to insert content in, the link inspector won't be able to insert the new link text into a slug, even if bug 44083 is fixed.
+
+The solution is probably to make the automatic paragraph insertion code in ve.ce.Surface.handleInsert more generic and moving it into ve.dm.SurfaceFragment.insertContent, triggered when inserting at a slug location.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44083",1358467500,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-iw27jj4bhfweo22d2lg4,task_description,resolved
+"VisualEditor: Insertion tools (link inspector, media inserter, reference, reference list, …) don't work in slugs",This has now been fixed and deployed.,1372462623,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iw27jj4bhfweo22d2lg4,task_subcomment,NA
+"VisualEditor: Insertion tools (link inspector, media inserter, reference, reference list, …) don't work in slugs",Noting that this is more severe.,1372253678,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iw27jj4bhfweo22d2lg4,task_subcomment,NA
+VisualEditor: Placing the cursor in a slug doesn't cause a contextChange event,"1. Make an article that begins with an alien followed by a paragraph with some text
+2. Click on a word in the paragraph
+3. Click on the slug
+4. Press the link button
+5. See that rather than the link inspector knowing to begin inserting a new link inside the slug, it inspects the word you clicked on in the paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44084
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50141",1358467260,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-6nqkzsnqx67qeicoilm6,task_description,declined
+VisualEditor: Placing the cursor in a slug doesn't cause a contextChange event,Actually closing it.,1383060862,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6nqkzsnqx67qeicoilm6,task_subcomment,NA
+VisualEditor: Placing the cursor in a slug doesn't cause a contextChange event,"Confirming that this is now fixed, and was done so some time ago - back-dating to approximately when I think it was fixed.",1382654223,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6nqkzsnqx67qeicoilm6,task_subcomment,NA
+VisualEditor: Placing the cursor in a slug doesn't cause a contextChange event,"Hm.. I can't reproduce this.
+
+
+1. Opening a MediaWiki page with the following source in VisualEditor:
+
+<<<MW
+<templatedata>{
+    ""params"": {}
+}</templatedata>
+
+Foo bar baz.
+MW;
+
+2. Selecting word ""bar"".
+3. Clicking in the slug area above the green templatedata alien.
+4. Pressing the link button.
+
+Shows a link inspector with an empty input field. Upon entering some text in the link input widget and closing the link editor, the link target page is inserted as plain text (different bug?)",1380747300,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6nqkzsnqx67qeicoilm6,task_subcomment,NA
+"VisualEditor: Key commands should be ""platform-able"".","Key commands should be able to vary based on language/locale and platform. E.g. toggling something as Bold could be:
+
+* Ctrl + b (Windows, English)
+* Cmd  + b (Mac OS X, English)
+* Meta + b (Solaris, English)
+
+* Ctrl + f (Windows, German)
+* Cmd  + f (Mac OS X, German)
+* Meta + f (Solaris, German)
+
+... etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42919",1358279820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-obbqrn6j222whjin4fm6,task_description,resolved
+"VisualEditor: Key commands should be ""platform-able"".","Now merged, will go out in 2013-02-04 release cycle.
+
+Note that the internationalisation aspect (Ctrl+F rather than Ctrl+B for Bold in German) is WONTFIX as directed by the Language Engineering team, who advised against.",1358469781,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-obbqrn6j222whjin4fm6,task_subcomment,NA
+"VisualEditor: Key commands should be ""platform-able"".",Patched in https://gerrit.wikimedia.org/r/#/c/44347/,1358375043,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-obbqrn6j222whjin4fm6,task_subcomment,NA
+VisualEditor: Clean up canHaveGrandchildren mess,"""Can have grandchildren"" is a misnamed check that should be cleaned up. What it really appears to mean is ""is this a non-content-containing branch node"", given that it checks that the node can have children, is not content, and is not a content container.
+
+canHaveGrandchildren seems to still be used in some places, it should be renamed and documented adequately.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1357966200,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xzuyfy5phfxcgoae52f6,task_description,resolved
+VisualEditor: Clean up canHaveGrandchildren mess,https://gerrit.wikimedia.org/r/#/c/53750/,1363266054,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xzuyfy5phfxcgoae52f6,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"We should use pushState such that pressing the back button after clicking VisualEditor takes you back to read mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1357863540,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_description,resolved
+VisualEditor: Browser back button should work as expected,"(In reply to Lokal_Profil from comment #11)
+> (In reply to Andre Klapper from comment #10)
+> > Lokal_Profil: Where? Example link? Browser? Reopening not helpful without
+> > giving instructions to reproduce... :-)
+> 
+> Sorry ;)
+> 
+> Confirmed in both Firefox and Chorme running on Ubuntu
+> 
+> Tested on both sv.wp[1] and en.wp[2] (logged out on sv.wp to make sure no
+> personal settings were affecting it)
+> 
+> [1] https://sv.wikipedia.org/wiki/Bonsai?uselang=en
+> [2] https://en.wikipedia.org/wiki/Bonsai
+
+Moved to bug 63739 as a new regression.",1397067880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"(In reply to Andre Klapper from comment #10)
+> Lokal_Profil: Where? Example link? Browser? Reopening not helpful without
+> giving instructions to reproduce... :-)
+
+Sorry ;)
+
+Confirmed in both Firefox and Chorme running on Ubuntu
+
+Tested on both sv.wp[1] and en.wp[2] (logged out on sv.wp to make sure no personal settings were affecting it)
+
+[1] https://sv.wikipedia.org/wiki/Bonsai?uselang=en
+[2] https://en.wikipedia.org/wiki/Bonsai",1395932065,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Lokal_Profil: Where? Example link? Browser? Reopening not helpful without giving instructions to reproduce... :-),1395925983,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,This seems to be broken again (back button changes URL but doesn't take user back to read state),1395924522,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Merged and will go out with wmf7 (from tomorrow).,1371042698,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,*** Bug 49336 has been marked as a duplicate of this bug. ***,1370840639,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Related URL: https://gerrit.wikimedia.org/r/67172 (Gerrit Change I5c345c1526852a84b04436955845bf1b56d94402),1370472014,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Related URL: https://gerrit.wikimedia.org/r/67171 (Gerrit Change Ia4b949d9c066a3f7b07217aa3d51de9908734e85),1370472012,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"Setting milestone to 2013-06-27 since it is marked as blocker for ""Beta"" (2013-07). It may be moved to an earlier milestone as we see fit. But no later than 06-27. Setting it since I use milestone to sort ""My bugs"".",1370298472,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"We currently use ?veaction=edit as trigger for VisualEditor from a permanent url.
+
+This is implemented by checking the query parameter on page load and triggering init (just like a click on ""VisualEditor"" would do), and then we replace (without refresh) the url to drop this query parameter using the HTML5 History api (replaceState).
+
+I'd recommend we build on this by using pushState when VisualEditor is initialised (we can then remove the current behaviour as there's no longer any reason to remove it from the url).
+
+Note that it is slightly more complicated than just calling replaceState on init. We also need to listen on('popstate') to move back to read mode if the user presses Back to a url within the history that contains HTML5 history state data from VisualEditor.",1368496708,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"To further clarify what the issue here is:
+
+* a user visits <https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals>;
+* user clicks ""edit"";
+* VisualEditor form loads;
+* user tries to escape the form by pressing the ""back"" button in his/her browser;
+* browser's ""back"" button doesn't work as expected (it should take the user back to the implicit view action where he/she started).",1368496497,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Is this an easy bug?,1368496332,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message","When the diff result is null (no changes), don't show a confusing blank diff but instead a message like ""There are no changes detected in your edit"" so that users aren't confused.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1357693440,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_description,resolved
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Merged; re-closing.,1368575229,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Related URL: https://gerrit.wikimedia.org/r/63691 (Gerrit Change I537bcae91f51a3f30ca4736c41f7a5619bbf321d),1368553503,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Re-opening to provide less hacky fix.,1368553470,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Merged into master and will go out in wmf4.,1368311679,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Related URL: https://gerrit.wikimedia.org/r/63236 (Gerrit Change I8daae124b060ccf54ce5ca7c1e1a6d18b7265ade),1368225175,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Working on this now.,1366738661,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,"For whatever reason (may be a bug in the DM, or in the seralizer, or in selser), whitespace preservation didn't work in this edit https://en.wikipedia.org/w/index.php?title=International_Air_Transport_Association_airport_code&diff=530666305&oldid=526301045 . The whitespace changes didn't show in the initial diff I was asked to verify, only in the final change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1356989040,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_description,resolved
+VisualEditor: Whitespace preservation for list items not working,*** Bug 48367 has been marked as a duplicate of this bug. ***,1368379914,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,Merged.,1366206699,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,"(In reply to comment #3)
+> Related URL: https://gerrit.wikimedia.org/r/59570 (Gerrit Change
+> Ic4c93510518163894201a693ab50331413715967)
+
+This commit fixes the bug. CC Gabriel and Subbu because they'd probably like to test it.",1366161752,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,Related URL: https://gerrit.wikimedia.org/r/59570 (Gerrit Change Ic4c93510518163894201a693ab50331413715967),1366161678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,"It looks like this is happening because getDomFromData() somehow messes up the whitespace information. Then when getDomFromData() runs a second time (because you go back, change things, then diff again, or if you save after diffing), it sees inconsistent whitespace information and refuses to serialize it.",1366160823,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,"Confirm not happening in live - but /does/ happen with heads of VisualEditor and Parsoid (and MediaWiki) in testing. As Roan says, doesn't appear in diff, does appear in the final change.",1362784369,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: JS TypeError when Parsoid returns an error,"Steps to reproduce issue:
+* Load VisualEditor on a page where the server will return in error
+  (to simulate, call mw.loader.load('ext.visualEditor.viewPageTarget') from the console on a page where VE is not enabled, e.g. the Manual namespace on mw.org)
+* Click Cancel on the server error alert()
+* Witness said error on your console.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355786940,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-i3m3gsgv7zrvvcskhdat,task_description,resolved
+VisualEditor: JS TypeError when Parsoid returns an error,"Now fixed - you get the message: ""Error loading data from server: novenamespace: VisualEditor is not enabled in namespace 100. Would you like to retry?""
+
+Arguably the option to retry should be skipped, but marking this as now fixed.
+
+J.",1364318463,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i3m3gsgv7zrvvcskhdat,task_subcomment,NA
+VisualEditor: JS TypeError when Parsoid returns an error,"**Coiby.Xu** wrote:
+
+I meet this problem, too",1358937264,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-i3m3gsgv7zrvvcskhdat,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**Author:** `swalling`
+
+**Description:**
+On English Wikipedia, we should add a tag (https://www.mediawiki.org/wiki/Manual:Tags) to edits made to articles chosen from Special:GettingStarted by new editors. 
+
+We are logging actions anonymously with EventLogging, but providing a public tag of edits made through this interface has additional advantages:
+
+* It will allow product managers and analysts the ability to see a real time stream of the edits
+* It will help community members inspect the overall stream of edits, and assess them for quality
+* It will explain to anyone who is watching a page how new editors found the article, and why they are editing it
+* It will allow us to find and contact the new editors who use Special:GettingStarted (right now vandals are being warned, but good editors are being ignored for the most part)
+
+If we're adding a tag, we should assume that most community members won't know what Special:GettingStarted is. With that in mind, I propose the following for the tag text: [[Special:Tags|Tag]]: new editor [[Wikipedia:GettingStarted|getting started]]
+
+This is also appropriately agnostic to the task type (copyediting, wikifying, etc.), which is likely to change as the project evolves. You can see other tags in use on English Wikipedia at Special:Tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355729280,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sqgxilqkeecvprvfh7ro,task_description,resolved
+Tag edits made through Special:GettingStarted,https://gerrit.wikimedia.org/r/#/c/42198/ is mostly done.,1357771169,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,The specs for the server-side logging API that Dario hashed out with S and me earlier this morning would totally cover this. I think we can do it. I'll shoot for getting this done in time for the deployment window next Thursday (Jan 10th).,1357164189,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"They're using a totally different VisualEditor-specific API back/middleend, calling the API, then calling ChangeTags::AddTags after the save is done:
+
+https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=blob;f=ApiVisualEditor.php;h=b0fe2048a450cf9ee2e158931a10bf98d8ab5723;hb=refs/heads/master#l220
+
+That approach is not workable for us.  
+
+They also use a hook to list it as an available tag, which we could do:
+
+https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=blob;f=VisualEditor.hooks.php;h=d4660cb0eda0fe54e2ea00905c29182a9d2f4828;hb=refs/heads/master#l53",1355796068,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"(In reply to comment #3)
+> Adding Maxsem as well, since he did this for MobileFrontEnd.
+
+No, what I did was a quick AbuseFilter hack. Look in VE for real solution:)",1355793937,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**tchay** wrote:
+
+Only newly registered users that have been onboarded, but your point is taken.
+
+We could log a different event since logging stores log_page and join against that.",1355791694,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**swalling** wrote:
+
+I'm not sure a time window and tagging of all edits by newly-registered users within the window works. Lots of users edit shortly after account creation, but are not editing one of the articles selected from the list on Special:GettingStarted. We only want edits to those pages, by people who came from the Special page.",1355791571,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**tchay** wrote:
+
+Oops! Adding Andrew Garret.
+
+The code is in ChangTags.php
+
+Possibility?
+
+1. Use the tags interface to create a tag on the getting started event during account creation: say ""onboarded""
+
+2. During an edit save, you check the tags database for the tag for that user
+
+SELECT count(*) from change_tag as ct AND logging as log WHERE ct.ct_log_id=log.log_id AND log.log_type=1 AND ct.tag=""onboarded"" AND log.log_user=$user_id AND (some time window filter?)
+
+3. If this returns anything then you add a (different) tag to the edit tags that allows this to be tracked.",1355790756,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**tchay** wrote:
+
+Possibility?
+
+You use the tags interface to",1355790322,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**swalling** wrote:
+
+Adding Maxsem as well, since he did this for MobileFrontEnd.",1355789222,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**swalling** wrote:
+
+Adding Kaldari, since he has experience adding tags for WikiLove.",1355783504,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"Does anyone know how to pass this along the chain (view->edit->save)?  Ideally, we could use a query string parameter.  There are no useful docs at https://www.mediawiki.org/wiki/Manual:Tags , so we'll have to dig into the code.",1355781256,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+"Inline aliens behaving incorrectly in some cases, seems to depend on selection","Inline image (used as icon) is incorrectly alienated, sometimes (?).
+
+Test case:
+
+Open https://en.wikipedia.org/wiki/User:Raymond/inline_image in VisualEditor mode:
+
+1. Thumbed image and inline image are alienated
+2. Dismiss the notice bubble
+3. Thumbed image is alienated, but inline image is NOT. It is clickable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/inline_image",1355677860,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-xtwsiyvycjjuwkmu2mcm,task_description,resolved
+"Inline aliens behaving incorrectly in some cases, seems to depend on selection","(In reply to comment #2)
+> I'm not able to reproduce it. Please confirm if this still occurs to you -
+> and
+> if o - please provide information about your platform as well. Thanks.
+
+As reporter of this bug I cannot reproduce it now.",1360359290,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-xtwsiyvycjjuwkmu2mcm,task_subcomment,NA
+"Inline aliens behaving incorrectly in some cases, seems to depend on selection",I'm not able to reproduce it. Please confirm if this still occurs to you - and if o - please provide information about your platform as well. Thanks.,1360356597,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-xtwsiyvycjjuwkmu2mcm,task_subcomment,NA
+"Inline aliens behaving incorrectly in some cases, seems to depend on selection","4. Click in the paragraph containing the inline image. It's now behaving correctly again.
+
+
+I've seen this bug with references as well: inline aliens have incorrect hover behavior in some cases, seems to be related to where the selection is.",1355693611,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xtwsiyvycjjuwkmu2mcm,task_subcomment,NA
+VisualEditor: A slug's new contents appear not to get inserted into the DM in at least once case,"* Click into VE on https://en.wikipedia.org/wiki/User:Thehelpfulone/test
+* Click cursor into one of the many LI slugs of the multiply-indented list.
+* Type some contents into the slug
+* Press ""left""; suddenly, the cursor is back at 0,0
+* Click into the ultimate LI with ""real"" content (not the one just created) and outdent repeatedly; you will over-write the new LI as if it wasn't there (indeed, it never reaches the DM).
+
+This may be similar to other slug bugs, given the core issue. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355530440,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czuwyblk43urnavypsbt,task_description,resolved
+VisualEditor: A slug's new contents appear not to get inserted into the DM in at least once case,"(In reply to comment #1)
+> @James: Are you still able to reproduce it?
+
+No; partially invalid because we no longer show lots of distinct slugged LIs for lists. :-)
+
+> Also, I wonder if it is correct behavior that if you have completely empty by
+> multiply-indented list and you press backspace in the deepest li - it delete
+> entire list. Check out this video:
+> https://dl.dropboxusercontent.com/u/1026938/multiplyindented.mov
+
+This feels a bit wrong, yeah; maybe just decrease by one?",1371171784,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czuwyblk43urnavypsbt,task_subcomment,NA
+VisualEditor: A slug's new contents appear not to get inserted into the DM in at least once case,"@James: Are you still able to reproduce it?
+
+Also, I wonder if it is correct behavior that if you have completely empty by multiply-indented list and you press backspace in the deepest li - it delete entire list. Check out this video: https://dl.dropboxusercontent.com/u/1026938/multiplyindented.mov",1371002735,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-czuwyblk43urnavypsbt,task_subcomment,NA
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,"Screenshot showing the diff and the editor
+
+Steps to reproduce problem:
+* Open VisualEditor on https://en.wikipedia.org/wiki/Buri_Ram_Airport
+* The cursor will be on top of the article in a paragraph-placeholder with bold styling (because the first word of the article is bolded)
+* Type ""a""
+
+Expected result:
+The character is inserted. Showing the diff now shows the addition of ""'''a'''"" (either above or below the {{infobox}}, doesn't really matter). Preferably below so that it is next to the paragraph it was added before.
+
+Actual result:
+The character is inserted. Visually nothing else changed (the infobox and the rest of the article are stil there). However, clicking ""Review and save"" now will show a diff where the infobox and the entire article have been removed and ""'''a'''"" was added in its place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9591}",1355443440,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_description,resolved
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,This seems to be fixed already (try to reproduce on English Wikipedia).,1371063948,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_subcomment,NA
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,I think I know what's the reason of this problem. I will work on it next week.,1364152745,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_subcomment,NA
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,*** Bug 46506 has been marked as a duplicate of this bug. ***,1364127463,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_subcomment,NA
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,"This is fundamentally an ""editing what appears to be a blank space but is actually a slug means this behave in a way I did not anticipate"" - assigning to CE, but we really need to talk about this and what we should do longer-term.",1357598884,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_subcomment,NA
+VisualEditor: Slug oddness - new text in list item before alien node is ignored,"Screenshot
+
+Steps to reproduce problem:
+* Open VisualEditor on https://en.wikipedia.org/wiki/Buri_Ram_Airport
+* Put cursor in the placeholder slug in the second list item of the External links. There is an alien node here as the external link is generated with a template.
+* Type ""a""
+* Press ""Review and save""
+
+Expected result:
+A diff adding the letter ""a"".
+
+Actual result:
+Empty diff (see attachment)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9589}",1355442900,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xsynpfa72ixj4q44cgdk,task_description,resolved
+VisualEditor: Slug oddness - new text in list item before alien node is ignored,This seems to be fixed already (try to reproduce on English Wikipedia).,1371067225,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-xsynpfa72ixj4q44cgdk,task_subcomment,NA
+"VisualEditor: ""localStorage is null"" error message","Firefox 17.0.1 and Ubuntu 12.10; using the VE causes a failure with a ""localStorage is null"" error.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355424480,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-zi2tai4mmhmdntkaup52,task_description,invalid
+"VisualEditor: ""localStorage is null"" error message","**orbit** wrote:
+
+We're going to resign (for now at least) from using localStorage for copy and paste. Although I was unable to reproduce this error, we're only using localStorage for copy and paste.",1361832521,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zi2tai4mmhmdntkaup52,task_subcomment,NA
+"VisualEditor: ""localStorage is null"" error message","@James: Yes, it is. I will look into it.",1360357578,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-zi2tai4mmhmdntkaup52,task_subcomment,NA
+"VisualEditor: ""localStorage is null"" error message",Sounds like a CE-issue (for the copy-and-paste code?).,1355508197,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zi2tai4mmhmdntkaup52,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations","Here is normal behavior:
+
+1. In VisualEditor, type a line of text.
+2. Position your cursor at the beginning of that line.
+3. Press the Home key on your keyboard, to move the cursor to the beginning of the line.
+4. Wait a moment.
+5. Press Enter, and the current text is pushed downward one line. This is correct and expected.
+
+Here is the buggy behavior:
+
+1. In VisualEditor, type a line of text.
+2. Position your cursor at the beginning of that line.
+3. VERY QUICKLY, press the Home key followed by the Enter key.
+4. The cursor moves down one line, so it is positioned below the line of text. The text did not move. This is incorrect behavior. The line of text should have been pushed downward.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355422260,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-zvx6cpsh2puavdxxft2q,task_description,resolved
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations","Fixed and will go out with wmf8, from Thursday 20 June.",1371169075,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations",https://gerrit.wikimedia.org/r/68300 (Gerrit Change I35c892581943057acbf9ddd638576e998cc82c1a) | change APPROVED and MERGED [by jenkins-bot],1371169013,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations",Related URL: https://gerrit.wikimedia.org/r/68300 (Gerrit Change I35c892581943057acbf9ddd638576e998cc82c1a),1371076469,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations",I've just created a test that covers this problem: https://github.com/inez/VE-tests/commit/4c1a444b207b37f90dc5d5ce969b5af00ee893ef (solution still not pushed).,1371002298,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations",This issue is not browser specific.,1371000914,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations","Sounds like a polling issue. ""Very quickly"" probably means ""before the polling loop gets a chance to run""; it runs every 200ms.",1355558848,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations","Crap... I made a mistake in my report.
+
+In line (2) of both examples, change ""beginning of the line"" to ""end of the line."" The cursor needs to be at the END of the line.",1355422346,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally","1. Using VisualEditor, edit an article that already has some text in it.
+2. Select all text with Ctrl-A.
+3. Press the DELETE key. All text disappears as expected.
+4. Click ""Review and Save"". The diff shows that text is STILL PRESENT in the article.
+5. Finish saving. You will see that text is still in the article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1355422080,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-i4afw6okkvtcnnnerpcr,task_description,resolved
+"VisualEditor: Select All + Delete removes all text from sight, but not internally",This is now fixed (as of the new deletion code).,1371505460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally","**orbit** wrote:
+
+Reproducible in Firefox.",1356133772,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally","I can reproduce this with backspace too. Does seem to be a CE issue, because the linear model isn't emptied (it could also have been a selser issue).",1355693980,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally","More widely, it looks like the CE layer doesn't bind to delete the way it does to backspace; assigning.",1355429997,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally",The problem also occurs if you highlight all the article text with your mouse and press DEL.,1355423978,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+VisualEditor: Some elements not alienated,"The coord template is not hatched but still visible and the links are still clickable.
+
+https://en.wikipedia.org/wiki/User:Raymond/coords
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1355413560,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-bhfeaa4hp3iuxtp7inrp,task_description,resolved
+VisualEditor: Some elements not alienated,This (first part; second part is now bug 43155) is fixed in gerrit 39834 which is now merged; will be deployed as part of the 2013-01-16 release cycle.,1357678877,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bhfeaa4hp3iuxtp7inrp,task_subcomment,NA
+VisualEditor: Some elements not alienated,"(In reply to comment #0)
+> The coord template is not hatched but still visible and the links are still
+> clickable.
+> 
+> https://en.wikipedia.org/wiki/User:Raymond/coords
+
+Inspecting it shows that this is being alienated correctly, but for some reason it's not getting hatched out and not behaving quite correctly. That's a CE bug.
+
+Inspecting the coords element shows:
+
+<div contenteditable=""false"" class=""ve-ce-leafNode ve-ce-alienNode ve-ce-alienInlineNode""><span typeof=""mw:Object/Template "" about=""#mwt1"" ...>[lots of scary stuff here, including nested <span>s]</span></div>
+
+
+(In reply to comment #1)
+> There are a few templates that aren't hatched. For example, the tables
+> created
+> by [[w:en:Template:Canadian_first_minister_list]] are editable with
+> VisualEditor, and trying to do so results in a mess of wikitext.
+This is actually a different bug. Tables of Canadian prime ministers aren't alienated at all due to a bug in Parsoid, while on Raymond's coords page the template is alienated correctly but the alien itself is misbehaving. Keeping this bug for the coords bug, splitting off the Canadian prime ministers bug to bug 43155.",1355560412,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bhfeaa4hp3iuxtp7inrp,task_subcomment,NA
+VisualEditor: Some elements not alienated,"**jnichols** wrote:
+
+There are a few templates that aren't hatched. For example, the tables created by [[w:en:Template:Canadian_first_minister_list]] are editable with VisualEditor, and trying to do so results in a mess of wikitext.",1355426222,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bhfeaa4hp3iuxtp7inrp,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'left'  / call method 'getOuterLength'.""","A couple more uncaught TypeError, a la https://bugzilla.wikimedia.org/show_bug.cgi?id=43014:
+
+Uncaught TypeError: Cannot read property 'left' of undefined
+
+Uncaught TypeError: Cannot call method 'getOuterLength' of undefined
+
+Reported http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Error_loading_data_from_server:_Server_error
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355346720,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-alx56wytsjcuj4hvxv6h,task_description,invalid
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'left'  / call method 'getOuterLength'.""","Cannot reproduce this without a deep stack trace; also, this is from three months ago, and we're unlikely to still have the same issue.",1364318251,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-alx56wytsjcuj4hvxv6h,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'left'  / call method 'getOuterLength'.""","Given errors sounds like a selection issue; assigning to CE, but please advise if not.",1355429701,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-alx56wytsjcuj4hvxv6h,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Example Page: http://en.wikipedia.org/wiki/Ansaldo_Poggi
+
+1. Go to the top, click into the empty line above the ineditable image (the normally right floating image). This empty line should not exist. It can however, be deleted (press ""delete"" on the keyboard) which causes the start text to jump in front of the ""Modern Bolognese Violin-Making Table"" image.
+
+2. Click somewhere inside ""References"". Move the cursor with the keyboard  to the position after the ""s"". Press ""delete"" on the keyboard. The line starting with ""Tito Gotti"" will be merged with the heading (ignoring the uneditable ""references"" tag and ""cite"" template).
+
+3. Similar to the above: Click somewhere inside ""References"". Move the cursor with the keyboard  to the position after the ""s"". Move one more right into the (errorneously existing) empty line between the heading and the uneditable references tag. Press ""delete"" on the keyboard. The line starting with ""Tito Gotti"" will jump above the uneditable ""references"" tag and ""cite"" template.
+
+4. Do the same as above, i.e. go to the empty line after the References-Heading. However, this time click with the mouse into the line. Press ""delete"" on the keyboard. This time the behavior is different, nothing is deleted and the cursor jumps to the start of the article. This in itself seems again to be an error in the ordering of page objects. Now try to repeat this with different browser windows screen or zoom sizes, so that the originally, the start of the article is not visible before clicking delete. It can be seen that the focus is not updated, the cursor is outside of the visible area. Press ""delete"" again and with seeing it, parts of the text can be deleted.
+
+5. Do the same as above, click on line below reference with the mouse, delete once, cursor jumps to top. Do not delete again, but put the cursor again into the line below the reference heading with the mouse. This time the ineditable <references> tag is deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355334540,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-qr4la5fjep3uvnewafhr,task_description,resolved
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),These are all moot since the redesign of slugs over a year ago.,1420844082,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Would having an object inspector on the non-editable non-text things that provides options to ""insert text before""/""insert text after"" be a solution to the problem?",1360616789,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Created attachment 11767
+Mockup of VisualEditor in various modes
+
+Just wanted to note that slugs were an experimental solution to the problem of ""how do you allow users to insert content between non-text things?
+
+We have had a lot of ideas, but so far the direction we intend to go is to remove them entirely from the existing ""layout"" mode and provide an ""outline"" mode to the editor which includes them. There could also be a ""source"" mode where we could integrate the markup editing experience directly into VisualEditor.
+
+**Attached**: {F10138}",1360609163,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Gladly: Windows 7, continuous updates, Google Chrome, Version 23.0.1271.95 m",1355343138,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Thank you for the bug report.  Though I am unable to reproduce the first step in Firefox or Chrome.  To help with debugging, would you please include your browser information?",1355341412,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"According to <https://test.wikipedia.org/wiki/Special:Version>, the VisualEditor extension is installed, but it doesn't seem to be enabled. I think VisualEditor should be enabled for all namespaces, all skins, all users, etc. on test.wikipedia.org.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1355330700,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3qimgh7ycaviacztiyae,task_description,resolved
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,This is now deployed. Marking as fixed.,1367270827,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"(In reply to comment #9)
+> Yeah; it would be helpful if gerrit changes which mentioned bugs were either
+> always or never proxied by the bot to bugzilla, instead of the half-way house
+> of being unknown. :-)
+
+Feel free to file a new ticket with reference to bug 17322. :)",1367251782,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"Yeah; it would be helpful if gerrit changes which mentioned bugs were either always or never proxied by the bot to bugzilla, instead of the half-way house of being unknown. :-)
+
+Apologies, all!
+
+J.",1367250758,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"(In reply to comment #7)
+> Related URL: https://gerrit.wikimedia.org/r/61382 (Gerrit Change
+> I56906c123e924b84eb9ee076cd67254f8935911d)
+
+Result of a typo. ^",1367249638,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,Related URL: https://gerrit.wikimedia.org/r/61382 (Gerrit Change I56906c123e924b84eb9ee076cd67254f8935911d),1367247867,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"(In reply to comment #5)
+> Related URL: https://gerrit.wikimedia.org/r/61250 (Gerrit Change
+> I98028df0bcb621e8f13a2f8ab130e86a9010ebeb)
+This change enables VisualEditor on test2wiki, and will be deployed on Monday.
+
+I fixed the namespace configuration last week, it's now the same on all wikis: VisualEditor is enabled in the main and user namespaces, as well as the VisualEditor namespace where it exists (testwiki and mediawikiwiki have this namespace for historical reasons).",1367130629,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,Related URL: https://gerrit.wikimedia.org/r/61250 (Gerrit Change I98028df0bcb621e8f13a2f8ab130e86a9010ebeb),1367130305,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"http://test.wikipedia.org/wiki/Special:Preferences#mw-prefsection-editing allows to ""Enable VisualEditor (only in the main and user namespaces)""
+http://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-editing does not offer enabling VisualEditor.
+
+Roan: As this is assigned to you, do you plan to work on this and is this high priority? If not, please reset. Thanks.",1366908803,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"I can see ""Enable VisualEditor"" checkbox at en.wikipedia.org[1] but not at test2.wikipedia.org[2].
+
+[1] http://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-editing
+[2] http://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-editing",1355926606,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,I believe Roan will be doing this later today.,1355343355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,Apparently there's interest in having VisualEditor enabled on test2.wikipedia.org as well (cf. <http://lists.wikimedia.org/pipermail/wikitech-l/2012-December/065034.html>).,1355341331,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"When I go to <https://en.wikipedia.org/wiki/User:Trevor_Parscal> and click the ""visualeditor"" tab, my browser console says:
+
+---
+The page at https://en.wikipedia.org/wiki/User:Trevor_Parscal displayed insecure content from http://en.wikipedia.org/w?title=Special:FilePath/California_Bay_Area_county_map.svg&width=.
+---
+
+Consequently, the pretty green lock icon in Google Chrome turns yellow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1355327160,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_description,resolved
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934071,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),https://gerrit.wikimedia.org/r/70344 (Gerrit Change I253b9b7a9b463439e86d7cf7975cd92f9c851e70) | change APPROVED and MERGED [by jenkins-bot],1372119634,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),The fix will go out with tomorrow's Parsoid deployment.,1372119634,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),https://gerrit.wikimedia.org/r/70348 (Gerrit Change Ied95c87fda13dbea2b8c46ad1e96fde1c50c1517) | change APPROVED and MERGED [by jenkins-bot],1372119224,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Related URL: https://gerrit.wikimedia.org/r/70348 (Gerrit Change Ied95c87fda13dbea2b8c46ad1e96fde1c50c1517),1372117100,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Related URL: https://gerrit.wikimedia.org/r/70344 (Gerrit Change I253b9b7a9b463439e86d7cf7975cd92f9c851e70),1372115462,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),*** Bug 49984 has been marked as a duplicate of this bug. ***,1371855005,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"We used to use a special page redirect hack, but now use the API to properly retrieve image information including the path. So the new code needs to implement some similar protocol-relative massaging for image URLs, at least for the domains we know to support both http and https.",1371603843,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"Per Roan's comments, moving to Parsoid so they can fix.",1371603429,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"(In reply to comment #7)
+> This seems to have been unfixed in production.
+> 
+Specifically, Parsoid is now once again returning http:// URLs for images (except in labs, where it returns https:// URLs). MZ submitted a fix in December to make these URLs protocol-relative, but this seems to have been unfixed somehow.
+
+Perhaps the repository URL is being grabbed from the API? That would explain why it's now a fully qualified URL, and it might explain the difference between labs and production.",1371603136,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"This seems to have been unfixed in production.
+
+Strangely, parsoid.wmflabs.org is now giving me https URLs for images.",1371583342,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),*** Bug 49283 has been marked as a duplicate of this bug. ***,1371576350,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),The page at https://en.wikipedia.org/wiki/User:Trevor_Parscal?veaction=edit displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/f/ff/California_Bay_Area_county_map.svg/38px-California_Bay_Area_county_map.svg.png.,1371574794,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"I am getting this issue, on the test page referenced in the bug and others, again. The URLs do not contain Special:FilePath anymore, so perhaps something was changed about  how images are handled that introduced a regression? Reopening this bug since the issue appears to be essentially the same.",1371531045,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Tagging with deploy-train cycle.,1357578934,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Fixed by <https://gerrit.wikimedia.org/r/38673>.,1355449078,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Upstream Parsoid bug: bug 42976,1355339026,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","[Wikitech-l] Alpha version of the VisualEditor now available on the English Wikipedia
+
+I tried it on enwiki in my sandbox. 
+
+It does not work: when I want to ""Review and save"" a box pops up ""Review your changes"" --- but nothing happens.
+
+* MediaWiki 	1.21wmf5 (f4a44f9)
+* VisualEditor (Version 0.1.0) 	(2e6425a)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355299800,PHID-USER-ppvnwr24o32pux3le5ov,PHID-TASK-vhisdvekk4sgvgkkuben,task_description,resolved
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","For completeness: This was fixed in https://gerrit.wikimedia.org/r/38382, because I broke new page creation in the Selective Serializer by not properly handling the error that was raised on not finding page content. Sorry about that folks, there was some turbulence, but we're looking to arrive at our destination ahead of schedule.",1355515620,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","Just a note: this affected all page creations, not just subpages. The selective serializer mode did not deal properly with the fetch failure for the original (non-existing) page source.",1355436359,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them",Happy to help. :-),1355436247,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","@James Yes I confirm that it now works for me on my subpage ! Well and quickly fixed.
+
+:-)",1355434816,PHID-USER-ppvnwr24o32pux3le5ov,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","This appears to now be fixed, following an update to the Parsoid service yesterday; I can now edit and create articles with ""/""s in their title. Closing as fixed.",1355429392,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","There are going to be lots of things that are broken... that's why it's an experimental alpha release. It works on lots of pages but it still doesn't on lots of others. Personally I'd say the hype is valid but so are the huge cautions of how many things don't work :). 
+
+Roan et.al: After some quick experimentation this looks like a possible issues with sub pages in general. The 'hang and not do anything' error that Wikinaut is talking about happens when you're trying to create the subpage (Also experienced it trying to create a subpage in mainspace with the VE). If you try to edit a subpage with VE after it already existed (was created with normal editor) then you get a pop up warning ""Error loading data from server: Server error. Would you like to retry?"". Trying a couple times on a couple different pages the situation appears to be the same each time.
+
+Tested pages:
+
+User:Jalexander/sandbox
+Wikipedia/History?redirect=no
+User:Wikinaut/sandbox
+Wikipedia/test
+
+I can do screenshots if you need them easily.",1355357679,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","Big hype about non working VE...
+
+this page does not work with VE https://en.wikipedia.org/wiki/User:Wikinaut/sandbox",1355355946,PHID-USER-ppvnwr24o32pux3le5ov,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","(In reply to comment #6)
+> VE alpha == not mature yet
+That's what we've been telling everyone all along. There's a reason we called it an alpha release ;)
+
+Could you link to the page that was failing for you?",1355338217,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","I tried other pages, saw different page formatting when using template {{ok}}  and got immediately 
+
++ ""Error loading data from server: Unsuccessful request: Error contacting the Parsoid server""
+
+when trying to edit and ""Review and save""
+
+VE alpha == not mature yet",1355309356,PHID-USER-ppvnwr24o32pux3le5ov,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","@James
+
++ works on my User page
++ does not work on User:username/Sandbox page (personal link portlet ""Sandbox"")
+
+I modified the bug title.",1355302660,PHID-USER-ppvnwr24o32pux3le5ov,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","Not totally sure what's up with the Firefox piece other then see if you can try again a couple minutes later or another page (though your sandbox shouldn't be a problem) so I'll leave that for JamesF and the VE crew ;). 
+
+For IE 8, however, it's likely because VE isn't supported in IE8 yet ( per https://en.wikipedia.org/wiki/Wikipedia:VisualEditor#Current_limitations Chrome/Firefox/Safari only). If I remember correctly it's because it actually needs a fair bit of refactoring specifically for IE (and possibly only 9 and 10 and never 8) because it handles things totally differently.",1355301776,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","IE8 shows errors
+Details zum Fehler auf der Webseite
+
+Benutzer-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C)
+Zeitstempel: Wed, 12 Dec 2012 08:18:19 UTC
+
+
+Meldung: Bezeichner, Zeichenfolge oder Zahl erwartet
+Zeile: 5
+Zeichen: 746
+Code: 0
+URI: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Cjquery.multiSuggest%7Crangy&skin=vector&version=20121212T032708Z&*",1355300330,PHID-USER-ppvnwr24o32pux3le5ov,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them",http://i.imgur.com/gsL16.png,1355300009,PHID-USER-ppvnwr24o32pux3le5ov,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them",* Firefox 17.0.1,1355299935,PHID-USER-ppvnwr24o32pux3le5ov,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+VisualEditor: Removing copy/pasted link annotations removes the original as well,"1. Add a link to some text
+2. Copy the text
+3. Paste the text somewhere else
+4. Remove the link using the link inspector's trash icon
+5. See that both links are gone
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1355191860,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-rifozrrb2mk5wki2qrw4,task_description,resolved
+VisualEditor: Removing copy/pasted link annotations removes the original as well,Now landed in master.,1355193795,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rifozrrb2mk5wki2qrw4,task_subcomment,NA
+VisualEditor: Removing copy/pasted link annotations removes the original as well,Fixed in gerrit 38009.,1355192089,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rifozrrb2mk5wki2qrw4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,"**Author:** `orbit`
+
+**Description:**
+Steps to reproduce:
+1. Copy part of a headline and part of a following paragraph
+2. Paste into a paragrah
+
+The linmod being inserted will look something like this:
+[""s"", ""u"", ""m"", ""?"", Object, Object, ""C"", ""o"", ""n"", ""t""]
+
+The objects are closing heading and opening paragraph.
+
+The error is in ve.dm.Document.js on 1145.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354837920,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-upsvylaxm2favfgmiub4,task_description,resolved
+VisualEditor: Type mismatch when inserting unbalanced content,Now merged into master.,1354916275,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,Id9269a29e51ca213508de8f155d3feec5e5b0774 should resolve this,1354907772,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,I believe Trevor meant ab</p></li></ol><p>cd breaking.,1354904980,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,"**orbit** wrote:
+
+ab</p></li><p>cd is invalid markup anyway.",1354903732,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,"I0d2b593e05ebdee807e2cc6eeb902d542db3895f is a start, but there's still some issues.
+
+Given the target: <p>12[cursor]34</p>
+
+OK: ab</p><p>cd
+OK: ab</h2><p>cd
+BAD: ab</p></li><p>cd",1354843715,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,Now being done by Trevor; reassigning.,1354841984,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Deleting across inline alien errors,"**Author:** `orbit`
+
+**Description:**
+Try creating ""some text <inlinealien>blah</inlinealien> more text"" and select across the inline alien and delete. 
+
+Uncaught TypeError: Cannot call method 'getDataFromNode' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354669260,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3mbtnybtpij42l625lvd,task_description,resolved
+VisualEditor: Deleting across inline alien errors,Fix in gerrit 37056.,1354738462,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3mbtnybtpij42l625lvd,task_subcomment,NA
+VisualEditor: Deleting across inline alien errors,"Argh. I figured out why this happens.
+
+* .splice() is called on the dm.ParagraphNode to remove the alien
+* which calls .adjustLength() on the dm.ParagraphNode
+* which emits an update event on the dm.ParagraphNode
+* which causes .renderContents() to be called on the ce.ParagraphNode
+* which attempts to rerender its ce.TextNode children
+* one of which is now associated with a detached dm.TextNode
+* which means it crashed when trying to get the data from the linear model
+
+I'm not entirely sure what the solution should be. Perhaps ce.ContentBranchNode shouldn't rerender for an update on the node itself, only on its children?",1354733644,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3mbtnybtpij42l625lvd,task_subcomment,NA
+VisualEditor: Backspace over a slug at the end of the document throws an error,"Pressing backspace in a slug at the end of the document throws an error:
+
+* Create a new page (or go to an existing one), and enter ""ABCD\n"" at the end
+* With the cursor in the new slug, press backspace; this throws an error:
+
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 9 is out of bounds
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1354563780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bsg3qk2puigbios7b56m,task_description,resolved
+VisualEditor: Backspace over a slug at the end of the document throws an error,Fixed here: https://gerrit.wikimedia.org/r/#/c/37162/,1354755508,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-bsg3qk2puigbios7b56m,task_subcomment,NA
+VisualEditor: Link inspector doesn't close when moving cursor to a different link,"Inspect a link, then click on a different link, the inspector moves to the new cursor location and remains open.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354217520,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-mutotkwptjvzfn2nuk4y,task_description,resolved
+VisualEditor: Link inspector doesn't close when moving cursor to a different link,"Resolved in I859123a5fcd36bc2afb2e578f81f30a944c8583a
+
+This bug was introduced somewhere in the recent context rewrite.",1354227540,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-mutotkwptjvzfn2nuk4y,task_subcomment,NA
+VisualEditor: Save dialog triggers error (selection bug?),"On launching the save dialog, a console error is thrown:
+
+Uncaught TypeError: Cannot read property 'nodeType' of null /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:117
+ve.ce.getOffset /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:117
+ve.ce.SurfaceObserver.poll /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:136
+ve.ce.SurfaceObserver.stop /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:82
+ve.ce.Surface.documentOnBlur /w/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js:324
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354155360,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bp5lorruinm7xnzv76mb,task_description,resolved
+VisualEditor: Save dialog triggers error (selection bug?),"
+
+*** This bug has been marked as a duplicate of bug 41504 ***",1354155569,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-bp5lorruinm7xnzv76mb,task_subcomment,NA
+VisualEditor: Integrate edit conflict confirmation into the save dialog,"As of I002c5aa23704c1c46ef46fa1970a4254614b9eb1 when saving and an edit conflict occurs the user is shown a browser-provided confirmation box which allows them to either cancel or resolve the conflict manually.
+
+It would be much better if this was integrated into the save dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1354147200,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-2iww52jmzvuwmwgsjy5e,task_description,resolved
+VisualEditor: Integrate edit conflict confirmation into the save dialog,Merged into master and will go out with wmf5.,1368574606,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2iww52jmzvuwmwgsjy5e,task_subcomment,NA
+VisualEditor: Integrate edit conflict confirmation into the save dialog,Related URL: https://gerrit.wikimedia.org/r/63679 (Gerrit Change I709d936d998b130515b62de880c6e7aa7978786b),1368550555,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2iww52jmzvuwmwgsjy5e,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"It isn't just that this would throw an exception:
+
+ new mw.Uri('http://krinkle.dev/mediawiki/alpha/index.php?title=VisualEditor:S@box&action=edit');
+
+Although that is also bad (when done on non-@ pages), it is especially bad that on pages containing an @ in the url, the module won't even finish loading because of this line:
+
+ defaultUri = new Uri( documentLocation );
+
+So instead, mw.Uri stays undefined.
+
+--------------------------
+**Version**: 1.19
+**Severity**: critical",1354127040,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vrsv454ata26ui2zocei,task_description,resolved
+mediawiki.Uri crashes in pages with '@' in their url,"I know mine doesn't work, because I put it together in five minutes, but it's definitely proper. Here's the code I used to construct it: http://pastebin.com/ELJ4LdKy",1358706140,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"Tyler, this looks way too short on the first glance and doesn't work. It also explicitly doesn't support protocol-relative URIs.
+
+Here's one that works (this is used by Ruby's URI parsing library). Of course it's not hardcoded in the code like this, but constructed on the fly from regexes for specific URI parts. I could port this to JS in a reasonable way, if anybody except for me actually wants this.
+
+/^(?:[a-zA-Z][\-+.a-zA-Z\d]*:(?:(?:\/\/(?:(?:(?:[\-_.!~*'()a-zA-Z\d;:&=+$,]|%[a-fA-F\d]{2})*@)?(?:(?:[a-zA-Z0-9\-.]|%\h\h)+|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}|\[(?:(?:[a-fA-F\d]{1,4}:)*(?:[a-fA-F\d]{1,4}|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})|(?:(?:[a-fA-F\d]{1,4}:)*[a-fA-F\d]{1,4})?::(?:(?:[a-fA-F\d]{1,4}:)*(?:[a-fA-F\d]{1,4}|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}))?)\])(?::\d*)?|(?:[\-_.!~*'()a-zA-Z\d$,;:@&=+]|%[a-fA-F\d]{2})+)(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*)?|\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*)(?:\?(?:(?:[\-_.!~*'()a-zA-Z\d;\/?:@&=+$,\[\]]|%[a-fA-F\d]{2})*))?|(?:[\-_.!~*'()a-zA-Z\d;?:@&=+$,]|%[a-fA-F\d]{2})(?:[\-_.!~*'()a-zA-Z\d;\/?:@&=+$,\[\]]|%[a-fA-F\d]{2})*)|(?:\/\/(?:(?:(?:[\-_.!~*'()a-zA-Z\d;:&=+$,]|%[a-fA-F\d]{2})*@)?(?:(?:[a-zA-Z0-9\-.]|%\h\h)+|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}|\[(?:(?:[a-fA-F\d]{1,4}:)*(?:[a-fA-F\d]{1,4}|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})|(?:(?:[a-fA-F\d]{1,4}:)*[a-fA-F\d]{1,4})?::(?:(?:[a-fA-F\d]{1,4}:)*(?:[a-fA-F\d]{1,4}|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}))?)\])(?::\d*)?|(?:[\-_.!~*'()a-zA-Z\d$,;:@&=+]|%[a-fA-F\d]{2})+)(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*)?|\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*|(?:[\-_.!~*'()a-zA-Z\d;@&=+$,]|%[a-fA-F\d]{2})+(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*)?)(?:\?(?:[\-_.!~*'()a-zA-Z\d;\/?:@&=+$,\[\]]|%[a-fA-F\d]{2})*)?)?(?:#(?:[\-_.!~*'()a-zA-Z\d;\/?:@&=+$,\[\]]|%[a-fA-F\d]{2})*)?$/",1358688372,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"BTW, for whoever's curious, here is what an official URI regular expression would look like (it does't work, needs debugging; it's probably missing a parentheses or something):
+
+/^[A-Za-z][A-Za-z0-9\+\-\.]*:(\/\/(([:A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2})@)?(\[(|v[A-Fa-f]+\.[:A-Z0-9-\._~!\$&'\(\)\*\+,;=]+)\]|([0-9]|[1-9][0-9]|2[0-4][0-9]|25[0-5])\.([0-9]|[1-9][0-9]|2[0-4][0-9]|25[0-5])\.([0-9]|[1-9][0-9]|2[0-4][0-9]|25[0-5])\.([0-9]|[1-9][0-9]|2[0-4][0-9]|25[0-5])|([A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))(:[0-9]*)?(\/(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))*)*|\/(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))+(\/(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))*)*|(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))+(\/(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))*)*|)\?((([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2})|[\/\?])*)?(#(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2})|[\/\?])*)?$/",1358636139,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,Change-Id: I4954bfd3750d5c990e91cc0dc8a175225ccbad1e,1358621587,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"Yes, but is it truly necessary to validate that much? I mean, for example, take the (invalid) URI ""https://www.google.com/search?q=test test"". The URI is invalid because it has a space character in the query, but if you were to do something like ""location.href = <that uri>"", it would work perfectly fine, because the browser automatically percent-encodes the space.
+
+Basically, I'm wondering for what the mw.Uri class is being used for that requires such strict validation.",1358556627,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #10)
+> I wouldn't attempt to make a comprehensive URI parsing library in JavaScript.
+
+> The first reason is because it's unnecessary. With the fix I just uploaded to
+> Gerrit, there should not be any more bugs in this function. 
+
+I just pointed out a glaring one above.
+
+(In reply to comment #8)
+> What about whitespace in the authority part? (This isn't allowed,
+> but those regexes match it just fine.)
+
+I'm sure there are more, waiting to be uncovered.
+
+
+> Secondly, the
+> regular expression would be absurdly complicated. URIs have specific sets of
+> characters that can be included only in certain sections. I wrote a regex for
+> an official URI once when I was working on the PHP version of this class
+> (still
+> in Gerrit), and it was so confusing it took days to get it working properly.
+
+Of course, I know this. That's why I'm suggesting using the work of someone who has already spent time pulling his hair out to get this right; or at least just taking those crazy regexes in from some other library.",1358549728,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"I wouldn't attempt to make a comprehensive URI parsing library in JavaScript. The first reason is because it's unnecessary. With the fix I just uploaded to Gerrit, there should not be any more bugs in this function. Secondly, the regular expression would be absurdly complicated. URIs have specific sets of characters that can be included only in certain sections. I wrote a regex for an official URI once when I was working on the PHP version of this class (still in Gerrit), and it was so confusing it took days to get it working properly.",1358545565,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #8)
+> (In reply to comment #6)
+> > On further investigation and following links from that gist, it looks like
+> > the
+> > regexes in mw.Uri aren't so half-baked.
+> > 
+> > They actually come from here:
+> > http://blog.stevenlevithan.com/archives/parseuri
+> 
+> If they weren't half-baked, mw.Uri wouldn't crash on '@' in the URL. 
+> 
+> These regexes are already awful (177 characters? Seriously?), and are bound
+> to
+> get worse as we discover more edge-cases. 
+> 
+> What about password with a '@' in it? (Yeah, this is allowed as far as I
+> know,
+
+No, those need to be url escaped afaik. At least in Chrome and in the nodejs modules I used it the password (especially the @ symbol) needs to be url escaped or it won't work.
+
+> While on second though the <a>-abuse I linked isn't a good idea, we really
+> need a serious parsing library.
+
+I'm open to suggestions, though it'll need to be flexible and be replaceable in-place to allow smooth transition (same API and and unit tests, different internal implementation).
+
+The module is generic enough to easily allow a different parser.
+
+But there is some ambiguity on the fields to be extracted and their meaning[1], so even a ""perfect"" library may need modification to work for us and our interpretation of those terms.
+
+[1] http://tantek.com/2011/238/b1/many-ways-slice-url-name-pieces",1358542770,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #6)
+> On further investigation and following links from that gist, it looks like
+> the
+> regexes in mw.Uri aren't so half-baked.
+> 
+> They actually come from here:
+> http://blog.stevenlevithan.com/archives/parseuri
+
+If they weren't half-baked, mw.Uri wouldn't crash on '@' in the URL. 
+
+These regexes are already awful (177 characters? Seriously?), and are bound to get worse as we discover more edge-cases. 
+
+What about password with a '@' in it? (Yeah, this is allowed as far as I know, and works.) What about whitespace in the authority part? (This isn't allowed, but those regexes match it just fine.)
+
+While on second though the <a>-abuse I linked isn't a good idea, we really need a serious parsing library.",1358532368,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #6)
+> (In reply to comment #3)
+> > I googled a little for a reasonable JS URI parsing library that could replace
+> > those half-baked regexes, and found this: https://gist.github.com/2428561
+> > 
+> > It seems genius and is 100% correct. Is it a good idea to use something like
+> > this? If it is, I can implement it.
+> 
+> That's not a URI parsing library, that's an unreliable hack using <a href="""">
+> parsing. See the comments there.
+> 
+> On further investigation and following links from that gist, it looks like
+> the
+> regexes in mw.Uri aren't so half-baked.
+> 
+> They actually come from here:
+> http://blog.stevenlevithan.com/archives/parseuri
+
+Indeed. You'll also notice that the user and password aren't parsed at all in that implementation.
+
+Also, https://gerrit.wikimedia.org/r/44665",1358531480,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #3)
+> I googled a little for a reasonable JS URI parsing library that could replace
+> those half-baked regexes, and found this: https://gist.github.com/2428561
+> 
+> It seems genius and is 100% correct. Is it a good idea to use something like
+> this? If it is, I can implement it.
+
+That's not a URI parsing library, that's an unreliable hack using <a href=""""> parsing. See the comments there.
+
+On further investigation and following links from that gist, it looks like the regexes in mw.Uri aren't so half-baked.
+
+They actually come from here:
+http://blog.stevenlevithan.com/archives/parseuri",1358530663,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,Found the problem. Expect a patch in the near future.,1358530566,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,It should be noted that those are HTML5-specific properties.,1358529061,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"I googled a little for a reasonable JS URI parsing library that could replace those half-baked regexes, and found this: https://gist.github.com/2428561
+
+It seems genius and is 100% correct. Is it a good idea to use something like this? If it is, I can implement it.",1355779261,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"Not yet, but if nobody does I will eventually.",1355764277,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"Krinkle: As dependency bug 42306 is assigned to, do you work on this?",1355708459,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,"Wikitext to reproduce:
+
+<span>
+[bunch of newlines]
+</span>
+
+Parsoid generates <span><p></p></span> for this, but it doesn't mark the span.
+
+Todo:
+* Make the failure a bit more graceful
+* Investigate whether p inside span is legal
+* Investigate other cases where this breakage occurs
+* File bug with Parsoid for proper protection of user-generated tags
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354071720,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_description,resolved
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,Resolved in If420ae80ab0777424a9a5517335ef9d0170e87ae,1354826179,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_subcomment,NA
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,"Slight tweak to the approach: it was easier not to back up to the outer node, but instead just inline-alienate the inner node.
+
+https://gerrit.wikimedia.org/r/37172",1354756947,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_subcomment,NA
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,"(In reply to comment #1)
+> This content would be in violation of the HTML spec, I believe.
+Yes. But Gabriel argues this is bound to occur in some cases anyway.
+
+Proposed approach: detect these cases (block node inside inline node or annotation node) without crashing, and handle them by backing out and alienating the outer node.",1354146377,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_subcomment,NA
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,"This content would be in violation of the HTML spec, I believe.",1354124174,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_subcomment,NA
+VisualEditor: Still get a pawn when select-all->replace in Firefox,"Go to demos/ve/?page=aliens in Firefox; select all:
+
+  TypeError: end is undefined    ve.ce.Surface.js (line 980)
+
+Press ""a"" (or backspace and then ""a""):
+
+  TypeError: start is undefined  ve.ce.Surface.js (line 995)
+  
+  (And a pawn appears in its own <p> above the a.)
+
+On any click thereafter,
+
+  TypeError: node is null        ve.ce.Surface.js (line 1073)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57355",1353725160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j3shvug7fft7t4wshe6d,task_description,resolved
+VisualEditor: Still get a pawn when select-all->replace in Firefox,"I resolved this in Ia7347527e6466262e819f456404b32926fd95e34 by correcting the offsets before showing selection. This seems to work well so far, but really getNodeAndOffset is a nasty function that needs some love soon.",1353971144,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-j3shvug7fft7t4wshe6d,task_subcomment,NA
+"VisualEditor: Selective serialisation has landed in Parsoid, now VE needs to handle that","Due to gerrit 31118 being merged, Parsoid now has selective serialisation live. This means that VisualEditor needs to include Mark's patch to handle this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1353721680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hgicqduvx6exq6mle75r,task_description,resolved
+"VisualEditor: Selective serialisation has landed in Parsoid, now VE needs to handle that",gerrit 35340,1353981072,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hgicqduvx6exq6mle75r,task_subcomment,NA
+VisualEditor: Failure in saving integration code,"this.emit( 'saveError', null, 'Unsuccessful request: ' + data.result, null );
+
+(ve.init.mw.Target.js line 131)
+
+causes ""TypeError: data is undefined""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353719400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-76qxn5mqf3hcvdkgf2kt,task_description,resolved
+VisualEditor: Failure in saving integration code,Fixed in gerrit 34959,1353724364,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-76qxn5mqf3hcvdkgf2kt,task_subcomment,NA
+VisualEditor: Clean up meta nodes,"For after December:
+* consolidate 'type': 'metaInline' / 'metaBlock' into 'type': 'meta'
+* get rid of ve.{ce,dm}.Meta{Inline,Block}Node
+* create ve.dm.MetaNode with converter stuff but don't inherit ve.dm.LeafNode
+** eventually integrate that into the new node API
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353702180,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-o3u5ojlmiw3bdf7dgyiu,task_description,resolved
+VisualEditor: Clean up meta nodes,This is fixed in gerrit 39847 which is now merged; will be deployed as part of the 2013-01-16 release cycle.,1357679596,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o3u5ojlmiw3bdf7dgyiu,task_subcomment,NA
+VisualEditor: Clean up meta nodes,"Turns out this could only be fixed partially. Consolidating metaBlock and metaInline was not possible and will have to wait until the node API rewrite, so I removed ce.Meta{Block,Inline}Node in https://gerrit.wikimedia.org/r/39847 and wrote up some ideas for the node API rewrite at https://www.mediawiki.org/wiki/User:Catrope/Node_API",1356175301,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-o3u5ojlmiw3bdf7dgyiu,task_subcomment,NA
+VisualEditor: Delete and backspace broken around inline aliens in Firefox,"When I place the cursor before the template output, and press ""Delete"", it deletes the template and one more character after the template. When I place the cursor after the template output and press ""Backspace"", it does not delete the template (simply does nothing).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353576600,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-75uqqg6zbs3w4jxdyn43,task_description,resolved
+VisualEditor: Delete and backspace broken around inline aliens in Firefox,Resolved in I73215df88519450965be35d9e04cf4e621d1e90d,1354149956,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-75uqqg6zbs3w4jxdyn43,task_subcomment,NA
+VisualEditor: Delete and backspace broken around inline aliens in Firefox,"Confirmed.
+
+Trivial test case: Start with an article with an inline alien - e.g. ""ABC<tt>:-)</tt>DEF"". Place the cursor immediately after C, and press (forwards) delete; instead of just deleting the alien, it also deletes D.
+
+Undo; place cursor immediately before D (just after the alien), and press backspace; instead of deleting the alien, it does nothing.
+
+Confirmed in Firefox.",1353718829,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-75uqqg6zbs3w4jxdyn43,task_subcomment,NA
+"VisualEditor: Link inspector suggestions box should instantly show, then populate with more as API returns","Right now the link inspector's suggestions box displays only after the ; instead, it should show instantly, then populate with more data as API returns with a spinner. Trevor has some ideas if you want to bug him. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353543420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-smsvykwx7lxu2tyag7ye,task_description,resolved
+"VisualEditor: Link inspector suggestions box should instantly show, then populate with more as API returns","Patched in https://gerrit.wikimedia.org/r/#/c/36110/1
+Awaiting merge.",1354231674,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-smsvykwx7lxu2tyag7ye,task_subcomment,NA
+VisualEditor: Annotation of inline nodes fails,"Annotation of inline nodes fails - the data model is not updated to have any annotations added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1353542940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jml4yae3q65u4srebbyl,task_description,resolved
+VisualEditor: Annotation of inline nodes fails,https://gerrit.wikimedia.org/r/#/c/34958/,1354054132,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jml4yae3q65u4srebbyl,task_subcomment,NA
+VisualEditor: Handle percent-encoding in MWInternalLinkAnnotation,"Per conversation with Gabriel, MWInternalLinkAnnotation needs to deal with percent-encoded hrefs. At least question marks (?) and percent signs (%) will be encoded. We need to decode these before presenting them to the user, encode the user input on the way out, and use href shadowing to make sure we don't change the href if the user didn't change the target (even if that would otherwise happen due to complete vs partial percent-encoding).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353441780,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jazf6d7oefzddss6mv36,task_description,resolved
+VisualEditor: Handle percent-encoding in MWInternalLinkAnnotation,"It's resolved on our end, we have bug 41116 to track the other issues.",1354921807,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jazf6d7oefzddss6mv36,task_subcomment,NA
+VisualEditor: Handle percent-encoding in MWInternalLinkAnnotation,"I5e1de9244d727641c10b6f0a89acc61afba7ecad will not actually fix the problem. I'm cleaning up our link serialization handler right now, which should also fix this issue.",1354916743,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jazf6d7oefzddss6mv36,task_subcomment,NA
+VisualEditor: Handle percent-encoding in MWInternalLinkAnnotation,If5d22e88904d6b2c438caac403ac2d78d440b017 resolves this issue. It's still dependent on bug 41116 (which has a patch that needs merging: I5e1de9244d727641c10b6f0a89acc61afba7ecad ),1354912585,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jazf6d7oefzddss6mv36,task_subcomment,NA
+VisualEditor: Clicking link toolbar button with zero-length selection makes UI go crazy,"...presumably because the link becomes a pre-annotation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353376740,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-idkrdic2vphpfwclosyo,task_description,resolved
+VisualEditor: Clicking link toolbar button with zero-length selection makes UI go crazy,Fixed in I38995d4101fda71bfb2e6fe516603507ce820937 and Ibf6b26de299e54ae8688a2653bf5d5538927f8c3,1353971585,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-idkrdic2vphpfwclosyo,task_subcomment,NA
+VisualEditor: Clicking link toolbar button with zero-length selection makes UI go crazy,This was resolved in the recent inspector rewrite.,1353971422,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-idkrdic2vphpfwclosyo,task_subcomment,NA
+VisualEditor: Provide a way of users seeing the edit-notices and page protection level warnings as they're editing,"From Max's bug 42142
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42142",1353122280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uxbnfma4ejiksnkp2e7x,task_description,resolved
+VisualEditor: Provide a way of users seeing the edit-notices and page protection level warnings as they're editing,Resolved in I581bf5a005a9c18422f952d71064d17d0ba9b540,1354317270,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-uxbnfma4ejiksnkp2e7x,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,"1. Go to https://www.mediawiki.org/wiki/VisualEditor:Testy and click edit
+2. Select all using Ctrl-A (or Cmd-A) and press backspace
+3. Press any content key (e.g. ""a"")
+
+What should happen:
+
+: You get a document with an ""a"" in its own paragraph.
+
+What does happen:
+
+: You get a document with an ""a"" in its own paragraph, and two console errors:
+
+TypeError: this.data[offset] is undefined
+
+...ation)===false){return null;}while(start>0){start--;if(this.offsetContainsAnnota...
+
+load.p...4105Z&* (line 89)
+
+
+TypeError: this.data[offset] is undefined
+
+...ation)===false){return null;}while(start>0){start--;if(this.offsetContainsAnnota...
+
+load.p...4105Z&* (line 89)
+
+
+Thereafter, pressing return in the new context gives:
+
+TypeError: node is null
+
+...ve.Node.call(this,type);this.model=model;this.$=$element||$('<div>');this.parent...
+
+Etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1353120840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_description,resolved
+VisualEditor: Trivial way to get a lot of errors,"Confirmed fixed, will be pushed live on Monday.",1353541840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,https://gerrit.wikimedia.org/r/#/c/34597/1,1353535425,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,"There were actually two cases, with two different root causes.
+
+If the last node in the document was not a paragraph, comment #2 applies: the document is empty and the pre-annotations code was asking for annotations at offset 0. This was fixed a while ago.
+
+If the last node in the document was a paragraph (this is common), the document wouldn't actually be emptied. Instead, all nodes would be removed except the last paragraph, which gets stripped. So after removing ""everything"", we are left with a document that only contains an empty paragraph. However, in the model tree, this empty paragraph is truly empty and does not contain a zero-length text node (most other empty paragraphs do have one).
+
+Once you type a character, CE pawns it first, processing a transaction that inserts a pawn in the paragraph. The transaction processor gets confused by the lack of any content nodes in the paragraph, and issues a rebuild for the contents of the paragraph, which fails spectacularly. The model tree ends up in an inconsistent state with a text node being a direct child of the document node and the paragraph node being gone. This then caused offset computations to be off by one, which caused other parts of CE to do strange things, culminating in an exception in openAnnotations(). When the exception occurs, the pawn hasn't been unpawned yet, so there's pawn leakage.
+
+Trevor has a commit queued up that will fix this.",1353530127,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,"After deleting all the content document if completely empty (data.length = 0),
+however view still askes what are the annotations at offset 0 - and that's what
+fails.
+Possible fix it to make method getAnnotationsFromOffset return empty set if
+given offset does not exists.",1353138590,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,%%%*** Bug 42218 has been marked as a duplicate of this bug. ***%%%,1353138404,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a pawn (♙) appearing,"1. Go to https://www.mediawiki.org/wiki/VisualEditor:Testy and click edit
+2. Select all using Ctrl-A (or Cmd-A) and press backspace
+3. Press any content key (e.g. ""a"")
+
+What should happen:
+
+: You get a document with an ""a"" in its own paragraph.
+
+What does happen:
+
+: You get a document with an ""a"" in its own paragraph, and a pawn.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1353120720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6hldnmgl7xtnj7zwjyv,task_description,resolved
+VisualEditor: Trivial way to get a pawn (♙) appearing,"
+
+%%%*** This bug has been marked as a duplicate of bug 42219 ***%%%",1353138404,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-p6hldnmgl7xtnj7zwjyv,task_subcomment,NA
+VisualEditor: Inserting text content around inline alien nodes throws an exception,"Specifically it fails when trying to insert text content between two inline aliens or after last inline alien inside its parent.
+
+Exception:
+Uncaught TypeError: Cannot read property 'start' of undefined ve.dm.TransactionProcessor.js:259
+ve.dm.TransactionProcessor.processors.replace
+
+// Set change markers on the parents of the affected nodes
+for ( i = 0; i < selection.length; i++ ) {
+	this.setChangeMarker(
+		selection[i].parentOuterRange.start + this.adjustment,
+		'content'
+	);
+}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353106740,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-murhom53ypttvsazncwz,task_description,resolved
+VisualEditor: Inserting text content around inline alien nodes throws an exception,https://gerrit.wikimedia.org/r/34224,1353366778,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-murhom53ypttvsazncwz,task_subcomment,NA
+VisualEditor: Inserting text content around inline alien nodes throws an exception,It also happens when inserting text content before inline alien if that alien is a first child of its parent.,1353137908,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-murhom53ypttvsazncwz,task_subcomment,NA
+"VisualEditor: Sync availability of ""minor edit"" with MW backend","Currently when using VisualEditor to create a new page, the ""Save page"" dialog box offers two checkboxes below the edit summary field: ""This is a minor edit"" and ""Watch this page"".
+
+When creating a page, ""This is a minor edit"" does not typically show up. It's a bug that the checkbox appears when creating a page with the VisualEditor interface.
+
+This bug is closely related to bug 40774.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1352957280,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cougiswjchh3cn6khldz,task_description,resolved
+"VisualEditor: Sync availability of ""minor edit"" with MW backend",Code now live in master; will get deployed in the next cycle.,1354565365,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cougiswjchh3cn6khldz,task_subcomment,NA
+"VisualEditor: Sync availability of ""minor edit"" with MW backend",Change-Id: I9c659845feebb3e9bbf8e13ee67be27c6adb4321,1354426566,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cougiswjchh3cn6khldz,task_subcomment,NA
+"VisualEditor: Sync availability of ""minor edit"" with MW backend","The EditPage backends has this logic in three places:
+
+* Getting html of checkboxes (only if user has minoredit right and if not on a  new page)
+* Setting initial values of checkboxes (if user has minordefault preference)
+* Processing the save action with the minoredit flag (only if has user right and not on a new page)",1354418381,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cougiswjchh3cn6khldz,task_subcomment,NA
+VisualEditor: Floated nodes don't get shields in Chrome,"If you have a floated table inside an alien, it gets a shield (and a phantom) in Firefox but not in Chrome. This is because the table is floated with external CSS triggered by class=""infobox"", rather than an inline style attribute. At the time when we check for $this.css('float'), $this hasn't been attached to the main DOM yet. Firefox computes styles on unattached nodes correctly, but Chrome doesn't.
+
+The solution is to wait until after the entire CE rendering has been built and attached to the DOM before generating shields and phantoms. Possible implementations:
+
+1. Add an onAttach function to ce.Node. After attaching, traverse the entire CE tree and invoke onAttach() on every node (bottom up). This is expensive, though, because you have to traverse the entire tree just to invoke onAttach on the few nodes that use it.
+
+2. Make the ce.Surface throw an 'attached' event after attaching to the DOM, and make the ce.AlienBlockNode constructor listen for this event. This is not as clean, but more efficient, because only nodes that need processing are processed.
+
+I have a slight preference for #2, but I can be convinced either way.
+
+In both cases, the call to onUpdate() in the ce.AlienBlockNode constructor would be removed, otherwise the HTML would be set twice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352948940,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-oxmalsbaodappytqtaoo,task_description,resolved
+VisualEditor: Floated nodes don't get shields in Chrome,Fixed here: https://gerrit.wikimedia.org/r/#/c/33661/,1353018780,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-oxmalsbaodappytqtaoo,task_subcomment,NA
+VisualEditor: Spinner keeps spinning after save fail,"If you try to save a page and it fails (e.g. because of an edit conflict, blocked user, Parsoid down, or whatever), then click Cancel, the spinner keeps spinning and the Save page button remains greyed out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352940660,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kk4vhnmofck2qdxtjn2o,task_description,resolved
+VisualEditor: Spinner keeps spinning after save fail,"
+
+*** This bug has been marked as a duplicate of bug 37837 ***",1354054812,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kk4vhnmofck2qdxtjn2o,task_subcomment,NA
+VisualEditor: Paragraph generated for an empty document should not be unwrapped on the way out,"Currently, the DOM->data converter generates an empty paragraph if the input is an empty string. This paragraph is marked with .internal.generated=='wrapper', so it's unwrapped on the way out. This is bad because we lose change markers that way, and have no way to propagate them.
+
+Instead, it should use another generated marker which causes the paragraph to be unwrapped only if it is empty, and be preserved if it's not empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352938920,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lag2eyarvgkricqxqmeh,task_description,resolved
+VisualEditor: Paragraph generated for an empty document should not be unwrapped on the way out,*** Bug 41905 has been marked as a duplicate of this bug. ***,1353133977,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lag2eyarvgkricqxqmeh,task_subcomment,NA
+VisualEditor: Paragraph generated for an empty document should not be unwrapped on the way out,https://gerrit.wikimedia.org/r/33854,1353123761,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lag2eyarvgkricqxqmeh,task_subcomment,NA
+VisualEditor: Converter should inline-alienate inline tags in wrapping mode even in the mw:unrecognized case,"Normally, unrecognized tags in wrapped blocks are alienated as inline or block depending on the tag name. This is broken for tags with unrecognized mw: types (and for about groups), which are always alienated as block when in wrapping mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352938680,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hfb6u2us7tcoc2xke4cf,task_description,resolved
+VisualEditor: Converter should inline-alienate inline tags in wrapping mode even in the mw:unrecognized case,https://gerrit.wikimedia.org/r/34261,1353386649,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hfb6u2us7tcoc2xke4cf,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg","When loading a page with VE enabled, the ""edit"" tab is changed from the ""vector-view-edit"" message to the ""edit"" message. This is apparent on enwiki, where these messages have different values. It's also apparent when using ?uselang=qqx
+
+This shouldn't happen, the message for the edit tab should be consistent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1352937420,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_description,resolved
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg",Now merged.,1365036328,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg","Rephrased summary.
+
+The problem is that different skins use a different message for the Edit button. Vector uses msg key ""vector-view-edit"". Monobook (and most other skins) use msg key ""edit"".
+
+By default the messages are equal but on en.wikipedia.org, as example, classic msg ""edit"" has been changed to contain ""Edit this page"".
+
+This lead to the tab replacement causing a weird change from ""Edit"" to ""Edit this page"" when in VE mode.",1365027641,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg",Change-Id: I2e7dd85cd14049101e2d49751d37797d77bc7c9d,1365027456,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg","De-prioritising for December; instead, bug 42221 will take on this need, as discussed with Trevor and Roan.",1353122866,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg","Problem is in ViewPageTarget, which assumes that the name of the action and the action's label are the same ('edit' or 'create') or something, per hurried conversation with Trevor. :-)
+
+More widely, we might want our own label for this at first anyway to make it clear which editor people are using during the initial integration - just call it ""VisualEditor"" and leave the other tab visible next to it?",1353017565,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+VisualEditor: Change marking branch appears to be live on MWwiki,"Possibly the wrong version of Parsoid updated? See https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=next&oldid=604180 as an example of '<p data-ve-changed=""[...]"">' elements being created.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352858220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jh7jzzemygqrgcfg25dq,task_description,resolved
+VisualEditor: Change marking branch appears to be live on MWwiki,Fixed in https://gerrit.wikimedia.org/r/#/c/33410/,1352939134,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jh7jzzemygqrgcfg25dq,task_subcomment,NA
+VisualEditor: A wild pawn character appeared!,"Roan told me that, if I ever saw one of your comical placeholder Unicode characters, that it was a pretty well-defined bug. So here:
+
+1. Create an unordered list
+2. Enter some items
+3. Hit enter twice
+4. Type something
+
+Expected: Whatever I typed should appear on the screen.
+
+Actual: Pawn character! It also prints my text, but only after '♙\n'.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352856780,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-az3twbgyfogcznpnnndd,task_description,declined
+VisualEditor: A wild pawn character appeared!,"**orbit** wrote:
+
+This must've been something that was fixed as part of some other work. I'm unable to reproduce.",1354656971,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-az3twbgyfogcznpnnndd,task_subcomment,NA
+VisualEditor: A wild pawn character appeared!,"Potentially deeper meaning: The list-creation code is really buggy and needs to be fixed. I can't seem to *end* an unordered list, once I create it.",1352857130,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-az3twbgyfogcznpnnndd,task_subcomment,NA
+"VisualEditor: In bullet list, SHIFT-LEFT selection reseted when reaching deeper item","Steps to reproduce:
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press ""Edit""
+3) Click at the end of an item in the big list at the bottom of the page.
+4) Press SHIFT and LEFT, maintaining them pressed for a while
+
+Expected behavior: Text is selected as long as SHIFT-LEFT is pressed
+Actual behavior: Text is selected until deeper-level bullet is reached. When it is reached, the previous selection is unselected, and a new selection starts.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351564200,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-qacmwzmv3ujwgmodf5y7,task_description,resolved
+"VisualEditor: In bullet list, SHIFT-LEFT selection reseted when reaching deeper item",Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306610,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qacmwzmv3ujwgmodf5y7,task_subcomment,NA
+"VisualEditor: In bullet list, SHIFT-LEFT selection reseted when reaching deeper item",Resolved in Iba55cfc3d531e7d1333b78c94912ff22179aace8,1354222673,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-qacmwzmv3ujwgmodf5y7,task_subcomment,NA
+"VisualEditor: In bullet list, SHIFT-LEFT selection reseted when reaching deeper item",Confirmed in Firefox and Chrome.,1351565870,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qacmwzmv3ujwgmodf5y7,task_subcomment,NA
+VisualEditor: ve.ce throws Uncaught TypeError: Cannot read property 'nodeType' when suface loses focus,"In Chrome, when I click inside the editor, then right-click outside the editor, I get an exception:
+
+
+Uncaught TypeError: Cannot read property 'nodeType' of null /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:118
+ve.ce.getOffset /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:118
+ve.ce.SurfaceObserver.poll /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:135
+ve.ce.SurfaceObserver.stop /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:81
+ve.ce.Surface.documentOnBlur /w/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js:322
+proxy l.php:775
+jQuery.event.dispatch l.php:3063
+elemData.handle.eventHandle l.php:2681
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351539120,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-f2x5ytlsmyx24xetmj5s,task_description,resolved
+VisualEditor: ve.ce throws Uncaught TypeError: Cannot read property 'nodeType' when suface loses focus,Fixed in gerrit 36687.,1354581344,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f2x5ytlsmyx24xetmj5s,task_subcomment,NA
+VisualEditor: ve.ce throws Uncaught TypeError: Cannot read property 'nodeType' when suface loses focus,*** Bug 42525 has been marked as a duplicate of this bug. ***,1354155569,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f2x5ytlsmyx24xetmj5s,task_subcomment,NA
+VisualEditor: ve.ce throws Uncaught TypeError: Cannot read property 'nodeType' when suface loses focus,"Confirm issue in Chrome, Safari; not in Firefox.",1351541465,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f2x5ytlsmyx24xetmj5s,task_subcomment,NA
+VisualEditor: Clicking inside an alien node throws an TypeError,"Uncaught TypeError: Cannot call method 'getModel' of undefined ve.ce.js:208
+ve.ce.getOffsetFromElementNode ve.ce.js:208
+ve.ce.getOffset ve.ce.js:121
+ve.ce.SurfaceObserver.poll ve.ce.SurfaceObserver.js:135
+ve.ce.SurfaceObserver.start ve.ce.SurfaceObserver.js:66
+ve.ce.Surface.onMouseUp ve.ce.Surface.js:352
+proxy jquery.js:775
+jQuery.event.dispatch jquery.js:3063
+elemData.handle.eventHandle
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351536660,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-hrsow4jckaq52vpprzud,task_description,resolved
+VisualEditor: Clicking inside an alien node throws an TypeError,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306603,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hrsow4jckaq52vpprzud,task_subcomment,NA
+VisualEditor: Clicking inside an alien node throws an TypeError,This has been resolved.,1354222915,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-hrsow4jckaq52vpprzud,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","We have this dude in the Vector skin next to the user name:
+
+{F26476317,size=full,layout=inline} http://bits.wikimedia.org/static-1.21wmf2/skins/vector/images/user-icon.png
+
+If one specifies their gender in preferences as female, it would be cool to see a female user icon instead of the dude. :)  If we're interested in gender gap, this could be one tiny thing to help make the software more welcoming.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45056
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51927
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53732",1351487760,PHID-USER-lzhljhpbm3qfphvqyill,PHID-TASK-y3luskovb4jkrwp3ep3w,task_description,resolved
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**Jason_quinn** wrote:
+
+Postscript:
+
+Blue is for boys. Pink is for girls. Yellow or green are neutral.
+
+This is a cultural convention for gender through the Western world and much of the rest of the World, especially for example in nurseries, and has been for the better part of a century. This is *why* many here associate blue with male. If you are from the Western world and don't have at least some mental association about that, you're an oddity. The suggestion of ""red"" rather than ""pink"" to denote female is puzzling. (In fact, the red icon suggested above for female and the old icon's blue color are clearly similar to the red and blue used for instance by Olympic boxers.) It is also puzzling why ""yellow"" or ""green"" weren't mentioned as possible general neutral colors.
+
+I'm not saying that this color convention (or any color convention) should be used for the icon. There would be many issues to discuss about it. Some people might object saying it re-enforces gender stereotypes and so on. There may be countries where the conventions are totally different (I'm unaware of any but this same issue came up when color-coding Asian family tree charts in the encyclopedia and nobody has yet complained). All I am saying is that it wasn't clear to me from the above discussion that anybody even was even consciously aware of the convention so it needed to be mentioned explicitly. Getting rid of the icon altogether may be the best course of action anyhow so this might be moot except to better understand the issue.
+
+Regardless, it was a fantastic suggestion that the icon should not have an indefinable skin color. Bravo on that.",1411440166,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Change 157990 merged by jenkins-bot:
+Make profile icon gender neutral and remove from login link in Vector
+
+https://gerrit.wikimedia.org/r/157990",1410560713,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Change 146979 abandoned by Robmoen:
+Make profile icon gender neutral and remove from login link in Vector
+
+Reason:
+Abandoned in favor of new patch in skins directory.
+https://gerrit.wikimedia.org/r/#/c/157990/
+
+https://gerrit.wikimedia.org/r/146979",1409694538,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Change 157990 had a related patch set uploaded by Robmoen:
+Make profile icon gender neutral and remove from login link in Vector
+
+https://gerrit.wikimedia.org/r/157990",1409694478,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","While we wait for screenshots here, I've loaded the icon at its default size of 13px and out of context I would have called it a sunset over a hill. I guess that *is* gender neutral, no idea how clear it is.
+
+See also bug 45056 comment 15.",1405584342,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Change 146979 had a related patch set uploaded by Robmoen:
+Make profile icon gender neutral.  Remove from Login link
+
+https://gerrit.wikimedia.org/r/146979",1405552771,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**wmf.amgine3691** wrote:
+
+This idea has already been discussed in this bug (starting around comment 9, 17) and was discussed in other bugs (35341) and has its own bug (45056).",1405106440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**swalling** wrote:
+
+(In reply to Nemo from comment #57)
+> The problem in this bug is very well defined and it has nothing to do with
+> your proposed solution. Your proposal is a solution for the supposed problem
+> ""personal toolbar personalises"", which is a) different, b) not agreed upon
+> as a problem. It's possible that the two problems will be resolved by a
+> single solution in the end, but collapsing them in a single report doesn't
+> help anything.
+
+When a problem comes up with a current design (whether it's an icon, a button, or a whole feature), it is extremely useful to go back to basic principles and talk about why something is needed in the first place. Questioning whether a design element is necessary hones in on why it's important. If we understand why it's important, then if we want to keep it, we can be clearer about what it's supposed to be doing. 
+
+TL;DR: all options are on the table. If you don't like it, we can always go discuss this on the more open-ended bug I filed. But berating a designer for having ideas is not progress.",1405099573,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I don't know what ""personal toolbar personalises"" means, can you explain/clarify?",1405099452,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","The problem in this bug is very well defined and it has nothing to do with your proposed solution. Your proposal is a solution for the supposed problem ""personal toolbar personalises"", which is a) different, b) not agreed upon as a problem. It's possible that the two problems will be resolved by a single solution in the end, but collapsing them in a single report doesn't help anything.",1405098958,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Nemo, bugs shouldn't neccesarily express a solution, the problem here is ""icon represents gender"" it's easy to assume the fix is ""make a better icon"" when the problem could just as easily be ""don't have an icon"" when we presuppose a solution we close ourselves off to many possible correct conclusions for the same issue. 
+
+Pre- and post- login icons are currently the same asset by the way, to answer your question.",1405097844,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","What is the pre-login or post-login icon? Jared, please file a separate bug report for separate issues. This bug is not about removing the icon.",1405075490,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Created attachment 15907
+post login
+
+see post login sketch
+
+- icon removed
+- additional per item padding added
+- right margin adjusted to align with search.
+
+**Attached**: {F9746}",1405057269,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I propose we remove the post-login icon for now, and when wikifont is in core we can add the updated icon then. We have personal bar instrumented right now, so we'll be able to see if there is any dropoff from users based on the removed icon.",1405056730,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**swalling** wrote:
+
+(In reply to Jared Zimmerman (WMF) from comment #51)
+> Created attachment 15906 [details]
+> no icon -> mediawiki.ui controls
+> 
+> How about for now we just remove the icon altogether, pre-login we should
+> use medaiwiki.ui controls, and post login, just remove the existing icon.
+
+I think this is the right way to go for login. 
+
+Not sure about removing the icon for once you're logged in. It does provide value, in that it denotes that the menu items are related to you personally. I think if we try something simpler (the version May did pushed things a bit in terms of personality and verve) then we can easily replace it. Munaf is working on something in conjunction with our designs for a task suggestions alpha.
+
+**Attached**: {F9744}",1405056372,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Created attachment 15906
+no icon -> mediawiki.ui controls
+
+How about for now we just remove the icon altogether, pre-login we should use medaiwiki.ui controls, and post login, just remove the existing icon.
+
+**Attached**: {F9744}",1405056147,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel",*** Bug 67837 has been marked as a duplicate of this bug. ***,1405052255,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Hi RituS! Actually I don't think this bug at this point is the best first task for a new contributor. We have many other bugs to choose from at 
+
+https://www.mediawiki.org/wiki/Annoying_little_bugs
+
+The reason is...
+
+(In reply to comment #39)
+> Removing easy keyword; the implementation may be easy, but as we still
+> haven't 
+> agreed on what to do with this, it's probably not something we'd necessarily
+> want to bring a new person into.
+
+I agree. Have we agreed on a plan? If so, a new comment summarizing the work that needs to be done is welcome. With 48 comments and 5 attachments, the chances to work on something that won't be directly merged are high.",1386775181,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Hi RituS, thanks for your interest! Please see https://www.mediawiki.org/wiki/Developer_access and https://www.mediawiki.org/wiki/Gerrit/Tutorial for information and also for where to receive help with the general development setup.",1386769884,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**ritusparks** wrote:
+
+Hey!
+I'm a newbie to mediawiki and I would like to work on this bug! Could somebody navigate me through the required procedure?",1386766074,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #40)
+> 
+> As you point out, it should likely be anthropomorphic. Blue is used for
+> accent in the skin, but every icon and graphic is monochromatic grey
+> (http://ur1.ca/fx8u3, search) - as should be this one.
+
+Good point - I must have been thinking of some extension icons I'd seen that were link-coloured.
+
+(In reply to comment #44)
+> Created attachment 13548 [details]
+> Profile icon
+
+As I said, an icon like that defeats the purpose of having a user icon in the first place, as it is not immediately recognisable as 'user account' related and thus does not adequately function as a graphical label for the personal tools. Indeed, that it is so similar to the echo thanks thing should help explain why it isn't appropriate here.
+
+The one Munaf made or one of the ones thehelpfulone linked would be much more appropriate and effective. May need to fix the colours/weight for the skin, but that is the direction this should be taking. Or rather that it should never have left.
+
+//attachment profile.svg ignored as obsolete//",1382493376,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #43)
+> Created attachment 13547 [details]
+> Example use of icon
+
+I want to say that I appreciate all of the work that the design team does. Good design on our projects and in our products is important. A rich, meaningful, and aesthetically pleasing user experience is something that every user who visits our sites or uses our services should have.
+
+That said, sweet Jesus no, we will not be putting that icon anywhere near MediaWiki core or Wikimedia wikis. It conjures up [[blackface]] in the mind and will be viewed by many users to be offensive and completely inappropriate. This icon flatly will not work.
+
+In seeing another squared-headed smiley face in the wrong color, I'm reminded of bug 51927. (Oh, it's already marked as a ""see also."" Hrm.)
+
+//attachment Screenshot 2013-10-22 16.06.53.png ignored as obsolete//",1382492283,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Profile icon
+
+//attachment profile.svg ignored as obsolete//",1382486305,PHID-USER-tjeabpzbwsqw3xciydvb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Example use of icon
+
+//attachment Screenshot 2013-10-22 16.06.53.png ignored as obsolete//",1382486273,PHID-USER-tjeabpzbwsqw3xciydvb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Realized the asset uploaded was slightly out of date, May is uploading the correct asset and mockup now. 
+
+I feel that the asset she's uploading (a variation on the original she posted) head and shoulders (ha!) better than what we have now. its a small change, I'd prefer to integrate it, since its in-line with the user icon on mobile as well as upcoming multi-media features. Stay tuned for the updated asset in just a bit.",1382481068,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**wmf.amgine3691** wrote:
+
+Hmmph. https://bits.wikimedia.org/static-1.22wmf21/extensions/UniversalLanguageSelector/resources/images/cog-sprite.svg?2013-10-10T16:45:00Z works just fine... <grumbles>",1382480808,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**wmf.amgine3691** wrote:
+
+(In reply to comment #39)
+...
+> It seems rather like we're stuck on a choice - whether to be intuitive and
+> clear or to not offend people. Strange choice, since no matter what you do
+> you'll pretty much always wind up offending or disturbing someone if you've a
+> broad enough audience.
+
+Nonsense.
+
+As you point out, it should likely be anthropomorphic. Blue is used for accent in the skin, but every icon and graphic is monochromatic grey (http://ur1.ca/fx8u3, search) - as should be this one.
+
+Aesthetically not the best choice for some people, but it's likely the least offending (even to the designers) compromise and we're all just waiting for someone to point this out and force the stakeholders to grow up and accept the compromise.",1382480582,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Removing easy keyword; the implementation may be easy, but as we still haven't agreed on what to do with this, it's probably not something we'd necessarily want to bring a new person into.
+
+There are arguments here that an icon is not needed at all, but based on what Trevor said, even if it isn't needed, it's definitely useful. To remain useful, however, it needs to also remain a recognisable 'user' icon - that rules out anything with too much abstraction that wouldn't necessarily have the same meaning to the user, like a smiley face or animal (even without added issues those might present such as those Siddhartha Ghai points out), and brings us back to the more standard head and shoulders, which arguably tend to look male. Blue, which fits the skin, is apparently also problematic because in some cultures blue is associated with masculinity.
+
+It seems rather like we're stuck on a choice - whether to be intuitive and clear or to not offend people. Strange choice, since no matter what you do you'll pretty much always wind up offending or disturbing someone if you've a broad enough audience.",1382479349,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #28)
+> Another design practice that I'm a fan of is to go with more abstract user
+> icons or animal icons e.g. github's
+> https://dribbble.s3.amazonaws.com/users/8063/screenshots/873671/
+> github_icon_vector_shape_teaser.png
+
+I'd just like to point out that animal icons would not be wise since languages may associate certain animals with certain genders by default. For example, a user with native language hindi might consider a cat icon to be female and a lion to be male. Cat: male: बिल्ला, female: बिल्ली, latter is what is generally default usage. Lion invokes a male idea since hindi, like English, defaults to lion (शेर), not lioness (शेरनी)",1380860683,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Can we get someone to integrate this, we've recently updated the general user icon used in mobile for user talk, article history, and watchlist, so it would be great to get this one in sync sooner rather than later.",1380748396,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Removed May (visual designer) as the assignee, not that she's uploaded the new asset from the Echo icon set. Please assign a developer to submit a patch as needed.",1375220836,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Profile icon
+
+//attachment User_web.svg ignored as obsolete//",1375121322,PHID-USER-tjeabpzbwsqw3xciydvb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Thanks Jared; please leave correct terminology too in the bug summaries for the purposes of discoverability (the area is called ""personal tools"").",1372369546,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel",We'll address this icon as part of a a visual alignment exercise we're doing with the echo notifications,1372368686,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #5)
+> (In reply to comment #3)
+> > Thanks for pointing this out, Aude.  For ideas on how to rework the default
+> > icon to make it more gender-neutral, here's the ""gallery of default
+> > anonymity"":
+> > http://www.murketing.com/journal/?p=3098
+> 
+> Flickr is IMHO the best.
+
+BTW, apparently Flickr disagreed :) , they replaced the default buddy icon with a purple square containing a rainbow camera.",1369728557,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**Thehelpfulonewiki** wrote:
+
+What about https://commons.wikimedia.org/wiki/File:Gnome-stock_person.svg or https://commons.wikimedia.org/wiki/File:Crystal_Clear_app_personal_gray.png (I prefer the former).",1366938313,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Looks like it wasn't linked yet: monobook icon on Commons, ""Racially, gender neutral icon"". https://commons.wikimedia.org/wiki/File:User-variant.png
+
+(In reply to comment #29)
+> I say we keep it, and when we make all the other icons monochrome (going
+> along
+> with work like Agora and VisualEditor) it should become a silhouette.
+
+I don't understand, are you saying it can't be changed before that for some reason of consistency? Also, does ""silhouette"" mean that in
+
+(In reply to comment #28)
+> abstract
+> head + shoulders or an abstract face in b&w.
+
+you recommend the former?",1363515550,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Just adding my 2 cents in here.
+
+The icon was chosen, by me, in 2009. It was the standard generic user icon in the Tango icon library, which we were embracing at the time.
+
+I agree with some of comments here that using stereotypes to make the icon more gender specific is going to be offensive. Should we also assume their nationality based on their location or language and adjust the icon accordingly? Obviously this is going to be a nightmare. Besides, none of this would any value.
+
+The use of the icon was inherited from Monobook. As many people are aware, Vector was more of a riff on Monobook than a new skin. At the time especially, Monobook had become this iconic skin that everyone was so attached to after years of staring at it, that every tiny adjustment we proposed was highly controversial.
+
+Do we still need the icon? I think so. It's actually one of the more reasonable uses of iconography - which we use very selectively in Vector - because it is...
+
+1. Identifiable (must be obvious what it means)
+2. Necessary (icons for the sake of icons are bad)
+3. Important (icons for obscure tasks bring attention to the wrong things)
+
+I say we keep it, and when we make all the other icons monochrome (going along with work like Agora and VisualEditor) it should become a silhouette.",1361994999,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**sumanah** wrote:
+
+symbolic variant from gnome-icon-theme courtesy Mizmo (Máirín Duffy of Red Hat)
+
+I asked a few other designers who work in open source to comment.  Georgia Bullen wrote:
+
+""Hmmm...
+
+Well there are the options of just stick figure gender-less icons e.g.
+http://wikieducator.org/images/1/16/Dummy_user.png and if you avoided
+colors, and went with gray or something like that then it wouldn't even
+have gender color implications.
+
+Another design practice that I'm a fan of is to go with more abstract user
+icons or animal icons e.g. github's
+https://dribbble.s3.amazonaws.com/users/8063/screenshots/873671/github_icon_vector_shape_teaser.png
+
+Or this awesome site: https://diy.org/ which uses animal avatars to avoid
+issues with COPA for children.
+
+Hope that's helpful!
+
+-georgia""
+
+
+Máirín Duffy of Red Hat wrote:
+
+""The best gender- and race-neutral icons of people are basically abstract
+head + shoulders or an abstract face in b&w. One of the links you posted
+in the bug had a few good examples:
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/garageband.gif
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/myspacenophoto.jpg
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/nopic_192.gif
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/vimeo.jpg
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/identica.png
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/npr.gif
+
+FWIW the icon you guys are using now is one of the old gnome-icon-theme
+icons. I am attaching a copy of the same icon from the newer
+gnome-icon-theme, symbolic variant - it's licensed GPL, I've pasted the
+link with license details below:
+
+http://git.gnome.org/browse/gnome-icon-theme/tree/COPYING
+
+You may of course feel free to use it!
+
+~m""
+
+//attachment avatar-default-symbolic.svg ignored as obsolete//",1361566851,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**sumanah** wrote:
+
+(In reply to comment #24)
+
+> Speaking on this issue, I think we should avoid any kind of gender cues in
+> the
+> icon. The concept of ""gender"" is intensely personal, mercurial, and
+> ephemeral.
+
+I completely get what you're saying here (and nudge you to potentially undo the WONTFIX on Bug 25834 to expand the currently binary gender options MediaWiki preferences offer users).  But is it really possible to avoid *any* gender cues in an icon given that ""male"" is, to the perception of most users, the default state of any head-and-shoulders icon unless it includes specific ""not male"" markers?  Defeating the unmarked state is tough.
+
+> This bug actually points to a larger issue that we have within the software
+> itself (which is that gender is a binary switch, rather than something that
+> accommodates individuals who identify as ""genderqueer"").
+
+> (And yes, I know that namespace translations for user pages based on gender
+> is
+> a whole other ball of wax, and I can't hope to think we'll ever solve for
+> gender-identification problems that are fundamental to a language itself).
+
+Solve entirely?  No.  *Improve* how we deal with genderqueer people in all languages?  Sure.
+
+People opining on this bug ought to also look at Bug 30442 - give the user a chance to specify the gender when opening the account - and Bug 31816 - Improve the wording of gender selection option.
+
+> As far as the icon itself goes, I would prefer that we also would move
+> towards
+> an image that is also racially neutral (thus, Munaf's grey icon is probably
+> the
+> best choice).
+
+Seconding the request for the icon's ""skin color"" to be neutral. :-)",1361014746,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I don't necessarily think I need to address them; my position is that the icon isn't needed at all and I think it distracts as clutter rather than providing a visual cue.
+
+However, I'm not married to killing it off, and if people decide that we want to keep it, I'm fine with that, but I also want to make sure that we're working inside some rational guidelines.",1360986464,PHID-USER-ua75tm4u7cmt4mdof6vb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Brandon, thanks for adding your points about older comments, but I hope you can also address comment 20, comment 23 and bug 45056 comment 6: instead of explaining your position you just restated it in a post-scriptum. Thanks.",1360985671,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #4)
+
+> How do you make a ""female"" icon anyway, short of giving it breasts? Long
+> hair?
+> Tell that to Brandon and Sumana!
+
+Are you suggesting that I could be mistaken for a woman? ;)
+
+Speaking on this issue, I think we should avoid any kind of gender cues in the icon. The concept of ""gender"" is intensely personal, mercurial, and ephemeral. This bug actually points to a larger issue that we have within the software itself (which is that gender is a binary switch, rather than something that accommodates individuals who identify as ""genderqueer"").
+
+(And yes, I know that namespace translations for user pages based on gender is a whole other ball of wax, and I can't hope to think we'll ever solve for gender-identification problems that are fundamental to a language itself).
+
+As far as the icon itself goes, I would prefer that we also would move towards an image that is also racially neutral (thus, Munaf's grey icon is probably the best choice).
+
+That said, I still want to get rid of the icon entirely.",1360985052,PHID-USER-ua75tm4u7cmt4mdof6vb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**massaf** wrote:
+
+
+> But why did you change the color of userpage link in that mockup?
+> This just distracts from the purpose of the change :/
+
+Unintentional. I habitually plugged in Agora red (#cc0000) instead of our current link red (#ba0000) so there's a weird differential.
+
+> Actually I'm starting to lean towards just killing the icon per bug 45056.
+
+Not sure I'm convinced of that yet. Just one icon does make the user tool list more scannable (ideally they'd be re-arranged or redesigned altogether).",1360984917,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I agree with the three comments above (as said on bug 45056). Finding a better icon doesn't seem that hard, and we're not in a hurry: the current one is not doing any severe harm, it's just imperfect (and in monobook probably even good enough).",1360983710,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel",Agora doesn't really work with Vector.,1360981328,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I kind of find the icon to be a sort of visual cue. Without it the personal bar is just a collection of unidentified links. While with the icon it's instantly identified as a series of links related to the user.
+
+Stuff like proper padding and lining up of whitespace are invisible when they are present and done right. But when they are not there they give uncomfortable feelings, usability issues, etc... I think the personal icon fits into that category.
+
+Why don't we try Agora-fying the icon?
+https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_Icon_Set",1360977067,PHID-USER-gibrlx54k2riiuit5paf,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Two things: One, that is not a male icon. Blue does not make it male. Blue matches the skin, and I really don't understand why there is a fuss about that in particular. Two, killing the icon entirely would make sense with current skins especially since it has no functional significance anyway.
+
+GRAW. Arg. Chickidee?",1360972762,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #17)
+> Personally, I say kill the icon.  It's the only one we have, and it stands
+> out because of it.  Maybe we revisit them in the future, but for now I don't
+> see a purpose.
+
+We may one day have an avatar up there (similar to Facebook). Definitely something to think about for [[mw:GlobalProfile]]. For now, I think you're probably right that no icon is better than the current icon.",1360971005,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Personally, I say kill the icon.  It's the only one we have, and it stands out because of it.  Maybe we revisit them in the future, but for now I don't see a purpose.",1360970770,PHID-USER-ua75tm4u7cmt4mdof6vb,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #14)
+> Created attachment 11794 [details]
+> testing out a gender-neutral icon
+> 
+> Not sure I see what you're seeing. It fits fine when you scale and color it
+> based on context. 
+
+Okay, it's considerably better when appropriately colored (but still looks like a pawn). But why did you change the color of userpage link in that mockup? This just distracts from the purpose of the change :/
+
+Actually I'm starting to lean towards just killing the icon per bug 45056.
+
+//attachment gender-icon-test.png ignored as obsolete//",1360967877,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #9)
+> Killing this icon was briefly proposed at bug 35341.
+
+Filed separately as bug 45056.",1360967497,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**massaf** wrote:
+
+testing out a gender-neutral icon
+
+Not sure I see what you're seeing. It fits fine when you scale and color it based on context. 
+
+A shade of gray would work if each user portlet item had an icon alongside it, which we're talking about in other bugs.
+
+//attachment gender-icon-test.png ignored as obsolete//",1360965592,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","So, I don't want to be a buzzkill and mean, but Munaf, have you actually tried putting that icon into the interface?
+
+Because it looks awful. It doesn't fit the rest of the skin and hardly resembles a human, especially scaled-down. Maybe it would be a little better if made blue-ish, but I'm still skeptical about the new look.",1360955260,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**massaf** wrote:
+
+an attempt at a gender-neutral icon
+
+Here's a first attempt. I agree with Krinkle that it shouldn't draw attention. Link blue (#3366bb) might be appropriate, but for now it's gray. Thoughts?
+
+//attachment GenderNeutralPerson.png ignored as obsolete//",1360954184,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Well, as Sumana notes, the current icon can be perceived as conforming to some gender stereotypes, so it's not ""neutral"" in its common perception. I've clarified the summary further.",1360949789,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I agree with Krinkle.  I don't see what makes this icon (https://bits.wikimedia.org/static-1.21wmf9/skins/vector/images/user-icon.png) male.  I don't think a blue shirt makes it male.
+
+As he said, Vector uses a lot of blue.  In particular, light blue.  We could change the shirt color to light blue to make it further match the theme, but I don't know that this is really necessary.",1360947541,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel",Killing this icon was briefly proposed at bug 35341.,1360946866,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #6)
+> I ask our designers to figure out how to make a more gender-neutral icon
+> (perhaps dispensing with the requirement that it look like a person).
+
+Species-neutral too, I like it :)",1360945647,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Sorry for double comment.
+
+(In reply to comment #5)
+> Flickr is IMHO the best. Should also be {{PD-ineligible}} and in compliance
+> with the colour scheme per Krinkle above.
+
+(Same for Yahoo and identi.ca, very similar.)
+
+(In reply to comment #6)
+> The current icon is
+> https://bits.wikimedia.org/static-1.21wmf9/skins/vector/images/user-icon.png
+> .
+
+Ah, right, I forgot that monobook is different! You can see the old good one e.g. in the screenshot at https://creativecommons.org/weblog/entry/13967
+I've never considered it particularly manly: the hair always looked to me like a bun (if this is the correct term for the hairstyle), which is indeed particularly rare for men. :-)
+Hence the ? in the bug summary.",1360945543,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**sumanah** wrote:
+
+The current icon is https://bits.wikimedia.org/static-1.21wmf9/skins/vector/images/user-icon.png .
+
+(In reply to comment #4)
+> I prefer a single, neutral icon to gender specific icons. 
+> 
+> How do you make a ""female"" icon anyway, short of giving it breasts? Long
+> hair?
+> Tell that to Brandon and Sumana!
+
+For people who haven't met us: Brandon is a man with long hair, and I am a woman with short hair.
+
+These kinds of avatars are usually heads, head-and-shoulders, or stick figures of the whole body, so some designers use long hair, earrings, or a skirt as a shorthand for ""female.""
+
+I ask our designers to figure out how to make a more gender-neutral icon (perhaps dispensing with the requirement that it look like a person).",1360945018,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #3)
+> Thanks for pointing this out, Aude.  For ideas on how to rework the default
+> icon to make it more gender-neutral, here's the ""gallery of default
+> anonymity"":
+> http://www.murketing.com/journal/?p=3098
+
+Flickr is IMHO the best. Should also be {{PD-ineligible}} and in compliance with the colour scheme per Krinkle above.",1360944568,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I prefer a single, neutral icon to gender specific icons. 
+
+How do you make a ""female"" icon anyway, short of giving it breasts? Long hair? Tell that to Brandon and Sumana!",1360943543,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**sumanah** wrote:
+
+Thanks for pointing this out, Aude.  For ideas on how to rework the default icon to make it more gender-neutral, here's the ""gallery of default anonymity"": http://www.murketing.com/journal/?p=3098",1360943098,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","The MediaWiki Vector skin is primarily white/grey oriented with focus on blue and activity on orange (mouse down).
+
+Blue is not male in this context, it is theme colours. Using red would grab wrong attention to the icon.
+
+Removing 'easy' keyword until it is clear whether we want this in the first place. Adding 'design' and CC-ing Trevor for his opinion.",1355997451,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**p.selitskas** wrote:
+
+If the icon from Vector is this[1], then we can pick a red one for girls[2]. If red is not OK, then anyone can just change the color in SVG and it's done.
+
+--
+[1] https://commons.wikimedia.org/wiki/File:Emblem-person-blue.svg
+[2] https://commons.wikimedia.org/wiki/File:Emblem-person-red.svg",1355924272,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","Tested with IE 8 and latest RC of FF.
+
+Current behaviour:
+When clicking the ""preview"" or ""show diff"" button, the page reloads.
+
+Evidence:
+...after the DOM is ready...
+...executed in JavaScript console...
+> mw.loader.getState('mediawiki.action.edit.preview');
+'registered'
+
+Expected behaviour:
+When clicking the ""preview"" or ""show diff"" button, live preview just replaces some elements in the DOM. No page reload.
+
+> mw.loader.getState('mediawiki.action.edit.preview');
+'ready'
+
+How to reproduce:
+Set your interface language to de or en, enable ""Use live preview"" in [[Special:Preferences]], go to a page, edit a section, click preview.
+
+Note:
+Using manually
+mw.loader.load('mediawiki.action.edit.preview');
+works perfectly: After it is loaded, LivePreview works as expected.
+
+--------------------------
+**Version**: 1.20.x
+**Severity**: normal",1350898080,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-rjnvooe4gramc7frhovi,task_description,resolved
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","(In reply to comment #5)
+> https://bugzilla.wikimedia.org/show_activity.cgi?id=41267
+> 
+> I am confused. Please tell me what is ""right"" now?
+> 
+> Using [Regression] in bug title or Keyword ""code-update-regression"" or both?
+
+They keyword is what counts. The reason various people prefer to (sometimes) include (parts of) keywords or components (e.g. ""[Regression]"", ""VisualEditor: .."" etc.) is because most interfaces with bugzilla content lack proper indication of components and tags, so we put them in the subject so that they can be seen directly (e.g. in irc notifications for bug changes and in e-mail notifications[1]).
+
+[1] Yes, for some of the fields there are mail headers sent, but that is only useful for querying e-mails, not when browsing them in any mail applications plain list view.",1351012277,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","I guess different people have different habits, so I change my mind and say: Do what you want with the bug subject, but having the keywrod set would be really great."" Sorry for any confusion.",1351008994,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","https://bugzilla.wikimedia.org/show_activity.cgi?id=41267
+
+I am confused. Please tell me what is ""right"" now?
+
+Using [Regression] in bug title or Keyword ""code-update-regression"" or both?",1351008627,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","In the 1.20 release-notes:
+
+* Live preview functionality has been improved and moved into the
+ 'mediawiki.action.edit.preview' module. The old 'mediawiki.legacy.preview' module
+  has been removed.
+
+Looking at core, the only usage of 'mediawiki.action.edit.preview' is in the resource definition
+
+Original commit:
+https://github.com/mediawiki/core/commit/4d4bfc27a1bedf6b0d1670707ac812fe36fe85ad
+
+EditPage.php now:
+
+		if ( $wgUser->getOption( 'uselivepreview', false ) ) {
+			$wgOut->addModules( 'mediawiki.legacy.preview' );
+		}
+
+It got killed by https://github.com/mediawiki/core/commit/bb51a58e575b13eb8b6c496482f7066a7081f676
+
+https://gerrit.wikimedia.org/r/29339",1350924643,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]",(Regression => keyword code-update-regression),1350923316,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]",Used Vector skin to test,1350898685,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","Commons runs 1.21wmf2
+
+Also tested at dw.wp which runs 1.21wmf1 and there it works. So my guess is that the bug slipped-in between the two versions.",1350898365,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+VisualEditor: Strange behavior after overwriting nowiki block,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Put cursor within the nowiki block
+2) Press a
+3) Press Left
+4) Press b
+5) Problem: ""a"" has disappeared
+
+
+(off-topic: with more complex moves I have spotted a self-replicating snowman ☃, now hunting him down)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1350624900,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-c65rdnrtnbgfg3a46ubp,task_description,resolved
+VisualEditor: Strange behavior after overwriting nowiki block,Now fixed as part of the alienation re-write.,1360205998,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c65rdnrtnbgfg3a46ubp,task_subcomment,NA
+VisualEditor: Strange behavior after overwriting nowiki block,Confirmed.,1350939018,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c65rdnrtnbgfg3a46ubp,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Put cursor at end of nowiki line
+2) Select a different style
+3) Problem: Style not applied
+
+The style is applied if the line contains simple text instead.
+The style is applied if selecting the whole nowiki line instead of just putting the cursor at end of line.
+
+I guess nowiki in headers is not usual, though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350623940,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-5pbz4o5r22cqczijgvqj,task_description,resolved
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,Merged and will go out in the deploy train tomorrow.,1367181672,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,https://gerrit.wikimedia.org/r/#/c/61157/,1367020557,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,"This is a bug in newFromContentBranchConversion(), and is caused by selectNodes() returning the paragraph rather than a text node, because the selection is between the open/closing paragraph and the alien.",1363988049,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,"Can't reproduce. Note that it is nowiki in paragraph, not in a header.",1360361449,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,And in Chrome.,1360205937,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,Confirmed in FF.,1350928759,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Backspace does not remove paragraph when previous paragraph contains nowiki block,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Put cursor at end of nowiki line
+2) Press Enter
+3) Press Backspace
+4) Cursor moves back but newly created paragraph remains
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350622500,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-7erbrnp4x3oao3bdre67,task_description,resolved
+VisualEditor: Backspace does not remove paragraph when previous paragraph contains nowiki block,Still a CE issue (?).,1360205834,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7erbrnp4x3oao3bdre67,task_subcomment,NA
+VisualEditor: Backspace does not remove paragraph when previous paragraph contains nowiki block,Confirmed.,1350928635,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7erbrnp4x3oao3bdre67,task_subcomment,NA
+VisualEditor: Text entered at left of nowiki block replaced with a slug character (pawn) when saved,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Put cursor at end of line
+2) Press Left
+3) Press a
+4) Problem: ""a"" does not seem to appear. Instead, it seems like the beginning of the block is being selected.
+5) Save
+6) Where ""a"" is expected, there is a pawn ♙
+
+= Heading 1a =
+♙<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1350615420,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-peotted4ituorcv5mtdk,task_description,resolved
+VisualEditor: Text entered at left of nowiki block replaced with a slug character (pawn) when saved,"This has been fixed in the ensuing 3 months, probably when aliens was re-written.",1360205789,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-peotted4ituorcv5mtdk,task_subcomment,NA
+VisualEditor: Text entered at left of nowiki block replaced with a slug character (pawn) when saved,Confirmed.,1350928483,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-peotted4ituorcv5mtdk,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Author:** `orbit`
+
+**Description:**
+This used to work by using localStorage, but was removed due to problems with stringifying and parsing annotationSets.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350601440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_description,resolved
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #25)
+> I did a quick test on mediawiki.org just now using [[mw:VisualEditor:What A]]
+> and [[mw:VisualEditor:What B]]. It seems to mostly work in my browser, though
+> it inserted a non-breaking space before the header. I'll file a separate bug
+> about this.
+
+Filed as bug 58563.",1387246854,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"I did a quick test on mediawiki.org just now using [[mw:VisualEditor:What A]] and [[mw:VisualEditor:What B]]. It seems to mostly work in my browser, though it inserted a non-breaking space before the header. I'll file a separate bug about this. This bug report seems to be resolved/fixed and I'll echo others in suggesting that new bug reports be filed for cases in which copying and pasting misbehaves. Basic support appears to be implemented, however.",1387246576,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #22)
+> @Quim somewhat true, but we should also not forget that if you have a title
+> like: ""support copy and paste from other VE instances"", which basically reads
+> as a user story, that you can expect folks to judge the ticket as a user
+> story as well.
+
+Yes, I fully agree. This is what I meant in previous post when qualifying this bug report (perhaps too nicely) as far from perfect. We have a title and a one-line comment that doesn't provide any details about the feature expected.
+
+It was filed more than a year ago, when VisualEditor was basically a feature developed and used by one small team. The note to remember is that even in those circumstances reports filed must be minimally descriptive in order to set a clear expectation about the requirement to fix it.
+
+Anyway, back to the actual problem. Many more bug reports have been added to tracking Bug 33105 (thank you!) which is clearly the report that will define the quality of copy&pasting in VisualEditor.",1386861491,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(In reply to comment #21)
+> This discussion is not helpful. Please read 
+> 
+> https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquette
+> 
+> This report is far from perfect since Comment 0 since all we have to evaluate
+> is
+> 
+> ""VisualEditor: Support copy and paste from other VE instances (surfaces)""
+> 
+> Now this support is in place. You are saying that it doesn't work in certain
+> circumstances. Are there file bugs opened for the circumstances you can
+> reproduce? Currently we have
+> 
+> Bug 33105 - VisualEditor: Preserve rich text formatting when pasting from
+> internal or external sources (tracking)
+> 
+> which tracks 6 bug reports. Are the problems you are encountering covered
+> there? I didn't read the whole conversation at the wiki page, but the
+> problems
+> seemed to be related with formatting being lost from copy to paste, which is
+> what Bug 33105 is tracking. 
+> 
+> If not, please create new bugs for the cases that are missing.
+
+This discussion is not helpful? On the contrary, it has made the position of many devs a lot clearer, and the gap between them and their ""customers"", for lack of a better word. That it may have violated your Bugzilla Etiquette is the least of my concerns, and that my Bugzilla access may be taken away is your loss, not mine. 
+
+I am not saying that ""it doesn't work in certain circumstances"", I'm saying that it doesn't work in nearly all circumstances. 
+
+Are there file bugs opened for it? Don't know, don't really care. I have done your (devs) job, testing the software, and have reported at length what I encountered in those far from exhaustive tests. Perhaps now you (devs) can do what is apparently my job, and file the bugs? The arrogance of this thread and these statements may escape you, but it is unmistakeable for an outsider. 
+
+What bugs are coupled at the moment to the mythical bug 33105 (""The main work is done' Priority back to normal"")? Bug 37932 is not relevant, 48172 may be related, 48720 is not relevant, 50126 has nothing to do with my reported problems, 51725 doesn't seem to be about what the title describes, 52091 is about copying from read mode (which WhatamIDoing (WMF) claimed was not what this was about)... So no, the many problems I reported are not yet noted, or at least not coupled to 33105. 
+
+""If not, please create new bugs for the cases that are missing."" No, even though you ask nicely, but the treatment by others, the ones that should have found these problems in the first place, doesn't give me any reason to waste my time repeating the errors I reported here once again, where they will be closed at the whim of a dev anyway, sometimes fixed, sometimes not. I hope that someone who should have tested this from the WMF devs or the in-name-only QA team will be a tiny bit ashamed about all that's happened here, and file the bugs themselves. I doubt it though. It's easier to blame the messenger than to look at your own faults.",1386837060,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"@Quim somewhat true, but we should also not forget that if you have a title like: ""support copy and paste from other VE instances"", which basically reads as a user story, that you can expect folks to judge the ticket as a user story as well.
+
+We say that this is fixed because the basic technical backbone work for it has been done and that the 'content' part of it is separate tracked in it's parent ticket, but that is a very narrow definition of course when the line between user/developer is as thin as it often is on bugzilla. Such differences are bound to create friction.",1386808905,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"This discussion is not helpful. Please read 
+
+https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquette
+
+This report is far from perfect since Comment 0 since all we have to evaluate is
+
+""VisualEditor: Support copy and paste from other VE instances (surfaces)""
+
+Now this support is in place. You are saying that it doesn't work in certain circumstances. Are there file bugs opened for the circumstances you can reproduce? Currently we have
+
+Bug 33105 - VisualEditor: Preserve rich text formatting when pasting from internal or external sources (tracking)
+
+which tracks 6 bug reports. Are the problems you are encountering covered there? I didn't read the whole conversation at the wiki page, but the problems seemed to be related with formatting being lost from copy to paste, which is what Bug 33105 is tracking. 
+
+If not, please create new bugs for the cases that are missing.",1386804166,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(In reply to comment #18)
+> (In reply to comment #17)
+> > Have you actually looked at and read (and understood) the linked enwiki
+> > thread? And you can straight-faced claim that this is ""fixed""?
+> 
+> I am aware that this bug, though fixed, does not encompass the entirety of
+> what
+> we want to see. There are other bugs, many of which we are trying to fix but
+> are being distracted by people who think it's productive to edit-war on
+> Bugzilla and sling insults and threats rather than actually engaging.
+> 
+> If you had bothered to ask, rather than just assume, we could have pointed
+> this
+> out before you got so very excited. But you seem more content to scream than
+> talk, and then act surprised when we choose to spend our time more
+> productively.
+
+
+""Though fixed"". Right... 
+
+""Does not encompass the entirety of what we want to see"" is newspeak for ""actually screws up nearly every edit""?
+
+""People who think it is productive to edit-war on Bugzilla and sling insults and threats rather than actually engaging""; history has shown that complacency isn't productive with you (plural), so another approach is needed. ""Actually engaging""? The section about this bug and these problems has been open for days at enwiki, I have done ''all'' the work on it, I am the only one that actually tested this bugfix (and the rest of the deployment as well, clearly). Your ""engagement"" was a hardly relevant reply focusing on one minor aspect, but ignoring the larger picture; 
+
+""Being distracted""; well, I didn't see any positive results when you weren't being distracted either...
+
+""If you had bothered to ask""? Instead of e.g. reclosing this without even commenting? 
+
+I would be very happy if you spent your working hours productively, but the results are lacking. Of course, if you consider something that is as extremely buggy as this thing ""a fix"", then I understand your replies; I can't use them though.",1386801157,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(edit conflict)
+As for rewriting history, I reopened this here with the comment
+
+""As reported at
+[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.3F],
+this is clearly not yet fixed. Testing at MediaWiki shows that copying between
+VisualEditor pages (both within MediaWiki, and from enwiki to MediaWiki) gives
+very poor results. I have made four tests, none of them anything extreme (only
+one section header and text, no images, templates, ...), and none of them gave
+a satisfactory result.""
+
+Can you indicate where you replied to this comment and/or adressed the issues I highlighted in them? Are you seriously claiming that your comment at the Status page was a reply (never mind a sufficient reply) for problem reports like what happened [https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=837324&oldid=837321 here]? You didn't at least think about retesting this when you thought that this was ""resolved""? It still happens, FYI. And when I reopened this, you didn't think that just perhaps I didn't believe that this was resolved onwiki or offwiki? 
+
+I have pointed out countless bugs, probably more than anyone else the last half year: perhaps it is time you start taking them seriously, and consider that I may have a point, instead of blundering on blindly.",1386800636,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #17)
+> Have you actually looked at and read (and understood) the linked enwiki
+> thread? And you can straight-faced claim that this is ""fixed""?
+
+I am aware that this bug, though fixed, does not encompass the entirety of what we want to see. There are other bugs, many of which we are trying to fix but are being distracted by people who think it's productive to edit-war on Bugzilla and sling insults and threats rather than actually engaging.
+
+If you had bothered to ask, rather than just assume, we could have pointed this out before you got so very excited. But you seem more content to scream than talk, and then act surprised when we choose to spend our time more productively.",1386799884,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+Oh, my edit rights at Bugzilla? I'm scared now. What will I do without the possibility to edit Bugzilla? I imagine that if you continue to bury your head in the sand, someone will take away your job, but my imagination and reality sadly don't always match. 
+
+Have you actually looked at and read (and understood) the linked enwiki thread? And you can straight-faced claim that this is ""fixed""? This is comparable to ""operation successful, patient dead"".",1386799712,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"Your attempts to re-write history notwithstanding, Fram, this is and remained fixed. If you edit war again, I imagine someone will end up taking your edit rights away. Please stop.",1386799249,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+[https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=585650020&oldid=585645740]
+
+This thing is so not ready that it is laughable to claim otherwise. I would seriously urge you to keep this on open now, read and check all the comments (bug reports), and only then come back. This is more serious than any of you seems to understand. 
+
+THIS FIX IS ABSOLUTELY NOT READY TO BE DEPLOYED. 
+
+Read the fucking linked section, [[en:Wikipedia:VisualEditor/Feedback#Who needs bugs when you get ""fixes"" like this?]], don't bury your heads in the sand.",1386797989,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(In reply to comment #13)
+> Fram,
+> 
+> I closed this without comment because we'd already discussed this, and it
+> didn't seem like a worthwhile expenditure of my time or yours to re-hash the
+> issue when we already agreed about things. I'm sad that you think I did it
+> out
+> of malice. AGF clearly doesn't apply to your attitude. :-( Please be less
+> aggressive in future.
+
+No, I'll only get more aggressive, just read my last post at enwiki or my next post here, which will be a link to enwiki. 
+
+""We'd already discussed this""? You mean your replies at [https://www.mediawiki.org/wiki/Talk:VisualEditor/status]? No, I don't see where we actually agreed upon things. You were pinged about the enwiki discussion as well, which contained further examples. 
+
+But I don't said you did it out of malice, there are a number of other possible reasons, including (but probably not limited to) laziness, incompetence, stupidity, or a hopefully well-founded fear of losing your job after the umpteenth VE fiasco.",1386797730,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #12)
+> (In reply to comment #11)
+> > Wikifram: Sorry, I won't read through the entire
+> > https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.
+> > 3F -
+> > summarize clear testcases in Bugzilla in separate followup tickets to keep
+> > things constructive, change your passive-aggressive tone, keep this ticket
+> > closed as FIXED (as functionality exists but obviously is extremely
+> > error-prone
+> > for your testcases), and discuss high-level stuff refering to general testing
+> > on the mailing list instead. Thanks.
+> 
+> My tone isn't passive-agressive, it is simply agressive, as in thoroughly fed
+> up with the way the WMF handles things. I love it though that theDJ has
+> added a
+> ticket that blocks this one, but that you closed it again nevertheless. 
+> 
+> I am not interested in discussing things on the mailing list, I am discussing
+> it at enwiki which has the largest and least biased audience of all public
+> discussion places (compared to MediaWiki, which has a rather more slanted and
+> smaller audience, Foundation, where there are no public discussion spaces,
+> and
+> Bugzilla, which is not suited for this). 
+> 
+> Closing tickets without any explanation, like Product Manager Forrester did,
+> is passive-agressive and completely unconstructive though.
+
+Fram,
+
+I closed this without comment because we'd already discussed this, and it didn't seem like a worthwhile expenditure of my time or yours to re-hash the issue when we already agreed about things. I'm sad that you think I did it out of malice. AGF clearly doesn't apply to your attitude. :-( Please be less aggressive in future.",1386795057,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(In reply to comment #11)
+> Wikifram: Sorry, I won't read through the entire
+> https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.
+> 3F -
+> summarize clear testcases in Bugzilla in separate followup tickets to keep
+> things constructive, change your passive-aggressive tone, keep this ticket
+> closed as FIXED (as functionality exists but obviously is extremely
+> error-prone
+> for your testcases), and discuss high-level stuff refering to general testing
+> on the mailing list instead. Thanks.
+
+My tone isn't passive-agressive, it is simply agressive, as in thoroughly fed up with the way the WMF handles things. I love it though that theDJ has added a ticket that blocks this one, but that you closed it again nevertheless. 
+
+I am not interested in discussing things on the mailing list, I am discussing it at enwiki which has the largest and least biased audience of all public discussion places (compared to MediaWiki, which has a rather more slanted and smaller audience, Foundation, where there are no public discussion spaces, and Bugzilla, which is not suited for this). 
+
+Closing tickets without any explanation, like Product Manager Forrester did, is passive-agressive and completely unconstructive though. Perhaps you can lecture him on these things instead. My posts have been constructive, trying to improve Wikipedia and VE, but the format and tone hasn't been to your liking. Tough luck. If you wan to know what is wrong with this ""feature"", either read the enwiki thread or (better still) test it or get your team to test it thoroughly, but don't expect me to repeatedly seek the shabby treatment the WMF people routinely handle out to critics, by submitting new bugs about this.",1386773010,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"Wikifram: Sorry, I won't read through the entire https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.3F - summarize clear testcases in Bugzilla in separate followup tickets to keep things constructive, change your passive-aggressive tone, keep this ticket closed as FIXED (as functionality exists but obviously is extremely error-prone for your testcases), and discuss high-level stuff refering to general testing on the mailing list instead. Thanks.",1386769779,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+But can't we expect new functionality to work sometimes? ''Every'' test I have done produced errors. You could copy and paste before this ""fix"", it didn't give any layout though. With this fix, you get some layout, and a lot of botched layout.
+
+I really can't believe that any of you believe this ""fix"" is sufficiently reliable, stable, mature to be implemented in live environments. Sometimes, like here, ''not'' having a feature is a lot better than having an extremely poor attempt at one. I don't expect it to work 100% in all cases, but I do expect it to work 100% in some cases, and 95% in most cases. I don't believe this can truthfully be claimed of this. 
+
+As for ""provide exact steps to reproduce"": RTFM. I have given a link to the many tests I have done, I have described there what goes wrong. I have only received evasive or plainly incorrect answers from WMF people there. I am not going to repeat all of that here, you can just as easily follow the link I provided and try do to the same. 
+
+No thanks for your (WMF collective) help.",1386766093,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"> Why do you reclose a bug as resolved -fixed without any improvement or comment
+
+Because the functionality to copy and paste from other VE instances exists with the given patch having been merged, so this request is FIXED.
+
+This bug report never was about ""Implement functionality to copy and paste from other VE instances and make sure that it works in 100% of all cases"".
+Software always has issues. But the request in this bug report has been fixed.
+
+Hence please create separate followup bug reports on issues that don't work and provide exact steps to reproduce. Comment 7 does not have steps to reproduce.
+Thanks for your help!",1386765597,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+James Forrester, get lost. 
+
+Why do you reclose a bug as resolved -fixed without any improvement or comment, when people take the time to test this, report their findings, and show where the problems are? 
+
+The least you can do is explain why this is resolved - fixed despite my remarks; the best you can do is test this, correct it, and only then close it as fixed. 
+
+How many times will you make the same mistakes, how often will you close bugs as duplicates when they are not, as fixed when they are not, or present things as finished when they aren't even tested? Please change your approach to this or leave it to people who seem to be more competent or less defensive. You are not doing yourself, WMF, or Wikipedia a favour by your continued behaviour wrt VisualEditor.",1386749798,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+As reported at [https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.3F], this is clearly not yet fixed. Testing at MediaWiki shows that copying between VisualEditor pages (both within MediaWiki, and from enwiki to MediaWiki) gives very poor results. I have made four tests, none of them anything extreme (only one section header and text, no images, templates, ...), and none of them gave a satisfactory result.",1386577251,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"Change 86664 merged by jenkins-bot:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1385500079,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"Change 86664 had a related patch set uploaded by Esanders:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1381157521,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),*** Bug 50421 has been marked as a duplicate of this bug. ***,1373407947,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #2)
+> Also, question to the other of this ticket: Do you mean copying content from
+> VisualEditor opened in one tab to VisualEditor opened in another tab of the
+> same browser (Chrome for instance)?
+
+This is still not working:
+
+1. Open two different articles with VisualEditor.
+2. Copy or cut content from one and paste it to the other one.
+
+Format is lost. Links are lost. Not worth even trying in an average wiki page.
+
+This is a relatively frequent action when cleaning, reorganizing archiving content in articles.",1372456721,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"In order to support this functionality we need to develop some sort of annotations serializer and deserializer.
+
+Also, question to the other of this ticket: Do you mean copying content from VisualEditor opened in one tab to VisualEditor opened in another tab of the same browser (Chrome for instance)?",1351118896,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**orbit** wrote:
+
+Assigning to myself.",1350601508,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"At first the last letter is not linked but after save-reload it becomes linked.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350557280,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-7cd6puxwf2ufvh73gnet,task_description,resolved
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"(In reply to comment #6)
+> It could be actually a problem in Parosid/Serializer.
+Yup, this is a Parsoid bug, duped as such.",1363987478,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"
+
+*** This bug has been marked as a duplicate of bug 33091 ***",1363987427,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"It could be actually a problem in Parosid/Serializer.
+
+@Liangent: Could you please provide exact steps to reproduce?",1360363577,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"Apparently, not fixed.  Link trails get included in the link and not preserved.",1354217293,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,This is fixed in master.,1354217237,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"(In reply to comment #1)
+> If a link is set on a selection, need to special-case extend the annotation to
+> the first breaking character on from the selection (but only forwards) to
+> re-create how wikitext works.
+
+Remember though it's less used, there's also linkprefix, like:
+
+som[[eth]]ing -> [[eth|something]]",1350625179,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,This is because the document is out of sync with the model.  This is a CE bug.,1350585606,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"If a link is set on a selection, need to special-case extend the annotation to the first breaking character on from the selection (but only forwards) to re-create how wikitext works.",1350583959,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: Backspace can't remove Preformatted,"1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press: a Enter b Enter c
+3) Select b with the mouse, set style to Preformatted
+4) Click after c
+5) Backspace as much as you can
+
+Expected result: c, b, a disappear
+Actual result: c disappears, subsequent newline disappears, then nothing disappears anymore.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350547200,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-hbxpldwjo7edx75sbrgd,task_description,resolved
+VisualEditor: Backspace can't remove Preformatted,"Confirm similar bug in Firefox, not in Chrome or Safari - c disappears, then b looses its PRE formatting and the cursor jumps to the left side of b, then a disappears.",1350580959,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hbxpldwjo7edx75sbrgd,task_subcomment,NA
+VisualEditor: Give user some notice if their browser is not supported,"I had a look at its code and finally found the compatibility map. See gerrit 41147.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350542220,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-vezbsxzq3qktiqaner6o,task_description,resolved
+VisualEditor: Give user some notice if their browser is not supported,"We've changed our plans for how the overall integration will work, so marking this as a DUPE of 38128 now.
+
+*** This bug has been marked as a duplicate of bug 38128 ***",1368039230,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vezbsxzq3qktiqaner6o,task_subcomment,NA
+VisualEditor: Give user some notice if their browser is not supported,For browsers that support JS but don't have VE support - e.g. Opera or Iceweasel - have a notice somewhere (above the wikitext edit page?) to inform users of why they don't get the nice editor...,1350580343,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vezbsxzq3qktiqaner6o,task_subcomment,NA
+VisualEditor: Give user some notice if their browser is not supported,* bug 41147,1350542281,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-vezbsxzq3qktiqaner6o,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"**Author:** `orbit`
+
+**Description:**
+If the linmod is 
+ABC<alienInline></alienInline>DEF
+0123            4             5678
+
+When the cursor is at 5, getOffset returns 3. Programmatically setting selection to 5 will correctly place the cursor, but once again, getting the offset will return 3.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350495360,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-peieofedvf7rbivy6oia,task_description,invalid
+VisualEditor: Offset is incorrect after alienInline in Firefox,"**orbit** wrote:
+
+Yeah, fixed through various re-writes. We're going to leave aliens as ce=""false"" for standards-based browsers and we'll have to programmatically fix IE if the cursor ends up inside.",1364248074,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"Is this still an issue, or has it been fixed through the various re-writes of this area?",1360205444,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"Having contentEditable=""false"" is the original idea but unfortunately it does not work for IE (IE does not respect contentEditable=""false"" inside contentEditable=""true""). Now we are experimenting with having contentEditable=""true"" and blocking interaction with JavaScript but this approach has its downsides as well - for instance you would get a spellcheck underlines for misspelled words inside alien (majority of browsers we want to support does not respect spellcheck=""false"" inside spellecheck=""true"").
+We might end up with different approaches for different browsers (of course this is not the preferred solution due to possible high costs of maintenance and testing).",1351101271,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"(In reply to comment #1)
+> This is if aliens are contentEditable=""true"".
+Aren't they supposed to be contentEditable=""false""?",1351099924,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"**orbit** wrote:
+
+This is if aliens are contentEditable=""true"".",1350591225,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"**Author:** `hydrogen_cyanide`
+
+**Description:**
+when adding a link with Chinese characters, [[天安门广场]] in wikitext, the unicode character in the wikilink are percent-encoded, and the result i get after saving is [[%E5%A4%A9%E5%AE%2589%E9%2597%A8%E5%B9%BF%E5%9C%BA|天安门广场]]. 
+
+it seems to be linked with the browser. my browser is firefox 14.0.1. the link added by others before are also encoded. see 
+http://www.mediawiki.org/w/index.php?diff=594584
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=40004",1350493800,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_description,resolved
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,Confirmed fixed in master.,1355171819,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"(In reply to comment #5)
+> I5e1de9244d727641c10b6f0a89acc61afba7ecad looks to be the commit that will
+> resolve the dependency - it's not the whole solution and it's not done yet
+> though, so don't go and resolve this bug just yet.
+
+That change was abandoned, I45fb3206 is the successor (and has been merged).",1355166897,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"I5e1de9244d727641c10b6f0a89acc61afba7ecad looks to be the commit that will resolve the dependency - it's not the whole solution and it's not done yet though, so don't go and resolve this bug just yet.",1354842287,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"Whatever patch we make, it's going to depend on I9cb862f8498ba62ad7fc7669d70ea2b8e2eddbef and whatever additional patch comes after it to finish fixing what that didn't quite accomplish.",1354833640,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"Per bug 41152 , the Parsoid team decide to keep non-urlencoded form in <a href="" ""> so VisualEditor shouldn't send an encoded form for newly created links, at least by default (except when user manually input an encoded link target).",1353389516,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,*developer tool,1350494436,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"This does not happen in Chromium. From developer I see, in Firefox, href of a[rel=mw:WikiLink] is urlencoded in generated DOM but in Chromium it is not.
+
+The second issue is bug 40004.",1350494393,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Complex script (Indic) compatibility,"The tests mentioned in the link fail for Indic text.
+
+* Using styling icons.
+* Deleting text properly using delete / backspace keys.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://www.mediawiki.org/wiki/VisualEditor/Typing/Indic",1350483960,PHID-USER-3stle7x2whgjz463c4zz,PHID-TASK-73dsmojov4fu5z4edh64,task_description,resolved
+VisualEditor: Complex script (Indic) compatibility,Works in current version of the editor (thanks to IME support). However I will make sure to keep executing tests from this page: http://www.mediawiki.org/wiki/VisualEditor/Typing/Indic (at this moment we have problems with automating IME tests).,1360364417,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-73dsmojov4fu5z4edh64,task_subcomment,NA
+VisualEditor: Cursor jumps at the top/bottom of page after particular deletions/moves,"1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Put your cursor anywhere in simple text
+3) Press: Enter, Enter, Up
+4) Click the bullet list icon
+5) Press: Backspace, Enter, Down
+6) Problem: Cursor jumps at the bottom of the page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350451500,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-tlecjwjjkrzbeglszhlp,task_description,resolved
+VisualEditor: Cursor jumps at the top/bottom of page after particular deletions/moves,"**orbit** wrote:
+
+It appears both of these are fixed. Probably due to list fixes from Roan and cursor fixes from Inez.",1371773435,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tlecjwjjkrzbeglszhlp,task_subcomment,NA
+VisualEditor: Cursor jumps at the top/bottom of page after particular deletions/moves,"**orbit** wrote:
+
+Yeah, the second example is a different bug which has been fixed. First one is still a problem though.",1350603378,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tlecjwjjkrzbeglszhlp,task_subcomment,NA
+VisualEditor: Cursor jumps at the top/bottom of page after particular deletions/moves,"Easier way to reproduce (might be a different bug):
+
+1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Select a paragraph with the mouse
+3) Press Delete
+4) Press Up
+6) Problem: Cursor jumps to the top of the page",1350452011,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-tlecjwjjkrzbeglszhlp,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Put your cursor anywhere in simple text
+3) Press: Enter, Enter, Up
+4) Click the bullet list icon
+5) Press: Backspace, Enter, Down
+6) Surprise: A wild pawn appears! ♙
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350376800,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-jqxpftgvocz6dbwkyo26,task_description,resolved
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"Marking back as fixed as of October. If you have new bugs, please create new reports rather than re-open ones tangentially-related.",1369911007,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,This seems to be fixed already in master and on mediawiki.org.,1369874909,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,*** Bug 47687 has been marked as a duplicate of this bug. ***,1367254472,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"I think that this happens again, but only on Firefox.
+
+Here's another simple test:
+
+https://www.mediawiki.org/wiki/VisualEditor:Pawn
+
+Edit this page in VE and start moving with the arrow keys forward (right). A pawn appears in the beginning and the end of every list item.",1367079084,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,I (original reporter) confirm the fix.,1351563924,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"**orbit** wrote:
+
+All pawn problems have been resolved and pushed to mediawiki.org.",1350450678,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"Confirming bug.
+
+It also occurs in this simplified sequence:
+(1) Click anywhere on the text
+(2) Enter, enter, up
+
+(Note: Christian, Konami code is an easter egg, not a bug. It doesn't occur with normal operations. I agree the sequence enter enter up backspace enter down appears to be a little like a up up down down left right left right b a (enter) but ... the sequence Nicolas use is a legit one to edit text.)",1350380046,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"**orbit** wrote:
+
+It's like the Konami code of the Visual Editor. :) I'll take a look at this. We're specifically using a pawn for a certain trick that we need to do so that if it ever appears, we know where the problem is.",1350378115,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,Linux Ub,1350377919,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Implement keyboard command registry,"From Trevor:
+> [1] https://gerrit.wikimedia.org/r/#/c/26703/
+> [2] https://github.com/madrobby/keymaster
+> [3] https://github.com/ccampbell/mousetrap
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1349804760,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wfbwa6r6kerlfz6umih6,task_description,resolved
+VisualEditor: Implement keyboard command registry,This has been implemented now.,1353111407,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-wfbwa6r6kerlfz6umih6,task_subcomment,NA
+VisualEditor: Implement keyboard command registry,"(In reply to comment #1)
+> Change-Id: Ic69a3c70759052094aefbeab623d885f8b118e14
+
+This has been merged, keeping bug open as implementation isn't finished yet.",1351544052,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wfbwa6r6kerlfz6umih6,task_subcomment,NA
+VisualEditor: Implement keyboard command registry,Change-Id: Ic69a3c70759052094aefbeab623d885f8b118e14,1350974080,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wfbwa6r6kerlfz6umih6,task_subcomment,NA
+VisualEditor: Pre-annotations don't work if at first character of a blank line (paragraph or list item),"Go to a blank paragraph. Press Ctrl-B or the Bold button; the button depresses, but if you type the text comes out unannotated.
+
+This does not occur when the caret is at any point in the paragraph or list item which has any content in it, only when it is blank.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1349133000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-43hyj7572ppndylnp2wq,task_description,resolved
+VisualEditor: Pre-annotations don't work if at first character of a blank line (paragraph or list item),"**orbit** wrote:
+
+This is now fixed.",1349999541,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-43hyj7572ppndylnp2wq,task_subcomment,NA
+VisualEditor: Pre-annotations don't work if at first character of a blank line (paragraph or list item),"**orbit** wrote:
+
+Inez is working on pre-annotations + slug replacement. Reassigning to him.",1349896863,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-43hyj7572ppndylnp2wq,task_subcomment,NA
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,"Little hard to reproduce but has come up several times. Selecting some text, playing around with the inspector and pasting some text.
+
+Stack:
+
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null
+> ve.dm.Document.getNodeFromOffset
+> ve.ui.Toolbar.updateTools
+> ve.EventEmitter.emit
+> ve.dm.Surface.change
+> ve.ce.Surface.onPaste
+> jQuery.extend.proxy.proxy
+> jQuery.event.dispatch
+> jQuery.event.add.elemData.handle.eventHandle
+
+
+ve.dm.Document.prototype.getNodeFromOffset = function(offset) {
+        var node = this.documentNode.getNodeFromOffset(offset);
+        if (!node.canHaveChildren
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null
+        ()) {
+            node = node.getParent();
+        }
+        r
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348451460,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_description,resolved
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,This was fixed in Ia7347527e6466262e819f456404b32926fd95e34,1354054590,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_subcomment,NA
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,Pushing to next milestone as they did not make it to master by yesterday.,1352832079,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_subcomment,NA
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,"Aside from Surface.change, Surface.showSelection also has a similar problem:
+
+http://cl.ly/image/1v1h3f2M2722",1349127029,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_subcomment,NA
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,"Thought this one got fixed, but clearly not. :-)",1348507765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_subcomment,NA
+VisualEditor: Backspace deletes the wrong character,"The backspace button is sometimes deleting the character immediately ahead of the caret, instead of the character behind it. Other times, the backspace button functions fine, though I don't know which situations it works or doesn't work in. 
+
+For example, in [[VisualEditor:Test]], if one selects the place between the ""n"" and ""l"" in the word ""only"" on the third line and presses backspace, ""oly"" is displayed for a split second before changing to ""ony"".
+
+Tested on Chrome/IE9/FF15 on Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348189080,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-wg7j7pyuulwf75hox73z,task_description,resolved
+VisualEditor: Backspace deletes the wrong character,"**orbit** wrote:
+
+This was fixed by Roan.",1349896759,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wg7j7pyuulwf75hox73z,task_subcomment,NA
+VisualEditor: Backspace deletes the wrong character,"**orbit** wrote:
+
+Leaving a note for myself... This is caused when a paragraph begins with a breaknode. The breaknode is sluggable and the slug is inserted before the breaknode. I'm going to discuss with Inez next week.",1348874855,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wg7j7pyuulwf75hox73z,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348007700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-innmgpodu5aq5mgfve6a,task_description,resolved
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,Fixed in gerrit 36597.,1354574782,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,"Confirmed still a problem in master as of 2012-11-27; now is a properly-thrown error from ve.dm.Document.prototype.getNodeFromOffset:
+
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 26 is out of bounds ve.dm.Document.js:546
+ve.dm.Document.getNodeFromOffset ve.dm.Document.js:546
+ve.dm.Surface.change ve.dm.Surface.js:212
+ve.ce.Surface.onSelectionChange ve.ce.Surface.js:260
+[...]",1354059513,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,Reassigning to Trevor because Rob is out,1353115172,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,Pushing to next milestone as they did not make it to master by yesterday.,1352832078,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,Confirmed still an issue.,1350326626,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,"The correct stack error for this is:
+Uncaught TypeError: Cannot read property 'html/data-parsoid' of undefined ve.js:357
+ve.compareObjects ve.js:357
+ve.dm.Transaction.newFromContentBranchConversion ve.dm.Transaction.js:284
+ve.ui.ListButtonTool.list ve.ui.ListButtonTool.js:66
+ve.ui.ListButtonTool.onClick ve.ui.ListButtonTool.js:175
+VeUiButtonTool.tool.$.on.mouseup ve.ui.ButtonTool.js:40
+jQuery.event.dispatch load.php:3060
+jQuery.event.add.elemData.handle.eventHandle
+
+Fixed in https://gerrit.wikimedia.org/r/25974",1349134475,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,"Details:
+
+Uncaught TypeError: Cannot read property 'annotations' of undefined ve.dm.Document.js:529
+> ve.dm.Document.getAnnotationsFromOffset ve.dm.Document.js:529
+> ve.dm.Surface.change ve.dm.Surface.js:123
+> ve.ui.ListButtonTool.unlist ve.ui.ListButtonTool.js:161
+> ve.ui.ListButtonTool.onClick ve.ui.ListButtonTool.js:177
+> VeUiButtonTool.tool.$.on.mouseup ve.ui.ButtonTool.js:40
+> jQuery.event.dispatch load.php:3060
+> elemData.handle.eventHandle",1349116126,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Support templates,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=46521",1345761720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_description,resolved
+VisualEditor: Support templates,"**vladjohn2013** wrote:
+
+Hi, this project is still listed at  https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Work_on_RefToolbar 
+
+Should this project be still listed in that page? If not, please remove it. If it still makes sense, then it could be moved to the ""Featured projects"" section if it has community support and mentors.",1385912543,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"The main template editing functionality is now live. Though there are some fixes to make, I'm marking this one as closed.",1371609890,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,Change-Id: I9174ed7c9012522246a6defc859276bf36763f5b,1368646678,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"VE will support template editing quite soon (famous last words!) which will replace (alongside the TemplateData extension) pretty much all of what the RefToolbar does in terms of telling users how to use the templates and what each parameter means.
+
+We should certainly look at some accessor functionality to make it easy and obvious when in a reference to know what templates to use, but that would be in longer time.
+
+My concern is that we're currently targetting this landing in the middle of the GSoC period - too late for someone working on GSoC to react to it and extend it, and so soon into the period (and so obviously-about-to-happen) to make working on the area that VE will replace it. :-(",1364245751,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"**brassratgirl** wrote:
+
+Fair enough. Maybe the project should be ""work on citation stuff"" broadly -- not sure how to frame that :) There is plenty of work that should overlap between the reftoolbar and the VE, though; like figuring out what citation template parameters need to be used, figuring out how to work with Lua conversions, and so on. I wonder if reftoolbar could be converted into a VE plugin -- the interface is actually pretty good, no need to reinvent the wheel on handling citations.",1364245075,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"Phoebe is recommending to Work_on_RefToolbar improvements at
+http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Work_on_RefToolbar
+
+However, I wonder whether our focus shouldn't be put in VisualEditor support for the Cite templates, either out of the box or via plugin. Any advice?",1364187670,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,*** Bug 46520 has been marked as a duplicate of this bug. ***,1364167729,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"Maybe this ""Template Parameter Wizard"" is of some interest:
+
+http://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_103#Template_Parameter_Wizard",1357401262,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support categories,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345761720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-txytmd2sbsfb7usyegll,task_description,resolved
+VisualEditor: Support categories,"Now live in master, going out in tomorrow's branch.",1370485998,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Support categories,Speculatively putting this in the -27 deploy.,1368323555,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Support categories,DM support for categories in https://gerrit.wikimedia.org/r/55120,1363988651,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Support categories,Fixing test broken by 50045 https://gerrit.wikimedia.org/r/#/c/53180/,1363020764,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Support categories,https://gerrit.wikimedia.org/r/#/c/50045/,1363017773,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,"The edit summary length counter (which counts backwards from 255) counts characters, not bytes. However, in languages that heavily rely on unicode charaters, a character is usually more than a byte.
+
+When saving an edit with a summary that is accepted by the counter but with more than 255 bytes, a part of the summary is cut off.
+
+Ceterum censeo bug 4715 esse delendam.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=4715",1345637520,PHID-USER-j27ofmod3h6tzafsujyq,PHID-TASK-yhyqhzgc2jfbifybi6up,task_description,resolved
+VisualEditor: Edit summary length counter counts characters instead of bytes,"Fixed in I25e93862a39134961bf80835f46cbf531d8109e0.
+
+Though see also bug 40035.",1346892931,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,"Should use either $.fn.byteLimit (jquery.byteLimit) or $.byteLength (jquery.byteLenght).
+
+byteLength is for calculating the byte count, byteLimit is an application of that but VE might need its own implementation.",1345820343,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,"Oh, I was describing the comment for the normal editor. Yes, the comment counter for the visual editor seems wrong. Sorry.",1345640999,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,Is that a recent fix? On https://www.mediawiki.org/wiki/VisualEditor:Test it does not work as described by you (though it might be that the live version is out of date).,1345638543,PHID-USER-j27ofmod3h6tzafsujyq,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,"The db accepts 255 bytes. The php code sets the input maxlength to 250 (instead of 255) to account for some of that overhead, and then a javascript is used to adjust it to the real space.
+This is a fixed duplicate, unless it is somehow not working right.",1345637951,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Select all then replace causes 'Return' to act as 'cursor-left' in Heading mode,"To reproduce:
+
+Go to a blank VisualEditor page, click edit, change entry mode to Heading 1 (or whichever Heading mode), select all (Ctrl-A or Cmd-A), type in some content, press 'Return'.
+
+The content will appear (subject to bug 39517), but the 'Return' will cause the cursor to move to the left rather than inserting a newline. Indeed, further 'Returns' will insert newlines only to split a Heading, or when transitioning to a Paragraph or Pre-formatted block.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=39517",1345503180,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mvbvbyjoydgdze5uwazb,task_description,resolved
+VisualEditor: Select all then replace causes 'Return' to act as 'cursor-left' in Heading mode,"**orbit** wrote:
+
+I just fixed this here:
+https://gerrit.wikimedia.org/r/#/c/21397/
+
+This fix should release to mediawiki.org on September 3.",1345846642,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mvbvbyjoydgdze5uwazb,task_subcomment,NA
+VisualEditor: #<nowiki><p>http://www.wikipedia.de</p></nowiki> round-trips to #<nowiki><p><p>http://www.wikipedia.de</p></p></nowiki>,"http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&diff=569290&oldid=569131
+
+I didn't touch Line 29 at all.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1344201300,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-6xoak4ts4kf6g44ewytz,task_description,resolved
+VisualEditor: #<nowiki><p>http://www.wikipedia.de</p></nowiki> round-trips to #<nowiki><p><p>http://www.wikipedia.de</p></p></nowiki>,"This is completely fixed on my localhost. In production, it's kind of fixed but not completely, see https://www.mediawiki.org/w/index.php?title=VisualEditor%3ABug39059&diff=571884&oldid=571883 .",1344907812,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6xoak4ts4kf6g44ewytz,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode","Steps to reproduce:
+* Go to a page
+* Switch to Edit mode
+* Switch to Read mode
+* Go to a different page (e.g. ""View history"" or ""Main Page"")
+
+> Uncaught TypeError: Cannot call method 'getModel' of null
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343783700,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7fkwhekj4glhqvjvdax3,task_description,resolved
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode",Fixed a long time ago (September?). Closing.,1392750003,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode","Not fixed - that fixes a type error for undefined, not a range error.",1372388545,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode",Resolved in I13a2f02d256937b7da3aca3ad3c3404bd8f31244 by checking that the surface object was still around before using it.,1345671883,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode","Also:
+
+> Uncaught RangeError: Maximum call stack size exceeded
+> >  jQuery.extend.proxy.proxy
+> >  ve.init.mw.ViewPageTarget.onBeforeUnload
+> >  jQuery.extend.proxy.proxy
+> >  ve.init.mw.ViewPageTarget.onBeforeUnload
+> >  [..]
+> >  jQuery.extend.proxy.proxy
+> >  ve.init.mw.ViewPageTarget.onBeforeUnload
+> > jQuery.extend.proxy.proxy
+> >  ve.init.mw.ViewPageTarget.onBeforeUnload",1343802836,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode","Either onbeforeunload() needs logic that we might have already torn down the surface and not complain if that's happened, or we need to not clean up after switching from the Edit tab to the Read tab. :-)",1343785459,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"The `position` CSS attribute is allowed in wikitext and TemplateStyles CSS; it can be used to position parts of the user-generated content in places which are normally software-generated, e.g. on top of the sidebar menu or the search box. (Depending on the skin, `z-index` might or might not be also needed to achieve this.) A similar effect can be achieved with negative margins as well.
+
+This is occasionally used for vandalism, e.g. [[https://hu.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Adminisztr%C3%A1torok_%C3%BCzen%C5%91fala&diff=19674665&oldid=19670961|flipping the contents of the page]] or [[https://en.wikipedia.org/w/index.php?title=Module:Dynkin&diff=prev&oldid=669919700|obscuring everything using absolute or fixed positioning]]. This is confusing for patrollers as it also affects difflinks, but still relatively easy to revert using the undo/rollback links in recent changes / page history / etc.
+In theory it could also be used for more dangerous things, by overlaying transparent links on top of clickable areas of the interface area it's possible to hijack clicks.
+[[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5392|CVE-2012-5392]] has been reserved for this.
+
+On the other hand, positioning is a fundamental part of anything with a nontrivial amount of formatting, and is regularly used in infoboxes, amboxes and similar templates. Even the ability to break out of the content area is (ab)used for displaying various indicators on top of the page (such as a featured star, or the coordinates of the article subject). [[https://www.mediawiki.org/wiki/Help:Page_status_indicators|Page status indicators]] have been provided as a replacement for this, but the old method is still being used, so fixing this issue is blocked on finishing that migration. (See T135802#2332298 for some problems communities have with using indicators.) They are also used decoratively on user pages (e.g. to modify the site logo); breaking that probably would not be the end of the world.
+
+Some potential solutions that were dicussed in the comments:
+* Make the content are a stacking context (done in df10f03a7a28) and make sure everything else has a higher z-index (and non-transparent background, although positioning content behind a transparent interface block is harder to abuse). This would have to be done for every skin.
+* Make the content area `overflow: hidden` (and either ban `position: fixed`, or make the content area a 3D rendering context). See T40848#1913661 for more details.
+* Use [[https://caniuse.com/#feat=css-containment|CSS containment]]. Not widely supported yet though.
+
+Per T40848#1938655 the plan is to use `overflow: hidden`, first on a larger area so it's still possible to overlay the interface area where status indicators are, then on the content area once status indicator migration is finished. Status indicator blocks themselves would have to be secured (T135802). ",1343661300,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eru2tiwghisa2sl7pdsv,task_description,open
+Security: CSS positioning can be used to break out of the content area,"Given @matmarex' notes above and some additional discussion off-Phab, I'm comfortable making this bug public due to its age, its likely risk and the confounding factors described by @matmarex above.",1669060154,PHID-USER-dccizlq7dtc2zihfk7cd,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"One of the places this came up was T322702, where the proposed patch would change the behavior of legacy Vector to this [see test case in my previous comment]:
+| Before | After
+| -- | --
+| {F35735231} | {F35735298} |
+
+I left a -1 on the patch referring to this task, and I think we should find a different way to solve that (an overlay as proposed by Sam), but I'm not sure if we're still treating this as a security issue. This problem has been known for years (looks like we missed the 10th anniversary in July…), without being fixed in any other skins, and it has become newly broken in new Vector. Do we still care? (I think we should, but I'd like to hear some third opinions.)
+
+Also – this problem has been known for years, there are many references to it in public on the wikis and in other tasks, and the fact that it's secret makes it difficult to explain to people why positioning on Vector is the way it is, and easy to forget the purpose of these styles (as evidenced by new Vector losing the fix, and the proposed patch for legacy Vector). Could we make this task public?",1668030092,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"This problem came up a few times recently, so I wanted to check the current status.
+
+I am using the following as a test case, just putting it on a wikitext page:
+```lang=html
+<div style=""background: grey; position: fixed; z-index: 999999; top: 0; left: 0; bottom: 0; right: 0;""></div>
+```
+
+Except for legacy Vector, all skins deployed on Wikimedia wikis (including new Vector) are vulnerable :
+| vector | vector-2022 | minerva | monobook | timeless | cologneblue | modern
+| -- | -- | -- | -- | -- | -- | --
+| {F35735231} | {F35735233} | {F35735235} | {F35735237} | {F35735239} | {F35735241} | {F35735243}
+| Okay! (although some nav elements are transparent) | Fail  | Fail  | Fail  | Fail  | Fail (deprecated skin) | Fail (deprecated skin)
+",1668029238,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,Indeed,1629215003,PHID-USER-ctchvhisqfvk4rz7nt7d,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Yes, it used `position:fixed` ([[https://en.wikipedia.org/w/index.php?title=Template:Wbr&diff=1039070194&oldid=1039070019&unhide=1&diffmode=source|diff]]; now revdeleted). Although I doubt that limiting the image to the content area would have reduced the impact much.",1629157949,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,I don't know if the attacks today (https://www.businessinsider.com/wikipedia-pages-briefly-showed-pictures-of-swastikas-2021-8) took advantage of this security issue or not but it looks like it.,1629129396,PHID-USER-ctchvhisqfvk4rz7nt7d,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"cc @Jdrewniak who's working on a DOM restructuring in new Vector, and needs to know about this issue so he can make sure the fix for this is maintained",1601310218,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Yeah, `contain: content` will perform better than `overflow: hidden`, but has imho a different semantic purpose and meaning. Either way, it's too new to cover us from a security perspective. Either way, this is blocked in migration of indicators to use <https://www.mediawiki.org/wiki/Help:Page_status_indicators>. Last I checked, many major wikis still aren't using it (much) yet.
+
+See T40848#1938655 and T40848#1913661 for the next steps after that.",1487996779,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"https://developer.mozilla.org/en-US/docs/Web/CSS/contain describes the CSS Containment Module 3, which is supported in Chrome 52 & up. This modules offers a general way to restrict the rendering of styled content to its parent element's dimensions: `contain: content`",1485474766,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"https://developer.mozilla.org/en-US/docs/Web/CSS/contain describes the CSS Containment Module 3, which is described as supported in Chrome 52 & up. This modules offers a general way to restrict the rendering of styled content to its parent element's dimensions: `contain: content`",1485474738,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"It would probably be possible to sandbox away the content area (make sure the top skin, left skin and content are in different stacking contexts and the skin ones have positive z-index). There is no way for content in a stacking context to ever overlap content in sibling stacking contexts with higher z-index, even with `position:fixed`.",1485474759,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"It would probably be possible to sandbox away the content area (make sure the top skin, left skin and content are in different stacking contexts and the skin ones have positive z-index. There is no way for content in a stacking context to ever overlap content in sibling stacking contexts with higher z-index, even with `position:fixed`.",1485474733,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Negative margins combined with z-index can be used for similar re-dressing attacks. Example:
+
+ <div style=""margin-top: -340px; margin-left: 100px; color: red"">Hello there</div>",1485473964,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Negative margins combined with z-index can be used for similar attacks. Example:
+
+ <div style=""margin-top: -340px; margin-left: 100px; color: red"">Hello there</div>",1485473941,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Just to comment that `position:fixed` also affect extensions, such as Flow. I suggest sanitize it completely.",1453246689,PHID-USER-lprp4ui4cwnnwdkp4vyj,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I chatted with Krinkle about this bug yesterday, I think we have a clear roadmap for fixing it. We'll start by pushing method A to our sites, which is the least risk to our sites. It will affect some users who have updated their user pages to ""customize"" the wiki logo, so those users will notice as soon as we patch the cluster. Due to that, we'll need to push the fix to our sites, and release this as a mediawiki tarball update in quick succession. We'll time it so that we also alert ambassadors and tech-news, so that technical people in the movement all hear about this soon after we push it onto the site.
+
+Once that is in place, we'll work towards change C as a public followup. Wikis will need some time to finish converting indicators, and we can test ways of fixing the margin collapse issue.
+
+Before we can start this, we need to do some more testing with method A. Maybe we can use Tim's visual-diff to see what it would affect. Target of Early Feb might be realistic.",1452905131,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"In light of recent attacks, reviving this task.
+
+First of all, the current state of things has changed over the past year. Some layer security patches have been applied as part of other security bugs.
+
+Current state of Vector (using example code from T40848#425108):
+
+{F3198387}
+
+* Logo: Safe, but transparent
+* Sidebar: Safe, but transparent
+* Personal: Safe, but transparent
+* Page tabs: Safe, but transparent
+* Search: Safe, but transparent
+* Sitenotice: Not safe
+* Page name: Not safe
+
+""Safe"" refers to the visibility and click-ability of the above listed components' contents. Not their container overall. Meaning, an attacker is not able to change the link target of any of our user interface links and cannot overlap e.g. the logo. However, as you can see, the space in between the sidebar links and page tabs etc is still vulnerable because things can be layered underneath. This is why the z-index approach is only effective as an attack, not as a defence.
+
+Overflow-hidden is still the best way forward. However as mentioned, this is non-trivial because of established use cases from the community surrounding ""hacks"" that place icons outside the page content area (e.g. Geo coordinates, Featured article status, Spoken Wikipedia, etc.). This use case has been recognised by MediaWiki in 2014 in the MediaWiki 1.25 release cycle ([mw:Help:Page status indicators](https://www.mediawiki.org/wiki/Help:Page_status_indicators)). I don't know how well this has been adopted by now. I'd say we give communities a heads up through mailing lists, ambassadors and tech news and then go ahead with it.
+
+Proposed change A:
+```lang=css
+.mw-body {
+    overflow: hidden;
+}
+```
+
+Impact:
+{F3198404}
+
+This has no bad side sides (compared to status quo) and protects transparency from all currently safe areas. It still leaves page title and site notice unsafe, however. This proposal exists because of the side effects and complications with the following proposals. I'd recommend this as a transitional change to cover most of our problem space while we work on the rest.
+
+Proposed change B:
+```lang=css
+.mw-body-content {
+    overflow: hidden;
+}
+```
+{F3198430}
+
+
+This makes all listed areas safe (including the previously unsafe site notice and page title). Side effects:
+* This would break any ""top icons"" and ""indicators"" that haven't migrated from absolute-position to using `<indicator>` yet. (Because change B shrinks the overflow area from mw-body to mw-body-content, meaning content can't overlay icons and images next to the page title. An otherwise desirable change.)
+* This breaks anti-margin collapse between contentSub and elements inside the text content. This element is unfortunately within mw-body-content in most skins. It is empty by default and enjoys CSS auto margin collapse and takes up no space. Setting overflow-hidden on its container (mw-body-content) means it is no longer able to collapse its margin with the page title. As such, creating a relatively large white gap between the page title and the start of the content.
+
+Proposed change C:
+```lang=css
+#mw-content-text {
+    position: relative;
+    overflow: hidden;
+}
+```
+{F3198450}
+
+This makes all listed areas safe (including the previously unsafe site notice and page title). Side effects:
+* Breaks any indicators that haven't migrated yet (same as B).
+* This breaks margin collapse between page title (firstHeading) and page content . Even if we move out `contentSub` to be child of mw-body directly before mw-body-content, the same effect will still affect margin collapse between the first heading of the content area. We can probably avoid that by setting margin-bottom to zero for the page title.",1452824841,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"In light of recent attacks, reviving this task.
+
+First of all, the current state of things has changed over the past year. Some layer security patches have been applied as part of other security bugs.
+
+Current state of Vector (using example code from T40848#425108):
+
+{F3198387}
+
+* Logo: Safe, but transparent
+* Sidebar: Safe, but transparent
+* Personal: Safe, but transparent
+* Page tabs: Safe, but transparent
+* Search: Safe, but transparent
+* Sitenotice: Not safe
+* Page name: Not safe
+
+""Safe"" refers to the visibility and click-ability of the above listed components' contents. Not their container overall. Meaning, an attacker is not able to change the link target of any of our user interface links and cannot overlap e.g. the logo. However, as you can see, the space in between the sidebar links and page tabs etc is still vulnerable because things can be layered underneath. This is why the z-index approach is only effective as an attack, not as a defence.
+
+Overflow-hidden is still the best way forward. However as mentioned, this is non-trivial because of established use cases from the community surrounding ""hacks"" that place icons outside the page content area (e.g. Geo coordinates, Featured article status, Spoken Wikipedia, etc.). This use case has been recognised by MediaWiki in 2014 in the MediaWiki 1.25 release cycle ([mw:Help:Page status indicators](https://www.mediawiki.org/wiki/Help:Page_status_indicators)). I don't know how well this has been adopted by now. I'd say we give communities a heads up through mailing lists, ambassadors and tech news and then go ahead with it.
+
+Proposed change A:
+```lang=css
+.mw-body {
+    overflow: hidden;
+}
+```
+
+Impact:
+{F3198404}
+
+This has no bad side sides (compared to status quo) and protects transparency from all currently safe areas. It still leaves page title and site notice unsafe, however. This proposal exists because of the side effects and complications with the following proposals. I'd recommend this as a transitional change to cover most of our problem space while we work on the rest.
+
+Proposed change B:
+```lang=css
+.mw-body-content {
+    overflow: hidden;
+}
+```
+{F3198430}
+
+
+This makes all listed areas safe (including the previously unsafe site notice and page title). Side effects:
+* This would break any ""top icons"" and ""indicators"" that haven't migrated from absolute-position to using `<indicator>` yet. (Because change B shrinks the overflow area from mw-body to mw-body-content, meaning content can't overlay icons and images next to the page title. An otherwise desirable change.)
+* This breaks anti-margin collapse between contentSub and elements inside the text content. This element is unfortunately within mw-body-content in most skins. It is empty by default and enjoys CSS auto margin collapse and takes up no space. Setting overflow-hidden on its container (mw-body-content) means it is no longer able to collapse its margin with the page title. As such, creating a relatively large white gap between the page title and the start of the content.
+
+Proposed change C:
+```lang=css
+#mw-content-text {
+    position: relative;
+    overflow: hidden;
+}
+```
+{F3198450}
+
+This makes all listed areas safe (including the previously unsafe site notice and page title). Side effects:
+* Breaks any indicators that haven't migrated yet (same as B).
+* This breaks margin collapse between page title (firstHeading) and page content . Even if we move out `contentSub` to be child of mw-body directly before mw-body-content, the same effect will still affect margin collapse between the first heading of the content area. We can probably solve this by setting margin-bottom to zero for the page title.",1452824832,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"In light of recent attacks, reviving this task.
+
+First of all, the current state of things has changed over the past year. Some layer security patches have been applied as part of other security bugs.
+
+Current state of Vector (using example code from T40848#425108):
+
+{F3198387}
+
+* Logo: Safe, but transparent
+* Sidebar: Safe, but transparent
+* Personal: Safe, but transparent
+* Page tabs: Safe, but transparent
+* Search: Safe, but transparent
+* Sitenotice: Not safe
+* Page name: Not safe
+
+""Safe"" refers to the visibility and click-ability of the above listed components' contents. Not their container overall. Meaning, an attacker is not able to change the link target of any of our user interface links and cannot overlap e.g. the logo. However, as you can see, the space in between the sidebar links and page tabs etc is still vulnerable because things can be layered underneath. This is why the z-index approach is only effective as an attack, not as a defence.
+
+Overflow-hidden is still the best way forward. However as mentioned, this is non-trivial because of established use cases from the community surrounding ""hacks"" that place icons outside the page content area (e.g. Geo coordinates, Featured article status, Spoken Wikipedia, etc.). This use case has been recognised by MediaWiki in 2014 in the MediaWiki 1.25 release cycle ([mw:Help:Page status indicators](https://www.mediawiki.org/wiki/Help:Page_status_indicators)). I don't know how well this has been adopted by now. I'd say we give communities a heads up through mailing lists, ambassadors and tech news and then go ahead with it.
+
+Proposed change A:
+```lang=css
+.mw-body {
+    overflow: hidden;
+}
+```
+
+Impact:
+{F3198404}
+
+This has no bad side sides (compared to status quo) and protects transparency from all currently safe areas. It still leaves page title and site notice unsafe, however. This proposal exists because of the side effects and complications with the following proposals. I'd recommend this as a transitional change to cover most of our problem space while we work on the rest.
+
+Proposed change B:
+```lang=css
+.mw-body-content {
+    overflow: hidden;
+}
+```
+{F3198430}
+
+
+This places all listed areas in safety (including the previously unsafe site notice and page title). Side effects:
+* This would break any ""top icons"" and ""indicators"" that haven't migrated from absolute-position to using `<indicator>` yet. (This shrinks the overflow area from mw-body to mw-body-content, meaning content can't overlay icons and images next to the page title. An otherwise desirable change.)
+* This breaks `<div id=""contentSub"">` anti-margin collapse. This element is unfortunately within mw-body-content in most skins. It is empty by default and enjoys CSS auto margin collapse and takes up no space. Setting overflow-hidden on its container (mw-body-content) means it is no longer able to collapse its margin with the page title. As such, creating a relatively large white gap between the page title and the start of the content.
+
+Proposed change C:
+```lang=css
+#mw-content-text {
+    position: relative;
+    overflow: hidden;
+}
+```
+{F3198450}
+
+This places all listed areas in safety (including the previously unsafe site notice and page title). Side effects:
+* Breaks any indicators that haven't migrated yet (same as B).
+* This breaks content heading anti-margin collapse. Even if we move out `contentSub` to be child of mw-body directly before mw-body-content, the same effect will still affect margin collapse between the first heading of the content area (e.g. wikiPreview's ""Preview"" in the screenshot, or something like the heading atop the sandbox page). This creates an even bigger gap. Something that could be worked around by targeting the first mw-heading and cancelling its top margin manually. I'd like to avoid this as it significantly complicates future changes.",1451854681,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,">>! In T40848#1449889, @csteipp wrote:
+> Krinkle mocked up the interface if we also had overflow: hidden, and the result visually (imo) looks much less like a security issue and more like vandalism,
+> 
+>> If we had done overflow-hidden, the page would've looked like this: http://i.imgur.com/TrPeYxG.png
+>> Instead of the current: http://i.imgur.com/MFN8cBo.png
+> 
+> @Krinkle, can you post the style updates that you used to get that result? It looks as Trevor said, setting overflow:hidden isn't quite enough.
+
+It turns out that result was a lucky match between screen height and the exact code used by that piece of vandalism. It used `width: 100%; height: 100%;` which means in an overflow scenario with sufficient page content and a short window, it wouldn't extend far enough to peak out.
+
+Ignoring `position: fixed` for a second (see T123811 for that), `overflow: hidden` is enough and addresses this issue entirely for both Vector, MonoBook and any other skin. The core patch will affect modern skins using the `mediawiki.skinning` base; other skins can adopt the same in their own CSS.
+
+As for `position: fixed`. That can be reliably addressed by giving the content its own rendering context using `transform: translateZ(0);`. See http://jsfiddle.net/Loezmm7y/4/. However that impacts rendering performance. Supported in 90%+ of browsers per http://caniuse.com/#feat=transforms2d (not in IE<=8).
+
+However I suggest we simply forbid `position: fixed` in the Sanitizer. I don't see any valid use case for it. Fixed position is bound to rendering context (= window by default) and can always peek out if allowed. The original issue here was absolute position and relative position.",1452902490,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,">>! In T40848#1449889, @csteipp wrote:
+> Krinkle mocked up the interface if we also had overflow: hidden, and the result visually (imo) looks much less like a security issue and more like vandalism,
+> 
+>> If we had done overflow-hidden, the page would've looked like this: http://i.imgur.com/TrPeYxG.png
+>> Instead of the current: http://i.imgur.com/MFN8cBo.png
+> 
+> @Krinkle, can you post the style updates that you used to get that result? It looks as Trevor said, setting overflow:hidden isn't quite enough.
+
+It turns out that result was a lucky match between screen height and the exact code used by that piece of vandalism. It used `width: 100%; height: 100%;` which means in an overflow scenario with sufficient page content and a short window, it wouldn't extend far enough to peak out.
+
+Ignoring `position: fixed` for a second, `overflow: hidden` is enough and addresses this issue entirely for both Vector, MonoBook and any other skin. The core patch will affect modern skins using the `mediawiki.skinning` base; other skins can adopt the same in their own CSS.
+
+As for `position: fixed`. That can be reliably addressed by giving the content its own rendering context using `transform: translateZ(0);`. See http://jsfiddle.net/Loezmm7y/4/. However that impacts rendering performance. Supported in 90%+ of browsers per http://caniuse.com/#feat=transforms2d (not in IE<=8).
+
+However I suggest we simply forbid `position: fixed` in the Sanitizer. I don't see any valid use case for it. Fixed position is bound to rendering context (= window by default) and can always peek out if allowed. The original issue here was absolute position and relative position.",1436812682,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(documenting my email to security@, and Timo's writeup)
+
+Last week Jerry Hoff from WhiteHat Security posted https://twitter.com/jerryhoff/status/617340137689755653?s=03.
+
+> The page the Twitter user in question was viewing is:
+> https://en.wikipedia.org/wiki/Thomas_Sowell
+> 
+> This page uses Template:Hlist in the infobox, which was changed briefly to include Lua Module ""Dynkin"" (edit made by an experienced user):
+> https://en.wikipedia.org/w/index.php?title=Template:Hlist&diff=prev&oldid=669920021
+> 
+> Which in turn was vandalised to include the red box (edit made by an anonymous user):
+> https://en.wikipedia.org/w/index.php?title=Module:Dynkin&diff=prev&oldid=669919700
+
+Because https://gerrit.wikimedia.org/r/#/c/178086/ was deployed last December, on Vector
+
+> So all that happened is a big red box was displayed *behind* the interface menus.
+
+For monobook, much of the interface was obscured. Fixing this issue on monobook seems unlikely.
+
+Krinkle mocked up the interface if we also had overflow: hidden, and the result visually (imo) looks much less like a security issue and more like vandalism,
+
+> If we had done overflow-hidden, the page would've looked like this: http://i.imgur.com/TrPeYxG.png
+> Instead of the current: http://i.imgur.com/MFN8cBo.png
+
+@Krinkle, can you post the style updates that you used to get that result? It looks as Trevor said, setting overflow:hidden isn't quite enough.",1436807288,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,">>! In T40848#1122583, @Anomie wrote:
+> Hiding overflow will also hide content when someone with a very wide screen resolution makes something that won't fit for people with lower resolutions. Horizontal scrollbars suck, yes, but is just cutting it off necessarily better?
+
+This task is about elements placing themselves outside the content area to overlap interface elements. Capturing overflow doesn't mean it has to be inaccessible. `overflow: auto;` (e.g. scroll when overflow) would work just as well. The scrollbar would be on the content area instead of on the window. Unless scrolled to the bottom of the page the user wouldn't notice much difference in behaviour. Except that the excess content would be correctly displayed on a white background instead of against the outer the skin body (which is grey in Vector).
+
+Example: https://codepen.io/Krinkle/debug/eNEwYo.
+
+The only difference is that (on desktop) the sidebar would stay in view. On mobile the sidebar may be out of view depending on the viewport and how far away you scroll (virtual depth is applied). This is making its way to desktop browsers as well.
+
+http://www.quirksmode.org/mobile/viewports.html
+http://www.androidpolice.com/2015/01/09/chrome-beta-v40-new-zoom-behavior-makes-fixed-headers-scrollable-less-aggravating/",1434565219,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Hiding overflow will also hide content when someone with a very wide screen resolution makes something that won't fit for people with lower resolutions. Horizontal scrollbars suck, yes, but is just cutting it off necessarily better?",1426533532,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Giving content its own rendering context (e.g. using `translateZ(0)`) would also restrict `position: fixed;`. It's similar to ""visual"" security provided by iframes. Perhaps `overflow: hidden;` and translate can be used together.
+
+Note that mw-indicators has been introduced in MediaWiki core and projects can now migrate templates such as Coordinates, Featured article etc. to using that instead. Which, to my knowledge, was the last remaining (valid) use case for allowing position: absolute; outside the content area. Which means, once migration period settles, we are free to apply `overflow: hidden;`. We may want to additionally add z-indexes in various places, but we should hide overflow no matter what.",1426532220,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Turns out applying overflow: hidden to .mw-body doesn't solve for fixed positioned content[1].
+
+I looked at various techniques, including using backface-hidden which works in certain cases on certain browsers, but nothing appears to be reliable.
+
+The only safe approach I can see is to combine z-indexing with obscuring content behind UI areas using positioned divs that fully block out the UI area and have opaque backgrounds[3].
+
+[1] https://en.wikipedia.org/wiki/User_talk:Bababa67
+[2] http://jsfiddle.net/w119kpwL/
+[3] http://jsfiddle.net/Loezmm7y/1/",1421358403,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"The Vector skin has been moved into a separate repository and the element is now targeted as `.mw-body-content` instead of `#bodyContent`.
+
+Part of task has been resolved with T76965.",1417984117,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,*** Bug 24667 has been marked as a duplicate of this bug. ***,1415456361,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I see you've found the issue with the navigation tabs in monobook. Those rely on the content being on top because they are longer than they have to be.
+
+Note that these are longer on purpose because of relative font-size differences on different browsers. I see you shortened them to arbitrary values 0.2em and 0.3em.
+
+Presumably, after you moved the content behind the tabs and removed the z-index from the tabs, you trimmed those values until they no longer stick out, but not so short that they leave a gap and would no longer touch the content container.
+
+As you can guess by now, those em values would expand to different sizes and most certainly in one of the browsers Monobook supports this will now leave a gap (as if they're shorter), or cause an ugly border to stick it (as if they're longer).",1399246331,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15282
+Patch for Monobook
+
+Changed it to use #column-one > *, which seems to work.
+
+**Attached**: {F9561}",1399068340,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to Chris Steipp from comment #58)
+> Which seems to fix the issue, but would break some of the widgets that
+> position elements outside of the content area. Do those usually work with
+> monobook?
+
+Yes, they do. And since this would break common things like enwiki's ""featured article"" star, I recommend against doing this.
+
+A better fix would be to apply the z-index to the contents of div#column-one rather than to the whole thing; you could either target them individually by id or by targeting something like ""#column-one > *"" (do we still care about browsers old enough to not support "">""?).",1399048997,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I wasn't seeing a great way to fix monobook with z-index=0, so I used another fix that Krinkle had also mentioned
+
+#bodyContent {
+	position: relative;
+	overflow: hidden;
+}
+
+Which seems to fix the issue, but would break some of the widgets that position elements outside of the content area. Do those usually work with monobook? I looked at https://en.wikivoyage.org/wiki/Clearwater with Vector and Monobook, and the map widget is gone in monobook.",1399046601,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Thanks Bartosz,
+
+Testing this on my dev system, the monobook patch doesn't seem to be working right. Since div#column-one covers over the top of everything in the content area, it prevents clicking on any forms / links in that area. So it breaks all special pages.
+
+I'm testing it on master as of this afternoon, so might be a recent change?",1398982508,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15223
+Patch for Modern
+
+**Attached**: {F9560}",1398601963,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15222
+Patch for Monobook
+
+I ended up just guessing better padding values for the tabs to allow them to always have a higher z-index than content.
+
+At first I tried to properly calculate the necessary heights and to not mix pixels and ems, but it required changing the code considerably (mostly to keep IE6 from breaking). The end result was not really prettier than what we have now, and definitely not something appropriate for a security patch.
+
+//attachment 0003-SECURITY-Monobook-Secure-interface-layer-from-page-c.patch ignored as obsolete//",1398601909,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15221
+Patch for CologneBlue
+
+**Attached**: {F9559}",1398601483,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15220
+Patch for Vector
+
+Patch from attachment 14981 no longer applies, here's a rebased version.
+I'm going to work on patches for other skins today (finally; sorry for the delay).
+
+I'm using this very simple test case:
+  <div style=""background: red; position: fixed; z-index: 999999;
+  top: 0; left: 0; bottom: 0; right: 0;"">&nbsp;</div>
+…and verifying that all of the elements listed by Krinkle in earlier comments (logo, sidebar, personal, tabs, search, sitenotice, page name) are visible and clickable (unless any of them are missing in given skin, of course).
+
+**Attached**: {F9558}",1398594547,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to Bartosz Dziewoński from comment #51)
+> My personal opinion is that we should either WONTFIX this bug
+
+I disagree. The advantage to fixing this bug, even if it's not perfect with respect to the TOC and other in-content ""chrome"", is that when some vandal tries to take advantage of it then people don't have to know about manually editing the URL to include ""?action=edit"" to be able to fix it.",1397053662,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"For Monobook, we could make the top border of content area be actually generated by <div id=""p-cactions""/> or one of its descendants, which should make applying Krinkle's idea reasonably straightforward. (Or, someone could sit down with pen and paper and actually calculate what exactly is the height of the tabs, with all of the em sizings applied, which would let us avoid z-index hacks.)
+
+Modern and CologneBlue should also be straightforward to adjust.
+
+I could do that (when I find the time, probably the soonest could be this weekend), but I'm not entirely sure if the fix is really worth the effort: we would still have important UI bits interspersed with the content (table of contents, section edit links), and the whole exercise is rendered pointless if such easily exploitable elements remain. (Moving them out of content would require a pretty big redesign of all skins, including third-party ones.)
+
+My personal opinion is that we should either WONTFIX this bug (I actually thought that this ""bug"" was almost common knowledge…) or combine Krinkle's solution with something that would also protect inter-content chrome (possibly the z-index limiting mentioned earlier, if we can't come up with anything less nasty – I'm all out of ideas). But I can prepare the skin patches anyway.",1396994010,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"MatmaRex, Brad had noticed specifically that I07223ba4 made fixing Monobook more difficult.",1396472315,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Adding MatmaRex, in case he can help out with the Monobook and Cologne Blue skins",1396472047,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 14983
+Screenshot of test case (on master, with patch)
+
+**Attached**: {F9557}",1396302249,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 14982
+Screenshot of test case (on master, before patch)
+
+**Attached**: {F9556}",1396302212,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 14981
+Patch for Vector skin
+
+//attachment security-vector-zindex.patch ignored as obsolete//",1396302192,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Okay, updated the patch one more time with a check. A few things have changed in the Vector skin since last time.
+
+Test case:
+
+<div style=""
+ position: absolute;
+ top: -180px; left: -10%;
+ z-index: 99999;
+ width: 120%; height: 400px;
+ background: rgba(0, 0, 255, 0.8);
+ outline: 1px solid orange;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid blue;
+"">[[File:Transparent.gif|4000x4000px|link=//example.org|Click]]</div>
+<div style=""position: absolute; bottom: 0; text-align: center;"">Navigation/Search</div>
+</div>
+
+<div style=""
+ position: absolute;
+ top: -170px; left: -190px;
+ z-index: 99999;
+ width: 240px; height: 640px;
+ background: rgba(0, 255, 255, 0.8);
+ outline: 1px solid red;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""position: absolute; bottom: 0; text-align: center;"">Logo/Sidebar</div>
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid green;
+"">
+[[File:Transparent.gif|350x350px|link=//example.org|Click]]
+</div>
+</div>
+
+
+Current mediawiki/core.git@master:
+
+== Vector skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Not safe
+- Tabs:       Not safe
+- Search:     Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+After my patch:
+
+== Vector skin ==
+- Logo:       Safe
+- Sidebar:    Safe
+- Personal:   Safe
+- Tabs:       Safe
+- Search:     Safe
+- Sitenotice: Safe
+- Page name:  Safe",1396302130,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,So I'd recommend we move ahead with just the Vector fix.,1396301184,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Monobook can't get fixed, it is currently relying on insecure z-index overrides. It needs to be refactored in general.
+
+I think we can do so in public without exposing or explaining this bug though, but it's more than a bug fix, we basically need to re-make the same visual layout with a different It requires a few changes to the html as well, which always make this more complicated with regards to caching and backwards compatibility while the html cache rolls over but stylesheets are on a separate request that will roll over separately (earlier).",1395013208,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to Chris Steipp from comment #41)
+> Timo, any chance you were able to get Monobook fixed?
+
+Timo: ping?",1394632548,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #39)
+> Created attachment 13731 [details]
+> Patch for Vector skin
+> 
+> As for Monobook, can't take the same approach due to it purposely having the
+> navigation behind the content (because of the overflow of the tabs). So we'll
+> need to take a different approach there (or, preferably, refactor it to not
+> use
+> that weird nesting).
+
+Timo, any chance you were able to get Monobook fixed? It would be great to get this fixed on the cluster once fundraising's big push is done in Jan. I think Monobook is the only non-default skin that many admins use.
+
+Also adding Jared so UX is aware of this.
+
+//attachment bug38848.patch.diff ignored as obsolete//",1388098293,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"By far the easiest way to solve this problem for all skins is to apply ""overflow: hidden;"" to #mw-content-text. That is both skin agnostic (the element is output by the page output handler around only the wiki page content and nothing else) and water tight.
+
+However the difference is that that doesn't just move content to its own layer, it also restricts its boundaries. Meaning, the skin interface isn't just on top of any content sticking out, the content sticking out will be invisible (cropped) at the border of the content area.
+
+However I don't think that is feasible at the moment due to the large number of icons and semi-genuine use cases we don't yet provide natively (e.g. article quality icons, coordinates, interproject links etc.).
+
+So for now the approach we've been taking seems fine (although this time it'll actually work), which is ensuring layer security. That way none of the skin interfaces are affected (e.g. logo, personal links etc.) however any empty space outside the wikipage content that isn't covered by interface components  (e.g. the space between logo and personal links, space between logo and first sidebar link etc. anything that is colored purple or blue in the screenshot) could still be hijacked, though it is much less frighting in those cases. And that can only be prevented if we completely crop content. Which we can't do until we drop support for positioning of icons such as Featured Article, and Coordinates to the top right of the article (just outside the content area, next to the title).
+
+As crazy as it sounds, we can actually drop support for that relatively soon because we only have to drop support for icons positioned there from wikitext. Most wikis don't actually do that anymore, instead they give those templates a css classes, and move the icons to the ""proper"" place in the DOM outside the content area through site javascript. Though that is somewhat evil too, it is what we'd do in an extension as well. And from javascript, any changes uncontrollable anyway and must be presumed safe (due to user right restrictions).",1383881287,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 13731
+Patch for Vector skin
+
+As for Monobook, can't take the same approach due to it purposely having the navigation behind the content (because of the overflow of the tabs). So we'll need to take a different approach there (or, preferably, refactor it to not use that weird nesting).
+
+//attachment bug38848.patch.diff ignored as obsolete//",1383880586,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"
+Meanwhile, a year later.
+
+Updated the test html to 'cover' all skins (mostly increasing dimensions and offset).
+
+!!! If testing on production wiki, please *DO NOT SAVE* but use preview as we don't want to hand the below hack on a plate for someone to find and abuse.
+
+Content:
+
+<div style=""
+ position: absolute;
+ top: -180px; left: -10%;
+ z-index: 99999;
+ width: 120%; height: 400px;
+ background: rgba(0, 0, 255, 0.8);
+ outline: 1px solid orange;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid blue;
+"">[[File:Transparent.gif|4000x4000px|link=//example.org|Click]]</div>
+<div style=""position: absolute; bottom: 0; text-align: center;"">Navigation/Search</div>
+</div>
+
+<div style=""
+ position: absolute;
+ top: -170px; left: -190px;
+ z-index: 99999;
+ width: 240px; height: 640px;
+ background: rgba(0, 255, 255, 0.8);
+ outline: 1px solid red;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""position: absolute; bottom: 0; text-align: center;"">Logo/Sidebar</div>
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid green;
+"">
+[[File:Transparent.gif|350x350px|link=//example.org|Click]]
+</div>
+</div>
+
+
+Current mediawiki/core.git@master:
+
+== Vector skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Not safe
+- Tabs:       Not safe
+- Search:     Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+== Monobook skin ==
+- Logo:       Safe
+- Sidebar:    Not safe
+- Personal:   Safe
+- Tabs:       Not safe
+- Search:     Safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+== Modern skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Not safe
+- Tabs:       Not safe
+- Search:     Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+Monobook has weird z-index overrides all over the place. For example the
+following have an overriden z-index that made them safe for this test:
+
+- li a.selected (the selected tab in the tabs)
+- #p-search (portlet for search in the sidebar)
+- #p-logo (portlet for the logo in the sidebar)
+- #p-lang (porlet for interwiki links in the sidebar)
+
+But the other tabs or the tab bar itself, and the other portlets or the sidebar
+itself were all not safe.
+
+
+After my patch:
+
+
+== Vector skin ==
+- Logo:       Safe
+- Sidebar:    Safe
+- Personal:   Safe
+- Tabs:       Safe
+- Search:     Safe
+- Sitenotice: Safe
+- Page name:  Safe
+
+Tested to confirm proper compatibility with jQuery UI and VisualEditor dialogs and overlays etc. (e.g. personal portlet stays behind the overlay that mutes the page, as it should).",1383880423,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,Krinkle: Do you plan to rework your patch in comment 36 (as you obsoleted it)?,1378758027,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Comment on attachment 11395
+Updated combined patch for 1.21, with Brad's fixes.
+
+Obsoleting this patch set. Also I see you fell into the same clean up trap as I did for Monobook. The z-indexes there for the tabs are needed to 1) display the tabs underneath #content (since they are taller than they should be), and 2) make the selected tab go on top so it overlaps the top border of #content.",1375079731,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Meanwhile, a year later.
+
+Updated the test html to 'cover' all skins (mostly increasing dimensions and offset).
+
+!!! If testing on production wiki, please *DO NOT SAVE* but use preview we don't want to hand the below hack on a plate for someone to abuse
+
+Location: http://mw.local.dev/wiki/Sandbox?action=edit
+Content:
+
+<div style=""
+ position: absolute;
+ top: -180px; left: -10%;
+ z-index: 99999;
+ width: 120%; height: 270px;
+ background: rgba(0, 255, 255, 0.8);
+ outline: 1px solid red;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid blue;
+"">
+[[File:Transparent.gif|4000x4000px|link=//example.org|Click]]
+</div>
+Navigation/Search overlay
+</div>
+
+<div style=""
+ position: absolute;
+ top: -170px; left: -190px;
+ z-index: 99999;
+ width: 170px; height: 340px;
+ background: rgba(0, 255, 255, 0.8);
+ outline: 1px solid red;
+ font-size: 2em;
+ text-align: center;
+"">
+Logo overlay
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid blue;
+"">
+[[File:Transparent.gif|350x350px|link=//example.org|Click]]
+</div>
+</div>
+
+
+Current mediawiki/core.git@master:
+
+== Vector skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Safe
+- Tab bar:    Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+== Monobook skin ==
+- Logo:       Safe
+- Sidebar:    Not safe
+- Personal:   Safe
+- Tab bar:    Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+There are weird z-index overrides all over the place. For example the following have an overriden z-index that made them safe for this test:
+
+- li a.selected (the selected tab in the tabs)
+- #p-search (portlet for search in the sidebar)
+- #p-logo (portlet for the logo in the sidebar)
+- #p-lang (porlet for interwiki links in the sidebar)
+
+But the other tabs or the tab bar itself, and the other portlets or the sidebar itself are all not safe.
+
+== Modern skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Not safe
+- Tabs:       Not safe
+- Search:     Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+
+
+Working on a revised patch set now based on a more solid approach.",1375079605,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,It does. It's just been a little lower priority.,1372373729,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Chris, does this still need to happen?",1372369898,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #19)
+> In monobook, the left-hand menu is still covered up. I wasn't able to fix that.
+
+Set position:relative on .portlet?
+
+(In reply to comment #28)
+> * Sitenotice: Fail (wikipage remains on top)
+
+Since the Sitenotice is inside the #content area, that's going to be a bit difficult.",1366310500,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11403
+Screenshot of attachment 11395 fix in Modern
+
+**Attached**: {F9555}",1353518782,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11402
+Screenshot of attachment 11395 fix in Monobook
+
+**Attached**: {F9554}",1353518768,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11401
+Screenshot of attachment 11395 fix in Vector
+
+//attachment ba11395-vector.png ignored as obsolete//",1353518754,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #27)
+> Created attachment 11395 [details]
+> Updated combined patch for 1.21, with Brad's fixes.
+> 
+> Updated patch. Should apply with `git am` with current master
+
+
+Given the test of comment #2 on my local wik (with different top-offsets depending on the skin)i:
+> Location:
+> https://www.mediawiki.org/w/index.php?title=Project:Sandbox&action=edit
+> 
+> <div style=""
+> position: absolute;
+> top: -178px;
+> left: 0;
+> z-index: 2;
+> width: 100%;
+> height: 195px;
+> background: rgba(0, 255, 255, 0.2);
+> text-align: center;
+> ""> Breaks Nav </div>
+> 
+> 
+> <div style=""
+> position: absolute;
+> top: -120px;
+> left: -180px;
+> z-index: 2;
+> width: 150px;
+> height: 150px;
+> background: rgba(0, 255, 255, 0.2);
+> text-align: center;
+> ""><div style=""position: absolute; -webkit-user-select: none; -moz-user-select:
+> none; user-select: none;"">Goes to
+> Toolserver.org</div>[[File:Transparent.gif|150x150px|link=//toolserver.org|Go
+> to the Main Page, or... Tooserver.org?]]</div>
+
+
+I confirm that this patch does not effect the visual appearance of Vector, Monobook and Modern. Now as for the effectiveness in removing the ability of wikipage content to overtake the interface:
+
+Vector: Improvement
+* Logo: Success (unclickable: wikipage layered behind)
+* Tabs: Success (wikipage layered behind)
+* Personal: Success (wikipage layered behind)
+* Sitenotice: Fail (wikipage remains on top)
+
+Monobook: Improvement
+* Logo: Success (unclickable; wikipage layered behind)
+* Tabs: Success (wikipage layered behind)
+* Personal: Success (wikipage layered behind)
+* Sitenotice: Fail (wikipage remains on top)
+
+Modern: Improvement
+* Sitename/logo: Fail (clickable; wikipage layered on top)
+* Tabs: Success (wikipage layered behind)
+* Personal: Success (wikipage layered behind)
+* Sitenotice: Fail (wikipage remains on top)
+
+So overal an improvement, but some areas still vulnerable.
+
+//attachment 38848m_20121120.patch ignored as obsolete//",1353518615,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11395
+Updated combined patch for 1.21, with Brad's fixes.
+
+Updated patch. Should apply with `git am` with current master
+
+//attachment 38848m_20121120.patch ignored as obsolete//",1353434225,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11363
+Combined patch for 1.19 branch
+
+Tested with REL1_19
+
+//attachment 38848m-119.patch ignored as obsolete//",1353010821,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11362
+Combined patch for vector, monobook, modern, and Brad's fixes - 1.21
+
+Just tested on 1.21-master, and works / fixes the issue
+
+//attachment 38848m.patch ignored as obsolete//",1353010048,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11282
+Patch to fix monobook inactive tabs
+
+(In reply to comment #19)
+> One part that may cause problems is Monobook had a z-index of 2 for
+> div#content, which I set to 0. I wasn't sure why it was set to 2, but I'm
+> guessing there was a reason, so we may need to bring the other elements to a
+> z-index of 2 or higher.
+
+It's for the tabs. Monobook has the links in #p-cactions overlap the top edge of div#content. Then it uses z-index 0 on inactive tabs and z-index 3 on active tabs to get the effect of the active tab looking like ""part of"" div#content. See screenshots such as [[File:Wp-main-page-20100513-monobook.png]] to see this in action. But there would be no point in raising div#content back to z-index 2 in monobook because we'd just have to make #p-cactions z-index 2 or higher too.
+
+It looks like we can achieve the same effect in another way, though. See patch.
+
+//attachment 0001-Fix-monobook-inactive-tab-appearance.patch ignored as obsolete//",1351782105,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #21)
+> Using CVE-2012-5392 to track this
+
+Took me a while to figure out what this is (horrible website)
+
+Future reference: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5392",1351226207,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11245
+Patch for Modern skin
+
+After the email about supporting skins today, I thought we should try and support a patch for modern and Colognblue. This patch for modern has been working well on my localhost, and tested on beta.
+
+//attachment modern.patch ignored as obsolete//",1351224348,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,Using CVE-2012-5392 to track this,1351202383,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Krinkle, I think you said you had some comments on the patch. I'll try and get it tested with browserstack too, but if you think this looks ok, I'd like to get this patched in production and rolled into the 1.19.3 release this week.",1350358309,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11157
+z-index:0 for Vector & Monobook
+
+This seems to work for me, but I would appreciate more eyes on it. It prevents a div in the content body from blocking the edit button and the footers. In monobook, the left-hand menu is still covered up. I wasn't able to fix that.
+
+One part that may cause problems is Monobook had a z-index of 2 for div#content, which I set to 0. I wasn't sure why it was set to 2, but I'm guessing there was a reason, so we may need to bring the other elements to a z-index of 2 or higher.
+
+//attachment zindex_css.patch ignored as obsolete//",1349279915,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #16)
+> Would position relative (with no additional top/left/right/bottom properties)
+> work ? Or does it have to be position absolute?
+
+Trevor mentioned this, and iirc, he said it was any position except static
+
+(In reply to comment #17)
+> So as being ineffective and problematic towards non-evil markup, I'd say lets
+> drop wgMaxZIndex and go with setting z-index: 0; on the page container and
+> treat it as a skin vulnerability as opposed to a wikitext vulnerability.
+
+I completely agree. Draft deleted.
+
+Krinkle, is setting a z-index: 0 on each of the skins something you can help with? Like I said, I was able to do it for Vector/Monobook, but I wasn't able to get it working with many of the other ones.",1346971089,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I'd recommend dropping the wgMaxZIndex implementation (as drafted in I92b2821c3).
+
+I'd prefer this to be a fix for the skins (something that custom skins would have to implement themselves) as opposed to implementing it in the wikitext parser. Doing it in the parser/sanitizer complicates things and can cause weird issues because it sets an arbitrary limit that:
+
+1) doesn't fully kill the vulnerability
+2) also kills unrelated markup that doesn't go beyond the page container
+
+For instance things could easily be stacked above 50 (or whatever value) and not be outside the body content. Because in order to go outside the body content I'd have to use absolute or relative position. z-index on itself is harmless.
+
+Also, to go outside the page container, one doesn't even need a high z-index value at all. As demonstrated in comment 2 z-index: 2; can do the trick already. So to actually cover it we'd need the z-index: 0; restriction on the page container still. And when doing that, we won't need wgMaxZIndex.
+
+So as being ineffective and problematic towards non-evil markup, I'd say lets drop wgMaxZIndex and go with setting z-index: 0; on the page container and treat it as a skin vulnerability as opposed to a wikitext vulnerability.",1346970000,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #15)
+> I tested this out for some other skins, and many do not work with this, because
+> the menu section does not have a position attribute, so the stacking is not
+> applied to effectively prevent this bug. 
+
+Would position relative (with no additional top/left/right/bottom properties) work ? Or does it have to be position absolute?",1346969553,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I tested this out for some other skins, and many do not work with this, because the menu section does not have a position attribute, so the stacking is not applied to effectively prevent this bug. So, to make this method work, we would need to also add some positioning to the rest of the skin, which is beyond my css skills.
+
+I'd like to get a security fix rolled out before the end of the month, and include a patch for this. Krinkle (or maybe Trevor), would that be possible?
+
+As a compromise, we could just roll this out for Vector and Monobook, which would be simple.",1345480433,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I tested setting z-index: 0 directly on the bodyContent div in the vector skin, and it seems to prevent the clickjacking in Chrome, Opera and Firefox for everything outside of the article body. Obviously it can take over the article, but it seems to prevent overlaying the menus.",1345165993,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #12)
+> Positive integers can start with ""+"":
+> 
+> <http://www.w3.org/TR/CSS2/syndata.html#numbers>
+> 
+> Otherwise I think it will work, as long as the entire user interface is
+> elevated to some z-index larger than $wgMaxZIndex. IIRC, IE imposes a fairly
+> low limit on the maximum z-index, like 2^15 or 2^16, so it should be tested if
+> the user interface is raised to a high z-index.
+> 
+> However, I have an idea that I think will work without changing the z-index of
+> any user interface elements, and without limiting the z-index values in user
+> supplied CSS. 
+> 
+> Z-index values are only valid within a single ""stacking context"". Applying
+> z-index: 0 to the #bodyContent div would establish a separate stacking context
+> for the content area, and should prevent any descendant from overlapping
+> anything with z-index: 1 or higher in the UI.
+> 
+> http://tstarling.com/stuff/z-index-context.html
+> 
+> I tested it in Firebug on Wikipedia and it seems to work.
+I played with this in Firebug on mediawiki.org, adding the following rules:
+
+#bodyContent { z-index: 0; }
+#toc { position: absolute; left: -17em; top: -12em; z-index: 50 }
+
+The latter attempts to move the TOC such that the [hide] link clickjacks part of the logo. This works without the z-index:0 rule and breaks with it.
+
+CC Trevor because this is about CSS magic and Krinkle is on vacation.",1344990922,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Positive integers can start with ""+"":
+
+<http://www.w3.org/TR/CSS2/syndata.html#numbers>
+
+Otherwise I think it will work, as long as the entire user interface is elevated to some z-index larger than $wgMaxZIndex. IIRC, IE imposes a fairly low limit on the maximum z-index, like 2^15 or 2^16, so it should be tested if the user interface is raised to a high z-index.
+
+However, I have an idea that I think will work without changing the z-index of any user interface elements, and without limiting the z-index values in user supplied CSS. 
+
+Z-index values are only valid within a single ""stacking context"". Applying z-index: 0 to the #bodyContent div would establish a separate stacking context for the content area, and should prevent any descendant from overlapping anything with z-index: 1 or higher in the UI.
+
+http://tstarling.com/stuff/z-index-context.html
+
+I tested it in Firebug on Wikipedia and it seems to work.",1344989381,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Thanks Roan.
+
+Change is now here https://gerrit.wikimedia.org/r/#/c/19651/2",1344984488,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #9)
+> (In reply to comment #8)
+> > Created attachment 10958 [details]
+> > Strip user styles with high zindex
+> > 
+> Because the second \s is non-optional and not repeated, it looks like
+> ""z-index:30000"" and ""z-index:    30000"" would fool the regex.
+Confirmed that this is the case.
+
+Also, an invalid z-index leads to the entire style attribute being stripped, which isn't very nice. It would be nicer to just strip the rule (or clamp the value maybe). This probably requires using preg_replace_callback() instead.
+
+//attachment zindex.patch ignored as obsolete//",1344978120,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #8)
+> Created attachment 10958 [details]
+> Strip user styles with high zindex
+> 
+Because the second \s is non-optional and not repeated, it looks like ""z-index:30000"" and ""z-index:    30000"" would fool the regex.
+
+//attachment zindex.patch ignored as obsolete//",1344977890,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 10958
+Strip user styles with high zindex
+
+Patch to Sanitizer's checkCss() to strip out css that has a z-index over a site's defined $wgMaxZIndex.
+
+Sites can determine appropriate $wgMaxZIndex values, and skins can set a z-index over this value for important items (menus, buttons, etc).
+
+//attachment zindex.patch ignored as obsolete//",1344885003,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(links: bug 8679, bug 9526)",1344047096,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"After thinking through some more abuses of this, it makes me nervous having this out there.
+
+How much would break if we:
+1) Add a fairly high z-index on whatever container is holding the main menu links
+2) Prevent setting inline z-indexes to anything equal to or greater than or menu's z-index",1344014431,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Related bugs: 8679 and 9526, which both use inline styles to do unexpected things with the user experience.
+
+The comforting thing is that if this becomes a common vector for vandals, we can easily block specific cases with an abusefilter rule.
+
+That being said, have we considered having different css/style rules for different namespaces? So we could prevent position styles in articles, but not templates or user pages?
+
+Or adding !important and high z-indexes to the navigation areas?",1343936081,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I'm afraid so, yes.
+
+Both on their user page (e.g. to stylize the heading of their user name or the Wikipedia logo), as well as in templates on actual articles. E.g. to create graphs and such (the latter is much less evil since the absolute positioning there is only relative to the wrapper div of the template - this I'd say is genuine and to-be-supported use of absolute css).
+
+Usage of position absolute outside the page wrapper (e.g. to overlap #firstHeading, which some users do on their User page to make it look nicer, or to overlap the #p-logo with something they think looks cooler - again only on their user page)",1343762312,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,Thanks for the demo Krinkle. So editors are actively using position styles on wiki?,1343762080,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Both position relative and position absolute are very common. Especially because CSS absolute positioning is relative to the closest parent that has relative positioning.
+
+So a user can have an element with relative position and in there another element with absolute position and negative values, and still be within the page viewport.
+
+As for linkability, there is no way to execute javascript within the session from there (since there is no way to do that anywhere in wikitext, regardless). However it is possible to link to an external link.
+
+
+Location: https://www.mediawiki.org/w/index.php?title=Project:Sandbox&action=edit
+
+<div style=""
+position: absolute;
+top: -118px;
+left: 0;
+z-index: 2;
+width: 100%;
+height: 100px;
+background: rgba(0, 255, 255, 0.2);
+text-align: center;
+""> Breaks Nav </div>
+
+
+<div style=""
+position: absolute;
+top: -120px;
+left: -180px;
+z-index: 2;
+width: 150px;
+height: 150px;
+background: rgba(0, 255, 255, 0.2);
+text-align: center;
+""><div style=""position: absolute; -webkit-user-select: none; -moz-user-select: none; user-select: none;"">Goes to Toolserver.org</div>[[File:Transparent.gif|150x150px|link=//toolserver.org|Go to the Main Page, or... Tooserver.org?]]</div>",1343757488,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"It is certainly possible to cover useful buttons and sections of the page with a div, which could prevent users from being to click a button or a link (DoS, effectively).
+
+<div style=""position:absolute; top:-118px; left:0px; z-index:2; width: 100%; height: 100px""> Breaks Nav </div>
+
+However, there should *not* be a way to get the click to do anything that is attacker controlled-- run javascript, or navigate to an external link. If either of those becomes possible, then this becomes a major security issue. Otherwise, this is probably more of an annoyance, that we can easily revert if we encounter it.
+
+We could disable setting position, or only allow position:relative with positive values and within certain limits. I'm not sure how common it is for editors to use div positioning, so we would need to research that. I'll try and find someone on the UI team to comment.",1343755934,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+"VisualEditor: Pressing 'Esc' in Save-dialog should exit saving, return to editor","[From a user report.]
+
+""If the user press ESC while the save popup is open, it should just return to the edit mode, but it does nothing unless we click in the [x] button.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1343084880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bw4tf22xsrw2meuuvmyr,task_description,resolved
+"VisualEditor: Pressing 'Esc' in Save-dialog should exit saving, return to editor",Fixed in https://gerrit.wikimedia.org/r/16782,1343341026,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-bw4tf22xsrw2meuuvmyr,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,"Arrow keys move the caret in the opposite direction in RTL environment. Simple textareas in browsers do this correctly, so as much as possible, the Visual Editor should rely on the browsers' behavior.
+
+See https://www.mediawiki.org/wiki/VisualEditor/Internationalization_requirements .
+
+Related: bug 38000.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342868640,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6xsc6lb6uvcf633e32tb,task_description,resolved
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,Merged and will go out in wmf6.,1369780070,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,Related URL: https://gerrit.wikimedia.org/r/65703 (Gerrit Change Ic01e110a5e6094cd275327a2e8cea90c900f1bd1),1369693188,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,"@Amir: Your guess it correct, we are capturing keyboard events (keydown to be specific) and then moving cursor forward (right arrow) or backward (left arrow). We implemented it in this way because it let's us block user from moving cursor inside a non-editable element (alien node - like rendered template for instance). It seems that we will have to work a little bit more on this, I will try to just let browser handle cursor movement but then ""fix"" it in JavaScript if it ends up in wrong place.",1343170407,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,"Try it with text that is actually RTL :)
+
+Without looking at the code, I guess that you capture keypress events, and if it's a right arrow, you move it one character forward, and vice versa. But for RTL right is backward etc.
+
+Simply reversing the direction for RTL text will not be enough, because an LTR word in the middle of an RTL paragraph will mess things up. And that's just one of the many complications. It took Gecko and Webkit developers years to get it right and both still have bugs.
+
+The best way to handle arrow events is to simply let the browser handle them.",1343080494,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,"**orbit** wrote:
+
+Amir, I'm pretty sure that this should be working properly in the new contenteditable-based editor. Can you double-check for me? Here's my RTL demo: http://framezero.com/work/wikia/VisualEditor/demos/ve/index.php",1343079723,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Build out support for Monobook,"The VisualEditor extension currently only works with the Vector skin. It should work with other skins such as Monobook.
+
+From [mediawiki/extensions/VisualEditor.git] / VisualEditor.hooks.php (<https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=blob;f=VisualEditor.hooks.php;h=e43fef59dd678ba5309f2335829dd6fe1e041a2d;hb=4fea35acd451c939a522ab7a4d7bd13e4ac95e76>):
+
+---
+class VisualEditorHooks {
+	/**
+	 * Adds VisualEditor JS to the output if in the correct namespace.
+	 *
+	 * This is attached to the MediaWiki 'BeforePageDisplay' hook.
+	 *
+	 * @param $output OutputPage
+	 * @param $skin Skin
+	 */
+	public static function onBeforePageDisplay( &$output, &$skin ) {
+		global $wgTitle;
+		if (
+			// Vector skin supported for now.
+			$skin->getSkinName() === 'vector' &&
+			(
+				// Article in the VisualEditor namespace
+				$wgTitle->getNamespace() === NS_VISUALEDITOR ||
+				// Special page action for an article in the VisualEditor namespace
+				$skin->getRelevantTitle()->getNamespace() === NS_VISUALEDITOR
+			)
+		) {
+			$output->addModules( array( 'ext.visualEditor.editPageInit' ) );
+		}
+		return true;
+	}
+---
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1341350580,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-kxjmckaitcfmwxa44pgn,task_description,resolved
+VisualEditor: Build out support for Monobook,"(In reply to comment #4)
+> I've added support for Monobook in Ia39e034229204ae5f1f70dce5d74c6c4db42277b
+
+Awesome. Thank you, Trevor!",1345771635,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,The primary request here was monobook support - I've renamed the bug and am now closing it.,1345745134,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,"I've added support for Monobook in Ia39e034229204ae5f1f70dce5d74c6c4db42277b
+
+This doesn't mean ""all"" skins are supported, so I am not sure I should close the bug, but for most purposes this is sufficient.",1345745065,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,"(In reply to comment #2)
+> Enhancement, not bug. Resource issues are non-trivial. To discuss as part of
+> the product strategy.
+
+I've found the cost of all the noise switching back and forth between bug and enhancement to far outweigh any benefit. I don't care what you call this ticket and neither does nearly any other ticket filer.
+
+The VisualEditor extension should work with non-Vector skins. (And the fact that it doesn't is getting in the way of power-users, a good number of whom use Monobook.)
+
+You can classify the request as whatever you'd like or just disable the stupid categorization altogether. Nobody cares.",1341351777,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,"Enhancement, not bug. Resource issues are non-trivial. To discuss as part of the product strategy.",1341351016,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,Bumping the importance of this as it's annoying the shit out of me when trying to play with the extension.,1341350663,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","More for the wishlist...
+
+Need a dialog to manipulate image properties (size, alignment, border, caption).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1341271020,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-mxnglgs5g63joubkufdc,task_description,resolved
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Moving all of these out into their own bugs and closing this:
+
+(In reply to James Forrester from comment #18)
+> * media thumbnail over-ride: not yet done, low priority
+
+Now bug 62669.
+
+> * alignment (baseline/middle/…): not yet done, low priority
+
+Now bug 62670.
+
+> * need a ""set as 'upright'"" size value setting (default to 75%)
+
+Now bug 62671.
+
+> * link: not yet done, low priority
+
+Now bug 62672.
+
+> Non-image things:
+> * page (for multi-page items, e.g. PDFs): not yet done, low priority
+
+Now bug 62673.
+
+> * noicon (for multimedia items): not yet done, low priority
+
+Now bug 62674.
+
+
+> * start: not yet done, low priority
+
+Now bug 62675.
+
+
+> * thumbtime: not yet done, low priority
+
+Now bug 62676.
+
+
+> * merging with the (future) gallery editing dialog: not yet done
+
+Now bug 62677.
+
+
+> * CE-surface fixes to make TMH's media items display correctly: not yet done
+
+Now bug 62678.
+
+Closing this one as an unhelpful semi-tracker.",1394835371,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Updated list of not-yet-done items from comment #16:
+
+* which media item is shown (but keeping other options): bug 51033
+* media thumbnail over-ride: not yet done, low priority
+* alignment (baseline/middle/…): not yet done, low priority
+* need a ""set as 'upright'"" size value setting (default to 75%)
+* link: not yet done, low priority
+
+Non-image things:
+* page (for multi-page items, e.g. PDFs): not yet done, low priority
+* noicon (for multimedia items): not yet done, low priority
+* start: not yet done, low priority
+* thumbtime: not yet done, low priority
+
+Other things:
+* preview of media item: bug 52461
+* remove from page button: bug 51764
+* merging with the (future) gallery editing dialog: not yet done
+* CE-surface fixes to make TMH's media items display correctly: not yet done",1394082712,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 105247 merged by jenkins-bot:
+Add image type change to media edit dialog
+
+https://gerrit.wikimedia.org/r/105247",1391820350,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","A quick review of the settings functionality for the media dialog right now:
+
+* which media item is shown (but keeping other options): bug 51033
+* media item type (thumb, frame, frameless): underway in gerrit 105247
+** media thumbnail over-ride: not yet done, low priority
+* border: not yet done, low priority
+* location (left/right/centre/non): bug 51293, done
+* alignment (baseline/middle/…): not yet done, low priority
+* size: mostly done; needs some fixes
+** need a ""set at default size"" button
+** need a ""set as 'upright'"" value setting (default to 75%)
+** logic rule changes when image is frame not thumb (no upscaling of image)
+* link: not yet done, low priority
+** Possibly needs to know licence to avoid linking in violation of licence, e.g. CC-BY?
+* alt text: done
+* caption: done
+
+Non-image things:
+* page (for multi-page items, e.g. PDFs): not yet done, low priority
+* noicon (for multimedia items): not yet done, low priority
+* start: not yet done, low priority
+* thumbtime: not yet done, low priority
+
+Other things:
+* preview of media item: bug 52461
+* remove from page button: bug 51764
+* merging with the (future) gallery editing dialog: not yet done
+* CE-surface fixes to make TMH's media items display correctly: not yet done",1391658048,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 105247 had a related patch set uploaded by Jforrester:
+[WIP] Add image type change to media edit dialog
+
+https://gerrit.wikimedia.org/r/105247",1391657049,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 105098 merged by jenkins-bot:
+Adding alternate text to media edit dialog
+
+https://gerrit.wikimedia.org/r/105098",1391655563,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 103193 merged by jenkins-bot:
+Changing image size in MWMediaEditDialog
+
+https://gerrit.wikimedia.org/r/103193",1390445864,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 105098 had a related patch set uploaded by Jforrester:
+Adding alternate text to media edit dialog
+
+https://gerrit.wikimedia.org/r/105098",1389677199,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 103193 had a related patch set uploaded by Jforrester:
+Changing image size in MWMediaEditDialog
+
+https://gerrit.wikimedia.org/r/103193",1389677179,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 92767 abandoned by Mooeypoo:
+[WIP] Add further image attribute editing to the media dialog
+
+Reason:
+Split into separate dependent commits
+
+https://gerrit.wikimedia.org/r/92767",1388787172,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",*** Bug 53937 has been marked as a duplicate of this bug. ***,1383759270,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 92767 had a related patch set uploaded by Jforrester:
+[WIP] Add further image attribute editing to the media dialog
+
+https://gerrit.wikimedia.org/r/92767",1383759257,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","We have another request for ""alt text"" support in the media dialog.  As this is an accessibility concern for the visually impaired in our reader base, it's an important option to offer (the dialog will have to explain this field, and why it's desirable).",1375634468,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 74082 had a related patch set uploaded by Jforrester:
+Base for media settings size widget.
+
+https://gerrit.wikimedia.org/r/74082",1374168350,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",*** Bug 51126 has been marked as a duplicate of this bug. ***,1373481769,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",Just adding another urge for alt.text at English Wikipedia. :),1372976750,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",*** Bug 50709 has been marked as a duplicate of this bug. ***,1372900959,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Caption editing is now done and will be live in a few minutes; setting size, alignment, type and border will come later.",1371603773,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",Speculatively putting into the next release.,1368323694,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Example: Android 2.x browser (tested Kindle Fire), iOS < 5 browser.
+
+The editor initializes, but since there's no ContentEditable support you can't actually type anything. In iOS 4.3.2 simulator initialization never quite completes...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1341270660,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_description,resolved
+VisualEditor should not try to initialise if no ContentEditable support,Related URL: https://gerrit.wikimedia.org/r/67082 (Gerrit Change Ic38992e04b5f3932cf18f2dfc217cd733196efb8),1370436939,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,Related URL: https://gerrit.wikimedia.org/r/66993 (Gerrit Change Idc5f4a23a2709264d869a91d00873c4e187bc470),1370370120,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"@Ed Feature tests:
+
+* Engine is ECMAScript5 compliant.
+
+  Avoid testing things like Object.create or Function#bind which can easily
+  be polyfills (and asserting the difference between native and polifill can
+  be tricky). Assert that strict mode works. 
+
+  supportsStrictMode = ( function () {
+      ""use strict"";
+      function x() {
+          return this;
+      }
+      return x() === undefined;
+  }() );
+
+  Perhaps you could even take out x() and just return this === undefined.
+  Though that appears to work and seems more straight forward, I see all
+  patterns out there use a function inside. Let's figure out if its needed
+  and only do it if needed.
+
+* Browser supports ContentEditable.
+
+  DOMElements have all supported properties defined in their default state.
+  e.g. all input fields have property 'placeholder' (empty string as value
+  by default).
+  supportsPlaceholder = 'placeholder' in document.createElement( 'input' );
+
+  For content editable we don't need to create an element, we can just
+  use document.body as test target since it works body as well. 
+
+  supportsContentEditable = 'contentEditable' in document.body;",1369526726,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,Setting milestone per James.,1368554214,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,*** Bug 41149 has been marked as a duplicate of this bug. ***,1368039230,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Having discussed this with Timo just now, ua-parser has now moved even further away from being appropriate for client-side use, so here's the new plan:
+
+* We will have some basic up-front tests of browser functionality - contentEditable, localStorage, etc.
+
+If the browser is detected to not have this, we will fail with an error message along the lines of ""Sorry, this browser does not support some of the core technologies used in VisualEditor and so it will not load. <Oh well>""
+
+* Then we have two lists - a known-good list (i.e., currently the IE9+/Firefox10+/Chrome16+/Safari5+ list) and a known-bad list (e.g., Android<=2, Opera) If the browser is in the former, VE loads; if in the latter we will fail with an error message along the lines of ""Sorry, this browser is known to have serious issues with VisualEditor and so it will not load. <Oh well>""
+
+If we reach this point (seems to have the technologies, not a known-bad or a known-good), we give the user a choice about whether to proceed - ""We do not know if this browser works perfectly with VisualEditor; do you wish to proceed? <OK> <Cancel>"" - and set the answer in localStorage.",1367944191,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"I submitted a pull request to ua-parser just now.
+
+Once they merge it I'll add that as a new module and let VisualEditor use that instead. I should probably keep jquery.client in core so that extensions using that can continue to do so (maybe as a wrapper though, to avoid repetition).",1349120569,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"I'll see if its possible to extend jQuery.client. Otherwise we may want re-consider replacing this module with something more solid.
+
+There's two major parsers I know work very well and have been proven to work by ""the mass"":
+
+* browscap [1] (supported by PHP's get_browser functionality)
+  - Currently PHP only, and the source is a hugely inefficient .ini file that isn't very future proof. Not the kind of thing we'd want to port to javascript, not to mention the huge manifest.
+
+* ua-parser [2] (forked from 
+ - Currently in many languages, including javascript. Though nodejs, we'll have to export the yaml file to JSON and figure out if there is any nodejs modules we need to substitute.
+
+
+[1] http://browscap.org | https://browsers.garykeith.com/ | https://github.com/GaretJax/phpbrowscap
+[2] https://github.com/tobie/ua-parser | https://github.com/tobie/ua-parser/tree/master/js",1348076962,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Timo, can you work on getting Android support into jQuery.client so we can close this out?",1347302938,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Now that bug 38857 is fixed, this is easy... Or is it?
+
+This is what I got from $.client.profile() on Jon's phone which runs Android 4.04:
+
+{""name"":""safari"",""layout"":""webkit"",""layoutVersion"":534,""platform"":""linux"",""version"":""4.0"",""versionBase"":""4"",""versionNumber"":4}
+
+Maybe we could enhance jQuery.client so it can cope with Android user agent strings.",1345673017,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"According to http://stackoverflow.com/questions/1882205/how-do-i-detect-support-for-contenteditable-via-javascript you can check for the contentEditable property in the DOM, but this gives false positives on iOS and Android versions where the engine supports it but provides no way to edit things.
+
+So possibly a test combined with a blacklist for Android browser < 3 and iOS < 5?",1341271526,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Is there a nice way to test for CE functionality automatically, or do we need to create a whitelist-of-doom?",1341270976,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,"(Save needs to be selected as default action?) Very irritating for those of us that don't use the mouse much when we edit. ;-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50897",1340916180,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2egq3hlgvj5ljxkovvce,task_description,declined
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,This was deliberately removed by bug 40034.,1374613842,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,"**ignatzmice.wiki** wrote:
+
+Was going to file a new bug, but this popped up as a possible duplicate. I notice that rather than doing *nothing*, it does create a newline in the edit summary box, which is then transformed into a space on saving. I too use Monobook, not that I image it makes a difference.",1373849913,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,"Agree with comment #4, this is still an issue, and it's now more problematic due to a higher number of experienced users being used to hit 'Enter' to save.
+
+Has Rob's code (committed almost a year ago) been merged?",1373532785,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,"**KilliondudeWP** wrote:
+
+This is an issue and has been for at least a few weeks. I'll note that I use Monobook in case that is relevant.",1373411137,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,*** Bug 38735 has been marked as a duplicate of this bug. ***,1343347540,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,Fixed in https://gerrit.wikimedia.org/r/16782,1343340991,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,*** Bug 38039 has been marked as a duplicate of this bug. ***,1340916283,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination,"When copy-pasting from the VisualEditor into LibreOffice 3 (tested 3.5.2.2 on Ubuntu 12.04), links are copied with the target URL of the wiki page being edited plus ""#"" on the end, eg <https://www.mediawiki.org/wiki/VisualEditor:Welcome#>
+
+This doesn't happen when copy-pasting from the view mode.
+
+See also bug 33239 comment 6 -- if we retain the original href and use JavaScript to suppress regular clicking, I think this would lead to more natural cut-n-paste behavior with other apps.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33105",1340905200,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-qttnmog5m4ro2nv4m5sn,task_description,resolved
+VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination,This is now fully correct; closing as fixed.,1361834067,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qttnmog5m4ro2nv4m5sn,task_subcomment,NA
+VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination,"This is a bit better now, but not quite there yet. External links now point to the correct destination, but internal links don't, they just contain the name of the page in the href.",1352597120,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qttnmog5m4ro2nv4m5sn,task_subcomment,NA
+VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination,Add see-also to bug 33105 which wants rich copy-and-paste - this is distinct but related.,1340930523,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qttnmog5m4ro2nv4m5sn,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Once basic image support is included, and there's some integration with UploadWizard or similar, it should be possible to initialize the upload tool with drag-and-dropped image files.
+
+This would allow simply dragging one or more files from your file manager over to the spot in the document where you want them, ending up with a single image or gallery at the end.
+
+Compared to {T40030}, needs to be able to initialize the wizard with given File objects received via a drop.
+
+**See also**: {T11133}",1340904000,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-duiplk7fkjkz4nppzcgi,task_description,resolved
+VisualEditor: Initiate file upload by drag-and-drop,@Aklapper Understood. ,1540797650,PHID-USER-cb53pyjz3ccu7fvgd7m2,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"@Thedonquixotic : This task is resolved (see top bar). If something does not work for you, see https://www.mediawiki.org/wiki/VisualEditor/Portal for where to discuss issues. Thanks!",1540785805,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Hey, just curious if this feature is actually in Visual Editor or not? I can't seem to find it, or figure out how to use it. ",1540769669,PHID-USER-cb53pyjz3ccu7fvgd7m2,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Change 246185 merged by jenkins-bot:
+Media upload: Initialize booklet before setting file on drag drop
+
+[[https://gerrit.wikimedia.org/r/246185]]",1444827161,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Change 246185 had a related patch set uploaded (by Prtksxna):
+Media upload: Initialize booklet before setting file on drag drop
+
+[[https://gerrit.wikimedia.org/r/246185]]
+",1444816024,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Change 244331 merged by jenkins-bot:
+Media upload: Initiate upload process on image drop
+
+[[https://gerrit.wikimedia.org/r/244331]]",1444760995,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Change 244331 had a related patch set uploaded (by Esanders):
+Media upload: Initiate upload process on image drop
+
+[[https://gerrit.wikimedia.org/r/244331]]
+",1444249087,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"VE's drop handler needs a list of allowed file extensions on the target remote wiki. You can get this via the API – http://commons.wikimedia.org/w/api.php?action=query&meta=siteinfo&siprop=fileextensions – but we'll need T114765 before we can scrape it. It also/instead needs a list of MIME types; not sure if that's possible in MW, sadly.",1444183790,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"(In reply to comment #3)
+> If using UploadWizard itself is not feasible at this stage, a lightweight
+> uploader UI similar to what's available on mobile might be good -- this does
+> a cross-origin POST to Commons for the upload, so we don't have to leave the
+> page or open an iframe or anything weird like that.
+
+Opening up an iframe isn't too hard for VisualEditor (every dialog is one already), but re-using UploadWizard (and refactoring it so this is possible) seems like a much better solution than writing our own.
+
+There's wider product questions about whether to allow uploading to local, or just to Commons (given that relatively few wikis allow local uploads, and that those are only meant to be used in special circumstances, making it too easy to upload copyvios/etc. and having licence proliferation might be the wrong approach).",1373477183,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"I think roughly what we'd want to happen is something like this:
+
+* user drag-and-drops an image file from Explorer/Finder/file manager into the document.
+** if possible, show a rectangular placeholder box around the cursor position while dragging
+* on drop, save the cursor position so we know where in the document to insert...
+* ...and spawn the UploadWizard or similar interface, handing it the file we've received to start the actual upload process, select a license, save a description etc.
+* At the end of the UploadWizard, instead of showing you the link to the file we transition straight back to the editor...
+* ...and you can then modify the positioning/sizing/caption/etc with the VisualEditor's existing dialogs.
+
+
+If using UploadWizard itself is not feasible at this stage, a lightweight uploader UI similar to what's available on mobile might be good -- this does a cross-origin POST to Commons for the upload, so we don't have to leave the page or open an iframe or anything weird like that.",1373477004,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Request for similar functionality made at MediaWiki today:
+
+Hi, I see a number of requests for the ability to easily upload local images (from our local HD to Wiki I guess). I'd like to add my vote for this request. How is this progressing? How would it work? Simply browse for an image locally and then go through the captioning, sizing, aligning, positioning, licensing — then upload for it to appear immediately in the desired location with also the hi-res and info immediately in Wikimedia Commons?
+
+Robertwhyteus (talk)‎20:27, 9 July 2013",1373423973,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,This is not on schedule for before the next big release; noting as such.,1365636093,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","Our traditional editor toolbars have buttons to insert a [[File:Foo.png]] or similar, but not that would help you with the actual editing process.
+
+A button that launches the UploadWizard -- possibly uploading to Commons -- and ends with inserting the image(s) into the article would be a big leap forward.
+
+--------------------------
+
+User journey:
+# User clicks on ""insert media""
+# In the dialog, user clicks on ""upload new""
+{F176539}
+
+ //… or 'User drags a file into the editor', see T40031 //
+
+3. Dialog is launched
+{F176534}
+
+4. User confirms that the media file is theirs, and accepts that it will thus be under the default licence (CC-BY-SA-3.0); file starts uploading with a progress bar (indeterminate for now)
+
+{F176541}
+
+ //… or user is directed to Special:Upload if local uploads are available.//
+> ""To upload a file which cannot be freely re-used, please use the __restricted form__.""
+
+ //… or user is directed to Special:UploadWizard on Commons.//
+> ""To upload a file created by someone else, or under a different licence, please use the __advanced form__.""
+5. User enters a title.
+{F176543}
+
+6. User enters a description (default in the user's interface language, with a control to set the language to something else).
+{F1000}
+
+7. User optionally over-rides the date of creation from 'today'.
+{F1000}
+
+8. User optionally enters (Commons) categories.
+{F176551}
+
+9. User clicks ""Publish and Insert"", and file is un-gated on the stash and published on Commons, and inserted locally as a `thumb|right` (or `|left` on RTL) at default size with the description as the caption (if the description is in the content language).
+{F176555}
+
+ //… or user clicks ""Cancel Publishing"" and the file is left in the stash for garbage collection, never published.//
+
+10. Done.",1340903820,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_description,resolved
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","Change 240116 merged by jenkins-bot:
+Add image upload tab to media dialog
+
+[[https://gerrit.wikimedia.org/r/240116]]",1444182861,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","Change 240116 had a related patch set uploaded (by Esanders):
+[WIP] Image uploading
+
+[[https://gerrit.wikimedia.org/r/240116]]
+",1442950783,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","@nirzar, @matmarex, @marktraceur, please clarify if I've missed or misunderstood anything.",1439369004,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","Notes from `#wikimedia-multimedia`, with @matmarex and @marktraceur //(logs are edited to keep only relevant messages)//:
+
+{P1870}
+
+***
+
+**tl;dr**
+Our first step is to make a tool that can upload a file from enwiki to commons with a default license. The local vs remote and license choices can come later. 
+The commons specific subclass of [[https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.Upload.Dialog|mw.Upload.Dialog]] can go to [[https://www.mediawiki.org/wiki/Extension:CommonsMetadata|CommonsMetadata]]. The `mw.CommonsUpload` model will take care of the `{{information}}` template on Commons. 
+This new code could live in VE-mediawiki, or in core, after naming it `MediaRepoUpload` instead of `CommonsUpload`.
+",1439368960,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","I had a discussion with @nirzar, on how we can integrate the [[https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.Upload.Dialog|upload dialog in core]] with VisualEditor. @nirzar explained to me the expectations of the user when in VE, and how a simplified workflow would work best. @marktraceur was talking about a bare bones version for the first iteration too, more in my next comment. In simplifying the workflow, we wanted to cut some details currently required to upload, but aren't sure if it is  acceptable from a product or legal point of view—
+
+1. Isolate global and local information to avoid cognitive overload.
+2. Pick sane license defaults and don't give the user too much choice
+3. Auto-categorize the image to— //from-VE//, or some such, making it easier to find these images on Commons.
+4. Hide where the image is going (local wiki vs commons). Inform user later that the image went to commons — //Thanks for uploading to Commons. [[https://commons.wikimedia.org/wiki/Commons:Welcome|Learn More]].//
+
+***
+
+When uploading through VE there would be two entry points—
+1. An //Add more// button in the Insert Media (//Media settings//) dialog //[1]//.
+2. Dropping a file into VE.
+
+The first option would lead to the first pane of the upload dialog //[2]//. The second option would jump straight to the second pane //[3]//. For VE we'll always skip the last, //Usage// pane and directly insert the image on the page. 
+
+@nirzar wanted the local editing to be more inline in VE, but, it currently opens up a dialog //[4] (this isn't exactly in the purview of making upload work with VE, but deserves mentioning)//. We need to decide whether we want to automatically open up this dialog or let the user initiate the action.
+He has also requested User Research for this workflow, but I don't know much about that yet.
+
+***
+
+1. F1359538
+2. F1359743
+3. F1360116
+4. F1360346
+",1439368885,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","//Comments from the pitch meeting last week//
+* Show a preview of the image in the dialog? Easier in VE but useful for WE.
+* Licensing imposition info and user click-through
+** Let them choose? Danger of choice turning into what we have with UW?
+* Build a preview whilst you go through the steps – show where the caption will be rendered, anticipate the final result.
+* Description and caption. If we’re doing it in an article, do users have that distinction? Hard to provide them as separate things?
+** Separation between local information and global information? Do local activities after the ‘publish’ step?
+** Show caption as part of preview?
+** Just use caption as description?
+** Call out //“how it will appear in the article”// vs //“how it will appear to re-users”//?
+** Each step may have a different license, need to split them by those lines
+* Split licences – possibly CC0 for description/etc. but CC-BY-SA-3.0 [or whatever] for the image and possibly CC-BY-SA-3.0 or CC-BY-SA-4.0 or PD or … for the caption (and may be different)
+
+",1439364784,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","//Comments from the pitch meeting last week//
+* Show a preview of the image in the dialog? Easier in VE but useful for WE.
+* Licensing imposition info and user click-through
+** Let them choose? Danger of choice turning into what we have with UW?
+* Build a preview whilst you go through the steps – show where the caption will be rendered, anticipate the final result.
+* Description and caption. If we’re doing it in an article, do users have that distinction? Hard to provide them as separate things?
+** Separation between local information and global information? Do local activities after the ‘publish’ step?
+** Show caption as part of preview?
+** Just use caption as description?
+** Call out “how it will appear in the article” vs “how it will appear to re-users”?
+** Each step may have a different license, need to split them by those lines
+* Split licences – possibly CC0 for description/etc. but CC-BY-SA-3.0 [or whatever] for the image and possibly CC-BY-SA-3.0 or CC-BY-SA-4.0 or PD or … for the caption (and may be different)
+
+",1439364250,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","//Comments from the product pitch meeting today//
+
+* @Esanders: inline inspectors are there for things that probably shouldn’t be easily dismissed
+* Need to think about when information should be required - some things can be postponed
+* Can we use a non-linear workflow for this?  Additional information is recorded non-modally
+* Doesn’t provide any user education about what’s allowed on Commons and what’s not
+** @Jdforrester-WMF: almost all users skip straight past that page in the UploadWizard anyway
+",1433984120,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion",*** Bug 64158 has been marked as a duplicate of this bug. ***,1398101283,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion",This is not on schedule for before the next big release; noting as such.,1365636099,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+VisualEditor: Triple-click to select block level element,"From user feedback. Expected behaviour is to select entire current context (i.e. paragraph or if you're in a table, the table cell).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340834460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nicumpfbj5y55eeu3oq3,task_description,resolved
+VisualEditor: Triple-click to select block level element,Merged and will be pushed to production in a few minutes.,1372090012,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nicumpfbj5y55eeu3oq3,task_subcomment,NA
+VisualEditor: Triple-click to select block level element,"We could trivially extend the functionality as it has just been implemented so that each subsequent click beyond the third expands the selection to the next block parent. Might be useful for selecting multiple paragraphs within a table cell, table rows, full tables etc. Or might be annoying. Thoughts?",1372024524,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nicumpfbj5y55eeu3oq3,task_subcomment,NA
+VisualEditor: Triple-click to select block level element,Related URL: https://gerrit.wikimedia.org/r/70104 (Gerrit Change Ic80d24581535766714d80104222924f7a0d20f1a),1372024243,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nicumpfbj5y55eeu3oq3,task_subcomment,NA
+VisualEditor: Triple-click to select block level element,I just encountered this again when editing a table on a wiki. Especially in table cells it is tedious to have to manually select the contents of a table cell.,1367895234,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nicumpfbj5y55eeu3oq3,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"## Requirements
+
+- Identify links to pages that do not exist.
+- Support different red link behavior on desktop (class, link to edit view) and apps (remove links).
+- Support re-styling of red links for skins & accessibility.
+- Perform well, both server & client side.
+
+## Non-requirements
+
+- Stub thresholds: These can be implemented client side with a separate API request, for users that have this option enabled.
+
+## Solutions
+
+### 1) Separate metadata
+
+Provide a JSON array containing hrefs of pages that do not exist. On most pages, this array will be very short or empty.
+
+Clients can then use this array to find links to non-existing pages, and apply the transformations they would like.
+
+Advantages:
+
+- Easy to implement server side.
+- Avoids latency overheads of server-side DOM parsing.
+- Can be consistently applied to old content. However, a general limitation of red link updates for old revisions is that current link tables are only available for the latest revision, which means that links in old revisions might not be updated.
+- Consistent matching interface helps clients render red links for specific use cases.
+
+Disadvantages:
+
+- Client requirements:
+  - Process JSON and run JS.
+  - Extra API request.
+- API complexity: Need to expose metadata in separate API.
+
+
+### 2) Parsoid DOM pass
+
+Retrieve list of red links in page (as in separate metadata solution), and rewrite href / add classes in DOM processing pass.
+
+Advantages:
+
+- Still relatively easy to implement server side.
+- Low extra cost.
+- No need for JS on the client.
+- Compatible with existing skins.
+- No need for extra API.
+- Records accurate 'at the time' snapshot of how a page looked.
+
+Disadvantages:
+
+- Implements a specific kind of handling / rewriting, which then needs to be undone / changed for other use cases.
+- Changes in href (ex: linking to edit views) complicate matching for further post-processing. Not touching the href would mean that clients would need to modify the href dynamically, negating the advantage of not needing to execute JS.
+- Does not automatically update for old revisions.
+- Increases fraction of re-renders that change the content.
+
+
+### 3) Parsoid DOM pass + html2html update end point
+
+As in `Parsoid DOM pass`, but also update red link markup in old revisions through a Parsoid HTML2HTML end point.
+
+Advantages: 
+
+- As for `Parsoid DOM pass`.
+- More up-to-date red link information in old revisions.
+
+Disadvantages:
+
+- Extra complexity in Parsoid and RESTBase.
+- Increased latency and cost for accesses to old revisions, especially if the update is applied on each request.",1340566560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_description,resolved
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVzly25pU4b8yJAIAY5X} [2017-06-26T19:05:33Z] <mobrovac@tin> Finished deploy [restbase/deploy@3975ab2]: Update Parsoid HTML version to 1.5.0 - T39902 (duration: 06m 16s)",1498503933,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVzlxbBhU4b8yJAIAY5J} [2017-06-26T18:59:17Z] <mobrovac@tin> Started deploy [restbase/deploy@3975ab2]: Update Parsoid HTML version to 1.5.0 - T39902",1498503557,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVzlvvIiU4b8yJAIAY40} [2017-06-26T18:51:55Z] <arlolra> Updated Parsoid to b59045f2 (T39902, T149794)",1498503115,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Change 351537 merged by jenkins-bot:
+[mediawiki/services/parsoid@master] Implement rendering of redlinks, etc. as a post-processor
+
+[[https://gerrit.wikimedia.org/r/351537]]
+",1497459707,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Change 351537 had a related patch set uploaded (by Arlolra; owner: Arlolra):
+[mediawiki/services/parsoid@master] WIP: Port VE's LinkCache::styleElement
+
+[[https://gerrit.wikimedia.org/r/351537]]
+",1493764578,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,See https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/HEAD/modules/ve-mw/init/ve.init.mw.LinkCache.js,1493069684,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,To highlight one of the blocked tasks: T119266 makes for a pretty bad user experience in the Android app.,1484055996,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Change 303827 abandoned by Arlolra:
+[WIP] Add redlinks to a doc
+
+Reason:
+Per offsite
+
+[[https://gerrit.wikimedia.org/r/303827]]",1476815077,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@ssastry, I put this on the list for the next services / parsoid sync meeting. Red links are frequently requested, and we now have the tools to implement this efficiently.",1475787000,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2537871, @Legoktm wrote:
+> Unfortunately, relying on the links API or the current database state isn't enough. We also have to be aware of `Title::isKnown()`, so things like special pages are blue if they exist, foreign files/global user pages (and future shadow namespaces) are looked up remotely.
+
+I see {T141963} already exists.
+
+Also, BTW, the suggested API query already handles Special- and Media-namespace links. That does leave MediaWiki-namespace links and anything using the 'TitleIsAlwaysKnown' hook.",1471285541,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2537460, @Pchelolo wrote:
+> So at this point #changeprop knows which particular redlink was updated and can give this information to #restbase and #parsoid. So if #parsoid implements this an an html2html endpoint with the semantics of 'add/remove redlink information to this one particular title' - it wouldn't need to call MW API at all.
+
+It should watch out for races.  Two pages are created in close succession.  The creation of Page_1 triggers a job to update that in the DOM to blue/exists.  While that is running, Page_2 is created, triggering another job.  It needs to not clobber the first.",1471049555,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,Per @gwicke at E258,1470861583,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2537460, @Pchelolo wrote:
+>
+> So at this point #changeprop knows which particular redlink was updated and can give this information to #restbase and #parsoid. So if #parsoid implements this an an html2html endpoint with the semantics of 'add/remove redlink information to this one particular title' - it wouldn't need to call MW API at all.
+
+The base case is not solved ... you are talking about steady state behavior after a revision has been rendered and stored. But, on page edit, when the page is reparsed, you need to set up red links which requires getting information from the API.
+
+>>! In T39902#2537871, @Legoktm wrote:
+> Unfortunately, relying on the links API or the current database state isn't enough. We also have to be aware of `Title::isKnown()`, so things like special pages are blue if they exist, foreign files/global user pages (and future shadow namespaces) are looked up remotely.
+
+This is not a problem per se. Whatever code in Mediawiki provides this functionality can be implemented in the ParsoidBatchAPI extension / API call providing the functionality, unless I am missing something.",1470773166,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Unfortunately, relying on the links API or the current database state isn't enough. We also have to be aware of `Title::isKnown()`, so things like special pages are blue if they exist, foreign files/global user pages (and future shadow namespaces) are looked up remotely.",1470772294,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2537353, @GWicke wrote:
+>> Rely on Change Propagation to provide Parsoid the information about what redlinks to update
+> 
+> This is a possible optimization, but if that precise information is not available right away we could perhaps start by indicating ""update all red links"" only. See {T114413} for more on the html2html end point.
+
+Basically we already have (partially) code in CP to propagate redlinks updates, but it's not enabled. What it would do is on each new page creation/deletion it would go over the links table to see which pages were linking to this one and send rerender requests to each of those pages.
+
+So at this point #changeprop knows which particular redlink was updated and can give this information to #restbase and #parsoid. So if #parsoid implements this an an html2html endpoint with the semantics of 'add/remove redlink information to this one particular title' - it wouldn't need to call MW API at all.
+
+We could even not involve parsoid and do it with a regex in #restbase (I'm joking)",1470766766,PHID-USER-gpb2ynmxbgmy4ld2555w,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"> I am not opposed to this, but, can someone summarize what led to this change?
+
+Red links change rarely, and we do have information & infrastructure to propagate those changes. This means that it is significantly cheaper (esp. for the PHP API) to only process red links on change, rather than on each view.
+
+> Rely on Change Propagation to provide Parsoid the information about what redlinks to update
+
+This is a possible optimization, but if that precise information is not available right away we could perhaps start by indicating ""update all red links"" only. See {T114413} for more on the html2html end point.",1470765567,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Thanks @RobLa-WMF for the summary and the poke. :) Looks like @arlolra submitted a wip patch already, but a bunch of details still need to be ironed out. So, I am moving that discussion here.
+
+So, it appears that the original idea of storing HTML (without redlinks) and doing a post-process on that HTML (in a html2html) pass has morphed into something different:
+* Render red links in Parsoid as part of the normal render.  Internally, the code can continue to be structured as a DOM transformation on the parsed HTML.
+* Rely on Change Propagation to provide Parsoid the information about what redlinks to update which can be done efficiently as a html2html transform (without reparsing the page from scratch).  T39902#2199600 has some options.
+
+I am not opposed to this, but, can someone summarize what led to this change? @GWicke ?
+
+But, in any case, no matter how / when the redlink transform happens, in order to get the redlinks info, we would have to query the mediawiki API. Here are a few different options for doing so:
+* @Anomie provided a link to the links API. That can work, but to get the full list of links the continue links would have to be navigated which is a bunch of API calls (in series, not parallel) in the general case which makes this inefficient and adds to the parse time.
+* It would be better would be to have a redlinks api call that only returns missing links (if that can be done efficiently). But, I understand that this is Parsoid-specific which brings me to the next alternative.
+* This can be done as part of the ParsoidBatchAPI extension (which has some custom Parsoid functionality already).
+* However, as far as I understand, all the 3 solutions above assume / require that the core parser to have already processed the page and is an unnecessary dependency. Instead, a better alternative would be to have Parsoid send a bunch of links to the API and request a list of links that don't have a corresponding page entry in the database. This functionality is probably best done in the ParsoidBatchAPI and also eliminates the dependency on the core parser.
+
+Thoughts?",1470765376,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Thanks @RobLa-WMF for the summary and the poke. :) Looks like @arlolra submitted a wip patch already, but a bunch of details still need to be ironed out. So, I am moving that discussion here.
+
+So, it appears that the original idea of storing HTML (without redlinks) and doing a post-process on that HTML (in a html2html) pass has morphed into something different:
+* Render red links in Parsoid as part of the normal render.  Internally, the code can continue to be structured as a DOM transformation on the parsed HTML.
+* Rely on Change Propagation to provide Parsoid the information about what redlinks to update which can be done efficiently as a html2html transform (without reparsing the page from scratch).  T39902#2199600 has some options.
+
+I am not opposed to this, but, can someone summarize what led to this change? @GWicke ?
+
+But, in any case, no matter how / when the redlink transform happens, in order to get the redlinks info, we would have to query the mediawiki API. Here are 3 different options for doing so:
+* @Anomie provided a link to the links API. That can work, but to get the full list of links the continue links would have to be navigated which is a bunch of API calls (in series, not parallel) in the general case which makes this inefficient and adds to the parse time.
+* It would be better would be to have a redlinks api call that only returns missing links (if that can be done efficiently). But, I understand that this is Parsoid-specific which brings me to the next alternative.
+* Aternatively, this can be done as part of the ParsoidBatchAPI extension (which has some custom Parsoid functionality already).
+* However, as far as I understand, all the 3 solutions above assume / require that the core parser to have already processed the page and is an unnecessary dependency. Instead, a better alternative would be to have Parsoid send a bunch of links to the API and request a list of links that don't have a corresponding page entry in the database. This functionality is probably best done in the ParsoidBatchAPI and also eliminates the dependency on the core parser.
+
+Thoughts?",1470765232,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Comment from Arlo's [Gerrit change 303827](https://gerrit.wikimedia.org/r/303827):
+> [WIP] Add redlinks to a doc
+> * Makes use of the suggestion here: T39902#2209625
+> * Since this is still a WIP, provides an internal qs param (_redlinks) to add them to wt2html requests.
+>This probably belongs in html2html, as described here: T39902#2240375
+> However, it's not clear that there's a consensus on doing that yet.
+> See the discussion [in T114413]
+",1470764678,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Change 303827 had a related patch set uploaded (by Arlolra):
+[WIP] Add redlinks to a doc
+
+[[https://gerrit.wikimedia.org/r/303827]]
+",1470762648,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2535493, @Arlolra wrote:
+>> @Anomie provided advice how to use the Action API to get redlink information.
+> 
+> Can you put that here?
+
+See his April 2016 comments, starting at T39902#2209625
+",1470705533,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"> @Anomie provided advice how to use the Action API to get redlink information.
+
+Can you put that here?",1470703746,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@Jdlrobson and I just had a really good conversation about this.  The thing #ArchCom (or someone) needs to provide is guidance for what code that someone (possibly Jon?) can contribute in order to accelerate progress on the redlink issue.  @anomie provided advice how to use the Action API to get redlink information.  @gwicke, is there any guidance you're waiting on the rest of #ArchCom for?  @ssastry, do you agree with @gwicke that Parsoid needs modification to provide redlink information in the HTML?",1470702038,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Here's my understanding of the chronology so far:
+1.  Filed by @jdforrester-wmf in 2012-06-24
+   * Title: ""//VisualEditor: Parsoid needs to hint on each 'internal' link as to the status of its target (redlink; stub; interwiki)//"" 
+   * Description: ""//For the arbitrary stub threshold preference, perhaps just hint with the character length of the link and leave it to the UI to decide how to render based on user preferences? This would mean that we wouldn't fragment the parser cache...//""
+   * Assignee: @GWicke
+2.  @Gwicke drops priority to lowest priority on 2012-06-29
+3.  Jan 2013: new title ""Implement rendering of redlinks and stubs"" (moved out of #Parsoid and into Bugzilla's ""General"" project) T39902#413848
+2.  Discussion in 2013, suggesting Action API changes, and hinting that ""bug 11"" (T2011) could be fixed by this
+3.  Feb 2014: James reports that @Catrope will attempt to implement this, ""at least as a first run"" and raises to high priority (T39902#413952).
+4.  March 2014: James fixes related issue T39901
+4.  Early 2015: James drops Roan as assignee, @ssastry drops priority to normal
+8. Sept 2015: @Jdlrobson expands the task description (T39902#1690785)
+1.  March 2016: @gwicke flags this as an #ArchCom-RFC
+8. April 2016:
+   * #ArchCom very briefly discusses this in E161 as part of our planning/triage
+   * @gwicke posts an implementation strategy, but remarks ""As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article."" (T39902#2208376)  
+   * @anomie responds, advising about how to do this, but cautions: ""//We might have to disable it (or reduce the functionality) in miser mode though, like we do with various other parameters, to avoid bugs like T97797.//"" (T39902#2209625)
+   * @gwicke ties this to the change propagation service (T133221) and suggests Parsoid would need to provide redlink markup as part of the re-render request (T114413). (T39902#2240375)
+9. August 2016: @Jdlrobson cross posts ""[Redlinks in Android app](https://lists.wikimedia.org/pipermail/wikitech-l/2016-August/086242.html)"" on mobile-l and wikitech-l: ""//I've cced wikitech in case anyone has an update.//""  
+
+Next steps?  I suppose #ArchCom can discuss this in E258, and possibly make this a candidate for one of our office hours in the not-to-distant future.  We can discuss the #ArchCom-RFC triage process in Z425.
+",1470601404,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"We are currently working on implementing the update logic in the change propagation service: T133221. This will trigger HTML re-renders for all pages linking to a created / deleted page. As part of the re-render request (see T114413), we will supply
+
+- an update mode ('redlinks', 'brokenlinks' or the like),
+- whether this is a deletion or creation, and
+- the created / deleted title (so that updates can be targeted).
+
+The number of update requests from this will be fairly small, so optimizations are not critical. However, for this to actually result in red links being inserted / updated, Parsoid will need to mark up red links as part of the normal render process.
+",1461690900,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2209625, @Anomie wrote:
+>>>! In T39902#2208376, @GWicke wrote:
+>> This end point already supports restricting links to a specific namespace using the `plnamespace` parameter.  Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. 
+> 
+> We might have to disable it (or reduce the functionality) in miser mode though, like we do with various other parameters, to avoid bugs like T97797.
+
+The current query for this module is reasonably simple, basically
+```
+-- Generic
+SELECT pl_from, pl_namespace, pl_title FROM pagelinks WHERE pl_from IN (...) ORDER BY pl_from ASC, pl_namespace ASC, pl_title ASC LIMIT 501;
+
+-- With plnamespace
+SELECT pl_from, pl_namespace, pl_title FROM pagelinks WHERE pl_from IN (...) AND pl_namespace IN (...) ORDER BY pl_from ASC, pl_namespace ASC, pl_title ASC LIMIT 501;
+```
+
+Adding a `plbrokenlinks` parameter would require joining with `page`, though:
+```
+SELECT pl_from, pl_namespace, pl_title FROM pagelinks LEFT JOIN page ON (pl_namespace = page_namespace AND pl_title = page_title) WHERE pl_from IN (...) AND page_id IS NULL ORDER BY pl_from ASC, pl_namespace ASC, pl_title ASC LIMIT 501;
+```
+Just a join there is probably not too bad (it's an `eq_ref` which isn't a bad join type, although it's still a join on a 261-byte key so it's not the greatest), but using the join as a filter where the vast majority of the time the filter is going to fail would certainly be a T97797 issue waiting to be reported.
+
+So what you'd end up with on WMF wikis is that using your `plbrokenlinks` parameter would do a query more like
+```
+SELECT pl_from, pl_namespace, pl_title, page_id FROM pagelinks LEFT JOIN page ON (pl_namespace = page_namespace AND pl_title = page_title) WHERE pl_from IN (...) ORDER BY pl_from ASC, pl_namespace ASC, pl_title ASC LIMIT 501;
+```
+then on the PHP side it would filter out the rows with `$row->page_id !== null`, typically leaving zero to actually be returned and a continuation for it to do the same check on the next batch of links.",1461004303,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@anomie, thanks for the input! And sorry to hear about the flu- hope you are better soon!",1460743811,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2208376, @GWicke wrote:
+> As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest).
+
+You could use something like https://en.wikipedia.org/w/api.php?action=query&generator=links&titles=User:GWicke/LinkTest.
+
+> This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. 
+
+We might have to disable it (or reduce the functionality) in miser mode though, like we do with various other parameters, to avoid bugs like T97797.
+
+I'll try to remember to look at it next week when I'm over the flu.",1460723870,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Based on the performance information we have from elematch, I think it is clear that updating red link information server-side is doable at very moderate cost. Here is a proposal:
+
+### Implement red link updates in change propagation
+
+The recently deployed change propagation service will follow page creation / deletion events, and will initiate red link updates for all pages linking to the created / deleted pages. (#services)
+
+### Parsoid to mark red links with an attribute by default
+
+Regular parse: Parsoid will request a list of red links from the API, and annotate <a> elements with appropriate attributes in a DOM pass. 
+
+Update: When getting a 'red link update' request from the change propagation service, RESTBase will pass the current HTML and **the update mode (""redlinks"")** to Parsoid, the same way it already does right now for template or image updates. Parsoid will then update red links using any technique of its choosing. For example, it could do this using elematch, avoiding the need for expensive DOM parsing. (#parsing-team)
+
+### Issue: API for red links
+
+As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest). Nor does it support only retrieving red links.
+
+This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. 
+
+@Anomie @ssastry @Pchelolo @mobrovac @Arlolra, does this sound sane to you?
+
+(#services or #parsing-team)",1460667870,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Based on the performance information we have from elematch, I think it is clear that updating red link information server-side is doable at very moderate cost. Here is a proposal:
+
+### Implement red link updates in change propagation
+
+The recently deployed change propagation service will follow page creation / deletion events, and will initiate red link updates for all pages linking to the created / deleted pages. (#services)
+
+### Parsoid to mark red links with an attribute by default
+
+Regular parse: Parsoid will request a list of red links from the API, and annotate <a> elements with appropriate attributes in a DOM pass. 
+
+Update: When getting a 'red link update' request from the change propagation service, RESTBase will pass the current HTML and **the update mode (""redlinks"")** to Parsoid, the same way it already does right now for template or image updates. Parsoid will then update red links using any technique of its choosing. For example, it could do this using elematch, avoiding the need for expensive DOM parsing. (#parsing-team)
+
+### Issue: API for red links
+
+As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest). Nor does it support only retrieving red links.
+
+This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. @Anomie, does this sound sane to you?
+
+(#services or #parsing-team)",1460667723,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Based on the performance information we have from elematch, I think it is clear that updating red link information server-side is doable at very moderate cost. Here is a proposal:
+
+### Implement red link updates in change propagation
+
+The recently deployed change propagation service will follow page creation / deletion events, and will initiate red link updates for all pages linking to the created / deleted pages. (#services)
+
+### Parsoid to mark red links with an attribute by default
+
+Regular parse: Parsoid will request a list of red links from the API, and annotate <a> elements with appropriate attributes in a DOM pass. 
+
+Update: When getting a 'red link update' request from the change propagation service, RESTBase will pass the current HTML and **the update mode (""redlinks"")** to Parsoid, the same way it already does right now for template or image updates. Parsoid will then update red links using any technique of its choosing. For example, it could do this using elematch, avoiding the need for expensive DOM parsing. (#parsing)
+
+### Issue: API for red links
+
+As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest). Nor does it support only retrieving red links.
+
+This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. @Anomie, does this sound sane to you?
+
+(#services or #parsing-team)",1460667711,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Based on the performance information we have from elematch, I think it is clear that updating red link information server-side is doable at very moderate cost. Here is a proposal:
+
+### Implement red link updates in change propagation
+
+The recently deployed change propagation service will follow page creation / deletion events, and will initiate red link updates for all pages linking to the created / deleted pages. (#services)
+
+### Parsoid to mark red links with an attribute by default
+
+Regular parse: Parsoid will request a list of red links from the API, and annotate <a> elements with appropriate attributes in a DOM pass. 
+
+Update: When getting a 'red link update' request from the change propagation service, RESTBase will pass the current HTML and **the update mode (""redlinks"")** to Parsoid, the same way it already does right now for template or image updates. Parsoid will then update red links using any technique of its choosing. For example, it could do this using elematch, avoiding the need for expensive DOM parsing. (#services)
+
+### Issue: API for red links
+
+As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest). Nor does it support only retrieving red links.
+
+This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. @Anomie, does this sound sane to you?
+
+(#services or #parsing-team)",1460667674,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"A patch for element & attribute matching is now up at https://github.com/wikimedia/elematch/pull/5. Performance results for Obama (1.5mb):
+
+- match / replace all figures: 1.95ms
+- match / replace all links: 13.9ms
+- **match / replace a *specific* link (`a[href=""./Riverdale,_Chicago""]`): 1.9ms**
+- match / replace references section (`ol[typeof=""mw:Extension/references""]`): 3.7ms
+
+Other options:
+- libxml XML DOM round-trip (no matching): 51.1ms
+  - plus xpath match: ~15ms
+- domino round-trip (no matching): 255.3ms
+
+This means that we can dynamically update red links in large documents using less than ~2ms of cpu time. This is over a magnitude less than libxml in XML mode, the next best option.",1460479663,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"A patch for element & attribute matching is now up at https://github.com/wikimedia/elematch/pull/5. Performance results for Obama (1.5mb):
+
+- match / replace all figures: 1.95ms
+- match / replace all links: 13.9ms
+- **match / replace a *specific* link: 1.9ms**
+- match / replace references section (`ol[typeof=""mw:Extension/references""]`): 3.7ms
+
+Other options:
+- libxml XML DOM round-trip (no matching): 51.1ms
+  - plus xpath match: ~15ms
+- domino round-trip (no matching): 255.3ms
+
+This means that we can dynamically update red links in large documents using less than ~2ms of cpu time. This is over a magnitude less than libxml in XML mode, the next best option.",1460479419,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a full DOM parse + XPath match, but incurs some extra cost for DOM serialization.
+
+The cost is directly proportional to the number of elements matched. For comparison, matching only <figure> elements in Obama takes only 2ms.
+
+Edit: Updated benchmark results at https://github.com/wikimedia/elematch#performance
+
+Edit 2: Assuming XML spec compatible serialization, it turns out that we should actually be able to implement relatively efficient matches on attribute values as well. There are several gotchas around optional entity encoding, but they look solvable so far. I'll try to explore this approach in [elematch](https://github.com/gwicke/elematch).",1459546168,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a full DOM parse + XPath match, but incurs some extra cost for DOM serialization.
+
+The cost is directly proportional to the number of elements matched. For comparison, matching only <figure> elements in Obama takes only 2ms.
+
+Edit: Updated benchmark results at https://github.com/wikimedia/elematch#performance",1458948750,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a full DOM parse + XPath match, but incurs some extra cost for DOM serialization.
+
+The cost is directly proportional to the number of elements matched. For comparison, matching only <figure> elements in Obama takes only 2ms.",1458762366,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a full DOM parse + XPath match, but incurs some extra cost for DOM serialization.",1458762273,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a pull DOM parse + XPath match, but incurs some extra cost for DOM serialization.",1458762250,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a lower bound on server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of cpu time. LibXML offers similar performance for a pull DOM parse + XPath match, but incurs some extra cost for DOM serialization.",1458762059,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"cscott: the image blocklist is actually very very small, much fewer than 1000 images on there.
+cscott: i'm not worried about caching the image as blocked in the archive.  it's the same as any other template dependency; the page ""as it looks right now"" depends on the current state of the image blocklist.
+cscott: because it's small and a corner case, i don't think it should drive redlink discussions/decisions.
+
+redlinks are orders of magnitude more common.  let's not try to make these two cases the same thing.",1458761460,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@ssastry, I have added option 3) as an extension in the task description.
+
+One question we should make up our mind on is whether we would rewrite href attributes to point to edit views, to match what is currently done on the web. Doing so would complicate further processing:
+
+- VisualEditor would need to strip ?action=edit from its link widget. The same will likely be true for other clients, like mining of link graphs.
+- Matching could not rely on the plain href, but would need to either match on a mangled href, or use other attributes like a class instead.
+
+If we decide to not mangle href, then web clients would need to do so after the fact, negating the advantage of not needing to run JS.
+
+Another consideration is that link updates in old revisions are currently only efficiently possible using link information from the latest revision. This means that links that were only present in the older revision won't be checked for existence in queries based on the latest revision's links.
+
+In the context of the API-driven front-end effort, it seems likely that we'll serve metadata about a page separately. This metadata would contain red links, language links (from wikidata), categories, table of content hints and more. If we assume that we'll need this anyway for other bits of metadata, then the extra cost of a general page metadata request is becoming less of an issue in this discussion.
+
+So, overall I'm still torn, but am starting to lean more towards 1) than 2) / 3).",1458755702,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@ssastry, I have added option 3) as an extension in the task description.
+
+One question we should make up our mind on is whether we would rewrite href attributes to point to edit views, to match what is currently done on the web. Doing so would complicate further processing:
+
+- VisualEditor would need to strip ?action=edit from its link widget. The same will likely be true for other clients, like mining of link graphs.
+- Matching could not rely on the plain href, but would need to either match on a mangled href, or use other attributes like a class instead.
+
+If we decide to not mangle href, then web clients would need to do so after the fact.
+
+Another consideration is that link updates in old revisions are currently only efficiently possible using link information from the latest revision. This means that links that were only present in the older revision won't be checked for existence in queries based on the latest revision's links.
+
+In the context of the API-driven front-end effort, it seems likely that we'll serve metadata about a page separately. This metadata would contain red links, language links (from wikidata), categories, table of content hints and more. If we assume that we'll need this anyway for other bits of metadata, then the extra cost of a general page metadata request is becoming less of an issue in this discussion.
+
+So, overall I'm still torn, but am starting to lean more towards 1) than 2) / 3).",1458755650,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Soln 3: Provide a Parsoid API endpoint that transforms stored HTML with red link info added in. But, this will require some caching / temporary storage  (and associated invalidation) to alleviate performance impact of a secondary api request.
+Soln 2 will cause old revisions to render broken.
+Soln 1 is the ideal solution.
+
+That said, this question will surface again for ""bad images"". For ""bad images"", we do not have the luxury of breaking old revisions. Bad images are probably expected to be blacklisted in all revisions. Plus, client-side solution for that will probably not be acceptable for the no-js case since those images will render in full glory.
+
+It seems like we should pick a solution that works in both scenarios => solution 3?",1458689807,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Soln 3: Provide a Parsoid API endpoint that transforms stored HTML with red link info added in. But, this will require some caching / temporary storage  (and associated invalidation) to alleviate performance impact of a secondary api request.
+Soln 2. => old revisions will render broken.
+Soln 1 is the ideal solution.
+
+That said, this question will surface again for ""bad images"". For ""bad images"", we do not have the luxury of breaking old revisions. Bad images are probably expected to be blacklisted in all revisions. Plus, client-side solution for that will probably not be acceptable for the no-js case since those images will render in full glory.
+
+It seems like we should pick a solution that works in both scenarios => solution 3?",1458689368,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Soln 3: Provide a Parsoid API endpoint that transforms stored HTML with red link info added in. But, this will require some caching / temporary storage  (and associated invalidation) to alleviate performance impact of a secondary api request.
+Soln 2. => old revisions will render broken.
+Soln 1 is the ideal solution.
+
+That said, this question will surface again for ""bad images"". For ""bad images"", we do not have the luxury of breaking old revisions. Bad images are probably expected to be blacklisted in all revisions. Plus, client-side solution for that will probably not be acceptable for the no-js case since those images will render in full glory.
+
+It seems like we should pick a solution that works in both scenarios. ",1458689321,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"We discussed this again in today's Reading / Services sync-up meeting. We really need to figure out a general solution for this to avoid each client needing to implement their own.
+
+In the discussion, the consensus was that external metadata might also be workable, but inline information would be easier to work with. I have updated the task description with some use cases, requirements & pros / cons of each approach. Please update / add your view, so that we can decide on the way forward soon.",1458681763,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"I wouldn't hold that patch up as an example, though, at least in its current form; we had to un-deploy it because of memory issues.",1457654688,PHID-USER-d2tiurktk2jgxzcpd2jw,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,https://gerrit.wikimedia.org/r/#/c/274638/ has a patch implementing red link hiding in the mobile app content service.,1457651778,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#1694428, @GWicke wrote:
+>>>! In T39902#413952, @Jdforrester-WMF wrote:
+>> Roan's going to try to work on this, at least as a first run.
+> 
+> Famous last words ;)
+
+This was complete two weeks later – {T39901}.
+
+> I am wondering if we could implement this at the edge / client after all, as part of a setup like T111588. Idea would be:
+> 
+> 1) API providing an array of links in the page that don't exist, and
+> 2) JS skin code running in a service worker or in nodejs on the edge generating CSS to style red links, or JS code running on the DOM to add classes.
+
+{T64803} is the task to turn the current client-side VE code into a service that provides an additional stylesheet per your recommendation – something like:
+
+  restbase/styleContent/page/Foobar/revision/123456
+
+… which returns a stylesheet like
+
+  a[href=LinkDoesNotExist],
+  a[href=AnotherLinkDoesNotExist]
+  { color: red; }
+
+… or whatever.",1446686133,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"I would prefer to add a class to the DOM. The app can provide the CSS rules to style it or do something else with it (like replace the link with a span).
+
+This task is very old already. Any chance of getting this in soon?",1446576329,PHID-USER-tjyfydvd4ncrfvvr6mkr,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#413952, @Jdforrester-WMF wrote:
+> Roan's going to try to work on this, at least as a first run.
+
+Famous last words ;)
+
+I am wondering if we could implement this at the edge / client after all, as part of a setup like T111588. Idea would be:
+
+1) API providing an array of links in the page that don't exist, and
+2) JS skin code running in a service worker or in nodejs on the edge generating CSS to style red links, or JS code running on the DOM to add classes.",1443726232,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Roan's going to try to work on this, at least as a first run.",1393538172,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(In reply to comment #14)
+> (In reply to comment #13)
+> > As a note, if we did this cross-cluster, that would fix bug 11 (!) which
+> > would be a lovely additional feature.
+> 
+> Sounds doable with separate API requests to each target wiki. Or even HEAD
+> requests for external links, so that even non-wiki external links could be
+> redlinked ;)
+
+That would just be showing off. :-)",1378418392,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(In reply to comment #13)
+> As a note, if we did this cross-cluster, that would fix bug 11 (!) which
+> would
+> be a lovely additional feature.
+
+Sounds doable with separate API requests to each target wiki. Or even HEAD requests for external links, so that even non-wiki external links could be redlinked ;)",1378418353,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"As a note, if we did this cross-cluster, that would fix bug 11 (!) which would be a lovely additional feature.",1378416210,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"For stub thresholds, the API could also return an array of linked articles and their respective size. I think it would be fine to put the burden of an additional request onto those few users using stub indicators (they are disable d by default). The actual rendering can be done client-side based on that user's stub thresholds, which can sadly be arbitrary byte sizes.",1364588810,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(In reply to comment #10)
+> Presumably an optional parameter to that core API is ""stub length
+> preference"".
+
+That could work, but feels a little messy. Gabriel as guardian of all that is appropriate coding might well have some thoughts. :-)",1364365941,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Presumably an optional parameter to that core API is ""stub length preference"".",1364354581,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(In reply to comment #8)
+> One option might be to merge in information from another API into the <head>
+> of the document which parsoid returns, to minimize round trips -- but in that
+> case the API should first be added to core.  The simplest possible API would
+> supply the name of an article and get back an array of stubbed or red links
+> in that article.
+
+Only problem is that this doesn't solve the ""colouring stubs differently at a user-set arbitrary byte length"" preference; I'd be reasonably OK with us removing that feature anyway, but that should be an actual decision discussed with people rather than just over-looked. :-)",1364351527,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"One option might be to merge in information from another API into the <head> of the document which parsoid returns, to minimize round trips -- but in that case the API should first be added to core.  The simplest possible API would supply the name of an article and get back an array of stubbed or red links in that article.",1364335396,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,Changing component to general- this would either happen in MediaWiki PHP/DOM post-processing or the client side.,1359413223,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Moving this to the CPP DOM subcomponent for now, as this would be something to implement on the DOM if it is going to be done on the server side. A JS-only implementation could also use node to work on the server-side DOM as a fall-back for non-js clients.",1344288190,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,Mass-moving bugs into the new 'Parsoid' product.,1344281141,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"IMO this should not be the task of the parser however, hence the low priority on this bug.",1342990813,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"I'm a bit surprised about the importance. Coloring for stub may be an enhancement, but a link to a nonexistent page definitely shouldn't be blue.",1342869964,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(Mark as ASSIGNED for completeness.)
+
+Yes, worth discussing.",1340568633,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,See my reply in bug #37901. I'd prefer to take the opportunity and move as many user preferences out of the parser as possible.,1340568582,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"To show red links (and stub links) correctly, Parsoid will need to hint on each link as to the status of its target. Also some work in CE and UI. ;-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=38726",1340565720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7km7sjcw27m7salmhqyx,task_description,resolved
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Verified, working fine on the English and Italian Wikipedias.",1396033621,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to pamdavies7 from comment #25)
+> It doesn't seem to be resolved. I found
+> https://en.wikipedia.org/wiki/Demented_Are_Go#Studio_albums by hitting
+> ""Random article"" until I found a redlink, tried to edit it in VE, and the
+> red link (""Welcome back to Insanity Hall "") looked blue. Am I missing
+> something?
+> 
+> In case it was any of my settings, I tried again using my (declared)
+> alternative account which has default settings for everything: went to
+> preferences to enable VE, tried editing that article, still a blue link.
+
+The code is not yet deployed to the English Wikipedia. It will be deployed today to MediaWiki.org (hence the date in the ""milestone""), and to the English Wikipedia in a week, following the regular schedule.",1395333876,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"It doesn't seem to be resolved. I found https://en.wikipedia.org/wiki/Demented_Are_Go#Studio_albums by hitting ""Random article"" until I found a redlink, tried to edit it in VE, and the red link (""Welcome back to Insanity Hall "") looked blue. Am I missing something?
+
+In case it was any of my settings, I tried again using my (declared) alternative account which has default settings for everything: went to preferences to enable VE, tried editing that article, still a blue link.",1395333779,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Change 118045 merged by jenkins-bot:
+Display links to nonexistent pages as red
+
+https://gerrit.wikimedia.org/r/118045",1395283464,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Change 118045 had a related patch set uploaded by Jforrester:
+[WIP] Red link support
+
+https://gerrit.wikimedia.org/r/118045",1395179140,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Change 118045 had a related patch set uploaded by Jforrester:
+[WIP] Red link support
+
+https://gerrit.wikimedia.org/r/118045",1394500950,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Revert. Lots of ""basic"" features are enhancements. Bugs are ""this should already be working and its lack of presence is a code failure"". Noting however that this is high priority.",1385369238,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Changing importance to ""Normal"". Even though it's not a regression compared to the source editor, common sense says that it should be a basic feature of VE and not an ""Enhancement"".",1385369038,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 56442 has been marked as a duplicate of this bug. ***,1383277462,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"**jonathan.haas** wrote:
+
+(In reply to comment #16)
+> * Internal links
+> ** If the page does not exist, colour it red
+> ** If the page does exist but is a disambiguation page, colour it yellow
+> ** If the page does exist but is under (arbitrary) stub threshold, colour it
+> purple
+> ** Elsewise, colour it dark blue
+
+Don't forget about redirection pages. In some Wikipedia's it is probably bad practice to link them. In german Wikipedia, it's okay to link them, but only if the link target makes more sense than the main page title. So in any case it's nice to see that the link target is a redirect. A bonus would be a tooltip which shows the page the redirect redirects to.
+
+(In reply to comment #6)
+> This can be implemented with a generated CSS file containing attribute
+> selectors matching red link targets like this:
+> 
+> a[href=""./Foo""],
+> a[href=""./Bar""] { color: red }
+
+This is a really horrible idea. About 5% of the population are color blind, you really don't want to hardcode colors like this in any way. If embedding this information in the page source is technically impossible for whatever reason, then load a list of external pages using JS and add css classes or other attributes on the fly.",1378103629,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to comment #16)
+
+> * Internal links
+> ** If the page does not exist, colour it red
+> ** If the page does exist but is a disambiguation page, colour it yellow
+> ** If the page does exist but is under (arbitrary) stub threshold, colour it
+> purple
+> ** Elsewise, colour it dark blue
+
+If the link is a redirect, will the system pick up the properties of the target page or just code it as a stub because it's short? (Target could be a dab page, stub, or normal page).",1378073610,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to comment #14)
+> This is an 80/20 issue - 80% of the value comes from fixing just the coloring
+> of internal wikilinks. Coloring of external links isn't critical. (There can
+> be
+> significant time-delay in getting 404 or similar error codes for page
+> non-existence, as well as false negatives when a website is temporarily
+> down.)
+> And of the internal wikilinks, most of the value is redlinks, some of the
+> value
+> is disambiguation pages, and little of the value is stubs (which, again, are
+> subject to false positives, since article assessments aren't automated).
+> 
+> In short, the priority ought to be to code internal wikilinks that go to
+> non-existent pages (as red), and internal wikilinks that go to disambiguation
+> pages (as yellow, I think), and not to worry all that much about anything
+> else.
+
+The solution we're considering is a service that, given an array of links, returns a set of CSS selectors that VE applies to the page, to give the appropriate hinting on links.
+
+To be very specific, we are talking about:
+
+* Internal links
+** If the page does not exist, colour it red
+** If the page does exist but is a disambiguation page, colour it yellow
+** If the page does exist but is under (arbitrary) stub threshold, colour it purple
+** Elsewise, colour it dark blue
+
+* External links
+** If the link is to a wiki that is ""internal"" (i.e., an interwiki), colour it mid-blue
+** Elsewise, colour it mid-blue with an ""external link"" icon.
+
+It is a mistake to think that doing this but only for internal link state and only for existence/non-existence is 20% of the work for 80% of the gain; it's much more like 90% of the work for 80% of the gain. :-) Building the service itself is definitely the hard part of this.",1377959776,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to comment #14)
+> This is an 80/20 issue - 80% of the value comes from fixing just the coloring
+> of internal wikilinks. Coloring of external links isn't critical.
+
+
+I don't think anyone suggested (or has ever implemented?) coloring of external links. They only change color based on your browser settings, for clicked/unclicked links (essentially).
+
+
+> And of the internal wikilinks, most of the value is redlinks, some of the
+> value
+> is disambiguation pages, and little of the value is stubs (which, again, are
+> subject to false positives, since article assessments aren't automated).
+
+
+Stubs are colored based on byte-count, not whether they're tagged-as-a-stub. You can change the byte-count in your [[special:preferences]], under ""Appearance->Threshold for stub link formatting (bytes):[dropdownmenu]""
+
+
+> In short, the priority ought to be to code internal wikilinks that go to
+> non-existent pages (as red), and internal wikilinks that go to disambiguation
+> pages (as yellow, I think), and not to worry all that much about anything
+> else.
+
+
+Agreed that only redlinks are crucial. 
+
+For disambig links, possibly the new Property system can help?
+https://en.wikipedia.org/wiki/Special:PagesWithProp?propname=disambiguation&propname-other=
+
+For anything more complex than that, Anomie's Linkclassifier code might be useful/insightful. 300+ users have it installed. I recommend the ""run on demand"" version. https://en.wikipedia.org/wiki/User:Anomie/linkclassifier
+code at https://en.wikipedia.org/wiki/User:Anomie/linkclassifier.js",1377929906,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"This is an 80/20 issue - 80% of the value comes from fixing just the coloring of internal wikilinks. Coloring of external links isn't critical. (There can be significant time-delay in getting 404 or similar error codes for page non-existence, as well as false negatives when a website is temporarily down.) And of the internal wikilinks, most of the value is redlinks, some of the value is disambiguation pages, and little of the value is stubs (which, again, are subject to false positives, since article assessments aren't automated).
+
+In short, the priority ought to be to code internal wikilinks that go to non-existent pages (as red), and internal wikilinks that go to disambiguation pages (as yellow, I think), and not to worry all that much about anything else.",1377917820,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),Right now the linking problems detected only after saving the page. So please raise the importance of this bug and fix it on priority.,1376796900,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to comment #10)
+> There has just been another editor on en.wp requesting this functionality. 
+> 
+> (In reply to comment #9)
+> > Would it be possible also to make other kinds of pages to appear in different
+> > colours, by changing CSS pages on the local wikis? I know that some wikis
+> > have
+> > different colours for redirects (green), others make links to disambiguation
+> > pages appear highlighted in yellow.
+> 
+> That is bug 52173. Although there was some discussion about whether that was
+> a duplicate of this the consensus seemed to be that it wasn't.
+
+That bug was asking for the same problem to be fixed, but was suggesting a different technical solution (and one which is a WONTFIX from the Parsoid team, as it makes the cached pages get invalidated by other pages getting created/deleted/expanded out of the stub threshold/made into/out of a redirect/made into/out of a disambiguation page). Sorry for the confusion.",1375303713,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 52173 has been marked as a duplicate of this bug. ***,1375303572,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"There has just been another editor on en.wp requesting this functionality. 
+
+(In reply to comment #9)
+> Would it be possible also to make other kinds of pages to appear in different
+> colours, by changing CSS pages on the local wikis? I know that some wikis
+> have
+> different colours for redirects (green), others make links to disambiguation
+> pages appear highlighted in yellow.
+
+That is bug 52173. Although there was some discussion about whether that was a duplicate of this the consensus seemed to be that it wasn't.",1375303150,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Would it be possible also to make other kinds of pages to appear in different colours, by changing CSS pages on the local wikis? I know that some wikis have different colours for redirects (green), others make links to disambiguation pages appear highlighted in yellow.",1374836101,PHID-USER-myojicphhrv5eiqtoq52,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"We don't want to encode this information in the DOM to avoid cache updates for the page content. There is really no need to do so since CSS selectors work well these days, and purging / regenerating CSS is much cheaper than updating page content.",1373556054,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Normally, in article view mode, redlinks have CSS class ""new"" and I'm suggesting doing it in the same way for the sake of consistency.",1373555910,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"This can be implemented with a generated CSS file containing attribute selectors matching red link targets like this:
+
+a[href=""./Foo""],
+a[href=""./Bar""] { color: red }
+
+Alternatively a JSON file containing the redlink targets could be fetched and a redlink class set on each of them. CSS seems to be the more elegant solution without a need for JS and DOM changes though.
+
+In the longer term this is something we should implement for core too.",1373386102,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 50974 has been marked as a duplicate of this bug. ***,1373353929,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 50020 has been marked as a duplicate of this bug. ***,1371912053,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 49475 has been marked as a duplicate of this bug. ***,1371049016,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"It is actually shown as blue links which are considered to be existing pages. This is confusing.  I understand the parsoid isn't doing existence checks at all, so better use a natural color for all links.",1366924344,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"So far my idea is to keep link existence checks out of Parsoid, and add the colors from JS or CSS instead. This should avoid some parser cache invalidations and makes the parser output less dependent on user preferences.
+
+To do this, a data structure with the status of all outgoing links in a page would need to be fetched separately. This could be a JSON structure, or a CSS file that directly matches some target-hash-based classes on links.
+
+Doing the same for media or images would be harder, and is not something we plan to do right now. We'll instead render them normally, and perform the existence check in the parser while retrieving the image dimensions.",1340568470,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Tested in Firefox 16 nightly.
+
+Steps to repro:
+* go to https://www.mediawiki.org/wiki/VisualEditor:Welcome
+* hit 'edit'
+* click in, select all, copy to clipboard
+* go to https://www.mediawiki.org/wiki/VisualEditor:Blorpo etc
+* hit 'edit'
+* click in, paste
+
+Expected results:
+Beautiful pasted HTML
+
+Actual results:
+All formatting lost. Newlines are turned into little newline symbols.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340418900,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_description,resolved
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Sorry, not ""fixed"" but duplicate of bug 33105.
+
+*** This bug has been marked as a duplicate of bug 33105 ***",1375942744,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Just copy content from a page (e.g. https://it.wikipedia.org/wiki/Fire?veaction=edit) and paste in another one (e.g. https://it.wikipedia.org/wiki/Phantom?veaction=edit) :-) all the links, italics, lists etc. are lost.",1374852759,PHID-USER-myojicphhrv5eiqtoq52,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Francisco: Exact steps to reproduce highly welcome, so developers can take a look.",1374852358,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,I have to confirm that this bug still occurs on it.wiki.,1374845048,PHID-USER-myojicphhrv5eiqtoq52,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"(In reply to comment #6)
+> Bug 33105 is *not* general c'n'p, it's only c'n'p from external sources.
+
+You're right, sorry, I didn't update the title. Fixed. (Also, another VE instance is definitely an external source.)",1373143762,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Bug 33105 is *not* general c'n'p, it's only c'n'p from external sources.",1373142524,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"This was replaced with bug 33105 (general copy-and-paste)
+
+*** This bug has been marked as a duplicate of bug 33105 ***",1372795675,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"This bug seems to be occurring again.  Same issue- format loss.
+
+Ref:
+https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=561998028&oldid=561996397",1372444393,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,will thst work between wikis?,1340990138,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"**orbit** wrote:
+
+This is fixed in:
+https://gerrit.wikimedia.org/r/#/c/13423/
+
+Previously, copied data was stored in a local JS variable. Only copy and paste from within a single document was supported. Now, using localStorage, rich content may be copied from one article to another on the same wiki in the same browser.",1340929791,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Same behavior in Firefox 13, Chrome 19, Safari 5.1.7 (though Chrome & Safari don't show the little newline symbols, you just don't get line breaks at all).
+
+This makes common editing tasks like moving text from one page to another impossible, so might want to bump priority up.",1340470722,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,"VE should give nice error messages (where possible, graceful degradation?) to users without JavaScript or not using Vector as their skin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340417940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jb33pbb73nuyy4d6ar52,task_description,declined
+VisualEditor: Nice error message for users without JavaScript,VE already gracefully degrades. It simply doesn't appear. I don't think there's anything more we should do at this point.,1345671293,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,This might be a partial duplicate of bug 38154,1345668931,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,"If you don't have JavaScript, then nothing will happen at all - there's no need for a ""nice error message"".
+
+And even if there was, you would do what? Implement something in PHP that detects if JavaScript is enabled on the client and then output a custom page, just for that user, that tells them they can't use VisualEditor because they don't have JavaScript enabled? So - that part of this bug is useless (sorry to be snarky, just having fun)
+
+As for other skins - VisualEditor skin integration is something we are still working on. We want it to be skin-independent, and soon it will be, but we have to make an API for this, and in the mean time we are just hacking in support for a couple skins. That part of the bug is valid - maybe we should rename this to ""VisualEditor lacks skin integration API"".",1345659493,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,"(In reply to comment #1)
+> What currently locks things into Vector skin? This shouldn't be skin-dependent,
+> in theory.
+
+I split the lack of support for other skins out to bug 38154.
+
+Changing this bug's summary from ""VisualEditor: Nice error messages for no-JS/no-Vector users"" to ""VisualEditor: Nice error message for users without JavaScript"". VisualEditor isn't going to be Vector-only, so there's no reason to work on an error message for that.",1341350822,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,"What currently locks things into Vector skin? This shouldn't be skin-dependent, in theory.",1340468013,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,"Create some text - e.g. ""Expe dit ious"". Set the first seven characters as bold, and the last seven as italics. Round-trip.
+
+Expected wikitext: '''Expe''dit'''''<nowiki></nowiki>''ious''
+
+Expected HTML: <strong>Expe<em>dit</em></strong><em>ious</em>
+
+Actual wikitext:'''Expe''dit'''''''ious''
+
+Actual HTML: <strong>Expe<em>dit''</em></strong>ious
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340397840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_description,resolved
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,Patch committed in https://gerrit.wikimedia.org/r/37985.,1355186279,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,"Confirmed that the HTML send from VE to Parsoid is:
+
+""<p data-parsoid=""{&quot;dsr&quot;:[0,25]}""><b>Expe<i>dit</i></b><i>ious</i></p>""
+
+But that behaviour by Parsoid is as before. Assigning there.",1353121539,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,"Please try to reproduce again, if it's still broken, move it into Parsoid.",1353115094,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,Pushing to next milestone as they did not make it to master by yesterday.,1352832079,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,Mass-moving items into VisualEditor product,1340402753,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+VisualEditor: Handle edit conflicts,"From
+https://www.mediawiki.org/w/index.php?title=Visual_editor/Feedback&oldid=553398#Are_there_edit_conflicts.3F
+----
+I've removed content[1] from previous edits but got no warning about that.
+:Yes, we discovered this during deployment. A priority right away, certainly!
+[1] https://www.mediawiki.org/w/index.php?diff=next&oldid=552684
+----
+
+From
+https://www.mediawiki.org/w/index.php?title=Visual_editor/Feedback&oldid=553398#mid-air_collisions_are_not_detected_.28currently.29
+----
+I ""lost"" my edits due to a mid-air collision. Currently there appears to be no mechanism to detect if someone edits a text which you opened and changed and saved before... I thought we have edit tokens
+----
+
+From
+https://www.mediawiki.org/wiki/Thread:VisualEditor_talk:Welcome/Some_issues
+----
+It looks like the editor disables edit conflict handling. As I appear to have ended up overwriting an other user's edit.
+----
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker
+**URL**: https://www.mediawiki.org/w/index.php?diff=next&oldid=552684",1340368080,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-evnmq44e74m2oihqgr55,task_description,resolved
+VisualEditor: Handle edit conflicts,This is resolved in I002c5aa23704c1c46ef46fa1970a4254614b9eb1 but could be improved as per bug 42522,1354147235,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-evnmq44e74m2oihqgr55,task_subcomment,NA
+VisualEditor: Handle edit conflicts,"Sorry, I should have modified; this is a blocker to deployment in December, but is mostly a transient artefact of the (temporary) integration we're using for MWwiki deployment. The deployments to 'real' wikis from December onwards will be different, and this will not be an issue in the same way.
+
+Thanks for the reminder.",1350932595,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-evnmq44e74m2oihqgr55,task_subcomment,NA
+VisualEditor: Handle edit conflicts,Roan / James: As highest priority was set for this report four months ago I wonder if there's been any progress / work to follow? If not this should probably have a lower priority set.,1350930363,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-evnmq44e74m2oihqgr55,task_subcomment,NA
+VisualEditor: Handle edit conflicts,Mass-moving items into VisualEditor product,1340402765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-evnmq44e74m2oihqgr55,task_subcomment,NA
+VisualEditor: Unable to edit an old revision,"On https://www.mediawiki.org/w/index.php?title=VisualEditor:Welcome&oldid=551728 I click ""edit"", then I'm editing the current version of text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340342220,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-yuwu5opgb5rp2g46lbs3,task_description,resolved
+VisualEditor: Unable to edit an old revision,Resolved in I9e957e6f5bc7920093481ffe3c33e299f87ce50a,1345748642,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-yuwu5opgb5rp2g46lbs3,task_subcomment,NA
+VisualEditor: Unable to edit an old revision,"This is now fixed in Parsoid, please provide the oldid parameter for both GET (DOM retrieval) and POST (DOM -> Wikitext conversion).",1344283134,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yuwu5opgb5rp2g46lbs3,task_subcomment,NA
+VisualEditor: Unable to edit an old revision,Mass-moving items into VisualEditor product,1340402754,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yuwu5opgb5rp2g46lbs3,task_subcomment,NA
+HTML/JS/XSS injection in visual editor (attribute sanitation on links),"Create a new link in the visual editor. Add this text as the link target (including quotes exactly):
+
+"" onmouseover=""alert(document.cookie)"" alt=
+
+When mousing over the link in the editor, you'll get an alert popup with cookie contents. Same occurs in the HTML serialization (""preview"").
+
+
+I notice that ve.Html.makeAttributeList() doesn't do any escaping. Changing it locally to escape the text before putting it into an attribute seems to help on the preview (HTML serialization) but not in the editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://test.wikipedia.org/wiki/Special:VisualEditorSandbox",1328826240,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-lowef3zhz3so2jcgpngl,task_description,resolved
+HTML/JS/XSS injection in visual editor (attribute sanitation on links),Noting bugs closed in the 2012-10-15 release.,1351534215,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lowef3zhz3so2jcgpngl,task_subcomment,NA
+HTML/JS/XSS injection in visual editor (attribute sanitation on links),Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341875,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lowef3zhz3so2jcgpngl,task_subcomment,NA
+HTML/JS/XSS injection in visual editor (attribute sanitation on links),"This is a bug report against old code, but the new code had a similar issue. Now fixed with https://gerrit.wikimedia.org/r/#/c/12550/1",1340319728,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lowef3zhz3so2jcgpngl,task_subcomment,NA
+Narayam not working in contenteditable div,"Narayam not working in contenteditable div. Example for such a  page:  https://www.mediawiki.org/wiki/Special:WebFonts?uselang=ta
+
+Also has impact on visualeditor if contenteditable div is used, as discussed in Bug 33076
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**:   https://www.mediawiki.org/wiki/Special:WebFonts?uselang=ta",1328503560,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-arynstjhbybir4k6knmy,task_description,resolved
+Narayam not working in contenteditable div,https://gerrit.wikimedia.org/r/3731 has the patchset for this issue.,1332756638,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-arynstjhbybir4k6knmy,task_subcomment,NA
+Narayam not working in contenteditable div,"jquery.textselection.js will not work in contenteditable divs. The caretposition, selection range etc are bit different from input fields or textarea. I am looking into this bug",1328505036,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-arynstjhbybir4k6knmy,task_subcomment,NA
+Narayam not working in contenteditable div,"**junu.pv+public** wrote:
+
+I just tried with:
+
+$.narayam.addInputs( '#webfonts-preview-area' );
+
+It does not work.",1328504889,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-arynstjhbybir4k6knmy,task_subcomment,NA
+inArray's use of strict equals in es.ContentView.js may be inappropriate (FIX attached),"**Author:** `acocaracha`
+
+**Description:**
+I've noticed a problem with es.ContentView.js when implementing tex equation support.  When you click text outside an annotation and then click back into the annotation, the new content is determined to have a different type than the surrounding text.  I believe this is because inArray uses strict equals and really the only thing it should be comparing is the type key and I don't think that necessarily needs to be strict (although I guess it could be).
+
+Here is a copy of the old code: https://jalto.net/equationdb/VisualEditor_save/demo/
+
+And the new code: https://jalto.net/equationdb/VisualEditor_old/demo/
+
+Steps to reproduce in old code:
+1) Create an inline equation
+2) Click a different section of the text
+3) Click in the middle of the inline equation
+4) Type something
+
+The new code is working fine.  The commits are:
+
+https://github.com/jalto/VisualEditor/commit/5e544447e5d54b260f5c0333f4dc9da5f15124d7
+
+and
+
+https://github.com/jalto/VisualEditor/commit/0f5a139d24870f200070a95cd70539b04dc0ce33
+
+Thanks,
+
+John
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1326072600,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-x54eh7ootvdxv4yravzz,task_description,invalid
+inArray's use of strict equals in es.ContentView.js may be inappropriate (FIX attached),Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341829,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-x54eh7ootvdxv4yravzz,task_subcomment,NA
+inArray's use of strict equals in es.ContentView.js may be inappropriate (FIX attached),Fixed with new version of VE (code replaced).,1340400649,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-x54eh7ootvdxv4yravzz,task_subcomment,NA
+inArray's use of strict equals in es.ContentView.js may be inappropriate (FIX attached),"**acocaracha** wrote:
+
+Rereading this I should have mentioned I'm new to javascript and in general a bit rusty in programming.  Here is a new commit to fix some of the mistakes I made in the previous ones.  I've done more testing and I think this actually is working now.
+
+https://github.com/jalto/VisualEditor/commit/f9b3cd519420df518c4d0189c32c36ae77a908c6
+
+Again you can see the working copy at https://jalto.net/equationdb/VisualEditor_old/demo/ .  The reason for the old is that I plan to made future changes and I wanted to keep a static copy.",1326303680,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-x54eh7ootvdxv4yravzz,task_subcomment,NA
+MediaWiki Vagrant broken,"I am following [[ https://www.mediawiki.org/wiki/MediaWiki-Vagrant#Quick_start | quick start ]] instructions on a Mac.
+
+```
+$ sw_vers -productVersion
+10.9.5
+```
+
+```
+$ git --version
+git version 2.1.3
+```
+
+```
+$ vboxmanage --version
+4.3.18r96516
+```
+
+```
+$ vagrant -v
+Vagrant 1.6.5
+```
+
+```
+$ git clone ssh://Zfilipin@gerrit.wikimedia.org:29418/mediawiki/vagrant
+Cloning into 'vagrant'...
+remote: Counting objects: 1015, done
+remote: Finding sources: 100% (390/390)
+remote: Getting sizes: 100% (259/259)
+remote: Compressing objects: 100% (127427/127427)
+remote: Total 7887 (delta 94), reused 7780 (delta 91)
+Receiving objects: 100% (7887/7887), 1.88 MiB | 379.00 KiB/s, done.
+Resolving deltas: 100% (3831/3831), done.
+Checking connectivity... done.
+```
+
+```
+$ cd vagrant/
+```
+
+```
+$ git submodule update --init --recursive
+Submodule 'puppet/modules/cdh' (https://gerrit.wikimedia.org/r/operations/puppet/cdh) registered for path 'puppet/modules/cdh'
+Submodule 'puppet/modules/mariadb' (https://gerrit.wikimedia.org/r/operations/puppet/mariadb) registered for path 'puppet/modules/mariadb'
+Submodule 'puppet/modules/nginx' (https://gerrit.wikimedia.org/r/operations/puppet/nginx) registered for path 'puppet/modules/nginx'
+Submodule 'puppet/modules/wikimetrics' (https://gerrit.wikimedia.org/r/operations/puppet/wikimetrics) registered for path 'puppet/modules/wikimetrics'
+Cloning into 'puppet/modules/cdh'...
+remote: Counting objects: 92, done
+remote: Finding sources: 100% (5/5)
+remote: Getting sizes: 100% (4/4)
+remote: Compressing objects: 100% (5690/5690)
+remote: Total 1292 (delta 0), reused 1288 (delta 0)
+Receiving objects: 100% (1292/1292), 250.13 KiB | 171.00 KiB/s, done.
+Resolving deltas: 100% (677/677), done.
+Checking connectivity... done.
+Submodule path 'puppet/modules/cdh': checked out '65335f7d027c635065966a15a7b4467c1ce311b5'
+Cloning into 'puppet/modules/mariadb'...
+remote: Counting objects: 26, done
+remote: Finding sources: 100% (18/18)
+remote: Getting sizes: 100% (8/8)
+remote: Compressing objects: 100% (4224/4224)
+remote: Total 70 (delta 6), reused 66 (delta 6)
+Unpacking objects: 100% (70/70), done.
+Checking connectivity... done.
+Submodule path 'puppet/modules/mariadb': checked out 'b5690999702552cc7fea48b2206f4bb92191d8ca'
+Cloning into 'puppet/modules/nginx'...
+remote: Total 61 (delta 0), reused 61 (delta 0)
+Unpacking objects: 100% (61/61), done.
+Checking connectivity... done.
+Submodule path 'puppet/modules/nginx': checked out '10a1e925fa707654102f39092b46a64c61710614'
+Cloning into 'puppet/modules/wikimetrics'...
+remote: Counting objects: 40, done
+remote: Finding sources: 100% (19/19)
+remote: Getting sizes: 100% (12/12)
+remote: Compressing objects: 100% (23171/23171)
+remote: Total 263 (delta 4), reused 253 (delta 4)
+Receiving objects: 100% (263/263), 57.59 KiB | 0 bytes/s, done.
+Resolving deltas: 100% (118/118), done.
+Checking connectivity... done.
+Submodule path 'puppet/modules/wikimetrics': checked out '5f416bbce4188914f48a044a8df09f1c34b07183'
+```
+
+```
+$ ./setup.sh
+Plugin vagrant-vbguest is already installed
+Installing plugin mediawiki-vagrant-0.2.1.gem
+- Installing the 'mediawiki-vagrant-0.2.1.gem' plugin. This can take a few minutes...
+- Installed the plugin 'mediawiki-vagrant (0.2.1)'!
+Your git/Gerrit username
+Enter 'anonymous' for anonymous access, leave blank to manage it yourself
+git_user: Zfilipin
+
+
+You're all set! Simply run `vagrant up` to boot your new environment.
+```
+
+```
+$ vagrant roles list
+Available roles:
+
+  accountinfo                gwtoolset                  popups                  
+  analytics                  hadoop                     proofreadpage           
+  antispam                   hive                       renameuser              
+  antispoof                  https                      scholarships            
+  apisandbox                 hue                        scribunto               
+  apparmor                   iegreview                  securepoll              
+  babel                      imagemetrics               simple_miser            
+  betafeatures               interwiki                  simple_performant       
+  categorytree               jsduck                     sitematrix              
+  centralauth                jsonconfig                 smtplog                 
+  centralnotice              labledsectiontransclusion   svg                     
+  chromium                   mantle                     templatedata            
+  cirrussearch               massmessage                textextracts            
+  cite                       math                       thumb_on_404            
+  cldr                       mathoid                    timedmediahandler       
+  codeeditor                 mathsearch                 translate               
+  cologneblue                memcached                  uls                     
+  commons                    mleb                       uploadwizard            
+  commonsmetadata            mobileapp                  urlshortener            
+  confirmedit                mobilefrontend             usermerge               
+  doublewiki                 modern                     vectorbeta              
+  echo                       molhandler                 visualeditor            
+  education                  monobook                   warnings_as_errors      
+  elk                        multimedia                 wikidata                
+  eventlogging               multimediaviewer           wikidiff2               
+  featuredfeeds              navigationtiming           wikieditor              
+  flow                       newusermessage             wikigrok                
+  fss                        nuke                       wikihiero               
+  fundraising                oauth                      wikilove                
+  gadgets                    oozie                      wikimediaevents         
+  gadgets2                   pagedtiffhandler           wikimediaincubator      
+  geodata                    pageimages                 wikimediamessages       
+  geshi                      pagetriage                 wikimetrics             
+  gettingstarted             parserfunctions            wikitech                
+  globalcssjs                parsoid                    xhprof                  
+  globaluserpage             pdfhandler                 zend                    
+  graph                      phptags                    zero                    
+  guidedtour                 poem                                               
+
+Roles marked with '*' are enabled.
+Note that roles enabled by dependency are not marked.
+Use `vagrant roles enable` & `vagrant roles disable` to customize.
+```
+",1416497151,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-faneqy7veketsdzp7dgx,task_description,invalid
+MediaWiki Vagrant broken,`vagrant up` worked fine when I deleted //everything// and started with an empty repository.,1416519382,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-faneqy7veketsdzp7dgx,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"Write a Parsoid backend for VirtualRestService, and replace VisualEditor's and Flow's hacks with that. Incorporate the cookie forwarding hacks from VE as well.
+
+See https://www.mediawiki.org/wiki/Requests_for_comment/PHP_Virtual_REST_Service and https://github.com/wikimedia/mediawiki/tree/master/includes/libs/virtualrest
+
+This would also be a good opportunity to clean up the way the Parsoid URL (and whether it's available) is configured in mediawiki-config
+
+See also: T74988",1415656386,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_description,resolved
+Use PHP Virtual REST Service to access Parsoid,"Change 181011 merged by jenkins-bot:
+Use ParsoidVirtualRESTService
+
+[[https://gerrit.wikimedia.org/r/181011]]",1420595467,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"Change 181706 merged by jenkins-bot:
+Make a VirtualRESTService class for Parsoid
+
+[[https://gerrit.wikimedia.org/r/181706]]",1420594186,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"Change 181706 had a related patch set uploaded (by Alex Monk):
+Make a VirtualRESTService class for Parsoid
+
+[[https://gerrit.wikimedia.org/r/181706]]
+
+#patch-for-review",1419380807,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"@krenair: Ahh, great news! @aaron: Thank you! ",1419022316,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,">>! In T1218#935534, @Krenair wrote:
+> I ran into issues with the way I was trying to use VirtualRESTService. My onResponses function was not getting called. Aaron said ""seems like there should be a $execReqsByService for the second loop to over so onReponse is called for non-replaced requests too"" (referring to code in VirtualRESTServiceClient::runMulti)
+
+We fixed the issue I was running into in https://gerrit.wikimedia.org/r/181121, @Aaron made https://gerrit.wikimedia.org/r/181119 to fix the issue we found last night.",1419021688,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"Change 181011 had a related patch set uploaded (by Alex Monk):
+Make a VirtualRESTService class for Parsoid, and use it
+
+[[https://gerrit.wikimedia.org/r/181011]]
+
+#patch-for-review",1419020274,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"I ran into issues with the way I was trying to use VirtualRESTService. My onResponses function was not getting called. Aaron said ""seems like there should be a $execReqsByService for the second loop to over so onReponse is called for non-replaced requests too"" (referring to code in VirtualRESTServiceClient::runMulti)",1418956514,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"It might be nice to model the internal interface somewhat similar to the way the RESTBase interface will look like:
+
+- `GET /v1/local/page/Foo/html/123456` -- HTML for page Foo at revision 123456
+- `GET /v1/local/page/Foo/data-mw/123456` -- data-mw for same
+- `POST /v1/local/convert/html/to/wikitext` -- convert html to wikitext, body tbd
+
+The `local` bit here could be shorthand for the local domain / wiki. Page titles are percent-encoded, so slashes are no problem.
+
+The cookie authentication business should be doable in the virtualrest backend handler for the parsoid end point, so that users don't need to deal with it. The backend is also the only place that needs to deal with actual host names etc from the config.",1418767738,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"It might be nice to model the internal interface somewhat similar to the way the RESTBase interface will look like:
+
+- `GET /v1/local/page/Foo/html/123456` -- HTML for page Foo at revision 123456
+- `GET /v1/local/page/Foo/data-mw/123456` -- data-mw for same
+- `POST /v1/local/convert/html/to/wikitext` -- convert html to wikitext, body tbd
+
+The `local` bit here could be shorthand for the local domain / wiki. Page titles are percent-encoded, so slashes are no problem.
+
+The cookie authentication business should be doable in the parsoid backend handler, so that users don't need to deal with it. The backend is also the only place that needs to deal with actual host names etc from the config.",1418767709,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"It might be nice to model the internal interface somewhat similar to the way the RESTBase interface will look like:
+
+- `GET /v1/local/page/Foo/html/123456` -- HTML for page Foo at revision 123456
+- `GET /v1/local/page/Foo/data-mw/123456` -- data-mw for same
+- `POST /v1/local/convert/html/to/wikitext` -- convert html to wikitext, body tbd
+
+The `local` bit here could be shorthand for the local domain / wiki. Page titles are percent-encoded, so slashes are no problem.",1418767609,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+RfC: Allow styling in templates,"Currently the MediaWiki markup allows the inclusion of html elements with style attributes. Mixing layout with content causes various problems with reusability, maintainability and is not future proof. Already on the mobile version of MediaWiki problems are being seen with inline styles with how pages render on smaller screens which could be solved via css3 media queries, however these cannot be done in inline styles.
+
+It should be possible for templates to have associated stylesheets so that media queries can be applied where necessary. This is related to T37704.
+
+This RFC was proposed in 2013, discussed at two separate RFC meetings in 2014, and the status is unclear as of 2016-03-29.  More detailed status in the comments of this task
+
+Full writeup:
+[[ https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates | Allow styling in templates RfC ]].
+",1411645188,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-urypd4qwlje662u65qd3,task_description,resolved
+RfC: Allow styling in templates,"Nevertheless, it can be closed. The RfC was accepted and the feature implemented, reviewed and deployed; nothing actionable left in this task.",1519785718,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"To be less confusing, let's make this a sub-task instead.",1519319580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Once {T133410} is done, then the exact functionality this task has requested will be in production. So, functionally, this task is a duplicate of that task, which is in process right now.",1519319400,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Once {T483} is done, then the exact functionality this task has requested will be in production. So, functionally, this task is a duplicate of that task, which is in process right now.",1519319385,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,,1505694925,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,,1505665883,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2316983, @MZMcBride wrote:
+> I'm hoping to find some time to play around with TemplateStyles this week. I'm curious whether features such as `url()` will be totally banned or only banned for non-Wikimedia domains. If we're going to disallow certain kinds of CSS (i.e., if we're only going to allow a subset of CSS), we'll want to make sure that the documentation and user interface both make this clear early and often to prevent headaches and frustration.
+
+I presume that anything banned inline is banned in TemplateStyles as well, as they are both 'public access' so to speak. What would be cool is to have some directive to import stylesheets from MediaWiki: space, where CSS is unrestricted.",1464003950,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2239190, @coren wrote:
+> Regardless, it is probably worthwhile to ask what the communities around templates think before we figure it out - at least on the bigger projects.  Ima do this this week.
+
+Is there any follow-up to this? I agree with Brion that restricting TemplateStyles to the Template namespace seems unnecessary. I'm pretty wary of global configuration variables, so if we can kill `$wgTemplateStylesNamespaces`, I think that's a win.
+
+>>! In T483#2293604, @GWicke wrote:
+>> It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?
+> 
+> The <style> tag in the header requires a page-global aggregation pass to collect styles, which would need to be implemented in the PHP parser, Parsoid, VisualEditor, and any other application composing wiki content (such as apps).
+> 
+> The inline stylesheet on the other hand keeps each template expansion self-contained, and avoids the complexity of global passes. It is both easier to implement, and easier to consume.
+
+I looked at T124966 a bit recently. The TemplateStyles extension is scheduled for a security review the week of May 30, according to T133408#2281285. Do you think your implementation concerns are hard blockers to deploying the TemplateStyles extension to Wikimedia wikis in the next few months?
+
+>>! In T483#2289858, @TheDJ wrote:
+> This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+
+It's funny, when I was skimming T133408 and starting to consider the various security concerns, one thought I had was ""thank God we're not trying to start with a CSS preprocessor, variables and functions and a whole embedded programming language would make this crazy difficult to review."" If we get really comfortable with being able to fully sanitize CSS output, I suppose adding a preprocessor wouldn't be totally insane. You'd still need to either do the processing client-side in JavaScript or do sandboxing server-side, the latter being similar to how we deal with embedded Lua, I believe.
+
+I don't think we need to block the deployment of TemplateStyles over preprocessor support, though. Support for a preprocessor would probably happen in this extension at around the same time or after it happens for MediaWiki core (cf. T56864).
+
+I'm hoping to find some time to play around with TemplateStyles this week. I'm curious whether features such as `url()` will be totally banned or only banned for non-Wikimedia domains. If we're going to disallow certain kinds of CSS (i.e., if we're only going to allow a subset of CSS), we'll want to make sure that the documentation and user interface both make this clear early and often to prevent headaches and frustration.",1463973740,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Hi @coren. We're looking at goal options for [[ https://www.mediawiki.org/wiki/Reading/Quarterly_planning/FY2016-2017/Q1#Reading_Infrastructure | Reading Infrastructure in Q1 FY 2016-2017]].
+
+The question arose: is the following something that's still relevant and that you were thinking to pursue?
+
+> Safety/security notes:
+> * need to parse/validate CSS rules for safety anyway -- avoid external refs, scary things
+>  * probably have to do a 'real' CSS parse rather than blacklisting a few keywords like we do on inline styles
+>  * doing this reliably may be the hardest part!
+
+@coren, if it's not on your list (yet still in scope), we were thinking this might be something Reading Infrastructure could work on starting July 2016. If it's already on your list, we would consider a different Reading Infrastructure goal for Q1 FY 2016-2017.
+
+CC @JKatzWMF, @tgr, @anomie",1463679811,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2294327, @matmarex wrote:
+> We do care about IE 8, and even IE 6, as allowing users to view the site with correct styling is a basic core feature of MediaWiki, and therefore we should strive to support grade C browsers here. See https://www.mediawiki.org/wiki/Compatibility#Basic for details.
+
+I'm not sure about this requirement. Right now we are just talking about template styles. Would it be a travesty if these styles didn't apply but an IE6 browser could still use the content? If we were talking about disabling skin styles I would understand but an unstyled infobox is not the end of the world.
+",1463185950,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> We do care about IE 8, and even IE 6
+
+The read-only JS fix for IE8 would work in earlier IE versions as well.",1463180219,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@matmarex, do you expect a drastic increase in the size of the CSS associated with templates? If anything, being able to migrate some inline styles to rules should reduce CSS size somewhat, and compression would pick up repetitions & avoid a significant impact on download sizes. 
+
+Less styles in the <head> can also unblock rendering of above-fold content more quickly, which matters especially on mobile (see T124966).
+
+In any case, I would expect very frequently used transclusions like cite to still be predominantly styled globally. Changing some linked / global CSS is a lot cheaper than re-rendering all of Wikipedia to update a detail in citation styling.",1463180616,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@matmarex, do you expect a drastic increase in the size of the CSS associated with templates? If anything, being able to migrate some inline styles to rules should reduce CSS size somewhat, and compression would pick up repetitions & avoid a significant impact on download sizes. 
+
+Less styles in the <head> can also unblock rendering of above-fold content more quickly, which matters especially on mobile (see T124966).
+
+In any case, I would expect very frequently used transclusions like cite to still be predominantly styled globally. Changing some linked CSS is a lot cheaper than re-rendering all of Wikipedia to update a detail in citation styling.",1463180568,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@matmarex, do you expect a drastic increase in the size of the CSS associated with templates? If anything, being able to migrate some inline styles to rules should reduce HTML size somewhat, and compression would pick up repetitions & avoid a significant impact on download sizes. 
+
+Less styles in the <head> can also unblock rendering of above-fold content more quickly, which matters especially on mobile (see T124966).
+
+In any case, I would expect very frequently used transclusions like cite to still be predominantly styled globally. Changing some linked CSS is a lot cheaper than re-rendering all of Wikipedia to update a detail in citation styling.",1463180280,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@matmarex, do you expect a drastic increase in the size of the CSS associated with templates? If anything, being able to migrate some inline styles to rules should reduce HTML size somewhat, and compression would pick up repetitions & avoid a significant impact on download sizes. 
+
+Less styles in the <head> can also unblock rendering of above-fold content more quickly, which matters especially on mobile (see T124966).
+
+In any case, I would expect very frequently used transclusions like cite to still be predominantly styled globally. Changing some linked CSS is a lot cheaper than re-rendering all of Wikipedia to update a detail in citation styles.",1463179968,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@gwicke Are you suggesting that we duplicate the template stylesheet for every template invocation? That's crazy, and it would be literally the opposite of what this feature is being developed for.",1463179015,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"We do care about IE 8, and even IE 6, as allowing users to view the site with correct styling is a basic core feature of MediaWiki, and therefore we should strive to support grade C browsers here. See https://www.mediawiki.org/wiki/Compatibility#Basic for details.",1463178881,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> Just as side-note: Why would you base64 text? That might result in more data over the wire –after gzipping– like with SVGs laid out here.
+
+Good point! The following seems to work just as well:
+
+```lang=html
+<div id=""mw12345"">
+  <link rel=""stylesheet""
+    href=""data:text/css,#mw12345 { color: red }"">
+  This text is styled red.
+</div>
+```
+
+The main limitation with data URLs is [limited support in IE8](http://caniuse.com/#search=data). Only IE9+ supports stylesheets in data URLs. If we care about IE8, then we could create some JS for a read-only fix-up. VisualEditor does not support IE8, so there is no need to support the more complex editing scenarios.",1463178193,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2293454, @GWicke wrote:
+>             href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+Just as side-note: Why would you base64 text? That might result in more data over the wire –after gzipping– like with [[ https://css-tricks.com/probably-dont-base64-svg/ | SVGs laid out here ]].",1463175760,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2289858, @TheDJ wrote:
+> I was thinking a bit about variance, maintainability etc. And in the mobile-friendly content meeting we were also discussing: How do we document this so that editors know what they should do ?
+> 
+> Lets say we have a block like:
+> ```lang=css
+> @media print and (min-width: 480px)
+> ```
+> 
+> How do we make sure that not every single template has a different cutoff width and thus triggers a reflow? In every single language ?
+> 
+> This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+> 
+> This would make templatestyles a lot more maintainable and consistent, still give lot's of flexibility to editors and also allow us to make changes from the MediaWiki/Wikimedia side.
+
+:thumbsup: This seems very reasonable to me. From user experience _and_ developer perspective it makes sense to choose the media query breakpoints wisely and provide them in a central stylesheet. Less and future CSS offers this capability! ",1463175484,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?
+
+The <style> tag in the header requires a page-global aggregation pass to collect styles, which would need to be implemented in the PHP parser, Parsoid, VisualEditor, and any other application composing wiki content (such as apps).
+
+The inline stylesheet on the other hand keeps each template expansion self-contained, and avoids the complexity of global passes. It is both easier to implement, and easier to consume.",1463169597,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?
+
+The <style> tag in the header requires a page-global aggregation pass to collect styles, which would need to be implemented in the PHP parser, Parsoid, VisualEditor, and any other application composing wiki content (such as apps).
+
+The inline stylesheet on the other hand keeps each template expansion self-contained, and avoids the complexity of global passes.",1463169256,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?
+
+The <style> tag in the header requires a page-global aggregation pass to collect styles, which would need to be implemented in the PHP parser, Parsoid, VisualEditor, and any other application composing wiki content (such as apps).
+
+The inline stylesheet on the other hand keeps each template self-contained, and avoids the complexity of global passes.",1463169189,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2293454, @GWicke wrote:
+> All modern browsers support <link rel=""stylesheet""> in the body
+
+It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?",1463168868,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox, [JSFiddle](https://jsfiddle.net/xpL878ev/)):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in this example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we might be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463168516,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox, [JSFiddle](https://jsfiddle.net/xpL878ev/)):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in this example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we might be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463168014,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox, [JSFiddle](https://jsfiddle.net/xpL878ev/)):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in this example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463167963,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox, [JSFiddle](https://jsfiddle.net/xpL878ev/)):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in the example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463167905,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in the example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463167698,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in the example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future.",1463167560,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prepending all CSS selectors in the example with `#mw12345`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future.",1463167043,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,Ym9keSB7IGNvbG9yOiByZWQgfQ=="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prepending all CSS selectors in the example with `#mw12345`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future.",1463166918,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome is explicitly working on further improvements in how it handles rendering of such styles [1](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,Ym9keSB7IGNvbG9yOiByZWQgfQ=="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prepending all CSS selectors in the example with `#mw12345`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future.",1463166868,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2289895, @GWicke wrote:
+> Adding the parsing team, as this would introduce page-global state, and also needs to work in Parsoid and VE.
+
+I've been pondering on that issue for a bit; clearly there needs to be an API endpoint for parsoid to hit - but I'm not certain what data would be most useful to return; would the final ""merged"" stylesheet be apropriate?
+",1463162334,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Adding the parsing team, as this would introduce page-global state, and also needs to work in Parsoid and VE.",1463073496,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Adding the parsing team, as this would introduce page-global state, and also needs to be implemented in Parsoid and VE.",1463073450,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"I was thinking a bit about variance, maintainability etc. And in the mobile-friendly content meeting we were also discussing: How do we document this so that editors know what they should do ?
+
+Lets say we have a block like:
+```lang=css
+@media print and (min-width: 480px)
+```
+
+How do we make sure that not every single template has a different cutoff width and thus triggers a reflow? In every single language ?
+
+This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+
+This would make templatestyles a lot more maintainable and consistent, still give lot's of flexibility to editors and also allow us to make changes from the MediaWiki/Wikimedia side.",1463072821,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"I was thinking a bit about variance, maintainability etc. And in the mobile-friendly content meeting we were also discussing: How do we document this so that editors know what they should do ?
+
+Lets say we have a block like:
+```css
+@media print and (min-width: 480px)
+```
+
+How do we make sure that not every single template has a different cutoff width and thus triggers a reflow? In every single language ?
+
+This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+
+This would make templatestyles a lot more maintainable and consistent, still give lot's of flexibility to editors and also allow us to make changes from the MediaWiki/Wikimedia side.",1463072785,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"I was thinking a bit about variance, maintainability etc. And in the mobile-friendly content meeting we were also discussing: How do we document this so that editors know what they should do ?
+
+Lets say we have a block like:
+```
+@media print and (min-width: 480px)
+```
+
+How do we make sure that not every single template has a different cutoff width and thus triggers a reflow? In every single language ?
+
+This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+
+This would make templatestyles a lot more maintainable and consistent, still give lot's of flexibility to editors and also allow us to make changes from the MediaWiki/Wikimedia side.",1463072677,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2232623, @brion wrote:
+> If volunteers are +2'ing config updates and deploying them, I'm impressed. :)
+
+Regardless, it is probably worthwhile to ask what the communities around templates think before we figure it out - at least on the bigger projects.  Ima do this this week.",1461674644,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"If volunteers are +2'ing config updates and deploying them, I'm impressed. :)",1461436854,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2232450, @brion wrote:
+> on communities to deal with the question, and on wmf releng to handle updating the setting.
+
+I don't know if you've been watching #wikimedia-site-requests lately but the credit for handling that process really should go to the volunteers involved.",1461436624,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"It seems like an unnecessary burden on users to figure out why it didn't work and ask their communities for permission to change, on communities to deal with the question, and on wmf releng to handle updating the setting.
+
+What downside is there to just having it always on everywhere?",1461430224,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2232314, @brion wrote:
+> Note that people do like to use templates outside the template NS, for user or project pages for instance. Not sure if we want to support that explicitly/implicitly/not at all, etc. :)
+
+It's supported via $wgTemplateStylesNamespaces; whether that is left to just Template: or not when that gets deployed to prod seems to me to be a decision best left to the individual communities.",1461429975,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Note that people do like to use templates outside the template NS, for user or project pages for instance. Not sure if we want to support that explicitly/implicitly/not at all, etc. :)
+",1461423840,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"With the latest rounds of merges, the TemplateStyles extension appears to be in a reasonable state and implements the major substantive part of this RfC as discussed in Jerusalem.
+
+An interesting side effect of the current implementation is that a `<templatestyles>` tag appearing on a page //not// appearing in the list of allowed namespaces will not - as designed - affect pages transcluding it but it **does** style //itself// regardless of namespace.
+
+I'm not sure that shouldn't simply be documented as a feature.  :-)",1461419944,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Change 283772 merged by jenkins-bot:
+Add unit tests for CSSParse and CSSRender
+
+[[https://gerrit.wikimedia.org/r/283772]]",1461183515,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2223326, @Edokter wrote:
+> I think scoping to `#mw-content-text` should be enough. Any tempate appearing outside actual content is usually protected anyway.
+
+I would tend to agree; let's not overcomplicate the first go at this and aim for an implementation that is simple to implement //and// describe: template styles allow styling of contents.
+
+I think there's a good case to be made that styling UI elements is outside the scope of this extension; it's a marginal use at best and should probably be left to some other mechanism (especially since fiddling with the UI is very skin-specific and depends a great deal on the actual interface in use).
+",1461168666,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,I think scoping to `#mw-content-text` should be enough. Any tempate appearing outside actual content is usually protected anyway.,1461158655,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Would it be safer to introduce this feature as only available on admin-protected templates?  Then we could relax that requirement gradually once the issues are better understood and have been prevented..?,1461120083,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2218236, @Edokter wrote:
+> Actually, plenty of templates can appear outside 'content' space, such as edit notices. Those should be able to be styled. The risk of clashing CSS classes is pretty low anyway.
+
+In addition to the desirability of avoiding clashes, there is also the issue that part of the objective of placing styling in templates is to allow non-administrator the ability to edit styles - which means that we need to protect most UI elements from accidental (or malicious) alteration.
+
+It might be worthwhile to consider alternatives by which UI elements can be styled in controlled contexts, but I think this is a good project for a future version.  :-)
+",1461119524,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2215393, @Entlinkt wrote:
+> It should probably be avoided that templates can leak styles into that area.
+
+Actually, plenty of templates can appear outside 'content' space, such as edit notices. Those should be able to be styled. The risk of clashing CSS classes is pretty low anyway.",1461079820,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2211010, @TheDJ wrote:
+> We have `#mw-content-text` that contains all generated output for wikitext pages, but more importantly the classes `mw-content-ltr` and `mw-content-rtl`.
+
+Please note that in diff views, `#mw-content-text` also contains the `table.diff` element with the actual diff, revert links etc. It should probably be avoided that templates can leak styles into that area.
+
+I don't know of any selector that precisely catches user-generated content. Currently, `#mw-content-text` is just an approximation.",1461009856,PHID-USER-4j6uu43bpl65dnji6462,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Change 283772 had a related patch set uploaded (by coren):
+Add unit tests for CSSParse and CSSRender
+
+[[https://gerrit.wikimedia.org/r/283772]]
+",1460823433,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2211010, @TheDJ wrote:
+> Right, found a quite important point... We are now scoping using:
+> `mw-body-content` it seems. But that is a skin specific class, amongst others not used by the mobile minerva skin.
+> 
+> We have `#mw-content-text` that contains all generated output for wikitext pages, but more importantly the classes `mw-content-ltr` and `mw-content-rtl`.
+
+Aha.  Good catch.  Fixing.",1460772104,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Right, found a quite important point... We are now scoping using:
+`mw-body-content` it seems. But that is a skin specific class, amongst others not used by the mobile minerva skin.
+
+We have `#mw-content-text` that contains all generated output for wikitext pages, but more importantly the classes `mw-content-ltr` and `mw-content-rtl`.",1460743734,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2210556, @Legoktm wrote:
+>>>! In T483#2209954, @TheDJ wrote:
+>> Tried [[ http://ts.wmflabs.org/w/index.php?title=Template%3AWide_image&type=revision&diff=124&oldid=121 | using wikimarkup inside the style block ]], but that doesn't seem to work (and scary if it would..)
+> 
+> What if you used `{{#tag:templatestyles}}` so the wikitext is processed? I'm not sure how the extension is storing the actual styles though.
+
+It's stored as a serialized parse tree of the rules; the processing would happen exactly once on save, then parsed as CSS and stored in a fixed format.
+",1460738047,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209954, @TheDJ wrote:
+> Tried [[ http://ts.wmflabs.org/w/index.php?title=Template%3AWide_image&type=revision&diff=124&oldid=121 | using wikimarkup inside the style block ]], but that doesn't seem to work (and scary if it would..)
+
+What if you used `{{#tag:templatestyles}}` so the wikitext is processed? I'm not sure how the extension is storing the actual styles though.",1460736262,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209954, @TheDJ wrote:
+> Tried [[ http://ts.wmflabs.org/w/index.php?title=Template%3AWide_image&type=revision&diff=124&oldid=121 | using wikimarkup inside the style block ]], but that doesn't seem to work (and scary if it would..)
+
+That wouldn't have worked even if the tag was parsed: the stylesheet is parsed on save and stored as a page property for use by transcluding pages, so it cannot differ from one transclusion to another.",1460736209,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209954, @TheDJ wrote:
+> Some first practical experiences:
+> 1: i quickly found a situation, where in lieu of inline styles, i'll have to use a unique (per parserrun) class or ID. we have no good options for this right now. For now, i'll keep using inline styles for those situations. (width specific to the image being transcluded)
+
+There isn't a good option for this that I can think of.  Certainly, ""new"" best practices would be to avoid such parametrization entirely whenever at all possible since they play poorly with window width and mobile in all cases.  I expect most cases can be reduced to a smaller set of limited options, though (say, ""auto, 75%, 100%"").
+
+At the very least, it then becomes possible to override such variation in a `@media` block with a `!important`; so the situation is ""less bad"" than it otherwise might have been.
+
+> 2: the style block should probably be inserted AFTER the <meta name=""ResourceLoaderDynamicStyles"" content=""""/>
+
+The point of insertion is actually picked by core (in `OutputPage::addInlineStyle()`); we'd need to check whether that's the best spot in all contexts.
+
+> 3: These style blocks will have to be exposed in the api, so that something like LivePreview can update them.
+> 4: The style block will need an identifying attribute, so that something like livepreview can replace it.
+
+I'm not familiar enough with LivePreview to evaluate what that entails.  I'll have to look into it.
+
+> 5: Every conditional styling option of a template will require it's own class (always included). For instance, even if I don't use the border option of  http://ts.wmflabs.org/w/index.php/Template:Wide_image, I will always have to include the .noborder styling class. This might be more bytes and more unused styling classes for uses of certain templates.
+
+I //expect// that's not a significant issue in practice; that duplication is probably offset by the fact that multiple inclusions of the same template cause the styles to be inlined only once and that using a class more than once within the same template removes the repetition of the inline style.
+
+That said, it's theoretically possible to omit classes that are not in fact used on the page - the selectors for every rule are known at the point of insertion.  That would, however, require non-trivial parsing of the document and is probably best left to after we have determined that there is an issue to fix.
+",1460736023,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209954, @TheDJ wrote:
+> Some first practical experiences:
+> 1: i quickly found a situation, where in lieu of inline styles, i'll have to use a unique (per parserrun) class or ID. we have no good options for this right now. For now, i'll keep using inline styles for those situations. (width specific to the image being transcluded)
+
+There isn't a good option for this that I can think of.  Certainly, ""new"" best practices would be to avoid such parametrization entirely whenever at all possible since they play poorly with window width and mobile in all cases.  I expect most cases can be reduced to a smaller set of limited options, though (say, ""auto, 75%, 100%"").
+
+At the very least, it then becomes possible to override such variation in a `@media` block with a `!important`; so the situation is ""less bad"" than it otherwise might have been.
+
+> 2: the style block should probably be inserted AFTER the <meta name=""ResourceLoaderDynamicStyles"" content=""""/>
+
+The point of insertion is actually picked by core (in `OutputPage::addInlineStyle()`); we'd need to check whether that's the best spot in all contexts.
+
+> 3: These style blocks will have to be exposed in the api, so that something like LivePreview can update them.
+> 4: The style block will need an identifying attribute, so that something like livepreview can replace it.
+
+I'm not familiar enough with LivePreview to evaluate what that entails.  I'll have to look into it.
+
+> 5: Every conditional styling option of a template will require it's own class (always included). For instance, even if I don't use the border option of  http://ts.wmflabs.org/w/index.php/Template:Wide_image, I will always have to include the .noborder styling class. This might be more bytes and more unused styling classes for uses of certain templates.
+
+I ''expect'' that's not a significant issue in practice; that duplication is probably offset by the fact that multiple inclusions of the same template cause the styles to be inlined only once and that using a class more than once within the same template removes the repetition of the inline style.
+
+That said, it's theoretically possible to omit classes that are not in fact used on the page - the selectors for every rule are known at the point of insertion.  That would, however, require non-trivial parsing of the document and is probably best left to after we have determined that there is an issue to fix.
+",1460735945,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Some first practical experiences:
+1: i quickly found a situation, where in lieu of inline styles, i'll have to use a unique (per parserrun) class or ID. we have no good options for this right now. For now, i'll keep using inline styles for those situations. (width specific to the image being transcluded)
+2: the style block should probably be inserted AFTER the <meta name=""ResourceLoaderDynamicStyles"" content=""""/>
+3: These style blocks will have to be exposed in the api, so that something like LivePreview can update them.
+4: The style block will need an identifying attribute, so that something like livepreview can replace it.
+5: Every conditional styling option of a template will require it's own class (always included). For instance, even if I don't use the border option of  http://ts.wmflabs.org/w/index.php/Template:Wide_image, I will always have to include the .noborder styling class. This might be more bytes and more unused styling classes for uses of certain templates. Not really sure what to do about that... Tried [[ http://ts.wmflabs.org/w/index.php?title=Template%3AWide_image&type=revision&diff=124&oldid=121 | using wikimarkup inside the style block ]], but that doesn't seem to work (and scary if it would..)",1460729380,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Done.  I added ParserFunctions and Scribunto, and reimported Template:Wide image recursively to make sure it worked.",1460726048,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209633, @TheDJ wrote:
+> Coren, can you add parserfunctions extension to your experimental wiki ?
+> i'd like to test a few actual en.wiki templates, and almost all of those need parserfunctions and/or scribunto
+
+Yeah, those and a couple others really - will do so shortly.",1460724697,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Coren, can you add parserfunctions extension to your experimental wiki ?
+i'd like to test a few actual en.wiki templates, and almost all of those need parserfunctions and/or scribunto",1460724423,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2207021, @coren wrote:
+> The current WIP can be played with [[ http://ts.wmflabs.org/w/index.php/Main_Page | on an experimental wiki ]].  The main page is an example of a transclusion of a style template.
+
+[[http://ts.wmflabs.org/w/index.php?title=Template:Boilerplate&action=edit|Direct link to the styled template]]",1460652612,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,The current WIP can be played with [[ http://ts.wmflabs.org/w/index.php/Main_Page | on an experimental wiki ]].  The main page is an example of a transclusion of a style template.,1460645012,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Change 282155 merged by jenkins-bot:
+TemplateStyles extension prototype
+
+[[https://gerrit.wikimedia.org/r/282155]]",1460227082,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Change 282155 had a related patch set uploaded (by coren):
+[WIP] TemplateStyles extension prototype
+
+[[https://gerrit.wikimedia.org/r/282155]]
+",1460065630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Current plan summary based on the etherpad notes (in case they get lost):
+* use mechanism similar to TemplateData
+ * extension tag to encapsulate a CSS chunk directly in the template's wikitext
+ * note supporting media queries is super important for mobile & narrow-window views!
+ * use save hook to validate & store the style data
+* have parser pull up the style data of all used templates when rendering out a page
+ * build them into a <style> tag (this keeps style & html versions consistent within parsercache, and is simpler than trying to load lots of deps via ResourceLoader)
+
+That much should be pretty easy to prototype.
+
+Encapsulation notes:
+* one idea is to do the template styles only on properly balanced templates
+ * encourage people to 'do the right thing' with templates ;)
+* this allows wrapping the template in a (custom?) html element which can be added to the prefix of any CSS rules in the template
+ * should prevent leakage of defined rules outside the template
+ * which should also prevent conflicts in styles and class/id names between templates
+ * but requires parsing the CSS well enough to be able to reliably prefix all selectors
+
+Safety/security notes:
+* need to parse/validate CSS rules for safety anyway -- avoid external refs, scary things
+ * probably have to do a 'real' CSS parse rather than blacklisting a few keywords like we do on inline styles
+ * doing this reliably may be the hardest part!
+
+Editor helper tools:
+ * jon is interested in a helper tool to look for suspicious inline styles and warn users on edit that their page or template is likely to render badly on mobile/narrow window
+ * if we're parsing & storing metadata on the css styles, we can build a tool to look for common/duplicated styles and suggest moving truly common ones to MediaWiki:Common.css
+
+Open questions:
+* what about style libraries to be shared between templates? (maybe not a high prio; truly common styles can go in existing MediaWiki:Common.css)",1459685891,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"After some architecture discussion with @Brion and @jdlrobson, we came up with a fairly good plan for which I'm going to do a first prototypical implementation.
+
+The summary: styles are to be added inline to the template (with a mechanism comparable to that of templatedata and/or outright coopting that mechanism), combined at page rendering time, and placed inline with the page.  We avoid redundancy by eschewing true scoped styles, opting to make them global instead.
+
+//Faux//-scoping is provided for balanced templates by making certain they are encapsulated and given a class that is then used as a selector for the template's declared classes; this would ideally rely on T114445 to avoid duplicating effort.",1459685613,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Notes from @Jdlrobson @coren & @brion at Wikimedia Hackathon 2016: https://etherpad.wikimedia.org/p/WikiHack16_TemplateStyles
+
+@coren is interested in doing some prototyping work.
+",1459685142,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#1884696, @Jdlrobson wrote:
+> Any update on this?
+
+This was moved into the ""Approved, but not resourced"" column in T483#1073658 (@daniel, 2015-02-27).  The answer to ""what happens next?"" when an RFC reaches that state is admittedly unclear; #ArchCom doesn't have the ability to assign developers to things, and should be very stingy about volunteering their own time.  There are some old action items documented @brion and @tstarling from the RFC meeting on 2014-10-15, but that doesn't seem relevant today.
+
+Given that the  [[ https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates | Allow styling in templates RfC ]] writeup on mw.org states that the author is ""Jon Robson who no longer has time to move this forward"" and the state marked there is ""stalled"", it's tempting to treat the RFC as abandoned, were it not for the frequent mentions this task gets, and @Jdlrobson adding this as a blocker to resolving @ori's bug report T130846.
+
+Looking at the history on the  [[ https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates | Allow styling in templates RfC ]] page, it would seem that this needs a new driver who is probably not @brion.  For tasks in the #ArchCom-RFC, we have been provisionally using (misusing?) the assignment field as where we assign the shepherd.  I think it potentially makes sense for @brion to remain the shepherd, but someone else needs to be the driver for this.
+
+Any volunteers to drive this? 
+",1459319067,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Any update on this?,1450282910,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"From https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-10-15-21.02.html
+
+* ACTION: tim interested in helping with the css parsing, may port some tools from node if nothing good already in php (brion, 21:46:56)
+* ACTION: accepted styling in templates, work & final details to be done by brion & tim (brion, 21:50:58)",1425052965,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Found logs that say APPROVED here: https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-10-15-21.02.html,1425052920,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Seems to be stalled after an inconclusive discussion on 2014-03-26: https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-26
+
+** ''LINK:'' https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates  (sumanah, 21:11:10)
+** ''LINK:'' https://www.mediawiki.org/wiki/Requests_for_comment/Deprecating_inline_styles was an older RfC that Jon abandoned in favour of ""Allow styling in templates""  (sumanah, 21:11:10)
+** ''LINK:'' https://www.mediawiki.org/wiki/Talk:Architecture_Summit_2014/UI_styling#Allow_styling_in_templates We discussed this topic during the Architecture Summit in January  (sumanah, 21:11:10)
+** the next steps from January said - Jon & friends would lock down some details, code up a prototype/working beta with some sample templates, and so on by about the end of March.  (sumanah, 21:11:31)
+** Jon wants: ""some agreement on the way forward and someone with time to write the code to get this kicked off :)  i've been a bit swamped recently""  (sumanah, 21:12:00)
+** (we were supposed to talk about this in February https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-02-27 but ran out of time in that meeting)  (sumanah, 21:12:54)
+** ''LINK:'' https://www.mediawiki.org/wiki/Requests_for_comment/Associated_namespaces  (marktraceur, 21:14:15)
+** Jon looked at supporting style tags rather than separate wiki pages for styles, per discussion at the summit, and it was nasty and required messing with the parser.  https://gist.github.com/anonymous/9262427  (sumanah, 21:23:36)
+** discussion of having a separate Template:Foo.css page; see https://gerrit.wikimedia.org/r/68123  (sumanah, 21:23:36)
+** discussion of sanitizing/making secure CSS and <style> content, and performance implications of having a separate CSS bundle  (sumanah, 21:23:36)
+** ''IDEA:'' could we have ResourceLoader bundle it?  (sumanah, 21:23:36)
+** ''HELP:'' Jon needs help writing the code to get this kicked off  (sumanah, 21:30:20)
+** <YuviPanda> However we do this, this would definitely need ops buy in of some sort (at least notifications)  (sumanah, 21:33:01)
+",1425052262,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Also related: {T37704}.,1418413724,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Related: {T52644}.,1418413421,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> Brion interested in this
+> will update the RfC w/ implementation plans and schedule it for next weekish
+
+https://www.mediawiki.org/wiki/Architecture_committee/2014-10-08#RFCs_to_triage",1412804918,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+Document a process to request new projects,"On Day 1 we will need a process to request a new project, because plain users will not be able to create projects themselves.
+
+In fact, we need such progress already now in this Labs instance. We can define the process as we document it, and fine tune it as we see fit, real request after real request.
+
+I have started a draft at https://www.mediawiki.org/wiki/Phabricator/Help. @aklapper & co, feel free fine tuning it while satisfying the current requests for Labs.",1405443204,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_description,resolved
+Document a process to request new projects,//importing issue status//,1410486132,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-08-04 16:42:20 (UTC)`
+
+I'm resolving this task because we have a process in place:
+
+https://www.mediawiki.org/wiki/Phabricator/Help#Requesting_a_new_project
+
+We will mature the process as we define T68, and with the experience acquired.",1410486132,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**aklapper** wrote on `2014-07-28 19:32:47 (UTC)`
+
+Heja, let's please move the naming scheme discussion to T68 where we have more target audience (PMs). I will comment on concerns and thoughts brought up here in T68.",1410486132,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-28 14:50:42 (UTC)`
+
+@Rush, thank you for the long explanation but I have to say that I still disagree.
+
+Your argument is based on the assumption that people memorize and type entire URLs. This is why having ""sane"" URLs is key for you, and the rest needs to be adapted to this assumption, sacrificing the use of natural language in the UI.
+
+I believe for most users the UI goes first, and using natural language there makes them happier. Phabricator, web links, search engines, and users' browsers will deal with the full URLs. This is what happens nowadays in most web services, including Wikipedia and our developer infrastructure sites.
+
+Summarizing my opinion:
+
+* Using original project names in Phabricator makes them easier to type and find.
+* Project names are used as simple tags, except in the case of explicit subprojects of an existing project à la ""Product - Component"". No ""MediaWiki-Extensions-Etc"".
+* Since projects are proper nouns, by default they use the regular Title Case. Other uses of case are allowed only when the original project name uses them (e.g. GoogleLogin, VisualEditor, MySQL, FOSDEM)
+
+> mediawiki-extensions-googlelogin ftw
+
+Two reasons why this is not a good solution:
+
+# If you search for ""googlelogin"" or any substring, you will not find this project in the search engine or via typeahead in a new task. If the project has separate words like ""MediaWiki Extensions GoogleLogin"" then yes, starting to type ""Goo..."" the project will appear and the user can just select it. Test this by typing ""Dashes"" or ""dashes"". ""[[ http://fab.wmflabs.org/project/view/61/ | test-project-dashes ]]"" will never show up, while ""[[ http://fab.wmflabs.org/project/view/62/ | Test Project Dashes Searchable ]]"" will as soon as you type ""D"" or ""d"". If all what users know is the project name, they will find it only with separate words.
+# Considering the importance of typeahead in Phabricator, we want to avoid having hundreds of entries starting with ""mediawiki..."" or ""wikimedia..."". Users with a problem in ""GoogleLogin"" will come and start typing that string directly. This is not Git/Gerrit or Bugzilla, we don't need to reflect any tree structure. Phabricator is about tags. What is important about ""GoogleLogin"" is that users can find it or reference it easily. Therefore the best is to use the name as is.",1410486131,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Florian** wrote on `2014-07-28 12:02:33 (UTC)`
+
+@Rush: So you would suggest to use always lowercase project namens? But the extension/project itself can still be named ""as it is"" with CamelCase and/or whitespaces?",1410486131,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Rush** wrote on `2014-07-25 18:38:35 (UTC)`
+
+Sorry, my lack of response to that wasn't meant to be opaque or rude, I've been trying to figure out the best way to make the argument.
+
+I've been here before and the culmination of my thinking boils down to 'oh no not again!', but that's a really difficult thing to communicate.  I'm hoping I can at least relate challenges I see here from previous experience.
+
+===The case of tags===
+
+This exists: http://fab.wmflabs.org/project/view/40/
+
+Only nobody remembers project 40, everyone remembers the name shown at the top as `Trusted User Tool`, the most common way to reference a project when projects reach a certain scale, especially in Phabricator, is via the `/tag/name` mechanism.  Only that doesn't work out for this name. 
+
+This doesn't exist: http://fab.wmflabs.org/tag/Trusted%20User%20Tool/
+This doesn't exist: http://fab.wmflabs.org/tag/Trusted_User_Tool/
+
+This does exist: http://fab.wmflabs.org/tag/trusted_user_tool/
+
+Technically per [spec](http://en.wikipedia.org/wiki/URL_encoding) the above should work out the spacing UTF8 as %20 and that should be fine, but as anyone who has done url encoding is aware users do not understand URL encoding.  Thus the human option of replacing %20 control character with '_'.  Which I think is the sanest option, and we should mimic it, to do otherwise is to intentionally create a disparity in how a project is referenced.
+
+If we don't follow the Phabricator standard we now have two names for one thing.  This inconsistency means we end up with a page in the wiki that boils down to ""how to translate your project name into the tag name"".  Because it isn't precisely URL spec, even if you ignore the case sensitivity issues.
+
+Versus:
+
+This exists: http://fab.wmflabs.org/project/view/47/
+This exists: http://fab.wmflabs.org/tag/operations-core/
+
+===On readability and flat namespacing===
+
+Taking the case of https://www.mediawiki.org/wiki/Extension:GoogleLogin
+
+Because the project namespace is flat we have to infer hierarchy (sub grouping) with a mostly sane single string naming scheme
+
+Bugzilla:
+
+    Mediawiki
+      -> Extensions
+         -> GoogleLogin
+
+Phabricator:
+
+    mediawiki-extensions-googlelogin
+
+Or
+
+    Mediawiki-Extensions-GoogleLogin
+
+We are representing the same hierarchy and maintaining namespace isolation consistency with this paradigm.  googlelogin is ambiguous while mediawiki-extensions-googlelogin is not.
+
+Taking this camel case idea down the line it becomes things like:
+
+ResearchAndReview-GrantProposals-Ready
+
+versus encouraging lower case and readability:
+
+research-grantmaking
+
+We are labeling things more than we are naming them.  Eventually it becomes necessary to follow proper noun usage with things like: GoogleReady-OAuth-LoginProtocol.  The limitations of flat namespacing mean we end up with 10, 20, 30 and up character strings for which the CAmELCase usecase is not more readable except in the simplest of cases.  
+
+Once we start doing camel case it will be an issue of having to respect all proper nouns which make strings less readable, and going back because we realize it's adding far more problems than it creates readability it will be impossible.  The intangible problem of why some `Projects` are now `projects` is essentially very difficult culturally.  External references all end up inconsistent if we try to change this later.
+
+===URL's and Case===
+
+So when creating a project name we are really creating a URL reference for a bucket of objects.  This isn't the same with other things within the Phabricator landscape.  We don't try to hit phab.com/theawesometicket or phab.com/myawesomelegalagreement.  We do reference phab.com/tag/project-foo.  When you get right down to [it](http://tools.ietf.org/html/rfc4343) case sensitivity and URL's is confusing.  Technically, case should be ignored in the FQDN.  Google.com and GOOGLE.com are equivalent, but should be respected in the trail.  GOOGLE.com/foo and google.com/Foo are distinct.  Even that falls apart though because different server implementations can handle those cases in different ways.  Even the w3 takes a pragmatic approach.  See http://www.w3.org/TR/WD-html40-970708/htmlweb.html and http://www.w3.org/tr/wd-html40-970708/htmlweb.html where rather than respecting the case sensitivity they just redirect, which is pretty much the sane approach for reference documentation like that I guess.  But demonstrates the weirdness.
+
+Shown out of love:
+
+yes: http://en.wikipedia.org/wiki/case_sensitivity
+yes: http://en.wikipedia.org/wiki/Case_sensitivity
+no: http://en.wikipedia.org/wiki/CASE_SENSITIVITY
+
+So projects are going to be directly referenced as URL's and URL's are finicky.  There are [characters](http://tools.ietf.org/html/rfc3986#section-2) that are OK to use as project names in the absolute sense -- it won't stop you, but are not valid in a URL
+
+I've been doing a lot of testing for how we can move the namespace from bugzilla to phabricator and it has only reinforced these ideas.
+
+Right now in bugzilla we have names that when translated look like: one-two-three/four
+
+This isn't a valid project reference, because it is not a valid URL.  That only works as phab.com/tag/one-two-three_four/
+
+If we allow characters in project names that are not valid in a URL we are going to make things much harder for us and users.
+
+===Referencing===
+
+Projects are also referenced in remarkup as well but this comes with its own inconsistencies. As an example you can refer to user @rush and project #operations-requests.  But if we allow non-standard URL characters such as spaces we end up with these cases:
+
+no : #Trusted User Tool
+yes: #Trusted_User_Tool
+yes: #trusted_user_tool
+
+Note the same happens for ampersand:
+
+project `foo_and_bar` is fine: `foo_and_bar`
+project `foo&bar` is *not* fine: `foo_bar`
+
+The way this is handled under the covers is this reference is a ""hashtag"", and since it's infeasible to parse out spaced tags it is converted to the i_am_snake_case whenever a project with a space is created. That means we have two cases within the context of phabricator ignoring the /tag/Trusted User Tool fiasco, it can't be referenced as project in remarkup within any text field as written.
+
+===Character Groupings===
+
+Probably allowed: 
+
+`abcdefghijklmnopqrstuvwxyz0123456789-._~:[]!'()*+,;=`
+
+Missing due to custom use: 
+
+`# @`
+
+Missing due to inconsistency in reference or incompatbility:
+
+ `ABCDEFGHIJKLMNOPQRSTUVWXYZ&?/`
+
+
+===tl;dr=== 
+
+we are going to regret allowing things to be named in ways that create inconsistent references across the application.  please let's not do this and condemn ourselves to explaining it every day for the next ten years 
+
+
+`mediawiki-extensions-googlelogin` ftw",1410486131,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-25 13:55:28 (UTC)`
+
+@Rush, see {T495}. It's a project creation request with a strict CamelCase name. You said this is a problem. I asked why and provided my reasons to avoid project names with lower case only and dashes. What is the conclusion?",1410486130,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-17 11:38:14 (UTC)`
+
+I had what I needed, I only couldn't see it.
+
+Anyway, I have simplified the instructions to request a new project. It all boils down to create a task specifying the name and description of the project, and a reasoning for special access permissions if the defaults don't work for you. 
+
+There is a note for teams expecting to create several projects. Those will need to start with a project for the team.
+
+https://www.mediawiki.org/wiki/Phabricator/Help#Requesting_a_new_project
+
+I will start testing this process with {T458}.",1410486130,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Rush** wrote on `2014-07-16 19:01:19 (UTC)`
+
+@qgil, I""m not sure what you are looking at?
+
+your a phab admin (meant in both senses)
+your in security group
+phabricator-request-project is all users for all fields
+http://fab.wmflabs.org/T458 is all users for all fields
+
+what perm screen are you looking for?
+",1410486129,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-16 18:57:07 (UTC)`
+
+@Rush I still can't access the admin options to check the possible permissions...",1410486129,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Rush** wrote on `2014-07-16 15:26:16 (UTC)`
+
+@qgil you are now security! ",1410486129,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-16 12:05:52 (UTC)`
+
+>>! In T457#7, @Rush wrote:
+> * I'm not sure how we limit comment ability unless it's the broader view/edit permissions?
+
+This might be because I had to recall the types of permission by heart. Can I get momentarily admin access to check those permissions, document accordingly, and then give back (again) the admin rights, please?",1410486128,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-16 11:54:30 (UTC)`
+
+>>! In T457#7, @Rush wrote:
+> * Naming scheme should depend on the type of project (these determine the icon and picture and maybe color?)
+> 
+> -- work queues (buckets for work to be organized into...overlapping)
+> -- group of people
+> -- straight up tag
+
+Documented at https://www.mediawiki.org/wiki/Phabricator/Help
+ 
+>  * In order to have a naming scheme projects can't be editable by users once created?  Otherwise we spend a lot of time ensuring consistent levels of abstraction, and organization and then it's all out the window post-creation process.  
+
+Yes, ideally projects can only be renamed by the Phabricator Request Project members.
+
+ 
+> * Project creation isn't a super user priv, just one that requires understanding how this stuff is organized for consistency across the install.   I would say, team leads, etc can create?  Assuming reasonable good faith in the context for people we trust.
+
+I would leave it to Phabricator Request Project memberr, or even something more precise like ""Phabricator Project Creators"", and then invite there whoever needs to create projects regularly and understands the drill.
+
+
+> * This one is sure to be fun :)  projects should be not be camel case, also known as lower case only please.
+
+??? ""Wikimedia Phabricator Day 1"" results in http://fab.wmflabs.org/tag/wikimedia_phabricator_day_1/ automatically.
+
+> this type of reference being pretty standard we are going to dig ourselves into a weird space where Security is a project in the project field, yet /tag/Security doesn't reference the object (/tag/security does).
+
+How do you get "" /tag/Security"" apart from typing it manually? Why is this is a problem? I'd rather give preference to a human friendly interface, where projects can be defined with natural names.
+
+About project members, is there a need to define them when requesting a new project? We can create ""Project X"" with the user requesting its creation as member, and then set permissions so that the ""Project X"" team can invite new members, right?",1410486128,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Rush** wrote on `2014-07-15 18:13:13 (UTC)`
+
+@MissGayle I'm not sure yet how to respond since the process itself doesn't exist :)
+
+Ok, so a few general thoughts re: project creation I have been hoarding...
+
+* Naming scheme should depend on the type of project (these determine the icon and picture and maybe color?)
+
+-- work queues (buckets for work to be organized into...overlapping)
+-- group of people
+-- straight up tag
+
+ * In order to have a naming scheme projects can't be editable by users once created?  Otherwise we spend a lot of time ensuring consistent levels of abstraction, and organization and then it's all out the window post-creation process.  
+
+* Project creation isn't a super user priv, just one that requires understanding how this stuff is organized for consistency across the install.   I would say, team leads, etc can create?  Assuming reasonable good faith in the context for people we trust.
+
+* This one is sure to be fun :)  projects should be not be camel case, also known as lower case only please.
+
+There are a few reasons but the most overt can be demonstrated like this:
+
+this exists: http://fab.wmflabs.org/project/view/40/
+
+Often referenced within the install as http://fab.wmflabs.org/tag/<project>
+
+But, only lower case non-space references work:
+
+http://fab.wmflabs.org/tag/trusted_user_tool/
+
+this type of reference being pretty standard we are going to dig ourselves into a weird space where Security is a project in the project field, yet /tag/Security doesn't reference the object (/tag/security does).  That is how it works currently, and it's already confusing and weird.
+
+That means spaces and capitals within a project name force an inconsistency in reference
+
+* Before creating people centric projects for assigning of rights, etc.  An effort should be made to ensure it doesn't exist as another name already. (same logic applied all around I guess)
+
+* For non-people oriented projects restricting who can join them, not sure if it makes sense?
+
+* I'm not sure how we limit comment ability unless it's the broader view/edit permissions?
+
+* The who can join/edit/see type permissions need to be specified in phabricator user account terms
+or group terms
+
+Using the request here as a first-through-the-breach  instance I have done this:
+
+http://fab.wmflabs.org/T458
+
+Mostly for discussion...
+
+
+tl;dr to get a new project:
+
+* create a request task and associate http://fab.wmflabs.org/tag/phabricator-request-project/
+* gets reviewed in same manner as a gerrit change, etc.  Can be commented on, certain people can do the work, etc
+
+",1410486128,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**MissGayle** wrote on `2014-07-15 17:42:18 (UTC)`
+
+What're the naming conventions?
+
+project name following the naming conventions (link)
+- Talent & Culture Office
+description including the purpose of the project -- you will be able to edit it after the project has been created
+- Tracking HR projects and key deliverables in a transparent manner
+access policies -- the defaults are public view and equal access for all registered users
+- public 
+who can view the project and tasks (list options, default Public)
+- public 
+who can join the project (list options, default ?)
+- anyone in HR (Gayle, Anna Stillwell, Joady Lohr, Anna Lantz, Emanuela Neagu, Heather McAndrew, Emily Blanchard, Jenn Suzuki, Elena Hernandez) 
+who can edit tasks (list options)
+- anyone in HR (Gayle, Anna Stillwell, Joady Lohr, Anna Lantz, Emanuela Neagu, Heather McAndrew, Emily Blanchard, Jenn Suzuki, Elena Hernandez) 
+who can add comments (list options)
+- anyone
+(are there more sensible options?)",1410486127,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects",Currently the process (except for security) https://www.mediawiki.org/wiki/Backporting_fixes implies usage of flags.,1397887689,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_description,resolved
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","@MarkAHershberger, @Mglaser: Task 76168 got backported to 1.24. Not sure if you want the #MediaWiki-Tarball-Backports project to be added to that task. https://www.mediawiki.org/wiki/Backporting_fixes#Backports_to_stable.2Fsupported_release does not cover this ""retroactively"" - whatever works for you and isn't overhead.",1417656886,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects",">>! In T101#11104, @Aklapper wrote:
+> Project names: ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports""
+> 
+> as usual confused whether the action to create and set up these two projects should now be separate tasks...
+
+@greg, @MarkAHershberger, @mglaser: I have created #WMF-Server-Backports and #MediaWiki-Tarball-Backports and added you accordingly. Was unsure which [[ https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Type%20project | type/kind of project ]] these are so I sticked with the default (briefcase/blue) for the time being.",1417057965,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","We do not migrate any flag data from Bugzilla so this does not block T259.
+
+Project names: ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports""
+
+Closing the ""figure out a process"" part as resolved, as usual confused whether the action to create and set up these two projects should now be separate tasks...",1413283003,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","Are there any more details that must be decided here? We really need to close this task, or at least have it in a state where it is not blocking T259 anymore.
+
+In other words, the period for input to the migration script needs to end. We can always file tasks based on the results of {T552}.",1413026975,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects",">>! In T101#9607, @Aklapper wrote:
+> **Project naming:**
+> 
+> ""WMF-Backports"" and ""MediaWiki-Backports"" doesn't feel explanatory enough to me. Sounds too similar to other subprojects which have a defined codebase area. ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" will work for me. Let's go for that?
+
+I'll probably make a short version for WMF-Server-Backports (aka ""WMF-Backport""), but sure :)   (just like I made ""#releng"" for ""#Release-Engineering"")
+
+
+> **Bugzilla Backport Flags migration aspect only:**
+> 
+> Tickets with any of our two Bugzilla flags (Backport_WMF and Backport_to_Stable) set will not have the flag information migrated to Phabricator. I don't see any historical need to know whether something was backported at some undefined point in the past (and that information is available in comments anyway if somebody is curious).
+> 
+> Regarding currently open tickets with Backport requests that have not been decided on, there are less than 10 of them hence the effort is not worth it to write migration code covering that.
+> I have cleaned up WMF backport requests yesterday and I've sent an email today to the Tarball Release Team to please take a look at the queue of undecided tarball backport requests. 
+> Furthermore Bugzilla will be available as read-only for some time after the migration so we could still look up which Bugzilla tickets had this flag if we wanted.
+
+Probably fine. We can get backport information from git but it'll obviously not have the bug info (if there was a bug).",1412806878,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**Project naming:**
+
+""WMF-Backports"" and ""MediaWiki-Backports"" doesn't feel explanatory enough to me. Sounds too similar to other subprojects which have a defined codebase area. ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" will work for me. Let's go for that?
+
+**Bugzilla Backport Flags migration aspect only:**
+
+Tickets with any of our two Bugzilla flags (Backport_WMF and Backport_to_Stable) set will not have the flag information migrated to Phabricator. I don't see any historical need to know whether something was backported at some undefined point in the past (and that information is available in comments anyway if somebody is curious).
+
+Regarding currently open tickets with Backport requests that have not been decided on, there are less than 10 of them hence the effort is not worth it to write migration code covering that.
+I have cleaned up WMF backport requests yesterday and I've sent an email today to the Tarball Release Team to please take a look at the queue of undecided tarball backport requests. 
+Furthermore Bugzilla will be available as read-only for some time after the migration so we could still look up which Bugzilla tickets had this flag if we wanted.",1412781221,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","No strong opinion either, and no willingness to bikeshed at all. Just trying to apply a principle of starting simple, knowing that we can write more complex names if the simple are confusing.",1411569958,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","> WMF-Backports?
+
+No strong opinion - just not sure if that's clear enough, keeping in mind that we will also have projects like ""Wikimedia-Site_requests"" after importing from Bugzilla, see T43
+
+> MediaWiki-Backports?
+
+...and that would be in a Product-Component row with stuff like ""MediaWiki-Categories"", ""MediaWiki-Page_editing"" and so on, but the different color and tag (like a keyword) might be sufficient.",1411568380,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","Could we simplify the name? WMF-Backports?
+What about backports to MediaWiki releases? MediaWiki-Backports?",1411560539,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","Alright, let's keep it simple for the start: Create a ""Backport_to_WMF_servers"" project in Phabricator and ask interested people (@greg, SWAT) to become members of that project (so they are subscribed to the project) or even ""watch"" that project (more or less the same).
+
+Anybody can propose a backport for the fix of a task by adding ""Backport_to_WMF_servers"" to the Projects list for a task (similar to setting that flag in Bugzilla which also wasn't very discoverable, so not much worse). 
+We'll fall back to adding comments (and closing tasks) for clarification when a commit has been backported. 
+It's not better or worse than Bugzilla currently, where there's also some ambiguity whether to keep a ticket open or resolved when a fix has been merged into git master vs. all the wmf branches: It boils down to defining social workflows.
+
+Documentation in https://www.mediawiki.org/wiki/Backporting_fixes will need updates.
+
+We can still iterate on a more sophisticated solution after having migrated Bugzilla content.",1411558630,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","We need to define the process to be applied here and now.
+
+>>! In T101#21, @flimport wrote:
+> **greg** wrote on `2014-08-28 22:27:10 (UTC)`
+>> **Question2**: I //do not// see a way in Herald to define a rule ""Projects | name includes the string | WMF_server_deployment"" though, so somebody tell me I'm wrong that this would require subscribing to each project created every week? Uhm.
+> 
+> I couldn't find anything useful. I assume some script somewhere will be creating this projects (not Phab itself), so maybe the logic of who should be subscribed could stay in that script for now?
+
+Such script doesn't exists today...
+
+>> **Fallback:** If my questions above indeed do make things complicated, we could also start simple and stupid with a generic ""Backport_to_WMF_servers"" project, and could switch to a more sophisticated process later on when Phabricator provides more functionality (cf. release notes) needed.
+> 
+> I'm fine with that.
+
+So this might be it for now.",1411312636,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**Mglaser** wrote on `2014-08-28 22:33:43 (UTC)`
+
+Sounds like a good start. I assume the project ""MediaWiki_tarball_release"" will be generic and always points to the next maintenance release. It is then within the scope of the release team to decide whether to backport this to legacy and lts releases as well, right? ",1410485344,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**greg** wrote on `2014-08-28 22:27:10 (UTC)`
+
+>>! In T167#36, @aklapper wrote:
+> So it sounds like James and Greg want separate ""WMF server deployment 2014-05-29 (1.24wmf7)""-style projects for each weekly deployment.
+
+something, even just 1.XXwmfYY would be fine with me (dates may change due to holidays etc, so predicting them is hard, and we may change our deploy cycle/cadence in the future, too)
+ 
+> **Question1**: If above was possible (release notes) and we automatically set such a project: If a task with that ""deployment of the week""-project set is reopened (e.g. not entirely fixed) and that project entry isn't removed from the task, wouldn't the next person looking at the task interpret it as a backport request, if I understand the proposed logic correctly?
+
+If a task is reopened then who ever is triaging those should move the project to the latest 1.XXwmfYY project. That should be clear enough.
+(This is where I want Launchpad's per project status... but I digress)
+
+> **Question2**: I //do not// see a way in Herald to define a rule ""Projects | name includes the string | WMF_server_deployment"" though, so somebody tell me I'm wrong that this would require subscribing to each project created every week? Uhm.
+
+I couldn't find anything useful. I assume some script somewhere will be creating this projects (not Phab itself), so maybe the logic of who should be subscribed could stay in that script for now?
+
+> **Fallback:** If my questions above indeed do make things complicated, we could also start simple and stupid with a generic ""Backport_to_WMF_servers"" project, and could switch to a more sophisticated process later on when Phabricator provides more functionality (cf. release notes) needed.
+
+I'm fine with that.
+",1410485344,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-08-27 19:23:17 (UTC)`
+
+And to summarize what this task is about in one sentences: ""define a process to mark tasks which have merged commits in git master and those commits should be backported into 1.24wmf123 and deployed on the Wikimedia servers, and automatically notify those folks doing backports and deployments by adding such a ""backport"" project to such a task""",1410485344,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-08-27 19:20:32 (UTC)`
+
+@greg, @jdforrester: Any comments? I'm leaning towards ""keep it simple and stupid"" at the beginning, due to the open questions in my previous comment which sound cumbersome and error-prone.",1410485343,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-08-18 13:54:53 (UTC)`
+
+So it sounds like James and Greg want separate ""WMF server deployment 2014-05-29 (1.24wmf7)""-style projects for each weekly deployment.
+
+I have not tried yet if we can add such a ""deployment of the week""-project by default: ""If task is closed as ""resolved"" in certain timeframe, automatically set project X"" for the sake of getting release notes by running one Maniphest query. Need to play more with [[https://secure.phabricator.com/book/phabricator/article/herald/ | Herald]] rules which are pretty powerful.
+
+**Question1**: If above was possible (release notes) and we automatically set such a project: If a task with that ""deployment of the week""-project set is reopened (e.g. not entirely fixed) and that project entry isn't removed from the task, wouldn't the next person looking at the task interpret it as a backport request, if I understand the proposed logic correctly?
+
+So currently the summary would currently be:
+* Security issues will be handled via a ""Security"" project. Out of discussion/focus here.
+* For non-security fixes/bugs that are candidates to backport, we are going to use projects/tags:
+** ""WMF_server_deployment_2014-05-29_(1.24wmf7)"" (specific)
+** ""MediaWiki_tarball_release"" (generic, we can still change that)
+* People can and should follow (=receive mail notifications from Phabricator) these projects by setting up a personal [[ https://secure.phabricator.com/book/phabricator/article/herald/ | Herald ]] rule in Phabricator. **Question2**: I //do not// see a way in Herald to define a rule ""Projects | name includes the string | WMF_server_deployment"" though, so somebody tell me I'm wrong that this would require subscribing to each project created every week? Uhm.
+* General info: Projects can be marked as archived (e.g. tarballs that have been released) so they are not offered anymore.
+
+**Fallback:** If my questions above indeed do make things complicated, we could also start simple and stupid with a generic ""Backport_to_WMF_servers"" project, and could switch to a more sophisticated process later on when Phabricator provides more functionality (cf. release notes) needed.
+
+General reminder on the old ""one task can only have one task status"" vs. ""we have 'branches' being git master, versions on servers, and tarballs"" problem: Each Project board allows custom columns, and a task can belong to more than one project.
+
+(And now to bikeshed about our [[http://fab.wmflabs.org/project/query/advanced/ | favorite icon and color]]. Not!)",1410485343,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**Mglaser** wrote on `2014-07-17 09:29:33 (UTC)`
+
++1 to @greg wrt security releases. 
+
+Another question is whether we need to be able to differentiate between backport to current stable and backport to legacy/lts. In particular, this would be useful during pre-release / RC phases, where we want to get some of the master changes still into the tarball. Using a separate flag might be a bit over-organized, though.",1410485342,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**greg** wrote on `2014-07-16 16:58:31 (UTC)`
+
+>>! In T167#32, @aklapper wrote:
+>>>! In T167#28, @Nemo_bis wrote:
+>> Discussion above is focused on 1 out of 3 backport processes. Were MediaWiki release managers asked to comment?
+> 
+> The ""backport to deployed version on WMF servers"" process isn't that different to the ""backport to stable branch for next tarball release"" process and feels sufficiently covered to me.
+
++1 to ""backport to WMF servers"" and ""backport to stable releases"" are basically the same; I see zero substantial difference. So that's 2 of 3 use cases.
+
+The last use case, security releases, will be handled differently than the other 2 use cases, and it basically won't change in the world of Phab. We'll still have a Security private project, and we'll still make security releases from those bugs, er, tasks. We don't have a ""Backport to Security Release"" flag because all security bugs are private and in the same queue together already, a flag would be redundant.",1410485342,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-07-16 14:57:33 (UTC)`
+
+>>! In T167#28, @Nemo_bis wrote:
+> Discussion above is focused on 1 out of 3 backport processes. Were MediaWiki release managers asked to comment?
+
+The ""backport to deployed version on WMF servers"" process isn't that different to the ""backport to stable branch for next tarball release"" process and feels sufficiently covered to me.
+
+As written in T166, subprojects in https://secure.phabricator.com/T3670 will probably the way to go here too.",1410485342,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**Nemo_bis** wrote on `2014-06-12 06:40:48 (UTC)`
+
+Discussion above is focused on 1 out of 3 backport processes. Were MediaWiki release managers asked to comment? https://www.mediawiki.org/wiki/Backporting_fixes#Backports_to_stable.2Fsupported_release
+(Added Markus; I don't find hexmode.)",1410485341,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**jdforrester** wrote on `2014-05-30 15:56:48 (UTC)`
+
+>>! In T167#23, @greg wrote:
+>>>! In T167#21, @jdforrester wrote:
+>> We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" //etc.//. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+> 
+> I think that might be overkill initially, honestly. But I can be convinced otherwise.
+
+If we don't do it for WMF-wide we'll need to do it for VisualEditor at least to preserve the existing milestones which are used to tracking bugs, regressions, patches and so on… The feedback we've had from community members is that the clarity of deployment target on every bug (for Phabricator, read: task) and patch is that it's been very helpful and clear for them in understand what has changed and when.
+
+Also, I'd presume (hope!) that it would allow us to no longer create [[ https://www.mediawiki.org/wiki/MediaWiki_1.24/wmf7/Changelog | mw:MediaWiki 1.24/wmf7/Changelog ]] and its ilk, but instead have it neatly and usefully listed on the project ""WMF server deployment 2014-05-29 (1.24wmf7)"".",1410485341,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**jdforrester** wrote on `2014-05-30 15:55:32 (UTC)`
+
+>>! In T167#26, @aklapper wrote:
+>> We'd discussed creating a project for each deployment – so reproducible etc.. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+> 
+> I've also copied this comment to T166 as it relates not only to **backporting**. If we managed to //automatically// add a ""WMF server deployment 2014-05-29 (1.24wmf7)"" project to tasks whose status is set to resolved based on a timeframe, that would be lovely and would drop the need for a separate ""Backport to WMF servers"" project, as one could query for open tickets where that project was //manually// added.
+
+Yeah; I was thinking that it would also answer the ""what things are being proposed for backport to MW 1.23?"" with a ""MediaWiki 1.23"" project.",1410485341,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-05-30 15:37:56 (UTC)`
+
+> We'd discussed creating a project for each deployment – so reproducible etc.. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+
+I've also copied this comment to T166 as it relates not only to **backporting**. If we managed to //automatically// add a ""WMF server deployment 2014-05-29 (1.24wmf7)"" project to tasks whose status is set to resolved based on a timeframe, that would be lovely and would drop the need for a separate ""Backport to WMF servers"" project, as one could query for open tickets where that project was //manually// added.",1410485340,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**greg** wrote on `2014-05-29 22:17:33 (UTC)`
+
+>>! In T167#24, @jdforrester wrote:
+> Also, I'd presume (hope!) that it would allow us to no longer create [[ https://www.mediawiki.org/wiki/MediaWiki_1.24/wmf7/Changelog | mw:MediaWiki 1.24/wmf7/Changelog ]] and its ilk, but instead have it neatly and usefully listed on the project ""WMF server deployment 2014-05-29 (1.24wmf7)"".
+
+I'm convinced.",1410485340,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**greg** wrote on `2014-05-29 21:52:29 (UTC)`
+
+>>! In T167#21, @jdforrester wrote:
+> We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" //etc.//. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+
+I think that might be overkill initially, honestly. But I can be convinced otherwise.
+
+
+
+>>! In T167#19, @aklapper wrote:
+> Greg: Any opinions here?
+> 
+> Currently I favor creating a generic ""Backport to WMF servers"" project and making you subscribe to that project's notifications by you setting up a rule in Maniphest's Herald.
+
+I like this. Also a ""Backport to MediaWiki Releases"" project that the Release Team subscribe to.",1410485340,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**jdforrester** wrote on `2014-05-29 15:36:02 (UTC)`
+
+>>! In T167#19, @aklapper wrote:
+> Greg: Any opinions here?
+> 
+> Currently I favor creating a generic ""Backport to WMF servers"" project and making you subscribe to that project's notifications by you setting up a rule in Maniphest's Herald.
+
+We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" //etc.//. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.",1410485339,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-05-26 13:44:20 (UTC)`
+
+Greg: Any opinions here?
+
+Currently I favor creating a generic ""Backport to WMF servers"" project and making you subscribe to that project's notifications by you setting up a rule in Maniphest's Herald.
+
+(Note to myself: Updating the docs on https://www.mediawiki.org/wiki/Backporting_fixes is covered by T350)",1410485339,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**qgil** wrote on `2014-04-23 13:51:20 (UTC)`
+
+""query that project regularly"" = [[ https://secure.phabricator.com/book/phabricator/article/herald/ | Herald ]]
+
+We still need to play with that tool and see what can it offer.",1410485339,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-04-23 06:37:15 (UTC)`
+
++1 for using a project and making people responsible for backports receive automatic notifications about it, or query that project regularly (social thing to solve, not technical).",1410485338,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**qgil** wrote on `2014-04-22 18:02:51 (UTC)`
+
+It looks like Phabricator provides enough elements for us to define this process.",1410485338,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**qgil** wrote on `2014-04-19 16:11:19 (UTC)`
+
+Create a ""Backport WMF"" project and add the related tasks to that project? This could be used in combination with release projects and what not, see T166. ",1410485337,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+Decide how to organize iterations and releases,"Related task upstream: [[ https://secure.phabricator.com/T390#21 | Implement project types ]].
+
+I don't understand how we're going to mark release milestones: each release a blocked task, kept open for each sub-point release until the RELX_Y branch in question is frozen?
+(Due to http://fab.wmflabs.org/T164 we can't have two levels of dependency so I suppose we'll instead give up on granularity.)
+
+A handful of MediaWiki extensions are maintained by teams who use sprints, so the sprints could then be mapped to the RELX_Y branch in which they first appear and to the corresponding task; in this case (in theory) we'd gain, for no cost, that WMF work would be visible to tarball users.
+",1397886924,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_description,resolved
+Decide how to organize iterations and releases,I consider this task decided/resolved/closed.,1413266763,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,Works for us.  I like the rainbow.,1413247789,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"Thumb ups from me, this fits my team's workflow.",1413203234,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"Are there any more details that must be decided here? We really need to close this task, or at least have it in a state where it is not blocking T259 anymore.
+
+In other words, the period for input to the migration script needs to end. We can always file tasks based on the results of {T552}.",1413026715,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,">>! In T100#9608, @Aklapper wrote:
+> Trying to keep it simple for the start: Combine one color with one icon.
+
+Deal.
+
+> * Projects have a {icon briefcase} Briefcase icon (and blue color).
+> * Releases have a {icon truck} Release icon (and orange color).
+> * Sprints have a {icon calendar} Deadline icon (and some other color - indigo? shrug).
+> * For completeness: Cross-project 'keywords' (Bugzilla terminology) have a {icon tag} Tag icon (and red color I think).
+
+Yes to most points, but look what I've done instead: {M4}
+
+Let's finish the discussion about icons and colors in the mockup.",1412790085,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"Happy for the VisualEditor TMs to be magically transformed into projects to which each Bugzilla item is transferred as appropriate, but yes, we really need to keep that data if at all possible.",1412784445,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**Target Milestone data migration:**
+
+Sorry, this fell through the cracks and this is not entirely 'ready to go' yet but close.
+
+I'm currently checking the use of Target Milestones in Bugzilla products, and which TMs are in the past so I can disable setting these TMs in Bugzilla (cleaning up but need to talk to several teams), and which TMs are rubbish (see e.g. https://bugzilla.wikimedia.org/show_bug.cgi?id=71807 ).
+
+Projects in Bugzilla using Target Milestones:
+* Huggle (3 TMs, 3 of them active)
+* MediaWiki (15 TMs, 6 of them active)
+* MediaWiki extensions (8 TMs, 5 of them active)
+* MediaWiki skins (1 TMs, 1 of them active but TM set on 0 tickets)
+* VisualEditor (89 TMs, 89 of them active but asked James if past ones could be made inactive)
+* Wikimedia (1 active TM called 'Mysterious future' which I want to delete, see https://bugzilla.wikimedia.org/show_bug.cgi?id=71807)
+* Wikipedia App (2 TMs, 0 active)
+
+**Question:** Not sure if that makes things more complicated or not in the migation logic hence question might not make sense: I'm wondering whether we could/should ignore past TMs (TMs that are 'not active' / cannot be set anymore on Bugzilla tasks) and not necessarily migrate them into //archived// projects in Phabricator. On the other hand we'd lose data, e.g. which VisualEditor bug was fixed at which time, hence probably going for archived makes more sense.
+
+In any case, Bugzilla TMs should become deadline or release projects. See my previous comment.",1412784244,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"Different/separate tags for project (e.g. '{icon briefcase} VisualEditor') which covers all tasks in a project, vs. release (e.g. '{icon truck} VisualEditor 1.0.1') and vs. deadline (e.g. '{icon calendar} VisualEditor 2014-12-24').
+
+Trying to keep it simple for the start: Combine one color with one icon.
+
+* Projects have a {icon briefcase} Briefcase icon (and blue color).
+* Releases have a {icon truck} Release icon (and orange color).
+* Sprints have a {icon calendar} Deadline icon (and some other color - indigo? shrug).
+* For completeness: Cross-project 'keywords' (Bugzilla terminology) have a {icon tag} Tag icon (and red color I think).",1412782089,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"I just created a project for the [[ https://phabricator.wikimedia.org/T18 | Engineering Community October 2014 ]] sprint. A sprint is not a release, so I used another icon: {icon calendar}
+
+Sprints could have a color on their own, or they could have the same as releases, not to end up with a full-fledged rainbow.",1412715249,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"I got a bit lost with the discussion above and what we will start doing right now. Different tags for project and release, or single tags ""project + release""?
+
+Above you have covered stable MediaWiki releases 1.xx and also WMF weekly releases 1.xx-wmfZZ. Could we also add months as in yyyy-mm for those teams organizing monthly sprints? This is the case of at least Engineering Communty, but I imagine we are not the only ones.
+
+PS: enthusiastic thumbs up for {icon truck}!",1411312173,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"I got a bit lost with the discussion above and what we will start doing right now. Different tags for project and release, or single tags ""project + release""?
+
+Above you have covered stable MediaWiki releases 1.xx and also WMF weekly releases 1.xx-wmfZZ. Could we also add months as in yyyy-mm for those teams organizing monthly sprints? This is the case of at least Engineering Communty, but I imagine we are not the only ones.
+
+PS: enthustastic thumbs up for {icon truck}!",1411312160,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"I got a bit lost with the discussion above and what we will start doing right now. Different tags for project and release, or single tags ""project + release""?
+
+Above you have covered stable MediaWiki releases 1.xx and also WMF weekly releases 1.xx-wmfZZ. Could we also add months as in yyyy-mm for those teams organizing monthly sprints? This is the case of at least Engineering Communty, but I might imagine we are not the only ones.
+
+PS: enthustastic thumbs up for {icon truck}!",1411312112,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-08-10 19:58:22 (UTC)`
+
+For the time being (as implementing subprojects might take too long for us in upstream), the basic idea is to use projects (tags) in Phab, differentiating types via icons and colors. For releases (""target milestones"" in Bugzilla), imagine a truck tag for example, or check out the preliminary screenshot. 
+
+Not entirely set in stone yet and just to show the basic idea. All kudos goes to Chase.
+Sigh, as I get an ""Upload Failure"" both with Chrome and Firefox here, external link to screenshot: [[ http://home.arcor.de/ak-47/tmp/Phab-Project-Tags-T46.png ]]",1410485335,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**SG** wrote on `2014-07-10 20:27:36 (UTC)`
+
+That does seem like it would fit our needs. It's slightly less clunky than our proposed solution.",1410485335,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-07-06 20:35:34 (UTC)`
+
+Upstream decided to try subprojects in https://secure.phabricator.com/T3670 (makes our T240 a WONTFIX), which ""will make an attack on sprints/milestones/versions."" This might make our life easier?",1410485334,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**jdforrester** wrote on `2014-06-09 18:16:52 (UTC)`
+
+>>! In T166#40, @aklapper wrote:
+>  * Planning to fix a task in a past version (backporting to servers; only applies for //WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//)
+
+Actually, we also do this for releases – tagging bugs as things that need to get fixed in 1.23.1 for example.  However, I don't think it makes a major difference.
+
+> So.... does this novel make any sense?
+
+Yes! It looks good. I'd suggest having a ""Backport to MediaWiki releases"" project for the MW release maintainers as well, but yes, it works for us.",1410485334,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**mmodell** wrote on `2014-06-09 17:51:24 (UTC)`
+
+Documenting when a big fix got released should be simple because you can link a git commit to a task as well as linking differential revisions. It would be trivial to traverse the git log from the newest commit to find the next release tag that occurs between the relevant commit and HEAD. That version tag can be exposed In the task ui as the first release containing the fix.",1410485334,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-06-06 17:14:12 (UTC)`
+
+Spent the afternoon thinking about this item. Please show me that I'm wrong and that this can be made less complex.
+
+**Underlying assumptions:**
+* On branching for a new //xx// in //WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//: No fix for a task / commit can be included in //WMF server deployment 1.xx-wmfZZ// which would not also automatically be included in //tarball 1.xx-rc// or //tarball 1.xx.0//. In other words: When switching from //WMF server deployment 1.23-wmf26// to //WMF server deployment 1.24-wmf0//, the //tarball// branch for 1.23 gets created at the very same time.
+* The term ''version'' in the rest of this comment refers to a string like //1.xx.y// or //1.xx-wmfZZ// or //Sprint 1// or //yyyy-mm-dd//. It might also be an //iteration// or a //sprint// (simplified as several //iterations// can become a //release// / //version//, but I really got to start somewhere).
+* We do not rename projects which include versioning in their names as it would make ChangeLog creation (and burndown charts?) impossible. Discussed above in T166.
+
+**Situations we face:**
+ * Planning to fix a task in a future version (//WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//, would automatically also end up in //tarball 1.xx.0//)
+ * Planning to fix a task in a past version (backporting to servers; only applies for //WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//)
+ * Documenting that a task got resolved in a timeframe (cf. ChangeLog), hence fixed in //WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//, would automatically also end up in //tarball 1.xx.0//. (TODO: No idea if this could be set automatically, but that would be lovely.)
+ * Documenting that a task planned for a version (well, rather explicitly //sprint// in this case) was planned but did //not// get resolved in that timeframe.
+
+**Conflict about interpreting versions (//affected// vs //fixed in//):**
+* If we reflect //versions// in or via //project names//, we easily end up with a semantic conflict when the task is closed as resolved: Was that version //affected// by the bug reported in the task? Or did that version include a //fix// for the bug reported in the task?
+* I tend towards using //Versions which include a fix for a problem/task// because planning is more important in a task management tool than info about the version used by the task's reporter. This must be clearly expressed in our docs (T350).
+* Making this clear is also important for projects with sprints / release cycles not aligned with WMF deployment cycles (also keep 3rd party development in mind).
+
+**Getting notified about backporting requests (T167):**
+ * Refering to the situation //Planning to fix a task in a past version (backporting to servers)//; the third assumption says //We do not rename projects which include versioning in their names//.
+ * In practice it means that when 1.xx-wmfZZ gets deployed on the first WMF servers, Release Management (Greg etc) would have to subscribe via Herald to watch the project //WMF server deployment 1.xx-wmfZZ// in order to get notifications whenever a task is added to that project (= a request to backport).
+ * The same thing would happen every 7 days (for //WMF server deployment 1.xx-wmfZZ+1//, etc.) which sounds really cumbersome and error-prone.
+ * Instead we might want to have a ""static""/""generic"" //Backport to WMF// project so people don't have to subscribe to its notifications every week?
+ * Once a backport has been granted and merged, the task must be edited by removing the //Backport to WMF// project and by adding the //WMF server deployment 1.xx-wmfZZ// project. Disadvantage here: We'd lose statistics on how often we need to backport stuff.
+ * TODO: We might also have to document that the task whose fix should get backported must remain open (T350), not sure how flexible the notification system is.)
+
+Based on that above assumptions can be considered correct, we might end up with these things //in parallel//:
+ * generic projects: //MediaWiki// (covered in T68; task reporters are encouraged to set them)
+ * sprint/iteration projects: //Team XYZ Sprint 23 (2014-05-08)//
+ * WMF server deployment projects: //Fixed in WMF server deployment 1.xx-wmfZZ//
+ * One generic WMF backport request project release management should subscribe to: //Backport to WMF servers//
+ * For projects not following the WMF server deployment or MediaWiki tarball release schedule: //Fixed in $projectname x.y.z//
+
+Tarball release projects (like //MediaWiki release 1.xx.y//) for fixed/resolved tasks would not be needed if the aforementioned first assumption on branching holds true, as one could query for all tasks in project //WMF server deployment 1.xx-wmfZZ// where 0 ≤ ZZ ≤ 26. 
+Though I am not convinced if that would be discoverable enough to 3rd party MediaWiki users in order to find out in which tarball version a fix is supposed to be included - TODO: might need to document that.
+
+So.... does this novel make any sense?",1410485333,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-05-30 21:40:04 (UTC)`
+
+In this case, renaming projects is not an option.
+
+Wouldn't the workboard of <sprint/deployment> be enough?",1410485333,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**jdforrester** wrote on `2014-05-30 21:35:40 (UTC)`
+
+>>! In T166#37, @qgil wrote:
+> Maybe this sounds silly, but what about
+> 
+> # Work on the tasks at project ""WMF server deployment 2014-05-29 (1.24wmf7)"".
+> # By the end of 2014-05-29, some tasks will be resolved and forgotten, others will remain open.
+> # Rename the project to ""WMF server deployment 2014-06-05 (1.24wmf8)"".
+> # Add the new tasks you want to complete in addition to the ones you still have open.
+> 
+> If you don't like the idea of simply renaming projects for whatever obscure archiving reason, then ""Edit batch"" selecting ll open tasks of a project can make wonders. Not automatic but still pretty simple.
+
+Where would the static links to ""tasks fixed in <sprint/deployment>"" and ""code landed in <sprint/deployment>"" live? That's one of the key needs from my POV. ",1410485333,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-05-30 19:19:49 (UTC)`
+
+Maybe this sounds silly, but what about
+
+# Work on the tasks at project ""WMF server deployment 2014-05-29 (1.24wmf7)"".
+# By the end of 2014-05-29, some tasks will be resolved and forgotten, others will remain open.
+# Rename the project to ""WMF server deployment 2014-06-05 (1.24wmf8)"".
+# Add the new tasks you want to complete in addition to the ones you still have open.
+
+If you don't like the idea of simply renaming projects for whatever obscure archiving reason, then ""Edit batch"" selecting ll open tasks of a project can make wonders. Not automatic but still pretty simple.",1410485332,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**jdforrester** wrote on `2014-05-30 15:53:56 (UTC)`
+
+>>! In T166#33, @aklapper wrote:
+> Copying @jdforrester's comment from T167:
+> 
+>> We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" etc.. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+> 
+> If we did that, we might want to be able to //close projects if they are in the past// (disable adding a project to a task). Now I need to find out if that's possible already, and if not I'll upstream.
+> 
+> The problem I see is that we'd want to add such a ""Deployment Target Milestone"" project to tasks automatically in the long run: Closing a task in a certain timeframe in a certain project should automatically add this project to the task. Which will be a complex feature request.
+
+That'd be a nice-to-have, but we don't have it on Bugzilla and I manage it manually instead. The important thing would be an automtic ""add change to project"", which presumably we could do as part of the script that currently posts the list on MediaWiki.org?",1410485332,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-05-30 15:39:17 (UTC)`
+
+Answering my own question thanks to upstream IRC:
+
+> we might want to be able to close projects if they are in the past (disable adding a project to a task).
+
+<mikkn>  If you go to Projects then click on the project in question, then edit, you will have an ""Archive Project"" button there",1410485331,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-05-30 15:16:16 (UTC)`
+
+Copying @jdforrester's comment from T167:
+
+> We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" etc.. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+
+If we did that, we might want to be able to //close projects if they are in the past// (disable adding a project to a task). Now I need to find out if that's possible already, and if not I'll upstream.
+
+The problem I see is that we'd want to add such a ""Deployment Target Milestone"" project to tasks automatically in the long run: Closing a task in a certain timeframe in a certain project should automatically add this project to the task. Which will be a complex feature request.",1410485331,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-05-15 14:07:55 (UTC)`
+
+At the teampractices mailing list there is a discussion about [[ http://lists.wikimedia.org/pipermail/teampractices/2014-May/000411.html | how to organize sprints ]]. While [[ https://secure.phabricator.com/T390#21 | the upstream solution ]] arrives, it would be good to know how Phabricator users do this nowadays.
+
+As far as I can see, the process seems to be something like this:
+
+# A //Project X// exists containing several tasks. Optionally, a team is created for it.
+# A new //Project X Sprint 1// project is created. The tasks from //Project X// to be included in the sprint are tagged accordingly. The only relation between these projects is their naming convention. For Phabricator these are independent projects. Herald rules can be created to assign to //Project X// any task created for //Project X*// automatically.
+# At the end of the sprint, //Project X Sprint 1// is archived and //Project X Sprint 2// is created. The remaining tasks of Sprint 1 can be moved to the next sprint with a single batch edit.
+
+There are some manual steps that in the future should be automatized, but other than that the process seems to be simple enough? Creating projects is simple, you only need to add a title and, if you wish, you can copy & paste a stock description. Membership of these subprojects is not relevant. If you want to set some special permissions for the developer team you can simply set those permissions to the //Project X// team.",1410485331,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**mattflaschen** wrote on `2014-04-29 04:30:12 (UTC)`
+
+>  (Due to http://fab.wmflabs.org/T164 we can't have two levels of dependency so I suppose we'll instead give up on granularity.)
+
+Do you mean that you can't visualize two levels in a chart?  You can have arbitrary dependencies, as far as I can tell.  Two-level example: T248 depends on T249, which depends on T250.",1410485330,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-04-28 13:14:48 (UTC)`
+
+Moving here this comment from @awjrichards at {T44}
+
+* The concept of bucketing 'tasks' into an 'iteration'
+** This also includes the ability to look at past iterations (and what was contained in them)
+** As well as the ability to look at future iterations (and what will be contained in them)
+* The concept of bucketing 'iterations' into a broader 'release'",1410485330,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-04-24 14:05:29 (UTC)`
+
+There is a plan to [[ https://secure.phabricator.com/T390#21 | implement project types ]] that would include 
+
+  ( ) Tag
+    Tags are lightweight projects that don't have members or wiki pages.
+    
+  ( ) Sprint
+    Sprint projects organize work into a series of iterations. Iterations
+    are created automatically and incomplete tasks roll from one iteration to
+    the next.
+
+In the meantime, I think we could work with specific projects and queries. According to some comments in that task, this is how some orgs are doing it.",1410485330,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-04-24 09:15:47 (UTC)`
+
+Projects + queries (like ""open tickets in all these projects: '1.23.0 release' && 'MediaWiki'"").",1410485329,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-04-22 18:03:22 (UTC)`
+
+It looks like Phabricator provides enough elements for us to define this process.",1410485329,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-04-19 16:05:43 (UTC)`
+
+Why not creating project ""1.23.0 release"", and add the relevant tasks there? Release managers would even get a workboard to mark mark the status of each task from that release point of view.",1410485329,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize projects,"> Project behavior in Maniphest is similar to keywords behavior in Bugzilla
+
+Right, but then... what about keywords? Are they supposed to be enabled separately or are we using projects literally as keywords?
+
+By the way, since we may have finally a common system for keywords/tags across different tools, this might be relevant: https://www.mediawiki.org/wiki/Project:New_contributors/One_ontology
+
+**UPDATED**: 
+
+Projects are keywords, keywords are projects, components might be projects if we want... We need to come up with a default organization of projects, knowing that user will come and create the projects they miss (unless we stop them by restricting permissions), just like wiki editors create categories.
+
+**RULES FOR MIGRATING PROJECT NAMES**
+
+
+  buginfo[""product""] = buginfo[""product""].replace('-', '_')
+  buginfo[""product""] = buginfo[""product""].replace(' ', '_')
+  buginfo[""component""] = buginfo[""component""].replace('/', '_and_')
+  buginfo[""component""] = buginfo[""component""].replace('-', '_')
+  buginfo[""component""] = buginfo[""component""].replace(' ', '_')
+
+  component_separator = '-' 
+  project = ""%s%s%s"" % (buginfo[""product""],
+                       component_separator,
+                       buginfo[""component""])
+
+
+Examples:
+
+| Bugzilla product | Bugzilla component | Phabricator project |
+| MediaWiki | Change tagging | MediaWiki-Change_tagging |
+| MediaWiki‑Vagrant | labs-vagrant | MediaWiki_Vagrant-labs_vagrant |
+| Wikimedia | Git/Gerrit | Wikimedia-Git_and_Gerrit |
+| Wiki Loves Monuments | Unused images | Wiki_Loves_Monuments-Unused_images |",1397154942,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-6tvdmfknnn6daqnwcthv,task_description,resolved
+Decide how to organize projects,">>! In T43#15328, @Qgil wrote:
+> It's not a bug, it makes sense that URLs of projects follow the names of the projects, and if you edit one, the other follows.
+
+Lack of redirects after renaming a project is almost certainly a bug, as I laid out in T910.
+
+>>! In T43#15314, @Qgil wrote:
+> Please, could you revert your changes and open a new tasks to discuss specifically the substitution of dashes and underscores by spaces?
+
+I filed T911 to track this issue.",1414278905,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"True, the URLs. I have reverted your renaming of ""Bugzilla-Preview"" to make sure that this URL that we have sent to everybody in the past 48h works:
+
+https://phabricator.wikimedia.org/tag/bugzilla-preview/
+
+If you change the dash for a space, then you get
+
+https://phabricator.wikimedia.org/tag/bugzilla_preview/
+
+It's not a bug, it makes sense that URLs of projects follow the names of the projects, and if you edit one, the other follows. You can also link to the project number (https://phabricator.wikimedia.org/project/view/40/) but we opted to promote the self-explanatory URL.
+
+",1414278460,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,">>! In T43#15315, @chasemp wrote:
+> Changing this broke links currently shared to the migration effort.  I have locked this project to prevent this from happening again as people are trying to follow up on emails sent with details about the coming changes.  It would be more appropriate to start a discussion on whether another name is preferable rather than taking action that has unintended consequences.
+
+Uhh, that sounds like a Phabricator bug. I filed T910 to track this issue.",1414278151,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,">>! In T43#15276, @MZMcBride wrote:
+> I changed ""Bugzilla-Migration"" to ""Bugzilla migration"" because MediaWiki/Wikimedia development typically uses sentence case and standard word demarcation.
+> 
+> If Phabricator can't handle spaces, a very basic component of English and other languages, in project display names, then Phabricator will need to be fixed. But as a label, ""Bugzilla-Migration"" and similar awkwardly hyphenated and capitalized project names are pretty bad and should be avoided, in my opinion.
+
+Changing this broke links currently shared to the migration effort.  I have locked this project to prevent this from happening again as people are trying to follow up on emails sent with details about the coming changes.  It would be more appropriate to start a discussion on whether another name is preferable rather than taking action that has unintended consequences.",1414277785,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,">>! In T43#15276, @MZMcBride wrote:
+> I changed ""Bugzilla-Migration"" to ""Bugzilla migration"" because MediaWiki/Wikimedia development typically uses sentence case and standard word demarcation.
+> 
+> If Phabricator can't handle spaces, a very basic component of English and other languages, in project display names, then Phabricator will need to be fixed. But as a label, ""Bugzilla-Migration"" and similar awkwardly hyphenated and capitalized project names are pretty bad and should be avoided, in my opinion.
+
+Changing this broke links currently shared to the migration effort.  I have locked this project to prevent this fromhappening again as people are trying to follow up on emails with details about the coming changes.  It would be more appropriate to start a discussion on whether another name is preferable rather than taking action that has unintended consequences.",1414277751,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"@MZMcBride, we invested a fair amount of time, energy and patience in order to decide [[ https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Guidelines | the current guidelines ]]. You can challenge the guidelines with better arguments, and if the guidelines change then we can change the names of project accordingly. Please, could you revert your changes and open a new tasks to discuss specifically the substitution of dashes and underscores by spaces?",1414277598,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"I changed ""Bugzilla-Migration"" to ""Bugzilla migration"" because MediaWiki/Wikimedia development typically uses sentence case and standard word demarcation.
+
+If Phabricator can't handle spaces, a very basic component of English and other languages, in project display names, then Phabricator will need to be fixed. But as a label, ""Bugzilla-Migration"" and similar awkwardly hyphenated and capitalized project names are pretty bad and should be avoided, in my opinion.",1414275908,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"We aim at having a clear and consistent migration script logic. MediaWiki has 43 components; Wikimedia 34; MediaWiki_extensions a few more; we can rename stuff after importing, but please not in the migration script logic.
+
+Redundancy: Depends. Seeing component names such as ""Uploading"" you're supposed to have different teams working on uploading related stuff on different architecture levels (Core upload handling code, low-level media storage, Multimedia team's UploadWizard etc.).",1411653583,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"Some time ago I proposed to get rid of ""MediaWiki"" and ""Wikimedia"" since most of the times they are redundant, but I can see how that might be easier to do manually than with a magical instruction in the scrip.
+
+I find the combination of -_-_ disturbing. Possible scenarios:
+
+# Leave it as it is now and wait until our eyes get used to them.
+# Leave it as it is now and convert everything to dashes manually where makes sense.
+# Convert everything to dashes with the script, editing manually if this option is confusing in a project name.
+
+My preferred is 3, although 2 would be fine, an even 1 if I'm the only one being picky about this.  :)",1411649710,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"| Bugzilla product | Bugzilla component | Phabricator project |
+| MediaWiki | Change tagging | MediaWiki-Change_tagging |
+| MediaWiki‑Vagrant | labs-vagrant | MediaWiki_Vagrant-labs_vagrant |
+| Wikimedia | Git/Gerrit | Wikimedia-Git_and_Gerrit |
+| Wiki Loves Monuments | Unused images | Wiki_Loves_Monuments-Unused_images |",1411645395,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"Could you give some examples of the result of this pattern? I think I get it, but maybe I'm wrong.",1411587325,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"Yeah, done.
+
+Pasting the name replacement rules here, for the records:
+
+  buginfo[""product""] = buginfo[""product""].replace('-', '_')
+  buginfo[""product""] = buginfo[""product""].replace(' ', '_')
+  buginfo[""component""] = buginfo[""component""].replace('/', '_and_')
+  buginfo[""component""] = buginfo[""component""].replace('-', '_')
+  buginfo[""component""] = buginfo[""component""].replace(' ', '_')
+
+  component_separator = '-' 
+  project = ""%s%s%s"" % (buginfo[""product""],
+                       component_separator,
+                       buginfo[""component""])",1411557406,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"Naming guidelines as discussed here are have been drafted at https://www.mediawiki.org/wiki/Phabricator/Help#Requesting_a_new_project 
+
+[[ https://phabricator.wikimedia.org/project/query/o8VA7EyUUHZT/#R | Active projects ]] in this instance have been renamed accordingly.
+
+Is there anything else left in this task?",1411142613,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-09-08 15:48:20 (UTC)`
+
+at this point we can leave existing?  Mainly these restrictions are for imported content atm, I'm sure the ongoing etymology will provide plenty of conversation and change opportunities :)",1410485032,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-09-07 20:45:35 (UTC)`
+
+Is there anything else to be decided before closing this task?
+
+>>! In T68#68, @aklapper wrote:
+> Once issues created by **spaces** for URLs and referencing have been handled/fixed in upstream, we can still pretty up project names in our instance if we want.
+
+Is it worth renaming now the projects that will be migrated to follow all the same guideline?
+
+* Project
+* Great-Project
+
+I can do it in the next hours. Or we can wait and do it after the migration if you prefer.",1410485032,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-08-10 19:25:38 (UTC)`
+
+Once issues created by **spaces** for URLs and referencing have been handled/fixed in upstream, we can still pretty up project names in our instance if we want. 
+
+Currently we cannot entirely judge how often referencing is needed and used e.g. in Differential (pre-push code review tool) etc. Upstream does avoid spaces in project names, so I'd like to follow upstream here, even if things don't look pretty for use at first.",1410485031,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-08-05 20:14:10 (UTC)`
+
+Indeed! Regardless of the outcome, it is very good to see that this discussion is helping making Phabricator more robust with project names. Thank you @Rush.",1410485031,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Florian** wrote on `2014-08-05 19:03:19 (UTC)`
+
+@Rush That seems to solve one problem and looks very good :) Thanks!",1410485031,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-08-05 00:11:53 (UTC)`
+
+for fun:
+
+http://fab.wmflabs.org/tag/mediawiki/
+http://fab.wmflabs.org/tag/MEDIAWIKI/
+http://fab.wmflabs.org/tag/MeDiAwIkI/
+",1410485030,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-08-05 00:10:34 (UTC)`
+
+Case sensitivity in urls is now handled by normalizing to lower case:
+
+https://github.com/phacility/phabricator/commit/1e375c97c594e029d8e796c3fa937a7522e3b42f
+
+applied to fab for testing :)",1410485030,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-08-04 20:49:25 (UTC)`
+
+>>! In T68#60, @aklapper wrote:
+> So whenever people wanted to link to ""Project Name"" as in ""#project name"", we'd recommend to write ""#Project_Name"" and replace spaces by underscores. Question is how many users (non-heavy Phabricator users) we can make aware of it
+
+How many non-heavy Phabricator users are going to know that they can type ""#project"" in the first place? How often do you see this Markup feature in use? It sounds like a minor case even without spaces. Being project with spaces a minority, the relevance of the problem becomes smaller. And the worse that can happen is that a user can't type properly a reference of a project; not a big problem either.
+
+> plus I really don't know how much referencing is used in e.g. Differential and what other stuff we might break by using spaces in project names.
+
+Do we have specific examples? Phabricator supports spaces in project names. If this causes a problem we can file a bug upstream.",1410485029,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-08-04 20:03:35 (UTC)`
+
+thanks andre for that update :)  
+
+
+
+Pretty much my thought, get wider input on spaces if we are (in my eyes at least) overriding technical consistency for readability, and push along the case sensitivity mixup if that is a need for us.  FWIW, evan seemed to indicate the case strictness wasn’t too hard of a fix",1410485029,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-08-04 20:00:06 (UTC)`
+
+So whenever people wanted to link to ""Project Name"" as in ""#project name"", we'd recommend to write ""#Project_Name"" and replace spaces by underscores. Question is how many users (non-heavy Phabricator users) we can make aware of it, plus I really don't know how much referencing is used in e.g. Differential and what other stuff we might break by using spaces in project names.
+
+On the latter, //input from folks who have been using Phabricator extensively would help//. Chase and I don't feel entirely comfortable deciding for everybody here - it's clear that developers and engineering is the primary customer of Phab, but we'd also have HR and Legal and others here in the long run.
+
+As we'd like to not only use lower-case for project names, we want to get https://secure.phabricator.com/T5728 fixed first. Because if things don't work properly, people //will// work around them. I've asked in the upstream tickets for pointers.
+
+The general tradeoff we're discussing here is readability for humans vs. technical consistency (the value and use of referencing in Markup).",1410485029,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-07-30 21:00:36 (UTC)`
+
+Than you for the summary! Everything sounds sensible, except the bit about underscores in project names that I still (almost apologize for) disagree(ing) with.  :)
+
+>>! In T68#58, @aklapper wrote:
+> * Spaces //do not work// in the context of Remarkup in Phabricator. Hence we should avoid spaces in tag/project names. Make spaces become underscores.
+
+Phabricator converts automatically spaces in project names into underscores in their corresponding hastags in Remarkup. For what is worth, it even ignores the case style (while names with dashes/underscores seem to be case sensitive, one annoyance more to consider): 
+
+  #Wikimedia_Phabricator_Day_1, #Developer_Hub, #Human_Resources, #Trusted_User_Tool
+  #wikimedia_phabricator_day_1, #developer_hub, #human_resources, #trusted_user_tool
+  #WikImediA_pHabRicator_DaY_1, #deVELoper_HUB, #HUMAN_resources, #trustEd_User_tOoL
+renders as
+ #Wikimedia_Phabricator_Day_1, #Developer_Hub, #Human_Resources, #Trusted_User_Tool
+ #wikimedia_phabricator_day_1, #developer_hub, #human_resources, #trusted_user_tool
+ #WikImediA_pHabRicator_DaY_1, #deVELoper_HUB, #HUMAN_resources, #trustEd_User_tOoL 
+
+Therefore, substituting spaces with underscores in project names doesn't add anything apart from the inconvenient case sensitivity and the lack of tokenization.
+
+Also note that the labels above look visually good and feel human, natural. Put the underscores between words, and it will look like computer generated text with a slightly broken UI (like a string without localization). Project names are visible everywhere in Phabricator. If they look nice, our Phabricator will look nicer.
+
+> (Underscores however are not tokenized (yet), same problem for dashes in https://secure.phabricator.com/T5727.) I don't see this as a big issue for type-ahead in the Project field. If some consider it, it is fixable.
+
+Tokenization works fine with spaces in projects names.",1410485028,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-07-30 18:11:30 (UTC)`
+
+We have two aspects and we've mixed them up so far. My fault.
+1) Migrating data from Bugzilla to Phabricator, in a consistent way, via a script. That's T423.
+2) Fixing some of Bugzilla's product and component taxonomy. For example, ""MediaWiki extensions"" should have never been a product in Bugzilla as it's not ""one codebase/shared ownership"". Instead, its components should have been products in Bugzilla. A few years too late.
+
+In today's Phab meeting there was pretty much agreement on:
+* Fix Bugzilla's broken taxonomy //after// migrating, instead of trying to cover and fix lots of cornercases in the migration script itself. (Not sure if we can (mass-)rename via API. If not, I'll spend a long night on coffee.)
+* Convert forward slashes like in ""General/Unknown"" to underscores or just drop the part after the slash, because slashes would break project URLs. There are 15 components affected in Bugzilla.
+* Spaces //do not work// in the context of Remarkup in Phabricator. Hence we should avoid spaces in tag/project names. Make spaces become underscores. (Underscores however are not tokenized (yet), same problem for dashes in https://secure.phabricator.com/T5727.) I don't see this as a big issue for type-ahead in the Project field. If some consider it, it is fixable.
+* The ""Product Component"" pair in Bugzilla should become ""Product:Component"", with a colon as separator. (And I just renamed two components in Bugzilla to not include colons.)
+* As Bugzilla's keywords and ""Product Component"" pairs will be in the same namespace in Phabricator, a Bugzilla keyword becomes a tag, ""Product Component"" becomes a project. These would be two different types and Mukunda said this should not be too hard to fix if I got it right at the end.",1410485028,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**jdforrester** wrote on `2014-07-28 23:59:55 (UTC)`
+
+@qgil's suggestions all make sense to me.
+
+Spaces in project names is a fact of life, but we should discourage it unless it's needed; in general, the first space being a subproject is a neat enough design idea.
+
+My only concern is where we have clashes in name (//e.g.// we used to have Vector the skin and Vector the extension), but I think we can manage our way around those as needed.",1410485028,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-07-28 21:53:35 (UTC)`
+
+I summarized my opinion about this topic at T457#19. In short:
+
+> * Using original project names in Phabricator makes them easier to type and find.
+> * Project names are used as simple tags, except in the case of explicit subprojects of an existing project à la ""Product - Component"". No ""MediaWiki-Extensions-Etc"".
+> * Since projects are proper nouns, by default they use the regular Title Case. Other uses of case are allowed only when the original project name uses them (e.g. GoogleLogin, VisualEditor, MySQL, FOSDEM)
+
+If the VisualEditor team wants to have a ""VisualEditor Data Model"" project, that's fine, but I don't see the usefulness of adding ""MediaWiki Extension"" to the project name. Especially when with the same principle we will add the same string to hundreds of extension projects, ruining type-ahead for any users typing ""MediaWiki"" and/or ""extension""
+
+As the description of this task says, in Phabricator projects are keywords, keywords are projects. Search and type-ahead are essential in Phabricator (and in MediaWiki itself, btw). The tree structure that Bugzilla and Git/Gerrit enforce doesn't need to be replicated here. What's the use? Project naming should focus on proper tagging instead of trying to emulate a tree structure.",1410485027,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-07-28 20:47:30 (UTC)`
+
+@aklapper @qgil
+
+I took this to mean that we qgil does not want either categorization or hierarchy in the googlelogin case
+
+> What is important about ""GoogleLogin"" is that users can find it or reference it easily. Therefore the best is to use the name as is.
+
+@qgil can you maybe clarify so we aren't shadow boxing here?",1410485027,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-07-28 19:35:14 (UTC)`
+
+Would love to get feedback from more parties on this:
+
+There have been discussions on project naming schemes with good and valid arguments by all involved parties in T457 but those discussions seems to fit better here to keep T457 focused on //documenting//.
+
+The three main aspects I see mentioned which are intermingled:
+* allowing spaces in project names,
+* expressing hierarchy in project names,
+* ""discoverability"" of existing projects when using type-ahead to make Phabricator list project proposals for matching strings in the ""Projects"" field.
+
+For the fourth and minor aspect of //enforcing lower case names// for projects: Currently, not using a lower case project name would break URL redirecting from e.g. http://fab.wmflabs.org/tag/trusted_user_tool/ to http://fab.wmflabs.org/project/view/40/ . Treating lower and upper case the same way //should be fixed upstream// in https://secure.phabricator.com/T5728 and IMHO we as downstream should not really bother about this.
+
+In order to understand ""discoverability"", here is the current behavior of type-ahead in Phabricator's ""Projects"" field: Type-ahead is not restricted to the very beginning of a project name but to words (tokens). We have a project named ""Wikimedia Phabricator Maintenance (after Day 1)"" in fab.wmflabs.org. If you go to http://fab.wmflabs.org/maniphest/task/create/ and enter ""after"" or ""Day"" in the ""Projects"" field, it will be proposed. It does not match random substrings though - entering ""fter"" does not propose ""after"".
+
+=== Hierarchy or Categories ===
+
+It seems we all agree that we do need some level of organization and rules in that flat Projects namespace, otherwise things will get messy, ambigious, colliding in the long run.
+
+Question is whether we want to express //hierarchy// like ""MediaWiki extension: VisualEditor: Data Model"" or ""MediawikiExtension-VisualEditor-DataModel"" or instead //categorization// like ""VisualEditor: Data Model (extension)"".
+
+The latter feels more readable for the human eye but not sure if that's reason enough.
+
+=== Spaces in Project Names ===
+
+If we did //not// allow spaces in project names, like in ""mediawikiextensions-visualeditor-datamodel"", entering ""datamodel"" in the ""Projects"" field would currently not propose the given project via type-ahead. I consider this problematic as reporters should be able to try entering and finding the correct project, and the first thing they'd try is the actual name, if aware of. On a related note, Chase proposed treating hyphens/dashes the same way as spaces for type-ahead proposals in upstream https://secure.phabricator.com/T5727 (and Evan was in favor on IRC).
+
+If we did allow using spaces in project names, referencing a ""#project name"" in text via the # suffix will not work for these projects, as Chase brought up in http://fab.wmflabs.org/T457#17 , plus entering a URL replacing spaces by %20 HTML entities (instead of underscores) like in http://fab.wmflabs.org/tag/Trusted%20User%20Tool/ will not work.",1410485027,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-07-23 14:54:41 (UTC)`
+
+A note aside: there is an RfC about Bugzilla taxonomy: https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy
+
+We should check which concerns still are relevant in the context of Phabricator, even if here we don't have trees, product-component pairs, and restrictions to file reports only under one product-component.",1410485026,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-07-02 16:20:51 (UTC)`
+
+Refering to differentiating between types of projects (e.g. keywords and components in Bugzilla language), it looks like upstream is going towards project tags. That means that https://secure.phabricator.com/T390 (Implement Project Types) might not gonna happen, but https://secure.phabricator.com/D9709 and https://secure.phabricator.com/T2628 (Add project tags to Pholio, Ponder, Differential, and other applications) instead.
+
+As one example, upstream Phabricator shows a different (kind of transparent) background on umbrella projects now, see e.g. https://secure.phabricator.com/T1205",1410485026,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Nemo_bis** wrote on `2014-06-15 10:36:47 (UTC)`
+
+> (Phab doesn't list project names first which start with the entered substring).
+
+Doesn't?",1410485025,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-06-12 18:11:33 (UTC)`
+
+>>! In T68#42, @qgil wrote:
+> Let's avoid repetitive mentions to ""Wikimedia"" and ""MediaWiki"". Think again about the side effects this creates in type-ahead when a user starts typing ""Wiki..."" when actually the request is the very licit WikiLove.
+
+Good point, as type-ahead proposals for the Project field always have the alphabetical order of project names it would clutter a lot (Phab doesn't list project names first which //start// with the entered substring).
+""skin"" and ""extension"" implicitly refer to MediaWiki nowadays; crossing fingers it'll stay like this.",1410485025,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-06-11 22:17:57 (UTC)`
+
+I wouldn't patch anything before receiving consistent feedback from real users. I still believe type-ahead will just work as a method, and we might just fix nmes of projects based on what people is not finding easily.
+
+Let's avoid repetitive mentions to ""Wikimedia"" and ""MediaWiki"". Think again about the side effects this creates in type-ahead when a user starts typing ""Wiki..."" when actually the request is the very licit WikiLove.
+
+I would keep keywords as projects. It is easier to get rid of those projects we won't user than to fix missing keywords after the migration.",1410485025,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**jdforrester** wrote on `2014-06-11 18:23:28 (UTC)`
+
+>>! In T68#40, @aklapper wrote:
+> * Please help: What are further potential categories (skins, extensions, tool labs, mobile apps) you can imagine?
+
+I think the main one will be cross-cutting pieces of work, which currently are represented as you say as either:
+* a tracking bug, often in a in poor location
+** //e.g.// ""All repositories should pass jshint test (tracking)"" https://bugzilla.wikimedia.org/show_bug.cgi?id=60619 which is in the component for Wikimedia's CI infrastructure rather than being a cross-tracked ""code quality"" compontent
+* a keyword, often poorly understood, abused or ignored
+** //e.g.// ""shell"" https://bugzilla.wikimedia.org/buglist.cgi?keywords=shell&list_id=321010&resolution=--- which really just means ""deployment rights needed"" and so duplicates the ""Site requests"" component a chunk.
+
+I would suggest that:
+
+* All tracking bugs should be merged into existing projects / components or tasks within a larger cross-cutting project
+* All keywords should become projects (with overlap with the above), or just be killed.
+
+Examples:
+
+* //Code quality// is clearly something we'd want as a cross-cutting project (taking on the tracking bugs around CI/etc.); some keywords (//e.g.// hiphop) would want to be a task underneath this project.
+* //Language support// would replace the i18n and utf8 keywords
+
+> * Keywords like ""community-consensus-needed"" - will that become a column in the //Wikimedia Site Requests// project?
+
+Sounds good to me.",1410485024,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-06-11 16:49:54 (UTC)`
+
+General thoughts:
+We have no hierarchy. Project description text (providing further info/context) is //only// visible on project homepages but not when filing a task.
+We may want to ""patch in"" a link to the list of projects at http://fab.wmflabs.org/project/query/all/ or http://fab.wmflabs.org/project/query/active/ (also see T52) but that's bonus. We may want to patch in an explicit ""Leave Project field empty if you don't know"" on /maniphest/task/create/.
+
+In any case: We need to guess what people would enter into the //Project// field to describe the area they have in mind when creating a new task. Think in search terms attitude. We do have full type-ahead searching for project names available. So we can express alternative names, context, categories in brackets as part of the project name.
+
+James' proposal above is a great start (thanks!). Extending/iterating on this:
+
+* For Wikimedia and MediaWiki products in Bugzilla: By default, try to merge product and component (Bugzilla's ""Wikimedia→Foo"" becomes ""Wikimedia Foo"". ""MediaWiki→Bar"" becomes ""MediaWiki Bar""), or even drop the ""Wikimedia"" product if distinct enough (""Continuous integration"": I hope we'll never get a MediaWiki extension offering that functionality. Yeah, unlikely, but you get the thinking).
+* Categorize specific skins as such: ""Vector (MediaWiki skin)"" / ""Chameleon (MediaWiki skin)""; Skins Bugzilla product got requested in https://bugzilla.wikimedia.org/show_bug.cgi?id=66441
+* Categorize extensions as such, mention alternative names: ""AbuseFilter (MediaWiki extension)""; ""Echo (Notifications; MediaWiki extension)""; ""Popups (Hovercards; MediaWiki extension)""
+* Categorize tools on Tool Labs as such: ""lists (tool on Tool Labs)""
+* Maybe categorize mobile applications as such?
+* (We can always rename projects after Day 1 but would be cool to keep that to a minimum.)
+* Please help: What are further potential categories (skins, extensions, tool labs, mobile apps) you can imagine?
+
+Going deeper / Followup issues at some point: 
+* Browse for / decide on specific conflicts (examples: //i18n// keyword vs //MediaWiki→Internationalization// component; //analytics// keyword vs //Analytics// product; //parser// keyword vs //MediaWiki→Parser// component):
+ * Components: https://bugzilla.wikimedia.org/describecomponents.cgi
+ * Keywords: https://bugzilla.wikimedia.org/describekeywords.cgi
+ * Tracking tickets: https://bugzilla.wikimedia.org/showdependencytree.cgi?id=2007&maxdepth=1&hide_resolved=1
+* Historically (organic growing), we do have quite some duplication between Keywords and Tracking tickets, e.g. //tracking// keyword ∪ //blocking bug 2007//. We should treat tracking tickets as if they were keywords if the blocked ticket itself is not actionable && is not technically blocked on a depending task. (I'll add this in a future comment in T39.)
+* Decide to merge some components (e.g. //WM→Extension setup// ∪ //WM→Site requests//?)
+* Keywords like ""community-consensus-needed"" - will that become a column in the //Wikimedia Site Requests// project?
+* Kill some rather uncommon keywords after wondering whether anybody ever really queries for tickets with those keywords set (e.g. //mobile-lang//, //utf8//?)",1410485024,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**jdforrester** wrote on `2014-05-11 09:31:45 (UTC)`
+
+> Sounds good to me. Ultimately, whoever works on the migration script will request the discrete mapping from Bugzilla products-components to Phabricator projects, with the exact names (or name schema) for each combination. Maybe this is a task on its own?
+
+Yeah, that makes sense; or maybe a ""present the final mapping of fields/values/etc. for comment before running the import""?",1410485024,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-05-11 09:20:26 (UTC)`
+
+Sounds good to me. Ultimately, whoever works on the migration script will request the discrete mapping from Bugzilla products-components to Phabricator projects, with the exact names (or name schema) for each combination. Maybe this is a task on its own?",1410485023,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**jdforrester** wrote on `2014-05-11 08:01:31 (UTC)`
+
+> I don't think we should make project hierarchy a blocker of Day 1, though.
+
+Agreed.
+
+I'd suggest instead some careful implicit hierarchy in naming of like things, and where there are duplicates clear them up with a disambiguating term, but otherwise leave things to be named naturally.
+
+For example:
+* ""MediaWiki"" for MediaWiki core
+* ""Vector"" for the MediaWiki skin (not ""MediaWiki"" > ""Skin and page rendering"" (!))
+* ""Vector (extension)"" for the MediaWiki extension (not ""MediaWiki extensions"" > ""Vector"")
+* ""Continuous integration"" for continuous integration issues (not ""Wikimedia"" > ""Continuous integration"")
+* ""Wikimedia site configuration"" for configuration of Wikimedia's hosted sites (not ""Wikimedia"" > ""Site configuration"")
+* ""VisualEditor"" for VisualEditor core
+* ""VisualEditor MediaWiki integration"" for VisualEditor's MediaWiki integration (not ""VisualEditor"" > ""MediaWiki"")
+
+Thoughts?
+",1410485023,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-05-10 23:40:05 (UTC)`
+
+> I'd strongly recommend having project hierarchies implemented before giving in to the flatness.
+
+Status of project hierarchies feature upstream:
+
+* ~~[[ https://secure.phabricator.com/T333 | Allow projects to have subprojects ]]~~ (Closed, Wontfix)
+* [[ https://secure.phabricator.com/T390 | Implement Project Types ]] (Open since August 2011, Normal)
+
+Looks good and they will eventually implement different types of project hierarchy. I don't think we should make project hierarchy a blocker of Day 1, though.",1410485023,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**parent5446** wrote on `2014-05-10 14:46:10 (UTC)`
+
+As much as naming rules will ""work"" for this, I'd strongly recommend having project hierarchies implemented before giving in to the flatness.",1410485022,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-05-10 09:17:11 (UTC)`
+
+Since Day 1 is defined by the Bugzilla migration, I think we should focus on the projects that would be automatically generated out of that migration. Once we see the situation after 65k tasks have been migrated, we can decide whether this is good enough for Day 1, or we want to fine tune projects before opening the gates for everybody.
+
+A simple proposal for this first iteration:
+
+* Every ""[[ https://bugzilla.wikimedia.org/describecomponents.cgi | Product - Component ]]"" combination is a project.
+* Every [[ https://bugzilla.wikimedia.org/describekeywords.cgi | keyword ]] is a project.
+
+Project names can be edited without causing any disruption, therefore the members of the ""MediaWiki extensions - TorBlock"" project can just rename it to ""TorBlock"".
+
+Good enough for a first decision?",1410485022,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-05-10 09:05:14 (UTC)`
+
+I created [[ http://fab.wmflabs.org/herald/rule/3/ | a Herald rule ]] to add an identified parent project automatically every time a child project is added. Testing this here for the first time right now.
+
+PS: it works.  :)",1410485021,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-05-03 16:56:06 (UTC)`
+
+Another aspect to think about which I run into this afternoon when giving porting my Bugzilla Greasemonkey triagescripts to Phabricator a shot: //Deployed/planned-to-get-deployed vs. 3rd party extensions//, as a random WMF triager has more interest in making sure that bug reports on extensions which are more relevant to WMF (=deployed on WMF servers) get handled sufficiently. Differentiation isn't currently done in Bugzilla either. I do differentiate though in my (client-side) Greasemonkey script for Bugzilla, by dully comparing component name strings against a hardcoded list (not cool, I know).
+
+As a task can have more than on project in Phabricator, something less cumbersome could be having a general ""MediaWiki extension"" product and an additional ""Deployed on WMF servers"" project, but only //if// this could be automatically set via a ""if task in Project A, also automatically add Project B"" rule, and if this differentiation isn't considered visual overkill making the ""Projects"" field too noisy. Don't know yet either.",1410485021,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-04-18 17:26:18 (UTC)`
+
+I don't think it is messy at all. It is just different of the (inflexible and problematic) hierarchy of products and components in Bugzilla.
+
+We have well defined items out there: products usually tied to code repositories (VisualEditor, Flow, PyWikiBot...), Wikimedia projects (en.wiki, Commons...), Bugzilla keywords (i18n, design, shell...), and we have the current Bugzilla taxonomy, of course.
+
+We could start with this, and see what happens. Tasks filed without a project specified might show lazy users... and might show also gaps in our current taxonomy. And, as said, users will create also projects, which is another way to provide feedback.
+
+If we agree on the basic idea, we can start thinking on the specific case of the Bugzilla migration.",1410485021,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-04-18 17:10:08 (UTC)`
+
+◀ Merged tasks: T54.",1410485020,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-04-18 08:39:30 (UTC)`
+
+Git repositories, useful Bugzilla keywords (assuming we use keywords instead of dependencies to express the relation of a task to a certain area), and Bugzilla components when one repository is big/complex enough that it needs subareas for developers to find stuff that they work on. Sounds a bit messy, I know...",1410485020,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-04-17 21:45:05 (UTC)`
+
+In practice this means that we would create the initial list of projects based on... Bugzilla components? Git repositories? ",1410485020,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-04-17 19:01:35 (UTC)`
+
+Also relevant: T54#9",1410485019,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-04-10 21:15:27 (UTC)`
+
+AFAIK there's no separate keyword concept in Phabricator, so if we don't want code changes, keywords would become projects (as tasks can have more than one project). In a kind of way that's even more consistent, as current Bugzilla keywords like ""accessibility"", ""i18n"" or ""easy"" could be considered projects across projects too, and Phabricator's Advanced Query allows AND and OR queries for the Projects field. 
+
+I expect a few people to complain about missing free-form tagging (in Bugzilla: globally visible ""Status Whiteboard"" and private ""Tags"" field) though. Translating this functionality to Phabricator terminology, I'd probably call it ""private projects"" if a user could define her/his own projects only visible to her/him in the project field, e.g. via a prefix being the username in Phabricator so they'd be easy to find via the autocomplete (type ""aklapper"", find ""aklapper-moreinfo"" and others and have these items only be available and visible to the user ""aklapper"" in the projects field).
+Damn, I didn't plan to propose an implementation, but I guess I just did.",1410485019,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"Which features would Trello users really miss? If you are not sure whether feature X is supported, under development, roadmapped... just ask. Let's create new subtasks for features considered blockers.",1396569879,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gm3iscenilyd5pim7stg,task_description,resolved
+Identify features Trello users would miss in Phabricator,"@spage 
+
+I think porting trello checklists into this type of checklist is acceptable for a migration, but it is definitely something that people will miss ( actual interactive checklists) ",1417739912,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,">>! In T21#305, @connorshea wrote on `2014-04-22 01:43:08 (UTC)`
+> 
+> As far as I can tell, there's no checklist functionality in Phabricator. There are numbered lists, but that isn't particularly convenient in comparison to the checklist functionality of Trello.
+
+If you make the items subtasks, then Phabricator tracks them in **Blocked by**.
+
+If you want an internal checklist, [[ https://secure.phabricator.com/book/phabricator/article/remarkup/ | Phabricator's ""Remarkup""]] turns `[]` and `[x]` at the start of a line into a checklist:
+[x] buy eggs
+[] scramble eggs
+
+The task's ""card"" in the Phabricator workboard doesn't show an indicator there's a checklist or a ""2/6"" completion count next to it, and the single task view doesn't show a ""33%"" progress bar under the checklist. The latter I think is simply client-side JavaScript. I don't find any of these indicators particularly useful, but T1141 covers them.",1417741277,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,">>! In T21#305, @connorshea wrote on `2014-04-22 01:43:08 (UTC)`
+> 
+> As far as I can tell, there's no checklist functionality in Phabricator. There are numbered lists, but that isn't particularly convenient in comparison to the checklist functionality of Trello.
+
+If you make the items subtasks, then Phabricator tracks them in **Blocked by**.
+
+If you want an internal checklist, [[ https://secure.phabricator.com/book/phabricator/article/remarkup/ | Phabricator's ""Remarkup""]] turns `[]` and `[x]` at the start of a line into a checklist:
+[x] buy eggs
+[] scramble eggs
+
+The task's ""card"" in the Phabricator workboard doesn't show an indicator there's a checklist or a ""2/6"" completion count next to it, and the single task view doesn't show a ""33%"" progress bar under the checklist. The latter I think is simply client-side JavaScript. I don't find any of these indicators particularly useful.",1417739764,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,//importing issue status//,1410484891,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**qgil** wrote on `2014-04-30 23:49:39 (UTC)`
+
+The current list of subtasks seems to be accurate. No blockers have been identified. Some missing features would make our life easier and nicer, but the integration with bug reporting and code review would pay off.
+
+If there are relevant Trello features not listed here, please add them as subtasks.
+
+Resolving this task. Your attention is welcome especially in the subtasks above, {T238}, and {T61}.",1410484890,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**qgil** wrote on `2014-04-28 06:15:27 (UTC)`
+
+After reading all the current a previous feedback related to the RfQ, including [[ https://blog.wikimedia.org/2014/04/15/agile-and-trello-the-planning-cycle/ | Tomasz's recent blog post ]], I cannot find any blocker due to Trello features missing in Phabricator. Trello does perform better in its territory, but I couldn't find anything that would outweigh the benefits of moving to one single open source tool hosted in Wikimedia servers and integrated with bug reporting and software development. The missing features reported could be contributed locally and/or upstream, if we would really need them.
+
+Do you agree with this? If you see any Trello related blocker, please highlight it.",1410484890,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**mattflaschen** wrote on `2014-04-24 21:18:33 (UTC)`
+
+> Is this provided by the mobile app or the web? In Phabricator you can check your notifications in mobile, but you have to click the ""flame"" button (or your mailbox) to find out. Which minimum improvement would you welcome in this direction?
+
+""Push notifications"" means there is no need to check.  I don't use Trello notifications (though I know other people do).  However, the general idea of push notifications is that the notification is sent directly to your phone, and it typically buzzes or beeps, similar to if you received a text (of course, this depends on your phone configuration).  Then, you check a notification list on your phone.  So there is no need to keep opening the app or mobile web site until you get notified.
+
+> The ability to develop a product roadmap (as opposed to just a task list/project management tool) using a board.
+
+This might be doable by just having a separate workboard for the roadmap.
+
+> Easy customization. The labels/task columns/themes/ etc. are so easy to change at a whim.
+
+Phabricator does let you change the task columns freely (and per-workboard), albeit a different UI from Trello.
+",1410484890,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**qgil** wrote on `2014-04-24 21:06:49 (UTC)`
+
+Important question for Trello users:
+
+**If you could get one thing  implemented in Phabricator tomorrow, only one thing, which one would that be?**
+
+As commented in {T44}, there is currently a mess of Mingle/Trello features being requested without a clear ranking of priorities. Let's focus on Trello first. And let's focus on what matters most. 
+
+Feel free creating cards for any of the tasks below, or just comment here with more details, and I will do it.
+
+> Real-time collaborative updating (it's an amazing way to task an issue without copying the breakdown work back and forth between tools)
+
+What does this mean in terms of features missing in Phabricator?
+
+> Great mobile support. Trello gives me push notifications for a board/card I am following. 
+
+Is this provided by the mobile app or the web? In Phabricator you can check your notifications in mobile, but you have to click the ""flame"" button (or your mailbox) to find out. Which minimum improvement would you welcome in this direction?
+
+> The ability to develop a product roadmap (as opposed to just a task list/project management tool) using a board.
+
+Could you link to an example, please?
+
+> Easy customization. The labels/task columns/themes/ etc. are so easy to change at a whim.
+
+What specifically do you miss most in Phabricator? When you say the ""theme"", do you mean the design of the cards or the UI in general?
+
+> Team independence and control over task management styles.
+
+How specifically do you see your workflow is conditioned by general policies or settings in Phabricator? Interesting and possibly related link upstream: [[ https://secure.phabricator.com/T390 | Implement project types ]].
+
+> Markdown
+
+Well, ok, although the toolbar makes the syntax irrelevant in basic usage. Is there any difference that really annoys you? See {T165}.
+
+> A pretty interface
+
+Understood, but the starting point is very decent, especially considering that the same team members that enjoy the beauty of Trello have to spend several hours in Bugzilla and Gerrit. Therefore, the total percentage of UI beauty vs ugliness would ultimately increase.  ;)  Please create tasks for the specific features you think we should push upstream.",1410484889,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**kevinator** wrote on `2014-04-22 15:31:49 (UTC)`
+
+I logged a bug (er task) because I believe task titles should not get truncated in the Workboard View.  Trello wraps titles and makes its cards taller to accommodate for long titles.  
+http://fab.wmflabs.org/T195
+",1410484889,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**connorshea** wrote on `2014-04-22 01:43:08 (UTC)`
+
+As far as I can tell, there's no checklist functionality in Phabricator. There are numbered lists, but that isn't particularly convenient in comparison to the checklist functionality of Trello.",1410484889,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**swalling** wrote on `2014-04-11 00:42:53 (UTC)`
+
+Here's a list off the top of my head:
+
+- Great **mobile** support. Trello gives me push notifications for a board/card I am following. The mobile website + email for Phabricator is a workable but not perfect replacement. 
+- The **ability to develop a product roadmap** (as opposed to just a task list/project management tool) using a board. Ultimately this is a ""nice to have"" feature and we can easily switch to using another tool like MediaWiki. 
+- **Easy customization**. The labels/task columns/themes/ etc. are so easy to change at a whim. It really support ongoing refinement of a team's project management toolkit, in an agile fashion. 
+- **Team independence and control** over task management styles. Each team also has a high degree of independence, since settings can be different across boards. Once we all move to Phabricator there is more interdependence between project management styles across teams. 
+- **Markdown** Phrabricator has some weird mix of Markdown and MediaWiki-like syntax which we will all have to learn. Trello just formats with Markdown. 
+- **A pretty interface** Trello has a nice clean friendly UI. Enhancements like turning image attachments in to covers for tasks, setting stickers, emoji, and more are all features that make a task management system more fun and easy. We //really need// to continue to support memes and other fun interface elements of Phabricator to achieve parity here. Turning on serious business mode is not fun!
+
+To expand, here's a list of **things I //won't// miss** about Trello:
+
+- No dependencies. You can only manually list dependencies in Trello.
+- Not easy for community members to use. You have to login to a third party site to use it, and it clearly is not a Wikimedia-run tool, which scares community/volunteer participants away. 
+- Paying for Business Class license. This costs a (small) fee for the WMF. ",1410484888,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**swalling** wrote on `2014-04-11 00:12:19 (UTC)`
+
+@kevinator have you seen the board view of Phabricator task lists? We have customizable boards like that now, such as [[ http://fab.wmflabs.org/project/board/1/ | VisualEditor test board ]]. You can find it via ""Workboards"" on any project. ",1410484888,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**kevinator** wrote on `2014-04-11 00:02:31 (UTC)`
+
+found this on quora:
+http://www.quora.com/Phabricator/If-you-had-to-choose-between-Phabricator-or-Pivotal-Tracker-what-would-you-choose-and-why
+
+Here's what I love about trello:
+
+Where cards appear on the screen has meaning (column denotes stage, top is importance).
+It's easy to move things around.",1410484888,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**milimetric** wrote on `2014-04-09 00:01:51 (UTC)`
+
+  - Real-time collaborative updating (it's an amazing way to task an issue without copying the breakdown work back and forth between tools)
+
+",1410484887,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Paste the following table (or any table from a non-Mediawiki source) into VE. While in edit mode, it will look fairly normal, with borders and a grey background for header cells (due to VE's own style rules). But after the page is saved, it will appear in read mode without any borders or background.
+
+| Animal | Ferocity | Cuddliness
+| ------- | ---------- | -------------
+| Bunny | 0 | 9
+| Cat | 4 | 10
+| Tiger | 10 | ? 
+ 
+{F25893} 
+
+This is because pasted tables do not get `class=""wikitable""` which provides the normal table styling.
+",1419983289,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-eo27t627sh27uj66uxst,task_description,resolved
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Change 265812 merged by jenkins-bot:
+Follow-up I9714cf3: Add tests for wikitable paste
+
+[[https://gerrit.wikimedia.org/r/265812]]",1453494073,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Change 265812 had a related patch set uploaded (by Esanders):
+Follow-up I9714cf3: Add tests for wikitable paste
+
+[[https://gerrit.wikimedia.org/r/265812]]
+",1453493669,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Change 265785 merged by jenkins-bot:
+MWTableNode: Apply wikitable class to pasted tables
+
+[[https://gerrit.wikimedia.org/r/265785]]",1453489842,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Change 265785 had a related patch set uploaded (by Esanders):
+MWTableNode: Apply wikitable class to pasted tables
+
+[[https://gerrit.wikimedia.org/r/265785]]
+",1453488324,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","I just got bit by this while helping some folks copy over existing information from a Word document. 
+
+Perhaps a solution would be to allow tables to have a modal like Media and Templates where one could click to bring up a window to make configuration changes to the table? One option could be to apply styles - directly by class name or perhaps language indicating ""with borders"" or some such. Less ambiguity in the language is better for editors unfamiliar with language such as ""class=wikitable"" but also understandably more difficult to implement consistently.
+
+Or, conversely (and I can't believe I'm taking inspiration from Microsoft Word) upon paste there is a modal to ask editors 'match default style' or ""keep existing style""?
+
+Tables created in VE-MW do get class=""wikitable"" applied by default, correct?
+
+",1449855907,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",Question: Are we //stripping// any table classes these days?,1453286581,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",Question: Are we stripping any table classes?,1447410555,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","So it sounds like `.wikitable` is, in fact, just one style out of many. So I think task will remain limited to what it says in the title: automatically give pasted tables `class=""wikitable""` in VisualEditor-Mediawiki.",1436215566,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">>! In T85577#1379805, @Neil_P._Quinn_WMF wrote:
+> In fact, I'd go further and ask why Vector doesn't style all tables like this by default? In the rare cases when people actually want the default style, //that// could be applied using a class. 
+
+fwiw... The use of `.wikitable` is relegated almost exclusively to discussions and help pages on Wikisource at best -- where the last thing we want is a table that renders //nothing// like the ones found in works we're transcribing.
+
+Go ahead and make it the default for VE but please provide a way to override/usurp that or it will just wind up as another never-used dialog in our case.",1435211161,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">>! In T85577#1398663, @Izno wrote:
+>>>! In T85577#1379898, @Jdforrester-WMF wrote:
+>> It's important to note that we only want this to be the case in VE-MW, not VE-core. :-)
+> 
+> Last I checked .wikitable ships in core. Am I crazy, or is there some other reason why not?
+
+You're not crazy, it's just that the naming is confusing :). ""VE-core"" (VisualEditor core) is a rich text editor independent of MediaWiki. ""VE-MW"" (VisualEditor MediaWiki) is what everyone knows as **the** VisualEditor, the extension to MediaWiki. We want this behavior in VE-MW, but not VE core.
+
+
+>>>! In T85577#1380307, @Neil_P._Quinn_WMF wrote:
+>>>In fact, I'd go further and ask why Vector doesn't style all tables like this by default? 
+>> 
+>> To answer my own question, it's probably that this would break tables used as a poor man's layout tool by Mediawiki editors
+> 
+> These very rarely, if ever, occur in mainspace on en.wp. Probably rare on the other wikis. Why doesn't someone do the research of getting a dump of mainspace of x or y or z MW wikis and look for tables without the class assigned?
+
+We wish :) https://en.wikipedia.org/wiki/San_Francisco has 39 `table` elements without the `wikitable` class. This includes the infobox, some nested infobox bits which have their own tables, all the navboxes, all the maintenance templates, assorted templates which generate infobox-like or thumbnail-like structures, and some other bits and pieces.",1435195599,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">>! In T85577#1379898, @Jdforrester-WMF wrote:
+> It's important to note that we only want this to be the case in VE-MW, not VE-core. :-)
+
+Last I checked .wikitable ships in core. Am I crazy, or is there some other reason why not?
+
+>>! In T85577#1380307, @Neil_P._Quinn_WMF wrote:
+>>In fact, I'd go further and ask why Vector doesn't style all tables like this by default? 
+> 
+> To answer my own question, it's probably that this would break tables used as a poor man's layout tool by Mediawiki editors
+
+These very rarely, if ever, occur in mainspace on en.wp. Probably rare on the other wikis. Why doesn't someone do the research of getting a dump of mainspace of x or y or z MW wikis and look for tables without the class assigned?",1435193161,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",I've asked at https://en.wikipedia.org/wiki/Help_talk:Table#Where_is_class.3Dwikitable_not_used.3F,1434674736,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">In fact, I'd go further and ask why Vector doesn't style all tables like this by default? 
+
+To answer my own question, it's probably that this would break tables used as a poor man's layout tool by Mediawiki editors",1434662558,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","It's important to note that we only want this to be the case in VE-MW, not VE-core. :-)",1434657142,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","I agree with @Quiddity. From the user's perspective, `wikitable` styling //is// how Mediawiki tables look. We should definitely apply `class=""wikitable""` automatically. 
+
+In fact, I'd go further and ask why Vector doesn't style all tables like this by default? In the rare cases when people actually want the default style, //that// could be applied using a class. ",1434655792,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">>! In T85577#1105146, @Catrope wrote:
+> This is ""correct"" behavior: tables in MW read mode do not have borders unless `class=""wikitable""` is explicitly set. Perhaps pasted tables should automatically get `class=""wikitable""`, like newly created tables do?
+
+I believe that would be good. All tables I've ever seen in articles use this (or more complex) styling, and it's used almost everywhere in https://www.mediawiki.org/wiki/Help:Tables",1434587068,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","This is ""correct"" behavior: tables in MW read mode do not have borders unless `class=""wikitable""` is explicitly set. Perhaps pasted tables should automatically get `class=""wikitable""`, like newly created tables do?",1426005863,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,"Seen as both anon and while logged in: 
+
+Edit any page at http://en.wikipedia.beta.wmflabs.org
+
+Use insert menu to insert almost anything: I had the same experience with Formula, Table, and Media. 
+
+Save the page after inserting the element. 
+
+After save, click the wikitext edit link, whether logged in or anonymous.  Nothing happens. 
+
+I see no javascript errors when clicking the wikitext edit, but I do see a warning on saving the page in VE, but I'm not sure it's relevant: 
+
+ load.php:61
+""Invalid _currentGuiderID.  Returning early"" load.php:153
+console.trace(): load.php:154
+mw.log</log.warn() load.php:154
+transition/<()",1419973179,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-2fasjdalcvfhpa6dgghm,task_description,resolved
+Edit source link broken after editing the page with VisualEditor,Checked in betalbs - Edit source works after VE Save.,1420491349,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,"Change 181679 merged by jenkins-bot:
+Don't break ""Edit source"" link after VE has closed
+
+[[https://gerrit.wikimedia.org/r/181679]]",1420464524,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,"I just saw the patch, thanks!",1419973731,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,Sounds like this is something I already spotted and uploaded a patch for.,1419973665,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,"Change 181679 had a related patch set uploaded (by Alex Monk):
+Don't break ""Edit source"" link after VE has closed
+
+[[https://gerrit.wikimedia.org/r/181679]]
+
+#patch-for-review",1419973626,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"Seen in Firefox and Chrome: 
+
+Edit any page in VE, e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click Insert/Template
+
+The input text field briefly shows a cursor and a blue bar indicating that the element has focus, but then the focus disappears. User should be able to type directly into text field without needing to click the text field element first, but no longer can. 
+
+This is the failure at https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/423/testReport/(root)/VisualEditor%20Transclusion/Add_parameter_to_template/",1419893532,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-xtbmxjggz7gkbjodpajo,task_description,resolved
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"On Firefox 35 Mac, I am editing Wikipedia with the Visual Editor.
+
+By habit, I type ""{{cit"". This brings a dialog for choosing a template with one field for typing the name. But the ""cit"" went nowhere. And typing the name does nothing. I have to click in the field first. It would be nice to have the focus in the field. Thus, when we type, by habit, ""{{cit"", the characters ""cit"" would go in the field for the template name.
+
+Thank you.
+",1423492732,PHID-USER-fjve3gq5wsmaaccti7pb,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,Fixed/checked in beta.,1422565427,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"Change 186505 merged by jenkins-bot:
+Focus the add template input in the template dialog
+
+[[https://gerrit.wikimedia.org/r/186505]]",1422069884,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"Change 186505 had a related patch set uploaded (by Mooeypoo):
+Focus the add template input in the template dialog
+
+[[https://gerrit.wikimedia.org/r/186505]]
+
+#patch-for-review",1422050824,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,Duplicate to https://phabricator.wikimedia.org/T86040,1420664997,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"Still happening for me - Mac - betalabs FF, Chrome and Windows7 IE. ",1419962342,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,This no longer happens,1419959811,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"As a logged in user with access to VE in MobileFrontend, bring up a random page and click the pencil icon to edit with VE e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/0.6922277312143298#/random. 
+
+Note that in the upper left, the back-arrow icon ""escape"" button appears before the other controls. 
+
+Click the back-arrow escape icon as the page loads, before the page is finished loading. Nothing happens. 
+
+This is the failure at https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/455/testReport/(root)/VisualEditor%20Mobile/Going_back_from_save_screen_in_VisualEditor/",1419890942,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_description,resolved
+Back arrow appears before other VE controls in MobileFrontend but does nothing,Verified the fix in en.wiki,1421363585,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,Verified the fix in Betalabs and test2,1420605576,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"https://gerrit.wikimedia.org/r/#/c/181698/ also needs to get deployed.
+",1420562666,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"I stand corrected, this is now fixed in master. The error above is in wmf13, so we seem to have missed another patch that should be cherry-picked.",1420562558,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"`Uncaught TypeError: boolean is not a function in Overlay.extend.hide`
+
+ It's trying to call `this._hasChanged()` , while `this._hasChanged` is a boolean property (set to true). Appears to be related to https://gerrit.wikimedia.org/r/#/c/182113/ , which was cherry-picked to wmf13 but doesn't seem to have solved everything.",1420561914,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"```Uncaught TypeError: boolean is not a function in Overlay.extend.hide```. It's trying to call ```this._hasChanged()``` , while ```this._hasChanged``` is a boolean property (set to true). Appears to be related to https://gerrit.wikimedia.org/r/#/c/182113/ , which was cherry-picked to wmf13 but doesn't seem to have solved everything.",1420561885,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Lua error: too many language codes requested,"When trying to assemble the December's issue of VE multilingual newsletter,
+I got this message after [[ https://meta.wikimedia.org/w/index.php?title=VisualEditor%2FNewsletter%2FSandbox&diff=10833033&oldid=10815060  |  this edit ]] (I guess LUA can't actually handle so many languages. If I'm right, this needs to change - 20-something languages aren't ""many"" at all.)
+
+More info:
+
+Backtrace:
+[C]: in function ""isRTL""
+mw.language.lua:99: in function ""isRTL""
+mw.language.lua:132: in function ""getDir""
+Module:Assemble_multilingual_message:46: in function ""chunk""
+mw.lua:490: ?",1419877407,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_description,resolved
+Lua error: too many language codes requested,Wouldn't it be nice to automatically set the value of whether manual recache is enabled or not? Hopefully things will be faster when we start hitting the 200 languages limit :),1526991905,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Change 430068 **merged** by Tim Starling:
+[operations/mediawiki-config@master] Raise Scribunto maxLangCacheSize to 200
+
+[[https://gerrit.wikimedia.org/r/430068]]",1526813253,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Change 430068 had a related patch set uploaded (by Anomie; owner: Anomie):
+[operations/mediawiki-config@master] Raise Scribunto maxLangCacheSize to 200
+
+[[https://gerrit.wikimedia.org/r/430068]]",1525183146,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"I just run into this issue again at https://commons.wikimedia.org/wiki/Module_talk:Name/testcases Maybe some functions do not need to be in the language objects, like: mw.language:isRTL or mw.language:lc. 
+
+One consequence of this error is that lua code writers avoid calling mw.language functions and use  frame:callParserFunction instead. For example [[ https://commons.wikimedia.org/wiki/Module:Date| c:Module:Date]] (used on 46M pages) uses `datestr = mw.getCurrentFrame():callParserFunction( ""#time"", { dFormat, timeStamp, lang } )` instead more logical `datestr = mw.language.new(lang):formatDate( dFormat, timeStamp) `. The output is the same except for no ""Lua error: too many language codes requested"".  From performance point of view, is there a difference between mw.language.new(lang) and mw.getCurrentFrame():callParserFunction calls?",1525181352,PHID-USER-j4jntnatcouoxfrk74sh,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Change 343590 merged by jenkins-bot:
+[mediawiki/extensions/Scribunto@master] Make the maximum language cache size configurable
+
+[[https://gerrit.wikimedia.org/r/343590]]
+",1490279834,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Alright @Elitre, I wrote the patch for option 2. https://gerrit.wikimedia.org/r/#/c/343590/",1489979106,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Change 343590 had a related patch set uploaded (by Tim Starling):
+[mediawiki/extensions/Scribunto] Make the maximum language cache size configurable
+
+[[https://gerrit.wikimedia.org/r/343590]]
+",1489979057,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,Thanks Tim. What needs to be done here? Do we need to involve someone in particular in this conversation? (I'd really love to be able to deliver the next visual editor newsletter into more than 20 languages.),1489592232,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"IIRC my concern was that there was no eviction from the cache in LocalisationCache::$data, which continues to be the case. If recaching is required, memory usage is about 1.5MB per language, measured locally today. So a limit of 20 implies 30MB, which seems reasonable compared to the Lua memory limit of 50MB.
+
+However, in the WMF production setup, l10n recaching is done in advance, so there's no way recaching would be done in response to a Lua request. It only needs to load the preloaded messages plus the data actually requested (isRTL). Using eval.php on a production server, I measured 145KB per language, which is not so concerning.
+
+So I think the options are:
+# Fix LocalisationCache so that it doesn't use unlimited amounts of memory when recaching on demand. Implementation ideas can be found in LocalisationCacheBulkLoad.
+# Make MAX_LANG_CACHE_SIZE configurable and set it to say 200 on WMF, leave it at 20 by default. We would probably need to add ScribuntoEngineBase::getOptions() so that Scribunto_LuaLanguageLibrary::register() can get access to the configuration options, which are stored in a protected variable.
+# Increase the default MAX_LANG_CACHE_SIZE very modestly, say to 30. This seems like a bad choice since in a month or two someone will reopen the same bug, having found a really important use case for loading 31 languages.
+
+Somewhat off topic, but speaking of lightweight Language object construction, I think having $wgLangObjCacheSize = 10 by default is actually bit rot, I don't think there's any reason for that anymore. Language objects used to hold message arrays, presumably that is the reason for it being so low.",1489556381,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Would it be feasible to raise the cap to, say, 30 languages (although that's a limit the VE newsletter has already crushed at least once) and see how it goes?",1485854372,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"This seems to go back to the issue that constructing language objects was slow and memory consuming. The most likely culprit was the preloading a big set of language data and some messages every time a language object was constructed. But I was under the impression that this has been improved enough a long time ago, so maybe the restriction in Lua is not necessary anymore. Or if it turns out there are still issues, Language object construction should be made light-weight.",1485853303,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,Yes.,1460741037,PHID-USER-go2ym6ta2zn6ofdsrqnx,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"@johan, I gather this is a problem you may also have at some point.",1457976468,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"This limit is also why Commons template:Dir (https://commons.wikimedia.org/wiki/Template:Dir ), which is the most transcluded template on Commons (with 32,721,515 pages transcluding it) is not using Lua's ""isRTL"" function. ",1436464033,PHID-USER-j4jntnatcouoxfrk74sh,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Thank you, Anomie! The VE newsletter is quite popular, so I'd really like to get rid of the restriction somehow if possible (/bragging).",1419885375,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,">>! In T85461#947512, @Elitre wrote:
+> Has this never occurred for Tech News?
+
+No, we've never had so many translations in Tech News.",1419881226,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"I note the restriction was added by Tim (see [[https://gerrit.wikimedia.org/r/#/c/36496/|Gerrit change 36496]], which was the original source of [[https://gerrit.wikimedia.org/r/#/c/42050/|Gerrit change 42050]] that was actually merged), so adding him as a CC here.",1419880981,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Thanks, Guillaume. Splitting the page doesn't seem very feasible though - one would have to split recipients' lists as well, and maintaining them... doesn't really look sustainable. Has this never occurred for Tech News?",1419880694,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,See also https://www.mediawiki.org/wiki/Extension_talk:Scribunto/Lua_reference_manual#Lua_error:_too_many_language_codes_requested.,1419879839,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","The first time I open a link inspector using ""[["", Ctrl-K, or the toolbar button, it takes about 5 seconds on my laptop. The subsequent times I do it in the same editing session it opens immediately.",1419347942,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_description,resolved
+"the first time that the VisualEditor link inspector appears, it takes a very long time","Awesome, thanks.",1420932762,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","What happened is that inspector dialogs no longer use isolation, so my
+guess was probably correct.",1420932545,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","I'm not sure what happened, but I cannot reproduce it on Firefox in the version that is currently deployed in Wikipedia. The link inspector appears immediately.",1420930784,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","What do you know, it's indeed faster on Chrome - about 1.5 seconds.",1419360301,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","I also vaguely recall this having been reported already, but can't find it. I only found T72467, which was actually an entirely separate issue.",1419350684,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","This also happens for me when using Opera 12 (which is somewhat slow compared to more modern browsers). The inspector dialogs are still using isolation (rendered inside an `<iframe>`) and I can reproduce using isolated dialogs in the demo, so that's probably the reason. We're apparently working on killing isolation, though.",1419348629,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","(This may be a dupe. I remember reporting it a few weeks ago, but I cannot find it now.)",1419348170,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#Schedule
+Monday 26, 10:30am
+
+@Tfinc is the owner of the Mobile theme at the #MWDS15. He is also in charge of organizing the Mobile plenary session, or find someone to organize it.
+
+meeting notes: http://etherpad.wikimedia.org/p/MWDS2015_multi-device_world",1419267000,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-chdbjfofb5zihbj3xecj,task_description,resolved
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,">>! In T85151#1068841, @MZMcBride wrote:
+> Is there a reason this task is still open?
+
+Let's find out.",1424916580,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,Is there a reason this task is still open?,1424915627,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,Please update the description with the achievements of this session. Thank you in advance.,1422341688,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,Etherpad for today: https://etherpad.wikimedia.org/p/MultiDeviceWorld,1422292449,PHID-USER-qmantxp3p7omhisp3qgq,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Currently you have 45 minutes for this plenary session, and right after you have another 45' slot in the main room for a non-plenary session to be defined. If you want to pre-schedule this second session, we need urgently a task describing it. Or perhaps you want to extend this topic, having a short break after the first 45' leading to a discussion among those staying in the room?",1421226727,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Good discussion today about the plenary and focusing it on the challenges of preparing for a multi device world and what technological blockers/opportunities we have. We've done a quick pass on what we'd like to highlight:
+
+* Desktop <-> Mobile convergence
+** Highlight success/challenges of building for both
+* Building mobile-relevant applications
+** Wikirgrok, infoboxes, etc
+* WikiData
+** How recent mobile app work can enable new desktop workflows
+* Editing/Micro Contributions (Gabriel/JonR)
+* What's slowing us down?
+** API availability
+
+Which may change as the week goes on. Over the next days we'll prepare a short plenary on this, room for discussion, and the the relevant breakout sessions.
+
+notes: http://etherpad.wikimedia.org/p/DevSummitMain
+
+
+",1421100694,PHID-USER-qmantxp3p7omhisp3qgq,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Personally I want people to come out of the session with the mind to explore the limitations of our existing software when it comes to editing and challenges these issues.
+
+From Mobile Web perspective, summarising what @Kaldari and I have said I can see the tdlr as
+* People have less time and need new ways to contribute especially on mobile
+* We are exploring new was such as Wikigrok and infoboxes (we could refer to mobile uploads and how that showed a thirst to edit but wasn't the right fit)
+* Editing does not have to be editing a big chunk of text e.g. wikitext/VisualEditor full edit page
+* Take away: How can we do more of this? How can we break down our current editing model using things like wikidata and Parsoid? Let's spend the summit exploring that.
+",1420824213,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Here's a quick outline for a presentation on WikiGrok:
+
+Motivation:
+* Give readers an easy way to make contributions on mobile
+* Help build Wikidata for the semantic future
+* Experiment with game-like contribution methods
+
+History:
+* Magnus's Wikidata Game
+* Consulted Magnus at Wikimania 2014 and built prototypes
+* First working versions October 2014 (A and B versions)
+* Rewrote backend to be scalable
+* Removed dependency on Magnus's Wikidata query API
+* Test for logged in users (December 2014)
+* Test for anonymous readers (January 2014)
+* WikiGrok Roulette (January 2014)
+
+Future:
+* Pick an interface version
+* Push data to WikiGrok
+* Add new campaigns
+* Use to verify existing data or data from other databases
+* New Wikidata query engine for asking better questions
+* Desktop version?
+* More gamification?",1420792533,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Thoughts so far:
+The goal of the native Mobile Apps is to bring the contents of Wikipedia as close as possible to the user's fingertips.  This means:
+1) Integrating more tightly with the OS on the user's device (notifications, widgets, location-based things, etc). This would require things like server-side APIs/infrastructure for push notifications.
+2) Presenting content in ways that the user ""expects"" to see, based on other patterns and behaviors in the mobile OS.  In this vein, Wikipedia content has to become more ""parceled"" into factoids for consumption on mobile. (Thus, an ever-growing dependency on Wikidata)
+We've started to tackle some of #2, with our implementation of Lead Images, as well as the Gallery feature (not to mention Wikidata descriptions throughout the app).  
+We could begin by demoing our work on lead images, and the associated successes and challenges that came out of it.  We'll show a few articles where the lead image looks excellent and really transforms the first-glance experience of the article. We'll also show some articles where the lead image is ""suboptimal"", which would lead to a discussion about face detection for proper alignment of the image, a possible microcontribution for the proper cropping/alignment of the image (or indeed which image to use as the lead image), etc.",1420766517,PHID-USER-pbvnfgskfwsdalhpd7np,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"**Apps! Try all the things!  **
+
+Native apps provide a unique opportunity to showcase Wikipedia media and data, in boundary pushing, even beautiful ways.   
+
+With ""lead image styling"" we've mixed article title, main image and Wikidata descriptions seamlessly at the top of the article.  
+
+With search results, saved pages, recent and nearby items we've incorporated Wikidata descriptions.  
+
+With native article image galleries, users get instant access to a liquid smooth image browsing interface.  
+
+With nearby we've leveraged location awareness and native performance to guide readers to article geodata coordinates.  
+
+APIs for search, nearby and article data were enhanced to return Wikidata descriptions so we didn't have to make separate requests. Other API clients can now do this as well.      
+
+
+
+**Challenges & Opportunities.  ** 
+
+One challenge we encountered with lead image styling was intelligent cropping for constrained lead image presentation. It can be difficult, given widely varying image dimensions, to determine what the ""focal area"" of an image is so we don't crop through it. Happily, apps can performantly determine certain image focal areas, so we don't crop a notable person's face noticeably in half.   
+
+However, there are edge cases. But we see these challenges as opportunities. If apps could hit a ""commons data"" endpoint for images, they could report back apps-detected image focal areas, and apps interfaces for users to curate focal area data would be trivial to implement as well. Then any consumer of commons images could easily perform intelligent cropping. ",1420766288,PHID-USER-ohzzl3maortma7y4znpb,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"@deskana, we'll have a plenary and several other sessions about SOA at the summit. See T85154 and T86028.
+
+I'm not sure yet whether there will be a dedicated evangelization session, but there should be an evangelizing effect in any case.",1420758125,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,">>! In T85151#961900, @RobLa-WMF wrote:
+> 
+> @Maryana, I have heard in meetings the murmurings of putting desktop on hold.  Not from you, and I don't think the suggestion has truly taken root in our planning process, but I believe it's well worth spelling out (or discussing) in a plenary a very general sense of the size and shape of our investment in desktop vs mobile user interface in the next year or two.  I'll grant you that there's no master plan, but I've also heard many intelligent and compelling hunches about what the right strategy is.  
+> 
+> We will probably need to state the (only seemingly obvious) point that it's not a zero sum game where more mobile investment == less desktop investment.  For example, while our work on Wikidata querying (T85159) was motivated by a mobile use case, there is absolutely nothing mobile specific about the service.  In fact, the heart of our strategy almost certainly needs to be minimizing the cases where we are making zero sum tradeoffs.
+
+Investments into creating a service-oriented architecture for our projects is another example of this choice often not being zero-sum; the mobile apps as pure API consumers benefit greatly from having cleanly defined services, but in actuality this benefits any API consumer, and there are plenty of API consumers on desktop! And, although the discussion about front-end standardisation is of prime importance to mobile web and desktop, it's irrelevant for the mobile apps as they use the front-end frameworks and design patterns that come with the iOS and Android SDKs and platforms. So, even that isn't as zero-sum as it appears! :-)
+
+On the topic of service-oriented architecture, Rob raised the astute point that although service-oriented architecture may seem obvious to us at the WMF, it may not be obvious to others. Our developer community is very decentralised, and one of the disadvantages of a decentralised community is that a bit harder to get people to rally around a totally new concept and way of doing things, such as SOA. And since there is clearly a big belief that service-oriented architecture is the future, the developer summit is a prime opportunity to speak to this decentralised community and evangelise service-oriented architecture to them. Is @gwicke planning anything such as this for the summit?",1420736803,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,">>! In T85151#961318, @Maryana wrote:
+> It sounds like these ""mobile skeptics"" you're alluding to assume that WMF has already formulated some big mobile master plan (and perhaps cynically believe it involves ditching desktop development altogether...?),
+
+@Maryana, I have heard in meetings the murmurings of putting desktop on hold.  Not from you, and I don't think the suggestion has truly taken root in our planning process, but I believe it's well worth spelling out (or discussing) in a plenary a very general sense of the size and shape of our investment in desktop vs mobile user interface in the next year or two.  I'll grant you that there's no master plan, but I've also heard many intelligent and compelling hunches about what the right strategy is.  
+
+We will probably need to state the (only seemingly obvious) point that it's not a zero sum game where more mobile investment == less desktop investment.  For example, while our work on Wikidata querying (T85159) was motivated by a mobile use case, there is absolutely nothing mobile specific about the service.  In fact, the heart of our strategy almost certainly needs to be minimizing the cases where we are making zero sum tradeoffs.
+
+However, there are going to be cases where it is zero sum.  Good user interface is messy like that.  We need to have a frank conversation about how much to invest in which area.
+
+> but the reality is that our mobile teams and projects are still very new/emergent, we're still in the exploratory phase with a lot of our work, and there are still many ideas floating around for the directions mobile could go in the future.
+
+I don't think this part needs a great deal of consensus building.  It needs some, because we have a lot of people working on it, and so one could argue we could scale back a little, but that's not the most urgent aspect that requires a big group conversation, and that's not what I was thinking of.
+
+> So I think a ""group alignment conversation"" is a bit premature. It might be better just to provide a space to talk openly about all these possible future directions (mobile as a service! mobile as the one skin to rule them all! mobile as the shiny new unicorn!, etc.), without necessarily forcing any sort of consensus on the process or making it seem like any of these things are going to happen tomorrow ;)
+
+Sure, there are limits to what we can accomplish in one session or even over the course of two days.  Just having the open conversation might be enough.  And, we don't have to ""force"" consensus in any way.  However, I think we should inject some amount of urgency and relevance to the conversation, and aspire to actually get something done by having the conversation.
+
+BTW, as long as we're using quotes here, I am going to have to point out that I did say ""mobile strategy skeptics"" and not ""mobile skeptics""  :-)",1420699618,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,">>! In T85151#961318, @Maryana wrote:
+> It sounds like these ""mobile skeptics"" you're alluding to assume that WMF has already formulated some big mobile master plan (and perhaps cynically believe it involves ditching desktop development altogether...?), but the reality is that our mobile teams and projects are still very new/emergent, we're still in the exploratory phase with a lot of our work, and there are still many ideas floating around for the directions mobile could go in the future.
+
+I'm not sure where you get new/emergent from. MobileFrontend is not new. And there was a completely separate mobile site before it and a completely separate mobile site before that, so we're talking about many years of experience here.
+
+A lot of mobile development has come about as the result of either stripping everything away and slowly and painfully re-implementing it (category links at the bottom of the page is a small example of this) or the result of trying to inject features into mobile first as a means of bypassing what would likely be outright rejection, for better or worse, on desktop (Special:UserProfile and the last edit strapline at the top of the page are two examples of this).
+
+So, scare quotes or not, yeah, there needs to be a discussion about what mobile development has looked like and what it should look like going forward. The cold hard truth is that writing an encyclopedia (or a dictionary or a whatever) on the desktop site continues to be a pretty agonizing process. It's basically currently impossible to do serious editing on a mobile device and may remain so indefinitely, again for better or worse. The best we can probably hope for is optimizing micro-contributions, as kaldari says, and reunifying the desktop and mobile experiences, work on which has thankfully finally started.",1420693651,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,We should definitely have at least one presentation about microcontributions via Wikidata. This would probably show off WikiGrok and possibly the experimental infobox and description editing. I would really like to have Jon's ForiegnApi code (https://gerrit.wikimedia.org/r/#/c/182134/) implemented as a core mediawiki module before then so that people can hack with it in the break-out sessions (on both desktop and mobile). Other possible things to demo include the experimental lead section styling in alpha and the mobile Media Viewer.,1420682543,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"
+
+
+
+
+
+>>! In T85151#961235, @RobLa-WMF wrote:
+> I think we need to have a large group alignment conversation about our engineering strategy around mobile, and what the organization as a whole should be doing.  I repeatedly hear skepticism about the fall of desktop and rise of mobile as a reason to drop what we're doing and have everything be about mobile.  It's not so much skepticism about the fact that it's happening (though there is a little misplaced skepticism there), but cynicism about what that fact is being used to justify.
+> 
+> The temptation on this session would be to ""go with what we know"", which is lots of presentations and demos.  These will be utterly unconvincing and unengaging to mobile strategy skeptics.  I think it likely needs to be a conversation rather than a presentation in order to win over skeptics, but exactly what this looks like is a bit unclear to me.
+
+It sounds like these ""mobile skeptics"" you're alluding to assume that WMF has already formulated some big mobile master plan (and perhaps cynically believe it involves ditching desktop development altogether...?), but the reality is that our mobile teams and projects are still very new/emergent, we're still in the exploratory phase with a lot of our work, and there are still many ideas floating around for the directions mobile could go in the future. So I think a ""group alignment conversation"" is a bit premature. It might be better just to provide a space to talk openly about all these possible future directions (mobile as a service! mobile as the one skin to rule them all! mobile as the shiny new unicorn!, etc.), without necessarily forcing any sort of consensus on the process or making it seem like any of these things are going to happen tomorrow ;)",1420676428,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"I think we need to have a large group alignment conversation about our engineering strategy around mobile, and what the organization as a whole should be doing.  I repeatedly hear skepticism about the fall of desktop and rise of mobile as a reason to drop what we're doing and have everything be about mobile.  It's not so much skepticism about the fact that it's happening (though there is a little misplaced skepticism there), but cynicism about what that fact is being used to justify.
+
+The temptation on this session would be to ""go with what we know"", which is lots of presentations and demos.  These will be utterly unconvincing and unengaging to mobile strategy skeptics.  I think it likely needs to be a conversation rather than a presentation in order to win over skeptics, but exactly what this looks like is a bit unclear to me.",1420674906,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"What are we aiming to achieve in this Mobile plenary session? You will have all the Summit attendees in one room, right after the opening. Which are the key messages you want to push? What do you want from them?
+
+>>! In T85151#959834, @Jdlrobson wrote:
+> explore other ways to edit that are not via the traditional wikitext model.
+> (...)
+> I think essentially the role of mobile is to break down the complicated wikitext markup language that we have built over the last 10 years and encourage our projects to dogfood Wikidata more and make wikitext easy for newbies to understand again.
+
+I wonder how this 'role of mobile' you are describing fits with the role of VisualEditor and the Editing plans altogether. CCing JamesF.",1420649507,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Early thoughts:
+""Think outside the wikitext""(play on think outside the box) In addition to demoing the obvious Wikigrok, in the plenary I would like to propose demoing the Wikidata infobox editing/lead photos in alpha [1]. Although we currently have no plans to productise this and this is an experimentation project, I think it would be a useful thought exercise to imagine a world where we start breaking down wikitext and reducing our dependency on {{template markup}} and explore other ways to edit that are not via the traditional wikitext model.
+
+I'm not sure what the reaction to this will be. For instance if infoboxes were generated from Wikidata and not within the markup how would our existing community react to that? But I'd hope it might polarise the crowd and lead to some interesting conversations going out of it.
+
+I think essentially the role of mobile is to break down the complicated wikitext markup language that we have built over the last 10 years and encourage our projects to dogfood Wikidata more and make wikitext easy for newbies to understnd again. Microedits are proving successful in mobile and we need to find better ways to support that. @GWicke and I have talked about how Parsoid can help do things such as insert citations in place of 'citation needed' text and I'm hoping we can have a session around Parsoid/Mobile in one of the later sessions to continue this theme.
+
+[1] http://en.m.wikipedia.beta.wmflabs.org/wiki/Albert_Einstein?wikidataid=Q937&mobileaction=alpha",1420647216,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Picking this back up now that were all back. 
+
+Tech leads: @kaldari @Dbrant @Mhurd @jdlrobson
+
+We have a 45min plenary that were going to be creating here. I'd like to have your list of topics by Thur of this week to review and be able to run the by Damon on Friday. Each topic should take up 10-20 if your presenting with someone else or 10-15 if your on your own. Out of these we'll need to think about the potential breakout sessions we brainstormed last month [1] and get them on the MediaWiki Developers Summit Schedule [2] 
+
+No need to create slides at this point (or at all if your demoing), keep them at high level bullet points so that we can validate with Damon and move forward. 
+
+If there are others that want to jump in on the planning of this then please let me know.
+
+[1] - http://etherpad.wikimedia.org/p/Mobile-WMDS
+[2] - https://docs.google.com/spreadsheets/d/15pMDR_h84KUTQK7IR95etVJyJBYC5nVxoG9k_9danV0
+",1420586285,PHID-USER-qmantxp3p7omhisp3qgq,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Picking this back up now that were all back. 
+
+Tech leads: @kaldari @Dbrant @Mhurd @jdlrobson
+
+We have a 45min plenary that were going to be creating here. I'd like to have your list of topics by Thur or this week to review and be able to run the by Damon on Friday. Each topic should take up 10-20 if your presenting with someone else or 10-15 if your on your own. Out of these we'll need to think about the potential breakout sessions we brainstormed last month [1] and get them on the MediaWiki Developers Summit Schedule [2] 
+
+No need to create slides at this point (or at all if your demoing), keep them at high level bullet points so that we can validate with Damon and move forward. 
+
+If there are others that want to jump in on the planning of this then please let me know.
+
+[1] - http://etherpad.wikimedia.org/p/Mobile-WMDS
+[2] - https://docs.google.com/spreadsheets/d/15pMDR_h84KUTQK7IR95etVJyJBYC5nVxoG9k_9danV0
+",1420582333,PHID-USER-qmantxp3p7omhisp3qgq,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Current feeling is to have the tech leads from mobile web @kaldari and apps @dbrant @mhurd present on at least 1 and at most 2 products/features that they've shipped over the last 6 months to highlight what's possible on mobile and what is difficult and/or impossible to do. It would be interesting to have @maryana and @deskana weigh in on those too. I'm going to be eager to paint the narrative of opportunity and highlight where we can do better. Especially along API's, services, etc.
+
+We spent some time earlier this week brainstorming some potential sessions to get us started
+
+http://etherpad.wikimedia.org/p/Mobile-WMDS",1419301604,PHID-USER-qmantxp3p7omhisp3qgq,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"{F22740}
+
+This is caused by MobileFrontend setting box-sizing: border-box on every element.",1419112500,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_description,resolved
+Inspector titles clipped in VisualEditor on mobile,"Belay that. now that T86366 is fixed, this is fixed too in master. Thanks!",1429205383,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,Yes. We're waiting for the stalled patch in Mobile to be merged.,1429205322,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Is this still a problem?
+",1429205262,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"I'm waiting for a reply here: https://phabricator.wikimedia.org/T86366#1136772
+",1428450186,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"So I tried VE on mobile using the latest MobileFrontend master with ""Experimental"" (alpha) enabled. It looks to me like it's still getting clipped because of that `height: @icon-size` on `.oo-ui-processDialog-location`?",1428443967,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Change 180775 abandoned by Jdlrobson:
+Remove border-box rule from reset.less
+
+Reason:
+https://gerrit.wikimedia.org/r/183987 is merged now so removing this from the review backlog. We can always restore it later depending on the outcome of that patch. Thanks for your patience.
+
+[[https://gerrit.wikimedia.org/r/180775]]",1422893603,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Change 183987 merged by jenkins-bot:
+Turn off universal box-sizing in alpha
+
+[[https://gerrit.wikimedia.org/r/183987]]",1422665702,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Change 183987 had a related patch set uploaded (by Jdlrobson):
+Turn off universal box-sizing in alpha
+
+[[https://gerrit.wikimedia.org/r/183987]]
+
+#patch-for-review",1420840039,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"I think my fix is the only sensible way to fix the bug. I'm happy with the patch in its current state, but ideally I'd like someone from mobile to give it a test.",1420657204,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"@Jdlrobson, @Esanders: What's the status on this? If Ed's change isn't going to be merged, we should at least fix this specific bug.",1420656568,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Change 180775 had a related patch set uploaded (by Esanders):
+Remove border-box rule from reset.less
+
+[[https://gerrit.wikimedia.org/r/180775]]
+
+#patch-for-review",1420456979,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,Every element? So... Fix MobileFrontend?,1419509177,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request","The output of the embedded `user.tokens` module changes on every request. I'm not entirely sure whether this was on purpose.
+
+Traced it back to https://github.com/wikimedia/mediawiki/commit/b1e4006b44
+{b1e4006b44}
+
+This is a bit of a problem since we minify this module, and by default all minifications are cached at a key that is the hash of the unminified contents. We should implement a way to bypass the minification cache.
+
+As such, we're creating a new cache key and populating it on every page view for every logged in user. And that key is never used again.
+
+Example from localhost:
+
+```
+<script>...mw.loader.implement(""user.tokens"",function($,jQuery){mw.user.tokens.set({""editToken"":""5da7f8da8cc2c12b40e63510d3b83f3754937d96+\\"",""patrolToken"":""bc1e366f8f7806ed27d067667cdeebe554937d96+\\"",""watchToken"":""c52e9fcc036b315fe8ba3e0135cb928d54937d96+\\""});},{},{},{});
+/* cache key: alphawiki:resourceloader:filter:minify-js:7:aed9432283c8152b3eaff1761844e771 */
+```",1418952452,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qguei6bgca37llfakum,task_description,resolved
+"Embedded ""user.tokens"" module changes on every request","With the cache issues resolved, this is no longer a performance problem.
+
+The constant regeneration isn't actually a problem since they are not actually all stored. MediaWiki uses encoding and encryption to restrict internal tokens with a timestamp salt.
+
+> 6fa4893928 — resourceloader: Don't cache minification of user.tokens
+> https://gerrit.wikimedia.org/r/210845
+",1435036147,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request","Here's a graph showing a successful drop in RL-minification cache lookups after deploying [I6016e4b01e44](https://gerrit.wikimedia.org/r/#/q/I6016e4b01e44,n,z).
+
+Labels added to match relevant events from the [Server Admin Log](https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&oldid=161613).
+{F173780}
+
+Source: https://graphite.wikimedia.org/render?from=-4weeks&until=now&width=900&target=MediaWiki.rl-minify-js-cache-misses.count
+",1433343594,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#1284121, @Anomie wrote:
+>>>! In T84960#1284083, @Krinkle wrote:
+>> I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes.
+> 
+> Except that's not true. I see nothing in MediaWiki core or WMF-deployed extensions that uses the $maxage parameter for User::matchEditToken() except the ApiCheckTokens module. Maybe Restbase is doing it, but nothing currently in PHP is considering tokens expired any sooner than the end of the session.
+
+I'm guessing VE is submitting to restbase, and restbase is using ApiCheckTokens to check the token. I've lost track of who did that integration (Roan? Gwicke?), but I'm guessing that call needs to fix the maxtokenage param?",1431620193,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#1284083, @Krinkle wrote:
+> I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes.
+
+Except that's not true. I see nothing in MediaWiki core or WMF-deployed extensions that uses the $maxage parameter for User::matchEditToken() except the ApiCheckTokens module. Maybe Restbase is doing it, but nothing currently in PHP is considering tokens expired any sooner than the end of the session.",1431572729,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#950866, @Anomie wrote:
+> The point isn't to make the tokens last **longer** than the session. [...] You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or [..]
+
+I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes. Similarly it seems useless that VisualEditor and other uses of tokens almost always have to make two or three round trips just to make a write action. Right now its three. 1) Failed write action for token expired, 2) get new token, 3) Re-try write again. Not only does it make two more http requests then desired, it also transmits a potentially large amount of data to the server multiple times. We could cut this back to 2 requests by making the client-side aware of how long the tokens are valid for. While that is better, it is imho not good enough.
+
+Two facts:
+
+* In the past we made the decision to embed the user.tokens module in the page because we saw performance problems with the client-side having to request a token for write actions by JavaScript (for e.g. watch star click, or VE edit save).
+* In the past we made the observation that saving content with VisualEditor is a performance bottle neck, that we worked hard to cut down. Due to this token expiration problem, we basically nullified all that effort by having to submit everything twice for a lot of users.
+
+As such, I would recommend strongly that we **figure out a feasible way to allow MediaWiki frontend to perform write actions with the API without needing to fetch a token over a separate HTTP request**. The client's cookie is already authority enough to request as many tokens as it wants during the session, so in theory it seems really stupid that we need a token at all when making a write action. Clearly whatever origin can make or forge one request, can also forge the other. Raising the bar might make sense to just make it a tiny bit harder, but I'm questioning whether that's worth it.
+
+From this perspective, this change was a significant regression as both of these two expectations are no longer met by the system.
+
+The naive approach of not making the tokens change every request is understandably not acceptable from a security perspective because of ""BREACH""-type reflection attacks. The only option I left then is to continue issuing new tokens each page view but have those tokens (that are embedded in the page) be valid for the entire duration of a page view (or otherwise, at least for an hour or so).",1431569278,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#950866, @Anomie wrote:
+> The point isn't to make the tokens last **longer** than the session. [...] You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or [..]
+
+I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes. Similarly it seems useless that VisualEditor and other uses of tokens almost always have to make two or three round trips just to make a write action. Right now its three. 1) Failed write action for token expired, 2) get new token, 3) Re-try write again. Now only does it make two more http requests then desired, it also submits a potentially large amount of data multiple times.
+
+Two facts:
+
+* In the past we made the decision to embed the user.tokens module in the page because we saw performance problems with the client-side having to request a token for write actions by JavaScript (for e.g. watch star click, or VE edit save).
+* In the past we made the observation that saving content with VisualEditor is a performance bottle neck, that we worked hard to cut down. Due to this token expiration problem, we basically nulled that effort by now having to submit everything twice.
+
+As such, I would recommend strongly that we figure out a feasible way to allow MediaWiki frontend to perform write actions with the API without needing to fetch a separate token over HTTP. From this perspective, this change was a significant regression as both of these two expectations are no longer met by the system.
+
+The naive approach of not making the tokens change every request is understandably not acceptable from a security perspective because of ""BREACH""-type reflection attacks. The only option I see right now would be to continue issuing new tokens each page view but having those tokens (that are embedded in the page) be valid for the entire duration of a page view (or otherwise, at least an hour or so).",1431568900,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#950866, @Anomie wrote:
+> The point isn't to make the tokens last **longer** than the session. [...] You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or [..]
+
+I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes. Similarly it seems useless that VisualEditor and other uses of tokens almost always have to make two or three round trips just to make a write action. Right now its three. 1) Failed write action for token expired, 2) get new token, 3) Re-try write again. Now only does it make two more http requests then desired, it also submits a potentially large amount of data multiple times.
+
+Two facts:
+
+* In the past we made the decision to embed the user.tokens module in the page because we saw performance problems with the client-side having to request a token for write actions by JavaScript (for e.g. watch star click, or VE edit save).
+* In the past we made the observation that saving content with VisualEditor is a performance bottle neck, that we worked hard to cut down. Due to this token expiration problem, we basically nulled that effort by now having to submit everything twice.
+
+As such, I would recommend strongly that we figure out a feasible way to allow MediaWiki frontend to perform write actions with the API without needing to fetch a separate token over HTTP. From this perspective, this change was a significant regression as both of these two expectations are no longer met by the system.
+
+The naive approach of not making the tokens change every request is understandably not acceptable from a security perspective because of ""BREACH""-tpe reflection attacks. The only option I see right now would be to continue issuing new tokens but having tokens that are embedded in the page be valid for the entire page view session (or otherwise, at least an hour or so).",1431568844,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#950866, @Anomie wrote:
+> The point isn't to make the tokens last **longer** than the session. [...] You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or [..]
+
+I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes. Similarly it seems useless that VisualEditor and other uses of tokens almost always have to make two or three round trips just to make a write action. Right now its three. 1) Failed write action for token expired, 2) get new token, 3) Re-try write again. Now only does it make two more http requests then desired, it also submits a potentially large amount of data multiple times.
+
+Two facts:
+
+* In the past we made the decision to embed the user.tokens module in the page because we saw performance problems with the client-side having to request a token for write actions by JavaScript (for e.g. watch star click, or VE edit save).
+* In the past we made the observation that saving content with VisualEditor is a performance bottle neck, that we worked hard to cut down. Due to this token expiration problem, we basically nulled that effort by now having to submit everything twice.
+
+As such, I would recommend strongly that we figure out a feasible way to allow MediaWiki frontend to perform write actions with the API without needing to fetch a separate token over HTTP. From this perspective, this change was a significant regression as both of these two expectations are no longer met by the system.",1431568646,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request","I have no idea what distinction you're making between ""client-side"" tokens and other tokens. All tokens are sent from the server to the client via a channel that CSRF attackers shouldn't have access to, and then sent from the client back to the server to detect CSRF.
+
+The point isn't to make the tokens last **longer** than the session. That won't happen anyway, if the session is lost then all the tokens go away too just as they have always done. The point is to make it possible for tokens to expire **before** the session does to reduce the window of vulnerability if an attacker somehow manages to compromise a single token, with a predictable lifetime after generation for each token. You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or get a 5-minute token but then it expires early because some other code requests another instance of the same token, and you won't be able to flood the session with hundreds of tokens waiting to expire. The constantly-changing nature of the tokens also protects against attacks such as BREACH which depend on multiple requests to reveal individual bits or bytes of a constant token.
+
+
+Now, if the caching situation really can't be worked around by requesting the tokens from the API as needed, we might be able to make User::getEditTokenAtTimestamp() public and use that to generate a token with a constant distant-past timestamp for your JS. Uses of the token that don't specify a maximum age will accept such a token as long as the session is valid, while uses that do will still treat them as expired. But I'd wait for Chris to look that plan over before spending a lot of time on it.",1420041856,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#936308, @Anomie wrote:
+> Why is this bug marked as private? I'm not seeing anything obviously sensitive here.
+
+I filed it under security because the varying tokens, while sensible in general, wasn't necessarily applied on purpose for API requests from the web interface. There also seems potential abuse against the minification cache. Or at the very least a performance/scale hazard for sites without LRU in their cache system. MediaWiki's the default DB cache, for instance, would get blown up by this (my localhost install did).
+
+>>! In T84960#936308, @Anomie wrote:
+> Or the tokens could just be fetched from the API when they're needed instead of being served with every request.
+
+That would require fair amount of token fetching from the client-side for AJAX actions originating from core modules (e.g. watch), as well as gadgets and extensions.
+
+I'd like to better understand why tokens are time-limited. I assume it has to do with reducing impact of compromise. However does that apply to client-side tokens? The client is able to fetch tokens whenever using its session cookie (which doesn't mutate on every request). Sessions do expire, however. And having tokens last longer than the session seems odd. Perhaps we can associate them with a session and only give clients new tokens once per session? If I recall correctly, that was the previous behaviour as well for CSRF tokens used in HTML (e.g. for EditPage). Or was there a problem with that?",1419989593,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request","Why is this bug marked as private? I'm not seeing anything obviously sensitive here.
+
+> I'm not entirely sure whether this was on purpose.
+
+The fact that tokens change based on the time they're generated is necessary behavior of the time-limiting: the timestamp must be included (in ""plain"" text) in the token so it can be checked, and it must be included in the hash so it can't be faked.
+
+> We should implement a way to bypass the minification cache.
+
+Or the tokens could just be fetched from the API when they're needed instead of being served with every request.",1418999026,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Release VisualEditor-MediaWiki as ""1.0""","Lots of things to do here, but broadly they break down into six categories:
+
+[ ] Functionality – mostly done
+[ ] Performance – main focus area left
+[ ] User experience – the current integration is a bit lacking, but otherwise this is not far off
+[ ] Language support – still a lot of work for IME support here
+[ ] Browser support – mostly done
+[ ] Major bugs – not many of these left (he says…)",1418941653,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-supxiuf2snjkiztaupce,task_description,open
+"Release VisualEditor-MediaWiki as ""1.0""",1.0,1598446543,PHID-USER-mqxfovqi5o53vonvhaeh,PHID-TASK-supxiuf2snjkiztaupce,task_subcomment,NA
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,"In betalabs: 
+
+1. On a page in VE open Find/Replace - not typing anything in it, just open - a cursor will be in the Find field.
+1. Open an existing template on the page for editing.  
+2. Place a cursor in the first field of the transclusion box and click Tab to navigate to the next field.
+
+The cursor will be placed into Replace field; clicking Tab one more time brings the cursor back into Transclusion box. 
+
+The same issue is with Citation.",1418935912,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-woqxqv6iluugikztqpwo,task_description,resolved
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,It seems that I fixed this in 2015 with this change to use natural tab order: <https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/243527>.,1611951130,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-woqxqv6iluugikztqpwo,task_subcomment,NA
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,"Or maybe listen for events to make sure things focus in the order I wanted, or something",1420046868,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-woqxqv6iluugikztqpwo,task_subcomment,NA
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,"So we could work out the current highest tabindex in the page and then add it to all our tabindexes in the template dialog. Which is horrible.
+
+Or I wonder if we should really just have the info button next to the parameter name and the remove button immediately following the value field, or something. Then the actual order of the elements might be logical and we could remove the tabindexes.",1419900981,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-woqxqv6iluugikztqpwo,task_subcomment,NA
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,The find and replace dialog also sets tabindexes... Guess the transclusion dialog is setting the same indexes.,1419509992,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-woqxqv6iluugikztqpwo,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","In our quest to convert the whole cluster to trusty and HHVM, we've got to the imagescalers.
+
+From what I can see from puppet/the current image scalers is that we have the following packages custom-built at the moment:
+
+  - ffmpeg2theora (disabled libav multithreading)
+  - librsvg (external resources loading protection)
+  - libvips31 (backport)
+  - libvpx1 (backport)
+
+We also need to evaluate the performance of HHVM under the peculiar imagescalers load, which is probably going to be non-optimal.
+
+Finally, testing should be very accurate to assess any rendering differences on trusty vs precise.",1418890706,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_description,resolved
+"Convert eqiad imagescalers to HHVM, Trusty","Just for cross-reference, a regression was found with rsvg - svgs > 10 MB (there's about 9000 such files) don't render. We'd need to upgrade to a later version of rsvg to fix, see T111815",1442126072,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227967 merged by Giuseppe Lavagetto:
+imagescalers: convert the last two servers to HAT
+
+[[https://gerrit.wikimedia.org/r/227967]]",1438686339,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227967 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescalers: convert the last two servers to HAT
+
+[[https://gerrit.wikimedia.org/r/227967]]
+",1438252852,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227676 merged by jenkins-bot:
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227676]]",1438186253,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227733 merged by jenkins-bot:
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227733]]",1438186235,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227732 merged by jenkins-bot:
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227732]]",1438186180,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227733 had a related patch set uploaded (by BryanDavis):
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227733]]
+",1438184069,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227732 had a related patch set uploaded (by BryanDavis):
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227732]]
+",1438184036,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227676 had a related patch set uploaded (by Giuseppe Lavagetto):
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227676]]
+",1438164978,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","I think I found what is the latest gotcha with imagescalers:
+
+```
+curl -H 'X-Forwarded-Proto: https' -H 'Host: commons.wikimedia.org' 'http://mw1152/w/thumb_handler.php/7/75/John_Bauer-Tyr_and_Fenrir.jpg/180px-John_Bauer-Tyr_and_Fenrir.jpg' -v
+* About to connect() to mw1152 port 80 (#0)
+*   Trying 10.64.16.132... connected
+> GET /w/thumb_handler.php/7/75/John_Bauer-Tyr_and_Fenrir.jpg/180px-John_Bauer-Tyr_and_Fenrir.jpg HTTP/1.1
+> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
+> Accept: */*
+> X-Forwarded-Proto: https
+> Host: commons.wikimedia.org
+> 
+< HTTP/1.1 302 Found
+< Date: Wed, 29 Jul 2015 09:56:29 GMT
+< Server: Apache
+< X-Powered-By: HHVM/3.6.1
+< X-Content-Type-Options: nosniff
+< Cache-control: no-cache
+< Expires: Wed, 29 Jul 2015 21:56:29 GMT
+< Vary: X-Forwarded-Proto
+< Location: https://upload.wikimedia.org/wikipedia/commons/thumb/1/18/Tyr_and_Fenrir-John_Bauer.jpg/180px-Tyr_and_Fenrir-John_Bauer.jpg
+< Transfer-Encoding: chunked
+< Content-Type: text/html; charset=utf-8
+```
+
+while on non-HHVM ones
+```
+curl -H 'X-Forwarded-Proto: https' -H 'Host: commons.wikimedia.org' 'http://mw1159/w/thumb_handler.php/7/75/John_Bauer-Tyr_and_Fenrir.jpg/180px-John_Bauer-Tyr_and_Fenrir.jpg' -v
+* About to connect() to mw1159 port 80 (#0)
+*   Trying 10.64.16.139... connected
+> GET /w/thumb_handler.php/7/75/John_Bauer-Tyr_and_Fenrir.jpg/180px-John_Bauer-Tyr_and_Fenrir.jpg HTTP/1.1
+> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
+> Accept: */*
+> X-Forwarded-Proto: https
+> Host: commons.wikimedia.org
+> 
+< HTTP/1.1 302 Found
+< Date: Wed, 29 Jul 2015 09:58:24 GMT
+< Server: Apache
+< X-Content-Type-Options: nosniff
+< Cache-control: no-cache
+< Location: https://upload.wikimedia.org/wikipedia/commons/thumb/1/18/Tyr_and_Fenrir-John_Bauer.jpg/180px-Tyr_and_Fenrir-John_Bauer.jpg
+< Expires: Wed, 29 Jul 2015 21:58:24 GMT
+< Vary: X-Forwarded-Proto
+< Content-Length: 0
+< Content-Type: text/html
+< 
+```
+
+In this case we have the same problem we had with 404s: thumb.php doesn't set the content-length, which makes apache assume the transfer-encoding is chunked, which for a 0 sized body makes varnish barf.",1438163989,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227160 merged by Ori.livneh:
+Re-introduce ProxyPass rule for thumb_handler.php, with corrected docroots
+
+[[https://gerrit.wikimedia.org/r/227160]]",1437952373,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227160 had a related patch set uploaded (by Ori.livneh):
+Re-introduce ProxyPass rule for thumb_handler.php, with corrected docroots
+
+[[https://gerrit.wikimedia.org/r/227160]]
+",1437946163,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 226738 merged by Ori.livneh:
+Follow-up for Ie17cb06: add thumb_handler.php ProxyPass rule to all vhosts
+
+[[https://gerrit.wikimedia.org/r/226738]]",1437756519,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 226738 had a related patch set uploaded (by Ori.livneh):
+Follow-up for Ie17cb06: add thumb_handler.php ProxyPass rule to all vhosts
+
+[[https://gerrit.wikimedia.org/r/226738]]
+",1437756390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 226658 merged by Ori.livneh:
+Add ProxyPass rule for thumb_handler.php
+
+[[https://gerrit.wikimedia.org/r/226658]]",1437697040,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 226658 had a related patch set uploaded (by Ori.livneh):
+Add ProxyPass rule for thumb_handler.php
+
+[[https://gerrit.wikimedia.org/r/226658]]
+",1437696974,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1473663, @Krenair wrote:
+> ```2015-07-23 00:06:38 mw1153 commonswiki exception ERROR: [d68c4bb1] /w/thumb_handler.php/2/2e/Mirage_III_A_01_Mus%0Aee_du_Bourget_P1020118.JPG/424px-%0AMirage_III_A_01_Musee_du_Bourget_P1020118.JPG   MWException from line 171 of /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php: CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. {""exception"":""[object] (MWException(code: 0): CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. at /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php:171)""}```
+> Seen from mw115[2-8]
+
+See {T106743}",1437692346,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1473663, @Krenair wrote:
+> ```2015-07-23 00:06:38 mw1153 commonswiki exception ERROR: [d68c4bb1] /w/thumb_handler.php/2/2e/Mirage_III_A_01_Mus%0Aee_du_Bourget_P1020118.JPG/424px-%0AMirage_III_A_01_Musee_du_Bourget_P1020118.JPG   MWException from line 171 of /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php: CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. {""exception"":""[object] (MWException(code: 0): CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. at /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php:171)""}```
+> Seen from mw115[2-8]
+
+Ummm, why/how do we have HHVM boxes without APC enabled?",1437692170,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","```2015-07-23 00:06:38 mw1153 commonswiki exception ERROR: [d68c4bb1] /w/thumb_handler.php/2/2e/Mirage_III_A_01_Mus%0Aee_du_Bourget_P1020118.JPG/424px-%0AMirage_III_A_01_Musee_du_Bourget_P1020118.JPG   MWException from line 171 of /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php: CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. {""exception"":""[object] (MWException(code: 0): CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. at /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php:171)""}```
+Seen from mw115[2-8]",1437610749,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","New imagescalers fun found today: 
+
+an high level of 5xx were going on today, so I intercepted a few urls that were returning a 503 - for example, I requested
+
+https://upload.wikimedia.org/wikipedia/commons/thumb/0/01/Casquette-IMG_0922.jpg/600px-Casquette-IMG_0922.jpg
+
+from my browser and got a 503:
+
+```
+...
+If you report this error to the Wikimedia System Administrators, please include the details below.
+Request: GET http://upload.wikimedia.org/wikipedia/commons/thumb/0/01/Casquette-IMG_0922.jpg/600px-Casquette-IMG_0922.jpg, from 10.64.32.81 via cp1048 cp1048 ([10.64.32.100]:3128), Varnish XID 3696382267
+Forwarded for: 79.58.168.196, 10.64.32.81, 10.64.32.81
+Error: 503, Service Unavailable at Wed, 22 Jul 2015 16:21:18 GMT
+```
+
+while if I do a plain curl I get the correct behaviour, a 302:
+
+```
+curl -I https://upload.wikimedia.org/wikipedia/commons/thumb/0/01/Casquette-IMG_0922.jpg/600px-Casquette-IMG_0922.jpg
+HTTP/1.1 302 Found
+Server: nginx/1.9.3
+Date: Wed, 22 Jul 2015 16:30:29 GMT
+Content-Type: text/html
+Content-Length: 0
+Connection: keep-alive
+X-Content-Type-Options: nosniff
+Expires: Thu, 23 Jul 2015 04:22:53 GMT
+Vary: X-Forwarded-Proto
+Location: https://upload.wikimedia.org/wikipedia/commons/thumb/9/99/Casquette_d%27administrateur_colonial_-IMG_0922.jpg/600px-Casquette_d%27administrateur_colonial_-IMG_0922.jpg
+Cache-Control: no-cache
+```
+
+So I tought this could have to do with compression. But subsequent requests were successful from the browser as well, so no idea what is going on here - maybe one imagescaler doing something wrong?
+
+",1437582881,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1466863, @Joe wrote:
+> FTR, I am going to depool all remaining Zend imagescaler today to test any outstanding problems with those. If none arise, I'm going to upgrade the last three tomorrow.
+
+Great. Sounds like a good plan. Thanks for pushing forward.",1437498908,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","FTR, I am going to depool all remaining Zend imagescaler today to test any outstanding problems with those. If none arise, I'm going to upgrade the last three tomorrow.",1437486922,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 225285 merged by Giuseppe Lavagetto:
+imagescalers: re-image mw115[6-8] to trusty, HHVM
+
+[[https://gerrit.wikimedia.org/r/225285]]",1437114439,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 225285 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescalers: re-image mw115[6-8] to trusty, HHVM
+
+[[https://gerrit.wikimedia.org/r/225285]]
+",1437114386,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 224594 merged by Giuseppe Lavagetto:
+imagescalers: reimage mw1154, mw1155 to HAT
+
+[[https://gerrit.wikimedia.org/r/224594]]",1436868273,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 224594 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescalers: reimage mw1154, mw1155 to HAT
+
+[[https://gerrit.wikimedia.org/r/224594]]
+",1436867484,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 223331 merged by Giuseppe Lavagetto:
+imagescalers: reimage mw1153 with HAT
+
+[[https://gerrit.wikimedia.org/r/223331]]",1436347245,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 223331 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescalers: reimage mw1153 with HAT
+
+[[https://gerrit.wikimedia.org/r/223331]]
+",1436284180,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","(codfw imagescalers are all HHVM+Trusty already, so we're just left with mw1153-1160)",1435969942,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","For the past several weeks, this task was blocked on the fact that the HHVM renderer (mw1152) would cause 5xx spikes whenever it was pooled. The issue appears to have been a corruption in the cached byte-code for `/w/404.php` which caused Varnish to be unable to parse 404 responses generated by HHVM on mw1152. These responses were transformed by varnish into 503s. Touching the file fixed it.
+
+The remaining task is to re-image the other scalers.",1435968941,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Bah, edit conflicts.",1435619612,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Since the latest test I did after ori found we needed that file was unsuccessful, and I have zero time to work on this at the moment, I'll release this ticket so that somebody else can grab it.
+
+As matanya clearly stated ""We've been waiting forever for this"".",1433252548,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 213228 merged by Ori.livneh:
+mediawiki: Touch /etc/wikimedia-image-scaler on image scalers
+
+[[https://gerrit.wikimedia.org/r/213228]]",1432463202,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 213228 had a related patch set uploaded (by Ori.livneh):
+mediawiki: Touch /etc/wikimedia-image-scaler on image scalers
+
+[[https://gerrit.wikimedia.org/r/213228]]
+",1432463124,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1306421, @greg wrote:
+> What ya'll think now? :)
+
+We should probably not schedule this until we resolve the issue Giuseppe spotted in T84842#1265055.",1432462003,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","```
+greg moved this task to This week: May 4-8 on the Roadmap workboard.
+greg moved this task to This week: May 11-15 on the Roadmap workboard.
+greg moved this task to May 18-22 on the Roadmap workboard.
+
+```
+
+What ya'll think now? :)",1432460828,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Ok so, after a lot of battles with HHVM 3.6.1, the mysterious 503s on the imagescalers continued.
+
+One possible cause is the fact that apparently some images require more memory to be converted on trusty:
+```
+curl -H 'Host: commons.wikimedia.org' 'http://mw1152/w/thumb_handler.php/1/17/HawkridgeBarton_Chittlehampton_NorthDevon.PNG/1000px-HawkridgeBarton_Chittlehampton_NorthDevon.PNG' -I
+HTTP/1.1 500 Internal server error
+Date: Wed, 06 May 2015 15:13:17 GMT
+Server: Apache
+X-Powered-By: HHVM/3.6.1
+X-Content-Type-Options: nosniff
+Cache-control: no-cache
+X-MW-Thumbnail-Renderer: mw1152
+Connection: close
+Content-Type: text/html; charset=utf-8
+```
+
+which results in the kernel recording
+
+```
+May  6 15:13:20 mw1152 kernel: [4775538.759268] memory: usage 307200kB, limit 307200kB, failcnt 50
+May  6 15:13:20 mw1152 kernel: [4775538.759269] memory+swap: usage 0kB, limit 18014398509481983kB, failcnt 0
+May  6 15:13:20 mw1152 kernel: [4775538.759270] kmem: usage 0kB, limit 18014398509481983kB, failcnt 0
+May  6 15:13:20 mw1152 kernel: [4775538.759271] Memory cgroup stats for /mediawiki/job/15592: cache:0KB rss:307200KB rss_huge:202752KB mapped_file:0KB writeback:0KB inactive_anon:0KB active_anon:307132KB inactive_file:0KB active_file:0KB unevictable:0KB
+May  6 15:13:20 mw1152 kernel: [4775538.759282] [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
+May  6 15:13:20 mw1152 kernel: [4775538.759334] [15592]    33 15592     5222      426      16        0             0 bash
+May  6 15:13:20 mw1152 kernel: [4775538.759336] [15594]    33 15594     2867      167      11        0             0 timeout
+May  6 15:13:20 mw1152 kernel: [4775538.759337] [15595]    33 15595    93743    77414     186        0             0 convert
+May  6 15:13:20 mw1152 kernel: [4775538.759339] Memory cgroup out of memory: Kill process 15595 (convert) score 1010 or sacrifice child
+May  6 15:13:20 mw1152 kernel: [4775538.768545] Killed process 15595 (convert) total-vm:374972kB, anon-rss:307004kB, file-rss:2652kB
+May  6 15:15:01 mw1152 CRON[15698]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
+```
+
+Also, I tested that at smaller resulting sizes this doesn't cause the 500 to be emitted.
+
+This is the mediawiki error log: P612
+
+I'm still unsure this is really the cause of the larger number of 503s I see.
+",1430925671,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Ok so, after a lot of battles with HHVM 3.6.1, the mysterious 503s on the imagescalers continued.
+
+One possible cause is the fact that apparently some images require more memory to be converted on trusty:
+```
+curl -H 'Host: commons.wikimedia.org' 'http://mw1152/w/thumb_handler.php/1/17/HawkridgeBarton_Chittlehampton_NorthDevon.PNG/1000px-HawkridgeBarton_Chittlehampton_NorthDevon.PNG' -I
+HTTP/1.1 500 Internal server error
+Date: Wed, 06 May 2015 15:13:17 GMT
+Server: Apache
+X-Powered-By: HHVM/3.6.1
+X-Content-Type-Options: nosniff
+Cache-control: no-cache
+X-MW-Thumbnail-Renderer: mw1152
+Connection: close
+Content-Type: text/html; charset=utf-8
+```
+
+which results in the kernel recording
+
+```
+May  6 15:13:20 mw1152 kernel: [4775538.759268] memory: usage 307200kB, limit 307200kB, failcnt 50
+May  6 15:13:20 mw1152 kernel: [4775538.759269] memory+swap: usage 0kB, limit 18014398509481983kB, failcnt 0
+May  6 15:13:20 mw1152 kernel: [4775538.759270] kmem: usage 0kB, limit 18014398509481983kB, failcnt 0
+May  6 15:13:20 mw1152 kernel: [4775538.759271] Memory cgroup stats for /mediawiki/job/15592: cache:0KB rss:307200KB rss_huge:202752KB mapped_file:0KB writeback:0KB inactive_anon:0KB active_anon:307132KB inactive_file:0KB active_file:0KB unevictable:0KB
+May  6 15:13:20 mw1152 kernel: [4775538.759282] [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
+May  6 15:13:20 mw1152 kernel: [4775538.759334] [15592]    33 15592     5222      426      16        0             0 bash
+May  6 15:13:20 mw1152 kernel: [4775538.759336] [15594]    33 15594     2867      167      11        0             0 timeout
+May  6 15:13:20 mw1152 kernel: [4775538.759337] [15595]    33 15595    93743    77414     186        0             0 convert
+May  6 15:13:20 mw1152 kernel: [4775538.759339] Memory cgroup out of memory: Kill process 15595 (convert) score 1010 or sacrifice child
+May  6 15:13:20 mw1152 kernel: [4775538.768545] Killed process 15595 (convert) total-vm:374972kB, anon-rss:307004kB, file-rss:2652kB
+May  6 15:15:01 mw1152 CRON[15698]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
+```
+
+Also, I tested that at smaller resulting sizes this doesn't cause the 500 to be emitted.
+
+This is the mediawiki error log: P612
+
+I'm still unsure this is really the cause of the larger 503s I see.
+",1430925624,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","OK, let's schedule to a specific week once we have confidence on the ETA.",1428004554,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1175265, @Eloquence wrote:
+> @Joe, do we need to push this to next week?
+
+At minimum. Giuseppe ran into segfaults with Tim's output buffer patch and that's blocking the rollout of a new package, which the scalers need.",1428004454,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Joe, do we need to push this to next week?",1428004192,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 196173 merged by Giuseppe Lavagetto:
+mediawiki: install fonts metric-compatible with Calibri and Cambria
+
+[[https://gerrit.wikimedia.org/r/196173]]",1427696479,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","This was scheduled for March, is this happening next week or should we bump it to April?",1426819491,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","The HHVM upstream bug tracked in {T91468} should block this rollout. See analysis in T89918#1052318 for full gory details, but the TL;DR is that HHVM's async i/o and fcgi bridge interact in such a way that a slow consumer and a fast producer can OOM the HHVM process resulting in a 503 from Apache.",1426268546,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1112319, @Joe wrote:
+> @brion problem confirmed, but this would be relevant for the videoscalers, right?
+
+ah good if video scalers are a separate config then please regard my comment as belonging to them and ignore it here :D",1426183149,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","ok, then it was probably a false positive. I'm a bit in the dark about what is timing out here then, will need to investigate further",1426162058,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","What happens with those requests is that the web server queries the image scalers internally to have them scale an image which isn't public yet.
+
+What I don't know yet, and am trying to figure out in that bug, is if any error happens at the image scalers' level, or if it's a timeout happening higher in the chain (in varnish, for example). My main theory is that the image scaler is taking too long to generate the requested thumbnail and *something* times out in the chain, causing a nasty 503 instead of the cleaner error that should happen if the curl request to the image scalers hit the timeout setting.",1426161732,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",Special:UploadStash has a known 503 issue happening at the moment: T90599,1426161590,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","I re-pooled the HHVM imagescaler and got confirmation that SVG files rendered correctly.
+
+However, I was still seeing a significant amount of 503s, but nothing stood out in any log apart from a few occurrencies of errors in Special:UploadStash, like e.g.
+```
+http://commons.wikimedia.org/wiki/Special:UploadStash/thumb/13091utfih7k.ab6yzc.1488278.jpg/71px-13091utfih7k.ab6yzc.1488278.jpg
+```
+
+but this is just a shot in the dark, as those are probably handled by the general appserver pool. I will have to ask someone with expertise on UploadWizard to confirm how the thumb request is performed in this case.",1426159486,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 196186 merged by jenkins-bot:
+imagescaling: remove legacy option for HHVM imagescalers
+
+[[https://gerrit.wikimedia.org/r/196186]]",1426156122,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 196186 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescaling: remove legacy option for HHVM imagescalers
+
+[[https://gerrit.wikimedia.org/r/196186]]
+",1426155115,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","If the new rsvg version doesn't need a specific option turned on to avoid external resources, then it's just a matter of having a slightly different mediawiki configuration for the hhvm image scaler.
+
+Set wgSVGConverter to 'rsvg-broken' for it instead of the default 'rsvg-secure'.
+
+Relevant code is in:
+mediawiki-config/wmf-config/CommonSettings.php
+mediawiki-config/wmf-config/InitialiseSettings.php",1426153770,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Gilles I imagined that - given our svg code now supports the security model in the more modern rsvg versions I guessed it would work automagically. It is not the case, I am still looking at the code to be sure of what's wrong here.",1426152998,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",--no-external-files is an option that was coming from our custom patches to librsvg,1426152382,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","I had to depool the server, as quite a lot of unexpected errors were spawning.
+
+E.G. when rescaling http://commons.wikimedia.org/w/thumb_handler.php/c/ca/Alarilla_Guadalajara_-_Mapa_municipal.svg/39px-Alarilla_Guadalajara_-_Mapa_municipal.svg.png I got the following error
+
+```
+<!DOCTYPE html>
+<html><head>
+<meta charset=""UTF-8"" />
+<title>Error generating thumbnail</title>
+</head>
+<body>
+<h1>Error generating thumbnail</h1>
+<p>
+Error creating thumbnail: Unknown option --no-external-files<br />
+
+</p>
+<!-- /w/thumb_handler.php/c/ca/Alarilla_Guadalajara_-_Mapa_municipal.svg/39px-Alarilla_Guadalajara_-_Mapa_municipal.svg.png -->
+<!-- mw1152 -->
+
+</body>
+</html>
+```
+
+Probably the imagescaling code needs to be corrected? I'll look at rsvg options later today",1426151938,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@brion problem confirmed, but this would be relevant for the videoscalers, right?",1426150660,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",The imagescaler is now into rotation.,1426150632,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 196173 had a related patch set uploaded (by Giuseppe Lavagetto):
+mediawiki: install fonts metric-compatible with Calibri and Cambria
+
+[[https://gerrit.wikimedia.org/r/196173]]
+",1426149856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","May you add some additional fonts, e.g. [[https://wiki.debian.org/SubstitutingCalibriAndCambriaFonts|Caladea and Carlito]] for easier SVG rendering?
+
+See also https://commons.wikimedia.org/wiki/File:MediaWiki_SVG_fonts.svg",1426148245,PHID-USER-mpi3m7v2orbtizvqa43q,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",Announcement made https://commons.wikimedia.org/wiki/Commons:Village_pump#Upgrade_of_image_rendering_servers ( permalink: https://commons.wikimedia.org/w/index.php?title=Commons:Village_pump&oldid=152736923#Upgrade_of_image_rendering_servers ),1426016825,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Joe here's a test case for the webm->ogv ffmpeg2theora conversion:
+
+```
+wget https://upload.wikimedia.org/wikipedia/commons/c/c8/Sneak_Preview_-_Wikipedia_VisualEditor.webm
+
+ffmpeg2theora \
+  --width 640 --height 360 -V 512 -a 1 -H 44100 -c 2 --no-upscaling --keyint 128 --buf-delay 256 \
+  -o Sneak_Preview_-_Wikipedia_VisualEditor.360p.ogv \
+  Sneak_Preview_-_Wikipedia_VisualEditor.webm
+```
+
+Lots of errors about audio format during conversion, then the resulting .ogv is unplayable.
+",1425932726,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Bawolff none of the new links you posted presented any issue. I think we can move on and put at least one machine in rotation by thursday 10 AM UTC; are you able to make the announcement on Commons:VP about it?
+
+@brion: if you have a good example I'll test it.",1425915948,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",Another thing to test: .ogg / .ogv transcoding output (from .webm or opus source). I've had some troubles with ffmpeg2theora on Trusty (though the note above about multithreading disabled might have resolved that?),1425669302,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Some other GIF files since that's where we ran into problems (These are from the most popular list, most will be really small cases that don't stress the server, so I expect they will render fine):
+
+* https://upload.wikimedia.org/wikipedia/commons/thumb/2/26/Mug_and_Torus_morph.gif/120px-Mug_and_Torus_morph.gif
+* https://upload.wikimedia.org/wikipedia/commons/thumb/8/86/Qxz-ad137.gif/320px-Qxz-ad137.gif
+* https://upload.wikimedia.org/wikipedia/commons/thumb/1/19/Second_world_war_europe_animation_small.gif/215px-Second_world_war_europe_animation_small.gif
+* https://upload.wikimedia.org/wikipedia/commons/thumb/8/81/ADN_animation.gif/100px-ADN_animation.gif
+* https://upload.wikimedia.org/wikipedia/commons/thumb/9/9b/Lang-fr.gif/220px-Lang-fr.gif",1425659471,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Animated gifs have always been memory intensive. File:Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif was already on the edge of what was running out of memory in the old config. I guess the newer image magick uses a bit more memory to push it over the edge.
+
+If a memory limit is set by ulimit (or via a command line option to image magick), image magick will try to trade memory usage for time, which could be a solution to this issue.
+
+For VP9: The default libvpx on trusty should be new enough, but the default libav is too old. Needs at least libav10
+
+-----
+
+Some other things that might possibly be fixed on trusty (Not sure, either way not a regression):
+
+* https://upload.wikimedia.org/wikipedia/commons/thumb/1/18/Zentralbibliothek_Solothurn_S_I_498_Kosciuszko_Inventarium_02.tif/lossy-page1-800px-Zentralbibliothek_Solothurn_S_I_498_Kosciuszko_Inventarium_02.tif.jpg is purple currently. Rumour is that this may be fixed on newer image magick, but I haven't tested.
+* 16 bit tiff files don't render on vips. I've heard this is fixed on newer vips, but I'm not sure at what point. example https://upload.wikimedia.org/wikipedia/commons/thumb/a/a9/Amelia_earhart_received_by_president_coolidge.tif/lossy-page1-464px-Amelia_earhart_received_by_president_coolidge.tif.jpg (This issue is possible to work around on MW side if the upgrade doesn't fix it)
+",1425656260,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","animated gif conversion seems to take a lot of memory
+
+
+```
+[4844824.480807] convert invoked oom-killer: gfp_mask=0xd0, order=0, oom_score_adj=0
+[4844824.480813] convert cpuset=/ mems_allowed=0-1
+[4844824.480816] CPU: 0 PID: 4631 Comm: convert Not tainted 3.13.0-24-generic #47-Ubuntu
+[4844824.480817] Hardware name: Dell Inc. PowerEdge R410/01V648, BIOS 1.5.3 10/22/2010
+[4844824.480819]  ffff88009c842c00 ffff8801a4eebc48 ffffffff81715ac4 ffff880070972fe0
+[4844824.480823]  ffff8801a4eebcd0 ffffffff817103ff 0000000000000246 ffff88009c842c00
+[4844824.480826]  ffff8801a4eebc90 ffff8801a4eebca0 ffffffff81151587 0000000000000001
+[4844824.480829] Call Trace:
+[4844824.480838]  [<ffffffff81715ac4>] dump_stack+0x45/0x56
+[4844824.480843]  [<ffffffff817103ff>] dump_header+0x7f/0x1f1
+[4844824.480848]  [<ffffffff81151587>] ? find_lock_task_mm+0x27/0x70
+[4844824.480850]  [<ffffffff8115197e>] oom_kill_process+0x1ce/0x330
+[4844824.480854]  [<ffffffff812d0135>] ? security_capable_noaudit+0x15/0x20
+[4844824.480860]  [<ffffffff811b184c>] mem_cgroup_oom_synchronize+0x4fc/0x540
+[4844824.480862]  [<ffffffff811b0da0>] ? mem_cgroup_charge_common+0xa0/0xa0
+[4844824.480864]  [<ffffffff81152104>] pagefault_out_of_memory+0x14/0x80
+[4844824.480866]  [<ffffffff8170ea48>] mm_fault_error+0x8e/0x180
+[4844824.480869]  [<ffffffff81721d41>] __do_page_fault+0x4a1/0x560
+[4844824.480875]  [<ffffffff811112fc>] ? acct_account_cputime+0x1c/0x20
+[4844824.480879]  [<ffffffff8109d76b>] ? account_user_time+0x8b/0xa0
+[4844824.480880]  [<ffffffff8109dd84>] ? vtime_account_user+0x54/0x60
+[4844824.480882]  [<ffffffff81721e1a>] do_page_fault+0x1a/0x70
+[4844824.480886]  [<ffffffff8171e288>] page_fault+0x28/0x30
+[4844824.480889] Task in /mediawiki/job/4628 killed as a result of limit of /mediawiki/job/4628
+[4844824.480891] memory: usage 307200kB, limit 307200kB, failcnt 54
+[4844824.480892] memory+swap: usage 0kB, limit 18014398509481983kB, failcnt 0
+[4844824.480893] kmem: usage 0kB, limit 18014398509481983kB, failcnt 0
+[4844824.480894] Memory cgroup stats for /mediawiki/job/4628: cache:16KB rss:307184KB rss_huge:145408KB mapped_file:12KB writeback:0KB inactive_anon:0KB active_anon:307160KB inactive_file:0KB active_file:0KB unevictable:0KB
+[4844824.480907] [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
+[4844824.480948] [ 4628]    33  4628     5223      427      15        0             0 bash
+[4844824.480950] [ 4630]    33  4630     2868      168      11        0             0 timeout
+[4844824.480952] [ 4631]    33  4631    94085    77321     185        0             0 convert
+[4844824.480953] Memory cgroup out of memory: Kill process 4631 (convert) score 1009 or sacrifice child
+[4844824.490074] Killed process 4631 (convert) total-vm:376340kB, anon-rss:306800kB, file-rss:2484kB
+```",1425644502,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","So I'd have to debug the animated gif problem, and after that I guess we can throw the new imagescaler in the ring as soon as this is resolved.",1425643709,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","I found no other regressions, and - good news! - https://upload.wikimedia.org/wikipedia/commons/thumb/3/3b/WorldAviation.198409.BackCover.pdf/page1-342px-WorldAviation.198409.BackCover.pdf.jpg gets rendered by the new imagescaler. So does https://upload.wikimedia.org/wikipedia/commons/thumb/7/70/John_Stuart_Mill%2C_Considerations_on_Representative_Government_%281st_ed%2C_1861%29.pdf/page1-382px-John_Stuart_Mill%2C_Considerations_on_Representative_Government_%281st_ed%2C_1861%29.pdf.jpg",1425643534,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","the animated gif test throws an error on the HHVM imagescaler:
+
+  <!DOCTYPE html>
+  <html><head>
+  <meta charset=""UTF-8"" />
+  <title>Error generating thumbnail</title>
+  </head>
+  <body>
+  <h1>Error generating thumbnail</h1>
+  <p>
+  Error creating thumbnail: /srv/mediawiki/php-1.25wmf19/includes/limit.sh: line 101: 30955 Killed                  /usr/bin/timeout $MW_WALL_CLOCK_LIMIT /bin/bash -c &quot;$1&quot; 3&gt;&amp;-<br />
+  <br />
+  Error code: 137
+  </p>
+  <!-- /w/thumb_handler.php/5/5d/Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif/850px-Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif -->
+  <!-- mw1152 -->
+
+  </body>
+  </html>
+
+I am still unsure of the reason, I'll investigate this further.",1425642012,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Ok, first bad news: 
+
+the VP9 encoding still doesn't work, but it may just need some additional codecs to be installed. At least this is not a regression :)",1425635091,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Bawolff first of all, thanks for the list of urls to test, this is a great starting point.
+Then, I apologize for lagging behind on this, but I have been busy with other priorities after the dev summit, but since this is blocking other tasks, I'll try to get back to this as soon as possible.
+
+I'll plan a migration schedule next week, so that we can also make an announcement.
+
+",1425128064,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",Ping on this?,1424972464,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","A random assortment of images to test that covers a wide variety of formats we use (Just going to give thumbnail urls, hope that's good):
+
+* Super large tiff file: https://upload.wikimedia.org/wikipedia/commons/thumb/3/39/Zentralbibliothek_Z%C3%BCrich_-_Mittelalterliche_Stadt_-_000005203.tif/lossy-page1-1024px-Zentralbibliothek_Z%C3%BCrich_-_Mittelalterliche_Stadt_-_000005203.tif.jpg
+* Small tiff file: https://upload.wikimedia.org/wikipedia/commons/thumb/8/89/%2215th_or_16th_century_Benin_king%22_-_NARA_-_558985.tif/lossy-page1-179px-%2215th_or_16th_century_Benin_king%22_-_NARA_-_558985.tif.jpg
+* large PNG file https://commons.wikimedia.org/wiki/File:Arab_West_Midlands_2011_census.png
+* large full colour png file https://upload.wikimedia.org/wikipedia/commons/thumb/d/d0/Welland_cafe_inside_02.png/450px-Welland_cafe_inside_02.png
+* small png https://upload.wikimedia.org/wikipedia/commons/thumb/9/98/P_sports.png/120px-P_sports.png
+* Thumbnail of VP8 webm file https://upload.wikimedia.org/wikipedia/commons/thumb/d/d3/%27Trick_or_Treat%27_-_Kinetic_Typography.webm/540px--%27Trick_or_Treat%27_-_Kinetic_Typography.webm.jpg
+* VP9 thumbnail: https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/VP9test.webm/512px--VP9test.webm.jpg (This doesn't work on old image scalars, I hope it works on the new one).
+* ogg thumbnail: https://upload.wikimedia.org/wikipedia/commons/thumb/7/75/Reflex-Control-of-Robotic-Gait-Using-Human-Walking-Data-pone.0109959.s016.ogv/300px--Reflex-Control-of-Robotic-Gait-Using-Human-Walking-Data-pone.0109959.s016.ogv.jpg
+* xcf file https://upload.wikimedia.org/wikipedia/commons/thumb/9/90/%22What_a_Brilliant_Idea!%22_Barnstar.xcf/111px-%22What_a_Brilliant_Idea!%22_Barnstar.xcf.png (Note, newer image magick has fixed a bunch of xcf bugs, this file may render differently but ""better"" on the new version)
+* Random djvu image thrown in for good measure: https://upload.wikimedia.org/wikipedia/commons/thumb/3/3b/%27A_morte.djvu/page11-398px-%27A_morte.djvu.jpg
+* PDF that is landscape oriented https://upload.wikimedia.org/wikipedia/commons/thumb/b/b0/GA20891.pdf/page1-800px-GA20891.pdf.jpg (make sure that dimensions are right)
+* Animated GIF https://upload.wikimedia.org/wikipedia/commons/thumb/5/5d/Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif/800px-Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif
+* SVG lang option - make sure https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/SystemLanguage.svg/320px-SystemLanguage.svg.png says ""en"" and https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/SystemLanguage.svg/langfr-320px-SystemLanguage.svg.png says ""fr""
+* Do the svg fonts change significantly https://upload.wikimedia.org/wikipedia/commons/thumb/4/4e/Meta_SVG_fonts.svg/1024px-Meta_SVG_fonts.svg.png (or https://upload.wikimedia.org/wikipedia/commons/thumb/d/d8/MediaWiki_SVG_font_list.svg/920px-MediaWiki_SVG_font_list.svg.png but that would be a pita to compare)
+** SVGs is probably the place that's most likely to get a regression, but unfortunately I don't really know enough to give specific svg features to test.
+
+Some other things that probably won't work, but worth testing on the off chance the update fixes the issue:
+
+* https://upload.wikimedia.org/wikipedia/commons/thumb/3/3b/WorldAviation.198409.BackCover.pdf/page1-342px-WorldAviation.198409.BackCover.pdf.jpg (Currently doesn't work because it takes way to long to render, just curious if that changes with the new server)
+* https://upload.wikimedia.org/wikipedia/commons/thumb/7/70/John_Stuart_Mill%2C_Considerations_on_Representative_Government_%281st_ed%2C_1861%29.pdf/page1-382px-John_Stuart_Mill%2C_Considerations_on_Representative_Government_%281st_ed%2C_1861%29.pdf.jpg JPEG2000 chunks in pdf files. Didn't used to work, maybe upgrade fixed?
+
+-----
+When are you planning to put the new server in rotation? I'd like to make an announcement on Commons:VP before that happens so that users can be on the look out for any rendering changes.",1421251705,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","The first HAT imagescaler is reimaged, and basic testing shows it's working fine.
+
+I would need suggestions on how/what to test before taking it into rotation.",1421081714,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","ffmpeg2theora already includes the patch to disable libav threads in trusty, so we don't have any additional need to repackage things for trusty imagescalers.",1420797761,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Librsvg 2.40.2-1+wm1 is on apt.wikimedia.org and includes the patch at https://git.gnome.org/browse/librsvg/commit/?id=5ba4343bccc7e1765f38f87490b3d6a3a500fde1
+
+I'll look at ffmpeg2theora, then I'll repurpose mw1152 as the test HAT imagescaler",1420796912,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","The patch that @PleaseStand referenced cleanly applies on the librsvg package in trusty, so I'll rebuild it using it alone. I don't think we need a repository, the source package upload should be enough.
+",1420792801,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Thanks for the feedback.
+
+@Bawolff I guess ffmpeg2theora was there because the package lists are shared with the videoscalers.",1418918016,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","There's also a second patch to librsvg ([[https://gerrit.wikimedia.org/r/#/c/173639/|80dd6ad665610979]]), which fixes a parsing bug in the library. I think even trusty's version of librsvg is too old to already have the patch, which was only applied upstream last month.",1418901297,PHID-USER-3ampiwske4lc434cm6ot,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">ffmpeg2theora (disabled libav multithreading)
+
+(Unless I missed something) That's only used in the encoding process (on the video scalars), not during thumbnailing. So I don't think that's needed on image scalars. Additionally, I'm not entirely sure why we have multithreading disabled, but we do use 2 threads (since f1675415) when encoding webm videos with libav (on the video scalars), so the disabling of multithreading for theora videos might not be needed anymore. But I don't know the history behind that, so I may be wrong.",1418891954,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","This might be slightly off-topic, but... Video support on commons would be significantly improved with support of VP9 codec (T55863). In order for MediaWiki (as it currently stands) to make the static placeholder thumbnails for VP9 videos, it would need libav10 backported to the image scalars. So if it is possible to backport the newer version of libav while rebuilding the image scalars, that would be really cool.",1418891525,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","the newer librsvg supports a different security mechanism that should only load resources in the same directory. Given it seems to me that we're already processing SVG images in a dedicated temporary directory, this should be good enough without patching, but I'd like Tim to comment on this",1418890993,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","So, libvps31 and libvpx1 are both at newer versions on trusty and don't need backporting",1418890855,PHID-USER-fdo23otm6ztt674vjqko,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+Search text for inserting media should be selected on open,"On a page such as http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click Insert/Media
+
+Note that the default text in the search box is the title of the page. 
+
+Click inside the search box.
+
+Default text should disappear but does not. RETURN also does not remove the default text.
+
+Compare to the Link interface which looks similar but behaves correctly. 
+",1418848456,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p76q3pkvm3ujbswasdmd,task_description,resolved
+Search text for inserting media should be selected on open,Also seen in Chrome as of 23 January,1422038288,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p76q3pkvm3ujbswasdmd,task_subcomment,NA
+Search text for inserting media should be selected on open,"On closer examination, I believe that the default text in the media search box is briefly selected, but the selection disappears. Again, compare to Link which does the same thing correctly.
+
+Seen in Firefox. ",1418849300,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p76q3pkvm3ujbswasdmd,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"CSS via load.php sometimes takes as long as 10  seconds to be returned on my local instance.
+If I run
+> redis-cli
+> monitor
+
+I will notice that the log will considerably slow on lines which look like this:
+""GET"" ""wiki:resourceloader:filter:minify-css:7:ef038bf45ab521177624638cbeb85f3d""
+
+Anyone know why this might be happening?
+",1418775220,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_description,resolved
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"This hasn't been an issue for a while afaik.
+
+Related issues that contributed to this:
+* {T112035}
+* {T107377}
+* and more..",1470362201,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Removing the #resourceloader tag. I don't see an easy fix for this, and it does not make sense to optimize ResourceLoader for VirtualBox Shared Folders or NFS. ",1442613254,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 201616 merged by jenkins-bot:
+Allow use of cachefilesd to speed up file system operations
+
+[[https://gerrit.wikimedia.org/r/201616]]",1435623174,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 201616 restored by BryanDavis:
+Use cachefilesd to speed up file system operations
+
+[[https://gerrit.wikimedia.org/r/201616]]",1435251140,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 201616 abandoned by Ori.livneh:
+Use cachefilesd to speed up file system operations
+
+[[https://gerrit.wikimedia.org/r/201616]]",1434390630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 194217 abandoned by BryanDavis:
+Enable stat cache for HHVM fcgi container
+
+Reason:
+Makes things worse rather than better unfortunately.
+
+[[https://gerrit.wikimedia.org/r/194217]]",1428282440,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Relevant:
+* {7a46e84d69a3c912ba9e3c19c0943dba13026ae3}
+* {4ebdd607f5de4fbdf2cfba732452c4df239847c8}
+* {061904a913db144b1d81835b37896cec6a7e5e6d}
+* {3897868db104b88f70569a22613829031fa64f5c}",1448413416,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Relevant:
+* {7a46e84d69a3c912ba9e3c19c0943dba13026ae3}
+* {4ebdd607f5de4fbdf2cfba732452c4df239847c8}
+* {061904a913db144b1d81835b37896cec6a7e5e6d}
+* {3897868db104b88f70569a22613829031fa64f5c}",1428063298,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 201616 had a related patch set uploaded (by BryanDavis):
+Use cachefilesd to speed up file system operations
+
+[[https://gerrit.wikimedia.org/r/201616]]
+",1428018451,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,">>! In T78733#972401, @Jdlrobson wrote:
+> It seems to become an issue as soon as I install multiple wikis
+
+Do we have independent verification of this? It would be significant if true.
+
+",1427791072,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,">>! In T78733#1130869, @Yurik wrote:
+> i wonder if enabling ""zend"" role (switch back to PHP engine) would have solved it.
+
+I would also like to see if anyone has disabled NFS and seen an ongoing performance improvement.  I realize NFS was supposed to //improve// performance, but IIRC it was originally put in before HHVM, and both VirtualBox and our setup have changed since then.",1427346633,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"i wonder if enabling ""zend"" role (switch back to PHP engine) would have solved it.",1426726635,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"I did some debugging with legoktm and less seemed to be the issue. We'd need someone who knows #ResourceLoader inside out. Maybe @Catrope to get to the bottom of this.
+
+I've actually stopped using Vagrant now. It was becoming impractical but the URL I was using was:
+
+http://localhost:8080/w/load.php?debug=false&lang=en&modules=mediawiki.sectionAnchor%7Cmediawiki.ui.button%2Cicon%7Cmobile.pagelist.styles%7Cskins.minerva.beta.images%2Cstyles%7Cskins.minerva.chrome.styles%7Cskins.minerva.content.styles%7Cskins.minerva.drawers.styles%7Cskins.minerva.icons.images%2Cstyles%7Cskins.minerva.tablet.styles&only=styles&skin=minerva&target=mobile&*
+
+I had Flow, MobileFrontend, Apisandbox, Echo, Cite, ConfirmEdit, EventLogging, MultimediaViewer, PageImages roles installed.
+",1426720504,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"@Jdlrobson can you provide the URL of the request that's taking so long? I fear we're all working off the same symptom here (slowness) but not necessarily the same root cause (general NFS performance vs. less compilation, etc.). We need to single in on a particular request that can be consistently profiled. Providing your currently enabled roles would help as well (`vagrant roles list -e`).",1426537801,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Any way forward with this? Any idea of timeline to fix this? Anything I, a frontend engineer can do to help move this along?",1426530689,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Disabling tests made no difference for me @Legoktm
+This hook is only run in test mode anyhow so that didn't surprise me.
+I think the issue is here is purely lots of RL modules and thus files and thus lookup times.
+I'm going to be forced to move off Vagrant next week if this continues, this is very impacting my ability to get things done.
+",1426197873,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Some controlled tests verify that NFS + stat is a part of this performance issue, but maybe not the whole problem.
+
+First I created 5000 files in `vagrant/tmp/mtime` and dropped this into `/var/www/w/mtimes.php`:
+```
+<?php
+
+chdir('/vagrant/tmp/mtime');
+array_map('stat', scandir('.'));
+```
+
+I experimented with NFS [[ http://linux.die.net/man/5/nfs | mount options ]] dealing with the [[ http://docstore.mik.ua/orelly/networking_2ndEd/nfs/ch18_06.htm#nfs2-CHP-18-SECT-6.html | attribute cache ]] and requests to `mtimes.php`.
+
+Using the default options the performance is variable depending on how long you wait between requests. Quick subsequent requests can preempt the default file attribute cache timeout (which is between 3 and 30 seconds, `acregmin`/`acregmax`), while waiting longer results in uncached results. The first two requests below show that the PHP `stat` calls resulted in NFS `getattr` calls to the server, while the final request was made quickly enough that it preempted the cache expiration (no `getattr` calls).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   775067
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.750s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   780068
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m4.228s
+user	0m0.009s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785070
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.249s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785074
+```
+
+Using a fixed attribute cache timeout of 30 (`actimeo=30`) instead of the variable min/max, I was able to get the improved performance more reliably (after an initial warmup).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,acregmin=30,acregmax=30,acdirmax=30,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   790086
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.695s
+user	0m0.010s
+sys	0m0.009s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795087
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.240s
+user	0m0.008s
+sys	0m0.008s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795088
+```
+
+Anyway... upping the NFS attribute cache improves performance drastically in this controlled experiment (~ 90%). However, running the same experiment using the curl request that @Mattflaschen posted yields a lesser (but still significant) performance gain (~ 25%), and the overall request time is still an attrocious 4+ seconds for me.
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   804036
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m5.758s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805076
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m4.270s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805098
+```",1426107959,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Some controlled tests verify that NFS + stat is a part of this performance issue, but maybe not the whole problem.
+
+First I created 5000 files in `vagrant/tmp/mtime` and dropped this into `/var/www/w/mtimes.php`:
+```
+<?php
+
+chdir('/vagrant/tmp/mtime');
+array_map('stat', scandir('.'));
+```
+
+I experimented with NFS [[ http://linux.die.net/man/5/nfs | mount options ]] dealing with the [[ http://docstore.mik.ua/orelly/networking_2ndEd/nfs/ch18_06.htm#nfs2-CHP-18-SECT-6.html | attribute cache ]] and requests to `mtimes.php`.
+
+Using the default options the performance is variable depending on how long you wait between requests. Quick subsequent requests can preempt the default file attribute cache timeout (which is between 3 and 30 seconds, `acregmin`/`acregmax`), while waiting longer results in uncached results. The first two requests below show that the PHP `stat` calls resulted in NFS `getattr` calls to the server, while the final request was made quickly enough that it preempted the cache expiration (no `getattr` calls).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   775067
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.750s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   780068
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m4.228s
+user	0m0.009s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785070
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.249s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785074
+```
+
+Using a fixed attribute cache timeout of 30 (`actimeo=30`) instead of the variable min/max, I was able to get the improved performance more reliably (after an initial warmup).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,acregmin=30,acregmax=30,acdirmax=30,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   790086
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.695s
+user	0m0.010s
+sys	0m0.009s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795087
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.240s
+user	0m0.008s
+sys	0m0.008s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795088
+```
+
+Anyway... upping the NFS attribute cache improves performance drastically in
+this controlled experiment (~ 90%). However, running the same experiment using the curl request that @Mattflaschen posted yields a lesser (but still significant) performance gain (~ 25%), and the overall request time is still an attrocious 4+ seconds for me.
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   804036
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m5.758s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805076
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m4.270s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805098
+```",1426107936,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Some controlled tests verify that NFS + stat is a part of this performance
+issue, but maybe not the whole problem.
+
+First I created 5000 files in `vagrant/tmp/mtime` and dropped this into `/var/www/w/mtimes.php`:
+```
+<?php
+
+chdir('/vagrant/tmp/mtime');
+array_map('stat', scandir('.'));
+```
+
+I experimented with NFS [[ http://linux.die.net/man/5/nfs | mount options ]] dealing with the [[ http://docstore.mik.ua/orelly/networking_2ndEd/nfs/ch18_06.htm#nfs2-CHP-18-SECT-6.html | attribute cache ]] and requests to `mtimes.php`.
+
+Using the default options the performance is variable depending on how long you wait between requests. Quick subsequent requests can preempt the default file attribute cache timeout (which is between 3 and 30 seconds, `acregmin`/`acregmax`), while waiting longer results in uncached results. The first two requests below show that the PHP `stat` calls resulted in NFS `getattr` calls to the server, while the final request was made quickly enough that it preempted the cache expiration (no `getattr` calls).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   775067
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.750s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   780068
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m4.228s
+user	0m0.009s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785070
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.249s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785074
+```
+
+Using a fixed attribute cache timeout of 30 (`actimeo=30`) instead of the variable min/max, I was able to get the improved performance more reliably (after an initial warmup).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,acregmin=30,acregmax=30,acdirmax=30,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   790086
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.695s
+user	0m0.010s
+sys	0m0.009s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795087
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.240s
+user	0m0.008s
+sys	0m0.008s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795088
+```
+
+Anyway... upping the NFS attribute cache improves performance drastically in
+this controlled experiment (~ 90%). However, running the same experiment using the curl request that @Mattflaschen posted yields a lesser (but still significant) performance gain (~ 25%), and the overall request time is still an attrocious 4+ seconds for me.
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   804036
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m5.758s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805076
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m4.270s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805098
+```",1426107853,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"The following tests are with HHVM and NFS:
+
+Before:
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl
+nfs v4 client        total:   696869 
+------------- ------------- --------
+nfs v4 client         read:     3114 
+nfs v4 client        write:   156537 
+nfs v4 client       commit:     6120 
+nfs v4 client         open:   129880 
+nfs v4 client    open_conf:       37 
+nfs v4 client        close:   129397 
+nfs v4 client      setattr:      129 
+nfs v4 client       fsinfo:        4 
+nfs v4 client        renew:      478 
+nfs v4 client    setclntid:        4 
+nfs v4 client      confirm:        2 
+nfs v4 client         lock:        1 
+nfs v4 client        locku:        1 
+nfs v4 client       access:    59190 
+nfs v4 client      getattr:   194778 
+nfs v4 client       lookup:    11294 
+nfs v4 client  lookup_root:        4 
+nfs v4 client       remove:       35 
+nfs v4 client       rename:        6 
+nfs v4 client       create:        1 
+nfs v4 client     pathconf:        3 
+nfs v4 client       statfs:        2 
+nfs v4 client      readdir:      213 
+nfs v4 client  server_caps:        7 
+nfs v4 client  delegreturn:     5629 
+nfs v4 client  rel_lkowner:        1 
+nfs v4 client      secinfo:        2 
+```
+
+Request (made from outside, generated from using Firefox's Copy as cURL):
+
+time curl 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' -H 'Host: 127.0.0.1:8080' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.5.0' -H 'Accept: */*' -H 'Accept-Language: en-us,en;q=0.9,eng-us;q=0.8,eng;q=0.7,en-gb;q=0.6,en-au;q=0.4,en-ca;q=0.3,en-us.utf-8;q=0.2,en-local;q=0.1' -H 'Accept-Encoding: gzip, deflate' -H 'DNT: 1' -H 'Referer: http://127.0.0.1:8080/wiki/Main_Page' -H 'Cookie: wikiUserName=Admin; mediaWiki.user.bucket%3Amoodbar%403-trigger=3%3Aediting; ext.moodBar%403-tooltip=1; wikiEditor-3-booklet-colors-page=colors; wikiEditor-3-booklet-emoticons-page=emoticons; wikiUserID=1; stopMobileRedirect=true; wikiEditor-0-toolbar-section=advanced; wikiEditor-0-booklet-characters-page=latin; mediaWiki.user.sessionId=cc8787424e30789f; wiki_session=svsh89804l89ns69fpgrv7rbf7' -H 'Connection: keep-alive' -H 'If-Modified-Since: Wed, 11 Mar 2015 00:11:04 GMT'
+
+(output omitted)
+
+    0.01s user 0.00s system 0% cpu 1:10.11 total
+
+After:
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl
+nfs v4 client        total:   706258 
+------------- ------------- --------
+nfs v4 client         read:     3114 
+nfs v4 client        write:   159015 
+nfs v4 client       commit:     6290 
+nfs v4 client         open:   131533 
+nfs v4 client    open_conf:       38 
+nfs v4 client        close:   131019 
+nfs v4 client      setattr:      129 
+nfs v4 client       fsinfo:        4 
+nfs v4 client        renew:      482 
+nfs v4 client    setclntid:        4 
+nfs v4 client      confirm:        2 
+nfs v4 client         lock:        1 
+nfs v4 client        locku:        1 
+nfs v4 client       access:    59751 
+nfs v4 client      getattr:   197448 
+nfs v4 client       lookup:    11464 
+nfs v4 client  lookup_root:        4 
+nfs v4 client       remove:       35 
+nfs v4 client       rename:        6 
+nfs v4 client       create:        1 
+nfs v4 client     pathconf:        3 
+nfs v4 client       statfs:        2 
+nfs v4 client      readdir:      213 
+nfs v4 client  server_caps:        7 
+nfs v4 client  delegreturn:     5689 
+nfs v4 client  rel_lkowner:        1 
+nfs v4 client      secinfo:        2 
+```",1426036784,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"I'm using NFS with a Debian Jessie host, with 3000 MB allocated in .settings.yaml, out of 8 GB on my host.
+
+Performance got a lot worse for me recently.  Talking about it with @bd808, I think the cause of it suddenly getting worse may have been enabling VisualEditor (many JS files could interact badly with any MediaWiki-Vagrant and/or RL stat problems).
+
+I'm also currently using the memcached role (currently with 300 MB, but that's one thing I'm experimenting with).  Before, I was using Redis, but Flow is not as well tested with that.  Just recently before switching to memcached, I got some errors that may or may not have been related to caching.
+
+Finally, I had wgResourceLoaderStorageEnabled set to true (but may experiment with turning that off) and I have:
+
+    $wgCacheEpoch = '20141008025959';",1426035181,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"If MF is installed, T91659 could be related.",1426034821,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Enabling HHVM's stat cache is a bust. The implementation in HHVM awesomely uses `inotify` to have the kernel notify it of changes to files on disk. Sadly `inotify` doesn't work on NFS mounts, so HHVM never gets clued in that files are changing.",1425441502,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Magnitudes faster with that patch 12 seconds -> 4 seconds. Still room for improvement though. cc @rmoen @jhernandez who have been having similar issues.
+",1425423870,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,We looked at this for a bit today and may be narrowing in on some parts of the problem. ResouceLoader is doing a lot of file mtime operations. The patch I've posted is one attempt at applying a bandaid to the bleeding patient. I want to dig deeper though and see if there are other settings we can change to make RL happier.,1425423639,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 194217 had a related patch set uploaded (by BryanDavis):
+Enable stat cache for HHVM fcgi container
+
+[[https://gerrit.wikimedia.org/r/194217]]
+",1425423205,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"yup. My vagrant is a complete mess right now. :-/ Was hoping to get some time during the dev summit to debug but didn't get the chance.
+",1422576272,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"@jdlrobson, have you experienced this same issue since bumping up your VM's memory?",1422565797,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"This is resurfacing. It seems to become an issue as soon as I install multiple wikis (I just had a fresh install and installed both wikidata and commons roles)
+",1421105335,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Still hitting this issue with a new install.
+Changed less to 0.4.0.
+and then sshing into my vagrant instance and ran `composer update`
+Switched back to 0.5.0 and ran `composer update` and the problem seems to have gone. Strange. Will keep investigating and updating this bug report if/when it comes back.",1420571476,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,">>! In T78733#937057, @matmarex wrote:
+> It upgraded the lessphp library from 0.4.0 to 0.5.0, so I guess they had a performance regression.
+
+Actually https://gerrit.wikimedia.org/r/#/c/174448/ is what upgraded the library, bringing it via composer should have been the same version since Krinkle created a new tag from master.",1419023178,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"It upgraded the lessphp library from 0.4.0 to 0.5.0, so I guess they had a performance regression.",1419022998,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"@legoktm any idea why this has had just a negative effect on performance for me?
+",1419022825,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"This is the commit where it all went wrong for me
+https://gerrit.wikimedia.org/r/#/c/175485/",1419022791,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"I can't view T84960 :(
+Okay now I'm getting somewhere. If I checkout commit Id0221e9f68786758e10b2f222f5e9170898e320d it only takes 1 second. Going to keep investigating till I find the core change that introduced my woes...",1419022343,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Depending on how recently you mean. The result of some `compileFile` calls used to be cached separately some time ago, now it isn't (only the final CSS is).
+
+Perhaps you have some modules there that are being invalidated (incorrectly) too often?",1419019112,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,The cache misses may be due to T84960.,1419019043,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Okay so I debugged this and the source of slowdown seems to be $result = $compiler->compileFile( $fileName ); in compileLessFile
+
+Did something change to do with less recently?
+
+To replicate install MobileFrontend vagrant role and load:
+http://localhost:8080/w/load.php?debug=false&lang=en&modules=mediawiki.ui.button%7Cmobile.pagelist.styles%7Cskins.minerva.alpha.styles%7Cskins.minerva.chrome.styles%7Cskins.minerva.content.styles%7Cskins.minerva.content.styles.beta%7Cskins.minerva.drawers.styles%7Cskins.minerva.icons.styles%7Cskins.minerva.tablet.styles%7Cskins.minerva.tablet.styles.beta&only=styles&skin=minerva&target=mobile&forceprofile=1
+
+On my machine this is taking over 16s to load. Can anyone else confirm similar slowdown?
+",1419018835,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"I'm rarely changing the css. I'm seeing lots of rl-minify-css-cache-misses in the redis trace though. Is it possible my caching isn't setup correctly? Will take look at profiling
+
+Reloading and stopping/starting not helping.
+
+@dduval yeh updating LocalSettings.php to support development for MobileFrontend and installing certain pages seems like a good idea.",1419013265,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Also, since it sounds like you're dependent on a fair amount of custom wiki configuration and content/templates for your development, you might want to consider packaging it as a local or published Vagrant role. (Watch @bd808's part of the recent [[ https://www.mediawiki.org/wiki/File:What%27s_new_with_MediaWiki-Vagrant.webm | tech talk ]] for examples; I'm also available to pair on it.)",1418848863,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"From what I remember when we were troubleshooting this yesterday, HHVM was tacking the CPU during those same moments which makes me think it's not any sort of IO wait on redis that's hanging things up. I second the profiling and maybe restarting HHVM (or `vagrant reload`) for good measure.",1418847882,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Are you constantly changing your CSS? All the info you've posted looks like RL is either minifying the CSS each time (cache misses), or contacting redis in vagrant is slow.
+
+Have you tried profiling to see what exactly is slow?",1418847540,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"This is making it near impossible for me to work now :-(
+I really don't want to vagrant destroy as setting up a new wiki instance will take up most of my day.
+",1418847345,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"ve.ce.Surface is a 130k beast (>4000 lines) - more than twice as long as Converter and Transaction, the next largest files. Working on it will kill your mouse wheel and sanity.
+
+We should try and break it up by functionality, e.g.
+
+* Key strokes
+* Copy/paste
+* Drag/drop",1418756950,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-j5vmxwhgpdua5wcyruej,task_description,open
+Break up ve.ce.Surface.js by functionality,"Change #1079329 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (0e82a6db8)%%%
+https://gerrit.wikimedia.org/r/1079329",1730315223,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079329 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (69d7ca482)%%%
+https://gerrit.wikimedia.org/r/1079329",1730223714,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1080733 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Move drag/drop handling code to DragDropHandler%%%
+https://gerrit.wikimedia.org/r/1080733",1730213735,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079324 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Move selection handling code to SelectionManager%%%
+https://gerrit.wikimedia.org/r/1079324",1730213526,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1081991 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (bae9101b7)%%%
+https://gerrit.wikimedia.org/r/1081991",1730211475,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1081991 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (bae9101b7)%%%
+https://gerrit.wikimedia.org/r/1081991",1729522997,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079286 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Move paste handling code to ve.ce.ClipboardHandler%%%
+https://gerrit.wikimedia.org/r/1079286",1729279978,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1080733 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] Move drag/drop handling code to DragDropHandler%%%
+https://gerrit.wikimedia.org/r/1080733",1729090254,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079324 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Move selection handling code to SelectionManager%%%
+https://gerrit.wikimedia.org/r/1079324",1728581141,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079286 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Move paste handling code to ve.ce.PasteHandler%%%
+https://gerrit.wikimedia.org/r/1079286",1728567923,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"After the above patch it dropped to 3,400 lines. Today it is 5,400 (!)",1701814187,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change 248911 merged by jenkins-bot:
+Introduce key down handlers to separate logic from ce surface
+
+[[https://gerrit.wikimedia.org/r/248911]]",1446233373,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,https://gerrit.wikimedia.org/r/#/c/248911/,1446135119,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+When I changed the website link in an infobox all other links got redlinks,"I tried to edit an infobox with the VisualEditor in the German Wikipedia. I changed the website address there.
+But when I closed the ""infobox editor"" all links in the infobox (except of the link I changed) got redlinks.
+
+I think this is only a display error, but anyway I didn't saved the changes I made.",1418491053,PHID-USER-qq2c7r7m35tr32zlbsc3,PHID-TASK-dgumy74z3zd6vmd4zme2,task_description,duplicate
+When I changed the website link in an infobox all other links got redlinks,"James, did you confirm this?",1421804311,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dgumy74z3zd6vmd4zme2,task_subcomment,NA
+When I changed the website link in an infobox all other links got redlinks,This feels like a duplicate.,1419523069,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dgumy74z3zd6vmd4zme2,task_subcomment,NA
+Performance issues in Internet Explorer 11,"This problem with VisualEditor's performance was reported at MediaWiki.org by User:Leaderboard, who was editing on the English Wikibooks.  The problem is intermittent or at least variable in severity.  It may depend on the size of the page.  It appears to happen at MediaWiki (testing in the sandbox) as well, after about a page's worth of text has been added.  Here's the problem in his own words:
+
+> First , it is too slow to display text which I am typing. It shows it in a slow and slideshow speed. Looks like it's quite slow. And , on Task Manager , it shows that it is using one and only 1 full(utilizes 100% CPU for that) thread for this. It stays at full utilization when I'm typing and becomes very slow. I'm using Internet Explorer 11.
+>
+> When testing using Performance Dashboard , it stays at 5-15% during idle and while typing , it spikes to 50-55% of total CPU usage.
+>
+> %%% Running on a Dell Inspiron 6400 with Intel Core2Duo T7200 @ 2Ghz and 4GB DDR2 with Windows 8.1 tested.""
+",1418411665,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-c2lpx2p2cpizjy235cz3,task_description,declined
+Performance issues in Internet Explorer 11,IE11 support will end within the next year. Not worth making new investments that are specific to how certain browser APIs may perform less well in IE11.,1632431721,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-c2lpx2p2cpizjy235cz3,task_subcomment,NA
+Don't text-transform: capitalize; section headers in the special character inserter,"In Polish, headlines are written with 1st-letter uppercase only. That's why there are ""Polskie diakrytyzowane"" and ""Inne diakrytyzowane"" in [[https://translatewiki.net/wiki/MediaWiki:Visualeditor-specialcharinspector-characterlist-insert/pl|Translatewiki:MediaWiki:Visualeditor-specialcharinspector-characterlist-insert/pl]]. VE displays it wrong (as if English Case Style was Default). {F20866}",1418328634,PHID-USER-gf5juv3z3p75bykrcrhf,PHID-TASK-fxifnazewrqgvu4gcnog,task_description,resolved
+Don't text-transform: capitalize; section headers in the special character inserter,"Change 179957 merged by jenkins-bot:
+SpecialCharacterInspector: Don't auto-capitalise the headings
+
+[[https://gerrit.wikimedia.org/r/179957]]",1418744358,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fxifnazewrqgvu4gcnog,task_subcomment,NA
+Don't text-transform: capitalize; section headers in the special character inserter,"Change 179957 had a related patch set uploaded (by Jforrester):
+SpecialCharacterInspector: Don't auto-capitalise the headings
+
+[[https://gerrit.wikimedia.org/r/179957]]
+
+#patch-for-review",1418664161,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fxifnazewrqgvu4gcnog,task_subcomment,NA
+Parameter entries aren't indented in the transclusion dialog's booklet layout in VisualEditor when using the OOUI MediaWiki theme,"See screenshot:
+
+{F20244}",1418326903,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sqhibubgcam4rw6zg2im,task_description,resolved
+Parameter entries aren't indented in the transclusion dialog's booklet layout in VisualEditor when using the OOUI MediaWiki theme,"Change 179198 merged by jenkins-bot:
+MediaWiki theme: Copy .theme-oo-ui-outline{Controls,Option}Widget from Apex
+
+[[https://gerrit.wikimedia.org/r/179198]]",1418335593,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sqhibubgcam4rw6zg2im,task_subcomment,NA
+Parameter entries aren't indented in the transclusion dialog's booklet layout in VisualEditor when using the OOUI MediaWiki theme,"Change 179198 had a related patch set uploaded (by Bartosz Dziewoński):
+Copy .theme-oo-ui-{outlineControlsWidget, outlineOptionWidget} from Apex to MediaWiki
+
+[[https://gerrit.wikimedia.org/r/179198]]
+
+#patch-for-review",1418332521,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sqhibubgcam4rw6zg2im,task_subcomment,NA
+"""Uncaught TypeError: Cannot read property 'getSurface' of null"", on undoing a comment in block quote.","Environment- test2, beta, Production
+Browser- Chrome 39
+
+1> Insert a comment.Click on ""Insert"" button to close the dialog.
+2> While the comment is still highlighted, select any option from the Heading format list.For ex- select Block quote
+3> Click to undo(keeping the comment highlighted).Notice the icon and the comment pop-up get detached. Also, JS error ""Uncaught TypeError: Cannot read property 'getSurface' of null"" shows up in console.
+
+See screenshot.
+",1418315290,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-fpwsjr2z43gzastjf6ak,task_description,declined
+"""Uncaught TypeError: Cannot read property 'getSurface' of null"", on undoing a comment in block quote.","There are over 300+ calls to .getSurface() in VisualEditor.
+
+It's important to distinguish between instances of an error and categories of errors. Sometimes errors are unique by their message, other times they are unique by their cause or stack. Cases of bad method calls vary by their caller.
+
+Let's assume the 2014 reproduction steps for a specific case of a bad method call ocurred are not related.",1692891005,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fpwsjr2z43gzastjf6ak,task_subcomment,NA
+"""Uncaught TypeError: Cannot read property 'getSurface' of null"", on undoing a comment in block quote.","Seeing quite of a few errors in log:
+```
+at ve.ce.FocusableNode.getBoundingRect  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:501:932
+at ve.ce.LinearSelection.getSelectionBoundingRect  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:610:833
+at ve.ce.LinearSelection.getSelectionFocusRect  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:612:871
+at ve.ui.Surface.scrollSelectionIntoView  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:694:403
+at ve.ui.Surface.adjustVisiblePadding  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:698:804
+at ve.ui.Surface.onViewPosition  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:696:537
+at OO.EventEmitter.emit  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.centralNotice.choiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2CstartUp%7Cext.centralauth.ForeignApi%2Ccentralautologin%7Cext.cite.ux-enhancements%7Cext.cx.entrypoints.languagesearcher.init%7Cext.cx.entrypoints.mffrequentlanguages%7Cext.cx.eventlogging.campaigns%7Cext.cx.model%7Cext.dismissableSiteNotice%2CeventLogging%2CnavigationTiming%2Cpopups%2CshortUrl%2CwikimediaEvents%7Cext.echo.centralauth%7Cext.growthExperiments.SuggestedEditSession%7Cext.relatedArticles.readMore.bootstrap%7Cjquery%2Coojs%2Csite%7Cjquery.client%2Ccookie%7Cmediawiki.ForeignApi%2CString%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Crouter%2Cstorage%2Ctemplate%2Cuser%2Cutil%2CvisibleTimeout%7Cmediawiki.ForeignApi.core%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.page.watch.ajax%7Cmediawiki.template.mustache%7Cmediawiki.ui.anchor%7Cmobile.init%2Cstartup%7Cmobile.ooui.icons%7Cmobile.pagelist.styles%7Cmobile.pagesummary.styles%7Cmobile.placeholder.images%7Cmobile.startup.images%7Cmw.cx.SiteMapper%7Cmw.externalguidance.init%7Cskins.minerva.icons.images.scripts.misc%7Cskins.minerva.icons.page.issues.default.color%7Cskins.minerva.icons.page.issues.medium.color%7Cskins.minerva.icons.page.issues.uncolored%7Cskins.minerva.messageBox.styles%7Cskins.minerva.scripts&skin=minerva&version=bxy2z:302:399
+at https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:816:614
+at mightThrow  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.centralNotice.choiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2CstartUp%7Cext.centralauth.ForeignApi%2Ccentralautologin%7Cext.cite.ux-enhancements%7Cext.cx.entrypoints.languagesearcher.init%7Cext.cx.entrypoints.mffrequentlanguages%7Cext.cx.eventlogging.campaigns%7Cext.cx.model%7Cext.dismissableSiteNotice%2CeventLogging%2CnavigationTiming%2Cpopups%2CshortUrl%2CwikimediaEvents%7Cext.echo.centralauth%7Cext.growthExperiments.SuggestedEditSession%7Cext.relatedArticles.readMore.bootstrap%7Cjquery%2Coojs%2Csite%7Cjquery.client%2Ccookie%7Cmediawiki.ForeignApi%2CString%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Crouter%2Cstorage%2Ctemplate%2Cuser%2Cutil%2CvisibleTimeout%7Cmediawiki.ForeignApi.core%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.page.watch.ajax%7Cmediawiki.template.mustache%7Cmediawiki.ui.anchor%7Cmobile.init%2Cstartup%7Cmobile.ooui.icons%7Cmobile.pagelist.styles%7Cmobile.pagesummary.styles%7Cmobile.placeholder.images%7Cmobile.startup.images%7Cmw.cx.SiteMapper%7Cmw.externalguidance.init%7Cskins.minerva.icons.images.scripts.misc%7Cskins.minerva.icons.page.issues.default.color%7Cskins.minerva.icons.page.issues.medium.color%7Cskins.minerva.icons.page.issues.uncolored%7Cskins.minerva.messageBox.styles%7Cskins.minerva.scripts&skin=minerva&version=bxy2z:199:881
+at process  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.centralNotice.choiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2CstartUp%7Cext.centralauth.ForeignApi%2Ccentralautologin%7Cext.cite.ux-enhancements%7Cext.cx.entrypoints.languagesearcher.init%7Cext.cx.entrypoints.mffrequentlanguages%7Cext.cx.eventlogging.campaigns%7Cext.cx.model%7Cext.dismissableSiteNotice%2CeventLogging%2CnavigationTiming%2Cpopups%2CshortUrl%2CwikimediaEvents%7Cext.echo.centralauth%7Cext.growthExperiments.SuggestedEditSession%7Cext.relatedArticles.readMore.bootstrap%7Cjquery%2Coojs%2Csite%7Cjquery.client%2Ccookie%7Cmediawiki.ForeignApi%2CString%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Crouter%2Cstorage%2Ctemplate%2Cuser%2Cutil%2CvisibleTimeout%7Cmediawiki.ForeignApi.core%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.page.watch.ajax%7Cmediawiki.template.mustache%7Cmediawiki.ui.anchor%7Cmobile.init%2Cstartup%7Cmobile.ooui.icons%7Cmobile.pagelist.styles%7Cmobile.pagesummary.styles%7Cmobile.placeholder.images%7Cmobile.startup.images%7Cmw.cx.SiteMapper%7Cmw.externalguidance.init%7Cskins.minerva.icons.images.scripts.misc%7Cskins.minerva.icons.page.issues.default.color%7Cskins.minerva.icons.page.issues.medium.color%7Cskins.minerva.icons.page.issues.uncolored%7Cskins.minerva.messageBox.styles%7Cskins.minerva.scripts&skin=minerva&version=bxy2z:200:544
+```
+https://logstash.wikimedia.org/app/dashboards#/doc/logstash-*/logstash-default-1-7.0.0-1-2023.06.12?id=cGYgsIgBEBRX9obd4Pwh",1686613889,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-fpwsjr2z43gzastjf6ak,task_subcomment,NA
+"""Uncaught TypeError: Cannot read property 'getSurface' of null"", on undoing a comment in block quote.","Screenshot 
+{F20838}",1418315346,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-fpwsjr2z43gzastjf6ak,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"1. Click on https://www.mediawiki.org/w/index.php?title=VisualEditor/status&veaction=edit
+2. Wait for editor to load
+3. Use find-and-replace
+4. Try to type ""now support ""
+5. Observe system die in flames after 'n' was typed, not letting you type 'o' yet, let alone the rest.
+6. Cry.
+
+250ms is our normal threshold. Let's do that.",1418275115,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_description,resolved
+Limit effect of search-and-replace assessment on long documents,"This is now better, but not great in very extreme cases.",1420467860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Change 180635 merged by jenkins-bot:
+Use viewport clipping when lots of search results found
+
+[[https://gerrit.wikimedia.org/r/180635]]",1420466184,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Change 180195 merged by jenkins-bot:
+Limit number of find and replace results to render
+
+[[https://gerrit.wikimedia.org/r/180195]]",1420465915,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Change 180635 had a related patch set uploaded (by Esanders):
+Use viewport clipping when lots of search results found
+
+[[https://gerrit.wikimedia.org/r/180635]]
+
+#patch-for-review",1418849860,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"getVisibleRange is only ever going to be an estimate due to floats and position absolute, and you'll probably add +/- 50% for good measure. Throwing in a computed style calls ( .css('position') ) is going to make it several times slower.",1418755519,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Yeah I was thinking of binary search too, but I don't know how reliable it'll be because the DOM sequence is similar to but not the same as the rendered visual sequence (due to floated things; good call on absolute positioning but I don't think you'll see absolutely positioned editable text very often).
+
+getVisibleRange() sounds interesting, and that may well be binary search-able if you stick to known-safe things (like .css( 'position' ) === 'static' maybe?)",1418755060,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"So I considered the render on screen things, and as you point out you'd have occasional problems with floated things or worse, position absolute things. As you point it your approach doesn't help you work out where to start rendering and calculating if something is on screen is basically as expensive as rendering it (getClientRects being the bottleneck). As viable solution might be to do a binary search. Even on a document of 100k characters that would only be 16 checks.
+
+That shouldn't be too difficult to implement, the only problem being we'd have to re-evaluate on window resize and scroll (although debounced), but being a binary search it should be efficient enough. In might even make sense to push that functionality up to the surface view, so you can just ask it to getVisibleRange.",1418754195,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Change 180195 had a related patch set uploaded (by Esanders):
+Limit number of find and replace results to render
+
+[[https://gerrit.wikimedia.org/r/180195]]
+
+#patch-for-review",1418745343,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"I wonder how much not rendering off-screen would save. You'd save on a bunch of DOM modification, but you'd still have to find every result and compute a rect for it to find out whether it's off-screen. I don't know how much time is spent in the DM search vs the highlight rendering, let's find out.
+
+We could also refactor the DM code so it returns one result at a time instead of all at once, then stop once we hit the first off-screen result. This isn't quite perfect (there might be results in floated image captions that appear significantly above/below the text immediately before/after in the DM/DOM), and it would break the ""Kth of N results"" thing, so maybe we could try a hybrid approach where we only do full rendering (i.e. the current approach, maybe without off-screen highlights) if there are <=50 results, and above that we aggressively try to stop searching and rendering as soon as we can, while still allowing the user to force the next result to be found and highlighted by pressing next. Or we could base the approach on finding and rendering at most 10 results before and 10 after the currently highlighted one.
+
+(Another problem that I don't quite have a solution for: if the user is scrolled most of the way down the page, how do you know where results start being visible without just trying them all in sequence)",1418743887,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"That makes it less likely to explode, but doesn't fix the problem, which is that rendering 16000 highlights is too much. There should either be a cap, or some smartness about not rendering off screen.",1418742498,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+"Chinese full stop disappears at the end of paragraphs, if preceded by ref tags","In VisualEditor, it is not always possible to save a paragraph that ends with <ref>(cite source)</ref>。 Upon saving the page, the full stop disappears.  See [[ https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&offset=20141206172053#Symbol_after_citation_disappear_after_edit_50625 | the original report ]].
+
+I successfully added one [[ https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=1309016&oldid=1228107 | in my sandbox at MediaWiki ]], but (a) I pasted the Chinese full stop into the text, rather than entering it normally, and (b) when I pasted it after the ref, it gave me a black sun before the full stop.  Also, I'm running Safari on a Mac, so it may be browser or OS dependent.",1418190956,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gpbnxuzghyxgmcl5cika,task_description,resolved
+"Chinese full stop disappears at the end of paragraphs, if preceded by ref tags",I've re-tested and this seems to now work.,1440120521,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gpbnxuzghyxgmcl5cika,task_subcomment,NA
+"Japanese text disappears (kanji and maybe hiragana, not katakana) when you are writing list entries","[[ https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&offset=20141204053320#Japanese_in_lists_51392 | Original report from MediaWiki.org: ]] from a logged-out editor, on 4 December 2014:
+
+""I just tried to add list items in Japanese. Katakana seemed ok in lists but kanji and maybe hiragana too seemed to delete automatically when pressing enter to go to the next list item.""
+
+I believe that this is different from T74619 in which katakana can't be typed at all.",1418188190,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yfvk4vo7aqne3mus4xte,task_description,resolved
+"Japanese text disappears (kanji and maybe hiragana, not katakana) when you are writing list entries","As far as I can tell, this issue and other Japanese text entry issues are all now fixed. Sorry it took so long to confirm!",1435941289,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yfvk4vo7aqne3mus4xte,task_subcomment,NA
+"Japanese text disappears (kanji and maybe hiragana, not katakana) when you are writing list entries","Confirmed in production. Somehow all works in betalbs and test2. 
+
+This issue is most likely the same bug as T74619.",1418260874,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-yfvk4vo7aqne3mus4xte,task_subcomment,NA
+"Bottom border of text box in save dialog only appears when zoomed in, in VisualEditor when using the OOjs UI MediaWiki theme","See screenshot:
+
+{F20270}",1418156285,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hmqwa7xe2lrqdvsrno4s,task_description,resolved
+"Bottom border of text box in save dialog only appears when zoomed in, in VisualEditor when using the OOjs UI MediaWiki theme",Can't reproduce.,1420929029,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hmqwa7xe2lrqdvsrno4s,task_subcomment,NA
+Layout of the image size options is jarring in VisualEditor when using the OOjs UI MediaWiki theme,"See screenshots:
+
+{F20264}{F20266}",1418156178,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xfimimrnkl7a4samm5xn,task_description,resolved
+Layout of the image size options is jarring in VisualEditor when using the OOjs UI MediaWiki theme,This was fixed in the great MediaWiki theme re-write for wmf13.,1420853400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xfimimrnkl7a4samm5xn,task_subcomment,NA
+Layout of the image size options is jarring in VisualEditor when using the OOjs UI MediaWiki theme,"One of the screenshots got converted to TIFF locally, it seems.",1418327272,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xfimimrnkl7a4samm5xn,task_subcomment,NA
+Layout of the image size options is jarring in VisualEditor when using the OOjs UI MediaWiki theme,It doesn't seem very different from Apex to me. Also what's up with the attachments on this task?,1418327170,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-xfimimrnkl7a4samm5xn,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"See screenshot:
+
+{F20251}
+
+(A problem in Apex too, but feels worse in MW.)",1418155768,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wegjd34ahvbrxxjftgql,task_description,resolved
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,Verified the fix in Betalabs and test2,1421366652,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,Checked in betalabs - see the attached screenshot.{F28262},1421103113,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,">>! In T78039#966523, @Krenair wrote:
+> I checked the resolution to this bug on deployment-prep and found that to close the category popup you actually have to click outside the button which opened it. But I would expect that clicking the button again (while the popup is still open) would close it.
+
+Open a ticket?",1420833547,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,I checked the resolution to this bug on deployment-prep and found that to close the category popup you actually have to click outside the button which opened it. But I would expect that clicking the button again (while the popup is still open) would close it.,1420833140,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"@Ricordisamoa, since you subscribed the same minute that @Jdforrester-WMF resolved this (and removed your subscription in the process), I'm assuming it was just Phabricator's lack of conflict detection. See T78236",1420832447,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,@Jdforrester-WMF Why shouldn't I be subscribed?,1420821946,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"Change 183486 merged by jenkins-bot:
+Fix styling of MWCategoryWidget to match MW theme
+
+[[https://gerrit.wikimedia.org/r/183486]]",1420821413,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,The rounded corners are just left over the from Apex skin where they looked less out of place. Fixed in patch above.,1420721158,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"Change 183486 had a related patch set uploaded (by Esanders):
+Fix styling of MWCategoryWidget to match MW theme
+
+[[https://gerrit.wikimedia.org/r/183486]]
+
+#patch-for-review",1420721044,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"(The category selector really should be implemented using the kind of multiselect widget used here by Phabricator for lists of projects or people subscribed to the task, etc. (Phab calls them ""tokenizers"", which if you ask me is a pretty silly name.) Some of MediaWiki's forms also use something similar, e.g. on <https://wikitech.wikimedia.org/wiki/Special:NovaSecurityGroup> (alas, you need to be logged in to view that page, apparently).)",1420679005,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"Whatever you call it, (nearly) everything else in VE is using the standard form style first used in MediaWiki UI, while this is using something different and therefore looks weird and silly. ",1420678026,PHID-USER-2z6624adiq3sr74fvzu6,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,">>! In T78039#942748, @Jay8g wrote:
+> Why aren't we just using a standard mw-ui form for this?
+
+Nothing in VisualEditor or the new OOjs UI front-end has anything to do with MediaWiki UI, which was built as an //ad hoc// provision for systems not yet using OOjs UI.",1420657809,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"I agree, lets use the standard form field for this.",1420485532,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,Why aren't we just using a standard mw-ui form for this?,1419391070,PHID-USER-2z6624adiq3sr74fvzu6,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Local Info and Discussions for Visual Editor,"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/64 //
+
+== Narrative ==
+
+As a user, I want localinfo and discussion pages forVisual Editor Beta Features, so I can read them and respond in my language.
+
+
+
+== Acceptance Criteria ==
+
+Enable local links for info and discussion pages forthe VisualEditor Beta Features.
+
+
+
+== Related Bugs ==
+
+== Related Stories ==
+
+See more VE BF feature requirements here:
+
+ [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] ",1418054449,PHID-USER-64gvupsl7ajewpshylma,PHID-TASK-tobiwpavuldjyxvbgv2n,task_description,resolved
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,This would be hugely appreciated.,1417905944,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t6gmkam4z4t2upv65tdm,task_description,resolved
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,Thanks!,1418681597,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,Herald rule H10 created.,1418681581,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,">>! In T76954#849205, @Aklapper wrote:
+> Summarizing to check I get this right before executing:
+> 
+> So whenever a task's projects include any of
+> * VisualEditor-ContentEditable
+> * VisualEditor-ContentLanguage
+> * VisualEditor-CopyPaste
+> * VisualEditor-DataModel
+> * VisualEditor-EditingTools
+> * VisualEditor-Initialisation
+> * VisualEditor-InterfaceLanguage
+> * VisualEditor-MediaWiki
+> * VisualEditor-MediaWiki-Links
+> * VisualEditor-MediaWiki-Media
+> * VisualEditor-MediaWiki-Mobile
+> * VisualEditor-MediaWiki-References
+> * VisualEditor-MediaWiki-Templates
+> * VisualEditor-Performance
+> * VisualEditor-Tables
+> automatically add project ""VisualEditor""?
+
+Yes.
+
+> Note there are two options: Take this actions //every time// or //only the first time// this rule matches. I guess you want everytime.
+
+I think that would make sense, yes.
+
+> Also note that whenever you create a new VE-* project the rule needs to be adjusted. It's not possible to define some placeholders like * for parts of project names like ""begins with the string"".
+
+Yeah, I guessed as much.",1418680979,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,">>! In T76954#848827, @Qgil wrote:
+> If the Phabricator team would be included in the Herald policy, I could help you. @aklapper, your choice.  :)
+
+I think that makes sense, still would like to discuss with the team first due to security implications.",1418680245,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,"Summarizing to check I get this right before executing:
+
+So whenever a task's projects include any of
+* VisualEditor-ContentEditable
+* VisualEditor-ContentLanguage
+* VisualEditor-CopyPaste
+* VisualEditor-DataModel
+* VisualEditor-EditingTools
+* VisualEditor-Initialisation
+* VisualEditor-InterfaceLanguage
+* VisualEditor-MediaWiki
+* VisualEditor-MediaWiki-Links
+* VisualEditor-MediaWiki-Media
+* VisualEditor-MediaWiki-Mobile
+* VisualEditor-MediaWiki-References
+* VisualEditor-MediaWiki-Templates
+* VisualEditor-Performance
+* VisualEditor-Tables
+automatically add project ""VisualEditor""?
+
+Note there are two options: Take this actions //every time// or //only the first time// this rule matches. I guess you want everytime.
+Also note that whenever you create a new VE-* project the rule needs to be adjusted. It's not possible to define some placeholders like * for parts of project names like ""begins with the string"".",1418680167,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,"If the Phabricator team would be included in the Herald policy, I could help you. @aklapper, your choice.  :)",1418675152,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","When editing the infobox in https://fr.wikipedia.org/w/index.php?title=S%C3%A9bastien_Texier&veaction=edit , the heading is misaligned (overlapping with button), see screenshot.
+
+{F19186}",1417892100,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_description,resolved
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","The main place people encounter this is where all three labels are very long; this ""fix"" doesn't actually help them.",1433457500,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Well, no, it doesn't change anything except for the case where the label would be clipped.
+
+| | Normal label | Long label
+| | -- | -- |
+| Before | {F174792,size=full} | {F174794,size=full}
+| -- |
+| After | {F174798,size=full} | {F174796,size=full}
+| -- |",1433457742,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Well, no, it doesn't change anything except for the case where the label would be clipped.
+
+| | Normal label | Long label
+| | -- | -- |
+| Before | {F174792,size=full} | {F174794,size=full}
+| -- |
+| After | {F174796,size=full} | {F174798,size=full}
+| -- |",1433457714,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Well, no, it doesn't change anything except for the case where the label would be clipped.
+
+Before:
+{F174787}
+After:
+{F174790}",1433457448,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",">>! In T76947#1339343, @matmarex wrote:
+> Worth a #user-notice, I think? I believe this improves our UI in several languages significantly. :)
+
+And makes it look worse in others. We'll need to test it post-release to see what further tweaks we need to make VE-side.",1433457396,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Worth a #user-notice, I think? I believe this improves our UI in several languages significantly. :)",1433457357,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Change 160812 merged by jenkins-bot:
+ProcessDialog: Don't center the title label if there's not enough space
+
+[[https://gerrit.wikimedia.org/r/160812]]",1433457158,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Change 160812 had a related patch set uploaded (by Bartosz Dziewoński):
+ProcessDialog: Don't center the title label if there's not enough space
+
+[[https://gerrit.wikimedia.org/r/160812]]
+",1433347960,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",">>! In T76947#1187412, @Whatamidoing-WMF wrote:
+> A few images to add to this problem (images show Russian): 
+
+""tempfile.ru"" is not very reassuring about the lifetime of these links, so let's copy here.
+
+>   - save: http://img1.tempfile.ru/14007/217cf59a63/72ca3ef85264e46dc8940df5.png
+{F109767}
+>   - review: http://img5.tempfile.ru/14007/21e2c7cd06/db0830133840b484326c1ae5.png
+{F109769}
+>   - in templates: http://img1.tempfile.ru/14007/2141f10bfd/81132103a7b84539c4196b6c.png
+{F109771}
+>   - when add already used ref: http://tempfile.ru/view/14007/21b40770ca/cd799edc8198704e4665e283.png
+{F109774}",1428439216,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","A few images to add to this problem (images show Russian): 
+
+  - save: http://img1.tempfile.ru/14007/217cf59a63/72ca3ef85264e46dc8940df5.png
+  - review: http://img5.tempfile.ru/14007/21e2c7cd06/db0830133840b484326c1ae5.png
+  - in templates: http://img1.tempfile.ru/14007/2141f10bfd/81132103a7b84539c4196b6c.png
+  - when add already used ref: http://tempfile.ru/view/14007/21b40770ca/cd799edc8198704e4665e283.png
+",1428438606,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",FYI this was brought up again by a user [[ https://phabricator.wikimedia.org/F103020 | testing Citoid ]].,1427231816,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","https://www.mediawiki.org/wiki/VisualEditor/Feedback#terrible_title_in_the_form_of_saving_the_page_52517
+
+save:
+{F38963}
+
+review: 
+{F38964}
+
+in templates: 
+{F38965}
+
+when add already used ref:
+{F38966}",1423569342,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",https://www.mediawiki.org/wiki/VisualEditor/Feedback#terrible_title_in_the_form_of_saving_the_page_52517,1421176643,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","This just became worse with the new design, IMHO.",1421163821,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Same at the German Wikipedia (check the Saving dialog). The French workaround to this one was changing the equivalent of ""Save your changes"" to ""Contribution""...",1417895052,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Thanks, Bartosz. The current behavior is clearly undesirable (useless or partially overlapping dialog titles); we may need to do both (shorten some button labels and optimize placement). I defer to @Jdforrester-WMF on the final approach.",1417892855,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","The solution would be not to absolutely center the title if it can't fit.
+
+| Before | After |
+| ---------|------------ |
+| {F19192,size=full} | {F19190,size=full} |
+",1417892482,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","This is the same issue as T70571, where this has been declined (the suggested solution is to make the button labels shorter). The abandoned patch https://gerrit.wikimedia.org/r/160812 would probably still work.",1417892327,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",{F19186},1417892184,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+A number of VisualEditor dialogs do not cover full screen when 'full' size,"A number of VisualEditor dialogs do not cover full screen when 'full' size.
+
+I can't reproduce this in OOUI demo.
+
+To reproduce:
+
+1. Open a page in VisualEditor
+2. Insert → Template (or Insert → Media, or (hamburger) → Options, or others)
+3. Resize browser window until it is narrower than the dialog
+
+{F19019}",1417791464,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_description,resolved
+A number of VisualEditor dialogs do not cover full screen when 'full' size,"Checked in beta(Chrome, Safari) - VE dialogs fill up the reduced browser window.",1421784791,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_subcomment,NA
+A number of VisualEditor dialogs do not cover full screen when 'full' size,"Change 185094 merged by jenkins-bot:
+ToolbarDialogWindowManager: Don't pollute parent's .static.sizes
+
+[[https://gerrit.wikimedia.org/r/185094]]",1421286417,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_subcomment,NA
+A number of VisualEditor dialogs do not cover full screen when 'full' size,"Change 185094 had a related patch set uploaded (by Bartosz Dziewoński):
+ToolbarDialogWindowManager: Don't pollute parent's .static.sizes
+
+[[https://gerrit.wikimedia.org/r/185094]]
+
+#patch-for-review",1421280963,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_subcomment,NA
+A number of VisualEditor dialogs do not cover full screen when 'full' size,Caused by 5eb7294a748231dca841d49896ccfdd630baef7c (https://gerrit.wikimedia.org/r/#/c/174491/).,1421280019,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"[x] Deprecate
+[x] Replace all code instances in Wikimedia core & deployed extensions
+  [x] `iconTitle` https://codesearch.wmflabs.org/search/?q=iconTitle&i=nope&files=&repos=
+    [x] Kartographer
+    [x] BlueSpiceVisualEditorConnector
+    [x] CollaborationKit
+    [x] CX
+    [x] LanguageTool
+    [x] PerformanceInspector
+    [x] WikibaseQualityConstraints
+  [x] `setIconTitle` https://codesearch.wmflabs.org/search/?q=setIconTitle&i=nope&files=&repos=
+    [x] MW core APISandBox
+  [x] `indicatorTitle` https://codesearch.wmflabs.org/search/?q=indicatorTitle&i=nope&files=&repos=
+  [x] `setIndicatorTitle` https://codesearch.wmflabs.org/search/?q=setIndicatorTitle&i=nope&files=&repos=
+    [x] VE
+[x] Remove – https://gerrit.wikimedia.org/r/#/c/oojs/ui/+/495949/",1417635365,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tjkkepz2glxx6dypkoab,task_description,resolved
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 484850 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Re-introduce: Replace deprecated `setIndicatorTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/484850]]",1548117786,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482145 **merged** by jenkins-bot:
+[mediawiki/core@master] Replace deprecated `setIconTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/482145]]",1548116383,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 484850 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/VisualEditor@master] Re-introduce: Replace deprecated `setIndicatorTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/484850]]",1547705628,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 483796 **merged** by jenkins-bot:
+[mediawiki/core@master] Update OOUI to v0.30.1
+
+[[https://gerrit.wikimedia.org/r/483796]]",1547227735,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 483796 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/core@master] Update OOUI to v0.30.1
+
+[[https://gerrit.wikimedia.org/r/483796]]",1547223618,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),VE change caused T212975. Also inspired T212977,1546899248,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482132 **merged** by jenkins-bot:
+[mediawiki/extensions/ContentTranslation@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482132]]",1546600138,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482130 **merged** by jenkins-bot:
+[mediawiki/extensions/CollaborationKit@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482130]]",1546599778,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482128 **merged** by jenkins-bot:
+[mediawiki/extensions/Kartographer@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482128]]",1546599775,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482138 **merged** by jenkins-bot:
+[mediawiki/extensions/WikibaseQualityConstraints@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482138]]",1546595634,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482137 **merged** by jenkins-bot:
+[mediawiki/extensions/PerformanceInspector@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482137]]",1546575123,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482136 **merged** by jenkins-bot:
+[mediawiki/extensions/LanguageTool@master] Use standard `title` and add better supported screen reader label on top
+
+[[https://gerrit.wikimedia.org/r/482136]]",1546550390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482127 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Replace deprecated `setIndicatorTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/482127]]",1546549021,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482145 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/core@master] Replace deprecated `setIconTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/482145]]",1546548267,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482138 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/WikibaseQualityConstraints@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482138]]",1546547455,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482137 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/PerformanceInspector@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482137]]",1546547141,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482136 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/LanguageTool@master] Use standard `title` and add better supported screen reader label on top
+
+[[https://gerrit.wikimedia.org/r/482136]]",1546546921,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482132 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/ContentTranslation@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482132]]",1546546342,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482130 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/CollaborationKit@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482130]]",1546546054,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482128 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/Kartographer@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482128]]",1546545808,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482127 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/VisualEditor@master] Replace deprecated `setIndicatorTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/482127]]",1546545190,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 480696 **merged** by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE]: Deprecate `iconTitle` and `indicatorTitle`
+
+[[https://gerrit.wikimedia.org/r/480696]]",1546542514,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 480696 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[oojs/ui@master] [DEPRECATING CHANGE]: Deprecate `iconTitle` and `indicatorTitle`
+
+[[https://gerrit.wikimedia.org/r/480696]]",1545196091,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Potential violators:
+```
+
+core/resources/src/mediawiki.special.apisandbox/apisandbox.js:
+  104  					ok = ok || suppressErrors;
+  105  					that.setIcon( ok ? null : 'alert' );
+  106: 					that.setIconTitle( ok ? '' : mw.message( 'apisandbox-alert-field' ).plain() );
+  107  				} );
+  108  			}
+  ...
+  186  				var ok = this.getApiValue() !== undefined || suppressErrors;
+  187  				this.setIcon( ok ? null : 'alert' );
+  188: 				this.setIconTitle( ok ? '' : mw.message( 'apisandbox-alert-field' ).plain() );
+  189  				return $.Deferred().resolve( ok ).promise();
+  190  			}
+  ...
+  234  
+  235  				this.setIcon( ok ? null : 'alert' );
+  236: 				this.setIconTitle( ok ? '' : mw.message( 'apisandbox-alert-field' ).plain() );
+  237  				return $.Deferred().resolve( ok ).promise();
+  238  			},
+  ...
+  292  				var ok = this.getValue() !== null || suppressErrors;
+  293  				this.setIcon( ok ? null : 'alert' );
+  294: 				this.setIconTitle( ok ? '' : mw.message( 'apisandbox-alert-field' ).plain() );
+  295  				return $.Deferred().resolve( ok ).promise();
+  296  			}
+  ...
+  469  					} );
+  470  					widget.setIcon = widget.input.setIcon.bind( widget.input );
+  471: 					widget.setIconTitle = widget.input.setIconTitle.bind( widget.input );
+  472  					widget.getValidity = widget.input.getValidity.bind( widget.input );
+  473  					widget.paramInfo = pi;
+  ...
+ 1364  		this.outlineItem.setLabel( this.displayText );
+ 1365  		this.outlineItem.setIcon( this.apiIsValid || suppressErrors ? null : 'alert' );
+ 1366: 		this.outlineItem.setIconTitle(
+ 1367  			this.apiIsValid || suppressErrors ? '' : mw.message( 'apisandbox-alert-page' ).plain()
+ 1368  		);
+ ....
+ 2009  				if ( that.getOutlineItem() ) {
+ 2010  					that.getOutlineItem().setIcon( that.apiIsValid || suppressErrors ? null : 'alert' );
+ 2011: 					that.getOutlineItem().setIconTitle(
+ 2012  						that.apiIsValid || suppressErrors ? '' : mw.message( 'apisandbox-alert-page' ).plain()
+ 2013  					);
+
+extensions/CollaborationKit/modules/ext.CollaborationKit.list.ui.js:
+  289  					framed: false,
+  290  					icon: 'trash',
+  291: 					iconTitle: mw.msg( 'collaborationkit-list-delete' )
+  292  				} );
+  293  
+  ...
+  298  						framed: false,
+  299  						icon: 'move',
+  300: 						iconTitle: mw.msg( 'collaborationkit-list-move' )
+  301  					} );
+  302  				}
+
+extensions/ContentTranslation/modules/ui/widgets/mw.cx.ui.TitleOptionWidget.js:
+   53  			languageIcon = new OO.ui.IconWidget( {
+   54  				icon: 'language',
+   55: 				iconTitle: mw.msg( 'cx-page-number-of-languages' )
+   56  			} );
+   57  			languageLabel = new OO.ui.LabelWidget( {
+
+extensions/Kartographer/modules/dialog/dialog.js:
+   64  						label: mw.msg( 'kartographer-sidebar-togglebutton' ),
+   65  						icon: 'newWindow',
+   66: 						iconTitle: mw.msg( 'kartographer-sidebar-togglebutton' )
+   67  					} );
+   68  					dialog.mapDetailsButton.connect( dialog, { change: 'toggleSideBar' } );
+
+extensions/Kartographer/modules/wikivoyage/wikivoyage.js:
+   80  				icon = new OO.ui.IconWidget( {
+   81  					icon: 'linkExternal',
+   82: 					iconTitle: mw.msg( 'kartographer-wv-warning-external-source-message' ),
+   83  					classes: [ 'leaflet-control-layers-oo-ui-icon' ]
+   84  				} );
+
+extensions/LanguageTool/modules/ext.LanguageToolDialog.js:
+   71  	this.sendButton = new OO.ui.ButtonWidget( {
+   72  		icon: 'check',
+   73: 		iconTitle: 'LanguageTool'
+   74  	} );
+   75  	this.previousButton = new OO.ui.ButtonWidget( {
+   76  		icon: 'previous',
+   77: 		iconTitle: ve.msg( 'visualeditor-find-and-replace-previous-button' ) + ' ' +
+   78  			ve.ui.triggerRegistry.getMessages( 'findPrevious' ).join( ', ' )
+   79  	} );
+   80  	this.nextButton = new OO.ui.ButtonWidget( {
+   81  		icon: 'next',
+   82: 		iconTitle: ve.msg( 'visualeditor-find-and-replace-next-button' ) + ' ' +
+   83  			ve.ui.triggerRegistry.getMessages( 'findNext' ).join( ', ' )
+   84  	} );
+
+extensions/PerformanceInspector/modules/collectors/ext.PerformanceInspector.modulescss.js:
+  167  						label: mw.msg( 'performanceinspector-modules-css-show-details' ),
+  168  						icon: 'info',
+  169: 						iconTitle: mw.msg( 'performanceinspector-modules-css-show-details' )
+  170  					} );
+  171  				button.on( 'click', function () {
+
+extensions/VisualEditor/modules/ve-mw/ui/pages/ve.ui.MWParameterPage.js:
+   62  		this.statusIndicator
+   63  			.setIndicator( 'required' )
+   64: 			.setIndicatorTitle(
+   65  				ve.msg( 'visualeditor-dialog-transclusion-required-parameter' )
+   66  			);
+   ..
+   75  		this.statusIndicator
+   76  			.setIndicator( 'alert' )
+   77: 			.setIndicatorTitle(
+   78  				ve.msg( 'visualeditor-dialog-transclusion-deprecated-parameter' )
+   79  			);
+   ..
+  378  			this.outlineItem
+  379  				.setIndicator( 'required' )
+  380: 				.setIndicatorTitle(
+  381  					ve.msg( 'visualeditor-dialog-transclusion-required-parameter' )
+  382  				);
+  ...
+  385  			this.outlineItem
+  386  				.setIndicator( 'alert' )
+  387: 				.setIndicatorTitle(
+  388  					ve.msg( 'visualeditor-dialog-transclusion-deprecated-parameter' )
+  389  				);
+
+extensions/WikibaseQualityConstraints/modules/gadget.js:
+  212  	 * @param {jQuery} $container The container to which the button is appended.
+  213  	 * @param {string} icon Identifier for an icon as provided by OOUI.
+  214: 	 * @param {string} iconTitleMessageKey The message key of the title attribute of the icon.
+  215  	 * @param {string} [flags] Optional custom flags the {@link OO.ui.PopupButtonWidget} can understand.
+  216  	 */
+  217: 	SELF.prototype._buildPopup = function ( $content, $container, icon, iconTitleMessageKey, flags /* = '' */ ) {
+  218  		var widget = new OO.ui.PopupButtonWidget( {
+  219  			icon: icon,
+  220: 			iconTitle: mw.message( iconTitleMessageKey ).text(),
+  221  			flags: flags || '',
+  222  			framed: false,
+
+extensions/WikidataPageBanner/includes/WikidataPageBanner.functions.php:
+   50  				$iconName = Sanitizer::escapeClass( $iconname );
+   51  				$iconUrl = Title::newFromText( $value );
+   52: 				$iconTitleText = $iconName;
+   53  				$finalIcon = [ 'url' => '#' ];
+   54  				// reference article for icons provided and is valid, then add its link
+   ..
+   56  					$finalIcon['url'] = $iconUrl->getLocalURL();
+   57  					// set icon title to title of referring article
+   58: 					$iconTitleText = $iconUrl->getText();
+   59  				}
+   60  				$finalIcon['icon'] = $iconName;
+   61: 				$finalIcon['title'] = $iconTitleText;
+   62  				$iconsToAdd[] = $finalIcon;
+   63  			}
+```",1545174186,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Rename a lot of getters for consistency,"[x] OO.ui.BookletLayout.prototype.getPageName ➞ OO.ui.BookletLayout.prototype.get**Current**PageName https://gerrit.wikimedia.org/r/#/c/177799/
+
+[x] OO.ui.BookletLayout.prototype.getClosestPage ➞ OO.ui.BookletLayout.prototype.**find**ClosestPage
+** [x] Deprecate https://gerrit.wikimedia.org/r/#/c/375935/
+** [x] Fix https://gerrit.wikimedia.org/r/#/c/375937/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/375936/
+
+[x] OO.ui.SelectWidget.prototype.getTargetItem ➞ OO.ui.SelectWidget.prototype.**find**TargetItem https://gerrit.wikimedia.org/r/#/c/375938/
+
+[x] OO.ui.SelectWidget.prototype.getFirstSelectableItem ➞ OO.ui.SelectWidget.prototype.**find**FirstSelectableItem
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/376171/
+** [x] Fix
+*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/#/c/376172/
+*** [x] VE ➞ https://gerrit.wikimedia.org/r/#/c/376177/
+*** [x] VE extension ➞ https://gerrit.wikimedia.org/r/#/c/376175/
+*** [x] MediaWiki core ➞ https://gerrit.wikimedia.org/r/#/c/376176/
+*** [x] TemplateData extension ➞ https://gerrit.wikimedia.org/r/#/c/376174/
+** [x] Break ➞ https://gerrit.wikimedia.org/r/#/c/376173/
+
+[x] OO.ui.SelectWidget.prototype.getHighlightedItem ➞ OO.ui.SelectWidget.prototype.**find**HighlightedItem
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/376501
+** [x] Fix ➞ https://gerrit.wikimedia.org/r/376502
+** [x] Break ➞ https://gerrit.wikimedia.org/r/376503
+
+[x] OO.ui.SelectWidget.prototype.getRelativeSelectableItem ➞ OO.ui.SelectWidget.prototype.**find**RelativeSelectableItem
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/376183
+** [x] Fix
+*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/376184
+*** [x] Mediawiki core: RCFilter ➞ https://gerrit.wikimedia.org/r/376186
+** [x] Break ➞ https://gerrit.wikimedia.org/r/376185
+
+[x] OO.ui.ToolGroup.prototype.getTargetTool ➞ OO.ui.ToolGroup.prototype.**find**TargetTool https://gerrit.wikimedia.org/r/#/c/375940/
+
+[x] OO.ui.GroupElement.prototype.getItemFromData ➞ OO.ui.GroupElement.prototype.**find**ItemFromData
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398004/
+** [x] Fix 
+*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/#/c/398209/
+*** [x] ContentTranslation ➞ https://gerrit.wikimedia.org/r/#/c/398217/
+*** [x] AdvancedSearch ➞ https://gerrit.wikimedia.org/r/#/c/398223/
+*** [x] Echo ➞ https://gerrit.wikimedia.org/r/#/c/398224/
+*** [x] Flow ➞ https://gerrit.wikimedia.org/r/#/c/400466/
+*** [x] CentralNotice ➞ https://gerrit.wikimedia.org/r/#/c/400467/
+*** [x] TemplateData ➞ https://gerrit.wikimedia.org/r/#/c/400468/
+*** [x] VisualEditor ➞ https://gerrit.wikimedia.org/r/#/c/400470
+*** [x] VisualEditor-MediaWiki ➞ https://gerrit.wikimedia.org/r/#/c/400469/
+*** [x] MediaWiki ➞ https://gerrit.wikimedia.org/r/#/c/398221/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415227/
+
+[x] OO.ui.GroupElement.prototype.getItemsFromData ➞ OO.ui.GroupElement.prototype.**find**ItemsFromData
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398004/
+** [x] Fix
+*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/#/c/398209/
+*** [x] ContentTranslation ➞ https://gerrit.wikimedia.org/r/#/c/398217/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415227/
+
+[x] OO.ui.SelectWidget.prototype.getSelectedItem ➞ OO.ui.SelectWidget.prototype.**find**SelectedItem
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398005/
+** [x] Fix
+*** [x] OOUI: https://gerrit.wikimedia.org/r/#/c/403934/
+*** [x] {T184037}
+*** [x] {T184041} 
+*** [x] {T184040}
+*** [x] {T184039}
+*** [x] Kartographer: https://gerrit.wikimedia.org/r/#/c/404669/
+*** [x] CentralNotice: https://gerrit.wikimedia.org/r/#/c/414935/
+*** [x] CollaborationKit: https://gerrit.wikimedia.org/r/#/c/414936/
+*** [x] Math: https://gerrit.wikimedia.org/r/#/c/404671/
+*** [x] ContentTranslation: https://gerrit.wikimedia.org/r/414937
+*** [x] UploadWizard: https://gerrit.wikimedia.org/r/414942
+*** [x] ProofreadPage: https://gerrit.wikimedia.org/r/#/c/404673/
+*** [x] MultimediaViewer: https://gerrit.wikimedia.org/r/#/c/414943/
+*** [x] VE: https://gerrit.wikimedia.org/r/#/c/404667/
+*** [x] VE-MW: https://gerrit.wikimedia.org/r/#/c/404666/
+*** [x] Mediawiki core: https://gerrit.wikimedia.org/r/414944
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415229/
+
+[x] OO.ui.MultiselectWidget.prototype.getSelectedItems ➞ OO.ui.MultiselectWidget.prototype.**find**SelectedItems
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398006/
+** [x] Fix
+*** [x] Mediawiki core: https://gerrit.wikimedia.org/r/#/c/415224/
+*** [x] UploadWizard: https://gerrit.wikimedia.org/r/#/c/415225/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415231/
+
+[x] OO.ui.MultiselectWidget.prototype.getSelectedItemsData ➞ OO.ui.MultiselectWidget.prototype.**find**SelectedItemsData
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398006/
+** [x] Fix
+*** [x] UploadWizard: https://gerrit.wikimedia.org/r/#/c/415226/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415231/
+",1417634878,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_description,resolved
+Rename a lot of getters for consistency,Excellent work!,1525726664,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415227 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] GroupElement: Remove getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/415227]]",1525726268,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415231 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] MultiSelectWidget: Remove getSelectedItems and getSelectedItemsData
+
+[[https://gerrit.wikimedia.org/r/415231]]",1525726232,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415229 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/415229]]",1525726231,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415226 **merged** by jenkins-bot:
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItemsData instead of getSelectedItemsData
+
+[[https://gerrit.wikimedia.org/r/415226]]",1519928715,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415224 **merged** by jenkins-bot:
+[mediawiki/core@master] Use findSelectedItems instead of getSelectedItems
+
+[[https://gerrit.wikimedia.org/r/415224]]",1519862527,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415225 **merged** by jenkins-bot:
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItems instead of getSelectedItems
+
+[[https://gerrit.wikimedia.org/r/415225]]",1519861874,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415231 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] MultiSelectWidget: Remove getSelectedItems and getSelectedItemsData
+
+[[https://gerrit.wikimedia.org/r/415231]]",1519799131,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415229 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/415229]]",1519798953,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415227 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] GroupElement: Remove getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/415227]]",1519798385,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415226 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItemsData instead of getSelectedItemsData
+
+[[https://gerrit.wikimedia.org/r/415226]]",1519797741,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415225 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItems instead of getSelectedItems
+
+[[https://gerrit.wikimedia.org/r/415225]]",1519797536,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415224 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] Use findSelectedItems instead of getSelectedItems
+
+[[https://gerrit.wikimedia.org/r/415224]]",1519797222,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414935 **merged** by jenkins-bot:
+[mediawiki/extensions/CentralNotice@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414935]]",1519758949,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414944 **merged** by jenkins-bot:
+[mediawiki/core@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414944]]",1519758271,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414936 **merged** by jenkins-bot:
+[mediawiki/extensions/CollaborationKit@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414936]]",1519757512,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414937 **merged** by jenkins-bot:
+[mediawiki/extensions/ContentTranslation@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414937]]",1519757067,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414942 **merged** by jenkins-bot:
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414942]]",1519752092,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414943 **merged** by jenkins-bot:
+[mediawiki/extensions/MultimediaViewer@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414943]]",1519748620,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414944 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414944]]",1519711589,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414943 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/MultimediaViewer@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414943]]",1519711087,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414942 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414942]]",1519710546,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414937 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/ContentTranslation@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414937]]",1519709947,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414936 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/CollaborationKit@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414936]]",1519709660,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414935 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/CentralNotice@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414935]]",1519709383,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400467 **merged** by jenkins-bot:
+[mediawiki/extensions/CentralNotice@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400467]]
+",1517262540,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 404513 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (d5428e9b3)
+
+[[https://gerrit.wikimedia.org/r/404513]]
+",1516210175,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 404513 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (d5428e9b3)
+
+[[https://gerrit.wikimedia.org/r/404513]]
+",1516127047,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398224 **merged** by jenkins-bot:
+[mediawiki/extensions/Echo@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398224]]
+",1515634648,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398221 **merged** by jenkins-bot:
+[mediawiki/core@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/398221]]
+",1515616772,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398223 **merged** by jenkins-bot:
+[mediawiki/extensions/AdvancedSearch@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398223]]
+",1515616625,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398217 **merged** by jenkins-bot:
+[mediawiki/extensions/ContentTranslation@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398217]]
+",1515616624,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400469 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400469]]
+",1515614073,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400468 **merged** by jenkins-bot:
+[mediawiki/extensions/TemplateData@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400468]]
+",1515613877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400466 **merged** by jenkins-bot:
+[mediawiki/extensions/Flow@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400466]]
+",1515613876,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400470 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400470]]
+",1515613572,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398006 **merged** by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] MultiSelectWidget: Rename getters
+
+[[https://gerrit.wikimedia.org/r/398006]]
+",1515014388,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398005 **merged** by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getSelectedItem to findSelectedItem
+
+[[https://gerrit.wikimedia.org/r/398005]]
+",1515014345,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400470 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[VisualEditor/VisualEditor@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400470]]
+",1514442501,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400469 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/VisualEditor@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400469]]
+",1514442228,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400468 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/TemplateData@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400468]]
+",1514441803,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400467 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/CentralNotice@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400467]]
+",1514441613,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400466 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/Flow@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400466]]
+",1514441206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398209 **merged** by jenkins-bot:
+[oojs/ui@master] Use findItem(s)FromData instead of getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398209]]
+",1513362323,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398004 **merged** by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] GroupElement: Rename getItem(s)FromData to findItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398004]]
+",1513361286,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398224 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/Echo@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398224]]
+",1513238791,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398223 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/AdvancedSearch@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398223]]
+",1513238413,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398221 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/398221]]
+",1513237626,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398217 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/ContentTranslation@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398217]]
+",1513236102,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398209 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Use findItem(s)FromData instead of getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398209]]
+",1513230421,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398006 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] MultiSelectWidget: Rename getters
+
+[[https://gerrit.wikimedia.org/r/398006]]
+",1513149733,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398005 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getSelectedItem to findSelectedItem
+
+[[https://gerrit.wikimedia.org/r/398005]]
+",1513149172,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398004 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] GroupElement: Rename getItemFromData to findItemFromData
+
+[[https://gerrit.wikimedia.org/r/398004]]
+",1513148429,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"> OO.ui.SelectWidget.prototype.getSelectedItem ➞ OO.ui.SelectWidget.prototype.findSelectedItem
+
+We should also change this for `MultiSelectWidget` (not just `SelectWidget`) and thus `getSelectedItemsData`.",1513147727,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,">>! In T76630#3833381, @Volker_E wrote:
+> @Prtksxna Yes, please. Also `getSelectedItemsData` ➞ `findSelectedItemsData`.
+
+Yes, thanks, just writing a comment about that.",1513147592,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,">>! In T76630#3833381, @Volker_E wrote:
+> @Prtksxna Yes, please. Also `getSelectedItemsData` ➞ `findSelectedItemsData`.
+
+Yes, that one is already filed in the description.",1513147493,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"@Prtksxna Yes, please. Also `getSelectedItemsData` ➞ `findSelectedItemsData`.",1513147439,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"> OO.ui.GroupElement.prototype.getItemFromData ➞ OO.ui.GroupElement.prototype.findItemFromData
+
+Just confirming, we should also change the plural, OO.ui.GroupElement.prototype.getItem**s**FromData ➞ OO.ui.GroupElement.prototype**.find**Item**s**FromData",1513147274,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"@Prtksxna Would you please care about the two last open items here, as well? Want to get this in for v0.25.0.",1513122808,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376173 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376173]]
+",1513122104,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376185 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376185]]
+",1513113113,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375936 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] Remove BookletLayout#getClosestPage
+
+[[https://gerrit.wikimedia.org/r/375936]]
+",1513112666,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376503 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376503]]
+",1513112664,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376186 merged by jenkins-bot:
+[mediawiki/core@master] RCFilters: Use findRelativeSelectableItem instead of getRelativeSelectableitem
+
+[[https://gerrit.wikimedia.org/r/376186]]
+",1506018081,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376176 merged by jenkins-bot:
+[mediawiki/core@master] apisandbox.js: Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376176]]
+",1506017666,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376174 merged by jenkins-bot:
+[mediawiki/extensions/TemplateData@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376174]]
+",1506017591,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376175 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376175]]
+",1506017590,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376177 merged by jenkins-bot:
+[VisualEditor/VisualEditor@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376177]]
+",1506017237,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376184 merged by jenkins-bot:
+[oojs/ui@master] Use findRelativeSelectableItem instead of getRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376184]]
+",1505852457,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376183 merged by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getRelativeSelectableItem to findRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376183]]
+",1505852456,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376172 merged by Prtksxna:
+[oojs/ui@master] Use findFirstSelectableItem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376172]]
+",1505391686,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376502 merged by jenkins-bot:
+[oojs/ui@master] Use findHighlightedItem instead of getHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376502]]
+",1504798452,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376501 merged by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getHighlightedItem to findHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376501]]
+",1504798356,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376171 merged by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getFirstSelectableItem to findFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376171]]
+",1504798320,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376503 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376503]]
+",1504785155,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376502 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Use findHighlightedItem instead of getHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376502]]
+",1504785154,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376501 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getHighlightedItem to findHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376501]]
+",1504785153,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376182 abandoned by Prtksxna:
+[BREAKING CHANGE] SelectWidget: Rename getHighlightedItem to findHighlightedItem
+
+Reason:
+> As these are public methods, we should deprecate them even if they're unused in git. They might be used on wiki, or by third parties.
+
+Yeah makes sense. Abandoning this because its easier for me :/
+
+[[https://gerrit.wikimedia.org/r/376182]]",1504784613,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376186 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] RCFilters: Use findRelativeSelectableItem instead of getRelativeSelectableitem
+
+[[https://gerrit.wikimedia.org/r/376186]]
+",1504683857,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376185 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376185]]
+",1504683834,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376184 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Use findRelativeSelectableItem instead of getRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376184]]
+",1504683833,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376183 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getRelativeSelectableItem to findRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376183]]
+",1504683832,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"> OO.ui.SelectWidget.prototype.getHighlightedItem ➞ OO.ui.SelectWidget.prototype.**find**HighlightedItem
+
+There is a `getHighlightedItem` being used in #mediawiki-recent-changes but it isn't related to this change and doesn't use `OO.ui.SelectWidget`. Could someone please confirm my observation?",1504682251,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"> OO.ui.SelectWidget.prototype.getHighlightedItem ➞ OO.ui.SelectWidget.prototype.**find**HighlightedItem
+
+There is a `getHighlightedItem` being used in #mediawiki-recent-changes but it isn't related to this change and doesn't use `OO.ui.SelectWidget`.",1504682001,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376182 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] SelectWidget: Rename getHighlightedItem to findHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376182]]
+",1504681933,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376177 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[VisualEditor/VisualEditor@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376177]]
+",1504676888,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376176 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] apisandbox.js: Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376176]]
+",1504676878,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376175 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/VisualEditor@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376175]]
+",1504676871,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376174 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/TemplateData@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376174]]
+",1504676868,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376173 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376173]]
+",1504676858,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376172 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Use findFirstSelectableItem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376172]]
+",1504676857,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376171 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getFirstSelectableItem to findFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376171]]
+",1504676856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375937 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWTemplateDialog: BookletLayout: Use findClosestPage instead of getClosestPage
+
+[[https://gerrit.wikimedia.org/r/375937]]
+",1504658314,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375935 merged by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] BookletLayout: Rename getClosestPage to findClosestPage
+
+[[https://gerrit.wikimedia.org/r/375935]]
+",1504633553,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375938 merged by jenkins-bot:
+[oojs/ui@master] SelectFileWidget: Rename getTargetItem to findTargetItem
+
+[[https://gerrit.wikimedia.org/r/375938]]
+",1504627531,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375940 merged by jenkins-bot:
+[oojs/ui@master] Toolgroup: Rename getTargetTool to findTargetTool
+
+[[https://gerrit.wikimedia.org/r/375940]]
+",1504627530,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375940 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Toolgroup: Rename getTargetTool to findTargetTool
+
+[[https://gerrit.wikimedia.org/r/375940]]
+",1504579758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375938 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] SelectFileWidget: Rename getTargetItem to findTargetItem
+
+[[https://gerrit.wikimedia.org/r/375938]]
+",1504579127,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375937 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/VisualEditor@master] MWTemplateDialog: BookletLayout: Use findClosestPage instead of getClosestPage
+
+[[https://gerrit.wikimedia.org/r/375937]]
+",1504577626,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375936 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] Remove BookletLayout#getClosestPage
+
+[[https://gerrit.wikimedia.org/r/375936]]
+",1504577519,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375935 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] BookletLayout: Rename getClosestPage to findClosestPage
+
+[[https://gerrit.wikimedia.org/r/375935]]
+",1504577518,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,I don't see anything stalled here.,1479485224,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"I don't really see the value in changing this, sorry. (But won't oppose if someone does it, I guess.)",1424183629,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,Ping. What's happening with this?,1424129889,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"The idea was simply that there were three classes of getters.
+
+1. Get a single thing that is always there - like input.getValue()
+2. Get a single thing that may or may not be there - like booklet.getOutline()
+3. Get one of the 0+ items inside something - like select.getItemFromData()
+
+I was feeling like there were too many cases where class 2 and 3 getters were being chained, which causes problems since they may or may return null. Since the method names don't hint at whether they are safe to chain - and in the case of class 1 they are perfectly safe to chain, code that is dangerous is very easy to mistake for code that is safe.
+
+I don't have a solution for class 2 yet. I'm very interested in ideas.
+
+The solution I came up with for class 3 is to use find instead of get. I think this hints at the method being unsafe to chain, makes the code clearer that you are asking for one of 0+ items, and is a very simple change in the code.",1418162918,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 177799 merged by jenkins-bot:
+[BREAKING CHANGE] Rename BookletLayout#getPageName → #getCurrentPageName
+
+[[https://gerrit.wikimedia.org/r/177799]]",1417825555,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,But why?! :),1417825403,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,Consistency with what Trevor wants OOUI to look like. :-),1417805658,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Hm.. consistency with what? At first glance I'd guess that a ""get"" method returns a reference or value that is computed or gathered on-demand. It typically takes either no argument or a unique identifier for a single item. A ""find"" method on the other hand seems different, maybe something that might takes a search query and return varying results (0 or more). ack-grep found 0 matches for `prototype.find` in oojs/ui, and 2 matches in lib/ve/*.",1417791056,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"The BookletLayout#getPageName → #getCurrentPageName one was an obvious improvement and is entirely painless, but I would like to hear the rationale for get→find replacements before I spend tons of time replacing tons of usages across the repos.",1417790475,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 177799 had a related patch set uploaded (by Bartosz Dziewoński):
+[BREAKING CHANGE] Rename BookletLayout#getPageName → #getCurrentPageName
+
+[[https://gerrit.wikimedia.org/r/177799]]
+
+#patch-for-review",1417790387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+K3. Run Flow tests with Parsoid on Jenkins,"@EBernhardson said that they are currently run with wikitext (without Parsoid).  It would be good to run them with Parsoid (since that's our main backend) in addition to or instead of wikitext.
+
+--------------------------
+**Trello card**: [[ https://trello.com/c/YpgazY2B/701-k3-run-flow-unit-tests-with-parsoid-3 | YpgazY2B ]]",1417606214,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-rtdocuudreaisizzfzfc,task_description,open
+K3. Run Flow tests with Parsoid on Jenkins,"I think @Ebernhardson changed most/all of these to use a fixture (mock output for given input) if Parsoid is not available.  We'd still like the real thing, but that should help.",1424461437,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-rtdocuudreaisizzfzfc,task_subcomment,NA
+K3. Run Flow tests with Parsoid on Jenkins,"@hashar: How far of do you think those proposed ideas are?
+Would it make sense to contact an existing Parsoid, until we can properly clone & run it in isolation?
+We're not in a huge rush, but it would be nice to have our tests run with Parsoid.
+
+
+Possible implementation suggestion, copied from [Trello](https://trello.com/c/YpgazY2B/701-k3-run-flow-unit-tests-with-parsoid-3):
+
+http://www.mediawiki.org/wiki/Parsoid/API says ""A production version of Parsoid on the Wikimedia cluster can be accessed at http://parsoid-lb.eqiad.wikimedia.org/"", so I guess that one would be good to use.
+
+I'm no Jenkins expert, but I think we should add a build step ""Execute shell"" with the following command on https://integration.wikimedia.org/ci/view/Extensions/job/mwext-Flow-testextension/configure - this would override the default Parsoid settings:
+
+```
+# Load context (namely: MW_INSTALL_PATH)
+. ""/srv/deployment/integration/slave-scripts/bin/mw-set-env.sh""
+
+# Configure Parsoid
+echo -e \
+ ""<?php\n\$wgFlowParsoidURL = 'http://parsoid-lb.eqiad.wikimedia.org/';\n""\
+ ""\$wgFlowParsoidPrefix = 'enwiki';\n""\
+ ""\$wgFlowParsoidTimeout = 100;\n"" >> ""$MW_INSTALL_PATH/LocalSettings.php""
+```",1421168395,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-rtdocuudreaisizzfzfc,task_subcomment,NA
+K3. Run Flow tests with Parsoid on Jenkins,"So i know that doing this ""correct"" is of big benefit, but could we have most of the benefits now just by setting Flow config to point to already existing parsoid in labs? Without having to install or boot a parsoid instance the changes required become trivial, as long as the jenkins runners have network access to the labs machines.",1417818190,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-rtdocuudreaisizzfzfc,task_subcomment,NA
+K3. Run Flow tests with Parsoid on Jenkins,"Copying @hashar's comment on Trello:
+
+Sorry for the rather long delay. To run tests with Parsoid as a backend, we would need a job that:
+
+  - spawn a Parsoid daemon like we do for some Parsoid integration tests
+  - setup MediaWiki behind a web server which we do for qunit tests
+
+The mwext-Flow-testextension job execute the PHPUnit test suite which combines unit tests for the Flow function as well as integration tests against mediawiki/core.
+
+It is totally doable to spawn a Parsoid daemon and run whatever tests you want. That being said, I would prefer to avoid rushing a solution that would match just the Flow extension in favor of a system that would work for other use cases (such as VisualEditor).
+
+During the summer, I worked on a set of utilities that would let us clone core + vendor + extensions and run them all together with the appropriate patches/branches checked out. That will yield a state of code to be tested and is subject of an RFC: https://www.mediawiki.org/wiki/RFC/Extensions_continuous_integration
+
+Once we have that stack of code available, everything is loaded via include() and we will run: the PHPUnit test suite the qunit page
+
+That will supersede all the testextension and extension-qunit jobs in favor of a two jobs that are used by all repositories.
+
+We can come up with a third job that would have a bit more backend configured such as ElasticSearch or Parsoid. But that will take a bit more time since I want the other two jobs to be setup first.
+
+As I understand, running Flow tests with Parsoid is more of a nice to have feature than a breaker and I guess it can wait a bit. In short: yes, but a bit later and on a wider scale :-)
+
+I am subscribed to this Trello card so we can keep the discussion here 8-)",1417633169,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-rtdocuudreaisizzfzfc,task_subcomment,NA
+Explore performance gains from progressive (JIT?) de-alienation of content types in VisualEditor,"See {T54365} for the same idea, but for content blocks.",1417567272,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yja5lvncvpyih4flmthe,task_description,open
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Somehow(?) load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document.
+
+Will probably need {T49344} for the document splitting.
+",1417566671,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_description,resolved
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","I think the testing of this re-factor is pretty much done. I'm going to go ahead and mark it as verified. If we find more bugs as part of more integration testing, we will create new bugs. At least this one won't have to sit around under QA column. ",1551990955,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Currently this  is disabled behind a feature flag, so QA should just check that editing/section editing is unaffected by the code refactor. We will do a separate QA for the feature itself when we get around to enabling it by default.",1550691051,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 440809 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Support only surfacing part of the document
+
+[[https://gerrit.wikimedia.org/r/440809]]",1550689592,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 489319 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (c4d559b29)
+
+[[https://gerrit.wikimedia.org/r/489319]]",1549761425,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 489319 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (b629aa8b1)
+
+[[https://gerrit.wikimedia.org/r/489319]]",1549660398,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 433753 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Support only surfacing part of the document
+
+[[https://gerrit.wikimedia.org/r/433753]]",1549655229,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 440809 had a related patch set uploaded (by Divec; owner: Divec):
+[mediawiki/extensions/VisualEditor@master] WIP Support only surfacing part of the document
+
+[[https://gerrit.wikimedia.org/r/440809]]",1529298219,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","As well as the approach in https://gerrit.wikimedia.org/r/433753 , we should also consider the following alternative:
+- A class provides the LinearData interface on a live slice of the linear data (performing offset translation and bounds checking)
+- ve.dm.Document builds on top of that class
+That approach would more robustly prevent access outside the slice. But one drawback would be apparent dangling references in the slice.",1526802428,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 433753 had a related patch set uploaded (by Divec; owner: Divec):
+[VisualEditor/VisualEditor@master] WIP POC: Support only surfacing part of the document
+
+[[https://gerrit.wikimedia.org/r/433753]]",1526802127,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","We already support fetching specific HTML sections by ID in the REST API (see https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_html_title), but until consistent <section> wrapping with a sensible granularity & perhaps a predictable section ID for the lead section are implemented in Parsoid (T114072), this is not as useful in practice as it could be.
+
+Behind the scenes, the section-by-id retrieval is currently based on byte offset mappings provided by Parsoid and stored in Cassandra. Given the performance we see in [web-html-stream](https://github.com/wikimedia/web-html-stream) (the library @cscott mentioned), we could however get rid of the explicit section offsets stored in cassandra, and do the matching / extraction dynamically instead.
+
+Apart from the server side section retrieval API, clients will need to discover the page outline & section ids. The reading team has already been doing some section loading in apps & mobile web. This is not yet fully general, but is moving in that direction. Metadata about sections is exposed in [the page summary end point](https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_summary_title). Another source of metadata is the [lead section end point](https://en.wikipedia.org/api/rest_v1/#!/Mobile/get_page_mobile_sections_lead_title_revision) used by apps, which additionally includes the lead section content itself. Eventually, I hope that we will have standard <section>s in Parsoid output, and can refer to those in these summary end points for easy section retrieval.",1504895813,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","We've had a somewhat-related discussion in Parsoid-land about being able to fetch only subsets of the DOM tree from restbase.  The idea there was that restbase would do the actual subtree extraction from the full document, using the fancy fast regexp-based stuff that @gwicke wrote.  But you'd also want to extract and fetch data-mw and data-parsoid for the same subtree.  We've talked about tree-structuring the data-mw and data-parsoid JSON blobs to make that possible (using a variant of @gwicke's HTML regexp technique), but I'm not sure we've actually implemented that yet.",1504891814,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+VisualEditor image resize icon must be flipped and moved to the opposite edge for RTL wikis,"The VisualEditor image resize icon must appear on the inner side of the page (inner in relation to the page). For RTL now it appears on the outer edge, which makes it not really usable. The direction of the arrow heads must be flipped, too.",1417526272,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-np6rbo55hknbpzfqqpzh,task_description,open
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","This is valid HTML:
+```
+<blockquote>
+<p>
+Foo
+</p>
+<p>
+Bar
+</p>
+</blockquote>
+```
+But when such structure is edited in VE, the inner paragraphs get alienated.
+//*sighs*//
+
+>>! In T154231, @dchan wrote:
+> At present, BlockquoteNode behaves like a ContentBranchNode ; it should not.
+> 
+> Right now, ve.ce.BlockquoteNode extends ve.ce.ContentBranchNode, but ve.dm.BlockquoteNode extends ve.dm.BranchNode . I would say BranchNode is the correct parent, because HTML blockquote elements can contain flow content such as paragraph elements (see https://html.spec.whatwg.org/multipage/semantics.html#the-blockquote-element ).
+> 
+> If however there's some special weird reason to treat BlockquoteNode as a ContentBranchNode, then I'll implement that instead and document the special weird reason.
+
+>>! In T154231#2913587, @Jdforrester-WMF wrote:
+> ISTR there is — or at least, was — a solid reason for doing this. But I don't recall at all what it was.
+
+>>! In T154231#4000786, @matmarex wrote:
+> It seems the reason was that we treat it as a top-level block element, like paragraphs or heading.
+> 
+>>>! @Esanders in https://gerrit.wikimedia.org/r/#/c/329448/
+>> This is probably correct but it means we have to come up with a new tool for inserting block quote, as it is currently treated as a CBN conversion in the format dropdown. I think we did it that way because most blockquotes are only one paragraph.
+>> 
+>> Alternatively, we could go the other way and make it fully ContentBranchNode, at least for the time being.
+> 
+> It was actually changed to be fully ContentBranchNode in 94dbb244dd.
+
+",1417481643,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_description,resolved
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","There is formal QA approval on T209162… I think we can skip the rest, things seem to work fine.",1559171278,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","QA note: please also check the parent tasks, I think they should all be resolved by the fixes here:
+
+* {T120827}
+* {T54398}
+* {T86794}
+* {T209162}",1556049031,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",">>! In T76426#5086359, @matmarex wrote:
+> The patches now only resolve the technical issue of multi-paragraph blockquotes not being editable. I'll file a separate task to consider the toolbar changes later.
+
+I filed: {T221692}",1556048047,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475962 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (7cd15cfe9)
+
+[[https://gerrit.wikimedia.org/r/475962]]",1556033496,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475961 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Make blockquote a non-content branch node
+
+[[https://gerrit.wikimedia.org/r/475961]]",1555695456,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",The patches now only resolve the technical issue of multi-paragraph blockquotes not being editable. I'll file a separate task to consider the toolbar changes later.,1554405157,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475962 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] [PULLTHROUGH] Update stuff for making blockquote a non-content branch node
+
+[[https://gerrit.wikimedia.org/r/475962]]",1554404541,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475961 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[VisualEditor/VisualEditor@master] Make blockquote a non-content branch node, update tools and stuff accordingly
+
+[[https://gerrit.wikimedia.org/r/475961]]",1554404537,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",moving this to Blocked/Waiting because I suspect that the work in https://phabricator.wikimedia.org/T211255 will impact the decisions on this.,1553002269,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",Process question - is this something that we should focus on in conjunction with T211255?,1549901114,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","An issue I'd careful with is putting the blockquotes underneath “list”. It's often close to the lists in other interfaces, but I wonder if people will actually assume or find it there. I wouldn't. Point taken, that it might be one of the least used features anyways.",1547510447,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","To the icon: Blockquote command is basically done in every Rich Text Editor GUI (email/web) with the beginning (English!) quotes “ that we use for “Cite” function in VE. 
+Gmail as example {F27892598 size=thumb}
+
+We've prob locked ourselves out for using the same icons for those two different use cases, although I wonder how many new editors are confused by finding a functionality that the assume to know resulting in a different action.
+",1547510262,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",">>! In T76426#4878309, @iamjessklein wrote:
+> Re: changing the location of blockquotes: I know that @cmadeo did some kind of audit when she was look at editing app UIs. Carolyn - did you find the block quotes functionality located in other places in the UI? (Other than nested under the dropdown for paragraph styles). I'd like to be a bit mindful before moving this because we are trying to maintain consistency as much as possible across the different interfaces. 
+
+Unfortunately block quote was not a common formatting option:
+- The Notion app places block quotes in with both what we consider paragraph stylings and list styles
+- The Medium app has block quotes as it's own toolbar level option (eg. not related to paragraph stylings)
+
+Currently on the iOS app we're following suit with how VE is handling this, but I'm happy to move this out of paragraph styling if you all come to a different conclusion. 
+
+Not based on any testing, but I could see this falling under text stylings (same as computer code), but it does seem like block quote and preformatted text should be grouped together. Is this issue (alienated paragraphs) occurring with preformatted text from VE? ",1547493537,PHID-USER-rblpzor23smiqjmaezyw,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Re: changing the location of blockquotes: I know that @cmadeo did some kind of audit when she was look at editing app UIs. Carolyn - did you find the blockquotes functionality located in other places in the UI? (Other than nested under the dropdown for paragraph styles). I'd like to be a bit mindful before moving this because we are trying to maintain consistency as much as possible across the different interfaces. 
+
+Re: identifying an appropriate icon for blockquotes: In terms of icon, most folks have it as quotes (even phabricator). Medium has an interaction where you click the button multiple times and cycle through the different options for quote formatting, but I find that to be a touch unintuitive. I'm not sure what to use in terms of the icon though, I suspect that if we have multiple quote icons it could begin to complicate the issue. cc/ @Volker_E ",1547490322,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Copying replies from gerrit:
+
+> Should the tool remain in the ""Format"" menu? Probably not, ...
+Agreed.
+
+> Should Ctrl+8 remain as the keyboard shortcut? ...
+Meh. We have ctrl+shift+5 for strikethrough, and we short on available shortcuts
+
+> Should the tool have an icon? ...
+Yeah - ""quotes"" is fine for now - if we don't like the duplication we can fix it later.
+
+> Should we have some styles that make it easier to tell where a blockquote begins and ends...
+Possibly - they should be subtle/greyed out so it's clear they aren't part of the read mode styling, a bit like how we have default table cell styling. Some wikis do have blockquote styling though.",1543334481,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","cc @iamjessklein 
+
+The patch proposes moving the tool from ""Format"" to ""Structure"":
+| {F27317563}| {F27317557} 
+…and some interesting changes to how the tool behaves – blockquotes can now be nested in other nodes (e.g. lists) and have other nodes nested inside them (e.g. also lists, but more simply, paragraphs and headings etc.). They can also be nested in each other.
+
+Open questions:
+* Should the tool remain in the ""Format"" menu? Probably not, as that
+  would allow two items in that menu to be active at the same time,
+  which looks silly.
+* Should Ctrl+8 remain as the keyboard shortcut? It doesn't really
+  make sense anymore now that this is not the 8th item in the ""Format""
+  menu.
+* Should the tool have an icon? There is space for one now. I wanted
+  to use 'quotes', but it has been usurped by Citoid.
+* Should we have some styles that make it easier to tell where a
+  blockquote begins and ends, especially in case the user inserts
+  multiple next to each other?
+",1543307404,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475962 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] Update stuff for making blockquote a non-content branch node
+
+[[https://gerrit.wikimedia.org/r/475962]]",1543306862,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475961 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[VisualEditor/VisualEditor@master] Make blockquote a non-content branch node, update tools and stuff accordingly
+
+[[https://gerrit.wikimedia.org/r/475961]]",1543306847,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",This has become a priority because of {T209162}.,1543305873,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",We can resurrect https://gerrit.wikimedia.org/r/329448 if we provide a tool for blockquote insertion,1519655235,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 329448 abandoned by Divec:
+Make BlockquoteNode fully non-ContentBranchNode
+
+Reason:
+We went the opposite way (fully ContentBranchNode) in 94dbb244dd
+
+[[https://gerrit.wikimedia.org/r/329448]]",1519645073,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 329448 had a related patch set uploaded (by Bartosz Dziewoński; owner: Divec):
+[VisualEditor/VisualEditor@master] Make BlockquoteNode fully non-ContentBranchNode
+
+[[https://gerrit.wikimedia.org/r/329448]]",1519644702,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",">>! In T76426#801853, @Whatamidoing-WMF wrote:
+> What is a CBN?
+
+Content branch node.",1417540280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",What is a CBN?,1417540133,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+New search interface for link dialogue,"As a new editor I want to see more information about pages so that I can choose the correct 1 to link to.
+
+Problem: The existing search interface doesn't look like a list of articles on Wikipedia. 
+Based on usability testing, this is rated a 3 - Major usability problem: important to fix, so should be given high priority.
+https://www.mediawiki.org/wiki/VisualEditor/Usability#Creating_a_link
+
+View click-through prototype here http://invis.io/NP2TOI4GU
+
+{F34278}
+
+Title area of dialogue shows Link icon, ""Link to page"" and ""External link"". Clicking External link will take user to T76398
+
+The search field will be filled with the text the user has selected to link.
+
+The search items show:
+Image thumbnail, article title, wikidata description
+Article icon if no lead image
+Indicate Redirect to [[article]] with redirect icon
+Indicate disambiguation page with its icon
+Empty page icon if redlink
+
+",1417474573,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-llwgzv3tlimidw6znewt,task_description,resolved
+New search interface for link dialogue,"Based on usability testing, this is rated a 3 - Major usability problem: important to fix, so should be given high priority.
+Summary: Users don't realize that the link's search results are actual pages on Wikipedia.
+2 out of 5 tested were able to link to a page with a title different from link text. 
+https://www.mediawiki.org/wiki/VisualEditor/Usability#Creating_a_link
+",1429124247,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-llwgzv3tlimidw6znewt,task_subcomment,NA
+New search interface for link dialogue,I have a WIP patch for a page selector widget at https://gerrit.wikimedia.org/r/#/c/195240/ - in case it helps.,1427167676,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-llwgzv3tlimidw6znewt,task_subcomment,NA
+New search interface for link dialogue,"Content Translation also need this component to enhance our link adaptation features, also for providing a better source article selector.
+
+Is this currently planned as  a reusable component so that other projects can use it? Is there any rough timeline for implementation?",1425883552,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-llwgzv3tlimidw6znewt,task_subcomment,NA
+New search interface for link dialogue,"For the option to create a red link, we may consider a language more related to the user action. So instead of ""Page does not exist yet"", we can label that option as ""Link as a missing page"" or something along those lines.",1424687811,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-llwgzv3tlimidw6znewt,task_subcomment,NA
+Incorrect Parsoid output for image wrapped in bold and paragraph,"For this wikitext: 
+```
+<p>'''[[File:Wiki.png|thumb]]'''</p>
+```
+Parsoid produces HTMLDOM that has bold tag inside anchor tag inside figure tag - which is not consistent with https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec
+```
+<!DOCTYPE html>
+<html prefix=""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/""><head prefix=""mwr: http://en.wikipedia.org/wiki/Special:Redirect/""><meta property=""mw:articleNamespace"" content=""0""/><meta property=""mw:parsoidVersion"" content=""0""/><link rel=""dc:isVersionOf"" href=""//en.wikipedia.org/wiki/Main%20Page""/><title></title><base href=""//en.wikipedia.org/wiki/""/><link rel=""stylesheet"" href=""//en.wikipedia.org/w/load.php?modules=mediawiki.legacy.commonPrint,shared|mediawiki.skinning.elements|mediawiki.skinning.content|mediawiki.skinning.interface|skins.vector.styles|site|mediawiki.skinning.content.parsoid&amp;only=styles&amp;debug=true&amp;skin=vector""/></head><body data-parsoid='{""dsr"":[0,37,0,0]}' lang=""en"" class=""mw-content-ltr sitedir-ltr ltr mw-body mw-body-content mediawiki"" dir=""ltr""><p data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""dsr"":[0,6,3,0]}'><b data-parsoid='{""autoInsertedEnd"":true,""dsr"":[3,6,3,0]}'></b></p><figure class=""mw-default-size"" typeof=""mw:Image/Thumb"" data-parsoid='{""optList"":[{""ck"":""thumbnail"",""ak"":""thumb""}],""dsr"":[6,29,2,2]}'><a href=""./File:Wiki.png"" data-parsoid='{""a"":{""href"":""./File:Wiki.png""},""sa"":{},""dsr"":[8,27,null,null]}'><b data-parsoid='{""tsr"":null,""autoInsertedEnd"":true,""autoInsertedStart"":true}'><img resource=""./File:Wiki.png"" src=""//upload.wikimedia.org/wikipedia/en/b/bc/Wiki.png"" height=""155"" width=""135"" data-parsoid='{""a"":{""resource"":""./File:Wiki.png"",""height"":""155"",""width"":""135""},""sa"":{""resource"":""File:Wiki.png""}}'/></b></a></figure><p data-parsoid='{""autoInsertedStart"":true,""stx"":""html"",""dsr"":[32,36,0,null]}'></p>
+</body></html>
+```
+It breaks rendering for such wikitext in VisualEditor.",1417463326,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-2krxsenupth53kalib2f,task_description,resolved
+Incorrect Parsoid output for image wrapped in bold and paragraph,This should now be fixed in latest master. New code will be deployed to production on Monday. Please verify and reopen if not fixed.,1438291931,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2krxsenupth53kalib2f,task_subcomment,NA
+Incorrect Parsoid output for image wrapped in bold and paragraph,"This is a variation of T70395  where the paragraph tags are present as HTML tags in the wikitext rather than being added by the paragraph wrapper.
+
+```a
+
+'''[[File:Wiki.png|thumb]]'''
+
+b```
+
+renders properly. So, the fixes for T70395 need to be expanded to deal with HTML <p> tags as well.",1417514118,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2krxsenupth53kalib2f,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"NOTE: This Google Summer of Code project has been completed successfully. Thank you @tinaj1234 for your contributions, and thank you @01tonythomas for your technical mentoring. This team has worked very well so far!
+
+For details, read {T109288}.
+
+The work continues at {T110170}. As always, your feedback and contributions are welcome. This is not an internship project anymore; patches are very welcome.  :)
+
+== Newsletter extension ==
+
+An extension allowing publishers to create newsletters and announce new issues, and allowing users to browse and subscribe to newsletters.
+
+A #Google-Summer-of-Code-2015 project lead by @tinaj1234, mentored by @01tonythomas and @qgil.
+
+Currently working on {T99784} and blockers.
+
+Weekly reports: T100997
+Weekly meetings: every [[ http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150605T1030 | Thursday at 10:30 UTC ]] (4pm IST, 12:30 CEST, 3:30 PST) in `#wikimedia-ect` IRC. 
+URL of web proxy of Labs instance where development takes place : http://newsletter-test.wmflabs.org/
+
+== Plan ==
+
+=== Readers ===
+
+* **A catalog of newsletters in one multilingual wiki** (Meta). Let's start defining a single translatable location to find all the newsletters. Meta is the logical choice. No matter which project the newsletter authors come from, all of them would create and organize their newsletters in a common location.
+* Easy subscription. As a logged-in user, click a button. As anonymous user, log in or create an account. (Ideally just entering an email address would work too, with confirmation). Question: should an email address in your profile be required? Can this be checked? Echo probably has solved this.
+* A notification is received when a new issue is published. Notifications are handled via Echo, and therefore they can be received via web or email according to user preferences.
+* Easy to unsubscribe. As a logged-in user, click a button. Accessing a URL from notifications should unsubscribe you as well, after confirmation.
+* Usernames and emails of subscribes should be kept private. The number of users subscribed to a newsletter would be public (and eventually used to promote popular newsletters).
+
+=== Publishers ===
+
+* A process defining the conditions in which a newsletter can be created, featured, demoted, closed (actions that might imply database changes). Just a basic framework to promote best practices and prevent abuse.
+* Once a newsletter is created, maintaining the content (homepage, subpages) could be done in a plain wiki way for creating pages, watching, editing, reverting, protecting if needed... New content is in practice a draft, since it hasn't been announced to the subscribers. Whoever wants to watch changes can read the drafts and get involved.
+* Once a new issue (a page) is ready, the owners of the newsletter send a notification. This requires special permissions.
+
+**Permissions**
+Any autoconfirmed user can become a publisher - create newsletters, announce issues, manage newsletters because of two particular reasons ( quoting Quim ):
+  # Autoconfirmed users can create newsletter pages and issues anyway (even anonymous can).
+  # Even if a publisher were to cause any kind of damage it will affect popularity of their newsletters as well. The extension takes care of subscriptions to the newsletter and notifications from newsletters and hence the creation of newsletters and issues are external to our extension.
+=== Newsletters ===
+A newsletter generally has one or more of the following properties (some newsletters have more of these than others):
+
+* Home page: a page that contains information about the newsletter and what it contains
+* Current issue page: self-explanatory
+* Archive pages: past editions of the newsletter that were previously published
+* Authors / Editors: a group of people that are allowed and/or expected to contribute content
+* Publishers: a group of people that are allowed to finalize an edition and publish it to readers
+
+Most likely, showing a user (on the preferences page mentioned above) a link to the home page, a description of the newsletter, and maybe a link to the current issue and archive pages would be useful.
+
+As mentioned in a comment below, it would probably be best to shift management of authors and editors to the existing page protection feature, i.e., if the newsletter really needs to be protected from unauthorized editing, make a restriction level and assign authors the necessary permission. Publishers would probably need separate management, and would probably be maintained in the same interface that information about the newsletter itself is maintained.
+
+===Backend===
+Check this Etherpad entry on discussions with hoo: https://etherpad.wikimedia.org/p/newsletterExtension
+While discussing with other developers, we realized there are two options for the extension's backend architecture - either use Contenthandlers or use Database( sql tables ). As of now while we prepare the patches for MVP, the database approach is taken. To choose the best for the extension out of all available options at it's earliest stages of development would be the apt thing to do, hence opening up this section for further discussions.
+
+=== See also ===
+
+* https://www.mediawiki.org/wiki/Extension:Newsletter
+* https://meta.wikimedia.org/wiki/Grants:IdeaLab/Newsletter_extension_for_MediaWiki
+
+===Proposed Schedule===
+
+| **Tasks to be completed **|**Timeline**|**Remarks**|
+|Create Wikimedia Labs project, create instance, community bonding| 28/03/15 - 30/04/15| Created Labs project 'newsletter' and instance, 'newsletter-test'. Successfully ssh-ed to the instance|
+|Decide on MVP plan and create necessary tasks|01/05/15 - 05/05/15|Done |
+|Create the Special:NewsLetterCreate interface, and design DB ( the new table )| 06/05/15 - 10/05/15|Done |
+|Create the Special:NewsLetterManage interface - Publisher's view, Newsletter skeleton| 20/05/15 - 30/05/15|Done |
+|Create Special:Newsletters and deploying features on vagrant| 31/05/15 - 15/06/15|Done |
+|Adding newsletter in Notifications tab of Special:Preferences and completing T101546| 16/06/15 - 24/06/15|Done |
+|  Mid Term Evaluation| 26/06/15 - 03/07/15|Done |
+| Work on Blockers and complete extension considering case of Meta alone and no inter wiki newsletters| 04/07/15 - 20/07/15|Done |
+| Work on T102945, T101832, T104829| 21/07/15 - 10/08/15|Done |
+| Writing unit tests, testing the work flow, documentation, deployment | 11/08/15 - 20/08/15|Done|
+| Final Report Submission| 21/08/2015|Done |",1417165348,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_description,resolved
+Goal: Newsletter extension for MediaWiki,"@ResheilA: Hi! Whatever page called ""CA"" you refer to, it's unrelated to this software development task about creating a MediaWiki extension called ""Newsletter"". Please either use https://www.mediawiki.org/wiki/Project:Support_desk for general software problems, or the village pump of your Wikimedia site instead. Thanks.",1464173003,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#2325761, @ResheilA wrote:
+> Hello !
+> Its long I have been active in this group. Can someone help me up ? I have
+> a page called CA. Uttam Agrawal. And its been deleted by the community. I
+> worked hard on it and all my coded stuff are gone. Help me up !! I need it
+> urgent.
+
+Was your page on a wiki? If yes, I think you should contact the people who maintain the wiki in which your page was in.",1464172981,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hello !
+Its long I have been active in this group. Can someone help me up ? I have
+a page called CA. Uttam Agrawal. And its been deleted by the community. I
+worked hard on it and all my coded stuff are gone. Help me up !! I need it
+urgent.
+
+
+
+Resheil Agarwal,
+Founder,
+Webportal.in",1464170352,PHID-USER-sututmegiourdiellndf,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"If you try to say that there is no way to fix the issues I bring up in this particular software development, yes I am aware of that. I try to give feedback not just for the moment, but also for future developments.
+
+> please correct me if I'm not understanding your recommendations
+You are not understanding my recommendations.
+
+And I finish reacting here, I have made my points clear. Other people seem to understand them, and being ridiculed is not something I would like to continue.",1440768632,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, the problem I see is that you leave us no reasonable options following your line of argument. According to your standards, what specific requirements should we handle in this project to guarantee this continuity? A full-time position hired by the Wikimedia Foundation with budget assured for the years to come? And if we don't reach your standards, should we stop this project altogether? This is literally what I understand reading your comments, please correct me if I'm not understanding your recommendations.
+
+As said several times, there is a process to evaluate extensions willing to be deployed in Wikimedia servers (T110170). That process is open for community enquiries and feedback. I will be the first one not pushing for this extension if its development and maintenance plan has open blockers or other flaws. The people that can seriously stop this initiative are the ones that will have to eventually maintain it if the three current contributors involved suddenly disappear from planet Earth. It's free software, all the code and documentation is available, and this is the ultimate guarantee that if there is a serious problem, it can be solved by someone with the skills. This is how the actual economy of open source software works, at Wikimedia and mostly every project maintaining a large codebase.
+
+> If important factors for end-users are missing in software, the software is incomplete.
+
+Please, file tasks for any feature you are missing.",1440568412,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, the problem I see is that you leave us no reasonable options following your line of argument. According to your standards, what specific requirements should we handle in this project to guarantee this continuity? A full-time position hired by the Wikimedia Foundation with budget assured for the years to come? And if we don't reach your standards, should we stop this project altogether? This is literally what I understand reading your comments, please correct me if I'm not understanding your recommendations.
+
+As said several times, there is a process to evaluate extensions willing to be deployed in Wikimedia servers (T110170). That process is open for community enquiries and feedback. I will be the first one not pushing for this extension if its development and maintenance plan has open blockers or other flaws. The people that can seriously stop this initiative are the ones that will have to eventually maintain it if the three current contributors involved suddenly disappear from planet Earth. It's free software, all the code and documentation is available, and this is the ultimate guarantee that if there is a serious problem, it can be solved by someone with the skills. This is how the actual economy of open source software works, at Wikimedia and mostly every project maintaining a large codebase.",1440568359,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, the problem I see is that you leave us no reasonable options following your line of argument. According to your standards, what specific requirements should we handle in this project to guarantee this continuity? A full-time position hired by the Wikimedia Foundation with budget assured for the years to come? And if we don't reach your standards, should we stop this project altogether? This is literally what I understand reading your comments, please correct me if I'm not understanding your recommendations.
+
+As said several times, there is a process to evaluate extensions willing to be deployed in Wikimedia servers (T110170). That process is open for community enquiries and feedback. I will be the first one not pushing for this extension if its development and maintenance plan has open blockers or other flaws. The people that can seriously stop this initiative are the ones that will have to eventually maintain it if the three current contributors involved suddenly disappear from planet Earth. It's free software, all the code and documentation is available, and this is the ultimately guarantee that if there is a serious problem, it can be solved by someone with the skills. This is how the actual economy of open source software works, at Wikimedia and mostly every project maintaining a large codebase.",1440568298,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I think we keep too much talking around the core of the problem.
+
+> disappears one day, users of this extension would be able to go back to the current way keeping whatever subscribers they have.
+You are with this confirming the problem I indicated.
+Unless a software development is intended to be temporary, one of the most important parts for end users is continuity. As I said in my initial post about the problems in the process, this is an example of such problem. The continuity as important aspect would have come up if there was a genuine involvement of the stakeholders/end users.
+
+I was concerned about the process, but I am now really surprised. If important factors for end-users are missing in software, the software is incomplete. If I tell this to my community, they find this crazy. Not to mention the waste of resources.
+
+",1440544451,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I think we keep too much talking around the core of the problem.
+
+> disappears one day, users of this extension would be able to go back to the current way keeping whatever subscribers they have.
+You are with this conforming the problem I indicated.
+Unless a software development is intended to be temporary, one of the most important parts for end users is continuity. As I said in my initial post about the problems in the process, this is an example of such problem. The continuity as important aspect would have come up if there was a genuine involvement of the stakeholders/end users.
+
+I was concerned about the process, but I am now really surprised. If important factors for end-users are missing in software, the software is incomplete. If I tell this to my community, they find this crazy. Not to mention the waste of resources.
+
+",1440544423,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, what @bawolff said.
+
+{T110170} has a long and complex review process ahead, designed to test the appropriateness and robustness of this piece of software and their maintainers. 
+
+Even if one day this extension is implemented in Wikimedia, newsletter owners will not be forced to use it. If you want to keep your current way of managing your newsletter, just keep it. And in the way it is designed, even if the extension blows up and disappears one day,  users of this extension would be able to go back to the current way keeping whatever subscribers they have.
+
+So really, I don't see which harm we are causing by trying to develop and contribute the right thing. ",1440541827,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> In this particular case, I believe yes, because several Foundation-led efforts---the Research Newsletter and Tech/News---will come to rely on it. A cynical answer but a correct one.
+
+This is really an important part of developing software. If newsletters, like mine, are going to use an extension, it is important that continuity is arranged.
+And again, general, I see too little commitment in the Wikimedia Foundation to secure the continuity.
+
+> if Wikimedia would have deployed only software written by people guaranteed to stay around in the long term
+Sorry, but this is not the essence. It is not about individual people. It can be various people. The essence is that WMF gives a guarantee.
+
+> I still think this feature is needed and will be welcome by many authors of current and future newsletters.
+I think not, the number one overall complaint from the community what I see (beyond the irritations of changes and worse styles of implementations) is that the community gets bored that again and again and again software is failing and no longer repaired, while the community makes active use of it. Sure there will be lots of people who have not the previous experience of failing software due lack of maintenance, and like the extension, but that is overall only a short term situation of continuity is not guaranteed.",1440540344,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> But will the Foundation commit to maintaining this extension in the long term?
+
+WMF and volunteer developers do critical maintenance on all extensions deployed to Wikimedia. Whether or not there will be long term resources dedicated to improving the extension depends on a lot of factors which are anyone's guess, but if it is deployed, it will at least be kept in working order.",1440536867,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> But will the Foundation commit to maintaining this extension in the long term?
+
+This is a discussion for {T110170}. See you there.  :)
+
+PS: I'm well aware of of the problem of software maintenance. Then again, if Wikimedia would have deployed only software written by people guaranteed to stay around in the long term, we would have never got MediaWiki and friends. I still think this feature is needed and will be welcome by many authors of current and future newsletters.",1440518091,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Qgil Unlike communications interns, tech interns create products that the community has to rely on in the long term. But will the Foundation commit to maintaining this extension in the long term?
+
+In general, no (you say ""that's not the point""). In this particular case, I believe yes, because several Foundation-led efforts---the Research Newsletter and Tech/News---will come to rely on it. A cynical answer but a correct one.",1440512851,PHID-USER-rtxvf2yd2qd3qmsps3bk,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This Google Summer of Code project has been completed successfully. Thank you @tinaj1234 for your contributions, and thank you @01tonythomas for your technical mentoring. This team has worked very well so far!
+
+For details, read {T109288}.
+
+The work continues at {T110170}. As always, your feedback and contributions are welcome. This is not an internship project anymore; patches are very welcome.  :)",1440494638,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Ohh,1440442926,PHID-USER-muobtocub3solbj4sz5f,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"For what is worth, {T108205} is still open, to be closed this week.",1440442224,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas - okay, thanks, that's helpful. I don't know if giving someone credit for code he didn't write is ""perfect"" - it could confuse people (at least, it confused me). Those credits, like the ""author"" field in mediawiki.org infoboxes, are not just there to give respect; they also give helpful information, like whom to contact if you're thinking of submitting a patch. What about adding a ""History"" section to the mediawiki.org page, to be able to credit Siebrand while clarifying the current situation?",1440438738,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1568209, @Yaron_Koren wrote:
+> @01tonythomas - when you say ""built from scratch"", does that mean that the old extension code was simply wiped out? Looking at the mediawiki.org page, it doesn't look that way - Siebrand is still listed as the author of the extension.
+
+Yeah - the first commit by @Tinaj1234 wiped out everything ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/commit/f0e8491e0c1abda0117b67f05db42fbc708568ca ) if you ignore $wgExtensionCredits entries in Newsletter.php :).  Since @siebrand made an inital commit of the extension in https://github.com/wikimedia/mediawiki-extensions-Newsletter/commit/8cf079a2c2cb71670728eef36c9e42ccbff077be back in 2013 - I think @Tinaj1234 wants to give him credit for his work - which is perfect. ",1440436842,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas - when you say ""built from scratch"", does that mean that the old extension code was simply wiped out? Looking at the mediawiki.org page, it doesn't look that way - Siebrand is still listed as the author of the extension.",1440436546,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"In the Internet most newsletters have a private list of subscribers. If you want to discuss this topic further, please create a new task.
+
+Google Summer of Code has strict deadlines. Projects have to deliver functional code in less than four months. We cannot spend half of that time waiting for feedback without writing any code.
+
+On resources, Tina is a volunteer receiving a stipend from Google, Tony is volunteering as primary mentor, and I'm dedicating about 1-2 hours/week as secondary mentor. Other people has been involved in this project in a smaller capacity, most of them by personal initiative and as volunteers.
+
+I have re-read your comments above, and I still don't see which specific problems can we address. You say
+
+> * MediaWiki is not designed for global navigation, nor navigation across wikis.
+
+I'm not sure what that means, but in any case this extension is not read for interwiki use today. This was left out of scope for the GSoC project and needs to be revisited now.
+
+> * the MediaWiki software is very primitive - it is for example not possible to create a simple button in what someone can (un)subscribe or one of the many other limitations that prevent it to be easy.
+
+This extension allows users to subscribe and unsubscribe from newsletters using checkboxes.
+
+Again, you are encouraged to file tasks for specific problems.",1440415565,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> I'm sorry you received such notifications in your busiest time, but I hope you understand that we cannot wait for the best spot in everybody's agendas. In terms of communication and feedback, I think we have covered the minimum and more.
+That was not my point. It reacted on this:
+> worked upon for 4-5 months and was open to anyone interested
+But only 2 months time was actually given to react.
+
+As said before, I am especially disappointed in the problem definition and how the plan in post 1 is described. I gave feedback on that. I have described problems in the process, but I do not get the impression that it is taken seriously.
+
+@Tinaj1234 & @01tonythomas My apologies to you both if my messages are unpleasant. The problems I notice are outside your involvement in this project (so far I understand). I am personally concerned about how the resources (like you) are used in software development. So please do not take this as criticism on your work, so far I can see you have done in the given circumstances a great job. ",1440410042,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> User expectations, user privacy.
+Those are choices. Here it is chosen to give users privacy. I think it is thought too easy about this.
+
+> It is a usual practice in the Internet that only admins of a newsletter can see who is subscribed to it. For what is worth, by default Wikimedia mailing lists don't disclose the identity of their subscribers either, and only their admins can access to this data.
+It is a usual practice thanks to Twitter and other social media that it is publicly known who is watching what. The comparison with mailing lists is not accurate enough imo.
+",1440409090,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1564774, @Romaine wrote:
+> 
+>> Usernames and emails of subscribes should be kept private. The number of users subscribed to a newsletter would be public (and eventually used to promote popular newsletters).
+> 
+> I do not see a reason for this.
+
+User expectations, user privacy. It is a usual practice in the Internet that only admins of a newsletter can see who is subscribed to it. For what is worth, by default Wikimedia mailing lists don't disclose the identity of their subscribers either, and only their admins can access to this data.",1440407054,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1564774, @Romaine wrote:
+> 
+>> Usernames and emails of subscribes should be kept private. The number of users subscribed to a newsletter would be public (and eventually used to promote popular newsletters).
+> 
+> I do not see a reason for this.
+
+User expectations, user privacy. It is a usual practice that only admins of a newsletter can see who is subscribed to it. For what is worth, by default Wikimedia mailing lists don't disclose the identity of their subscribers either, and only their admins can access to this data.",1440402234,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, @ResMar, here goes some background and a request to be respectful with the open and documented work that others are doing. The summary is: I think this project and its lead developer don't deserve the tone of your first posts here, feel free to learn and ask about the steps we have done, and by all means please bring all the specific objections you might have about this project.
+
+Since 2013, I have been advocating for a newsletter type of functionality for MediaWiki, to be deployed in Wikimedia servers (if you want me to dig in wikitech-l archives, I will). Anybody working on a project in our context knows about the difficulty of setting up one-to-many communications with regular Internet users, not necessarily familiar with watching pages (and following watchlists) or subscribing to services MassMessage style.
+
+https://www.mediawiki.org/wiki/Extension:Newsletter was created on 10 September 2013‎, after I proposed @Siebrand to fork the code related to notifications in the Translate extension. That path didn't progress further.
+
+After some discussions in the context of MassMessage tasks, it was clear that that project would not be the solution for this use case. In 28 November 2014 I created this task. 
+
+The rest can be read in this task. On 10 February 2015 I proposed it as a #Possible-Tech-Projects, and from that point it entered the community review process. @01tonythomas (a former GSoC student, sticking around) volunteered as technical mentor. @Tinaj1234 stepped in as a Google Summer of Code candidate, together with several other students. Tina was selected, and we started to work following the GSoC deadlines. We had a couple of scheduled sessions at the Wikimedia Hackathon in Lyon on May, in June we contacted all the newsletter admins we found in several Wikimedia projects... 
+
+I'm sorry you received such notifications in your busiest time, but I hope you understand that we cannot wait for the best spot in everybody's agendas. In terms of communication and feedback, I think we have covered the minimum and more.
+
+As of today this GSoC project is actually completed, awaiting only its evaluation. We are already discussing the next steps, which include addressing the open tasks, and go through the process to have this extension deployed in Beta, Meta, and then we'll see. Even if you just joined the discussion now, you still have time and chances to bring your feedback and objections.
+
+This is about the project. Now let me add something about the developer that has put hundreds of hours on it in the past months. @Romaine @ResMar,  our new developers deserve a welcoming attitude from all of us. Especially when they are volunteers and interns in programs like GSoC, where Wikimedia decides to participate with a tailored community review process. Nobody knows whether these newcomers will be around in three years. And by the way, the same could be said about all of us (yourselves included) when we joined, and still today.
+
+But you know what? In this specific case it is not even accurate to call @tinaj1234 a newcomer. [[ https://gerrit.wikimedia.org/r/#/q/owner:%22Tinaj1234+%253Ctinajohnson.1234%2540gmail.com%253E%22,n,z | Her first patches ]] for Wikimedia were uploaded on December 2013 and since then she has got code merged in MediaWiki core and some extensions. She has a [[ https://www.mediawiki.org/wiki/User:Tinaj1234 | user account in mediawiki.org ]] since February 2014, when she started to prepare a GSoC proposal. She wasn't accepted because another candidate was chosen for the same project instead (@wctaiwan, who is another example of a GSoC student sticking around until today). So really, Tina has shown a remarkable level of commitment and perseverance even before the end of her GSoC internship.",1440407501,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, @ResMar, here goes some background and a request to be respectful with the open and documented work that others are doing. The summary is: I think this project and its lead developer don't deserve the tone of your first posts here, feel free to learn and ask about the steps we have done, and by all means please bring all the specific objections you might have about this project.
+
+Since 2013, I have been advocating for a newsletter type of functionality for MediaWiki, to be deployed in Wikimedia servers (if you want me to dig in wikitech-l archives, I will). Anybody working on a project in our context knows about the difficulty of setting up one-to-many communications with regular Internet users, not necessarily familiar with watching pages (and following watchlists) or subscribing to services MassMessage style.
+
+https://www.mediawiki.org/wiki/Extension:Newsletter was created on 10 September 2013‎, after I proposed @Siebrand to fork the code related to notifications in the Translate extension. That path didn't progress further.
+
+After some discussions in the context of MassMessage tasks, it was clear that that project would not be the solution for this use case. In 28 November 2014 I created this task. 
+
+The rest can be read in this task. On 10 February 2015 I proposed it as a #Possible-Tech-Projects, and from that point it entered the community review process. @01tonythomas (a former GSoC student, sticking around) volunteered as technical mentor. @Tinaj1234 stepped in as a Google Summer of Code candidate, together with several other students. Tina was selected, and we started to work following the GSoC deadlines. We had a couple of scheduled sessions at the Wikimedia Hackathon in Lyon on May, in June we contacted all the newsletter admins we found in several Wikimedia projects... 
+
+I'm sorry you received such notifications in your busiest time, but I hope you understand that we cannot wait for the best spot in everybody's agendas. In terms of communication and feedback, I think we have covered the minimum and more.
+
+As of today this GSoC is actually completed, awaiting only its evaluation. We are already discussing the next steps, which include addressing the open tasks, and go through the process to have this extension deployed in Beta, Meta, and then we'll see. Even if you just joined the discussion now, you still have time and chances to bring your feedback and objections.
+
+This is about the project. Now let me add something about the developer that has put hundreds of hours on it in the past months. @Romaine @ResMar,  our new developers deserve a welcoming attitude from all of us. Especially when they are volunteers and interns in programs like GSoC, where Wikimedia decides to participate with a tailored community review process. Nobody knows whether these newcomers will be around in three years. And by the way, the same could be said about all of us (yourselves included) when you joined, and still today.
+
+But you know what? In this specific case it is not even accurate to call @tinaj12143 a newcomer. [[ https://gerrit.wikimedia.org/r/#/q/owner:%22Tinaj1234+%253Ctinajohnson.1234%2540gmail.com%253E%22,n,z | Her first patches ]] for Wikimedia were uploaded on December 2013 and since then she has got code merged in MediaWiki core and some extensions. She has a [[ https://www.mediawiki.org/wiki/User:Tinaj1234 | user account in mediawiki.org ]] since February 2014, when she started to prepare a GSoC proposal. She wasn't accepted because another candidate was chosen for the same project instead (@wctaiwan, who is another example of a GSoC student sticking around until today). So really, Tina has shown a remarkable level of commitment and perseverance even before the end of her GSoC internship.",1440401343,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, @ResMar, here goes some background and a request to be respectful with the open and documented work that others are doing. The summary is: I think this project and its lead developer don't deserve the tone of your first posts here, feel free to learn and ask about the steps we have done, and by all means please bring all the specific objections you might have about this project.
+
+Since 2013, I have been advocating for a newsletter type of functionality for MediaWiki, to be deployed in Wikimedia servers (if you want me to dig in wikitech-l archives, I will). Anybody working on a project in our context knows about the difficulty of setting up one-to-many communications with regular Internet users, not necessarily familiar with watching pages (and following watchlists) or subscribing to services MassMessage style.
+
+https://www.mediawiki.org/wiki/Extension:Newsletter was created on 10 September 2013‎, after I proposed @Siebrand to fork the code related to notifications in the Translate extension. That path didn't progress further.
+
+After some discussions in the context of MassMessage tasks, it was clear that that project would not be the solution for this use case. In 28 November 2014 I created this task. 
+
+The rest can be read in this task. On 10 February 2015 I proposed it as a #Possible-Tech-Project, and from that point it entered the community review process. @01tonythomas (a former GSoC student, sticking around) volunteered as technical mentor. @Tinaj1234 stepped in as a Google Summer of Code candidate, together with several other students. Tina was selected, and we started to work following the GSoC deadlines. We had a couple of scheduled sessions at the Wikimedia Hackathon in Lyon on May, in June we contacted all the newsletter admins we found in several Wikimedia projects... 
+
+I'm sorry you received such notifications in your busiest time, but I hope you understand that we cannot wait for the best spot in everybody's agendas. In terms of communication and feedback, I think we have covered the minimum and more.
+
+As of today this GSoC is actually completed, awaiting only its evaluation. We are already discussing the next steps, which include addressing the open tasks, and go through the process to have this extension deployed in Beta, Meta, and then we'll see. Even if you just joined the discussion now, you still have time and chances to bring your feedback and objections.
+
+This is about the project. Now let me add something about the developer that has put hundreds of hours on it in the past months. @Romaine @ResMar,  our new developers deserve a welcoming attitude from all of us. Especially when they are volunteers and interns in programs like GSoC, where Wikimedia decides to participate with a tailored community review process. Nobody knows whether these newcomers will be around in three years. And by the way, the same could be said about all of us (yourselves included) when you joined, and still today.
+
+But you know what? In this specific case it is not even accurate to call @tinaj12143 a newcomer. [[ https://gerrit.wikimedia.org/r/#/q/owner:%22Tinaj1234+%253Ctinajohnson.1234%2540gmail.com%253E%22,n,z | Her first patches ]] for Wikimedia were uploaded on December 2013 and since then she has got code merged in MediaWiki core and some extensions. She has a [[ https://www.mediawiki.org/wiki/User:Tinaj1234 | user account in mediawiki.org ]] since February 2014, when she started to prepare a GSoC proposal. She wasn't accepted because another candidate was chosen for the same project instead (@wctaiwan, who is another example of a GSoC student sticking around until today). So really, Tina has shown a remarkable level of commitment and perseverance even before the end of her GSoC internship.",1440401294,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1566016, @ResMar wrote:
+> I think that Romaine is implicitly criticizing a problem that's plagued the movement for a long time: outside contractors are brought in, write a feature, and then leave. No offense to you, Tinaj, but I //highly// doubt that say three years from now you will be maintaining this codebase, or even contactable.
+
+Just for the record, there are several developers who had GSOC projects and stuck around for 3 or more years. I have no idea if Tinaj will be one of them, and s/he certainly has no obligations past the end of his/her project but its entirely possible that s/he could be.
+
+> 
+> In your absence no one attached to the movement will be familiar with the code, causing it to trip up other extensions, suffer legacy rot, and eventually become completely unusable. This turnover problem is one half of the legacy dependence problem of the Wikimedias (a total lack of intercommunal standards across Wikimedias is the other half).
+> 
+> In this case the extension backs into a ""platform for the future"", Echo, that's in continual development. Hopefully that will keep this extension alive.
+
+I'm not sure its fair to have this discussion here. These sound more like generic issues surrounding the GSOC/OPW program and doesn't have much to do with this particular project.
+
+Keep in mind, creating a feature for use by the Wikimedia movement over the long term is not necessarily the goal of the GSOC/OPW program.",1440395825,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1566284, @Yaron_Koren wrote:
+> Can someone briefly explain the goal of this project? From the title and description, it sounds like a project to create a new extension. But instead, this project seems to have modified an existing extension, [[ https://www.mediawiki.org/wiki/Extension:Newsletter | ""Newsletter""]]. Is that the case? If so, did the task change at some point? And what is the goal that was achieved?
+
+The goal of the project was to build a 'Newsletter' extension which must allow: 
+
+
+  # Newsletter Authors to easily create and manage Newsletters with scope limited to his rights
+  # A usual wiki user to subscribe/unsubscribe to available newsletters in his Wiki ( inter-wiki is post GSoC scope ) 
+  # Receive notifications via web/email using Echo whenever a Newsletter creates a new issuse. 
+
+The project took place basically from the description of this task, and was built from scratch ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/commits/master )  - now live at http://newsletter-test.wmflabs.org/wiki/Main_Page - You can find the instructions on how to use the same over there. @Tinaj1234 will work on it further to cross the arch/sec and performance review to take it to production which is of course, not in the scope of GSoC 2015. 
+",1440394972,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Can someone briefly explain the goal of this project? From the title and description, it sounds like a project to create a new extension. But instead, this project seems to have modified an existing extension, [[ https://www.mediawiki.org/wiki/Extension:Newsletter | ""Newsletter""]]. Is that the case? If so, did the task change at some point? And what is the goal that was achieved?",1440393491,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Thanks ResMar!
+What ResMar is describing is indeed a part of the issue I see. I am concerned about both the process of the development of this software as the general situation of software development. I am concerned about a long term stability.
+
+",1440375449,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I think that Romaine is implicitly criticizing a problem that's plagued the movement for a long time: outside contractors are brought in, write a feature, and then leave. No offense to you, Tinaj, but I //highly// doubt that say three years from now you will be maintaining this codebase, or even contactable.
+
+In your absence no one attached to the movement will be familiar with the code, causing it to trip up other extensions, suffer legacy rot, and eventually become completely unusable. This turnover problem is one half of the legacy dependence problem of the Wikimedias (a total lack of intercommunal standards across Wikimedias is the other half).
+
+In this case the extension backs into a ""platform for the future"", Echo, that's in continual development. Hopefully that will keep this extension alive.",1440372300,PHID-USER-rtxvf2yd2qd3qmsps3bk,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"(Please remember that this bug is about developing a newsletter extension for *MediaWiki*, not *Wikimedia*.)",1440366890,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> 4-5 months
+We received a message only 2 months ago: 9 June 2015. Just before the most busiest time of the year.
+
+> I don't think the plan [...] is insufficient at all.
+Reading the plan, as described in the first post in this Task, it is insufficient to judge.
+
+> The answer is a 'yes'.
+I doubt that. I think the difference in answering is likely caused by interpreting the questions differently than how they were intended.
+
+I am not necessary negative about the idea, but the plan described in post 1 is insufficient. And the involvement from stakeholders was also insufficient. (Yes, insufficient with the current level of participation.)
+Based on the provided information I get too much the idea that this extension is //developed for// instead of //developed with//. Of course you then say that you have asked newsletter to give feedback, but that makes it still insufficient. The biggest pain in the ass for the Wikimedia community is that they are too little considered to be stakeholder, and are to little involved from the first plan until the end during the whole process.
+
+> I don't quite get what you meant here.
+I described two large issues we experience working on wikis too often. The problem description on Meta can be completely derived from these two large issues. This makes ""fixing"" the described problem a form of treating symptoms, instead of the core problems.
+
+It gives me this feeling: https://xkcd.com/927/
+
+> But we have brought up a beautiful extension which works fine( with tables and buttons and what not ) and is believed to benefit many, do have a look.
+This sounds like a car salesman. I do not think it is a good idea if a developer him/herself is saying that it is beautiful, fine working, benefit many, etc. That is up to the stake holders and end users to judge.
+",1440349365,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1564783, @Romaine wrote:
+> Reading this plan, no publisher is able to give feedback as the actual contents are missing. The actual things that matter to publishers is not described in the plan. The plan described is too vague.
+> 
+> It is like describing a new car: it has doors, a steering wheel, seets, a roof, lights and more. This is completely insufficient.
+I don't think the plan ( which was worked upon for 4-5 months and was open to anyone interested ) is insufficient at all. The extension pretty much makes easy any task a publisher or an owner is required to do. Please go through the features implemented as well because the extension has evolved very much from its initial stages. 
+> Also some other issues:
+> * Where there any publishers and readers involved in the plan?
+> * Has there been any priority check for which software developments are really needed and make a big difference for the movement?
+> * Where there any publishers and readers involved during the development process?
+> 
+> Reading more pages I get the impression that these three questions are to be answered with ""no"".
+The answer is a 'yes'. I see you've gone through T100604 and we waited over a week before closing that task to collect reviews and opinions of stakeholders. A message was left on each page( the list of links in T100604 ) to inform existing newsletters and various other developers about the extension and we were encouraged by a lot of positive replies from many editors and publishers to move forward with the extension. 
+> Seeing what problem description is [[ https://meta.wikimedia.org/wiki/Grants:IdeaLab/Newsletter_extension_for_MediaWiki | given ]], I can only think it is too simplistic and not reaching to the core of the problem: 
+> * MediaWiki is not designed for global navigation, nor navigation across wikis.
+> * the MediaWiki software is very primitive - it is for example not possible to create a simple button in what someone can (un)subscribe or one of the many other limitations that prevent it to be easy.
+I don't quite get what you meant here. But we have brought up a beautiful extension which works fine( with tables and buttons and what not ) and is believed to benefit many, do have a [[ http://newsletter-test.wmflabs.org/wiki/Main_Page | look ]]. ",1440322710,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,,1440311866,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,,1440311815,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Reading this plan, no publisher is able to give feedback as the actual contents are missing. The actual things that matter to publishers is not described in the plan. The plan described is too vague.
+
+It is like describing a new car: it has doors, a steering wheel, seets, a roof, lights and more. This is completely insufficient.
+
+Also some other issues:
+* Where there any publishers and readers involved in the plan?
+* Has there been any priority check for which software developments are really needed and make a big difference for the movement?
+* Where there any publishers and readers involved during the development process?
+
+Reading more pages I get the impression that these three questions are to be answered with ""no"".
+
+Seeing what problem description is [[ https://meta.wikimedia.org/wiki/Grants:IdeaLab/Newsletter_extension_for_MediaWiki | given ]], I can only think it is too simplistic and not reaching to the core of the problem: 
+* MediaWiki is not designed for global navigation, nor navigation across wikis.
+* the MediaWiki software is very primitive - it is for example not possible to create a simple button in what someone can (un)subscribe or one of the many other limitations that prevent it to be easy.
+
+Instead of improving this limited and too often too difficult situation, effort is taken to fight only a symptom of the core problems.
+
+I am afraid that this extension appears to be a waste of energy and resources.",1440311808,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I believe @Qgil was referring to the case of http://newsletter-test.wmflabs.org/wiki/Special:Newsletters where a user need not know who is subscribed to the newsletter instead we tell him/her the popularity of the newsletter through the subscriber count.,1440310566,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"
+> Usernames and emails of subscribes should be kept private. The number of users subscribed to a newsletter would be public (and eventually used to promote popular newsletters).
+
+I do not see a reason for this.
+
+
+",1440309938,PHID-USER-pwdu7zlsq3lcr63acm5c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hi, I have associated two blocked-by tasks with this project. 
+
+**For the student:** 
+1. Please go through the checklist in the end-term evaluation and fill out the fields which require any links. The checkboxes are for the mentor(s) only. Adding information on the past projects page is your task. 
+2. Ensure that you have completed //all// the items listed in the end-term evaluation task. If there's a strong reason about why a particular item was not completed, please comment on the task and we shall look into it. 
+3. Wrap-up report is //mandatory// and so is a demo-able link to the project (either in production or in a demo server). 
+4. If you want your project to be featured in the blogpost on the Google OSPO blog, kindly comment back with a short, catchy description of the project along with a screenshot. ",1439822789,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Great. @Tinaj1234, please write up a short description of the project when you get time for the blog. Also add one, most relevant screenshot which I can include in the post. Thanks!",1439402096,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1528553, @Dzahn wrote:
+> It would be great if you could import the repo to Gerrit instead of working off of github.
+
+Ah. We were committing to Gerrit from the start of the project. We have it over here http://git.wikimedia.org/tree/mediawiki%2Fextensions%2FNewsletter",1439320942,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,It would be great if you could import the repo to Gerrit instead of working off of github.,1439319909,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"In our case, ""merged"" is what exists in the Newsletter extension repo, fully functional in Labs. ""Deployed in Wikimedia"" is a goal for us, but definitely out of scope of GSoC.",1439319554,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1514646, @NiharikaKohli wrote:
+> A few questions (for both mentors and student):
+> - Are you confident in completing the project on time?
+Of course. Almost all the blockers are resolved as of now, and looking at the open tasks at https://phabricator.wikimedia.org/T76199 - its more of the design elements still there. The strictly planned MVP which came as a result of discussions from Lyon and weekly meetings made sure that we have the minimum features ready even before mid-term. This made it easy for @Tinaj1234, as most of the post-mid term works were design stuff. Most features lacked documentation, but @Tinaj1234 was impressive with getting it done. 
+ 
+> - By when do you think you can merge the code, if at all?
+Almost all of the patchsets that showed up in Gerrit was reviewed and merged to the github repo in < 2 days - and if you are talking about deployment to production, it might take a bit long to go through the security, arch and performance review through beta to prod - and I expect these to happen in the coming month. Deployment to production was not a part of the GSoC project, anyway. 
+> - Are there any major blockers or important missing features?
+I dont think there is anything critical as of now. 
+
+Great work till date. You can see the code produced over here : https://github.com/wikimedia/mediawiki-extensions-Newsletter, and test it live at newsletter-test.wmflabs.org
+",1439310932,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1514646, @NiharikaKohli wrote:
+> 
+> A few questions (for both mentors and student):
+> - Are you confident in completing the project on time?
+Yes, ofcourse.
+> - By when do you think you can merge the code, if at all?
+Most of the completed features are merged already. Everything will be merged before 17th August.
+> - Are there any major blockers or important missing features?
+No, all important features are almost done. Remaining high priority tasks will be completed in the coming week.
+
+",1438881037,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hello!
+
+End of GSoC is fast approaching. 17 August is ""Suggested pencils down"" deadline and 21 August is ""Firm pencils down"" deadline. It is expected that you don't dive into new features which might take longer than two weeks to complete and instead work on polishing up your project, testing thoroughly and getting your code merged into the main branch. I hope this project is almost complete so you can merge it and make it available to everyone as quickly as possible. :)
+
+A few questions (for both mentors and student):
+- Are you confident in completing the project on time?
+- By when do you think you can merge the code, if at all?
+- Are there any major blockers or important missing features?
+
+We are looking for projects which are (nearly) complete to feature on our post on Wikimedia and Google OSPO's blogs (for example: http://google-opensource.blogspot.in/2015/02/google-summer-of-code-wrap-up-processing.html). If you're interested in getting yours up there, hurry up and get this finished!
+
+The hard deadline on getting code merged is September. {T101393} for details. 
+
+We'll be asking the students to demo their projects towards the end of the program as well. 
+
+Good luck!",1438873949,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1428602, @ResMar wrote:
+> I do wonder if a short tagline could not be added to the Echo notification (something along the lines of ""In this issue: see what really goes in the Phabricator"")
+Yes, it would be more informative for the readers if the notification can contain more details indicating what the new issue is about. Thank you! I'll add a blocker task for this.
+
+",1436162055,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I tested it a bit. Looking good so far! I do wonder if a short tagline could not be added to the Echo notification (something along the lines of ""In this issue: see what really goes in the Phabricator""), but other than that it's already a dream come true.",1436158629,PHID-USER-rtxvf2yd2qd3qmsps3bk,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I tested it a bit. Looking good so far! I do wonder if a short tagline could not be added to the Echo notification, but other than that it's already a dream come true.",1436158445,PHID-USER-rtxvf2yd2qd3qmsps3bk,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"The criteria to define a blocker should be: 
+
+  Bugfix or feature required to handle newsletters hosted in Meta. 
+
+Let's leave the multi-wiki scenario for the next milestone (hopefully to be still address during this GSoC round, will depend on the blockers for the single wiki scenario).",1435848198,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"The criteria to define a blocker should be: 
+
+ Bugfix or feature required to handle newsletters hosted in Meta. 
+
+Let's leave the multi-wiki scenario for the next milestone (hopefully to be still address during this GSoC round, will depend on the blockers for the single wiki scenario).",1435848184,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Since the MVP is completed we are in position to discuss on our next milestone!
+
+You can see a number of blockers listed in #MediaWiki-extensions-Newsletter workboard. But we think there is a possibility for more blockers and if anyone finds one feel free to create a task and add it to the workboard. The blockers to be closed by end of July will be decided on the next week's meeting ( 9th June 10:30 AM UTC ) and it would be convenient to have all the blockers out by then.
+
+Test MVP here: http://newsletter-test.wmflabs.org/ ( Check description on Main Page to find which page to go to )
+
+@quiddity, @Bawolff, @legoktm Awaiting reviews and comments especially from you guys :)
+  ",1435847222,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Just a note to say that mentoring this project until completion is one of my individual goals for {T101100}.
+
+| Goal |	Measurement of success | Dependency | ETA | Status
+| ----- | ----- | ----- | ----- | ----- |
+| Mentor {T76199} successfully | New extension deployed in Labs and ready to start Wikimedia's review process | @Tinaj1234 @01tonythomas | #ECT-September-2015 | In progress |
+",1435678504,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@MGChecker, Thanks for pointing it out. Fixed it.",1435093814,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"If I open Special:Preferences in your devwiki, I get
+
+
+```
+[25a347c3] /wiki/Special:Preferences MWException from line 182 of /srv/vagrant/mediawiki/includes/Hooks.php: Invalid callback NewsletterHooks::onGetPreferences in hooks for GetPreferences
+
+Backtrace:
+
+#0 /srv/vagrant/mediawiki/includes/Preferences.php(99): Hooks::run(string, array)
+#1 /srv/vagrant/mediawiki/includes/Preferences.php(1260): Preferences::getPreferences(User, RequestContext)
+#2 /srv/vagrant/mediawiki/includes/specials/SpecialPreferences.php(60): Preferences::getFormObject(User, RequestContext)
+#3 /srv/vagrant/mediawiki/includes/specialpage/SpecialPage.php(384): SpecialPreferences->execute(NULL)
+#4 /srv/vagrant/mediawiki/includes/specialpage/SpecialPageFactory.php(581): SpecialPage->run(NULL)
+#5 /srv/vagrant/mediawiki/includes/MediaWiki.php(285): SpecialPageFactory::executePath(Title, RequestContext)
+#6 /srv/vagrant/mediawiki/includes/MediaWiki.php(634): MediaWiki->performRequest()
+#7 /srv/vagrant/mediawiki/includes/MediaWiki.php(431): MediaWiki->main()
+#8 /srv/vagrant/mediawiki/index.php(41): MediaWiki->run()
+#9 /var/www/w/index.php(5): include(string)
+#10 {main}
+
+```
+
+I think this schould be fixed.
+",1435085653,PHID-USER-4z6eerx3m7iocsrcpku5,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Currently, we are implementing T99784 with two of them merged already, T101505 and T100125. When it comes to communication, if you look at the description you'll see that we have weekly meetings every Thursday and also like Quim said there was a task open for Stakeholder Outreach. You might get a better idea of what is going on if you look at the [[ https://phabricator.wikimedia.org/T100997 | weekly reports task ]] and [[ https://phabricator.wikimedia.org/tag/mediawiki-extensions-newsletter/ | corresponding tasks ]] created for each feature maybe.",1434926239,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Thanks for the clarifications.
+
+Is this task's description supposed to be an accurate reflection of the current development and implementation plan? I was responding directly to screenshots such as M12 that are included in this task's description. In addition to a mock-up, there are also comments such as ""Adding Newsletter tab to Special:Preferences"" in the timeline... this seems pretty confusing to me.
+
+I can appreciate wanting to break down a large task into smaller tasks, but fracturing discussion among dozens of tasks has very real communications costs. There should be a centralized place to discuss this proposal and review its current implementation plan. I thought that place was this task, but perhaps I'm mistaken?",1434918146,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@MZMcBride, this proposal has gone through a review process as part of #Google-Summer-of-Code-2015 and now we are in full development mode. Let's  help @Tinaj1234 (our GSoC student for this project) focus on the existing plan, which right now welcomes implementable feedback and suggestions for improvement. The result of this work should be a functional extension running in a Labs instance by the end of September (latest). From there we will discuss whether this makes sense for Wikimedia and, if so, what is missing for deployment.
+
+>>! In T76199#1386184, @MZMcBride wrote:
+> Parts of this proposal feel like natural complements to the existing work that's already been done in MassMessage.
+
+Just for the background: in T59935 we decided to detach newsletter types of features from MassMessage. Legoktm has been following this project and I think both extensions will be good neighbors accomplishing complementary but not equivalent objectives.
+
+> Are users really interested in the flexibility of receiving the Military history newsletter via e-mail, but the Signpost via talk page message (which would trigger an e-mail for most users anyway...)? Are per-newsletter delivery preferences something we actually want or need?
+
+We are not planning per-newsletter delivery preferences, see {T100492} and comment there if you have feedback.
+ 
+> As always, I'm wary of yet another preferences tab, especially sitting next to an existing ""Notifications"" tab.
+
+There is no new preferences tab, just a new entry for Newsletters in the Notifications tab, as this will be integrated with Echo. If you want to discuss further, see {T101546}.
+
+ 
+> I'm not yet convinced of the need for a separate MediaWiki extension here. Publishing content is what the core wiki software should be good at already. I don't see the great value in a specialized layer for creating newsletters specifically.
+
+For what is worth, we made a {T100604} and authors of actual newsletters think this project is useful for their needs. This extension doesn't deal with publishing content per se, as this is done through regular wiki pages. What this extension aims to solve are problems that our current software doesn't solve well: possibility to subscribe/unsubscribe easily to newsletters (without relying on watchlists) and possibility to announce new issues of newsletters via email or web notification (without relying on Talk pages). While advanced users of watchlist and talk pages might see little difference / value, we expect this extension to help newsletter authors to get a lot more subscribers (even among new users feeling more comfortable about subscribing to a newsletter than about start editing on a regular basis) and a lot more actual readers not missing their issues as easily as they might miss changes in their watchlists.
+
+I hope this reply is good enough to see the point of this GSoC project. Your attention to detail is welcome in the ongoing tasks or in new tasks that you are encouraged to create.",1434917690,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@MZMcBride, this proposal has gone through a review process as part of #Google-Summer-of-Code-2015 and now we are in full development mode. Let's  help @Tinaj1234 (our GSoC student for this project) focus on the existing plan, which right now welcomes implementable feedback and suggestions for improvement. The result of this work should be a functional extension running in a Labs instance by the end of September (latest). From there we will discuss whether this makes sense for Wikimedia and, if so, what is missing for deployment.
+
+>>! In T76199#1386184, @MZMcBride wrote:
+> Parts of this proposal feel like natural complements to the existing work that's already been done in MassMessage.
+
+Just for the background: in T59935 we decided to detach newsletter types of features from MassMessage. Legoktm has been following this project and I think both extensions will be good neighbors accomplishing complementary but not equivalent objectives.
+
+> Are users really interested in the flexibility of receiving the Military history newsletter via e-mail, but the Signpost via talk page message (which would trigger an e-mail for most users anyway...)? Are per-newsletter delivery preferences something we actually want or need?
+
+We are not planning to per-newsletter delivery preferences, see {T100492} and comment there if you have feedback.
+ 
+> As always, I'm wary of yet another preferences tab, especially sitting next to an existing ""Notifications"" tab.
+
+There is no new preferences tab, just a new entry for Newsletters in the Notifications tab, as this will be integrated with Echo. If you want to discuss further, see {T101546}.
+
+ 
+> I'm not yet convinced of the need for a separate MediaWiki extension here. Publishing content is what the core wiki software should be good at already. I don't see the great value in a specialized layer for creating newsletters specifically.
+
+For what is worth, we made a {T100604} and authors of actual newsletters think this project is useful for their needs. This extension doesn't deal with publishing content per se, as this is done through regular wiki pages. What this extension aims to solve are problems that our current software doesn't solve well: possibility to subscribe/unsubscribe easily to newsletters (without relying on watchlists) and possibility to announce new issues of newsletters via email or web notification (without relying on Talk pages). While advanced users of watchlist and talk pages might see little difference / value, we expect this extension to help newsletter authors to get a lot more subscribers (even among new users feeling more comfortable about subscribing to a newsletter than about start editing on a regular basis) and a lot more actual readers not missing their issues as easily as they might miss changes in their watchlists.
+
+I hope this reply is good enough to see the point of this GSoC project. Your attention to detail is welcome in the ongoing tasks or in new tasks that you are encouraged to create.",1434917656,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@MZMcBride, this proposal has gone through a review process as part of #Google-Summer-of-Code-2015 and now we are in full development mode. Let's  help @Tinaj1234 (our GSoC student for this project) focus on the existing plan, which right now welcomes implementable feedback and suggestions for improvement. The result of this work should be a functional extension running in a Labs instance why the end of September (latest). From there we will discuss whether this makes sense for Wikimedia and, if so, what is missing for a deployment.
+
+>>! In T76199#1386184, @MZMcBride wrote:
+> Parts of this proposal feel like natural complements to the existing work that's already been done in MassMessage.
+
+Just for the background: in T59935 we decided to detach newsletter types of features from MassMessage. Legoktm has been following this project and I think both extensions will be good neighbors accomplishing complementary but not equivalent objectives.
+
+> Are users really interested in the flexibility of receiving the Military history newsletter via e-mail, but the Signpost via talk page message (which would trigger an e-mail for most users anyway...)? Are per-newsletter delivery preferences something we actually want or need?
+
+We are not planning to per-newsletter delivery preferences, see {T100492} and comment there if you have feedback.
+ 
+> As always, I'm wary of yet another preferences tab, especially sitting next to an existing ""Notifications"" tab.
+
+There is no new preferences tab, just a new entry for Newsletters in the Notifications tab, as this will be integrated with Echo. If you want to discuss further, see {T101546}.
+
+ 
+> I'm not yet convinced of the need for a separate MediaWiki extension here. Publishing content is what the core wiki software should be good at already. I don't see the great value in a specialized layer for creating newsletters specifically.
+
+For what is worth, we made a {T100604} and authors of actual newsletters think this project is useful for their needs. This extension doesn't deal with publishing content per se, as this is done through regular wiki pages. What this extension aims to solve are problems that our current software doesn't solve well: possibility to subscribe/unsubscribe easily to newsletters (without relying on watchlists) and possibility to announce new issues of newsletters via email or web notification (without relying on Talk pages). While advanced users of watchlist and talk pages might see little difference / value, we expect this extension to help newsletter authors to get a lot more subscribers (even among new users feeling more comfortable about subscribing to a newsletter than about start editing on a regular basis) and a lot more actual readers not missing their issues as easily as they might miss changes in their watchlists.
+
+I hope this reply is good enough to see the point of this GSoC project. Your attention to detail is welcome in the ongoing tasks or in new tasks that you are encouraged to create.",1434917496,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Please see that we are not going to affect Special:Preferences - and - what we have would be a Special:Newsletter which would list down the available newsletters for the wiki, and the user can click on each - read its shorty bio and see some stats - and click on Subscribe button to subscribe. Populating the overpopulated Special:Preference more is definitely a bad idea. 
+
+The extension is designed in such a way that existing Newsletters can be easily added to the extension to increase manageability. The Newsletter admins would be given something like http://newsletter-test.wmflabs.org/wiki/Special:NewsletterCreate ( log-in required ) which would allow addition of existing Newsletters - which are wiki pages. Maybe in the later steps, we would have a feature to readily create a newsletter with pre-defined templates right from the Special:NewsletterCreate
+
+",1434916067,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"On-wiki newsletters are an interesting idea, though I wonder if we're not just painfully duplicating the features of a mailing list.
+
+Parts of this proposal feel like natural complements to the existing work that's already been done in MassMessage. For example, ContentHandler-backed MassMessage subscription lists should be trivially query-able to retrieve and expose numbers of subscribers.
+
+Adding on-wiki notification (Echo) support to MassMessage might be nice and would begin to expose a need for some kind of extension to manage a user's contact preference, perhaps. However, I'm not sure many users want to get that granular. Are users really interested in the flexibility of receiving the Military history newsletter via e-mail, but the Signpost via talk page message (which would trigger an e-mail for most users anyway...)? Are per-newsletter delivery preferences something we actually want or need?
+
+As always, I'm wary of yet another preferences tab, especially sitting next to an existing ""Notifications"" tab.
+
+I'm not yet convinced of the need for a separate MediaWiki extension here. Publishing content is what the core wiki software should be good at already. I don't see the great value in a specialized layer for creating newsletters specifically.",1434915380,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Works for me too! See you guys tomorrow at 15:00 IST,1433431873,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"[[ http://www.timeanddate.com/worldclock/meetingdetails.html?year=2015&month=6&day=5&hour=9&min=30&sec=0&p1=311&p2=771 | This time ]] works for me, yes.",1433424615,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Qgil, @Tinaj1234 : How about we having a meeting, tomorrow ( 5 June 2015 ) at 3-4 pm IST ?",1433423347,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"How about we having a meeting, tomorrow ( 5 June 2015 ) at 3-4 pm IST ?",1433423328,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1315875, @Qgil wrote:
+> 
+> @Tinaj1234, I think this is a good idea. Could you create a task for this?
+
+T100604 created for further discussions.",1432785980,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1314246, @Tbayer wrote:
+> Is it planned to do some kind of stakeholder outreach to the people who will be using this new software, in particular publishers of existing newsletters?
+
+@Tinaj1234, I think this is a good idea. Could you create a task for this? There @tbayer and @quiddity will tell us the best to reach to the publishers of newsletters.  ;)  (MassMessage against... a list of Newsletters somewhere? Please discuss in the new task, so we keep this one relatively quiet.)",1432764107,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1314246, @Tbayer wrote:
+> Is it planned to do some kind of stakeholder outreach to the people who will be using this new software, in particular publishers of existing newsletters? (I understand ""community bonding"" refers to something different.) It would seem prudent to get their feedback on the planned features, to make sure they will actually get used.
+
+Oops! Sorry for the confusion, but this project is scheduled to be done as part of the Google Summer of Code 2015 program, and @Tinaj1234 is the student assigned with 'us' mentoring. 'Community Bonding' is the phase 1 of the project workflow when the candidate gets to know the community and the project. We are preparing the bare minimum product for a start before the mid term ( https://developers.google.com/open-source/soc/ ) and you we welcome existing stakeholders like you to start creating 'sub tasks' to this phab task so that we make sure its delivered before hitting production. 
+
+",1432731110,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Very exciting to see work progressing in this area! (Speaking as someone who has been regularly sending out newsletters since 2010, and author of one of the pages that Nick linked.)
+
+Is it planned to do some kind of stakeholder outreach to the people who will be using this new software, in particular publishers of existing newsletters? (I understand ""community bonding"" refers to something different.) It would seem prudent to get their feedback on the planned features, to make sure they will actually get used.",1432728023,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Just FYI, here's my bookmark folder for ""Newsletters"", which has many useful parts, many outdated pages, and much potential for distraction. ;-)
+
+* https://meta.wikimedia.org/wiki/Newsletters
+* https://meta.wikimedia.org/wiki/Internal_news_media
+* https://en.wikipedia.org/wiki/Wikipedia:News
+* https://de.wikipedia.org/wiki/Wikipedia:Nachrichten
+* https://www.mediawiki.org/wiki/Communication
+* https://www.mediawiki.org/wiki/Extension_talk:Newsletter and https://www.mediawiki.org/wiki/Extension:Newsletter
+* https://www.mediawiki.org/wiki/Movement_broadcasting",1432038992,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Discussions #2  ( 19/05/2015 ) paste: 
+https://phabricator.wikimedia.org/P653
+",1432031867,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Qgil: Since we wont be able to do much of code work, since a student is assigned for the same, I think we are looking for something in the 'Meeting' category where we can list out what we are planning to do with the NewsLetter. We should be looking at: 
+
+
+  # How the SpecialPage(s) should look like, what all functions should be made public
+  # Who should be given the right to create/edit NewsLetters 
+  # More design inputs for the NewsLetter SpecialPage 
+  # Showcase our current idea of creating/storing a NewsLetter - and get more inputs about its feasibility
+  # Possibility of handling subscription from the Special:Preferences 
+
+I think we will have to prepare few mockups ( I can take care of that ) !
+
+",1431949127,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"It is time to promote #Wikimedia-Hackathon-2015 activities in the [[ https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015/Program | program ]] (training sessions and meetings) and [[ https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015#Activities_confirmed | main wiki page ]] (hacking projects and other ongoing activities). [[ https://phabricator.wikimedia.org/T97121 | Follow the instructions ]], please. If you have questions, about this message, ask [[ https://phabricator.wikimedia.org/T97121  | here ]].",1431947539,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Log of IRC meeting on #wikimedia-newsletter - P627.,1431102000,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Created web proxy for the Labs instance and can now be accessed using: http://newsletter-test.wmflabs.org/ !,1430765379,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I associated this task to #Wikimedia-Hackathon-2015 when I was trying to get development hours for it from anywhere possible.  :)  Are we going to have any specific activity there, though? If so, please create a specific task for this activity.
+
+In general, we need to keep this task as silent as possible, blocking it by the main tasks of this project (that will have their own subtasks).",1430391456,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas, @Qgil - Thanks a lot for the opportunity. Created subtask, T97413 to start off with the community bonding period. Looking forward to working with everyone involved !",1430229839,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1241220, @Qgil wrote:
+> Alright, let's start with the [[ https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#Community_bonding_period | community bonding period ]]. Please create a subtask as described in T94166, and let's discuss there the tasks related with this phase (i.e. starting our routine of weekly meetings). 
+> 
+> @01tonythomas, thank you for your efforts providing microtasks and support to all candidates. Let's leave no excuse to Tina to deliver this extension.  ;) 
+@qgil True! Cant wait to start this one :) Congrats @Tinaj1234!
+Thanks to everyone who came forward with their proposals! 
+
+",1430228651,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Congratulations @Tinaj1234 and welcome to #Google-Summer-of-Code-2015 with {T93583}! I'm looking forward to working with you on a first release of the Newsletter extension.
+
+Alright, let's start with the [[ https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#Community_bonding_period | community bonding period ]]. Please create a subtask as described in T94166, and let's discuss there the tasks related with this phase (i.e. starting our routine of weekly meetings). 
+
+@01tonythomas, thank you for your efforts providing microtasks and support to all candidates. Let's leave no excuse to Tina to deliver this extension.  ;) 
+
+Anybody interested in seeing this extension deployed one day in Wikimedia, please step in and get involved.",1430217577,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"goodreads.com is my current ideal model - just look at this delicious malleability!   (I know developers are very wary of adding preferences (because extra complexity, and testing, and maintenance) but users tend to love them, especially the broad diversity of powerusers in highly-complex projects. ;-)
+{F109890}",1428461024,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Please see the updated comment ! ,1427965454,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,ohh yeaah :),1427956944,PHID-USER-sututmegiourdiellndf,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"There was an extra ""]"" at the end of the link:
+https://github.com/wikimedia/mediawiki-extensions-BounceHandler/blob/master/includes/ProcessUnRecognizedBounces.php",1427919275,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Github link is non existent.,1427918734,PHID-USER-sututmegiourdiellndf,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This task to add an echo notification came directly to the BounceHandler project - T94436 - and would be a relevant micro-task to the project as you need to be doing that to notify the subscribers.
+Hints: 
+* You have the failing recipient ( to be notified ) user object in here [ https://github.com/wikimedia/mediawiki-extensions-BounceHandler/blob/master/includes/BounceHandlerActions.php#L93 ]
+* Follow http://www.mediawiki.org/wiki/Echo_(Notifications)/Developer_guide to see how you can integrate Echo notifications to an extension!
+* You can see how Extension:Thanks hook into 'Echo' notifications in line 33 - 37 here ( https://etherpad.wikimedia.org/p/newsletterExtension )",1427965416,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This task to add an echo notification came directly to the BounceHandler project - T94436 - and would be a relevant micro-task to the project as you need to be doing that to notify the subscribers.
+Hints: 
+* You have the failing recipient ( to be notified ) email id passed as $email in processUnRecognizedBounces( ) [https://github.com/wikimedia/mediawiki-extensions-BounceHandler/blob/master/includes/ProcessUnRecognizedBounces.php]
+* Follow http://www.mediawiki.org/wiki/Echo_(Notifications)/Developer_guide to see how you can integrate Echo notifications to an extension!
+* You can see how Extension:Thanks hook into 'Echo' notifications in line 33 - 37 here ( https://etherpad.wikimedia.org/p/newsletterExtension )",1427881434,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This task to add an echo notification came directly to the BounceHandler project - T94436 - and would be a relevant micro-task to the project as you need to be doing that to notify the subscribers.
+Hints: 
+* You have the failing recipient ( to be notified ) email id passed as $email in processUnRecognizedBounces( ) [https://github.com/wikimedia/mediawiki-extensions-BounceHandler/blob/master/includes/ProcessUnRecognizedBounces.php]
+* You can see how Extension:Thanks hook into 'Echo' notifications in line 33 - 37 here ( https://etherpad.wikimedia.org/p/newsletterExtension )",1427820609,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"More microtasks, if you're still looking for it: T55564 ! and you can find few over here too : T67673#1074667
+
+Basically, search in here for more : https://phabricator.wikimedia.org/maniphest/query/Wi.yo3mXEjwF/",1427484627,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"More microtasks, if you're still looking for it: T55564 ! and you can find few over here too : T67673#1074667",1427484517,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"More microtasks for grabs :  T59414 
+( Will add more soon )! 
+
+
+",1427376286,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1145330, @koustuvcse wrote:
+> okay... I will look into it.. but what is the GMT of the irc?
+
+err. Its just normal humans ( is it? :P ) and bots hanging around in a public chat-place. So,  normal GMT = IRC GMT :). Please click on the date-time link in https://phabricator.wikimedia.org/T76199#1138098 to get exact conversions and maybe, Google a little :) ",1427213688,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,okay... I will look into it.. but what is the GMT of the irc?,1427213339,PHID-USER-muobtocub3solbj4sz5f,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1145323, @koustuvcse wrote:
+> I am new to the irc ecosystem. can you please guide me through it? please
+
+You can find loads of (Mediawiki+IRC) relevant links over here : https://www.mediawiki.org/wiki/MediaWiki_on_IRC ",1427213247,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I am new to the irc ecosystem. can you please guide me through it? please,1427213132,PHID-USER-muobtocub3solbj4sz5f,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Hello! The IRC meeting tomorrow has been shifted to #wikimedia-ect channel. Looking forward to seeing you there. :),1427213058,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"We're holding an IRC meeting on [March 25, at 1700 UTC](http://www.timeanddate.com/worldclock/fixedtime.html?msg=MediaWiki+GSoC%2FOutreachy+IRC+party&iso=20150325T17&p1=%3A&ah=1) for prospective GSoC and Outreachy participants with Wikimedia, on #wikimedia-office channel. Do join us! ",1426943754,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@resheila A project being selected for GSoC or not is decided by the quality of proposals received. If we get a good proposal for the same, we'll keep this project for the upcoming GSoC round, else not. ",1426620405,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Yes, it is. https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015#MediaWiki_extensions",1426620361,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Is this project for sure there in Gsoc?,1426619536,PHID-USER-sututmegiourdiellndf,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"If someone is still in search of microtasks : T72784 
+
+If you think you're enough cool with the codebase and extensions, please follow the link in Quims comment above, and start preparing your proposal. ",1426612367,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Hi @ResheilA thank you for your interest in this project idea. See https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015#Add_your_proposal,1426593919,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hey,
+This project seems interesting, I would like to work on it. And I can make it more efficient and look good. Can any one tell me how to add it for summer of code?  ",1426593626,PHID-USER-sututmegiourdiellndf,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hi @koustuvcse, thank you for your interest in contributing to Wikimedia. Please read the conversation and try to solve one of the microtasks suggested in the task description. If you have questions, just ask.",1426541879,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,this project is cool.. i am from gsoc and i want to work for this project.. the requirements for this project matches my skill set... ,1426536779,PHID-USER-muobtocub3solbj4sz5f,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Ricordisamoa, could be... although the current Newsletters proposal already relies on leveraging existing features. If I understand you correctly, your proposal is based on apparently significant modifications to Flow and the implementation of 'tags', a new type of content in Flow. This might be more work than offering plain wiki pages for newletters, Flow for their discussion pages, Echo for notifications and relatively straightforward special pages for managing subscriptions, and the catalog of newsletters. 
+
+I mean, wiki pages are good for publishing articles, and newsletters are articles. Flow is good for discussion, and ""instantly-locked threads with certain tags through which users would subscribe"" sounds more of a stretch. Besides, wiki pages are a solid and stable basis, with VisualEditor and full-fledged wikitext, while Flow is probably too young to be used as a platform. For a GSoC 2015 project, I think the current proposal is sensible.",1426511488,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Ricordisamoa, could be... although the current Newsletters proposal already relies on leveraging existing features. If I understand you correctly, your proposal is based on apparently significant modifications to Flow and the implementation of 'tags'. This might be more work than offering plain wiki pages for newletters, Flow for their discussion pages, Echo for notifications and relatively straightforward special pages for managing subscriptions and the catalog of newsletters. 
+
+I mean, wiki pages are good for publishing articles, and newsletters are articles. Flow is good for discussion, and ""instantly-locked threads with certain tags through which users would subscribe"" sounds more of a stretch. Besides, wiki pages are a solid and stable basis, with VisualEditor and full-fledged wikitext, while Flow is probably too young to be used as a platform. For a GSoC 2015 project, I think the current proposal is sensible.",1426511390,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I find this a bit redundant to Flow, where newsletters could be cross-wiki instantly-locked threads with certain <spam>[[ //www.mediawiki.org/wiki/User:Ricordisamoa/Flow | tags ]]</spam> through which users would subscribe, leveraging the existing integration with watchlist & Echo.
+Just my 2 cents.",1426507049,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Looks like you've finished most of the microtasks listed in the description. You can leave the echo notif as of now ( as people say : 10:32 PM <legoktm> Echo isn't really easy to work with :/ ) :D. To help you gain expertise more with the code base, consider these easy tasks: T4335, T92728, ",1426485759,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1109430, @01tonythomas wrote:
+> * Design : 
+> https://phabricator.wikimedia.org/T62725 
+> https://phabricator.wikimedia.org/T62725
+-- since it belongs to UI standardization, you can always see how it's one over here ( https://phabricator.wikimedia.org/project/sprint/board/24/query/Z6mtlWoK9aIj/) - or check this one - https://gerrit.wikimedia.org/r/#/c/192282/
+",1426146769,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1109612, @Tinaj1234 wrote:
+> Yes, that's pretty much all about me. Thanks, @Qgil !
+> 
+> Starting with the microtasks. Is there something like claiming the tasks? Do I have to comment under the bug ? Or just start right away with the bug ? 
+
+I think you can just start working on the same, and submit the patch with the correct Bug: <id> in the commit message. www.mediawiki.org/wiki/Gerrit/Tutorial would help you prepare the patch to gerrit",1426087706,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Yes, that's pretty much all about me. Thanks, @Qgil !
+
+Starting with the microtasks. Is there something like claiming the tasks? Do I have to comment under the bug ? Or just start right away with the bug ? ",1426087337,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"See https://www.mediawiki.org/wiki/User:Tinaj1234/MassMessage . She applied but at the end the project was for wctaiwan (who finished the project and has continued contributing until today). With this I mean that @Tinaj1234 is in a good starting point, with good experience and clear perseverance. 
+
+Anyway, let's go back to Extension:Newsletter. Sorry for the interlude.",1426084828,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"See https://www.mediawiki.org/wiki/User:Tinaj1234/MassMessage . She applied but at the end the project was for wctaiwan (who finished the project and has continued contributing until today). With this I mean that @Tinaj1234 is in a good starting point, with good experience and clear perseverance. 
+
+Anyway, let's go back to Extenmsion:Newsletter. Sorry for the interlude.",1426084818,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,See https://www.mediawiki.org/wiki/User:Tinaj1234/MassMessage,1426084534,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I was wondering if @Tinaj1234 was a previous GSoC/OPW intern with us. I didn't find an entry on GSoC Past projects pages though.,1426084198,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hi @Tinaj1234, thank you for your interest in this project. Wow, looking at tasks and commits related to your profile one can clearly see that you are not new here. Very interesting.",1426083980,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas, add it to the task description. :) ",1426083549,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"That looks great. Adding few microtasks. I think most of the work would go similar to the Echo/MassMessage extensions + some SpcialPage works, so hacking on them would get you familiar with the same: 
+https://phabricator.wikimedia.org/T56533 - from echo - this would help you understand the procedure of adding a new notification. 
+* Design : 
+https://phabricator.wikimedia.org/T62725 
+https://phabricator.wikimedia.org/T62725
+* Special Pages hacks: 
+https://phabricator.wikimedia.org/maniphest/query/VXEJAQ_oaxCM/#R
+
+Good luck :) ",1426083443,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I'm very much interested in working on this project. I believe I'm equipped with most of the skills required for the projects. Looking forward to the microtasks !,1426082324,PHID-USER-3pzrnfkwxgwn4v6askvo,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Awesome @01tonythomas! :) 
+
+You and @qgil can hack on it together in the Lyon Hackathon to iron out the details (unless either/both of you have made commitments otherwise :). ",1425994097,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1104168, @Qgil wrote:
+> @01tonythomas, the structure of a newsletter is basically an index of issues, yes, but the design could glorify a bit each issue: the most recent one could be featured at the top and the other ones could be in a list, more compact, but still making room to i.e. a thumbnail if the newsletter contains an image.
+Yeah. the design can come later through the project though. It would be great if we can complete the desired functions in the 2 month period, and polish the design later. 
+> ... Anyway, these are details. I'd rather focus now in finding a main mentor and filling the template in the description.  :)
+Something this cool should not be stalled due to a mentor not turning up, and I am positive to play the mentor role, expecting @legoktm, @parent5446, @Qgil and other devs support ( just like we completed bouncehandler :) )",1425993894,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas, the structure of a newsletter is basically an index of issues, yes, but the design could glorify a bit each issue: the most recent one could be featured at the top and the other ones could be in a list, more compact, but still making room to i.e. a thumbnail if the newsletter contains an image.
+
+... Anyway, these are details. I'd rather focus now in finding a main mentor and filling the template in the description.  :)",1425991356,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Dissecting it for fun :  
+>>! In T76199, @Qgil wrote:
+> Publisher: 
+>A process defining the conditions in which a newsletter can be created, featured, demoted, closed (actions that might imply database changes). Just a basic framework to promote best practices and prevent abuse.
+So that would mean a Special:NewsLetter page, that would be something similar to the LiquidThreads template ( https://www.mediawiki.org/wiki/Extension_talk:LiquidThreads ), and the publisher can ""Create a new Newsletter"" over there, give the subject, and body of his newsletter.
+Below that, the user can see the NewsLetters ( subjects ) he has created followed by the ones he is currently subscribed to. 
+When the publisher clicks on one of the Newsletter he had created, we should have editing options coming up below the suject with JS, I think. The options over there should be simialr to ""New page"", ""View pages"", ""Trash  Newsletter"", ""Stop publishing"" etc.
+
+@qgil: above looks similar to something you expected ?
+",1425920054,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Yes, let's try GSoC/Outreachy first.
+
+I have edited the description adding the template for GSoC / Outreachy. Your help filling skills and microtasks is welcome.
+
+Then we need a technical mentor. As a co-mentor, I can contribute the product and community perspective, but we need a developer as main mentor. ",1425547238,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Pine, it'd take one technical mentor devoting a little of his time for three months to a student. :) ",1425546988,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"What would it take to bump up the priority of this project? This is a high impact project for community communications and wikiprojects, and it's a pity to let this sit here waiting for resources. I'm not sure how many other projects could be considered higher priorities from the consumer and community standpoints.",1425544940,PHID-USER-l7v72q5tq6vg6zclrld6,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@ImPacific, Hello! This project is still under discussion. Although I believe the required skills would be PHP, JavaScript, HTML, CSS. 
+",1425376567,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hi all,
+I find this newsletter extension interesting. I would like to take it up as GSOC project and would like to know what skills would be required to accomplish the required tasks. If required skills are mentioned it would be easier to know whether I meet the minimum skill requirement or not.
+Thanks.",1425375186,PHID-USER-zlgwinzlyyz4gescprcx,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"My only motivation for the centralization is the need to offer a catalog with all the newsletters available in a wiki farm, and the possibility to subscribe/unsubscribe and receive notifications without having to visit or be an active editor of any wiki. If we solve these use cases, then I agree that each wiki community should be able to manage their own newsletters. Anyway, the first prototype will be most likely a single Labs instance, so this is not the most urgent aspect we need to solve.
+
+About notifications, I think we should focus first on strict notifications, a short message telling you that a new issue can be found at URL. Email notifications are a must (directly or via Echo, I don't know) because this is the simplest process that new users and many others will prefer. Web notifications as a logged in Wikimedia user are also good, but make sense only when email is resolved. 
+
+I'm not convinced at all with ""deliveries"", as in the full content of an issue pasted in Talk pages etc. If you are on web, then it is better to go to the canonical source and eventually read / join the discussion in its canonical place. Email deliveries make sense, though, as many people will prefer to read the content at the moment, even if they are offline.",1425036986,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I'm interested in how this will interact with existing notification systems like MassMessage, Echo, and TranslationNotifications. 
+
+MassMessage has a not-yet-super-advertised feature which makes signing up for deliveries significantly easier: <https://test.wikipedia.org/wiki/Yay_mm-ch!>. Creating a central listing of these pages and allowing creation of MediaWiki messages to add descriptions would come close to what is being proposed in M12 I think.",1424984155,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Se4598: If we're accommodating something like the Signpost, then I'd imagine that we'd definitely have to support local distributions. I think the MassMessage approach is a good one, i.e., having centralized but also allowing locally managed mass messaging.",1424983810,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I don't like the idea of centralizing newsletter definition. I'm also for centralizing specific newsletters but let communities handle their own (custom to the wiki) newsletters themself, like it's possible to use MassMessage on any wiki, managed by local admins/senders, but also send messages from Meta to all wikis.
+to clarify: My main point here is not the central place, but who will have which rights and how that integrates with local community wishes.
+
+Also a extension probably worth a look at the features is [[https://www.mediawiki.org/wiki/Extension:TranslationNotifications|Extension:TranslationNotifications]], where you can choose where to recieve the notifications (email, local or a remote wiki).",1424971498,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Good questions, @Parent5446! I have started drafting a more precise plan in the task description, addressing your points and other elemental factors. Feel free to fine tune the plan with questions and edits. ",1424970520,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This definitely seems like a cool idea, and somewhat of an extension of Extension:MassMessage. The only thing to think about is what the interface for authors and administrators would be. Specifically:
+
+  - How do admins define what newsletters are available to users?
+  - Where do authors put drafts, and can other people edit them?
+  - How do authors publish a draft? How do admins define who can publish?
+  - Can authors set a draft to auto-publish at a specific time?
+
+Assuming we attempt to not disturb current workflows, then we'd probably opt for having newsletters on normal wikipages, and rely on page protection (if necessary) to prevent unauthorized editing. Admins would change an interface message containing all the newsletters and the wikipage they are published on. And finally, we have a special page to pull it all together that allows authors to specify when an edition is published.",1424965950,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"https://meta.wikimedia.org/wiki/Grants:IdeaLab/Newsletter_extension_for_MediaWiki
+
+All fronts covered!",1424951395,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Call for a GSoC / Outreachy co-mentor or a hackathon buddy sent to wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2015-February/081022.html,1424949582,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I have marked {T30085} if only to think about this scenario:
+
+# Anonymous user finds an interesting Wikimedia newsletter.
+# Anonymous only needs to submit an email address to subscribe and receive notifications.
+# Eventually, anonymous can complete their Wikimedia username registration.
+
+This is a model that in my opinion works well in many contemporary newsletters from interesting services: the first time they only require an email address (which is a sensible requirement), and once you are in the hook, slowly slowly you feel like more encouraged to be more involved, create your user profile etc.",1424854487,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I have marked {T30085} if only to think about this scenario:
+
+# Anonymous user finds an interesting Wikimedia newsletter.
+# Anonymous only needs to introduce an email address to subscribe and receive notifications.
+# Eventually, anonymous can complete their Wikimedia username registration.
+
+This is a model that in my opinion works well in many contemporary newsletters from interesting services: the first time they only require an email address (which is a sensible requirement), and once you are in the hook, slowly slowly you feel like more encouraged to be more involved, create your user profile etc.",1424854116,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I'm willing to co-mentor this project, which I consider very much needed in Wikimedia and MediaWiki in general. But I need a technical mentor.
+
+If we miss this GSoC/Outreachy round, another possibility is to propose an activity for the Wikimedia Hackathon in Lyon, although in that case I will also need a technical mentor of sorts.
+
+Sigh.",1424694142,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Wikimedia will [[ https://phabricator.wikimedia.org/T921 | apply to Google Summer of Code and Outreachy ]] on Tuesday, February 17. If you want this task to become a featured project idea, please follow [[ https://phabricator.wikimedia.org/project/view/1042/ | these instructions ]]. ",1423662274,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I guess any pixel helps.  :),1417721793,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Alright, but it already has&had a project in BZ/Phab so wondering whether to associate that here. :)",1417701293,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"https://www.mediawiki.org/wiki/Extension:Newsletter is not a real project, just one of my attempts (with @siebrand) to kick this feature in a productive direction.",1417694390,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I assume this is about resource allocation? Or does this also refer to technically enhancing functionality in https://www.mediawiki.org/wiki/Extension:Newsletter (so that project should be associated to this task)?,1417623925,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Create Spelling-Dictionary project,"**Name:** Spelling-Dictionary
+
+**Type of Project:** Project, #spelldict
+
+**Policy:** Visible To Public 
+
+**Description:** Spelling dictionaries for the major languages of the world (English, Italian, French) help make Wikipedia articles in these languages more readable and professional and provide an opportunity for participation in improving spelling. Many languages, however, don’t have spelling dictionaries.
+
+This project aims at developing a collaborative dictionary which shall also have an additional feature of checking spellings of the words. This is to be achieved with the collaborative efforts of the mediawiki community using crowd-sourcing, as a MediaWiki extension integrated with VisualEditor, and possibly using Wikidata as a backend. We need to create something that's useful as VE module.
+
+The essence of the project shall aim to develop an admin panel where the administrator/moderator will be able to manage the submissions: verify the suggested spellings of the words, accept them, reject them, filter and build new versions of the spelling dictionary upon them. A simple start to the project could be by starting with a simple list of words.
+
+The detailed time line can be read [[ http://www.mediawiki.org/wiki/User:Ankitashukla/Proposal | here ]]",1417122558,PHID-USER-vktcpyhhgydpo36f44uz,PHID-TASK-6gmrv6d3roeydcelmnyh,task_description,resolved
+Create Spelling-Dictionary project,Please also add yourself to the project members to receive updates. See https://www.mediawiki.org/wiki/Phabricator/Help#Receiving_updates_and_notifications for more information.,1417619687,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Create Spelling-Dictionary project,"#spelldict created. If for some reason you want to rename it, please check https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Renaming_projects
+
+Enjoy!",1417602843,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Create Spelling-Dictionary project,I'm OK with this name.,1417592846,PHID-USER-abr5ge6gl2ovg7jokpst,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Create Spelling-Dictionary project,">>! In T76160#792226, @Qgil wrote:
+> @amire80, @kartikmistry, are you ok with this name of project? CCing @Jdforrester-WMF as well, since this is a project related to VisualEditor.
+
+Ping? I want to create this project today, if possible.",1417592611,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Create Spelling-Dictionary project,"@amire80, @kartikmistry, are you ok with this name of project? CCing @Jdforrester-WMF as well, since this is a project related to VisualEditor.",1417123002,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,The job: [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/ | browsertests-VisualEditor-language-screenshot-windows_8.1-firefox ]],1417084690,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-sgoczofqmqi4d2v3nizb,task_description,resolved
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,That job has been deleted by https://gerrit.wikimedia.org/r/#/c/183480/ which replaced it with a mac os version.,1421169278,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"Most of the jobs is green, but a few failed.
+
+https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/",1417877349,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"The job is green now.
+
+https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/LANGUAGE_SCREENSHOT_CODE=ar,label=contintLabsSlave%20&&%20UbuntuTrusty/7/consoleFull",1417612127,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"The only [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/LANGUAGE_SCREENSHOT_CODE=ar,label=contintLabsSlave%20&&%20UbuntuTrusty/4/console | failing scenario ]] at the moment is caused by T76134.",1417101292,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"Change 176235 merged by jenkins-bot:
+[BrowserTest] Fixed a couple of page elements
+
+[[https://gerrit.wikimedia.org/r/176235]]",1417088814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"Change 176235 had a related patch set uploaded (by Zfilipin):
+[BrowserTest] Fixed a couple of page elements
+
+[[https://gerrit.wikimedia.org/r/176235]]
+
+#patch-for-review",1417084758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+[Regression wmf10] <visualeditor-formatdropdown-format-blockquote> is displayed in Headings menu ,"Open VE-> Heading - under sub-heading 4, visualeditor-formatdropdown-format-blockquote will be displayed from <span class=""oo-ui-tool-title-text"">&lt;visualeditor-formatdropdown-format-blockquote&gt;</span>(see the attached screenshot).
+{F16461}",1417031233,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ymyyonb4npnvudsmny5o,task_description,declined
+[Regression wmf10] <visualeditor-formatdropdown-format-blockquote> is displayed in Headings menu ,This functionality was released in wmf10 so shouldn't show up in wmf9 wikis; on MediaWiki.org and test2.wikipedia.org it appears fine for me (and also on Beta Labs). Deployment issue?,1417228531,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ymyyonb4npnvudsmny5o,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"There's a range of different loading indicators in Wikimedia Foundation products. 
+Let's unify them.
+
+=== Standard progress indicators
+==== Progress bar (application, elevated above view)
+- **VisualEditor** -   [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=widgets&theme=wikimediaui&direction=ltr&platform=desktop#Progress-bar | ProgressBarWidget (OOUI widget)]] as elevated application loading indicator
+{F33930009 width=50%}
+
+==== Progress indicator (in page)
+- **Three (bouncing) dots** for in-view loading content, for example RCFilters
+  [[ https://codepen.io/Volker_E/pen/yqNXMe | CodePen with dots indicator example at 16px ]]. Depending on context product designers can also choose to go for 12px dot sizes. 
+
+
+---
+
+=== //Outdated, non-standard// progress indicators in Foundation products
+
+**Content translation** - loading article (content). 
+{F3067365}
+
+**Notifications** - loading notifications (content) 
+{F3067366}
+
+**Structured Discussion** - loading more topics (content) 
+|{F27614503}|{F3067367} 
+
+loading contents on infinite scroll
+{F3068028}
+
+**MobileFrontend** - loading ""nearby"" articles (content) 
+|{F27614726}|{F3067368}
+
+---
+**Related notes:**
+- User:Splarka has done some analysis [[ https://www.mediawiki.org/wiki/User:Splarka/Throbber | here ]] to see how loaders work in different colored backgrounds. 
+- Relevant [[ https://phabricator.wikimedia.org/T95137 | task about loading indicators should accelerate as it nears completion ]]
+- {T78062}
+
+",1416989044,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_description,open
+Loading indicators / Progress indicators are inconsistent. ,"hi @Volker_E - here's an example on Growth of how we are using skeleton shimmer instead of the loading indicators due to the large area of content elements all being loaded at different times (Image, article title, extract, page views):
+{F33930219}",1606840372,PHID-USER-ejp5b4zwkqh7wf62j2gh,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,CodePen now also includes small variant and variant with inverted colors for dark background usage.,1532003120,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"A follow-up note on mobile app discussion at T75972#845549
+Apps should make use of the OS specific loading indicators if any possible. ",1531397743,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"Ok, I think //Base30 is a good compromise// as long as designers are aware of the context and consider upping contrast if indicator is used on a dark(er) background in order to stay well recognizable for affected users.",1531393168,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,">>! In T75972#4417813, @Volker_E wrote:
+> From a conversation in Contributors Design meeting this week, let's declare the 3 dots animation our in-view loading animation. 
+> One small amendment that we should be making is increasing the contrast slightly, from `@colorGray12` (`#c8ccd1`) currently to `#54595d` in order to ensure visibility.
+> We can still revisit this later for improvements or alternative animation proposals.
+
+I'm ok in increasing the contrast, but using Base20 (#54595d) seems a bit too dark for a non-interactive element that we want to communicate background activity. I made examples for [[ https://codepen.io/anon/pen/WKvGRj | Base20 ]], [[ https://codepen.io/anon/pen/BPNLZQ | Base30 ]] and [[ https://codepen.io/anon/pen/QBbKaq | Base50 ]]. I think that Base30 (#72777d) could be a good option if we want good-enough contrast without attracting too much attention.",1531393001,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"From a conversation in Contributors Design meeting this week, let's declare the 3 dots animation our in-view loading animation. 
+One small amendment that we should be making is increasing the contrast slightly, from `@colorGray12` (`#c8ccd1`) currently to `#54595d` in order to ensure visibility.
+We can still revisit this later for improvements or alternative animation proposals.",1531347981,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,I changed from indeterminate to just a discussion of loading indicators so we can look at loading indicators as a whole. Documented here on MW: https://www.mediawiki.org/wiki/Wikimedia_User_Interface/Use_cases/Loading_Indicators,1449814259,PHID-USER-tjeabpzbwsqw3xciydvb,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,Over on T61699 I've got a hi-dpi update to jquery.spinner in MW core that doesn't change its design -- should I go ahead and try to land that as-is for now or wait on this design to replace it?,1436477741,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"@prtksxna yes, here's my first cut http://nirzar.github.io/prototypes/ui/primary-button-loading.html",1436477184,PHID-USER-ed7ta55b47bd3ag6cnuw,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"@nirzar, didn't you at some point make prototypes of this indicator along with buttons? Is this same/related? Could you please add a link to that task?",1435823360,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"sure, @Pginer-WMF has designs for an in-page indeterminate loading indicator, I'd like for us to consistently use this when we have in-page indeterminate loaders. On the app this could be… loading search results, long articles, large images, nearby lists, etc. ",1418671203,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,">>! In T75972#848540, @Jaredzimmerman-WMF wrote:
+> @Deskana, There are other other in-page loaders that you see occasionally, are these all inherited from mobile web?
+
+From the engineering perspective, we don't inherit anything about our UI from mobile web or desktop. It's nontrivial to inherit UI elements from mobile web for a variety of technological reasons. It's possible that they were designed the same way and therefore look very similar, however. You'd have to ask your designers about that. :-)
+
+> As far as inconsistency with Material Design or iOS guidelines, I feel we've already settled on a look and feel that is wikimedia, rather than being platform specific. I know that we've made subtle platform adjustments, but overall we've diverged pretty far from each platform's design in order to have something that is unique to the application. 
+
+Yes and no. We use material design icons in the Android app almost everywhere for things like search, table of contents, hamburger menu, etc. We also use an Android-spec progress bar for page load indication. For pretty routine operations like this, it means if someone's used another app on their phone then they reasonably know what to expect from ours. As mentioned, I would be reluctant to break that pattern.
+
+In other places, we don't pay much attention to their guidelines (e.g. progressive action buttons in the editing workflow are not in line with Android). For editing I think that makes sense, because the editing workflow is so unique to our application.
+
+But anyway, this is a pretty high level discussion. To figure out our next steps, could you say specifically what you're proposing we do in the iOS app and the Android app? Thanks!",1418670441,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"@Deskana, There are other other in-page loaders that you see occasionally, are these all inherited from mobile web? As far as inconsistency with Material Design or iOS guidelines, I feel we've already settled on a look and feel that is wikimedia, rather than being platform specific. I know that we've made subtle platform adjustments, but overall we've diverged pretty far from each platform's design in order to have something that is unique to the application. ",1418669449,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"This doesn't make much sense as a task for mobile apps. For system controls like loading indicators, it's much important to use the platform's built-in controls rather than making our own arbitrary ones, because our app should be consistent with other apps in the platform.
+
+For example, the Android platform has the Toolbar class (which we use for our toolbar) which has a built in progress bar; that's the standard paradigm on the platform, and we'd need a //really// good reason to intentionally make our apps incompatible with material design.",1418448174,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"Here are some details:
+- [[ http://codepen.io/anon/pen/VYYvXM | Live example ]]
+- [[ https://gerrit.wikimedia.org/r/#/c/144873/ | Patchset from the Language team implementing it in Content Translation]]
+- More details in [[ https://trello.com/c/2u8W6qn8/53-consistent-load-more-animation-in-core | this Trello card ]]
+
+{F20240}",1418154713,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"
+
+
+- [[ http://codepen.io/anon/pen/VYYvXM | Live example ]]
+- [[ https://gerrit.wikimedia.org/r/#/c/144873/ | Patchset from the Language team implementing it in Content Translation]]
+- More details in [[ https://trello.com/c/2u8W6qn8/53-consistent-load-more-animation-in-core | this Trello card ]]
+",1418154686,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,@pginer-wmf can you link to the indeterminate loaders that are being used in flow/CX please?,1417811605,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+A message key appears instead of the actual message in visualeditor-dialog-meta-settings-newsectioneditlink-help,"In the help bubble that shows the message visualeditor-dialog-meta-settings-newsectioneditlink-help, the message ""vector-view-edit"" is mentioned. It is supposed to show ""Edit"" to the user, but it shows ""[vector-view-edit]"" instead. The value of the message should probably be sent as a parameter instead of using {{int:vector-view-edit}}.",1416984339,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-zmcluk2i4zmrgthivhmp,task_description,resolved
+A message key appears instead of the actual message in visualeditor-dialog-meta-settings-newsectioneditlink-help,"Change 176071 merged by jenkins-bot:
+i18n: Pass value to <visualeditor-dialog-meta-settings-newsectioneditlink-help>
+
+[[https://gerrit.wikimedia.org/r/176071]]",1417462535,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zmcluk2i4zmrgthivhmp,task_subcomment,NA
+A message key appears instead of the actual message in visualeditor-dialog-meta-settings-newsectioneditlink-help,"Change 176071 had a related patch set uploaded (by Jforrester):
+i18n: Pass value to <visualeditor-dialog-meta-settings-newsectioneditlink-help>
+
+[[https://gerrit.wikimedia.org/r/176071]]
+
+#patch-for-review",1417036737,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zmcluk2i4zmrgthivhmp,task_subcomment,NA
+Create technical-debt project,"Name: technical-debt
+Type of project: Tag
+Description:
+
+Technical debt (also known as design debt[1] or code debt) is a recent metaphor referring to the eventual consequences of poor system design, software architecture or software development within a codebase. The debt can be thought of as work that needs to be done before a particular job can be considered complete or proper. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on. Unaddressed technical debt increases software entropy. - https://en.wikipedia.org/wiki/Technical_debt
+Examples: Missing unit tests, duplicate code.
+",1416928132,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-ncbhpeaekx466zjaq6at,task_description,resolved
+Create technical-debt project,We need to tag existing bugs with the keyword. But this ticket can be closed. Thanks for creating the keyword.,1418076477,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"What needs to be done here for Wikidata, or can we mark this as Resolved?",1418075295,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,">>! In T75892#831488, @Qgil wrote:
+>> Editable By VisualEditor (Project)
+> 
+> You do it.  :)
+
+Done: https://phabricator.wikimedia.org/project/view/609/
+I also merged all the MobileFrontend tasks into it, archived that project with a note, and added the old projects' tags to the new one.",1418075139,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"> Editable By VisualEditor (Project)
+
+You do it.  :)",1418071319,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,">>! In T75892#824439, @Qgil wrote:
+>>>! In T75892#790593, @Jdforrester-WMF wrote:
+>> Rather than create a new project, just re-label one of the existing two and be done with it?
+> 
+> Should we go for renaming #VisualEditor-TechnicalDebt ?
+
+That would involve the fewest tasks needing to have a project added, so WFM. Let's do it?",1418054800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,">>! In T75892#790593, @Jdforrester-WMF wrote:
+> Rather than create a new project, just re-label one of the existing two and be done with it?
+
+Should we go for renaming #VisualEditor-TechnicalDebt ?",1418031720,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,">>! In T75892#793155, @JanZerebecki wrote:
+> This ""old bugs and feature requests that are standing somewhere and we never had the time to address"" definitively does not describe _technical_ debt. Some specific technical debt may at the same time also be a functionality bug, but neither is a sufficient condition for the other.
+> 
+> See the link to en.wp in the description. do you think that does not sufficiently define the term?
+
+Indeed, the definition on enwiki is very badly worded. Technical debt covers ""poor"" decisions about code structure, but it also covers great decisions that turn out five years later to be inadequate for future needs. //E.g.// a reasonable technical debt bug would be ""Have MediaWiki use a NoSQL rather than RDBMS back-end""; the ""decision"" not to use NoSQL never happened, because MediaWiki's design and creation pre-dates that technology.
+
+Some real-world examples of types from VisualEditor: T51439 is (was) a criticism of our code that we made when we built the original; T49344 is a subsequent decision about what architecture would be better given developing needs.",1417198682,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"Yes, yes, I agree with you and I am glad that we have such a good description in Wikipedia. I wasn't referring to the theoretical description but to the deviation in regular use that might occur if we don't pay attention.",1417176934,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"This ""old bugs and feature requests that are standing somewhere and we never had the time to address"" definitively does not describe _technical_ debt. Some specific technical debt may at the same time also be a functionality bug, but neither is a sufficient condition for the other.
+
+See the link to en.wp in the description. do you think that does not sufficiently define the term?",1417175501,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"+1 to renaming an existing project and consolidating the rest (tracking bug etc) around it.
+
++1 also on sharing a clear definition of what is and what is not ""technical debt"". Frequently I have heard this term in product management and management management conversations with the meaning of ""old bugs and feature requests that are standing somewhere and we never had the time to address"".",1417161566,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"Rather than create a new project, just re-label one of the existing two and be done with it?",1417073613,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"Shouldn't we maybe just convert T2700 from a tracking bug into a [[ https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Type_of_project | tag project ]]? :)
+
+Also wondering if that means that tasks in #VisualEditor-TechnicalDebt should be moved to the generic VisualEditor project && that new Technical-Debt tag project (or whatever it will be called). 
+And maybe same for #MobileFrontend-Hygiene ?",1417059498,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"+1, this would be useful. How much tech debt vs. feature work gets done is a sort of project health metric (as is the number of tech debt tickets, of course). A team might decide to spend X% of its time on working off tech debt, etc. An explicit way of marking tech debt tasks would make it much easier to track that.",1416953103,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Cancel button does not work for Insert-Template and some Cite options in VisualEditor in Monobook,"The dialog boxes that have extremely small font(T75800)  get stuck on the screen when Cancel button is clicked. 
+
+1. VE in beta with redirect=no&veaction=edit&useskin=monobook
+2. Insert -> Template - click Cancel- nothing happens; the dialog box gets stuck on the screen, need to refresh.
+
+The same issue with Cancel in Cite-Website, Book, News, Journal.
+ ",1416870621,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-twc6oxttivmbeivgzrtf,task_description,resolved
+Update bits of VisualEditor still referring to Bugzilla,"The ""Leave feedback"" option in VE allows to report a bug:
+The ""list of known bugs"" link should point to its equivalent here;
+The ""I checked, report a new bug"" button needs to point to the (possibly partially pre-filled) task creation form here.
+",1416833813,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-h4m4lscojm4qbgfbthk7,task_description,resolved
+Update bits of VisualEditor still referring to Bugzilla,"Links refer to Phabricator - however, what happened to the color of links? 
+
+From color: #0b0080; in test2 and production to color: #362b36 in beta? 
+https://phabricator.wikimedia.org/T85857 is filed.",1420492721,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"Change 182464 merged by jenkins-bot:
+Update bugzilla links to phabricator
+
+[[https://gerrit.wikimedia.org/r/182464]]",1420459663,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"Change 182462 merged by jenkins-bot:
+Update bugzilla links to phabricator
+
+[[https://gerrit.wikimedia.org/r/182462]]",1420459657,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"Change 182464 had a related patch set uploaded (by Alex Monk):
+Update bugzilla links to phabricator
+
+[[https://gerrit.wikimedia.org/r/182464]]
+
+#patch-for-review",1420214863,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"Change 182462 had a related patch set uploaded (by Alex Monk):
+Update bugzilla links to phabricator
+
+[[https://gerrit.wikimedia.org/r/182462]]
+
+#patch-for-review",1420213367,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"To be precise, the 2 messages are MediaWiki:Feedback-bugornote and MediaWiki:Feedback-bugcheck.
+",1420203433,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"The ""Alternative text"" label in the VisualEditor media adding dialog is not entirely clear to people who aren't familiar with web authoring and accessibility technologies. It would be useful to add a little explanation in a small font near that label, that would explain what is alternative text for and how to write it so it will be really useful.",1416831637,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-rqmz2t77d5756bkn77xp,task_description,resolved
+Add an explanation about Alternative text in the media adding dialog,Checked in betalabs. ,1422916476,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"Change 187447 merged by jenkins-bot:
+Add help icon for FieldsetLayout
+
+[[https://gerrit.wikimedia.org/r/187447]]",1422571846,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"Change 187447 had a related patch set uploaded (by Mooeypoo):
+Add help icon for FieldsetLayout
+
+[[https://gerrit.wikimedia.org/r/187447]]
+
+#patch-for-review",1422557955,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"Change 186108 merged by jenkins-bot:
+MWMediaDialog: Add contextual help for controls
+
+[[https://gerrit.wikimedia.org/r/186108]]",1422488523,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"Change 186108 had a related patch set uploaded (by Jforrester):
+MWMediaDialog: Add contextual help for controls
+
+[[https://gerrit.wikimedia.org/r/186108]]
+
+#patch-for-review",1421798146,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Decide what to do with tracking bugs,"There are a lot of them, see T4007 and the #tracking tag.
+
+I suppose they should eventually all be closed and replaced with tags or projects.
+
+See also T266.",1416790347,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-flyugauog5dd6v4unsi7,task_description,resolved
+Decide what to do with tracking bugs,"Removed {{draft}}, linked from https://www.mediawiki.org/w/index.php?title=Phabricator%2FProject_management&diff=1426794&oldid=1425629
+
+Closing as resolved.",1425050149,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,Draft: https://www.mediawiki.org/wiki/Phabricator/Project_management/Tracking_tasks,1424897051,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"Copying my steps from T86232#1034556:
+* Requested project has been created: MediaWiki-jQuery-Tablesorter
+* Dependency tasks of tracking task 33601 have been added to the new project.
+* Subscribers of 33601 have been added as project members to the new project.
+* Tracking task 33601 has been closed and its summary updated. Also added new summary as a comment as mail notification settings differ among folks.",1423759341,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,">>! In T75703#936981, @Qgil wrote:
+> So what about this guideline:
+> 
+> * Subtasks and blockers of real tasks are totally fine.
+> * If someone wants to convert a tracking task in a project, they just need to follow the regular process to request a new project, announcing the proposal in the own tracking task. 
+> * New tracking tasks are discouraged. If we find one, let's propose the promoter(s) to create a project instead.
+
++1. Should move these bullet points plus the workaround in T75703#937036 to some wikipage. 
+Probably some subpage of https://www.mediawiki.org/wiki/Phabricator/Project_management and linking from ""Tasks cannot be worked on yet"" (covers dependencies) or ""Scope of tasks"" (covers subtasks)?
+
+Should also note that the actual work (mass-add new project to open and closed tasks; close old tracking bug by editing description saying ""This task is not used anymore for tracking. Tickets have been moved to project #Foobar"") to convert a tracking task to a project could be done by the requester having batch-edit permissions.
+Might also want to mention advantages: Workboard for project.
+
+After moving this to a wikipage I consider this task done.",1423175791,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,">>! In T75703#1006222, @Ciencia_Al_Poder wrote:
+> Now in Phabricator I find it a lot harder to do.
+
+See T33.",1422737387,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"Adding a bug to a tracking bug in bugzilla was easy, because there were 2 ways of doing that: from the tracking bug or from the bug itself. And it was a matter of adding the bug number in the comma-separated list of bug numbers.
+
+Now in Phabricator I find it a lot harder to do. You can only do that from the tracking task, which usually contains **tons** of blocked tasks (see T2384). It presents you a search to type the task number or description, and below the interminable list of blocked tasks, and you need to scroll until the end of the list to add the new task. I find it crappy enough to comment this situation.
+
+This situation could be alleviated if Phabricator allowed to edit the blocking tasks from the inverse perspective (add the tracking task from the child task itself) as Bugzilla allowed.
+
+Converting tracking tasks into projects would be more helpful",1422708507,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"# Select all the blocking tasks
+# Paste in Gedit or equivalent
+# Save as csv
+# Open in Calc or equivalent, using ""space"" as separator
+# Copy the column with the reference numbers
+# Paste it in Gedit or equivalent
+# Ctrl-H to substitute all colons by commas
+# Copy the list of task numbers with commas
+# Paste it in ""Task IDs"" field in Maniphest advanced search and hit ""Search""
+
+Sounds complicated but it takes just a couple of minutes. See an example from T2745 to https://phabricator.wikimedia.org/maniphest/query/bKU3kGuAWKFB/#R (278 tasks)
+",1419022698,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"# Select all the blocking tasks
+# Paste in Gedit or equivalent
+# Save as csv
+# Open in Calc or equivalent, using ""space"" as separator
+# Copy the column with the reference numbers
+# Paste it in Gedit or equivalent
+# Ctrl-H to substitute all colons by commas
+# Copy the list of task numbers with commas
+# Paste it in ""Task IDs"" field in Maniphest advanced search and hit ""Search""
+
+Sounds complicated it takes just a couple of minutes. See an example from T2745 to https://phabricator.wikimedia.org/maniphest/query/bKU3kGuAWKFB/#R (278 tasks)
+",1419022657,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"# Select all the blocking tasks
+# Paste in Gedit or equivalent
+# Save as csv
+# Open in Calc or equivalent, using ""space"" as separator
+# Copy the column with the reference numbers
+# Paste it in Gedit or equivalent
+# Ctrl-H to substitute all colons by commas
+# Copy the list of task numbers with commas
+# Paste it in ""Task ID"" field in Maniphest advanced search and hit ""Search""
+
+Sounds complicated it takes just a couple of minutes. See an example from T2745 to https://phabricator.wikimedia.org/maniphest/query/bKU3kGuAWKFB/#R (278 tasks)
+",1419022631,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,">>! In T75703#936981, @Qgil wrote:
+> So what about this guideline:
+> 
+> * Subtasks and blockers of real tasks are totally fine.
+> * If someone wants to convert a tracking task in a project, they just need to follow the regular process to request a new project, announcing the proposal in the own tracking task. 
+> * New tracking tasks are discouraged. If we find one, let's propose the promoter(s) to create a project instead.
+
+Sounds good. Note that the line between real tasks and tracking bugs can get a little blurry, though — e.g. ""Get Xyz ready to go"" or ""Release Abc version 1.0"", so some judgement may be needed. ",1419021948,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,">>! In T75703#936775, @Aklapper wrote:
+> I wonder if there's a sane way to get all the tasks under ""Blocked by"" on (e.g. T2745 for T78670) into a ""Maniphest search query"" format to then use the ""Batch editing"" mode and mass-add a newly created project tag. I am afraid there isn't, which will make converting really cumbersome.
+> 
+> https://phabricator.wikimedia.org/maniphest/query/advanced/ does not offer a field ""Blocking: T9876543"" either.
+> 
+> Even if I had a list, ""Batch editing"" does not offer a ""Remove Blocker bug T9876543"" either so I guess I'd just leave that as is, and add a comment to the tracking bug that it's replaced by a project tag and close it as invalid.
+> 
+> Meh.
+
+Yeah, I filed this upstream but I'm on my phone right now so can't find it. Consequently all the VisualEditor tracking bugs are waiting for me to have some time and being bored as hell. :-)",1419021824,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"So what about this guideline:
+
+* Subtasks and blockers of real tasks are totally fine.
+* If someone wants to convert a tracking task in a project, they just need to follow the regular process to request a new project, announcing the proposal in the own tracking task. 
+* New tracking tasks are discouraged. If we find one, let's propose the promoter(s) to create a project instead.",1419021397,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I wonder if there's a sane way to get all the tasks under ""Blocked by"" on (e.g. T2745 for T78670) into a ""Maniphest search query"" format to then use the ""Batch editing"" mode and mass-add a newly created project tag. I am afraid there isn't, which will make converting really cumbersome.
+
+https://phabricator.wikimedia.org/maniphest/query/advanced/ does not offer a field ""Blocking: T9876543"" either.
+
+Even if I had a list, ""Batch editing"" does not offer a ""Remove Blocker bug T9876543"" either so I guess I'd just leave that as is, and add a comment to the tracking bug that it's replaced by a project tag and close it as invalid.
+
+Meh.",1419017988,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"@Lydia_Pintscher: Yes, sorry, I meant T54385. Comment edited.",1418039157,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,@Qgil: I think that is the wrong ticket id you linked? We have a few tasks in Wikidata that are not worth their own project like T73519 but would still be good to mark as tracking somehow. The tag works fine for that for me.,1418038537,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I think we could decide the deprecation of the Tracking tag, but without getting too obsessed about it. The idea is that tracking tasks are either converted to projects or to regular tasks with blockers, having a chance to have more projects associated with them now.
+
+#tracking includes a list of recent changes, which is useful to see which tracking tasks are seeing activity. We could start with these. 
+
+For instance, {T37707} has Tracking and an own project, so Tracking could be safely removed there. 
+
+T54385 is a less clear candidate for an own project, but it seems that its scope fall almost entirely within Wikidata/Wikibase. We could ask @Lydia_Pintscher what does she prefer to do with it.
+
+",1418038918,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I think we could decide the deprecation of the Tracking tag, but without getting too obsessed about it. The idea is that tracking tasks are either converted to projects or to regular tasks with blockers, having a chance to have more projects associated with them now.
+
+#tracking includes a list of recent changes, which is useful to see which tracking tasks are seeing activity. We could start with these. 
+
+For instance, {T54385} has Tracking and an own project, so Tracking could be safely removed there. 
+
+T37707 is a less clear candidate for an own project, but it seems that its scope fall almost entirely within Wikidata/Wikibase. We could ask @Lydia_Pintscher what does she prefer to do with it.
+
+",1418038897,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I think we could decide the deprecation of the Tracking tag, but without getting too obsessed about it. The idea is that tracking tasks are either converted to projects or to regular tasks with blockers, having a chance to have more projects associated with them now.
+
+#tracking includes a list of recent changes, which is useful to see which tracking tasks are seeing activity. We could start with these. 
+
+For instance, {T37707} has Tracking and an own project, so Tracking could be safely removed there. 
+
+T37707 is a less clear candidate for an own project, but it seems that its scope fall almost entirely within Wikidata/Wikibase. We could ask @Lydia_Pintscher what does she prefer to do with it.
+
+",1418033300,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I'm not sure if this needs a ""generic solution"". I'm curious to see which tracking tasks will actually see activity (adding and removing items) and which ones were and are mostly forgotten.
+
+In general and when still actively used, tracking tasks sound like something to convert into tag projects (as tracking tasks were a workaround in Bugzilla to emulate keywords; keywords needed to be set up by a Bugzilla admin who might have asked questions why something is actually needed, while some folks loved to just go ahead and categorize items).",1417218535,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"In #VisualEditor I'm in the process of converting them all into projects, which is quite painful without the bulk edit right. :-)",1416791649,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","Goal:
+
+Save page with edit summary ""Copyedit"".
+
+
+(Almost) result:
+
+Save page with no edit summary, but with the word 'Copyedit' added in the middle of the link that I had just fixed.
+
+
+Steps to reproduce:
+
+1) Edit any page.
+
+2) Click the save button.
+
+3) Start typing your edit summary.
+
+4) Stop typing your edit summary and start backspacing.
+
+5) Click inside the Save dialog.
+
+6) Type your edit summary again.
+
+7) File another bug in Bugzilla.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416516180,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uonptigegjibdzpnxm6t,task_description,resolved
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","Change 182976 merged by jenkins-bot:
+Re-focus edit summary input when save dialog is ready
+
+[[https://gerrit.wikimedia.org/r/182976]]",1420549052,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","Change 182976 had a related patch set uploaded (by Alex Monk):
+Re-focus edit summary input when save dialog is ready
+
+[[https://gerrit.wikimedia.org/r/182976]]
+
+#patch-for-review",1420505772,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog",Oh I did manage to reproduce what I think is this issue when I tried it on testwiki though - the focus moves from the summary field to somewhere else when I press save again.,1420504423,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","The cursor always goes back to the summary field for me, after following those instructions.",1420504284,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","Tricky to reproduce - happens only in test2: 
+
+- make some changes on a page - click Save
+- in 'Save your changes dialog box' check(or uncheck) 'This is minor edit' check box - notice that the cursor will be gone from the Summary area.
+- click 'Resume editing' and make some changes again
+- click Save - the cursor won't be placed in the Summary area anymore",1417567033,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog",Did anyone other than the reporter ever manage to reproduce this issue?,1417481630,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","James also tried this and couldn't reproduce it. I think I may have asked someone else as well since... not sure.
+
+If anything caused this, it's probably https://gerrit.wikimedia.org/r/172658/ (and -maybe- another thing related to the de-isolation of windows?)",1416863565,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog",Worksforme...,1416528682,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog",Is this a regression? I thought it used to work…,1416524958,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+VisualEditor: mw.Target / ViewPageTarget re-write,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416365160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e3w6zshniruifvkfks6d,task_description,open
+VisualEditor: mw.Target / ViewPageTarget re-write,"Not really a tracking bug, on reflection.",1416436188,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e3w6zshniruifvkfks6d,task_subcomment,NA
+VisualEditor: Decide whether this.active should be in mw.Target or mw.ViewPageTarget,"Right now ViewPageTarget defines this.active, but it's set to true by mw.Target. This is horrible. The obvious fix is to push the setting to true down to ViewPageTarget, but we should consider whether the Target class itself should have some sort of active state.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416364980,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-x62ljudld7jl6ovaojqy,task_description,open
+VisualEditor: Improve FileDropHandler API,"From comments at https://gerrit.wikimedia.org/r/#/c/173296/1/src/ui/filedrophandlers/ve.ui.DSVFileDropHandler.js :
+
+* Right now every child class calls createProgress( insertableDataDeferred.promise() ); in its process() method. This seems like something that should be in the base class instead. Would you ever want to not do that, or pass a different promise?
+
+* Child classes should not have to override abort() just to add this.reader.abort();, because this.reader is added by the base class.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416338940,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2aag2u6vtt53677npv2w,task_description,open
+VisualEditor: Warn if editing a citation that is used multiple times,"The fix 52792 will display a warning ""This reference is used [n] times on this page."" when editing Basic citation only. 
+
+Apply the same warning when editing mutliple instances of any kind of citations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416331860,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-a44mepuutxluyfml3j5g,task_description,open
+VisualEditor: Warn if editing a citation that is used multiple times,"This is the same issue as editing the group of a non-basic citation.
+
+It's possible by simply selecting the reference, opening the menu and selecting 'Basic' (even if it isn't basic).",1416345549,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-a44mepuutxluyfml3j5g,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"Hi, I'm posting this request on behalf of the https://ca.wikiquote.org admins. They want to bring VisualEditor to their users. We have discussed this idea, and I see no problem at all. At the end, most articles there have a very simple structure with initial paragraph, some pictures, and then the same template used always for adding quotes.
+
+I would be happy to help adding template data to the templates affected, and act as bridge in this test.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://ca.wikiquote.org/wiki/Viquidites:La_taverna#Editor_Visual_a_Viquidites",1416135000,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_description,resolved
+Enable VisualEditor in ca.wikiquote.org,Indeed. Sorry for the mistake and thank you for fixing it so quick.,1416330309,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,This was due to an edit to the {{Cita}} template. I've reverted it. https://ca.wikiquote.org/w/index.php?title=Plantilla:Cita&diff=50689,1416330141,PHID-USER-lsveyqlsb4acoowxr5yj,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"PLEASE REVERT THIS CHANGE ASAP
+
+Something very weird is happening. In all pages ""}}}}}}"" appears instead of quotes. I mean all pages, not the ones edited with VE. Seeing the source and the history, I can't find any explanation.
+
+See for instance https://ca.wikiquote.org/wiki/Pensaments_den_Goethe",1416329864,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"Now done:
+https://ca.wikiquote.org/w/index.php?title=Especial:Canvis_recents&tagfilter=visualeditor",1416326792,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"Change 174036 merged by jenkins-bot:
+Enable VisualEditor by default on Catalan Wikiquote (cawikiquote)
+
+https://gerrit.wikimedia.org/r/174036",1416326446,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"Change 174036 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on Catalan Wikiquote (cawikiquote)
+
+https://gerrit.wikimedia.org/r/174036",1416271699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"(In reply to Glaisher from comment #1)
+> Posting a link here to community consensus might be helpful.
+
+Fair enough. I posted https://ca.wikiquote.org/wiki/Viquidites:La_taverna#Editor_Visual_a_Viquidites
+
+Note that the ca.wikiquote.org community of regular contributors is very small (this is why they are so interested in VisualEditor). Docosong is the only admin. Unapersona is the second most active contributor currently. ESM, KRLS, and ArnauGir are veteran contributors (the last two also ca.wiki admins helping bridging this project with the rest of Catalan-speaking sister projects).
+
+You can wait for more voices, or you can trust the current result.  :)
+
+> Also should it
+> be enabled by default or should it be enabled as a Beta Feature?
+
+In our discussion at the conference, they said that they preferred to have it side by side next to the ""edit source"", because new users are very unlikely to find the option to enable it, or even know that such thing exists.",1416265635,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,Posting a link here to community consensus might be helpful. Also should it be enabled by default or should it be enabled as a Beta Feature?,1416149548,PHID-USER-lsveyqlsb4acoowxr5yj,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+VisualEditor: Undefined index: newtimestamp in …/ApiVisualEditorEdit.php,"Nov 15 12:32:30 mw1023:  #012Notice: Undefined index: newtimestamp in /srv/mediawiki/php-1.25wmf7/extensions/VisualEditor/ApiVisualEditorEdit.php on line 137
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1416055080,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-devcuj6oy6zi6ehpdryq,task_description,resolved
+VisualEditor: Undefined index: newtimestamp in …/ApiVisualEditorEdit.php,"Change 173747 merged by jenkins-bot:
+Don't try to get newtimestamp from edit if no change was made
+
+https://gerrit.wikimedia.org/r/173747",1416246526,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-devcuj6oy6zi6ehpdryq,task_subcomment,NA
+VisualEditor: Undefined index: newtimestamp in …/ApiVisualEditorEdit.php,"Change 173747 had a related patch set uploaded by Alex Monk:
+Don't try to get newtimestamp from edit if no change was made
+
+https://gerrit.wikimedia.org/r/173747",1416186618,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-devcuj6oy6zi6ehpdryq,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","edit a page on beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click the Link inspector. Note the local link created.
+
+Click Remove. 
+
+Click the Link inspector again. 
+
+See an entirely different UI showing ""New page/Matching pages""
+
+Click in the ContentEditable part. ""New page/Matching pages"" UI disappears. 
+
+Click the Link inspector again. 
+
+Nothing happens. Link inspector stops working completely.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415985480,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-wejuqtqqsktmkabwdqxr,task_description,resolved
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE",This looks like it was fixed a while ago.,1444488231,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Also, happens when you type a text and select that and try to open link inspector for it",1416857350,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Environment:betalabs,test2, en.wiki",1415995223,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Steps to reproduce:
+
+1.Go to this page:http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+2.Click on link inspector icon from the toolbar , but make sure you do not place your cursor in the article first
+
+3.Once the link inspector opens for the first text ""Media"" , click on ""Done"" or ""Remove"" to close the link inspector.Again, do not place the cursor inside CE
+
+4.Click on link inspector icon from the toolbar again
+
+At this step, you will see a broken UI for link inspector,just the link suggestions are appearing as the screenshot.
+
+Also, after this step link inspector stops working completely, clicking on the link icon from the toolbar does not open link inspector for any other text in the article .",1415993491,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","FWIW, I can repro this consistently in Firefox 32.0.3",1415992428,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Created attachment 17126
+clicking Link no longer invokes the Link inspector at all
+
+**Attached**: {F15328}",1415991325,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Created attachment 17125
+after clicking Remove and then clicking Link inspector again
+
+This is clearly wrong
+
+**Attached**: {F15327}",1415991284,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Created attachment 17124
+after invoking Link inspector the first time, before clicking Remove
+
+**Attached**: {F15326}",1415991225,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE",I cannot reproduce this issue following these steps either.,1415990480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","On http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit - the link was applied to a specific word(s)? 
+
+I tried to follow your scenario with the word Test on that page - ""New page/Matching pages"" seems to be identical with any attempts.",1415988998,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE",Note: this behavior is seen in Firefox. Chrome seems to be OK.,1415985719,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","Gallery with caption gets added to the table inside the image
+
+Environment- test2, beta, production
+
+1> Insert -> media 
+2> insert a table in the caption sub- editor of Media Settings.Click to insert to the main editor.
+2> Highlight the media, insert a gallery with just caption(no filename).
+3> Now drag and drop the gallery on to the table inside the image. Notice the gallery gets added to the table inside the image.
+4> click on the image’s context menu to go to media settings, notice the gallery shows up in the caption pane.See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15189}",1415890380,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-evrokwipdbub7qma7gbx,task_description,resolved
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",Verified the fix in test2.,1416442198,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",Verified the fix in betalabs.,1416262501,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","**gerritadmin** wrote:
+
+Change 173442 merged by jenkins-bot:
+Don't allow dropping inside a handlesOwnChildren node
+
+https://gerrit.wikimedia.org/r/173442",1416256931,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","**gerritadmin** wrote:
+
+Change 173442 had a related patch set uploaded by Catrope:
+Don't allow dropping inside a handlesOwnChildren node
+
+https://gerrit.wikimedia.org/r/173442",1416255192,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",Step 3 should not be possible and is fixed by https://gerrit.wikimedia.org/r/#/c/173442/,1416155394,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","(In reply to etonkovidova from comment #5)
+> Yes, I checked the functionality of inserted tables - all is fine(a tiny bug
+> 73435 was filed). 
+> 
+> Btw, Gallery can be dragged to a Media's Caption.
+yes, if there is something in the media's caption(not just tables even plain text)the gallery gets added to the media's caption.
+
+or
+
+if you had something in the media caption and you deleted it.And then if you drag a gallery to the media's caption part it gets added.
+
+steps- 
+1> go to media settings dialog. 
+2> type in some text in the caption pane,and apply changes.
+3> insert a gallery.
+4> reopen the media settings dialog and delete the caption you put in, at step#2.
+5> now drag the gallery to where the media's caption was. Notice a line is gets drawn and the gallery gets added.",1416069039,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","Yes, I checked the functionality of inserted tables - all is fine(a tiny bug 73435 was filed). 
+
+Btw, Gallery can be dragged to a Media's Caption.",1416002830,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","Tables inside captions are okay. They probably shouldn't be encouraged but in the cases where they exist, we need to provide the tools to edit them.",1415994298,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","Gallery(with just caption) can be added to a table in the main editor.
+Gallery cannot be added to an image otherwise and is also not available as an insert sub menu option in the media settings toolbar .But if the image has a table it gets added to it.",1415983259,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",In addition to bug 73341 - should tables be allowed for insertion in Media settings?,1415919842,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",Also in FF 33.1.,1415890448,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"See https://tl.wikipedia.org/wiki/Wikipedia:VisualEditor/Komentaryo#Did_you_know_why.3F .
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://tl.wikipedia.org/wiki/Wikipedia:VisualEditor/Komentaryo#Did_you_know_why.3F",1415886300,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hjiff2rve77sfx43cqpe,task_description,resolved
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),Now done.,1416271503,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"**gerritadmin** wrote:
+
+Change 172993 merged by jenkins-bot:
+Enable VisualEditor by default on Tagalog Wikipedia
+
+https://gerrit.wikimedia.org/r/172993",1416271230,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"(In reply to Roan Kattouw from comment #3)
+> Once the schedule for next week is put on the wiki page, I'll schedule this
+> change again, probably for either Monday 16:00-17:00 UTC or Tuesday
+> 00:00-01:00 UTC.
+> 
+Now scheduled for 00:00-01:00 UTC on Tuesday November 18.",1416003869,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"(In reply to Gerrit Notification Bot from comment #2)
+> Change 172993 had a related patch set uploaded by Jforrester:
+> Enable VisualEditor by default on Tagalog Wikipedia
+> 
+> https://gerrit.wikimedia.org/r/172993
+
+We planned to deploy this about 6 hours ago, but because of an issue with other VisualEditor changes scheduled for the same time, the deployer overlooked this change and I didn't notice that he hadn't deployed it until it was way too late :(
+
+Once the schedule for next week is put on the wiki page, I'll schedule this change again, probably for either Monday 16:00-17:00 UTC or Tuesday 00:00-01:00 UTC.
+
+Sorry for spacing on this :(",1415946788,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"**gerritadmin** wrote:
+
+Change 172993 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on Tagalog Wikipedia
+
+https://gerrit.wikimedia.org/r/172993",1415889146,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),Sure.,1415889017,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,"Link inspector opens at the upper left corner
+
+Only Safari(betalbs, test2, production)
+
+1. In VE type a word and convert it into a link.
+
+2. Place a cursor at the end of the word - the link inspector opens at the upper left corner of the screen. The screenshot is attached. 
+
+Note: The link inspector opens correctly if the cursor is placed in the middle of an inserted link. Place a cursor at the end of the link and start moving left - the position of the link inspector will be changed from the correct.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15101}",1415833020,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-23kytwe342kbpmgthgmt,task_description,resolved
+VisualEditor: Link inspector opens in a upper left corner in Safari,"Duplicate to 76083.
+",1423174446,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,"Created attachment 17174
+Safari link inspector
+
+**Attached**: {F15102}",1416432429,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,"**gerritadmin** wrote:
+
+Change 173007 merged by jenkins-bot:
+Update RangeFix library 0.1.0 -> 0.1.1
+
+https://gerrit.wikimedia.org/r/173007",1416246799,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,"**gerritadmin** wrote:
+
+Change 173007 had a related patch set uploaded by Esanders:
+Update RangeFix library 0.1.0 -> 0.1.1
+
+https://gerrit.wikimedia.org/r/173007",1415891713,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,Safari browser bug. Applying patch upstream in rangefix.,1415890348,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"This is bug 72251 for magic words.  
+
+{{cite book|isbn=1234567890}} displays as a redlink, and it shouldn't.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415816280,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-luvruzm46k3dlau5z6wg,task_description,resolved
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"(In reply to etonkovidova from comment #4)
+> I copied  
+> {{cite book|isbn=123456789X|url = http://www.amazon.com|title = Fish}} from
+> http://en.wikipedia.beta.wmflabs.org/wiki/User:Jdforrester_(WMF)/Bug_73320
+> and pasted it into test2 - look at the attached screenshot. 
+> 
+> 
+> <a
+> href=""/w/index.php?title=International_Standard_Book_Number&amp;
+> action=edit&amp;redlink=1"" class=""new"" title=""International Standard Book
+> Number (page does not exist)"">ISBN</a>
+> 
+> @media screen
+> 
+> a.new:visited, #p-personal a.new:visited {
+> 	.	
color: #a55858;
+> 
+> 
+>  ISBN is still red.
+
+Yeah, because the word ""ISBN"" links to a page that doesn't exist. This is about the number being red.",1415918355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"I copied  
+{{cite book|isbn=123456789X|url = http://www.amazon.com|title = Fish}} from http://en.wikipedia.beta.wmflabs.org/wiki/User:Jdforrester_(WMF)/Bug_73320 and pasted it into test2 - look at the attached screenshot. 
+
+
+<a href=""/w/index.php?title=International_Standard_Book_Number&amp;action=edit&amp;redlink=1"" class=""new"" title=""International Standard Book Number (page does not exist)"">ISBN</a>
+
+@media screen
+
+a.new:visited, #p-personal a.new:visited {
+	.	
color: #a55858;
+
+
+ ISBN is still red.",1415918297,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"Created attachment 17122
+ISBN is  displayed in red
+
+**Attached**: {F15070}",1415918147,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,Confirmed with http://en.wikipedia.beta.wmflabs.org/wiki/User:Jdforrester_(WMF)/Bug_73320 – marking as FIXED.,1415916533,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"I can reproduce this at en.wp today, but not at en.wikipedia.beta.wmflabs.org, so presumably the problem has already been fixed.",1415860817,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor: Drag-and-drop of a block image doesn't remove the marker lines sometimes (?),"screenshot in chrome
+
+Environment- test2, beta
+
+1> Insert a media with default settings.
+2> keeping the media highglighted,insert a gallery with just caption(no filename).
+3> Now drag and drop the gallery to the image and then image to the gallery. Either way it draws focusablenode dropmarker lines above and below the media content. See screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14939}",1415724180,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-isjhm5lhynj6lgf5pve2,task_description,open
+VisualEditor: Drag-and-drop of a block image doesn't remove the marker lines sometimes (?),"Confirmed - the ""extra"" element that appears during drag-and-drop is <p contenteditable=""false"" class=""ve-ce-branchNode-slug ve-ce-branchNode-blockSlug"">
+
+However, the saved page does not have any traces of extra lines.",1415815891,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-isjhm5lhynj6lgf5pve2,task_subcomment,NA
+VisualEditor: Drag-and-drop of a block image doesn't remove the marker lines sometimes (?),"Created attachment 17095
+screenshot in FF 33.1
+
+**Attached**: {F14940}",1415724365,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-isjhm5lhynj6lgf5pve2,task_subcomment,NA
+"VisualEditor: When selecting FocusableNode with arrow keys, context flickers at position of last mouse click","1. Open a document that contains a line of plain (not linked) text with an inline focusable node (e.g. template or reference)
+2. Use the mouse to put the cursor on this line, some distance away from the text
+3. Use the arrow keys to move the cursor to the focusable node
+4. When the node is focused, the context flickers in the position where you clicked in step 2 before moving to the focusable node
+
+This doesn't happen when you use the mouse to focus the node. It also doesn't happen when the context appears for an annotation (e.g. link).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1415654940,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sojeywgrcg6knl7y5dzy,task_description,resolved
+"VisualEditor: When selecting FocusableNode with arrow keys, context flickers at position of last mouse click",Verified the fix in beta.,1416443096,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-sojeywgrcg6knl7y5dzy,task_subcomment,NA
+"VisualEditor: When selecting FocusableNode with arrow keys, context flickers at position of last mouse click","Change 173804 merged by jenkins-bot:
+Don't always use updateDimensionsDebounced
+
+https://gerrit.wikimedia.org/r/173804",1416256925,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sojeywgrcg6knl7y5dzy,task_subcomment,NA
+"VisualEditor: When selecting FocusableNode with arrow keys, context flickers at position of last mouse click","Change 173804 had a related patch set uploaded by Esanders:
+Don't always use updateDimensionsDebounced
+
+https://gerrit.wikimedia.org/r/173804",1416229923,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sojeywgrcg6knl7y5dzy,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Proposed in #community-wishlist-survey-2016. Received 41 support votes and was ranked #31 out of 265 proposals. [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | View full discussion and votes here ]].  
+
+----
+
+As a use who is preparing an edit, I'd like to be confident that if some bad interruption happens before I save it (e.g. power outage) I'll likely be able to recover most of my work when I try to edit the page again, even if other countermeasures (e.g. browser cache, local copy) are missing or failed.
+
+Local vs. remote storage, frequency of autosave, expiry etc. are negotiable. The less interface there is, the better; there should be no added preference(s).
+
+Creating because of https://lists.wikimedia.org/pipermail/wikitech-l/2014-November/079378.html and the lack of a bug in core to track this.
+
+----
+
+Something else that I have had in the pipeline for a long while is autosave drafts. Basically, whenever you type, the article is saved to your local computer. If the browser crashes, and you visit the same article, it will prompt you for recovery. Making a Special:Autosave drafts index page would be trivial.
+
+Implementation:
+https://gerrit.wikimedia.org/r/#/c/5130/ <https://gerrit.wikimedia.org/r/#/c/5130/>
+
+Of this, I also have an alternate implementation:
+https://gerrit.wikimedia.org/r/#/c/157818/ <https://gerrit.wikimedia.org/r/#/c/157818/>
+https://gerrit.wikimedia.org/r/#/c/159626/ <https://gerrit.wikimedia.org/r/#/c/159626/>
+
+The original one is based on code by Joancreus and uses localStorage. It works, quite well actually, but while improving it, I became of the opinion that localStorage is basically so limited in storage and gives you so little feedback as an API and an enduser, that it's not really suited for much more than usersettings (big cookies). Not for saving potentially multiple 1MB articles, with structured details.
+
+As a storage layer, indexedDB is much nicer in that regard. API wise, it's a bit convoluted, but a jQuery plugin makes it usable and readable. There are WebSQL polyfills for platforms that don't have indexedDB, which would allow us to support browsers of the past 6 years.
+
+I would like some opinions on which way to go here. Additionally, i would love to hear what else people think would be required to make this usable for the Wikipedia audience and the naming. Would this be Drafts ? Autosave drafts ? autosave ? Would you say 'recover' when asking the user to use the version from drafts, or just 'use draft' etc?
+
+Note that the '2nd' version also has a few more improvements like a separate RL module and a preference option, but those can easily be added to the first implementation as well. 
+
+----
+
+Clearly, I prefer the word ""autosave"", which reminds people of the recovery features endemic in any document editing software; rather than ""draft"", which in the past caused a lot of confusion. LibreOffice, when restarted, asks if you want to ""recover"" a previous document, and many other FLOSS productivity softwares use the same terminology: what do they do on the devil's side (M$ and Apple)?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**Possible consumers**:
+* VisualEditor ({T57370})
+* ContentTranslation, T113221#1844393 (currently DB-based: {rECTX00ebcc6e3e31b278092abde755cbd9009ef65cf4})
+**See Also**:
+* {T39992}
+* {T11749}",1415654160,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_description,resolved
+Auto-save to increase chances of lost edits recovery,"Boldly resolving this as the first part of an autosave feature is now in core, and further improvements are being tracked in the #Edit_Recovery project (which is the terminology we decided on, although I'm sure there's more bikeshedding possible with that if anyone's keen).",1690505060,PHID-USER-hlhhe6qw6qfkl7wyfhxk,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Editing/Autosave_edited_or_new_unpublished_article,1651238704,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,I really need him.,1630387852,PHID-USER-4a5dsnuy5lyy72ieqsb2,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Editing/Make_edits_auto-recoverable_if_the_editor%27s_network_crashes,1608818448,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Change 5130 abandoned by TheDJ:
+mediawiki.action.edit: Autosave edit textareas in localStorage
+
+Reason:
+No progress on this for the past year, abandoning.
+
+[[https://gerrit.wikimedia.org/r/5130]]",1502404558,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,Doesn't fit the definition of stalled. https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle,1465390171,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Change 5130 had a related patch set uploaded (by Jdlrobson):
+mediawiki.action.edit: Autosave edit textareas in localStorage
+
+[[https://gerrit.wikimedia.org/r/5130]]
+",1462483745,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,Looks stalled to me.,1462483736,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Merged in ContentTranslation: 00ebcc6e3e31b278092abde755cbd9009ef65cf4
+No idea how much of its code/idea is reusable.",1416304650,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"(In reply to Umherirrender from comment #3)
+> You have linked the bug, but there should also be a link to
+> [[mw:Extension:Drafts]], which supports auto saving on the server side.
+
+Sure, though that's not ready and even if it was, is not getting deployed to Wikimedia wikis, for reasons explained at length.",1415907123,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"You have linked the bug, but there should also be a link to [[mw:Extension:Drafts]], which supports auto saving on the server side.",1415722646,PHID-USER-qaoxfiqu6bxhd5ehlwhc,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Change 159626 had a related patch set uploaded by Nemo bis:
+Drafts: Refactor with IndexedDB
+
+https://gerrit.wikimedia.org/r/159626",1415654297,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Change 5130 had a related patch set uploaded by Nemo bis:
+mediawiki.action.edit: Autosave edit textareas in localStorage
+
+https://gerrit.wikimedia.org/r/5130",1415654282,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+VisualEditor: Drag-and-drop in IE9 doesn't work,"I can successfully drag-n-drop an image from one part of the page to another in VE while using Chrome and Firefox, but not IE.
+
+Chrome and FF provide feedback, indicating where the object will land if it is dropped, but IE doesn't.  Nor does dropping the object move it.
+
+I don't see any errors in the js console on IE during this process.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51669",1415653560,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-k7ndkr4spt2bt7mgctja,task_description,resolved
+VisualEditor: Drag-and-drop in IE9 doesn't work,"Change 284361 merged by jenkins-bot:
+Fix node drop in IE9
+
+[[https://gerrit.wikimedia.org/r/284361]]",1461111218,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7ndkr4spt2bt7mgctja,task_subcomment,NA
+VisualEditor: Drag-and-drop in IE9 doesn't work,"Change 284361 had a related patch set uploaded (by Esanders):
+Fix node drop in IE9
+
+[[https://gerrit.wikimedia.org/r/284361]]
+",1461101719,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k7ndkr4spt2bt7mgctja,task_subcomment,NA
+VisualEditor: Drag-and-drop in IE9 doesn't work,"Filed the exception as a different bug. Apart from that works in IE11/10 but not 9, where I get a different exception (cannot slice undefined).",1461099325,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-k7ndkr4spt2bt7mgctja,task_subcomment,NA
+VisualEditor: Drag-and-drop in IE9 doesn't work,"Just re-tested against https://en.wikipedia.org/w/index.php?oldid=678508180 ([[Ray County, Missouri]]) and drag-n-drop of images didn't work on IE still.  It did work on FF and Chrome, though.
+
+In IE, clicking on the Route 13 sign ([[File:MO-13.svg]]) shows the Media highlight.  Click off of that and you get the following exception:
+   SCRIPT5022: Nested change of newModelSelection File: load.php, Line: 832, Column: 517
+
+IE's debugger has this call stack:
+
+    ve.ce.Surface.prototype.changeModel [Line: 832, Col: 517], load.php
+    ve.ce.Surface.prototype.handleObservedChanges [Line: 819, Col: 510], load.php
+    ve.ce.SurfaceObserver.prototype.pollOnceInternal [Line: 836, Col: 73], load.php
+    ve.ce.SurfaceObserver.prototype.pollOnceSelection [Line: 835, Col: 625], load.php
+    ve.ce.Surface.prototype.onDocumentSelectionChange [Line: 791, Col: 569], load.php
+    jQuery.event.dispatch [Line: 65, Col: 907], load.php
+    elemData.handle [Line: 60, Col: 384], load.php
+    ve.selectElement [Line: 62, Col: 281], eval code (48)
+    ve.ce.Surface.prototype.preparePasteTargetForCopy [Line: 816, Col: 530], load.php
+    ve.ce.Surface.prototype.onModelSelect [Line: 815, Col: 591], load.php
+    oo.EventEmitter.prototype.emit [Line: 65, Col: 545], eval code (46)
+    ve.dm.Surface.prototype.setSelection [Line: 578, Col: 532], load.php
+    ve.dm.Surface.prototype.changeInternal [Line: 580, Col: 371], load.php
+    ve.dm.Surface.prototype.change [Line: 579, Col: 351], load.php
+    ve.ce.Surface.prototype.changeModel [Line: 832, Col: 609], load.php
+    ve.ce.Surface.prototype.handleObservedChanges [Line: 819, Col: 510], load.php
+    ve.ce.SurfaceObserver.prototype.pollOnceInternal [Line: 836, Col: 73], load.php
+    ve.ce.SurfaceObserver.prototype.pollOnceSelection [Line: 835, Col: 625], load.php
+    ve.ce.Surface.prototype.onDocumentSelectionChange [Line: 791, Col: 569], load.php
+    jQuery.event.dispatch [Line: 65, Col: 907], load.php
+    elemData.handle [Line: 60, Col: 384], load.php
+    ve.ui.LinearContext.prototype.onContextChange [Line: 904, Col: 976], load.php
+    oo.EventEmitter.prototype.emit [Line: 65, Col: 545], eval code (46)
+    ve.dm.Surface.prototype.emitContextChange [Line: 575, Col: 206], load.php
+    ve.dm.Surface.prototype.setSelection [Line: 578, Col: 682], load.php
+    ve.dm.SurfaceFragment.prototype.select [Line: 590, Col: 861], load.php
+    Anonymous function [Line: 760, Col: 529], load.php
+    ve.ce.FocusableNode.prototype.onFocusableMouseDown [Line: 760, Col: 436], load.php
+    jQuery.event.dispatch [Line: 65, Col: 907], load.php
+    elemData.handle [Line: 60, Col: 384], load.php
+",1447172508,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-k7ndkr4spt2bt7mgctja,task_subcomment,NA
+VisualEditor: Removing table row where rowspanned cell starts un-merges the remaining spanned cells,"Removing the table row where rowspanned cell starts un-merges the remaining spanned cells.
+
+1. Look at the tables.html demo.
+2. In ""Merged cells"" example, place cursor at the ""10"" cell.
+3. Delete row.
+
+The ""4"" cell has correctly changed from spanning three to two rows. However, the ""9"" cell has split into three cells, while it should have been changed from spanning four to three rows instead.
+
+Analogous behavior occurs when removing the column where a colspanned cell starts. (Try with the ""16"" cell.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415582400,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xmwils3vchvzzdbgegip,task_description,resolved
+VisualEditor: Removing table row where rowspanned cell starts un-merges the remaining spanned cells,"Change 172193 merged by jenkins-bot:
+Don't unmerge spanned cells when spanned cell is removed
+
+https://gerrit.wikimedia.org/r/172193",1415645918,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xmwils3vchvzzdbgegip,task_subcomment,NA
+VisualEditor: Removing table row where rowspanned cell starts un-merges the remaining spanned cells,"Change 172193 had a related patch set uploaded by Bartosz Dziewoński:
+[WIP] Don't un-merge spanned cells when spanned cell is removed
+
+https://gerrit.wikimedia.org/r/172193",1415589726,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xmwils3vchvzzdbgegip,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","VisualEditor: ""Insert table"" tool should be (also?) in the ""Table"" menu, not (or in addition to?) ""Insert"" menu. I was quite confused for a moment by the table icon being grayed out, and I've been told I'm not the only one.",1415582100,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-paw5zcxophppwlal7wbs,task_description,resolved
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","Change 267532 merged by jenkins-bot:
+Introduce table and table cell context
+
+[[https://gerrit.wikimedia.org/r/267532]]",1454351829,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","Change 267532 had a related patch set uploaded (by Esanders):
+Introduce table and table cell context
+
+[[https://gerrit.wikimedia.org/r/267532]]
+",1454239081,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","My client asked about this and I told her ""That's how it is on Wikipedia"" and found this bug (before I filed my own, yay!).
+
+I vote for enabling the icon when not in a table to allow for table creation.
+
+If I were really sick, I'd say that the option to insert a table should remain available even when in a table cell, so that we could do 90s style webpage layouts in the VisualEditor.
+
+But I'm only a little sick, so activating it to enable table creation/insertion is what I'm going with.",1429629534,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","Alternatively, we could put the table inspector in the proper place (i.e., on the table) rather than over-loading the toolbar, which would remove the confusion.",1415642030,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","The current option is highly temporary, AFAIK.",1415607025,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","+1. When user wants to create a new table, he can see the icon in the toolbar, but it's marked as displayed. Really confusing. Imho, if we have a special menu for tables, ""Insert table"" should be placed there instead of being in ""Insert menu"". The current solution is reasonable, but unintuitive. (Maybe ""Insert table"" could be visible alternatively with ""Delete table"" #brainstorm).",1415583523,PHID-USER-gf5juv3z3p75bykrcrhf,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed","After editing an unreviewed page using VisualEditor, reviewing the page doesn’t review the just-made edit if the page isn’t reloaded between publishing the edit and pressing review.
+
+How to reproduce:
+1) go to some article that hasn't been reviewed yet
+2) make an edit to the article using Visual Editor. save the edit
+3) review the article
+4) when you look at the article history you can see that the article you marked as reviewed has one unreviewed change (the one you just did using VE)
+
+I tried this at https://test2.wikipedia.org/wiki/Testing_something",1415453100,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-d3c74irtdh5bydamc36k,task_description,open
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed","I tried to rephrase the description to be easier to understand (I hope I understood it correctly). However, when I tried to reproduce it on test2wiki, I couldn’t – when I opened VisualEditor, the FlaggedRevs interface disappeared, and when I published the edit, it didn’t come back, so there was no button that could have worked incorrectly. Well that’s also a way to fix this bug…",1731774911,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed","If this is still issue, add more details.",1731542149,PHID-USER-i2ki3npptssmkwi5oirg,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed","But if you try to change it, you get ""Invalid inclusion parameter key"".
+That key is actually a hash of several things (including the oldid): https://github.com/wikimedia/mediawiki-extensions-FlaggedRevs/blob/master/business/RevisionReviewForm.php#L211-L213
+We'd need to regenerate it somehow I guess...",1438130013,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",We're not updating the mw-fr-input-oldid hidden input in the FlaggedRevs page review form when we update the page contents.,1438129166,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",We're not updating the oldid hidden in the FlaggedRevs page review form when we update the page contents.,1438129144,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",We're not updating the oldid in the FlaggedRevs page review form when we update the page contents.,1438129136,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",">>! In T75171#1471012, @Jdforrester-WMF wrote:
+> Is this still an issue?
+
+It is. Just tested it again at https://test2.wikipedia.org/wiki/Testing_something",1437583466,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",Is this still an issue?,1437581122,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Splitting the bug from 72392.
+
+Open a page in VE and insert a link with the shortcut - Ctrl+K - the link inspector opens and closes momentarily. 
+
+The console displays the following(consistently): 
+
+DOM7009: Unable to decode image at URL: 'data:image/gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA'.  File: gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415390280,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-urgeoycg3qunrfzhjulb,task_description,resolved
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,Seems to work fine now - please re-open if it is still broken for you.,1460644310,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Re: ""Strange presentation""
+
+On further examination, The ""File:"" bit was presented as a link with the full URL. Clicking the link took me to the contents of a 1x1 pixel.  That is, where you normally see source code or raw HTML in the debugger, I saw:
+  1. GIF87a□□□Ü□,□□□□□□□□□
+
+Maybe the data urls are messing with IE's head?
+",1426282563,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Just updated to the 1.25wmf21 branch and I'm seeing the message in IE11:
+
+  DOM7009: Unable to decode image at URL: 'data:image/gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA'.
+  File: gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA
+
+There is a [[ http://stackoverflow.com/a/28426679 | stackoverflow answer ]] that indicates this may be related to OOM problems -- and the strange presentatoin of this (""File: gif;base64..."") leads me to believe that might be  the case.
+
+Note that I'm seeing this blatted on the console multiple times while simply selecting text.",1426280123,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"@Etonkovidova: Why was ""Verified-in-Phase0"" set here?",1422893851,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Yes, the message in the console is unrelated to the issue. 
+
+Reproducible **only in production** - inserting a link with a Ctrl+K displays flickering link inspector and move the cursor to the beginning of a paragraph. The link will, in fact, inserted, and can be edited afterwards without any problems. 
+
+Inserting links with a short cut [[ or from Tool menu does not present any issues.",1419371203,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Can't reproduce. I get the message in the console, but only while VE is loading, unrelatedly to link inspector; the inspector opens and works perfectly fine.",1419349851,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Wait, the link inspector actually closes? I thought it was just the error...",1415390374,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,"Preformatted text in tables
+
+In betalabs
+
+1. In VE insert a table and double-click in any cell to make it editable.
+
+2. Select the 'preformatted' option - the cell will be yanked from the table(similar to bug 72990). The preformatted are will be displayed outside of the table. 
+
+The same happens when you apply preformatted to the cells' text.
+
+Look at the screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15190}",1415313600,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-osvgc2rrhwadyji7x6hl,task_description,resolved
+VisualEditor: handling preformatted text in tables,Verified the fix in test2 and production.,1416434768,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,Verified the fix in Betalabs.,1415658523,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,"Definitely fixed, I ran into this in prod today, wanted to file a bug and couldn't reproduce on master. Now I know why. :)",1415581929,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,"Change 171835 merged by jenkins-bot:
+Support pre's in tables
+
+https://gerrit.wikimedia.org/r/171835",1415382974,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,"Change 171835 had a related patch set uploaded by Esanders:
+Support pre's in tables
+
+https://gerrit.wikimedia.org/r/171835",1415375088,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+Flow: Use PHP Virtual REST Service to access Parsoid,"From gerrit 170869:
+> Gabriel suggested that in the future we migrate to the PHP Virtual REST Service and through that share code between Flow, VE and anything else that wants to talk with parsoid.
+https://www.mediawiki.org/wiki/Requests_for_comment/PHP_Virtual_REST_Service
+
+With [[ https://gerrit.wikimedia.org/r/#/c/181011/ | gerrit 181011]] VisualEditor is doing this, so Flow can do the same and remove whatever cookie hacks @Ebernhardson needed to access Parsoid from the private officewiki.
+
+--------------------------
+**Version**: master
+**Severity**: minor",1415138880,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-cz3rtgfxbykofx4kvsia,task_description,open
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"screenshot of JS errors in beta
+
+Environment- test2, beta
+
+1> In a blank page, open the Language inspector.
+2> While the inspector is open ,select any Heading format from the drop-down,for ex- select Heading.
+2> The inspector closes and you see the language context menu. 
+3> type in some text, it doesn’t take the language annotation(looks like plain paragraph text)
+4> Hit enter and JS error “Uncaught Error: Inserted data is trying to close the root node (at index 0)”. See screenshot.
+5> Notice no matter where your cursor is on the page, the language context menu never moves from its place or closes for a new line.
+
+In beta an additional  JS error appears at step#2, “Uncaught Error: Offset could not be translated to a DOM element and offset: 2”.
+
+Reproducible in FF too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows XP
+
+**Attached**: {F14776}",1415115600,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-wt57zr2htyhkzzgovt4f,task_description,resolved
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"I've tried various variations of these steps including with some text to start with (since the original sequence of ""language inspector tujrns into language context, when no text is typed and heading selected"" no longer happened).
+
+No error found in that testing. I suppose this code has likely changed numerous since 2014, and propose any related issue that can be reproduced today be filed as a new task.",1629314979,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"This is surfacing today in the production error logs.
+https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-2020.09.14/clienterror/?id=AXSNst-8c14jQX20-BU0
+
+```
+at writeElement URL1:293:914
+at URL1:296:984
+at URL1:171:877
+at URL1:260:949
+at URL1:535:424
+at URL1:534:922
+at URL1:527:727
+at URL1:523:520
+
+URL1: https://www.mediawiki.org/w/load.php?lang=en&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2CdesktopArticleTarget%2CdesktopTarget%2Cdiffing%2Cicons%2Clanguage%2Cmediawiki%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2Cwelcome%7Cext.visualEditor.core.desktop%2Cutils%7Cext.visualEditor.mwextensions.desktop%7Cext.visualEditor.mwimage.core&skin=vector&version=18e9q
+```",1600106182,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"Yes, it is. 
+Here, I was also pointing at the typed text appearing plain, i.e., without any language annotation.",1420914110,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,Isn't that already reported as T76717?,1420898423,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"{F27349}Screenshot of the JS Error ""Offset could not be translated to a DOM element and offset: 2"".",1420866363,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"I could not reproduce it either.But I did get the JS  error “Uncaught Error: Offset could not be translated to a DOM element and offset: 2” and the text typed was just plain paragraph-like.
+
+Here are the steps-:
+
+Environment- test2, beta
+
+1> In a blank page, open the Language inspector.
+2> While the inspector is open ,select any Heading format from the drop-down,for ex- select Heading.
+3> The inspector closes and you see the language context menu. 
+4> Type some text, it doesn’t take the language annotation(looks like plain paragraph text).JS error “Uncaught Error: Offset could not be translated to a DOM element and offset: 2” appears.
+
+See the screencast at http://youtu.be/qXID9SlMClo",1420865941,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,I can't reproduce this.,1420852027,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,Confirmed in betalabs Chrome.,1415124077,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"To reproduce:
+
+- Navigate to an article
+- Open Chrome's Developer Tools
+- Click 'Profiles'
+- Select 'Collect JavaScript CPU Profile'
+- Click 'Start'
+- Click 'Edit [beta]'
+- Wait for VisualEditor to finish loading
+- Click 'Stop'
+
+Result:
+
+Both oo.Factory.create or oo.EventEmitter.emit are flagged by the profiler with the warning: ""Not optimized: Inlining bailed out.""
+
+To investigate, I recommend reading <https://github.com/GoogleChrome/devtools-docs/issues/53>
+
+v8 comes with a 'd8' executable that can be used for getting some performance debug info from v8. If you can craft a file that utilizes these functions without depending on the DOM API, you can try running it with:
+
+> d8 --trace-opt --trace-bailout some-js-file.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1415064480,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_description,resolved
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"Change 186244 merged by jenkins-bot:
+v8 opt: Copy arguments into new array rather than use [].slice
+
+[[https://gerrit.wikimedia.org/r/186244]]",1422038468,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_subcomment,NA
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"Change 186244 had a related patch set uploaded (by Jforrester):
+v8 opt: Copy arguments into new array rather than use [].slice
+
+[[https://gerrit.wikimedia.org/r/186244]]
+
+#patch-for-review",1421948376,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_subcomment,NA
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"EventEmitter.emit also seems to be because of arguments. I checked, though, and there's very little ""self"" time spent in EventEmitter.emit and Factory.create: 25ms and 53ms respectively for Obama. But I'll see what that drops to after optimizing them.",1415216420,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_subcomment,NA
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"For oo.Factory.create, my version of Chrome tells me ""Not optimized: Bad value context for arguments value"" which seems to be a consequence of doing args = Array.prototype.slice.call( arguments, 1 ); . I don't really see a way around that, unless there's some way of making the arguments list a real array that V8 is able to optimize.
+
+For oo.EventEmitter.emit it does say ""Inlining bailed out"". I'm installing d8 now to investigate.
+
+I saw a bunch of other ""not optimized"" warnings too, but most of those seem to be about try-catch statements. The only other one that jumped out at me was in oo.copy: ""ForInStatement is not fast case"". Will investigate that too.",1415131201,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,"Edit summary textbox is black
+
+Steps to reproduce: 
+
+ In IE 11 perform some editing in VE and click Save page.
+
+Observe: 'Edit summary' text box is displayed black. When clicked in it - it becomes white. 
+
+The screenshot is attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15398}",1415045640,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-vcg3kzlidjqghgcegqdp,task_description,resolved
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,"Can't reproduce even if I display input.focus() (which has always worked, I think). ",1461096698,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,"Well you said:
+> When clicked in it - it becomes white.
+
+So I assume you focusing it was just hiding the problem, and we now do it automatically.",1421203405,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,"Is it black if we don't focus? If so, what other dialogs are affected by this IE bug?",1421202864,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,So I can't reproduce this in IE11 but I assume that's because we auto-focus that text box now? What shall we do about this task?,1421202773,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,So I can't reproduce this in IE11 but I assume that's because we auto-focus this now? What shall we do about this task?,1421202750,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+"VisualEditor: Restore selection when user exits the save dialog (on clicking ""Resume editing"")","Edit any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Perform some action, for example highlight text and indent some. 
+
+Click Save page and then click Resume editing from the Save modal dialog.
+
+Upon returning to the edit page, VE edit tools should be enabled but are not enabled.  User must click again in the CE area to enable edit tools.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1415037480,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-4kpfmliccubzixbhguff,task_description,resolved
+"VisualEditor: Restore selection when user exits the save dialog (on clicking ""Resume editing"")",Verified in test2.,1416439167,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-4kpfmliccubzixbhguff,task_subcomment,NA
+"VisualEditor: Restore selection when user exits the save dialog (on clicking ""Resume editing"")","Change 172658 merged by jenkins-bot:
+Restore selection after closing save dialog
+
+https://gerrit.wikimedia.org/r/172658",1415816987,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4kpfmliccubzixbhguff,task_subcomment,NA
+"VisualEditor: Restore selection when user exits the save dialog (on clicking ""Resume editing"")","Change 172658 had a related patch set uploaded by Alex Monk:
+Restore selection after closing save dialog
+
+https://gerrit.wikimedia.org/r/172658",1415750293,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4kpfmliccubzixbhguff,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"screenshot showing multiple Categories with same title
+
+Environment- production, test2
+
+1>Select Categories. Add a category for ex- “Japan”.
+2>The cursor moves to the next input field. Type in “Japan” again. Click somewhere else in the modal, to move the focus. 
+3>Click back in the input field. While the cursor is in the field,hit enter key.
+4>The category with the same name Japan gets added.See screenshot.
+
+In beta, at step#2, after typing in the title, just click twice in the input field(to close the drop-down) and hit enter key. The category with the same title gets added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15381}",1415029080,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_description,resolved
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,Verified in production.,1416425972,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,The fix is verified in betalabs and test2.,1415232622,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"**gerritadmin** wrote:
+
+Change 171033 merged by jenkins-bot:
+Kill MWCategoryWidget#onLookupEnter
+
+https://gerrit.wikimedia.org/r/171033",1415150298,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"**gerritadmin** wrote:
+
+Change 171033 had a related patch set uploaded by Alex Monk:
+Kill MWCategoryWidget#onLookupEnter
+
+https://gerrit.wikimedia.org/r/171033",1415133439,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"Sorry, Alex.",1415056909,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"Confirmed in betalabs, test2, and production.",1415051897,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,"There is text in these forms that can only be seen when selecting.
+
+The same issue as described in bug 72188 applies in VisualEditor; namely that dark system settings lead to unreadable text in certain forms. This is almost certainly because the background colour has been defined and the text colour has been left to the system, leading, in this case, to white text on a white background.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15230}",1414819200,PHID-USER-uku6gl4xeqbtbrcbr5ig,PHID-TASK-kjvvoq653qna4dsuzabo,task_description,resolved
+OOjs UI: Unreadable input box text with dark colour schemes,"**gerritadmin** wrote:
+
+Change 172174 merged by jenkins-bot:
+Match 'color' rules to 'background-color' rules for accessibility
+
+https://gerrit.wikimedia.org/r/172174",1415612177,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,"(In reply to etonkovidova from comment #1)
+> Is it duplicate to 72192? 
+
+It's not a duplicate of bug 72192, but it's the same issue. The codebases are unfortunately still separate.",1415567523,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,"**gerritadmin** wrote:
+
+Change 172174 had a related patch set uploaded by Bartosz Dziewoński:
+Match 'color' rules to 'background-color' rules for accessibility
+
+https://gerrit.wikimedia.org/r/172174",1415567453,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,I'll look into this.,1415410462,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,"Is it duplicate to 72192? 
+
+Tried it with Chrome(Mac) and with 'Cite web' template - it's not reproducible.",1415401708,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,"Steps to reproduce:
+
+1.  Open a page in Firefox (v. 32.0.3 on Mac 10.8.5) that contains several refs in a row:  [1][2][3][4].
+
+2.  Decide that refs 1, 2, and 3 are inappropriate.  Place cursor between refs 3 and 4.
+
+3.  Press shift + back arrow to start selecting the refs.
+
+
+Results:
+
+Press shift + left arrow once:  [3] is highlighted.  Press it again (i.e., to extend the selection to include [2]):  [3] is no longer highlighted.  Press it again:  [3] is highlighted again.  
+
+Repeat cycle of select-deselect as long as you would like.
+
+
+Workaround:
+
+Place cursor before ref [1], and select the three refs by pressing shift + forward arrow.
+
+
+I cannot reproduce this in Safari 6.1.2.  I haven't tested it in a LTR (left-to-right) language.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1414787400,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-xmktwdgi2pttbrlspf73,task_description,resolved
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,Verified the fix in production(in FF) - backward selection(highlighting) works smoothly and no js errors are displayed.,1416426666,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,The fix is confirmed in test2 and betalabs.,1415235623,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,"Change 170697 merged by jenkins-bot:
+Catch backwards selection error in Firefox
+
+https://gerrit.wikimedia.org/r/170697",1415040198,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,"Change 170697 had a related patch set uploaded by Esanders:
+Catch backwards selection error in Firefox
+
+https://gerrit.wikimedia.org/r/170697",1415023482,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,"Confirmed in FF  test2: cannot select a group of reference with Shift+left arrow(highlighting nackward) - NS_ERROR_FAILURE is displayed.
+
+This is perfectly functioning in Chrome - a group of references can be selected with Shift+right arrow and back wards.",1414794323,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"Screenshot
+
+Steps to reproduce:
+
+1.Insert a table
+2.Insert an empty caption to the table
+3.Save the page
+4.Now select any cell in the table
+
+Observe that,the column editing icon at the top of the empty space which looks odd 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15173}",1414784820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v6lbymq7s3dov27etrxo,task_description,resolved
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,Verified the fix in production,1416445927,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,Verified the fix in Betalabs and test2,1416265420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"**gerritadmin** wrote:
+
+Change 172225 merged by jenkins-bot:
+Position the table context relative to the first section node
+
+https://gerrit.wikimedia.org/r/172225",1415648045,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"**gerritadmin** wrote:
+
+Change 172191 abandoned by Bartosz Dziewoński:
+TableNode: Position row/column overlays better when caption is present
+
+Reason:
+Superseded by I3d790d71
+
+https://gerrit.wikimedia.org/r/172191",1415631406,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"**gerritadmin** wrote:
+
+Change 172225 had a related patch set uploaded by Esanders:
+Position the table context relative to the first section node
+
+https://gerrit.wikimedia.org/r/172225",1415623133,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"(In reply to Bartosz Dziewoński from comment #2)
+> To the unfortunate soul tasked with resolving this
+
+Nevermind, it was fun.",1415587110,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"**gerritadmin** wrote:
+
+Change 172191 had a related patch set uploaded by Bartosz Dziewoński:
+TableNode, TableContext: Position row/column overlays better when caption is present
+
+https://gerrit.wikimedia.org/r/172191",1415587016,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"To the unfortunate soul tasked with resolving this: there exists a CSS
+'caption-side' property, which allows the caption to be placed on every of the four usual sides (at least on Firefox, Chrome only supports 'top' and 'bottom'). (It is also supposed to accept a number of other unorthodox values, but it seems no one cares much about those.)",1415584893,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"(In reply to Rummana Yasmeen from comment #0)
+> 3.Save the page
+> 4.Now select any cell in the table
+
+Not necessary, this is immediately visible when you add the empty caption and move selection back to a table cell.",1415581775,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,"Screenshot in Betalabs
+
+Compare the screenshots taken from Betalabs and test2 for the Page Settings tab and see how they are all cramped in Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F15065}",1414705140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_description,resolved
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,Verified the fix in production,1415833384,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,Verified the fix in test2,1415228918,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,Verified the fix in Betalabs,1415060464,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,"Change 170789 merged by jenkins-bot:
+Followup d3367bb: make FieldsetLayout <label>s display: block;
+
+https://gerrit.wikimedia.org/r/170789",1415047423,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,"Change 170789 had a related patch set uploaded by Catrope:
+Followup d3367bb: make FieldsetLayout <label>s display: block;
+
+https://gerrit.wikimedia.org/r/170789",1415047132,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,"Created attachment 16970
+Screenshot in test2
+
+**Attached**: {F15066}",1414705217,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Type a template name in the textbox
+4.Now click on the ""Show Options"" button without selecting anything from the dropdown and closing it
+
+Observed Result:
+The drop down for search results stays in the dialog in the middle of the left panel and add template panel
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15056}",1414704060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-re6vwytcthwmzpbqbfoy,task_description,resolved
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown",Verified the fix in production,1415834939,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-re6vwytcthwmzpbqbfoy,task_subcomment,NA
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown",Verified the fix in Betalabs and test2,1415061702,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-re6vwytcthwmzpbqbfoy,task_subcomment,NA
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown","**gerritadmin** wrote:
+
+Change 170280 merged by jenkins-bot:
+MWTransclusionDialog: Blur active input when switching modes
+
+https://gerrit.wikimedia.org/r/170280",1414796126,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-re6vwytcthwmzpbqbfoy,task_subcomment,NA
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown","**gerritadmin** wrote:
+
+Change 170280 had a related patch set uploaded by Catrope:
+MWTransclusionDialog: Blur active input when switching modes
+
+https://gerrit.wikimedia.org/r/170280",1414725289,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-re6vwytcthwmzpbqbfoy,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Basic References or References list dialog
+3.Place cursor inside the ""Use this group"" combo box
+
+
+Observed Result:
+The group names for reference list are appearing in a short form
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15039}",1414701480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xnyble5ko7cj77odceh5,task_description,resolved
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Verified the fix in production,1415833112,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Verified the fix in test2,1415228995,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Verified the fix in Betalabs,1415060041,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","**gerritadmin** wrote:
+
+Change 170784 merged by jenkins-bot:
+MWReferenceGroupInputWidget: Remove dummy call to onInputChange()
+
+https://gerrit.wikimedia.org/r/170784",1415052587,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","(In reply to Gerrit Notification Bot from comment #6)
+> Change 170784 had a related patch set uploaded by Catrope:
+> MWReferenceGroupInputWidget: Remove dummy call to onInputChange()
+> 
+> https://gerrit.wikimedia.org/r/170784
+
+This patch doesn't look like it fixes this bug?",1415048514,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","**gerritadmin** wrote:
+
+Change 170784 had a related patch set uploaded by Catrope:
+MWReferenceGroupInputWidget: Remove dummy call to onInputChange()
+
+https://gerrit.wikimedia.org/r/170784",1415046188,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","(In reply to Elitre from comment #4)
+> (Is this different from Bug 72785?)
+
+Yes. That's about the height of the box, this is about the width of the text.",1415030641,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",(Is this different from Bug 72785?),1415002692,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Confirmed that this is a regression from https://gerrit.wikimedia.org/r/#/c/169968/,1414778255,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Trevor says it's probably caused by the menu being shown too early.,1414777850,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",James thinks this may be a regression from https://gerrit.wikimedia.org/r/#/c/169968/,1414777686,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"Please.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1414624320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_description,resolved
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,Slugs are now inserted with buttons which are ce=true,1433773199,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"(In reply to Ed Sanders from comment #3)
+> *sigh* Chrome doesn't even let you set such a selection programmatically, so
+> it appears book-ending is required. Although I'd like to do programmatic
+> handling too to catch things like table and focusable node selections (where
+> the native selection is in the paste target).
+
+So… gerrit 172039 didn't fix this. Is it do-able?",1416257031,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"*sigh* Chrome doesn't even let you set such a selection programmatically, so it appears book-ending is required. Although I'd like to do programmatic handling too to catch things like table and focusable node selections (where the native selection is in the paste target).",1414702058,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"Solutions:
+
+1. Book-end the document with selectable but invisible content. Have to make sure this doesn't break ve.ce.getOffset.
+
+2. Register CTRL+A as a trigger and do it programmatically.
+
+
+Further complicating the issue is CE true inside CE false inside CE true, as is the case with table cell editing. In this case CTRL+A should only select the cell contents, so any programmatic solution would have to be aware of that, and any book-end solution would have to work in these ""sub-surfaces"" as well.",1414686261,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"Chromium bug, has been around for a year, but maybe we've made it more common by having ce=false slugs?
+
+https://code.google.com/p/chromium/issues/detail?id=322444
+
+http://jsfiddle.net/edg2s/afhq6ef0/",1414685832,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Convert several MW core special pages to OOUI as a demonstration that it's possible now.
+
+Part of ""front-end standardisation"" Q2 priority project.",1414621860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_description,resolved
+Convert some MW core special pages to OOUI,For further work see T107037.,1446661792,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"I think this task, as written (""Convert some MW core special pages to OOUI""), is sufficiently resolved. We have converted some special pages, and then some more (although most of the relevant commits weren't linked to this bug).
+
+Quick tally:
+
+* Special:ChangeContentModel (fa31bf1675af7255431aeffd9757066e0ce572e2)
+* Special:ChangeEmail (b51076a84446d157bed511246450e70d26e0f945)
+* Special:LinkSearch (5bd98dacfaaf08e9645fdb215a6e18e9d7f80c04)
+* Special:PageLanguage (b51076a84446d157bed511246450e70d26e0f945)
+* Special:PasswordReset (b51076a84446d157bed511246450e70d26e0f945)
+* Special:ResetTokens (2550de9552230585e33b45f37cada0f13e396953)
+
+Several more are in progress or waiting for reviews.
+",1437833883,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"> Are you going to Cc a designer to review? E.g. the label was intended to sit closer to the field underneath, which is still the case on login form.
+
+I don't know who would review these, or if there's anyone willing to at all? If anyone has any feedback to offer, we'll be happy to hear it. Just note that this is the same interface as used in VisualEditor's dialogs and any changes should fit both use cases.
+
+There is about twice as much spacing between the label and widget in OOUI-styled forms than in the old ones, but the widgets are also about twice as big. I agree that the OOUI style might be a bit too whitespacey, though.
+
+> vform stood for ""vertically-stacked form"", everything was intended to be the same width. It was a $displayFormat different from the existing div, table, and raw which also used mediawiki.ui styles. I think clients should be able to request buttons styled as OOUI without getting the vform layout e.g. OOUI buttons in 'table' display format.
+
+It should be possible to use OOUI widgets for existing forms, let's just be cautious about this to avoid breaking interfaces. OOUI integrates seamlessly with HTML, so you can just replace, say, `Html::input( $name, $value, 'submit' )` with `new OOUI\ButtonInputWidget( array( 'name' => $name, 'value' => $value, 'type' => 'submit' ) )`. We could do the same in `HTMLFormField` subclasses, possibly controlled by some config, if anyone desires. I'm not sure how useful this would be in general, though.
+
+The various display formats of HTMLForm are terribly confused, eh. I think a better naming would be 'horizontal' instead of 'table' and 'vertical' instead of 'div', since that's basically what these two result with. 'vform' would then be 'vertical-mediawikiui' and 'ooui' would be 'vertical-oui'. But this is probably not worth doing.
+
+While we're using a vertical layout in OOUI HTMLForm, and while this is the generally recommended layout for OOUI forms, we do sort of kind of support a more horizontal one too – you can it by setting `align: 'left'` rather than `align: 'top'` for individual FieldLayouts. It doesn't exactly behave like 'table' HTMLForm, though, especially for individual checkboxes/toggles. It looks like this: {F175554}
+
+> When you specify 'vform' as displayFormat, the form width needs to be constrained. (Picking a width for vform was challenging, it ended up being determined by the width of the restyled FancyCaptcha on the login form.).
+
+OOUI form widgets' widths are generally limited to 50em (~600px, depending on the skin) for sanity (to avoid input fields stretching across the whole width of 4k display, for example), but this isn't a hard limit.",1433597091,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"This is excellent!
+
+Are you going to Cc a designer to review? E.g. the label was intended to sit closer to the field underneath, which is still the case on [[ https://en.wikipedia.org/wiki/Special:UserLogin | login form ]].
+
+> These pages were previously using the ""VForm"" style and switching them over to the new ""OOUI"" style
+vform stood for ""vertically-stacked form"", everything was intended to be the same width.  It was a `$displayFormat` different from the existing div, table, and raw which also used mediawiki.ui styles. I think clients should be able to request  buttons styled as OOUI without getting the vform layout e.g. OOUI buttons in 'table' display format.
+
+When you specify 'vform' as displayFormat, the form width needs to be constrained. (Picking a width for vform was challenging, it ended up being determined by the width of the restyled FancyCaptcha on the login form.).",1433469430,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Change 208285 had a related patch set uploaded (by Mattflaschen):
+[WIP] Switch some HTMLForms in special pages to OOUI
+
+[[https://gerrit.wikimedia.org/r/208285]]
+",1433464615,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Change 208285 had a related patch set uploaded (by Jforrester):
+[WIP] Switch some HTMLForms in special pages to OOUI
+
+[[https://gerrit.wikimedia.org/r/208285]]
+",1432556477,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Also, once the value is changed, we can take out some of the weird special-casing in forms that use OOUI or mwui in part - BetaFeatures comes to mind immediately (so Special:Preferences in general), but OAuth and many other core forms will benefit.",1431441992,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Here are some screenshots of the ""first iteration"", brought to you by @marktraceur's work on T85291. These pages were previously using the ""VForm"" style and switching them over to the new ""OOUI"" style, once implemented, is a matter of changing a single value.
+
+# Special: ChangeEmail
+| VForm | OOUI |
+| -- | -- |
+| {F163967,height=240} | {F163969,height=260} |
+
+# Special: ResetPassword
+| VForm | OOUI |
+| -- | -- |
+| {F163952,height=250} | {F163954,height=250} |
+
+Issues:
+* The help icon looks slightly blurry, this will be fixed after T97631.
+* The checkbox is smaller, this is a design decision being discussed on T86003.
+
+# Special: PageLanguage
+| VForm | OOUI |
+| -- | -- |
+| {F163958,height=170} | {F163960,height=180} |
+
+Issues:
+* The extremely long dropdown list with languages has usability issues, most importantly T91126.
+* Radio buttons are not OOUI-like yet, we're working on this on T98855.
+",1431442191,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Here are some screenshots of the ""first iteration"", brought to you by @marktraceur's work on T85291. These pages were previously using the ""VForm"" style and switching them over to the new ""OOUI"" style, once implemented, is a matter of changing a single value.
+
+# Special: ChangeEmail
+| VForm | OOUI |
+| -- | -- |
+| {F163967,height=240} | {F163969,height=260} |
+
+# Special: ResetPassword
+| VForm | OOUI |
+| -- | -- |
+| {F163952,height=250} | {F163954,height=250} |
+
+Issues:
+* The help icon looks slightly blurry, this will be fixed after T97631.
+* The checkbox is smaller, this is a design decision being discussed on T86003.
+
+# Special: PageLanguage
+| VForm | OOUI |
+| -- | -- |
+| {F163958,height=170} | {F163960,height=180} |
+
+Issues:
+* The extremely long dropdown list with languages has usability issues, most importantly T91126.
+* Radio buttons are not OOUI-like yet, we're working on this on T91126.
+",1431441796,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Change 208285 had a related patch set uploaded (by Bartosz Dziewoński):
+[WIP] Switch some HTMLForms in special pages to OOUI
+
+[[https://gerrit.wikimedia.org/r/208285]]
+",1431439690,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"This would be a lot less unpleasant if somebody did T19312, or maybe even T12317, first.",1419440091,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+"VisualEditor: When applying the <pre> formatting to multiple paragraphs, make them instead a single <pre> with newlines between the paragraphs","I was wondering if we could have a feature whereby multiline selected text could be enveloped in one <pre> or <code> when the corresponding heading level or text formatting option is clicked from the toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414619520,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-a2u5v6wtvnxub3uml7uz,task_description,open
+"VisualEditor: When applying the <pre> formatting to multiple paragraphs, make them instead a single <pre> with newlines between the paragraphs","Ignore the ""Viewing Profile Info"" part. It could be any section :)",1414685721,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-a2u5v6wtvnxub3uml7uz,task_subcomment,NA
+"VisualEditor: When applying the <pre> formatting to multiple paragraphs, make them instead a single <pre> with newlines between the paragraphs","Suppose one visits an article using Google Chrome for Mac OS. After selecting two consecutive paragraphs in the ""Viewing Profile Info"" section, then choosing either ""Preformatted"" from the heading level dropdown, or ""{ } Computer code"" from the text formatting popover ""pane"", two <code> or two <pre> sections are created, not one. Furthermore, if one starts a new stanza with ""Preformatted"" or ""{ } Computer code"" heading level / formatting, upon pressing the Enter key (as well as Command+Enter for the typical non-terminating line break in Mac OS or Shift+Enter), the editing context switches out of <pre> or <code> mode.",1414685696,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-a2u5v6wtvnxub3uml7uz,task_subcomment,NA
+"VisualEditor: When applying the <pre> formatting to multiple paragraphs, make them instead a single <pre> with newlines between the paragraphs","(If I select multiple lines, I'm able to wrap them in code tags using the corresponding option in the toolbar. How is this different from your request?)",1414670124,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-a2u5v6wtvnxub3uml7uz,task_subcomment,NA
+VisualEditor: [Regression wmf6] deleting text formatted as computer code produces: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.) in Safari,"Found in Safari test2.
+
+1. In VE type some text(spanned several lines), highlight it and apply computer code formatting option. 
+
+2. Delete one line of code - Console shows: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414614240,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-cf7sodft5apnwjetm2ek,task_description,open
+VisualEditor: [Regression wmf6] deleting text formatted as computer code produces: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.) in Safari,This sounds… odd.,1414623296,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cf7sodft5apnwjetm2ek,task_subcomment,NA
+VisualEditor: [Regression wmf6] deleting text formatted as computer code produces: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.) in Safari,"Actually, the console error: ""Failed to load resource: The operation..."" shows for all formatting options - underline, bold, strikethrough etc
+
+The error is displayed when the previously formatted chunk of text is deleted.",1414614535,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-cf7sodft5apnwjetm2ek,task_subcomment,NA
+VisualEditor: Edit notices popup shows out of screen in RTL,"a screenshot with the problem
+
+To reproduce, edit an old version of a Hebrew Wikipedia article, e.g.:
+https://he.wikipedia.org/w/index.php?title=ASCII&oldid=15904477&veaction=edit
+
+The popup with the edit notice about editing an old version appears immediately. It's misaligned and shown mostly out of screen.
+
+See the screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14738}",1414586280,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-67cctylbfobidrbv3hfd,task_description,resolved
+VisualEditor: Edit notices popup shows out of screen in RTL,Attached is a screenshot from betalabs -Page settings menu box  still overflows. The browser window was  Maximized.,1414799613,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-67cctylbfobidrbv3hfd,task_subcomment,NA
+VisualEditor: Edit notices popup shows out of screen in RTL,"Created attachment 16988
+Page settings menu overflow
+
+**Attached**: {F14739}",1414799516,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-67cctylbfobidrbv3hfd,task_subcomment,NA
+VisualEditor: Edit notices popup shows out of screen in RTL,This was fixed in wmf5 by Roan.,1414623664,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67cctylbfobidrbv3hfd,task_subcomment,NA
+VisualEditor: Edit notices popup shows out of screen in RTL,"Confirmed on https://he.wikipedia.org/w/index.php?title=ASCII&oldid=15904477&veaction=edit 
+
+Both 'Page options' and 'Help' boxes are cut off.",1414600629,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-67cctylbfobidrbv3hfd,task_subcomment,NA
+VisualEditor: Content menu is embedding off-screen for left-floated node in RTL environment,"To reproduce:
+
+1. Edit the Hebrew Wikipedia article about Haifa:
+https://he.wikipedia.org/wiki/%D7%97%D7%99%D7%A4%D7%94?veaction=edit
+
+2. Click the infobox on top left.
+
+Observed: The pop-up puzzle bubble for editing the template appears to the left of the infobox, goes off-screen and creates a horizontal scroll-bar.
+
+Expected: The pop-up puzzle bubble must appear in a visible convenient place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414580160,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-tihohw65um5nqiof2m35,task_description,resolved
+VisualEditor: Content menu is embedding off-screen for left-floated node in RTL environment,Checked in beta/test2/production  including the page https://he.wikipedia.org/wiki/%D7%97%D7%99%D7%A4%D7%94?veaction=edit  - all look good to me too. ,1419733251,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-tihohw65um5nqiof2m35,task_subcomment,NA
+VisualEditor: Content menu is embedding off-screen for left-floated node in RTL environment,Looks good to me now. Not sure when it was fixed.,1419722431,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-tihohw65um5nqiof2m35,task_subcomment,NA
+VisualEditor: Content menu is embedding off-screen for left-floated node in RTL environment,"Did we fix this in master? It looks ""fine"" (different breakage) on http://he.wikipedia.beta.wmflabs.org/wiki/%D7%95%D7%99%D7%A7%D7%98%D7%95%D7%A8_%D7%9B%D7%A8%D7%99%D7%A1%D7%98%D7%A0%D7%A7%D7%95?veaction=edit&uselang=he",1414609808,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tihohw65um5nqiof2m35,task_subcomment,NA
+VisualEditor: [Regression] Clicking on an image with wikilink opens up link inspector,"screenshot
+
+Environment- test2
+
+1> In a blank page insert an image with a wikilink as caption.
+2> Now click on the image in the main editor. Notice in the context menu,  along with the name of the image now the link also appears.
+3> click on the context menu and it opens the link inspector for you populated with the target.
+
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15374}",1414558140,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-scoh4xqxum72mhxquk27,task_description,open
+VisualEditor: [Regression] Clicking on an image with wikilink opens up link inspector,Confirmed that the bug exists in betalabs and test2.,1414605250,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-scoh4xqxum72mhxquk27,task_subcomment,NA
+VisualEditor: [Regression] Clicking on an image with wikilink opens up link inspector,"(In reply to Ritu Swain from comment #1)
+> Also see 72431.
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72431",1414558240,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-scoh4xqxum72mhxquk27,task_subcomment,NA
+VisualEditor: [Regression] Clicking on an image with wikilink opens up link inspector,Also see 72431.,1414558213,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-scoh4xqxum72mhxquk27,task_subcomment,NA
+VisualEditor: Be able to serialise the linear model,For things like auto-save (T57370) and collaboration.,1414551060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qsgnrw34off5kbfx52lz,task_description,resolved
+VisualEditor: Be able to serialise the linear model,"Change 231017 merged by jenkins-bot:
+Provide methods to (de)serialize transactions
+
+[[https://gerrit.wikimedia.org/r/231017]]",1472060773,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsgnrw34off5kbfx52lz,task_subcomment,NA
+VisualEditor: Be able to serialise the linear model,"Change 231017 had a related patch set uploaded (by Esanders):
+Provide methods to (de)serialize transactions
+
+[[https://gerrit.wikimedia.org/r/231017]]
+",1439477911,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qsgnrw34off5kbfx52lz,task_subcomment,NA
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,"IE11 transparency flaws
+
+Steps to reproduce: 
+
+
+1. Open any page in VE on IE11(test2). 
+
+2. Click on 'Page option' icon and select 'Options'
+
+3. Options-Advanced settings have three small info icons - click on each of them - the box becomes transparent(look at the attched screenshot). There is also a screenshot of how it behaves in Chrome, for comparison. 
+
+Another way to reproduce the bug - when in Step 3 you click on the first info icon, open another browser tab, go and return back - the box for Options will become transparent.  
+
+Note: does not happen with Insert-Template(a template should have one info icon).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15339}",1414526520,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_description,resolved
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,Also can't reproduce. Please re-open if it re-occurs.,1460644121,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_subcomment,NA
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,"Cannot reproduce on beta with IE11... @Etonkovidova, is this still an issue for you?",1421201256,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_subcomment,NA
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,The dialog box 'Are you sure?' which appears when switching from Edit mode to Read is transparent too.,1414529408,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_subcomment,NA
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,"Created attachment 16934
+Chrome shows correct transparency - to compare
+
+**Attached**: {F15341}",1414526648,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_subcomment,NA
+OOjs UI: [Regression] Menu width isn't working in IE11 any more – see VisualEditor's 'Page options' drop down menu,"Page options drop down horizontal scroll bar
+
+Steps to reproduce: 
+
+1. In IE 11 in full screen- open any page for edit in VE.
+2. Click on Page option icon - the drop down menu options will be displayed partially and a horizontal window scroll bar will be displayed.
+
+{F15330}
+
+--------------------------
+**See Also**:
+{T74592}",1414523340,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-z7lqudiqsx3toqxfmyrh,task_description,resolved
+OOjs UI: [Regression] Menu width isn't working in IE11 any more – see VisualEditor's 'Page options' drop down menu,"This is caused by some IE bugs with `display: inline-table`. Applying the set of patches from T78499, which gets rid of it, fixes the issue.",1418584468,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-z7lqudiqsx3toqxfmyrh,task_subcomment,NA
+OOjs UI: [Regression] Menu width isn't working in IE11 any more – see VisualEditor's 'Page options' drop down menu,"Probably the same bug as bug 72592, but leaving distinct for now.",1415884633,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z7lqudiqsx3toqxfmyrh,task_subcomment,NA
+OOjs UI: [Regression] Menu width isn't working in IE11 any more – see VisualEditor's 'Page options' drop down menu,"As it was described in 56713 - the bug ""alternates""  i.e. 
+
+IE11 test2: Open a page in VE and click on the 'Page options' icon - the drop-down menu options are partially displayed. Then switch to 'Maximize' browser view(or if you were in  'Restore down', switch to 'Maximize'), the menu options will be displayed in full.",1414524734,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-z7lqudiqsx3toqxfmyrh,task_subcomment,NA
+VisualEditor: Text in Japanese disappears,"First reported by miya at ja.wp:
+write something in Japanese; press Enter; the whole line disappears. This also happens when adding a picture - in the Caption field.
+This does not seem to be browser or OS-specific.
+miya says that adding a ""single-byte character"" or a number at the beginning of the line, the line doesn't disappear - I don't seem able to confirm this (my tests are in Safari/X Yosemite).
+I'm able to reproduce the general issue at mediawiki.org (using the laptop input system for Katakana; hope I'm doing this right).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72508",1414497360,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-setrj27w67t7gktol4z3,task_description,resolved
+VisualEditor: Text in Japanese disappears,"As far as I can tell, this issue and other Japanese text entry issues are all now fixed. Sorry it took so long to confirm!
+
+>>! In T74619#977974, @Yukichi99 wrote:
+> Why did you change the priority?
+> I recognize this bug is blocked against using by Japanese.
+> If you have a reason, let me know.
+
+Sorry, this was done in a mass action for everything we were not working on that month.",1435941327,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-setrj27w67t7gktol4z3,task_subcomment,NA
+VisualEditor: Text in Japanese disappears,"Why did you change the priority?
+I recognize this bug is blocked against using by Japanese.
+If you have a reason, let me know.",1421280936,PHID-USER-6b5wxetq6egh6g7rvdjd,PHID-TASK-setrj27w67t7gktol4z3,task_subcomment,NA
+VisualEditor: Text in Japanese disappears,"Thanks for changing its priority!
+
+For your information, I tried the above case with Google Input method and Google chrome on Mac OS X Yosemite, got the same result. 
+
+Let me know if you need other test cases.",1418266930,PHID-USER-6b5wxetq6egh6g7rvdjd,PHID-TASK-setrj27w67t7gktol4z3,task_subcomment,NA
+VisualEditor: Text in Japanese disappears,"Confirmed in betalabs with hirogana, katakana(and, of course, not for romaji), and kanji. 
+
+Sometime it takes two hit of Enter to delete the entered text in such languages- but the text gets deleted. For English text, 'Enter' behaves normally  - a cursor goes to the new line.",1414804224,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-setrj27w67t7gktol4z3,task_subcomment,NA
+"VisualEditor Mobile: When the context menu appears in mobile, the button alignment for ""Next"" and ""Page Settings"" option at the top right gets a bit lower","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Select a link or a citation so that the context menu for it appears on the top
+
+Observed Result:
+When the context menu appears observe the positions of the buttons at the left-""Save"" and ""Settings"" icon also gets changed to a much lower position , they should be fixed while the context menu opens at the bottom of the menu bar
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15145}",1414436160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-au5g35tuuylapsk7eubl,task_description,resolved
+"VisualEditor Mobile: When the context menu appears in mobile, the button alignment for ""Next"" and ""Page Settings"" option at the top right gets a bit lower",Needs re-testing.,1430336288,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-au5g35tuuylapsk7eubl,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,"I just tested the feature
+https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2014-October/000991.html
+with VisualEditor and it seems to be using a low resolution image instead of MathMl (while editing). When I save the page,
+https://pt.wikipedia.org/w/index.php?diff=40380507
+the formula disappears and it only reappear after I reload the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414357320,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-qetvgvrqjisxdxa4u7np,task_description,resolved
+VisualEditor: Math rendering 2.0 does not work in edit mode,Verified in production  - used the sample from https://pt.wikipedia.org/w/index.php?diff=40380507: \frac{\sqrt{(x+1)}}{y^2} ,1417045436,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,"Verified the fix in test2
+
+- resolution of an edited/inserted formula in VE is the same as after saving the page
+
+- <meta name=""generator"" content=""MediaWiki 1.25wmf8""> is present",1415909541,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,"**gerritadmin** wrote:
+
+Change 172775 merged by jenkins-bot:
+Allow <meta> tags in GeneratedContentNodes
+
+https://gerrit.wikimedia.org/r/172775",1415821938,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,"**gerritadmin** wrote:
+
+Change 172775 had a related patch set uploaded by Esanders:
+Allow <meta> tags in GeneratedContentNodes
+
+https://gerrit.wikimedia.org/r/172775",1415815050,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,Isn't this what gerrit 130828 was for?,1414625185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"Environment:
+Ubuntu 14.04.1 LTS
+IBus 1.5.5
+mozc 1.13.1651.102-2
+
+Test sequence:
+0. Open a blank page with VisualEditor.
+1. Switch to Japanese input.
+2. Enter ""nihongo"".
+3. Convert it (usually by pushing down the space key). You'll see it converted ""日本語"" here.
+4. Disable Japanese input.
+5. Enter ""a"". You'll see here ""日本語"" removed and only ""a"" remaining.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72619",1414234140,PHID-USER-meyjnh7zdarfb7u7upzo,PHID-TASK-32waecquxrqyav4wai64,task_description,resolved
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"As far as I can tell, this issue and other Japanese text entry issues are all now fixed. Sorry it took so long to confirm!
+
+>>! In T74508#1014577, @whym wrote:
+> @Jdforrester-WMF: do you have any idea which change fixed it? We'd want to link it here, if possible.
+> 
+> Anyway, I think it's safe to close this task as resolved already.
+
+Sadly we've done dozens of changes to the typing support system in the past few years to fix this issue and ones like it, and we only added systematic tests for Japanese typing support this week, which helped us confirm that it was working as expected.",1435941596,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"@Jdforrester-WMF: do you have any idea which change fixed it? We'd want to link it here, if possible.
+
+Anyway, I think it's safe to close this task as resolved already.",1423061060,PHID-USER-meyjnh7zdarfb7u7upzo,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"Unsure of what changed, but I'm not experiencing this problem now on MediaWiki.org anymore.",1419134889,PHID-USER-meyjnh7zdarfb7u7upzo,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"Changed to critical as it involves loss of data, and affects significantly many (effectively all trials of editing in Japanese).",1416107856,PHID-USER-meyjnh7zdarfb7u7upzo,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,the similar issue is bug 72619.,1415296033,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"I first experienced the same bug around 2014-10-24.
+Environment:Windows 7　PC （Firefox 33.0.1,　Chrome 38.0.2125.104 m, IE 11.0.13）
+
+Test sequence 1: 
+0 - 5. All the same as Yusuke Matsubara's.
+(note: you cant move the cursor with right or left key on ""日本語"")
+
+Test sequence 2: 
+0 - 4. same as Yusuke Matsubara's.
+5. Push ""Enter key"" to make a br there. You'll see here ""日本語"" vanished and nothing remaining. 
+(It drove me panicky at first: I couldnt even copy the Japanese text there to　salvage. )
+
+Test sequence 3:
+0. Open a blank page with VisualEditor.
+1-1. Enter ""1"" (or any alphabet, any number or any sign like ""@"", ""#"", ""*"", ""^"", ...).   
+1-2. Switch to Japanese input.
+2. Enter ""nihongo"" after ""1"".
+3. Convert it (usually by pushing down the space key). You'll see it converted ""日本語"" - you'll see here ""1 日本語"" 
+4. Disable Japanese input.
+5. Enter ""a"". You'll see here ""1 日本語 a"" remaining.",1415262576,PHID-USER-uy4w45ngb7c554efp3rq,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"Above was tested browsers below:
+Mozilla Firefox 33.0
+Chromium Version 37.0.2062.120 Ubuntu 14.04 (281580) (64-bit)",1414237159,PHID-USER-meyjnh7zdarfb7u7upzo,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+"VisualEditor: Clicking on somewhere else in the document after opening a link inspector inside a slug throws error ""TypeError: Cannot read property 'previousSibling' of undefined""","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a bullet list
+3.Add some indentation 
+4.Now click on any slug that got created due to indentation
+5.Open a link inspector on that position
+6.While the link inspector is open, click somewhere else in the document to close the inspector
+
+Observed Result:
+The link inspector stays opened in that position and there is an error in the console:
+TypeError: Cannot read property 'previousSibling' of undefined
+
+See the screenshot attached
+
+Environment:Betalabs,test2 and en.wiki
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72558
+
+**Attached**: {F14916}",1414183680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2ik4qr5eikvbxsyx7ihu,task_description,resolved
+"VisualEditor: Clicking on somewhere else in the document after opening a link inspector inside a slug throws error ""TypeError: Cannot read property 'previousSibling' of undefined""","Change 190022 merged by jenkins-bot:
+Simplify slug behaviour
+
+[[https://gerrit.wikimedia.org/r/190022]]",1424725247,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2ik4qr5eikvbxsyx7ihu,task_subcomment,NA
+"VisualEditor: Clicking on somewhere else in the document after opening a link inspector inside a slug throws error ""TypeError: Cannot read property 'previousSibling' of undefined""","Change 190022 had a related patch set uploaded (by Esanders):
+Simplify slug behaviour
+
+[[https://gerrit.wikimedia.org/r/190022]]
+
+#patch-for-review",1423756455,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2ik4qr5eikvbxsyx7ihu,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Search for any image and select one 
+
+Observed Result:
+As soon as you select any image and the Media Settings dialog appears,the following error appears in the console
+
+Uncaught TypeError: Cannot read property 'isDefault' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14910}",1414181520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_description,resolved
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image",Verified the fix in production,1415226630,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image",Verified the fix in Betalabs,1414433153,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image","**gerritadmin** wrote:
+
+Change 168675 merged by jenkins-bot:
+Make sure initialHash exists before checking its value
+
+https://gerrit.wikimedia.org/r/168675",1414380313,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image","**gerritadmin** wrote:
+
+Change 168675 had a related patch set uploaded by Mooeypoo:
+Make sure initialHash exists before checking its value
+
+https://gerrit.wikimedia.org/r/168675",1414182012,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"There are different controls for the Cache-Control headers for the API and MediaWiki's OutputPage.  This may have seemed innocuous in the past, but it is causing problems now that VisualEditor is moving page editing to the API.
+
+On my local wiki pages are served with:
+
+  Cache-Control: private, must-revalidate, max-age=0
+
+and, when mCacheMode is set to 'private', the default, API responses are sent with:
+
+  Cache-Control: private
+
+[[ http://www.ietf.org/rfc/rfc2616.txt | RFC 2616 ]] says:
+
+  private
+      Indicates that all or part of the response message is intended for
+      a single user ... A private (non-shared) cache MAY cache the response.
+
+and:
+
+   A cache MAY be configured to return stale responses without
+   validation, but only if this does not conflict with any ""MUST""-level
+   requirements concerning cache validation (e.g., a ""must-revalidate""
+   cache-control directive).
+
+and:
+
+   If a cache receives a 5xx response while attempting to revalidate an
+   entry, it MAY either forward this response to the requesting client,
+   or act as if the server failed to respond. In the latter case, it MAY
+   return a previously received response unless the cached entry
+   includes the ""must-revalidate"" cache-control directive (see section
+   14.9).
+
+**old description:**
+IE 11 seems to cache faulty parsoid responses.
+
+I had a misconfigured server and, even after I fixed the problem and other browsers were able to continue after clicking ""edit"", IE didn't even attempt to make a request but just kept showing the alert box with the error message.
+",1414164780,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_description,resolved
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,Since this was merged...,1426119916,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Change 194208 merged by jenkins-bot:
+Browser should clear cache for API responses
+
+[[https://gerrit.wikimedia.org/r/194208]]",1425574879,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Change 194208 had a related patch set uploaded (by MarkAHershberger):
+Browser should clear cache for API responses
+
+[[https://gerrit.wikimedia.org/r/194208]]
+",1425421093,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Updated description with my findings.  I think this shows that while IE's behavior may be different, it isn't out-of-spec, especially given that the urls providing the content for reading are different than the urls providing content for the VisualEditor.
+
+Patch to arrive shortly.",1425419400,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Like {T73119}, my client has specified this as an important issue.  I'm looking for information on tracking down these issues.  Any pointers? ",1419810857,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Please don't use ""MSIE""; we normally call it ""Internet Explorer"" for clarity.",1415902721,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"It isn't just caching errors.  It looks like it is caching all sorts of responses.  I think I've seen this in more than just IE, but I can reliably reproduce it with IE.",1415902171,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,Not sure how we could work around browser-intentional behaviour like this…,1414625653,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+VisualEditor: MWTitleInputWidget should return titles,"MWTitleInputWidget should have a .getTitle() getter (which can return null, if the value isn't a valid title). Using this getter should be preferred over .getValue(). Callers of MWTitleInputWidget.getValue() should be converted to .getTitle(), and they should check for null-ness, because we probably have more bugs like bug 71998 hiding in various places.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414114860,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nhmtatolxkhjgn54hngt,task_description,resolved
+VisualEditor: MWTitleInputWidget should return titles,"Change 169603 merged by jenkins-bot:
+Introducing getTitle() in MWTitleInputWidget
+
+https://gerrit.wikimedia.org/r/169603",1414606448,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nhmtatolxkhjgn54hngt,task_subcomment,NA
+VisualEditor: MWTitleInputWidget should return titles,"Change 169603 had a related patch set uploaded by SuchetaG:
+Introducing getTitle() in MWTitleInputWidget
+
+https://gerrit.wikimedia.org/r/169603",1414534602,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nhmtatolxkhjgn54hngt,task_subcomment,NA
+VisualEditor: MWTitleInputWidget should return titles,"Also, per bug 71249, now that we have isValid() in TextInputWidget, it makes sense for MWTitleInputWidget to reimplement isValid() as a check for getTitle() not being null.",1414117466,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nhmtatolxkhjgn54hngt,task_subcomment,NA
+VisualEditor: Reorganize and restrategize how Scalable information works with all existing images,"Make the API call for scalable information unified on load, and make sure the call only comes out once per image (at least) and is persistent between the image and the image model in the edit dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414088400,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-uzavsh7jiyrspclcykx3,task_description,open
+VisualEditor: Reorganize and restrategize how Scalable information works with all existing images,Unassigning myself - but I'm pretty sure this is irrelevant now after the many many refactorings done to the code?,1468967195,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-uzavsh7jiyrspclcykx3,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"inspector opens up on the left side in FF 33.0
+
+Environment- beta
+
+1> In VE, insert a media(with any settings but no content in ""Caption"") to blank page.
+
+2> Highlight the image and select link or language from the toolbar.The inspector opens and closes quickly.
+
+This happens in chrome 38 only.
+
+In FF 33.0, when you do the above steps, the inspectors do not open on top of the image.But always on the left side in the CE .See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14768}",1414082160,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-vexowcgnl3zfx2wx744e,task_description,open
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"Also see 72660, https://bugzilla.wikimedia.org/show_bug.cgi?id=72660",1414558284,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"Created attachment 16939
+Caption appearing in the link target field
+
+**Attached**: {F14769}",1414556839,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"(In reply to James Forrester from comment #2)
+> I believe that this is describing intentional functionality for links? You
+> can't make an image into a link in wikitext (there's a distinct feature
+> about image target but that's tracked elsewhere).
+> 
+> But yes, this needs to be cleaned up a bit (especially the different
+> behavior between Firefox and Chrome).
+
+I also noticed that when i try to apply link to images having caption,the link inspector opens with the caption text as link target in the input field(which i thought was fine).
+
+Environment-test2, beta, production
+steps-
+1> insert a media with a caption(could be an internal link or text).Highlight the image and select to apply link.
+2> Link inspector opens on top of the image, populated with the caption in the input field.
+3> Click done and the inspector closes.See screenshot.
+
+Is this expected?",1414556756,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"I believe that this is describing intentional functionality for links? You can't make an image into a link in wikitext (there's a distinct feature about image target but that's tracked elsewhere).
+
+But yes, this needs to be cleaned up a bit (especially the different behaviour between Firefox and Chrome).",1414441147,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"Now reproducible in test2.
+
+1> insert a media with no captions.Highlight the image and select to apply link or language.
+2> Link or language inpsector opens and closes quickly.",1414164069,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Parsoid output has broken output because Mediawiki:common.css is not included.
+
+For example:
+http://parsoid-lb.eqiad.wikimedia.org/frwiki/Guerre_froide?oldid=108085194
+
+Here the original version:
+https://fr.wikipedia.org/w/index.php?title=Guerre_froide&oldid=108085194
+
+And with the visual editor:
+https://fr.wikipedia.org/w/index.php?title=Guerre_froide&oldid=108085194&veaction=edit
+
+Like you can see the infobox width is huge probably because there is no rule for the ""infobox_v2"" CSS class.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414054260,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_description,resolved
+"Navbox rendering incorrect, all items in the same line","Tidy is no longer around and Remex and Parsoid have the same HTML5 behavior. So, this is no longer an issue.",1592506990,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",I've just filed {T155634} which also has some spaces inserted (which may be relevant).,1484754322,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Also, see https://www.mediawiki.org/wiki/Parsing/Replacing_Tidy .. especially Sections 2.2 and 2.5 on that page.
+
+As part of T89331, we are working to replace Tidy with a proper HTML5 parser which will require wikitext fixes of the kind that @Od1n did above.",1466083632,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",Please note I have workarounded the above issue since: https://fr.wikipedia.org/w/index.php?title=Mod%C3%A8le:Portail&diff=prev&oldid=126720710,1466056889,PHID-USER-povcbbfr2b6v4te3anc7,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Same issue occurs with <li> tags.
+[[https://fr.wikipedia.org/w/index.php?title=Utilisateur:Pols12/brouillon_eve&oldid=126290496|An example]] on fr.wiki: there are a <li> per line in HTML code however all <li> tags are displayed on the same line with VisualEditor (with Template:Portail)",1463595328,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Same issue occurs with <li> tags.
+[[https://fr.wikipedia.org/w/index.php?title=Utilisateur:Pols12/brouillon_eve&oldid=126290496|An example]] on fr.wiki: there are a <li> per line in HTML code however all <li> tags are displayed on the same line with VisualEditor.",1463595253,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","We'll have to figure out what to do about this Tidy-caused discrepancy. Template edit to not depend on this Tidy effect might be the simplest. For now, moving this out of Q4.",1433276814,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Tidy decodes and moves the space:
+
+```
+> print MWTidy::tidy('<span class=""a""><span class=""b"">x</span>&#32;</span>y');
+
+<p><span class=""a""><span class=""b"">x</span></span> y</p>
+
+> $opt = new ParserOptions;
+
+> print $wgParser->parse('<span class=""a""><span class=""b"">x</span>&#32;</span>y', Title::newMainPage(), $opt)->getText();
+
+<p><span class=""a""><span class=""b"">x</span>&#32;</span>y
+</p>
+
+> $opt->setTidy(true);
+
+> print $wgParser->parse('<span class=""a""><span class=""b"">x</span>&#32;</span>y', Title::newMainPage(), $opt)->getText();
+
+<p><span class=""a""><span class=""b"">x</span></span> y</p>
+```",1433201054,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",">>! In T74416#1322436, @ssastry wrote:
+> The second part to this puzzle here is: even if the space char entity was *outside*, Parsoid would wrap that entity with a mw:Entity span which would also likely break the CSS rendering in this case.
+
+So, I was wrong it looks like, thankfully. If I manually edited the HTML to:
+```</span><span typeof=""mw:Entity""> </span><span class=""nowrap""```
+the rendering is correct, of course, since the nowrap class doesn't apply to the entity span.
+
+So, if we can figure out the action=parse vs action=expandtemplates difference, we might be on our way to solving this issue. We need to figure out whether one of those API endpoints has a bug and/or the template needs fixing.
+",1432942780,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",@tstarling: any clue what is going on there with action=expandtemplates vs action=parse ? Can also dig into code next week.,1432942282,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","This is interesting.
+
+Compare: 
+https://fr.wikipedia.org/w/api.php?action=parse&format=json&text={{Palette|Seconde%20Guerre%20mondiale|Guerre%20froide|Communisme|Histoire%20des%20%C3%89tats-Unis}}
+vs.
+ https://fr.wikipedia.org/w/api.php?action=expandtemplates&format=json&text={{Palette|Seconde%20Guerre%20mondiale|Guerre%20froide|Communisme|Histoire%20des%20%C3%89tats-Unis}}
+
+So, action=expandtemplates returns:
+```... </span>&#32;</span><span class=""nowrap"" ... ```
+and action=parse returns:
+```... </span></span> <span class=""nowrap"" ...```
+
+How did the &#32; (which is a space char) move from inside the span to outside because of parsing? Parsoid is of course processing the result of action=expandtemplates and faitfully preserves the whitespace char where it exists .. inside the previous span. Something is goofy with the PHP parser there .. Or is it Tidy that is doing this?
+
+The second part to this puzzle here is: even if the space char entity was *outside*, Parsoid would wrap that entity with a mw:Entity span which would also likely break the CSS rendering in this case.",1433199968,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","This is interesting.
+
+Compare: 
+https://fr.wikipedia.org/w/api.php?action=parse&format=json&text={{Palette|Seconde%20Guerre%20mondiale|Guerre%20froide|Communisme|Histoire%20des%20%C3%89tats-Unis}}
+vs.
+ https://fr.wikipedia.org/w/api.php?action=expandtemplates&format=json&text={{Palette|Seconde%20Guerre%20mondiale|Guerre%20froide|Communisme|Histoire%20des%20%C3%89tats-Unis}}
+
+So, action=expandtemplates returns:
+```.. </span>&#32;</span><span class=""nowrap"" ```
+and action=parse returns:
+```</span></span> <span class=""nowrap"">```
+
+How did the &#32; (which is a space char) move from inside the span to outside because of parsing? Parsoid is of course processing the result of action=expandtemplates and faitfully preserves the whitespace char where it exists .. inside the previous span. Something is goofy with the PHP parser there .. Or is it Tidy that is doing this?
+
+The second part to this puzzle here is: even if the space char entity was *outside*, Parsoid would wrap that entity with a mw:Entity span which would also likely break the CSS rendering in this case.",1432942154,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",I verified by manually adding that single space between the spans and the navbox table at the bottom renders properly. The infobox at the top has the same problem and is fixed if I manually added that single space between spans.,1432941323,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Okay, I checked. There is a subtle but important difference that is causing this.
+
+In the PHP output, between the individual links in that column, there is a single whitespace character.
+```
+... </span> <span class=""nowrap""> ...
+```
+In Parsoid output, there is no whitespace  between the individual links
+```
+ ...</span><span class=""nowrap"" data-parsoid='{""stx"":""html""}'> ...
+```
+Without the whitespace, and with the nowrap class on the links, this means that there is no place for the browser to break the line, and hence that column stretches out forever. So, we need to figure out the reason why that single whitespace is being lost in Parsoid output.",1432941000,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",I don't think it is mw:Entity entirely ... I am testing a html dump from that page where I replaced the mw:Entity with space or the entity as in the PHP html and it didn't change the rendering substantially. This requires some more digging into the HTML diffs between the two.,1416234700,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Mediawiki:Common.css is included by the parsoid-rendered page, you can see this inspecting the infobox table with Firebug (or similar).
+
+The rendering problem comes from the navboxes at the end, which have all the links in each cell in the 2nd column in the same line, instead of wrapping them. If (using Firebug) the .nowrap style (or just ""white-space: nowrap;"") is disabled, the page returns to a more appropriate width.
+
+The only difference I can see in the HTML is the presence of multiple mw:Entity elements to indicate the white-space present in wikitext, so maybe that's what's interfering with nowrap.",1414511626,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+VisualEditor Mobile: The Citation icon does not get highlighted upon clicking or tapping on it in Mobile VE using desktop Safari and iOS safari,"Screenshot
+
+Steps to reporduce
+
+
+When you tap on Bold, Italic or Link buttons from the toolbar, the icons for these become highlighted in the toolbar.but when you tap on citation icon , there is no highlight on it, which looks a bit inconsistent
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14712}",1414024140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-irwbawwd34nibsp6cr6n,task_description,resolved
+VisualEditor Mobile: The Citation icon does not get highlighted upon clicking or tapping on it in Mobile VE using desktop Safari and iOS safari,Toolbar has changed a lot since this.,1438966850,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-irwbawwd34nibsp6cr6n,task_subcomment,NA
+VisualEditor Mobile: Cannot overwrite a text entered in CE in mobile VE using desktop Firefox,"Steps to reproduce:
+
+1.Open any page with mobile VE
+2.Type a text
+3.Select the text and type something else to overwrite it'
+
+Observed Result:
+Nothing gets entered into the CE and does not replace the old text
+
+
+Environment: Production, test2 and Betalabs",1414023600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iybf6jspgbrl4k2sojui,task_description,resolved
+VisualEditor Mobile: Cannot overwrite a text entered in CE in mobile VE using desktop Firefox,I can't reproduce this on Firefox 70.0b5 on Mac 10.14.6.,1568158597,PHID-USER-cbjanejnwkkrbnj77d2d,PHID-TASK-iybf6jspgbrl4k2sojui,task_subcomment,NA
+VisualEditor Mobile: Double clicking on citation note in Mobile using desktop Safari opens up the Basic reference dialog which was explicitly disabled for Mobile,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE which has citation note in it using desktop Safari
+
+2.Now double click on citation 
+
+Observed Result:
+It opens the Basic Reference dialog , which we explicitly disabled because there were lot of things we didn't implement inside that dialog
+
+See the screenshot attached
+
+Environment: Betalabs, test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15388}",1414022220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-urbyde4ziyfvfk6kwccx,task_description,declined
+VisualEditor Mobile: Double clicking on citation note in Mobile using desktop Safari opens up the Basic reference dialog which was explicitly disabled for Mobile,"In the weekly triage on 2015-04-22, this task was discussed. We decided to decline this task, as making all functions available is part of the plan for mobile.",1429738870,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-urbyde4ziyfvfk6kwccx,task_subcomment,NA
+VisualEditor Mobile: The context menu for Citations are not appearing after tapping on it when the keyboard is closed,"Screenshot
+
+Steps to reproduce:
+
+1.Load a page with Citations with Mobile VE in iOS safari or desktop Safari
+2.Keep the keyboard closed in iOS Safari so that the cursor is not active in CE, for desktop just click somewhere out of CE to keep the cursor inactive on CE
+3.Now click or tap on Citation note
+
+Observed Result:
+The context menu for it does not appear and a light shade of highlight appears on top of it when I click but it also goes away
+
+
+  
+See the screenshot attached
+
+Environment:test2, Betalabs and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15386}",1414020240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wljrwrl4avglyuy7j5wi,task_description,resolved
+VisualEditor Mobile: The context menu for Citations are not appearing after tapping on it when the keyboard is closed,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488130,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wljrwrl4avglyuy7j5wi,task_subcomment,NA
+VisualEditor Mobile: The context menu for Citations are not appearing after tapping on it when the keyboard is closed,Needs re-testing.,1430336136,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wljrwrl4avglyuy7j5wi,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE which does not have any reference in it to re-use.
+
+
+Observed Result:
+
+The ""Re-use"" label for the button is not greyed out even if the button icon is 
+
+See the screenshot attached
+Environment:Production,test2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15377}",1414019340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n73esked2uknidkk6dcc,task_description,resolved
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)",Verified the fix in production,1415834434,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)",Verified the fix in test2,1415229246,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)",Verified the fix in Betalabs,1415059679,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","**gerritadmin** wrote:
+
+Change 170790 merged by jenkins-bot:
+VE: Don't set @grayDark colour for tool titles in disabled widgets
+
+https://gerrit.wikimedia.org/r/170790",1415054928,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","**gerritadmin** wrote:
+
+Change 170790 had a related patch set uploaded by Alex Monk:
+VE: Don't set @grayDark colour for tool titles in disabled widgets
+
+https://gerrit.wikimedia.org/r/170790",1415047180,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","(In reply to Alex Monk from comment #1)
+> Looks like this is caused by MobileFrontend's
+> less/modules/editor/VisualEditorOverlay.less file - specifically this part:
+> .oo-ui-tool-title {
+>     color: @grayDark;
+>     font-size: .9em;
+> }
+> Which is taking precedence over the styles for the oo-ui-widget-disabled
+> stuff.
+> 
+> What if we changed it to this?
+> .oo-ui-widget-enabled > .oo-ui-tool-title {
+>     color: @grayDark;
+> }
+> .oo-ui-tool-title {
+>     font-size: .9em;
+> }
+
+Eurgh. Another reminder that we need to kill VisualEditorOverlay.less.",1415031272,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","Looks like this is caused by MobileFrontend's less/modules/editor/VisualEditorOverlay.less file - specifically this part:
+.oo-ui-tool-title {
+    color: @grayDark;
+    font-size: .9em;
+}
+Which is taking precedence over the styles for the oo-ui-widget-disabled stuff.
+
+What if we changed it to this?
+.oo-ui-widget-enabled > .oo-ui-tool-title {
+    color: @grayDark;
+}
+.oo-ui-tool-title {
+    font-size: .9em;
+}",1414882548,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+VisualEditor: Move default value and autoValue code from MWParameterPage (UI) to MWParameterModel (DM),"Half of dm.MWParameterModel is dedicated to looking things up in the parent template's spec. Despite that, ui.MWParameterPage manually looks up the default value and autoValue because there are no getters in dm.MWParameterModel for those things, for no good reason whatsoever. Those getters should be added.
+
+What's even worse is the ""if there is no real value, set the value to the autoValue"" logic (added in https://gerrit.wikimedia.org/r/168204 ). Currently this logic (which is fundamentally DM logic) is in ui.ParameterPage as well. Instead, MWParameterPage.getValue() should be smart enough to return either the real value or the autoValue if there is no real value.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414019220,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gsdjjehs7duzg6p7efj3,task_description,resolved
+VisualEditor: Move default value and autoValue code from MWParameterPage (UI) to MWParameterModel (DM),"**gerritadmin** wrote:
+
+Change 168926 merged by jenkins-bot:
+Move autoValue logic from ui.MWParameterPage to dm.MWParameterModel
+
+https://gerrit.wikimedia.org/r/168926",1414433710,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gsdjjehs7duzg6p7efj3,task_subcomment,NA
+VisualEditor: Move default value and autoValue code from MWParameterPage (UI) to MWParameterModel (DM),"**gerritadmin** wrote:
+
+Change 168926 had a related patch set uploaded by Alex Monk:
+Move autoValue logic from ui.MWParameterPage to dm.MWParameterModel
+
+https://gerrit.wikimedia.org/r/168926",1414380772,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gsdjjehs7duzg6p7efj3,task_subcomment,NA
+VisualEditor: Move default value and autoValue code from MWParameterPage (UI) to MWParameterModel (DM),"(In reply to Roan Kattouw from comment #0)
+> Instead, MWParameterPage.getValue() should be
+> smart enough to return either the real value or the autoValue if there is no
+> real value.
+
+MWParameterModel.getValue()?",1414336868,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gsdjjehs7duzg6p7efj3,task_subcomment,NA
+VisualEditor: Pasting in text containing a tab character causes VE to scroll to the top,"Intention:
+Paste bibliographic information from Google books
+
+Steps to Reproduce:
+1. Almost any book will do for this, but to pick an example http://books.google.co.uk/books?id=VYvS7MyaEE8C
+2. Scroll down to the ""Bibliographic information"" section at the end
+3. Select everything between the name of the publisher and the first ISBN number.  Ignoring whitespace, you should have something like ""Academic Press, 2012 ISBN 0123914213"" on the clipboard. It is important that the selection spans at least two lines and includes at least one tab character.  Other than that it is not vital what infomation from the bib is selected, but this is what I would normally select and gives me problems.
+4. Choose a Wikipedia page with a substantial amount of text, or create one in sandbox
+5. Launch VE and scroll down far enough so the top of the article is no longer visible.
+6. Start a new line and type some text such as ""Author name, Book Title, "" (this step is essential)
+7. Paste the clipboard contents immediately at the end of this line (this currently has to be done with right-click paste rather than CTrl-V due to another bug, but this was still happening before Ctrl-V got broke)
+
+
+Actual Results:  
+The part of the article you are working on (this will usually be the references or bibliography section right at the end of the article) disappears from sight as VE scrolls right to the top of the article.
+
+Expected Results:  
+The focus should stay at the pasting insertion point.
+
+Scrolling to the top also occurs when a tab is typed from the keyboard, which I assume is related.  Possibly this is meant to be a feature, but it is not a very helpful one - I find myself typing tabs while in tables expecting to tab to the next cell as is common on internet forms.  I know VE doesn't do this, but the expected behaviour is so ingrained I keep getting caught out.  In any case, a tab pasted in with text doing this is definitely a bug.
+
+Reproducible: Didn't try
+
+The bug is quite intrusive to me, I am frequently pasting in source bibliographic information, almost every session.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**: {T73728}",1414014540,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-nngads3asyp22g2mfznd,task_description,resolved
+VisualEditor: Pasting in text containing a tab character causes VE to scroll to the top,"Works for me on en.wiki. Feel free to reopen if necessary.
+",1433463442,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-nngads3asyp22g2mfznd,task_subcomment,NA
+VisualEditor: Pasting in text containing a tab character causes VE to scroll to the top,"Seems to work for me on En.wiki. Reopen if necessary.
+",1433463416,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-nngads3asyp22g2mfznd,task_subcomment,NA
+VisualEditor: Pasting in text containing a tab character causes VE to scroll to the top,"Confirmed in test2 and betalbs.
+
+Steps to reproduce: 
+
+1. Copy all(or part of) Bibliographic information on http://books.google.co.uk/books?id=VYvS7MyaEE8C. It's a html table.  
+
+2. Paste it at the end of an existing line in a chunk of text of test2 or betalabs.  The amount of text should be large enough to allow you to scroll down the page and then paste the table at the end of any line. 
+
+
+Observed result: after pasting, the page scrolls up. The pasted table is correctly placed though. The issue does not happen if a table is pasted on a new line.",1414079652,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-nngads3asyp22g2mfznd,task_subcomment,NA
+"VisualEditor: Pasting invalidly parented <figcaption> throws ""Uncaught TypeError: Cannot read property 'type' of undefined"" in ve.dm.LinearData.static.getType","1. Copy to the clipboard the below invalid rich content from NYTimes.com:
+   <div><div …><a …><img …></a></div><figcaption …>Foo</figcaption></div>
+
+2. Go to any page in VE
+
+3. Paste; observe crash of paste engine.
+
+Paste rules are probably not checking parentage (HTML spec says no <figcaption>s except as children of <figures>s) and it's breaking things. Instead, we should… eh. Downcast to <div>?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414011120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pwgzlrz42g3jw6le42cr,task_description,resolved
+"VisualEditor: Pasting invalidly parented <figcaption> throws ""Uncaught TypeError: Cannot read property 'type' of undefined"" in ve.dm.LinearData.static.getType","Although I don't have the example from NYTimes.com, copy-pasting similar HTML from a local page doesn't crash anymore (the caption text is discarded).",1535731341,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pwgzlrz42g3jw6le42cr,task_subcomment,NA
+"Use the local namespace for files, instead of the English default","If you add a file in VisualEditor, then it sometimes adds the file using the English namespace or other English terms.  Examples:
+
+https://ca.wikipedia.org/w/index.php?diff=14187112&oldid=14185423 – ""File"" is not a Catalan word
+
+https://es.wikipedia.org/w/index.php?diff=77684034&oldid=73098946 – ""File"" is not a Spanish word
+
+https://de.wikipedia.org/w/index.php?diff=135103424&oldid=135103377 – German uses ""mini"" instead of ""thumb""
+
+https://ro.wikipedia.org/w/index.php?diff=8882945&oldid=7944846 – ""File"" is not a Romanian word
+
+https://ru.wikipedia.org/w/index.php?diff=66358996&oldid=55356951 – or Russian
+
+https://sv.wikipedia.org/w/index.php?diff=28184524&oldid=20202611 – or Swedish
+
+https://pl.wikipedia.org/w/index.php?title=Pawe%C5%82_z_Eginy&diff=40760929&oldid=38644980 – or Polish 
+
+https://it.wikipedia.org/w/index.php?title=Paolo_di_Egina&diff=68773170&oldid=63002904 – or Italian
+
+
+In other cases, it did use the local name, including French, Hungarian, and Estonian.  I'm not sure what the common thread is.  It's possible that some of these communities deliberately choose to use the English namespace, but at least a few change such edits.  If we can use the local name more often, then we should be able to reduce the burden on local communities.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1414004040,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gglnxexerzlpc27dmjou,task_description,open
+"Use the local namespace for files, instead of the English default","Thought this was already filed with Parsoid, but I can't find it. Please merge if I've missed it!",1414004465,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gglnxexerzlpc27dmjou,task_subcomment,NA
+Give a hint there is a save button in action=edit,"While observing three librarians editing each their own page, I noticed that they had uncertainties when asked to save their edit. I had to explain them they have to scroll the page, and exactly where to scroll: not the text area, the whole page.
+
+Indeed, the save button is easily outside the screen, even without overly long copyrightwarning areas. We should always give a hint to users so that they know where to proceed.
+
+Something as simple as a biggish button on top of the text area, linking the [[#wpSave]] anchor, might even suffice. Worth some prototyping and usability testing IMHO.
+
+I filed a twin report for VisualEditor without realising:  T90864
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413971040,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-3l67fot6jvz627mticzv,task_description,open
+Give a hint there is a save button in action=edit,This is really usability rather than accessibility.,1520998387,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-3l67fot6jvz627mticzv,task_subcomment,NA
+Give a hint there is a save button in action=edit,"Created attachment 16839
+Save buttons outside of screen
+
+**Attached**: {F15242}",1413971086,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-3l67fot6jvz627mticzv,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open Link inspector in an empty line 
+
+
+Observed Result:
+A scroll bar is appearing inside the link inspector
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15203}",1413931380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xm2mk6rfi3neidlarp5g,task_description,resolved
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,Verified the fix in production,1414613285,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,Verified the fix in test2,1414101630,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,"**gerritadmin** wrote:
+
+Change 168206 merged by jenkins-bot:
+Increase inspector height by 1 to deal with Chrome opacity bug
+
+https://gerrit.wikimedia.org/r/168206",1414020472,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,"**gerritadmin** wrote:
+
+Change 168206 had a related patch set uploaded by Esanders:
+Increase inspector height by 1 to deal with Chrome opacity bug
+
+https://gerrit.wikimedia.org/r/168206",1414018115,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,"Proximate cause is https://gerrit.wikimedia.org/r/#/c/167446/ , it was working before that change.
+
+What seems to be going on is that there's a browser bug in Chrome that causes the inspector's body to immeasurably have a slightly greater height if the opacity of the Open button is not equal to 1. That's why this bug is only reproducible in creation mode, and the scrollbar goes away as soon as you type: the Open button is initially disabled (opacity:0.5), then enabled when you type something (opacity:1).
+
+If you want entertainment, inspect an enabled Open button, add opacity:0.999; to it and toggle it off and on a few times.",1413936016,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"This site, https://wiki.transitionnetwork.org/ is running on amd64 Debian Wheezy with Parsoid installed using apt as per the instructions at https://www.mediawiki.org/wiki/Parsoid/Setup#Ubuntu_.2F_Debian_on_amd64
+
+Today the new GPG siging key was installed and Parsoid updated (see https://trac.transitionnetwork.org/trac/ticket/692#comment:103 ) to version 0.1.15 and this has caused all edits using the VisualEditor to generate 500 errors, this is what is logged when you try to save a page:
+
+  [info][localhost/Sandbox2?oldid=946] started parsing
+  [fatal/request][localhost/Sandbox2?oldid=946] undefined is not a function
+  TypeError: undefined is not a function
+      at TreeBuilder.resetState (/usr/lib/parsoid/src/lib/mediawiki.HTML5TreeBuilder.node.js:61:17)
+      at new TreeBuilder (/usr/lib/parsoid/src/lib/mediawiki.HTML5TreeBuilder.node.js:28:7)
+      at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:231:17)
+      at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:227:17)
+      at ParserPipelineFactory.getPipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:363:15)
+      at ParserPipelineFactory.parse (/usr/lib/parsoid/src/lib/mediawiki.parser.js:311:20)
+      at /usr/lib/parsoid/node_modules/prfun/lib/index.js:436:24
+      at new Promise (/usr/lib/parsoid/src/node_modules/es6-shim/es6-shim.js:1228:11)
+      at /usr/lib/parsoid/node_modules/prfun/lib/index.js:419:14
+      at /usr/lib/parsoid/src/api/routes.js:152:62
+
+The error presented to editors is:
+
+> Error loading data from server: parsoidserver-http-bad-status: 500. Would you like to retry?
+
+I have reverted to the old version of parsoid to get around this issue:
+
+  apt-get install parsoid=0.1.12
+
+There are some more details on this ticket https://trac.transitionnetwork.org/trac/ticket/799
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Linux
+",1413895440,PHID-USER-hlhhdspdobxg2jb5lyms,PHID-TASK-g4sqyb3luctzxk2bog3r,task_description,declined
+Parsoid 0.1.15 generates 500 errors when editing pages,"@chrisc, I'm sadly a bit out of ideas. I haven't been able to reproduce this so far (but am running sid), and it seems to be working fine for most users. I would just put it down to wheezy, except that it's a JS error that would be specific to running old JS code.
+
+Is your `sources.list` line matching the one recommended at https://www.mediawiki.org/wiki/Parsoid/Setup#Ubuntu_.2F_Debian_on_amd64 ?",1424471190,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"@chrisc, I'm sadly a bit out of ideas. I haven't been able to reproduce this so far (but am running sid), and it seems to be working fine for most users. I would just put it down to wheezy, except that it's a JS error that would be specific to running old JS code.",1424471080,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"Yes, I tried that and it didn't make a difference I'm afraid, anything else I could try?",1419078211,PHID-USER-hlhhdspdobxg2jb5lyms,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,@ChrisC Is the error message still the same after a `apt-get remove --purge parsoid` followed by `apt-get install parsoid`?,1418941862,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"This is with `0.10.29~dfsg-1~bpo70+1` on Wheezy, with `nodejs/wheezy-backports` and `nodejs-legacy/wheezy-backports`:
+
+  cat /etc/debian_version 
+  7.7
+
+  aptitude search node | grep ^i
+  i A nodejs                          - evented I/O for V8 javascript             
+  i   nodejs-legacy                   - evented I/O for V8 javascript (legacy syml
+
+  dpkg --print-avail nodejs
+  Package: nodejs
+  Priority: optional
+  Section: web
+  Installed-Size: 2811
+  Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
+  Architecture: amd64
+  Version: 0.10.29~dfsg-1~bpo70+1
+  Depends: libc-ares2 (>= 1.8.0), libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), libssl1.0.0 (>= 1.0.1), libstdc++6 (>= 4.1.1), libv8-3.14.5, zlib1g (>= 1:1.1.4)
+  Size: 900744
+  Description: evented I/O for V8 javascript
+   Node.js is a platform built on Chrome's JavaScript runtime for easily
+   building fast, scalable network applications. Node.js uses an
+   event-driven, non-blocking I/O model that makes it lightweight and
+   efficient, perfect for data-intensive real-time applications that run
+   across distributed devices.
+   .
+   Node.js is bundled with several useful libraries to handle server
+   tasks:
+   .
+   System, Events, Standard I/O, Modules, Timers, Child Processes, POSIX,
+   HTTP, Multipart Parsing, TCP, DNS, Assert, Path, URL, Query Strings.
+  Homepage: http://nodejs.org/
+
+  dpkg --print-avail nodejs-legacy
+  Package: nodejs-legacy
+  Priority: extra
+  Section: web
+  Installed-Size: 101
+  Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
+  Architecture: all
+  Source: nodejs
+  Version: 0.10.29~dfsg-1~bpo70+1
+  Depends: nodejs (>= 0.6.19~dfsg1-3~)
+  Conflicts: node
+  Size: 80428
+  Description: evented I/O for V8 javascript (legacy symlink)
+   Node.js is a platform built on Chrome's JavaScript runtime for easily
+   building fast, scalable network applications. Node.js uses an
+   event-driven, non-blocking I/O model that makes it lightweight and
+   efficient, perfect for data-intensive real-time applications that run
+   across distributed devices.
+   .
+   This package contains a symlink for legacy Node.js code requiring
+   binary to be /usr/bin/node (not /usr/bin/nodejs as provided in Debian).
+   .
+   No other Debian packages should depend on this package.  For more
+   information, see
+   <http://lists.debian.org/debian-devel-announce/2012/07/msg00002.html>
+  Homepage: http://nodejs.org/
+  
+  dpkg -L nodejs | grep bin/
+  /usr/bin/nodejs
+  
+  dpkg -L nodejs-legacy | grep bin/
+  /usr/bin/node
+
+  ls -lah /usr/bin/node
+  lrwxrwxrwx 1 root root 6 Aug  3 02:41 /usr/bin/node -> nodejs
+  
+  ps -lA | grep node
+  5 S     0  2738     1  0  80   0 - 12885 -      ?        00:13:29 munin-node
+  0 S   110 28296 28294  0  80   0 - 150789 -     ?        00:00:00 nodejs
+  0 S   110 28298 28296  0  80   0 - 184463 -     ?        00:00:02 nodejs
+  0 S   110 28299 28296  0  80   0 - 163198 -     ?        00:00:00 nodejs
+
+",1417743339,PHID-USER-hlhhdspdobxg2jb5lyms,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"I built & tested the 0.2.0 package on sid. Could this perhaps be a wheezy-specific issue? Which node version are you running? There are 0.10 package available in backports: https://packages.debian.org/wheezy-backports/nodejs
+
+We are generally running 0.10 these days, but used to support 0.8 until fairly recently.",1417710631,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"No change, switched to the latest version and when I tried to edit a page I got:
+
+//""Error loading data from server: parsoidserver-http-bad-status: 500. Would you like to retry?""//
+
+So I have reverted to the old version.
+
+Is there anything else I could do to help debug this?",1417695182,PHID-USER-hlhhdspdobxg2jb5lyms,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,We just released v0.2.0 to both npm and the Debian repository. Could you check if this issue is fixed?,1417572579,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"The HTML5 library was updated in the deploy repo at the end of August, which was after the 0.1.12 deb release. I'm not sure if the deb packages that (@Gwicke?) but did you try running `npm install`?",1416959240,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,gwicke: Any clue about the published debian package? Is this just a matter of updating the debian package?,1416235849,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"Yes, looks to me like a conflict with the html5 library. I don't know much about our Debian packaging though.",1413946419,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"This sounds like it's caused by the silently-breaking-change made by one of the upstream npm modules – Parsoid team, could you advise?",1413914687,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+VisualEditor: Categories set in wikitext not showing up in category dialog on a category page,"Open https://it.wikipedia.org/wiki/Categoria:Personalità_del_buddhismo?veaction=edit .
+Notice that no categories appear in the category dialog, while that page features 2 of them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61921",1413894840,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sxtng5ghv2nfoij5k4cf,task_description,resolved
+VisualEditor: Categories set in wikitext not showing up in category dialog on a category page,"
+
+*** This bug has been marked as a duplicate of bug 72080 ***",1413917443,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-sxtng5ghv2nfoij5k4cf,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Screenshot
+
+Steps to reproduce:
+
+1.Load a page from http://en.m.wikipedia.beta.wmflabs.org/wiki/
+2.Open the page in Edit Source mode first
+3.Now go to the Settings icon and try to open the page with Mobile VE
+
+Observed Result:
+The following error appears in the console and VE does not open, stays in Edit Source mode:
+""TypeError: Cannot set property 'MWMobileContext' of undefined""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15064}",1413842040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zetzc2ngsimcakpv3og3,task_description,resolved
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears",Verified the fix in test2,1414103122,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears",Verified the fix in Betalabs,1413932523,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Change 167850 merged by jenkins-bot:
+Followup fbc7ecb: make mediawiki.mobile depend on core.mobile, not core
+
+https://gerrit.wikimedia.org/r/167850",1413922833,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Change 167850 had a related patch set uploaded by Catrope:
+Followup fbc7ecb: make mediawiki.mobile depend on core.mobile, not core
+
+https://gerrit.wikimedia.org/r/167850",1413915635,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Change 167715 merged by jenkins-bot:
+Followup e20b47f: make .mediawiki.mobile depend on .core
+
+https://gerrit.wikimedia.org/r/167715",1413844553,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Change 167715 had a related patch set uploaded by Catrope:
+Followup e20b47f: make .mediawiki.mobile depend on .core
+
+https://gerrit.wikimedia.org/r/167715",1413842758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"From a Wikia staff member working on ZH communities:
+
+Basically we need to type Pinyin (English words) first to select Chinese characters, but the New VisualEditors react very slowly or over fast. Before I make a Chinese word, the en words already pop up and are put in the editor.
+
+Here's a video of the bug happening on Mediawiki.org: http://youtu.be/G1WStvYrPPA 
+
+Report comes from Mac/Chrome but it could be happening on more.
+
+I asked if this was the same issue as T63429 but he said it was not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1413825840,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_description,invalid
+ZH IME input sometimes inserts latin characters,VulpesVulpes825: Thanks for the quick reply and thanks for re-testing!,1589878465,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"@Aklapper, I cannot reproduce it using the Pinyin IME on macOS 10.15.4 using Safari 13.1, Chrome 81.0.4044.138, and Firefox 76.0.1. Hence I have closed this task as invalid. If anyone can reproduce this phenomenon, please update steps to reproduce and feel free to reopen the task.",1589877303,PHID-USER-pb7r4bwzfkqxwgliqtet,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"@Liuxinyu970226: Can you explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle))?
+
+Also, three years later: Does anyonw still see this problem? And if yes, can provide updated steps to reproduce? Thanks!",1589876469,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,">>! In T74268#3136097, @Arthur2e5 wrote:
+> This happens on zhwiki too. And well, the reporter mentioned MediaWiki.org itself! No reason to keep it in ""Non-WMF sites"".
+> 
+> Certain pinyin IMEs (e.g. MS Pinyin) like to give the latin characters in the ""pinyin buffer"" area ahead of time, since it helps the application (e.g. search engine) make predictions. Visual Editor sometimes randomly trips over a point and keeps prematurely engulfing these characters. The code editor for Lua and JavaScript, on the other hand, consistently displays this problem with near-zero randomness.
+> 
+> My personal workaround to this problem occurs is switching to RIME until I finish one edit.
+
+Thank you for your clarification, however, I doubt if you have a fixme way due to T155928#3015470:
+>>! In T155928#3015470, @dchan wrote:
+> Change 336648 (which I've just merged) makes Tab step directly into the next cell. So you still get this problem, but only once when editing multiple adjacent cells.
+> 
+> I think that's probably the best we can do on this, until/unless Javascript/IME integration improves. (See https://w3c.github.io/input-events/ for current activity in this area).",1490677441,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"This happens on zhwiki too. And well, the reporter mentioned MediaWiki.org itself! No reason to keep it in ""Non-WMF sites"".
+
+Certain pinyin IMEs (e.g. MS Pinyin) like to give the latin characters in the ""pinyin buffer"" area ahead of time, since it helps the application (e.g. search engine) make predictions. Visual Editor sometimes randomly trips over a point and keeps prematurely engulfing these characters. The code editor for Lua and JavaScript, on the other hand, consistently displays this problem with near-zero randomness.
+
+My personal workaround to this problem occurs is switching to RIME until I finish one edit.
+
+",1490666413,PHID-USER-2qhtjovziou4utiyiop5,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"This happens on zhwiki too. And well, the reporter mentioned MediaWiki.org itself! No reason to keep it in ""Non-WMF sites"".
+
+Certain pinyin IMEs (e.g. MS Pinyin) like to give the latin characters in the ""pinyin buffer"" area ahead of time, since it helps the e.g. search engine make predictions. Visual Editor sometimes randomly trips over a point and keeps prematurely engulfing these characters. The code editor for Lua and JavaScript, on the other hand, consistently displays this problem with near-zero randomness.
+
+My personal workaround to this problem occurs is switching to RIME until I finish one edit.
+
+",1490666391,PHID-USER-2qhtjovziou4utiyiop5,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"This happens on zhwiki too. And well, the reporter mentioned MediaWiki.org itself! No reason to keep it in ""Non-WMF sites"".
+
+Certain pinyin IMEs (e.g. MS Pinyin) like to give the latin characters in the ""pinyin buffer"" area ahead of time, since it helps the e.g. search engine make predictions. Visual Editor sometimes randomly trips over a point and keeps prematurely engulfing these characters. The code editor for Lua and JavaScript, on the other hand, consistently displays this problem with near-zero randomness.
+
+My personal workaround when this problem occurs is switching to RIME until I finish one edit.
+
+",1490666374,PHID-USER-2qhtjovziou4utiyiop5,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Annotation continuation is working but the browser styles it wrongly (i.e., not at all)","Red color for link and blue background for language is not applied to the text
+
+Environment- test2
+
+1> Insert an internal link, the target is shown in red color. 
+2> Now while the cursor is at the last character of the link ,select the language annotation.
+3> Click Done on the inspector and type in some text. Notice although the context menu shows both Language and link labels, but the text typed is not red in color(indicating a link) and also the background color for language annotation is not applied to it. Appears as plain paragraph text.Move the cursor back and forth on the  entire text , still no change.However, when you go to new line by pressing enter key it does appear.
+
+See screenshot.
+
+In beta, the background color for language gets applied immediately but the link color takes effect only after you hit enter key to go to a new line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72108
+
+**Attached**: {F15009}",1413819600,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-y2ze4622w2dwciygcnjb,task_description,resolved
+"VisualEditor: [Regression wmf4] Annotation continuation is working but the browser styles it wrongly (i.e., not at all)","I widened the scope of bug 72108 to include this bug without realizing this bug existed, so I might as well merge them now.
+
+*** This bug has been marked as a duplicate of bug 72108 ***",1413940204,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-y2ze4622w2dwciygcnjb,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Annotation continuation is working but the browser styles it wrongly (i.e., not at all)","(In reply to Ritu Swain from comment #0)
+> Created attachment 16820 [details]
+> Red color for link and blue background for language is not applied to the
+> text
+> 
+> Environment- test2
+> 
+> 1> Insert an internal link by selecting the link icon from toolbar and typing in a name, the target is shown in red color. 
+> 2> Now while the cursor is at the last character of the link ,select the
+> language annotation.
+> 3> Click Done on the inspector and type in some text. Notice although the
+> context menu shows both Language and link labels, but the text typed is not
+> red in color(indicating a link) and also the background color for language
+> annotation is not applied to it. Appears as plain paragraph text.Move the
+> cursor back and forth on the  entire text , still no change.However, when
+> you go to new line by pressing enter key it does appear.
+> 
+> See screenshot.
+> 
+> In beta, the background color for language gets applied immediately but the
+> link color takes effect only after you hit enter key to go to a new line.
+
+**Attached**: {F15009}",1413821318,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-y2ze4622w2dwciygcnjb,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open","JS error in test2
+
+Environment- test2
+
+1> In VE,insert a media to a blank page with any settings, but without captions.
+
+2> highglight the image and then select the language from toolbar, the inspector opens on top of the image. JS error in console- ""Uncaught TypeError: Cannot read property 'resolve' of null"". clicking on done or Remove does not close the inspector.
+
+In beta , the inspector does not open when an image is highlighted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72258
+
+**Attached**: {F15001}",1413815040,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_description,resolved
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open",Verified the fix in production,1414625481,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open",Verified the fix in test2.,1414105836,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open", verified the fix in beta.,1413993678,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open","**gerritadmin** wrote:
+
+Change 168021 merged by jenkins-bot:
+Prevent JS error in getNativeRange()
+
+https://gerrit.wikimedia.org/r/168021",1413943158,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open","**gerritadmin** wrote:
+
+Change 168021 had a related patch set uploaded by Catrope:
+Prevent JS error in getNativeRange()
+
+https://gerrit.wikimedia.org/r/168021",1413942956,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open",Almost certainly the same flaw as bug 72258.,1413817346,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open","JS errors in test2
+
+Environment- test2, beta
+
+1>In VE, insert a media(with any settings but no content in ""Caption"") to blank page.
+
+2> Highlight the image and select link from the toolbar.JS Error-
+
+Uncaught TypeError: Cannot read property 'from' of null 
+Uncaught TypeError: Cannot read property 'resolve' of null 
+Uncaught TypeError: Cannot read property 'from' of null
+
+at this point.The inspector stays open and clicking on Remove or done does not close it.See screenshot. 
+
+In beta, the JS error(following the above steps) is - Uncaught TypeError: Cannot read property 'from' of null.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72259
+
+**Attached**: {F14995}",1413814140,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_description,resolved
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open",Verified the fix in production.,1414626645,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open","Verified in test2(wmf5) - FF, Chrome are fine. 
+
+Safari does not display Language and Link inspectors.",1414106930,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open",verified the fix in beta.,1413993600,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open","**gerritadmin** wrote:
+
+Change 168021 merged by jenkins-bot:
+Prevent JS error in getNativeRange()
+
+https://gerrit.wikimedia.org/r/168021",1413943162,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open","**gerritadmin** wrote:
+
+Change 168021 had a related patch set uploaded by Jforrester:
+Prevent JS error in getNativeRange()
+
+https://gerrit.wikimedia.org/r/168021",1413942992,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,"Since a few days all externl links, incl. coordinates in the upper right edge, are rendered as red links on dewiki. I guess this is a regression?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1413800400,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-3ukvlx3ldefokpkbnka7,task_description,resolved
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,Verified the fix in en.wiki,1414625832,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,Verified in test2 and betalabs(with 'Cite web' template).,1414434953,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,*** Bug 72376 has been marked as a duplicate of this bug. ***,1414007362,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,*** Bug 72287 has been marked as a duplicate of this bug. ***,1413849744,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,This was fixed in gerrit I35c9bea4.,1413816867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied (all template and wikitext blocks in it have been removed), because the button is disabled.
+
+Split off from bug 71701.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413566460,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-aj6cx3ygftk3motxe7xa,task_description,resolved
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied",Verified the fix in production.,1416270229,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","https://www.mediawiki.org/wiki/MediaWiki_1.25/Roadmap has some more details about what version (see 'Target Milestone') goes to which Wikimedia production wiki and when. Right now this change should be on the following sites in Wikimedia production: mediawikiwiki, testwiki, test2wiki, testwikidatawiki",1415051834,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","Hey Elena, it has not yet made it to production(en.wiki), since it got fixed in wmf6.Lets check it on production after wednesday deployment.",1415051636,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied",test2 is in production.,1415050161,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","Works correctly in test2.  The bug still exists in production. 
+
+To check if my steps are correct: 
+
+1.Insert a template 'Cite web' 
+
+2. Open template properties for editing - and click 'Show options'. 
+
+3. Click on a trash can symbol - all fields should be empty, but 'Apply changes' is active.
+
+4. clicking on 'Apply changes' should delete the template.",1415050084,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied",Verified in betalabs.,1414442831,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","**gerritadmin** wrote:
+
+Change 168721 merged by jenkins-bot:
+Allow removing all parts from a transclusion to remove the transclusion
+
+https://gerrit.wikimedia.org/r/168721",1414433591,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","**gerritadmin** wrote:
+
+Change 168721 had a related patch set uploaded by Alex Monk:
+Allow removing all parts from a transclusion to remove the transclusion
+
+https://gerrit.wikimedia.org/r/168721",1414192463,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","Yeah; this should be available when there are changes (and on clicking it should remove the transclusion), but it should still be disabled in ""insert"" mode (as there's nothing to insert).",1413568314,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Change the image size to a custom one
+4.Reopen the media Settings dialog
+5.Click on ""Make full size""
+Observed Result:
+Its changing the size values in the fields inside the dialog it does not enable the ""Apply Changes"" button
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14737}",1413496980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-peyhafaf5o5etsa2l5gh,task_description,resolved
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size",Verified the fix in production,1414613837,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-peyhafaf5o5etsa2l5gh,task_subcomment,NA
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size",Verified the fix in test2,1414103035,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-peyhafaf5o5etsa2l5gh,task_subcomment,NA
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size","**gerritadmin** wrote:
+
+Change 167964 merged by jenkins-bot:
+Add 'valid' event to MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/167964",1413936281,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-peyhafaf5o5etsa2l5gh,task_subcomment,NA
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size","**gerritadmin** wrote:
+
+Change 167964 had a related patch set uploaded by Mooeypoo:
+Add 'valid' event to MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/167964",1413930065,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-peyhafaf5o5etsa2l5gh,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Steps to reproduce:
+
+1.  Open a page that already contains an external link without a label: [http://example.com].
+
+2.  Try to change that link to [http://example.com anything].  No fair removing the whole link and re-adding it.
+
+
+Results:
+
+Yeah, I couldn't figure out how to do that either.
+
+
+(According to the bug titles, bug 51309, bug 53505, and maybe some others address this, but the descriptions don't seem to match the titles very closely.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413492960,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-22uqtxwdglxq7a27zivv,task_description,resolved
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"**gerritadmin** wrote:
+
+Change 168030 merged by jenkins-bot:
+Open the linkNode inspector when pressing Ctrl+K on a link node
+
+https://gerrit.wikimedia.org/r/168030",1413947014,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"**gerritadmin** wrote:
+
+Change 168030 had a related patch set uploaded by Catrope:
+Open the linkNode inspector when pressing Ctrl+K on a link node
+
+https://gerrit.wikimedia.org/r/168030",1413946095,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Phatom87 says he's been using ""the tab that shows up after clicking on the link.""  He's running Mozilla browser version is 32.0.3 and kde Linux 4.14.1.",1413847030,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Aha, the trick is you're using the toolbar button (or keyboard shortcut) rather than the context menu item. 
+
+This is a regression. It's loading the link annotation editor rather than the link node editor. Clicking the context menu works just fine. Boo.",1413575134,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"(Also, works fine in both skins.)",1413559784,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"I tried this earlier and works for me in Chrome/Win8 and Safari on my Air. (6.2 isn't the most recent Safari version, but I don't think that matters). Can it be some kind of cache issue?",1413559671,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Steps to reproduce:
+
+1.  1.  Open a page that already contains an external link without a label: [http://example.com], such as   https://en.wikipedia.org/wiki/User:Whatamidoing_%28WMF%29/sandbox?veaction=edit (scroll down to the ==External links== section).
+
+2.  Open the link dialog.
+
+I get the 'wrong' dialog in both Safari 6.2 and Firefox 32 on en.wp, mw.org, and beta labs, so it's not just one version.  Perhaps it's Mac specific?  I've asked Phatom87 (Mozilla Firefox user) for browser and OS information.",1413559316,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"(In reply to WhatamIdoing from comment #4)
+> Not done.  There's no ""Add label"" button (see screenshot).
+
+How did you get the wrong link dialog to trigger? Link and reproduction steps please.",1413503822,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Not done.  There's no ""Add label"" button (see screenshot).",1413503759,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Created attachment 16793
+Screenshot of link dialog
+
+**Attached**: {F14724}",1413503736,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"1. Select link.
+2. Edit link.
+3. Click ""Add label"".
+
+Done?",1413500706,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Add label
+Change selection to select all except the last letter
+type : anything
+delete last letter
+
+not ...",1413495952,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","buggy link dialog
+
+Links don't correctly autocomplete when adding them from the references dialog and not the main editor (see screenshot; Chrome, en.wp today).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15331}",1413424800,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-r4igd57u7iobs63xxnge,task_description,open
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","Change 636522 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/extensions/VisualEditor@master] [WIP] ve.ui.MWMediaDialog: Use an overlay%%%
+Reason:
+%%%%%%
+https://gerrit.wikimedia.org/r/636522",1706727607,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","Change 636522 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] [WIP] ve.ui.MWMediaDialog: Use an overlay
+
+https://gerrit.wikimedia.org/r/636522",1603758933,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","This is still an issue today, although somehow it has changed back to clipping the inspector, like in the original report from 2014.
+{F32415818}",1603758035,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","This is still an issue, with the minor difference that the inspector is not clipped, but rather forces the dialog to have a scrollbar:
+
+{F12139380}
+
+It should look like this: (mockup)
+
+{F12139527}",1514605651,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small",">>! In T74121#3702775, @Elitre wrote:
+> Is this still relevant?
+
+The link dialogue is still contained inside the basic reference form, so this is still a valid report. I don't expect a great many people use the basic reference form, so I think the priority here can stay as it is.",1508750551,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small",Is this still relevant?,1508748075,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","I need to pick Trevor's brain about this. Right now the WindowManager for inspectors is in the localOverlay, which is a sibling of the ce-surface (and so is inside the iframe). It would be interesting to explore putting this in the globalOverlay, but then that would be nasty for scrollable surfaces (or even surfaces embedded in a scrollable container; like, for example, an iframe) where the anchor moves as you scroll: in a globalOverlay situation, we'd have to manually reposition the inspector to account for scrolling, but with the localOverlay as it is we get this for free.",1413942295,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","The links are autocompleting just fine, it's just that the dropdown is so small that you only see one suggestion, and the rest can be accessed by scrolling (notice the scrollbar).
+
+What we should really be doing though, is not clip the link inspector against the boundaries of the dialog it's in, but allow it to go beyond those boundaries. That's a bit fiddly but probably not very hard.",1413941873,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,"Screenshot of Zuul status
+
+A few hours ago the Zuul queue started to get stuck. A stack of three changes in mediawiki-extensions-DonationInterface was reviewed with CodeReview+3. The top one (commit C, depending on B, depending on A) had a merge conflict in it.
+
+C https://gerrit.wikimedia.org/r/#/c/166678/3
+B https://gerrit.wikimedia.org/r/#/c/166803/1
+A https://gerrit.wikimedia.org/r/#/c/166889/2
+
+Somehow this caused Zuul's gate-and-submit pipeline to get stuck indefinitely. Even changes from mwext-VisualEditor, mediawiki-core, mwext-MobileFrontend were all waiting.
+
+Debug information from Zuul's log
+
+-------
+
+```
+$ cat /var/log/zuul/zuul.log.2014-10-15 | grep '166678,3'
+2014-10-15 19:17:14,453 INFO zuul.Gerrit: Updating information for 166678,3
+2014-10-15 19:17:15,169 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline check-only>
+2014-10-15 19:17:15,169 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline check-voter>
+2014-10-15 19:17:15,170 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline test>
+2014-10-15 19:17:15,171 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes []
+2014-10-15 19:17:17,470 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes []
+2014-10-15 19:17:17,470 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0ff0590 166678,3> with dependent changes []
+2014-10-15 19:17:17,474 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0ff0590 166678,3> with dependent changes []
+2014-10-15 19:17:19,481 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes []
+2014-10-15 19:17:19,481 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0ff0590 166678,3> with dependent changes []
+2014-10-15 19:18:08,759 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f17b0ff0590 166678,3>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 2}>]
+2014-10-15 19:18:08,842 INFO zuul.Gerrit: Updating information for 166678,3
+2014-10-15 23:21:16,969 INFO zuul.Gerrit: Updating information for 166678,3
+2014-10-15 23:21:17,284 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline gate-and-submit>
+2014-10-15 23:21:17,284 INFO zuul.DependentPipelineManager: Reporting start, action [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 0}>] change <Change 0x7f17b0ff0590 166678,3>
+2014-10-15 23:21:17,359 INFO zuul.Gerrit: Updating information for 166678,3
+2014-10-15 23:21:17,362 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes [<Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:30,406 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,790 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,790 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,794 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,798 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:48:30,564 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:50:13,976 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:50:13,976 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,864 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,864 INFO zuul.Gearman: Launch job mwext-VisualEditor-qunit for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,868 INFO zuul.Gearman: Launch job mwext-VisualEditor-bundle-rubocop for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,876 INFO zuul.Gearman: Launch job mwext-VisualEditor-phpcs-HEAD for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,884 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,888 INFO zuul.Gearman: Launch job mwext-VisualEditor-npm for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,893 INFO zuul.Gearman: Launch job mwext-VisualEditor-lint for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,957 INFO zuul.Gearman: Launch job mwext-VisualEditor-doc-test for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:56,023 INFO zuul.Gearman: Launch job experiment-gating-dependencies for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+[00:45 UTC] zuul at gallium.wikimedia.org in /srv/org/wikimedia/integration ((no branch)%)
+```
+
+-------
+
+```
+$ cat /var/log/zuul/zuul.log.2014-10-15 | grep '166803,1'
+2014-10-15 19:38:32,047 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 19:38:32,382 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline check-only>
+2014-10-15 19:38:32,405 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline check-voter>
+2014-10-15 19:38:32,406 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline test>
+2014-10-15 19:38:32,407 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes []
+2014-10-15 19:38:34,115 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes []
+2014-10-15 19:38:34,115 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0f64c10 166803,1> with dependent changes []
+2014-10-15 19:38:34,119 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0f64c10 166803,1> with dependent changes []
+2014-10-15 19:38:35,718 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes []
+2014-10-15 19:38:35,718 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0f64c10 166803,1> with dependent changes []
+2014-10-15 19:38:48,199 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f17b0f64c10 166803,1>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 2}>]
+2014-10-15 19:38:48,273 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 19:40:23,214 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 19:40:23,668 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 23:47:29,998 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 23:47:30,326 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline gate-and-submit>
+2014-10-15 23:47:30,327 INFO zuul.DependentPipelineManager: Reporting start, action [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 0}>] change <Change 0x7f17b0f64c10 166803,1>
+2014-10-15 23:47:30,402 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 23:47:30,406 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,790 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,790 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,794 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,798 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:48:30,564 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:50:13,976 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:50:13,976 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Resetting builds for change <Change 0x7f17b0c3d250 166918,2> because the item ahead, <QueueItem 0x7f180b290c10 for <Change 0x7f17b13caed0 166889,2> in gate-and-submit>, is not the nearest non-failing item, <QueueItem 0x7f17b10042d0 for <Change 0x7f17b0f64c10 166803,1> in gate-and-submit>
+2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,864 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,864 INFO zuul.Gearman: Launch job mwext-VisualEditor-qunit for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,868 INFO zuul.Gearman: Launch job mwext-VisualEditor-bundle-rubocop for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,876 INFO zuul.Gearman: Launch job mwext-VisualEditor-phpcs-HEAD for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,884 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,888 INFO zuul.Gearman: Launch job mwext-VisualEditor-npm for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,893 INFO zuul.Gearman: Launch job mwext-VisualEditor-lint for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,957 INFO zuul.Gearman: Launch job mwext-VisualEditor-doc-test for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:56,023 INFO zuul.Gearman: Launch job experiment-gating-dependencies for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+```
+
+-------
+
+```
+$ cat /var/log/zuul/zuul.log.2014-10-15 | grep '166889,2'
+2014-10-15 22:33:35,953 INFO zuul.Gerrit: Updating information for 166889,2
+2014-10-15 22:33:36,261 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline check-only>
+2014-10-15 22:33:36,261 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline check-voter>
+2014-10-15 22:33:36,262 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline test>
+2014-10-15 22:33:36,263 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes []
+2014-10-15 22:33:39,803 INFO zuul.IndependentPipelineManager: Unable to merge change <Change 0x7f17b13caed0 166889,2>
+2014-10-15 22:33:39,803 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f17b13caed0 166889,2>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': -1}>]
+2014-10-15 22:33:39,876 INFO zuul.Gerrit: Updating information for 166889,2
+2014-10-15 23:48:30,171 INFO zuul.Gerrit: Updating information for 166889,2
+2014-10-15 23:48:30,484 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline gate-and-submit>
+2014-10-15 23:48:30,484 INFO zuul.DependentPipelineManager: Reporting start, action [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 0}>] change <Change 0x7f17b13caed0 166889,2>
+2014-10-15 23:48:30,559 INFO zuul.Gerrit: Updating information for 166889,2
+2014-10-15 23:48:30,564 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:48:31,761 INFO zuul.DependentPipelineManager: Unable to merge change <Change 0x7f17b13caed0 166889,2>
+2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Resetting builds for change <Change 0x7f17b0c3d250 166918,2> because the item ahead, <QueueItem 0x7f180b290c10 for <Change 0x7f17b13caed0 166889,2> in gate-and-submit>, is not the nearest non-failing item, <QueueItem 0x7f17b10042d0 for <Change 0x7f17b0f64c10 166803,1> in gate-and-submit>
+```
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://launchpad.net/bugs/1358517
+
+**Attached**: {F15298}",1413420420,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hlivvhccoogrytjztz4v,task_description,resolved
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,Patch got merged upstream.,1461058704,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,"The patch solved the issues of patches being stuck in the event queue whenever the connection is lost with the Gearman server. That happened yesterday on the Wikimedia setup, on reestablishing the connection, all the pending merger:merge function have been executed and the event queue processed everything :-)
+
+Keeping bug open until the patch is approved by upstream.",1414856489,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,The patch has been deployed. Lets monitor the issue for a few days.,1414703006,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,I am now deploying https://review.openstack.org/#/c/128921/3 by merging in our Zuul fork at integration/zuul.git,1414684508,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,I have proposed a change at https://review.openstack.org/#/c/128921/ with a test which most probably has a race condition :D,1413837673,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,"Turns out I already filled a bug upstream in August.  The case was the connection to Gearman timing out while preparing a reference (same code path): https://bugs.launchpad.net/zuul/+bug/1358517
+
+I have replied there with a potential solution to the issue.
+
+
+Marking bug as an upstream issue.",1413466078,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,"Looking at debug.log.2014-10-15
+
+
+23:21:17
+- receives a code review +2 event for change 166678,3
+- triggers a merge:merge function
+
+23:21:47 (30 seconds later):
+
+ ERROR gear.Client.unknown:
+   Connection <gear.Connection 0x1ca7f90 host: 208.80.154.135 port: 4730>
+   timed out waiting for a response to a submit job request:
+      <gear.Job 0x7f1809f1dd50
+          handle: None
+          name: merger:merge
+          unique: d928090c54474fa59b51d1661263750b>
+ NoConnectedServersError: No connected Gearman servers
+
+Zuul forks to spawn a Gearman server and both process communicate over TCP 4730 via the host public IP.
+
+The Zuul code that handles the creation of the reference (zuul.scheduler.BasePipelineManager.prepareRef() ) does not handle exceptions when submitting the job to Gearman, so it is raised up to the main loop and leave the enqueued change in an inconsistent state.
+
+
+I am not familiar with that part of the code.  I guess exceptions should be caught and some internal status (there is a `ready` variable) be set accordingly.
+
+
+To unblock such issue either:
+
+A) potentially a new patchset could be sent (that would remove the previous one from the Zuul queues) then +2ed again to reenter the gate-and-submit pipeline
+
+B) use the Zuul client to move the change ahead in the queue (an action known as 'promote') which would reorder the changes in the pipeline and retrigger merge jobs. Ie:
+
+ zuul promote --pipeline gate-and-submit --changes 166678,3
+
+See doc at http://ci.openstack.org/zuul/client.html#usage
+
+
+Adjusting priority, we can't have everything highest/critical.",1413464929,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+VisualEditor Mobile: The down-arrow is not appearing in against the cite menu's icon in Mobile VE,"Screenshot
+
+See the screenshot attached to see the position of the arrow
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15292}",1413419460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gx6gtxwaujgia6xrg3cb,task_description,resolved
+VisualEditor Mobile: The down-arrow is not appearing in against the cite menu's icon in Mobile VE,The icon was actually missing before; reversing the logic of this bug and marking it FIXED. :-),1413830564,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gx6gtxwaujgia6xrg3cb,task_subcomment,NA
+VisualEditor Mobile: The down-arrow is not appearing in against the cite menu's icon in Mobile VE,What's wrong about the position?,1413817191,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gx6gtxwaujgia6xrg3cb,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a group reference
+3.Now go to Insert>References list
+4.Click on the arrow to bring up the drop down box for the ""Use this group"" field
+
+
+Observe Result:
+The drop down box with options of group names are not opening unless you type something in the textfield
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15267}",1413412800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dr7acvvfxto6plbboi4q,task_description,resolved
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box",Verified the fix in production,1414100945,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box",Verified the fix in test2,1413504297,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box",Verified the fix in Betalabs,1413423082,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box","**gerritadmin** wrote:
+
+Change 166512 merged by jenkins-bot:
+TextInputMenuWidget: Handle undefined value properly when toggling visibility
+
+https://gerrit.wikimedia.org/r/166512",1413413173,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box","**gerritadmin** wrote:
+
+Change 166512 had a related patch set uploaded by Alex Monk:
+TextInputMenuWidget: Handle undefined value properly when toggling visibility
+
+https://gerrit.wikimedia.org/r/166512",1413412930,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the basic reference dialog
+3.Place the cursor inside the field ""Use the group""
+4.Type something or keep it empty while the drop down is open.
+5.Place cursor somehwhere else in the dialog to close it
+
+Observed Result:
+The drop down box does not get closed
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15265}",1413411180,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b2w334geyn6xehtamxqg,task_description,resolved
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Verified the fix in production,1414101205,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Verified the fix in test2,1413504179,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Verified the fix in Betalabs,1413423117,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Now fixed?,1413413104,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing","**gerritadmin** wrote:
+
+Change 166898 merged by jenkins-bot:
+Support MenuWidget's config.widget being in a different document
+
+https://gerrit.wikimedia.org/r/166898",1413412564,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing","**gerritadmin** wrote:
+
+Change 166898 had a related patch set uploaded by Catrope:
+Support MenuWidget's config.widget being in a different document
+
+https://gerrit.wikimedia.org/r/166898",1413412220,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Ugh yeah this is because it's in the outer overlay :(,1413411380,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor:  If I click on ""show all fields"" and add a parameter, then leave the list of all fields open so I can add another (and another and another)","This is from Salix alba, and I don't believe that I can improve upon his description:
+
+
+I wanted to add {{tl|Infobox musical artist}} to an article and it proved to be much more painful than it needs to be. 
+
+If you want add one of the minor fields like {{param|genre}} you have to
+#Click on '''Add more information'''
+#Click on '''Show 17 more fields'''
+#scroll down to find the field you want and click on it
+#The window will then scroll to the top of the form so you have to
+#scroll down again to find the field you want and fill in the value
+#repeat the whole process again.
+
+This could be made easier. Why do I need to click twice to show all fields? Why do I need to go back to square one after adding a field? Why does it not auto scroll to the correct place (actually why not simply show the field under it description in the list of fields).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69734",1413395280,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wfyoixdybjp6v6matvrj,task_description,open
+"VisualEditor:  If I click on ""show all fields"" and add a parameter, then leave the list of all fields open so I can add another (and another and another)","This task appears to be the closest to what we think might be a solution to this wishlist survey proposal: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Editing/Customised_infobox
+
+The #TemplateWizard design for template parameters is to always have the list visible in the dialog's sidebar. Perhaps something similar would be appropriate for VE?
+",1643335561,PHID-USER-hlhhe6qw6qfkl7wyfhxk,PHID-TASK-wfyoixdybjp6v6matvrj,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown","--------------------------
+**Version**: unspecified
+**Severity**: normal",1413386880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdtadfeyhzed33gkdvtq,task_description,resolved
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown","Change 166863 merged by jenkins-bot:
+Follow normalisation response from category status query
+
+[[https://gerrit.wikimedia.org/r/166863]]",1416967349,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown","Change 166863 had a related patch set uploaded (by Alex Monk):
+Follow normalisation response from category status query
+
+[[https://gerrit.wikimedia.org/r/166863]]
+
+#patch-for-review",1416958578,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown",*** Bug 72303 has been marked as a duplicate of this bug. ***,1413917443,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown","**gerritadmin** wrote:
+
+Change 166863 had a related patch set uploaded by Alex Monk:
+Follow normalisation response from category status query
+
+https://gerrit.wikimedia.org/r/166863",1413404106,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown",E.g. on https://www.mediawiki.org/wiki/VisualEditor - extra invisible characters at the end of each category name seems to be causing this,1413402055,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"VisualEditor: When auto-filling citations using citoid, don't add any empty parameters","See the empty author parameters in this:  https://en.wikipedia.org/w/index.php?diff=629488479&oldid=629487984
+
+Empty, non-required parameters would ideally not be added by Citoid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413235020,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-x35ncnimbtqjngphowun,task_description,resolved
+"VisualEditor: When auto-filling citations using citoid, don't add any empty parameters","There isn't any VE code using citoid yet, just a user script… however, assigning to Marielle.",1413915180,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-x35ncnimbtqjngphowun,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","screenshot
+
+Environment- test2, beta, production.
+
+1> Select template. In the Add a Template dialog when the cursor is in the input box, hit spacebar.
+2> The Add a Template button becomes active.click on it. 
+JS console error-“Uncaught Error: Unable to parse title”.
+
+Screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14999}",1413214140,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ptvgwefznutknxfidbsh,task_description,resolved
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template",Verified the fix in production along with the bug fix for 71249.,1416427523,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template",the fix is a part of 71249.,1415232901,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template",Fixed for validating template titles - verified in betalabs FF,1415133290,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","**gerritadmin** wrote:
+
+Change 170071 merged by jenkins-bot:
+Replacing MWTitleInputWidget.getValue() with MWTitleInputWidget.getTitle()
+
+https://gerrit.wikimedia.org/r/170071",1415063921,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","**gerritadmin** wrote:
+
+Change 170071 had a related patch set uploaded by SuchetaG:
+Replacing MWTitleInputWidget.getValue() with MWTitleInputWidget.getTitle()
+
+https://gerrit.wikimedia.org/r/170071",1415061379,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","(In reply to Gerrit Notification Bot from comment #3)
+> Change 168531 merged by jenkins-bot:
+> Add template button remains disabled when entering space as a template
+> 
+> https://gerrit.wikimedia.org/r/168531
+
+This fixes the issue as filed: when you type a space, the Add template button remains disabled. However, there are still a few values that you can use to make it crash, like ""Talk:"" (I was expecting ""|"" to break to, but surprisingly it doesn't because of unrelated evil hacks).
+
+That is part of a larger issue though, which I've filed as bug 72468.",1414114978,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","**gerritadmin** wrote:
+
+Change 168531 merged by jenkins-bot:
+Add template button remains disabled when entering space as a template
+
+https://gerrit.wikimedia.org/r/168531",1414114574,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","**gerritadmin** wrote:
+
+Change 168531 had a related patch set uploaded by SuchetaG:
+Add template button remains disabled when entering space as a template
+
+https://gerrit.wikimedia.org/r/168531",1414113846,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","Confirmed - test2, Betalabs, produciton(Chrome, FF)
+
+The following error is dispayed: 
+Uncaught Error: Unable to parse title VM5621:36
+TitleVM5621:36

+ve.dm.MWTemplateModel.newFromNameload.php?debug=false&lang=en&modules=ext.disambiguator.visualEditor%7Cext.math.visualEditor%7Cext.v…:257

+ve.ui.MWTemplatePlaceholderPage.onAddTemplateload.php?debug=false&lang=en&modules=ext.disambiguator.visualEditor%7Cext.math.visualEditor%7Cext.v…:277

+oo.EventEmitter.emitVM5625:7

+OO.ui.ButtonWidget.onClickload.php?debug=false&lang=en&modules=ext.visualEditor.core%2CviewPageTarget%7Cmediawiki.feedback%7C…:615

+jQuery.event.dispatchload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141017T2…:65

+elemData.handleload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141017T2…:60",1413842881,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: ""Categories"" dialog behaves differently for existing values and entered values","Screenshot of initial render with 1 category present
+
+When opening the dialog and one category is already on the page, that category is rendered on its own line and the input field has its own line too (full width).
+
+When removing that category and re-adding it, the input field shrinks and the category bubble is in front of it on the same line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14793}",1412973900,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x2js3cwk25pg7q5wraqv,task_description,resolved
+"VisualEditor: ""Categories"" dialog behaves differently for existing values and entered values",Can't reproduce. It works as expected now.,1420773172,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x2js3cwk25pg7q5wraqv,task_subcomment,NA
+"VisualEditor: ""Categories"" dialog behaves differently for existing values and entered values","Created attachment 16746
+Screenshot of later rendering when adding a category
+
+**Attached**: {F14794}",1412973930,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x2js3cwk25pg7q5wraqv,task_subcomment,NA
+First line in edit window is sometimes hidden in Safari,"Intermittent bugs are the worst.
+This is happening to me randomly in Safari 7.1: when I try to create a new page, what I type won't show up sometimes. It seems like the first line (or two) of the edit window is ""hidden"" under the edit toolbar. It just happened to me several times in a row on a page similar to https://meta.wikimedia.org/w/index.php?title=Talk:Tech/News/2014/39&action=edit&redlink=1 .
+It also happens on existing pages: I remember I had difficulties placing templates at the top of a page on Meta, so I just tried to edit https://meta.wikimedia.org/w/index.php?title=Talk:Community_Engagement_(Product)/Media_Viewer_consultation/Other&action=edit , and the first two lines are ""missing"". Nothing happens if I try to scroll up and down, with mouse or keyboard (except I can't see the cursor blinking if it is on one of those lines).
+
+--------------------------
+**Version**: 1.25-git
+**Severity**: normal
+**OS**: Mac OS X 10.9",1412932980,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hrzcgmgl37xcbzoguhtx,task_description,invalid
+First line in edit window is sometimes hidden in Safari,Haven't noticed this in a while.,1458573763,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hrzcgmgl37xcbzoguhtx,task_subcomment,NA
+First line in edit window is sometimes hidden in Safari,"Actually, I just had this again in Chrome, while trying to update https://meta.wikimedia.org/wiki/VisualEditor/Newsletter/Sandbox :(",1415385867,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hrzcgmgl37xcbzoguhtx,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE with Firefox
+2.Edit the page
+3.Save the page or just navigate to Readmode after discarding the edit
+
+
+Observed Result:
+Cursor appears in the last line of the page in readmode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71829
+
+**Attached**: {F15300}",1412806320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4zyamq2uzqay4psf2mpk,task_description,resolved
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Verified the fix in production,1415834858,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Verified the fix in test2,1415227620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Verified the fix in Betalabs,1415219458,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Change 144089 merged by jenkins-bot:
+Blur contentEditable node while destroying surface
+
+https://gerrit.wikimedia.org/r/144089",1415150050,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Still fixed, we're just moving it to a better place.",1415139852,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Change 144089 had a related patch set uploaded by Jforrester:
+Blur contentEditable node while destroying surface
+
+https://gerrit.wikimedia.org/r/144089",1415139296,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Change 169546 merged by jenkins-bot:
+Clear selection after tearing down surface to work around Firefox bug
+
+https://gerrit.wikimedia.org/r/169546",1414624899,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Change 169546 had a related patch set uploaded by Catrope:
+Clear selection after tearing down surface to work around Firefox bug
+
+https://gerrit.wikimedia.org/r/169546",1414520612,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","This issue is not fixed by the way, the cursor is still appearing the end of the document after saving a page in Firefox",1413831246,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Gah.,1413829922,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Different issue.,1413829912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",This now seems fixed from my testing?,1413819892,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+VisualEditor Mobile: Can't select an image node if the cursor is active?,"If you open the editor and click on an image it works fine (albeit alienated), but once you've dropped the cursor anywhere in the document, even in a slug, it doesn't seem possible to select the node any more?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412803320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3unnspcgavr6xhail2er,task_description,resolved
+VisualEditor Mobile: Can't select an image node if the cursor is active?,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488283,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3unnspcgavr6xhail2er,task_subcomment,NA
+VisualEditor: Copying text causes browser to scroll to the top of the page and move the cursor to the top in Safari,"Steps to reproduce:
+
+1.  Open a long page in Safari 6.2 (maybe others?)
+
+2.  Scroll down a ways and select some text.
+
+3.  Copy (Command-C) that text.
+
+
+Results:
+
+After a brief delay (one second?), the page scrolls all the way to the top.  The cursor is located at the very beginning of the page.  (The text is correctly copied.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**: {T74390}",1412650920,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-remttdefwzofqhhvwg2h,task_description,resolved
+VisualEditor: Copying text causes browser to scroll to the top of the page and move the cursor to the top in Safari,"Update:  As of July 2015, this is still happening in Safari 8.0 on Mac 10.10  
+
+However, instead of scrolling all the way to the top of the page, it scrolls until the selected/copied text is at the very bottom of the screen.",1437586008,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-remttdefwzofqhhvwg2h,task_subcomment,NA
+VisualEditor: Cannot enable or disable formatting of lines starting with semicolon markup,"If there is a line on a page that includes the semicolon syntax, VisualEditor does not handle this well. For example:
+
+<example>
+;Foo
+
+Some more text.
+</example>
+
+In VE, if I place the cursor either immediately before or immediately after the (bold-formatted) text ""Foo"", and then I add several new lines, I end up with multiple lines that include the semicolon formatting, such as:
+
+<example>
+;Bar
+;
+;Foo
+;Baz
+
+Some more text.
+</example>
+
+There is no way (that I can tell) to disable such formatting, and highlighting the (apparently) bold text and trying to select ""clear formatting"" has no effect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412634780,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-bh5fnqsfor56ucbo6du7,task_description,duplicate
+VisualEditor: Cannot enable or disable formatting of lines starting with semicolon markup,"In 'Edit source' - adding ; in front of a word makes a block displayed in bold in VE You cannot un-bold it in VE.
+
+<dl class=""ve-ce-branchNode""><dt class=""ve-ce-branchNode""><p class=""ve-ce-paragraphNode ve-ce-generated-wrapper ve-ce-branchNode"">Foo sjhajshjahssdsd</p></dt><dt class=""ve-ce-branchNode""><p class=""ve-ce-paragraphNode ve-ce-branchNode"">saksjdjskadja</p></dt></dl>
+
+dt {
+	.	
display: block;
+}
+
+dt {
+	.	
font-weight: bold;
+	.	
margin-bottom: .1em;
+}",1415137453,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-bh5fnqsfor56ucbo6du7,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],"Pages with a <link rel=""mw:PageProp/redirect"" href=""./Category:Foo""> but without a <link rel=""mw:WikiLink/Category"" href=""./Category:Foo""> should be serialised to [[:Category:Foo]] per the spec, but instead are becoming [[Category:Foo]] which (a) is wrong and (b) doesn't round-trip.
+
+----
+
+//Original VE complaint://
+
+The VE's Page Settings dialog redirect options work badly for category destinations.
+
+For example, if you choose 'Category:Article stubs' as your destination, it inserts this:
+
+#REDIRECT [[Category:Article stubs]]
+
+While this does redirect the page, it also places that page in the ""Article stubs"" category.
+
+It *should* put this on the page:
+
+#REDIRECT [[:Category:Article stubs]]
+
+Note the additional "":"" - this prevents the category being interpreted wrongly.
+
+https://www.mediawiki.org/w/index.php?title=VisualEditor:Redirecttest&action=history
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1412614020,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-2xatbyajrpglcczqz7gu,task_description,resolved
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],This change was deployed on March 19.,1426846636,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],">>! In T73708#1131553, @marcoil wrote:
+>>>! In T73708#1126551, @Krenair wrote:
+>> What about files?
+> 
+> What's the situation with files? Should they also be serialized with a ':'?
+
+Hmm... After doing some more checking, I think it may be OK without a ':' actually. Ignore me.",1426802989,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],"Change 197035 merged by jenkins-bot:
+T73708: Serialize category redirects with a ':'
+
+[[https://gerrit.wikimedia.org/r/197035]]",1426789820,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],">>! In T73708#1126551, @Krenair wrote:
+> What about files?
+
+What's the situation with files? Should they also be serialized with a ':'?",1426763987,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],What about files?,1426626267,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],"Change 197035 had a related patch set uploaded (by Marcoil):
+T73708: Serialize category redirects with a ':'
+
+[[https://gerrit.wikimedia.org/r/197035]]
+",1426511258,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],"I wonder if there is any use case for allowing the version without "":"" with these namespaces, even if it should clearly not be the default. I don't think we want to add an extra button for something so obscure to most users.",1421805384,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+VisualEditor: Annotation tools should be visibly disabled when selection is a formula node (which doesn't take annotations),"Screenshot
+
+Environment: test2, beta
+
+1> Insert a formula .
+2>highlight the formula and change its formatting to Bold/Italic/Underline/Strikethrough. None of these styles get applied to it.
+
+Now select Language, it opens the language inspector. Language should be disabled for formulas.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14907}",1412612100,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-btvs2s2ihxdsixm3lt3a,task_description,open
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,"Screenshot
+
+Environment- test2, beta, production
+
+1> insert a comment in a blank page.
+2> open the Edit comment box
+3> while the cursor is still blinking in the comment box, click to add numbered / Bullet point. The comment box closes and the comment is shown as the bullet/numbered list item
+4> Now open the edit comment box again and decrease the indentation.I get ""JS console error, Uncaught Error: Cannot set attributes on closing element"".See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14904}",1412607240,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-br5a45fin6czazh3islo,task_description,resolved
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,test2 - checked both scenarios - no js errors.,1416440312,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-br5a45fin6czazh3islo,task_subcomment,NA
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,"**gerritadmin** wrote:
+
+Change 173812 merged by jenkins-bot:
+Apply comment changes using fragment
+
+https://gerrit.wikimedia.org/r/173812",1416248160,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-br5a45fin6czazh3islo,task_subcomment,NA
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,"**gerritadmin** wrote:
+
+Change 173812 had a related patch set uploaded by Esanders:
+Apply comment changes using fragment
+
+https://gerrit.wikimedia.org/r/173812",1416232442,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-br5a45fin6czazh3islo,task_subcomment,NA
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,"This isn't as bad any more (no JS errors), probably thanks to Ed's change making the comment inspector use staging. But there's still a minor bug:
+
+* Insert a comment in a blank page
+* Type some text into the comment
+* While comment box is still open, click Bullet list
+* Comment inspector closes, comment ends up inside list
+* Inspect comment
+* Comment is empty (?!)
+* Close inspector. Comment is automatically removed because it is empty
+
+(If you don't type some text at step 2, the comment is removed at that point because it's empty.)
+
+(Marking as regression pre-wmf5 even though the behavior in wmf4 was much worse.)",1413943410,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-br5a45fin6czazh3islo,task_subcomment,NA
+VisualEditor: Links to Draft namespace show as red links in link inspector search,"Draft namespace articles incorrectly showing as red links in search
+
+Draft namespace articles incorrectly showing as red links in search
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14790}",1412502240,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-k2h6lp7jsa6s76ca2dx4,task_description,resolved
+VisualEditor: Links to Draft namespace show as red links in link inspector search,Verified in en.wiki - not reproducible.,1415654778,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-k2h6lp7jsa6s76ca2dx4,task_subcomment,NA
+VisualEditor: Links to Draft namespace show as red links in link inspector search,"Indeed, this was probably fixed when we modified MW's API return to always give the exact value.",1415031827,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k2h6lp7jsa6s76ca2dx4,task_subcomment,NA
+VisualEditor: Links to Draft namespace show as red links in link inspector search,Can't reproduce issue...,1414807703,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-k2h6lp7jsa6s76ca2dx4,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the Insert menu
+
+Observe that, the icon for Media and Comment are appearing a bit darker compared to other options in the menu.
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15228}",1412210640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a3rsqh3622rlfp4zpwul,task_description,resolved
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,Verified the fix in production,1414100982,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,checked in BetaLabs and test2.,1413585832,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,"Maths icon fixed in gerrit 167031, which will be in wmf5 but is relatively minor.",1413483556,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,"Created attachment 16785
+Screenshot
+
+**Attached**: {F15229}",1413423563,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,The opacity of Formula icon and Special Character did not get fixed with other icons.Is that intentional?,1413423512,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,Fixed with gerrit 166292 and gerrit 166293.,1413303144,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+"VisualEditor: Check locally for the user preference to prompt an edit summary, rather than waiting for the API to round-trip","Right now we rely on the API moaning about this, which means you have to wait for the whole page to be serialised, returned and saved before we prompt the user to do something that takes up some cycles, and so avoids them wasting time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412202840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ivp5hiloykrq3ijnlcsd,task_description,declined
+"VisualEditor: Check locally for the user preference to prompt an edit summary, rather than waiting for the API to round-trip","Never mind me, already done. *sighs*",1412289219,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ivp5hiloykrq3ijnlcsd,task_subcomment,NA
+"VisualEditor: Check locally for the user preference to prompt an edit summary, rather than waiting for the API to round-trip","You mean ""Prompt me when entering a blank edit summary""? I'm pretty sure we're handling that locally...",1412284901,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ivp5hiloykrq3ijnlcsd,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Now that it's been created, launching this should be scheduled…
+
+Release requirements from https://www.mediawiki.org/wiki/Beta_Features/Package :
+
+[x]    Make an extension - [[https://www.mediawiki.org/wiki/Extension:VectorBeta |Extension:VectorBeta]]
+[]    Get prelim design review
+[]    Get prelim security review
+[]    Get prelim performance review
+[]    Make sure there is a wiki page on mw.org for it that is understandable to the general public
+[]    Flowify the Talk page for the project
+[]    Make sure there is someone on point for feedback - a product manager (either volunteer or WMF staff)
+[]    Make a bugzilla component for the extension
+[]    Enable the Final Version of the code on Beta Cluster at least a week before you want to go for production.
+[]    Make gerrit change (do not merge) to the BF whitelist in mediawiki config
+[]    Deploy!
+",1412100840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ovf2mbalohzcr6eav5wb,task_description,declined
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Change 175406 abandoned by Glaisher:
+Enable ""Form Refresh"" as a BetaFeature
+
+Reason:
+Per task
+
+[[https://gerrit.wikimedia.org/r/175406]]",1432471511,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",We decided to do {T100161} instead.,1432471403,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1298356, @Mattflaschen wrote:
+> I hope we can discuss this at the Lyon Hackathon and make a commitment which approach we will take.  There are various possible resolutions:
+
+Filed as {T99827}.  Tentatively scheduled for Workplace 2, Sunday 14:00.",1432154427,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Change 211081 abandoned by Mattflaschen:
+Add margin about watchlist submit button, on MW UI
+
+Reason:
+So as to focus on the HTMLForm alternative.
+
+[[https://gerrit.wikimedia.org/r/211081]]",1432098001,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","I hope we can discuss this at the Lyon Hackathon and make a commitment which approach we will take.  There are various possible resolutions:
+
+1. Finish $wgUseMediaWikiUIEverywhere (see {T72913}, etc. for the progress that has already been made).  A beta feature is not required for this.
+2. Completely remove $wgUseMediaWikiUIEverywhere from core, leaving it as if it were false.
+3. If there is a commitment to actually convert all of core to OO UI PHP (unlike MW UI, AFAICT, OO UI PHP is available in core, but not used from core), we could consider leaving the status quo until that is done.  This only makes sense if there's actually a commitment to do this, which it doesn't sound like there is if matmarex is describing it as 'allegedly'.",1432097874,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","I hope we can discuss this at the Lyon Hackathon and make a commitment which approach we will take.  There are various possible resolutions:
+
+1. Finish $wgUseMediaWikiUIEverywhere (see {T72913}, etc. for the progress that has already been made).  A beta feature is not required for this.
+2. Roll back $wgUseMediaWikiUIEverywhere 100% in the meantime.
+3. If there is a commitment to actually convert all of core to OO UI PHP (unlike MW UI, AFAICT, OO UI PHP is available in core, but not used from core), we could consider leaving the status quo until that is done.  This only makes sense if there's actually a commitment to do this, which it doesn't sound like there is if matmarex is describing it as 'allegedly'.",1432097738,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","It should be pointed out that **these styles have been live on mobile since day one with no problem.** and have made various forms usable.
+
+I don't care how we implement these standard forms, whether it's oojs ui, mediawiki ui classes or some other library but we really should start validating our designs across all our forms and gauging reactions to changes in appearance. Bugs get fixed quicker when in front of people's eyes. The idea of the beta feature was to capture reactions to a new design, regardless of how made, and this feels like a wasted opportunity.
+
+In my opinion, this entire initiative stalled because we were given the impression that the forms would be rewritten in oojs ui and I had thought that would have happened by now. I'd love a roadmap for UX standardisation as it's been a year now on how we plan to get a standard UI across the site and from an outsiders perspective I don't see any improvement to the state of affairs since last year (apart from a much sexier VisualEditor and a tiny bit more infrastructure namely templates and icons).",1432033743,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Bah, I've been repeatedly advising against creating a BetaFeature for this, much less enabling it everywhere, until we've made it work correctly at least most of the time. Apparently it was done quietly while I wasn't looking. I've been told that this will help us spot and fix issues, but I remember reporting the same issue with radio buttons myself a year ago and I see it's still there? Sad to see that all the effort goes into enabling new features and none into polishing them.
+
+We should mark this as ""Declined"" and focus our effort on something useful that people want to work on, since clearly no one wants to work on this.
+
+The blockers for this would probably amount to a few weeks of work, and it is all redundant anyway since we are allegedly moving from ""MediaWiki UI"" to ""OOjs UI MediaWiki theme"". The designs of the two have been rapidly diverging; if the aim is supposed to unify our interfaces, this must not be deployed.",1431793770,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1287139, @Mattflaschen wrote:
+>>>! In T73477#1266924, @greg wrote:
+>> Removed Jared from assignee; who is driving this now? Let's not push something out as a beta feature that doesn't have someone to care for it.
+> 
+> @greg, there is technical debt in core for this (wgUseMediaWikiUIEverywhere).  We really need to resolve this one way or the other.  
+> 
+> This is not a 'feature' we want to maintain separately on an ongoing basis the way VE or Flow is.  It is part of core, and the code forks need to be removed.  Then, it needs to be maintained by the UX team and in general engineers leveraging it (same as any core component).
+> 
+> Using a Beta Feature temporarily is one possible path, but not the only one.  We could also just do it directly (T72424), after sufficient testing.
+> 
+
+I have no idea what will come of the BetaFeatures project/process post Jared, but there were (presumably still are) very stringent rules on what can go out as a BF. Without a PM owning it, it doesn't go out (as a BF). Really, for any big UI refresh like this, I want a PM to own it to respond to feedback and drive it to a successful conclusion. Who will be doing that for this?
+",1431704588,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","> The goal should be for the new version to be a productive interface.
+
+If the positioning of radio selects and checkboxes seemingly becomes inverted from the original, with no apparent reasoning behind it, then I call that a problem, not a productive interface.
+
+Examples of these are everywhere:
+{F165110}",1431699888,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","I'm with @Quiddity. What causes all the control to be misplaced? If checkboxes are placed on one line, I expect them to be on one line. The controls should behave as standard UI controls with regards to being placed inline or as block elements.",1431679757,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1287132, @Quiddity wrote:
+> The radiobuttons should be on individual lines here (and in TheDJ's second image above)
+> {F165030}
+> But vice-versa for the checkboxes (and the submit button) here (they should be on the same line)
+> {F165033}
+
+It seems like you want them on the same line or not just because they were in the original version. That's not the goal here.  The goal should be for the new version to be a productive interface.",1431670164,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1266924, @greg wrote:
+> Removed Jared from assignee; who is driving this now? Let's not push something out as a beta feature that doesn't have someone to care for it.
+
+@greg, there is technical debt in core for this (wgUseMediaWikiUIEverywhere).  We really need to resolve this one way or the other.  
+
+This is not a 'feature' we want to maintain separately on an ongoing basis the way VE or Flow is.  It is part of core, and the code forks need to be removed.  Then, it needs to be maintained by the UX team and in general engineers leveraging it (same as any core component).
+
+Using a Beta Feature temporarily is one possible path, but not the only one.  We could also just do it directly (T72424), after sufficient testing.
+
+>>! In T73477#1280648, @Quiddity wrote:
+> Beyond the design problems (examples above, plus more: [[http://i.imgur.com/Algh0Se.png| eg1]], [[http://i.imgur.com/FDYzdgX.png |eg2]]), 
+> this probably also needs to be QA-checked for functionality.
+
+What exactly are you saying is wrong with the first one?  Do you want them all on one line?
+
+For the second, I guess you're referring to the button wrongly touching 'Associated namespace'.  Fixed in https://gerrit.wikimedia.org/r/#/c/211081/ ; please review.
+
+Please file bugs (you don't need to for the one I already fixed), so we can triage them and decide what's a blocker.",1431670027,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","The radiobuttons should be on individual lines here (and in TheDJ's second image above)
+{F165030}
+But vice-versa for the checkboxes (and the submit button) here (they should be on the same line)
+{F165033}
+",1431669688,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Change 211081 had a related patch set uploaded (by Mattflaschen):
+Add margin about watchlist submit button, on MW UI
+
+[[https://gerrit.wikimedia.org/r/211081]]
+",1431669626,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1241123, @TheDJ wrote:
+> {F158088}
+> {F158090}
+> Not sure if people will be too exited when stuff looks like this....
+
+I guess for the first you're referring to the slightly awkward spacing?  This is not a blocker to the Beta Feature in my opinion.  It's something we can refine at any time.
+
+For the second, I don't see anything wrong at all.  Do you just not like the style?",1431668160,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Beyond the design problems (examples above, plus more: [[http://i.imgur.com/Algh0Se.png| eg1]], [[http://i.imgur.com/FDYzdgX.png |eg2]]), 
+this probably also needs to be QA-checked for functionality.
+
+I just discovered this Bug: {T98905}
+",1431460039,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",Removed Jared from assignee; who is driving this now? Let's not push something out as a beta feature that doesn't have someone to care for it.,1430948340,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","{F158088}
+{F158090}
+Not sure if people will be too exited when stuff looks like this....",1430215982,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","{F158088}
+
+Not sure if people will be too exited when stuff looks like this....",1430215922,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",This is now available on the beta cluster. http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences#mw-prefsection-betafeatures,1429950264,PHID-USER-lsveyqlsb4acoowxr5yj,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",,1429442434,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",,1429442393,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","As I mentioned on [[ https://gerrit.wikimedia.org/r/#/c/175406/ | gerrit ]], the changes that were needed in mw.ui have been made. But, I am not sure how other parts of the work is progressing. 
+
+@jdlrobson might know more.
+
+***
+//oops, made the same comment twice//",1429442492,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","As I mentioned on [[ https://gerrit.wikimedia.org/r/#/c/175406/ | gerrit ]], the changes that were needed in mw.ui have been made. But, I am not sure how other parts of the work is progressing. 
+
+@jdlrobson might know more.",1429442377,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1198457, @greg wrote:
+> What's the plan/timeline, yo?
+
+ETA please.",1429284925,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","What's the plan/timeline, yo?",1428686518,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Tagged assuming that this might go ahead, but I have no special knowledge of it. :-)",1428680638,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",https://gerrit.wikimedia.org/r/#/c/175406/,1416823928,PHID-USER-lsveyqlsb4acoowxr5yj,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","screenshot 1
+
+Environment- test2, beta
+
+1> In VE, go to Options  -> Categories. And add two categories.
+2> Now delete the categories.Click on “Cancel” to close the  options dialog.
+3> Error in console, “Uncaught TypeError: Cannot read property 'disconnect' of undefined”(see screenshot 1)
+
+After this step, reopen the Options dialog , notice the first Category is repeated( see screenshot 2).
+
+Trying to delete any of the categories throws errors in console “Uncaught Error: Cannot remove detached item” and “Uncaught TypeError: Cannot read property 'metaItem' of undefined”.Clicking on Cancel or Apply changes does not close the dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F15029}",1412092140,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-sdgsqmliomodrzl3kegc,task_description,resolved
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”",Verified the fix in production,1412885547,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”",Verified the fix in production,1412885539,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”",Issue is now fixed in beta too.,1412609817,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”",Verified the fix in test2,1412362082,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Change 164018 merged by Catrope:
+Account for categories being removed twice in MWCategoryWidget
+
+https://gerrit.wikimedia.org/r/164018",1412203342,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Change 164018 had a related patch set uploaded by Jforrester:
+Account for categories being removed twice in MWCategoryWidget
+
+https://gerrit.wikimedia.org/r/164018",1412127002,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Change 163887 merged by jenkins-bot:
+Account for categories being removed twice in MWCategoryWidget
+
+https://gerrit.wikimedia.org/r/163887",1412115034,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Change 163887 had a related patch set uploaded by Catrope:
+Account for categories being removed twice in MWCategoryWidget
+
+https://gerrit.wikimedia.org/r/163887",1412100892,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Created attachment 16634
+screenshot 2
+
+**Attached**: {F15030}",1412092199,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken if the link target suggestion dropdown overlaps with the border of the page,"video capture of the bug
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a link some where towards the end of the current viewport so that when you open the link inspector the link target suggestions overlap with the border of the page
+3.After inserting the link, reopen the link inspector and place cursor inside to bring up the link target suggestion 
+4.When the link target suggestion dropdown appears, scroll up the page 
+
+Observed Result: 
+The UI for the link inspector is open. 
+
+See the video capture attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14747}",1411769040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x4n4ij754asqbc6h7jmx,task_description,resolved
+VisualEditor: Link inspector UI gets broken if the link target suggestion dropdown overlaps with the border of the page,Verified the fix in production,1412885750,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x4n4ij754asqbc6h7jmx,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken if the link target suggestion dropdown overlaps with the border of the page,Verified the fix in test2,1412367951,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x4n4ij754asqbc6h7jmx,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken if the link target suggestion dropdown overlaps with the border of the page,This is fixed by https://gerrit.wikimedia.org/r/#/c/163228/ and https://gerrit.wikimedia.org/r/#/c/163280/ as a side effect of fixing bug 52526,1411778730,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-x4n4ij754asqbc6h7jmx,task_subcomment,NA
+VisualEditor: Inserting a comment before the last word in a Language (RTL direction)Text moves the word to the start of the line.,"Environment-test2, beta
+
+1> Insert Language in RTL direction.
+2>insert a comment in the language text, right before the last word. Notice the word moves to the start of line.See screencast.
+3>Now place the cursor at the end of the last char in the langauge text and press backspace to delete.
+
+This also happens while inserting a citation or a formula.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP",1411668480,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ckia45kqd4ianv3wg3rp,task_description,open
+VisualEditor: Inserting a comment before the last word in a Language (RTL direction)Text moves the word to the start of the line.,Confirmed in test2 and Betalabs in Chrome.,1413834930,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ckia45kqd4ianv3wg3rp,task_subcomment,NA
+VisualEditor: Inserting a comment before the last word in a Language (RTL direction)Text moves the word to the start of the line.,http://youtu.be/6vtjey9UcCU,1411668687,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ckia45kqd4ianv3wg3rp,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2469/console
+
+https://integration.wikimedia.org/ci/job/VisualEditor-npm/3226/console
+
+Etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1411664160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_description,resolved
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"I've purged the .npm cache. The coffee-scripts dependency seems to have been a result of cache corruption.
+
+https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2489/console
+
+Passing now on integration-slave1006.",1411757722,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"Seems to be an entirely different issue:
+
+00:00:03.045 [mediawiki-core-npm] $ /bin/bash -xe /tmp/hudson6526668683101242560.sh
+00:00:03.051 + cd /mnt/jenkins-workspace/workspace/mediawiki-core-npm/src/tests/frontend
+00:00:03.052 + npm --version
+00:00:03.346 1.3.10
+00:00:03.351 + npm install
+00:00:03.850 npm WARN package.json mediawiki@0.0.0 No description
+00:00:03.851 npm WARN package.json mediawiki@0.0.0 No repository field.
+00:00:03.852 npm WARN package.json mediawiki@0.0.0 No README data
+00:00:03.910 + npm test
+00:00:04.290 
+00:00:04.290 > mediawiki@0.0.0 test /mnt/jenkins-workspace/workspace/mediawiki-core-npm/src/tests/frontend
+00:00:04.290 > grunt test
+00:00:04.291 
+00:00:04.390 
+00:00:04.390 module.js:340
+00:00:04.390     throw err;
+00:00:04.391           ^
+00:00:04.392 Error: Cannot find module 'coffee-script'
+
+I have took a snapshot of the workspace on integration-slave1006 in /home/hashar/bug71314/ and the issue is reproduced.
+
+Looking at the dependencies:
+
+$ npm list
+mediawiki@0.0.0 /home/hashar/bug71314/src/tests/frontend
+├─┬ grunt@0.4.2
+│ ├── UNMET DEPENDENCY async ~0.1.22
+│ ├── UNMET DEPENDENCY coffee-script ~1.3.3
+│ ├── UNMET DEPENDENCY colors ~0.6.2
+...
+
+$ ls -1 node_modules/
+grunt/
+grunt-banana-checker/
+grunt-contrib-jshint/
+grunt-contrib-watch/
+grunt-jscs/
+grunt-jsonlint/
+$
+
+There are no 'node_modules' subdirectories below.
+
+So somehow npm install does not install the dependencies :-/  Maybe it considers them as already installed because they are in the ~/.npm cache ?  I gave it a try by deleting my /home/hashar/.npm and running `npm install`.  That managed to pull all the needed dependencies and npm test is runnable.
+
+I then deleted the node_modules sub directory and ran npm install again.  It installed the dependencies properly.
+
+
+Maybe it is a cache corruption and we should delete the /mnt/home/jenkins-deploy/.npm/ directory?",1411745654,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"This is still broken today, but in a different way now.
+
+https://gerrit.wikimedia.org/r/#/c/163168/
+https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2484/console",1411743480,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"**gerritadmin** wrote:
+
+Change 163119 merged by jenkins-bot:
+Migrate mediawiki-core-npm to Zuul cloner
+
+https://gerrit.wikimedia.org/r/163119",1411718546,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,Fixed by migrating the job to Zuul cloner which does not fetch submodules.,1411718306,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"**gerritadmin** wrote:
+
+Change 163119 had a related patch set uploaded by Hashar:
+Migrate mediawiki-core-npm to Zuul cloner
+
+https://gerrit.wikimedia.org/r/163119",1411717761,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"Timo wrote:
+
+> Hi Antoine,
+> 
+> https://integration.wikimedia.org/ci/job/mediawiki-core-npm/
+> 
+> As of build 2463[1], it's broken with some git error (there seems to be
+> a stray extension directory even though it's against master).
+> The previous build 2462[2] passed fine.
+> 
+> FYI: This is not related to switching to Ubuntu Trusty, since the jobs
+> before that were working fine and also on Trusty.
+> 
+> — Timo
+> 
+> 
+> [1] https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2463/console
+> [2] https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2462/console
+
+
+I noticed it attempt to submodule update and fails on AbuseFilter which
+is the first submodule in core wmf branches.
+
+My assumption is that a job previously ran for a wmf branch which has
+submodule which were initialized.  Then a job against master is created,
+the Jenkins git plugin clean the repo but does not uninitialise
+submodules though they are not existant, so it bails out.
+
+That is probably a behaviour change in git (Precise has 1.7.9.x while
+Trusty has 1.9.1).
+
+
+I would recommend to revert the npm jobs back to Precise nodes. Will
+look at migrating the job from the evil Jenkins git plugin to the Zuul
+cloner.
+
+
+Do NOT upgrade the Jenkins git plugin.  It is terribly bugged and would
+kill everything (I tried on labs, does not work :-D).",1411716729,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,I depooled integration-slave1006.eqiad.wmflabs and a rebuild of the last failed mediawiki-core-npm job succeeded: https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2471/,1411664961,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+"VisualEditor Mobile: After tapping on ""Go back""/""Continue Anyway"" in the ""Required parameter missing"" confirmation dialog in iOS Safari, it flickers at the top of the screen","Steps to reproduce:
+
+1.Open a page with mobile VE in iOS Safari
+2.Open Cite>Website
+3.Keep one of the required parameters empty and click on Insert
+4.When the confirmation dialog for required parameter being missing shows up, click on Go back or Continue anyway.
+
+
+Observed Result:
+Observe that, the animation of the confirmation dialog appearing and disappearing is not same as how it is in desktop safari.Also, when closing the dialog, by tapping on ""Go back""/""Continue Anyway"", instead of sliding up it flickers at the top of the screen.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1411599540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jetfcrjzmljadekjnwqj,task_description,resolved
+"VisualEditor Mobile: After tapping on ""Go back""/""Continue Anyway"" in the ""Required parameter missing"" confirmation dialog in iOS Safari, it flickers at the top of the screen","Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488277,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jetfcrjzmljadekjnwqj,task_subcomment,NA
+VisualEditor: Pasting in image caption with a repeated reference causes VE to crash,"I found this bug while trying to swap the captions of two images, but it can be duplicated with just one image:
+
+1. Paste this into a page and save:
+
+Example text<ref name=Ref1>Ref 1</ref>
+[[File:Example.jpg|thumb|Example text.<ref name=Ref1/>]]
+
+2. Launch VE
+3. Click the image and open the Media settings dialogue
+4. Select all the caption text (Ctrl-A) and cut it out (Ctrl-X)
+5. Apply changes
+6. Reopen the Media settings dialogue
+7. Paste the caption text back in (Ctrl-V)
+8. Apply changes
+
+VE will now hang on the Media settings dialogue.  The dialogue will not complete and will not cancel.  It is completely impossible to carry on editing, all the changes up to that point have to be discarded.
+
+I am using FF32, Windows 7, Monobooks
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1411520940,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-3itlwc5mvcohetlwjnl4,task_description,open
+VisualEditor: Pasting in image caption with a repeated reference causes VE to crash,"Since T259038 is resolved I now get a different error:
+```
+ve.ce.MWReferencesListNode.js:245 Uncaught TypeError: Cannot read properties of undefined (reading 'getAttribute')
+    at VeCeMWReferencesListNode.eval (ve.ce.MWReferencesListNode.js:245:58)
+    at Array.forEach (<anonymous>)
+    at ve.ce.MWReferencesListNode.update (ve.ce.MWReferencesListNode.js:226:20)
+    at later (oojs-ui-core.js:251:11)
+```",1714649234,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3itlwc5mvcohetlwjnl4,task_subcomment,NA
+VisualEditor: Pasting in image caption with a repeated reference causes VE to crash,"> VE will now hang on the Media settings dialogue. The dialogue will not complete and will not cancel. It is completely impossible to carry on editing, all the changes up to that point have to be discarded.
+
+It seems like it no longer hangs this way now, although the steps still result in an exception (""TypeError: group.firstNodes[index2] is undefined"" – same one as T259038) and mess up some internal state, which causes further exceptions whenever you do basically anything (although I'm not sure what's the impact on the users, I was still able to make changes and save the page despite them).",1692565153,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3itlwc5mvcohetlwjnl4,task_subcomment,NA
+VisualEditor: Pasting in image caption with a repeated reference causes VE to crash,See also bug 60919?,1414883335,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3itlwc5mvcohetlwjnl4,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert the template ""Citation needed""
+3.Observe that in the field for ""Month and year"", the following has been used:
+{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}
+4.Now click on ""Apply Changes""
+5.Save the page
+6.Reopen the page
+7.Open the transclusion dialog for the ""Citation Needed"" template
+
+Observed Result:
+The current month name and current year value did not get added in the field.
+
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14868}",1411432560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ljyxu64angwfdp5jfokm,task_description,resolved
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"(In reply to Rummana Yasmeen from comment #7)
+> This seem to be not working in production (en.wiki).I dont even see the
+> substitute values {{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}} for the
+> parameters.
+
+This seems to be because the Citation needed template on enwiki doesn't have the autovalue set up yet. James said he would do this, but he was waiting for this bug to be fixed.",1414627219,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,This seem to be not working in production (en.wiki).I dont even see the substitute values {{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}} for the parameters.,1414623851,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,Verified in betalabs.,1414437118,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Change 168205 merged by jenkins-bot:
+Apply pre-save transform to template previews
+
+https://gerrit.wikimedia.org/r/168205",1414435124,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Change 168204 merged by jenkins-bot:
+Actually set parameter autoValues as values
+
+https://gerrit.wikimedia.org/r/168204",1414018433,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Change 168205 had a related patch set uploaded by Catrope:
+Apply pre-save transform to template previews
+
+https://gerrit.wikimedia.org/r/168205",1414018101,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Change 168204 had a related patch set uploaded by Catrope:
+Actually set parameter autoValues as values
+
+https://gerrit.wikimedia.org/r/168204",1414018095,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,Definitely VE's fault. We're somehow not sending the parameter value to Parsoid when saving.,1414014943,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert a bullet list or numbered list
+3.Now try to add indentation to one of the item
+
+Observed Result:
+Apart from adding indentation, it ia also adding a new line and a new bullet point/numbered point
+
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14804}",1411416780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3jv4morfdfduiqmadob2,task_description,declined
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"(In reply to Ed Sanders from comment #8)
+> Recommend wontfix. There's no regular case to start a list at double
+> indentation. This change doesn't event prevent that, just makes it visually
+> clear what structure you should use.
+
+Very well.",1416243978,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"Recommend wontfix. There's no regular case to start a list at double indentation. This change doesn't event prevent that, just makes it visually clear what structure you should use.",1416237513,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"(In reply to Mark A. Hershberger from comment #6)
+> This is probably part related to Bug #37938, Bug #48010, and Bug #58335.
+
+No, this has nothing to do with those bugs; it's about the visual display of empty structural list items.",1415878385,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"This is probably part related to Bug #37938, Bug #48010, and Bug #58335.",1415815182,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"(In reply to Ed Sanders from comment #4)
+> I think it makes sense to have a slug there, as a double indented list is
+> actually a list wrapped in a list, so you need to be able to split them and
+> insert content.
+> 
+> Also you shouldn't double indent a list without content between, so this
+> make it clear something is being done wrongly.
+
+Sure, except you were the one to change the behaviour to this a few months ago, to match read mode rendering…",1411685967,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"I think it makes sense to have a slug there, as a double indented list is actually a list wrapped in a list, so you need to be able to split them and insert content.
+
+Also you shouldn't double indent a list without content between, so this make it clear something is being done wrongly.",1411678095,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"Created attachment 16592
+Screenshot in wmf22
+
+Okay, so if I compare the behavior of indentation in wmf 22 , it didnt add any slug when I increase indentation for any bullet list.It just added indentation for that bullet point moving it to the right.But now it is adding a slug ,See the screenshot attached for wmf 22 to compare how it used to work.
+
+**Attached**: {F14805}",1411671595,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,Can you give more detailed instructions. I'm seeing slugs in lists but only in sensible places.,1411660611,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"Due to the changes in how slugs work, presumably?",1411417528,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"**Author:** `d_iarnov`
+
+**Description:**
+win 8.1  сенсорный .вообще нереально написать нажимая backspace  чтоб стереть  ошибочно написанное страницу подбрасывает вверх. и на этом точка. дальше работать соответственно не возможно. мало того в плиточном браузере вообще говорится что он не поддерживается. все браузеры у меня IE
+
+**See Also**: {T73561}
+
+---
+Alternative steps to reproduce (in English, from T89196):
+
+1. Edit [[Nausea]] in VE: https://en.wikipedia.org/wiki/Nausea?veaction=edit
+2. Scroll down to the ""Medications"" section
+3. Click in the middle of a sentence and hit ""backspace"" a few times.
+
+Each time you do this, the page jumps, and the sentence in which the cursor is located always ends up at the very bottom of the viewport.
+
+4. Press ""delete"" key a few times
+
+Same behaviour.
+
+5. Now click in the middle of the very long paragraph under ""Diagnostic approach"". Hit ""backspace"" a few times.
+
+Once again, the page jumps, but now it is worse, because the page lands with the cursor offscreen.",1411392420,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_description,resolved
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Thank you, @matmarex  ",1549986756,PHID-USER-nbq4yci7flcs7evltagr,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"@Fulla07 That looks like a different, new issue. I filed a separate task with more details: T215914",1549985189,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,This bug still appears on the english wikipedia.,1549975394,PHID-USER-nbq4yci7flcs7evltagr,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"This task is about VisualEditor. It sounds like you are talking about the mobile source editor, so please file a new task.",1487404429,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"On android, mobile view, editing any wikimedia page, using backspace or cut for deleting text, makes the screen scroll up to almost top of page. For example, I try to edit https://en.m.wikipedia.org/wiki/Ringwoodite top paragraph, backspace to delete the dot on the end scrolls me back to | class... in the infobox.",1487401622,PHID-USER-igzxxrouiten65uus2an,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Change 207875 merged by jenkins-bot:
+ui.ListAction: Fix screen jumping in Internet Explorer
+
+[[https://gerrit.wikimedia.org/r/207875]]",1430567035,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Change 207875 had a related patch set uploaded (by MarkAHershberger):
+Fix screen jumping
+
+[[https://gerrit.wikimedia.org/r/207875]]
+",1430418926,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Probably not. We keep all existing documentation public, in source code or on mediawiki.org.",1419810803,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"I'd like to get a better understanding of how to troubleshoot and extend VE and this issue has been marked as very important by a client.
+
+I've poked at similar bugs, but I'm not sure how they relate to this one and their solutions confuse me.  Is there anywhere I can look for more information on tracking it down?",1419810716,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,*** Bug 72646 has been marked as a duplicate of this bug. ***,1414530966,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"For me it scrolled abruptly almost to the top of the page (but not quite) and stayed there when I continued backspacing. I was testing on https://pl.wikipedia.org/wiki/Fotografia_cyfrowa (random page), for the record.",1412369925,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,Added possibly-related bug 71561?,1412369709,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Testing VE (both mobile and desktop) on a tablet (not phone) with both
+Windows 7 and 8.1, backspacing (both using software or hardware keyboards) works, but causes the page to abruptly scroll up. Just typing text doesn't cause this behavior. I'm going to assume that this was the original issue that was meant to be reported here :)",1412369526,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Marking as ""Low"" priority until more details are provided.",1412359019,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Thanks for taking the time to report this!
+
+Am I correct that this is about Windows 8.1 phone?
+Could you provide exact steps to reproduce (step by step) in English what exactly is broken with backspace, and where exactly this happens (web address)?
+
+Please also see https://www.mediawiki.org/wiki/How_to_report_a_bug because ""doesn't work"" isn't a good bug summary. :)",1411396196,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image with caption
+3.Reopen the media settings dialog 
+4.Now apply link to the existing caption
+
+Observed Result:
+The ""Apply changes"" button does not become enabled after applying link unless user make some other change for that image
+
+Environment: Betalabs, Test2 and Production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411156560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6x3yrgo5cawaeou4wbls,task_description,resolved
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button",">>! In T73065#959930, @Whatamidoing-WMF wrote:
+> No, this is still broken.  I could reproduce this problem at mediawiki.org this morning.
+
+Re-broken in T8… something.",1420648664,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6x3yrgo5cawaeou4wbls,task_subcomment,NA
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button","No, this is still broken.  I could reproduce this problem at mediawiki.org this morning.",1420648629,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6x3yrgo5cawaeou4wbls,task_subcomment,NA
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button",This apparently is long-ish-fixed?,1420597574,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6x3yrgo5cawaeou4wbls,task_subcomment,NA
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button",This was also reported in Mac OS X 10.9.5 in both Firefox and Safari.,1414085906,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6x3yrgo5cawaeou4wbls,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","**Author:** `physik`
+
+**Description:**
+On a fresh vagrant box with the role math enabled I get the following error message while trying to run the browser tests for math
+
+ unable to obtain stable firefox connection in 60 seconds (127.0.0.1:7055) (Selenium::WebDriver::Error::WebDriverError)
+  /srv/vagrant/mediawiki/extensions/Math/tests/browser/.gem/ruby/2.0.0 /gems/selenium-webdriver-2.42.0/lib/selenium/webdriver/firefox
+see
+ https://gist.github.com/physikerwelt/8a9ff6b292609449a2df
+
+I was doing nothing else beside running
+ bundle exec cucumber features/math.feature
+
+I checked my environment variables
+MW_INSTALL_PATH=/vagrant/mediawiki
+MEDIAWIKI_API_URL=http://127.0.0.1/w/api.php
+MEDIAWIKI_USER=Selenium_user
+MEDIAWIKI_PASSWORD=vagrant
+INSTANCEPROJECT=math
+COMPOSER_CACHE_DIR=/vagrant/cache/composer
+MEDIAWIKI_URL=http://127.0.0.1:8080/wiki/
+
+but could not detect any problems there
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411049880,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_description,resolved
+"running browser tests ""unable to obtain stable firefox connection""","**physik** wrote:
+
+Technically you are right.
+I added a section to 
+https://www.mediawiki.org/wiki/Quality_Assurance/Browser_testing/Running_tests#Running_VisualEditor_browser_tests_via_labs-vagrant",1411070693,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","X isn't required as headless mode runs Firefox through xvfb. Use of phantomjs (note the ""js"") as the browser is inherently headless so you don't need to specify the HEADLESS env var.
+
+You can also try using X forwarding but it's a little trickier since your labs instance may not allow it. You can inquire on #wikimedia-labs or #wikimedia-qa IRC channels about getting that setup.
+
+This bug is technically resolved if you're not seeing the firefox connection error. Your feature looks to be executing correctly, and the scenario is either failing positively or falsely. You'll have to jump into the browser session to find our more. Jump on the #wikimedia-qa channel or email the QA list for help! [1]
+
+[1] https://lists.wikimedia.org/mailman/listinfo/qa",1411069276,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","**physik** wrote:
+
+Thanks. This changes the problem
+And I am at page that does not exist           # features/step_definitions/math_steps.rb:13
+    And I click link Create source                 # features/step_definitions/math_steps.rb:17
+      timed out after 5 seconds, waiting for {:text=>""Create source"", :tag_name=>""a""} to become present (Watir::Wait::TimeoutError)
+      ./features/step_definitions/math_steps.rb:18:in `/^I click link Create source$/'
+      features/math.feature:18:in `And I click link Create source'
+    When I type <math>3 + 2</math>                 # features/step_definitions/math_steps.rb:25
+
+I did not setup an x environment. Is that required?
+I tried to set my environment variable BROWSER=phantom but this did not help either.",1411068061,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","Those error messages from Firefox don't necessarily indicate failure. I would kill the firefox processes and try again, running in headless mode first to rule out X-forwarding issues.
+
+HEADLESS=true bundle exec cucumber ...",1411067002,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","Those error messages from Firefox don't necessarily indicate failure. I would kill the firefox processes and try again, running in headless mode first to rule out X-forwarding issues.
+
+HEADLESS=true bundle exec cucumber ...",1411066978,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","**physik** wrote:
+
+Thanks for the tip.
+However, that did not change anything.
+tests/browser$ bundle show selenium-webdriver
+/var/lib/gems/2.0.0/gems/selenium-webdriver-2.43.0
+tests/browser$ firefox --version
+(process:21861): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
+Mozilla Firefox 32.0
+
+Even downgrading to ff28 did not help.",1411066457,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","This issue was recently documented on the QA list. [1]
+
+Issue: selenium-webdriver < 2.42 doesn't work with Firefox 32.
+Solution: Update your gems by running `bundle update` in your tests/browser directory and verify that you're using selenium-webdriver >= 2.43 by running `bundle show selenium-webdriver`.
+
+[1] https://lists.wikimedia.org/pipermail/qa/2014-September/001890.html",1411062930,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"TODO someone needs to figure out what the visual treatment should look like
+
+The inputs in question already match :required:empty , so we can probably do most of this with CSS.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410984600,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yd4kojpa26xd52r2dadr,task_description,resolved
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,Verified the fix in production,1414101254,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 161613 merged by jenkins-bot:
+Style required but currently-invalid parameters on the template dialog
+
+https://gerrit.wikimedia.org/r/161613",1413312187,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 162511 merged by jenkins-bot:
+TextInputWidget: Add setValidation function to change pattern used to validate text
+
+https://gerrit.wikimedia.org/r/162511",1412030888,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 162511 had a related patch set uploaded by Alex Monk:
+TextInputWidget: Determine validity in onEdit rather than in setValue
+
+https://gerrit.wikimedia.org/r/162511",1411516231,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 161516 merged by jenkins-bot:
+TextInputWidget: Determine validity on blur and change.
+
+https://gerrit.wikimedia.org/r/161516",1411503450,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 161613 had a related patch set uploaded by Alex Monk:
+Style required but currently-invalid parameters on the template dialog
+
+https://gerrit.wikimedia.org/r/161613",1411164893,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 161516 had a related patch set uploaded by Alex Monk:
+Make InputWidget mixin FlaggedElement
+
+https://gerrit.wikimedia.org/r/161516",1411155876,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"Possible options:
+
+* Put a red(?) ring/border around the field
+* Put a red(?) ring/border around the field's label
+* Make the field's indicator red(?)
+* Make the field's background red(?)
+
+This class we'd toggle on/off should probably be in OOUI.",1410985084,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","screenshot
+
+Environment- Test2, beta, production
+
+Highlight a citation and select any text style from the drop-down. I get ""Uncaught TypeError: Cannot read property 'getSurface' of null"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14829}",1410886020,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_description,invalid
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation",This three year old task was probably fixed a long time ago.,1519405233,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","(In reply to Rummana Yasmeen from comment #4)
+> (In reply to Ritu Swain from comment #3)
+> > (In reply to Rummana Yasmeen from comment #1)
+> > > I could reproduce it while applying the text style, but the heading styles
+> > > on Citation,your screenshot also matches with the later case.
+> > 
+> > Rummana,it happens when the citation is highlighted and i change the text
+> > style to anything(not just Heading). In the screenshot, i had changed the
+> > style from paragraph to Heading, while the citation was highlighted.
+> 
+> Ritu, yes that is what I am referring to by ""applying Heading Style"" which
+> includes any of those heading formats (Heading,sub-heading 1 etc). By ""Text
+> style"", I thought you are referring to text formatting (Bold/Italic etc),
+> which I think is not how you reproduced this issue?
+
+i am not in front of my system to actually check it. but yes by ""Text Style"" i meant the headings and not the font styles.",1410901242,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","(In reply to Ritu Swain from comment #3)
+> (In reply to Rummana Yasmeen from comment #1)
+> > I could reproduce it while applying the text style, but the heading styles
+> > on Citation,your screenshot also matches with the later case.
+> 
+> Rummana,it happens when the citation is highlighted and i change the text
+> style to anything(not just Heading). In the screenshot, i had changed the
+> style from paragraph to Heading, while the citation was highlighted.
+
+Ritu, yes that is what I am referring to by ""applying Heading Style"" which includes any of those heading formats (Heading,sub-heading 1 etc). By ""Text style"", I thought you are referring to text formatting (Bold/Italic etc), which I think is not how you reproduced this issue?",1410897811,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","(In reply to Rummana Yasmeen from comment #1)
+> I could reproduce it while applying the text style, but the heading styles
+> on Citation,your screenshot also matches with the later case.
+
+Rummana,it happens when the citation is highlighted and i change the text style to anything(not just Heading). In the screenshot, i had changed the style from paragraph to Heading, while the citation was highlighted.",1410896613,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","(In reply to Rummana Yasmeen from comment #1)
+> I could not reproduce it while applying the text style, but the heading styles
+> on Citation,your screenshot also matches with the later case.",1410890520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","I could reproduce it while applying the text style, but the heading styles on Citation,your screenshot also matches with the later case.",1410890503,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a citation in the page
+3.Now click outside the page
+
+Observed Result:
+The Cite option and the Re-use option inside it remains enabled in the toolbar
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14780}",1410820020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o2nuawja3gd5ensyabpx,task_description,resolved
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,Verified the fix in production,1411682461,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,Verified the fix in test2,1411081667,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,Verified the fix in Betalabs,1410984894,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,"Change 160556 merged by jenkins-bot:
+Check whether there is a range selected when enabling/disabling re-use citation tool
+
+https://gerrit.wikimedia.org/r/160556",1410823383,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,"Change 160556 had a related patch set uploaded by Alex Monk:
+Check whether there is a range selected when enabling/disabling re-use citation tool
+
+https://gerrit.wikimedia.org/r/160556",1410823175,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","size invalid message shown
+
+Environment- Test2, beta
+
+1> Go to media settings dialog for any image.
+2>Go to Advanced Settings -> In Image size, click on custom and change its size to 0x0px.Notice message saying “Size values are invalid” shows up under the Make Full size button.
+3> Now choose a different image and for that image repeat steps #2.Notice “Size values are invalid” does not show up.
+
+Also if the image size is invalid then the insert button should get disabled, preventing the user from inserting it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14762}",1410809520,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ne77k6a4n7agmzuuryr2,task_description,resolved
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","Not pulled through yet, but will be.",1412646271,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 164784 merged by jenkins-bot:
+Emit change event when dimensions change in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/164784",1412632008,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 164784 had a related patch set uploaded by Mooeypoo:
+Emit change event when dimensions change in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/164784",1412536024,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","When the image size is default, inserting a non-numeric char changes it to custom.And if i keep entering non-numerics, then it gives the message ""Size values are Invalid"", but the ""Insert"" button stays active.
+
+It gets disabled only when you further make any changes to the settings. for ex-uncheck the “Wrap text around this item” checkbox or change the Image type to Basic /Frameless.Notice when any change is made to the settings then only the Insert button gets disabled and not when an invalid size is detected.",1411665315,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","(In reply to Rummana Yasmeen from comment #9)
+> Right now, it is not doing what you are suggesting here,the widget just does
+> not let you type anything when you try to input 0 and ""not"" making it
+> ""default""
+
+It's making it default, which erases the visible values. Technically it does what I explained; practically it does what you say. It's the same thing, but different user experiences.
+
+I am not sure if it's right to change the current behavior on that, though.
+
+> But, this is what it is doing right now.It is changing the value
+> automatically to default when user inputs non-numeric character.So, I
+> suggested to have similar behavior for both cases.
+
+I see what you're saying, but my point is that there's a difference conceptually between the two cases, so I think it's okay that the two behaviors are different two.
+
+When a user inserts ""0"" value, they likely meant for the image to have no dimensions, which effectively means it is defaulted.
+
+When a user inserts a non-numeric letter like ""a"" or ""-"" it is very likely that it's an error and even if it's not, we have no way of knowing what the user meant. Hence, we don't assume anything and instead we mark the values as ""invalid"".",1411066989,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","(In reply to Moriel Schottlender from comment #8)
+> We didn't want to force an input on the user, which is why non-numeric input
+> is allowed (but invalid.) The only problem with 0's is that practically
+> speaking, an empty input and 0 are more or less the same, so 0 (or empty)
+> assumes the user *meant* to say they don't want to set values -- which means
+> they wanted to go with ""default"".
+
+Right now, it is not doing what you are suggesting here,the widget just does not let you type anything when you try to input 0 and ""not"" making it ""default""
+
+> 
+> Changing the value automatically when the user inputs a non-numeric
+> character can be annoying if it was done by mistake. If I want to type 156
+> and I accidentally type 15t, it wouldn't be very comfortable to have the
+> widget automatically make my values into default.
+
+But, this is what it is doing right now.It is changing the value automatically to default when user inputs non-numeric character.So, I suggested to have similar behavior for both cases.
+
+> 
+> I think that the 0-to-default makes sense, but the other behavior will be
+> more of a hinderance to the user than help.",1411065711,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","We didn't want to force an input on the user, which is why non-numeric input is allowed (but invalid.) The only problem with 0's is that practically speaking, an empty input and 0 are more or less the same, so 0 (or empty) assumes the user *meant* to say they don't want to set values -- which means they wanted to go with ""default"".
+
+Changing the value automatically when the user inputs a non-numeric character can be annoying if it was done by mistake. If I want to type 156 and I accidentally type 15t, it wouldn't be very comfortable to have the widget automatically make my values into default.
+
+I think that the 0-to-default makes sense, but the other behavior will be more of a hinderance to the user than help.",1411008386,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","Right now, if you try to input 0 , the widget just does not let you to enter it, but as soon as you type some non numeric character, it automatically sets to default size , I think both cases should have same action: set to default size.",1411002564,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 160790 merged by jenkins-bot:
+Set size to default on 0 value
+
+https://gerrit.wikimedia.org/r/160790",1410983569,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px",I can still reproduce this on Betalabs.,1410982122,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 160789 merged by jenkins-bot:
+Validate size widget when activating/deactivating apply button
+
+https://gerrit.wikimedia.org/r/160789",1410911669,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 160790 had a related patch set uploaded by Mooeypoo:
+Set size to default on 0 value
+
+https://gerrit.wikimedia.org/r/160790",1410893461,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 160789 had a related patch set uploaded by Mooeypoo:
+Validate size widget when activating/deactivating apply button
+
+https://gerrit.wikimedia.org/r/160789",1410893393,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","Created attachment 16474
+size invalid message not shown when choosing a different image
+
+**Attached**: {F14764}",1410809614,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog","Environment- Test2, beta
+
+1> Go to Media Search dialog, it opens with the input box populated with the user name in it.
+2> I get JS console error Uncaught TypeError: undefined is not a function   , while the media search is still in progress .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1410808800,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-2jzgntengke75ccufbeh,task_description,declined
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog","(In reply to James Forrester from comment #3)
+> This was fixed in MediaWiki core as of wmf4 (to be released tomorrow to
+> MediaWiki.org).
+
+James is talking about a different thing that was fixed in wmf4.
+
+This bug is caused by an issue in jQuery with canceling JSONP requests. It can only be fixed if jQuery fixes it upstream, and I don't think that will happen.
+
+Closing as WONTFIX for lack of a RESOLVED UPSTREAM status.",1413386695,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2jzgntengke75ccufbeh,task_subcomment,NA
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog",This was fixed in MediaWiki core as of wmf4 (to be released tomorrow to MediaWiki.org).,1413386333,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2jzgntengke75ccufbeh,task_subcomment,NA
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog","This is a problem with the API in general, and while it is throwing an error, it shouldn't actually affect anything in the system -- that is, this error is stating that the API is unhappy about uselang variable, but the system is still working through the responses properly.",1413386204,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-2jzgntengke75ccufbeh,task_subcomment,NA
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog","Created attachment 16625
+screenshot
+
+1> Open insert -> Media. click ""cancel""to close the dialog.
+2> reopen the media search dialog,JS console error at this point.
+
+**Attached**: {F14759}",1412014027,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-2jzgntengke75ccufbeh,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"The list of allowed skins of the BetaFeatures extension (in $prefs[$key]['requirements']['skins']) is not displayed in the HTML code.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-betafeatures",1410615900,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-qwgyzixmq7444faqzt2k,task_description,resolved
+BetaFeatures: Warnings about allowed skins are not displayed,Thank you!,1411233187,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Change 161629 merged by jenkins-bot:
+Display allowed skins if and only if the current skin is not allowed
+
+https://gerrit.wikimedia.org/r/161629",1411233187,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"(In reply to Seb35 from comment #9)
+> Yes, I didn’t describe exactly the bug: the allowed skins were never
+> displayed in the HTML, neither when the current skin is an allowed skin,
+> neither when the current skin is not an allowed skin.
+> 
+> With the patch, the JS warning is now correctly triggered. When a blacklist
+> is specified for a beta feature, it is always added in the HTML.
+> 
+> For the skin, you are right, it should be displayed only when the current
+> skin is not allowed. See next patch.
+
+This looks good, thank you. :-)",1411170480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Change 161629 had a related patch set uploaded by Seb35:
+Display allowed skins if and only if the current skin is not allowed
+
+https://gerrit.wikimedia.org/r/161629",1411170016,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Yes, I didn’t describe exactly the bug: the allowed skins were never displayed in the HTML, neither when the current skin is an allowed skin, neither when the current skin is not an allowed skin.
+
+With the patch, the JS warning is now correctly triggered. When a blacklist is specified for a beta feature, it is always added in the HTML.
+
+For the skin, you are right, it should be displayed only when the current skin is not allowed. See next patch.",1411169281,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"I'm… confused.
+
+The purpose of the Beta Feature warning section is to inform you why enabling it won't be useful to you.
+
+I.e.:
+
+* if you don't have JS working, tell you if it needs JS;
+* if you don't use Vector, tell you if it only works for that skin;
+* if you don't have Internet Explorer, tell you if it only works in that browser.
+
+If none of these are met (i.e., it should work), the warnings should not appear.
+
+The title of this bug suggests that this is not understood.",1411162604,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Hah, fascinating. Okay, let's do this then.
+
+Should we mark this as resolved after merging the patch, or do you want to actually display this information?",1411161898,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Change 160213 merged by jenkins-bot:
+Display the required skins
+
+https://gerrit.wikimedia.org/r/160213",1411161865,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Thanks for your comment, I didn’t paid attention to the JS warning who disappeared, but by further investigating:
+1/ it is a feature to hide the warning ""JS is required"" when JS is enabled (see resources/betafeatures.js, there is the comment ""We're here so JavaScript works""), and
+2/ it was previously displayed because no skins were found in BetaFeaturesHooks::getPreferences (there are warnings in the debug log ""[BetaFeatures] The visualeditor-enable BetaFeature has no valid skins installed.""), which results not to add these beta features in the wgBetaFeaturesFeatures JS variables, which results betafeatures.js don’t loop into these beta features and don’t hide the JS warning (and don’t test if the browser is supported).
+
+So the bug is deeper I first thought, and I find it worth fixing it. But I aggree the skins requirements are not necessary and it is a change from the current behaviour, so I hide them in the LESS file (to keep consistency with current behaviour).",1411080422,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Fixing this bug will result in big red warnings being displayed under most BetaFeatures. The warnings also mention the hidden Minerva skin (e.g. for VisualEditor). Furthermore, they override the warnings about JavaScript being required.
+
+The bug is real and the fix is correct, but I'm pretty sure people started relying on the bug being a feature, and fixing this brings out a few more bugs. The existing beta features need be reviewed in context of this first, and I have no idea who's going to do it. :/",1411073812,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"The current state on the Wikimedia project is without the names of the required skins. In the case it is wanted to keep the current state (for Wikimedia and/or for the master branch of BetaFeatures), this feature can be hidden with CSS, similarly to the browser requirements, by editing BetaFeatures/resources/betafeatures.less.",1410617440,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Change 160213 had a related patch set uploaded by Seb35:
+Display the required skins
+
+https://gerrit.wikimedia.org/r/160213",1410616678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"The problem comes from BetaFeaturesHooks::getPreferences, in the code
+
+  $prefs[$key]['requirements']['skins'] = array_intersect( $prefs[$key]['requirements']['skins'], Skin::getAllowedSkins() );
+
+because Skin::getAllowedSkins() is an array key-value and we want the key and not the value, so it should be used array_keys( Skin::getAllowedSkins() ).
+
+I prepare the patch.",1410616013,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+VisualEditor: Copying and pasting a template causes comment to be inserted in Chrome on Windows due to broken native clipboard behaviour,"**Author:** `thalia.chan`
+
+**Description:**
+Copied the heading ""Lilypond source"" and the line of text below from this page: https://commons.wikimedia.org/wiki/File:C_sharp_and_double_sharp_music.svg?veaction=edit
+
+Pasted it into a similar page, open in a different tab, and a grey circle containing a question mark appeared at the end, which I am reliably informed is a comment. (Abandoned my edit in the end, so there's nothing to clean up.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: PC",1410569820,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-u3fli75nyhvezrtxd2vp,task_description,resolved
+VisualEditor: Copying and pasting a template causes comment to be inserted in Chrome on Windows due to broken native clipboard behaviour,"**gerritadmin** wrote:
+
+Change 160179 merged by jenkins-bot:
+Strip Start/EndFragment comments from paste
+
+https://gerrit.wikimedia.org/r/160179",1410800265,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-u3fli75nyhvezrtxd2vp,task_subcomment,NA
+VisualEditor: Copying and pasting a template causes comment to be inserted in Chrome on Windows due to broken native clipboard behaviour,"**gerritadmin** wrote:
+
+Change 160179 had a related patch set uploaded by Esanders:
+Strip Start/EndFragment comments from paste
+
+https://gerrit.wikimedia.org/r/160179",1410573171,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-u3fli75nyhvezrtxd2vp,task_subcomment,NA
+VisualEditor: Copying and pasting a template causes comment to be inserted in Chrome on Windows due to broken native clipboard behaviour,"The copied element here is just the LilyPond source template. Confirmed this bug in Win8/Chrome but not Ubuntu/Chrome. The comment inserted is <!-- EndFragment --> and comes from the clipboard API, not CE paste.",1410571230,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-u3fli75nyhvezrtxd2vp,task_subcomment,NA
+Errors in one module can affect other modules via $.ready,"This is not really a ResourceLoader bug but serious enough that some workaround is needed and that probably has to be done via RL.
+
+Due to jQuery bug #10251 [1] (wontfixed), errors in a jQuery domready handler prevent all subsequently added domready handlers from running. This means that errors in less reliable scripts like gadgets or user scripts can break any production code that is loaded after them and relies on $.ready (which is true for most extensions).
+
+
+[1] http://bugs.jquery.com/ticket/10251
+",1410534420,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-wfaki2636ucppxoiacm4,task_description,declined
+Errors in one module can affect other modules via $.ready,"* This applies to any event handler, not just DOMContentLoaded. E.g. click events: http://jsfiddle.net/mj8yeLmy/. Most instances of domready-handlers should probably use a `mw.hook` if they want to work as expected in the future of partial documents changing without refresh (as is already happening in LiquidThreads, VisualEditor, Flow and core's LivePreview).
+* Regarding gadgets not breaking, the same policy as extensions applies. Extensions can interfere with core, just as gadgets. If they misbehave with a certain language/wikiproject/skin combination; that should be fixed, or the relevant module excluded from running in that case, or disabled/not-enabled by those users (it's common for gadgets to say in their description ""Vector-only""). Can you given an example of a gadget causing errors in a certain skin-browser combination? That's relatively rare in my experience (except for outdated copies of gadgets on small wikis; this is generally addressed by loading the gadget from commons/meta/enwiki/mworg directly). It's generally fixed quickly when reported to gadget maintainers.
+* I've seen gadgets affecting the DOM of MediaWiki core and extension modules plenty. It's not rare.
+
+I'm still open to exploring a workaround on our side (in MediaWiki core). Note however that:
+* The $.ready promise does not expose its internal `jQuery.Callbacks` instance. Neither does it keep track of which have fired.
+* domready handlers should become rare over time. There are very few use cases left for it in our environment.
+* Beware the inconsistency with other event handlers.",1435888619,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wfaki2636ucppxoiacm4,task_subcomment,NA
+Errors in one module can affect other modules via $.ready,"* This applies to any event handler, not just DOMContentLoaded. E.g. click events: http://jsfiddle.net/mj8yeLmy/. Most instances of domready-handlers should probably use a `mw.hook` if they want to work as expected in the future of partial documents changing without refresh (as is already happening in LiquidThreads, VisualEditor, Flow and core's LivePreview).
+* Regarding gadgets not breaking, the same policy as extensions applies. Extensions can interfere with core, just as gadgets. If they misbehave with a certain language/wikiproject/skin combination; that should be fixed, or the relevant module excluded from running in that case, or disabled/not-enabled by those users (it's common for gadgets to say in their description ""Vector-only""). Can you given an example of a gadget causing errors in a certain skin-browser combination? That's relatively rare in my experience (except for outdated copies of gadgets on small wikis; this is generally addressed by loading the gadget from commons/meta/enwiki/mworg directly). It's generally fixed quickly when reported to gadget maintainers.
+* I've seen gadgets effecting the DOM of MediaWiki core and extension modules plenty. It's not rare.
+
+I'm still open to exploring a workaround on our side (in MediaWiki core). Note however that:
+* The $.ready promise does not expose its internal `jQuery.Callbacks` instance. Neither does it keep track of which have fired.
+* domready handlers should become rare over time. There are very few use cases left for it in our environment.
+* Beware the inconsistency with other event handlers.",1420714765,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wfaki2636ucppxoiacm4,task_subcomment,NA
+Errors in one module can affect other modules via $.ready,"See the blocked bug (T72756) for an example.
+
+Broken code should definitely not be silenced; the jQuery bug is not about silencing but limiting the effect of an error to the code which caused it. Which is a good practice in general, but I can see how jQuery has no easy way of following it in this case, without causing massive B/C breaks in promise behavior (although special-casing $.ready might be easier).
+
+This wouldn't be a problem on Wikimedia sites if there was an expectation for gadgets to not break, but my experience on medium-to-small wikis is that a few gadget-skin-browser combinations are broken at any given time, so seeing errors in the console in itself is not surprising, and if a completely unrelated product starts misbehaving, gadget maintainers are not going to attach any significance to it. So I'm not sure ""loudly"" is a fair description of a gadget throwing an exception.
+
+I don't think the same if true for gadgets messing up the DOM or otherwise affecting other modules; while in theory it's possible for that to happen in such a way that the gadget is not suspected, in practice I haven't ever seen that happening.
+
+One way to handle this (that could be inside or outside of jQuery) is to set up a timeout to check whether all domready handlers were executed, and force execution manually if it was broken by an exception. That would not stop the exception from being thrown and reported, but would limit its effect to the domready handler which caused it.",1418069344,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-wfaki2636ucppxoiacm4,task_subcomment,NA
+Errors in one module can affect other modules via $.ready,"An example of where this happened would be useful to assess what kind of code did this, who the affected users were, how and by whom it was addressed, etc.
+
+Initially I'm inclined to agree with jQuery and, here too, consider this an invalid bug. Broken code should not be silenced. There's a 1001 ways for gadgets and user scripts to break unrelated modules. That's the DOM for you. 
+
+This problem is in many ways similar to extensions vs MediaWiki core. When it goes wrong, the bug is reported, the broken module is found and either fixed or temporarily disabled until a maintainer can look into it. I think it's acceptable to encourage the community to apply a similar policy to their gadgets.
+
+If a gadget is broken, you can't leave it enabled and expect everything to degrade gracefully. There's too many asynchronous paths for code to take that absorbing it would be impossible (or unpractical). That's a responsibility gadget authors carry and should be familiar with if they've been given such access. And even if we could, trying to absorb it is in my opinion not we should want to achieve.
+
+I'm all for graceful degradation and often try to address hurdles and make user experiences as smooth as we can.
+
+But in cases like this, I'm all for letting it fail loudly. That's what errors are for.",1418060154,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wfaki2636ucppxoiacm4,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"double Toolbars in VE
+
+Environment- Test2, beta
+
+1> switch from Edit beta mode to Read mode notice the toolbar has slide down and is still visible in the Read mode.
+
+2> Click on Edit beta again,the Editor is displayed with two toolbars.See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70770
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70782
+
+**Attached**: {F15240}",1410526140,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-rurgi2fk663rrehd4j3x,task_description,resolved
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Verified the fix in production,1411681191,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,verified the backport in test2,1411666888,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162497 merged by Catrope:
+Don't drop 1px rects for FocusableNodes if all we have is 1px rects
+
+https://gerrit.wikimedia.org/r/162497",1411599824,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Verified the fix in Betalabs,1411592037,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162497 had a related patch set uploaded by Catrope:
+Don't drop 1px rects for FocusableNodes if all we have is 1px rects
+
+https://gerrit.wikimedia.org/r/162497",1411513254,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162360 merged by jenkins-bot:
+Don't drop 1px rects for FocusableNodes if all we have is 1px rects
+
+https://gerrit.wikimedia.org/r/162360",1411511065,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162359 merged by jenkins-bot:
+Tolerate null boundingRect in all code paths in DesktopContext#updateDimensions
+
+https://gerrit.wikimedia.org/r/162359",1411510662,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162360 had a related patch set uploaded by Catrope:
+Don't drop 1px rects for FocusableNodes if all we have is 1px rects
+
+https://gerrit.wikimedia.org/r/162360",1411499064,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162359 had a related patch set uploaded by Catrope:
+Tolerate null boundingRect in all code paths in DesktopContext#updateDimensions
+
+https://gerrit.wikimedia.org/r/162359",1411499058,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"Ok thanks so much Ritu! I can now reproduce it.The following error appears in the console as well:
+Uncaught TypeError: Cannot read property 'height' of null",1411493163,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"(In reply to Rummana Yasmeen from comment #11)
+> I cannot reproduce it following your steps.In steps 4, you mentioned to
+> repeat step 2, what change have you done in the page for the second time to
+> save it?
+
+http://youtu.be/CNqxmnconN8",1411486511,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"I cannot reproduce it following your steps.In steps 4, you mentioned to repeat step 2, what change have you done in the page for the second time to save it?",1411409958,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"This issue is reappearing.
+
+Steps-
+1> in a blank page insert a Reflist or Notelist Template.
+2> Save the page and reopen it in VE mode.
+3> Now cilck on the Read tab. 
+4> Repeat steps #2 and #3. Toolbars are getting added.",1411402650,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Verified the fix in test2,1410823905,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Verified the fix in Betalabs,1410559793,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,https://gerrit.wikimedia.org/r/160076 (the fix for bug 70770 fixes this too).,1410557788,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"Created attachment 16454
+Screenshot
+
+Ok, so I reproduced it on my user page too.This is happening when you just have the following on your page:
+
+ __NEWSECTIONLINK____NOTOC__
+
+**Attached**: {F15241}",1410557395,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"(In reply to Rummana Yasmeen from comment #4)
+> Ritu, can you share the link to the page where you are getting this, I can't
+> reproduce it either.
+
+links-:
+https://test2.wikipedia.org/wiki/User:Swainr?veaction=edit
+
+http://en.wikipedia.beta.wmflabs.org/wiki/User:Swainr?veaction=edit",1410556709,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"Ritu, can you share the link to the page where you are getting this, I can't reproduce it either.",1410553602,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"(In reply to Roan Kattouw from comment #2)
+> I can't reproduce this. Does this also happen when you're logged out?
+
+I can reproduce it(tried with a clear cache). Yes, it happens even when i am logged out.",1410548856,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,I can't reproduce this. Does this also happen when you're logged out?,1410543555,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Browsers- FF and Chrome. Couldn't test on Safari.,1410526326,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: Write unit tests for dm.Converter's use of dm.Model APIs,"There are no unit tests exercising features of dm.Converter that are currently unused by our node types, like returning null/undefined from toDataElements to trigger alienation, returning one a different type from toDataElements, returning an annotation type from a node's toDataElements, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410487620,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rcih7yd7sainywzff7di,task_description,open
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"1. place cursor in large body of text in FF
+2. Cursor up then down, everything is fine
+3. Cursor right a dozen or so times, then up
+
+Then cursor jumps up and left to the same place it was after (2).
+
+Initial investigations show that disabling handling of up/down arrows makes no difference, but disabling handling of left/right does fix, so probably something to do with the surfaceObserver state?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.mozilla.org/show_bug.cgi?id=1075901",1410456540,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_description,open
+VisualEditor: Up/down arrow in Firefox broken after using left/right,Possibly not anything we can actually fix…,1412359526,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"Workaround reverted, caused bug 71580 (ugly-looking ""NS_ERROR_FAILURE"" exceptions in some cases).",1412342877,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"More ""worked around"" than actually fixed, but…",1412266880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"**gerritadmin** wrote:
+
+Change 164162 merged by jenkins-bot:
+ve.ce.Surface: Magic workaround for broken Firefox cursoring
+
+https://gerrit.wikimedia.org/r/164162",1412261583,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"**gerritadmin** wrote:
+
+Change 164162 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ce.Surface: Magic workaround for broken Firefox cursoring
+
+https://gerrit.wikimedia.org/r/164162",1412193248,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1075901,1412191505,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"Calling nativeSelection.collapseToStart() seems to magically fix the erroneous behavior (http://jsfiddle.net/ybawstce/3/), we can probably use that as a workaround for selections that are already collapsed.
+
+(I see no neat way to fix non-collapsed ones; randomly calling some other Selection methods might help, but they probably won't be no-ops. These are a smaller problem anyway and can wait for Firefox to fix their bug.)
+
+I'm filing this upstream.",1412190573,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"Minimal test case: http://jsfiddle.net/ybawstce/1/
+
+(This will throw errors in some edge cases, but that's not the point; try arrowing around near the middle of the text.)",1412189941,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,Looks like a browser bug with Firefox's native selection having inconsistent state. I'm going to try poking some more at this tomorrow and maybe file some upstream bugs.,1412119103,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+"VisualEditor: ContextItemWidget's ""edit"" label should be a sibling of the description","Per Ed:
+
+| FIXME: This should be a sibling of the description label, with enough space
+| left to the right of the description so it shows even if the description is
+| too wide (e.g. an external link)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410389880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rqg7uqc7ixojj2plkvbr,task_description,invalid
+"VisualEditor: ContextItemWidget's ""edit"" label should be a sibling of the description",This code has been substantially re-written since this task was created; the concern no longer applies.,1493661496,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rqg7uqc7ixojj2plkvbr,task_subcomment,NA
+"Dropdowns in the VE toolbar opening ""under"" the content area in the Chameleon skin","There is an issue in Chrome when using the VisualEditor extension. The dropdowns in the VE toolbar seem to be opening ""under"" the content area, hiding their contents.
+
+The problem is a bug in the jQuery 1.8 lib used in MW <1.24 (or a variation thereof): http://bugs.jquery.com/ticket/11635
+
+Todo: Backport the fix in jQuery 1.11.
+
+--------------------------
+**Version**: 1.23
+**Severity**: normal",1410377400,PHID-USER-cc6dswbtmstfsb4ldmit,PHID-TASK-uk3slh6vbmq3xu4fvsu3,task_description,resolved
+"Dropdowns in the VE toolbar opening ""under"" the content area in the Chameleon skin",Works with latest versions of VE and Chameleon skin.,1433587635,PHID-USER-cc6dswbtmstfsb4ldmit,PHID-TASK-uk3slh6vbmq3xu4fvsu3,task_subcomment,NA
+VisualEditor: LinkCache should also cache mw-redirect and mw-disambig statuses,"… and use them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410376320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f6bgxahe6w7alqbxqvv6,task_description,invalid
+VisualEditor: LinkCache should also cache mw-redirect and mw-disambig statuses,... Doesn't it do this already?,1410437964,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-f6bgxahe6w7alqbxqvv6,task_subcomment,NA
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","screenshot1
+
+Environment- test2, beta, production
+
+1> open a page in VE, add a template. Add a Field name to the template, now delete that name.
+2>click to add more information again, notice  the previous field name entry is shown  in a list.
+3>  In the same Field name, type in another name , now delete that name.
+4> Repeat steps #2 and 3. Until you get the show one more field(this appears after the 4th entry). Click on it and it seems to add nothing to the existing Template data.
+Same behavior can be seen with Templates having at least 4 parameters, for ex- Reflist.
+See screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14783}",1410275700,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-hrnl7scbkqiphhkzetoj,task_description,resolved
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","Issue fixed in test2, beta, production.",1412608950,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-hrnl7scbkqiphhkzetoj,task_subcomment,NA
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","**gerritadmin** wrote:
+
+Change 160500 merged by jenkins-bot:
+Template dialog: Show up to the limit of parameters, not up to the limit + 1
+
+https://gerrit.wikimedia.org/r/160500",1410911097,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hrnl7scbkqiphhkzetoj,task_subcomment,NA
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","**gerritadmin** wrote:
+
+Change 160500 had a related patch set uploaded by Jforrester:
+Template dialog: Show up to the limit of parameters, not up to the limit + 1
+
+https://gerrit.wikimedia.org/r/160500",1410808571,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hrnl7scbkqiphhkzetoj,task_subcomment,NA
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","Created attachment 16415
+screenshot2
+
+**Attached**: {F14784}",1410275763,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-hrnl7scbkqiphhkzetoj,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,"In Chrome and Internet Explorer it is perfectly possible to click repeatedly on the Save button and achieve nothing. On large portions of it (especially at the top, but you can also place the pointer exactly between the two words and get the same result) the pointer won't change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410254700,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-edczq7heipb4q3v2tcxp,task_description,resolved
+VisualEditor: Save page button is not fully clickable,"Nope. Just tried again incognito mode on IE, FF and Chrome.",1410544386,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,"(In reply to Elitre from comment #4)
+> It's not gone for me.
+
+It works for me. Does it work for you when you're logged out?",1410543637,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,It's not gone for me.,1410537943,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,Yes.,1410461670,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,This is probably the bug fixed by 2aebe8054eed2516ac06c62101f2793f29c416aa.,1410267366,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,"Actually, Safari is probably the only browser where this doesn't happen. You can reproduce on all the 3 buttons near the Save one, but not on the dialogs' ones.",1410255470,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"The LST markers <section begin=""2011-07-25"" /> and <section end=""2011-07-25"" /> used to be unparsed, but now that Parsoid parses them to <meta>s they're uneditable. Boo.
+
+(The actual transclusion {{#lst:Foo|Bar}} as a parser function ""just works"".)
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1410209220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-abnrntzw5wtc5wukwim2,task_description,stalled
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"how would you activate the alienextensionnode editor/module on a Wiki? I've played around with the $wgVisualEditorPluginModules array, but cannot get it to work.",1467931922,PHID-USER-gqtrt6xysxqoow52i7fc,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"Ok, it seems to me that the alienextensionnode editor is activated on the Page: namespace but not on the main namespace (or something like that).
+
+But as we should definitely create an editing widget for this tag, we will fix this issue at the same time.",1467874769,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"I tried this page and unfortunately it was just changed today so that the <section> tag at the beginning was removed; so I created another page on that Wiki with a section tag:
+
+[[ https://en.wikisource.org/w/index.php?title=Sectiontest&veaction=edit | https://en.wikisource.org/w/index.php?title=Sectiontest&veaction=edit ]]
+
+unfortunately I don't see that the section tag is handled at all; it doesn't seem to be rendered. Can you take a look?",1467836993,PHID-USER-gqtrt6xysxqoow52i7fc,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"I tried this page and unfortunately it was just changed today so that the <section> tag at the beginning was removed; so I created another page on that Wiki with a section tag:
+
+[[ https://en.wikisource.org/w/index.php?title=Sectiontest&action=edit | https://en.wikisource.org/w/index.php?title=Sectiontest&action=edit ]]
+
+unfortunately I don't see that the section tag is handled at all; it doesn't seem to be rendered. Can you take a look?",1467832744,PHID-USER-gqtrt6xysxqoow52i7fc,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"It seems to me that the latest versions of VisualEditor and Parsoid provides basic support (with an editing UI) for the <section> tag.
+
+For example: https://en.wikisource.org/wiki/Page:Dictionary_of_Christian_Biography_and_Literature_(1911).djvu/161?veaction=edit (there is a <section begin=""""> tag at the beginning of the page's body.
+
+But we should definitely create a nicer UI for them.",1467790836,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,will this task be worked again?,1467783508,PHID-USER-gqtrt6xysxqoow52i7fc,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"**gerritadmin** wrote:
+
+Change 162652 had a related patch set uploaded by Jforrester:
+[WIP] In VisualEditor, show <section> elements and let them be edited
+
+https://gerrit.wikimedia.org/r/162652",1411581215,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"**gerritadmin** wrote:
+
+Change 159182 abandoned by Jforrester:
+[WIP] Show LST <section> elements and let them be edited
+
+Reason:
+Moving to LST repo.
+
+https://gerrit.wikimedia.org/r/159182",1411581079,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"**gerritadmin** wrote:
+
+Change 159182 had a related patch set uploaded by Jforrester:
+[WIP] Show LST <section> elements and let them be edited
+
+https://gerrit.wikimedia.org/r/159182",1410211162,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button","Steps to reproduce:
+
+1.Open a page with VE
+2.Open Media Settings dialog for a Frameless/Basic type image which does not have ""Border"" set to it.
+3.Now check the ""Border"" checkbox
+
+
+Observed Result:
+It does not enable the ""Apply Changes"" button in the media Settings dialog
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1410206160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ix3up4zzzosiimtj4nop,task_description,resolved
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button",Verified the fix in production,1411071344,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button",Verified the fix in test2,1410553926,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button","Released in OOjs 1.1.1, now in MW-core etc.",1410396413,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button",Should be fixed by https://gerrit.wikimedia.org/r/#/c/159639/,1410395270,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button","This is due to an OOjs bug.
+
+>>> OO.compare( { foo: 3 }, { foo: 4 } )
+false
+
+>>> OO.compare( { foo: false }, { foo: true } )
+true
+
+Because we have special cases for 'number' and 'string' but not 'boolean'.",1410394010,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","This is similar to Bug 69711.
+
+Steps to reproduce:
+
+1.  Type some text:  ""Foo bar baz bat""
+
+2.  Add a citation.
+
+3.  Finish typing the sentence.
+
+6.  Oops, where did the citation go?
+
+
+Results:
+
+When you exit the ref dialog, the new ref text remains highlighted, and typing results in it being overwritten by your next character.  
+
+Expectation:  after I've made a ref, de-select the ref and put the cursor at the end, so I can keep writing or add a second ref.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410205260,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_description,open
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","> Do you think that design decision should be reversed
+
+Yes.  Unless I'm likely to need that thing to be selected when I'm done (e.g., if I'm likely to create a link *and* italicize it – which isn't a likley case), then I want it to be de-selected by default.",1410217088,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","(In reply to Mike Christie from comment #4)
+> On reflection I agree; ""Save and add another"" isn't a common case.  I'll see
+> if I run into situations where that would be a useful option and will post
+> an enhancement request if I do.
+
+Thanks! :-)",1410213405,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","On reflection I agree; ""Save and add another"" isn't a common case.  I'll see if I run into situations where that would be a useful option and will post an enhancement request if I do.",1410208984,PHID-USER-ufjbf3qatjamiwoal5fp,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","(In reply to Mike Christie from comment #2)
+> I wouldn't want to make a blanket statement, and I can recall situations
+> where the fact that an object remains selected was useful -- going straight
+> back into a cite to fix an error I just realized I made, for example.  For
+> some things, such as links, I think it's definitely better to deselect --
+> it's absolutely normal for a user to want to continue typing.  For
+> templates, I can see an argument for keeping the selection.  Citations seem
+> to me more like links than templates in this way.
+> 
+> I think the design question is: what would a user who is expert in VE want
+> the system to do to maximize productivity?  I think the answer is going to
+> be to leave it unselected more often than not.
+
+That's a reasonable way of looking at it; I think I agree. There are some possible issues with block images (where, especially if you have a long infobox on a short screen, the content may have been inserted off-screen), but maybe we should optimise for the most common case? Will ask others on the team to weigh in, but broadly this seems sensible. Thanks!
+
+
+> One other thought: just as there's a ""Save"" and also a ""Save and new"" pair
+> of buttons in some interfaces, there might be a ""Save and add another
+> citation"" button on the interface, or something along those lines.  But
+> perhaps that's a separate enhancement suggestion.
+
+(Yes, this should be a new bug, but…)
+
+Hmm. I think that ""Save and also add a new one"" is really rare for inserting content, and really confusing. Wouldn't it be better to have easily-rememberable keyboard shortcuts instead?",1410208394,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","I wouldn't want to make a blanket statement, and I can recall situations where the fact that an object remains selected was useful -- going straight back into a cite to fix an error I just realized I made, for example.  For some things, such as links, I think it's definitely better to deselect -- it's absolutely normal for a user to want to continue typing.  For templates, I can see an argument for keeping the selection.  Citations seem to me more like links than templates in this way.
+
+I think the design question is: what would a user who is expert in VE want the system to do to maximize productivity?  I think the answer is going to be to leave it unselected more often than not.
+
+One other thought: just as there's a ""Save"" and also a ""Save and new"" pair of buttons in some interfaces, there might be a ""Save and add another citation"" button on the interface, or something along those lines.  But perhaps that's a separate enhancement suggestion.",1410207927,PHID-USER-ufjbf3qatjamiwoal5fp,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","In VE, new stuff always gets selected after you insert it – images, references, templates, comments, …. Do you think that design decision should be reversed, or do you think that there is something special about references that deserves different treatment?",1410206978,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: When CE gets re-enabled, the cursor always jumps to the beginning index of the first line irrespective of where user wanted to position it","Steps to reproduce:
+
+
+1.Open a page with VE which has some text in it
+2.Place somewhere outside the CE to disable it
+3.Now click at the end of a text to place your cursor on that position of article to make an edit
+
+Observed Result:
+The cursor jumps to the beginning of the first line of the article.
+
+
+Envionment:Betalabs,test2,production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410200160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-w7b6jdh4p5xzbufd7owv,task_description,open
+VisualEditor:  Insert > References list is very large in Firefox,"This may be the opposite of bug 68226:  
+
+The References List dialog in Firefox 31 on my Mac is the expected width, but it is the full height of the screen.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70317",1410150120,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-eng4eygt5qljaa7eds7p,task_description,resolved
+VisualEditor:  Insert > References list is very large in Firefox,Verified the fix in production,1411681735,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eng4eygt5qljaa7eds7p,task_subcomment,NA
+VisualEditor:  Insert > References list is very large in Firefox,"Yeah, part of Roan's fixes.",1411417195,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eng4eygt5qljaa7eds7p,task_subcomment,NA
+VisualEditor:  Insert > References list is very large in Firefox,"Can't reproduce using Firefox 32 on Windows 7, nor any other browser. Is this still happening for you? I think it was fixed along with other dialog sizing bugs in OOjs UI recently.",1411414227,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eng4eygt5qljaa7eds7p,task_subcomment,NA
+VisualEditor:  Insert > References list is very large in Firefox,Is this another OOUI breakage?,1410202929,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eng4eygt5qljaa7eds7p,task_subcomment,NA
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"I was cutting & pasting sentences and it worked nearly flawlessly, including the references! :)
+
+Though, somehow during cut & paste of a reference to the end of a sentence, the period ended up inside the wiki link:
+
+https://en.wikipedia.org/w/index.php?title=Tim_Hortons&diff=624612573&oldid=624559527
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410140640,PHID-USER-lzhljhpbm3qfphvqyill,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_description,resolved
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"Yup, good spot.",1491407105,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_subcomment,NA
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"I think this has been resolved a while ago by the ""active link"" functionality. It is still possible to paste things into a link rather than after it, but it should be clear that this is what you're doing.
+
+{F7267037}
+
+{F7267050}",1491406979,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_subcomment,NA
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"If you're typing at the end of a link and press ' ' (space), '.', or one of a bunch of other characters defined in Unicode as word-separators, we terminate the link before the new character.
+
+It's possible, however, to insert a sequence with a '.' or similar via rich copy-and-paste; I'm not sure if we should strip it here or not. Seems a bit magical…",1410203368,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_subcomment,NA
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"it's possible there is some user error involved, although see if this can be reproduced...",1410141067,PHID-USER-lzhljhpbm3qfphvqyill,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_subcomment,NA
+VisualEditor: Inserted link annotations don't take pre-annotations (but inserted language annotations do),"cmd K (and link button) after a space lost previous italic or/and bold formatting
+
+Mac OS/X Chrome and Safari
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410121020,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-wkcjdg26ppvadj2qcmne,task_description,resolved
+VisualEditor: Inserted link annotations don't take pre-annotations (but inserted language annotations do),"Change 160216 merged by jenkins-bot:
+ve.ui.AnnotationInspector: Apply existing annotations to inserted content
+
+https://gerrit.wikimedia.org/r/160216",1410802184,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wkcjdg26ppvadj2qcmne,task_subcomment,NA
+VisualEditor: Inserted link annotations don't take pre-annotations (but inserted language annotations do),"Change 160216 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ui.AnnotationInspector: Apply existing annotations to inserted content
+
+https://gerrit.wikimedia.org/r/160216",1410623352,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wkcjdg26ppvadj2qcmne,task_subcomment,NA
+VisualEditor: Inserted link annotations don't take pre-annotations (but inserted language annotations do),"> (but inserted language annotations do)
+
+That's because they don't insert any content, unlike link annotations.",1410623326,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wkcjdg26ppvadj2qcmne,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,"Steps to reproduce:
+
+1.Open a page with VE
+2.Click on the link inspector icon from the toolbar
+
+
+Observed Result:
+The link inspector is not opening up in the first session
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409954460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u7wmfggaowz3nwqsib4h,task_description,resolved
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,Verified the fix in production,1411070671,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,Verified the fix in Betalabs,1410197975,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,"**gerritadmin** wrote:
+
+Change 158807 merged by jenkins-bot:
+Followup 67f83f1: fall back to empty string to avoid 'undefined'
+
+https://gerrit.wikimedia.org/r/158807",1409958908,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,"**gerritadmin** wrote:
+
+Change 158807 had a related patch set uploaded by Catrope:
+Followup 67f83f1: fall back to empty string to avoid 'undefined'
+
+https://gerrit.wikimedia.org/r/158807",1409956827,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,It also happens when you try to inspect an existing link,1409954648,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+"Flow: when enabled on a subpage, doesn't show ""< grandparent | parent"" crumb trail","Compare https://www.mediawiki.org/wiki/Talk:VisualEditor/Beta_Features/Language
+with https://www.mediawiki.org/wiki/Roadmap/Archive
+
+The Flow page doesn't show the < Talk:VisualEditor | Beta_Features ""crumb trail"" to parent pages that you normally see under the page title of a subpage in a <div id=""contentSub""><span class=""subpages"">.
+
+I think includes/skins/Skin.php's subPageSubtitle() normally fabricates this.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1409952060,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-aa6mqfnkyrurwc3qf3hi,task_description,open
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"Missing template field name
+
+On any page e.g. http://en.wikipedia.beta.wmflabs.org/wiki/0.2619265827018721?veaction=edit
+
+Click Insert/Template
+
+
+Type a name like ""New template"" and click ""Add template""
+
+In the resulting box, type ""New template field"" or some such. 
+
+Click the ""Unknown field"" to add the field to the template
+
+Result should show ""New template field"" but instead is blank.  Note that a ""Remove field"" icon is in place for the invisible template field. 
+
+See screen shot comparing beta labs with test2wiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14914}",1409851740,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_description,resolved
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,Verified the fix in production,1411070490,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"Yes, working properly in Betalabs and test2",1409944422,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,Seems to be working properly in beta labs now,1409866602,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,Should be fixed on master.,1409866416,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"**gerritadmin** wrote:
+
+Change 158508 merged by jenkins-bot:
+Rename $label to $labelElement in MWParameterPage to avoid naming conflict
+
+https://gerrit.wikimedia.org/r/158508",1409865732,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"**gerritadmin** wrote:
+
+Change 158508 had a related patch set uploaded by Jforrester:
+Rename $label to $labelElement in MWParameterPage to avoid naming conflict
+
+https://gerrit.wikimedia.org/r/158508",1409865386,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"**gerritadmin** wrote:
+
+Change 158503 merged by jenkins-bot:
+Rename $label to $labelElement in MWParameterPage to avoid naming conflict
+
+https://gerrit.wikimedia.org/r/158503",1409864864,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"**gerritadmin** wrote:
+
+Change 158503 had a related patch set uploaded by Alex Monk:
+Rename $label to $labelElement in MWParameterPage to avoid naming conflict
+
+https://gerrit.wikimedia.org/r/158503",1409864633,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"If you keep it as $label, then add a parameter to a template, then get parameterPage.$label, it appears in place of the outline item widget's label.
+
+Looks like the OOUI element mixin refactor is to blame...",1409864355,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,Renaming this.$label to something else (e.g. $labelElement) in modules/ve-mw/ui/pages/ve.ui.MWParameterPage.js fixes this,1409862506,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],"We should even if it's a minuscule part of the market for tablets, because we're going to eventually support phones (and for decency's sake).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409789520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3gsxa566npjtwodxt42a,task_description,resolved
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],Please do not break the history.,1470786015,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3gsxa566npjtwodxt42a,task_subcomment,NA
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],Moved to projects instead.,1422405435,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3gsxa566npjtwodxt42a,task_subcomment,NA
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],"(In reply to Alex Monk from comment #1)
+> Is this a tracking bug?
+
+Yes.",1415031175,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3gsxa566npjtwodxt42a,task_subcomment,NA
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],Is this a tracking bug?,1414870223,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3gsxa566npjtwodxt42a,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Kdammers is running the current version of Mozilla on Windows 7 with a dual-script keyboard.  Typing in Hangul (한글) is not working in VisualEditor:  letters can be removed but when they are typed, they just disappear.
+
+
+Stefan2 did some related testing:
+
+Ibus-hangul (Korean) seems to work correctly in Firefox 32.0. In Chromium 37.0.2062.94, it produces spaces instead of Hangul letters. However, if a syllable only consists of two letters, the syllable shows up after typing in the second letter. It seems that syllables consisting of more than two letters can't be typed in using Chromium.
+
+Anthy (Japanese) is broken in both browsers.
+
+**See Also**: {T52631}",1409765460,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uhvgmgrdscjhwyvdb474,task_description,resolved
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,Follow-up in {T127108}.,1457046550,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,">>! In T72353#1864840, @revi wrote:
+> Nope., It's still happening, in different form now.
+
+I think that's the same as {T120156} right?",1454540912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Nope., It's still happening, in different form now.
+
+----
+Current status of Korea page
+---
+
+(`|` means cursor)
+```
+가나다라마바사아자차카파타하|
+```
+After I put two enters,
+```
+가나다라마바사아자차카파타하
+
+|
+```
+And now I put the word ""치킨"".
+Expected behavior
+---
+```
+가나다라마바사아자차카파타하
+
+치킨|
+```
+Actual Behavior
+---
+```
+가나다라마바사아자차카파타하치킨|
+
+// blank lines still there, phabricator doesn't recognize blank lines...
+```
+
+OS: Win7, 64bit, MS default IME, UserAgent: `Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0` See also P2386.",1450170537,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Nope., It's still happening, in different form now.
+
+----
+Current status of Korea page
+---
+
+(`|` means cursor)
+```
+가나다라마바사아자차카파타하|
+```
+After I put two enters,
+```
+가나다라마바사아자차카파타하
+
+|
+```
+And now I put the word ""치킨"".
+Expected behaviors
+---
+```
+가나다라마바사아자차카파타하
+
+치킨|
+```
+Actual Behavior
+---
+```
+가나다라마바사아자차카파타하치킨|
+
+// blank lines still there, phabricator doesn't recognize blank lines...
+```
+
+OS: Win7, 64bit, MS default IME, UserAgent: `Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0` See also P2386.",1449656546,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Nope., It's still happening, in different form now.
+
+----
+Current status of Korea page
+---
+
+(`|` means cursor)
+```
+가나다라마바사아자차카파타하|
+```
+After I put two enters,
+```
+가나다라마바사아자차카파타하
+
+|
+```
+And now I put the word ""치킨"".
+Expected behaviors
+---
+```
+가나다라마바사아자차카파타하
+
+치킨|
+```
+Actual Behavior
+---
+```
+가나다라마바사아자차카파타하치킨|
+
+// blank lines still there, phabricator doesn't recognize blank lines...
+```
+
+OS: Win7, 64bit, MS default IME, UserAgent: `Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0`",1449655021,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"OK, @revi, any chance you could re-check http://deployment.wikimedia.beta.wmflabs.org/wiki/Korea?veaction=edit ? If I type 'ganada' into my Korean IME I get 가나다  correctly. However, {T120156} is a horrible bug but I think a distinct blocker from this one. Provisionally re-closing.",1449104765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Change 247800 merged by jenkins-bot:
+Diff richtext to build model changes
+
+[[https://gerrit.wikimedia.org/r/247800]]",1449100129,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"I have optimistically tagged this bug in change 247800, because it will fix many DOM/DM synchronization errors, and I suspect that is the underlying cause of the symptoms @revi reports above.",1448871169,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Change 247800 had a related patch set uploaded (by Divec):
+Diff richtext to build model changes
+
+[[https://gerrit.wikimedia.org/r/247800]]
+",1448871004,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Typed ##가나다## in the page.
+
+It makes newline (I thought like I typed enter.) and then 가나다. When I clicked the first line, it just don't let me write there and wrote my 가  at the newline.
+
+So, more graphically.
+
+what I did:
+My browser is in this stage;
+```
+|(cursor)
+```
+type ##가나다## now.
+
+what I expected:
+```
+가나다|(cursor)
+```
+what I get:
+```
+(empty line)
+가나다|(cursor)
+```
+At this stage, further ""enter"" command does not work, and I am stuck in that particular line.
+
+If I try to put the words on empty line...
+
+```
+|
+가나다
+```
+then it becomes...
+```
+(empty)
+가|가나다
+```
+
+Really weird, isn't it?
+
+OS: Win 7, Browser: FireFox 41.0.",1443609196,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hello, does it now work correctly on http://deployment.wikimedia.beta.wmflabs.org/wiki/Korea?veaction=edit ? It works for me there with IE/Windows 8 .
+
+@Revi, Thanks for the updated log for Firefox!",1443547826,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hello, does it now work correctly on http://deployment.wikimedia.beta.wmflabs.org/wiki/Korea?veaction=edit ? It works for me there with IE/Windows 8 .",1443547680,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"OK, @dchan I updated the P2090 and P2091 to FF info.
+
+Also, @Jdforrester-WMF I still can reproduce this.",1443325286,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"I haven't got any time to sit in front of the desk, run FF, verify whether
+this is fixed (in this case I will close the bug as I did on T52631) or not
+(in this case I will provide additional debug information as requested by
+@dchan.) Since dchan cannot reproduce the bug, it seems that I am the SPoF.
+
+It's national holiday in Korea and I'm currently at a house without any
+computer. So, please wait until I can touch computers ;)",1443313193,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,Is this now resolved?,1443277648,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,">>! In T72353#1675748, @dchan wrote:
+> Thanks for the event log!
+> 
+> That's on Chrome 45 right? Are you seeing the issue in Chrome too? It seems to work correctly for me in Chrome on Windows 8, and I get an essentially identical event log, so I'm confident our IMEs are essentially the same :-)
+> 
+>  Could you also provide a log created on Firefox? Thanks!
+
+Oh well, my bad. I was proven stupid. New log will be uploaded later tomorrow or Monday. (since it's [[ https://en.wikipedia.org/wiki/Chuseok | Chuseok ]] )",1443266036,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Change 241124 merged by jenkins-bot:
+Ignore slugs and chimeras when preventing identical re-renderings
+
+[[https://gerrit.wikimedia.org/r/241124]]",1443265417,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Change 241124 had a related patch set uploaded (by Divec):
+Ignore slugs and chimeras when preventing identical re-renderings
+
+[[https://gerrit.wikimedia.org/r/241124]]
+",1443209981,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"I can reproduce similar symptoms on IE on Windows 8. It can be reproduced by pressing Enter then 'ㄱ', which triggers the issue in T91244 . Perhaps the Firefox on Windows 7 issue is essentially the same; if you provide a log I will confirm.",1443207768,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Thanks for the event log!
+
+That's on Chrome 45 right? Are you seeing the issue in Chrome too? It seems to work correctly for me in Chrome on Windows 8, and I get an essentially identical event log, so I'm confident our IMEs are essentially the same :-)
+
+ Could you also provide a log created on Firefox? Thanks!",1443205750,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Here you are. P2090 for English and P2091 for Korean.
+
+{P2090}
+{P2091}",1443172097,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hi, unfortunately I can't reproduce the problem. (I guess it may depend on the IME version, which is very common). So to help us debug this, could you help us by sending the event log when you type '가나다' on your platform?
+
+1. Go to https://rawgit.com/wikimedia/VisualEditor/master/demos/ve/eventLogger.html
+2. Click 'Start Logging Keyboard Events'
+3. Type the text (i.e. just press 'rkskek' - don't press any other key)
+4. Click on the big box full of debug info
+5. Copy the text with the mouse
+6. Paste into a file and attach the file to this bug
+
+Thanks very much!",1443151406,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hi, unfortunately I can't reproduce the problem. So to help us debug this, could you help us by sending the event log when you type '가나다' on your platform?
+
+1. Go to https://rawgit.com/wikimedia/VisualEditor/master/demos/ve/eventLogger.html
+2. Click 'Start Logging Keyboard Events'
+3. Type the text (i.e. just press 'rkskek' - don't press any other key)
+4. Click on the big box full of debug info
+5. Copy the text with the mouse
+6. Paste into a file and attach the file to this bug
+
+Thanks very much!",1443151029,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"I can reproduce this. Win 7, 64bit, (I don't know what IME I'm using but default IME for Korean in Windows). Firefox Version 41.0.
+
+== Step to reproduce==
+
+1. Go to [[https://ko.wikipedia.org/wiki/%EC%82%AC%EC%9A%A9%EC%9E%90:Gisado/VEtest?veaction=edit|https://ko.wikipedia.org/wiki/%EC%82%AC%EC%9A%A9%EC%9E%90:Gisado/VEtest?veaction=edit]]
+2. Type enter twice.
+3. Try to type ##가나다##
+
+== Expected result ==
+ ##가나다## shows up below ##가나다라마바사아자차카파타하##., like this.
+{P2083}
+
+==Result bug==
+Two enters magically removed, and two ##ㅏ##s are put after ##가나다라마바사아자차카파타하##, like:
+{P2084}
+",1443086053,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hi, typing phonetically with Nalgaeset keyboard seems to work for me on Windows 8, Firefox 40.0.3 (and also Chrome 45.0.2454.99 m), both on en.wikipedia.org and on VE-standalone master.
+
+Can we close this, or is anyone still seeing corruption?",1443035039,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"When I tried to do test for bug 50631 on [[en:User:Hym411/VETest]] (second line), I got this bug. bug 50631 at least returns some result - though it's full of errors - but this gives some nonsense.
+
+Test envorinment: Win7, Google Chrome version 37.0.2062.120 m",1410753008,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,Are we sure?  Bug 50631 can get something.  I believe that this user can't get anything.,1409850815,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,Exactly same problem of bug 50631. This should be merge into 50631.,1409808290,PHID-USER-ipgdr6xrndwpztdrubk4,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"What is ""the current version of Mozilla""? Firefox? Seamonkey?",1409777133,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"This is probably a dupe of bug 50631, but leaving it open.",1409766034,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] anoneditwarning notice displays unparsed links with $1 and $2,"Screenshot of bug.
+
+The anoneditwarning message now takes parameters apparently. ApiVisualEditor.php.
+
+See mediawiki-core's EditPage.php for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14741}",1409736780,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3jtahafvmd46fufkeey7,task_description,resolved
+VisualEditor: [Regression pre-wmf20] anoneditwarning notice displays unparsed links with $1 and $2,Fixed in gerrit Ia28f59a34.,1409859524,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3jtahafvmd46fufkeey7,task_subcomment,NA
+VisualEditor should respect [[MediaWiki:Noarticletext]],"**Author:** `gryllida`
+
+**Description:**
+[[MediaWiki:Noarticletext]] is shown when someone is creating a page, above the edit box. See:
+
+https://en.wikiversity.org/w/index.php?title=MediaWiki:Noarticletext
+https://en.wikiversity.org/w/index.php?title=Lalala&action=edit
+
+VisualEditor should respect this and also show such text in some prominent place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409710020,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-utd4dwndfqs2xvimd262,task_description,invalid
+VisualEditor should respect [[MediaWiki:Noarticletext]],Indeed.,1409781154,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utd4dwndfqs2xvimd262,task_subcomment,NA
+VisualEditor should respect [[MediaWiki:Noarticletext]],"https://en.wikiversity.org/w/index.php?title=Lalala&action=edit&uselang=qqx is showing 'newarticletext' (not 'noarticletext'), which VE already does...
+
+'noarticletext' is shown on action=view.",1409775654,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-utd4dwndfqs2xvimd262,task_subcomment,NA
+VisualEditor: Switch to source editing dialog too tall,"**Author:** `josephsieh`
+
+**Description:**
+screen shot of ""Switch to source editing"" dialog too tall issue on Safari.
+
+After user modified something in Visual Editor and then tries to click on ""Edit"" without clicking ""Save page"", the ""Switch to source editing?"" dialog appears to be too tall as the attached screenshot shows.
+
+It happens on 
+
+OSX 10.9.4
+Safari 7.0.6.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70545
+
+**Attached**: {F14706}",1409705580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5zoyxx73z2lluiw4akkr,task_description,resolved
+VisualEditor: Switch to source editing dialog too tall,Verified the fix in production,1411681613,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5zoyxx73z2lluiw4akkr,task_subcomment,NA
+VisualEditor: Switch to source editing dialog too tall,"Yeah, checked on a Mac.",1411417372,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5zoyxx73z2lluiw4akkr,task_subcomment,NA
+VisualEditor: Switch to source editing dialog too tall,"This might be the same issue as bug 70545 and looks similarly fixed to be, but I don't have a Mac to test on.",1411415059,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5zoyxx73z2lluiw4akkr,task_subcomment,NA
+"VisualEditor: Adding a link right before a wikilinked word leads to unexpected results, including a nowiki","This can be seen by placing the cursor right at the beginning of any existing wikilinked word, then trying to add any kind of link. 
+User's expectation is that this changes the wikilink target with no corruption.
+
+<<To reproduce this:
+* [https://fr.wikipedia.org/w/index.php?title=Boys_band&veaction=edit Edit Boys band on frwiki]
+* In the history chapter, 4th paragraph, put the cursor before the S of the link to Super Junior
+* Click on link icon in the toolbar
+* Copy the URL <code><nowiki>https://fr.wikipedia.org/wiki/B.A.P</nowiki></code> in the link inspector and click Terminé
+* When previewing modifications, you can see that it has been replaced by <code><nowiki>[[B.A.P]] [[Super Junior|<nowiki/>]][[B.A.P|Super]] Junior</nowiki></code> which shows several problems: there's a link without text displayed, the existing link has been cut in two
+* And also, what is displayed in VE doesn't match at all what the result will be when saved:
+** ""Super"" is displayed as an external link, but in the modifications preview, you see it's an internal link
+** If you hover over ""Super"", both ""Super"" and ""Junior"" get underlined, but in the modifications preview, ""Junior"" is not inside the link
+** ""Junior"" is displayed as an internal link, but in the modifications preview, you see it's now just text
+** If you hover over ""Junior"", both ""Super"" and ""Junior"" get underlined, but in the modifications preview, ""Junior"" is not inside a link .>> Instructions by NicoV.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409660820,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-d2yxda424o7uk6liddmf,task_description,resolved
+"VisualEditor: Adding a link right before a wikilinked word leads to unexpected results, including a nowiki",Resolved with this: https://gerrit.wikimedia.org/r/#/c/197425,1426638000,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-d2yxda424o7uk6liddmf,task_subcomment,NA
+"VisualEditor: Adding a link right before a wikilinked word leads to unexpected results, including a nowiki",The root cause here is very odd; I've opened {T86399} to work this out.,1420861251,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d2yxda424o7uk6liddmf,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,"The qqq documentation for the message Visualeditor-dialog-action-done is either misleading or I misunderstand it :)
+
+It says: ""Label text for button to exit from a dialog that has no changes to make.""
+
+However, this message is used in the link inspector - this is not quite a dialog, and it does make changes.
+
+I can think of three options:
+* I misunderstand something :)
+* This message shouldn't be used in the link inspector
+* This message's documentation should be changed
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409645820,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_description,resolved
+Documentation for the message Visualeditor-dialog-action-done is misleading,"Change 184642 merged by jenkins-bot:
+Create separate message for find-and-replace-done
+
+[[https://gerrit.wikimedia.org/r/184642]]",1421165213,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,I think this is just a copy and paste error from visualeditor-dialog-action-cancel,1421163995,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,"Change 184642 had a related patch set uploaded (by Esanders):
+Create separate message for find-and-replace-done
+
+[[https://gerrit.wikimedia.org/r/184642]]
+
+#patch-for-review",1421163926,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,"After reading @Jdforrester-WMF's reasoning on T85852 I am even more convinced that this is a problem.
+
+UI consistency is a good idea, but enforcing too much of it is not. In particular, reusing the same message in several different dialogs is a bad idea. See
+https://www.mediawiki.org/wiki/Localisation#Avoid_message_reuse
+
+""Done"" is used now in several contexts that may seem similar to developers, but are not actually the same. In Russian and Hebrew it's definitely wrong to apply the same message too all these different dialogs. As the localisation guide says, this may seem counter-intuitive, but it is also based on a lot of experience.",1420568195,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,"... This caused T85852.
+
+""Done"" just doesn't sound like a button in a dialog that has no changes to make.",1420491504,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"Just discovered this tool, and since it makes it so much easier to add TemplateData, it would be a huge improvement for us template editors, and consequently for the VisualEditor users out there. Can't see any reason it should be controversial, but if requested I'll bring it up in our village pump.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1409430780,PHID-USER-jqjb54lbf7psat6shbcc,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_description,resolved
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,Merged and deployed!,1409671057,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"**gerritadmin** wrote:
+
+Change 157476 merged by jenkins-bot:
+Enable TemplateData GUI on Norwegian Bokmål (nowiki)
+
+https://gerrit.wikimedia.org/r/157476",1409670702,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"Start to involve the projects in the decision process, or at least don't try to override existing processes. This request does _NOT_ follow due process and will interfere with the project own decision.
+
+Why does it seem like I always repeat myself.. ;/",1409566750,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"(In reply to jeblad from comment #5)
+> There is no consensus at WP:Tinget, and that would usually take at least a
+> week. There is a notice about this at WP:Torget, but this page is not used
+> for project wide decisions at nowiki.
+
+This isn't really seeking a ""decision"", in the same way that most of the hundreds of improvements which are rolled out every week.
+
+> Before final consensus is reached all system messages should be translated
+
+Your input on https://translatewiki.net/w/i.php?title=Special:Translate&action=proofread&group=ext-templatedata&language=nb&filter=translated%7C%21reviewer%3A8576%7C%21last-translator%3A8576 is of course welcome in ensuring that. :-)
+
+> and necessary help pages created.
+
+Obviously you're not suggesting that WMF should interfere with a project and re-write their help pages here, I assume. :-)",1409525530,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"There is no consensus at WP:Tinget, and that would usually take at least a week. There is a notice about this at WP:Torget, but this page is not used for project wide decisions at nowiki.
+
+Before final consensus is reached all system messages should be translated and necessary help pages created. Only then should this be scheduled.
+
+In short, this request is invalid.",1409523675,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,Currently scheduled for 15:00 UTC on Tuesday 2 September; we can postpone it if there are an issues.,1409432185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"**gerritadmin** wrote:
+
+Change 157476 had a related patch set uploaded by Jforrester:
+Enable TemplateData GUI on Norwegian Bokmål (nowiki)
+
+https://gerrit.wikimedia.org/r/157476",1409431776,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"To be on the safe side I posted in our village pump asking if there are any objections:
+
+https://no.wikipedia.org/wiki/Wikipedia:Torget#.C2.ABManage_TemplateData.C2.BB",1409431332,PHID-USER-jqjb54lbf7psat6shbcc,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"Sure, no problem.",1409430901,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+VisualEditor Mobile: Performance issue with adding Citations in Mobile,There is a noticeable lag observed while trying to add any citation in mobile in Beta labs environment.,1409339820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jleaptwiihwbszn24ore,task_description,resolved
+VisualEditor Mobile: Performance issue with adding Citations in Mobile,Tested and performance is more than adequate on my iPhone.,1439257531,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jleaptwiihwbszn24ore,task_subcomment,NA
+VisualEditor: non-editable element inserted before a colon,"*Sorry about the lame summary*
+
+This bug can probably have a better title.
+
+A rather simple and innocent edit in the Hebrew Wikipedia introduced an element that had no reason to appear in the code. Here's the edit:
+https://he.wikipedia.org/w/index.php?title=%D7%9B%D7%99%D7%91%D7%95%D7%A9%D7%99_%D7%90%D7%9C%D7%9B%D7%A1%D7%A0%D7%93%D7%A8_%D7%94%D7%92%D7%93%D7%95%D7%9C_%D7%91%D7%90%D7%A1%D7%99%D7%94_%D7%94%D7%AA%D7%99%D7%9B%D7%95%D7%A0%D7%94&diff=15812721&oldid=15812716
+
+The problematic element appears between the words ""מטרות נוספות היו"" and the colon.
+
+The element was removed in the following edit:
+https://he.wikipedia.org/w/index.php?title=%D7%9B%D7%99%D7%91%D7%95%D7%A9%D7%99_%D7%90%D7%9C%D7%9B%D7%A1%D7%A0%D7%93%D7%A8_%D7%94%D7%92%D7%93%D7%95%D7%9C_%D7%91%D7%90%D7%A1%D7%99%D7%94_%D7%94%D7%AA%D7%99%D7%9B%D7%95%D7%A0%D7%94&diff=15887470&oldid=15878013
+
+When editing it in the VisualEditor, the element appears as ""Sorry, this element can only be edited in source mode for now.""
+
+When I showed this to David, he thought that it may be somewhat related to the ""unicorn"" patch, but it is not certain.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409312820,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dx53p7272wo7nmcymv63,task_description,open
+VisualEditor: non-editable element inserted before a colon,"Confirmed in betalabs - for en wiki too.
+- Insert a colon into a paragraph text and - Important!- put white spaces around it
+
+The colon (:) will be transformed into 
+```<span typeof=""mw:Placeholder"" data-parsoid=""{&quot;src&quot;:&quot; &quot;,&quot;isDisplayHack&quot;:true,&quot;dsr&quot;:[83,84,null,0]}"" class=""ve-ce-leafNode ve-ce-focusableNode"" contenteditable=""false"">&nbsp;</span> ```
+
+with
+
+```<div class=""ve-ce-focusableNode-highlight ve-ce-alienNode-highlight"" title=""Sorry, this element can only be edited in source mode for now."" draggable=""false"" style=""top: 11px; left: 391px; width: 5px; height: 15px;""><img class=""ve-ce-focusableNode-highlight-relocatable-marker"" src=""data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==""></div>```
+
+
+",1424302398,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dx53p7272wo7nmcymv63,task_subcomment,NA
+VisualEditor: wikitext warning doesn't auto-hide the first time you enter wikimarkup,"Verified with Chrome and Safari.
+If you type wikitext ( I tried with * ) and then delete it, the wikitext warning won't go away automatically.
+If you click on it to make it disappear, proceed to add more wikitext and delete this again, then the box will auto-hide correctly.
+
+(Two square parentheses don't seem to trigger the warning at all?)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51701",1409308440,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hzqhjjti55dwecogv2dm,task_description,resolved
+VisualEditor: wikitext warning doesn't auto-hide the first time you enter wikimarkup,"**gerritadmin** wrote:
+
+Change 157278 merged by jenkins-bot:
+Make sure mediawiki.notification is loaded -before- calling ViewPageTarget#checkForWikitextWarning
+
+https://gerrit.wikimedia.org/r/157278",1409343958,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hzqhjjti55dwecogv2dm,task_subcomment,NA
+VisualEditor: wikitext warning doesn't auto-hide the first time you enter wikimarkup,"**gerritadmin** wrote:
+
+Change 157278 had a related patch set uploaded by Alex Monk:
+Make sure mediawiki.notification is loaded -before- calling ViewPageTarget#checkForWikitextWarning
+
+https://gerrit.wikimedia.org/r/157278",1409343557,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hzqhjjti55dwecogv2dm,task_subcomment,NA
+VisualEditor: wikitext warning doesn't auto-hide the first time you enter wikimarkup,Taking this bug,1409342978,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hzqhjjti55dwecogv2dm,task_subcomment,NA
+VisualEditor: Applying a link to an invalid title triggers an undo,"1. Type some text which is an invalid title in MW, e.g. ""|InvalidTitle""
+2. Select it and hit link
+-  Notice that there are no suggestions, and no initial link is applied
+3. Type in a valid page name, e.g. ""Main page"" and press Done
+-  Notice some of your text has been deleted (by and undo operation) before the link was applied
+
+The bug is actually in core AnnotationInspector#getTeardownProcess. We call a surface undo() to remove the initial annotation, but in the case of an invalid title there is no initial annotation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409306340,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zznxlmtpisyv35ph3vdy,task_description,resolved
+VisualEditor: Applying a link to an invalid title triggers an undo,"**gerritadmin** wrote:
+
+Change 157053 merged by jenkins-bot:
+Only undo if an initial annotation was applied
+
+https://gerrit.wikimedia.org/r/157053",1409334982,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zznxlmtpisyv35ph3vdy,task_subcomment,NA
+VisualEditor: Applying a link to an invalid title triggers an undo,"**gerritadmin** wrote:
+
+Change 157053 had a related patch set uploaded by Esanders:
+Only undo if an initial annotation was applied
+
+https://gerrit.wikimedia.org/r/157053",1409307103,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zznxlmtpisyv35ph3vdy,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70744",1409239140,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-444jjina7afgsdohllry,task_description,resolved
+create browser test build for IE11/VisualEditor,"This build now exists at https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-windows_8.1-internet_explorer-11-sauce/
+
+Notice the rather nifty failure due to javascript error.",1410541891,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 157164 abandoned by Zfilipin:
+WIP Trying to create IE11 Jenkins job for VisualEditor
+
+Reason:
+moved to https://gerrit.wikimedia.org/r/#/c/160008/
+
+https://gerrit.wikimedia.org/r/157164",1410539112,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 157480 merged by jenkins-bot:
+browsertests: Enable VE on IE and Safari; remove Chrome on Windows XP
+
+https://gerrit.wikimedia.org/r/157480",1410037042,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 157164 had a related patch set uploaded by Zfilipin:
+WIP Trying to create IE11 Jenkins job for VisualEditor
+
+https://gerrit.wikimedia.org/r/157164",1409845273,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 156448 abandoned by Jforrester:
+browsertests: Enable VE on IE11 and Safari; remove Chrome on Windows XP
+
+Reason:
+Moved to master branch.
+
+https://gerrit.wikimedia.org/r/156448",1409433203,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 157480 had a related patch set uploaded by Jforrester:
+browsertests: Enable VE on IE11 and Safari; remove Chrome on Windows XP
+
+https://gerrit.wikimedia.org/r/157480",1409433190,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 156448 had a related patch set uploaded by Jforrester:
+browsertests: Enable VE on IE11 and Safari; remove Chrome on Windows XP
+
+https://gerrit.wikimedia.org/r/156448",1409240289,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Education Programme:
+> On page
+> https://pt.wikipedia.org/wiki/User:Alpha_Centaurus?veaction=edit&oldid=39924153&uselang=en
+> the link to
+> https://pt.wikipedia.org/wiki/Ensino:Universidade_Federal_do_Rio_Grande_do_Sul/C%C3%A1lculo_Num%C3%A9rico_%28MAT01169%29_%282014-2%29
+> is red, but it should be blue because (from the user's point of view) the page exists.
+
+GlobalUserPages:
+> Viewing https://www.mediawiki.org/wiki/Extension:TemplateData shows a blue link for ""James Forrester"". However, when editing with VisualEditor, the link is red.
+
+
+----
+See also: {T134073}",1409234640,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-kfwpka7h3inptj65moc2,task_description,resolved
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Change 315432 merged by jenkins-bot:
+mw.LinkCache: Links aren't missing if they're known
+
+[[https://gerrit.wikimedia.org/r/315432]]",1476319929,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Change 315455 merged by jenkins-bot:
+TitleWidget: Take 'known' status into account when deciding page existence
+
+[[https://gerrit.wikimedia.org/r/315455]]",1476316894,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Change 315455 had a related patch set uploaded (by Alex Monk):
+TitleWidget: Take 'known' status into account when deciding page existence
+
+[[https://gerrit.wikimedia.org/r/315455]]
+",1476234312,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Change 315432 had a related patch set uploaded (by Jforrester):
+mw.LinkCache: Links aren't missing if they're known
+
+[[https://gerrit.wikimedia.org/r/315432]]
+",1476222686,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","I filed a blocker bug to expose Title::isKnown() via the API, so VE can use it.
+
+Once that is in place, someone will need to update `ve.init.mw.LinkCache` to use it.",1470208154,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Extension:WikimediaIncubator also uses this hook so ""Valid Wx/xyz info pages should be considered as existing pages"". SemanticMediaWiki also uses it for something.
+
+There are other issues due to Title::isAlwaysKnown that aren't just the TitleIsAlwaysKnown hook - existence of files vs. file pages, and existence of system messages.",1425697754,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Unfortunately, that page doesn't actually exist. EducationProgram just pretends it does via the hook I mentioned in T72504#942697.",1419537917,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Tap somewhere in the middle of the page or towards the end
+
+Observed Result:
+The page focus bumps up to the top of the page, not getting scrolled down to the point where the cursor is actually positioned.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409181600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szhrrt6yhyfzihjpjade,task_description,resolved
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"**jgonera** wrote:
+
+Maryana said that she doesn't consider that very high priority so I might not get to it before I leave. Unassigning myself.",1409264628,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"**jgonera** wrote:
+
+Correction: the page doesn't scroll up. It should scroll up when the keyboard opens and covers up the cursor. Instead, the page stays in place.
+
+This is because we no longer scroll the whole page on iOS (we scroll inside of a div) and Safari's default mechanism for preventing the cursor from being covered by the keyboard doesn't work anymore (that's my guess).
+
+I think an easy solution would be to implement scrolling the CE on focus in such a way that the cursor ends up being close to the top of the screen. This way the keyboard won't occult it. We have to keep in mind though that this code should only run on iOS (which is easy because we already let MobileViewTarget know that we're on iOS using isIos config argument).",1409260466,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"The page scrolls up, the cursor is correctly positioned with the fix of https://bugzilla.wikimedia.org/show_bug.cgi?id=66697",1409182967,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"**jgonera** wrote:
+
+""The page focus bumps up to the top of the page"" - you mean the page is scrolled to the top or the cursor moves to the top?",1409182819,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Click on ""Show Options""
+4.Add the template ""Cite Web""
+5.Select one of those required parameter from the left panel of the dialog
+6.Add some more template with some optional parameters and content in the transclusion dialog
+7.Now select one of the required parameter for the ""Cite Web"" template from the left panel
+8.Now from left panel,select any other template/optional parameter/content or even the ""Cite web"" template 
+
+Observe that the trash icon that used to appear at the corner of the left panel for other template/optional parameter/content or ""Cite web"" template are not appearing now.
+
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14309}",1409168760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5azsp7uzzucqdg6yukh3,task_description,resolved
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,Verified the fix in production,1409865667,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,Verified the fix in test2,1409260092,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,Verified the fix in Betalabs,1409178636,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,"Change 156671 merged by jenkins-bot:
+Toggle trash button (on transclusion dialog) visibility when changing to non-parameter pages
+
+https://gerrit.wikimedia.org/r/156671",1409174915,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,"Change 156671 had a related patch set uploaded by Alex Monk:
+Toggle trash button (on transclusion dialog) visibility when changing to non-parameter pages
+
+https://gerrit.wikimedia.org/r/156671",1409169644,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,"Created attachment 16297
+The missing trash icon
+
+**Attached**: {F14310}",1409168921,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Steps to reproduce:
+
+1.  Open page containing the {{good article}} (or similar) template in VisualEditor, such as https://en.wikipedia.org/w/index.php?oldid=622810787 (which contains only that template)
+
+2.  Click the good article icon/template
+
+3.  VisualEditor exits, and you are reading the Wikipedia:Good article page (the same one that you would be reading if you clicked that icon in 'read' mode).
+
+
+Expected behavior:
+
+1.  Open page containing {{good article}} in VisualEditor
+
+2.  Click the good article icon/template
+
+3.  Edit the template just like any other.
+
+
+It's possible that this can only be reproduced on Windows, because on my Mac, when I open the page, the template isn't even visible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409099760,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-z2d3f6p2ejg2badg7nph,task_description,resolved
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Change 161957 merged by jenkins-bot:
+Prevent page elements from displaying on top of highlights
+
+https://gerrit.wikimedia.org/r/161957",1411509996,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Ed, that's bug 23796, with the related bug 51420 in VE.",1411399971,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Change 161957 had a related patch set uploaded by Bartosz Dziewoński:
+Prevent page elements from displaying on top of highlights
+
+https://gerrit.wikimedia.org/r/161957",1411399800,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Setting topicons with CSS like this is a horrible hack. Imagine if we did the same with category links!
+
+We should create a simple extension to add topicons to a page, so that they are rendered in the correct place in the HTML (i.e. not the article body). Parsoid can then provide them to VE as metadata and we can handle them accordingly.
+
+I've discussed this with Trevor and Roan and we think it's a fairly simple project to take on.",1411399687,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","While this could possibly be fixed on-wiki for this particular case, we should prevent people from accidentally or intentionally breaking this in VE, too.",1411398987,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Caused by ""z-index: 10;"" in [[w:en:MediaWiki:Monobook.css]].",1411398593,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","It was reported on Firefox 31 on Windows 7, using Monobook.
+
+There's a screenshot at https://commons.wikimedia.org/wiki/File:VE_with_GA_icon.png",1409152635,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia",Which browsers are you using ?,1409132291,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Take this query from the suggester:
+
+https://en.wikipedia.org/w/api.php?format=jsonfm&uselang=en&action=query&list=allcategories&acprefix=1895+es&acprop=hidden&redirects=
+
+Now read [[mw:Manual:Category table]]:
+""Track all existing categories. Something is a category if it has an entry somewhere in categorylinks, or it once did.""
+
+So it's logical that something like 1895 establisANONYMOUS IS LEGIONhments is in the suggestion list, but it is really not desirable. It contains many 'bad' words and deleted stuff that we don't really want to present to users.
+
+
+https://en.wikipedia.org/w/api.php?format=jsonfm&uselang=en&action=query&list=allcategories&acprefix=1895+es&acprop=hidden&redirects=&acprop=size|hidden
+
+This can be easily solved by adding:
+acmin=1 to the query.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1409044020,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fypqepsh6l776gwf6e2h,task_description,resolved
+VisualEditor: Category suggestion lists no longer existing categories,*** Bug 69927 has been marked as a duplicate of this bug. ***,1409094378,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Actually, i forgot, HotCat now actually runs 2 queries on both of these tables, and then combines them into a result..
+
+
+Perhaps we should fix the api ? :)",1409083278,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Change 156250 merged by jenkins-bot:
+Categories: Don't suggest empty or old categories
+
+https://gerrit.wikimedia.org/r/156250",1409083244,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Alternative is to use the HotCat methodology:
+
+Here only categories that have their own page are considered to exist:
+https://en.wikipedia.org/w/api.php?format=json&action=query&list=allpages&apnamespace=14&aplimit=30&apfrom=1895%20es&apprefix=1895%20es",1409083001,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Change 156250 had a related patch set uploaded by TheDJ:
+Categories: Don't suggest empty or old categories
+
+https://gerrit.wikimedia.org/r/156250",1409045158,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"Reference dialog in test2
+
+The size of the Reference dialog got changed to a bigger size after wmf18
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70601
+
+**Attached**: {F14691}",1409012040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e532vezhqz47vwem7t6o,task_description,resolved
+VisualEditor: Shrink back the Basic Reference dialog size,*** Bug 70601 has been marked as a duplicate of this bug. ***,1414137121,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,Verified the fix in production,1411681864,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,Verified the fix in test2,1411083546,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"**gerritadmin** wrote:
+
+Change 161165 merged by jenkins-bot:
+Fix automatic sizing of windows
+
+https://gerrit.wikimedia.org/r/161165",1411065126,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"**gerritadmin** wrote:
+
+Change 161165 had a related patch set uploaded by Catrope:
+Fix automatic sizing of windows
+
+https://gerrit.wikimedia.org/r/161165",1411012487,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"Many other dialogs have this problem too, including referenceList. It looks like getBodyHeight() is returning a value that's way too high.",1409680874,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"Created attachment 16279
+Reference dialog in production
+
+**Attached**: {F14692}",1409012100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1409011560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-advminout52vzy4o576h,task_description,resolved
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,Verified the fix in Production,1410545808,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,So the first patch set I made (to deal with existing links when you clear the target page) should be deployed to all Wikimedia wikis. But the second one (per Rummana's comment 4) was merged a day later which just happened to put it on the next deployment version (so it should be another week).,1409869692,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,I just tested this on MediaWiki.org and it seems to have been fixed. . .,1409869210,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"Again in production, the ""open"" button remains enabled when I open a link inspector in a blank line without selecting a text.I will wait for a while to see whether it gets started working automatically like it did in Betalabs.Reopening it for now.",1409865004,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"Yeah, just started working for me! Marking as Resolved .",1409347795,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,Works for me. Gerrit change 157212 should've sent my fix to beta labs.,1409347253,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"Created attachment 16315
+Screenshot
+
+hmm..but I still see that button as active :/
+
+**Attached**: {F14688}",1409345516,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"I uploaded Gerrit change 157017 to resolve that issue, and Roan just merged it. I forgot to link it to this bug, sorry!",1409272184,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"The ""Open"" button is now getting disabled when you clear the link target name , but if you just open the link inspector in any empty line and there is no link target name specified yet , the ""Open"" button still remains enabled",1409259547,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"**gerritadmin** wrote:
+
+Change 156582 merged by jenkins-bot:
+Link target input widget: Make '' an invalid link target
+
+https://gerrit.wikimedia.org/r/156582",1409184286,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"**gerritadmin** wrote:
+
+Change 156582 had a related patch set uploaded by Alex Monk:
+Link target input widget: Make '' an invalid link target
+
+https://gerrit.wikimedia.org/r/156582",1409160980,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"Right now, when you open link inspector and keep the link target field empty, you will still be able to click on ""Open"" button as it remains active, though it serves no purpose.We should disable it in this case",1409011737,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor:  Category names are taking long time (~6-7 secs)to appear in the Category section,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add some categories to the page
+3.Save the page
+4.Reopen the page and go to the categories section
+
+Observed Result:
+The categories are not appearing immediately,after waiting for approx. 6-7 secs they do appear in that section.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409009400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ic44hmdblr4rvvctpw5r,task_description,resolved
+VisualEditor:  Category names are taking long time (~6-7 secs)to appear in the Category section,This was happening because of HHVM issue. Now it is working fine.,1409011011,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ic44hmdblr4rvvctpw5r,task_subcomment,NA
+"VisualEditor:  {{#tag:ref}} is not processed by VisualEditor, so the references list claims that there are no refs in that group","This may be related to bug 51289 and bug 61777.
+
+
+Steps to reproduce:
+
+1.  Open a page that contains refs formatted like this:  {{#tag:ref|Text goes here. |group=n |name=Foo}}
+
+2.  Add a references list for the group.
+
+3.  Read the error message.  VisualEditor says that there are no refs in group 'n' on the page.
+
+
+Expectation:
+
+Refs would be properly recognized and displayed even if they use this rather odd format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409008680,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6fjxmlk42cz5vwd46onb,task_description,open
+VisualEditor: The article Sindhi language cannot be edited in VE if the Language tool is enabled,"Trying to edit the article [[Sindhi language]] in VE while the language tool is enabled produces gets the browser stuck with the animated loading bar and produces a JavaScript error in the console:
+Uncaught TypeError: Cannot read property 'toLowerCase' of null ve.ce.LanguageAnnotation.js:52
+
+(This is from Chrome; the error in Firefox is slightly different, but it's broken there as well.)
+
+If the language tool beta feature is disabled, then the article can be edited.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408870740,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-bdmcqwt76vyccvojptxl,task_description,resolved
+VisualEditor: The article Sindhi language cannot be edited in VE if the Language tool is enabled,"Change 156143 merged by jenkins-bot:
+Fix JS error in ce.LanguageAnnotation when dir is set but lang isn't
+
+https://gerrit.wikimedia.org/r/156143",1408987293,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bdmcqwt76vyccvojptxl,task_subcomment,NA
+VisualEditor: The article Sindhi language cannot be edited in VE if the Language tool is enabled,"Change 156143 had a related patch set uploaded by Catrope:
+Fix JS error in ce.LanguageAnnotation when dir is set but lang isn't
+
+https://gerrit.wikimedia.org/r/156143",1408985963,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bdmcqwt76vyccvojptxl,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"Sometimes you want a single quotation mark next to an italicized (or bolded) word. 
+It would be nice if VisualEditor/Parsoid did something elegant with the wikitext, like ""celui d'<nowiki/>''Homo sapiens''"" instead of wrapping half a sentence inside nowiki tags to deal with a single character.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408839360,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-nk4g5ukj6fdtvpowneko,task_description,resolved
+Improve nowiki additions to only wrap the string that needs protection,"Change 193842 merged by jenkins-bot:
+T71950: Output <nowiki> closer to quotes
+
+[[https://gerrit.wikimedia.org/r/193842]]",1425925165,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"> [[https://gerrit.wikimedia.org/r/193842]]
+
+This is a WIP that should fix the https://fr.wikipedia.org/w/index.php?title=Grand_Line&curid=4571652&diff=111992974&oldid=111360543 case, but I want to make sure it doesn't break anything else.",1425315475,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"Change 193842 had a related patch set uploaded (by Marcoil):
+WIP: T71950: Output <nowiki> closer to actual reason
+
+[[https://gerrit.wikimedia.org/r/193842]]
+",1425315346,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"nowiki addition for quotes has improved since this ticket was created. We should investigate what needs fixing here. But, one recent diff that could be investigated (as reported by @NicoV) is https://fr.wikipedia.org/w/index.php?title=Grand_Line&curid=4571652&diff=111992974&oldid=111360543",1424538050,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"See https://fr.wikipedia.org/w/index.php?title=La_Horde_sauvage_(film,_1969)&curid=88578&diff=106771550&oldid=106771188
+
+https://fr.wikipedia.org/w/index.php?title=Archelon&curid=1273494&diff=106770342&oldid=105728402
+
+If in a long string, only a single small piece of it needs nowiki-ing, that single string can be wrapped. In general, this requires knowing that nothing else in the long string needs a nowiki wrapper, but heuristics could work for common scenarios. This seems to be a problem that affects frwiki especially.",1408998537,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","This might be related to Bug 49524.
+
+See https://commons.wikimedia.org/wiki/File:VE_selection_box_goes_over_menus.png
+
+When you open https://en.wikipedia.org/w/index.php?oldid=620028233 in Firefox on Windows 7, the sandbox template is autoselected.  If you click on a menu (e.g., to set bold text), the menu drops down but the items that overlap with the auto-selected template can't be chosen.
+
+I am unable to reproduce this in either Safari or Firefox on a Mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408839060,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-utuehsjkuc2a6rnd6nid,task_description,resolved
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","Change 156723 merged by jenkins-bot:
+Fix various bugs in our Monobook stylesheet
+
+https://gerrit.wikimedia.org/r/156723",1409247823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-utuehsjkuc2a6rnd6nid,task_subcomment,NA
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","Change 156723 had a related patch set uploaded by Catrope:
+Fix various bugs in our Monobook stylesheet
+
+https://gerrit.wikimedia.org/r/156723",1409181526,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-utuehsjkuc2a6rnd6nid,task_subcomment,NA
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","I couldn't reproduce this bug, and realized it was specific to Monobook. There are other minor display issues with the toolbar in Monobook as well (like its height).",1409177114,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-utuehsjkuc2a6rnd6nid,task_subcomment,NA
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","This appears to only happen if you are at the top of the page.  If you scroll down at all, then it works correctly.",1409007413,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-utuehsjkuc2a6rnd6nid,task_subcomment,NA
+Enable DOM editing of transclusion parameters,"This is needed to allow VisualEditor to support such lovely wikitext as {{echo|{{echo|Foo!}}}} and more complex variations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408649880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-djmwv2eookrt5vpvsei5,task_description,open
+Enable DOM editing of transclusion parameters,"A different approach that we have considered over the last few months is to generate these HTML representation of tpl params on demand rather than for Parsoid to generate this all the time and then store it.
+
+So, whenever a template is opened up for editing in VE, VE would request Parsoid for HTML representation of these parameters, and then use that to enabled HTML editing of these params. If  this is considered a workable approach, we can work out the details and this can see the light of day much faster.",1448296086,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-djmwv2eookrt5vpvsei5,task_subcomment,NA
+Enable DOM editing of transclusion parameters,"(In reply to Marc Ordinas i Llopis from comment #1)
+> With this enabled, it's possible to make Parsoid accept new transclusion
+> parameters from HTML by removing the wt ones. We are also planning on adding
+> support for detecting changes in parameters (so that the wikitext ones don't
+> have to be removed) in the future.
+
+That sounds great.
+
+> I'll be working on improving performance shortly.
+
+Excellent. :-)",1409067257,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-djmwv2eookrt5vpvsei5,task_subcomment,NA
+Enable DOM editing of transclusion parameters,"The current status for DOM transclusion parameters is: The code is there, but it is disabled by default as it affects performance. For example, it increases the rendering of [[Barack_Obama]] by more than 3s.
+
+To enable it (in case someone wants to try it out), add
+parsoidConfig.addHTMLTemplateParameters = true;
+to localsettings.js.
+
+With this enabled, it's possible to make Parsoid accept new transclusion parameters from HTML by removing the wt ones. We are also planning on adding support for detecting changes in parameters (so that the wikitext ones don't have to be removed) in the future.
+
+I'll be working on improving performance shortly.",1409047482,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-djmwv2eookrt5vpvsei5,task_subcomment,NA
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,"Save button not working after creating citation
+
+After fixing https://bugzilla.wikimedia.org/show_bug.cgi?id=69856
+
+Do everything to create a Citation as shown in the screen shot. 
+
+Click Save. Save does nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14354}",1408645140,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_description,resolved
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,Verified the fix in production,1409866397,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_subcomment,NA
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,"**gerritadmin** wrote:
+
+Change 155601 merged by jenkins-bot:
+Followup 67f304a: use .openWindow(), not .open(), to open save dialog
+
+https://gerrit.wikimedia.org/r/155601",1408664848,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_subcomment,NA
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,"**gerritadmin** wrote:
+
+Change 155601 had a related patch set uploaded by Jforrester:
+Followup 67f304a: use .openWindow(), not .open(), to open save dialog
+
+https://gerrit.wikimedia.org/r/155601",1408648658,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_subcomment,NA
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,"This happens while trying to save a page after adding anything in the page, not just citations.The error that appears in the console is:
+Uncaught TypeError: Cannot read property 'openWindow' of null",1408647243,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_subcomment,NA
+VisualEditor shows double page title after edit when 'edittop' gaget (or similar) is enabled,"Screenshot
+
+VisualEditor shows double page title after edit when the 'edittop' gaget (or similar) is enabled.
+
+This is because the code to update page's DISPLAYTITLE is too aggressive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14331}",1408638660,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2lh4x2ggoyfra3mal2dj,task_description,resolved
+VisualEditor shows double page title after edit when 'edittop' gaget (or similar) is enabled,"Change 155577 merged by jenkins-bot:
+mw.ViewPageTarget: Be more careful when updating page title
+
+https://gerrit.wikimedia.org/r/155577",1408642051,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2lh4x2ggoyfra3mal2dj,task_subcomment,NA
+VisualEditor shows double page title after edit when 'edittop' gaget (or similar) is enabled,"Change 155577 had a related patch set uploaded by Bartosz Dziewoński:
+mw.ViewPageTarget: Be more careful when updating page title
+
+https://gerrit.wikimedia.org/r/155577",1408639000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2lh4x2ggoyfra3mal2dj,task_subcomment,NA
+"VisualEditor: Reinstate the semantic class on the ""Save page"" button","The firsteditve tour (the ""first edit"" tour, specialised for VE) relied on the ve-ui-toolbar-saveButton class to attach a guider to the ""Save page"" toolbar button. The class was removed as part of https://git.wikimedia.org/commit/mediawiki%2Fextensions%2FVisualEditor.git/cc089d6bd3334791453c6474c56f49d4a2d243dd.
+
+At the moment, there's no resilient selector that we can use to reference just that element. Can the class be reinstated?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1408547940,PHID-USER-w3pd7vqenmta6vpmhwcn,PHID-TASK-5djpuvo4wkwj32snxeof,task_description,resolved
+"VisualEditor: Reinstate the semantic class on the ""Save page"" button","**gerritadmin** wrote:
+
+Change 155280 merged by jenkins-bot:
+Reinstate the ve-ui-toolbar-saveButton class
+
+https://gerrit.wikimedia.org/r/155280",1408553307,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5djpuvo4wkwj32snxeof,task_subcomment,NA
+"VisualEditor: Reinstate the semantic class on the ""Save page"" button","**gerritadmin** wrote:
+
+Change 155280 had a related patch set uploaded by Phuedx:
+Reinstate the ve-ui-toolbar-saveButton class
+
+https://gerrit.wikimedia.org/r/155280",1408549473,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5djpuvo4wkwj32snxeof,task_subcomment,NA
+"Search results (for links, redirects, categories…) should select the exact match by default","This is somewhat related to {T64917}.
+
+When you add an internal link, or otherwise are looking at search results, VisualEditor should defaultly select any page that is an exact match for what you've typed.  In particular, if you search for ""Computer"", and there actually is a page at [[Computer]], then it should default to [[Computer]], not to [[Computer science]] or whatever else comes up first in the search system.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T71780}
+{T57390}
+{T64917}
+{T71716}",1408396020,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6rg4t2epelfvjth52scv,task_description,resolved
+"Search results (for links, redirects, categories…) should select the exact match by default","Current situation:
+
+* If you type ""fool"" and press return or click ""Insert"" you get a link to ""fool"", even if it doesn't appear in the suggestions list.
+* If you type ""fool"" and there are no title matches, you'll get what you've typed in as a redlink suggestion.
+* If you type ""fool"" and the only title match result is ""Fool's gold"" as a redirect to ""Pyrite"", you'll get the latter shown first with the former directly below it. You won't get a redlink suggestion.
+* If you type ""fool"" and there are several title match results, the ""best"" match from the search engine will show first even if that isn't the closest match.
+
+I think this is ""good enough"", and much better than when this task was filed.",1490394554,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6rg4t2epelfvjth52scv,task_subcomment,NA
+"Search results (for links, redirects, categories…) should select the exact match by default","This is aggravated if the exact match is a redirect, because matching redirects are in a separate section of the suggester, and the auto select only considers the first match in the 'articles' section of the suggester.
+
+
+When trying to link to the en.wp redirect ""Republic of Vietnam"" by typing this directly into the link dialog, the article ""Republic of Vietnam Airborne Division"" is selected. Ideally, as I type, I would expect that the exact redirect match of ""Republic of Vietnam is chosen and that after done, I get: [[Republic_of_Vietnam_Airborne_Division|Republic of Vietnam]].",1408402286,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-6rg4t2epelfvjth52scv,task_subcomment,NA
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation","I get ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation. This is rather insidious, as the error only happens when trying to save the page, which causes you to lose some work. (The same error happens when trying to switch to wikitext.)
+
+1. https://en.wikipedia.org/wiki/Combining_Grapheme_Joiner?veaction=edit
+2. Click the ""[1]"" link in the first paragraph, ""Add label"" from inspector
+3. Ctrl+X to cut the link (which should have been automatically selected)
+4. Click ""Cite"" → ""Basic"" to insert citation at the same spot
+5. Ctrl+V to paste the link, ""Insert reference""
+6. Click ""Save page"", receive error
+
+I'm not sure if step 2 is relevant, but I can consistently reproduce like this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1408381140,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_description,resolved
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation","Indeed, works for me too now.",1414051086,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_subcomment,NA
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation","I just followed these steps exactly (I opened the save dialog and viewed the diff, but did not actually change the content) and it worked fine. FIXED, or am I missing something?",1414008955,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_subcomment,NA
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation","(In reply to marielle.volz from comment #1)
+> I ca
+Whoops. Premature enter there.
+
+I can confirm, but in my case upon inserting the reference, I can no longer open any dialogs, including the citation dialog, nor the save dialog (i.e. when I hit save, nothing happens.)",1408381949,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_subcomment,NA
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation",I ca,1408381693,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Let's stop using inline <img> for thumbnail magnify icon. According to bug 69277 comment 11, there are 87619775 requests per day for 'magnify-clip.png'. It should be embedded in some piece of CSS.
+
+(Bug 65160 / [[mw:Thumbnail style update]] call for complete removal of the icon, but it would only affect the Vector skin.)
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: normal",1408301100,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2a4evartaeoqgwykf6un,task_description,resolved
+Stop using inline <img> for thumbnail magnify icon,"Change 161625 merged by jenkins-bot:
+Remove WMF deployment hack for 'Enlarge' image
+
+https://gerrit.wikimedia.org/r/161625",1411169229,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 154831 merged by jenkins-bot:
+Remove WMF deployment hack for 'Enlarge' image
+
+https://gerrit.wikimedia.org/r/154831",1411168756,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 161625 had a related patch set uploaded by Jforrester:
+Remove WMF deployment hack for 'Enlarge' image
+
+https://gerrit.wikimedia.org/r/161625",1411168341,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Deeming this merged now, as this is 'fixed' even without the clean-up from gerrit 154831 landing.",1408492493,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 154830 merged by jenkins-bot:
+Generate 'Enlarge' image in CSS rather than HTML (Linker)
+
+https://gerrit.wikimedia.org/r/154830",1408492283,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 154831 had a related patch set uploaded by Bartosz Dziewoński:
+Remove WMF deployment hack for 'Enlarge' image
+
+https://gerrit.wikimedia.org/r/154831",1408375536,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 154830 had a related patch set uploaded by Bartosz Dziewoński:
+Generate 'Enlarge' image in CSS rather than HTML (Linker)
+
+https://gerrit.wikimedia.org/r/154830",1408375531,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"(In reply to Bartosz Dziewoński from comment #0)
+> Let's stop using inline <img> for thumbnail magnify icon. According to bug
+> 69277 comment 11, there are 87619775 requests per day for
+> 'magnify-clip.png'. It should be embedded in some piece of CSS.
+> 
+> (Bug 65160 / [[mw:Thumbnail style update]] call for complete removal of the
+> icon, but it would only affect the Vector skin.)
+
+Makes sense to me.",1408314957,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"(In reply to James Forrester from comment #2)
+> At this point this artefact would become a Monobook-only item, right? Should
+> it be moved to that repo at that point?
+
+No, it would become every-skin-but-Vector-including-custom-skins-only item.
+
+
+> VisualEditor only uses it through mediawiki.content.styling.parsoid
+
+It is also used in ve.ce.MWImageCaptionNode.js via 'magnifyClipIconURL' config item.",1408310707,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"(In reply to Bartosz Dziewoński from comment #0)
+> (Bug 65160 / [[mw:Thumbnail style update]] call for complete removal of the
+> icon, but it would only affect the Vector skin.)
+
+At this point this artefact would become a Monobook-only item, right? Should it be moved to that repo at that point?
+
+(In reply to Bartosz Dziewoński from comment #1)
+> A number of extensions also refer to this file directly, including
+> VisualEditor and WikiEditor. These will need to be updated.
+
+VisualEditor only uses it through mediawiki.content.styling.parsoid (faked Vector-like content rendering; yes yes, I know…), which should be fixed as the fixing for bug 65160.",1408310491,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"A number of extensions also refer to this file directly, including VisualEditor and WikiEditor. These will need to be updated.
+
+There are probably also innumerable user scripts that refer to it. Looking at bug 69277 comment 10, the Popups gadget is a big offender.",1408301230,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+VisualEditor Mobile: tapping into middle of link inspector text causes lots of issues,"Steps to repro:
+
+1. In prod/stable on iPad, enter VE edit mode and tap on a 2-word wikilink (e.g. [[European robin]])
+2. Open link inspector
+3. Tap on the end of the second word (e.g., after ""European"") to drop cursor between the two words
+4. Attempt to backspace and enter new text
+
+I've seen a number of weird things happen after this step:
+
+* No suggestions come up in the drop-down, even when there clearly should be some
+* Adding new text or spaces is impossible; you can only backspace
+* Backspacing too fast closes the dialog (known issue) or crashes Safari (not sure if known issue)
+
+None of these seem to happen if you tap at the end of the text in the link inspector (e.g., after ""robin"") and backspace/add new text from there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408053060,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-e5hoozp2bm6dugby2g2l,task_description,resolved
+VisualEditor Mobile: tapping into middle of link inspector text causes lots of issues,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487324,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e5hoozp2bm6dugby2g2l,task_subcomment,NA
+VisualEditor Mobile: tapping into middle of link inspector text causes lots of issues,"Sorry, that should be:
+
+3. Tap on the end of the FIRST word (e.g., after ""European"")",1408053162,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-e5hoozp2bm6dugby2g2l,task_subcomment,NA
+VisualEditor:  Category input box is too small (sometimes),"Steps to reproduce:
+
+1.  Add a short category or three.  (At en.wp, you can add Category:1, Category:2, and Category:3, etc.)  The box for adding the next cat should still be on the same (first) line.
+
+2.  Now try to add a very long category name.  If you're on Meta, try Category:Association of Wikipedians - AWWDMBJAWGCAWAIFDSPBATDMTD
+
+
+Result:  
+
+The search field pops up, but you can't really see much of it.  In particular, unless what you're trying to add can be reliably added from the first and last few characters, then you might add the wrong category.
+
+
+Expectation:  
+
+The category field will be wide enough to see what's in the search list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57200",1408050900,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-l5v5vrwex3hz2ct4owi2,task_description,duplicate
+VisualEditor:  Category input box is too small (sometimes),[[ https://www.mediawiki.org/wiki/Topic:T8cllr8xqawliza4 | We got a new report about this from Ziko. ]],1470321534,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-l5v5vrwex3hz2ct4owi2,task_subcomment,NA
+VisualEditor:  Category input box is too small (sometimes),*** Bug 71657 has been marked as a duplicate of this bug. ***,1414086378,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-l5v5vrwex3hz2ct4owi2,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots. Without this all the screenshots in these languages show squares instead of the correct characters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408020900,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_description,resolved
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"I'm closing this. Installing fonts in the future should be simple enough... I think :)
+
+Thanks a lot for the help!",1412025554,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,Amir can we close this bug or maybe we can keep it open to track the installation of fonts for all the other languages?,1412017255,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162869 merged by jenkins-bot:
+Running language screenshot job using local Firefox
+
+https://gerrit.wikimedia.org/r/162869",1412002045,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162869 had a related patch set uploaded by Zfilipin:
+Running language screenshot job using local Firefox
+
+https://gerrit.wikimedia.org/r/162869",1411648144,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162604 merged by Filippo Giunchedi:
+contint: labs slaves +mediawiki::packages::fonts
+
+https://gerrit.wikimedia.org/r/162604",1411642949,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Thanks Antoine, screenshots are fine now! :)",1411574356,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"I have installed the puppet patch on all jenkins instances:
+
+Info: Applying configuration version '1411572497'
+Notice: /Stage[first]/Apt::Update/Exec[/usr/bin/apt-get update]/returns: executed successfully
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-tamil-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-takao-mincho]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-75dpi]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-liberation]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-100dpi]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-ubuntu-font-family]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-lyx]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-punjabi-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-ezra]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-kochi-gothic]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[culmus-fancy]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-nuosusil]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-lklug-sinhala]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-wqy-zenhei]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-takao-gothic]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-mgopen]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-arphic-uming]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[culmus]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-malayalam-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-vlgothic]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-gujarati-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-lao]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-telugu-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-kannada-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-unfonts-extra]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-oriya-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-linuxlibertine]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-mplus]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-abyssinica]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-thai-tlwg]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-scheherazade]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-arphic-ukai]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-padauk]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-bengali-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-kacst]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-khmeros]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-kochi-mincho]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-tibetan-machine]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-nafees]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-manchufont]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-base]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-devanagari-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Apt::Noupgrade/Package[update-manager-core]/ensure: removed
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-dejavu-extra]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-farsiweb]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-arabeyes]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-alee]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-scalable]/ensure: ensure changed 'purged' to 'present'
+Notice: Finished catalog run in 636.32 seconds",1411573386,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162604 had a related patch set uploaded by Hashar:
+contint: labs slaves +mediawiki::packages::fonts
+
+https://gerrit.wikimedia.org/r/162604",1411572428,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Kartik proposed a change to add the font 'fonts-wqy-zenhei' https://gerrit.wikimedia.org/r/#/c/154086/  but it has been abandoned.
+
+Daniel Zahn pointed out it is made by https://github.com/wikimedia/operations-puppet/blob/8f14fc7cdbfb5c6f16cb4b1a3bbc64dfd5d200e8/modules/mediawiki/manifests/multimedia.pp#L91
+
+But:
+
+hashar@integration-slave1002:~$ apt-cache policy ttf-wqy-zenhei 
+ttf-wqy-zenhei:
+  Installed: (none)
+  Candidate: 0.9.45-3.1ubuntu1
+  Version table:
+     0.9.45-3.1ubuntu1 0
+        500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
+
+
+So apparently mediawiki::packages::fonts is not applied on the continuous integration slaves though we include ::mediawiki::packages , we apparently need to explicitly add that puppet class.",1411572208,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"I have created a short script[1] and a simple jenkins job[2] to demonstrate the problem.
+
+The script opens main page using firefox in several languages and takes screenhots[3-5]. Screenshots show that Chinese and Japanese characters are not displayed properly.
+
+Are we doing something wrong? Or, is the jenkins slave where the firefox is running missing the fonts?
+
+1: https://gerrit.wikimedia.org/r/#/c/162576/2/modules/ve-mw/tests/browser/fonts.rb,cm
+2: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox-69535/
+3: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox-69535/lastSuccessfulBuild/artifact/modules/ve-mw/tests/browser/ja.png/*view*/
+4: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox-69535/lastSuccessfulBuild/artifact/modules/ve-mw/tests/browser/zh-hans.png/*view*/
+5: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox-69535/lastSuccessfulBuild/artifact/modules/ve-mw/tests/browser/zh-hant.png/*view*/",1411570315,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162576 abandoned by Zfilipin:
+WIP [BrowserTest] reproducing bug 69535
+
+https://gerrit.wikimedia.org/r/162576",1411569870,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162576 had a related patch set uploaded by Zfilipin:
+WIP [BrowserTest] reproducing bug 69535
+
+https://gerrit.wikimedia.org/r/162576",1411564868,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162569 abandoned by Zfilipin:
+WIP reproducing bug 69535
+
+https://gerrit.wikimedia.org/r/162569",1411564681,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162569 had a related patch set uploaded by Zfilipin:
+WIP reproducing bug 69535
+
+https://gerrit.wikimedia.org/r/162569",1411560943,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Submitted Sauce Labs support ticket:
+
+https://support.saucelabs.com/requests/15238",1411556975,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"The jobs as they are configured now run on Sauce, whee we cannot control the fonts.
+
+We need to run the jobs on a machine where we can install the required fonts.",1411485994,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 154086 abandoned by Dzahn:
+Add Chinese fonts for VE screenshots feature
+
+Reason:
+abandoning because the related bug is resolved. also it's easy to restore if needed. cheers, Daniel
+
+https://gerrit.wikimedia.org/r/154086",1410565690,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"(In reply to Željko Filipin from comment #5)
+> Vikas, Amir, are Japanese and Chinese screenshots now good?
+
+ping :)",1410561749,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Vikas, Amir, are Japanese and Chinese screenshots now good?",1409595399,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Daniel Z. pointed out that ""ttf-wqy-zenhei"" works as a package name on both Precise and Trusty. On Trusty, it is a virtual package that depends on ""fonts-wqy-zenhei"", to make migration easier. And, in fact, we already install it:
+
+https://github.com/wikimedia/operations-puppet/blob/8f14fc7cdbfb5c6f16cb4b1a3bbc64dfd5d200e8/modules/mediawiki/manifests/multimedia.pp#L91",1409349346,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"""fonts-wqy-zenhei"" is available on Trusty but not Precise:
+
+    [mw1001:~] $ cat /etc/issue
+    Ubuntu 12.04.4 LTS \n \l
+
+    [mw1001:~] $ apt-get --dry-run install fonts-wqy-zenhei
+    NOTE: This is only a simulation!
+          apt-get needs root privileges for real execution.
+          Keep also in mind that locking is deactivated,
+          so don't depend on the relevance to the real current situation!
+    Reading package lists... Done
+    Building dependency tree
+    Reading state information... Done
+    Package fonts-wqy-zenhei is not available, but is referred to by another package.
+    This may mean that the package is missing, has been obsoleted, or
+    is only available from another source
+
+    E: Package 'fonts-wqy-zenhei' has no installation candidate",1409348944,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 154086 had a related patch set uploaded by KartikMistry:
+Add Chinese fonts for VE screenshots feature
+
+https://gerrit.wikimedia.org/r/154086",1408034978,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,Moving to Wikimedia -> Quality.  Will have to figure out the font packages to install.  Maybe we could reuse the one defined in puppet class mediawiki::multimedia::fonts,1408022325,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+VisualEditor: Undo resizing of image with explicit dimension in core doesn't render correctly,"1. Create an image in VE standalone with no width/heigh attrs (using the html editor mode)
+2. Resize the image in VE and undo
+
+The image doesn't go back to it's original size (in the view).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408015440,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hahseqx35ztkj6fz5cfs,task_description,resolved
+VisualEditor: Undo resizing of image with explicit dimension in core doesn't render correctly,"**gerritadmin** wrote:
+
+Change 154036 merged by jenkins-bot:
+Make sure image attribute is cleared if set to null
+
+https://gerrit.wikimedia.org/r/154036",1408016718,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hahseqx35ztkj6fz5cfs,task_subcomment,NA
+VisualEditor: Undo resizing of image with explicit dimension in core doesn't render correctly,"**gerritadmin** wrote:
+
+Change 154036 had a related patch set uploaded by Esanders:
+Make sure image attribute is cleared if set to null
+
+https://gerrit.wikimedia.org/r/154036",1408015486,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hahseqx35ztkj6fz5cfs,task_subcomment,NA
+Cannot copy text when dm.surface.enabled === false,"**Author:** `ryan.wold`
+
+**Description:**
+When disabling an Editor's .target.surface (by calling .disable()), the text is no longer editable, which is great.  However, the text in the disabled Editor cannot be copied and pasted.  It does not appear to make it to the clipboard. 
+
+Desired behavior is that the text can be be copied even when the editor is disabled.  Or perhaps there could be a setting/option around that.
+
+
+
+We traced this to ve.dm.Surface.prototype.changeInternal, where it returns immediately if the surface is disabled.
+
+if ( !this.enabled ) {
+  return;
+}
+
+I found this here: https://doc.wikimedia.org/VisualEditor/master/source/ve.dm.Surface.html#ve-dm-Surface-method-changeInternal
+
+
+I'm using OSX Mavericks and Google Chrome Version 36.0.1985.125.
+
+Thanks!
+
+- Ryan Wold
+  ryan.wold@neo.com
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407976320,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-faekguqj2f5hrdp6337k,task_description,declined
+Cannot copy text when dm.surface.enabled === false,The surface model also tracks selections so disabling the surface model would also disable any meaningful copy/paste functionality. dm.Surface#disable is not really intended for putting the surface into a useful read-only mode. What exactly are you trying to achieve?,1416318771,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-faekguqj2f5hrdp6337k,task_subcomment,NA
+Cannot copy text when dm.surface.enabled === false,"**ryan.wold** wrote:
+
+%%%*** Bug 69516 has been marked as a duplicate of this bug. ***%%%",1407976455,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-faekguqj2f5hrdp6337k,task_subcomment,NA
+VisualEditor:  Link tool is too small when adding captions to new images,"""Before"".  This is what you see at step #4.
+
+See attached screenshots.  
+
+Steps to reproduce:
+
+1.  Open VisualEditor and Insert > Media.
+
+2.  Pick and image and add a caption.
+
+3.  Select a word and press Command-K to make an internal link. 
+
+4.  Notice that the link inspector ought to be bigger, so you can see all the new buttons.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14165}",1407973920,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5soltwr3wdlryrbxkfmr,task_description,resolved
+VisualEditor:  Link tool is too small when adding captions to new images,Works for me in Firefox 31 and Safari 6.,1410217508,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5soltwr3wdlryrbxkfmr,task_subcomment,NA
+VisualEditor:  Link tool is too small when adding captions to new images,"This appears to now be fixed?
+
+(Tested: Vector & Monobook on wmf19, wmf20, and pre-wmf21 with Firefox and Chrome.)",1410202626,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5soltwr3wdlryrbxkfmr,task_subcomment,NA
+VisualEditor:  Link tool is too small when adding captions to new images,"Created attachment 16188
+""After"":  This is what you get when you click inside the box, to get past bug 69510's focus problem.
+
+**Attached**: {F14166}",1407973999,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5soltwr3wdlryrbxkfmr,task_subcomment,NA
+VisualEditor: Inspectors close immediately in IE,"In Internet Explorer, if you open a link or comment inspector, it closes immediately after opening. It doesn't matter if you use Ctrl+K or the context or the toolbar or double-click or enter to open the inspector, the exact same thing happens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407970620,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5jyi6gfrdcofdg2qdtbv,task_description,resolved
+VisualEditor: Inspectors close immediately in IE,Fixed in https://gerrit.wikimedia.org/r/#/c/155182/,1408666091,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5jyi6gfrdcofdg2qdtbv,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary","This is related to bug 50872.
+
+If you click the edit link on a section, then that section's heading is pre-populated in the edit summary when you save.
+
+This does not work very well if you have turned on https://en.wikipedia.org/wiki/MediaWiki:Gadget-edittop.js (""Add an [edit] link for the lead section of a page"") in the gadgets for your preferences.  Editing the first (lead) section of the page gets a suggested edit summary that includes the first section heading on the page i.e., the section heading immediately underneath the section you were actually editing.
+
+The link for 'edit source' says:
+
+https://en.wikipedia.org/w/index.php?title=User:WhatamIdoing&action=edit&section=0&summary=/*%20top%20*/%20 
+
+The link for 'edit' says:
+
+https://en.wikipedia.org/w/index.php?title=User:WhatamIdoing&veaction=edit&vesection=1
+
+The subsequent section editing links are all correct.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407969600,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-orpzganqdg7lbcpdb7jk,task_description,resolved
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary",I went back and fixed up that gadget so it should handle VE links correctly. This change to pick up 'summary' from the URL should take affect on all Wikipedias on Thursday (it should already be on test and test2).,1409953109,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary","**gerritadmin** wrote:
+
+Change 156744 merged by jenkins-bot:
+Pick up 'summary' parameter from URL to use as initial edit summary
+
+https://gerrit.wikimedia.org/r/156744",1409261350,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary","**gerritadmin** wrote:
+
+Change 156744 had a related patch set uploaded by Alex Monk:
+Pick up 'summary' parameter from URL to use as initial edit summary
+
+https://gerrit.wikimedia.org/r/156744",1409191026,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary",Although VE should probably pick up the default summary from the URL.,1407976491,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary","It looks like the gadget needs to be fixed to deal with VE. In particular, it needs to be able to deal with 've' between the '&' and 'section='.",1407975957,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work","Steps to reproduce:
+
+1.  Open VisualEditor and select a word.
+
+2.  Press Command-K to open the link inspector.
+
+3.  We're going to make an external link to http://www.example.com so start typing:  h-t-t-p-:-/-/-w-w-w-
+
+4.  Why is it trying to find an internal page for the URL I'm typing?
+
+
+If you're obviously typing in a URL, the search feature should be disabled.  Offering to make a link to the ""local page"" http://www.example.com risks broken links like this:  https://en.wikipedia.org/w/index.phpdiff=621124784&oldid=620566012
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44011",1407968460,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_description,open
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work","About external links detection, it now works well.
+
+About links to pages with URL-like names, [[https://test.wikipedia.org/w/index.php?title=User:Pols12/sandbox&diff=455494&oldid=411023 | VE adds]] `./` instead of `:` to prefix the page name, even if you manually set a colon before the URL. By the way, prefixing colon seems to don’t be required.
+
+Since VE preview is fine, I think this is a Parsoid issue, that’s why I re-add Parsoid project for a new review (sorry if I’m wrong).
+
+Related: {T222082}.",1604536570,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work","About external links detection, it now works well.
+
+About links to pages with URL-like names, [[https://test.wikipedia.org/w/index.php?title=User:Pols12/sandbox&diff=455494&oldid=411023 | VE adds]] `./` instead of `:` to prefix the page name, even if you manually set a colon before the URL.
+
+Since VE preview is fine, I think this is a Parsoid issue, that’s why I re-add Parsoid project for a new review (sorry if I’m wrong).
+
+Related: {T222082}.",1604536306,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work",See also {T76398},1417554553,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work",">>! In T71500#749617, @Krenair wrote:
+> Interesting that MediaWiki allows you to create pages that are URLs, but you can't link to them...
+
+Sorry - it turns out you can link to internal pages named like URLs in MediaWiki, but you have to use the ':' prefix.",1417554365,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work",Bug 44011 sounds slightly related,1407975023,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work","Interesting that MediaWiki allows you to create pages that are URLs, but you can't link to them...",1407974528,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+Use {{!}} rather than <nowiki>|</nowiki> when inserting a | in a template argument,"In https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=621079160&oldid=621075505 it is pointed out that if an argument to a template contains a | then <nowiki>|</nowiki> is added. The new magic word {{!}} might be a better alternative.
+
+See also bug 67863
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407949080,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-jbatrq3ogdwn3vlvgukn,task_description,resolved
+Use {{!}} rather than <nowiki>|</nowiki> when inserting a | in a template argument,"Change 195559 merged by jenkins-bot:
+T71482: Convert | to {{!}} in template parameters
+
+[[https://gerrit.wikimedia.org/r/195559]]",1426018520,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jbatrq3ogdwn3vlvgukn,task_subcomment,NA
+Use {{!}} rather than <nowiki>|</nowiki> when inserting a | in a template argument,"Change 195559 had a related patch set uploaded (by Marcoil):
+T71482: Convert | to {{!}} in template parameters
+
+[[https://gerrit.wikimedia.org/r/195559]]
+",1426010733,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jbatrq3ogdwn3vlvgukn,task_subcomment,NA
+Use {{!}} rather than <nowiki>|</nowiki> when inserting a | in a template argument,A relevant diff is https://en.wikipedia.org/w/index.php?title=Bone_remodeling&diff=prev&oldid=621072608,1407949415,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-jbatrq3ogdwn3vlvgukn,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","For citation template references we may also want to specify a subset of parameters to show first.
+Links and citation mocks:
+{F18090}
+
+{F18092}
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407939960,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_description,resolved
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",,1423821836,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",,1423821811,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",,1417648165,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",,1417570409,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","(In reply to Bartosz Dziewoński from comment #6)
+> (I tried messing around with ve.dm.Converter too, but it seems impossible to
+> render the contents of templated references without involving the surface,
+> probably because they're magically generated in ve.ce.)
+
+Yeah, this needs CE. I think we may have to rethink how we do descriptions a little.",1411777912,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","(I tried messing around with ve.dm.Converter too, but it seems impossible to render the contents of templated references without involving the surface, probably because they're magically generated in ve.ce.)",1411776880,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","I played with it and the following sort of works for all reference node types. There must be a better way to do it, but I can't find one. (It also doesn't update the tooltip after reference contents are changed, probably because that is done deferred or something.)
+```
+ve.ce.MWReferenceNode.static.getDescription = function ( model ) {
+  var refModel = ve.dm.MWReferenceModel.static.newFromReferenceNode( model );
+  var surface = ve.init.target.createSurface( refModel.getDocument() );
+  var text = $( surface.getView().$element ).text();
+  surface.destroy();
+  return text;
+};
+```",1424101267,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","I played with it and the following sort of works for all reference node types. There must be a better way to do it, but I can't find one. (It also doesn't update the tooltip after reference contents are changed, probably because that is done deferred or something.)
+
+ve.ce.MWReferenceNode.static.getDescription = function ( model ) {
+  var refModel = ve.dm.MWReferenceModel.static.newFromReferenceNode( model );
+  var surface = ve.init.target.createSurface( refModel.getDocument() );
+  var text = $( surface.getView().$element ).text();
+  surface.destroy();
+  return text;
+};",1410961821,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","Any attempt to ""parse"" the template parameters is going to become very complex or fail to address the needs of wikis other than the English Wikipedia. How about just displaying the parsed content of the reference, stripped of links and any block markup, and limited to some length?",1410956058,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","I think we'd much rather keep the current model of showing the name of something shown, or the value of something not shown (like for HTML comments)…",1408487253,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","We could list template values in order until we run out of room, but this may not lead to desirable results, for example the first parameter in {{Cite web}} is URL.
+
+A more complex solution would be to come up with a format for defining how to generate the summary of a template and store it in template data, either as a value on the column (summary order):
+
+Field     Desc  Summary order
+url       ...   null
+publisher ...   2
+title     ...   1
+date      ...   3
+month     ...   null
+
+A simplified version of this would just flag one field as being used in the summary.
+
+etc.
+
+Or as a string concatenation message somewhere:
+
+""{{{title}}}, {{{publisher}}} - {{{date}}}""",1408464080,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",*** Bug 69744 has been marked as a duplicate of this bug. ***,1408464025,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: If you just change an image, the border parameter setting is lost","When you just change image on a media, the border parameter is lost.
+
+https://test2.wikipedia.org/w/index.php?title=BorderLost&diff=98843&oldid=98842
+
+Safari/Mac OS X
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407887580,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-qfttw2uqh62xx2xebpyu,task_description,resolved
+"VisualEditor: If you just change an image, the border parameter setting is lost","Change 149217 merged by jenkins-bot:
+Make the image model persistent
+
+https://gerrit.wikimedia.org/r/149217",1409242088,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qfttw2uqh62xx2xebpyu,task_subcomment,NA
+"VisualEditor: If you just change an image, the border parameter setting is lost","Change 149217 had a related patch set uploaded by Mooeypoo:
+Make the image model persistent
+
+https://gerrit.wikimedia.org/r/149217",1408487294,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qfttw2uqh62xx2xebpyu,task_subcomment,NA
+"VisualEditor: After inserting a comment and a link, a cursor is moved at the end of the line, but typed text gets inserted between the comment and the link","screenshot
+
+1> open a page in VE, insert a comment.
+2> While the comment is still highlighted, insert a link. Notice the cursor is in between the comment and the link.
+3>Now select the Language style text. Click “Done” in the language inspector.
+Notice the cursor has now moved to the end of the comment. Type in some text, it gets inserted after the link. See screenshot.
+
+Try the above steps, but instead of comment insert a Formula.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14630}",1407858060,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-pyvddazcokg6hnj3x73g,task_description,open
+"VisualEditor: After inserting a comment and a link, a cursor is moved at the end of the line, but typed text gets inserted between the comment and the link","Confirmed in Betalabs and test2. 
+
+After inserting a comment and a link, a cursor is moved at the end of the line, but typed text gets inserted between the comment and the link.",1413910361,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-pyvddazcokg6hnj3x73g,task_subcomment,NA
+"VisualEditor: After inserting a comment and a link, a cursor is moved at the end of the line, but typed text gets inserted between the comment and the link","Environment-test2 and beta
+Found only in chrome and Safari.",1407858464,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-pyvddazcokg6hnj3x73g,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","See e.g. http://parsoid-lb.eqiad.wikimedia.org/wikimania2014wiki/Submissions%2FVisualEditor_%E2%80%94_engineering_against_the_odds?oldid=47825 vs https://wikimania2014.wikimedia.org/wiki/Submissions/VisualEditor_%E2%80%94_engineering_against_the_odds?oldid=47825
+
+Wikitext:
+
+; '''Sunday August 10, 12:30, [[Frobisher 123]]'''
+
+Parsoid HTML:
+
+<dl><dt> <b>Sunday August 10, 12</b></dt><dd><b>30, <a rel=""mw:WikiLink"" href=""./Frobisher_123"">Frobisher 123</a></b></dd></dl>
+
+
+PHP parser HTML:
+
+<dl><dt><b>Sunday August 10, 12:30, <a href=""/wiki/Frobisher_123"" title=""Frobisher 123"">Frobisher 123</a></b></dt></dl>
+
+It looks like this might be a syntax ambiguity, but hopefully we can have bug-for-bug compatibility with the PHP parser? :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407406200,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nfrlo5myv3v4eprweid5,task_description,resolved
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Change 155868 merged by jenkins-bot:
+Context aware parsing of definition list colon
+
+[[https://gerrit.wikimedia.org/r/155868]]",1418243010,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Change 155868 had a related patch set uploaded (by Arlolra):
+Context aware parsing of definition list colon
+
+[[https://gerrit.wikimedia.org/r/155868]]
+
+#patch-for-review",1418186385,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Updating the title to reflect that this is not just i/b wikitext context, but more general. As indicated in comment 2, this could use some more testing to better spec out what the right behavior is.",1408907806,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Change 155868 had a related patch set uploaded by Arlolra:
+b/i context aware parsing of definition list colon
+
+https://gerrit.wikimedia.org/r/155868",1408770525,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Thankfully, this is not related to time, but more related to context-sensitive tokenization of the "":"" char in a dt-dl list.
+
+;a:b
+;''a:b''
+
+The behavior require a bit more testing. Ideally, this is reasonably well-behaved that it can be fixed in the tokenizer without requiring a DOM transformation fixup.",1407407505,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Also, if you try to edit this, the resulting wikitext is something like '''Sunday August 10, 11''':30, [[Frobisher 123]]''' . It's trying to close the bolding twice.",1407406346,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+VisualEditor: visualeditor-beta-warning help mentions non-existent Cancel button,"VE's help icon popup includes this ""visualeditor-beta-warning"" text:
+
+""VisualEditor is in 'beta'. You may encounter software issues, and you may not be able to edit parts of the page. To switch back to source editing at any time without losing your changes, open the dropdown next to \""{{int:visualeditor-toolbar-cancel}}\"" and select \""{{int:visualeditor-mweditmodesource-title}}\"".""
+
+But I don't see this Cancel button in the VE UI these days. The page options ""hamburger"" dropdown is now between (?) and [Save page].  It would be more helpful to show the hamburger icon in the help message, maybe WikiFont some day.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407356520,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-tsdm6dyf3irbaneuouwo,task_description,resolved
+VisualEditor: visualeditor-beta-warning help mentions non-existent Cancel button,Fixed in gerrit I36f13b2ff this morning. :-),1407361045,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tsdm6dyf3irbaneuouwo,task_subcomment,NA
+"VisualEditor: In the image advanced settings dialog, the alignment button order is wrong in RTL UI","In the image advanced settings dialog the image alignment buttons say ""right"", ""center"" and ""left"". In RTL UI their order is confusing, because the ""right"" button is on the ""left"" and vice versa. They should be in a more logical order. (The icons are correct, however.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407316680,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-iuk3q3w2mokdzao6ks7s,task_description,resolved
+"VisualEditor: In the image advanced settings dialog, the alignment button order is wrong in RTL UI","Change 152043 merged by jenkins-bot:
+Flip direction buttons in media dialog in RTL
+
+https://gerrit.wikimedia.org/r/152043",1407331618,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iuk3q3w2mokdzao6ks7s,task_subcomment,NA
+"VisualEditor: In the image advanced settings dialog, the alignment button order is wrong in RTL UI","Change 152043 had a related patch set uploaded by Amire80:
+Correct buttons order in media advanced settings
+
+https://gerrit.wikimedia.org/r/152043",1407328384,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iuk3q3w2mokdzao6ks7s,task_subcomment,NA
+vagrant_ram overrides sometimes ignored/forgotten,"I have two overrides for vagrant_ram:
+
+* CirrusSearch has a puppet-managed override setting it to 1536
+* I have a .settings.yaml with the following contents:
+---
+vagrant_ram: 2048
+git_user: ''
+puppet_debug: true
+
+However, sometimes it's lower than both of those.  I.E.:
+------
+             total       used       free     shared    buffers     cached
+Mem:           993        933         60         18          0         23
+-/+ buffers/cache:        909         84
+Swap:            0          0          0
+------
+
+Tested with 6b27f39 (I know that's a little old, so feel free to close if you think it's been fixed since).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69720",1407194880,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gomohetkd7ro7h36m2z2,task_description,resolved
+vagrant_ram overrides sometimes ignored/forgotten,"Probably fixed by 9da72b12c40f3e7a54870da8f6ec3c235ec6c337 (""Load settings if vagrant is run from subdirectory"")",1410294111,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gomohetkd7ro7h36m2z2,task_subcomment,NA
+vagrant_ram overrides sometimes ignored/forgotten,"Went back to:
+
+===
+vagrant@mediawiki-vagrant:~$ free -m
+             total       used       free     shared    buffers     cached
+Mem:          2001       1037        964          8         17        370
+-/+ buffers/cache:        649       1352
+Swap:            0          0          0
+===
+
+after a vagrant reload --provision",1408850957,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gomohetkd7ro7h36m2z2,task_subcomment,NA
+vagrant_ram overrides sometimes ignored/forgotten,"I noticed that I had this problem again after a vagrant halt, vagrant up cycle.  The reason I did the halt was that it was non-responsive, so it's possible it was already wrong even before the halt.
+
+Actual total and usage (when I have enough memory to do the free command, took a couple retries):
+
+===
+vagrant@mediawiki-vagrant:~$ free -m
+             total       used       free     shared    buffers     cached
+Mem:           993        938         55         20          0         25
+-/+ buffers/cache:        912         81
+Swap:            0          0          0
+
+===
+Roles:
+
+===
+Available roles:
+
+  accountinfo              * guidedtour               * popups                  
+  analytics                  gwtoolset                  proofreadpage           
+  antispam                   hadoop                     renameuser              
+  antispoof                  hive                       scholarships            
+  apisandbox                 https                      scribunto               
+  apparmor                   hue                        simple_miser            
+  babel                      imagemetrics               simple_performant       
+* betafeatures               interwiki                  sitematrix              
+  centralauth                jsduck                     svg                     
+  centralnotice              jsonconfig                 templatedata            
+  chromium                   mantle                     textextracts            
+  cirrussearch               massmessage                thumb_on_404            
+  cite                     * math                       timedmediahandler       
+  cldr                       mathsearch                 translate               
+* codeeditor                 mleb                       uls                     
+* cologneblue                mobileapp                  uploadwizard            
+  commons                    mobilefrontend             urlshortener            
+  commonsmetadata          * modern                     usermerge               
+  confirmedit                molhandler               * vectorbeta              
+  doublewiki               * monobook                 * visualeditor            
+* echo                       multimedia                 wikidata                
+  education                * multimediaviewer           wikidiff2               
+* eventlogging               navigationtiming         * wikieditor              
+  featuredfeeds              newusermessage             wikihiero               
+* flow                       oauth                      wikilove                
+  fss                        oozie                    * wikimediaevents         
+  fundraising                pagedtiffhandler           wikimediaincubator      
+* gadgets                  * pageimages                 wikimetrics             
+  gadgets2                   pagetriage                 wikitech                
+  geodata                  * parserfunctions            xhprof                  
+  geshi                    * parsoid                    zend                    
+* gettingstarted             pdfhandler                 zero                    
+  globalcssjs                phptags                                            
+  graph                      poem                                               
+===
+
+.settings.yaml
+
+===
+---
+git_user: ''
+vagrant_ram: 2048
+puppet_debug: true
+===
+
+vagrant.d/10-cirrussearch.yaml:
+===
+# Vagrant settings
+# Managed by puppet. Local changes will be lost on next puppet run.
+vagrant_ram: 2000
+forward_ports:
+    9200: 9200
+===",1408850801,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gomohetkd7ro7h36m2z2,task_subcomment,NA
+vagrant_ram overrides sometimes ignored/forgotten,Possibly fixed by https://gerrit.wikimedia.org/r/154975 .,1408482768,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gomohetkd7ro7h36m2z2,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?","The new Save dialog has two buttons at the top:  ""Cancel"" and ""Save""
+
+It's not clear whether Cancel means ""exit this dialog"" or ""lose all your work"".  Please change the label to something like ""Return to editing"" or ""Resume editing"", or something that clearly indicates that this button allows you to keep editing and will not exit VisualEditor and cause you to lose all of your work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407175800,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_description,resolved
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?",Verified the fix in production,1411681904,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?",Verified the fix in test2,1411083364,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?",Verified the fix in Betalabs,1410556935,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?","Change 159806 merged by jenkins-bot:
+Relabel the cancel button in the save dialog to ""Resume editing""
+
+https://gerrit.wikimedia.org/r/159806",1410471267,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?","Change 159806 had a related patch set uploaded by Jforrester:
+Relabel the cancel button in the save dialog to ""Resume editing""
+
+https://gerrit.wikimedia.org/r/159806",1410461574,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+LivePreview doesn't allow interaction with page content outside of #wikiPreview (it is not passed to mw.hook),"Currently, LivePreview only passes the $wikiPreview to the hook
+https://github.com/wikimedia/mediawiki/blob/6709a1fd082bcbc1b89d499edeafa04fd2e8a517/resources/src/mediawiki.action/mediawiki.action.edit.preview.js#L101
+but the script changes the page content in many other places:
+https://github.com/wikimedia/mediawiki/blob/6709a1fd082bcbc1b89d499edeafa04fd2e8a517/resources/src/mediawiki.action/mediawiki.action.edit.preview.js#L31-L43
+The new content for these parts should also be made available to the user, by passing them to the hook (as VisualEditor does, for example
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/ccdc215a9882d6bb3e079ca822f64c9089c0d363/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.js#L1574
+).
+
+This would allow scripts like
+https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-featured-articles-links.js&oldid=619815637
+to update the modifications of the language links after the user makes some changes and use the live preview (in the example, the ""badges"" for featured/good articles in other languages).
+
+Also, this is likely what UniversalLanguageSelector needs in order to fix bug T53029.",1407163740,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-floz7aecowu5ipopiscf,task_description,open
+VisualEditor: Pasting <em> content into a VE-MW surface should down-convert <em>s to <i>s (and <strong>s to <b>s),"See diff at https://de.wikipedia.org/w/index.php?title=Schotts_Sammelsurium&diff=prev&oldid=132639553 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406824380,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-k65a4qbdt2vssa5txndo,task_description,resolved
+VisualEditor: Pasting <em> content into a VE-MW surface should down-convert <em>s to <i>s (and <strong>s to <b>s),"(In reply to Kurt Jansson from comment #1)
+> The ""<em>"" tag was inserted via italicised text in the clipboard. Source for
+> the text was a web page. I would expect that the VE drops the tag or
+> replaces it with two singe quotes.
+
+Yeah, good point. I thought we already did this?
+
+> Ich have no idea where the ""<nowiki>"" tag came from. I wasn't able to delete
+> it in the VE.
+
+That's because you ended up with a paragraph starting with a ' ', and to stop it turning into a <pre> block it instead – bug 66628. It's harmless, if irritating.",1414452746,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k65a4qbdt2vssa5txndo,task_subcomment,NA
+VisualEditor: Pasting <em> content into a VE-MW surface should down-convert <em>s to <i>s (and <strong>s to <b>s),"Looking at this again, I believe VE used to add those nowiki tags to prevent the line being displayed differently from the others because of the space at its beginning; and VE does retain formatting when pasting, but that can be avoided by using the shortcut Ctrl + Shift + V.",1414154500,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-k65a4qbdt2vssa5txndo,task_subcomment,NA
+VisualEditor: Pasting <em> content into a VE-MW surface should down-convert <em>s to <i>s (and <strong>s to <b>s),"The ""<em>"" tag was inserted via italicised text in the clipboard. Source for the text was a web page. I would expect that the VE drops the tag or replaces it with two singe quotes.
+
+Ich have no idea where the ""<nowiki>"" tag came from. I wasn't able to delete it in the VE.",1407345383,PHID-USER-ctff2aq5r64yvikejdwo,PHID-TASK-k65a4qbdt2vssa5txndo,task_subcomment,NA
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),"When resizing the window, after a certain point the MediaWiki page layout may change (media queries). This affects the offset from the left side of the page (specifically, width of the sidebar).
+
+However the toolbar caches its computed offset once and never updates it.
+
+1. Open window wider than 1024px with Vector skin in MediaWiki.
+2. Enter VisualEditor.
+3. Resize to < 980px.
+
+Expected:
+
+Sidebar shrinks (per Vector styles) and toolbar should still align with left edge of the page.
+
+Actual:
+
+Sidebar shrinks but toolbar stays behind causing an awkward gap to appear as well as odd interruption in the shadow. It results in part of the Save page button to go off-screen. 
+
+Other:
+
+The reverse happens as well. Opening a narrow window and scaling it up will cause it to stay behind in the other direction. It results in part of the toolbar overlapping links in the sidebar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1406808480,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yyipeqjrkozgykvwcduy,task_description,resolved
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),Verified the fix in production.,1416272093,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-yyipeqjrkozgykvwcduy,task_subcomment,NA
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),"Change 169232 merged by jenkins-bot:
+Recalculate toolbar size on window resize
+
+https://gerrit.wikimedia.org/r/169232",1414448177,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yyipeqjrkozgykvwcduy,task_subcomment,NA
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),"Change 169232 had a related patch set uploaded by Esanders:
+Recalculate toolbar size on window resize
+
+https://gerrit.wikimedia.org/r/169232",1414447822,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yyipeqjrkozgykvwcduy,task_subcomment,NA
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),"Created attachment 16109
+Screenshot of bug.
+
+**Attached**: {F14581}",1406808595,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yyipeqjrkozgykvwcduy,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"These seem to be the leading cause of edit corruption right now.
+
+myEventWatcherDiv: https://ru.wikipedia.org/?diff=64516612 https://ru.wikipedia.org/?diff=64516412 https://pt.wikipedia.org/?diff=39659121 https://pt.wikipedia.org/?diff=39659108
+
+<embed> tags: https://pt.wikipedia.org/?diff=39696565
+
+<object> tags: https://fr.wikipedia.org/?diff=105796883 https://fr.wikipedia.org/?diff=105796959 https://fr.wikipedia.org/?diff=105797061
+
+I'm thinking we should put in hacks to remove these kinds of tags. Maybe at the point where we serialize the HTML and send it to Parsoid (ve.init.mw.Target#getHTML). If these tags are added immediately upon document creation (we'd need to get our hands on one of these bad plugins to test that) we could also consider trying to work around this in ve.createDocumentFromHtml instead. I suspect, though, that these tags are probably added asynchronously, and probably only in cases where we fall back to the iframe trick because DOMParser HTML support is not available.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406788020,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_description,resolved
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"Marking this as fixed, will keep an eye on the others in the next couple of weeks or so to see if those are resolved by it.",1412114053,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114010,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113119,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"(In reply to Alex Monk from comment #2)
+> I wonder if we can just do something like this
+> 
+> $( newDoc )
+> 	.remove( '[id=myEventWatcherDiv]' ) // Bug 51423
+> 	.remove( 'object[type=cosymantecnisbfw],
+> script[id=NortonInternetSecurityBF]' ) // Bug 63229
+> 	.remove( 'embed[id ^= xunlei_com_thunder_helper_plugin]' ) // Bug 63121
+> 	.remove( 'div[id=sendToInstapaperResults]' ) // Bug 61776
+> 	.remove( 'style[id=_clearly_component__css]' ) // Bug 53252
+> 	.remove( 'script[id=FoxLingoJs]' ) // Bug 52884
+> 	.remove( 'embed[type=application\\/x-datavault]' ) // Bug 52791
+> 	.remove( 'embed[type=application\\/iodbc]' ); // Bug 51521
+
+Yeah I was thinking about doing something like that. We have no easy way to know in advance what that will fix, but we can try it.",1412112352,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"I wonder if we can just do something like this
+
+$( newDoc )
+	.remove( '[id=myEventWatcherDiv]' ) // Bug 51423
+	.remove( 'object[type=cosymantecnisbfw], script[id=NortonInternetSecurityBF]' ) // Bug 63229
+	.remove( 'embed[id ^= xunlei_com_thunder_helper_plugin]' ) // Bug 63121
+	.remove( 'div[id=sendToInstapaperResults]' ) // Bug 61776
+	.remove( 'style[id=_clearly_component__css]' ) // Bug 53252
+	.remove( 'script[id=FoxLingoJs]' ) // Bug 52884
+	.remove( 'embed[type=application\\/x-datavault]' ) // Bug 52791
+	.remove( 'embed[type=application\\/iodbc]' ); // Bug 51521",1412112163,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),Here's a novel one: https://sv.wikipedia.org/?diff=27732757,1412096766,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,"The context menu for Basic Reference is still appearing, letting user to get stuck inside it after adding dfferent elements in it.
+We need to disable it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406774460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fvgll6ju7di7hlztbvdl,task_description,declined
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,The context menu for math and references list started appearing too.,1414614982,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,This is again appearing in mobile.,1414614819,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,Verified the fix in production.,1408653939,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,Verified the fix in test2,1408051332,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,Verified the fix in Betalabs,1407946189,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,The context menu for basic reference is still appearing in Betalabs,1407350062,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,"Change 151807 merged by jenkins-bot:
+Disable basic reference on mobile
+
+https://gerrit.wikimedia.org/r/151807",1407320455,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,"Change 151807 had a related patch set uploaded by JGonera:
+Disable basic reference on mobile
+
+https://gerrit.wikimedia.org/r/151807",1407200132,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor lost the first character when inputting with some IME,"**Author:** `hu60.cn`
+
+**Description:**
+There is a strange trouble happen when I edit with Baidu Pinyin (a Chinese IME) on Firefox runing on Windows 8.1. Baidu Pinyin can input two or more characters once. When I input ""你好"" at once, display is OK. But when I save or delete some characters, the display refreshs and ""你"" lost, a blank instead of the character.
+
+Example:
+
+I input ""可视化编辑器已可用。""
+
+And save, it looks like:
+
+ 视化 辑器 可用。
+
+The first character at each input lost.
+
+However, when I switch IME to Microsoft Pinyin, the BUG disappear. All input works fine. Switch to Baidu Pinyin, the BUG continuing.
+
+I don't know what happened.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 8.1
+**Platform**: PC",1406770740,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4ptlg2ito6vzer5kk57s,task_description,open
+VisualEditor lost the first character when inputting with some IME,Does this block T51569?,1428337360,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-4ptlg2ito6vzer5kk57s,task_subcomment,NA
+VisualEditor lost the first character when inputting with some IME,"**hu60.cn** wrote:
+
+I made a mistake. The IME I use is Sogou Pinyin, not Baidu Pinyin.",1406850777,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4ptlg2ito6vzer5kk57s,task_subcomment,NA
+VisualEditor Mobile:CE is getting zoomed in on rotating the screen orientation in iPad Mini,"Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Place the cursor anywhere in CE
+3.Change the screen orientation to landscape
+4.Again rotate the screen
+
+Observed Result:
+CE gets zoomed in each time I rotate the screen
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406760900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e33lumruqobfcwjjasrw,task_description,resolved
+VisualEditor Mobile:CE is getting zoomed in on rotating the screen orientation in iPad Mini,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487201,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e33lumruqobfcwjjasrw,task_subcomment,NA
+VisualEditor Mobile:CE is getting zoomed in on rotating the screen orientation in iPad Mini,Needs re-testing.,1430336522,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e33lumruqobfcwjjasrw,task_subcomment,NA
+Parsoid: Automatic newline prepending to table-template causes incorrect rendering and messed up HTML in Parsoid parser,"+++ This bug was initially created as a clone of Bug #68297 +++
+
+On mediawiki.org, there is a family on fancy templates like [[mw:Template:MW 1.23]] that generate a right-floated MediaWiki version number in a frame.
+
+These templates generate a wikitext table (starting with '{|'), which means that due to bug 529 / bug 12974 a newline is prepended before it. This behavior is incredibly annoying in practice, but it seems that we're very much wedded to it because it made Parsoid people's lives easier.
+
+However, Parsoid rendering of this particular template is inconsistent with PHP. On [[mw:Manual:Skinning#Localisation_messages]], PHP generates an empty paragraph before the table, while Parsoid doesn't and produces an about-grouped pair of <span>\n</span><table>…</table> (the span tag only contains the prepended newline).
+
+This rendering, that looks good in Parsoid/VisualEditor, therefore looks like crap in PHP parser.
+
+Note that the <span> is not nested in a <p> or any other block-level element, it just sits there right in the <body>. (It is not visible since, as I mentioned, it just contains some whitespace.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406735100,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5bjxxerf7yoz2uejrrao,task_description,resolved
+Parsoid: Automatic newline prepending to table-template causes incorrect rendering and messed up HTML in Parsoid parser,"```
+[subbu@earth:~/work/wmf/parsoid] echo ""{{MW 1.22|and later}} MediaWiki 1.22 added support for <code>."" | php bin/parse.php --domain www.mediawiki.org --wt2wt
+{{MW 1.22|and later}} MediaWiki 1.22 added support for <code>.
+```",1590706405,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-5bjxxerf7yoz2uejrrao,task_subcomment,NA
+Parsoid: Automatic newline prepending to table-template causes incorrect rendering and messed up HTML in Parsoid parser,"The php parser no longer seems to generate an empty paragraph and the parsoid output seems comparable. The span wrapping of the newline is to mark it as template generated for suppressing on roundtrip.
+
+The `_rtselser/mediawikiwiki/Manual:Skinning?oldid=1072136` seems fine.
+
+But of note,
+
+```
+echo ""{{MW 1.22|and later}} MediaWiki 1.22 added support for <code>."" | node parse --prefix mediawikiwiki --wt2wt
+{{MW 1.22|and later}}
+<nowiki> </nowiki>MediaWiki 1.22 added support for <code>.
+```
+
+",1418932905,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-5bjxxerf7yoz2uejrrao,task_subcomment,NA
+VisualEditor Mobile: Cannot type the reference name inside Re-use existing reference dialog unless select a reference from that dialog,"Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Add few references 
+3.Now open Re-use existing reference dialog
+4.Try to type a reference name in the field
+
+Observed Result: 
+Nothing happens
+
+5.Save the page
+6.Reopen the page and try again typing reference name in the field,
+
+Observed Result:
+Nothing happens
+
+
+7.Now select any reference from the list
+8.Reopen the Re-use dialog,try typing a reference name in that dialog
+
+Observed Result
+this time it will work
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406673660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zhhx6gkxdzizm66cix7v,task_description,resolved
+VisualEditor Mobile: Cannot type the reference name inside Re-use existing reference dialog unless select a reference from that dialog,"Seems to work for me now (in Citoid), but it's a bit of a mess. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488531,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zhhx6gkxdzizm66cix7v,task_subcomment,NA
+VisualEditor Mobile: Cannot type the reference name inside Re-use existing reference dialog unless select a reference from that dialog,"Seems to work for me now (in Citoid), but it's a bit of a mess. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488526,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zhhx6gkxdzizm66cix7v,task_subcomment,NA
+VisualEditor Mobile: Cannot type the reference name inside Re-use existing reference dialog unless select a reference from that dialog,Needs re-testing.,1430336312,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zhhx6gkxdzizm66cix7v,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"screenshot1
+
+Environment- test2
+
+Steps-
+1> open a page in VE.
+2> Insert ->Media. 
+3>Select to add a media file. Opens the Media Settings dialog.
+4>Now click on “Caption” pane and Select Language from the text style menu, closes the drop down.
+5>Cursor is at the beginning of the line. Click again on the style text menu to see that the Language is selected . See screenshots.
+6> Notice typing the first letter deselects the Language from the drop-down, and so the language inspector never appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14328}",1406649060,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-psfncojk42sp2n4fkx6z,task_description,resolved
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Created attachment 16121
+screenshot
+
+**Attached**: {F14330}",1406921105,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,In Chrome and FF only the Language Inspector appears out of place when launched for the first time.The steps to reproduce are the same.See screenshot.Both in test2 and beta.,1406921066,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Change 150738 merged by jenkins-bot:
+Set a default language for ve.dm.Document if we can't guess it otherwise
+
+https://gerrit.wikimedia.org/r/150738",1406765133,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,This is… interesting.,1406764869,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Change 150738 had a related patch set uploaded by Jforrester:
+Set a default language for ve.dm.Document if we can't guess it otherwise
+
+https://gerrit.wikimedia.org/r/150738",1406764817,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null)., baehavior found in betalabs.,1406652768,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Ed, is this fixed by gerrit 149635?",1406650596,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Created attachment 16089
+screenshot2
+
+**Attached**: {F14329}",1406649118,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"screenshot
+
+Environment- test2,betalabs, production.
+Steps-
+1> Open a page in VE.
+2> Insert ->Media. 
+3>Select to add a media file. Opens the Media Settings dialog.
+4>Now click on “Alternative Text”. This should make the “Caption” inaccessible, but it is not. See screenshot.
+Now click on Caption pane, and then into Alternative Text, this makes the toolbar in the Caption pane blurred.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14322}",1406647800,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-qkdhag2mz377tvfw5d6p,task_description,resolved
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,Issue Resolved in test2 and beta.,1406922763,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"Change 150304 merged by jenkins-bot:
+Focus the caption surface on initialization
+
+https://gerrit.wikimedia.org/r/150304",1406664021,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"Change 150304 had a related patch set uploaded by Mooeypoo:
+Focus the caption surface on initialization
+
+https://gerrit.wikimedia.org/r/150304",1406662799,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"Okay, I seem to have misunderstood the bug, sorry about that; I thought you were talking about the entire caption field, not just the toolbar.
+
+I'll take care of this. Thank you for the report!",1406656762,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,*** Bug 68809 has been marked as a duplicate of this bug. ***,1406655142,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"This is a little more complicated than that, though. An image could absolutely have both a caption and an alternate text, and a caption can ""act"" like alternate text in case of inline images. 
+
+More to the point, a block image can have both a caption under the image and an alternative text (""title"" popup). An inline image doesn't have a functional caption - but the caption serves as its alternate text unless an alternate text overrides it.
+
+In short, we need to figure out a consistent way of how to handle caption and alt text in images in general. Just disabling the caption in case of alternate text is not really representative of what is allowed under all cases.",1406650739,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","Take this HTML:
+```
+<ul><li>asd
+sdf</li></ul>
+```
+Parse to wikitext:
+```
+* asd
+sdf
+```
+Parse back to HTML:
+```
+<ul><li>asd</li></ul>
+<p>sdf</p>
+```
+I'm not sure what should happen here, but definitely not this.
+
+It's rather easy to run into this in VisualEditor – take a paragraph with newlines and convert it to a list item. I ran into it making this edit: https://en.wikipedia.org/w/index.php?title=Polish_nationality_law&diff=prev&oldid=618961884 (I manually replaced the newlines with spaces before saving).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**: {T55568}",1406638920,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-p57423cc4ujmx5lgadoy,task_description,duplicate
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","I'm a bit confused - what was the actual list item content given in the Description of this task suppose to be -- 2 words or 1 word?
+```
+* asd sdf
+```
+OR
+```
+* asdsdf
+```
+If the desired output was the first one (2 words), then I can get that (no VE) by inserting then previewing the following:
+```
+<ul>
+<li>asd 
+sdf</li>
+</ul>
+```
+",1420995987,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-p57423cc4ujmx5lgadoy,task_subcomment,NA
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","This will need a Parsoid fix since other Parsoid users might still give it HTML that won't be preserved in the html -> wt -> html transformation. 
+
+VE can choose to fix or not independently.",1406802925,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-p57423cc4ujmx5lgadoy,task_subcomment,NA
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","In cases like this, it would probably be reasonable to just convert newlines to spaces at some point (either in VisualEditor or in Parsoid).
+
+Perhaps VisualEditor would be a better place to implement this from the user's perspective, but Parsoid doing what it does now would still be weird :) – maybe we should just fix this in both places?",1406802443,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-p57423cc4ujmx5lgadoy,task_subcomment,NA
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","Yes, this is a known issue. Parsoid currently cannot handle arbitrary HTML and convert it to wikitext in a way that preserves rendering on the html -> wt -> html path. But, we've talked about this issue more generally in the past and will address it including fallback mechanisms where some forms of HTML will have to get serialized as HTML tags rather than native wikitext. I thought we had a tracking or related set of bugs for this but, cannot find it right now.
+
+We should identify any other related breakages that arise from within VE (which doesn't necessarily generate arbitrary HTML) and fix them together in Parsoid. This fix would be simpler than support for generic HTML->wt conversion that is preserved in a html2html transformation.",1406802108,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-p57423cc4ujmx5lgadoy,task_subcomment,NA
+"VisualEditor: Opening the link inspector and then closing, while selecting an image moves the image to the previous position","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it thumbnail-left
+4.Now while the image is selected,Open the link inspector tool
+5.Without making any change, just close the link inspector by clicking on Done button
+  
+Observed Result:
+The image gets repositioned as thumbnail-right again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406577840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2kwqewofv75ewmmj7vjy,task_description,resolved
+"VisualEditor: Opening the link inspector and then closing, while selecting an image moves the image to the previous position",Verified the fix in Production,1410545977,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2kwqewofv75ewmmj7vjy,task_subcomment,NA
+"VisualEditor: Opening the link inspector and then closing, while selecting an image moves the image to the previous position",Has been fixed in d635974160ee749a344420ca18b43b401080c346.,1410031260,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2kwqewofv75ewmmj7vjy,task_subcomment,NA
+"VisualEditor: Opening the link inspector and then closing, while selecting an image moves the image to the previous position","This is almost certainly because there's an undo in AnnotationInspector, which expects there to be a corresponding transaction, but there isn't one.",1406747068,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2kwqewofv75ewmmj7vjy,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"Output of the error in commons beta lab
+
+Error: 
+
+Could not read or write file ""mwstore://local-backend/local-public/3/3d/VisualEditor_save_dialog-he.png"" due to insufficient permissions or missing directories/containers.
+
+Could not store file ""/tmp/UgKpr4"" at ""mwstore://local-backend/local-public/3/3d/VisualEditor_save_dialog-he.png"".
+
+I had got similar error while uploading images through API: 
+
+{    
+     ""servedby"": ""deployment-mediawiki02"",     
+     ""error"":
+          {         
+              ""0"": [             ""backend-fail-usable"",             ""mwstore://local-backend/local-public/6/68/VisualEditor_Insert_Menu-he.png""         ],         
+              ""1"": [             ""backend-fail-store"",             ""/tmp/owzHOG"",             ""mwstore://local-backend/local-public/6/68/VisualEditor_Insert_Menu-he.png""         ],         
+              ""code"": ""internal-error"",         
+              ""info"": ""An internal error occurred""     
+          } 
+}
+
+Scenario: 
+
+* I go to one of the image which I had already uploaded in commons[0].
+
+* I click on upload new version of this file at the bottom of the page.
+
+* I add a new image[1] by browsing my file system and I click Upload file.
+
+* Then I get the error reported above or the image in attachment.
+
+-
+[0]: http://commons.wikimedia.beta.wmflabs.org/wiki/File:VisualEditor_save_dialog-en.png
+
+[1]: http://commons.wikimedia.beta.wmflabs.org/w/index.php?title=Special:Upload&wpDestFile=VisualEditor_save_dialog-en.png&wpForReUpload=1
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14238}",1406576520,PHID-USER-b5bosdf7b7zp3vqofbug,PHID-TASK-waltxxgf7klwuydmvsrb,task_description,resolved
+Unable to upload new version of images in commons beta lab,"Resolving per:
+
+>>! In T70760#719880, @bd808 wrote:
+> Beta uses the NFS shared directory /data/project/upload7 to store images. 
+> 
+> I just did a permissions check on this directory for sub-directories that are not world writable and found a bunch. This is a likely cause of at least some of the failures.
+
+Swift is: {T64835}",1416949018,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"Beta uses the NFS shared directory /data/project/upload7 to store images. 
+
+I just did a permissions check on this directory for sub-directories that are not world writable and found a bunch. This is a likely cause of at least some of the failures.
+
+To check: 
+
+  $ cd /data/project/upload7
+  $ find . -type d ! -perm -o=w
+    ... lots of dirs output here ...
+
+To fix:
+
+  $ cd /data/project/upload7
+  $ sudo find . -type d ! -perm -o=w -exec chmod 0777 {} +
+
+A hack fix would be to cron this fix somewhere in beta. A better fix would be to kill NFS and use swift for image storage.",1406756728,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,cc'ing ori/bryan in case this was an effect of hhvm permission weirdness.,1406740927,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,Looks like the images which were uploaded before(i.e. before we got the some problems with beta labs recently) have this problem. I tried updating the image which was uploaded yesterday and it works fine.,1406659122,PHID-USER-b5bosdf7b7zp3vqofbug,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"(In reply to Chris McMahon from comment #2)
+> Let me know your user names and I can upgrade your privileges on beta labs.
+
+LanguageScreenshotBot",1406658908,PHID-USER-b5bosdf7b7zp3vqofbug,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"(In reply to Chris McMahon from comment #2)
+> Let me know your user names and I can upgrade your privileges on beta labs.
+
+""Greg (WMF)""",1406655871,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,Let me know your user names and I can upgrade your privileges on beta labs.,1406655159,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"Showing my ignorance: Do you have the right permissions? I apparently don't as I see ""You cannot overwrite this file."" on that and other images on the beta cluster commons.",1406655034,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+VisualEditor: Comment icon is truncated,"Screenshot
+
+See screenshot, from ""Barack Obama"" on enwiki beta. I assume it's meant to be an entire orange circle...
+
+This was seen in Firefox 30.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14125}",1406541780,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-v5onbdu6jehxicnrwhag,task_description,resolved
+VisualEditor: Comment icon is truncated,Fixed and deployed to wmf15 an hour ago. Sorry!,1406594236,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v5onbdu6jehxicnrwhag,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"From User:Encyclopedant:
+
+The Save dialog should have a link to open a new window to a bug report form. This is a good time to start a bug report because you have what you need at hand to write clearly about the bug.
+
+There is no link to report a bug. There is a ""leave feedback"" item under the ? help link in the editor toolbar, but that's kind of hidden, and it doesn't take you to a real bug report form.
+
+There should be a link to open a new window to a bug report form. The link should be explicit that you won't lose what you're doing and that the bug report form will open in a new window.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406497740,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4qeseygjikdfuaqbrolu,task_description,declined
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,We (now?) have a nice link in the help menu which leaves a comment on the local wiki's VE comments page.,1438370753,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"My second solution, then. Since that template doesn't probably exist elsewhere, my guess is we could copy it onto mediawiki and centralize that kind of feedback there.",1406708658,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,I'd assumed that such a link would be the same as the existing feedback link and go to the on-wiki feedback pages (either local or at mediawiki.org).,1406671682,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"We can't link them to Bugzilla (or Phabricator) without:
+
+* a detailed note about the different privacy policy there,
+* and that their bug reports must be written in English,
+* then the system would need to prompt them to create an account,
+* (which is not part of SUL-authorisation on Bugzilla),
+* then redirect back to opening a bug,
+
+… almost all of which will be written by someone unfamiliar with bug reporting, so they will likely waste a huge amount of time for everyone in re-writing or just closing.
+
+I'm minded to say WONTFIX…",1406668821,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"IMHO, currently that would be https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditor&component=General&format=guided . (That would probably need to point to the system which replaces Bugzilla at some point.)
+At en.wp there's also this link to report bugs through a template right on the feedback page https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&action=edit&section=new&watchthis=1&preload=Template:VE_Bug2/bug_template , but I think the first solution would be more desirable, especially since the future bug report system should be more user-friendly than the current one.",1406667036,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"What is a ""real bug report form""?",1406597486,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,"The version number in the help panel must be bidi-isolated so it won't mess up the date in RTL wikis.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406488800,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-zvn2wduyu4ldd2i4hote,task_description,resolved
+VisualEditor: version number in the help panel must be bidi-isolated,Now it is. :-),1406742261,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,"Change 149656 merged by jenkins-bot:
+Bidi-isolate the version in the help panel
+
+https://gerrit.wikimedia.org/r/149656",1406741972,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,It's not merged yet.,1406714107,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,Thanks!,1406566292,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,"Change 149656 had a related patch set uploaded by Amire80:
+Bidi-isolate the version in the help panel
+
+https://gerrit.wikimedia.org/r/149656",1406489027,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: Typing over a link doesn't undo correctly,"1. Select a link fully
+2. Type one letter
+3. Press undo
+
+Observer the first letter of the link is no longer linked.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406466900,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-lwcxwsesbmhskncgd577,task_description,resolved
+VisualEditor: Typing over a link doesn't undo correctly,"Change 149633 merged by jenkins-bot:
+Copy annotation indexes before returning
+
+https://gerrit.wikimedia.org/r/149633",1406584633,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lwcxwsesbmhskncgd577,task_subcomment,NA
+VisualEditor: Typing over a link doesn't undo correctly,The cause here is that the removal data in the transaction gets modified by annotationSet.removeAt(). Now the recorded removal data doesn't match the actual data that was there. If you created that link in this session then you also have have a sequence of transactions that don't connect.,1406473513,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-lwcxwsesbmhskncgd577,task_subcomment,NA
+VisualEditor: Typing over a link doesn't undo correctly,"Change 149633 had a related patch set uploaded by Esanders:
+Copy annotation indexes before returning
+
+https://gerrit.wikimedia.org/r/149633",1406473051,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lwcxwsesbmhskncgd577,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"Something wrong with the browsertests role, got after http://paste.debian.net/111811/
+
+Notice: /Stage[main]/Role::Browsertests/File[/srv/browsertests/config]/ensure: created
+Notice: /Stage[main]/Role::Browsertests/File[/srv/browsertests/config/secret.yml]/ensure: defined content as '{md5}b0aa09943ae3b5df22215876b3573a05'
+Error: Working directory '/srv/browsertests/tests/browser' does not exist
+Error: /Stage[main]/Role::Browsertests/Browsertests::Bundle[/srv/browsertests/tests/browser]/Ruby::Bundle[/srv/browsertests/tests/browser]/Exec[bundle_install_/srv/browsertests/tests/browser]/returns: change from notrun to 0 failed: Working directory '/srv/browsertests/tests/browser' does not exist
+
+[...]
+
+Notice: /Stage[main]/Browsertests/Mediawiki::User[Selenium_user]/Exec[mediawiki_user_Selenium_user]/returns: include_once ""$IP/extensions/WikimediaIncubator/WikimediaIncubator.php"";Account exists. Perhaps you want the --force option?
+Error: php5 createAndPromote.php Selenium_user vagrant returned 1 instead of one of [0]
+Error: /Stage[main]/Browsertests/Mediawiki::User[Selenium_user]/Exec[mediawiki_user_Selenium_user]/returns: change from notrun to 0 failed: php5 createAndPromote.php Selenium_user vagrant returned 1 instead of one of [0]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406399160,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-u54ktpl5srhndkfxtln2,task_description,resolved
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"Change 149921 merged by jenkins-bot:
+Removed browsertests role
+
+https://gerrit.wikimedia.org/r/149921",1406574712,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"Change 149921 had a related patch set uploaded by Dduvall:
+Removed browsertests role
+
+https://gerrit.wikimedia.org/r/149921",1406572528,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"Someone asked about removing the role on IRC about a week back. However, it doesn't look like that ever happened.",1406571386,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"The qa/browsertests repository has been emptied of content -- https://github.com/wikimedia/qa-browsertests. I thought there was a bug to remove the browsertests role altogether, but I'm not finding it at the moment.
+
+The ::mediawiki::extension define now supports a `browser_tests => true` setting to setup browser test support for an individual extension. I know the visualeditor role has been updated to use this setting, but there may be other extensions that need to be updated.",1406408257,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"At the next puppet run only the first is left:
+
+Notice: /Stage[main]/Apt/Exec[update_package_index]/returns: executed successfully
+Error: Working directory '/srv/browsertests/tests/browser' does not exist
+Error: /Stage[main]/Role::Browsertests/Browsertests::Bundle[/srv/browsertests/tests/browser]/Ruby::Bundle[/srv/browsertests/tests/browser]/Exec[bundle_install_/srv/browsertests/tests/browser]/returns: change from notrun to 0 failed: Working directory '/srv/browsertests/tests/browser' does not exist
+Notice: Finished catalog run in 282.18 seconds",1406401259,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+VisualEditor: Cursoring off focusable nodes scrolls viewport to the top of the document,"Steps:
+
+1. Open http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+2. Scroll to bottom
+3. Select the gallery
+4. Cursor right
+5. Press a letter.
+
+Expected outcome: Cursor ends up in slug after the gallery, with an 'a' in it; focus stays.
+
+Actual outcome: Focus moves to the top of the document, then restores when 'a' is typed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68708",1406322000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-77b6hmihb7n4klffjkkg,task_description,resolved
+VisualEditor: Cursoring off focusable nodes scrolls viewport to the top of the document,"Change 151400 merged by jenkins-bot:
+Set selection before focusing document
+
+https://gerrit.wikimedia.org/r/151400",1407065076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-77b6hmihb7n4klffjkkg,task_subcomment,NA
+VisualEditor: Cursoring off focusable nodes scrolls viewport to the top of the document,"Change 151400 had a related patch set uploaded by Esanders:
+Set selection before focusing document
+
+https://gerrit.wikimedia.org/r/151400",1407061967,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-77b6hmihb7n4klffjkkg,task_subcomment,NA
+VisualEditor: Cursoring off focusable nodes scrolls viewport to the top of the document,"From other reports it sounds like this may be happening for all focusable nodes, not just galleries.",1406576496,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-77b6hmihb7n4klffjkkg,task_subcomment,NA
+VisualEditor Mobile: The link text is not appearing in the link target field inside the link inspector for Android,"Steps to reproduce:
+
+1.Open a page with Mobile VE in Android with Chrome browser
+2.Type a text in CE
+3.Select the text
+4.Open the link inspector
+
+Observed Result:
+The link text is not appearing inside the link inspector in the link target field, it is just empty.
+
+Enviornment:Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406316240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-442235joepfyed6ueex4,task_description,resolved
+VisualEditor Mobile: The link text is not appearing in the link target field inside the link inspector for Android,This issue is not reproducible anymore.,1430341166,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-442235joepfyed6ueex4,task_subcomment,NA
+VisualEditor Mobile: The link text is not appearing in the link target field inside the link inspector for Android,This is issue in not reproducible anymore.,1430341151,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-442235joepfyed6ueex4,task_subcomment,NA
+VisualEditor Mobile: The link text is not appearing in the link target field inside the link inspector for Android,Needs re-testing.,1430336301,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-442235joepfyed6ueex4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,"Steps to reproduce:
+
+1.Open a page with VE which has 4 citations 
+2.Open Cite>Re-use
+3.Select the first reference to re-use
+4.Now again open the use existing reference dialog and observe that the last reference that you added is selected
+5.Try to add it in the article
+
+
+Observed Result:
+
+It does not get added, if you select some other reference and then try to add the previous one , it will work
+
+
+Environment:Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68869",1406311980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bmlzjgktkdmjeslkstm4,task_description,resolved
+VisualEditor: Cannot include the same existing reference after adding it once in an article,Verified the fix in production,1408047020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,Verified the fix in test2,1407191526,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,*** Bug 69027 has been marked as a duplicate of this bug. ***,1406929690,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,"Change 150708 merged by jenkins-bot:
+Unselect currently selected item in re-use citation dialog when reopening
+
+https://gerrit.wikimedia.org/r/150708",1406767242,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,"Change 150708 had a related patch set uploaded by Alex Monk:
+Unselect currently selected item in re-use citation dialog when reopening
+
+https://gerrit.wikimedia.org/r/150708",1406756572,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,Is this just because the reference is selected?,1406755218,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,Sounds like an OptionWidget/SelectWidget thing? Clear the selection when reopening the dialog?,1406746563,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+The checkboxen in the save dialog wrap poorly if the texts are too long,"VisualEditor: in the saving dialog, the ""Watch this page"" box can move to the next line with very large spacing between the lines. This happens in languages where it's longer than it is in English.
+
+Here's a screenshot of the problem (in Russian):
+
+{F14387}
+
+Possible solutions include:
+* Putting these boxes on separate lines form the start.
+* Making the line spacing smaller. This is a bit problematic, because the text of the second box may appear under the second, and this may be confusing.
+",1406297400,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ohfy6lgpehsflydjpak3,task_description,resolved
+The checkboxen in the save dialog wrap poorly if the texts are too long,"Change 231300 merged by jenkins-bot:
+Convert save checkboxes to OOUI widgets
+
+[[https://gerrit.wikimedia.org/r/231300]]",1439833998,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ohfy6lgpehsflydjpak3,task_subcomment,NA
+The checkboxen in the save dialog wrap poorly if the texts are too long,"After:
+{F1471410}",1439484196,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ohfy6lgpehsflydjpak3,task_subcomment,NA
+The checkboxen in the save dialog wrap poorly if the texts are too long,"Change 231300 had a related patch set uploaded (by Esanders):
+Convert save checkboxes to OOUI widgets
+
+[[https://gerrit.wikimedia.org/r/231300]]
+",1439484177,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ohfy6lgpehsflydjpak3,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,"https://fr.wikipedia.org/w/index.php?title=M%C3%A9thyl%C3%A8nedioxypyroval%C3%A9rone&curid=7265462&diff=105673189&oldid=102426146
+
+If you change anything in the template, nowiki tags will be added into the IUPAC name field. Also happens for the same article in other languages where the name is written in the same way (i.e. English or Spanish).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406216520,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_description,resolved
+VisualEditor: Adding nowiki tags in unrelated edit,I'm unable to reproduce. I suppose this was fixed in the round of `nowiki` work last quarter. Please reopen if seen again.,1430474728,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,Investigating…,1430409896,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,Nominating as blocker since it's a pretty nasty issue. I'm not sure if it's still happening but we should make sure.,1430238633,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,This is slightly aggressive <nowiki>ing by #Parsoid – looks to still be an issue. Is it a part of a wider task?,1421378405,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,"Isolated brackets (with no letter nearby) in a template parameter (compulsory) are over-protected by nowiki tags on any change in the template
+
+see : https://test2.wikipedia.org/w/index.php?title=Drong-1&diff=101272&oldid=101271
+
+Safari - MAC OS/X",1408805547,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Environment-test2
+
+steps-
+
+1> open a page in VE and open language inspector.
+2> Click upon ""English"" in the inspector, to open the Language Selector dialog.
+3> Now click on Language selector icon on top of the page, beside the username link (This extension is used for viewing pages in the language specified by the user's preferences).
+4> Notice dialog saying ""Select a Language"" appears and the Language Inspector gets closed.But the Language Selector dialog(with two-letter code for languages) is still open.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1406156220,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-7od6d3icidxgdzhb3ji2,task_description,resolved
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Hey Ritu, Can you specify the environment where you checked the fix?",1407190922,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,Issue Resolved.,1406920116,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Change 149635 merged by jenkins-bot:
+[BREAKING CHANGE] Fix ve.ui.Overlay classes
+
+https://gerrit.wikimedia.org/r/149635",1406676565,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Change 149635 had a related patch set uploaded by Esanders:
+Make the overlay used by the language dialog global
+
+https://gerrit.wikimedia.org/r/149635",1406475289,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Those links at the top shouldn't be accessible when a dialog is open. The problem is that the language dialog is launched in a slightly different way to others because it is launched from an inspector, and isn't getting a 'global' overlay which would shield those links.",1406475083,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node","Steps to reproduce:
+
+1.Open a page with VE
+2.Place the cursor after a reference note
+3.Press return
+
+Observed Result:
+
+Uncaught TypeError: Cannot read property 'context' of undefined appears and the cursor jumps to the beginning of the document
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406141820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_description,resolved
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node",Verified the fix in production,1407187962,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_subcomment,NA
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node",Verified the fix in test2,1406327220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_subcomment,NA
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node",Verified the fix in Betalabs,1406159954,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_subcomment,NA
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node","Fixed by https://gerrit.wikimedia.org/r/#/c/148671/ , needs an oojs release.",1406143164,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","I tried editing a page. I pressed Save and received a little ""Something went wrong"" window. I pressed ""Dismiss"". I wanted to try saving again, but the ""Save page"" button was disabled.
+
+It should probably be re-enabled.
+
+VE Version: 234e4e6, on mediawiki.org.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406140800,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-jkzbviyi473qzvp6r5kd,task_description,invalid
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled",I would mark this invalid until we could find out what error it would've been. But maybe we should make it clear in the UI when an error is unrecoverable (and have related patch(es) point to this bug).,1410125346,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","<Krenair> James_F, also, to clarify about badtoken - I was talking about saveErrorNewUser
+<Krenair> for invalid session
+<Krenair> it appears VE gets a new token to check whether the user ID has changed, when a badtoken error is encountered
+<RoanKattouw> Yeah we don't expose a badtoken error to the error handling code unless the API gave us a badtoken error twice
+<RoanKattouw> In which case the server's session storage is probably broken",1409697696,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","Badtoken errors are automatically recovered from, though…",1409692566,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","Hmmmm, don't remember what it could be. Possibly badtoken.",1409685705,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","ViewPageTarget#showSaveError allows errors to be recoverable or unrecoverable (defaulting to recoverable)
+
+The following errors should be recoverable:
+abusefilter
+badtoken
+
+The following errors are not:
+empty
+spamblacklist
+unknown
+
+Amir, what error did you run into?",1409685574,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled",I think we only show the error message for unrecoverable errors. Maybe we should prompt the user to give up rather than just exiting to an unusable save dialog?,1409669887,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"screenshot_chrome1
+
+In Chrome 36-
+Scenario#1-
+1> Open a page in VE and select Preformatted from text style menu.
+2> enter some text at the beginning and hit the spacebar till the cursor reaches the end of the line. Further pressing the spacebar takes the cursor out of the </pre> tag. See screenshot_chrome1.
+
+Scenario#2- tried the above steps, but with some characters at the end of the line and then inserting whitespace.See screenshot_chrome2. The cursor still  moves out.
+
+In FF 31-
+Tried the above steps without any characters at the end of the line and just inserting whitespaces. The cursor moves out.
+
+In Safari- No issue found.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14120}",1406137200,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-enbovi37zxerllyc24yd,task_description,resolved
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"I think my recent change 71ceef7dbb6ba95c84987c5c7ffbfecada9257f2 made this saner. Now preformatted text never wraps; if you insert more spaces than fit in the screen, you can still cursor out of the grey-bordered area, but the general behavior is saner (no weird scrolling inside the surface and no weird collapsing of spaces).",1429610947,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"Issue found in test2 too. 
+Steps-
+
+1> Open a page in VE and select Preformatted from text style menu.
+2> enter some text at the beginning and select Language inspector.Don't click any buttons on the inspector.
+3> Now click anywhere inside the preformatted.This closes the inspector dialog. 
+4>Now hit the spacebar till the cursor reaches the end of the line. Further pressing the spacebar takes the cursor out of the </pre> tag. See screenshot_test2.",1406217839,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"Created attachment 16033
+screenshot_test2
+
+**Attached**: {F14122}",1406215441,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,Test Environment:Production,1406139623,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"Created attachment 16015
+screenshot_chrome2
+
+**Attached**: {F14121}",1406137289,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Breadcrumb doesn't reappear upon saving page,"After using VE to edit a subpage in a namespace with subpages enabled, and saving changes, the breadcrumb link (< ParentPageName) underneath the page title does not come back.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406111820,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-xaopuar5atia63pv7slc,task_description,resolved
+VisualEditor: Breadcrumb doesn't reappear upon saving page,"Change 149351 merged by jenkins-bot:
+Don't overwrite #contentSub just to try to get the correct subtitle for redirects
+
+https://gerrit.wikimedia.org/r/149351",1406311507,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xaopuar5atia63pv7slc,task_subcomment,NA
+VisualEditor: Breadcrumb doesn't reappear upon saving page,"Change 149351 had a related patch set uploaded by Alex Monk:
+Don't overwrite #contentSub just to try to get the correct subtitle for redirects
+
+https://gerrit.wikimedia.org/r/149351",1406311070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xaopuar5atia63pv7slc,task_subcomment,NA
+VisualEditor: Breadcrumb doesn't reappear upon saving page,"<Krenair> So what's currently broken here is how we try to deal with the 'redirect page' text under the title
+<Krenair> We just do $( '#contentSub' ).text( ve.msg( 'redirectpagesub' ) ); which will overwrite the subpage breadcrumb
+<Krenair> Unfortunately, core doesn't wrap that redirect text in a way which we could single it out.
+
+Gerrit change 148883 to fix MW core",1406157282,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-xaopuar5atia63pv7slc,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","**Author:** `misc2006`
+
+**Description:**
+The most obvious way to add a non-breaking space (other than typing it, see T53045) would be the Insert -> Special Characters dialog.
+
+--------------------------
+Alternative: {T53045}",1406106000,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_description,resolved
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888717, @Esanders wrote:
+>>>! In T70429#6888458, @ppelberg wrote:
+>> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+>> 
+>> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+> 
+> It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+Understood. I've filed T278915 as a reminder.
+> 
+>> 
+>> 
+>>>>! In T70429#6875715, @iamjessklein wrote:
+>>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+>> Good question and I'm not aware of us having an answer to it.
+> The letters nbsp are probably understood in all languages because of the html sequence `&nbsp;` used to enter them in wikitext. People are only going to be looking in the special character inserter for this if the already know what it is. If you were just trying to fix a word wrapping issue and didn't know about NBSPs you probably wouldn't be looking for a special character.
+> 
+>>> 
+>>> How common is this affordance? 
+>> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+>> 
+>> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+> 
+> No, the logging only records which group is used.
+Understood.
+
+I am going to resolve this task considering:
+- I do not think anything here requires further action at this time. 
+- The patch that introduced this behavior landed in production via `MW-1.36-notes (1.36.0-wmf.29; 2021-02-02)`
+
+
+
+",1617164550,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+The letters nbsp are probably understood in all languages because of the html sequence `&nbsp;` used to enter them in wikitext. People are only going to be looking in the special character inserter for this if the already know what it is. If you were just trying to fix a word wrapping issue and didn't know about NBSPs you probably wouldn't be looking for a special character.
+
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+",1615019685,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+The letters nbsp are probably understood in all languages because of the html sequence `&nbsp;` used to enter them in wikitext. People are only going to be looking in the special character inserter for this if the already know what it is. If you were just trying to fix a word wrapping issue and didn't know about NBSPs you would probably be looking elsewhere.
+
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+",1615019606,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+",1615019149,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+
+> 
+>> Does it actually need to be more discoverable via the menu? 
+> Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+",1615019084,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+>>>! In T70429#6824562, @Esanders wrote:
+>>> For reference, it can be found here in the menus:
+>> 
+>> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+
+> 
+>> Does it actually need to be more discoverable via the menu? 
+> Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+",1615019036,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6824562, @Esanders wrote:
+>> For reference, it can be found here in the menus:
+> 
+> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+@Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+
+//Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most.//
+
+
+>>! In T70429#6875715, @iamjessklein wrote:
+> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+Good question and I'm not aware of us having an answer to it.
+> 
+> How common is this affordance? 
+If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+
+...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar?
+
+> Does it actually need to be more discoverable via the menu? 
+Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+
+",1614997977,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6824562, @Esanders wrote:
+>> For reference, it can be found here in the menus:
+> 
+> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+@Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+
+//Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – seems like it //could// be dynamic based on which symbols are used most by the editors at a particular project.//
+
+
+>>! In T70429#6875715, @iamjessklein wrote:
+> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+Good question and I'm not aware of us having an answer to it.
+> 
+> How common is this affordance? 
+If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+
+...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar?
+
+> Does it actually need to be more discoverable via the menu? 
+Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+
+",1614997924,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6824562, @Esanders wrote:
+>> For reference, it can be found here in the menus:
+> 
+> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+@Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+
+//Note: the comment you posted above leads me to wonder whether the list is hard-coded while the naming of the section – ""Often used"" – seems like it //could// be dynamic based on which symbols are used most by the editors at a particular project.//
+
+
+>>! In T70429#6875715, @iamjessklein wrote:
+> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+Good question and I'm not aware of us having an answer to it.
+> 
+> How common is this affordance? 
+If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+
+...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar?
+
+> Does it actually need to be more discoverable via the menu? 
+Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+
+",1614997913,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6824562, @Esanders wrote:
+>> For reference, it can be found here in the menus:
+> 
+> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+@Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+
+//Note: the comment you posted above leads me to wonder whether the list is hard-coded and the naming of the section – ""Often used"" – seems like it //could// be dynamic based on which symbols are used most by the editors at a particular project.//
+
+
+>>! In T70429#6875715, @iamjessklein wrote:
+> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+Good question and I'm not aware of us having an answer to it.
+> 
+> How common is this affordance? 
+If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+
+...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar?
+
+> Does it actually need to be more discoverable via the menu? 
+Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+
+",1614997869,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+
+How common is this affordance? Does it actually need to be more discoverable via the menu? (I would really prefer if we had a search menu under the omega menu but that would be a much larger task).
+
+",1614708836,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","> For reference, it can be found here in the menus:
+
+The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).",1613075426,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","For reference, it can be found here in the menus: 
+| Visual editor | Wikitext editor
+| -- | --
+| {F34100802} | {F34100807}
+
+This is admittedly very hidden. We have a follow-up task to add a keyboard shortcut for it: T53045.
+
+>>! In T70429#6795734, @Bdijkstra wrote:
+> [[ https://meta.wikimedia.org/wiki/Tech/News/2021/05 | Tech/News/2021/05]] suggests that this feature can currently be used. If so, how exactly can users of the 2010, 2017, and visual editors insert this character? I've tried various wikis (even test.wikipedia) and couldn't find it.
+
+It's not available on the production Wikimedia wikis yet due to a delay of the deployment train, but you can test it on <https://en.wikipedia.beta.wmflabs.org/>.
+",1613074423,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Test wiki on [[ https://patchdemo.wmflabs.org | Patch Demo ]]  by PPelberg (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/9ccca56b0e5403e33b61e9e8711b5c8c/w/ ]]~~",1612384898,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch Demo ]] by PPelberg (WMF) using patch(es) linked to this task:
+
+https://patchdemo.wmflabs.org/wikis/9ccca56b0e5403e33b61e9e8711b5c8c/w/",1612370821,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","@Bdijkstra It's in this week's train, so it'll start working today, tomorrow or on Thursday, depending on which wiki.",1612267423,PHID-USER-go2ym6ta2zn6ofdsrqnx,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","[[ https://meta.wikimedia.org/wiki/Tech/News/2021/05 | Tech/News/2021/05]] suggests that this feature can currently be used. If so, how exactly can users of the 2010, 2017, and visual editors insert this character? I've tried various wikis (even test.wikipedia) and couldn't find it.",1612268410,PHID-USER-xoa3aehuzhwg7enutrrl,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","[[ https://meta.wikimedia.org/wiki/Tech/News/2021/05 | Tech/News/2021/05]] that this feature can currently be used. If so, how exactly can users of the 2010, 2017, and visual editors insert this character? I've tried various wikis (even test.wikipedia) and couldn't find it.",1612264967,PHID-USER-xoa3aehuzhwg7enutrrl,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659378 **merged** by jenkins-bot:
+[mediawiki/core@master] Add &nbsp; to the special character list
+
+https://gerrit.wikimedia.org/r/659378",1611944794,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659376 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Implement mwPlatform#decodeEntities
+
+https://gerrit.wikimedia.org/r/659376",1611867462,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659408 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (fe9082b21)
+
+https://gerrit.wikimedia.org/r/659408",1611867086,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659408 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (fe9082b21)
+
+https://gerrit.wikimedia.org/r/659408",1611863850,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659374 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Allow HTML entities in the special character list
+
+https://gerrit.wikimedia.org/r/659374",1611863437,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Test wiki created on [[ http://patchdemo.wmflabs.org | Patch Demo ]] by ESanders (WMF) using patch(es) linked to this task:
+
+http://patchdemo.wmflabs.org/wikis/8593b7f469ef5349d6a47359e1d3b977/w/",1611861591,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659378 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/core@master] Add &nbsp; to the special character list
+
+https://gerrit.wikimedia.org/r/659378",1611860194,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659376 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Implement mwPlatform#decodeEntities
+
+https://gerrit.wikimedia.org/r/659376",1611860046,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659374 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] Allow HTML entities in the special character list
+
+https://gerrit.wikimedia.org/r/659374",1611860043,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Given that https://phabricator.wikimedia.org/T53045#1947804 happened, I guess that the special character option is still more difficult to implement than the other one, even if just as a temporary workaround?",1457711072,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Due to various implementation details this is more difficult than it looks (it's not just a matter of adding an entry to the list of available characters). If we implement {T53045}, I'm not sure if this one will be worth it.",1448821098,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","We already have the ability to use different label on the button than the character that will be inserted (we use it for more meaningful labels for combining characters, and in fact for invisible ones like zero-width non-joiner and joiner). We should probably make the label say ""NBSP"" if we do this.",1429721750,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",Or you could somehow annotate the whole word as nowrap. Arguably <nowrap>100 °C</nowrap> would be clearer than 100&nbsp;°C,1429613379,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","A hopefully clearer rationale for this request, from User:Gnom:
+
+//Our typography rules call for a non-breaking space when discussing units and abbreviations (""a marathon is run over a distance of 42.195 km"" calls for `42.195&nbsp;km` ; ""water boils at 100 °C"" requires `100&nbsp;°C` ; ""Mary Shelley created the character of Dr. Frankenstein"" includes `Dr.&nbsp;Frankenstein` ). I frequently use it in every law-related article in relation to the ""§"" sign, an example for this would be the article on Mietvertrag (Deutschland). //
+
+(Notice the several occurrences of the NBSP in https://de.wikipedia.org/wiki/Mietvertrag_(Deutschland).)",1426530087,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",Adding 68425 or users will have no idea what it is.,1406598979,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"**Author:** `misc2006`
+
+**Description:**
+There are at least two dash-like characters in the ""Special character"" dialog. They should have a tooltip describing them, otherwise it won't be obvious to most users which character is to be used in which situation. Actually, why not add a descriptive tooltip to all special characters?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406103960,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_description,resolved
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"Change 205558 merged by jenkins-bot:
+Allow special characters with tooltip or that encapsulate text
+
+[[https://gerrit.wikimedia.org/r/205558]]",1429750555,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"Change 205557 merged by jenkins-bot:
+ve.ui.SpecialCharacterPage: Allow providing a tooltip for characters
+
+[[https://gerrit.wikimedia.org/r/205557]]",1429744994,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"Change 205558 had a related patch set uploaded (by Bartosz Dziewoński):
+Allow special characters with tooltip or that encapsulate text
+
+[[https://gerrit.wikimedia.org/r/205558]]
+",1429608439,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"Change 205557 had a related patch set uploaded (by Bartosz Dziewoński):
+ve.ui.SpecialCharacterPage: Allow providing a tooltip for characters
+
+[[https://gerrit.wikimedia.org/r/205557]]
+",1429608421,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"For VisualEditor-MediaWiki, we're now reusing the special characters list from the wikitext WikiEditor. It has over 2000 entries and I am positive there is no point in providing and translating a tooltip for every single one of them.
+
+However, there are at least a few which could use a tooltip. That list has them for three similar-looking characters: − (minus sign), – (en dash) and — (em dash). We currently ignore these in VisualEditor, I'm fixing it.
+
+{F131436}
+
+For VisualEditor standalone, it would be reasonable to add labels for these three, too, but it's probably not be necessary, since we display the list in a clearer form (proportional fonts and shorter sections). I won't be doing this for now, someone else can decide.
+
+{F131440}",1429607706,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"**misc2006** wrote:
+
+(In reply to Andre Klapper from comment #1)
+
+> Assuming you refer to − and — : Don't use and situations highly depend on
+> cultures (and languages) anyway?
+
+I guess so (and that's probably why de.wikipedia has a different dialog than en.wikipedia), but still these characters have names that at least help explain their meaning and make it possible to tell them apart.
+
+> Any citation for ""won't be obvious to most users""?
+
+I've fixed about 2000 typos in de.wikipedia in the last few months and typographical problems (although not limited to the dash characters) are very common.
+
+> I doubt there is a usecase for explaining every single character (and making
+> translators translate them). Which actual problem to solve?
+
+It increases confidence in what you're doing if you can see that you are actually using the right character (instead of one that maybe just looks the same - this could easily happen with then tens of thousands of unicode characters available). For translation, either use the Unicode name without translation, or an official translation (that might be available or not).",1406109963,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"(In reply to Daniel Naber from comment #0)
+> There are at least two dash-like characters in the ""Special character""
+> dialog. They should have a tooltip describing them, otherwise it won't be
+> obvious to most users which character is to be used in which situation.
+
+Assuming you refer to − and — : Don't use and situations highly depend on cultures (and languages) anyway? Wondering if it would be possible to generally explain at all.  Any citation for ""won't be obvious to most users""?
+
+(In reply to Daniel Naber from comment #0)
+> Actually, why not add a descriptive tooltip to all special characters?
+
+I doubt there is a usecase for explaining every single character (and making translators translate them). Which actual problem to solve?",1406108435,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"no Message for error
+
+""Not logged in"" message has no Message text, shows placeholder id, see screen shot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14425}",1405964460,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-4itcjtumhnjkxw77si2v,task_description,resolved
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148573 merged by jenkins-bot:
+Update messages list for oojs-ui
+
+https://gerrit.wikimedia.org/r/148573",1406128714,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148550 merged by jenkins-bot:
+Update messages list for oojs-ui
+
+https://gerrit.wikimedia.org/r/148550",1406078176,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148573 had a related patch set uploaded by Jforrester:
+Update messages list for oojs-ui
+
+https://gerrit.wikimedia.org/r/148573",1406077975,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148120 abandoned by Catrope:
+Declare dependency on ooui-dialog-* messages as they're needed
+
+Reason:
+Done in MW core in https://gerrit.wikimedia.org/r/148550
+
+https://gerrit.wikimedia.org/r/148120",1406073076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148550 had a related patch set uploaded by Catrope:
+Update messages list for oojs-ui
+
+https://gerrit.wikimedia.org/r/148550",1406073057,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148120 had a related patch set uploaded by Jforrester:
+Declare dependency on ooui-dialog-* messages as they're needed
+
+https://gerrit.wikimedia.org/r/148120",1405965762,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: Pasting more than one paragraph is painfully slow in large documents,"Pasting more than one paragraph triggers a full document re-render. This is clearly seen in the standalone client where all the paragraphs flash grey on re-render.
+
+On en:Cat in Firefox it takes ~2s.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1405887180,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-st45mendifimrc7daviy,task_description,resolved
+VisualEditor: Pasting more than one paragraph is painfully slow in large documents,"Change 147987 merged by jenkins-bot:
+Fix calculation of affectedRange in transaction processor
+
+https://gerrit.wikimedia.org/r/147987",1406081163,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-st45mendifimrc7daviy,task_subcomment,NA
+VisualEditor: Pasting more than one paragraph is painfully slow in large documents,"Change 147987 had a related patch set uploaded by Esanders:
+Fix marking of affected range in transaction processor
+
+https://gerrit.wikimedia.org/r/147987",1405887249,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-st45mendifimrc7daviy,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","(This bug notes issues with both Parsoid and VisualEditor. I think all of this is caused by the terrible mistake that is bug 529 / bug 12974. I'll leave it for you to figure out this mess. :) )
+
+----
+
+On mediawiki.org, there is a family on fancy templates like [[mw:Template:MW 1.23]] that generate a right-floated MediaWiki version number in a frame.
+
+These templates generate a wikitext table (starting with '{|'), which means that due to bug 529 / bug 12974 a newline is prepended before it. This behavior is incredibly annoying in practice, but it seems that we're very much wedded to it because it made Parsoid people's lives easier.
+
+----
+
+However, Parsoid rendering of this particular template is inconsistent with PHP. On [[mw:Manual:Skinning#Localisation_messages]], PHP generates an empty paragraph before the table, while Parsoid doesn't and produces an about-grouped pair of <span>\n</span><table>…</table> (the span tag only contains the prepended newline).
+
+This rendering, that looks good in Parsoid/VisualEditor, therefore looks like crap in PHP parser.
+
+Note that the <span> is not nested in a <p> or any other block-level element, it just sits there right in the <body>. (It is not visible since, as I mentioned, it just contains some whitespace.)
+
+----
+
+More problems appear when you try to edit text with this template in VisualEditor.
+
+For example, testing on [[mw:Manual:Skinning#Localisation_messages]]:
+
+* Place cursor before/after one of the templates.
+* Press 'Right'/'Left' keyboard key twice.
+** First press selects the template, as expected.
+** Second press scrolls the page all the way up.
+
+* Try inserting the ""MW 1.23"" template on an empty line.
+** Observe that the blue highlights are different than for the
+   templates already present on the page – there is both the table, as
+   well as a single ""space"" (?) in text flow. Observe that the context
+   menu is placed weirdly in the middle of the page.
+** Place cursor after the ""space"" and try typing. Weird things happen,
+   sometimes I get an exception ""Uncaught Error: Unbalanced set of
+   replace operations found"", sometimes my input is duplicated or I
+   get snowmen and pawns.
+** Try deleting the template in any way. It is deleted, but the page
+   is scrolled all the way up.
+
+* Edit the two paragraphs right after the ""Localisation messages""
+  heading (add a letter somewhere in the middle or something).
+* Try saving the page.
+** Observe that multiple newline-related changes appear to have been
+   made. Strangely, there are actually no changes, but the *before*
+   half of the comparison has some newlines removed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405871700,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dobhhdqzp556tigyqgiz,task_description,resolved
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]",All VE items appear fixed as of a while ago. Marking as such.,1412889795,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","Let's turn this into a mini tracking bug, then? I split off the Parsoid issue to bug 68862, together with VE bug 68733, bug 68708 and bug 58038 this seems to describe all of the problems.",1406735205,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","The pawn, snowman and offset exception bugs should be fixed by https://gerrit.wikimedia.org/r/149920 .
+
+The scrolling all the way up is bug 68589.
+
+The rendering weirdness due to the span-wrapped newline is probably unique to this bug.",1406576539,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","(In reply to Bartosz Dziewoński from comment #0)
+> * Place cursor before/after one of the templates.
+> * Press 'Right'/'Left' keyboard key twice.
+> ** First press selects the template, as expected.
+> ** Second press scrolls the page all the way up.
+
+So if you select a node that's floating right and is half way down the page, then press left or right, you scroll all the way to the top of the page (though the cursor is positioned correctly).
+
+> ** Place cursor after the ""space"" and try typing. Weird things happen,
+>    sometimes I get an exception ""Uncaught Error: Unbalanced set of
+>    replace operations found"", sometimes my input is duplicated or I
+>    get snowmen and pawns.
+
+Yeah, I get that error and other weirdness (e.g. the cursor moving around - to before/after the template I think?) when typing normally, then snowmen+pawns when I try to undo/redo things. I've also been getting some extra errors: Uncaught Error: Unbalanced input passed to document 
+At one point I got this error as well: Uncaught Error: Offset could not be translated to a DOM element and offset: 77",1406333869,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","This is causing breakage in edits (that is not being detected by VE):
+https://www.mediawiki.org/w/index.php?title=Manual:Skinning&diff=1074312&oldid=1072136",1406115379,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"**Author:** `gabrasca2`
+
+**Description:**
+The text show/hide in the right of the navbox disappear after have edited a page where there is a navbox collapsed and the navbox appears uncollapsed, until the page is refreshed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1405797900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7zaj564v4tdljuzqups,task_description,declined
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,Please reopen if you can still reproduce this issue.,1415210380,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"(Quoting Alex Monk from comment #6)
+> Gabrasca, could you link to the page showing this issue?",1412626900,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"**gabrasca2** wrote:
+
+the issue appens only after it is saved from VE, if I reload the page the show/hide text returns.",1412408663,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"Gabrasca, please respond.",1412378459,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"Gabrasca, could you link to the page showing this issue?",1410125451,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"**gabrasca2** wrote:
+
+I tried on itwiki, in a personal sandbox with a navbox (example discography of a band).(In reply to Alex Monk from comment #4)
+> Hm.. Doesn't seem to happen with MW's built-in collapsible functionality.
+> And obviously enwiki's navbox (and related JS gadgets) is not a MediaWiki
+> feature, so this bug is probably invalid.",1406739658,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"Hm.. Doesn't seem to happen with MW's built-in collapsible functionality. And obviously enwiki's navbox (and related JS gadgets) is not a MediaWiki feature, so this bug is probably invalid.",1406734406,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"**gabrasca2** wrote:
+
+Edit a page with VisualEditor, add a template written with navbox, save, the template added is uncollapsed and in the right corner of the template there is not the text show/hide.",1406716452,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,Gabrasca: Could you clarify what you mean please? Some of the language in this bug is unclear. It sounds as if some of this might be valid for MW core's collapsible elements.,1406681224,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"There's a hook or something to call to get these to re-activate; it's already used in VPT for sortable tables or another common gadget, I believe.",1406602361,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+"VisualEditor Mobile: In android, while trying to apply a link on a selected text, strips off the first letter of the text in the link inspector","Steps to reproduce:
+
+1.Open a page with Mobile Ve in android with Chrome browser
+2.Select a text such as ""Text""
+3.Click on link inspector tool
+
+Observed Result:
+Observe that in the link inspector, the ""text"" is appearing as ""ext""",1405725780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rltauqohawt55lchrl4d,task_description,open
+"VisualEditor Mobile: In android, while trying to apply a link on a selected text, strips off the first letter of the text in the link inspector","This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592583998,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rltauqohawt55lchrl4d,task_subcomment,NA
+"VisualEditor Mobile: In android, while trying to apply a link on a selected text, strips off the first letter of the text in the link inspector","The previous comments don't explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status.
+
+//(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}. If this task is stalled on an upstream project, then the #upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task needs retesting, then the #testme tag should be added. If this task is either out of scope and nobody should ever work on this, or nobody else managed to reproduce the problem described in this task, then this task should have the ""Declined"" status.)//",1590761756,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rltauqohawt55lchrl4d,task_subcomment,NA
+"VisualEditor Mobile: In android, while trying to apply a link on a selected text, strips off the first letter of the text in the link inspector",Needs re-testing.,1430336424,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rltauqohawt55lchrl4d,task_subcomment,NA
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to the Advanced Settings and change the image size
+4.Click on Apply changes
+5.Reopen the Advanced Settings panel for that image again
+
+
+Observed Result:
+Observe that, the size values of the image are still showing the previous ones , though the image actually got resized
+If I save the page and reopen it and then check the Advanced Settings dialog , I see the updated values then.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405722900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_description,resolved
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page",Verified the fix in production,1407189132,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_subcomment,NA
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page",Verified the fix in test2,1406322997,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_subcomment,NA
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page","Change 147219 merged by jenkins-bot:
+Make the image model work without a node
+
+https://gerrit.wikimedia.org/r/147219",1406161979,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_subcomment,NA
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page","Change 147219 had a related patch set uploaded by Mooeypoo:
+Make the image model work without a node
+
+https://gerrit.wikimedia.org/r/147219",1405978515,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Cite>Basic
+3.Click on ""Use an existing reference"" button
+4.Now resize down the window 
+
+Observed Result:
+The ""Use Existing Reference"" dialog suddenly gets squished in and if I drag the window to its original size it stays like that.
+Now if you click on ""Go Back"" button the basic reference dialog also appears that way
+
+See the screenshot attached
+
+Browser: Chrome and Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14226}",1405712280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u5svmf673m5i5zmpc5ng,task_description,resolved
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,Verified the fix in production,1407188186,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,Verified the fix in test2,1406327085,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,Verified the fix in Betalabs,1406160162,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,Fixed now. :-),1406081224,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Change 148577 merged by jenkins-bot:
+Clamp height of MWReferenceDialog to between 300 and 400px to avoid it being too small
+
+https://gerrit.wikimedia.org/r/148577",1406080948,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Change 148577 had a related patch set uploaded by Jforrester:
+Clamp height of MWReferenceDialog to between 300 and 400px to avoid it being too small
+
+https://gerrit.wikimedia.org/r/148577",1406080696,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Created attachment 16010
+Screenshot
+
+**Attached**: {F14227}",1406072881,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Still happening but in a slightly different way.Also,there are now two ways of opening use existing reference dialog , but the initial size of the dialog upon opening is not same for both cases.
+
+See the screenshot attached",1406072745,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Change 147710 merged by jenkins-bot:
+Fix heights of Reference, ReferenceList and Template dialogs
+
+https://gerrit.wikimedia.org/r/147710",1406045501,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Change 147710 had a related patch set uploaded by Jforrester:
+Fix heights of Reference, ReferenceList and Template dialogs
+
+https://gerrit.wikimedia.org/r/147710",1405736124,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Screenshot
+
+The references list dialog is appearing a bit smaller in Firefox which also makes the text field for group name overlap with the border of the dialog.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70601
+
+**Attached**: {F14204}",1405709100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dqhaia75vamsl3rmnltp,task_description,resolved
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,Verified the fix in production,1407189700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,Verified the fix in production,1407189694,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,Verified the fix in test2,1406321895,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Change 148903 merged by jenkins-bot:
+Bump the height of the references list a little
+
+https://gerrit.wikimedia.org/r/148903",1406162585,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Change 148903 had a related patch set uploaded by Jforrester:
+Bump the height of the references list a little
+
+https://gerrit.wikimedia.org/r/148903",1406161479,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Created attachment 16027
+Screenshot
+
+This is still looking like this
+
+**Attached**: {F14205}",1406159502,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Change 147710 merged by jenkins-bot:
+Fix heights of Reference, ReferenceList and Template dialogs
+
+https://gerrit.wikimedia.org/r/147710",1406045504,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Change 147710 had a related patch set uploaded by Jforrester:
+Fix heights of Reference, ReferenceList and Template dialogs
+
+https://gerrit.wikimedia.org/r/147710",1405736119,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","Steps to reproduce:
+
+
+1.Open a page with mobile VE
+2.Select the option ""USe existing reference"" from Cite menu options
+3.Click on the ""Go Back"" button on use existing reference
+4.It takes you to the basic reference dialog
+
+
+Issue 1: Type something in the dialog pawn appears
+Issue 2: Click on ""Insert Reference"" nothing happens
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405638780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-caaaahazbcu7qa5ilv5p,task_description,resolved
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog",Verified the fix in production,1407186733,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog",Verified the fix in test2,1406327428,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","This issue got resolved with replacing ""Go Back"" button with ""Cancel"" button in Use Existing Reference dialog",1406072380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","Change 144058 merged by jenkins-bot:
+Put ""re-use reference"" in the toolbar ""Cite"" menu, and give it an icon
+
+https://gerrit.wikimedia.org/r/144058",1406064636,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","Change 144058 had a related patch set uploaded by Jforrester:
+Put ""re-use reference"" in the toolbar ""Cite"" menu, and give it an icon
+
+https://gerrit.wikimedia.org/r/144058",1406055177,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","Created attachment 15969
+Screenshot
+
+Issue 3: It also lets you add a template and get stuck there.
+
+**Attached**: {F14153}",1405639094,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf15] The highlights of the nodes are appearing over the toolbar menu,"Screenshot
+
+Steps to reproduce:
+
+1.Select any node such as reference in mobile VE using iOS or desktop safari
+
+2.Now open the cite menu option from the toolbar
+
+Observed Result:
+Observe that, the highlight of the reference node is appearing over the cite menu option.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14137}",1405637040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e6jsiulpiw5hjbfetpvc,task_description,resolved
+VisualEditor Mobile: [Regression pre-wmf15] The highlights of the nodes are appearing over the toolbar menu,Verified the fix in production,1408046907,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e6jsiulpiw5hjbfetpvc,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf15] The highlights of the nodes are appearing over the toolbar menu,Verified the fix in test2,1407265155,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e6jsiulpiw5hjbfetpvc,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf15] The highlights of the nodes are appearing over the toolbar menu,To check…,1406747398,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e6jsiulpiw5hjbfetpvc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Place the cursor in the CE
+3.Open Link inspector and insert a link
+4.Click on the link inspector icon again.
+
+Observed Result:
+The inspector appears a bit zoomed , which makes the title ""Link"" and the button ""Done"" on the top overlapped with the browser tabs
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14134}",1405635840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x2p7hqn3esqtuse7scxc,task_description,resolved
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab",Verified the fix in production,1408048262,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab",Verified the fix in test2,1407197493,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab","Cannot reproduce it anymore, might got fixed with windows refactor.",1406751119,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab","Created attachment 15966
+cursor position
+
+**Attached**: {F14136}",1405636258,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab","Created attachment 15965
+link suggestions
+
+Also see the other screenshots on how the cursor and the link suggestions appear when user tries to enter a link target when it appears like that.
+
+**Attached**: {F14135}",1405636232,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+VisualEditor Mobile: The Remove button for the link inspector in mobile is not styled as Red,"Screenshot
+
+See the screenshot attached
+The ""Remove"" button in the link inspector is not styled as Red
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14123}",1405634400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3q2oh7zhspz3z3iusr7s,task_description,resolved
+VisualEditor Mobile: The Remove button for the link inspector in mobile is not styled as Red,Verified the fix in production,1408046946,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3q2oh7zhspz3z3iusr7s,task_subcomment,NA
+VisualEditor Mobile: The Remove button for the link inspector in mobile is not styled as Red,Verified the fix in test2,1407197522,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3q2oh7zhspz3z3iusr7s,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"I've set up a new labs project for ExtensionDistributor to serve tarballs instead of using github. Example tarball: http://extdist.wmflabs.org/?version=REL1_23&ext=VisualEditor
+
+This will provide better privacy for users, and also fix a few bugs like submodule support (bug 44022).
+
+Yuvi is helping puppetize the setup.
+
+I want to temporarily enable ExtensionDistributor on testwiki, point it labs, make sure there are no issues, and then turn it on on mediawiki.org.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405545060,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-nu7ycsxlgziqvsqjceef,task_description,resolved
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,Should we track download counts for the tarballs? :),1406831216,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"Deployed, nothing looks broken! :D",1406830792,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"This will go live tomorrow, when 1.24wmf16 hits mediawiki.org",1406756544,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"Change 150589 merged by jenkins-bot:
+Switch ExtensionDistributor to serve tarballs from extdist.wmflabs.org
+
+https://gerrit.wikimedia.org/r/150589",1406742934,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"Change 150589 had a related patch set uploaded by Legoktm:
+Switch ExtensionDistributor to serve tarballs from extdist.wmflabs.org
+
+https://gerrit.wikimedia.org/r/150589",1406741479,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"New plan after talking with Chad: have ExtensionDistributor get a list of branches from Gerrit's API (I5c4ca2ee13f256260a7fe9b703af5fbdb902db66), and just assume that the tarballs exist on extdist.wmflabs.org. This way prod will never have to talk to labs.
+
+> Yuvi is helping puppetize the setup.
+
+I63d285612bd30d24b83718c4c8967144d146afeb 
+
+> I want to temporarily enable ExtensionDistributor on testwiki, point it
+> labs, make sure there are no issues, and then turn it on on mediawiki.org.
+
+My half-re-write of the extension makes it so this really isn't possible :/",1406360119,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Edit the page
+3.Now click on the ""Edit Source"" tab
+4.Click on the option ""Discard Changes""
+
+Observed Result:
+It redirects to the edit source mode of the main page .
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14497}",1405544880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekrm36buebgsetzut4ox,task_description,resolved
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",Verified the fix in production en.wiki,1406314095,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap is a useful reference for Wikimedia deployments,1405964514,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","(In reply to Alex Monk from comment #7)
+> Are you sure that wiki is running a version of VisualEditor with the fix for
+> this bug? I'm pretty sure Wikipedia is supposed to get this change is on
+> Thursday...
+
+I see. I thought it was already deployed to all wikis. Sorry.",1405964265,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",Are you sure that wiki is running a version of VisualEditor with the fix for this bug? I'm pretty sure Wikipedia is supposed to get this change is on Thursday...,1405964025,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","It still redirects to the main page, if you choose some version from the history page and then do the same.
+
+1) https://en.wikipedia.org/w/index.php?title=Test&oldid=614834396
+2) click edit
+3) (make some changes to the page)
+4) switch to source editing
+5) discard changes
+and you're again editing the main page",1405963079,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",Verified the fix in test2,1405720820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","Change 146956 merged by jenkins-bot:
+Set title of page to use if discarding changes when changing to the wikitext editor
+
+https://gerrit.wikimedia.org/r/146956",1405555740,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","Change 146956 had a related patch set uploaded by Alex Monk:
+Set title of page to use if discarding changes when changing to the wikitext editor
+
+https://gerrit.wikimedia.org/r/146956",1405549014,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",This is a fun one. Are we passing '' to the API instead of the page name?,1405546990,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",It happens also if I switch to Edit Source mode from the Switch to Source Editing option.,1405545105,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"Script error for each citation
+
+Test Environment-test2
+Steps to Reproduce-
+
+Scenario#1-
+1> Select the ” Cite “ drop down and add a Journal, News, Book,  one of each citations.
+2> Now click on “Insert” and select “Media”. Click on any picture returned in the dialog(do not enter any search term)
+3> In the Media Settings dialog click on “Insert” again and select “Media” from the Caption toolbar. Click on any picture returned in the dialog.
+4> Now close all the dialogs. 
+5> Repeat again steps #2,3 and 4.
+6>In the main VE window  click on “Cite”  and select “Basic”. Reference dialog opens.
+5> In the Reference dialog select “Use an existing reference”.
+6> Script Error is shown as existing reference.
+
+Scenario#2-
+1> Go to the Media Settings dialog. 
+2> While General Settings is highlighted, select the ” Cite “ drop down and add a Journal, News, Book,  one of each citations to the Caption pane.
+3> Now click on “Insert “dropdown and select “Media”.
+4>Click on any picture in the media search dialog. Media Settings dialog pops. Close this dialog.
+5> Repeat steps 3 and 4 again.
+5> Notice that the previously opened Media Settings dialog is still open with the citations in the Caption pane.
+6> Click on “Cite” again and select “Basic”. Reference dialog opens.
+7> In the Reference dialog select “Use an existing reference”.
+8> Script Error is shown as existing reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14429}",1405466460,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-czceip6xh6hv5epzval5,task_description,resolved
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"okay, so there is no need to have a new bug on it I guess.",1407350346,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,Probably an effect of whatever caused this?,1407323763,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"The delay to load citations in RE-Use dialog is pretty noticeable now.Previously,it was not like that.Is it an effect of this fix?",1407263283,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,Issue Resolved in test2.,1406922194,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"This looks like it's now fixed.
+
+(Note that the ""re-use"" list can take a few seconds to update, so if you've just created a cite it may render as ""[4]"" rather than ""[4] Foo. Bar (Baz)"" which will happen later if you wait.
+
+Thanks, Krenair!",1406770961,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"(In reply to Rummana Yasmeen from comment #2)
+> However there is one issue here, when you first time add any reference, and
+> open use existing reference dialog, the reference name will not appear but
+> after that if you do any other action like adding a media, or a link or a
+> reflist it appears.
+
+That sounds like bug 67342. Is this valid?",1406769368,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"This bugs is found in test2 so the reason why it is showing script error for the Cite News,Cite Journal,Cite Book but not Cite Web, the template data for those options are not defined in test2.
+So if you just add those Cite Options and add a reflist , you will also see script errors in the reference list.
+
+
+However there is one issue here, when you first time add any reference, and open use existing reference dialog, the reference name will not appear but after that if you do any other action like adding a media, or a link or a reflist it appears.",1405538788,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"(In reply to Ritu Swain from comment #0)
+> Created attachment 15949 [details]
+> Script error for each citation
+> 
+> Test Environment-test2
+> Steps to Reproduce-
+> 
+> Scenario#1-
+> 1> Select the ” Cite “ drop down and add a Journal, News, Book,  one of each
+> citations.
+> 2> Now click on “Insert” and select “Media”. Click on any picture returned
+> in the dialog(do not enter any search term)
+> 3> In the Media Settings dialog click on “Insert” again and select “Media”
+> from the Caption toolbar. Click on any picture returned in the dialog.
+> 4> Now close all the dialogs. 
+> 5> Repeat again steps #2,3 and 4.
+> 6>In the main VE window  click on “Cite”  and select “Basic”. Reference
+> dialog opens.
+> 5> In the Reference dialog select “Use an existing reference”.
+> 6> Script Error is shown as existing reference.
+
+The problem here is the ""re-use existing reference"" code seems to rely on there being a reference list on the page (or there having been one at some point in this edit?) – if there's no reference list yet, it shows the references as blank or with a Lua script error. Is this something as simple as populating the internal list as needed?
+
+**Attached**: {F14429}",1405526743,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Steps to reproduce:
+
+1.Open the media settings dialog for an image
+2.Edit something in the caption field to enable the ""Apply Changes"" button
+3.Undo the edit from the toolbar
+
+Observed Result:
+The ""Apply Changes"" button still remains enabled
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1405450800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_description,resolved
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog",Verified the fix in production,1411070271,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog",Verified the fix in test2,1410554273,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog",Verified the fix in Betalabs,1409961205,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Change 152790 merged by jenkins-bot:
+Check for changes in the model
+
+https://gerrit.wikimedia.org/r/152790",1409864834,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Change 152790 had a related patch set uploaded by Mooeypoo:
+[wip] Check for changes in the model
+
+https://gerrit.wikimedia.org/r/152790",1407431083,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Change 150478 abandoned by Mooeypoo:
+Check for changes in media dialog
+
+Reason:
+Redone in a different commit
+
+https://gerrit.wikimedia.org/r/150478",1407431002,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Change 150478 had a related patch set uploaded by Mooeypoo:
+Check for changes in media dialog
+
+https://gerrit.wikimedia.org/r/150478",1406692874,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"For repositories that we're (also) mirroring at a custom name, they are currently being mirrored twice.
+
+For example:
+
+* https://github.com/wikimedia/VisualEditor
+  https://github.com/wikimedia/VisualEditor-VisualEditor
+
+
+* https://github.com/wikimedia/oojs
+  https://github.com/wikimedia/oojs-core
+
+* https://github.com/wikimedia/puppet-kafka
+  https://github.com/wikimedia/operations-puppet-kafka
+
+This is confusing and also decentralises things like Watching and Fork tracking. But, more importantly, it also makes our Star rating and Pull requests harder to maintain.
+
+
+I don't know whether we intentionally do both, or whether it was just easier to implement this way.
+
+I'd recommend we get rid of the full names where we want to publish the repo under a different name.
+
+If it was a conscious choice to do this I'm curious why. The only reason I can think of is to make them easier to find on GitHub, which is hardly a big issue since they have excellent search for repo names right on https://github.com/wikimedia.
+
+Another reason might be being able to automatically generate a GitHub address for a Git repo, but I'm not sure that's a big issue.
+
+Also note that GitHub supports renaming of repositories and automatically keeps redirects[1]. So we can remove the ""unwanted"" names from Gerrit replication config and have our github.com/wikimedia admins delete the repos and create a redirect (by renaming the good one to the bad one and then renaming it back).
+
+As an example I've created a redirect from https://github.com/wikimedia/mediawiki to https://github.com/wikimedia/mediawiki-core. Eventually this should be done the other way around but this was easier to set up since Gerrit replag currently did not push to /mediawiki yet (unlike oojs and VisualEditor).
+
+
+[1] https://github.com/blog/1508-repository-redirects-are-here
+[2] https://help.github.com/articles/renaming-a-repository
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1405448880,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cvdip7jn2gnnatmluyma,task_description,resolved
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"Fwiw, we renamed the parsoid repository to https://github.com/wikimedia/parsoid with no ill effects. Even the travis tests kept working.",1415722581,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"Change 167162 merged by Dzahn:
+gerrit: Remove duplicate mirrors
+
+https://gerrit.wikimedia.org/r/167162",1413846804,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"Change 167162 had a related patch set uploaded by Krinkle:
+gerrit: Remove duplicate mirrors
+
+https://gerrit.wikimedia.org/r/167162",1413513240,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"The redirects GitHub has in place apply both to the HTTP protocol (web interface) as well as the Git interface itself. We can simply remove the duplicate ""pretty name"" replications and perform the renames on GitHub. That way there's only one repo Gerrit is pushing two and both urls work.
+
+I've gone ahead and done this with mediawiki-core as example.
+
+From Gerrit's perspective it's a straight up replication from gerrit:mediawiki/core to github:mediawiki-core. There is no fancy-name duplicate set up for it.
+
+On GitHub it has been renamed from mediawiki-core with a full redirect in place. Gerrit is now effectively pushing to https://github.com/wikimedia/mediawiki while all urls and logs for mediawiki-core continue to work as expected.",1413512026,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"(In reply to christian from comment #1)
+> > If it was a conscious choice to do this I'm curious why.
+> 
+> We want all gerrit repos replicated on github.
+> 
+> We could setup replication for each repository in our gerrit
+> separately. That would allow full control of repository names at
+> github. But it is tedious, time-consuming, and has other warts too.
+> 
+
+> So in order to escape such a messy, verbose replication setup, gerrit
+> replicates each and every projects to github under the name that gets
+> used on gerrit [1]. For this replication, we do not prune leading
+> paths, as that would map different names on gerrit to the same names
+> on github [2].
+
+I wasn't suggesting that we do it manually. All repos should be replicated. I'm also well-aware of naming conflicts if we were to prune leading paths. Nobody was suggesting that.
+
+> However, some people felt strongly that they needed a better
+> repository name on github, or had a following on github that they
+> would not want to loose. So they had an additional, separate
+> replication target set up. And hence, those repositories get replicated
+> twice to github. Once for the canonical name. And a second time for
+> the custom name of their liking.
+
+Exactly. And there's no reason to have to replications. It should be easy to remove the additional one. For projects using github more publicly, they tend to have a better name there to hide internal implementation details of Gerrit or Wikimedia (e.g. VisualEditor, MediaWiki and OOjs have stupidly named repos in gerrit of VisualEditor/VisualEditor and oojs/core and mediawiki/core, this is due to conventions and limitations in our use of Gerrit).
+
+> > Also note that GitHub supports renaming of repositories and
+> > automatically keeps redirects[...]
+> 
+> Thanks! That wasn't available when we added custom replication.
+> We could use that to solve most issues.
+> 
+> > As an example I've created a redirect from
+> > https://github.com/wikimedia/mediawiki to
+> > https://github.com/wikimedia/mediawiki-core. Eventually this should be
+> > done the other way around [...]
+> 
+> Not too sure about this one.
+> Doing it “the other way around” would make it even more confusing for
+> people, because the “canonical” github name would differ from the
+> gerrit name too much to be able to map it clearly.
+> 
+
+I'm not sure you understood that I meant.
+
+Right now we replicate all repos from <gerrit-id> to github:<gerrit-id-escaped> and have additional replications for those that needed better names.
+
+I'm saying: Omit the ones with custom names from the wildcard replication so that there's only one.
+
+For existing repos already replicated twice, we'll have to manually remove the (now stale) repository from the admin panel at github. While at it, we can turn those into redirects to the custom name to make sure any urls stay working.",1408969654,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"> If it was a conscious choice to do this I'm curious why.
+
+We want all gerrit repos replicated on github.
+
+We could setup replication for each repository in our gerrit
+separately. That would allow full control of repository names at
+github. But it is tedious, time-consuming, and has other warts too.
+
+So in order to escape such a messy, verbose replication setup, gerrit
+replicates each and every projects to github under the name that gets
+used on gerrit [1]. For this replication, we do not prune leading
+paths, as that would map different names on gerrit to the same names
+on github [2].
+
+However, some people felt strongly that they needed a better
+repository name on github, or had a following on github that they
+would not want to loose. So they had an additional, separate
+replication target set up. And hence, those repositories get replicated
+twice to github. Once for the canonical name. And a second time for
+the custom name of their liking.
+
+> Also note that GitHub supports renaming of repositories and
+> automatically keeps redirects[...]
+
+Thanks! That wasn't available when we added custom replication.
+We could use that to solve most issues.
+
+> As an example I've created a redirect from
+> https://github.com/wikimedia/mediawiki to
+> https://github.com/wikimedia/mediawiki-core. Eventually this should be
+> done the other way around [...]
+
+Not too sure about this one.
+Doing it “the other way around” would make it even more confusing for
+people, because the “canonical” github name would differ from the
+gerrit name too much to be able to map it clearly.
+
+
+
+[1] github does not like “/”s in repo names, so we're having them
+    replaced by “-”s.
+
+[2] For example we currently have three repositories in gerrit that
+    end in “/data”.
+    Or which of “analytics/kraken” and “analytics/vagrant/kraken”
+    should become github's “kraken”?
+    Same problems for “/Nostalgia”.",1405502216,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+VisualEditor: Scroll bar is appearing inside the language inspector,"Screenshot
+
+Open a language inspector, a scroll bar is appearing inside the inspector
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14372}",1405448700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aay645uqkadlmx7yyijx,task_description,resolved
+VisualEditor: Scroll bar is appearing inside the language inspector,Verified the fix in production,1407188930,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aay645uqkadlmx7yyijx,task_subcomment,NA
+VisualEditor: Scroll bar is appearing inside the language inspector,Verified the fix in test2,1406324116,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aay645uqkadlmx7yyijx,task_subcomment,NA
+VisualEditor: Scroll bar is appearing inside the language inspector,Verified the fix in Betalabs,1406160613,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aay645uqkadlmx7yyijx,task_subcomment,NA
+VisualEditor Mobile: Text cannot be pasted into link inspector search field from mobile browser,"Tap, or tap and hold on text input field in tablet VE, expected behavior, native iOS copy/paste flag should be shown, but it us not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405412580,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-rihr5cwlyy5m2utltcfx,task_description,resolved
+VisualEditor Mobile: Text cannot be pasted into link inspector search field from mobile browser,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487876,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rihr5cwlyy5m2utltcfx,task_subcomment,NA
+VisualEditor Mobile: Text cannot be pasted into link inspector search field from mobile browser,Needs re-testing.,1430336362,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rihr5cwlyy5m2utltcfx,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Steps to reproduce:
+
+1.Insert an image in a page
+2.Change the size of the image by going to Custom tab
+3.Click on ""Apply Changes""
+4.Now again open the media settings dialog and switch to default tab
+
+
+Observed Result:
+Previously as soon as user switched to default tab, it used to set the text fields to default size, but now its keeping the custom size values.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405363500,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-74pysrayjf4h6tgvqp3q,task_description,resolved
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Verified the fix in production,1411069966,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Verified the fix in test2,1410556646,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Verified the fix in Betalabs,1409945915,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 158395 merged by jenkins-bot:
+Set default dimensions based on original dimensions
+
+https://gerrit.wikimedia.org/r/158395",1409864506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 158395 had a related patch set uploaded by Mooeypoo:
+Set default dimensions based on original dimensions
+
+https://gerrit.wikimedia.org/r/158395",1409844685,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Still reproducible...,1409255728,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 149217 merged by jenkins-bot:
+Make the image model persistent
+
+https://gerrit.wikimedia.org/r/149217",1409242085,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 149217 had a related patch set uploaded by Mooeypoo:
+Make the image model persistent
+
+https://gerrit.wikimedia.org/r/149217",1408487289,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","This is again happening in production for this image:https://en.wikipedia.org/wiki/File:Black_sandbox.JPG
+
+Go to this page: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&oldid=619869934
+
+Go to the Media settings>Advanced Settings for this image.Switch to default tab.
+
+Observe that, the size values are still showing 22x17 which should be 220x165 as soon as I switch to Default tab.
+If you click on Apply Changes and reopen this dialog , still you will see its showing 22x17 instead of 220x165.
+If you Save the page and then reopen the page and the media settings dialog only then you will see the size value got changed to 220x165",1407186077,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","I cant reproduce it now , the problem was after changing the custom size value, when i was clicking on default tab , it was not changing the size values into default on the size value fields.But now it seems like doing that.",1406759565,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","I can't manage to reproduce this in master or in beta labs.
+
+When a new image is inserted, the default behavior is that it has 'default' size. If the user goes to the size widget and just clicks the 'custom' button, it will transform the existing (default) values to custom values (so, the values are the same as the default, but they are literally expressed).
+
+So the values are the same because the user didn't change them, but the difference is whether the image is default or limited in size (despite the fact both sizes are functionally the same)
+
+For instance, for the image ""Chef's knife grip.jpg"" in beta labs:
+
+Clicking ""Custom"" size will result in this wikitext:
+
+[[File:Chef's knife grip.jpg|thumb|200x200px]]
+
+Clicking ""Default"" size will result in this wikitext:
+
+[[File:Chef's knife grip.jpg|thumb]]
+
+That's the expected result. Is something else happening? I can't reproduce a bug.",1406745809,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",This is happening again (!) in Betalabs now,1406744714,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Verified the fix in test2,1406323644,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 147219 merged by jenkins-bot:
+Make the image model work without a node
+
+https://gerrit.wikimedia.org/r/147219",1406161977,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 147219 had a related patch set uploaded by Mooeypoo:
+Make the image model work without a node
+
+https://gerrit.wikimedia.org/r/147219",1405978510,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add some categories
+3.Click on the newly added category to bring up the context menu for the category
+
+Observed Result:
+
+The context menu for the newly added category is appearing as blank with no option to specify ""sort this page as if it is called"" field value.
+
+See the screeshot attached
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14597}",1405110420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftd3677o2fooxu3axvei,task_description,resolved
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,Verified the fix in production en.wiki,1406316351,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,Verified the fix in test2,1405724443,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,BetaLabs gremlin. Blargh.,1405123633,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,Works for me without debug=true...,1405123401,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,Goes away when debug=true is called – maybe a deployment/BetaLabs gremlin issue?,1405122521,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"[[https://en.wikipedia.org/wiki/Wikipedia:Media_Viewer/June_2014_RfC|Wikipedia:Media Viewer/June 2014 RfC]]
+
+The consensus on the English Wikipedia is to disable Media Viewer by default.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/Wikipedia:Media_Viewer/June_2014_RfC
+**See Also**:
+* {T71080}
+* {T71292}",1405031700,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_description,declined
+Disable Media Viewer by default on the English Wikipedia,"(In reply to WhatamIdoing from comment #2)
+> Changing default user preferences means overriding the choices of registered
+> editors who actually want the feature (including thousands of editors who
+> voluntarily opted-in before MediaViewer was made avaialble by default).  
+> 
+> It's too bad that MediaWiki doesn't have a good one-click system for
+> changing prefs, like a ""Click here to enable X"" button or pop-up.  It'd be
+> so much easier than telling hundreds of users ""Go to Special:Preferences,
+> click to this tab, scroll halfway down, find this item, tick the box, scroll
+> all the way down, save the page.""
+
+That's an interesting idea and I've filed it as bug 67846.",1405075470,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"(In reply to Brent Laabs from comment #10)
+> MV tells users that they have to attribute CC0 and PD images (they don't).
+
+This is https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/736
+
+> I wanted to see the message that was in the public domain attribution message, 
+> so I clicked in the message field, and pressed the right arrow to see the end 
+> of the selection -- oops!  Next image.
+
+We try to make copying the message very easy, which means the text gets focused and preselected automatically from time to time (e.g. when switching tabs). If it would capture keystrokes on top of that, that would result in a very confusing behavior (prev/next would basically stop working when you open the panel).
+
+Opened bug 67835 about the underlying issue though, which is that it should be possible to just read these texts without copying them.",1405051614,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"(In reply to Erik Moeller from comment #9)
+> even if you are still unhappy with the result.
+
+Erik, my level of satisfaction is irrelevant. As I expressed in the Commons RfC, ""I Don't Like It""-style votes are not valuable, and should not be counted in evaluating consensus.
+
+https://commons.wikimedia.org/w/index.php?title=Commons:Requests_for_comment/Media_Viewer_software_feature&diff=128325247&oldid=128324966
+
+It seems that you and the Multimedia Team, though, don't take the same view on the other side. You seem to attach great importance to the fact that you reached out to some Wikipedians, and they responded ""I Like It.""
+
+The ""NOTCONSENT"" policy cited makes it clear that WMF must act on its own discretion on legal matters, and I have no quarrel with that. Certainly there are cases where consensus has no place. But this is not one of them. On matters that involve sophisticated judgment -- is it your position that WMF is capable of evaluating what constitutes good judgment, and local communities are not?
+
+It seems that you are quick to cite your community engagement practices when doing so serves your objective of deploying the software, but quick to dismiss community input that do not support that objective.",1405043664,PHID-USER-am4534nrql73corsejoh,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"**bslaabs** wrote:
+
+I have to admit that I didn't like MediaViewer at first, but I read Erik's comments, and decided to give it another try.  And it's definitely improving.  It's now at the quality level of an early beta release, rather than the alpha release level it was at when it was first implemented.
+
+The fullscreen button was surprising at first, but I can see the use of it.  But after that, it only took me 2 minutes to find two bugs. MV tells users that they have to attribute CC0 and PD images (they don't).  I wanted to see the message that was in the public domain attribution message, so I clicked in the message field, and pressed the right arrow to see the end of the selection -- oops!  Next image.
+
+I'm not a person with highly established workflows -- my contributions to English Wikipedia are around one edit per month, and I use other wiki software.  Media Viewer is just confusing, and feels incomplete.  It's not my workflow breaking, it's a new feature's interface being confusing.
+
+I'm really disappointed that the WMF seems to want to force this on the community, when it's so clearly a product still in need of development.  And I'm more disappointed that the only response to the community has been based on Silent Majority arguments and a disdain for experienced members of the community.
+
+If this bug is marked WONTFIX, where can I file a bug about the WMF?",1405042116,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"Pete: Not at all. We've paid close attention to the requests by readers and editors throughout the development process. In fact, there are aspects of Media Viewer (like the prominent Commons links) which I believe can be directly traced to your own early feedback, even if you are still unhappy with the result. 
+
+Recent significant changes include an off switch for readers, and an easy click-through link to the full resolution version. I think you will also appreciate the attribution hints recently added to the download tab (see here: https://www.mediawiki.org/wiki/Lightbox_demo#mediaviewer/File:Swallow_flying_drinking.jpg ). Some of these changes were made _while_ the RFC took place.
+
+We'll continue to improve Media Viewer, but we'll also focus more attention in coming weeks on the upload process and on structured data support in partnership with Wikidata (the latter should help ensure that we can more consistently pull useful metadata into applications like Media Viewer, and potentially add some basic edit functionality to the overlay as well).",1405040744,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"(In reply to Erik Moeller from comment #7)
+
+Erik, the RfC is full of critiques of the methodology that led the WMF team responsible for this feature to the conclusion that it serves the reader better. Through this action you seem to be saying that the WMF team is correct by virtue of its being the WMF team, and the English Wikipedia community is wrong by virtue of its being the English Wikipedia community.",1405039576,PHID-USER-am4534nrql73corsejoh,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"Steinsplitter:
+
+It's longstanding WMF policy and practice to apply judgment to community RFCs and requests regarding software and configuration changes on a case-by-case basis, depending on the nature of the requested change, the level of participation, the impact on readers/editors, etc. See: https://meta.wikimedia.org/wiki/Limits_to_configuration_changes
+
+In this case, we will keep the feature enabled by default (it's easy to turn off, both for readers and editors), but we'll continue to improve it based on community feedback (as has already happened in the last few weeks).",1405038276,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"@Erik Moeller:
+Why the Wikimedia Fondation as content provider overwrites community consensus?
+Is this only a ""i don't like to follow communety consensus"" WONTFIX or a Office Action?
+
+Per shellpolicy there is enough consensus to merge this change.",1405038074,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"(In reply to WhatamIdoing from comment #2)
+> It's too bad that MediaWiki doesn't have a good one-click system for
+> changing prefs, like a ""Click here to enable X"" button or pop-up.  It'd be
+> so much easier than telling hundreds of users ""Go to Special:Preferences,
+> click to this tab, scroll halfway down, find this item, tick the box, scroll
+> all the way down, save the page.""
+
+MediaViewer does provide that functionality, actually (it's at the bottom of the metadata panel).",1405037726,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"Closing WONTFIX per previously provided explanation:
+https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Media_Viewer/June_2014_RfC&diff=prev&oldid=616407785",1405037582,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"I see no reason in honoring this request. MediaViewer only displays media in a different way, *and* it can be disabled in your preferences. This is normal software evolution.
+
+It is nothing like VisualEditor, which was disruptive for all editors. This is not, and editor consensus cannot dicatate how all *readers* should experience the use of media.",1405036716,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"Changing default user preferences means overriding the choices of registered editors who actually want the feature (including thousands of editors who voluntarily opted-in before MediaViewer was made avaialble by default).  
+
+It's too bad that MediaWiki doesn't have a good one-click system for changing prefs, like a ""Click here to enable X"" button or pop-up.  It'd be so much easier than telling hundreds of users ""Go to Special:Preferences, click to this tab, scroll halfway down, find this item, tick the box, scroll all the way down, save the page.""",1405035696,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,Just need to set the default user option to 'false' really.,1405032080,PHID-USER-4n6zx4s5v23pjdztvtnr,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception","Steps to reproduce:
+
+1.Open a page with VE which has a reference note in it
+2.Now place your cursor after the reference note
+3.Press backspace to select the reference note
+4.Now press down key to go to the next line
+
+Observed Result:
+The cursor does not go to the next line and an error appears in the console:
+
+Uncaught NotFoundError: Failed to execute 'selectNode' on 'Range': The node provided is null. 
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404944220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bszbfrxj2jltj2nwse7z,task_description,resolved
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception",Verified the fix in production en.wiki,1406317860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception",Verified the fix in test2,1405721607,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception",Verified the fix in Betalabs,1405553568,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception","Change 146472 merged by jenkins-bot:
+Don't handle up/down on focusableNodes even if backwards
+
+https://gerrit.wikimedia.org/r/146472",1405444891,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception","Change 146472 had a related patch set uploaded by Esanders:
+Don't handle up/down on focusableNodes even if backwards
+
+https://gerrit.wikimedia.org/r/146472",1405437014,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Enter a search term
+4.Select the first image that appears on the search result
+4.Click on Change image immediately
+5.Enter a different search term
+6.Now try to select the first image on of the new search results 
+
+
+Observed Result:
+It throws an error:Uncaught TypeError: Cannot read property 'context' of undefined 
+
+and cannot select that image
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404935520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_description,resolved
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one",Verified the fix in production,1408046600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one",Verified the fix in test2,1407196170,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","Yeah, deeming this FIXED.",1406757740,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","When I tried to reproduce this bug (before the merge of the above fix), I kept getting this error in chrome:
+
+Uncaught TypeError: undefined is not a function commons.wikimedia.org/w/api.php?callback=jQuery1111024360889615491033_14067…set=0&prop=imageinfo&iiprop=dimensions%7Curl%7Cmediatype&iiurlheight=150:1
+
+And this in in firefox
+
+TypeError: jQuery111109862733512069084_1406742881657 is not a function
+	
+/**/jQuery111109862733512069084_1406742881657({""warnings"":{""main"":{""*"":""Unrecogn...
+
+And only after that I get an 'uncaught type error' that seems to be related to missing details in the image (like the caption document). It only happens right after the first API bug. I wasn't able to reproduce it after the 150054 fix was introduced. 
+
+The API response just before the bug appears seems to suggest that the information from the API is maybe mismatch to the loaded image, which is why I thought it was related. 
+
+The bug doesn't happen with this fix anymore (I can't reproduce it in master or in beta labs now that it's merged)",1406754030,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","(In reply to Moriel Schottlender from comment #1)
+> This seems to be the same jQuery/API issue we've had with calling the mw API
+> consecutively. When the API is queried more than once the callback function
+> goes haywire.
+> 
+> In debug mode when clicking the 'change image' (#4 in the above reproduce
+> list), the console error is
+> 
+> ""Uncaught TypeError: undefined is not a function"" 
+> api.
+> php?callback=jQuery111109575085956603289_1404944903047&format=json&uselang=en
+> &action=query&gene…:1
+
+That undefined function error is not related in any way, that's bug 59604.",1406740660,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","Change 150054 merged by jenkins-bot:
+MWMediaSearchWidget: Use json/jsonp for local/foreign api respectively
+
+https://gerrit.wikimedia.org/r/150054",1406740428,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","Change 150054 had a related patch set uploaded by Mooeypoo:
+MWMediaSearchWidget: Use json/jsonp for local/foreign api respectively
+
+https://gerrit.wikimedia.org/r/150054",1406678138,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","This seems to be the same jQuery/API issue we've had with calling the mw API consecutively. When the API is queried more than once the callback function goes haywire.
+
+In debug mode when clicking the 'change image' (#4 in the above reproduce list), the console error is
+
+""Uncaught TypeError: undefined is not a function"" 
+api.php?callback=jQuery111109575085956603289_1404944903047&format=json&uselang=en&action=query&gene…:1",1404945249,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes","Steps to reproduce:
+
+1.Open a page with VE which has image inside it
+2.Open the media settings dialog for the image
+3.Edit the values for the image size
+4.Without saving this change just close the Media Settings dialog
+5.Reopen the media settings dialog again and check the image size values
+
+Observed Result:
+It shows the changed value even though you have not saved it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67684",1404849360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gnfxkxgge6jy5yegpul5,task_description,resolved
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes",Verified the fix in production en.wiki,1406317590,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gnfxkxgge6jy5yegpul5,task_subcomment,NA
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes",Verified the fix in test2,1405723196,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gnfxkxgge6jy5yegpul5,task_subcomment,NA
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes","Change 146513 merged by jenkins-bot:
+Update VE core submodule to master (ad18102)
+
+https://gerrit.wikimedia.org/r/146513",1405550634,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gnfxkxgge6jy5yegpul5,task_subcomment,NA
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes","Change 146513 had a related patch set uploaded by Mooeypoo:
+Work on a cloned scalable when editing images
+
+https://gerrit.wikimedia.org/r/146513",1405459529,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gnfxkxgge6jy5yegpul5,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Steps to reproduce:
+
+1.Open a page with VE which has an image inside it
+2.Open the advanced settings dialog for that image 
+3.Type something in the Custom fields 
+
+Observed Result:
+The Apply changes button does not get enabled upon changing the size value, it should change the tab to custom and enable the button
+
+Environment:Betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67687",1404848100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a532f3kpz7dqjttdx5l3,task_description,resolved
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button",*** Bug 68014 has been marked as a duplicate of this bug. ***,1406427644,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button",Verified the fix in production en.wiki,1406317798,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button",Verified the fix in test2,1405723080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Change 146682 merged by jenkins-bot:
+Listen to widget changes in MediaDialog
+
+https://gerrit.wikimedia.org/r/146682",1405550963,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Change 146676 merged by jenkins-bot:
+Switch to 'custom' when MediaSizeWidget updates
+
+https://gerrit.wikimedia.org/r/146676",1405543080,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Change 146682 had a related patch set uploaded by Mooeypoo:
+Listen to widget changes in MediaDialog
+
+https://gerrit.wikimedia.org/r/146682",1405477222,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Change 146676 had a related patch set uploaded by Mooeypoo:
+Switch to 'custom' when MediaSizeWidget updates
+
+https://gerrit.wikimedia.org/r/146676",1405476932,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button",It also happens when you reopen an image which was previously has been set to a custom size and try to edit those values.,1404848767,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with mobile VE with iOS Safari
+2.Tap the cursor on a link to bring up the context menu for it
+3.Now tap at the end of some other text to place the cursor there
+
+Observed Result:
+The context menu for the previous link is appearing on top of the article.
+
+
+Environment : Betalabs and test2
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67433
+
+**Attached**: {F14661}",1404773940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_description,resolved
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document",Verified the fix in production,1408047291,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document","Both the cases got resolved, checked in test2",1407265581,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document",I think this is now fixed too.,1406747354,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document","Another case to get such issue could be:
+
+
+If you delete the content of a page which had a link, it shows the context menu for the deleted link on a blank page, I suppose the fix for the original issue, should fix this case as well?",1404775519,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_subcomment,NA
+"VisualEditor: ""Make full Size"" is not enabling ""Apply changes"" button therefore cannot make any image fullsize","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to the Advanced Settings of an image
+4.Click on ""Make full size""
+
+
+Observed Result:
+The ""Apply Changes"" button is still disabled , cannot make any image full size
+
+Environment:test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404764520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wdsm7d6qbu5bt75ivacj,task_description,resolved
+"VisualEditor: ""Make full Size"" is not enabling ""Apply changes"" button therefore cannot make any image fullsize",Verified the fix in production,1405625917,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wdsm7d6qbu5bt75ivacj,task_subcomment,NA
+"VisualEditor: ""Make full Size"" is not enabling ""Apply changes"" button therefore cannot make any image fullsize",Verified the fix in test2,1405035306,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wdsm7d6qbu5bt75ivacj,task_subcomment,NA
+"VisualEditor: ""Make full Size"" is not enabling ""Apply changes"" button therefore cannot make any image fullsize","This was the same issue as https://bugzilla.wikimedia.org/show_bug.cgi?id=66863
+The following commit fixed it:
+
+Apply 'original size' to images
+
+https://gerrit.wikimedia.org/r/144637",1404865232,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wdsm7d6qbu5bt75ivacj,task_subcomment,NA
+Enable Visual Editor by default on pt.Wikiversity,"Ni!
+
+Since early this year we at pt.wikiversity have used the Visual Editor as an opt-in ""beta feature"".
+
+After this experimental phase, we have agreed that we want the Visual Editor to be enabled as default editor for everyone on pt.wikiversity, including unregistered users.
+
+https://pt.wikiversity.org/wiki/Wikiversidade:Esplanada#Habilitar_editor_visual_por_padr.C3.A3o
+
+We'd really appreciate if this could happen before the end of the July, since classes in Brazil start on early August.
+
+Cheers,
+Solstag
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1404719340,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-kckucons2r46xrc5a3xw,task_description,resolved
+Enable Visual Editor by default on pt.Wikiversity,"(Note that it will take a 30 days for the cache to be purged, so pages that aren't edited before then will appear to only have one tab to logged-out users until the pages are purged, edited, or the cache expires.)",1404775551,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kckucons2r46xrc5a3xw,task_subcomment,NA
+Enable Visual Editor by default on pt.Wikiversity,Now done.,1404775431,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kckucons2r46xrc5a3xw,task_subcomment,NA
+Enable Visual Editor by default on pt.Wikiversity,"Change 144476 merged by jenkins-bot:
+Enable VisualEditor by default on Portuguese Wikiversity
+
+https://gerrit.wikimedia.org/r/144476",1404774163,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kckucons2r46xrc5a3xw,task_subcomment,NA
+Enable Visual Editor by default on pt.Wikiversity,"Change 144476 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on Portuguese Wikiversity
+
+https://gerrit.wikimedia.org/r/144476",1404751768,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kckucons2r46xrc5a3xw,task_subcomment,NA
+Annotations are not preserved between edits,"**Author:** `drobbins`
+
+**Description:**
+Currently, any edits to a page will create a new page with no annotations, which makes this extension very difficult to use. You must look at the page history, and look at each revision for potential annotations that people may have added, and there is no icon or other indication that a revision actually *has* annotations. So they are likely to be lost or ignored.
+
+Ideally, annotations would be preserved through wiki edits and apply to newer revisions of pages. This would likely require updates to the editor.
+
+I realize that this may be technically challenging to implement. However, the preservations of annotations across edits does seem to be essential for really ensuring that this extension is useful (In fact, I wouldn't consider this annotation feature actually fully implemented until this is supported.)
+
+The true ideal implementation would be to display annotations in the editor, and like a true word processor, track changes to the underlying text to ensure that the annotation still existed even if the underlying text was modified in some way, as is how annotations work in word processors. This would have the added benefit of allowing editors to view annotations in real-time as they are editing a document, which would be extremely handy as many annotations deal with changes to the document that need to be made (or at least, should be addressed in some way during an edit cycle.
+
+Proposed design:
+
+[ editor window top ]
+
+
+[ Highlighted yellow: Editing this line in the editor.... ]
+
+
+[ editor window bottom ]
+
+[ Annotation: Display annotation(s) related to cursor position here. ]
+[ Button: add comment ] <-- editor would use this to add comment to existing annotation, related to any edits.
+
+I don't know if that is helpful for conveying how annotations could work in the editor, or not. I think this should be added to the default editor, and VisualEditor can add its own support. I don't think this feature should be VE-only.
+
+A possible work-around to make things a bit more bearable in the mean-time would be to add some kind of icon in the page history to indicate revisions that have annotations, so that the maintainer of the page can go through the page's history and look for annotations from people.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1404696600,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6tl7tgozycm2vk3qmwxb,task_description,declined
+Annotations are not preserved between edits,Declining per {T189753}. The extension is no longer maintained and has been archived.,1521636419,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-6tl7tgozycm2vk3qmwxb,task_subcomment,NA
+Annotations are not preserved between edits,"This is a valid report.  However, as you say it is technically challenging, and we did not intend the initial version to have this support.
+
+(In reply to Daniel Robbins from comment #0)
+> A possible work-around to make things a bit more bearable in the mean-time
+> would be to add some kind of icon in the page history to indicate revisions
+> that have annotations, so that the maintainer of the page can go through the
+> page's history and look for annotations from people.
+
+That's a good idea.  Filed as bug 67939.",1405227656,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-6tl7tgozycm2vk3qmwxb,task_subcomment,NA
+"VisualEditor: On wikis where anons can't create pages, you aren't told this until you try and save","Admittedly there are no links to take you to edit the page, but navigating to New_page?action=edit gives you and error, whereas New_page?veaction=edit let's you start editing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404562740,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ts644nvpin7nzxjkmyqi,task_description,resolved
+"VisualEditor: On wikis where anons can't create pages, you aren't told this until you try and save","Change 144275 merged by jenkins-bot:
+Give a notice if the user isn't allowed to create the page
+
+https://gerrit.wikimedia.org/r/144275",1406074327,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ts644nvpin7nzxjkmyqi,task_subcomment,NA
+"VisualEditor: On wikis where anons can't create pages, you aren't told this until you try and save","Change 144275 had a related patch set uploaded by Alex Monk:
+Give a notice if the user isn't allowed to create the page
+
+https://gerrit.wikimedia.org/r/144275",1404587535,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ts644nvpin7nzxjkmyqi,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Parsoid must produce/preserve the metadata about additional ResourceLoader modules required by extension tags. (I've heard some gossip that it falls back to PHP parser to do this, so this should be easy to do.)
+
+For example, in PHP parser, ""<syntaxhighlight lang=php>$foo</syntaxhighlight>"" will add up to two modules to ParserOutput's $mModuleStyles:
+* 'ext.geshi.language.php' (there is such a module for every supported language)
+* 'ext.geshi.local' (if $wgUseSiteCss is true)
+
+This information must somehow be provided by the API used by VisualEditor.
+
+The minimum set of things that have to be provided is the ones provided by OutputPage::addParserOutputContent() in PHP, that is modules, module styles, module scripts, module messages and JS config vars. (These are available via the action=parse&prop=modules API in core.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1404491460,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_description,resolved
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,Presumably this is resolved by T162399,1632170096,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"There were two requests at wikimania for the rest of the stuff included in this bug.  Namely:
+* Link to JS necessary to render the page contents.  (Especially for maps modules, etc)
+* Some sort of machine-readable enumeration of the modules required (in case you wanted to do manual loading of CSS/JS/etc).",1437516471,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 215883 merged by jenkins-bot:
+Include RL style modules from parser functions in <head>
+
+[[https://gerrit.wikimedia.org/r/215883]]",1434394337,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"* https://gerrit.wikimedia.org/r/215874 (branch master): #mw1.26, #mw1.26wmf9
+",1433784601,PHID-USER-n4kveqwjjlpsb6ydn73h,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 215874 merged by jenkins-bot:
+Expose RL modules and js config vars in action=expandtemplates
+
+[[https://gerrit.wikimedia.org/r/215874]]",1433521008,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 215883 had a related patch set uploaded (by Marcoil):
+Include RL style modules from parser functions in <head>
+
+[[https://gerrit.wikimedia.org/r/215883]]
+",1433418438,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 215874 had a related patch set uploaded (by Marcoil):
+Expose ResourceLoader modules in action=expandtemplates
+
+[[https://gerrit.wikimedia.org/r/215874]]
+",1433413960,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"A little status update:
+
+What currently works:
+* Parsoid correctly includes style modules from extensions present in the page that add them through ResourceLoader, so that when requesting the HTML directly from Parsoid it's presented correctly.
+
+What doesn't:
+* Style modules added by parser functions, as the expandtemplates API doesn't expose them yet. A patch similar to  @jackmcbarn's https://gerrit.wikimedia.org/r/162123, but without including non-RL modules would solve this.
+* All non-style modules exposed through ResourceLoader (Javascript, global vars, messages…). Parsoid's HTML output doesn't load ResourceLoader client infrastructure, so it's difficult to correctly load those modules.
+
+I'm not sure if it's even a good idea to load non-style modules in Parsoid's HTML <head>, tbh, given that it's not really used independently by anything right now. I like @cscott's proposal of exposing the information in data-mw so that clients can use them as they see fit.
+
+So my proposed next steps would be:
+* Expose all modules in action=expandtemplates, excluding non-RL modules.
+* Add the style ones to Parsoid's <head> as we do now with extension ones.
+* Expose all modules (styles and all others) through data-mw.
+
+That way, for example, when VE receives just the body of a page for editing, it would look into the data-mw and load the modules it sees there, which would fix T69515 and related. Right now VE can't get that data directly as it's in Parsoid's <head>.",1433264911,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"BTW, i'm trying to move TMH from it's global context into a more isolated one, but i'm guessing that due to the state of this ticket, that will also mean that when that patch lands, it will actually break TMH videos when added by VE right ? Since the global handlers would be gone and the 'local' ones are not loaded yet ?
+
+https://gerrit.wikimedia.org/r/172556
+https://gerrit.wikimedia.org/r/172421
+",1426927796,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"The merged patch takes care of adding the appropriate CSS modules to the load list, but only for extensions. Some parser functions (e.g. Babel) also have CSS modules, there's a patch for MW that would allow Parsoid to know about them here:
+https://gerrit.wikimedia.org/r/162123",1411490244,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 160423 merged by jenkins-bot:
+Bug 67540 - Load extension CSS modules
+
+https://gerrit.wikimedia.org/r/160423",1411487498,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"As discussed on IRC, we'll do a first patch only for CSS support, and then expand on it with the rest of extensions' resources. We can continue using this bug for this and for C. Scott's proposal of exposing the modules in metadata.
+
+Btw, does anyone have examples of pages where an extension CSS causes Parsoid to render differently from PHP? I'd like to test the visual diffs with this patch. Thanks!",1410801157,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"(12:15:15 PM) gwicke: cscott: we should expose the list separately, but for browsers it's probably more efficient to still do some bundling
+(12:15:29 PM) gwicke: good to unbundle the per-page modules from the global ones though
+(12:15:35 PM) gwicke: right now those are all mixed afaik
+(12:18:03 PM) cscott-free: gwicke: agreed.  i'm thinking of exposing the list via data-mw (for example) while still providing the resource url in a <link> tag for browsers.",1410797922,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"I think we'll want the lowlevel information about the modules available (via data-mw?), in addition to having One True Resource Loader URL which will load them all.
+
+In particular two of OCG backends, the ZIM writer and the future parsoid-phantomjs-PDF backend, will want to download the set of resources used by a (potentially large) set of pages.  We don't want to have to download the same resources in slight variations over and over again.  If there are N different resources used on a wiki, there are 2^N different resource loader URLs which load various combinations of the N resources.  We'd rather just load the N resources once, even if that means we have to do a little extra work ourselves to order and merge them.",1410797849,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"There's a WIP patch now at https://gerrit.wikimedia.org/r/160423 that adds the extensions' CSS modules to the style link.
+
+If we also want to load further extension resources, like JS or messages, I suppose we'll have to add loading ResourceLoader's client first and let it load everything else. Is this the way we should go?",1410780309,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 160423 had a related patch set uploaded by Marcoil:
+WIP: Bug 67540 - Load extension CSS modules
+
+https://gerrit.wikimedia.org/r/160423",1410780110,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Ex: http://en.wikipedia.org/w/api.php?action=parse&format=json&page=MathML&prop=modules 
+
+includes
+
+""modulestyles"":[""ext.rtlcite"",""ext.math.styles"",""ext.geshi.language.xml"",""ext.geshi.local"",""ext.geshi.language.html5""]
+
+CSS modules for inclusion in the <head> would be a good start and will help reduce rendering diffs.",1410554810,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""","Screenshot
+
+Try to open any page with mobile VE in iOS Safari on Betalabs, the page does not load in VE and it shows an error at the bottom:
+""Error,can't load section""
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14353}",1404429960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-amg4rcgoazznjnphzquh,task_description,resolved
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Verified the fix in production,1405626073,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Verified the fix in test2,1405033146,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Fix by Roan unbreaking the databases.,1404755388,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",This seems to be working now :),1404755143,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Looks like this is caused by beta labs being in read-only mode. I can't edit on desktop either.,1404434217,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""","I can reproduce this on beta labs, but not in local master.",1404433574,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Sounds like it might be something on the MobileFrontend end.,1404431954,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Tap on a link
+3.When the context menu for that link appears tap on that
+4.Try to edit the link target name in the search box for link inspector
+5.No Link target page suggestions will appear inside the link inspector
+6.Close the link inspector
+7.Close the keyboard that is still appearing on CE
+
+Observed Result:
+The link suggestions are appearing on CE now
+See the screenshot attached
+
+
+This issue started happening after merging the new code for context menu on Mobile VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+
+**Attached**: {F14100}",1404258420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uv7harsaw6uegtz3aesy,task_description,resolved
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",Verified the fix in production,1405026565,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",Verified the fix in test2 with iOS,1404774256,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",Verified the fix in Betalabs with iOS,1404333352,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",Yay deployment.,1404331543,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",This is still happening on Betalabs.,1404323693,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open","Change 143524 merged by jenkins-bot:
+Use globalOverlay as the contextOverlay in MobileContext
+
+https://gerrit.wikimedia.org/r/143524",1404260536,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open","Change 143524 had a related patch set uploaded by Catrope:
+Use globalOverlay as the contextOverlay in MobileContext
+
+https://gerrit.wikimedia.org/r/143524",1404260386,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Do not place your cursor anywhere on CE but try to select a node 
+3.Scroll down the page
+
+Observed Result:
+The toolbar also gets repositioned down while scrolling down the page.
+
+It might get resolved with :https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+
+Still I am filing it as a separate issue.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60110
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67433
+
+**Attached**: {F14695}",1404250320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_description,resolved
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected",Verified the fix in production,1408047625,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected",Verified the fix in test2,1407266218,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected","Change 145185 had a related patch set uploaded by Jforrester:
+Improve fixed header in overlays on iOS
+
+https://gerrit.wikimedia.org/r/145185",1405985194,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected","Interestingly, this bug only seems to occur in landscape mode on iPad.",1405726465,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected","This is also happening for the context menu bar in Mobile VE.When you put your cursor for the first time on a node such as link, the context menu bar appears somewhere in the middle of the screen and then scrolls down as you scroll down the page.
+However, it does not happen once you close the keyboard and try it for the second time on that session.",1404257056,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,"Steps:
+
+1. Create page with VE
+2. Insert New Template
+3. Enter text that is the prefix of one or more pages in the User namespace with template data
+
+Expected result:
+
+Suggestions show up as:
+ User:Foo/Template:Example
+ User:Foo/Template:Unsigned
+ User:Foo/Template:Unsigned2
+
+Actual result:
+
+Suggestions show up as
+ :User:Foo/Template:Example
+ :User:Foo/Template:Unsigned
+ :User:Foo/Template:Unsigned2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404243060,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-bcsjdeldob7pksf2jsjk,task_description,resolved
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,"(In reply to Alex Monk from comment #3)
+> So this *should* be fixed this time...
+
+Famous last words. :-)",1405472563,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bcsjdeldob7pksf2jsjk,task_subcomment,NA
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,So this *should* be fixed this time...,1405465885,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-bcsjdeldob7pksf2jsjk,task_subcomment,NA
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,"Change 144497 merged by jenkins-bot:
+MWTitleInputWidget: Remove prefixColon option and use relative title instead
+
+https://gerrit.wikimedia.org/r/144497",1405462245,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bcsjdeldob7pksf2jsjk,task_subcomment,NA
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,"Change 144497 had a related patch set uploaded by Alex Monk:
+Get rid of my prefixColon config option from TitleInputWidget, use relative title
+
+https://gerrit.wikimedia.org/r/144497",1404761879,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bcsjdeldob7pksf2jsjk,task_subcomment,NA
+"""Maximum execution time"" error in JavaScriptMinifier while minifying QUnit test modules","It might possible to make this less likely by grouping them into smaller requests.
+
+The request is:
+
+---
+http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=Base64.js%7Ceasy-deflate.core%2Cdeflate%7Cext.eventLogging%2Cmantle%7Cext.eventLogging.tests%7Cext.flow.new.handlebars.tests%7Cext.flow.new.tests%7Cext.gettingstarted.user%7Cext.gettingstarted.user.tests%7Cext.guidedTour.lib%2Cstyles%7Cext.guidedTour.lib.internal%2Ctests%7Cext.mantle.handlebars%2Ctemplates%7Cext.templateData.test%7Cext.templateDataGenerator.core%7Cext.visualEditor.base%2Ccore%2Clanguage%2Cmediawiki%2Cmwalienextension%2Cmwcore%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlink%2Cmwmeta%2Cmwreference%2Cmwtransclusion%2Cstandalone%2Ctest%2CviewPageTarget%7Cext.visualEditor.core.desktop%7Cext.visualEditor.mwimage.core%7Cext.visualEditor.viewPageTarget.init%7Cjquery.accessKeyLabel%2CautoEllipsis%2CbyteLength%2CbyteLimit%2CcheckboxShiftClick%2Cclient%2Ccookie%2CgetAttrs%2ChighlightText%2Ci18n%2Cjson%2CmakeCollapsible%2Cmw-jump%2CmwExtension%2Cplaceholder%2Cqunit%2CtabIndex%2Cthrottle-debounce%2CvisibleText%7Cjquery.qunit.completenessTest%7Cjquery.uls.data%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2Cfeedback%2CjqueryMsg%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.api.edit%7Cmediawiki.language.init%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.guiders%2Cpluralruleparser%7Cmediawiki.page.ready%2Cstartup%7Cmediawiki.skinning.content.parsoid%7Cmediawiki.special.javaScriptTest%7Cmediawiki.ui.button%7Coojs%2Coojs-ui%2Crangy%7Cskins.vector.js%7Ctest.mediawiki.qunit.testrunner%7Ctest.sinonjs%7Cunicodejs.wordbreak&skin=vector&version=20140701T185441Z&*
+
+---
+
+The error response is:
+
+
+Fatal error: Maximum execution time of 30 seconds exceeded in /vagrant/mediawiki/includes/libs/JavaScriptMinifier.php on line 428
+
+Call Stack:
+    0.0021     656184   1. {main}() /vagrant/mediawiki/load.php:0
+    0.2177   10838400   2. ResourceLoader->respond() /vagrant/mediawiki/load.php:43
+    0.4901   11686616   3. ResourceLoader->makeModuleResponse() /vagrant/mediawiki/includes/resourceloader/ResourceLoader.php:543
+    2.1315   19034048   4. ResourceLoader->filter() /vagrant/mediawiki/includes/resourceloader/ResourceLoader.php:923
+    2.1480   19272904   5. JavaScriptMinifier::minify() /vagrant/mediawiki/includes/resourceloader/ResourceLoader.php:181
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404241500,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-2ccuu4qtfxpytbz5rhoh,task_description,resolved
+"""Maximum execution time"" error in JavaScriptMinifier while minifying QUnit test modules","I can't reproduce this anymore. See also:
+
+* {b7eb243d9204a40977761fb2453070825dfeab97} 
+* {T107377}
+
+Things are now minified in smaller chunks and also better re-used as a result.",1448401810,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2ccuu4qtfxpytbz5rhoh,task_subcomment,NA
+"""Maximum execution time"" error in JavaScriptMinifier while minifying QUnit test modules","This might be improved by enabling fsc caching for the VM: `vagrant config nfs_cache yes; vagrant reload`
+
+@dduvall and I would love feedback from power users on the pros/cons of using the fsc nfs cache.",1438044238,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-2ccuu4qtfxpytbz5rhoh,task_subcomment,NA
+"""Maximum execution time"" error in JavaScriptMinifier while minifying QUnit test modules","I'm hitting this issue now in my local vagrant - this really shouldn't be taking 30 seconds to load should it even if it's a big file..?
+",1438043688,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-2ccuu4qtfxpytbz5rhoh,task_subcomment,NA
+VisualEditor: Converting a numbered external link to a regular one from the link inspector drops the annotations,"Converting a MWNumberedExternalLinkNode to MWExternalLinkAnnotation from the UI (link inspector) loses annotations on the node, even though there is code in place that aims handle this.
+
+See the behavior of the 'convert' variable in ve.ui.MWLinkNodeInspector.prototype.getTeardownProcess.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404236940,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kpjfjaghlnt74hhgi5cv,task_description,resolved
+VisualEditor: Converting a numbered external link to a regular one from the link inspector drops the annotations,"Change 143387 merged by jenkins-bot:
+MWLinkNodeInspector: Actually preserve annotations when converting to link annotation
+
+https://gerrit.wikimedia.org/r/143387",1406076286,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kpjfjaghlnt74hhgi5cv,task_subcomment,NA
+VisualEditor: Converting a numbered external link to a regular one from the link inspector drops the annotations,"Change 143387 had a related patch set uploaded by Bartosz Dziewoński:
+MWLinkNodeInspector: Actually preserve annotations when converting to link annotation
+
+https://gerrit.wikimedia.org/r/143387",1404244053,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kpjfjaghlnt74hhgi5cv,task_subcomment,NA
+VisualEditor: Converting a numbered external link to a regular one from the link inspector drops the annotations,This is because the node is removed from DM before its annotations are copied. Let me just fix it while I'm at it. :),1404242888,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kpjfjaghlnt74hhgi5cv,task_subcomment,NA
+VisualEditor:  The Help menu does not scroll on small screens while using Monobook,"Steps to reproduce:
+
+1.  Make your browser window short (<400 pixels?).
+
+2.  Open a page using the Monobook skin, e.g., https://en.wikipedia.org/wiki/Nicholas_Rigby?veaction=edit&useskin=monobook.
+
+3.  Click the (?) button to open the Help menu.
+
+4.  Because of the short screen, the entire menu does not fit on the screen at once.  Try to scroll down to read the last line on the Help menu.
+
+
+The Help menu is not scrolling, so you can't see anything that doesn't fit on your screen.  This is not a problem in Vector.  I have confirmed this in both Safari 6.1.4 and Firefox 30.
+
+Original report:  https://ru.wikipedia.org/w/index.php?diff=63851178 from Sunpriat
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404228840,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-nu4jynpne3safxk75oss,task_description,resolved
+VisualEditor:  The Help menu does not scroll on small screens while using Monobook,This was fixed a while ago.,1413330573,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nu4jynpne3safxk75oss,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Screenshot
+
+Steps to reproduce:
+
+1.Rotate the screen of your iOS device to landscape
+2.Open a page with mobile VE
+3.Tap on a drop down menu which has lot of options under it like for now we have ""Reference"" menu
+4.Open that menu
+5.Try to select the options from the bottom of the menu such as ""Use an existing reference"" or ""Journal""
+
+Observed Result:
+Cannot select any of those options since the keyboard is always open and overlapping with the menu,and scrolling down menu again drags the screen back to the top
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14572}",1404174840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_description,resolved
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,The design of the interface has changed so much in the intervening four years that this bug is effectively resolved; the menus look significantly different now. and additionally interacting with any of them collapses the keyboard.,1535711851,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Confirming that, it is still occurring.",1416354295,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"I attempted to reproduce this using CrossBrowserTesting.com, but whenever I click on the ""Cite"" icon using it, the entire toolbar disappears. I can't tell if it's a real bug or the testing app being broken. All in all, this was a wonderful waste of time and I'm still unable to debug, much less fix, this bug (and I still believe it shouldn't be accurring anyway in the first place per comment 5).",1416092830,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"(In reply to Roan Kattouw from comment #3)
+> Juliusz explained to me that there's a bug in iOS Safari when the keyboard
+> comes up: the viewport becomes smaller, but measuring the viewport does not
+> take this into account. The hack Juliusz is currently using in
+> MobileFrontend to compensate for this is to arrange the document such that
+> the main viewport never scrolls, instead everything is wrapped in a
+> scrollable <div> that's exactly the size of the viewport.
+
+This seems to be _fixIosHeader() in /javascripts/Overlay.js in MF.
+
+
+> To address this bug, we would have to have menus clip to this wrapper div
+> rather than the body, and we would have to have them reevaluate their
+> clipping state (by calling .clip()) every time this wrapper <div> is resized.
+
+Why doesn't this already work? ClippableElements are supposed to be clipped to the closest scrollable element, and surely the MF overlay is closer than body.",1413299032,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Bumping over to Bartosz; this is an awkward three-way bug between VE, MobileFrontend and OOUI as I understand it. Fun. :-(",1412970371,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"(In reply to Roan Kattouw from comment #2)
+> Hmm, this sounds like a bug related to ClippableElement. The menu should
+> automatically clip and become scrollable when there isn't enough screen
+> space for it. You can see this on desktop if you resize the window. Maybe
+> iOS Safari isn't emitting a resize event, or is emitting an event we're not
+> listening to, or isn't giving us the correct viewport dimensions?
+
+Juliusz explained to me that there's a bug in iOS Safari when the keyboard comes up: the viewport becomes smaller, but measuring the viewport does not take this into account. The hack Juliusz is currently using in MobileFrontend to compensate for this is to arrange the document such that the main viewport never scrolls, instead everything is wrapped in a scrollable <div> that's exactly the size of the viewport. Then he listens for focus events, and attempts to scroll the viewport down by a large amount (9999px or something?). Under normal circumstances, this has no effect, but if the keyboard is up, the viewport will be scrollable and measuring how much it scrolled by gives you the height of the keyboard. He then adjusts the sizing of the wrapper <div> so it once again fits the viewport exactly.
+
+This is also part of why things sometimes behave very strangely when focus events are dropped or emitted at the wrong time, because then Juliusz's code may not notice that the keyboard has appeared or disappeared, and it may not adjust the size of the wrapper <div> when it should.
+
+To address this bug, we would have to have menus clip to this wrapper div rather than the body, and we would have to have them reevaluate their clipping state (by calling .clip()) every time this wrapper <div> is resized.",1409695738,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Hmm, this sounds like a bug related to ClippableElement. The menu should automatically clip and become scrollable when there isn't enough screen space for it. You can see this on desktop if you resize the window. Maybe iOS Safari isn't emitting a resize event, or is emitting an event we're not listening to, or isn't giving us the correct viewport dimensions?",1407962590,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Yep, I can confirm this on my iPad Air (iOS 7.1) when not using an external Bluetooth keyboard.
+
+In landscape mode with the keyboard open there is *very* little vertical space, only about 220px high, between the VE toolbar and the top of the keyboard -- vertically laid-out menus are probably not a good idea here.
+
+iOS text-selection menus tend to be laid out horizontally like a segmented toolbar presented as a popup from the selection itself; Android 4.x uses a horizontal action bar at the top of the screen.
+
+I would recommend going with some sort of horizontal button layout, perhaps as a second layer of toolbar.",1404224198,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","If I go to a page that has been redirected, the URL retains the original title instead of the redirected title. So if I enter VE and then refresh, I'm taken to the editing the original page instead of the redirect page.
+
+For example, go here: https://en.wikipedia.org/wiki/Zedonk, then click VE, then refresh the page. 
+
+URL should be changed to: https://en.wikipedia.org/wiki/Zebroid?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1404163440,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-jggh6lkqz7csocnbz4oo,task_description,declined
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title",That change has been merged and this should therefore be magically fixed. I'd appreciate if someone could verify.,1408570153,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title",Likely to be made WORKSFORME by gerrit 143852 but isn't actually a patch for VE. :-),1404401825,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","Change 143852 had a related patch set uploaded by Bartosz Dziewoński:
+On redirect, actually rewrite page URL to the target one with JavaScript
+
+https://gerrit.wikimedia.org/r/143852",1404383390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","Note: This doesn't happen on mobile, on refresh user stays on redirect page.",1404165903,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","(In reply to Bartosz Dziewoński from comment #2)
+> (In reply to James Forrester from comment #1)
+> > Ideally MediaWiki's redirects should 307 rather than 200 so we don't have
+> > this problem… :-(
+> 
+> They shouldn't because then you can't show the ""Redirected from"" message
+> without hacks,
+
+I'm aware of that minor impact on users, but that info is normally duplicated by editorial templates anyway on Wikimedia wikis, at least.
+
+> but they probably should update the URL with JavaScript instead.
+
+> Wanna file a bug or that? (I wouldn't be surprised if there was one already.)
+
+Yes, that looks like bug 35045.",1404164118,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","(In reply to James Forrester from comment #1)
+> Ideally MediaWiki's redirects should 307 rather than 200 so we don't have
+> this problem… :-(
+
+They shouldn't because then you can't show the ""Redirected from"" message without hacks, but they probably should update the URL with JavaScript instead. Wanna file a bug or that? (I wouldn't be surprised if there was one already.)",1404163917,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","Rewriting the URL is a bit evil, but if we don't we have the issue of users having a URL they can't share/reload without the context changing.
+
+Ideally MediaWiki's redirects should 307 rather than 200 so we don't have this problem… :-(",1404163827,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+VisualEditor:  Template dialog doesn't display very long template names gracefully,"See https://commons.wikimedia.org/wiki/File:VE_bug-Template_name_overlaps_remove_icon_in_advanced_dialog.png
+
+If the name of the template is very long, then it overlaps with the trashcan icon for removing it.
+
+This may or may not remain a consideration with the upcoming change to labels (instead of icons) and the redesign of all the boxes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1404014220,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-c27kk34icz4bpyrlvjpf,task_description,resolved
+VisualEditor:  Template dialog doesn't display very long template names gracefully,This is wrapped correctly now,1412590143,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-c27kk34icz4bpyrlvjpf,task_subcomment,NA
+VisualEditor: resizing audio file causes it to resize 0px dialogs do not report size.,"resize and size reporting issue with audio files
+
+issue is highlighed on https://en.wikipedia.org/wiki/Iceberg
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14397}",1404012180,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-zlieutzkthf2674wairs,task_description,resolved
+VisualEditor: resizing audio file causes it to resize 0px dialogs do not report size.,This no longer happens.,1701963934,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zlieutzkthf2674wairs,task_subcomment,NA
+VisualEditor: resizing audio file causes it to resize 0px dialogs do not report size.,"197.218 has provided some useful steps for reproduction here:  https://www.mediawiki.org/wiki/Topic:Ttg05p4t0hox34jh
+",1501697887,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zlieutzkthf2674wairs,task_subcomment,NA
+VisualEditor: resizing audio file causes it to resize 0px dialogs do not report size.,"I'm seeing it start off with the 0px size (in the display), and no way to change it.  It seems to save correctly, though.
+
+This problem was reported after this edit was made:  https://en.wikipedia.org/w/index.php?title=Perry_DeAngelis&diff=660113505&oldid=653104203
+
+I cannot re-size the audio box in VisualEditor.  (In the wikitext editor, I can [only] make it smaller than default.)  
+",1430438845,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zlieutzkthf2674wairs,task_subcomment,NA
+VisualEditor: Floating toolbar is mis-aligned in non-HD vector css,"Detached toolbar when floating in non-HD Vector
+
+Works fine when normally placed, but is out by ~ 30px when floating.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14365}",1403981160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g7bdag3ouhcedtw4w7px,task_description,resolved
+VisualEditor: Floating toolbar is mis-aligned in non-HD vector css,Looks like this got fixed two weeks ago.,1405555416,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g7bdag3ouhcedtw4w7px,task_subcomment,NA
+VisualEditor: Floating toolbar is mis-aligned in non-HD vector css,"Created attachment 15773
+Non-detached static toolbar
+
+**Attached**: {F14366}",1403981244,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g7bdag3ouhcedtw4w7px,task_subcomment,NA
+VisualEditor: Merge the inserting and editing media dialogs,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403824980,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_description,resolved
+VisualEditor: Merge the inserting and editing media dialogs,*** Bug 58245 has been marked as a duplicate of this bug. ***,1412590279,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_subcomment,NA
+VisualEditor: Merge the inserting and editing media dialogs,"Change 140813 merged by jenkins-bot:
+Merge Media Edit and Media Insert dialogs
+
+https://gerrit.wikimedia.org/r/140813",1404269588,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_subcomment,NA
+VisualEditor: Merge the inserting and editing media dialogs,"Change 140813 had a related patch set uploaded by Mooeypoo:
+[wip] Merge Media Edit and Media Insert dialogs
+
+https://gerrit.wikimedia.org/r/140813",1403856246,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_subcomment,NA
+VisualEditor: Merge the inserting and editing media dialogs,Once more with feeling.,1403825005,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_subcomment,NA
+"VisualEditor:  Can't tab from Caption to Alt text fields in image media dialog box, in Safari only","Steps to reproduce:
+
+1.  Open a page containing an image in Safari.
+
+2.  Open an image in the media dialog box.  The cursor begins in the Caption field (of General settings).
+
+3.  Press tab (to get to the next field).
+
+
+Results:
+
+Nothing happens.  The cursor is stuck in the Caption field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67156",1403810760,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-bd7sldgzh3ssrxvsie4v,task_description,resolved
+"VisualEditor:  Can't tab from Caption to Alt text fields in image media dialog box, in Safari only","Hmm. Will sling into the list, then, but this feels odd…",1404954592,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bd7sldgzh3ssrxvsie4v,task_subcomment,NA
+"VisualEditor:  Can't tab from Caption to Alt text fields in image media dialog box, in Safari only","This works for me at Mediawiki.org (1.24wmf12) but not at the English Wikipedia on Safari 6.1.4 with Mac OS 10.8.5.  
+
+Presumably it will work everywhere after tomorrow's update, so I'm marking it as fixed.",1404954523,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-bd7sldgzh3ssrxvsie4v,task_subcomment,NA
+"VisualEditor:  Can't tab from Caption to Alt text fields in image media dialog box, in Safari only",WFM (Safari 5.1.7 for Windows),1404946411,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-bd7sldgzh3ssrxvsie4v,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"This is related to {T69153}, but specific to Chrome/Safari:
+
+Whatever the dialog box, once you've tabbed through whatever links and buttons are inside that dialog (and on the tab list, which isn't always all of them), then pressing tab takes you outside the dialog box to these items:
+
+1) the browser's URL bar
+2) the main Wikipedia search box 
+3) the Cancel button (on VisualEditor's toolbar)
+4) the Save button (on VisualEditor's toolbar)
+5) the top of the article
+6) the slug at the top of the article, where it gets stuck forever.
+
+and never lets you get back to the dialog box.  This means that if you press tab one time more than you meant to, you cannot use or close the dialog box without taking your hands off the keyboard.
+
+**See Also**: {T69162}",1403808420,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-mawqu55vtwhutyac6fl2,task_description,resolved
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 237505 merged by jenkins-bot:
+Re-attempt I31ab2bace4: Try to stop user from tabbing outside of open dialog box
+
+[[https://gerrit.wikimedia.org/r/237505]]",1442834801,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 237480 merged by jenkins-bot:
+Rewrite isFocusableElement for performance and correctness
+
+[[https://gerrit.wikimedia.org/r/237480]]",1442252376,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 237480 had a related patch set uploaded (by Esanders):
+Rewrite isFocusableElement for performance and correctness
+
+[[https://gerrit.wikimedia.org/r/237480]]
+",1441922268,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 237505 had a related patch set uploaded (by Esanders):
+Re-attempt I31ab2bace4: Try to stop user from tabbing outside of open dialog box
+
+[[https://gerrit.wikimedia.org/r/237505]]
+",1441919838,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Turns out that we have a method to find focusable elements now (6ff7e5c7ae384038b314dc90036f0a8468e7e65a), but it's a bit broken (T107343). Let's try to fix it and use it.",1438203848,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Some more notes:
+* The previously suggested focus trap only works for tab, not for shift-tab
+* a focus trap only fixes keyboard navigation, not screenreader accessibility
+** You can use aria-hidden to hide everything outside the dialog, opacity does not hide things....
+
+Suggested reading:
+* http://www.w3.org/TR/wai-aria-practices/#modal_dialog
+* http://www.w3.org/TR/wai-aria-practices/#dialog_modal
+* http://www.w3.org/TR/wai-aria-practices/#dialog_nonmodal
+* http://www.w3.org/TR/wai-aria-practices/#dialog_tooltip
+",1424255489,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Let me add links for jQuery UI's :focusable and :tabbable 
+
+http://api.jqueryui.com/focusable-selector/
+http://api.jqueryui.com/tabbable-selector/",1424250704,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"if jQuery UI can add a selector focusable and 'tabbable' for this. Can't we mix those in ourselves ? We'd have to account for the situation where both jQueryUI and OOjs UI are loaded, but we can do that with prefixes I think...",1424250506,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"The reverted patch did, in fact, do something like that. But we still need to find the place inside the dialog where we want to move the focus, and it used `:focusable` for this.
+
+I did some googling and found http://accessibility.oit.ncsu.edu/training/aria/modal-window/version-2/, which uses `a[href], area[href], input:not([disabled]), select:not([disabled]), textarea:not([disabled]), button:not([disabled]), iframe, object, embed, *[tabindex], *[contenteditable]`. Sadly, I think they're wrong in both using `[disabled]` rather than `:disabled` and not checking `[tabindex='-1']`.
+
+Note also that `:focusable` implied `:visible`, we'd need to add this filter ourselves.",1423342981,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Can we do it using observe and fixup, e.g.  listen to focusin on the body, and if the event originates form outside the dialog, move it back inside the dialog.",1423341758,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Patch was reverted, so what's the status of this? We need to do the same again, but without `:focusable`? 
+
+I looked at the source code and `:focusable` can be reasonably approximated using `input:enabled:not([tabindex='-1']), select:enabled:not([tabindex='-1']), textarea:enabled:not([tabindex='-1']), button:enabled:not([tabindex='-1']), a[href]:not([tabindex='-1']), [tabindex]:not([tabindex='-1'])`, or even just `*:enabled:not([tabindex='-1']), a[href]:not([tabindex='-1']), [tabindex]:not([tabindex='-1'])`. If that's too nasty, then we might also do `[tabindex]:not([tabindex='-1'])` and probably no one will notice the difference (OOUI focusable elements generally have tabindex=0 set, even if that's not strictly necessary).",1423341062,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"The applied patch throws an exception, see gerrit.",1412938656,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,Merged. Hopefully this doesn't break anything else.,1412114329,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 159902 merged by jenkins-bot:
+Try to stop user from tabbing outside of open dialog box
+
+https://gerrit.wikimedia.org/r/159902",1412114245,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 159902 had a related patch set uploaded by Alex Monk:
+Try to stop user from tabbing outside of open dialog box
+
+https://gerrit.wikimedia.org/r/159902",1410473896,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"So after some confusion about this I looked into it again, and I believe that there's two issues here:
+* We perhaps shouldn't let tab take the focus out of the dialog box at all
+* Tab definitely should not be getting lost and become unable to return to the dialog
+
+Different browsers appear to do different things:
+* Chrome on Ubuntu lets it out of the dialog, but it properly goes back and doesn't get stuck.
+* Chrome and Safari on Windows just let the tabbing leave the dialog, and then it gets stuck and doesn't return to the beginning of the page
+* Firefox (on Ubuntu or Windows) does not let it out of the dialog",1405558247,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,In that case this feels like an upstream issue,1404994158,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Firefox lets me leave the dialog box, but it eventually tabs back into it.  Safari gets stuck.  I haven't checked Chrome; Safari and Chrome often have the same problems, so it might be anything WebKit/not Mozilla.",1404954736,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"I don't think we do this deliberately. This happens in Chrome for me... Are you sure this is Safari-specific, Sherry?",1404947139,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Krenair, is this something that we do as part of the aria-role stuff (and is it something we should do)?",1404848207,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","When adding a link inside a reference in VisualEditor, if one clicks 'apply' without first clicking outside the link inspector, the link is not added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60837",1403637660,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-juabtt3jtkdtozbvwjyi,task_description,resolved
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)",Спасибо! Happy New Year!,1420072225,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","Being bold and marking as resolved.
+
+С новым годом :)",1420070837,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)",Seems to be fixed to me too - checked in betalabs/test2/production.,1420069952,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","I believe this was fixed when Roan worked on the focus issue with inspectors. I can't reproduce this either, it works as it should now with links and language inspector both.",1420050291,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","Can anybody reproduce this? I can't. Either I misunderstand the description, or it was fixed.",1419721481,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","Maybe we just need to give the edit box focus when applying changes, like in bug 60837's fix?",1403638221,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+VisualEditor: Toolbar is sometimes misaligned and ugly in Safari; corrects itself after interaction,"Misaligned toolbar
+
+The bottom of the bar is too high, the Cancel and Save buttons are at different heights.  
+
+However, I can't reproduce it consistently, and changing the font size caused everything to realign correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14345}",1403548380,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jjbnp6qzxgfufzean2ux,task_description,resolved
+VisualEditor: Toolbar is sometimes misaligned and ugly in Safari; corrects itself after interaction,This seems to have been fixed a long time ago.,1508930094,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-jjbnp6qzxgfufzean2ux,task_subcomment,NA
+VisualEditor: Toolbar is sometimes misaligned and ugly in Safari; corrects itself after interaction,*** Bug 67071 has been marked as a duplicate of this bug. ***,1403734997,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jjbnp6qzxgfufzean2ux,task_subcomment,NA
+VisualEditor: Toolbar is sometimes misaligned and ugly in Safari; corrects itself after interaction,"
+
+*** This bug has been marked as a duplicate of bug 67071 ***",1403700121,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jjbnp6qzxgfufzean2ux,task_subcomment,NA
+"VisualEditor: Turn structure dropdown into a ""split button"" with ""make bulleted list"" the primary action","A split button consists of a ""command button"" and a ""dropdown button"". These are two separate clickable entities. The command button behaves like a regular toolbar button, but it displays the most recent command the user invoked from the dropdown menu.
+
+It was suggested by User:Theflyer to convert VE's list toolbar button into a split button:
+
+
+> When selecting an item from the menu, like lists, I think the button should be sticky and perform the action that is currently shown rather than requiring two clicks to take an action. The example that brought this to my attention is when creating bullets. The default icon shows a traditional bullet so when I click on that, I expect it to just start a bullet. However, the action I get is to open the menu where I then have to select which bullet list option I would prefer. I think there should be a way to act on the existing icon (and it should change to whatever I had last selected) and also a way to pull down the list if I want to change to a different type of action. This is the way Microsoft Word works. There are two clickable hotspots. Thanks. Don Theflyer (talk) 15:55, 21 June 2014 (UTC)
+
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403417400,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ad7ys6ayrhumzmd7s5np,task_description,open
+"VisualEditor: Turn structure dropdown into a ""split button"" with ""make bulleted list"" the primary action",">>! In T68940#720833, @TTO wrote:
+> [1] http://tinypic.com/r/52jl7p/8 Sorry, it's a disgusting video hosting site, I hope you can tolerate the advertising!
+
+For future convenience:
+{F27317467}",1543305064,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ad7ys6ayrhumzmd7s5np,task_subcomment,NA
+"VisualEditor: Turn structure dropdown into a ""split button"" with ""make bulleted list"" the primary action","I think you're slightly misunderstanding what is meant by ""split button"". There is no single ""primary action""; see this video [1] for an example of how the command on the ""command button"" part of the split button changes as different options are picked from the dropdown.
+
+[1] http://tinypic.com/r/52jl7p/8 Sorry, it's a disgusting video hosting site, I hope you can tolerate the advertising!",1403694056,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ad7ys6ayrhumzmd7s5np,task_subcomment,NA
+"VisualEditor: Turn structure dropdown into a ""split button"" with ""make bulleted list"" the primary action","Hmm. Maybe. Is bulleted list the principal structure-action people will take, over ""make blockquote"" or ""indent"" or ""insert table"" or ""insert row"" or…?",1403658694,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ad7ys6ayrhumzmd7s5np,task_subcomment,NA
+VisualEditor: Use comma-separator interface message,"There are a few places where we use the string ', ' but in all of those cases we should really be using the comma-separator message. This requires backfilling comma-separator for standalone OOUI, since we also use commas in VE core and OOUI.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403310780,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6svejr4dlr5a76d65y4o,task_description,resolved
+VisualEditor: Use comma-separator interface message,"Change 174302 merged by jenkins-bot:
+ve.ce.MWTransclusionNode: Replace last use of ', ' in VE-MW with <comma-seperator>
+
+https://gerrit.wikimedia.org/r/174302",1416396118,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6svejr4dlr5a76d65y4o,task_subcomment,NA
+VisualEditor: Use comma-separator interface message,"Change 174302 had a related patch set uploaded by Jforrester:
+ve.ce.MWTransclusionNode: Replace last use of ', ' in VE-MW with <comma-seperator>
+
+https://gerrit.wikimedia.org/r/174302",1416349471,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6svejr4dlr5a76d65y4o,task_subcomment,NA
+VisualEditor: Use comma-separator interface message,...but it gets converted. Hm.,1403628331,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6svejr4dlr5a76d65y4o,task_subcomment,NA
+VisualEditor: Use comma-separator interface message,The MW message includes HTML. Ew.,1403628205,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6svejr4dlr5a76d65y4o,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Right now we have things like mw.Title.newFromText( template ); , while really that should use something like mw.Title.newFromText( template, 10 ); or whatever. This is probably fine in practice, but theoretically matters is NS_MAIN and NS_TEMPLATE have different capitalization settings.
+
+We also currently render the titles of {{foo}} (which points to Template:Foo, renders as Foo) and {{:foo}} (which points to Foo, also renders as Foo) the same, we should fix that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403310360,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zq64ne5etzq4kohyhblm,task_description,resolved
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"(In reply to Roan Kattouw from comment #3)
+> (In reply to Roan Kattouw from comment #0)
+> > Right now we have things like mw.Title.newFromText( template ); , while
+> > really that should use something like mw.Title.newFromText( template, 10 );
+> > or whatever. This is probably fine in practice, but theoretically matters is
+> > NS_MAIN and NS_TEMPLATE have different capitalization settings.
+> > 
+> This is not fixed yet, reopening.
+> 
+Somewhat to my surprise this is in fact fully fixed in https://gerrit.wikimedia.org/r/143685",1404350702,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Change 143685 merged by jenkins-bot:
+Try some more to handle template namespace properly
+
+https://gerrit.wikimedia.org/r/143685",1404350631,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Change 143685 had a related patch set uploaded by Catrope:
+Try some more to handle template namespace properly
+
+https://gerrit.wikimedia.org/r/143685",1404350404,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"(In reply to Roan Kattouw from comment #0)
+> Right now we have things like mw.Title.newFromText( template ); , while
+> really that should use something like mw.Title.newFromText( template, 10 );
+> or whatever. This is probably fine in practice, but theoretically matters is
+> NS_MAIN and NS_TEMPLATE have different capitalization settings.
+> 
+This is not fixed yet, reopening.
+
+> We also currently render the titles of {{foo}} (which points to
+> Template:Foo, renders as Foo) and {{:foo}} (which points to Foo, also
+> renders as Foo) the same, we should fix that.
+This was indeed fixed by https://gerrit.wikimedia.org/r/141082",1404350281,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Change 141082 merged by jenkins-bot:
+Normalize titles in template descriptions in context menu
+
+https://gerrit.wikimedia.org/r/141082",1403730637,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Change 141082 had a related patch set uploaded by Jforrester:
+Normalize titles in template descriptions in context menu
+
+https://gerrit.wikimedia.org/r/141082",1403314162,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a svg image with large size 
+(I found this issue with this image: https://test2.wikipedia.org/wiki/File:MO-123.svg, which has full size of 2,543 × 2,160 pixels.
+I tried with svg images of upto 2000 x 2000 pixels, but could not reproduce for them.)
+
+3.Go to Media Settings tab of this image and go to Advanced Settings
+4.Click on Make full size (it wont try to make it full size which is another bug)
+5.Now again click on Make full size
+
+Observed Result:
+It changes the size values to the full size of the images but it also says ""Size values are invalid""
+
+Page:https://test2.wikipedia.org/wiki/19thjanFF?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403223600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-axpv35jfsr4hb5ftvtac,task_description,resolved
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""",Verified the fix in production,1405035015,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-axpv35jfsr4hb5ftvtac,task_subcomment,NA
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""",Verified the fix in Betalabs,1403908612,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-axpv35jfsr4hb5ftvtac,task_subcomment,NA
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""","Change 142380 merged by jenkins-bot:
+Unimplement wgSVGMaxSize
+
+https://gerrit.wikimedia.org/r/142380",1403822223,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-axpv35jfsr4hb5ftvtac,task_subcomment,NA
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""","Change 142380 had a related patch set uploaded by Mooeypoo:
+Unimplement wgSVGMaxSize
+
+https://gerrit.wikimedia.org/r/142380",1403812565,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-axpv35jfsr4hb5ftvtac,task_subcomment,NA
+mediawiki.feedback: The 'submit feedback' form does not add the feedback page to the user's watchlist,"Users who submit feedback through the in-VisualEditor form may not see any responses to their feedback because the page is not added to their watchlists, and there's no option to add it.
+
+This feature comes from the `mediawiki.feedback` module in MediaWiki core.",1403195700,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rw3z2ncxhjiapf53g2dj,task_description,resolved
+mediawiki.feedback: The 'submit feedback' form does not add the feedback page to the user's watchlist,"I don't think most contributors would know to go to their watchlist to see if their feedback got a response. It's perhaps better than nothing, though, so it's certainly an understandable fallback strategy for the more experienced user. And if the feedback page is wikitext, then it would presumably have to watch the whole page and thus still not be a very good user experience.
+
+This was filed in 2014 and in the meanwhile we do have Echo notifications enabled by default. This means if the reply to the person's feedback @-mentions their name, they will be notified automatically today already.
+
+Another thing we gained is Flow being deployed and used for most of these feedback pages afaik. And from a quick look in the Flow/MessagePoster plugin (used by mediawiki.feedback), new topics that are created are by default immediately watched by the current user.
+
+Tentatively marking this as resolved.
+
+Perhaps that's an adequate solution for now?",1586711588,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rw3z2ncxhjiapf53g2dj,task_subcomment,NA
+mediawiki.feedback: The 'submit feedback' form does not add the feedback page to the user's watchlist,"This is pretty irritating. Not sure whether it should just respect the users' default wishes, actively add the page anyway, or give an option…",1403195859,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rw3z2ncxhjiapf53g2dj,task_subcomment,NA
+Strip initial and trailing <br>s out of section headings,"https://en.wikipedia.org/w/index.php?diff=612724427&oldid=612719708 added an invalid section heading:
+
+===== <br>
+Buses =====
+
+
+VisualEditor should always strip <br> out of section headings.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403195100,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-tx3tnhbz5553iuofuywl,task_description,resolved
+Strip initial and trailing <br>s out of section headings,Should now be fixed thanks to the Parsoid munging magic.,1437698410,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tx3tnhbz5553iuofuywl,task_subcomment,NA
+Strip initial and trailing <br>s out of section headings,I can't reproduce…,1434493143,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tx3tnhbz5553iuofuywl,task_subcomment,NA
+Strip initial and trailing <br>s out of section headings,This is still happening: https://en.wikipedia.org/wiki/Special:Diff/655367592,1428429209,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-tx3tnhbz5553iuofuywl,task_subcomment,NA
+VisualEditor:  Clear the 'search memory' after making a link,"Steps to reproduce:
+
+1.  Open a page in VisualEditor and make a link:  [[Foo]].  Easy, right?  Select text, press Command–K, and hit return twice.  You know the page exists under that name and that it doesn't need to be piped, so you don't even need to wait for the link inspector to get the information back from search.
+
+2.  Make another link the same way, but to a different page:  [[Bar]].
+
+3.  Why does VisualEditor offer to point that second link to [[Foo]]?
+
+
+Steps to avoid this problem:
+
+1.  Open a page in VisualEditor and make a link:  [[Foo]].
+
+2.  Start to make another link to a different page ([[Bar]]), but after you've opened the link inspector, just stop and wait and wait and wait.
+
+3.  Ah, it's finally figured out that [[Bar]] is not [[Foo]] and stopped trying to tell me that I want to link this to [[Foo]].  *Now* you can hit return twice and go on with your editing.
+
+
+Can we make VisualEditor ""forget"" the search results in between attempts to link pages?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403144040,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-2rmkxa2is7nps4mba7xt,task_description,resolved
+VisualEditor:  Clear the 'search memory' after making a link,This is now fixed with the changed way that the search interface triggers on link creation (and about a dozen other minor changes). So… yay?,1403144528,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2rmkxa2is7nps4mba7xt,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"In advance of rewriting the skins system, MediaWiki 1.24 introduces a mediawiki.skinning.content.parsoid module which is a dependency of VisualEditor master.
+
+Making it so that downstream users can use newer versions of VisualEditor but not bleeding-edge MediaWiki would be a nice improvement for them, especially for LTS versions.
+
+However, we may want to have it settle down a bit more until now?
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: enhancement",1403122680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rvudp57rsxh5tyqambv6,task_description,declined
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"This is going nowhere, and REL1_23 is EOL within the next two months. There's little point putting any effort into this",1489977944,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"This has been in the ""MediaWiki-Tarball-Backports"" project for over a year now. Suggest we either close as WONTFIX, or someone proposes a way forward.",1450709644,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"Restoring the ""Backport_to_stable?"" flag in Bugzilla by adding this to the MediaWiki-Tarball-Backports project in Phab.",1417060060,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"(In reply to James Forrester from comment #4)
+> There are probably more to come, but this is good enough. Given that 1.23 is
+> LTS, I imagine Mark wants to support VE on it? Confused why he just rejected
+> the backport he requested…
+
+I was going through the backport request queue and didn't see anything to backport.
+
+Replacing the flag and, hopefully, I'll have time later to go through the list of patches.",1412904045,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"(In reply to Andre Klapper from comment #3)
+> Which specific, identified commits are proposed as backport candidates here?
+
+`git log --oneline resources/src/mediawiki.skinning/content.parsoid.less`:
+
+4ae23e7 Fix Parsoid's span.reference styling to match PHP's output
+5ada680 Remove Parsoid-specific padding and background
+244e1fc Apply bidi styles to references in Parsoid styles
+76a5ea6 Minor: Remove unnecessary @noflip annotation
+9573eb2 Add unfloated thumb styling in Parsoid CSS
+56300b6 Align image frame padding with core
+4f69ebe Tweaks to Parsoid CSS styles for citations.
+6f45ac4 Fix rendering of centered caption-less images
+26a39ec Hide the caption of frameless or inline images in Parsoid HTML
+4fe80f6 Minor: more specific parsoid image styling with child selectors
+a3525f0 Bug 51245: Add auto-numbered link CSS to Parsoid styles
+a6c074a Minor clarification & tweak for Parsoid render testing
+7086dad Bug 66287: Proper caption styling
+99f093a Make sure images that don't have an explicit alignment get aligned right
+e826298 Add border and background styling to the Parsoid styles for images
+295b2dc Followup dd1c7f7fd7: fix LESSification errors in Parsoid styles
+dd1c7f7 Create a version of mediawiki.skinning.content for Parsoid HTML
+
+There are probably more to come, but this is good enough. Given that 1.23 is LTS, I imagine Mark wants to support VE on it? Confused why he just rejected the backport he requested…",1412880759,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"Which specific, identified commits are proposed as backport candidates here?",1412769048,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"(In reply to Kunal Mehta (Legoktm) from comment #1)
+> Is this still the only thing blocking VE master on 1.23? Or have there been
+> new breaking things since then?
+
+Lots of new breaking things since then, like your patches to make VE use Config, but VE-not-quite-master from a month ago or so probably would be able to go if this stuff was backported to MW REL1_23 (and more importantly, users wouldn't need to install the very confusing Parsoid PHP extension in addition to the Parsoid nodejs service).",1408566225,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,Is this still the only thing blocking VE master on 1.23? Or have there been new breaking things since then?,1408563679,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+VisualEditor Mobile: Cursor moving handle (?) doesn't appear in Android,"On mobile devices there's the ""stick"" blinking cursor, and usually also another handle for moving the cursor around more conveniently. I'm not sure what is it called.
+
+I cannot see it in the mobile VE.
+
+I'm using ASUS Transformer with Android 4.2.1.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403098320,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ffq5hsenml5yhfful4jm,task_description,open
+VisualEditor Mobile: Cursor moving handle (?) doesn't appear in Android,"This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592583998,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ffq5hsenml5yhfful4jm,task_subcomment,NA
+VisualEditor Mobile: Cursor moving handle (?) doesn't appear in Android,"The previous comments don't explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status.
+
+//(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}. If this task is stalled on an upstream project, then the #upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task needs retesting, then the #testme tag should be added. If this task is either out of scope and nobody should ever work on this, or nobody else managed to reproduce the problem described in this task, then this task should have the ""Declined"" status.)//",1590761756,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ffq5hsenml5yhfful4jm,task_subcomment,NA
+"VisualEditor Mobile: For the first time in each edit session in Nexus 7 (Android 4.4.2), Link Inspector gets auto-zoomed in, which looks like partial rendering of the UI","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Select a text
+3.Click on the link inspector icon from the toolbar
+
+Observed Result:
+The link inspector appears a bit zoomed, which at first glance made me feel like a failure in rendering the inspector.
+
+See the screeshot attached
+
+Device: Nexus 7(Android 4.4.2)
+Environment:Production (en.wiki) and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13925}",1403051220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rwcczd2xhqirmziyxmyi,task_description,resolved
+"VisualEditor Mobile: For the first time in each edit session in Nexus 7 (Android 4.4.2), Link Inspector gets auto-zoomed in, which looks like partial rendering of the UI","Not happening anymore, tested in test2 and en.wiki.",1430340251,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rwcczd2xhqirmziyxmyi,task_subcomment,NA
+"VisualEditor Mobile: For the first time in each edit session in Nexus 7 (Android 4.4.2), Link Inspector gets auto-zoomed in, which looks like partial rendering of the UI",Needs re-testing.,1430336295,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rwcczd2xhqirmziyxmyi,task_subcomment,NA
+"VisualEditor Mobile: For the first time in each edit session in Nexus 7 (Android 4.4.2), Link Inspector gets auto-zoomed in, which looks like partial rendering of the UI",Maybe don't let users zoom at all?,1404329672,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rwcczd2xhqirmziyxmyi,task_subcomment,NA
+VisualEditor Mobile: Tapping at the end of each link duplicates the preceding link text in Nexus 7 (Android 4.4.2),"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Tap at the end of a link
+
+Observed Result:
+The link gets copied at the position your cursor was on and it will keep continue doing that everytime you place your cursor at the end of extended link.
+
+See the screenshot attached
+
+Device: Nexus 7(Android 4.4.2)
+Environment:Production (en.wiki) and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13918}",1403046960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2jqvp6o5rukgut7ypeps,task_description,declined
+VisualEditor Mobile: Tapping at the end of each link duplicates the preceding link text in Nexus 7 (Android 4.4.2),">>! In T68754#6180057, @Aklapper wrote:
+> 6 years later, is this still an issue? If nobody can reproduce (or nobody has time to reproduce), then this ticket should be closed as 'declined'. Thanks!
+
+Closing this Phabricator task as no further information has been provided.
+If this still happens, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks a lot!",1604273725,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2jqvp6o5rukgut7ypeps,task_subcomment,NA
+VisualEditor Mobile: Tapping at the end of each link duplicates the preceding link text in Nexus 7 (Android 4.4.2),"6 years later, is this still an issue? If nobody can reproduce (or nobody has time to reproduce), then this ticket should be closed as 'declined'. Thanks!",1590943697,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2jqvp6o5rukgut7ypeps,task_subcomment,NA
+VisualEditor Mobile: Tapping at the end of each link duplicates the preceding link text in Nexus 7 (Android 4.4.2),Needs re-testing.,1430336378,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2jqvp6o5rukgut7ypeps,task_subcomment,NA
+Dump the change_tag table,"https://www.mediawiki.org/wiki/Manual:Change_tag_table , no private data involved and very useful for research (public editing patterns of all sorts and now visualeditor, mobile etc.).
+
+On wikitech-l nobody could find a reason not to do it.
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070255.html
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402992420,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-5xjx5bhytilus36xtsqu,task_description,resolved
+Dump the change_tag table,"done, tested, works. closing. ",1443610896,PHID-USER-jtxavgb3caz53o45csni,PHID-TASK-5xjx5bhytilus36xtsqu,task_subcomment,NA
+Dump the change_tag table,"Change 242499 merged by ArielGlenn:
+dump change tag table, T68700
+
+[[https://gerrit.wikimedia.org/r/242499]]",1443610070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5xjx5bhytilus36xtsqu,task_subcomment,NA
+Dump the change_tag table,"Since change tags can now be deleted, I'm moving this along. ",1443606034,PHID-USER-jtxavgb3caz53o45csni,PHID-TASK-5xjx5bhytilus36xtsqu,task_subcomment,NA
+Dump the change_tag table,"Change 242499 had a related patch set uploaded (by ArielGlenn):
+dump change tags table, T68700
+
+[[https://gerrit.wikimedia.org/r/242499]]
+",1443606009,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5xjx5bhytilus36xtsqu,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Tap somewhere in the middle of the article
+3.Insert some text
+4.Close the keypad
+5.Now again tap at the end of the text that you typed in
+
+Observed Result:
+The cursor moves to the beginning of the article, not where the user wanted to start his edit.
+
+Device: iPad Mini
+iOS:7.1.1
+Environment:Production and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402962060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oamnqxetj6ams3volnvi,task_description,resolved
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into",Verified the fix in production,1409865559,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into",Verified the fix in test2,1409260518,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","The original issue that cursor jumps to the beginning of the article is resolved, but still remains issue where the page is not actually getting scrolled down to the point where the cursor is currently positioned at.I have filed a different bug on that (https://bugzilla.wikimedia.org/show_bug.cgi?id=70111) as discussed with Roan.",1409181698,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","Change 155839 merged by jenkins-bot:
+Check for selection in ve.ce.Surface#onDocumentFocus
+
+https://gerrit.wikimedia.org/r/155839",1409098207,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","Change 155839 had a related patch set uploaded by JGonera:
+Check for selection in ve.ce.Surface#onDocumentFocus
+
+https://gerrit.wikimedia.org/r/155839",1408746801,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","**jgonera** wrote:
+
+this.dragging is false because onFocusChange is called after onDocumentMouseUp.
+
+The order of events on iOS Safari seems to be fine though:
+
+* mousedown
+* focus
+* mouseup",1408742416,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","**jgonera** wrote:
+
+It's because we call
+
+    this.getModel().selectFirstContentOffset();
+
+in ve.ce.Surface#onDocumentFocus as a workaround for Firefox. I guess we'd want this.dragging to be true when someone taps on a touch device, but it's false instead.",1408740739,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","**jgonera** wrote:
+
+Trying to figure this one out now.
+
+If you set hasFocus to false in ve.ce.Surface#onFocusChange, the problem goes away.
+
+If you already have the fix for bug 68832 [1][2], then this is easier to reproduce because it happens on every tap on the CE.
+
+[1] https://gerrit.wikimedia.org/r/#/c/155678/
+[2] https://gerrit.wikimedia.org/r/#/c/155671/",1408740409,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","**jgonera** wrote:
+
+Might be related to bug 68832.",1407446825,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into",Might be related to the context being wrong in iOS?,1404329901,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","As a logged in user at http://en.m.wikipedia.beta.wmflabs.org/\
+
+With beta setting enabled
+
+Click edit
+
+VE never appears, user sees just a spinner. 
+
+js error is: Uncaught Error: Unknown dependency: jquery.uls.data
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402677300,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_description,resolved
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever",The error goes away after enabling the 'uls' role in vagrant.,1423616745,PHID-USER-grftjc3ekkyjf6bwlsqi,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever",This is happening to me. I have latest code from master.,1421196859,PHID-USER-grftjc3ekkyjf6bwlsqi,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever",Checked on betalabs and test2 mobile.,1417636413,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","Change 139484 merged by jenkins-bot:
+Add mobile target for modules that VE depends on
+
+https://gerrit.wikimedia.org/r/139484",1402692497,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","Change 139435 merged by jenkins-bot:
+Add targets missing from jquery.i18n libraries
+
+https://gerrit.wikimedia.org/r/139435",1402692446,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","Change 139484 had a related patch set uploaded by JGonera:
+Add mobile target for modules that VE depends on
+
+https://gerrit.wikimedia.org/r/139484",1402692073,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","Change 139435 had a related patch set uploaded by Esanders:
+Add targets missing from jquery.i18n libraries
+
+https://gerrit.wikimedia.org/r/139435",1402682004,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever",Error introduced by I54c0a8e5816a3c81851f95f1d3062a6091a9f4a3 in VisualEditor,1402681583,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/MuQh23gb",1402677614,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+VisualEditor: Typing multiple deadkeys at the end of text expands selection to new line,"**Author:** `oliver.buchtala`
+
+**Description:**
+Put the cursor at the end of a text node and e.g. type ``.
+After short delay the selection expands to the begin of the next node.
+
+This happens for me under OSX Chrome 35 and Safari 7.0 for  VE@356f325ab21731e0aa5c83f90fb4fa037cc60cff.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1402673820,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zvu24wr6gapdwg6aoskt,task_description,open
+VisualEditor: Typing multiple deadkeys at the end of text expands selection to new line,"Confirmed; the re-select happens on master.
+
+When the cursor is at the start or in the middle of a paragraph and the next cursor position is text, nothing odd happens.
+
+When the cursor is at the end of the paragraph (and the next paragraph begins with text or a node), it selects from the end of the paragraph to the start of the next. However, the selection is still n,n – it's not showing as a selection n to n+2 as it is showing.
+
+When the cursor is at the start or in the middle of a paragraph and the next cursor position is a node (e.g. a reference or a link node), the cursor suddenly disappears (but the selection is still n,n).",1404248576,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zvu24wr6gapdwg6aoskt,task_subcomment,NA
+VisualEditor: Typing multiple deadkeys at the end of text expands selection to new line,"**oliver.buchtala** wrote:
+
+Animation showing the issue in Safari
+
+**Attached**: {F14132}",1402673914,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zvu24wr6gapdwg6aoskt,task_subcomment,NA
+"VisualEditor: Gallery and Math inspector closes with an animation from right to left after clicking on ""<"" to close them","Steps to reproduce:
+
+1.Open a page with VE
+2.Open the gallery inspector for an already added gallery or open the math inspector
+3.Close the gallery inspector or math inspector after inserting math function
+
+Observed Result:
+The inspector closes with an animation coming from right to left
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60501",1402602720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gbmahf2nvdgcfrdtetva,task_description,resolved
+"VisualEditor: Gallery and Math inspector closes with an animation from right to left after clicking on ""<"" to close them",Fixed in gerrit 139550.,1405375906,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gbmahf2nvdgcfrdtetva,task_subcomment,NA
+"VisualEditor: Gallery and Math inspector closes with an animation from right to left after clicking on ""<"" to close them",This is also on test with wmf9,1402618667,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gbmahf2nvdgcfrdtetva,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"**Author:** `oliver.buchtala`
+
+**Description:**
+Currently, if the menu for a FocusNode gets embedded, this also happens for the Inspector. It would be better to let the Inspector itself decide.
+
+Details:
+
+This gets executed when the menu for a focus node is shown. 'this.embedded' is set according to the size of the focus node:
+
+https://github.com/wikimedia/VisualEditor/blob/356f325ab21731e0aa5c83f90fb4fa037cc60cff/modules/ve/ui/ve.ui.DesktopContext.js#L428-L435
+
+OTOH, when the inspector gets opened, 'this.embedded' is not recomputed:
+
+https://github.com/wikimedia/VisualEditor/blob/356f325ab21731e0aa5c83f90fb4fa037cc60cff/modules/ve/ui/ve.ui.DesktopContext.js#L420-L425
+
+This has the consequence that the inspector is rendered over the focussed node.
+IMO, at least the same embedded check should be done in the 'inspector' case.
+Also the tail should be enabled accordingly.
+
+To leave the inspector implementation even more control I would suggest to add something like this to the Inspector interface:
+
+/**
+ * @returns {boolean}
+ */
+Inspector.prototype.isEmbedded = function() {};
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402596900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_description,resolved
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Change 155704 merged by jenkins-bot:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/155704",1408727876,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Change 155704 had a related patch set uploaded by Esanders:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/155704",1408711057,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,Regressed.,1408710970,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,*** Bug 67306 has been marked as a duplicate of this bug. ***,1408710950,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Change 143393 merged by jenkins-bot:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/143393",1404247817,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Change 143393 had a related patch set uploaded by Jforrester:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/143393",1404246534,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"[Bah]
+
+(In reply to James Forrester from comment #4)
+> Sorry for the slow triage here; between this and bug 67306 we think it'd be
+> best to actively prevent the context menu from showing over an item that is
+> inspectable (rather than just have it be a configuration), so I'm going to
+> mark this one as the primary and the other as
+
+… as possibly a WONTFIX, rather than leave it be.",1404246505,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Sorry for the slow triage here; between this and bug 67306 we think it'd be best to actively prevent the context menu from showing over an item that is inspectable (rather than just have it be a configuration), so I'm going to mark this one as the primary and the other as",1404246476,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"**oliver.buchtala** wrote:
+
+
+(In reply to Oliver Buchtala from comment #2)
+
+> https://github.com/oliver----/VisualEditor/commit/
+> 26baf0bf57fb3fb23ce7ae5971b25f29ac8182db
+Sorry, this link was wrong.
+
+https://github.com/oliver----/VisualEditor/commit/8c0e5acb6df5bc104165e9fbbf3f9b9959f89135",1402599525,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"**oliver.buchtala** wrote:
+
+(In reply to Oliver Buchtala from comment #1)
+
+Maybe it could look like this:
+
+https://github.com/oliver----/VisualEditor/commit/26baf0bf57fb3fb23ce7ae5971b25f29ac8182db",1402599219,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"**oliver.buchtala** wrote:
+
+... or better:
+
+/**
+ * @returns {boolean}
+ */
+Inspector.prototype.isEmbeddable = function() {
+  return true;
+};
+
+A custom inspector can then override this to avoid embedding and existing implementations would not be influenced.",1402597991,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Creating a new page shows footer above the article,"Screencast of the behaviour.
+
+When I create a new article on Swedish Wikipedia with VE, the page footer is displayed above the cursor but below the title (se attached ogv).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13951}",1402561200,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-rchunvbnr26iqkmvxxy5,task_description,resolved
+VisualEditor: Creating a new page shows footer above the article,"This isn't happening any more, so I guess it was fixed at some point during the last three years.",1516116364,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-rchunvbnr26iqkmvxxy5,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Insert another image inside the caption of it.
+4.Select the image and observe the position of the context menu that appears on top of the image
+
+Observed Result:
+The context menu's position is shifted few pixels to the right.
+See the screenshot to compare the position of it .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13897}",1402515000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-flp4acupxj7fjvq4mgfw,task_description,resolved
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,Verified the fix in production,1405027609,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,Verified the fix in Betalabs and test2,1404771014,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,"Change 142797 merged by jenkins-bot:
+Add a ve direction class to all surfaces
+
+https://gerrit.wikimedia.org/r/142797",1403990446,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,"Change 142797 had a related patch set uploaded by Esanders:
+Add a ve direction class to all surfaces
+
+https://gerrit.wikimedia.org/r/142797",1403960368,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,But not for me (though the highlight is correctly aligned now).,1403713121,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,"Created attachment 15743
+Demonstration in Beta Labs
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox&oldid=108546&veaction=edit
+
+**Attached**: {F13898}",1403713110,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,WFM in beta labs,1403709860,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","There is a difference in behavior between explicitly stating ""none"" in the image wikitext and setting no alignment (which is usually default) This difference is especially complicated when we're dealing with switching between block to inline, as inline images basic/frameless have no initial alignment (attrs.align = undefined) but if an alignment is chosen in basic/frameless they turn into blocks.
+
+There is no real way to choose ""none"" alignment for inline blocks with our current GUI.
+
+You can see the outcome and differences between default/no alignment to 'none' and other alignments in each of the different image types in this table:
+https://www.mediawiki.org/wiki/User:Mooeypoo/VE_ImageAlignment
+
+
+I've tried to explore what other programs do in this case, but there doesn't seem to be a good analogy for the difference between having 'float' value and not having a float value while mixing block with inline. 
+
+In Microsoft Word 2013, images are inserted as block image with default alignment that is the direction of the text (left for ltr, right for rtl) *BUT* without text wrapping - so no float. You can change the image to inline (""In Line with Text"") or to be wrapped (""With Text Wrapping"") but the wrapping options are limited to how close the text is around the image; the user is then allowed to manually drag the image wherever they want ti to be (no actual 'left' / 'center' / 'right')
+
+We should find a working solution to let users decide between having 'none' alignment explicitly while still having the default value available for both inline and block images.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402440600,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-iqulbj2ddfudaregj3jn,task_description,open
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","The comparison to wikitext functionality should be something like:
+* In line: frameless/basic without alignment
+* Wrap text: thumb/frame/frameless/basic with explicit right/left alignment
+* Break line: thumb/frame/frameless/basic with either ""center"" or ""none"" alignments. No float, no text wrap.
+
+The only problem in that case would be to adjust the fine print of the behavior, but in general terms it would be more or less consistent to the user.",1402468268,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","(In reply to Moriel Schottlender from comment #6)
+> Interestingly enough, in Google Docs you seem to have three main alignment
+> options:
+> 
+> * In line - an inline image
+> * Wrap text - Block image with floating, you can then drag/drop it either
+> left, center or right in the text and choose how small the margin to the
+> text is.
+> * Break text - this is just like our ""none"" option, it's an image in its own
+> line that is automatically aligned to the text (so, left in LTR)
+> 
+> The functionality (drag/drog) and some options aren't all relevant, but
+> maybe we could get some ideas from the naming of the features.
+
+Dragging to the left/right/centre actually could be really nice, but we'd probably want both that and a way to set it in the dialog I think.
+
+""Inline"" vs. ""Break text"" vs. ""Wrap text"" seems reasonable language…",1402446964,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Interestingly enough, in Google Docs you seem to have three main alignment options:
+
+* In line - an inline image
+* Wrap text - Block image with floating, you can then drag/drop it either left, center or right in the text and choose how small the margin to the text is.
+* Break text - this is just like our ""none"" option, it's an image in its own line that is automatically aligned to the text (so, left in LTR)
+
+The functionality (drag/drog) and some options aren't all relevant, but maybe we could get some ideas from the naming of the features.",1402442352,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15627
+Image alignment in Google Docs
+
+**Attached**: {F13814}",1402442206,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15626
+Word 2013 image wrap text menu
+
+**Attached**: {F13813}",1402441159,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15625
+Word 2013 image position menu
+
+**Attached**: {F13811}",1402441084,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15624
+Word 2013 image popup menu
+
+**Attached**: {F13810}",1402441065,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15623
+Word 2013 image alignment menu
+
+**Attached**: {F13809}",1402441044,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Image
+2.Open the Media Settings dialog
+3.Now quickly double click on Apply changes Button
+
+Observed Result:
+An error appears in the console:
+
+Uncaught TypeError: Cannot read property 'getSurface' of null
+Media Settings dialog for that image and all other images on that page becomes unresponsive.
+
+This is happening in Betalabs and test , not on production(en.wiki)
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13637}",1402341840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_description,resolved
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","**Coiby.Xu** wrote:
+
+(In reply to Roan Kattouw from comment #10)
+> Right, ActionDialog.js was introduced after the 1.23 release. I thought this
+> bug was introduced after the 1.23 release though, so I'm surprised to hear
+> it's breaking for you.
+
+So will the development team resolve this bug for 1.23?",1407980375,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","Right, ActionDialog.js was introduced after the 1.23 release. I thought this bug was introduced after the 1.23 release though, so I'm surprised to hear it's breaking for you.",1407896547,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","**Coiby.Xu** wrote:
+
+Sorry, it's typo. I mean .js.
+
+There are two files related to Media Seetings dialogue, ve.ui.MWMediaInsertDialog.js and ve.ui.MWMediaEditDialog.js. There's no ve.ui.ActionDialog.js.",1407896395,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","(In reply to Coiby from comment #7)
+> (In reply to Coiby from comment #6)
+> > This problem still exist on snapshot 9883566
+> > (https://extdist.wmflabs.org/dist/VisualEditor-REL1_23-9883566.tar.gz).
+> 
+> I just look through the patch, I can't find such file
+> ve/ui/dialogs/ve.ui.ActionDialog.json in snapshot 9883566.
+
+.js , not .json . Also, try looking for lib/ve/modules/ve/ui/dialogs/ve.ui.ActionDialog.js",1407896131,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","**Coiby.Xu** wrote:
+
+(In reply to Coiby from comment #6)
+> This problem still exist on snapshot 9883566
+> (https://extdist.wmflabs.org/dist/VisualEditor-REL1_23-9883566.tar.gz).
+
+I just look through the patch, I can't find such file ve/ui/dialogs/ve.ui.ActionDialog.json in snapshot 9883566.",1407896012,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","**Coiby.Xu** wrote:
+
+This problem still exist on snapshot 9883566 (https://extdist.wmflabs.org/dist/VisualEditor-REL1_23-9883566.tar.gz).",1407895586,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that",Verified the fix in production (en.wiki),1403302531,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that",Verified the fix on test2,1402690444,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that",Verified the fix on Betalabs,1402595814,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","Change 139019 merged by jenkins-bot:
+Re-enable apply button in action dialog on close
+
+https://gerrit.wikimedia.org/r/139019",1402526941,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","Change 139019 had a related patch set uploaded by Trevor Parscal:
+Re-enable apply button in action dialog on close
+
+https://gerrit.wikimedia.org/r/139019",1402526679,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","To reproduce:
+1. Edit an article in Arabic.
+2. Move the caret forward using the arrow keys.
+
+Observed: The Arabic letters next to which the caret moves are disconnected.
+
+Expected: Moving the caret must only move the caret. It must not change the appearance of the text.
+
+This works well in Firefox, but broken in Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402213980,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-yw4b4pmbrw2obgk33kph,task_description,resolved
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","I cannot reproduce it in recent versions of Safari, Chrome and Firefox.",1420878426,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","(In reply to Amir E. Aharoni from comment #3)
+> Well, I reported it, and I only have Chrome on Linux, so I guess I meant
+> ""Chrome"" or ""Blink"" and not ""WebKit"".
+
+If it was present in Chrome at that point in time though, depending on whether it was a recent regression in Chrome, it likely still exists in WebKit/Safari (since Blink is a fork of WebKit).",1409147282,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","Well, I reported it, and I only have Chrome on Linux, so I guess I meant ""Chrome"" or ""Blink"" and not ""WebKit"".",1409147088,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","Be sure to also test in a recent version of Safari (which runs on WebKit).
+
+Chrome hasn't been based on WebKit for almost 2 years now. It's using Chromium/Blink instead.",1409146973,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","I am not sure what fixed it, but it works for me now in Chrome 36.0.1985.143 on Fedora 20.
+
+Can this be tested automatically to prevent regression?",1409146067,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in test2
+2.Insert an image
+3.Change the image type to Frameless/Basic
+4.Now observe the checkbox for wrap is now unchecked
+5.Try to check the checkbox
+
+Observed Result:
+It does not check the checkbox , but all the alignment tabs becomes visible .
+
+This is happening in test2 only,
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14010}",1402096260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_description,resolved
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,Verified the fix in production (en.wiki),1403301056,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,Verified the fix in test2 running wmf9,1402696567,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"Change 138122 merged by jenkins-bot:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/138122",1402105349,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,This makes for a confusing bug history. :-),1402102858,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"Change 138122 had a related patch set uploaded by Jforrester:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/138122",1402102769,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"The patchset that fixed the wrapping textbox was merged yesterday evening. That might explain the inconsistency; it's not in mw and test2 yet.
+
+https://gerrit.wikimedia.org/r/#/c/137524/
+
+If this isn't happening in beta labs, it should show the patchset fixed the bug. (Correct me if I'm wrong?)",1402098589,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"Yes, it is also in MW.org , but not on Betalabs , not on en.wiki.
+
+So, its in wmf 8, not on wmf 7 and wmf 9",1402097353,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"This is happening in test2 and other wmf8 sites (like MW.org) but not wmf7s and Beta Labs, or just test2?",1402096999,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Initially the image is Thumbnail-right
+4.Now change the image type to Basic-Right-Border
+5.Apply changes
+6.Save the page
+7.Reopen the image
+8.Try to open the media settings dialog for the image
+
+Observed Result:
+Caption field is missing in the Media Settings dialog and cannot close the media settings dialog for the image.
+
+The following error appears in the console:
+
+TypeError: node is null appears in the console 
+
+This is happening in en.wiki and betalabs but not for some reason in test2
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13991}",1402092600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-otgwycebw25ej3on4cg6,task_description,resolved
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,Verified the fix in en.wiki running wmf 8,1402684839,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,"OK, let's declare this one fixed in wmf8. :-)",1402427523,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,"This is no more reproducible in Betalabs and test2 , but only on en.wiki",1402427465,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,"I can't manage to reproduce this bug in master on both Firefox and Chrome.
+
+Did this happen again?",1402426859,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,Try the image on this page to reproduce: https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1402092670,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"If the alignment of an image is not explicitly set, Parsoid does not output an alignment class for the resultant figure element. This can lead to the image not being aligned/floated.
+
+We need to modify content.parsoid.less to apply the default right-alignment styling to all images and then override this in cases where the alignment is explicitly set.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: normal",1402089360,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_description,resolved
+Default image alignment is not applied to parsoid-output figure elements,Seems like it must be fixed to me as of @Aklapper comment. @Gwicke correct me if wrong.,1446511244,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"(In reply to Gabriel Wicke from comment #5)
+> Right now this is deployed to group 1 wikis, but not yet to group 2. Lets
+> keep this open until it has made its way there.
+
+gwicke: So can this ticket be closed as FIXED?",1416053543,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"Right now this is deployed to group 1 wikis, but not yet to group 2. Lets keep this open until it has made its way there.
+
+Also see tracking bug 51245 for more Parsoid-specifc CSS tweaking.",1402934215,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,*** Bug 66668 has been marked as a duplicate of this bug. ***,1402934098,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"Change 138106 merged by jenkins-bot:
+Make sure images are properly aligned in Mobile VisualEditor
+
+https://gerrit.wikimedia.org/r/138106",1402353105,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"Change 138106 had a related patch set uploaded by Kaldari:
+Make sure images are properly aligned in Mobile VisualEditor
+
+https://gerrit.wikimedia.org/r/138106",1402096895,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"Change 138038 had a related patch set uploaded by Kaldari:
+Make sure images that don't have an explicit alignment get aligned right
+
+https://gerrit.wikimedia.org/r/138038",1402089519,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+VisualEditor: vesection not removed on save/cancel,"veaction is removed on save, but not vesection.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1402021260,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-3y4bzefvz74zyiylvmg7,task_description,resolved
+VisualEditor: vesection not removed on save/cancel,"Change 145277 merged by jenkins-bot:
+mw.ViewPageTarget: Remove vesection from URL on save/cancel
+
+https://gerrit.wikimedia.org/r/145277",1405001089,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3y4bzefvz74zyiylvmg7,task_subcomment,NA
+VisualEditor: vesection not removed on save/cancel,"Change 145277 had a related patch set uploaded by Alex Monk:
+Remove vesection from URL on save/cancel
+
+https://gerrit.wikimedia.org/r/145277",1404994761,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3y4bzefvz74zyiylvmg7,task_subcomment,NA
+VisualEditor: vesection not removed on save/cancel,Same for cancel.,1404937090,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-3y4bzefvz74zyiylvmg7,task_subcomment,NA
+VisualEditor:  Some images not displayed in the correct place ? due to floating,"Where the image was displayed before saving
+
+Steps to reproduce:
+
+1.  Open an article with a lot of images.  I started with https://en.wikipedia.org/w/index.php?title=Candy&oldid=611646505
+
+2.  Pick a right-aligned image and switch it to left-aligned.
+
+3.  Think, ""That's weird:  it seems to have put it in the middle of a paragraph or something"".
+
+4.  Drag the image to a more appropriate location.
+
+5.  Think, ""Hey, I put it up there, so why is it all the way down there?""
+
+
+NB that the diff here:  https://en.wikipedia.org/w/index.php?title=Candy&diff=611749324&oldid=611748715
+also places the image in between the text and the invisible {{anchor}} template that ought to be attached to the text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62850
+
+**Attached**: {F13861}",1402010880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kcdt6evoxb7dyclasvhr,task_description,open
+VisualEditor:  Some images not displayed in the correct place ? due to floating,"Created attachment 15579
+Where the image was (correctly) displayed after saving
+
+**Attached**: {F13862}",1402010936,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kcdt6evoxb7dyclasvhr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"Similar to how we have ve.batchSplice for splice.apply
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401993060,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nq5cnmniruskng2atihr,task_description,resolved
+VisualEditor: Replace uses of push.apply with something safe,"Change 166799 merged by jenkins-bot:
+Replacing push.apply in VE-MW with ve.batchPush from VE core
+
+https://gerrit.wikimedia.org/r/166799",1413481493,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"(In reply to Roan Kattouw from comment #5)
+> (In reply to James Forrester from comment #4)
+> > VE-MW patch coming or not needed?
+> 
+> There are two usages in VE-MW that do need to be cleaned up. Now that 166790
+> was pulled through into VE-MW (a few minutes ago) that can be done.
+
+Ugh somehow we missed the fact that there was a patch for this that was submitted three hours ago. We're both blind :S",1413413103,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"(In reply to James Forrester from comment #4)
+> VE-MW patch coming or not needed?
+
+There are two usages in VE-MW that do need to be cleaned up. Now that 166790 was pulled through into VE-MW (a few minutes ago) that can be done.",1413411436,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,VE-MW patch coming or not needed?,1413411219,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"Change 166790 merged by jenkins-bot:
+Replacing push.apply with newly created ve.batchPush in VE core
+
+https://gerrit.wikimedia.org/r/166790",1413400701,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"Change 166799 had a related patch set uploaded by SuchetaG:
+Replacing push.apply in VE-MW with ve.batchPush from VE core
+
+https://gerrit.wikimedia.org/r/166799",1413400657,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"Change 166790 had a related patch set uploaded by SuchetaG:
+Replacing push.apply with newly created ve.batchPush in VE core
+
+https://gerrit.wikimedia.org/r/166790",1413398862,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Link inspector should catch 400 errors from sending overly-long queries to the API,"This results in a quite bad outcome for the user, totally inexplicably. Instead we should just catch these errors and state them as invalid links (or have a different message?).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66135",1401914520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3c2zptsonkrp7vi7nbpx,task_description,resolved
+VisualEditor: Link inspector should catch 400 errors from sending overly-long queries to the API,"Change 138016 merged by jenkins-bot:
+Don't send invalid titles from the link inspector to the API
+
+https://gerrit.wikimedia.org/r/138016",1402102914,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3c2zptsonkrp7vi7nbpx,task_subcomment,NA
+VisualEditor: Link inspector should catch 400 errors from sending overly-long queries to the API,"Change 138016 had a related patch set uploaded by Alex Monk:
+Don't sent invalid titles from the link inspector to the API
+
+https://gerrit.wikimedia.org/r/138016",1402085857,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3c2zptsonkrp7vi7nbpx,task_subcomment,NA
+VisualEditor: Link inspector should catch 400 errors from sending overly-long queries to the API,Gerrit change 138016 should make it so that these show invalid title warnings. Though I haven't got CirrusSearch installed on my dev wiki so haven't tested it against the request_too_long Cirrus error.,1402085842,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3c2zptsonkrp7vi7nbpx,task_subcomment,NA
+VisualEditor: Create distribution files for VE core,"OOJS(UI) has a build script which creates a dist folder with concatenated JS/CSS and copied images and i18n files. VE should have the same so that:
+
+* We avoid IE9 stylesheet limits (31 files, 4096 rules)
+* We can create an RTL stylesheet using Janus.
+* We can embed small images inside the stylesheets.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401887280,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5pgxr7pnqmtyrolp2ztp,task_description,resolved
+VisualEditor: Create distribution files for VE core,"Change 137367 merged by jenkins-bot:
+Grunt: Create a distribution files for the ve module
+
+https://gerrit.wikimedia.org/r/137367",1404270407,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5pgxr7pnqmtyrolp2ztp,task_subcomment,NA
+VisualEditor: Create distribution files for VE core,"Change 137367 had a related patch set uploaded by Jforrester:
+Grunt: Create a single file stand-alone distribution for demos etc.
+
+https://gerrit.wikimedia.org/r/137367",1401905976,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5pgxr7pnqmtyrolp2ztp,task_subcomment,NA
+"VisualEditor: For all drop down boxes, the first match with check mark and highlight, loses it highlight upon hovering over it and then moving mouse out of the object","Screenshot
+
+Steps to reprduce:
+
+1.Open VE
+2.Open any drop down box that comes up with a list of matching suggestions:for example:Link inspector, Category editor, template etc.
+3.Type something in the text box
+4.When the matching suggestions appear in the drop down box,observe that the first match which has a check mark next to it, is highlighted
+5.Now mouse over that match in the drop down and 
+
+Observed Result:
+The selection loses it highlight
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13596}",1401841740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6xolie2zefzogwp7ndhu,task_description,resolved
+"VisualEditor: For all drop down boxes, the first match with check mark and highlight, loses it highlight upon hovering over it and then moving mouse out of the object",Appears to have been fixed.,1402921830,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6xolie2zefzogwp7ndhu,task_subcomment,NA
+"VisualEditor: For all drop down boxes, the first match with check mark and highlight, loses it highlight upon hovering over it and then moving mouse out of the object",Not a shield issue.,1402921809,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6xolie2zefzogwp7ndhu,task_subcomment,NA
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again","Screenshot
+
+Steps to reproduce:
+
+
+1.Open VE
+2.Go to Page options>Categories
+3.Insert a new category:Ca, it appears under matching categories section according to the change on https://bugzilla.wikimedia.org/show_bug.cgi?id=49044
+4.Select the first match Ca
+4.Now again type Ca
+
+Observed Result:
+This time it appears under New Category section.
+
+
+see the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13594}",1401840480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v376iz64hfsix2c3s4lh,task_description,resolved
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again",Verified the fix in en.wiki running wmf 8,1402688290,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-v376iz64hfsix2c3s4lh,task_subcomment,NA
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again","Fixed. That function is full of horrible things to do with following redirects (where a supposed category is actually a redirect to another category) and categories which are marked as hidden, mostly my fault and probably full of bugs if you want to poke around with that. Particularly in cases where we're supposed to exclude suggestions due to already having the suggestion on the list.",1401920048,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-v376iz64hfsix2c3s4lh,task_subcomment,NA
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again","Change 137307 merged by jenkins-bot:
+Check last existing category for whether or not we're trying to re-add it
+
+https://gerrit.wikimedia.org/r/137307",1401919823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v376iz64hfsix2c3s4lh,task_subcomment,NA
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again","Change 137307 had a related patch set uploaded by Alex Monk:
+Check last existing category for whether or not we're trying to re-add it
+
+https://gerrit.wikimedia.org/r/137307",1401889985,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v376iz64hfsix2c3s4lh,task_subcomment,NA
+VisualEditor: Issues with shields/highlights/phantoms (tracking),"This is a tracking bug for all shields/highlights/phantoms related issues.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401819000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p7uyyr5xswg5yrofkqdd,task_description,declined
+VisualEditor: Issues with shields/highlights/phantoms (tracking),Tracking bug with no outstanding blockers. Closing.,1411510006,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p7uyyr5xswg5yrofkqdd,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"This is overdue.
+
+Various packages used by individual Grunt tasks used by local projects already throw warnings for the engine being unsupported.
+
+These are not the packages for the legacy global tools in package.json in integration/jenkins.git:/tools aka slave-scripts, but the local package.json in projects like oojs, oojs-ui and VisualEditor.
+
+As far as I can see these jobs seem to function fine, but it's really dangerous territory. The packages are explicitly indicated as requiring 0.10.x or higher (it's like executing a PHP application documented as requiring PHP 5.3 under PHP 5.1.x).
+
+Both the upstream developer, their integration tests and the developers in our teams working locally already use Nodejs 0.10.x or higher, so this is waiting for something to fail.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1401749760,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_description,resolved
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"Change 159224 merged by jenkins-bot:
+job-templates: Move {name}-npm from Precise to Trusty
+
+https://gerrit.wikimedia.org/r/159224",1411259816,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"Change 159224 had a related patch set uploaded by Krinkle:
+[WIP] job-templates: Move {name}-npm from Precise to Trusty
+
+https://gerrit.wikimedia.org/r/159224",1410222687,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"The Trusty slave is integration-slave1006-trusty.eqiad.wmflabs
+
+The label remain unchanged:  UbuntuTrusty.
+
+
+Marking this bug as fixed since npm/nodejs are available there. ""Just"" have to update the label in the job configuration.",1408703173,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"We have a Trusty Jenkins slave in labs: integration-slave1004-trusty.eqiad.wmflabs
+
+It has the label UbuntuTrusty.  The npm based jobs can be made to run on it by changing the node:  definition in Jenkins Job Builder configuration.
+
+The node has:
+
+$ npm --version
+1.3.10
+$ nodejs --version
+v0.10.25
+$",1406886366,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"On contint slaves we have nodejs 0.8.2 which comes from apt.wikimedia.org.  AFAIK that is the version used on parsoid servers as well.
+
+When I asked npm package to be backported with RT #6519 Faidon the plan is to migrate to Ubuntu Trusty (14.04) which ships 0.10.25.
+
+wmflabs now provides a Trusty virtual image and we run npm jobs there.
+
+So you can:
+- build an instance using Trusty image
+- attempt to apply the puppet manifest role::ci::slave::labs
+- add the slave in Jenkins (we can pair that part)
+- apply a label to the slave (ex: UbuntuTrusty) and tie some job to it
+
+
+A culprit: anything running in production with nodejs 0.8 should probably be kept with nodejs 0.8 (parsoid parser tests come to mind) or we might end up missing incompatibility.  You can sync with Gabriel Wicke for that part.
+
+
+Overall: yeah lets go!",1401752278,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+"VisualEditor:  Be able to specify a file name in the media or image dialog, even if search can't find the file","This might be something that could be associated with Bug 52463:
+
+If Search can't find an image—which happens fairly often with images that the user just uploaded—then please let the user specify the file name anyway.  Right now, if Search didn't happen to index your file yet, then you cannot add the image.  ""Try again tomorrow, because maybe the search index will have caught up by then"" is not an ideal user experience.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401737880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-bi34wimyectesmdx6jar,task_description,declined
+"VisualEditor:  Be able to specify a file name in the media or image dialog, even if search can't find the file",I disagree with your comment about search results working fine now. I added some findings to https://bugzilla.wikimedia.org/show_bug.cgi?id=62917#c1 .,1409737567,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bi34wimyectesmdx6jar,task_subcomment,NA
+"VisualEditor:  Be able to specify a file name in the media or image dialog, even if search can't find the file","(In reply to Elitre from comment #1)
+> Isn't this fixed?
+> Right now I can paste the file name of the pic I want while adding a media.
+> It looks like the only way to currently get to the desired image, because
+> the search seems to be even worse than I remembered (try looking for a
+> ""European robin"" image on en.wp, give up in frustration, paste
+> File:Erithacus rubecula with cocked head.jpg in the dialog to put the image
+> on the page after you found it on Commons).
+
+Technically not done, but the search results generally work well enough.",1409583730,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bi34wimyectesmdx6jar,task_subcomment,NA
+"VisualEditor:  Be able to specify a file name in the media or image dialog, even if search can't find the file","Isn't this fixed?
+Right now I can paste the file name of the pic I want while adding a media. It looks like the only way to currently get to the desired image, because the search seems to be even worse than I remembered (try looking for a ""European robin"" image on en.wp, give up in frustration, paste File:Erithacus rubecula with cocked head.jpg in the dialog to put the image on the page after you found it on Commons).",1409569002,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bi34wimyectesmdx6jar,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,"There should be links http://stats.wikimedia.org/EN/EditsRevertsIT.htm <-> http://ee-dashboard.wmflabs.org/dashboards/itwiki-metrics#reverts-graphs-tab and http://ee-dashboard.wmflabs.org/dashboards/itwiki-metrics#registrations-graphs-tab <-> http://ee-dashboard.wmflabs.org/dashboards/itwiki-metrics#registrations-graphs-tab .
+Only applies to the ten Wikipedias having them: https://meta.wikimedia.org/wiki/Research:VisualEditor
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401617460,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-w6vt4utuqyldv2cmmund,task_description,declined
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,We're killing ee-dashboard (and have been for three years); let's not add more cruft and links to it.,1463086361,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,">>! In T67994#1773128, @ezachte wrote:
+> What's the best way to detect which language codes have new stats? (other than screen scraping https://meta.wikimedia.org/wiki/Research:VisualEditor)
+
+I guess parsing the list of *wiki directories at https://datasets.wikimedia.org/public-datasets/",1446540387,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,What's the best way to detect which language codes have new stats? (other than screen scraping https://meta.wikimedia.org/wiki/Research:VisualEditor),1446464875,PHID-USER-m5uwh66djeylkim5chfe,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,"Nemo: Are you still working on this, as this ticket is assigned to you?",1416496278,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,Good idea Nemo. Erik -- thoughts?,1401736314,PHID-USER-ud7f5gp5h3uqup6viq4e,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+VisualEditor: Do not allow creation of empty lists inside tables (?!),"This should not happen:
+https://pt.wikipedia.org/w/index.php?diff=39042930
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401531960,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-iqrozz7c5dzdomgukors,task_description,open
+Unrelated content in produced PDF,"Sample PDF
+
+1) http://eo.wikipedia.beta.wmflabs.org/wiki/Headings_VisualEditor_Test
+2) ""Elŝuti kiel WMF PDF""
+
+Result: a page with content coming from I have no idea where, see attachment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13832}",1401439440,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-alhxfplatrwdgk43xfb3,task_description,resolved
+Unrelated content in produced PDF,I filled a bug to have an integration job that ensure puppet repo is updated before all-labs.dblist has a new wiki added. https://bugzilla.wikimedia.org/show_bug.cgi?id=68532,1406235686,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"Change 148330 merged by Alexandros Kosiaris:
+beta: update Parsoid localsettings entries
+
+https://gerrit.wikimedia.org/r/148330",1406018271,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,I have applied the puppet patch above on the beta cluster and restarted Parsoid that should fix the issue.,1406017249,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"Change 148330 had a related patch set uploaded by Hashar:
+beta: update Parsoid localsettings entries
+
+https://gerrit.wikimedia.org/r/148330",1406016978,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,Amended the add wiki documentation https://wikitech.wikimedia.org/w/index.php?title=Nova_Resource:Deployment-prep/Add_a_wiki&diff=120678&oldid=120568,1406016177,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"Matt says PDF is using Parsoid has a backend.
+C. Scott reproduces the issue with VisualEditor.
+
+That means Parsoid is badly configured on beta and use the wrong backend.  Maybe it is fetching articles from production API?
+
+And the winner is: Antoine! The list of wikis is hardcoded in a puppet configuration file http://git.wikimedia.org/blob/operations%2Fpuppet.git/c585887114/files%2Fmisc%2Fparsoid-localsettings-beta.js and the documentation to add a wiki is missing that step https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/Add_a_wiki",1406015986,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"(In reply to C. Scott Ananian from comment #3)
+> That is, the PDF renderer is misconfigured on eo.beta and is requesting
+> pages from eowiki instead.  It is communicating its request by page id...
+> with the surprising results you have noted.
+
+cc hashar",1405664326,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"The page you are trying to print is:
+http://eo.wikipedia.beta.wmflabs.org/w/index.php?title=Headings_VisualEditor_Test&oldid=11
+
+The content you are getting is:
+https://eo.wikipedia.org/w/index.php?title=Headings_VisualEditor_Test&oldid=11
+
+That is, the PDF renderer is misconfigured on eo.beta and is requesting pages from eowiki instead.  It is communicating its request by page id... with the surprising results you have noted.
+
+But ultimately this is an eo.wiki misconfiguration.  Note that http://eo.wikipedia.beta.wmflabs.org/wiki/Headings_VisualEditor_Test?veaction=edit is also ""surprising"".",1405655198,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"**mwalker** wrote:
+
+It's not a problem per-se with the renderer; we're rendering what parsoid is giving us... I'm not sure what parsoid is doing.",1405652831,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,That may have to do with FlaggedRevs (or with the wiki being empty): http://simple.wikipedia.beta.wmflabs.org/wiki/List_of_literary_terms worked,1401439983,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+VisualEditor: Remove gallery button from the Insert Menu,"Screenshot
+
+I dont see any option to insert gallery in the Insert medu suddenly.
+Happening in betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13825}",1401431340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s4vdrbpgig26i4hixati,task_description,resolved
+VisualEditor: Remove gallery button from the Insert Menu,Verified the fix in production,1402086311,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s4vdrbpgig26i4hixati,task_subcomment,NA
+VisualEditor: Remove gallery button from the Insert Menu,"Yes, sorry, this was done intentionally in gerit 135965.",1401471842,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s4vdrbpgig26i4hixati,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Steps to reproduce:
+
+1.Click on the Edit/Edit Beta link beside a section heading of an article
+
+Observed Result:
+It places the cursor at the beginning of the document .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401412380,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qh467vyga6czchrrd2p,task_description,resolved
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"(In reply to Tony Thomas from comment #11)
+> This still happens. Check
+> https://www.mediawiki.org/w/index.
+> php?title=WYSIWYG_editor&veaction=edit&vesection=18 from chrome !
+
+Eugh, there seems to be a regression here when clicked on the page; if you click that link it works fine… As such, rather than re-opening I've created bug 72919 for this. Thanks for the spot.",1415045956,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,This still happens. Check https://www.mediawiki.org/w/index.php?title=WYSIWYG_editor&veaction=edit&vesection=18 from chrome !,1415035976,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Verified the fix in production. There is a different issue with cursor now though 
+which has been reported in:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67106",1403892427,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"WFM; cache issue, it appears.",1403726656,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,This is still happening on FireFox in Betalabs running from master.,1403723709,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,Probably a deployment issue; fixed on MW.org and test2.,1403622161,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,WFM in Firefox at http://en.wikipedia.beta.wmflabs.org/wiki/WikiNodes and on master,1403620028,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Not fixed for Firefox , there is no cursor at all pointing anywhere in the document after clicking on Edit link for section editing.",1403305166,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,Verified the fix in Betalabs,1403043756,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Change 139677 merged by jenkins-bot:
+Wait for onDocumentFocus to happen before setting section range
+
+https://gerrit.wikimedia.org/r/139677",1402835997,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Change 139677 had a related patch set uploaded by Esanders:
+Wait for onDocumentFocus to happen before setting section range
+
+https://gerrit.wikimedia.org/r/139677",1402833473,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"It seems like the dm.Surface's selection is getting set to the beginning of the section like it should be, but then when the ce/ui.Surface is intialized, the cursor isn't put there. It seems the surface isn't focused correctly on init anyway, and as soon as you interact with it SurfaceObserver will notice the cursor is at (1,1) and change the DM selection to that.",1402002772,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+"VisualEditor: On pages which are redirects, veaction=edit should actually do redirect=no&veaction=edit","Steps to Reproduce:
+1. Click on https://en.wikipedia.org/wiki/Sugar_candies?veaction=edit
+
+2. Wonder why it is editing https://en.wikipedia.org/wiki/Sugar_candy (the target) instead of https://en.wikipedia.org/wiki/Sugar_candies (the redirect)?
+
+
+Actual Results:  
+It first redirects me to the target page, and then opens the target page for editing.  This makes it impossible to change the redirect to some other page, unless you modify the URL to say https://en.wikipedia.org/wiki/Sugar_candies?veaction=edit&redirect=no (either manually or by first visiting to the redirect page).
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65621",1401409620,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-i33x4h5mjnat262gctqt,task_description,resolved
+"VisualEditor: On pages which are redirects, veaction=edit should actually do redirect=no&veaction=edit","Change 138585 merged by jenkins-bot:
+Suppress redirects if veaction=edit is requested
+
+https://gerrit.wikimedia.org/r/138585",1402422369,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i33x4h5mjnat262gctqt,task_subcomment,NA
+"VisualEditor: On pages which are redirects, veaction=edit should actually do redirect=no&veaction=edit","Change 138585 had a related patch set uploaded by Alex Monk:
+Suppress redirects if veaction=edit is requested
+
+https://gerrit.wikimedia.org/r/138585",1402402998,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i33x4h5mjnat262gctqt,task_subcomment,NA
+"VisualEditor: On pages which are redirects, veaction=edit should actually do redirect=no&veaction=edit","https://en.wikipedia.org/w/index.php?title=Sugar_candies&redirect=no&veaction=edit works fine, but https://en.wikipedia.org/wiki/Sugar_candies?veaction=edit takes you to the target. Bah.",1401412090,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i33x4h5mjnat262gctqt,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Steps to Reproduce:
+1. Open a page that contains inline images at the start of a paragraph or list item.
+
+2. Select the image, open the image dialog, and de-select the ""Wrap text around"" item.  The item will float right.
+
+3. Change your mind.  Open the imge dialog again, and re-select the ""Wrap text around"" item.
+
+Actual Results:  
+The inline image appears to be, but isn't actually, on its own line.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401406980,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_description,resolved
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 139269 merged by jenkins-bot:
+Insert inline image inside list to the existing paragraph
+
+https://gerrit.wikimedia.org/r/139269",1403034579,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 139064 abandoned by Mooeypoo:
+Add inline images into existing paragraphs
+
+Reason:
+Moving this to the MWImageModel in a new commit
+
+https://gerrit.wikimedia.org/r/139064",1402611641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 139269 had a related patch set uploaded by Mooeypoo:
+Don't create new paragraph for inline image inside list
+
+https://gerrit.wikimedia.org/r/139269",1402610848,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 139064 had a related patch set uploaded by Mooeypoo:
+Add inline images into existing paragraphs
+
+https://gerrit.wikimedia.org/r/139064",1402545423,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"(In reply to Gerrit Notification Bot from comment #8)
+> Change 138114 had a related patch set uploaded by Catrope:
+> [BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window
+> process cleanup
+> 
+> https://gerrit.wikimedia.org/r/138114
+
+Whoops, not relevant; my mistake.",1402533723,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 138114 had a related patch set uploaded by Catrope:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533465,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"If we can have fixUpInsertion insert the image into an existing paragraph in the case of lists, that can be a good solution too.",1401906392,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,Why does it always add a paragraph? Surely that's for fixUpInsertion to decide?,1401905156,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"After further examination, this isn't an image bug per say, it is a list bug.
+
+When the image is transformed from block to inline it goes back to being on its own paragraph (as it does always regardless of lists) letting the user decide where it should be.
+
+The problem with the list, however, is that when the image goes back to being inline it is presented as if it is on its own line inside the list (with the text being on a different paragraph in the list item) 
+
+However, the list itself won't allow for multi paragraphs and the resulting wikitext shows the image and followup text without the extra line space.
+
+We could either add a <br> in between the image and the new text (in Parsoid?) or find a creative solution to make lists with multiline text behavior reflect that of the resulting wikitext in general.",1401904664,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Created attachment 15535
+Before moving the image.  This is what it ought to look like after I move it back, too (perhaps minus the space between image and text).
+
+**Attached**: {F13791}",1401462992,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Created attachment 15534
+Inline image has been moved back, and displays on its own line
+
+**Attached**: {F13789}",1401462938,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Look at what happens to the ""laundromat"" image at http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=100058&oldid=100057
+
+It was inline; I made it be a normal/non-inline image (perhaps ""floating"" isn't the right word?).  Then I moved it back.  When I moved it back, it displayed oddly—on its own line in the display, although it was inline when I saved.  
+
+I'll upload some screenshots for you.",1401462772,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"I'm a bit confused. You mentioned you need to de-select the floating value of the image, but inline images aren't supposed to have floating values at all (the checkbox should be unchecked) -- are you sure you're looking at inline images, or that you unchecked the value first?
+
+Can you give me an example to look at? Thanks!",1401424249,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Screenshot
+
+Steps to reproduce:
+
+1.Insert an image of any type
+
+2.Uncheck the wrap option
+
+3.Check the wrap option again
+
+4.Checking the wrap option automatically selects the ""Right"" as alignment again
+
+5.Now click on one of the other alignment option:Centre/Left
+
+Observed Result:
+
+The alignment tab for ""Right"" is still selected, also the new one of step 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13768}",1401400020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2dy4aao545tjoscghlgd,task_description,resolved
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,Verified the fix in production (en.wiki),1403301154,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,Verified the fix in test2 running wmf9,1402696114,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,Verified the fix in Betalabs,1402350197,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 138122 merged by jenkins-bot:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/138122",1402105346,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 138122 had a related patch set uploaded by Jforrester:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/138122",1402102762,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 137524 merged by jenkins-bot:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/137524",1402018372,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 137729 merged by jenkins-bot:
+Allow programmatic selection of options while disabled
+
+https://gerrit.wikimedia.org/r/137729",1402017589,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 137729 had a related patch set uploaded by Catrope:
+Allow programmatic selection of options while disabled
+
+https://gerrit.wikimedia.org/r/137729",1402001211,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 137524 had a related patch set uploaded by Mooeypoo:
+[wip] Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/137524",1401935542,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Also, if you set the image type to Basic, the alignment checkbox will behave really strangely:
+
+1. Set image type to basic
+2. Checkbox is unticked, left/center/right toggle is disabled
+3. Click checkbox. Checkbox is ticked and immediately unticked again, but left/center/right toggle is now enabled.
+4. Click Left. Checkbox is ticked
+5. Untick checkbox. Toggle is now disabled again
+
+Go home alignment widget, you're drunk.",1401925266,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+"VisualEditor: When providing a list of potential links, show redirects' destinations, not just that they are redirects","VisualEditor can determine if the link you are adding is a redirect or not (since Bug 50240), but it doesn't tell what the redirect page goes to. Just seeing ""Redirect page"" in the linking tool doesn't tell the user whether or not they're linking to the page they want to be linking to, so I think it should say ""Redirect page to $1"", where $1 is the destination of the redirect that's being linked.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401343080,PHID-USER-qze3uk4zsetjvgf7liey,PHID-TASK-dlmffyeaeajaau5cpsge,task_description,resolved
+"VisualEditor: When providing a list of potential links, show redirects' destinations, not just that they are redirects",This was fixed a while ago.,1435939976,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dlmffyeaeajaau5cpsge,task_subcomment,NA
+"VisualEditor: When providing a list of potential links, show redirects' destinations, not just that they are redirects","(In reply to James Forrester from comment #1)
+> The idea is that it's generally a mistake to link to a redirect, and it's
+> generally discouraged on most (all?) wikis. However, yes, this might be a
+> nice improvement.
+
+In that case, it'd be very helpful for editors for VisualEditor to show where the redirect goes to. If you're linking to a redirect and doing so is discouraged on that wiki, it's helpful to know what you should be linking to instead! :)",1401400411,PHID-USER-qze3uk4zsetjvgf7liey,PHID-TASK-dlmffyeaeajaau5cpsge,task_subcomment,NA
+"VisualEditor: When providing a list of potential links, show redirects' destinations, not just that they are redirects","The idea is that it's generally a mistake to link to a redirect, and it's generally discouraged on most (all?) wikis. However, yes, this might be a nice improvement.",1401377050,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dlmffyeaeajaau5cpsge,task_subcomment,NA
+VisualEditor: Changing image from floated (right+basic) to thumb does not update size correctly,"Take an image like [[File:Bigimage.png|border|right]], inspect it, and change it to a thumbnail. You get a thumbnail image of the exact same dimensions. But when you save, this serializes to [[File:Whatever.png|thumb]], which renders in read mode (and when you reopen it in VE) as a much smaller image, because it's using the default thumb size.
+
+I would argue that, when you switch to thumb, it should use the default size for thumbs right then and there, but in any case, it's clear here that what's being displayed in CE is not an accurate reflection of what's actually going to happen when the user saves, and that's a problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401325260,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-futqy7nlsvxuqr4dx2cu,task_description,resolved
+VisualEditor: Changing image from floated (right+basic) to thumb does not update size correctly,"Change 136981 merged by jenkins-bot:
+Update image size after changing type
+
+https://gerrit.wikimedia.org/r/136981",1401925856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-futqy7nlsvxuqr4dx2cu,task_subcomment,NA
+VisualEditor: Changing image from floated (right+basic) to thumb does not update size correctly,"Change 136981 had a related patch set uploaded by Mooeypoo:
+Update image size after changing type
+
+https://gerrit.wikimedia.org/r/136981",1401780873,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-futqy7nlsvxuqr4dx2cu,task_subcomment,NA
+VisualEditor: Make SurfaceWidget constructor not depend on global target,"See discussion at https://gerrit.wikimedia.org/r/#/c/135012/ . I think the SurfaceWidget constructor shouldn't use the global target, but instead take a config option telling it what kind of surface to construct, or take a surface object, or something.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401319080,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-64xilll6eo5zib7plcyu,task_description,open
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","If the ""description"" field for TemplateData is empty, clicking the help/information button (an i with a circle around it) for the parameter produces a very skinny, empty box.  Nothing should be displayed when there is no description to display.
+
+Alternatively, it's possible that some standard text could be put in the box, like ""There is no description for this item"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401297960,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-667pdzsnat3vywzbk5ru,task_description,resolved
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","Change 136348 merged by jenkins-bot:
+Trim description when working out whether or not we should disable the info button
+
+https://gerrit.wikimedia.org/r/136348",1401474560,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button",Thanks!,1401471687,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","Change 136348 had a related patch set uploaded by Alex Monk:
+Trim description when working out whether or not we should disable the info button
+
+https://gerrit.wikimedia.org/r/136348",1401470435,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","Ah:  the TemplateData at https://en.wikipedia.org/wiki/Template:Infobox_UK_place/doc#TemplateData says,
+
+
+""os_grid_reference"": { ""label"": ""os grid reference"", ""description"": "" "", ""type"": ""string"", ""required"": false },
+
+
+If it said this instead,
+
+""os_grid_reference"": { ""label"": ""os grid reference"", ""description"": """", ""type"": ""string"", ""required"": false },
+
+or perhaps this:
+
+""os_grid_reference"": { ""label"": ""os grid reference"", ""type"": ""string"", ""required"": false },
+
+(if it's permitted to omit the description item), then this should go away.",1401469622,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","The description is set as a single space for this parameter, so I think this is expected behaviour.",1401462759,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","Open the infobox in https://en.wikipedia.org/wiki/Aberystwyth and look at the parameter ""os_grid_reference"".
+
+The original report is at https://en.wikipedia.org/w/index.php?oldid=610519258#Info_on_template_fields",1401462539,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","WhatamIdoing, can you perhaps give an example page where it does this?",1401453961,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","If the parameter is required, I do get 'Field is required.' which should be shown still. But if it's not required, then the help/information button is disabled... No empty box.",1401453869,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","I thought we had disabled these, but apparently not. Bah.",1401392630,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a new image
+3.Select the option ""Centre"" for wrapping the text around it
+4.Select the type as ""Frameless"" or ""Basic""
+5.Save the page
+
+Observed Result:
+
+The image moves to the left side of the page 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13568}",1401230100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,Verified the fix in production,1402087975,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,Verified the fix in test2,1401403091,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,Verified the fix on betalabs,1401316525,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,"Change 135729 merged by jenkins-bot:
+Make sure <figure> has proper dimensions
+
+https://gerrit.wikimedia.org/r/135729",1401303252,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,"Change 135729 had a related patch set uploaded by Mooeypoo:
+Make sure <figure> has proper dimensions
+
+https://gerrit.wikimedia.org/r/135729",1401241733,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: Issues with new Image model (tracking),"This is a tracking bug for all the issues related with new Image model
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401217980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cmqoovhbvvqbxuay3bwi,task_description,resolved
+VisualEditor: Issues with new Image model (tracking),Wow. This looks nice.,1403120147,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cmqoovhbvvqbxuay3bwi,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"On mediawiki.org in both Chrome and FF. 
+
+Edit any page with VE, either logged in or not.  Note that you get the beta warning.
+
+Save your edit. Edit the page again. 
+
+See the beta warning again.
+
+After one new VE edit, the user should never see the beta warning again.  This is controlled by setting a cookie in the browser.  No betawarning cookie is being set now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1401210720,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-jc3gqyo3pxpfmohz2253,task_description,resolved
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136124 merged by jenkins-bot:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136124",1401485083,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136122 merged by jenkins-bot:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136122",1401485066,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136122 had a related patch set uploaded by Alex Monk:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136122",1401482358,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136124 had a related patch set uploaded by Jforrester:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136124",1401382643,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136120 merged by jenkins-bot:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136120",1401382641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136120 had a related patch set uploaded by Alex Monk:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136120",1401381771,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,Also getting reports of this on enwiki etc. – not great.,1401217265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Yeah, this is a worrying regression, possibly due to the bug 55551 changes.
+
+(Saw breakage for Rummana on her account on MW.org, so this is probably a timing issue related to when the accounts hit a wiki before the code changed or similar?)",1401214599,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Actually, this is seen on test2 only so far.",1401212317,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,*** Bug 65710 has been marked as a duplicate of this bug. ***,1401210879,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+Enabling TemplateData editor in Catalan Wikipedia,"/me waves with my volunteer ca.wiki tech ambassador hat on.
+
+The Catalan Wikipedia community wants to try the TemplateData editor. Can you enable it, please? Discussion (in Catalan) at
+
+https://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Ajuda#VisualEditor_global_newsletter.E2.80.94May_2014
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401145140,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-fkv4g3aqxijtbgft56ij,task_description,resolved
+Enabling TemplateData editor in Catalan Wikipedia,This is now live.,1402010019,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fkv4g3aqxijtbgft56ij,task_subcomment,NA
+Enabling TemplateData editor in Catalan Wikipedia,"Change 135580 merged by jenkins-bot:
+Enable TemplateData GUI on Catalan Wikipedia
+
+https://gerrit.wikimedia.org/r/135580",1401992640,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fkv4g3aqxijtbgft56ij,task_subcomment,NA
+Enabling TemplateData editor in Catalan Wikipedia,"Change 135580 had a related patch set uploaded by Jforrester:
+Enable TemplateData GUI on Catalan Wikipedia
+
+https://gerrit.wikimedia.org/r/135580",1401206855,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fkv4g3aqxijtbgft56ij,task_subcomment,NA
+VisualEditor: Left/right cursoring into block slug doesn't trigger animations,"--------------------------
+**Version**: unspecified
+**Severity**: normal",1401018180,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gs7sqst6umknljvlszmu,task_description,resolved
+VisualEditor: Left/right cursoring into block slug doesn't trigger animations,"Change 190022 merged by jenkins-bot:
+Simplify slug behaviour
+
+[[https://gerrit.wikimedia.org/r/190022]]",1424725248,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gs7sqst6umknljvlszmu,task_subcomment,NA
+VisualEditor: Left/right cursoring into block slug doesn't trigger animations,"Change 190022 had a related patch set uploaded (by Esanders):
+Simplify slug behaviour
+
+[[https://gerrit.wikimedia.org/r/190022]]
+
+#patch-for-review",1423756454,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gs7sqst6umknljvlszmu,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it Frameless-right or Basic-Right
+4.Hover over the image after that
+
+Observed Result:
+The area around the image remains highlighted but not the image itself
+
+See the screenshot attached
+Environment: Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13899}",1400889120,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nwx24kr2omo3papjy3ml,task_description,resolved
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right",Verified the fix in production,1403900614,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right",Verified the fix in test2,1403303677,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 140747 merged by Catrope:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140747",1403200717,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 140747 had a related patch set uploaded by Jforrester:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140747",1403200681,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 140687 merged by jenkins-bot:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140687",1403200677,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 140687 had a related patch set uploaded by Esanders:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140687",1403175920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 139824 merged by jenkins-bot:
+Fix selection after inserting nodes
+
+https://gerrit.wikimedia.org/r/139824",1403132279,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 137040 merged by jenkins-bot:
+[BREAKING CHANGE (ish)] Track original data position in insertion operations
+
+https://gerrit.wikimedia.org/r/137040",1403130608,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 139824 had a related patch set uploaded by Esanders:
+Fix selection after inserting nodes
+
+https://gerrit.wikimedia.org/r/139824",1402925757,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 137040 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE (ish)] Track orignal data position in insertion operations
+
+https://gerrit.wikimedia.org/r/137040",1402923261,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","
+
+*** This bug has been marked as a duplicate of bug 65706 ***",1402923208,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Selection range issue, not a shield issue.",1402921893,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Corrected steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it Frameless-Left or Basic-Left
+4.Now uncheck the wrapping option.
+5.Hover over the image after that.
+
+Observed Result:
+The area around the image remains highlighted but not the image itself.",1401323936,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400885280,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_description,resolved
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,Verified the fix in production,1403893138,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,Verified the fix in test2,1403304493,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 140747 merged by Catrope:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140747",1403200714,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 140747 had a related patch set uploaded by Jforrester:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140747",1403200685,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 140687 merged by jenkins-bot:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140687",1403200674,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 140687 had a related patch set uploaded by Esanders:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140687",1403175915,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 139824 merged by jenkins-bot:
+Fix selection after inserting nodes
+
+https://gerrit.wikimedia.org/r/139824",1403132282,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"DM selection issue, not a shield bug.",1402925615,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 139824 had a related patch set uploaded by Esanders:
+Fix selection after inserting nodes
+
+https://gerrit.wikimedia.org/r/139824",1402925569,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,*** Bug 65716 has been marked as a duplicate of this bug. ***,1402923208,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,The previous line also gets highlighted while adding an image.,1401819912,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,This is happening in Chrome only not in Firefox,1400886178,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to the end of the page 
+3.Insert a reference list
+
+Observed Result:
+It is highlighting the previous line while adding the reference list.
+This behavior has been observed as of 23rd may",1400885687,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","""Translation unit markers in unexpected position."" can just go die in Hell. Gah.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also:** {T58451}, {T73730}, {T50891}",1400786640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_description,open
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort",FWIW [[https://www.mediawiki.org/w/index.php?title=Manual:Developing_extensions&diff=2696555&oldid=2696554|this]] worked in the end.,1516414993,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","Also results in a bunch of JS errors along the line of
+```
+Uncaught TypeError: Cannot read property 'top' of null
+    at <anonymous>:405:348
+    at Array.forEach (<anonymous>)
+    at VeUiDiffElement.ve.ui.DiffElement.positionDescriptions (<anonymous>:405:25)
+    at <anonymous>:682:225
+    at VeUiMwSaveDialog.OO.ui.Window.withoutSizeTransitions (<anonymous>:45:1)
+    at <anonymous>:682:129
+```
+and
+```
+Uncaught TypeError: Cannot read property 'getSelection' of undefined
+    at VeUiFindAndReplaceDialog.ve.ui.FindAndReplaceDialog.renderRangeOfFragments (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:952)
+    at VeUiFindAndReplaceDialog.ve.ui.FindAndReplaceDialog.renderFragments (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:952)
+    at run (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:1048)
+    at VeUiFindAndReplaceDialog.renderFragmentsThrottled (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:1048)
+    at VeUiFindAndReplaceDialog.ve.ui.FindAndReplaceDialog.onSurfaceViewPosition (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:949)
+    at VeCeMwWikitextSurface.oo.EventEmitter.emit (<anonymous>:233:445)
+    at VeCeMwWikitextSurface.<anonymous> (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:713)
+    at later (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:1048)
+```
+I think those started propping up after trying visual diff for curiosity (broken by Translate, of course).",1516414841,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort",">>! In T67653#3363689, @Deskana wrote:
+> Can you give me some more details on what the problem is, and what the steps to reproduce are? 
+
+Open a translatable page for editing, do an innocent change, get useless error report.
+E.g. I'm trying to save https://www.mediawiki.org/w/index.php?title=Manual:Developing_extensions&oldid=2696554 with this diff:
+
+```lang=diff
+--- 1.txt	2018-01-19 18:12:32.130524437 -0800
++++ 2.txt	2018-01-19 18:13:50.941714520 -0800
+@@ -479,11 +479,11 @@
+ 
+ <translate>
+ 
+-==Support other core versions== <!--T:286-->
++==Support other core versions== <!--T:286--></translate>
+ <!-- keep this in sync with [[Compatibility#MediaWiki_extensions]] -->
+ 
+-<!--T:315-->
+-There are two widespread conventions for supporting older versions of MediaWiki core:</translate>
++<translate>
++<!--T:315-->There are two widespread conventions for supporting older versions of MediaWiki core:</translate>
+ 
+ <translate><!--T:316--> * Master: the master branch of the extension is compatible with as many old versions of core as possible. This results in a maintenance burden (backwards-compatibility hacks need to be kept around for a long time, and changes to the extension need to be tested with several versions of MediaWiki), but sites running old MediaWiki versions benefit from functionality recently added to the extension.</translate>
+ <translate><!--T:317--> * Release branches: release branches of the extension are compatible with matching branches of core, e.g. sites using MediaWiki 1.27 need to use the REL1_27 branch of the extension. (For extensions hosted on [[gerrit]], these branches are automatically created when new versions of MediaWiki are released.) This results in cleaner code and faster development but users on old core versions do not benefit from bugfixes and new features unless they are backported manually.</translate>
+```
+(That is, break up the flow of translatable text with an untranslatable comment. None of the translation items are changed.)
+
+I've tried a handful of different positions for the translate tag, to no avail.
+
+(FWIW this is in new wikitext editor, not normal VE. I don't imagine it makes any difference.)",1516414669,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort",">>! In T67653#3359087, @jeblad wrote:
+> With WikitextEditor this has become critical for editing translated pages.
+
+Can you give me some more details on what the problem is, and what the steps to reproduce are? ",1497971179,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","With WikitextEditor this has become critical for editing translated pages.
+",1497859187,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to Nemo from comment #5)
+> I guess it can also be put that way. :) Does this new summary reflect the
+> aim?
+
+Not really. Putting a hack into VisualEditor to cope with another extension's model is not good. Either way, I don't care enough. :-)",1415031943,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort",I guess it can also be put that way. :) Does this new summary reflect the aim?,1415031727,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to Nemo from comment #3)
+> (In reply to James Forrester from comment #2)
+> > I don't know. You're the Translate extension expert. :-)
+> 
+> Ok. That error probably just means that some newline was inserted in the
+> wrong place before or after <!--T:1--> and similar, IIRC.
+> 
+> So if you don't have a specific intention here I guess this is one bug of
+> the series ""make VisualEditor not touch Translate stuff which otherwise
+> breaks"" (bug 56451, bug 71730), and is probably blocked on bug 48891 as its
+> friends.
+
+No, this is not a parser bug.
+
+It's just a ""VE should react to stupidly vague error responses by killing stupid comments in stupid places used by a stupid extension to do critical functions that should be done better"" bug. :-)",1415031396,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to James Forrester from comment #2)
+> I don't know. You're the Translate extension expert. :-)
+
+Ok. That error probably just means that some newline was inserted in the wrong place before or after <!--T:1--> and similar, IIRC.
+
+So if you don't have a specific intention here I guess this is one bug of the series ""make VisualEditor not touch Translate stuff which otherwise breaks"" (bug 56451, bug 71730), and is probably blocked on bug 48891 as its friends.",1415031186,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to Nemo from comment #1)
+> (In reply to James Forrester from comment #0)
+> > ""Translation unit markers in unexpected position."" can just go die in Hell.
+> > Gah.
+> 
+> Is this bug related to other bugs?
+
+I don't know. You're the Translate extension expert. :-)",1415030710,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to James Forrester from comment #0)
+> ""Translation unit markers in unexpected position."" can just go die in Hell.
+> Gah.
+
+Is this bug related to other bugs?",1414866147,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"Sometimes editing a page in VisualEditor is rearranging categories so that they always end up on a single line, which is inconvenient for people looking at the wikitext source later.
+
+See https://fr.wikipedia.org/w/index.php?title=Jean-Baptiste_Vallière&diff=prev&oldid=104017086
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400782560,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6bfwstz2ygurnkr45nkj,task_description,open
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"Other example that also displays other problems (extra characters at the beginning, and strange characters in the text ☃☃)
+https://fr.wikipedia.org/w/index.php?title=Absolom_2022&diff=104059827&oldid=96660949",1400919158,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-6bfwstz2ygurnkr45nkj,task_subcomment,NA
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"Other example
+https://fr.wikipedia.org/w/index.php?title=Mines_de_Ranci%C3%A9&diff=104031209&oldid=97118583",1400821311,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-6bfwstz2ygurnkr45nkj,task_subcomment,NA
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"We only use the default newline spacing if the categories are actually new content. So if VE is just removing the newlines, but leaves the categories, a result as in the link is to be expected.
+
+Round-tripping works fine with selser:
+
+http://parsoid-lb.eqiad.wikimedia.org/_rtselser/frwiki/Jean-Baptiste_Valli%C3%A8re?oldid=95815820
+
+Even without selser the newlines are preserved:
+
+http://parsoid-lb.eqiad.wikimedia.org/_rt/frwiki/Jean-Baptiste_Valli%C3%A8re?oldid=95815820
+
+This makes it very likely that this is in fact VE removing newlines.",1400782936,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-6bfwstz2ygurnkr45nkj,task_subcomment,NA
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"Parsoid bug? We hopefully aren't dirtying these, but even if we are, Parsoid's default whitespace should insert a \n before each of these anyway…",1400782652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6bfwstz2ygurnkr45nkj,task_subcomment,NA
+VisualEditor:  Span tags for Language tool only mark part of the page,"Intention:
+Mark almost an entire page with language (en) and direction (LTR).
+
+Steps to Reproduce:
+1.  Open the page and select almost all of the content.
+ 
+2.  Insert > Language
+
+3.  Set the language to English and the direction to LTR.
+
+Actual Results:  
+Only a small fraction of the page was marked with span tags.  See https://office.wikimedia.org/w/index.php?diff=112247&oldid=112246
+
+Expected Results:  
+I wanted this:
+
+<span lang=""en"" dir=""ltr"">
+Div box 
+Image
+Text
+Image
+Some text
+End of div box
+Lots and lots and lots of text
+</span>
+
+I got this:
+
+Div box 
+Image
+<span lang=""en"" dir=""ltr"">Text</span>
+Image
+<span lang=""en"" dir=""ltr"">Text</span>Some te</span>xt
+End of div box
+Lots and lots and lots of text
+
+
+Reproducible: Always
+
+This was exactly repeatable on this page:  the last span tag always ended in the middle of the same word.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://office.wikimedia.org/w/index.php?diff=112247&oldid=112246",1400781180,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-edh3xjjr7fz32wcyfzho,task_description,open
+VisualEditor:  Span tags for Language tool only mark part of the page,"(In reply to WhatamIdoing from comment #2)
+> When I've selected the whole page, I'd rather have the whole page marked
+> with a single pair of tags, even if defining the block content as having a
+> ""language"" is meaningless.
+
+Tough. That's not how HTML works. :-)",1402341119,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-edh3xjjr7fz32wcyfzho,task_subcomment,NA
+VisualEditor:  Span tags for Language tool only mark part of the page,"When I've selected the whole page, I'd rather have the whole page marked with a single pair of tags, even if defining the block content as having a ""language"" is meaningless.",1402341063,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-edh3xjjr7fz32wcyfzho,task_subcomment,NA
+VisualEditor:  Span tags for Language tool only mark part of the page,"The language tool only covers text, not block content, so that's expected.
+
+The not-getting-to-the-end-of-the-selection thing sounds like an odd data model bug.",1402328768,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-edh3xjjr7fz32wcyfzho,task_subcomment,NA
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"When you create a redirect with wikitext, it adds redirect=no.
+
+However, VisualEditor does not (just venotify=created), so you end up going to the target.  Besides being inconsistent, that means it's one extra step to check WhatLinksHere, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65926",1400742720,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_description,resolved
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"Change 138631 merged by jenkins-bot:
+Add redirect=no to new URL when creating a new page as a redirect
+
+https://gerrit.wikimedia.org/r/138631",1402422774,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_subcomment,NA
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"Change 138631 had a related patch set uploaded by Alex Monk:
+Add redirect=no to new URL when creating a new page as a redirect
+
+https://gerrit.wikimedia.org/r/138631",1402419495,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_subcomment,NA
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"Seems to only break if you're creating a new page as a redirect. If you're replacing an existing one with a redirect, it's fine (With the exception of the 'Redirect page' text which it should be adding to #contentSub).",1401118743,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_subcomment,NA
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"Ick. We shouldn't actually be refreshing the page to the extent that a redirect is triggered, however; did we change this?",1400776422,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"Intention:
+Copy a reference's contents (not including ref tags).
+
+Steps to Reproduce:
+1. Open a page in Safari.  Add a citation using the Cite tool.
+
+2. Open the new reference in the Reference dialog via Insert > Reference.
+
+3. Select the contents, and press Command-X to cut it.
+
+Actual Results:  
+Nothing happens.  The template is not cut.
+
+Expected Results:  
+It should be possible to copy and paste citation templates, so that you can modify them for other citations or display them on the page outside of <ref> tags.  
+
+Reproducible: Always
+
+This bug cannot be reproduced in Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400688180,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gxjcazoxkhshpy57yk43,task_description,resolved
+VisualEditor:  Can't cut or copy citation template in Reference dialog,Can't reproduce. Given the age of the task I'll assume it's fixed. Please re-open otherwise.,1701963637,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"See attached screenshot.  On the screenshot you can see that the citation template is selected and that Edit > Cut is grayed out.  
+
+Selecting the template and pressing Command-X does nothing, no matter how many times I press it.  The cite journal template remains stubbornly in place, despite trying to cut the entire contents repeatedly.  If my problem were with pasting, then I'd have an empty box and be complaining that I'd lost work.  Instead, I have a full box and I'm complaining that it is not possible to CUT the contents out of this ref (in Safari 6.1.2, at least).",1415075849,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"Created attachment 17008
+Screenshot showing grayed-out ""Cut"" item in Edit menu
+
+**Attached**: {F13603}",1415075520,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"It's possible to cut/copy things from references, but you can't then paste them back into VE once you shut the dialog – this is bug 51725.
+
+*** This bug has been marked as a duplicate of bug 51725 ***",1415063196,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"Now I can reproduce this in Firefox:
+
+
+1.  Open [[Railway company]].
+
+2.  Discover that the allegedly reliable source is a wikilink to another article.
+
+3.  Open ref dialog.
+
+4.  Select entire contents (one link).
+
+5.  Be confused about why nothing appears to happen.
+
+
+I can copy the link, and I can replace it with garbage, but I cannot make it be empty.  Perhaps this is intentional?  In which case, how can I first remove the unwanted contents, and then add in good contents?",1413500353,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,"It's possible to have a category bubble in the category editor for a category that doesn't have a description page. It would be useful to see that it doesn't exist.
+
+In the source editor this can be achieved while editing by doing a preview and seeing that the link at the bottom is red, so this is a bit of a regression.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49044",1400565480,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-cq5fibwchbc6tbp3nqih,task_description,resolved
+VisualEditor: Categories without description pages don't show as red,Verified the fix in production,1416446905,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,Verified the fix in Betalabs.,1415663361,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,"Change 171464 merged by jenkins-bot:
+Show category items as red if they don't have description pages
+
+https://gerrit.wikimedia.org/r/171464",1415542234,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,"Change 171464 had a related patch set uploaded by Alex Monk:
+Show category items as red if they don't have description pages
+
+https://gerrit.wikimedia.org/r/171464",1415227697,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,*** Bug 69507 has been marked as a duplicate of this bug. ***,1414805875,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"Right now, the way that the save button is disabled when you click it is that MWSaveDialog listens to the button's click event, in response to that it fires the 'save' event, ArticleTarget gets that event, reaches into the save dialog and disables the button.
+
+This is only one of many insane things about the totally dysfunctional MWSaveDialog - ArticleTarget relationship; the whole way these two interact should be refactored.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400545500,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qj4gnvod7alfvonyqkys,task_description,open
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"Change 140868 abandoned by Alex Monk:
+Move some stuff from ViewPageTarget to MWSaveDialog
+
+https://gerrit.wikimedia.org/r/140868",1415057440,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"Change 140868 had a related patch set uploaded by Alex Monk:
+Move some stuff from ViewPageTarget to MWSaveDialog
+
+https://gerrit.wikimedia.org/r/140868",1403220877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"Yeah, that patch wasn't really intended to fully fix this.",1403127812,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,Mostly fixed in gerrit 135945 but Roan said there are still some outstanding issues.,1403127411,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"This'd be lovely to get fixed properly. Alex, could you take a look at this at some point? I imagine Roan'd love to be involved in the refactor, though. :-)",1400545702,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Instrument all actions in visual editing toolbar for organization and frequency of use analysis and improvements,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64711",1400535300,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-czjybdfyzr6v25qeuy65,task_description,open
+VisualEditor: Template editor is missing accessibility features,"ve-ui-mwParameterPage-actions have tabindex=-1, which makes them unreachable by keyboard, the same for the ""Add parameter"" button.
+
+
+The text area of the fields is missing the 'required' attribute for fields that are required.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65473
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62337",1400491140,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-42m5jdfxp7jxtni7uvzn,task_description,resolved
+VisualEditor: Template editor is missing accessibility features,*** Bug 63014 has been marked as a duplicate of this bug. ***,1402553868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-42m5jdfxp7jxtni7uvzn,task_subcomment,NA
+VisualEditor: Template editor is missing accessibility features,"Change 137152 merged by jenkins-bot:
+Add tabindexes to template editor and required attribute where appropriate
+
+https://gerrit.wikimedia.org/r/137152",1401924503,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-42m5jdfxp7jxtni7uvzn,task_subcomment,NA
+VisualEditor: Template editor is missing accessibility features,"Change 137152 had a related patch set uploaded by Alex Monk:
+Add tabindexes to template editor and required attribute where appropriate
+
+https://gerrit.wikimedia.org/r/137152",1401826147,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-42m5jdfxp7jxtni7uvzn,task_subcomment,NA
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","When I access
+https://pt.wikipedia.org/w/index.php?title=Usuário(a):Helder.wiki/Testes&oldid=38949256&veaction=edit&debug=1
+with an empty cache on Firefox 29, it takes at 5+ seconds until I see any progress bar. Sometimes this makes me click in the edit link again because it seems not to be loading at all...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400418840,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-6mc64lhux5u37tjrwhgt,task_description,resolved
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","Change 167736 merged by jenkins-bot:
+Make spinner appear immediately when clicking edit
+
+https://gerrit.wikimedia.org/r/167736",1413928437,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6mc64lhux5u37tjrwhgt,task_subcomment,NA
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","Change 167736 had a related patch set uploaded by SuchetaG:
+Fixing the delay in the spinner to appear and the change in the URL on clicking edit
+
+https://gerrit.wikimedia.org/r/167736",1413865046,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6mc64lhux5u37tjrwhgt,task_subcomment,NA
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","**sucheta.ghoshal** wrote:
+
+The change in the URL with veaction=edit happens late, too. Spinner appears at about the same time as that change happnes.",1413823458,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6mc64lhux5u37tjrwhgt,task_subcomment,NA
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","There are a few issues with how things are initialized. The delay until the loading animation appears is only a symptom of a larger problem: there are multiple requests being made, blocked on each other, that should really be combined.",1402595315,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6mc64lhux5u37tjrwhgt,task_subcomment,NA
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE which has some content in it
+2.Delete all the content
+3.Click on the Link inspector icon from the toolbar
+
+Observed Result:
+
+User gets stuck at this point , cannot close the link inspector dialog anymore by tapping on ""<"" or trash icon
+
+Test Environment: https://en.m.wikipedia.org/
+Device: iPad Mini
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13828}",1400275140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_description,resolved
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,Verified the fix in production,1405024014,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_subcomment,NA
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,Verified the fix in test2,1404775097,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_subcomment,NA
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,"Yes, not getting this issue in Betalabs.Marking it as Fixed.",1404167469,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_subcomment,NA
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,Can this be re-checked? May have been fixed.,1404166413,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Reproducible: Didn't try
+
+Tables like the ones seen at https://en.wikipedia.org/w/index.php?oldid=608813235#Early_years don't display with the correct row height when editing, because VisualEditor assumes that table cells' paragraphs should be styled like other paragraphs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1400272920,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-v3zkwy3tg4leghjf72lu,task_description,resolved
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Change 141923 merged by jenkins-bot:
+Add missing TableCell CSS file and Vector-specific rule
+
+https://gerrit.wikimedia.org/r/141923",1403720050,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Change 141923 had a related patch set uploaded by Esanders:
+Add missing TableCell CSS file and Vector-specific rule
+
+https://gerrit.wikimedia.org/r/141923",1403692740,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be",We should probably do a follow-up tech debt bug about margins for non-paragraphs in table cells…,1402945010,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Change 139676 merged by jenkins-bot:
+Remove margins from paragraphs inside table cells
+
+https://gerrit.wikimedia.org/r/139676",1402944760,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Change 139676 had a related patch set uploaded by Esanders:
+Remove margins from paragraphs inside table cells
+
+https://gerrit.wikimedia.org/r/139676",1402833547,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be",https://gerrit.wikimedia.org/r/#/c/139676/,1402832802,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+VisualEditor Mobile: VE is not appearing as an option to edit even if Beta-Experimental mode is on in iPhone 4S,"Screenshot
+
+I am not getting the VisualEditor for mobile even after enabling it through Beta-Experimental mode while trying to edit this page:https://en.m.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox
+
+see the screenshot attached:
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13822}",1400272860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-s4ok5yjksrgckoh7pb4g,task_description,invalid
+VisualEditor Mobile: VE is not appearing as an option to edit even if Beta-Experimental mode is on in iPhone 4S,Intentional behaviour.,1401417974,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s4ok5yjksrgckoh7pb4g,task_subcomment,NA
+VisualEditor Mobile: VE is not appearing as an option to edit even if Beta-Experimental mode is on in iPhone 4S,VisualEditor is only loaded when you are on a screen with a resolution of 768px width / height. Thus this will currently not work on iPhone 4S as it is not a tablet...,1400522739,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-s4ok5yjksrgckoh7pb4g,task_subcomment,NA
+VisualEditor Mobile: The tapping on Mobile VE is extremely inconsistent compared to standard,"I experienced a huge inconsistency around the precision of tapping action for Mobile VE in all kind of iOS devices I have tried so far.The devices I observed this issue are: iPad 2 with iOS 7.1.1 , iPhone 4S with iOS 7.1.1 and iPad Mini with iOS 7.0.6
+
+Some times , to open the VE and to select a menu options like Settings/Random/Username , it literally takes me to tap twice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400271360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xb4vn67r37nss6carg4t,task_description,resolved
+VisualEditor Mobile: The tapping on Mobile VE is extremely inconsistent compared to standard,"Seems to work for me well enough, now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488548,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xb4vn67r37nss6carg4t,task_subcomment,NA
+VisualEditor Mobile: The tapping on Mobile VE is extremely inconsistent compared to standard,Needs re-testing.,1430336186,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xb4vn67r37nss6carg4t,task_subcomment,NA
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile
+2.Attempt to edit it
+3.While keyboard is still appearing tap on the ""X"" button on the top left of VE or just tap on the browser back button.
+
+Observed Result:
+User is redirected to Readmode but the keyboard is still appearing .
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13816}",1400270460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iiy3kce22e4pguynjf55,task_description,resolved
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487692,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iiy3kce22e4pguynjf55,task_subcomment,NA
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,"Yes, still happens on taping on browser back button",1407868361,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iiy3kce22e4pguynjf55,task_subcomment,NA
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,Is this still an issue?,1406663136,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iiy3kce22e4pguynjf55,task_subcomment,NA
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,Correction: Do not edit the page on step2 just tap on CE to place the cursor and cross the VE out to reproduce.,1400270684,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-iiy3kce22e4pguynjf55,task_subcomment,NA
+VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited,"Something like `http://example.com{{deadlink}}` cannot be properly edited in VisualEditor. It should be processed as two pieces:  one external link that is followed immediately by one template.  Instead, it is presented as the text ""http://example.com[]"", linked to `http://example.com[]`. ",1400180460,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-pxmtpggakccpl77xndne,task_description,open
+VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited,"URLs followed by templates are still broken. However, they now seem to be broken differently: they display as regular links with broken syntax, rather than as alienated nodes.",1437771402,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-pxmtpggakccpl77xndne,task_subcomment,NA
+VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited,"Supposedly the reason for this is that http://example.com{{echo|/index.php}} would produce a link to http://example.com/index.php , rather than a link followed by text. But it depends on what the template outputs; if the output starts with a space or a newline this won't happen. Maybe Parsoid is being a bit too trigger-happy with mw:ExpandedAttrs in the second case?",1400276706,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pxmtpggakccpl77xndne,task_subcomment,NA
+VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited,"Caused by mw:ExpandedAttrs from Parsoid.
+
+Input:
+
+| http://example.com{{deadlink}}
+
+Output:
+
+<a data-mw=""…"" typeof=""mw:ExpandedAttrs"" about=""#mwt2"" rel=""mw:ExtLink"" href=""http://example.com"" data-parsoid=""…"">http://example.com</a>",1400181160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pxmtpggakccpl77xndne,task_subcomment,NA
+VisualEditor: Edit led to a <noinclude> tag being removed (?),"* https://www.mediawiki.org/w/index.php?diff=prev&oldid=1002914
+
+I performed the edit by highlighting the digit '3' with my mouse, and pressing the alphanumerical key '5' on my keyboard; my intention was only to change the date, but VE also removed the <noinclude> tag (I re-added it in a subsequent edit).
+
+Filing this bug after a request from James on IRC.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://www.mediawiki.org/w/index.php?title=MediaWiki_1.24/Roadmap&diff=prev&oldid=1002914",1400179560,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-joglrkxpvi7xbxra2nb4,task_description,declined
+VisualEditor: Edit led to a <noinclude> tag being removed (?),This looks like a temporary Parsoid issue; marking as WORKSFORME as we can't reproduce.,1403220256,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-joglrkxpvi7xbxra2nb4,task_subcomment,NA
+VisualEditor: Edit led to a <noinclude> tag being removed (?),Can't reproduce in Firefox or Chrome.,1402500896,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-joglrkxpvi7xbxra2nb4,task_subcomment,NA
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with Mobile VE which has some content in it
+2.Scroll a bit down 
+3.Tap on any text and then keep on tapping on Return until it deletes the whole line just after the toolbar 
+
+Observed Result:
+After deleting the line just after where the toolbar starts it moves over the toolbar
+
+See the screenshot attached
+
+Test Environment: https://en.m.wikipedia.org/
+Device: iPad Mini
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13595}",1400113740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_description,resolved
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488607,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_subcomment,NA
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,Needs re-testing.,1430336273,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_subcomment,NA
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,Maybe will go away if we use a different method for a sticky header.,1404329851,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_subcomment,NA
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,"This is not an iOS specific issue here, happens in Nexus 7 as well sadly.",1402962955,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_subcomment,NA
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"A more generic way of doing https://gerrit.wikimedia.org/r/133379
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400108520,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-235ze5es2nor6ps5ebbv,task_description,resolved
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"Change 133395 merged by jenkins-bot:
+Hide PageTriage curation toolbar when VE activates
+
+https://gerrit.wikimedia.org/r/133395",1400110422,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-235ze5es2nor6ps5ebbv,task_subcomment,NA
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"Change 133394 merged by jenkins-bot:
+Fire hook when VE activates/deactivates
+
+https://gerrit.wikimedia.org/r/133394",1400110176,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-235ze5es2nor6ps5ebbv,task_subcomment,NA
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"Change 133395 had a related patch set uploaded by Alex Monk:
+Hide PageTriage curation toolbar when VE activates
+
+https://gerrit.wikimedia.org/r/133395",1400110131,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-235ze5es2nor6ps5ebbv,task_subcomment,NA
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"Change 133394 had a related patch set uploaded by Alex Monk:
+Fire hook when VE activates/deactivates
+
+https://gerrit.wikimedia.org/r/133394",1400110055,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-235ze5es2nor6ps5ebbv,task_subcomment,NA
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make some edit
+3.Click on Save Page on the Save page dialog
+4.While loading bar is in progress click on ""Review your changes""
+
+
+Observed Result:
+It opens up the Review section while the loading bar is still showing up above and below the dialog.
+
+Environment:Betalabs,test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13552}",1400099820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_description,resolved
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy","Change 171474 merged by jenkins-bot:
+Disable review button while save dialog is pending
+
+https://gerrit.wikimedia.org/r/171474",1415234119,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_subcomment,NA
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy","Change 171474 had a related patch set uploaded by Alex Monk:
+Disable review button while save dialog is pending
+
+https://gerrit.wikimedia.org/r/171474",1415230477,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_subcomment,NA
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy",It doesn't do anything while the dialog is pending now. Should we be marking it as disabled though?,1408842605,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_subcomment,NA
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy",*** Bug 65485 has been marked as a duplicate of this bug. ***,1400507426,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_subcomment,NA
+Vector: Menu items that are hidden should not be made visible by collapsibleTabs,"Add an item to the tab area with class ""collapsible"" and display none applied.
+
+Then make the window narrow (so it moves into the vector menu), and expand again (so it becomes a tab again).
+
+The item is now visible when it was previously hidden.
+
+vector.collapsibleTabs.js should not override this state.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400088600,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-c4o3u3guy4bzz3drfvag,task_description,declined
+Vector: Menu items that are hidden should not be made visible by collapsibleTabs,"I'm not sure that this is the right call, but I also don't really care. :-)",1400541756,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c4o3u3guy4bzz3drfvag,task_subcomment,NA
+Vector: Menu items that are hidden should not be made visible by collapsibleTabs,"Bug 65292 was fixed in a different way, so let's close this.",1400527665,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-c4o3u3guy4bzz3drfvag,task_subcomment,NA
+Vector: Menu items that are hidden should not be made visible by collapsibleTabs,"I am tempted to WONTFIX this. This bug is actually a proposed way of solving bug 65292 in VisualEditor and not a real bug in core. If a tab is supposed to be treated as not being there, then it just should be removed from the DOM (and bug 65292 has a pending patch that does this).",1400346722,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-c4o3u3guy4bzz3drfvag,task_subcomment,NA
+"VisualEditor: When editor is unavailable, edit menu item can re-appear","Steps to Reproduce:
+1.  Open a Wikipedia article in the article namespace. 
+
+2.  Resize the window to a very small size so that the buttons overlap to the next line. 
+
+3.  Resize the window to the original size and see that the ""Edit beta"" button shows up, which was previously not there.
+
+4.  Click on the new button to open VisualEditor.
+
+Actual Results:  
+Clicking the button produces an error message:
+
+Error loading data from server: novenamespace: VisualEditor is not enabled in namespace 4. Would you like to retry?
+
+Clicking OK closes this dialog, but immediately pops up another one of the same kind. 
+
+Expected Results:  
+That the button wouldn't ever be visible, and that if it were, that it wouldn't give an error message about namespace 4.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400086320,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-iplno7nvlo3lydwjjepq,task_description,resolved
+"VisualEditor: When editor is unavailable, edit menu item can re-appear","Change 133851 merged by jenkins-bot:
+Remove edit tab from the DOM if it's hidden
+
+https://gerrit.wikimedia.org/r/133851",1400521875,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iplno7nvlo3lydwjjepq,task_subcomment,NA
+"VisualEditor: When editor is unavailable, edit menu item can re-appear","Change 133851 had a related patch set uploaded by Alex Monk:
+Remove edit tab from the DOM if it's hidden
+
+https://gerrit.wikimedia.org/r/133851",1400284010,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iplno7nvlo3lydwjjepq,task_subcomment,NA
+"VisualEditor: When editor is unavailable, edit menu item can re-appear","Rephrasing bug title as bug is broader in scope.
+
+The window resize bug is actually caused by a logic error in Vector in MediaWiki core (filed as bug 65294).
+
+So it affects all browsers, and can bypass any soft restriction that we evaluate in javascript (browser support, namespace, content model, user preference etc.).
+
+Because it's basically just always made to be visible regardless of why it was hidden, when doing the resize handle trick from minimum width back out.",1400088777,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-iplno7nvlo3lydwjjepq,task_subcomment,NA
+"VisualEditor:  Using ""page down"" (PgDn) key to scroll down moves the wrong number of lines if the toolbar is on multiple lines","Steps to Reproduce:
+1. Open a long page in VisualEditor.  Press Ctrl-+ several times, until the toolbar is too wide to fit on a single line.
+
+2. Press PgDn (the page down key).
+
+
+
+Actual Results:  
+The wrong number of lines is moved, so that a couple of lines is never seen.
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399935060,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-7kyxrtyxcyoydu6uyyz6,task_description,open
+"VisualEditor:  Using ""page down"" (PgDn) key to scroll down moves the wrong number of lines if the toolbar is on multiple lines","One more thing ... I just hit Ctrl-+ a second time (my eyes are tired) and ... holy crap, the menu bar takes 3 lines, almost half the screen.
+
+Dan",1400025083,PHID-USER-k5yjhsqwhpwazgdemb6v,PHID-TASK-7kyxrtyxcyoydu6uyyz6,task_subcomment,NA
+"VisualEditor:  Using ""page down"" (PgDn) key to scroll down moves the wrong number of lines if the toolbar is on multiple lines","Please see https://en.wikipedia.org/wiki/File:Screenshot1_of_Lamb_article_in_VE,_monobook,_Firefox.png (Windows 7, Firefox 28.0), and after I hit ""Pgdn"" once, https://en.wikipedia.org/wiki/File:Screenshot2_of_Lamb_article_in_VE,_monobook,_Firefox.png. Note that the 2-line VE toolbar takes up enough space that 3 lines from [[Lamb]] are missing between the 2 screens, which makes ""Pgdn"" (and anything else that does the same thing) useless for reading the whole article. Also, the VE toolbar appears to be a lot bigger than it needs to be, both because it takes up 2 lines (if the user has clicked Ctrl-+ at least once, and many do), and because the icons and letters are much larger than they need to be (that is, much larger than the text font).
+
+I'm suggesting that this bug is particularly important because this will be your target viewer's first impression ... in the first few seconds they're exposed to VE, they'll be seeing a much smaller window to edit in (the WP menus including the 2-line VE toolbar take up a quarter of the vertical space), and that paging down is useless for reading the article. Some people make snap judgments based on first impressions.
+
+Dan",1399947739,PHID-USER-k5yjhsqwhpwazgdemb6v,PHID-TASK-7kyxrtyxcyoydu6uyyz6,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","https://en.wikipedia.org/wiki/MediaWiki:Visualeditor-cite-tool-definition.json says:
+
+   { ""name"": ""news"", ""icon"": ""ref-cite-news"", ""template"": ""Cite news"" },
+
+
+Shouldn't the ""name"" part determine the name that's showing in the list?
+
+The actual tool says ""newspaper"" instead of ""news"".  I want it to say ""news"" (because the news might come out of a news-magazine or a news-TV show or a news-website, not just a news-paper).
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1399852860,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-a3rrdosrq4m3cjifkopd,task_description,resolved
+"VisualEditor: Change ""newspaper"" to ""news""","Change 133841 merged by jenkins-bot:
+Change Cite > Newspaper to Cite > News
+
+https://gerrit.wikimedia.org/r/133841",1400279196,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","Change 133839 abandoned by Catrope:
+Change label for news citation tool from ""Newspaper"" to ""News""
+
+Reason:
+Abandoning in favor of https://gerrit.wikimedia.org/r/#/c/133841/
+
+https://gerrit.wikimedia.org/r/133839",1400279060,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","Change 133841 had a related patch set uploaded by Catrope:
+Change Cite > Newspaper to Cite > News
+
+https://gerrit.wikimedia.org/r/133841",1400278559,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","(In reply to Gerrit Notification Bot from comment #2)
+> Change 133839 had a related patch set uploaded by Catrope:
+> Change label for news citation tool from ""Newspaper"" to ""News""
+> 
+> https://gerrit.wikimedia.org/r/133839
+
+All done, just pending a yay/nay from James (since I don't wanna go around changing messages without talking to anyone).
+
+Also, sorry for the long turnaround on this, most of the team was at the hackathon in Zürich last weekend and some people took some vacation time around that as well.",1400275905,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","Change 133839 had a related patch set uploaded by Catrope:
+Change label for news citation tool from ""Newspaper"" to ""News""
+
+https://gerrit.wikimedia.org/r/133839",1400275684,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","(In reply to WhatamIdoing from comment #0)
+> https://en.wikipedia.org/wiki/MediaWiki:Visualeditor-cite-tool-definition.
+> json says:
+> 
+>    { ""name"": ""news"", ""icon"": ""ref-cite-news"", ""template"": ""Cite news"" },
+> 
+> 
+> Shouldn't the ""name"" part determine the name that's showing in the list?
+> 
+Not exactly, but close. It means that the name is taken from [[MediaWiki:Visualeditor-cite-tool-name-news]]. The default translation of that message in English is ""Newspaper"", but we could change that to say ""News"" in the software. You could also edit the MediaWiki: page locally but I'd recommend changing it in the software instead to prevent enwiki diverging from the rest of the universe.",1400275603,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),"Just don't.
+
+* https://pl.wikipedia.org/w/index.php?diff=39429954&oldid=38515622
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1399826160,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-kawtquvxo6egab2fazwx,task_description,resolved
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),"Maybe this was invalid. There is a ""Sort this page by default as"" option in the Categories section of the settings dialog, so now it's pretty obvious how one can change or remove that option, but I don't know when this was introduced.",1457516717,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kawtquvxo6egab2fazwx,task_subcomment,NA
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),Can't reproduce this bug anymore.,1457475200,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kawtquvxo6egab2fazwx,task_subcomment,NA
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),"(To clarify, obviously categories can be removed from an article anytime, but from the diffs it looks like the user has selected and deleted a huge part of text at the bottom of the article, and it doesn't seem that he was there to vandalize it - hence, could be a bug.)",1404662107,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kawtquvxo6egab2fazwx,task_subcomment,NA
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),"Here https://fr.wikipedia.org/w/index.php?title=Henri_D%C3%A8s&diff=105153393&oldid=104979477 and here https://fr.wikipedia.org/w/index.php?title=Henri_D%C3%A8s&diff=next&oldid=105153476 the categories are gone as well. (Wasn't that impossible to do, as per bug 61858?)",1404399512,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-kawtquvxo6egab2fazwx,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,"e.g. in wiktionary semantic classes such as ""distinct feature,"" ""usage example,"" ""syllables,"" ""pronunciation,"" etc.
+
+These would likely be more important for this community than the default preformatted styles used on wikipedia.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399769820,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-uccadm75mlxcgmk4xnec,task_description,open
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,"I'd say that this //may// be wiki-specific, but it should also be possible to make it global.
+
+For now, we don't have global tools, but we should have them (T121470). For tools that are global, this definition should be as global and unified as possible.",1574890274,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,formatting bar,1399816915,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,"To confirm, is this is asking for a tool to wrap selections in templates?",1399814928,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,"It would be good if the addition of the new text styles was as simple as eg. adding of new gadget definitions (instead of having to code long javascript code to add new items in the list)
+
+example:
+
+* usage example | <span class=""usageexample"">{{{1|usage example}}}</span>
+* definition | <dfn class=""definition"">{{{1|definition}}}</dfn>
+
+etc.",1399770721,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,This would likely be a site admin task to add the site specific styles.,1399770008,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"Please enable VisualEditor as a Beta Feature on Wikimedia Commons, not enabled by default.
+
+Beta features are (as far as I know) completely harmless so I do not think a community discussion is necessary but I would be happy to start one if necessary.
+
+I will post a heads-up on this on Wikimedia Commons village pump.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399639800,PHID-USER-m7etbwqrv6cfrg5ymrwx,PHID-TASK-eyop3dml22vuj2xt5thb,task_description,resolved
+Enable VisualEditor as Beta Feature on Wikimedia Commons,Now live.,1400137590,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"Change 132409 merged by jenkins-bot:
+Enable VisualEditor as a Beta Feature on Commons
+
+https://gerrit.wikimedia.org/r/132409",1400109598,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"(In reply to Jean-Fred from comment #2)
+> James told me that by default VE will be active for File, Category, User and
+> main (gallery) namespaces.
+> 
+> Please enable it for Creator: and Institution: too, as pages in these NS use
+> one template, respectively {{Creator}} & {{Institution}}. With TemplateData
+> on them it will be very convenient to use VE to edit them.
+
+Prepared.",1399758277,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"James told me that by default VE will be active for File, Category, User and main (gallery) namespaces.
+
+Please enable it for Creator: and Institution: too, as pages in these NS use one template, respectively {{Creator}} & {{Institution}}. With TemplateData on them it will be very convenient to use VE to edit them.",1399756704,PHID-USER-m7etbwqrv6cfrg5ymrwx,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"Change 132409 had a related patch set uploaded by Jforrester:
+Enable VisualEditor as a Beta Feature on Commons
+
+https://gerrit.wikimedia.org/r/132409",1399640013,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+VisualEditor: Standalone doesn't have an RTL stylesheet,"Build a grunt task out of https://github.com/trevorparscal/cssjanus ?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399629240,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-epbhwclyvevd6ywuakhx,task_description,resolved
+VisualEditor: Standalone doesn't have an RTL stylesheet,"Change 134802 merged by jenkins-bot:
+Use CSSJanus to generate RTL stylesheets
+
+https://gerrit.wikimedia.org/r/134802",1404322307,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-epbhwclyvevd6ywuakhx,task_subcomment,NA
+VisualEditor: Standalone doesn't have an RTL stylesheet,"Change 134802 had a related patch set uploaded by Esanders:
+Use CSS Janus to generate RTL stylesheets
+
+https://gerrit.wikimedia.org/r/134802",1400756554,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-epbhwclyvevd6ywuakhx,task_subcomment,NA
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"The concept of a block slug from a UX POV is great, but why do we need to keep them out of the DM? It seems to be the source of far too many getOffset hacks, as you can put your cursor somewhere that doesn't have a real offset (model-view inconsistency). We already have a way of marking a paragraph as to-be-ignored-by-the-converter-if-empty ({internal:'empty'}), so let's just put them in the DM, and throw them away at convert time if they're empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399621440,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_description,resolved
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"Change 135131 merged by jenkins-bot:
+Stage slugs
+
+https://gerrit.wikimedia.org/r/135131",1412897855,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_subcomment,NA
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"Change 135131 had a related patch set uploaded by Catrope:
+Stage slugs
+
+https://gerrit.wikimedia.org/r/135131",1406919176,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_subcomment,NA
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"Change 135131 had a related patch set uploaded by Jforrester:
+Stage slugs
+
+https://gerrit.wikimedia.org/r/135131",1406767762,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_subcomment,NA
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"Also if we do this we can force the SurfaceObserver to always move cursor positions to content offsets (except for FocusableNodes) which should prevent bugs like Firefox select-all giving you [0,data.length].",1399622043,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_subcomment,NA
+VisualEditor: Media dialog search box is blank after the first use; should instead be reset to the page name,"page title in media search box
+
+on any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/0.8782466280521993?veaction=edit
+
+on first page load, select some text in the page, and then open Media
+
+* page title may be in Media search box. see screen shot.
+
+close the Media inspector, select text again, open Media inspector
+
+* Media search box is now blank
+
+** Sometimes selected text is in the Media inspector search box instead of page title.  see other screen shot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64655
+
+**Attached**: {F13511}",1399574700,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ycmbmogx7itnsveopvs4,task_description,resolved
+VisualEditor: Media dialog search box is blank after the first use; should instead be reset to the page name,"Re-writing the bug title; this has nothing to do with the selection.
+
+Fixed in gerrit 143749.",1404405491,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ycmbmogx7itnsveopvs4,task_subcomment,NA
+VisualEditor: Media dialog search box is blank after the first use; should instead be reset to the page name,"Created attachment 15319
+sometimes selected text is in Media inspector search box
+
+**Attached**: {F13512}",1399574773,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ycmbmogx7itnsveopvs4,task_subcomment,NA
+VisualEditor: Pasting plain text from external sources inserts spurious double new lines between paragraphs in Safari,"Intention:
+Paste some plain text.
+
+Steps to Reproduce:
+1. Type a few paragraphs of plain text.  I typed mine into an Apple Mail message with rich text turned off.  My text was:
+
+I get to play with lists.
+I like to play with lists.
+
+I wonder if this will do what I want.
+
+What I want is for this not to be in a list.
+
+
+2. Open VisualEditor.
+
+3. Copy and paste the plain text into VisualEditor.
+
+
+Actual Results:  
+Instead of getting this:
+
+I get to play with lists.
+I like to play with lists.
+
+I wonder if this will do what I want.
+
+What I want is for this not to be in a list.
+
+
+I got this:
+
+I get to play with lists.
+I like to play with lists.
+
+
+I wonder if this will do what I want.
+
+
+What I want is for this not to be in a list.
+
+
+When it saved, there were actually three blank lines between the paragraphs.  This can be seen at http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=92715&oldid=92368
+
+
+Reproducible: Always
+
+This is not the same as Bug 58283.  Also, I could not reproduce this in Firefox 29.  It happens every time in Safari 6.1.3.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399495620,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-vtl6oy2eryypamslyqf3,task_description,open
+VisualEditor: Pasting plain text from external sources inserts spurious double new lines between paragraphs in Safari,Confirmed in Safari 8.0.,1414011489,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vtl6oy2eryypamslyqf3,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","As of May 6th, I am experiencing a lag in switching from VE to Edit source mode, after clicking on Ok on ""Switch to source editing"" dialog, for 5-6 secs, it seems like nothing is happening on my browser. 
+
+This is happening even if I have perfect network speed and all other things loading properly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399489320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_description,resolved
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar",Verified the fix in production,1411682277,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar",Verified the fix in test2,1411081841,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar",Verified the fix in Betalabs,1410984389,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","Change 144505 merged by jenkins-bot:
+Show pending state on action button and keep dialog open when switching to source mode
+
+https://gerrit.wikimedia.org/r/144505",1410911064,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","Change 144505 had a related patch set uploaded by Alex Monk:
+Show pending state and block clicks when switching to source mode
+
+https://gerrit.wikimedia.org/r/144505",1404763221,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","Spinner? Hmm... I've been thinking perhaps mark the switch confirmation dialog as pending and just not close it.
+
+As for blocking overlay... Not sure about what the best way to do that is yet. I assume setting pointer-events:none; on the <body> isn't great.",1404588119,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","This is only in beta labs, probably because beta labs is just slow. We should have a spinner and a blocking overlay, though. Right now you can even interact with the surface while we switch to source mode.",1400096282,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+VisualEditor: Vertical cursoring can get cursor stuck on a paragraph-terminal reference in Firefox,"From bug 50726 comment : 
+
+| 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.
+| 3. Press down. (the cursor should now be directly right of of the first reference)
+| 4. 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)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/Jos%C3%A9_Cl%C3%A1udio_Ribeiro_da_Silva?veaction=edit",1399419720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5466yh2wfhphliediki,task_description,resolved
+VisualEditor: Vertical cursoring can get cursor stuck on a paragraph-terminal reference in Firefox,"I don't recall when, but this is long-since fixed.",1493661863,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5466yh2wfhphliediki,task_subcomment,NA
+"VisualEditor: [Regression] ""Middle click"" / Cmd+Click on mac no longer open links' targets in a new tab","open in new tab used to work for links while in VE with CMD+Click on mac, this no longer works
+
+Mac 10.9.2 / Chrome Version 35.0.1916.86 beta
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399414860,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-4cw53y6ozxxq4jifc5pd,task_description,resolved
+"VisualEditor: [Regression] ""Middle click"" / Cmd+Click on mac no longer open links' targets in a new tab","Turns out I was wrong and this did already exist - sorry!
+
+*** This bug has been marked as a duplicate of bug 50321 ***",1402552906,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4cw53y6ozxxq4jifc5pd,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version","**Author:** `richlv`
+
+**Description:**
+mw 1.22.6. enabling latest visual editor from git results in :
+""Fatal exception of type MWException""
+
+after some testing, no specific error messages could be seen in apache error log.
+
+according to James_F, ""VE master needs MW 1.23, yes - but it should also fail gracefully when you try to start it, rather than have random fatal errors"" :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399412280,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wio2msjxwwllpptk2lsk,task_description,declined
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version","Well, we won't do anything about MW 1.22 today.
+
+Generally, VisualEditor will show an appropriate error these days when running on unsupported MediaWiki, since {c0c5a028cf82baf79db1f11b36898bd72945dae0}.",1613562732,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version",,1436994300,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version",,1436994281,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version",This also happens with master and MW 1.23,1402558884,PHID-USER-3x5zfm7iedaghxnnelco,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version","**richlv** wrote:
+
+master",1399413762,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version","(In reply to richlv from comment #0)
+> enabling latest visual editor from git
+
+Which branch?",1399413414,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+VisualEditor:  A straight line appears above the image while making it (Frameless/Basic-Left/Right-border),"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it frameless-left-border or basic-left-border 
+
+Observed Result:
+A straight line appears over the image.If you now move the image to center it will go away, but if you again change it to frameless-right-border or basic-right-border from center, the straight line will appear again
+
+
+See the screenshot attacahed
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13981}",1399403760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6w5hbvxithekehcvu66c,task_description,resolved
+VisualEditor:  A straight line appears above the image while making it (Frameless/Basic-Left/Right-border),"This issue is not happening anymore, might got fixed by some changes with image .
+Marking it as resolved .",1404866921,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6w5hbvxithekehcvu66c,task_subcomment,NA
+VisualEditor:  A straight line appears above the image while making it (Frameless/Basic-Left/Right-border),This issue did not get resolved with new image model,1400202049,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6w5hbvxithekehcvu66c,task_subcomment,NA
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"Right now if you have some rich content with an image and paste it into VisualEditor, we discard the image.
+
+However, it'd be nice to add some special handling in VisualEditor's paste for the HTML of images so that those from Commons used on a MediaWiki instance get sought out and inserted instead.
+
+Perhaps via a special custom attribute VE would sniff for, that would make VE try to find the image from Commons (if the wiki was configured for InstantCommons), or other fileRepos?
+
+MediaViewer's ""embed"" HTML looks like:
+
+| <p><a href=""http://commons.wikimedia.org/wiki/File:Beach_sand.jpg#mediaviewer/File:Beach_sand.jpg""><img src=""http://upload.wikimedia.org/wikipedia/commons/c/c5/Beach_sand.jpg"" alt=""Beach sand.jpg"" height=""1200"" width=""1600""></a>[…]</p>
+
+If we asked them to add an attribute, e.g. (simplified):
+
+| <p><a href=""…""><img src=""…"" alt=""…"" ve-data=""ve-pastableImage"" ></a>[…]</p>
+
+… could we do this?
+
+(Also, yes, they should be using <figure> instead of <p><img></p>.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399337460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_description,open
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"(In reply to Tisza Gergő from comment #3)
+> We tried to avoid using the description where a caption is available; the
+> description is often less relevant and too verbose. Also, the caption might
+> be in the right language - copy-pasting images does not necessarily happen
+> across wikis. (I guess we could add a lang attribute, which is a sensible
+> thing to do anyway, and then language mismatch could be detected on paste.)
+
+Yeah, if the <figcaption> had a lang attribute it'd be a lot easier for us, and we'd use that in preference if it were in the content language of the paste target.",1399481558,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_subcomment,NA
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"We tried to avoid using the description where a caption is available; the description is often less relevant and too verbose. Also, the caption might be in the right language - copy-pasting images does not necessarily happen across wikis. (I guess we could add a lang attribute, which is a sensible thing to do anyway, and then language mismatch could be detected on paste.)",1399450066,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_subcomment,NA
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"(In reply to Tisza Gergő from comment #1)
+> At any rate, whether it is in a figure tag figure or something else, users
+> would probably expect the caption to end up inside the image wikicode, not
+> as a HTML wrapper. So I suppose the caption would need special attributes as
+> well?
+
+Sure, or we could fetch the caption from Commons in the context language automatically, so users don't have to be using the right language?",1399339115,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_subcomment,NA
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"Granted, MediaViewer's HTML format is total crap, but there isn't a clean, semantic way to mark up image captions that works in HTML4. Maybe browsers these days understand HTML5 tags no matter the doctype, and using figure is fine - we should look into that.
+
+At any rate, whether it is in a figure tag figure or something else, users would probably expect the caption to end up inside the image wikicode, not as a HTML wrapper. So I suppose the caption would need special attributes as well?",1399338461,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"mediawiki.Uri does not support IPv6 URIs:
+
+```
+> var uri = new mw.Uri( 'http://127.0.0.1/' )
+undefined
+> var uri = new mw.Uri( 'http://[::1]/' )
+Error: Bad constructor arguments
+```",1399291380,PHID-USER-3dmql6z7s5lnn5lu2vs3,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_description,declined
+mediawiki.Uri does not support IPv6 URIs,"I did T305010 for DiscussionTools mostly as an exercise for myself while learning how to use the `URL` API. But we also had several workarounds for `mw.Uri` bugs, so it seemed like a good thing from a maintenance perspective.
+
+I wasn't planning to make similar changes in VisualEditor, but if you'd also enjoy some exercise ;) , then I'd be happy to review a patch. Generally I don't like making such changes, since they're error-prone, but it's a different thing if it's also fixing a bug (like the editor not loading on IPv6 wikis).",1649283714,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,Thanks for the answer. It’s indeed more safe not to mass-replace since there are different dialects of URLs (I discovered recently [[https://hackerone.com/reports/704621|this not-issue in curl]] and [[https://github.com/bagder/docs/blob/master/URL-interop.md|this document about URL interoperability issues]]).,1649273403,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"@Seb35 Yes and no. The two are not directly compatible, but are similar enough that it's easy for developers to change one to the other in cases where edge cases are known to happen. For example, the VisualEditor team is doing this at T305010.
+
+There are no plans at this time to mass-replace or deprecate mw.Uri. It's a stable module that incurs essentially no maintenance cost for our team to keep providing for a long time as-is. Expect handling of regressions and security issuse, and e.g. any regular maintenance as needed to keep up with external changes (coding practices, browser support etc.). A major shift to support IPv6 with a new internal parser that is yet also backwards-compatible is not currently planned to take place.",1649271885,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"Is there plans to replace `mw.Uri` by `URL`?
+
+I was interested by this task because my test installation is `https://[::1]/mediawiki/master/index.php` (I like edge cases), and the VisualEditor was failing and is still failing since it still uses `mw.Uri`, but more generally there are a lot of users of `mw.Uri`. (no issue for myself, I know how to circumvent this issue by using 127.0.0.1 when needed.)",1649271478,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"Change 759635 **abandoned** by Krinkle:
+%%%[mediawiki/core@master] mediawiki.Uri: Support IPv6 parsing%%%
+Reason:
+%%%Done.%%%
+https://gerrit.wikimedia.org/r/759635",1645032689,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,Declining in favour of T103379.,1645032574,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"Change 759635 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/core@master] Support IPv6 in mw.Uri parsing%%%
+https://gerrit.wikimedia.org/r/759635",1643939933,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"The caller is initDesktop() in Echo, but the underlying problem is T106244.",1602707398,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"The caller is initDesktop() in Echo, but the underlying problem is T265506.",1602707382,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"We don't run with IPv6 URLs in prod, we use hostnames like ""wikipedia.org"".
+
+I'll be a different issue frrom whatever the caller is in that trace, please file a separate task.",1602701569,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"This urfaces as ` TypeError: can't access property ""clone"", defaultUri is undefined` and `Unable to get property 'clone' of undefined or null reference` https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-2020.10.14/clienterror/?id=AXUm60RcLNRtRo5XyfQb",1602699242,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"On a MediaWiki installation with IPv6 URL like
+http://[::1]/w/index.php
+the class mw.Uri gets not created because it is initialized with
+
+mw.Uri = mw.UriRelative( document.location.href );",1399299571,PHID-USER-3dmql6z7s5lnn5lu2vs3,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"Ctrl-Arrow is supposed to move the caret one word in the direction of the arrow.
+
+In RTL wikis it moves too far. It looks like to goes to the next reference or the next sentence rather than the next word.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1399285200,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ebuzshnkdnhhawwjczws,task_description,resolved
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"Change 131767 merged by jenkins-bot:
+unicodejs: Update moveBreakOffset to include 'HebrewLetter' category
+
+https://gerrit.wikimedia.org/r/131767",1399626961,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"Presuming that the rename of this bug is correct, marking this as FIXED.",1399626919,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"Change 131767 had a related patch set uploaded by Esanders:
+Update moveBreakOffset to include 'HebrewLetter' category
+
+https://gerrit.wikimedia.org/r/131767",1399404578,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"This looks like just a problem with Hebrew. The new Unicode spec introduced a ""HebrewLetter"" group which we didn't add to the WordBreak checker.",1399404357,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,On a Mac it's Alt-Arrow a.k.a. Option-Arrow.,1399285418,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Keyboard shortcut dialog lists heading change incorrectly labelled on Mac,"Noticed on our Wikia integration, and saw that it was incorrect here: https://www.mediawiki.org/wiki/VisualEditor?veaction=edit
+
+http://screencast.com/t/sin5AakmN0
+
+The shortcut list shows that Command plus a number changes the heading value. This is incorrect, as it controls the browser's tabs. The correct label should be ""Command"".
+
+I tested this in latest Firefox and latest Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1399069920,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-studawgsnaudqrhmhjyt,task_description,resolved
+VisualEditor: Keyboard shortcut dialog lists heading change incorrectly labelled on Mac,"Change 131596 merged by jenkins-bot:
+Fix command help for CTRL+1-6 on mac
+
+https://gerrit.wikimedia.org/r/131596",1399323217,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-studawgsnaudqrhmhjyt,task_subcomment,NA
+VisualEditor: Keyboard shortcut dialog lists heading change incorrectly labelled on Mac,"Change 131596 had a related patch set uploaded by Esanders:
+Fix command help for CTRL+1-6 on mac
+
+https://gerrit.wikimedia.org/r/131596",1399322977,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-studawgsnaudqrhmhjyt,task_subcomment,NA
+Optimistic saving,"We should adapt the save prediction / optimistic parsing logic in VisualEditor and provide it for the standard wikitext editor. See T58011 for the full description.
+
+Adding Roan as CC since he implemented this for VisualEditor and thus may have useful feedback.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: enhancement",1399063020,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-qnn2vzzsqhnziozjaxbu,task_description,resolved
+Optimistic saving,"Some things to account for:
+
+* Account for use of rev ID parser functions (e.g. don't cache at all)
+* Use of parser timestamp functions lower TTL appropriately (or don't cache in some cases too)
+* Account for user prefs and options fully (they might change before the actual ""save"" click)",1399063632,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-qnn2vzzsqhnziozjaxbu,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Issues right now:
+
+* Different set of elements (e.g. #contentSub is shown in read mode, but not in edit mode. The same goes for TOC, though we do account for that one).
+
+* Different offset (the toolbar is injected which causes an abrupt visual shift).
+
+* Different scroll offset (same as before, but applies when you open the editor when scrolled down the page, after the transition, you're looking at a potentially very different part of the document, we should preserve it or jump to the top, not leave you somewhere randomly).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399049040,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cnqs3vwq6pny7mken344,task_description,resolved
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,Enough now that I'm going to call this done.,1399344356,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Change 131071 merged by jenkins-bot:
+ve.init.mw.ViewPageTarget: Actually animate the toolbar during setup
+
+https://gerrit.wikimedia.org/r/131071",1399344331,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Change 131074 merged by jenkins-bot:
+ve.init.mw.ViewPageTarget: Hide #contentSub in addition to #toc when muted
+
+https://gerrit.wikimedia.org/r/131074",1399053819,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Change 131074 had a related patch set uploaded by Krinkle:
+ve.init.mw.ViewPageTarget: Hide #contentSub in addition to #toc when muted
+
+https://gerrit.wikimedia.org/r/131074",1399049179,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Change 131071 had a related patch set uploaded by Krinkle:
+ve.init.mw.ViewPageTarget: Actually animate the toolbar during setup
+
+https://gerrit.wikimedia.org/r/131071",1399049107,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","In Firefox
+
+Steps to reproduce:
+
+1.Open a page with VE in Firefox
+
+2.Insert a media
+
+3.Go to Media Settings of that image
+
+4.Scroll down the dialog box 
+
+Observed Result:
+
+There is no gap between the textbox for Alternative text and the border of the dialog , its almost overlapped with the border as compared to how it appears in Chrome
+
+See the screenshots attached
+
+Test Environment:
+http://en.wikipedia.beta.wmflabs.org/ and 
+https://en.wikipedia.org/
+
+Browser: FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14031}",1398981780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6imkll3gv77iihieqgvg,task_description,resolved
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog",">>! In T66723#709422, @Catrope wrote:
+> The Firefox people disagree that this is a bug: https://bugzilla.mozilla.org/show_bug.cgi?id=748518
+
+It seems they changed their mind a couple years ago, as this bug is now marked as resolved.
+
+I can't reproduce our bug, so maybe it's fixed as a result of that (or maybe something else changed).",1697485607,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","(In reply to Roan Kattouw from comment #2)
+> The PageLayout has 1.5em of padding on all sides. In Chrome, the bottom
+> padding is taken into account in the overflow (i.e. in determining whether
+> to draw a scrollbar and how far down to allow scrolling) while in Firefox it
+> is now. Using bottom margin rather than padding does appear to sort of work
+> in Firefox, but it makes the vertical scroll bar end too early (as it
+> correctly ends before the margin).
+
+The Firefox people disagree that this is a bug: https://bugzilla.mozilla.org/show_bug.cgi?id=748518",1400095736,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","The same issue appears to be in the Reference dialog box as well ,the ""Use this group"" textbox overlaps with the border of the dialog in Firefox",1399926311,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","The PageLayout has 1.5em of padding on all sides. In Chrome, the bottom padding is taken into account in the overflow (i.e. in determining whether to draw a scrollbar and how far down to allow scrolling) while in Firefox it is now. Using bottom margin rather than padding does appear to sort of work in Firefox, but it makes the vertical scroll bar end too early (as it correctly ends before the margin).",1399332578,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","The PageLayout has 1.5em of padding on all sides. In Chrome, the bottom padding is taken into account in the overflow (i.e. in determining whether to draw a scrollbar and how far down to allow scrolling) while in Firefox it is now. Using bottom margin rather than padding does appear to sort of work in Firefox, but it makes the vertical scroll bar end too early (as it correctly ends before the margin).",1399332503,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+VisualEditor: Citation tool should not add empty citation templates,"Steps to Reproduce:
+1. Citation > Cite web
+
+2. Don't add any information.  Just click ""Apply changes"".
+
+Result:  <ref>{{Cite web|url = |title = |date = |accessdate = |website = }}</ref>
+
+That's pointless.  If the fields are blank, don't add it (or remove it).
+
+
+Steps to reproduce, part 2:
+
+1. Citation > Cite web
+
+2. Don't add any information.  Delete all the parameters. 
+
+3. Click ""Apply changes"".
+
+Result:  <ref>{{Cite web}}</ref>
+
+That's even more pointless.  If there are no parameters, don't add it (or remove it).
+
+
+
+
+
+Reproducible: Didn't try
+
+(The ""invalid"" parameter in that diff was manually created by me.  I don't think you can do anything to help the person adding invalid parameters, because there's no way to differentiate between invalid parameter names and valid names that don't happen to be defined in TemplateData.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=91690&oldid=91686",1398976860,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-sfyrbpff7z277arpuv5d,task_description,resolved
+VisualEditor: Citation tool should not add empty citation templates,"Whoops, sorry, wrong bug report :(",1401993942,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-sfyrbpff7z277arpuv5d,task_subcomment,NA
+VisualEditor: Citation tool should not add empty citation templates,"Created attachment 15573
+More than one field error
+
+**Attached**: {F14012}",1401993896,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-sfyrbpff7z277arpuv5d,task_subcomment,NA
+VisualEditor: Citation tool should not add empty citation templates,"Change 136436 merged by jenkins-bot:
+Don't allow inserting blank citations
+
+https://gerrit.wikimedia.org/r/136436",1401922649,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sfyrbpff7z277arpuv5d,task_subcomment,NA
+VisualEditor: Citation tool should not add empty citation templates,"Change 136436 had a related patch set uploaded by Alex Monk:
+Don't allow inserting blank citations
+
+https://gerrit.wikimedia.org/r/136436",1401478661,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sfyrbpff7z277arpuv5d,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","Intention:
+Edit an existing citation.
+
+Steps to Reproduce:
+1.  Select an existing citation (one using a citation template).
+2.  Press the return key to open it.
+3.  That's odd, I'm in the Reference dialog.  Exit.  
+4.  Re-select the citation.  
+5.  Double-click to open it.  
+6.  That's odd, I'm in the Reference dialog.  Exit.  
+7.  Re-select the citation.  
+8.  Click the little cite-web icon.  That opens the citation tool's simplified dialog.
+
+This happens in both Safari and Firefox, so presumably everywhere. ",1398975240,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_description,resolved
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead",This was fixed some time in the past 3.5 years.,1531409201,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","@jdforrester-WMF If that sounds reasonable to you, I'd like to see this resolved as part of the citations experience work that we're doing in Q3 - it's a UI niggle that can distract from an otherwise dramatically improved experience. Obviously not an issue if made obsolete by a new UI.",1421390457,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","(In reply to Erik Moeller from comment #3)
+> As the citation experience overall has recently improved in leaps and bounds
+> this is one of those issues that sticks out -- any chance we can chop it
+> down soon?
+It's a non-trivial problem. We have some ideas for how to do this, but I need Trevor's brain, and he's been sick all week :(",1406263756,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead",As the citation experience overall has recently improved in leaps and bounds this is one of those issues that sticks out -- any chance we can chop it down soon?,1406263018,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","In talking with Trevor this is going to take quite some time to fix, sadly.
+
+(In reply to WhatamIdoing from comment #1)
+> Once you're inside the Reference dialog, if you double-click the citation
+> template, then it takes you to the Citation tool (rather than to the generic
+> template tool).  I don't know if that's intentional, but it's not obviously
+> wrong.
+
+It's intentional. :-)",1399336402,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","Once you're inside the Reference dialog, if you double-click the citation template, then it takes you to the Citation tool (rather than to the generic template tool).  I don't know if that's intentional, but it's not obviously wrong.",1398978720,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+VisualEditor: Link inspector does not highlight/remove default linked text sometimes in automated testing in Chrome,"first word in page text is still in link box after clicking and typing
+
+seen in Chrome only as of 30 Apr: 
+
+as a logged in user on beta labs, invoke VE on a page containing text
+
+without typing or clicking anything else, click the Link icon
+
+the first word in the page text is in the box to create the link
+
+* problem: the text in the link box is not automatically highlighted
+
+click in the link box to create the link text
+
+* problem: default text in the link box that should be highlighted should also be removed when the user clicks in the box to type their own link
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65038
+
+**Attached**: {F13875}",1398867000,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5juvbbzvkfwawhcrnc5e,task_description,declined
+VisualEditor: Link inspector does not highlight/remove default linked text sometimes in automated testing in Chrome,No consistent repro,1401818677,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-5juvbbzvkfwawhcrnc5e,task_subcomment,NA
+VisualEditor: Link inspector does not highlight/remove default linked text sometimes in automated testing in Chrome,I can't reproduce this in Chrome or Firefox on Beta Labs now – possibly a temporary/cached deployment bug?,1398898514,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5juvbbzvkfwawhcrnc5e,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","In Vector/1.24wmf2, the ""Edit source"" tab is not highlighted when editing a page in source mode (no tab is highlighted).
+
+Example:
+http://www.mediawiki.org/w/index.php?title=Help:Preferences&action=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398829320,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-fsxmbv5x3nocq46ayz64,task_description,resolved
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Verified the fix on Production, Betalabs and Test2",1399410116,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Change 130622 merged by Catrope:
+Preserve pre-existing css classes on edit tab link
+
+https://gerrit.wikimedia.org/r/130622",1398899133,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Change 130622 had a related patch set uploaded by Jforrester:
+Preserve pre-existing css classes on edit tab link
+
+https://gerrit.wikimedia.org/r/130622",1398875579,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Change 130594 merged by jenkins-bot:
+Preserve pre-existing css classes on edit tab link
+
+https://gerrit.wikimedia.org/r/130594",1398875491,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit",*** Bug 64645 has been marked as a duplicate of this bug. ***,1398863834,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","(For the record, yes, confirmed this is broken in production and on latest master).",1398863005,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Change 130594 had a related patch set uploaded by Krinkle:
+Preserve pre-existing css classes on edit tab link.
+
+https://gerrit.wikimedia.org/r/130594",1398862925,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Caused by Ib2e6237483338c8072d5f7919c6459bf7418946a, which overides the 'class' attribute of the original edit tab with 'collapsed'. Thus blowing away the class ""selected"" that MediaWiki core puts there when on action=edit.",1398862419,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: 500 server error from api.php and ""Unknown Error"" appears on the Save dialog box if only a newline is added to the document after a gallery","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Just add a newline by pressing the return
+3.Click on the ""Save Page"" button which got enabled 
+
+Observed Result:
+ ""Unknown Error"" appears on the Save dialog box
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/28thAprilChrome?veaction=edit
+
+**Attached**: {F13652}",1398715020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zxmvdaa5bbdoniada2kf,task_description,resolved
+"VisualEditor: 500 server error from api.php and ""Unknown Error"" appears on the Save dialog box if only a newline is added to the document after a gallery",LGTM. Maybe this was fixed by the changes to the save dialog? Not sure…,1399994453,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zxmvdaa5bbdoniada2kf,task_subcomment,NA
+"VisualEditor: 500 server error from api.php and ""Unknown Error"" appears on the Save dialog box if only a newline is added to the document after a gallery",Am I missing something or has this been fixed? http://en.wikipedia.beta.wmflabs.org/w/index.php?title=28thAprilChrome&diff=94065&oldid=91283,1399991715,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-zxmvdaa5bbdoniada2kf,task_subcomment,NA
+"VisualEditor: 500 server error from api.php and ""Unknown Error"" appears on the Save dialog box if only a newline is added to the document after a gallery","It also shows the following error in the console:
+POST http://en.wikipedia.beta.wmflabs.org/w/api.php 500 (Internal Server Error)",1398715583,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zxmvdaa5bbdoniada2kf,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.In the caption of the image add templates/images/cite notes/math/reference
+4.Click on ""Apply Changes""
+5.Now hover over the image
+
+Observed Result:
+The highlight boxes for templates/images/cite notes/math/references are appearing as well while highlighting the image
+
+See the screenshot attached.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62681
+
+**Attached**: {F13649}",1398710700,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cvfoo26a6vgdda4p5l74,task_description,resolved
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,Verified the fix in production (en.wiki),1403301350,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,Verified the fix in test2 running wmf9,1402694827,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,This seems to be working fine now.There is one single shield appearing over the image even if it has different nodes inside the caption,1402446768,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,"Change 134363 merged by jenkins-bot:
+[BREAKING CHANGE] Merge ProtectedNode into FocusableNode
+
+https://gerrit.wikimedia.org/r/134363",1402442354,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,"Change 134363 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Merge protected node into focusable node
+
+https://gerrit.wikimedia.org/r/134363",1400696169,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,This did not get resolved with the new image model.Giving it to Moriel .,1400198811,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add Heading
+3.Add Subheading 1
+4.Now go to Page Settings and set the option to show the TOC as Always
+
+Observed Result:
+In the TOC inside VE the link to hide the TOC appears as <hidetoc> instead of Hide
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14029}",1398468240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_description,resolved
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""",Verified the fix in production,1400011740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_subcomment,NA
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""",Verified the fix in test2,1399071175,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_subcomment,NA
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""",Verified the fix in Betalabs,1398895706,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_subcomment,NA
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""","Change 129852 merged by jenkins-bot:
+Export showtoc and hidetoc messages
+
+https://gerrit.wikimedia.org/r/129852",1398470511,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"A screenshot indicating where exactly between the VisualEditor toolbar and the content being edited with VisualEditor the 'Insert' menu becomes hidden under such content being edited
+
+As shown in the attached screenshot, attempting to open VisualEditor's 'Insert' menu causes it to open behind the content of the page that you have opened within VisualEditor.  This occurs when VisualEditor is used in Safari 6.1.3 under OS X 10.8.5 'Mountain Lion' when this OS is run on a mid-2007 aluminum iMac with a 2.4-GHz Intel Core 2 Duo processor, 4 GB of 667-MHz DDR2 SDRAM, and an ATI Radeon HD 2600 Pro with 256 MB of dedicated VRAM.  For some reason, though, this bug has been somewhat intermittent over the past month or so (it showed up for a while at first, then appeared as if it had been fixed before whatever patch that fixed it was reverted or otherwise messed with.)  Is my bug a duplicate of another one even though I couldn't find a similar one via Bugzilla's search mechanism?  If so, have there been notices in the comments of this other bug about its status?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh
+
+**Attached**: {F13846}",1398369840,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_description,invalid
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"This issue went away for me shortly before I updated my system to OS X 10.10.x 'Yosemite' and Safari 8.0.x and has not resurfaced since then.  I'm assuming that somebody fixed this by resolving a related issue and am, as such, closing it as 'Invalid' since it no longer describes behavior under the currently used versions of MediaWiki.  ",1427663679,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,@WhatamIdoing:  Methinks that the problem is highly exacerbated by the use of Safari Extensions (see comment 2 for the full list of stuff I had on my computer when this bug first appeared for me.),1412633895,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Assuming that the steps to reproduce are:
+
+1.  Read Wikipedia article in Safari.  Zoom in at least twice (Command-+).
+
+2.  Open page in VisualEditor.
+
+3.  Click on drop-down menus (e.g., the character formatting menu).
+
+then I cannot reproduce this today in Safari 6.2 on Mac OS 10.8.5.",1412627563,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Ah, I see; that *would* be a problem since Apple no longer supplies current versions of Safari to Windows users.  It seems to me, however, that this bug has been fixed for users of Safari 7.1 (9537.85.10.17.1), to which I updated a little while back, by recent changes to either WebKit or the MediaWiki software.  Since I no longer have either Safari 6.1.3 or Safari 7.0.5, could anybody check to see if this bug still exists for those versions of Safari?",1412543272,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,I'd love to help but I don't own a Mac. :(,1412366537,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,Any progress on fixing the zooming issue?,1411834869,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"P. P. S.:  It turns out that VisualEditor's menus load properly if you reset Safari's zoom level before clicking on 'Edit [beta]' even if you then zoom in afterwards!  Crazy, right?",1407786576,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"P. S.:  I just looked at the duplicate bug, number 67741, and I realized that I *always* zoom in by two levels when I use Wikipedia!  I will therefore check to see if VisualEditor works normally when I'm not zoomed in at all before you guys have me do any deeper testing, all right?",1407781848,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to James Forrester from comment #22)
+> (In reply to Bryce Glover from comment #21)
+> > I'm still seeing this bug with Safari 6.1.4, guys; maybe it's more serious
+> > than we all think?  It would be really nice if we could figure out what's
+> > going on here, because it's really annoying for me to not be able to use
+> > VisualEditor since it's such a great product (I can't even access the
+> > 'Switch to Source Editing' command since the menus hide behind page content!)
+> 
+> Hey, sorry, please re-open bugs if you think more work needs to be done on
+> them. This bug was lost to the mists of time (bugs marked RESOLVED/VERIFIED
+> are only looked at by happenstance). :-(
+> 
+> Unfortunately I don't have access to Safari 6.1.x here, and I still can't
+> replicate in Safari 6.0.5 or 7.0.4/5 – and given that only security updates
+> and a sidebar were added, it seems almost certain that the issue is specific
+> to your setup somehow. Re-opening but I'm not sure if there's anything we
+> can do…
+
+Well, I just updated my system to OS X 10.9.4 'Mavericks,' which contains Safari 7.0.5, and the menus *still* refuse to come out from underneath the content of any page that I might be trying to edit with VisualEditor.  (Speaking of this component, why did you change this bug's summary to indicate that it's a bug in OOJs rather than a bug in VisualEditor?  Is VisualEditor partly implemented OOJs, and do you suspect that this part of its implementation may be causing me my problems with VisualEditor?)  So, you may be right that my seeing this bug has something to do with my setup.  Do you want me to disable my Extensions again and empty my caches and then try using VisualEditor again?  How about re-enabling Safari's Extensions framework without enabling any of my installed extensions and then troubleshooting my installed extensions one by one to see which one causes the error?  I'll attach any error messages that pop up in my console when I run that test to this bug if you have me do so.  In addition, should I maybe contact either Apple or the developer of whichever Extension turns out to be the culprit and ask them to help us squash this bug once we figure out what's going on here?  I'd really *love* to solve this problem; it's driving me *nuts* that I can't use VisualEditor properly!",1407781542,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,*** Bug 67741 has been marked as a duplicate of this bug. ***,1404965618,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #21)
+> I'm still seeing this bug with Safari 6.1.4, guys; maybe it's more serious
+> than we all think?  It would be really nice if we could figure out what's
+> going on here, because it's really annoying for me to not be able to use
+> VisualEditor since it's such a great product (I can't even access the
+> 'Switch to Source Editing' command since the menus hide behind page content!)
+
+Hey, sorry, please re-open bugs if you think more work needs to be done on them. This bug was lost to the mists of time (bugs marked RESOLVED/VERIFIED are only looked at by happenstance). :-(
+
+Unfortunately I don't have access to Safari 6.1.x here, and I still can't replicate in Safari 6.0.5 or 7.0.4/5 – and given that only security updates and a sidebar were added, it seems almost certain that the issue is specific to your setup somehow. Re-opening but I'm not sure if there's anything we can do…",1404849255,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"I'm still seeing this bug with Safari 6.1.4, guys; maybe it's more serious than we all think?  It would be really nice if we could figure out what's going on here, because it's really annoying for me to not be able to use VisualEditor since it's such a great product (I can't even access the 'Switch to Source Editing' command since the menus hide behind page content!)",1403810479,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Created attachment 15289
+Safari 6.1.3 JavaScript Console Logs for https://en.wikipedia.org/wiki/Foobar?veaction=edit
+
+As this title says, this attachment contains the JavaScript console logs which Safari 6.1.3 running on OS X 10.8.5 'Mountain Lion' provided for the URL 'https://en.wikipedia.org/wiki/Foobar?veaction=edit'.
+
+**Attached**: {F13848}",1399233089,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Andre Klapper from comment #18)
+> The ""Add an attachment"" link should work, unrelated to bug status.
+
+Oh, wait; I see it, but it moved from below the 'Additional Comments:' dialog box to below the list of attachments to this bug at the top of the page.  Stupid me; I should have looked first!",1399227158,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"The ""Add an attachment"" link should work, unrelated to bug status.",1399198199,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #16)
+> (In reply to Bryce Glover from comment #15)
+> > Maybe I should disable my Extensions and then turn them back on one by one
+> > to figure out which one is causing the problem?  That way, I could contact
+> > that plug-in's developer and discuss the bug with him or her.
+> 
+> Okay, guess what?  It's apparently *Apple's* fault since this bug occurs for
+> me with Extensions enabled (it goes away when they aren't — yay!) but (get
+> this!) *no extensions enabled*.  I'll attach what my error console gives me
+> to this bug in a sec.
+
+Sorry about changing the bug status; I thought that doing so would bring back the 'UNRESOLVED' option so that I could attach a picture of my browser's console logs for that page to which you sent me a link.  Could somebody un-'RESOLVED WONTFIX' this for me so that I can do this, or am I on my own here?",1399147476,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #15)
+> Maybe I should disable my Extensions and then turn them back on one by one
+> to figure out which one is causing the problem?  That way, I could contact
+> that plug-in's developer and discuss the bug with him or her.
+
+Okay, guess what?  It's apparently *Apple's* fault since this bug occurs for me with Extensions enabled (it goes away when they aren't — yay!) but (get this!) *no extensions enabled*.  I'll attach what my error console gives me to this bug in a sec.",1399147170,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Maybe I should disable my Extensions and then turn them back on one by one to figure out which one is causing the problem?  That way, I could contact that plug-in's developer and discuss the bug with him or her.",1399146493,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #12)
+> OK, I know that the version of Firefox which I mentioned (17.0.1) works just
+> fine even when I'm logged in to Wikipedia as myself (I didn't see the
+> 'Edit^[beta]' link when I wasn't,) so it's got to be something in Safari
+> 6.1.3 that's going wrong.
+
+That's unfortunate. I've tried it with Safari 6.0.5 and it works as expected; this is either a very odd problem with a sub-version of Safari (which is unlikely) or caused by a browser plugin. I don't really like to close such bugs as ""WORKSFORME"" but there's nothing much I can offer at this point, sadly…",1399076933,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Created attachment 15283
+Screenshot of no issue in Safari 6.0.5
+
+**Attached**: {F13847}",1399076820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #11)
+> (In reply to James Forrester from comment #10)
+> > (In reply to Bryce Glover from comment #9)
+> > > (In reply to James Forrester from comment #6)
+> > > > Would it be possible for you to visit
+> > > > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> > > > Safari, and/or in a different browser, and see if it recurs?
+> > > 
+> > > Yup; it still occurs even while I'm logged out of Wikipedia.  I've also
+> > > confirmed that all of the other menus ('Paragraph' — that's a styling menu,
+> > > right? — and the ones labeled with a question mark inside of a circle —
+> > > 'Help', maybe? — , a triangular warning sign — could this be 'Report a
+> > > Problem?' — , and a column of stacked lines — I'm assuming that this means
+> > > 'More Options') open with their menus tucked under the content of the page
+> > > that is being edited with VisualEditor.
+> > 
+> > Thanks. I take it this is still with Safari 6.1.3 with all your plugins,
+> > whilst logged out?
+> 
+> That's right.  Hold on, though; I forgot to check Firefox 17.0.1 (yeah, I
+> know; I'll remind my dad to update it as soon as I can…)
+
+OK, I know that the version of Firefox which I mentioned (17.0.1) works just fine even when I'm logged in to Wikipedia as myself (I didn't see the 'Edit^[beta]' link when I wasn't,) so it's got to be something in Safari 6.1.3 that's going wrong.",1399057745,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to James Forrester from comment #10)
+> (In reply to Bryce Glover from comment #9)
+> > (In reply to James Forrester from comment #6)
+> > > Would it be possible for you to visit
+> > > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> > > Safari, and/or in a different browser, and see if it recurs?
+> > 
+> > Yup; it still occurs even while I'm logged out of Wikipedia.  I've also
+> > confirmed that all of the other menus ('Paragraph' — that's a styling menu,
+> > right? — and the ones labeled with a question mark inside of a circle —
+> > 'Help', maybe? — , a triangular warning sign — could this be 'Report a
+> > Problem?' — , and a column of stacked lines — I'm assuming that this means
+> > 'More Options') open with their menus tucked under the content of the page
+> > that is being edited with VisualEditor.
+> 
+> Thanks. I take it this is still with Safari 6.1.3 with all your plugins,
+> whilst logged out?
+
+That's right.  Hold on, though; I forgot to check Firefox 17.0.1 (yeah, I know; I'll remind my dad to update it as soon as I can…)",1399057471,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #9)
+> (In reply to James Forrester from comment #6)
+> > Would it be possible for you to visit
+> > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> > Safari, and/or in a different browser, and see if it recurs?
+> 
+> Yup; it still occurs even while I'm logged out of Wikipedia.  I've also
+> confirmed that all of the other menus ('Paragraph' — that's a styling menu,
+> right? — and the ones labeled with a question mark inside of a circle —
+> 'Help', maybe? — , a triangular warning sign — could this be 'Report a
+> Problem?' — , and a column of stacked lines — I'm assuming that this means
+> 'More Options') open with their menus tucked under the content of the page
+> that is being edited with VisualEditor.
+
+Thanks. I take it this is still with Safari 6.1.3 with all your plugins, whilst logged out?",1399057369,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to James Forrester from comment #6)
+> Would it be possible for you to visit
+> https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> Safari, and/or in a different browser, and see if it recurs?
+
+Yup; it still occurs even while I'm logged out of Wikipedia.  I've also confirmed that all of the other menus ('Paragraph' — that's a styling menu, right? — and the ones labeled with a question mark inside of a circle — 'Help', maybe? — , a triangular warning sign — could this be 'Report a Problem?' — , and a column of stacked lines — I'm assuming that this means 'More Options') open with their menus tucked under the content of the page that is being edited with VisualEditor.",1399057226,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to James Forrester from comment #6)
+> Would it be possible for you to visit
+> https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> Safari, and/or in a different browser, and see if it recurs?
+
+Doing now…",1399056754,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Andre Klapper from comment #5)
+> (In reply to Bryce Glover from comment #4)
+> > Has this been fixed yet
+> 
+> If it was fixed, the status of this ticket was RESOLVED FIXED.
+> 
+> As long as only one user has ran into this issue and steps to reproduce are
+> unclear, it's likely not a high priority.
+
+Ah, sorry; I was getting a little impatient, not to mention worried!  I'm relatively new to Bugzilla, so, duh:  I should have thought, ""Oh!  It hasn't been marked as 'RESOLVED FIXED' yet.""  Now I feel ignorant…heh, heh.  (sheepish smile)",1399056693,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Sorry for the brief delay.
+
+I am unable to reproduce this for default-setup users on the English Wikipedia in Safari 7.0.3, in default Vector or Monobook, or whilst logged in with fewer gadgets switched on.
+
+Though it's theoretically possible that there's a rendering difference between Safari 6.1.3 and 7.0.3 in this respect, it's very unlikely, and I would assume the bug is caused by a browser plugin or a gadget.
+
+Given that you're getting the same behaviour on a different site (meta as well as enwiki), it's most likely to be a browser plugin issue (though none of your plugins look suspicious at first glance).
+
+Would it be possible for you to visit https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in Safari, and/or in a different browser, and see if it recurs?",1399045851,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #4)
+> Has this been fixed yet
+
+If it was fixed, the status of this ticket was RESOLVED FIXED.
+
+As long as only one user has ran into this issue and steps to reproduce are unclear, it's likely not a high priority.",1399031037,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Has this been fixed yet, or did everybody forget about me?",1398969156,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"I've just found out that this bug also occurs for another menu (the 'Formatting' one — that's what the menu with an icon that looks like an underlined capital 'A' is called, right?) at en:meta under my user environment.  I'll update this bug with my results as I try and use other menus in VisualEditor at other wikis.",1398538597,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Yes; I have several modifications installed as modifications both to my local copy of Safari and to my Wikipedia account (I was experiencing this bug on the English WP.)  In Safari, I have the 'Duplicate Tab' Button 2.0, Print Plus 1.1.0.2, Middle-Click AutoScroll 1.04, TabLock 1.1, Search Preview 1.2.3, Tab Reloader 1.5.2, Session 1.3.0.2, Feedly 16.0.5.21, and Ultimate Status Bar 1.3 extensions installed and enabled and the Cuss Off 1.1, MacRumors Minimal 1.7, and Lazarus Form Recovery 3.2 extensions installed, but disabled.  The en:wp Gadgets that I have enabled in my preferences are, as listed on en:wp:Special:Gadgets, Gadget-searchFocus.js, Gadget-ImageAnnotator.js, Gadget-imagelinks.js, Gadget-popups.js/Gadget-navpops.css, Gadget-PrintOptions.js, Gadget-revisionjumper.js, Twinkle, Gadget-HideFundraisingNotice.js/Gadget-HideFundraisingBanner.css, Gadget-teahouse.js/Gadget-teahouse.css, Gadget-WatchlistChangesBold.js/Gadget-WatchlistChangesBold.css, Gadget-defaultsummaries.js, Gadget-citations.js, Gadget-HotCat.js, Gadget-wikEd.js, Gadget-afchelper.js, Gadget-DRN-wizard-loader.js, Gadget-edittop.js/Gadget-edittop.css, Gadget-UTCLiveClock.js, Gadget-mySandbox.js, Gadget-purgetab.js, Gadget-externalsearch.js, Gadget-dropdown-menus.js/Gadget-dropdown-menus.css, Gadget-CommentsInLocalTime.js, Gadget-NoSmallFonts.css, Gadget-metadata.js, Gadget-MenuTabsToggle.js/Gadget-MenuTabsToggle.css, Gadget-JustifyParagraphs.css, Gadget-righteditlinks.css, Gadget-PrettyLog.js/Gadget-PrettyLog.css, Gadget-SidebarTranslate.js/Gadget-SidebarTranslate.css, Gadget-widensearch.css, Gadget-DejaVu Sans.css, Gadget-contribsrange.js, Gadget-BugStatusUpdate.js, Gadget-RTRS.js, and Gadget-NewImageThumbs.js/Gadget-NewImageThumbs.css.  The beta features that I am using on en:wp are 'New search,' 'Media Viewer,' 'VisualEditor,' 'VisualEditor formulae editing,' and 'Compact language links.'  (Maybe I should open another new bug labeled as an 'enhancement' asking for users to have the ability to export their Gadget and Beta Features settings as a CSV file so that they don't have to type them all out when they need to submit them as pieces of technical information for help with bugs?)",1398535237,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"What skin are you using, and do you have any gadgets or local user scripts or styling that might be competing?",1398371393,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+"VisualEditor: In Firefox, the context menu's background sometimes does not appear for items inside a media caption (but the icons appear still)","cite icon not having any layout
+
+Steps to reproduce:
+
+
+1.Open a page with VE in Firefox
+2.Insert a media file
+3.Now go the media settings for this image
+4.Add some cite options and reference inside media settings icon
+
+Observed Result:
+
+Just after adding the cite options and references, observe that the icon layouts for cite options and reference are missing
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13698}",1398292980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cdonwzrog6i3xfchvyc6,task_description,resolved
+"VisualEditor: In Firefox, the context menu's background sometimes does not appear for items inside a media caption (but the icons appear still)",Probable browser bug. Fun.,1401323667,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdonwzrog6i3xfchvyc6,task_subcomment,NA
+"VisualEditor: In Firefox, the context menu's background sometimes does not appear for items inside a media caption (but the icons appear still)",Needs investigation as to the cause.,1400138573,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdonwzrog6i3xfchvyc6,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Template parameter input with one line of text
+
+If I am entering text for a template parameter and then I press enter to start a new line, the input box remains the same (small) vertical size and the first line of text disappears. A very small scroll handle appears at the right, but it is not obvious that this is what it is.
+
+Press enter again to add a third line will enlarge the input box so that both the second and third lines are visible, and the dark grey scroll handle disappears (but the light grey slot for it remains. Once it gets to four lines it starts working as expected.
+
+This input box should expand enough with the first few lines, at least, that no scrolling is even necessary. By the time it becomes necessary, it should already be large enough that the scroll handle will be recognizable to users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13516}",1398186840,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-cfl3njg4dbpxcmrct57o,task_description,duplicate
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Maybe a browser bug. It happens to me (still) in Iceweasel (Debian Jessie), but not in Chromium.",1401422499,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"This is very odd. Browser bug, maybe? This isn't the behaviour for me in Chrome, Safari, Opera or Firefox here…",1401417704,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Created attachment 15164
+Template parameter input with four lines of text
+
+**Attached**: {F13519}",1398186951,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Created attachment 15163
+Template parameter input with three lines of text
+
+**Attached**: {F13518}",1398186931,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Created attachment 15162
+Template parameter input with two lines of text
+
+**Attached**: {F13517}",1398186910,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,"Related to bug 48560?
+IP editor reports that when he removed categories from this category https://it.wikipedia.org/w/index.php?title=Categoria%3AMarketing&diff=65461531&oldid=60402800 , all he could see after he saved was the category description.
+The category tree and the list of the categories at the bottom only appeared after refreshing the page.
+
+His setup: Firefox 28.0 , Vector, Windows 7
+I reproduce the same issue with that setup in this edit: https://it.wikipedia.org/w/index.php?title=Categoria%3AVisualEditor&diff=65497855&oldid=64118006 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398172860,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5gjtponbzcvgfibouvua,task_description,resolved
+VisualEditor: Need to refresh to see category tree and updated footer on category page,"Change 136311 merged by jenkins-bot:
+On category pages, only replace category description when saving
+
+https://gerrit.wikimedia.org/r/136311",1401736962,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,"Change 136311 had a related patch set uploaded by Alex Monk:
+On category pages, only replace category description when saving
+
+https://gerrit.wikimedia.org/r/136311",1401455301,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,Presumably this is pretty trivial?,1401408780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,*** Bug 65925 has been marked as a duplicate of this bug. ***,1401408756,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,Sounds like the same problem as for File: pages.,1400869847,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+Define an official thumb API,"See also:
+* {T89971}
+
+------
+
+
+MediaWiki never had an official API for the retrieval of thumbnailed images. Existing thumb URLs are considered private, and are not designed for use as a public API. Instead, clients are supposed to request a URL individually from the action API. This complicates API design and API response caching whenever the response references a thumb, and makes it difficult to dynamically select image size or quality in a client.
+
+The move to content-based addressing could provide a good opportunity to address this by defining a simple and stable thumb API.
+
+### Use cases / problem statement
+
+- **Dynamic client-side thumb size / quality selection without extra round-trips**: Clients would like to adapt image size and quality to actual network and device characteristics. Most current techniques for lazy-loading and dynamic resource selection are using JS. Having the ability to select the thumb size and quality in this code without extra round-trips would enable interesting performance optimizations.
+
+- **Caching of API responses referencing thumbnails**: Many cached API responses (such as [summary](https://rest.wikimedia.org/en.wikipedia.org/v1/?doc#!/Page_content/get_page_summary_title) or [related pages](https://rest.wikimedia.org/en.wikipedia.org/v1/?doc#!/Page_content/get_page_related_title)) contain references to thumbnails. Currently, there is no way for clients to sanely select thumb sizes, which means that we either need to fragment caches on thumb size, or try to include several sizes in the response. Good caching of API responses is becoming more pressing as high-traffic features like hovercards (see T70860) are built as direct API consumers. The need to negotiate thumb sizes supported by API end points introduces delays, and reduces the design flexibility in clients. 
+
+- **Image info caching**: Parsoid and other clients like VisualEditor currently need to request image information in order to render thumbnails. Those requests are very common, making imageinfo one of the most-used API entry points. Currently, the request necessarily contains the desired thumb size, which renders caching of imageinfo responses ineffective. If the response was dimension-independent instead, most of these responses could be served directly from caches. This would reduce response latency and load on the API cluster and related infrastructure.
+
+### API requirements
+
+- Simple selection of thumb size and -quality without a need for extra API calls.
+- Avoid cache fragmentation with deterministic URLs.
+- Support for encoding complex options in a uniform and extensible manner, without breaking existing use cases or introducing non-determinism.
+- Optional support for content negotiation (ex: client hints) in the future.
+- Support migrating to hash-based image identification in a later stage.
+
+## API proposal: Use query strings
+
+- `/v1/someimage.jpg`: Original. Returned by API end points referencing thumbnails. 
+- `/v1/someimage.jpg?w=220`: JPG thumb 220px wide. 
+- `/v1/someimage.jpg?p=22&w=500`: 500px thumb of page 22 in a multi-page document.
+- `/v1/someimage.jpg?t=2m30s&w=220`: Thumb of a video at 2m30s.
+- `/v1/someimage.jpg?lang=fr&w=220`: Thumb of an SVG, rendered to a PNG using French texts. We aren't explicitly mentioning the file format, so the client does not need to know that the original is an SVG, or that it is rendered to a PNG image.
+
+Server side requirements:
+
+- Audit and document the [existing query string API](https://commons.wikimedia.org/w/thumb.php?f=Camera2_mgx.svg&w=100&lang=fr) in [thumb.php](https://github.com/wikimedia/mediawiki/blob/master/thumb.php). T153497
+- Add strict parameter validation. Each thumb should have only a single URL. Don't allow unknown parameters, and (generally) avoid specifying default values explicitly. Exceptions can be made for page & time offset parameters, where little actual fragmentation is expected, and consistency in the use of the parameter is important.
+- Query string order normalization in Varnish (vmod): T138093
+
+### Providing original dimensions to clients
+
+In order to accurately calculate and select thumbnail dimensions, clients need to know the original image's dimensions (where applicable). Using this informations, clients can then construct a unique URL for a given thumbnail size, independent of the constraints it applied to select this size. They can also avoid content jumping around by updating image dimensions to the exact thumbnail dimensions, before the thumbnail has loaded. 
+
+Currently, MediaWiki already provides original dimensions in `data-file-{width,height}` attributes for MediaViewer's benefit. Some API responses referencing thumbnails include the equivalent information in JSON:
+
+```
+image: {
+  src: ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12"",
+  width: 640,
+  height: 480
+}
+```
+
+We can either stick to these different formats, or consider unifying this information in the URL, either in query parameters (**`/someimage.jpg?oh=768&ow=1024&w=100`**), or separately in a fragment (**`/someimage.jpg?w=100#oh=768&ow=1024`**). The latter avoids sending back purely informational parameters to the server.
+
+
+### Pros
+
+- Familiar query string syntax with wide parsing support.
+- Does not distinguish between advanced & frequently changed properties.
+
+### Cons
+
+- Requires custom ordered query string serialization code for both simple (size, quality) & more complex use cases.
+  - Subtlety of ordering requirement (still works) means that users will often ignore it, causing client side cache fragmentation.
+- Need for general query string normalization in Varnish. Weak con, as this would be generally useful.
+
+## Options for content negotiation and -selection
+
+We would like to use modern thumbnail formats where this has a benefit for users, but need to make sure that we don't break older clients with insufficient support in the process.
+
+The two main approaches for this content negotiation process are: 
+
+a) Server-side HTTP content negotiation, using client supplied headers like `accept`, and
+b) client-side JS explicitly requesting specific formats.
+
+There are pros & cons to either method, and they aren't mutually exclusive. HTTP content negotiation can work without any client-side effort for bitmap formats (ex: Chrome advertises WebM support). Client side JS can add explicit parameters for more fine-grained control, but also has only limited information to base such decisions on.
+
+Either way, the status quo and starting point is to serve widely supported formats (JPG and PNG) by default. We don't need to solve this question right away, and the proposed API is leaving all options for content negotiation open.
+
+## Deployment strategy
+
+A change like this isn't complete without a strategy that allows us to roll out new-style thumbs gradually. To avoid performance impacts, all (simple) requests for a thumb of a given size should map to the same cache entries using either URL scheme. To this end, we can roll things out in a way that lets us *rewrite* one URL scheme to the other.
+
+- New to old style:
+
+  - Simple thumbs (only width parameter specified):
+    1) Prefix the image name with the width parameter value followed by 'px-'.
+    2) Calculate the MD5 of the image name, and prefix first & first two chars of hex encoding to path (ex: `/7/72/`).
+  - Complex thumbs: Let PHP code handle the request & cache the response separately.
+- Old to new style:
+  - Simple thumbs (need to check if we can determine this with a regex):
+    1) Extract & strip width parameter
+    2) Send a request with a query string to backend
+  - Complex thumbs: Let PHP code handle the request & cache the response separately.
+
+
+### Users / apps making assumptions about the current thumb URL format
+
+See T153498.
+
+### Migration strategies in Varnish
+
+- Feasibility of rewriting majority of ""simple"" thumbnails (no key-value parameters) in Varnish.
+- Feasibility of avoiding redirect latency penalty by resolving redirect responses from thumb service in Varnish.
+
+## Small MediaWiki installs
+
+Currently, MediaWiki defaults to serving thumbnails directly from an upload directory. This means that there is no PHP code involved in serving thumbnails. This is good for performance (especially without caching), but also means that on-demand generation & a parameter-based API cannot be supported out of the box. There are several options we can pursue:
+
+1) Start to serve all thumbs through thumb.php (or an API module). The migration to this would generally be easy (especially with the API), but we would add the overhead of serving thumbs through PHP. Authentication would be supported out of the box. Caching could eliminate the performance issue for higher volume installs, or in an appliance container install that includes Varnish.
+2) Create a new way of supporting direct file serving with 404 handler and storage based on encoded query strings. This requires an advanced web server configuration, and might not be possible with less common web servers.
+
+At this point, the default option would be 1), but we can always optimize the setup with 2). We can provide 2) by default in a container-based distribution solution.
+
+
+",1398126240,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_description,open
+Define an official thumb API,"The swap of #traffic for #traffic-icebox in this ticket's set of tags was based on a bulk action for all such tickets that haven't been updated in 6 months or more.  This does not imply any human judgement about the validity or importance of the task, and is simply the first step in a larger task cleanup effort.  Further manual triage and/or requests for updates will happen this month for all such tickets.  For more detail, have a look at the extended explanation on the main page of #traffic-icebox .  Thank you!",1630538491,PHID-USER-lhtlnmkdbzlz6pbxaqdd,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592583998,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@jdrewniak shared a pointer to the https://cloudinary.com API which I thought could be a source of inspiration for this task. Be sure to check out their [[ https://cloudinary-res.cloudinary.com/video/upload/ac_none,c_scale,h_388,q_40,w_1170/manipulation_video.mp4 | 57 second demo ]].",1530805718,PHID-USER-6tlavgtsosjuvizsej53,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ugh, I am really sorry, I don't know how I could misread that so badly :( I guess my eye is trained to react to the word ""Declined"" in Phabricator emails, without reading them properly.",1522375690,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr we are just putting it in the Declined TechCom-RFC workboard, not in Phabricator as a whole. For reference, this is how we approach declining RFCs now: https://phabricator.wikimedia.org/T184653
+
+TechCom is declining at this time but will be more than happy to discuss further RFCs on this topic in the future (noting that @Fjalapeno mentioned interest in picking this up). ",1522328886,PHID-USER-a3ndrbmqqq7sb7olfps4,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#4086547, @kchapman wrote:
+> The other issue we see is there should be multiple RFCs broken out for that. Perhaps that means this is not an RFC, but an overall task that has RFCs linked to it. 
+
+I would disagree, I don't think this RfC can be meaningfully broken up. There are a few ideas it mentions but does not actually propose to do (hash-based identification, content negotiation) and those could be removed for clarity, but that's all I can see.
+
+But regardless, even if the task is not a real RfC, that's not a good reason to decline it as a Phabricator task. Probably the RfC project tag should just be removed in that case.",1522191134,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr perhaps I was not as clear as I could have been. The other issue we see is there should be multiple RFCs broken out for that. Perhaps that means this is not an RFC, but an overall task that has RFCs linked to it. 
+
+I will bring up the process in the next TechCom meeting. ",1522188019,PHID-USER-a3ndrbmqqq7sb7olfps4,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The problem here is that TechCom is using Phabricator in a different way from the rest of the movement.
+
+The normal way is that you create one task for one concept / task, and multiple groups share that task and do their workflow management in such a way that it does not conflict with that of other groups. That means using projects or workboards (since there can be any number of those but there is only one task status). Declining a task means that it was decided that it should not be done (ie. people should be actively prevented from doing it) because it is a bad idea. Most tasks are not resourced but kept open (or stalled) nevertheless.
+
+So if TechCom insists on their current workflow, it should make it clear that it prefers a different workflow, and for every idea that goes through the TechCom process there should be a separate idea task and a separate RfC task so that the TechCom can decline the RfC task when there is no resourcing, while the idea task can be kept open as something that's potentially still valid; and the existing RfC tasks should be split in two. Or TechCom should change their workflow to match that of everyone else on Phabricator, and use a workboard column or the removal of the TechCom tag or something similar for tracking ""rejected without prejudice"".
+
+In either case please keep this task open, whether it gets resourced in the near future or not. The use cases described here are still valid, the solution proposed here still captures our best understanding of the solution space, declining it would be confusing and hamper the use of Phabricator as a technical knowledge management system.",1521830534,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,For context: We have lots of client code with work arounds for getting the right sizes of images. So much duplication and bugs. We want to get rid of this code in the client and instead use this much more flexible proposed API. ,1521822249,PHID-USER-zuzwi67gyuz7wfxvuerx,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@kchapman we are interested in picking this up in Reading Infrastructure, but haven't been able to get to it. We would still like to do this if we can find some time… I should know more in Q4 about feasibility/timing.
+
+",1521822115,PHID-USER-zuzwi67gyuz7wfxvuerx,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"TechCom discussed this at our last meeting. The problem statement is still valid, but that doesn't mean it needs to be kept open as there is currently no resourcing for this. If there is still interest in this issue it could be used as material for a new RFC but the new RFC should contain one problem statement. Note: {T149847} has already been broken out into a single issue. 
+
+We are moving this to last call to be declined closing on 2018-03-29 at 1 pm PST(21:00 UTC, 22:00 CET
+
+
+
+ ",1521762316,PHID-USER-a3ndrbmqqq7sb7olfps4,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,Thanks @Anomie my information might be old. Moving to TechCom-RFC Inbox for discussion. ,1521641658,PHID-USER-a3ndrbmqqq7sb7olfps4,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#4064480, @kchapman wrote:
+> TechCom is declining because the use case is not current.
+
+Everything listed in the task's description under ""Use cases / problem statement"" seems current to me. See also T66214#1842437.",1521557737,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,The current thumbnail URL scheme could easily start including a revision number or sha1 of the original without changing the format.,1521555174,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"TechCom is declining because the use case is not current. This needs a new owner and use case. 
+
+There is actually one current use case still , which is the idea of having the thumb urls be versioned instead of “current” (ref. Performance-Team), but we intend to address that at a later point with a different proposal.",1521550747,PHID-USER-a3ndrbmqqq7sb7olfps4,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#3256693, @Tgr wrote:
+> We'll also need a way to display old versions of images. Clients can encounter old versions without expecting to due to FlaggedRevs hiding unreviewed image changes.
+
+{T149847} is designed to provide this ability, but it looks like that will still take a while. MediaWiki currently seems to prefix a timestamp to request old revisions, as in 20161203102219%21Kyoto_Station_November_2016_-02.jpg.
+
+Either version will work with this API, since the ""name"" portion is treated as an opaque identifier.",1497985249,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,We'll also need a way to display old versions of images. Clients can encounter old versions without expecting to due to FlaggedRevs hiding unreviewed image changes.,1494533430,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2981032, @Gilles wrote:
+> Accept headers and Vary: Accept are missing from the current task description.
+
+I added a section on this, but proposed to defer this question for now. As far as I am aware we don't need content negotiation right away, and the API proposal leaves all options open for a follow-up RFC.",1487875341,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2981032, @Gilles wrote:
+> Accept headers and Vary: Accept are missing from the current task description.
+
+I added a section on this, but proposed to defer this question for now. As far as I am aware we don't need content negotiation right away, and the API proposal leaves all optiones open for a follow-up RFC.",1487875318,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I think the discussion about restricting thumbnail sizes is orthogonal to this RFC. Nothing in this RFC limits our ability to later a) prefer specific sizes in a client side library, or even b) enforce the use of a limited set of sizes by returning a standard size instead of the non-standard requested size.",1487867873,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#3030371, @cscott wrote:
+> The one exception is that the current thumbnail code arbitrarily quantizes sizes in order to reduce cache overhead.  I'm not sure that is necessary to pull forward into the new service, but presumably the original quantization was added to reduce a particular cache-exhaustion DoS.  Limiting the size query to a limited set of ""thumbnail sizes"" (or ""media styles"") might be one way of avoiding a blowup in the number of different versions of a thumbnail.
+
+The current API prefers some sizes over others but does not limit clients (IIRC sizes are rounded to the closest multiple of 5px but that's not much of a limitation). That preference manifests in three ways:
+* certain sizes are pre-rendered at upload (`$wgUploadThumbnailRenderMap`)
+* for huge images, a thumbnail of some intermediary size is used as the source for scaling, not the original (see [[https://www.mediawiki.org/wiki/Manual:$wgThumbnailBuckets|`$wgThumbnailBuckets`]])
+* thumbnail rendering for non-standard sizes is throttled more aggressively.
+Mostly this is meant to improve performance for clients which limit themselves to predefined sizes (MediaWiki HTML pages and MediaViewer); to a smaller extent to help against accidental DOS by a combination of bot uploads of huge files + getting lots of thumbnailing requests in parallel when someone visits a category/gallery of said files. Cache exhaustion attacks were AFAIK not considered.
+The cache invalidation in Varnish is currently not intelligent about standard vs. nonstandard sizes (and in Swift there is no invalidation - every thumbnail is kept forever), but if that were feasible it would certainly be nice.",1487818481,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents? I've only been working with the consuming side, not the producing side of that hash.
+
+I remember that the temp path was an exception based on the filename, but didn't realize that the general hash was based on the filename as well.
+
+Not sure why we don't just compute it in Swift's rewrite.py instead of passing it along the whole pipepline. At any rate, you can ignore my previous remark.",1487795418,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents? I've only been working with the consuming side, not the producing side of that hash.
+
+I remember that the temp path was an exception based on the filename, but didn't realize that the general hash was based on the filename as well.
+
+Not sure why we don't just compute it in Swift's rewrite.py instead of passing it along the whole pipepline.",1487795379,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents? I've only been working with the consuming side, not the producing side of that hash.
+
+I remember that the temp path was an exception based on the filename, but didn't realize that the general hash was based on the filename as well.",1487795318,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents? I've only been working with the consuming side, not the producing side of that hash.",1487795256,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents?",1487795231,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"You might not have access to the file contents when you generate a URL. What I'm saying is that you can't just drop that information from the URL, Swift needs it in some form, to hit the right shard. Because it, too, can't guess the contents of the original when you ask it to look for a thumbnail in a certain shard. And when the thumbnail is missing, it also needs to hit the right shard to fetch the original.
+
+While some wikis don't have sharding for their originals/thumbnails storage and don't need that information, any attempt at defining a new API should take that information into account. Right now none of the new URL examples provided in the task description contain storage sharding information.",1487795150,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2981357, @Gilles wrote:
+> Something that's missing in the current plan, however, is the swift sharding information that is currently part of the thumb URL in production.
+
+Do you mean [the md5 of the file name](https://github.com/wikimedia/mediawiki/blob/9ac29c74edda2f457814a1ed634a19f9a44fd0a5/includes/filerepo/FileRepo.php#L685)? Calculating this on the fly is not that expensive. OpenSSL does 7248416 md5s over 16 byte data per second on my machine, which works out to about 0.1ms per md5.",1487720573,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I'll pitch {T90914} as a better solution to the ""name for different thumbnail sizes"", as it generalizes that requirement and lets wikis come up with names for arbitrary groups of image properties.  But I agree that should be mostly abstracted from the thumbnail service.  The one exception is that the current thumbnail code arbitrarily quantizes sizes in order to reduce cache overhead.  I'm not sure that is necessary to pull forward into the new service, but presumably the original quantization was added to reduce a particular cache-exhaustion DoS.  Limiting the size query to a limited set of ""thumbnail sizes"" (or ""media styles"") might be one way of avoiding a blowup in the number of different versions of a thumbnail.
+
+But better would probably be to be semi-intelligent about cache strategy, so that 1,000 different versions requested of a certain image each requested once, (a) don't necessarily push other images out of the cache (cache slots are per-image, not shared), and (b) don't necessarily push out the highest-frequency cached thumbnails of that image (ie, not just LRU strategy).",1487185083,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr, the concerns you raise are primarily about the implementation, and not really about the API. I think it is important to separate the two, and avoid relatively minor implementation concerns dictate our API design. Public APIs will stay around & affect a lot of users, while implementations can be replaced transparently.
+
+We can definitely avoid duplication of the vast majority of thumbnails by rewriting ""simple"" thumbnails in Varnish (see migration strategy section). Similarly, thumbnail serving performance for small third party installs is something we can optimize by mapping requests to file names, for example as part of the container-based distribution project.
+
+Edit: I forgot to mention that client side size selection won't work with purely static file serving in any case. At a minimum, a 404 handler would need to be configured, which is something we can do for either API, but is more complex than using thumb.php.",1487185610,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr, the concerns you raise are primarily about the implementation, and not really about the API. I think it is important to separate the two, and avoid relatively minor implementation concerns dictate our API design. Public APIs will stay around & affect a lot of users, while implementations can be replaced transparently.
+
+We can definitely avoid duplication of the vast majority of thumbnails by rewriting ""simple"" thumbnails in Varnish (see migration strategy section). Similarly, thumbnail serving performance for small third party installs is something we can optimize by mapping requests to file names, for example as part of the container-based distribution project.",1486589895,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr, the concerns you raise are primarily about the implementation, and not really about the API. I think it is important to separate the two, and avoid relatively minor implementation concerns dictate our API design. Public APIs will stay around & affect a lot of users, while implementations can be replaced transparently.
+
+We can definitely avoid duplication of the vast majority of thumbnails by rewriting ""simple"" thumbnails in Varnish (see migration strategy section). Similarly, thumbnail serving performance for small third party users is something we can optimize by mapping requests to file names, for example as part of the container-based distribution project.",1486589846,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I think the third-party MediaWiki concerns are somewhat understated and are not actually third party as we use the same arrangement via Swift (sorry, should have spotted that sooner).
+
+This is the status quo:
+* default MediaWiki setup: thumbnails are only rendered on parse, client requests for arbitrary thumbnail sizes (arbitrary being anything that's not already present in the article) are not possible. Thumbnails are referred to by URLs which mirror the filename (generated by `MediaHandler::makeParamString`) and directory structure, so setting up the web server is as easy as configuring the image directory on disk to be the webroot for `<wiki root URL>/images`. This would probably have to be deprecated if we move along with the RfC (there is not point to an API which might or might not work).
+* everything through `thumb.php`: apart from a little syntactic sugar, this is what the RfC is going for. This is a possible configuration currently although I don't think it is used much. Every image request gets streamed through PHP (or served by some external cache like Varnish).
+* 404 handling: like the default, but requests for non-existent images are sent to `thumb.php` via the web server's 404 handler, and get converted from filenames back into proper key-value querystrings (via `MediaHandler::parseParamString`), then saved to disk so the next request to the same URL gets served by the web server directly. This is probably the common setup for non-small wikis.
+* Wikimedia setup: basically same as 404 handling, with two extra layers on top: Varnish and Swift. Varnish caches URLs and is mostly agnostic of how thumbs are served. Swift (a distributed file storage) is used the same way as the disk in the previous example: the thumb URL uses a path/filename which can be represented in a filesystem, and in case of a Varnish miss, the ""web server"" (in this case a small python script) looks up the file in Swift using that path; if that fails, it forwards the request to `thumb.pgp` which transforms it into a nice query URL, renders the thumbnail, saves it to Swift then streams it.
+
+So the proposal as it is now would duplicate thumbnail storage in Swift and degrade performance in third-party wikis that don't use a reverse proxy. It makes more sense to keep the current parameter-array -> filename-on-disk mapping and document it as standard (it's ugly and ad hoc but there are seven parameters altogether in all known extensions and almost all are mutually exclusive so meh), and reimplement it in Thumbor and the Swift router script.",1486526310,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2988556, @GWicke wrote:
+>>>! In T66214#2988550, @Tgr wrote:
+>>>>! In T66214#2982093, @Fjalapeno wrote:
+>>> One piece of feedback we have been discussing is having a higher level abstraction in addition to specifying actual width.
+>> 
+>> A similar proposal on the wikitext side is {T90914}. IMO it's an interesting issue but too complicated and vaguely understood to include in the current RfC which has largely orthogonal concerns anyway.
+> 
+
+I don't think its a problem addressing outside of the current RFC.
+
+> Agreed. Such a higher-level abstraction could always be implemented in a client side library, which would select the right pixel size based on the desired high-level thumbnail type (and possibly other criteria, like device properties).
+
+
+I would like to consider not putting this type of logic in a client side library. One of the advantages of sharing an API is to prevent clients form needing to implement the same logic in multiple languages/platforms. 
+",1485980579,PHID-USER-zuzwi67gyuz7wfxvuerx,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,^ Captured in {T156910}.,1485950677,PHID-USER-w3pd7vqenmta6vpmhwcn,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2988556, @GWicke wrote:
+> Agreed. Such a higher-level abstraction could always be implemented in a client side library, which would select the right pixel size based on the desired high-level thumbnail type (and possibly other criteria, like device properties).
+
+I was one of the engineers that discussed this higher level of abstraction with @Fjalapeno. I do believe that the Reading Web team should pursue this abstraction in the projects they maintain, which are predominantly clients, and continue to discuss pushing the abstraction further down the stack when it's better understood.",1485946625,PHID-USER-w3pd7vqenmta6vpmhwcn,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2988550, @Tgr wrote:
+>>>! In T66214#2982093, @Fjalapeno wrote:
+>> One piece of feedback we have been discussing is having a higher level abstraction in addition to specifying actual width.
+> 
+> A similar proposal on the wikitext side is {T90914}. IMO it's an interesting issue but too complicated and vaguely understood to include in the current RfC which has largely orthogonal concerns anyway.
+
+Agreed. Such a higher-level abstraction could always be implemented in a client side library, which would select the right pixel size based on the desired high-level thumbnail type (and possibly other criteria, like device properties).",1485908455,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2982093, @Fjalapeno wrote:
+> One piece of feedback we have been discussing is having a higher level abstraction in addition to specifying actual width.
+
+A similar proposal on the wikitext side is {T90914}. IMO it's an interesting issue but too complicated and vaguely understood to include in the current RfC which has largely orthogonal concerns anyway.",1485908258,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Thank you all for pushing this forward! This is really great for the reading platforms where we have had lots of ambiguity with thumbnails.
+
+I'm gathering input from the platform teams (Web, Android, iOS) on the current proposal, I want to make sure we have all existing use cases covered.
+
+One piece of feedback we have been discussing is having a higher level abstraction in addition to specifying actual width. Some potential examples:
+
+- thumbnail-small
+- thumbnail-large
+- preview
+- preview-hi-resolution 
+- inline
+- inline-mobile
+- original
+
+This could have a couple advantages:
+# This allows us to evaluate sizes for each use case and specify an approbate size and canonize it in the API
+# Helps control cache fragmentation by discouraging specific size requests
+# When technology/needs change, we can update the sizes without requiring clients to update code.
+
+
+Any thoughts here?
+
+
+
+
+ ",1485790492,PHID-USER-zuzwi67gyuz7wfxvuerx,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I don't think that the existing requirements are to be touched at first. I.e. thumbnails would still be width-based only.
+
+Some adaptation of rewrite.py will probably be required, but I think for the most part it would pass along the new request format to the backend (Mediawiki or Thumbor).
+
+Something that's missing in the current plan, however, is the swift sharding information that is currently part of the thumb URL in production.",1485770318,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"WRT deployment strategy note that ATM all thumb accesses after varnish go through our [[https://github.com/wikimedia/operations-puppet/blob/production/modules/swift/files/SwiftMedia/wmf/rewrite.py | custom swift rewrite middleware]], how would that (if?) change? Would all thumbs with arbitrary height be stored alongside existing thumbs?",1485767459,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Accept headers and Vary: Accept are missing from the current task description.
+
+Standardizing entry point to thumb.php (and I guess img_auth.php) sounds great to me.
+
+Looking at existing parameters between the various handlers that we'll likely reuses as-is, I think it could be nice to use this as an opportunity to merge ""seek"" and ""page"" which are essentially the same thing in different contexts.",1485764071,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> The simplest solution would be to just move all thumb accesses to thumb.php (or an api module)
+
+I note thumb.php could probably use `MW_NO_SESSION` (see T127233), while an action API module cannot.",1485534767,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr and I discussed some more details in the office today.
+
+- General syntax: We both see general consensus around using query strings, and the (subset of) existing thumb.php parameters generally look like a sane starting point already.
+- Communicating original dimensions: We both have a preference for using the URL, with a slight preference for the hash variant (`/someimage.jpg?w=100#oh=1024&ow=768`).
+- Versioning: We expect a need to migrate the API format in the future (to content-based hashes, for example). To ensure that we can do this cleanly, we propose to prefix the thumb path with `/v1/`.
+- Third party support: We explored options for migrating third party users to the new thumb API in the future. The simplest solution would be to just move all thumb accesses to thumb.php (or an api module), but there would be a slight performance cost, which can however be addressed. Overall, we expect to be able to offer a smooth migration path.
+
+Next steps:
+
+1) Wrap up the bikeshedding on the general syntax choices & versioning. <- This is where you can contribute here & now.
+2) Audit & document the official thumb.php API. This is largely covered in {T153497}.
+3) Meet with the main stakeholders to detail an implementation plan.
+4) Finalize the RFC in a last call period.
+5) Implement. ",1485471162,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2970912, @GWicke wrote:
+> Are those key-value parameters already supported by all media handlers, or is support limited to built-in ones?
+
+`f` is magic and does not get passed to the media handlers (they receive the file as a `File` object). There are a few similar parameters, see T153497 (the ""unset..."" parts) for details.
+Apart from that, media handlers are free to do whatever. `width`/`page` is convention and supported by everything for which it makes sense, the other parameters only make sense for a single handler. (See the other task for parameters; I only reviewed the handlers which are hosted in gerrit.)",1485393372,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2970912, @GWicke wrote:
+> Are those key-value parameters already supported by all media handlers, or is support limited to built-in ones?
+
+`f` is magic and does not get passed to the media handlers (they receive the file as a PHP argument). There are a few similar parameters, see T153497 (the ""unset..."" parts) for details.
+Apart from that, media handlers are free to do whatever. `width`/`page` is convention and supported by everything for which it makes sense, the other parameters only make sense for a single handler. (See the other task for parameters; I only reviewed the handlers which are hosted in gerrit.)",1485393343,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr: That is great news. This means that we already have a means of feeding generic key-value parameters to the thumb machinery. Are those key-value parameters already supported by all media handlers, or is support limited to built-in ones?
+
+Looking at [thumb.php](https://github.com/wikimedia/mediawiki/blob/master/thumb.php#L98), it seems that some of this interface is currently considered deprecated (including the `w` and `p` shorthands). We should make a pass over this API to see if everything makes sense as-is.
+
+> That would result in URLs like https://commons.wikimedia.org/w/thumb.php?f=Camera2_mgx.svg&w=100&lang=fr, which is a bit uglier than https://commons.wikimedia.org/thumb/Camera2_mgx.svg?w=100&lang=fr but no difference in functionality
+
+The 404 handler already [tries to pull the thumb name from the path info](https://github.com/wikimedia/mediawiki/blob/master/thumb.php#L60), so it should not be that hard to support requests of the form /thumb.php/Sometitle.jpg?w=100&p=10. In production, we would probably use a prefix like /thumb/. Either way, clients would see a slightly cleaner separation between the thumb name & its parameters that is consistent between large & small installs.",1485389194,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"After thinking more about this and looking at the code I am getting more and more confused about what exactly we are trying to do. Media handlers already use two representations: a parameter array (which can be passed to `File::transform`, or by an external client to `thumb.php` - so we do have an API with sane parameters, it's just not used because there isn't any caching in front of it) and a filename prefix; `MediaHandler::makeParamString` and `MediaHandler::parseParamString` can be used to convert between the two. All that's needed for a Wikimedia thumbnail API is to set up Varnish to cache the `thumb.php` responses, and disable the `transformVia404` config flag if we also want to use query-string-style URLs in the generated HTML. That would result in URLs like [[https://commons.wikimedia.org/w/thumb.php?f=Camera2_mgx.svg&w=100&lang=fr|https://commons.wikimedia.org/w/thumb.php?f=Camera2_mgx.svg&w=100&lang=fr]], which is a bit uglier than `https://commons.wikimedia.org/thumb/Camera2_mgx.svg?w=100&lang=fr` but no difference in functionality (and it's not hard to add a wrapper if needed). Since we want to use a separate domain for uploads, we would probably change `$wgThumbnailScriptPath` to point to `https://upload.wikimedia.org/<project>/<language>/thumb.php` and use a multiwiki dispatcher script, like we used to do with bits/`load.php`. Or it could point to a RESTBase or Thumbor installation; in any case, I don't see any changes that would be needed to MediaWiki internals.",1482037109,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2850204, @Ciencia_Al_Poder wrote:
+>>>! In T66214#2827486, @GWicke wrote:
+>> Since the need for explicit control should be rare, I think using the Accept header offers the better trade-offs overall.
+> 
+> If I understand correctly, you propose to potentially send different image formats under the same request URL. That would require cache varying depending on the Accept: header (and I'm not sure about the implications of this), otherwise a cached webp response might be served to clients not supporting that format.
+
+Yes, the proposal includes setting a `Vary: accept`, and normalizing the `Accept` header value on thumb requests in Varnish. At least in the foreseeable future, the number of format variations will be very low, which keeps the normalization logic simple.",1481073842,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Not sure if it is helpful to examine, but here is a commercial image service API:
+
+https://docs.imgix.com/setup/serving-images
+https://docs.imgix.com/apis/url
+
+They do in fact pass the extension back but most other options are in query parameters (including format)
+
+
+",1481037024,PHID-USER-zuzwi67gyuz7wfxvuerx,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2827486, @GWicke wrote:
+> Since the need for explicit control should be rare, I think using the Accept header offers the better trade-offs overall.
+
+If I understand correctly, you propose to potentially send different image formats under the same request URL. That would require cache varying depending on the Accept: header (and I'm not sure about the implications of this), otherwise a cached webp response might be served to clients not supporting that format.",1481026269,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, the client can communicate the exact format(s) it prefers using either the URL, or via the Accept header. 
+
+For the vast majority of browser use cases, the Accept header has the advantage of doing the right thing implicitly, without the user needing to do anything. Advanced clients can still express their format preferences in a custom Accept header, which makes this scheme future-proof. 
+
+The downside of using Accept headers is that advanced clients would need to manually request images to control the Accept header, which will have performance disadvantages vs. native image loading.
+
+Since the need for explicit control should be rare, I think using the Accept header offers the better trade-offs overall.",1480351406,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I think it might be just a little misunderstanding. If you're talking about describing to the client what kind of media the original is, yes, a general category is probably fine. But the client needs to retain control of which mime type the thumbnail will be in. In order to avoid formats it might not support, etc. Since you bring up the Accept header, I assume that you're fine with that idea. What I think is a bad idea is the client only being able to request ""bitmap"" and getting a JPG, a PNG or a WEBP depending on criteria that only we know about without any way to control that.",1480011217,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the conversion that is interesting to clients. Do you have concrete use cases in mind that would *require* more exotic format conversions, and aren't covered by the combination of Accept header, format selector, size & quality?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later (ex: `om=image/svg+xml`), if we find an actual use case that requires it. For current use cases, I think that dealing with the low-level file types mostly adds unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server. Even if we add finer-grained information & selection control at some point, most clients will probably continue to prefer using the simplest possible solution that satisfies their requirements.",1479926154,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the conversion that is interesting to clients. Do you have concrete use cases in mind that would *require* more exotic format conversions, and aren't covered by the combination of Accept header, format selector, size & quality?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later (ex: `om=image/svg+xml`), if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479921842,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the conversion that is interesting to clients. Do you have concrete use cases in mind that would *require* more exotic format conversions, and aren't covered by the combination of Accept header, format selector, size & quality?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479919300,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the conversion that is interesting to clients. Do you have concrete use cases in mind that would *require* more exotic thumbnail conversions?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479919235,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the only one that's interesting to clients. Do you have concrete use cases in mind that would *require* more exotic thumbnail conversions?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479919207,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the only one that's interesting to clients. Do you have concrete use cases in mind that would *require* more exotic conversions?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479919090,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector to bitmap will always be possible, and is the only one that's interesting to clients. Do you have concrete use cases in mind that would *require* more exotic conversions?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479918464,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2816123, @GWicke wrote:
+> - Supply original format and size in the URL or metadata, and let the client choose between SVG originals & bitmap thumbs. Example using URL syntax: `/someimage?o=vec`
+>   - `o=vec` or `o=vid` (metadata): Original is a vector image or video. Can consider omitting this for bitmaps (default).
+>   - `oh=1024&ow=768` (metadata): Original width & height. Absent for SVGs when API or HTML use case recommends using SVG original.
+
+I don't understand the obsession with passing context through useless query parameters. Clients already obtain the minimum information about the file in some way (image name/hash) they can fetch more context about the file from that same source before making a thumbnail request. It's not like we're running out of bits when we inform a client of a thumbnail and its corresponding file. There is absolutely no constraint forcing it to all be in a single field. And if there were, you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  `/someimage#o=vec&oh=1024&ow=768` This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I still see the video/bitmap/vector abstraction in this latest example as misguided. Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc. Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.",1479898638,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2816123, @GWicke wrote:
+> - Supply original format and size in the URL or metadata, and let the client choose between SVG originals & bitmap thumbs. Example using URL syntax: `/someimage?o=vec`
+>   - `o=vec` or `o=vid` (metadata): Original is a vector image or video. Can consider omitting this for bitmaps (default).
+>   - `oh=1024&ow=768` (metadata): Original width & height. Absent for SVGs when API or HTML use case recommends using SVG original.
+
+I don't understand the obsession with passing context through useless query parameters. Clients already obtain the minimum information about the file in some way (image name/hash) they can fetch more context about the file from that same source before making a thumbnail request. It's not like we're running out of bits when we inform a client of a thumbnail and its corresponding file. There is absolutely no constraint forcing it to all be in a single field. And if there were, you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  `/someimage#o=vec&oh=1024&ow=768` This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side.
+
+I still see the video/bitmap/vector abstraction in this latest example as misguided. Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc. Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.",1479898582,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We do have some information about format support from Accept & User-Agent headers in regular image requests. Chrome for example sends `accept: image/webp,image/*,*/*;q=0.8`, indicating that it prefers WEBP where available, followed by other image formats. Firefox sends `accept: */*`, which at least indicates that it does not yet support webp. 
+
+However, there is no information about SVG support levels in common browser's accept headers. While [basic support is rather good across the board at 97+%](http://caniuse.com/#search=svg), support for advanced features is less common and mature. We can't communicate very detailed information about features used in a given SVG, so I agree with you that the conservative option will be to default to bitmap thumbs when a size is requested, and let clients opt in to using the SVG original when they are sure that client support is decent. Some indication of SVG original size & render effort could be helpful for this decision, but we'd need to add more metadata to make this available client-side.
+
+Let me sketch how this could work with a combination of negotiation & explicit parameters:
+
+- Supply original format and size in the URL or metadata, and let the client choose between SVG originals & bitmap thumbs. Example using URL syntax: `/someimage?o=vec`
+  - `o=vec` or `o=vid` (metadata): Original is a vector image or video. Can consider omitting this for bitmaps (default).
+  - `oh=1024&ow=768` (metadata): Original width & height. Absent for SVGs when API or HTML use case recommends using SVG original.
+  - `w=640` (server / client controlled): Request a bitmap thumb with this width. Thumb URLs served by APIs or HTML content can recommend a bitmap or original SVG format by adding / omitting the thumb width parameter.
+- Use basic content negotiation based on accept and user-agent headers at the Varnish layer to select the most appropriate low-level bitmap image format. In particular:
+  - Serve WEBP only when the client explicitly indicates support in its `accept` header, and the UA does not match a blacklist of browsers with incomplete WEBP support. PNG and JPG are used as the safe baseline.
+  - Can also take into account quality parameter.",1479849971,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The client doesn't necessarily have to advertise what it wants, but then if it doesn't tell us anything, we would have to be conservative and not serve formats like WEBP or SVG that aren't widely supported. When the client doesn't ask for a specific format, it would be wise to stick to JPG and PNG as the only options, as we do now.
+
+I think that accept headers make the most sense, because the client can use them in two ways. Either provide us with a list of what it supports, and let our backend pick within that selection what we think is best. Or request a specific format.
+
+In either case some knowledge of what we're capable of for a given file type is needed if you're constructing a thumbnail URL from scratch and want a specific output format. But that's the same in your proposal if you ask for a ""vector"" when the original is a JPG. That request doesn't make any sense. And if we serve a JPG in that case, the client that was expecting a ""vector"" or an SVG, if the format is asked explicitly, might not be able to process it if the data is sent to a component only designed to render SVGs.
+
+I can't see how you intend to make WEBP and SVGsupport work without the client explicitly advertising its support for these formats. Asking for ""bitmap"" doesn't mean that you support WEBP, asking for ""vector"" doesn't mean that you support SVG. At the end of the day the client support list is fine-grained. Which is why I believe that the accept header is the best option, because it can give us a comprehensive list of the client's capabilities, based on which we can decide what makes the most sense for a given file.
+
+Now on the subject of the client needing some knowledge of our original type -> thumbnail type mapping. Like I mentioned above it's unavoidable regardless of your level of abstraction about the kind of output is requested. The question is how does the client know that it can request an SVG for a given file? Or rather, that it can request just SVG and it will get what it wants. I think it's the same issue as the original's dimension, it has to be provided as metadata alongside the rest of the thumbnail information in the APIs that clients consume to construct thumbnail URLs. Think of the Media Viewer case again. Right now the original sized as passed as attributes, because that's metadata that the thumbnail URL (or the original's URL) doesn't tell you. If in the future thumbnail URLs are addressed by hash and not by filename, Media Viewer becomes ""blind"" to what kind of thumbnails it can request. Therefore it would make sense to advertise either the original's mime type as another attribute, or the list of possible output mime types, if we don't want the client to need to keep a mapping up to date between original mime types and possible thumbnail mime types we support.
+
+Even when you consider the use case of constructing a thumbnail URL ""from scratch"". Right now you need to know the filename, presumably you got that from an API or from parsing some page. Granted that you know what thumbnail formats we support for each original type, that's enough to request a thumbnail, which might fail if you request something too big. When thumbnails are addressed by hash, the hash will become the new minimum. You can still request a thumbnail with just that, but we might give you a thumbnail format you don't expect. And you still have the original size issue. If you want to generate thumbnail URLs with certainty that it will work, you're going to want to get the original size alongside the hash. And if you know that you can't process some formats we might throw at you based on our list of possible output formats, you might as well get the list of possible output formats for that file while you're already getting the hash and original dimensions.
+
+Of course the ideal case is a client that supports everything we do, but I think it would be very dangerous to make the default, when the client doesn't tell us what it supports/wants, to send what we think is the best format for a given file among all possible file formats. Our content is heavily skewed towards JPG and PNG: https://commons.wikimedia.org/wiki/Special:MediaStatistics More than 90% of our content is either of those. Meaning that if we serve SVG thumbnails for SVG files when the client doesn't tell us anything about what it wants, we're quite likely to make some clients fail 3% of the time, because people who built them didn't encounter SVGs when testing (because it's easy not to stumble upon them).
+
+Which is why I think the default behavior when nothing special is requested is to stick to JPG & PNG. That creates a really safe environment where the client can ignore the metadata I've just mentioned (which mime types can this original be rendered to) and always get a JPG or PNG back, which should be universally supported. Should the client support more, it can still ignore metadata about the file at hand and advertise through the Accept header that it can treat SVGs. Then we start serving SVGs to it when appropriate. And the client can look at the mime type of the response and act accordingly. To me that's the most likely use case and it makes the extra metadata I mention in the previous paragraph less necessary. That's what browsers already do and it doesn't require prior knowledge about the URL you're requesting.
+
+To sum up, I see two scenarios from our perspective:
+
+- client doesn't tell us what format it supports of wants. We stick to serving only JPG and PNG. We can still make ""judgment calls"" about which we serve. For example if the client wants a low-quality thumbnail, PNG originals could be served as JPG.
+- client gives us a list of formats it supports (can be just one). We do the judgment call based on that list, picking what we think is best for the file at hand, given the other thumbnail parameters (eg. quality), if any. Should we not support any of the request formats for that file, we serve an error (it's the same situation as requesting a thumbnail bigger than the original - the client asked for a conversion we won't do). The solution for a client to avoid that error is to either always include JPG & PNG in the supported list (we can document that) or fetch metadata about the file, ideally at the same time it currently gets the hash/filename, to know which mime types it can be thumbnailed into.",1479807370,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, let me try to summarize how you see this working:
+
+- We supply the exact original image format (svg, pdf, png, gif, tiff, jpg, webp-lossy, webp-lossless, videos) in URL or metadata.
+- The client maintains some mapping of original to target format & quality, and rewrites URLs to match (or manually loads images, so that it can set Accept headers). For example, it would need to know that tiff & png originals are likely line art, and might map those to webp-lossless, but only if the client supports webp-lossless well.
+
+Is this understanding correct?
+
+Do you have a concrete use case in mind that requires this level of client-side control over which format to use? Would control over SVG vs. bitmap, quality & content negotiation for support issues be sufficient to cover the same use case?",1479760922,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, let me try to summarize how you see this working:
+
+- We supply the exact original image format (svg, png, gif, tiff, jpg, webp-lossy, webp-lossless, videos) in URL or metadata.
+- The client maintains some mapping of original to target format & quality, and rewrites URLs to match (or manually loads images, so that it can set Accept headers). For example, it would need to know that tiff & png originals are likely line art, and might map those to webp-lossless, but only if the client supports webp-lossless well.
+
+Is this understanding correct?
+
+Do you have a concrete use case in mind that requires this level of client-side control over which format to use? Would control over SVG vs. bitmap, quality & content negotiation for support issues be sufficient to cover the same use case?",1479760516,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, let me try to summarize how you see this working:
+
+- We supply the exact original image format (svg, png, gif, tiff, jpg, webp-lossy, webp-lossless, videos) in URL or metadata.
+- The client maintains some mapping of original to target format & quality, and rewrites URLs to match (or manually loads images, so that it can set Accept headers). For example, it would need to know that tiff & png originals are likely line art, and might map those to webp-lossless, but only if the client supports webp-lossless well.
+
+Do you have a concrete use case in mind that requires this level of client-side control over which format to use? Would control over SVG vs. bitmap, quality & content negotiation for support issues be sufficient to cover the same use case?",1479758637,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"If you're looking for hardware acceleration/battery saving, JPG is probably your best bet. If you want the most lightweight file, then Webp. Should the device you're working with be slow or buggy when dealing with a certain format, you might want to avoid it by requesting another one.
+
+The majority of our content is on Commons where editors already use file formats according to the image contents. Eg. PNG is preferred for diagrams and JPG for photos. If you upload a diagram as a JPG you'll generally be advised to reupload it as PNG. The policy is well followed for photos and has allowed the community to put in place conditional sharpening parameters for JPGs that works well on photos but would make diagrams look terrible.",1479753306,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I don't see the search for the right granularity as a contradiction, but more as a search for the best set of trade-offs along a continuum. On one end, we have no client control & possibly server-side negotiation, while on the other end we have fine-grained client control without any content negotiation. The best set of trade-offs might not lie at the extremes of this spectrum. Lets continue to evaluate options against our use cases, and add use cases to the list in case any are missing.
+
+> If you're going to override the automatic behavior, you should have precise control.
+
+Can you think of use cases that would benefit from directly selecting jpg vs. png vs. webp lossy / lossless, rather than just vector vs. bitmap & quality level? Would those use cases need more information about the image contents (ex: line art vs. photo) to usefully pick the right format?",1479751660,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I don't see the search for the right granularity as a contradiction, but more as a search for the best set of trade-offs along a continuum. On one end, we have no client control & possibly server-side negotiation, while on the other end we have fine-grained client control without any content negotiation. The best set of trade-offs might not lie at the extremes of this spectrum. Lets continue to evaluate options against our use cases, and add use cases to the list in case any are missing.
+
+> If you're going to override the automatic behavior, you should have precise control.
+
+Can you think of use cases that would benefit from directly selecting jpg vs. png vs. webp lossy / lossless? Would those use cases need more information about the image contents (ex: line art vs. photo) to usefully pick the right format?",1479743589,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I don't see the search for the right granularity as a contradiction, but more as a search for the best set of trade-offs along a continuum. On one end, we have no client control & possibly server-side negotiation, while on the other end we have fine-grained client control without any content negotiation. The best set of trade-offs might not lie at the extremes of this spectrum. Lets continue to evaluate options against our use cases, and add use cases to the list in case any are missing.
+
+> If you're going to override the automatic behavior, you should have precise control.
+
+Can you think of use cases that would benefit from such fine-grained control? Would those use cases need more information about the image contents (ex: line art vs. photo) to usefully pick the right format?",1479743479,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"There is contradiction here. You want to serve what's best for the client ""automatically"", but you want the client to retain some control just in case, but not too much as they can't pick the specific file format they're interested in. I think that while making some options more semantic makes sense, in the case of file formats it does not. Webp, JPG, PNG have very different properties and a client should be able to specifically pick one of those if it wants to. If you're going to override the automatic behavior, you should have precise control. Especially since something as simple semantically as ""bitmap"" can already contain webp, which definitely won't work on all devices. If the only thing the client can tell us about what it accepts is ""bitmaps"" we won't be able to tell if we can serve it a webp image.
+
+As for the Accept header, if the client is using the native image fetching functions, said functions should advertise Accept headers that represent file types the device is capable of displaying. Having to use lower-level functions would only be necessary if the client wants to do something custom, like wanting a specific file format and no other. I think that's acceptable. You're point is full of assumptions about what people would implement and how they would go about it, I think it's a weak argument against dismissing a mechanism that's been a standard for decades for a client to declare what file types it can consume.",1479725429,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2805495, @Gilles wrote:
+>>>! In T66214#2803304, @GWicke wrote:
+>> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+> 
+> How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.
+
+I think Accept headers as great for selecting supported formats (such as jpg vs webm), but they aren't very usable for client-driven decisions around SVG vs. bitmaps, or bitmap thumb vs. video. To control the accept header, clients would need to use `fetch` or `xhr` to fetch images, instead of highly optimized native image loading. It might work better for video, but at the same time video needs more control over quality (adaptive streaming) than accept headers alone are intended to provide.
+
+Generally, outside of video it seems that the main use case for client code driven format selection / behavior change are around vector vs. bitmap (without caring about the exact bitmap format), and quality. Something like `?f=bmp`, `?f=vec`, `?f=vid` should be sufficient to provide this information, and allow clients to choose between retrieving a vector original vs. requesting a bitmap thumbnail.",1479494974,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2805495, @Gilles wrote:
+>>>! In T66214#2803304, @GWicke wrote:
+>> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+> 
+> How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.
+
+I think Accept headers as great for selecting supported formats (such as jpg vs webm), but they aren't very usable for client-driven decisions around SVG vs. bitmaps, or bitmap thumb vs. video. To control the accept header, clients would need to use `fetch` or `xhr` to fetch images, instead of highly optimized native image loading. It might work better for video, but at the same time video needs more control over quality (adaptive streaming) than accept headers alone can provide.
+
+Generally, outside of video it seems that the main use case for client code driven format selection / behavior change are around vector vs. bitmap (without caring about the exact bitmap format), and quality. Something like `?f=bmp`, `?f=vec`, `?f=vid` should be sufficient to provide this information, and allow clients to choose between retrieving a vector original vs. requesting a bitmap thumbnail.",1479494921,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2805495, @Gilles wrote:
+>>>! In T66214#2803304, @GWicke wrote:
+>> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+> 
+> How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.
+
+I think Accept headers as great for selecting supported formats (such as jpg vs webm), but they aren't very usable for client-driven decisions around SVG vs. bitmaps, or bitmap thumb vs. video. To control the accept header, clients would need to use `fetch` or `xhr` to fetch images, instead of highly optimized native image loading. For video, 
+
+Generally, to me it seems that the main use cases for client code driven format selection / behavior change are around vector vs. bitmap (without caring about the exact bitmap format), and quality. Something like `?f=bmp`, `?f=vec`, `?f=vid` should be sufficient to provide this information, and allow clients to choose between retrieving a vector original vs. requesting a bitmap thumbnail.",1479494606,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2805495, @Gilles wrote:
+>>>! In T66214#2803304, @GWicke wrote:
+>> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+> 
+> How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.
+
+I think Accept headers as great for selecting supported formats (such as jpg vs webm), but they aren't very usable for client-driven decisions around SVG vs. bitmaps, or bitmap thumb vs. video. To control the accept header, clients would need to use `fetch` or `xhr` to fetch images, instead of highly optimized native image loading.",1479492179,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2803304, @GWicke wrote:
+> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.",1479465868,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2804824, @Tgr wrote:
+> Re: type selection, we should use real file extensions (`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12.png` instead of `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`) otherwise we are probably going to trigger some mime type guessing bug in some obscure browser when used in HTML pages (thumbnails must work for [[https://www.mediawiki.org/wiki/Compatibility#Browsers|Grade C]] browsers).
+
+Unless we have a specific list of UAs affected by a concrete problem, this is paranoia. I recall problems with URLs that would cause a mismatch (i.e. /foo-thumb.pdf but actually returning a jpeg), but not extension-less URLs.",1479465708,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Would the API cover `img_auth.php`? How about stashed uploads and thumbnails thereof (a horrible pile of hacks currently)? Or more generally the whole ""zones"" feature of FileRepo?",1479437397,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Re: original size in URL, beside feeling a bit hacky, there are some (minor) disadvantages: generating the URL to the original file based on the filename becomes more complicated (less of an issue if we use context-based addressing anyway), and B/C becomes more limited (for a MediaHandler which has not been updated, we probably want to use the old-style URL so that we prefer breaking clients doing URL rewriting over breaking displaying the file at all; and clients expecting the size to be in the URL would be more likely to break). Also, keep in mind that size information might get more complex than two numbers (e.g. SVGs have a nominal original size but can be scaled beyond that without loss of quality and we probably want to tell the client that).
+
+Re: type selection, we should use real file extensions (`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12.png` instead of `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`) otherwise we are probably going to trigger some mime type guessing bug in some obscure browser when used in HTML pages (thumbnails must work for [[https://www.mediawiki.org/wiki/Compatibility#Browsers|Grade C]] browsers).
+
+Re: format selection use cases, there is also language selection. But I don't think the API has to be aware of formats - they are just parameters to pass through.",1479437295,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the same conversation, @Pchelolo brought up a potential issue around image format conversion / selection. We do have a need to support format conversions, for example a conversion from SVG to PNG. However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+This requirement is similar to informing the client about original dimensions, except that the desired file type also //needs// to be sent to the API to avoid default parameter fragmentation. Since we also need to support uses without any rewriting (ex: HTML), including the file type in the URL (for example, as a query parameter) seems to make the most sense.
+
+Example original URL, using query string syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`
+
+Another (possibly prettier) option would be to use a custom file extension syntax, but the downside of this would be slightly more effort for parsing.
+
+Edit: Thinking about this some more, I think we should detail a bit more which kind of control over the format we need. Aspects that come to mind:
+
+- Quality selection (esp. for bitmaps). Coarse granularity (high, normal, low) is probably all we want to expose.
+- Bitmap vs. vector graphics vs. video. 
+  - Clients might want to load the original image in case it is an SVG. For this, they need to know whether an original is a SVG vs bitmap / video before making a request. Specifying the size does not make sense for SVGs in general.
+  - Videos: Some clients could offer a video player, rather than displaying a bitmap thumb.
+- Selecting a specific bitmap format. This seems questionable, but it's conceivable that there could be client support limitations that would make this useful. Content negotiation might be a better alternative for phasing in new formats like webm.
+
+Are there any other format selection related use cases that aren't covered by these options yet?",1479416227,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the same conversation, @Pchelolo brought up a potential issue around image format conversion / selection. We do have a need to support format conversions, for example a conversion from SVG to PNG. However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+This requirement is similar to informing the client about original dimensions, except that the desired file type also //needs// to be sent to the API to avoid default parameter fragmentation. Since we also need to support uses without any rewriting (ex: HTML), including the file type in the URL (for example, as a query parameter) seems to make the most sense.
+
+Example original URL, using query string syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`
+
+Another (possibly prettier) option would be to use a custom file extension syntax, but the downside of this would be slightly more effort for parsing.
+
+Edit: Thinking about this some more, I think we should detail a bit more which kind of control over the format we need. Aspects that come to mind:
+
+- Quality selection (esp. for bitmaps). Coarse granularity (high, normal, low) is probably all we want to expose.
+- Bitmap vs. vector graphics vs. video. 
+  - Clients might want to load the original image in case it is an SVG. For this, they need to know whether an original is a SVG vs bitmap / video before making a request. Specifying the size does not make sense for SVGs in general.
+  - Videos: Some clients could offer a video player, rather than displaying a bitmap thumb.
+- Selecting a specific bitmap format. This seems questionable, but it's conceivable that there could be client support limitations that would make this useful. Content negotiation might be a better alternative for phasing in new formats like webm.
+
+Can we write down some use specific use cases for format / quality selection?",1479414790,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the same conversation, @Pchelolo brought up a potential issue around image format conversion / selection. We do have a need to support format conversions, for example a conversion from SVG to PNG. However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+This requirement is similar to informing the client about original dimensions, except that the desired file type also //needs// to be sent to the API to avoid default parameter fragmentation. Since we also need to support uses without any rewriting (ex: HTML), including the file type in the URL (for example, as a query parameter) seems to make the most sense.
+
+Example original URL, using query string syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`
+
+Another (possibly prettier) option would be to use a custom file extension syntax, but the downside of this would be slightly more effort for parsing.
+
+Edit: Thinking about this some more, I think we should detail a bit more which kind of control over the format we need. Aspects that come to mind:
+
+- Quality selection (esp. for bitmaps). Coarse granularity (high, normal, low) is probably all we want to expose.
+- Bitmap vs. vector graphics. Clients might want to load the original image in case it is an SVG. Specifying the size does not make sense for SVGs in general.
+- Selecting a specific bitmap format. This seems questionable, but it's conceivable that there could be client support limitations that would make this useful.
+
+Can we write down some use specific use cases for format / quality selection?",1479413793,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the same conversation, @Pchelolo brought up a potential issue around image format conversion / selection. We do have a need to support format conversions, for example a conversion from SVG to PNG. However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+This requirement is similar to informing the client about original dimensions, except that the desired file type also //needs// to be sent to the API to avoid default parameter fragmentation. Since we also need to support uses without any rewriting (ex: HTML), including the file type in the URL (for example, as a query parameter) seems to make the most sense.
+
+Example original URL, using query string syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`
+
+Another (possibly prettier) option would be to use a custom file extension syntax, but the downside of this would be slightly more effort for parsing.",1479407982,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Anomie thanks… The explanation makes sense. 
+
+@GWicke and I spoke at the Reading Services meeting and we are good to go - the content type is enough for the client to make decision on how to render the image - along with being able to deterministically request a specific file format.",1479406414,PHID-USER-zuzwi67gyuz7wfxvuerx,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Fjalapeno, could you say a bit more about why knowing the content type *ahead of time* would be useful to you?",1479321254,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2799548, @Fjalapeno wrote:
+> I was reading over some of the Strawman API  was wondering, is the response going to specify the file type? I couldn't quite tell.
+
+The thumb API being discussed here serves the file data. It should include an appropriate Content-Type header in the HTTP response.
+
+The details of other APIs that might return a pointer to the thumb API are probably out of scope here, even though such other APIs are mentioned.",1479314564,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I was reading over some of the Strawman API  was wondering, is the response going to specify the file type? I couldn't quite tell.
+
+I ask, because for instance, the iOS app would need to handle SVGs differently than it handles handle PNGs (though it could handle both). So knowing the file type ahead of time would be convenient. 
+",1479314051,PHID-USER-zuzwi67gyuz7wfxvuerx,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Gilles, I mostly care about providing original dimensions in a uniform and convenient way across different formats (JSON and HTML). From my point of view, both a standardized JSON structure / HTML attributes, as well as URL parameters are workable, and both have advantages and disadvantages. Overall, I see URL parameters as slightly easier to use, easier to extend & more consistent across contexts, while separate attributes are conceptually cleaner, and avoid sending unnecessary information to the server.",1479145400,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"As for face recognition to guide focused cropping, this is a functionality Thumbor provides out of the box. It even supports doing the computation remotely with a service called remotecv. Which can be useful for example if you want to run that part on servers that have GPUs, which can greatly accelerate face detection.
+
+It's a project of its own to enable that in the Thumbor setup we have, though. This update of the thumbnail URL would probably be a blocker for it, as enabling this new functionality would require at least one new thumbnail parameter.",1479123673,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Passing context like the original dimensions seems like a hack. The thumbnailing server doesn't need it.
+
+The API should be agnostic of specific use cases. This was easily solved in Media Viewer, I don't see why it couldn't be solved the same way in the API calls the apps get their thumb URLs from. Instead of only passing a thumb URL, also pass the original dimensions in additional properties. This is solvable right now, without the need for a thumbnail URL overhaul, the same way this problem was solved for Media Viewer almost 3 years ago.
+
+Not every consumer of the API needs to rewrite existing thumbnail URLs. However, API calls that currently only provide the thumbnail URL as ""information about a thumbnail"" should be able to easily provide original dimensions as well. And any other additional context defined by specific use cases of that API call in the future.
+
+Shoving all functional parameters in a single URL is crowded enough already, let's not add context that could be passed differently to the client and that the server rendering thumbnails doesn't care about.
+
+I think you're conflating your specific needs and the API's needs, as if the thumbnail URL is the only thing that can be touched to achieve your goals.
+
+And the extra metadata APIs should provide about thumbnails in addition to the thumbnail URL could be standardized or even defined in code.",1479123382,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The main potential benefit I see in encoding the original dimensions in the URL would be consistency across formats, and some ease of use from only having to pass the URL to a re-scale function. That said, with some effort we could probably get away with two alternate formats:
+
+- HTML <img> tag: `data-file-{width,height}`, as used by MediaViewer.
+- JSON: A structure like `{ src: ""..."", height: 1024: width: 768 }`, as proposed in the task description.
+
+Compared to a URL only, it is slightly more work to pass those values into a scaling function.",1478881942,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The main benefit of encoding the original dimensions in the URL would be consistency across formats, and some amount of ease of use. That said, with some effort we could probably get away with two alternate formats:
+
+- HTML <img> tag: `data-file-{width,height}`, as used by MediaViewer.
+- JSON: A structure like `{ src: ""..."", height: 1024: width: 768 }`, as proposed in the task description.
+
+Compared to a URL only, it is slightly more work to pass those values into a scaling function.",1478829621,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2787573, @Tgr wrote:
+> Is there any situation where that information could not be easily provided alongside in a more structured way (HTML attribute or API reply field)?
+
+Probably not. At least none that comes to mind right now. This idea came up since I was struggling a bit with also providing an answer for T149450#2783012.
+",1478820513,PHID-USER-tjyfydvd4ncrfvvr6mkr,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786657, @bearND wrote:
+> Requirements for a long term solution should include, in addition to scaling, the ability to crop based on a focus area[1].
+
+Cropping is {T9757}. (There are experimental services which do it: IIIF (T89552) and #imagetweaks. That's less useful than thumb URL integration of course.)
+
+>>! In T66214#2786655, @bearND wrote:
+> Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path).
+
+Is there any situation where that information could not be easily provided alongside in a more structured way (HTML attribute or API reply field)?",1478815927,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786657, @bearND wrote:
+>> look into which users rely on the current thumb format
+> 
+> The apps and MCS rely on the current thumb format to resize thumbnails downwards. If we could solve T75935 or T74328 the we could also use it to resize thumbnails upwards. That alone would solve our immediate needs.
+
+Do you already have access to original dimensions in all cases? If not, then all this scaling (and especially scaling up) is likely to result in rounding errors when calculating the actual dimensions, which would lead to distorted / ugly display.
+
+> Requirements for a long term solution should include, in addition to scaling, the ability to crop based on a focus area[1].
+> 
+> [1] That area is ideally user selectable but defaults to something based on face-detection. The apps could provide the face-detection and upload the desired coordinates to a server somewhere.
+
+In the API requirements, this is covered by general key-value support. Adding the functionality is mostly a matter of implementing it in the backend, and adding the parameter.",1478814266,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786655, @bearND wrote:
+> Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path). I don't want to call it a requirement at this time. Just something that could be useful to avoid having to also provide the original dimensions in other places, like the `data-file-*` attributes in HTML or additional width/height properties for the JSON case.
+
+I think this is an intriguing possibility. This would encapsulate all information needed for scaling an image in just the URL. Example, using query string syntax:
+
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?oh=768&ow=1024`
+More compact, but slightly custom syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?o=1024x768`
+
+To avoid cache fragmentation, we would need to require these parameters in requests, and could also check that they do indeed match the original dimensions.
+
+The main downside I see is slightly larger image URLs being sent back to the server. It's only a few bytes though, which seems unlikely to make a measurable performance difference in practice.",1478813148,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786655, @bearND wrote:
+> Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path). I don't want to call it a requirement at this time. Just something that could be useful to avoid having to also provide the original dimensions in other places, like the `data-file-*` attributes in HTML or additional width/height properties for the JSON case.
+
+I think this is an intriguing possibility. This would encapsulate all information needed for scaling an image in just the URL. Example, using query string syntax:
+
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?oh=768&ow=1024`
+More compact, but custom syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?o=1024x768`
+
+To avoid cache fragmentation, we would need to require these parameters in requests, and could also check that they do indeed match the original dimensions.
+
+The main downside I see is slightly larger image URLs being sent back to the server. It's only a few bytes though, which seems unlikely to make a measurable performance difference in practice.",1478813120,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786655, @bearND wrote:
+> Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path). I don't want to call it a requirement at this time. Just something that could be useful to avoid having to also provide the original dimensions in other places, like the `data-file-*` attributes in HTML or additional width/height properties for the JSON case.
+
+I think this is an intriguing possibility. This would encapsulate all information needed for scaling an image in just the URL. Example, using query string syntax:
+
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?oh=768&ow=1024`
+
+To avoid cache fragmentation, we would need to require these parameters in requests, and could also check that they do indeed match the original dimensions.
+
+The main downside I see is slightly larger image URLs being sent back to the server. It's only a few bytes though, which seems unlikely to make a measurable performance difference in practice.",1478811801,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> look into which users rely on the current thumb format
+
+The apps and MCS rely on the current thumb format to resize thumbnails downwards. If we could solve T75935 or T74328 the we could also use it to resize thumbnails upwards. That alone would solve our immediate needs.
+
+Requirements for a long term solution should include, in addition to scaling, the ability to crop based on a focus area[1].
+
+[1] That area is ideally user selectable but defaults to something based on face-detection. The apps could provide the face-detection and upload the desired coordinates to a server somewhere.",1478802566,PHID-USER-tjyfydvd4ncrfvvr6mkr,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path). I don't want to call it a requirement at this time. Just something that could be useful to avoid having to also provide the original dimensions in other places, like the `data-file-*` attributes in HTML or additional width/height properties for the JSON case.
+",1478802484,PHID-USER-tjyfydvd4ncrfvvr6mkr,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Related: {T74328}, {T67383}, {T75935}",1478736772,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"IRC meeting notes discussing this RFC: E355
+
+Next steps:
+
+1) look into which users rely on the current thumb format
+2) investigate effort needed to clean up the mediahandler parameter parsing
+3) discuss possible migration strategies with the traffic team
+4) reconvene with the results.",1478734948,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Maybe you didn't get it after all. There's nothing special about the ""page"" parameter, you could have the same problem with ""t=0s"" and several other options.
+
+I think you'd agree that we shouldn't allow `q=default` or `crop=none` as an alias of omitting those parameters completely.",1478718669,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> and (generally) avoid specifying default values explicitly. (Exception might be the page parameter.)
+
+Maybe you didn't get it after all. There's nothing special about the ""page"" parameter, you could have the same problem with ""t=0s"" and several other options.
+
+> Server side requirements:
+> 
+> - Query string order normalization in Varnish (vmod)
+> 
+> *Cons*
+> 
+> - Familiar query string syntax, but has ordering requirement to avoid cache fragmentation.
+>   - Need custom query string serialization in clients to avoid client cache fragmentation.
+> - Need for query string normalization in Varnish (but would be generally useful).
+
+You said the same thing (""query string normalization"") four times. Either have Varnish do it and don't even check in the API, or just make the API either error or redirect.
+
+BTW, your ""/{size}{/bandwidth}"" format is easy to misuse too, it could easily wind up with ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/330/square if a client gets the ""original spec"" confused, and it'd be possible to get confused if someone's percent-encoder is tuned to not encode characters like "";"" and ""/"" that aren't typically required to be encoded in the query portion of a URI when they're implementing special code to handle your custom format.",1478717277,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I would once again recommend that you write code that would parse, generate and cover a few known use cases for all considered schemes, in a language with decent URL parsing libraries. Limiting to bare bones string manipulation would skew things in favor of the custom formats, which I think is not a good benchmark based on modern development practices.
+
+And I mean writing that code for the existing URI scheme and the two prototype versions discussed. A lot of judgement is made here about what is practical, what is easy, what mistakes are possible, without code consuming those schemes to demonstrate those hypothetical issues.
+
+Between subjective calls on how ""hard"" something would be for client developers, to extreme examples of languages that have terrible hash behavior defaults in the context of URLs, I think the debate of the quality of each option is veering into very subjective and undemonstrative territory based on a growing army of straw men.
+
+I think future-proofness is what matters most here, but the debate of which format is best in terms of developer perspective seems hard to avoid as it keeps coming up. I just don't see a resolution coming out of people arguing that one is best based on a very hypothetical scenario.",1478715550,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I would once again recommend that you write code that would parse, generate and cover a few known use cases for all considered schemes, in a language with decent URL parsing libraries. Limiting to bare bones string manipulation would skew things in favor of the custom formats, which I think is not a good benchmark based on modern development practices.
+
+And I mean writing that code for the existing URI scheme and the two prototype versions discussed. A lot of judgement is made here about what is practical, what is easy, what mistakes are possible, without code consuming those schemes to demonstrate those hypothetical issues.
+
+Between subjective calls on how ""hard"" something would be for client developers, to extreme examples of languages that have terrible hash behavior defaults in the context of URLs, I think the debate of the quality of each option is veering into very subjective and undemonstrative territory based on a growing army of straw men.",1478715406,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"""Easy to select size and thumb type."" How is it not easy in the second example? What constitutes ""mis-use""?",1478714966,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,I'm sorry but the pros and cons you've entered are completely biased and focus on very subjective properties.,1478714839,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,The pros and cons of the current URI scheme should be included in the same matrix. Because you'll find that almost all of the upsides you're bringing up for the scheme currently in the task description also apply to the current scheme.,1478713772,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The point is that a custom ordered-querystring serialization function will be needed, while in the path-based API regular path manipulation functions will do the right thing wrt order.
+
+I think it's time to start collecting pros & cons like these for the different options, and then discuss the overall tally. API design is about finding the best trade-offs between frequently conflicting requirements. Ease of use for the most common use cases is just one of those criteria.",1478713364,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"You can look at any two formats and make up a use case that would be easier in one than the other. I don't think that should be the starting point of what the format is. That use case isn't very relevant in the infinite number of ways people might parse, transform and generate those URLs.",1478712949,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In both cases you need to parse a string and insert the value in the right place. I hope we're not going to design an API a certain way because we'd like a hypothetical developer to be able to deal with strings directly with explodes and appends rather than use a URL parsing method which nowadays should be available in all languages. If anything parsing and modifying a custom string format requires more lines of code than parsing a url and changing a value using a library designed for that.
+
+And you're making such a specific use case a first class citizen. It can't be what defines the whole format. By definition an API can be used in many ways, including many we can't foresee.",1478712842,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles: Having such author-supplied parameters in a query string means that changing the size is not just a matter of adding a *single* query parameter. This means that clients need to deal with the ordering issue, even if all they care about is the size.
+
+Compared to a URL scheme where ""advanced"" (typically author-supplied) parameters are separate from the common width & thumb type, this complicates clients and makes using the API harder.",1478712513,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles: Having such author-supplied parameters in a thumb means that changing the size is not just a matter of adding a *single* query parameter. This means that clients need to deal with the ordering issue, even if all they care about is the size.
+
+Compared to a URL scheme where ""advanced"" (typically author-supplied) parameters are separate from the common width & thumb type, this complicates clients and makes using the API harder.",1478712490,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Provided by editors in the context of wikitext, yes. I thought you meant the media's author was somehow able to set default parameters.
+
+That just means those parameters are optional. I don't see how that impacts ordering. In fact all parameters are optional if in the new scheme a lack of query parameters returns the original.",1478712274,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Provided by editors in the context of wikitext, yes. I thought you meant the media's author was somehow able to set default parameters.
+
+That just means those parameters are optional. I don't see how that impacts ordering. In fact all parameter are optional if in the new scheme a lack of query parameters returns the original.",1478712246,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Provided by editors in the context of wikitext, yes. I thought you meant the media's author was somehow able to set default parameters.
+
+That just means those parameters are optional. I don't see how that impacts ordering. In fact all parameter are optional if in the new scheme lacks of query parameters returns the original.",1478712224,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>>! In T66214#2782454, @GWicke wrote:
+>> This is because any thumbnail can have any number of author-supplied parameters already
+> 
+> Can you provide a concrete example? I don't think I'm familiar with that feature.
+
+Many advanced parameters are mostly author-supplied. Examples: page number, video thumb offset, content language for SVGs
+
+See brion's comment in T66214#1743938.
+
+Regarding API versioning & stability: Of course we can't predict the future perfectly & need mechanisms for cleanly evolving our APIs without breaking existing clients. This doesn't mean though that we should throw all caution in the wind, and ignore versioning and validation rules, or make no effort to design APIs in a thoughtful way based on our best knowledge.",1478712292,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>>! In T66214#2782454, @GWicke wrote:
+>> This is because any thumbnail can have any number of author-supplied parameters already
+> 
+> Can you provide a concrete example? I don't think I'm familiar with that feature.
+
+Many advanced parameters are mostly author-supplied. Examples: page number, video thumb offset, content language for SVGs
+
+See brion's comment in T66214#1743938.",1478711885,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2782449, @Anomie wrote:
+> I think redirects are probably //essential//. You say that the performance impact of redirects as a mechanism to encourage clients to update their code is bad, but throwing fatal errors at them is far, far worse.
+
+Where did I state that throwing a fatal error was the alternative? That's nonsense.
+
+> Sure, put a Varnish layer in front of the API as deployed for WMF to canonicalize the URLs as much as possible so the API itself doesn't have to return redirects. [[https://phabricator.wikimedia.org/T149408#2759693|But don't make a complicated Varnish layer be required for the API to be easily usable by clients of low-traffic installations.]]
+
+Nothing in what I proposed would make the URL scheme for small installations problematic. We're talking about improving cache fragmentation at the Varnish level for Varnish itself. On smaller wikis by definition the image set isn't gigantic and should they set up a caching layer the way we do with Varnish, fragmentation probably wouldn't be the end of the world. And that's assuming misbehaving clients on top of small wikis. Small wikis are quite likely to either be using well-supported extensions, which by default would probably do the right thing after this migration happens, or their own code, in which case they are responsible for their own sensible behavior when it comes to cache fragmentation at the backend caching layer. If anything the flexibility of a query string-based solution makes things easier for small wikis, as the logic behind the scheme is more universal and much less WMF-specific than what we currently have.
+
+>>! In T66214#2782563, @Anomie wrote:
+> Not necessarily. A naive query-string builder based on a python dict or a perl hash, for example, is liable to have a random parameter ordering. Perl, in particular, [[http://perldoc.perl.org/perlsec.html#Algorithmic-Complexity-Attacks|intentionally randomizes the order of hash entries for security reasons]].
+
+That's something developers using those languages should be aware of. We can't design a URL scheme or API defensively, based on terrible defaults in language X or Y. It's those languages problem, not ours. And it's probably the cause of cache fragmentation on many APIs, if constructing URLs with the helper functions in those languages results in random parameter ordering with given values. And while the example you give is for hashes, do functions in those languages that construct URLs really do that too, given who counter-productive that obviously is for caching?
+
+
+>>! In T66214#2782454, @GWicke wrote:
+> Maintaining all kinds of specific parameter validation and rewrite rules in Varnish, and keeping them in sync with the actual backend service does not sound very practicable. If we do our job of designing APIs right, then we shouldn't need to resort to such band-aids. 
+
+That's wishful thinking, because designing a URL scheme now can only be based on what you know now. You can't predict the future and unforeseen needs will come up that will directly conflict with an overly broad policy like ""we can't introduce new parameters with defaults on old urls"". The current URL scheme is testament that future needs are difficult to anticipate. Look at the history of the existing URL scheme and plan for the obvious: it will have to change and it will need massaging for backwards compatibility. If you don't plan for that, we'll get stuck again with a new format that has an equally painful migration plan as the current one. The inflexibility and hard rules need to go away, because that's exactly the source of how painful change in that area is at the moment.
+
+So far the only blocker to having a fully flexible format seems to be cache fragmentation. We can solve Varnish cache fragmentation, we just need to figure out how far that might have to go once we go down that rabbit hole. We can solve it at the client level by propagating best practices. It could be as simple as issuing a warning in headers of the response when a client doesn't have sorted parameters, in addition to documentation and communication.
+
+>>! In T66214#2782454, @GWicke wrote:
+> This is because any thumbnail can have any number of author-supplied parameters already
+
+Can you provide a concrete example? I don't think I'm familiar with that feature.",1478709245,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2782454, @GWicke wrote:
+> The bigger issue I see with query strings is that (contrary to what I thought earlier) all clients really need to implement sorted query string serialization if they want to avoid fragmenting client-side caches.
+
+I'm not opposed to this, although it does make it harder for humans to test it by putting URLs into the browser. But we'd also have to specify exactly which characters must and must not be percent-encoded (e.g. [a-zA-Z0-9._~-] must never be encoded and all others must always be) and clearly specify the sorting method (e.g. ASCIIbetical sort on encoded key=value pairs).
+
+> This is because any thumbnail can have any number of author-supplied parameters already, and changing the size of the thumb will require rewriting the query string, preserving the order. This is a loss in usability compared to separating author-supplied parameters from size & quality parameters.
+
+If size and quality are specified sanely as unique query parameters such as `size=$ABC` (or even `s=$ABC`) and `q=$XYZ`, I can't see any way that changing the specific values of $ABC or $XYZ would change the ordering of the parameters.",1478705288,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2782384, @Gilles wrote:
+> In regards to the client cache fragmentation, I think most clients are consistent with themselves and that's what matters.
+
+Not necessarily. A naive query-string builder based on a python dict or a perl hash, for example, is liable to have a random parameter ordering. Perl, in particular, [[http://perldoc.perl.org/perlsec.html#Algorithmic-Complexity-Attacks|intentionally randomizes the order of hash entries for security reasons]].",1478704998,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Currently the Varnish task seem to only focus on parameter reordering, when this is already an early sign that as the URL scheme evolves we'll want more parsing and rewriting to happen than just reordering in order to avoid cache fragmentation through future updates of the URL scheme.
+
+Maintaining all kinds of specific parameter validation and rewrite rules in Varnish, and keeping them in sync with the actual backend service does not sound very practicable. If we do our job of designing APIs right, then we shouldn't need to resort to such band-aids. For the case brought up by @anomie, there should really be little reason to bother stripping `page=1`. If we want to avoid that fragmentation internally, then we can return a redirect from the backend service for one of those, and set up a generic Varnish rule to follow those redirects on behalf of the client, avoiding round-trip penalties.
+
+The bigger issue I see with query strings is that (contrary to what I thought earlier) all clients really need to implement sorted query string serialization if they want to avoid fragmenting client-side caches. This is because any thumbnail can have any number of author-supplied parameters already, and changing the size of the thumb will require rewriting the query string, preserving the order. This is a loss in usability compared to separating author-supplied parameters from size & quality parameters.",1478703790,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Currently the Varnish task seem to only focus on parameter reordering, when this is already an early sign that as the URL scheme evolves we'll want more parsing and rewriting to happen than just reordering in order to avoid cache fragmentation through future updates of the URL scheme.
+
+Maintaining all kinds of specific parameter validation and rewrite rules in Varnish, and keeping them in sync with the actual backend service does not sound very practicable. If we do our job of designing APIs right, then we shouldn't need to resort to such band-aids. For the case brought up by @anomie, there should really be little reason to bother stripping `page=1`.
+
+The bigger issue I see with query strings is that (contrary to what I thought earlier) all clients really need to implement sorted query string serialization if they want to avoid fragmenting client-side caches. This is because any thumbnail can have any number of author-supplied parameters already, and changing the size of the thumb will require rewriting the query string, preserving the order. This is a loss in usability compared to separating author-supplied parameters from size & quality parameters.",1478703487,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781793, @GWicke wrote:
+> @anomie, I see- ""page 1"" being the default is indeed one way where there could be fragmentation. It might indeed make sense to make an exception to the ""no fragmentation"" rule in this case, and either return an identical thumbnail, or a HTTP redirect to the canonical version of this thumb.
+
+Good. I don't really care about identical thumbnail versus HTTP redirect, I was just concerned that an HTTP error as you seemed to be saying would turn out to be problematic.
+
+> In any case, existing clients wouldn't break, as none of them would be using the (new) page parameter.
+
+They would if you added it as a non-optional parameter, per your earlier statement that optional parameters wouldn't be allowed.
+
+
+>>! In T66214#2782399, @Gilles wrote:
+> I think redirects should be a last resort. An extra round trip can be very costly for users in terms of performance. Even as a mechanism to encourage clients to update their code, it's an unnecessary punishment on users who don't know how to or can't update their dated clients. 
+
+I think redirects are probably //essential//. You say that the performance impact of redirects as a mechanism to encourage clients to update their code is bad, but throwing fatal errors at them is far, far worse.
+
+Sure, put a Varnish layer in front of the API as deployed for WMF to canonicalize the URLs as much as possible so the API itself doesn't have to return redirects. [[https://phabricator.wikimedia.org/T149408#2759693|But don't make a complicated Varnish layer be required for the API to be easily usable by clients of low-traffic installations.]]",1478703358,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781793, @GWicke wrote:
+> @anomie, I see- ""page 1"" being the default is indeed one way where there could be fragmentation. It might indeed make sense to make an exception to the ""no fragmentation"" rule in this case, and either return an identical thumbnail, or a HTTP redirect to the canonical version of this thumb.
+> 
+> In any case, existing clients wouldn't break, as none of them would be using the (new) page parameter.
+
+I think redirects should be a last resort. An extra round trip can be very costly for users in terms of performance. Even as a mechanism to encourage clients to update their code, it's an unnecessary punishment on users who don't know how to or can't update their dated clients. Imho solving that at the URL sanitation level in Varnish is the way to go. Which means it should be part of the requirements for the software solution to that problem (which so far looks like a vmod, either bringing Etsy's up to date for Varnish 4 or writing a custom one). Currently the Varnish task seem to only focus on parameter reordering, when this is already an early sign that as the URL scheme evolves we'll want more parsing and rewriting to happen than just reordering in order to avoid cache fragmentation through future updates of the URL scheme.",1478702158,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781285, @GWicke wrote:
+> The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+Where is that mentioned in the task description? Are you referring to a more detailed definition hosted elsewhere? It should be linked from the task description or added to it.
+
+I fail to see how quality and cropping format are related, and it's yet another separator character for those two parameters. 
+
+>>! In T66214#2781285, @GWicke wrote:
+> /2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+
+This looks much saner to me.
+
+Considering that parameter order sanitation at the Varnish layer is desirable for many APIs, I think it makes sense to make it a dependency. Instead of designing an awkward format that enforces parameter order. If there's an upside to be had in moving to a new format without adding new features, it's that. Something based on query strings that are ordered at the Varnish layer is flexible, easy to generate/parse, extensible in ways that the existing URL scheme isn't. If we go for something that has the same constraints as the current URL scheme and is just different, then I stand by my earlier comment and @tgr's position that this is a lot of work just for aesthetics.
+
+In regards to the client cache fragmentation, I think most clients are consistent with themselves and that's what matters. I.e. if your mobile app and desktop browser don't use the same parameter ordering, it doesn't matter as they each have their separate cache. And they are are likely to request different thumbnail sizes. The reverse proxy scenario is so far fetched that I don't think it should be considered. What are the odds that different client types on the same network going through a reverse proxy request the exact same thumbnail, with the same parameter, including the same size just ordered differently? That's so narrow, I don't think we should optimize for that unlikely scenario.
+
+
+
+>>! In T66214#2781560, @Anomie wrote:
+> Say we didn't already have a parameter to select the page of a PDF. Then we add the parameter. Either the parameter needs to be optional, so probably ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?w=220"" and ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?page=1&w=220"" return the same thing, or every client that doesn't know about the new page parameter (and so uses the first URL) starts getting errors. Or, I suppose, the interface could be strange and throw an error for page=1 but not any other (valid) page.
+
+That's only problematic if we want to limit Varnish's understanding of the underlying parameters. Otherwise this is solved in the URL normalization happening at the Varnish level by stating that ""page=1"" should be stripped if encountered, because it's the default in terms of backwards compatibility. I think it will be a trade-off we'll have to consider every time we extend the available parameters. Cache fragmentation versus complexity of the code processing query parameters at the Varnish level. We'll have to make sure that whatever does the URL wrangling in Varnish performs well when we have dozens of special cases for different APIs. For something so high traffic as thumbnails I think it's kind of inevitable if we go down that road.
+
+>>! In T66214#2781961, @Tgr wrote:
+>  If we decide dropping that optimization to be able to skip some imageinfo API calls is a good tradeoff
+
+But you still can't skip imageinfo if you don't know the dimensions of the original.
+",1478701795,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781560, @Anomie wrote:
+> Say we didn't already have a parameter to select the page of a PDF. Then we add the parameter. Either the parameter needs to be optional, so probably ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?w=220"" and ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?page=1&w=220"" return the same thing, or every client that doesn't know about the new page parameter (and so uses the first URL) starts getting errors. Or, I suppose, the interface could be strange and throw an error for page=1 but not any other (valid) page.
+
+That's only problematic if we want to limit Varnish's understanding of the underlying parameters. Otherwise this is solved in the URL normalization happening at the Varnish level by stating that ""page=1"" should be stripped if encountered, because it's the default in terms of backwards compatibility. I think it will be a trade-off we'll have to consider every time we extend the available parameters. Cache fragmentation versus complexity of the code processing query parameters at the Varnish level. We'll have to make sure that whatever does the URL wrangling in Varnish performs well when we have dozens of special cases for different APIs. For something so high traffic as thumbnails I think it's kind of inevitable if we go down that road.
+
+>>! In T66214#2781961, @Tgr wrote:
+>  If we decide dropping that optimization to be able to skip some imageinfo API calls is a good tradeoff
+
+But you still can't skip imageinfo if you don't know the dimensions of the original.
+
+>>! In T66214#2781285, @GWicke wrote:
+> The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+Where is that mentioned in the task description? Are you referring to a more detailed definition hosted elsewhere? It should be linked from the task description or added to it.
+
+I fail to see how quality and cropping format are related, and it's yet another separator character for those two parameters. 
+
+>>! In T66214#2781285, @GWicke wrote:
+> /2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+
+This looks much saner to me.
+
+Considering that parameter order sanitation at the Varnish layer is desirable for many APIs, I think it makes sense to make it a dependency. Instead of designing an awkward format that enforces parameter order. If there's an upside to be had in moving to a new format without adding new features, it's that. Something based on query strings that are ordered at the Varnish layer is flexible, easy to generate/parse, extensible in ways that the existing URL scheme isn't. If we go for something that has the same constraints as the current URL scheme and is just different, then I stand by my earlier comment and @tgr's position that this is a lot of work just for aesthetics.
+
+In regards to the client cache fragmentation, I think most clients are consistent with themselves and that's what matters. I.e. if your mobile app and desktop browser don't use the same parameter ordering, it doesn't matter as they each have their separate cache. And they are are likely to request different thumbnail sizes. The reverse proxy scenario is so far fetched that I don't think it should be considered. What are the odds that different client types on the same network going through a reverse proxy request the exact same thumbnail, with the same parameter, including the ss ordered differently
+
+
+",1478701732,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The reason the current thumb URL format does not allow larger-than-original (and in most cases same-as-original) sizes is to avoid cache fragmentation (which could be circumvented in the reverse proxy but not in the client). If we decide dropping that optimization to be able to skip some imageinfo API calls is a good tradeoff, then we can keep the current URL syntax and make the original file some simple variation of that syntax (say `orig` instead of `123px`). That's a simple change, and would capture most benefits of the proposal. Granted the current URL format looks horrible, and the proposed one looks nice, but what the migration would entail is rewriting file URL generation/parsing in MediaWiki, updating every media handler extension, updating every client (or forcing their maintainers to update them), forcing everyone to change URL rewrite rules, changing VCL rules... That seems like a pretty high price to pay for aesthetics.",1478686029,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The reason the current thumb URL format does not allow larger-than-original (and in most cases same-as-original) sizes is to avoid cache fragmentation (which could be circumvented in the reverse proxy but not in the client). If we decide dropping that optimization to be able to skip some imageinfo API calls is a good tradeoff, then we can keep the current URL syntax and make the original file some simple variation of that syntax (say `orig` instead of `123px`). That's about ten lines of PHP changed, and would capture most benefits of the proposal. Granted the current URL format looks horrible, and the proposed one looks nice, but what the migration would entail is rewriting file URL generation/parsing in MediaWiki, updating every media handler extension, and updating every client (or forcing their maintainers to update them). That seems like a pretty high price to pay for aesthetics.",1478682119,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@anomie, I see- ""page 1"" being the default is indeed one way where there could be fragmentation. It might indeed make sense to make an exception to the ""no fragmentation"" rule in this case, and either return an identical thumbnail, or a HTTP redirect to the canonical version of this thumb.
+
+In any case, existing clients wouldn't break, as none of them would be using the (new) page parameter.",1478663501,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@anomie, I see- ""page 1"" being the default is indeed one way where there could be fragmentation. It might indeed make sense to make an exception to the ""no fragmentation"" rule in this case, and either return an identical thumbnail, or a HTTP redirect to the canonical version of this thumb.
+
+In any case, existing client wouldn't break, as none of them would be using the (new) page parameter.",1478663468,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Say we didn't already have a parameter to select the page of a PDF. Then we add the parameter. Either the parameter needs to be optional, so probably ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?w=220"" and ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?page=1&w=220"" return the same thing, or every client that doesn't know about the new page parameter (and so uses the first URL) starts getting errors. Or, I suppose, the interface could be strange and throw an error for page=1 but not any other (valid) page.",1478648190,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@anomie, adding parameters without changing the semantics of existing parameters won't break any existing clients, as none of those would be using the new parameter yet. In fact, this is another benefit of strict validation.
+
+It's possible I misunderstood you, though. If so, could you elaborate?",1478646799,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781285, @GWicke wrote:
+> 2) Validate parameters in the backing service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed.
+
+That could be problematic if at any point in the future we want to add additional parameters, since if you don't allow optional parameters then you'll be breaking every client in existence every time you do so.
+
+For example, if we didn't already have a time-index parameter for thumbnailing videos, or a language parameter for SVGs, or a page parameter for PDFs, etc.",1478645827,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> the description mentions the response containing JSON
+
+This is about other APIs, such as pageinfo & other references to thumbnails providing original dimensions along with the base thumb URL. It is not about the thumb API itself, which returns thumbnails.
+
+> There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+```
+# Low resolution (for mobile)
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres
+# Low resolution + square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres-square
+# Extra high quality thumb
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/highres
+# Default quality, square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/square
+```
+
+If we used query strings in general for anything but the base image, this could look like this:
+
+```
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=high&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&w=220
+```
+
+To make this work without fragmenting caches, we'd need:
+
+1) Query string order normalization in Varnish: T138093
+2) Validate parameters in the backing service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed. Only a single size spec can be used to select a given thumbnail size (`w` parameter bounding the width).
+3) Query string order normalization in clients, to avoid client cache fragmentation.
+
+Points 1) and 2) are very doable I think, but the third point somewhat complicates basic tasks like selecting the thumb size. However, if we assume that most clients *only* need to select the size & thus only need a single parameter, then this should be workable.",1478642871,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> the description mentions the response containing JSON
+
+This is about other APIs, such as pageinfo & other references to thumbnails providing original dimensions along with the base thumb URL. It is not about the thumb API itself, which returns thumbnails.
+
+> There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+```
+# Low resolution (for mobile)
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres
+# Low resolution + square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres-square
+# Extra high quality thumb
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/highres
+# Default quality, square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/square
+```
+
+If we used query strings in general for anything but the base image, this could look like this:
+
+```
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=high&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&w=220
+```
+
+To make this work without fragmenting caches, we'd need:
+
+1) Query string order normalization in Varnish: T138093
+2) Validate parameters in the backing service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed. Only a single size spec can be used to select a given thumbnail size.
+3) Query string order normalization in clients, to avoid client cache fragmentation.
+
+Points 1) and 2) are very doable I think, but the third point somewhat complicates basic tasks like selecting the thumb size. However, if we assume that most clients *only* need to select the size & thus only need a single parameter, then this should be workable.",1478642828,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> the description mentions the response containing JSON
+
+This is about other APIs, such as pageinfo & other references to thumbnails providing original dimensions along with the base thumb URL. It is not about the thumb API itself, which returns thumbnails.
+
+> There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+```
+# Low resolution (for mobile)
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres
+# Low resolution + square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres-square
+# Extra high quality thumb
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/highres
+# Default quality, square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/square
+```
+
+If we used query strings in general for anything but the base image, this could look like this:
+
+```
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=high&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&w=220
+```
+
+To make this work without fragmenting caches, we'd need:
+
+1) Query string order normalization in Varnish: T138093
+2) Validate parameters in the backing service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed. Only support one size spec for a given thumbnail size.
+3) Query string order normalization in clients, to avoid client cache fragmentation.
+
+Points 1) and 2) are very doable I think, but the third point somewhat complicates basic tasks like selecting the thumb size. However, if we assume that most clients *only* need to select the size & thus only need a single parameter, then this should be workable.",1478642782,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> the description mentions the response containing JSON
+
+This is about other APIs, such as pageinfo & other references to thumbnails providing original dimensions along with the base thumb URL. It is not about the thumb API itself, which returns thumbnails.
+
+> There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+```
+# Low resolution (for mobile)
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres
+# Low resolution + square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres-square
+# Extra high quality thumb
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/highres
+# Default quality, square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/square
+```
+
+If we used query strings in general for anything but the base image, this could look like this:
+
+```
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=high&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&w=220
+```
+
+To make this work without fragmenting caches, we'd need:
+
+1) Query string order normalization in Varnish: T138093
+2) Validate parameters in the service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed. Only support one size spec for a given thumbnail size.
+3) Query string order normalization in clients, to avoid client cache fragmentation.
+
+Points 1) and 2) are very doable I think, but the third point somewhat complicates basic tasks like selecting the thumb size. However, if we assume that most clients *only* need to select the size & thus only need a single parameter, then this should be workable.",1478642698,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+I'm now noticing something strange that I missed before, as the description mentions the response containing JSON? I would have expected that the response body would be the binary image, so that browsers can consume it directly in the no-JS case. Extra information like original URL path and original image dimensions can be passed via HTTP headers in the response, no need for JSON.
+
+I like the idea of ensuring the ordering in Varnish, if it is possible. I haven't seen how that works in VCL, have you checked how that would be implemented? That would allow us to maintain flexibility on the client side, as the URL scheme could simply be the classic &= separated URL format we all know, for example. Which would allow many clients to leverage existing libraries to construct and parse URLs in that format (which I believe is just a very old convention). It would be the client's responsibility to have sensible consistency in ordering across requests for client caches' sake, but cache fragmentation on our end is entirely avoided and I think that's all we should worry about, as all the clients we'll be responsible for will follow best practices in that respect.",1478640706,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+I'm now noticing something strange that I missed before, as the description mentions the response containing JSON? I would have expected that the response body would be the binary image, so that browsers can consume it directly in the no-JS case. Extra information like original URL path and original image dimensions can be passed via HTTP headers in the response, no need for JSON.
+
+I like the idea of ensuring the ordering in Varnish, if it is possible. I haven't seen how that works in VCL, have you checked how that would be implemented? That would allow us to maintain flexibility on the client side, as the URL scheme could simply be the classic &= separated URL format we all know, for example. Which would allow many clients to leverage existing libraries to construct and parse URLs in that format (which I believe is just a very old convention). It would be the client's responsibility to have sensible consistency in ordering across requests for client caches' sake, but cache fragmentation is entirely avoided and I think that's all we should worry about, as all the clients we'll be responsible for will follow best practices in that respect.",1478640661,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, there are several examples illustrating page and media thumbnails, as well as the (orthogonal) selection of size and thumb type / quality. The ordered key-value syntax can be used to encode rotation, cropping, effects, or other features we have not thought of yet. I'm happy to iterate through a couple of permutations if that would help to allay doubts. Dividing the API in an original spec (typically author-controlled) vs. the basic size & thumb type / quality selection was proposed by @brion earlier in this thread: T66214#1743938.
+
+I don't have overly strong opinions on the exact separators used to encode the original spec. For example, we could also use query string syntax, following the example of [media fragments](https://www.w3.org/TR/media-frags/). As long as the format is hard to abuse, and avoids cache fragmentation, a lot of options can work. If we use query strings, then we might want to strongly consider normalizing the order of parameters in Varnish, as most query string libraries don't provide any order guarantees.",1478639916,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"No examples of what rotation, cropping or effects would look like are provided.
+
+No complex examples of current capabilities are provided either, like a PDF page in low quality. Which would bring up whether the proposed format enforces optional parameter ordering. This is a property that the current scheme has and ensure good caching. At the moment it seems like things aren't thought through enough. There is no edge against the status quo, because you mention upsides that are theoretical, with no examples to back them up.
+
+To demonstrate sensibility of the proposed format, the most extreme example should be considered, just to get an idea of what it looks like to construct and parse such a URL.
+
+For example I think that using 3 different separator characters in the examples needlessly complexities parsing those URLs. Writing PoC code that generates and parses those URLs would help guide the thinking here, imho. Even better if comparing that to functions that generate and parse the current URLs. Especially if we're going to enforce ordering to ensure caching that's as good as now. Which we probably should, with the anticipated expansion of available features.",1478636541,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs, and we should aim to keep API usage for the common size & thumb type / quality selection as simple as possible. In the proposal, this is done by encoding those parameters in separate path components, making it trivial to construct the thumb URL in most cases.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.
+
+> Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL.
+
+Current thumbnail URLs are private to MediaWiki, and are explictly not intended or designed to be used as APIs. Clients can ignore this rule, but will break once we change our private thumb URL structure, for example by introducing a documented, stable thumb API.",1478635703,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs, and we should aim to keep API usage for the common size & thumb type / quality selection as simple as possible. In the proposal, this is done by encoding those parameters in separate path components.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.
+
+> Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL.
+
+Current thumbnail URLs are private to MediaWiki, and are explictly not intended or designed to be used as APIs. Clients can ignore this rule, but will break once we change our private thumb URL structure, for example by introducing a documented, stable thumb API.",1478635667,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs, and we should aim to keep API usage for the common size & thumb type / quality as simple as possible. In the proposal, this is done by encoding those parameters in separate path components.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.
+
+> Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL.
+
+Current thumbnail URLs are private to MediaWiki, and are explictly not intended or designed to be used as APIs. Clients can ignore this rule, but will break once we change our private thumb URL structure, for example by introducing a documented, stable thumb API.",1478635643,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs though, and we should aim to keep API usage for the common size & thumb type / quality as simple as possible. In the proposal, this is done by encoding those parameters in separate path components.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.
+
+> Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL.
+
+Current thumbnail URLs are private to MediaWiki, and are explictly not intended or designed to be used as APIs. Clients can ignore this rule, but will break once we change our private thumb URL structure, for example by introducing a documented, stable thumb API.",1478635575,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs though, and we should aim to keep API usage for the common size & thumb type / quality as simple as possible. In the proposal, this is done by encoding those parameters in separate path components.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.",1478635421,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2772934, @Tgr wrote:
+> Projects which can get away with being Wikimedia-only (such as the mobile apps) could just use the Thumbor API directly, though. That seems like a much less ambitious project than replacing the MediaWiki thumb API.
+
+That depends on what you want the caching and storage strategy to be. If you want to achieve reusing the same Varnish entries, as suggested in the current version of the task description, the URL translation that has to be done in Varnish becomes more complex. Furthermore, given that in the current state of affairs Thumbor is responsible for storing the resulting thumbnails in Swift, it needs Swift sharding awareness.
+
+Currently I've written an URL adapter for Thumbor for it to take care of that translation, this way Thumbor can take Wikimedia URLs directly, like so:
+
+http://127.0.0.1:8888/images/wikipedia/commons/thumb/a/a6/Chamarel_Falls_Mauritius_2.JPG/qlow-300px-Chamarel_Falls_Mauritius_2.JPG
+
+Now, you could achieve the same image by requesting this, going through the standard Thumbor URL handler:
+
+http://127.0.0.1:8888/unsafe/300x/filters:quality(40):conditional_sharpen(0.0,0.8,1.0,0.0,0.85):format(jpg)/upload.wikimedia.org/wikipedia/commons/a/a6/Chamarel_Falls_Mauritius_2.JPG
+
+But that wouldn't save the end result in Swift. Granted, we could reconstruct the Wikimedia URL from the Thumbor URL, or parse the same information from it, and make it save the output to Swift. But I felt that it was better not to mess with default Thumbor behavior because people have expressed the need to want to use Thumbor without saving the results in Swift.
+
+I would like a new service to replace what rewrite.py currently does and would be responsible for coordinating the various services involved in thumbnailing (currently Thumbor, Swift and the Mediawiki API). It would basically combine all that URL parsing/translating logic + swift sharding currently found in rewrite.py and thumbor, keeping Thumbor and Swift dumb. Thumbor would only care about returning a thumbnail, not where it gets stored. And Swift would only care about writing and reading content and Swift locations, without the need to rewrite URLs and proxy requests itself. This doesn't solve the Varnish side of things, though. If you want Varnish to support two URL schemes pointing to the same Varnish entry, there's no escaping writing some VCL or a vmod.
+
+Now, regarding the current plan of this task. It seems to me like the goal is to simplify what's currently available, with no plan to add new features, since the ""limited choice"" property ensure that a new URL scheme would be as efficient cache-wise as the old one. The deployment plan, if the Varnish side of things can be done, looks ok. But what I dislike about this plan is that it's not a migration plan. You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme. Creating that much technical debt without an owner shouldn't be allowed. I would support this plan if it was a full migration one and the project included upgrading mediawiki's built-in URL scheme to a cleaner, more extensible one.
+
+Furthermore, the value of a migration aiming for 1-to-1 mapping between two URL schemes is questionable. It's a lot of work, potentially a dual URL scheme for the foreseeable future due to the lack of plan to get rid of the old one, a new service to support. What do we get out of it that's new? A few minutes of developer time saved figuring out the existing URL scheme? These URLs will be consumed by programs that don't care about their beauty.
+
+Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL. It's just a convenience to have it made for you and to have the fallback to the original when a width that's too large is requested. The newly proposed URL scheme doesn't solve that. You still can't know the dimensions of the original in advance if you only have the filename and you are susceptible to requesting a size that can't be rendered. Just like you would be if you constructed a thumbnail URL manually without using imageinfo.",1478539413,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2772934, @Tgr wrote:
+> Projects which can get away with being Wikimedia-only (such as the mobile apps) could just use the Thumbor API directly, though. That seems like a much less ambitious project than replacing the MediaWiki thumb API.
+
+That depends on what you want the caching and storage strategy to be. If you want to achieve reusing the same Varnish entries, as suggested in the current version of the task description, the URL translation that has to be done in Varnish becomes more complex. Furthermore, given that in the current state of affairs Thumbor is responsible for storing the resulting thumbnails in Swift, it needs Swift sharding awareness.
+
+Currently I've written an URL adapter for Thumbor for it to take care of that translation, this way Thumbor can take Wikimedia URLs directly, like so:
+
+http://127.0.0.1:8888/images/wikipedia/commons/thumb/a/a6/Chamarel_Falls_Mauritius_2.JPG/qlow-300px-Chamarel_Falls_Mauritius_2.JPG
+
+Now, you could achieve the same image by requesting this, going through the standard Thumbor URL handler:
+
+http://127.0.0.1:8888/unsafe/300x/filters:quality(10):conditional_sharpen(0.0,0.8,1.0,0.0,0.85):format(jpg)/upload.wikimedia.org/wikipedia/commons/a/a6/Chamarel_Falls_Mauritius_2.JPG
+
+But that wouldn't save the end result in Swift. Granted, we could reconstruct the Wikimedia URL from the Thumbor URL, or parse the same information from it, and make it save the output to Swift. But I felt that it was better not to mess with default Thumbor behavior because people have expressed the need to want to use Thumbor without saving the results in Swift.
+
+I would like a new service to replace what rewrite.py currently does and would be responsible for coordinating the various services involved in thumbnailing (currently Thumbor, Swift and the Mediawiki API). It would basically combine all that URL parsing/translating logic + swift sharding currently found in rewrite.py and thumbor, keeping Thumbor and Swift dumb. Thumbor would only care about returning a thumbnail, not where it gets stored. And Swift would only care about writing and reading content and Swift locations, without the need to rewrite URLs and proxy requests itself. This doesn't solve the Varnish side of things, though. If you want Varnish to support two URL schemes pointing to the same Varnish entry, there's no escaping writing some VCL or a vmod.
+
+Now, regarding the current plan of this task. It seems to me like the goal is to simplify what's currently available, with no plan to add new features, since the ""limited choice"" property ensure that a new URL scheme would be as efficient cache-wise as the old one. The deployment plan, if the Varnish side of things can be done, looks ok. But what I dislike about this plan is that it's not a migration plan. You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme. Creating that much technical debt without an owner shouldn't be allowed. I would support this plan if it was a full migration one and the project included upgrading mediawiki's built-in URL scheme to a cleaner, more extensible one.
+
+Furthermore, the value of a migration aiming for 1-to-1 mapping between two URL schemes is questionable. It's a lot of work, potentially a dual URL scheme for the foreseeable future due to the lack of plan to get rid of the old one, a new service to support. What do we get out of it that's new? A few minutes of developer time saved figuring out the existing URL scheme? These URLs will be consumed by programs that don't care about their beauty.
+
+Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL. It's just a convenience to have it made for you and to have the fallback to the original when a width that's too large is requested. The newly proposed URL scheme doesn't solve that. You still can't know the dimensions of the original in advance if you only have the filename and you are susceptible to requesting a size that can't be rendered. Just like you would be if you constructed a thumbnail URL manually without using imageinfo.",1478539394,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2767815, @Gilles wrote:
+> These issues have been decoupled. Thumbor is currently set to be a drop-in replacement for image scalers in Wikimedia production for public wikis. No functional, thumbnail URI change, etc. set to happen with Thumbor's initial deployment. ""Just"" switching from an open-source piece of stack to another, so to speak.
+
+Projects which can get away with being Wikimedia-only (such as the mobile apps) could just use the Thumbor API directly, though. That seems like a much less ambitious project than replacing the MediaWiki thumb API.",1478293629,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+We could clearly allow arbitrary limits on width, height, or both. However, if we did this with different URLs, then this would fragment caches. Avoiding cache fragmentation is one of the explicit goals for this API.
+
+The API strawman still supports limiting on either of those dimensions, provided that the original image's dimensions (or exact aspect ratio) are available to the client. This information is fairly easy to provide, and is in fact already provided in MediaWiki HTML for the benefit of the media viewer (see `data-file-{width,height}`).
+
+Additionally, knowledge of original image dimensions enables the client to pre-calculate the exact thumb dimensions, which is important to avoid content jumping around during HTML rendering.
+
+I added this explicitly in the strawman description. @gilles, thanks for bringing this up, it's a very good point!",1478279253,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+We could clearly allow arbitrary limits on width, height, or both. However, if we did this with different URLs, then this would fragment caches. Avoiding cache fragmentation is one of the explicit goals for this API.
+
+The API strawman still supports limiting on either of those dimensions, provided that the original image's dimensions (or exact aspect ratio) are available to the client. This is information is easy to provide, and is in fact already provided in MediaWiki HTML for the benefit of the media viewer (see `data-file-{width,height}`).
+
+Additionally, knowledge of original image dimensions enables the client to pre-calculate the exact thumb dimensions, which is important to avoid content jumping around during HTML rendering.
+
+I added this explicitly in the strawman description. @gilles, thanks for bringing this up, it's a very good point!",1478279204,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+We could clearly allow arbitrary limits on width, height, or both. However, if we did this with different URLs, then this would fragment caches. Avoiding cache fragmentation is one of the explicit goals for this API.
+
+The API strawman still supports limiting on either of those dimensions, provided that the original image's dimensions (or exact aspect ratio) are available to the client. This is information is easy to provide, and is in fact already provided in MediaWiki HTML for the benefit of the media viewer (see `data-file-{width,height}`).
+
+Additionally, knowledge of original image dimensions enables the client to pre-calculate the exact thumb dimensions, which is important to avoid content jumping around during HTML rendering.",1478279106,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+We could clearly allow arbitrary limits on width, height, or both. However, this would fragment caches, and avoiding cache fragmentation is one of the explicit goals for this API.
+
+The API strawman still supports limiting on either of those dimensions, provided that the original image's dimensions (or exact aspect ratio) are available to the client. This is information is easy to provide, and is in fact already provided in MediaWiki HTML for the benefit of the media viewer (see `data-file-{width,height}`).",1478278167,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+In a way, the square example is a special case of defining both height and width constraints.
+
+This is the sort of thing that might be more obvious by looking at other thumbnail URI schemes for inspiration, such as Thumbor's (probably a good idea to look at that considering it will be backing it) or IIIF. Thumbor in particular offers some features that will likely be the first requested additions to be publicly exposed, like smart cropping.
+
+In we only consider existing features for the design of the new URI scheme, we risk reproducing the same mistaking of not planning enough for the future and ending up with something awkward-looking for the sake of backwards compatibility.
+
+I've been considering as a follow-up project to the Thumbor deployment extracting Swift's rewrite.py into its own service to facilitate URI rewriting and Swift/Thumbor coordination. It would be the natural place to live for code to handle a new URI scheme such as what is proposed here. I.e. a service that would sit between varnish and swift/thumbor/mediawiki/whatever comes next.",1478170986,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format.
+
+In a way, the square example is a special case of defining both height and width constraints.
+
+This is the sort of thing that might be more obvious by looking at other thumbnail URI schemes for inspiration, such as Thumbor's (probably a good idea to look at that considering it will be backing it) or IIIF. Thumbor in particular offers some features that will likely be the first requested additions to be publicly exposed, like smart cropping.
+
+In we only consider existing features for the design of the new URI scheme, we risk reproducing the same mistaking of not planning enough for the future and ending up with something awkward-looking for the sake of backwards compatibility.
+
+I've been considering as a follow-up project to the Thumbor deployment extracting Swift's rewrite.py into its own service to facilitate URI rewriting and Swift/Thumbor coordination. It would be the natural place to live for code to handle a new URI scheme such as what is proposed here. I.e. a service that would sit between varnish and swift/thumbor/mediawiki/whatever comes next.",1478170945,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2762226, @bearND wrote:
+> In addition to that I'd like to know what the relationship between this task and the Thumbor project is. I don't see it tagged here.
+
+These issues have been decoupled. Thumbor is currently set to be a drop-in replacement for image scalers in Wikimedia production for public wikis. No functional, thumbnail URI change, etc. set to happen with Thumbor's initial deployment. ""Just"" switching from an open-source piece of stack to another, so to speak.",1478169489,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2762226, @bearND wrote:
+> In addition to that I'd like to know what the relationship between this task and the Thumbor project is. I don't see it tagged here.
+
+These issues have been decoupled. Thumbor is currently set to be a drop-in replacement for image scalers in Wikimedia production for public wikis. No functional, thumbnail URI change, etc. set to happen with Thumbor's initial deployment.",1478169274,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I have refactored this RFC to focus on the public thumb API, and moved content hash based thumb naming to a sub-task.
+
+We would like to tackle the public thumb API first, and expect to be able to move to content hash based thumb naming transparently at a later point.",1478121246,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,In addition to that I'd like to know what the relationship between this task and the Thumbor project is. I don't see it tagged here.,1478059605,PHID-USER-tjyfydvd4ncrfvvr6mkr,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We are continuing to bump into the basic issue of letting clients select thumb sizes, so would really like to start tackling that part of the problem soon.
+
+@brion, has there been any movement on this during the off-site?",1478033714,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@GWicke Yes, I think we should revive it as part of a concerted effort between Editing/Parsing and Reading to improve image & multimedia handling. In particular we need to sync up parameter handling between the classic parser, parsoid, and things that use that output and then do other things (like media viewer widget) that want to be able to manipulate media parameters with fewer API roundtrips...
+
+This'll go easier if I can get another engineer or two on board, we'll see. :) But I think the priority should be raising soon. (Editing dept offsite is next week, I will be lobbying people with specific ideas. ;)",1476228988,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion, this task looks pretty stalled by now. Do you see a chance for reviving it any time soon?",1476225458,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Discussed in {E148}.  Releve
+
+3:00 PM <wm-labs-meetbot`> Minutes:        https://tools.wmflabs.org/meetbot/wikimedia-office/2016/wikimedia-office.2016-03-16-21.00.html
+3:00 PM <wm-labs-meetbot`> Minutes (text): https://tools.wmflabs.org/meetbot/wikimedia-office/2016/wikimedia-office.2016-03-16-21.00.txt
+3:00 PM <wm-labs-meetbot`> Minutes (wiki): https://tools.wmflabs.org/meetbot/wikimedia-office/2016/wikimedia-office.2016-03-16-21.00.wiki
+3:00 PM <wm-labs-meetbot`> Log:            https://tools.wmflabs.org/meetbot/wikimedia-office/2016/wikimedia-office.2016-03-16-21.00.log.html
+
+  * topic discussed: where we add extra parameters (page, time,
+    language, etc) is the format sufficiently clearly specified?
+    (robla, 21:04:13)
+  * to discuss in future: implementation details for small/large
+    installs (backlog)  (brion, 21:05:47)
+  * avoiding cache fragmentation will require normalization of
+    parameters (deterministic serialization of hashmap or other
+    ordering)  (brion, 21:19:50)
+  * daniel suggests having the failed-validation case be a redirect,
+    gwicke warns they're expensive  (brion, 21:20:24)
+  * normalizing parameters within varnish would be painful  (brion,
+    21:20:43)
+
+Log from this portion:
+{P2778}",1458167610,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I have updated the task description to more clearly separate out use cases and requirements, especially for the API portion.",1458158302,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What problem would such a VCL rule solve?
+
+We need both a good long-term API design, as well as a migration strategy that lets us gradually move towards an API without throwing away existing caches. Such a VCL rule could potentially help with the migration.
+
+I think we should first try to work out the requirements and at least a solid outline of a longer-term solution. While the migration path is important, it should not be the single concern dictating the design of the final API.",1458155783,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2114121, @GWicke wrote:
+> This depends on how much information is available in the opaque id. For example, we could consider using the current thumb URL as the ID until we introduce hashes, which would leave the VCL to fill in the width parameter (if supplied). Format selection support could then be added at a later stage.
+
+That seems somewhat pointless, given that the current thump URL is already an API capable of interpreting itself. What problem would such a VCL rule solve?",1457754010,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Also, a 100% compatible VCL-layer mapping of nice URLs to old URL is just not gonna happen. For example the URL to a full-sized JPEG thumbnail is different depending on whether the JPEG has an EXIF rotation.
+
+This depends on how much information is available in the opaque id. For example, we could consider using the current thumb URL as the ID until we introduce hashes, which would leave the VCL to fill in the width parameter (if supplied). Format selection support could then be added at a later stage.
+
+It is also good to remember that the reason for doing this in VCL is performance for the common case. If there is a small percentage of requests that requires more complex rewriting during a transition period, then falling through to a backend service for those can be okay.",1457751314,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What data is fetched and used before knowing what thumbnail to request?
+
+Normally, no separate request should be needed beyond the original HTML or API request referencing the image:
+
+- In a page, data attributes already indicate original dimensions.
+- In API end points such as summary, relatedpages or imageinfo itself, we will provide at least:
+  - the base thumb path
+  - the original dimensions
+
+Combined knowledge of a generally supported list of formats / qualities this is sufficient to build up the appropriate thumb URL by:
+
+1) appending the size, and, optionally
+2) appending the preferred format / quality parameter.",1457750558,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2106748, @faidon wrote:
+> This isn't currently possible with the existing tech and without some rearchitecturing, so it's not just a matter of URL rewriting in VCL as has been already proposed. (upload.wikimedia.org traffic is directed directly to Swift, which knows nothing about the possible thumbnail sizes)
+
+Agreed, we'd need to at least change some of the backend logic behind thumb.php and the 404-magic to resolve those edge cases... in which case we might be halfway towards making the existing system not awful without a URL reform ;)
+
+>> Secondary use case: local caching of those images is simplified if the caching properties of those thumbnail URLs are more predictable.
+> 
+> Could you elaborate on that? Are you talking about content-hashed or other versioned URLs that always point to the same version of the image and can be locally cached or do you mean something else by predictable?
+
+Version stability yes; this can be achieved without hash-based IDs by always including a timestamp with the link/reference provided in the web pages/APIs/etc.
+
+>> Tertiary use case: there's a lot of use on mobile of squared-off images in lists/menus, and specially-cropped 'hero' images on articles. Having a cleaner thumb URL API should make it easier to extend it to move more of that cropping to the server-side, simplifying client code and reducing the amount of data transferred over mobile networks by pre-cropping unseen edges before download.
+> 
+> *Nod*, I remember hearing about this use case before. It doesn't seem to have been thought of in the existing strawman proposal so far and I agree that it's definitely something that we should keep in mind when talking about a ""thumb API"".
+
+Yeah this is mostly a 'keep in mind we need to be able to extend whatever API we end up with, cleanly' reminder. The existing parameters stuffed into the thumbnail filenames (such as time point for videos, page for multi-page PDF/TIFF/DjVu, etc) are awkward and hard to parse or generate.
+",1457630165,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105088, @brion wrote:
+> Quick note from IRC regarding the thumb-URL needs for mobile apps/web:
+
+Thanks for this — and judging from the response, I'm glad I asked :)
+
+> The primary use case for mobile apps/web here is loading an appropriately-sized thumbnail of a given image as quickly as possible. Currently this requires either an extra HTTPS round-trip for the 'imageinfo' API, or rewriting the existing thumb URLs on the client and then working around the various edge cases (having to know that .svg thumbnails to .svg.png; handling failure cases when asking for a too-big size, knowing that very long filenames in thumbnail paths are sometimes rewritten to fit a length limit, etc). A cleaner, more consistent URL-based API will allow leaving the formatting and sizing questions to the server end.
+
+This isn't currently possible with the existing tech and without some rearchitecturing, so it's not just a matter of URL rewriting in VCL as has been already proposed. (upload.wikimedia.org traffic is directed directly to Swift, which knows nothing about the possible thumbnail sizes)
+
+> Secondary use case: local caching of those images is simplified if the caching properties of those thumbnail URLs are more predictable.
+
+Could you elaborate on that? Are you talking about content-hashed or other versioned URLs that always point to the same version of the image and can be locally cached or do you mean something else by predictable?
+
+> Tertiary use case: there's a lot of use on mobile of squared-off images in lists/menus, and specially-cropped 'hero' images on articles. Having a cleaner thumb URL API should make it easier to extend it to move more of that cropping to the server-side, simplifying client code and reducing the amount of data transferred over mobile networks by pre-cropping unseen edges before download.
+
+*Nod*, I remember hearing about this use case before. It doesn't seem to have been thought of in the existing strawman proposal so far and I agree that it's definitely something that we should keep in mind when talking about a ""thumb API"".",1457618569,PHID-USER-ktuojnvco4fpzmyhzyaf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2106026, @Gilles wrote:
+> Which means that a default implementation in mediawiki would have no use in production, as it's inefficient to query mediawiki for some translation before trying to hit swift if the thumbnail already exists.
+
+Given that the old format is based on filenames and the new one on content hashes, MediaWiki would have to be queried anyway as there is no way to do that translation without a DB lookup.
+
+Also it's generally best to keep frontend layers simple: forward misses to the MediaWiki API, and have the API set up the appropriate redirect in the frontend. Swift apparently has a [[ https://specs.openstack.org/openstack/swift-specs/specs/in_progress/symlinks.html | symlink API ]], not sure what's the equivalent in Varnish.",1457605085,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2106020, @Gilles wrote:
+> What data is fetched and used before knowing what thumbnail to request?
+* original size (cannot really be helped by the API, indeed)
+* extension (e.g. .svg -> .svg.png) and whether this file type can be scaled beyond the original size (also cannot be helped, and is a global one-time lookup anyway)
+
+Other info that's not required for looking up a thumbnail URL given a thumbnail URL of different size, but is required for looking up a thumbnail URL given a filename:
+* filename hash (can be computed, but that's not the kind of thing you want to require a client to do)
+* per-repo configuration (hash level, URL prefix, initial capital), based on which repo the file is in (which is typically not known by the client)
+* content hash (in the future)
+
+There are some idiosyncrasies which also prevent guessing the thumbnail URL but could be solved within the current system:
+* the full URL, if requesting a size larger than or equal to the original
+* knowing whether a thumbnail or the full URL must be requested when asking for the exact same size as the original (specifically for JPEG files, knowing whether they have an EXIF rotation)
+* name reduction if the filename is longer than `abbrvThreshold`
+",1457603737,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105215, @brion wrote:
+>similar to how not-yet-cached thumbnail URLs are routed through MW's thumb.php and friends the first time.
+
+The thumbnail URLs are passed verbatim to Swift, which does some translation inside a Swift plugin, checks whether it has a copy of the thumbnail, and then hits mediawiki if it doesn't have a copy.
+
+This logic would have to be extracted out of Swift into its own service sitting in front of it, then that service extended for new things. Adding to the existing Swift plugin or to VCL are both undesirable.
+
+Which means that a default implementation in mediawiki would have no use in production, as it's inefficient to query mediawiki for some translation before trying to hit swift if the thumbnail already exists.",1457598921,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105215, @brion wrote:
+>similar to how not-yet-cached thumbnail URLs are routed through MW's thumb.php and friends the first time.
+
+The thumbnail URLs are passed verbatim to Swift, which does some translation inside a Swift plugin, checks whether it has a copy of the thumbnail, and then hits mediawiki if it doesn't have a copy.
+
+This logic would have to be extracted out of Swift into its own service sitting in front of it, then that service extended for new things. Adding to the existing Swift plugin or to VCL are both undesirable.",1457598852,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105088, @brion wrote:
+> Currently this requires either an extra HTTPS round-trip for the 'imageinfo' API
+
+What data is fetched and used before knowing what thumbnail to request? Original width? The API won't solve not knowing the original size. If it's a matter of always getting something back even when the original is smaller than the requested size, that's something that can be fixed now.",1457598485,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105138, @Tgr wrote:
+> IMO the two main questions here are:
+> # is this going to be supported by MediaWiki or just by some external service (or Varnish hack)?
+
+I think it would have to be supported by MediaWiki core (though as with many things, could be / will be in our usage enhanced by scary services/vasnish hacks). A default implementation could use a PHP endpoint similar to the existing img_auth.php and thumb.php
+
+> # is it going to support all image parameters or just some common subset?
+
+I think it would have to support all parameters that can affect the output image, otherwise you'd need to expose a second URL scheme for the actual generated thumbnails.
+
+> Some considerations:
+> * if we want to support all parameters, that should probably involve a new parameter specification/parsing interface for media handlers as the existing one is quite insane (basically just ""get full thumbnail name, read/write your parameters"" which in practice ends up in walking up the inheritance chain and throwing regexes at the string while trying to take the regexes used by all ancestors into account).
+
+Agreed it's pretty awful at present.
+
+
+>>! In T66214#2105146, @Tgr wrote:
+> Also, a 100% compatible VCL-layer mapping of nice URLs to old URL is just not gonna happen. For example the URL to a full-sized JPEG thumbnail is different depending on whether the JPEG has an EXIF rotation.
+
+I suspect this is another case where an initial mapping has to run through a service with some logic, similar to how not-yet-cached thumbnail URLs are routed through MW's thumb.php and friends the first time. Once the proper source file or internal redirect has been found it should be able to stay cached...
+
+(Might make sense to do the mapping the other way as well; letting accesses of the old URLs map to their new locations.)",1457566769,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Also, a 100% compatible VCL-layer mapping of nice URLs to old URL is just not gonna happen. For example the URL to a full-sized JPEG thumbnail is different depending on whether the JPEG has an EXIF rotation.",1457565227,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"IMO the two main questions here are:
+# is this going to be supported by MediaWiki or just by some external service (or Varnish hack)?
+# is it going to support all image parameters or just some common subset?
+
+Some considerations:
+* if the answer to #1 is no, the answer to #2 will be likewise, as MediaWiki extensions can add new thumbnail URL parameters.
+* if this ends up WMF-only, we will have to support old-style URLs forever in MediaWiki and all tools that want to remain usable outside of WMF wikis - not a happy prospect in my opinion.
+* if we end up not supporting all image parameters, then even WMF-specific tools might end up having to support both formats.
+* if we want to support all parameters, that should probably involve a new parameter specification/parsing interface for media handlers as the existing one is quite insane (basically just ""get full thumbnail name, read/write your parameters"" which in practice ends up in walking up the inheritance chain and throwing regexes at the string while trying to take the regexes used by all ancestors into account).",1457565105,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Quick note from IRC regarding the thumb-URL needs for mobile apps/web:
+
+The primary use case for mobile apps/web here is loading an appropriately-sized thumbnail of a given image as quickly as possible. Currently this requires either an extra HTTPS round-trip for the 'imageinfo' API, or rewriting the existing thumb URLs on the client and then working around the various edge cases (having to know that .svg thumbnails to .svg.png; handling failure cases when asking for a too-big size, knowing that very long filenames in thumbnail paths are sometimes rewritten to fit a length limit, etc). A cleaner, more consistent URL-based API will allow leaving the formatting and sizing questions to the server end.
+
+Secondary use case: local caching of those images is simplified if the caching properties of those thumbnail URLs are more predictable.
+
+Tertiary use case: there's a lot of use on mobile of squared-off images in lists/menus, and specially-cropped 'hero' images on articles. Having a cleaner thumb URL API should make it easier to extend it to move more of that cropping to the server-side, simplifying client code and reducing the amount of data transferred over mobile networks by pre-cropping unseen edges before download.
+",1457564647,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What's the caching strategy for this API? Will it simply redirect/proxy
+
+The most efficient option for introducing a thumb API is to rewrite requests in Varnish to directly map to the existing cached thumbs, thereby avoiding a duplication of cache entries. Given the simple URL structure, this should be relatively straightforward to do.
+
+As with any API design, we need to consider future needs carefully, while also avoiding to get stuck forever by worrying about unknown unknowns. We know that we have a concrete need to let clients select thumb sizes and optionally the quality in a sane and cacheable manner, and this RFC discusses possible solutions. I personally think that the present design is also reasonably future-proof, allowing a future use of content-negotiation for both the size and density if client-side selection doesn't end up dominating.
+
+@Gilles, do you have specific concerns or improvement ideas that you could share?",1457376174,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What's the caching strategy for this API? Will it simply redirect/proxy
+
+The most efficient option for introducing a thumb API is to rewrite requests in Varnish to directly map to the existing cached thumbs, thereby avoiding a duplication of cache entries. Given the simple URL structure, this is relatively straightforward to do.
+
+As with any API design, we need to consider future needs carefully, while also avoiding to get stuck forever by worrying about unknown unknowns. We know that we have a concrete need to let clients select thumb sizes and optionally the quality in a sane and cacheable manner, and this RFC discusses possible solutions. I personally think that the present design is also reasonably future-proof, allowing a future use of content-negotiation for both the size and density if client-side selection doesn't end up dominating.
+
+@Gilles, do you have specific concerns or improvement ideas that you could share?",1457376040,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What's the caching strategy for this API? Will it simply redirect/proxy
+
+The most efficient option for introducing a thumb API is to rewrite requests in Varnish to directly map to the existing cached thumbs, thereby avoiding a duplication of cache entries. Given the simple URL structure, this is relatively straightforward to do.
+
+As with any API design, we need to consider future needs carefully, while also avoiding to get stuck forever by worrying about unknown unknowns. We know that we have a concrete need to let clients select thumb sizes and optionally the quality in a sane and cacheable manner, and this RFC discusses possible solutions. I personally think that the present design is also reasonably future-proof, allowing a future use of content-negotiation for both the size and density if client-side selection doesn't end up dominating.
+
+@Gilles, do you have specific proposals for improving the API strawman?",1457375684,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"What's the caching strategy for this API? Will it simply redirect/proxy to the canonical thumbnail URL we already have? Or will it do caching of its own, essentially doubling the caching capacity requirements for thumbnails?
+
+What can a REST API for thumbnails do that HTTP and a URL scheme can't? In fact calling it REST API is a stretch, since we're only talking about GETs here. It's just a different URL scheme.
+
+This seems to me like a cleanup without a plan to address existing usage. There isn't much insight into how this should evolve with upcoming known technologies like client hints, let alone unforeseen needs. The reason why our current thumbnail URL scheme looks weird is because it was developed incrementally with no vision about future needs. Every time a new need appeared, some kind of parameter was added. And backward compatibility could never be broken, because our images are hotlinked. The approach here seems no different, in fact the only examples provided don't even address the existing options, only a small subset of features. If you only care about id, size and quality/format the existing URL scheme isn't that awkward to use.
+
+Explicit versioning looks nicer at a glance, but you run into the same problem of old version support and how it relates to client-side and server-side caching. And without a strategy for priming/migrating the caches for new formats, each version update would be extremely costly to deploy.
+
+I'm all for a comprehensive plan to rethink our thumbnail URL scheme, including all existing options, planning for future needs as well as addressing the issue of migration (considering that existing URLs will have to redirect to new ones forever). But I'm not seeing anything like that here, just an eagerness to create a new endpoint that's more to your liking and does less than the status quo, without careful consideration for operational consequences and homework required to do this right. As-is, this would be creating instant technical debt.
+
+I'll be at the meeting, but it'd be nice to have a draft spec to look at that addresses these issues by then.",1457356851,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We plan to discuss this in {E147}.  Based on the [2016-03-02 ArchCom meeting](https://www.mediawiki.org/wiki/Architecture_committee/2016-03-02) and what he said in T66214#2087161, I believe @GWicke hopes we can reach consensus on the format of a thumb API, possibly putting that aspect into last call.",1457323948,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Do you think we should do them in a particular order?
+
+From a user and API design perspective, I think the public thumb API is more urgent. It is also relatively easy to implement in a way that maps to our existing thumb caching & storage systems.
+
+Moving to content hashes will require more serious backend work, as well as a translation layer. @Gilles and @aaron are working on this, but my understanding is that content hashes are still some ways out.
+
+So, my proposal is to tackle the API first, and then move to hashes in a second step.",1457053254,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2087098, @GWicke wrote:
+> This task is really discussing two separate issues, which can be tackled in separate phases:
+> 
+> 1) Define a thumb API, which lets clients easily select thumb size and quality. Define the image identifier as an opaque string. Examples: `/thumb/{id}/{size}{/quality_format}`, value `/thumb/Wiki.png/640`.
+> 
+> 2) Switch from name-based identifiers to hash + selector based IDs. Example value: `/thumb/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/640`.
+
+Do you think we should do them in a particular order?",1457052610,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"This task is really discussing two separate issues, which can be tackled in separate phases:
+
+1) Define a thumb API, which lets clients easily select thumb size and quality. Define the image identifier as an opaque string. Examples: `/thumb/{id}/{size}{/quality_format}`, value `/thumb/Wiki.png/640`.
+
+2) Switch from name-based identifiers to hash + selector based IDs. Example value: `/thumb/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/640`.",1457052304,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Per T125865 and the [2016-02-10 ArchCom meeting](https://www.mediawiki.org/wiki/Architecture_committee/2016-02-10), I'm assigning this to @brion",1455241975,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@GWicke: how would you like to move forward on this?  This seems like a natural candidate for you to be the shepherd on per T125865, no?",1454988544,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The lack of a stable / simple thumb API is a serious issue for cacheable REST end points that contain a reference to a thumbnail, such as [the page summary end point](https://en.wikipedia.org/api/rest_v1/?doc#!/Page_content/get_page_summary_title), and an upcoming ""related pages"" end point.
+
+We (#services) would like to make progress on the API portion along the lines of the task summary soon, and are willing to implement this in a way that maps to existing thumbnail backends. If there are no objections I am going to push for this RFC to be discussed soon.",1454356431,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr, less sophisticated clients shouldn't need to select more than size and quality in any case, which both are easy enough to get right.",1450375965,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The new thumbnail api, at least on Wikimedia, needs to support one more parameter (`qlow`), as I've found in T119797#1839787, which complicates things, unless we discard it in favor of something else, like a dedicated domain, a different entry point, etc
+
+>>! In T119797#1839787, @tstarling wrote:
+> JPEG thumbnails already support a quality parameter ""qlow"", which was added to support zero, for example with Arcimboldo_Librarian_Stokholm.jpg:
+> 
+> * [[https://upload.wikimedia.org/wikipedia/commons/thumb/7/76/Arcimboldo_Librarian_Stokholm.jpg/200px-Arcimboldo_Librarian_Stokholm.jpg|200px standard quality: 14,618 bytes]]
+> * [[https://upload.wikimedia.org/wikipedia/commons/thumb/7/76/Arcimboldo_Librarian_Stokholm.jpg/qlow-200px-Arcimboldo_Librarian_Stokholm.jpg|200px low quality: 6,080 bytes]]
+
+",1450296093,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The new thumbnail api, at least on Wikimedia, needs to support one more parameter (`qlow`), as I've found in T119797#1839787, which complicates things, unless we discard it in favor of something else, a dedicated domain
+
+>>! In T119797#1839787, @tstarling wrote:
+> JPEG thumbnails already support a quality parameter ""qlow"", which was added to support zero, for example with Arcimboldo_Librarian_Stokholm.jpg:
+> 
+> * [[https://upload.wikimedia.org/wikipedia/commons/thumb/7/76/Arcimboldo_Librarian_Stokholm.jpg/200px-Arcimboldo_Librarian_Stokholm.jpg|200px standard quality: 14,618 bytes]]
+> * [[https://upload.wikimedia.org/wikipedia/commons/thumb/7/76/Arcimboldo_Librarian_Stokholm.jpg/qlow-200px-Arcimboldo_Librarian_Stokholm.jpg|200px low quality: 6,080 bytes]]
+
+",1450296048,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,I don't think there is much overlap between the people who use broken clients and those for whom performance matters to such an extent that an extra redirect becomes problematic.,1449967165,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> redirects are expensive
+
+Much more expensive is terminating once-valid URLs. Still looking for an answer to:
+
+>>! In T66214#1855231, @Nemo_bis wrote:
+> Yes, but content of an image can vary and so will the hash-based URL. Will every single hash-based URL keep working forever?
+
+To the benefit of the mass of MediaWiki users it would also be nice to explicitly know whether this feature will cater to:
+* wikis running on Windows, which naturally have issues with filenames (T3780, already in blocked tasks);
+* wikis for which it's too hard to set up a thumb handler with the current mechanism  (https://www.mediawiki.org/wiki/Manual:Thumb.php), ideally by making thumbnails fully work in vanilla MediaWiki (cf. {T58926}, {T27958}, {T67220}; things got better now with {T114098}).",1449916816,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Anomie, redirects are expensive, and are easy to overlook by broken clients. Failing fast & loudly makes sure that broken clients are fixed quickly, rather than creating a hidden performance regression. The number of advanced clients with a need to manipulate `hash_spec` should be very small in any case.",1449877971,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1867845, @GWicke wrote:
+> Requests with `hash_spec`s not conforming to this would be rejected as invalid by the API.
+
+That doesn't seem particularly user-friendly. Any reason not to 301 redirect to the canonical ordering instead of a 500?",1449758701,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients want to select the size and image quality, so we should make it extra easy to do so. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order and syntax. Requests with `hash_spec`s not conforming to this would be rejected as invalid by the API.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+Pages are already re-parsed when images referenced in them are re-uploaded. This is to make sure that image dimensions and other metadata is correct.
+
+> Why do you only want to support square bounding boxes?
+
+Of all the fixed bounding boxes, the square one has the advantage of offering reasonably-sized images independent of aspect ratio. It is also the typical choice in other APIs such as [flickrs](https://www.flickr.com/services/api/misc.urls.html).
+
+As mentioned earlier, most clients have access to the original image dimensions from an API response, or the data attributes in HTML. This means that they can select arbitrary image sizes for their application with some simple math, independent of the bounding box scheme used.",1449711267,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients want to select the size and image quality, so we should make it extra easy to do so. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order and syntax. Requests with `hash_spec`s not conforming to this would be rejected as invalid by the API.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+Pages are already re-parsed if images referenced in them are re-uploaded. This is to make sure that image dimensions and other metadata is correct.
+
+> Why do you only want to support square bounding boxes?
+
+Of all the fixed bounding boxes, the square one has the advantage of offering reasonably-sized images independent of aspect ratio. It is also the typical choice in other APIs such as [flickrs](https://www.flickr.com/services/api/misc.urls.html).
+
+As mentioned earlier, most clients have access to the original image dimensions from an API response, or the data attributes in HTML. This means that they can select arbitrary image sizes for their application with some simple math, independent of the bounding box scheme used.",1449711222,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients only care about the size and image quality, so we should make it easy to change that. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order and syntax. Requests with `hash_spec`s not conforming to this would be rejected as invalid by the API.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+Pages are already re-parsed if images referenced in them are re-uploaded. This is to make sure that image dimensions and other metadata is correct.
+
+> Why do you only want to support square bounding boxes?
+
+Of all the fixed bounding boxes, the square one has the advantage of offering reasonably-sized images independent of aspect ratio. It is also the typical choice in other APIs such as [flickrs](https://www.flickr.com/services/api/misc.urls.html).
+
+As mentioned earlier, most clients have access to the original image dimensions from an API response, or the data attributes in HTML. This means that they can select arbitrary image sizes for their application with some simple math, independent of the bounding box scheme used.",1449706667,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients only care about the size and image quality, so we should make it easy to change that. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order (like alphabetically). Other orders need to be rejected as invalid.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+Pages are already re-parsed if images referenced in them are re-uploaded. This is to make sure that image dimensions and other metadata is correct.",1449706043,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients only care about the size and image quality, so we should make it easy to change that. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order (like alphabetically). Other orders need to be rejected as invalid.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+This is already the case, as aspect ratios often change on re-upload.",1449705994,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients only care about the size and image quality, so we should make it easy to change that. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order (like alphabetically). Other orders need to be rejected as invalid.",1449705910,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@jhobs, @yurik: another one that may interact with https://github.com/wikimedia/mediawiki-extensions-ZeroBanner/blob/e21286bf61f454a106cea5b9c728247ae2dbbc0c/includes/PageRendering.php#L1104.
+
+Reading apps and web crew: this is probably for tracking, but it's worth tracking in case there are any assumptions (e.g., regexes) about URL format for media.
+
+This is a tentative Q3 goal per https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q3_Goals#Performance.",1449622217,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1862573, @Anomie wrote:
+> Why do you only want to support //square// bounding boxes? It doesn't seem particularly unlikely that a client has a rectangular bounding box to fill. If you only support square boxes, the client has to separately query the image's dimensions to decide what square bounding box to supply to the thumbnailer.
+
+I guess the client can get the dimensions when it requests the sha of the image. I mean, any particular client would already need to query the api to get the sha of the image to use it in the thumb URL",1449598035,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1854415, @GWicke wrote:
+> Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.
+
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;p=22/500`: 500px thumb of page 22 in a multi-page document.
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;t=2m30s/220`: Thumb of a video at 2m30s.
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;lang=fr/220`: Thumb of an SVG, rendered to a PNG using French texts.
+
+What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+>>! In T66214#1855231, @Nemo_bis wrote:
+>>>! In T66214#1854334, @ori wrote:
+>>>>! In T66214#1854329, @Nemo_bis wrote:
+>>> How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.
+>> 
+>> There would be a mapping of old URLs to content-based URLs, which we'd just keep around forever.
+> 
+> Yes, but content of an image can vary and so will the hash-based URL. Will every single hash-based URL keep working forever?
+
+It appears that the hash-based URL would always be a permalink to the version of the image at the time. To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version. In other words, it would be the equivalent of all page links including ""?oldid=12345"".
+
+>>! In T66214#1856662, @GWicke wrote:
+> @ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail.
+
+OTOH, that doesn't mean that two different URLs cannot have the same content if the semantic intent of the thumbnail differs. For example, if a video is at 1 frame per second, t=1s and t=1.5s are semantically different but in practice identical.
+
+BTW, I note in your proposed scheme, it's either easily possible to specify `t=2m30s` and `t=150s`, or else it stupidly throws an error for the latter, or else it 301 redirects one to the other and you forgot to mention that.
+
+> The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+Why do you only want to support //square// bounding boxes? It doesn't seem particularly unlikely that a client has a rectangular bounding box to fill. If you only support square boxes, the client has to separately query the image's dimensions to decide what square bounding box to supply to the thumbnailer.
+
+If you really want one canonical URL and are willing to expend network round-trips to achieve it, the thumbnailer could easily enough redirect `size=200`, `size=200x300`, and `size=266x150` to the canonical `size=200x150` for a 1024×768 image.
+
+> I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351.
+
+I note that that change was actually tried and then reverted, and T351#1649303 has some analysis proposing more flexibility for that feature.",1449595454,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1854415, @GWicke wrote:
+> Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.
+
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;p=22/500`: 500px thumb of page 22 in a multi-page document.
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;t=2m30s/220`: Thumb of a video at 2m30s.
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;lang=fr/220`: Thumb of an SVG, rendered to a PNG using French texts.
+
+What if you have a format that supports both animated/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+>>! In T66214#1855231, @Nemo_bis wrote:
+>>>! In T66214#1854334, @ori wrote:
+>>>>! In T66214#1854329, @Nemo_bis wrote:
+>>> How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.
+>> 
+>> There would be a mapping of old URLs to content-based URLs, which we'd just keep around forever.
+> 
+> Yes, but content of an image can vary and so will the hash-based URL. Will every single hash-based URL keep working forever?
+
+It appears that the hash-based URL would always be a permalink to the version of the image at the time. To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version. In other words, it would be the equivalent of all page links including ""?oldid=12345"".
+
+>>! In T66214#1856662, @GWicke wrote:
+> @ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail.
+
+OTOH, that doesn't mean that two different URLs cannot have the same content if the semantic intent of the thumbnail differs. For example, if a video is at 1 frame per second, t=1s and t=1.5s are semantically different but in practice identical.
+
+BTW, I note in your proposed scheme, it's either easily possible to specify `t=2m30s` and `t=150s`, or else it stupidly throws an error for the latter, or else it 301 redirects one to the other and you forgot to mention that.
+
+> The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+Why do you only want to support //square// bounding boxes? It doesn't seem particularly unlikely that a client has a rectangular bounding box to fill. If you only support square boxes, the client has to separately query the image's dimensions to decide what square bounding box to supply to the thumbnailer.
+
+If you really want one canonical URL and are willing to expend network round-trips to achieve it, the thumbnailer could easily enough redirect `size=200`, `size=200x300`, and `size=266x150` to the canonical `size=200x150` for a 1024×768 image.
+
+> I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351.
+
+I note that that change was actually tried and then reverted, and T351#1649303 has some analysis proposing more flexibility for that feature.",1449594481,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Thanks @GWicke for your thorough explanation. I was wondering why not pick the same semantics as wikitext, but it makes sense to use bounding box dimensions for the api.",1449433773,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leave the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the growing popularity of the 16:9 aspect ratio, as thumbs for 16:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limit shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussed here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449434560,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leave the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the growing popularity of the 16:9 aspect ratio, as thumbs for 16:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limits shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussed here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449434527,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leave the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the 16:9 aspect ratio, as thumbs for 19:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limits shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussed here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449434388,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leaves the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the 16:9 aspect ratio, as thumbs for 19:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limits shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussed here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449427223,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leaves the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the 16:9 aspect ratio, as thumbs for 19:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limits shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussion here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449427104,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"this would effectively make 2 identical files with different name to get the same URL in this scenario. That's pretty good.
+
+As for the size parameter, it's the width of the bounding box (with variable height depending on the dimensions of the image) or just a maximum width and height?. I'd expect the first, since that will provide room for, at a later date, extend it to specify height only (`/x150`) or maximum width and height (`/200x150`), following the current thumbnail syntax in wikitext.",1449316697,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1854334, @ori wrote:
+>>>! In T66214#1854329, @Nemo_bis wrote:
+>> How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.
+> 
+> There would be a mapping of old URLs to content-based URLs, which we'd just keep around forever.
+
+Yes, but content of an image can vary and so will the hash-based URL. Will every single hash-based URL keep working forever?",1449306683,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449273780,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion (especially T66214#1743371), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449273721,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449273684,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449273650,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion, @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449272794,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1854329, @Nemo_bis wrote:
+> How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.
+
+There would be a mapping of old URLs to content-based URLs, which we'd just keep around forever.",1449271319,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.",1449271147,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"This doesn't really **block** T89971, but if the sort of thing being discussed here happens then one of the more nebulous bits of that (fixing iiurlwidth/iiurlheight/iiurlparam into something multi-valued but still sane) would just go away since we could just point to the ""/api/rest_v1/media/img/{original-sha1}"" bit and let the client fill in the width/height/page/seek-time/language/etc. when it talks to that endpoint.
+
+But that, of course, depends on (1) someone actually working on this any time soon and (2) the end result actually existing for all MediaWiki installations and not just as an optional bespoke service like too many things seem to be planned as these days.",1448997067,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,,1447900314,PHID-USER-tjyfydvd4ncrfvvr6mkr,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,,1447899356,PHID-USER-tjyfydvd4ncrfvvr6mkr,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,T117082 is an example for how better support for client-side thumb size selection would simplify the API design for end points like page previews.,1447088584,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Imageinfo responses are perfectly cacheable (apart from invalidation when the file changes, but that's a generic problem with the action API (or, rather, with varnish) and not easy to solve). That said, they are a distraction. Most of the time, clients want the image, not information about the image. IIRC when we were writing MediaViewer, using the API to fetch image URLs would have been a 200ms delay for the median user. I'm sure it's much less after the HHVM switch but even cutting down a few dozen ms is a win.",1446621369,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We recently considered making imageinfo responses cacheable in T116840, but in a subsequent discussion @tstarling made good points about the current response & associated APIs not facilitating client-side decisions on dimensions, format or quality. There are a lot of irregularities around multi-page images, vector and video formats etc that are currently left to the client to figure out, and all this is ignoring that our thumb urls are not considered a public API.
+
+To address the need for more client-side control over thumb parameters, as well as improved caching of image metadata responses, it seems that we'll need to address the thumb URL as API question raised in the discussion on this task. The move to content-based addressing seems to provide a good opportunity to do this.",1446599988,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion: In your distinction, the 'author-supplied' parameters are all closely related to selecting the base image for a thumb. I wonder if we could leverage a syntax similar to section identifiers for this:
+
+- `p=20` for page selection
+- `t=20` for time offset selection (following the HTML5 temporal fragment standard)
+- `lang=en` for the language
+
+Example URL, using `;` as delimiter: `/api/rest_v1/media/img/90edff310ba1420a7b6e2e5f49a0820c96450a35;t=20/{size}`
+
+Instead of using the width, we could also consider interpreting the size parameter as a square bounding box. This would be more useful for preview applications where the image has to fit in a limited space, and would still support retrieval of exact widths / heights if the client has information about the original dimension and thus the aspect ratio. This is for example true for Parsoid HTML, which provides the original dimensions in data attributes.
+ 
+> With sizes we also have the question of whether to again support every size under the sun or specific size steps. 
+
+We have discussed limiting thumb sizes a couple of times before, without a clear consensus. I don't think that this is necessarily an issue for the API, though. If we determine that client-side re-scaling quality is acceptable, we can start to return approximate (rounded) thumbs in response to requests for odd numbers later.
+
+> Video derivatives are produced at specific size steps... but per video convention, based on a max height, not a specific width. If this is an API, then either we need to accept any input parameter and return a sensible file, or clients have to know what the acceptable set of sizes they can specify is.
+
+I think it makes sense to focus on the thumb use case first, as the considerations for video are quite different. For example, we might want to move to manifest files for adaptive streaming with MPEG-DASH (see T44591), which could again be stored using the original video file's hash.",1445555854,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion: In your distinction, the 'author-supplied' parameters are all closely related to selecting the base image for a thumb. I wonder if we could leverage a syntax similar to section identifiers for this:
+
+- `p=20` for page selection
+- `t=20` for time offset selection (following the HTML5 temporal fragment standard)
+- `lang=en` for the language
+
+Example URL, using `;` as delimiter: `/api/rest_v1/media/img/90edff310ba1420a7b6e2e5f49a0820c96450a35;t=20/{size}`
+
+Instead of using the width, we could also consider interpreting the size parameter as a square bounding box. This would be more useful for preview applications where the image has to fit in a limited space, and would still support retrieval of exact widths / heights if the client has information about the original dimension and thus the aspect ratio. This is for example true for Parsoid HTML, which provides the original dimensions in data attributes.
+ 
+> With sizes we also have the question of whether to again support every size under the sun or specific size steps. 
+
+We have discussed limiting thumb sizes a couple of times before, without a clear consensus. I don't think that this is necessarily an issue for the API, though. If we determine that client-side re-scaling quality is acceptable, we can start to return approximate (rounded) thumbs in response to requests for odd numbers later.
+
+> Video derivatives are produced at specific size steps... but per video convention, based on a max height, not a specific width. If this is an API, then either we need to accept any input parameter and return a sensible file, or clients have to know what the acceptable set of sizes they can specify is.
+
+I think it makes sense to focus on the thumb use case first, as the considerations for video are quite different. For example, we might want to move to manifest files for adaptive streaming with MPEG-DASH, which could again be stored using the original video file's hash.",1445555824,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion: In your distinction, the 'author-supplied' parameters are all closely related to selecting the base image for a thumb. I wonder if we could leverage a syntax similar to section identifiers for this:
+
+- `p=20` for page selection
+- `t=20` for time offset selection (following the HTML5 temporal fragment standard)
+- `lang=en` for the language
+
+Example URL, using `;` as delimiter: `/api/rest_v1/media/img/90edff310ba1420a7b6e2e5f49a0820c96450a35;t=20/{size}`
+
+Instead of using the width, we could also consider interpreting the size parameter as a square bounding box. This would be more useful for preview applications where the image has to fit in a limited space, and would still support retrieval of exact widths / heights if the client has information about the original dimension and thus the aspect ratio.
+ 
+> With sizes we also have the question of whether to again support every size under the sun or specific size steps. 
+
+We have discussed limiting thumb sizes a couple of times before, without a clear consensus. I don't think that this is necessarily an issue for the API, though. If we determine that client-side re-scaling quality is acceptable, we can start to return approximate (rounded) thumbs in response to requests for odd numbers later.
+
+> Video derivatives are produced at specific size steps... but per video convention, based on a max height, not a specific width. If this is an API, then either we need to accept any input parameter and return a sensible file, or clients have to know what the acceptable set of sizes they can specify is.
+
+I think it makes sense to focus on the thumb use case first, as the considerations for video are quite different. For example, we might want to move to manifest files for adaptive streaming with MPEG-DASH, which could again be stored using the original video file's hash.",1445555714,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"It probably makes sense to conceptually separate the params into author-supplied and client-selectable portions:
+
+Author-supplied:
+* page (if relevant - PDF/DjVu/TIFF)
+* seek time (if relevant - WebM/Ogg)
+* text rendering language (if relevant - localizable SVGs)
+
+Client-selectable:
+* target size (width and/or height?)
+* output format (potential to override default .png/.jpg output with .webp or other formats in future)
+
+With sizes we also have the question of whether to again support every size under the sun or specific size steps. Video derivatives are produced at specific size steps... but per video convention, based on a max height, not a specific width. If this is an API, then either we need to accept any input parameter and return a sensible file, or clients have to know what the acceptable set of sizes they can specify is.
+
+Ditto with output formats -- if we support only .png for SVG rasterization, but either .png or .jpg (or .png or .jpg or .webp someday?) as options for PDF .... how does the client know which to safely select from?",1445462229,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion, that is indeed a long list of optional parameters, and will require some thinking to accommodate in a clean and cacheable API. 
+
+Generally, I think the APIs we are defining for media are public in any case; cached and stored content relies on those APIs being reasonably stable. It's worth using an opportunity like the move to content-addressable media to clean them up.",1445455846,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We know we already have parameters for width (base images), page (SVG, PDF, etc), thumbtime (TimedMediaHandler), and language (SVG). Custom handlers, or additional extensions, could add more.
+
+Additionally we have the format conversions, where we currently add a second extension ('.svg.png', '.djvu.jpg', whatever); we may want to add additional output formats such as .webp.
+
+Further, we have derivative files for TimedMediaHandler -- transcodes to various output formats at various bitrates and resolutions, which are currently stashed in similar infrastructure to the thumbnail images but not in the same place.
+
+So if we're going to make those URLs predictable instead of extensible, we need to at least cover all that territory...?",1445454392,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@GWicke +1, having a RESTful interface for requesting thumbnails would be nice.  Your suggestion, however, assumes prior knowledge of the ""prefix,"" which might not always be at hand.  IMHO, ideally, the interface would only require clients to specify the filename/hash/identifier and (optionally) desired width.  That way clients can:
+
+- Prevent automatic downloads of images—even when offscreen
+- Have more control over image thumbnails that are downloaded, which allows for: 
+  - taking advantage of high-bandwidth, high DPI situations
+  - requesting lower-res thumbnails initially in case the user is on a slow connection
+  - rendering images at the width of the device w/o scaling artifacts",1445454380,PHID-USER-6vqtwycrvuonr2xo7bqi,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format, page, ...), so having the width and other parameters in a deterministic and easy-to-parse / replace location would be useful.
+
+Strawman url for a basic thumb: `/api/rest_v1/media/img/{original-sha1}/{width}`
+
+Edit: Modified strawman URL to clarify that the 'prefix' is a path to a stable API entry point.",1445455175,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format, page, ...), so having the width and other parameters in a deterministic and easy-to-parse / replace location would be useful.
+
+Strawman url: `/api/rest_v1/media/img/{original-sha1}/{width}`
+
+Edit: Modified strawman URL to clarify that the 'prefix' is a path to a stable API entry point.",1445455030,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format), so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/api/rest_v1/media/img/{original-sha1}/{width}`
+
+Edit: Modified strawman URL to clarify that the 'prefix' is a path to a stable API entry point.",1445454498,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format), so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/api/rest_v1/media/img/{original-sha1}/{width}`",1445454464,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format), so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/prefix/{original-sha1}/{width}`",1445454383,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb width, so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/prefix/{original-sha1}/{width}`",1445454095,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure. Clients might want to rewrite the thumb width, so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/prefix/{original-sha1}/{width}`",1445453909,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure. Clients might want to rewrite the thumb width, so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Example url: `/prefix/{original-sha1}/{width}`",1445453876,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Subfader, in Parsoid HTML [the image name is already provided in an RDFa `resource` attribute](https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images). @Prtksxna is also [working on](https://gerrit.wikimedia.org/r/#/c/196532/) bringing the PHP thumb HTML structure closer to the Parsoid output. We should make sure to include the resource attribute there as well.",1433361426,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Subfader, in Parsoid HTML [the image name is already provided in an RDFa `resource` attribute](https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images). There is also [work by @Prtksxna ongoing](https://gerrit.wikimedia.org/r/#/c/196532/) to bring the PHP thumb HTML structure closer to the Parsoid output. We should make sure to include the resource attribute there as well.",1433361384,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Subfader, in Parsoid HTML [the image name is already provided in an RDFa `resource` attribute](https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images). There is also [work ongoing](https://gerrit.wikimedia.org/r/#/c/196532/) to bring the PHP thumb HTML structure closer to the Parsoid output. We should make sure to include the resource attribute there as well.",1433361343,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Some JS scripts in extensions rely on the image name as they grab it from the src-URL to pass it to the API or thumb.php.
+
+So if this comes, please make sure to provide the proper image name in a data parameter at least.
+",1420023336,PHID-USER-qjb2hbe663dhrrpskylp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Some JS scripts in extensions rely on the image name as they grab it to pass it to the API or thumb.php.
+
+So if this comes, please make sure to provide the proper image name in a data parameter at least.
+",1420023314,PHID-USER-qjb2hbe663dhrrpskylp,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,See also T1210.,1419899961,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"(In reply to Tisza Gergő from comment #1)
+> By content-based thumbnail URL do you mean the URL is based on the content
+> of the thumbnail, or on the content of the original file? 
+
+Definitely the latter. Example: <sha1 of orig>-300.jpg",1398181397,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"(In reply to Bawolff (Brian Wolff) from comment #2)
+> I believe there is already a bug for this, but cant find it.
+
+Bug 44428 comment 0?",1398149823,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We already have support for content disposition headers on files (for swift backend anyways). I imagine we could still use htcp for quick purging.
+
+There are very definite advantages here related to caching. Among other things, It would also let us set more aggresive cache headers for the client.
+
+File moving would also become much ""better"".
+
+I believe there is already a bug for this, but cant find it.",1398144820,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"By content-based thumbnail URL do you mean the URL is based on the content of the thumbnail, or on the content of the original file? None of the advantages seem to apply to the former, it makes quick purging even harder, and makes it impossible to guess the URL needed for resizing the image (which can be used for some fairly significant speed improvements).",1398128071,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+VisualEditor: Don't bind the 'v' accesskey for VisualEditor in namespaces where VE is not enabled,"Visual editor adds accesskey 'v' for visual edit in namespaces where the editor is not enabled. For example (in Firefox) pressing alt+shift+v in [[sv:Diskussion:Stockholm]] shows the error message:
+
+""Error loading data from server: novenamespace: VisualEditor is not enabled in namespace 1. Would you like to retry?""
+
+It should be possible to avoid getting an error message by removing the access key. (Also, if Visual editor is not enabled there is no point in asking users to retry.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1397938920,PHID-USER-axibsactcdotqkfh3mfe,PHID-TASK-fe5hswi3ghhljkcsvvmj,task_description,resolved
+VisualEditor: Don't bind the 'v' accesskey for VisualEditor in namespaces where VE is not enabled,"Change 133851 merged by jenkins-bot:
+Remove edit tab from the DOM if it's hidden
+
+https://gerrit.wikimedia.org/r/133851",1400521877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fe5hswi3ghhljkcsvvmj,task_subcomment,NA
+VisualEditor: Don't bind the 'v' accesskey for VisualEditor in namespaces where VE is not enabled,"Change 133851 had a related patch set uploaded by Alex Monk:
+Don't add ve-edit tab in namespaces where it's not available
+
+https://gerrit.wikimedia.org/r/133851",1400279284,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fe5hswi3ghhljkcsvvmj,task_subcomment,NA
+VisualEditor extension on AffCom wiki,"**Author:** `admin`
+
+**Description:**
+Greetings,
+Please add the VisualEditor extension - and any related elements - to the AffCom wiki (chapcom.wikimedia.org).
+
+Thank you!
+-greg aka varnent
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1397915580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ff5dovr2nj7hbi4mfk6d,task_description,resolved
+VisualEditor extension on AffCom wiki,Looks like that would've been done in https://gerrit.wikimedia.org/r/#/c/174793/ - sorry this bug was missed.,1433071229,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ff5dovr2nj7hbi4mfk6d,task_subcomment,NA
+VisualEditor extension on AffCom wiki,Looks like that would've been done in https://gerrit.wikimedia.org/r/#/c/174793/ - sorry it was missed.,1433071217,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ff5dovr2nj7hbi4mfk6d,task_subcomment,NA
+VisualEditor extension on AffCom wiki,"**admin** wrote:
+
+Whoops - sorry - meant to close a different one - my bad.  :/",1398701272,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ff5dovr2nj7hbi4mfk6d,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"Div tags like the ones seen in https://meta.wikimedia.org/wiki/Grants:IdeaLab cause ""alienated content""/prevent people from editing the page.  VisualEditor should support div tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397572320,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rvzy7u46557pyglomvpy,task_description,open
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,Filed {T139388},1467737899,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"This is definitely not new, but this looks like a Parsoid problem with the selective serializer. I think the bug is different from the request in the title of the page. The bug here is that if you edit the content of a div that has a templated style, the edits are being lost. This is a bug with the DOM diff algorithm which probably is mistakenly ignoring edits in nodes marked mw:ExpandedAttrs (as far as I can tell), and has been around since the very beginning. I'll open a new bug report for this and let this task be for the original request (which is allowing edits of <div>s with templated attributes).",1467737626,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,I can confirm this problem exists at least for some months. ,1466673250,PHID-USER-bdyms27sdtgdvjm7zfz4,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"Eurgh, that's not good. Was there a Parsoid change recently-ish, or is it breakage at our end?",1466672862,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"Confirmed, this now silently fails to save your edits, which is VERY confusing for an end user.",1466672573,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"Unfortunately, it seems this has regressed from 'cannot edit' to 'can edit, but changes do not show up'. Could the priority be increased to reflect that?",1460920415,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"<div> tags work just fine, and have for nearly a year. The problem here is a <div> tag with a template in its style attribute.",1397587517,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+"VisualEditor: Existing non-positional metas (like categories) get wrapped in format changes, but new ones get appended in a terminal paragraph","Steps to reproduce:
+* go to https://test.wikipedia.org/wiki/Page466?veaction=edit
+* select the whole article content (Ctrl + A)
+* from the format menu, select one of the options (except ""Paragraph"")
+* go to ""Save page"" > ""Review your changes""
+
+No matter if you selected ""Heading"", ""Preformatted"" or something else, all existing categories would get that format. So one can accidentally put a category in a header.
+
+However, if you add one or more categories in VE using the dedicated menu, then (without saving) repeat those steps, you will see that the newly added categories are left out of the formatting change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://test.wikipedia.org/w/index.php?diff=197978",1397524380,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r2gtjg6dw22voeqzade6,task_description,open
+"VisualEditor: Existing non-positional metas (like categories) get wrapped in format changes, but new ones get appended in a terminal paragraph",Any updates?,1414263222,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r2gtjg6dw22voeqzade6,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,"I edited https://www.mediawiki.org/w/index.php?title=MediaWiki-Vagrant&oldid=946962 with VisualEditor.  Everything after the ""Quick Start"" section appeared in monospace.
+
+I repro'd with the smaller test page https://www.mediawiki.org/wiki/User:S_Page_(WMF)/VE_span_bug
+
+I think the issue lies in
+
+ <p style=""font-size: 1.2em; margin-top: 1.2em;"">When Vagrant is done configuring your machine, browse to <span class=plainlinks>http://127.0.0.1:8080/</span> to find your MediaWiki instance. The admin password is <code>vagrant<code>.</span>
+
+Note its incorrect second opening <code> instead of closing the code, and a second closing </span>. Yet regular wiki parsing can handle it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:S_Page_(WMF)/VE_span_bug",1396988880,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-4tie5um47m54nxlowc4v,task_description,declined
+Parsoid and Tidy differ in how they deal with misnested tags,Tidy is on the way to being removed next year. Parsoid and RemexHTML will handle broken HTML markup much more similarly since they both using HTML5 tree building to fix up broken markup.,1513635415,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,">>! In T65699#1694336, @MarkAHershberger wrote:
+> fwiw, one of the people behind tidy-html5 says [[ https://github.com/htacg/tidy-html5/issues/277#issuecomment-144808830 |  he tested ]]  and found that this issue was fixed.
+
+Thanks @MarkAHershberger. What we are getting at with the Tidy replacement and which applies here as well is that we really don't need Tidying or any such thing in mediawiki. What we need is a HTML5 parser (something that takes a string and parses it according to the well-specified HTML5 parsing algorithm). 
+
+We don't need all the extra things that the old Tidy did. So, if the new tidy-html5 project implemented what we needed, it would simply be a HTML5 tree builder that takes a string, and builds a DOM. If we needed (for backward compatibility reasons) to implement additional post-processing on the DOM (to do some of the things the old/in-production Tidy does), then we would need a full DOM API. But, if we determine as part of the work in T89331 that we can drop all the extra things the old Tidy does, then we may be able to not bother with the DOM API, as long as the tool generated a faithful serialization of the parsed DOM tree.
+
+T89331 does not mandate an external HTML5 parsing service. If we determine that tidy-html5 is ""good enough"", then, it would be an acceptable fallback for mediawiki installations that are happy with it. In fact, wikis don't even need to replace the ""old tidy"" if they don't care about all the bugs filed against it. Part of the impetus to T89331 is to pay down technical debt. It also moves PHP parser and Parsoid output closer. It also brings us closer to reducing complexity in Parsoid, and eventually in the glorious future, to maybe have a simple bidirectional parser entirely in core without need for an external service. We can chat more on IRC if you have more questions. I didn't add this explanation to T89331 since that ticket is already very long with a lot of discussion.",1443739513,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,"fwiw, one of the people behind tidy-html5 says [[ https://github.com/htacg/tidy-html5/issues/277#issuecomment-144808830 |  he tested ]]  and found that this issue was fixed.",1443724777,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,*** Bug 63798 has been marked as a duplicate of this bug. ***,1399417330,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,"(In reply to spage from comment #0)
+ 
+> Note its incorrect second opening <code> instead of closing the code, and a
+> second closing </span>. Yet regular wiki parsing can handle it.
+
+This is Tidy doing the cleanup. PHP parser does not do the fixup automatically. This is a known issue -- we have a bunch of these scenarios now where Parsoid and Tidy fixup broken code differently. We'll never match Tidy behavior (which is not always the desired behavior in any case). But, as for this specific scenario, fixing this will require us to use heuristics in the tokenizer and more complexity. At this time, it is not clear if the additional complexity is worth it, except for easy to auto-fix scenarios.",1396990520,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+"VisualEditor: Fatal ""SCRIPT16389: Unspecified error"" error in IE9","Turning on debugging in IE9 and then hitting ""Edit"" ends up with this in the console:
+
+  SCRIPT16389: Unspecified error. 
+  load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-
+  vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&
+  version=20140408T180250Z&*, line 642 character 159
+
+
+The line that is highlighted (running with ""Format JavaScript"" checked) is:
+
+  this.nativeSelection.addRange(getNativeRange(range).cloneRange());
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396985820,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-deyxxgilo6bu43xrinwb,task_description,resolved
+"VisualEditor: Fatal ""SCRIPT16389: Unspecified error"" error in IE9","IE9 loads fine now, just not in debug mode.",1461148432,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-deyxxgilo6bu43xrinwb,task_subcomment,NA
+VisualEditor: Newly inserted inline templates do not take annotations from the surrounding text,"When adding templates such as https://fr.wikipedia.org/wiki/Mod%C3%A8le:E (which adds a superscripted ""e"" to words), the letter will need further formatting to match the surrounding text if that is italic, bold, ... .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396954980,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2scgn55flrrhzwl72ldr,task_description,open
+VisualEditor: Newly inserted inline templates do not take annotations from the surrounding text,Related: T140919,1579043632,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2scgn55flrrhzwl72ldr,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","1. Log in at http://en.wikipedia.beta.wmflabs.org
+2. Enable VE
+3. Visit http://en.wikipedia.beta.wmflabs.org/wiki/File:ButtonsReversed.png
+   (or any foreign file with no local description page)
+
+You see the following views (tabs):
+    Read
+    View on Wikimedia Commons
+    Create source
+    Add local description ^beta
+
+4. Visit http://en.wikipedia.beta.wmflabs.org/wiki/File:Button_hover.svg
+   (or any foreign file with an existing local description page)
+
+You see:
+    Read
+    View on Wikimedia Commons
+    Edit source
+    Edit local description ^beta
+    View history
+
+The tab name ""Create/Edit source"" does not sit well next to ""Add/Edit local description ^beta"". The wikitext-editing tab needs a better name when viewing foreign files.
+
+Admittedly these tabs were altered in core [1] without consulting the VE people, but of course, it is the responsibility of extension authors to catch up to new core functionality.
+
+[1] Gerrit change 104182
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396949940,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-elatzf7sipmoeh7h3gfm,task_description,resolved
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","Change 124775 merged by jenkins-bot:
+Use updated tab labels on description pages for files in foreign repos
+
+https://gerrit.wikimedia.org/r/124775",1397243472,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","Change 124775 had a related patch set uploaded by Alex Monk:
+Use updated tab labels on description pages for files in foreign repos
+
+https://gerrit.wikimedia.org/r/124775",1396998747,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","(In reply to Alex Monk from comment #2)
+> So ""Edit source"" or ""Create source"" should become ""Edit local description
+> source"" or ""Add local description source"" on file description pages for
+> files in foreign repositories?
+
+I guess. It's verbose, but then that's really my fault...",1396993688,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","So ""Edit source"" or ""Create source"" should become ""Edit local description source"" or ""Add local description source"" on file description pages for files in foreign repositories?",1396985463,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","Sorry that we missed this.
+
+BTW, changes to major MediaWiki semantics (even good ones like this) should really be highlighted on wikitech-l and/or ideally design-l before being implemented and merged. I have a bunch of ideas about how this could have been done more cleanly that it's now too late to try out. :-(",1396980948,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics","This is related to bug 50996.
+
+Open a page that contains hieroglyphics, like https://www.mediawiki.org/w/index.php?oldid=942532#Hieroglyphics
+
+You should be able to open the hieroglyphics ""node"" by double-clicking, but it isn't working.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396903680,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_description,resolved
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics",Verified the fix in test2,1397513626,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics",Verified the fix on betalabs,1397074560,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics","Change 124469 merged by jenkins-bot:
+Actually actually fix double-clicking on hieroglyphics nodes
+
+https://gerrit.wikimedia.org/r/124469",1396985397,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics","Change 124469 had a related patch set uploaded by Catrope:
+Actually actually fix double-clicking on hieroglyphics nodes
+
+https://gerrit.wikimedia.org/r/124469",1396907151,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics",https://gerrit.wikimedia.org/r/#/c/121514/,1396903898,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics","I think Trevor fixed this in an unrelated recent commit, let me find it.",1396903815,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"**Author:** `richlv`
+
+**Description:**
+visual editor from git f8d56e6804a12248b485c2d3b49d4ff0ffa7220c
+
+edit a page with opera 12.16 on linux, place cursor on an empty line, hit 'esc' - 
+symbol ♙ is inserted.
+
+bug #51140 was about this symbol being inserted in a different situation and is supposed to be fixed.
+
+reproducible at https://www.zabbix.org/wiki/Docs/visual_editor_test (if you would like to create a test account, ""real name"" is mandatory)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396884180,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lyauywwlebuzz4wjazr5,task_description,resolved
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"Change 143322 merged by jenkins-bot:
+ve.ce.Surface: Prevent incorrect pawning in Opera 12
+
+https://gerrit.wikimedia.org/r/143322",1404371327,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"Change 143322 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ce.Surface: Prevent incorrect pawning in Opera 12
+
+https://gerrit.wikimedia.org/r/143322",1404225651,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,Seems like it wouldn't be a problem if you just filtered out those keycodes.,1404210279,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"This is probably a regression from 4e377629e39a4af9405a5ea8972bdeb1af37ddf6
+(fix for bug 48335).",1399670246,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"So, Opera 12 sends the events for the keypresses of Esc and Tab. These events reach ve.ce.Surface.prototype.onDocumentKeyPress and eventually ve.ce.Surface.prototype.handleInsertion, which decides to insert the pawn, which will not be overwritten because neither Esc not Tab produce any text.
+
+onDocumentKeyPress attempts to filter out non-character keypresses by discarding ones where the charCode is 0; Opera's event for Esc has charCode == 27,
+for Tab charCode == 9. I guess other browsers use 0 here for some weird reason and you depend on this behavior.",1399669752,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"Yes. I don't have time right now, but I'll try to get around to this sooner or later.",1398188177,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"MatmaRex, you still interested in taking on Opera 12 bugs?",1396922428,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"**richlv** wrote:
+
+(1) another way to get that symbol with opera - hit 'tab' on an empty line.
+
+both of these also ""work"" in an empty table cell",1396892008,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,"Both enwiki and frwiki (at least) use {{FULLPAGENAME}} in [[MediaWiki:newarticletext]], which is unusable, because it is replaced by “API” in VisualEditor.
+
+So the warnings contain texts like
+ — “You can also start your new article at Special:Mypage/API.” (https://en.wikipedia.org/wiki/Nawak?veaction=edit)
+ — “Comment faire pour créer l'article API ?” (https://fr.wikipedia.org/wiki/Nawak?veaction=edit)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59608",1396819500,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_description,resolved
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,*** Bug 63673 has been marked as a duplicate of this bug. ***,1402295035,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,"Change 127388 merged by jenkins-bot:
+Set context title when rendering edit notices and checkboxes
+
+https://gerrit.wikimedia.org/r/127388",1397879339,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,*** Bug 63811 has been marked as a duplicate of this bug. ***,1397866699,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,"Change 127388 had a related patch set uploaded by Catrope:
+Set context title when rendering edit notices
+
+https://gerrit.wikimedia.org/r/127388",1397866440,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,Presumably we're not passing the 'title' parameter to the URL to give it context?,1396887988,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,*** Bug 63631 has been marked as a duplicate of this bug. ***,1396887928,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"Some icons need to be flipped for RTL languages. Here's what I found till now:
+
+In lib/ve/lib/oojs-ui/images/icons:
+* help.svg - This is a question mark in a circle. This should be flipped for all RTL languages, but *not* for Hebrew (he) and Yiddish (yi).
+
+In lib/ve/modules/ve/ui/styles/images/icons:
+* external-link.svg
+
+In modules/ve-mw/ui/styles/images/icons:
+* gallery.svg
+* parameter.svg
+* parameter-set.svg
+* ref-cite-book.svg
+* ref-cite-journal.svg
+* ref-cite-news.svg
+* reference.svg
+* references.svg
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396793460,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-aulut6cxxmdw4srpyjpu,task_description,resolved
+VisualEditor: Some icons need to be flipped for RTL languages,"Except for the remaining technical issue in OOjs UI, this was done 6 months ago. Closing, and follow-up for OOUI is in T76540.",1417566229,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to Ed Sanders from comment #4)
+> (In reply to James Forrester from comment #3)
+> > No; OOUI only understands RTL and LTR, not specific languages. The bold icon
+> > isn't from OOUI but from VE itself, which does. Oy.
+> 
+> Actually the per-language icon format is in OOUI (IconedElement.js line 42).
+> You need to define the language overrides every time you specify the icon
+> instead of just making it a 'feature' of the icon like directionality.
+
+Oh, interesting. OK, so we'd need to use that in downstream tools if particular languages want over-rides? Ick. See gerrit 143407 for the easy part.",1404246888,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to James Forrester from comment #3)
+> No; OOUI only understands RTL and LTR, not specific languages. The bold icon
+> isn't from OOUI but from VE itself, which does. Oy.
+
+Actually the per-language icon format is in OOUI (IconedElement.js line 42). You need to define the language overrides every time you specify the icon instead of just making it a 'feature' of the icon like directionality.",1404244142,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to Amir E. Aharoni from comment #2)
+> (In reply to James Forrester from comment #1)
+> > (In reply to Amir E. Aharoni from comment #0)
+> > > Some icons need to be flipped for RTL languages. Here's what I found till
+> > > now:
+> > > 
+> > > In lib/ve/lib/oojs-ui/images/icons:
+> > > * help.svg - This is a question mark in a circle. This should be flipped for
+> > > all RTL languages, but *not* for Hebrew (he) and Yiddish (yi).
+> > 
+> > This should (a) be an OOUI bug, and (b) is really quite hard for us to do as
+> > our build system only supports LTR or RTL, it doesn't do language-specific
+> > builds. How high priority is this?
+> 
+> Pretty important for people who write Arabic, Persian and Urdu.
+> Can't it be done the same way it's done for Bold and Italic?
+
+No; OOUI only understands RTL and LTR, not specific languages. The bold icon isn't from OOUI but from VE itself, which does. Oy.",1404229874,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to James Forrester from comment #1)
+> (In reply to Amir E. Aharoni from comment #0)
+> > Some icons need to be flipped for RTL languages. Here's what I found till
+> > now:
+> > 
+> > In lib/ve/lib/oojs-ui/images/icons:
+> > * help.svg - This is a question mark in a circle. This should be flipped for
+> > all RTL languages, but *not* for Hebrew (he) and Yiddish (yi).
+> 
+> This should (a) be an OOUI bug, and (b) is really quite hard for us to do as
+> our build system only supports LTR or RTL, it doesn't do language-specific
+> builds. How high priority is this?
+
+Pretty important for people who write Arabic, Persian and Urdu.
+Can't it be done the same way it's done for Bold and Italic?",1404194275,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to Amir E. Aharoni from comment #0)
+> Some icons need to be flipped for RTL languages. Here's what I found till
+> now:
+> 
+> In lib/ve/lib/oojs-ui/images/icons:
+> * help.svg - This is a question mark in a circle. This should be flipped for
+> all RTL languages, but *not* for Hebrew (he) and Yiddish (yi).
+
+This should (a) be an OOUI bug, and (b) is really quite hard for us to do as our build system only supports LTR or RTL, it doesn't do language-specific builds. How high priority is this?
+
+> In lib/ve/modules/ve/ui/styles/images/icons:
+> * external-link.svg
+
+Not currently used, but done in gerrit 143240.
+
+> In modules/ve-mw/ui/styles/images/icons:
+> * gallery.svg
+> * parameter.svg
+> * parameter-set.svg
+> * ref-cite-journal.svg
+> * ref-cite-news.svg
+> * reference.svg
+> * references.svg
+
+Done in gerrit 143241.
+
+> * ref-cite-book.svg
+
+Not now needed (no LTR/RTL variance). Similarly for ref-cite-web.",1404186595,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Try to open math inspector, it does not open up.
+Not showing any error in the console
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396636260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-adfbbfgylcnmev6236w2,task_description,resolved
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Verified the fix on production:
+https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox",1397775316,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,Verified the backported fix on test2: https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1397086948,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,Verified the fix on betalabs: http://en.wikipedia.beta.wmflabs.org/wiki/9thaprilChrome?veaction=edit,1397086640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Change 125023 merged by jenkins-bot:
+Update tool to use a command
+
+https://gerrit.wikimedia.org/r/125023",1397086016,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Change 125023 had a related patch set uploaded by Jforrester:
+Update tool to use a command
+
+https://gerrit.wikimedia.org/r/125023",1397085355,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Change 125017 merged by jenkins-bot:
+Update tool to use a command
+
+https://gerrit.wikimedia.org/r/125017",1397085211,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,Apparently the Gerrit bot is broken? Trevor submitted https://gerrit.wikimedia.org/r/#/c/125017/ for this and I +2ed it. Now we're waiting for Jenkins/Zuul to stop being broken so it'll actually get merged.,1397084425,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: Update styling of the MW format paragraph menu to match changes to Vector,"It would be nice if the new typography (e.g. serifed fonts for headlines) were reflected in VisaulEditor's ""format paragraph"" menu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63985",1396635960,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4wvfrqahqjzbkpjnaxd4,task_description,resolved
+VisualEditor: Update styling of the MW format paragraph menu to match changes to Vector,"Change 130771 merged by jenkins-bot:
+Style the FormatTool to be more like Vector's new look
+
+https://gerrit.wikimedia.org/r/130771",1398972824,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4wvfrqahqjzbkpjnaxd4,task_subcomment,NA
+VisualEditor: Update styling of the MW format paragraph menu to match changes to Vector,"Change 130771 had a related patch set uploaded by Jforrester:
+Style the FormatTool to be more like Vector's new look
+
+https://gerrit.wikimedia.org/r/130771",1398901458,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4wvfrqahqjzbkpjnaxd4,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"`mw.util.$content` from module `mediawiki.util` seems to be needless.
+
+```lang=js
+	$( function () {
+		mw.util.$content...
+	} );
+```
+can be replaced by
+```lang=js
+	mw.hook( 'wikipage.content' ).add( function ( $content ) {
+		$content...
+	} );
+```
+`mw.hook()` is necessary to support [[https://www.mediawiki.org/wiki/Manual:Live_preview|Live Preview]].",1396517640,PHID-USER-3dmql6z7s5lnn5lu2vs3,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_description,open
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"[[https://hu.wikipedia.org/w/index.php?title=MediaWiki:Gadget-warning.js&oldid=25499069#L-474|hu:MediaWiki:Gadget-warning.js]] uses this in an event handler to put a DOM element on the top of the page. The `wikipage.content` hook is not a good replacement, for two reasons:
+* (mildly bad) it’s asynchronous, and can be fired multiple times. Since the event handler can also run multiple times, it would require a global state to ensure that not more than one hook listener is active at a time.
+* (quite bad) it may be fired with several elements, not only `mw.util.$content` (e.g. #discussiontools previews fire it too). Adding the DOM element to all sorts of parser output blocks is definitely not what the user wants to see.
+
+What should be the path forward?",1671802302,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"@TheDJ Yeah, we could mark it as deprecated, do a Tech-News round, track the usage in Grafana/mw-js-deprecate and maybe do a few Global Search queries ourselves to help mitigate a few.",1671655569,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),@Krinkle It seems this has been done for all extensions now ? Which means that only gadgets and userscripts are still users. Do we investigate the userscripts or do we simply mark as deprecated and then investigate what needs it ?,1671576912,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 766859 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/InlineCategorizer@master] Remove needless use of mw.util.$content%%%
+https://gerrit.wikimedia.org/r/766859",1654562808,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 766867 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/CirrusSearch@master] ext.cirrus.serp: Use \""wikipage.content\"" instead of mw.util.$content%%%
+https://gerrit.wikimedia.org/r/766867",1646087341,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 766867 had a related patch set uploaded (by Krinkle; author: Krinkle):
+%%%[mediawiki/extensions/CirrusSearch@master] ext.cirrus.serp: Use \""wikipage.content\"" instead of mw.util.$content%%%
+https://gerrit.wikimedia.org/r/766867",1646084271,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 766859 had a related patch set uploaded (by Krinkle; author: Krinkle):
+%%%[mediawiki/extensions/InlineCategorizer@master] Remove needless use of mw.util.$content%%%
+https://gerrit.wikimedia.org/r/766859",1646083215,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"@Fomafix: Hi, I'm resetting the task assignee due to inactivity. Please feel free to reclaim this task if you plan to work on this - it would be welcome! Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for more information - thanks!",1643840291,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),">>! In T65466#683593, @Fomafix wrote:
+> Thanks for explanation.
+> 
+> What about a new hook 'wikipage.body'?
+
+If there's a need for something subscription/offering based in that way, I think that would be useful yes.
+
+However, I think the existing use-cases for `mw.util.$content` need/want something direct and synchronous.
+
+But, based on how we solved the Notifications use case, with a dedicated interface contract to the skin, we can probably do the same for other use cases. I think that's better than the generic  `mw.util.$content` which is quite difficult to use right now (because you have to wait for `$()` before it exists), and also inverts the responsibility. The module placing stuff in the body should not be the one deciding where it goes, unless it is the skin code doing it.
+
+Re-opening this (also in light of restricted T203549). Let's identify what uses/needs it, and then migrate them to either use `mw.hook('wikipage.content')` for cases where they need to find things in the content, or to other mechanisms like we did for Notifications (if they need to add something).
+
+I don't mind keeping it long-term or providing `wikipage.body` - if we find a need for that.",1588450365,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 123559 abandoned by Krinkle:
+Deprecate mw.util.$content
+
+Reason:
+Superseded by I30bdd893e0a0a340076.
+
+https://gerrit.wikimedia.org/r/123559",1398882823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Thanks for explanation.
+
+What about a new hook 'wikipage.body'?
+
+In mediawiki.page.startup.js fire
+	mw.hook( 'wikipage.body' ).fire( mw.util.$content ) );
+
+In mediawiki.notification.js replace
+	$( function () {
+		mw.util.$content...
+	} );
+by
+	mw.hook( 'wikipage.body' ).add( function ( $body ) {
+		$body...
+	} );",1396693934,PHID-USER-3dmql6z7s5lnn5lu2vs3,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Closing as won't fix per discussion between Daniel Friesen and myself at https://gerrit.wikimedia.org/r/123559.
+
+Although the naming is unfortunate, these are different things for different use cases.
+
+mw.hook( 'wikipage.content' ) is to get a reference to #mw-content-text (the true wiki page content, no skinning around it). It is different from $( '#mw-content-text' ) in that:
+
+* It can be asynchronous (you can register the hook without needing to explicitly wait for document-ready).
+* It is more semantically correct if your intent is ""change content"" because it will re-fire when the content changes dynamically (e.g. after saving an edit with VisualEditor, or when ajax live previewing wikitext, or in some hypothetical ""ajax navigation"" feature).
+
+mw.util.$content is to get a reference to the body content wrapper (the element containing #mw-content-text, usually indicated by .mw-body). Because mw.util.$content has been around since before mw.hook, it is likely that there are existing uses out there that would benefit from using mw.hook instead. However there remain uses for mw.util.$content where mw.hook is not a suitable alternative.
+
+Having said that, I still think we should deprecate mw.util.$content because it sucks (retrieving its value is tricky because it is asynchronously initialised without a clear callback for when that happens). However until we have an alternative for it, let's keep it.
+
+Ideally we'd just mandate that all skins follow the convention to use mw-body class and then just document that as an API (similar to how addPortletLink's html structure has become more or less skin independent, though not quite there yet) that people use by waiting for domready and querying mw-body or mw-body-primary.",1396643082,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 123559 had a related patch set uploaded by Gerrit Patch Uploader:
+Deprecate mw.util.$content
+
+https://gerrit.wikimedia.org/r/123559",1396517857,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Screenshot of excessive whitespace on top of an in-content dialog with h2 heading
+
+Since inner padding of the dialog container and top margin of the header don't collapse, they get stacked and now have an excessive amount of whitespace (see screenshot).
+
+The margin-top of 'div#content h2' should be safe to remove. We didn't have it in the past, and in any regular text flow context it is already spaced away from the preceding element by the bottom margin of block level elements (like paragraphs and tables).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63312
+
+**Attached**: {F13341}",1396381920,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h3rnvqmaajhu7cd26sul,task_description,invalid
+Vector: Headings have excessive top margin when used as first element in a content container,">Could we tweak it to have a !firstChild or something on H2s so it only triggers
+>for the H2s that we actually want to style?
+
+I can't think of any way to do this that would be reliable. We could do something like...
+#content h2(:not( .dialogHeader ))
+but that would still require making sure that all headers in dialogs included that class. (And if we're updating those headers anyway, we might as well convert them from h2s into something else.)
+
+We could also use jQuery to try to guess which h2s are actually section headers and which ones aren't, but that would cause a style change flash.
+
+I still haven't heard any evidence that this bug actually affects more than a single dialog box. If it's just one dialog, is it really that hard to fix, even though the code is unmaintained? What extension generates that dialog box?",1403037124,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"(In reply to Ryan Kaldari from comment #11)
+> What James says is true, although there currently isn't any way to have
+> large margins between the sections on desktop without increasing the margins
+> on "".content h2"", so unless design agrees to reduce those margins, the fix
+> will have to be to the unmaintained code (at least until the desktop DOM
+> includes some sort of section elements).
+
+Could we tweak it to have a !firstChild or something on H2s so it only triggers for the H2s that we actually want to style?",1403036084,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"What James says is true, although there currently isn't any way to have large margins between the sections on desktop without increasing the margins on "".content h2"", so unless design agrees to reduce those margins, the fix will have to be to the unmaintained code (at least until the desktop DOM includes some sort of section elements).",1403032221,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"(In reply to Jared Zimmerman (WMF) from comment #9)
+> This is as designed, as Steven said, if there are 1 one off cases where the
+> padding is too large within specific features or use cases (not articles or
+> content pages) the feature teams should write modifications to the style for
+> those cases.
+
+This is a complaint about the breakage of unmaintained code that was written with the expectation that people wouldn't unexpectedly change these, though. There are no ""feature teams"" to fix the breakage for you…",1403031342,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"This is as designed, as Steven said, if there are 1 one off cases where the padding is too large within specific features or use cases (not articles or content pages) the feature teams should write modifications to the style for those cases.",1403031035,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,CCing Jared since this is really a design issue.,1403027394,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Change 123024 abandoned by Krinkle:
+vector: Remove margin-top from 'div#content h2'
+
+Reason:
+Implementing something in a hacky way that breaks expectations about how page layout works and then putting the burden on other maintainers to make it work well with the rest of the web is imho not ideal practice. But I can't invest in this now, so snafu. You're welcome.
+
+https://gerrit.wikimedia.org/r/123024",1401852285,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Because the discussion here clearly points to a lack of consensus, I'm removing the 1.23.0 target.",1399652862,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,">I think you might've missed that I said the margin-top can be safely removed 
+>because it is ineffective. It isn't ""increasing"" the visible whitespace between 
+>sections...
+
+I don't think that's accurate. Having ""h2 { margin-top: 1em; }"" is definitely increasing the whitespace significantly between sections. With that rule in place, the whitespace is effectively 21 pixels (0.875em x 1.5em x 1em x 16px). Without it, in most cases, the whitespace is only 7 pixels (0.875em x 0.5em x 16px). That's a big difference.
+
+If we want to change the amount of whitespace between sections, we need to get input from design on this. If we don't want to change the amount of whitespace between sections, we need to find a different way to implement the whitespace. Currently, however, I don't see any better way to implement the whitespace between sections.
+
+As the bug is currently defined, I recommend WONTFIX.",1398882628,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Rephrasing bug to reflect the two most common problem cases:
+
+* Using a heading as first element on page (e.g. the first section, as opposed to between two sections).
+
+* Using a heading inside a container that isn't the root of the page (e.g. inside a bubble such as on [1], or any other kind of sub container).
+
+
+[1] https://www.mediawiki.org/w/index.php?title=Help:VisualEditor/User_guide&oldid=984581#toc",1398873871,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"I think you might've missed that I said the margin-top can be safely removed because it is ineffective. It isn't ""increasing"" the visible whitespace between sections, because all block level elements already have sufficient *bottom* margin. And browsers collapse/merge the top margin of the next element with the bottom margin of the previous element.
+
+No matter whether it's a paragraph, list, <pre>, gallery or <table>, their bottom margin is already taking care of that space. When I removed the top-margin of headings locally it made little to no visible difference.
+
+So if the goal was to increase the space between sections, it failed to do that.
+
+If we do want to increase space between sections, I suggest it is implemented in different way. Using margin-top for that is in my opinion inappropriate and bound to cause layout hazards.
+
+I agree the specific instance in which I ran into this bug is dubious, but in general you mustn't assume that a heading will only be used in the root flow of the content and only in the n+1th section of page.
+
+Using margin-top means that:
+* Using the heading in the first section on a page will cause a weird gap on top because it's trying to offset itself from the previous section when in fact that is the top of the page. Which is a problem since content wrappers already have padding, and that doesn't merge with margins of elements inside.
+
+* Using the heading inside another element (blockquote, table, infobox, form), even inside elements that aren't intended as their own block (e.g. heading bubbles such as on [1]) will now have a margin on top on the inside intended to separate itself from a section. This could in theory be worked around by resetting margins or creating negative catch margins. However that would be an unintuitive hack that doesn't scale because it's moving the responsibility to the wrong component (e.g. if you want to use a <table> on a page, you cannot be expected to have to set all kinds of inline styles to make it render properly, it is the skin's fault for changing the default of all headings to act like section separators. The skin should take care to recognise the relevant headings and style them and leave the others untouched).
+
+I'm not going to spend time on finding one of many alternate ways to implement section separation margins on desktop, but the way it is implemented right now is and will continue to cause all kinds of layout problems due to it applying top-margins that are too large when applied in a context that isn't between two sections.
+
+[1] https://www.mediawiki.org/w/index.php?title=Help:VisualEditor/User_guide&oldid=984581#toc)",1398873661,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"**swalling** wrote:
+
+I think this is probably something where special UI elements like dialogs should be adding/changing their own H2 styles, rather than reusing styles intended for content pages.
+
+Repeating Kaldari's comment on the patch:
+
+""The 1em margin was implemented on purpose by the design team. As mentioned in the FAQ, they wanted to significantly increase the whitespace between sections. Unfortunately on desktop we don't have any ""section"" DOM element, so adding top margin to h2s is the best way to accomplish that.
+
+Since dialogs don't often belong to the content div, it seems like better solutions to bug 63390 would be:
+
+1. Move the dialog outside the content div;
+2. Don't use h2s in that dialog, or...
+3. Override the h2 style in that case.
+Is there more than 1 dialog affected by this bug?""",1397201147,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Change 123024 had a related patch set uploaded by Krinkle:
+vector: Remove margin-top from 'div#content h2'
+
+https://gerrit.wikimedia.org/r/123024",1396382016,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Intention:
+Add a value to an empty cell in a table using VE
+
+Steps to Reproduce:
+1. You need a page with a table with at least one empty cell (e.g. https://en.wikipedia.beta.wmflabs.org/wiki/User:ESanders_(WMF)/sandbox/T65356)
+2. Open page for VE editing
+3. Double click on the empty cell, then add some text
+4. Show the wikitext diff in the save dialog
+
+Actual Results:  
+In addition to the entered text a line-break is added
+
+Expected Results:  
+No additional line-break
+
+Reproducible: Always
+
+Note that this does not happen for cells which already contains a value
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396347240,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-b2kjds44fcmdnsoqczzm,task_description,resolved
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Change 670606 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (145cf95d8)
+
+https://gerrit.wikimedia.org/r/670606",1615494433,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Change 670606 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (145cf95d8)
+
+https://gerrit.wikimedia.org/r/670606",1615417291,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Change 667411 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Use wrapper paragraphs in empty branch nodes
+
+https://gerrit.wikimedia.org/r/667411",1615417123,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Change 667411 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] Use wrapper paragraphs in empty branch nodes
+
+https://gerrit.wikimedia.org/r/667411",1614528761,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Hmm, the difference seems to be that if you click once on the empty cell and start typing, VE doesn't wrap the text in a `<p>`,
+
+```
+<td data-parsoid=""{&quot;stx_v&quot;:&quot;row&quot;,&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[38,41,2,0]}"">haha</td>
+```
+
+However, doubling clicking and then typing does,
+
+```
+<td data-parsoid=""{&quot;stx_v&quot;:&quot;row&quot;,&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[38,41,2,0]}""> <p>haha</p></td>
+```
+
+Serializing the paragraph introduces a newline which would break the row syntax, so Parsoid switches the other format.  I suppose we could be smarter about the p/td nl constraints, or VE maybe avoid introducing the paragraph to begin with?",1490804735,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,*** Bug 73215 has been marked as a duplicate of this bug. ***,1415618411,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Created attachment 14994
+Screenshot
+
+Screenshot showing the result to the source of editing a filled and an empty cell using VE.
+
+**Attached**: {F13280}",1396347330,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+VisualEditor: Double colons when linking to File/Category,"Intention:
+Linking to a file using visual editor
+
+Steps to Reproduce:
+1. Edit page on using VE
+2. Click add link
+3. Enter a filename with File-prefix (e.g. File:Foo.svg)
+4. Press enter
+5. Press enter again
+
+The same thing happens for categories or if the preceding colon is added manually.
+
+
+Actual Results:  
+4. Inserted text is changed to :File:Foo.svg
+5. Inserted text is changed to ::File:Foo.svg
+
+Expected Results:  
+4. As result
+5. No change
+
+Reproducible: Sometimes
+
+The same thing happens for categories or if the preceding colon is added manually. I can get this to happen repeatedly but occasionally VE will correctly know not to add the second colon (have not identified when though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63355",1396343280,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-vkbfyitznumudqoxqfgs,task_description,resolved
+VisualEditor: Double colons when linking to File/Category,"Dupe of 50279 (and now fixed).
+
+*** This bug has been marked as a duplicate of bug 50279 ***",1403995088,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vkbfyitznumudqoxqfgs,task_subcomment,NA
+VisualEditor: Double colons when linking to File/Category,"Here's a variation:
+
+1.  Edit page on using VisualEditor.
+
+2.  Type the file name you want (with or without the colon prefix that you want):  File:Example.jpg
+
+3.  Open the link inspector, which will offer to link these files (at least on en.wp):
+
+:File:Example.jpg
+File:Example.jpg
+File:Example.JPG
+
+4.  Choose the first.  Press enter.  Now it has changed the link target to ""::File:Example.jpg"" and says ""Invalid page title"".  (Saving this link will work correctly anyway.)
+
+5.  Alternatively, choose the second, and press enter.  This also works and does not produce the error message.",1401819333,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-vkbfyitznumudqoxqfgs,task_subcomment,NA
+VisualEditor: Double colons when linking to File/Category,"Also happening with FF, Win8.
+The resulting wikilink works, though.",1401801899,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-vkbfyitznumudqoxqfgs,task_subcomment,NA
+VisualEditor: Double colons when linking to File/Category,"Created attachment 14992
+Screencast
+
+Added video since this is not 100% reproducible
+
+**Attached**: {F13270}",1396344427,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-vkbfyitznumudqoxqfgs,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Click on Show Options
+4.Click on the trash icon.
+5.Click on ""Add Content""
+
+Observed Result:
+The ""Insert transclusion"" button becomes enabled and an empty transclusion with empty content gets added upon clicking on it.
+
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13225}",1396312320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pxydfaaecdb2drrqo3x6,task_description,resolved
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,Verified the fix in production,1415835803,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,Verified the fix in test2,1415229959,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Change 169638 merged by jenkins-bot:
+MWTransclusionModel: Exclude parts serialising to '' from the plain object
+
+https://gerrit.wikimedia.org/r/169638",1414624850,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Change 169638 had a related patch set uploaded by Alex Monk:
+MWTransclusionModel: Exclude parts serialising to '' from the plain object
+
+https://gerrit.wikimedia.org/r/169638",1414545036,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"See also bug 63340, which was duped to this one but is actually subtly different: it's about when the only part is a TemplatePlaceholderPage",1414117605,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,*** Bug 63340 has been marked as a duplicate of this bug. ***,1414098890,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Also, there is an error in the console:
+Uncaught TypeError: Cannot read property 'length' of null",1414091215,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Created attachment 14990
+Screenshot
+
+**Attached**: {F13226}",1396312398,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+"VisualEditor: ""Insert Transclusion""  button becomes enabled after adding a second empty template","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the transclusion add dialog box by going to Insert>Template
+3.Click on the ""Show Options"" button
+4.Now click on the ""Add template"" button
+
+Observed Result:
+The ""Insert Transclusion"" button becomes enabled and clicking on that does nothing 
+
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13220}",1396311480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cgka64ivffbox23apkiw,task_description,resolved
+"VisualEditor: ""Insert Transclusion""  button becomes enabled after adding a second empty template","
+
+*** This bug has been marked as a duplicate of bug 63341 ***",1414098890,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cgka64ivffbox23apkiw,task_subcomment,NA
+"VisualEditor: ""Insert Transclusion""  button becomes enabled after adding a second empty template","Yeah , this one I filed for adding empty template and bug 63341 was specifically for adding empty content,but they might get fixed at one shot.In that case I guess we should merge these two?",1414097061,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cgka64ivffbox23apkiw,task_subcomment,NA
+"VisualEditor: ""Insert Transclusion""  button becomes enabled after adding a second empty template",Is this the same as bug 63341?,1414096243,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cgka64ivffbox23apkiw,task_subcomment,NA
+VisualEditor: There is no keyboard function to exit the Math Inspector and Gallery,"Right now, there is no keyboard function to exit the Math Inspector and Gallery inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396306440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gyyhelxas56x6xvw7n7w,task_description,declined
+VisualEditor: There is no keyboard function to exit the Math Inspector and Gallery,Escape works for me…,1402296299,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gyyhelxas56x6xvw7n7w,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"The media selector (both in WikiEditor and Visual Editor) does not find local images in a private wiki. When the same wiki is set to public, it works.
+
+I've tried this with 3 different installations (1.22 and 1.23wmf20) on two different servers, both with Visual Editor and WikiEditor. 
+
+The relevant setting is
+
+$wgGroupPermissions['*']['read'] = false;
+
+When this is set to false, when a user (logged in and registered) edits a page and starts typing the name of an existing file in the media selector, the input box remains empty and does not suggest existing file names. 
+
+When the read permission is set to true, then it works as expected (giving a list of suggestions in the input box) - but of course then the wiki is no longer private.
+
+On the other hand, the link selector finds the files when I type ""File:Filename.."". Also, the image is actually shown in the article when I insert it with Wiki markup, or when I type in the correct filename in the selector and click on ""insert"".
+
+So somehow the media selector (but not the link selector) does not understand the permission correctly for a logged-in user.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396213080,PHID-USER-mn2oreq3jstq45jm3fp5,PHID-TASK-qlnckdanskw255gs5et4,task_description,resolved
+Media selector doesn't find local media in private wiki,Related and more recent: T188236,1717452855,PHID-USER-3baphe4xso6l4kkryqex,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,See also T63151 and https://www.mediawiki.org/wiki/Topic:Rb7adzuz9pt6ifno,1444632168,PHID-USER-wtbw6n3qdyre3vir7o3z,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"I could not reproduce the error on officewiki (a private wiki which is about a week behind master). Both your examples return a `readapidenied` error (which is a bug on its own right, reported as T106425). The VE media selector works fine, with or without an asterisk.
+
+You could try to reproduce the bug in a controlled environment by using [[ https://www.mediawiki.org/wiki/MediaWiki-Vagrant | MediaWiki-Vagrant ]] with the `private` and `visualeditor` roles.",1437516326,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"Yes, this is the API request that fails to find the image:
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+It results in: 
+
+```
+/**/jQuery1113038504008506424725_1437475882811({""batchcomplete"":""""})
+```
+
+If I add an astericks at the end of the search-term, it works:
+
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server*&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+
+Results in:
+
+```
+/**/
+jQuery1113038504008506424725_1437475882811({
+    ""continue"": {
+        ""iistart"": ""2015-06-23T05:30:36Z"",
+        ""continue"": ""||""
+    },
+    ""query"": {
+        ""pages"": {
+            ""6672"": {
+                ""pageid"": 6672,
+                ""ns"": 6,
+                ""title"": ""Datei:Server\u00dcbersicht.png"",
+                ""index"": 1,
+                ""imagerepository"": ""local"",
+                ""imageinfo"": [{
+                    ""timestamp"": ""2015-06-23T05:31:57Z"",
+                    ""size"": 188839,
+                    ""width"": 3000,
+                    ""height"": 1606,
+                   ....
+                    ""mediatype"": ""BITMAP""
+                }]
+            }
+        }
+    }
+})
+```
+
+When using the astericks, the VE request works, but is repeated endlessly:
+
+{F203227}",1437479949,PHID-USER-wtbw6n3qdyre3vir7o3z,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"Yes, this is the API request that fails to find the image:
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+It results in: 
+
+```
+/**/jQuery1113038504008506424725_1437475882811({""batchcomplete"":""""})
+```
+
+If I add an astericks at the end of the search-term, it works:
+
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server*&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+
+Results in:
+
+```
+/**/
+jQuery1113038504008506424725_1437475882811({
+    ""continue"": {
+        ""iistart"": ""2015-06-23T05:30:36Z"",
+        ""continue"": ""||""
+    },
+    ""query"": {
+        ""pages"": {
+            ""6672"": {
+                ""pageid"": 6672,
+                ""ns"": 6,
+                ""title"": ""Datei:Server\u00dcbersicht.png"",
+                ""index"": 1,
+                ""imagerepository"": ""local"",
+                ""imageinfo"": [{
+                    ""timestamp"": ""2015-06-23T05:31:57Z"",
+                    ""size"": 188839,
+                    ""width"": 3000,
+                    ""height"": 1606,
+                    ""thumburl"": ""http://10.248.8.1/wiki/images/thumb/6/6c/ServerÜbersicht.png/300px-ServerÜbersicht.png"",
+                    ""thumbwidth"": 300,
+                    ""thumbheight"": 161,
+                    ""url"": ""http://10.248.8.1/wiki/images/6/6c/ServerÜbersicht.png"",
+                    ""descriptionurl"": ""http://10.248.8.1/wiki/index.php/Datei:ServerÜbersicht.png"",
+                    ""extmetadata"": {
+                        ""DateTime"": {
+                            ""value"": ""2015-06-23T05:31:57Z"",
+                            ""source"": ""mediawiki-metadata"",
+                            ""hidden"": """"
+                        },
+                        ""ObjectName"": {
+                            ""value"": ""Server\u00dcbersicht"",
+                            ""source"": ""mediawiki-metadata"",
+                            ""hidden"": """"
+                        }
+                    },
+                    ""mediatype"": ""BITMAP""
+                }]
+            }
+        }
+    }
+})
+```
+
+When using the astericks, the VE request works, but is repeated endlessly:
+
+{F203227}",1437479899,PHID-USER-wtbw6n3qdyre3vir7o3z,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"Yes, this is the API request that fails to find the image:
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+It results in: 
+
+```
+/**/jQuery1113038504008506424725_1437475882811({""batchcomplete"":""""})
+```
+
+If I add an astericks at the end of t he search-term, it works:
+
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server*&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+
+Results in:
+
+```
+/**/
+jQuery1113038504008506424725_1437475882811({
+    ""continue"": {
+        ""iistart"": ""2015-06-23T05:30:36Z"",
+        ""continue"": ""||""
+    },
+    ""query"": {
+        ""pages"": {
+            ""6672"": {
+                ""pageid"": 6672,
+                ""ns"": 6,
+                ""title"": ""Datei:Server\u00dcbersicht.png"",
+                ""index"": 1,
+                ""imagerepository"": ""local"",
+                ""imageinfo"": [{
+                    ""timestamp"": ""2015-06-23T05:31:57Z"",
+                    ""size"": 188839,
+                    ""width"": 3000,
+                    ""height"": 1606,
+                    ""thumburl"": ""http://10.248.8.1/wiki/images/thumb/6/6c/ServerÜbersicht.png/300px-ServerÜbersicht.png"",
+                    ""thumbwidth"": 300,
+                    ""thumbheight"": 161,
+                    ""url"": ""http://10.248.8.1/wiki/images/6/6c/ServerÜbersicht.png"",
+                    ""descriptionurl"": ""http://10.248.8.1/wiki/index.php/Datei:ServerÜbersicht.png"",
+                    ""extmetadata"": {
+                        ""DateTime"": {
+                            ""value"": ""2015-06-23T05:31:57Z"",
+                            ""source"": ""mediawiki-metadata"",
+                            ""hidden"": """"
+                        },
+                        ""ObjectName"": {
+                            ""value"": ""Server\u00dcbersicht"",
+                            ""source"": ""mediawiki-metadata"",
+                            ""hidden"": """"
+                        }
+                    },
+                    ""mediatype"": ""BITMAP""
+                }]
+            }
+        }
+    }
+})
+```
+
+When using the astericks, the VE request works, but is repeated endlessly:
+
+{F203227}",1437476343,PHID-USER-wtbw6n3qdyre3vir7o3z,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,Presumably some permission is missing. Can you post the exact API requests and responses?,1436560729,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,,1435749957,PHID-USER-wtbw6n3qdyre3vir7o3z,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,,1435734088,PHID-USER-wtbw6n3qdyre3vir7o3z,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"I've got the same problem (on a private wiki).
+
+I've tryed the permission fix. Still no effect on the first glance.
+
+However, If i type ""*"" or the complete name (including the namespace), it finds my image, if I type the only the name (or a part of the name) nothing appears.
+
+This seems to be an issue with the MediaWiki API. It's search algorithm is so strict, that you already need to know the exact name in order to get a result.
+
+Appending / prepending an astericks helps, though. Maybe VE should do that by default?
+
+VisualEditor-REL1_25
+MediaWiki	1.25.1
+PHP	5.5.9-1ubuntu4.9 (apache2handler)",1435750120,PHID-USER-wtbw6n3qdyre3vir7o3z,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"I've got the same problem (on a private wiki).
+
+Couldn't change that with the proposed permission fix.
+
+Interestingly, If i type ""*"", it finds my image, if I type the name (or part of the name) nothing appears.",1435733866,PHID-USER-wtbw6n3qdyre3vir7o3z,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"I still have the same problem in version 1.25wmf17 (d70b751)
+e.g. typing ""l"" shows only two images, adding an ""e"" shows only one, other(!) image.
+In order to find a file, I have to enter the complete name, including the extension :-( 
+Even worse, some files cannot be found at all. They can only be inserted using the text-editor.
+I cannot find the file ""At_venice.jpg"". The file appears as ""At_venice.jpg"" in the images-directory, but as ""At venice"" on the wiki-page describing the image.
+Anyway, I can't find the file Koala.jpg either, no spaces or underscores there :-( (but a capital letter...)
+
+Still the same issues as described earlier: I can find the file ""test_lego.jpg"" by typing ""test"", but not by typing ""lego"".
+
+It's getting better: I upload a file as ""jorun.jpg"" but cannot find it, unless by typing the complete name. I upload the same file as ""jorun test.jpg"". I can find this photo by typing 'jorun'.
+
+Still looks like a bug to me!
+",1426429220,PHID-USER-y4tnf7qjm6yk3pjxmhg2,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"In 1.25wmf8, it works now correctly without the (unsecure) workaround. I guess some other things with permissions were fixed which solved this one as a side effect too.",1416312559,PHID-USER-mn2oreq3jstq45jm3fp5,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"**gabriel_stelmach** wrote:
+
+Hello there,
+
+I just face this issue in my installation. There are any news about solution for this?
+
+In time. Thank you Stephan for the workaround.
+
+[]s",1414784948,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"(In reply to Bawolff (Brian Wolff) from comment #3)
+> Actually that can be exploited to get around read protection everywhere
+> (including normal web requests). Any url can have that string in it.
+
+Of course, and I don't recommend it. It was just meant as an indication that it's a bug in this specific api call for image searches and that other api calls are ok, so it's not a disabled api.",1397227191,PHID-USER-mn2oreq3jstq45jm3fp5,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"(In reply to Stephan Matthiesen from comment #2)
+> (In reply to Bawolff (Brian Wolff) from comment #1)
+> > Maybe private only wikis cause api to be disabled.
+> 
+> API is not disabled completely. All other API calls seem to work, only image
+> search is affected.
+> 
+> The following workaround in LocalSettings.php also works:
+> 
+> if ( strpos($_SERVER['REQUEST_URI'], ""prop=imageinfo"") > 0 ) {
+>     $wgGroupPermissions['*']['read'] = true;
+> }
+> 
+> This disables read protection selectively for the image search.
+
+Actually that can be exploited to get around read protection everywhere (including normal web requests). Any url can have that string in it.",1397226365,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"(In reply to Bawolff (Brian Wolff) from comment #1)
+> Maybe private only wikis cause api to be disabled.
+
+API is not disabled completely. All other API calls seem to work, only image search is affected.
+
+The following workaround in LocalSettings.php also works:
+
+if ( strpos($_SERVER['REQUEST_URI'], ""prop=imageinfo"") > 0 ) {
+    $wgGroupPermissions['*']['read'] = true;
+}
+
+This disables read protection selectively for the image search.",1397222536,PHID-USER-mn2oreq3jstq45jm3fp5,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,Maybe private only wikis cause api to be disabled.,1396214506,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+VisualEditor: Reference's highlight is misplaced if it appears after a references list block,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a Cite reference like Cite>Web/Book/Newspaper/Journal
+
+Observed Result:
+The selection highlight box is appearing a bit above the reference note
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12974}",1396046220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-twqcomuca3vkpbi4cgb7,task_description,resolved
+VisualEditor: Reference's highlight is misplaced if it appears after a references list block,"Yes, this looks like it was fixed a while ago.",1411403567,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-twqcomuca3vkpbi4cgb7,task_subcomment,NA
+VisualEditor: Reference's highlight is misplaced if it appears after a references list block,Is this still broken?,1404905022,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-twqcomuca3vkpbi4cgb7,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Guillemets, French quotation marks (https://en.wikipedia.org/wiki/International_variation_in_quotation_marks#French), are now available through the special characters tool in VE on fr.wiki.
+When you select a word and then add the guillemets in the wikitext editor, the word gets wrapped in them.
+This is not the case in VE - the symbols appear, the word gets deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396007580,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2io5oqagajkj54tjjrwx,task_description,resolved
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Oh, great. I was wondering that quotation marks have disepeard with new charset.",1433205573,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","The pairs of quotes appropriate for various languages can be inserted now (“” „“ „” «»), from the ""Symbols"" section, and if you do it while you have text selected, they will wrap it instead of replacing it.
+
+{F154006}
+
+If you wish to add items supporting this functionality to ""Often used"" characters list (https://www.mediawiki.org/wiki/VisualEditor/Special_characters#Adding_often_used_characters), the required syntax is (replace ""A"" and ""B"" with appropriate characters):
+
+```
+  ""AB"": {
+    ""action"": {
+      ""type"": ""encapsulate"",
+      ""options"": {
+        ""pre"": ""A"",
+        ""post"": ""B""
+      }
+    }
+  },
+```
+
+(Per https://www.mediawiki.org/wiki/MediaWiki_1.26/Roadmap, this change will be deployed on Wikipedias on Wednesday, 06 May 2015.)",1429770634,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Change 205558 merged by jenkins-bot:
+Allow special characters with tooltip or that encapsulate text
+
+[[https://gerrit.wikimedia.org/r/205558]]",1429750554,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Change 205556 merged by jenkins-bot:
+ve.ui.SpecialCharacterDialog: Allow encapsulation of selected content
+
+[[https://gerrit.wikimedia.org/r/205556]]",1429740887,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Change 205558 had a related patch set uploaded (by Bartosz Dziewoński):
+Allow special characters with tooltip or that encapsulate text
+
+[[https://gerrit.wikimedia.org/r/205558]]
+",1429608440,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Change 205556 had a related patch set uploaded (by Bartosz Dziewoński):
+ve.ui.SpecialCharacterDialog: Allow encapsulation of selected content
+
+[[https://gerrit.wikimedia.org/r/205556]]
+",1429608420,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","I confirm this at cs.wp. For the Czech „“ its common, to select a word click on spacial character button and insert quotatin marks arround.",1399013809,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with
+2,Add a bullet list or numbered list
+3.Add an empty bullet item 
+4.Add indentation to it
+5.Select the previous item
+6.Change the paragraph style of the previous item
+
+
+Observed Result:
+An error appears in the console
+Uncaught Error: Unbalanced set of replace operations found 
+
+Now press enter to add another item :
+Uncaught Error: Unbalanced input passed to document 
+
+Press undo:
+Uncaught Error: Offset could not be translated to a DOM element and offset
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/27thmarChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12902}",1395962100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gxhvf2p6374tnbqf755k,task_description,resolved
+VisualEditor: Changing format of a list item right above a nested list item breaks,Verified the fix in:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1397775053,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,Verified the fix on test 2,1397519641,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Change 124493 merged by jenkins-bot:
+Exclude insertions in ve.dm.SurfaceFragment#isolateAndUnwrap
+
+https://gerrit.wikimedia.org/r/124493",1397105117,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Change 123892 abandoned by Catrope:
+Adjust range manually in isolateAndUnwrap()
+
+Reason:
+Superseded by https://gerrit.wikimedia.org/r/#/c/124493/
+
+https://gerrit.wikimedia.org/r/123892",1396928035,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Change 124493 had a related patch set uploaded by Catrope:
+Exclude insertions in ve.dm.SurfaceFragment#isolateAndUnwrap
+
+https://gerrit.wikimedia.org/r/124493",1396912258,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Change 123892 had a related patch set uploaded by Catrope:
+Adjust range manually in isolateAndUnwrap()
+
+https://gerrit.wikimedia.org/r/123892",1396634796,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,I've figured out why this bug happens and I know how to fix it. I have to go now but I'll write a patch when I get back (~1.5 hours),1396559050,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"It suffices to do a format change on any list item that has a nested list item directly beneath it. In other words, if you have the list
+
+* Foo
+* Bar
+** Baz
+
+then changing ""Bar"" to a heading will break. It doesn't matter if ""Baz"" is empty, it just has to be at a deeper list level than ""Bar"".",1396558081,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Link inspector icon appears after deleting the content of the page and closing the inspector causes an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 65,"Screenshot
+
+Steps to reproduce:
+
+1.Open this page: https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit
+
+2.Select all the content 
+
+3.Delete it.
+
+4.A link inspector icon appears in the page.
+
+5.Open the link inspector
+
+6.Close it 
+
+Observed Result:
+The links inspector gets all blank and an error appears in the console:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 65
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12901}",1395959940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ahuroh4hw3ltw7jphxcw,task_description,resolved
+VisualEditor: Link inspector icon appears after deleting the content of the page and closing the inspector causes an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 65,"Change 122556 merged by jenkins-bot:
+Fix handlesOwnChildren check in getRelativeOffset
+
+https://gerrit.wikimedia.org/r/122556",1396299546,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ahuroh4hw3ltw7jphxcw,task_subcomment,NA
+VisualEditor: Link inspector icon appears after deleting the content of the page and closing the inspector causes an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 65,"Change 122556 had a related patch set uploaded by Esanders:
+Fix handlesOwnChildren check in getRelativeOffset
+
+https://gerrit.wikimedia.org/r/122556",1396299373,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ahuroh4hw3ltw7jphxcw,task_subcomment,NA
+VisualEditor: Link inspector icon appears after deleting the content of the page and closing the inspector causes an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 65,"Deleting everything results in an empty document but for the internalList, i.e. [{'type':'internalList'...}, ...]. The popup tool is then look for annotations at range 0 which is then going inside the internal list and finding the link.",1396047717,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ahuroh4hw3ltw7jphxcw,task_subcomment,NA
+"VisualEditor: The link inspector opens after gallery , if there is gallery just after the text on which the link is getting applied","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a text
+3.Add a gallery right after that.
+4.Select the text by selecting whole line
+5.Click on the link inspector
+
+Observed Result:
+The link inspector opens after the gallery 
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/27thmarChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12878}",1395952200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3nqxc32ajmzpi3hsotvq,task_description,resolved
+"VisualEditor: The link inspector opens after gallery , if there is gallery just after the text on which the link is getting applied",I /think/ Ed fixed this with his changes last fortnight. Maybe.,1402553191,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3nqxc32ajmzpi3hsotvq,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"Consequently to the success of VisualEditor on the French Wikipedia and Wikiversity, the French Wiktionary and Wikibooks have voted in favor of its utilization:
+
+https://fr.wiktionary.org/wiki/Wiktionnaire:Prise_de_d%C3%A9cision/Installation_de_l%27%C3%A9diteur_visuel
+
+https://fr.wikibooks.org/wiki/Wikilivres:Prise_de_d%C3%A9cision/Installation_de_l%27%C3%A9diteur_visuel
+
+So, thank you to deploy it on fr.wikt and fr.b please.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395927360,PHID-USER-dtdj4p6jtxbzs7trc3c6,PHID-TASK-nuycumir3hop5ekks7h2,task_description,resolved
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,This was done yesterday; sorry for not noting this then.,1396021903,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"Change 121439 merged by Mwalker:
+Enable VisualEditor by default on French Wiktionary & French Wikibooks
+
+https://gerrit.wikimedia.org/r/121439",1395961403,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"We will get this setting turned on this afternoon (Pacific time), in the usual deployment.",1395949344,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"Change 121439 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on French Wiktionary & French Wikibooks
+
+https://gerrit.wikimedia.org/r/121439",1395948955,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"[Moving to ""Wikimedia"" product as this request is about settings / configuration of the website, not about the codebase of VisualEditor extension itself.]",1395928893,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Transclusion
+3.Insert a template for example : The Cite web
+4.Click on ""Show options""
+5.Keep on clicking on trash icon until you delete all the parameters and the template itself
+
+Observed Result:
+
+Observe that, even if there is no template in the dialog box , the add parameter button remains enabled , it should be disabled if there is o template.
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13393}",1395881520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3zamatwiubewzrfjcxeq,task_description,resolved
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,Verified the fix in production,1415226510,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3zamatwiubewzrfjcxeq,task_subcomment,NA
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,"Change 168379 merged by jenkins-bot:
+Disable parameter add icon when there's no transclusion parts
+
+https://gerrit.wikimedia.org/r/168379",1414442389,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3zamatwiubewzrfjcxeq,task_subcomment,NA
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,Confirmed in betalabs and test2.,1414439952,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3zamatwiubewzrfjcxeq,task_subcomment,NA
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,"Change 168379 had a related patch set uploaded by Alex Monk:
+Disable parameter add icon when there's no transclusion parts
+
+https://gerrit.wikimedia.org/r/168379",1414090303,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3zamatwiubewzrfjcxeq,task_subcomment,NA
+BetaFeatures: Skin warning message pulls in skin names regardless of whether skin is available,"On beta features tab in your user preferences http://de.wikipedia.org/wiki/Spezial:Einstellungen?useskin=modern&uselang=de#mw-prefsection-betafeatures visualeditor shows a red requirement warning if the current skin is not supported. But this warning uses not available system messages:
+
+This feature only works with the following skins:
+    Vector
+    &lt;skinname-apex&gt;
+    MonoBook
+    &lt;skinname-minerva&gt; 
+
+The problem on wikimedia wikis is that both skins, apex and minerva, are not installed and so the system messages skinname-apex and skinname-minerva are missing.
+
+I think there are two options how to fix this bug:
+1. add these two messages to localisation files used by wmf
+2. test if a skin is available before adding it to the skin list of the warning message
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**URL**: http://de.wikipedia.org/wiki/Spezial:Einstellungen?useskin=modern#mw-input-wpvisualeditor-enable",1395871980,PHID-USER-rbcxdzszrm6s4izt67kj,PHID-TASK-p565vznerestdkazvkox,task_description,resolved
+BetaFeatures: Skin warning message pulls in skin names regardless of whether skin is available,"
+
+*** This bug has been marked as a duplicate of bug 58623 ***",1395898645,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-p565vznerestdkazvkox,task_subcomment,NA
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","I don't know what it should be, but the following is not very clear:
+
+Error loading data from server: error. Would you like to retry?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=39057
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43147",1395869100,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yigtzgsn2qahxek7rusl,task_description,resolved
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","With the above patch, the former message:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500. Would you like to retry?
+
+… turns into:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500: Page Fetch failure for ""BADURL"": Error: getaddrinfo
+    ENOTFOUND. Would you like to retry?
+
+Which is not ideal, but at least describes things a bit. Marking this as FIXED.",1409684423,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yigtzgsn2qahxek7rusl,task_subcomment,NA
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","Change 157775 merged by jenkins-bot:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409681809,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yigtzgsn2qahxek7rusl,task_subcomment,NA
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","Change 157775 had a related patch set uploaded by Jforrester:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409669840,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yigtzgsn2qahxek7rusl,task_subcomment,NA
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","(In reply to Roan Kattouw from comment #0)
+> I don't know what it should be, but the following is not very clear:
+> 
+> Error loading data from server: error. Would you like to retry?
+
+Maybe:
+
+| The editor's contact with the server failed (5xx). Would you like to retry?
+
+?",1395882419,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yigtzgsn2qahxek7rusl,task_subcomment,NA
+VisualEditor: Icons for citation tool don't all appear to be the same (visual) weight — the book icon looks darker than the others,"The icons for the new citation tool don't all appear to be the same weight.  The book icon looks darker than the others, which makes it seem like it's more important than other others, or perhaps that the others are non-functional/grayed out.  Perhaps it could be a dark gray?
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1395859980,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-tjsegrcnpxgmtmoqmaq2,task_description,resolved
+VisualEditor: Icons for citation tool don't all appear to be the same (visual) weight — the book icon looks darker than the others,Fixed with the new icons.,1401472252,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tjsegrcnpxgmtmoqmaq2,task_subcomment,NA
+VisualEditor:  Citation tool adds stray line break at the end of the template,"Intention:
+Add a citation with the new citing tool
+
+Steps to Reproduce:
+1. Add a citation.
+
+2. Look at the dirty diff that results.
+
+
+
+Actual Results:  
+The new cite tool produces this
+
+<ref>{{Cite web|url = http://example.com|title = Example Title|date = 2014|last = Expert|first = Alice}}
+</ref> 
+
+(on two lines) rather than one line that it should:
+
+<ref>{{Cite web|url = http://example.com|title = Example Title|date = 2014|last = Expert|first = Alice}}</ref> 
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395859560,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qp5fiwrkazudpv3vzwkc,task_description,resolved
+VisualEditor:  Citation tool adds stray line break at the end of the template,"This may possibly have been fixed? Seems to now work correctly (on one line) for me, see e.g. http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox&diff=92409&oldid=91378",1399336298,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qp5fiwrkazudpv3vzwkc,task_subcomment,NA
+VisualEditor:  Citation tool adds stray line break at the end of the template,"Do you have a link to an example diff? I'm trying to reproduce this locally but I can't, in neither Chrome nor Firefox.",1399333539,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qp5fiwrkazudpv3vzwkc,task_subcomment,NA
+VisualEditor:  Citation tool adds stray line break at the end of the template,"That's not the meaning of the term ""dirty diff"". :-) But yes.",1395887579,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qp5fiwrkazudpv3vzwkc,task_subcomment,NA
+VisualEditor removes a colon from the first existing indented list item when adding another item to the list,"When adding an item to a list, VisualEditor is stripping the first indent (colon in wikisyntax) when adding a new one in the list.
+
+Example:
+https://www.mediawiki.org/w/index.php?title=User%3AKeegan_%28WMF%29%2Fsandbox&diff=939610&oldid=939609
+
+Steps to reproduce:
+1. Create an indented list, save
+   :*a
+   :*b
+   :*c
+2. Add a new item to the list, looks fine before saving
+   :*a
+   :*b
+   :*q
+   :*c
+3. Save, and the result is
+   *a
+   :*b
+   :*q
+   :*c
+
+Windows 7/Chrome 33.0.1750.154 m & Firefox 28.0
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1395768720,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-3egehmh4zidndvgzwfvm,task_description,resolved
+VisualEditor removes a colon from the first existing indented list item when adding another item to the list,The bug doesn't happen any more: https://en.wikipedia.beta.wmflabs.org/w/index.php?title=T65079&diff=499304&oldid=499303&diffmode=source,1625945177,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3egehmh4zidndvgzwfvm,task_subcomment,NA
+VisualEditor removes a colon from the first existing indented list item when adding another item to the list,...adding an item to *a bullet* list...,1395776546,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-3egehmh4zidndvgzwfvm,task_subcomment,NA
+VisualEditor: Long parameter names get hidden under their input fields,"This happen when you're editing a template, or, if you're just adding it instead, once you add the parameter as well.
+For example of very long names try to change Infobox settlement in https://en.wikipedia.org/wiki/Ames,_Iowa?veaction=edit .
+Since some of these parameters only differ at the very end, like Fram noted, the user can be confused when seeing what is apparently the same parameter just repeated. Some of them also lack a description, so the description alone wouldn't solve the problem.
+While he suggests that ""a pop-up that displays the full name may be some initial solution"", I think adjusting the character size or window size might work better.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395754800,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-o7phiemau5qvzpjncsca,task_description,resolved
+VisualEditor: Long parameter names get hidden under their input fields,We fixed this by making them not on the side but above.,1402553952,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o7phiemau5qvzpjncsca,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"See reproduction below
+```
+[subbu@earth:~/work/wmf/parsoid] cat /tmp/wt
+[[Imagem:Ellipse PLS en.png|256px|thumb|Parâmetros de uma elipse.]]
+[subbu@earth:~/work/wmf/parsoid] php bin/parse.php --wt2wt < /tmp/wt
+[[Imagem:Ellipse PLS en.png|256px|thumb|Parâmetros de uma elipse.]]
+
+[subbu@earth:~/work/wmf/parsoid] php bin/parse.php --domain pt.wikibooks.org < /tmp/wt > /tmp/old.html
+[subbu@earth:~/work/wmf/parsoid] cp /tmp/old.html /tmp/new.html
+
+... edit new.html and change the image ...
+
+[subbu@earth:~/work/wmf/parsoid] php bin/parse.php --domain pt.wikibooks.org --html2wt < /tmp/new.html 
+[[Ficheiro:Ellipse_PLS_en.snv|256px|thumb|Parâmetros de uma elipse.]]
+```
+
+----------
+On this edit
+https://pt.wikibooks.org/wiki/Matem%C3%A1tica_elementar/Trigonometria/Arcos_e_%C3%A2ngulos?diff=270018
+VisualEditor replaced the good namespace ""Imagem"" by ""Ficheiro"", which is worse.
+The word ""Ficheiro"" is not appropriated here:
+* It is not used in the pt-BR variant, so per discussion in the community it should be avoided whenever it is possible[1][2]. And it is always possible to be avoid this word if the file is an image (because ""Imagem"" is a common word in pt-BR and pt-PT);
+* It replaced a precise description of the file by a generic one. There is nothing wrong in saying that ""Foo.PNG"" is a image.
+
+[1] https://pt.wikipedia.org/wiki/WP:Esplanada/propostas/Incentivar_o_uso_de_%22Imagem%22_em_vez_de_%22Arquivo%22_ou_%22Ficheiro%22_(12mar2011)
+[2] http://sourceforge.net/p/pywikipediabot/bugs/1323/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395750540,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-orropflowqhqpd4oiqpd,task_description,open
+Parsoid should not replace namespace aliases by other translations,"Now I found the recently created and fixed {T237040}. Can we assume that after that change currently no automatic replacement happens, and that this issue can be closed, too, even if the original cause might have been different?",1572690784,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This happened in dewiki: https://de.wikipedia.org/w/index.php?title=Totengr%C3%A4ber_(K%C3%A4fer)&type=revision&diff=193594417&oldid=191699592
+And the funny thing is that some users can reproduce it, and some can't, and sometimes the behaviour just changes. When I tested a few days ago, VE/Parsoid changed every Bild (""Image"") to Datei (""File""), but when I tested again today, no such automatic changes occurred, even with the same edits in the same articles.",1572689086,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This is still happening:
+https://pt.wikipedia.org/w/index.php?diff=42819013
+https://pt.wikipedia.org/w/index.php?diff=42819531
+https://pt.wikipedia.org/w/index.php?diff=42819605
+https://pt.wikipedia.org/w/index.php?diff=42819868",1436464859,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This is still happening:
+https://pt.wikipedia.org/w/index.php?diff=42819013
+https://pt.wikipedia.org/w/index.php?diff=42819531
+https://pt.wikipedia.org/w/index.php?diff=42819605",1436462506,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This is still happening:
+https://pt.wikipedia.org/w/index.php?diff=42819013
+https://pt.wikipedia.org/w/index.php?diff=42819531",1436462430,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This is still happening:
+https://pt.wikipedia.org/w/index.php?diff=42819013",1436459158,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"https://pt.wikibooks.org/w/index.php?title=Matem%C3%A1tica_elementar/Trigonometria/Arcos_e_%C3%A2ngulos&oldid=264430&veaction=edit
+
+http://parsoid-lb.eqiad.wikimedia.org/_rt/ptwikibooks/Matem%C3%A1tica_elementar/Trigonometria/Arcos_e_%C3%A2ngulos?oldid=264430
+
+I tried a vedit on that version and ran rt on it, for good measure. The issue seems to be resolved but please reopen if I'm mistaken.",1416972936,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,Sorry for the slow triage here; I'm not sure if this is still an issue in Parsoid?,1411583056,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+VisualEditor: Pressing delete on an indented list item does not unindent it rather merges it with the previous item in a numbered list,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add a numbered or bullet list
+3.Edit the first item of the list
+4.Add indentation to it
+5.Place the cursor just before the list
+6.Press delete
+
+Observed Result:
+Instead of unindenting it, it rather merges it with the previous line .
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page: https://test2.wikipedia.org/wiki/24thmarchrome?veaction=edit
+
+**See Also**: {T63863}",1395707640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-k5farhnvyfzzpgjvizgv,task_description,open
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"screenshot 1
+
+Steps to reproduce:
+
+1.Go to the media settings of an image
+2.Create a slug 
+3.Try to insert a special character/link/reference in the slug
+
+
+Observed Result:
+
+It shows an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 63
+Also if it is an inspector it goes all blank
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13082}",1395688860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_description,resolved
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,Verified the fix in production,1414101150,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,Verified the fix in test2,1413504401,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,This is now fixed with latest slug work I guess.,1413415239,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,Huh. Darn.,1412807923,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"Nope, this bug must have a different cause because it occurs in test2 and production as well.",1412806887,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"That was bug 71825, now fixed.",1412799442,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"This issue has resurfaced with error as ""Uncaught Error: offset -1 out of bounds"" when trying to insert a link/special character in a slug.",1412789418,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,I believe/hope this is now fixed…,1401475904,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,Try the first image on this page:http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome?veaction=edit,1395689025,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"Created attachment 14893
+screenshot 2
+
+**Attached**: {F13083}",1395688906,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Gallery code gets added in the Table of Content and gets overlapped with the next item in the VE mode,"Screenshot
+
+Steps to reproduce:]
+
+
+1.Open a page with VE
+2.Select the whole line just preceding a Heading
+3.Insert a gallery with some invalid code: for example:
+
+
+An example image. It has flowers and flowers It has flowers and flowersIt has flowers and flowersIt has flowers and flowersIt has flowers and flowersIt has flowers and flowers
+
+
+Observed Result:
+1. The text inside gallery inspector gets overlapped with the heading 
+2. After saving you will see the gallery code got inserted in the TOC 
+3.The heading got converted to paragraph format
+4.The gallery code is appearing just beside the heading in paragraph format ( in addition to appearing inside the gallery)
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Newpagetocheck62934
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12890}",1395444300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gchq7jmbvglbydxeihay,task_description,open
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"For example, action=visualeditor is an internal API for the VisualEditor client to talk to its server, isn't really useful for third parties, and isn't remotely stable. However, because it's a built-in assumption that APIs are for third-party use rather than every tool being the first client of its API, this isn't possible. Boo.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1395361800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dsoezmplcqkvtg5il36e,task_description,resolved
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 1010987 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] api: Tweak the 'internal' API label to explain that they shouldn't be used%%%
+https://gerrit.wikimedia.org/r/1010987",1710453188,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 1010987 had a related patch set uploaded (by Jforrester; author: Jforrester):
+%%%[mediawiki/core@master] api: Tweak the 'internal' API label to explain that they shouldn't be used%%%
+https://gerrit.wikimedia.org/r/1010987",1710367202,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 160798 merged by jenkins-bot:
+API: HTMLize and internationalize the help, add Special:ApiHelp
+
+https://gerrit.wikimedia.org/r/160798",1413238801,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,Taken over by Brad.,1412969071,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 158546 abandoned by Legoktm:
+API: Implement concept of 'internal' API modules
+
+Reason:
+Superseded by Ib14c00df06d85c2f6364d83b2b10ce34c7f513cc
+
+https://gerrit.wikimedia.org/r/158546",1412929000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 160798 had a related patch set uploaded by Anomie:
+API: HTMLize and internationalize the help, add Special:ApiHelp
+
+https://gerrit.wikimedia.org/r/160798",1410895615,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 158546 had a related patch set uploaded by Alex Monk:
+Make it possible for API modules to hide their documentation behind an 'includeinternal' parameter
+
+https://gerrit.wikimedia.org/r/158546",1409874405,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"(In reply to Brad Jorsch from comment #2)
+> (In reply to James Forrester from comment #0)
+> > For example, action=visualeditor is an internal API for the VisualEditor
+> > client to talk to its server, isn't really useful for third parties, and
+> > isn't remotely stable. However, because it's a built-in assumption that APIs
+> > are for third-party use rather than every tool being the first client of its
+> > API, this isn't possible. Boo.
+> 
+> Ideally a tool's API would be perfectly usable by third parties, not
+> something overly specific to the one tool's internal implementation,
+> although that may not always be possible. I don't know which is the case for
+> VE's API or if it's just that it's not yet stable.
+
+Completely agreed in the general case that we should encourage tools to create APIs that are useful for third parties. VE, as an exclusive consumer of APIs, comes up against the problem of the existing APIs in MW and extensions not actually providing the necessary features — we're well aware of how bad this is in some areas! My view is that all tools, core and otherwise, should be expected to be the first client of their own, normally public API rather than magically and silently reach into the codebase to make changes that other tools cannot (EditPage.php, I'm looking at you).
+
+With VE's API, it's a combination of:
+
+* not yet sufficiently stable (new features and formats being added each week or so),
+* not a long-term prospect (this exists mostly to code around a lack of genericness in MW, and eventually we'll fix that rather than keep this), and
+* not being a 'real' API (much of the content of the API is available from other API calls, but having a single call improves efficiency for VE's client).
+
+As an illustrated example, see this change made this week to VE's API to add hinting to links that don't exist (so VE can add red colouring): https://gerrit.wikimedia.org/r/#/c/118045/14/ApiVisualEditor.php
+
+This:
+* changed just yesterday,
+* is intended to be replaced reasonably soon with a proper Parsoid post-processor to sit in front of the HTML+RDFa cache for making changes that are currently parser cache-busting like this, and
+* is trivially something that can be provided by the pre-existing public APIs.",1395413828,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Brainstorming:
+
+Add a method, something like ""isInternalApi"", to ApiBase that by default returns false.
+
+Add a boolean ""includeinternal"" parameter to ApiHelp, which when specified would include these internal API modules.
+
+Adjust ApiBase::makeHelpMsg() to take a boolean indicating whether internal API modules should be shown (i.e. whether ""includeinternal"" was given to action=help).
+
+Then ApiHelp::execute(), if not passed a ""modules"" parameter explicitly, would check the flag and isInternalApi() to decide whether to include each module in the output. Modules like ApiQuery that have submodules would use the new parameter to their ::makeHelpMsg() methods to do the same.
+
+The help output should also include indication of whether a module is internal, much like it now does for stuff like ""This module only accepts POST requests"".
+
+I'm not sure whether we should also try to adjust the output of getAllowedParams() to omit these internal modules from the valid values for ""action"", or if that would be too expensive for too little gain (if we did do that, we'd need to do like how ApiPageSet handles generators). We certainly should be sure not to omit the internal modules for action=paraminfo though.
+
+
+(In reply to James Forrester from comment #0)
+> For example, action=visualeditor is an internal API for the VisualEditor
+> client to talk to its server, isn't really useful for third parties, and
+> isn't remotely stable. However, because it's a built-in assumption that APIs
+> are for third-party use rather than every tool being the first client of its
+> API, this isn't possible. Boo.
+
+Ideally a tool's API would be perfectly usable by third parties, not something overly specific to the one tool's internal implementation, although that may not always be possible. I don't know which is the case for VE's API or if it's just that it's not yet stable.",1395410558,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,Maybe we should have not deprecated the ajax interface.,1395363976,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+VisualEditor: Image flickers but shield stays in the correct position while dragging the page on Mac,"Steps to reproduce:
+
+If you drag a page down which contains an image large enough to go beyond the border of developer tool and has the developer tool open ,the image seems to flicker and appear again while the shield stays in the same position.
+
+Try this page.
+See the Video Capture attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395359220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2zikzspgdiyrdhq43hy6,task_description,resolved
+VisualEditor: Image flickers but shield stays in the correct position while dragging the page on Mac,"Yes, this is not happening anymore",1404855686,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2zikzspgdiyrdhq43hy6,task_subcomment,NA
+VisualEditor: Image flickers but shield stays in the correct position while dragging the page on Mac,I think this is now working.,1404851230,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2zikzspgdiyrdhq43hy6,task_subcomment,NA
+VisualEditor: Image flickers but shield stays in the correct position while dragging the page on Mac,Page:https://test2.wikipedia.org/wiki/Wmf19?veaction=edit,1395359277,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2zikzspgdiyrdhq43hy6,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a small default sized SVG image for example a SVG image with 50x50px :https://en.wikipedia.org/wiki/File:Gnome-fs-home.svg
+
+3.Now Save the page
+
+Observed Result:
+The image size that appears after saving is much larger (200x200px) 
+
+See the screenshot attached.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13403}",1395351720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_description,resolved
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,Verified the fix in en.wiki running wmf 8,1402687864,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"Change 137442 merged by jenkins-bot:
+Followup to small SVG default size
+
+https://gerrit.wikimedia.org/r/137442",1401925466,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"Change 137442 had a related patch set uploaded by Mooeypoo:
+Followup to small SVG default size
+
+https://gerrit.wikimedia.org/r/137442",1401911708,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"Change 137054 merged by jenkins-bot:
+Small SVG images should still adhere to default thumb size
+
+https://gerrit.wikimedia.org/r/137054",1401903798,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"Change 137054 had a related patch set uploaded by Mooeypoo:
+Small SVG images should still adhere to default thumb size
+
+https://gerrit.wikimedia.org/r/137054",1401817797,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Since Parsoid already runs an API call for each image given to it in wikitext, it would be extremely helpful for the editing in terms of user experience if the call also asked for the original dimensions.
+
+At the moment, VisualEditor asks for details from the API on each edited image to get its original dimensions. When this is done for the edit dialog the asynchronous call works fine because we don't mind letting the user wait the seconds it takes the async call to finish.
+
+But when the user resizes images with the mouse (with the resize handles) the information about original dimensions usually comes too late. The user may (and often does) resize the image to above its limits, and by the time VE gets the API response, the user is already done resizing. On top of that, calculating aspect ratio from original size is a lot more accurate than calculating it from the given (usually smaller) size, though, granted, this is a lot less crucial.
+
+We have some fall backs and we are considering an after-the-fact user experience ideas to make this work, but it would be extremely helpful if the information was already available when it comes from Parsoid -- especially since Parsoid already asks for information from the API.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395339300,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-hzbsw24557jvqnw3xxby,task_description,resolved
+Make available original image dimensions info from the API in Parsoid DOM.,"Disregard, this was already closed",1436986700,PHID-USER-6vqtwycrvuonr2xo7bqi,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Chiming in from iOS, we'd love to know the current thumbnail and original size so we can handle scaling up to higher resolutions elegantly.  Is it worth making which properties to include configurable?  Maybe some clients don't want it, maybe some do?",1436986671,PHID-USER-6vqtwycrvuonr2xo7bqi,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"@esanders, @jdforrester-WMF: perhaps you VE guys should add one?  I think @mooeypoo was doing the original work here (a year ago!).",1428078595,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,Is there a task for VE to use this now?,1428062303,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"This will go out on Monday. Roan confirmed that there are no VE changes that are required. Also for a while, VE should be prepared to accept HTML with / without these attributes till all the revisions turn over in RESTBase.",1427414195,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Change 195666 merged by jenkins-bot:
+T64881: Add original dimension information for images.
+
+[[https://gerrit.wikimedia.org/r/195666]]",1427413837,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Change 195798 abandoned by Cscott:
+T64881: Add original dimension information for images to data-mw.
+
+Reason:
+Abandoned in favor of https://gerrit.wikimedia.org/r/195666
+
+[[https://gerrit.wikimedia.org/r/195798]]",1427406846,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,Should missing/error images have `data-file-width`/`data-file-height` attributes?  Right now I'm not adding them.,1427403950,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Restating subbu's (b) slightly, for more accuracy: Mediaviewer already adds it (to PHP parser output), and so other gadgets might expect it.",1426606626,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Summary of IRC conversation:
+
+So, if we had to add this info, it makes sense to add data-file-width and data-file-height attributes because (a) it is read only (b) mediaviewer and other gadgets already expect it and when Parsoid html is used for read views, those applications don't break suddenly (c) most pages have few images relative to the size of the DOM itself, so the DOM bloat is expected to be minor.
+
+Parsoid is probably already handling HTML invalidation (via parsoid cache update jobs, to be confirmed for sure) and so there are no new cache invalidation issues that crop up from this change.",1426544643,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Change 195798 had a related patch set uploaded (by Cscott):
+T64881: Add original dimension information for images to data-mw.
+
+[[https://gerrit.wikimedia.org/r/195798]]
+",1426029924,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Uploaded a patch ^ which uses `data-file-width` and `data-file-height` to match the PHP HTML output created by the MediaViewer extension.
+
+Perhaps this bloats the DOM, and we should use data-mw instead.  I don't have a strong opinion here.  My hand-wavy argument is that data-mw should be used for properties which are important/signficiant for editors in terms of defining a particular wikitext serialization.  These new `data-file-*` properties are not consulted for WTS, they are just ignored.
+
+(But perhaps we should consult these in order to serialize upright images correctly?)",1426020950,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Change 195666 had a related patch set uploaded (by Cscott):
+T64881: Add original dimension information for images.
+
+[[https://gerrit.wikimedia.org/r/195666]]
+",1426020749,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"What do we want to happen if the target image doesn't exist?  Presumably leave off the attributes, right?",1426020101,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,That comes from Multimedia Viewer or some such.,1424981710,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,Mediawiki core seems to use `data-file-width` and `data-file-height` on `<img>` tags for this.  I wonder when that was added to core?,1424981266,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,Per conversations last week this should be reprioritised.,1423251809,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"The size concern also matters less once we move data-mw out of the DOM. There's still the minor nuisance of having some read-only attributes in data-mw, which is otherwise a read-write interface.
+
+Maybe it would make sense to group dimensions & image type in a separate 'imageinfo' sub-object inside data-mw that is documented to be read-only. The grouping & naming should make it clearer that this is read-only info only, even without looking at the docs.",1402005070,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"On top of the dimensions, it would also be helpful to get the 'mediatype' property of images, separating them between ""DRAWING"" and ""BITMAP"". The two types behave differently, especially with size considerations.
+
+It is useful for VE to know (we request this now with our separate api call) but it might actually make sense to categorize the difference between the images for other purposes.",1401926981,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"We have a new strategy for serializing square bounding boxes that will be helped by having original image size hanging around, so we will probably put original image size in data-mw.",1396301812,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"I do agree we should be careful, but I think this is worth including. It's really useful and costs very little.",1395342449,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"(In reply to C. Scott Ananian from comment #1)
+> I'm not convinced we should be bloating our Parsoid DOM representation with
+> original size information which can easily be obtained from the imageinfo
+> API.  In order to do a proper resize, you are probably going to have to
+> fetch the original image anyway so that things don't get blurry when you
+> scale up.
+> 
+> But I'm interesting in hearing other thoughts.
+
+We don't fetch the original image unless the new size is the image's original dimensions – we ask MW for the thumbnail of that size. We certainly don't ask e.g. for a 10MiB original 5000x4000px image when the user is just resizing from 250x200px to 300x240px. Also, we fetch the new image /after/ the image is resized.",1395341768,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"I'm not convinced we should be bloating our Parsoid DOM representation with original size information which can easily be obtained from the imageinfo API.  In order to do a proper resize, you are probably going to have to fetch the original image anyway so that things don't get blurry when you scale up.
+
+But I'm interesting in hearing other thoughts.",1395339892,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+VisualEditor: Save dialog animates size while animating open if it was large when it was closed,"1. Open save dialog. It animates normally to small size.
+2. Click Review changes. Dialog animates to medium size.
+3. Close dialog.
+4. Open dialog again.
+
+When the dialog opens again, it's still medium size from last time, which we animate back to small. But this animation is concurrent with the scale 0.5->1.0 opening animation, and the result of the two animations combined is pretty strange-looking.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395279120,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-25trlvhkq536lvbbruzl,task_description,resolved
+VisualEditor: Save dialog animates size while animating open if it was large when it was closed,Verified the fix in production (en.wiki),1403561072,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-25trlvhkq536lvbbruzl,task_subcomment,NA
+VisualEditor: Save dialog animates size while animating open if it was large when it was closed,Yay Trevor. :-),1402551181,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-25trlvhkq536lvbbruzl,task_subcomment,NA
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,"screenshot-1
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image 
+3.Go to Media Settings>General Settings 
+4.Click outside the caption textbox
+5.Click on link inspector icon
+
+Observed Result:
+The link inspector opens outside the textbox.
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13306}",1395274860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vggdfu44niwggkew2ust,task_description,resolved
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,Verified the fix in production (en.wiki),1403301925,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vggdfu44niwggkew2ust,task_subcomment,NA
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,Verified the fix in test2 running wmf9,1402692374,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vggdfu44niwggkew2ust,task_subcomment,NA
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,I believe that this one is now fixed courtesy of Ed's changes this week or last.,1402549198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vggdfu44niwggkew2ust,task_subcomment,NA
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,"Created attachment 14866
+screenshot
+
+**Attached**: {F13307}",1395274955,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vggdfu44niwggkew2ust,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","Steps to reproduce:
+
+1.Open a page with VE
+2.Now change the image settings to Right,Basic and Border 
+3.Save the page
+
+Observed Result:
+In the wikitext the options ""Right"" and ""Border"" are missing
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395266640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_description,resolved
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext",Verified the fix in test2,1401498423,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext",Verified the fix in Betalabs,1401311647,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext",Skipping right (and just using default) is OK for thumb and frame (but not frameless or basic).,1400630689,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","So, this is still happening.In addition to that, for all Right aligned Images regardless of its type the alignment options gets missing from the wikitext",1400629615,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","CE responds correctly to the type and alignment shifts, and yet something seems to goes awry in the DM. I'm checking into the issue.",1395339648,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","Parsoid does the right thing with the input giving the expected output:
+
+<figure class=""mw-default-size mw-halign-right mw-image-border"" typeof=""mw:Image"" data-parsoid=""{&quot;optList&quot;:[{&quot;ck&quot;:&quot;thumbnail&quot;,&quot;ak&quot;:&quot;thumb&quot;},{&quot;ck&quot;:&quot;left&quot;,&quot;ak&quot;:&quot;left&quot;},{&quot;ck&quot;:&quot;caption&quot;,&quot;ak&quot;:&quot;Foo&quot;}],&quot;dsr&quot;:[0,35,2,2]}""><a href=""./File:Example.png"" data-parsoid=""{&quot;a&quot;:{&quot;href&quot;:&quot;./File:Example.png&quot;},&quot;dsr&quot;:[2,null,null,null]}""><img resource=""./File:Example.png"" src=""//upload.wikimedia.org/wikipedia/en/thumb/7/70/Example.png/220px-Example.png"" height=""238"" width=""220"" data-parsoid=""{&quot;a&quot;:{&quot;resource&quot;:&quot;./File:Example.png&quot;,&quot;height&quot;:&quot;238&quot;,&quot;width&quot;:&quot;220&quot;},&quot;sa&quot;:{&quot;resource&quot;:&quot;File:Example.png&quot;}}""></a><figcaption data-parsoid=""{&quot;dsr&quot;:[null,33,null,null]}"">Foo</figcaption></figure>
+
+->
+
+[[File:Example.png|Foo|right|border]]",1395266959,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","Created attachment 14864
+Screenshot
+
+**Attached**: {F13291}",1395266767,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: Centre floated image next to right floated image means image is shown partially offscreen, and shield is put in the wrong place","Screenshot
+
+Steps to reproduce:
+
+This issue was found specifically on this page for the second image:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/19thMarChrome?veaction=edit
+
+The original settings for the image was Right,Basic and Border.
+
+When I changed the image position to ""Centre"", it appeared distorted with irregular highlight box for the image
+
+See the screenshot attached:
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62590
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66228
+
+**Attached**: {F13287}",1395265200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-py5gbrzeyuwgfnhmvab3,task_description,open
+"VisualEditor: Centre floated image next to right floated image means image is shown partially offscreen, and shield is put in the wrong place","No, definitely still happening.
+
+Issue seems to be that the centre-floated image is moved down by the lack of space to below the right-floated image, but the document's length is not extended (so it runs off the edge of the window) and the shield remains in place (so you can click on the image and go to the File: page)…",1401312865,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-py5gbrzeyuwgfnhmvab3,task_subcomment,NA
+"VisualEditor: Centre floated image next to right floated image means image is shown partially offscreen, and shield is put in the wrong place",This should be fixed now.,1401312083,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-py5gbrzeyuwgfnhmvab3,task_subcomment,NA
+"VisualEditor: Centre floated image next to right floated image means image is shown partially offscreen, and shield is put in the wrong place",This doesn't happen when the image is by itself on the page (or inside a bunch of paragraphs) so I am pretty sure this is due to the fact the image is within two PRE tags.,1395339578,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-py5gbrzeyuwgfnhmvab3,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Right now, MWLinkInspector needs to know exactly how to construct a new link annotation with the right attributes. This pattern is repeated (albeit somewhat less egregiously) for every single annotation and node created by any UI component anywhere. This is horrible. The DM should provide helpers so UI classes can much more easily create linmod elements from data.
+
+----
+
+Update, 2015-08-25: We now have a bespoke method for the MW link inspector, but the general pattern across VE's UI is still there.",1395194460,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-25agkmu2ndsyxxwmvqos,task_description,open
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Change 233727 merged by jenkins-bot:
+Use new internal link builder
+
+[[https://gerrit.wikimedia.org/r/233727]]",1440518475,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Change 233727 had a related patch set uploaded (by Esanders):
+Use new internal link builder
+
+[[https://gerrit.wikimedia.org/r/233727]]
+",1440517877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Change 231155 merged by jenkins-bot:
+Builder for ve.dm.MWInternalLinkAnnotation
+
+[[https://gerrit.wikimedia.org/r/231155]]",1440176289,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"From IRC:
+> James_F: RoanKattouw says that for T64816 something that every UI tool can call (name not really thought of; #constructMe() or whatever) was what he was thinking.
+
+The patch in https://gerrit.wikimedia.org/r/231155 is just a tiny start, it makes it a little easier to construct correct `ve.dm.MWInternalLinkAnnotation` objects given a `mw.Title`.  It doesn't address the bigger picture, since I don't really have  a solid grasp on the bigger picture.",1439486649,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Change 231155 had a related patch set uploaded (by Cscott):
+Builder for ve.dm.MWInternalLinkAnnotation
+
+[[https://gerrit.wikimedia.org/r/231155]]
+",1439414684,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"Duplicated logic is bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395179580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_description,resolved
+VisualEditor: Extract red link API code from VE and put into Parsoid,"So I verified that the correct color is showing up for different kinds of links. Regarding the API requests, I am not sure which ones I should consider as ""additional"". I have moved this task to Engineering QA if that's a better suited task for engineers. 
+>>! In T64803#4976829, @Esanders wrote:
+> QA: Check that links are still the correct colours, and that additional API requests aren't being fired when initialising the page.
+
+",1553195405,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"Change 492358 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ApiVisualEditor: Remove red-link cache warming
+
+[[https://gerrit.wikimedia.org/r/492358]]",1550918218,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"QA: Check that links are still the correct colours, and that additional API requests aren't being fired when initialising the page.",1550862234,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"Change 492358 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] ApiVisualEditor: Remove red-link cache warming
+
+[[https://gerrit.wikimedia.org/r/492358]]",1550858154,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,">>! In T64803#3380142, @Esanders wrote:
+> Red link code is now in Parsoid so can be removed from VE
+
+Will need us to round-trip new links, though. Right now we pick how to render them with local code which is pretty speedy.",1498651711,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,Red link code is now in Parsoid so can be removed from VE,1498503516,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"(In reply to Gabriel Wicke from comment #2)
+> For static pages we should be able to do this with CSS retrieved from an
+> API. We'll provide this API for normal pages.
+
+*nods*
+
+
+> For dynamic hints during editing we'd still need to inject styles
+> dynamically. The latter would probably remain VE-specific.
+
+Yeah, but Flow/etc. may want to style too.",1411609546,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"For static pages we should be able to do this with CSS retrieved from an API. We'll provide this API for normal pages.
+
+For dynamic hints during editing we'd still need to inject styles dynamically. The latter would probably remain VE-specific.",1411608588,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"(In Parsoid or whatever; the point is, this code should be re-useable by Flow, OCG and anyone else rather than buried inside VE.)",1411594065,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Slugs don't animate when jumping from one to another,"1. Create a page with just a table
+2. Focus the top slug (it animates)
+3. Focus the bottom slug
+
+Expected:
+Top slug collapses, bottom slug expands
+
+Observed:
+Nothing
+
+The logic for adding animation classes only checks to see if we've gone from in a slug to not in a slug, so we'll need to check if the slug has changed as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395150300,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-l2jl4edzrpyacaksfsyv,task_description,resolved
+VisualEditor: Slugs don't animate when jumping from one to another,"Change 119287 merged by jenkins-bot:
+Check if newly focused slug is different to previous slug
+
+https://gerrit.wikimedia.org/r/119287",1395164477,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l2jl4edzrpyacaksfsyv,task_subcomment,NA
+VisualEditor: Slugs don't animate when jumping from one to another,"Change 119287 had a related patch set uploaded by Esanders:
+Check if newly focused slug is different to previous slug
+
+https://gerrit.wikimedia.org/r/119287",1395150372,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l2jl4edzrpyacaksfsyv,task_subcomment,NA
+VisualEditor: The Save dialog box prompts to fill out a new captcha if a user goes to review changes section and switches back after filling out the captcha field for the first time,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an external link in the VE so that it prompts to enter a captcha 
+3.Click on the Save Page button
+4.Click on the Save Page button on the Save dialog
+5.Fill up the textbox for the captcha
+6.Click on ""Review Your Changes""
+7.Return to the save form
+
+
+Observed Result:
+It again asks you to fill up a new captcha
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395106620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jvt3xyvqjt3cysi2vihe,task_description,resolved
+VisualEditor: The Save dialog box prompts to fill out a new captcha if a user goes to review changes section and switches back after filling out the captcha field for the first time,Verified the fix in Betalabs,1398894727,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jvt3xyvqjt3cysi2vihe,task_subcomment,NA
+VisualEditor: The Save dialog box prompts to fill out a new captcha if a user goes to review changes section and switches back after filling out the captcha field for the first time,"Change 129830 merged by jenkins-bot:
+Call clearAllMessages in setup instead of swapPanel on the save dialog
+
+https://gerrit.wikimedia.org/r/129830",1398881956,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jvt3xyvqjt3cysi2vihe,task_subcomment,NA
+VisualEditor: The Save dialog box prompts to fill out a new captcha if a user goes to review changes section and switches back after filling out the captcha field for the first time,"Change 129830 had a related patch set uploaded by Alex Monk:
+Call clearAllMessages in setup instead of swapPanel on the save dialog
+
+https://gerrit.wikimedia.org/r/129830",1398462405,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jvt3xyvqjt3cysi2vihe,task_subcomment,NA
+Improve VisualEditor's performance on tablet devices,"Kenan reports some sluggishness on iPads, and will update this bug with more details.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395094920,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-bsy6cd23dxzzu4de3gqm,task_description,invalid
+Improve VisualEditor's performance on tablet devices,"General ""improve performance of X"" tasks are not actionable in the absence of specific acceptance criteria, so this isn't really a valid task. ",1534438142,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-bsy6cd23dxzzu4de3gqm,task_subcomment,NA
+Improve VisualEditor's performance on tablet devices,Not actionable as a task; this is a tracker.,1428521843,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bsy6cd23dxzzu4de3gqm,task_subcomment,NA
+Improve VisualEditor's performance on tablet devices,Is this a bug or a tracker?,1395095390,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bsy6cd23dxzzu4de3gqm,task_subcomment,NA
+VisualEditor: Provide a clean interface for rendering detached CE nodes,"In ve.ce.MWTreferenceListNode we do something quite evil, which is creating a one-off CE node, adding it's $element to the DOM, then destroying it. This happens to work because destroy doesn't abort async rendering processes, but in the future this may change. It's also quite messy to do things this way, and all we really need is a simple way to get a rendering from a model.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394842740,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-xgahiq6goif4ltykeqno,task_description,resolved
+VisualEditor: Provide a clean interface for rendering detached CE nodes,ve.ui.PreviewElement probably fits the bill here. See T94130 (which might have been a duplicate of this).,1580721921,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xgahiq6goif4ltykeqno,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add a caption to it
+3.Save the page 
+4.Reopen the page
+5.Go to the Media Settings of that image and change the image type to thumbnail/frame
+
+
+Observed Result:
+The image highlight box does not appear properly, caption also gets missing
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/14thmarchwmf18
+
+Try the image in this page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64563
+
+**Attached**: {F12893}",1394842020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_description,resolved
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"(In reply to ryasmeen from comment #7)
+> Created attachment 15871 [details]
+> Screenshot
+> 
+> Making an image frame-right or frame-left makes the highlight of the image
+> too big to go beyond the CE, not sure if this should be tagged with this bug
+> or not.
+> 
+> See the screenshot attached
+
+I think that's a distinct issue. :-(
+
+**Attached**: {F12897}",1404864095,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,bug* not bag :|,1404860275,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Created attachment 15871
+Screenshot
+
+Making an image frame-right or frame-left makes the highlight of the image too big to go beyond the CE, not sure if this should be tagged with this bag or not.
+
+See the screenshot attached
+
+**Attached**: {F12897}",1404860239,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,This now appears to be working fine?,1404851133,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Edited wrong bug, ignore change 137040 and above comment.",1402923170,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Issue is with dm selection, not shields/highlights.",1402923055,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Change 137040 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE (ish)] Track orignal data position in insertion operations
+
+https://gerrit.wikimedia.org/r/137040",1402922995,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,This issue did not get resolved with new image model.,1400199678,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Created attachment 15299
+Screenshot april 5th
+
+**Attached**: {F12895}",1399317964,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: Make CE-surface fixes to make TMH's media items display correctly,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394835240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5s7zqldna73gv3hkyshd,task_description,resolved
+VisualEditor: Make CE-surface fixes to make TMH's media items display correctly,"For the most part, this seems to have been done, sometime between 2014 and now. CE nodes for video and audio files render sensibly. 
+
+{F26280466}
+
+```
+[[File:A.png|thumb|200px|Test]]
+[[File:B.webm|thumb|200px|Test]]
+[[File:C.ogg|thumb|200px|Test]]
+
+[[File:A.png|200px|Test]]
+
+[[File:B.webm|200px|Test]]
+
+[[File:C.ogg|200px|Test]]
+```
+
+I've just filed T206022 about the obvious issue with audio thumbnails (before finding this task), so I'll just close this one, since everything else it would cover seems to be resolved.",1538513853,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5s7zqldna73gv3hkyshd,task_subcomment,NA
+VisualEditor: Be able to set a non-image multi-paged item's display page (page=) in the media dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rmisq2mh4lmql7yzicx6,task_description,open
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"Moved out of bug T40129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_description,open
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"My personal experience is that, as a newer editor, I edited ~30 articles using the visual editor before I realized that this was happening. It seems like a straight-forward upgrade to the visual editor. By the way, I went back and modified those 30 edited articles using ""upright"". I have since noticed many articles with specific ""px"" instead of upright and manually fix those myself; so this seems to be a fairly widespread problem.",1678751805,PHID-USER-l3sssyst6wh7vey2cxpl,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,">>! In T64671#7549236, @kostajh wrote:
+>>>! In T64671#1644967, @cscott wrote:
+>> The `upright` option suffers from some severe problems.  Consensus was reached on replacing it, see https://www.mediawiki.org/wiki/Requests_for_comment/Square_bounding_boxes  -- unfortunately, the replacement agreed upon had to be reverted due to some unexpected interactions with page layout.  We need to revisit the RFC and select one of the other proposed options for implementation.
+>> 
+>> But at the moment, authoring new content using the `upright` flag is discouraged.  
+> 
+> @cscott is this advice still up-to-date? https://www.mediawiki.org/wiki/Help:Images#Syntax should probably be updated. For context, we were looking at this flag in {T296869}.
+
+Or @subbu perhaps you know the answer to this question? Thank you in advance!",1647504763,PHID-USER-jzbjfcs2csloltie4voe,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,">>! In T64671#1644967, @cscott wrote:
+> The `upright` option suffers from some severe problems.  Consensus was reached on replacing it, see https://www.mediawiki.org/wiki/Requests_for_comment/Square_bounding_boxes  -- unfortunately, the replacement agreed upon had to be reverted due to some unexpected interactions with page layout.  We need to revisit the RFC and select one of the other proposed options for implementation.
+> 
+> But at the moment, authoring new content using the `upright` flag is discouraged.  
+
+@cscott is this advice still up-to-date? https://www.mediawiki.org/wiki/Help:Images#Syntax should probably be updated. For context, we were looking at this flag in {T296869}.",1638790184,PHID-USER-jzbjfcs2csloltie4voe,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"I think that whatever solution is reached, it should comply with relevant policies on the Wikipedias that are affected by it. On enwiki, (https://en.wikipedia.org/wiki/Wikipedia:Image_use_policy#Displayed_image_size), the following policy is in place:
+
+""**Except with very good reason, do not use** px (e.g. thumb|300px), **which forces a fixed image width.** In most cases upright=scaling factor should be used, thereby respecting the user's base preference (which may have been selected for that user's particular devices).""
+
+Additionally, respecting a user's preference for image size is an accessibility issue, and needs careful consideration before any attempt is made to change or eliminate it.",1492277661,PHID-USER-cctxaafy3x73lcil6bsc,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,">>! In T64671#3130642, @Schnark wrote:
+>>>! In T64671#1734077, @Trizek-WMF wrote:
+>> So the message we have to spread is ""don't use upright anymore"" ? 
+> Is somewhere work going on  to implement a replacement for ""upright"" which will be supported in VE?
+
+It looks to me like this is being blocked by T351 and T65904. Discussion above appears to indicate that implementing what `upright` //does// is being held up by a desire to redefine what it //should// do, or even to //deprecate// it.",1490456733,PHID-USER-5afgigb2oyaaralisy55,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,">>! In T64671#1734077, @Trizek-WMF wrote:
+> So the message we have to spread is ""don't use upright anymore"" ? 
+
+Are there any updates on this? Is somewhere work going on  to implement a replacement for ""upright"" which will be supported in VE?",1490438205,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"So the message we have to spread is ""don't use upright anymore"" ? ",1445243509,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"Change 238855 had a related patch set uploaded (by Cscott):
+WIP: Allow serialization of images which scale the default thumbnail size.
+
+[[https://gerrit.wikimedia.org/r/238855]]
+",1442435327,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"The `upright` option suffers from some severe problems.  Consensus was reached on replacing it, see https://www.mediawiki.org/wiki/Requests_for_comment/Square_bounding_boxes  -- unfortunately, the replacement agreed upon had to be reverted due to some unexpected interactions with page layout.  We need to revisit the RFC and select one of the other proposed options for implementation.
+
+But at the moment, authoring new content using the `upright` flag is discouraged.  There is a separate bug (T112710) that currently affects resizing images tagged with `upright`; that will be fixed.  But that will result in a serialization with an explicit bounding box, not the upright flag, and we have no current plans to emit an `upright` flag in newly-authored content.  Any existing use cases should be dealt with as part of the {T351} process (go comment over there!), so that we can come up with a way to solve these problems which doesn't rely on a broken feature.",1442415656,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,[[https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=118625212&oldid=118570520|New feedback]] concerning upright.,1442229339,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,A user on frwp [[ https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=116008432&oldid=115979310 | explains ]] that having a number of pixels instead of an upright (configurable) is an accessibility problem. ,1434637737,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,A user on frwp [[ https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=116008432&oldid=115979310 | explains ]] that having rough pixels instead of an upright is an accessibility problem. ,1434637672,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,A user on frwp [[ https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=116008432&oldid=115979310 | explains ]] this upright issue is an accessibility problem. ,1434636758,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"So the blocking status for T64666 is a little misleading here.  AFAIK, Parsoid parses the 'upright' option properly, and emits DOM with the correct size set.
+
+But we're not clear at all that we want to support *authoring* images with the 'upright' option, because we'd rather deprecate that option and replace it with something better.
+
+So, can we reset the discussion a little bit: what is the *current* behavior when you edit an image which has the 'upright' option.  What (if anything) is actually broken?",1422556136,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"(In reply to Spinningspark from comment #8)
+> One point about the upright parameter is that it does something sensible
+> with a portrait image by default without the user having to think about what
+> scaling factor he wants to use.  The scale parameter per se is a good thing
+> to have, but being forced to calculate a scale factor to get the equivalent
+> of the old upright parameter is a step backwards in my opinion (its a step
+> forward from the current two-steps-backward position of not having anything
+> at all but is still a step backwards from what we had before.)
+
+I think you're making assumptions here. :-) The idea was that we'd default to the usual value of 75% (and make it clear that this is the preferred value).",1412039580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"One point about the upright parameter is that it does something sensible with a portrait image by default without the user having to think about what scaling factor he wants to use.  The scale parameter per se is a good thing to have, but being forced to calculate a scale factor to get the equivalent of the old upright parameter is a step backwards in my opinion (its a step forward from the current two-steps-backward position of not having anything at all but is still a step backwards from what we had before.)",1412027527,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"(In reply to C. Scott Ananian from comment #6)
+> Mm.  Now I'm thinking the mw option might be `square` so that Parsoid emits:
+> 
+> [[Figure:Foobar.jpg|200px|square]]
+> [[Figure:Foobar.jpg|thumb|square]] <!-- equivalent to upright=1 -->
+> [[Figure:Foobar.jpg|upright=0.5|square]]
+> 
+> That would provide the same functionality but address James' concern in
+> comment 2.
+
+I'm not a fan of adding more work-arounds that modify older work-arounds. If we can fix this up cleanly with something like scale & square bounding box by default then we should do so IMO. That would result in cleaner wikitext like this:
+
+[[Figure:Foobar.jpg|200px]]
+[[Figure:Foobar.jpg|thumb]]
+[[Figure:Foobar.jpg|scale=0.75]]
+
+An automatic conversion that preserves existing image sizes is very much possible if the community agrees that going for a square bounding box by default makes sense. But again, lets not get ahead of ourselves to much here & focus on the Parsoid interface for now.",1395772902,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"Mm.  Now I'm thinking the mw option might be `square` so that Parsoid emits:
+
+[[Figure:Foobar.jpg|200px|square]]
+[[Figure:Foobar.jpg|thumb|square]] <!-- equivalent to upright=1 -->
+[[Figure:Foobar.jpg|upright=0.5|square]]
+
+That would provide the same functionality but address James' concern in comment 2.",1395762643,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"200x200px is what we already emit.  That's been the case for a while.
+
+Current thinking is that the new PHP image option will be called 'scale' (not 'thumbscale'), and that parsoid will mark its use with a 'mw-scale' class on the image wrapper, not a data-mw attribute.",1395436484,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"(In reply to James Forrester from comment #2)
+> That seems bad. [[Figure:Foobar.jpg|200px]] is vastly-preferred and
+> [[Figure:Foobar.jpg|200x200px]] is considered broken wikitext except in rare
+> cases.
+
+We could also omit this if we don't care about size stability on image aspect ratio change. Alternatively we could also change the default behavior to use a square bounding box. Lets make that decision when we get there. For now we'll just use upright.",1395425982,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"Related: https://www.mediawiki.org/wiki/Requests_for_comment/Standardized_thumbnails_sizes
+
+We could encourage users to use a limited set of pre-defined scaling factors. This could potentially let us handle some user pref based scaling in CSS instead of JS.
+
+For now the plan is to add a data-mw.scale factor which corresponds to a default-sized image. If the format is 'thumb' or 'frameless', the default image size is given by a *square bounding box* of the default thumb size.",1395425866,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"(In reply to C. Scott Ananian from comment #1)
+> Parsoid will *only* generate wikitext of the form:
+> 
+> [[Figure:Foobar.jpg|200x200px]]
+> or
+> [[Figure:Foobar.jpg|thumb|thumbscale=1]]
+
+That seems bad. [[Figure:Foobar.jpg|200px]] is vastly-preferred and [[Figure:Foobar.jpg|200x200px]] is considered broken wikitext except in rare cases.",1395424354,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"The parsoid plan is to support only square bounding boxes.
+
+Unfortunately, PHP core doesn't have a way to specify 'a square bounding box of the default thumbnail size' yet.  So for purposes of discussion let's assume there's a wikitext option named 'thumbscale' which enforces a square bounding box of (an appropriate factor of) the default thumbnail size (then quantized to nearest 10px, like upright does, in order to avoid creating lots of odd-sized thumbs).
+
+So Parsoid will *only* generate wikitext of the form:
+
+[[Figure:Foobar.jpg|200x200px]]
+or
+[[Figure:Foobar.jpg|thumb|thumbscale=1]]
+
+We will attempt to round-trip other wikitext forms ('upright', 'x200px', 'thumb' by itself (which is a width restriction only), etc) if the image is not edited.  But if the image is edited, we will emit only a square bounding box.
+
+In the short term, we might use:
+
+[[Figure:Foobar.jpg|thumb|upright=<number>]]
+
+as an approximation to the 'thumbscale' factor, where we compute <number> as <aspect ratio>*<thumbscale>.  But this is viewed as a short term hack only.
+
+The VE UI should present this as something like 'use default thumbnail size', rather than explicitly mentioning the 'upright' parameter.",1395424134,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a template
+3.Click on Add Parameter
+4.But do not add any parameter just click on ""Apply Changes""
+5.Reopen the template
+
+Observed Result:
+An undefined parameter appears inside the template dialog box
+
+See the screenshot attached
+
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13443}",1394744880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-47vdxcoqpdotzl5weohn,task_description,resolved
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter",Verified the fix in test2 : https://test2.wikipedia.org/wiki/Wmf19?veaction=edit,1395356305,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","Change 119699 merged by jenkins-bot:
+Ignore placeholder parameters in serialization
+
+https://gerrit.wikimedia.org/r/119699",1395293566,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","Change 119699 had a related patch set uploaded by Catrope:
+Ignore placeholder parameters in serialization
+
+https://gerrit.wikimedia.org/r/119699",1395293339,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","It's technically not corrupting wikitext, just inserting oddness, but yes.",1395261213,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","This is causing wikitext corruption on the wikis, upping severity.",1395260602,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter",*** Bug 62827 has been marked as a duplicate of this bug. ***,1395256801,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+VisualEditor: MediaWiki <source>  used between text nodes should render block instead of inline-block,"Screenshot of MediaWiki rendering
+
+Wikitext:
+
+=== Example ===
+Foo <code>bar</code> baz.
+You'll want to add <source lang=""javascript"">
+        ""predef"": [
+                ""OO"",
+        ]
+</source> x y.
+
+
+In MediaWiki's PHP parser:
+
+  <h3>..</h3>
+  <p>Foo <code>bar</code> baz.</p>
+  <p>You'll want to add</p>
+  <div> .. syntax highlgiht ..
+  <p>x y.</p>
+
+In Parsoid:
+
+  <h3>..</h3>
+  <p>Foo <code>bar</code> baz.</p>
+  You'll want to add
+  <div> .. syntax highlgiht ..
+  x y.
+
+Notice the lack of paragraphs from the Parsoid DOM, though this is odd, it still renders fine visually in browsers.
+
+In VisualEditor:
+
+  <h3 class=""ve-ce-branchNode"">Naming</h3>
+  <p class=""ve-ce-generated-wrapper ve-ce-branchNode"">
+    You'll want to add&nbsp;
+    <span class=""ve-ce-leafNode ve-ce-generatedContentNode ve-ce-mwExtensionNode ve-ce-mwAlienExtensionNode ve-ce-protectedNode"" contenteditable=""false"">
+      <div dir=""ltr"" class=""mw-geshi mw-code mw-content-ltr"" typeof=""mw:Extension/source"" data-mw="".."" about=""#mwt24"">..</div>
+    </span>
+    &nbsp;x y.
+  </p>
+
+It renders as an inline-block within a paragraph, that's where it goes wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13385}",1394734980,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7z4tlyfijoeek5deckps,task_description,open
+VisualEditor: MediaWiki <source>  used between text nodes should render block instead of inline-block,"Created attachment 14805
+Screenshot of Parsoid rendering and Parsoid DOM
+
+**Attached**: {F13389}",1394735068,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7z4tlyfijoeek5deckps,task_subcomment,NA
+VisualEditor: MediaWiki <source>  used between text nodes should render block instead of inline-block,"Created attachment 14804
+Screenshot of VisualEditor rendering
+
+**Attached**: {F13387}",1394735052,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7z4tlyfijoeek5deckps,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"* Latest mediawiki and VisualEditor master locally
+* Chrome incognito
+* Sandbox?veaction=edit
+
+Shows:
+
+ 1 notice                      X
+ ----
+ Warning: You are not logged in.
+ Your IP address will be recorded
+ in this page's edit history.
+
+When hovering over the [X], the text ""1 notice"" and ""Warning: .. "" go down 1px and then back up again.
+
+Not sure what it causing it, could be a browser rendering bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394667060,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n3jah3fg23mapojunl7u,task_description,resolved
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"Change 121279 merged by jenkins-bot:
+Don't use transitions for opacity on hover for now
+
+https://gerrit.wikimedia.org/r/121279",1395877134,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"Change 121279 had a related patch set uploaded by Catrope:
+Don't use transitions for opacity on hover for now
+
+https://gerrit.wikimedia.org/r/121279",1395876804,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"Cause of the wiggling seems to be a transition on the opacity. Going to work around this by just commenting out that transition, because it's such a minor detail.
+
+I'll also try to isolate a test case and file a bug upstream with Chrome.",1395876281,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,*** Bug 63020 has been marked as a duplicate of this bug. ***,1395876216,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"Widening scope, the ""back"" button of the inspector context is affected as well.
+
+Screen capture of ""Toolbar notice close button""
+: http://cl.ly/2O3c2F072a02
+
+
+Screen capture of ""Inspector context back button""
+: http://cl.ly/2S3g0V0y2O1J",1394745588,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,Screen capture: http://cl.ly/2O3c2F072a02,1394676856,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Save the page
+4.Reopen the page
+5.Open the media settings for the image 
+
+Observed Result:
+The following error appears in the console and Media Settings dialog box cannot be closed:
+
+Uncaught TypeError:Cannot read property 'width' of null
+Uncaught TypeError:Cannot call method 'getItemFromData'of undefined.
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=12thmarchchrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13283}",1394660040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_description,resolved
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load",Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754433,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Change 118601 merged by jenkins-bot:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118601",1394752327,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","(In reply to James Forrester from comment #4)
+> Still occurring after the above patch. :-(
+
+Belay that, now working. Probably browser cache issues. *sigh*
+
+(Thanks, Moriel!)",1394752129,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Still occurring after the above patch. :-(
+
+I've re-worded the bug title based on my understanding. The issue is probably in the binding of the variable – note that everything is fine as soon as you refresh the page, the problem is when you re-load VE on the same page (so re-using a lot of the VE running code).",1394748489,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Change 118427 merged by jenkins-bot:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118427",1394744961,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Change 118601 had a related patch set uploaded by Catrope:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118601",1394744862,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Change 118427 had a related patch set uploaded by Mooeypoo:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118427",1394683659,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in VE
+2.Insert a reference
+3.Open the reference dialog 
+4.Insert another reference inside it
+5.Save the page
+
+Observed Result:
+In read mode :Cite error: Closing </ref> missing for <ref> tag appears
+Inside VE: for the reference that is inside another reference, the wikitext appears in the reflist section
+
+See the screenshots attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13271}",1394653320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_description,resolved
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,Verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=Wmf19&veaction=edit,1395355830,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Change 119704 merged by jenkins-bot:
+Followup 861d097: actually exclude reference tool in reference dialog toolbar
+
+https://gerrit.wikimedia.org/r/119704",1395295485,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"(In reply to Roan Kattouw from comment #2)
+> Adding references inside of references shouldn't be possible. That toolbar
+> button is supposed to be hidden. Repurposing bug.
+> 
+Turned out to be an accidental overcorrection from fixing bug 62286.",1395295231,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Change 119704 had a related patch set uploaded by Catrope:
+Followup 861d097: actually exclude reference tool in reference dialog toolbar
+
+https://gerrit.wikimedia.org/r/119704",1395295209,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Adding references inside of references shouldn't be possible. That toolbar button is supposed to be hidden. Repurposing bug.
+
+However, we should verify that we deal correctly with cases where this has already been done in wikitext.",1395256513,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Created attachment 14794
+Wikitext in the reflist
+
+**Attached**: {F13272}",1394653411,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"I learned today from Rob Lanphier that it has recently become possible to do this reliably in every extension repo as well as mw core: 
+
+$ git checkout wmf/1.23wmf17
+
+
+For example: 
+
+/VisualEditor$ git checkout wmf/1.23wmf17
+Branch wmf/1.23wmf17 set up to track remote branch wmf/1.23wmf17 from origin.
+Switched to a new branch 'wmf/1.23wmf17'
+
+The current branch of each wiki is tracked in https://git.wikimedia.org/blob/operations%2Fmediawiki-config/HEAD/wikiversions.json
+
+The current branch of core (which should be consistent across all extensions also) is available on https://test2.wikipedia.org/wiki/Special:Version (and theoretically in the API somewhere)
+
+It would be good if we could change our Jenkins builds with test2 as a target to pull the current wmf branch instead of master. 
+
+In the short term, we could update the build config manually every Thursday. 
+
+In the slightly longer term it should be possible to read Special:Version or the wikiversions.json file in order to determine at run time the proper version of the tests appropriate for test2 (and any other target environment not beta labs, e.g. enwiki or commons)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394483880,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-dbb75rdjycfheqcgaqvh,task_description,resolved
+investigate updating test2 Jenkins builds weekly to pull by branch,"I think this was implemented entirely back in May 2014.  The fix was to have MediaWiki API the branch it runs then have the browser test checkout the matching branch, fall backing to master if the branch is not found.",1407233064,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Gilles from the Multimedia team reported an issue with the browser tests running some outdated version of the code.   Turns out the repo was not reset to origin/master but to local master branch.
+
+Fixed up with https://gerrit.wikimedia.org/r/#/c/134576/",1400664667,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"I tested it on a few change and it seems to be working fine.
+
+The qa/browsertests.git is missing wmf branches, so I have added a fallback to the 'master' branch.
+
+Lets see what happens tomorrow :)",1400617809,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134483 merged by jenkins-bot:
+Fallback to master branch when test repo miss branch
+
+https://gerrit.wikimedia.org/r/134483",1400617745,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134483 had a related patch set uploaded by Hashar:
+Fallback to master branch when test repo miss branch
+
+https://gerrit.wikimedia.org/r/134483",1400617666,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134236 merged by jenkins-bot:
+Get mw branch from target URL and check it out
+
+https://gerrit.wikimedia.org/r/134236",1400617040,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134376 merged by jenkins-bot:
+mw-sort-wmf-branches: sort wmf branchs numerically
+
+https://gerrit.wikimedia.org/r/134376",1400602772,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134376 had a related patch set uploaded by Hashar:
+mw-sort-wmf-branches: sort wmf branchs numerically
+
+https://gerrit.wikimedia.org/r/134376",1400601941,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134236 had a related patch set uploaded by Hashar:
+Get mw branch from target URL and check it out
+
+https://gerrit.wikimedia.org/r/134236",1400531916,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"The lame mw-api-siteinfo.py is now deployed.  We can use to query the target MediaWiki installation to grab the branch and attempt to check it out before running the browser tests.
+
+Should do git checkout -f  iirc.",1400530464,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131861 merged by jenkins-bot:
+mw-api-siteinfo: fetch siteinfo from MW API
+
+https://gerrit.wikimedia.org/r/131861",1400530340,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131936 abandoned by Hashar:
+API: Expose git branch in siteinfo
+
+Reason:
+No urgency to have this deployed in 1.24wmf3 since commit is in the branch wmf/1.24wmf4 which is going to be deployed on the remaining production wikis on May 15th ( https://wikitech.wikimedia.org/wiki/Deployment ).
+
+https://gerrit.wikimedia.org/r/131936",1399898263,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131935 abandoned by Reedy:
+API: Expose git branch in siteinfo
+
+Reason:
+1.24wmf2 is not used now
+
+https://gerrit.wikimedia.org/r/131935",1399657280,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"I will try to get it included in the currently deployed wmf installations, else the patch will land under the next two weeks.
+
+The tiny python script will let us easily get the branch of a target wiki. Knowing it, we can then git checkout that branch before starting the browsertests.
+
+I might be able to handle that during this week hackaton, no promise though.",1399492449,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131936 had a related patch set uploaded by Hashar:
+API: Expose git branch in siteinfo
+
+https://gerrit.wikimedia.org/r/131936",1399448471,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131935 had a related patch set uploaded by Hashar:
+API: Expose git branch in siteinfo
+
+https://gerrit.wikimedia.org/r/131935",1399448452,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131768 merged by jenkins-bot:
+API: Expose git branch in siteinfo
+
+https://gerrit.wikimedia.org/r/131768",1399422613,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"The mw-api-siteinfo.py script will let us do something like:
+
+ $ mw-api-siteinfo.py http://test2.wikipedia.org/ git_branch
+ 1.24wmf2
+ $
+
+We can then checkout that branch in the extensions to run the matching set of browser tests.",1399408181,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131861 had a related patch set uploaded by Hashar:
+mw-api-siteinfo: fetch siteinfo from MW API
+
+https://gerrit.wikimedia.org/r/131861",1399408053,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131768 had a related patch set uploaded by Hashar:
+Api: expose git branch in siteinfo
+
+https://gerrit.wikimedia.org/r/131768",1399404721,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,I am pretty sure I have a good idea about fixing this :-],1399394021,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"From bug 64611:
+
+When browsertests hit the production wikis, we should fetch the extension wmf branch that match the targeted website.  The mapping of wiki vs wmf branch can be found via the dblist files in operations/mediawiki-config.git
+
+Instead of using the Jenkins git plugin, we will have to use a script to find out which branch to check.",1398788977,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,*** Bug 64611 has been marked as a duplicate of this bug. ***,1398788949,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+VisualEditor: Changing the format of a block slug between a list and a block template breaks badly,"In this page https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_(WMF)/Prove2&oldid=101942635, if you click Enter twice after the last sub-item of the list and then select Titre de section (Heading), that item and the Portal template below disappear, and results from the Undo action may vary (the French user who found this reports that a couple of CTRL+Z blank the page for him; for me, nothing happens, or the item comes back but the template doesn’t). 
+Nothing changes if the list is unordered or ordered, but it does seem to matter that it features sub-items and not just items (as a matter of fact I couldn't reproduce with a simple list here http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Elitest&oldid=82999).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://fr.wikipedia.org/wiki/Utilisateur:Elitre_%28WMF%29/Prove2?oldid=101942635&veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50250",1394455740,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dirtzibr6cqkhuru3pvp,task_description,resolved
+VisualEditor: Changing the format of a block slug between a list and a block template breaks badly,Appears to be fixed,1423749922,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dirtzibr6cqkhuru3pvp,task_subcomment,NA
+VisualEditor: Changing the format of a block slug between a list and a block template breaks badly,We'll see if the patch for that works :),1395857888,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dirtzibr6cqkhuru3pvp,task_subcomment,NA
+VisualEditor: Changing the format of a block slug between a list and a block template breaks badly,Not sure if this is related to bug 50250?,1395440640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dirtzibr6cqkhuru3pvp,task_subcomment,NA
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,"As reported by NicoV on fr.wp, 
+unrelated edits remove the syntax for an image from an external wikilink.
+See tests at https://fr.wikipedia.org/w/index.php?title=Utilisateur%3ANicoV%2FTest&diff=101782688&oldid=101782616 , https://www.mediawiki.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandboxVE&diff=924704&oldid=924702 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394446440,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lvbwtwmxsjk452ye6dto,task_description,resolved
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,"Change 639633 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.dm.MWExternalLinkAnnotation: Alienate malformed links
+
+https://gerrit.wikimedia.org/r/639633",1607350957,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lvbwtwmxsjk452ye6dto,task_subcomment,NA
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,"Change 639633 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.dm.MWExternalLinkAnnotation: Alienate malformed links
+
+https://gerrit.wikimedia.org/r/639633",1604614338,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lvbwtwmxsjk452ye6dto,task_subcomment,NA
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,"(In reply to Elitre from comment #1)
+> PS: the edit summary window correctly displays the warning that something's
+> wrong.
+
+Now that you say there's a warning, I see it, but unless you're looking for it, it's almost invisible, lost among other texts, without any highlighting. And nothing more is said when you save.",1394618321,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-lvbwtwmxsjk452ye6dto,task_subcomment,NA
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,PS: the edit summary window correctly displays the warning that something's wrong.,1394455954,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lvbwtwmxsjk452ye6dto,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","Some (many) templates do not use any parameters (e.g., hundreds of templates like https://en.wikipedia.org/wiki/Template:Stub).  However, if you add those templates, VisualEditor will ask you for parameters, just like it does for any other template.  It would be nice to have a TemplateData setting for ""no parameters here, so don't bother asking"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394239320,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_description,open
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","> How to proceed? For {{stub}} on en.wp, I don’t achieve to add any parameter […]
+
+Turns out this is an unrelated bug, see T333826. As long as this is not fixed you can use the [keyboard shortcut](https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts#Template_editor_dialog_shortcuts_and_keyboard_interactions) Ctrl+Shift+D to add undocumented parameters to any template, no matter how it is documented.",1681234486,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","> The user can proceed as before, but the option to add what we now clearly mark as ""undocumented"" parameters is much less prominent, and explained as well.
+How to proceed? For {{stub}} on en.wp, I don’t achieve to add any parameter (as requested by this task).",1680291128,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","As part of the #wmde-templates-focusarea we made the #VisualEditor dialog say this when the #TemplateData documentation has an empty list of `""params"": {}`: ""This template has no documented parameters and may be intended for use without them."" The user can proceed as before, but the option to add what we now clearly mark as ""undocumented"" parameters is much less prominent, and explained as well. The relevant task was {T300710}.
+
+We spend quite some time on this detail and are quite happy with the result and how it performed in user tests. I suggest to leave it like that and close this task.",1680274691,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition",Another use case suggested by an editor at https://www.mediawiki.org/wiki/Topic:Wgw42pcci4g5zjn6,1632241133,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","Here's another example for the list of use cases:  The sole contents of
+{{userboxbottom}} is the table-closing wikitext code `|}`.  There are
+dozens of similar templates on enwiki.  Adding parameters to these is
+pointless at best.",1477065683,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","But @Krinkle  why shouldn't we have a way to signal that there are no parameters in the template?
+
+Yes, it could be wrong.  There could also be incorrectly incomplete TemplateData blocks added (probably far more common, actually).  
+
+I'm not saying that you'd have to prevent the addition of parameters.  But could you **just tell me** that adding a parameter to {{France-university-stub}} is probably a bad idea?  Just a friendly note, not something that's going to break the workflow if the TemplateData is wrong.  Just a note that says something like ""According to the template documentation, this template doesn't normally use any parameters.""",1475261502,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","I don't think we should have a property specifically to indicate that there are no parameters. I agree there needs to be room for TemplateData being wrong or outdated and VisualEditor's advanced transclusion editor would always allow for parameters to be added.
+
+However I think it'd be fine to remove the ability to add parameters from the simple editor that loads by default in VisualEditor - for cases where TemplateData data //did// exist but had no parameters specified.",1472693067,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","Maybe something like that, although I'd be happy to to restrict it to an empty array (=the case when it is least likely to be wrong).
+
+Even a ""warning"" note would be an improvement.  We could probably reduce confusion if we could have it display a sentence that says,  ""This template uses no parameters.  It is technically possible to add parameters here, but they will be ignored by the template"".
+
+",1458226640,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","So maybe something like a ""This TemplateData definition is complete, don't allow any undocumented parameters."" (not necessarily restricted to an empty array of parameters).
+
+I'm not sure this is a direction we want to go in though - IIRC we want to allow  for TemplateData being wrong and therefore able to be overridden inside VE.",1452891758,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","I think I wasn't quite clear earlier.  T53429 is about saying (nicely) that no parameters have been listed in TemplateData.  I'm glad that we made that improvement, but that's not what I want here.  Instead of a nice message, I want to **define, in TemplateData, that this template actually does not accept or use any parameters**.  This is ""no parameters in the //template//"", not ""no parameters currently typed into the //TemplateData//"".
+
+When a template is so marked, I'd also like VisualEditor disable the 'field name' search box, so that people can't insert any made-up or invalid parameters.  I want TemplateData to be able to stop editors from trying to add pointless parameters.",1434061888,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","
+
+*** This bug has been marked as a duplicate of bug 51429 ***",1398711170,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+VisualEditor: Link inspector opens up in the Alternative textbox inside Media Settings,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE which has an image inside it.
+2.Now open the Media Settings for the image
+3.Type something for the Alternative Text
+4.Select the text and click on the Link Inspector icon 
+
+Observed Result:
+The link inspector opens up in the Alternative text textbox as it appears in the screenshot.However, it does get placed inside the caption textbox
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59868
+
+**Attached**: {F12881}",1394234880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zmuntlo4o5mkodhqeydo,task_description,resolved
+VisualEditor: Link inspector opens up in the Alternative textbox inside Media Settings,"Change 117658 merged by jenkins-bot:
+Disable MW tools when surface loses focus
+
+https://gerrit.wikimedia.org/r/117658",1397158691,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zmuntlo4o5mkodhqeydo,task_subcomment,NA
+VisualEditor: Link inspector opens up in the Alternative textbox inside Media Settings,"(In reply to Gerrit Notification Bot from comment #1)
+> Change 117658 had a related patch set uploaded by Catrope:
+> Disable MW tools when surface loses focus
+> 
+> https://gerrit.wikimedia.org/r/117658
+
+This commit addresses a different issue, but once it lands this bug will be impossible to trigger.",1394660366,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zmuntlo4o5mkodhqeydo,task_subcomment,NA
+VisualEditor: Link inspector opens up in the Alternative textbox inside Media Settings,"Change 117658 had a related patch set uploaded by Catrope:
+Disable MW tools when surface loses focus
+
+https://gerrit.wikimedia.org/r/117658",1394654169,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zmuntlo4o5mkodhqeydo,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,"Intention:
+Read the description from TemplateData
+
+
+Actual Results:  
+The description of the parameter from TemplateData is too pale.  People with poor eyesight, lower quality monitors, in sunlight on their mobile devices, etc. will not be able to read it.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394218380,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kd7fv3uer3q4cxedaaca,task_description,resolved
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,Please open a new task. This was work done in mid-2015.,1486169504,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,"Could anybody point out in a screenshot what's meant by parameter descriptions? The dialog has several minor issues, I've tried to catch some of them:
+{F5470647 width=703}",1486164717,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,"I think this is from an old version of the template dialog. Template parameter descriptions are now black for existing fields, and #555 in the search list.",1443035549,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,"The options are ""practically white"" (when you've clicked on something else) and ""extremely pale gray"" (when you've clicked inside that parameter).
+
+I hate them both.",1394220185,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,Do you mean when it's faded out or when it's faded up?,1394219223,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+returnto and returntoquery in login/signup links doesn't get updated on pushState or popstate,"VisualEditor uses pushState to add veaction=edit to the URL when you click the VE edit tab, without causing a true reload.  However, this does not cause a true reload.  Similarly, when you click Read, the same happens to go back to read mode.
+
+Unfortunately, this does not update the returnto and returntoquery in the login and signup links.  So if you click the tab for VE, then go to login and signup in the top right, you will no longer be in VE when you get back.
+
+VE could make a custom solution for this, but a general method might be nice.  
+
+It's possible to listen to user-initiated navigation (e.g. back/forward) with the popstate event.  That could solve the problem for back and forward.
+
+However, that doesn't tell you about pushState.  So perhaps there should be a mw.pushState that updates these links, then calls the underlying browser method.
+",1394157660,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-4cf26q6ltrha64fqtdx3,task_description,open
+returnto and returntoquery in login/signup links doesn't get updated on pushState or popstate,"<Krinkle> [15:50:38] Krenair: Sounds like a good reason to have our page managed by a composition of embedded data-bound dom-based template objects. This'd be trivial there.
+<Krinkle> [15:50:52] Krenair: But that's still a year or so away, with neccecary pushback..",1420565108,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-4cf26q6ltrha64fqtdx3,task_subcomment,NA
+returnto and returntoquery in login/signup links doesn't get updated on pushState or popstate,I have a feeling that we might need to support extensions doing things when a mw.pushState is called...,1420265812,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-4cf26q6ltrha64fqtdx3,task_subcomment,NA
+VisualEditor: Removing last char from paragraph removes entire paragraph and throws in IE,"Screenshot of bug (incl. console error)
+
+Encountered in IE9 using BrowserStack ""Windows 7/IE9"" using latest MediaWiki and VisualEditor master via a tunnel. Could either be a browser bug we have to work around, or something on our end applicable to other browsers as well.
+
+
+* Put the cursor at the end of the second paragraph in a simple document
+* Removing the last character (e.g. full stop)
+
+It suddenly removes the entire paragraph and then throws an uncaught exception:
+
+> “Offset could not be translated to a DOM element and offset: 112”
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64128
+
+**Attached**: {F13344}",1394128260,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-q2usgov5bljwewguaiq4,task_description,resolved
+VisualEditor: Removing last char from paragraph removes entire paragraph and throws in IE,Can't reproduce in IE9. CE offset code has changed a lot in the last 18 months.,1460637744,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-q2usgov5bljwewguaiq4,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","When VisualEditor deactivates itself after Parsoid fails, this exceptions thrown because the property never got set.
+
+
+
+  ve.init.mw.ViewPageTarget.prototype.deactivate = function(override) {
+    if (..) {
+      if (..) {
+        this.deactivating = true;
+        if (ve.msg('accesskey-save') !== '-' && ve.msg('accesskey-save') !== '') {
+          this.elementsThatHadOurAccessKey.attr('accesskey', ..);
+                        ^
+
+ve.init.mw.ViewPageTarget.prototype.setupToolbarButtons = function () {
+  ..
+    if (ve.msg('accesskey-save') !== '-' && ve.msg('accesskey-save') !== '') {
+      this.elementsThatHadOurAccessKey = $( .. );
+
+
+The code in deactivate() shouldn't be repeating conditions like that as they're no longer semantically relevant, and in this case even incorrect. Instead the top one (which usually runs after setupToolbarButtons) should limit its interest to elementsThatHadOurAccessKey itself which we either set to null or to a jQuery object.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394125680,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-l3o54qij3sav6s6cs6gu,task_description,resolved
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117228 merged by jenkins-bot:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117228",1394150560,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117230 merged by jenkins-bot:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117230",1394150501,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117230 had a related patch set uploaded by Jforrester:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117230",1394127076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117228 had a related patch set uploaded by Alex Monk:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117228",1394126885,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117224 merged by jenkins-bot:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117224",1394126291,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117224 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117224",1394125939,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+VisualEditor:  Caption of nested image is centered in image dialog box,"Screenshot of image dialog
+
+1.  Go to page with images nested iside captions, e.g., the sandboxes at http://en.wikipedia.beta.wmflabs.org/w/index.php?&oldid=82442
+
+2.  Open the images and look at the caption for the first one.  The second image is displayed there, with its own caption centered.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F13240}",1394060040,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-seke4lquqzuxgalldvtb,task_description,resolved
+VisualEditor:  Caption of nested image is centered in image dialog box,Text is now correctly aligned.,1701963258,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-seke4lquqzuxgalldvtb,task_subcomment,NA
+VisualEditor: Block slugs don't shrink back when selection moves to a FocusableNode,"1. Click in a block slug
+2. The slug expands
+3. Click in another paragraph
+4. The slug contracts, as expected
+5. Click in the slug again
+6. The slug expands
+7. Click on a FocusableNode (reference, template, etc.)
+8. The slug doesn't contract
+9. Click in a paragraph somewhere
+10. Now the slug does contract
+
+This is because contracting the slug when it's unfocused happens in pollOnceInternal, which is not invoked when selecting FocusableNodes (and only invoked by accident when changing the selection programmatically). onModelSelect in ce.Surface should probably clear the focusedness of the focused slug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394058780,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3a75i4egmmyligpq2dlv,task_description,resolved
+VisualEditor: Block slugs don't shrink back when selection moves to a FocusableNode,"Change 117214 merged by jenkins-bot:
+Fix application of slug focus classes
+
+https://gerrit.wikimedia.org/r/117214",1394240928,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3a75i4egmmyligpq2dlv,task_subcomment,NA
+VisualEditor: Block slugs don't shrink back when selection moves to a FocusableNode,"Change 117214 had a related patch set uploaded by Esanders:
+Fix application of slug focus classes
+
+https://gerrit.wikimedia.org/r/117214",1394124079,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3a75i4egmmyligpq2dlv,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"Phantoms appearing in wrong position
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image which has large enough original size to go beyond the page say for example: http://en.wikipedia.beta.wmflabs.org/wiki/File:Ho-Ho-Kus_Inn.jpg
+
+3.Make it full size 
+4.Save the page
+
+5.Reopen the editor
+6.Select the image by clicking on a but further from the border of the image
+
+Observed Result:
+The phantom for selection is appearing in the wrong position
+
+See the screenshots attached
+
+Now to observe some additional behavior:
+Set the image size back to default size and observe the shield is still appearing in the previous position in the page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13227}",1394058180,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_description,resolved
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"I think this issue is fixed now, the only issue I see now is, for image with too big size which goes beyond CE, the phantom is also going beyond the page.Not sure if that is something we can fix or not.",1407197289,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"Yeah, this looks fixed to me.",1406752402,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,I can't replicate this. I think this was fixed after the refactor of the phantoms.,1406727411,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"(In reply to ryasmeen from comment #5)
+> I am not getting the phantom appearing at wrong position issue anymore ,but
+> what I am see now is, it takes two clicks to select that image when you have
+> made it full size.
+> If it is an unrelated issue , i will file a separate bug.
+
+Let's keep it in this one.",1400226230,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"I am not getting the phantom appearing at wrong position issue anymore ,but what I am see now is, it takes two clicks to select that image when you have made it full size.
+If it is an unrelated issue , i will file a separate bug.",1400200358,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,This also happens when I change the image position from Left to Center,1398798218,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"It the phantom remains in the previous position even if I close the editor and reopen it .
+
+Selecting the phantom also selects the image below it.
+
+Please go to this page to better understand the issue:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=5thfebchrome&veaction=edit",1394058655,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"Created attachment 14750
+Phantom appearing in previous position after reverting it to default size
+
+**Attached**: {F13229}",1394058371,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"Created attachment 14749
+How it appears when you select by clicking close to the border of the image
+
+**Attached**: {F13228}",1394058286,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+Sizing of `framed` images,"https://www.mediawiki.org/wiki/Help:Images#Size_and_frame says:
+
+> An image with frame always ignores the size specification, the original image
+> will be reduced if it exceeds the maximum size defined in user preferences.
+
+However, as bug 53514 describes, the actual behavior seems to have regressed at some point.  The code in includes/Linker.php to check the user preference for size (which seems to be the same as the thumbnail size preference) is unreachable.  As presently written, framed images are always rendered at their ""natural"" size, *unless a height* is specified, in which case the height is honored (and the width, if any, ignored).
+
+It's not entirely clear what the proper fix should be.  There are three options:
+
+1. Leave the code as is, and update the spec on the wiki.
+2. If a height is specified, honor the height *and* width (conservative, should change few pages)
+3. Implement what I think was the original idea: *always* ignore the width and height, and limit the maximum image size with the user's thumbnail size preference.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1394031840,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_description,resolved
+Sizing of `framed` images,"I checked image documentation on mw as well as enwiki and other language-specific wikis, as well as reading the code.  It was clear that the intent was as documented -- framed images were original size.  They even called getUnscaledThumb in the code.  However, getUnscaledThumb had a bug so that it did not always return unscaled thumbs.  This affected a miniscule number of pages, all of which (upon examination) were really trying to do something else (usually 'thumb' not 'frame').  We fixed most of those pages, and fixed the bug.  This bug has been merged and closed for over a month now and is already live on all the wikis.  (See https://en.wikipedia.org/wiki/User:Cscott/framed )
+
+I think you are actually trying to review the 'square bounding box' RfC -- which is Not This Bug.",1400696244,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"(In reply to Krinkle from comment #17)
+> I can't be bothered to read through and interpret the logic of height bound
+> and width bound and square cropped box ponies.
+> 
+> But I'm confused by two things:
+> 
+> 1) I can understand why certain keywords should not result in a cropped
+> image and thus for 'frame' to now only respect height of width. But ignoring
+> both seems like a pointless change that is asking to break and upset
+> existing content.
+> 
+> Existing usage like [[File:Example.jpg|frame]] would be unaffected, but
+> existing content like [[File:Test wiki logo notext.png|frame|200x200px]]
+> will not result in a gigantic 3000px image being framed on the page[1]
+
+Note that only 200x200px was scaled so far, and is rare in combination with frame. 200px was *not* scaled with frame, and still isn't.
+
+
+> 2) Wait, we made this change because some old Help documentation page[2] on
+> mediawiki.org says[3] so? That's not by any means a specification. Also,
+> that same exact documentation page has an example of
+> [[File:Example.jpg|frame|50px]] which is now broken[4] by being way too
+> large.
+
+There should be no change here at all. Framed images with only a width bbox specified were not scaled so far.
+
+Gabriel",1400691818,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"I can't be bothered to read through and interpret the logic of height bound and width bound and square cropped box ponies.
+
+But I'm confused by two things:
+
+1) I can understand why certain keywords should not result in a cropped image and thus for 'frame' to now only respect height of width. But ignoring both seems like a pointless change that is asking to break and upset existing content.
+
+Existing usage like [[File:Example.jpg|frame]] would be unaffected, but existing content like [[File:Test wiki logo notext.png|frame|200x200px]] will not result in a gigantic 3000px image being framed on the page[1]
+
+
+2) Wait, we made this change because some old Help documentation page[2] on mediawiki.org says[3] so? That's not by any means a specification. Also, that same exact documentation page has an example of [[File:Example.jpg|frame|50px]] which is now broken[4] by being way too large.
+
+[1] https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&oldid=1011846
+[2] https://www.mediawiki.org/w/index.php?title=Help:Images&oldid=945436
+[3] ""An image with frame always ignores the size specification, the original image will be reduced if it exceeds the maximum size defined in user preferences.""
+[4] https://www.mediawiki.org/w/index.php?title=Help:Images&oldid=945436#Size_and_frame",1400688484,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"We use the parsoid HTML for the page, so we do in fact handle localized option names.  However, the caveat in comment 6 applies: ""One limitation is that it uses the wp allimages API query, so it does not include pages which include images *only from commons*.""  That seems to have been the case on the page you link to.",1400182358,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"You have missed the localized version at least for dewiki (""gerahmt""), see [1]
+There are also english aliase (""enframed"" and ""frame"")
+
+
+
+[1] https://de.wikipedia.org/w/index.php?title=Airbus_A350&oldid=129797202#Zweiter_Entwurf",1398612692,PHID-USER-qaoxfiqu6bxhd5ehlwhc,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 125885 merged by jenkins-bot:
+Match fixed PHP behavior for framed images with a height specification.
+
+https://gerrit.wikimedia.org/r/125885",1397577592,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 125885 had a related patch set uploaded by Cscott:
+Match fixed PHP behavior for framed images with a height specification.
+
+https://gerrit.wikimedia.org/r/125885",1397511789,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 125876 merged by jenkins-bot:
+Update release notes to describe user-visible change to framed images.
+
+https://gerrit.wikimedia.org/r/125876",1397510183,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 125876 had a related patch set uploaded by Cscott:
+Update release notes to describe user-visible change to framed images.
+
+https://gerrit.wikimedia.org/r/125876",1397508948,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 116995 merged by jenkins-bot:
+Ignore height as well as width for framed images.
+
+https://gerrit.wikimedia.org/r/116995",1397506081,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"(In reply to comment #8)
+cscott had already fixed the pages ""Gliederung des Feldheeres (Bundeswehr, Heeresstruktur 4)"", ""Hauptkirche Sankt Michaelis (Hamburg)"", and ""Ceylor"" and I've fixed the rest now on de.wp.",1397156460,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Full list for dewiki:
+Ceylor Datei:Lochtest.png x206px
+Ceylor Datei:Volumentest.png x206px
+Fernsehwerbung Datei:Werbeanteile.png x200px
+Fahrtanzeiger Datei:FSM_WT.png 500x300px
+Friedrich Glauner Datei:Grafik_Wertetrichter_unterlegt.png 480x367px
+Gliederung des Feldheeres (Bundeswehr, Heeresstruktur 4) Datei:II._Korps.svg x150px
+Gliederung des Feldheeres (Bundeswehr, Heeresstruktur 4) Datei:III._Korps.svg x150px
+Gliederung des Feldheeres (Bundeswehr, Heeresstruktur 4) Datei:I._Korps.svg x150px
+Hauptkirche Sankt Michaelis (Hamburg) Datei:Oratorium_zur_Einweyhung_der_Michaeliskirche_1762.JPG 180x180px
+Opernhaus vorm Salztor Datei:Salztor_NMB_1800.JPG 200x200px
+Opernhaus vorm Salztor Datei:Karte_NB_Oper.jpg 300x300px
+Raketenartilleriebataillon Datei:APP-6_MLRS.svg x80px
+Reedschalter Datei:Form_A_-_Schließer_(Normally_Open).jpg x50px
+Reedschalter Datei:Form_C_-Wechsler_bzw._Umschalter.jpg x50px
+Rheintal-Express Datei:Rheintal-Express_RABe_511.jpg 260x260px
+SV Salamander Kornwestheim Datei:Logo_TV_Kornwestheim_Kodiaks.gif x130px
+STUDIOPARK KinderMedienZentrum Datei:STUDIOPARK_KinderMedienZentrum.png x100px
+ToiToiToi Datei:Toitoitoi-symbole.svg x70px
+Spotlight (Software) Datei:Spotlight-Suche_im_Finder.png x222px
+Zwergsignal Datei:Zs-beispiel1.png 500x300px",1397155043,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Sorry, my stats were slightly wrong above:
+frwiki: 
+  60 image links using the ""framed"" option
+   1 of which uses a height bound
+dewiki:
+ 538 image links using the ""framed"" option
+  20 of which use a height bound
+
+So on dewiki/frwiki I've only been about to find 21 image links whose size would be changed by this bug fix.  I'm still collecting data on enwiki, I'll update this bug with the numbers when I have them.",1397154556,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"The patch attached to https://gerrit.wikimedia.org/r/116995 now fixes the bug in the ""right way"" -- that is, it fixes File::getUnscaledThumb.
+
+This will change the size of all images which combine a height bound and a framed image.
+
+In order to determine whether fixing this bug will affect this display of too many images, I wrote a script to grunge through all images and pages containing images on a wiki.  See https://github.com/cscott/wp-image-info
+
+One limitation is that it uses the wp allimages API query, so it does not include pages which include images *only from commons*.
+
+I'm still collecting data for enwiki, but for frwiki:
+   43,014 total non-commons images
+    8,839 of them are in portrait orientation
+1,242,985 image links on pages, of which only
+       60 use the 'framed' option with a height bound
+
+For dewiki:
+  170,701 total non-commons images
+   55,208 of these are in portrait orientation
+1,786,779 image links on pages, of which only
+      538 use the 'framed' option with a height bound
+
+I fixed some of these:
+https://de.wikipedia.org/w/index.php?title=Hauptkirche_Sankt_Michaelis_%28Hamburg%29&diff=129396939&oldid=129292349
+https://de.wikipedia.org/w/index.php?title=Ceylor&diff=129396510&oldid=129332266
+https://de.wikipedia.org/w/index.php?title=Ceylor&diff=129396510&oldid=129332266",1397153496,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"To be specific, the reason why framed images respect height (but not width) is because the linker uses:
+  $thumb = $file->getUnscaledThumb( $hp );
+but includes/filerepo/file/File.php::getUnscaledThumb forces the requested width to be the same as the images natural width *but not the height*.  So if there is a height specification, getUnscaledThumb actually returns a scaled thumb.  Which is... a bug.
+
+https://gerrit.wikimedia.org/r/116995 fixes this, but probably in the wrong way (unsets height for framed images).  File::getUnscaledThumb should probably be fixed so that it ignores the specified height if present.",1396541440,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,Parsoid commit https://gerrit.wikimedia.org/r/#/c/116983/ makes Parsoid match the old (broken) behavior. We'll need to partly undo it once this bug is fixed.,1394247126,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 116995 had a related patch set uploaded by Cscott:
+Ignore height as well as width for framed images.
+
+https://gerrit.wikimedia.org/r/116995",1394040589,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"As you say, James, these are mostly questions for an RFC, and not really relevant here, though maybe blockers. A separate bug is called for.
+
+For what it's worth I would err in the direction of following the spec, but without a complaining user it may just be that the spec has fallen out of favour with reality. I would suggest asking on VPT and a few other sites that use lots of images in their work - Wikibooks and Commons come to mind - and maybe getting some CL time to help you sort out the replies, and post to more languages than just English.
+
+HTH...",1394040416,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"(In reply to C. Scott Ananian from comment #0)
+> https://www.mediawiki.org/wiki/Help:Images#Size_and_frame says:
+> 
+> > An image with frame always ignores the size specification, the original image
+> > will be reduced if it exceeds the maximum size defined in user preferences.
+> 
+> However, as bug 53514 describes, the actual behavior seems to have regressed
+> at some point.  The code in includes/Linker.php to check the user preference
+> for size (which seems to be the same as the thumbnail size preference) is
+> unreachable.  As presently written, framed images are always rendered at
+> their ""natural"" size, *unless a height* is specified, in which case the
+> height is honored (and the width, if any, ignored).
+> 
+> It's not entirely clear what the proper fix should be.  There are three
+> options:
+> 
+> 1. Leave the code as is, and update the spec on the wiki.
+> 2. If a height is specified, honor the height *and* width (conservative,
+> should change few pages)
+> 3. Implement what I think was the original idea: *always* ignore the width
+> and height, and limit the maximum image size with the user's thumbnail size
+> preference.
+
+I think option 2 is best; option 3 would be quite disruptive given that I think this is how it's been for a while (getting out git blame here might be interesting), so people aren't expecting this fundamental a thing to change much. We should talk to the Multimedia team a bit here to check with them, though.
+
+However, MediaWiki's image system needs some serious review, and I don't think a bug is the place to do it. Some possible questions, just to illustrate:
+
+*Why* does a frame image work like a thumb image except for the thumbnail and the magnifying glass icon?
+
+*Why* does frameless not operate like frame with respect to size, but does for everything else? (Though that might be just this bug, I guess?)
+
+*Why* are galleries fundamentally different in options and some of the new gallery options like hover-caption aren't implemented?
+
+Given that the proposed changes to Vector (but not Monobook, and not MediaWiki core?) in Typography Update remove the frame from frame and thumb images, should those options be merged? Should the wikitext for ""thumb"" be killed off? Should |border=1 still work in these cases? Why?
+
+… etc.",1394036538,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+"VisualEditor: Show the ""*"" mark beside the required parameter in the Add Parameter section","screenshot
+
+Right now , we are not showing the * mark beside the required parameter in the Add Parameter section.I think we should show it there too, because if a user accidentally deletes a required parameter from the left panel of transclusion dialog then he will not have any indication on the required parameter anymore.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12919}",1393876980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7l5b3wunws2md2o6jk66,task_description,invalid
+"VisualEditor: Show the ""*"" mark beside the required parameter in the Add Parameter section","(In reply to Rummana Yasmeen from comment #0)
+> because if a user accidentally deletes a required parameter from the left
+> panel of transclusion dialog
+
+We removed the ability to do this (bug 60358).",1414085457,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-7l5b3wunws2md2o6jk66,task_subcomment,NA
+VisualEditor: Display description for selected and required parameters in transclusion dialog,"Not exactly Bug 51774, but:
+while descriptions of what a parameter is supposed to mean/do are provided in the list of available parameters inside the template inspector, this is not (no longer?) true for required and already selected parameters. The only way to read their description is to remove them from the left panel and get them back in the list, where they can be selected again, but clearly this is not optimal. Not sure a tooltip would be the way, so I'm filing this separately.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51774",1393854120,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_description,resolved
+VisualEditor: Display description for selected and required parameters in transclusion dialog,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755443,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_subcomment,NA
+VisualEditor: Display description for selected and required parameters in transclusion dialog,Verified the fix in test2,1394229550,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_subcomment,NA
+VisualEditor: Display description for selected and required parameters in transclusion dialog,Verified the fix in Betalabs,1393960662,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_subcomment,NA
+VisualEditor: Display description for selected and required parameters in transclusion dialog,This has been done by gerrit 115548 which will be coming soon. Completely agreed that it was a pain.,1393868175,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Navigate to https://commons.wikimedia.org/wiki/File:Apthorp_south_jeh.JPG
+Now navigate to the same page via a ForeignAPI https://en.wikipedia.org/wiki/File:Apthorp_south_jeh.JPG
+
+Notice that in the latter a broken VisualEditor link appears.
+Expected: No VisualEditor link
+
+Similarly if you go to the mobile site you will see the same problem - an edit link appears in square brackets rather than an edit icon (see bug 61807). The mobile skin uses doEditSectionLink which seems to be incompatible with FileRepo.
+
+ I've spent the morning talking with Brion to understand more about how the magic commons file page works and how the page is rendered.
+
+Basically the problem is in FileRepo.php
+getDescriptionRenderUrl creates an API request to something akin to https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en
+If we can route this through the current skin this problem goes away.
+e.g.
+https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useformat=mobile
+or
+https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useskin=vector
+
+Brion is taking a look to see if he can add a hook.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54259",1393617960,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-3ntrwhhennryl3bteiii,task_description,resolved
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,">>! In T64071#675063, @MaxSem wrote:
+> Making FileRepo stuff depend on current skin would be horrible, also there's a problem with permissions/being logged in on foreign wiki which makes displaying edit links unreliable. However, I redid Bartosz's fix for bug 19415 (T21415) in https://gerrit.wikimedia.org/r/#/c/118135/
+
+Apparently, this never worked for File pages. I just fixed that with https://gerrit.wikimedia.org/r/468203. Since there will be no more section edit links in file descriptions fetched from foreign repo, I think we can consider this resolved.",1539896996,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Making FileRepo stuff depend on current skin would be horrible, also there's a problem with permissions/being logged in on foreign wiki which makes displaying edit links unreliable. However, I redid Bartosz's fix for bug 19415 in https://gerrit.wikimedia.org/r/#/c/118135/",1394568890,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Actually in the case of the file page we would like to render the edit links and make it possible to edit the content (albeit on a foreign wiki)
+
+So really it would be great if this could just pass the current skin name along with the request..",1394222399,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Hmm. You seem to be requesting the same thing as bug 19415 here – I already tried to fix it once, but there were complications. There's a patch there that needs to be reworked.
+
+(On a side note, my personal opinion about doEditSectionLink is that it should die in a fire and you should style the section edit links with CSS, as I made it possible to easily hide the brackets a few months ago.)",1393940047,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Thanks for clarifying the VE issue is a different problem.
+
+Compare results of
+https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useskin=vector
+https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useformat=mobile
+(triggers useskin=minerva but minerva is unregistered so this is needed)
+
+The MinervaSkin overrides doEditSectionLink. There may be other skins that also override it and will thus be inconsistent.",1393623766,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,The VE bug for this is bug 54259.,1393618182,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"That sounds like a VE/mobile bug, the links generated by core work just fine.",1393618100,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,Apologies for the brain dump - I hope this is relatively clear.,1393618031,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Applying the patch from Ie6b47f5d192953366911 in VisualEditor did not result in a module change update.
+
+I kept refreshing and purging but nothing happened.
+
+Turns out the way we fetch files in #getModifiedTime is broken for 'skinStyles'.
+
+For some reason, this method duplicates the logic to interpret the 'skinStyles' array structure from #getStyleFiles (instead of using that method), and did so incorrectly causing it to always end up with an empty array.
+
+The bug is quite subtle in that the module is capable of including these files (they're not missing from the css build), it's just that the module cache isn't invalidated if a commit only changed files listed in that part of a module.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393615200,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_description,resolved
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Change 116143 abandoned by Krinkle:
+[WIP] resourceloader: Regression test for bug 62068
+
+https://gerrit.wikimedia.org/r/116143",1411500953,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_subcomment,NA
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Change 112837 merged by jenkins-bot:
+resourceloader: Fix broken skinStyles loop in #getModifiedTime
+
+https://gerrit.wikimedia.org/r/112837",1393618151,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_subcomment,NA
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Change 116143 had a related patch set uploaded by Krinkle:
+[WIP] resourceloader: Regression test for bug 62068
+
+https://gerrit.wikimedia.org/r/116143",1393615477,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_subcomment,NA
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Change 112837 had a related patch set uploaded by Krinkle:
+resourceloader: Fix broken skinStyles loop in #getModifiedTime
+
+https://gerrit.wikimedia.org/r/112837",1393615472,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_subcomment,NA
+VisualEditor: Cursor navigation loops in block slugs at the start/end of the document,"Start case:
+1. Create a document that starts with {{echo|<div>foo</div>}} followed by some more content
+2. Put the cursor on the paragraph below the template
+3. Press left arrow until you're selecting the template
+4. Press left arrow; the cursor is now in the block slug
+5. Press left arrow; the cursor is now on the template
+6. Go to step 4
+
+End case:
+
+1. Create a document that ends with <references /> preceded by some content
+2. Put the cursor in the paragraph above the reflist
+3. Press right arrow until you're at the end of this paragraph
+4. Press right arrow; the cursor is now on the reflist
+5. Press right arrow; the cursor is now in the block slug
+6. Press right arrow; the cursor is now before the reflist 
+7. Go to step 4
+
+Note how the end case differs from the start case in that the loop is 3 keypresses long rather than 2.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393612500,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qlstyqepo7ltrgysuslj,task_description,duplicate
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Hello,
+
+Just to ask if it's possible to unable the Visual Editor for IP user on fr.wikiversity like fr.wikipedia.
+
+Thanks a lot and have a nice day.
+
+Lionel
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393587180,PHID-USER-mxwamhfxuzomk4umydpl,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_description,resolved
+Enable VisualEditor for all users and IPs by default on French Wikiversity,Thanks every one and have a nice day !,1396023903,PHID-USER-mxwamhfxuzomk4umydpl,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,This was done three weeks ago.,1396023734,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Change 117238 merged by jenkins-bot:
+Enable VisualEditor by default on French Wikiversity
+
+https://gerrit.wikimedia.org/r/117238",1394546232,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Ok, I didn't understand every things but it looks like I have to wait. Thank you Andre.",1394396667,PHID-USER-mxwamhfxuzomk4umydpl,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Lionel: https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle - this bug report is in PATCH_TO_REVIEW status, see comment 3.",1394309946,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Hello every one, Some body can translate in human language what's happen about the resolution of this ""bug"" because I didn't understand nothing about what's happen. What I just can see is the Visual editor still not work on fr.wikiversity for IP connection. Have a nice day.",1394297634,PHID-USER-mxwamhfxuzomk4umydpl,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Change 117238 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on French Wikiveristy
+
+https://gerrit.wikimedia.org/r/117238",1394129607,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Yep !
+
+You can already see the result of our vote about visual editor for IP on fr.wikipedia : https://fr.wikiversity.org/wiki/Projet:Wikiversit%C3%A9/Editeur_Visuel_pour_utilisateur_IP
+
+Have a nice day,
+
+Lionel",1394059713,PHID-USER-mxwamhfxuzomk4umydpl,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Yes, this is possible, but you should confirm with the rest of the community that they are OK with doing it.",1393631019,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block),"In Thai language, it is possible that many characters (at most 3 or 4) will be on top each other. For example, ""ที่"" consists of three characters: ""ท"", ""ี"", and ""่"". In standard textbox/textarea, including normal wikieditor, when you press left, the cursor will go left by 1 block = 3 characters in case of ""ที่"". However, for VE's editor, it will go left by only 1 character, making editors feel that he unsuccessfully pressed the key. More importantly, with the way VE's editor is, it opens possibility that editors, thinking that the cursor is after ""่"", will accidentally insert text between ""ี"" and ""่"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393547460,PHID-USER-vuus2gmqsnxh6mnavgml,PHID-TASK-tulkkn7hqx5jvhx43ruj,task_description,resolved
+VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block),This is working now; I guess it has been since 2d8c3e799601d3eb70127b32e262dbe1d64a7e4e .,1536154773,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-tulkkn7hqx5jvhx43ruj,task_subcomment,NA
+VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block),Thank you very much for this bug report; it's very clear.,1393548166,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tulkkn7hqx5jvhx43ruj,task_subcomment,NA
+VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block),"Note that VE produces the correct behavior for deleting text. For example, ""ที่"" requires 3 backspaces in order to delete it. It has already been correct. Just only iterating through letters that is wrong.",1393547857,PHID-USER-vuus2gmqsnxh6mnavgml,PHID-TASK-tulkkn7hqx5jvhx43ruj,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Page Settings page
+3.Now type something 
+
+Observed Result:
+
+It inserts the text in the CE
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Imageghau&veaction=edit
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13238}",1393545840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yewo3tdl2luoyru63ra4,task_description,resolved
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE",Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754654,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE",Verified the fix in test2,1394233053,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE",Verified the fix in betalabs,1393626056,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE","Change 116114 merged by jenkins-bot:
+Blur the surface when a dialog is opened
+
+https://gerrit.wikimedia.org/r/116114",1393615316,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE","Change 116114 had a related patch set uploaded by Esanders:
+Blur the surface when a dialog is opened
+
+https://gerrit.wikimedia.org/r/116114",1393602975,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE","This issue is not just for Page Settings rather for all these dialogs :Advanced Settings,Categories,Languages and Keyboard shortcuts page",1393546933,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings>Advanced Settings for that image
+4.Set the position to left and image type to border
+5.Save the page
+6.Reopen the page 
+7.Select the image and open the media settings for it
+
+Observed Result:
+
+TypeError: this.typeInput.getSelectedItem(...) is null appears in the console and also I could not cross out the media settings page for that image and got stuck in VE.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27thfebff&veaction=edit
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13211}",1393541100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_description,resolved
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120690 merged by Catrope:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120690",1395705067,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120691 merged by Catrope:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120691",1395705057,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Looks like its fixed in Betalabs.I tried the bonsai image in this page after the fix has been merge , did not get that error whereas previously I was getting it there:
+http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome",1395703661,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120057 merged by jenkins-bot:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120057",1395701643,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120691 had a related patch set uploaded by Catrope:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120691",1395701490,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120690 had a related patch set uploaded by Catrope:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120690",1395701471,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120057 had a related patch set uploaded by Mooeypoo:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120057",1395428254,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,*** Bug 62926 has been marked as a duplicate of this bug. ***,1395424182,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"https://bugzilla.wikimedia.org/show_bug.cgi?id=62926 might be a duplicate of this. Although in a more general setting.
+
+Note though that this also occurs for a thumbnail images* (which is the default setting for images inserted by VE).
+
+*This occurs on sv.wp [1] whilst it does not seem to occur on en.wp [2]
+
+[1] https://sv.wikipedia.org/w/index.php?title=User:Andr%C3%A9_Costa_%28WMSE%29/test2&veaction=edit
+[2] https://en.wikipedia.org/w/index.php?title=User:Andr%C3%A9_Costa_%28WMSE%29/test2&veaction=edit
+
+I would also argue for bringing the priority of this up since not being able to close the dialogue window means that any unsaved data in the article is lost. We have already had this occur during a workshop.",1395415054,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Created attachment 14856
+The most recent error appeared on 18th March
+
+**Attached**: {F13215}",1395184657,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Correction: everytime you make it frameless and fullsize, it results into NaNxNaN",1395182307,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Also, observe that for every copy of that image if you make it frameless , the resulting size in wikitext becomes NaNxNaN",1395182036,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"I just reproduced it on betalabs again : http://en.wikipedia.beta.wmflabs.org/wiki/18thMarChrome?veaction=edit
+
+Try the second image
+
+See the screenshot attached.",1395181049,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755943,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,Verified the fix in test2,1394228677,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,Verified the fix in Betalabs,1394052273,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046690,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 115939 had a related patch set uploaded by Mooeypoo:
+[wip] Add type 'none' to the media edit dialog
+
+https://gerrit.wikimedia.org/r/115939",1393616786,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"This is the bug ed noticed this morning. 
+
+This should fix the error: https://gerrit.wikimedia.org/r/#/c/115939/",1393549487,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Small modification: It has nothing to do with the image position, just select the image type as border with whatever image position it will throw that error.",1393543498,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Created attachment 14710
+Missing caption section
+
+**Attached**: {F13213}",1393541600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Also , observe in the general settings of the image with such position and format there is not caption section.
+See the screenshot attached",1393541569,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content","Screenshot
+
+Steps to reproduce:
+
+1.Create a page with VE
+2.Add a bullet list
+3.Add an image as a bulleted item of that list (
+4.Save the page
+5.Reopen the editor
+
+Observed Result:
+As soon as I open the page I get the error:
+ ""Uncaught TypeError: Cannot call method 'getOffset' of null""
+
+And then clicking on Bullet list icon again does not un-bullet the list
+Also, every time I switch to this page from other window/page it shows this error again and again. 
+
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/27thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13207}",1393538400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_description,resolved
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content",Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755222,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content",verified the fix in test2,1394230476,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content",Verified the fix in betalabs,1393888306,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content","Change 116172 merged by jenkins-bot:
+Don't allow getNearestCorrectOffset to return -1
+
+https://gerrit.wikimedia.org/r/116172",1393631799,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content","Change 116172 had a related patch set uploaded by Esanders:
+Don't allow getNearestCorrectOffset to return -1
+
+https://gerrit.wikimedia.org/r/116172",1393629113,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+Using the language link tool in the sidebar when inside VisualEditor loses the edit without warning,"A user at en.wp reported today that you can add interlanguage links while you're in VE. The last step when doing so means the whole page gets reloaded, so whatever was done in VE until that moment gets lost. I am not aware of ways to prevent this, and there is no indication in VE that this will happen when you start that procedure.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Whiteboard**: u=dev c=backend p=0
+**See Also**:
+{T54105}",1393520520,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-3ttlflt7d3qnjlwwyi2n,task_description,resolved
+Using the language link tool in the sidebar when inside VisualEditor loses the edit without warning,"I think this is no longer a problem.
+
+In the most common case, where the Wikidata item already exists, ""Edit links"" is just a link to wikidata.org, and it displays a browser warning if clicked while VisualEditor is open (like any other link).
+
+{F26721044}
+
+When the Wikidata item doesn't exist, it's trickier, since the ""Add links"" button open a dialog that lets you connect the pages. But this also works mostly fine: after completing the dialog, you still get the browser warning, and will not lose your changes made in VisualEditor unless you confirm that you want to reload the page.
+
+(I found a page I could test this on via Special:UnconnectedPages.)
+
+{F26721137}
+
+Video recording: 
+{F26721091}
+
+The experience could be better (e.g. Wikibase's page connect dialog could update the page rather than reloading it), but I think it is fine as it is, especially since this feels like a corner case.",1540258002,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3ttlflt7d3qnjlwwyi2n,task_subcomment,NA
+Using the language link tool in the sidebar when inside VisualEditor loses the edit without warning,"(Filed initially as WD, thought you hadn't mentioned this detail, re-filed again as VE. Close enough.)",1393521024,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-3ttlflt7d3qnjlwwyi2n,task_subcomment,NA
+Using the language link tool in the sidebar when inside VisualEditor loses the edit without warning,"Wikidata bug, not VE bug.",1393520906,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ttlflt7d3qnjlwwyi2n,task_subcomment,NA
+"VisualEditor: Deal with universal types like mw:Error, mw:ExpandedAttrs, mw:Placeholder","Some types like mw:ExpandedAttrs are universal, meaning they can apply to any element and their presence shouldn't be taken into account when figuring out which node handler to invoke. The node handlers themselves probably do need to make decisions based on their presence, but that's fine, they can do that already.
+
+For now the approach I'm considering is to add the concept of a universal RDFa type, which will be ignored by ve.dm.ModelRegistry#matchElement for all purposes (including the ""if not all mw: types are matched it's not a match"" logic and all of that). mw:ExpandedAttrs and mw:Error (the latter would be introduced by bug 50788) would be universal types. mw:Placeholder wouldn't be one, because it needs to trigger alienation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1393458480,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tufvyhfqrhacbhpyytqx,task_description,resolved
+"VisualEditor: Deal with universal types like mw:Error, mw:ExpandedAttrs, mw:Placeholder","We've dealt with it by introducing `allowedRdfaTypes` (in 2015: T98999). Nodes that wish to handle the ""universal"" types can do it like this:
+```
+ve.dm.MWImageNode.static.allowedRdfaTypes = [ 'mw:Error' ];
+```
+The required handling is different for each node type, so the above is not set globally, each node type has to be ""opted in"". ",1652133850,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tufvyhfqrhacbhpyytqx,task_subcomment,NA
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings of that image
+4.Insert another image inside it in the General Settings section
+5.Go to Media Settings for that image and set the Image type as Frameless and keep the position to right
+
+Observed Result:
+The image resize handlers appear at all four corners instead of appearing only at bottom left corner
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393456440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ypg6arsu3fplwmwytrtn,task_description,resolved
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,"yes, now it is fixed.",1404860737,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ypg6arsu3fplwmwytrtn,task_subcomment,NA
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,This appears to now be fixed.,1404850889,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ypg6arsu3fplwmwytrtn,task_subcomment,NA
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,*** Bug 62283 has been marked as a duplicate of this bug. ***,1404850803,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ypg6arsu3fplwmwytrtn,task_subcomment,NA
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,"Created attachment 14695
+screenshot
+
+**Attached**: {F13084}",1393457058,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ypg6arsu3fplwmwytrtn,task_subcomment,NA
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again","Use Existing reference dialog  box
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Reference >Use an existing reference
+3.Type a search term in the search box
+4.Select a reference from the search result.
+5.Now again attempt to add another existing reference 
+
+Observed Result:
+When the page of existing references opens up it still keeps the search term from previous attempt and shows the search results , it should rather clear the previous search term and let user to start over.
+This issue also occurs for new media adding dialog
+
+See the screenshots attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13051}",1393447320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o4kh74skefuz5dgfcvx5,task_description,resolved
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again",verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27thmarChrome&veaction=edit,1395944703,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o4kh74skefuz5dgfcvx5,task_subcomment,NA
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again","Change 120566 merged by jenkins-bot:
+Blank the reference and media search queries when closing dialogs
+
+https://gerrit.wikimedia.org/r/120566",1395870578,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4kh74skefuz5dgfcvx5,task_subcomment,NA
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again","Change 120566 had a related patch set uploaded by Jforrester:
+Blank the reference and media search queries when closing dialogs
+
+https://gerrit.wikimedia.org/r/120566",1395682883,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4kh74skefuz5dgfcvx5,task_subcomment,NA
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again","Created attachment 14690
+New Media Add dialog
+
+**Attached**: {F13052}",1393447363,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o4kh74skefuz5dgfcvx5,task_subcomment,NA
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),"Specifically on this page, https://it.wikipedia.org/w/index.php?title=Categoria:Aggiornare_-_economia&veaction=edit .
+I tried adding all those categories to my sandbox but they work fine there (https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&oldid=64431369&veaction=edit ), same if I add the rest of the content of that page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72303",1393352640,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-742b3uk4lvclm4lzhhp4,task_description,open
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),"(In reply to Elitre from comment #3)
+> So... is there a bug about how VE needs to be doing that yet?
+
+I thought so, but no; re-opening as said bug.",1413922420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-742b3uk4lvclm4lzhhp4,task_subcomment,NA
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),So... is there a bug about how VE needs to be doing that yet?,1413920704,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-742b3uk4lvclm4lzhhp4,task_subcomment,NA
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),"The only two categories on this page directly are listed by VE. Obviously, we can't include transcluded categories.",1413902741,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-742b3uk4lvclm4lzhhp4,task_subcomment,NA
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),Very odd.,1401416815,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-742b3uk4lvclm4lzhhp4,task_subcomment,NA
+"VisualEditor:  ""Notices"" tooltip says ""$1 notices"" rather than the correct number","Steps to Reproduce:
+1. Open a page (like Today's Featured Article) that will have notices.
+2. Hover over the ""Notices"" triangle.
+3. Read the tooltip.
+
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1393309740,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-evkkc4zlooiizhrujg2e,task_description,resolved
+"VisualEditor:  ""Notices"" tooltip says ""$1 notices"" rather than the correct number","Change 115826 merged by jenkins-bot:
+Don't use a changeable tooltip for edit notices
+
+https://gerrit.wikimedia.org/r/115826",1393464234,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-evkkc4zlooiizhrujg2e,task_subcomment,NA
+"VisualEditor:  ""Notices"" tooltip says ""$1 notices"" rather than the correct number","Change 115826 had a related patch set uploaded by Jforrester:
+Don't use a changeable tooltip for edit notices
+
+https://gerrit.wikimedia.org/r/115826",1393458868,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-evkkc4zlooiizhrujg2e,task_subcomment,NA
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list","Steps to reproduce:
+
+- Create a numbered list as follows:
+```
+1.item 1
+2.
+3.item 3
+```
+- Now add indentation to the third item , so it becomes:
+```
+1.item 1
+2.
+      1.item 3
+```
+- Now place the cursor just before the item 3 and press delete
+
+Instead of having the item 3 unindented the resulting list comes up as: 
+```
+1.item 1
+2. 1. item 3
+```
+See the screenshot: {F12837}
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit
+
+**See Also**: {T65051}",1393270740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_description,resolved
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list",What do you mean with “more sensibly”? I can still reproduce the visual issue described in initial report.,1701984700,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_subcomment,NA
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list",This behaves more sensibly now.,1701963109,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_subcomment,NA
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list","Actually, this seems to duplicate T54557, which refers to OpenOffice and Word for external consistency.",1650764976,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_subcomment,NA
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list","Rendering has changed since the first report: now, an empty line with a “Insert paragraph” slug displays after `2.`.
+
+Yet, whatever you click on this slug (i.e. whatever you add an empty paragraph starting item 2), Parsoid strips it. This means: even if you don’t press backspace, Parsoid will merge anyway item 3 with empty item 2:
+```lang=sh
+$ echo -e ""#item1\n#\n##item3"" | php bin/parse.php --wt2wt
+#item1
+##item3
+```
+
+However, if item 2 is not empty, the current behavior seems expected, so this could be declined.",1650764486,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","The proper order is #REDIRECT[[Whatever]], then categories and other stuff.  If you place the redirect anywhere other than the very top of the page, it won't work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1393270500,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-at437ap3jp2nwtfjwgi6,task_description,resolved
+"VisualEditor: Place redirects at the top of the page, not the bottom",Will mark this as fixed in favour of Parsoid bug 53508 then.,1393537213,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Change 115309 merged by jenkins-bot:
+Always try to put redirects at index 0, offset 0
+
+https://gerrit.wikimedia.org/r/115309",1393287020,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","(In reply to Gabriel Wicke from comment #7)
+> Moving back to VE; Position of inline metadata is the client's
+> responsibility. Our long-term solution is to move that metadata out of the
+> content altogether.
+
+This is semantically non-positional meta-data that breaks if not in a particular syntactical position…",1393281899,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom",Moving back to VE; Position of inline metadata is the client's responsibility. Our long-term solution is to move that metadata out of the content altogether.,1393280047,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Change 115287 merged by jenkins-bot:
+Always try to put redirects at index 0, offset 0
+
+https://gerrit.wikimedia.org/r/115287",1393279819,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Change 115309 had a related patch set uploaded by Catrope:
+Always try to put redirects at index 0, offset 0
+
+https://gerrit.wikimedia.org/r/115309",1393279725,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","(In reply to WhatamIdoing from comment #2)
+> If ""rendering in place"" means ""where the cursor is"", then that's not
+> happening.  It's placing the redirect at the bottom of the page even if your
+> cursor is at the top or in the middle.
+
+No, it's rendering ""in place"" in the HTML document; VE just puts meta-items at the end of the HTML string (because internal logic of what MW's parser does and doesn't prefer is a decision for Parsoid), so Parsoid renders this at the end of the wikitext, which helpfully doesn't work.
+
+(In reply to Gerrit Notification Bot from comment #3)
+> Change 115287 had a related patch set uploaded by Jforrester:
+> Always try to put redirects at index 0, offset 0
+> 
+> https://gerrit.wikimedia.org/r/115287
+
+This is a hack to make VE try to insert it right at the top, which may not work in all cases but at least should patch over the issue.",1393276720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Change 115287 had a related patch set uploaded by Jforrester:
+Always try to put redirects at index 0, offset 0
+
+https://gerrit.wikimedia.org/r/115287",1393276161,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","If ""rendering in place"" means ""where the cursor is"", then that's not happening.  It's placing the redirect at the bottom of the page even if your cursor is at the top or in the middle.",1393275826,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Logically, Parsoid should decide where in the page such things go (right now it just renders in place); VisualEditor could hack around this by putting it at the top of the HTML, but that's not a scalable fix (and will likely break other things).
+
+Parsoid, what do you think?",1393270693,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"When you set a redirect in VisualEditor, it doesn't display anything, so it looks like it didn't work.",1393270380,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gqge6ob2qbmzizzddum7,task_description,resolved
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 273391 merged by jenkins-bot:
+Show redirect target inside target
+
+[[https://gerrit.wikimedia.org/r/273391]]",1458255280,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 273397 merged by jenkins-bot:
+Make mediawiki.action.view.redirectPage available on mobile
+
+[[https://gerrit.wikimedia.org/r/273397]]",1456445600,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 273397 had a related patch set uploaded (by Alex Monk):
+Make mediawiki.action.view.redirectPage available on mobile
+
+[[https://gerrit.wikimedia.org/r/273397]]
+",1456444980,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 271701 abandoned by Alex Monk:
+Move redirects out of the meta list into actual nodes
+
+Reason:
+Per Ed, in favour of a different commit
+
+[[https://gerrit.wikimedia.org/r/271701]]",1456443686,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 273391 had a related patch set uploaded (by Alex Monk):
+Show redirect target inside target
+
+[[https://gerrit.wikimedia.org/r/273391]]
+",1456443122,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"As discussed on IRC there are two approaches: Make the redirect render as a node (the patch just submitted) or keep it in metadata and render a new control above the document.
+
+Having it as a node gives us selection and delete for free, but there are no systems in place to make that node un-moveable, or un-copyable. Given that an unmovebale node can only ever be at the start or end of a document (by definition) I'm not sure we need to support that. 
+
+If all we need is a bit of rendering in the surface we can add a styled button above the document showing the redirect, and which launches the dialog.",1455902303,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 271701 had a related patch set uploaded (by Alex Monk):
+Move redirects out of the meta list into actual nodes
+
+[[https://gerrit.wikimedia.org/r/271701]]
+",1455837699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Note that in some cases redirects actually have some content, so are not necessarily blank.",1443891375,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,Still valid.,1443036053,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,">>! In T63861#648996, @Krenair wrote:
+> When checking that I was right about the valid positioning of redirects, I found that Parsoid implements redirects wrong (or rather, differently to MediaWiki core's parser): it seems quite happy to accept a redirect that is anywhere in the document.
+
+Reported as T88081",1422591190,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Created attachment 15753
+In this case, I re-pointed a redirect, so it was displayed, and now it *looks like* changing it caused the redirect to be removed rather than changed.
+
+**Attached**: {F12829}",1403805225,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"I spoke to Roan about what I would need to know to do this today. After some explanation we realised that this relies on meta items (e.g. redirects) having the possibility of being visible (at the moment they are just stripped from the model data so we don't know where they are). That is somewhere on his work list but he is not particularly close to starting it.
+
+Also, I thought for a moment that since a valid redirect must be in a certain position (at the top of the document - if it's under something else then it's actually just a list element starting with 'redirect' and with a link to the target page), we could perhaps rely on that to make it visible. But I suspect that would be a pretty ugly solution.
+
+When checking that I was right about the valid positioning of redirects, I found that Parsoid implements redirects wrong (or rather, differently to MediaWiki core's parser): it seems quite happy to accept a redirect that is anywhere in the document.",1397256310,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,This was mis-labelled; sorry for the confusion.,1397162060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"We should probably show the same as the MW-rendered redirect:
+
+https://bits.wikimedia.org/static-1.23wmf14/skins/common/images/redirectltr.png
+
+… or ideally a better system that doesn't use an image, and fix MW whilst we're at it.",1393271027,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,"I find the whole thing to be rather confusing. It's much too technical. Also it partially mixes the concept of ToC with that of a structure editor. It has some widgets on the ToC (add template, add content, change order) and others inside the editor (Add param, del param, del template). This is terribly inconsistent. And makes you having to scan the screen too much.
+
+Also by default it tries to introduce you to the concept of chained templates ( starttemplate, content, endtemplate ). Which is rather complex and often not even needed.
+
+This needs serious work to make the usability much more consistent and predictable. I would take the following into account.
+
+
+1: Make a decision. Is it a toc, or a structure editor ? If the latter, then put all structure controls in the structure editor. Otherwise avoid putting them in there.
+2: By default, don't show the buttons for chained/wrapping templates. Instead, only add them if Parsoid assumes there is content wrapping happening. For new templates insertion, make an addition to templatedata ""openedBy, closedBy"", and only add the buttons if the template data says they are needed.
+3: Keyboard control. I try tab key to move focus to the ""Add template"" button next to the field. Seems this is captured by the UI, so I cannot move focus that way. It seems I can only click the button. BAD... Also seems that the add button and the delete buttons do not have a :focus state. Or rather, it seems that buttons have focus state, but the focusable element is the <a> inside it, so it doesn't really work.
+4: The layout of the params view.. I don't know how to do it better right now, but this needs work. too many lines/blocks, it's too cluttered. Do you need a double line separator if you have a heading ?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393171260,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-z2cr4me55wbuu3qesrhc,task_description,resolved
+VisualEditor: Improve the UX of the template editor,"(In reply to James Forrester from comment #3)
+> Most of these points are met by the re-work of these that has been worked on
+> for months as part of the citation work – see
+> http://mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog but broadly a
+> much simplified version of the full transclusion dialog is being made
+> (provisionally I'm calling it the template dialog) which removes the TOC and
+> makes a lot of other changes.
+> 
+> There's also bug 53604 which tracks improvements in general; should we
+> factor out the unique parts of this bug (not quite sure which)?
+> 
+> (In reply to Derk-Jan Hartman from comment #0)
+> > I find the whole thing to be rather confusing. It's much too technical. Also
+> > it partially mixes the concept of ToC with that of a structure editor. It
+> > has some widgets on the ToC (add template, add content, change order) and
+> > others inside the editor (Add param, del param, del template). This is
+> > terribly inconsistent. And makes you having to scan the screen too much.
+> 
+> Add param – moved to ToC for transclusion dialog, and to bottom for template
+> dialog.
+
+{{done}}
+
+> Del param – currently being left on each param; we could move it, but not
+> sure where?
+> 
+> Del template – will not available in template dialog; being left in place
+> right now for transclusion dialog.
+
+{{done}}
+
+[Snip]
+
+> > For new templates insertion, make an addition to templatedata
+> > ""openedBy, closedBy"", and only add the buttons if the template data says
+> > they are needed.
+> 
+> This is a nice idea, though it could get very complex (""this template can be
+> opened by these four templates, or these two templates in conjunction, but
+> not following this template, except on Category: pages, but only with
+> language conversion switched on, unless it's a Tuesday…"").
+
+I've spun this out to its own bug, bug 62338.
+
+> > 3: Keyboard control. I try tab key to move focus to the ""Add template""
+> > button next to the field. Seems this is captured by the UI, so I cannot move
+> > focus that way. It seems I can only click the button. BAD... Also seems that
+> > the add button and the delete buttons do not have a :focus state. Or rather,
+> > it seems that buttons have focus state, but the focusable element is the <a>
+> > inside it, so it doesn't really work.
+> 
+> Yeah, there's some bits of keyboard work that need improvement, and the
+> tension between accessibility and utility is acute here.
+
+Partially done; OOjs UI buttons are not, which is bug 62337.
+
+> > 4: The layout of the params view.. I don't know how to do it better right
+> > now, but this needs work. too many lines/blocks, it's too cluttered. Do you
+> > need a double line separator if you have a heading ?
+> 
+> See
+> https://commons.wikimedia.org/wiki/File:VE-reference-dailog-design-05b.png
+
+{{done}}
+
+(In reply to Elitre from comment #4)
+> What about a drop-down menu with a list of most used templates (on the
+> project or chosen by the single user)? I think it was asked somewhere else,
+> but it's being brought up again on en.wp so I hope this is the right place
+> to mention it. I know something like this will be added to the referencing
+> system, but it'd be great to have it for more general purposes as well.
+
+That's bug 53590.
+
+Consequently, I'm closing this bug as ""FIXED"", which is not quite right but is a better disposal that the alternatives.",1394130209,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,"What about a drop-down menu with a list of most used templates (on the project or chosen by the single user)? I think it was asked somewhere else, but it's being brought up again on en.wp so I hope this is the right place to mention it. I know something like this will be added to the referencing system, but it'd be great to have it for more general purposes as well.",1393707727,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,"Most of these points are met by the re-work of these that has been worked on for months as part of the citation work – see http://mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog but broadly a much simplified version of the full transclusion dialog is being made (provisionally I'm calling it the template dialog) which removes the TOC and makes a lot of other changes.
+
+There's also bug 53604 which tracks improvements in general; should we factor out the unique parts of this bug (not quite sure which)?
+
+(In reply to Derk-Jan Hartman from comment #0)
+> I find the whole thing to be rather confusing. It's much too technical. Also
+> it partially mixes the concept of ToC with that of a structure editor. It
+> has some widgets on the ToC (add template, add content, change order) and
+> others inside the editor (Add param, del param, del template). This is
+> terribly inconsistent. And makes you having to scan the screen too much.
+
+Add param – moved to ToC for transclusion dialog, and to bottom for template dialog.
+
+Del param – currently being left on each param; we could move it, but not sure where?
+
+Del template – will not available in template dialog; being left in place right now for transclusion dialog.
+
+> Also by default it tries to introduce you to the concept of chained
+> templates ( starttemplate, content, endtemplate ). Which is rather complex
+> and often not even needed.
+
+Indeed, hence the split.
+
+> This needs serious work to make the usability much more consistent and
+> predictable.
+
+Which is why we've been working on this for months. :-)
+
+> I would take the following into account.
+
+> 1: Make a decision. Is it a toc, or a structure editor ? If the latter, then
+> put all structure controls in the structure editor. Otherwise avoid putting
+> them in there.
+
+See above.
+
+> 2: By default, don't show the buttons for chained/wrapping templates.
+> Instead, only add them if Parsoid assumes there is content wrapping
+> happening.
+
+See above.
+
+> For new templates insertion, make an addition to templatedata
+> ""openedBy, closedBy"", and only add the buttons if the template data says
+> they are needed.
+
+This is a nice idea, though it could get very complex (""this template can be opened by these four templates, or these two templates in conjunction, but not following this template, except on Category: pages, but only with language conversion switched on, unless it's a Tuesday…"").
+
+> 3: Keyboard control. I try tab key to move focus to the ""Add template""
+> button next to the field. Seems this is captured by the UI, so I cannot move
+> focus that way. It seems I can only click the button. BAD... Also seems that
+> the add button and the delete buttons do not have a :focus state. Or rather,
+> it seems that buttons have focus state, but the focusable element is the <a>
+> inside it, so it doesn't really work.
+
+Yeah, there's some bits of keyboard work that need improvement, and the tension between accessibility and utility is acute here.
+
+> 4: The layout of the params view.. I don't know how to do it better right
+> now, but this needs work. too many lines/blocks, it's too cluttered. Do you
+> need a double line separator if you have a heading ?
+
+See https://commons.wikimedia.org/wiki/File:VE-reference-dailog-design-05b.png",1393526920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,That would be https://bugzilla.wikimedia.org/show_bug.cgi?id=49772 I think? (although not specific to the missing TD case).,1393526600,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,"Add way to access/view /doc, if TemplateData is not visible.",1393526222,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+Flow: Parsoid HTML for videos doesn't work,"eg. https://ca.wikipedia.org/wiki/Tema:T3edcbkgt2ns31ff 
+
+(Old example: http://ee-flow.wmflabs.org/w/index.php?title=User_talk:Quiddity&topic_postId=rpnkneesuic1rsx8&workflow=rnhr0vbpmcq1wj5m#flow-post-rpnkneesuic1rsx8 )
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: http://ee-flow.wmflabs.org/w/index.php?title=User_talk:Quiddity&topic_postId=rpnkneesuic1rsx8&workflow=rnhr0vbpmcq1wj5m#flow-post-rpnkneesuic1rsx8",1393014300,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-ilx4l4y6zoryzl6763pk,task_description,duplicate
+Flow: Parsoid HTML for videos doesn't work,"> The ""thumb"" works ok
+
+Not really. A thumbnail is created, but clicking it doesn't play the video, it leads to the File page.
+
+Reported at [[ https://ca.wikipedia.org/wiki/Fitxer:This_is_the_Wikimedia_Foundation.webm | w:ca.Tema:T3edcbkgt2ns31ff ]].",1462557739,PHID-USER-h6xz2shsbvhdtx5puurj,PHID-TASK-ilx4l4y6zoryzl6763pk,task_subcomment,NA
+Flow: Parsoid HTML for videos doesn't work,"Copying from merged:
+
+>>! In T72532#769902, @Amire80 wrote:
+> Link: https://he.wikipedia.org/wiki/%D7%A0%D7%95%D7%A9%D7%90:S1wm63huv90migi0
+> 
+> Thanks for the reporting.
+
+",1423511030,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-ilx4l4y6zoryzl6763pk,task_subcomment,NA
+Flow: Parsoid HTML for videos doesn't work,"fresh examples of webm video failing to render at fullsize, and ogg audio failing to display its player: https://www.mediawiki.org/wiki/Topic:S52i2un1zblzd8s8#flow-post-s5fley5jhc8a8pub (Does this bug/issue also cover audio files? I'm not sure whether to rename, or fork.)",1415046152,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-ilx4l4y6zoryzl6763pk,task_subcomment,NA
+Flow: Parsoid HTML for videos doesn't work,"This is partly the same as bug 61786 (the image HTML generated by Parsoid is different from PHP parser output), but there are additional problems for video links.
+
+For both [[File:Sequence-Test.ogv]] and [[ File:Sequence-Test.ogv|thumb]] in a Flow post, the links to the video are an invalid <a href=""./File:Sequence-Test.ogv"">. The HTML doesn't include a <video> tag, just an <img> tag. The full-size video uses the original .ogv file as the src of the nested image tag, which obviously doesn't work, while the thumb video correctly uses the Sequence-Test.ogv.jpg thumbnail.
+
+Furthermore, the resulting HTML doesn't seem to trigger the MwEmbedSupport/TimedMediaHandler RL modules that add player controls and such to the video. Maybe those look for <div class=""mediaContainer""> or the <video> tag.
+
+O VisualEditor team, do you have CSS and JS that make Parsoid video HTML work? :)",1394075239,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ilx4l4y6zoryzl6763pk,task_subcomment,NA
+VisualEditor: Extension tags that create block-level items aren't allowed inside pre-formatted rows in MW,"If you add a formula (or other inline item) to a normal paragraph, everything works in VE consistently with MW (yay).
+
+If you add a formula (or other inline item) to a pre-formatted paragraph, everything still works works (yay).
+
+If you add a gallery (or other block item) to a normal paragraph, everything works in VE consistently with MW (yay).
+
+If you add a gallery (or other block item) to a pre-formatted paragraph, VE tries to let you do that, and MW decides retroactively that the paragraph wasn't actually pre-formatted (boo), unless it's a <pre>-formatted rather than indent-pre-formatted block, in which case galleries don't work.
+
+Not tested with Headings, but there's probably similar wonkiness there too.
+
+*sighs*
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393014300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p44y73skf774qafrhxfm,task_description,resolved
+VisualEditor: Extension tags that create block-level items aren't allowed inside pre-formatted rows in MW,Looks like this is now fixed.,1493661754,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p44y73skf774qafrhxfm,task_subcomment,NA
+VisualEditor: Extension tags that create block-level items aren't allowed inside pre-formatted rows in MW,Sounds like a Parsoid issue.,1393952314,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-p44y73skf774qafrhxfm,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"We are currently using a hack[1] to make VisualEditor to be the default edit mode on Portuguese Wikibooks.
+
+Could someone make it the default in the right way?
+
+[1] https://pt.wikibooks.org/wiki/MediaWiki:Gadget-VisualEditorByDefault.js
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://pt.wikibooks.org/wiki/T%C3%B3pico:Wikilivros_Discuss%C3%A3o:Portal_comunit%C3%A1rio/Testes_com_o_Editor_Visual_no_Wikilivros/resposta_%284%29",1393011960,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-jyfxkeisbvohmunciamd,task_description,resolved
+Make VisualEditor opt-out on Portuguese Wikibooks,Thanks!,1393327454,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"(In reply to Gerrit Notification Bot from comment #6)
+> Change 115213 merged by jenkins-bot:
+> Make VisualEditor opt-out on Portuguese Wikibooks
+> 
+> https://gerrit.wikimedia.org/r/115213
+Deployed now.",1393287705,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"Change 115213 merged by jenkins-bot:
+Make VisualEditor opt-out on Portuguese Wikibooks
+
+https://gerrit.wikimedia.org/r/115213",1393286656,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,Scheduled for 16:00 PST today.,1393271991,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"Change 115213 had a related patch set uploaded by Jforrester:
+Make VisualEditor opt-out on Portuguese Wikibooks
+
+https://gerrit.wikimedia.org/r/115213",1393268819,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"(In reply to Helder from comment #2)
+> The link is in the URL field
+
+Sorry, I missed that. If there have been no objections from the community I guess it is OK to proceed then.",1393069463,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"The link is in the URL field, but there is little activity there currently, so I doubt there will be more comments...",1393063683,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"I assume, because the JS is in place by default, that community consensus has already been reached? Could you provide a link for completeness' sake?",1393047051,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Please uninstall the Flow extension from Meta-Wiki. Relevant discussion: <https://meta.wikimedia.org/w/index.php?title=Meta:Babel&curid=69328&diff=16251209&oldid=16240965>.
+
+The extension was installed in <https://gerrit.wikimedia.org/r/114088>.
+
+Explicit consensus for complete removal (and lack of consensus for any partial survival of the extension): https://meta.wikimedia.org/w/index.php?title=Meta:Babel&oldid=16337330#Proposal_to_remove_Flow_on_Meta-Wiki",1392946860,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_description,resolved
+Remove Flow from Meta-Wiki,">>! In T63729#3967503, @Alsee wrote:
+>>>! In T63729#3957407, @Mattflaschen-WMF wrote:
+>> This applies to any extension with log types, not just StructuredDiscussions.  It's expected behavior.  There is no solution other than code duplication (which is okay if that's the best solution, but no one has explained why it is in this case).
+> 
+> The Flow logs are OK as-is, but I have a possible generic solution that can handle (probably) any future extension. Wouldn't it be possible to run the logs through the extension and store the results as plaintext? Then you don't need the code anymore. Any links would generally point to non-existent objects anyway.
+
+But then users wouldnt be able to select language. It also makes searching through logs much more difficult (see issues with checkuser logs).
+",1518540335,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3957407, @Mattflaschen-WMF wrote:
+> This applies to any extension with log types, not just StructuredDiscussions.  It's expected behavior.  There is no solution other than code duplication (which is okay if that's the best solution, but no one has explained why it is in this case).
+
+The Flow logs are OK as-is, but I have a possible generic solution that can handle (probably) any future extension. Wouldn't it be possible to run the logs through the extension and store the results as plaintext? Then you don't need the code anymore. Any links would generally point to non-existent objects anyway.
+
+",1518532265,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3948471, @MarcoAurelio wrote:
+> 1 can be fixed with a rWMME entry
+
+Before we identify an alternative technical solution (e.g. code duplication to put log formatting in WikimediaMessages), we should first identify a technical problem with the simplest solution (deleting SD boards, preventing new ones from being created, and leaving the extension installed).
+
+>>! In T63729#3950882, @Alsee wrote:
+> Considering that the extension is uninstalled, I'd say those log issues are pretty insignificant.
+> 
+> However I think it suggests that new extension development should have a checklist item to consider and test uninstallation. We wouldn't want some other extension causing hard-to-reverse problems in the future.
+
+This applies to any extension with log types, not just StructuredDiscussions.  It's expected behavior.  There is no solution other than code duplication (which is okay if that's the best solution, but no one has explained why it is in this case).",1518148819,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Actually please follow the discussion at T186463. This task has been long closed. Thanks.,1517997687,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Considering that the extension is uninstalled, I'd say those log issues are pretty insignificant.
+
+However I think it suggests that new extension development should have a checklist item to consider and test uninstallation. We wouldn't want some other extension causing hard-to-reverse problems in the future.",1517958062,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"1 can be fixed with a rWMME entry as for 2 I'd not care much, as the Topics are either converted to Wikitext using the script, or deleted, or both. As for Meta-Wiki, nothing broke after uninstallation.",1517910896,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069153, @Catrope wrote:
+>>>! In T63729#3068503, @demon wrote:
+>>>>! In T63729#3068479, @Dereckson wrote:
+>>> @demon @MZMcBride The collaboration team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+>>> 
+>> 
+>> Integrity? What?
+>> 
+> 
+> The concern here was that the rendering of e.g. https://meta.wikimedia.org/wiki/Special:Contributions/Flow_talk_page_manager would break, because the Topic namespace would go away.
+
+It's also the actual logs:
+
+1. Valid log entries don't render, so you just get ""flow-delete-post (Test)"", instead of something like ""deleted a post on ""Test"" on Structured Discussions/Sandbox (delete test post)"" (these are different examples, but the same action type; correct version also has proper links): https://en.wikipedia.org/w/index.php?title=Special%3ALog&type=delete&user=Fram&page=&year=2016&month=9&tagfilter=&subtype=
+2. The namespace stops existing, which still causes breakage even with https://wikitech.wikimedia.org/wiki/Flow .  See https://en.wikipedia.org/w/index.php?title=Special%3ALog&type=&user=Roan+Kattouw+%28WMF%29&page=&year=2016&month=-1&tagfilter=&hide_thanks_log=1&hide_patrol_log=1&hide_tag_log=1&hide_review_log=1 (namespace is missing even for the workaround deletes).",1517879734,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,I would like to thank all participants in this and related tasks here on Phabricator for their communication and handling of what was and is a delicate and sometimes tense matter on the wikis. I truly appreciate it from everyone.,1488496284,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069224, @Catrope wrote:
+>>>! In T63729#3069218, @demon wrote:
+>>>> , but otherwise that plan sounds good. Let's get this on Wikitech.
+>>> It's already there, for the deployment window that's right now. Matt is doing the cawiki change, I'll coordinate with him.
+>> 
+>> I meant more a [[Uninstalling Flow]]
+> 
+> Oh, the procedure for it, gotcha. Will do that right after I do it on meta so it's fresh in my mind.
+
+Done now: https://wikitech.wikimedia.org/wiki/Flow",1488496026,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,This is now done,1488495297,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVqRM-z1lCyyDMEPvQd9} [2017-03-02T22:46:23Z] <catrope@tin> Synchronized dblists/: T63729: disable Flow on metawiki (duration: 00m 58s)",1488494784,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 333860 merged by Catrope:
+[operations/mediawiki-config] Remove Flow from Meta-Wiki
+
+[[https://gerrit.wikimedia.org/r/333860]]
+",1488494481,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069218, @demon wrote:
+>>> , but otherwise that plan sounds good. Let's get this on Wikitech.
+>> It's already there, for the deployment window that's right now. Matt is doing the cawiki change, I'll coordinate with him.
+> 
+> I meant more a [[Uninstalling Flow]]
+
+Oh, the procedure for it, gotcha. Will do that right after I do it on meta so it's fresh in my mind.",1488492925,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069212, @Catrope wrote:
+>>>! In T63729#3069205, @demon wrote:
+>> I'm not sure we need `deleteBatch.php` in this case since it's already down to just one page
+> 
+> We do need it, there is more than one topic page: https://meta.wikimedia.org/wiki/Special:AllPages/Topic:
+> 
+
+Ah ok, I understand what you mean.
+
+>> , but otherwise that plan sounds good. Let's get this on Wikitech.
+> It's already there, for the deployment window that's right now. Matt is doing the cawiki change, I'll coordinate with him.
+
+I meant more a [[Uninstalling Flow]]",1488492852,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069205, @demon wrote:
+> I'm not sure we need `deleteBatch.php` in this case since it's already down to just one page
+
+We do need it, there is more than one topic page: https://meta.wikimedia.org/wiki/Special:AllPages/Topic:
+
+> , but otherwise that plan sounds good. Let's get this on Wikitech.
+It's already there, for the deployment window that's right now. Matt is doing the cawiki change, I'll coordinate with him.
+",1488492775,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I'm not sure we need `deleteBatch.php` in this case since it's already down to just one page, but otherwise that plan sounds good. Let's get this on Wikitech.",1488492613,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3068503, @demon wrote:
+>>>! In T63729#3068479, @Dereckson wrote:
+>> @demon @MZMcBride The collaboration team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+>> 
+> 
+> Integrity? What?
+> 
+
+The concern here was that the rendering of e.g. https://meta.wikimedia.org/wiki/Special:Contributions/Flow_talk_page_manager would break, because the Topic namespace would go away. Flow also doesn't let you delete pages in the Topic namespace, and without Flow the namespace doesn't exist. So the way I worked around this on enwiki was:
+- Uninstall Flow
+- Temporarily add `$wgExtraNamespaces[2600] = 'Topic';` to the config
+- Use `deleteBatch.php` to delete all pages in the Topic namespace
+- Remove the `$wgExtraNamespaces` config
+That's a bit ugly, but we should just do the same thing on metawiki, since there's only a test board there and the only real board was transwikied. If we ever wanted to reinstall Flow there, we could undelete the relevant pages: they wouldn't be gone forever, they just wouldn't be viewable or undeletable without reinstalling Flow (because of content model issues).
+
+I've scheduled this (the uninstall + namespace + deleteBatch dance) for the deployment window we already had (for T159047) at 22:00 UTC (i.e. 7 minutes from now).",1488491574,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"There were two flow boards: the ORES talk page has been moved to mw.org and the contributions can be seen there (also in Special:Contributions). As for the development test page, I daresay I won't miss that. The comments on there were: 1 thread of complaint and 1 thread of test. Given the clear, explicit consensus to remove the extension in the RfC, this isn't an excuse not to honour it.",1488480410,PHID-USER-q4v6ujukzx2pt3y5kogz,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3068479, @Dereckson wrote:
+> @demon @MZMcBride The collaboration team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+> 
+
+Integrity? What?
+
+> To remove the extension is possible, but will be at the detriment of the capability to explore past contributions.
+
+Why did we not have this discussion with enwiki?",1488478469,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"@demon @MZMcBride The collaboration team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+
+As much, as an alternative discussion, it's offered to keep the extension, so it's still possible to explore  the full contributions, but don't have any Flow page active.
+
+To remove the extension is possible, but will be at the detriment of the capability to explore past contributions.",1488478381,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"@demon @MZMcBride The Flow team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+
+As much, as an alternative discussion, it's offered to keep the extension, so it's still possible to explore  the full contributions, but don't have any Flow page active.",1488478281,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3066801, @MZMcBride wrote:
+> @Dereckson: I missed the discussion in `#wikimedia-operations`. I'm trying to better understand the status of this task. Are you unwilling to deploy <https://gerrit.wikimedia.org/r/333860>?
+
+I'm more than willing.",1488476273,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,@Dereckson: I missed the discussion in `#wikimedia-operations`. I'm trying to better understand the status of this task. Are you unwilling to deploy <https://gerrit.wikimedia.org/r/333860>?,1488439083,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"As @MZMcBride said, I don't think there are technical reasons for not doing this. The English Wikipedia had way more Flow boards enabled and got removed there per request of its community. Now there's this request, with large community consensus and no active Flow boards. It should be even easier to perform, even if afterwards we need some manual work to do. The community has asked clearly that they want the feature removed (@Alsee even opened a section in that discussion for if it was any doubt), not socially disabled, which is an euphemism for not doing what it was explicitly requested. I don't think they are serious problems for this not to be done, but some personal choices of not wanting Flow gone from Meta; and that is not appropriate when executing valid community consensus. The community at large had their opportunity to voice their personal opinion, and the result was that we want the feature removed. We ain't requesting anything impossible to do, or prohibited or absurd (ie: remove CheckUser or CentralAuth). Thank you.",1488388508,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I strongly agree with MarcoAurelio. Installing Flow on Meta-Wiki never had consensus and there's now a strong consensus to remove the extension completely. The discussion even specifically addressed whether this meant removing Flow from all pages or completely uninstalling the extension.
+
+If there are technical reasons that Flow cannot be uninstalled from Meta-Wiki currently, I would like to know what those reasons are specifically in Phabricator Maniphest tasks so that these issues can be addressed.",1487896471,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 333860 restored by MarcoAurelio:
+Remove Flow from Meta-Wiki
+
+Reason:
+This is not appropriate, Dereckson. The discussion at -operations is that the contribs of Flow talk page manager can stay where they are w/o any problems so far. Restoring. Please implement the community consensus. If this was done for enwiki, this can happen for Meta-Wiki as well. Nothing broke there and nothing will break here either.
+
+[[https://gerrit.wikimedia.org/r/333860]]",1487878688,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 333860 abandoned by Dereckson:
+Remove Flow from Meta-Wiki
+
+Reason:
+Per discussion on #wikimedia-operations, we'll disable it socially, but will leave the Flow extension installed.
+
+That will avoid to get an inconsistent state in the logs, contributions.
+
+The meta RFC is still satisfied as there isn't any active Flow page on meta. (and socially won't), as steps have been taken to move the last one to another wiki.
+
+[[https://gerrit.wikimedia.org/r/333860]]",1487878544,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I ran the preparatory scripts.
+
+Thanks to @Matiia for doing the 4 steps above.",1487807369,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Re {T154816} and {T156113}, the script parts are done.  Could an admin please do the following:
+1. Delete https://meta.wikimedia.org/wiki/Research_talk:ORES_paper
+2. Soft redirect from https://meta.wikimedia.org/wiki/Research_talk:ORES_paper to https://www.mediawiki.org/wiki/Talk:ORES/Paper .
+2. Delete https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page
+3. Move https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page/Wikitext to https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page .
+
+? Thanks.",1487806425,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Re {T154816} and {T156113}, the script parts are done.  Could an admin please do the following:
+1. Delete https://meta.wikimedia.org/wiki/Research_talk:ORES_paper
+2. Delete https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page
+3. Move https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page/Wikitext to https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page .
+
+? Thanks.",1487805919,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Added to the latest window available for Europeans: https://wikitech.wikimedia.org/w/index.php?title=Deployments&action=historysubmit&type=revision&diff=1555498&oldid=1555483,1487682860,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3038137, @jeblad wrote:
+> <rant>Sometimes I would really want a more firm standpoint from WMF against people moving backwards… </rant>
+
+<rant>Agreed. And the necessary prerequisite is to correctly identify ""forward"" in the first place. During the Flow prototype stage numerous community members told Flow's lead designer that the project was going in the wrong direction. He was told that it could never be successfully deployed as a replacement for Talk pages. The designer aggressively ignored critical project requirements. Uninstalling a non-viable project is a step forwards.</rant>",1487657499,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"T154816 is not a hard blocker, just a nice to have (why not make a couple persons happy if it costs us nothing). Doing T156113 before the disabling is instead definitely recommended, though not absolutely necessary per T156113#2964757.
+
+Since there is no way in Phabricator to distinguish ""real blockers"" from ""things you'd also do at the same time in an ideal world"", I'm removing the soft subtask again.",1487496677,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I asked for a status update regarding {T154816} at T154816#3038183. This task turns three years old in a couple of days. ;-)  But more seriously, I'd like to see this task resolved in the next week or two. March 1 seems like a reasonable deadline.
+
+One way or another, I'm going to call March 1, 2017 a hard deadline. We will not be saving posts to a Flow-backed version of <https://meta.wikimedia.org/wiki/Research_talk:ORES_paper> after this date.",1487442713,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Standing against the communities which gave success to the WMF movement ain't going to work. Saying that Flow is moving forward is also a disputable statement, specially when so much people has objected to its use on that project, some of those because they ain't able to use that software at all. World is not fair, but excluding community members from discussion pages is not what I'd call moving forward.",1487433981,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,<rant>Sometimes I would really want a more firm standpoint from WMF against people moving backwards… </rant>,1487427762,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3016898, @MarcoAurelio wrote:
+> Flow board still needs to be ported to mw.org and a maintenance script run
+> afterwards to convert remaining Flow boards before being removed I think.
+
+That would be nice, but not necessary: we're not dropping the database tables any time soon. Also, if there is really an urgency to keep the content the script for conversion to wikitext is available.",1487407427,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Flow board still needs to be ported to mw.org and a maintenance script run
+afterwards to convert remaining Flow boards before being removed I think.",1486735904,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,It seems about time to schedule the configuration change and send notices. Can a week or two of windows be added to https://wikitech.wikimedia.org/wiki/Deployments ?,1486721573,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#2963875, @MZMcBride wrote:
+> I think it's reasonable to wait for {T154816} to be resolved, if possible, but we should set a firm deadline. Is four weeks enough time?
+
+4 weeks seems unnecessarily long, but should be tolerable.",1485617945,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Proposed workflow:
+
+# {T154816}, then
+# {T156113}, then
+# SWAT https://gerrit.wikimedia.org/r/#/c/333860/",1485250346,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 333860 had a related patch set uploaded (by MarcoAurelio):
+Remove Flow from Meta-Wiki
+
+[[https://gerrit.wikimedia.org/r/333860]]
+",1485249656,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I think it's reasonable to wait for {T154816} to be resolved, if possible, but we should set a firm deadline. Is four weeks enough time?",1485230338,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"[[ https://meta.wikimedia.org/w/index.php?title=Meta:Babel&curid=69328&diff=16251209&oldid=16240965 | The RFC on Meta has closed]] with a clear consensus to remove Flow. Note that this was not an RFC to reduce active Flow pages to zero, this was an RFC for the extension be uninstalled as was done on Enwiki. (T148611)
+
+",1485212471,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Note: There is an ongoing proposal to remove Flow from Meta: https://meta.wikimedia.org/wiki/Meta:Babel#Proposal_to_remove_Flow_on_Meta-Wiki,1483218188,PHID-USER-vzo36k53hgat5bwuxsn5,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#2755301, @Alsee wrote:
+> Flow is to be uninstalled on EnWiki T148611, can we just roll the two tasks into one?
+
+
+No separate tasks, should always be kept seperate",1477858479,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Flow is to be uninstalled on EnWiki T148611, can we just roll the two tasks into one?
+
+The [[ https://meta.wikimedia.org/wiki/Meta:Requests_for_comment/Enable_Flow_as_beta_feature | RFC for Flow on Meta ]] was unanimous against Flow, except for the author. I wish I heard about the RFC, I would have eagerly piled-on against Flow. The lead software designer for Flow was told during the prototyping stage, by many many editors, that the design was wrong and that it was never going to be used. He just blew-off all community input on it. (EnWiki Flow talk archives, and almost certainly anywhere else Flow was discussed at the time.)
+",1477870278,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Flow is to be uninstalled on EnWiki T148611, can we just roll the two tasks into one?
+
+The [[ https://meta.wikimedia.org/wiki/Meta:Requests_for_comment/Enable_Flow_as_beta_feature | RFC for Flow on Meta ]] was unanimous against Flow, except for the author. I wish I heard about the RFC, I would have eagerly piled-on against Flow. The lead software designer for Flow was told during the prototyping stage, by many many editors, that the design was wrong and that it was never going to be used. He just blew-off all community input on it. (EnWIki Flow talk archives, and almost certainly anywhere else Flow was discussed at the time.)
+",1477856226,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Triaged.,1468865416,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,The RfC is closed now and the closure result has not been contested for some time. Flow has no use on Meta other than the test page linked above so there should be no major fuss in removing this.,1468865374,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Also, [[ https://meta.wikimedia.org/wiki/Meta:Requests_for_comment/Enable_Flow_as_beta_feature | this RfC ]] on enabling Flow on Meta as beta feature, although few people participated, is leaning towards not allowing this.",1464026872,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"> (there was a discussion at https://gerrit.wikimedia.org/r/#/c/115412/ too)
+
+NSFW link! My eyes bleed... luckily the past is behind us.",1463344740,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,(there was a discussion at https://gerrit.wikimedia.org/r/#/c/115412/ too),1463344450,PHID-USER-qlodcndtwpolbdhncjis,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#2295518, @Nemo_bis wrote:
+> This request should probably be reopened and completed.
+
+Sure. I've re-opened this task to allow for further consideration.",1463336988,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Two years later, from https://meta.wikimedia.org/wiki/Special:AllPages?from=&to=&namespace=2600 it appears there is no meaningful content anywhere, only https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page with some garbage and complaints.
+
+This request should probably be reopened and completed.",1463307836,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 115412 abandoned by Odder:
+Remove Flow from Meta-Wiki
+
+Reason:
+This is very unlikely to ever be merged.
+
+https://gerrit.wikimedia.org/r/115412",1394645055,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I interpret comments 13 to 17 as WONTFIX for this request.
+
+Are there any further arguments that have not been brought up yet plus need answers?",1394017452,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"**wmf.amgine3691** wrote:
+
+(In reply to Erik Moeller from comment #17)
+> Yeah, sure - I agree there's no point pissing off people unnecessarily while
+> we're looking at different test scenarios. There's also no point creating
+> more drama than required about a single page test deploy. :) Preemptively
+> deleting comments on a page flagged as ""developer test page"" and then
+> raising alarm bells about the coming incursion seems a wee bit premature.
+> Let's all have a sensible chat about what makes sense on Meta, but let's
+> also give each other the benefit of the doubt as we go please.
+
+AGF is stretched a bit, since there were clear examples cited, communications channels were not used, etc. That is, AGF is not required from only one party.",1393396906,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Where does the single page test end, and using it as a backdoor to enabling it wider or sitewide without community consensus",1393396783,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Yeah, sure - I agree there's no point pissing off people unnecessarily while we're looking at different test scenarios. There's also no point creating more drama than required about a single page test deploy. :) Preemptively deleting comments on a page flagged as ""developer test page"" and then raising alarm bells about the coming incursion seems a wee bit premature. Let's all have a sensible chat about what makes sense on Meta, but let's also give each other the benefit of the doubt as we go please.",1393396061,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Erik Moeller from comment #15)
+> What practical concerns are there with the current test page deploy?
+
+I think you and I may fundamentally disagree about whether pissing off a local editing community and engendering further ill will toward these type of projects (ArticleFeedbackv5, LiquidThreads, Flow, UniversalLanguageSelector, VisualEditor, etc.) is a practical concern. The erosion of trust and collaboration between the Wikimedia Foundation and the active editing communities is a very serious and practical concern, in my opinion.
+
+As far as I know, deploying Flow will not cause anything to explode. This is _not_ the same as saying deploying Flow will not cause any harm. I think attempting to force this alpha discussion software on Meta-Wiki (and wherever else next) will actively harm already battered relations.
+
+I'll try to put it another way: if the software has virtue and merit as a product, it should be no issue for the Flow team to establish local community consensus to test it out. However there are over 800 Wikimedia wikis; if, after discussion and consultation, the Meta-Wiki community decides it doesn't want to install Flow right now, test it elsewhere. What's the issue?",1393395182,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I think everyone agrees that the communication about the single-page test wasn't sufficient. But I don't think the LQT comparison is valid. LQT comes with a rather scary per-page flag allowing any page to be LQT-enabled, and the discussions you're pointing to refer to enabling LQT across Meta.
+
+Flow has no such flag right now - pages are manually and carefully selected for testing purposes, and effects truly are pretty limited. This deploy enabled a page called ""Developer test page"". So this analogy seems _very_ stretched, and the arguments seem theoretical at this point. What practical concerns are there with the current test page deploy?",1393394462,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Erik Moeller from comment #13)
+> We can't get consensus on a per-wiki basis before enabling any software
+> change. That has never been our practice and never will be.
+
+Nobody is asking you to.
+
+> What are the actual material issues with this deploy?
+
+I think both you and Maryana are perhaps missing the point.
+
+* [[m:Wikimedia Forum/Archives/2010-04#LiquidThreads]]
+* [[m:Meta:Babel/Archives/2010-12#LiquidThreads]]
+* [[m:Meta:Babel/Archives/2012-01#Enabling Liquid Thread on meta]]
+
+The Flow team has put forward the idea that it can operate in a vacuum on a wiki. I don't believe this is acceptable or reasonable. The Flow team has also put forward the idea that hyper-local consensus (or in the case of Meta-Wiki, no visible consensus...) can override project or global consensus. This is pretty unchartered territory, no? For example, when's the last time a group of five or six users determined whether to enable an extension on the English Wikipedia?
+
+The Flow team says Flow will be opt-in software, but then unilaterally declares that it's going to deploy Flow to Meta-Wiki, with an accompanying self-merge in Gerrit, and without any on-wiki discussion or any attempt to discuss the idea with the Meta-Wiki community. Consensus is a _pillar_ of Wikimedia wikis.
+
+I can't help but think that Tomasz is correct that you're repeating the mistakes of VisualEditor by trying to steamroll communities into accepting this software. Particularly on a smaller wiki such as Meta-Wiki, Flow can't simply exist in a vacuum. Special:RecentChanges, Special:Watchlist, IRC feeds, etc. are all common and will be infected by Flow.
+
+Echoing what I said in comment 8, Meta-Wiki has repeatedly rejected LiquidThreads, but perhaps the response to Flow will be different. Has anyone asked the Meta-Wiki community about its thoughts on using alpha discussion software? If the Flow team came into this seeking collaboration, it might find users willing to test out its software.
+
+I can't directly stop you from deploying the Flow extension to Meta-Wiki or any other Wikimedia wiki against the local community's wishes, but I wouldn't recommend it: history has repeatedly shown that the insurgents quite often beat out an occupying force. If you try to force Flow onto the wikis, I think you can only expect backlash and an increasingly inhospitable discussion environment.",1393393146,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"We can't get consensus on a per-wiki basis before enabling any software change. That has never been our practice and never will be. Clear communication is another matter and it looks like we could have done better in this respect.
+
+What are the actual material issues with this deploy?",1393361884,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Maryana Pinchuk from comment #9)
+
+> We are not going to disable Flow from Meta unless there is an actual issue
+> with the software. Please do not reopen this bug again unless you can point
+> to an actual issue with the software; doing otherwise is disruptive and
+> pointless.
+
+You have conveniently avoided answering any of the questions asked by MZMcBride. The truth is, you did not ask the Meta community for their opinion on whether Flow should be enabled or not, and you refuse to acknowledge it.
+
+This is VisualEditor all over again: you have learnt nothing from that experience, and that's just sad.",1393352536,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 115412 had a related patch set uploaded by Odder:
+Remove Flow from Meta
+
+https://gerrit.wikimedia.org/r/115412",1393351937,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Just as is enabling an extension on a production wiki without asking its community for opinion first.,1393351813,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,We are not going to disable Flow from Meta unless there is an actual issue with the software. Please do not reopen this bug again unless you can point to an actual issue with the software; doing otherwise is disruptive and pointless.,1393351735,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Maryana Pinchuk from comment #4)
+> This is all following along our course of enabling Flow on an opt-in, user
+> requested basis on a limited set of pages for testing purposes over the next
+> 3-6 months.
+
+I don't believe the Meta-Wiki community wants the Flow extension enabled right now. Have you tried asking the community about its thoughts on the matter?
+
+Unlike most of the Flow team, most active users at Meta-Wiki have been around for a long time. Meta-Wiki eschewed LiquidThreads (I believe I even once proposed enabling it there and it was quickly shot down). Perhaps with Flow, the Meta-Wiki community will be more receptive, but I think it would make sense to ask. Have you asked?",1393032148,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to spage from comment #6)
+> Enabling Flow on a wiki test page before enabling it on a requested Talk
+> page on that wiki is clearly the right thing to do. We found a problem with
+> Parsoid configuration on meta by doing so.  We do indeed have playgrounds
+> already so I didn't see much point in publicizing yet another test page, but
+> since people find them anyway we should do so in the future.
+> 
+> I think people's bigger objection is Flow coming to a wiki because some
+> small group requests it on ""their"" Talk page. That's implicit in the
+> roll-out strategy Maryana mentioned, which is on the main Flow page:
+>    Wider release to more WikiProject and community discussion spaces on
+> English Wikipedia and other projects, on an opt-in trial basis
+> 
+> I don't think this bug is the best place to discuss the rollout strategy,
+> I've created https://www.mediawiki.org/wiki/Flow/Rollout and it has a talk
+> page, the latter is not yet Flow-enabled :)
+
+I think you're totally missing the point about the objections raised in this bug.",1393014881,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Enabling Flow on a wiki test page before enabling it on a requested Talk page on that wiki is clearly the right thing to do. We found a problem with Parsoid configuration on meta by doing so.  We do indeed have playgrounds already so I didn't see much point in publicizing yet another test page, but since people find them anyway we should do so in the future.
+
+I think people's bigger objection is Flow coming to a wiki because some small group requests it on ""their"" Talk page. That's implicit in the roll-out strategy Maryana mentioned, which is on the main Flow page:
+   Wider release to more WikiProject and community discussion spaces on English Wikipedia and other projects, on an opt-in trial basis
+
+I don't think this bug is the best place to discuss the rollout strategy, I've created https://www.mediawiki.org/wiki/Flow/Rollout and it has a talk page, the latter is not yet Flow-enabled :)",1393011506,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,No. Meta is not your playground. Go test Flow on the Beta cluster if you need to.,1393003465,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Andre: From https://wikitech.wikimedia.org/wiki/Deployments: Tuesday February 18th, ""enable Flow on meta test page and a few more mediawiki.org talk pages"" :)
+
+I got a request from the WMF Programs Evaluations team to enable Flow on the talk page of https://meta.wikimedia.org/wiki/Programs:Evaluation_portal/Learning_modules. The extension's been tested in production for 2 months now (on mw.org, as well as English Wikipedia for about 2 weeks now), but we wanted to be sure to enable it on a test page on Meta before releasing it on a real discussion page. 
+
+This is all following along our course of enabling Flow on an opt-in, user requested basis on a limited set of pages for testing purposes over the next 3-6 months.",1393002860,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Bawolff (Brian Wolff) from comment #2)
+>(Surely flow should add a page property
+> or something to flow pages so that they can be found sanely?)
+
+Filed as bug 61747",1392986145,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Andre Klapper from comment #1)
+> I did not see this mentioned anywhere on
+> https://wikitech.wikimedia.org/wiki/Deployments (link welcome if I missed
+> it). 
+> The patch is missing any link to a bug report or on-wiki discussion, as
+> MZMcBride correctly pointed out. And I have no idea what the ""one page of
+> meta"" is, as the commit message is so vague.
+> 
+
+It's https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page . You can find flow pages by doing searches like https://meta.wikimedia.org/w/index.php?title=Special:Search&search=%22This%20talk%20page%20has%20been%20taken%20over%20by%20a%22&fulltext=Search&profile=all&redirs=1 (Surely flow should add a page property or something to flow pages so that they can be found sanely?)",1392985659,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I did not see this mentioned anywhere on https://wikitech.wikimedia.org/wiki/Deployments (link welcome if I missed it). 
+The patch is missing any link to a bug report or on-wiki discussion, as MZMcBride correctly pointed out. And I have no idea what the ""one page of meta"" is, as the commit message is so vague.
+
+I really hope I missed something, otherwise this would look like pretty bad communication.",1392984733,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+Open the VE and observe the toolbar
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13046}",1392934800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_description,resolved
+VisualEditor: Toolbar broken in Betalabs,Verified the fix in betalabs,1392939577,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"This has been resolved because the offending commit was reverted
+
+I7e8ab90f7a9f77f5cf6d7baeab586d4e0332042e",1392937691,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"Change 114637 abandoned by Trevor Parscal:
+Fix a missing { and remove some debugging CSS left in Ied29358
+
+Reason:
+Ied29358 was reverted
+
+https://gerrit.wikimedia.org/r/114637",1392936992,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"Change 114637 had a related patch set uploaded by Krinkle:
+Fix a missing { and remove some debugging CSS left in 4a067460
+
+https://gerrit.wikimedia.org/r/114637",1392936388,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"Created attachment 14638
+Screenshot
+
+**Attached**: {F13047}",1392934866,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"The file modules/syntaxhighlight/rules/mysql.json has at least one double quoted string containing unescaped double quotes. I.e something like:
+
+{
+ ""match"" : """"""
+}
+
+That cause PHP json_decode() to choke with a syntax error.  I wrote a json linter to lint json files in Jenkins.  You can try it using integration/jenkins.git and running bin/json-lint.php
+
+ ./modules/syntaxhighlight/rules/mysql.json: Syntax error
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392906540,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_description,resolved
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"hashar@gallium:~/extensions$ /srv/deployment/integration/slave-scripts/bin/json-lint.php VisualEditor/; echo $?
+0
+hashar@gallium:~/extensions$",1392926451,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,The PHP json_decode() no more reports any error. Thank you!,1392926436,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"Change 114518 merged by jenkins-bot:
+Fix broken JSON in modules/syntaxhighlight/rules/mysql.json
+
+https://gerrit.wikimedia.org/r/114518",1392925383,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"(In reply to Antoine ""hashar"" Musso from comment #0)
+> The file modules/syntaxhighlight/rules/mysql.json has at least one double
+> quoted string containing unescaped double quotes. I.e something like:
+> 
+> {
+>  ""match"" : """"""
+> }
+> 
+> That cause PHP json_decode() to choke with a syntax error.  I wrote a json
+> linter to lint json files in Jenkins.  You can try it using
+> integration/jenkins.git and running bin/json-lint.php
+> 
+>  ./modules/syntaxhighlight/rules/mysql.json: Syntax error
+
+It's in a file that's not currently used (the code needs some work), but I've fixed it.",1392923964,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"Change 114518 had a related patch set uploaded by Jforrester:
+Fix broken JSON in modules/syntaxhighlight/rules/mysql.json
+
+https://gerrit.wikimedia.org/r/114518",1392923895,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values","Right now the reference group input (in both MWReferenceDialog and MWReferenceListDialog) is a plain text input box (with a placeholder).
+
+Instead, it should be a drop-down that suggests existing groups, as well as giving the ability to write in a new value, aka a ComboBox.
+
+The default value should still have a placeholder, I think.
+
+[Blocked on OOjs UI having a ComboBox widget.]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392861240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bthorzb222zjqyyqflqv,task_description,resolved
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values",Verified the fix in Production,1410545581,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bthorzb222zjqyyqflqv,task_subcomment,NA
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values",Verified it in Betalabs and test 2,1409872373,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bthorzb222zjqyyqflqv,task_subcomment,NA
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values","Change 156160 merged by jenkins-bot:
+Use combo box widget to suggest existing values for reference group
+
+https://gerrit.wikimedia.org/r/156160",1409689295,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bthorzb222zjqyyqflqv,task_subcomment,NA
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values","Change 156160 had a related patch set uploaded by Alex Monk:
+Use combo box widget to suggest existing values for reference group
+
+https://gerrit.wikimedia.org/r/156160",1408991900,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bthorzb222zjqyyqflqv,task_subcomment,NA
+VisualEditor: Factor out ./ stripping logic,"Right now it's in MWInternalLinkAnnotation and MWRedirectMetaItem just calls into that (see https://gerrit.wikimedia.org/r/#/c/114381/). There's also some ./ stripping regexes strewn across the rest of the codebase. This should all be factored out and centralized.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392860160,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-k52nhgcjimjne3g6enih,task_description,open
+"VisualEditor:  In the category dialog, there should be a drop down indicator on existing categories","Inside the category editor, there used to be a drop-down indicator on categories.  It's not there now.  Not at MediaWiki, not at Wikipedias, not in Safari 6, not in Firefox 26 (on Mac OS 10.8.5).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392858900,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-hwxwkjrd5ypn4cohgwlt,task_description,resolved
+"VisualEditor:  In the category dialog, there should be a drop down indicator on existing categories",Verified the fix in test2,1393009228,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hwxwkjrd5ypn4cohgwlt,task_subcomment,NA
+"VisualEditor:  In the category dialog, there should be a drop down indicator on existing categories","Yes, this got broken some time ago due to an oversight – and we just fixed it on Friday (gerrit 113477). The fix will be going out to MediaWiki.org tomorrow. Sorry!",1392859556,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hwxwkjrd5ypn4cohgwlt,task_subcomment,NA
+VisualEditor: Burn ve.ce.getElementOffset down to the ground,"It's incredibly confusing spaghetti code that's not documented well. Kill it with fire and start from scratch.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392852060,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-caf2jml522yw7s4hrz7i,task_description,resolved
+VisualEditor: Burn ve.ce.getElementOffset down to the ground,This function doesn't actually exist. I'm assuming this refers to getOffset/getOffsetFromElementNode/getOffsetFromTextNode which have been rewritten in https://gerrit.wikimedia.org/r/#/c/121563/,1404350652,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-caf2jml522yw7s4hrz7i,task_subcomment,NA
+"VisualEditor: Don't allow users to insert images inside images' captions inside images' captions, as MediaWiki can't cope with that","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings of that image and add another image inside it
+4.Now Go to the media settings of the image that you just added
+5.Type something in the caption of the second image
+6.Apply changes
+7.Save the page
+
+Observed Result:
+The wiki text for the image shows up in the read mode
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/19thfebFF
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13390}",1392850500,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ziermjjci3oyywhcltgx,task_description,duplicate
+"VisualEditor: Don't allow users to insert images inside images' captions inside images' captions, as MediaWiki can't cope with that","I can't make three-deep nested images work in wikitext.
+
+Three deep (image1's caption contains image2, and image2's caption contains image3) causes this problem if done in VisualEditor:  
+http://en.wikipedia.beta.wmflabs.org/w/index.php?&oldid=82440  It displays correctly in VisualEditor, but makes a mess when you save.
+
+Two deep in wikitext displays correctly:  https://en.wikipedia.org/w/index.php?&oldid=598318957#List
+
+Three deep in wikitext shows me only the first image.  The other two in my (unsaved) attempts simply disappeared from view (although present in the wikitext code).
+
+It's possible that I simply haven't found the perfect sequence of nesting the images, but if wikitext can't handle more than two in a nested sequence, the VisualEditor shouldn't offer it.",1394059797,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ziermjjci3oyywhcltgx,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Parsoid's bug 49844 with link attributes has been fixed.
+
+In https://bugzilla.wikimedia.org/show_bug.cgi?id=49844#c5 James Forrester wrote:
+
+This is worked around (albeit with potentially a bit of a hack) in VisualEditor, so not so important now from VisualEditor's POV.
+
+Now that the parsoid fix has been deployed (for a while now), I'm opening a new bug to revert Visual Editor's hack.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392847560,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-zltiznjn5tevkdkrgrvo,task_description,invalid
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"As discussed, this wasn't a hack, this was the right thing to do, so INVALIDing this bug.",1395082995,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 119088 merged by jenkins-bot:
+Remove commented-out, now-confirmed-as-wrong wrong image insertion code
+
+https://gerrit.wikimedia.org/r/119088",1395082729,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 119087 merged by jenkins-bot:
+Clarified the default link for image insertion.
+
+https://gerrit.wikimedia.org/r/119087",1395081903,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 119088 had a related patch set uploaded by Jforrester:
+Remove commented-out, now-confirmed-as-wrong wrong image insertion code
+
+https://gerrit.wikimedia.org/r/119088",1395081642,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 119087 had a related patch set uploaded by Cscott:
+Clarified the default link for image insertion.
+
+https://gerrit.wikimedia.org/r/119087",1395081568,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"I believe the reversion is correct.  Clarified the spec: https://www.mediawiki.org/w/index.php?title=Parsoid%2FMediaWiki_DOM_spec&diff=931265&oldid=931084
+VE's current behavior matches the spec.",1395081459,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"This isn't fixed.
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=81525&oldid=81245
+
+*sighs*",1393637856,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 114352 merged by jenkins-bot:
+Revert ""Set href attribute of newly inserted image to image title""
+
+https://gerrit.wikimedia.org/r/114352",1392932238,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 114352 had a related patch set uploaded by Jforrester:
+Revert ""Set href attribute of newly inserted image to image title""
+
+https://gerrit.wikimedia.org/r/114352",1392848850,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Error thrown when typing something while a left aligned image is selected,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image .
+3.Go to Media Settings>Advances Settings
+4.Set the image alignment to left/None
+5.Save the page
+6.Reopen the page
+7.Select the image
+8.Start typing something
+
+
+Observed Result:
+ncaught Error: Offset could not be translated to a DOM element and offset: 143 appears in the console 
+
+See the screenshot attached
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=18thfebchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13297}",1392767520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ioicrlnneujuclmsdn76,task_description,resolved
+VisualEditor: Error thrown when typing something while a left aligned image is selected,IME cursor code has changed significantly since 2014 and I can't reproduce. Please re-open if this is still hapenning.,1701962955,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ioicrlnneujuclmsdn76,task_subcomment,NA
+VisualEditor: Error thrown when typing something while a left aligned image is selected,"Found the steps to reproduce the case with deleting the reflist:
+
+1.Add an image
+2.Go to Media Settings>Advanced Settings
+3.Set the position to left
+4.Add a reference inside the image
+5.Save the page
+6.Open the page again
+7.Delete the reflist
+
+The error Uncaught Error: Offset could not be translated to a DOM element and offset: 143 appears in the console",1392769346,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ioicrlnneujuclmsdn76,task_subcomment,NA
+VisualEditor: Error thrown when typing something while a left aligned image is selected,This is also happening while deleting the reflist of the same page,1392767690,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ioicrlnneujuclmsdn76,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"It seems Flow has not defined any HTML accesskeys for previewing/submitting posts and topics.
+
+The default accesskey ""p"" should be added to the ""Preview"" button.
+The default accesskey ""s"" should be added to the ""Reply""/""Add Topic""/""Submit changes"" buttons when replying to a topic/adding a topic or editing a post respectively.
+
+Docs (I'm not sure which of these are most uptodate):
+* https://www.mediawiki.org/wiki/Manual:Interface/Access_keys
+* https://meta.wikimedia.org/wiki/Help:Keyboard_shortcuts
+* https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+* https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts
+
+See also {T158779}
+",1392758820,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-xle733tl52tx5qckejj2,task_description,open
+Flow lacking accesskeys for preview/submit,"I use alt(+shift)+s to save in articles, which is specified when hovering over the save-button (in wikicode-mode). That should be standard for Flow as well.",1440623374,PHID-USER-4j7xntcqqwei7izzlfnd,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"Well, it's ""non-standard in the Wikimedia world"" because we didn't decide to use it as a standard. There is no Wiki God (sorry, Jimbo!) declaring ""the standard"". There is only us.
+
+And Echo is being introduced for the same reason Visual Editor is: Because ""our ways"" don't cut it for the mere rest of the world. There, WYSIWYG editing is standard. So is Crtl/Cmd-Enter to save.",1439992612,PHID-USER-hms7bpiczbwhx4dxgiqw,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"First of all the long established accesskeys (with ""S"" for saving and ""P"" for preview respectively) should be added to Flow.
+
+If we add yet another - currently non-standard (in the Wikimedia world) - possibility for submitting (like Ctrl+Enter) is not within the scope of the bug as far as I'm concerned.",1439984330,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"Frankly, I think the ULS should get a different shortcut then. Simple question:
+* How many people will use the ULS often enough to remember and use a shortcut, per day?
+* How many people will save a comment on a Flow talk page, using the pseudo-standard shortcut (used by gmail, phabricator, etc.), per day?
+
+Principle of least surprise, people...",1439368805,PHID-USER-hms7bpiczbwhx4dxgiqw,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"We could use the standard accesskey mechanism, and the same keys for save (corresponding to Flow submit) and preview (corresponding to Flow ""switch to VE"") as standard edit pages (mouse over the save and preview buttons).",1439331104,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,Is there a different shortcut we could use? ,1439328813,PHID-USER-37czexl6ekrvcmp2tyqq,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,Ctrl+Enter is currently taken over by UniversalLanguageSelector. T106700,1439326993,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"A request for Ctrl-Enter (Cmd-Enter) to ""Save"" an edit, via twitter: https://twitter.com/MagnusManske/status/631122281931112448  (and the previous onwiki discussion I linked above, also suggested this standard key combination)",1439326509,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"Thanks Eduard. :)
+
+Tracked at https://trello.com/c/Y8vvggBw/99-keyboard-shortcuts-accesskeys
+
+with previous discussion and notes at https://www.mediawiki.org/w/index.php?title=Talk:Flow&topic_postId=roaqtzq187eo7d74&workflow=roaqtzq187eo7d74",1392841990,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"For projects built with npm (e.g. VE, OOjs UI) this could be relatively easy, but for MW core I imagine it's a bit harder to parse .php files.
+
+(For VE we'd want this blocking merge, but that's a distinct conversation.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392753720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q5awmwers7vnmtk3yywm,task_description,resolved
+Have an i18n CI job that ensures there's a qqq message for each en message,Other repositories (i.e. MediaWiki extensions) will be checked using a dedicated Jenkins job. That is the purpose of bug 64045.,1397719573,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Change 125050 merged by jenkins-bot:
+Use new banana checker as a linter to avoid lacking qqq messages
+
+https://gerrit.wikimedia.org/r/125050",1397692280,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"(In reply to Gerrit Notification Bot from comment #5)
+> Change 5550 abandoned by Jforrester:
+> tests to compare En, Qqq and messages.inc
+> 
+> Reason:
+> Replaced by https://www.npmjs.org/package/grunt-banana-checker now.
+> 
+> https://gerrit.wikimedia.org/r/5550
+
+Sounds good to me :-]",1397640219,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Change 5550 abandoned by Jforrester:
+tests to compare En, Qqq and messages.inc
+
+Reason:
+Replaced by https://www.npmjs.org/package/grunt-banana-checker now.
+
+https://gerrit.wikimedia.org/r/5550",1397600038,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Done in https://www.npmjs.org/package/grunt-banana-checker – gerrit 125050 adds this to MediaWiki core; gerrit 124069, gerrit 124023 and gerrit 124021 added it to OOjs UI, VisualEditor, and VisualEditor-MediaWiki.",1397600012,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Change 125050 had a related patch set uploaded by Jforrester:
+Use new banana checker as a linter to avoid lacking qqq messages
+
+https://gerrit.wikimedia.org/r/125050",1397596499,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Change 5550 had a related patch set uploaded by Hashar:
+tests to compare En, Qqq and messages.inc
+
+https://gerrit.wikimedia.org/r/5550",1393242023,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"For mediawiki/core I once wrote a test suite that compares messages in messages.inc, en and qqq https://gerrit.wikimedia.org/r/#/c/5550/
+
+They are not passing though and I don't really have the mood to complete this patch though :-(",1393242009,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"Last working job:
+  https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/942/console
+
+  - Feb 16, 2014
+  - Building remotely on integration-slave01
+
+  - node v0.10.22
+  - npm v1.1.38
+
+First failing job:
+  https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/943/console
+
+  - Feb 18, 2014
+  - Building remotely on integration-slave02
+
+  - node v0.8.2
+  - npm v1.1.39
+
+16:23:41 npm ERR! Error: SSL Error: CERT_UNTRUSTED
+16:23:41 npm ERR!     at ClientRequest.<anonymous> 
+16:23:41 npm ERR!     at Socket.ondata (stream.js:38:26)
+16:23:41 npm ERR!  [Error: SSL Error: CERT_UNTRUSTED]
+
+Server log:
+  https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&diff=99596&oldid=99549
+
+
+  - February 17
+    - 16:15 hashar: Jenkins deleting slave integration-slave01
+    - 16:14 hashar: Jenkins added two labs slaves with 4 CPU: integration-slave02 and integration-slave03
+    - 08:46 hashar: Upgrading Jenkins, half an hour downtime
+
+
+
+So npm was upgraded one minor version, and nodejs was downgraded *2 major versions*, and (possibly unrelated) it seems to be unable to verify the certificate properly.
+
+According to existing bug reports, this is related to it being a self-signed certificate, however this shouldn't be a problem since a validation mechanism for their official certificate ships with the npm package. Upstream recommends upgrading to the most recent minor version, but that doesn't seem to be the problem considering the bug started happening for us overnight (no certificate change upstream) when we went from v1.1.38 to v1.1.39 (not down).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://github.com/npm/npm/issues/4838",1392752580,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_description,resolved
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"Existing instances have been patches so marking this as fixed.
+
+The fact that we need to puppetize the patches is a separate bug.
+
+See:
+* bug 68256
+* bug 66056
+
+And the patches are documented at:
+https://wikitech.wikimedia.org/wiki/Nova_Resource:Integration/Setup",1405742229,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,The new,1405719711,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,Thank you Timo for fixing up the installation on integration-slave1003.  I guess we can close that bug since you proposed to use node 10.x on bug 66056 which would definitely fix the issue.,1401752463,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"(In reply to Antoine ""hashar"" Musso from bug 66048 comment #1)
+> Node marked offline on
+> https://integration.wikimedia.org/ci/computer/integration-slave1003/
+
+Brought back online.",1401749458,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,*** Bug 66048 has been marked as a duplicate of this bug. ***,1401749314,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&oldid=115053
+
+> 20:08 hashar: Jenkins unpolled integration-slave1003 npm is outdated there and does not trust npmregistry.org ( bug 61508 )
+> 22:37 Krinkle: Hack-patching integration-slave1003.eqiad.wmflabs per https://bugzilla.wikimedia.org/show_bug.cgi?id=61508#c2
+
+
+krinkle at integration-slave1003.eqiad.wmflabs in ~
+$ node --version
+v0.8.2
+
+$ npm --version
+1.1.39
+
+$ sudo -s
+# export HOME=/root
+# npm conf set strict-ssl false
+# l /usr/bin/npm
+
+  /usr/bin/npm -> /etc/alternatives/npm*
+
+# rm /usr/bin/npm
+# /etc/alternatives/npm install -g npm
+
+  ...
+  npm@1.4.13 /usr/lib/node_modules/npm
+
+# cd /tmp && mkdir foo123 && cd foo123
+# npm install jshint
+
+  .. success ..
+  jshint@2.5.1 node_modules/jshint
+
+# l `which npm`
+
+  /usr/bin/npm -> ../lib/node_modules/npm/bin/npm-cli.js*
+
+# npm conf set strict-ssl true
+
+# cd ~ && rm -rf /tmp/foo123/
+# npm install -g grunt-cli
+
+  .. success ..
+  /usr/bin/grunt -> /usr/lib/node_modules/grunt-cli/bin/grunt
+  grunt-cli@0.1.13 /usr/lib/node_modules/grunt-cli
+
+# npm --version
+1.4.13
+# grunt --version
+grunt-cli v0.1.13",1401748882,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,Has this recurred?,1401745339,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"I was a bit upset this morning. I have applied Timo fix from Comment #2 on all four instances:
+
+ integration-slave02.pmtpa.wmflabs
+ integration-slave03.pmtpa.wmflabs
+ integration-slave1001.eqiad.wmflabs
+ integration-slave1002.eqiad.wmflabs
+
+Seems to work now.",1395237768,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"(In reply to Nemo from comment #7)
+> I don't know if it's the same for you, but docs were wrong for me.
+> <https://www.mediawiki.org/w/index.
+> php?title=Parsoid%2FSetup&diff=930615&oldid=930612>
+
+The doc instructs to use a ppa which provides 0.10.x.  We do not use ppa.",1395227517,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,Mailed ops list.  The Parsoid and VisualEditor npm jobs are now failing and preventing changes to be merged until the SSL cert issue is properly fixed.,1395227463,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"(In reply to Antoine ""hashar"" Musso from comment #6)
+> Will mail ops list to figure out how to get nodejs 0.10.x marked for install
+> on those hosts.
+
+I don't know if it's the same for you, but docs were wrong for me.
+<https://www.mediawiki.org/w/index.php?title=Parsoid%2FSetup&diff=930615&oldid=930612>",1395226795,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"For some reason I managed to get the pmtpa slave nodes back to nodejs 0.8.x which break the VisualEditor npm jobs.
+
+I also created two new slaves in eqiad (integration-slave1001 and integration-slave1002) and they come up with nodejs 0.8.x as well.
+
+Will mail ops list to figure out how to get nodejs 0.10.x marked for install on those hosts.",1395226165,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"(In reply to Antoine ""hashar"" Musso from comment #3)
+> integration-slave01 received nodejs 0.10.x when it got added to
+> apt.wikimedia.org. It has been later removed but the instance never got
+> cleaned up.
+> 
+> npm, I have no idea, probably similar.
+> 
+> 
+> I dont want the slaves to be tweaked manually, everything must be in puppet.
+> So there is a few bugs that we should fill all related to updating packages
+> in apt.wikimedia.org:
+> 
+> * nodejs 0.10.x (that is apparently a work in progress)
+> * npm 1.3.10 should be backported from Ubuntu Trusty
+> * grunt-cli needs to be packaged
+> 
+> Then we can update the list of packages in operations/puppet.git file
+> ./modules/contint/manifests/packages/labs.pp . It list npm but no grunt-cli
+> since there is no package there.
+> 
+> Does it sound right?
+
+Yes, except for grunt-cli needing to be packaged. We explicitly don't want to do that, like the over 300 other arbitrary npm modules we fetch daily on the integration slaves based on things listed in package.json in local repositories, this yet just another package like that. We can and should (for consistency and for it being the right version) install this via npm.
+
+I'm sure there is a puppet syntax for ensuring a certain shell command has been executed (e.g. based on a certain file existing). Similar to how we use git::clone in some places and the puppet file{} syntax. They're not provisioned packages, just inline specified within our manifest created by something other than a package (a rb template file, a git clone, or, in this case, an npm install)",1394660054,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,Lowering priority and assigning back to Timo.  He applied a workaround.  Still have to fill bugs as mentioned in comment #3,1393240120,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"integration-slave01 received nodejs 0.10.x when it got added to apt.wikimedia.org. It has been later removed but the instance never got cleaned up.
+
+npm, I have no idea, probably similar.
+
+
+I dont want the slaves to be tweaked manually, everything must be in puppet. So there is a few bugs that we should fill all related to updating packages in apt.wikimedia.org:
+
+* nodejs 0.10.x (that is apparently a work in progress)
+* npm 1.3.10 should be backported from Ubuntu Trusty
+* grunt-cli needs to be packaged
+
+Then we can update the list of packages in operations/puppet.git file ./modules/contint/manifests/packages/labs.pp . It list npm but no grunt-cli since there is no package there.
+
+Does it sound right?",1392827453,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"krinkle at integration-slave03:
+
+# Enter root and fix HOME so that npm doesn't put cache in /home
+# which is read-only in labs (why?)
+$ sudo -s
+$ export HOME=/root
+
+# Temporarily disable ssl check
+$ npm conf set strict-ssl false
+
+# Remove symlink to apt-get installed version
+# because npm is not allowed to to delete this shadow 
+$ l /usr/bin/npm
+  /usr/bin/npm -> /etc/alternatives/npm*
+$ rm /usr/bin/npm
+
+# Upgrade npm
+$ /etc/alternatives/npm install -g npm
+
+ npm@1.1.39
+ ...
+ npm@1.4.3
+
+# Re-enable ssl check
+$ npm conf set strict-ssl true
+
+# Verify that stuff works by doing an
+# install of an example package (jshint)
+# in a tmp dir
+$ cd /tmp && mkdir foo123 && cd foo123
+$ npm install jshint
+ ...
+ success
+$ cd ~
+$ rm -rf /tmp/foo123
+
+# Install Grunt
+$ npm install -g grunt-cli
+
+ ...
+ success",1392755172,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"So the certificates partially ship with nodejs, not the npm package.
+
+Upstream nodejs takes care to backport these cert changes to v0.8, however the slaves not only downgraded from v0.10 to v0.8 but also to an way older minor release of the v0.8 branch.
+
+There have been 24 (!) minor releases since v0.8.2, latest is v0.8.22.
+
+In case this particular cert change can be mitigated by only upgrading npm, I've done a manual upgrade of npm on the individual instances using npm itself:
+
+ $ sudo -s
+ $ npm conf set strict-ssl false
+ $ npm install -g npm
+ npm 1.1.39
+ ...
+ npm 1.4.3
+ $ npm conf set strict-ssl true
+ $ cd /tmp && mkdir foo123 && cd foo123
+ $ npm install jshint
+ success
+
+The jobs still fail after this because the new labs slaves are also missing grunt.
+
+ $ sudo -s
+ $ npm install -g grunt-cli
+ success
+
+
+Note that I couldn't interact with npm the normal way because for some reason /home is read-only on the integration instances (even in root, npm still uses your original home as location to do some temporary work and caching).
+
+Had to set `export HOME=/root` to bypass that.",1392754229,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+Reusing references inside the VE template dialog,"The VE template dialog can - with the help of #templatedata - show input fields for a template's parameters. Usually these are simple text fields that offer no editing tools.
+
+As a user it would be nice to have a simple way to add references or re-use reference from the main article to input fields in dialog.
+
+A way to move forward here could be:
+- For a specific template parameter type (e.g. `content`) add...
+- ...either a button that opens the Citation dialog and adds wikitext, similar to how it's done in the WTE2017
+- ...or add a ""inline"" VisualEditor similar to what's done for the image dialog's caption field ",1392748620,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-fuicnfjgm4dh24qhshha,task_description,open
+Reusing references inside the VE template dialog,{T52896} seems closely related.,1510253286,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-fuicnfjgm4dh24qhshha,task_subcomment,NA
+VisualEditor: Automatically remove empty ref tags (and refuse to insert new ones),"If you add an empty, unnamed reference in wikitext (""<ref />""), then you get an empty, invalid reference.
+
+If you add an empty, unnamed reference in VisualEditor (Insert>Reference, then ""Add reference"" without typing anything), then you get an empty, invalid reference.
+
+VisualEditor should do better than wikitext:  it should detect empty, unnamed ref tags and refuse to insert them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392746820,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-e22m3ew36smar7n5obdf,task_description,resolved
+VisualEditor: Automatically remove empty ref tags (and refuse to insert new ones),We fixed this a while ago. Sorry for the slow triage!,1403743200,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e22m3ew36smar7n5obdf,task_subcomment,NA
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,"**Author:** `duongxvu`
+
+**Description:**
+I was wondering whether it is possible for VisualEditor to work with other skins besides the officially supported ones (which I believe to be Vector, Monobook, and Apex). I’ve been tasked with creating a custom skin to meet my organization’s existing design standards, but it does not seem so easy to add support for VisualEditor in this regard. And documentation addressing similar issues to mine seem to be rare at the moment.
+
+For now, I've heavily modified Vector as a workaround, but would prefer a more long-term solution if one exists. I assume that the Vector skin will continue to receive regular updates in the future, and I’d like to avoid having to modify it every time that happens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://www.mediawiki.org/wiki/VisualEditor/Skin_requirements",1392743160,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-adi2ks5r3obfupmjeuws,task_description,resolved
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,I'm going to deem this fixed based on the details in https://www.mediawiki.org/wiki/VisualEditor/Skin_requirements now available.,1401204582,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-adi2ks5r3obfupmjeuws,task_subcomment,NA
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,"I have a skin ([[Skin::Cameleon]]) that's based on Dantmman's excellent tutorial ([[Manual:Skinning/Tutorial]]). All I really did (aside from installing Visual Editor) was to add my skin's name to the $wgVisualEditorSupportedSkins global array variable.
+
+We already found a number of CSS issues, that need fixing, but aside from that it seems to work.",1399754193,PHID-USER-cc6dswbtmstfsb4ldmit,PHID-TASK-adi2ks5r3obfupmjeuws,task_subcomment,NA
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,"I started writing some notes about what VE expects of skins in https://docs.google.com/a/wikimedia.org/document/d/1awG4IKujTFd72RJzr_4DVInKDO1BqRxRHbTnCHvYLr4/edit (Obviously, when I started a Google doc I expected to end up writing more. :/). Looking for feedback.
+
+Currently it starts with the IDs it expects to be present and then a note relating to Gerrit change 130085 and Gerrit change 130656.
+
+Never having made a skin myself I'm not 100% confident about what we need to make clear here or what's wanted by the bug reporter.",1399062940,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-adi2ks5r3obfupmjeuws,task_subcomment,NA
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,"Yes, we currently don't document well what requirements we have on skins (because we're adding requirements as we go). We should improve documentation so that it's easier for skin maintainers to know what they need to do.",1394503143,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-adi2ks5r3obfupmjeuws,task_subcomment,NA
+VisualEditor: Using auto select zhu-yin input and it keeps bouncing duplicate chinese characters,"Please go to the youtube link for fully demo http://www.youtube.com/watch?v=DZ90EDLqHUI
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Mac OS X 10.6
+**Platform**: Macintosh",1392515640,PHID-USER-adqeptkffhhfdhukexph,PHID-TASK-n7aygelprycptenbqxi4,task_description,open
+VisualEditor: Using auto select zhu-yin input and it keeps bouncing duplicate chinese characters,"**Coiby.Xu** wrote:
+
+Same problem on Ubuntu 13.04, Firefox 26 and Chrome 33. I've tested both on wikipedia and local server.
+
+For the details, see https://www.mediawiki.org/wiki/Talk:VisualEditor#first_line_comes_out_extra_words_when_typing_chinese.",1396437642,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-n7aygelprycptenbqxi4,task_subcomment,NA
+VisualEditor: Ref group does not get updated when the group name is changed from References List dialog,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add a reference with a group name ""first group""
+3.Now Add a references list but under Use this group, type ""first group one""
+4.Apply changes.(""there are no references with this group"" will appear which is correct)
+5.Now reopen the References list dialog again.
+6.Just delete the ""one"" from ""first group one"" to make it ""first group""
+7.Apply changes
+
+Observed Result:
+Even this time it says ""there are no references with this group"" which is wrong.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392415980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2f5c5qfnz7mu3qheybrb,task_description,resolved
+VisualEditor: Ref group does not get updated when the group name is changed from References List dialog,"This appears fixed, although I have no idea which patch and when could have fixed it.",1540268768,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2f5c5qfnz7mu3qheybrb,task_subcomment,NA
+VisualEditor: A black shadow is appearing in the Cite Web template dialog inside Media Settings after scrolling down a bit,"The shadow
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings for that image
+4.Go to Insert>Transclusion
+5.Search for the Cite Web template
+6.Add a value for URL and Source Title
+7.Apply Changes
+8.Now again re-open the cite web dialog for the template you just added
+9.When all the parameter list appears in the dialog box , scroll down a bit.
+
+Observed Result:
+
+Observe that,there is a black shadow appearing on the border above the Apply Changes button, it seems to me coming from the ""URL Access Date"" field as it was initially aligned with that border.
+
+
+See the screenshot attached to better understand the problem
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12975}",1392411060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ceazwtjwm6a7jnascqca,task_description,resolved
+VisualEditor: A black shadow is appearing in the Cite Web template dialog inside Media Settings after scrolling down a bit,Verified the fix.,1401476052,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ceazwtjwm6a7jnascqca,task_subcomment,NA
+VisualEditor: A black shadow is appearing in the Cite Web template dialog inside Media Settings after scrolling down a bit,"This appears to now be fixed, AFAICT, due to the changes to this layout. Closing.",1401418554,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ceazwtjwm6a7jnascqca,task_subcomment,NA
+VisualEditor: A black shadow is appearing in the Cite Web template dialog inside Media Settings after scrolling down a bit,"Created attachment 14594
+The position of URL access date field when the dialog is opened
+
+**Attached**: {F12976}",1392411126,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ceazwtjwm6a7jnascqca,task_subcomment,NA
+VisualEditor: Be able to access a display file's description page from within VE (e.g. in the media settings dialog),"On inserting an image, or editing an image, it should be possible to visit the file description page. Currently it's not even possible to get the filename of an image when in VE.
+
+Why this is needed: In order to access the captions on the image page or verify the license or similar. E.g. on inserting an image of Obama shaking hands with some other important person into the Obama article you might want to find out who this other person is
+
+Suggested solution: Add a link to the filepage in media settings.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392369960,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-tv45m2ck4vwdr4ovivkr,task_description,resolved
+VisualEditor: Be able to access a display file's description page from within VE (e.g. in the media settings dialog),"This was implemented during the last major work on the media dialog.  Choose an image from the search results, and click on the ""More information"" link (at the end of list of information about the image).",1434918715,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-tv45m2ck4vwdr4ovivkr,task_subcomment,NA
+VisualEditor: Uncaught SyntaxError: Invalid flags supplied to RegExp constructor 'index'  appears in production while saving any change from Edit Source mode,"Screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make some changes
+3.Switch to edit source mode
+4.Save the page from Edit source mode
+
+Observed Result:
+Uncaught SyntaxError: Invalid flags supplied to RegExp constructor 'index' appears in the console
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12828}",1392322440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pikh7ix5hnqd4nnyiadm,task_description,invalid
+VisualEditor: Uncaught SyntaxError: Invalid flags supplied to RegExp constructor 'index'  appears in production while saving any change from Edit Source mode,Bug caused by the Citation expander gadget.,1392335656,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pikh7ix5hnqd4nnyiadm,task_subcomment,NA
+VisualEditor: Rich paste fails and crashes surface with (? specific) content,"Steps to replicate:
+
+1. Edit an article in VisualEditor (or start a new one)
+2. Go to http://git-scm.com/download/linux
+3. Copy the list, from ""Debian/Ubuntu"" to the end of the content in the white space.
+4. Paste into the article in VE.
+
+Observed: 
+
+""Uncaught TypeError: Cannot call method 'getComparableObjectForSerialization' of undefined""
+
+After that, interaction with the CE - mostly with link inspector and surface widgets produces errors or is unresponsive (Without console error)
+
+I got this when I tried to add a link: ""Uncaught TypeError: Cannot call method 'getSurface' of null""
+""
+
+
+
+Chrome 32.0.1700.107 under Ubuntu 12.04.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392321600,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ps7lp2luxy7m2thoc7zr,task_description,resolved
+VisualEditor: Rich paste fails and crashes surface with (? specific) content,"Committed while bugzilla was down:
+https://gerrit.wikimedia.org/r/#/c/113538/",1392744740,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ps7lp2luxy7m2thoc7zr,task_subcomment,NA
+VisualEditor: Rich paste fails and crashes surface with (? specific) content,"This is a bug in remapStoreIndexes, so this only happens when the target document already has some annotations, and the content being pasted has annotated elements (in Moriel's case, a <br> inside a <code>)",1392476991,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ps7lp2luxy7m2thoc7zr,task_subcomment,NA
+VisualEditor: Rich paste fails and crashes surface with (? specific) content,WFM in standalone and MediaWiki. Can anyone else reproduce?,1392374805,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ps7lp2luxy7m2thoc7zr,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"**Author:** `swalling`
+
+**Description:**
+Francais
+
+Edit beta is specific to English Wikipedia but we hard coded it in the tour text for GettingStarted, so it is showing up incorrectly in translated versions such as French etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12815}",1392312420,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lfp625smnes4vmcpcaey,task_description,resolved
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"Change 114698 merged by Phuedx:
+Use VisualEditor configuration for appendices (e.g. beta).
+
+https://gerrit.wikimedia.org/r/114698",1392999633,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"Change 114698 had a related patch set uploaded by Mattflaschen:
+Use VisualEditor configuration for appendices (e.g. beta).
+
+https://gerrit.wikimedia.org/r/114698",1392962475,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,This is in a firsteditve message in the GuidedTour extension.,1392937652,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"See the attachment for the issue.  Note how the guider says ""Modifier bêta"", but the actual tab just says ""Modifier"".  We want to fix the guider to check the configuration and always match the tab.",1392402776,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"(In reply to Nemo from comment #2)
+> (In reply to Matthew Flaschen from comment #1)
+> > It's easy to detect if this is enabled (mw.config.get(
+> > 'wgVisualEditorConfig' ).tabMessages).  However, I need to decide whether to
+> > make separate messages or substitute it in.
+> 
+> Can you pass two messages to it directly?
+
+Sorry, I'm a little unclear what you mean.  What would the two messages be, and what would I pass them to?
+
+> If the message(s) are just '{{int:vector-view-edit}}
+> {{int:visualeditor-beta-appendix}}' it's not less lego to have two. You can
+> pass to the tab a message '{{int:vector-view-edit}}$1"" where $1 is nothing
+> or ""&#160;{{int:visualeditor-beta-appendix}}"".
+
+I'm not controlling the text of the tab (sorry, the bug title was misleading).  I'm controlling the text of the guider (a kind of modal popup), which refers to the text of the tab.
+
+However, I think your suggestion of using a parameter just for the second part could still apply.",1392402667,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"(In reply to Matthew Flaschen from comment #1)
+> It's easy to detect if this is enabled (mw.config.get(
+> 'wgVisualEditorConfig' ).tabMessages).  However, I need to decide whether to
+> make separate messages or substitute it in.
+
+Can you pass two messages to it directly?
+
+> 
+> Is this an acceptable use of a parameter (passing either
+> '{{int:vector-view-edit}} {{int:visualeditor-beta-appendix}}""' or
+> '{{int:vector-view-edit}}' depending on configuration?
+> 
+> Or should I make separate messages?
+
+If the message(s) are just '{{int:vector-view-edit}} {{int:visualeditor-beta-appendix}}' it's not less lego to have two. You can pass to the tab a message '{{int:vector-view-edit}}$1"" where $1 is nothing or ""&#160;{{int:visualeditor-beta-appendix}}"".",1392362941,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"It's easy to detect if this is enabled (mw.config.get( 'wgVisualEditorConfig' ).tabMessages).  However, I need to decide whether to make separate messages or substitute it in.
+
+Is this an acceptable use of a parameter (passing either '{{int:vector-view-edit}} {{int:visualeditor-beta-appendix}}""' or '{{int:vector-view-edit}}' depending on configuration?
+
+Or should I make separate messages?",1392340028,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"After a discussion with no objections amongst the OTRS administrators on our mailing list, we would like to have the Translate extension enabled on OTRS wiki to facilitate translating messaging. Thanks!
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1392259920,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-fde4qftmev4t5neslgqj,task_description,resolved
+Enable Extension:Translate on OTRS wiki,"Just to make it clear, {{autotranslate}} ({{int:Lang}}), LangSelect (+ {{mld}}), LanguageSelection, LangSwitch have nothing to do with the Translate extension.",1393409802,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"(In reply to Steinsplitter from comment #11)
+> {{autotranslate}} dos not work. The template seems okay. (problems with
+> {{int:*}} ?).
+> 
+> Can someone pleas take a look?
+
+They actually do work, I just overlooked something and told Steinsplitter that they don't seem to work...",1393368243,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"{{autotranslate}} dos not work. The template seems okay. (problems with {{int:*}} ?).
+
+Can someone pleas take a look?",1393366880,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Bungled jargon. Tomasz for the patch/commit,  Reedy deploy. Thanks.",1392370885,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Thanks for the patch, Tomasz, thanks for the commit, Reedy, thanks for the comments, all. This should a very small but useful tool in agent onboarding. :)",1392368934,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,Merged & deployed by Reedy; the extension is now available on the wiki (and working).,1392368737,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Change 113160 merged by jenkins-bot:
+Enable Translate extension on OTRS wiki
+
+https://gerrit.wikimedia.org/r/113160",1392333185,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Change 113160 had a related patch set uploaded by Odder:
+Enable Translate extension on OTRS wiki
+
+https://gerrit.wikimedia.org/r/113160",1392315891,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"(In reply to Keegan Peterzell from comment #0)
+> After a discussion with no objections amongst the OTRS administrators on our
+
+Who? The OTRS admins, the admins on OTRS wiki, the end users on OTRS wiki?
+
+From what i've heard the end users (aka the otrs agents that use the wiki) haven't even been really asked for consensus…",1392289630,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,You would have to do without a translation memory if the content is private.,1392286498,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Eh, I'd rather see OTRS pick up VisualEditor (which is incompatible with the Translate extension...) than the Translate extension. It's a bit of a rough user experience. However the Translate extension _is_ supported on the cluster and if the OTRS admins want it (after consulting with the relevant stakeholders), it's fine to enable there.
+
+This happens to be MediaWiki configuration related to OTRS rather than OTRS configuration related to Wikimedia, so this goes into ""Site requests"" with the ""shell"" keyword.",1392264928,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Yes, it would be useful for providing documentation pages (like Help: space) in other languages for agents.",1392261727,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"(In reply to Keegan Peterzell from comment #0)
+> wiki to facilitate translating messaging. Thanks!
+
+For such a small wiki, Do you really want it? It does complicate the subpage management workflow for some simple functions.",1392260690,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+"VisualEditor: Using ""Make full size"" doesn't work when size is default","Maggie Dennis on bug 50645:
+> I'm not sure if this is the same issue, but as reported on English Wikipedia
+> and tested by myself, using the image resizer to ""Make full size"" resulted in
+> either a notice that no change had been made or a silent failure to save.
+> 
+> This was tested on FF26, W7 and Chrome 32.0.1700.107 m, W7. 
+> 
+> The reporting editor concludes that ""These new settings, for what they are
+> worth, only work if the image already has a size indication (200px,
+> 250px*250px, whatever), not when it only has a 'thumb' indication. Sadly, the
+> latter is the default and by far most common situation.""
+> 
+> He also questions the purpose of ""Make full size"", but I'll report that
+> separately. 
+> 
+> See:
+> https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Feedback&oldid=595141503#Advanced_image_settings.
+> 3F_More_VisualEditor_rubbish.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392223320,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gwz2iw7f66yzzxl37lvc,task_description,resolved
+"VisualEditor: Using ""Make full size"" doesn't work when size is default","Change 112942 had a related patch set uploaded by Jforrester:
+Update image size properly when size is default
+
+https://gerrit.wikimedia.org/r/112942",1392238144,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gwz2iw7f66yzzxl37lvc,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"In an effort to allow the legal and lca team to work directly on a wiki more often (including for legally sensitive work) and to move away from google docs and the like as much as possible we would like to set up a private wiki for the team.
+
+In general Ombudsmanwiki would be a good wiki to copy settings from but for the ones I can think of off the top of my head:
+
+Wiki domain should be legalwiki.wikimedia.org.
+Language should be English.
+Logo can be $stdlogo.
+Favicon can be wmf.ico
+Canonical server should be https (forced should be on).
+Account creation should be bureaucrat only (not sysop).
+Transwiki destinations of office, collab and meta would be helpful. (Not sure if private wikis can be tw destinations though... if not that's fine.
+wmgUseDisableAccount should be true
+
+I can be the original sysop/crat.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1392140760,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-cpftde25rzzyhyrt3v2b,task_description,resolved
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,All done here methinks! Enjoy your new wiki.,1394607638,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 117377 merged by jenkins-bot:
+Add logo for legalteamwiki
+
+https://gerrit.wikimedia.org/r/117377",1394546157,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 117377 had a related patch set uploaded by Jalexander:
+Add logo for legalteamwiki
+
+https://gerrit.wikimedia.org/r/117377",1394162684,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to Sam Reed (reedy) from comment #21)
+> (In reply to Sam Reed (reedy) from comment #20)
+> > Does $stdlogo work on other privte wikis?
+> > https://upload.wikimedia.org/wikipedia/legalteam/b/bc/Wiki.png 404s
+> 
+> Because it won't have been uploaded yet... Duh.
+
+Yup, but you are indeed correct, it doesn't work for private wikis because it puts it into a different (private) file url scheme which you have to be logged in to use. I'm uploading a config patch with the logo.",1394162386,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to Sam Reed (reedy) from comment #20)
+> Does $stdlogo work on other privte wikis?
+> https://upload.wikimedia.org/wikipedia/legalteam/b/bc/Wiki.png 404s
+
+Because it won't have been uploaded yet... Duh.",1394120051,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"This is mostly done now...
+
+Does $stdlogo work on other privte wikis? https://upload.wikimedia.org/wikipedia/legalteam/b/bc/Wiki.png 404s",1394120010,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112717 merged by jenkins-bot:
+Enable VisualEditor for legalteamwiki by default
+
+https://gerrit.wikimedia.org/r/112717",1394119668,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112850 merged by jenkins-bot:
+Initial setup for legalteamwiki
+
+https://gerrit.wikimedia.org/r/112850",1394117165,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 116219 merged by Mark Bergsma:
+Apache config for legalteamwiki
+
+https://gerrit.wikimedia.org/r/116219",1394116057,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 116220 merged by Mark Bergsma:
+DNS setup for legalteamwiki
+
+https://gerrit.wikimedia.org/r/116220",1394115465,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 116220 had a related patch set uploaded by Jalexander:
+DNS setup for legalteamwiki
+
+https://gerrit.wikimedia.org/r/116220",1393646524,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 116219 had a related patch set uploaded by Jalexander:
+Apache config for legalteamwiki
+
+https://gerrit.wikimedia.org/r/116219",1393645632,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112716 merged by jenkins-bot:
+Add support for new private legalteamwiki
+
+https://gerrit.wikimedia.org/r/112716",1393343728,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112850 had a related patch set uploaded by TTO:
+Initial setup for legalteamwiki
+
+https://gerrit.wikimedia.org/r/112850",1392185679,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #10)
+> I note that ombudsmenwiki assigns no rights to the autoconfirmed and
+> confirmed
+> groups (except OAuth and transcode rights). Is this required for
+> legalteamwiki?
+
+hmm, no, I just saw that... not entirely sure why that was done but it would be best to still allow the normal options on legalteamwiki. I don't anticipate semi protection being a thing on the wiki obviously but no reason to turn something off (especially upload) without reason.",1392171922,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,I note that ombudsmenwiki assigns no rights to the autoconfirmed and confirmed groups (except OAuth and transcode rights). Is this required for legalteamwiki?,1392171322,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"
+> How about legalteam.wikimedia.org? Using the name legalwiki.wikimedia.org
+> could
+> be confusing, as wiki internal names are by convention formed by taking the
+> subdomain and adding ""wiki"".
+
+> I also disagree with 'legalwiki.wikimedia.org', especially if you see the
+> potential of using legal.wikimedia.org in the future (which would probably
+> be a
+> wiki too, the difference between the two then actually being access controls
+> -
+> and obviously content).
+
+I'm fine with legalteam if we prefer, I don't really care I just want it to make sense and get done :).",1392170704,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"I also disagree with 'legalwiki.wikimedia.org', especially if you see the potential of using legal.wikimedia.org in the future (which would probably be a wiki too, the difference between the two then actually being access controls - and obviously content).",1392170512,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #5)
+> (In reply to comment #1)
+> > Why not legal.wikimedia.org?
+> 
+> To keep legal.wikimedia free incase it's wanted for something broader and
+> more
+> open then a confidential wiki.
+
+How about legalteam.wikimedia.org? Using the name legalwiki.wikimedia.org could be confusing, as wiki internal names are by convention formed by taking the subdomain and adding ""wiki"".",1392170239,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #0)
+> Transwiki destinations of office, collab and meta would be helpful. (Not sure
+> if private wikis can be tw destinations though... if not that's fine.
+
+I don't know that either but would guess that not. Even if, you'd have the problem that any sysop on the target wiki could then make guesses which pages exist on the private wiki and try to import them.",1392142192,PHID-USER-7e4yonmruupxzg23swum,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #1)
+> (In reply to comment #0)
+> 
+> > Wiki domain should be legalwiki.wikimedia.org.
+> 
+> Why not legal.wikimedia.org?
+
+To keep legal.wikimedia free incase it's wanted for something broader and more open then a confidential wiki.",1392142072,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Above patches will allow VisualEditor support; it needs to be created first, however (obviously).",1392141490,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112717 had a related patch set uploaded by Jforrester:
+Enable VisualEditor for legalwiki by default
+
+https://gerrit.wikimedia.org/r/112717",1392141396,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112716 had a related patch set uploaded by Jforrester:
+Add support for new private legalwiki
+
+https://gerrit.wikimedia.org/r/112716",1392141273,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #0)
+
+> Wiki domain should be legalwiki.wikimedia.org.
+
+Why not legal.wikimedia.org?",1392140983,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Enable VisualEditor on frwikiversity,"Per e-mail request
+
+Consensus: https://fr.wikiversity.org/wiki/Projet:Wikiversit%C3%A9/Editeur_Visuel
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1392067440,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3i3uyys5czodi4h5dtpg,task_description,resolved
+Enable VisualEditor on frwikiversity,This is now done.,1392253986,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3i3uyys5czodi4h5dtpg,task_subcomment,NA
+Enable VisualEditor on frwikiversity,"Change 112582 had a related patch set uploaded by Jforrester:
+Enable VisualEditor in opt-in mode for French Wiktionary
+
+https://gerrit.wikimedia.org/r/112582",1392067948,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3i3uyys5czodi4h5dtpg,task_subcomment,NA
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings>Advanced Settings for the image
+4.Select the value ""None"" under the postion 
+
+Observed Result:
+Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page
+
+See the screenshot attached.
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/10thFeb
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13027}",1392061500,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_description,declined
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page",Think this is OK now?,1395354482,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_subcomment,NA
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page","When I try this in betalabs, the image shifts to the left of the page when I select ""None"", as expected.
+
+There is, however, another bug where the image doesn't have an *initial* position visible in the editor. That is fixed in the upcoming commit that I mentioned above.",1392158997,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_subcomment,NA
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page","I can't manage to replicate this bug in master. ""None"" shifts the image to the left in an English wiki, and right in an RTL wiki (Hebrew on my local machine)
+
+That said, this fix changes the behavior of the position widget. I tested it under that commit as well and couldn't replicate in both Chrome and Firefox.
+
+https://gerrit.wikimedia.org/r/#/c/112041/",1392155216,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_subcomment,NA
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page","After that , Selecting Right moves the image to the left",1392061763,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"'Cos we do most of the others.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1391818800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fm5h62v32kkok5qvd6go,task_description,resolved
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"Change 133037 merged by jenkins-bot:
+Allow VisualEditor users to set if a page whether a Disambiguation
+
+https://gerrit.wikimedia.org/r/133037",1402341616,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"Change 130328 merged by jenkins-bot:
+Allow extensions to add extra meta item checkboxes to the page settings dialog
+
+https://gerrit.wikimedia.org/r/130328",1401323601,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"Change 133037 had a related patch set uploaded by Alex Monk:
+Allow VE users to set whether a page is for Disambiguation or not
+
+https://gerrit.wikimedia.org/r/133037",1399936920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"Change 130328 had a related patch set uploaded by Alex Monk:
+Allow users to set whether a page is for Disambiguation or not
+
+https://gerrit.wikimedia.org/r/130328",1398775468,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"I guess we could query action=paraminfo&querymodules=querypage and look for ""DisambiguationPages"" in data.paraminfo.querymodules[0].parameters[0].type
+
+Would prefer not to though. Might have to pass whether or not Disambiguation is there via paction=parse (ugh)",1398773973,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,Looks like we need to try to detect the Disambiguation extension somehow...,1398126883,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"Appears towards the end of the page
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Select a text in such way that it selects the whole line
+3.Now open the link inspector
+
+Observed Result:
+
+Sometimes the link inspector appears in a broken way and sometimes it appears little below the text towards the end of the page
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12833}",1391817120,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-db4a2ffve3au67ttwvrv,task_description,resolved
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"On discussion, we'll leave this as is.",1406322759,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-db4a2ffve3au67ttwvrv,task_subcomment,NA
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"Created attachment 15640
+12thjune
+
+The broken UI issue seems like got fixed, but if a gallery follows a line and I select the whole line and try to open the link inspector , it still opens at the end of the page after the gallery.
+See the recent screesnhot attached:12thjune
+
+**Attached**: {F12836}",1402620035,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-db4a2ffve3au67ttwvrv,task_subcomment,NA
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"I think that we fixed this recently, though I can't pin it down.",1402549804,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-db4a2ffve3au67ttwvrv,task_subcomment,NA
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"Created attachment 14528
+Broken UI
+
+**Attached**: {F12835}",1391817253,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-db4a2ffve3au67ttwvrv,task_subcomment,NA
+"VisualEditor: After inserting a gallery, the newly inserted gallery does not remain highlighted but the inspector icon shows up at the corner of the page","Screenshot
+
+steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Gallery 
+3.Insert a gallery
+
+Observed Result:
+The newly inserted gallery is not highlighted but the gallery inspector icon is appearing at the corner of the page which is not consistent with the behavior observed with other link inspectors like Math/Hiero
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12822}",1391814840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zvvrmcmz4eig3vs37trj,task_description,resolved
+"VisualEditor: After inserting a gallery, the newly inserted gallery does not remain highlighted but the inspector icon shows up at the corner of the page","mwGallery is not in the insert menu anymore, but testing locally they do appear to highlight correctly if they are re-enabled.",1402921585,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-zvvrmcmz4eig3vs37trj,task_subcomment,NA
+"VisualEditor: After inserting a gallery, the newly inserted gallery does not remain highlighted but the inspector icon shows up at the corner of the page","Actually, every time when I try to select the newly inserted gallery , it seems its not selecting it as it does not get highlighted like the usual selection behavior, however the gallery inserter icon appears at the far right end.",1392765753,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zvvrmcmz4eig3vs37trj,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,"Steps to reproduce:
+
+1.Open a page with VE which contains an image
+
+2.Open the media settings for the image
+
+3.Go to the advanced settings page
+
+4.Now switch the browser tab or window and then again switch back
+
+
+Observed Result:
+
+The tab in Media Settings got switched to General Settings from Advanced Settings.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391813340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_description,resolved
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,yeah! Not reproducible anymore at my end as well.,1416264866,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,Rummana?,1416182261,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,"I can't reproduce this in Chrome on my local wiki. Rummana, can you still reproduce this issue?",1408842460,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,"As noted in bug 61226, I can't reproduce this in Firefox.  
+
+I can reproduce it at the English Wikipedia, not only at Beta Labs.",1392156155,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,*** Bug 61226 has been marked as a duplicate of this bug. ***,1392144760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Steps to reproduce:
+
+1.Open the page in VE
+2.Insert an image
+3.Go to Media Settings>Advanced Settings
+4.Now delete the first digit of the size.For example:if you have size :600*450
+Just attempt to make it 500*450
+
+Observed Result:
+The Width and the Height both values turned into 0.User have to again type the input of Height value which he might not wanted to change.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1391812020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aaoipsgz7oyqufzeblee,task_description,resolved
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754565,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,Verified the fix in test2 environment.,1394233667,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046692,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Change 115939 had a related patch set uploaded by Mooeypoo:
+[wip] Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1393991576,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"I'm working on trying to get default size to work. There are several technical problems I am trying to sort through now, but once those are solved, we'll be able to have more options with default size, like a 'default' button and reverting to default on 0 value.",1392851126,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"What about making any ""0"" immediately become the wiki's default size?  
+
+Right now, there's no way to remove a size and return to unspecified default (see bug 50379).",1392850649,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"The problem is that the size widget constantly adjusts both values numerically, so value ""00"" in the width is read as the number '0', which actively changes the value in the height input (to 0). 
+
+Now, since a change occurred in height, that triggers an automatic change to width, which brings it down to the number 0.
+
+We can fix this by not triggering the adjustment on keypress but rather when you leave the input (so, onChange event) but that has several other issues it may raise. For instance, what happens if I changed a width without moving away from the input (technically no 'change' input event) and then clicked the ""Apply"" button? The corresponding dimension didn't get updated, and while the 'change' event will trigger when I click the button (because the input loses focus) it will be too late to notify the user of a changed dimension.
+
+I am not sure how this can be fixed without removing the functionality of updating both dimensions simultaneously. We should discuss this further.",1392178859,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"If the size is ""400"" and you delete the first character (4), it becomes ""00"", which instantly becomes ""0"". Undoing this restores the 4… so it becomes ""40"" (and there's nothing left on the browser undo stack).
+
+Maybe if you change the value such that it doesn't make sense, rather than cleaning up ""00"" or ""0"" and then complaining, we should just blank the field?",1392162652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Cannot replicate in master.
+
+Changing the size in either width or height (by deleting or changing the first digit or typing from scratch) changes the corresponding input.
+
+Example:
+
+- Inserted an image with initial size 182x150
+- Media settings -> Advanced settings, deleted '1' to result in width: 82
+- Result: Height adjusted to 68 (Expected)
+- Marked the first digit in Width (8) and changed to 9
+- Result: Height adjusted to 76
+
+This works for me in both Chrome and Firefox.
+
+Am I missing any details to replicate?",1392156609,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Created attachment 14524
+Screenshot
+
+**Attached**: {F12816}",1391812142,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"Intention:
+Add a link to a template using {{tl}} on English Wikipedia.
+
+Steps to Reproduce:
+1.  Add Template:Tl.
+2.  Add any template name, and press return afterwards (so that the parameter field is name+return)
+3.  Apply changes.
+
+Expected Results: No newline is inserted.
+
+Actual Results:  
+The template is broken because the parameter can't support the inclusion of a return.
+",1391799720,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_description,open
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"`modules/ve-mw/ui/pages/ve.ui.MWParameterPage.js` actually has `// TODO: Use spec.type` :) (should be `getParameterType()`, rather).",1423675992,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_subcomment,NA
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"This is now being done for named parameters per T52439, which do not preserve whitespace. However, it must not be done for positional parameters (like in {{tl}}) per T53484, because these do actually preserve whitespace.
+
+Like Krenair says, VE shouldn't use multiline text inputs for single-line parameters, like this one (I just fixed the templatedata on en.wp). Let's rephrase the bug.",1423675689,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_subcomment,NA
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"I wonder if this parameter should be marked with TemplateData type ""line"" and VE should enforce this in the input.",1421887933,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_subcomment,NA
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"If it's not desirable to always strip returns (or spaces) from the end of parameters, then perhaps we should be able to specify in TemplateData how they should be handled.",1391799788,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_subcomment,NA
+VisualEditor:  Pipe trick in templates displays wikitext rather than link,"Intention:
+Add more information to an infobox.
+
+Steps to Reproduce:
+1. Open the infobox.
+
+2. Add a parameter with a link to a disambiguated page name.
+
+3. Use the pipe trick to label the link: [[Wooden spoon (award)|]]
+
+4.  Apply changes.
+
+Actual Results:  
+In VisualEditor, the template displays raw wikitext for that item:   [[Wooden spoon (award)|]] 
+
+Expected Results:  
+That VisualEditor would display the same blue link with the same link label as the page will when it is saved (""Wooden spoon"")
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=594279537&oldid=593922721",1391726580,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wvcdfkoucmmc4frpdguw,task_description,resolved
+VisualEditor:  Pipe trick in templates displays wikitext rather than link,"Change 112829 merged by jenkins-bot:
+Pass 'pst' as true in parse request for fragments
+
+https://gerrit.wikimedia.org/r/112829",1392175345,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvcdfkoucmmc4frpdguw,task_subcomment,NA
+VisualEditor:  Pipe trick in templates displays wikitext rather than link,"Change 112829 had a related patch set uploaded by Jforrester:
+Pass 'pst' as true in parse request for fragments
+
+https://gerrit.wikimedia.org/r/112829",1392167341,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvcdfkoucmmc4frpdguw,task_subcomment,NA
+VisualEditor:  Pipe trick in templates displays wikitext rather than link,This looks like we're passing the wrong flag to action=parse; will try to fix this myself.,1392167168,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wvcdfkoucmmc4frpdguw,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"CTRL/CMD+B for bolding highlighted text
+CTRL/CMD+I for italicising highlighted text
+CTRL/CMD+U for underline highlighted text
+
+CTRL+1,2,3 for H1,H2, H3, etc
+
+CTRL/CMD+K for linking highlighted text
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1391648220,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-bothhqbjosqeckagzghn,task_description,resolved
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I disagree that those are not basic action keyboard shortcuts, especially as they were mentioned in the task description, but nonetheless created {T380087}.",1731695395,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"You can file a separate task for that – those are more controversial as they conflict with browser shortcuts for navigating between tabs on Windows. This ticket is for ""basic formatting and action keyboard shortcut commands"". (Not to mention being harder to implement as the VE behaviour is to use Control key instead of Cmd on Mac.) ",1731675074,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,I still think Ctrl+1/2/3/4/5/6 should’ve been also added. It was also in the task description. I don’t think resolving this task without it is satisfactory enough.,1731672860,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,Suggested blurb: `The 2010 wikitext editor now supports common keyboard shortcuts such Ctrl-B for bold and Ctrl-I for italics.` (?) Full list of shortcuts: [[https://www.mediawiki.org/wiki/Help:Extension:WikiEditor#Keyboard%20shortcuts|mw:Help:Extension:WikiEditor#Keyboard_shortcuts]].,1731648287,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1080802 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/CodeMirror@master] CodeMirror support for WikiEditor keyboard shortcuts%%%
+https://gerrit.wikimedia.org/r/1080802",1730823154,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1079588 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/WikiEditor@master] Retry adding keyboard shortcuts for formatting tools in WikiEditor 2010%%%
+https://gerrit.wikimedia.org/r/1079588",1729708413,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1080802 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/CodeMirror@master] CodeMirror support for WikiEditor keyboard shortcuts%%%
+https://gerrit.wikimedia.org/r/1080802",1729108501,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#10230819, @SD0001 wrote:
+> To turn on syntax highlighting, click the highlighter icon in the toolbar.
+> 
+> {F57617417}
+
+Aah, thanks! That workaround does work well.",1729020018,PHID-USER-b54igy3ozftikuepd4t5,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#10230819, @SD0001 wrote:
+> To turn on syntax highlighting, click the highlighter icon in the toolbar.
+> 
+> {F57617417}
+
+Aah, thanks!",1729020005,PHID-USER-b54igy3ozftikuepd4t5,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"To turn on syntax highlighting, click the highlighter icon in the toolbar.
+
+{F57617417}",1729017459,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,This is quite frustrating for dvorak users ... any timeframe for it being reverted / help pointing out how to turn syntax highlighting on? Surprised this wasn't mentioned in yesterday's Tech News.,1729016245,PHID-USER-b54igy3ozftikuepd4t5,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1079588 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/WikiEditor@master] Retry adding keyboard shortcuts for formatting tools in WikiEditor 2010%%%
+https://gerrit.wikimedia.org/r/1079588",1728724103,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1078960 **abandoned** by SD0001:
+%%%[mediawiki/extensions/WikiEditor@master] shortcuts: Use KeyboardEvent.key instead of KeyboardEvent.code%%%
+Reason:
+%%%KeyboardEvent.key is no good either, will%%%
+https://gerrit.wikimedia.org/r/1078960",1728724023,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Both of those links work fine! The only issue for me is in the normal editor (""action=edit""), when syntax highlighting is off.",1728689571,PHID-USER-2vkn56bsbelr5lsqnrwf,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"@Leijurv @jhsoby as Dvorak keyboard users, can you tell us if this problem is also present in VisualEditor? https://en.wikipedia.org/w/index.php?title=Draft:Sandbox&veaction=edit (visual mode) or https://en.wikipedia.org/w/index.php?title=Draft:Sandbox&veaction=editsource (source mode)
+
+If it is, it might be good to create/use a JS solution to solve a separate issue for all editing environments. There is also a possibility that people with QWERTZ layout (German) might be confused when Ctrl+Z/Ctrl+Y work differently. I’ve found some attempts from people to solve this, though maybe it is already solved in VE: https://stackoverflow.com/questions/70211837/keyboard-shortcuts-commands-on-non-latin-alphabet-keyboards-javascript",1728683487,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#10222826, @SD0001 wrote:
+> Workaround is to turn on syntax highlighting. The shortcuts don't work with CodeMirror enabled.
+That seems like another issue to fix if this gets re-added, btw. https://ru.wikipedia.org/wiki/Участник:Stjn/wikiEditorShortcuts.js#L-132 shows how.",1728682757,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Thanks, that works!",1728682698,PHID-USER-2vkn56bsbelr5lsqnrwf,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,Workaround is to turn on syntax highlighting. The shortcuts don't work with CodeMirror enabled.,1728682480,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Noting that I am now unable to copy/paste in the editor since I use Dvorak. It looks like this will be reverted by next Thursday, but any workaround in the meantime?
+
+
+{F57606954}",1728682028,PHID-USER-2vkn56bsbelr5lsqnrwf,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1078939 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/WikiEditor@master] Revert ""Keyboard shortcuts for formatting tools in WikiEditor 2010""%%%
+https://gerrit.wikimedia.org/r/1078939",1728581579,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Sure, done.",1728576037,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Restating [[ https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikiEditor/+/1078939/comment/d51e1dc6_57d42d3f/ | my comment ]] on the gerrit changeset, I'd suggest that we revert first and try again after. Is that okay @SD0001?",1728570239,PHID-USER-hu7nuhczm4gmfufd4qmg,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Only like this:
+```
+$( '#wpTextbox1' ).on( 'keydown', ( e ) => {
+	console.log( e.key );
+} );
+```
+{F57601389}",1728492687,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#10214676, @stjn wrote:
+> AFAIK he new provided patch and the suggestion would make it impossible to use this feature for people on non-Latin keyboards (since `e.key` for `K` doesn’t match to `K` or `k` on a Russian keyboard, it would match to `Л` or `л`), therefore reducing the usability of this tremendously. I understand the concern with Dvorak keyboards, but maybe there are better ways to resolve this than this.
+
+Did you test this? My understanding is that when Cmd/Ctrl modifiers are held pressed, `e.key` will be `k` even on a non-Latin keyboard. Caps lock also doesn't make a difference with Cmd/Ctrl pressed, `e.key` is always in lowercase.",1728492460,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"AFAIK he new provided patch and the suggestion would make it impossible to use this feature for people on non-Latin keyboards (since `e.key` for `K` doesn’t match to `K` or `k` on a Russian keyboard, it would match to `Л` or `л`), therefore reducing the usability of this tremendously. I understand the concern with Dvorak keyboards, but maybe there are better ways to resolve this than this.",1728486467,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1078960 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/WikiEditor@master] shortcuts: Use KeyboardEvent.key instead of KeyboardEvent.code%%%
+https://gerrit.wikimedia.org/r/1078960",1728484462,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Submitted the revert above because the patch basically makes it impossible for me to copy/paste things, since it hijacks Ctrl+C and Ctrl+V on dvorak keyboards (and possibly other layouts too?). The revert commit message has suggestions for how to fix this.",1728481422,PHID-USER-jqjb54lbf7psat6shbcc,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1078939 had a related patch set uploaded (by Jon Harald Søby; author: Jon Harald Søby):
+%%%[mediawiki/extensions/WikiEditor@master] Revert ""Keyboard shortcuts for formatting tools in WikiEditor 2010""%%%
+https://gerrit.wikimedia.org/r/1078939",1728480582,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"@SD0001 also, just as a note, is Ctrl+1/2/3/4/5 not being a thing intentional? Those are available in the visual editor and seem very useful to have.",1728337911,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"The currently merged patch is a step in the good direction, but it doesn’t contain any indication for editors that they can press certain shortcuts to press the buttons. Would be good to add that.",1728042761,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1077335 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/WikiEditor@master] Keyboard shortcuts for formatting tools in WikiEditor 2010%%%
+https://gerrit.wikimedia.org/r/1077335",1728042228,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1077335 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/WikiEditor@master] Keyboard shortcuts for formatting tools in WikiEditor 2010%%%
+https://gerrit.wikimedia.org/r/1077335",1727863734,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#4779443, @TheDJ wrote:
+> I think it is very unlikely this will ever be added to #wikieditor, now that we have #visualeditor-mediawiki-2017wikitexteditor providing this functionality.
+
+As time has shown, the majority of users didn't migrate to that.",1711379875,PHID-USER-p6gpvwnc6ske65oxuoof,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I'm about to implement the shortcuts in #convenient-discussions as this is requested by users and I would rather not implement this apart from WikiEditor which Convenient Discussions employs. But if there is no activity in this task, I will have to.",1711379545,PHID-USER-p6gpvwnc6ske65oxuoof,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I'm about to implement the shortcuts in #convenient-discussions as this is requested by users and I would rather not implement this apart from WikiEditor. But if there is no activity in this task, I will have to.",1711379514,PHID-USER-p6gpvwnc6ske65oxuoof,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"In the meantime, https://ru.wikipedia.org/wiki/Участник:Stjn/wikiEditorShortcuts.js provides similar functionality. But I do think that all modes of editing need to have the same keyboard shortcuts (at least where that makes sense) for a better user experience.",1624989209,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I think it is very unlikely this will ever be added to #wikieditor, now that we have #visualeditor-mediawiki-2017wikitexteditor providing this functionality.",1543356971,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I'm not sure which of these is most uptodate, but... here are some known knowns.
+
+* https://www.mediawiki.org/wiki/Manual:Interface/Access_keys
+* https://meta.wikimedia.org/wiki/Help:Keyboard_shortcuts
+* https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+* https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts",1728063933,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I'm not sure which of these is most uptodate, but... here are some known knowns.
+
+    https://www.mediawiki.org/wiki/Manual:Interface/Access_keys
+
+    https://meta.wikimedia.org/wiki/Help:Keyboard_shortcuts
+
+    https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+
+    https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts",1403684232,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Moving to WikiEditor; we're probably going to kill the difference between the two, but for now…",1403657041,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page","Screenshot
+
+Steps to reproduce:
+
+1.Open the page with VE
+2.Add a text with reference
+3.Add an image
+4.Go to Media Settings for the image
+5.Go to Insert>Reference
+
+Observed Result:
+Observe that, the ""Use an existing reference "" button remains disabled even if there is a reference added in the page
+
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Wmf12chrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13113}",1391638020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qkmndwu7hujefvxd4fpz,task_description,open
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page",">>! In T62919#3709391, @Deskana wrote:
+> This specific problem doesn't happen any more, although there is some really weird UI stuff going on...
+> 
+> {F10426560}
+
+Actually this issue is still happening. It was about ""Use an existing reference"" button  inside Media Settings>Cite> Basic reference dialog remaining disabled. 
+
+Updated screenshots:
+
+{F10521929}
+",1509395078,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page",">>! In T62919#3709391, @Deskana wrote:
+> This specific problem doesn't happen any more, although there is some really weird UI stuff going on...
+
+For posterity, the weird UI stuff is filed as {T178986}.
+
+",1508929740,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page","This specific problem doesn't happen any more, although there is some really weird UI stuff going on...
+
+{F10426560}",1508929246,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page","This is blocked by bug 47344, the infamous sub-documents bug.",1415054491,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page","(In reply to Ed Sanders from comment #1)
+> Looks like we aren't copying over the internalList object from the parent dm
+> document.
+
+Does that explain bug 58322 or bug 71214?",1414883288,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page",Looks like we aren't copying over the internalList object from the parent dm document.,1391644762,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+Enable VisualEditor in the Projekt namespace on se.wikimedia.org,"Please enable VisualEditor also in the ""Projekt"" namespace on the wmse chapters wiki.
+
+Please note that this is not the same as the NS_PROJECT/Wikimedia
+namespace.
+
+Poll/request at: https://se.wikimedia.org/wiki/Tr%C3%A5d:Wikimedia:Bybrunnen/VisualEditor_p%C3%A5_Projekt:-sidorna
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1391599320,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-pkc5qf2xz72ywhnd6t26,task_description,resolved
+Enable VisualEditor in the Projekt namespace on se.wikimedia.org,Merged & deployed by Reedy (thank you!).,1392330904,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-pkc5qf2xz72ywhnd6t26,task_subcomment,NA
+Enable VisualEditor in the Projekt namespace on se.wikimedia.org,"Change 113141 merged by jenkins-bot:
+Enable VisualEditor for Projekt: NS on sewikimedia
+
+https://gerrit.wikimedia.org/r/113141",1392327485,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pkc5qf2xz72ywhnd6t26,task_subcomment,NA
+Enable VisualEditor in the Projekt namespace on se.wikimedia.org,"Change 113141 had a related patch set uploaded by Odder:
+Enable VisualEditor for Projekt: NS on sewikimedia
+
+https://gerrit.wikimedia.org/r/113141",1392311448,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pkc5qf2xz72ywhnd6t26,task_subcomment,NA
+Create an API module to allow apps to set global preference,"Discussion: {T196314}
+
+Deliverables:
+* API module to allow apps to set global value for a preference.
+
+See also:
+* {T197259}
+* {T197260}
+",1391567760,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-52g62pbs7jogl5cwjmrs,task_description,resolved
+Create an API module to allow apps to set global preference,"Change 442219 **merged** by jenkins-bot:
+[mediawiki/extensions/GlobalPreferences@master] Add an API module to set global preferences
+
+[[https://gerrit.wikimedia.org/r/442219]]",1530849525,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"Change 442218 **merged** by jenkins-bot:
+[mediawiki/core@master] Refactor ApiOptions for reusability
+
+[[https://gerrit.wikimedia.org/r/442218]]",1530080174,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"Change 442219 had a related patch set uploaded (by MaxSem; owner: MaxSem):
+[mediawiki/extensions/GlobalPreferences@master] Add an API module to set global preferences
+
+[[https://gerrit.wikimedia.org/r/442219]]",1530053782,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"Change 442218 had a related patch set uploaded (by MaxSem; owner: MaxSem):
+[mediawiki/core@master] Refactor ApiOptions for reusability
+
+[[https://gerrit.wikimedia.org/r/442218]]",1530053670,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,I think the biggest use case for this is to support setting the edit tabs preference across all wikis at once from the VisualEditor popup.,1519666006,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"OK, thank you Sam. We'll keep it on the GlobalPrefs backlog for now.",1519665689,PHID-USER-5s7hp7zjreoi3dmulai3,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"It probably wouldn't be too hard to add, but without a use case in mind I think it can be postponed.
+",1519434599,PHID-USER-hlhhe6qw6qfkl7wyfhxk,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,@Samwilson  Do we need to do anything with this task? Herald says hi.,1519430411,PHID-USER-5s7hp7zjreoi3dmulai3,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"**Author:** `jhall`
+
+**Description:**
+While developing a browser test for bug 60797, I've noticed that some production wikis where VisualEditor is expected to be available do not load VE as expected.  In each case, the error message captured at the browser level is (with some variation in the specific line numbers referenced):
+
+
+[Error] Error: JavaScript parse error: Parse error: Missing operand in file 'MediaWiki:Common.js' on line 125
+	global code (load.php, line 1)
+
+
+
+Repro steps:
+
+1) Visit a production wiki where VE is expected to be available, and request a random article with a VE edit param: http://cv.wikipedia.org/wiki/Special:Random?veaction=edit
+
+2) In browser error console, note JavaScript error mentioned above, and note also that the VE editing surface simply never loads (although it appears to keep trying!)
+
+
+I'll add list(s) of production wikis where this problem occurs as I uncover them in comments on this bug ticket.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60797",1391544360,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_description,resolved
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"Change 127373 merged by jenkins-bot:
+[Browser tests] Updated list of production wikis to check
+
+https://gerrit.wikimedia.org/r/127373",1397858649,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"Change 127373 had a related patch set uploaded by Jforrester:
+[Browser tests] Updated list of production wikis to check
+
+https://gerrit.wikimedia.org/r/127373",1397857736,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"Updated current list of failures:
+
+http://bpy.wikipedia.org
+http://cv.wikipedia.org
+http://mzn.wikipedia.org
+http://new.wikipedia.org
+
+I have fixed:
+
+> http://af.wikipedia.org
+> http://am.wikipedia.org
+> http://kaa.wikipedia.org
+> http://ln.wikipedia.org
+> http://szl.wikipedia.org",1394501677,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"**jhall** wrote:
+
+Found one more, so here's a consolidated list of ""broken"" wikis identified so far:
+
+http://af.wikipedia.org
+http://am.wikipedia.org
+http://bpy.wikipedia.org
+http://cv.wikipedia.org
+http://kaa.wikipedia.org
+http://ln.wikipedia.org
+http://mzn.wikipedia.org
+http://new.wikipedia.org
+http://szl.wikipedia.org",1391554304,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"**jhall** wrote:
+
+Some more wikis with the same problem:
+
+http://kaa.wikipedia.org
+http://ln.wikipedia.org
+http://mzn.wikipedia.org
+http://new.wikipedia.org
+http://szl.wikipedia.org",1391548251,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"**jhall** wrote:
+
+Wikis where this problem has been seen:
+
+http://af.wikipedia.org
+http://bpy.wikipedia.org
+http://cv.wikipedia.org",1391544768,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+"Native Mac OS special character inserter fails to get content into DM, just CE, in Safari","Intention:
+Add a special character from the built-in Mac OS character inserter.
+
+Steps to Reproduce:
+1. Using Safari, open a page in VisualEditor.
+
+2. In Safari's menu bar, choose Edit > Special Characters...
+
+3. Double-click on special characters to add them.
+
+Actual Results:  
+The special characters display on the screen, but are not present when you try to save the text.  Characters that were typed from the keyboard are saved.  No characters (even if they are 'normal' ones) are saved if they were added with the character inserter.
+
+
+Reproducible: Always
+
+It works in Firefox 26.  It does not work in Safari 6.  I haven't tested Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391541420,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5dustpsver5abqahxsbc,task_description,resolved
+"Native Mac OS special character inserter fails to get content into DM, just CE, in Safari","This is now working, presumably through the same fix that fixed {T61748}.",1428511594,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5dustpsver5abqahxsbc,task_subcomment,NA
+"Native Mac OS special character inserter fails to get content into DM, just CE, in Safari",Confirmed in Safari 8.0 in VE master as of now; almost certainly the same issue as {T61748} and {T63884}.,1417578194,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5dustpsver5abqahxsbc,task_subcomment,NA
+"Native Mac OS special character inserter fails to get content into DM, just CE, in Safari","Created attachment 14484
+The red oval on the far left shows the three characters (one normal 'r' and two fancier ones) added with the OS's special character inserter.  These should appear in the Review Changes diff, but don't
+
+**Attached**: {F12931}",1391541678,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5dustpsver5abqahxsbc,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image in the page
+3.Open the Media Settings for that image
+4.Insert another image inside it.
+5.Apply Changes
+6.Save the page
+7.Reopen the page again
+8.Open the media settings again for the image on the page
+
+
+Observed Result:
+VE stops reposnding.Cannot cross out the dialog box.""Apply Changes"" does not close the dialog box.
+An error appears in the console
+Error: Offset could not be translated to a DOM element and offset: 22
+	
+
+(297 out of range 182)
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/3rdfebFF?veaction=edit
+
+See the screenshot attached,
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12818}",1391467620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o64myfteta7sv33kwhio,task_description,resolved
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1391734538,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111695 merged by jenkins-bot:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111695",1391731445,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,Verified the fix in Betalabs,1391712726,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111695 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111695",1391650882,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111694 abandoned by Catrope:
+Make globalOverlay really global
+
+Reason:
+Wrong branch
+
+https://gerrit.wikimedia.org/r/111694",1391650784,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111694 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111694",1391650754,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111690 merged by jenkins-bot:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111690",1391649998,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111690 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111690",1391649620,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"This error also appears when you delete the reflist that contains a reference which has image inside:
+
+Error: Offset could not be translated to a DOM element and offset: 31
+	
+
+(297 out of range 182)",1391473010,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image and a reference
+3.Open the Media Settings for the image and include another image
+4.Click on the Media Settings icon on the second image that you just inserted
+OR
+5.Open the reference dialog box
+6.Add an image inside
+7.Click on the Media Settings icon on the image you just inserted
+
+Observed Result:
+In both cases after step 4 and step 7, Media Settings dialog box does not open up
+In the console following error appears:
+NS_ERROR_NOT_AVAILABLE:
+	
+
+...w Date()).getTime();}});jQuery.ready.promise=function(obj){if(!readyList){readyL...
+
+load.p...034436Z (line 11)
+
+See the screenshot attached
+
+**This is happening in FireFox only** 
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13424}",1391465040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_description,resolved
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1391734427,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111695 merged by jenkins-bot:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111695",1391731448,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,Verified the fix in Betalabs,1391712647,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111695 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111695",1391650886,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111694 abandoned by Catrope:
+Make globalOverlay really global
+
+Reason:
+Wrong branch
+
+https://gerrit.wikimedia.org/r/111694",1391650781,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111694 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111694",1391650758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111690 merged by jenkins-bot:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111690",1391650000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111690 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111690",1391649625,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,"screenshot of empty gallery in edit mode
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Gallery
+3.Just close the inspector
+
+Observed Result:
+An empty gallery inspector is getting added in the page
+
+
+See the screenshot attached.
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:
+https://test2.wikipedia.org/w/index.php?title=31st_january&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13379}",1391456820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_description,resolved
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,Verified the fix on test2,1392254285,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,Verified the fix in Betalabs,1391720180,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,*** Bug 60914 has been marked as a duplicate of this bug. ***,1391668703,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,Fixed in gerrit 111178.,1391660307,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,"Created attachment 14456
+Screenshot in edit source mode
+
+**Attached**: {F13380}",1391456863,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Firefox also supports CSS3 animations and transitions, see how it can be done: http://tympanus.net/Development/ModalWindowEffects/
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1391263200,PHID-USER-b27lopawgf2h6utuuqyi,PHID-TASK-sa4ylwldmmhrky72otw3,task_description,declined
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Now everything has the same appearance like in Chrome, so well done!",1394980634,PHID-USER-b27lopawgf2h6utuuqyi,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"(In reply to Andre Klapper from comment #4)
+> Hello! Nobody yet, obviously. 
+> If this functionality is important to you, providing patches speeds up
+> getting this implemented. See https://www.mediawiki.org/wiki/Developer_access
+
+Thanks Andre!",1393064445,PHID-USER-b27lopawgf2h6utuuqyi,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Hello! Nobody yet, obviously. 
+If this functionality is important to you, providing patches speeds up getting this implemented. See https://www.mediawiki.org/wiki/Developer_access",1393010006,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Hello? Nobody?
+Dialog animations have been already implemented(!) and work in Chrome, only!
+Could someone create some CSS love for Firefox as well?",1393005931,PHID-USER-b27lopawgf2h6utuuqyi,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"(In reply to comment #1)
+> Why should VE ""support"" this? I am missing a usecase / user story here so
+> far.
+
+This animation is supported in Google Chrome/Chromium, just open this dialog in this browser and see. Same effect can be done in Firefox as well. VE has this animation already implemented!",1391428321,PHID-USER-b27lopawgf2h6utuuqyi,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Why should VE ""support"" this? I am missing a usecase / user story here so far.",1391345406,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown","For wikis with FlaggedRevs extension: After saving a page the notice on top of page ""1 change in this version is pending review ..."" is not shown.
+
+I guess due to not reloading the whole page.
+
+This is a bad experience for every editor w/o reviewer right. No chance to spot that the new revision has to be sighted first.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391255160,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-6zaw3in4igorb3k4bavq,task_description,resolved
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown","Change 172746 merged by jenkins-bot:
+When saving, return the full contentSub to the client
+
+https://gerrit.wikimedia.org/r/172746",1415911512,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown",(It's slightly less horrible now. But only slightly.),1415805215,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown","Change 172746 had a related patch set uploaded by Alex Monk:
+When saving, return the full contentSub to the client
+
+https://gerrit.wikimedia.org/r/172746",1415805160,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown",I came up with some terrible code that successfully achieves this yesterday.,1415459670,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown",I took a look into this today... Seems that the review notice is not being made available even as part of the page subtitle to VE.,1415326465,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","Screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add any image 
+3.Go to Media Settings>Advanced Settings
+4.Say for example the original dimension of the image is  150x150
+5.Change the values in such way that it exceeds the original size for example: 300x300
+
+Observed Result:
+Apply Changes button remains active even though ""Size values are invalid "" appears in the dialog box.
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Sample Page:http://en.wikipedia.beta.wmflabs.org/wiki/29th_January?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12971}",1391035980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mtoupxdcw637uabefm23,task_description,resolved
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","This has been fixed in {20c4fbbc1e1ffa61a8716ead01d5efebffa11931}. Invalid dimensions now cause the ""Apply changes"" button to be disabled.
+
+{F26724268}",1540269111,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","I think this can be best ""fixed"" by altering the design and copy so that it's clear that invalid changes won't be put into effect.",1391661046,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","The problem in my opinion with #2 is that if a user spent time working on new settings (caption / alternate text / position etc) we force them to deal with size before applying the rest. In general I think that might be less convenient in the long run.
+
+I think the better approach (giving the user more leeway) is to alert the user that the parameter is wrong and won't be applied, save everything else, and allow the user to go back in and deal with the size widget specifically if they want to (or decide they don't want to deal with numerical values and resize with the mouse)
+
+I think that while it's less like ""others"" are doing, this might give the user more leeway when fixing and working on stuff. Instead of forcing the user to deal with a problem they might just want to undo, we let the user save everything else and choose if they want to go back to retrying the size specifically.",1391106128,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","> I am leaning towards #1, but we should discuss and see if we want to apply
+> #2.
+Wont #2 be more obvious ?",1391105362,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","This is actually intended behavior, but one that's not clearly explained; if the size parameters are invalid, the media edit dialog will apply all other changes except for size (so to allow other changes like image type, alternate text, etc)
+
+There are two ways to solve this bug imho:
+
+1. Adjust the message to ""Size values are invalid and will not be applied.""
+
+2. Make the 'apply' button inactive if size is invalid, forcing the user to find valid parameters or cancel -- but this will also mean that if other changes were made in the dialog, and the user doesn't know or want to change the size after seeing it is invalid (or wants to revert to the previous dimensions) we force them to cancel *all* changes and redo them again.
+
+I am leaning towards #1, but we should discuss and see if we want to apply #2.",1391104335,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+VisualEditor: Removing or breaking HTML tags (</small> and </code> tags vanish),"Ex. #1, https://fr.wikipedia.org/w/index.php?title=%C3%89conomie_de_la_France&diff=100357906&oldid=100354236 , the </small> tag vanishes (the user said he fixed the spaces and removed a link);
+ex. #2, https://fr.wikipedia.org/w/index.php?title=Utilisateur:NemesisIII/Brouillon&diff=100052444&oldid=99902909 , the </code> tag misses the less-than sign (the user had just added a link);
+ex. #3, https://fr.wikipedia.org/w/index.php?title=Utilisateur:NemesisIII/Brouillon&diff=99902829&oldid=99228289 the same thing happens (the user just deleted a template).
+Some curly brackets went missing as well.",1391013480,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fl6ckzrwls3bv7wziv27,task_description,resolved
+VisualEditor: Removing or breaking HTML tags (</small> and </code> tags vanish),I think this has been long-since fixed.,1437586955,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fl6ckzrwls3bv7wziv27,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"**Author:** `jhall`
+
+**Description:**
+Follow-up to a pairing session between Jeff and Željko on 1/29/2013.  In order to make headless browser testing available in as many WMF repositories as possible, we should add headless support[1] to the env.rb and hooks.rb setup in the mediawiki-selenium Rubygem[2].
+
+
+[1] http://watirwebdriver.com/headless/
+[2] https://git.wikimedia.org/tree/mediawiki%2Fselenium/ef67a1f40db97a7e0b456fcc3fbf20c6a8ec4e81/lib%2Fmediawiki%2Fselenium
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1391012400,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atlm4jbmrywbsofx5zts,task_description,resolved
+Add support for running headless browser tests to mediawiki-selenium Rubygem,But then he introduced the same thing in https://gerrit.wikimedia.org/r/#/c/110606 :),1391439349,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,Zeljko are you sure it is fixed ? Jeff reverted https://gerrit.wikimedia.org/r/110390,1391438764,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110390 merged by jenkins-bot:
+Make it possible to run VisualEditor tests in headless mode
+
+https://gerrit.wikimedia.org/r/110390",1391106871,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110390 had a related patch set uploaded by Zfilipin:
+Make it possible to run VisualEditor tests in headless mode
+
+https://gerrit.wikimedia.org/r/110390",1391099566,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110205 merged by jenkins-bot:
+Run browsers headlessly if HEADLESS environment variable is set to true
+
+https://gerrit.wikimedia.org/r/110205",1391094013,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"at one point CirrusSearch had this hook.  It's in the README, but I don't see the hook itself any more.",1391092901,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"I still have to test this with repositories that have at_exit hook. Looks like only VisualEditor has the hook, and it should probably be moved to the gem.",1391078414,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110335 abandoned by Zfilipin:
+WIP run browsers headlessly if HEADLESS environment variable is set to true
+
+https://gerrit.wikimedia.org/r/110335",1391076449,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110335 had a related patch set uploaded by Zfilipin:
+WIP run browsers headlessly if HEADLESS environment variable is set to true
+
+https://gerrit.wikimedia.org/r/110335",1391074845,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"We had some browser tests running on integration-selenium-driver.pmtpa.wmflabs which is an Ubuntu Precise instance. xvfb package is 2:1.11.4-0ubuntu10.14 
+
+There is apparently no package for ruby gems headless but it is going to be a dependency of mediawiki-selenium apparently ( https://gerrit.wikimedia.org/r/#/c/110205/3/mediawiki-selenium.gemspec,unified )",1391072803,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110205 had a related patch set uploaded by Zfilipin:
+WIP run browsers headlessly if HEADLESS environment variable is set to true
+
+https://gerrit.wikimedia.org/r/110205",1391026423,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"**jhall** wrote:
+
+Should note that in order to run headless browser tests, the test environment(s) needs to have two additional components installed:
+
+a) Headless Rubygem[1]
+b) Xvfb binary for your OS[2]
+
+[1] http://rubygems.org/gems/headless
+[2] http://en.wikipedia.org/wiki/Xvfb",1391012831,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,"Steps to reproduce:
+
+1.Open a page with VE
+2.Select a reference note or a text and open the gallery inspector or a Link inspector
+3.Close the inspector and go to the next line
+4.Again go to Insert>Gallery or Open the link inspector
+
+Observed Result:
+The inspector opens up with an animation from left to right
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66552",1390861440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cgjlomsf2qva26bhkh5o,task_description,resolved
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,Fixed in gerrit 139550.,1405375924,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,"This also happens when working with a list of links.
+
+1. Have a page with a list containing a list item with a link.
+2. Put cursor at end of list item (thus triggering the context menu).
+3. Press return (creating a new list item)
+4. Insert link.
+
+The link inspector animates in an odd way from the left of the screen.
+
+Can also be seen at the beginning of this (otherwise unrelated) recording for another bug. http://cl.ly/3s460Q442L3S",1403712295,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,This is still happening,1402690833,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,This looks like it's now fixed.,1402553325,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF
+OS: MAC OS X 10. 8. 5",1390861673,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Diff styling in save dialog is broken,"Screenshot of the bug
+
+The diff in the save dialog isn't being styled correctly, which causes highlighted text to overlap with text above it. Timo tells me that this is due to a missing line-height style.
+
+This is exacerbated by bug 60494. which causes the save dialog to be narrower than it should be, which means lines wrap more often and highlighted text more frequently has text directly above it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13394}",1390859040,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tgchpzb2re5dhfc6dype,task_description,resolved
+VisualEditor: Diff styling in save dialog is broken,*** Bug 57300 has been marked as a duplicate of this bug. ***,1414810803,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tgchpzb2re5dhfc6dype,task_subcomment,NA
+VisualEditor: Diff styling in save dialog is broken,"This has been fixed, AFAICT.",1404168811,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tgchpzb2re5dhfc6dype,task_subcomment,NA
+VisualEditor: Diff styling in save dialog is broken,"So I think we just need to apply line-height: 1.6px to the body of the frame like MW core does for #bodyContent, .mw-body-content (but I don't think we should use those here as they apply some other changes which don't look right e.g. font-size: 0.875em)",1400029729,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tgchpzb2re5dhfc6dype,task_subcomment,NA
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.","When adding a special character via the new tool,
+this will not retain styles applied to what was being typed; that is,
+it will not appear for example in bold or italics.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1390841520,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nlvlcsu6onawdloowc5x,task_description,resolved
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.","Change 157703 merged by jenkins-bot:
+Annotate inserted special characters
+
+https://gerrit.wikimedia.org/r/157703",1409596262,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nlvlcsu6onawdloowc5x,task_subcomment,NA
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.","Change 157703 had a related patch set uploaded by Jforrester:
+Annotate inserted special characters
+
+https://gerrit.wikimedia.org/r/157703",1409596100,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nlvlcsu6onawdloowc5x,task_subcomment,NA
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.",*** Bug 70265 has been marked as a duplicate of this bug. ***,1409596086,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nlvlcsu6onawdloowc5x,task_subcomment,NA
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.",*** Bug 65497 has been marked as a duplicate of this bug. ***,1400546427,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nlvlcsu6onawdloowc5x,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","Screenshot attached
+
+Steps to reproduce:
+
+
+1.Open a page with VE 
+2.Go to Insert>Transclusion
+3.Search for the template Cite Web
+4.Observe that the required parameters are now marked with * symbol
+5.Delete the required parameters
+
+Observed Result:
+
+The required parameters gets deleted
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50747
+
+**Attached**: {F13028}",1390435920,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wicgwgtwpynij2ce4n4w,task_description,resolved
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData",Verified the fix in production,1409864356,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData",This kind of relationship between parameters was requested on bug 50407.,1409777327,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","(In reply to Helder from comment #8)
+> (In reply to James Forrester from comment #6)
+> > (In reply to Ricordisamoa from comment #5)
+> > > or a set of fields may be mutually exclusive (and yet one of them would
+> > > be required).
+> > 
+> > That doesn't make sense. ""Required"" means ""the template will die horribly if
+> > you don't include this"". It is *not* a ""we'd like you to fill this in"" –
+> > that's what ""suggested"" is for. Most templates will have no 'required'
+> > fields.
+> 
+> It seems perfectly valid for a template to require that ""either A or B be
+> provided"" and the user should be able to delete one of them if it is not
+> needed.
+
+This feels like a pretty edge case (and suggests that we should consider whether the template should be re-written to be less anti-human); maybe file a TemplateData bug to ask for a way to express this relationship?",1409771964,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","(In reply to Ricordisamoa from comment #5)
+> ...a set of fields
+> may be mutually exclusive (and yet one of them would be required).
+
+(In reply to James Forrester from comment #6)
+> > or a set of fields may be mutually exclusive (and yet one of them would
+> > be required).
+> 
+> That doesn't make sense. ""Required"" means ""the template will die horribly if
+> you don't include this"". It is *not* a ""we'd like you to fill this in"" –
+> that's what ""suggested"" is for. Most templates will have no 'required'
+> fields.
+
+It seems perfectly valid for a template to require that ""either A or B be provided"" and the user should be able to delete one of them if it is not needed.",1409711953,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","(In reply to James Forrester from comment #6)
+> The wikitext editor lets you do lots of things that are stupid.
+
+I do 'stupid' things all the time.
+Now I understand that VE will always be a toy for newbies, and never a valid replacement for the wikitext editor.",1409701206,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","(In reply to Ricordisamoa from comment #5)
+> VisualEditor should only make edits easier,
+
+I agree.
+
+> not restrict the users' capabilities.
+
+I think this is a false dichotomy.
+
+> As long as the wikitext editor allows removing required fields from
+> templates (and it should, indeed), VE should too.
+
+The wikitext editor lets you do lots of things that are stupid. VisualEditor's job is to make it easy to make good content, not easy to make broken pages. :-)
+
+> Sometimes the TemplateData information may be incorrect, 
+
+Then the TemplateData should be fixed.
+
+> or a set of fields may be mutually exclusive (and yet one of them would
+> be required).
+
+That doesn't make sense. ""Required"" means ""the template will die horribly if you don't include this"". It is *not* a ""we'd like you to fill this in"" – that's what ""suggested"" is for. Most templates will have no 'required' fields.
+
+> Sometimes a user may want to remove a wrong value, and a template may
+> show a warning for missing arguments (always better than wrong data).
+
+If the template outputs an error, that's probably a required parameter.
+
+> Instead, a warning should be shown when a required parameter is going to be
+> removed.
+
+I disagree, for the reasons above.",1409696656,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","VisualEditor should only make edits easier, not restrict the users' capabilities.
+As long as the wikitext editor allows removing required fields from templates (and it should, indeed), VE should too.
+Sometimes the TemplateData information may be incorrect, or a set of fields may be mutually exclusive (and yet one of them would be required). Sometimes a user may want to remove a wrong value, and a template may show a warning for missing arguments (always better than wrong data).
+Instead, a warning should be shown when a required parameter is going to be removed.",1409616727,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData",Verified the fix in test2,1409260648,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData",Verified the fix in Betalabs,1409166948,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","Change 154133 merged by jenkins-bot:
+Remove delete button from required parameters in template dialog
+
+https://gerrit.wikimedia.org/r/154133",1409133882,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","Change 154133 had a related patch set uploaded by Alex Monk:
+Don't add delete button to required parameters in template dialog
+
+https://gerrit.wikimedia.org/r/154133",1408048592,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"**Author:** `jhall`
+
+**Description:**
+The time has come to create additional VisualEditor browser tests for accessing VE via the Mobile interface.
+
+James F had great feedback on which repo (MobilefrontEnd vs. VisualEditor) these tests belong in:
+
+""​One way of looking at it is on the blocking model. If (when!) these tests were to block merge, which repo's changes should they be triggered by? In this case, I think there's a case for some basic browser tests for VE-on-Mobile to be in VisualEditor (specifically, in the MediaWiki VisualEditor repo) with the major tests be in MobileFrontend.""
+
+An example URL for accessing VE via Mobile UI is: [1]
+
+
+[1] http://en.m.wikipedia.beta.wmflabs.org/wiki/0.04730373828804457?mobileaction=alpha#editor/0
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1390322220,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_description,open
+VisualEditor: Create browser tests for using VE via Mobile UI,In the Triage meeting we felt that this wasn't a clear enough ask for Q4.,1428521913,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"So.. MobileFrontend has some basic ones [1]. I wonder if we should have a dedicated extension for MobileFrontendVETests that depends on MobileFrontend and VisualEditor? It seems silly having two (might even be worth breaking out MobileFrontendVE into its own extension?)
+
+[1] e.g. https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/440/testReport/(root)/VisualEditor%20Mobile/I_can_edit_a_page_using_VisualEditor/",1420843913,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,">>! In T62290#967236, @Cmcmahon wrote:
+> I'll take this on. Having refactored both MF and VE at the end of 2014, both repos are in good shape to support new feature coverage.
+
+Awesome. :-)",1420843497,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"I'll take this on. Having refactored both MF and VE at the end of 2014, both repos are in good shape to support new feature coverage.",1420843401,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"Change 108987 abandoned by Jforrester:
+[Browser test] WIP New test(s) for editing with VisualEditor via mobile user interface.
+
+Reason:
+Not currently being worked on AFAICT.
+
+https://gerrit.wikimedia.org/r/108987",1396279296,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"**jhall** wrote:
+
+Setting status back to ASSIGNED since Gerrit is a little over-eager to mark even WIP patch sets as being ready for review!",1390429368,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"Change 108987 had a related patch set uploaded by Jhall:
+[Browser test] WIP New test(s) for editing with VisualEditor via mobile user interface.
+
+https://gerrit.wikimedia.org/r/108987",1390429176,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Daniel on Mediawiki.org says they use strikethrough a lot and would like a shortcut for it.
+",1390231620,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_description,resolved
+VisualEditor: Add a shortcut for strikethrough (?which?),"Re-confirmed in production. It's availabe in the formatting menu, and the indicated shortcut works as expected (Note: on macOS, you may have to use fn+shift+cmd+5 instead of shift+cmd+5 given the latter is by default used by the system's screengrab utility).
+{F31513593}",1579113752,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),I'm not currently working on this.,1579112937,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Google Docs uses Cmd+Shift+X on OSX (as opposed to +5): https://support.google.com/docs/answer/179738?co=GENIE.Platform%3DDesktop&hl=en
+
+~~Happy to switch to this...~~
+
+Unfortunately VE uses Cmd+Shift+X for ""Change directionality""...",1556472660,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Google Docs uses Cmd+Shift+X on OSX (as opposed to +5): https://support.google.com/docs/answer/179738?co=GENIE.Platform%3DDesktop&hl=en
+
+Happy to switch to this...",1556472553,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"@Jdforrester-WMF Since macOS Mojave, Shift-Command-5 is now used for an additional screenshot option, which conflicts with strikethrough. Is it possible to reconfigure? https://support.apple.com/en-us/HT201236",1543241693,PHID-USER-ep6ujeg6mjkhz4d7yx25,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),Verified the fix in production,1411681786,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),Verified the fix in Betalabs and test2,1411150108,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),Re-fixed.,1411088342,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"We need to change the shortcut key for code annotation on mac from ""cmd+shift+3"".Because,its a shortcut to take screenshot so it does not work there.",1411064760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Change 160174 merged by jenkins-bot:
+Add keyboard shortcuts for strikethrough and code annotations
+
+https://gerrit.wikimedia.org/r/160174",1410823315,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Change 160174 had a related patch set uploaded by Jforrester:
+Add keyboard shortcuts for strikethrough and code annotations
+
+https://gerrit.wikimedia.org/r/160174",1410570238,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"I added your comment to Mediawiki.org. 
+I think I noticed that the numbers 8 and 9 are still available?
+Or at least this is what I read in the new keyboard shortcuts list.
+(Which, BTW, is not available for me by its shortcut, since / is located on the numeric pad or above number 7, thus won't work).",1390478424,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Sure. But what short-cut? Remember that it needs to:
+
+* not clash with
+** any existing VE shortcut,
+** any expected VE shortcut for future uses (e.g. edit image/template/table), or
+** any OS or browser shortcut (e.g. Ctrl+C for copy, Cmd+Q for quit);
+* be available on most users' keyboards;
+* be type-able; and
+* ideally be the ""standard"" shortcut.
+
+This doesn't leave many options. :-(",1390415278,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),*he uses,1390231974,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle <div lang='xx' dir='yyy'> blocks and similar,"[Split from bug 47759 to cover block level items.]
+
+Bug 47759 covers a language inspector to handle <span lang='xx' dir='yyy'>s, but for <div lang='xx' dir='yyy'> blocks and similar (like annotations on <ul>s or <li>s) we'll need a totally different editing concept.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1390006800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e27vu3d74mxw2xwf3ahr,task_description,open
+VisualEditor: Provide a language inspector to handle <div lang='xx' dir='yyy'> blocks and similar,*** Bug 69892 has been marked as a duplicate of this bug. ***,1408734760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e27vu3d74mxw2xwf3ahr,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Opt-in state, per community member requesting.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://pt.wikibooks.org/wiki/Tópico:Wikilivros_Discussão:Portal_comunitário/Testes_com_o_Editor_Visual_no_Wikilivros",1389996660,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_description,resolved
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Thank you James, it's working great now =)",1391716631,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"(In reply to comment #20)
+> Hi,
+> 
+> Well, something got through because, though it's still not working, it no
+> longer pops up that error message, just quietly hangs while ""loading"" the VE.
+> 
+> Is this a different issue? Or just consequence of stuff that went wrong on
+> monday? I mean, will it get fixed with the next deployment?
+
+Sorry for the slow response - the issue has now (finally) been fixed. See https://pt.wikiversity.org/w/index.php?namespace=&tagfilter=visualeditor&title=Especial%3AMudan%C3%A7as+recentes for a list of all edits with VisualEditor on Portuguese Wikiversity (just my test one so far).",1391711278,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Hi,
+
+Well, something got through because, though it's still not working, it no longer pops up that error message, just quietly hangs while ""loading"" the VE.
+
+Is this a different issue? Or just consequence of stuff that went wrong on monday? I mean, will it get fixed with the next deployment?",1391608662,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,I'm afraid that the deployment went slightly wrong and this fix did not get merged. Sorry. :-(,1391467046,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Hi, thanks, that's useful information. The workshop is not about wikis (it's a permaculture course promoted by the city, that will use wikiversity for classes), and in fact starts at 21:30, so we can plan to start introducing wiki editing after 22:00 and get a better chance of meeting the fix =) Cheers!",1391450361,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"This is scheduled to happen in the hour-long block from 21:00 to 22:00 UTC today (see https://wikitech.wikimedia.org/wiki/Deployments#Week_of_February_3rd row three); it's quite a tricky operation this time around due to other changes, so unfortunately you shouldn't expect it to be available until later in that hour, sorry.",1391448826,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Thank you James,
+
+Any indication this might be shipped by 21:00 UTC today?
+
+[]s",1391444623,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"OK, the configuration change has been merged; this should now ship on Monday (Pacific time); sorry for the confusion and disruption. I'll get a more exact time when I know.",1391212862,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 110660 merged by jenkins-bot:
+Add Wikiversity to site list in ParsoidConfig
+
+https://gerrit.wikimedia.org/r/110660",1391212784,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 110660 had a related patch set uploaded by Jforrester:
+Add Wikiversity to site list in ParsoidConfig
+
+https://gerrit.wikimedia.org/r/110660",1391211712,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"(In reply to comment #11)
+> Ni!
+> 
+> Any idea of whether/when will this get fixed for Wikiversity?
+> 
+> I am giving a workshop Monday evening and I was really really expecting to be
+> able to show people the Visual Editor working on Wikiversity.
+> 
+> Cheers
+> .~´
+
+
+Sorry, this is because https://gerrit.wikimedia.org/r/#/c/108158/ wasn't merged and deployed, so Parsoid has no idea what Wikiversity is. :-(
+
+Working on getting it fixed now.",1391210395,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Ni!
+
+Any idea of whether/when will this get fixed for Wikiversity?
+
+I am giving a workshop Monday evening and I was really really expecting to be able to show people the Visual Editor working on Wikiversity.
+
+Cheers
+.~´",1391137660,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"I confirm it is working on Portuguese Wikibooks[1] but not on Portuguese Wikiversity[2].
+
+[1] https://pt.wikibooks.org/wiki/Special:RecentChanges?tagfilter=visualeditor
+currently has 3 edits.
+[2] https://pt.wikiversity.org/wiki/Álgebra_linear?veaction=edit&uselang=en
+shows the message ""Error loading data from server: parsoidserver-http-bad-status: 404. Would you like to retry?""",1390989577,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Ni!
+
+It ain't working on pt.wikiversity.
+
+After activating VisualEditor, clicking ""Edit"" pops up a floaty with this error:
+
+""Erro ao carregar dados do servidor:  parsoidserver-http-bad-status: 404. Gostaria de tentar novamente?""
+
+I guess that freely translates to
+
+""Error loading data from server: parsoidserver-http-bad-status: 404. Would you like to try again?""
+
+Does seem to be working on pt.wikibooks though.",1390967668,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 108156 merged by Reedy:
+Enable VisualEditor on ptwikibooks, ptwikiversity for testing
+
+https://gerrit.wikimedia.org/r/108156",1390938311,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"(In reply to comment #6)
+> Community consensus for this is where?
+
+It's enabling a widely-deployed code path as an opt-in beta feature for testing…",1390005711,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,Community consensus for this is where?,1390003943,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 108158 had a related patch set uploaded by Jforrester:
+Add ptwikiversity to interwiki map
+
+https://gerrit.wikimedia.org/r/108158",1389998250,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Yes, this is OK. Thank you!",1389997301,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"^^^
+
+Done by that config change; we should be able to get that pushed out w/c 27 January (next week we're in lock-down because people are busy at a conference).
+
+Will this be OK? If there's a major issue, we may need to switch it back off, though this hasn't been a problem so far.",1389997117,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 108156 had a related patch set uploaded by Jforrester:
+Enable VisualEditor on ptwikibooks, ptwikiversity for testing
+
+https://gerrit.wikimedia.org/r/108156",1389996953,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Ni!
+
+Community member here.
+
+.~´",1389996844,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"screenshot
+
+Steps to reproduce:
+
+1.Open VE for a page
+2.Now resize the window down
+2.Go to Settings>Keyboard shortcuts
+
+Observed Result:
+There is no scroll bar in this window therefore cannot see the last line of it as it is getting cut off.
+
+See the screenshot
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13257}",1389992460,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_description,resolved
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Verified the fix in production: https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394827175,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Verified the fix in test2 environment,1394153262,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Verified the fix in Betalabs,1393959948,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Should now be fixed.,1393880384,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Change 116479 merged by jenkins-bot:
+Increase keyboard shortcut height hack to work in FF
+
+https://gerrit.wikimedia.org/r/116479",1393877733,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Change 116479 had a related patch set uploaded by Esanders:
+Increase keyboard shortcut height hack to work in FF
+
+https://gerrit.wikimedia.org/r/116479",1393852600,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Both the scroll bars:Horizontal and vertical remains active in the same time which seems like moving the whole page instead of scrolling in a specific direction,1392941342,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Change 109483 merged by jenkins-bot:
+Fix layout of keyboard shortcuts page
+
+https://gerrit.wikimedia.org/r/109483",1392853095,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Change 109483 had a related patch set uploaded by Esanders:
+Fix layout of keyboard shortcuts page
+
+https://gerrit.wikimedia.org/r/109483",1390677240,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Created attachment 14334
+screenshot
+
+**Attached**: {F13260}",1389992554,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"Once we're happy with it. Currently feature-flagged off.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389930720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_description,resolved
+Deploy TemplateData's GUI editing tool to all wikis,"Change 157478 merged by jenkins-bot:
+Enable TemplateData GUI for all wikis; move config to CommonSettings.php
+
+https://gerrit.wikimedia.org/r/157478",1415297440,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,Scheduled for 6 November.,1412884407,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"Change 157478 had a related patch set uploaded by Jforrester:
+Enable TemplateData GUI for all wikis; move config to CommonSettings.php
+
+https://gerrit.wikimedia.org/r/157478",1409431787,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"(In reply to James Forrester from comment #4)
+> (In reply to Lokal_Profil from comment #3)
+> > What is the current status on deployment to other wikis?
+> 
+> The GUI is deployed on MediaWiki.org but has had little use; we're working
+> on improvements to it, and we'd be interested in feedback. It might be a
+> little premature to deploy it to other wikis, but if you've tried it and
+> think your community would like it, please do ask.
+
+Mainly asking since VisualEditor is now default on many wikis yet the knowledge on how to prepare the templates is sparse and the understanding of how the json works is even more so.
+
+Would an embedded solution (as on Commons) work better/feel more natural? I.e. a ""normal"" template for documenting the template which also produces TemplateData behind the scenes.",1400743392,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"(In reply to Lokal_Profil from comment #3)
+> What is the current status on deployment to other wikis?
+
+The GUI is deployed on MediaWiki.org but has had little use; we're working on improvements to it, and we'd be interested in feedback. It might be a little premature to deploy it to other wikis, but if you've tried it and think your community would like it, please do ask.",1400718826,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,What is the current status on deployment to other wikis?,1397294591,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,*** Bug 63815 has been marked as a duplicate of this bug. ***,1397293229,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"From bug 51734 comment 14:
+| 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
+
+First I think we should deploy it to MediaWiki.org to let people try it out.",1391795259,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"The OOjs UI library has a useful demos directory, which shows off each of the widgets available. Similarly, VisualEditor also has a demos directory, and I imagine other projects do (or would if it became an established pattern.
+
+It would be really great if we could somehow expose these alongside their projects' documentation, so we can point people to a living thing rather than telling them to checkout the repo and play. Something like…
+
+https://doc.wikimedia.org/visualeditor/master/
+https://doc.wikimedia.org/visualeditor/master/demo/
+
+https://doc.wikimedia.org/visualeditor/v0.1.0/
+https://doc.wikimedia.org/visualeditor/v0.1.0/demo/
+
+https://doc.wikimedia.org/oojs-ui/master/
+https://doc.wikimedia.org/oojs-ui/master/demos/
+
+https://doc.wikimedia.org/oojs-ui/v1.0.6/
+https://doc.wikimedia.org/oojs-ui/v1.0.6/demos/
+",1389900720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j4fy326x5cwxfcmowqlo,task_description,resolved
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#1165994, @Krinkle wrote:
+> The main this this is blocked on now is:
+> * Setting up a redirect.
+
+Redirect for what?
+
+> * Upstream OOjs UI and VisualEditor need to have their demo-directory be standalone (like docs). So must not reference `../` but instead build and copy relevant files.
+
+For OOUI, {e538462cbd8f7dcf2423a8ee49b8ebd329f10c84} introduces a `npm demos` command to build the standalone demos directory.",1435891858,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,Timo worked on generic templates to publish /cover/ directories. It can be reused now to publish the /demos/ directories.,1428411882,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#1162486, @hashar wrote:
+> We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+The main blocker for this used to be the ability to run a build script. That is resolved now that we migrated jsduck to labs. The OOjs UI publication job for documentation already makes use of `npm-install` ([example](https://github.com/wikimedia/integration-config/blob/96fa3fd720d13c2f52454ab283382fd0cd38802a/jjb/misc.yaml#L28-L36)).
+
+The main this this is blocked on now is:
+* Setting up a redirect.
+* Upstream OOjs UI and VisualEditor need to have their demo-directory be standalone (like docs). So must not reference `../` but instead build and copy relevant files.
+
+After that, it's just a simple change to update publication job to call push-doc a second time (once for `docs/` to `visualeditor/:version` and a second time for `demos/` to `visualeditor/:version/demo`
+
+> That is similar to {T87490}.
+
+That one is primarily blocked on {T93558}. Trivial otherwise.",1427785748,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#1162486, @hashar wrote:
+> We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+The main blocker for this used to be the ability to run a build script. That is resolved now that we migrated jsduck to labs. The OOjs UI publication job for documentation already makes use of `npm-install` ([example](https://github.com/wikimedia/integration-config/blob/96fa3fd720d13c2f52454ab283382fd0cd38802a/jjb/misc.yaml#L28-L36)).
+
+The main this this is blocked on now is:
+* Setting up a redirect.
+* Upstream OOjs UI and VisualEditor need to have their demo-directory be standalone (like docs). So must not reference `../` but instead build and copy relevant files.
+ 
+ After that, it's just a simple change to update publication job to call push-doc a second time (once for `docs/` to `visualeditor/:version` and a second time for `demos/` to `visualeditor/:version/demo`
+
+> That is similar to {T87490}.
+
+That one is primarily blocked on {T93558}. Trivial otherwise.",1427785735,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#1162486, @hashar wrote:
+> We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+The main blocker for this used to be the ability to run a build script. That is resolved now that we migrated jsduck to labs. The OOjs UI publication job for documentation already makes use of `npm-install` ([example](https://github.com/wikimedia/integration-config/blob/96fa3fd720d13c2f52454ab283382fd0cd38802a/jjb/misc.yaml#L28-L36)).
+
+The main this this is blocked on now is:
+* Setting up a redirect.
+* Upstream OOjs UI and VisualEditor need to have their demo-directory be standalone (like docs). So must not reference `../` but instead build and copy relevant files.
+ 
+ After that, it's just a simple change to update publication job to call push-doc a second time (once for `docs/` to `visualeditor/:version` and a second time for `/demos` to `visualeditor/:version/demo`
+
+> That is similar to {T87490}.
+
+That one is primarily blocked on {T93558}. Trivial otherwise.",1427785693,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"From https://www.mediawiki.org/wiki/Continuous_integration/meetings/2015-03-30/minutes
+
+We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+I have not much time available to handle this though. So it is going to sit in the backlog for now :/
+
+That is similar to {T87490}.",1427724674,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"From https://www.mediawiki.org/wiki/Continuous_integration/meetings/2015-03-30/minutes
+
+We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+I have not much time available to handle this though. So it is going to sit in the backlog for now :/",1427724642,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#962939, @hashar wrote:
+> Can you ship the demo directly in the doc ? Ie: https://doc.wikimedia.org/visualeditor/v0.1.0/doc/demos/ ? The demos could be linked from the documentation main page.
+
+No, they don't nest well and are independent web entry points. Keep them as `doc/` and `demos/`. The `doc/` dir is auto-generated and managed by jsduck. The `demo/` on the other hand is in git and should work after a plain git clone and running install/build.",1420733528,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#962939, @hashar wrote:
+> Can you ship the demo directly in the doc ? Ie: https://doc.wikimedia.org/visualeditor/v0.1.0/doc/demos/ ? The demos could be linked from the documentation main page.
+
+No, they don't nest well and are independent web entry points. Keep them as `doc/` and `demos/`. The `doc/` dir is auto-generated completely. The `demo/` on the other hand is in git and should work after a plain git clone and running install/build.",1420733509,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,Can you ship the demo directly in the doc ? Ie: https://doc.wikimedia.org/visualeditor/v0.1.0/doc/demos/ ? The demos could be linked from the documentation main page.,1420729268,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,Can you ship the demo directly in the doc ? Ie: https://doc.wikimedia.org/visualeditor/v0.1.0/doc/demos/ ? They could be linked from the main page.,1420729253,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"Once we have dev.wikimedia.org up and running, we should migrate documentation to there, which will help remove the awkward terminology overlap/ambiguity between ""documentation"" and ""demo"". We'd e.g. have:
+
+* dev.wikimedia.org/visualeditor/documentation/
+* dev.wikimedia.org/visualeditor/demo/
+
+But for the time being on doc.wikimedia.org, we can just do the same and don't mind the fact that there is already ""doc"" in the url somewhere.
+
+So there's nothing blocking us from having additional directories up on doc.wikimedia.org. The blocking aspects of this are specific to each project.
+
+>>! In T62143#666023, @Spage wrote:
+> This is similar to bug 58620.  Since the OOjs UI demos require nodejs/npm setup similar to building the KSS documentation, fixing this will require similar steps as hashar outlined in comment 1 there.
+
+The blocker for OOjs UI is being able to run Grunt and arbitrary npm dependencies on the server. Which is blocked on migrating that job from gallium to labs slaves.
+
+For VisualEditor, the main blocker was directory management (it doesn't require a build step).",1420733430,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"Once we have dev.wikimedia.org up and running, we should migrate documentation to there, which will help remove the awkward terminology overlap/ambiguity between ""documentation"" and ""demo"". We'd e.g. have:
+
+* dev.wikimedia.org/visualeditor/documentation/
+* dev.wikimedia.org/visualeditor/demo/
+
+But for the time being on doc.wikimedia.org, we can just do the same and don't mind the fact that there is already ""doc"" in the url somewhere.",1420729145,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"This is similar to bug 58620.  Since the OOjs UI demos require nodejs/npm setup similar to building the KSS documentation, fixing this will require similar steps as hashar outlined in comment 1 there.",1390635527,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"(In reply to comment #1)
+> Do the demo require a server side backend or are they 100% executing in the
+> browser?  If we need to serve content, that would need to be done on another
+> server.  Else, it is ""just"" about enhancing the doc jobs to publish the demo
+> to
+> the document root.
+
+Fully stand-alone client-side JS only, providing static files. Theoretically they could just be linked off beta's bits – e.g. http://bits.beta.wmflabs.org/static-master/extensions/VisualEditor/lib/ve/demos/ve/eventLogger.html – but this is ugly (and doesn't work for OOjs UI because it's only deployed in compiled form without demos).",1389930597,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"Do the demo require a server side backend or are they 100% executing in the browser?  If we need to serve content, that would need to be done on another server.  Else, it is ""just"" about enhancing the doc jobs to publish the demo to the document root.",1389903054,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+VisualEditor: Math inspector live preview double-escapes angle brackets,"1. Create a new math node (Insert -> Formula)
+2. Type L' = \{\<x, \underbrace{1111\dots1111}_{s(|x|)}0\> | x \in L\} into the input box
+3. Observe &lt; and &gt; in the preview :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1389829140,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qqtn53sr5xr6josxp5cm,task_description,resolved
+VisualEditor: Math inspector live preview double-escapes angle brackets,"
+
+*** This bug has been marked as a duplicate of bug 57429 ***",1404431099,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qqtn53sr5xr6josxp5cm,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Intention:
+Delete a template.
+
+Steps to Reproduce:
+1. Open an article containing a template.
+2. Select the template.
+3. Try to press the delete key on the now-non-existent keyboard.
+
+Actual Results:  
+The keyboard closes, so you can't delete them.
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67390",1389825480,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_description,resolved
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 230592 merged by jenkins-bot:
+MobileContext: Provide a delete button for nodes' context
+
+[[https://gerrit.wikimedia.org/r/230592]]",1439307483,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Mobile styling:
+{F1273774}",1439290242,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 163662 abandoned by Esanders:
+[WIP] Add a ""Remove"" context button to all Focusable nodes
+
+Reason:
+Context items have moved on a fair bit. See I41109537d for latest attempt.
+
+[[https://gerrit.wikimedia.org/r/163662]]",1439244361,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 230592 had a related patch set uploaded (by Esanders):
+[WIP] Delete button for node context items
+
+[[https://gerrit.wikimedia.org/r/230592]]
+",1439233247,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","I have a patch which adds a delete action. The only question is should we hide it on desktop, because it looks okay and could be useful:
+
+{F1182099}
+",1439233080,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 163662 had a related patch set uploaded (by Jforrester):
+[WIP] Add a ""Remove"" context button to all Focusable nodes
+
+[[https://gerrit.wikimedia.org/r/163662]]
+",1428510131,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","(In reply to Ed Sanders from comment #11)
+> Of course this behaves completely differently in iOS 8 (the keyboard stays
+> up). *sigh*
+
+Re-prioritising.",1412469153,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",Of course this behaves completely differently in iOS 8 (the keyboard stays up). *sigh*,1412437336,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 163662 had a related patch set uploaded by Jforrester:
+Add a ""Remove"" context button to all Focussable nodes
+
+https://gerrit.wikimedia.org/r/163662",1412020628,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","This seems to be because we programmatically move focus from the surface to the pasteTarget, and iOS Safari is very picky about when it allows a programmatic focus move to open the keyboard. Something like, it only works if you do it in direct response to a mouse/touch event. I tried a few solutions I found on the internet but I haven't gotten any of them to work yet.",1408469978,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",*** Bug 67257 has been marked as a duplicate of this bug. ***,1407064915,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","(In reply to Brion Vibber from comment #6)
+> I've noticed a few bugs coming through related to certain operations hiding
+> the keyboard and then that killing focus and causing selections and menus to
+> disappear. Is there a general problem where losing keyboard focus causes VE
+> to lose state?
+
+Quite possibly; escalating.",1404332970,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",I've noticed a few bugs coming through related to certain operations hiding the keyboard and then that killing focus and causing selections and menus to disappear. Is there a general problem where losing keyboard focus causes VE to lose state?,1404331255,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Yes, for all block items such as image, reference note, template ,math function: selecting it hides the keyboard.",1404168367,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",Can this be rechecked?,1404166204,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Aaaah, OK. Updating summary to reflect that.",1389833609,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","No, I mean the keyboard.  It's an iPad without an attached physical keyboard.  The keyboard is displayed on the screen, like the one shown in the picture at https://commons.wikimedia.org/wiki/File:Apple_iPad_Event03.jpg
+
+(Presumably the same problem happens on any mobile device.)",1389831224,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",Did you mean the cursor instead of the keyboard? Surely VisualEditor didn't make your physical keyboard dissolve into a pool of molten plastic?,1389826148,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+VisualEditor: Namespace mixin properties,"Especially now that we have mixins adding properties with very generic names like this.min and this.max (ResizeableNode), we should look at namespacing them. Maybe an object to contain them all, like this.resizeableNode = { min: 1, max: 1000 }; ?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389822180,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xkdnjrereisoecj453z5,task_description,open
+Zuul: python git assert error assert len(fetch_info_lines) == len(fetch_head_info),"Spotted by EdSanders on https://gerrit.wikimedia.org/r/#/c/107036/
+
+
+2014-01-12 14:29:20,163 INFO zuul.IndependentPipelineManager: Change <Change 0x7f30084dcf10 107036,1> depends on changes []
+2014-01-12 14:29:20,165 DEBUG zuul.Repo: Resetting repository /srv/ssd/zuul/git/mediawiki/extensions/VisualEditor
+2014-01-12 14:29:20,165 DEBUG zuul.Repo: Updating repository /srv/ssd/zuul/git/mediawiki/extensions/VisualEditor
+2014-01-12 14:29:24,064 DEBUG zuul.Repo: Checking out master
+2014-01-12 14:29:26,280 DEBUG zuul.Merger: Unable to merge <Change 0x7f30084dcf10 107036,1>
+Traceback (most recent call last):
+  File ""/usr/local/lib/python2.7/dist-packages/zuul/merger.py"", line 206, in _mergeChange
+    repo.merge(change.refspec, 'resolve')
+  File ""/usr/local/lib/python2.7/dist-packages/zuul/merger.py"", line 97, in merge
+    self.fetch(ref)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul/merger.py"", line 111, in fetch
+    origin.fetch(ref)
+  File ""/usr/lib/python2.7/dist-packages/git/remote.py"", line 593, in fetch
+    return self._get_fetch_info_from_stderr(proc, progress or RemoteProgress())
+  File ""/usr/lib/python2.7/dist-packages/git/remote.py"", line 539, in _get_fetch_info_from_stderr
+    assert len(fetch_info_lines) == len(fetch_head_info), ""len(%s) != len(%s)"" % (fetch_head_info, fetch_info_lines)
+AssertionError: len([""3d35f5b84a26171535e869fed4a1c73dbeaeec69\t\t'refs/changes/36/107036/1' of ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor\n""]) != len(['Total 9 (delta 7), reused 9 (delta 7)', ' * branch            refs/changes/36/107036/1 -> FETCH_HEAD'])
+2014-01-12 14:29:26,318 INFO zuul.IndependentPipelineManager: Unable to merge change <Change 0x7f30084dcf10 107036,1>
+2014-01-12 14:29:26,319 DEBUG zuul.IndependentPipelineManager: Reporting change <Change 0x7f30084dcf10 107036,1>
+2014-01-12 14:29:26,319 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f30084dcf10 107036,1>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x25821d0>, {'verified': -1}>]
+2014-01-12 14:29:26,319 DEBUG zuul.reporter.gerrit.Reporter: Report change <Change 0x7f30084dcf10 107036,1>, params {'verified': -1}, message: Build failed.
+
+This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset.
+
+
+
+There is a few occurrences in the Zuul debug log: fgrep assert /var/log/zuul/debug*
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1389609900,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-cfrv36eokvo6qttirzvb,task_description,resolved
+Zuul: python git assert error assert len(fetch_info_lines) == len(fetch_head_info),"The Zuul Debian package embeds some python modules including `GitPython` which is now `>=0.3.3`.
+
+",1446722644,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-cfrv36eokvo6qttirzvb,task_subcomment,NA
+Zuul: python git assert error assert len(fetch_info_lines) == len(fetch_head_info),That is apparently solved in v3.2.  Now pending upgrade of Zuul.,1428919361,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-cfrv36eokvo6qttirzvb,task_subcomment,NA
+Zuul: python git assert error assert len(fetch_info_lines) == len(fetch_head_info),"Possible upstream bug: https://github.com/gitpython-developers/GitPython/issues/94
+
+Got to find a way to reliably reproduce the issue :(",1389610881,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-cfrv36eokvo6qttirzvb,task_subcomment,NA
+VisualEditor: Exception thrown placing cursor at end of document with no content offsets,"1. Create a document with just a block image [[File:Foo.jpg|thumb]] on one line
+2. Edit the document and try to place the cursor in the second slug (after the image)
+3. An exception is thrown (getNearestContentOffset(selection.end) returns -1 and this is fed into getAnnotationsFromOffset)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389539280,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2pul64ax3wl2rgoic6ap,task_description,resolved
+VisualEditor: Exception thrown placing cursor at end of document with no content offsets,verified the fix in test2,1389911469,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2pul64ax3wl2rgoic6ap,task_subcomment,NA
+VisualEditor: Exception thrown placing cursor at end of document with no content offsets,"Change 107134 merged by jenkins-bot:
+Check for valid offset when calculating insertion annotations
+
+https://gerrit.wikimedia.org/r/107134",1389641853,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2pul64ax3wl2rgoic6ap,task_subcomment,NA
+VisualEditor: Exception thrown placing cursor at end of document with no content offsets,"Change 107134 had a related patch set uploaded by Esanders:
+Check for valid offset when calculating insertion annotations
+
+https://gerrit.wikimedia.org/r/107134",1389616550,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2pul64ax3wl2rgoic6ap,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"In the read mode
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a reference to a text by going to Insert>Reference
+3.When the reference dialog box opens up insert a numbered list and then type the reference for example as: 1.reference
+4.Click on ""Insert Reference""
+5.Save the page
+
+Observed Result:
+In the read mode,the serials of the numbered list are appearing in wikitext with #.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan7th
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12322}",1389122340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_description,resolved
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"The PHP parser requires a \n before every *, including the first one. So it should be:
+
+Hey!<ref>
+* foo
+* ...
+
+Unless you want to start messing with the PHP parser...",1392388249,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"(In reply to Ed Sanders from comment #5)
+> Todo: create a ticket for the Parsoid side if this bug (not inserting line
+> breaks before */#)
+
+Ed, what's the specific problem Parsoid's doing wrong?
+
+<p>Hey!<span class=""reference"" data-mw=""{&quot;name&quot;:&quot;ref&quot;,&quot;body&quot;:{&quot;html&quot;:&quot;&lt;ul &gt;&lt;li &gt; foo&lt;/li&gt;&lt;li &gt; bar&lt;/li&gt;&lt;li &gt; baz&lt;/li&gt;&lt;/ul&gt;&quot;},&quot;attrs&quot;:{}}"" id=""cite_ref-1-0"" rel=""dc:references"" typeof=""mw:Extension/ref""><a href=""#cite_note-1"">[1]</a></span></p>
+
+… goes neatly to …
+
+Hey!<ref>* foo
+* bar
+* baz</ref>
+
+With \n as needed.",1392320541,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,Todo: create a ticket for the Parsoid side if this bug (not inserting line breaks before */#),1391676490,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,https://gerrit.wikimedia.org/r/#/c/111507/,1391630644,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,One really shouldn't put lists inside a reference. References are supposed to be a single paragraph. I'll remove the tools for doing so which should reduce the impact of this.,1391630603,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"This issue is also occurring for bullet list thats is added inside Reference dialog bix, they appear as * in the Read mode",1389213301,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"Created attachment 14250
+In Edit mode
+
+**Attached**: {F12323}",1389122417,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor:Special Character option remains selected even after closing the window,"screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select Insert>Special Character
+3.Close the special character window.
+4.Go to Insert option in the toolbar
+
+Observed Result:
+The Special Character option is still appearing selected even after closing the window
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Jan7th?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12316}",1389120960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-46ixfpirqh7liqxoja7t,task_description,resolved
+VisualEditor:Special Character option remains selected even after closing the window,This issue got fixed with https://gerrit.wikimedia.org/r/#/c/107193/,1389900742,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-46ixfpirqh7liqxoja7t,task_subcomment,NA
+mediawiki/extensions.git is broken again (so VisualEditor isn't getting updated on betalabs),"Bug 49846 was this happening last time around. Possibly the same cause.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389084780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3recwohppy6wk6kediy2,task_description,resolved
+mediawiki/extensions.git is broken again (so VisualEditor isn't getting updated on betalabs),"Merging into 49846 then.
+
+*** This bug has been marked as a duplicate of bug 49846 ***",1389149751,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3recwohppy6wk6kediy2,task_subcomment,NA
+mediawiki/extensions.git is broken again (so VisualEditor isn't getting updated on betalabs),"Ok, so it's definitely bug 49846 coming back again.
+
+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)
+
+Which is wrong Wrong WRONG! There's a bug here, will need to report upstream.
+
+In the meantime: we can't have submodule subscriptions where there's a repo with the same base name. Gerrit gets confused.
+
+VisualEditor.git will have to be renamed or something if we expect mw/ext/VisualEditor to update properly.",1389115077,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-3recwohppy6wk6kediy2,task_subcomment,NA
+mediawiki/extensions.git is broken again (so VisualEditor isn't getting updated on betalabs),"Trying to update manually on deployment-bastion.pmtpa.wmflabs in /home/wikipedia/common/php-master/extensions
+
+Looking at VisualEditor:
+
+
+$ git submodule VisualEditor
+ 3e925e634398ab80711819ee4c10a29b89854588 VisualEditor (remotes/origin/wmf/1.23wmf9-1-g3e925e6)
+
+Although the HEAD of mediawiki/extensions.git checkout is up to date :(",1389085980,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-3recwohppy6wk6kediy2,task_subcomment,NA
+VisualEditor: Add tooltips to drop-down menus,"Especially if the icon for a menu button is a mere symbol, add a tooltip to that button (i.e., the three-bars icon).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389017400,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ckbwvojthagfr3sxjhi7,task_description,resolved
+VisualEditor: Add tooltips to drop-down menus,"Change 108855 had a related patch set uploaded by Jforrester:
+Add tooltips to the drop-down menus explaining what they do
+
+https://gerrit.wikimedia.org/r/108855",1390348682,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ckbwvojthagfr3sxjhi7,task_subcomment,NA
+VisualEditor: Use multipart/form-data encoding when POSTing HTML,"Per Gabriel's report via email, when VE POSTs HTML, it uses multipart/x-www-urlencoded to encode the POST body, which results in a lot of URL-encoding of special characters (especially <>"") in the HTML. We should instead use multipart/form-data , which is more efficient for such large POST bodies with many special characters.
+
+TODO: Figure out how to tell the browser to use this encoding when sending an AJAX request.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388891640,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-buhdykqbpmicqrkqd7ao,task_description,resolved
+VisualEditor: Use multipart/form-data encoding when POSTing HTML,"Change 105486 merged by jenkins-bot:
+Add multipart/form-data emulation to ve.init.mw.Target#apiRequest
+
+https://gerrit.wikimedia.org/r/105486",1389824910,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-buhdykqbpmicqrkqd7ao,task_subcomment,NA
+VisualEditor: Use multipart/form-data encoding when POSTing HTML,"Change 105486 had a related patch set uploaded by Catrope:
+Add multipart/form-data emulation to ve.init.mw.Target#ajax
+
+https://gerrit.wikimedia.org/r/105486",1388901240,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-buhdykqbpmicqrkqd7ao,task_subcomment,NA
+"VisualEditor:  Can't add new paragraphs to the end of the page, if the last line is an empty section heading == <nowiki/> ==","Intention:
+Add a new paragraph at the bottom of a page that ended in == <nowiki/> == (not counting the category after the empty section heading).
+
+I was hoping that adding a new paragraph underneath the blank section heading would allow me to select, and therefore to remove, the blank section heading.
+
+
+Steps to Reproduce:
+1. Edit a page that ends in a == <nowiki/> ==, like https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox2&oldid=589158823
+
+2. Place the cursor in the empty section heading.
+
+3. Hit return.
+
+Actual Results:  
+Pressing return adds blank paragraphs *above* the empty section heading. 
+
+If you type anything into the section heading, then it starts behaving normally.
+
+Expected Results:  
+Doing the same thing for an empty (or non-empty) section heading anywhere else on the page adds new paragraphs *under* the empty section heading.  Pressing return in a section heading should produce the same behavior everywhere on the page.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388854920,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rmjvwpvg64vxchilw4se,task_description,resolved
+"VisualEditor:  Can't add new paragraphs to the end of the page, if the last line is an empty section heading == <nowiki/> ==","Change 160215 merged by jenkins-bot:
+ve.ce.Surface: Insert new paragraphs after empty nodes rather than before
+
+https://gerrit.wikimedia.org/r/160215",1410802196,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rmjvwpvg64vxchilw4se,task_subcomment,NA
+"VisualEditor:  Can't add new paragraphs to the end of the page, if the last line is an empty section heading == <nowiki/> ==","Change 160215 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ce.Surface: Insert new paragraphs after empty nodes rather than before
+
+https://gerrit.wikimedia.org/r/160215",1410622295,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rmjvwpvg64vxchilw4se,task_subcomment,NA
+"VisualEditor:  Can't add new paragraphs to the end of the page, if the last line is an empty section heading == <nowiki/> ==","This is also reproducible with other block nodes, like preformatted text.
+
+There's code in ve.ce.Surface#handleEnter to ""If we're at the start/end of something that's not a paragraph, insert a paragraph before/after"". The quirk is that it checks for the ""at the start"" case before checking the ""at the end"" case, and for empty elements both of these are true. Let's just flip the order.",1410622014,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-rmjvwpvg64vxchilw4se,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63600",1388780520,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_description,resolved
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","Change 127388 merged by jenkins-bot:
+Set context title when rendering edit notices and checkboxes
+
+https://gerrit.wikimedia.org/r/127388",1397879336,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","Change 127388 had a related patch set uploaded by Alex Monk:
+Set context title when rendering edit notices and checkboxes
+
+https://gerrit.wikimedia.org/r/127388",1397873423,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","In FlaggablePageView::addReviewCheck, $this->article->isReviewable() returns false.
+
+I made some uncommitted live hacks on deployment-apache01.eqiad.wmflabs and replayed the API request in Chrome until I got the right server. Turns out, $this->article represents the ""API"" title. Why is this not happening on my machine?",1397848981,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","I see the same thing on Wikimedia sites, but cannot replicate the issue locally.",1394068668,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing",The message is <revreview-check-flag-p>. Presumably this doesn't get fetched in the new save dialog like it used to?,1394064108,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+VisualEditor: adding a reference duplicates infobox on da.wp,"https://da.wikipedia.org/w/index.php?title=F-35_Lightning_II&diff=prev&oldid=7409486
+and
+https://da.wikipedia.org/w/index.php?title=Enhedslisten&diff=prev&oldid=7414100 seem a few examples of what the title says. 
+
+I couldn't reproduce because of {T61599}.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See also**: {T51823}",1388769180,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-42a5ngyvptb5lztis6k3,task_description,resolved
+VisualEditor: adding a reference duplicates infobox on da.wp,I tried reproducing this and got nothing. Feel free to reopen if I've missed something.,1437602936,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-42a5ngyvptb5lztis6k3,task_subcomment,NA
+VisualEditor: adding a reference duplicates infobox on da.wp,"If you can't reproduce any longer, given how old the task is, feel free to close - it can be reopened if and when the need arises.",1432646744,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-42a5ngyvptb5lztis6k3,task_subcomment,NA
+VisualEditor: adding a reference duplicates infobox on da.wp,Is this still valid?,1421888145,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-42a5ngyvptb5lztis6k3,task_subcomment,NA
+VisualEditor: Make it more obvious when the user is doing something foolish with links (e.g. extending the wrong one),"Minor corruption:
+
+<https://www.mediawiki.org/w/index.php?title=Architecture_Summit_2014/Straw_poll&diff=870066&oldid=870065&diffonly=1> and <https://www.mediawiki.org/w/index.php?title=Architecture_Summit_2014/Straw_poll&diff=870064&oldid=870063&diffonly=1>
+
+More serious corruption:
+
+<https://www.mediawiki.org/w/index.php?title=Architecture_Summit_2014/Straw_poll&diff=870067&oldid=870066&diffonly=1>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388701200,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-b6gfeng3ezs2u5pyporj,task_description,resolved
+VisualEditor: Make it more obvious when the user is doing something foolish with links (e.g. extending the wrong one),Should be fixed by the new link cartouching.,1443035624,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-b6gfeng3ezs2u5pyporj,task_subcomment,NA
+VisualEditor: Make it more obvious when the user is doing something foolish with links (e.g. extending the wrong one),@Trevor: Do you know already how you are going to handle this?,1389993157,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-b6gfeng3ezs2u5pyporj,task_subcomment,NA
+"VisualEditor: Copying part of a table into an existing cell should over-write cell values, not insert it as a sub-table","Steps to reproduce:
+
+1) Begin with an existing wikitext table (e.g., 4 rows, 4 columns).  Open the page in VisualEditor.
+
+2) Copy part of a different table or spreadsheet (e.g., 2 rows, 4 columns).
+
+3) Place cursor inside a cell of the table in VisualEditor.
+
+4) Paste the copied table.
+
+
+Results:
+
+VisualEditor places the entire new/rich-copied table, including wikitext formatting, inside the first cell.  The wikitext parser does not deal very gracefully with table-within-table formatting.
+
+
+Desired outcome:
+
+VisualEditor should overwrite the contents of the cells with the new material.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/w/index.php?diff=588462959&oldid=588405367#Create_and_copy_table.",1388613660,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-fz6jo77atbl2ydzv46s4,task_description,resolved
+"VisualEditor: Copying part of a table into an existing cell should over-write cell values, not insert it as a sub-table",I wasn't wrong. Done in wmf.12.,1454136198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fz6jo77atbl2ydzv46s4,task_subcomment,NA
+"VisualEditor: Copying part of a table into an existing cell should over-write cell values, not insert it as a sub-table","This'll be… hard, to put it mildly. We should think about whether it's what we want to achieve in terms of UX before embarking on it.",1390025021,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fz6jo77atbl2ydzv46s4,task_subcomment,NA
+mw.user.tokens does not include all token types,"mw.user.getToken only supports edit, watch and patrol.
+It should support all other types of token.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: enhancement",1388444160,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-asfp6tebtqdcuww7w2ty,task_description,declined
+mw.user.tokens does not include all token types,"The `user.tokens` module is an internal optimisation to avoid one extra API roundtrip for built-in ajax actions such as ""Ajax watchstar"" and submitting edits to the API for e.g. VisualEditor and such.
+
+The tokens should be retrieved via `mw.Api#getToken` which already supports all other token types. There are no plans to expand the set of preloaded token types as there is no performance reason to do so (yet).
+
+Note that since 2014, most token types (such as `move`, `edit`, `delete` etc.) have been deprecated in favour of a single `csrf` token type, which should already significantly reduce the number of cases where `mw.Api#getToken` would actually need to fetch a token.",1571098112,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-asfp6tebtqdcuww7w2ty,task_subcomment,NA
+mw.user.tokens does not include all token types,Apologies mw.user.tokens.get,1388678493,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-asfp6tebtqdcuww7w2ty,task_subcomment,NA
+mw.user.tokens does not include all token types,"???
+
+I can't find mw.user.getToken. mw.api.getToken exists and it supports all tokens.",1388664579,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-asfp6tebtqdcuww7w2ty,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page using VE in Chrome browser.
+2.Copy a math function or item from that page
+3.Open another page with VE in FireFox
+4.Paste the copied math item in this page
+
+Observed Result:
+The math item does not get copied and in the console there is an error appearing:
+ TypeError:Item is undefined
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12369}",1388093400,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a3gencpajun7iccgc53o,task_description,resolved
+VisualEditor: Copy paste is not working for Math elements,Fixed a while ago,1442495255,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"No, I mean it renders fine for me.",1416332653,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"(In reply to Rummana Yasmeen from comment #4)
+> you mean, its fine if the copied math math function does not render on the other
+> page?
+
+*Does not*
+
+Because , right now it is not rendering unless I save the page",1416266416,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"you mean, its fine if the copied math math function does render on the other page?",1416266350,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,This... Appears to work now.,1416182975,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"Not getting the error - presumably that got fixed, but the copy does not *appear* to do anything. When I run the target in debug mode, I see that we're getting mwMath entries in the model, and you can select them. They just don't render as anything.",1407252211,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=26th_paste_ff&veaction=edit",1388093526,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,"screenshot of the link after copy paste
+
+Steps to reproduce:
+
+1.Open an editor in Firfox which contains a link
+2.Copy the link 
+3.Paste it into another VE and save it
+
+Observed Result:
+The link is appearing within [] bracket and with a lock icon beside it.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12199}",1387823880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_description,resolved
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,*** Bug 60379 has been marked as a duplicate of this bug. ***,1390515118,PHID-USER-4cgt73x34j35pnbem65l,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,Possibly got fixed by https://gerrit.wikimedia.org/r/#/c/106253/ as it was happening even just before wmf11 deployment in test2,1389902753,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,This is also happening for Chrome Browser.,1389821557,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,Test Environment should be test2 in above comment,1387824115,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,"Test Environment:betalabs
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/23rd_paste",1387824027,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"[14:38] <gwicke> in native CE shift-enter inserts a newline in a pre
+[14:38] <gwicke> normal enter splits it
+[14:40] <gwicke> woah: shift-enter actually works in VE as long as it is not on the last line of a pre
+[14:41] <gwicke> it does not work when the cursor is on the first or last char in a pre
+[14:41] <gwicke> before first char a paragraph is inserted before the pre
+[14:41] <gwicke> after last char a paragraph is inserted after the pre and the cursor moves there
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1387579680,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-el7cvjkat7q3jypwgavh,task_description,resolved
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"Change 809024 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (c5804af0a)%%%
+https://gerrit.wikimedia.org/r/809024",1656367024,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"Change 809024 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (c5804af0a)%%%
+https://gerrit.wikimedia.org/r/809024",1656365029,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"Change 806917 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Handle Shift+Enter at the start/end of pre nodes too%%%
+https://gerrit.wikimedia.org/r/806917",1656350224,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"Change 806917 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[VisualEditor/VisualEditor@master] Handle Shift+Enter at the start/end of pre nodes too%%%
+https://gerrit.wikimedia.org/r/806917",1655736623,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"The (ugly) workaround I'm using since years on this issue:
+- type an 'x' and the end
+- move the cursor left next to the 'x'
+- press shift-enter a couple of times to get the blank lines needed
+- edit those lines
+- finally remove the trailing 'x'
+
+I would really like to see a more user-friendly fix on this.",1639733697,PHID-USER-hhjjrf7an2jltkq76hub,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"And ran into this again :( quite annoying for preformatted sections in VE, I need to switch back to source editing",1639732555,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"I've also ran into this and was wondering what the status/plan for fixing or working around this bug is, thanks!",1633591756,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"I just ran into this bug while using VisualEditor and preformatted text. I consider this a severe issue in the preformatted editor, so I wonder if this could be raised and fixed.",1559285876,PHID-USER-hhjjrf7an2jltkq76hub,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Pasting formulæ isn't working in Firefox,"screenshot
+
+Steps to reproduce:
+
+1.Create a new page in FF
+2.Copy a math function from another VE 
+3.Paste it in this new page
+4.Click on Save Page
+
+Observed Result:
+""Error: Creating new, empty pages is not allowed"" appears
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12772}",1387577640,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ikkzdnx32gvzflyd7h5m,task_description,resolved
+VisualEditor: Pasting formulæ isn't working in Firefox,"Actually, Math functions are not at all getting copy pasted in FF.For a new page it says this error ""Error: Creating new, empty pages is not allowed"" and for any other existing page when you copy a math function and paste it into another VE,it shows it in the edit mode but after saving it just disappears.",1387577982,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ikkzdnx32gvzflyd7h5m,task_subcomment,NA
+VisualEditor: Pasting formulæ isn't working in Firefox,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5",1387577688,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ikkzdnx32gvzflyd7h5m,task_subcomment,NA
+VisualEditor:Math formula does not appear immediately after copy-paste in test2,"Steps to reproduce:
+
+1.Open the editor for a page
+2.Open the latex window and insert ""\sqrt\pi""
+3.Click on the ""<"" button to close the latex window
+4.Copy the formula immediately
+5.Paste it onto another page
+
+Observed Result:
+The math elements does not appear on the page after pasting.However after saving it appears there are multiple of those 
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/19th_december?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387485660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bcrdaw3njczs7zhzj3to,task_description,resolved
+VisualEditor:Math formula does not appear immediately after copy-paste in test2,We fixed this a while ago. :-),1415881871,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bcrdaw3njczs7zhzj3to,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,"Copied from bug 58347:
+
+1.Create a page ""A"" with three links in three consecutive lines.
+2.Create another page ""B"" where you will copy these links to.
+3.Copy the first and second link to ""B""
+4.Save it.
+5.Reopen the editor.
+6.Now copy the third link and paste it to the third line of ""B""
+7.Save it.
+
+Observed Result:
+The second and the third link in page B is getting merged.
+
+Example Pages:
+
+A:http://en.wikipedia.beta.wmflabs.org/wiki/19th_december_source?veaction=edit
+B:http://en.wikipedia.beta.wmflabs.org/wiki/19th_destination
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387471560,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2j26u6grwn6r7iymvg75,task_description,open
+New line at end of document sometimes merged into previous line on paste,"In ryasmeen's HTML dump the last paragraph contains both the text and the pasted citation. Apparently the VE rendering showed the citation in a separate line, so the discrepancy in the HTML emitted by VE (citation actually in the preceding paragraph) seems to be a bug in VE. Moving this to VE for that reason.",1389059559,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,"HTML dump:
+
+Request URL:http://en.wikipedia.beta.wmflabs.org/w/api.php
+Request Method:POST
+Status Code:200 OK
+Request Headersview source
+Accept:application/json, text/javascript, */*; q=0.01
+Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
+Accept-Encoding:gzip,deflate,sdch
+Accept-Language:en-US,en;q=0.8
+Connection:keep-alive
+Content-Length:10758
+Content-Type:application/x-www-form-urlencoded; charset=UTF-8
+Cookie:uls-previous-languages=%5B%22en%22%5D; mediaWiki.user.sessionId=IWxgkz08OFNZxaGwaIxUNKilap37xFbY; mediaWiki.user.bucket%3Aext.articleFeedbackv5%4011-tracking=11%3Aignore; mediaWiki.user.bucket%3Aext.articleFeedbackv5%406-form=6%3A6; mediaWiki.user.bucket%3Aext.articleFeedbackv5%405-links=5%3AX; centralnotice_bucket=1-4.2; enwikiLoggedOut=1389029323; centralauth_LoggedOut=1389029332; enwikiUserID=1348; enwikiUserName=RYasmeen+%28WMF%29; enwikiSession=568d9870c44e9934b5912175d6faaea9; centralauth_User=RYasmeen+%28WMF%29; centralauth_Session=0d74cc0544d444b6ba6b684092f01228; edittoolscharsubset=0; ve-beta-welcome-dialog=1
+Host:en.wikipedia.beta.wmflabs.org
+Origin:http://en.wikipedia.beta.wmflabs.org
+Referer:http://en.wikipedia.beta.wmflabs.org/wiki/Copy-paste6th?veaction=edit
+User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31
+X-Requested-With:XMLHttpRequest
+Form Dataview sourceview URL encoded
+action:visualeditor
+paction:serializeforcache
+html:<!doctype html><html prefix=""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/"" about=""http://en.wikipedia.beta.wmflabs.org/wiki/Special:Redirect/revision/73736""><head prefix=""mwr: http://en.wikipedia.beta.wmflabs.org/wiki/Special:Redirect/""><meta property=""mw:articleNamespace"" content=""0""><link rel=""dc:replaces"" resource=""mwr:revision/73705""><meta property=""dc:modified"" content=""2014-01-07T01:05:54.000Z""><meta about=""mwr:user/1348"" property=""dc:title"" content=""RYasmeen (WMF)""><link rel=""dc:contributor"" resource=""mwr:user/1348""><meta property=""mw:revisionSHA1"" content=""a473161a3483e47f6d590fd9f039238f9303b459""><meta property=""dc:description"" content=""""><meta property=""mw:parsoidVersion"" content=""0""><link rel=""dc:isVersionOf"" href=""//en.wikipedia.beta.wmflabs.org/wiki/Copy-paste6th""><title>Copy-paste6th</title><base href=""//en.wikipedia.beta.wmflabs.org/wiki/Copy-paste6th""></head><body data-parsoid=""{&quot;dsr&quot;:[0,277,0,0]}""><p data-parsoid=""{&quot;dsr&quot;:[0,20,0,0]}""><a href=""./Link_to_catapult"" rel=""mw:WikiLink"" data-parsoid=""{&quot;stx&quot;:&quot;simple&quot;,&quot;a&quot;:{&quot;href&quot;:&quot;./Link_to_catapult&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;link to catapult&quot;},&quot;dsr&quot;:[0,20,2,2]}"">link to catapult</a></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[22,31,0,0]}""><a href=""./LinkA"" rel=""mw:WikiLink"" data-parsoid=""{&quot;stx&quot;:&quot;simple&quot;,&quot;a&quot;:{&quot;href&quot;:&quot;./LinkA&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;linkA&quot;},&quot;dsr&quot;:[22,31,2,2]}"">linkA</a></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[33,42,0,0]}""><a href=""./LinkB"" rel=""mw:WikiLink"" data-parsoid=""{&quot;stx&quot;:&quot;simple&quot;,&quot;a&quot;:{&quot;href&quot;:&quot;./LinkB&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;linkB&quot;},&quot;dsr&quot;:[33,42,2,2]}"">linkB</a></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[44,101,0,0]}"">[<a href=""http://en.wikipedia.beta.wmflabs.org/wiki/LinkC|linkC"" rel=""mw:ExtLink"" data-parsoid=""{&quot;targetOff&quot;:99,&quot;contentOffsets&quot;:[99,99],&quot;dsr&quot;:[45,100,54,1]}""></a>]</p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[103,119,0,0]}""><img class=""tex"" alt=""\pi"" src=""//upload.beta.wmflabs.org/math/5/2/2/522359592d78569a9eac16498aa7a087.png"" typeof=""mw:Extension/math"" data-mw=""{&quot;name&quot;:&quot;math&quot;,&quot;attrs&quot;:{},&quot;body&quot;:{&quot;extsrc&quot;:&quot;\\pi&quot;}}"" data-parsoid=""{&quot;src&quot;:&quot;&lt;math&gt;\\pi&lt;/math&gt;&quot;,&quot;dsr&quot;:[103,119,2,2]}"" about=""#mwt7""></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[121,174,0,0]}"">text<span class=""citation web"" about=""#mwt2"" typeof=""mw:Transclusion"" data-mw=""{&quot;parts&quot;:[{&quot;template&quot;:{&quot;target&quot;:{&quot;wt&quot;:&quot;Cite web&quot;,&quot;href&quot;:&quot;./Template:Cite_web&quot;},&quot;params&quot;:{&quot;url&quot;:{&quot;wt&quot;:&quot;http://yahoo.com&quot;},&quot;title&quot;:{&quot;wt&quot;:&quot;yahoo&quot;}},&quot;i&quot;:0}}]}"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;,&quot;dsr&quot;:[125,174,null,null],&quot;pi&quot;:[[{&quot;k&quot;:&quot;url&quot;,&quot;named&quot;:true},{&quot;k&quot;:&quot;title&quot;,&quot;named&quot;:true}]]}""><a rel=""mw:ExtLink"" href=""http://yahoo.com"" data-parsoid=""{&quot;targetOff&quot;:45,&quot;contentOffsets&quot;:[45,52],&quot;a&quot;:{&quot;href&quot;:&quot;http://yahoo.com&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;A]]\n\n[[linkB]]\n\n&quot;}}"">""yahoo""</a>.</span><span title=""ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.beta.wmflabs.org%3ACopy-paste6th&amp;rft.btitle=yahoo&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fyahoo.com&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook"" class=""Z3988"" about=""#mwt2"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;}""><span style=""display:none;"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;}""><span typeof=""mw:Entity"" data-parsoid=""{&quot;src&quot;:&quot;&amp;nbsp;&quot;,&quot;srcContent&quot;:&quot;&nbsp;&quot;}"">&nbsp;</span></span></span></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[176,180,0,0]}"">text</p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[182,198,0,0]}""><img class=""tex"" alt=""\pi"" src=""//upload.beta.wmflabs.org/math/5/2/2/522359592d78569a9eac16498aa7a087.png"" typeof=""mw:Extension/math"" data-mw=""{&quot;name&quot;:&quot;math&quot;,&quot;attrs&quot;:{},&quot;body&quot;:{&quot;extsrc&quot;:&quot;\\pi&quot;}}"" data-parsoid=""{&quot;src&quot;:&quot;&lt;math&gt;\\pi&lt;/math&gt;&quot;,&quot;dsr&quot;:[182,198,2,2]}"" about=""#mwt9""></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[200,204,0,0]}"">text</p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[206,222,0,0]}""><img class=""tex"" alt=""\pi"" src=""//upload.beta.wmflabs.org/math/5/2/2/522359592d78569a9eac16498aa7a087.png"" typeof=""mw:Extension/math"" data-mw=""{&quot;name&quot;:&quot;math&quot;,&quot;attrs&quot;:{},&quot;body&quot;:{&quot;extsrc&quot;:&quot;\\pi&quot;}}"" data-parsoid=""{&quot;src&quot;:&quot;&lt;math&gt;\\pi&lt;/math&gt;&quot;,&quot;dsr&quot;:[206,222,2,2]}"" about=""#mwt11""></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[224,277,0,0]}"">text<span class=""citation web"" about=""#mwt5"" typeof=""mw:Transclusion"" data-mw=""{&quot;parts&quot;:[{&quot;template&quot;:{&quot;target&quot;:{&quot;wt&quot;:&quot;Cite web&quot;,&quot;href&quot;:&quot;./Template:Cite_web&quot;},&quot;params&quot;:{&quot;url&quot;:{&quot;wt&quot;:&quot;http://yahoo.com&quot;},&quot;title&quot;:{&quot;wt&quot;:&quot;yahoo&quot;}},&quot;i&quot;:0}}]}"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;,&quot;dsr&quot;:[228,277,null,null],&quot;pi&quot;:[[{&quot;k&quot;:&quot;url&quot;,&quot;named&quot;:true},{&quot;k&quot;:&quot;title&quot;,&quot;named&quot;:true}]]}""><a rel=""mw:ExtLink"" href=""http://yahoo.com"" data-parsoid=""{&quot;targetOff&quot;:45,&quot;contentOffsets&quot;:[45,52],&quot;a&quot;:{&quot;href&quot;:&quot;http://yahoo.com&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;A]]\n\n[[linkB]]\n\n&quot;}}"">""yahoo""</a>.</span><span title=""ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.beta.wmflabs.org%3ACopy-paste6th&amp;rft.btitle=yahoo&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fyahoo.com&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook"" class=""Z3988"" about=""#mwt5"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;}""><span style=""display:none;"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;}""><span typeof=""mw:Entity"" data-parsoid=""{&quot;src&quot;:&quot;&amp;nbsp;&quot;,&quot;srcContent&quot;:&quot;&nbsp;&quot;}"">&nbsp;</span></span></span></p><span typeof=""mw:Transclusion"" data-mw=""{&quot;parts&quot;:[{&quot;template&quot;:{&quot;target&quot;:{&quot;wt&quot;:&quot;Cite web&quot;,&quot;href&quot;:&quot;./Template:Cite_web&quot;},&quot;params&quot;:{&quot;url&quot;:{&quot;wt&quot;:&quot;http://yahoo.com&quot;},&quot;title&quot;:{&quot;wt&quot;:&quot;yahoo&quot;}},&quot;i&quot;:0}}]}"" data-ve-no-generated-contents=""true"" class=""citation web""></span><p></p></body></html>
+page:Copy-paste6th
+oldid:73736
+format:json
+Response Headersview source
+Accept-Ranges:bytes
+Age:0
+Cache-control:private
+Connection:keep-alive
+Content-Encoding:gzip
+Content-Length:97
+Content-Type:application/json; charset=utf-8
+Date:Tue, 07 Jan 2014 01:12:09 GMT
+Server:Apache
+Vary:Accept-Encoding
+Via:1.1 varnish, 1.1 varnish
+X-Cache:deployment-cache-text1 miss (0), deployment-cache-text1 frontend miss (0)
+X-Content-Type-Options:nosniff
+X-Frame-Options:SAMEORIGIN
+X-Powered-By:PHP/5.3.10-1ubuntu3.9+wmf1
+X-Varnish:239733000, 2143990872
+X-Vary-Options:Accept-Encoding;list-contains=gzip",1389057352,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,"Created attachment 14240
+Screenshot of template getting merged with the previous line
+
+**Attached**: {F12624}",1389048178,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,"The original issue described in this bug is not occurring anymore but a similar issue is found not sure if they are related or not.If not, I will file a separate issue:
+
+1.Create a page ""A"" with a template Cite Web
+2.Create another page ""B"" where you will copy the template.
+3.Add some text or any other element like math function/Link to Page ""B""
+4.Copy the CiteWeb template created in page A and paste it into the next line of B
+
+Observed Result:
+The template gets merged with the previous element/line.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Copy-paste6th
+
+See the screenshot attached.",1389048141,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,Can you provide a sample of the relevant HTML your are producing in VE?,1387495467,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+TemplateData: Add property to indicate in which namespaces a template should be used,"**Author:** `prlpz`
+
+**Description:**
+I suggest including in TemplateData a field about the namespaces where the template is intended to be used. VisualEditor should use this field to suggest the template only in the right namespaces.
+
+For example, nowadays VisualEditor suggest using template documentation templates while editing articles, but such templates should only be used in template namespace. TemplateData could make VisualEditor know that those templates shouldn't be suggested there.",1387393320,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cu3bvvy2inqyghkz63xu,task_description,duplicate
+TemplateData: Add property to indicate in which namespaces a template should be used,"@Krinkle, @Jdforrester-WMF: Any thoughts on this one? If we decided this is a good idea, we'd need to figure out which is the best format for users to express the namespaces in.",1452891227,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cu3bvvy2inqyghkz63xu,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Core has a build system to generate HTML from kss-formatted CSS/LESS (docs/kss). It would be nice if this documentation appeared in doc.wikimedia.org along with other generated documentation.
+
+This sounds like T50337. Presumably there's some Zuul job somewhere building the doc that appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1387336620,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_description,declined
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,Old school cc @Volker_E ,1532486031,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,kss is still in core.,1464911476,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,We are no longer using kss in MobileFrontend. It wasn't being maintained due to lack of visibility and shift to OOjs UI.,1464025554,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Seems fine: npm-run-script doc
+
+In Jenkins Job Builder, I have generic templates for python tox and ruby bundler:
+
+'{name}-tox-{toxenv}'
+'{name}-bundle-{bundlecommand}'  https://gerrit.wikimedia.org/r/#/c/160983/
+
+So we can probably come up with a '{name}-npmrunscript-{npmscript}' command which would be realized as:
+
+- project:
+  name: VisualEditor
+  npmscript:
+   - doc
+  jobs:
+   - '{name}-npmrunscript-{npmscript}'
+
+
+And the template would contain:
+
+ npm run-script {npmscript}
+
+Might need to add an 'npm install' before, not sure.",1411573308,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"(In reply to Antoine ""hashar"" Musso from comment #14)
+> > Do you mean Grunt (which runs on node.js)?  That's the node.js build tool
+> > I normally see used.
+> 
+> I guess npm as an entry point for jenkins (i.e. npm test) which would then
+> use grunt to run a wide range of different tests :d
+
+Hmm, thanks.  This is not a test though.
+
+While ""npm test"" exists (https://www.npmjs.org/doc/cli/npm-test.html), ""npm doc"" does not.  There is apparently a way to have custom scripts (https://www.npmjs.org/doc/misc/npm-scripts.html , https://www.npmjs.org/doc/cli/npm-run-script.html), but we would need to standardize on a name (e.g. npm-run-script doc).
+
+Is there such a convention already?",1411530930,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Change 161998 had a related patch set uploaded by Prtksxna:
+kss: Add Gruntfile
+
+https://gerrit.wikimedia.org/r/161998",1411409150,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"> Do you mean Grunt (which runs on node.js)?  That's the node.js build tool
+> I normally see used.
+
+I guess npm as an entry point for jenkins (i.e. npm test) which would then use grunt to run a wide range of different tests :d",1411372542,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"(In reply to Antoine ""hashar"" Musso from comment #11)
+> Can you reach out to Timo about it?  I think for Javascript purposes he
+> would like developers to define npm entry points.  So we would simply invoke
+> 'npm doc' or something and publish whatever is generated under a given dir
+> (ex: /doc/).
+
+Do you mean Grunt (which runs on node.js)?  That's the node.js build tool I normally see used.",1411185072,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,Timo is in the office this week.. Maybe you could grab him S?,1411152851,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Can you reach out to Timo about it?  I think for Javascript purposes he would like developers to define npm entry points.  So we would simply invoke 'npm doc' or something and publish whatever is generated under a given dir (ex: /doc/).
+
+That would let you define whatever you want to run to build documentation which is much more scalable than having to handle defines in jenkins.",1411138490,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,yardoc is now being used and Jenkins is populating https://doc.wikimedia.org/rubygems/mediawiki-ruby-api/ and https://doc.wikimedia.org/rubygems/mediawiki-selenium/ .  So that's something to study when implementing this.,1411083312,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"In the interim, `ssh tools-login.wmflabs.org; become styleguide` is generating http://tools.wmflabs.org/styleguide/ in a cron job. I don't understand misc.yaml, mediawiki.yaml, zuul-config/layout.yaml enough to work on this.",1411077493,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,*** Bug 64221 has been marked as a duplicate of this bug. ***,1400706420,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Since mss is a node module, we could have it added to the integration/jenkins.git repository which has tools/package.json. It currently provides:
+
+ {
+	""name"": ""wikimedia-integration-jenkins"",
+	""version"": ""0.2.5"",
+	""dependencies"": {
+		""grunt"": ""0.4.1"",
+		""grunt-cli"": ""0.1.13"",
+		""grunt-contrib-qunit"": ""0.4.0"",
+		""phantomjs"": ""~1.9.0-1"",
+		""grunt-contrib-csslint"": ""0.2.0"",
+		""jshint"": ""2.4.4""
+	}
+ }
+
+So maybe add kss in there and forget about git-deploy and integration/kss.",1399032201,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,Pending upload of kss in integration/kss.git so we can get it deployed on Jenkins slaves.  Then we need some script to generate the doc and move the generated doc under the doc website.,1393241708,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Change 103095 merged by Alexandros Kosiaris:
+Add integration/kss to deployment repo config
+
+https://gerrit.wikimedia.org/r/103095",1388491753,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,I have created a .gitreview file for integration/kss.git repository so we can add it in the deployment system.,1388491699,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Change 103095 had a related patch set uploaded by Spage:
+Add integration/kss to deployment repo config
+
+https://gerrit.wikimedia.org/r/103095",1387626505,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Target url should indeed me something like one of these this:
+
+
+https://doc.wikimedia.org/mediawiki-core/master/less/
+https://doc.wikimedia.org/mediawiki-core/master/css/
+https://doc.wikimedia.org/mediawiki-core/master/style-guide/css/
+
+Preferences, anyone?
+
+(where master can also be REL1_22, and in the future tags like 1.23.0)
+
+With a shortcut from the https://doc.wikimedia.org/ home page, of course.
+
+PS: I'm planning on renaming /mediawiki-core to /mediawiki at some point (with redirects and symlinks of course).",1387430906,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"S, as a first step we need a way to deploy kss on the Jenkins slave.
+
+It seems that is a nodejs application so I guess we want to use our own repository that would provide kss and ALL the required modules.  We did such a thing to provide ruby bundler (integration/bundler.git) and phpunit (integration/phpunit.git).
+
+Could you take care of having an integration/kss.git repository created and upload there the kss + its npm modules ?
+
+
+Once done, register that repository in git-deploy configuration. That is done in operations/puppet.git under manifests/role/deployment.pp.  The deployment would then be done from tin.eqiad.wmnet.
+
+
+Then, we need a shell script wrapper that would execute the script (deployed somewhere under /srv/deployment/integration/kss ).  https://doc.wikimedia.org/ document root is under /srv/org/wikimedia/doc/  the following sub directories are usually: <project-name> / <branch> / <doc component>.  Example:
+
+ /srv/org/wikimedia/doc/mediawiki-core/REL1_22/js
+
+
+So I guess you would want to have kss generate the doc to  /srv/org/wikimedia/doc/mediawiki-core/master/css
+
+
+Once done, we need a new job-template in Jenkins Job Builder configuration, apply it to mediawiki/core project.  The job will need to be added in Zuul configuration (integration/zuul-config.git) in the postmerge pipeline.",1387357961,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"This causes the test 'document with meta elements: data' in ve.dm.MWConverter to fail. Not sure if it is any more serious than that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387307700,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-irztrimblav2ughjnygh,task_description,open
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"Is this still a problem? I don't see any such test failing, at least.",1574099357,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"(In reply to comment #3)
+> (In reply to comment #0)
+> > This causes the test 'document with meta elements: data' in ve.dm.MWConverter
+> > to fail. Not sure if it is any more serious than that.
+> 
+> Are you comparing a HTML serialization or the DOM attribute? A diff in the
+> former is fine, but a diff in the latter would be a bug.
+
+Actually, a diff in the *percent-decoded* DOM href attribute would be a bug.
+
+We decode all hrefs in the serializer, so to us it makes no difference if it is encoded as %20 or a literal space in HTML.",1387572712,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"(In reply to comment #0)
+> This causes the test 'document with meta elements: data' in ve.dm.MWConverter
+> to fail. Not sure if it is any more serious than that.
+
+Are you comparing a HTML serialization or the DOM attribute? A diff in the former is fine, but a diff in the latter would be a bug.",1387563203,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"(In reply to comment #1)
+> A space is not a valid character in an URL, it must always be
+> percent-encoded.
+> https://en.wikipedia.org/wiki/URL#List_of_allowed_URL_characters
+
+Are we talking about HTTP or HTML here? If it is HTML, then I'd suggest looking at the relevant HTML5 spec.",1387559561,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"A space is not a valid character in an URL, it must always be percent-encoded. https://en.wikipedia.org/wiki/URL#List_of_allowed_URL_characters",1387309200,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+Cut and Paste of references occasionally fails,"Occasionally, cut and paste of text that includes a reference will fail in a weird way. I was able to isolate one reproducible case: 
+
+1. The article contains text S, followed by a reference for S, some more text T, followed by a reference for T.
+
+2. We cut (Ctrl-X) part or all of text T, including its reference.
+
+3. We paste (Ctrl-V) somewhere in the middle of text S (*not* at the beginning of S)
+
+Result: the article view is scrolled to the top, the pasted text is in wrong order, all of a sudden we have three references.
+
+See https://www.mediawiki.org/wiki/VisualEditor:TestAxelBoldt#Regression_15:_Cut.2FPaste_of_references for a sandbox where you can try it out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387229820,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-yqdyvohgcbxzehgnpq4g,task_description,resolved
+Cut and Paste of references occasionally fails,I can't reproduce either.,1436503691,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-yqdyvohgcbxzehgnpq4g,task_subcomment,NA
+Cut and Paste of references occasionally fails,"I tired it on the page where the original test is placed- https://www.mediawiki.org/wiki/VisualEditor:TestAxelBoldt?veaction=edit#Regression_15%253A_Cut.2FPaste_of_references
+
+- no scroll-up when pasting the text
+- the text pasted correctly",1419351940,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-yqdyvohgcbxzehgnpq4g,task_subcomment,NA
+Cut and Paste of references occasionally fails,Can't reproduce anymore.,1419350787,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yqdyvohgcbxzehgnpq4g,task_subcomment,NA
+Enable VisualEditor in the Reports namespace on officewiki,"Per Guillaume's request on IRC. This is namespace 100.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1387226280,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-d7gosdnm6wposiphhgbw,task_description,resolved
+Enable VisualEditor in the Reports namespace on officewiki,Now done.,1387324738,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d7gosdnm6wposiphhgbw,task_subcomment,NA
+Enable VisualEditor in the Reports namespace on officewiki,"Change 101908 merged by Reedy:
+Make officewiki's Report: namespace VE-enabled
+
+https://gerrit.wikimedia.org/r/101908",1387315187,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d7gosdnm6wposiphhgbw,task_subcomment,NA
+Enable VisualEditor in the Reports namespace on officewiki,\o/ Thanks :),1387305647,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-d7gosdnm6wposiphhgbw,task_subcomment,NA
+Enable VisualEditor in the Reports namespace on officewiki,"Change 101908 had a related patch set uploaded by Jforrester:
+Make officewiki's Report: namespace VE-enabled
+
+https://gerrit.wikimedia.org/r/101908",1387226388,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d7gosdnm6wposiphhgbw,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Steps to reproduce:
+
+1.Open the editor.
+2.Add a template
+3.Save the page
+4.Reopen the editor
+5.Copy the template 
+
+Observed Result:
+
+It gives an error:Uncaught TypeError: Cannot convert null to object .However, it does get pasted correctly onto other VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386890940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7g7uyqfy56h27dadb2t4,task_description,resolved
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Verified the fix in test2 with MediaWiki 1.23wmf8 on page:
+https://test2.wikipedia.org/wiki/19th_december",1387484794,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/The_destination_template,1386993261,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Change 101148 merged by jenkins-bot:
+Check values property exists before removing attribute
+
+https://gerrit.wikimedia.org/r/101148",1386963584,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"For betalabs, I could reproduce for only templates which has parameters with values",1386896635,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Change 101148 had a related patch set uploaded by Esanders:
+Check values property exists before remove attribute
+
+https://gerrit.wikimedia.org/r/101148",1386893250,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,Can you reproduce on beta labs?,1386892999,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Created attachment 14077
+screenshot
+
+**Attached**: {F12097}",1386891161,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Test Environment: production-https://en.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5",1386891103,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: The active template sprite stays at the same place when a window is resized,"To reproduce:
+
+1. Edit a page with a template.
+2. Click the template so the darker blue sprite appears.
+3. Resize the window.
+
+Observed: The transparent blue sprite stays at the same place on the screen.
+
+Expected: The transparent blue sprite should move to the new location of the template of the screen.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386863460,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-3ysx7zhkex33mtvcwvjv,task_description,resolved
+VisualEditor: The active template sprite stays at the same place when a window is resized,This is now fixed.,1394223139,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ysx7zhkex33mtvcwvjv,task_subcomment,NA
+"VisualEditor: <visualeditor-toolbar-insert> is showing up in the toolbar instead of ""Insert"" in betalabs","screenshot
+
+<visualeditor-toolbar-insert> is showing up in the toolbar instead of More in betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11989}",1386806520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yj26bqg27rohxa63lh2v,task_description,resolved
+"VisualEditor: <visualeditor-toolbar-insert> is showing up in the toolbar instead of ""Insert"" in betalabs",verified on test2:https://test2.wikipedia.org/w/index.php?title=13th_december&veaction=edit,1386982882,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yj26bqg27rohxa63lh2v,task_subcomment,NA
+"VisualEditor: <visualeditor-toolbar-insert> is showing up in the toolbar instead of ""Insert"" in betalabs",Verified in Betalabs,1386824971,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-yj26bqg27rohxa63lh2v,task_subcomment,NA
+"VisualEditor: <visualeditor-toolbar-insert> is showing up in the toolbar instead of ""Insert"" in betalabs",This is now fixed in betalabs after we caused the English messages to get re-synched.,1386821225,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yj26bqg27rohxa63lh2v,task_subcomment,NA
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion","The following pages all exist on en.wikipedia.org:
+
+* [[Bird]]
+* [[Big]]
+* [[Big!]]
+* [[Big Ten Conference]]
+
+When querying action=opensearch for:
+
+* ""Bir"": 0 => ""Bird""
+   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Bir
+   [input,[""Bird"",""Birmingham"",..]]
+
+* ""Bird"": 0 => ""Bird""
+   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Bird
+   [input,[""Bird"",""BirdLife International"",..]]
+
+* ""Big"": 
+   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Big
+   [""Big"",[""Big Ten Conference"",""Big band"",...]]
+
+* ""Big"": 
+   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Big!
+   [""Big!"",[""Big Ten Conference"",""Big band"",...]]
+
+In the last two, ""Big"" and ""Big!"" are nowhere in the response.
+
+Filing against Wikimedia for now, because this seems related to one of our search backends, not plain MediaWiki core or plain MediaWiki core with Extension:TitleKey installed.
+
+This is currently causing issues in VisualEditor when making a link to a page called ""Big"", or ""Big!"" as it will think the page doesn't exist and suggest to make a red link, as, thus far, we've always assumed that if a page by the exact title exists, it should be the first suggestion.
+
+It normalising casing and/or special characters is fine, but shouldn't make it not give an exact match as first result.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**Whiteboard**: cirrus-fixed",1386736380,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_description,resolved
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion",This issue is now fixed.,1478802678,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_subcomment,NA
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion","Some good news, at least.  Cirrus does what you'd expect.  If you have a page named ""Big!"" and type ""Big!"" into the search box it'll return Big! as the suggestion.",1386774325,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_subcomment,NA
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion","I'm pretty sure 'OpenSearchXml' is not the right component. Also, cc-ing search people.",1386773876,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_subcomment,NA
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion","VisualEditor screenshots:
+
+- Big! http://cl.ly/image/3U3V1h1B3i0r
+- Big  http://cl.ly/image/193c290i1X0z",1386736491,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/w/index.php?title=Toronto_Maple_Leafs&diff=585067098&oldid=584791615",1386701940,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-abahz4qyzn3wpoxxwffa,task_description,duplicate
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",Last report a year ago; presumably this was a Parsoid issue that was since fixed?,1429611978,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","No steps to reproduce; no-one managed to reproduce; no new known occurrences for nearly a year. Setting status to STALLED.
+
+>>! In T60282#642603, @Whatamidoing-WMF wrote:
+> I'll ask the user who encountered this one:
+
+The reply of that user was ""I am using Mozilla Firefox on a Dell Inspiron One desktop computer.""",1426770504,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",Thanks!,1397773016,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","It happened yesterday:
+
+https://en.wikipedia.org/w/index.php?title=IPhone&curid=8841749&diff=604427150&oldid=604113181
+
+I'll ask the user who encountered this one:
+
+https://en.wikipedia.org/w/index.php?title=Michael_Jackson&curid=14995351&diff=603943260&oldid=603918451
+
+since she's pretty active.",1397772982,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","I can't reproduce this in Chrome, Safari, Opera or Firefox. Is it possible that this is a browser plug-in or a very odd browser corruption?",1397761334,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Here's another:  
+
+https://en.wikipedia.org/w/index.php?title=Fandango_%28wrestler%29&curid=21330399&diff=602066359&oldid=601951852
+
+This one broke over ""&quot;""",1396282951,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Here's another:
+
+https://en.wikipedia.org/w/index.php?title=The_National_%28band%29&curid=2308112&diff=600606533&oldid=600023816
+
+This time, the ref name contained a template:  <ref name=""{{BillboardURLbyName|artist=the national|chart=Billboard 200}}"">
+
+Like most of the others, this is probably the result of a sloppy script.",1395856532,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Other example on frwiki https://fr.wikipedia.org/w/index.php?title=Salon_international_de_l%27agriculture&curid=205829&diff=101773303&oldid=101729054
+
+Apparently, the user didn't even modify the chapter where the problem occurs.",1393949199,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",According to https://en.wikipedia.org/w/index.php?title=Colours_in_the_Dark_%28album%29&curid=39317223&diff=595492480&oldid=593715294 it appears that this happens on HTML codes for things other than non-breaking spaces.  #124 is a vertical bar.,1392491240,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Another diff, this time involving a {{nowrap}} template:  https://en.wikipedia.org/w/index.php?title=Michael_Jackson&curid=14995351&diff=595247974&oldid=595208734
+
+This only seems to affect nbsp's that are present in ref names (where they probably oughtn't be anyway).",1392333395,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",Another report of this: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=590211100&oldid=590159444,1389446531,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",This also affects vertical bars ( &#124; ) as seen at ttps://en.wikipedia.org/w/index.php?title=Paper_Planes&diff=585505452&oldid=581736416,1386881945,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"We're seeing more and more JSON files entering our repos, and there is an RfC in discussion[1] to move to JSON files for our localisation.
+
+Please add standard JSON linting when patch sets that have Jenkins jobs configured.
+
+[1] https://www.mediawiki.org/wiki/Requests_for_comment/Localisation_format
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major",1386696900,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-op7hsmyyqri3qvye5pcj,task_description,resolved
+Jenkins: Add a lint job for JSON,"Whether ideal for the long term or not, it was resolved by Antoine by including it in the jslint job.
+
+For the long term, projects should include a jsonlint task in their own test pipeline.
+
+For localisation json files in particular, see T66045#962750.",1420726011,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Whether ideal for the long term or not, it was resolved by Antoine by including it in the jslint job.
+
+For the long term, projects should include a jsonlint task in their own test pipeline.",1420725969,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to Bawolff (Brian Wolff) from comment #26)
+> (In reply to Bawolff (Brian Wolff) from comment #25)
+> > Re-opening. I just managed to submit a patch (
+> > https://gerrit.wikimedia.org/r/#/c/147754/ ) with a rather stupid json
+> > error, and jenkins did not complain.
+> 
+> Its been pointed out to me that the jslint job (which is non-voting on
+> TimedMediaHandler) is what verifies json files (Although
+> https://integration.wikimedia.org/ci/job/mwext-TimedMediaHandler-jslint/497/
+> consoleText doesn't seem to say anything about an i18n file failing). I'd
+> like to suggest that the job be split. As missing a coding convention and a
+> fatal error are rather different types of issues.
+
+I agree it shouldn't be part of the jslint job. But I don't think we should change that for the time being. The jslint job in general is an older one that is being phased out by having projects adopt Grunt instead. Where they can add jshint, jscs, banana-checker, and (if they have non-i18n json files) json-lint to their pipeline.
+
+TMH repo should be updated by adding the appropriate jshint config and ignores so that their non-voting exemption may be lifted. Because right now, obvious syntax errors in javascript files aren't caught, either. Which is just as important as json syntax errors.",1416447458,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to Bawolff (Brian Wolff) from comment #25)
+> Re-opening. I just managed to submit a patch (
+> https://gerrit.wikimedia.org/r/#/c/147754/ ) with a rather stupid json
+> error, and jenkins did not complain.
+
+Its been pointed out to me that the jslint job (which is non-voting on TimedMediaHandler) is what verifies json files (Although https://integration.wikimedia.org/ci/job/mwext-TimedMediaHandler-jslint/497/consoleText doesn't seem to say anything about an i18n file failing). I'd like to suggest that the job be split. As missing a coding convention and a fatal error are rather different types of issues.",1406487694,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Re-opening. I just managed to submit a patch ( https://gerrit.wikimedia.org/r/#/c/147754/ ) with a rather stupid json error, and jenkins did not complain.",1406486678,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,All 275 jobs updated.,1396269337,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 113958 merged by jenkins-bot:
+Add json-lint.php command to -jslint jobs
+
+https://gerrit.wikimedia.org/r/113958",1396267695,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,I forgot to deploy https://gerrit.wikimedia.org/r/#/c/113958/ last monday. Updating jobs now.,1396266829,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to Nemo from comment #19)
+> > Will be done next Monday: March 17th.
+> 
+> Was it?
+
+Seems not.
+
+Setting severity from Siebrand's duplicate.",1396254075,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,*** Bug 63293 has been marked as a duplicate of this bug. ***,1396253986,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to Antoine ""hashar"" Musso from comment #18)
+> Mailled wikitech-l about it
+> http://lists.wikimedia.org/pipermail/wikitech-l/2014-March/075092.html
+> 
+> Will be done next Monday: March 17th.
+
+Was it? Another example: https://gerrit.wikimedia.org/r/#/c/121910/
+All extensions should have JSON files checked for validity (locally I use a simple json_verify < $FILE.json ).",1396088633,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Mailled wikitech-l about it http://lists.wikimedia.org/pipermail/wikitech-l/2014-March/075092.html
+
+Will be done next Monday: March 17th.",1394468825,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 114464 merged by jenkins-bot:
+json syntax error with escaped single quotes
+
+https://gerrit.wikimedia.org/r/114464",1392909530,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 114464 had a related patch set uploaded by Hashar:
+json syntax error with escaped single quotes
+
+https://gerrit.wikimedia.org/r/114464",1392906623,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"I have run the json linter on all extensions and three files are not understood by PHP json_decode() :-(
+
+hashar@gallium:~/extensions$ /srv/deployment/integration/slave-scripts/bin/json-lint.php .
+./TemplateData/spec.templatedata.json: json decode error.
+./VisualEditor/modules/ve-mw/i18n/qqq.json: json decode error.
+./VisualEditor/modules/syntaxhighlight/rules/mysql.json: json decode error.
+hashar@gallium:~/extensions$",1392904903,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 113958 had a related patch set uploaded by Hashar:
+Add json-lint.php command to -jslint jobs
+
+https://gerrit.wikimedia.org/r/113958",1392734924,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 107163 merged by jenkins-bot:
+json-lint.php: recursively lint json files with PHP
+
+https://gerrit.wikimedia.org/r/107163",1390853068,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to comment #11)
+> Have you verified that it warns for double quotes in *.json files as well?
+
+Yes I did (comment #4) which prompted me to repurpose this bug in writing a wrapper around PHP json_decode() which I did in Gerrit change #107163.
+
+I guess jshint would have the same issue with trailing comma in arrays (none in json) or keys having to be enclosed by quotes.",1389643526,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to comment #4)
+> json files requires double quotes which jshint complains about. So I guess we
+> need a different job that would use jshint with a specific configuration.
+
+Have you verified that it warns for double quotes in *.json files as well?
+
+I don't think JSHint will parse json files exactly the same as js files, even if explicitly told to via ` --extra-ext json` because a plain JSON object is not a valid JS statement.
+
+Meaning, if you feed { ""foo"": ""bar"" } to a javascript parser as a statement, it will not be an object (it will be a block statement with a label foo and a statement with an unassigned string ""bar"").
+
+As such, using jshint to parse json files would either be
+1) pointless, as it would be validated as javascript instead of json, likely causing all kinds of false positives not even related to coding or quoting style
+
+or 2) JSHint recognises it as a JSON file and therefore one would expect it to not warn for double quotes.",1389629338,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 107163 had a related patch set uploaded by Krinkle:
+json-lint.php: recursively lint json files with PHP
+
+https://gerrit.wikimedia.org/r/107163",1389629045,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 107163 had a related patch set uploaded by Hashar:
+json-lint.php: recursively lint json files with PHP
+
+https://gerrit.wikimedia.org/r/107163",1389627596,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"I guess one can write a basic lint script that would wrap around PHP json_decode() ?   If we can decode it, I guess we are safe :]",1389359970,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"I have an example of invalid JSON that got merged, and caused issues in the L10n process:
+
+Line 215 of https://gerrit.wikimedia.org/r/#/c/106460/1/data/i18n/qqq.json has a trailing comma that, when a JSON linter is there, should have blocked the merge of that patch set.",1389359446,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to comment #5)
+> (In reply to comment #4)
+> > json files requires double quotes which jshint complains about. So
+> > I guess we need a different job that would use jshint with a specific
+> > configuration.
+> 
+> If we're using JSON, we might as well do it right, so I guess those
+> complaints
+> are justified?
+
+Oh, wait. Yes, of course, Antoine :).",1389004291,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to comment #4)
+> json files requires double quotes which jshint complains about. So I guess we
+> need a different job that would use jshint with a specific configuration.
+
+If we're using JSON, we might as well do it right, so I guess those complaints are justified?",1389004257,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,json files requires double quotes which jshint complains about. So I guess we need a different job that would use jshint with a specific configuration.,1389003947,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"The jslint job is already present for extension and is triggered by Zuul whenever a .jshint*, *.js or *.json file is modified.
+
+A culprit is that by default jshint does not parse .json files, so we want to instruct it to parse such files using:
+
+ jshint --extra-ext json .",1389003835,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,Any updates on this yet?,1389002205,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,Timo thoughts?  Should we incorporate that in the jslint job that runs jshint ?,1386697332,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+VisualEditor: Make the media dialog one dialog again,"Merge MWMediaInsertDialog and MWMediaEditDialog into one dialog that has an insert page and an edit page, and a BookletLayout without an outline. This way we can switch between modes without closing one dialog and opening another.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1386638100,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-o26zcq73b7wls4nly65z,task_description,resolved
+VisualEditor: Make the media dialog one dialog again,"
+
+*** This bug has been marked as a duplicate of bug 67170 ***",1412590279,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-o26zcq73b7wls4nly65z,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Toolserver has a limited and anonimized view of the user_properties table available. This is used for reports like https://en.wikipedia.org/wiki/Wikipedia:Database_reports/User_preferences
+
+mysql> describe user_properties;
+| Field       | Type           | Null | Key | Default | Extra |
+| -----  | -----  | -----   | ----- | ----- | ----- |
+| up_user     | int(11)        | NO   |     | 0       |       |
+| up_property | varbinary(255) | YES  |     | NULL    |       |
+| up_value    | blob           | YES  |     | NULL    |       |
+3 rows in set (0.00 sec)
+
+mysql> describe user_properties_anonym;
+| Field                   | Type           | Null | Key | Default | Extra |
+| -----  | -----  | -----   | ----- | ----- | ----- |
+| up_property             | varbinary(255) | YES  |     | NULL    |       |
+| up_value                | blob           | YES  |     | NULL    |       |
+| ts_user_touched_cropped | varbinary(8)   | NO   |     |         |       |
+3 rows in set (0.00 sec)
+
+Only preferences that are considered to be public are replicated, the list from enwiki_p is:
+mysql> select distinct(up_property) from user_properties;
+| up_property    |
+| -----  |
+| disablemail    |
+| fancysig       |
+| gender         |
+| language       |
+| nickname       |
+| skin           |
+| timecorrection |
+| variant        |
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+* {T27302}
+* {T21288}",1386566220,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_description,resolved
+Tool Labs: Provide anonymized view of the user_properties table,The underlying data has been backfilled.,1448850365,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Re-opening since the `user_properties_anon` table is still missing the `upa_touched` timestamp field (per @coren earlier's comment, this is blocked on T92841).
+",1442982359,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Re-opening since the `user_properties_anon` table is still missing the `upa_touched` field (per @coren earlier's comment, this is blocked on T92841).
+",1442982341,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"T66115 has been resolved, but `user_properties_anon` isn't working properly yet since `upa_touched` is null everywhere. (Depends on T92841).
+
+Due to the lack of this column, utility queries previously common on Toolserver like ""How many active users are using gadget X"" are not possible. And essential queries for gadget maintainers when making decisions about deprecated gadgets being replaced, etc.
+
+Now we get shell requests for these (or over IRC) and run them in production. But it'd be better if people can run these themselves in labs or via Quarry.",1442981844,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"T66115 has been resolved, but `user_properties_anon` isn't working properly yet since `upa_touched` is null everywhere. (Depends on T92841).
+
+Previously common utility queries like ""How many active users are using Cologne Blue"" are not possible yet. And essential queries for gadget maintainers when making decisions about deprecated gadgets being replaced.
+
+Now we get shell requests for these (or over IRC). But it'd be better if they can run those themselves.",1434502044,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"The view exists, and is working.  Whitelisting other properties is fairly easy, but requests for this should be made in separate tasks.",1427309623,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#1123999, @Ricordisamoa wrote:
+> AFAICS, and as noted in this task's description, the user_properties table already contains ""preferences that are considered to be public"", such as the ones you mentioned.
+> 
+> Just tried:
+> ```lang=sql
+> SELECT up_value FROM user_properties INNER JOIN user ON user_id = up_user AND user_name = 'Ricordisamoa' AND up_property = 'gender';
+> ```
+
+Huh, fair play. I guess most of this database report got fixed with the resolution of {T66115}.",1426556503,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#1123825, @MZMcBride wrote:
+> Thank you for <https://gerrit.wikimedia.org/r/197055>!
+> 
+> Looking at <https://en.wikipedia.org/wiki/Wikipedia:Database_reports/User_preferences/Configuration>, it looks like ""gender"", ""language"", and ""skin"" would be the easiest targets next. If anyone would prefer to close this task as resolved and file new tasks for additions to the whitelisted user properties list, I'm fine with that.
+
+AFAICS, and as noted in this task's description, the user_properties table already contains ""preferences that are considered to be public"", such as the ones you mentioned.
+
+Just tried:
+```lang=sql
+SELECT up_value FROM user_properties INNER JOIN user ON user_id = up_user AND user_name = 'Ricordisamoa' AND up_property = 'gender';
+```",1426553237,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"It was `user_properties_anonym` on the Toolserver and it's `user_properties_anon` now. Probably doesn't really matter, just noting.
+
+Thank you for <https://gerrit.wikimedia.org/r/197055>!
+
+Looking at <https://en.wikipedia.org/wiki/Wikipedia:Database_reports/User_preferences/Configuration>, it looks like ""gender"", ""language"", and ""skin"" would be the easiest targets next. If anyone would prefer to close this task as resolved and file new tasks for additions to the whitelisted user properties list, I'm fine with that.",1426549384,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Change 197055 merged by coren:
+Update maintain-replicas
+
+[[https://gerrit.wikimedia.org/r/197055]]",1426519887,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"The view has been created (on all but size 1 wikis) but the timestamps currently return NULL because none of the user_touched values are on the replicas at this time (they are redundantly nulled during replication and in the views).
+",1426519618,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Change 197055 had a related patch set uploaded (by coren):
+Update maintain-replicas
+
+[[https://gerrit.wikimedia.org/r/197055]]
+",1426519411,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#1120423, @MZMcBride wrote:
+> Can we start with ""gadget-*"" and then decide on the others in a separate future task?
+
+Sounds like a reasonable first pass.  I'll have to do some testing to see if wildcard matching is sufficiently efficient for the view to be usable; but otherwise I'll collect the existing gadget- names and use those as our first whitelist.",1426511590,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#1109452, @coren wrote:
+> The one thing I am missing to implement this at this time is either
+> (a) the whitelist of properties to collate or
+> (b) the method by which that whitelist is generated.
+
+Can we start with ""gadget-*"" and then decide on the others in a separate future task?",1426468431,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"The one thing I am missing to implement this at this time is either
+(a) the whitelist of properties to collate or
+(b) the method by which that whitelist is generated.
+",1426083857,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"A brief summary of past discussion and verification that we understood each other.
+
+A database view with a whitelisted set of keys is available with connections to individual accounts (`fancysig`, `language`, `nickname`, `timecorrection`, etc.). This information is already available by other means and is provided as convenience to perform queries on. This database view has since been created!
+
+An anonymised database view will be created as follows:
+* `up_user`: omit. This view will not associate preferences with users.
+* `up_property`: included. As was Toolserver, the set of properties exposed may be quite large and controlled by a whitelist (to avoid exposing new sensitive properties by accident). The whitelist includes wildcard patterns for things like `gadget-*`.
+* `up_value`: included.
+* `_user_touched_cropped`: generated based on `user.user_touched` value where `user.user_id = up_user`. Trimmed to YYYY-MM. Values for the current month are displayed as last month's.
+
+
+The reason the current month is displayed as last month's is to reduce chances of identifying users via their activity at the start of a month (which is not limited by the size of a wiki). This because using timestamps of YYYY-MD essentially reset every month. This in contrary to Special:ActiveUsers, which rolls continuously using relative timespan of ""last 30 days"". Without this modification, one could link a recently active user on a wiki at the start of a month. This modification would extend that timeframe from mere seconds to two full months (a user would have to be the only one active for two months). Note that this is for a timespan for two months, not one. Is that acceptable or should be still disable this view on small wikis? (Toolserver had it enabled for all wikis.)",1419127106,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"There are, in essence, two steps.  The underlying table needs to be replicated, and a view need to be created to it.
+
+Access to the underlying table is already there (it is used to provide the view into limited number of keys); all that is needed is the creation of a new view that carefully aggregates the data and respects the size limits, etc.
+
+The script that creates the views is there:
+
+https://git.wikimedia.org/blob/operations%2Fsoftware/HEAD/maintain-replicas%2Fmaintain-replicas.pl
+
+I'm usually the one who creates views, but my schedule is a bit on the buried side.  I'd be happy to review a patch adding the view - look starting line 90, it should be fairly evident how to add one.
+",1418343424,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#630652, @LuisV_WMF wrote:
+> If the users are OK with the month-filtered view, and exclusion of small wikis, that seems like a workable compromise to me.
+
+Okay, this sounds like sign-off to me.
+
+Who does this typically? @coren or @Springle? Is there documentation for what's needed to add/remove a database table or column from Labs' views? I vaguely remember there now being two filters in place, maybe.
+
+If anyone has links to the code repos or documentation (or even another task where we did something similar), that would likely help move this forward. At this point, it sounds like there's general consensus to move forward, this just hasn't been written out and gone through Gerrit/code review.",1418341468,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #51)
+> If the users are OK with the month-filtered view, and exclusion of small
+> wikis, that seems like a workable compromise to me.
+
+Well to speed up the process and keep compatibility at the same time, it would be better to add the view now, with YYYYMMDD rewritten as YYYYMM01 on larger wikis, and as 19700101 on small wikis, and we can keep discussing afterwards...",1402676577,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"If the users are OK with the month-filtered view, and exclusion of small wikis, that seems like a workable compromise to me.",1402600465,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Silke Meyer (WMDE) from comment #49)
+> * As far as we know, ""live"" tools depended on #64115 (filtered view) which
+> has been resolved. But no live tools seem to depend on this one. Please
+> correct me, if I am wrong!
+
+http://toolserver.org/~liangent/gadget_usage/",1402560424,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Summary of what was discussed during office hour (https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-office/20140611.txt, from [17:17:25] on):
+
+* This will probably take longer for WMF Legal, so it's unlikely that it will be done before Toolserver shutdown.
+* As far as we know, ""live"" tools depended on #64115 (filtered view) which has been resolved. But no live tools seem to depend on this one. Please correct me, if I am wrong!
+
+Still, it would be interesting to get an update from Luis. :)",1402557988,PHID-USER-qqgzlefcbycpok45pchr,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Hi Luis, do the comments 46 and 47 provide the answers you need? If not, who can help? We are ... sort of in a hurry by now.",1402504494,PHID-USER-qqgzlefcbycpok45pchr,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Active editors are not the only users changing preferences on a wiki, there are also many global users changing preferences everywhere (or in many places); only user_touched knows that.",1401947943,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Hi Luis, thanks for the update.
+
+(In reply to Krinkle from comment #40)
+> 
+> To avoid strange statistical variance like that, I'd recommend making
+> timestamp of the currently running month appear as last month's. That way no
+> data is excluded. This seems like a simple enough variance that tools should
+> be able to work with without much hassle.
+
+I think it is good solution. The timestamp is used mainly for filtering active vs non-active users.
+
+
+(In reply to Luis Villa (WMF Legal) from comment #42)
+> (In reply to Tisza Gergő from comment #35)
+> > Maybe instead of a live view, this table could be generated by a query which
+> > runs at the end of the day; that way no information is leaked by the timing
+> > of the change. Although that still does not solve the issue for small wikis
+> > since we probably want to run it more often than once a month.
+> 
+> If we only provide one month granularity in the answer, then it can be run
+> only once a month, right? Sounds like the use cases here don't need
+> precise/fine-grained answers to this question?
+
+*My use case: the user_properties_anonym table is used for generating[[meta:Gadgets]] - statistics on the most popular gadgets accross Wikimedia projects.
+* (other example for use case) User preferences statistics are provided by MZMcBride in [[en:Wikipedia:Database reports/User preferences]]
+So I belive one month resolution is fine for statistics use cases, and running it once a month could be enougth.
+As Krinkle wrote above, month resolution (YYYY-MM) make it hard to associate it to specific user.
+
+
+However for very very small wikis I think it isn't possible to provide such statistics: refering to http://stats.wikimedia.org/EN/TablesWikipediansEditsGt5.htm (Wikipedias by active users) some languages such as Tsonga or Oromo have only one active user. I think there should be a threshold on the number of active users in a wiki.",1401919915,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Current status of the bug is ""questions have been posed about privacy concerns"". It would be helpful to have feedback from people who use the field; in particular, my question in comment 42 and response to Krinkle's last statement in comment 40 would be good.",1401906930,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Changing to major per previous comment.,1401888473,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"What is the current status of the bug?
+It becomes very importantly to fix it in the very soon future, as the toolserver is going to be down in 3 weeks
+
+http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2014-June/000722.html",1401882015,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Tisza Gergő from comment #35)
+> Maybe instead of a live view, this table could be generated by a query which
+> runs at the end of the day; that way no information is leaked by the timing
+> of the change. Although that still does not solve the issue for small wikis
+> since we probably want to run it more often than once a month.
+
+If we only provide one month granularity in the answer, then it can be run only once a month, right? Sounds like the use cases here don't need precise/fine-grained answers to this question?",1399486602,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"> To avoid strange statistical variance like that, I'd recommend making timestamp of the currently running month appear as last month's.
+
+I don't see how that would help (other than making the window of opportunity smaller). You could still poll the data on the first day of the month to get an accurate edit timestamp. Since the attack is based on reading *when* the timestamp changes and correlating that with edit times, *what* the timestamp changes to is irrelevant. If you want users of the table to have a precision of T, you could protect users who edit more often than T by setting the timestamps to some deterministically chosen point within T so that changes within that interval are suppressed, but information would still leak about users who edit less often. For T = 1 day, that's hardly acceptable, even on large wikis.
+
+We could randomize the last few bits of the date, that would make it hard to tell when it changes, but it would still be doable via statistical means... really the only reliable way to mitigate this is to use a temporary table instead of a view, and only update it once a day/week/whatever so that the timing of the field changing becomes completely disconnected from the timing of the edit.",1399262606,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Tim Landscheidt from comment #39)
+> (In reply to Krinkle from comment #38)
+> > [...]
+> 
+> > In theory this could still be exploited by being a patient person and
+> > waiting for the moment one month has ended. Then the first user to become
+> > active in the new month would be the only person with a newer month
+> > timestamp.
+> 
+> > [...]
+> 
+> Could this be mitigated by excluding data for the current month?
+
+Essentially, yes. See my comment 17:
+
+(citing comment #17 from Krinkle)
+> [..] no matter how much we crop the timestamp (even if we'd crop it to the
+> month or year), one could in theory still retrieve the preferences of one
+> user by performing queries in a loop until the next day, month or year
+> starts and correlate that to the one user currently editing on that wiki..
+>
+> The only way I can think of that would mitigate that is forcing the current
+> matching crop of the date being delayed (e.g. all users active today on
+> 2014-03-17 would be listed under 2014-03-16 until this day is over, so that
+> all active users have had a chance to be active that day).
+
+However ""excluding data"" isn't trivial. It'll make statistics and sum queries act very counter intuitive. If you'd exclude all rows where timestamp == current YYYY-MM, that would essentially hide all values of active users, and make them re-appear next month and back and forth like that.
+
+To avoid strange statistical variance like that, I'd recommend making timestamp of the currently running month appear as last month's. That way no data is excluded. This seems like a simple enough variance that tools should be able to work with without much hassle.",1399258655,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Krinkle from comment #38)
+> [...]
+
+> In theory this could still be exploited by being a patient person and
+> waiting for the moment one month has ended. Then the first user to become
+> active in the new month would be the only person with a newer month
+> timestamp.
+
+> [...]
+
+Could this be mitigated by excluding data for the current month?",1399252416,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Changing the timestamp in this table based on wiki size would be a mistake in my opinion. It would make the data too arbitrary and hard to maintain. It also probably won't scale well into the MySQL mapping and relevant configuration.
+
+The reason we don't want to provide the full timestamp is because it exposes rather detailed information that would be trivial to map to an individual on most wikis (even large wikis) based on when an edit has happened.
+
+Shortening this to a month minimised this ability greatly, reducing it to only being able to tell that those with the current month as their last-active timestamp (YYYY-MM) are one of the users listed on Special:ActiveUsers.
+
+In theory this could still be exploited by being a patient person and waiting for the moment one month has ended. Then the first user to become active in the new month would be the only person with a newer month timestamp.
+
+For this particular exploit it is irrelevant how much we crop the timestamp (year, month, date, it's all the same, it only reduces how often one can make such attempt and with that the usefulness the data in the first place).
+
+If we consider that possibility important enough to warrant a solution, then that solution will work equally for year, month and day. I don't think there is any reason to trim it further than month, nor is there any reason to bring small/medium/large into the balance.",1399244062,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Small/medium/big wikis have 10/100/1000 thousands total pages or more. You can see the lists at https://noc.wikimedia.org/conf/ The lists were originally made as rough indication of how expensive certain heavy database operations are (you can easily find the bugs in question).,1399223320,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #34)
+> Sorry for the slow response, Liangent - email slipped through the cracks for
+> some reason. Q: what's the criteria for small/medium/large? And how often is
+> that updated? 
+
+I have no idea about the criteria, but I guess generally wikis only grow larger, and if the list is not updated in time, we're just anonymizing more, not less.",1399210199,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Tisza Gergő from comment #33)
+> As for timestamp anonimization, showing the (truncated) date of the last
+> edit of the user which did not happen in the current day(/month/year) should
+> be pretty straightforward.
+
+Nevermind, I see this comes from user_touched, not the edit log, and we do not keep a past record of that.
+
+Maybe instead of a live view, this table could be generated by a query which runs at the end of the day; that way no information is leaked by the timing of the change. Although that still does not solve the issue for small wikis since we probably want to run it more often than once a month.",1398906049,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Sorry for the slow response, Liangent - email slipped through the cracks for some reason. Q: what's the criteria for small/medium/large? And how often is that updated? 
+
+And Gergo's q is a good one too.",1398903291,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Is the order of rows randomized? Being able to correlate other preferences with, say, fancysig based on row number would be bad.
+
+As for timestamp anonimization, showing the (truncated) date of the last edit of the user which did not happen in the current day(/month/year) should be pretty straightforward.",1398899591,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #31)
+> So, let's keep this bug focused on the question of the ""anonymized"" table;
+> i.e., the table that currently has most (but not all) rows, with userID
+> removed but last active timestamp available. 
+> 
+> The current proposal is to provide this table on labs. It has also been
+> suggested that:
+> 
+> 1) we remove the whitelist altogether and provide everything; and/or
+> 2) we sample down the timestamp to YYYY-MM so that it is more difficult to
+> map ""last active"" to editors on small wikis.
+> 
+> I still have a few concerns:
+> 
+> 1) I still don't know how we created the original whitelist, or how we plan
+> to create the new one. (Note that if we trust our anonymization, having a
+> whitelist probably isn't necessary.)
+
+Note that some user_properties rows are not actually preferences. eg. watchlisttoken.
+
+> 
+> 2) I'm still concerned about the impact on anonymity of small wikis.
+> Rounding to months helps, but could still be problematic in at least some
+> cases (as Krinkle pointed out).
+
+So ... wikis are already grouped as small, medium and large, then YYYYMMDD in large, YYYYMM in medium and YYYY in small wikis?
+
+https://noc.wikimedia.org/conf/highlight.php?file=large.dblist
+https://noc.wikimedia.org/conf/highlight.php?file=medium.dblist
+https://noc.wikimedia.org/conf/highlight.php?file=small.dblist
+
+> I do not have a great solution to these questions. Trying to
+> brainstorm/think out loud here: maybe we could provide aggregate totals for
+> all editors, for active editors, and for new editors (based on the standard
+> analytics definition of active editors/new editors), instead of access to
+> individually anonymized rows?",1397868671,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"So, let's keep this bug focused on the question of the ""anonymized"" table; i.e., the table that currently has most (but not all) rows, with userID removed but last active timestamp available. 
+
+The current proposal is to provide this table on labs. It has also been suggested that:
+
+1) we remove the whitelist altogether and provide everything; and/or
+2) we sample down the timestamp to YYYY-MM so that it is more difficult to map ""last active"" to editors on small wikis.
+
+I still have a few concerns:
+
+1) I still don't know how we created the original whitelist, or how we plan to create the new one. (Note that if we trust our anonymization, having a whitelist probably isn't necessary.)
+
+2) I'm still concerned about the impact on anonymity of small wikis. Rounding to months helps, but could still be problematic in at least some cases (as Krinkle pointed out).
+
+I do not have a great solution to these questions. Trying to brainstorm/think out loud here: maybe we could provide aggregate totals for all editors, for active editors, and for new editors (based on the standard analytics definition of active editors/new editors), instead of access to individually anonymized rows?",1397862031,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"I'm cloning this bug so that we can have two discussions - one about the anonymized data, one about the filtered data. The discussion about a filtered view (with the handful of properties described in the original bug description and in comment #23) is now in bug 64115. I will continue the other discussion in my next comment.",1397861019,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"FYI, a ""ghost infrastructure"" makes this data available to select users, per http://lists.wikimedia.org/pipermail/analytics/2014-April/001768.html : folks should/can ask [[wikitech:EventLogging]] access if they need it.",1396991344,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,ASSIGNED != pending,1396617774,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"There's no reason to change the status of the bug, it remains pending an all-clear from Legal and a short implementation away.",1396616976,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to silke.meyer from comment #24)
+> Hello! What's the status on this?
+
+No movement in 4 months: resetting status.",1396616836,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,*** Bug 56491 has been marked as a duplicate of this bug. ***,1396616715,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Hello! What's the status on this?,1395998164,PHID-USER-qqgzlefcbycpok45pchr,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #22)
+> To confirm: INTERSECT here is the whitelist; DIFF 1 is properties that never
+> made it onto the whitelist?
+
+That is correct.
+
+INTERSECT are properties present in both Toolserver's anonymized view and in wikimedia production databases.
+
+DIFF 1 are properties present in production and not visible in Toolserver anonymized view.
+
+DIFF 2 are properties only present in Toolserver's anonymized view (none).
+
+
+The Toolserver's non-anonimized filtered view has a much stricter whitelist:
+
+nlwiki_p at toolserver> SELECT DISTINCT(up_property) FROM user_properties;
++----------------+
+| up_property    |
++----------------+
+| disablemail    |
+| fancysig       |
+| gender         |
+| language       |
+| nickname       |
+| skin           |
+| timecorrection |
+| variant        |
++----------------+
+8 rows in set",1395951431,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,To confirm: INTERSECT here is the whitelist; DIFF 1 is properties that never made it onto the whitelist?,1395678287,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Comparison for nlwiki.
+
+nlwiki at wmf> DISTINCT(up_property) FROM user_properties
++--------------------------------------------+
+| ajaxsearch
+| autopatrol
+| betafeatures-auto-enroll
+| betafeatures-geonotahack
+| betafeatures-vector-typography-update
+| ccmeonemails
+| cirrussearch-default
+| cols
+| contextchars
+| contextlines
+| date
+| diffonly
+| disablemail
+| disablesuggest
+| echo-email-format
+| echo-email-frequency
+| echo-email-last-batch
+| echo-show-alert
+| echo-subscriptions-email-article-linked
+| echo-subscriptions-email-edit-thank
+| echo-subscriptions-email-education-program
+| echo-subscriptions-email-mention
+| echo-subscriptions-email-reverted
+| echo-subscriptions-web-article-linked
+| echo-subscriptions-web-edit-thank
+| echo-subscriptions-web-education-program
+| echo-subscriptions-web-mention
+| echo-subscriptions-web-reverted
+| editfont
+| editondblclick
+| editsection
+| editsectionondblclick
+| editsectiononrightclick
+| editwidth
+| enotifminoredits
+| enotifrevealaddr
+| enotifusertalkpages
+| enotifwatchlistpages
+| ep_bulkdelcourses
+| ep_bulkdelorgs
+| ep_showdyk
+| ep_showtoplink
+| extendwatchlist
+| externaldiff
+| externaleditor
+| fancysig
+| forceeditsummary
+| gadget-Achtergrondkleur
+| gadget-Berichtbalk
+| gadget-Diffkleuren
+| gadget-Direct-link-to-Commons
+| gadget-Externe_links
+| gadget-Extra_bewerkingsknoppen
+| gadget-Geavanceerde_bijdragen
+| gadget-GoogleTrans
+| gadget-HideFundraiser
+| gadget-HotCat
+| gadget-IProject
+| gadget-LocalLiveClock
+| gadget-Navigatie_popups
+| gadget-OldDiff
+| gadget-OpenStreetMapFrame
+| gadget-OpenStreetMapFrameUit
+| gadget-ProtectionTemplates
+| gadget-ReferenceTooltips
+| gadget-Sneltoetsen
+| gadget-Twinkle
+| gadget-UTCLiveClock
+| gadget-Uitleg_verwijderlijst
+| gadget-VectorSearchNav
+| gadget-Verbergding
+| gadget-WhatLeavesHere
+| gadget-Zeusmodus
+| gadget-fixhoofdbetekenis
+| gadget-hoofdbetekenis-titelwijziging
+| gadget-labelfilter
+| gadget-mijnKladblok
+| gadget-purgelink
+| gadget-searchFocus
+| gadget-updatemarker
+| gadget-verwijderreden
+| gender
+| hideminor
+| hidepatrolled
+| highlightbroken
+| hover
+| imagesize
+| justify
+| language
+| math
+| mfWatchlistFilter
+| mfWatchlistView
+| minordefault
+| moodbar-disable
+| multimedia-viewer
+| newpageshidepatrolled
+| nickname
+| nocache
+| norollbackdiff
+| numberheadings
+| prefershttps
+| previewonfirst
+| previewontop
+| quickbar
+| rcdays
+| rclimit
+| rcshowwikidata
+| rememberpassword
+| rows
+| searchNs-1
+| searchNs0
+| searchNs1
+| searchNs10
+| searchNs100
+| searchNs101
+| searchNs11
+| searchNs12
+| searchNs13
+| searchNs14
+| searchNs15
+| searchNs2
+| searchNs3
+| searchNs4
+| searchNs4294967295
+| searchNs446
+| searchNs447
+| searchNs5
+| searchNs6
+| searchNs7
+| searchNs8
+| searchNs828
+| searchNs829
+| searchNs9
+| searcheverything
+| searchlimit
+| showhiddencats
+| showjumplinks
+| shownumberswatching
+| showtoc
+| showtoolbar
+| skin
+| stubthreshold
+| thumbsize
+| timecorrection
+| uls-compact-links
+| uls-enable
+| uls-preferences
+| underline
+| usebetatoolbar
+| usebetatoolbar-cgd
+| useeditwarning
+| uselivepreview
+| usenewrc
+| userjs-already-set-common-preferences
+| variant
+| vector-collapsiblenav
+| vector-noexperiments
+| vector-simplesearch
+| visualeditor-betatempdisable
+| visualeditor-enable
+| visualeditor-enable-mwmath
+| watchcreations
+| watchdefault
+| watchdeletion
+| watchlistdays
+| watchlisthideanons
+| watchlisthidebots
+| watchlisthideliu
+| watchlisthideminor
+| watchlisthideown
+| watchlisthidepatrolled
+| watchlisttoken
+| watchmoves
+| wllimit
+| wlshowwikibase
++--------------------------------------------+
+176 rows in set (4.95 sec)
+
+nlwiki_p at toolserver> DISTINCT(up_property) FROM user_properties_anonym
++-----------------------------------------+
+| up_property
++-----------------------------------------+
+| ajaxsearch
+| autopatrol
+| ccmeonemails
+| cols
+| contextchars
+| contextlines
+| date
+| diffonly
+| disablemail
+| disablesuggest
+| echo-email-format
+| echo-email-frequency
+| echo-show-alert
+| echo-subscriptions-email-article-linked
+| echo-subscriptions-email-edit-thank
+| echo-subscriptions-email-mention
+| echo-subscriptions-email-reverted
+| echo-subscriptions-web-article-linked
+| echo-subscriptions-web-edit-thank
+| echo-subscriptions-web-mention
+| echo-subscriptions-web-reverted
+| editfont
+| editondblclick
+| editsection
+| editsectiononrightclick
+| editwidth
+| enotifminoredits
+| enotifrevealaddr
+| enotifusertalkpages
+| enotifwatchlistpages
+| extendwatchlist
+| externaldiff
+| externaleditor
+| fancysig
+| forceeditsummary
+| gadget-Achtergrondkleur
+| gadget-Berichtbalk
+| gadget-Diffkleuren
+| gadget-Direct-link-to-Commons
+| gadget-Externe_links
+| gadget-Extra_bewerkingsknoppen
+| gadget-fixhoofdbetekenis
+| gadget-Geavanceerde_bijdragen
+| gadget-GoogleTrans
+| gadget-HideFundraiser
+| gadget-hoofdbetekenis-titelwijziging
+| gadget-HotCat
+| gadget-IProject
+| gadget-labelfilter
+| gadget-LocalLiveClock
+| gadget-mijnKladblok
+| gadget-Navigatie_popups
+| gadget-OldDiff
+| gadget-OpenStreetMapFrame
+| gadget-OpenStreetMapFrameUit
+| gadget-ProtectionTemplates
+| gadget-purgelink
+| gadget-ReferenceTooltips
+| gadget-searchFocus
+| gadget-Sneltoetsen
+| gadget-Twinkle
+| gadget-Uitleg_verwijderlijst
+| gadget-updatemarker
+| gadget-UTCLiveClock
+| gadget-VectorSearchNav
+| gadget-Verbergding
+| gadget-verwijderreden
+| gadget-WhatLeavesHere
+| gadget-Zeusmodus
+| gender
+| hideminor
+| hidepatrolled
+| highlightbroken
+| hover
+| imagesize
+| justify
+| language
+| math
+| minordefault
+| newpageshidepatrolled
+| nocache
+| norollbackdiff
+| numberheadings
+| previewonfirst
+| previewontop
+| quickbar
+| rcdays
+| rclimit
+| rememberpassword
+| searcheverything
+| searchlimit
+| searchNs-1
+| showhiddencats
+| showjumplinks
+| shownumberswatching
+| showtoc
+| showtoolbar
+| skin
+| stubthreshold
+| thumbsize
+| timecorrection
+| underline
+| usebetatoolbar
+| usebetatoolbar-cgd
+| useeditwarning
+| uselivepreview
+| usenewrc
+| variant
+| vector-noexperiments
+| visualeditor-enable
+| watchcreations
+| watchdefault
+| watchdeletion
+| watchlistdays
+| watchlisthideanons
+| watchlisthidebots
+| watchlisthideliu
+| watchlisthideminor
+| watchlisthideown
+| watchlisthidepatrolled
+| watchmoves
+| wllimit
++-----------------------------------------+
+122 rows in set (51.05 sec)
+
+INTERSECT: 
+
+| ajaxsearch
+| autopatrol
+| ccmeonemails
+| cols
+| contextchars
+| contextlines
+| date
+| diffonly
+| disablemail
+| disablesuggest
+| echo-email-format
+| echo-email-frequency
+| echo-show-alert
+| echo-subscriptions-email-article-linked
+| echo-subscriptions-email-edit-thank
+| echo-subscriptions-email-mention
+| echo-subscriptions-email-reverted
+| echo-subscriptions-web-article-linked
+| echo-subscriptions-web-edit-thank
+| echo-subscriptions-web-mention
+| echo-subscriptions-web-reverted
+| editfont
+| editondblclick
+| editsection
+| editsectiononrightclick
+| editwidth
+| enotifminoredits
+| enotifrevealaddr
+| enotifusertalkpages
+| enotifwatchlistpages
+| extendwatchlist
+| externaldiff
+| externaleditor
+| fancysig
+| forceeditsummary
+| gadget-Achtergrondkleur
+| gadget-Berichtbalk
+| gadget-Diffkleuren
+| gadget-Direct-link-to-Commons
+| gadget-Externe_links
+| gadget-Extra_bewerkingsknoppen
+| gadget-Geavanceerde_bijdragen
+| gadget-GoogleTrans
+| gadget-HideFundraiser
+| gadget-HotCat
+| gadget-IProject
+| gadget-LocalLiveClock
+| gadget-Navigatie_popups
+| gadget-OldDiff
+| gadget-OpenStreetMapFrame
+| gadget-OpenStreetMapFrameUit
+| gadget-ProtectionTemplates
+| gadget-ReferenceTooltips
+| gadget-Sneltoetsen
+| gadget-Twinkle
+| gadget-UTCLiveClock
+| gadget-Uitleg_verwijderlijst
+| gadget-VectorSearchNav
+| gadget-Verbergding
+| gadget-WhatLeavesHere
+| gadget-Zeusmodus
+| gadget-fixhoofdbetekenis
+| gadget-hoofdbetekenis-titelwijziging
+| gadget-labelfilter
+| gadget-mijnKladblok
+| gadget-purgelink
+| gadget-searchFocus
+| gadget-updatemarker
+| gadget-verwijderreden
+| gender
+| hideminor
+| hidepatrolled
+| highlightbroken
+| hover
+| imagesize
+| justify
+| language
+| math
+| minordefault
+| newpageshidepatrolled
+| nocache
+| norollbackdiff
+| numberheadings
+| previewonfirst
+| previewontop
+| quickbar
+| rcdays
+| rclimit
+| rememberpassword
+| searchNs-1
+| searcheverything
+| searchlimit
+| showhiddencats
+| showjumplinks
+| shownumberswatching
+| showtoc
+| showtoolbar
+| skin
+| stubthreshold
+| thumbsize
+| timecorrection
+| underline
+| usebetatoolbar
+| usebetatoolbar-cgd
+| useeditwarning
+| uselivepreview
+| usenewrc
+| variant
+| vector-noexperiments
+| visualeditor-enable
+| watchcreations
+| watchdefault
+| watchdeletion
+| watchlistdays
+| watchlisthideanons
+| watchlisthidebots
+| watchlisthideliu
+| watchlisthideminor
+| watchlisthideown
+| watchlisthidepatrolled
+| watchmoves
+| wllimit
+
+DIFF 1: 
+| betafeatures-auto-enroll
+| betafeatures-geonotahack
+| betafeatures-vector-typography-update
+| cirrussearch-default
+| echo-email-last-batch
+| echo-subscriptions-email-education-program
+| echo-subscriptions-web-education-program
+| editsectionondblclick
+| ep_bulkdelcourses
+| ep_bulkdelorgs
+| ep_showdyk
+| ep_showtoplink
+| mfWatchlistFilter
+| mfWatchlistView
+| moodbar-disable
+| multimedia-viewer
+| nickname
+| prefershttps
+| rcshowwikidata
+| rows
+| searchNs0
+| searchNs1
+| searchNs10
+| searchNs100
+| searchNs101
+| searchNs11
+| searchNs12
+| searchNs13
+| searchNs14
+| searchNs15
+| searchNs2
+| searchNs3
+| searchNs4
+| searchNs4294967295
+| searchNs446
+| searchNs447
+| searchNs5
+| searchNs6
+| searchNs7
+| searchNs8
+| searchNs828
+| searchNs829
+| searchNs9
+| uls-compact-links
+| uls-enable
+| uls-preferences
+| userjs-already-set-common-preferences
+| vector-collapsiblenav
+| vector-simplesearch
+| visualeditor-betatempdisable
+| visualeditor-enable-mwmath
+| watchlisttoken
+| wlshowwikibase
+
+DIFF 2: 
+
+(none)",1395206347,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Do we know how that whitelist was created?,1395164140,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #18)
+> (In reply to Krinkle from comment #17)
+> > So if I understand correctly, the whitelist of properties you approved in
+> > comment 12 are in fact allowed for identifiable queries (e.g. with
+> > user_id/user name attached to it), as opposed to the anonymized view.
+> 
+> Yes, that is correct, for those categories. 
+> 
+> As far as implementation, we'll want to review new fields as they are added,
+> which is why I prefer a whitelist approach (review what is released; hard to
+> accidentally release data accidentally) to a blacklist approach (review what
+> is not released; easy to release data accidentally by not adding it to the
+> blacklist).
+> 
+> > And when you say ""OK in principle"" for the anonymized view, that means all
+> > properties?
+> 
+> Yes, based on my understanding that they are already available on toolserver
+> in user_properties_anonym and/or via the API. If they aren't already public
+> (via API or toolserver) we should probably review one-by-one, and/or do a
+> more careful scrutiny of the anonymization procedures. Maybe that deserves a
+> separate bug?
+
+anonym on Toolserver is also whitelist based. I don't have access to the original list ts_global.user_properties_anonym_whilelist, but it's possible to sniff it with select distinct up_property from user_properties_anonym; (a slow query).",1395104663,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Krinkle from comment #17)
+> So if I understand correctly, the whitelist of properties you approved in
+> comment 12 are in fact allowed for identifiable queries (e.g. with
+> user_id/user name attached to it), as opposed to the anonymized view.
+
+Yes, that is correct, for those categories. 
+
+As far as implementation, we'll want to review new fields as they are added, which is why I prefer a whitelist approach (review what is released; hard to accidentally release data accidentally) to a blacklist approach (review what is not released; easy to release data accidentally by not adding it to the blacklist).
+
+> And when you say ""OK in principle"" for the anonymized view, that means all
+> properties?
+
+Yes, based on my understanding that they are already available on toolserver in user_properties_anonym and/or via the API. If they aren't already public (via API or toolserver) we should probably review one-by-one, and/or do a more careful scrutiny of the anonymization procedures. Maybe that deserves a separate bug?",1395101959,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"So if I understand correctly, the whitelist of properties you approved in comment 12 are in fact allowed for identifiable queries (e.g. with user_id/user name attached to it), as opposed to the anonymized view. That's great news. I wasn't expecting a non-anonymized view of the properties table at all. Having one with this limited set of properties can be useful indeed.
+
+And when you say ""OK in principle"" for the anonymized view, that means all properties?
+
+Good point on the user activity measure being potentially identifying on small wikis. I suppose a month crop of the timestamp (YYYY-MM) would still be good enough for practical applications and be a lot less likely to reveal identifying information.
+
+Though no matter how much we crop the timestamp (even if we'd crop it to the month or year), one could in theory still retrieve the preferences of one user by performing queries in a loop until the next day, month or year starts and correlate that to the one user currently editing on that wiki.. The only way I can think of that would mitigate that is forcing the current matching crop of the date being delayed (e.g. all users active today on 2014-03-17 would be listed under 2014-03-16 until this day is over, so that all active users have had a chance to be active that day).",1395017899,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Retitling then :) 
+
+For the filtered table: I am OK with this in principle, but would like to better understand (1) how we choose which fields to filter and (2) how we prevent new fields from leaking.
+
+For the anonymized table: Again, OK in principle; it would be good (but not a must-have) to know more about the impact on users of small wikis.",1394823426,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #14)
+> Ah! Thanks for explaining more clearly, Krinkle. The first comment now makes
+> a lot more sense to me :) 
+> 
+> One question on the anonymization - this data is still per-wiki, right?
+> Would last-active dates at the day-level allow deanonymization for those
+> users?
+
+Those are two different requests: one table (view) containing user identifiable info (user id) with fewer properties includes, and another anonymized one with more properties.",1394778923,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Ah! Thanks for explaining more clearly, Krinkle. The first comment now makes a lot more sense to me :) 
+
+One question on the anonymization - this data is still per-wiki, right? Would last-active dates at the day-level allow deanonymization for those users?",1394751837,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"I'm hoping we can get permission to provide this view on Tool Labs without a whitelist of keys like that and instead allow all, or at least a more liberal subset.
+
+The main request is to provide what Toolserver provided which is:
+
+An anonimized view of the user_properties table with an extra column that shows the date (not the time) of when the associated user was last active (which allows consumers of the data to focus on (or reject) recently active users vs. abandoned user accounts).
+
+The raw user_properties database in Wikimedia production contains:
+
+- up_user: The user_id of the user, this must of course not be exposed
+   because that would allow consumers of the data to know which preferences
+   belong to the same user, and in addition, since user ids are already public,
+   to also know which user it belongs to).
+
+- up_property: The preference names (disablemail, gender, language, skin, gadget-Foo, gadget-Bar etc.)
+
+- up_value: The value of the preference. For most preferences these are boolean values (0 of off, 1 for on). Others are one of a finite set of values (like ""language"" and ""skin""). And then there are some that take free numerical input (like ""rclimit"" which can be any number, e.g. 10 or 500, for the number of results to show by default on Special:Search or Special:RecentChanges). And lastly, there are some that take free textual input (like nickname and fancysig). This last category is usually identifying to a person. So I could understand why one might keep these hidden (though Luis already said those two were fine). I imagine it's fine because they're public (people use their signature and nickname all the time), and anonymised (not connected to other preferences of that same user).
+
+Of these, the anonimized view would expose:
+
+- up_property
+- up_value
+
+This will allow tools to know how popular certain preferences are (e.g. How many people use the Monobook skin, How many people change their interface language to French on German Wikipedia). I think however that this view should not be restricted to certain preferences. Especially because:
+
+ 1) Extensions and core add new preferences all the time.
+
+ 2) Gadgets are enabled through preferences as well, so if we do use a
+    whitelist, it should whitelist any preference starting with ""gadget-*"".
+
+ 3) BetaFeatures also comes and goes with new preferences.
+    The case of BetaFeatures is interesting, because it actually tracks
+    and exposes the usage of its own preferences publicly (doesn't even
+    require making a Tool of some kind).
+
+
+In addition to these two columns, it would be very useful to have some kind of indicator to interpret these values. Toolserver did this by adding a shadow column showing a trimmed part of the timestamp of when the associated user was last active (trimmed to only show the date in YYYY-MM-DD, not the exact time of day). With this, statistics about preferences are much more useful due to the large number of abandoned accounts polluting the results.
+
+Here's a query showing which keys are currently exposed in Toolserver's  user_properties_anonym table:
+
+krinkle at willow.toolserver.org$ sql nlwiki_p
+mysql> SELECT DISTINCT(up_property) FROM user_properties_anonym;
++-----------------------------------------+
+| up_property                             |
++-----------------------------------------+
+| ajaxsearch                              |
+| autopatrol                              |
+| ccmeonemails                            |
+| cols                                    |
+| contextchars                            |
+| contextlines                            |
+| date                                    |
+| diffonly                                |
+| disablemail                             |
+| disablesuggest                          |
+| echo-email-format                       |
+| echo-email-frequency                    |
+| echo-show-alert                         |
+| echo-subscriptions-email-article-linked |
+| echo-subscriptions-email-edit-thank     |
+| echo-subscriptions-email-mention        |
+| echo-subscriptions-email-reverted       |
+| echo-subscriptions-web-article-linked   |
+| echo-subscriptions-web-edit-thank       |
+| echo-subscriptions-web-mention          |
+| echo-subscriptions-web-reverted         |
+| editfont                                |
+| editondblclick                          |
+| editsection                             |
+| editsectiononrightclick                 |
+| editwidth                               |
+| enotifminoredits                        |
+| enotifrevealaddr                        |
+| enotifusertalkpages                     |
+| enotifwatchlistpages                    |
+| extendwatchlist                         |
+| externaldiff                            |
+| externaleditor                          |
+| fancysig                                |
+| forceeditsummary                        |
+| gadget-Achtergrondkleur                 |
+| gadget-Berichtbalk                      |
+| gadget-Diffkleuren                      |
+| gadget-Extra_bewerkingsknoppen          |
+| gadget-fixhoofdbetekenis                |
+| gadget-Geavanceerde_bijdragen           |
+| gadget-HideFundraiser                   |
+| gadget-HotCat                           |
+| gadget-IProject                         |
+| gadget-Navigatie_popups                 |
+| gadget-purgelink                        |
+| gadget-ReferenceTooltips                |
+| gadget-Twinkle                          |
+| gadget-UTCLiveClock                     |
+| gender                                  |
+| hideminor                               |
+| hidepatrolled                           |
+| highlightbroken                         |
+| hover                                   |
+| imagesize                               |
+| justify                                 |
+| language                                |
+| math                                    |
+| minordefault                            |
+| newpageshidepatrolled                   |
+| nocache                                 |
+| norollbackdiff                          |
+| numberheadings                          |
+| previewonfirst                          |
+| previewontop                            |
+| quickbar                                |
+| rcdays                                  |
+| rclimit                                 |
+| rememberpassword                        |
+| searcheverything                        |
+| searchlimit                             |
+| searchNs-1                              |
+| showhiddencats                          |
+| showjumplinks                           |
+| shownumberswatching                     |
+| showtoc                                 |
+| showtoolbar                             |
+| skin                                    |
+| stubthreshold                           |
+| thumbsize                               |
+| timecorrection                          |
+| underline                               |
+| usebetatoolbar                          |
+| usebetatoolbar-cgd                      |
+| useeditwarning                          |
+| uselivepreview                          |
+| usenewrc                                |
+| variant                                 |
+| vector-noexperiments                    |
+| visualeditor-enable                     |
+| watchcreations                          |
+| watchdefault                            |
+| watchdeletion                           |
+| watchlistdays                           |
+| watchlisthideanons                      |
+| watchlisthidebots                       |
+| watchlisthideliu                        |
+| watchlisthideminor                      |
+| watchlisthideown                        |
+| watchlisthidepatrolled                  |
+| watchmoves                              |
+| wllimit                                 |
++-----------------------------------------+
+102 rows in set
+
+
+Are there any preferences we would explicitly not want to expose?",1394750751,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Sorry, this got lost in the shuffle. To respond to Silke: I'm still not entirely clear which fields we're talking about replicating. If the list from en_wikip: 
+
++----------------+
+| up_property    |
++----------------+
+| disablemail    |
+| fancysig       |
+| gender         |
+| language       |
+| nickname       |
+| skin           |
+| timecorrection |
+| variant        |
++----------------+
+
+Is what we're actually talking about, then yes - no legal barrier to making that information available.",1394746288,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"The gender gap plots by emijrp also depends on this:
+
+https://toolserver.org/~emijrp/wmcharts/
+
+(they don't work atm. for some other reason)",1394745066,PHID-USER-53x4y44yt43qjivfzsqf,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #9)
+
+> Legoktm, which of your tools depends on this to migrate?
+
+Database reports, specifically [[Wikipedia:Database reports/User preferences]].",1391540347,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"So, am I right in assuming there is no legal barrier to make that table available? 
+Legoktm, which of your tools depends on this to migrate?",1391532830,PHID-USER-qqgzlefcbycpok45pchr,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #7)
+> Ah, didn't know that, thanks. Though, given that the AbuseFilter has been
+> giving out emailconfirmed timestamps (bug 20005), it's probably a moot point.
+
+That seems to me a good reason to fix 20005 more than anything (especially since that isn't in the dumps).",1387510467,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #6)
+> (In reply to comment #4)
+> > For example, if you go to Special:EmailUser, you can tell if a user has
+> > disabled email or not (disableemail).
+> 
+> That's not actually correct; you can know whether someone has disabled their
+> email /or/ never confirmed one to begin with (i.e.: it's emailconfirmed &&
+> !disableemail).
+
+Ah, didn't know that, thanks. Though, given that the AbuseFilter has been giving out emailconfirmed timestamps (bug 20005), it's probably a moot point.",1387505659,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #4)
+> For example, if you go to Special:EmailUser, you can tell if a user has
+> disabled email or not (disableemail).
+
+That's not actually correct; you can know whether someone has disabled their email /or/ never confirmed one to begin with (i.e.: it's emailconfirmed && !disableemail).",1387503916,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"If a field is already exposed by the API/website, then that's fine. Just wasn't clear which of those fields that was already true for.",1387503572,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #3)
+> Legoktm, when you say ""Only preferences that are considered to be public are
+> replicated, the list from enwiki_p is..."" is that the list of things
+> currently
+> considered public? Or the list of things that could be made public?
+
+Since it's already replicated onto the Toolserver, I assume they are currently considered to be public.
+
+For example, if you go to Special:EmailUser, you can tell if a user has disabled email or not (disableemail). fancysig/nickname are just a user's signature, which is public as soon as a user adds ~~~~ to any page. gender is also exposed by the software and the API.",1387503366,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"I don't think we've formally set out a policy that new field replication has to run through legal, but it's a good habit to be in.
+
+Legoktm, when you say ""Only preferences that are considered to be public are replicated, the list from enwiki_p is..."" is that the list of things currently considered public? Or the list of things that could be made public?",1387492207,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Adding Luis Villa so that he can chime in.,1387480184,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Coren says there's a requirement that the Wikimedia Foundation legal team sign off on changes of this nature. I'm not able to verify this requirement. The process seems to be largely undocumented, though as far as I'm aware, there was never any such requirement during the Toolserver's reign: it was merely left to root discretion.",1386566431,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Steps to reproduce:
+
+
+1.Open the editor for a page which contains a link
+2.Copy the link
+3.Now open VE for another article and paste the copied link onto it
+4.Save the page
+
+
+Observed Result:
+
+The copied link appears as a plain text on the read mode where as in the Edit Source/Edit mode it appears as a link
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58138",1386376320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_description,resolved
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",Verified the fix on test 2,1391132245,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 108954 merged by jenkins-bot:
+Relativise URLs against target document
+
+https://gerrit.wikimedia.org/r/108954",1390445932,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",Possibly now fixed. Hopefully.,1390442043,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 108953 had a related patch set uploaded by Krinkle:
+Resolve URLs against correct document when copying.
+
+https://gerrit.wikimedia.org/r/108953",1390424401,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 108954 had a related patch set uploaded by Esanders:
+Relativise URLs against target document
+
+https://gerrit.wikimedia.org/r/108954",1390421253,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",Sorry 16th January :),1390343484,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Ed, I tested it on 16th december(Last thursday) after the deployment on test2.So it should have been merged to test2 by that time right? Also, I am still getting it on test2",1390339282,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",The last fix was merged on 15th Jan. The test environment you point to says it is running code from 14th Jan. Please re-open if broken with master.,1390316590,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",*** Bug 59216 has been marked as a duplicate of this bug. ***,1390024188,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","The testing environment is test2, wmf 11.
+Broswer:Chrome/Firefox",1389901609,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","The issue described later in this bug still exists in test.Again giving the steps here:
+This issue is still occurring for following case:
+
+1.Open the editor for a page ""A"" which contains a link to another page ""B""
+2.Copy the link and Paste it into ""B""
+3.Save the page
+
+Observed Result:
+The link to the same page is appearing as plain text in the read mode.",1389901513,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 105706 merged by jenkins-bot:
+Support external links in MWInternalLinkAnnotation
+
+https://gerrit.wikimedia.org/r/105706",1389824850,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 106253 merged by jenkins-bot:
+Always use absolute URLs in external links in the clipboard
+
+https://gerrit.wikimedia.org/r/106253",1389641923,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 106253 had a related patch set uploaded by Esanders:
+Always use absolute URLs in external links in the clipboard
+
+https://gerrit.wikimedia.org/r/106253",1389191918,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 105706 had a related patch set uploaded by Esanders:
+Always use absolute URLs in external links in the clipboard
+
+https://gerrit.wikimedia.org/r/105706",1389028307,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","This issue is still occurring for following case:
+
+1.Open the editor for a page ""A"" which contains a link to another page ""B""
+2.Copy the link and Paste it into ""B""
+3.Save the page
+
+Observed Result:
+The link to the same page is appearing as plain text in the read mode.
+
+Found in :http://en.wikipedia.beta.wmflabs.org/wiki/The_paste_destination",1387397886,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=13th_december,1386984067,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",Verified in betalabs,1386790162,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",A fix for this is going out in about 4 minutes' time. Sorry for the disruption.,1386633329,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 100493 merged by jenkins-bot:
+Only strip style attributes on rich paste from VE
+
+https://gerrit.wikimedia.org/r/100493",1386632961,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 100422 merged by jenkins-bot:
+Only strip style attributes on rich paste from VE
+
+https://gerrit.wikimedia.org/r/100422",1386629947,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 100493 had a related patch set uploaded by Jforrester:
+Only strip style attributes on rich paste from VE
+
+https://gerrit.wikimedia.org/r/100493",1386629891,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 100422 had a related patch set uploaded by Esanders:
+Only strip style attributes on rich paste from VE
+
+https://gerrit.wikimedia.org/r/100422",1386618650,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Page: Observe the second ""Edit source"" text on the page:
+http://en.wikipedia.beta.wmflabs.org/wiki/To_edit_source
+
+Test Environment: Betalabs
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5",1386376423,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+VisualEditor:The icon for underline option is missing in betalabs,"screenshot
+
+The icon for underline option is missing in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/The_link?veaction=edit
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12362}",1386364620,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fk5w6cwyl6t7fo226qow,task_description,resolved
+VisualEditor:The icon for underline option is missing in betalabs,Verified,1386370145,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fk5w6cwyl6t7fo226qow,task_subcomment,NA
+VisualEditor:The icon for underline option is missing in betalabs,"Change 99755 merged by jenkins-bot:
+Followup 418f2606e03b82a5ae0afc853406c7e9f2d1e35f: put <?xml tag back.
+
+https://gerrit.wikimedia.org/r/99755",1386366847,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fk5w6cwyl6t7fo226qow,task_subcomment,NA
+VisualEditor:The icon for underline option is missing in betalabs,"Change 99755 had a related patch set uploaded by Catrope:
+Followup 418f2606e03b82a5ae0afc853406c7e9f2d1e35f: put <?xml tag back.
+
+https://gerrit.wikimedia.org/r/99755",1386366381,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fk5w6cwyl6t7fo226qow,task_subcomment,NA
+VisualEditor: <ooui-toolbar-more> is showing up instead of More button in betalabs,"Screenshot
+
+<ooui-toolbar-more> is showing up instead of More button in betalabs
+http://en.wikipedia.beta.wmflabs.org/wiki/6th_december?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12338}",1386356940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-du3trqyxzlr7pus3ud55,task_description,declined
+VisualEditor: <ooui-toolbar-more> is showing up instead of More button in betalabs,"Deployment bug, now fixed.",1386392274,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-du3trqyxzlr7pus3ud55,task_subcomment,NA
+VisualEditor: <ooui-toolbar-more> is showing up instead of More button in betalabs,"Created attachment 14009
+screenshot of the notification
+
+**Attached**: {F12339}",1386358017,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-du3trqyxzlr7pus3ud55,task_subcomment,NA
+VisualEditor: <ooui-toolbar-more> is showing up instead of More button in betalabs,"Also instead of the notification message after saving a page <visualeditor-notification-saved> is appearing.
+
+See the screenshot attached.",1386357987,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-du3trqyxzlr7pus3ud55,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),"**Author:** `Wikifram`
+
+**Description:**
+When you have made changes to a page in VE, you can use the ""undo"" button to reverse these. However, the page doesn't scroll when doing this, so you don't ""see"" what the undo is actually doing. The same probably applies to the ""redo"" button, I haven't checked that one
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51911",1386321060,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_description,resolved
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),This was probably fixed a while ago.,1456235332,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),"(In reply to Alex Monk from comment #3)
+> Dupe then?
+
+Doing it for the undo/redo stack is probably complicated, so I was leaving them distinct.",1415046177,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),Dupe then?,1415045955,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),"(In reply to Alex Monk from comment #1)
+> Hmm... Shouldn't this be a case of scrolling to the new location of the
+> cursor when you undo/redo?
+
+Pretty much, which is bug 51911.",1415045652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),Hmm... Shouldn't this be a case of scrolling to the new location of the cursor when you undo/redo?,1414813862,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+"VisualEditor: Auto context links (#contentSub) under the title in the User: namespace is only hidden, not suppressed, so can still be clicked","Screenshot
+
+Steps to reproduce:
+
+1.Open the VE for a page in a User's namespace
+2.Hover your mouse over the position where the link to user namespace appears in the Read mode.
+3.Click on that position
+
+Observed Result:
+It redirects to user namespace from VE.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52243
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54325
+
+**Attached**: {F12247}",1386288540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bgaxa5whdy4rwfmma5hm,task_description,resolved
+"VisualEditor: Auto context links (#contentSub) under the title in the User: namespace is only hidden, not suppressed, so can still be clicked","Environment:Production (https://en.wikipedia.org/)
+Browser:Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5",1386288748,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bgaxa5whdy4rwfmma5hm,task_subcomment,NA
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted","Screenshot
+
+Steps to reproduce:
+
+1.Open the editor
+2.Place the cursor in the middle of a text
+3.Then click on More>Hieroglyphics
+4.The inspector does not open just the < icon in that position.
+5.Save the page
+6.Reopen the editor.
+
+
+Observed Result:
+The text after that cursor position gets shifted to the newline and a return arrow appears after reopening the editor.
+
+For a text which is not link it just goes to the next line but the return arrow does not get added.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12190}",1386269880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zzarel5lh2xkfhzr752t,task_description,resolved
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted","I believe that this is now fixed… can't really check any more, though.",1410033747,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zzarel5lh2xkfhzr752t,task_subcomment,NA
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted",While going to the next line it also adds an empty <hiero> tags in that position.,1386286227,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zzarel5lh2xkfhzr752t,task_subcomment,NA
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted","Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=The_something&veaction=edit",1386270837,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zzarel5lh2xkfhzr752t,task_subcomment,NA
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted","Created attachment 13994
+Screenshot of the < appearing instead of the hieroglyphics inspector
+
+**Attached**: {F12191}",1386270471,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zzarel5lh2xkfhzr752t,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Screenshot
+
+Steps to reproduce:
+
+
+1.Open the editor.
+2.Select an image
+3.Select the option More>Latex/Hieroglyphics
+
+Observed Result:
+
+A small input window opens up over the window where text can be inserted.
+
+In the console I get the following error:
+Uncaught TypeError: Cannot read property 'body' of undefined load.php:521
+ve.ui.MWExtensionInspector.setup load.php:521
+(anonymous function) load.php:113
+proxy load.php:10
+listenerWrapper load.php:98
+oo.EventEmitter.emit load.php:98
+(anonymous function) load.php:110
+pollExternalStylesheets
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60804
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56644
+
+**Attached**: {F12183}",1386268980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_description,resolved
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies",Verified the fix in production,1398988445,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies",Verified the fix in test2,1398898363,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Change 129622 merged by jenkins-bot:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/129622",1398384373,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Change 129622 had a related patch set uploaded by Jforrester:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/129622",1398384262,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Change 126900 merged by jenkins-bot:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/126900",1397845436,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Change 126900 had a related patch set uploaded by Esanders:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/126900",1397780745,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies",WFM,1397778331,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+VisualEditor: Cursoring off the page with left/right doesn't scroll the cursor in to view,"Contrast with up/down which always keeps the cursor in view.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68708",1386258480,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sjbb3upxz7oa72molxbx,task_description,resolved
+VisualEditor: Cursoring off the page with left/right doesn't scroll the cursor in to view,Seems to work now. ,1443036355,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-sjbb3upxz7oa72molxbx,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"LQT intercepts section=new from users to add a new thread (but not via the API, see bug 41276). It'd be really awesome if Flow could let you add a new topic like this, using the old API.
+
+https://www.mediawiki.org/wiki/API:Edit#Example
+
+--------------------------
+**See Also**: 
+* {T43276}
+* {T85197}",1386178920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfuu4csnnqoanjnouo7z,task_description,declined
+S2. Flow API: Let code add a new topic with action=edit&section=new,"Note that will work for both wikitext and Flow, so the gadget does not need to know which the page is.
+
+The above is for if you're trying to create the post immediately through the script.
+
+---
+
+It looks like for this example, you just want to prefill it (rather than use the API), then let the user edit before saving.  Flow supports that too:
+
+https://www.mediawiki.org/wiki/User_talk:Mattflaschen-WMF?topiclist_preloadtitle=Preloaded%20title&topiclist_preload=User:Mattflaschen-WMF/Preloaded%20body%20example
+
+The preloadtitle is inlined.  The preload is a template (in this example [User:Mattflaschen-WMF/Preloaded body example](https://www.mediawiki.org/wiki/User:Mattflaschen-WMF/Preloaded_body_example).
+
+This is basically the same as for old-style talk pages.  For old-style, it's:
+
+https://en.wikipedia.org/wiki/User_talk:Mattflaschen-WMF?preloadtitle=Preloaded title&preload=User:Mattflaschen-WMF/Preloaded body example&action=edit&section=new
+
+In that case, you do currently need to check what kind of page it is, though, using prop=info:
+
+https://en.wikipedia.org/w/api.php?action=query&titles=User%20talk:Mattflaschen-WMF&prop=info
+
+vs.
+
+https://www.mediawiki.org/w/api.php?action=query&titles=User%20talk:Mattflaschen-WMF&prop=info
+
+There is a possibility to make this use case easier for script writers: {T107637}",1439852916,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"Note that will work for both wikitext and Flow, so the gadget does not need to know which the page is.
+
+The above is for if you're trying to create the post immediately through the script.
+
+---
+
+It looks like for this example, you just want to prefill it (rather than use the API), then let the user edit before saving.  Flow supports that too:
+
+https://www.mediawiki.org/wiki/User_talk:Mattflaschen-WMF?topiclist_preloadtitle=Preloaded%20title&topiclist_preload=User:Mattflaschen-WMF/Preloaded%20body%20example
+
+The preloadtitle is inlined.  The preload is a template (in this example [User:Mattflaschen-WMF/Preloaded body example](https://www.mediawiki.org/wiki/User:Mattflaschen-WMF/Preloaded_body_example).
+
+This is basically the same as for old-style talk pages.  For old-style, it's:
+
+https://en.wikipedia.org/wiki/User_talk:Mattflaschen-WMF?preloadtitle=Preloaded title&preload=User:Mattflaschen-WMF/Preloaded body example&action=edit&section=new
+
+In that case, you do currently need to check what kind of page it is, though, using action=info:
+
+https://en.wikipedia.org/w/api.php?action=query&titles=User%20talk:Mattflaschen-WMF&prop=info
+
+vs.
+
+https://www.mediawiki.org/w/api.php?action=query&titles=User%20talk:Mattflaschen-WMF&prop=info
+
+There is a possibility to make this use case easier for script writers: {T107637}",1438383435,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,">>! In T59989#1499951, @tarlocesilion wrote:
+> I believe, I should emphasize that this gadget is old (2006) and //very// popular among experienced Wikipedians, the core of plwiki community, who are likely to be //concerned// about next Flow releases, not only on personal talk pages. Just for the record, if action=edit&section=new isn't to be supported, please, create something instead.
+
+Our recommended solution is to use mw.messagePoster (which we implemented for this purpose).  Usage:
+
+```
+	var title = new mw.Title( 'titleString' );
+	var posterPromise = mw.messagePoster.factory.create( title );
+	posterPromise.done( function ( poster ) {
+		poster.post( 'This is the topic title', 'This is the body of a message posted with MessagePoster' );
+	} );
+```
+
+The gadget should also depend on 'mediawiki.messagePoster' and 'mediawiki.Title' (user scripts can depend on those with mw.loader.using).
+
+If you need further technical assistance, please ask (e.g. in #wikimedia-collaboration on IRC).",1438382035,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"I believe, I should emphasize that this gadget is old (2006) and //very// popular among experienced Wikipedians, the core of plwiki community, who are likely to be //concerned// about next Flow releases, not only on personal talk pages. Just for the record, if action=edit&section=new isn't to be supported, please, create something instead.",1438381026,PHID-USER-gf5juv3z3p75bykrcrhf,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"Note: This has consequences (breakage) for some gadgets, such as 
+https://pl.wikipedia.org/wiki/Wikipedia:Narz%C4%99dzia/Odpowiedzi_z_linkami - A ""replylinks"" gadget at the Polish Wikipedia that adds an ""`[odp]`"" (or  ""`[reply]`"") link after all userpage links, and when clicked, it creates a new user_talkpage section, using the heading of the section that the [reply] link was in.
+
+E.g. Clicking [reply] at: 
+{F292406}
+then opens that user's talkpage, and starts a new section, like so:
+{F292405}
+
+",1438379382,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"@legoktm convinced us not to take this approach, at least for now.
+
+We're instead going to target the sources (e.g. {T91805}), inform early adopters of user talk of this risk ({T90383}), and keep an eye out for reports of missing messages (then fix, or help authors' fix, them to support Flow).",1426116024,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,">>! In T59989#1067648, @Mattflaschen wrote:
+>>>! In T59989#1067094, @Legoktm wrote:
+>> I still think this is a bad idea. It makes transition just a little bit easier, but it means that bots or tools that aren't Flow-aware are just going to more serious issues later on.
+>> 
+>> Tools like mw.feedback should allow Flow to override them to use its API or something.
+> 
+> I think this will be good enough for some write-only tools (they may never need to update to explicitly be Flow-aware).  Others definitely will need to, but this will hopefully ease the transition.
+
+There are no 'write-only' tools, they all have some read actions. What happens if a page is protected? Or they trigger a captcha? Or (spam|title)blacklist/AF is hit? Is Flow going to re-write all of those error cases into their wikitext equivalents? Are we going to strip ~~~~ from posts because (last I checked) that doesn't work in Flow?
+
+It will ease the transition by putting a band-aid over it, but it's going to hurt a lot more when you take that band-aid off.
+
+> We definitely plan on working towards all tools handling Flow correctly; this is just one aspect of that.
+
+Why not just do that from the beginning? If someone tries action=edit on a Flow page, return an error so they're forced to fix the tool.",1426100381,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"hmm, i guess we could be evil and give them the rev id of the page we just created in NS_TOPIC for it, but that probably wont be what they expect :)  Will have to ponder this a bit.",1424904263,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"Yeah, that sounds right.  It [looks like](https://www.mediawiki.org/wiki/API:Edit#Example) we're have to do some tricks with the revid (we also need to support at least XML and JSON, preferably all the output formats).",1424904162,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"I was initially thinking this was basically going to be a rewrite procedure:
+
+* receive api request, rewrite to flow api request
+* receive flow response, rewrite to look like normal api response.",1424903218,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"I was initially thinking this was basically going to be a rewrite procedure:
+
+* receive api request, rewrite to flow api request
+* receive flow response, rewrite to look like normal api request.",1424903203,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"We should discuss whether to try to make the output match, or just use the Flow output.",1424903160,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,">>! In T59989#1067094, @Legoktm wrote:
+> I still think this is a bad idea. It makes transition just a little bit easier, but it means that bots or tools that aren't Flow-aware are just going to more serious issues later on.
+> 
+> Tools like mw.feedback should allow Flow to override them to use its API or something.
+
+I think this will be good enough for some write-only tools (they may never need to update to explicitly be Flow-aware).  Others definitely will need to, but this will hopefully ease the transition.
+
+We definitely plan on working towards all tools handling Flow correctly; this is just one aspect of that.",1424899878,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"I still think this is a bad idea. It makes transition just a little bit easier, but it means that bots or tools that aren't Flow-aware are just going to more serious issues later on. 
+
+Tools like mw.feedback should allow Flow to override them to use its API or something.",1424894374,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"This really doesn't have anything to do with LQT except that ""It worked in LQT; it should work in Flow"".  We're not proposing any change to LQT, though.",1421290668,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"It also affects various other things, e.g. MoodBar (I know, I know, MoodBar's not widely used, but I hit it recently when testing an unrelated fix in MoodBar).
+
+Plus, I'm sure it affects many things we're not thinking of.",1420745630,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,We can't convert the https://www.mediawiki.org/wiki/VisualEditor/Feedback LQT page to Flow until this is fixed. :-(,1420737319,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,">>! In T59989#602152, @Jdforrester-WMF wrote:
+> See also bug 49636 which means that pointing MW's feedback tool at a Flow board won't work. Boo.
+
+Now {T51636}",1420667668,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,See also bug 49636 which means that pointing MW's feedback tool at a Flow board won't work. Boo.,1386179090,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+VisualEditor: Deleting a reflist along with some content and saving the page keeps the previous the content on the page,"Steps to reproduce:
+
+1.Click on the Edit button for a page
+2.Type two paragraphs
+3.Add a text with reference
+4.Add a reflist
+5.Save the page
+6.Re-open the editor
+7.Delete the reference and the reflist and the second paragraph
+8.Save the page
+Observed Result:
+The second paragraph and the text with reference did not get deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386119340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zgtluxsdmxcciykkdi5g,task_description,declined
+VisualEditor: Deleting a reflist along with some content and saving the page keeps the previous the content on the page,ryasmeen: If there is no identifiable code commit this should not be closed as FIXED but as WORKSFORME. See https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle,1387318251,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zgtluxsdmxcciykkdi5g,task_subcomment,NA
+VisualEditor: Deleting a reflist along with some content and saving the page keeps the previous the content on the page,Cannot reproduce it now,1387299115,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zgtluxsdmxcciykkdi5g,task_subcomment,NA
+VisualEditor: Deleting a reflist along with some content and saving the page keeps the previous the content on the page,"Test Environment: betalabs
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example:http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386119422,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zgtluxsdmxcciykkdi5g,task_subcomment,NA
+VisualEditor:  Print/Export tools are enabled while editing,"Actual Results:  
+When you open VisualEditor, the Print/Export section in the sidebar is still present.  It is not displayed when you open the same page in the wikitext editor.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1386098520,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jskdpgwlerlkftfmfqxh,task_description,resolved
+VisualEditor:  Print/Export tools are enabled while editing,"Change 129059 merged by jenkins-bot:
+Hide some tools when VE is open
+
+https://gerrit.wikimedia.org/r/129059",1398294414,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jskdpgwlerlkftfmfqxh,task_subcomment,NA
+VisualEditor:  Print/Export tools are enabled while editing,"Change 129059 had a related patch set uploaded by Alex Monk:
+Hide some tools when VE is open
+
+https://gerrit.wikimedia.org/r/129059",1398206983,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jskdpgwlerlkftfmfqxh,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"screenshot
+
+Steps to reproduce:
+
+1.Click on the Edit beta button
+2.Switch to Edit Source
+3.Switch back to VE
+4.Click on Cancel
+5.Reload the page
+
+
+Observed Result:
+Even after cancelling the edit, in the URL ""&veaction=edit"" still remains appended , therefore after reloading the page, VE opens up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12776}",1386028200,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_description,resolved
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"Change 118357 merged by jenkins-bot:
+mw.ViewPageTarget: Tag our state changes and reject foreign states
+
+https://gerrit.wikimedia.org/r/118357",1394659811,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"Rephrasing bug.
+
+There is explicit logic in place to not update the url sometimes. This is for when we're reacting to a popstate event (e.g. you open VisualEditor from the read page, this activates the editor without a refresh, if you then click back, the browser has already updated the url and it is now telling us to react to that, we don't want to update the url again in that case).
+
+Whenever the editor is initialised in Chrome by direct query parameter  (e.g. by clicking ""Edit"" on a page where we don't load visualeditor, e.g. MediaWiki's Edit source page), the weird initial popstate fired by Chrome was misinterpreted as a dynamic state change.
+
+Then, when leaving the editor, we still think we're reacting to a popstate event so we don't touch the url.",1394659627,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"Change 118357 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Tag our state changes and reject foreign states
+
+https://gerrit.wikimedia.org/r/118357",1394659617,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"It should be reliably reproducible on all of the above.
+
+It happens when you access veaction=edit directly in the url on a fresh load.
+
+Chrome has the nasty habit of firing a popstate event (sometimes?) on a regular load that wasn't via the history.
+
+This can be worked around by storing a piece of data with the state and using that to tell events apart (to distinguish between a state pop to one we pushed/replaced into the history, from a pop state to one some other application pushed in or one the browser is faultily firing, like Chrome does).
+
+jquery-pjax (the plugin GitHub uses to ajax navigate everywhere, powered by popState), does the same thing. Generate an ID or tag, store that with the push/replace state, and on the popstate, use that to identify ours and ignore others.
+
+This will fix lots of other potential bugs as well.
+
+Assigning back to me as it's on my mind now, might as well fix it.",1394655517,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,I can reproduce it on en.wikipedia.org but not on mediawiki.org,1394648854,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"I can't reproduce this on mediawiki.org or en.wikipedia.org, but I can locally and on en.wikipedia.beta.wmflabs.org",1394648234,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,This appears to be to do with actFromPopState in ve.init.mw.ViewPageTarget,1393868716,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,*** Bug 57902 has been marked as a duplicate of this bug. ***,1386035934,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","Screenshot
+
+Steps to reproduce:
+
+1.Click on Edit for a page
+2.Add a reference
+3.Use same reference multiple times in the page
+4.Now again while adding reference click on ""Use an Existing reference""
+
+Observed Result:
+On this dialog box beside the reference [1] the ref name "":0"" appears.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12716}",1386013680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r6noyqq7rq63j346ezyr,task_description,resolved
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","This bug seems to be back. I'm experiencing it on Chrome, and thought they were invalid references until Google-ing 
+```
+<ref name="":0"" />
+```
+
+brought me here",1463358964,PHID-USER-z5numv3lbo6csllpqb73,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations",Verified the fix in test2,1392254661,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations",Verified the fix in Betalabs,1391719877,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","Change 111626 merged by jenkins-bot:
+Hide automatic reference names
+
+https://gerrit.wikimedia.org/r/111626",1391648543,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","Change 111626 had a related patch set uploaded by Esanders:
+Hide automatic reference names
+
+https://gerrit.wikimedia.org/r/111626",1391641248,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","I noticed this while fixing the reference content bug. We used to detect the auto numbering pattern, but not any more. I think we should hide these.",1391633875,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/addimage&veaction=edit",1386013741,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Pressing ""undo"" deletes the content of an article making the ""save page"" button disable for that session","Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button for a page
+2.Type something with a link on the main page
+3.Add a template for example:Bronze Age
+4.Add another line with a reference
+5.Add reflist to the article
+6.Save the page
+7.Reopen the editor
+8.Press Delete (Deletes the first line)
+9.Press Delete again (Nothing happens)
+10.Press Undo
+
+Observed Result:
+
+1.Deletes all the content of the article.
+2.Only the blue empty highlighted box remains at the right
+3.Save Page button becomes disabled
+4.Make further edit but still the ""Save Page"" button remains disabled for that session
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12501}",1385853780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fs5utskfc7v7hpp4u6fl,task_description,resolved
+"VisualEditor: Pressing ""undo"" deletes the content of an article making the ""save page"" button disable for that session",Fixed by Ed as part of bug 57217.,1410461760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fs5utskfc7v7hpp4u6fl,task_subcomment,NA
+"VisualEditor: Pressing ""undo"" deletes the content of an article making the ""save page"" button disable for that session","Test Environment: production
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/twicedeleted",1385853865,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fs5utskfc7v7hpp4u6fl,task_subcomment,NA
+VisualEditor: newFromDocumentInsertion not implemented properly for reference/media insertions,"Currently inserting a new reference fails because of changes to newFromDocumentInsertion. The first thing that looks wrong is that the 'empty' document we generate for new references/media captions contains one paragraph and an empty internal list, I suspect we need to copy the existing internal list over.
+
+Even with that fixed it appears we aren't generating the correct sequence of transactions so they need to be reviewed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385836200,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-orj2erahi5zpz3pkgwc6,task_description,resolved
+VisualEditor: newFromDocumentInsertion not implemented properly for reference/media insertions,Fixed a while ago.,1386931739,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-orj2erahi5zpz3pkgwc6,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,"On fr.wp, see:
+https://fr.wikipedia.org/w/index.php?title=Indicateur_du_d%C3%A9veloppement_durable&diff=98505933&oldid=98352104
+
+https://fr.wikipedia.org/w/index.php?title=Dan_Flavin&diff=prev&oldid=98639433
+
+Somehow, categories (and in one case, DEFAULTSORT) move from the bottom of the page and get inside a reference.
+
+I'll very roughly translate for you the comment of Drongou, who tried to replicate but didn't manage to:
+
+<<I can't reproduce this bug (on Mac OS X) but what they have in common is the suppression of a template at the top of the page. For the reference, I have tried to manipulate one several times but that didn't lead to anything. Since it's always the first reference which is affected, I think this [...] is probably due to the template being deleted but not in an usual way. Regards.>>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385747760,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_description,invalid
+VisualEditor: All metadata moved from bottom of the page into a reference,@Pols12 I haven't seen it recently,1593613982,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,Would probably be never reproducible… @NicoV have you seen it since your last report in 2014?,1593613921,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,"Still happening, any plan on fixing this bug that has been reported for 6 months now ?
+
+https://fr.wikipedia.org/w/index.php?title=Richard_Orlinski&diff=prev&oldid=103966506",1400701246,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,"(In reply to Trevor (Wikia) from comment #1)
+> This may also be related to this kind of dirty diff:
+> https://www.mediawiki.org/w/index.
+> php?title=VisualEditor%3ATest123&diff=933910&oldid=933905
+> 
+> Essentially, it seems to happen if you edit right at the page end - I simply
+> pressed enter on the last line of text, changed the format to a heading, and
+> typed. Then pressed enter and typed a line of normal text. Saved page.
+> 
+> Wikia's ticket for this is VE-802
+
+That's unrelated. The title of this bug was a red herring: the data was moved across large distances (which didn't happen in your case) into a <ref> tag (which didn't happen in your case), and it so happened that that <ref> tag was in a heading in one case. This bug isn't related to headings, it's related to references.",1395257038,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,"This may also be related to this kind of dirty diff: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ATest123&diff=933910&oldid=933905
+
+Essentially, it seems to happen if you edit right at the page end - I simply pressed enter on the last line of text, changed the format to a heading, and typed. Then pressed enter and typed a line of normal text. Saved page.
+
+Wikia's ticket for this is VE-802",1395253868,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: Expand commands (keyboard shortcuts) to target level commands,"Currently commands are executed on the surface, and don't fire at all when not in a surface context (e.g. a dialog), however we want to have target level shortcuts (save, show menu, show help, etc.) that don't just fire when the document is fired.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385674920,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fc5nfpvuhrxs4qd4v73j,task_description,resolved
+VisualEditor: Expand commands (keyboard shortcuts) to target level commands,"Is this now fixed? We now have save-page, show-help and other target-level shortcuts…",1401473606,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fc5nfpvuhrxs4qd4v73j,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"We are trying to debug a failure with the way parsoid is set up in the Labs-Vagrant visualeditor role setup
+<https://wikitech.wikimedia.org/wiki/Talk:Labs-vagrant#Parsoid_errors_using_VisualEditor_role>
+
+When the client gets 404 errors, the error in /var/log/upstart/parsoid.log is just 
+  ERROR in localhost:Main_Page
+  Stack trace: DoesNotExistError: Page Fetch failure for null
+  worker 25269 died (1), restarting.
+
+but it doesn't say what the error is.
+ebernhardson tweaked the second line to actually say what's going wrong by adding error to the output, so the second line becomes
+
+  Stack trace: DoesNotExistError: Page Fetch failure for null : Error: Invalid URI ""undef/w/api.php?format=json&action=query&meta=siteinfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensiontags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols""
+
+, and now we can get somewhere :)
+
+Two-line patch on its way
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385598780,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_description,resolved
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Change 101336 merged by GWicke:
+More informative DoesNotExistError logging.
+
+https://gerrit.wikimedia.org/r/101336",1386964611,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Change 101336 had a related patch set uploaded by GWicke:
+More informative DoesNotExistError logging.
+
+https://gerrit.wikimedia.org/r/101336",1386964549,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,I changed the title so we can review that we do have useful logging in all handlers and wanted to keep this open till we have actually reviewed it.,1386271167,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Change 98038 merged by jenkins-bot:
+More informative DoesNotExistError logging.
+
+https://gerrit.wikimedia.org/r/98038",1386183235,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Let us leave this bug open even after this patch is merged. We should review all our response handlers and make sure we are emitting informative log messages based on the error that is returned. Looking at the code, I see that we return early in many handlers.",1386171798,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Change 98038 had a related patch set uploaded by Spage:
+More informative DoesNotExistError logging.
+
+https://gerrit.wikimedia.org/r/98038",1385599614,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+VisualEditor: Pre-annotation in a block slug should never read from the next character,"Screenshot
+
+Steps to reproduce:
+
+1.Click on the Edit button.
+2.Add a template to a page.
+3.Add another template on it.
+4.Type something on the next line of second template and format it to Preformatted ,Bold,Italic,Subscript/Underlined.
+5.Now type something between the two templates.
+
+Observed Result:
+The text added between two templates takes the format of the next line to the second template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12332}",1385588100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-brz6dzyxm67j6sqaxjdh,task_description,resolved
+VisualEditor: Pre-annotation in a block slug should never read from the next character,"Fixed some time ago, it seems.",1409596597,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-brz6dzyxm67j6sqaxjdh,task_subcomment,NA
+VisualEditor: Pre-annotation in a block slug should never read from the next character,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+Example Page:
+https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test2511?veaction=edit",1385588180,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-brz6dzyxm67j6sqaxjdh,task_subcomment,NA
+VisualEditor: Save dialog not torn down properly after edit,"Consequently the second time you edit a page, it thinks the save dialog already exists so it isn't set up again, and it fails to render.
+
+We should add a ""double edit"" workflow to our Selenium or manual tests.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385559240,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ucrlmd4fhqqckto7xviu,task_description,resolved
+VisualEditor: Save dialog not torn down properly after edit,"Change 97913 merged by jenkins-bot:
+Tear down the save dialog and remove it from memory on surface teardown
+
+https://gerrit.wikimedia.org/r/97913",1385936588,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ucrlmd4fhqqckto7xviu,task_subcomment,NA
+VisualEditor: Save dialog not torn down properly after edit,"Change 97913 had a related patch set uploaded by Esanders:
+Tear down the save dialog and remove it from memory on surface teardown
+
+https://gerrit.wikimedia.org/r/97913",1385561026,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ucrlmd4fhqqckto7xviu,task_subcomment,NA
+VisualEditor: Save dialog not torn down properly after edit,Specifically when the surface is torn down the surface overlays are detached.,1385559985,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ucrlmd4fhqqckto7xviu,task_subcomment,NA
+VisualEditor: Adjacent lists should be easily joinable,"It is quite easy to create two adjacent lists that appear to be one list (but for a small amount of extra spacing) through copy/paste or deletion. More often than not this is not what the user means semantically, so such a situation should be highlighted to the user and they should be given an easy way to fixup the code.
+
+I have yet to see an editor which does this well, but that shouldn't stop us being the first.
+
+==Steps to reproduce==
+Just as a helpful example.
+
+1. Create a list.
+1. Decide to end the list by pressing enter while on a blank bullet.
+1. Change your mind and decide to continue the list by clicking the list buttons.
+1. Now the document has two separate lists, but your mental model only has one.",1385558520,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-kjvmewrqq2l7f4hcprhb,task_description,open
+VisualEditor: External paste of list into list should unwrap pasted list,"Currently pasting a list into a list creates a sub-list. From a technical point of view this is correct (the paste contents will always be a full list) but from a user expectation point of view this will be wrong 99% of the time, so we should unwrap the pasted list so it flattens to the same list level as the target.",1385558160,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yzpiypk2d2inixzpoytj,task_description,open
+VisualEditor: There should be tests asserting we use code points as opposed to grapheme clusters,"Timo astutely observed that no tests had to be changed in https://gerrit.wikimedia.org/r/#/c/80689 despite the change from grapheme clusters to code points. I share his feeling that there should have been tests that would have been broken by that change. It's never too late to write some :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385507220,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5vxcaydqorsjojhwsdme,task_description,open
+VisualEditor: Get rid of ve.splitClusters,"It has a comment that says TODO: strip out calls to splitClusters then delete this method.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385506740,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_description,resolved
+VisualEditor: Get rid of ve.splitClusters,"Change 165433 merged by jenkins-bot:
+Getting rid of ve.splitClusters in VE core
+
+https://gerrit.wikimedia.org/r/165433",1412756070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"Change 165430 merged by jenkins-bot:
+Getting rid of ve.splitClusters in ve-mw
+
+https://gerrit.wikimedia.org/r/165430",1412756028,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"Change 165430 had a related patch set uploaded by SuchetaG:
+Getting rid of ve.splitClusters in ve-mw
+
+https://gerrit.wikimedia.org/r/165430",1412755760,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"Change 165433 had a related patch set uploaded by SuchetaG:
+Getting rid of ve.splitClusters in VE core
+
+https://gerrit.wikimedia.org/r/165433",1412755689,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"Hi, yes, we wrote ve.splitClusters because we wanted to make the document model be a list of grapheme clusters, instead of a list of raw Javascript characters (i.e. Unicode code units, so each surrogate pair like '\uD860\uDEE2' is treated as two separate entities '\uD860' and '\uDEE2').
+
+However, we've subsequently decided against that, because browsers will not always agree what constitutes a grapheme cluster. The example of Malayalam, where the font can affect the number of clusters, is one example of how problematic it could be to try to match the browser's clusterings exactly.
+
+Therefore, the DM is to remain a list of raw Javascript characters, and support related to clustering is being developed at a level on top of the DM.",1412697433,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"(In reply to Sucheta Ghoshal from comment #1)
+> Well, if we are going beyond BMP, we need to take surrogate pairs into
+> account, too. JavaScript does not do that natively, AFAIK. Would code points
+> be enough in that case?
+
+I think the idea is that at the DM layer, we won't be combining anything beyond code points, but David (CC) can confirm.",1412696779,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"**sucheta.ghoshal** wrote:
+
+Well, if we are going beyond BMP, we need to take surrogate pairs into account, too. JavaScript does not do that natively, AFAIK. Would code points be enough in that case?",1412696686,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Insert a reference with no content.
+3.Save the page
+
+Observed Result:
+
+The error message that appears on the page is ""Cite error: The opening <ref> tag is malformed or has a bad name"" where as 
+when you edit a reference (not first time insert) to an empty content the error message that appears is ""Cite error: There are <ref> tags on this page without content in them""
+
+The later one is more understandable for a user.So maybe we can change the message to the later one.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385497740,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uontdax7p5isoaavstyc,task_description,resolved
+Cite: Error message for an empty reference should be more appropriate and helpful,"VisualEditor does not any more allow adding empty reference, so the VE side of the issue is no more reproducible.
+ 
+Maybe, VE was converting empty reference as <ref/> and therefore it was showing ""Cite error: The opening <ref> tag is malformed or has a bad name"" , which seems like expected behavior. 
+
+Therefore, closing this bug.",1506637627,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"The VisualEditor does not any more allow adding empty reference, so the VE side of the issue is no more reproducible.
+ 
+Maybe, VE was converting empty reference as <ref/> and therefore it was showing ""Cite error: The opening <ref> tag is malformed or has a bad name"" , which seems like expected behavior. 
+
+Therefore, closing this bug.",1506637608,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,I'm not convinced this is a tone matter.,1446209841,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Error messages are controlled by MediaWiki interface pages. Enter `MediaWiki:Cite error ref no key` into the search box and it will open the interface page. These pages have a default, so if it is not customized, the page does not actually exist as such and when you edit it, it shows as if you are creating a brand new page but it shows the default message. If you go to `Special:AllMessages` you can enter `Cite error ref no key` and it will show the default and the custom if it exists. If you enter `Cite error` is will show all cite error interface pages.
+
+Cite.php is the software extension for all of this.
+https://www.mediawiki.org/wiki/Extension:Cite
+
+The error messages are set up through `cite body.php` and then there are language files in the i18n folder.
+
+
+The English Wikipedia is VERY customized. We use {{broken ref}} to control the message display and the namespace. Every message links to a help page. See https://en.wikipedia.org/wiki/Help:Cite_errors#Error_messages for a list of all messages. Each help page has a Technical section that has a link to the MediaWiki interface page.",1425242197,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,,1425242226,PHID-USER-nk32pihw2thyf2uczoq5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,,1425241010,PHID-USER-nk32pihw2thyf2uczoq5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Ah.
+
+<ref /> is indeed invalid and triggers `MediaWiki:Cite error ref no key` which displays `Invalid <ref> tag; refs with no content must have a name` by default and is customized to `The opening <ref> tag is malformed or has a bad name (see the help page).` on the English Wikipedia which is a better description.",1425236652,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"{F51632} 
+when i entered the reference with no content still i had this error
+Cite error: Invalid <ref> tag;
+refs with no content must have a name
+{F51634}
+so what should i do
+both of them are set to the same message in my en.json
+""cite_error_ref_no_key"": ""Invalid <code>&lt;ref&gt;</code> tag;\nrefs with no content must have a name"",
+	""cite_error_ref_no_input"": ""Invalid <code>&lt;ref&gt;</code> tag;\nrefs with no name must have content"",
+",1425236169,PHID-USER-nk32pihw2thyf2uczoq5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"{F51632} 
+when i entered the reference with no content still i had this error
+Cite error: Invalid <ref> tag;
+refs with no content must have a name
+
+{F51634}",1425235969,PHID-USER-nk32pihw2thyf2uczoq5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Looking at the original issue:
+
+----
+1.Click on the ""Edit"" button
+2.Insert a reference with no content.
+3.Save the page
+
+Observed Result
+
+The error message that appears on the page is `Cite error: The opening <ref> tag is malformed or has a bad name.`
+----
+
+I don't see this. I create a test page with <ref></ref> and save. The page shows Cite error: There are <ref> tags on this page without content in them (see the help page). which is customized on the English Wikipedia from `MediaWiki:Cite error ref no input`. This is correct.",1425234889,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Looking at the original issue:
+
+----
+1.Click on the ""Edit"" button
+2.Insert a reference with no content.
+3.Save the page
+
+Observed Result:
+
+The error message that appears on the page is `Cite error: The opening <ref> tag is malformed or has a bad name.`
+----
+
+I don't see this. I create a test page with <ref></ref> and save. The page shows Cite error: There are <ref> tags on this page without content in them (see the help page). which is customized on the English Wikipedia from `MediaWiki:Cite error ref no input`. This is correct.",1425234871,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Looking at the original issue:
+
+----
+1.Click on the ""Edit"" button
+2.Insert a reference with no content.
+3.Save the page
+
+Observed Result:
+
+The error message that appears on the page is ""Cite error: The opening <ref> tag is malformed or has a bad name.""
+----
+
+I don't see this. I create a test page with <ref></ref> and save. The page shows ""Cite error: There are <ref> tags on this page without content in them (see the help page)."" which is customized on the English Wikipedia from 'MediaWiki:Cite error ref no input'. This is correct.",1425234812,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful," ""cite_error_ref_no_key"": ""Invalid <code>&lt;ref&gt;</code> tag;\nrefs with no content must have a name"", is already set to this in the local environment.
+should i create a patch for this.",1425231591,PHID-USER-nk32pihw2thyf2uczoq5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,Rits: See https://en.wikipedia.org/wiki/Help:Cite_errors/Cite_error_ref_no_key,1425230436,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"i am working on this bug i am unable to generate  ""Cite error: The opening <ref> tag is malformed or has a bad name"" although i am able to generate the  ""Cite error: There are <ref> tags on this page without content in them"" . ",1425227409,PHID-USER-nk32pihw2thyf2uczoq5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"The test page in question includes '<ref />' which is invalid. This triggers 'MediaWiki:Cite error ref no key'.
+
+The default error message is ""Invalid <ref> tag; refs with no content must have a name""
+
+The customized message on enwiki is ""The opening <ref> tag is malformed or has a bad name (see the help page)."" The linked help page explains the issue in depth.",1405983491,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"The examples are on the English Wikipedia, where the cite errors are heavily customized.
+
+* ""Cite error: The opening <ref> tag is malformed or has a bad name"" is through ""MediaWiki:Cite error ref no key""
+
+
+* ""Cite error: There are <ref> tags on this page without content in them"" is through ""MediaWiki:Cite error ref no input""",1398941036,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,(Not a VisualEditor-specific issue.),1392747737,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Created attachment 13913
+Screenshot of the error
+
+**Attached**: {F12187}",1385497954,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Created attachment 13912
+screenshot
+
+**Attached**: {F12186}",1385497847,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"To figure out:
+* Does this work in all browsers we support? I have anecdotally confirmed support in Firefox 25 and Chrome 30
+* Protocol-relative URLs in <base> are broken, because documents created this way don't have a creator context or whatever.
+
+Benefits:
+* Not a hack involving iframes :)
+* Faster than the iframe hack
+* Does not have issues with HTTPSEverywhere in Firefox
+
+For the <base> issue, it looks like something like this will work:
+
+>>> d.querySelector('base')
+<base href=​""/​/​example.com"">​
+>>> d.baseURI
+null
+>>> d.querySelector('base').getAttribute('href')
+""//example.com""
+>>> d.querySelector('base').setAttribute('href', 'http://example.com');
+undefined
+>>> d.baseURI
+""http://example.com/""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385472240,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_description,resolved
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"Change 120836 merged by jenkins-bot:
+Use DOMParser in ve.createDocumentFromHtml() if available
+
+https://gerrit.wikimedia.org/r/120836",1395875951,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"(In reply to Roan Kattouw from comment #2)
+> ...or use DOMParser, which actually does *precisely* what we want. We could
+> use it in browsers where it's available as a replacement for
+> ve.createDocumentFromHtml, because it's supported only in FF 12+, Chrome 30+
+> (!), IE 10+, Opera 17+ (!) and not at all (!!) in Safari.
+This is what I ended up going with.",1395771178,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"Change 120836 had a related patch set uploaded by Catrope:
+Use DOMParser in ve.createDocumentFromHtml() if available
+
+https://gerrit.wikimedia.org/r/120836",1395771153,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"...or use DOMParser, which actually does *precisely* what we want. We could use it in browsers where it's available as a replacement for ve.createDocumentFromHtml, because it's supported only in FF 12+, Chrome 30+ (!), IE 10+, Opera 17+ (!) and not at all (!!) in Safari.",1392850210,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"(In reply to comment #0)
+> For the <base> issue, it looks like something like this will work:
+>
+I read the spec some more and it looks like the trick I outlined is actually something that the spec specifically covers and says should work.
+
+Other issue: we can't parse doctypes or <html> tags this way, so we can't respect non-HTML5 doctypes and we won't see any attributes on the <html> element. This isn't a problem for Parsoid documents at this time, although it'll be pretty annoying if we ever want to respect things like <html lang=""nl"">.",1387370415,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28proposals%29&oldid=582561035#Proposed_new_Draft_namespace
+
+I believe this discussion demonstrates sufficient community consensus to create a ""Draft"" namespace on the English Wikipedia.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28proposals%29&oldid=582561035#Proposed_new_Draft_namespace
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57315",1385425560,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-atmvpvsegseglymt64gn,task_description,resolved
+"Create ""Draft"" namespace on the English Wikipedia","thx, i have done. 
+
+i suggest this namespace be added to MediaWiki. ",1522881510,PHID-USER-klaycnqc3osjrltt7lu4,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","@Johnywhy No, but you can setup this yourself following https://www.mediawiki.org/wiki/Manual:Using_custom_namespaces
+
+You can also check the changes above if you've Visual Editor or wants to configure robotx.txt to discourage crawling",1522880965,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","hi, i noticed the Draft namespace doesn't exist in my off-the-shelf MediaWiki installation 1.30. Any plans for that? -thx",1522880797,PHID-USER-klaycnqc3osjrltt7lu4,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Thank you Matt, Steven, and everyone else for your work on this. :-)",1387337581,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","This is deployed to English Wikipedia.
+
+You can also resume testing on Beta.  The old drafts are at http://en.wikipedia.beta.wmflabs.org/wiki/Special:PrefixIndex/Draft .  They can be moved back into the Draft space if desired.",1387326342,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Change 97675 merged by jenkins-bot:
+Create ""Draft"" namespace on the English Wikipedia
+
+https://gerrit.wikimedia.org/r/97675",1387325866,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia",The VE stuff has now been included into the main change (https://gerrit.wikimedia.org/r/#/c/97675/).,1387318226,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia",VisualEditor will be enabled in the namespace for opt-in users.  See https://www.mediawiki.org/wiki/Draft_namespace and https://gerrit.wikimedia.org/r/#/c/102311/ .,1387317317,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #33)
+> FYI: we're testing the new namespace on Labs
+> (http://en.wikipedia.beta.wmflabs.org). Please help give it a try.
+
+Thank you for testing.
+
+Please hold off on creating additional Drafts for now, until it is deployed (this is due to the namespace ID change mentioned at https://bugzilla.wikimedia.org/show_bug.cgi?id=57315#c44).",1387275142,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #29)
+> Change 99600 merged by jenkins-bot:
+> Test under-review English Wikipedia draft namespace on Labs
+> 
+> https://gerrit.wikimedia.org/r/99600
+
+FYI: we're testing the new namespace on Labs (http://en.wikipedia.beta.wmflabs.org). Please help give it a try.",1386634272,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","I used to have very strong opinions on easy with shell bugs, but that was back in the svn days where you actually needed to be shell to do anything useful on these bugs. Now anyone can submit changes, so that argument is less compelling.",1386422563,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #30)
+> We don't use easy keyword for shell bugs, as they're advertised not as ""easy
+> bug to write"" but as ""easy bugs for new contributors to discover the code"".
+> Shell bugs ask a knowledge of community consensus, and so they aren't
+> suitable for newcomers.
+
+I'm not sure this logic is sound. The ""easy"" keyword is associated with technical complexity. Couldn't we presume that the person adding the ""easy"" keyword is capable of making a full judgment of the bug, evaluating both the technical complexity and the social implications?
+
+That is, committing a change for an ""easy"" shell ticket still allows new users to learn and experience Git and code review without them needing to be able to divine Wikimedia wiki consensus. On bugs where consensus, technical or otherwise, is unclear, there's a strong case for not marking the bug as ""easy."" I don't believe that's the case here or in many other cases of ""shell"" bugs.",1386407353,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #8)
+> (In reply to comment #6)
+> > We're talking about a two-line configuration change here.
+> 
+> Probably a few more than two lines to create the namespace, the talk
+> namespace,
+> and set noindex. Maybe a half-dozen to a dozen lines? In any case, this seems
+> fairly easy to implement to me.
+
+We don't use easy keyword for shell bugs, as they're advertised not as ""easy bug to write"" but as ""easy bugs for new contributors to discover the code"". Shell bugs ask a knowledge of community consensus, and so they aren't suitable for newcomers.",1386320427,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Change 99600 merged by jenkins-bot:
+Test under-review English Wikipedia draft namespace on Labs
+
+https://gerrit.wikimedia.org/r/99600",1386302568,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Change 99600 had a related patch set uploaded by Mattflaschen:
+Test under-review English Wikipedia draft namespace on Labs
+
+https://gerrit.wikimedia.org/r/99600",1386298083,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**equazcion** wrote:
+
+> (In reply to comment #25)
+> > I have a hard time understanding what is going on here? If this was any other
+> > wiki, we would note that their is community consensus, and implement the
+> > change.
+> > 
+> > The only thing slightly iffy thing here is to be able to let anons create
+> > pages
+> > in this namespace - that might require someone taking 10 seconds writing a
+> > hook
+> > (Or even better, someone fixing mediawiki so we have proper per-namespace
+> > permissions). However that can easily be done later. the robots thing is
+> > already a config option.
+> > 
+> > Furthermore, all these various ""config"" related changes are trivial to change
+> > after the fact if people discover they want something different.
+> > 
+> > New namespaces get created for other wikis all the time. This has
+> > traditionally
+> > been something that has entirely been up to the community to decide for
+> > themselves. I don't understand why enwiki gets treated so differently.
+> > 
+> > >Key minimum requirements for launch are being hashed out at
+> > >https://www.mediawiki.org/wiki/Draft_namespace 
+> > 
+> > Kind of seems odd this is being written up on mediawiki.org, for something
+> > that
+> > is in essence a config change coming out of enwikipedia community. Its not
+> > like
+> > there are non-user facing technical hurtles to surmount. There's no new db
+> > schema being proposed or anything like that.
+
+Bawolff has a hard time understanding what most of us are having a hard time understanding. The piece you're missing, Bawolff, is that after this new namespace was proposed and passed as simply a new namespace, Steven Walling took it over by submitting the supposed bug for implementation (bug 57315), which was actually for something much more than a new namespace. 
+
+While I'm sure he originally had the best of intentions, it was pointed out thereafter that his plan for implementation was markedly different from the accepted proposal that was supposed to have originated it. Rather than admit his error as a good Wikipedia administrator should, he's made every effort to outwardly cling to his original position like a good infallible corporate manager would: He attempted to pass off the bloat in his proposed implementation as ""requirements"" for the namespace, when they had actually been some new ideas he wanted to tinker with. The claim that these were ""requirements"" was again pointed out as erroneous, but he still insisted on making some list of requirements regardless, rather than simply letting it go. This is the show of complexity where none is actually necessary that you're seeing now and have astutely pointed out. 
+
+And this is, in my mind, an example of the type of behavior that has brought the relationship between the WMF and the Wikipedia community to the sour state it is. And it felt good to get that out. 
+
+Hope we can get some actual stuff done now.",1385604994,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #25)
+> I have a hard time understanding what is going on here? If this was any other
+> wiki, we would note that their is community consensus, and implement the
+> change.
+> 
+> The only thing slightly iffy thing here is to be able to let anons create
+> pages
+> in this namespace - that might require someone taking 10 seconds writing a
+> hook
+> (Or even better, someone fixing mediawiki so we have proper per-namespace
+> permissions). However that can easily be done later. the robots thing is
+> already a config option.
+> 
+> Furthermore, all these various ""config"" related changes are trivial to change
+> after the fact if people discover they want something different.
+> 
+> New namespaces get created for other wikis all the time. This has
+> traditionally
+> been something that has entirely been up to the community to decide for
+> themselves. I don't understand why enwiki gets treated so differently.
+> 
+> >Key minimum requirements for launch are being hashed out at
+> >https://www.mediawiki.org/wiki/Draft_namespace 
+> 
+> Kind of seems odd this is being written up on mediawiki.org, for something
+> that
+> is in essence a config change coming out of enwikipedia community. Its not
+> like
+> there are non-user facing technical hurtles to surmount. There's no new db
+> schema being proposed or anything like that.
+
+I suggest you check out the mediawiki.org page and the associated bug 57315. They both include some explanation, including the technical discussions involved about implementation, and about future plans.",1385596480,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","I have a hard time understanding what is going on here? If this was any other wiki, we would note that their is community consensus, and implement the change.
+
+The only thing slightly iffy thing here is to be able to let anons create pages in this namespace - that might require someone taking 10 seconds writing a hook (Or even better, someone fixing mediawiki so we have proper per-namespace permissions). However that can easily be done later. the robots thing is already a config option.
+
+Furthermore, all these various ""config"" related changes are trivial to change after the fact if people discover they want something different.
+
+New namespaces get created for other wikis all the time. This has traditionally been something that has entirely been up to the community to decide for themselves. I don't understand why enwiki gets treated so differently.
+
+>Key minimum requirements for launch are being hashed out at
+>https://www.mediawiki.org/wiki/Draft_namespace 
+
+Kind of seems odd this is being written up on mediawiki.org, for something that is in essence a config change coming out of enwikipedia community. Its not like there are non-user facing technical hurtles to surmount. There's no new db schema being proposed or anything like that.",1385596241,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Key minimum requirements for launch are being hashed out at https://www.mediawiki.org/wiki/Draft_namespace .  Some are pretty definite already (e.g. NOINDEX), while others are not 100% certain yet.  We may also have omitted some questions, so if you think of any that need to be resolved before launch, add them.",1385595280,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #22)
+> Ori's point was partly that acting in a hasty manner and populating the
+> namespace with content right, so that it's less flexible to essential changes
+> in the near future, *will* make the situation worse.
+
+Worse than hypothetical future is not worse than the present, so it's still a gradual improvement. Populating a ""drafts"" namespace doesn't seem to pose any risk to me: it's completely normal to move pages in and out new namespaces (Wikipedia<->Draft in this case) and this namespace is supposed to be purged regularly anyway. If you're so worried about workload, you can run a move script yourself when it's time; the only real risk when creating namespace is forgetting to run namespaceDupes.php‎.",1385537497,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #21)
+> (In reply to comment #19)
+> 
+> I agree with most of what you wrote, though a lot of it is relevant to bug
+> 57315 rather than this bug.
+> 
+> > Steven Walling is well-positioned to enlist some developer time within the
+> > Foundation for this project. If he is asking for additional time to grok the
+> > requirements, the sensible and gracious thing to do is to grant it. If you
+> > can railroad the patch through today, you can do it two weeks from now, too.
+> 
+> Requirements are still being gathered. As I understand it, no implementation
+> ideas have been formally proposed yet, much less coded, and we're fast
+> approaching the U.S. holiday season. I don't imagine we'll see any real work
+> on
+> bug 57315 before 2014. While it's possible to wait a few weeks (or months) to
+> add this namespace, I don't see any benefit to doing so. The current system
+> is
+> so bad and so hackish that there's very little that could make it worse.
+
+Ori's point was partly that acting in a hasty manner and populating the namespace with content right, so that it's less flexible to essential changes in the near future, *will* make the situation worse. Or at the very least, replicate the current bad situation. Considering the patch you put up for review literally does replicate the current problem (IPs can't create actual drafts, just Talk pages), I am convinced by this argument. 
+
+What I've asked for, and stated on-wiki, is that we need to at least do two things:
+
+1). Actually write down the requirements for the namespace, and agree on them. I can commit to making this happen _far_ before 2014. Ideally in the current week.
+2). Test the functionality on Labs or similar environment before deploying, with feedback from the community. People have responded positively to this idea, and we're using it with features like Flow as well. Giving people a chance to test drive the new namespace before dropping it on enwiki seems wise to me. 
+
+Neither of these things necessarily require that all the potential features extending and improving the namespace be implemented. I do believe in releasing something that's ""minimum viable product"" quickly as is reasonable. But considering we have no agreement on what the minimum viable product is, we need to settle that first.",1385516798,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #19)
+
+I agree with most of what you wrote, though a lot of it is relevant to bug 57315 rather than this bug.
+
+> Steven Walling is well-positioned to enlist some developer time within the
+> Foundation for this project. If he is asking for additional time to grok the
+> requirements, the sensible and gracious thing to do is to grant it. If you
+> can railroad the patch through today, you can do it two weeks from now, too.
+
+Requirements are still being gathered. As I understand it, no implementation ideas have been formally proposed yet, much less coded, and we're fast approaching the U.S. holiday season. I don't imagine we'll see any real work on bug 57315 before 2014. While it's possible to wait a few weeks (or months) to add this namespace, I don't see any benefit to doing so. The current system is so bad and so hackish that there's very little that could make it worse.",1385514221,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #16)
+> I might even support it, once it's clear what the proposed changes are (all
+> I've seen spelled out so far are a new landing page and some sort of special
+> permission changes, which are both still pretty vague).
+
+It's vague because that's one of the things we're still trying to figure out (before adding the namespace).",1385505493,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #4)
+> As I stated at the other bug, these are not questions that need to block
+> creation of the namespace.
+
+There are no blockers; you can have the namespace. I do think it is being rushed, though.
+
+I never quite understood how consensus is determined, so I may be getting this wrong, but reading over the RFC, I think a detect a shared conviction that a namespace by itself may not do the trick, and that some additional software support may be required. This much is entailed by the very thought of having a namespace in the first place, right?
+
+Once the namespace exists, it will begin to be populated with content, and at that point the range of things you can practically do with it are severely limited. For example: MediaWiki provides an abstract framework for expressing an edit and review workflow called ContentHandler (<http://www.mediawiki.org/wiki/Manual:ContentHandler>). Taking the default content handler for articles (WikitextContentHandler) as a starting point and extending it so that it provides guided page creation and peer review interfaces seems like a potentially fruitful direction to take, and saddling it with the additional requirement of migrating existing content is a great way to ensure that it will never get done.
+
+Steven Walling is well-positioned to enlist some developer time within the Foundation for this project. If he is asking for additional time to grok the requirements, the sensible and gracious thing to do is to grant it. If you can railroad the patch through today, you can do it two weeks from now, too.
+
+I would recommend making the mapping of requirements collaborative by provisioning a MediaWiki instance in Labs, granting shell access to all interested parties, and using it as a staging area for hashing out how the namespace would work and how its purpose and function would be presented to editors.",1385492693,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #17)
+> I am fine with whichever proposal
+> gets
+> this done, as long as it does through whatever procedure it is normally
+> expected to.
+
+Don't worry: the procedure is [[m:Requesting wiki configuration changes]]. It seems to be clear that there is consensus and we already have a patch, so now you only need the patch to be approved by a shell user, after it's verified that the code in question does what asked. Typically, that takes about a week or two of waiting; namespace creation is among the simplest and most routinary configuration changes happening in here, so I don't expect any problem.",1385486372,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #14)
+> (In reply to comment #2)
+> > (In reply to comment #1)
+> > > Like I said on bug 57315, there are still too many unanswered questions about
+> > > this namespace to roll it out in a hasty way.
+> > 
+> > Does anyone else share your view?
+> 
+> I fully share this view.  
+
+As do I. If a quick six-lines-of-code patch can work, then that is good. But if the long run requires a more comprehensive approach, then so it be. As far as I am concerned, the enwiki just needs the namespace in a reasonable amount of time. If those two requirements are met, I am fine with whichever proposal gets this done, as long as it does through whatever procedure it is normally expected to.",1385474421,PHID-USER-65pjzcmoby2fsgzdrfjq,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**equazcion** wrote:
+
+(In reply to comment #14)
+> I fully share this view.  I've been toying with the idea of an extension here
+> for some time.  There is this new namespace, there is the new userright that
+> the community agreed upon, there are the common complaints that AfC templates
+> and scripts don't do this or that (and can't be modified as the wiki stands
+> to
+> without creating an on-by-default gadget or adding code to
+> MediaWiki:Common.js
+> or possibly by creating a guided tour (which is a fairly new option that was
+> introduced as I've been developing the extension)).  There are a LOT of
+> factors
+> that need to go into draft creation alone, not to mention I think (as I
+> stated
+> in bug 57315) that I think requested articles could be rolled into articles
+> for
+> creation and the whole process could be streamlined.  I'm constantly seeing
+> stuff about editor retention and we need to do this and that and that is
+> great,
+> but what I have a problem with is the fact that our current fairly difficult
+> to
+> use system turns new editors away... Maybe stating the obvious, but if there
+> are fewer new editors, then there is a much smaller pool to work from for
+> retention.
+
+It's fine that you share Steven's view on that -- but the question was whether these things are a block to the Draft namespace implementation. An extension may be a good idea and I don't necessarily dispute that, but it wasn't part of this proposal and it regards changes that should be proposed separately. I might even support it, once it's clear what the proposed changes are (all I've seen spelled out so far are a new landing page and some sort of special permission changes, which are both still pretty vague).",1385472289,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #4)
+> As I stated at the other bug, these are not questions that need to block
+> creation of the namespace. It rather seems apparent that you saw this
+> proposal
+> as something other than it was -- a more substantial change to AFC that you
+> had
+> already envisioned prior -- but it wasn't, and the closure states that pretty
+> clearly. 
+> 
+> Anyone is allowed to create drafts because anyone was allowed to before. This
+> is just a change to their location.
+> 
+> Publishing drafts will continue to merely require a move to mainspace,
+> because
+> that's all that was required before. 
+> 
+> We don't need to tell anyone anything other than through altered
+> documentation
+> at AFC, because nothing other than that will be changing. 
+> 
+> Phrasing these added proposals as questions doesn't make them requirements
+> that
+> apply to this proposal. They are merely possible additions that should be
+> proposed and discussed separately. As concerns this proposal, we need only
+> create a draft namespace.
+
+Wait, IP editors aren't allow to create pages in this new draft: namespace?  They will still have to create in Draft_talk:?  At least that's what I'm reading here, exactly the same as before only people will use ""Draft( talk):"" instead of ""Wikipedia( talk):Articles for creation/""?",1385471608,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #2)
+> (In reply to comment #1)
+> > Like I said on bug 57315, there are still too many unanswered questions about
+> > this namespace to roll it out in a hasty way.
+> 
+> Does anyone else share your view?
+
+I fully share this view.  I've been toying with the idea of an extension here for some time.  There is this new namespace, there is the new userright that the community agreed upon, there are the common complaints that AfC templates and scripts don't do this or that (and can't be modified as the wiki stands to without creating an on-by-default gadget or adding code to MediaWiki:Common.js or possibly by creating a guided tour (which is a fairly new option that was introduced as I've been developing the extension)).  There are a LOT of factors that need to go into draft creation alone, not to mention I think (as I stated in bug 57315) that I think requested articles could be rolled into articles for creation and the whole process could be streamlined.  I'm constantly seeing stuff about editor retention and we need to do this and that and that is great, but what I have a problem with is the fact that our current fairly difficult to use system turns new editors away... Maybe stating the obvious, but if there are fewer new editors, then there is a much smaller pool to work from for retention.",1385471383,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","I've not read the discussion but I have to say the closure is quite straightforward: «the heart of the proposal: a new namespace for Drafts [...] This community discussion does not change the AfC process». It obviously doesn't entail any extension, nor special user permissions for the namespace for that matter; those can come later if wanted.",1385447453,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Change 97675 had a related patch set uploaded by MZMcBride:
+Create ""Draft"" namespace on the English Wikipedia
+
+https://gerrit.wikimedia.org/r/97675",1385439190,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #6)
+> > We still need to specify things like:
+> > 
+> > * who is allowed to create drafts. (e.g. Are anonymous users allowed to do
+> > so?
+> > I assume so but the proposal summary and closure don't specify.)
+> > * how to publish drafts
+> > * who is allowed to publish drafts
+> > * how do we tell users they can create/publish drafts, on search, redlinks,
+> > and other places
+> > * do we want to let people make drafts of pages that already exist?
+> 
+> None of this is relevant to adding a new namespace and you know this.
+
+All of those questions are relevant.  Some I certainly consider blockers.  For example, I am strongly inclined to determine an initial permission model before we deploy it (that's not the only one).  
+
+It is irrelevant how many lines it takes to create a dumb namespace.  The questions are how it will function initially (which may include A/B testing multiple possibilities) and how it will relate to other features.",1385437989,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #3)
+> (In reply to comment #2)
+
+> * who is allowed to create drafts. (e.g. Are anonymous users allowed to do
+> so?
+> I assume so but the proposal summary and closure don't specify.)
+
+I've left Tom Morris (the RfC closer) a note asking him to clarify - [[Special:Permalink/583319065]].
+
+That said, I don't think that question specifically blocks the creation of the namespace, a hook can be added to userCan later on to allow anon's to create pages in it.",1385429337,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**equazcion** wrote:
+
+(In reply to comment #7)
+> I'm not talking about articles for creation at all. That's a community
+> process,
+> not a software feature that has direct overlap with a drafts namespace, with
+> the exception of what we want to appear on search.
+
+The accepted proposal we seek to implement here doesn't concern any software feature. If you want one, propose one separately. You've stated nothing that couldn't also be applied without a draft namespace, or after it's already created. They are separate suggestions, and they may be useful ones, but still have no bearing on the implementation of this namespace.",1385429155,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #6)
+> We're talking about a two-line configuration change here.
+
+Probably a few more than two lines to create the namespace, the talk namespace, and set noindex. Maybe a half-dozen to a dozen lines? In any case, this seems fairly easy to implement to me.",1385429101,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+> None of this is relevant to adding a new namespace and you know this.
+> 
+> If you want to improve the articles for creation process, great! I've filed
+> several bugs in this area. :-)  No objections from me.
+> 
+> But the two ideas (adding a new namespace on the English Wikipedia and
+> improving the articles for creation process) are not tied to each other in
+> any
+> meaningful way. We're talking about a two-line configuration change here.
+
+I'm not talking about articles for creation at all. That's a community process, not a software feature that has direct overlap with a drafts namespace, with the exception of what we want to appear on search.",1385428945,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #3)
+> This is not about consensus. We don't know basic things about how the
+> namespace would work.
+
+I'm pretty sure we know how namespaces work. :-)
+
+> We still need to specify things like:
+> 
+> * who is allowed to create drafts. (e.g. Are anonymous users allowed to do
+> so?
+> I assume so but the proposal summary and closure don't specify.)
+> * how to publish drafts
+> * who is allowed to publish drafts
+> * how do we tell users they can create/publish drafts, on search, redlinks,
+> and other places
+> * do we want to let people make drafts of pages that already exist?
+
+None of this is relevant to adding a new namespace and you know this.
+
+If you want to improve the articles for creation process, great! I've filed several bugs in this area. :-)  No objections from me.
+
+But the two ideas (adding a new namespace on the English Wikipedia and improving the articles for creation process) are not tied to each other in any meaningful way. We're talking about a two-line configuration change here.",1385428674,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #4)
+> As I stated at the other bug, these are not questions that need to block
+> creation of the namespace. 
+
+Deciding the basics of who can do what in a new namespace, and how, are things that block creating a new namespace. 
+
+I really don't see why you're in such a huge hurry. This is quite a large new feature, so understanding the basics of how it will function in relation to regular page creation, the permissions involved, and so on seem quite obviously basic things we need to figure out before we deploy a major new namespace to English Wikipedia.",1385428346,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**equazcion** wrote:
+
+As I stated at the other bug, these are not questions that need to block creation of the namespace. It rather seems apparent that you saw this proposal as something other than it was -- a more substantial change to AFC that you had already envisioned prior -- but it wasn't, and the closure states that pretty clearly. 
+
+Anyone is allowed to create drafts because anyone was allowed to before. This is just a change to their location.
+
+Publishing drafts will continue to merely require a move to mainspace, because that's all that was required before. 
+
+We don't need to tell anyone anything other than through altered documentation at AFC, because nothing other than that will be changing. 
+
+Phrasing these added proposals as questions doesn't make them requirements that apply to this proposal. They are merely possible additions that should be proposed and discussed separately. As concerns this proposal, we need only create a draft namespace.",1385427644,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > Like I said on bug 57315, there are still too many unanswered questions about
+> > this namespace to roll it out in a hasty way.
+> 
+> Does anyone else share your view?
+
+This is not about consensus. We don't know basic things about how the namespace would work. We still need to specify things like:
+
+* who is allowed to create drafts. (e.g. Are anonymous users allowed to do so? I assume so but the proposal summary and closure don't specify.)
+* how to publish drafts
+* who is allowed to publish drafts
+* how do we tell users they can create/publish drafts, on search, redlinks, and other places
+* do we want to let people make drafts of pages that already exist?
+
+There are numerous other smaller details to work out as well.",1385427328,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #1)
+> Like I said on bug 57315, there are still too many unanswered questions about
+> this namespace to roll it out in a hasty way.
+
+Does anyone else share your view?",1385426645,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+Like I said on bug 57315, there are still too many unanswered questions about this namespace to roll it out in a hasty way. Please be patient. It's only been a week since the RFC on enwiki was closed.",1385426291,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"The browser tests for MobileFrontend should be triggered by Gerrit just like it is going to be the case for ULS (T54120) or VisualEditor (T55691).
+
+The tests need to be carefully filtered out since they are expecting content or behavior which are not to be found on a freshly installed wiki.
+
+
+CC:
+- Zeljkof  our Selenium Guru
+- Arthur our Mobile scrum master
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53691
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52120",1385415180,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-bphj5ytqpxc666bbt2xo,task_description,resolved
+browsertests: triggers for MobileFrontend,Reflecting the true state.,1440045549,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"We do not have the capacity yet to had browser tests on patchset proposals. The VE (T55691) and ULS (T54120) jobs have been removed because they were too slow and ill conceived.
+
+We will revisit it when we have improved the browser test speed (ex: {T92613}) and most importantly the CI isolation project which will provide us fresh VM to install all of what we need ensuring a clean environment.
+
+I guess when we are ready we will poke the parent task {T55697}.",1427208623,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,Adding Dan to this bug as his work on MF tests in Vagrant will probably inform some of this.,1405455476,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"Change 97497 abandoned by Hashar:
+QA: profile for default settings
+
+Reason:
+Indeed those preferences have been moved elsewhere (mediawiki selenium gem).
+
+https://gerrit.wikimedia.org/r/97497",1391529850,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,Patchset 9 of https://gerrit.wikimedia.org/r/#/c/97497/ pass on a fresh wiki with mobilefrontend having no specific configuration. That is done by ignoring any scenario relying on a specific feature/setting on the target wiki.,1386692405,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"Most of the tests do not work against a freshly installed wiki. Either because of Watir timeout or because the test is expecting something which is only on some specific wiki.
+
+The features definition need a bunch of improvements before we can trigger the tests from Gerrit.",1385479428,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"Change 97497 had a related patch set uploaded by Hashar:
+browsertests: profile for default settings
+
+https://gerrit.wikimedia.org/r/97497",1385478671,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+VisualEditor: Make fakeIme QUnit testing more rigorous,"The fakeIme tests pass IME-like event sequences into the CE Surface and check that it behaves reasonably. Currently the tests are too weak, in that they don't detect certain problematic behaviour:
+
+1. Calls to the simulated preventDefault do nothing at all.
+
+2. Some tests are disabled because they fail.
+
+3. Only plain text in a single blank paragraph is tested.
+
+4. In real usage, changing the CE surface content/selection during input will close the candidate window and commits the candidate text. The tests currently do not check for this. The test data does not show which pieces of text are candidates, since there is no way to detect this from Javascript, but we can infer that at least any text which is subsequenctly changed was a candidate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385387460,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-fxi2rdyqsib2css4ztr4,task_description,open
+VisualEditor:  Please add a shortcut for adding a reference to a page (?which?),"Intention:
+Add a reference
+
+Steps to Reproduce:
+1. Took hands off the keyboard.
+2. Grabbed mouse.
+3. Clicked ""More"" menu.
+4. Scrolled down.
+5. Clicked on ""Reference"".
+
+Actual Results:  
+Works as designed.
+
+Expected Results:  
+That it would work better than as designed:  Leave hands on keyboard, press a couple of keys, and have the reference dialog pop open.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385161380,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jxecea6ezbybvmmufndn,task_description,duplicate
+VisualEditor:  Please add a shortcut for adding a reference to a page (?which?),"My first choice is ctrl-alt-r, which unfortunately is in use as a shortcut to open Special:RecentChanges, and command-R is in use by the browsers to reload pages.
+
+I'll personally use this enough that I'll be able to get used to just about anything.  Maybe ctrl-alt-1, if you want this to work across multiple languages?  Adding citations has ""number one"" importance to many Wikipedia editors.",1385400305,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jxecea6ezbybvmmufndn,task_subcomment,NA
+VisualEditor:  Please add a shortcut for adding a reference to a page (?which?),"Let's avoid symbols not available on non-English keyboards for a start, like backslash :p",1385397735,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jxecea6ezbybvmmufndn,task_subcomment,NA
+VisualEditor:  Please add a shortcut for adding a reference to a page (?which?),What would you suggest as the shortcut?,1385394792,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jxecea6ezbybvmmufndn,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Copied from bug 43058 
+
+Screenshot of editing a math block
+
+Some small tweaks are needed to the dialog box. Editing the last equation at
+https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+there are a a few problems
+
+1) The dialog obscures the actual equation
+2) The dlalog is too small to see the whole source text of the equation
+
+This could be solved the making the dialog, moveable and resizeable.
+
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=12223
+
+//attachment missing in source//",1385145960,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_description,open
+Allow the VE dialog for math elements to be movable and resizable,"In T51969 TrevorParscal write
+
+> The idea of the dialog being modal is that you aren't multi-tasking with it at all.
+
+There is a question as to whether a modal dialog is appropriate here or a modeless dialog. A typical modal dialog would be password entry which must happen before continuing. 
+
+Here we are multi-tasking editing an equation is a subtask of the job of editing the whole page. You do want to switch back and forward to see how changing the equation will affect the look of the whole page. To me, the use-case suggests a modeless dialog is appropriate here. ",1573915077,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,">>! In T59437#5658604, @John_Broughton wrote:
+> https://ux.stackexchange.com/questions/81134/should-modal-dialogs-be-movable seems to show a (rough) consensus that when a proposed solution to a dialog is to make it moveable, the dialog itself is poorly designed. That implies looking for a different solution that addresses the underlying user problem.
+
+See discussion of this in T51969 ",1573913848,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"https://ux.stackexchange.com/questions/81134/should-modal-dialogs-be-movable seems to show a (rough) consensus that when a proposed solution to a dialog is to make it moveable, the dialog itself is poorly designed. That implies looking for a different solution that addresses the underlying user problem.",1573598939,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"The second point in this task is really annoying when working with large equations; The dialog is too small to see the whole source text of the equation.
+
+Workaround is to use the plain old editor, but then it is easy to do an error and the whole equation bombs out.",1538784516,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"This is only done for auto-resizing and auto-positioning, not manual resizing and positioning (""dragging"") which this bug is asking for (and which depends on bug 49969). Reopening.",1413835705,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"**physik** wrote:
+
+Change was merged. Seems to be fixed.",1413748422,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"**physik** wrote:
+
+Can someone look at https://gerrit.wikimedia.org/r/#/c/105647/ ... It would be great to merge this before it has to rebased manually again.",1391900695,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Re-positioning of OOjs UI windows is a really major piece of work, yes.
+
+Re-sizing is very do-able, however.",1387222681,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"I'm still trying to get a Google Code-in task or more out of these VE Math plugin reports...
+
+If I understand the comments, the ""movable"" part can't be fixed for this plugin because it depends on VE's current capacity to do so (bug 49969), right?
+
+Can the size of the window be controlled? If so, could this be a GCI task?",1387222391,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"(In reply to comment #5)
+> Change 97750 had a related patch set uploaded by Catrope:
+> Fix moving over an image with the arrow keys in Firefox
+> 
+> https://gerrit.wikimedia.org/r/97750
+
+Mis-targeted, sorry!",1385485858,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Change 97750 had a related patch set uploaded by Catrope:
+Fix moving over an image with the arrow keys in Firefox
+
+https://gerrit.wikimedia.org/r/97750",1385485737,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"(In reply to comment #3)
+> Just to note I'm just an end user, so don't really know much about how the
+> Visual Editor code works. It might be an idea to consult with the VE people
+> for
+> the best way to achieve this. I've not found any other VE dialog which is
+> movable or resizable, so I'm not sure if there is code you can copy.
+
+See bug 49969 (and maybe bug 49549).
+
+> (...)
+> What might also be possible would be to detect if the equation is inline or a
+> block mode.
+
+See bug 12223.",1385224372,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Just to note I'm just an end user, so don't really know much about how the Visual Editor code works. It might be an idea to consult with the VE people for the best way to achieve this. I've not found any other VE dialog which is movable or resizable, so I'm not sure if there is code you can copy.
+
+What is really important is that the box is big enough. Following from Helders comment you could detect the size of the original equation and size accordingly. 
+
+What might also be possible would be to detect if the equation is inline or a block mode. (In the tex world this would be $eqn$ vrs $$eqn$$) a larger edit window is preferred for block mode equations. Its a little tricker to detect the difference in wikitext, suronding text on the same line indicates inline mode. Being a single item in a list element <li><math> ...</math></li> indicates block mode.",1385224018,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Cross-posting from previous bug
+
+@Richard/others: Thinking about making the dialog draggable and resizable...
+
+The solution I initially think of is installing jquery.ui and then adding some
+parameters to OO.ui.Window that allow it to be made resizable and/or draggable.
+However, if I recall correctly one of the principles of OOJS was to be
+self-contained... so would this be wrong? Could someone else with a bit more
+firsthand experience chime in here?",1385161048,PHID-USER-wgpse4towjiaqbzotzgo,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"But it should also be smart enough not to present a tiny box when the formula is already very large. E.g. the last example from
+https://www.mediawiki.org/w/index.php?title=VisualEditor:TestMath&oldid=749189&veaction=edit
+
+Otherwise the user will need to resize the box on every formula of some pages",1385146969,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"There are many templates in Wikipedia that create right floated content other than info boxes and images.
+
+Examples are for instance Template:Stack, but there are many similar templates. These are currently not rendering as right floated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384944720,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-22g4j3j7uwe6d4goqunf,task_description,resolved
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"I vaguely think there was another task (since fixed) which this duplicates, but I have no idea what it was called.",1427403972,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,">>! In T59296#1154512, @TheDJ wrote:
+> If I remember correctly, it would be that the right floating stack, was opened in VE as full width and left aligned, pushing all visual adjacent content to be positioned underneath the stack template.
+
+Seems to be fixed to me - not happenning anymore: inserting Stack template(with/without specifying float- right) will position the template on the right.
+
+Btw, left - puts the template on the left.
+
+",1427403906,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"If I remember correctly, it would be that the right floating stack, was opened in VE as full width and left aligned, pushing all visual adjacent content to be positioned underneath the stack template.",1427402176,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"I checked in production some samples from https://en.wikipedia.org/wiki/Template:Stack:
+
+ {{stack |[[File:Test.png|thumb|right|Example 2a]] [[File:Test.png|thumb|right|Example 2b]]}}
+
+Without  float=left/right parameter - default is right. Is that what's been fixed? ",1427401123,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,This seems mostly fixed to me. Is that correct team ?,1427400395,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"This is caused by the div block surrounding it, that should receive 'similar' traits in that case.
+
+It is worsened, because in the case of stack in particular also takes fullwidth, due to the broken implementation of inline images with captions. These currently feature a figcaption that has display block, and no width constraint (shouldn't be allowed to be wider than the image frame, but it is).",1384945379,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,"https://en.wikipedia.org/w/index.php?title=Mozarteum_University_of_Salzburg&oldid=582046262
+
+https://parsoid.wmflabs.org/enwiki/Mozarteum_University_of_Salzburg?oldid=582046262
+
+Yet when opened in VE, the dom shows border=""1""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384944240,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_description,declined
+VisualEditor: Table with attribute border=0 is displayed as if border=1,"(In reply to Raimond Spekking from comment #5)
+> Sorry, but border=1 is very different from border=0. Your ""some light
+> default styling"" shows a border. This means, this bug is not fixed. 
+> 
+> If it has no priority, ok. But please leave it open.
+
+No. VisualEditor is not intended to be and will not reach a perfect simulacrum of read mode. First and foremost, VisualEditor is an editor; the borders are explicitly shown to make editing tables sane.",1412114211,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,"Sorry, but border=1 is very different from border=0. Your ""some light default styling"" shows a border. This means, this bug is not fixed. 
+
+If it has no priority, ok. But please leave it open.",1412096474,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,"(In reply to Raimond Spekking from comment #3)
+> Maybe a regression: the VE renders the table in
+> https://de.wikipedia.org/w/index.
+> php?title=Landschaftsversammlung_Rheinland&oldid=134477792 with border=1
+> instead of the given border=0. Or is this another bug?
+
+This is what ""some light default styling"" looks like.",1412096042,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,Maybe a regression: the VE renders the table in https://de.wikipedia.org/w/index.php?title=Landschaftsversammlung_Rheinland&oldid=134477792 with border=1 instead of the given border=0. Or is this another bug?,1412060228,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,We fixed this last week with some light default styling,1404172600,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,*** Bug 57368 has been marked as a duplicate of this bug. ***,1385123360,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+Images: {{Gallery}} template parsed differently by PHP parser and Parsoid,"{{Gallery}} is implemented by a Lua template here: https://en.wikipedia.org/wiki/Module:Gallery
+
+See example below
+
+```
+[subbu@earth lib] cat /tmp/gallery
+{{Gallery
+| lines = 2
+| File:Arc de Triomphe de l'Etoile - Projet Chalgrin - 02.jpg|1806: Architectural drawing project of [[Jean Chalgrin]]
+}}
+[subbu@earth lib] node parse --dump tplsrc < /tmp/gallery
+=================================
+Template:Gallery
+---------------------------------
+<table style=""background:transparent;border:1px solid #f0f0f0;margin-top:0.5em;""><tr><td><table style=""width:200px;float:left;border-collapse:collapse;margin:3px;""><tr><td style=""height:200px;border:1px solid #CCCCCC;background-color:#F8F8F8;padding:0px;text-align:center;"">[[File:Arc de Triomphe de l'Etoile - Projet Chalgrin - 02.jpg|center|border|180x180px|alt=|1806: Architectural drawing project of [[Jean Chalgrin]]]]</td></tr><tr style=""vertical-align:top;""><td style=""display:block;font-size:1em;height:3.2em;padding:0px;""><div class=""gallerytext"" style=""height:3.1em;width:187px;line-height:1.3em;padding:2px 6px 1px 6px;overflow-y:auto;margin:0px;border:none;border-width:0px;"">1806: Architectural drawing project of [[Jean Chalgrin]]&nbsp;</div></td></tr></table></td></tr></table>
+---------------------------------
+```
+
+So, the {{Gallery}} template emits the image in a <td> and the caption in a separate <tr> below. As far as I can tell, Parsoid therefore (correctly) duplicates the caption in both the <tr>s. However, somehow, the PHP parser magically suppresses the first caption (see https://en.wikipedia.org/w/index.php?title=User:Ssastry/sandbox&oldid=582405791)
+
+This is based on a report on VE/F @ https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=582367222#Pages_that_go_wrong_in_VE",1384885800,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-psruyhkjwka6oelbiqmt,task_description,resolved
+Images: {{Gallery}} template parsed differently by PHP parser and Parsoid,"Seems to be covered by,
+https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.skinning/content.parsoid.less#L150-L158",1491864814,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-psruyhkjwka6oelbiqmt,task_subcomment,NA
+Images: {{Gallery}} template parsed differently by PHP parser and Parsoid,"Is this still an issue?
+
+https://en.wikipedia.org/api/rest_v1/page/html/User:SSastry%20(WMF)%2Fsandbox/582405791 and https://en.wikipedia.org/w/index.php?title=User:Ssastry/sandbox&oldid=582405791 look identical to me.",1491863620,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-psruyhkjwka6oelbiqmt,task_subcomment,NA
+Add a link to the new guided format in the Navigation menu,"Pretty much what the Summary says:
+I would have used the new format but I keep forgetting how to reach it!
+I had proposed that the link reads ""Enter a new bug (guided)"" but in the end everything is actually ok for me as long as it's easy to discover for everyone, obviously.
+Cheers.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1384878480,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qjeerptbgnssiimoy3ki,task_description,declined
+Add a link to the new guided format in the Navigation menu,"http://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia&component=Bugzilla now says at the top ""If you prefer a simpler way to create a bug report, try the guided bug entry form."" linking to it. To me this feels sufficient.",1389089823,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-qjeerptbgnssiimoy3ki,task_subcomment,NA
+Add a link to the new guided format in the Navigation menu,"Some products need that kind of depth that the new guided form provides (i.e., VisualEditor :p ). I guess experienced users can find the way to add the link to the left column anyway, if they need to.",1384879246,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qjeerptbgnssiimoy3ki,task_subcomment,NA
+Add a link to the new guided format in the Navigation menu,"I wonder if that wording would be clear enough if both links provide the
+same functionality.
+
+So I have the naive idea that this could be based on how ""new"" (recently
+registered) the Bugzilla user account is. I have no idea if I have
+sufficient coding skills though. :)
+bugzilla.mozilla.org displays a ""(New to Bugzilla)"" string next to some
+user names, so it must be possible to gather such information and use
+it. I (or somebody else) ""just"" need to investigate their code a bit...",1384879011,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-qjeerptbgnssiimoy3ki,task_subcomment,NA
+VisualEditor: Don't use deprecated mw.util.wikiGetlink function,"When in debug mode the browser console always shows a message
+
+MWDeprecationWarning: Use of ""wikiGetlink"" property is deprecated. Use mw.util.getUrl instead.
+
+caused somewhere in VE's startup module. When you are trying to find uses of deprecated functions in your own scripts this message is a bit annoying, as you can't do anything about it and it shows up on every page. So please replace all calls to .wikiGetlink with .getUrl (in startup module and possibly elsewhere).
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1384856940,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-qf5vsjv66k5lg7t737hz,task_description,resolved
+VisualEditor: Don't use deprecated mw.util.wikiGetlink function,"This was done in gerrit 94263 which is in wmf3, which will be deployed to Wikipedias on Thursday.",1384857395,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qf5vsjv66k5lg7t737hz,task_subcomment,NA
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction","Steps to reproduce:
+
+
+1.Click on the edit button
+2.Click on a link and click on the link insertion icon.
+3.Without making any change just close the link inspector
+
+Observed Result:
+The ""Save Page"" button becomes active though if you review the changes it will say that this revision matches the lastest version of the page.
+
+Expected Result:
+If there is not modification in the content it is probably better to keep the ""Save Changes"" button inactive.
+
+Sample Page:
+
+https://en.wikipedia.org/w/index.php?title=Tea_tree_oil&veaction=edit
+
+Browser: Chrome Version 26.0.1410.65
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384800900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wgfiyucmntqggrzaytku,task_description,resolved
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction",Verified the fix in production (en.wiki),1403301720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wgfiyucmntqggrzaytku,task_subcomment,NA
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction",Verified the fix in test2 running wmf 9,1402694232,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wgfiyucmntqggrzaytku,task_subcomment,NA
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction",Now fixed by Trevor's work on the link inspector and window transactions.,1402549147,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wgfiyucmntqggrzaytku,task_subcomment,NA
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction",Instead we should check to see if the new annotation is actually different before applying it.,1384841672,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wgfiyucmntqggrzaytku,task_subcomment,NA
+VisualEditor: Allow users to set/edit __HIDDENCAT__ status in the page metadata panel,"Checkbox flag, category namespace only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fdmergs3gf3rbdk5e44x,task_description,resolved
+VisualEditor: Allow users to set/edit __HIDDENCAT__ status in the page metadata panel,"Change 126015 merged by jenkins-bot:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1398123272,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fdmergs3gf3rbdk5e44x,task_subcomment,NA
+VisualEditor: Allow users to set/edit __HIDDENCAT__ status in the page metadata panel,"Change 126015 had a related patch set uploaded by Alex Monk:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1397579986,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fdmergs3gf3rbdk5e44x,task_subcomment,NA
+VisualEditor: Allow users to set/edit __HIDDENCAT__ status in the page metadata panel,"Change 95726 had a related patch set uploaded by Jforrester:
+[WIP] Create remaining meta items in DM
+
+https://gerrit.wikimedia.org/r/95726",1384754690,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fdmergs3gf3rbdk5e44x,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Syntax highlighting doesn't work with Flow.
+
+Example input:
+
+```
+<syntaxhighlight lang=""css"">
+.foo {
+    font-weight: bold;
+}
+</syntaxhighlight>
+```
+Output is not appropriately highlighted: https://www.mediawiki.org/wiki/Topic:Sb29d13fybslwgjh
+It should look like this: https://www.mediawiki.org/w/index.php?title=User:Quiddity_%28WMF%29/sandbox&oldid=1397603
+
+----
+TheDJ notes (in comment below) that this might be related (plus its blockers): {T69540}",1384750140,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-u7imfvtjqvaumjzh3knn,task_description,open
+Flow: syntax highlighting tags (GeSHi) don't get styled,"This issue also affects the `highlight=` attribute, by the way – marked lines aren’t distinguished either.",1616345188,PHID-USER-7raa3vx5zsq6a56gil3q,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,">>! In T59159#6923746, @Krinkle wrote:
+> As a recent example, this can be seen at <https://www.mediawiki.org/wiki/Topic:W5dh34nv202fzq7f>.
+
+Other examples of likely affected features include Cite `<ref>`, Math, WikiHiero, TemplateData docs, TimedMediaHandler video player, 3D graphics, and more ([Codesearch](https://codesearch.wmcloud.org/deployed/?q=par.%2BaddModuleStyles&i=nope&files=&excludeFiles=&repos=))",1616029370,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"As a recent example, this can be seen at <https://www.mediawiki.org/wiki/Topic:W5dh34nv202fzq7f>.",1616028925,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Note: the ResourceLoader module missing is `ext.pygments`. You can load it unconditionally using `mw.loader.load( 'ext.pygments' )`, and I guess you could add this to your `common.js` to work around this bug if it’s very important :)",1517502237,PHID-USER-hrcsuxxosiyjqpef64tc,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Ok. I make rollback to 1.28.2
+No one fixes the bug.",1507572566,PHID-USER-ckht4z43xrkznivuzxeu,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,News? Solutions? Anything?,1507204315,PHID-USER-ckht4z43xrkznivuzxeu,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,{T174374} may solve this task. I'll ask.,1505898511,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,Any news?,1505857887,PHID-USER-ckht4z43xrkznivuzxeu,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,">>! In T59159#3548628, @aka_sektor wrote:
+> @Aklapper : Just let them return it as it was in 1.28.2
+> I do not know what exactly they broke.
+
+I only know that this problem affects board too: https://www.mediawiki.org/w/index.php?title=Flow/Sandbox&header_revId=twwnd0zvz6kx6bhb&action=view-header",1504100705,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"@Aklapper : Just let them return it as it was in 1.28.2
+I do not know what exactly they broke.",1503584278,PHID-USER-ckht4z43xrkznivuzxeu,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"@aka_sektor: The status of this task is ""open"", see the upper corner. Hence this issue is not fixed and we all know that. :) No need to comment and tell. If you would like to [[ https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker | contribute a code change ]] to fix this problem, you are very welcome to use [[ https://www.mediawiki.org/wiki/Developer_access | developer access ]] to submit the proposed code changes as a [[ https://www.mediawiki.org/wiki/Git/Tutorial | Git branch directly into Gerrit ]].",1503584022,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Setup 1.29.1: https://releases.wikimedia.org/mediawiki/1.29/mediawiki-1.29.1.tar.gz
+
+Bug with syntax highlight - stiil not fixed.",1503583157,PHID-USER-ckht4z43xrkznivuzxeu,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Release new MW version 1.29.1: https://www.mediawiki.org/wiki/Release_notes/1.29#MediaWiki_1.29.1
+
+Bug with syntax highlight fixed?",1503578921,PHID-USER-ckht4z43xrkznivuzxeu,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"I'm having the same problem.
+
+All codes is not styled.
+
+In the log, nothing is printed.
+
+Any help?",1474649170,PHID-USER-hhc5rqrodlqteaizzxd7,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"I'm having the same problema.
+
+All codes is not styled.
+
+In the log, nothing is printed.
+
+Any help?",1474031299,PHID-USER-hhc5rqrodlqteaizzxd7,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Another example from hewiki:
+https://he.wikipedia.org/wiki/%D7%A0%D7%95%D7%A9%D7%90:T8azrr7jamnrqfuy",1469334564,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"I just noticed this problem on Portuguese Wikipedia too:
+https://pt.wikipedia.org/w/index.php?title=T%C3%B3pico:Sav6mxon1ianxj4l&topic_showPostId=sb8xryegdo65sq73#flow-post-sb8xryegdo65sq73",1423164901,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Flow needs 2 things here. When rendering the original page, it needs to pick up the resources and add them into the parser output, so they end up on the head. Additionally, they need to be transferred in api results, preferably similar to how action=parse does it for prop=modules.
+
+
+This is probably closely related to bug 67540:
+
+And specifically you might want to look at one of it's blockers:
+Bug 51245, bug 58388 and bug 67515 which detail similar problems for VE..",1410256700,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,On trello at https://trello.com/c/qb7ulCmy/,1410232630,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"TheDJ notes, ""ah, I see that Resourceloader modules don't work yet :)"".[1]
+
+So perhaps this bug should be expanded to cover that? 
+I'll leave that up to the devs.
+
+[1] at https://www.mediawiki.org/w/index.php?title=Talk:Flow&workflow=rxtlvx7tsc2qqf1b#flow-post-ry5zwru18qpuglqk",1405618171,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"another example at https://www.mediawiki.org/w/index.php?title=Talk:Sandbox&workflow=050c27a75b2dcc146adc842b2b77e796#flow-post-050c27dd37d200e9aae290b11c2788d8
+
+which is copied from https://www.mediawiki.org/wiki/Talk:About_Beta_Features#HTML
+
+(possibly the same as bug 55533 (""VisualEditor: MWSyntaxHighlight* is badly broken"") ?)",1387499812,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/475, but people from the community are welcome to contribute here and in Gerrit.",1384761854,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"The browser tests are acting on User:Selenium_user. On a default VisualEditor installation, the User namespace does not have VisualEditor enabled.
+
+The easiest would be to enable VisualEditor on user page I guess.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384522740,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-irtxbpca23zxuomdrg5i,task_description,resolved
+VisualEditor: Browser tests assume the User namespace is VE-editable,"Change 118029 merged by jenkins-bot:
+Enable VisualEditor by default in NS_USER as well as $wgContentNamespaces
+
+https://gerrit.wikimedia.org/r/118029",1394660374,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"Change 118029 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default in NS_USER as well as $wgContentNamespaces
+
+https://gerrit.wikimedia.org/r/118029",1394496845,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"Yup the VisualEditor.php entry point has:
+
+ $wgVisualEditorNamespaces = $wgContentNamespaces;
+
+Which does not include the User namespace.  So the tests should probably only hit the content namespaces.",1393926141,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,Is this still true?,1393640526,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"**jhall** wrote:
+
+Ignore previous comment - I meant to put that comment in BZ 57103.",1386263501,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"**jhall** wrote:
+
+This issue was resolved with the following commit:
+
+https://gerrit.wikimedia.org/r/#/c/99257/",1386263310,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,I have just noticed that it is already assigned to Chris (_after_ adding him to cc).,1386256237,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,And Chris. :),1386256197,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"Jeff, Željko that might be appealing to you :-]",1386252913,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume User:Selenium_user exists,"The browser tests are assuming the user Selenium_user exist. It should instead rely on the user passed within the environment variable MEDIAWIKI_USER and its associated password in MEDIAWIKI_PASSWORD.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384522140,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-3tvzg52f222bnnwlfsai,task_description,resolved
+VisualEditor: Browser tests assume User:Selenium_user exists,"The wmf6 (2013-12-05) cut hasn't been made yet, so this actually goes into the cut for today, not wmf7. :-)",1386264422,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tvzg52f222bnnwlfsai,task_subcomment,NA
+VisualEditor: Browser tests assume User:Selenium_user exists,"**jhall** wrote:
+
+This issue was resolved with the following commit:
+
+https://gerrit.wikimedia.org/r/#/c/99257/",1386263541,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3tvzg52f222bnnwlfsai,task_subcomment,NA
+VisualEditor: Selecting text with command+down actually selects the whole current paragraph and also the 0th character of the next one; show this more obviously,"Paragraph turned into heading format
+
+Steps to reproduce:
+
+1.Click the edit button on a page
+2.Write down a paragraph and the text for its heading 
+3.Select the text to be heading of the paragraph
+
+Observed Result:
+
+The whole paragraph including the text turns into heading format.
+
+See the screenshot attached
+
+Found in:
+
+http://en.wikipedia.beta.wmflabs.org/
+(Example Page:http://en.wikipedia.beta.wmflabs.org/wiki/Test_52608?veaction=edit)
+
+Browser:FireFox 25 
+OS:MAC OS X 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11950}",1384472820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-qooshzhaumbtp7cw7ahy,task_description,declined
+VisualEditor: Selecting text with command+down actually selects the whole current paragraph and also the 0th character of the next one; show this more obviously,"The rendering is consistent with native selections. We should ignore the empty partial selection for most actions, but that is T52419.",1701814075,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qooshzhaumbtp7cw7ahy,task_subcomment,NA
+VisualEditor: Selecting text with command+down and then pressing command+right takes the cursor to the end of the next line,"Steps to reproduce:
+
+1.Click on the Edit button of a page which has multiple lines
+2.Select the text in the first line by pressing command+down
+3.Press on command+right 
+
+Observed Result:
+
+Instead of moving to the end of the line for the selected text, the cursor goes to the end of the second line.
+
+However, when you select the text with command+right/left it goes to end of the selected line.
+
+Found in:
+
+http://en.wikipedia.beta.wmflabs.org/
+Browser:FireFox 25, Chrome Version 26.0.1410.65
+OS:MAC OS X 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384469880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vqb2npuzjlgfxcuruzpi,task_description,open
+Add CSS classes based on writing system code,"It would be useful to have the languages that MediaWiki supports be aware of the alphabet in which they are written.
+
+ISO 15924 writing systems code can be used for the most part, so it will be ""latn"" for English, French, Vietnamese, etc.; ""cyrl"" for Russian, Udmurt, etc.; ""deva"" for Hindi, Marathi, etc. - and so on.
+
+This is useful for applying special styles that are common to all languages written in a script. For example the notorious line-height fix is applied in shared.css by element name and language code, and it could be greatly simplified by using the relevant script codes so instead of having selectors for bh, bho, hi, ks, mr, mai, ne, new, pi and sa, there would only be one selector for class deva.
+
+Of course, it will have to take into account language variants (Serbian Cyrillic / Latin, Kazakh Cyrillic / Latin / Arabic etc.) and also special cases not covered by ISO 15924, such as the internal differences between styles of Arabic (so Arabic may use ""arab"" and Urdu may use something like ""arab-nastaleeq"").
+
+An easy way to implement this would be to add a variable to each Messages file, similarly to $rtl. (In fact, this can make $rtl obsolete, because the direction is inherent in the writing system.)
+
+Comment 1: In this bug, ""writing system"", ""script"" and ""alphabet"" are synonyms. I mentioned all to make it easier to find.
+
+Comment 2: I vaguely recall that there is a bug for this, but I cannot find it. If there is one, please mark this one as a dupe.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384410720,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dlrnznpa3flmvxcmva4s,task_description,open
+Add CSS classes based on writing system code,"Late to the party, but I am thinking about how such a grouping could optimize our CSS here: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1053076",1722301447,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,">>! In T59045#6510311, @Volker_E wrote:
+> @Amire80 I was incredibly happy to have stumbled into this task.
+
+Thanks, it means a lot :)
+
+For years, I've been having these big ideas, and it's not always easy to convince people they're necessary.
+
+> When developing on several of our products, I've been asking a similar question about 3 years ago, but one that should in the mid-term be resolved by the W3C in CSS standard in my opinion. We've got `:lang()` selector, why not `:lang-script()` as additional pseudo-class.
+> Maybe you are interested to work together on a write-up for when such a selector would come helpfully into play?
+
+It would be nice to do it in a universally standard way, as you suggest, but my experience with the W3C till now has been that they are very reluctant about deriving a writing system from a language. I recommended deriving the `dir` from the `lang`: if `lang=""he""`, shouldn't the renderer assume `dir=""rtl""` by default? Apparently, they really didn't want it. Their argument was that it will hurt ""small"" languages like Azerbaijani and Punjabi, which can be written in both LTR and RTL alphabets. I disagree with this argument, at least as far as these two languages go, because these languages have different codes for the LTR and RTL versions (az/azb, pa/pnb), and we have fairly active Wikipedias in all four of them, but this didn't convince them.
+
+(I did manage to convince them to apply bidi isolation by default to elements that have an explicit `dir` attribute. My little contribution to the HTML/CSS standard.)
+
+So yeah, it would be nice, but because it's similar to that thing in which I failed, I suspect that it will not be easy to actually get done. But hey, I'm willing to try again! Share a doc or a wiki page with me or something.
+
+But until it succeeds, perhaps we should do something by ourselves, and it will be a real-world proof of concept for them...",1601584001,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"@Amire80 I was incredibly happy to have stumbled into this task. When developing on several of our products, I've been asking a similar question about 3 years ago, but one that should in the mid-term be resolved by the W3C in CSS standard in my opinion. We've got `:lang()` selector, why not `:lang-script()` as additional pseudo-class.
+Maybe you are interested to work together on a write-up for when such a selector would come helpfully into play?",1601583317,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,Slightly related: Bug 56908,1386233337,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"(In reply to comment #4)
+> I have two points related to this bug:
+> 
+> 1/ Is the information of the ""ISO 15924 <-> language code"" somewhere in
+> MediaWiki? I quickly searched and didn’t find.
+
+Not in core, but it's available in the UniversalLanguageSelector extension's ""langdb"" feature. Its most readable version can be found here:
+https://github.com/wikimedia/jquery.uls/blob/master/data/langdb.yaml
+
+(It's tracked in GitHub and periodically updated in Gerrit.)
+
+I occasionally fantasize about separating the langdb into an independent jQuery library and adding it to core.",1386167081,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"I have two points related to this bug:
+
+1/ Is the information of the ""ISO 15924 <-> language code"" somewhere in MediaWiki? I quickly searched and didn’t find.
+
+2/ Rethinking about the CSS classes, there is a problem in adding multiple levels of CSS classes: if there is
+
+  <html class=""writing-Latn""><div class=""writing-Cyrl"">здесь</div></html>
+
+then the inner <div> is affected by the classes ""writing-Latn"" and ""writing-Cyrl"", and there is no mean to know what is the most inner class between the two.",1386165812,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"(In reply to comment #2)
+Some Day Soon, when VisualEditor
+> will
+> have full support for marking pieces of text in another language, then there,
+> too. (It's already a beta feature.)
+
+... Just checked, and it doesn't seem to be deployed anywhere in Wikimedia. But it has been in development for months already.",1386139010,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"(In reply to comment #1)
+> Where do you think adding these CSS classes? If I understand correctly the
+> structure of the page, the <html> tag has the language and directionality of
+> the user interface language and the <div id=""mw-content-text""> tag has the
+> language and directionality of the page language. Adding these CSS classes on
+> these two places?
+> 
+> Interwikis could perhaps also be considered.
+
+Actually, any place where we currently use lang and dir.
+
+<html>, <div id=""mw-content-text"">, interlanguage links, ULS, various elements of the Translate and Wikibase extensions. Some Day Soon, when VisualEditor will have full support for marking pieces of text in another language, then there, too. (It's already a beta feature.) Many of these are not in the core, but they will need it just as well, so there probably should be core PHP and JS functions that make it easy to add them everywhere.",1386138855,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"Where do you think adding these CSS classes? If I understand correctly the structure of the page, the <html> tag has the language and directionality of the user interface language and the <div id=""mw-content-text""> tag has the language and directionality of the page language. Adding these CSS classes on these two places?
+
+Interwikis could perhaps also be considered.",1386111823,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","Steps:
+* Edit page
+* Add heading ""External links""
+* Press Enter, click ""Bulleted list"" in toolbar
+* Click on the link tool and paste a url in the link input widget
+* Type a label where the cursor is
+
+Expected:
+
+ <h2>External links
+ <ul><li> <a>Typing</a>
+
+Actual:
+
+ <h2>External links
+ <ul><li> <a>http://example.org/foobarTyping</a>♙
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384301160,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_description,resolved
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","Change 98116 merged by jenkins-bot:
+Close inspectors when surface is focused but selection doesn't change
+
+https://gerrit.wikimedia.org/r/98116",1386106765,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","Change 98116 had a related patch set uploaded by Catrope:
+Close inspectors when surface is focused but selection doesn't change
+
+https://gerrit.wikimedia.org/r/98116",1385662232,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","Clarification:
+
+* Create an empty list item
+* Open the link inspector
+* Type a link target
+* CLICK to position the cursor at the SAME PLACE where it was before
+* The inspector DOES NOT close
+* Type
+* The first key press is ignored and inserts a pawn instead, the remaining key presses insert characters before the pawn
+
+Root cause: when the document is focused, the inspector should close. We currently close the inspector when the selection changes, and usually clicking out of the inspector does change the selection, but in creation mode this isn't necessarily true.",1385473056,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","(In reply to comment #1)
+> Is there a JS error or exception in the console?
+
+There is not.
+
+Reduced steps:
+
+
+Steps:
+* Edit page with a list (or create a new unordered list)
+* Create a new list item
+* Click on the link tool and enter a url (e.g. ""http://example.org"") in the link input widget
+* Type a label (e.g. ""example"") where the cursor is
+
+Expected:
+<a href=""http://example.org"">example</a>
+
+Actual:
+<a href=""http://example.org"">http://example.orgxample</a>♙
+
+
+Note how the first character typed was ignored.",1384301747,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content",Is there a JS error or exception in the console?,1384301470,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+VisualEditor:The language selector takes user to the top of a page making user to scroll down again to the line where he was editing.,"Taking user to the top of the page
+
+Steps to reproduce:
+
+1.Click on the Edit button for a page with long article(For Example:https://test2.wikipedia.org/wiki/First_line?veaction=edit)
+2.Go to the end of the article
+3.Click the button More>Language
+
+Observed Result:
+The language selector takes user at the top of the page which is a bit inconvenient for user editing long article as he has to scroll down again to the point where he was editing.
+
+See the video attached
+
+Browser: Chrome Version 26.0.1410.65
+OS:MAC OS X 10.8.5
+Environment:test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12431}",1384218720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-i4u3xd3ofse5i6zio6uu,task_description,resolved
+VisualEditor:The language selector takes user to the top of a page making user to scroll down again to the line where he was editing.,This was fixed last month as part of the suite of such fixes.,1399641526,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i4u3xd3ofse5i6zio6uu,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"A limited rich text box, defaulting to page title.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53566
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49076",1384101420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rierearzanexovgzmq5m,task_description,resolved
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"Change 129065 merged by jenkins-bot:
+Allow VE users to change displaytitle in advanced settings dialog
+
+https://gerrit.wikimedia.org/r/129065",1402536738,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"Change 129065 had a related patch set uploaded by Alex Monk:
+Basic VE code for changing displaytitle as wikitext in metadata panel
+
+https://gerrit.wikimedia.org/r/129065",1398208005,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"Okays, turns out I hadn't read this properly and it's blocked on Parsoid recognising this as a meta item rather than a transclusion of 'DISPLAYTITLE'.",1398197686,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"(In reply to Alex Monk from comment #1)
+> This is more complicated than it looked.  For now we might have to just
+> accept wikitext (like the edit summary) instead of using a VE surface widget
+> (like the reference dialog), because DISPLAYTITLE can do crazy things like
+> accept templates.
+
+That works for now, though it's imperfect. :-)",1398184736,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"This is more complicated than it looked.  For now we might have to just accept wikitext (like the edit summary) instead of using a VE surface widget (like the reference dialog), because DISPLAYTITLE can do crazy things like accept templates.",1398127502,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTOC__ status in the page metadata panel,"A checkbox, setting:
+
+  <meta property=""mw:PageProp/notoc"">
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384101120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ccm3vufixpqdiieyj7mc,task_description,resolved
+VisualEditor: Allow users to set/edit __NOTOC__ status in the page metadata panel,"Change 95103 merged by jenkins-bot:
+Let users set __NOTOC__ & __FORCETOC__ status
+
+https://gerrit.wikimedia.org/r/95103",1388919566,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ccm3vufixpqdiieyj7mc,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTOC__ status in the page metadata panel,"Change 95103 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT, __NOTOC__, & __FORCETOC__
+
+https://gerrit.wikimedia.org/r/95103",1384313409,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ccm3vufixpqdiieyj7mc,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTOC__ status in the page metadata panel,See also bug 56867 comment 1,1384185698,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ccm3vufixpqdiieyj7mc,task_subcomment,NA
+VisualEditor: Allow users to set/edit behaviour flags in the page metadata panel (tracker),"Tracking bug for support for setting #REDIRECT, __NOTOC__, etc. behavioural flags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384100940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-664j7lcmpr3idv6utx47,task_description,resolved
+VisualEditor: Allow users to set/edit behaviour flags in the page metadata panel (tracker),No remaining children tickets; closing for now. We can re-open if it turns out to be necessary.,1402547626,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-664j7lcmpr3idv6utx47,task_subcomment,NA
+VisualEditor: Allow users to set/edit behaviour flags in the page metadata panel (tracker),*** Bug 52248 has been marked as a duplicate of this bug. ***,1385384185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-664j7lcmpr3idv6utx47,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","tab not adding indentation to newline
+
+Steps to reproduce:
+
+1.Add a numbered/bulleted list in the editor 
+2.Go to a newline afte the list
+3.Now click on ""tab"" from keyboard
+
+Observed Result:
+Instead of adding indentation to the new line, it keeps on adding indentation to first line of the numbered list.
+
+Sometimes it also selects other items outside the editor.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12204}",1383948660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hu5muegrlrswr533nsfw,task_description,open
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list",Check the attachment with video capture of the steps.,1386960227,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","Created attachment 14090
+video capture of the bug
+
+**Attached**: {F12206}",1386960184,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list",This still works for me.,1386932363,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","There is modification in the steps to reproduce this issue:
+
+1.Add a numbered list in the document
+2.Add the first item ""item1""
+3.Press enter and add the second item of the list ""item2""
+4.Place the cursor just before the text item2 and press tab.
+5.Now click on bullet list icon from the toolbar
+6.Go the end of second line and press enter (another bullet gets added to the newline)
+7.Now press enter again.
+8.Then keep on pressing tabs
+
+Observed Result:
+It is adding indentation to the first line of the page like 1.1.1.1.1 
+
+Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/wrong_serial&veaction=edit",1386106735,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","Created attachment 13970
+Screenshot of the error
+
+**Attached**: {F12205}",1386098757,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","I just reproduced it on production on this page:
+https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/wrong_ref_serial?veaction=edit
+
+Go to the last line of the page and keep pressing tab.",1386098669,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","I can't reproduce the behaviour described. Note the expected behaviour is either nothing or the document loses focus, not that the line is indented (yet).
+
+Re-open if you can reproduce.",1385746433,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list",Note that we don't support any sort of indentation outside of lists yet.,1384079747,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","Browser: Chrome Version 26.0.1410.65
+OS:MAC OS X Version 10.8.4",1384054314,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","(In reply to comment #1)
+> Found this bug on:
+> 
+> Browser:Chrome
+
+Please *always* add your browser version.
+
+> OS:MAC
+
+Please *always* add your OS version.",1384020820,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","Found this bug on:
+
+Browser:Chrome
+Environmenr:test 2
+Page: https://test2.wikipedia.org/wiki/Teetly
+OS:MAC",1383949245,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+VisualEditor: Math inspector(LaTeX) does not open up after adding a reference to the article,"Steps to reproduce:
+
+1.Click on the Edit button
+2.Add a reference to a text from More>Reference
+3.Now try to open up LaTeX window for any text in the article
+
+Observed Result:
+
+The math inspector does not open up after adding a reference to the article
+
+
+Environment:Test 2
+Page:Any
+Browser:FireFox 20 and Chrome Version 26.0.1410.65
+Reproducible: Yes
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383940080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ybs7n5eiujqyko2jnore,task_description,resolved
+VisualEditor: Math inspector(LaTeX) does not open up after adding a reference to the article,This issue might got resolved.Cannot reproduce it anymore.,1386024583,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ybs7n5eiujqyko2jnore,task_subcomment,NA
+VisualEditor: The default direction of the <textarea> for editing the content of <source> must be LTR,"Currently, if I go to https://www.mediawiki.org/wiki/User:Amire80/ve-source and
+edit it using VE, I can edit the content of the <source> tag. If my UI language
+is Hebrew, then the <textarea> for editing the poem is RTL. I would expect it
+to be always LTR by default, because source code is almost always LTR. (There are some RTL programming languages like Hebrew Logo and Arabic Alb, but these are very rare exceptions and the <source> tag doesn't support them anyway.)
+
+This is comparable to Bug 56779, but unlike in that bug, here the request is that the direction will be explicitly set to ltr rather than the surrounding direction.
+
+There may be other tags for which something like this would be useful, but I can't think of any at the moment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383920820,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-fmxzdu423cuvq3v2z6tl,task_description,resolved
+VisualEditor: The default direction of the <textarea> for editing the content of <source> must be LTR,"Change 94424 merged by jenkins-bot:
+Force LTR direction in MWSyntaxHighlightDialog
+
+https://gerrit.wikimedia.org/r/94424",1383964966,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fmxzdu423cuvq3v2z6tl,task_subcomment,NA
+VisualEditor: The default direction of the <textarea> for editing the content of <source> must be LTR,"Change 94424 had a related patch set uploaded by Mooeypoo:
+Force LTR direction in MWSyntaxHighlightDialog
+
+https://gerrit.wikimedia.org/r/94424",1383944480,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fmxzdu423cuvq3v2z6tl,task_subcomment,NA
+VisualEditor: The default direction of the <textarea> for editing the content of <source> must be LTR,Another nice thing to do would be to use CodeEditor instead of <textarea>.,1383920931,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-fmxzdu423cuvq3v2z6tl,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","When cite web is used, webpage title, and access date should be filled automatically for 1 click web citations.
+
+
+**Status:**  Title and other information is done via #citoid, but auto-adding the current date to the access-date parameter is a problem because of {T4700}.",1383914040,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_description,open
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically",,1677437245,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically",,1677400700,PHID-USER-vtpndgjtp2crb6jslv5y,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically",T96000 ?,1451388644,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically",Is it Citoid ?,1444861009,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","Here's what I did: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Template:Cite_web/doc&diff=prev&oldid=216044
+
+The problem is indeed that substitution does not work inside 'ref' tags (T4700), so there's no way in its current form to autofill the 'access date' field via TemplateData.
+
+It seems like this could be solved just within VE, though, by adding some way of directly adding the current date as the default for a field and leaving the parser out of it altogether. But! It looks like there's a shiny new patch for review for actually fixing that hoary bug!",1429824718,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","@Capt_Swing: can you please clarify? What did you test, and where? Links are appreciated. Thank you.",1429795695,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","@ragesoss tried this on enwiki beta, and it doesn't work: the subst; template is not rendered. ",1429123834,PHID-USER-i6la3rbocleoqjqldvzu,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","Web page title is done by citoid, I'm not sure if we can migrate the operation to the Cite web template automatically.
+
+However (as per irc chat) filling in the date automatically is exactly what the TemplateData autofill property is for. It can be set up with a template substitution for current date, and VE will fill it in automatically.",1429122286,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","I created https://gerrit.wikimedia.org/r/#/c/137824/ a while ago. I'll try to get around to reworking it to make it work, which will allow you to do this.",1415032827,PHID-USER-3qsavo6roa5h32xcsgng,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","(In reply to Alex Monk from comment #3)
+> It should be possible to achieve the accessdate part of this by editing
+> TemplateData to use the autovalue field from bug 52029 (subst: the date in
+> automatically).
+> 
+> Webpage title - isn't that something Citoid would do?
+
+Unfortunately bug 2700 means this isn't very trivial…",1415032174,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","(actually, leaving this as reopened for now due to the citoid bit...)",1414807310,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","It should be possible to achieve the accessdate part of this by editing TemplateData to use the autovalue field from bug 52029 (subst: the date in automatically).
+
+Webpage title - isn't that something Citoid would do?",1414807261,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","This has not been implemented, as of the version in English Wikipedia.",1405252019,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","Merging this with bug 50768.
+
+*** This bug has been marked as a duplicate of bug 50768 ***",1384845303,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+VisualEditor: Present the wikitext warning to users writing <ref> tags,"Intention:
+To add a ref (incorrectly, by typing out the wikicode)
+
+Steps to Reproduce:
+1.  Open a page. 
+2.  Type <ref>Whatever</ref>
+3.  Discover that there is no warning about wikitext markup being detected.
+
+Actual Results:  
+Nothing.
+
+Expected Results:  
+It should display the same wikitext markup warning that typing ''' produces.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383875160,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lh72hjfjcfl6ttsyvwlr,task_description,resolved
+VisualEditor: Present the wikitext warning to users writing <ref> tags,"Verified in test2 with Firfox 25 on MAC OS X 10.8.5.
+Example test page:
+https://test2.wikipedia.org/wiki/Verify_56274",1384548147,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lh72hjfjcfl6ttsyvwlr,task_subcomment,NA
+VisualEditor: Present the wikitext warning to users writing <ref> tags,"Change 94311 merged by jenkins-bot:
+Add <ref> tags to wikitext detection regex
+
+https://gerrit.wikimedia.org/r/94311",1383936986,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lh72hjfjcfl6ttsyvwlr,task_subcomment,NA
+VisualEditor: Present the wikitext warning to users writing <ref> tags,"Change 94311 had a related patch set uploaded by Catrope:
+Add <ref> tags to wikitext detection regex
+
+https://gerrit.wikimedia.org/r/94311",1383875277,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lh72hjfjcfl6ttsyvwlr,task_subcomment,NA
+VisualEditor: wiki markup for link shows up if a template is selected with another text and applied link onto them together,"wiki markup
+
+Steps to reproduce:
+
+1.Click on the Edit button for any page 
+2.Type a text in the editor.
+3.Add a template for example:citation needed,
+4.Now select both the text and the template and press command+l or link icon
+5.Apply a link to them through link inspector
+
+Observed Result:
+The wiki markup for link shows up in the view mode
+
+See the screenshot attached.
+
+
+Found this bug using firefox 20 or chrome Version 26.0.1410.65 in MAC OS
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12078}",1383868860,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pdnnreco64cgppyjvp4j,task_description,resolved
+VisualEditor: wiki markup for link shows up if a template is selected with another text and applied link onto them together,This appears to be fixed from what I can tell. Maybe part of the work we did in late February?,1402553588,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pdnnreco64cgppyjvp4j,task_subcomment,NA
+VisualEditor: The link inspector and the language selector opens up outside the editor while selecting a text outside the editor,"Link inspector
+
+Steps to reproduce:
+
+1. Click on the Edit button on any page 
+2. Go to a new line by pressing enter
+3. Now click at the top of the page or select the current user's name.
+4. Click on the link icon or More>Language from the toolbar
+
+Observed Result:
+The link inspector and the language selector opens up at the top right corner of the page ,outside the editor
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12072}",1383866520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lgpuuxaum6kkmmaplhbc,task_description,resolved
+VisualEditor: The link inspector and the language selector opens up outside the editor while selecting a text outside the editor,Fixed by Ed's null selection change.,1398726576,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lgpuuxaum6kkmmaplhbc,task_subcomment,NA
+VisualEditor: The link inspector and the language selector opens up outside the editor while selecting a text outside the editor,"Found in FireFox 20 and Chrome Version 26.0.1410.65 with MAC OS in both test2 and betalabs for any page.
+
+For FireFox, it opens somewhere at the bottom of the page.",1383867035,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lgpuuxaum6kkmmaplhbc,task_subcomment,NA
+VisualEditor: The link inspector and the language selector opens up outside the editor while selecting a text outside the editor,"Created attachment 13726
+Language selector
+
+**Attached**: {F12073}",1383866627,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lgpuuxaum6kkmmaplhbc,task_subcomment,NA
+Launch the 'gettingstartedtasktoolbar' tour by default,"**Author:** `swalling`
+
+**Description:**
+Right now, the workflow for GettingStarted tours is as follows:
+
+- The user gets 'gettingstartedtasktoolbarintro' once and immediately on their first view of a suggested task page. This is a one step intro tour, and then is never seen again. 
+- The user is then shown the task page, with the GettingStarted toolbar. They can click ""Show me how"" in the toolbar, which launches the 'gettingstartedtasktoolbar' tour. 
+
+Without changing the toolbar behavior, let's automatically launch the 'gettingstartedtasktoolbar' tour after the user completes the intro tour. Right now, only 9% of users are using the tour provided by ""Show me how"", which is fewer than we intended.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383779160,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_description,resolved
+Launch the 'gettingstartedtasktoolbar' tour by default,"Change 107726 merged by jenkins-bot:
+Auto-launch full tour, not just intro
+
+https://gerrit.wikimedia.org/r/107726",1391540557,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_subcomment,NA
+Launch the 'gettingstartedtasktoolbar' tour by default,"Change 107726 had a related patch set uploaded by Mattflaschen:
+Auto-launch full tour, not just intro
+
+https://gerrit.wikimedia.org/r/107726",1390890093,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_subcomment,NA
+Launch the 'gettingstartedtasktoolbar' tour by default,"My understanding is it should still be auto-launched only once.  The difference is that now it's the full tour, not the one step intro.
+
+Let me know if I have the wrong idea.",1389816682,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_subcomment,NA
+Launch the 'gettingstartedtasktoolbar' tour by default,"**swalling** wrote:
+
+Note: ideally, we want to launch 'gettingstartedtasktoolbar' or 'gettingstartedtasktoolbarve' conditionally based on whether the user has VisualEditor enabled.",1383779699,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"mw.Api has nice features now like automatically retrying bad tokens, we should migrate to it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383724260,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bggjq452trm2zbnm5rkp,task_description,resolved
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"Change 186548 merged by jenkins-bot:
+Use mw.Api to run requests rather than our own stuff in ve.init.mw.Target
+
+[[https://gerrit.wikimedia.org/r/186548]]",1424885189,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"Change 186548 had a related patch set uploaded (by Alex Monk):
+Use mw.Api to run requests rather than our own stuff in ve.init.mw.Target
+
+[[https://gerrit.wikimedia.org/r/186548]]
+
+#patch-for-review",1422060600,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,Done in https://gerrit.wikimedia.org/r/#/c/98713/ AFAICT.,1415890693,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"Yeah, you're right, the automatic retry without regard for the user changing is not what we want.",1383762753,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"One of the intentional functionality points in current VE is warning users when the token is bad because they user has changed (i.e. you've been logged out, or logged in as someone else), and explicitly asking for the user to consent to continue.
+
+This avoids the repeated cause of pain for users of the current wikitext editor where if you get logged out for some reason, it just saves as your IP, outing you (and needing revision deletion, drama and anguish). We should be fixing the wikitext editor to mirror the protocol in VisualEditor.
+
+It's unclear from how this is written whether ""automatically retrying"" means getting a new one, but only for a given user, or getting a new one regardless. If the latter, I think this is a WONTFIX. Advice?",1383754942,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Restore selection after blur+focus,"When the surface is blurred, then focused, we should restore the selection. Right now we don't, and that causes section editing to break when ULS is present.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383702120,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bl52d56tzpumlzzhbr7q,task_description,resolved
+VisualEditor: Restore selection after blur+focus,"Change 93925 merged by jenkins-bot:
+Restore selection when editor is refocused
+
+https://gerrit.wikimedia.org/r/93925",1383856735,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bl52d56tzpumlzzhbr7q,task_subcomment,NA
+VisualEditor: Restore selection after blur+focus,"Change 93925 had a related patch set uploaded by Catrope:
+Restore selection when editor is refocused
+
+https://gerrit.wikimedia.org/r/93925",1383718783,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bl52d56tzpumlzzhbr7q,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"1. Insert an image from Commons
+2. Press Ctrl+Z quickly
+
+When you undo the image insertion, there's still an API request pending. When it comes back, ve.ce.GeneratedContentNode.prototype.doneGenerating crashes because the node is now detached.
+
+GCNode should protect against being detached, and should abort any pending requests when it's detached (the latter alone is not enough: GCNode promises aren't guaranteed to be abortable).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383699720,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-akovpzpidyf5rwspkfmg,task_description,resolved
+VisualEditor: Exception when undoing foreign image insertion,"(In reply to comment #3)
+> I am getting this following errors while undoing an image insertion quickly
+> on
+> both FireFox 25 and Chrome Version 26.0.1410.65 with MAC OS X 10.8.5.
+> 
+> Uncaught TypeError: Cannot read property 'imageinfo' of null
+> ve.ui.MWMediaInsertDialog.teardown
+> OO.ui.Window.close
+> (anonymous function)
+> proxy load.php:10
+> 
+> 
+> See the screenshots.
+> 
+> Not sure if it is related with this bug or not.For now, I am reopening it.If
+> it
+> is a different issue I will create a separate ticket for that if required.
+
+Unrelated issue caused by a buggy gadget, ""popups"".",1384945498,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Created attachment 13808
+Screenshot of errors
+
+**Attached**: {F12811}",1384542540,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"After getting this error,cannot open the media dialog box again on that session.Attaching some more screenshots of the error.",1384542414,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Created attachment 13807
+Screenshot of the error
+
+**Attached**: {F12810}",1384542198,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Created attachment 13806
+Screenshot of the error
+
+**Attached**: {F12809}",1384542076,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"I am getting this following errors while undoing an image insertion quickly on both FireFox 25 and Chrome Version 26.0.1410.65 with MAC OS X 10.8.5.
+
+Uncaught TypeError: Cannot read property 'imageinfo' of null
+ve.ui.MWMediaInsertDialog.teardown
+OO.ui.Window.close
+(anonymous function)
+proxy load.php:10
+
+
+See the screenshots.
+
+Not sure if it is related with this bug or not.For now, I am reopening it.If it is a different issue I will create a separate ticket for that if required.",1384541718,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Change 93920 merged by jenkins-bot:
+Guard against detached nodes in ve.ce.GeneratedContentNode#doneGenerating
+
+https://gerrit.wikimedia.org/r/93920",1384258517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Change 93920 had a related patch set uploaded by Catrope:
+Guard against detached nodes in ve.ce.GeneratedContentNode#doneGenerating
+
+https://gerrit.wikimedia.org/r/93920",1383715166,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Insert media dialog lets you select an image via mouseup even if mousedown occurred elsewhere,"Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Click on More>Media
+3.Now attempt to drag the dialog downward
+
+Observed Result:
+The dialog box for media inclusion closes upon dragging down
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383699180,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2c2keu6qpdpobf5algrr,task_description,resolved
+VisualEditor: Insert media dialog lets you select an image via mouseup even if mousedown occurred elsewhere,This was fixed a while ago.,1404866655,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2c2keu6qpdpobf5algrr,task_subcomment,NA
+VisualEditor: Insert media dialog lets you select an image via mouseup even if mousedown occurred elsewhere,"Amended steps to reproduce:
+
+1. Mousedown on the title bar of the dialog
+2. Move mouse (i.e. drag) onto an image
+3. Mouseup on the image
+4. Dialog closes and inserts the image",1383699477,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2c2keu6qpdpobf5algrr,task_subcomment,NA
+VisualEditor: Make byte counter in save dialog use widget accessors rather than $textarea,"var $textarea = this.editSummaryInput.$input is bad, should just use .getValue() or whatever it is.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383698880,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yyxfhtfwvvpwlkr3s2rr,task_description,resolved
+VisualEditor: Make byte counter in save dialog use widget accessors rather than $textarea,Masked by bug 71837.,1412800505,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yyxfhtfwvvpwlkr3s2rr,task_subcomment,NA
+VisualEditor: Make byte counter in save dialog use widget accessors rather than $textarea,"Change 165597 merged by jenkins-bot:
+Replacing $input in save dialog
+
+https://gerrit.wikimedia.org/r/165597",1412799985,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yyxfhtfwvvpwlkr3s2rr,task_subcomment,NA
+VisualEditor: Make byte counter in save dialog use widget accessors rather than $textarea,"Change 165597 had a related patch set uploaded by SuchetaG:
+Replacing $input in save dialog
+
+https://gerrit.wikimedia.org/r/165597",1412799370,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yyxfhtfwvvpwlkr3s2rr,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,"Empty inspector
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Click on More>LaTeX
+3.Type something on the dialog box
+4.While keeping this dialog box open , Click on More>Reference
+5.Add something as reference 
+6.Click the button ""Insert Reference""
+
+Observed Result:
+A blank inspector comes up which also does not get closed unless user reopens the editor
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58045
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60850
+
+**Attached**: {F12800}",1383696720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_description,resolved
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,Appears to work now,1426003673,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,Ping on this bug.,1400701651,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,*** Bug 64915 has been marked as a duplicate of this bug. ***,1399333995,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,"Indeed; but not on a non-blank page.
+
+Minimum test:
+
+* Open VE on new (blank) page
+* Enter ""a"", <return>
+* Insert > Formula; enter ""1=1""
+* Insert > Reference; enter ""a""
+
+Voilà.",1399047179,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,Working fine locally and on beta labs with a blank page. Chrome && FF,1399044233,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,"Not for me still though,I am  giving the steps again :
+
+1.Open the editor
+2.Open the math inspector
+3.Put the cursor inside the inspector and type something in it
+4.While keeping the math inspector open , go to Insert>Reference
+5.Type something in the reference dialog box and click on Insert Reference
+
+Observed Result:
+The following error appears in the console and a blank inspector shows up:
+
+Uncaught Error: Cannot set attributes to non-element data 
+
+See the latest screenshot.",1398978174,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,Works for me.,1398942286,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,This is not fixed in Betalabs or Test 2.I can still reproduce this one on both the environments.,1398906203,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,*** Bug 63783 has been marked as a duplicate of this bug. ***,1397757927,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,*** Bug 60801 has been marked as a duplicate of this bug. ***,1397757894,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""","The search text box
+
+Steps to reproduce:
+
+1. Click on the ""Edit-beta"" button on beta-labs
+2.Click on the Language option from the toolbar
+3. Click the button ""Change language""
+
+Observed Result:
+The search textbox is going beyond the dialog box for selecting language.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12789}",1383691440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_description,resolved
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""",This was fixed in a ULS update.,1399641326,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""",This bug is found in betalabs on MAC OS with Chrome Version 26.0.1410.65 and FireFox 20.0,1383762862,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""","I can't manage to reproduce this in MediaWiki.org with Chrome 30.0.1599.101 m and Firefox 24.0 in Windows.
+
+ULS works properly for me. Can you share the browser and OS this happened in?",1383703924,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""",seems likely.  Ccing Amir and Zeljko,1383692271,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""","CC Moriel.
+
+Is this a bug in ULS, perhaps?",1383691945,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"We want to cache gzipped responses in Varnish. For this to work all clients need to send an Accept-Encoding header that includes 'gzip'.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383635820,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_description,declined
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"Change 101454 abandoned by Jforrester:
+[WIP] Accept-Encoding: gzip for read requests from Parsoid
+
+Reason:
+Abandoning for now.
+
+https://gerrit.wikimedia.org/r/101454",1401227823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,Appears intractable. :-(,1401227796,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"And also I should mention that on my local setup with no Varnish in the middle, and cURL installed, MW requests a gzipped copy from Parsoid and receives it. And decodes it properly.
+
+If I force it to use the PHP engine instead of cURL, it requests a non-gzipped version and receives it fine. This should be fixed in core rather than VE having to change anything.",1393294777,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"As far as I can tell from reading the code, this should currently only be necessary if the PHP cURL extension is not installed. (And it would also be necessary to decode the response you get back.)
+
+And really it should never be necessary - see bug 61507",1393294483,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"Varnish actually transparently decompresses stored compressed content and strips the supplied Accept header in its backend request. Since mid-November we always return compressed content, and Varnish stores it in compressed form for a much better hit rate. So the impact is not as high as I thought:
+
+1) it causes some extra CPU load in Varnish for decompression
+
+2) it results in a larger network transfer on the internal network
+
+Both have a very small performance impact. The Parsoid Varnish is basically idle CPU-wise and the internal network is fast.
+
+Lowering the priority to reflect this.",1388953957,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"Change 101454 had a related patch set uploaded by Jforrester:
+Accept-Encoding: gzip for read requests from Parsoid
+
+https://gerrit.wikimedia.org/r/101454",1386978406,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"This is important for performance, so setting priority to reflect that. Currently this causes Varnish to store uncompressed HTML, which reduces the hit rate significantly.",1384887489,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Templates with a conditional <li> asterisk in the beginning render in VE with it always visible,"Some frequently-used templates in the Hebrew Wikipedia, for example {{ynet}} have an asterisk in the beginning, which is inserted conditionally according to a parameter.
+
+They don't appear in the rendered article, but they appear as bullets when editing the article in VE.
+
+For an example see the URL.
+
+I demonstrated the issue to Moriel.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://he.wikipedia.org/wiki/%D7%A9%D7%9C%D7%93_%D7%91%D7%95%D7%A8%D7%A1%D7%90%D7%99",1383564420,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-zlmgxm2zkcke3qpckzhj,task_description,open
+VisualEditor: Templates with a conditional <li> asterisk in the beginning render in VE with it always visible,Possible Parsoid bug?,1394223034,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zlmgxm2zkcke3qpckzhj,task_subcomment,NA
+VisualEditor: Templates with a conditional <li> asterisk in the beginning render in VE with it always visible,"Created attachment 14508
+A video of the behaviour in Swedish Wikipedia.
+
+Perhaps the video might be an additional issue as the first template in the video; https://sv.wikipedia.org/wiki/Mall:IMDb-titel does not contain an conditional asterisk but just a plain one, which seem to be handled well in the parser.
+
+**Attached**: {F12610}",1391701100,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-zlmgxm2zkcke3qpckzhj,task_subcomment,NA
+VisualEditor: line breaks are added before and after image description when it is changed,"I'm not sure that it happens always, but in this edit I changed the description of an image, and line breaks were added:
+
+https://he.wikipedia.org/w/index.php?title=%D7%90%D7%95%D7%A4%D7%A7_%28%D7%A4%D7%93%D7%95%D7%9C%D7%95%D7%92%D7%99%D7%94%29&diff=14768833&oldid=13742934
+
+It's the first change in the diff.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383561060,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-acfakt67yvd2rrao52i6,task_description,resolved
+VisualEditor: line breaks are added before and after image description when it is changed,Is this still happening? I can't reproduce.,1420843420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-acfakt67yvd2rrao52i6,task_subcomment,NA
+Rename the BetaFeatures extension,"I realize it's probably already water under the bridge, but I believe
+this should be said anyway. Just WONTFIX the bug if we can't do
+anything about it.
+
+The name ""BetaFeatures"" is bad. Like, really bad. And I don't think
+this is just my personal opinion (but I don't like it personally
+either).
+
+* We have so many things named ""beta"" right now live on the wikis that
+  it's not even funny. VisualEditor is beta. MobileFrontend has some
+  beta stuff. Now we're also going to have ""beta"" features.
+  Depending on the person, the ""beta"" label has either lost its
+  meaning or is negatively associated with past deployment failures.
+
+* It's non-descriptive. It may be the non-native English speaker in
+  me, but it sounds like marketing-speech. ""beta"" doesn't mean much
+  these days (see point 1); ""feature"" is a catch-all buzzword.
+
+* It's stupidly hard to translate:
+  * Most languages don't even have a word for ""beta"" – unless somebody
+    talented does the translation, these will keep using the English
+    word in likely very awkward ways – most of currently translated
+    messages just keep the ""beta"" label tacked onto a normal word:
+    [[translatewiki:Special:Translations/Mediawiki:Prefs-betafeatures]],
+    some went with ""experimental"" instead.
+  * Similarly, most languages don't have a word for ""feature"" – in the
+    link above, most translations say the equivalent of
+    ""functionality"" or ""function"", and neither is a friendly word.
+    Basically, any translation of this will consist solely of
+    English/Latin loanwords in almost all languages, which may make it
+    sound ""remote"" or ""unfriendly"".
+
+
+So what do we do about it?
+
+* We can try renaming the project. We could go with the lowest
+  friction option and call it ""Experimental features"", which would be
+  at least a little better.
+
+* Or we could use others' experiences and name that section
+  ""Laboratory"", which would also give us an obvious, clear icon to use
+  (laboratory beaker) – Google does this with their experimental
+  options and it has always seemed like a great idea to me.
+
+
+No idea if ""rebranding"" as this point is still viable – it might be
+possible, as I don't think it was widely announced yet. But I'm just
+saying.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383491580,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ainrxat373d2ajxvqix6,task_description,declined
+Rename the BetaFeatures extension,"OK, since Nemo added me here...
+
+* ""Beta"" is kinda OK to translate in the languages that I know well, but it will probably be really understood only by techie people. Maybe that is the intention anyway.
+* ""Features"" is an awful English word to translate. It's very common in software, and it's always hard to interpret well.
+* I am working on the development of a big new Beta Feature (ContentTranslation), and everybody - everybody! - keeps confusing the word ""beta"" in ""beta feature"" and ""beta labs"", which is a completely different thing. At least one of these should be renamed.",1419938174,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"10.21 < aharoni> YuviPanda|zzz: kart_ hallo.
+10.21 < aharoni> it's about https://phabricator.wikimedia.org/T85106
+10.21 < aharoni> beta features
+10.21 < aharoni> not beta cluster
+10.22 < aharoni> on the production cluster.
+10.22 < aharoni> the beta feature is not installed there yet, but should be in two weeks.
+10.22 < YuviPanda|zzz> aharoni: yeah, indeed. kart_ was trying to do this on the betacluster, which is why I was confused
+10.23 < aharoni> WE REALLY NEED A DIFFERENT NAME FOR THE BETA CLUSTER
+",1419937330,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"As suggested at <http://lists.wikimedia.org/pipermail/design/2013-November/001200.html>, we could rename the extension ""FeaturesFeedback"". :-)",1385524345,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #19)
+> Are extension names ever translated? I believe the canonical (English) name
+> is
+> always used when referring to the extension name itself.
+
+Surely not. There is no general rule for this (every language's translators coordinate as do as they see fit), but most extensions ""are"" special pages and it is standard to translate the name of the special page/extension: https://www.mediawiki.org/wiki/Manual:Special_pages#The_Messages.2FInternationalization_File
+In Special:Version, the name shown is not what ""used when referring to the extension"" but a quotation, as shown by the italics.
+
+You could also try an ack-grep ""\-desc"" /mnt/user-store/git/extensions and try to find out how many translate the name when it's used in it, but in general the name lives elsewhere.",1384410819,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"I wonder how many native English speakers in different ages/gender/geographical/technical ability distributions will be able to guess what the ""Beta Feature"" is.
+It is an IT slang that pretends it went mainstream, that's all.",1384394260,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #18)
+> It is frustrating to see how the original issue, i.e. how to translate the
+> name of that feature into other languages, is addressed.
+
+Are extension names ever translated? I believe the canonical (English) name is always used when referring to the extension name itself.
+
+For interface messages, we should use what makes the most sense in whatever language is being used, of course. That languages other than English don't contain the word ""beta"" is a non-issue: they also don't contain words like ""category"" or ""visual"" or whatever else. We approximate based on the intended meaning and context (e.g., by substituting ""experimental"" for ""beta"").
+
+Again, this isn't to say that we'll never change the extension's name, but I don't think _not_ doing so is an insult to non-English speakers.",1384393478,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"It is frustrating to see how the original issue, i.e. how to translate the name of that feature into other languages, is addressed.
+
+I'll take a liberty to name it as I find appropriate in my language, then - just don't force me into ""please communicate with the community"" thing when the issue should be fixed in messages/ui/translations and not into wasted time explaining to surprised users, what Beta Features are.",1384393058,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #16)
+> (In reply to comment #0)
+> > Just WONTFIX the bug if we can't do anything about it.
+> 
+> As it is, I think this bug should be marked resolved/worksforme
+> (not resolved/wontfix), though as I said in comment 4, I don't
+> have the same visceral reaction to the name that you do. :-)
+
+Your wish is my command. :-)
+
+We may wish to revisit this later, however.",1384293799,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #0)
+> Just WONTFIX the bug if we can't do anything about it.
+
+If we hadn't gotten rid of it, I think this bug would be a reasonable case for using resolved/later (""later"" being ""until such a time that a better name is available for discussion""). As it is, I think this bug should be marked resolved/worksforme (not resolved/wontfix), though as I said in comment 4, I don't have the same visceral reaction to the name that you do. :-)",1384291417,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #11)
+> Face it. These are ""Upcoming features"". They will be deployed no matter if a
+> few angry users don't like them.
+
+Well, yeah. A few angry users don't outweigh the importance of building new, potentially better things for the good of the projects.
+
+If we let emotion and a few individual opinions affect our ability to get things done, I doubt even the people we'd appeased by backing out would respect us. Certainly nobody else would, including ourselves.
+
+We're not in ""beta"" because we expect to have to scrap the project. That's almost certainly not going to happen. We deployed to get feedback. Guess what? We got it! And now we're building an even more kickass bunch of projects for the next iteration.
+
+(In reply to comment #14)
+> Why does WMF build a separate one that can't be controlled by
+> the communities and calls it ""Beta"" instead of what it really is?
+
+Do you want to help maintain these projects? We have infrastructure for that. I'll happily sponsor you for +2 rights on them after a few patches and demonstrating that you're playing nice as a contributor.
+
+> After looking at the actual implementation of the ""Typography Update"" I hope
+> you are right. This is not even ""Beta"". I'm afraid deploying such ""half-baked
+> ideas"" will make things worse, no matter how you call it.
+
+If you're concerned, file a bug against it and make noise there. This isn't the arena for that discussion.
+
+And now I'm going to hit ""save changes"", and hopefully be able to talk about this bug instead of some topic that doesn't belong here.",1384281528,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"**mr.heat** wrote:
+
+(In reply to comment #13)
+> This comment probably adds more heat [...]
+
+My comments aren't intended to add something. All I'm trying to do is to find honest words for what's already there.
+
+> significant cost to Wikimedia community relations [...]
+
+Let me put it that way: If you are being criticized for adding non-requested features why are you adding an other non-requested feature that can be criticized for the exact same reasons? It's not that we don't have a Gadget infrastructure. Why does WMF build a separate one that can't be controlled by the communities and calls it ""Beta"" instead of what it really is?
+
+> I think there may be some value in explicitly marking particularly
+> half-baked ideas or implementations. I think that's more honest.
+
+After looking at the actual implementation of the ""Typography Update"" I hope you are right. This is not even ""Beta"". I'm afraid deploying such ""half-baked ideas"" will make things worse, no matter how you call it.",1384270667,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #11)
+> Face it. These are ""Upcoming features"". They will be deployed no matter if a
+> few angry users don't like them. These features are coming like the Google+
+> integration in YouTube. So call it what it really is, please. Be honest, at
+> least.
+
+This comment probably adds more heat than light (punintentional). Both ArticleFeedback and VisualEditor were scaled back following a barrage of negative feedback from their deployments (albeit not without significant cost to Wikimedia community relations...).
+
+I'd recommend focusing on specific problems with each of the proposed 'beta' features rather than continuing to 'bikeshed' over the extension name.
+
+> ""Beta"" doesn't mean anything nowadays. All we do in all Wikimedia projects is
+> ""Beta"". Nothing will ever be finished.
+
+Sure, but I think there may be some value in explicitly marking particularly half-baked ideas or implementations. I think that's more honest. :-)",1384263599,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #11)
+> These are ""Upcoming features"".
+
+I actually like this proposal, simple and to the point.",1384256768,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"**mr.heat** wrote:
+
+Face it. These are ""Upcoming features"". They will be deployed no matter if a few angry users don't like them. These features are coming like the Google+ integration in YouTube. So call it what it really is, please. Be honest, at least.
+
+""Beta"" doesn't mean anything nowadays. All we do in all Wikimedia projects is ""Beta"". Nothing will ever be finished.",1384250949,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #9)
+> ""Proving ground""? No idea how well it translates.
+
+Sounds like ""sandbox"".",1383614386,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #5)
+> I still like ""Laboratory"", but James has a point – even though the same point
+> can be made about ""Beta"" (I pointed out some examples in comment 0, another
+> would be the beta cluster, ironically also called ""beta labs"").
+
+Please, no more Labs/Laboratory names. In Wikimedia land we already have Labs, Tool Labs, IdeaLab, Labs²...
+
+> 
+> Other ideas for a name: something related to ""innovation"" or ""pioneering""?
+> (I quite like the second one, it gives off a nice vibe.)
+
+""Proving ground""? No idea how well it translates.",1383577308,PHID-USER-grgqimagqq3ankitlzm5,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #2)
+
+> * The language using the term ""beta"" is intentionally consistent with the
+>   Mobile team's beta channel - this is the same concept (and will likely
+>   cover Mobile technologies at some point too) and so should be translated
+>   the same.
+
+Excuse me, I can't understand the above paragraph at all :(
+
+btw. I posted https://www.mediawiki.org/wiki/Talk:About_Beta_Features#Name few days back",1383570493,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"Sure, I just set a high priority since this would be best FIXED or WONTFIXed before deployment, and deployment is happening very soon.",1383560392,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"I'm sorry, MatmaRex, I'd love to think that this was an important bug, but it's really not. I mean, as wonderful as a pioneering-based name would be, it's not like ""stop everything and work on this"" sort of stuff.",1383558037,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"Unlike those, BetaFeatures' name can probably still be changed. And we don't have Vector anymore, since I killed it (bug 45051).
+
+I still like ""Laboratory"", but James has a point – even though the same point can be made about ""Beta"" (I pointed out some examples in comment 0, another would be the beta cluster, ironically also called ""beta labs"").
+
+Other ideas for a name: something related to ""innovation"" or ""pioneering""?
+(I quite like the second one, it gives off a nice vibe.)",1383518755,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"We have a lot of poorly named extensions (""Vector"" and ""AbuseFilter"" come to mind). I'm not sure ""BetaFeatures"" is terrible, though.",1383510539,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #0)
+>     Basically, any translation of this will consist solely of
+>     English/Latin loanwords in almost all languages, which may make it
+>     sound ""remote"" or ""unfriendly"".
+
+And where I said ""Latin"", what I actually meant was Greek for ""beta"" and Latin for ""function"".",1383494293,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"Five points:
+
+* The language using the term ""beta"" is intentionally consistent with the
+  Mobile team's beta channel - this is the same concept (and will likely
+  cover Mobile technologies at some point too) and so should be translated
+  the same.
+
+* ""Experimental"" sounds clinical, complicated and confusing in English,
+  which is why it wasn't used.
+
+* If you are translating from English into a language that doesn't use the
+  Greek word 'beta', and also does not have an equivalent, calling it
+  ""experimental"" sounds fine.
+
+* The language using the term ""features"" is intentionally broad, to cover
+  new functionality, new UX approaches to existing functionality, new
+  design concepts, new skins, and other new things. Translations should
+  use a broad, inclusive term to cover all of these.
+
+* ""Labs"" is unfortunately already taken by WMF Labs. It would have been a
+  great name for this, I agree, but that's life. Unless you have a time-
+  machine handy, we can't fix the confusion that naming these the same
+  would cause.",1383494265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #0)
+> * We can try renaming the project. We could go with the lowest
+>   friction option and call it ""Experimental features"", which would be
+>   at least a little better.
+
+I think this was rejected in the past because it may include features thought or meant to be stable, just too ""new"" to be enabled for everyone at once.
+
+> 
+> * Or we could use others' experiences and name that section
+>   ""Laboratory"", which would also give us an obvious, clear icon to use
+>   (laboratory beaker) – Google does this with their experimental
+>   options and it has always seemed like a great idea to me.
+
+No idea if ""Laboratory"" is better than ""Beta"", they seem equally generic. ""Beta"" is just the most common way across the web/software industry to brand something as ""the last thing"" and tell people not to blame you if it breaks something; it doesn't have ""a meaning"" apart from that. I don't know if ""Laboratory"" has an equally wide usage/understanding.
+The main confusion here might be that not all features branded ""beta"" are controlled by this ""beta"" general switch; no idea if this is temporary.",1383492885,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+VisualEditor: Saving a page should update both wgRevisionId and wgCurRevisionId,"When we open a random page, we get
+wgCurRevisionId === wgRevisionId
+and if we make an edit using the source editor, both variables are increased to a new Id.
+
+On the other hand, if the edit is made using the VisualEditor, only the wgCurRevisionId is updated.
+
+This inconsistent behavior should be fixed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383474420,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-o3kocsqzjyadygy3bp6m,task_description,resolved
+VisualEditor: Saving a page should update both wgRevisionId and wgCurRevisionId,"Change 127441 merged by jenkins-bot:
+Update wgRevisionId when we change wgCurRevisionId
+
+https://gerrit.wikimedia.org/r/127441",1398107206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o3kocsqzjyadygy3bp6m,task_subcomment,NA
+VisualEditor: Saving a page should update both wgRevisionId and wgCurRevisionId,"Change 127441 had a related patch set uploaded by Alex Monk:
+Update wgRevisionId when we change wgCurRevisionId
+
+https://gerrit.wikimedia.org/r/127441",1397926805,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o3kocsqzjyadygy3bp6m,task_subcomment,NA
+"VisualEditor: Shows ""<""  icon on the last clicked link, if user clicks on the link icon from the toolbar on a blank space","The ""<"" icon on last clicked link
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.click on a text which has link on it but do not open the link inspector
+3.Now click on a blank space
+4.Click on the link icon from the toolbar.
+
+Observed Result:
+
+The ""<"" icon shows up at the end of the text in step 2.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12481}",1383350520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-zwu66cvpdyxa3rt4yxqv,task_description,resolved
+"VisualEditor: Shows ""<""  icon on the last clicked link, if user clicks on the link icon from the toolbar on a blank space",This was fixed a while ago; sorry for not catching it then.,1402329509,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zwu66cvpdyxa3rt4yxqv,task_subcomment,NA
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"Steps to reproduce:
+
+-Click on the Edit button
+-Click on the icon to insert a link from the toolbar or press ctrl+k or command+k -Now type a valid URL without http:// for example:yahoo.com
+
+Observed Result:
+There is no option for selecting this link as external link other than creating a new page.
+
+It would be better if the external link option is made available to user when they type a valid URL (text with ""."" inside it), and then transforms it into a HTTP link if no prefix is provided.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383339600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_description,resolved
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"
+
+*** This bug has been marked as a duplicate of bug 50360 ***",1402609062,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_subcomment,NA
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Change 97733 had a related patch set uploaded by Marcoil:
+> > Bug 56490: Use the HTTP API in round-trip testing
+> > 
+> > https://gerrit.wikimedia.org/r/97733
+> 
+> I don't think this has anything to do with that?
+
+Sorry! I entered the wrong bug for git-review.",1385471440,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_subcomment,NA
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"(In reply to comment #1)
+> Change 97733 had a related patch set uploaded by Marcoil:
+> Bug 56490: Use the HTTP API in round-trip testing
+> 
+> https://gerrit.wikimedia.org/r/97733
+
+I don't think this has anything to do with that?",1385471279,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_subcomment,NA
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"Change 97733 had a related patch set uploaded by Marcoil:
+Bug 56490: Use the HTTP API in round-trip testing
+
+https://gerrit.wikimedia.org/r/97733",1385468513,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","Difference in the view mode
+
+Steps to reproduce:
+
+1.Click on the Edit-beta button
+2.Type a text to apply link on it, For example: CNN
+3.Now click on the link icon from the tool bar or press ctrl+k/ Command+K
+4.Now type the link as http://cnn.com as an external link.
+5.Now type again another text CNN
+6.Now apply link insertion onto it as : http://cnn.com as new page
+7.Press the button ""Save""
+
+Observed Result:
+Now observe that the link created in step 4 looks reasonable to have an external
+link when the URL is specific in the link inspector.
+But user wont usually want a new page while specifying the URL itself and might accidentally to do that without any intention to do that.
+
+Also, observe the output format of step 6 looks wrong as the wiki markup for link shows up in the CE in view mode with a number.Though functionally, it works same as a link to external page.   
+
+Expected Result:
+As a suggestion,collapse the ""New Page"" part of the link inspector when a URL pattern detected.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12432}",1383333240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-reos2ubqqepoytoaxumu,task_description,resolved
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","(In reply to Alex Monk from comment #4)
+> (In reply to James Forrester from comment #3)
+> > We don't want to do this, because ""http://www.amazon.com"" is a valid page
+> > name and someone might actually want to use it - for example, [[en:Http://]]
+> > is a page (specifically, a redirect to the HTTP article).
+> > 
+> > However, maybe we should demote the ""new"" section below the external link
+> > one, to make it clearer?
+> 
+> It looks like this has already been done? Am I missing something?
+
+You're completely right, we did this a while ago. Never mind me! Sorry for wasting your time. :-(",1402680839,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","(In reply to James Forrester from comment #3)
+> We don't want to do this, because ""http://www.amazon.com"" is a valid page
+> name and someone might actually want to use it - for example, [[en:Http://]]
+> is a page (specifically, a redirect to the HTTP article).
+> 
+> However, maybe we should demote the ""new"" section below the external link
+> one, to make it clearer?
+
+It looks like this has already been done? Am I missing something?",1402680333,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","We don't want to do this, because ""http://www.amazon.com"" is a valid page name and someone might actually want to use it - for example, [[en:Http://]] is a page (specifically, a redirect to the HTTP article).
+
+However, maybe we should demote the ""new"" section below the external link one, to make it clearer?",1402550055,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","Created attachment 13657
+Difference in the review mode
+
+**Attached**: {F12433}",1383333707,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","Also, if I review my changes it shows the attached format.",1383333678,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","==== Problem
+The orange ""You have new messages"" talkpage-message Notification, currently leads just to the top of the user's Talk page. (Ie. [User talk:Quiddity])
+This is potentially confusing and makes it harder for users to locate the new message.
+{F26220991}
+
+==== Proposed solution
+* Tapping on ""new messages"" should take the user to the specific subsection (if known, and if there's just one new message); and
+* Append the message with a ""(view changes)"" link which takes the user to the diff (if subsection is unknown, or if there are multiple new talkpage messages).
+
+(Note: This essentially follows the same message format as shown to users of the gadget to ""Display a floating alert for new talk page messages"" (link to [[ https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets | gadget on enwiki ]])
+
+
+// One user has requested that it *always* lead to the diff, which /would/ be more consistent, but I also understand the desire to not confront everyone with a diff (VE, newcomer friendliness, etc etc). ( https://en.wikipedia.org/wiki/Wikipedia_talk:Notifications#Two_clicks_instead_of_one:_Why.3F ) //
+
+",1383326040,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-dknub327yjfltf5egogv,task_description,resolved
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Yes. (But I have one pedantic clarification: it takes you to the top of the section, rather than precisely to the message.)",1630508980,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","@matmarex: would it be accurate for @ryasmeen and I to think that this patch has the following impact?
+
+**Impact**
+- This patch **does** make it so when someone clicks/taps the `new messages` yellow banner they //are// taken to the precise location on the talk page where that new comment was posted.
+- This patch does **not** make it so said new comment will appear highlighted in blue. [i]
+
+---
+i. The blue highlight depends on T281590 being resolves as [you noted in gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Echo/+/683932/): ` Together with the changes proposed in T281590, this would allow linking directly to individual messages (and highlighting them), rather than just the section`",1630455300,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","@matmarex: would it be accurate for @ryasmeen and I to think that this patch has the following impact?
+
+**Impact**
+- This patch **does** make it so when someone clicks/taps the `new messages` yellow banner they //are// taken to the precise location on the talk page where that new comment was posted.
+- This patch does **not** make it so said new comment will appear highlighted in blue. [i]
+
+---
+i. The blue highlight depends on T281590 being resolves as [you noted in gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Echo/+/683932/): ` Together with the changes proposed in
+T281590, this would allow linking directly to individual messages (and highlighting them), rather than just the section`",1630455275,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Change 683932 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Echo@master] Link to the section (if known) from the orange banner%%%
+https://gerrit.wikimedia.org/r/683932",1628242062,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Change 683932 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/Echo@master] Link to the section (if known) from the orange banner%%%
+https://gerrit.wikimedia.org/r/683932",1619801630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","5. Add an icon ""diff"" just after the regular message.
+",1535578022,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Notes: 
+**Functionality**: The [[ https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets | gadget ]] on Enwiki (""Display a floating alert for new talk page messages"" ([[https://en.wikipedia.org/wiki/MediaWiki:Gadget-topalert.js|.js]]/[[https://en.wikipedia.org/wiki/MediaWiki:Gadget-topalert.css|.css]])) provides the desired link. 
+E.g. For 2 test messages at my talkpage, it provides [[https://en.wikipedia.org/w/index.php?title=User_talk:Quiddity%20(WMF)&oldid=855470833&diff=cur|a ""view changes"" diff link that shows both of them]]. 
+It displays the link (and a plain link to the top of the talkpage) in a floating-top-center overlay.
+{F25502484}
+**Design**: As discussed above, the main question is how to integrate this link with the existing ""New message indicator"", because we probably don't want to have the default link to go to a diff (because that's extra confusing for a newcomer who was writing in VisualEditor, and receives some huge welcome or warning templates (e.g. [[https://en.wikipedia.org/w/index.php?title=User_talk:157.48.244.85&oldid=857134302&diff=cur|semi-relevant example]] pulled from recentchanges showing 2 changes)). 
+Options include:
+# add a ""(view changes)"" link to the end of the existing New message indicator. -- This would make it a bit longer in English, but still not too bad. The [[https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3AEcho-new-messages&namespace=8 |French default]] is a good example of a longer string, as is [[https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3ANotification-link-text-view-changes&namespace=8|the French for ""View changes""]]. [demo below]
+# add a ""(diff)"" link to the end [...]. -- This would potentially confuse newcomers. It's short in English, but [[https://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki%3ADiff|quite a bit longer in some other languages]].
+# add either of those options //below// the existing New message indicator. -- Kinda messy?
+# other??
+
+A (hacked-HTML) demo of option #1 would look like this in French:
+{F25503614}",1535577889,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Notes: 
+**Functionality**: The [[ https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets | gadget ]] on Enwiki (""Display a floating alert for new talk page messages"" ([[https://en.wikipedia.org/wiki/MediaWiki:Gadget-topalert.js|.js]]/[[https://en.wikipedia.org/wiki/MediaWiki:Gadget-topalert.css|.css]])) provides the desired link. 
+E.g. For 2 test messages at my talkpage, it provides [[https://en.wikipedia.org/w/index.php?title=User_talk:Quiddity%20(WMF)&oldid=855470833&diff=cur|a ""view changes"" diff link that shows both of them]]. 
+It displays the link (and a plain link to the top of the talkpage) in a floating-top-center overlay.
+{F25502484}
+**Design**: As discussed above, the main question is how to integrate this link with the existing ""New message indicator"", because we probably don't want to have the default link to go to a diff (because that's extra confusing for a newcomer who was writing in VisualEditor, and receives some huge welcome or warning templates (e.g. [[https://en.wikipedia.org/w/index.php?title=User_talk:157.48.244.85&oldid=857134302&diff=cur|semi-relevant example]] pulled from recentchanges showing 2 changes). 
+Options include:
+# add a ""(view changes)"" link to the end of the existing New message indicator. -- This would make it a bit longer in English, but still not too bad. The [[https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3AEcho-new-messages&namespace=8 |French default]] is a good example of a longer string, as is [[https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3ANotification-link-text-view-changes&namespace=8|the French for ""View changes""]]. [demo below]
+# add a ""(diff)"" link to the end [...]. -- This would potentially confuse newcomers. It's short in English, but [[https://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki%3ADiff|quite a bit longer in some other languages]].
+# add either of those options //below// the existing New message indicator. -- Kinda messy?
+# other??
+
+A (hacked-HTML) demo of option #1 would look like this in French:
+{F25503614}",1535577853,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Change 94506 abandoned by Aude:
+Link ""You have new messages"" to user talk diff
+
+Reason:
+since ext.echo.alert.js is deleted, shall try new approach :)
+
+https://gerrit.wikimedia.org/r/94506",1390511546,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Change 94506 had a related patch set (by Aude) published:
+Link ""You have new messages"" to user talk diff
+
+https://gerrit.wikimedia.org/r/94506",1384321229,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","(In reply to comment #3)
+> I could have sworn this was a duplicate bug... I may be remembering the bug
+> about the Echo drop-down nav thing not including a ""view changes"" link.
+
+You're probably thinking of bug 54391 - which I've been told is just to do with the email bundled diff (or something).",1384320811,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","I could have sworn this was a duplicate bug... I may be remembering the bug about the Echo drop-down nav thing not including a ""view changes"" link.",1384320470,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","(In reply to comment #0)
+> The orange ""You have new messages"" talkpage-message Notification, currently
+> leads just to the top of the user talkpage. (Ie. [User talk:Quiddity])
+
+This is one of the things I probably miss the most about the OBOD, that I could get a direct diff to the new edits.
+
+> 
+> It should lead to either:
+> * the subsection (if known, and if there's just one new message), or 
+> * to the diff (if subsection is unknown, or if there are multiple new
+> talkpage
+> messages).
+
+From a code standpoint, either of these are probably doable.
+
+> 
+> One user has requested that it *always* lead to the diff, which /would/ be
+> more
+> consistent, but I also understand the desire to not confront everyone with a
+> diff (VE, newcomer friendliness, etcetc).
+
+I don't think always going to the diff is a good idea, for some of the reasons you mentioned.
+
+Adding a ""You have new messages (diff)"" thing to the personal tools menu would be icky and add some more clutter. I don't know where else we could add the link.
+
+CC'ing Jared for some design input.",1384316580,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/395, but people from the community are welcome to contribute here and in Gerrit.",1383589314,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+VisualEditor: Track in some way (add tag to revision?) edits where user switched into wikitext editor,"Since bug 50687 was fixed, I was wondering if wouldn't be a good idea to identify which edits made using the wikicode editor were actually started using Visual Editor. This could be useful to identify potential areas of improvement of Visual Editor, providing a list of actions which users are unable to complete using it.
+
+A way to do this would be the use of a new tag (similar to the ""visualeditor"" and ""visualeditor-needcheck"" tags).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50687",1383304560,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-5jz7sjvvr5dsv6ewj3sj,task_description,resolved
+VisualEditor: Track in some way (add tag to revision?) edits where user switched into wikitext editor,"Change 113665 merged by jenkins-bot:
+Track edits where user switched into wikitext editor from VE
+
+https://gerrit.wikimedia.org/r/113665",1393464958,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5jz7sjvvr5dsv6ewj3sj,task_subcomment,NA
+VisualEditor: Track in some way (add tag to revision?) edits where user switched into wikitext editor,"Change 113665 had a related patch set uploaded by Alex Monk:
+Track edits where user switched into wikitext editor from VE
+
+https://gerrit.wikimedia.org/r/113665",1392564041,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5jz7sjvvr5dsv6ewj3sj,task_subcomment,NA
+"VisualEditor: Add a second keyboard shortcut for Clear Formatting for keyboards without a ""\""","Split from bug 51507 which introduced Ctrl/Cmd + \ as a trigger for this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51507",1383283920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nlj7q7vdqadglucet365,task_description,resolved
+"VisualEditor: Add a second keyboard shortcut for Clear Formatting for keyboards without a ""\""","Change 116967 merged by jenkins-bot:
+Add cmd/ctrl+m as alternative shortcut for clear formatting
+
+https://gerrit.wikimedia.org/r/116967",1394054776,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nlj7q7vdqadglucet365,task_subcomment,NA
+"VisualEditor: Add a second keyboard shortcut for Clear Formatting for keyboards without a ""\""","Change 116967 had a related patch set uploaded by Esanders:
+Add cmd/ctrl+m as alternative shortcut for clear formatting
+
+https://gerrit.wikimedia.org/r/116967",1394029152,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nlj7q7vdqadglucet365,task_subcomment,NA
+"VisualEditor: Add a second keyboard shortcut for Clear Formatting for keyboards without a ""\""",Changing priority to 'normal' since 51507 was 'high' and I'm hesitant to make this 'low'; please feel free to re-adjust.,1383331671,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-nlj7q7vdqadglucet365,task_subcomment,NA
+VisualEditor: It should be possible to add a link with only pressing enter once,"Steps to reproduce:
+1.Click on the ""Edit-Beta"" button
+2.Type a text on which to insert link
+3.Press ""Enter"" to select the suggested links or if there is no match just press ""Enter""
+4.Then again press ""Enter""
+
+Observed Result:
+To insert a link the step 4 is a redundant step , Pressing enter once should just add the link.
+
+Pressing the ""Enter"" twice seems justified in the case, where the content of the link box is different from what user initially typed into.
+
+[Suggested by Erik Moeller]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383255660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bfggoy34bkzy45f7kcpd,task_description,resolved
+VisualEditor: It should be possible to add a link with only pressing enter once,Verified the fix in production,1403306780,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bfggoy34bkzy45f7kcpd,task_subcomment,NA
+VisualEditor: It should be possible to add a link with only pressing enter once,Verified the fix in test2,1402690628,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-bfggoy34bkzy45f7kcpd,task_subcomment,NA
+VisualEditor: It should be possible to add a link with only pressing enter once,Now fixed with the changes to the link inspector.,1402552625,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bfggoy34bkzy45f7kcpd,task_subcomment,NA
+VisualEditor:The cursor position for newly inserted link should be at the end of the link that is being created,"Screenshot showing cursor at the beginning of the text ""Yahoo""
+
+Steps to reproduce:
+-Click on the Edit-beta button
+-Type a text on which you will insert a link.
+-click on the link icon from the toolbar or use shortcut keys ctrl+k/command+k(MAC)
+-Type the link on the dialog box that appears .
+-Press ""Enter"" to apply that.
+
+Observed Result:
+The cursor position postion moves to the beginning of the text on which the link inserted making user to reposition it to the end of it to continue editing.
+
+Expected Result:
+The cursor position for newly inserted link should be at the end of the link to ease user experience.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12328}",1383251880,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-eusx3radyuz75qavwdhm,task_description,resolved
+VisualEditor:The cursor position for newly inserted link should be at the end of the link that is being created,"This was fixed a few months ago (the cursor returns to the original position if you exit normally, or goes to the beginning of the document if you exit with escape).",1402552556,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eusx3radyuz75qavwdhm,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","VisualEditor deliberately drops <span typeof=""mw:Nowiki""> annotations on changed content to prevent originally-necessary <nowiki> blocks interfering with editing. This means that HTML editors don't need to know or care about <nowiki>s, and they are just magically sorted out in the back-end so the resultant wikitext is the most like what a human would create.
+
+However, <nowiki />s come out as a <meta typeof=""mw:Placeholder"">, which VisualEditor doesn't show to users but also won't ever remove, leading to potential issues where a no-longer-needed <nowiki /> sits in the wikitext, disruptively confusing to wikitext editors.
+
+If Parsoid instead represented it as <span typeof=""mw:Nowiki""></span> or similar, VisualEditor could do the same (well, a bit more work) and so drop it when the context has been edited, letting Parsoid re-generate it if needed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=Footprints_%28film%29&curid=39472392&diff=579475542&oldid=579357688",1383161460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iptvwjtzvbnrwojokpim,task_description,resolved
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","@Jdforrester-WMF Do we actually need any work in VE? This seems to be magically working okay in my testing. If I'm missing something, is there a task?",1488384460,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVo97A6WHQCSeVEJfLNq} [2017-02-14T18:39:24Z] <arlolra> Updated Parsoid to 79ccfb93 (T58381, T108216)",1487097565,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",Thank you!,1486494471,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Parsoid now represents them as <span typeof=""mw:Nowiki""></span>, but VisualEditor still needs to do the work to drop them when the context has been edited.",1486493729,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 281076 merged by jenkins-bot:
+Treat html pre and nowiki as extension tags
+
+[[https://gerrit.wikimedia.org/r/281076]]",1486493070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 281076 had a related patch set uploaded (by Arlolra):
+WIP: Tokenize html pre as an extension tag
+
+[[https://gerrit.wikimedia.org/r/281076]]
+",1481072290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 232313 abandoned by Arlolra:
+WIP: Edited nowiki content should invalidate the nowiki
+
+Reason:
+For now ... until I pick it up again.
+
+[[https://gerrit.wikimedia.org/r/232313]]",1459809667,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 191096 abandoned by Subramanya Sastry:
+WIP: T58381: Represent <nowiki/> as a mw:Nowiki meta tag
+
+Reason:
+Once we figure out how to not generate HTML for <nowiki>s and instead add them back where needed, this is going to be irrelevant.
+
+[[https://gerrit.wikimedia.org/r/191096]]",1450473413,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 232313 had a related patch set uploaded (by Arlolra):
+WIP: Edited nowiki content should invalidate the nowiki
+
+[[https://gerrit.wikimedia.org/r/232313]]
+",1449177908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 232313 had a related patch set uploaded (by Arlolra):
+T58381: Edited nowiki content should invalidate the nowiki
+
+[[https://gerrit.wikimedia.org/r/232313]]
+",1440021958,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",Works for me.,1424474368,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","I agree that fixing nowiki issues are important. But, we should add specific nowiki corruption tasks to the board rather than have a generic longer-term solution like this. I will go over our current nowiki list and add any specific nowiki corruption scenarios to the VE Q3 board. Sound good?",1424474321,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",">>! In T58381#1055479, @ssastry wrote:
+> Based on all this, I am not sure that this task should be on the VE Q3 blocker list anymore. These fixes are more of a longer-term nature than what is required immediately for VE in Q3. @Jdforrester-WMF, thoughts?
+
+I'm not sure. Reducing the frequency of <nowiki>s is a key ""corruption"" concern of users, and as such is a key blocking focus for Q3. I don't particularly see this task as the one-true-fix, and happy for this to be removed if the other work in this area addresses the concerns. What do you think?",1424473082,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Based on an IRC discussion y'day during the VE/Parsoid/Services check-in, it seems that more than fixing the representation for nowiki, VE wants Parsoid html2wt to be more aggressive removing existing <nowiki/> from edited content rather than emit those back as is. Something to be considered.
+
+A related idea that came up during the discussion was: maybe Parsoid shouldn't emit the nowiki markup anymore in its HTML. This will work only if:
+(a) selser is smart enough to add nowikis wherever required (even for unedited content)
+(b) selser is smart enough to not introduce dirty diffs  by optimizing / moving around nowikis because of (a). This is especially a concern fwiki, itwiki, etc. where quotes are used in non-italic/non-bold scenarios more heavily. So, any fixes we do should be tested more heavily against these wikis.
+
+A related discussion around (a)/(b) here can be found in https://phabricator.wikimedia.org/T87708#1055269 and later comments.
+
+But, based on all this, I am not sure that this task should be on the VE Q3 blocker list anymore. These fixes are more of a longer-term nature than what is required immediately for VE in Q3. @Jdforrester-WMF, thoughts?",1440022256,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Based on an IRC discussion y'day during the VE/Parsoid/Services check-in, it seems that more than fixing the representatoin for nowiki, VE wants Parsoid html2wt to be more aggressive removing existing <nowiki/> from edited content rather than emit those back as is. Something to be considered.
+
+A related idea that came up during the discussion was: maybe Parsoid shouldn't emit the nowiki markup anymore in its HTML. This will work only if:
+(a) selser is smart enough to add nowikis wherever required (even for unedited content)
+(b) selser is smart enough to not introduce dirty diffs  by optimizing / moving around nowikis because of (a). This is especially a concern fwiki, itwiki, etc. where quotes are used in non-italic/non-bold scenarios more heavily. So, any fixes we do should be tested more heavily against these wikis.
+
+A related discussion around (a)/(b) here can be found in https://phabricator.wikimedia.org/T87708#1055269 and later comments.
+
+But, based on all this, I am not sure that this task should be on the VE Q3 blocker list anymore. These fixes are more of a longer-term nature than what is required immediately for VE in Q3. @Jdforrester-WMF, thoughts?",1424470082,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Based on an IRC discussion y'day during the VE/Parsoid/Services check-in, it seems that more than fixing the representatoin for nowiki, VE wants Parsoid html2wt to be more aggressive removing existing <nowiki/> from edited content rather than emit those back as is. Something to be considered.
+
+A related idea that came up during the discussion was: maybe Parsoid shouldn't emit the nowiki markup anymore in its HTML. This will work only if:
+(a) selser is smart enough to add nowikis wherever required (even for unedited content)
+(b) selser is smart enough to not introduce nowikis by optimizing / moving around nowikis because of (a). This is especially a concern fwiki, itwiki, etc. where quotes are used in non-italic/non-bold scenarios more heavily. So, any fixes we do should be tested more heavily against these wikis.
+
+A related discussion around (a)/(b) here can be found in https://phabricator.wikimedia.org/T87708#1055269 and later comments.
+
+But, based on all this, I am not sure that this task should be on the VE Q3 blocker list anymore. These fixes are more of a longer-term nature than what is required immediately for VE in Q3. @Jdforrester-WMF, thoughts?",1424469867,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","<meta> tags will be metadata in VE, so may end up somewhere else if content is deleted. Also <meta> and <link> tags suffer from being destroyed by copy/paste and so require special treatment (we also do this for HTML comments).",1424217065,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",Uploaded a WIP there in case that would work. The meta tag seems the right approach and fits in with the use of marker meta tags for various other wikitext constructs.,1424198389,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 191096 had a related patch set uploaded (by Subramanya Sastry):
+WIP: T58381: Represent <nowiki/> as a mw:Nowiki meta tag
+
+[[https://gerrit.wikimedia.org/r/191096]]
+
+#patch-for-review",1424198157,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","How about <meta typeof=""mw:Nowiki"" ../>. Can VE handle that instead?",1424197863,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",*** Bug 59650 has been marked as a duplicate of this bug. ***,1390023730,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",*** Bug 53659 has been marked as a duplicate of this bug. ***,1390023708,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",*** Bug 59829 has been marked as a duplicate of this bug. ***,1390023700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","(In reply to comment #1)
+> If we want to perform clean-up like this, then we should perhaps implement
+> that in Parsoid rather than VE so that other users benefit from it as well.
+
+Happy for it to be done in Parsoid instead, and for us to remove the dropping from VE.",1384481135,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","If we want to perform clean-up like this, then we should perhaps implement that in Parsoid rather than VE so that other users benefit from it as well.",1384474548,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Blurred Autonym font
+
+Interwiki names blurred and legible with difficulty (using the hardcoded ""Autonym"" font)
+
+Firefox 25 / WinXPSP3 / standard antialiasing (= no ClearType)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows 7
+**Platform**: PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=40874
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56552
+https://github.com/santhoshtr/AutonymFont/issues/38
+https://github.com/santhoshtr/AutonymFont/issues/50
+
+**Attached**: {F12122}",1383081900,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_description,resolved
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",Thanks for confirming.,1390379901,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #87)
+> (In reply to comment #86)
+> > With the tofu detection that recently added into ULS, users no longer see
+> > degradation of text quality for fonts they have. I think that addresses the
+> > main concern of this bug report.
+> 
+> That was https://gerrit.wikimedia.org/r/#/c/108024/
+> 
+> Given https://gerrit.wikimedia.org/r/#/c/108735/ I think the change can
+> currently be tested (only) on test.wikipedia.org. The main page may suffice:
+> https://test.wikipedia.org/wiki/Main_Page
+
+So, the fix is apparently not deployed on testwiki, but it *is* deployed on beta labs: http://en.wikipedia.beta.wmflabs.org/ (after you register and enable ULS). And it does seem to help there, most language names are displayed in normal fonts for me; the list still looks pretty silly with some language names being pretty and antialiased and some not, but it's definitely better.",1390378545,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #87)
+> (In reply to comment #86)
+> > With the tofu detection that recently added into ULS, users no longer see
+> > degradation of text quality for fonts they have. I think that addresses the
+> > main concern of this bug report.
+> 
+> That was https://gerrit.wikimedia.org/r/#/c/108024/
+> 
+> Given https://gerrit.wikimedia.org/r/#/c/108735/ I think the change can
+> currently be tested (only) on test.wikipedia.org. The main page may suffice:
+> https://test.wikipedia.org/wiki/Main_Page
+
+This has not fixed the issue for me; the list of languages still looks just like in the screenshots provided here.",1390377652,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #82)
+> This bug cannot be marked ""fixed"" but should become a tracker, [...]
+
+But the tracked bugs are on another bug tracker; that's the difficulty.
+
+(In reply to comment #86)
+> With the tofu detection that recently added into ULS, users no longer see
+> degradation of text quality for fonts they have. I think that addresses the
+> main concern of this bug report.
+
+That was https://gerrit.wikimedia.org/r/#/c/108024/
+
+Given https://gerrit.wikimedia.org/r/#/c/108735/ I think the change can currently be tested (only) on test.wikipedia.org. The main page may suffice: https://test.wikipedia.org/wiki/Main_Page",1390375567,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","With the tofu detection that recently added into ULS, users no longer see degradation of text quality for fonts they have. I think that addresses the main concern of this bug report.
+
+For the fonts users don't have, the issue is still present. However, going from completely unreadable tofu to more readable autonym font is an improvement in my opinion.",1390369610,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #78)
+> ULS has been disabled on all wikis except Wikidata (bug 46306 +
+> https://gerrit.wikimedia.org/r/108735), so this bug is not relevant for WMF
+> wikis right now. Considering we also have two duplicate reports on GitHub I
+> think it's clearer to close this one.
+
+This isn't in keeping with standard practice. We usually tag the local bug as upstream and leave the local bug open in order to make discovery easier.
+
+Thank you for adding the GitHub links to the ""see also"" section.",1390347616,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I'd also reopen this bug. Only because ULS can be switched off now does not mean it will not be used by people who find it useful. Additionally I could personally imagine the default state of the newly created option to be switched to ""enabled"" in future (therefore enabling ULS by default unless the user opts out).
+
+The bad font rendering was one of the worst annoyances around ULS (and probably the most visible one). Especially since it basically broke something that worked without problems before.
+
+I'd keep this bug open to track the progress of the ""upstream"" bug in Git.",1390344289,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #82)
+> I also agree that forcing ULS completely off is a bad situation. At least it
+> should remain as an optional gadget in user preferences, possibly in the Beta
+> preferences...
+
+You can still enable it in the user preferences > User profile > Internationalisation.",1390343760,PHID-USER-zzlez5ppzytn7ghyo6sc,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I also agree that forcing ULS completely off is a bad situation. At least it should remain as an optional gadget in user preferences, possibly in the Beta preferences.
+
+I really love the possibility of switching user langguage of the interface in one click, notably for testing translatable pages, usng the ULS icon at top of pages, even if I did not like much the ugly look of the Autonym font
+
+Nothe that the Autonym font lacks is still lacking a BOLD version, for example in language navboxs displayinf the current language in Bold black instead of a normal link, or usable with the LangSelect template or the ""multilingual"" on Commonns, where all language autonyms are displayed. If the ""autonym"" class is present, and Autonym webfont downloaded, the browser will use synthetic bold which is almost unreadable in sme scripts like Hebrew.
+
+This bug cannot be marked ""fixed"" but should become a tracker, expecting for more work to be done. IT should remain open or at least replaced by a new tracking bug collecting the efforts in ULS and all the various things to do to improve it.
+
+So please reenable ULS at least in Beta preferences, and split ULS into several separate gadgets (Webfonts alone independantly of languages, IME, script variant selector for Chinese with automated transliterators, per-languuage font preferences with or without webfonts, and UI language selector) even if there remains a central dialog to setup all these components.",1390343377,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",Now that ULS is disabled by default the usage of webfonts is totally broken: https://de.wikipedia.org/wiki/Benutzer:Raymond/Webfonts :-(,1390339861,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #79)
+> This still applies if somebody chooses to enable ULS. I suggest reopening.
+
+Indeed we don't know what was the rationale for bug 46306, but I suppose it was that one will just disable ULS if one doesn't see a benefit. So if the Autonym font gives you problems you won't enable it. Unregistered users can't enable preferences, so the ""if somebody chooses to enable ULS"" scenario doesn't apply to them.
+So, yes, technically the issue still exists but not in default code.",1390339529,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",This still applies if somebody chooses to enable ULS. I suggest reopening.,1390338559,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","ULS has been disabled on all wikis except Wikidata (bug 46306 + https://gerrit.wikimedia.org/r/108735), so this bug is not relevant for WMF wikis right now. Considering we also have two duplicate reports on GitHub I think it's clearer to close this one.
+
+General discussion continues at bug 56292, bug 60304 tracks the revert of bug 46306, the future is unknown but should be bug 56433 comment 22.",1390338333,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",*** Bug 57999 has been marked as a duplicate of this bug. ***,1388320739,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","importing glyphs from some free fonts is not enough; some scripts need that you also borrow the OpenType features allowing their contextual selection (for now only the Arabic contextual forms are borrows, Indic scripts are ignored so you only get the isolated forms of their letters, e.g. in Devenagari or Myanmarese). The result is then incorrect.
+
+The mandatory features should be obeyed, even if we can safely ignore optional features  such as variant forms, decorated forms (unless they are usually used in autonyms, but anyway even in HTML these optional features are not rendered unless you activate them specifically with specific CSS styles).
+
+-- see the OpenType specs about which opentype feature is mandatory for each documented script; note that some scripts are still not documented, OpenType specifications are still a work in progress, even for scripts which are already encoded in Unicode, notably for the most recently added ones. For example the Myanmarese and Tibetan scripts require some mandatory features still not documented, but that have been tried by various font vendors with more or less success. Only the Arabic script is very precisely documented, not just informatively in OpenType, but normatively in the Unicode specifications for its contextual joining types, which become madatory features in the OpenType specs, and similar features in other font technologies like AAT, Graphite, or SVG fonts. --
+
+Thanks for pointing where the fonts are developed.
+
+I note that your Github repository contains a ""languages.txt"" file that you maintain yourself manually, when it should be generated from the wiki, using a Lua or PHP script enumerating all supported language codes (from the Site matrix, or from languages.php) and generating the list using te equivalent of {{#language:code}} in wiki syntax. This list may evolve over time when the Language Committee will add new wikis, or when it will decide to change the preferred language names.
+
+Your list is completely unordered, and as it is long, it will be hard to see if it does not contain duplicates, or alternate names no longer supported, or typos. I suggest you sort this list by importing it in an Excel column to sort it in CLDR order (make sure you've selected the English language in your Excel document so that its CLDR collation tailoring will be correct and stable).
+
+The other option is to prefix each line in languages.txt by the language code and a TAB or SPACE before the autonym, allowing to sort the file simply by language code. These language codes (using lowercase Badic latin letters a-z and the hyphen-minus) and TAB or SPACE will not pollute the list of characters to include into the Autonym font which already need these characters for the autonyms themselves (the only addition would be the TAB or SPACE separator and the newline characters which are already mapped in the font, so you  don't need specific character filters for these, when your script will generate the list of Unicode characters to map in the generated font).
+
+For stability of the font (if there are several deployed versions of MediaWiki with different lists of languages supported by #language), you may want to add an additional ""mul"" language for adding additional characters to keep, or use a versioned line (such as ""kk-x-1.2"" containing the language autonym for Kazakh in version 1.2), so that the Autonym font for ULS will work on all wikis with different versions of their language support.
+
+Note also that these generated language names may contain RLM/LRM marks (which you don't need to map to glyphs in the geenrated fonts, are they are to be supported only by the text renderers themselves; but if you map glyphs for these controls, they should be completely empty with a zero-width advance, or should be mapped to symbols for visible controls, but this is not a good thing to do for this Autonym font which is not intended to be used in text editors with a ""visible controls"" mode).",1385275154,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Nux, (In reply to comment #68)
+> Hi. Not sure what you've used for generating the font, but if you've used
+> fontsquirrel.com, then consider the following:
+> 1. Generate SVG font (if you're not doing it already).
+> 2. Use ttf above woff.
+> 3. Preserve original hinting if it was available.
+
+ULS Preserve the hints in woff and eot. See
+https://gerrit.wikimedia.org/r/#/c/95987/ (Nov 20)
+
+Documentation about how the fonts are developed: https://github.com/santhoshtr/AutonymFont/
+
+And about how webfonts are created: see http://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector#Preparing_webfonts
+
+Note the 200% size increase in your version of the font from fontsquirrel.",1385272433,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","> For this project, just uploading the generated fonts into the MediaWiki
+repository is clearly not enough, there should exist a full project containing
+or documenting the build tools used to perform these conversions.
+
+I don't agree. The generated font is better in practice. In practice all fonts are visible and selectable (or at least in all browsers I tried).
+
+Also note that there is a configuration in the attachment describing the process (""generator_config.txt""). So the effect should be reproducible without any problems.
+
+If you can make a better font go ahead. Seriously. I know that the tool (fontsquirrel) is not perfect. I've converted a different font and had to do a lot tweaking to get good results. BUT we should progress to a better solution then the current one and then fix other issues (if we can).",1385213144,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Also the ""missinglyph"" item of the SVG is just mapped with an advance-width equal to the space character; it has no path for the glyph itself, where it should have a path drawing an empty box in that space.
+
+The unselectable glyphs seem to come from an incomplete conversion tool, that does not know really how to map the glyphs selectable by OpenType features into the necessary mappings for making them selectable by the SVG font.
+
+An SVG font cannnot use OpenType feature, because it lacks the logic included in the OpneType renderers to select these features. OpenType features have implicit selection rules from the script and character properties. Then each feature adds GSUB and GPOS rules for mapping glyph definitions. In an SVG font, all the implicit rules must be mapped (the only exception supported by current relase of the SVG font spec being the Arabic joining type). This means that Indic script cannot work with simple one-to-one mappings of a character code to a glyph, with their required features. You need to map Unicode strings (not characters) into a SVG glyph definition to support the equivalent of contextual substitutions, and use the ""hkern"" (or ""vkern"") definitions to support the equivalent of OpneType GSUB (for contextual positioning).
+
+I think that the tool used to convert OpenType fonts to SVG font is insufficient for ""complex scripts"" (those that have REQUIRED features needed; see the OpenType specfiications). This means that extra manual tweaking are needed in the SVG font to make it work correctly (the existing tool is not doing things properly with its one-to-one character-to-glyph mappings, and its bogous unselectable zero-to-one mappings).
+
+For this project, just uploading the generated fonts into the MediaWiki repository is clearly not enough, there should exist a full project containing or documenting the build tools used to perform these conversions.",1385174944,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I don't why are those glyphs present but I think they won't be used anyway if they don't have `unicode` attribute. If someone knows for sure they are not needed, then I guess they can be removed. BTW selecting characters (and copy&paste) works fine for me for all characters used for Main Page.",1385165474,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Note that the SVG version includes 76 glyphs which are not selectable at all (they have no unicode attribute and no id attribute referenced by some assigned glyph with script features. I wonder how they can be present, or if the tool converting TTF fonts to SVG fonts simply lacks info on how to map the opentype features needed to select and render these contextual glyphs. Some of these glyphs are also non-spacing (no horiz-adv-x attribute) but also not correctly selected. Some of them are for mandatory ligatures, and should be selectable by an unicode attribute specifying 2 Unicode characters, or sometimes more.
+Only the contextual forms of letters in the Arabic script (up to 3 in addition to the default isolated form) are selectable.",1385148146,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #69)
+> Created attachment 13871 [details]
+
+Nice! Thank you Maciej!
+It looks great on Windows XP too (Windows 7 was the worse).
+
+Now, could we replace the current
+
+https://bits.wikimedia.org/static-current/extensions/UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.ttf?version=20131112
+and
+https://bits.wikimedia.org/static-current/extensions/UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.woff?version=20131112
+
+with these uploaded by Maciej?
+
+This should then allow us to close this bug.
+
+**Attached**: {F12132}",1385125998,PHID-USER-mapumhlp3gw5qefhvafn,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13871
+Fixed font - notice how the font is defined in stylesheet.css!
+
+Fontsquirrel to the rescue :-). Attaching fixed font (made from automnym.ttf).
+
+Have tested on IE 10, Opera 12, Chrome 31 and Firefox 25 (Windows 7). All glyphs in all sizes seem fine and readable beyond font size 11.
+
+Also tested in IE compatibility modes. The font remains readable even in IE 8, though kerning seem worse in this version (better from IE 9 up). If you see this as a problem then you can set `letter-spacing:.1em`.
+
+**Attached**: {F12132}",1385077916,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Hi. Not sure what you've used for generating the font, but if you've used fontsquirrel.com, then consider the following:
+1. Generate SVG font (if you're not doing it already).
+2. Use ttf above woff.
+3. Preserve original hinting if it was available.
+
+You might want to experiment a bit, but that was the best options for me when generating web fonts from open type font.",1384968104,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Autonym font is a soulution for a problem, that never existed before ULS. Even now I didn't understand the reason to serve (load) webfonts by default to Latin languages. Nowadays even problematic Indic languages have much better support in OSs, a situation which makes Webfonts less than a necessity there. So I think most favorable solution may be disabling webfonts than 'temporarily intelligent' solutions like problematic Autonym font.",1384967107,PHID-USER-zmjwaqq2chic4csbxwuy,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Here some screenshot on Firefox 25, Windows LCD rendering (*).
+
+12px (en.wikipedia): http://files.espace-win.org/2013/Capture.PNG
+13px (fr.wikipedia): http://files.espace-win.org/2013/Capture2.PNG
+
+(*) There are two fonts rendering mode on Windows, one with LCD support when ClearView option is enabled, one without.",1384964635,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Then the font in this one sidebar section would be larger than in all the other ones, which is going to look even more silly than the current state. I suggest not doing that.",1384959098,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","To achieve comment 63 suggestion:
+
+  #p-lang-list li {
+      font-size: 0.8125em !important;
+  }",1384957802,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #62)
+> The critical bad rendering occurs:
+> * when rendering font sizes below 13px (for example, small text: you loose
+> important pixels: don't render lists of languags with a reduced font size;
+> unfortunately the default font-size of MediaWiki is reduced from the browser
+> standard, so you see these effects with lost pixels).
+
+Actually, 13px (0.8 x 16px) is the default for Vector, and Autonym looks acceptable at 13px. However, the navbar has its font-size set to 0.75em, which causes Autonym to drop to 12px, and the problem is very apparent.
+
+Seems like a little CSS tweaking on #p-lang might solve the primary concern.",1384889978,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Note that it's true that the Autonym font lacks hinting; but my test page demonstrates that it should not be used with all CSS styles, but that it works quite well within some limits (font-size:13px;font-weight;normal;font-style:normal;letter-spacing:normal), provided that the browser does not zoom in, on displays with low pixel densities (96dpi).
+
+Displays with high pixel densities look OK (example: smartphones that typically have densities around 190 dpi or more). With their default zoom (you'll experience poor readability only if you soom out).
+
+The critical bad rendering occurs:
+* when the browser zoom is around 120-150 dpi, because glyphs are just scaled up from a low dpi rendering (around 96 dpi on desktops/notebooks displays) without hinting, or
+* when rendering font sizes below 13px (for example, small text: you loose important pixels: don't render lists of languags with a reduced font size; unfortunately the default font-size of MediaWiki is reduced from the browser standard, so you see these effects with lost pixels).",1384869728,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #37)
+> Against this common sense ULS was designed to load webfonts for a huge bunch
+> of
+> languages. Therefore we started to load additional font support for every
+> Wikipedia user, even if it was most unlikely that a user actually needed it.
+
+You're wrong! Autonym in ULS was designed to load ONLY this font instead of a bunch of fonts.
+
+Performance tests show that
+* the download bandwidth uis highly reduced because ULS no longer needs to download many fonts (OK you don't download fonts for your installed system fonts)
+* the time to render the page is faster (the Autonym webfont is normally cached by your brower, it won't load again when you navigate, unless it has been updated on the server)
+* the browser needs to load many less fonts to render lists of language names: with your many system fonts configured for each script or language by your CSS preferences or by your browser settings, the browser will need to load all these system fonts in memory (even if the browser also uses a font rendering cache).
+* Nothing is changed for the rest of the page content (outside language autonyms): the content still uses your own choice of fonts
+* You can tweak webfonts used by ULS to use other more complete (and hinted) webfonts proposed by ULS: they will override the Autonym font if the span element containing the language name does not only use the CSS class ""autonym"", but also sets the lang="""" attribute to specify its language.
+* You can tweak you own CSS rules to provide other local fonts you have for a specific language using CSS lang() selectors.",1384869013,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Note that the rendering of the Autonym font may be tweaked with ULS, provided that the span using the autonym class also sets the lang attribute (as it should).
+
+So you can use ULS to select another supported webfont for each language supported by ULS. The Autonym font will be used only if you select ""use system font"" in ULS for that language. If you select another proposed webfont, it will override the font specified in that class (and this other webfont will be loaded by your browser to render this language).",1384868416,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","For reference, you may look at this page which tests the Autonym font with all Active Wikimedias, under various styles:
+
+https://meta.wikimedia.org/wiki/Wikimedia_Forum/Autonym_font_test_with_active_Wikipedias",1384868152,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+(In reply to comment #57)
+> (In reply to comment #41)
+> > (In reply to comment #37)
+> > > Autonym (which will by definition never be as good as a native font like Arial on Windows)
+> > 
+> > I don’t understand the logic of this. Arial is hardly a great typeface
+> > anyway.
+> 
+> Don't confuse design with legibility. Arial is the default sens-serif on
+> Windows, and renders *very* well on Windows. Autonym renders *very* bad on
+> Windows, because the font (and its source FreeSans) were never desigend with
+> Windows in mind, and therefor lack any hinting.
+
+Sure, the design of a typeface doesn’t matter as much if your system distorts the character shapes to fit a pixel grid. As higher-resolution displays are becoming common, screen hinting is going away and good font design is starting to be considered good font design. 
+
+Anyway, the immediate fix is to import hinted character outlines from a better free font. Yes, easier said than done, but there’s no reason it couldn’t match Arial’s quality in any particular OS or browser.
+
+
+> 
+> > A simple fix for much of this would be to embrace installed fonts, and push
+> > Autonym to the bottom of a font stack that includes the default sans-serif
+> > fonts on the various platforms. I wonder if, indeed, “font-family:
+> > sans-serif, autonym;” would work to make this font the fallback’s fallback.
+> > Ideally, it should only be rendering text that would show up as tofu. Ideally.
+> 
+> I doubt it. Windows usually uses the first available font in the font stack
+> and
+> sticks with it, and revert to its default unicode font if it can't find a
+> glyph
+> (usually Lucida Sans Unicode).
+
+I think it might be more complicated than that. MSIE 6 ignores fallbacks for individual characters missing from a font, but I understand that newer versions have improved on this. As far as I know, Firefox uses its own font choice and rendering engine.",1384798166,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #41)
+> (In reply to comment #37)
+> > Autonym (which will by definition never be as good as a native font like Arial on Windows)
+> 
+> I don’t understand the logic of this. Arial is hardly a great typeface
+> anyway.
+
+Don't confuse design with legibility. Arial is the default sens-serif on Windows, and renders *very* well on Windows. Autonym renders *very* bad on Windows, because the font (and its source FreeSans) were never desigend with Windows in mind, and therefor lack any hinting.
+
+> A simple fix for much of this would be to embrace installed fonts, and push
+> Autonym to the bottom of a font stack that includes the default sans-serif
+> fonts on the various platforms. I wonder if, indeed, “font-family:
+> sans-serif, autonym;” would work to make this font the fallback’s fallback.
+> Ideally, it should only be rendering text that would show up as tofu. Ideally.
+
+I doubt it. Windows usually uses the first available font in the font stack and sticks with it, and revert to its default unicode font if it can't find a glyph (usually Lucida Sans Unicode).",1384796366,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #52)
+> Created attachment 13824 [details]
+> ENWP Sidebar, Windows 8, IE 10
+
+Seems like ordinary Arial. In other words, it does not use Autonym in this screenshot.
+
+**Attached**: {F12131}",1384795823,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #54)
+> (In reply to comment #51)
+> > Screenshot on a default Windows 8, IE 10
+> > 
+> > Good news? It seems better on Windows 8.
+> 
+> From your screen-shots, it seems there's something fundamentally wrong with
+> your font rendering(besides anything Autonym may cause):
+> - Do you notice the uneven thickness of vertical lines? This should not occur
+> if Hinting works as expected.
+> - You seem to have Subpixel-anti-aliasing (alias ClearType) turned off, but
+> you
+> seem to be still utilizing some sort of grayscale-anti-aliasing. Is this on
+> purpose?
+
+I have no idea at all. I happened to be using a Windows 8 PC (not mine) and took those screenshots.",1384789243,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #51)
+> Screenshot on a default Windows 8, IE 10
+> 
+> Good news? It seems better on Windows 8.
+
+From your screen-shots, it seems there's something fundamentally wrong with your font rendering(besides anything Autonym may cause):
+- Do you notice the uneven thickness of vertical lines? This should not occur if Hinting works as expected.
+- You seem to have Subpixel-anti-aliasing (alias ClearType) turned off, but you seem to be still utilizing some sort of grayscale-anti-aliasing. Is this on purpose?",1384788368,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #51)
+> Good news? It seems better on Windows 8.
+
+Could you test it with either Firefox/Chrome/Opera to make sure it's not just IE?",1384787796,PHID-USER-mapumhlp3gw5qefhvafn,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13824
+ENWP Sidebar, Windows 8, IE 10
+
+**Attached**: {F12131}",1384785419,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13823
+Screenshot on a default Windows 8, IE 10
+
+Good news? It seems better on Windows 8.
+
+**Attached**: {F12129}",1384785375,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Also setting ""Windows 7"" as the most recent Windows cited as having the problem (""PC"" is a bit too generic).",1384761625,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #48)
+> (In reply to comment #47)
+> > (In reply to comment #44)
+> > > @Nemo: Thanks for comment 43, very helpful!
+> > > 
+> > > @Erik: Could you clarify comment 36? Which other systems did you experience
+> > > the
+> > > problem with?
+> > > 
+> > > (In reply to comment #42)
+> > > > It would help if this bug identified the specific code revisions (Gerrit
+> > > > links) that are responsible for this recent regression.
+> > > 
+> > > @MZMcBride:
+> > > https://blog.wikimedia.org/2013/10/28/the-autonym-font-for-language-names/
+> > > links to https://bugzilla.wikimedia.org/show_bug.cgi?id=40874 which links to
+> > > https://gerrit.wikimedia.org/r/#/c/84850/ and
+> > > https://gerrit.wikimedia.org/r/#/c/84851/
+> > 
+> > Um, now I must admit I had not tested it on any other systems until now. Don't know why I thought it was cross-platform. Mea culpa.
+> > --Eric",1384749410,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #47)
+> (In reply to comment #44)
+> > @Nemo: Thanks for comment 43, very helpful!
+> > 
+> > @Erik: Could you clarify comment 36? Which other systems did you experience
+> > the
+> > problem with?
+> > 
+> > (In reply to comment #42)
+> > > It would help if this bug identified the specific code revisions (Gerrit
+> > > links) that are responsible for this recent regression.
+> > 
+> > @MZMcBride:
+> > https://blog.wikimedia.org/2013/10/28/the-autonym-font-for-language-names/
+> > links to https://bugzilla.wikimedia.org/show_bug.cgi?id=40874 which links to
+> > https://gerrit.wikimedia.org/r/#/c/84850/ and
+> > https://gerrit.wikimedia.org/r/#/c/84851/
+> 
+> Um, now I must admit I had not tested it on any other systems until now. Don't > know why I thought it was cross-platform. Mea culpa.
+> --Eric",1384749365,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #44)
+> @Nemo: Thanks for comment 43, very helpful!
+> 
+> @Erik: Could you clarify comment 36? Which other systems did you experience
+> the
+> problem with?
+> 
+> (In reply to comment #42)
+> > It would help if this bug identified the specific code revisions (Gerrit
+> > links) that are responsible for this recent regression.
+> 
+> @MZMcBride:
+> https://blog.wikimedia.org/2013/10/28/the-autonym-font-for-language-names/
+> links to https://bugzilla.wikimedia.org/show_bug.cgi?id=40874 which links to
+> https://gerrit.wikimedia.org/r/#/c/84850/ and
+> https://gerrit.wikimedia.org/r/#/c/84851/
+
+Um, now I must admit I had not tested it on any other systems. Don't know why I thought it was cross-platform. Mea culpa.
+--Eric",1384749167,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #43)
+> (In reply to comment #42)
+> > It would also help, for triaging, to know how many operating systems/browsers
+> > are affected (or rather, what percentage of typical users)? Only Windows
+> > users?
+> 
+> So far the only information provided pointed exclusively to Windows problems;
+> Erik removed Windows from the platform/OS fields shortly after comment 36
+> without clarifying why.
+
+Sorry, I switched the platform/OS to ""all"" because I thought this problem was not restricted to Windows. However, just now I checked on a Mac in Firefox and Chrome and did not encounter the text-blurring problem. But I'll leave it to someone else to switch back as I have not tested it on any other systems.
+--Eric",1384749061,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+language-choice text blurring on Commons
+
+screenshot of language-choice link text blurring, Win7 64-bit, Firefox 25, Chrome 31.0.1650.57 m
+
+**Attached**: {F12128}",1384748728,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","@Nemo: Thanks for comment 43, very helpful!
+
+@Erik: Could you clarify comment 36? Which other systems did you experience the problem with?
+
+(In reply to comment #42)
+> It would help if this bug identified the specific code revisions (Gerrit
+> links) that are responsible for this recent regression.
+
+@MZMcBride:
+https://blog.wikimedia.org/2013/10/28/the-autonym-font-for-language-names/ links to https://bugzilla.wikimedia.org/show_bug.cgi?id=40874 which links to https://gerrit.wikimedia.org/r/#/c/84850/ and https://gerrit.wikimedia.org/r/#/c/84851/",1384741481,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #42)
+> It would also help, for triaging, to know how many operating systems/browsers
+> are affected (or rather, what percentage of typical users)? Only Windows
+> users?
+
+So far the only information provided pointed exclusively to Windows problems; Erik removed Windows from the platform/OS fields shortly after comment 36 without clarifying why.",1384737391,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","It would help if this bug identified the specific code revisions (Gerrit links) that are responsible for this recent regression.
+
+It would also help, for triaging, to know how many operating systems/browsers are affected (or rather, what percentage of typical users)? Only Windows users?",1384737203,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+(In reply to comment #37)
+
+I don’t completely agree with Eduard Brown.
+
+WikiMedia hosts an unusual multilingual range of websites on unusual multilingual software. Text in some languages appears broken on many computers. There is nothing wrong with aspiring to fix the breakage when the technology is available.
+
+
+> Common sense dictates that users have fonts installed for their native
+> languages.
+
+An ideal. The reality is that millions of people cannot install fonts on the devices they depend on, for many different reasons. Smartphone users? Refugee immigrants relying on library computers configured in a language they barely know? They deserve access to information.
+
+
+> Autonym (which will by definition never be as good as a native font like Arial on Windows)
+
+I don’t understand the logic of this. Arial is hardly a great typeface anyway.
+
+
+> I'm afraid there is definitely room for improvement right now!
+
+True. I don’t know why this was pushed out without some basic testing on common platforms. 
+
+Most modern browsers on modern OSes render most language scripts these days. A simple fix for much of this would be to embrace installed fonts, and push Autonym to the bottom of a font stack that includes the default sans-serif fonts on the various platforms. I wonder if, indeed, “font-family: sans-serif, autonym;” would work to make this font the fallback’s fallback. Ideally, it should only be rendering text that would show up as tofu. Ideally.",1384732866,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #38)
+> [Removing random added keywords, see
+> https://bugzilla.wikimedia.org/editkeywords.cgi ]
+
+Sorry my addition of those keywords seemed random, Andre. It wasn't, but I'm not very experienced with Bugzilla. It seemed several commenters felt this bug was not drawing enough attention, and my reading of the design and community-consensus-needed keywords led me to believe they would be appropriate here and might draw more attention.
+--Eric",1384698800,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #38)
+> [Removing random added keywords, see
+> https://bugzilla.wikimedia.org/editkeywords.cgi ]
+
+https://bugzilla.wikimedia.org/describekeywords.cgi
+
+The original link doesn't work for normal users.",1384692209,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","[Removing random added keywords, see https://bugzilla.wikimedia.org/editkeywords.cgi ]",1384692058,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I share the opinion of many others:
+
+Autonym is actually
+a) a fix for a problem that most people never experienced.
+b) making thinks even worse as they would have been without ULS and Autonym in the first place
+
+
+The whole sad story from my point of view:
+
+Common sense dictates that users have fonts installed for their native languages. If they work multilingual they're most likely do also have all fonts necessary for those languages installed on their system. On top of that we can assume that on all modern systems there's support for even more languages that a normal user never ever needs anyway.
+
+Against this common sense ULS was designed to load webfonts for a huge bunch of languages. Therefore we started to load additional font support for every Wikipedia user, even if it was most unlikely that a user actually needed it.
+
+It turned out, that ULS was detrimental to performance. The additional traffic due to webfonts loading seems to have been so large, that even WMF saw the need for a change (I'm quite sure WMF would not have even cared to develop Autonym if it had only affected client performance).
+
+Now we have Autonym, which brings all sorts of problems, including the extremely bad rendering we're discussing in this bug...
+And now we're trying hardly to fix font rendering of Autonym (which will by definition never be as good as a native font like Arial on Windows), because we put much effort into Autonym, which was a fix for the bad performance for ULS, which was a huge project supported by WMF which was supposed to fix problems and add features... that users never faced and seldom requested!
+
+
+The whole thing seems pretty messed up to me, like many things that come from WMF lately. Since I see Siebrand Mazeland is active on this bug (who is the ""Product Manager Language Engineering"" of the WMF after all and therefore probably the one in charge for everything we're discussing here): Think about the doubts many users have about ULS, Autonym and all the other new language features. And think about why there are no users praising ULS, while there are tons of users facing problems with ULS and everything that is connected to it... I don't want to blame you for doing a bad job - but I'm afraid there is definitely room for improvement right now!",1384563438,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+Comment on attachment 13809
+screenshot font-rendering, en.wp in Firefox 25, Win7
+
+Seeing problem in Commons as well in language choice link (upper right).",1384556433,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+screenshot font-rendering, en.wp in Firefox 25, Win7
+
+Similar to ""Autonym glyphs are missing pixels"" shot.
+
+**Attached**: {F12127}",1384542694,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",Has there been any progress with this? What is the status? Is it supposed to be fixed? (Because it's not.),1384542094,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #31)
+> ULS master has hinting added for the Autnym font. This is active in the
+> Wikimedia branch 1.23wmf3.
+
+I see no difference. Do I need to do something? (Tested on pl.wikt, which is at wmf3 now.)",1384280994,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+(In reply to comment #30)
+> What's the plan for this bug?
+
+I wonder why you are asking this question. There is no ""plan"". For the average Bugzilla report it's often like ""ignore it long enough to make the users give up and stop complaining about, then pretend there is no problem"". It doesn't even matter if a report is almost 10 years old and received 50 votes (e.g. bug 674). There is no developer assigned and there are no developers to assign. WMF always moves them to the next project in the moment a feature is deployed. Sometimes the original developers even left WMF. If you are lucky a volunteer will make a pull request.
+
+I really, really don't understand why such bad changes aren't reverted (which would be simple), fixed (which may be hard) and deployed again (which is again simple). It's like WMF is more afraid of reverting something than being criticized for making bad changes. Why is that?
+
+I'm sorry, Andre, I'm just trying to explain what many users actually think. Reports like this are just tips of the iceberg.
+
+(In reply to comment #31)
+> ULS master has hinting added for the Autnym font.
+
+What about excluding the Wikidata link from using the font? What about excluding all Latin languages from using a font they don't need? What about delivering the font only to browsers that would show rectangles otherwise?",1384268462,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #30)
+> What's the plan for this bug?
+
+ULS master has hinting added for the Autnym font. This is active in the Wikimedia branch 1.23wmf3.",1384267110,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",What's the plan for this bug?,1384262802,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","As I quickly realized, and confirmed at the Autonym website, the majority of Latin glyphs were extracted form FreeSans, possibly the worst-rendering (at leats on Windows) open source font available. FreeSans (as well as the other UCS/GNU FreeFonts) lack *any* type of hinting, on which Windows relies for proper font rendering. We could blame Windows, but that will not solve anything.
+
+Autonym should find a better source for its Latin glyphs, preferably Nimbus Sans L (on which FreeSans is based!), which include at least some basic hinting.",1384194021,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #0)
+> Created attachment 13624 [details]
+> Blurred Autonym font
+> 
+> Interwiki names blurred and legible with difficulty (using the hardcoded
+> ""Autonym"" font)
+> 
+> Firefox 25 / WinXPSP3 / standard antialiasing (= no ClearType)
+
+Screenshot of
+https://www.mediawiki.org/w/index.php?title=UniversalLanguageSelector/AutonymFont
+using FF22 on Windows XP SP3 with the latest version of font http://app.crossbrowsertesting.com/public/id1b2af101bb8ef7/livetests/1196568/snapshots/zb68cdfaa35be26924f1 , font size 13px
+
+**Attached**: {F12122}",1384007121,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #26)
+> IE6? OK. Let's be serious. Majority of other users INCLUDING users of IE6 are
+> served with a bad font.
+
+
+IE 6(or anything less) will not get this font as per latest changes. Screenshot of https://www.mediawiki.org/w/index.php?title=UniversalLanguageSelector/AutonymFont using IE6 on Windows XP
+
+http://app.crossbrowsertesting.com/public/id1b2af101bb8ef7/livetests/1196571/snapshots/z7f7810ca035e37ef94c",1384006480,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","IE6? OK. Let's be serious. Majority of other users INCLUDING users of IE6 are served with a bad font. Users that are interested in certain language will have glyphs for the font they are interested. So using a bad font just creates a bad experience for all users.
+
+BTW. The font looks good only for 13px. So if you must please at least change default size.
+
+Also BTW, notice this font rendering is bad in almost any other size then 13px.",1384004758,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+(In reply to comment #24)
+> I see that MSIE 6 accounts for 0.83% of traffic, well over the 0.1%
+> threshold,
+
+Holy Hannah, MSIE 5.5 also qualifies with 0.11%!",1383948834,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+Thanks for the enlightening links, all. 
+
+I see that MSIE 6 accounts for 0.83% of traffic, well over the 0.1% threshold, and thus remains supported as a grade B browser, for reading, but not necessarily having all features working. The same applies to MSIE 7 (1.47%) and 8 (4.71%). 
+
+All these guidelines carry out-of-date warnings, and don’t account for the conflicted grey area wherein MSIE 6 and 7 are supported for reading, but not for the ULS which provides fonts that may be necessary for reading. 
+
+I think the gist is that if you are using MSIE 6, you are more-or-less on your own, and may need to install some fonts. Editors and developers don’t want to abandon MSIE 6 users, but no one will invest time and energy into testing MSIE 6 and 7, so the realistic support level is “good luck, mate.”
+
+Also good to know that WikiMedia is, or was, supposed to work without CSS3, without JavaScript, and in text-only browsers.
+
+One more question: does the ULS try to work in MSIE 6 and 7, or is it disabled in these browsers?",1383948467,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(Yes, that's VE, which is not going to work with IE 6, but I guess the ""less than 0,1%""-rule is generic? It's also mentioned at https://www.mediawiki.org/wiki/Compatibility#Grade_B .) :)",1383931810,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #21)
+> https://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix
+
+That's VE. :) There's also https://www.mediawiki.org/wiki/Compatibility#Software_for_using_MediaWiki in general.
+
+https://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector states:
+""Not compatible with Internet Explorer 7 or lower.""",1383931585,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Michael: here https://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix (warning, old data) I read:
+""The unofficial rule for Wikimedia's browser support is that we try to support reading (and not necessarily other functions) for all browsers used by at least 0.1% of page hits based on the WikiStats data.""
+
+If I read http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm correctly, MSIE 6.0 does not meet that requirement.",1383930913,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+> #p-lang a[lang=ja], #p-lang a[lang=th] { ... }
+> 
+> Selectors like this work in all browsers including very old ones. Problem
+> solved.
+
+Doesn’t work in MSIE 6. Sadly, millions use it and I think we still intend to support it. See http://www.ie6countdown.com/
+
+Is there any official or community statement on which browsers we do support?
+
+
+> Don't you think all users
+> that are able and interested in a specific language have the proper fonts
+> installed? 
+
+No. I think the point is to make wikis accessible to people who can’t or won’t install software on their machines. This means tens of millions who rely on library or work PCs, or the latest mobile devices, or almost anything in between. Not only techies need to read their own language.
+
+That said, it would be nice if the font spec only applied to the necessary language names, whichever those may be.",1383929643,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+(In reply to comment #18)
+> something like "" font-family: sans-serif, ""Autonym""; ""
+
+Unfortunately this is not how it works. My suggestion was to apply the font only to language names with otherwise missing glyphs. For example, the list in the sidebar looks like this:
+
+<ul>
+<li class=""interwiki-en""><a lang=""en"" hreflang=""en"">English</a></li>
+<li class=""interwiki-fr""><a lang=""fr"" hreflang=""fr"">Français</a></li>
+<li class=""interwiki-ja""><a lang=""ja"" hreflang=""ja"">日本語</a></li>
+</ul>
+
+Remove the current rule:
+
+#p-lang ul { font-family: ""Autonym"", sans-serif; }
+
+Instead use a rule set like this for all non-latin language names:
+
+#p-lang a[lang=ja], #p-lang a[lang=th] { ... }
+
+Selectors like this work in all browsers including very old ones. Problem solved.
+
+At least exclude the Wikidata ""Edit links"" item from the rule by applying it only to items that are in an other language (this may be an other issue, please tell me if I should split this):
+
+#p-lang a[lang] { ... }
+
+Besides, what was the problem in the first place? Don't you think all users that are able and interested in a specific language have the proper fonts installed? In think missing glyphs or rectangles are only visible to people that aren't interested in these languages anyway. Again, I'm very sorry to say that but this looks like a fix without a real world problem to me. I'm aware that it may help a few people but the current way the font is used creates more problems than it solves.",1383927388,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","As suggested by TMg (comment #6), is it not possible to let the browser choose the Autonym font only if there are missing glyphs? I’m not very knowledgeable about the details, but I know it is the global goal of the CSS list of fonts in font-family; is something like "" font-family: sans-serif, ""Autonym""; "" would achieve the goal by only searching missing glyphs in Autonym?",1383916058,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #15)
+> Isn't this a regression, since it worked before?
+
+Technically no because it's a new feature, no fonts have been served for interwikis in the last few weeks to save on bandwidth etc.",1383549438,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13681
+Comparison Autonym Arial
+
+I made a sample to show the problem: Two times ""Nederlands"" is shown, first with Autonym and then with Arial. The font size (height) is the same, even though Arial is slightly wider. Arial is better readable, just compare the first ""e"" of ""Nederlands"" or the lower-case ""n"": they seem to have holes.
+
+**Attached**: {F12126}",1383530954,PHID-USER-ayv2najkcouorpblxvzo,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I also experience this bug, with FF 24.0 on Windows 7.
+Isn't this a regression, since it worked before?",1383523242,PHID-USER-7e4yonmruupxzg23swum,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+Firefox/Opera 12/IE 9 with ClearType enabled
+
+Here is an other screenshot with ClearType enabled. From left to right:
+
+* Firefox with hardware acceleration disabled
+* Opera 12
+* IE 9
+
+Same bug in Firefox and Opera, some pixels are completely missing. Enabling or disabling ClearType has no effect on this bug, obviously.
+
+IE 9 uses hardware acceleration by default. Because of this the font looks different. But it's also distorted. The glyphs are more narrow and more blurred compared to the default font (seen in the upper half of the screenshot). Some glyphs are distorted. Look at the ""g"" from ""English"" and the ""S"" from ""Suomi"".
+
+Enabling ClearType *and* hardware acceleration in Firefox makes it the same as IE 9. Enabling hardware acceleration *without* ClearType makes it worse. A lot worse. That's why I have no other choice than do disable both.
+
+Why don't you use the default fonts for simple words like ""English"" that don't contain any problematic characters?
+
+**Attached**: {F12125}",1383321748,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+The problem seems to be “missing pixels.” Only one of three screenshots shows anything “blurred” that isn’t also occurring in the default font. Might both be caused by lack of hinting, but might be two different bugs.",1383320257,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+The language names on en.wiktionary.org’s home page render correctly on Safari 6.1/Mac, Firefox 25/Mac, and Chrome 30/Mac (on OS X Mountain Lion).
+
+They also renders correctly on iPad Safari (iOS 5), except that Burmese and Khmer characters are broken anyway.
+
+But they render correctly on the Mac with the Autonym font disabled. Every language name renders every character with the font spec set to “sans-serif.” Developers, please stop trying to “fix” an OS that doesn’t need help. Just serve this font to systems that need it, and do a reasonable amount of testing before releasing.",1383320023,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Just for the record:
+
+The same issue is with the <languages/> box.
+
+(-> changing the summary to be more general)",1383313682,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(Strike that, answer is in comment 0; setting Platform.)",1383303490,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #6)
+> Suggested reading:
+> http://www.smashingmagazine.com/2012/04/24/a-closer-look-at-font-rendering/
+
+TL;DR: Windows is bad. Danny, do you use Windows?",1383303436,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+(In reply to comment #6)
+> Suggested reading:
+> http://www.smashingmagazine.com/2012/04/24/a-closer-look-at-font-rendering/
+
+See my ""Subpixel rendering is a lie"" comment there.",1383303226,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I'm guessing there's not hinting information in the font; Windows' TrueType font renderer is notorious for relying on good hinting for on-screen resolutions, while OS X and Linux tend to ignore it and optimize their rendering without hinting.
+
+I've gone ahead and filed an entry on the Autonym github issue tracker and copied the images (they're viewable inline there, for easier reference): https://github.com/santhoshtr/AutonymFont/issues/38",1383302524,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",Suggested reading: http://www.smashingmagazine.com/2012/04/24/a-closer-look-at-font-rendering/,1383301324,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+Autonym glyphs are missing pixels
+
+Please tell me if I should post this as a separate issue.
+
+I'm using Opera 12 on Windows 7 with ""Clear Type"" rendering turned off (on purpose, because I get headaches from the red and blue blurry shadows it adds around the glyphs). Unfortunately the rendering of Autonym is a mess (sorry to say that, it's the best word to describe what I see, see my screenshot). This makes the situation a lot worse compared to the situation before where a few glyphs may be missing or displayed as rectangles. Now some pixels are completely missing. An ""o"" looks like an ""u"" and ""m"" looks like ""rri"", for example.
+
+Proposed solution: Either fix the font or simply don't use it on systems that don't have a problem with displaying the glyphs in the interlanguage links. If I disable Autonym (using the web developers tools) everything is back to normal, no glyphs are missing and no rectangles are displayed. In other words: Don't ""fix"" things that aren't broken. Thanks.
+
+**Attached**: {F12124}",1383300531,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Temporarily it can be fixed by adding in personal css:
+#p-lang div.body ul { font-family: sans-serif; }",1383297916,PHID-USER-jbysj3sdbucij47t2xt3,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13642
+Screenshot from en.wp
+
+**Attached**: {F12123}",1383262405,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",I am getting very similar messed up rendering on Opera 12 on Windows XP with ClearType rendering enabled.,1383262199,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Cannot reproduce with Win8, FF25 and 1024x768 on https://cs.wikipedia.org/wiki/ on crossbrowsertesting.com (only offering FF23 for XPSP3).",1383241926,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page","An unclosed <ref> tag on the page eats up the rest of the page, typically including the requisite <reference> tag at the bottom of the page. However, VisualEditor handles the unclosed <ref> tag more gracefully, treating it as plain text.
+
+At the URL above, the wikitext:
+
+    Before <ref> during
+    after
+    <references />
+
+is rendered:
+
+    Before[1]
+    Cite error: <ref> tag found without <references/>
+
+whereas VisualEditor shows:
+
+    Before <ref> during↵after
+    There are no references on this page to include on this list.
+
+This issue was brought to my attention by an editor who somehow created the unclosed <ref> tag in VisualEditor. (See the initial revision of [[vi:Danh sách các chi tiết gợi nhớ đến Disney trong phim Enchanted]].) I’ve reached out to the editor for information on how they might’ve gotten into that state.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:Mxn/56306",1383041940,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-7y5mvenxogghsfr7glsa,task_description,declined
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page",https://gerrit.wikimedia.org/r/#/c/255258/ fixes PHP parser behavior. Nothing to do in Parsoid land.,1453350985,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page",The bug for the PHP parser is T17712.,1448403047,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page","I'm not sure; that depends what the more graceful behavior would be, but I would expect Parsoid to match Cite in any case. Does Parsoid's current behavior seem like a more reasonable way for Cite to handle unclosed <ref> tags?",1401478701,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page","So is this a request for matching the more graceful behavior in the PHP Cite implementation, or is it a request for Parsoid to truncate the page as well?",1401461783,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page","Never mind about that last part. It looks like they introduced the unclosed <ref> tag by hand, not using VisualEditor.",1383042640,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+Make ULS more lightweight,"For many users, ULS serves no practical purpose. It is also quite large, which can be problematic if you're not on a first-world internet connection (or are in rural US), is occasionally host to somewhat problematic bugs, and generally is not worth the trouble if you're not part of the target audience.
+
+So there should be a way for such people to just turn the thing off, not load it at all, and be happy.
+
+I appreciate that adding an option for this has been been wontfixed, though I don't know why, but even without there being an option in the interface, there SHOULD be support in the extension itself to disable it, regardless of where it actually appears.
+
+There should be a way for users who are truly and consistently inconvenienced by it to actually solve the underlying problem (such as with a hidden preference or cookie), instead of just hiding it. There should also be a way for third-party hosts to add such an option for their users who also fit the target audience, even if they don't necessarily want it on for everyone.
+
+As it is it seems to inconvenience as many people as it helps on wikimedia projects, and isn't very appealing to third-party hosts, either, despite it solving some very real problems facing some of our users as well.
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1383019140,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_description,resolved
+Make ULS more lightweight,Things have been improved. We are no longer loading lots and lots of code before user interaction. Now I get `jquery.uls.data` (31 KB) and few other modules <10 KB.,1468323414,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,Does someone know if this issue is still present and relevant for T15097? Seems not according to T58464#2452190,1468323163,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"https://www.mediawiki.org/wiki/Universal_Language_Selector/Announcement_Feb2014
+https://www.mediawiki.org/wiki/Universal_Language_Selector/Upcoming_development_plan",1392822875,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"Change 113957 merged by jenkins-bot:
+resources/images: Optimize all SVGs (partially by hand)
+
+https://gerrit.wikimedia.org/r/113957",1392799823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"Change 113957 had a related patch set uploaded by Bartosz Dziewoński:
+resources/images: Optimize all SVGs (partially by hand)
+
+https://gerrit.wikimedia.org/r/113957",1392734042,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"The table is from the output of mw.loader.inspect(). You can also run it from your developer tools console of your browser.
+
+But the result of that has a few caveats. ULS has to serve a small svg file(cog icon) to UI. See https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector/blob/master/resources/css/ext.uls.interlanguage.css#L1
+
+You can see the svg with 'embed' more than once. Also note that the ResourceLoader module will have css  with the image data embedded. So the RL module have  this repeated svg data at client side, it is an image, so it will have some size. While calculating the module size, the total size is javascript, css and this image data(potentially duplicated) at client side. But what matters is bandwidth usage and in this case you will see a big difference between actual bandwidth usage and the uncompressed RL module size at client side. This is because the module is gzip compressed while serving. Gzip is efficient in compressing the duplicated strings. In short, don't take the output of mw.loader.inspect literally.",1392695488,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to Amir E. Aharoni from comment #12)
+> (In reply to Bryce Glover from comment #11)
+> > I just added up how many kilobytes the ULS loader's scripts take up once
+> > loaded onto client systems using my Mac's Calculator.app, and it came out to
+> > 450.2 KB!!!  This definitely needs to be fixed!
+> 
+> In which conditions did you make this calculation?
+
+Oops; I should have mentioned that I just used my Mac's built-in Calculator.app application to add up all of the script sizes from the right-hand side of the table provided as an attachment by MZMcBride in Comment #5.  I thought that my source would be obvious!  Now that I think about it, though, where exactly did the results provided by that table come from again?",1392682911,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to Bryce Glover from comment #11)
+> I just added up how many kilobytes the ULS loader's scripts take up once
+> loaded onto client systems using my Mac's Calculator.app
+
+Such comments are not helpful if you do not provide exact steps to reproduce.",1392578194,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to Bryce Glover from comment #11)
+> I just added up how many kilobytes the ULS loader's scripts take up once
+> loaded onto client systems using my Mac's Calculator.app, and it came out to
+> 450.2 KB!!!  This definitely needs to be fixed!
+
+In which conditions did you make this calculation?",1392572510,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to MZMcBride from comment #5)
+> Created attachment 13629 [details]
+> Screenshot of mw.loader.inspect() from the English Wikipedia, 2013-10-30
+
+I just added up how many kilobytes the ULS loader's scripts take up once loaded onto client systems using my Mac's Calculator.app, and it came out to 450.2 KB!!!  This definitely needs to be fixed!
+
+**Attached**: {F12024}",1392569418,PHID-USER-tulrxb4ebie42howqlxj,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"So, as far as we know and until corrected the plan still is, per Erik Moeller, bug 56433 comment 22:
+> OK, then I'd like to request that the language engineering team implement
+> that
+> approach for now, unless there are issues we're overlooking. As noted, we can
+> attach EventLogging to font activation, and we could potentially also run
+> notices or calls-to-action in specific affected wikis. We can figure out in
+> the
+> next couple weeks if we want to prioritize getting back into a default-on
+> state
+> for automatic font delivery for some users/languages quickly, or if this
+> should
+> take a backseat to the language team's other priorities.
+> 
+> But, considering the significant payload added by automatic font delivery, I
+> think that's a reasonable compromise for now. I appreciate the team's efforts
+> to improve ULS performance across the board.
+
+https://gerrit.wikimedia.org/r/#/c/108024/ was already merged and is supposed to serve webfonts only when strictly necessary. So, once the way forward is detected, we need another report for what's needed to complete the plan.",1390339174,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,Removed dependency on bug 56514. It no longer is relevant after gerrit 93035.,1383550424,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to comment #6)
+> (In reply to comment #4)
+> > This isn't a helpful comment.
+> 
+> The way to avoid this is to define when a report can be considered fixed. 
+> ""Make X faster"" is an invalid report as everybody can disagree when it's
+> considered fast enough. Instead, ""Make X load within Y seconds"" has clear
+> criteria.
+
+On what hardware? On what connection? Where, geographically? This is not a clear criterium either, and I'd argue that you can't define a ""clear"" one.",1383156611,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"Lego, Ori, or anyone else who might know: is there a reason that ULS loads anything more than the init script by default? This is what VisualEditor does, as I understand it.",1383156306,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to comment #4)
+> This isn't a helpful comment.
+
+The way to avoid this is to define when a report can be considered fixed. 
+""Make X faster"" is an invalid report as everybody can disagree when it's considered fast enough. Instead, ""Make X load within Y seconds"" has clear criteria.  It's up to requesters to explain and define issues well enough to avoid invalid bug reports, so I disagree with your interpretation.",1383140125,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"Created attachment 13629
+Screenshot of mw.loader.inspect() from the English Wikipedia, 2013-10-30
+
+**Attached**: {F12024}",1383138633,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to comment #3)
+
+This isn't a helpful comment. Please don't leave unhelpful comments.
+
+Nobody is required to justify a bug report's existence to you. If you can't understand the bug, that's a personal problem. Try following the steps laid out in comment 2 (i.e., run mw.loader.inspect() on the English Wikipedia and look at its output).",1383138573,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to comment #2)
+> I'm re-opening this bug with a focus on making ULS more lightweight and
+> acceptably performant.
+
+As it sohuld be possible for bug reports to define when they are fixed: 
+When exactly would ULS be ""lightweight enough"" and ""acceptably performant""? 
+
+Currently I consider this bug report unfixable (and hence INVALID) as requirements are highly subjective and it's impossible to say ""and now ULS is performant and lightweight enough so we can close this bug report"".",1383125871,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"According to mw.loader.inspect(), ULS appears to be by far the largest contributor to JavaScript load on <https://en.wikipedia.org/wiki/Main_Page>:
+
+* jquery.uls
+* jquery.uls.data
+* ext.uls.init
+* ext.uls.webfonts.repository
+* ext.uls.interface
+* ext.uls.languagenames
+* ext.uls.ime
+
+And possibly others. This is all for a feature that most users do not use. This is unacceptably large given that the vast majority of users on the English Wikipedia don't use ULS. This is disproportionate resource usage and is a valid bug to address.
+
+I'm re-opening this bug with a focus on making ULS more lightweight and acceptably performant.",1383053550,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"
+
+*** This bug has been marked as a duplicate of bug 46306 ***",1383031315,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","When editing a category page in VE, the page contents, such as a Subcategories heading and the list of categories in the cat, do not display.  
+
+A requested enhancement would be to display these items using the greyed/lined out display VE uses for other non-editable items.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383010800,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-tqu2xxzwj77ml37wgx66,task_description,resolved
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","Change 290653 merged by jenkins-bot:
+Genericise target initialisation across namespaces
+
+[[https://gerrit.wikimedia.org/r/290653]]",1464277796,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","Change 290653 had a related patch set uploaded (by Esanders):
+Genericise target initialisation across namespaces
+
+[[https://gerrit.wikimedia.org/r/290653]]
+",1464173756,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","Change 171155 had a related patch set uploaded by Alex Monk:
+[WIP] Show non-editable parts of pages in their normal places
+
+https://gerrit.wikimedia.org/r/171155",1415145586,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place",*** Bug 70821 has been marked as a duplicate of this bug. ***,1415046616,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","(In reply to comment #1)
+> This
+
+… also applies to File: pages.",1383011121,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place",This,1383010939,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+VisualEditor: Get rid of ve.ce.Surface.prototype.setContentBranchNodeChanged,"Was introduced as a hack in https://gerrit.wikimedia.org/r/#/c/91786 but we should really find a way to make this unnecessary.
+",1382983860,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ezapkfj5jvedysawagen,task_description,open
+VisualEditor: Hatnote cleanup problem,"User reports:
+There does not seem to be a way to delete the first of two hatnotes without leaving extra space at the top of the article. 28bytes (talk) 03:20, 15 October 2013 (UTC)
+
+Link: https://en.wikipedia.org/w/index.php?title=Maxi_single&diff=577225537&oldid=568995072
+
+User config: Firefox 24.0/Windows 7/Monobook, but the same's true for Safari and for Macs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382954280,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xdltfrkzgw4ix3sbkszo,task_description,resolved
+VisualEditor: Hatnote cleanup problem,"Re-checked: seems that it's not happening  anymore - look at the screenshots {F29287} {F29290}.
+
+Closing as Resolved.",1421687619,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xdltfrkzgw4ix3sbkszo,task_subcomment,NA
+VisualEditor: Hatnote cleanup problem,"Re-checked: seems that it's not happening  anymore - look at the screenshots {F29287} {F29290}.
+
+Closing as Invalid.",1421452520,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xdltfrkzgw4ix3sbkszo,task_subcomment,NA
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference","I think this is a code regression:
+
+The ""Watch this"" checkbox is always checked in Save dialog regardless of the user preference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382820900,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-tswnyxkeiir5xgyyjogc,task_description,resolved
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference","Change 95729 merged by jenkins-bot:
+Move setting of minor/watch defaults from MWSaveDialog to Target
+
+https://gerrit.wikimedia.org/r/95729",1385401101,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tswnyxkeiir5xgyyjogc,task_subcomment,NA
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference",*** Bug 57191 has been marked as a duplicate of this bug. ***,1384843375,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tswnyxkeiir5xgyyjogc,task_subcomment,NA
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference","Change 95729 had a related patch set uploaded by Jforrester:
+Move setting of minor/watch defaults from MWSaveDialog to Target
+
+https://gerrit.wikimedia.org/r/95729",1384768890,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tswnyxkeiir5xgyyjogc,task_subcomment,NA
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference","Probably solved by https://gerrit.wikimedia.org/r/#/c/95729/ ? That fixes a bug where if you had the 'watchcreations' preference set, ""Watch this"" would always be checked.",1384754215,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tswnyxkeiir5xgyyjogc,task_subcomment,NA
+VisualEditor: Refactor CSS so CE doesn't need to position things relative to the UI surface,"I see a lot of code like this:
+
+ve.Element.getRelativePosition( [something], this.getRoot().getSurface().getSurface().$ );
+
+Ideally, CE classes wouldn't need to reach into the UI surface for stuff like this. Positioning against the CE surface should just work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382473500,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5e3qnrqbc3plh3qb6zjr,task_description,open
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Seen in Reference and Transclusion, anywhere with an overlay containing a button saying 'Apply changes'. 
+
+* Hover the cursor over an existing Reference or Transclusion. 
+* Click the icon to invoke the Reference or Transclusion overlay
+* Without making any changes, click 'Apply changes'
+
+* Save page button goes from grey to active.
+
+* Click Save page
+* Click Review your changes. 
+
+Get message ""Could not start the review because your revision matches the latest version of this page.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1382388360,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-owm5ukn67i2uhxyue7qi,task_description,resolved
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","A single patch fixes the majority of the issues here, see the subtasks.",1420510877,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",">>! In T57976#823066, @Krenair wrote:
+> So this is now a tracker?
+
+No, it's a single task made up of sub-tasks.",1417830995,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",So this is now a tracker?,1417830684,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",">>! In T57976#823009, @Krenair wrote:
+> I kind of wish this had been broken into one bug for each dialog.
+
+Done. :-)",1417830313,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",I kind of wish this had been broken into one bug for each dialog.,1417828926,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Change 177944 merged by jenkins-bot:
+Don't re-enable apply changes in reference dialog if the changes have been undone
+
+[[https://gerrit.wikimedia.org/r/177944]]",1417827372,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Change 177944 had a related patch set uploaded (by Alex Monk):
+Don't re-enable apply changes in reference dialog if the changes have been undone
+
+[[https://gerrit.wikimedia.org/r/177944]]
+
+#patch-for-review",1417823506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Change 176861 merged by jenkins-bot:
+Disable Apply Changes in reference dialog until changes have been made
+
+[[https://gerrit.wikimedia.org/r/176861]]",1417819588,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Change 176861 had a related patch set uploaded (by Alex Monk):
+Disable Apply Changes in reference dialog until changes have been made
+
+[[https://gerrit.wikimedia.org/r/176861]]
+
+#patch-for-review",1417483872,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",*** Bug 58231 has been marked as a duplicate of this bug. ***,1416357284,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","No, I think this still applies to the places mentioned in the description (transclusions and references).",1414192705,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","This is not an OOUI bug, moving back to VE. Rather, it's a bug in the individual dialogs in VE that apparently commit no-op transactions when you click Apply changes without changing anything. Also, in most dialogs we disable the Apply changes button when there is nothing to change.
+
+Since this bug was filed in 2013, I imagine it might be mostly fixed now? We have some bugs in this area (filed individually as ""Apply changes is enabled even though XYZ"") but my impression is that generally we're pretty good about this now.",1414118984,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+VisualEditor: Clean up constructor params to dm.Node subclasses,"* dm.LeafNode has (length, element), where length is ignored and forced to 0 by all subclasses except for dm.TextNode
+* dm.BranchNode has (children, element), length is computed while children are added
+
+The code in dm.Document constructing node trees needs to be aware of this, but at the same time it doesn't even use these parameters, because branch nodes are created as childless nodes that have their children added later, and text nodes are created with length zero and have the correct length set later. So we should just get rid of these parameters and make the constructors take a single element parameter, that would get them in line with other dm.Model subclasses (dm.Annotation and dm.MetaItem) as well.
+
+While we're at it, we should also fix the documentation that claims that the element parameter is optional, it really isn't.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382100600,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2thfovp27y2lm7rjxegt,task_description,resolved
+VisualEditor: Clean up constructor params to dm.Node subclasses,https://gerrit.wikimedia.org/r/#/c/135878/,1412590447,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2thfovp27y2lm7rjxegt,task_subcomment,NA
+VisualEditor: Clean up constructor params to dm.Node subclasses,"(In reply to comment #0)
+> While we're at it, we should also fix the documentation that claims that the
+> element parameter is optional, it really isn't.
+
+
+It is in fact optional. The lowest class (ve.dm.Model) has:
+> element || { 'type': this.constructor.static.name }",1382108417,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2thfovp27y2lm7rjxegt,task_subcomment,NA
+Removing stub template removes too many lines,"Intention:  To remove a stub template
+
+
+Expectation:  That the stub template would disappear and everything else (references list, navbox) would remain the same
+
+
+Steps to reproduce:
+
+1)  Go to https://en.wikipedia.org/w/index.php?title=Gastric_volvulus&oldid=567517399 or (probably) any other article that contains these items on separate, adjacent lines:
+
+ * A list of references (in this case, a single bulleted list item)
+ * A blank line
+ * A stub template
+ * A navigation template
+
+2)  Open the article in VisualEditor.
+
+3)  Click on the the stub template to select it.
+
+4)  Press the delete/backspace key (it's same key on a Mac) one time to delete the stub template (and nothing else).
+
+
+Result:
+
+Instead of getting the slightly shorter expected list:
+
+ * A list of references (in this case, a single bulleted list item)
+ * A blank line
+ * A navigation template
+
+this produced a single line containing both the reference list item and the navbox, with no intervening spaces or lines:
+
+ * A list of references (in this case, a single bulleted list item)Navigation template
+
+This broke the navbox formatting for readers.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Gastric_volvulus&diff=577403274&oldid=576282874",1382053680,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-2jrwjzhk56qqi6hbuy6z,task_description,open
+Removing stub template removes too many lines,"Confirmed on Firefox 25/Linux
+
+It seems from very quick experimentation that deleting a template also deletes the preceding line.",1383574643,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-2jrwjzhk56qqi6hbuy6z,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"1. Create a page with two links that point to the same page or URL, and a link that points to a different page/URL
+2. Inspect one of the twin links with the link inspector. The suggestions dropdown is displayed (*)
+3. Inspect the other twin link. The suggestions dropdown isn't displayed
+4. Inspect the third link. The suggestions dropdown is displayed again
+5. Inspect the link from #3. The suggestions dropdown is displayed now
+6. Close the inspector, the inspect the same link again. The suggestions dropdown isn't displayed
+
+This is because the value in the text input doesn't change when you inspect the same link twice or inspect two links with the same target. The link inspector should consistently display the dropdown when it opens.
+
+(*) I would argue that we should /not/ display the dropdown in this case, IMO it's useless and confusing. But the point of this bug is that we should have consistent behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382019060,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fhofyq422q3wz75cdddw,task_description,resolved
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"This is now fixed, but anyway masked by the expedient of not opening the suggestion box until the user changes something.",1402548843,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"Created attachment 13670
+showing wrong suggestions at the end of the previously selected link
+
+**Attached**: {F11975}",1383349835,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"Created attachment 13669
+Showing suggestions in blank space
+
+**Attached**: {F11974}",1383349782,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"Created attachment 13668
+Showing suggestions in blank space
+
+**Attached**: {F11973}",1383349564,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"In step 3, if i click on the link icon from the tool bar instead of pressing ctrl+k or command+k , then the link inspector opens up at the end of the text created in step 1.
+
+See the screenshots for more reference.",1383349480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"Another issue which might be related with this follows the following steps:
+
+1.Create any link with a target URL
+2.Inspect another link of the page with a different target URL
+3.Now point to a blank space and press ctrl+k or command+k
+
+Observed Result:
+
+The link inspector appears in a swipe way from right to left and the content of the link inspector is the suggestion of the link that was created in step 1.
+
+I am not sure how the expected result should be in this case when a user press command+k in an empty space.I think there should not be any pre-set suggestion for that.",1383346779,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"According to https://gerrit.wikimedia.org/r/#/c/54984 , the new wikibugs code (not yet deployed) will split the wikibugs output into a myriad of channels (this is independent from the name of the default channel).
+
+This fragmentation is very annoying because it effectively subtracts important parts of the code/development/discussion from the normal public view on the main channel (whatever its name is) even though they are offtopic, hiding them in some secondary channel.
+The secondary channels should receive additional copies of the relay, but not remove them from the main channel if they are on topic (for instance, the visual editor for MediaWiki obviously is on topic for #mediawiki and #wikimedia-dev).
+ 
+As a fallback, if people really think those products are so unimportant/trashy (""noise"") as to be ignored by people on the main channel, I'd like a single unified feed somewhere, e.g. #mediawiki-feed (it's not clear to me what wm-bot4 [~wm-bot@wikimedia/bot/wm-bot] is doing there exactly).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52529
+https://bugzilla.wikimedia.org/show_bug.cgi?id=10760",1381952940,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-mb365ltelmuwscrj3lep,task_description,declined
+Don't fragment bugzilla conversation/IRC output,Sigh. http://lists.wikimedia.org/pipermail/wikitech-l/2014-May/076522.html,1400568876,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,Now done by pywikibugs.,1398198198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"+1 to all bugs continuing to go to #mediawiki. and all commit output (At least to mediawiki + ext) go to either #mediawiki or #wikimedia-dev
+
+Having bug output in these channels helps bring new contributors in, and allows them to see what is being worked on. Moving it to #mediawiki-feed would destroy this.",1393012958,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"Yeah, wikibugs-l is a global watcher, and wikibugs bot just relays all mail that is sent there. So *everything* goes to #mediawiki, apart from security bugs.",1381956514,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"(In reply to comment #4)
+> This bug is not about ""all the feeds"": pywikibot is already on another
+> channel,
+> because it's not sent to wikibugs-l.
+
+Actually Pywikibot bugs show up in #mediawiki, and I wrote a python script which copies the output of wikibugs into #pywikipediabot if it's one of our bugs.",1381954492,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"(In reply to comment #3)
+> (In reply to comment #2)
+> > The conversation
+> 
+> Where is this conversation happening? I have opinions but I'd rather read
+> first
+> what has been discussed.
+
+I mean the development conversation.
+
+(In reply to comment #2)
+> The conversation is currently fragmented between #mediawiki (wikibugs) and
+> #wikimedia-dev (grrit-wm).
+
+That's another bug.
+
+> 
+> grrit-wm can also post to other channels on demand, such as #-operations and
+> #-visualeditor, which is a very useful feature (both of these are completely
+> useless in #mediawiki and only tangenially related in #wikimedia-dev).
+
+This is also another issue, and only in part overlapping this (gerrit changes are apparently considered more ""noisy"", otherwise they wouldn't have been moved first).
+
+> 
+> A separate channel that would *mirror* all other feeds would be okay, but a
+> *separate* one.
+
+This bug is not about ""all the feeds"": pywikibot is already on another channel, because it's not sent to wikibugs-l.",1381954287,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"(In reply to comment #2)
+> The conversation
+
+Where is this conversation happening? I have opinions but I'd rather read first what has been discussed.",1381953572,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"The conversation is currently fragmented between #mediawiki (wikibugs) and #wikimedia-dev (grrit-wm).
+
+grrit-wm can also post to other channels on demand, such as #-operations and #-visualeditor, which is a very useful feature (both of these are completely useless in #mediawiki and only tangenially related in #wikimedia-dev).
+
+A separate channel that would *mirror* all other feeds would be okay, but a *separate* one.",1381953308,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,+1 to having it in #mediawiki-feed so people who want the full force of the firehose can have it.,1381953079,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+VisualEditor: Support the Command+Delete keyboard command on Mac (delete current line) and others,"On Chrome Version 30.0.1599.69 on Mac OSX 10.8.5 the Command+Delete keyboard shortcut is ignored. In most text editors it deletes the entire line of content (try it in gmail or on bugzilla!)
+
+The Option+Delete keyboard key (to delete the previous word) and Option+Fn+Delete (to delete the following word) do work correctly. There is no Command+Fn+Delete shortcut.
+
+I do not have easy access to test this shortcut on other versions of Chrome, nor do I know what the shortcut is on Firefox.",1381942500,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-k4x357kadd74krhi4jsl,task_description,resolved
+VisualEditor: Support the Command+Delete keyboard command on Mac (delete current line) and others,Command + Delete works for me in Chrome 43 and Firefox 40 on OS X 10.10.3. Tentatively closing.,1434667851,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-k4x357kadd74krhi4jsl,task_subcomment,NA
+VisualEditor: Highlights triggered while resizing aren't moved correctly,"While resizing an image with live preview, the highlight on the image is updated correctly. But if you mouse over another image while resizing, then that image's highlight isn't updated for the resize. This is a problem in situations where resizing the first image moves the second image, in that case the highlight stays where it was when you first entered the image.
+
+Maybe we just shouldn't show highlights at all while dragging?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55789",1381926000,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-du4fblehtatuv452azlx,task_description,resolved
+VisualEditor: Highlights triggered while resizing aren't moved correctly,"Agreed, I think we did back in January.",1400696049,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-du4fblehtatuv452azlx,task_subcomment,NA
+VisualEditor: Highlights triggered while resizing aren't moved correctly,I think we fixed this ages ago.,1400695667,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-du4fblehtatuv452azlx,task_subcomment,NA
+VisualEditor: Move floating functionality from SurfaceToolbar to Toolbar?,"The floating code is in ve.ui.SurfaceToolbar instead of OO.ui.Toolbar, but cursory inspection of the code indicates that it doesn't reach into the surface and doesn't receive any events from the surface, apart from a minor bit that ensures the cursor isn't obscured by the toolbar.
+
+Wanting to float a toolbar seems generic enough, so couldn't this be made into generic OO.ui functionality?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381921260,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ooymibfombnrpq5ugplm,task_description,open
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""","Intention:  To create a block of text to check line wrapping.
+
+
+Expectation:  That I'd end up with a block of plain paragraph-formatted text.
+
+
+Steps to reproduce:
+
+1)  Start with a page containing some text and a few section headings.  In my case, it was a list.  
+
+2)  Select all the text in one section using arrow/cursor keys, including all of the last line (including the blank part at the end of the paragraph), but none of the section heading that follows.
+
+4)  Copy this.
+
+5)  Make a new, blank paragraph-formatted line.
+
+6)  Paste the copied text into the new line.
+
+
+Results:  You get the desired paragraph, followed by a == <nowiki /> == section heading.
+
+See https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=577354576&oldid=577352415
+
+(For bonus points, if you skip step #5, you'll get your pasted text set to ==Section heading== formatting.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T52100}
+{T61647}",1381881120,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_description,resolved
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""","Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output <p> instead of <h#>
+
+[[https://gerrit.wikimedia.org/r/162310]]",1426893388,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_subcomment,NA
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""","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",1424197333,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_subcomment,NA
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""","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",1411496979,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_subcomment,NA
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""",This may be related to bug 49452 and/or bug 50100,1381881210,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_subcomment,NA
+Multiline list items rendering differently in ContentEditable than the resulting wikitext,"This is an interesting issue that, as far as I understand, can be either (or both) VE and Parsoid, and seems to be limited by wikitext. 
+
+I'm not entirely sure what the strategy here should be -- If the final article markup is ""the way things are supposed to be"" then the fix should be to correct the way things look to the user in ContentEditable so they match the final article display. 
+
+However, there might be a creative way to manipulate the wikitext in Parsoid (or the html VE sends to Parsoid) so that the end result fits what VisualEditor presents.
+
+The first solution will disallow multiline list items. The second solution would run the risk of having html tags in wikitext, or worse, having the dreaded dirty diffs if the desired multiline list item is more complex.
+
+Here's how to see the issue:
+(Refer to this image: http://mg.viewskew.com/mgoblin_media/media_entries/432/ve_listbug.png )
+
+1. Edit some wiki page (can be empty/new)
+2. Type 3-4 lines
+3. Mark the lines and make them a list with the list button
+4. Go to the second element (or whatever one that is in the middle of the list)
+5. Go to the end of that listItem's line, and hit ""Shift-Enter""
+6. In VisualEditor, the behavior is similar to other word processors with multiline list element -- you get a second line that is indented the same as the list item you're under.
+7. Type something so you have text on that multiline segment. (#1 in the image) 
+8. Click 'save' and review changes; wikitext is not representing what we see on the screen (see #2 in the image)
+9. Save the article -- the article presents a different format than what VE showed (#3 in the image) and presents a different content to edit if we want to edit that article again (#4 in the image)
+
+The way I see it (and I may well be wrong, as I'm not that familiar with wikitext) -- we can either fix this bug so VE presents the same display as the final article (as in, disallow shift-enter in lists) or we need to split multiline items into paragraphs that can render as such into wikitext (not sure if that's possible) -- the other alternative is to force a <br /> on multiline lists, which would make the wikitext into something like
+
+* item 1
+* item 2
+* item 3<br />and its multiline
+* item 4
+
+And that works perfectly in the article and in edit mode -- but it can be limited in what can be done inside a multiline list item, and requires the use of <br /> tag inside the wikitext. 
+
+Also, there may be more cases of complex list items with VE's expanding features. For instance, there can be cases where a multiline list item should contain a certain language block, or a short code highlight segment, or a <math> block. Right now they render proplery in CE if added as multiline list item, but break the list and become separate paragraph items on save.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381854300,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-dpieimh3wxp5zjcp2w6f,task_description,duplicate
+Multiline list items rendering differently in ContentEditable than the resulting wikitext,"Duplicate of T110986. This one is older, but the other has more discussion on it (sorry @Mooeypoo)",1701961617,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dpieimh3wxp5zjcp2w6f,task_subcomment,NA
+Multiline list items rendering differently in ContentEditable than the resulting wikitext,">>! In T57746#968491, @matmarex wrote:
+> The link to the image is dead now. Is this the same issue as T70800?
+
+According to the reproduction steps, this seems rather the same issue as T110986.
+
+I’m not sure about set child task.",1636496570,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-dpieimh3wxp5zjcp2w6f,task_subcomment,NA
+Multiline list items rendering differently in ContentEditable than the resulting wikitext,The link to the image is dead now. Is this the same issue as T70800?,1420909208,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dpieimh3wxp5zjcp2w6f,task_subcomment,NA
+VisualEditor: Wrong link rendered in edit mode when you click link in drop-down,"To reproduce:
+
+1. Goto https://en.wikipedia.org/w/index.php?title=Lancaster,_Pennsylvania&oldid=576777823&veaction=edit
+3. Highlight 'Brownfields'
+4. Press Ctrl-K
+5. Type 'brownfield land' as target.
+6. Click matching entry in drop-down once to accept.
+7. Click on unrelated text to hide the link widget.
+
+The internal representation is correct (as shown in e.g. 'Review your changes'), but the displayed/rendered link goes to https://en.wikipedia.org/w/Brownfields , not the correct target.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381813980,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-2iussc7hskb3wyvivj3j,task_description,resolved
+VisualEditor: Wrong link rendered in edit mode when you click link in drop-down,"This was fixed by Ed's re-working of these recently, I think.",1402549905,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2iussc7hskb3wyvivj3j,task_subcomment,NA
+VisualEditor: Fetch new image rendering after resize,"To prevent images which have just been scaled up from looking pixelated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381761840,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yhklbztfy4qioy5s3nw3,task_description,resolved
+VisualEditor: Fetch new image rendering after resize,"Change 89809 merged by jenkins-bot:
+Re-render images after resize
+
+https://gerrit.wikimedia.org/r/89809",1381961020,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yhklbztfy4qioy5s3nw3,task_subcomment,NA
+VisualEditor: Fetch new image rendering after resize,"Change 89809 had a related patch set uploaded by Esanders:
+Re-render images after resize.
+
+https://gerrit.wikimedia.org/r/89809",1381839582,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yhklbztfy4qioy5s3nw3,task_subcomment,NA
+Add mediawiki.ui dialogs,"mediawiki.ui should have dialogs/modals.  The new dialogs in GettingStarted can be used as a starting point, but more work is needed.  This includes choosing the right level of abstraction, and how to implement them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381359000,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_description,declined
+Add mediawiki.ui dialogs,"The mediawiki-ui styles in core are still maintained a little while longer, but dialogs seems like quite a significant task to take on. Engineering effort that is probably better invested elsewhere.
+
+Closing for now, though patches welcome if someone can volunteer reviewing it.",1426301201,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,">>! In T57534#943582, @Spage wrote:
+> OOUI's dialogs with the mediawiki.ui skin are probably a viable alternative.
+
+Yeah.  If there is a general consensus to move to OOJS-UI, this is probably a WONTFIX.",1421193543,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"Matt originally wrote:
+> The new dialogs in GettingStarted can be used as a starting point, but more work is needed
+
+Flow has implemented a general-purpose `mw.Modal` in [[ https://github.com/wikimedia/mediawiki-extensions-Flow/blob/master/modules/engine/misc/mw-ui.modal.js | mw.ui.modal.js]], see  Shahyar's e-mail to the design list in October ""MW UI Modals First Version & Concept"" ([[https://lists.wikimedia.org/pipermail/design/2014-October/002183.html | in ASCII]], but much easier to read the original HTML). There are a lot of features in Flow's modal tailored to [[ https://trello.com/c/uAoYLKf1/3-multi-step-modal-dialog | the design spec in Trello ]]. It use OOjs' EventEmitter.
+
+OOUI's dialogs with the mediawiki.ui skin are probably a viable alternative.
+",1419880579,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"Matt originally wrote:
+> The new dialogs in GettingStarted can be used as a starting point, but more work is needed
+
+Flow has implemented a general-purpose `mw.Modal` in
+[[ https://github.com/wikimedia/mediawiki-extensions-Flow/blob/master/modules/engine/misc/mw-ui.modal.js | mw.ui.modal.js]], see  Shahyar's e-mail to the design list in October ""MW UI Modals First Version & Concept"" ([[https://lists.wikimedia.org/pipermail/design/2014-October/002183.html | in ASCII]], but much easier to read the original HTML) There are a lot of features in Flow's modal tailored to [[ https://trello.com/c/uAoYLKf1/3-multi-step-modal-dialog | the design spec in Trello ]]. It use OOjs' EventEmitter.
+
+OOUI's dialogs with the mediawiki.ui skin are probably a viable alternative.
+",1419481997,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #8)
+> As for centring, the iframes don't particularly help there but I do know that
+> in VE we have a satisfying way of centring the dialog
+> vertically/horizontally.
+> 
+> The centring of dialogs is generally a solved problem in web development
+> afaik.
+> There's different ways to go about it, but there's at least 1 commonly used
+> way that works.
+
+I have a working solution, but it doesn't work in IE 6 or 7 (bug 55487).  If you have a recommendation, I'd be glad to look at it.
+
+> On the subject, oo.ui dialogs do have an interesting aspect that is worth
+> mentioning. They don't require a fixed width/height. CSS min-height /
+> max-height is dynamically honoured (it can shrink/grow, and overflow:auto
+> will show scrollbars if needed), and browser resizing as well.
+
+Unfortunately, that's an example of a compatibility issue which we're going to have to grapple with.  IE6 apparently can't support both min-height and max-height on the same element (http://stackoverflow.com/questions/1467664/how-to-implement-cross-browser-min-height-and-max-height-at-the-same-time)
+
+> As for the CSS, that's going to be the area that'll need most manual testing
+> and fixing. I think most browser bugs we account for date back pretty far (we
+> tend to IE8, Opera 12 and recent Firefox/Chrome).
+> 
+> Though IE6, IE7 and Firefox 4 (which would be the main browsers missing
+> between
+> VE requirements and MW requirements) do have a ton of specific quirks, afaik
+> those are all bugs that can be worked around, not actual missing CSS features
+> that would be blockers (aside from CSS3 enhancements, which will be absent
+> but
+> those degrade gracefully).
+
+Yeah, I primarily meant CSS and rendering.  I agree some have relatively simple workarounds.  However, others are a bit more complicated.",1381366742,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #7)
+> (In reply to comment #6)
+> > (In reply to comment #4)
+> > oo.ui is about two years ahead of mw.ui in development time, but we built
+> > things as we needed them in VisualEditor so there might be certain kinds of
+> > widgets that mw.ui has that aren't in oo.ui yet. Things like dialog support,
+> > though, have existed in oo.ui for a long time. oo.ui also fully supports
+> > running all of its widgets in iframes (which is how dialogs are done as
+> > well).
+> 
+> I don't really know much about the advantages of iframes for this kind of
+> thing.  However, I did have some issues (e.g. full horizontal and modal
+> centering), so if it solves that, that would be nice.
+
+
+iframes are mostly to allow text selection, focus and other complicated and cross-browser unstable states to remain while the dialog is up.
+
+As for centring, the iframes don't particularly help there but I do know that in VE we have a satisfying way of centring the dialog vertically/horizontally.
+
+The centring of dialogs is generally a solved problem in web development afaik. There's different ways to go about it, but there's at least 1 commonly used way that works.
+
+On the subject, oo.ui dialogs do have an interesting aspect that is worth mentioning. They don't require a fixed width/height. CSS min-height / max-height is dynamically honoured (it can shrink/grow, and overflow:auto will show scrollbars if needed), and browser resizing as well.
+
+(In reply to comment #7)
+> 
+> We'll be supporting more browsers than VE does, so oo.ui will need to do the
+> same if we take that approach.
+
+As far as javascript code itself, we currently require the browser to support most ES5 features (IE8 is missing some ES5 features, but we haven't needed those yet, and we keep an eye out for those with feature tests).
+
+At this point we only use ES5 features that have established polyfills (Array#filter, Function#bind, Object#create, String#trim, JSON.stringify etc., full list at[1]). We don't polyfill them right now because we don't have to, but we can easily bring in an es5shim if we have to.
+
+As for the CSS, that's going to be the area that'll need most manual testing and fixing. I think most browser bugs we account for date back pretty far (we tend to IE8, Opera 12 and recent Firefox/Chrome).
+
+Though IE6, IE7 and Firefox 4 (which would be the main browsers missing between VE requirements and MW requirements) do have a ton of specific quirks, afaik those are all bugs that can be worked around, not actual missing CSS features that would be blockers (aside from CSS3 enhancements, which will be absent but those degrade gracefully).
+
+
+[1] https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/4da68b71d11f15b10e2e1f418025b438954e7da5/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js#L68-L85",1381363772,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #6)
+> (In reply to comment #4)
+> > Are you planning to put oo.ui in core?  If so, are you going to merge it with
+> > mediawiki.ui?
+> oo.ui is going to be a standalone library, but we're planning for MW core to
+> depend on it and bundle it, same as with e.g. jQuery.
+
+Makes sense.
+
+> I personally would like to make mw.ui an extension of oo.ui, making
+> MW-specific things in mw.ui extensions of generic things in oo.ui, and moving 
+> any generic functionality from mw.ui into oo.ui if oo.ui doesn't already have 
+> it.
+
+That seems reasonable, though it might take some practice drawing that line.
+
+> oo.ui is about two years ahead of mw.ui in development time, but we built
+> things as we needed them in VisualEditor so there might be certain kinds of
+> widgets that mw.ui has that aren't in oo.ui yet. Things like dialog support,
+> though, have existed in oo.ui for a long time. oo.ui also fully supports
+> running all of its widgets in iframes (which is how dialogs are done as
+> well).
+
+I don't really know much about the advantages of iframes for this kind of thing.  However, I did have some issues (e.g. full horizontal and modal centering), so if it solves that, that would be nice.
+
+We'll be supporting more browsers than VE does, so oo.ui will need to do the same if we take that approach.",1381361993,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #4)
+> Are you planning to put oo.ui in core?  If so, are you going to merge it with
+> mediawiki.ui?
+oo.ui is going to be a standalone library, but we're planning for MW core to depend on it and bundle it, same as with e.g. jQuery.
+
+I personally would like to make mw.ui an extension of oo.ui, making MW-specific things in mw.ui extensions of generic things in oo.ui, and moving any generic functionality from mw.ui into oo.ui if oo.ui doesn't already have it.
+
+oo.ui is about two years ahead of mw.ui in development time, but we built things as we needed them in VisualEditor so there might be certain kinds of widgets that mw.ui has that aren't in oo.ui yet. Things like dialog support, though, have existed in oo.ui for a long time. oo.ui also fully supports running all of its widgets in iframes (which is how dialogs are done as well).",1381360769,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"Created attachment 13462
+Modal from GettingStarted
+
+This shows an example modal from GettingStarted.  This appearance is not necessarily exactly how the core version would look.
+
+**Attached**: {F12155}",1381359724,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"Are you planning to put oo.ui in core?  If so, are you going to merge it with mediawiki.ui?",1381359603,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #1)
+> Trevor and Roan mentioned that they may be trying to make ve.ui (aka oo.ui)
+> dialogs available to non-VisualEditor products and wikis. Those may be
+> appropriate to use/adapt for our purposes, we just need to compare it all.
+A WIP for that was just put in Gerrit: https://gerrit.wikimedia.org/r/#/c/88896/",1381359434,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"This should include the grey overlay as well.  Ideally, this dialog code will be general enough that GuidedTour can be ported to use it as well.",1381359407,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"**swalling** wrote:
+
+For reference, the dialogs being used in the currently-released GettingStarted A/B test are in Extension:GettingStarted's resources. 
+
+Trevor and Roan mentioned that they may be trying to make ve.ui (aka oo.ui) dialogs available to non-VisualEditor products and wikis. Those may be appropriate to use/adapt for our purposes, we just need to compare it all.",1381359330,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+VisualEditor: MWSyntaxHighlight* is badly broken,"ve.dm.MWSyntaxHighlightNode.static.toDataElements:
+* Assumes it always receives two DOM elements, one div and one span. This is dependent on an interaction issue between Parsoid and MediaWiki, and isn't always the case.
+* Stores the span and the div as two separate attributes, rather than a single domElements attribute containing an array
+* Stores the span and the div by reference rather than cloning them
+
+ve.dm.MWSyntaxHighlightNode.static.toDomElements:
+* Assumes attributes.span is always set, although per the above it may be undefined. In case it is undefined, this function returns [<div>, undefined] which ends up crashing VE with a DOM error (""DOM Exception 8"") because undefined is fed to appendChild() by the converter
+* Uses attributes.div and attributes.span by reference. This is bad because:
+** calling .appendChild() on a node that's already attached elsewhere removes it from its old location
+** the original nodes received by toDataElements() are in a different document than the output of this function is supposed to be, so we end up attaching nodes to the wrong document
+** the correct way to do this is ve.copyDomElements( originalDomElements, doc ) where doc is the second parameter
+* Unconditionally sets the data-mw attribute, without checking if anything actually changed. This should be avoided, because reordering of keys in the JSON blob may dirty the DOM and trigger a corruption warning. See the last bit of ve.dm.MWReferenceNode.static.toDomElements (dealing with originalMw) for an example of how to do this correctly
+** Note that this .setAttribute() call is once again modifying the original <div> by reference
+* Assumes attributes.div is always set, which won't be true for newly created MWSyntaxHighlightNodes that didn't come from Parsoid but were created by the user in VE. For such nodes, the .setAttribute() call will crash the editor. But we never get there because ...
+
+ve.ui.MWSyntaxHighlightDialog.prototype.onOpen:
+* Assumes that there's always a FocusedNode when the dialog opens. However, this isn't true in creation mode (i.e. when opening the dialog from the toolbar without selecting an existing node), and so opening the dialog in creation mode crashes the editor when trying to do this.sourceNode.getModel(). This means it's impossible to create new MWSyntaxHighlightNodes with VE
+* Note that there's also no if ( this.sourceNode instanceof ve.dm.MWSyntaxHighlightNode ) check, which means this dialog will attempt to edit other types of nodes if it's opened while such a node is focused
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381358700,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_description,open
+VisualEditor: MWSyntaxHighlight* is badly broken,"Another bug discovered:
+
+On every click in the edit area in the dialog, an error appears in the console:
+
+TypeError: e.innerText is undefined
+parseInt(e.getAttribute('idx'),10) + e.innerText.length > model);
+
+in VisualEditor/modules/syntaxhighlight/ve.ui.MWSyntaxHighlightSimpleSurface.js
+line #1252",1383947447,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_subcomment,NA
+VisualEditor: MWSyntaxHighlight* is badly broken,"Patch to disable SyntaxHighlight is now merged, so this problem will be suppressed with the production push tomorrow morning; restoring to ""ASSIGNED"".",1381370918,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_subcomment,NA
+VisualEditor: MWSyntaxHighlight* is badly broken,"Change 88901 merged by jenkins-bot:
+Remove SyntaxHighlight from the experimental set
+
+https://gerrit.wikimedia.org/r/88901",1381361798,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_subcomment,NA
+VisualEditor: MWSyntaxHighlight* is badly broken,"Change 88901 had a related patch set uploaded by Catrope:
+Remove SyntaxHighlight from the experimental set
+
+https://gerrit.wikimedia.org/r/88901",1381361403,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_subcomment,NA
+"Enforce proper nesting of most templates, and encapsulate compound content blocks","Transclusions can currently affect arbitrary parts of the page by producing unbalanced HTML. This makes both WYSIWYG editing and efficient updates difficult. We would thus like to move towards properly nested templates as much as possible. For existing multi-transclusion content we would like to enforce nesting as a unit, possibly using a <domparse> extension-like tag wrapping such a content block. This would still let us reuse expansions for multi-template content, which is important for large list pages like http://fr.wikipedia.org/wiki/Liste_des_premiers_pr%C3%A9fets_fran%C3%A7ais_(1800-1815).
+
+The solution should:
+* work with old and new revisions, with predictable HTML diff behavior
+* support multi-transclusion/extension content reuse
+* support a mix of transclusions, extension tags and page content
+* work well with the VisualEditor preview
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381345200,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-oelrynugtph5rjeyq7u4,task_description,duplicate
+"Enforce proper nesting of most templates, and encapsulate compound content blocks",I am just going to merge this into the Balanced Templates RFC since that captures most of the requirement here. The compound content block issues would be partially ameliorated by using heredoc syntax in some cases.,1582154907,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-oelrynugtph5rjeyq7u4,task_subcomment,NA
+"Enforce proper nesting of most templates, and encapsulate compound content blocks","Lowering the priority a bit, as other issues are more pressing currently.",1386109375,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-oelrynugtph5rjeyq7u4,task_subcomment,NA
+"Enforce proper nesting of most templates, and encapsulate compound content blocks",This is roadmap item https://www.mediawiki.org/wiki/Parsoid/Roadmap#Research_.2F_prototype:_Enforce_proper_nesting_of_most_templates.2C_and_encapsulate_compound_content_blocks_.5Bhard.2C_Q3-Q4_2013.5D,1381345264,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-oelrynugtph5rjeyq7u4,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","From https://integration.wikimedia.org/ci/job/mwext-cldr-phpcs-strict/1/console:
+
+11:21:52 FILE: ...nkins-slave/workspace/mwext-cldr-phpcs-strict/CldrNames/CldrNamesMy.php
+11:21:52  643 | ERROR   | Line exceeds maximum limit of 120 characters; contains 162
+11:21:52  648 | WARNING | Line exceeds 100 characters; contains 109 characters
+
+These are the lines in question:
+
+	'UM' => 'ယူနိုက်တက်စတိတ် အပြင်ထွက် နေသည့် သေးငယ်သောကျွန်းများ',
+	'VC' => 'စိန့်ဗင့်ဆင့်နှင့် သည်ဂရဲနာဒင်းစ်',
+
+Assuming tab width is 4, the line lengths are 67 and 48 respectively.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: minor",1381318620,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-igmisx4akeh5yixglyfo,task_description,resolved
+"PHP CodeSniffer reports line length based on bytes, not on characters","I have retriggered the original build:
+
+https://integration.wikimedia.org/ci/job/mwext-cldr-phpcs-strict/4/console
+
+The phpcs command being run is:
+
+
+ phpcs -v -s . --encoding=utf-8 \
+  --standard=/var/lib/jenkins/tools/mwcodesniffer/MediaWiki \
+  --extensions=php,php5,inc,sample \
+  '--ignore=languages/messages/Messages,*.i18n.php,*.i18n.alias.php' \
+  --report-checkstyle=checkstyle-phpcs.xml \
+  --report-full
+
+And the result is a SUCCESS.  So the fix was indeed to pass '--encoding=utf-8' to phpcs :-]",1382434399,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","All jobs got refreshed. That should fix the issue now, if that is actually the case I guess we can close the bug report.",1381396600,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","(In reply to comment #5)
+> Have the jobs been pushed? The change is merged but in
+> https://integration.wikimedia.org/ci/job/mwext-VisualEditor-phpcs-HEAD/1524/
+> console
+> I don't see --encoding being passed.
+
+Good catch Timo. Something went wrong when I refreshed the jobs :(
+
+Refreshing them:
+
+
+$ grep 'encoding=utf' /var/lib/jenkins/jobs/*phpcs*/config.xml
+/var/lib/jenkins/jobs/mwext-AbuseFilter-phpcs-HEAD/config.xml: --encoding=utf-8 \
+/var/lib/jenkins/jobs/mwext-ActiveAbstract-phpcs-HEAD/config.xml: --encoding=ut-8 \
+/var/lib/jenkins/jobs/mwext-AdminLinks-phpcs-HEAD/config.xml: --encoding=utf-8 \",1381395346,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters",Have the jobs been pushed? The change is merged but in https://integration.wikimedia.org/ci/job/mwext-VisualEditor-phpcs-HEAD/1524/console I don't see --encoding being passed.,1381343238,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","Change 88743 merged by jenkins-bot:
+Specify encoding of source files as utf-8
+
+https://gerrit.wikimedia.org/r/88743",1381329601,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","Change 88743 had a related patch set uploaded by Siebrand:
+Specify encoding of source files as utf-8
+
+https://gerrit.wikimedia.org/r/88743",1381328452,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","Our PHP files should be UTF-8 encoded, so we should run CodeSniffer in that mode. I'll see if I can submit a patch...",1381326992,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","phpcs defaults to iso-8859-1 defined in PHP_CODESNIFFER_ENCODING
+
+CodeSniffer/Standards/Generic/Sniffs/Files/LineLengthSniff.php uses strlen(), whenever the encoding is not iso-8859-1 it would use:
+
+  iconv_strlen($lineContent, PHP_CODESNIFFER_ENCODING);
+
+So need to pass:
+
+ --encoding=UTF-8",1381320099,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Right now jQuery.IME is horrendously, horribly broken when using VisualEditor (a quick perusal of bugs that make it unusable include bug 54421, bug 53700, bug 53701, bug 53705, bug 53706, bug 53711, bug 54283, bug 54331, bug 54334 and others).
+
+Having the jQuery.IME icon show up when it is actively broken makes a promise to the user that we can't possibly hope to meet right now.
+
+Please disable jquery.IME from VisualEditor surfaces entirely until we can get some proper testing and work done.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1381280040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4x34z4rnugcat2zdme3x,task_description,resolved
+Disable jquery.IME operating on VisualEditor surfaces,"> We will probably just ride the train on
+> Thursday rather than introduce an out-of-sequence deployment if that's OK.
+
+Preferred.",1381329931,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"(In reply to comment #5)
+> Patch merged. I think you can deploy HEAD of master of ULS whenever it's
+> convenient for you guys, James. There have been no functional changes but
+> this one in the past week.
+
+Thank you, Siebrand and Santhosh. We will probably just ride the train on Thursday rather than introduce an out-of-sequence deployment if that's OK.",1381329712,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Patch merged. I think you can deploy HEAD of master of ULS whenever it's convenient for you guys, James. There have been no functional changes but this one in the past week.",1381329332,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Change 88727 merged by jenkins-bot:
+Disable jquery.ime for VE till IME support is improved
+
+https://gerrit.wikimedia.org/r/88727",1381329205,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Change 88727 had a related patch set uploaded by Santhosh:
+Disable jquery.ime for VE till IME support is improved
+
+https://gerrit.wikimedia.org/r/88727",1381325894,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Just to be clear, VE and jQuery.IME are making incompatible assumptions about the javascript event sequences expected when entering text in an IME.
+
+To be fair, that's not really anyone's fault because (a) de jure, the standards are still emerging, and (b) de facto, every single browser/OS/IME combination seems to generate a different weird and wonderful sequence of events.
+
+We're currently refactoring the VE CE Surface code to make as few assumptions as possible about IME events. I expect we can do work from the jQuery.IME side too, to bring the two into line.",1381306572,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Not sure I like the framing. VE mangles IME input horribly and horrendously, not the other way around may be more accurate.
+
+We can disable jQuery.IME in content editable divs of VisualEditor because it cannot handle input methods. Which class identifies editable divs of VisualEditor?",1381303119,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+VisualEditor: DM's list of the page's categories can be invalidated by e.g. adding a template that inherits a category,"When adding a template that also adds a category, after saving the list of categories is not updated until the page is reloaded.
+
+To reproduce:
+
+1. Load any page in VE
+2. Add any template that also adds a category, e.g. {{user en}}
+3. Save page
+
+Expected behaviour: The list of categories includes the newly added category, e.g. [[Category:User en-N]]
+Actual behaviour: The list of categories is not updated.
+
+It doesn't seem to matter whether the category is plain or hidden.
+
+Firefox 24 on Linux using Monobook skin
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1381104060,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gc3mafjeizbrumfuxqil,task_description,open
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"With wikitext editing, people work around this by writing long articles in word, or relying on browsers remembering form data if it crashes.
+
+Perhaps with local storage we can take periodic snapshots of DM HTML, or even the entire surface state (DM data, IV store, internal list, transaction history etc.) and offer to restore it if the changes went unsaved.
+
+See also:
+* T39992 - Review and deploy Drafts extension to Wikimedia wikis
+* T75241 - Auto-save to increase chances of lost edits recovery",1381073520,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_description,resolved
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4047400, @Kaartic wrote:
+> Nice point, but ... only if the user actually does know that there is a feature known as ""autosave"" and it recovers their edits"" **silently** in some cases. What I'm trying to say is, this might become a //misfeature// if there are possibilities that we might recover the edits it when we shouldn't have AND we don't let the user know that we recover edits silently!
+> 
+> I guess we should at least show a fade away notice when we recover the edits thus letting the user know about the feature.
+
+Sorry, when I said ""silently"" I meant without a modal dialog. We will always show at least the notification when edits are recovered. This is an improvement on the current wikitext editor where the browser can automatically recover the state of the textarea without telling the user.
+
+",1521479444,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,@Deskana ah good.  I posted the info here when I couldn't find any mention or task of the 'switching editors' issue. Should the new task be added to the Related Objects task graph?,1521041012,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4048147, @Alsee wrote:
+> Report from [[ https://www.mediawiki.org/wiki/Topic:U9ad8eelljphdgao | VisualEditor/Feedback ]]:
+> //Whenever I switch from VE to the source editor, and then switch back to VE, it literally deletes the changes I made with the source editor, and then it gives me a ridiculous message saying the following://
+> //""Changes recovered Your unsaved changes have been automatically recovered.""//
+> //Well, thanks, but how do I get rid of this? Now I can't use VE properly anymore.//
+
+T189381.",1521039768,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Aklapper are you kidding? This is clearly a serious bug in the new code, and it **directly** relates to the discussion in the previous dozen comments.",1521038715,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Alsee: Support questions are handled on https://www.mediawiki.org/wiki/VisualEditor/Feedback , not here.",1521027190,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Report from [[ https://www.mediawiki.org/wiki/Topic:U9ad8eelljphdgao | VisualEditor/Feedback ]]:
+//Whenever I switch from VE to the source editor, and then switch back to VE, it literally deletes the changes I made with the source editor, and then it gives me a ridiculous message saying the following://
+//""Changes recovered Your unsaved changes have been automatically recovered.""//
+//Well, thanks, but how do I get rid of this? Now I can't use VE properly anymore.//",1520978923,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4046224, @Esanders wrote:
+> In the common case where the document IDs do match we continue to recover silently, ...
+
+Nice point, but ... only if the user actually does know that there is a feature known as ""autosave"" and it recovers their edits"" **silently** in some cases. What I'm trying to say is, this might become a //misfeature// if there are possibilities that we might recover the edits it when we shouldn't have AND we don't let the user know that we recover edits silently!
+
+I guess we should at least show a fade away notice when we recover the edits thus letting the user know about the feature.",1520963133,PHID-USER-yjl5dukrpd7aq6u3c4h4,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4046224, @Esanders wrote:
+> Perhaps a middle ground would be to prompt the user only if the document IDs don't match. In the common case where the document IDs do match we continue to recover silently, and if the user wants to undo they can press undo (as history is preserved),
+
+This seems like a good idea to me.",1520948641,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Note that one of the use cases for this is for when mobile devices automatically unload background tabs, so having the editor prompt you to recover every time you switch tabs could be annoying.
+
+Perhaps a middle ground would be to prompt the user only if the document IDs don't match. In the common case where the document IDs do match we continue to recover silently, and if the user wants to undo they can press undo (as history is preserved),",1520941633,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"An edit is considered intentionally abandoned if you click 'Read' or 'Article' (T189380 not yet deployed). If you close the tab, reload or navigate away in any other way we have no opportunity to delete. It would not be correct to only recover if the version IDs match, as on popular articles that will happen all the time. We should expect core's merge/conflict code to handle that in the same way it would if you just had the tab open for a long time.
+
+Given that people are getting confused about when they have actually ""abandoned"" their edit, we may want to ask the user.",1520940579,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I filed {T189576}
+
+In the mean time, my testing unearthed two workarounds you can use so that your edits are not ""recovered"" when they shouldn't be:
+# Close the tab you were using, and edit the same page in a new tab.
+# Click ""Read"" to close the editor.",1520940504,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4044693, @kaldari wrote:
+> @Deskana: Do you think we should make a follow-up task to implement James's UI to deal with TheDJs issue (T57370#4037827)?
+
+I'd prefer the software do the right thing (i.e. not ""recovering"" edits that were intentionally abandoned) rather than shifting the burden of the decision onto the user. If that's not possible for whatever technical reason, asking the user would be an acceptable backup option.",1520938797,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I experienced a similar issue recently when I was testing something else. I made a few changes in the 2017 wikitext editor, abandoned my edit, and when I came back to the page my edit was ""recovered"" which wasn't helpful. I'll file a task for this.",1520938703,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037827, @TheDJ wrote:
+> I just encountered this for the first time and it's already blocking me...
+> 
+> I started writing a reply to a user with a section edit (WE 2017). Then I aborted this (Intentionally because there was a severe edit conflict because I went away for an hour or so before trying to submit). Then I went back to the same section of the new version and my change was recovered, but this caused it to reinsert the very old document. Now I don't know how to get the auto save to ignore my outdated session, so that I can properly comment on the current version of the page .....
+> 
+> Can we decide not to restore if the base revisions of the document are not the same ? Or create some way for me to be in control somehow ?
+
+I encountered the same problem when trying to recover from T189079. It definitely seems like it needs to be addressed.",1520926435,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037827, @TheDJ wrote:
+> I just encountered this for the first time and it's already blocking me...
+> 
+> I started writing a reply to a user with a section edit (WE 2017). Then I aborted this (Intentionally because there was a severe edit conflict because I went away for an hour or so before trying to submit). Then I went back to the same section of the new version and my change was recovered, but this caused it to reinsert the very old document. Now I don't know how to get the auto save to ignore my outdated session, so that I can properly comment on the current version of the page .....
+> 
+> Can we decide not to restore if the base revisions of the document are not the same ? Or create some way for me to be in control somehow ?
+
+I encountered this as well when trying to recover from T189079. It definitely seems like it needs to be addressed.",1520926420,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,@Deskana: Do you think we should make a follow-up task to implement James's UI to deal with TheDJs issue (T57370#4037827)?,1520886541,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I was under the impression it was going to be optional to restore your edit, like in James's mockup: T57370#2548772.",1520886400,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Also, I note I had predicted and summarised some of such edge cases and considerations as recently as January in related tickets... T184308#3889701 Might be worthwhile to take a quick look at that.",1520596551,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I just encountered this for the first time and it's already blocking me...
+
+I started writing a reply to a user with a section edit (WE 2017). Then I aborted this (Intentionally because there was a severe edit conflict because I went away for an hour or so before trying to submit). Then I went back to the same section of the new version and my change was recovered, but this caused it to reinsert the very old document. Now I don't know how to get the auto save to ignore my outdated session, so that I can properly comment on the current version of the page .....
+
+Can we decide not to restore if the base revisions of the document are not the same ? Or create some way for me to be in control somehow ?",1520596351,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I just encountered this for the first time and it's already blocking me...
+
+I started writing a reply to a user with a section edit (WE 2017). Then I aborted this (Intentionally because there was a severe edit conflict because I went away for an hour or so before trying to submit). Then I went back to the same section of the new version and I my change was recovered, but this causes it to reinsert the very old document. Now I don't know how to get the auto save to ignore my outdated session, so that I can properly comment on the current version of the page .....
+
+Can we decide not to restore of the base revisions of the document are not the same ? Or create some way for me to be in control somehow ?",1520596004,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037783, @Deskana wrote:
+>>>! In T57370#4037595, @TheDJ wrote:
+> To my knowledge, there aren't any cookies used for this, so I don't think so.
+
+That's an old policy, but it's about ALL client side storage: ""These generally include tracking pixels, JavaScript, and a variety of ""locally stored data"" technologies, such as cookies and local storage.""",1520596029,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037783, @Deskana wrote:
+>>>! In T57370#4037595, @TheDJ wrote:
+> To my knowledge, there aren't any cookies used for this, so I don't think so.
+
+That's an old policy, but it's about ALL client side storage. ""These generally include tracking pixels, JavaScript, and a variety of ""locally stored data"" technologies, such as cookies and local storage.""",1520596013,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037783, @Deskana wrote:
+>>>! In T57370#4037595, @TheDJ wrote:
+> To my knowledge, there aren't any cookies used for this, so I don't think so.
+
+That's an old policy, but it's about ALL client side storage.",1520595703,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037595, @TheDJ wrote:
+> * Session storage doesn't protect against full-on browser crashes I presume ?
+
+I induced a full browser freeze and crash in Chrome, and my edits were successfully recovered. This may not be true in other, or older, browsers.
+
+> * This might have to be noted / listed in the [[ https://wikimediafoundation.org/wiki/Cookie_statement | cookie policy ]] ?
+
+To my knowledge, there aren't any cookies used for this, so I don't think so.
+
+The other two questions are for engineers, not myself. :-)",1520594625,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I have 4 potential follow up questions/issues
+* I spotted a problem in that patch.. no try/catch around the session storage access (as with local storage usage, always needed).
+* Session storage doesn't protect against full-on browser crashes I presume ?
+* This might have to be noted / listed in the [[ https://wikimediafoundation.org/wiki/Cookie_statement | cookie policy ]] ?
+* We should actively blank this when definitively saving / cancelling. This would prevent the last edit being left in the browser's storage on things like public library computers, which we would like to avoid I think... (also, is there username info in the content being put in session storage ? because that might be a problem in that situation)",1520586054,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I have 4 potential follow up questions/issues
+* I spotted a problem in that patch.. no try/catch around the session storage access (as with local storage, usage always needed).
+* Session storage doesn't protect against full-on browser crashes I presume ?
+* This might have to be noted / listed in the [[ https://wikimediafoundation.org/wiki/Cookie_statement | cookie policy ]] ?
+* We should actively blank this when definitively saving / cancelling. This would prevent the last edit being left in the browser's storage on things like public library computers, which we would like to avoid I think... (also, is there username info in the content being put in session storage ? because that might be a problem in that situation)",1520586025,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Yeah. There may be bugs or follow-up work, but that can be in different tasks.",1520342434,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,Resolved?,1520330938,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413273 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Use session storage to auto-save
+
+[[https://gerrit.wikimedia.org/r/413273]]",1519762832,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,Note: the above patches are not intended to be a long-term saving mechanism.,1519321185,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413266 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (1a0bc9981)
+
+[[https://gerrit.wikimedia.org/r/413266]]",1519259492,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413273 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Use session storage to auto-save
+
+[[https://gerrit.wikimedia.org/r/413273]]",1519254050,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413266 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (1a0bc9981)
+
+[[https://gerrit.wikimedia.org/r/413266]]",1519251448,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413249 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Use sessionStorage to auto-save
+
+[[https://gerrit.wikimedia.org/r/413249]]",1519249530,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413249 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] Use sessionStorage to auto-save
+
+[[https://gerrit.wikimedia.org/r/413249]]",1519247754,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3924115, @cscott wrote:
+> This would be a good use of a general ""fork storage"" mechanism: the edit-in-progress would get stored as an unmerged fork of the main revision.
+
+Cool idea. But what if there is no main revision (creating a new page)?",1516952029,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"This would be a good use of a general ""fork storage"" mechanism: the edit-in-progress would get stored as an unmerged fork of the main revision.",1516949735,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,Proposed to #community-wishlist-survey-2017 ,1511107173,PHID-USER-lz5f7t47np7ftbnhn6i5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3601942, @Esanders wrote:
+> 
+> do our own memory management
+
+...or use someone else's, e.g. https://github.com/monsur/jscache",1505246413,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3416020, @Jdforrester-WMF wrote:
+> silently fail when the user's machine either has local storage disabled or is full?
+
+Well given we will be writing to LocalStorage every time a new edit session is started, this is going to happen often (and we can't rely on the edit session being closed 'gracefully'). It appears that most browsers will throw an exception when storage is exceeded, so if we do our own memory management and keep track of VE save sessions, we can prune the LRU session until their is enough free space. We can also prune sessions older than N minutes/hours so other users can still use LocalStorage (e.g. ResourceLoader).",1505246172,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I am sorry, I wanted to close and merge the other way. I try to fix it.",1505073579,PHID-USER-lz5f7t47np7ftbnhn6i5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,(wrong tab),1502377152,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Whatamidoing-WMF
+I am admittedly stretching the limits of what I know about javascript, but it appears something like
+```
+textarea.on('input', ...
+```
+solves that issue. I'm unsure, but a little extra code may be needed to catch cut/paste via right click.",1501945495,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Whatamidoing-WMF
+I am admittedly stretching the limits of what I know about javascript, but it appears something like
+```
+textarea.on('input', ...
+```
+does exactly that. I'm unsure, but a little extra code may be needed to catch cut/paste via right click.",1501945421,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Alsee, the 2010 WikiEditor doesn't know whether or not you've typed anything in the editing window yet, and therefore it cannot know whether there are any changes to be saved.
+",1501782134,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490603, @Whatamidoing-WMF wrote:
+> Because it isn't actually possible in the older wikitext editors.  
+
+My apologies, but I have to question your technical expertise on that point. I find it very difficult to imagine any reason that data-storing javascript could be added to one editor, but couldn't be added to the other.
+
+The community [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | requested this feature]]. Nearly two-thirds of the people supporting the request use VE for **zero percent** of their edits. They were quite obviously requesting this feature for the only editor that they use. 85% of supporters use Visual for 8% or less of their edits. They were also quite obviously requesting this feature for substantially-the-only-editor they use. Exactly one person uses Visual for more than half of their edits (57.6%). I'm sure no one objects to implementing autosave in the secondary editor as well.
+
+There is already a task open for this request: T75241
+
+Unless there is some clear reason not to do so, this task should be merged into  T75241 as a duplicate.
+If there is a desire for separate tasks for the two editors, the first priority work should be on the primary editor. I guess that would make this a subtask of T75241. 
+",1501748363,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490603, @Whatamidoing-WMF wrote:
+> Because it isn't actually possible in the older wikitext editors.  
+
+My apologies, but I have to question your technical expertise on that point. I find it very difficult to imagine any reason that data-storing javascript could be added to one editor, but couldn't be added to the other.
+
+The community [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | requested this feature]]. Nearly two-thirds of the people supporting the request use VE for **zero percent** of their edits. They were quite obviously requesting this feature for the only editor that they use. 85% of supporters use Visual for 8% or less of their edits. They were also quite obviously requesting this feature for substantially-the-only-editor they use. Exactly one person uses Visual for more than half of their edits (57.6%). I'm sure no one objects to implementing autosave in the secondary editor as well.
+
+There is already a task open for this request: T75241
+
+Unless there is some clear reason not to do so, this task should be merged into  T75241 as a duplicate.
+If there is a desire for separate tasks for the two editors, **the first priority work should be on the primary editor**. I guess that would make this a subtask of T75241. 
+",1501747894,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490603, @Whatamidoing-WMF wrote:
+> Because it isn't actually possible in the older wikitext editors.  
+
+My apologies, but I have to question your technical expertise on that point. I find it very difficult to imagine any reason that data-storing javascript could be added to one editor, but couldn't be added to the other.
+
+The community [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | requested this feature]]. Nearly two-thirds of the people supporting the request use VE for **zero percent** of their edits. They were quite obviously requesting this feature for the only editor that they use. 85% of supporters use Visual for 8% or less of their edits. They were also quite obviously requesting this feature for substantially-the-only-editor they use. Exactly one person uses Visual for more than half of their edits (57.6%). I'm sure no one objects to implementing autosave in the secondary editor as well.
+
+There is already a task open for this request: T75241
+
+Unless there is some clear reason not to do so, this task should be merged into  T75241 as a duplicate.
+If there is a desire for separate tasks for the two editors, **the first priority work should be on the primary editor**.
+",1501747785,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490603, @Whatamidoing-WMF wrote:
+> Because it isn't actually possible in the older wikitext editors.  
+
+My apologies, but I have to question your technical expertise on that point. I find it very difficult to imagine any reason that data-storing javascript could be added to one editor, but couldn't be added to the other.
+
+The community [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | requested this feature]]. Nearly two-thirds of the people supporting the request use VE for **zero percent** of their edits. They were quite obviously requesting this feature for the only editor that they use. 85% of supporters use Visual for 8% or less of their edits. They were also quite obviously requesting this feature for substantially-the-only-editor they use. And I'm sure no one objects to implementing it in the secondary editor as well.
+
+There is already a task open for this request: T75241
+
+Unless there is some clear reason not to do so, this task should be merged into  T75241 as a duplicate.
+If there is a desire for separate tasks for the two editors, **the first priority work should be on the primary editor**.
+",1501747091,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490428, @Alsee wrote:
+> Why is this described as a Visual Editor task? Visual Editor is a minor secondary editor, only used for a small percentage of edits. If auto save is implemented, it's certainly reasonable to also implement it in the secondary editor as well (VE).
+
+Because it isn't actually possible in the older wikitext editors.  
+
+Most modern browsers can preserve text within the older wikitext editors (e.g., if you accidentally click the 'back' button while you're editing, then your changes are usually there if you click the 'forward' button to go back to the editing window), but that they can't do this with VisualEditor (either mode).  So, in effect, the team is planning to cover for a limitation in browsers by building this capability internally.  If you are interested in this subject, then you may want to read about HTML textareas (used in the older wikitext editors) and ContentEditable (used in online rich-text editors, including VisualEditor).
+",1501616413,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Why is this described as a Visual Editor task? Visual Editor is a minor secondary editor, only used for a small percentage of edits. If auto save is implemented, it's certainly reasonable to also implement it in the secondary editor as well (VE).",1501614519,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3415924, @Esanders wrote:
+>>>! In T57370#2976776, @Esanders wrote:
+>> The main concern is what happens when we run out of storage.
+> 
+> The workaround for local storage limitations is remote storage, with the downsides:
+> * slower (potentially several seconds for long articles and slow connections, but it's background and async so meh)
+> * doesn't work offline, obviously
+> * infrastructure costs of storing all the extra data
+> * would probably need user consent
+
+The trump concern is legal issues arising from holding server-side information subject to expensive discovery mechanisms, as I understand it (I'm not a lawyer, //etc.// //etc.//).
+
+How about we just go ahead with this as-is, persisting last-edit-state so restarting browsers get back to the state before the crash/whatever, and silently fail when the user's machine either has local storage disabled or is full?",1499447076,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#2976776, @Esanders wrote:
+> The main concern is what happens when we run out of storage.
+
+The workaround for local storage limitations is remote storage, with the downsides:
+* slower (potentially several seconds for long articles and slow connections, but it's background and async so meh)
+* doesn't work offline, obviously
+* infrastructure costs of storing all the extra data
+* would probably need user consent
+",1499444341,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Also the caveat for txs is that we need access to the original document state. That is fine for regular MW edits, but if they're using a restbase stash after switching that may be a problem. In those cases we could either store initial HTML or disable auto-save.",1485534255,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Also the caveat for txs is that we need access to the original document state. That is fine for regular MW edits, but if they're using a restbase stash after switching that may be a problem (although we could just disable auto-save :/ )",1485534114,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Twice HTML => maybe 3.4MiB for Obama => two unsaved edits and we've over-flowed Firefox's local storage, that sucks quite a bit, which would steer us to Transactions. OTOH, the growth characteristics of Transactions for long edits (the ones where this would be particularly useful) make me a little uncomfortable about whether it'd be better….",1485533621,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"The main concern is what happens when we run out of storage. A single document is unlikely to do this, but with multiple documents saved this would be quite common. We would need to do our own memory management to throw away old stashes.",1485533477,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"| | **Transactions** | **HTML** | **Entire linear model** |
+| **Initial storage** | None. With the caveat that we will have access to the initial document state the user saw at a later date. Could be problematic if user has switched from WT mode. Could instead use HTML storage for initial state, then transactions for changes, but wipes out storage advantage. | proportional to article size (~1.7MB for Obama) | About twice HTML |
+| **Incremental storage** | ~400 bytes to type a single character. Typing a 200 word / 3 sentence paragraph with a few annotations took 60k. | Not much more than a few bytes per character | About twice HTML |
+| **Storage edge cases** | Blanking whole document / pasting in large sections multiple times will results in really large transactions, more that the initial storage of ‘Entire linear model’ | None really, just the document length. | << |
+| **Undo stack** | Preserved | Not preserved | << |
+| **Save performance** | Very fast, small JSON.stringify | Can be a few hundred ms for long articles. If waiting for N seconds of user inactivity this may not be a big issue, but in some cases esp slow machines, edit area will become momentarily non-responsive. | Fairly fast, large JSON.stringify |",1485533164,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#2558298, @Ltrlg wrote:
+> @Jdforrester-WMF I have been working on a Confluence wiki with (server-side) auto-save for several months and they have something your current proposal do not include: being able to see a diff before choosing. It is really useful, because I often do not remember what I was doing exactly when I closed the editing page 2 or 3 days before editing again.
+
+Hmm. That's certainly a possibility, but I don't think it's a good idea to try to shoe-horn that into the first version. In particular, I'd rather we had (at least) designs for {T105173} (so that users didn't have to know wikitext to understand what they're shown) and possibly {T39931} as a better, more fluid way of showing that to users as they edit. I've created {T143341} for this idea.",1471542901,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Jdforrester-WMF I have been working on a Confluence wiki with (server-side) auto-save for several months and they have something your current proposal do not include: being able to see a diff before choosing. It is really useful, because I often do not remember what I was doing exactly when I closed the editing page 2 or 3 days before editing again.",1471375443,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,Hopefully,1471148521,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I lost some work recently when I accidentally closed the wrong tab.  Will your current plan solve that problem?
+",1471098931,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"OK, so, dusting this off, my current proposal is as follows:
+
+* As you edit, we stash a copy of the edited document whilst you're editing it into indexDB or whatever (locally on your machine); this would apply both to VE and the NWE surfaces.
+* When you save, once we get confirmation back that it's saved we delete from the local machine the in-process edit.
+* On load, if there's a draft for this page which based off the current revision, we prompt you to either resume the edit, or start a fresh edit (and discard the draft), with something looking roughly like:
+{F4357662}
+
+This means that //e.g.// if your computer crashes, you lose network/power, or whatever, you can resume edits. It's optional, so if somehow you've made an edit that causes the editor to crash you can avoid re-triggering it (so you're not caught in a loop).
+
+The main downside is that it doesn't let you move computers during an edit (which is not a common issue for users right now, but is a bit of an 'oh well').
+
+If you load and there's a partial edit based on an out-of-date revision it probably isn't possible for us to help out automatically — we can't do an edit merge at that point, as that's a DB/server-side operation, and we can't tell whether or not the edit will save cleanly. Maybe just discard it silently?",1471030276,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,See also: Wikitext editor patch for this: https://gerrit.wikimedia.org/r/#/c/5130/,1397680537,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,*** Bug 52988 has been marked as a duplicate of this bug. ***,1383280899,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"If local storage is going to be seriously considered, with pages being auto-saved, some issues to consider:
+
+How many open VE's can be autosaved?  Only saving one VE session makes management very simple, but it is probably sufficient for only a small subset of the editing community.
+
+The local storage limit of 5 MB in most user agents is going to be a problem.  Also VE needs to intelligently handle the case where the offline storage is not available or the origin has exceeded its limit.  The user needs to know when their session isnt being auto-saved due to client side factors.
+
+Are these autosaved versions going to persist across browser sessions?
+
+If the VE sessions do persist, how will VE determine which VE autosaved versions are no longer needed and can be deleted to allow more VE sessions to be autosaved in the future.  Will the user be able to manage which autosaves they no longer need?",1381283422,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"(In reply to comment #1)
+> Why not deploy the drafts extension, and add any VE support needed?
+
+Have commented there explaining.",1381267333,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"(In reply to comment #1)
+> Why not deploy the drafts extension, and add any VE support needed?
+
+[[mw:Extension:Drafts]], for those unfamiliar.",1381102292,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Why not deploy the drafts extension, and add any VE support needed?",1381101467,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Hi
+When I run parsoid linked to a wiki which is https only, it doesn't work. This can be reproduced in any installation.
+
+I set port 80 to be a redirect to port 443, and the parsoid URL is https://wiki.name/api.php in localsettings.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381073520,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-xya74ryevlevdpyqmth6,task_description,resolved
+Parsoid cannot connect to https-only host?,"Shall we close this? I know that VE functions happily on wikitech.wikimedia.org now, which always uses HTTPS.",1428265426,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I wanted to update this bug with my findings. I now have 1.23wmf7 and the latest builds of Parsoid and VisualEditor working happily with SSL as the default (and forced) connection method for users.
+
+In my LocalSettings.php I have the following:
+
+//Hook it up to Parsoid
+$wgVisualEditorParsoidURL = 'http://my.site.com:8000';
+ 
+$wgVisualEditorParsoidPrefix = 'localhost';
+
+
+In localsettings.js I have:
+
+parsoidConfig.setInterwiki('localhost' , 'http://my.site.com:81/w/api.php');
+
+You can see that we're directing traffic over port 81 to allow Parsoid access.
+
+The issue I was experiencing related to saving a page was due to having an older version (pre 1.9) of Semantic MediaWiki installed with 1.23.",1388082421,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I've followed the troubleshooting guide and I'm still having issues connecting to a https-only host.
+
+From the server I can run the following with success:
+
+curl http://my.site.com:81/w/api.php
+
+I opened port 81 to allow for http access to the api endpoint.
+
+However I cannot seem to connect to Parsoid, the app in question. 
+
+curl http://my.site.com:8000 returns the human-readable landing page for the Parsoid web service.
+
+curl http://my.site.com:8000/localhost/Introduction
+
+returns no message via the command line.
+
+I can start Parsoid via node server.js
+
+I can launch VisualEditor and edit a page normally, everything works.
+
+server.js spits out the following:
+
+starting parsing of localhost:Introduction
+completed parsing of localhost:Introduction in 1660 ms
+
+As soon as I go to save an edit, a small note appears under the Summary box.
+
+Error: Unknown error.
+
+server.js reports nothing
+
+
+While Parsoid is running (node server.js) and I attempt the following
+
+curl http://my.site.com:8000/localhost/Introduction
+
+I see the message:
+
+starting parsing of localhost:Introduction
+redirected localhost:Introduction to revision 62067",1387213772,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I know it works, it's a workaround. I am hosting the site in a CentOS server, but despite the research I have done some time ago I couldn't install the certificate in the system root, so neither PHP and node.js see the certificate. 
+
+I will try again now. Is there any documentation you know about this? (sorry if it's off-topic)",1386278143,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"(In reply to comment #8)
+> I am sorry, I can't pay for a real certificate. Is there a way to add my root
+> certificate to Parsoid? Does it use the system certificates?
+> 
+> Or as a workaround, is there a way to permit self-signed authorities?
+
+Your wiki actually works by setting the API URL to http://wiki.mc128k.info/api.php.
+
+Nodejs uses openssl, so I'm guessing that you can install additional CA certs in /etc/ssl/certs/ (assuming you are using Debian).",1386277852,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I am sorry, I can't pay for a real certificate. Is there a way to add my root certificate to Parsoid? Does it use the system certificates?
+
+Or as a workaround, is there a way to permit self-signed authorities?
+
+Thanks.",1386273347,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Parsoid is only using HTTP, so trying to connect to it via HTTPS is going to fail. It can connect to MediaWiki using HTTPS though when configured to do so in localsetting.js. Please check the steps in https://www.mediawiki.org/wiki/Parsoid/Troubleshooting to make sure Parsoid is working.
+
+> https://wiki.mc128k.info
+
+Your SSL cert does not seem to be signed by a trusted CA, which likely explains your issue. Try with a signed SSL cert.",1386270337,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Addition:
+Changing $wgVisualEditorParsoidURL to 'https://my.wiki.com:8000'; results in a different error.
+
+Error loading data from server: parsoidserver-http-curl-error: SSL connect error. Would you like to retry?
+
+
+Headers below:
+
+Start request POST /w/api.php
+HTTP HEADERS:
+HOST: my.wiki.com
+CONNECTION: keep-alive
+CONTENT-LENGTH: 60
+AUTHORIZATION: Basic bWVtY2FjadGU6cGFzc3dvcmQ=
+ACCEPT: application/json, text/javascript, */*; q=0.01
+ORIGIN: https://my.wiki.com
+X-REQUESTED-WITH: XMLHttpRequest
+USER-AGENT: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36
+CONTENT-TYPE: application/x-www-form-urlencoded; charset=UTF-8
+REFERER: https://my.wiki.com/w/index.php?title=Main_Page&veaction=edit
+ACCEPT-ENCODING: gzip,deflate,sdch
+ACCEPT-LANGUAGE: en-US,en;q=0.8
+COOKIE: infoLoggedOut=1386191878; __utma=198203634.1203293077.1386191715.1386191715.1386191715.1; __utmc=198203634; __utmz=198203634.1386191715.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); infoUserID=378; infoUserName=Clkoerne; info_session=4f15c368d4244cc2b9e72e06f65adc12; wikiEditor-0-booklet-characters-page=latin; wikiEditor-0-toolbar-section=advanced; vector-nav-p-Repository=true; vector-nav-p-tb=true
+CACHES: MemcachedPhpBagOStuff[main] MemcachedPhpBagOStuff[message] MemcachedPhpBagOStuff[parser]
+[cookie] session_set_cookie_params: ""0"", ""/"", """", ""1"", ""1""
+LocalisationCache: using store LCStoreDB
+Unstubbing $sfgFormPrinter on call of $sfgFormPrinter::setInputTypeHook from SFSelect_formSetup
+Unstubbing $wgParser on call of $wgParser::setHook from ExtDynamicPageList::setupDPL
+Parser: using preprocessor: Preprocessor_DOM
+Connected to database 0 at lnxvmiptdbt01
+Class UniversalLanguageSelectorHooks not found; skipped loading
+Fully initialised
+User: got user 378 from cache
+User: loading options for user 378 from override cache.
+User: logged in from session
+ApiMain::setCacheMode: setting cache mode private
+IP: 10.29.122.24",1386269909,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I am experincing the same bug.
+
+Attempting to evoke VisualEditor to edit any pages where we have redirected all traffic to https results in the error.
+
+
+In the browser:
+Error loading data from server:parsoidserver-hhtp-curl-error:
+Empty reply from server. Would you like to retry?
+
+
+Parsoid displays the following upon each attempt to edit a page (in this case Main Page):
+
+ERROR in localhost:Main_Page
+Stack trace: DoesNotExistError: Page Fetch failure for null
+worker 20040 died, restarting.
+
+
+MediaWiki logs show the following for the request:
+
+Start request POST /w/api.php
+HTTP HEADERS:
+HOST: my.wiki.com
+CONNECTION: keep-alive
+CONTENT-LENGTH: 60
+ACCEPT: application/json, text/javascript, */*; q=0.01
+ORIGIN: https://my.wiki.com
+X-REQUESTED-WITH: XMLHttpRequest
+USER-AGENT: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
+CONTENT-TYPE: application/x-www-form-urlencoded; charset=UTF-8
+REFERER: https://my.wiki.com/wiki/Main_Page?veaction=edit
+ACCEPT-ENCODING: gzip,deflate,sdch
+ACCEPT-LANGUAGE: en-US,en;q=0.8
+COOKIE: __utma=198203634.575160840.1386267474.1386267474.1386267474.1; __utmb=198203634.2.10.1386267474; __utmc=198203634; __utmz=198203634.1386267474.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); infoUserID=378; infoUserName=Clkoerne; info_session=7200a1cbfcef48ded410afb07850a6fc
+CACHES: MemcachedPhpBagOStuff[main] MemcachedPhpBagOStuff[message] MemcachedPhpBagOStuff[parser]
+[cookie] session_set_cookie_params: ""0"", ""/"", """", ""1"", ""1""
+LocalisationCache: using store LCStoreDB
+Unstubbing $sfgFormPrinter on call of $sfgFormPrinter::setInputTypeHook from SFSelect_formSetup
+Unstubbing $wgParser on call of $wgParser::setHook from ExtDynamicPageList::setupDPL
+Parser: using preprocessor: Preprocessor_DOM
+Connected to database 0 at lnxvmipdbt01
+Class UniversalLanguageSelectorHooks not found; skipped loading
+Fully initialised
+User: got user 378 from cache
+User: loading options for user 378 from override cache.
+User: logged in from session
+ApiMain::setCacheMode: setting cache mode private
+IP: 10.9.191.150",1386269124,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Debug log from parsoid:
+ - worker(23680) ready
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 4 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 3 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 2 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 1 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 0 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+ERROR in localhost:Main_Page:
+Page Fetch failure for null
+Stack trace: DoesNotExistError: Page Fetch failure for null
+worker 23671 died (1), restarting.
+ - worker(23690) loading...
+ - worker(23690) ready
+
+
+I don't know if the API works from the external network, this is a protected wiki, I hope login won't be necessary.
+
+https://wiki.mc128k.info",1386145344,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I just tested this with 'enwiki' and
+
+parsoidConfig.setInterwiki( 'enwiki', 'https://en.wikipedia.org/w/api.php' );
+
+We don't set the port explicitly and use the API uri as-is, so in theory https-only APIs should work. Do you have a public https-only API URI we can test with?",1386118696,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I'm sorry, I thought Parsoid was part of VisualEditor. Corrected. Thanks.
+Latest git versions, of parsoid, mediawiki, visualeditor.",1381092220,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Hmm, shouldn't this be filed under product ""Parsoid""? :)
+Which Parsoid version and which MediaWiki version is this about?",1381092082,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+VisualEditor: Link tooltip is not updated if link inspector is not explicitly closed,"Germanjoe reports:
+""A small (very small) bug: mouse display of links doesn't get actualized, when the editor leaves the small edit dialog to change links without pressing the ""<"" button (just by clicking somewhere else in the text the edit dialog closes aswell). 
+
+Example: change German to ""German language|German"" in some test article and leave the link editor without pressing ""<"". The mouse display should show ""German language"" as internal link info, but still shows ""German"". However, ""German language|German"" is correctly saved to the source text (just the display is wrong).""
+
+Further testing shows that this can be demonstrated multiple ways. In all cases close the link input widget by clicking elsewhere on the editing surface, do not click < (that works as expected)
+
+*Change ""[[German]]"" to ""[[German language|German]]"". Tooltip is ""German"" (expected ""German language)
+*Change ""[[Welsh language]]"" to ""[[Welsh language literature|Welsh language]]"". Tooltip is ""Welsh language"" (expected ""Welsh language literatue"")
+*Change ""French"" to ""[[French language|French]]"". Tooltip is ""French"" (expected ""French language"")
+*Change ""Portuguese"" to ""[[Brazillian|Portuguese]]"". Tooltip is ""Portuguese"" (expected ""Brazillian"")
+*Change ""Polish language"" to ""[[Polish Language Council|Polish language]]"". Tooltip is ""Polish language"" (expected ""Polish Language Council"")
+
+The tooltip is corrected as soon as one of the following actions happens:
+*The link input widget is opened on that link again. Even if no changes are made and it is closed by clicking elsewhere.
+*The link display text is amended on the editing surface, e.g. ""[[Polish Language Council|Polish language]]"" → ""[[Polish Language Council|Polish informal language]]""
+*Text is typed adjacent to either end of a link, e.g. [[Italian]] → [[Italian]]s
+*Annotation is applied to the display text.
+
+I've marked the severity as ""trivial"" because in all cases the correct target is displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1380909000,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-cefkpaw5jsqxys54667r,task_description,resolved
+VisualEditor: Link tooltip is not updated if link inspector is not explicitly closed,This has now been fixed.,1402549108,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cefkpaw5jsqxys54667r,task_subcomment,NA
+VisualEditor: Spellcheck freaks out in Firefox when focusable nodes are focused,"* Open a document in a language that is not your default language,
+  for example:
+  https://fr.wikipedia.org/wiki/Cumul_des_mandats_en_France?veaction=edit
+  (if you're not French).
+* Assuming your browser does have a French dictionary, the article should
+  have few to 0 red-underlined words.
+* Click on a [1] reference.
+* Observe suddenly almost every word is spellcheck invalidated by red lines
+* Moving the cursor by keyboard arrows still keeps them invalid.
+* As soon as you actually use the mouse to click for a cursor move, that is
+  when it switches back to the correct language (or perhaps it disables
+  spellcheck)
+
+Not sure, but I think this is a regression.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380896700,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mpgdokvlglkvrsqagxhx,task_description,resolved
+VisualEditor: Spellcheck freaks out in Firefox when focusable nodes are focused,Can't reproduce this issue anymore.,1530906787,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-mpgdokvlglkvrsqagxhx,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","I simply deleted a word from the leading paragraph in the article below, and got this as diff:
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%3ANurick%2F%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_-_%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99&diff=14670508&oldid=14667916
+
+To reproduce: Revert to the previous version in that diff, edit the article in VE, and delete a word from the leading paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380822960,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_description,resolved
+"Parsoid renders template as comment, breaking serialization",*** Bug 56722 has been marked as a duplicate of this bug. ***,1383851745,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","Change 90687 merged by jenkins-bot:
+Match all characters when testing comments for JSON
+
+https://gerrit.wikimedia.org/r/90687",1382551909,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","Change 90687 had a related patch set uploaded by Arlolra:
+Match all characters when testing comments for JSON
+
+https://gerrit.wikimedia.org/r/90687",1382152168,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","On second thought, I think it's because `.` doesn't match newline chars.",1382152030,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","The problem here is that the contents of that comment isn't matching this regex,
+
+  /^\{.*\}$/.test( content )
+
+https://github.com/wikimedia/mediawiki-extensions-Parsoid/blob/master/js/lib/mediawiki.DOMPostProcessor.js#L95
+
+It's not recognizing the last character as }. Taking content.charCodeAt( content.length - 1 ) returns undefined. Probably because of the unicode characters. Switching to something like,
+
+  /^\{\""@type\""/.test( content )
+
+seems to work but I'm interested to see where exactly things are going wrong.",1382149987,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","This is due to a Parsoid bug.
+
+Example that Moriel gave me: http://parsoid.wmflabs.org/he/%D7%93%D7%A0%D7%99%D7%90%D7%9C_%D7%A8%D7%93%D7%A7%D7%9C%D7%99%D7%A3
+
+HTML starts with:
+
+<html><head>...</head><body>
+<!--{""@type"":""mw:Transclusion"",""attrs"":[{""name"":""typeof"",""value"":""mw:Transclusion""},{""name"":""about"",""value"":""#mwt1""},{""name"":""id"",""value"":""mwt1""},{""name"":""data-mw-arginfo"",""value"":""{\""dict\"":{\""target\"":{\""wt\"":\""שחקנים
\\n\"",\""href\"":\""./תבנית:שחקנים\""},\""params\"":{\""שם\"":{\""wt\"":\""דניאל רדקליף\""},\""תמונה\"":{\""wt\"":\""[[קובץ:Daniel Radcliffe Paris 2012.jpg|200px]]\""},\""כיתוב\"":{\""wt\"":\""<small> דניאל רדקליף, [[2012]]</small>\""},\""תאריך לידה\"":{\""wt\"":\""23 ביולי 1989\""},\""מקום לידה\"":{\""wt\"":\""[[לונדון]], [[אנגליה]], [[הממלכה המאוחדת]]\""},\""כינוי\"":{\""wt\"":\""דן\""},\""דמות\"":{\""wt\"":\""[[הארי פוטר (דמות)|הארי פוטר]]\""},\""בכורה\"":{\""wt\"":\""בסדרה [[דייוויד קופרפילד]], 1999\""},\""אתר אינטרנט\"":{\""wt\"":\""http://www.danradcliffe.co.uk/\""},\""קישור\"":{\""wt\"":\""0705356\""}}},\""paramInfos\"":[{\""k\"":\""שם\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""
\\n\""]},{\""k\"":\""תמונה\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""כיתוב\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""תאריך לידה\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""מקום לידה\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""כינוי\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""דמות\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""בכורה\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""אתר אינטרנט\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""קישור\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]}]}""},{""name"":""data-parsoid"",""value"":""{\""tsr\"":[0,356],\""src\"":\""{{שחקנים
\\n|שם=דניאל רדקליף
\\n|תמונה=[[קובץ:Daniel Radcliffe Paris 2012.jpg|200px]]\\n|כיתוב=<small> דניאל רדקליף, [[2012]]</small>\\n|תאריך לידה=23 ביולי 1989\\n|מקום לידה=[[לונדון]], [[אנגליה]], [[הממלכה המאוחדת]]\\n|כינוי=דן\\n|דמות=[[הארי פוטר (דמות)|הארי פוטר]]\\n|בכורה=בסדרה [[דייוויד קופרפילד]], 1999\\n|אתר אינטרנט=http://www.danradcliffe.co.uk/\\n|קישור=0705356\\n}}\"",\""tagId\"":1}""}]}-->
+<table class=""infobox"" style=""width:18em; font-size:85%;"" cellspacing=""5"" about=""#mwt1"" data-parsoid=""{}"">[....]</table>
+<meta typeof=""mw:Transclusion/End"" about=""#mwt1"" data-parsoid=""{&quot;dsr&quot;:[null,356,null,null]}"">
+
+Note how:
+* The transclusion starts with a comment (!) which tries to be in the #mwt1 about group
+* The transclusion continues with a table in that same about group
+* The about group ends with a meta tag in that same about group
+
+This doesn't serialize cleanly at all, the template gets inserted into the wikitext and the table gets serialized as wikitext as well. Even the <meta> tag gets serialized: http://parsoid.wmflabs.org/_rt/he/%D7%93%D7%A0%D7%99%D7%90%D7%9C_%D7%A8%D7%93%D7%A7%D7%9C%D7%99%D7%A3
+
+In VisualEditor, this causes:
+* corruption on save like in the diff Moriel linked
+* the user to be able to edit inside the infobox, because the comment is ignored and there are no attributes on the <table> telling VE it's part of a template (there's about=""#mwt1"" but that doesn't refer back to a valid about group, so it's interpreted as the start of an about group)",1382031725,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"Repro:
+
+1. Create a new page with wikitext ""[[中文]]"" on zhwiki
+2. VisualEditor-edit this page and type ""s"" at the end
+3. The whole document now looks as if it has a link to ""中文"" with text ""中文s""
+4. Save the page
+5. Resulting wikitext is ""[[中文]]s"", and in rendered HTML (both PHP and Parsoid - bug 41151), ""s"" is not a part of the link text
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380741240,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_description,declined
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,I do not get the reported problem in Firefox 18 (And Chromium 25).,1381273288,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"I downloaded versions 21, 22 and 23 from: https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/21.0/ (etc.)
+
+I didn't get your reported behaviour in any of them. :-(",1380761975,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #7)
+> (In reply to comment #6)
+> > (In reply to comment #4)
+> > > I get:
+> > > 
+> > > <p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation
+> > > ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+> > > 
+> > > … when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+> > > 
+> > > Very odd. :-(
+> > 
+> > Hmm in Firefox 24 it's no longer reproducible here...
+> 
+> If you can reproduce in Firefox 22 again, once it's in the broken state in
+> the
+> ContentEditable surface please place the cursor to the left (up-page of) the
+> link and insert a new line. This should trigger a re-render and cause the
+> shown
+> HTML to be corrected to what it should be?
+
+Unfortunatly I don't know how to get it back now :(
+
+I simply APT updated it. Does any have some hint about downgrading a package?",1380761514,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #6)
+> (In reply to comment #4)
+> > I get:
+> > 
+> > <p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation
+> > ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+> > 
+> > … when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+> > 
+> > Very odd. :-(
+> 
+> Hmm in Firefox 24 it's no longer reproducible here...
+
+If you can reproduce in Firefox 22 again, once it's in the broken state in the ContentEditable surface please place the cursor to the left (up-page of) the link and insert a new line. This should trigger a re-render and cause the shown HTML to be corrected to what it should be?",1380759700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #4)
+> I get:
+> 
+> <p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation
+> ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+> 
+> … when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+> 
+> Very odd. :-(
+
+Hmm in Firefox 24 it's no longer reproducible here...",1380758934,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #4)
+> I get:
+> 
+> <p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation
+> ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+> 
+> … when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+> 
+> Very odd. :-(
+
+btw I can't reproduce it using Chrome either.",1380757200,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"I get:
+
+<p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+
+… when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+
+Very odd. :-(",1380756967,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #2)
+> Are you absolutely sure it showed as <a>中文s</a> (because it really
+> shouldn't!)?
+
+Yes - already checked with inspector.
+
+> What browser were you using?
+
+Firefox 22.",1380754494,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #0)
+> Repro:
+> 
+> 1. Create a new page with wikitext ""[[中文]]"" on zhwiki
+> 2. VisualEditor-edit this page and type ""s"" at the end
+> 3. The whole document now looks as if it has a link to ""中文"" with text ""中文s""
+> 4. Save the page
+> 5. Resulting wikitext is ""[[中文]]s"", and in rendered HTML (both PHP and
+> Parsoid
+> - bug 41151), ""s"" is not a part of the link text
+
+I can't reproduce that - I got <a>中文</a>s in the edit surface, and it saved as expected:
+
+* https://zh.wikipedia.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox&diff=28804968&oldid=28804967 (for linktrail)
+
+https://zh.wikipedia.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox&diff=28804969&oldid=28804968 (for linkhead)
+
+Are you absolutely sure it showed as <a>中文s</a> (because it really shouldn't!)? What browser were you using?",1380753439,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"Linkprefix is also affected - type ""s"" at the beginning instead of the end in the repro above.",1380741412,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,"See https://fr.wikipedia.org/wiki/Fichier:Bug_%C3%A9diteur_visuel_barre_de_menu_style_de_texte_sur_deux_lignes.png .
+In languages like French and Italian some options in that menu are long (multiple words names like Titre de section) and the last word will appear under the toolbar itself.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380711000,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xkup4dal7lu2v5on7iek,task_description,resolved
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,*** Bug 50639 has been marked as a duplicate of this bug. ***,1385378243,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,Fixed and will go out next week.,1380837026,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,"Change 87450 merged by jenkins-bot:
+Allow menu tool groups to be wider if needed
+
+https://gerrit.wikimedia.org/r/87450",1380836998,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,"Change 87450 had a related patch set uploaded by Trevor Parscal:
+Allow menu tool groups to be wider if needed
+
+https://gerrit.wikimedia.org/r/87450",1380835506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,"It happens with Firefox/Chrome, Monobook/Vector, and the zoom used in the page does not matter.",1380711110,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","Best seen on a slow connection e.g at crossbrowsertesting.com; I used Chrome 29 on OSX 10.7
+
+Seen on beta labs and test2wiki with a fresh browser instance: 
+
+* Click Edit/beta, invoke VE
+
+** View of page appears, then disappears, refreshes and appears again before ""Welcome to..."" iframe appears
+
+* Click X to dismiss iframe
+
+** iframe disappears for a moment, then reappears, then disappears again
+
+Given a slow enough connection, this behavior could be bothersome for regular users of VE.  
+
+It definitely causes constant failures in the browser tests for Chrome on both beta labs and test2wiki. 
+
+This is not seen in Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55756",1380670380,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-g37szxauflfw6qlavwpb,task_description,declined
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page",This bug was reported and is reproducible against Chrome version 29 but does not appear in Chrome version 30.  Closing.,1381934805,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","This may only happen in Chrome 29, I have yet to repro in Chrome 30",1381871567,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","
+Because both the underlying page and the Welcome to... overlay appear and disappear and reappear and then finally disappear for good, there is a chance that the correct elements will be in place at the times that the test looks for them.  On rare occasions the  build will hit everything with perfect timing. 
+
+The other interesting artifact of this issue is that the tests in each build fail for different reasons, because the page and the overlay are appearing and disappearing and reappearing.
+
+Watching the behavior in crossbrowsertesting as noted above is instructive.  The appear/disappear/reappear/disappear-again behavior is easily seen, I just checked it again.
+
+And while the appearance of the 'You are not logged in' notice despite being logged in is more difficult to reproduce, it seems to be a symptom of the same issue.",1381853242,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","I'm confused as to how the browser tests for Chrome passed 9 days after this bug was filed - https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/72/ - only to fail again immediately thereafter, where the only intervening change in VisualEditor's code base was an alteration to the browser tests - https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/73/ - which feels like a different issue, and one where the problem is with the tests, not the code they are testing?",1381851780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","still seeing this in automated tests
+
+also, I reproduced this again manually using the slow connection at crossbrowsertesting.com as noted, and in addition to seeing the double-load of the page and double-load of the welcome notice, after clearing the notice I am presented with a message ""You are not logged in"".  This is impossible of course, since I have to be logged in with the opt-in preference set in order to be able to invoke VE at all. 
+
+The ""You are not logged in"" notice does not appear consistently.",1381497555,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: Pressing ""enter""/""return"" on a selected node should open its dialog","When a template is selected in the VE editing surface pressing enter should open the transclusion dialog.
+
+When an image is selected in the VE editing surface pressing enter should open the media settings dialog.
+
+These will be of benefit to people making textual changes to the surrounding context who want to make textual changes to the template output / image caption.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50996",1380637920,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6g5do6pkec5ll56oa4cb,task_description,resolved
+"VisualEditor: Pressing ""enter""/""return"" on a selected node 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",1395274517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6g5do6pkec5ll56oa4cb,task_subcomment,NA
+"VisualEditor: Pressing ""enter""/""return"" on a selected node should open its dialog","Change 103062 had a related patch set uploaded by Robmoen:
+Create mixin for ce nodes that responds to dblclick
+
+https://gerrit.wikimedia.org/r/103062",1395182321,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6g5do6pkec5ll56oa4cb,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"**Author:** `romaine.wiki`
+
+**Description:**
+The VisualEditor substitutes templates that shouldn't been substituted. The largethumb template got substituted on several occasions, like:
+
+https://nl.wikipedia.org/w/index.php?title=Managua_%28stad%29&diff=38749742&oldid=38743043
+
+If this continues to happen too long, we are forced to disable the VisualEditor for everyone as it changes things that absolutely should not be changed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54315",1380575880,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2pa34yqzcieje3dwrtub,task_description,resolved
+Images: {{largethumb}} template on nlwiki getting substituted on save,Scheduled for deployment next Wednesday.,1392422883,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"Change 110095 merged by jenkins-bot:
+Set up data-mw for all templated image attributes.
+
+https://gerrit.wikimedia.org/r/110095",1392413847,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"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",1391639496,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"If the Parsoid will be able to parse this, this would at least avoid bad rendering (thumbnail at the right size) and fix (selfishly) my concern :)",1386531660,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"We can parse it (so that it renders as expected), but I don't see a sane way to represent multiple attributes generated by the same template for visual editing.",1386440765,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"@Gabriel Do you mean Parsoid won't be able to parse this template in the same way like the PHP one does?
+
+After discussing a little bit about that on the nlwiki IRC channel, they are (of course) not so happy about that. Not only because the thousands of pages but also because the template is old and a lot of people would have then to change their habits.",1386437138,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"(In reply to comment #4)
+> Wanted to create an offline copy of nlwiki; but this bug is, for this usage,
+> a
+> showstopper.
+> 
+> The rendering is awful (but this is nothing new), for example:
+> http://parsoid-lb.eqiad.wikimedia.org/nlwiki/Abraham_Lincoln?oldid=39371115
+> 
+> ... and such type of templates are widely used: ~10.000 articles only for
+> {{largethumb}} on nlwiki. This bumps the whole size of the dump by a factor
+> 2.
+> 
+> @James, good news: I have had a look a little bit around and I don't have
+> found
+> other templates working on the same principle.
+
+@Kelson, that is great news! Scott is looking into image rendering issues, so assigning to him. We should be able to add a special-case hack for this template and edit-protect affected images.
+
+For proper editing the thumb parameter should be pulled out, as in |thumb|{{large}} with large returning just something like '400px'. That will require some convincing and bot activity.",1386358615,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"Wanted to create an offline copy of nlwiki; but this bug is, for this usage, a showstopper.
+
+The rendering is awful (but this is nothing new), for example:
+http://parsoid-lb.eqiad.wikimedia.org/nlwiki/Abraham_Lincoln?oldid=39371115
+
+... and such type of templates are widely used: ~10.000 articles only for {{largethumb}} on nlwiki. This bumps the whole size of the dump by a factor 2.
+
+@James, good news: I have had a look a little bit around and I don't have found other templates working on the same principle.",1386332566,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,This doesn't round trip in Parsoid.,1382449752,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"**romaine.wiki** wrote:
+
+I haven't seen it happen with other templates so far.",1381767772,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"Is this just the {{largethumb}} template, or are there others? (Templates that define some but not all of the parameters of an image are particularly troublesome.)",1380833746,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+VisualEditor: Linebreaks not preserved when converting preformatted text to paragraph text. ↵ Displayed in VE but not saved.,"Screenshot explaining issue with visualeditor
+
+Hi
+These are the steps:
+
+*Create a preformatted multiline text, inserting a space before each line, in source mode.
+*Open visualeditor, select the text inside the box (the preformatted text)
+*Change text type to ""paragraph""
+*The text is badly converted, return characters appear on the line. If the text is saved the return characters are lost.
+*This happens in other cases too, tab symbols are displayed sometimes.
+
+Thank you.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12384}",1380563940,PHID-USER-vj2bbc63joi46qr5a5nq,PHID-TASK-iesy7n57vtjmvbveuqa4,task_description,open
+VisualEditor: Linebreaks not preserved when converting preformatted text to paragraph text. ↵ Displayed in VE but not saved.,The ↵ characters indicate that the newline is preserved as if you edit the page subsequently and convert the paragraph to preformatteed the line breaks return.,1380644617,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-iesy7n57vtjmvbveuqa4,task_subcomment,NA
+"VisualEditor: Provide a way (beyond Ctrl-Click, middle-click, or right-click/tab) to open links in another window","I couldn't find a way to click the links while editing and go to the target page. It's not easily available in the source editor, so it's not really a regression, but I find myself needing this features every time I edit, because the links are blue and look like links.
+
+GMail and Google have reasonably good ways of going to links' targets in editing mode, so hints can be taken from them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50321",1380443280,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ge3lxw5vifprlb3diogc,task_description,resolved
+"VisualEditor: Provide a way (beyond Ctrl-Click, middle-click, or right-click/tab) to open links in another window",Fixed in gerrit 139550.,1405375886,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ge3lxw5vifprlb3diogc,task_subcomment,NA
+"VisualEditor: Provide a way (beyond Ctrl-Click, middle-click, or right-click/tab) to open links in another window","Right-click and 'open in new tab' works for me (tested in Firefox 24), but it'd be better to have something findable in the edit toolbar (or at *least* the link edit dialog) with a 'regular' click.
+
+Right-click or long-press for context menus aren't something everybody knows well or jumps straight to.",1380484636,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-ge3lxw5vifprlb3diogc,task_subcomment,NA
+VisualEditor: Show user that drag-and-drop of textual content is not supported,"+++ This bug was initially created as a clone of Bug #50643 comment 6 +++
+
+Steps to reproduce:
+1. Edit a page in VE
+2. Select a piece of textual content without any fancy stuff in it.
+3. Drag it to another location in the page
+
+Expected results:
+The cursor should be a disabled-drop icon
+
+Actual results:
+The cursor is an 'image' icon
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1380437160,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-g2els4untqmatfgmtodr,task_description,declined
+VisualEditor: Show user that drag-and-drop of textual content is not supported,"Given we are about to support text drag and drop with bug 49981, marking as wontfix.",1403008828,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g2els4untqmatfgmtodr,task_subcomment,NA
+VisualEditor: Show user that drag-and-drop of textual content is not supported,"What the?  Drag and drop text appears to be not working in Chrome either; I am pretty sure I remember dragging and dropping text in Chrome in July, but maybe I am mistaken.",1380601042,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-g2els4untqmatfgmtodr,task_subcomment,NA
+VisualEditor: Dropdown clipping is a bit too aggressive,"Dropdown clipping
+
+Referring to the attached screenshots there are two issues:
+
+1. The width is not adjusted to account for the OS scrollbacks. I assume this is because has one of those fancy Macintosh computers that doesn't know how to draw a big chunky old-fashioned scroll bar.
+
+2. The assumption is made the the height of the VE container is the maximum height the scrollbar expand to. Here that is clearly not the case. It may be the case that because we don't know what lies beyond the borders of VE (e.g. z-index 9999 banner), we can't do anything about this. Maybe we can make the assumption the page content is sane, and if the dropdown ends up obscured, leave that as an integration problem for the user?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69707
+
+**Attached**: {F12176}",1380295440,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5udersenidwseo6m5grs,task_description,resolved
+VisualEditor: Dropdown clipping is a bit too aggressive,Fixed in OOjs UI with gerrit 157295.,1415881674,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5udersenidwseo6m5grs,task_subcomment,NA
+VisualEditor: Dropdown clipping is a bit too aggressive,"Corrections:
+scrollbacks -> scroll bars
+is because has -> is because Trevor has",1380301150,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5udersenidwseo6m5grs,task_subcomment,NA
+VisualEditor: Switching from categories to languages while suggestion popup is open doesn't close popup,"Screenshot of languages dialog tab with the new-category popup in front
+
+Switching from categories to languages while suggestion popup is open doesn't close popup -- see screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12105}",1380219960,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-4y6au3cwi5b6pobrhrz5,task_description,resolved
+VisualEditor: Switching from categories to languages while suggestion popup is open doesn't close popup,This was fixed a while ago.,1398184329,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4y6au3cwi5b6pobrhrz5,task_subcomment,NA
+VisualEditor: Category editing tool should preview or at least link to the input categories,"Screenshot of category dialog, showing no apparent way to get at the listed categories
+
+The category suggestion tool seems to provide a simple typeahead search, but provides no way to go and see if the categories you've found are relevant.
+
+At a minimum, you should be able to open up the category page via a link from the search box and and the little tag display.
+
+Better still might be a little preview that pulls the description text (if any) and some sample contents right within the dialog box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12103}",1380219780,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-w3ca2knqurlwdolz6rth,task_description,open
+VisualEditor: Category editing tool should preview or at least link to the input categories,Seems like a nice idea. Provide a link in the category menu?,1415881475,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w3ca2knqurlwdolz6rth,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"This is kind of a meta bug and not an actual issue in BZ. Couldn't think of a better place to file it...
+
+Filing bugs/enhancements is difficult for some people to figure out. We can lower the barrier pretty easily by making a 1 or 2 minute video showing you how. Upload to commons, link to from BZ main page.
+
+Key components:
+- Sign up
+- Choosing the right product
+- Giving clear description of the problem/request
+-- Screenshots are fantastic
+-- Providing links is great too
+- Make sure to emphasize to not worry about filling all the fields out properly, the important step is opening the bug!
+
+Major props to User:Biosthmors on enwiki for coming up with the idea.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**Whiteboard**: gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks
+**URL**: https://commons.wikimedia.org/wiki/File:How_to_file_a_report_in_Bugzilla.webm
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52696",1380129240,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_description,resolved
+Make tutorial video on how to use Bugzilla,Excellent work Shujat! Thank you very much :-),1389707273,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Shujat completed the tutorial, which is available at https://commons.wikimedia.org/wiki/File:How_to_file_a_report_in_Bugzilla.webm
+
+Your help featuring it in mediawiki.org and other projects is welcome!
+
+Thank you very much, Shujat.",1389653591,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,*** Bug 58965 has been marked as a duplicate of this bug. ***,1389276275,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"
+
+(In reply to comment #33)
+> That's totally fine. Is the address bar (where the URL is shown) still
+> visible?
+> I'd say that's preferable to have.
+> 
+Well, I got that fixed by now, so its not a problem anymore, only the address bar is visible.
+But the g-mail will would be appearing, can't fix that.",1387984472,PHID-USER-oyf7m4w6q3dcftbg22jg,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #30)
+> Hello, I'm a student from GCI, and I've been assigned this task.
+> So, about the screencast, I have an idea: how about once the user account has
+> been created successfully, I go to http://www.mediawiki.org/wiki/MediaWiki,
+> then search for How to report a bug. From there I move to the new guided
+> form.
+
+OK
+
+(In reply to comment #32)
+> The script tells to go to your e-mail client, and I went to my gmail account
+> to get the mail, is that okay?
+
+Let's see how it looks like. The idea about not showing browser/email/OS chrome is to make the video as generic and as brand-free as possible. Don't worry, we can always cut.",1387811170,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #31)
+> Well, in the video, the windows taskbar or chrome logo is not there but tabs
+> are visible, that okay?
+
+That's totally fine. Is the address bar (where the URL is shown) still visible? I'd say that's preferable to have.
+
+(In reply to comment #32)
+> The script tells to go to your e-mail client, and I went to my gmail account
+> to get the mail, is that okay?
+
+Yes, but if you prefer to not show your real private email address and inbox at that time to the world, you might want to create another email account just for testing and making this video.",1387809225,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"The script tells to go to your e-mail client, and I went to my gmail account to get the mail, is that okay?",1387789082,PHID-USER-oyf7m4w6q3dcftbg22jg,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Well, in the video, the windows taskbar or chrome logo is not there but tabs are visible, that okay?",1387787959,PHID-USER-oyf7m4w6q3dcftbg22jg,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Hello, I'm a student from GCI, and I've been assigned this task.
+So, about the screencast, I have an idea: how about once the user account has been created successfully, I go to http://www.mediawiki.org/wiki/MediaWiki, then search for How to report a bug. From there I move to the new guided form.",1387787509,PHID-USER-oyf7m4w6q3dcftbg22jg,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Thank you Richard!
+
+The task about writing a script has been completed. I just created the task to produce the screencast:
+
+http://www.google-melange.com/gci/task/view/google/gci2013/5787018130882560",1385741411,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+Ok, i think its just about there, Did i seem to mention anything
+Link for convenience: https://www.mediawiki.org/wiki/User:Richardusername/BugzillaScriptProject",1385677331,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"I have given Richard my last round of comments. The script already looks very good. If you have additional feedback don't comment: edit the script directly (""Be bold"").
+
+As soon as this task is completed I will create a new one about creating the screencast.",1385604293,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Ok Richard, you don't need to get stuck in this discussion about the origin of the link. Whenever someone (you?) creates the screencast we will use an existing entry point in a wiki page (VisualEditor would work, as specified in your script).",1385504263,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #18)
+> I'm not sure how to transition from logging in to using the new formatted bug
+> submission form, as there seems to be no link from the site homepage.
+
+Uhm. I don't have an easy answer to that either right now. :(
+
+So far I've expected users to follow links on wikipages which point to the ?format=guided form in the URL. 
+But as Elitre already wrote: Discussed in bug 57254.",1385463812,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"It's a good first draft, but still needs more work. I have left my feedback. Andre and other readers of this report are encouraged to comment there as well.",1385445031,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+The draft is finished if you're interested. Just going to clean it up and maybe add more details. Link again for CC:https://www.mediawiki.org/wiki/User:Richardusername/BugzillaScriptProject",1385427743,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+Thanks for the video! It was exactly what I was thinking of, except doing this one more to the point. Also this is my main account, was accidentally logged in to wrong one when posting the last one. (I was going through the steps again)  As for the brief sign-up , we can easily remove it if needed, so ill just leave it until final revisions.",1385426393,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Hi Richiell!
+
+Slides vs screencast, this video was well received here. Just in case it serves as source of inspiration: 
+
+> http://blog.johnath.com/2010/02/04/bugzilla-for-humans/
+
+There is another GCI task about title cards for videos, but they are not ready yet. Still, this task is about agreeing on the script, so never mind.
+
+Same for the link to the guided form. You are right, currently there is no way to reach it from Bugzilla itself. However, for your script we can assume that it will be in the home.
+
+About your script, feel free of reusing the very little I could do at https://www.mediawiki.org/wiki/Talk:How_to_report_a_bug#Screencast
+
+I also started thinking of the registration process. Then again, Bugzilla's registration is quite standard, so perhaps it is better to save that time to the viewers of the video and yourself. Mention in the script that users must be registered in order to file bugs, feel free spending 3 seconds to point to the Register link in the home and get directly to the stuff.
+
+This means that the beef of your script is ""Examples"".  :) 
+
+Sorry for not reaching to this conclusion before! Your draft helped reaching to this conclusion. This is how iterations work...",1385425713,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**richiell** wrote:
+
+Ive made a little bit of progress on the script, here's the link if anyone wants to follow it: https://www.mediawiki.org/wiki/User:Richardusername/BugzillaScriptProject",1385421755,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Hear, hear! Bug 57254.",1385418631,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+I'm not sure how to transition from logging in to using the new formatted bug submission form, as there seems to be no link from the site homepage.",1385418288,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,":) I wouldn't like to see slides in the video, but hey, that's just me. Let's see what Andre thinks, since he rules over Bugzilla here!",1385417958,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+(In reply to comment #15)
+*or girls",1385416581,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+OK, Im thinking about doing the script with part Slideshow and mostly a Guided screen recording. What do you guys think about that?",1385416522,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,Awww! Thanks a lot!,1385400061,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+I am a student from Google Code in this task was assighned to, and I will start today, begining in a couple of hours. (Regular updates were required)",1385399968,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #11)
+> You should post that guided form to wikitech-l
+
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-October/072786.html",1383585826,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #10)
+> https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditor&format=guided
+
+That is REALLY nice!!  You should post that guided form to wikitech-l, I am sure other components could make use of a similar form.",1383574738,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"The guided form is now ready (i.e. https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditor&format=guided ), and I'd really love to have a screencast about it!",1383570076,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Note that there are also bugzilla.mozilla.org thoughts on having video tutorials for specific Bugzilla topics: https://bmo.etherpad.mozilla.org/bugzilla-tips-videos
+I don't know how much upstream this would be though.",1381787304,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Currently I'd use the normal form with ""Hide Advanced Fields"" enabled, and either MediaWiki or Wikimedia product, plus component ""General/Unknown"".",1381763815,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,Guided form (bug 36762) is still under development and not deployed - this week was too busy with reallife but will try to get it into shape next week.,1381503809,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Well, yes, a video screencast.
+
+What I'm asking is whether we should do it using the plain Bugzilla interface or the guided form.",1381468109,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #4)
+> What interface should we use for this screencast? The traditional or this new
+> one Andre is cooking up?
+
+I'd assumed you'd create a video in .ogv format.
+
+A paginated PDF is also an option.",1381459718,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"What interface should we use for this screencast? The traditional or this new one Andre is cooking up?
+
+I have started defining a rough script at https://www.mediawiki.org/wiki/Talk:How_to_report_a_bug#Screencast",1381444276,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"For the records (and inspiration), the only pretty good (and partially Mozilla-centric) video I am aware of is http://blog.johnath.com/2010/02/04/bugzilla-for-humans/",1380150692,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"A screencast showing the shortest path to file a bug report should do. I haven't done a screencast in ages but I will try tomorrow, with the hope that someone hates what I did and produces something better.  :)
+
+In fact this could be start of something. We could have more short screencasts focusing on a specific action (advanced search, comment on a bug...) and extend the idea to other tools (get developer access, comment on Gerrit...). These short videos could be easily embedded in the right wiki pages and...
+
+But let me try with this File Your First Bug screencast first.  :)",1380145913,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Maybe Victor / some designers / whoever, can produce nice video intro and outro :)",1380143726,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Improve handling of stray table tags / Verify that we handle stray table tags correctly,"Occasionally, pages have stray opening table tags which may end up screwing up DSR computations (which in turns messes up selser). It is possible that our latest foster parenting code implicitly handles this by wrapping the entire table as templated and protected a large body of code (which could then serve as a flag to the user to look for bugs in the wikitext souce). So, it might be worth verifying this and adding tests to spec this behavior.
+
+See the bug report: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=574391235#Duplicated_content_when_deleting_apparently_blank_lines
+
+See my response that fixed the problem in the wikitext source: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=574483272#References_and_tables
+
+If this is not already handled by our handleUnbalancedTables and markFosteredContent DOM passes, we may need to tackle this -- by maybe adding a fixup in TokenStreamPatcher that enforces limited table scope (section boundaries is the obvious scope limiter => close unclosed tables whenever section heading tokens are encountered).
+
+To be investigated and fixed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380128640,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-s52vfnr5655l5mcn3ccw,task_description,resolved
+Improve handling of stray table tags / Verify that we handle stray table tags correctly,"We have made a bunch of fixes over the years. Since then, we also have wikitext linting that flags brokenness (fostering, missing end tags) which cover some of these cases. I don't think we should clutter the Parsoid code base trying to make sense of obviously broken markup. So, I am going to close this as resolved.",1592505284,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-s52vfnr5655l5mcn3ccw,task_subcomment,NA
+Improve handling of stray table tags / Verify that we handle stray table tags correctly,"(In reply to comment #0)
+> Occasionally, pages have stray opening table tags which may end up screwing
+> up
+> DSR computations (which in turns messes up selser). It is possible that our
+> latest foster parenting code implicitly handles this by wrapping the entire
+> table as templated and protected a large body of code (which could then serve
+> as a flag to the user to look for bugs in the wikitext souce). So, it might
+> be
+> worth verifying this and adding tests to spec this behavior.
+
+That seems to happen if a template is present, as in:
+
+  {|
+
+  {{echo|hi}}
+
+  ;Ho
+
+However, that's not the case in the bug report. It's more like,
+
+  {|
+
+  ;Off to work we go
+
+
+> 
+> See the bug report:
+> https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Feedback&oldid=574391235#Duplicated_content_when_deleting_apparently_blank_li
+> nes
+> 
+> See my response that fixed the problem in the wikitext source:
+> https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Feedback&oldid=574483272#References_and_tables
+> 
+> If this is not already handled by our handleUnbalancedTables and
+> markFosteredContent DOM passes, we may need to tackle this -- by maybe
+> adding a
+> fixup in TokenStreamPatcher that enforces limited table scope (section
+> boundaries is the obvious scope limiter => close unclosed tables whenever
+> section heading tokens are encountered).
+
+Seems reasonable.
+
+> 
+> To be investigated and fixed.",1380840132,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-s52vfnr5655l5mcn3ccw,task_subcomment,NA
+Large number of CSS rules for external links,"Assigning to Parser as I suspect this is what would need to be fixed up to support this.
+
+This patch [1] demonstrates the large number of rules exist for external links:
+
+The browser matches styles from right to left, so the rightmost selector is really important.
+
+We shouldn't need to have to resort to CSS rules in the form div#content a.external[href ^=""https://""] - a link with class external should also have a class describing what type of external link it is if it is necessary. These selectors are less efficient and are not supported by older browsers.
+
+Ideally we should simply these rules to become something like:
+
+.link-audio,
+.link-video,
+.link-document,
+.link-irc,
+.link-ftp,
+.link-https,
+.link-news,
+.link-mailto {
+padding-right: 13px;
+background: transparent center right no-repeat;
+}
+
+with rules for each of them for their correct icon.
+
+[1] https://gerrit.wikimedia.org/r/#/c/85920/2/skins/vector/externalLinks.less
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63725
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63521",1380128040,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_description,resolved
+Large number of CSS rules for external links,"Sigh.
+I'm frustrated by the removal of icons that were useful.",1418760677,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,Meh.,1418744473,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"PDF: To clarify this, the icon was always a generic document. On the English Wikipedia it uses an Adobe icon through Common.css.
+
+The Typography Refresh removed the other icons in Vector. HTTPS icons were removed per Bug 61178.
+
+So currently on the English Wikipedia we have the external link icon and the Adobe icon. Both are meaningless to our visually impaired readers since none of the icons have alt text; see Bug 45891.
+
+Since many documents are now produced by dynamic web pages, they do not have the file extension that the CSS rules trigger on, thus those documents will show the simple external link icon.
+
+Bottom line: How useful are the icons? Is there any other project using icons in this manner?",1413544350,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"1) As I said in comment #6 - the mailto, irc, audio/video, and pdf icons are frequently useful for:
+* Readers to have ""principle of least astonishment"" when clicking on links which often have a non-typical-navigation result.
+* Editors to see that an unusual link has been used/added, which might warrant further investigation.
+
+2) Our internal Pronunciation links all have an icon added automatically: e.g. https://en.wikipedia.org/wiki/Template:Pronunciation and https://en.wikipedia.org/wiki/Template:IPA - e.g. at [[Götterdämmerung]]
+
+Then, 2 similar ""bits of information - a difference that makes a difference"" that any of our users might appreciate.
+
+3) we have a request from the Internet Archive to add icons to their links: #1 at https://www.mediawiki.org/wiki/Archived_Pages#Implementation_ideas (mentioned at https://lists.wikimedia.org/pipermail/design/2013-October/001065.html )
+
+4) we have a request from the community, (and I believe connected to The Wikipedia Library), to add icons that denote Open-Access resources: https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Open_Access/Signalling_OA-ness
+
+For all of these reasons, I hope we can re-instate these icons in Vector. 
+The patch to do so is currently -2'd based on lack of apparent consensus (https://gerrit.wikimedia.org/r/#/c/154350/). 
+I've also left a comment (the first...) at [[Help talk:External link icons]]. 
+Comments here or there, with additional rationales for supporting or opposing the re-instatement (for use-case or technical or other reasons) would be appreciated.",1413530059,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Bartosz Dziewoński from comment #81)
+> So the general agreement is that it was good in the beginning and the change
+> above was a bad idea.
+
+I don't know how you have determined this from the above. Please give me the precise quotes you are attributing to.
+
+All I see is agreement that we shouldn't use classes and should use an approach such as [href^=""https://""]
+
+Whether they are a good idea is another question.
+I wouldn't want them on my local wiki for example.",1409175468,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 154350 had a related patch set uploaded by Bartosz Dziewoński:
+Restore external links icons
+
+https://gerrit.wikimedia.org/r/154350",1408142652,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"So the general agreement is that it was good in the beginning and the change above was a bad idea. In other words, we should revert https://gerrit.wikimedia.org/r/#/c/123817/ in the Vector skin.
+
+(Also, moving this to the Vector component, since the only changes that were implemented and the entire discussion involved only that skin.)",1408140797,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 141973 abandoned by Bartosz Dziewoński:
+Linker: Add CSS classes to external links to some protocols/filetypes
+
+Reason:
+Right.
+
+https://gerrit.wikimedia.org/r/141973",1408140617,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #77)
+> Isarra. What was the motivation for putting them in in the first place?
+
+Given that this was orginally added in 2004, I couldn't say. I can, however, point you to comment #3 and comment #6, which detail specific reasons for keeping them in now.
+
+> Putting styles in both core and common.css that do the same thing is a
+> terrible terrible terrible thing and we should at least resolve that problem
+> at the same time. The fact those rules exist there show MediaWiki was not
+> serving there purpose and they were /not/ useful.
+
+As I said, the English Wikipedia is not the only project that uses this software. What they do doesn't necessarily apply to other projects, especially when we don't even know why they did what they did.
+
+> Currently each project as complete free reign to add these icons in
+> common.css if they want to. I truly don't see the value in them being here.
+
+Each project is free to write their entire skin css in common.css if they want to. Doesn't mean they should have to do that either.",1404409477,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #77)
+> PS. How can I remove myself from this bug. Since I'm the creator, it doesn't
+> seem possible.
+
+Sorry, only available in next version: https://bugzilla.mozilla.org/show_bug.cgi?id=148564 - For the time being, custom filters / thread muting.",1404409227,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Isarra. What was the motivation for putting them in in the first place?
+
+Putting styles in both core and common.css that do the same thing is a terrible terrible terrible thing and we should at least resolve that problem at the same time. The fact those rules exist there show MediaWiki was not serving there purpose and they were /not/ useful.
+
+Currently each project as complete free reign to add these icons in common.css if they want to. I truly don't see the value in them being here.
+
+Isarra making use of icons is not the same as those icons giving value.
+
+PS. How can I remove myself from this bug. Since I'm the creator, it doesn't seem possible. @Andre.. ?",1404407556,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #75)
+> The icons for audio, video etc have been gone for some time without any
+> complaints that I am aware of. Maybe because a lot of these styles are
+> implemented in MediaWiki:Common.css
+
+Yes, nobody noticing would make it more difficult for anyone to complain about it.
+
+> Let's not re-instate these classes and CSS rules. The status quo is
+> currently fine. Let's not add back css rules for the sake of adding back css
+> rules. I feel like we are wasting far too much energy on this bug.
+
+MediaWiki serves more than just the English Wikipedia. While the icons often do serve little purpose on individual projects, many other projects do indeed make use of these icons, especially third-party technical projects which will not have seen that change at all due to generally being on stable releases (1.19, 1.22, 1.23 etc). This is not adding back css rules for the sake of adding them back, this is adding them back with a reasoned technical discussion about how best to do so considering the current technology, with the understanding that projects do use them, that there are real-life use cases speaking to their usefulness, and that there was no consensus to remove them in the first place.",1404403168,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"The icons for audio, video etc have been gone for some time without any complaints that I am aware of. Maybe because a lot of these styles are implemented in MediaWiki:Common.css
+
+Let's not re-instate these classes and CSS rules. The status quo is currently fine. Let's not add back css rules for the sake of adding back css rules. I feel like we are wasting far too much energy on this bug.",1404401835,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Phew .. long discussion. I could have gone either way (selectors or css classes) till I hit Gabriel and Roan's comments and now Krinkle's about client burden and code duplication to support classes/attributes. If there were no alternatives and this were the spec, of course, all clients would have to implement it, but given that there are no serious drawbacks to picking selectors over classes, I too think that it is a better idea to use css for icon-styling of links.",1404399874,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Bartosz Dziewoński from comment #54)
+> (In reply to Gabriel Wicke from comment #52)
+> > Do we have actual measurements that verify that this benefits total page
+> > view performance in practice?
+> 
+> We don't. Jon provided some funky tool in comment 11 but I've been unable to
+> get it to work. Krinkle provided a theoretical explanation on why this
+> should make a difference in comment 10.
+
+The performance impact is quite negligible actually. I'd rather let browsers worry about that. This shouldn't be a main driving factor in this case because it is too insignificant. My main point there was maintenance overhead:
+
+(Citing comment #10 from Krinkle)
+> * Hardcodes details that (other) stylesheets should not have to know or hardcode, thus causing maintenance issues (e.g. the fact that it is an <a>, and is inside #bodyContent. The container can change, and links might be wrapped for presentational reasons)
+
+This would be mitigated by using a selector like:
+
+.mw-body-content a[href^=""https://""] {}
+
+This doesn't have the added weight of an ID selector (#bodyContent) and is quite minimal and straight forward.
+ 
+
+(In reply to Gabriel Wicke from comment #62)
+> (In reply to Daniel Friesen from comment #61)
+> > What if we ""don't"" want an icon?
+> 
+> The .plainlinks class was normally used to mark this up, and applied to all
+> links inside a content block. How does this work with classes on each link?
+
+That is indeed an important one to remember. Let's make sure we're compatible with that.
+
+(In reply to Gabriel Wicke from comment #69)
+> One issue I didn't mention yet is editor complexity. Every editor for our
+> HTML including VE will need to replicate the class logic from the parser.
+> This includes future micro-contribution tools like 'fix this link'. It seems
+> likely that this will lead to rendering inconsistencies when the logic
+> replication is not perfect.
+
+I agree. Adding all these classes to the Parser will inflate Parser output with information that can trivially be derived from the href attribute, doesn't really provide value to customers of the HTML (other than saving a few characters in stylesheet), and adds more or less random complexity to other producers of HTML such as VisualEditor content editable preview nodes and Parsoid. All the information about the url is right in the href. I think keeping classes like these out of page HTML would be optimal for maintenance overall:
+
+* Avoid imposing requirements on VE and Parsoid to add arbitrary attributes that the applied stylesheets should maintain instead. Separating responsibility and concerns; Unless it's a huge performance penalty we really shouldn't consider adding hooks like these inside the Parser for the skins' convenience.
+
+* Avoid optimising arbitrarily for the needs of one skin (the classes we add would only be for certain protocols and include certain file extensions in the media types. If another consumer doesn't agree with our grouping or wants more, they'd be back to square one in using href-matching; ergo, the approach doesn't scale and signifies that it'd wrongly divide responsibility between parser and stylesheet.
+
+
+I'd recommend going with something like:
+
+.mw-body-content .external[href^=""https://""] {}",1404397752,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Re performance, I have not been able to find anything on the web that indicates that CSS selector performance is a significant issue in practice.
+
+This SO articles seems to provide a good overview:
+http://stackoverflow.com/questions/12279544/which-css-selectors-or-rules-can-significantly-affect-front-end-layout-renderi",1404340285,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,+1 to Roan and Gabriel.,1404337326,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #69)
+> One issue I didn't mention yet is editor complexity. Every editor for our
+> HTML including VE will need to replicate the class logic from the parser.
+> This includes future micro-contribution tools like 'fix this link'. It seems
+> likely that this will lead to rendering inconsistencies when the logic
+> replication is not perfect.
+
+This is also a problem for VisualEditor. Even in the current system, not including any micro-contribution tools that Gabriel talks about, we would need three entirely separate copies of this logic, in:
+* MediaWiki's wikitext->HTML parser
+* Parsoid, to generate correct HTML
+* VisualEditor, to display newly created links correctly
+
+VE generally deals well with styling that comes from the parser side and displays it correctly, but in this case the user could create a link entirely from scratch, and that link might be a .pdf link. Then even though there may not be another .pdf link anywhere on the page, we still need to know that .pdf is magical and should trigger a certain CSS class in order to produce the correct rendering. That's why we need a full duplicate of the icon logic.
+
+So in general, we try to move this kind of logic fully *into* CSS, rather than *out of* CSS and into *code*. Last year this was done for auto-numbered external link numbering: instead of implementing a bunch of numbering logic both in Parsoid and in VE, we were able to number them entirely in CSS using CSS3 counters.
+
+With that in mind, I would much prefer that link icons be done in pure CSS, with attribute selectors in their full ""glory"". That way VisualEditor and any other clients that need to generate new HTML will not have to reimplement the logic from scratch, and instead will just be able to load the CSS. Unless attribute selectors are horrendously slow (which they're probably not, the original CSS rules for link icons date back to 2004), moving to classes just makes things worse, not better.",1404267558,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,One issue I didn't mention yet is editor complexity. Every editor for our HTML including VE will need to replicate the class logic from the parser. This includes future micro-contribution tools like 'fix this link'. It seems likely that this will lead to rendering inconsistencies when the logic replication is not perfect.,1404264536,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Oh, MediaWiki uses more advanced things for styling (like… LESS?), that was never the problem. The only problem was unspecified performance issues.
+
+But I really don't feel like introducing two new ways of doing such a little feature is the right thing to do from a maintainability standpoint (both the maintainability of core, and maintainability of any skins that might want to use different icons).",1404260905,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Bartosz Dziewoński from comment #66)
+> As I said before, I'm okay with doing this either way (we can revert the old
+> patch that removed this feature in Vector), but let's please not do both
+> ways at once.
+
+We are using attribute matches for a bunch of things in any case, so it's not like somebody working on MediaWiki CSS would now be exposed to new CSS 2 selectors. The main change would be the introduction of classes to eliminate overly complex attribute matches on file extensions, which I think is fairly easy to understand.",1404145601,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #64)
+> Looking at the linked CSS [1], to me it seems that the most complex rules
+> are those matching on file extensions to figure out video / audio / document
+> links. As those links are not that common relative to the total number of
+> links I'd expect classes to be a win overall for those.
+> 
+> Protocol matches on the other hand are a single selector only (no need for
+> upper case variants), and a large chunk of external links is neither to
+> videos, audio or document files. This seems to favor keeping those matches
+> in CSS to keep the document size down.
+> 
+> Does this sound like a promising solution to you?
+
+Eh, I'd prefer if we decided on only one way of doing this and stuck to it. This seems to be the worst of both worlds.
+
+As I said before, I'm okay with doing this either way (we can revert the old patch that removed this feature in Vector), but let's please not do both ways at once.",1404067893,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #62)
+> The .plainlinks class was normally used to mark this up, and applied to all
+> links inside a content block. How does this work with classes on each link?
+
+.plainlinks .link-https has higher specificity than .link-https, so it's easy to disable the icon for plain links, if desired.
+
+(In reply to Gabriel Wicke from comment #64)
+> Looking at the linked CSS [1], to me it seems that the most complex rules
+> are those matching on file extensions to figure out video / audio / document
+> links. As those links are not that common relative to the total number of
+> links I'd expect classes to be a win overall for those.
+> 
+> Protocol matches on the other hand are a single selector only (no need for
+> upper case variants), and a large chunk of external links is neither to
+> videos, audio or document files. This seems to favor keeping those matches
+> in CSS to keep the document size down.
+
+I don't really know the performance details, but that seems reasonable.  PDF links are probably more common than audio/video, but still a minority.",1403925613,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Looking at the linked CSS [1], to me it seems that the most complex rules are those matching on file extensions to figure out video / audio / document links. As those links are not that common relative to the total number of links I'd expect classes to be a win overall for those.
+
+Protocol matches on the other hand are a single selector only (no need for upper case variants), and a large chunk of external links is neither to videos, audio or document files. This seems to favor keeping those matches in CSS to keep the document size down.
+
+Does this sound like a promising solution to you?
+
+[1]: https://gerrit.wikimedia.org/r/#/c/85920/2/skins/vector/externalLinks.less",1403807205,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #62)
+> > I'd like to see us moving away from descendant selectors and explore OOCSS
+> > [1] as a solution to our CSS mess we have created. We really should be
+> > making better uses of classes, and not be restricted by the implementation
+> > restrictions of Parsoid.
+> 
+> I don't have a strong opinion on what's done in skins. My interest is
+> restricted to the content area. In general, we are currently moving away
+> from any skin- and pref- specific HTML (including classes) in the page
+> content. Our goal is to speed up page views for editors to the level of
+> current anonymous views. This means that any variation in rendering between
+> skins should be implemented in CSS only, and should not rely on different
+> classes being set depending on skin or user preferences.
+
+The suggested link classes are universal, they are not skin or user specific they are always in the dom dependent on what is in the dom.
+
+> (In reply to Daniel Friesen from comment #61)
+> > What if we ""don't"" want an icon?
+> 
+> The .plainlinks class was normally used to mark this up, and applied to all
+> links inside a content block. How does this work with classes on each link?
+
+.plainlinks will continue to work for content, in fact it'll work even better since classes have less specificity than attribute selectors.
+But I'm not talking about content, but rather code. Adding links to elements or parts of the skin that happen to be under the root the link styles are defined on. With classes all an extension has to do is not use a link class. It can also add that link class to links that wouldn't normally match the selector (an extension could decide to link to a PDF reader with a document link style even though the url wouldn't have matched a .pdf$ selector.
+And to top that off by using classes instead of attribute selectors we can drop the root (#content / #bodyContent / .mw-body) since interface links won't be ruined by them anymore, and code can opt-in to link styles outside of content.
+
+> (In reply to Daniel Friesen from comment #60)
+> > Are the byte sizes of a few link classes really a big deal for actions as
+> > infrequent as a save?
+> 
+> Page size is a big deal for uncompressed uploads, as upload speeds are
+> normally much slower than download speeds. Uploading a large article like
+> [[San Francisco]] from a DSL connection in San Francisco takes many seconds
+> (23 with current inline Parsoid metadata, around 7 without it), so a change
+> of 5% in the page size does have a measurable impact on save times, even on
+> a relatively fast connection. Things are worse than that when you are on a
+> bad connection in India.
+
+Which brings me to my other point:
+""Also I thought delta based saves were being done which make small byte size differences moot.""
+
+So in theory changing %5 of [[San Francisco]] should not involve uploading all of San Francisco. Unless VE is implemented really inefficiently, tiny additions like link classes shouldn't have as much effect on small edits. And if it is implemented that inefficiently, we have a larger problem than the bytes add to link classes.
+
+> > If they are, isn't there any serverside sanitization of the DOM? These are
+> > internally generated classes, so if it were an issue couldn't you just strip
+> > them before transmission and let the sanitizer or parsoid generate the
+> > classes?
+> 
+> We are working towards using Parsoid HTML for both views and editing, so
+> that you don't even loading a new page when switching to VE.
+
+Not relevant, my suggestion is that if you want size reduction on upload, then you could strip the link classes right before upload (which are automatically generated based on a set of rules) since and the server-side sanitizer (which should exist anyways to prevent the rules of the parser being intentionally screwed with or broken by an old VE version) would add them back. The parsoid output and view content (which are compressed and delivered by the faster download bandwidth) would still have the classes.",1403749130,PHID-USER-gibrlx54k2riiuit5paf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #59)
+> Another reason is styles written in this way are not reusable.
+> 
+> What if we want to use the same audio icon elsewhere?
+> 
+> With an icon-audio selector class we can.
+> With a selector based on href we can't.
+
+This seems to overstate the case a bit. There's nothing stopping us from adding a selector in the CSS, and I don't see why that's more complex than adding the class in HTML. 
+
+> I'd like to see us moving away from descendant selectors and explore OOCSS
+> [1] as a solution to our CSS mess we have created. We really should be
+> making better uses of classes, and not be restricted by the implementation
+> restrictions of Parsoid.
+
+I don't have a strong opinion on what's done in skins. My interest is restricted to the content area. In general, we are currently moving away from any skin- and pref- specific HTML (including classes) in the page content. Our goal is to speed up page views for editors to the level of current anonymous views. This means that any variation in rendering between skins should be implemented in CSS only, and should not rely on different classes being set depending on skin or user preferences.
+
+All these decision are engineering trade-offs, not implementation restrictions. If there are good engineering reasons (performance and CSS sanity for example) for generally adding more classes in the DOM & dumbing down the CSS selectors, then I'd be all for it.
+
+So far our strongest performance data seems to be page sizes, as that's easy to measure. Quantitative data on the relative importance of selector performance on total page render time is missing so far. My anecdotal evidence is that it wasn't noticeable when I added external link icons in 2004, on a laptop that would be considered a feature phone these days.
+
+(In reply to Daniel Friesen from comment #61)
+> What if we ""don't"" want an icon?
+
+The .plainlinks class was normally used to mark this up, and applied to all links inside a content block. How does this work with classes on each link?
+
+(In reply to Daniel Friesen from comment #60)
+> Are the byte sizes of a few link classes really a big deal for actions as
+> infrequent as a save?
+
+Page size is a big deal for uncompressed uploads, as upload speeds are normally much slower than download speeds. Uploading a large article like [[San Francisco]] from a DSL connection in San Francisco takes many seconds (23 with current inline Parsoid metadata, around 7 without it), so a change of 5% in the page size does have a measurable impact on save times, even on a relatively fast connection. Things are worse than that when you are on a bad connection in India.
+
+> If they are, isn't there any serverside sanitization of the DOM? These are
+> internally generated classes, so if it were an issue couldn't you just strip
+> them before transmission and let the sanitizer or parsoid generate the
+> classes?
+
+We are working towards using Parsoid HTML for both views and editing, so that you don't even loading a new page when switching to VE.",1403744805,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #59)
+> Another reason is styles written in this way are not reusable.
+
+I'll add one more reason.
+
+What if we ""don't"" want an icon? This should be as simple as not including the class. Using selectors this means you have to override a skin specific css rule, with an unknown weight to it. The selectors aren't even standardized yet, Vector used to use #content, MonoBook uses #bodyContent, and commonElements of course uses .mw-body (though for non-icon styles).",1403741384,PHID-USER-gibrlx54k2riiuit5paf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to C. Scott Ananian from comment #57)
+> @Daniel: long story, but basically gzip compression in HTTP only works in
+> the download direction.  There is no equivalent content negotiation for
+> uploads in HTTP.
+
+Oh you're talking about save sizes.
+
+Are the byte sizes of a few link classes really a big deal for actions as infrequent as a save?
+
+If they are, isn't there any serverside sanitization of the DOM? These are internally generated classes, so if it were an issue couldn't you just strip them before transmission and let the sanitizer or parsoid generate the classes?
+
+Also I thought delta based saves were being done which make small byte size differences moot.",1403738770,PHID-USER-gibrlx54k2riiuit5paf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Another reason is styles written in this way are not reusable.
+
+What if we want to use the same audio icon elsewhere?
+
+With an icon-audio selector class we can.
+With a selector based on href we can't.
+
+I'd like to see us moving away from descendant selectors and explore OOCSS [1] as a solution to our CSS mess we have created. We really should be making better uses of classes, and not be restricted by the implementation restrictions of Parsoid.
+
+[1] http://www.smashingmagazine.com/2011/12/12/an-introduction-to-object-oriented-css-oocss/",1403738706,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to C. Scott Ananian from comment #57)
+> @Daniel: long story, but basically gzip compression in HTTP only works in
+> the download direction.  There is no equivalent content negotiation for
+> uploads in HTTP.
+
+JS implementations aren't universally a win on all browsers & hardware either. See https://bugzilla.wikimedia.org/show_bug.cgi?id=66914 for some related discussion.",1403737647,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"@Daniel: long story, but basically gzip compression in HTTP only works in the download direction.  There is no equivalent content negotiation for uploads in HTTP.",1403737425,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #52)
+> We have use cases where uncompressed HTML is sent over the wire (HTML save
+> from VE), so uncompressed DOM size does matter.
+
+Why is it not compressed?",1403737169,PHID-USER-gibrlx54k2riiuit5paf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Bartosz Dziewoński from comment #54)
+> (In reply to Gabriel Wicke from comment #52)
+> > Do we have actual measurements that verify that this benefits total page
+> > view performance in practice?
+> 
+> We don't. Jon provided some funky tool in comment 11 but I've been unable to
+> get it to work. 
+
+Same here, it wouldn't even load for me.
+
+> Krinkle provided a theoretical explanation on why this
+> should make a difference in comment 10.
+
+Both of these aren't really telling us whether it's an overall win, draw or loss to add extra classes in the DOM & use those rather than match on existing properties. They both focus on one part of the picture only, and lack quantitative data. Only measurements can really answer this question.
+
+> (In reply to Gabriel Wicke from comment #53)
+> > One more note on browser support: IIRC these selectors were already
+> > supported by IE 6 in 2004.
+> 
+> Not by IE 6, but by every other browser, yes. IE 7+ supports them too.
+
+Ah, okay. Misremembered that then ;)",1403736790,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #52)
+> Do we have actual measurements that verify that this benefits total page
+> view performance in practice?
+
+We don't. Jon provided some funky tool in comment 11 but I've been unable to get it to work. Krinkle provided a theoretical explanation on why this should make a difference in comment 10.
+
+
+> If there is no measurable improvement on page
+> view / rendering even on mobile, then I'd propose to keep this in CSS to
+> avoid slowing down use cases like VE saves.
+
+You are actually proposing restoring this to CSS :), because it's already been removed (in spite of working well since 2004). I wouldn't mind that, personally.
+
+
+(In reply to Gabriel Wicke from comment #53)
+> One more note on browser support: IIRC these selectors were already
+> supported by IE 6 in 2004.
+
+Not by IE 6, but by every other browser, yes. IE 7+ supports them too.",1403735921,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,One more note on browser support: IIRC these selectors were already supported by IE 6 in 2004.,1403734881,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"We have use cases where uncompressed HTML is sent over the wire (HTML save from VE), so uncompressed DOM size does matter.
+
+Do we have actual measurements that verify that this benefits total page view performance in practice? If there is no measurable improvement on page view / rendering even on mobile, then I'd propose to keep this in CSS to avoid slowing down use cases like VE saves.",1403734104,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to C. Scott Ananian from comment #50)
+> Hm, Parsoid does not tag links with classes.  The only CSS would work fine
+> for parsoid-generated HTML; the new CSS will not.
+
+That is a bug in parsoid. We've required the .external class at minimum for years, parsoid should be able to handle link classes.",1403733775,PHID-USER-gibrlx54k2riiuit5paf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Hm, Parsoid does not tag links with classes.  The only CSS would work fine for parsoid-generated HTML; the new CSS will not.",1403733257,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"We'll have https (secure) and external link icons in wiki font soon (probably already) but wiki font isn't in core yet, these issues are related but could be separate too.",1403727638,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 141973 had a related patch set uploaded by Bartosz Dziewoński:
+Linker: Add CSS classes to external links to some protocols/filetypes
+
+https://gerrit.wikimedia.org/r/141973",1403727424,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"I've looked at this again now that things have cooled down. I still do not like this solution, and I still like this alternative proposed a long time ago:
+
+(In reply to Bartosz Dziewoński from comment #13)
+> (In reply to Jon from comment #11)
+> > That aside use of a single class .link-https rather than a
+> > combination of class .link-https, div#content a.external[href
+> > ^=""https://""] would be preferable for a variety of reasons
+> > readability, maintainability, reduced file size... are you really
+> > telling me this is not a no-brainer?
+> 
+> Using the classes as you proposed does seem sane and mostly non-troublesome
+> (apart from the classic caching issues). I am perfectly fine with doing that
+> (as long as I'm not the one who will have to jerry-rig the Parser).
+
+So I looked at the Parser, or in fact the Linker, and doing this is actually amusingly trivial. Pity no one did this the first time around.
+
+A patch will follow momentarily.",1403727235,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Regardless of everyone's opinions the patch has been merged, so this is fixed.",1399940828,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 124618 merged by jenkins-bot:
+Follow-up: If985b16c – Vector external link change release notes
+
+https://gerrit.wikimedia.org/r/124618",1397145263,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 124618 had a related patch set uploaded by Jdlrobson:
+Follow up to If985b16c4f682d737683597ed80951c6d6644c8f
+
+https://gerrit.wikimedia.org/r/124618",1396972855,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"I can tell you that it's customary on sites like Reddit to add a ""PDF warning"" to a description of a link that points directly to a PDF document. (Other file types don't really come up often enough for such a custom to develop.)",1396952733,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #37)
+> As stated above external links were removed as part of the typography beta
+> feature. Actually, not a single person wrote about this on the talk page
+> (https://www.mediawiki.org/wiki/Talk:Typography_Update) during the 6 months
+> it was live. This evidence leads me to believe that they are /not/ important
+> and it is the basis for removing them.
+
+However, anyone who used a wiki (like English Wikipedia, which has such rules at https://en.wikipedia.org/wiki/MediaWiki:Common.css and https://en.wikipedia.org/wiki/MediaWiki:Vector.css) with local rules would not have seen any difference.
+
+Thus, it's a valid question how many people who used the Beta feature saw a visible change to the main (PDF and HTTPS seem like the biggies for article space, with the audio being used a decent amount, but not as much, but I don't have data) icons.  If a tiny number were affected, then ""not a single person wrote about this"" is not a convincing argument.
+
+I think English Wikipedia Beta users saw neither change, since PDF is at [[MediaWiki:Common.css]] and HTTPS is at [[MediaWiki:Vector.css]].
+
+However, it is certainly true that we are not going to be able to do dedicated research for every change, and this may be one such example.  I agree that this feature affects both readers and editors, and we need to consider the impact on both.  Having tools to do A/B tests on readers would certainly help, but it wouldn't solve everything.
+
+It can definitely be iterated on regardless.  In particular (if we proceed without the format-specific icons), there should be at least one follow-up change to do the following:
+
+1. Remove obsolete FIXME comment from externalLinks.css.
+2. Release notes
+3. Fixes from https://gerrit.wikimedia.org/r/#/c/123817/3/skins/vector/components/externalLinks.less .  Note the point about div#content on the left, and might as well do the formatting fix on the right (space before right paren) since there needs to be a commit anyway.
+
+Marking open again and assigning to Jon.",1396921020,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #37)
+> Commits and reverts are cheap.
+
+No. There's almost no evidence to suggest that commits and reverts of this nature are cheap. There's a ton of evidence to suggest that commits and reverts of this nature are expensive (in terms of community time and developer time).
+
+> We have a huge editor decline and here we are arguing about some icons next to
+> links.
+
+No fearmongering here, please. The stated editor decline is dubious, bordering on spurious. This bug is strictly about ""some icons next to links."" You (Jon) are sidetracking the technical conversation with FUD about an editor decline. Focus on the issue at hand, please.",1396920224,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jared Zimmerman (WMF) from comment #36)
+> (In reply to Isarra from comment #34)
+> We did a beta feature, it was called typography refresh, and little to no
+> feedback (negative or positive) addressed the removal of these icons, that
+> was the impetus for moving forward with this as a simple patch. 
+
+Lumping multiple changes together and then testing the entire pile is problematic by its very nature: it can become very difficult to differentiate between the effects of different changes, and getting meaningful feedback on any specific one often becomes very difficult. Thus you can wind up with an overall positive response despite individual aspects which significantly detract from the experience, and then wind up thinking those, too, are positive when they really aren't (or visa versa).
+
+Thus, to say anything specific about the external link icons and potential changes, I would suggest that you need to test or otherwise investigate those specifically, and distinctly, first. Jon's not wrong that this is a relatively minor thing, but while that means a full-on battery of tests probably isn't actually necessary here, like with any other change, discussion is definitely in order in order to establish some sort of consensus as to what best serves the users. So here we are. Discussing. Or we were, before the entire thing got a wee bit sidetracked.",1396918242,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #37)
+> The world is not breaking. The world of Vector is just going through
+> turbulence.
+
+I didn't mean to point fingers at any specific event, and wasn't actually thinking of typo refresh when making my comment (Or the actual subject of this bug. Oh well guess this bug is pretty hijacked). I wanted to address in the abstract the attitude in comment 23 of making changes willy nilly (which I flippantly phrased as ""breaking the world"") and then iterating on them until people like them (or cynically: until they become fait accompli), as being a good way to get feedback. I think its a good way to piss off people, and self-justify changes via confirmation bias.
+
+
+> 
+> The fact we have to actively discuss trivial changes like this concerns me
+> greatly. We have a huge editor decline and here we are arguing about some
+> icons next to links.
+
+I'm not sure I follow. Not asking editors for feedback on changes is somehow going to increase editor retention?
+
+> 
+> Also I think you mean /editors/ when you say /readers/ here. I think most
+> /readers/ care simply if a link will take them to an external site or not.
+
+I was responding as if ""readers"" = Users without an account who only read. For the actual change I think both groups care. My comment was aimed solely at attitudes for getting feedback. I'm not actually that concerned about the actual change",1396916621,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,I'm just going to leap in here in the middle of this heated discussion and change the title of the bug to be grammatically correct. It's been bugging me. Sorry.,1396915976,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"The world is not breaking. The world of Vector is just going through turbulence.
+
+As stated above external links were removed as part of the typography beta feature. Actually, not a single person wrote about this on the talk page (https://www.mediawiki.org/wiki/Talk:Typography_Update) during the 6 months it was live. This evidence leads me to believe that they are /not/ important and it is the basis for removing them.
+
+If this proves to be wrong, then we react and restore/amend it, it's no big deal. Commits and reverts are cheap.
+
+The fact we have to actively discuss trivial changes like this concerns me greatly. We have a huge editor decline and here we are arguing about some icons next to links.
+
+Also I think you mean /editors/ when you say /readers/ here. I think most /readers/ care simply if a link will take them to an external site or not.",1396915738,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Isarra from comment #34)
+We did a beta feature, it was called typography refresh, and little to no feedback (negative or positive) addressed the removal of these icons, that was the impetus for moving forward with this as a simple patch. 
+
+If you read on the Beta Features page, you'll see that Beta Features should not be only subtractive in nature, e.g. packaging up the removal of these icons as its own feature makes very little sense. — https://www.mediawiki.org/wiki/Beta_Features/Package",1396915523,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"
+> 
+> Its relevant because asking for feedback on ""the usual channels"" completely
+> omits the target user, when the target users is a reader. Jon's point that
+> we can do it and then iterate speaks to the fact that it is one of our only
+> ways to get reader feedback. To roll the change out publicly then iterate.
+> We can get better at this eventually, but at the current juncture, I think
+> this is a sound plan based on our infrastructure for eliciting feedback from
+> readers and others who aren't aware of, or participate in ""the usual
+> channels""
+> 
+> Hope that makes sense.
+
+breaking the world, and then seeing who complains isn't really a good way to get feedback from readers. First off, most people who complain aren't going to be ""readers"" they are going to be active users who are familiar with the regular channels. If you actually get readers angry enough that they figure out how to complain, you've probably massively screwed up the site. Second, that's prone to a massive confirmation bias of ""Well nobody or not that many people complained out of a group of people who don't know how to complain, therefore it must be a good idea""
+
+I really think this is an extraordinarily dangerous line of reasoning to go down.",1396914965,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"In reply to Jared Zimmerman (WMF) from comment #31)
+> Its relevant because asking for feedback on ""the usual channels"" completely
+> omits the target user, when the target users is a reader. Jon's point that
+> we can do it and then iterate speaks to the fact that it is one of our only
+> ways to get reader feedback. To roll the change out publicly then iterate.
+> We can get better at this eventually, but at the current juncture, I think
+> this is a sound plan based on our infrastructure for eliciting feedback from
+> readers and others who aren't aware of, or participate in ""the usual
+> channels""
+
+I would think that 'users' here would include readers and editors both, and even then, editors often know their readers better than one might expect (such as by talking to them, or being them). So talking to the editors is probably exactly the right place to start. They could tell you things like the fact that some of these external link styles, such as IRC, will never appear in article space (on a non-technical project, anyway - mw.org or archwiki and similar probably have quite a few irc links in various articles), but are often used in project and user space (so changes to that style would be purely editor-facing on projects like Wikipedia, not reader). Or that readers often complain when <blah> or have trouble with <blah>.
+
+And there is also ample infrastructure in place to test potential changes, is there not? For instance you could do:
+* A/B tests to determine if readers are less likely to click on external if they are or aren't visibly marked as whatever kind of link they are. 
+* Scripted tests on usertesting.com to gain insight into possible reactions to unexpected pdfs, audio files, IRC links, etc vs regular external links, and to the external link icons themselves when they are used, such as if they even figure out what they mean.
+* A betafeature for users to see if removing the special icons affects their workflows, or if they prefer it outright.
+
+If there is a problem, you should be able to prove it without just deploying it first and asking questions later. Also what Derk-Jan said.",1396914365,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Users of a product are aware (although not always consciously) of the absence of something equally well as the awareness of and existence of something (cruft). A user does not need to be aware of something, an ""absence,"" say to be aware that a product is better because of design choices to remove, and simplify. 
+
+
+""Good design is as little design as possible — Less is more – because it concentrates on the essential aspects and the products are not burdened with non-essentials. Back to purity, back to simplicity"" —Dieter Rams
+
+""Perfection is achieved perfection not when there is nothing left to add, but when there is nothing left to take away"" –Antoine de Saint-Exupery",1396914062,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Then again, can you expect a casual reader to ever appreciate that which is not there? A removal like this is hard to notice, because most links don't have these icons.
+
+Your proposal is basically: Ah, people asked for this 10 years ago. but there is a bunch of annoying css rules, so let's remove them and wait how long it takes for people to ask if they can have the feature back. This feature contributes to the rule of least astonishment, and you are removing it without considering replacing it with an alternative.
+
+I find that somewhat presumptuous if i'm honest. But then again, I thought messing with fonts was a dangerous plan and that turned out just splendid, so what do I know....",1396913306,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Isarra from comment #28)
+> And there is a right way to make change happen - by proposing changes and
+> getting feedback. By implementing this, you have inherently proposed it, and
+> now you are getting feedback. Whether or not they should be merged depends
+> on what consensus is established either here or in other appropriate
+> channels; we have these channels for a reason.
+
+Its relevant because asking for feedback on ""the usual channels"" completely omits the target user, when the target users is a reader. Jon's point that we can do it and then iterate speaks to the fact that it is one of our only ways to get reader feedback. To roll the change out publicly then iterate. We can get better at this eventually, but at the current juncture, I think this is a sound plan based on our infrastructure for eliciting feedback from readers and others who aren't aware of, or participate in ""the usual channels""
+
+Hope that makes sense.",1396911689,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jared Zimmerman (WMF) from comment #29)
+> Isarra, I've mentioned it before and I'll mention it here again, that
+> process makes total sense for editor or logged-in user features. It doesn't
+> make sense for reader facing features, as these users are not part of this
+> conversation.  
+> 
+> You know how to do cross site links but many users do not, and the systems
+> are not smart enough to automatically convert them in many cases.
+
+I agree, new users often don't appreciate the significance of many features. But how is this relevant to the matter at hand?",1396911306,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Isarra, I've mentioned it before and I'll mention it here again, that process makes total sense for editor or logged-in user features. It doesn't make sense for reader facing features, as these users are not part of this conversation.  
+
+You know how to do cross site links but many users do not, and the systems are not smart enough to automatically convert them in many cases.",1396910718,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #26)
+> To be clear, we still show an external link icon.
+> Yes I suspect it may annoy people but this can be easily remedied. Change is
+> also a trend that needs to start.
+
+And there is a right way to make change happen - by proposing changes and getting feedback. By implementing this, you have inherently proposed it, and now you are getting feedback. Whether or not they should be merged depends on what consensus is established either here or in other appropriate channels; we have these channels for a reason.
+
+(In reply to Jared Zimmerman (WMF) from comment #27)
+> Isarra, from a technical perspective a PDF hosted on commons while I'm on
+> wikipedia is ""leaving the site"" but this isn't how most readers or casual
+> editors see it. That was my point. I appreciate your point about it from a
+> literal perspective.
+
+External links appear if the external link format is used, regardless of where the link points. They are only supposed to be for links that go off the site (in other words, ones that are 'external'); we normally use wikilinks (ones formatted [[like this]]) to link to local and sister project pages, which do not result in external link formatting.
+
+For more information about how links work in MediaWiki, please see https://www.mediawiki.org/wiki/Links",1396910489,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Isarra, from a technical perspective a PDF hosted on commons while I'm on wikipedia is ""leaving the site"" but this isn't how most readers or casual editors see it. That was my point. I appreciate your point about it from a literal perspective.",1396903714,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"To be clear, we still show an external link icon.
+Yes I suspect it may annoy people but this can be easily remedied. Change is also a trend that needs to start.",1396903563,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jared Zimmerman (WMF) from comment #23)
+> From my understand the external/file format link icons are only relevant
+> when you are actually leaving the site, or when it would cause your browsers
+> to download a file rather than loading it in some kind of built in player,
+> either on site or in-browsers. The original code for this I assume was
+> created prior to mediawiki being able to natively handle many of these file
+> formats. 
+
+Generally external links do leave the site. This is what 'external link' means.
+
+(In reply to Jon from comment #24)
+> That said, I am happy to deal with any after effects of this change. I'd
+> hope such a drastic change would surface the icons that are important.
+> 
+> I think the removal of them although somewhat extreme, will make it clearer
+> and easier to restore ones that are vital.
+
+I would suggest that breaking everything and then seeing what people complain about the most may not be the best way to determine what is important. Yes, it may work, but more than anything it's probably just going to annoy people, and needlessly alienating users is a trend that needs to stop, not continue.",1396902884,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Apologies if I misunderstood and this had been the agreement.
+
+That said, I am happy to deal with any after effects of this change. I'd hope such a drastic change would surface the icons that are important.
+
+I think the removal of them although somewhat extreme, will make it clearer and easier to restore ones that are vital.
+
+A lot of these icons may be better done in something like MediaWiki:Vector/Monobook/Common.css on a per project basis anyhow.",1396902298,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"From my understand the external/file format link icons are only relevant when you are actually leaving the site, or when it would cause your browsers to download a file rather than loading it in some kind of built in player, either on site or in-browsers. The original code for this I assume was created prior to mediawiki being able to natively handle many of these file formats. 
+
+That said I think most if not all of these are no longer needed and confuse many users. Overall I would urge us to move towards simplicity when it comes to links, designating only links that take you out of the WMF sites, and links that point to non-existent articles. 
+
+If knowing target file types is relevant to a small subset of users I've argue that this code should be gadgetized by someone who cares to retain this feature.",1396900073,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #14)
+> Great. I'm agnostic about killing the icons or not. My main goal is to start
+> cleaning up and improving all the desktop CSS.
+
+I thought we'd agreed to clean up the expensive CSS, and not to delete the icons (which is what https://gerrit.wikimedia.org/r/123817 does).
+
+:/",1396809360,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 123817 merged by jenkins-bot:
+Vector: Simply style external links
+
+https://gerrit.wikimedia.org/r/123817",1396736501,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"If they're not affected, they're not representative. It doesn't sound rational to mention them in the commit message.",1396631124,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"I don't understand the question/problem. All wikis got the beta features experiment.
+
+If those wiki's have local icons, that is fine, they won't be effected by this change to Vector, and will get a performance boost by having a simpler set of css selectors for these icons.",1396630023,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"> During the typography experiment, these were removed, no one raised this as an 
+> issue during the 5 months it was live, suggesting that explicit pdf icons etc
+> are not as useful as we like to believe.
+
+How many of the (English) wikis in question did not have *local* icons? How do you know how many were actually affected by these changes?",1396629807,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 123817 had a related patch set uploaded by Jdlrobson:
+Vector: Simply style external links
+
+https://gerrit.wikimedia.org/r/123817",1396625023,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"See http://lists.wikimedia.org/pipermail/wikitech-l/2013-October/072642.html
+
+Main highlights:
+
+* We shouldn't confuse English Wikipedia's overrides with code in core.  However, there is room to clean that up, even if they want to keep a different icon from core (e.g. moving the Modern-specific code to Modern.css).
+* I like the idea of doing it in the parser, but it obviously requires more testing than a CSS change.  To expand on what I said in the email, we could do something generic like 'mw-link-extension-pdf'.  We would need to decide whether to do it for all extensions, or just the ones where core styles it.
+* We could consider using the Commons PDF icon in core, if it's freely licensed (have not investigated).",1382663777,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #14)
+> Great. I'm agnostic about killing the icons or not. My main goal is to start
+> cleaning up and improving all the desktop CSS.
+
+Sensible thing to do, indeed. Just bear in mind caching issues. >.<",1380781960,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,Great. I'm agnostic about killing the icons or not. My main goal is to start cleaning up and improving all the desktop CSS.,1380661301,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #11)
+> That aside use of a single class .link-https rather than a
+> combination of class .link-https, div#content a.external[href
+> ^=""https://""] would be preferable for a variety of reasons
+> readability, maintainability, reduced file size... are you really
+> telling me this is not a no-brainer?
+
+Using the classes as you proposed does seem sane and mostly non-troublesome (apart from the classic caching issues). I am perfectly fine with doing that (as long as I'm not the one who will have to jerry-rig the Parser).
+
+Killing the icons as suggested in comment 1 is a completely different thing and, apart from what I mentioned in comment 7, I will vehemently oppose doing it.
+
+
+(In reply to comment #11)
+> If you really feel the need for a citation check out:
+> http://stevesouders.com/efws/css-selectors/csscreate.php
+
+Either I am unable to figure it out, or it doesn't work. Reflow time is 0 for me no matter what I do. ""page load time"" is measuring the speed of my connection if anything.
+
+(In reply to comment #12)
+> CSS rule efficiency table:
+> http://csswizardry.com/2011/09/writing-efficient-css-selectors/
+
+This looks interesting; sorry, I don't have time to dig into it right now, but hopefully I will later. (Hopefully it's still relevant - it was apparently written in 2011, and two years is like a few decades at least ;) )",1380661163,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,CSS rule efficiency table: http://csswizardry.com/2011/09/writing-efficient-css-selectors/,1380657589,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #9)
+> (In reply to comment #8)
+> > The CSS is pretty ridiculous. Let's not forget that CSS parses from the
+> > rightmost rule so something like a.external[href ^=""news:""] can be a pretty
+> > expensive operation.
+> 
+> [citation needed]. I don't see why would it be particularly more expensive
+
+If you really feel the need for a citation check out:
+http://stevesouders.com/efws/css-selectors/csscreate.php
+
+That aside use of a single class .link-https rather than a combination of class .link-https, div#content a.external[href ^=""https://""] would be preferable for a variety of reasons readability, maintainability, reduced file size... are you really telling me this is not a no-brainer?",1380657176,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #9)
+> (In reply to comment #8)
+> > The CSS is pretty ridiculous. Let's not forget that CSS parses from the
+> > rightmost rule so something like a.external[href ^=""news:""] can be a pretty
+> > expensive operation.
+> 
+> [citation needed]. I don't see why would it be particularly more expensive
+> than
+> any of the hundreds of other rules we have. Assuming that the hypothetical
+> browser does indeed naively match from the right side always, [href^=""news:""]
+> will immediately not match (most elements don't even have a href attribute)
+> and
+> the ten or so of such rules should not be noticeable.
+
+Afaik selector engines have quick lookup maps for IDs, classes and elements. In the case of "".mw-link-pdf"" that is a very quick lookup.
+
+In the case of ""#bodyContent a.external[href=..]"" it is a lookup for elements of 'a', then for each the classname and the attribute is matched, and then it recursively does a parent check until it finds #bodyContent or the document element.
+
+In theory it could optimise if it had a quick lookup for elements having a certain attribute. But afaik they don't have that, and even if they did, I isn't more efficient per se, cause then the post-check would have to verify tag name and class name for each.
+
+Either way, none of this in particular is bad, it's the whole package of:
+* A very strong selector (#bodyContent)
+* A parent selector
+* Both element and class name (should never be used together)
+* Additional attribute matching and string operations on that
+* Hardcodes details that (other) stylesheets should not have to know or hardcode, thus causing maintenance issues (e.g. the fact that it is an <a>, and is inside #bodyContent. The container can change, and links might be wrapped for presentational reasons)
+
+Up sides of using a simple class:
+* Faster query (one could argue about how much, but it is certainly faster)
+* Support for older browsers (this is not a priority though, since all our grade A browsers support it, and it's a minor enhancement with graceful degradation)
+* Easier to extend from other components as there is no need to have any knowledge about implementation details (container element, tag name etc.)",1380569631,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #8)
+> The CSS is pretty ridiculous. Let's not forget that CSS parses from the
+> rightmost rule so something like a.external[href ^=""news:""] can be a pretty
+> expensive operation.
+
+[citation needed]. I don't see why would it be particularly more expensive than any of the hundreds of other rules we have. Assuming that the hypothetical browser does indeed naively match from the right side always, [href^=""news:""] will immediately not match (most elements don't even have a href attribute) and the ten or so of such rules should not be noticeable.",1380567205,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"The CSS is pretty ridiculous. Let's not forget that CSS parses from the rightmost rule so something like a.external[href ^=""news:""] can be a pretty expensive operation. These rules should be killed with fire in favour of specific classes like link-pdf if needed.
+
+I don't care if we kill or keep rules I just want these rules to die and the CSS in general to be cleaned up.",1380561554,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Per Isarra and Quiddity, I think that the only ones that should be killed are the HTTPS and FTP ones. That CSS is not ridiculous, it's just a little uncool.",1380371064,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #5)
+> My gut says remove them all esp. the https links, as @Isarra mentioned the
+> only
+> one that seems to make any real sense is links that point to files, like
+> PDFs,
+> however  internal (Commons) links have their own viewer. External PDFs seem
+> like the only file that marking their links seems relevant in any way. Most
+> modern browsers have built-in PDF renders so even the days of PDFs being
+> treated special is soon becoming irrelevant. 
+> 
+
+Isarra mentioned mailto and IRC links too, which I'd agree are instances where the icon is useful. 
+
+The audio/video icons are also good to have, per principle of least astonishment (eg, someone adds a link to a loud .wav file into an article's external links, and someone else in a quiet office clicks on it).
+
+They also help editors to notice that these uncommon link types are present, and hence to check whether they're really suitable/wanted or not. (If I see an audio-file icon, I often click it to check for spam/vandalism).
+
+
+> My recommendation would be to remove all special formatting other than
+> wikilinks vs external links. 
+> 
+> If we could determine and mark wikilinks that are to other sister projects,
+> I'd recommend they be treated as regular wikilinks as well.
+
+Interwiki links (everything in https://meta.wikimedia.org/wiki/Interwiki_map )
+are already styled with a slightly-lighter blue, via class ""extiw"" (external interwiki) located in https://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/skins/common/commonElements.css?view=markup and skins/monobook/main.css",1380345239,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"My gut says remove them all esp. the https links, as @Isarra mentioned the only one that seems to make any real sense is links that point to files, like PDFs, however  internal (Commons) links have their own viewer. External PDFs seem like the only file that marking their links seems relevant in any way. Most modern browsers have built-in PDF renders so even the days of PDFs being treated special is soon becoming irrelevant. 
+
+My recommendation would be to remove all special formatting other than wikilinks vs external links. 
+
+If we could determine and mark wikilinks that are to other sister projects, I'd recommend they be treated as regular wikilinks as well.",1380340657,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #1)
+> Honestly I'd recommend just killing these link icons outright...
+
+One of the things to consider is when and where the links are actually used, and if special treatment is even sensible anymore. 
+
+Generally we'd probably only want special icons for things that are both fairly commonly used and where the browser reaction would be significantly different from general browsing - for things like PDFs, which are often used for sources, that can open up in a new window or rearrange the tab depending on browser, or mailto and IRC which often send the request out of the browser entirely and open a new window. Users do like warning when it comes to that sort of thing, indeed.
+
+Whereas we probably don't want anything special for things like https, ftp, etc where the browser just opens it like normal, especially since for instance https is becoming more and more common as the default...",1380323575,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #1)
+> Honestly I'd recommend just killing these link icons outright...
+
+Some of the other icons could /possibly/ be removed without screaming. 
+
+But the PDF icon is important. Users get frustrated when they click a PDF without warning.
+
+(The only alternative is [[Template:PDFlink]] which makes article/citation code more complicated, so that's not good.)",1380179977,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #1)
+> Honestly I'd recommend just killing these link icons outright...
+
+This is a design question, I think. Adding the Bugzilla keyword accordingly.",1380173289,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,Honestly I'd recommend just killing these link icons outright...,1380131401,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+"VisualEditor: this.referenceSurface should be a Surface, not a SurfaceWidget","In ve.ui.MWReferenceDialog, this.referenceSurface changed from being a Surface to a SurfaceWidget. I noticed this because I rebased some old code that used this.referenceSurface.getModel() and broke, but this seems to have happened a while ago with the introduction of SurfaceWidget.
+
+When a variable name is 'fooSurface', it should be a Surface, not something else. In particular, you shouldn't have to do this.referenceSurface.getSurface() to get the surface.
+
+The same applies to this.captionSurface in ve.ui.MWMediaEditDialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1380077400,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dlrbz5yirqhdlb5ixx32,task_description,resolved
+"VisualEditor: this.referenceSurface should be a Surface, not a SurfaceWidget","These are now fooTarget instace of TargetWidget, however TargetWidget behaves like target, not a target wrapper, so this bug is resolved.",1533388170,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dlrbz5yirqhdlb5ixx32,task_subcomment,NA
+VisualEditor: Inserting a reference breaks up annotations around it,"When you insert a reference in the middle of a bolded word, the reference itself doesn't receive a bold annotation, and so the resulting text is something like '''He'''<ref name=""hello"" />'''llo''', with the bold breaking around the reference.
+
+When we insert inline nodes like references from the UI, they should take annotations. This is probably a wider problem beyond just references.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380074640,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-y3zmidmzskha5h7ldgcc,task_description,open
+VisualEditor: Inserting a reference breaks up annotations around it,See bug 48720.,1382626276,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-y3zmidmzskha5h7ldgcc,task_subcomment,NA
+VisualEditor: Inserting a reference breaks up annotations around it,"(In reply to comment #2)
+> Also, I'm not sure this is desirable behaviour.
+
+But we are. :-)",1380755694,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y3zmidmzskha5h7ldgcc,task_subcomment,NA
+VisualEditor: Inserting a reference breaks up annotations around it,"Also, I'm not sure this is desirable behaviour.",1380472840,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-y3zmidmzskha5h7ldgcc,task_subcomment,NA
+VisualEditor: Inserting a reference breaks up annotations around it,"The dialogs generate insertion transactions directly with newFromInsertion, and have no insertion annotation logic.",1380279978,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-y3zmidmzskha5h7ldgcc,task_subcomment,NA
+VisualEditor: MWExtensionNode/GeneratedContentNode should avoid emitting 'rerender' twice when rendering <img>s,"ce.MWExtensionNode.onParseSuccess contains the following code:
+
+	// Rerender after images load
+	this.$.find( 'img' ).on( 'load', ve.bind( function () {
+		this.emit( 'rerender' );
+	}, this ) );
+
+Problems:
+* Why is this in MWExtensionNode? Shouldn't it just be in GCNode?
+* This potentially emits multiple rerender events, one for each image
+* The first rerender event has already been emitted because we've already resolved the promise and attached the nodes to the DOM
+
+What we should really do is attach the nodes somewhere else (where?) so that the images load, then reattach them to a wrapper and resolve the promise with that. That way we only emit rerender once, and we correctly only resolve the promise once everything has actually loaded.
+
+In practice, this means the math inspector moves around twice after typing LaTeX in certain cases: once because of the 'rerender' event caused by the <img> tag being put on the page (at which point it measures 0x0), and once because of the 'rerender' event caused by the image actually loading (at which point it measures correctly).
+
+Open questions:
+* How does this work for images with invalid/unavailable sources?
+* Really what we care about here is the dimensions of the images. If those are known, we can render the node without its dimensions changing later
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380072600,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-d2izuitwfayrxbyhcjil,task_description,resolved
+VisualEditor: MWExtensionNode/GeneratedContentNode should avoid emitting 'rerender' twice when rendering <img>s,https://gerrit.wikimedia.org/r/#/c/86167/ fixes this,1380232745,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-d2izuitwfayrxbyhcjil,task_subcomment,NA
+"VisualEditor: ce.GeneratedContentNode.generateContents() should be static, so we can cache based on config objects alone","Right now, GCNode caching uses both the model hash and the hash of the config object. However, when properties in the config override properties in the model, the preview of a change and the new model node after the actual change will be the same but have different hashes (because the model is different, and because in the second case the config object is empty/undefined).
+
+We should make generatedContents() static, so it can't inspect the model or any object state, and have a function that provides the default config that is then used to extend the provided config. That way we don't end up duplicating things in cache and rendering things twice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1380071580,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pvtq3ysdgbspx2ubicva,task_description,open
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Currently http://korma.wmflabs.org/browser/its-repos.html shows that the Bugzilla products scanned are MediaWiki, All extensions, VisualEditor and Parsoid. However, this list must be in sync with http://korma.wmflabs.org/browser/scm-repos.html - which in turn is synced with https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects
+
+Let's update that wiki page with the relevant products / components. A 100% match is probably impossible, but a 90% (or so) should be feasible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49744",1379952300,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_description,resolved
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"(In reply to comment #6)
+> ==Core Extensions==
+> Don't want to spend too much time going through the list and syncing with
+> https://bugzilla.wikimedia.org/editcomponents.
+> cgi?product=MediaWiki%20extensions
+> however noteworthy naming differences from the top of my head:
+
+Currently korma lists all the extensions in a single project. This is good enough for now, but for the Bugzilla Response Time KPI [1] we will need to be more precise:
+
+* Including only the key projects.
+* Treating each component separately, just like we do with code repos.
+
+[1] https://www.mediawiki.org/wiki/Community_metrics#Bugzilla_response_time",1382560830,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Ok guys, you have the viz in:
+
+http://korma.wmflabs.org/browser/its-repos.html",1382549565,PHID-USER-lepsd737p6wqwsowcou2,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Great, I have programmed for adding to the report the next repos:
+
+Analytics > Kraken: https://bugzilla.wikimedia.org/buglist.cgi?product=analytics&component=kraken&list_id=243545
+Datasets > Webstatscollector: https://bugzilla.wikimedia.org/buglist.cgi?product=datasets&component=Webstatscollector&list_id=243568
+Analytics > Wikimetrics https://bugzilla.wikimedia.org/buglist.cgi?product=analytics&component=wikimetrics
+Analytics > Wikistats https://bugzilla.wikimedia.org/buglist.cgi?product=analytics&component=wikistats
+Analytics > Limn https://bugzilla.wikimedia.org/buglist.cgi?product=analytics&component=limn
+Analytics > General/Unknown https://bugzilla.wikimedia.org/buglist.cgi?product=Analytics&component=General%2FUnknown
+Commons App > iOS (iPhone or iPad) https://bugzilla.wikimedia.org/buglist.cgi?product=Commons%20App&component=iOS%20%28iPhone%20or%20iPad%29
+Wikipedia App https://bugzilla.wikimedia.org/buglist.cgi?product=wikipedia%20app
+Wiki Loves Monuments > Mobile https://bugzilla.wikimedia.org/buglist.cgi?product=Wiki%20Loves%20Monuments&component=Mobile
+Wikimedia > Continuous integration https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=Continuous%20integration
+Wikimedia > DNS https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=dns
+Wikimedia > OTRS https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=otrs
+Wikimedia > Bugzilla https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=bugzilla
+Wikimedia > wikibugs IRC bot https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=wikibugs%20IRC%20bot
+Wikimedia > Blog https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=blog
+Wikimedia > Fundraising: Misc. https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=Fundraising%3A%20Misc.
+Wikimedia > Fundraising: Requirements https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=Fundraising%3A%20Requirements
+Tools > code-utils https://bugzilla.wikimedia.org/buglist.cgi?product=tools&component=code-utils
+Tools > mw-dumper https://bugzilla.wikimedia.org/buglist.cgi?product=tools&component=mwdumper
+Pywikibot > * https://bugzilla.wikimedia.org/buglist.cgi?product=Pywikibot
+MediaWiki-Vagrant > * https://bugzilla.wikimedia.org/buglist.cgi?product=MediaWiki-Vagrant
+Wikimedia Labs > tools https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia%20labs&component=tools
+openZIM > * https://bugzilla.wikimedia.org/buglist.cgi?product=openZIM
+Wikimedia > Quality Assurance https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=quality%20assurance
+
+I have checked all of them and works. So tomorrow you should have the new info.",1382519999,PHID-USER-lepsd737p6wqwsowcou2,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,Yes!,1382370607,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Ok guys, is this ready to start downloading all those bugzilla product and components and adding them to the korma browser?",1382353678,PHID-USER-lepsd737p6wqwsowcou2,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"I guess we all know that there are no clear 1:1 mapping is possible, but instead 1:n or n:1. I just hope to avoid n:n. :)
+
+
+[[wikitech:Key_Wikimedia_software_projects]] -- Bugzilla product > component
+
+
+==Analytics==
+analytics/kraken                 --  Analytics > Kraken
+analytics/webstatscollector      --  Datasets > Webstatscollector
+analytics/wikimetrics            --  Analytics > Wikimetrics
+analytics/wikistats              --  Analytics > Wikistats
+github.com/wikimedia/limn        --  Analytics > Limn
+analytics/*                      --  Analytics > General/Unknown
+==Mobile apps==
+apps/android/commons 
+github.com/wikimedia/Commons-iOS --  Commons App > iOS (iPhone or iPad)
+github.com/wikimedia/WikipediaMobile  --  Wikipedia App
+github.com/wikimedia/WikipediaMobileFirefoxOS  --  Wikipedia App
+github.com/wikimedia/WLMMobile   -- Wiki Loves Monuments > Mobile
+==Integration==
+*                                --  Wikimedia > Continuous integration
+==Operations==
+Hard to define, mostly in rt.wikimedia.org, some in Bugzilla under ""Wikimedia > General"" with keyword ""ops"".
+operations/dns                   --  Wikimedia > DNS
+operations/software/otrs         --  Wikimedia > OTRS
+==Wikimedia==
+====Bugzilla====
+wikimedia/bugzilla/modifications --  Wikimedia > Bugzilla
+wikimedia/bugzilla/triagescripts --  Wikimedia > Bugzilla
+wikimedia/bugzilla/wikibugs      --  Wikimedia > wikibugs IRC bot
+====Communication====
+wikimedia/communications/WMBlog  --  Wikimedia > Blog
+====Fundraising====
+Mostly using CiviCRM; related components in Bugzilla are:
+                             --  MediaWiki extensions > FundraiserLandingPage
+                                 --  MediaWiki extensions > FundraiserPortal
+                                 --  Wikimedia > Fundraising Misc.
+                                 --  Wikimedia > Fundraising Requirements
+==MediaWiki misc==
+mediawiki/php/FastStringSearch
+    mediawiki/php/NativePreprocessor
+    mediawiki/php/luasandbox     --  MediaWiki extensions > Scribunto
+    mediawiki/php/wikidiff2      --  MediaWiki extensions > wikidiff2
+mediawiki/tools/code-utils       --  Tools > code-utils
+mediawiki/tools/mwdumper         --  Tools > mw-dumper
+==Pywikibot==
+pywikibot/*                      --  Pywikibot > *
+==Other==
+mediawiki/vagrant                --  MediaWiki-Vagrant > *
+labs/toollabs                    --  Wikimedia Labs > tools
+openzim                          --  openZIM > *
+qa/browsertests                  --  Wikimedia > Quality Assurance
+==Core Extensions==
+Don't want to spend too much time going through the list and syncing with https://bugzilla.wikimedia.org/editcomponents.cgi?product=MediaWiki%20extensions however noteworthy naming differences from the top of my head:
+
+PageTriage                       --  MediaWiki extensions > PageCuration
+Parsoid                          --  Parsoid > *
+SyntaxHighlight_GeSHi     --  MediaWiki extensions > SyntaxHighlight (GeSHi)
+VisualEditor                     --  VisualEditor > *
+Wikibase                         --  MediaWiki extensions > WikidataRepo",1382025323,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Andre, if you could point to the Bugzilla product/component of each project at https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects that would be perfect!",1381773164,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"(If there is something I can specifically help with as Bugzilla admin, please tell me what I need to do for you folks.)",1381764843,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Quim, for the Bugzilla components mapping, do you have some plan in mind for gathering the info from Wikimedia Community? Maybe we can start doing the mapping of the more clear components, but it there is a complete process to cover all of them, much better!",1381760730,PHID-USER-lepsd737p6wqwsowcou2,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Yes Quim, we can scan only components.",1380184604,PHID-USER-lepsd737p6wqwsowcou2,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Álvaro, can MetricsGrimoire scan only specific components of a Bugzilla product? The reason to ask is that, ideally, we wouldn't scan the whole MediaWiki Extension product but only the relevant components.",1379952721,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Broken wikitext with bold inside and outside a label wrongly interpretted as correct by Parsoid,"**Author:** `jmichrina`
+
+**Description:**
+Example:
+Line from ""International_Air_Transport_Association_airport_code""
+
+DFW for Dallas–Fort Worth, DTW for Detroit–Wayne County, RDU for Raleigh–Durham, MSP for Minneapolis–St. Paul and LBA for Leeds Bradford (Airport).
+
+Line appears correctly formatted in editor [caps represent bold]:
+dfw for Dallas-Fort Worth, dtw for DetroiT-Wayne county, rdu for Raleigh-DUrham, msp for Minneapolis-St. Paul and lba for Leeds Bradford (Airport).
+
+Line appears incorrect on page [caps represent bold]:
+dfw for DALLAS-FORT WORTH, stw for dEtROIT-wAYNE COUNTY, rdu for RALEIGH-DURHAM, msp for mINNEAPOLIS-sT. pAUL and lba for LEEDS BRADFORD (AIRPORT).
+
+Note that the correct version appears in the editor even after it's saved.
+
+Possibly related to bug 53208, but I didn't have time to verify.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1379880120,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-geakkjwdr2b6k3vobqx7,task_description,resolved
+Broken wikitext with bold inside and outside a label wrongly interpretted as correct by Parsoid,"This has long been merged, so closing as fixed. Please reopen if there is still an issue.",1386117085,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-geakkjwdr2b6k3vobqx7,task_subcomment,NA
+Broken wikitext with bold inside and outside a label wrongly interpretted as correct by Parsoid,"Tidy should result in non-broken HTML (unless there is a bug in Tidy). I just checked and Tidy fixes PHP parser's broken HTML and generates: <p><b><a href=""/wiki/Foo"" title=""Foo"" class=""mw-redirect"">F<b>oo</b> B<b>ar</b></a></b></p> (Can be verifed at https://en.wikipedia.org/wiki/User:Ssastry/sandbox)
+
+As for Parsoid, yes, this kind of broken wikitext was not being handled properly so far, but that is set to change with https://gerrit.wikimedia.org/r/#/c/83216/ which is awaiting review.
+
+That patch generates the following HTML on the snippet which is similar to what Tidy generates
+
+<p data-parsoid='{""dsr"":[0,27,0,0]}'><b data-parsoid='{""autoInsertedEnd"":1,""dsr"":[0,27,3,0]}'><a rel=""mw:WikiLink"" href=""./Foo"" data-parsoid='{""stx"":""piped"",""a"":{""href"":""./Foo""},""sa"":{""href"":""Foo""},""dsr"":[3,27,6,2]}'>F<b data-parsoid='{""dsr"":[10,19,3,3]}'>oo </b>B<b data-parsoid='{""autoInsertedEnd"":1,""dsr"":[20,25,3,0]}'>ar</b></a></b></p>",1380680793,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-geakkjwdr2b6k3vobqx7,task_subcomment,NA
+Broken wikitext with bold inside and outside a label wrongly interpretted as correct by Parsoid,"I have fixed the particular problem with this edit: https://en.wikipedia.org/w/index.php?title=International_Air_Transport_Association_airport_code&diff=574406042&oldid=574202912
+
+This is caused by a bug in Parsoid, I believe, which is wrongly interpretting wikitext as valid when it should be invalid. Specifically:
+
+  '''[[Foo|F'''oo '''B'''ar]]
+
+… as …
+
+  <b><a href=Foo>F</a></b><a href=Foo>oo </a><b><a href=Foo>B</a></b><a href=Foo>ar</a>
+
+… whereas it should result in broken HTML, per the PHP parser (post-Tidy), as:
+
+  <b><a href=Foo>F<b>oo </b>B<b>ar</b></a>
+
+The broken wikitext was added in https://en.wikipedia.org/w/index.php?title=International_Air_Transport_Association_airport_code&diff=568156811&oldid=568156261 which isn't tagged as a VisualEditor edit but possibly could have been (and a secondary bug means it isn't tagged) - will investigate separately.",1380075628,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-geakkjwdr2b6k3vobqx7,task_subcomment,NA
+VisualEditor: Editor incorrectly selects slug and infobox onload,"Screenshot
+
+https://en.wikipedia.org/w/index.php?title=Daniel_Rowe_%28footballer%29&oldid=570278760&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11872}",1379834460,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uw2trpgzgq47w4uqfske,task_description,resolved
+VisualEditor: Editor incorrectly selects slug and infobox onload,"Change 85866 merged by jenkins-bot:
+Detect collapsed range inside focusable node in ve.ce.Surface#onChange
+
+https://gerrit.wikimedia.org/r/85866",1380043305,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uw2trpgzgq47w4uqfske,task_subcomment,NA
+VisualEditor: Editor incorrectly selects slug and infobox onload,"Change 85866 had a related patch set uploaded by Esanders:
+Detect collapsed range inside focusable node in ve.ce.Surface#onChange
+
+https://gerrit.wikimedia.org/r/85866",1380038162,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uw2trpgzgq47w4uqfske,task_subcomment,NA
+VisualEditor: Editor incorrectly selects slug and infobox onload,"This is cause by ve.ce.Surface#showSelection not being aware of the slug at the start of the document. Also, because the focusableNode logic takes places before showSelection is called, it tries to do a native selection.",1380036773,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-uw2trpgzgq47w4uqfske,task_subcomment,NA
+VisualEditor: Editor incorrectly selects slug and infobox onload,"Created attachment 13347
+Screenshot of page after trying to Undo
+
+Causes loss of data as it makes it really easy to accidentally delete that selection when you start typing.
+
+When you then try to do Undo, the following exception is thrown:
+
+Uncaught Error: Cannot roll back a transaction that has not been committed 
+
+Also, for some reason the font has become noticably smaller (only in the affected paragraph; see screenshot)
+
+**Attached**: {F11873}",1379834796,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uw2trpgzgq47w4uqfske,task_subcomment,NA
+VisualEditor: Automatic Incorrect caret movement with ULS,"This is a separate report for automatic caret movement from one place to another when using VE with ULS.
+
+This problem has been seen with some other bugs, specifically, in the fourth[1], seventh[2] and tenth[3] comments of Bug 53708 and the original report of Bug 54421
+
+I also suspect that the problem in Bug 53701 is a form of this bug only.
+
+However, I am reporting this as a separate bug since I was able to reproduce it independent of these bugs.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit
+
+Steps:
+1 Enable ULS IME hindi transliteration
+2 Take the caret to the end of the first paragraph using the mouse (i.e click at the end of the first paragraph to take the caret there)
+3 Input [RETURN KEY][RETURN KEY]a
+
+Expected output:
+[NEWLINE][NEWLINE]अ
+
+Actual Output:
+[NEWLINE]अ[NEWLINE]
+
+As long as the return keys have been pressed, everything is fine and the caret is in the second newline. However, as soon as a is pressed, the input is in the first new line and not the second. The caret has hence moved up one line before the input is placed into the output text. The caret does not move back and is after the output अ
+
+This text is selectable, but can't be copy-pasted into an external text editor.
+The text is removable, so this is not entirely Bug 53708 . However, pressing a backspace when the caret is after अ removes अ along with the newline that precedes it.
+
+[1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c4
+[2]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c7
+[3]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c10
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379768640,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-nql2oht74xidzmey66vl,task_description,resolved
+VisualEditor: Automatic Incorrect caret movement with ULS,"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.",1453748489,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nql2oht74xidzmey66vl,task_subcomment,NA
+VisualEditor: Automatic Incorrect caret movement with ULS,"Hi,
+
+Confirming the above problem for VE+ULS (Typing input Marathi:अक्षरांतरण) Tested with Win 7 + Firefox 24.0 
+
+*Plus additional issue observed after Automatic Incorrect caret movement when I kept typing It started eating up text on right side in continuous movement simmiller to the problem described in Bug 53757 .
+
+
+
+
+Thanks and Regards",1379905436,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-nql2oht74xidzmey66vl,task_subcomment,NA
+VisualEditor: Text duplication when using jquery.IME on existing pages,"Screenshot showing text duplication
+
+This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3
+
+The entire test procedure is as follows:
+
+System Environment:
+Windows7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit
+
+Steps:
+Enable ULS IME hindi transliteration
+Take a caret to the end of the first paragraph using the mouse (i.e click at
+the end of the first paragraph to take the caret there.)
+Input ag
+Output will be अग् as expected but with incorrect selection as reported in the comment linked above
+Further input a
+This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.
+
+What should have happened:
+The original output अग् should have been changed to अग at the end of the first paragraph.
+
+So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated.
+
+Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11824}",1379764980,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-qb2engnawhn3el2wqyzm,task_description,resolved
+VisualEditor: Text duplication when using jquery.IME on existing pages,"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.",1453749108,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qb2engnawhn3el2wqyzm,task_subcomment,NA
+VisualEditor: Text duplication when using jquery.IME on existing pages,Automatic Incorrect caret movement has been reported separately as Bug 54424,1379768763,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-qb2engnawhn3el2wqyzm,task_subcomment,NA
+browsertests: configure Zuul,"This is a sub project of bug 53697 https://www.mediawiki.org/wiki/Continuous_integration/Browser_tests
+
+It covers setting up the Zuul configuration to trigger browser tests. From the wiki page:
+
+The exact workflow would need to be figured out with the VisualEditor team. A first step would be to run the browser tests after a change has been merged and report back in Gerrit for their information.
+At first we will only want to run browser tests after a change has been merged. This let us load the system progressively without disrupting the VisualEditor authors.
+
+We can later on make Zuul report back in Gerrit a message stating the result of the tests, that will raise awareness among developers and they can work on fixing the unsuccessful tests. Additionally, we can have the browser tests to be triggered on every patchset, the labs instance load will have to be carefully monitored.
+
+Once tests are properly passing and the setup has been proven useful, we can make Zuul to block patchsets not passing the browser tests. The developers would then be required to fix the code or the test to have their change merged in
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1379695800,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-3qnp2v5yec7kxc653kc7,task_description,resolved
+browsertests: configure Zuul,Being added on an ongoing basis. Already added the ULS browser tests in the Zuul 'test' pipeline.,1385993818,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-3qnp2v5yec7kxc653kc7,task_subcomment,NA
+browsertests: configure Zuul,"CCing Željko Filipin on any continuous bug related to browsertests. Main tracking bug is: bug 53697, see https://bugzilla.wikimedia.org/showdependencytree.cgi?id=53697&hide_resolved=0",1379705800,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-3qnp2v5yec7kxc653kc7,task_subcomment,NA
+Add _rtselser end point in web api,"For end users and VE folks the non-selser _rt end point is often confusing, as it shows diffs that are normally avoided by selser. It would be useful to add a _rtselser end-point that serializes to HTML, re-parses that HTML (to catch foster-parenting issues) and then serializes it back with selser enabled.
+
+This will provide us with a quick sanity check for the selser code, and a better link for end users and VE to establish that something has indeed dirtied the DOM.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379611080,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-g5cwud3usjdr2bplpq6x,task_description,resolved
+Add _rtselser end point in web api,"Change 85990 merged by jenkins-bot:
+Bug 54339: Add _rtselser endpoint in web API
+
+https://gerrit.wikimedia.org/r/85990",1380131239,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+Add _rtselser end point in web api,"Change 85990 had a related patch set uploaded by Marcoil:
+Bug 54339: Add _rtselser endpoint in web API
+
+https://gerrit.wikimedia.org/r/85990",1380124213,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+Add _rtselser end point in web api,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Just for clarity, this will catch any unhandled fostered parenting issues in
+> > Parsoid.
+> Depending on how it's written, it could catch these (or have a mode to detect
+> these), by serializing the DOM out to a string and parsing it back in again.
+
+Yes, that is the intention. 
+
+> With or without this kind of DOM normalization though, mass-testing articles
+> to find selser bugs would be very awesome.
+
+We haven't yet figured out how to do this reliably. We still have same problem that I mentioned on the VE/F page about absence of an oracle to tell us authoritative wikitext to compare against. So, the best we can do is simulate null edits, or modify text, etc. But those are, for the most part, the uninteresting bits of selser testing -- the most interesting bugs show up with more complex edits, and that is the bit that needs to be solved for using it in an automated manner in rt-testing.",1379617066,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+Add _rtselser end point in web api,"(In reply to comment #1)
+> Just for clarity, this will catch any unhandled fostered parenting issues in
+> Parsoid.
+Depending on how it's written, it could catch these (or have a mode to detect these), by serializing the DOM out to a string and parsing it back in again.
+
+With or without this kind of DOM normalization though, mass-testing articles to find selser bugs would be very awesome.
+
+> VE-DOM-dirtying will not be caught by this.
+Fortunately, VE does its own detection for this at run time: https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=visualeditor-needcheck",1379613552,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+Add _rtselser end point in web api,"Just for clarity, this will catch any unhandled fostered parenting issues in Parsoid. VE-DOM-dirtying will not be caught by this.",1379611334,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getOffset' of null"" triggered using jquery.IME","Screenshot of Console Error and Blanked Page
+
+This bug was found when testing per the sixth and seventh comment at Bug 53708
+This is very similar to Bug 54331 , however, this one is reproducible.
+
+System Environment:
+Windows7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/Project:Sandbox?veaction=edit
+
+Steps to reproduce:
+Enable ULS IME hi transliteration
+Input the following (below the 'Testing Area' heading):
+agar[SPACE][SPACE][BACKSPACE][BACKSPACE]
+
+What happens:
+Apart from a bunch of buggy behaviour described in the seventh comment at Bug 53708 , the template is entirely removed and the following console error shows up once the second [BACKSPACE] is pressed:
+
+Uncaught TypeError: Cannot call method 'getOffset' of null load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:231
+ve.ce.Document.getNodeAndOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:231
+ve.ce.Surface.showSelection load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:287
+ve.ce.Surface.onChange load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:274
+oo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139
+ve.dm.Surface.change load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:86
+ve.ce.Surface.handleDelete load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:286
+ve.ce.Surface.onDocumentKeyDown load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:267
+proxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10
+ve.EventSequencer.onEvent load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:19
+(anonymous function) load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:18
+jQuery.event.dispatch load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:45
+elemData.handle.eventHandle load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:38
+
+The file urls are:
+
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*
+
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11639}",1379606220,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-fkizlik3mtnbtsqbgnqs,task_description,resolved
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getOffset' of null"" triggered using jquery.IME","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.",1453749185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fkizlik3mtnbtsqbgnqs,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","This bug was found when testing per the sixth and seventh comment at Bug 53708
+It seems somewhat heisenbuggy and I haven't been able to reproduce it yet. However, I'm sure of the steps which caused it.
+Reporting this so that it's documented in case it is ever seen again.
+
+System Environment:
+Windows7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/Project:Sandbox?veaction=edit
+
+Steps to reproduce:
+Enable ULS IME hindi (hi) transliteration (labelled लिप्यंतरण)
+Input the following:
+agar[SPACE][SPACE][BACKSPACE]
+
+What happens:
+Apart from a bunch of buggy behaviour (described in the seventh comment at Bug 53708 ), the following console error shows up once the [BACKSPACE] is pressed:
+
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:106
+ve.dm.Document.getNodeFromOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:106
+ve.dm.Surface.change load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:84
+ve.ce.Surface.onSelectionChange load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:275
+oo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139
+ve.ce.SurfaceObserver.pollOnceInternal load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:292
+ve.ce.SurfaceObserver.pollOnce load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:291
+ve.ce.SurfaceObserver.timerLoop load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:290
+proxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10
+
+The file urls are:
+
+For the last line:
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z
+
+For all other lines:
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*
+
+Also, the template's formatting was gone with the input hindi text appearing alongside the template text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379605200,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-f3qthugptx3szx2kr56o,task_description,resolved
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","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.",1453749233,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","After Comment 3, reloading the page by pressing the return key in the address bar gave the following error:
+
+Uncaught RangeError: Maximum call stack size exceeded
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload",1379611711,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","Editable content in Read mode
+
+Further, after everything stated in Comment 1 has happened, if VE editing is canceled and the js prompt about losing unsaved changes is confirmed, the second error still continues. The tab is set to Read instead of Edit, however the content is still editable and the VE toolbar remains visible (although it doesn't seem to work).
+
+**Attached**: {F11633}",1379611271,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME",Related/similar bug: Bug 51526,1379610367,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","Screenshot showing original error and changed template formatting
+
+I've been able to reproduce this bug in the same system environment on the same test url with the following steps:
+
+Enable ULS hi transliteration
+Input a[SPACE][BACKSPACE]a
+
+The error as specified above shows up.
+
+Pressing a space after this brings up the following errors:
+
+Error 1:
+
+Uncaught TypeError: Cannot call method 'insertBefore' of null load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:239
+ve.ce.BranchNode.onSplice load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:239
+oo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139
+ve.dm.BranchNode.splice load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:44
+(anonymous function) load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…back%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:3
+ve.dm.Document.rebuildNodes load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:107
+ve.dm.DocumentSynchronizer.synchronizers.rebuild load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:117
+ve.dm.DocumentSynchronizer.synchronize load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:119
+ve.dm.TransactionProcessor.process load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:59
+ve.dm.Document.commit load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:104
+ve.dm.Surface.change load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:84
+ve.ce.Surface.handleInsertion load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:282
+ve.ce.Surface.onDocumentKeyPress load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:268
+proxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10
+ve.EventSequencer.onEvent load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:19
+(anonymous function) load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:18
+jQuery.event.dispatch load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:45
+elemData.handle.eventHandle load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:38
+6
+
+Error 2:
+Uncaught Error: offset 805 out of bounds load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:150
+ve.dm.ElementLinearData.getAnnotationIndexesFromOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:150
+ve.dm.ElementLinearData.getAnnotationsFromOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:150
+ve.ce.Surface.onContentChange load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:277
+oo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139
+ve.ce.SurfaceObserver.pollOnceInternal load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:292
+ve.ce.SurfaceObserver.pollOnce load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:291
+ve.ce.Surface.documentOnBlur load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:264
+proxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10
+jQuery.event.dispatch load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:45
+elemData.handle.eventHandle load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:38
+
+File urls:
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z
+
+The second error keeps repeating. Also, changing tabs makes the count in the chrome console go up.
+
+It also repeats each time a mouse click is done at the current caret position. It also repeats if the caret is taken to a different position in the text using the mouse or the arrow keys.
+
+**Attached**: {F11632}",1379608431,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,"I am trying to VEdit https://en.wikipedia.org/w/index.php?title=User:Elitre_%28WMF%29/Sandbox&oldid=573480590&veaction=edit , which is a blank version of my sandbox. There's a lot of white space between the title of the page and the point where I can start adding text, and although the source editor says the page is really empty, looks like there's still something there.
+
+If I hover with the mouse right below the comma in the tagline ""Wikipedia, the free encyclopedia"", the cursor changes as if there's an invisible link.
+1) Right under the comma, the ""link"" points to my userpage (it's clickable, and the page will open in the same tab);
+2) some pixels below, the link will point to [[Help:Page History]];
+3) going further down, it points to a diff of the sandbox.
+There are other points in the page which trigger the links, but the page history one is not easy to spot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52243
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58063",1379602440,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_description,resolved
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,"Change 107133 merged by jenkins-bot:
+Hide #contentSub properly
+
+https://gerrit.wikimedia.org/r/107133",1389633324,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_subcomment,NA
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,"Change 107133 had a related patch set uploaded by Jforrester:
+Hide #contentSub properly
+
+https://gerrit.wikimedia.org/r/107133",1389626449,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_subcomment,NA
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,Only partly a dupe of bug 52243.,1388963194,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_subcomment,NA
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,"The hidden text that causes this, if selected and copy/pasted elsewhere, reads:
+< User:Elitre (WMF)
+This is an old revision of this page, as edited by Elitre (WMF)  (talk | contribs) at 10:57, 18 September 2013. It may differ  significantly from the current revision.
+Revision as of 10:57, 18 September 2013 by Elitre (WMF)  (talk | contribs)
+
+This is reported as being common also in articles.
+Thanks.",1379667965,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_subcomment,NA
+Wikitech: Install TemplateData extension,"VisualEditor is installed already. Would be nice to have TemplateData as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379590500,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ufskmzg3xlrkksp26qtv,task_description,resolved
+Wikitech: Install TemplateData extension,"This seems to have been done, I think by the wikitech config/deployment changes.",1426690252,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ufskmzg3xlrkksp26qtv,task_subcomment,NA
+(Re-) unify data and metadata,"Because about half the code in the DM is solely there to keep this delicate data structure together, and now that we don't need ±1 cursoring it seems like a lot of effort for nothing.
+
+The behaviour it provides (protecting metadata from deletion) can all be done in the transaction builders, and in fact we already do this for internal lists)
+
+Going forward this will make multi user editing a lot easier to.
+
+That said this is going to be a massive commit.
+
+-----
+
+Currently, MetaItems are stored outside the main linear data structure, in a separate meta linear data structure. This complicates the processing of linear data: transaction processing, rebasing, serialization/deserialization etc, and makes it harder to reason about document correctness. Instead:
+* Store metadata as block nodes in the main data list
+* On conversion from HTML, hoist metadata found in a content position to a legal structural position
+* On conversion back to HTML, roundtrip metadata hoisted from unmodified content branch nodes back into the original content position
+* When deleting across metadata (e.g. <p>foo[-</p><meta/><p>-]bar</p>), hoist metadata to a legal structural position as necessary",1379550420,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vstc34ukjrx4agdul6rw,task_description,resolved
+(Re-) unify data and metadata,Gosh.,1517245931,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 405751 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (c5fddd508)
+
+[[https://gerrit.wikimedia.org/r/405751]]
+",1517245035,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 405751 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (67548dc57)
+
+[[https://gerrit.wikimedia.org/r/405751]]
+",1516647701,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 385492 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/385492]]
+",1516647435,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 336929 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] [WIP] [PULLTHROUGH] MW changes for the meta-data inlining commit
+
+[[https://gerrit.wikimedia.org/r/336929]]
+",1515616786,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 336925 abandoned by Divec:
+WIP: [BREAKING CHANGE] Store metadata as block nodes in the main data list
+
+Reason:
+Moved to Ib5174b0dcba1c24f44d889e08140bee31a064011
+
+[[https://gerrit.wikimedia.org/r/336925]]",1508543685,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 385492 had a related patch set uploaded (by Divec; owner: Divec):
+[VisualEditor/VisualEditor@master] WIP: [BREAKING CHANGE] Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/385492]]
+",1508543616,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 336925 had a related patch set uploaded (by Jforrester):
+[BREAKING CHANGE] Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/336925]]
+",1486679038,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 336899 had a related patch set uploaded (by Jforrester):
+Update VE core submodule to master (0dfc50a88)
+
+[[https://gerrit.wikimedia.org/r/336899]]
+",1486675750,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 314568 merged by jenkins-bot:
+Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/314568]]",1486668402,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 314568 had a related patch set uploaded (by Jforrester):
+Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/314568]]
+",1486584604,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,We now have ve.dm.Node.static.isDeletable.,1463763857,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+VisualEditor: ResizableNode should be able to live-preview the node it's resizing as you drag,"This would also solve the problem of the resize marker having to snap into the right position at the end of a drag if you use the wrong handle (or any handle if the image is centred)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379549580,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nqqibdaciuaeyw2lnzmy,task_description,resolved
+VisualEditor: ResizableNode should be able to live-preview the node it's resizing as you drag,"Change 89814 merged by jenkins-bot:
+Resizable node live preview
+
+https://gerrit.wikimedia.org/r/89814",1381926939,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nqqibdaciuaeyw2lnzmy,task_subcomment,NA
+VisualEditor: ResizableNode should be able to live-preview the node it's resizing as you drag,"Change 89814 had a related patch set uploaded by Esanders:
+Resizable node live preview
+
+https://gerrit.wikimedia.org/r/89814",1381839789,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nqqibdaciuaeyw2lnzmy,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of the sentence/paragraph when using jquery.IME,"**Author:** `renukaalurkar`
+
+**Description:**
+1)Logged in to http://en.wikipedia.beta.wmflabs.org/wiki/Main_Page
+2)Go to your user page.
+3)Click on Languages/cog, select Input and click on Enable Input tools.
+4)Click on Edit beta tab.
+5)Click on More, and using Media, select a couple of pictures
+6)Click on the tiny keyboard/typewriter and select language as Hindi or Telugu
+7)Now start entering text in Hindi or Telugu.
+
+Observations:
+1)After typing a few letters, the cursor jumps back to the beginning of the sentence.
+2)Sometimes, when Enter is hit, the cursor goes back to the beginning of the paragraph.
+3)Sometimes, when Enter is hit one of the images disappears.Write some more and the other image also disappears.
+4)Click on Save page button
+5)Now both the images are visible again.
+
+Observed on Firefox 24.0 and Chrome 29.0.1547.66
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379529000,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hu7ibauxmtlo3ljy4pvq,task_description,resolved
+VisualEditor: Cursor jumps to the beginning of the sentence/paragraph when using jquery.IME,"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.",1453748296,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hu7ibauxmtlo3ljy4pvq,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of the sentence/paragraph when using jquery.IME,"I've set my Language settings on https://en.wikipedia.org to using native keyboard for Hindi input.
+
+> 5)Click on More, and using Media, select a couple of pictures
+> 6)Click on the tiny keyboard/typewriter and select language as Hindi or Telugu
+
+Where exactly? In the ""alternative caption"" field of the ""Insert Image"" dialog? Some other field? The text of the page you edit?
+At least for लिप्यंतरण and इनस्क्रिप्ट I cannot reproduce any jumping back of the cursor in the ""alternative caption"" field.
+
+The steps to reproduce this problem are a bit unclear (but probably only because the user interface has changed since this problem was reported). 
+
+Clarification highly welcome.",1425553166,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hu7ibauxmtlo3ljy4pvq,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"? should be ؟ icon
+
+For  Notification Tool for  RTL languages Please change ""?"" icon in attached image to RTL icon
+
+See @Amire80's comment.  Not the same for all languages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54252
+
+**Attached**: {F11507}",1379514480,PHID-USER-dswbdv7ibhsefllcqarz,PHID-TASK-blsktvyvk2zcdw2o4yue,task_description,resolved
+RTL for Notification Tool: ? should be ؟ icon,"I believe that this is now long-since fixed, since we moved to OOjs UI.",1488434919,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"VisualEditor seems to deal with this issue with the help button (also presented as ?)
+
+It might help checking what lists they have to when to flip the question mark and when not to, and use that same strategy in this case.",1437684531,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"**nzmoihue** wrote:
+
+Seems dvwiki is also using ""؟"" http://dv.wikipedia.org/wiki/%DE%88%DE%A8%DE%86%DE%A8%DE%95%DE%A9%DE%91%DE%A8:%DE%A2%DE%A7%DE%82%DE%B0%DE%89%DE%AA_%DE%80%DE%AE%DE%85%DE%AA%DE%87%DE%A6%DE%81%DE%A8 (find ""؟"" on that bug using Ctrl+F)
+
+I guess something like https://github.com/wikimedia/mediawiki-core/blob/9ea365dcb2f1390e117767e0ead4a5655ad4631d/skins/common/shared.css#L240 is needed for reversed question mark",1383344041,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"This is not needed for all languages.
+
+It is definitely not needed for Hebrew and Yiddish.
+
+It is *probably* needed for all languages written in the Arabic script.
+
+I'm not sure about Divehi (dv) and Aramaic (arc).",1381915440,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"**bsitu** wrote:
+
+Oops, the patch referenced the wrong bug",1381518303,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"Change 89249 had a related patch set uploaded by Bsitu:
+Notification overlay is partially hidden in RTL language
+
+https://gerrit.wikimedia.org/r/89249",1381518148,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"**bsitu** wrote:
+
+
+
+%%%*** This bug has been marked as a duplicate of bug 54252 ***%%%",1380239232,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/252,1379969376,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"To devs:
+You just need to add element like ""#mw-echo-overlay-moreinfo-link"" but with a ""transform:scaleX(-1);"" [1] to the ext.echo.overlay.css
+and call that element instead the ltr one in ext.echo.overlay.js when .sitedir-rtl is true [2]
+
+[1]: http://nicolasgallagher.com/css-background-image-hacks/
+[2]: https://www.mediawiki.org/wiki/Manual:Interface/IDs_and_classes
+
+Best",1379681684,PHID-USER-ctchvhisqfvk4rz7nt7d,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+VisualEditor: Duplicating references groups,"See
+https://en.wikipedia.org/w/index.php?title=Fizeau_experiment&diff=573001070&oldid=572299847 - the user corrected a typo and this resulted in the references groups getting duplicated.
+Reproduced in 
+https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=573341379 and https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=573340833 while just testing wikilinks, as you can see. My first attempt to reproduce this actually resulted in more weird (although known, I think) behaviour: https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=573176079 .
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379500080,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-c45wkid72cnbk33nmpdr,task_description,resolved
+VisualEditor: Duplicating references groups,"I've tried to reproduce this using @Elitre's testcases, but couldn't; I'm tentatively closing as fixed.",1429223923,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-c45wkid72cnbk33nmpdr,task_subcomment,NA
+VisualEditor: Duplicating references groups,I wonder if this is still valid.,1421888557,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-c45wkid72cnbk33nmpdr,task_subcomment,NA
+VisualEditor: Duplicating references groups,"https://fr.wikipedia.org/w/index.php?title=Archives_sociales_suisses&diff=96769347&oldid=96768850
+
+https://fr.wikipedia.org/w/index.php?title=Jeu_vid%C3%A9o_ind%C3%A9pendant&diff=95172709&oldid=95071765",1379575952,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-c45wkid72cnbk33nmpdr,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,"Edit a page with One&nbsp;Two which displays as One Two.  Select the entire text, copy, past at end of the string.  Displays in VE fine at first.  Saving however produces One&nbsp;TwoOneTwo which displays as One TwoOneTwo. 
+
+Originally from 
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=573462315&oldid=573461696
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379493780,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_description,resolved
+Parsoid: mw:Entity not preserved if data-parsoid missing,"Change 89356 merged by jenkins-bot:
+Bug 54262: Serialize new entity to its contents
+
+https://gerrit.wikimedia.org/r/89356",1381535250,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,"(In reply to comment #2)
+> Is data-parsoid copied as well?
+
+Never mind, the title had that info.",1381532829,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,"Change 89356 had a related patch set uploaded by GWicke:
+Bug 54262: Serialize new entity to its contents
+
+https://gerrit.wikimedia.org/r/89356",1381532654,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,Is data-parsoid copied as well?,1381523696,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,"<p>Foo<span typeof=""mw:Entity"">&nbsp;</span>Bar</p>
+
+converts to
+
+FooBar
+
+which appears to be the problem",1381157310,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+VisualEditor: Show percentage of progress in loading animation,"DKqwerty at en.wp reports: ""Article Futurama took 58 seconds to load into VE, with the loading bar running the entire time. I think this is unacceptable as it is probably off-putting to inexperienced users. Further, the bar just fills, empties, fills, empties, etc. rapidly and continuously until the page is loaded... Would it be possible to make this bar actually indicate what percentage has been loaded so editors have at least a hint that something is being processed?""
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379426040,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-boxjw4hklzqeriwzj6zc,task_description,resolved
+VisualEditor: Show percentage of progress in loading animation,Implemented by Ed in https://gerrit.wikimedia.org/r/#/c/196583/,1427850989,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-boxjw4hklzqeriwzj6zc,task_subcomment,NA
+VisualEditor: Show percentage of progress in loading animation,"Not sure how we'd judge progress on this one, but it'd be useful for users…",1415881533,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-boxjw4hklzqeriwzj6zc,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Moving here the following proposals:
+<https://strategy.wikimedia.org/wiki/Proposal:Text_or_Syntax_driven_Charts,_Diagrams,_Graphs_and_more>
+<https://strategy.wikimedia.org/wiki/Proposal:Editable_Graphics>
+<https://strategy.wikimedia.org/wiki/Proposal:Markup_for_charts_and_graphs>
+(with some of the participants in cc).
+
+* «By now Wikipedia has markup/code for everything—math (TeX), parser functions, location maps, and even SVG is supported. However, what is notably missing from many articles (other than high-quality portraits) are graphs and charts.»
+* «There are many types of diagrams. The need for collaborative graphics is wide ranging, from map making to biochemical pathways to flow charts to genealogy to general charting. Each type of graphic has or could have a little language, XML or other representation to define graphics of that type succinctly. Whilst all can be presented as .pngs or .SVGs, the more succinct description is necessary for editability.»
+
+This is distinct from bug 43616 (Provide a way to create interactive 2D/3D timelines and infographics e.g. Java applets, AJAX, Flash) in that it's not about *interactive* stuff and that there are some existing extensions which someone should assess and develop for Wikimedia purposes. I'd also leave maps out of it because that's being addressed (at last) elsewhere.
+Part of it will be solved by bug 38271, but only to a degree.
+
+Mentioned extensions: [[mw:Extension:Graph]], [[mw:Extension:GnuplotBasic]], [[mw:Extension:Plotters]], [[mw:Extension:WikiPlot]].
+
+Keywords from the proposals: http://bloodgate.com/perl/graph/, Java .jar, Flash .swf, Silverlight .scr, ActiveX .ocx, Vector (.svg) .svg (XML), AnyWikiDraw, AnyWikiDraw, WikiPathways, WikiTex, Graph Plugin, DPL Bundle, TeX, gluplot, pgfplots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379420040,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_description,open
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Regarding ""enabling"", see https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment if someone is interested",1643486674,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","nowadays there is an extenstion https://www.mediawiki.org/wiki/Extension:Diagrams , would enabling it be a step into the right direction?
+",1643485832,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)",{T183689} is a related task.,1591962226,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Actionable tasks are not the only use case for Phabricator; cf. for example the #Epic project.  Additionally, I think tasks with subtasks are very preferable to projects in some cases as they themselves have a status, a dependency tree, etc.
+
+This task has two blocking subtasks that have not been resolved, so this task itself does not seem to be resolved.  AFAIUI, for example you don't want to work on T56222 (which is fine), but that also means that someone else needs to do the deed to convert those cladograms to Extension:Graph (or something else).",1450709456,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@nemo_bis, this is not what the bug description states. I think the better use of phabricator would be to create small, actionable, and well scoped tasks for specific feature, and mark those with some project tag for tracking. Otherwise this task grows infinitely large and not very useful. Having small tasks allows each feature to be discussed separately, and different devs can pick them up for implementation.  The only reason why we had the [tracking] tasks in Bugzilla was because there was no good support for tagging (projects).",1450703140,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","This bug's purpose is precisely to collect requirements and map alternatives. Two of them are identified by the two blockers. :) If you think the usecase behind that extension is another, please add to blockers.",1450683051,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Closing because we now have <graph>, and because this task is too broad. Please add more specific tasks for anything that's missing :)",1450639655,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@yurik OK.  I'm happy now.  Yep, I did know d3.js was under Vega, just previously had doubts that enough of that flexibility was exposed.   We can't have end users writing arbitrary javascript, so how the functionality is exposed really matters.
+
+I think I am already now OK with this task being closed.  There is obviously tons more to do and tons more that could be done, but the basics of the template driven transform of json to svg or canvas are there, which is what this task was asking for. 
+",1450639269,PHID-USER-tkx4pj3lyasedlwiiqzm,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@jamescrook, you mean [this example](http://vega.github.io/vega-editor/?mode=vega&spec=force)?  Also here is an [interactive version](http://vega.github.io/vega-editor/?mode=vega&spec=force_drag).
+
+As for d3 - vega is based on d3, so, in theory, most of the capabilities of d3 are exposed. But yes, we will have to dig through it.",1450638578,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@jamescrook, you mean [this example](http://vega.github.io/vega-editor/?mode=vega&spec=force)?  or an [interactive version](http://vega.github.io/vega-editor/?mode=vega&spec=force_drag)
+
+As for d3 - vega is based on d3, so, in theory, most of the capabilities of d3 are exposed. But yes, we will have to dig through it.",1450638556,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@Yurik , looking at the source for that tree it looks to be d3.js rather than Vega.",1450638376,PHID-USER-tkx4pj3lyasedlwiiqzm,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@yurik Vega doesn't currently seem to support those, at least not from the examples I can find.  They are motivating examples, so should not be swept under the carpet.  Biochemical pathways, flow charts and genealogy are all similar in being based on graphs (i.e. networks).  The Vega examples I am seeing are plots and maps.
+
+I am wondering why I am seeing no force directed layouts with Vega, although the visual encoding transform is described in the documentation.  If we can get even a basic demo of some biochemical pathway done using a force directed layout then I am cool with this task being closed.  Elaboration and prettiness can come later.",1450638292,PHID-USER-tkx4pj3lyasedlwiiqzm,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Just found this [expandable tree sample](http://bl.ocks.org/alcy/raw/7702db089164c493a705/) that seems to be based on Vega with some additional hacks. Might be interesting to build something similar.  And of course there are existing samples like [heatmap](http://vega.github.io/vega-editor/?mode=vega&spec=heatmap&renderer=svg) and many other that might be useful.
+CC: @jamescrook",1450636711,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@jamescrook, we have to narrow down this task, otherwise it sounds like ""create a platform that allows everything"", which is not really actionable.  From my reading of the description, Vega 2.0 should be able to handle most of it. If not, please create separate task that we can discuss.",1450633861,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Yurik, how does this address ""biochemical pathways to flow charts to genealogy"" from the description?
+
+",1450632768,PHID-USER-tkx4pj3lyasedlwiiqzm,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)",Should this be closed?  We now have interactive graphs/charts/etc: https://www.mediawiki.org/wiki/Extension:Graph/Demo#Vega_2.0_Interactive_Examples,1450622876,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Actually, this was one of the rawest ideas in the project list and is absolutely not usable for GSoC, unless a student comes who has an extremely clear idea of a feature to add and a plan for it. I'll move the possible project tag to T56222. The other blocker, T40271, would also be suitable, but I doubt it would benefit from GSoC (iterative GSoC cycles over the same problem rarely helped anything).",1423684001,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)",This task is about wikitext. VisualEditor support for the markup is a separate issue.,1423683746,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@qgil, I can totally see this becoming a GSoC project, but most of the mentorship would have to come from the UI/Visual Editor team because they have the expertise in building custom editors.  The student would build an editor with a dynamically updated viewer for the VE.  I already have a simplified version of that [[ http://graph.wmflabs.org/w/index.php?title=Graph:Stocks&action=edit | here ]] -- click preview and try changing the graph definition.",1423664307,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Wikimedia will [[ https://phabricator.wikimedia.org/T921 | apply to Google Summer of Code and Outreachy ]] on Tuesday, February 17. If you want this task to become a featured project idea, please follow [[ https://phabricator.wikimedia.org/project/view/1042/ | these instructions ]]. ",1423662263,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@Milimetric, @Yurik, is there a possible project related to this task that students like @Sumit could plan for in the context of Google Summer of Code 2015 (and that you would like to mentor)? Something about #MediaWiki-extensions-Graph ?",1423648511,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","> I'd like to take this up as a project. Is this still open for taking up and developing for this year?
+
+It's open, but not ready. Please choose one of the extensions mentioned by this report and start filing patches against them. When you find one you're comfortable developing, you'll know the area you can work on.",1423643389,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)",I'd like to take this up as a project. Is this still open for taking up and developing for this year?,1423640170,PHID-USER-ll7x5qhzru4lqz3xfdbm,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Sorry, meant to post last comment for bug 43616.  Yet, for this request, graph ext is still applicable, except that it is not wysiwyg unless some brave soul starts hacking a proper vega editor.",1411455023,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Graph extension might be applicable, even though it is not dynamic (yet), or even in production wikis, it does support various timelines, e.g. ""Napoleon"" at http://trifacta.github.io/vega/editor/ :)
+
+See https://www.mediawiki.org/wiki/Extension:Graph and samples at https://www.mediawiki.org/wiki/Extension:Graph/Demo 
+
+Discussion at https://meta.wikimedia.org/wiki/Wikimedia_Forum#Graphs.2C_Maps.2C_..._.28experimental.29",1411454841,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","I think what you're saying makes sense Pavel.  And no worries, to participate in this community you have to be really good at dealing with distractions.  I'm still waiting for someone else to help with mentoring on this important project.  I think someone with mediawiki extension development experience would be great.  Part of the reason I can't comment more, Pavel, is that I don't know anything about mediawiki extensions :)",1392061032,PHID-USER-vbyvvtbztxaeuaxelxx4,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Thanks, Dan. Vaga is excellent.
+
+But, for example, I need a template to draw a bar of population.
+The template takes a comma-separated list of cities.
+The population is taken from the wikidata.
+
+{{MyTemplate
+| cities=London,Berlin,Paris
+}}
+
+Source of wikipage Template:MyTemplate:
+
+... Some wiki markup ...
+<phptag>
+if ( isset($args[cities]) ) {
+  $cities = explode( $delimiter, $args[cities] );
+  $population = AskWikidata( 'Give me population of cities', $cities );
+  $data = array_combine($cities, $population);
+  echo new Vega( 
+      $data,
+      [ 'size'=>[400,200], 'scales'=>['x'=>'cities', y=>'population'] ] 
+    );
+}
+</phptag>
+... Some wiki markup ...
+
+There are:
+* functions 'explode', 'array_combine' is hooks of the extension PphTags Functions. (already done)
+* function 'AskWikidata' is fictional, but can be implemented as hook of some extension
+* objects 'Vega' is fictional, but can be implemented as hook of some extension
+* 'if', 'isset', 'echo' and '[...] (array definition)' is functions of extension PhpTags (already done)
+
+Suppose I'm developer of the extension Vega.
+I should just take the javascript source code from Vega and register hook in the extension PhpTags.
+
+source of Vega.php:
+
+$wgHooks['PhpTagsRuntimeFirstInit'][] = 'VegaExtension::initializeRuntime';
+
+class VegaExtension {
+  public static function initializeRuntime() {
+    \PhpTags\Runtime::setObjectsHook( 'VegaObject', array('Vega') );
+  }
+}
+
+class VegaObject extends PhpTags\BaseHooks {
+  public static function onObjectHook( ... ) {
+    // some code
+  }
+}
+
+The Class VegaObject will receive the arrays of data and parameters from the PhpTags,
+and when the function 'echo' is called returns all the necessary data for drowing the bar on the wikipage.
+a large part of the code (such as processing of various parameters) have to be implemented in the class PhpTags\BaseHooks.
+The class VegaObject will just have to inform PhpTags that it needs 'vega.min.js' and convey to one ready parameters.
+Since it is very simple, similar extensions can be done in one day.
+
+Maybe I'm writing all this is off topic, forgive me please.
+But I can not find anyone interested in this.
+I guess I'm looking for not out there, or can not speak understandable.
+Maybe I just doing nonsense and distract people from her work, I do not know.",1391663088,PHID-USER-qdblhomoh775qwgc6rra,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Dan, thank you for pushing this proposal. If you want to jump to the GSoC 2014 train you need to:
+
+* Take https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Support_for_text.2Fsyntax.2Fmarkup_driven_or_WYSIWYG_editable_charts.2C_diagrams.2C_graphs.2C_flowcharts_etc. , shorten the title, expand the description (one paragraph is enough), and move it under https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Featured_project_ideas
+
+* Find a second mentor.
+
+The sooner the better, since Wikimedia will be evaluated by the GSoC organizers in the next 1-2 weeks. You will know you are ready when your project looks great at https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014
+
+More: http://lists.wikimedia.org/pipermail/wikitech-l/2014-February/074277.html",1391623649,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Thanks Pavel.  I like the syntax you mention.  The advantage to using Vega JS syntax would be that it's a healthy active project and we get the parser, etc. for free.  Check it out if you haven't had a chance, I linked to it above.",1391615361,PHID-USER-vbyvvtbztxaeuaxelxx4,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","I'd suggest using a scripting language as markup for the editable charts, diagrams, graphs, flowcharts etc.
+
+For end users this may be like the example:
+
+== Extension:Graph ==
+
+ G { ""Bonn"" --> ""Berlin"" [ style: bold; ] }    
+As
+Graph( [ ""Bonn"" => [ ""Berlin"", ""style""=>""bold"" ] ] );
+or 
+$bonn = node(""Bonn"");
+$bonn->linkTo( node(""Berlin"", ""bold"") );
+Graph( $bonn );
+
+== Extension:WikiPlot ==
+
+<wikiplot height=""200"" width=""200"" caption=""Simple plot"" xspan=""-100;100"" yspan=""-100;100"">
+        <graph label=""Graph 1."" color=""255,0,0"">x+4</graph>
+        <graph label=""Graph 2."">3*x-3</graph>
+</wikiplot>
+
+as 
+
+$plot = new Plot( ['height'=>200, 'width'=>200, 'caption'=>'Simple plot', 'xspan'=>[-100, 100], 'yspan'=>[-100, 100] ] );
+
+or 
+
+$plot = new Plot();
+$plot->height = 200;
+$plot->width = 200;
+$plot->caption = ""Simple plot"";
+$plot->xspan = [-100, 100];
+$plot->yspan = [-100, 100];
+
+and
+
+$plot.addGraph( ['x+4', 'label'=> 'Graph 1.', 'color'=>[255,0,0] ]);
+
+$graph = new Graph( ""3*x-3"" );
+$graph->label = 'Graph 2.'
+$plot.add( $graph );
+
+echo $plot;
+
+It looks like directly code execution, but it is not.
+I did mw:Extension:Foxway for testing possibility of this. I ascertained that this may work and may work quickly.
+Now I do new mw:Extension:PhpTags. There any extension can register a hook as a constant, function or object.
+So far I have only worked on the functions and constants, and did not start work on objects.
+I am sure that the PhpTags will cover all the needs and will be convenient and powerful tool.
+I would like to find someone interested in discussing this.",1391598767,PHID-USER-qdblhomoh775qwgc6rra,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","tl;dr; I would be interested in being a mentor here, and probably collaborating until a solution is reached.
+
+We've done some thinking about this while we developed Limn [1] last year.  I believe Limn was headed in the wrong direction, but we (team analytics) are interested in solving this problem and it would be nice to combine efforts with anyone that is also interested.  Currently, I believe that Vega JS [2] is a very promising library.  It has a great mixture of simplicity and power.
+
+My personal opinion is that creating and editing infographics would work much like Visual Editor does.  There would be a simple JSON editor on the front end, which could evolve over time.  When saved, this would use a server to generate static infographics for consumption by the cache layer.  The dynamic infographic could be accessed through a link on the static image.  The cache could be repopulated with up-to-date infographics periodically if they depend on external data.  For this vision, Vega JS is quite suitable as it can generate PNGs server side for example.
+
+
+[1] https://github.com/wikimedia/limn
+[2] http://trifacta.github.io/vega/",1391530733,PHID-USER-vbyvvtbztxaeuaxelxx4,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","(In reply to comment #4)
+> Should this project be still listed in that page? 
+
+Yes.
+
+> If not, please remove it.
+> If
+> it still makes sense, then it could be moved to the ""Featured projects""
+> section
+> if it has community support and mentors.
+
+It lacks a mentor, plus (probably) someone to set a direction/the requirements (who may or not be the same person).",1385912944,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","**vladjohn2013** wrote:
+
+Hi, this project is still listed at  https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Support_for_text.2Fsyntax.2Fmarkup_driven_or_WYSIWYG_editable_charts.2C_diagrams.2C_graphs.2C_flowcharts_etc. 
+
+Should this project be still listed in that page? If not, please remove it. If it still makes sense, then it could be moved to the ""Featured projects"" section if it has community support and mentors.",1385912632,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Is there an interest in proposing this project for Outreach Program for Women?
+If so, and if there at least one mentor for it. please move it to the ""Featured projects"" section. This way it will be automatically transcluded in
+https://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7
+
+Thank you!",1383164696,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Correction, the links are: [[mw:Extension:WikiTeX]] (and [[mw:Extension:WikiTex]]).",1379434198,PHID-USER-wuic4cpqakaykj6cpvt5,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","What about reviving [[Extension:WikiTeX]] (not to be confused with [[Extension:WikiTex]])? This would have done graphs, plots, and more. It would be handy for it to also support simple circuit diagrams.",1379433154,PHID-USER-wuic4cpqakaykj6cpvt5,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"See https://github.com/mdevils/node-jscs
+
+This is the first tool I've seen in the category of asserting coding style for javascript that actually looks like it is worth looking into further.
+
+I intend to experiment with it in the near future for 1 or 2 projects, first in non-voting mode and perhaps later to become a standard enabled job for many projects.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1379415660,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2mkgo6douokimv6febmw,task_description,resolved
+Jenkins: Use node-jscs as checkstyle for javascript coding style,">>! In T56218#973118, @adrianheine wrote:
+> Cool, thanks. I added `npm test`, although I didn't go through grunt since we are not running any other grunt jobs, yet:
+> 
+> * Wikibase: https://gerrit.wikimedia.org/r/#/c/184591/
+> * integration/config: https://gerrit.wikimedia.org/r/#/c/184592/
+
+That's quite alright. If you don't need do run bash commands like `mv`, `cp`, `rm`, `ln` etc. which might not work cross-platform if put inside `scripts.test` (so you'll want to use a nodejs script or Grunt task for that); Running programs like jscs and jshint directly is perfectly fine and actually quite common. I've recently started to use this more often as well. Only use Grunt when there's a need for it. This avoids added complexity, needless abstraction, and indirect dependencies on the underlying framework (e.g. jscs/jshint) which can be quite annoying since it doesn't like being pinned to a direct version that way.
+
+http://blog.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool/
+http://ponyfoo.com/articles/choose-grunt-gulp-or-npm",1426088335,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Cool, thanks. I added `npm test`, although I didn't go through grunt since we are not running any other grunt jobs, yet:
+
+* Wikibase: https://gerrit.wikimedia.org/r/#/c/184591/
+* integration/config: https://gerrit.wikimedia.org/r/#/c/184592/",1421144139,PHID-USER-m2zne2efu3rgmre73nl7,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,">>! In T56218#972923, @adrianheine wrote:
+> Is there work being done to get this run on ci? I'd like to push this for Wikibase as well :)
+
+You will need a package.json and a npm 'test' entry point with a devDependencies for grunt-jscs.  From there we can add a Jenkins job that invokes 'npm test' and that should run jscs.
+
+Example:
+
+https://gerrit.wikimedia.org/r/#/c/100732/
+
+More details at https://www.mediawiki.org/wiki/Continuous_integration/Test_entry_points#JavaScript :-)",1421140918,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,Is there work being done to get this run on ci? I'd like to push this for Wikibase as well :),1421137099,PHID-USER-m2zne2efu3rgmre73nl7,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,Sounds good to me Timo. That nicely scale up CI to developers :-),1409164241,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"The bug is to figure out how to properly do it. Which I define by hacking it together for one repo, and as you repeat it for more repos you refine it until it seems sensible/maintainable.
+
+I think we've reached that point. Any further repos that want it, can enable it the same way other pipelines are introduced. By patching their Gruntfile or adding a new npm-test pipeline.",1409154874,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Is this intended to be a tracking bug for every repo, a bug for it to be done automatically for all repos and then repos that now break need to fix themselves, or can it be marked as FIXED?",1395766504,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 111963 merged by jenkins-bot:
+Set up node-jscs via Grunt (and pass it)
+
+https://gerrit.wikimedia.org/r/111963",1395730881,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 111963 had a related patch set uploaded by Krinkle:
+[WIP] Set up node-jscs via Grunt (and pass it)
+
+https://gerrit.wikimedia.org/r/111963",1391746605,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 100732 merged by jenkins-bot:
+Set up node-jscs, pass it, and configure in local Gruntfile
+
+https://gerrit.wikimedia.org/r/100732",1387317987,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 100732 had a related patch set uploaded by Krinkle:
+Set up node-jscs, pass it, and configure in local Gruntfile
+
+https://gerrit.wikimedia.org/r/100732",1386727450,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Now merged locally in the repo for VisualEditor, and appears to be adding value; moving back to NEW for consideration to be added to jenkins for automated running.",1386355646,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 99596 merged by jenkins-bot:
+Set up node-jscs, pass it, and configure in local Gruntfile
+
+https://gerrit.wikimedia.org/r/99596",1386355303,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 99596 had a related patch set uploaded by Krinkle:
+Set up node-jscs, pass it, and configure in local Gruntfile
+
+https://gerrit.wikimedia.org/r/99596",1386297732,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"node-jscs would be purely for coding style, not code quality (which is what jshint is primarily for).
+
+Although there are a few minor things that jshint does in the realm of coding style, those are arguably code quality as well (like using of braces in if/else blocks).
+
+This would allow us to validate the complete coding style (especially with regards to whitespace), which right now is mostly enforced by leaving comments in code review and fixup commits pointing to [[mw:CC/JS]].",1379461361,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,Unrelated.,1379460821,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,Is that a replacement for JSHint or unrelated?,1379433243,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+VisualEditor: Language link dialog should show language names and two-letter codes,"e.g. fr -> Français, cy -> Cymraeg
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379014140,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-w7k7v4pcanwqeehqmoyp,task_description,resolved
+VisualEditor: Language link dialog should show language names and two-letter codes,"Change 98284 merged by jenkins-bot:
+Show full language names in the MW language dialog
+
+https://gerrit.wikimedia.org/r/98284",1386694855,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w7k7v4pcanwqeehqmoyp,task_subcomment,NA
+VisualEditor: Language link dialog should show language names and two-letter codes,"Change 98284 had a related patch set uploaded by Esanders:
+Show full language names in the MW language dialog
+
+https://gerrit.wikimedia.org/r/98284",1385827780,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w7k7v4pcanwqeehqmoyp,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Around the time when VE started to support editing of pres we started to get dirty diffs like this:
+
+http://www.mediawiki.org/w/index.php?title=Parsoid&diff=779292&oldid=777387
+
+This might either be a selser issue, or VE dirtying the DOM.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379007960,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-six3hr3num5ryuty64kf,task_description,resolved
+VisualEditor: <pre> tags have leading whitespace removed,*** Bug 53775 has been marked as a duplicate of this bug. ***,1379613849,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Change 84896 merged by Catrope:
+Fix check for preformatted when stripping whitespace
+
+https://gerrit.wikimedia.org/r/84896",1379545395,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Change 84896 had a related patch set uploaded by Catrope:
+Fix check for preformatted when stripping whitespace
+
+https://gerrit.wikimedia.org/r/84896",1379545270,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Change 84332 merged by jenkins-bot:
+Fix check for preformatted when stripping whitespace
+
+https://gerrit.wikimedia.org/r/84332",1379466707,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Change 84332 had a related patch set uploaded by Esanders:
+Fix check for preformatted when stripping whitespace
+
+https://gerrit.wikimedia.org/r/84332",1379346257,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"There's a check tag on the edit, so VE dirtied something somewhere. That may or may not explain the whole bug, but we should fix it.",1379008191,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"For BLP's and disambiguation pages on the English Wikipedia, an extra edit notice is provided through the https://en.wikipedia.org/wiki/Wikipedia:EDITINTRO system using Extension:InputBox and some code in MediaWiki:Common.js. VisualEditor does not work with Extension:InputBox, so the edit notice is not displayed. 
+
+This hack is being used in several Wikimedia wikis besides the English Wikipedia:
+
+* https://ja.wikipedia.org/wiki/MediaWiki:Common.js
+* https://zh.wikipedia.org/wiki/MediaWiki:Common.js
+* https://vi.wikipedia.org/wiki/MediaWiki:Common.js
+
+See also [[https://www.wikidata.org/wiki/Q10566946| Template:BLP editintro (Q10566946)]] and [[https://www.wikidata.org/wiki/Q14400704|  Template:Disambig editintro (Q14400704) ]] for more of the potentially affected wikis.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378929900,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4a5risai7mr4y6na4dug,task_description,resolved
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931573 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Support '&editintro=…' etc. on subsequent loads via page tabs%%%
+https://gerrit.wikimedia.org/r/931573",1689089611,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931572 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Support '&editintro=…' etc. on back/forward and VE/NWE switch%%%
+https://gerrit.wikimedia.org/r/931572",1689089607,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931571 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Fix '&editintro=…' not working on Vector with some settings%%%
+https://gerrit.wikimedia.org/r/931571",1687373904,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Thank you @Ryasmeen, I figured out why that was happening. It was only broken when using single edit tab mode, and I didn't think to test that before.
+
+I also fixed the other issue, so after these changes, the message should appear after the editor is opened again as well.",1687256236,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931573 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Support '&editintro=…' etc. on subsequent loads via page tabs%%%
+https://gerrit.wikimedia.org/r/931573",1687256107,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931572 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Support '&editintro=…' etc. on back/forward and VE/NWE switch%%%
+https://gerrit.wikimedia.org/r/931572",1687256105,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931571 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Fix '&editintro=…' not working on Vector with some settings%%%
+https://gerrit.wikimedia.org/r/931571",1687256103,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"It seems the edit intro message is appearing only when you load the page following the link that has the 'editintro' url parameter. But, it's still not showing the edit notice when you click on the 'Edit' button directly on the same page which I think what the new patch was for? 
+
+
+>>! In T56029#8889645, @gerritbot wrote:
+> Change 923769 **merged** by jenkins-bot:
+> %%%[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget.init: Support '&editintro=…' in edit links%%%
+> https://gerrit.wikimedia.org/r/923769
+
+Here is the screen capture of the issue. Also, it seems the URL on the address bar is different from what it shows when you hover over the Edit link:
+{F37101586}
+
+This is different from the special case @matmarex mentioned here:
+
+>>! In T56029#8890073, @matmarex wrote:
+> This should make the edit intros work.
+> 
+> There's one known issue: the edit intro message only appears the first time the editor is opened after loading/refreshing the page. (Afterwards editor initialization is done differently, and adding this feature without messing up the browser back/forward navigation proved difficult.) We should probably file a separate task about this.
+
+",1686587044,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"This should make the edit intros work.
+
+There's one known issue: the edit intro message only appears the first time the editor is opened after loading/refreshing the page. (Afterwards editor initialization is done differently, and adding this feature without messing up the browser back/forward navigation proved difficult.) We should probably file a separate task about this.",1685471894,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 923769 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget.init: Support '&editintro=…' in edit links%%%
+https://gerrit.wikimedia.org/r/923769",1685467180,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 923769 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget.init: Support '&editintro=…' in edit links%%%
+https://gerrit.wikimedia.org/r/923769",1685320256,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"This already almost works. The API used by VE to fetch edit notices supports the 'editintro' parameter. In fact, if you follow this link, you'll see the notice: <https://en.wikipedia.org/w/index.php?title=Jasmin_Fejzić&veaction=edit&editintro=Template:BLP_editintro>. But if you just click ""Edit"" on the same page, you won't. This probably only needs a tiny bit of glue code to parse the parameters from the ""Edit"" link, like we're already parsing them from the URL.",1681952881,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Just to make you know: in ruwiki, we adapted RockMFR's ""magic editintros"" to work with VisualEditor (although the resultant script is rather hackish), see https://ru.wikipedia.org/wiki/MediaWiki:Gadget-blpEditNotice.js.",1533665741,PHID-USER-p6gpvwnc6ske65oxuoof,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Just to make you know: in ruwiki, we adapted RockMFR's ""magic editintros"" to work with VisualEditor (although the resuntant script is rather hackish), see https://ru.wikipedia.org/wiki/MediaWiki:Gadget-blpEditNotice.js.",1533665333,PHID-USER-p6gpvwnc6ske65oxuoof,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 329796 merged by jenkins-bot:
+Add editintro to notices
+
+[[https://gerrit.wikimedia.org/r/329796]]",1483474748,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 329796 had a related patch set uploaded (by Esanders):
+Add editintro to notices
+
+[[https://gerrit.wikimedia.org/r/329796]]
+",1483203828,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,I think it is better than editintro+JS yes.,1434999463,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"One way to fix this, as @Cenarium has observed, would be to fix {T85372} and switch wiki(?s) over to use that instead; is this the best option?",1434985888,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,">>! In T56029#945042, @Cenarium wrote:
+>
+> Adding support in VE for preload / editintro is still worthy on its own, but it looks like this task is a duplicate of T51622.
+
+Now Merging.",1434824530,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,">>! In T56029#1098976, @Cenarium wrote:
+> I've uploaded a patch for this (per-category editnotices) : [[https://gerrit.wikimedia.org/r/#/c/189178/|commit 189178]].
+
+I've updated the patch, it works properly now.",1432586632,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,I've uploaded a patch for this (per-category editnotices) : [[https://gerrit.wikimedia.org/r/#/c/189178/|commit 189178]].,1425821786,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,">>! In T56029#800523, @TheDJ wrote:
+> alternatively, get away from this specific implementation and try to move it into core as ""category based edit notices"" and VE gets the notice for free.
+
+I've created a specific task for per category editnotices, T85372, I had already suggested it for the more general T20596 but this didn't get implemented. 
+FYI, the English Wikipedia isn't the only wiki to use this.
+Adding support in VE for preload / editintro is still worthy on its own, but it looks like this task is a duplicate of T51622.",1419691441,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"alternatively, get away from this specific implementation and try to move it into core as ""category based edit notices"" and VE gets the notice for free.",1417508902,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"To work as desired VE would need to respect the editintro= url parameter. For example
+http://en.wikipedia.org/wiki/Paul_Bahn?veaction=edit&editintro=Template:BLP_editintro
+and use that to fill in the edit notice with Template:BLP_editintro.
+A couple of lines in MediaWiki:Common.js would add the parameters to URL's for all BLPs.",1378970400,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,Link for InputBox https://www.mediawiki.org/wiki/Extension:InputBox,1378969899,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Investigate where we can replace setTimeouts with EventSequencer,"For example, onBeforePaste/onAfterPaste in ve.ce.Surface
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378834020,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wh766os42bllzvmszxya,task_description,open
+VisualEditor: Investigate where we can replace setTimeouts with EventSequencer,"Thanks, looks like I hadn't properly updated my copy of VE to master. :P",1378839634,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-wh766os42bllzvmszxya,task_subcomment,NA
+VisualEditor: Investigate where we can replace setTimeouts with EventSequencer,"(In reply to comment #1)
+> Got a reference doc for EventSequencer?
+
+https://doc.wikimedia.org/VisualEditor/master/#!/api/ve.EventSequencer",1378839518,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wh766os42bllzvmszxya,task_subcomment,NA
+VisualEditor: Investigate where we can replace setTimeouts with EventSequencer,Got a reference doc for EventSequencer?,1378839441,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-wh766os42bllzvmszxya,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"<translate>…</translate> and the related <tvar>…</tvar> are currently un-parsed and shown as plain wikitext in VisualEditor because they're not recognised, per T50891; however, once that is fixed, the blocks won't be editable except as alien nodes (in wikitext), and won't be createable.
+
+Making a proper VisualEditor plugin to translate these in-page as a rich editor shouldn't be particularly hard (he says…).",1378773120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_description,open
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),">>! In T55974#8091892, @Tacsipacsi wrote:
+> I suppose this one, if we can call this a specification at all. I have the feeling that it was simply forgotten that translation syntax needs to be created, not only maintained…
+
+Not forgotten. What has been done so far was a necessary first step and only provides a basic support. The Language team is exploring options how to continue working towards full support. This doesn't mean adding a button or two; we want to take a deeper look to figure out what would actually be a good user experience. ",1658930211,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"I suppose this one, if we can call this a specification at all. I have the feeling that it was simply forgotten that translation syntax needs to be created, not only maintained…",1658336620,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),">>! In T55974#8086214, @Tacsipacsi wrote:
+> No, there’s another “minor” caveat the blog post doesn’t mention: you can’t add new markup. The content can be edited, they can be deleted, even copied and pasted, but if there’s no `<translate>` or `<tvar>` tag on the page you edit, there’s no way to create them.
+
+Thanks for this info. Which task/subtask of this task cluster specifies the work (add new markup) that's still to be done?",1658220589,PHID-USER-lbrksgjks7nerhn7d2xm,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"No, there’s another “minor” caveat the blog post doesn’t mention: you can’t add new markup. The content can be edited, they can be deleted, even copied and pasted, but if there’s no `<translate>` or `<tvar>` tag on the page you edit, there’s no way to create them.",1658180714,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),Is this task resolved by https://diff.wikimedia.org/2022/05/12/mediawiki-1-38-brings-support-for-editing-translatable-pages-with-the-visual-editor/ ?,1658172925,PHID-USER-bz37wupbujiswpiqntmt,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"I added this issue to MediaWiki Stakeholders' Group/TechConf Input:
+
+https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/TechConf_Input#Improved_Translate_-_VisualEditor_integration
+
+Please add your endorsement if you like to make this issue more visible.",1534491626,PHID-USER-yftvcvsb36qrmx4iohsm,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"I added this issue to MediaWiki Stakeholders' Group/TechConf Input:
+
+https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/TechConf_Input#Improved_Translate_-_VisualEditor_integration
+
+Please add your endorsement if you like make this issue more visible.",1534491589,PHID-USER-yftvcvsb36qrmx4iohsm,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"Also, I don't think I could do this in two weeks, which suggests this is too big for GSoC.",1457021325,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),">>! In T55974#2084495, @Micru wrote:
+> I see that the stalled bug has been marked as resolved, Could this task become a GsoC project?
+
+Eventually, yes; however this was missing a few dependencies, T49344 chief amongst them. That work might not be done for another year or more.",1457021192,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),,1555396632,PHID-USER-my5s6nat437le6q5fq7d,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),,1457021044,PHID-USER-my5s6nat437le6q5fq7d,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),">>! In T55974#1042621, @Qgil wrote:
+> If there is no interest / critical mentoring mass to promote this project for GSoC / Outreachy, then maybe the current ""Normal"" priority should be lower?
+
+It's not a matter of priority, see blockers: this is blocked on a stalled bug.",1424596006,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"If there is no interest / critical mentoring mass to promote this project for GSoC / Outreachy, then maybe the current ""Normal"" priority should be lower?",1424130694,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"Wikimedia will [[ https://phabricator.wikimedia.org/T921 | apply to Google Summer of Code and Outreachy ]] on Tuesday, February 17. If you want this task to become a featured project idea, please follow [[ https://phabricator.wikimedia.org/project/view/1042/ | these instructions ]]. ",1423662273,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"Is it true that parsoid has limitations parsing tags other than ""normal parser tags"". If yes what are they & why ? I want to make a plugin for VE to embed translate extension as mentioned above. Cant i include my own grammar for parser to do stuffs way i want.?",1422107606,PHID-USER-cqpeh4jvvexbszsxogrw,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"Pankaj: This bug depends on fixing bug 48891 first (see the ""Depends on"" field). If something is unclear with comment 0, please explain what is unclear and why. Also see [[mw:Annoying little bugs]].",1394440778,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"**pankaj10it45** wrote:
+
+Hello,I want to work on this bug.Can you tell me what exactly it is?
+Thank you.",1394405522,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,,1378691520,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_description,resolved
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,"Change 255931 merged by jenkins-bot:
+Use white-space: pre-wrap instead of using &nbsp; for spaces
+
+[[https://gerrit.wikimedia.org/r/255931]]",1448930482,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_subcomment,NA
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,"Change 255931 had a related patch set uploaded (by Bartosz Dziewoński):
+Use white-space: pre-wrap instead of using &nbsp; for spaces
+
+[[https://gerrit.wikimedia.org/r/255931]]
+",1448813669,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_subcomment,NA
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,"Still valid:
+```
+./src/ce/nodes/ve.ce.TextNode.js:		// Replace spaces with &nbsp; where needed
+```",1426789095,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_subcomment,NA
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,"From an email conversation I had with Aryeh in January 2012:
+
+(Since I'm thinking about canonicalization of whitespace, a tip: set
+white-space: pre-wrap on any contenteditable regions you use, and
+wherever you use them.  This will stop you from needing to use nbsp's
+in ways they were never intended to be used, which causes a variety of
+subtle bugs.  See
+<http://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#canonical-space-sequences>
+for a basic explanation, and click the first ""View Comments"" at
+<http://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#the-inserttext-command>
+for a more detailed explanation of how nbsp substitution works in
+practice.)",1378691662,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_subcomment,NA
+"VisualEditor: Hide ""version false"" in the help menu if it can't be shown","== Steps ==
+1) Go to
+https://www.mediawiki.org/wiki/BUG?veaction=edit&uselang=en
+2) Click on ""BETA""
+
+== Actual result ==
+There is the text ""Version false"" generated by the HTML:
+
+<div>
+ <span class=""ve-init-mw-ViewPageTarget-version-label"">Version</span> 
+ <a class=""ve-init-mw-ViewPageTarget-version-link""
+    target=""_blank""
+    href=""false"">false</a> 
+ <span class=""ve-init-mw-ViewPageTarget-version-date""></span>
+</div>
+
+== Expected result ==
+There should be some version number instead of the ""false"" text
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378656660,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-7wslc7ru3hkj3phtleql,task_description,resolved
+"VisualEditor: Hide ""version false"" in the help menu if it can't be shown","Yes, this was exposed as part of bug 53050, but due to bug 53972 in how code is currently deployed to the WMF cluster, we can't actually make this available outside of Beta Labs (boo). Consequently this was fixed in gerrit 84334 two weeks ago before it hit ""real"" production wikis (non-MW.org).",1380740276,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7wslc7ru3hkj3phtleql,task_subcomment,NA
+"VisualEditor: Hide ""version false"" in the help menu if it can't be shown","I don't see false anymore, but currently there is no element whose class contains ""ve-init-mw-ViewPageTarget-version"" either. Was this removed on purpose?",1380708958,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-7wslc7ru3hkj3phtleql,task_subcomment,NA
+"VisualEditor: Hide ""version false"" in the help menu if it can't be shown","I dont see 'false' on mw or en.wp.  I see 'beta'.
+
+Is the originally reported problem fixed, or masked somehow.
+
+I notice that version says '0.1.0', which is not useful as there have been many deploys of the code.  beta's should have build numbers or build dates for each release.
+
+https://www.mediawiki.org/wiki/Special:Version
+
+e.g. ULS is 'Version 2013-06-17'",1380678404,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-7wslc7ru3hkj3phtleql,task_subcomment,NA
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,"Article tabs are wrong when page is protected via cascading from another page.
+
+To reproduce: visit https://pl.wikipedia.org/wiki/Wikipedia:Strona_główna?uselang=en and behold the ""Edit source"" link, even if you're anonymus.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=11700",1378575540,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_description,resolved
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,"Change 128965 merged by jenkins-bot:
+Check cascade protection and show notice if relevant
+
+https://gerrit.wikimedia.org/r/128965",1398277452,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_subcomment,NA
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,"Change 128965 had a related patch set uploaded by Alex Monk:
+Check cascade protection and show notice if relevant
+
+https://gerrit.wikimedia.org/r/128965",1398192310,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_subcomment,NA
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,"Did something change here? MW shows an edit tab on these pages. If you turn on VE then it changes that ""Edit"" to ""Edit source"" and adds a new ""Edit"", which is what I would expect it to do.
+
+What probably should be done is showing the cascade notice on VE though.",1397779435,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_subcomment,NA
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,*** Bug 58452 has been marked as a duplicate of this bug. ***,1386959355,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_subcomment,NA
+provisioning browsertests role fails,"I added role ""browsertests"", but every time I run `vagrant provision` it fails. It seems to be trying to install an ""ffi"" (foreign function interface) module.
+
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Using rake (10.1.0)
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Using builder (3.2.2)
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): 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)
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice):
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice):         /usr/bin/ruby1.9.1 extconf.rb
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice):
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Gem files will remain installed in /home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.0 for inspection.
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Results logged to /home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.0/ext/ffi_c/gem_make.out
+
+gem_make.out has only:
+   /usr/bin/ruby1.9.1 extconf.rb
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69874",1378503240,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-da2sdjr5nuneldb7hbcy,task_description,resolved
+provisioning browsertests role fails,Forgot to tag the commit in https://gerrit.wikimedia.org/r/#/c/158564/ but the patch should have fixed this and other bugs related to botched ffi compilation. A good handful of the most problematic gems are now installed from packages.,1410462222,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"After profiling the `bundle install` process, I'm seeing around 128M as the peark memory usage. That seems like a reasonable amount of free memory to expect on the VM considering some of the other memory intensive processes that need to run (xvfb/firefox in browser testing, for example, uses around 192M).",1408742280,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,The ruby-ffi package is for Ruby 1.9. Perhaps we should try switching back to a shared directory for bundler gems. That would at least mitigate the failures by only performing ffi compilation (and other native gem compilation) once.,1408736249,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,Can we do `apt-get install ruby-ffi` instead of compiling ffi with bunder?,1408727122,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Is this still an active problem? The browsertests role has been removed, but there are now several extension specific roles which install gems via bundler to provide testing support.",1408494405,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"I managed to get tests running after increasing memory size to 1024. Is it possible to increase memory size just when gems are installing, and then decrease it back to 512?",1380204683,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Found it. Mediawiki-Vagrant[1] says to edit Vagrantfile-extra.rb. Now VM memory size is 1024.
+
+$ vagrant halt
+edit Vagrantfile-extra.rb
+$ vagrant up
+$ VBoxManage showvminfo ...
+...
+Memory size: 1024MB
+...
+
+1: https://www.mediawiki.org/wiki/Mediawiki-Vagrant",1380202260,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"I have tried this.
+
+#1 $ vagrant halt
+
+#2 changed
+
+vb.customize ['modifyvm', :id, '--memory', '768']
+
+in Vagrantfile to
+
+vb.customize ['modifyvm', :id, '--memory', '1024']
+
+#3 $ vagrant up
+   $ vagrant provision
+
+but both ""VBoxManage showvminfo"" and ""Oracle VM VirtualBox Manager"" still say ""Memory size: 768MB"".",1380201351,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Created attachment 13384
+VBoxManage showvminfo
+
+**Attached**: {F11493}",1380201068,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Created attachment 13383
+vagrant provision
+
+**Attached**: {F11492}",1380201049,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"I have the same problem. I will attach output of ""vagrant enable-role browsertests"" and ""VBoxManage showvminfo"".
+
+How do I increase VM memory size? (Looks like it is 768MB now.)
+
+In Vagrantfile[1] or ""Oracle VM VirtualBox Manager > VM > right click > Settings > System > Base Memory""?
+
+1: https://github.com/wikimedia/mediawiki-vagrant/blob/master/Vagrantfile#L65",1380201013,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"(In reply to comment #5)
+> I increased the VM to 1024, `vagrant halt` `vagrant up`!
+... that should have continued ""and the vagrant provision complete successfully, and I can run tests!""  Yay, thanks for the memory suggestion.
+
+(In reply to comment #6)
+> the way to resolve this is to document...
+I added something, https://www.mediawiki.org/w/index.php?title=MediaWiki-Vagrant&diff=783886&oldid=781408
+
+> ... one should try freeing some memory in the VM
+You mean by temporarily disabling other roles until vagrant provisions browsertests successfully?  I didn't try stopping apache/mysql/parsoid/redis in the vagrant VM, because I assumed `vagrant provision` would have restarted them before running the ruby gem bundler.
+
+I guess the opaque exception reporting is an upstream issue.",1379308175,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"(In reply to comment #5)
+> I increased the VM to 1024, `vagrant halt` `vagrant up`!
+
+And -- did it work? I guess it did, because you later speak of ""successful and unsuccessful runs"".
+
+I don't think it's viable to keep increasing the default RAM allocation just so that this one Gem can compile, so the way to resolve this is to document the fact that compiling the ffi Gem is a memory-hungry task and that if it fails one should try freeing some memory in the VM or increasing the RAM allocation.",1379306284,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Created attachment 13289
+output of `vboxmanage showvminfo ...` before I increased VM memory
+
+**Attached**: {F11491}",1379305914,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Thanks for the updates. I did not modify the VM's memory size.
+Maybe the difference between me and Chris is my roles include eventlogging, gettingstarted (which loads redis) and visualeditor+parsoid.
+
+I increased the VM to 1024, `vagrant halt` `vagrant up`!
+
+In the vagrant VM, on both successful and unsuccessful runs, puppet spends many minutes running
+/usr/bin/ruby /usr/bin/bundle install --path /home/vagrant/.gem
+with no output.
+
+/home/vagrant/.gem/ruby/1.9.1/gems contains a bunch of old gems from May14, and the new revisions of gems from this run.
+
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:28 builder-3.2.0
+drwxr-xr-x  6 vagrant vagrant 4096 Sep  6 22:14 builder-3.2.2
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:35 childprocess-0.3.9
+drwxr-xr-x  6 vagrant vagrant 4096 May 14 04:35 chunky_png-1.2.8
+drwxr-xr-x 10 vagrant vagrant 4096 May 14 04:44 cucumber-1.3.1
+drwxr-xr-x  6 vagrant vagrant 4096 May 14 04:45 data_magic-0.14
+drwxr-xr-x  7 vagrant vagrant 4096 May 14 04:35 diff-lcs-1.2.4
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:44 faker-1.1.2
+drwxr-xr-x  7 vagrant vagrant 4096 May 14 04:29 ffi-1.8.1
+drwxr-xr-x  7 vagrant vagrant 4096 Sep 16 03:50 ffi-1.9.0    <--- the problem
+drwxr-xr-x 10 vagrant vagrant 4096 May 14 04:35 gherkin-2.12.0
+drwxr-xr-x  5 vagrant vagrant 4096 May 14 04:44 i18n-0.6.4
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:35 multi_json-1.7.3
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:45 net-http-persistent-2.8
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:45 page_navigation-0.9
+drwxr-xr-x  5 vagrant vagrant 4096 May 14 04:45 page-object-0.8.10
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:45 parallel-0.6.4
+drwxr-xr-x  5 vagrant vagrant 4096 May 14 04:45 parallel_tests-0.12.3
+drwxr-xr-x  6 vagrant vagrant 4096 May 14 04:28 rake-10.0.4
+drwxr-xr-x  6 vagrant vagrant 4096 Sep  6 22:14 rake-10.1.0",1379305740,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,Apparently having two different people attempt to verify your report is not quite enough to warrant a follow-up. Closing as invalid.,1379144075,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.],1378939542,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"I ran into this problem before. If I recall correctly, it's an out-of-memory error that bundler is unhelpfully catching and re-throwing as an uninformative generic exception. The memory requirements of building the ffi gem were the original impetus for bumping the VM's memory allocation to 768 Mb, but since we've done that I have not run into this problem. Have you modified the VM's memory allocation setting at all?
+
+If you have not modified the VM, can you reproduce the output of ""vboxmanage showvminfo""? It should be invoked with the machine's UUID as the final command-line argument. The UUID can be found in .vagrant/machines/default/virtualbox/id, which should exist under your Vagrant repo root.",1378632611,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,I was not able to reproduce this in a fresh VM,1378503546,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+VisualEditor: Pasting text into VE from external text processor removes newlines,"System environment:
+Win7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a page
+Edit it in VE
+Copy-paste the following text:
+a
+b
+c
+d
+e
+
+Expected output:
+a
+b
+c
+d
+e
+
+Actual output:
+abcde
+
+The problem has been tested with notepad++ as the external editor, with line endings in windows format (CRLF), UNIX format (LF) and MAC format (CR). Newline is not copied in any of the cases.
+
+The problem has also been tested by trying to copy-paste html text from chrome itself. Newline is not copied.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52096",1378418160,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-3yhieue5lg5ipuzhildn,task_description,resolved
+VisualEditor: Pasting text into VE from external text processor removes newlines,"Change 86664 merged by jenkins-bot:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1385500082,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3yhieue5lg5ipuzhildn,task_subcomment,NA
+VisualEditor: Pasting text into VE from external text processor removes newlines,Works with gedit & chrome with the rich paste patch.,1381157678,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3yhieue5lg5ipuzhildn,task_subcomment,NA
+VisualEditor: Pasting text into VE from external text processor removes newlines,"Change 86664 had a related patch set uploaded by Esanders:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1381157509,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3yhieue5lg5ipuzhildn,task_subcomment,NA
+VisualEditor: Pasting text into VE from external text processor removes newlines,"Confirmed in Firefox 23 / Xubuntu Linux / Monobook
+
+Using kwrite:
+Tested with \n  \r and \r\n end of lines and it makes no difference.
+Tested also using UTF-8, UTF-16, ISO-8859-1, ISO-8859-2 and Windows-1258 encodings.
+
+Also tested copying from this page viewed in Firefox, Konqueror and Linuks, from a PDF, a text file in a terminal, and again from kwrite using the following:
+
+a
+
+b
+
+c
+
+d
+
+e
+
+None of it makes the slightest bit of difference.
+
+https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox3&diff=571705481&oldid=571089410 is the copy from comment 0",1378420228,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3yhieue5lg5ipuzhildn,task_subcomment,NA
+"Lazy load extensions' large resources in VisualEditor, rather than blocking load","Extensions such as Math or SyntaxHighlight may require the inclusion of large(ish) JS libraries. It would be good if we didn't load these on every VE page load, but rather when these elements are present, or become present (e.g. I add a formula to a new document)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378414320,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nydh4gpoq4wxodchwgi3,task_description,open
+mw.config doesn't expose page existence information about the target of a special page,"For special pages, no information about page existence is exposed to mw.config, which means that VisualEditor is forced to assume it exists regardless.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66885",1378324980,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rzsc7tmlupqbuaedolkl,task_description,resolved
+mw.config doesn't expose page existence information about the target of a special page,"Change 169639 merged by jenkins-bot:
+Expose ID of relevant page in JS variables
+
+https://gerrit.wikimedia.org/r/169639",1416369714,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"Change 169639 had a related patch set uploaded by Alex Monk:
+Expose ID of relevant page in JS variables
+
+https://gerrit.wikimedia.org/r/169639",1414545533,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"'wgRelevantArticleId' => WikiPage::factory( $relevantTitle )->getId() perhaps?
+
+I'm not sure we want to introduce new variables here though...",1413833849,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,Sounds like you need the js variable 'wgIsProbablyEditable' or 'wgIsArticle' according to page under 'wgRelevantPageName' or a new variable 'wgRelevantIsProbablyEditable'/'wgRelevantIsArticle' to cover this.,1404280264,PHID-USER-qaoxfiqu6bxhd5ehlwhc,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,This bug is about giving existence information for the relevant article (i.e. the article that the special page is working on). See bug 66885,1403552699,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"(In reply to comment #3)
+> There is wgCanonicalSpecialPageName set, when you are on a special page.
+
+-> WORKSFORME",1384032206,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"There is wgCanonicalSpecialPageName set, when you are on a special page.",1378631680,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"Change 82744 merged by jenkins-bot:
+Reference core bug 53774 in bug 49000 comment
+
+https://gerrit.wikimedia.org/r/82744",1378356954,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"Change 82744 had a related patch set uploaded by Jforrester:
+Reference core bug 53774 in bug 49000 comment
+
+https://gerrit.wikimedia.org/r/82744",1378325283,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**Author:** `kwwilliams`
+
+**Description:**
+When articles contain items that lead VE to corrupt the article, we've been protecting them by wrapping the article with <div class=""ve-ce-protectedNode""> and </div>. This used to keep VE from being able to select any material within the article, which allowed us to keep the article from being corrupted.
+
+VE is now allowing edits to templates inside the article (see https://en.wikipedia.org/w/index.php?title=Teenage_Dream_%28Katy_Perry_album%29&veaction=edit for an example), so we now have no way to protect articles that we know VE cannot handle.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52141",1378317960,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s47345xgplfmgixnp726,task_description,declined
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","(In reply to This, that and the other from comment #13)
+> As it stands, this is a dupe of bug 52141. I've put back the original bug
+> summary; it seems to me that WONTFIX is the appropriate resolution for this
+> bug.
+
+Agreed.",1403741232,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","As it stands, this is a dupe of bug 52141. I've put back the original bug summary; it seems to me that WONTFIX is the appropriate resolution for this bug.",1403416223,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","James, that is bug 52141.  This bug was about a specific problem with the existing code.",1383886236,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","Changing this to ""Provide a way to block VisualEditor from being active on a page""; I worry that this will lead to yet another magic word, but oh well.",1381342100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","I was very easily able to reproduce this problem; I dont have exact steps to reproduce, but with a few clicks and keypresses in the content area, all content was removed and the text I typed appeared in the body of the article.  Undo appeared to work as expected, however 'Review your changes' did not return any results - it hung, but didnt lock up the browser.  The toolbar is another way to override the protectedNode.
+
+This template is also being used to create a 'pre' text area on
+https://en.wikipedia.org/w/index.php?title=Morse_code&veaction=edit",1380637712,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+Note https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=572094345&oldid=572076135 , where another 26,000 articles that VE mutilates have been identified.
+
+We really need to have a method to shield articles from VE. It's critical to do, and beyond reason to expect that we will always modify articles to conform to VE's expectations.",1378671601,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","I tried again on my test page on a different computer running Firefox 17.0.2 (ESR) under XP.
+
+At first, it seemed that the protected node was working, but at some point (after clicking, double-clicking, typing, ...) I managed to write in the protected node: the result was an even greater mess than before: still the duplication, quotes added all over the place (they seem correct but unnecessary), pipes removed, space added, ...
+
+https://en.wikipedia.org/w/index.php?title=User%3ANicoV%2FTest&diff=571628361&oldid=571542702",1378379690,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+(In reply to comment #6)
+> On the wider point, it's not clear if there's an actual long-term need for a
+> proper VE-prevention system (or if it's all solvable with a few quick fixes
+> of
+> bad wikitext), but if there is, we should build a proper one, not rely on a
+> hack that might break.
+
+What's unclear about that?
+
+I agree that it would be better to do this with a category, but the need for VE to recognise some flag that tells it not to edit a given article seems fairly obvious. As long as VE mutilates pages in response to inputs that behaved reasonably with the working software, we will require a mechanism to tell VE not to edit certain pages.",1378324543,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","(In reply to comment #5)
+> The div has been removed, so people need to look at
+> https://en.wikipedia.org/w/index.
+> php?title=Teenage_Dream_%28Katy_Perry_album%29&oldid=571540632
+
+In this particular case, note that the reason everything was broken in editing this page was because the <ref> was defined outside of the table cell, in a the non-space between the end of the cell and the start of the row, and only happened to ""work"" in WT mode because of HTML Tidy moving it to somewhere sane - Ed's edit to the page fixed the duplication so the desired protection is no longer needed: https://en.wikipedia.org/w/index.php?title=Teenage_Dream_(Katy_Perry_album)&diff=571550633&oldid=571540632
+
+On the wider point, it's not clear if there's an actual long-term need for a proper VE-prevention system (or if it's all solvable with a few quick fixes of bad wikitext), but if there is, we should build a proper one, not rely on a hack that might break.",1378323301,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+The div has been removed, so people need to look at https://en.wikipedia.org/w/index.php?title=Teenage_Dream_%28Katy_Perry_album%29&oldid=571540632",1378322920,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+(In reply to comment #3)
+> According to the documentation, the div is only meant to block editing to a
+> section of a page (although that section can be the whole text), so adding
+> text
+> before is correct, likewise you should be able to add text after the /div.
+It's a change from the original behaviour. I agree that it's not technically wrong.",1378321376,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","According to the documentation, the div is only meant to block editing to a section of a page (although that section can be the whole text), so adding text before is correct, likewise you should be able to add text after the /div.
+
+The editing templates within the div does sound like a bug though.
+
+If VE (or Parsoid possibly) is not treating the div as invariant then the div definitely isn't doing what it was intended to do.",1378320819,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+Firefox 23.0.1 on Windows 7.
+
+To be clear, we are still prevented from editing the text. We are not prevented from editing templates, and we can insert text before div.",1378319066,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","The original person to report this noted that they were using Chrome 29 on Windows 7.
+
+I have been unable to reproduce this in Firefox 23 on Linux.
+
+Neither kww or the ip who can reproduce this have noted their system.",1378318792,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+VisualEditor: Range around an annotated alien calculated incorrectly,"1. Create '<p>Foo<cite>Bar</cite>Baz</p>'
+2. Select Bar
+3. Range is now [4,6] (correct as <cite/> becomes [<alien>,</alien>])
+4. Bold the selection
+5. Range is now [6,6] :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378317600,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ejnmmkuva4ygwqwckki3,task_description,resolved
+VisualEditor: Range around an annotated alien calculated incorrectly,"Change 82771 merged by jenkins-bot:
+Fix getOffsetFrom(Element|Text)Node for annotated aliens
+
+https://gerrit.wikimedia.org/r/82771",1378367478,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ejnmmkuva4ygwqwckki3,task_subcomment,NA
+VisualEditor: Range around an annotated alien calculated incorrectly,"Change 82771 had a related patch set uploaded by Esanders:
+Fix getOffsetFrom(Element|Text)Node for annotated aliens
+
+https://gerrit.wikimedia.org/r/82771",1378339784,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ejnmmkuva4ygwqwckki3,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","[Please move this to a different component if applicable, I'm not sure where the editor comes from.]
+
+It is impossible to insert the ""ę"" or ""Ę"" characters (latin letter ""e""/""E"" with ogonek) from keyboard when editing in Module: namespace with the code editor on the Polish Wikipedia.
+
+""ę"" is inserted on the Polish keyboard using AltGr+e (aka Ctrl+Alt+e). If the editor uses this as a hotkey, it shouldn't (nor should it use any other Ctrl+Alt combinations).
+
+(Reported at https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#VisualEditor_a_polskie_diakrytyki)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378316100,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-psky7k3cs2jglhz37xhh,task_description,resolved
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","This works correctly these days.
+
+It was apparently fixed by https://github.com/ajaxorg/ace/pull/1463 ([[https://github.com/ajaxorg/ace/pull/1463/commits/d4bdfe33001b4c13134515b0fa53b6b64d8b3ee1|d4bdfe33001b4c13134515b0fa53b6b64d8b3ee1]]) – which was already merged when I was filing this bug :) – and we upgraded to that version in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CodeEditor/+/104510 (early 2014).",1702336260,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","This works correctly these days.
+
+It was apparently fixed by https://github.com/ajaxorg/ace/pull/1463 – which was already merged when I was filing this bug :) – and we upgraded to that version in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CodeEditor/+/104510 (early 2014).",1702336181,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","These are all the default defined key combinations:
+https://github.com/ajaxorg/ace/blob/40ea516801332fb8e96f8ba2e5046eece2fd95d3/lib/ace/commands/default_commands.js",1388500776,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","In that case, it looks like you could follow the example in modules/jquery.codeEditor.js near line 151 to disable this command too.",1378324088,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","@Brad, depending on how exactly you remapped it, the Ctrl+Alt+E might be mapped to ""ę"" in some lower-level layer, not letting the browser even see it. (I used this a few times to wrestle with some stupid applications which take Ctrl+Alt shortcuts for themselves to take it away from them.)
+
+Some grepping shows ACE Editor uses ""Ctrl-Alt-E"" / ""Command-Option-E"" for the ""togglerecording"" command. This is most likely the culprit.
+
+This seems to be the only Ctrl-Alt shortcut involving regular letters (there are also a few with arrow keys and backspace).",1378320708,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","You want CodeEditor.
+
+I note that I can type ę and Ę fine in CodeEditor from here, where the key combinations are ""<Compose> ; e"" and ""<Compose> ; E"".
+
+I also remapped Ctrl+Alt+E to ""ę"" temporarily, and I was able to enter that character using that key combination in CodeEditor on a module page on plwiki with no issues (using Firefox 24 on Linux).",1378319184,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,"* This is language/script specific diacritic specific bug split from {T53472}
+
+* For language Marathi Script Devanagari anuswara diacritic is  ं 
+* If one types the anuswara diacritic  ं  after any devanagari script alphabet it is usually place above the concerned alphabet. For example  क is a Marathi/Devanagari alphabet if I type क+ ं I get  कं  
+* If I place cursor before the cluster कं and press delete then whole cluster gets deleted and that is right way to happen, and this behaviour needs to be retained (since if basic alphabet is not there then no need of anuswara diacritic  ं) .
+* Problem: In Visual Editor if I place cursor after the cluster e.g. after कं and press backspace current behaviour is the whole cluster gets deleted. Example कं + Backspace key = results in whole cluster getting deleted.
+* Expected behaviour is: Cluster with anuswara diacritic (कं) + Backspace key = retain rest of cluster(retain क ) and only anuswara diacritic  ं should get deleted.
+* Reason: During spell correction many times we need to retain rest of the cluster and only change the diacritics. For anuswara   ं diacritic spell change is required frequently for various reasons like change in singular-plural tense. Every time retyping the whole cluster is cumbersome. Traditional Source editing behaviour is proper and expected and problem is coming only with VisualEditor behaviour.
+* For example please see this https://mr.wikipedia.org/w/index.php?title=कृष्ण_श्रीनिवास_अर्जुनवाडकर&diff=1198833&oldid=1198826 edit difference a user had to change this diacritic at several places.
+
+Since users would be reluctant to use VE without correct behaviour, I would prefer this being treated as a bug not just enhancement and to have  fair importance level.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378306620,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-6g646hsi3p3j73jyxxaz,task_description,resolved
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,I'm provisionally deeming this fixed. We changed this behaviour significantly since this was filed. Please re-open if you find issues.,1449602907,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6g646hsi3p3j73jyxxaz,task_subcomment,NA
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,">>! In T55754#549797 in October 2013, @Jdforrester-WMF wrote:
+> we're switching back to native cursoring and backspacing, which hopefully will fix this
+
+@Mahitgar: Do you know if this is still a problem in Devanagari? (I'm afraid I'm missing input method skills to test this myself.)",1425552598,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6g646hsi3p3j73jyxxaz,task_subcomment,NA
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,"Retitled for clarity; we're switching back to native cursoring and backspacing, which hopefully will fix this, but keeping this open and distinct in case not.",1381274519,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6g646hsi3p3j73jyxxaz,task_subcomment,NA
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,"Per Bug 51472#c4 , the grapheme cluster handling for backspace is to be on a per script basis. So, this should be treated as the bug for specifically devanagari.
+
+Also note that I am confirming the bug for hindi.
+
+To further clarify the original report, devanagari has various diacritics which can be applied to base unicode characters. It also has a combining character halant (viram) ् (U+094D).
+
+Currently, pressing backspace after a grapheme cluster containing one or more base characters with one or more diacritics and/or combining character deletes the entire grapheme cluster. This is not desired behaviour. Pressing delete before a cluster deletes the entire cluster. This is desired behaviour.
+
+Examples of diacritics: ँ (Chandrabindu) U+0901 ं (Bindu) U+0902 etc.
+
+Examples of grapheme clusters:
+
+One base character with one diacritic: कं ( क + ं ), कँ ( क + ँ ), कः ( क + ः )
+
+One base character with multiple diacritics: किं ( क + ि + ं )
+
+Multiple base characters with halant: श्र ( श + ् + र ), क्ष ( क + ् + ष ), प्र ( प + ् + र )
+
+Multiple base characters with halant followed by diacritics: श्रिं (श + ् + र + ि + ं), क्षि ( क + ् + ष + ि ), प्रे ( प + ् + र + े )
+
+System environment:
+Win7 X64
+Google Chrome 29.0.1547.62 m
+Page used for testing: [[:w:hi:User:Siddhartha Ghai/sandbox]]
+
+Expected behaviour:
+Only one diacritic (the last one in the grapheme), ie one unicode character, is to be deleted. The rest of the grapheme cluster is to stay intact.
+
+Examples used (not exhaustive):
+Grapheme -> Grapheme after pressing backspace
+कं -> क
+कँ -> क
+कः -> क
+क् -> क
+किं -> कि
+श्र -> श्
+क्ष -> क्
+प्र -> प्
+श्रिं -> श्रि
+क्षि -> क्ष
+प्रे -> प्र
+
+Current behaviour (blank indicates entire grapheme cluster was removed) (these results should be verified on other browser/OS combinations):
+कं -> 
+कँ -> 
+कः -> 
+क् -> 
+किं ->
+श्र -> श्  (Working correctly)
+क्ष -> क् (Working correctly)
+प्र -> प् (Working correctly)
+श्रिं -> श् (Deletes र + ि + ं , ie three unicode characters instead of one)
+क्षि -> क् (Deletes ष + ि , ie two unicode characters instead of one)
+प्रे -> प् (Deletes र + े , ie two unicode characters instead of one)
+
+Points to note:
+Some IMEs may provide non-normalized input for characters such as फ़ (U+095E) in place of फ (U+092B) + ़ (U+093C), ढ़ (U+095D) in place of ढ (U+0922) + ़ (U+093C) etc. In such cases, the user may expect that pressing a backspace will only eliminate the diacritic, not the entire grapheme. So, VE may have to handle normalization in such cases.
+
+Results seem to indicate that halant is partially correctly handled. letter + halant + letter + backspace gives letter + halant correctly. But
+letter + halant + backspace, instead of giving the letter, deletes the entire grapheme.
+
+The remaining diacritics as of unicode 3.0 come under Nonspacing mark (Mn) and Spacing combining mark (Mc) (Note: This does not include devanagari extended added in unicode 6.0 and vedic extensions added in unicode 6.1)",1378411609,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-6g646hsi3p3j73jyxxaz,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"en.wp user Professor Hog reports:
+""If you try and use beta to edit a page, but you've forgotten to log in, so you log in directly off the beta page, once you have successfully logged in it takes you back to the edit source page instead of the beta page. Minor, but thought you may want to correct it? ""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52281",1378296540,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_description,resolved
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,I think that needs to wait until enwiki has SET.,1455934739,PHID-USER-mvx4x7ywk2flsaku2dbk,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"@Jdforrester-WMF It looks like the [workaround](https://en.wikipedia.org/wiki/MediaWiki:Anoneditwarning) at enwiki (and maybe others, though not that I know of) needs to be removed/altered.
+
+See my previous comment.",1455912954,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,This now works.,1455641681,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"Note, Steven added a [custom workaround](https://en.wikipedia.org/w/index.php?title=MediaWiki:Anoneditwarning&diff=572253350&oldid=572253272) at English Wikipedia (shortly after this was filed).  It removes the action=edit, so you don't go to //any// editor on return (otherwise, it can to the wrong one like this bug says).
+
+That was never the desired behavior, though.  The desired behavior is that it knows which editor you're using anonymously, and keeps you on the right editor when you return logged in.  Both VE and wikitext have suitable URL parameters; the issue is knowing which to use.",1416894768,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"Changing the depends on to bug 52471 (sorry, I typoed in comment 3)",1378315266,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"(In reply to comment #3)
+> To clarify the sequence I used to reproduce this was:
+> 1. log out
+> 2. load a page in VE. I tested with [[Symphony No. 8 (Mahler)]] and
+> [[user:Thryduulf/sandbox]]
+> 3. click to edit the page in VE
+> 4. Click the ""log in"" link in the notice that pops up. 
+> This loads
+> https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=User:
+> Thryduulf/sandbox&returntoquery=action%3Dedit
+> in a new tab.
+> 5. In that new tab, log in as normal
+> Get returned to the source editor.
+> 
+> The edit notice shown is that in [[MediaWiki:Anoneditwarning]] where the link
+> is hardcoded to the source editor (pre VE this would never have been an
+> issue).
+> 
+> To me this suggests that either editor-relative urls are needed or we need
+> different edit notices for the classic editor and VE (see bug 52741 for the
+> latter)
+
+Oh, I see, I was clicking on ""login"" in the personal links bar - sorry. Re-titling so I don't get confused again. :-)",1378314148,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"To clarify the sequence I used to reproduce this was:
+1. log out
+2. load a page in VE. I tested with [[Symphony No. 8 (Mahler)]] and [[user:Thryduulf/sandbox]]
+3. click to edit the page in VE
+4. Click the ""log in"" link in the notice that pops up. 
+This loads https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=User:Thryduulf/sandbox&returntoquery=action%3Dedit in a new tab.
+5. In that new tab, log in as normal
+Get returned to the source editor.
+
+The edit notice shown is that in [[MediaWiki:Anoneditwarning]] where the link is hardcoded to the source editor (pre VE this would never have been an issue).
+
+To me this suggests that either editor-relative urls are needed or we need different edit notices for the classic editor and VE (see bug 52741 for the latter)",1378313436,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"I'll ask for further clarification, but I've tested this in Firefox 23 on linux.
+
+Clicking the link in the VE popup that notes you're not logged in reproduces this bug. (Note that this loads the login window in a new tab, I logged in there and was returned to the source editor in that window).
+
+Dismissing that popup and then using the log in link at the top right of the page returned me to viewing the page not editing it in either editor.
+
+The results are the same using my Thryduulf account which has a couple of gadgets, and my Awkward42 account which has none.",1378312694,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"I can't reproduce this - I get back to VisualEditor (as expected) - the login link is something like https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=Foobar&returntoquery=veaction%3Dedit
+
+Can ""Professor Hog"" give any further details? What browser were they using? Can they reproduce? What about after a hard-refresh? Do they have any odd gadgets on the account into which they were logging-in?",1378310407,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**Author:** `rachelqa99`
+
+**Description:**
+shows error message
+
+I got this message when running a test automation script, that puts in a line of code and tries to save it. It doesn't recognize the new line of code I put in, so it gives this error message upon save. Not sure if you are aware of this particular scenario, which is why I am submitting it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11191}",1378241340,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y44xrgvhzk7uy25krg2j,task_description,resolved
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,I'm going to provisionally mark this as fixed as it appears to now work.,1449024014,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"Is this still a problem, or can the task be resolved?",1446479363,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"A clarification about each case we tried in the automated test: 
+
+* type a string and the string is shown correctly in CE and DM
+* type a string and :return and both the string and the empty line are shown correctly in CE and DM
+
+* but type a string and :enter and CE correctly shows *both* the string *and* the empty line but DM shows *neither* the string nor the empty line.  That is, the :enter command is recognized in CE but seems to have the effect of making all the changes in CE invisible to DM.",1378312673,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"
+I think this might be a real bug, but I think it might take some particular piece of hardware to trigger it. 
+
+WebDriver/Selenium has two ways of sending a newline to the browser
+
+:enter
+:return
+
+"":return"" is intended to emulate the ""Return"" key on a normal keyboard; "":enter"" is intended to emulate the ""Enter"" key on a numeric keypad.
+
+In this test, when we type a string plus :return in VE, the diff view is correct, and the test would pass.  But when the test sends a string plus :enter in VE, VE does not recognize that the contents of the edit page has changed. 
+
+I tried to reproduce this issue manually using a Macintosh USB keyboard on a Macbook Pro laptop but both the Return key and Enter key on that particular piece of hardware worked correctly with VE. 
+
+I suggest trying out Return (on the keyboard) and Enter (on the numeric keypad) on a few keyboards to make sure we don't see this in the wild.",1378309500,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**rachelqa99** wrote:
+
+I am adding the line of text  This is a test  at the beginning of the page into the Selenium user's homepage on test2.  There is a bunch of already existing text below it, I am just trying to add a new line at the begining of the page, ""This is a test"" and hit Return key for a new line.  I can't seem to reproduce it manually.",1378302946,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"(In reply to comment #0)
+> Created attachment 13227 [details]
+> shows error message
+> 
+> I got this message when running a test automation script,
+
+Yes, this is the normal (you tried to get the diff but as far as we're concerned, no changes were made to the page).
+
+> that puts in a line of code and tries to save it. It doesn't recognize the new
+> line of code I put in, so it gives this error message upon save.
+
+What ""line of code"" does it insert? Where does it insert it? On what page? On what wiki? Can you reproduce manually or does this only happen with the script?
+
+(In reply to comment #3)
+> Possibly a situation caused by bug 53360 which is marked as resolved.
+
+The fix for bug 53360 is running on test2 right now, so almost certainly not related to that bug.
+
+**Attached**: {F11191}",1378246805,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**rachelqa99** wrote:
+
+Possibly a situation caused by bug 53360 which is marked as resolved.",1378242207,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**rachelqa99** wrote:
+
+this is running off of test2",1378241594,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**rachelqa99** wrote:
+
+feature script
+
+**Attached**: {F11192}",1378241543,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+"VisualEditor: jquery.IME doesn't work in VisualEditor's iframes (template, reference, reference list, media, and page settings dialogs, and language, maths, code and link inspectors)","The ULS input methods (jquery.ime) currently do not work with the popup windows of VE. These include the template, reference, reflist, image, link and page settings popups.
+
+The problem has been tested by me on Win7 X64 with Google Chrome 29.0.1547.62 m and possibly by others on other browsers. The problem was originally reported on [1] by mr-wp users.
+
+[1]: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE_.2B_ULS_unicode_Devnagari_Script_input_issues
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378231800,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-nj4fiiksolcbit4ngngp,task_description,declined
+"VisualEditor: jquery.IME doesn't work in VisualEditor's iframes (template, reference, reference list, media, and page settings dialogs, and language, maths, code and link inspectors)",Don't need to make this work as we don't use `iframe`s any more.,1427915125,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nj4fiiksolcbit4ngngp,task_subcomment,NA
+"VisualEditor: jquery.IME doesn't work in VisualEditor's iframes (template, reference, reference list, media, and page settings dialogs, and language, maths, code and link inspectors)",*** Bug 55969 has been marked as a duplicate of this bug. ***,1382983618,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-nj4fiiksolcbit4ngngp,task_subcomment,NA
+VisualEditor: Cursor cannot move through text created with jquery.IME when editing bulleted text,"System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Either use google input tools for hindi or enable ULS hindi transliteration
+
+Input:
+Select bullet formatting from the VE toolbar
+agar[SPACE]main[SPACE]
+
+Expected output:
+with ULS: अगर[SPACE]मैन[SPACE]
+with Google input tools (depends on translation history, macros etc and may differ user-to-user): अगर[SPACE]मैं[SPACE]
+
+Actual output:
+Text output is same as expected. However, the text is partially non-navigable, ie pressing the left arrow key from the end of the text takes the caret to the beginning, and then left/right arrow key presses have no effect on the caret. Simultaneously, if the text is navigated by specifically placing the caret at a particular point using the mouse, the value shown for the formatting dropdown in the toolbar may go blank at one point in the text and become paragraph at the next.
+
+The text is also irremovable ie bug 53708
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53708",1378217520,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-bqgfek7rspw6d5gukppc,task_description,resolved
+VisualEditor: Cursor cannot move through text created with jquery.IME when editing bulleted text,"(In reply to comment #1)
+> 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!
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+The patch seems to have partially fixed the bug.
+
+Text input using google input tools is now navigable.
+
+But text input using ULS IME hindi transliteration is still non-navigable. Pressing the left arrow key from the end of the text takes the caret to the beginning, and then left/right arrow key presses have no effect on the caret. (Same behaviour as before)
+
+The text formatting at all points in the bullet text remains as paragraph though (no blanking of the formatting drop-down).
+
+Text input with ULS is still irremovable ( bug 53708 )",1379516449,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-bqgfek7rspw6d5gukppc,task_subcomment,NA
+VisualEditor: Cursor cannot move through text created with jquery.IME when editing bulleted text,"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!",1378943051,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-bqgfek7rspw6d5gukppc,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Screenshot of incorrect text placement
+
+System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Enable ULS IME hindi transliteration
+
+Input:
+[ENTER/RETURN KEY]x2 (two newlines)
+agar[SPACE]ma
+
+Expected output:
+[NEWLINE]x2 (two newlines)
+अगर[SPACE]म
+
+Actual output:
+[NEWLINE]x2 (two newlines)
+अग[NEWLINE]र[SPACE]म
+
+Once [ENTER/RETURN KEY]x2 followed by agar[SPACE] has been pressed, Bug 53706 shows up. If one continues the input, this bug is what happens. The incorrect placement is accompanied by the following incorrect bahaviours:
+
+The VE toolbar shows no format (while the editing had been begun with paragraph)
+
+Cursor movement is incorrect. When the cursor is at the end, pressing up key takes it to the end of the first line, then pressing the down key takes it in the second line after the [SPACE] and before म It is here that the incorrect behaviour occurs. Pressing either the left or the right arrow keys takes it to the end of the line (ie after म) While this should happen on right arrow key press, the left arrow key press should take the cursor(caret) to before the space.
+
+Also, when at the end of the second line, pressing backspace does nothing. Similarly pressing delete anywhere in the second line does nothing. The second line effectively becomes irremovable, while the first line can be removed.
+
+Note: Page used for this test is [[:w:hi:सदस्य:Siddhartha Ghai/sandbox]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53711
+
+**Attached**: {F11165}",1378212900,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_description,resolved
+VisualEditor: Incorrect and irremovable text placement with IMEs,Automatic Incorrect caret movement has been reported separately as Bug 54424,1379768773,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Tested out this bug for page with pre-existing devanagari text.
+
+System Environment: Same as Comment 4
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit
+
+Steps:
+1 Enable ULS IME hindi transliteration
+2 Take the caret to the end of the first paragraph using the mouse (i.e click at the end of the first paragraph to take the caret there)
+3Input k
+3.1 This will give the output of क् with the newline selected ( Bug 53706 )
+4 Now input g
+4.1 This will give an output of ग् but this output will show up in the next line
+4.1.1 This output cannot be copy-pasted into an external text editor though it can be selected in VE
+4.1.2 This output is ignored in caret movement when using the arrow keys, so the caret goes straight from the beginning of the second paragraph to the end of the first paragraph just after क् jumping past ग् in between. When right arrow key is pressed the caret goes from here to the beginning of the second paragraph इस jumping past ग्
+4.1.3 Pressing backspace from the beginning of the second paragraph joins the second paragraph with the first paragraph jumping past the ग् making it the last text in the page
+4.1.4 Taking the caret to the end of text i.e after ग् makes the formatting dropdown go blank
+4.1.5 Using the VE toolbar Undo button moves the second paragraph back to a new line but it still stays above the ग् which is still the last text on the page.
+4.1.6 Undoing everything and adding a space to the end of the second paragraph and then submitting and reviewing the changes diff shows that the ग् at the end of the page is not being added
+4.1.7 Typing something after the ग् shows the text added after both ग् and the second paragraph.
+
+So effectively the bug is present even while editing existing pages with devanagari text using VE+ULS.",1379767940,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Reported console errors in Bug 54331 and Bug 54334 per Comment 7
+
+There's possibly other console error instances which need to be reported.
+
+(In reply to comment #8)
+> If you were able to test the issues for non-blank pages that would be a great
+> help too, because it looks like the problems happen in different ways in
+> those
+> two cases.
+
+Will do.",1379608845,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Thank you very much for providing this level of detail; I can't emphasise enough how helpful it is!
+
+If you were able to test the issues for non-blank pages that would be a great help too, because it looks like the problems happen in different ways in those two cases.",1379605340,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"(In reply to comment #6)
+> Could you please try typing some text on the following page, under the words
+> ""Testing Area"":
+> 
+>   https://www.mediawiki.org/w/index.php?title=Project:Sandbox&veaction=edit
+> 
+
+System environment: same as Comment 4
+
+Here's my primary analysis of editing on that page (without ULS).
+
+1. In the beginning the formatting dropdown is blank.
+1.1 Pressing [RETURN KEY] does not have any effect no matter how many times it is pressed.
+1.2 Pressing the [TAB KEY] takes the caret to the top of the page (above the ""edit this page"" template)
+1.3 Typing an ASCII character (or an international digit) changes the value in the formatting dropdown to paragraph.
+1.3.1 If a backspace is now pressed, the formatting remains the same.
+1.3.2 Pressing the [RETURN KEY] also works once an ASCII character has been input.
+1.3.3 Undoing all actions takes one back to the original position and [RETURN KEY] doesn't work again.
+
+Here's what happens with ULS hi transliteration (labelled लिप्यंतरण) enabled:
+
+1 Enabling ULS moves the caret to the top of the page (above the ""edit this page"" template) and the IME name लिप्यंतरण appears beside the ULS icon.
+1.1 Manually taking the caret to the original location below the ""Testing Area"" can be done
+1.1.1 If the caret is taken to the original location after the api call for the transliteration rules has completed, ULS icon shows that the transliteration method is not active (i.e no IME name visible beside the icon). This is incorrect as the dropdown for the menu shows the method selected and typing with the method works. Moving the caret manually back to the top still shows no change in the icon.
+1.1.2 If the caret is taken to the original position before the api call for the transliteration rules has completed, ULS icon shows the name of the IME correctly.
+1.1.3 Points 1.1.1 and 1.1.2 seem heisenbuggy and need to be confirmed.
+2 In the beginning (i.e nothing typed before), typing with ULS works, but the formatting dropdown remains blank.
+3 Input: agar[SPACE] Expected output: अगर[SPACE]
+3.1 The output अगर appears, but the space doesn't.
+3.1.1 Point to note: Per the hi transliteration rules in ULS agar itself gives अगर् i.e there is a viram ् (U+094D) at the end. ULS removes this when a space is input, i.e pressing space causes the removal of viram as well as the addition of space (this behaviour is the fix for bug 35990 ). So ULS is recognizing the space and removing the viram, but the space itself is getting lost somwehere between ULS and VE.
+3.1.2 Copying the text node text from within the chrome console and pasting in an external text editor showed the text to be prefixed by U+FEFF (ZERO WIDTH NO-BREAK SPACE)
+3.1.2 This text is not navigable using the left or right arrow keys.
+3.1.3 The text also cannot be copied. It can be selected manually with the mouse, but copying it is not possible. Pasting the selected text in an external editor showed nothing, as if no text had been selected. Tried copying using both the Ctrl+C keyboard shortcut and the right-click menu.
+3.4 Another space press is recognized. However, VE seems to treat this as the first input character.
+3.4.1 The original text disappears, replaced by the space. ( bug 53705 )
+3.4.2 The formatting dropdown shows the formatting to be paragraph.
+
+To my noobish eye, it appears that if VE was told to consider the default formatting to be paragraph (i.e no blank formatting dropdown in the beginning) OR VE considered any text input without a formatting dropdown value to be paragraph, ULS input disappearing would stop (I'm guessing this since once the formatting is set to paragraph, the text doesn't seem to disappear.)
+
+NOTE 1: This bug is starting to look a lot like a catchall to me, with automatic caret movement, incorrect formatting in the dropdown, non-detection of ULS input by VE, and what not. Feel free to file separate bugs where you find them necessary (or tell me which ones need to be filed separately, I'll be glad to help).
+
+NOTE 2: I reported this bug (along with a bunch of other related bugs) editing on a blank page so as to minimize bugs interfering with each-other and to have the simplest possible steps to reproduce the problem. However, I think that some of these may be applicable even on non-blank pages. Do I need to separately test the issues for non-blank pages and report the behaviour in these bugs (or are the current reports sufficient)?
+
+NOTE 3: I'm also ending up with a bunch of js console errors from VE, but I haven't checked exactly which step causes them. I'' try to reproduce them and let you know.",1379601354,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Thanks for specifying the exact keystrokes -- it really helps!
+
+There's a specific input issue when the whole page is blank (whether or not an input method is used, i.e. even if you just type ASCII characters).
+
+Could you please try typing some text on the following page, under the words ""Testing Area"":
+
+  https://www.mediawiki.org/w/index.php?title=Project:Sandbox&veaction=edit
+
+Then click ""Save Page"" and ""Review your changes"", and see whether the text appears correctly in the right-hand version. (After that, you can cancel the edit without saving).
+
+I can type देवनागरी (""devnagrI"" using my Ibus Hindi phonetic IME) there, and it appears correctly.",1379514033,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"The behaviour has also changed for the input described in Comment 1
+
+Test at hindi wikipedia:
+Test url:
+https://hi.wikipedia.org/wiki/%E0%A4%B8%E0%A4%A6%E0%A4%B8%E0%A5%8D%E0%A4%AF:Siddhartha_Ghai/sandbox?veaction=edit
+
+Input:
+agar[SPACE]main[SPACE]kahoon[SPACE][RETURN KEY]
+
+Output:
+Fine except the newline never appears, no matter how many times the return key is pressed. The newline does not appear even when google input tools are disabled and the keyboard switched back to English (United States). The formatting dropdown is blank. The text is non-navigable ( bug 53711 ). However, pressing the left and right arrow keys a bunch of times and then pressing the return key still causes the text to be replaced with a newline followed by ♙
+
+Test at Mediawiki.org:
+Test url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+The behaviour with google input tools seems to be correct with the newline being placed correctly, and the text being navigable.",1379511359,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"(In reply to comment #3)
+> 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!
+
+The patch doesn't fix the bug. The behaviour has changed, however, and on first look it appears to be for the worse.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Input and expected output:
+Same as in comment 0
+
+Test at hindi wikipedia:
+Test url:
+https://hi.wikipedia.org/wiki/%E0%A4%B8%E0%A4%A6%E0%A4%B8%E0%A5%8D%E0%A4%AF:Siddhartha_Ghai/sandbox?veaction=edit
+
+What actually happens: (is too weird to be explained without prose)
+1. After inputting 2 newlines, as soon as a is pressed, VE shows input of अ but one line above the current line, i.e caret automatically moves from line 3 to line 2.
+2. Further inputting gar[SPACE] makes bug 53706 to show up, ie we have अगर[SPACE] in the second line with the space and newline selected, and the formatting dropdown having blanked.
+3. Then inputting m makes म् appear, but its in the next line, i.e line three.
+4. The caret has also moved back to line three ahead of it.
+5. Then, when the final a is input, the अगर[SPACE] in line two changes to अग with the र[SPACE] having moved to the beginning of line three followed by म . The text in line three is irremovable.
+
+Test at Mediawiki.org:
+Test url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+Firstly the page is blanked and the formatting reset to paragraph. The input described in Comment 0 is then done.
+
+What actually happens:
+Step 1-5 same as hindi wikipedia.
+Following this, after a (noticeable) fraction of a second, the text र[SPACE]म appears in the first line and the newline between lines 1 and 2 is selected.
+Caret movement is weird. When caret is at the end of the text (i.e end of third line), pressing a left arrow key takes it straight to the beginning of the second line. A right arrow keypress takes the caret back to end of third line. This effectively means that the text in lines two and three is non-navigable ( bug 53711 ). Pressing a backspace at the end of the third line removes the entire second line text, taking the caret to the second line. The first line is both navigable and removable. The third line text however, is irremovable.",1379510564,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"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!",1378943038,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,This bug was also seen when VE testing revealed Bug 53711,1378218621,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"This bug (or a variant of it) seems to happen when using Google input tools for hindi.
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Enable google input tools IME
+Type something. example keystrokes: agar[SPACE]main[SPACE]kahoon[SPACE][RETURN KEY]
+
+Expected output:
+The text is typed(exact output text would depend on the IME's translation memory, macros used etc.) with a newline at the end and the cursor (caret) in the newline.
+
+Actual output:
+The text is typed correctly, the newline is also placed, but the cursor remains in the first line. The formatting dropdown of the VE toolbar is blank. It changes back to paragraph on pressing either the right or left arrow key (haven't tested with any other key).
+
+Pressing the return key again causes the newline to disappear while the text remains (variant of Bug 53705 ?). The same behaviour (correctly) takes place on pressing the delete key.
+
+Possibly different bug: When at the end of the first line, pressing the left/right arrow keys a bunch of times and then pressing the return key made me somehow end up with ♙ as the only text and all the input text gone.
+
+Also note that this bug doesn't seem to appear when using the native windows input devanagari-INSCRIPT",1378214611,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Reset title opacity on API call failure,"System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Let the API call for the parsed json output fail
+VE asks if you would like to retry, press Cancel
+
+Expected behaviour:
+VE should reset the opacity for the title and sitesub back to 1 from 0.6
+
+Actual behaviour:
+Opacity is not changed, leaving it 0.6 although the user is effectively reading the article, not editing it with VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378211220,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-jvygvcsdp3dse45vpayw,task_description,resolved
+VisualEditor: Reset title opacity on API call failure,I believe we fixed this a few months ago; sorry for the slow triage.,1402329753,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jvygvcsdp3dse45vpayw,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"Screenshot of selection error
+
+System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Enable ULS IME hindi transliteration
+
+Input:
+[RETURN/ENTER KEY]x4 (four newlines)
+agar[SPACE]
+
+Expected output:
+[NEWLINE]x4 (four newlines)
+अगर[SPACE]
+
+no text selection should be there
+
+Actual output:
+[NEWLINE]x4 (four newlines)
+अगर[SPACE]
+
+the ending [SPACE] is selected with a newline. Also, the toolbar shows that VE has somehow jumped to changing the formatting to bulleted and numbered list from the original paragraph formatting.
+
+Further, pressing a backspace deletes not only the selected space/newline, but also the typed text अगर. I think this is Bug 53705 though I may be wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53700
+
+**Attached**: {F11150}",1378210380,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ejote3xjqqm7riq7xqwf,task_description,resolved
+VisualEditor: Incorrect text selection with jquery.IME,"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.",1453749350,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"Further testing Comment 3 seems to indicate that the newline selection happens when the last input is a consonant followed by a halant which can be input with one keystroke.
+
+The hindi transliteration IME inputs two characters whenever an ASCII consonant is input, the equivalent hindi consonant followed by the halant character ् (U+094D)
+
+So inputting g gives ग् i.e ग + ् , j gives ज् i.e ज + ् etc. with the newline selected.
+
+Some hindi consonants, however, need two keystrokes to be input. So gh gives घ् i.e घ + ् and jh gives झ् i.e झ + ् etc. Output for these depends on the input speed. If one is quick, the text is input correctly with no selection. However, if one is slow, Bug 54421 shows up with the grapheme containing the duplicated text at the beginning of the article being selected.
+
+This selection (or non-selection) behaviour takes place regardless of whether the input is one consonant or a word. The behaviour depends on what the last consonant is, one that can be input with one keystroke or one that is input with two keystrokes.",1379766638,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,Note: Comment 3 is ofcourse with ULS IME hindi transliteration enabled.,1379764673,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"Screenshot for comment 3
+
+**Attached**: {F11151}",1379764061,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"Per https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c8 the following report is for the bug behaviour when tested on a page with pre-existing text:
+
+System Environment:
+Windows7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit
+
+Steps:
+Take a caret to the end of the first paragraph using the mouse (i.e click at the end of the first paragraph to take the caret there.)
+Input ag
+
+Expected output:
+अग्
+
+Actual output:
+अग् but with the newline after it selected, although the newline or space wasn't typed in this edit and existed previously.",1379763646,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"(In reply to comment #1)
+> 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!
+
+The patch doesn't fix the bug.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test URL:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+Steps:
+Enable ULS IME hi transliteration
+Blank the page and reset the formatting to simple paragraph
+Follow the input steps described in Comment 0
+
+Result:
+The output is the same as described in Comment 0 as far as content selection is concerned. The formatting however, instead of changing to bulleted and numbered list, has gone blank. The formatting dropdown shows no value and no button in the VE toolbar is selected.
+
+Pressing backspace still deletes the space and the word. It also resets the formatting to paragraph.",1379508686,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.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!",1378943020,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Enable ULS IME hindi transliteration
+
+Input 1:
+agar[SPACE][ENTER/RETURN KEY]
+
+Input 2:
+kyaa[SPACE]
+
+Expected output 1:
+अगर[SPACE][NEWLINE]
+
+Expected output 2:
+क्या[SPACE]
+
+Actual output 1:
+[NEWLINE]
+
+Actual output 2:
+[SPACE]
+
+For the first case, when the given characters are typed, everything is fine upto the pressing of the return key, ie agar[SPACE] gives अगर[SPACE] as expected. However, as soon as the return key is pressed the entire text disappears leaving only a newline.
+
+For the second case, everything is fine till [SPACE] is pressed.
+
+If the page is not blank, extreme weirdness occurs, which can only be explained with further bugs (which I'm about to file). In short though, the disappearances persist, along with other buggy effects.
+
+Note: Page used for this test is [[:w:hi:सदस्य:Siddhartha Ghai/sandbox]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378209360,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ycbizrojj6ti4ywzojyo,task_description,resolved
+VisualEditor: Content disappears when using jquery.IME,"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.",1453749356,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"Hi,
+
+Besides Marathi and Hindi I tested this bug for more indic languages like Bangla, Ahirani,Konkni, etc.
+
+Even after defficulties I am trying to use VE+ULS combination on Marathi Wikipedia as much as possible to have real time feel and understand the issues better.
+
+For an example on Marathi Wikipedia we do have a page https://mr.wikipedia.org/wiki/वॉर_अँड_पीस . Other than info box it is empty. In Hindi and Marathi Wikipedia we do have large(huge) number of pages which are almost empty.Not able to type first word itself is a major hindrance and challenge before VE+ULS combinations.
+
+So wish and hope bug number 53700 and 53705 remain on priority list 
+
+
+rgds",1379826886,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"HTML after input kyaa[SPACE]
+
+**Attached**: {F11140}",1379506412,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"HTML after input kyaa
+
+**Attached**: {F11139}",1379506301,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"HTML after input agar[SPACE][ENTER/RETURN KEY]
+
+**Attached**: {F11138}",1379506002,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"HTML after input agar[SPACE]
+
+**Attached**: {F11136}",1379505701,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"(In reply to comment #3)
+> Here's the HTML which is in the result:
+
+The above HTML is not entirely correct. Copy-pasting messed up the text nodes. I'll be adding screenshots for the html as seen in the chrome console.",1379505046,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"(In reply to comment #2)
+> 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!
+
+The bug is not fixed. The behaviour for both the spaces specified in Comment 0 is still the same. Tested at https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+Here's the HTML which is in the result:
+
+HTML for Input 1:
+
+<div class=""ve-ce-documentNode ve-ce-branchNode"" contenteditable=""true"" spellcheck=""true"" lang=""en"" dir=""ltr""><p class=""ve-ce-branchNode""><span class=""ve-ce-branchNode-slug ve-ce-branchNode-inlineSlug""></span></p><p class=""ve-ce-branchNode""><span class=""ve-ce-branchNode-slug ve-ce-branchNode-inlineSlug""></span></p></div>
+
+HTML for Input 2:
+
+<div class=""ve-ce-documentNode ve-ce-branchNode"" contenteditable=""true"" spellcheck=""true"" lang=""en"" dir=""ltr""><p class=""ve-ce-branchNode"">&nbsp;</p></div>",1379503794,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.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!",1378943009,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,The further weirdness mentioned above is explained in Bug 53706 and Bug 53708,1378213142,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"*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
+
+*Problem description =In normal speed typing,after we type first alphaabate cursor moves from right to left direction.Word marathi need to apear मराठी with VE+ULS instead is coming राठीम 	
+
+**additional details = Marathi language devanagari is written in left to right direction.But when we use ULS Method of input = अक्षरांतरण with VE cursor is moving in opposite direction after typing first charecter as if we are typing a right to left script after typing first charecter and then again moves left to right 
+
+*Screenshot will be added
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49569",1378208100,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-fzc2bascptcvyjvfz6iv,task_description,resolved
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"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.",1453749391,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"Would it be possible to test 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!",1381270429,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"Automatic Incorrect caret movement has been reported separately as Bug 54424
+
+I suspect that this bug is a special case of that bug, but I may be wrong.",1379768841,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"(In reply to comment #2)
+
+Did primary testing seems some change of behaviour and different kind of weird  aspects . will need more tests and time before confirming. 
+
+Rgds",1379657273,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.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!",1378942983,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"[Not a blocker, see http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity ]
+
+> *Tested Browser and OS =Firefox+Win7
+
+Which Firefox version?
+
+
+What I tried:
+1. Go to http://mr.wikipedia.org/wiki/%E0%A4%85%E0%A4%AB%E0%A4%97%E0%A4%BE%E0%A4%A3%E0%A4%BF%E0%A4%B8%E0%A5%8D%E0%A4%A4%E0%A4%BE%E0%A4%A8
+2. make sure to be logged in
+3. Go to माझ्या पसंती (Preferences), संपादन and enable last option: यथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this enables VisualEditor
+4. Click cog next to इतर भाषांमध्ये
+5. Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण
+6. Click संपादन (Edit)
+7. Make sure that URL ends with &veaction=edit
+8. Type
+
+Results are weird under Firefox 23.0.1 and Fedora 19 (new lines inserted etc), but typing is not always backwards.",1378212107,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","*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
+
+*Problem description = No other text on a page> Type a word + space bar = eliminates typed text imidiately
+
+**additional details = If some text is already there on the page or we copy paste then we can give the space bar with less frequency of this problem.
+
+
+*Screen shot or Difference of edit if available = Can not create the screen shot/or edit diff
+
+
+Thanks and Regards
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49569
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53706",1378207380,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-3e25u2t2rvump3xhzmpi,task_description,resolved
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","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.",1453749416,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","Not just Marathi/Devanagari specific, apparently it's a general problem with jquery.IME in VE.",1381270732,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately",*** Bug 54960 has been marked as a duplicate of this bug. ***,1381270703,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","(In reply to comment #6)
+> (In reply to comment #4)
+> > I tested on  mr wiki
+> 
+> As comment 3 said, it's available on ***mediawiki.org***, not mr wiki (yet).
+> mediawiki.org is where to test it.
+
+Confirming this is not fixed.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test URL:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+Steps to reproduce:
+Enable ULS IME mr transliteration (labelled अक्षरांतरण)
+Blank the page (and reset formatting to simple paragraph, i.e remove bulleted list formatting)
+
+Input 1:
+agar[SPACE]
+
+Output 1:
+[SPACE]
+
+Expected Output (as seen in the old editor):
+अगर्[SPACE]
+
+Input 2:
+kyaa[SPACE]
+
+Output 2:
+[SPACE]
+
+Expected Output (as seen in the old editor):
+क्या[SPACE]",1379504653,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","(In reply to comment #4)
+> I tested on  mr wiki
+
+As comment 3 said, it's available on ***mediawiki.org***, not mr wiki (yet). mediawiki.org is where to test it.",1379323479,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","(In reply to comment #4)
+
+Hello, gave one more try during a live edit correction, result no success.
+
+*On mr wikipedia page was https://mr.wikipedia.org/wiki/नारायण_श्रीपाद_राजहंस  
+
+*During the last edit diff https://mr.wikipedia.org/w/index.php?title=नारायण_श्रीपाद_राजहंस&diff=1198688&oldid=1184350 one new user has removed  section heading to word जीवन  
+
+*I took corrective editing target to type Marathi word व्यक्तीगत (by using VE+ULS method ) before word जीवन   so it will be a two word section heading  ==व्यक्तीगत जीवन==
+** Sentence to be edited जीवन नारायण श्रीपाद राजहंस यांचा जन्म जून २६, इ.स. १८८८ रोजी जिल्ह्यातील पलुस तालुक्यात नागठाणे या गावी झाला.
+
+
+Steps tried
+
+*Visit Marathi language wikipedia
+*Enable visual editor from preferences [[Special:Preferences#mw-prefsection-editing]]
+* page https://mr.wikipedia.org/wiki/नारायण_श्रीपाद_राजहंस
+
+
+* Clicked संपादन that is edit (Visual Editor's)
+
+* Sentence appeared  जीवन ↵नारायण श्रीपाद राजहंस यांचा जन्म जून २६, इ.स. १८८८ रोजी जिल्ह्यातील पलुस तालुक्यात नागठाणे या गावी झाला. 
+
+* Display language Marathi For Input method selected ULS> 1)अक्षरांतरण (transliteration)
+
+*Clicked Enter after word जीवन  since rest of line needs to be in paragraph portion
+
+*Took cursor before word जीवन  
+
+* To transliterate Typed keys from key board 'vyaktigata >> अक्षरांतरण transliteration transliterated to>> व्यक्तिगत transliteration was success.
+
+* Then 'Pressed space bar' the result was word 'व्यक्तिगत' disappeared.
+
+
+* Repeated above with different ULS input method  ULS> 2) इनस्क्रिप्ट (Inscript)
+
+** To transliterate typed keys  bd/kdlfil transliterated to>> व्यक्तिगत transliteration was success.
+
+** Then 'Pressed space bar' the result was word 'व्यक्तिगत' disappeared.
+
+Windows 7 + tried two browsers Firefox (version mentioned earlier) and Google Chrome (is up to date Version 29.0.1547.66 m)  The results were failure.
+
+
+(VE+windows native Input method इनस्क्रिप्ट 'in script' worked successfully to type word  व्यक्तिगत + space bar was success.) 
+
+We still wait and look forward to VE +ULS success. Best wishes for the same 
+
+Rgds",1379248005,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","Hello,
+
+This is 14th Sept 18.52 pm Indian standard time. I tested on  mr wiki couple of pages and tested on en wiki my own user space . To me problem is as is and not resolved.
+
+
+Thanks and best wished for your continued effort
+
+
+Rgds",1379165121,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","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!",1378942971,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately",Possible duplicate: Bug 53705,1378228533,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","[Not a blocker, see http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity ]
+
+Confirming for Firefox 23.0.1 and Fedora 19.
+
+Steps to reproduce:
+1. Go to non existing page like https://mr.wikipedia.org/w/index.php?title=%E0%A4%85%E0%A4%AB%E0%A4%97%E0%A4%BE
+2. make sure to be logged in
+3. Go to माझ्या पसंती (Preferences), संपादन and enable last option: यथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this enables VisualEditor
+4. Click cog next to इतर भाषांमध्ये
+5. Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण
+6. Click तयार करा (Create page)
+7. Make sure that URL ends with &veaction=edit
+8. Type a word and press spacebar.",1378212092,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: Trigger keys can end up in CE surface, but not in DM","A user reported a problem to use the ""clear formatting"" shortcut with a french AZERTY keyboard. The shortcut is ""Ctrl + \"", but ""\"" is only accessible as ""AltGr + 8"".
+
+First, even with, ""Ctrl + AltGr + 8"", the shortcut doesn't work. I was unable to find a keyboard combination that triggers the ""clear formatting"" shortcut. When using a classic QWERTY keyboard, ""Ctrl + \"" works on the same computer/browser.
+See https://bugzilla.wikimedia.org/show_bug.cgi?id=51507
+
+But, when testing, I noticed an other problem, with a behaviour depending on OS/browser when using ""Ctrl + AltGr + 8"" with text selected:
+* On W7 + Chrome 29, the selected text is replaced by ""\"", but VE doesn't see any modification: save is disabled, undo is disabled, ...
+* On W7 + Firefox 23, the selected text is replaced by ""\"", and VE sees that text has been modified
+* On Ubuntu 12.04 LTS + Firefox 20, a user report that all page is selected.
+
+Same kind of problems happen with ""Ctrl + Alt + 8"", ""Alt + 8"", ... or other digits.
+
+https://fr.wikipedia.org/w/index.php?title=Wikipédia:ÉditeurVisuel/Avis#Raccourci_clavier_pour_effacer_la_mise_en_forme
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51507",1378132560,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-kxbkw2kfnhnvqihjlumu,task_description,resolved
+"VisualEditor: Trigger keys can end up in CE surface, but not in DM","Actually I think this was already fixed before Change 247800: On Ubuntu 15.10 with French keyboard, Alt+8 into a non-collapsed selection seems to overwrite the selection with \ in both the DOM and the DM, in both Firefox 42 and Chromium 45.",1449084298,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-kxbkw2kfnhnvqihjlumu,task_subcomment,NA
+"VisualEditor: Trigger keys can end up in CE surface, but not in DM","Change 247800 had a related patch set uploaded (by Divec):
+Diff richtext to build model changes
+
+[[https://gerrit.wikimedia.org/r/247800]]
+",1449082903,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kxbkw2kfnhnvqihjlumu,task_subcomment,NA
+"VisualEditor: Trigger keys can end up in CE surface, but not in DM",Trigger issue is split to bug 56452. Re-titled.,1383283899,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kxbkw2kfnhnvqihjlumu,task_subcomment,NA
+VisualEditor: Table rows with no defined cells rendered as an empty line,"At https://en.wikipedia.org/w/index.php?title=Flight_endurance_record&oldid=571122193#Free_Balloon.2C_Manned the table begins with an empty row where there would normally be a header:
+{|class=""wikitable""
+|-
+|-
+|content
+
+In view mode this empty line is not shown, but it does appear in VE.
+
+Testing at https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=571124234#Tables_with_empty_rows shows that the same thing happens, wherever the blank line is in the table. Oddly though the line is shown at full height when its in last position but ~half height elsewhere.
+
+In itself this isn't a problem, it's just different to what happens in view mode where the second |- is ignored.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1378066380,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-c6mjvz42mmi6bswdw56d,task_description,resolved
+VisualEditor: Table rows with no defined cells rendered as an empty line,This was fixed a while ago by the Parsoid team.,1404172794,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c6mjvz42mmi6bswdw56d,task_subcomment,NA
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#deprecated"" from TemplateData","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377905520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4ua7w7m7aik6txmrerbe,task_description,resolved
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#deprecated"" from TemplateData","Change 129856 merged by jenkins-bot:
+Restyle parameter pages
+
+https://gerrit.wikimedia.org/r/129856",1398900767,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4ua7w7m7aik6txmrerbe,task_subcomment,NA
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#deprecated"" from TemplateData","Change 129856 had a related patch set uploaded by Trevor Parscal:
+Restyle parameter pages
+
+https://gerrit.wikimedia.org/r/129856",1398469830,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4ua7w7m7aik6txmrerbe,task_subcomment,NA
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#required"" from TemplateData","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377905340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-346l3sxkrxirwfv4rf4g,task_description,resolved
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#required"" from TemplateData",Verified the fix in test2,1390422254,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-346l3sxkrxirwfv4rf4g,task_subcomment,NA
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#required"" from TemplateData",Done in I8f84a9ae277e5093356f591f7a56e8cebf4a1893.,1389902644,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-346l3sxkrxirwfv4rf4g,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, cursor keys can let you select parameters in the search results off the > screen and the dialog doesn’t scroll","
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377905220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3g3rbtewmym2ch553j4x,task_description,resolved
+"VisualEditor: In the transclusion dialog, cursor keys can let you select parameters in the search results off the > screen and the dialog doesn’t scroll","Change 74566 merged by jenkins-bot:
+Scroll into view support
+
+https://gerrit.wikimedia.org/r/74566",1379434760,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3g3rbtewmym2ch553j4x,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, cursor keys can let you select parameters in the search results off the > screen and the dialog doesn’t scroll","Change 74566 had a related patch set uploaded by Jforrester:
+Scroll into view support
+
+https://gerrit.wikimedia.org/r/74566",1378774554,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3g3rbtewmym2ch553j4x,task_subcomment,NA
+VisualEditor: Transclusion dialog improvements (tracking),"[Now tracked as #VisualEditor-MediaWiki-Templates instead.]
+
+
+Fork from bug 49833, which wasn't meant to be used this way.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377900000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3niuhnlezs7jfmugbwdy,task_description,resolved
+VisualEditor: Transclusion dialog improvements (tracking),[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343622,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3niuhnlezs7jfmugbwdy,task_subcomment,NA
+Add a functionality to gray out gadgets on gadgets preference tab that are dependent on other gadgets.,"Gadget checkboxes should be able to be grayed out (inaccessible) dependent on if another gadget is on or off, if other extensions exist that gadgets are unable to use, or if they require a specific skin to work.  For example, on en.wikipedia the current ""Editing"" section of the gadget tab on the preferences page looks like:
+ 
+[[ https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(current).png | commons:File:Special_Preferences_mw-prefsection-gadgets_(current).png ]]
+
+There should be a way to gray out functions, like:
+ 
+[[ https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(proposed).png | commons:File:Special_Preferences_mw-prefsection-gadgets_(proposed).png ]]
+If (in this instance) VisualEditor is enabled.",1377865740,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-anwdvhxvorgu42thq5we,task_description,open
+Add a functionality to gray out gadgets on gadgets preference tab that are dependent on other gadgets.,">>! In T55584#581617, @matmarex wrote:
+> The BetaFeatures extension implements something similar, maybe it could be extended to work with Gadgets. But I'm not sure if it's a good idea, you could just use the dependency system to load other gadgets regardless.
+
+Except in cases where the user doesn't want to use that other gadget.  In those cases, the dependent gadget should be greyed out and indicate they require the other component.  This lets the editor/user decide.",1419544542,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-anwdvhxvorgu42thq5we,task_subcomment,NA
+Add a functionality to gray out gadgets on gadgets preference tab that are dependent on other gadgets.,"The BetaFeatures extension implements something similar, maybe it could be extended to work with Gadgets. But I'm not sure if it's a good idea, you could just use the dependency system to load other gadgets regardless.",1383302073,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-anwdvhxvorgu42thq5we,task_subcomment,NA
+VisualEditor: histograms are duplicated while editing,"https://fr.wikipedia.org/w/index.php?title=Polisy&veaction=edit
+or
+https://fr.wikipedia.org/w/index.php?title=Aix-en-Othe&veaction=edit
+
+The demographic histogram gets duplicated while VEditing, although everything will be fine again once you save, but I see this can confuse users.
+
+Looks like it is generated, like other parts of the Démographie section, by https://fr.wikipedia.org/wiki/Mod%C3%A8le:Section_d%C3%A9mographie_d%27article_de_commune_de_France .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377864060,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sqkvabmnd7cfcbr6tkhz,task_description,resolved
+VisualEditor: histograms are duplicated while editing,"I don't see anything weird either on https://fr.wikipedia.org/w/index.php?title=Aix-en-Othe&veaction=edit
+
+Closing as FIXED.",1424365332,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-sqkvabmnd7cfcbr6tkhz,task_subcomment,NA
+VisualEditor: histograms are duplicated while editing,I discovered the bug in August 2013 and it was said to be fine from November 2013 at fr.wp. It must have been fixed by chance.,1422480548,PHID-USER-4cgt73x34j35pnbem65l,PHID-TASK-sqkvabmnd7cfcbr6tkhz,task_subcomment,NA
+VisualEditor: histograms are duplicated while editing,Looks fine to me... Was this fixed at some point?,1421888433,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-sqkvabmnd7cfcbr6tkhz,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Have seen multiple instances of this one backing up on commonswiki slaves recently:
+
+SELECT /* IndexPager::buildQueryInfo (LogPager) 148.160.132.46 */  log_id,log_type,log_action,log_timestamp,log_user,log_user_text,log_namespace,log_title,log_comment,log_params,log_deleted,user_id,user_name,user_editcount,ts_tags  FROM `logging` FORCE INDEX (times) LEFT JOIN `user` ON ((log_user=user_id)) LEFT JOIN `tag_summary` ON ((ts_log_id=log_id))  WHERE (log_action != 'revision') AND (log_type != 'suppress') AND log_type IN ('delete','move')  AND log_namespace = '0' AND log_title = '0' AND ((log_deleted & 1) = 0)  ORDER BY log_timestamp DESC LIMIT 11
+
+It runs in excess of 10 minutes.
+
+EXPLAIN says the FORCE INDEX sends MySQL onto a very slow index scan over `times` (log_timestamp) which is hardly better than a table scan in this case.
+
+Removing the FORCE allows `page_time` index be used which reduces execution time to a few seconds.
+
+Suggest either filtering by a range on log_timestamp or removing the FORCE.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54122",1377856620,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_description,resolved
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"With partitioned slaves LogPager queries are still not super fast, but they average <10s now and no longer dominate the slow query log.
+
+Closing this.",1396153047,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"16 looks reasonable, I just wouldn't want something crazy like 256 ;)",1389312673,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"16 partitions, a number chosen after some rough back-of-napkin style calculations for the larger wikis.
+
+The effect of accessing multiple partitions is closest to UNION. I don't anticipate excessive sorting or limiting penalties for our other queries though I do want to see how range access and index scans perform.
+
+Monitoring for queries adversely affected is definitely necessary and one of the reasons for only partitioning one slave per shard.",1389312419,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,How many partitions per table? So the Special:Log (no filter) case will have to UNION/resort/limit queries from each partition?,1389305283,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Much better than it was.
+
+I'm now trialing partitioned logging tables on one slave per production shard and directing these queries to those boxes. Since most of the queries use log_user = N, partitioning on key(log_user) allows the optimizer to use partition pruning.
+
+Still have to track down and sort out the ones without log_user = N. They're infrequent and low priority.",1389304624,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Resetting status as per comment 9. Sean: Is this still high prio?,1389268532,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"You're right, most of the slow queries we've seen in spikes do filter by log_user. But there are others that don't that also run slow.
+
+Ishmael, S3, db1003:
+
+/* IndexPager::buildQueryInfo */ select log_id, log_type, log_action, log_timestamp, log_user, log_user_text, log_namespace, log_title, log_comment, log_params, log_deleted, user_id, user_name, user_editcount, ts_tags from `logging` left join `user` on ((log_user=user_id)) left join `tag_summary` on ((ts_log_id=log_id)) where (log_type not in(?+)) and (log_type != ?) order by log_timestamp desc limit ?
+
+I went to S3 because that's where I saw the query form previously (zhwiktionary at the time). A quick check on S2 slaves doesn't show the same query running slow there, though there are other versions:
+
+* IndexPager::buildQueryInfo */ select log_id, log_type, log_action, log_timestamp, log_user, log_user_text, log_namespace, log_title, log_comment, log_params, log_deleted, user_id, user_name, user_editcount, ts_tags from `logging` left join `user` on ((log_user=user_id)) left join `tag_summary` on ((ts_log_id=log_id)) where (log_type != ?) and log_type = ? and log_namespace = ? and log_title = ? and ((log_deleted & ?) != ?) order by log_timestamp desc limit ?
+
+It's possible we'll trawl some of these up with the existing patch. Just something to keep in mind.",1384674453,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Which slow queries are *not* filtering on user ID? I thought that is where the slow queries still mostly happen.,1384673187,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Change 95584 merged by Springle:
+Changed use of tag_summary to use change_tag with GROUP_CONCAT()
+
+https://gerrit.wikimedia.org/r/95584",1384671061,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"True, ct_log_id cardinality still isn't brilliant, but it's better than ts_log_id.  The index is one that fluctuates cardinality estimates quite a bit between slaves, requiring periodic ANALYZE.  Eg, today the enwiki slaves manage to report ct_log_id cardinality values between 21 and 290251 :-| 
+
+Also, ct_log_id index covers (ct_log_id,ct_tag) which is useful.
+
+I've been trying different values for innodb_stats_sample_pages (=16 and =32) on several slaves to see if cardinality for a number of flakky indexes can be stabilized without the need for regular analysis (because of http://bugs.mysql.com/bug.php?id=33278). 
+
+After our chat on IRC on Friday I applied the change_tag/subquery version to other examples of slow LogPager logged on various wikis. It is generally better overall but can still be susceptible to hitting too much cold data.
+
+I'd still really like to see consideration on:
+
+- Making log_user=N clause enforced. The examples of the query that don't filter by user id hit the most rows.
+
+- If log_user=N isn't to be used then limit exposure to the last N months of data or something or change the way it's viewed entirely.
+
+- Consideration of your suggestion to break up tag_summary into three tables, which seems like a good plan given we already denormalize for tag_summary.",1384670134,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Though actually doesn't change_tag also have similar poor cardinality problems for the log_id index?,1384640491,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Change 95584 had a related patch set uploaded by Aaron Schulz:
+Changed use of tag_summary to use change_tag with GROUP_CONCAT()
+
+https://gerrit.wikimedia.org/r/95584",1384500369,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Possibilities after talking with Aaron on IRC, assuming group_concat can be sorted in MW code for pg...
+
+Using change_tag instead of tag_summary avoids the poor cardinality of ts_log_id and allows better query plans on `logging` indexes:
+
+v1
+
+enwiki> explain SELECT log_id,log_type,log_action,log_timestamp,log_user,log_user_text,log_namespace,log_title,log_comment,log_params,log_deleted,user_id,user_name,user_editcount,group_concat(distinct ct_tag separator ' ') as ts_tags FROM `logging`  LEFT JOIN `user` ON ((log_user=user_id)) LEFT JOIN change_tag ON (ct_log_id=log_id) WHERE (log_type NOT IN ('suppress','spamblacklist','review')) AND log_user = ? AND ((log_deleted & 4) = 0) GROUP BY log_id ORDER BY log_timestamp DESC LIMIT 51\G
+*************************** 1. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: logging
+         type: index
+possible_keys: type_time,user_time,log_user_type_time
+          key: times
+      key_len: 16
+          ref: NULL
+         rows: 2583
+        Extra: Using where; Using temporary
+*************************** 2. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: user
+         type: const
+possible_keys: PRIMARY
+          key: PRIMARY
+      key_len: 4
+          ref: const
+         rows: 1
+        Extra: 
+*************************** 3. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: change_tag
+         type: ref
+possible_keys: ct_log_id,change_tag_log_tag
+          key: ct_log_id
+      key_len: 5
+          ref: enwiki.logging.log_id
+         rows: 35
+        Extra: Using where; Using index
+3 rows in set (0.31 sec)
+
+pt-visual-explain
+
+JOIN
++- Filter with WHERE
+|  +- Index lookup
+|     key            change_tag->ct_log_id
+|     possible_keys  ct_log_id,change_tag_log_tag
+|     key_len        5
+|     ref            enwiki.logging.log_id
+|     rows           35
++- JOIN
+   +- Bookmark lookup
+   |  +- Table
+   |  |  table          user
+   |  |  possible_keys  PRIMARY
+   |  +- Constant index lookup
+   |     key            user->PRIMARY
+   |     possible_keys  PRIMARY
+   |     key_len        4
+   |     ref            const
+   |     rows           1
+   +- Table scan
+      +- TEMPORARY
+         table          temporary(logging)
+         +- Filter with WHERE
+            +- Bookmark lookup
+               +- Table
+               |  table          logging
+               |  possible_keys  type_time,user_time,log_user_type_time
+               +- Index scan
+                  key            logging->times
+                  possible_keys  type_time,user_time,log_user_type_time
+                  key_len        16
+                  rows           2583
+
+v2
+
+enwiki> explain SELECT log_id,log_type,log_action,log_timestamp,log_user,log_user_text,log_namespace,log_title,log_comment,log_params,log_deleted,user_id,user_name,user_editcount,(select group_concat(distinct ct_tag separator ' ') from change_tag where ct_log_id = log_id) as ts_tags FROM `logging`  LEFT JOIN `user` ON ((log_user=user_id)) WHERE (log_type NOT IN ('suppress','spamblacklist','review')) AND log_user = ? AND ((log_deleted & 4) = 0) ORDER BY log_timestamp DESC LIMIT 51\G
+*************************** 1. row ***************************
+           id: 1
+  select_type: PRIMARY
+        table: logging
+         type: range
+possible_keys: type_time,user_time,log_user_type_time
+          key: log_user_type_time
+      key_len: 38
+          ref: NULL
+         rows: 18675
+        Extra: Using index condition; Using where; Using filesort
+*************************** 2. row ***************************
+           id: 1
+  select_type: PRIMARY
+        table: user
+         type: const
+possible_keys: PRIMARY
+          key: PRIMARY
+      key_len: 4
+          ref: const
+         rows: 1
+        Extra: 
+*************************** 3. row ***************************
+           id: 2
+  select_type: DEPENDENT SUBQUERY
+        table: change_tag
+         type: ref
+possible_keys: ct_log_id,change_tag_log_tag
+          key: ct_log_id
+      key_len: 5
+          ref: enwiki.logging.log_id
+         rows: 35
+        Extra: Using where; Using index
+3 rows in set (0.32 sec)
+
+pt-visual-explain
+
+DEPENDENT SUBQUERY
++- Filter with WHERE
+|  +- Index lookup
+|     key            change_tag->ct_log_id
+|     possible_keys  ct_log_id,change_tag_log_tag
+|     key_len        5
+|     ref            enwiki.logging.log_id
+|     rows           35
++- JOIN
+   +- Bookmark lookup
+   |  +- Table
+   |  |  table          user
+   |  |  possible_keys  PRIMARY
+   |  +- Constant index lookup
+   |     key            user->PRIMARY
+   |     possible_keys  PRIMARY
+   |     key_len        4
+   |     ref            const
+   |     rows           1
+   +- Filesort
+      +- Filter with WHERE
+         +- Index range scan
+            key            logging->log_user_type_time
+            possible_keys  type_time,user_time,log_user_type_time
+            key_len        38
+            rows           18675
+
+
+v2 appears slightly better.",1384474133,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Larger WMF wikis are seeing more spikes of LogPager queries of which an example follows. These have had some recent tuning by initially removing forced indexes that no longer suited data set sizes, which has helped (10min down to ~100s), but we need to do more.
+
+mysql wmf db73 dewiki> explain SELECT /* IndexPager::buildQueryInfo (LogPager) xxx.xxx.xxx.xxx */ log_id,log_type,log_action,log_timestamp,log_user,log_user_text,log_namespace,log_title,log_comment,log_params,log_deleted,user_id,user_name,user_editcount,ts_tags FROM `logging` LEFT JOIN `user` ON ((log_user=user_id)) LEFT JOIN `tag_summary` ON ((ts_log_id=log_id)) WHERE (log_type NOT IN ('suppress','spamblacklist')) AND log_user = ? AND ((log_deleted & 4) = 0) AND (log_type != 'review') ORDER BY log_timestamp DESC LIMIT 51\G
+*************************** 1. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: logging
+         type: index
+possible_keys: type_time,user_time,log_user_type_time
+          key: times
+      key_len: 16
+          ref: NULL
+         rows: 6705
+        Extra: Using where
+*************************** 2. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: user
+         type: eq_ref
+possible_keys: PRIMARY
+          key: PRIMARY
+      key_len: 4
+          ref: dewiki.logging.log_user
+         rows: 1
+        Extra: 
+*************************** 3. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: tag_summary
+         type: ref
+possible_keys: ts_log_id,tag_summary_log_id
+          key: ts_log_id
+      key_len: 5
+          ref: dewiki.logging.log_id
+         rows: 20172                   <-- often much larger
+        Extra: Using where
+3 rows in set (0.29 sec)
+
+The remaining problems are:
+
+- The queries are fast enough until one hits cold data leading a slave to bottleneck on disk. The buffer pool churn has a flow-on effect on other normally fast queries which become false positives in the slow log. Especially problematic when a crawler like MSNBOT triggers a spike of these.
+
+- The tag_summary table often has a relatively low cardinality for ts_log_id (many nulls, few ids).
+
+- Sometimes a slave logs multiple identical copies of a query (always a form filtered by log_user) at intervals of several seconds. Presumably someone refreshing a page that is too slow to respond.
+
+Possibilities:
+
+- Pull out only log_id,log_user first to reduce the impact of the filesort and grab user and tag data in follow-up batch query. If the query plan sitches to using Index Condition Pushdown (""Using index condition"" in explain), cold data is less of an issue as fewer table rows are hit and fewer pages read.
+
+- Limit the size of the dataset to be considered. By timestamp perhaps, last X months maybe. For heavier users only?
+
+- Improve the method of retrieving ts_tags using something other than tag_summary. Or remove it entirely.
+
+- Isolate these queries to specific slaves (like watchlist).",1384428099,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Comment 2 correct.,1381972117,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Was this removed together with other FORCE INDEX recently?,1381520218,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Similar:
+
+SELECT /* IndexPager::buildQueryInfo (contributions page unfiltered) AstroChemist */  rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,user_name,page_namespace,page_title,page_is_new,page_latest,page_is_redirect,page_len,ts_tags  FROM `revision` INNER JOIN `page` ON ((page_id = rev_page)) LEFT JOIN `user` ON ((rev_user != 0) AND (user_id = rev_user)) LEFT JOIN `user_groups` ON ((ug_user = rev_user) AND ug_group = 'bot') LEFT JOIN `tag_summary` ON ((ts_rev_id=rev_id)) INNER JOIN `change_tag` FORCE INDEX (change_tag_tag_id) ON ((ct_rev_id=rev_id))  WHERE (rev_user >19555425) AND (ug_group IS NULL) AND (page_namespace != '0') AND ((rev_deleted & 4) = 0) AND ct_tag = 'visualeditor' AND (rev_timestamp<'20140101000000')  ORDER BY rev_timestamp DESC LIMIT 601;
+
+With force: 10+ mins
+
+Without force: 8s",1379619643,PHID-USER-lxluxbieyr4tgfyp5jru,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"Attachment 1
+
+Visual Editor became quite unusable (possibly) after a recent update in Malayalam Wikipedia. There are several selection, editing and linking problems started to appear recently. Two such problems are described here.
+
+See the example below
+
+1. Copy the following text and paste it in a test page at Malayalam Wikipedia using conventional editor and save it. 
+ഈ ദുരന്തം ഐറിഷ് രാജ്യാതിർത്തി
+
+2. Edit the page using VE.
+
+3. Change the third word ""ഐറിഷ്"" to ""അയർലൻഡ്"". To do that, select the word ""ഐറിഷ്"" by double clicking on it and type the word അയർലൻഡ്.
+
+4. Now I want to create a wikilink for അയർലൻഡ്. For that, I used shift+ctrl+left arrow. Now, instead of selecting the entire word, A PORTION OF THE WORD WAS SELECTED. See the attachment 1. 
+
+5. Select the entire word അയർലൻഡ് using double clicking on it
+
+6. Press ctrl+k. Now instead of popping up a linking suggestion for the word അയർലൻഡ്, THE WORD DISAPPEARED AND LINKING SUGGESTION FOR A PART OF NEXT WORD POPS UP. See the attachment 2
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Linux
+**Platform**: PC
+
+**Attached**: {F11751}",1377824820,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-n4sh4scopfxwny7l26we,task_description,resolved
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"(In reply to comment #9)
+> When will this be deployed in ml.wikipedia?
+
+Assuming that VE is deployed according to the roadmap for MediaWiki: [[mw:MediaWiki_1.22/Roadmap]], September 19. (Sorry, I should have mentioned that in my previous comment :) )",1379335311,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"(In reply to comment #7)
+> vssun, on which wiki? The patch is only deployed at [[mw:|MediaWiki.org]]
+> right
+> now.
+
+Thank you. The bug is about Malayalam Wikipedia (already mentioned in description)
+
+When will this be deployed in ml.wikipedia?",1379333338,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"(In reply to comment #6)
+> Still facing all the problems mentioned at comment 1
+
+Please always provide clear and exact steps to reproduce (e.g. URL testcase).
+Resetting status as I assume that this is fixed on mediawiki.org.",1379322294,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"vssun, on which wiki? The patch is only deployed at [[mw:|MediaWiki.org]] right now.",1379314575,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,Still facing all the problems mentioned at comment 1,1379313962,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"Marking this as ""FIXED"" on the expectation that it's fixed - please re-open if you find that it is still occurring.",1378958943,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"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!",1378943178,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"(In reply to comment #2)
+> Sorry for the incorrect attachment links on the above comments. Please
+> correct it if somebody can.
+
+Sorry, links in comments can't be edited in Bugzilla. :-(",1377827166,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,Sorry for the incorrect attachment links on the above comments. Please correct it if somebody can.,1377825981,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"Attachment 2
+
+**Attached**: {F11752}",1377825109,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+Automatically switch from wikitext to HTML syntax in serializer when attributes were added to elements,"When editing a document that contains:
+
+* Foo
+* Bar
+* Baz
+
+Adding an attribute to one of the list items in VE doesn't roundtrip (they serialise back to * instead of forcing <ul><li>..</ul>, as it will have to).
+
+Right now VisualEditor never does this, but earlier today I was experimenting with this (the language inspector might need to do this to properly flip the directionality of an individual list item, wrapping the inner content is not an option as then the number would be on the wrong side).
+
+When trying to reproduce this I noticed that it also happens when creating a new document (e.g. there is no existing page, it has no reason to force ""*"" instead of ""<li>"" other than that being the preferred default for wikitext).
+
+
+http://parsoid.wmflabs.org/_html/:
+
+In:
+<div dir=""ltr"">
+<ul>
+<li>a
+<li lang=""he"" dir=""rtl"">b
+<li>c
+</ul>
+</div>
+
+Out:
+<div dir=""ltr"">
+
+* a
+* b
+* c
+
+</div>
+
+The only case where Parsoid kept the attributes is when not editing a document with wikitext, and not creating a new document, but when editing an existing document with ""<li>"" in wikitext already, it did roundtrip those.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68800",1377813060,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5dek6g5wc736qamv43s5,task_description,open
+Automatically switch from wikitext to HTML syntax in serializer when attributes were added to elements,"An option might be to use T230683's `<<< .... >>>` syntax to handle T242777, and T230658's `{{#attr}}` to handle this task.
+
+Right now you can't mix ""wikitext"" and ""HTML-ish"" syntax in the same list (ie, some items `*` and some items `<li>`, which means the serializer needs to go back and convert *all* of the items in the list into html-ish syntax when it finds an item which can't be represented without it (either due to newlines in the content or attributes on the tag).  We could make that work, but it would probably require either (a) backtracking and reserializing the list, which could be O(N^2) in the worst case (O(N) nested lists, where the final item in each requires going back and reserializing the list using html-ish syntax), or (b) lookahead in the serializer for problematic content, which again could be O(N^2) if done naively (O(N) nested lists, where each requires O(N) look ahead to the end).",1579033369,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-5dek6g5wc736qamv43s5,task_subcomment,NA
+Automatically switch from wikitext to HTML syntax in serializer when attributes were added to elements,"@esanders, @Catrope, @Jdforrester-WMF, Is this an use case that Parsoid should support in Q3 / Q4?",1422986235,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-5dek6g5wc736qamv43s5,task_subcomment,NA
+Automatically switch from wikitext to HTML syntax in serializer when attributes were added to elements,"Timo indicated on IRC that lists and list items will be first, but other elements will follow. We should try to use this first case to develop the general infrastructure.
+
+We will need to convert an entire list to HTML syntax if an attribute is set on either the list or any list item.
+
+Mixed templated / non-templated list items are discussed in bug 53368. We protect the entire list if any list item's bullets are template-generated. That means that we (thankfully!) won't have to consider that case here.",1377818147,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-5dek6g5wc736qamv43s5,task_subcomment,NA
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment","MyOnlyEye says, ""When I write long articles in VisualEditor the whole screen scolls - and the VisualEditor toolbar is scrolling upward and out of the screen. If I want to make a headline or instert a picture I'll have to scroll up to the top to reach the toolbar. I've tried it in the lastest edition of Firefox and Chrome in Win8 - on my own mediawiki with visualeditor and Wikipedia and Mediawiki....On every page that is longer than the screen - e.g. http://en.wikipedia.org/wiki/Electron?veaction=edit
+I've tested a bit (after I wrote the feedback) and it seems to be OK on my Win7 and Linux-box (chrome and firefox, both in 64-bit), but it's not working on Win8 (32-bit). Both the lastest 32-bit edition of Chrome and Firefox have the ""scrolling error"" on my Acer W510 Win8-laptop in desktop-mode (and in tile-mode :-)....I tried the electron-article and updated my own wiki (with git pull on mediawiki developer and visualeditor). I tried it in Firefox and Chrome (latest 32-bits editions)....I've installed a virtualbox with Win8 (32-bit, same as my Acer W510) and ran some wiki-pages with visualeditor in Chrome. No problem with the toolbar. So there seems to be two options left - 1) it's the intel screen driver (Intel HD 9.14.3.1102) or 2) it's how the browsers behave in a touch screen environment. My W510 has touch screen, the virtualbox Win8 hasn't....
+I've tested it on another Win8-machine (ASUS VivoBook S400 14"" HD touch) with different hardware than Acer W510 _but_ with a touch screen - and... the toolbox/-bar scrolled out of the screen. So my guess is that this is something that happens when the browser knows that the user can scroll the webpage with the fingers.""
+
+It is apparently not quite the same as https://bugzilla.wikimedia.org/show_bug.cgi?id=52504
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377802500,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-nkghehcsjvmpig3dnbgm,task_description,invalid
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment","**odin** wrote:
+
+Now working in the lastest Firefox v25.0 for Windows8. Still not working in latest Chrome.",1383167709,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nkghehcsjvmpig3dnbgm,task_subcomment,NA
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment","**odin** wrote:
+
+Also confirmed in Android 4.3 (with default Chrome browser) on Asus Nexus 7 (2012).",1379099403,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nkghehcsjvmpig3dnbgm,task_subcomment,NA
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment","**odin** wrote:
+
+I just testet the bug in Android 4.2.1 with Chrome (on a Samsung Galaxy S4) - and when I scroll, the toolbox moves out of the screen.",1379077160,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nkghehcsjvmpig3dnbgm,task_subcomment,NA
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment",This sounds bad for our impending work for mobile. :-(,1377835053,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nkghehcsjvmpig3dnbgm,task_subcomment,NA
+VisualEditor: nowiki tags thrown right after a template,"I am filing a related common problem we meet at it.wp.
+
+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.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377800880,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qoahpa6ud2jrgv76kigv,task_description,open
+VisualEditor: nowiki tags thrown right after a template,"Related Parsoid behavior (this is serialization of new content):
+-----------------------
+[subbu@earth lib] echo ""<table><tbody><tr><td>foo</td></tr></tbody></table> a"" | node parse --html2wt
+{|
+|foo
+|}
+<nowiki> </nowiki>a
+-----------------------
+
+The following is for existing content in wikitext
+-----------------------
+[subbu@earth lib] echo ""{|\n|a\n|} a"" | node parse --wt2wt
+{|
+|a
+|} a
+-----------------------
+
+So, Parsoid does not split the line after the table if it is old content, but does if it is new content and can introduce a <nowiki>  Since the report states that happens no matter what is edited on the page, my suspicion is that the HTML has a newline break after the <table> added by VE.  Requires further investigation that I cannot do right now, but hope this is good for starters. Adding others who might have time to investigate.",1377802050,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-qoahpa6ud2jrgv76kigv,task_subcomment,NA
+VisualEditor: Added templates in RTL wikis should float in appropriate direction,"Templates that are inserted to a page in RTL appear first floating on the right side, then only after save and re-edit they appear correctly.
+
+Replicate:
+1. Go to hewiki (or any other rtl wiki)
+2. Add a template - for instance {{עליות}} which is supposed to be floated left - yet it is inserted floating right.
+3. Save the page. Edit it again -- the template floats in the correct direction.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377798180,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-77lwknbtryzjh4peqeh4,task_description,resolved
+VisualEditor: Added templates in RTL wikis should float in appropriate direction,This is working for me. Feel free to re-open if this is still an issue.,1701813764,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-77lwknbtryzjh4peqeh4,task_subcomment,NA
+"VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages","**Author:** `p.selitskas`
+
+**Description:**
+Entries in Page settings / Languages don't have dir attributes for the link text. It leads to bidi issues for RTL languages.
+
+Reproducing:
+1. Go to an article with a langlink to Hebrew, for instance. Here's my favourite: [[en:August 3]].
+2. Open the VisualEditor.
+3. Go to Page settings / Languages and scroll down to 'he'.
+4. Link text reads as ""3 באוגוסט"", but it should read with ""3"" after Hebrew characters (reading left-to-right, of course; in the beginning of the string, if right-to-left).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377728640,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ozeftogat7b2642er6vn,task_description,resolved
+"VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages",Merged and will go out with wmf16 (from Thursday 5 September).,1377895476,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ozeftogat7b2642er6vn,task_subcomment,NA
+"VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages","Change 81589 merged by jenkins-bot:
+VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages
+
+https://gerrit.wikimedia.org/r/81589",1377887216,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ozeftogat7b2642er6vn,task_subcomment,NA
+"VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages","Change 81589 had a related patch set uploaded by Wizardist:
+VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages
+
+https://gerrit.wikimedia.org/r/81589",1377728877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ozeftogat7b2642er6vn,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","See numbers 49 and 50 in https://pl.wikipedia.org/w/index.php?title=Biurokracja&oldid=37367869 and https://pl.wikipedia.org/w/index.php?title=Biurokracja&oldid=37367869&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51289
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52300",1377708300,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-4zstjmvxiakrfapfim3n,task_description,resolved
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","Actually, on review I'm pretty sure that this is a duplicate of bug 50474.
+
+*** This bug has been marked as a duplicate of bug 50474 ***",1377823295,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue",at en.wp user:KWW wonders if this is the same issue as bug 52300?,1377814639,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","Looking again, it seems this is not the same as the earlier bug. In that case the references from the infobox didn't appear in the reflist at all. Now it seems that it is just the numbering that is wrong. At [[Ptyhon (programming language)]] for example, there are 10 references in the infobox, so the first reference in the lead is numbered 11. 
+
+Looking at in VE though the first reference in the lead (TIOBE Software Index (2012)) is numbered 1. In the reference list though TIOBE Software Index (2012) is numbered as 11 and reference 1 is the first one from the infobox.",1377801805,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","To clarify the first comment: if you look at the vedit view of the page I linked, you'll see that references 50 and 49 are both labelled ""49"". So, potentially we might be dealing with two distinct bugs here - renumbering because it's not factoring in different surfaces, and duplicate numbering.",1377796895,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue",References in infobox not populating the main references list and not being counted sounds a lot like bug 51289 which was marked fixed at the start of the month,1377775105,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","<< Entering Visual Editor mode renumbered the references on page Python_(programming_language) https://en.wikipedia.org/wiki/Python_(programming_language)?veaction=edit , so they don't match the references listed at the end of the article. Davipo 08:36, 29 August 2013 (UTC) >>
+It will ignore the numbers in the infobox, and start again from n.1 in the first line of the article - should be 11 instead. I find it just slightly confusing, since in the end you are still able to edit footnotes correctly. Thanks.",1377770276,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+VisualEditor: Transclusion editor should not allow parameters with unmet dependencies,"The transclusion editor should not allow (or at least should warn about) template parameters with unmet dependencies.
+
+For example in [[template:For]] parameter 4 has no effect unless parameter 3 is also specified, so the transclusion editor should not allow/warn about template 4 without an accompanying parameter 3. (parameter 3 is otherwise optional and can be present without parameter 4).
+
+In at least some cite templates, parameter author2 requires the existence of author1, etc. 
+
+I'm fairly sure that this functionality depends on bug 50407, which requests that TemplateData allows dependency relationships like this to be defined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377690300,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-f6pggcvz6dsrki4glrbf,task_description,open
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Redlinks right now always take you into wikitext editor, regardless of what editor is primary on your wiki.
+
+--------------------------
+**See Also**:
+{T54162}
+{T54281}",1377650040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_description,resolved
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Makes sense. I'll do that.,1455819228,PHID-USER-go2ym6ta2zn6ofdsrqnx,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#2039758, @Johan wrote:
+> Something like this:
+> 
+> ""In the future, clicking a red link will open the page in your primary editor. Today it will open it the wikitext editor. This will only work for wikis with [[<tvar|set>mw:Special:MyLanguage/VisualEditor/Single edit tab</>|single edit tab]].""
+> 
+> (I know the change is happening now, but unless it actually affects editors because it only works for wikis with the single edit tab, it's still a future change for them.)
+
+The wording looks good. I'd push this to next week, and talk about how it will (then) be live on huwiki and people can see it there.",1455815567,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Something like this:
+
+""In the future, clicking a red link will open the page in your primary editor. Today it will open it the wikitext editor. This will only work for wikis with [[<tvar|set>mw:Special:MyLanguage/VisualEditor/Single edit tab</>|single edit tab]].""
+
+(I know the change is happening now, but unless it actually affects editors because it only works for wikis with the single edit tab, it's still a future change for them.)",1455809932,PHID-USER-go2ym6ta2zn6ofdsrqnx,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Something like this:
+
+""In the future, clicking a red link will open the page in your primary editor. Today it will open it the wikitext editor. This will only work for wikis with [[<tvar|set>mw:Special:MyLanguage/VisualEditor/Single edit tab|single edit tab]].""
+
+(I know the change is happening now, but unless it actually affects editors because it only works for wikis with the single edit tab, it's still a future change for them.)",1455809914,PHID-USER-go2ym6ta2zn6ofdsrqnx,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","So does this affect any other wikis than the test wiki at the moment? Hungarian Wikipedia is supposed to get the single edit tab, but doesn't have it yet, right?",1455798338,PHID-USER-go2ym6ta2zn6ofdsrqnx,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",(Only fixed for Single Edit Tab wikis.),1455651854,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446269, @matmarex wrote:
+>>>! In T55441#1446171, @Ricordisamoa wrote:
+>>>>! In T55441#1446154, @Krenair wrote:
+>>> We'd like to have a single edit tab where the user can chose between VE and a wikitext source editor
+>> 
+>> https://meta.wikimedia.org/wiki/Wikiafication
+> 
+> This comment is at best unfair and at worst willful ignorance or trolling. Being able to switch between editors while editing has been requested repeatedly, and using the action=edit view for editors is the obvious choice, already made by others such as CodeEditor. It is the most obvious, most intuitive and best way to present two or more editors
+
+It proves that the essay is biased and Wikiafication can be good sometimes.",1436623626,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446955, @TTO wrote:
+> Many of the MW installations that have requested this appear to be corporate/internal wikis. Would you be willing to provide the feature for them, even if you do not enable it on WMF wikis?
+
+Yes, that's fine (though ideally we'd do so in a way that doesn't create technical debt in MediaWiki which we'd have to carry).",1436578387,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Many of the MW installations that have requested this appear to be corporate/internal wikis. Would you be willing to provide the feature for them, even if you do not enable it on WMF wikis?",1436578325,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446206, @Solstag wrote:
+> This bug is about making the default choice of editor consistent. For red links. It's that simple.
+
+I understand. The current situation is poor for the majority of people who click 'edit' rather than 'edit source' and get VE rather than WT, except when it comes to red links.
+
+However, just blindly changing these from WT to VE would be a bad move for a few reasons:
+
+* It's a pretty core disruptive change to a core part of how MediaWiki works, which means it would probably break a number of scripts, gadgets, bots and other tools that have been built over the past 15 years relying on this being a certain way.
+* It would take a long time to roll out in Wikimedia production, as this would be a breaking change to the read HTML with `href`s' targets being changed, meaning the benefit for IPs would take many weeks to be fully felt (and likely breaking other things).
+* It would replace the bad system (use WT, no choice) with another bad system (use VE, no choice), rather than a 'proper' system of user choice
+* It would be particularly disruptive for 'power editors', who would be forced to switch over to WT every time they clicked edit, likely leading them to opt-out of VE in huge numbers.
+* It would be inconsistent – for namespaces which are WT-only, like `MediaWiki:` or `Template:`, would it take you to WT anyway?
+* For users who can't use VE (//e.g.// no JS, something we can't fix server-side), it would strand them on the 'read' page, rather than take then to WT
+
+Consequently, I am not willing to make this change before we have a single edit tab that solves (or obviates) each of these issues.",1436558337,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446171, @Ricordisamoa wrote:
+>>>! In T55441#1446154, @Krenair wrote:
+>> We'd like to have a single edit tab where the user can chose between VE and a wikitext source editor
+> 
+> https://meta.wikimedia.org/wiki/Wikiafication
+
+This comment is at best unfair and at worst willful ignorance or trolling. Being able to switch between editors while editing has been requested repeatedly, and using the action=edit view for editors is the obvious choice, already made by others such as CodeEditor. It is the most obvious, most intuitive and best way to present two or more editors, and not ""additional and costly bloat to a site as an unsuccessful means of ""engaging visitors"" or ""building community"""", like that page states. ",1436557895,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Please, this bug is not about having a single edit tab, or choice, or wikiafication or whatever.
+
+This bug is about making the default choice of editor consistent. For red links. It's that simple.",1436555598,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446154, @Krenair wrote:
+> We'd like to have a single edit tab where the user can chose between VE and a wikitext source editor
+
+https://meta.wikimedia.org/wiki/Wikiafication",1436554570,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I'm not sure we want to use this hook for VE. We'd like to have a single edit tab (pointing to action=edit) where the user can chose between VE and a wikitext source editor instead, so this would be obsolete.",1436554102,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1433506, @Juandev wrote:
+> So, why it was told to me, we need a community consensus?! Dont tell me that it cannot be set differently to each project?!
+
+At the moment, it cannot, because the feature you are asking for doesn't even exist yet. That is the problem we are trying to solve with the patch linked above.
+
+Once that is dealt with, then we can potentially act upon the community consensus and enable the feature on that wiki, if the VE boffins agree that it is a good thing to do. ",1436266371,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1327857, @Krenair wrote:
+> When it happens, it'll happen on every wiki. Until then it can't be on any wiki...
+
+So, why it was told to me, we need a community consensus?! Dont tell me that it cannot be set differently to each project?!
+
+
+
+",1436264992,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1429220, @Nemo_bis wrote:
+> Red links are the single most important entry point for article editing after the edit tabs and section editing, so it makes sense to make them smarter/configurable.
+
+I've been wondering how are articles created. Is it red links from other articles? The red links that appears when search for a page that doesn't exist? Something else?",1436182556,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Indeed, this bug is not about action=edit but about what gets linked most prominently. Red links are the single most important entry point for article editing after the edit tabs and section editing, so it makes sense to make them smarter/configurable.
+
+Then of course there are many other links to handle later (think of inputbox and so on) but divide et impera applies.",1436180945,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","@Krenair I'm a little puzzled by your comment:
+
+>>! In T55441#1412564, @Krenair wrote:
+> Sorry, but this is not a thing. MediaWiki does not let you set default=wikitext vs. default=visualeditor. You get given one editor by MediaWiki for wikitext, and it's what gets shown at action=edit (the target of all of MediaWiki's red links). 
+
+Well, isn't that part of the point of this issue - to make redlinks configurable? Of course, T102398 would render that moot, but in the interim, I have uploaded new patch sets to https://gerrit.wikimedia.org/r/178817 that allow extensions to retarget redlinks.
+
+I don't expect WMF wikis to use this, but some third-party installations are interested in it (judging by posts at Support Desk over the past few months).",1436163446,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1408724, @Solstag wrote:
+> A project that has visual editor as default for
+
+Sorry, but this is not a thing. MediaWiki does not let you set default=wikitext vs. default=visualeditor. You get given one editor by MediaWiki for wikitext, and it's what gets shown at action=edit (the target of all of MediaWiki's red links). VE hacks itself in via veaction=edit, but this cannot be considered a default by any means.",1435631163,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1408724, @Solstag wrote:
+> A project that has visual editor as default for everybody, even unauthenticated users, should open red links with the visual editor.
+
+A gadget (enabled by default) which replaces `action=edit` with `veaction=edit` might be the easiest short-term solution - it gives the ability to opt out, and does not cause cache fragmentation.",1435614861,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Hi folks! Just in case the duplicate doesn't speak by itself, I see no reason why we don't have right now:
+
+A project that has visual editor as default for everybody, even unauthenticated users, should open red links with the visual editor.
+
+All other projects should wait until you sort out the mess with picking the right editor for each user.
+
+This is definitely not hard to implement, there's not even a new config involved.
+
+Cheers and thanks for looking into this.",1435534756,PHID-USER-wr7prgh3p37xrvbdr6w5,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1327857, @Krenair wrote:
+> When it happens, it'll happen on every wiki. Until then it can't be on any wiki...
+
+A lot of Wikimedia wikis have been happily using VisualEditor for over a year, and the wikitext editor being the default even for new editors is problematic for them. (It is somewhat ridiculous, for example, that [[ https://www.mediawiki.org/wiki/Extension:SandboxLink | SandboxLink ]], which is mainly meant to make the life of new editors easier, drops them into a wikitext editor.) I don't see what's wrong with providing a per-wiki option.",1434826324,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Updated title to reflect actual desired end result. The url structure is secondary and may actually change (see T54281).,1433993685,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","When it happens, it'll happen on every wiki. Until then it can't be on any wiki...",1433206467,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Could you enable this on cs.wv per community consensus: https://cs.wikiversity.org/wiki/Wikiverzita:Diskusn%C3%AD_prostor#Zalo.C5.BEen.C3.AD_a_editace_str.C3.A1nky_ve_VisualEditoru,1433206300,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Change 178817 restored by TTO:
+Consistent edit links
+
+Reason:
+Seems like a valuable change.
+
+[[https://gerrit.wikimedia.org/r/178817]]",1431085942,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","This option should (must?) be available for those who wish to use VE on their own MediaWiki installations. Currently, redlinks are a ""hole"" through which unsuspecting users can ""fall"" into the ""pipework"" of the wikitext editor.
+
+Most of the discussion here deals with the social aspects of the task, which doesn't seem hugely relevant here. The functionality would presumably live behind a $wg flag, and be switched off by default.",1431085917,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Change 178817 abandoned by Ricordisamoa:
+Consistent edit links
+
+Reason:
+There ain't no such thing as a solution for this.
+
+[[https://gerrit.wikimedia.org/r/178817]]",1429130863,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I do not plan to work on it before the discussion has an outcome (nor I have any personal interest in supporting VisualEditor at the moment), but the patch is up for anyone who wants to play with it.",1422491673,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Are you going to work on it more? I got the impression from the way you unassigned this that we shouldn't review the patch before discussing this further.,1422491216,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",@Krenair: should I abandon my patch then?,1422490645,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",This has to be discussed further.,1421814853,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#849854, @matmarex wrote:
+> What I meant is that a vocal group of English Wikipedia users hates VisualEditor's guts and would enjoy the new opportunity to spit on it. I hope this clarifies the issue. :)
+> 
+> VisualEditor is also still not quite compatible with some languages and some wikis' conventions, so this would regardless need to be behind a configuration option.
+
+I thought, they asked to switch it off at all. ",1421475541,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I support not making assumptions about the editor, but I think making action=edit point to VisualEditor would break lots of things.",1420725110,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I think the editor should initialise at a canonical url. Perhaps with a way to force a specific editor but the vast majority of urls should point to the edit page without making assumptions about what editor that is. This means when we switch the default, existing urls will work as expected.
+
+We already have two different editors for wikitext (classic toolbar and WikiEditor). Though they don't have a way to switch without changing user preferences right now, WikiEditor loads on the old edit page. I think from a user perspective, VisualEditor should be introduced the same way.
+
+action=edit:
+* Would load editor based on user preference. Default user preference being the site default. As with any user preference, this preference can be made immutable or hidden from the preferences page if we don't want it to be per-user.
+* Use `&editor=...` to force a specific editor. This is what can be used when applications need to interoperate. E.g. in gadgets needing wikitext. Or when VisualEditor submits data to the wikitext editor (though it may incorporate its own wikitext editor). And of course in links like ""Edit"" / ""Edit source"". And permalinks (VisualEditor may want to do a pushState to editor=ve once loaded via plain action=edit so that one can share permalinks).",1420722912,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","What I meant is that a vocal group of English Wikipedia users hates VisualEditor's guts and would enjoy the new opportunity to spit on it. I hope this clarifies the issue. :)
+
+VisualEditor is also still not quite compatible with some languages and some wikis' conventions, so this would regardless need to be behind a configuration option.",1418717375,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#840960, @matmarex wrote:
+> I am not sure of this change will be beneficial at this point, given that VE is currently still used by  minority of users. It might result in more people disabling VE entirely.
+
+Why do you think so? I have a reason, why I set up VE and I am disappointed it doesn not work for creating new pages. Who might be disappointed from using it on VE?
+
+",1418699501,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I reported this as a nead to create new page with VE. In this ligt there is a not logic message ""you follow the link to the page which does not exist"" Basically yes, but I had to do the step out of the page displayed with normal wikitext editing to the different one in VE. Once this bug removed, this can stay.",1418699317,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","One question is whether we want to just overwrite existing edit links, or to add a new one, for example in the [[ https://www.mediawiki.org/w/index.php?title=VisualEditor&action=info&uselang=en#Page_properties | page properties ]] section.
+In the first case, we probably don't want that to happen on WMF sites at all.",1418291385,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Thanks for the patch. I think we should look for a solution that neither requires a user preference nor a forced standard for all users. Can we initialize the interface in a way that reflects the user's previous choice (for the first time, it is whatever the wiki's default is)? Can this be done intuitively without going all the way to reorganizing tabs? Partially a #design question.",1418289610,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I am not sure of this change will be beneficial at this point, given that VE is currently still used by  minority of users. It might result in more people disabling VE entirely.",1418289058,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I am not sure of this change will be beneficial at this point, given that VE is currently still used by  minority of users. It might result in more people disabling VE entirely. Especially since it still doesn't support real section editing (T50429).",1418288995,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Change 178817 had a related patch set uploaded (by Ricordisamoa):
+Consistent edit links
+
+[[https://gerrit.wikimedia.org/r/178817]]
+
+#patch-for-review",1418211040,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Let's give it a try.,1418211003,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+VisualEditor: Pressing a modifier key (Ctrl/Alt/Shift/Cmd/etc.) when cursor is offscreen or under the toolbar causes the page to scroll up,"**Author:** `p.selitskas`
+
+**Description:**
+Reproducing:
+1. Open the VisualEditor
+2. Put the cursor in a place where ""Paragraph"" (or whatever else) disappears. (For example, into the ugly and unbearable empty line in pages with infobox at the very beginning.) The content editor must be kept active and cursor blinking.
+3. Scroll it down a bit.
+4. Press Ctrl, Alt, or Shift, or every possible combination of these
+5. See the content editor scroll up step by step (or as many steps per time as many keys are in combination.
+
+I can reproduce this in Chrome 29.0.1547.57 and Firefox 23.0.1 on Windows.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377634200,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oveveoihmpyqrm3ltjzu,task_description,resolved
+VisualEditor: Pressing a modifier key (Ctrl/Alt/Shift/Cmd/etc.) when cursor is offscreen or under the toolbar causes the page to scroll up,Seems to be fixed now.,1437759675,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-oveveoihmpyqrm3ltjzu,task_subcomment,NA
+VisualEditor: Pressing a modifier key (Ctrl/Alt/Shift/Cmd/etc.) when cursor is offscreen or under the toolbar causes the page to scroll up,"fwiw, this is still happening.",1383117125,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-oveveoihmpyqrm3ltjzu,task_subcomment,NA
+"VisualEditor: Toolbar icons - ""Transclusion"" (puzzle piece) alternatives or improvements","en.wp user Risker reports from an editathon that of the participants:
+""not a one of them understood what the ""puzzle piece"" was supposed to represent, and when shown, all of them still thought it was a poorly chosen icon.  Most had no suggestion as to an alternative, although two thought ""curly brackets"" would be a good idea.  I suspect that's because they'd seen curly brackets for templates when using wikitext.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51372",1377598380,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-wnl2ydoz2ca2h7xcsvtk,task_description,open
+"VisualEditor: Toolbar icons - ""Transclusion"" (puzzle piece) alternatives or improvements",Can we close this given we now show text in the menu?,1453915511,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wnl2ydoz2ca2h7xcsvtk,task_subcomment,NA
+"VisualEditor: Toolbar icons - ""Transclusion"" (puzzle piece) alternatives or improvements","(In reply to comment #0)
+> en.wp user Risker reports from an editathon that of the participants:
+> ""not a one of them understood what the ""puzzle piece"" was supposed to
+> represent, and when shown, all of them still thought it was a poorly chosen
+> icon.
+
+Yeah; we all hate it, and are using it because it's the least-bad option suggested so far (it's historically been the icon used in attempts at visual editors for MW since 2003).
+
+>  Most had no suggestion as to an alternative, although two thought
+> ""curly brackets"" would be a good idea.  I suspect that's because they'd seen
+> curly brackets for templates when using wikitext.""
+
+Indeed - we're trying to break the linkage with wikitext, and I don't think braces make for much of an increased level of obviousness.
+
+The new toolbar which allows buttons to self-describe if they're in a drop-down may help this significantly, but for now will keep this open.",1377831641,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wnl2ydoz2ca2h7xcsvtk,task_subcomment,NA
+"VisualEditor: Toolbar icons - ""Transclusion"" (puzzle piece) alternatives or improvements","**ypnypn9** wrote:
+
+How about just using the word ""Template""? Words are more obvious than even the best icons. (A disadvantage of this is that it would require a lot of translations, but this is not a huge problem.)",1377638244,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wnl2ydoz2ca2h7xcsvtk,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"This is probably an occurrence of an existing bug, but I couldn't find one that really fitted.
+
+In these edits, the table header was duplicated several times:
+
+https://fr.wikipedia.org/w/index.php?title=CM_Punk&diff=95906046&oldid=95898800
+https://fr.wikipedia.org/w/index.php?title=CM_Punk&diff=95848040&oldid=95838194
+https://fr.wikipedia.org/w/index.php?title=CM_Punk&diff=95778036&oldid=95766921
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377596700,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_description,resolved
+Broken wikitext inside a table leads to it and the table header being duplicated,"The rts look pretty reasonable to me these days. I'll assume whatever was causing the issue has cleared up.
+
+http://localhost:8000/_rt/frwiki/CM_Punk?oldid=95898800
+http://localhost:8000/_rt/frwiki/CM_Punk?oldid=95838194
+http://localhost:8000/_rt/frwiki/CM_Punk?oldid=95766921
+http://localhost:8000/_rt/frwiki/Utilisateur%3AElitre_%28WMF%29%2FProve_VE?oldid=100438786",1418097332,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"Yes, it is:
+https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve_VE&diff=100438830&oldid=100438786 .",1390237691,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,Is thist still an issue in production?,1386113968,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"Ya, I've responded to this here: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Multiplication_of_table_headers. 
+
+This general use case of fosterable content has been handled in Parsoid. Not sure why it is failing in production when I cannot reproduce it locally. To be investigated.",1380067514,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"Trying to work out what the cause of the bug is here; certainly, it's trying to operate on completely-broken wikitext, viz.:
+
+{| bgcolor=""#f7f0ff"" border=""1"" cellpadding=""2"" cellspacing=""0"" style=""font-size: 90%; border: gray solid 1px; border-collapse: collapse;""
+** '''[[Pro Wrestling Illustrated#Top 50 Females|Top 50 Females]]
+
+(!)
+
+This looks to have DSR issues as well (see the creation broken syntax with a single close-] alongside the partial wikitext non-DOM-sensicle duplication), and as the broken edits don't get a VE-check tag I'm assuming the DOM is clean from the VE end - moving to Parsoid.",1380067021,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"More of them, making a lot of damages.
+Any idea when someone will look at this bug, prioritize it, assign it and fix it ?
+
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=96858939&oldid=96858743
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=next&oldid=96858939
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=96801326&oldid=96761115
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=prev&oldid=96761115
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=96119241&oldid=96014996",1379873418,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+"VisualEditor: Allow multiple commands (""keyboard shortcuts"") per tool on the same platform","Right now the CommandRegistry only takes a single command that can be used as a keybinding for a tool on a given platform (i.e. Mac, PC, etc.); it's thus not possible to have two keyboard shortcuts for the same tool, such as Undo (where both Ctrl+Y and Ctrl+Shift+Z are commonly used).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377533460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j32rmxvcdit6df4qvtqi,task_description,resolved
+"VisualEditor: Allow multiple commands (""keyboard shortcuts"") per tool on the same platform","(In reply to comment #1)
+> For ""Undo"" read ""Redo"" in James' comment
+
+Err. Yes. :-)",1377535865,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j32rmxvcdit6df4qvtqi,task_subcomment,NA
+"VisualEditor: Allow multiple commands (""keyboard shortcuts"") per tool on the same platform","For ""Undo"" read ""Redo"" in James' comment",1377533902,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-j32rmxvcdit6df4qvtqi,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","VE allows to mark text as both superscripted and subscripted (<sup><sub>text</sub></sup> or the other way). That sounds like a bad idea; such text simply ends up being displayed in smaller font.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377465840,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_description,resolved
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Let's leave the bug as fixed in the original fix, not the recent minor breakage.",1405043173,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",Verified the fix in production,1405033980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Change 143756 merged by jenkins-bot:
+Follow-up: If717ef98 – Re-add subscript and superscript removes to DM nodes
+
+https://gerrit.wikimedia.org/r/143756",1404341575,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Change 143756 had a related patch set uploaded by Catrope:
+Follow-up: If717ef98 – Re-add subscript and superscript removes to DM nodes
+
+https://gerrit.wikimedia.org/r/143756",1404341432,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",I can't reproduce. Steps?,1404313005,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","This is happening again, the superscript and subscript both are getting applied at the same time.",1404239230,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",Verified the fix in betalabs,1393631391,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Change 114488 merged by jenkins-bot:
+Allow annotations to remove other annotations
+
+https://gerrit.wikimedia.org/r/114488",1393453702,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Yeah, that's what I meant. Thanks.",1392914022,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(In reply to Bartosz Dziewoński from comment #9)
+> (In reply to James Forrester from comment #8)
+> > (a) what should happen in VE when the user attempts this
+> 
+> Text should be either super- or subscripted, not both.
+> 
+> Nesting superscripts in subscripts, subscripts in superscripts,
+> subscripts in subscripts and superscripts in superscripts
+> should be impossible, just like it's impossible to nest links in other
+> links. Currently only the last two are impossible.
+
+This works for me. Re-wording bug for clarity – is this acceptable to you?",1392913756,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Change 114488 had a related patch set uploaded by Esanders:
+Allow annotations to remove other annotations
+
+https://gerrit.wikimedia.org/r/114488",1392913587,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(In reply to Ed Sanders from comment #10)
+> I don't think we need to alienate such nested content though, in the same
+> way we don't alienate a double bold tag (if someone used one). As long as
+> the user doesn't try to change the sub/superscripting, the annotations will
+> remain untouched.
+
+I'm willing to trust you on implementation details :)",1392911441,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","I agree that the sub/superscript tool should clear any other sub/superscript annotations present. As pointed out you can't do a double superscript, so clearly our goal is not to let you create any complex hierarchy you want, that's for <math>.
+
+I don't think we need to alienate such nested content though, in the same way we don't alienate a double bold tag (if someone used one). As long as the user doesn't try to change the sub/superscripting, the annotations will remain untouched.",1392911200,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(In reply to James Forrester from comment #8)
+> (a) what should happen in VE when the user attempts this
+
+Text should be either super- or subscripted, not both.
+
+Nesting superscripts in subscripts, subscripts in superscripts,
+subscripts in subscripts and superscripts in superscripts
+should be impossible, just like it's impossible to nest links in other
+links. Currently only the last two are impossible.
+
+> (b) what should happen in VE when the page already has this
+
+The same thing that happens with all other unsupported input: it
+should be alienated and left alone.
+
+> (c) what should be changed in MediaWiki's PST to stop this happening
+> in future(?).
+
+Nothing. I suppose there are very rare use cases where this could be
+wanted, we should just keep supporting them for backwards-compatibility.
+
+In fact, the only things that I see in existing articles are currently
+impossible in VE – you can't nest superscripts to produce, say,
+10<sup>10<sup>26</sup></sup> (10^{10^26}) used in [[pl:Oś czasu dalekiej
+przyszłości]]. Arguably this should just use <math/> tags though.",1392900216,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Wikitext lets you do this too. Do you think we should just silently kill all examples of this in the database? :-)
+
+Closing again unless you can suggest (a) what should happen in VE when the user attempts this, (b) what should happen in VE when the page already has this, and (c) what should be changed in MediaWiki's PST to stop this happening in future(?).",1392749738,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","A dupe was just filed, this is not just me. Reopening.",1384111164,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",*** Bug 56795 has been marked as a duplicate of this bug. ***,1384111137,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","As input, sure. But as output, HTML lets you do lots of things that VE doesn't.",1377476809,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(In reply to comment #2)
+> Do other text editors permit that? I don't know of any that would.
+> 
+> (Or in other words, this is not fitting users' expectations.)
+
+Well, HTML lets you do this, which means VE needs to support it on the input side at the very least.",1377474493,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(Or in other words, this is not fitting users' expectations.)",1377467182,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",Do other text editors permit that? I don't know of any that would.,1377467085,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","I don't see how this is a bug? Yes, it's bad, in the same way that setting text's colour to be white, or putting an image inside another image's caption, but that doesn't mean we should stop people doing it…
+
+Generally, appropriate use of the software is a social thing, not a software thing. Willing to be convinced otherwise, but for now I'll mark this as a WONTFIX.",1377466817,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+ULS support needed in VisualEditor's dialog boxes,"We need ULS support in dialog boxes-
+
+1) Template dialog boxes - adding existing template for setting paratmeters
+2) Image dialog box
+3) Adding or editing references
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377447360,PHID-USER-qpuuryo2o37amdlkb5gk,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_description,resolved
+ULS support needed in VisualEditor's dialog boxes,Fixed with https://gerrit.wikimedia.org/r/#/c/264577/,1454774965,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_subcomment,NA
+ULS support needed in VisualEditor's dialog boxes,"Pavanaja: Can you elaborate on what you mean by ""We need ULS support in dialog boxes"". I think you mean ""input method support"", but I'd like to be sure.
+
+Additionally, if you could please add the following:
+1. Numbered steps to reproduce.
+2. Observed behavior
+3. Expected behavior
+
+This would allow us to unambiguously understand what you expect, and work towards resolving the issue you experience.",1378119977,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_subcomment,NA
+ULS support needed in VisualEditor's dialog boxes,"(In reply to comment #0)
+> We need ULS support in dialog boxes-
+> 
+> 1) Template dialog boxes - adding existing template for setting paratmeters
+> 2) Image dialog box
+> 3) Adding or editing references
+
+Is this something that is done on the VisualEditor side, or inside ULS? I'm pretty sure that there was no change made in VE for the enabling of jquery.IME inside the main VisualEditor surface…
+
+(Please move back if I'm wrong.)",1377823487,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_subcomment,NA
+ULS support needed in VisualEditor's dialog boxes,"[New feature => setting the ""Severity"" field to ""enhancement"". 
+Feel free to do so yourself when filing a report.]
+
+(In reply to comment #0)
+> We need ULS support in dialog boxes-
+> 
+> 1) Template dialog boxes - adding existing template for setting paratmeters
+> 2) Image dialog box
+> 3) Adding or editing references
+
+Please please elaborate what that means, for example steps to reproduce, current outcome, and expected outcome. Also see https://www.mediawiki.org/wiki/How_to_report_a_bug",1377460860,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_subcomment,NA
+VisualEditor: Can't return to save dialog after reviewing null edit,"reported on en.wp by Atethnekos:
+
+""So I put a space and then a backspace. Go to save, review changes to check and make sure it is a null edit, then it goes to this ""processing"" dialogue but then it shows ""Could not start the review because your revision matches the latest version of this page."" So then I press the little back link on the dialogue, but it just goes back to the processing dialogue. If the page is small, the processing is really quick, so before I can even press back again, it goes back to the ""Could not start"" warning message. Even if I do manage to press the back a second time quickly, it will only stay at the save dialogue for a split second and then again bring me to the warning message, although then pressing back does take me to the save dialogue securely. FF 23.0.1 Win7""
+
+I've confirmed this in Firefox 23.0 on Linux.
+The issue is with the < link only. Clicking the ^ does return you to the editing screen as expected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377426420,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_description,resolved
+VisualEditor: Can't return to save dialog after reviewing null edit,"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.",1381187081,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_subcomment,NA
+VisualEditor: Can't return to save dialog after reviewing null edit,"Change 81876 merged by jenkins-bot:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1381186923,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_subcomment,NA
+VisualEditor: Can't return to save dialog after reviewing null edit,"Change 81876 had a related patch set uploaded by Jforrester:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1378325644,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_subcomment,NA
+VisualEditor: Can't return to save dialog after reviewing null edit,*** Bug 53314 has been marked as a duplicate of this bug. ***,1377426954,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_subcomment,NA
+"VisualEditor: When reversing a transaction, create a new transaction rather than reusing the old one","Rather than passing around boolean parameters called 'reversed' all over the place, we should use each transaction only once, and implement a function that creates a new transaction that's the reverse of an existing transaction.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377192420,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-chjb2m7r6pmqmr457wgg,task_description,resolved
+"VisualEditor: When reversing a transaction, create a new transaction rather than reusing the old one",This was done ages ago in I3050c5430be4a12510f22e20853560b92acebb67,1394478857,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-chjb2m7r6pmqmr457wgg,task_subcomment,NA
+"VisualEditor: When reversing a transaction, create a new transaction rather than reusing the old one","But note that the code currently uses the fact that the commit and rollback transaction are the same in order to update the 'applied' field.  So the rollback transaction should still contain a pointer to the original transaction, and when it is committed both should be marked with 'applied=false' (which indicates that we can skip over these entries in the completeHistory).",1377652795,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-chjb2m7r6pmqmr457wgg,task_subcomment,NA
+VisualEditor: Undo/redo doesn't go through dm.Surface.change() code path,"dm.Surface.undo() and .redo() just call documentModel.rollback() / .commit() directly, without going through all the other stuff in .change() . Presumably this other stuff is useful, so we should figure out if bypassing it causes bugs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377191640,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-va4nmthl5rer6qeyil6y,task_description,resolved
+VisualEditor: Undo/redo doesn't go through dm.Surface.change() code path,"Change 88728 merged by jenkins-bot:
+Implement ve.dm.Surface.prototype.undo() and redo() in terms of change()
+
+https://gerrit.wikimedia.org/r/88728",1382735134,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-va4nmthl5rer6qeyil6y,task_subcomment,NA
+VisualEditor: Undo/redo doesn't go through dm.Surface.change() code path,"Change 88728 had a related patch set uploaded by Catrope:
+Implement ve.dm.Surface.prototype.undo() and redo() in terms of change()
+
+https://gerrit.wikimedia.org/r/88728",1381326083,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-va4nmthl5rer6qeyil6y,task_subcomment,NA
+VisualEditor: Undo/redo doesn't go through dm.Surface.change() code path,In theory Surface.change() should also have a corresponding Surface.unchange() method (or a 'reversed' parameter).,1377191752,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-va4nmthl5rer6qeyil6y,task_subcomment,NA
+"VisualEditor: When editing a section, don't wait for loading to be complete before scrolling to the section","When loading VisualEditor from a section edit link, the editor opens at that position on the page. However, as the TOC is not displayed in edit mode (bug 49224) the content is effectively rendered higher up so a later section in the article moves into the view (from a users point of view this is perceived as scrolling to a random point). 
+
+The view point does move to the new location of the desired section as the final step of loading, but only if the user has not scrolled at any point while waiting. 
+
+If they have attempted to find the section themselves while VE is loading then either (a) the view point subsequently doesn't move when loading completes, or (b) moves by the amount it would have done if the user had not scrolled (meaning it now points at a different point to desired). I have not worked out how to specifically induce one behaviour or indeed what causes either.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T51224}
+{T52206}
+{T54577}",1377187440,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-evkujyihqmirmqqeozmk,task_description,duplicate
+"VisualEditor: When editing a section, don't wait for loading to be complete before scrolling to the section","Should this be closed in favor of T52206?
+Also see T87556.",1423683149,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-evkujyihqmirmqqeozmk,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"I clicked to edit a section of a long article, and when I tried to file a bug, it looked like the screen just went dark - I couldn't immediately see a dialog box. It turned out to be because the feedback dialog was overlayed above the section I was editing, which was way, way down the page, and the browser didn't scroll to that part of the page when I pressed the button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377115140,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-5cuwqt62enm5hymwly75,task_description,declined
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"Unfortunately closing this Phabricator task as no further information has been provided.
+
+@Greenrd: After you have provided the information asked for and if this still happens, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks!",1590842330,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"Ahm, I'm sorry (obviously requires VE to be enabled to see those section heading links).
+Tried on http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Arrr0.5320366523148922&veaction=edit&vesection=2 but still the ""Submit feedback"" dialog is centered. 
+Still cannot reproduce with Chrome 41 or Firefox 36.",1425554338,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"@Greenrd: Sorry that this task has not received feedback earlier, and thank you for reporting this!
+
+> I clicked to edit a section of a long article
+
+Where did you click exactly? Link to that long article is also very welcome. :)
+
+> and when I tried to file a bug, it looked like the screen just went dark - I couldn't immediately see a dialog box. It turned out to be because the feedback dialog was overlayed above the section I was editing
+
+Does this refer to the ""Leave Feedback / Submit Feedback"" dialog available from the ""Help"" (question mark) button in VE's toolbar?
+
+I cannot reproduce in Firefox 36 and Chrome 41 trying with https://en.wikipedia.org/wiki/Hamburg?veaction=edit - is this still a problem?
+Setting task status to ""Stalled"" for the time being...",1425554071,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"(In reply to comment #1)
+> Which browser is this about?
+
+Chromium Version 27.0.1453.93 Built from source for Fedora release 18",1377160124,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"Thanks for taking the time to report this!
+
+Which browser is this about?",1377119887,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Annotating an inline alien breaks node protection,"1. Create a document with:
+   Foo <cite>Alien</cite> Bar
+2. Select all and bold
+
+Results
+3. 'Alien' is bolded, despite being protected (questionable)
+4. The shield has disappeared.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377085200,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-tyb65vkuz46fcurmj72h,task_description,resolved
+VisualEditor: Annotating an inline alien breaks node protection,"This seems to behave correctly these days.
+
+3. It is still bolded, but I think that's usually the right behavior. (We could change this by using `blacklistedAnnotationTypes`, which we use now mostly to disallow applying link annotations over nodes that already contain links.)
+4. This doesn't happen, the ""shield"" is still present and catches clicks. (I believe that's the same thing that we call ""highlights"" now, the striped overlay thing?) {F31513637}",1579117639,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tyb65vkuz46fcurmj72h,task_subcomment,NA
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Both ve.dm.ModelRegistry.js and its test file have references to  /^mw:/ . Any code relating to mw should be in modules/ve-mw/
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377084540,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hia733wv6lu2vvjmm2xv,task_description,resolved
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Change 116487 merged by jenkins-bot:
+Update VE core submodule to master (74be717)
+
+https://gerrit.wikimedia.org/r/116487",1393875313,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hia733wv6lu2vvjmm2xv,task_subcomment,NA
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Change 116485 merged by jenkins-bot:
+Remove MW-specific config and genericise tests in ModelRegistry
+
+https://gerrit.wikimedia.org/r/116485",1393874576,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hia733wv6lu2vvjmm2xv,task_subcomment,NA
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Change 116487 had a related patch set uploaded by Esanders:
+MW configuration for modelRegistry
+
+https://gerrit.wikimedia.org/r/116487",1393858493,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hia733wv6lu2vvjmm2xv,task_subcomment,NA
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Change 116485 had a related patch set uploaded by Esanders:
+Remove MW-specific config and genericise tests in ModelRegistry
+
+https://gerrit.wikimedia.org/r/116485",1393858486,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hia733wv6lu2vvjmm2xv,task_subcomment,NA
+Clean up single vs. multi-part data-mw,"We currently use { target: {}, params: {} } for single-transclusion content, and {parts: [{template:{target: {}, params: {}, i: 0}}]} for multi-part transclusions and extensions. This creates special cases and makes it necessary to know all keys to convert the single-transclusion format into the parts bit.
+
+The missing namespacing also makes it harder than necessary to add additional information to data-mw.
+
+To clean this up, we should consider moving to always using an array format like this:
+
+parts: [{""@type"":""mw:Transclusion"", target: {}, params: {}}]
+
+The change to always use an array is already supported by VisualEditor. Flattening the nested object and using a JSON-LDish @type key makes the parts structure more regular and easier to extend. It also moves it closer to the RDFa names. Both us and VE can support both formats as an input for a while to avoid caching issues, but should start by only emitting the new format.
+
+See also:
+http://json-ld.org/playground/index.html -- some example JSON-LD
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377042960,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-iwz7tbppv2hen4mzt3ny,task_description,open
+Clean up single vs. multi-part data-mw,"The other changes in this ticket will require co-ordination with VE since it will break existing code.
+
+This will also require the cached HTML versioning to be implemented to prevent weird editing errors between when parsoid is deployed and varnish caches or cleared.  Alternatively, VE and Parsoid serializer would have to handle old and new formats of data-mw temporarily.",1377558860,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-iwz7tbppv2hen4mzt3ny,task_subcomment,NA
+Clean up single vs. multi-part data-mw,"Change 81143 merged by jenkins-bot:
+(Bug 53135) Step 1: Always use parts array for transclusion data-mw
+
+https://gerrit.wikimedia.org/r/81143",1377558504,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iwz7tbppv2hen4mzt3ny,task_subcomment,NA
+Clean up single vs. multi-part data-mw,"Change 81143 had a related patch set uploaded by Subramanya Sastry:
+(Bug 53135) Step 1: Always use parts array for transclusion data-mw
+
+https://gerrit.wikimedia.org/r/81143",1377557762,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iwz7tbppv2hen4mzt3ny,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**Author:** `p.selitskas`
+
+**Description:**
+Please create an icon with bold cyrillic ""Т"" for [be] and [be-tarask].
+
+In Belarusian locales ([be] and [be-tarask]), the Bold icon is now read as ""Тл"" which may be interpreted as ""Тлусты"" (fat), but in fact it makes the selected text not fat, but bold (""Тоўсты""). :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377007260,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7uqnmenedinwiui6wz4s,task_description,resolved
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,This should now be fixed in production; sorry for the delay.,1379364856,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84361 merged by jenkins-bot:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84361",1379357724,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84361 had a related patch set uploaded by Reedy:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84361",1379357517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84095 merged by jenkins-bot:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84095",1379355814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84095 had a related patch set uploaded by Catrope:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84095",1379023642,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,You're welcome. It does.,1379019052,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #17)
+> Argh, sorry about this mess; we'll back-port the fix.
+
+Thanks for swift resolving! Does it mean the 'fix fix' will be deployed soon out of general deployment schedule?",1379015228,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Argh, sorry about this mess; we'll back-port the fix.",1379011818,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84027 merged by jenkins-bot:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84027",1379011697,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84027 had a related patch set uploaded by Esanders:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84027",1379011477,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,This is the offending commit: https://gerrit.wikimedia.org/r/#/c/81522/,1379011117,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #12)
+> Looks like Trevor's toolbar rewrite didn't merge cleanly with my commits and
+> they were partially undone.
+
+Obviously. I was not aware of the rewrite and first thought that the patch was merged but hasn't appeared in the codebase (black magic).",1379008274,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,Looks like Trevor's toolbar rewrite didn't merge cleanly with my commits and they were partially undone.,1379007349,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #10)
+> (In reply to comment #9)
+> > te-el shouldn't exist as it was replaced with just te, so maybe this is a
+> > caching issue?
+> 
+> https://bits.wikimedia.org/static-1.22wmf16/extensions/VisualEditor/modules/
+> ve/ui/styles/images/icons/bold-cyrl-te-el.svg
+> 
+> 404 (PNG as well). And I'm not counting the absent CSS class that should
+> display this icon. Did the deployment come smoothly? :)
+
+Oh, I'm sorry, I checked the wrong file. Anyway, JS adds the wrong class.",1379006964,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #9)
+> te-el shouldn't exist as it was replaced with just te, so maybe this is a
+> caching issue?
+
+https://bits.wikimedia.org/static-1.22wmf16/extensions/VisualEditor/modules/ve/ui/styles/images/icons/bold-cyrl-te-el.svg
+
+404 (PNG as well). And I'm not counting the absent CSS class that should display this icon. Did the deployment come smoothly? :)",1379006874,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"te-el shouldn't exist as it was replaced with just te, so maybe this is a caching issue?",1379006381,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+Class .ve-ui-icon-bold-cyrl-te-el was not created/generated, and now there is empty space instead of a ""Bold"" icon. Reopening the bug.",1379006056,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,Now merged and will go out in about an hour.,1377035770,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,Also related: https://gerrit.wikimedia.org/r/80126,1377029951,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"The be-tarask icons are now changed (and this version of the software will go out in a few hours' time); keeping the bug open for making it work with both be and be-tarask, as part of a general fall-back mode.",1377022483,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 80049 merged by jenkins-bot:
+Change be-tarask to use Te instead of Te-El for bold
+
+https://gerrit.wikimedia.org/r/80049",1377022412,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #1)
+> We don't currently support [be], just [be-tarask]. Can you confirm that we
+> should use the same icons for [be] (bold: T, italic: K)?
+
+Yes, I confirm this suggestion.",1377017841,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 80049 had a related patch set uploaded by Esanders:
+Change be-tarask to use Te instead of Te-El for bold
+
+https://gerrit.wikimedia.org/r/80049",1377017622,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"We don't currently support [be], just [be-tarask]. Can you confirm that we should use the same icons for [be] (bold: T, italic: K)?",1377017564,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","It first happened to the user who was trying to add a wikilink to a large page,  https://en.wikipedia.org/wiki/List_of_Criterion_Collection_DVD_and_Blu-ray_releases; he got the error while in VE so he made that edit with the classic editor later.
+He then copied the contents of the page to a sandbox - https://en.wikipedia.org/wiki/User:Marc_Kupper/sandbox2 -  for further testing and these are his findings:
+
+<< It took 74 seconds to load the page in VE, I made the change, save-page, give a reason (wikilink - testing VE), save-page again. After 1:45 (105 seconds) I got ""Error: Unknown error"" in the lower part of VE's edit-summary box. The save-page button is grayed out.
+I don't think the actual edit I did matters. If someone wants to reproduce using my sandbox then the edit was in the last paragraph of the lead. Where it says ""...Essential Art House, Eclipse, and Merchant Ivory Collection..."" I changed ""Eclipse"" to [[Eclipse (DVD)|Eclipse]] by double-clicking on Eclipse to select, control-K to bring up the insert/edit link box, appending "" (d"" to the link-to value, click ""Eclipse (DVD)"" in the list of offerings, and then press <enter> a couple of times to close out the box. I suspect you can make any change you want. --Marc Kupper|talk 22:06, 19 August 2013 (UTC)
+
+
+After documenting how I did the edit I tried the save again and again got the error. It happened 1:44 (104 seconds) after clicking save. I suspect the 105 seconds above is simply because I was a bit slow reacting as this time I was waiting for the error right around the 1:45 mark. --Marc Kupper|talk 22:06, 19 August 2013 (UTC)
+I then did the following tests
+I replaced all non-alphabetic characters with the letter ""x"" and can edit the page with VE. It appears the issue is with something in the page content, possibly combined with the page size.
+I removed all 'ref' tags. Saving from VE still fails after 1:44
+I removed most of the templates transcluded on the page. Saving with VE worked and took 1:17. However, I had intended to just add ""xxx"" in the middle of a word. VE also stripped a table in another part of the article of wikitext. (https://en.wikipedia.org/w/index.php?title=User%3AMarc_Kupper%2Fsandbox2&diff=569295763&oldid=569295507 ) --Marc Kupper|talk 23:16, 19 August 2013 (UTC)
+
+I don't have time to debug this further at present - particularly as we now have two VE issues. The next step is to revert back to 22:48, 19 August 2013 and to then see if I can narrow it down from there. --Marc Kupper|talk 23:11, 19 August 2013 (UTC) >>
+
+I tested on the first version of the sandbox as well, it took me almost 75 secs as well to load the page, I wikilinked a word and then hit Save - it took me 2min 15sec to get the error message while actually the edit was saved.  Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70726
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51636",1377006180,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_description,open
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)",">>! In T55093#572665, @GWicke wrote:
+> The issue does not seem to be specific to any particular page. At https://en.wikipedia.org/wiki/OpenOffice.org?veaction=edit for example an initial
+> load of 215k turns into a 3.6mb POST.
+> 
+> Possible remedies:
+> * use gzip compression for the POST request body
+> * use multipart/form-data POST encoding instead of application/x-ww-form-urlencoded to avoid percent encoding overhead
+> * send HTML as a separate POST variable without JSON wrapper to avoid JSON escaping, in particular of quotes
+
+Where are you seeing this? VE already does all of these things, which I just confirmed at https://en.wikipedia.org/wiki/OpenOffice.org?veaction=edit in Chrome. The POST that occurs when the (first) save button is pressed has a `multipart/form-data` POST body with gzipped content (the value of the `html` parameter starts with `rawdeflate,7H1rd9tGkuj3+RW9`). The POST that occurs when the second save button is pressed only sends a `cachekey` value, no large blob of HTML.
+
+You should not have been able to trigger a multi-megabyte POST upload. Perhaps you observed a cachekey miss and there's a bug where the POST body is not compressed in that case?",1440110032,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)",">>! In T55093#572665, @GWicke wrote:
+> Some additional info about the POST size issue on save:
+> 
+> To check the POST request size, I looked at the Content-Size header in the request headers once that completed (request to api.php started when opening the save dialog).
+> 
+> The issue does not seem to be specific to any particular page. At https://en.wikipedia.org/wiki/OpenOffice.org?veaction=edit for example an initial
+> load of 215k turns into a 3.6mb POST.
+
+You're saying that the page downloads gzipped at a weight of 215k and then when the browser goes to re-upload it has a weight of 3.6mb uncompressed? That sounds pretty bad to me.",1440108913,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)",Strike the last point about JSON- the HTML is already sent as a plain query parameter without JSON wrapper.,1388954245,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","Some additional info about the POST size issue on save:
+
+To check the POST request size, I looked at the Content-Size header in the request headers once that completed (request to api.php started when opening the save dialog).
+
+The issue does not seem to be specific to any particular page. At https://en.wikipedia.org/wiki/OpenOffice.org?veaction=edit for example an initial
+load of 215k turns into a 3.6mb POST.
+
+Possible remedies:
+* use gzip compression for the POST request body
+* use multipart/form-data POST encoding instead of application/x-ww-form-urlencoded to avoid percent encoding overhead
+* send HTML as a separate POST variable without JSON wrapper to avoid JSON escaping, in particular of quotes",1388703828,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","At
+https://en.wikipedia.org/wiki/List_of_Criterion_Collection_DVD_and_Blu-ray_releases?veaction=edit,
+I am seeing a 5.6mb upload on preview. This takes 47 seconds to transfer
+using my DSL connection. Connections with slower upload speeds would do
+worse, and possibly time out. The POST processing and response then
+takes 7.9 seconds according to the Chromium network console.
+
+For comparison, the HTML downloaded on VE open is 238kb in size and
+takes 3 seconds to load. Total load time until VE is ready is around 36
+seconds, again using Chromium.
+
+In my experience Firefox's client-side processing would be a bit slower.",1388698096,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","A user is reporting this problem at
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=588582743#Reliable_but_not_powerful",1388536381,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","Ok, so comment #3 should read that in one occasion,
+David got the message, the edit was not saved.
+Editing the same article, I didn't get the message, and my edit was saved.
+In other cases, it is possible to get the message and having the edit saved.",1380198153,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","I got ""Error: unknown error"", but the error saved anyway, on this edit: https://en.wikipedia.org/w/index.php?title=OpenOffice.org&curid=68227&diff=574513723&oldid=574510970 - first time I've ever had the error and it did in fact save.
+
+I'm now wondering if having the error and the edit not being saved is the same bug as having the error and the edit being saved.",1380197582,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","A fr.wp user reports he was confused when he got this message, since the edit was saved anyway.",1380125629,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","David Gerard and I had different experiences about this bug.
+He tried to edit https://en.wikipedia.org/wiki/Neuro-linguistic_programming , while I basically copy/pasted that article in my sandbox https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=573778358 and then attempted to change it.
+After 100 secs or so, VE managed to save our edits, but he got the error message, while I didn't. HTH.",1379794141,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","Here http://en.wikipedia.org/w/index.php?title=Fairfield%2C_Iowa&diff=569923054&oldid=569069756 is another case of the error message being thrown after an actually successful edit.
+The user wonders: "" it would be useful to know the current confidence limits around page length and the ability to edit same. Is it dependent upon local environment (i.e. PC configuration and memory allocated to browser)? Or is there a server side known performance limit?"".
+Thanks.",1377340698,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","(User specs, Vista - FF23 - Vector.)",1377007870,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"Screenshot
+
+Blocked IP addresses can see the VisualEditor, use it, and are presented with the error in the screenshot when saving.
+
+Reporting distinctly from bug 52004 because the error message and use case are both somewhat different.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52004
+
+**Attached**: {F11450}",1376861280,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-r3aliipwenpyb4simxc3,task_description,resolved
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"As with the normal local block bug, I'm going to mark this as fixed. We don't block the user from using VE, but there is now a notice warning them when they open VE.
+
+It would be difficult to get all the useful info into some smaller alert() message or similar. Though after thinking about it a bit more we could perhaps use a small VE dialog or something, I am open to suggestions of course - but perhaps that would be better to put in a more general ""not able to edit page due to protection/block/etc. dialog error"" as this patch simply brings global blocks into line with normal blocks, protection etc.",1398210636,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-r3aliipwenpyb4simxc3,task_subcomment,NA
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"Change 127840 merged by jenkins-bot:
+Show notice if user is globally blocked
+
+https://gerrit.wikimedia.org/r/127840",1398207749,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r3aliipwenpyb4simxc3,task_subcomment,NA
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"That error message that you do get on saving is also a bug of it's own, patched in Gerrit change 127835",1398126343,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-r3aliipwenpyb4simxc3,task_subcomment,NA
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"Change 127840 had a related patch set uploaded by Alex Monk:
+Show notice if user is globally blocked
+
+https://gerrit.wikimedia.org/r/127840",1398126310,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r3aliipwenpyb4simxc3,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer","The thermometer is important, as it explains why a radically modified document would give me an empty ""review changes"" box.
+
+Separate bugs: the thermometer never stops spinning, and my changes for review never appear--maybe Parsoid is gagging.  And, is that UI javascript running without a setTimeout?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1376813460,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-h7psvvdxqq5nurzgtxts,task_description,declined
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer","We can't reproduce this now, so closing as WORKSFORME.",1392062928,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer",I don't see a thermometer. :|,1391916090,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer","Sorry.
+
+* Edit a page, making changes
+* Click ""Save page"".  Save dialog pops down, and thermometer is spinning.
+* Click ""Review changes"" before the thermometer stops.
+The save dialog collapses down to a single line, which contains only the ""Review changes"" button, a left arrow button, and an up button.  This is strange.  The thermometer is gone.  There is no explanation of why i am presented with this damaged dialog.
+
+Apparently, with my broken VE, the loading/render/whatever the thermometer represents never finishes.  Which made it very easy to reproduce this other bug.",1376956217,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer","Trying to parse this. Is this:
+
+1. 'VisualEditor: Clicking ""Review changes"" mid-save causes the save dialog to disappear, which takes the save progress animation thermometer'
+
+… or
+
+2. 'VisualEditor: Clicking ""Review changes"" mid-save causes the save dialog to collapse but stay present, and also the save progress animation thermometer stays but stops animating'
+
+… or something else?",1376953643,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer",How does a thermometer spin?,1376814507,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**Author:** `jamesjoshualim`
+
+**Description:**
+Hi, everyone.  Yesterday, we had a meetup here in Manila, and I discussed with two Tagalog Wikipedia editors (including a fellow bureaucrat) about the creation of a new interface language for Tagalog in a bid to resolve long-standing differences over how the interface should be translated.  We agreed on a compromise solution, where we would accommodate Taglish (code-switched Tagalog and English) as a new interface language called ""Tagalog (informal)"" for the Tagalog-language projects, similar to how there is an interface language for formal German (de-formal).
+
+We decided that this new interface language will become the default interface language for all anonymous and new users on the Tagalog Wikipedia, in order to attract new editors who may be confused by the formal language used for the current Tagalog interface.  The current interface will be opt-in for those who want to use the interface as it currently is, and users will have the ability to select their preferred language using the Universal Language Selector which will only have Tagalog, Tagalog (informal) and English as the options.  All other languages may still be selected through the preferences.
+
+If this is possible to do, I'd love to see this come to fruition, and I hope to hear from all of you soon.  Thanks! :)
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1376723820,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tn3a37o3zgibya4bkm32,task_description,stalled
+Creation of tl-informal as a new interface language,"Or even better: https://www.mediawiki.org/wiki/Internationalisation_wishlist_2017#Better_support_for_formal_and_informal_variants
+
+This assumes that it is only wanted for interface, and that differences are not that big.",1511791485,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"Because language converter would need to cater to exceptions, the better way to do this is probably just open up a language and then only translate those that are different and then let the other terms fallback to Tagalog just like how zh_HK<>zh-Hant have been handled.
+
+That is provided that if a consensus are to be reached.",1511459800,PHID-USER-yba5kkq4bvwironiorlq,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,It might be possible to implement informal variants using LanguageConverter; see T33015#3183625,1492196403,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"This likely should be discussed *within* the community in order to reach consensus and support, however http://tl.wikipedia.org/wiki/WP:KAPE seems pretty inactive. Is there a better place?",1398135439,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jojit_fb** wrote:
+
+One more thing, why is it the localization project of the Mozilla Tagalog interface has no problems with retaining the technical terms untranslatable?  We can follow their example.",1398133896,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jojit_fb** wrote:
+
+(In reply to Josh Lim from comment #4)
+> (In reply to Joseph Ballesteros from comment #3)
+> > As a veteran editor in the Tagalog Wikipedia, I disagree with this.  I think
+> > it's redundant and I am for only one interface language for Tagalog.  I
+> > suggest that this should be discussed first with more editors.
+> 
+> It is not redundant when language issues are as divisive as they are on the
+> Tagalog Wikipedia.  Short of forcing everyone to abide by one standard
+> (which will not happen, given persistent conflicts between purists,
+> moderates and progressives/universalists) or creating two different
+> Wikipedias for Tagalog and Filipino, this is the best solution that can be
+> conceived.
+> 
+> (Also, I posted a discussion on this on both the Tagalog Wikipedia Facebook
+> group and the Kapihan months ago.)
+
+We cannot accommodate everyone.  We have to always look at what the majority of readers of the Tagalog Wikimedia projects understand.  They don't understand what is kasaputan, lambat-lambat and what have you. I realize the need to translate the interface after conducting editing workshops across the Philippines.  Most people in the workshops don't understand what is ""lumagda."" They understand the term ""login"" instead. 
+
+I bet that even some purists will laugh at the phrase ""Wala ka pa bang kuwenta?""  Do you even realize that in normal conversation the phrase may be translated as ""Are you still a useless person?"" instead of ""Don't have an account""?  I bet also that those so called purists also speak unpurely in normal conversation.  
+
+I believe it's still redundant and will add another burden to a handful of volunteers just to accommodate the principles of a few people.
+
+Another thing, it's not necessarily informal or Taglish when you use borrowed foreign words in a phrase or sentence.  There are words (especially technical terms) that are really untranslatable.  Forcing the translation will result to lots of misinterpretation just like with the term ""kuwenta.""  Thus, tl-informal is a misnomer and will just add to the confusion.
+
+I haven't seen a discussion in the WP:KAPE (or the Kapihan in the Tagalog Wikipedia) about this.  You are aware that I don't have a Facebook account and if you have posted that in Facebook, I haven't read it.  Instead of Facebook (where not all people who are involved in the projects are there), I recommend that you start a new section at WP:KAPE and discuss this further.  Please don't reply me here.",1398132909,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jamesjoshualim** wrote:
+
+(In reply to Joseph Ballesteros from comment #3)
+> As a veteran editor in the Tagalog Wikipedia, I disagree with this.  I think
+> it's redundant and I am for only one interface language for Tagalog.  I
+> suggest that this should be discussed first with more editors.
+
+It is not redundant when language issues are as divisive as they are on the Tagalog Wikipedia.  Short of forcing everyone to abide by one standard (which will not happen, given persistent conflicts between purists, moderates and progressives/universalists) or creating two different Wikipedias for Tagalog and Filipino, this is the best solution that can be conceived.
+
+(Also, I posted a discussion on this on both the Tagalog Wikipedia Facebook group and the Kapihan months ago.)",1398091189,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jojit_fb** wrote:
+
+As a veteran editor in the Tagalog Wikipedia, I disagree with this.  I think it's redundant and I am for only one interface language for Tagalog.  I suggest that this should be discussed first with more editors.",1398073332,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jamesjoshualim** wrote:
+
+(In reply to comment #1)
+> Is this asking for:
+> 
+> 1) Creating a new interface language, tl-informal, in TranslateWiki.net
+> 2) Creating a new interface language, tl-informal, in MW core
+> 3) Creating a new interface language, tl-informal, in production
+
+Just these first three.  For now, we're very undecided on pursuing the fourth option, as we have not yet agreed on having Taglish content on the Tagalog Wikipedia.  For now, we only agreed on having a new interface language, and we will get to the issue of content languages when we get there.",1378878251,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"Is this asking for:
+
+1) Creating a new interface language, tl-informal, in TranslateWiki.net
+2) Creating a new interface language, tl-informal, in MW core
+3) Creating a new interface language, tl-informal, in production
+4) Creating a new content language in MW core, adding to tlwiki as a variant
+5) Creating a new content language in MW core, adding to a new wiki (tl-inf-wiki)?
+
+I think this is 1, 2, 3 and 4 but not 5.
+
+Note that adding variants to a wiki is do-able but makes for a sucky experience in both editing and creating wikitext, and means that tlwiki wouldn't be possible as a release target for VisualEditor for at least some time whilst we wait for building out support in VisualEditor and Parsoid.",1378834373,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"**Author:** `swalling`
+
+**Description:**
+Hidden VE postedit confirmation
+
+If you edit successfully via wikitext, we delay loading the GettingStarted toolbar until after the post-edit confirmation disappears. We should do the same for the new style of postedit confirmation from VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11351}",1376715240,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-osskcs5pzqf76ce4lpyj,task_description,resolved
+GettingStarted toolbar overlaps with VE post edit confirmation,"Change 112880 merged by jenkins-bot:
+Delay showing the task toolbar after VisualEditor edit
+
+https://gerrit.wikimedia.org/r/112880",1392360585,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"Thanks, James.  The change on our side is https://gerrit.wikimedia.org/r/112880.",1392263311,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"The VE patch here has been merged and will be deployed in the train tomorrow (in wmf14); not sure if this achieves the fix desired, so just setting to ""NEW"" instead.",1392254220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"Change 112880 had a related patch set uploaded by Phuedx:
+Delay showing the task toolbar after Visual Editor edit
+
+https://gerrit.wikimedia.org/r/112880",1392205844,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"Change 112879 had a related patch set uploaded by Phuedx:
+Include edit status in the ve.deactivationComplete event
+
+https://gerrit.wikimedia.org/r/112879",1392205631,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+Refactor sanitizer to work on the DOM too,"Currently we always serialize to wikitext and re-parse that to HTML, which runs the sanitizer on the token stream to ensure that our final HTML does not cause bad things to happen.
+
+Soon both us and the Flow team want to store HTML from the VisualEditor directly without first serializing to wikitext. This means that we need to perform the sanitization on the HTML instead of the token stream. For performance, sanitizing on the way in would be preferable. We should however support re-sanitization when new issues were discovered. This could potentially be coupled with the versioning discussed in bug 52937. A new sanitizer could bump the version number, and the upgrade path would then run the new sanitizer on old HTML (and probably update the storage with the newly sanitized version).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376677680,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-zls4w4oon3y5sp6y4rot,task_description,open
+Refactor sanitizer to work on the DOM too,"Note that tokens are equivalent to SAX events. This suggests the following option for hooking up the current sanitizer to process a DOM:
+
+- Traverse the input DOM, emit SAX events
+- feed SAX events through the sanitizer
+- feed the resulting tokens / SAX events back to a HTML / XML DOM tree builder",1498752154,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-zls4w4oon3y5sp6y4rot,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"**Author:** `swalling`
+
+**Description:**
+Screenshot at 1024x768
+
+Very happy to see that VE is now using the same post-edit styling as wikitext! This is a big win for usability, since it is fixed position and so on.
+
+I did find one suboptimal fact though... Since the text of the message includes the page title, it is very variable width, depending on the page title length and the browser width. 
+
+One of the UX goals for this notification is to have new users notice it, but for it to eventually fade out of your attention as you become used to it. Since the page title produces very different widths as you edit different pages, this calls a lot more attention to the notification even if you've edit thousands of times. 
+
+My recommendation would be to match what's in the wikitext version, ""Your edit was saved."" since we A/B tested it and we know it meets the goals I mentioned above. Another good solution is simply removing the page title, so that the VE version says, ""Your changes have been saved."" That seems functionally the same, though I think using edit is good for consistency with the tab names etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11185}",1376526420,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3fcobyguspmbsv62uzbp,task_description,resolved
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Change 130968 merged by jenkins-bot:
+Switch to use MediaWiki's built-in messages for post-edit notifications
+
+https://gerrit.wikimedia.org/r/130968",1398983834,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Change 130968 had a related patch set uploaded by Alex Monk:
+Switch to use MediaWiki's built-in messages for post-edit notifications
+
+https://gerrit.wikimedia.org/r/130968",1398977566,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Change 127480 merged by jenkins-bot:
+Expand core post edit functionality to match VE
+
+https://gerrit.wikimedia.org/r/127480",1398976145,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),Now just needs VE to use the same function.,1398975938,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Change 127480 had a related patch set uploaded by Alex Monk:
+Expand core post edit functionality to match VE
+
+https://gerrit.wikimedia.org/r/127480",1398011806,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Current VE messages:
+
+    ""visualeditor-notification-created"": ""\""$1\"" has been created."",
+    ""visualeditor-notification-restored"": ""\""$1\"" has been restored."",
+    ""visualeditor-notification-saved"": ""Your changes to \""$1\"" have been saved."",
+
+Current MW core message:
+
+    'postedit-confirmation'            => 'Your edit was saved.',
+
+We should:
+
+1. Expand MW core to cater to all three states (create, restore, save):
+
+** Create: ""The page has been created.""
+** Restore: ""The page has been restored.""
+** Saved: ""Your edit was saved.""
+
+2. Not use different messages in VE – instead, use the core ones.
+
+Rather than create two bugs, let's just use this one?",1393377054,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: <references /> empty in edit mode,"The <references /> section is empty in edit mode, see URL.
+
+Other examples:
+
+https://de.wikipedia.org/wiki/Joachim_Wiesner
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Bahnhof_K%C3%B6ln_Eifeltor",1376480280,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-clul26iiuspnnu6ubobc,task_description,resolved
+VisualEditor: <references /> empty in edit mode,"Yeah, was already fixed. Great!",1378992675,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-clul26iiuspnnu6ubobc,task_subcomment,NA
+VisualEditor: <references /> empty in edit mode,"Hi Raimond,
+in both articles I can correctly see the contents of the Einzelnachweise sections.
+(Maybe this is a duplicate and the bug was already fixed?)",1378988604,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-clul26iiuspnnu6ubobc,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-searchoptions
+
+The ""Advanced options"" section of the ""Search"" tab in MediaWiki currently looks like this:
+
+---
+Advanced options
+
+[ ] Search in all namespaces
+
+Search in these namespaces by default:
+[ ] (Main)
+[ ] Talk
+[ ] User
+[ ] User talk
+[ ] Project
+[ ] Project talk
+[ ] File
+[ ] File talk
+[ ] MediaWiki
+[ ] MediaWiki talk
+[ ] Template
+[ ] Template talk
+[ ] Help
+[ ] Help talk
+[ ] Category
+[ ] Category talk
+[ ] Thread
+[ ] Thread talk
+[ ] Summary
+[ ] Summary talk
+[ ] Manual
+[ ] Manual talk
+[ ] Extension
+[ ] Extension talk
+[ ] API
+[ ] API talk
+[ ] Skin
+[ ] Skin talk
+[ ] Module
+[ ] Module talk
+[ ] Translations
+[ ] Translations talk
+[ ] VisualEditor
+[ ] VisualEditor talk
+---
+
+This list looks silly and excessive. While {T39878} has requested a layout change, I think we need to reconsider how this list is implemented.
+
+What about adding a checkbox to [[Special:Search]]'s advanced search section that looks something like this:
+
+[ ] Use these namespaces as my default
+
+This would de-duplicate the namespace listing (between Special:Preferences and Special:Search) and would allow the search user preference to be set more easily from the search interface itself.
+
+Rather than using Special:Preferences and having heavy user interface exposure, any custom search namespace preferences could be ""hidden"" user preferences. That is, they'll still be stored if they don't match the site-wide default, but they'll not clutter up Special:Preferences.
+
+--------------------------
+**See Also**:
+{T50615}",1376420940,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ueuakppu4zprla5jwywo,task_description,resolved
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Change 250271 merged by jenkins-bot:
+Remove search preferences from Special:Preferences JavaScript
+
+[[https://gerrit.wikimedia.org/r/250271]]",1446331757,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Change 250271 had a related patch set uploaded (by saper):
+Remove search preferences from Special:Preferences JavaScript
+
+[[https://gerrit.wikimedia.org/r/250271]]
+",1446322753,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Not really. As far as I understand the current search options are handled perfectly by the  [[http://git.wikimedia.org/blob/mediawiki%2Fcore.git/0158312d4bc3de9c15064a12a73b4bf57580e45e/resources%2Fsrc%2Fmediawiki.special%2Fmediawiki.special.search.js|mediawiki.special.search.js]] ResourceLoader module, while I intend to remove this from [[http://git.wikimedia.org/blob/mediawiki%2Fcore.git/0158312d4bc3de9c15064a12a73b4bf57580e45e/resources%2Fsrc%2Fmediawiki.special%2Fmediawiki.special.preferences.js#L284|mediawiki.special.preferences.js]] in https://gerrit.wikimedia.org/r/#/c/247728/. Probably this is just a leftover from this change.",1445517570,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","> I have found that we still have JavaScript code attaching to #mw-htmlform-advancedsearchoptions and #mw-input-wpsearcheverything. I understand this can be safely removed?
+
+Do you mean the All | None buttons inserted via JavaScript?",1445449896,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","One question:
+
+In https://gerrit.wikimedia.org/r/#/c/247728 I have found that we still have JavaScript code attaching to 
+`#mw-htmlform-advancedsearchoptions` and `#mw-input-wpsearcheverything`. I understand this can be safely removed?
+
+",1445420606,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",,1445420618,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",,1445420596,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Isarra from comment #27)
+> May also want a separate page of 'all settings' or 'advanced settings' for a
+> lot of them (it could also appear collapsed or something by default - the
+> point is while this is often not the stuff folks will necessarily be after,
+> it should be there somewhere in case they are), sort of like the extra
+> 'config' heap you see in firefox and whatnot, but hopefully somewhat easier
+> to find and use.
+
+Is there an open bug report about this? I wouldn't oppose a gated (behind a checkbox, perhaps) advanced user preferences tab. Safari does this as well, I believe, with a preferences checkbox that enables a ""Developer"" drop-down menu. Similar-ish idea.",1402265111,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Created attachment 15597
+Advanced search tab in mediawiki.org as of  	1.24wmf8
+
+**Attached**: {F11964}",1402261771,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #52)
+> My complaint has ""never"" been about any checkbox, but the removal of
+> Preferences.
+
+Are you able to offer another tab of Special:Preferences and other 35 checkboxes (in the case of en.wiki) to sacrifice instead?
+Preferences have been in a process of cutting for some time now and there are some rather extreme proposals around where your time would perhaps be better spent: https://www.mediawiki.org/wiki/Requests_for_comment/Redesign_user_preferences
+
+The path I'm following is the one of least resistance for the biggest result, you'll see that I'm reducing your future pain. :)",1402261544,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","My complaint has ""never"" been about any checkbox, but the removal of Preferences.",1402252214,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",So much drama about a single checkbox… get me out of here.,1402251490,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","No, I won't sit down, shut up and enjoy the ride.
+
+Really, most other places require consensus and consultation for change. I believe that Erik himself said that in edits relating to Flow. Something along the lines of 
+
+<quote>... We do strive to communicate, solve problems real users have, and resolve conflicts, especially if there are major points of contention. What are the material issues with the deploy at this time?</quote>
+
+So you have
+* major points of contention
+* no evidence that this fix actually a major point of contention
+* communication in a newsletter that points here, but you are not prepared to listen or discuss
+* no attempt to resolve a conflict
+* a merged change that is predicted to take place where no consultation has taken place
+* an opportunity to address matters raised prior to a deployment
+
+Have I missed something from that little list?
+
+Seems more than a technical fix. It appears to be a change planned to be implemented and you are not allowing broader discussion, or the base challenge to your assumptions. The points have been raised, and yet you forge ahead with your decision without an attempt at consensus, or some conciliation. And the history of bugs is that they are discussed in situ, not fobbed off somewhere else where you can ignore them in all their glory.
+
+I would think that it would actually be incumbent on you, those bringing the change forward to mediawiki, to propose and discuss that merged change. But no, instead we hide behind the ""technical"" barrier. Then expect others to go somewhere and complain ""I don't like it."" Grow up. The mature adult thing is for me to bring concerns here, to have them reasonably listened to, and to see if we can have a compromise. Seems that the mature approach is not suitable.
+
+If you want that change, you take it out and propose it and defend it. You have identified where it should be discussed, so I look forward to seeing it there. That is basically what I said at the beginning.
+
+If I don't see it there, then I feel that I am justified in reopening this bug until there is what I consider some reasonable conversation about this bug, and means to explore the matters raised.",1402251279,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #48)
+
+This bug is technically fixed: Advanced options preferences are now handled on Special:Search itself, which is the topic of this bug, so please stop reopening it. Also, a ""resolved"" status doesn't prevent you from commenting. If you detect flaws on the implementation, feel free to open a *new* bug describing the problems of this implementation (see [1]).
+
+I'd suggest you to raise your concerns in a mailing list (mediawiki-l seems to be the the best one for your concerns) [2]. Your message will be received by more people that can share their point of view about this, while your messages on this bug report are being received by the same developers that were involved in it. Feel free to put here a link to the discussion on the mailing list if you decide to start a discussion there.
+
+----
+
+[1] https://www.mediawiki.org/wiki/How_to_report_a_bug
+[2] https://www.mediawiki.org/wiki/Mailing_lists",1402249236,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I am sorry, that is a typical dismissive response, and pretty unhelpful.  I don't see the issues raised addresses by the bugzilla.
+
+BTW no one made you the decision maker, and as it is your code I would think a little less CoI, and some more communication would be preferable.",1402245055,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Quiddity from comment #40)
+> I think the problem with the new version, is the physical distance, or
+> dis-connection, of the checkbox from the search button... 
+
+Split to bug 66342.
+
+(In reply to billinghurst from comment #46)
+> I am wondering whether the proponents of the change have had the ability to
+> review suggestions
+
+Yes.",1402240628,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I am wondering whether the proponents of the change have had the ability to review suggestions made by people who are not in favour of the holistic change and may be able to suggest a compromise position.
+
+I have reopened this bug as I do not think that it should be considered fixed in light of this extra opinion.",1402239071,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+(In reply to MZMcBride from comment #43)
+
+> My gut feeling is that the real, underlying issue here is that you, me, and
+> others want global (wikifarm-wide) user preferences. 
+
+Speaking only for myself, I usually modify my search based on my involvement with the specific wiki. My search on a project I'm involved with and editing regularly usually needs the project and often the user namespaces. Ones I'm only occasionally editing need help and project namespaces. The defaults work fine on projects where I'm only a reader. It is a workflow issue.",1401810675,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+> It was 50/50 that you were going to say that. The other option was ""if it ain't > broke don't fix it"". Both are useless clichés. 
+
+Mmm, actually the third option was ""change for the sake of change"". They are clichés because they are common, valid issues. And you have not addressed the substance of the comment.
+
+I would suggest your response - highly defensive and dismissive - is itself a cliché of ""Dev knows best"", except I also know the reason it's a cliché is because it's often true. I'm with Quiddity, Isarra, and sDrewth: let's figure out a both-and solution, because it does not need to be either-or.",1401808846,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #37)
+> Nobody has argued about sensible defaults, nor the ability for communities
+> to be able to adjust and modify. I don't see how that introduction is
+> relevant.
+
+Amgine asked, ""Do we really want every special page to be creating and maintaining its own interface for user preferences?"" I was responding by noting that the goal is having a clean, easy-to-use user interface that uses sensible defaults. The goal is not a foolish consistency.
+
+> In fact if you follow that logic, we are now cluttering up a search page
+> with an option that is going to be used rarely or not at all, and maybe by a
+> small subset of people ...  Making visible an option that is probably used
+> zero times by most user, and maybe once or two by a small number of users.
+> That is perverse.
+
+Well, not quite. :-)  Rather than having this feature (the ability to customize search preferences) take up an entire Special:Preferences tab, it's now confined to a single checkbox. This seems proportionate and reasonable to me. If the feature were more important, it might make sense to give it more prominence, but I (personally) don't think it's very important.
+
+> I have no specific issue with an improvement or option at Special:Search, my
+> issue is that Preferences = Preferences and I expect to be able to go there
+> and to be able to set my preferences for search.
+
+My gut feeling is that the real, underlying issue here is that you, me, and others want global (wikifarm-wide) user preferences. In a similar vein to what I wrote in comment 35, as a user, if you're visiting Special:Preferences often, we're doing something wrong. You should only need to visit that page maybe once a year, but it sounds as though you and a few others visit it weekly or daily. (Which is not a criticism of power-users, to be clear, just a workflow observation.) I think we should focus on figuring out how to make it so that (power-)users don't need to visit Special:Preferences on every wiki in a wikifarm.",1401800527,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Quiddity from bug 52817 comment #40)
+> Searching for help documentation is HELL unless we add the Wikipedia: ,
+> Help: , and Template: namespaces to our default search. For the first few
+> years as a new editor, I was constantly searching those namespaces for tools
+> and guides. (Note that the Template: and Category: namespaces aren't
+> included in the ""Help and Project pages"" output)
+
+I guess this is an answer to:
+
+(In reply to MZMcBride from bug 52817 comment #35)
+> If many users are customizing their search settings, we're doing something
+> wrong.
+
+Split to bug 66066.",1401788398,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Quiddity from comment #40)
+> I'm surprised that we don't already have a link to
+> [[Special:Preferences#mw-prefsection-searchoptions]] anywhere at
+> [[Special:Search]] (advanced tab or otherwise)! How did we miss that, for so
+> long?!  Forest, trees.
+
+That's a very good point, and I've just made it happen on en.wp.",1401787806,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I fall right in the middle of this disagreement. Here's some notes, and an idea.
+
+There are good reasons to have the search-option-preferences in both locations (eg. easier-discoverability for newcomers, familiarity for oldtimers), 
+and there are good reasons to centralize/unduplicate at a single location (with Special:Search->Advanced being the reasonable contender because the options-list *has* to appear there).
+
+We do need easy-discoverability for newcomers. 
+Searching for help documentation is HELL unless we add the Wikipedia: , Help: , and Template: namespaces to our default search. For the first few years as a new editor, I was constantly searching those namespaces for tools and guides. (Note that the Template: and Category: namespaces aren't included in the ""Help and Project pages"" output)
+
+I'm surprised that we don't already have a link to [[Special:Preferences#mw-prefsection-searchoptions]] anywhere at [[Special:Search]] (advanced tab or otherwise)! How did we miss that, for so long?!  Forest, trees.
+
+I do also prefer the simple process for ""Save"" at Special:Preferences. It's not perfect (see {T57966}), but it's fairly intuitive. 
+The new system isn't intuitive. (It makes sense once explained, but an explanation is needed...)
+I think the problem with the new version, is the physical distance, or dis-connection, of the checkbox from the search button... 
+
+
+So, 2 fuzzy/rough suggestions:
+
+A) Add a new Blue ""Save selection as my default, and Search"" button, at the advanced-search tab, instead of the new ""Remember selection for future searches"" checkbox line. 
+
+B) leave the ""Search"" tab at Special:Preferences, but 
+B.1) just link to Special:Search->Advanced from within it.   
+B.2) Or, when clicked, have it open Special:Search->Advanced in a new tab/window.   (New tab, because the user might have other unsaved preference-changes, so we can't change the current page. (cf. {T57966}))  
+Either of these would solve the issues of discoverability and change-aversion.  Yes, it'll still leave an annoyingly almost-empty tab, but it's *way* better than the current/old layout, ie. comment #0
+
+--
+
+All 4 links, for your quick comparison:
+https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-searchoptions
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced",1448489786,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I fall right in the middle of this disagreement. Here's some notes, and an idea.
+
+There are good reasons to have the search-option-preferences in both locations (eg. easier-discoverability for newcomers, familiarity for oldtimers), 
+and there are good reasons to centralize/unduplicate at a single location (with Special:Search->Advanced being the reasonable contender because the options-list *has* to appear there).
+
+We do need easy-discoverability for newcomers. 
+Searching for help documentation is HELL unless we add the Wikipedia: , Help: , and Template: namespaces to our default search. For the first few years as a new editor, I was constantly searching those namespaces for tools and guides. (Note that the Template: and Category: namespaces aren't included in the ""Help and Project pages"" output)
+
+I'm surprised that we don't already have a link to [[Special:Preferences#mw-prefsection-searchoptions]] anywhere at [[Special:Search]] (advanced tab or otherwise)! How did we miss that, for so long?!  Forest, trees.
+
+I do also prefer the simple process for ""Save"" at Special:Preferences. It's not perfect (see bug 55966), but it's fairly intuitive. 
+The new system isn't intuitive. (It makes sense once explained, but an explanation is needed...)
+I think the problem with the new version, is the physical distance, or dis-connection, of the checkbox from the search button... 
+
+
+So, 2 fuzzy/rough suggestions:
+
+A) Add a new Blue ""Save selection as my default, and Search"" button, at the advanced-search tab, instead of the new ""Remember selection for future searches"" checkbox line. 
+
+B) leave the ""Search"" tab at Special:Preferences, but 
+B.1) just link to Special:Search->Advanced from within it.   
+B.2) Or, when clicked, have it open Special:Search->Advanced in a new tab/window.   (New tab, because the user might have other unsaved preference-changes, so we can't change the current page. (cf. bug 55966))  
+Either of these would solve the issues of discoverability and change-aversion.  Yes, it'll still leave an annoyingly almost-empty tab, but it's *way* better than the current/old layout, ie. comment #0
+
+--
+
+All 4 links, for your quick comparison:
+https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-searchoptions
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced",1401786703,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Amgine from comment #36)
+> This sounds so much like a solution looking for a problem.
+
+It was 50/50 that you were going to say that. The other option was ""if it ain't broke don't fix it"". Both are useless clichés. 
+
+Your comments are dripping with ""me, me, me"" privilege-based assumptions. Luckily, MediaWiki development is not based around avoiding advanced users having to have the minor inconvenience of learning a small interface change.",1401783456,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #37)
+> my
+> issue is that Preferences = Preferences
+
+Too bad this assumption is incorrect. We have plenty of preferences which have never been controlled by Special:Preferences, look https://www.mediawiki.org/w/api.php?action=query&meta=userinfo&uiprop=options&format=jsonfm again.
+Not to speak of all the preferences which are not even stored in the database, but instead on cookies or URL parameters (hence bookmarks at best).",1401778605,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to MZMcBride from comment #35)
+> (In reply to Amgine from comment #21)
+> > Sucks as UX. Do we really want every special page to be creating and
+> > maintaining its own interface for user preferences?
+> 
+> We want sensible defaults and intuitive, easy-to-use interfaces. For most
+> users, there shouldn't be a need to customize the default search settings.
+> If many users are customizing their search settings, we're doing something
+> wrong. For the few users who want to customize their search preferences,
+> there's now a checkbox in the same place as search. This seems like a good
+> thing to me.
+
+Nobody has argued about sensible defaults, nor the ability for communities to be able to adjust and modify. I don't see how that introduction is relevant.
+ 
+> Because there's now an additional checkbox that controls per-user search
+> preferences, we can de-duplicate the listing at Special:Preferences, which
+> makes for a cleaner user preferences interface (increased signal, decreased
+> noise). This also seems like a good thing to me.
+
+In fact if you follow that logic, we are now cluttering up a search page with an option that is going to be used rarely or not at all, and maybe by a small subset of people ...  Making visible an option that is probably used zero times by most user, and maybe once or two by a small number of users. That is perverse.
+
+> Perhaps a pointer from Special:Preferences to Special:Search would be
+> helpful, but I'm not sure it's needed and I'm not sure where it would
+> appropriately go.
+
+Or it could be '''at''' the search page that it says something the lines of ""Save this criteria to be your default"" and have a link to Special:Preferences.
+
+I have no specific issue with an improvement or option at Special:Search, my issue is that Preferences = Preferences and I expect to be able to go there and to be able to set my preferences for search.",1401778330,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+Would those 'few users' happen to be the experienced wikimedians (like those who have piped up here)? the ones who know (well, knew) where to modify their user preferences?
+
+This sounds so much like a solution looking for a problem.",1401772870,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Amgine from comment #21)
+> Sucks as UX. Do we really want every special page to be creating and
+> maintaining its own interface for user preferences?
+
+We want sensible defaults and intuitive, easy-to-use interfaces. For most users, there shouldn't be a need to customize the default search settings. If many users are customizing their search settings, we're doing something wrong. For the few users who want to customize their search preferences, there's now a checkbox in the same place as search. This seems like a good thing to me.
+
+Because there's now an additional checkbox that controls per-user search preferences, we can de-duplicate the listing at Special:Preferences, which makes for a cleaner user preferences interface (increased signal, decreased noise). This also seems like a good thing to me.
+
+Perhaps a pointer from Special:Preferences to Special:Search would be helpful, but I'm not sure it's needed and I'm not sure where it would appropriately go.",1401766548,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+Ah, but then how simple it is to alter the settings is also out of scope.
+
+My opinion is the people most familiar with the software are those most likely to wish to modify their search preferences. For those users, their user preferences are the most-likely first place to look to alter their user preferences. That would meet most 'least surprise' requirements. Being able to alter the search prefs elsewhere, as Isarra says, would be very cool. Being unable to set the search prefs via the least surprising interface would, in my opinion, not be cool.",1401732710,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",How well those features work is a valid question but it's out of scope for this discussion.,1401732312,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+(In reply to Scott Martin from comment #31)
+> (In reply to Scott Martin from comment #28)
+> > To get to Special:Search you click the magnifying glass
+> > icon in the search box.
+> 
+> Or search for nothing. Sorry for two posts in rapid succession, remembered
+> that a moment too late. (And also had the thought that maybe the magnifying
+> glass thing is a skin-specific feature.)
+
+Cool! and of course you have evidence that people just do this, intuitively.",1401731393,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Scott Martin from comment #28)
+> To get to Special:Search you click the magnifying glass
+> icon in the search box.
+
+Or search for nothing. Sorry for two posts in rapid succession, remembered that a moment too late. (And also had the thought that maybe the magnifying glass thing is a skin-specific feature.)",1401727475,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Nemo from comment #29)
+> (In reply to Isarra from comment #27)
+> > Ideally we'd have some way to automatically dump settings that appear in the
+> > interface elsewhere into main preferences just by telling it 'OY LOOK A
+> > SETTING'.
+> 
+> That's exactly what we did.
+> 
+> > 
+> > May also want a separate page of 'all settings' or 'advanced settings'
+> 
+> We have it:
+> https://www.mediawiki.org/w/api.
+> php?action=query&meta=userinfo&uiprop=options&format=jsonfm
+
+Oh, neat! Very nice.",1401727366,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Isarra from comment #27)
+> Ideally we'd have some way to automatically dump settings that appear in the
+> interface elsewhere into main preferences just by telling it 'OY LOOK A
+> SETTING'.
+
+That's exactly what we did.
+
+> 
+> May also want a separate page of 'all settings' or 'advanced settings'
+
+We have it: https://www.mediawiki.org/w/api.php?action=query&meta=userinfo&uiprop=options&format=jsonfm",1401727218,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Amgine from comment #26)
+> The suggested model is not as simple as Scott Martin describes it. 
+
+Actually, it is. To get to Special:Search you click the magnifying glass icon in the search box.",1401727194,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Ideally we'd have some way to automatically dump settings that appear in the interface elsewhere into main preferences just by telling it 'OY LOOK A SETTING'.
+
+May also want a separate page of 'all settings' or 'advanced settings' for a lot of them (it could also appear collapsed or something by default - the point is while this is often not the stuff folks will necessarily be after, it should be there somewhere in case they are), sort of like the extra 'config' heap you see in firefox and whatnot, but hopefully somewhat easier to find and use.",1401726928,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+@Isarra
+
+So you are saying ""both-and"", not ""eliminate one""? This would probably result in duplication of code and maintenance (which is one of my arguments against moving the preferences in the first place.)
+
+The suggested model is not as simple as Scott Martin describes it. Although setting the preference is top menu -> special: preferences -> tab, this is simpler than tools menu -> special:specialpages -> search -> settings because search is not readily found in the special:specialpages page. Yes, *if one has already done a search* you are already on the page, but if you have not, you aren't. I just attempted to land on search from the search box: foo, qux, and quux are redirs, foobar is an article, baz and asdf are disambigs, and foobaz gets me to search.",1401726027,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I guess there are two things here.
+
+1: Users will primarily care about preferences affecting a specific page when on that specific page. They will be able to most effectively see the effects when on that page, too, so giving them the option to save what works when they're there, seeing that it works, is generally quite useful.
+
+2: Users do tend to expect to find preferences in preferences. A common practice, especially for users who have used the software before but are on a new project, is to go through all of them and quickly configure things how they like them, or think they will. Alternately, if they want to go back and disable something after it behaves weirdly, or if another user tells them to change a setting, the preferences are a likely place to go for that.
+
+Yes.",1401722233,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I don't understand how clicking into Special:Preferences and then a subpage to set options for Special:SomePage is substantially less complicated than going to Special:SomePage and setting them there the first time you use it. Given that most changes to search options will be made on the fly during search experiences, requiring users to leave the special page, go into preferences and then come back (or change preferences in a new tab then reload the search) is a degradation of the UX.
+
+> Preferences are preferences, please keep them together not scattered around the wiki.
+
+""The wiki"" is a misunderstanding here. ""Preferences"" are operational modes for programs, and the special pages are a collection of small utility programs accompanying the core. There's no objective reason why their mode controls should be grouped together remotely with the core's. It's like having the windscreen wiper speed control as a switch on the engine instead of on the dashboard; old-school advanced users of that peculiarly-designed car may be fine with opening the hood to change it because ""it's always been there"", but that doesn't make doing it easy for everyone. A new car would seem particularly old-fashioned if it were still designed this way, and we should be trying to ensure that MediaWiki lives up to the interface design expectations of modern software.
+
+> Please produce the evidence base for this change.
+
+Pretty much every UX study ever that's shown that the further away you put a control from what it affects, the harder users find it to interact with, or even find in the first place - especially new users. It's the GUI-side version of [[Action at a distance (computer programming)]].
+
+S (speaking only for myself, I'm not a MediaWiki developer)",1401721927,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Clutter is removing unnecessary items, redundant items, messy items; clutter is not (re)moving a useful and considered page. So since when is a preference page like Search preference considered clutter? It is clear and specific.  Preferences are preferences, please keep them together not scattered around the wiki.
+
+My attitude is not about any other item, please don't presume.
+
+When I am setting up my preferences for a wiki it is very easy to go into preferences and change the settings that I want. Now you are going to make someone go to the search page to do it, off via other links. That is not more helpful.
+
+If the issue that we give (too) much choice to users, and they are confronted about tabs, then produce a simple and an advanced choice plan. Please produce the evidence base for this change.
+
+To the ""maybe I missed ..."". Have you missed the meaning of the word ""consultation"" and maybe seeking a broader opinion? 
+
+That it is considered that bugzilla is a suitable place for working out a social solution is less than ideal, and yet it happens repeatedly. That a few didn't think it is worthwhile consulting with the broader community about this is disappointing.",1401720133,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #20)
+> It is disappointing that a cabal effect has
+> taken place to what is a significant change to how things are done around
+> here.
+
+I'm sorry you see it that way; I suspect your attitude about this bug is affected by an unrelated change which got merged and reverted in these days after a MediaWiki RfC with a very obscure title. This is nothing like that. 
+
+Maybe you missed something: https://bugzilla.wikimedia.org/showdependencygraph.cgi?id=62559&display=tree&rankdir=LR
+If you did it's not your fault, implementation details discussed in each bug (like this) are just that, details; but it's safe to state that since some time ago there is wide consensus, and a strong push, towards reducing the clutter in MediaWiki by reducing interface complexity in general and Special:Preferences options specifically.",1401718043,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+Sucks as UX. Do we really want every special page to be creating and maintaining its own interface for user preferences?",1401717246,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Really? Preferences are preferences and have belonged in ... umm ... ""Preferences"". Shouldn't such a change have had a wider discussion than between eight and eleven people? Maybe it could have been trialled, and checked through the UI processes. Maybe have used the beta features for testing?
+
+This seems a significant change that really could have had better rigour put to it for an implementation. It is disappointing that a cabal effect has taken place to what is a significant change to how things are done around here.",1401716325,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","There's a very similar move of preferences to page proposed at Bug 48615, for Special:Watchlist. As this change has met approval, it would be great if that bug could see movement - not least because this change will now cause a preference location inconsistency, if you see what I mean.",1401713735,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Bohdan from comment #16)
+> Also why to do a small change on specific WMF wiki's config it's community
+> must hold 1 weeks discussion but a change concerning to all MediaWiki wikis
+> it being done with no discussion at all?
+
+How is the long comment thread above, and the even longer review list on the change itself, ""no discussion at all""? There was discussion, you just didn't participate.
+
+Config changes are not handled by any of the people who were involved in this, except maybe occasionally. Ask the people who handle them about why they have their requirements.",1401661235,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Bohdan from comment #15)
+> Why on Earth I must run through lots of pages to set personal configuration
+
+Lots? As far as I know Special:Preferences contains options for about 3 special pages. It's also less common for users to set preferences for Special:Search without ever having visited it: so the action of tweaking preferences will happen in a visit to Special:Search which would have happened anyway, and the total number of special pages visited should be lower (because it's not necessary to switch to Special:Preferences to save the search options you just selected).",1401653038,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",Also why to do a small change on specific WMF wiki's config it's community must hold 1 weeks discussion but a change concerning to all MediaWiki wikis it being done with no discussion at all?,1401651920,PHID-USER-sscimmfqgfuh4pe2kfyw,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",Why on Earth I must run through lots of pages to set personal configuration for myself on a wiki? I think the best is to keep both central place for changing config in preferences and page specific on appropriate pages.,1401651761,PHID-USER-sscimmfqgfuh4pe2kfyw,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Thanks for all the help, Chad and Bartosz.
+Let's get bug 31881 fixed in 1.24. :)",1401513089,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Change 131727 merged by jenkins-bot:
+Save advanced search namespace prefs on Special:Search itself
+
+https://gerrit.wikimedia.org/r/131727",1401486201,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Well, exact colouring is debatable, however we still have to consider colour-blind and blind users. Thus I believe that colour-highlighting is not a good idea.",1401292566,PHID-USER-37d2msujvpp2rippbzoq,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #9)
+and
+(In reply to Nemo from comment #10)
+
+Use Colored-highlights, and a Legend, for 
+* These options are the site-defaults
+* These options are your customized defaults
+* These options are selected for just-this-search.
+
+This will also solve the ""what were the defaults? I (might) want to reset!"" issue.
+
+My ugly mockup/napkin-sketches, from an unrelated topic, just to inspire further thinking: 
+https://i.imgur.com/IcEWCzF.png
+https://i.imgur.com/tOJOsXG.png",1401232148,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","The behaviour is similar to what happens with the login checkbox, I can't imagine it being so confusing. Only few users very used to the wiki will set their preferred namespaces before their first search.
+
+We can grey out the checkbox when the selection wasn't changed, but that can be done on a separate patch IMHO; a visual confirmation is provided by the checkboxes themselves, which are preserved the next time.",1399498482,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","The idea is good. Now that I see the implementation, it implies you have to perform the search *after* marking that checkbox for it to be saved in your preferences.
+
+Don't get me wrong, I'd also think that you have to mark the checkbox before performing the search, but people not so familiar with web forms may find it not too obvious.
+
+A possible solution to this that I'm thinking of: add a button that on click would change the preferences using an AJAX call, with a visual feedback of the settings being saved.
+
+Also, a checkbox may look weird if you mark it, and after performing the search it remains unchecked (did I checked it when performing the search? or was it totally ignored?).",1399497275,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Created attachment 15314
+Current appearance of the feature
+
+Screenshot of the feature as currently coded. It's just one more checkbox next to a few dozens: the HTML needs to be improved a bit but it's really straightforward from an interface perspective.
+
+//attachment Bug52817.png ignored as obsolete//",1399474582,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Change 131727 had a related patch set uploaded by Nemo bis:
+[WIP] Save advanced search namespace prefs on Special:Search itself
+
+https://gerrit.wikimedia.org/r/131727",1399394092,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","You'll want to use 'type' => 'api' (which is, admittedly, somewhat misleadingly named). One core preference using this is 'watchlisttoken'.",1399319859,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","[[mw:Manual:Preferences]] and [[mw:Manual:Hooks/GetPreferences]] are not particularly helpful. To hide preferences from Special:Preferences, should they be made of ""hidden"" type? Added to $saveBlacklist? Spinned off from Preferences.php completely?",1399304670,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Are we still collecting (re)thoughts or is this bug focused on a specific change? Seems the latter, changing subject.",1390658642,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",*** Bug 37878 has been marked as a duplicate of this bug. ***,1390582522,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to comment #1)
+> I really really like this idea.
+
+Should we set this ticket as for something we'd like to have in the next release (1.22) then?",1376595939,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",I really really like this idea.,1376589869,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","The ""Enable section editing via [edit] links"" user preference should be removed from MediaWiki core.
+
+Users interested in hiding section-edit links can use per-user (or site-wide) CSS.
+
+This should be an easy bug to resolve; marking it with the Bugzilla keyword
+accordingly.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1376416020,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cttzml5ohhludlqqeslk,task_description,resolved
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","**troyengel** wrote:
+
+Got it -- I had to add !important, so this works:
+
+  .mw-editsection { display:none!important; }
+
+I'll get the wiki page updated with the new method, thanks!",1404052977,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to TE from comment #16)
+> Can one of y'all please post exactly what needs to go where to disable
+> site-wide this feature for anonymous, new and previous (logged in) users so
+> that this change removing the feature can be put back into CSS?
+
+You can try adding the following code to the page ""MediaWiki:Common.css"" on your wiki (untested, but should work...):
+
+.mw-editsection { display: none; }",1404052704,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","**troyengel** wrote:
+
+I'm not a MediaWiki guru to be able to figure this out, but with the 1.23 release I can't figure out how to disable this again. It's referenced above:
+
+""Users interested in hiding section-edit links can use per-user (or site-wide) CSS.""
+
+Great, but can someone update documentation on exactly *how* to do this? In my LocalSettings.php I have the old setting which is apparently ignored now:
+
+  $wgDefaultUserOptions ['editsection'] = false;
+
+I've dumped the DB and grepped and find only one reference to 'noeditsection' in the data, and my user account still shows the [Edit] on sections. The wiki indicates nothing about this change yet:
+
+  http://www.mediawiki.org/wiki/Manual:$wgDefaultUserOptions
+
+Can one of y'all please post exactly what needs to go where to disable site-wide this feature for anonymous, new and previous (logged in) users so that this change removing the feature can be put back into CSS?
+
+I'd be happy to update the above wiki page if someone just tells me *how* to go about it as a low-speed wiki operator who doesn't live & breathe this code. Thanks!",1404051842,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to Danny B. from comment #14)
+> Described in the last line of comment #11.
+
+The last line of comment 11 is:
+> And gadgets are what? Saved in preferences. Hence we are where we were.
+
+Sure, but most users and most wikis don't want or need an extra user preference for this. These links are automatically shown based on user permission and they're able to be hidden on a site-wide basis, on a per-page basis, and on a per-user basis. I don't see a need for a user preference here. What's the use-case, exactly? Why would a user want to hide these links for only their account?
+
+Regarding gadgets specifically, a few wikis might create such a gadget, but I doubt it. The overall MediaWiki experience (including that of most Wikimedia wikis) will have less clutter. This seems like a win to me.
+
+>> Out of curiosity, has this happened anywhere?
+> 
+> Yes.
+
+Where? Links welcome. :-)",1392773594,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to MZMcBride from comment #13)
+> (In reply to Danny B. from comment #11)
+> > This is nonsense. It should not have been removed.
+> 
+> Why's that?
+
+Described in the last line of comment #11.
+
+> > So there will be gadget created on sites to enable hiding.
+> 
+> Out of curiosity, has this happened anywhere?
+
+Yes.",1392772887,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to Danny B. from comment #11)
+> This is nonsense. It should not have been removed.
+
+Why's that?
+
+> So there will be gadget created on sites to enable hiding.
+
+Out of curiosity, has this happened anywhere?",1392690275,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","See comment 0 and comment 5 for reasoning, plus this request (""Remove ... user preference"") is obviously FIXED as the code commit has been merged. :)
+
+I don't think this specific bug report is the place for a generic ""I want less popular ancient options to be removed from the user preferences to reduce UI clutter"" vs. ""I want less people to have to edit their custom CSS or write Gadgets to do X"" discussion - should maybe happen on mediawiki-l instead if there is interest.
+
+However I agree that statistics on how many users have enabled such a setting might be helpful for future evaluation when killing some preferences.",1391604424,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","This is nonsense. It should not have been removed.
+
+comment #0 says: ""Users interested in hiding section-edit links can use per-user (or site-wide) CSS.""
+
+Exactly.
+
+So there will be gadget created on sites to enable hiding. (because Jorm is totally true with 'Can we just agree from this day forward that ""put it in your user css"" is not an acceptable solution for any problem, ever?'
+
+And gadgets are what? Saved in preferences. Hence we are where we were.",1391543815,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 99171 merged by jenkins-bot:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+https://gerrit.wikimedia.org/r/99171",1390589269,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 108673 abandoned by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+Reason:
+Abandoned: Original patchset at :
+https://gerrit.wikimedia.org/r/#/c/99171/
+
+https://gerrit.wikimedia.org/r/108673",1390587668,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 99171 restored by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+Reason:
+Errors in Rebasing. 
+Restoring for further tests..
+
+https://gerrit.wikimedia.org/r/99171",1390376736,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 108673 had a related patch set uploaded by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+https://gerrit.wikimedia.org/r/108673",1390310439,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 99171 abandoned by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+Reason:
+Rebase errors persistant :(
+
+https://gerrit.wikimedia.org/r/99171",1390310410,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Brian's caution (asking some up to date stats) makes sense, however it should be noted that AFAIK this preference is mainly a relic of the ancient past when section editing was the last new thing. :) Maybe we'll need this preference again if VisualEditor ever finds some magic to allow section editing again. :P",1386970419,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to comment #3)
+> Maybe the relevant code form the parser itself can also be removed?
+
+I'm not sure what you mean here.",1386225166,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Just for the record:
+
+<jorm> Can we just agree from this day forward that ""put it in your user css"" is not an acceptable solution for any problem, ever?
+
+From https://bugzilla.wikimedia.org/quips.cgi?action=show
+
+Maybe the relevant code form the parser itself can also be removed?",1386186606,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 99171 had a related patch set uploaded by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from Mediawiki Preference.
+
+https://gerrit.wikimedia.org/r/99171",1386179478,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core",I would like to prepare a patch for this bug. Please assign it to me.,1386178444,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"A user asks if VE shouldn't now get rid of apostrophes used for formatting and use common tags instead <b>, <i>...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376398800,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bgfttfnluju4mvokk3ud,task_description,resolved
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"Closing this as a duplicate to avoid confusion.
+
+*** This bug has been marked as a duplicate of bug 49143 ***",1380661120,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"Supporting HTML storage is indeed one of our goals for this fiscal year, and an important part of our long-term strategy. We plan to store both HTML and wikitext (plus metadata) for a while, but are working on supporting HTML-only wikis. Those will still be editable using wikitext by using Parsoid for the conversion from HTML to wikitext and then back to HTML after the edit.
+
+See our roadmap at https://www.mediawiki.org/w/index.php?title=Parsoid/Roadmap&oldid=738055 for more detail.",1376517975,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"(Can't reply right now and for a few days, but in the meantime, someone else begs to differ: http://www.flickr.com/photos/fabola/7571369108/in/set-72157630578652390 )",1376516329,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,Bug 49143 is the related bug.,1376512331,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"To clarify, is this asking for VisualEditor to replace wikitext (WT) with HTML equivalents (but still inside a wikitext place)?
+
+If so, that's not something we will do:
+
+* it makes it hard for users to edit with WT;
+* it would be bad to have VE replace other users' WT unexpectedly;
+* it would be confusing to have mixtures of WT and HTML; and
+* it doesn't save anything technically (it'd still need to go through Parsoid).
+
+Because of these factors, that suggestion is a WONTFIX.
+
+However, there is a different goal for Parsoid to be able to store their HTML+RDFa in the database directly, either alongside, or instead of, the WT that is currently stored. This has a number of advantages but is very far off.
+
+I'm going to re-sort this to reflect the second of these, as I don't believe that there is an existing bug.",1376512174,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,I believe this is a long-term goal.,1376447318,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+VisualEditor: Warn if editing a reference that is used multiple times,"<< When editing a reference, there is no indication at all if it is used multiple times throughout the article. This makes it very easy to screw up references, e.g. when you replace a ref for one sentence by changing it and it gets propagated throughout the article. WS (talk) 11:45, 13 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376394960,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-pdifcdlqnopvfjzdvczw,task_description,resolved
+VisualEditor: Warn if editing a reference that is used multiple times,"The warning ""This reference is used [n] times on this page."" appears for Basic citations only  - verified the fix in beta, test2, and production. 
+
+Bug 73566 was filed to apply the same warning to multiple instances of any kind of citations.",1416331982,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-pdifcdlqnopvfjzdvczw,task_subcomment,NA
+VisualEditor: Warn if editing a reference that is used multiple times,"Change 169270 merged by jenkins-bot:
+Show warning on reference dialog when editing a reference used in more than one place
+
+https://gerrit.wikimedia.org/r/169270",1414517770,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pdifcdlqnopvfjzdvczw,task_subcomment,NA
+VisualEditor: Warn if editing a reference that is used multiple times,"Change 169270 had a related patch set uploaded by Alex Monk:
+Show warning on reference dialog when editing a reference used in more than one place
+
+https://gerrit.wikimedia.org/r/169270",1414453877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pdifcdlqnopvfjzdvczw,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52771",1376340600,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-m6mab3qibjjsonpriu5r,task_description,resolved
+VisualEditor: cutting block level elements changes the type of following element,"Change 981374 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (402570007)%%%
+https://gerrit.wikimedia.org/r/981374",1701976845,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"Change 981374 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (402570007)%%%
+https://gerrit.wikimedia.org/r/981374",1701971210,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"Change 980444 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Make headings of different levels ""un-mergeable""%%%
+https://gerrit.wikimedia.org/r/980444",1701967183,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"Change 980444 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] Make headings of different levels ""un-mergeable""%%%
+https://gerrit.wikimedia.org/r/980444",1701798922,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,Similar to T52419 in that it involves selections which overflow into the next CBN.,1701797695,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"This was first raised at 
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Removing_line_above_header_.22de-headers.22_it.3B_lack_of_.22undo.22_facility
+
+If you have a document like
+==Heading 2==
+===Heading 3===
+====Heading 4====
+Paragraph.
+
+i.e.
+
+<h2>Heading 2</h2>
+<h3>Heading 3</h3>
+<h4>Heading 4</h4>
+<p>Paragraph.</p>
+
+and select the heading 3 block, so the selection goes all the way to the right hand side of the screen then delete, it will change the following heading to be an <h3> element. Likewise deleting the whole of the heading 4 line and deleting changes the paragraph to be a <h3> heading.
+
+I've made a test file at http://en.wikipedia.org/wiki/User:Salix_alba/VE_test",1376341181,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, use TemplateData to hint the parameter's default value, if set","**Author:** `l736ewiki`
+
+**Description:**
+The data model for TemplateData allows the tag ""default"" to assign the default value for parameters which foresee it.
+
+However, when adding a template to an article via VisualEditor, the default value is not presented inside the corresponding input field, which appears empty, nor there are automatic hints about the default value (unless who generated the TemplateData object inserted it into the textual ""description"" item).
+
+I would have expected that:
+* either the user is presented with the input field already pre-filled with the default value as specified inside the TemplateData description - this would improve usability
+* or, if this pre-population of the input field is too complex/costly to achieve, at least the information about the ""default"" value is taken and highlighted using the corresponding ""default"" attribute from the parameter description.
+
+You can test this on it.wiki, by trying editing a new article using VE and adding the template named ""Azienda"", whose ""logo_dimensioni"" parameter has been defined in JSON with ""default"":""200"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376324640,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ejfpqmqzgmehdhmxzmty,task_description,resolved
+Show a message explaining how to edit references when user selects a references list,"Reports such as https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=568123469#I_can.27t_edit_the_references suggest that the references list being present but not editable is causing confusion for editors.
+
+It would therefore be helpful for VE to display a message (popup? tooltip?) whne the reference list is selected that explains how to edit references. The text of this message should be set on a MediaWiki namespace page.
+
+I don't have a suggested default wording at present.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52750",1376257440,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xffvpozuzkjhhlysn3cs,task_description,invalid
+Show a message explaining how to edit references when user selects a references list,No longer needed after {T54750} made the referenced editable inside the references list.,1724164016,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+Show a message explaining how to edit references when user selects a references list,I'm suggesting that task for the Hackathon 2019 since it is something that would ease newcomers' lives. ,1551084196,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+Show a message explaining how to edit references when user selects a references list,[[https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Questions_techniques/semaine_28_2016#Impossibilt.C3.A9_d.27apporter_des_corrections_dans_les_sections_Notes_et_r.C3.A9f.C3.A9rences|New feedback from a user]] (a beginner) who wants to change a reference rom the reflist while editing with VE. ,1468426304,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+Show a message explaining how to edit references when user selects a references list,"This would be most helpful if the backlinks took you to the position of reference while remaining in edit mode.
+
+Suggestion for the message from en.wp user Looie496:
+ ""This list of references is automatically generated and cannot be edited directly. If you would like to change the content of a reference, click on its number where it appears in the body of the article.""",1376323680,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+Show a message explaining how to edit references when user selects a references list,"If implemented, bug 52750 would make this request either unnecessary or applicable only as an interim measure. In the latter case there wouldn't be any need for the message requested here to be editable on-wiki.",1376315524,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**Author:** `gitartha.bordoloi`
+
+**Description:**
+Hello,
+Visual editor was deployed as an opt-in editing tool in Assamese wikipedia about 2 months ago. However it seems the tool doesn't support Assamese script well. While writing with some tools reproduces only vowels or consonants, the in-built keyboards do not work at all. Kindly look into this matter urgently before it is released as default editing tool. The discussions can be found here: http://as.wikipedia.org/wiki/%E0%A7%B1%E0%A6%BF%E0%A6%95%E0%A6%BF%E0%A6%AA%E0%A6%BF%E0%A6%A1%E0%A6%BF%E0%A6%AF%E0%A6%BC%E0%A6%BE_%E0%A6%AC%E0%A6%BE%E0%A7%B0%E0%A7%8D%E0%A6%A4%E0%A6%BE:%E0%A6%AD%E0%A6%BF%E0%A6%9C%E0%A7%81%E0%A7%B1%E0%A7%87%E0%A6%B2_%E0%A6%8F%E0%A6%A1%E0%A6%BF%E0%A6%9F%E0%A7%B0
+
+Thank you.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1376210460,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ltfnf6nk2htfdban76pc,task_description,resolved
+VisualEditor: Typing problem in Assamese,No replies. Assuming this has been resolved as I can neither reproduce with Assamese input methods provided by UniversalLanguageSelector nor with Assmese input methods offered by my operating system when using VisualEditor.,1644959034,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Could somebody please answer if what's left to do in this ticket ""just"" a dup of {T51569}, or is there more to do (if so, what?)",1429647219,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Is what is left to do in this ticket ""just"" a duplicate of {T51569}? 
+Or is there more to do (if so, what?)",1426772092,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Is what is left to do in this ticket ""just"" a duplicate of {T51569}? 
+Or is there more to do (if so, what?)",1425554546,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"(In reply to comment #11)
+> NONE of the 6 in-built keyboards are working as of today.
+
+I wonder if this is the same as T60662 comment 5 which is marked as a duplicate of T51569...",1425554489,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"(In reply to comment #11)
+> NONE of the 6 in-built keyboards are working as of today.
+
+I wonder if this is the same as bug 58662 comment 5 which is marked as a duplicate of bug 49569...",1389025768,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**gitartha.bordoloi** wrote:
+
+Hello developers,
+I'm regularly checking the visual editor in Assamese wikipedia and now it supports the ""external keyboards"" nicely. There is no problem with rendering of Assamese characters as I reported earlier. However NONE of the 6 in-built keyboards are working as of today. Trying to write something with those keyboards render only Roman characters. I reported the same problem in last August also. Here is a link to my sandbox page in Assamese wikipedia where I've tested the visualeditor with different keyboards. 
+https://as.wikipedia.org/wiki/user:Gitartha.bordoloi/visualeditor_test
+
+I've tested it on Mozilla Firefox 26 and Google chrome 30 (windows 7 pc). I'll be glad to hear about any new developments. Thanks.",1389023971,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"(In reply to comment #8)
+> I tested it in Assamese wikipedia because on 5th September it was mentioned
+> that ""please re-open if you find that it is still happening after tomorrow
+> (when the code will go live on the Assamese Wikipedia)"". I tested it in
+> mediawiki today and found some problems. I'll wait until Thursday and test it
+> in aswiki again. Thank you.
+
+Would it be possible to test 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!",1381269409,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Hello Gitartha, could you also please add some screenshots if you find any problems after your next test? Thanks.",1379515454,PHID-USER-ttw4tpoosxc4pbmskrla,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**gitartha.bordoloi** wrote:
+
+I tested it in Assamese wikipedia because on 5th September it was mentioned that ""please re-open if you find that it is still happening after tomorrow (when the code will go live on the Assamese Wikipedia)"". I tested it in mediawiki today and found some problems. I'll wait until Thursday and test it in aswiki again. Thank you.",1379403525,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"(In reply to comment #6)
+> Hello. I'm reopening the bug as the problems mentioned earlier are still
+> there. Nothing has changed.
+
+Which wiki did you test? The changes only went out to MediaWiki.org last Thursday, 12 September (so you can test these at https://mediawiki.org/wiki/VisualEditor:Test or similar) - they will not be released to the Assamese Wikipedia until this Thursday, 19 September.",1379346325,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**gitartha.bordoloi** wrote:
+
+Hello. I'm reopening the bug as the problems mentioned earlier are still there. Nothing has changed.",1379327158,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,Going to provisionally mark this as fixed - please re-open if you find that it is still happening after tomorrow (when the code will go live on the Assamese Wikipedia).,1378341679,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,I think https://gerrit.wikimedia.org/r/#/c/80080/ may have solved this - let us know!,1377353858,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Hello, Thanks for reporting this. We are currently working to resolve the several issues around using Indic language scripts on the VisualEditor and we expect to resolve them soon. The problem reported in the current bug is also known and exists in other Indic scripts as well.  More discussion about this topic can also be found on bug #49569 . Thanks.",1376926685,PHID-USER-ttw4tpoosxc4pbmskrla,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**gitartha.bordoloi** wrote:
+
+(In reply to comment #1)
+> Thanks for taking the time to report this!
+> 
+> (In reply to comment #0)
+> > doesn't support Assamese script well
+> > While writing with some tools
+> > in-built keyboards do not work at all
+> 
+> Can you please provide more information / exact steps to reproduce the
+> problems, plus information about browser and version? Also, what are ""some
+> tools"" exactly?
+> Also see https://www.mediawiki.org/wiki/How_to_report_a_bug . Thanks!
+
+Thanks for pointing out the problems with the report.
+
+* I have tested it in Mozilla Firefox 22 and Google chrome 23.
+* There are currently 6 input layouts for Assamese under ULS. While trying to write Assamese in visualeditor with any one of them, NO Assamese character comes out.
+* 'Some tools' refer various Assamese writing tools like to Rodali, Baraha, Azhagi+, Avro barnana etc.
+
+With Rodali, there seems to be problems with vowels like  ী (ঈ), ূ (ঊ), ৌ (ঔ). So while trying to write 'অসমীয়া', it becomes 'অসীয়া'. 'মূহুৰ্ত' becomes ' ূহুৰ্ত', 'কৌটি' becomes ' ৌটি' etc.
+
+with Azhagi+, the problem is more. Only the last vowel character of a word is shown in visualeditor. So 'অসমীয়া' becomes 'া'.
+
+With Baraha, the problem is again with vowel characters like ঐ and ঔ. So 'সৈমান' becomes ' ৈমান'.
+
+Similar problems exists with Avro.",1376765523,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Thanks for taking the time to report this!
+
+(In reply to comment #0)
+> doesn't support Assamese script well
+> While writing with some tools
+> in-built keyboards do not work at all
+
+Can you please provide more information / exact steps to reproduce the problems, plus information about browser and version? Also, what are ""some tools"" exactly?
+Also see https://www.mediawiki.org/wiki/How_to_report_a_bug . Thanks!",1376388861,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"MassMessage is an extension that allows a user to send a message to a list of pages through a special page and the job queue. It is intended to replace [[m:Global message delivery]].
+
+More details are available at [[mw:Extension:MassMessage]], and there is a test instance at http://legoktm.instance-proxy.wmflabs.org/wiki/Main_Page
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://www.mediawiki.org/wiki/Extension:MassMessage",1376204700,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_description,resolved
+Review and deploy MassMessage extension to Wikimedia wikis,"Change 91344 had a related patch set uploaded by MZMcBride:
+Enable MassMessage on all wikis
+
+https://gerrit.wikimedia.org/r/91344",1382635706,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #59)
+> Lego: can you please submit a changeset to enable MassMessage on all (public)
+> Wikimedia wikis?
+
+I submitted https://gerrit.wikimedia.org/r/#/c/91344/ a few days ago.",1382632875,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,Lego: can you please submit a changeset to enable MassMessage on all (public) Wikimedia wikis?,1382632099,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"I've been working with Aaron via email on the architecture review and I believe everything has been resolved (cc'd Aaron to get confirmation on that).
+
+(In reply to comment #57)
+> All of the blocking bugs have been resolved. What happens now? (Greg?)
+
+Thanks for merging :). I just added bug 55822 which is a config change for how the jobs will get processed, it would be good to get that deployed and make sure there are no issues before the full deployment.",1381975397,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,All of the blocking bugs have been resolved. What happens now? (Greg?),1381932420,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #54)
+> One more thing - we'll need to add standard licensing/ToS language to the
+> submit screen to ensure content is licensed consistent with Wikimedia
+> requirements. The wikimedia-copyrightwarning message in the WikimediaMessages
+> extension should do the trick.
+
+(The relevant function is EditPage::getCopyrightWarning(), the messages shouldn't be used directly.)",1380916155,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #53)
+> I have a quick question about the extension itself. Maybe I'm reading this
+> code
+> wrong, but the extension appears to iterate through the recipients on the
+> special page, and then make a new job for each recipient. If this is true,
+> that
+> means that this extension would be launching thousands of jobs from a single
+> web request. It kind of defeats the purpose of the job queue in the first
+> place.
+
+Yes, that's correct. I'm not sure how it defeats the purpose of the job queue though. We could do it like refreshlinks works and submit a job that submits more jobs, but I don't see how that would be any better. I did a simple test on testwiki a week ago and submitted 2k jobs at once and it seemed to work fine.
+
+> 
+> Also, do people have some sort of irrational fear of the FormSpecialPage
+> class?
+
+I actually didn't know that existed until now. I basically forked the code of TranslationNotifications and used that...",1380906728,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,One more thing - we'll need to add standard licensing/ToS language to the submit screen to ensure content is licensed consistent with Wikimedia requirements. The wikimedia-copyrightwarning message in the WikimediaMessages extension should do the trick.,1380906422,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"I have a quick question about the extension itself. Maybe I'm reading this code wrong, but the extension appears to iterate through the recipients on the special page, and then make a new job for each recipient. If this is true, that means that this extension would be launching thousands of jobs from a single web request. It kind of defeats the purpose of the job queue in the first place.
+
+Also, do people have some sort of irrational fear of the FormSpecialPage class?",1380906258,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #48)
+> (In reply to comment #39)
+<snip>
+
+I've filed bug 54954 as a blocker to this one. I've asked a few preliminary questions on how this should be implemented, so if people who have options could comment there please :)",1380863370,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #48)
+If there is any way to do global logs (alongside local ones) this would be a very good place to use that, as that would make all wikis much more easily accountable for any usage of this tool.
+
+That said you're probably right in that just enabling the sending part on meta would be better, since, on top of logs and such all being in one place, usage guidelines and crap would also be better synced. And implicitly trusting all admins isn't necessarily a good idea when different projects can have completely different methods and standards when approaching problems, and on top of that pretty much anyone can become an admin at least somewhere (which isn't even necessarily a bad thing, since if they happen to be in the right place even the most unexpected of folks can prove quite useful, but also doesn't mean it should carry weight elsewhere).
+
+So just have a request page for anyone new to use, and a right that can be added to anyone who ain't an admin if they've general use for the spammer and clearly understand what not to do, or whatever. I'm sure the meta folks can argue out some actual details there.",1380862739,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #34)
+> [...] Last year, there was a broken core change about timestamping slipped through
+> Platform review and got deployed. Because of that, a better thought-out and
+> previously-developed pending core change for the exact same feature from
+> Werdna
+> got bumped. [...]
+
+The only thing I found is https://gerrit.wikimedia.org/r/#/c/15746 which was merged after ignoring code-review for months, causing a developer and translator revolt.
+
+(In reply to comment #48)
+> So I'm not comfortable with a deploy that amounts to giving admins in every
+> wiki 'massmessage' permission to every other wiki. I'd be fine with 1)
+> limiting
+> the availability of the massmessage permission to Meta, or 2) adding back the
+> global/local message delivery distinction and enabling local delivery on all
+> wikis, and global delivery on Meta.
+> 
+> Better broadcasting tools should still continually be developed, and the
+> imperfections of this approach will hopefully feed into whatever comes next,
+> whether it's an iteration on MassMessage or an entirely new approach.
+
++1
+I think this is totally reasonable and was indeed my only true worry about the extension.
+I'd add the permission to a special group, possibly reusing centralnoticeadmin group, since the first deploy, to avoid needless requests for adminship.
+More than that, we could even try to replicate the logging of the messages content to a wiki page, for enhanced accountability.",1380862493,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,s/ReviewerBot/MessengerBot/,1380861508,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #39)
+> This was considered and it's probably easy enough to implement these
+> restrictions, but as I said above, I'm not sure they're necessary. My view
+> was
+> to take a ""wait and see"" approach. If local administrators begin to abuse or
+> misuse the tool, we can always add in restrictions later.
+
+I would actually look at it differently. Right now, as I understand it, cross-wiki message delivery is only configured to be run from Meta, where it's easy to see who's configuring what ""spams"" and for what audiences. It's easy for folks to have a shared conversation about what's appropriate and what isn't, and even for people to revert additions that they see as unreasonable.
+
+So you've actually created a very clever tool that plays well into the norms of the wiki community, and uses an existing shared space (Meta) in the intended manner.
+
+In contrast, enabling admins everywhere to _easily_ post bulk messages across wikis from anywhere, with the audit trail being HTML comments in the messages that are left, is IMO quite likely to play against the norms of the wiki, because messages _will_ be sent in a manner that's inconsistent with the norms of a given target wiki, and it'll be harder for the community to have a shared conversation about it or even to easily see what's happening (because there is no central message log at that point).
+
+Because actions such as compiling target lists are dispersed, the normal processes of community peer review won't kick in as effectively to moderate and monitor behavior.
+
+Yes, anyone can of course post anywhere today, but not everyone has access to a shared bot account that they can use on any wiki to do so, nor do they have an automated delivery tool. ReviewerBot would suddenly take bot actions on wikis and users would be tasked with figuring out what's going on. That's manageable if the only possible source is Meta, but more problematic if the source is any of our wikis.
+
+Cross-wiki bulk messages to anywhere from anywhere are a significant change from the status quo that requires more consideration. And on that point, WMF will certainly get the blame if the tool is misused.
+
+So I'm not comfortable with a deploy that amounts to giving admins in every wiki 'massmessage' permission to every other wiki. I'd be fine with 1) limiting the availability of the massmessage permission to Meta, or 2) adding back the global/local message delivery distinction and enabling local delivery on all wikis, and global delivery on Meta.
+
+Better broadcasting tools should still continually be developed, and the imperfections of this approach will hopefully feed into whatever comes next, whether it's an iteration on MassMessage or an entirely new approach.",1380861333,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+> > To the first document which has its origins in the SVN days, the first stop
+> > with Howie Fung and his product management team. To my knowledge the only
+> > person asked was a Dan Garry, and not as a first stop on anything. 
+> 
+> Dan was cc'd by Greg in comment 13. I wasn't aware that Platform and/or
+> Features were supposed to be in the loop so I never bothered to do it.
+
+It's unfortunate. Dan is new and is not really in a position to speak for product, and I don't think that was the intent of comment 13 to make him make a call.
+
+The implication of Platform or Features is in the later stage of code review for deployment. There was a time that Sumana would manage that using 20% time volunteered by Features, but that was over a year ago. :-( Since then commitment to maintain deployed extensions has fallen through the crack between Platform and Features.
+
+> Correct. I had spoken with Greg a few days earlier about emailing wikitech-l
+> /
+> Aaron / Tim for the architecture review, and he recommended that I wait for
+> your comments ;-)
+
+Oh, well then why was it added to the deploy calendar? Can we remove it backand wait for comments to make sure it's okay to deploy before adding it to the lsit of things to be deployed? As it stands now, my position is I'm okay with it because Ori is okay with helping you support and monitor it for issues that might crop up like comment 37 above.
+
+> > The second document is newly written by Platform not vetted by anyone in
+> > Features.
+> 
+> For someone outside of the WMF who is trying to get an extension deployed,
+> the
+> distinction between Platform and Features isn't very clear, nor really
+> important. Was VipsScaler (also written by a volunteer) handled by Features?
+
+No, and in earlier incarnations of the queue, I think [[mw:VipsScaler]] was linked. Development on it was started in 2011, I think multimedia team (originally a Features team, now in Platform) deployed it. That team is obviously committed to maintain. :-)
+
+> All we really want is our code deployed :P
+
+Totally understandable. :-)
+
+
+> The checklist is fine, it just seems like its missing one step according to
+> you
+> (notify Features and/or Platform teams).
+
+I'm okay with clarifying that a design review means a product design review and PM signoff and adding that a plan for engineering, product, and design maintenance needs to be in place going forward (beyond simply bugzilla).",1380858967,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+(In reply to comment #41)
+> (In reply to comment #7)
+> > == TODO/Check list ==
+> > Extension page on mediawiki.org: yes
+> > Bugzilla component: yes
+> > Extension in Gerrit: yes
+> > Design Review: no
+> > Archeticecture/Performance Review: no
+> > Security Review: no
+> > Screencast (if applicable): no
+> > Community support: no?
+> 
+> As a designer, I did a design review over IRC. I said something along the
+> lines
+> of 'looks shiny'.
+> 
+> I hope that helps, as I'm not sure what more you could want with this kind of
+> extension. Other issues beyond the interface itself have generally already
+> been
+> established by precedent (EdwardsBot).
+
+We'd have to ask Greg what he really meant by this when he added that to [[mw:Review queue]] instead of leaving the process pointing back to [[mw:Writing_an_extension_for_deployment]], but if I were to hazard a guess:
+
+I think Greg tried to clear the review queue because it was suffering from neglect. He tried summarize the original linked document: [[mw:Writing_an_extension_for_deployment#Design_review]] by saying it has a proper ""design review."" It clearly implies design review as being a product design review with a design UI design component [[mw:WMF_Project_Design_Review_Process]] probably dating back to when they were in the same department.
+
+If you look at an earlier revision [https://www.mediawiki.org/w/index.php?title=Review_queue&oldid=697844], you can see the tracking list that was its original purpose since Brion created it. Around that time, it was getting unmanageable four months ago with little movement. My guess is that there simply had been no recent Extensions (other than in-flight extensions like Math and SignupAPI) that had actually gone through this process and in an effort to systematize the process into a workable checklist, it got morphed over time from ""send it to product design for review"" to ""send an e-mail to a designer and to the design mailing list."" *shrug*",1380857974,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #40)
+> (In reply to comment #38)
+> 
+> > > The requirement for extensions to be deployed has ALWAYS been that Features
+> > > Engineering sign off on a commitment to maintain the extension.
+> > 
+> > This isn't consistent with the documentation at [[mw:Writing an extension for
+> > deployment]], [[mw:Review queue]] and Greg's checklist in comment 7.
+> 
+> Interesting links.
+> 
+> To the first document which has its origins in the SVN days, the first stop
+> with Howie Fung and his product management team. To my knowledge the only
+> person asked was a Dan Garry, and not as a first stop on anything. 
+
+Dan was cc'd by Greg in comment 13. I wasn't aware that Platform and/or Features were supposed to be in the loop so I never bothered to do it.
+
+> I mentioned
+> in my original post why that people should know better. The second stop was
+> wikitech-l. To my knowledge mine was the first post on the subject.
+
+Correct. I had spoken with Greg a few days earlier about emailing wikitech-l / Aaron / Tim for the architecture review, and he recommended that I wait for your comments ;-)
+
+
+> The second document is newly written by Platform not vetted by anyone in
+> Features.
+
+For someone outside of the WMF who is trying to get an extension deployed, the distinction between Platform and Features isn't very clear, nor really important. Was VipsScaler (also written by a volunteer) handled by Features? All we really want is our code deployed :P
+ 
+> The third link refers to someone who has been at the WMF even less time than
+> me. If we're to use MZMcBrides seniority rules, the fact that some
+> newly-minted, improperly vetted document was used by a relatively new
+> engineer
+> doesn't carry weight.
+
+The checklist is fine, it just seems like its missing one step according to you (notify Features and/or Platform teams).
+
+> I hope that documentation is updated.
+
+Be bold!",1380856387,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #41)
+> As a designer, I did a design review over IRC. I said something along the
+> lines
+> of 'looks shiny'.
+
+For reference, Isarra created [[commons:File:Massmessage preview (uncyc).png]], and pointed out a few flaws in the initial design, like using tables for the form (now switched to proper <div>s), and the submit/preview buttons stacked on top of each other (now side-by-side).",1380855315,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #39)
+> (In reply to comment #37)
+> > Is the current thinking to give users on any wiki the right to use
+> > Special:MassMessage to spam users on any other wiki?
+> 
+> Yes. The design idea here was that this is already possibly by any user.
+> Anyone
+> can open up a bunch of browser tabs and post to dozens of wikis quickly
+> without
+> even logging in. Or, for example, I've been posting to hundreds of wikis for
+> years without a privileged account using only a very simple Python script.
+
+It might be worth noting that the MassMessage bot account used automatically adds itself to the 'bot' group, but isn't able to override full protections or anything like that.
+
+> 
+> > It seems to me you'd want something like:
+> > 
+> > * Users on Meta can trigger cross-wiki notifications;
+> > * Users on any other wiki can only trigger local notifications.
+> 
+> This was considered and it's probably easy enough to implement these
+> restrictions, but as I said above, I'm not sure they're necessary.
+
+An initial version of the extension had this differentiation, but it was removed in https://gerrit.wikimedia.org/r/#/c/78047/. I don't mind revisiting the concept either (file a bug for it?), as it wouldn't be hard to implement technically.
+
+> My view was
+> to take a ""wait and see"" approach. If local administrators begin to abuse or
+> misuse the tool, we can always add in restrictions later.
+> 
+> > Otherwise you end up with an audit trail mess. Having a single log in one
+> > place and a single place to set policy around these things seems highly
+> > desirable.
+
+I actually wrote [[mw:Extension:CentralLogging]] for this problem a while back, but it wouldn't work in the WMF environment.
+
+  
+> The bot currently provides an audit trail by (optionally?) appending an HTML
+> comment containing the originating wiki, message sender's name, etc., I
+> believe. Lego can confirm this.
+
+The audit trail is not optional (though a wiki could choose to blank the message and make it useless). An example is <https://test2.wikipedia.org/w/index.php?title=User_talk:Legoktm&action=edit&section=2>, which includes the origin wiki, sender, and spamlist used.",1380855098,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #40)
+> Do you have a link to this doctrine regarding software deployments and
+> sign-offs? [...] perhaps there's a guideline you've written on mediawiki.org,
+> wikitech.wikimedia.org, or Meta-Wiki. Please share.
+
+Go on. I'll wait.",1380854469,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #7)
+> == TODO/Check list ==
+> Extension page on mediawiki.org: yes
+> Bugzilla component: yes
+> Extension in Gerrit: yes
+> Design Review: no
+> Archeticecture/Performance Review: no
+> Security Review: no
+> Screencast (if applicable): no
+> Community support: no?
+
+As a designer, I did a design review over IRC. I said something along the lines of 'looks shiny'.
+
+I hope that helps, as I'm not sure what more you could want with this kind of extension. Other issues beyond the interface itself have generally already been established by precedent (EdwardsBot).",1380854018,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+You're going to resort to ad hominem instead of attacking the argument when you're already getting what you want?
+
+I am not trying to ""dictate"" anything to volunteers. Volunteers didn't deploy the code onto test and test2, it was Reedy. Volunteers are free to develop. They're not free to have their developed code deployed on the cluster. Nobody is.
+
+As for the proof of this ""doctrine,"" just like MediaWiki core has always been the responsibility of Platform, the Extensions space has traditionally been the responsibility of Features Engineering. Historically, new extension deploy and a commitment to deploy was done by Brion and later by Roan. This used to be enforced in terms of SVN access, and the artifact still exists in the form of who has +2 on Gerrit. In the case of deploying a new extension, it requires +2 on gerrit, shell access, and an implied commitment to maintain.
+
+I've been trying to relax this as I feel this is unscalable solution, but with that right comes the responsibility. If you or other community developers are unwilling to hold yourselves to the same responsibility that every engineer of the Foundation is held to, you are free to do so. But nobody has the right to have +2, nobody has the right to shell access, etc. Just as Platform and Ops reserve the right as policy to rescind my +2 access and my non-existent shell access, they could rescind anyone else's, even yours if it existed.
+  
+
+(In reply to comment #38)
+
+> > The requirement for extensions to be deployed has ALWAYS been that Features
+> > Engineering sign off on a commitment to maintain the extension.
+> 
+> This isn't consistent with the documentation at [[mw:Writing an extension for
+> deployment]], [[mw:Review queue]] and Greg's checklist in comment 7.
+
+Interesting links.
+
+To the first document which has its origins in the SVN days, the first stop with Howie Fung and his product management team. To my knowledge the only person asked was a Dan Garry, and not as a first stop on anything. I mentioned in my original post why that people should know better. The second stop was wikitech-l. To my knowledge mine was the first post on the subject.
+
+The second document is newly written by Platform not vetted by anyone in Features. I assume that if Platform wants to operate that way then they're committed to maintaining an extension approved that that process, that's cool with me and entirely consistent to my statements. In it's original incarnation it was Sumana's way of managing code review of existing extensions.
+
+The third link refers to someone who has been at the WMF even less time than me. If we're to use MZMcBrides seniority rules, the fact that some newly-minted, improperly vetted document was used by a relatively new engineer doesn't carry weight.
+
+I hope that documentation is updated.",1380853822,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #37)
+> Is the current thinking to give users on any wiki the right to use
+> Special:MassMessage to spam users on any other wiki?
+
+Yes. The design idea here was that this is already possibly by any user. Anyone can open up a bunch of browser tabs and post to dozens of wikis quickly without even logging in. Or, for example, I've been posting to hundreds of wikis for years without a privileged account using only a very simple Python script. The difference here in functionality isn't very big. The primary difference is that we're adding a proper user interface for delivery submissions and reducing the need for an external dependency (a bot).
+
+> It seems to me you'd want something like:
+> 
+> * Users on Meta can trigger cross-wiki notifications;
+> * Users on any other wiki can only trigger local notifications.
+
+This was considered and it's probably easy enough to implement these restrictions, but as I said above, I'm not sure they're necessary. My view was to take a ""wait and see"" approach. If local administrators begin to abuse or misuse the tool, we can always add in restrictions later.
+
+> Otherwise you end up with an audit trail mess. Having a single log in one
+> place and a single place to set policy around these things seems highly
+> desirable.
+
+Again, anyone can go around posting messages to any wiki right now without even logging in. Giving local administrators the ability to send cross-wiki messages with a simpler tool doesn't seem to warrant much concern from my perspective, but if you consider this a requirement for wider deployment, Lego can add in the restrictions.
+
+The bot currently provides an audit trail by (optionally?) appending an HTML comment containing the originating wiki, message sender's name, etc., I believe. Lego can confirm this.",1380853667,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #35)
+> Ori has stepped up and is willing to commit his time to help Legoktm in
+> supporting MassMessage on an ongoing basis. According to the current standard
+> of the above, there is no longer any block on bug 52723.
+
+Thank you Ori!
+
+> The requirement for extensions to be deployed has ALWAYS been that Features
+> Engineering sign off on a commitment to maintain the extension.
+
+This isn't consistent with the documentation at [[mw:Writing an extension for deployment]], [[mw:Review queue]] and Greg's checklist in comment 7.",1380853061,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Is the current thinking to give users on any wiki the right to use Special:MassMessage to spam users on any other wiki?
+
+It seems to me you'd want something like:
+
+* Users on Meta can trigger cross-wiki notifications;
+* Users on any other wiki can only trigger local notifications.
+
+Otherwise you end up with an audit trail mess. Having a single log in one place and a single place to set policy around these things seems highly desirable. If we're on the same page on that, I'm significantly less concerned about the long term impact of the extension.",1380852890,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #35)
+> The requirement for extensions to be deployed has ALWAYS been that Features
+> Engineering sign off on a commitment to maintain the extension.
+
+You've been at the Wikimedia Foundation for, what, two years? You really feel it's appropriate to lecture me and others about how things have ""always"" been? You seem to have absolutely no sense of how software deployments have operated for the majority of Wikimedia's existence.
+
+You're attempting to dictate to volunteers as though they're your subordinates. This is wildly inappropriate.
+
+Do you have a link to this doctrine regarding software deployments and sign-offs? As far as I can tell, you've just made it up here on this bug. But perhaps there's a guideline you've written on mediawiki.org, wikitech.wikimedia.org, or Meta-Wiki. Please share.",1380851998,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+Ori has stepped up and is willing to commit his time to help Legoktm in supporting MassMessage on an ongoing basis. According to the current standard of the above, there is no longer any block on bug 52723.
+
+Time still has to be made to handle the rollout, but I'm assuming what is already in-process in Platform, and Ori can assist beyond that.
+
+The requirement for extensions to be deployed has ALWAYS been that Features
+Engineering sign off on a commitment to maintain the extension. I've relaxed it
+to be: ""If another engineering department in collaboration with product is
+willing to commit to it, Features will not block."" I'd like to someday relax
+this further to: ""If any engineering department or community development in
+collaboration with the other core competencies (features, product, design, and
+community) are willing to commit to it, no one should block."" We are not there
+yet, and trying to rail against that is winning a battle at the cost of the war
+breaking down these silos and having shared ownership and responsibility in our
+organization, in our community, and in our movement.
+
+Please realize the current state of affairs is that new Extension deploy can be done under the following frameworks:
+
+1) The traditional ""Features signs off on all extensions"" that has always been in place. For Features to sign off on this, like with our own engineering staff, we require collaboration and buy-in in affected areas like the product managers and designers who will lose productivity or might be retasked on this. We must be good stewards of each-others times, and I would not have permitted (and will not permit) my engineers to task Platform and Design engineers for MassMessage in the manner that has happened to date (water under the bridge at this point).
+2) The above can and has been be bypassed on a directive from the VPE as was the case for BetaFeatures.
+3) Like LanguageEngineering's use of TranslationNotifications instead of Echo, if another team consisting of engineering, product, and design is willing to commit to supporting on an ongoing basis, then extension deploy proceeds without the traditional rule of discussing Features. Note, in this example we have an assumption that the feature set of MassMessage is as-is so it currently doesn't involve Product or Design, nor does it require more engineering resources inside the WMF beyond Ori who is currently untasked.
+
+We still eventually want to reach the point where the criteria is not the amalgam of rules above but a simpler one based on intent, expertise-sharing and consensus-building: ""If any engineering department or community developer in collaboration with the other core competencies (engineering, product, design, and community) are willing to commit to ongoing maintenance of a feature, then no one group should block it.""
+
+We haven't reached there yet, and please realize that when me make exceptions as in this case, it compromises the larger picture of our need to break down these silos and create shared ownership and responsibility in the WMF, in our communities, and in the movement as a whole.",1380851471,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+(In reply to comment #33)
+
+> This comparison carries no value: 1) LQT can't be undeployed because we'd
+> lose
+> critical data (discussions) from the wiki, 2) AFT is being expanded right now
+> with no exit strategy I'm aware of (probably under the understanding that
+> nobody cares if all that data disappears from the wikis after undeployment).
+
+It carries more value that bug 31235 does to implement bug 52723. MassMessage is an extension, as an extension it is under the same rules as all other extensions for deployment.
+
+1) LQT can't be underplayed and we're stuck with it for an uncertainf eatures
+2) ReaderFeedback, AFT, and AFTv5 are all different extensions.
+
+> I highly doubt I do. My sentence started with an ""If"" for a reason: I've no
+> idea who's responsible for Echo.
+
+Then I apologize, it's easy to read your statement and not have the hidden assumption that someone is responsible for Echo. Nobody is, it, like everything else, is a shared responsibility.
+
+> Let me note that I asked how you planned to coordinate with other pieces of
+> code/devs working in this area already 9 months ago: [[m:IRC office
+> hours/2013-01-08]].
+
+Hmm, I didn't read what you said as being related to this, most of what was in that discussion was posted on the grandparent bug and little movement has been done since then.
+
+As to your logs: currently there is only one Dev working on Echo: bsitu. RoanKattouw and matthiasmullie never got the chance to work on this project, lwelling is no longer with us, Krenair is a community dev who I assume is wrapped up in other issues with core, kaldari is now in Mobile, fabriceflorin is in Multimedia and Werdna is on Flow. I don't know the state of [[mw:Extension:TranslationNotifications]] but I believe it's under active development/maintenance by Language Engineering. Their contributions are in this log, on mediawiki, in the code base, and in fabriceflorin's notes. When work on Echo is restarted, bsitu will be involved in it.
+
+
+> I gather that you feel insulted and circumvented or something like that and
+> I'm
+> sorry for this personal pain you're suffering, but all this talk about
+> exploiting doesn't look helpful.
+
+I'm not insulted. I pushed back one time in a close-door meeting (I prevented deployment on mediawiki.org with the understanding from all the participants of the meeting that MassMessage would not be deployed on the cluster). Since people aren't aware of it, I am trying to explain the decision and the reasoning behind it.
+
+I apologize for this language of ""exploiting."" Here was the topline of my original discussion which is relevant (but deleted from the bug comment):
+
+> When I use to loaded words like ""back-dooring"" etc, I believe that no malice was intended and the discussions so far have been in good faith from all parties. I think people have a valid concern and want it addressed and are wondering honestly how decisions have been made. In particular, my decision to not allow the MassMessage Extension to roll out onto MediaWiki last week, since that occurred during a meeting that didn't even involve or derive have consultation (except ex-post-facto) with any product manager or engineer here.
+
+It is very likely that adding the previous deploy and this one to the deploy calendar on Thursday would have someone like me either missing it or taking it at face value (that someone outside my own team added it and has adopted responsibility).
+
+Last week, I didn't have time to figure out the parameters of where the decision to deploy MassMessage came from, so I only pushed back on mediawiki.org. The understanding from me and all the participants of the Friday meeting was that MassMessage would not be deployed beyond that.
+
+The fact is at that moment this spent all of one day on the deploy calendar added by someone outside the WMF, one and a half weeks in public development on obscure parts of the wiki and bugzilla, had no discussion with product, no plan for support, etc.
+
+No new feature would have been deployed to even test or test2 without discussions from Features, Design and Product. I didn't realize that any of this had occurred.
+
+This is not a standard anymore for deployment of an extension, nor has it been for quite a while.
+
+> This is not a reply to my line you quoted.
+
+Hmm, I feel it is but I guess this depends on the definition of what is is? :-)
+
+If it is unreasonable to require sign off for Features Engineering for Extension deploy than it is an unreasonable thing that has been in place long before me. I'm trying to relax that requirement, one area of relaxing is to find another home for deployment and support.
+
+Last year, there was a broken core change about timestamping slipped through Platform review and got deployed. Because of that, a better thought-out and previously-developed pending core change for the exact same feature from Werdna got bumped. To get this fixed,the Echo team had to make a new core patch that superseded the earlier, broken patch, satisfied Language Engineering's wishlist, and handled what Echo needed which took weeks of effort and time that wasn't necessary had the timestamp patch not been put into core in the first place.
+
+It was unreasonable, but it was life.
+
+We can operate on the old rules of ""Features Engineering needs to sign on support for Extension wide cluster deploy"" or we cannot.
+
+Under the former, Features's answer is not no. Our answer is We need to hear something more urgent and important or my answer is not yet from Features. Everything WMF Features Engineering does is in collaboration with other areas: product, design, design, and community, and I refuse to allow me or my teams to operate differently.
+
+Under the latter, support for this needs to find another home just like TranslationNotifications or BetaFeatures did.
+
+Someday, I hope we can do better. Things like BetaFeatures and Workflows part of Flow may make that possible.",1380845232,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"I don't want to monopolise the discussion so I'll briefly reply to some ""personal points"".
+
+(In reply to comment #32)
+> > This appears to be a false problem. If Echo or something else in a future
+> > provides equivalent or better features, the extension will fall into disuse
+> > and/or it can be undeployed.
+> 
+> That argument may have held water back when extensions like ReaderFeedback or
+> LiquidThreads were written and deployed. 
+
+This comparison carries no value: 1) LQT can't be undeployed because we'd lose critical data (discussions) from the wiki, 2) AFT is being expanded right now with no exit strategy I'm aware of (probably under the understanding that nobody cares if all that data disappears from the wikis after undeployment).
+
+> [...]
+> 
+> > I don't get these points. If you're responsible for Echo, it's your
+> > responsibility to decide what Echo is going to incorporate, it's not the
+> > others' responsibility to guess it and be blocked for years while you figure
+> > it
+> > out.
+> 
+> I'm responsible for ENGINEERING RESOURCING on Echo. [...]
+> 
+> You have a misguided view of what I do or what works in general in our
+> movement
+> or at the WMF.
+
+I highly doubt I do. My sentence started with an ""If"" for a reason: I've no idea who's responsible for Echo.
+
+Let me note that I asked how you planned to coordinate with other pieces of code/devs working in this area already 9 months ago: [[m:IRC office hours/2013-01-08]].
+
+> [...] I'm asking that while I agree (and I think most would) that it'd be nice to
+> have movement on the parent bug, people stop trying to exploit known holes in
+> our development processes to try to get a particular implementation that is
+> not
+> derived from consensus and has bypassed every standard erected to safeguard
+> sustainable development at the WMF: either work within the system or don't
+> but
+> don't try to get something deployed and say it's Features' problem because
+> it's
+> an extension. This sort of behavior breaks down trust in our people and
+> processes many of whom and which are new, fragile,and need to be nurtured,
+> not
+> exploited.
+
+I gather that you feel insulted and circumvented or something like that and I'm sorry for this personal pain you're suffering, but all this talk about exploiting doesn't look helpful.
+
+> [...]
+> > > The above can occur independently or in parallel to the above. If Product
+> > > thinks it cool to commit Platform's constrained engineering resources to
+> > > [...] use it to take
+> > > advantage of Echo when the features roll out in some undefined future,
+> > 
+> > this looks like an unreasonable requirement
+> 
+> The requirement for extensions to be deployed has ALWAYS been that Features
+> Engineering sign off on a commitment to maintain the extension. [...]
+
+This is not a reply to my line you quoted.",1380838994,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+(In reply to comment #30)
+> (In reply to comment #28)
+> > bug 52723 is a recent bug to deploy Legoktm's MassMessage extension as a
+> > solution to bug 35306, it is less than a month old there has been little
+> > public
+> > discussion [...]
+> 
+> For your following points, it seems you're implying that the desiderata and
+> requirements for this extension are not clear. This couldn't be less true[edit]:
+> the
+> requirements are to take over EdwardsBot (a successful product) in the least
+> impactful way possible.
+
+bug 52723 on its own is clear, but as a solution to bug 35306, it is not. If we actually want to solve bug 35306 in an ideal world, nobody would use 52723, nor would Platform resources have been spent on 52723.
+
+For instance, what is the timescale necessary before EdwardsBot is unworkable? Has it failed immediately or is failure immanent? If not, why then the rush on bug 52723? If so, then we need to discuss what to do of which bug 52723 is the only option right now. No other extension in recent memory has been deployed on the cluster with so little public discussion, without any product approvals, without any commitment from Features for maintenance.
+
+> > The problem with moving on bug 52723 as a solution to bug 35306 is it commits
+> > Features Engineering to maintaining an extension that is a stop gap solution
+> > with no or very little discussion in a manner that doesn't serve a broad
+> > strategic goal about how messages, notifications, etc. should be handled on
+> > the
+> > wikis. [...]
+> 
+> This appears to be a false problem. If Echo or something else in a future
+> provides equivalent or better features, the extension will fall into disuse
+> and/or it can be undeployed.
+
+That argument may have held water back when extensions like ReaderFeedback or LiquidThreads were written and deployed. We still have those extensions cluttering the cluster with no serious commitment to support, no easy avenue for sunsetting. Unlike that time, we now real product and development processes in place. Those processes should be given a chance to work before being bypassed.
+
+It would be unfair to every engineer here and all extensions written if the old standard of, ""If something better comes along, this will die naturally"" is applied in this case barring some emergency. That standard hasn't been applied during my tenure here and I'm not going to make an exception just because Platform's checklist for covers core deployments has been gamed to cover a new extension deployment that would not reached this stage and would have received an reprimand from me (wasting Platform's resources) had my own engineers done this.
+
+While MassMessage is replacing or superseding current site functionality, this is this isn't improving or superseding a current (neglected) extension. For instance, the community-initiated work being done on the Math Extension (which I might had has had infinitely more discussion on wikitech-l) because this site functionality  If anything, the inability of Features Engineering to review and maintain the current deployed extensions should make the case against MassMessage adding to that balance sheet already deeply in the red.
+
+The simple reality is that Features Engineering will not support the MassMessage Extension as is. But if a different department like Platform Engineering is actually committed to supporting it indefinitely, I'll cede the ground entirely. I did the same to Language Engineering with Translation Notifications. This time, I'd recommend discussion with others how that experience has worked out (I don't know myself, because Feature ceded responsibility here).
+
+> > [...] After discussion during that Friday
+> > meeting among the EPMs, I compromised to let it to go out on two test wikis,
+> > but not on mediawiki. Nobody made the case that it should go out on
+> > mediawiki.
+> 
+> AFAIK, this is a MediaWiki extension. Do you mean ""not on mediawiki.org""?
+
+Yes, sorry. I meant the mediawiki.org. You can see the context of my use of mediawiki by itself from the change history I linked to above.
+
+> I don't get these points. If you're responsible for Echo, it's your
+> responsibility to decide what Echo is going to incorporate, it's not the
+> others' responsibility to guess it and be blocked for years while you figure
+> it
+> out.
+
+I'm responsible for ENGINEERING RESOURCING on Echo. Right now a full-time engineer has been devoting his full time in supporting a product that is ""done"" simply because the rollout hasn't yet happened on all the wikis. If I want to commit more time developing enhancements to it, I have to take that resource from somewhere else like VisualEditor or Flow. Because it affects those teams, I'd negotiate with the product managers on that time. In addition, I'm okay with being ordered to change that current level or resourcing by Erik, Sue, or the Board, but until then I make the resourcing decision based on my responsibility toward achieving the Annual Plan, the Strategy, and other commitments we've made.
+
+You have a misguided view of what I do or what works in general in our movement or at the WMF. What or what-not Echo incorporates, like all decisions of this nature, are not mine alone but the responsibility of Product Design in discussion with me, my teams, and others. When it comes to Echo specifically, because I have the least domain knowledge on the team, I have the least contribution and thus the least authority to do beyond a suggestion. This is a Good Thing. We should be good stewards of each others time and energy and not commit others without discussion with them.
+
+I have a lot of stuff I'd like to do and I'd like to promie, but I agree to abide by this framework and expect my teams to do the same. I make and enforce the rules with respect to Features Engineering, but I do not make all the decisions for the features, or even the most relevant ones in this matter.
+
+> Are you saying you're going to figure it out so that people can
+> understand
+> how to work with/for Echo without being just blocked by it?
+
+I am saying, ""Here is an approach we can take. I realize that it's a 3-6 month to 1 year thing, but so is everything else we've done. If you've held off for almost 2 years, can you hold off a bit longer? This approach can be done orthogonal to other approaches (like this bug), but the important thing to be is consistent so we avoid things (like ad-hoc extension deployments) that we know haven't worked in the past.""
+
+I'm saying if you can't be blocked by this bug and need Features to support it, then either go without Features or state reasons other than ""it's been in bugzilla for almost 2 years"" because that has never been a standard to get stuff fixed and deployed.
+
+I'm asking that while I agree (and I think most would) that it'd be nice to have movement on the parent bug, people stop trying to exploit known holes in our development processes to try to get a particular implementation that is not derived from consensus and has bypassed every standard erected to safeguard sustainable development at the WMF: either work within the system or don't but don't try to get something deployed and say it's Features' problem because it's an extension. This sort of behavior breaks down trust in our people and processes many of whom and which are new, fragile,and need to be nurtured, not exploited.
+
+For instance, BetaFeatures was shopped around long before MassMessage, bypassing Features Engineering. They got a bite in Multimedia and Mobile and now Multimedia wants to deploy this and move on to work on… Multimedia and is in a spot with respect to support for this extension. Part of me wants to say, ""Well you knew this was going to happen, why didn't you involve the rest of Product and Features before you got to this point?"" And that's for an extension that had far more buy-in, development, design, and direction (from the VP level even), and isn't even deployed yet!
+
+It is for exactly sort of situations that the consensus and discussions with product, design, and features is a standard for all new features in the first place. When this rule is bent as in the case of BetaFeatures, it causes problems which the people who took it on understood would come as a consequence. When this rule isn't even followed, as in the case of MassMessage, Features opts-out, but another department is welcome to take this on.
+
+> > The above can occur independently or in parallel to the above. If Product
+> > thinks it cool to commit Platform's constrained engineering resources to
+> > deploying and supporting MassMessage Extension forever 
+> 
+> This is one thing,
+> 
+> > and use it to take
+> > advantage of Echo when the features roll out in some undefined future,
+> 
+> this looks like an unreasonable requirement
+
+The requirement for extensions to be deployed has ALWAYS been that Features Engineering sign off on a commitment to maintain the extension. I've relaxed it to be: ""If another engineering department in collaboration with product is willing to commit to it, Features will not block."" I'd like to someday relax this further to: ""If any engineering department or community development in collaboration with the other core competencies (features, product, design, and community) are willing to commit to it, no one should block."" We are not there yet, and trying to rail against that is winning a battle at the cost of the war breaking down these silos and having shared ownership and responsibility in our organization, in our community, and in our movement.
+
+> (are you going to shutdown
+> message
+> bots too if they don't use Echo?).
+
+No. Message bots are not Extensions. I think the criteria to move EdwardsBot into ToolLabs is different. If MZMcBride would like assistance on this, I think the engineering community team and operations will offer it.
+
+Personally, I (and I assume you) would like a solution beyond and more sustainable than saddling MZ and EdwardsBot with more work. The original bug points out that much of the Wikimedia Foundation is dependent on MZ's bot. If MassMessage Extension is the only option or is an emergency option, so be it — people have shortcutted processes before and have had to live with the consequences.
+
+Otherwise, we need to have that discussion in front of all of WMF Tech, on Wikitech-l in front of the mediawiki community, and in front of the C-levels and the board as part of the annual plan, not just on this bug.",1380837927,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,*couldn't be less true,1380829988,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #28)
+> bug 52723 is a recent bug to deploy Legoktm's MassMessage extension as a
+> solution to bug 35306, it is less than a month old there has been little
+> public
+> discussion [...]
+
+For your following points, it seems you're implying that the desiderata and requirements for this extension are not clear. This couldn't be less clear: the requirements are to take over EdwardsBot (a successful product) in the least impactful way possible.
+
+> 
+> The problem with moving on bug 52723 as a solution to bug 35306 is it commits
+> Features Engineering to maintaining an extension that is a stop gap solution
+> with no or very little discussion in a manner that doesn't serve a broad
+> strategic goal about how messages, notifications, etc. should be handled on
+> the
+> wikis. [...]
+
+This appears to be a false problem. If Echo or something else in a future provides equivalent or better features, the extension will fall into disuse and/or it can be undeployed.
+
+> [...] After discussion during that Friday
+> meeting among the EPMs, I compromised to let it to go out on two test wikis,
+> but not on mediawiki. Nobody made the case that it should go out on
+> mediawiki.
+
+AFAIK, this is a MediaWiki extension. Do you mean ""not on mediawiki.org""?
+
+> [...]
+> 
+> For example, features in MassMessage and EdwardsBot need to be addressed in a
+> Must-Have, Should-Have, Could-Have, Won't-Have (MoSCoW) framework. 
+
+Isn't this what dependencies are for? I see one dependency and it's fixed.
+
+> [...]
+> 
+> 1) wait for some things to happen: legoktm to get an RfP, Echo to be on all
+> wikis, and Benny to do an entire Flow only sprint and balancing his time more
+> effectively wrt Echo.
+
+I don't understand how keeping to use a bot for the very same things this extension would do helps Echo.
+
+> 2) MoSCoW other features of MassMessage/EdwardsBot for integration into Echo
+> 3) Enhance and deploy a first pass to Echo to allow some sort of mass
+> notification from a wiki list
+> 4) Some sort of cross wiki notification enhancement (requires a design pass)
+> 5) Discuss how to implement must-have or should-have features of EdwardsBot
+> that can't live in Echo (permanent log of events)?
+> 6) Add those to plan and be done.
+
+I don't get these points. If you're responsible for Echo, it's your responsibility to decide what Echo is going to incorporate, it's not the others' responsibility to guess it and be blocked for years while you figure it out. Are you saying you're going to figure it out so that people can understand how to work with/for Echo without being just blocked by it?
+
+> The above can occur independently or in parallel to the above. If Product
+> thinks it cool to commit Platform's constrained engineering resources to
+> deploying and supporting MassMessage Extension forever 
+
+This is one thing,
+
+> and use it to take
+> advantage of Echo when the features roll out in some undefined future,
+
+this looks like an unreasonable requirement (are you going to shutdown message bots too if they don't use Echo?).",1380829865,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+I am not modifying this bug, to leave open the avenue that Platform Engineering commits to supporting [[mw:Extension:MassMessage]], only bug 35306.",1380828245,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+We have two separate but related bugs here: 
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=35306
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52723
+
+bug 35306 is an tracking bug MZMcBride posted for a solution to deal with EdwardsBot. I believe it dates to around the time I was first employed almost two years ago.
+
+bug 52723 is a recent bug to deploy Legoktm's MassMessage extension as a solution to bug 35306, it is less than a month old there has been little public discussion, and until it appeared on the deploy calendar last week, I wasn't even aware of its existence.
+
+The problem with moving on bug 52723 as a solution to bug 35306 is it commits Features Engineering to maintaining an extension that is a stop gap solution with no or very little discussion in a manner that doesn't serve a broad strategic goal about how messages, notifications, etc. should be handled on the wikis. To the first, maybe there is something wrong with my e-mail client, but I have yet to find this discussion on wikitech-l or anywhere outside the bug.
+
+Because of the above, my view is that this solution is being back-doored in and just moves the ""technical debt"" from one sheet (the community and tool labs) to another that has even less capability. I am biased against that because the latter sheet (WMF Features Engineering) is my responsibility. This is just my view, I'm open for us coming to consensus on a solution for this bug, but what I have seen is not consensus.
+
+It is along these lines that, I asked to remove MassMessage from the deploy calendar when it was added to the deploy calendar without discussion from Features, Design, or Product last week. After discussion during that Friday meeting among the EPMs, I compromised to let it to go out on two test wikis, but not on mediawiki. Nobody made the case that it should go out on mediawiki. I demurred because no person at the WMF, including me as Director of Features Engineering, should fiat a decision when unaware of the status of discussions involved.
+
+But let frank: if this had been a WMF employee writing this extension, it wouldn't have made it to even the test wikis by a country mile. In fact, a lot of extensions have been written by employees and either have extensive discussion, review, and buy-in (e.g. GuidedTours), or have not been deployed (e.g. Etherpad, the org chart, BetaFeatures) even though much more work has been done on them.
+
+I also don't like that WMF resources in Platform and Design are being spent to review something that has had no adequate discussion over in the annual plan, in anyone's 20% time, in any cross-team discussion, or public discussion on wikitech-l (There was a last minute thread in the Design list, I am not on the design list, nor should I be, and the Creative Director is new and the team is just trying to get their sea legs and some consideration to that needs to be done here). Furthermore, after further discussion, nearly all of Product felt I should not have compromised earlier because the following situation might occur: Having gotten it onto ""the cluster"" people would then move to back-door it into deployment on the basis that it's already on the cluster. Their prediction is occurring right now. This is a bogus argument because nobody agreed this should be on the cluster, it's just that nobody has reviewed it in a thorough enough manner to shout ""NO!""
+
+If necessary, I'm going to shout ""NO!"" at this moment.
+
+Having said that, there is the larger issue of bug 35306 which has been sitting there unsolved for a while as well as the smaller issue of the month's work Legoktm and MZMcBride have already put into Bug 52723 and [[mw:Extension:MassMessage]] possibly going to waste if I keep blocking it. Besides, MZ is sitting there trying to hold everything up on his own shoulders with EdwardsBot, and we all know it.
+
+…
+
+Let me address the functionality overlap with Echo:
+
+LanguageEngineering built their own parallel message/notification system before Echo that lives on Meta today. They commit to supporting their own parallel message/notification system, and I'm okay with it living outside Echo (where it currently does), but there is an understanding that they've basically committed to that work with no support from Features for the duration that it does live outside Echo.
+
+In those lines, I'm glad that Platform has helped out here, but unless Platform is committing to support MassMessage indefinitely into the future and not just provide one-time security and deploy assistance, I'm not okay with them adding to Features work even though they've been super helpful to MZMcBride and Legoktm. If Dan Garry is willing to commit Platform to support MassMessage, I'll think the same precedent we've done with LE applies here.
+
+Furthermore, before *in-echo, outside-echo, use-echo) for a solution to be bug 35306, it needs to actually exhibit product discipline. The WMF gets panned for having a ""agile processes"" but not actually doing so, but we do have some process and we need to at least apply the same product discipline that we apply everywhere else to this bug.
+
+For example, features in MassMessage and EdwardsBot need to be addressed in a Must-Have, Should-Have, Could-Have, Won't-Have (MoSCoW) framework. Features like ""mass delivery from a list"" are probably a Must-Have; features like ""cross-wiki notification"" are probably a should-have, other features like ""public over private notifications"", ""page-centric over user-centric"" or ""longer stream notifications"" are either not a must-have or could have or are should-haves to  be done outside Echo by a different service (bot) using the Echo API or some extension thereof. All that is a product issue, and I nor anyone in my team is in product. Those decisions should be done in discussion with the Product team and they should not be disintermediated from it, which they have been.
+
+I understand that many people would like to see a solution to Bug 35306 would be great to have. I'd like to see a better Signpost notification system and a more generalized solution for newsletter delivery also! I'd also like a pony. But we have already committed resources and continue to commit resources without discussion from the people (Product Design, not Features Engineering) who have been tasked with this responsibility and are very good at these sort of thing. I hope everyone participating on this bug can see that dropping this bomb on a newly hired associate product manager is simply not cool on so many levels.
+
+…
+
+Here is my suggestion:
+
+(This is thinking, not a directive so don't think of this as definitive or final, I'm seeking consensus here.)
+
+First, bug 35306 is a long-standing request. I think it's important we get headway on this, but I hope others will be understanding if it doesn't happen immediately, so long as there is a commitment for this to happen.
+
+(For perspective, Flow was first proposed years ago, and was added to the annual plan almost two years ago before their first actual development sprint was completed (end of this week!). Echo was first deployed almost 8 months ago and is still not out on all the wikis. BetaFeatures has been in discussion for months and is still not deployed, nor is the commitment to maintain inside Features and that has caused a lot of issues. Fixing things right right takes time because consensus takes time and open discussion.)
+
+There is an RfP for student developer time for legoktm for things like this (Finding a solution for Bug 35306 but not [[mw:Extension:MassMessage]] because MassMessage would not be deployed if it was my own engineer). Benny Situ has been spending all his time supporting [[mw:Extension:Echo]] when he should balancing [[mw:Flow]] development time into Echo bug fixes and needs to spend at least one sprint (two weeks) solely getting up to speed on Flow before doing enhancements for [[wm:Echo]]. Furthermore, Echo is not deployed everywhere yet and is still rolling out (though I've been pushing up the timetable on this as I feel we're too slow here), so it can't reach the places that EdwardsBot cat.
+
+After the above happen, I'd like Benny and Kunal to work together to add some of the functionality of EdwardsBot into Echo for mass message delivery. Because of this, I'm moving bug 35306 into Echo as an enhancement and raising it's priority.
+
+In the meantime I'll be OK with leaving MassMessage on test and test2 wikis because the alternative would be to remove it from the cluster entirely. The experiences and code Kunal derives by that can inform the enhancement to Echo, as well as things it already does that find themselves outside Echo (Echo does not and should not post to talk pages). So I figure two stages:
+
+1) wait for some things to happen: legoktm to get an RfP, Echo to be on all wikis, and Benny to do an entire Flow only sprint and balancing his time more effectively wrt Echo.
+2) MoSCoW other features of MassMessage/EdwardsBot for integration into Echo
+3) Enhance and deploy a first pass to Echo to allow some sort of mass notification from a wiki list
+4) Some sort of cross wiki notification enhancement (requires a design pass)
+5) Discuss how to implement must-have or should-have features of EdwardsBot that can't live in Echo (permanent log of events)?
+6) Add those to plan and be done.
+
+The above can occur independently or in parallel to the above. If Product thinks it cool to commit Platform's constrained engineering resources to deploying and supporting MassMessage Extension forever and use it to take advantage of Echo when the features roll out in some undefined future, consider this thinking moot or at least orthogonal to MassMessage. IMO, it is bad enough that something important like BetaFeatures is without a home, but my answer from Features is ""No"" for MassMessage. If this was my own engineer, I'd raise hell with them for this and yell at their Product Manager for not being a good steward of Platform's time.",1380828181,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"As someone that has discussed the topic of mass notifications / announcements / newsletters with many people I agree with the approach being proposed here:
+
+* MassMessage solves a problem here and now by deprecating EdwardsBotwith a better solution.
+
+* There is a possibility to integrate an Echo plugin to MM in the future, but this is no blocker for a deployment to Wikimedia wikis now.
+
+* There are other future possibilities around announcements / newsletters in the future, in the lines proposed at https://www.mediawiki.org/wiki/Extension:Newsletter#Wishlist and MassMessages might or might not be a good project to handle this, but again this is no obstacle for a deployment now.",1380730233,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #25)
+> There is some overlap with Echo with this. 
+In general, yes. Both extensions provide a 'notification' functionality, however there are some pretty big differences as well.
+
+1) Echo notifications for the most part are private; only you can see your Echo notifications. MM is designed so that everything (target list, message content) is fully public.
+
+2) Echo is centered around users, given that you can only send notifications to users. MM can send to basically any page, which is necessary for global message delivery (most messages are sent to village pumps, not users directly).
+
+3) Echo notifications are quick short messages that usually are just a link to something else. In many cases, EdwardsBot delivers the whole message to your talk page (example: <https://en.wikipedia.org/?diff=prev&oldid=565236352>). In this regard MM has been designed so that the end user receiving the message would not see any difference.
+
+(In reply to comment #25)
+> if we enable this extension we could always disable it should
+> Echo supersede it.
+
+I don't think merging MM into Echo is a good idea. Rather, MM should use Echo notifications instead of talk page ones if $wgMMUseEcho is enabled. Or something like that...",1380729349,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"There is some overlap with Echo with this. On the other hand, there are some things that this might be suited for, such as the delivery of the Wikipedia Signpost. It's my view that an in-built solution to replace EdwardsBot would be useful, and if we enable this extension we could always disable it should Echo supersede it.
+
+I'm CCing Fabrice Florin, the product manager for notifications, to see if he has any input.",1380726099,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #19)
+> Mostly, I brought this (deploying MassMessage) up in a Deployment updates
+> meeting, and there was some push back from a product view. In short:
+> ""shouldn't this functionality be built into something like Echo?"" So, I won't
+> go around them and deploy MassMessage everywhere until that conversation is
+> settled (for some value of ""settled"").
+
+I'm still awaiting feedback from Terry, Howie, or Fabrice on bug 35306 (I also e-mailed them yesterday with a pointer to the bug), however Lego pointed out to me that Echo doesn't currently support cross-wiki notifications, so Echo integration is probably completely off the table for now.
+
+I think a month of testing is sufficient for this extension, so I've tentatively scheduled a deployment to all Wikimedia wikis for the end of October (cf. <https://wikitech.wikimedia.org/w/index.php?diff=84903&oldid=84888#Near_term>). You know the calendar much better than me, though, so let me know if that's a particularly bad time for whatever reason.",1380680719,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #22)
+
+Hah! I just came here to write pretty much the same comment. Brilliant. Thank you, Lego.
+
+Testing is underway (cf. [[testwiki:Special:Log/massmessage]]) and feedback has started to come in (cf. [[m:Talk:MassMessage]]).",1380652159,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Some updates:
+
+MassMessage was successfully deployed to test and test2 today (thanks Reedy!). I did a few simple tests making sure everything worked fine (https://test.wikipedia.org/w/index.php?title=Special%3ALog&type=massmessage&user=Legoktm&page=&year=&month=-1&tagfilter=&hide_patrol_log=1&hide_review_log=1&hide_thanks_log=1)
+
+MZMcBride has sent out a message to people who currently use EdwardsBot on enwiki and meta asking them to test it on testwiki and provide feedback (https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Spam&oldid=5895864).
+
+We're still waiting on comments from Fabrice/Howie/Terry (bug 35306 comment 20).
+
+[[mw:Help:Extension:MassMessage]] has documentation on how an administrator would use the special page to send out a message. [[m:MassMessage]] has also been created.",1380607500,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"After a couple of updates, it all looks ok from the security side.",1380131839,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Err, I mean, after Chris S gives the all clear, security-review-wise: https://bugzilla.wikimedia.org/show_bug.cgi?id=52723#c16",1380044491,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #18)
+> (In reply to comment #17)
+> > There was a request to see if this extension would make sense as an
+> > improvement to Notifications/Echo. This discussion would probably be good to
+> > have with the WMF product team (maybe including Fabrice, Terry, and Howie).
+> 
+> This already took place at bug 35306.
+
+Right, so, I'm deferring judgement on that (and related) conversations to Terry C and Howie F right now. More on why below...
+
+> > I'll default to defer for now, until that conversation happens.
+> 
+> I don't know what this means. Can you clarify?
+
+Mostly, I brought this (deploying MassMessage) up in a Deployment updates meeting, and there was some push back from a product view. In short: ""shouldn't this functionality be built into something like Echo?"" So, I won't go around them and deploy MassMessage everywhere until that conversation is settled (for some value of ""settled"").
+
+Now, what we should do is deploy MassMessage somewhere so you/others can test its functionality on a WMF production-like site. Let's get this out to test2.wikipedia this Thursday. Filed bug 54518 for that.",1380044416,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #17)
+> There was a request to see if this extension would make sense as an
+> improvement to Notifications/Echo. This discussion would probably be good to
+> have with the WMF product team (maybe including Fabrice, Terry, and Howie).
+
+This already took place at bug 35306.
+
+> I'll default to defer for now, until that conversation happens.
+
+I don't know what this means. Can you clarify?",1379779756,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"There was a request to see if this extension would make sense as an improvement to Notifications/Echo. This discussion would probably be good to have with the WMF product team (maybe including Fabrice, Terry, and Howie).
+
+I'll default to defer for now, until that conversation happens.",1379703587,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Just an update, I'm still working on the review. There were a few bits that looked odd as I was testing, so I'd like to dig into those before giving the all clear. Should be able to get that finished on Monday.",1379649523,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"I just spent a few minutes talking with Chris who said he would be able to do a security review of the extension this week.
+
+Currently waiting for a few patches to be reviewed and then I'll send an email to wikitech-l.",1379462355,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #11)
+> (In reply to comment #9)
+> >> Not sure this is relevant as this extension isn't really user-facing, but if
+> >> you want to find someone to review the design, go for it.
+> > 
+> > Well, for some definition of user, right? It has sysop user facing UI. For a
+> > design review, the Design mailing list is a good place to start (and then
+> > ping until success).
+> 
+> Lego: please go ahead and e-mail the design mailing list (include a working
+> demo of the tool, of course). If they have constructive feedback, wonderful.
+> Otherwise, I don't consider this a blocker to deployment.
+> 
+
+Email sent to design list: http://lists.wikimedia.org/pipermail/design/2013-September/000923.html",1379461042,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,CC'ing Dan Garry (new Platform PM). No action needed Dan (yet ;) ). Just using this as a way to remind us to talk about this work and how you'll interface with it.,1379002862,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"The goal is to get this extension deployed (to phase 0 wikis) by the end of September. I'm not sure if this will be possible, but I've tentatively added it to the deployments calendar for September 30: <https://wikitech.wikimedia.org/w/index.php?diff=83188&oldid=83134#Near_term>.
+
+Lego: feel free to move the date into October if necessary.",1378777053,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #9)
+>> Not sure this is relevant as this extension isn't really user-facing, but if
+>> you want to find someone to review the design, go for it.
+> 
+> Well, for some definition of user, right? It has sysop user facing UI. For a
+> design review, the Design mailing list is a good place to start (and then
+> ping until success).
+
+Lego: please go ahead and e-mail the design mailing list (include a working demo of the tool, of course). If they have constructive feedback, wonderful. Otherwise, I don't consider this a blocker to deployment.
+
+>> Greg: how do we get this extension reviewed for architecture/performance and
+>> security?
+> 
+> First pass would be to send a note to wikitech-l asking for help.
+> Unfortunately, this week is a combined Tech Days and All Hands so WMF tech
+> staff will be slower to respond than normal, but I know you know who to ping
+> as needed (Aaron/Tim for arch, Chris for security).
+
+Lego: please go ahead and e-mail wikitech-l asking for a review once you're ready and you've done your best to ensure that the extension is in a reviewable state. Test rigorously!
+
+If you could cross-reference these two mailing list posts on this bug, that would be wonderful.
+
+> Well, if there are any userfacing bits (even for non-mortals), then it'd be
+> good to have a walk-through of how the extension is supposed to work/what the
+> process is. Think of it as a required bit of user documentation :)
+
+If you write docs about how to create one of these mythical screencasts, I'll consider it. In the meantime, over a decade of development has progressed without these being a requirement. We're not going to start with this extension. :-)
+
+>>> Community support: no?
+>> 
+>> Yes, plenty of it.
+> 
+> Awesome. I believe you, but would appreciate links to where discussion has
+> happened.
+
+This request is a blocker to bug 35306. It falls outside the requirement for community consensus as it's an obvious and uncontroversial enhancement request; it is replacing a non-production, largely unsupported tool (i.e., the Python script that currently powers [[m:Global message delivery]]); and it has limited exposure (only admins will have access by default, and even most admins won't use this tool... for now).
+
+Bug 35306 gives most of the background here, but it's probably reasonable for me to point out that many (if not most) global message deliveries are connected to Wikimedia Foundation staff. The targets lists at [[m:Global message delivery/Targets]] comprise hundreds (maybe thousands) of users who have signed up for various newsletters and other mailings, in addition to a number of distribution lists used by Wikimedia volunteers and staff (including technical announcements and other breaking changes announced to [[m:Distribution list/Global message delivery]]). You could consider this a third or fourth exemption to the community consensus guideline, if you'd like. ;-)",1378776753,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #9)
+> > 
+> > > Community support: no?
+> > 
+> > Yes, plenty of it.
+> 
+> Awesome. I believe you, but would appreciate links to where discussion has
+> happened.
+
+Long wanted feature to not have to have bots making tens/thousands of edits onwiki. Not sure a discussion par se would have happened.. (if one has, great)
+
+To users, it really doesn't matter where it comes from.",1378768971,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #8)
+> Thanks for writing out a checklist.
+
+:)
+
+> (In reply to comment #7)
+> > == TODO/Check list ==
+> > Extension page on mediawiki.org: yes
+> > Bugzilla component: yes
+> > Extension in Gerrit: yes
+> 
+> Right.
+> 
+> > Design Review: no
+> 
+> Not sure this is relevant as this extension isn't really user-facing, but if
+> you want to find someone to review the design, go for it.
+
+Well, for some definition of user, right? It has sysop user facing UI. For a design review, the Design mailing list is a good place to start (and then ping until success).
+
+> 
+> > Architecture/Performance Review: no
+> > Security Review: no
+> 
+> These are the two areas needed here.
+> 
+> Greg: how do we get this extension reviewed for architecture/performance and
+> security?
+
+First pass would be to send a note to wikitech-l asking for help. Unfortunately, this week is a combined Tech Days and All Hands so WMF tech staff will be slower to respond than normal, but I know you know who to ping as needed (Aaron/Tim for arch, Chris for security).
+
+> 
+> > Screencast (if applicable): no
+> 
+> Not sure what this is about. It seems irrelevant.
+
+Well, if there are any userfacing bits (even for non-mortals), then it'd be good to have a walk-through of how the extension is supposed to work/what the process is. Think of it as a required bit of user documentation :)
+
+> 
+> > Community support: no?
+> 
+> Yes, plenty of it.
+
+Awesome. I believe you, but would appreciate links to where discussion has happened.",1378768315,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Thanks for writing out a checklist.
+
+(In reply to comment #7)
+> == TODO/Check list ==
+> Extension page on mediawiki.org: yes
+> Bugzilla component: yes
+> Extension in Gerrit: yes
+
+Right.
+
+> Design Review: no
+
+Not sure this is relevant as this extension isn't really user-facing, but if you want to find someone to review the design, go for it.
+
+> Architecture/Performance Review: no
+> Security Review: no
+
+These are the two areas needed here.
+
+Greg: how do we get this extension reviewed for architecture/performance and security?
+
+> Screencast (if applicable): no
+
+Not sure what this is about. It seems irrelevant.
+
+> Community support: no?
+
+Yes, plenty of it.",1378423432,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"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: no
+Archeticecture/Performance Review: no
+Security Review: no
+Screencast (if applicable): no
+Community support: no?",1378415175,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #5)
+> Hi Legoktm, I see that http://www.mediawiki.org/wiki/Extension:MassMessage
+> exists but where is its bugtracker? See
+> https://www.mediawiki.org/wiki/Bug_management/Project_Maintainers#To_add_a_project_or_component
+
+Filed as bug 52730.",1376239786,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Hi Legoktm, I see that http://www.mediawiki.org/wiki/Extension:MassMessage exists but where is its bugtracker? See https://www.mediawiki.org/wiki/Bug_management/Project_Maintainers#To_add_a_project_or_component",1376238095,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #1)
+> (see [[meta:User talk:EdwardsBot/Archive 1#LQT compatibility]])
+The correct link is [[User talk:EdwardsBot/Archive 1#LQT compatibility]].",1376235918,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"For reference: <https://gerrit.wikimedia.org/r/#/q/project:mediawiki/extensions/MassMessage+status:open,n,z>.",1376229430,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #1)
+> Does it have the same problem as the global message delivery system on wikis
+> which use LiquidThreads?
+> (see [[meta:User talk:EdwardsBot/Archive 1#LQT compatibility]])
+
+The real bug is that those wikis are still using LiquidThreads. :-)
+
+But if you want to add a dependency bug about MassMessage supporting LiquidThreads, it shouldn't be too painful to code.",1376228263,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Does it have the same problem as the global message delivery system on wikis which use LiquidThreads?
+(see [[meta:User talk:EdwardsBot/Archive 1#LQT compatibility]])",1376224547,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Enable VisualEditor on se.wikimedia.org,"The Swedish chapter would like to get the VisualEditor enabled on their wiki at se.wikimedia.org. 
+
+Poll here: http://se.wikimedia.org/wiki/Tråd:Wikimedia:Bybrunnen/VisualEditor_och_Notifications
+
+/Jan
+CEO
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1376178900,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-sflxt54msumq4ifieh2r,task_description,resolved
+Enable VisualEditor on se.wikimedia.org,"This is now live - you can opt in to test VisualEditor using the Beta Features link in your personal tools at the top of the page, or through the Preferences link in the ""Beta Features"" tab.
+
+If there are any issues, please shout!",1386022170,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sflxt54msumq4ifieh2r,task_subcomment,NA
+Enable VisualEditor on se.wikimedia.org,"Change 97714 merged by jenkins-bot:
+Enable VisualEditor as opt-in on Swedish Wikimedia
+
+https://gerrit.wikimedia.org/r/97714",1386021563,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sflxt54msumq4ifieh2r,task_subcomment,NA
+Enable VisualEditor on se.wikimedia.org,"Change 97714 had a related patch set uploaded by Jforrester:
+Enable VisualEditor as opt-in on Swedish Wikimedia
+
+https://gerrit.wikimedia.org/r/97714",1385464058,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sflxt54msumq4ifieh2r,task_subcomment,NA
+"VisualEditor: In Firefox's High Contrast mode, buttons on the toolbar are unidentifiable","en.wp user Cryptic C62 reports that using Firefox with Windows Vista ""high contrast"" mode renders VE entirely unusable:
+
+""Using Windows Vista, press Shift + Alt + Print Screen to activate ""high contrast"" mode. Open VE in Firefox. Weep uncontrollably (see screenshot).""
+
+Screenshot: [[File:VE High Contrast.jpg]]
+
+
+It is worth noting that, when using the high contrast extension for Chrome, the interface is fully visible in every setting. Hooray!
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1376068440,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gysdgpu4licxwvxxosg3,task_description,invalid
+"VisualEditor: In Firefox's High Contrast mode, buttons on the toolbar are unidentifiable",id call this an OS bug...,1457161240,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-gysdgpu4licxwvxxosg3,task_subcomment,NA
+"VisualEditor: In Firefox's High Contrast mode, buttons on the toolbar are unidentifiable","Visual Editor in Windows 7 High Contrast Mode in Firefox 44 {F3524565}
+
+Google.com in Microsoft's very own Internet Explorer 11
+{F3524580}
+
+Microsoft.com in IE 11 at High Contrast Mode on Windows 7 
+{F3524584}
+
+Given those examples I highly question how many people **are actually able to use //any website with this functionality at all//** in its current implementation?! Seems poorly conceived. 
+@Jdforrester-WMF  If nobody is opposing that in a reasonable time frame (30 days?) I'd recommend closing this task as ""invalid"".",1457147578,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-gysdgpu4licxwvxxosg3,task_subcomment,NA
+VisualEditor: Welcome dialog doesn't expand/scroll to fit large fonts,"When a user has a larger font size than defualt, or a non-default font then the welcome dialog (the one controlled by the ve-beta-welcome-dialog cookie) doesn't expand or scroll to accommodate the extended length of the message and the text is cropped.
+
+Screenshot at [[File:WARNINGforVE.png]]
+
+This might be another example of bug 52602 but I'm not certain.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52602
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51755
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50885",1376041620,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7ix4hqmkcelueduz7hux,task_description,resolved
+VisualEditor: Welcome dialog doesn't expand/scroll to fit large fonts,"Change 82466 merged by jenkins-bot:
+Improve welcome dialog support for large fonts
+
+https://gerrit.wikimedia.org/r/82466",1378335727,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7ix4hqmkcelueduz7hux,task_subcomment,NA
+VisualEditor: Welcome dialog doesn't expand/scroll to fit large fonts,"Change 82466 had a related patch set uploaded by Trevor Parscal:
+Improve welcome dialog support for large fonts
+
+https://gerrit.wikimedia.org/r/82466",1378241684,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7ix4hqmkcelueduz7hux,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"en.wp user Redrose64 reports:
+With this edit: https://en.wikipedia.org/w/index.php?title=Paisley_Gilmour_Street_railway_station&diff=prev&oldid=567709873 ""the {{-}} was moved from the bottom of a section into a heading, effectively yielding the HTML <h3><span class=""mw-headline"" id=""2013"">2013<br style=""clear:both;"" /></span>[edit]</h3> ""
+
+I can reproduce that on that article by:
+1. Deleting with backspace the header ""Post-2008"" (and nothing else)
+2. Typing ""2013""
+
+I can't reproduce it in my sandbox with {{-}} (or {{clear}}) before a header and then changing the header.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375989720,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-cwptueorc4rxrgvc5shh,task_description,resolved
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1376609977,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"Because Subbu and Gabriel asked: this is a VE bug, not a Parsoid bug. Unfortunately it's not very clear where the {{-}} template is exactly because it doesn't really produce visible output. So pressing backspace or delete can cause the {{-}} to move to a different paragraph, which may be styled as a heading or restyled by the user to be a heading. And you don't really notice that you're doing this because it's not visible.",1376609124,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"Moving to VisualEditor:
+
+[16:19] <RoanKattouw> That looks like a VE issue
+[16:20] <RoanKattouw> It's probably because {{-}} doesn't produce any visible output (it outputs a <br> with clear: both;)
+[16:20] <RoanKattouw> And so people don't notice when their backspace or delete presses cause the {{-}} to be moved into a different paragraph which they then mark up as a heading",1376609113,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"I reproduced it - not precisely, but close enough.
+
+I pretended I was a brand new editor, and rather than changing the heading I created a new one, above the old. Then I deleted the old and applied formatting to the new word I typed.
+
+This rendered this: http://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29%2Fsandbox&diff=568643085&oldid=568642989
+
+The template moved, but in front of rather than behind the word.
+
+I'm using Chrome.
+
+I tried it again on Firefox, and caught the template again:
+https://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29%2Fsandbox&diff=568643930&oldid=568643677
+
+I guess that the IP editor may have positioned his cursor slightly differently, but that seems to be the behavior that led to the issue. It seems like potentially an easy decision to make.",1376567370,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"I agree with your recommendation, Chris.
+
+I think this was a valid bug, but it might have been specific to a particular set of conditions at the time of the bug (cached HTML, what the user was doing, the state that VE was in and the HTML it generated, source wikitext) which we are having a hard time reproducing now.  So, I am going to close this bug for now and we can reopen this or a new one if a similar error shows up.",1376407275,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"Having tried again, I still can't reproduce it. The original edit that caused this was by an anonymous user who hasn't edited since, so we're unlikely to get any more information from them.
+
+Should this be closed (WORKSFORME?) and then just reopened if it happens again in future?",1376388286,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"After about 5 minutes trying I can't reproduce this now on either the present or old revisions of that page. I haven't tried again in my sandbox but given the other findings I wouldn't expect it to.
+
+The only change is I'm now running Firefox 23 rather than the 22 I was running when I reported this (and I don't know how to keep separate versions of the same program available at the same time, sorry)",1376093134,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"Unfortunately, I am having a hard time reproducing the bug now.  And, as you noted, I am not able to copy it to my sandbox and reproduce it either.  This may have been some glitch in how VE might have modified the DOM on editing there.
+
+Can you verify that you can reproduce the error on the latest version or that oldid?  I even added a newline space back in case that matters (since that is what was present in the oldid).",1376083679,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Thai Wikipedia's coordinates template displays badly in tables,"During the edit
+
+This has been noted on the Thai wikipedia.  
+See screenshots for how it looks.  
+
+Basically, in edit mode, the sixth column of this table, containing Goehack coordinate links, displays as an HTML string in edit mode. Not only very messy, but it pushes the following columns off the page.
+
+Appears to save normally.
+
+Replicated on current FF, Chrome, on Mac OS and Ubuntu
+
+Page on Thai.wiki: https://th.wikipedia.org/wiki/%E0%B8%A3%E0%B8%B2%E0%B8%A2%E0%B8%8A%E0%B8%B7%E0%B9%88%E0%B8%AD%E0%B9%82%E0%B8%9A%E0%B8%A3%E0%B8%B2%E0%B8%93%E0%B8%AA%E0%B8%96%E0%B8%B2%E0%B8%99%E0%B9%83%E0%B8%99%E0%B8%81%E0%B8%A3%E0%B8%B8%E0%B8%87%E0%B9%80%E0%B8%97%E0%B8%9E%E0%B8%A1%E0%B8%AB%E0%B8%B2%E0%B8%99%E0%B8%84%E0%B8%A3_(%E0%B9%80%E0%B8%82%E0%B8%95%E0%B8%9E%E0%B8%A3%E0%B8%B0%E0%B8%99%E0%B8%84%E0%B8%A3_%E0%B8%9B%E0%B9%89%E0%B8%AD%E0%B8%A1%E0%B8%9B%E0%B8%A3%E0%B8%B2%E0%B8%9A%E0%B8%A8%E0%B8%B1%E0%B8%95%E0%B8%A3%E0%B8%B9%E0%B8%9E%E0%B9%88%E0%B8%B2%E0%B8%A2_%E0%B9%81%E0%B8%A5%E0%B8%B0%E0%B8%AA%E0%B8%B1%E0%B8%A1%E0%B8%9E%E0%B8%B1%E0%B8%99%E0%B8%98%E0%B8%A7%E0%B8%87%E0%B8%A8%E0%B9%8C)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11613}",1375975140,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-blwhpbgbhchhdkulxgr2,task_description,resolved
+VisualEditor: Thai Wikipedia's coordinates template displays badly in tables,"Not sure when, but this is now fixed, probably because of Ed's work on template wrapping.",1414165021,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-blwhpbgbhchhdkulxgr2,task_subcomment,NA
+VisualEditor: Transclusion dialog should validate template parameter values using TemplateData information,"If a parameter has '""type"": ""number""', VisualEditor should not allow the user to insert other kind of values. Alternativelly, it could just warn the user but still allow a value of the wrong type to be inserted.
+
+This should not be restricted just to the ""number"" type. Other types would also benefity from some validation (e.g., if at some point we have a type ""string/image-name"", VE should check if the user provided the name of an existing image).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52652",1375969680,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-c65b3wdhn2onui4dnvcj,task_description,open
+VisualEditor: Transclusion dialog should validate template parameter values using TemplateData information,"I don't agree with restricting users from only entering content as the hinting suggests (the hinting may be wrong, or may restrict users too much) - this is the same reason why we allow users to add un-hinted parameters.
+
+However, yes, we should definitely add this missing feature in soon.",1376115954,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c65b3wdhn2onui4dnvcj,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","If you want to add a ""template"" that is not in the template namespace, for example: ""User:UBX""; VE will make an API request like: ""GET https://en.wikipedia.org/w/api.php?format=json&action=templatedata&titles=Template%3AUser%3AUBX"".
+
+It should automatically detect that ""User:"" is a valid namespace, and not add the ""Template:"" prefix.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375875780,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_description,resolved
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","Change 140875 merged by jenkins-bot:
+Handle transcluding templates outside of the template namespace properly
+
+https://gerrit.wikimedia.org/r/140875",1404157149,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","What Matt pointed out is handled correctly except for main namespace titles (e.g. :Foo), where the input widget trips over itself and you always end up with Template:Foo.",1403824833,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","The commit says the purpose of the colon is ""to create a link to something that would normally be included as a File/Category"".
+
+That's true, but it also plays a role in transclusion.  It's used to transclude things in the main namespace.
+
+E.g. on English Wikipedia {{Main Page}} transcludes https://en.wikipedia.org/wiki/Template:Main_Page , whereas {{:Main Page}} transcludes https://en.wikipedia.org/wiki/Main_Page
+
+For other namespaces (e.g. {{Wikipedia:Community Portal}} / {{:Wikipedia:Community Portal}} ), it works either way.
+
+Full demo: https://en.wikipedia.org/w/index.php?title=User:Superm401/Sandbox&oldid=614564227
+
+This may be handled somewhere (e.g. Parsoid), but it needs to be tested.",1403823029,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","This was also hiding another problem (templates outside of the Template namespace ended up prefixed with ':', breaking them). This patch should fix that too (and hopefully not break any other link suggesting things).",1403224037,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","Change 140875 had a related patch set uploaded by Alex Monk:
+Handle transcluding templates outside of the template namespace properly
+
+https://gerrit.wikimedia.org/r/140875",1403223913,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","(Okay, it's not as simple as I was hoping)",1403222822,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided",It looks like we can just pass the title to mw.Title.newFromText with mw.config.get( 'wgNamespaceIds' ).template as the (default) namespace.,1403221498,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+VisualEditor: Get rid of IVStore check in toDomElements in GCNode subclasses,"Some toDomElements functions reach into the store, but they shouldn't and the check is redundant.
+",1375853340,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gx6k3eekkero53hloidz,task_description,open
+VisualEditor: Add keyboard shortcut for code element/style,"A keyboard shortcut for code would be helpful, particularly for MediaWiki.org.  We'll need to think of what to use.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375852380,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gf6k4fuodiscgbllfhpa,task_description,resolved
+VisualEditor: Add keyboard shortcut for code element/style,Verified the fix in production,1411682734,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"Change 160174 merged by jenkins-bot:
+Add keyboard shortcuts for strikethrough and code annotations
+
+https://gerrit.wikimedia.org/r/160174",1410823312,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"Change 160174 had a related patch set uploaded by Jforrester:
+Add keyboard shortcuts for strikethrough and code annotations
+
+https://gerrit.wikimedia.org/r/160174",1410570243,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"**fred** wrote:
+
+When is this planned? I was about to write that enhancement proposition as well when I saw this ticket.
+
+My personal preference would be to have a shortcut near the ctrl tab on the left of the keyboard.",1385041001,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"(In reply to comment #1)
+> One possiblity is Ctrl-{.  It takes three key strokes on some keyboards, but
+> it's memorable as long as it matches the toolbar icon, and not that hard to
+> type.
+
+We're almost certainly not going to keep '{}' for code (especially as there's <code> and <syntaxhighlight> that need to be distinguishable), but it's a possibility.",1375865906,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"One possiblity is Ctrl-{.  It takes three key strokes on some keyboards, but it's memorable as long as it matches the toolbar icon, and not that hard to type.",1375861847,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Some templates use numbered arguments (see for example http://en.wikipedia.org/wiki/Module:Citation/CS1/Whitelist in the numbered_arguments list). For example, you can use author1, author2, ... (no limit).
+
+Currently, there's no way to define such parameters in TemplateData, and the VE interface is not also optimal for them.
+
+Would it be possible to handle numbered arguments in TemplateData: a parameter named author# would define a numbered parameter named author with a numerical suffix. It should be possible to define lower bound (1 by default) and upper bound (no limit by default).
+
+Then VE should handle them accordingly: only propose the first parameter available in the list of parameters than can be added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+{T53740}",1375805280,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_description,open
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,We are currently only passively maintaining template wizard. See https://meta.wikimedia.org/wiki/Community_Tech/Maintenance for more.,1706108119,PHID-USER-hc3d7yz5cqmafn4osucd,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"I’ll add #community-tech team to the task as maintainers of TemplateWizard, maybe they have ideas :)",1705603244,PHID-USER-tuy2dac6pfhknbtqmqgh,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"> If you don’t display `author-link3` until I filled `author-link2`, I can’t […]
+
+That's a great example, thanks! Sounds like an argument for the {key +} button.
+
+> templates where a trailing “1” doesn’t denote a sequence, but a year, a code (e.g. ISO 639-1) […]
+
+True, these might behave odd. We can't avoid this entirely but limit the effect by using a clever regex like `/\p{L}[\p{P}\p{Z}]*1$/u`. This will not pick up the examples you listed.
+
+> MediaWiki message-style `editor$1-last` […]
+
+Either that or `{{{1}}}` to reuse a pattern users are familiar with. However, this can't replace the current parameter name for the same backwards-compatibility reason as above but must be part of the new syntax:
+```lang=JSON
+""author1"": { ""sequence"": { ""name"": ""author$1"", ""from"": ""1"", ""to"": ""5"" } }
+```
+
+There is also another very common special case that goes like `author`, `author2`, `author3`, and so on without the `1`. Luckily this is easy to solve with the proposed syntax:
+```lang=JSON
+""author"": {},
+""author2"": { ""sequence"": { ""name"": ""author$1"", ""from"": ""2"", ""to"": ""5"" } }
+```",1669128401,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,">>! In T54582#8408107, @Tacsipacsi wrote:
+> I think there are still a lot of templates that don’t use Lua and thus support exactly as many parameters as documented. They probably don’t show error messages if unknown parameters are used, either, since that would also require Lua. This means that the extra parameters would simply not appear – which doesn’t cause visual breakage, but it’s also hard for the editors to notice. What does Citoid do now if there are more authors/whatever data than what the template – according to TemplateData – supports?
+
+Right now it silently just doesn't add the authors. If there's template data for 20, it'll add 20 and then stop. Unless it's a collapsed param, and then it concatenates them all together. So right now the results are actually better using a collapsed param because you get all the authors. 
+
+A lot of the non Lua templates are configured to use collapsed params, i.e. they have just one author field. In that case, all the authors are concatenated and make it into the template. I.e. this is the de wiki case. It'd only be non-lua templates that are also configured with citoid to use separate fields. 
+
+There's a related wishlist item for this: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Citations#Preventing_VE_from_silently_omitting_co-authors
+
+There's a suggestion to using display-authors but coming up with a system to do that is even less fleshed out in terms of how we'd decide that. I'd rather just actually add the author. 
+
+There's also the option of producing two citations, one with and one without for the user to choose.
+
+Funny edgecases for my proposed hack - a param that looks like isbn2, might accidentally produce isbn3 and isbn4 depending on how the data is configured. 
+
+",1669116447,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"To allow linking author3 without having to link the previous ones, the field author-link3 could appear when you FOCUS in author-link2, and author-link2 when you focus in author-link1, etc
+
+This would also make it more obvious to users how to access collapsed parameters.",1674485033,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Tho allow linking author3 without having to link the previous ones, the field author-link3 could appear when you FOCUS in author-link2, and author-link2 when you focus in author-link1, etc
+
+This would also make it more obvious to users how to access collapsed parameters.",1669084905,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Regarding the problem with point 1, the field author-link3 may appear when you FOCUS in author-link2, and author-link2 when you focus in author-link1, etc
+
+This would allow to link author3 without having to link the previous ones, and would also make it more obvious to users how to access collapsed parameters.",1669083437,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,">>! In T54582#8409117, @thiemowmde wrote:
+> 1. Collapse numbered parameters in VisualEditor. For example, when you start with an empty template you see only `author1`. The moment `author1` does have a value `author2` appears. And so on. But stop when the next number is not documented.
+>  * We can do this in VisualEditor without touching TemplateData.
+>  * The only thing users need to do is to make sure all possible numbers are documented.
+>  * This doesn't solve the situation where the number is unlimited, but allows for a workaround. Users just need to document //a lot// of numbers, e.g. `author1` to `author25`.
+This may not work in all cases. For example, [[https://en.wikipedia.org/wiki/Template:Cite_web|en:Template:Cite web]] have several parameters for providing authors, but to keep the example simple, let’s concentrate on the three that are included in the vertical copy sample: `firstN`, `lastN` and `author-linkN`. If only the first and third author have articles, I’d like to include the following:
+```
+{{cite web |first1=John |last1=Doe |author-link1=John Doe |first2=Jane |last2=Doe |first3=Jimmy |last3=Wales |author-link3=Jimmy Wales |… }}
+```
+If you don’t display `author-link3` until I filled `author-link2`, I can’t link to Jimbo’s article without adding a red link to Jane Doe’s article, which should not be done according to the documentation.
+
+> 2. Ask users to document an unlimited number of parameters by only documenting the first one, e.g. `author1`, but nothing else. We can use this special case to distinguish the two unlimited vs. limited scenarios.
+I have no actual example at hand, but I’m pretty sure there are templates where a trailing “1” doesn’t denote a sequence, but a year, a code (e.g. ISO 639-1), and so on.
+
+> 3. Come up with some magic syntax for numbered parameters, e.g. `""author[1-9]""` means only 9 parameters exist and `""author[1-]""` means it's unlimited.
+>  * This allows to use other number systems, e.g. Hebrew `author[א-ט‎]`.
+>  * Biggest problem with an approach like this is that it's entirely incompatible with existing software that doesn't understand the feature.
+Also, we’d need to be very careful what the syntax is, since `{{{author[1-9]}}` is for example a legal parameter name. Even `{{{a{{!}}b}}}` is legal, so pipes are neither something we can freely play with…
+
+> 4. Add a flag that does the same, e.g. `""author1"": { ""sequence"": { ""name"": ""author"", ""from"": ""1"", ""to"": ""5"" } }`. Use `""from"": ""1"", ""to"": ""1000""` to make it effectively ""unlimited"".
+>  * This can be made backwards-compatible. Users can still document `author1` to `author5` if they want. They just need to copy the sequence name to all of them, e.g. `""author2"": { ""sequence"": { ""name"": ""author"" } }`. Parameters with the same sequence are considered one by software that understands the feature.
+I like this the best. However, the counter doesn’t need to be at the end (see `editor2-last` in {{Cite web}}), so we need a syntax to indicate where the number goes. For example, it could be a printf-style `editor%d-last` (with the usual `%%` escape if the parameter name literally contains `%d`), or the MediaWiki message-style `editor$1-last` (what’s the escape here?). Also, it needs to accept not only ASCII digits, but anything that’s sequential (non-ASCII numbers, maybe even letters).
+
+> 5. Somehow make use of the unused `set` feature.
+According to the [[https://www.mediawiki.org/wiki/Extension:TemplateData|documentation]], a set is “a group of parameters that should be used together” – this doesn’t fit this use case, since `author1` can be used without `author42`.",1669065650,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"#wmde-techwish here. Our #wmde-templates-focusarea last year focused on #TemplateData and the #VisualEditor template dialog. I'm aware of two situations we need to consider here:
+1. Non-Lua templates support exactly as many parameters as documented, as @Tacsipacsi explained above. For example, there is `author1` to `author9`, but there it ends. This causes a few problems:
+ * It's a little tedious to document this.
+ * Both #VisualEditor and #TemplateWizard get messy very fast the more such parameters exist. Note that having more than one is the norm, not the exception. Here is a [simple example](https://en.wikipedia.org/wiki/Template:Singles).
+ * The person writing the documentation might decide to stop earlier and document only e.g. `author1` to `author5` exactly to avoid the problem above. `author6` ff. will still work, but can only be entered in wikitext or with the ""add undocumented parameter"" feature. Unfortunately this creates the next problem: `author6` will be listed at the very end, not after `author5`.
+2. Lua-based templates can support an effectively unlimited number of such parameters. The currently only way to document this is to document a limited number, e.g. `author1` to `author5`. This creates almost the same problems:
+ * The documentation must stop at an arbitrary number. Typically this will not be `author1` but e.g. `author5` or `author9`.
+ * This is tedious, as above.
+ * VisualEditor and such always show all of the documented parameters.
+3. Because of all the problems above and thanks to the power of Lua users create more and more templates that accept multiple comma-separated values in a single parameter.
+ * This creates effectively a custom parameter type with a custom syntax (namely being comma-separated).
+ * TemplateData has no way to document this either. I mean, other than describing it to the user. But not in a machine-readable way.
+
+A relevant consequence of all this is that we don't have a way to distinguish the first two situations when both are documented as `author1` to `author5`.
+
+What we can do, in my opinion:
+1. Collapse numbered parameters in VisualEditor. For example, when you start with an empty template you see only `author1`. The moment `author1` does have a value `author2` appears. And so on. But stop when the next number is not documented.
+ * We can do this in VisualEditor without touching TemplateData.
+ * The only thing users need to do is to make sure all possible numbers are documented.
+ * This doesn't solve the situation where the number is unlimited, but allows for a workaround. Users just need to document //a lot// of numbers, e.g. `author1` to `author25`.
+2. Ask users to document an unlimited number of parameters by only documenting the first one, e.g. `author1`, but nothing else. We can use this special case to distinguish the two unlimited vs. limited scenarios.
+3. Come up with some magic syntax for numbered parameters, e.g. `""author[1-9]""` means only 9 parameters exist and `""author[1-]""` means it's unlimited.
+ * This allows to use other number systems, e.g. Hebrew `author[א-ט‎]`.
+ * Biggest problem with an approach like this is that it's entirely incompatible with existing software that doesn't understand the feature.
+4. Add a flag that does the same, e.g. `""author1"": { ""sequence"": { ""name"": ""author"", ""from"": ""1"", ""to"": ""5"" } }`. Use `""from"": ""1"", ""to"": ""1000""` to make it effectively ""unlimited"".
+ * This can be made backwards-compatible. Users can still document `author1` to `author5` if they want. They just need to copy the sequence name to all of them, e.g. `""author2"": { ""sequence"": { ""name"": ""author"" } }`. Parameters with the same sequence are considered one by software that understands the feature.
+5. Somehow make use of the unused `set` feature.
+6. Just give the user a {key +} button at the end of numbered parameters, no matter how it's documented in TemplateData. It acts very similar to the ""add undocumented parameter"" feature but makes sure the order is consistent.
+6. …?
+
+I would like to avoid presenting an extra empty parameter at the end of every sequence of numbered parameters when the documentation explicitly says it doesn't exist, or we just don't know.",1669035722,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"#wmde-techwish here. Our #wmde-templates-focusarea last year focused on #TemplateData and the #VisualEditor template dialog. I'm aware of two situations we need to consider here:
+1. Non-Lua templates support exactly as many parameters as documented, as @Tacsipacsi explained above. For example, there is `author1` to `author9`, but there it ends. This causes a few problems:
+ * It's a little tedious to document this.
+ * Both #VisualEditor and #TemplateWizard get messy very fast the more such parameters exist. Note that having more than one is the norm, not the exception. Here is a [simple example](https://en.wikipedia.org/wiki/Template:Singles).
+ * The person writing the documentation might decide to stop earlier and document only e.g. `author1` to `author5` exactly to avoid the problem above. `author6` ff. will still work, but can only be entered in wikitext or with the ""add undocumented parameter"" feature. Unfortunately this creates the next problem: `author6` will be listed at the very end, not after `author5`.
+2. Lua-based templates can support an effectively unlimited number of such parameters. The currently only way to document this is to document a limited number, e.g. `author1` to `author5`. This creates almost the same problems:
+ * The documentation must stop at an arbitrary number. Typically this will not be `author1` but e.g. `author5` or `author9`.
+ * This is tedious, as above.
+ * VisualEditor and such always show all of the documented parameters.
+3. Because of all the problems above and thanks to the power of Lua users create more and more templates that accept multiple comma-separated values in a single parameter.
+ * This creates effectively a custom parameter type with a custom syntax (namely being comma-separated).
+ * TemplateData has no way to document this either. I mean, other than describing it to the user. But not in a machine-readable way.
+
+A relevant consequence of all this is that we don't have a way to distinguish the first two situations when both are documented as `author1` to `author5`.
+
+What we can do, in my opinion:
+1. Collapse numbered parameters in VisualEditor. For example, when you start with an empty template you see only `author1`. The moment `author1` does have a value `author2` appears. And so on. But stop when the next number is not documented.
+ * We can do this in VisualEditor without touching TemplateData.
+ * The only thing users need to do is to make sure all possible numbers are documented.
+ * This doesn't solve the situation where the number is unlimited, but allows for a workaround. Users just need to document //a lot// of numbers, e.g. `author1` to `author25`.
+2. Ask users to document an unlimited number of parameters by only documenting the first one, e.g. `author1`, but nothing else. We can use this special case to distinguish the two unlimited vs. limited scenarios.
+3. Come up with some magic syntax for numbered parameters, e.g. `""author[1-9]""` means only 9 parameters exist and `""author[1-]""` means it's unlimited.
+ * This allows to use other number systems, e.g. Hebrew `author[א-ט‎]`.
+ * Biggest problem with an approach like this is that it's entirely incompatible with existing software that doesn't understand the feature.
+4. Add a flag that does the same, e.g. `""author1"": { ""sequence"": { ""name"": ""author"", ""from"": ""1"", ""to"": ""5"" } }` Use `""from"": ""1"", ""to"": ""1000""` to make it effectively ""unlimited"".
+ * This can be made backwards-compatible. Users can still document `author1` to `author5` if they want. They just need to copy the sequence name to all of them, e.g. `""author2"": { ""sequence"": { ""name"": ""author"" } }`. Parameters with the same sequence are considered one by software that understands the feature.
+5. Somehow make use of the unused `set` feature.
+6. Just give the user a {key +} button at the end of numbered parameters, no matter how it's documented in TemplateData. It acts very similar to the ""add undocumented parameter"" feature but makes sure the order is consistent.
+6. …?
+
+I would like to avoid presenting an extra empty parameter at the end of every sequence of numbered parameters when the documentation explicitly says it doesn't exist, or we just don't know.",1669035672,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"#wmde-techwish here. Our #wmde-templates-focusarea last year focused on #TemplateData and the #VisualEditor template dialog. I'm aware of two situations we need to consider here:
+1. Non-Lua templates support exactly as many parameters as documented, as @Tacsipacsi explained above. For example, there is `author1` to `author9`, but there it ends. This causes a few problems:
+ * It's a little tedious to document this.
+ * Both #VisualEditor and #TemplateWizard get messy very fast the more such parameters exist. Note that having more than one is the norm, not the exception. Here is a [simple example](https://en.wikipedia.org/wiki/Template:Singles).
+ * The person writing the documentation might decide to stop earlier and document only e.g. `author1` to `author5` exactly to avoid the problem above. `author6` ff. will still work, but can only be entered in wikitext or with the ""add undocumented parameter"" feature. Unfortunately this creates the next problem: `author6` will be listed at the very end, not after `author5`.
+2. Lua-based templates can support an effectively unlimited number of such parameters. The currently only way to document this is to document a limited number, e.g. `author1` to `author5`. This creates almost the same problems:
+ * The documentation must stop at an arbitrary number. Typically this will not be `author1` but e.g. `author5` or `author9`.
+ * This is tedious, as above.
+ * VisualEditor and such always show all of the documented parameters.
+3. Because of all the problems above and thanks to the power of Lua users create more and more templates that accept multiple comma-separated values in a single parameter.
+ * This creates effectively a custom parameter type with a custom syntax (namely being comma-separated).
+ * TemplateData has no way to document this either. I mean, other than describing it to the user. But not in a machine-readable way.
+
+A relevant consequence of all this is that we don't have a way to distinguish the first two situations when both are documented as `author1` to `author5`.
+
+What we can do, in my opinion:
+1. Collapse numbered parameters in VisualEditor. For example, when you start with an empty template you see only `author1`. The moment `author1` does have a value `author2` appears. And so on. But stop when the next number is not documented.
+ * We can do this in VisualEditor without touching TemplateData.
+ * The only thing users need to do is to make sure all possible numbers are documented.
+ * This doesn't solve the situation where the number is unlimited, but allows for a workaround. Users just need to document //a lot// of numbers, e.g. `author1` to `author25`.
+2. Ask users to document an unlimited number of parameters by only documenting the first one, e.g. `author1`, but nothing else. We can use this special case to distinguish the two unlimited vs. limited scenarios.
+3. Come up with some magic syntax for numbered parameters, e.g. `""author[1-9]"": {}` means only 9 parameters exist and `""author[1-]"": {}` means it's unlimited.
+ * This allows to use other number systems, e.g. Hebrew `author[א-ט‎]`.
+ * Biggest problem with an approach like this is that it's entirely incompatible with existing software that doesn't understand the feature.
+4. Add a flag that does the same, e.g. `""author1"": { ""sequence"": { ""name"": ""author"", ""from"": ""1"", ""to"": ""5"" } }` or `""from"": ""1"", ""to"": ""1000""` to make it effectively ""unlimited"".
+ * This can be made backwards-compatible. Users can still document `author1` to `author5` if they want. They just need to copy the sequence name to all of them, e.g. `""author2"": { ""sequence"": { ""name"": ""author"" } }`. Parameters with the same sequence are considered one by software that understands the feature.
+5. Somehow make use of the unused `set` feature.
+6. Just give the user a {key +} button at the end of numbered parameters, no matter how it's documented in TemplateData. It acts very similar to the ""add undocumented parameter"" feature but makes sure the order is consistent.
+6. …?
+
+I would like to avoid presenting an extra empty parameter at the end of every sequence of numbered parameters when the documentation explicitly says it doesn't exist, or we just don't know.",1669035410,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"I think there are still a lot of templates that don’t use Lua and thus support exactly as many parameters as documented. They probably don’t show error messages if unknown parameters are used, either, since that would also require Lua. This means that the extra parameters would simply not appear – which doesn’t cause visual breakage, but it’s also hard for the editors to notice. What does Citoid do now if there are more authors/whatever data than what the template – according to TemplateData – supports?",1668975175,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Change 858708 had a related patch set uploaded (by Mvolz; author: Mvolz):
+%%%[mediawiki/extensions/Citoid@master] [WIP] Extrapolate from limited templatedata%%%
+https://gerrit.wikimedia.org/r/858708",1668963559,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"In lieu of a better plan, I think I'm just going to have the Citoid extension ""guess"" additional parameters from the last one rather naively by incrementing whatever integer is at the end. I.e. if it's last7, the next param will be last8
+
+If the last param doesn't have an integer, we won't do this. So if it's just ""last"" or ""isbn"" no additional parameters will be added. 
+
+Does anyone object to this? It's a bit hacky, but it's the simplest to implement. 
+
+The potential flaw of this would be if there is a parameter out there that ends in a number that we don't want incremented. I don't know if there's an example out there, but if there were, we could potentially add parameters that don't actually exist and you could see errors in the citation (which the user could then, as always, fix.)
+
+I expect this doesn't come up much, but a potential fix to that is to extend TemplateData to add a box to suppress auto params, if we needed it. 
+
+",1668963340,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"@Iniquity, the way I'd ideally like to see this work is to just have a box people could check when editing a parameter's documentation in TemplateData indicating that it's an auto-numbered parameter (and specifying the limit, if applicable). The TemplateData would then display it intuitively in the documentation and allow people to use it when adding the template to a page.",1633200407,PHID-USER-tl3o6dlackm57f3qrt4b,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,Has anyone got any new ideas? :),1564943687,PHID-USER-tuy2dac6pfhknbtqmqgh,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"For draft template I'm working on for the Wikitionary, I came with things like `|définition.1.4.exemple.2.description =`. That is description of 2nd example of the 4th subdefinition of the first main definition. That might be a somewhat extreme example, but that would be nice to take it into account while treating this ticket.",1510643874,PHID-USER-6xgsmxxl62mgxypce6oa,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"For draft template I'm working on for the Wikitionary, I came things like `|définition.1.4.exemple.2.description =`. That is description of 2nd example of the 4th subdefinition of the first main definition. That might be a somewaht extrem example, but that would be nice to take it into account while treating this ticket.",1509227971,PHID-USER-6xgsmxxl62mgxypce6oa,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"I am also thinking of templates with an unlimited number of unnamed parameters, which are not handled well in VE currently.",1508444614,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Regarding the UX and UI of this feature, one possibility is that when a user adds content to the Author1 field, the Author2 field becomes visible, and when s/he adds content to Author2, Author3 becomes visible, and so on.",1496014248,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Regarding the visual implementation of this feature, one possibility is that when a user adds content to the Author1 field, the Author2 field becomes visible, and when s/he adds content to Author2, Author3 becomes visible, and so on.",1492548241,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"I think I may increase priority of this task. A lot of new templates, gadgets and scripts have autogenerated parameters.",1491072953,PHID-USER-tuy2dac6pfhknbtqmqgh,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"This will affect ProveIt when implemented. ProveIt relies on TemplateData to perform its work, much in the same way the VisualEditor does.",1480128425,PHID-USER-ptgz6fq66cg246bpgxzs,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Would be very useful also for, e.g., https://www.mediawiki.org/wiki/Template:Extension#TemplateData (up to hook48!)",1421099235,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Hmm, I've messed up the JSON in the first example. Should be:
+
+{{cite web
+| authors = [{ ""last"": ""Smith"", ""first"": ""John"" }, { ""last"": ""Doe"", ""first"": ""Jane"" }]
+}}
+
+Perhaps this proves my point about users not being able to input JSON manually? :)",1410102520,PHID-USER-rjtk3h6l2quifuajiime,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"(In reply to NicoV from comment #5)
+> This solution would be awkward when several parameters are related one to
+> each other. For example, on the cite templates, you usually have several
+> fields for each author (first name, last name, page link, ...) and they are
+> easier to manage for a user if they are grouped.
+> With lists, users would have to be careful and to be sure that several lists
+> are coherent between each other.
+
+One way to deal with this could be to pass JSON blobs into template parameters. So you could have:
+
+{{cite web
+| authors = { ""last"": ""Smith"", ""first"": ""John"" }, { ""last"": ""Doe"", ""first"": ""Jane"" }
+}}
+
+This is nice from a Lua perspective, but it would be confusing for users. Mixing template syntax with JSON syntax seems ugly, and probably only a select few editors will be capable of entering syntactically correct JSON into template parameters.
+
+The established way of doing something like this is to use a sub-template. So we would have something like:
+
+{{cite web
+| authors = {{author|last=Smith|first=John}}, {{author|last=Doe|first=Jane}}
+}}
+
+One problem with this is that the {{author}} templates are expanded before they are passed to Lua, so we lose data granularity. To solve this, we can use Lua to make the {{author}} templates output JSON and then read that JSON from the Lua module implementing {{cite web}}. But then to guarantee that we get clean JSON code we would need to make a template structure like this:
+
+{{cite web
+| authors = {{author list | {{author|last=Smith|first=John}} | {{author|last=Doe|first=Jane}} }}
+}}
+
+With this we have data grouping that can be reliably processed by Lua and that editors used to using wikitext will find intuitive. However, this would be hard for VisualEditor etc. to process and display to users in a meaningful way, as there is no guarantee how the {{author list}} and {{author}} templates will be implemented on any given wiki. So, instead of using Lua to create the JSON, we could do it in PHP using a new parser function. (I suggest ""#data"".) That would give us the following: 
+
+{{cite web
+| authors = {{#data: {{#data:last=Smith|first=John}} | {{#data:last=Doe|first=Jane}} }}
+}}
+
+This would give us a data structure that could be reliably parsed from VisualEditor, as well as the other benefits mentioned above. Perhaps it could displayed as a dynamically generated data tree (I'm thinking about something like json2html, but editable).
+
+http://visualizer.json2html.com/
+
+We would need to be careful about bad input:
+
+{{cite web
+| authors = foo {{#data: bar {{#data:last=Smith|first=John}} | {{#data:last=Doe|first=Jane}} baz }}
+}}
+
+To sanitise this, we could make the #data implementation throw an error (perhaps like a cite.php error) for ""bar"" and ""baz"" in this example. For ""foo"", we could leave it to the Lua module to properly validate the input.
+
+We would also have to think carefully about what to do with templates etc. inside #data parser functions. If template expansion inside #data parser functions worked the same way that it did in normal wikitext, it would be difficult to make #data work well in VisualEditor. But perhaps it can be made to work in the same way that VE handles other instances of templates in template parameters.",1410099057,PHID-USER-rjtk3h6l2quifuajiime,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"(In reply to Krinkle from comment #4)
+> Especially now that we have Lua, specifying a parameter as taking a list
+> seems more sensible (e.g. comma separated, line-break separated, whatever).
+> Even if a template isn't converted to Lua yet, it could make use of a
+> generic Lua module to do the string split and iteration.
+
+This solution would be awkward when several parameters are related one to each other. For example, on the cite templates, you usually have several fields for each author (first name, last name, page link, ...) and they are easier to manage for a user if they are grouped.
+With lists, users would have to be careful and to be sure that several lists are coherent between each other.",1392795486,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"The foo1, foo2, foo3 etc. model exists in many templates, however in most cases the limit is quite low (when converted to Lua a user might have dropped the limit, no sure that is a good pattern). Only in cases where the value is for e.g. a table row do they have a high limit (up to 500 seems common).
+
+e.g. 
+
+{{Something
+|row1=..
+|row2=..
+|row3=..
+|=..
+
+such as {{TemplateBox@commons.wikimedia.org
+|p1=..
+|p2=..
+|p3=..
+|..
+
+However both for VisualEditor, TemplateData and any other modern program or programming language it is very visible that such dynamically named parameters are an unwanted pattern that should not be encouraged. It is hard to work with and only has downsides over alternatives (e.g. hard to re-order, requires hacks to implement in wikitext and lua, hard to document, hard to use).
+
+Especially now that we have Lua, specifying a parameter as taking a list seems more sensible (e.g. comma separated, line-break separated, whatever). Even if a template isn't converted to Lua yet, it could make use of a generic Lua module to do the string split and iteration.
+
+Also, in the interest of not implementing too soon and get stuck in a corner, I'd like to wait for VisualEditor to catch up with the features we've already recently added to TemplateData and see how those work out.",1381079832,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"This proposal is based mostly on the idea that if TemplateData exists for a template, then editors should not be permitted to add any parameters that are not already in TemplateData.  
+
+Rather than coding a variety of flexible naming/numbering schemes, it might make more sense to have a way to specify that a given template accepts (or does not accept) whatever parameters the editor chooses to name, regardless of what's in TemplateData.  If the TemplateData is complete and no unlisted parameters are useable, then editors could not add others.  If the TemplateData is incomplete, or if the number of parameters is unbounded, then editors could add whatever they wanted.",1375983254,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"In the module code they use # to represent a number placeholder.
+numbered_arguments = {
+    ['author#'] = true,
+    ['Author#'] = true,
+    ['author-first#'] = true,
+    ['author#-first'] = true,
+    ['author-last#'] = true,
+    ['author#-last'] = true,
+...
+}
+As you can see the number can be in various places.
+
+http://en.wikipedia.org/wiki/Module:Citation/CS1/Whitelist",1375823227,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"When implemented, this should also accept an empty string as the ""base"" (""author"" in original example above) to apply to unnamed (positional) parameters. Would be useful for some templates like [[pl:Template:Dopracować]] which currently can't be properly described using TemplateData.",1375805699,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V),"I don't know if this is possible, or if it's been requested elsewhese, but a few users on the French-language Wikipedia have suggested that, when the user has scrolled through the page and invoked VisualEditor via the keyboard shortcut, VE should automatically scroll to that same position on the page when it opens (similarly to what the section edit link does).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53217",1375799880,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-pe6m5b3pbhmfcnu7uep4,task_description,open
+VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V),We've done the complicated part of this in T293158.,1663959026,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pe6m5b3pbhmfcnu7uep4,task_subcomment,NA
+VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V),"The complication here is that while the VE view is similar to the read mode, it is not identical, so scrolling to the same pixel offset will not necessarily leave you at the same place. We could do an approximation by finding the nearest section heading and it's pixel offset from the top.",1468335875,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pe6m5b3pbhmfcnu7uep4,task_subcomment,NA
+VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V),"**misc2006** wrote:
+
+This should always be the case, no matter how the editor is invoked. ""User's position"" when the editor is opened should be *exactly* the same as before. Use case: I want to fix a simple spelling error, so I click on the edit link on the paragraph. Often, the content has now scrolled up/down a bit and I need to find the location of the spelling error again. This is surprisingly difficult/annoying (just give it a try).",1405932609,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pe6m5b3pbhmfcnu7uep4,task_subcomment,NA
+"VisualEditor: Repetition of the parameter (""box"") icon in the transclusion dialog is a bit heavy","<< Icons can be useful to help a user navigate an interface, however in the transclusion dialog, the same box-shaped icon with the thick left border is shown so many times (when editing a template with more than a few parameters) that it is obnoxious. Almost every occurrence should be removed, keeping it displayed at at most one or two places.--[[User:Wouterstomp|WS]] ([[User talk:Wouterstomp|talk]]) 11:22, 6 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49833",1375794000,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-tb2wtwoarrokjafpdi3e,task_description,resolved
+"VisualEditor: Repetition of the parameter (""box"") icon in the transclusion dialog is a bit heavy",I disagree with this - the icon is used to identify which elements are parameters. Particularly in future they may be contrasted with sub-items such as images or sub-templates that are included in parameters but separately editable within the transclusion editor.,1375795854,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-tb2wtwoarrokjafpdi3e,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"[15:52] <T13> VE Question.  How is VE currently set up to handle users that have opted-in to gadgets that modify the editing window such as wikEd?
+...
+[15:54] <T13> Do those gadgets still load even though the hooks they use don't exist? Shouldn't having VE enabled disable those gadgets and grey out the optiobs for them in the gadgets tab of preferences?
+[15:56] <T13> I'm guessing some of the ""VE"" bugs are caused by these gadgets trying to do what they no longer can.
+...
+[16:06] <mooeypoo> T13: I think most of the edit-related gadgets work on the action=edit condition, and ve goes with action=vedit
+[16:07] <mooeypoo> but I am not sure :) you'll be safer getting the answer from the VE team
+[16:09] <MatmaRex> T13: i'm not on the team, but i'm pretty sure that's the reason
+[16:10] <MatmaRex> T13: basically there are two ways to detect if we're inedit mode - either look if 'action' is 'edit' or 'submit', or look for some elements that are parts of theedit form, like #wpTextbox1 (the main textbox)
+[16:10] <MatmaRex> VE avoids them both
+[16:11] <T13> I've seen questions on WP:THQ with a link to a screenshot of wikEd and the user thinking they were using VE.  So, I was curious how it was handled.
+[16:11] <T13> I'll add the suggestion to gray out the unusable with VE gadgets 
+[16:11] <mooeypoo> Ah, *that* kind of user errors. Hm. Not sure how you can handle those other than politely correct the user's false assumption
+[16:11] <T13> On Bugzilla...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375737720,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-u3h65rxvz452mowrmajb,task_description,open
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"Hmm. Not totally convinced by this - (a) because this is inherently transitional as gadgets are updated to work with VisualEditor, and (b) because disabling gadgets that work fine, just not in all places, seems a bit unfair. Re-titling and moving to the Gadgets pile, however.",1383282348,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"Working links:
+
+https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(current).png
+
+https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(proposed).png",1377871417,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"(In reply to comment #1)
+> Not sure what the bug is, here?
+> 
+> Gadgets can be written to work with VisualEditor, but gadgets not written to
+> do so won't work, and dated (and so now misleading) advertising on behalf of
+> these gadgets that it works with ""the editor"" will confuse people.
+> 
+> As normal, gadget authors and maintainers should make sure that they re-label
+> their gadgets to avoid this confusion.
+> 
+> Or am I missing something?
+
+I'm sorry James, I missed your question.  I've uploaded a couple screenshots of what I'm thinking (although I'm thinking this may require a change in the gadgets extension first on second thought).
+
+Currently, the ""Editing"" section of the gadgets tab on enwp looks like:
+   [[commons:File:Special_Preferences_mw-prefsection-gadgets_%28current%29.png]]
+
+What I'm proposing, is that when VisualEditor is active for the user, it should look like:
+   [[commons:File:Special_Preferences_mw-prefsection-gadgets_%28proposed%29.png]]
+
+With the options for things like dot's highlighter and wikiEd grayed out so they can't be clicked (and defaulted to off).",1377865283,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,Closing as INVALID as no response after 3 weeks (but happy to reconsider if I've mis-understood).,1377828505,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"Not sure what the bug is, here?
+
+Gadgets can be written to work with VisualEditor, but gadgets not written to do so won't work, and dated (and so now misleading) advertising on behalf of these gadgets that it works with ""the editor"" will confuse people.
+
+As normal, gadget authors and maintainers should make sure that they re-label their gadgets to avoid this confusion.
+
+Or am I missing something?",1375747264,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+VisualEditor: Backspace should not delete list and line in same action,"**Author:** `mcdevitd`
+
+**Description:**
+Typically, the expected behavior from hitting backspace at the beginning of a list line is to remove the bullet/number at that indent level so it is no longer a list, and no more. VisualEditor will completely delete the line itself and move the text to the end of the previous line. This is not how OpenOffice or Word works.",1375729680,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vrzpbb2v2s74ml5e53ww,task_description,open
+VisualEditor: Backspace should not delete list and line in same action,"Currently (for years), pressing backspace in LibreOffice makes the paragraph exit the list **only if it is empty** (note we may split an ordered list in OpenDocuments, whereas we cannot in wikitext). Else, the behavior is pretty consistent with VisualEditor (first Backspace press: the bullet is hidden — no equivalence in VE; second Backspace press: the paragraph is merged with previous element).",1650765676,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-vrzpbb2v2s74ml5e53ww,task_subcomment,NA
+VisualEditor: Backspace should not delete list and line in same action,"Currently (for years), backspace LibreOffice make the paragraph exit the list only if it is empty. Else, the behavior is pretty consistent with VisualEditor (first Backspace press: the bullet is hidden — no equivalence in VE; second Backspace press: the paragraph is merged with previous element).",1650765546,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-vrzpbb2v2s74ml5e53ww,task_subcomment,NA
+VisualEditor: Backspace should not delete list and line in same action,"Agreed. For
+
+| <ol><li><p>|</p></li><li><p>Foo</p></li></ol>
+
+… backspace at the cursor position indicated should convert the document into:
+
+| <p>|</p><ol><li><p>Foo</p></li></ol>
+
+… with the initial <p> being a slug.
+
+For nested list items we should pop to the next level:
+
+| <ol><li><p>Foo</p></li><li><ol><li><p>|</p></li><li><p>Foo</p></li></ol></li></ol>
+
+->
+
+
+| <ol><li><p>Foo</p></li><li><p>|</p></li><li><ol><li><p>Foo</p></li></ol></li></ol>
+
+I think?",1394479004,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vrzpbb2v2s74ml5e53ww,task_subcomment,NA
+VisualEditor: Unindent should not remove lists,"**Author:** `mcdevitd`
+
+**Description:**
+The expected behavior in most word processors (Word and OpenOffice) is that the user can unindent (shift-tab) only to get to the initial list indent level but it should not actually delete the bulleting/numbering itself when you to the end. In VisualEditor, unindenting once too many times can remove the initial bullet/number entirely.
+
+This becomes particularly annoying when (because of the behavior described in bug 48051) you accidentally split a list into two lists which can't be fixed clicking the list button again to re-add the bullet/number.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375726080,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nog34g36rvrxth34pzwz,task_description,open
+VisualEditor: Unindent should not remove lists,(Still valid in current VE; is this really normal priority?),1426861555,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-nog34g36rvrxth34pzwz,task_subcomment,NA
+VisualEditor: Unindent should not remove lists,*** Bug 56344 has been marked as a duplicate of this bug. ***,1384846149,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nog34g36rvrxth34pzwz,task_subcomment,NA
+VisualEditor: Unindent should not remove lists,"**mcdevitd** wrote:
+
+(In reply to comment #1)
+> (In reply to comment #0)
+> 
+> > This becomes particularly annoying when (because of the behavior described in
+> > bug 48051) you accidentally split a list into two lists which can't be fixed
+> > clicking the list button again to re-add the bullet/number.
+> 
+> ""Undo"" fixes that instantly, of course.
+
+I wasn't trying to say that it is unfixable. I was just pointing out that the current list behavior means that the way most(?) people might naturally try to correct losing their bulleting/numbering would only compound the error. (""Undo"" fixes almost anything, of course, except frustration and time wasted.)",1375754135,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nog34g36rvrxth34pzwz,task_subcomment,NA
+VisualEditor: Unindent should not remove lists,"(In reply to comment #0)
+> The expected behavior in most word processors (Word and OpenOffice) is that
+> the user can unindent (shift-tab) only to get to the initial list indent
+> level but it should not actually delete the bulleting/numbering itself when
+> you to the end. In VisualEditor, unindenting once too many times can remove
+> the initial bullet/number entirely.
+
+This was a deliberate choice, though I can't remember why (it was over a year ago that this was implemented). We should reconsider.
+
+> This becomes particularly annoying when (because of the behavior described in
+> bug 48051) you accidentally split a list into two lists which can't be fixed
+> clicking the list button again to re-add the bullet/number.
+
+""Undo"" fixes that instantly, of course.",1375747948,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nog34g36rvrxth34pzwz,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Users are requesting VE August update (https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/August_2013_update) to be deployed in on hewiki.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**URL**: https://he.wikipedia.org/wiki/%D7%A9%D7%99%D7%97%D7%AA_%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:%D7%A2%D7%A8%D7%9F#.D7.A9.D7.99.D7.A0.D7.95.D7.99_.D7.91.D7.9E.D7.99.D7.A7.D7.95.D7.9D_.D7.94.D7.A7.D7.99.D7.A9.D7.95.D7.A8_.22.D7.A2.D7.A8.D7.99.D7.9B.D7.94_.D7.91.D7.A7.D7.95.D7.93_.D7.9E.D7.A7.D7.95.D7.A8.22_-_.D7.9B.D7.9E.D7.95_.D7.91.D7.95.D7.95.D7.99.D7.A7.D7.99.D7.A4.D7.93.D7.99.D7.94_.D7.94.D7.90.D7.A0.D7.92.D7.9C.D7.99.D7.AA",1375721160,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_description,resolved
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",Finally done; sorry for the delay.,1381515689,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Change 87645 merged by Reedy:
+Switch VisualEditor to secondary status on hewiki
+
+https://gerrit.wikimedia.org/r/87645",1381515513,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","(In reply to comment #14)
+> Change 87645 had a related patch set uploaded by Jforrester:
+> Switch VisualEditor to secondary status on hewiki
+> 
+> https://gerrit.wikimedia.org/r/87645
+
+Will try to schedule this soon.",1380938287,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Change 87645 had a related patch set uploaded by Jforrester:
+Switch VisualEditor to secondary status on hewiki
+
+https://gerrit.wikimedia.org/r/87645",1380938237,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","(In reply to comment #12)
+> Thanks for adding the welcome message. 
+> 
+> I know there are discussions regarding these changes[1], but the change of
+> the tab order (Edit and Edit source) is important for he wikipedia and Erik
+> isn't totally against it [only ambivalent] :)
+> 
+> [1]
+> http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2013-September/
+> 000419.html
+
+To speak for Erik (:-)), his ambivalence is about changing it *globally*, not about changing it on a given wiki.
+
+There's scope for a lot of concern about changing it for some wikis and not others, and so having a very inconsistent configuration for people that use multiple wikis. I think that it's probably OK to do this, but I really haven't come to ""a decision"". However, it's unfair to hewiki to have you hanging around waiting for me to make up my mind, and I'm sorry about this. :-(
+
+> Since VE is enabled only in the main NS and user NS, for editors who also
+> edit in other namespaces, addition of the VE edit tab ""in the middle"" may
+> cause confusion.
+
+That is certainly one argument. (Though surely it only applies to people with a very narrow window, or the minority who use the Monobook skin? For the others, the VisualEditor tab sits prone in namespaces they can use it in, and otherwise they get the tab they currently have to use until Flow is fully rolled out). But I see your point.
+
+> For consistency the edit source option should be alway the first
+> option [in order], while VE edit should be second.
+
+An alternative argument is that it's right that the first and primary tab is always the one they can use, and there may or may not be a secondary editor tab depending on the nature of the content they're editing.
+
+Of course, we can partially 'fix' this by enabling VisualEditor in all the other namespaces that it's safe for (at the least, File, Portal, Category, Help; not Project, as that's normally signed and so should wait with *_Talk for Flow). Not sure.
+
+In the mean time, I'm happy to move hewiki to [ Edit source | Edit ] for the time being, and would really welcome thoughts on my other points above.",1380937661,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Thanks for adding the welcome message. 
+
+I know there are discussions regarding these changes[1], but the change of the tab order (Edit and Edit source) is important for he wikipedia and Erik isn't totally against it [only ambivalent] :)
+
+Since VE is enabled only in the main NS and user NS, for editors who also edit in other namespaces, addition of the VE edit tab ""in the middle"" may cause confusion. For consistency the edit source option should be alway the first option [in order], while VE edit should be second.
+
+----
+[1] http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2013-September/000419.html",1380883041,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Change 77269 merged by jenkins-bot:
+Enable VisualEditor beta welcome notice for all wikis
+
+https://gerrit.wikimedia.org/r/77269",1378927706,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","[Sorry for the delay in responding.]
+
+The beta welcome message is now queued up to go out on all wikis with the next release when available.
+
+We're still not decided on the way forward for the edit source/edit labelling split, so this is delayed until we have a proper answer. Sorry.",1378770465,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","We are now in September so enough time have passed since August change, and the community have voted for deploying the changes. Please let us know when this change is planned for deployment.",1378147154,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","There is is large support for the change in the 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=14551521#.D7.94.D7.97.D7.9C.D7.A4.D7.AA_.D7.9E.D7.99.D7.A7.D7.95.D7.9D_.D7.94.D7.A7.D7.99.D7.A9.D7.95.D7.A8_.22.D7.A2.D7.A8.D7.99.D7.9B.D7.94_.D7.91.D7.A7.D7.95.D7.93_.D7.9E.D7.A7.D7.95.D7.A8.22_.D7.A2.D7.9D_.D7.9E.D7.99.D7.A7.D7.95.D7.9D_.D7.A7.D7.99.D7.A9.D7.95.D7.A8_.22.D7.A2.D7.A8.D7.99.D7.9B.D7.94.22_-_.D7.9B.D7.9E.D7.95_.D7.91.D7.95.D7.95.D7.99.D7.A7.D7.99.D7.A4.D7.93.D7.99.D7.94_.D7.94.D7.90.D7.A0.D7.92.D7.9C.D7.99.D7.AA",1377842346,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",All of these,1377020909,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Hey,
+
+Which of the bits of the update do you mean?
+
+1. The re-ordered tabs and section edit links, so that the VE tab is second?
+2. Giving a welcome message when you open VisualEditor for the first time?
+3. Adding ""beta"" as a suffix after the VisualEditor tab and section edit link?
+4. Changing ""edit"" to ""edit source"" on non-VisualEditor pages for consistency?
+5. Removing the animation on section edit links?
+
+All of these? Items 4 and 5 are already done.",1376948752,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",is there any progress with the request?,1376848108,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",Gerrit change 77269 will handle part of this. They were just waiting on translations of the messages before enabling it.,1375862146,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",added in the url field.,1375792847,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","(In reply to comment #0)
+> Users are requesting VE August update
+> (https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/August_2013_update) to
+> be deployed in on hewiki.
+
+Please provide a link to these requests, if possible.",1375791382,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",Please mark the targeted milestone when it is known. Thanks,1375721827,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+VisualEditor: Empty HTML elements are not identifiable,"Slightly related to bug 51322 
+
+Take the Link FA templates on https://en.wikipedia.org/wiki/The_Adventures_of_Tintin?veaction=edit for instance. 
+
+These produce empty elements, and don't qualify under 'solely metadata' of bug 51322, even though they are somewhat similar to it.
+
+The templates are represented with the char: ↵
+Using the arrow keys to cursor trough this sequence will sometimes produce the template editor indicator. However their is little identifying these templates to the user and due to the interspersed ↵, users think they should be deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375720020,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-bm4l7dozmqtublm7xcao,task_description,resolved
+VisualEditor: Empty HTML elements are not identifiable,"Merging with bug 49806 (though non-transclusion empty HTML blocks do happen too).
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1393529166,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bm4l7dozmqtublm7xcao,task_subcomment,NA
+VisualEditor: Empty HTML elements are not identifiable,"(In reply to comment #0)
+> The templates are represented with the char: ↵
+
+Actually, that's representing the meaningless wikitext of the newline after the template.",1380753594,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bm4l7dozmqtublm7xcao,task_subcomment,NA
+"VisualEditor: Floated node's action icon (e.g. for template) appearing in wrong location, relative to its initial position, not its actual position","From http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Quote_box
+
+In the adventures of tintin 
+http://en.wikipedia.org/wiki/The_Adventures_of_Tintin?veaction=edit
+
+the first {{quote box}} has been pushed down by the info box. The transclusion icon for this appears appear where the quote box was initially (just below the History section header on the right hand side) not where it actually appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51548",1375712940,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-g7kzupvlt4lakd72su4u,task_description,resolved
+"VisualEditor: Floated node's action icon (e.g. for template) appearing in wrong location, relative to its initial position, not its actual position",Not any more!,1519404104,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-g7kzupvlt4lakd72su4u,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?
+
+Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".
+
+We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.
+
+```
+aftv5-last-filter: null
+ccmeonemails: 0
+cols: ""120""
+date: ""mdy""
+diffonly: ""1""
+disablemail: 0
+disablesuggest: 0
+echo-email-format: ""html""
+echo-email-frequency: 0
+echo-notify-show-link: true
+echo-show-alert: true
+echo-subscriptions-email-article-linked: false
+echo-subscriptions-email-edit-thank: false
+echo-subscriptions-email-edit-user-talk: 1
+echo-subscriptions-email-mention: false
+echo-subscriptions-email-other: false
+echo-subscriptions-email-page-review: false
+echo-subscriptions-email-reverted: false
+echo-subscriptions-email-system: true
+echo-subscriptions-web-article-linked: ""1""
+echo-subscriptions-web-edit-thank: true
+echo-subscriptions-web-edit-user-talk: true
+echo-subscriptions-web-mention: true
+echo-subscriptions-web-other: true
+echo-subscriptions-web-page-review: true
+echo-subscriptions-web-reverted: true
+echo-subscriptions-web-system: true
+editfont: ""default""
+editondblclick: 0
+editsection: 1
+editsectiononrightclick: 0
+enotifminoredits: 0
+enotifrevealaddr: 0
+enotifusertalkpages: 1
+enotifwatchlistpages: 0
+ep_bulkdelcourses: true
+ep_bulkdelorgs: false
+ep_showdyk: true
+ep_showtoplink: false
+extendwatchlist: 0
+fancysig: ""1""
+flaggedrevseditdiffs: true
+flaggedrevssimpleui: 1
+flaggedrevsstable: 0
+flaggedrevsviewdiffs: false
+forceeditsummary: ""1""
+gadget-BugStatusUpdate: ""1""
+gadget-DRN-wizard: 1
+gadget-HotCat: ""1""
+gadget-Navigation_popups: ""1""
+gadget-NoAnimations: ""1""
+gadget-PrintOptions: ""1""
+gadget-ReferenceTooltips: 1
+gadget-UTCLiveClock: ""1""
+gadget-addsection-plus: ""1""
+gadget-charinsert: 1
+gadget-contribsrange: ""1""
+gadget-edittop: ""1""
+gadget-exlinks: ""1""
+gadget-metadata: ""1""
+gadget-mySandbox: 1
+gadget-purgetab: ""1""
+gadget-teahouse: 1
+gadget-widensearch: ""1""
+gadget-wikEd: ""1""
+gadget-wikEdDiff: ""1""
+gender: ""male""
+gettingstarted-task-toolbar-show-intro: """"
+hideminor: 0
+hidepatrolled: 0
+imagesize: 2
+justify: 0
+language: ""en""
+math: ""6""
+mfWatchlistFilter: ""all""
+mfWatchlistView: ""feed""
+minordefault: 0
+newpageshidepatrolled: 0
+nocache: 0
+noconvertlink: 0
+norollbackdiff: 0
+numberheadings: 0
+previewonfirst: 0
+previewontop: 1
+rcdays: 7
+rclimit: 50
+rcshowwikidata: ""1""
+rememberpassword: 0
+rows: ""30""
+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: ""1""
+searchNs15: false
+searchNs100: false
+searchNs101: false
+searchNs108: false
+searchNs109: false
+searchNs446: false
+searchNs447: false
+searchNs710: false
+searchNs711: false
+searchNs828: false
+searchNs829: false
+searchlimit: 20
+showhiddencats: ""1""
+showjumplinks: 1
+shownumberswatching: 1
+showtoc: 1
+showtoolbar: 1
+skin: ""vector""
+stubthreshold: ""2000""
+thumbsize: 4
+timecorrection: ""ZoneInfo|120|Europe/Amsterdam""
+uls-preferences: """"
+underline: 2
+usebetatoolbar: 1
+usebetatoolbar-cgd: 1
+useeditwarning: 1
+uselivepreview: 0
+usenewrc: ""1""
+userjs-curationtoolbar: ""hidden""
+variant: ""en""
+vector-collapsiblenav: 1
+vector-simplesearch: 1
+visualeditor-betatempdisable: 0
+visualeditor-enable: 1
+watchcreations: 1
+watchdefault: 0
+watchdeletion: 0
+watchlistdays: 3
+watchlisthideanons: 0
+watchlisthidebots: 0
+watchlisthideliu: 0
+watchlisthideminor: 0
+watchlisthideown: 0
+watchlisthidepatrolled: 0
+watchmoves: 0
+wikilove-enabled: 1
+wllimit: 250
+wlshowwikibase: ""1""
+```
+--------------------------
+**See Also**:
+{T29471}",1375702860,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-yfjwr3je2btidmhmuccx,task_description,open
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","@Samwilson I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies.
+
+This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).",1519100508,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Also, just to note that `email-blacklist` is another outlier and is actually an array.",1519099509,PHID-USER-hlhhe6qw6qfkl7wyfhxk,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?",1519098837,PHID-USER-hlhhe6qw6qfkl7wyfhxk,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code.
+
+I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479716929,PHID-USER-p6gpvwnc6ske65oxuoof,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code.
+
+I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479715550,PHID-USER-p6gpvwnc6ske65oxuoof,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers.
+
+However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that.
+
+So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:
+
+```
+rclimit: 50
+rows: ""30""
+searchNs0: true
+searchNs1: false
+..
+searchNs10: ""1""
+searchNs11: false
+searchNs12: false
+searchNs13: false
+searchNs14: ""1""
+```
+
+Quite the mix up.
+
+Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1519100319,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers.
+
+However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that.
+
+So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:
+
+```
+rclimit: 50
+rows: ""30""
+searchNs0: true
+searchNs1: false
+..
+searchNs10: ""1""
+searchNs11: false
+searchNs12: false
+searchNs13: false
+searchNs14: ""1""
+```
+
+Quite the mix up.
+
+Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1423877781,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)",I have had similar difficulties and personally prefer booleans wherever possible.  They're more reliable and less likely to be unpredictable.  They are either true or false or they're invalid.,1423875937,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1)
+> ...
+> normalizing values of boolean prefs to true/false just before building this
+> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.
+
++1 for normalizing boolean preferences so that either
+> `mw.user.options.get( 'anyBooleanPreference' ) === true`
+> `mw.user.options.get( 'anyBooleanPreference' ) === false`
+and nothing else.
+
+The current behavior is ***very*** inconvenient:
+* If I do not set `$wgDefaultUserOptions['usebetatoolbar']`
+(i.e., if I use WikiEditor's default):
+  - If I don't change the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === null`
+  - If I enable the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === ""1""`
+* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]):
+  - If I don't change the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === 1`
+  - If I disable the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!)
+* On English Wikipedia
+  - If I don't change the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === 1`
+  - If I disable the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!)
+
+[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1466864706,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1)
+> ...
+> normalizing values of boolean prefs to true/false just before building this
+> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.
+
++1 for normalizing boolean preferences so that either
+> mw.user.options.get( 'anyBooleanPreference' ) === true
+> mw.user.options.get( 'anyBooleanPreference' ) === false
+and nothing else.
+
+The current behavior is ***very*** inconvenient:
+* If I do not set $wgDefaultUserOptions['usebetatoolbar']
+(i.e., if I use WikiEditor's default):
+  - If I don't change the preference
+    mw.user.options.get( 'usebetatoolbar' ) === null
+  - If I enable the preference
+    mw.user.options.get( 'usebetatoolbar' ) === ""1""
+* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]):
+  - If I don't change the preference
+    mw.user.options.get( 'usebetatoolbar' ) === 1
+  - If I disable the preference
+    mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!)
+* On English Wikipedia
+  - If I don't change the preference
+    mw.user.options.get( 'usebetatoolbar' ) === 1
+  - If I disable the preference
+    mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!)
+
+[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","The integer came from $wgDefaultSettings. Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.",1375735877,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them).
+
+Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case.
+
+I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",1375703425,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"VisualEditor: In the save dialog, also show the ""switch to wikitext"" button in the wikitext diff so they can fix last-minute issues","when saving, there is possibility to check the result visually. allow to edit it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T52687}",1375606860,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-escar4ypn3o4hbygakj4,task_description,open
+"VisualEditor: In the save dialog, also show the ""switch to wikitext"" button in the wikitext diff so they can fix last-minute issues","(In reply to comment #2)
+> agreed, james, that would be desireable. but is for sure a very different
+> feature not at all helping out when the diff reveals visual editor did
+> something unexpected.
+It does actually help: you can close the save dialog and switch to source mode, but this is not very discoverable.
+
+Maybe we should consider adding a button to the diff preview that sends you straight to source mode?",1390857782,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-escar4ypn3o4hbygakj4,task_subcomment,NA
+"VisualEditor: In the save dialog, also show the ""switch to wikitext"" button in the wikitext diff so they can fix last-minute issues","agreed, james, that would be desireable. but is for sure a very different feature not at all helping out when the diff reveals visual editor did something unexpected.",1377845408,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-escar4ypn3o4hbygakj4,task_subcomment,NA
+"VisualEditor: In the save dialog, also show the ""switch to wikitext"" button in the wikitext diff so they can fix last-minute issues","This is an interesting idea, but I think bug 50687 (with a button to switch to the wikitext editor) is probably more discoverable and more useful for some situations.",1377815545,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-escar4ypn3o4hbygakj4,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,"Greg also reproduced this.  He sees a superscript, but I have an additional issue, that the beta is roughly the same horizontal position.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375503180,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-yr55vawmutvv7jim7igv,task_description,resolved
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,*** Bug 71651 has been marked as a duplicate of this bug. ***,1412495213,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,"Upstream bug has been marked as fixed since 2014-06-19 15:05:07 (for FF33 - currently in Aurora, which seems to be fixed to me), marking this as fixed as well.",1408815618,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,Seems to be already reported as https://bugzilla.mozilla.org/show_bug.cgi?id=727125,1401826563,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,Filed as https://bugzilla.mozilla.org/show_bug.cgi?id=1009874,1400018028,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,Firefox-specific rendering bug.,1375765683,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,"Created attachment 13057
+Screenshot of beta with overline
+
+This is from a few hours ago on enwiki.  It is reproducible (try a fresh account on enwiki), almost 100% of the time (one load seemed not to do it).
+
+**Attached**: {F11270}",1375503720,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects.
+
+However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.
+
+There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.
+
+As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a:
+IF editor=""VisualEditor"" THEN do X ELSE do Y
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375469280,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-lusyegvtclbce7nfsesb,task_description,open
+"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","I don't think there should be a control for separate interface messages.
+
+However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.",1378320091,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lusyegvtclbce7nfsesb,task_subcomment,NA
+"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","Yes, that does sound far simpler to implement! More difficult to keep the two in synch, but I suppose you can't have everything.",1375472876,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-lusyegvtclbce7nfsesb,task_subcomment,NA
+"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example.
+
+This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)",1375470158,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-lusyegvtclbce7nfsesb,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","What it says on the tin: The transclusion editor should have a ""cancel"" button next to ""Apply changes"". This would close the editor without saving any changes.
+Possibly it should require a confirmation if one or more templates have been selected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52386",1375460340,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_description,resolved
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","(In reply to John Broughton from comment #8)
+> If in fact the link tool and the Formula window are outside the scope of this>
+> bug, feel free to close the bug
+
+They are. This bug is about dialogs.
+
+Design questions about non-dialogs is a distinct question – raising another ticket is probably a good idea if you think they should be changed.",1410807070,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","As noted previously, there no ""Cancel"" button on the link tool (dialog? insert window?). Also, there is no ""Cancel"" button on the Formula dialog (insert window?). 
+
+I'm reopening this bug because otherwise - in ""Resolved"" status - this bug is much more likely to be ignored. If in fact the link tool and the Formula window are outside the scope of this bug, feel free to close the bug - then we'll know that we need to open a new, separate bug to address those two issues.",1407699259,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","There is still no ""Cancel"" button on the link tool.",1407651731,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""",This was done as part of the window redesign work.,1406063829,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","A user at en.wp has reported that they were unaware that the ^ button on the save page dialog would return them to the article. Consequently they were under the impression that the only options were to preview the changes, save the changes or abort the edit, i.e. there was no way to go back and make addition changes or fix ones they had already made.
+
+A cancel button as discussed in this bug would solve this, although I think labelling it something like ""return to editing"" would be better than ""cancel"" here (which could imply discarding the edit).",1377683762,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","I think a cancel button makes perfect sense from a UX point of view for dialogs.
+
+Closing would be an alias of cancel, but that's not the primary flow for a user.
+
+Closing windows is always a bit of awkward and uncertain action to take.",1375493049,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","(In reply to comment #2)
+> Yes, I've seen it mentioned a couple  of times that people aren't sure what
+> state clicking the ""X"" will leave things in. Will it cancel everything
+> they've done, cancel only unfinished/unapplied changes, or close with
+> everything in its current state finished or not.
+
+* A ""rubbish bin"" icon (on lightweight inspectors, but not dialogs) is Option 1.
+* An ""X"" icon (on dialogs, but not inspectors) is Option 2.
+* The ""apply changes"" button (on dialogs, but not inspectors) is Option 3.
+
+Clearly this isn't ""obvious"" enough; we should consider what more we can do.",1375492557,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","Yes, I've seen it mentioned a couple  of times that people aren't sure what state clicking the ""X"" will leave things in. Will it cancel everything they've done, cancel only unfinished/unapplied changes, or close with everything in its current state finished or not.",1375486468,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","This functionality is currently provided by the ""X"" in the top-right corner (as for all dialogs). Is a duplicate button needed?",1375482783,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","User:Wouterstomp at en.wp suggests that in the media selection dialog, the full name of an image should be shown in a tooltip when you hover over it. Either for all images or only those whose name is too long to be shown in full beneath the image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375458480,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-erdij6gvcjcryxt3xqjp,task_description,resolved
+"In the VisualEditor media selector, show the name of each file so it can be identified",Checked in betalabs.,1422573163,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","Change 183729 merged by jenkins-bot:
+Add filename to the media dialog
+
+[[https://gerrit.wikimedia.org/r/183729]]",1421430202,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","Change 183729 had a related patch set uploaded (by Mooeypoo):
+Add filename to the media dialog
+
+[[https://gerrit.wikimedia.org/r/183729]]
+
+#patch-for-review",1420760594,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified",Or not.,1411746458,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","Since no one disagrees, I'm going to make that happen.",1411743607,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","I think a better place to display the name would be in the ""Media settings"" dialog. Right now, when inserting an image, you don't even know what you're inserting (neither a file name nor a thumbnail is shown in the dialog).
+
+That would also provide a better place for the ""Choose a different image"" button, which is now awkwardly placed in the bottom-left corner.",1410955390,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","This would be nice for desktop users, but not so good for mobile (tablet/phone) users who are using touch to navigate. Maybe something else for them, like displaying the details of the file on a page before inserting?",1375487540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected","en.wp editor GermanJoe suggests that if you try to add a template not in the transclusion editor's list of known templates that it should give a warning or ""are you sure?"" message.
+
+Such a message would note that very new templates might not appear in he list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375435380,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-qjdwtbzzs25aurzlowwr,task_description,resolved
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected","We now have a warning which is probably sufficient:
+{F13652706}",1518444836,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected","(In reply to Alex Monk from comment #2)
+> Unknown template = template with no TemplateData?
+
+(In reply to Alex Monk from comment #3)
+> Non-existent?
+
+It means ""the API didn't claim to know about it existing"". Given MediaWiki's… awkwardness about knowing whether or not a page actually exists I didn't want to assume something when I wrote it. :-)",1414103160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected",See comment #1?,1414099109,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected",Non-existent?,1414097282,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected",Unknown template = template with no TemplateData?,1414096922,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected","This feels like it could be a bit irritating as a modal alert, but maybe we could come up with something as effective whilst less in-your-face.",1375748014,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Currently the the transclusion editor's list of templates includes /Doc and other subpages of templates that are not themselves actual templates.
+
+At https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_2#Removing_template_subpages_from_the_template_selection_list.3F there was a discussion about this which suggested possible ways forward:
+* Exclude all subpages except those explicitly marked as templates, e.g by magic word or category
+* Include all subpages except those explicitly marked as not being templates, e.g. by magic word or category
+
+See also:
+* {T52512}
+* {T58516}",1375434960,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_description,resolved
+Transclusion dialog should not suggest documentation sub pages as templates,"Change 483205 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWTemplateTitleInputWidget: Filter out templates named '…/doc'
+
+[[https://gerrit.wikimedia.org/r/483205]]",1548973792,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,">>! In T54448#4888682, @Johan wrote:
+> Is this done and will be deployed next week? (It's been added to Tech News.) I can't see that in the task, but I could be missing something?
+
+Nope, sorry, code still going through review. I'll go poke it now.",1547752559,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Is this done and will be deployed next week? (It's been added to Tech News.) I can't see that in the task, but I could be missing something?",1547743671,PHID-USER-go2ym6ta2zn6ofdsrqnx,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Thanks!
+I think it worth a Tech News post since some communities may see the difference. It is a good opportunity to highlight `templatedata-doc-subpage` too is not already known. ",1547561928,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,I think it worth a Tech News post since some communities may see the difference. It is a good opportunity to highlight `templatedata-doc-subpage` too is not already known. ,1547561919,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,">>! In T54448#4876695, @Trizek-WMF wrote:
+> @Jdforrester-WMF, how this would be deployed? How your change will identify language variants for `/doc`?
+
+It'd be a train patch. Communities already (can) define the template documentation sub-page for the TemplateData extension via the `templatedata-doc-subpage` message, and this just re-uses that, which defaults to `foo` (so if you create `Template:Foo/doc` it'll be hidden, but `Template:Foo/I have another sub-page to be confusing` won't). Not merged yet though. I don't think this'd be worth a Tech News post.",1547492363,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"@Jdforrester-WMF, how this would be deployed? How your change will identify language variants for `/doc`?",1547460974,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Change 483205 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] MWTemplateTitleInputWidget: Filter out templates named '…/doc'
+
+[[https://gerrit.wikimedia.org/r/483205]]",1547062350,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Change 464718 **merged** by jenkins-bot:
+[mediawiki/extensions/TemplateData@master] Don't store templatedata pageprop on doc-subpage
+
+[[https://gerrit.wikimedia.org/r/464718]]",1540999311,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Change 464718 had a related patch set uploaded (by Krinkle; owner: Krinkle):
+[mediawiki/extensions/TemplateData@master] Don't store templatedata pageprop on doc-subpage
+
+[[https://gerrit.wikimedia.org/r/464718]]",1538687276,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,">>! In T54448#1991488, @maiden_taiwan wrote:
+> Suggestion: allow the wiki administrator to designate a particular subpage string, such as `doc`, as the official place to keep TemplateData. Then VisualEditor can intelligently and unambiguously filter these pages out. See T125222.
+
+(This is an old comment but I think it would be helpful.) TemplateData already has a message for this in the configuration, `MediaWiki:Templatedata-doc-subpage`, so implementing solutions based on that shouldn’t be a problem.",1531613135,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"[[ https://hu.wikipedia.org/w/index.php?title=Vars%C3%A1nyi_Istv%C3%A1n&diff=prev&oldid=19944747 | An example ]]: I accidentally //{{Nemzetközi katalógusok/doc}}// instead of //{{Nemzetközi katalógusok}}//, because I was not thoughtful enough. We should find a way to avoid the problem.",1526835132,PHID-USER-qdbrv6swdxlgemqwwbuw,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,">>! In T54448#1991488, @maiden_taiwan wrote:
+> Suggestion: allow the wiki administrator to designate a particular subpage string, such as `doc`, as the official place to keep TemplateData. Then VisualEditor can intelligently and unambiguously filter these pages out. See T125222.
+
+This one could work! On pt-wiki we use ""doc"" as the documentation subpage and ""dados"" as the TemplateData. Maybe blacklisting both of them could help VisualEditor interpreting them as **not** templates to be transcluded. 
+I don't think that //""excluding all subpages except those explicitly marked as templates""// would be a good idea, because there are plenty of templates (Info/Patologia, Info/Grupo étnico, Info/Facção de conflito etc.) located on subpages.",1479326628,PHID-USER-46kgwzejnrokds6ov24i,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Suggestion: allow the wiki administrator to designate a particular subpage string, such as `doc`, as the official place to keep TemplateData. Then VisualEditor can intelligently and unambiguously filter these pages out. See T125222.",1454445652,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Another option: instead of filtering, use sorting by usage (group by on templatelinks) instead of alphabetic sorting.",1439039697,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,I think we have simple way to filter out subpages of templates.,1439039410,PHID-USER-ipgdr6xrndwpztdrubk4,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"> Suggested possible ways forward:
+> 
+> * Exclude all subpages except those explicitly marked as templates, e.g by magic word or category
+> * Include all subpages except those explicitly marked as not being templates, e.g. by magic word or category
+
+Neither of these options are imho maintainable or author-friendly. Alternative ideas (from T98562).
+
+> * Filter out /doc (hardcoded).
+>  * Principally not as ugly as one might think, since TemplateData does this as well. Though TemplateData only uses that hardcoded value to discover related pages in the graphical interface. It is in no way enforced server-side or encouraged in its interface when inserting/editing template data.
+>  * We'd have to filter it client-side, which means the number of results shown is inconsistent. To avoid false positives with template names that actually end in ""/doc"", we'd only remove results if the other title is also in the list. (E.g. ""Template:Dac/duc/doc"" or something like that.)
+> * Filter out results that are transcluded in other results.
+>  * Requires an additional query somewhere, but might be a smart way to do it. We'd only omit results that are transcluded by others. So ""Template:Foo/doc"" would be omitted because according to the link tables, ""Template:Foo"" (also in the suggestions) transcludes ""Template:Foo/doc"". This doesn't work well because documentation pages themselves often make use of various other templates. So any template used in the preview, examples, or documentation would never show up in the suggestions.
+> * Filter out results that transclude template data.
+>  * Not sure how this would work, but since the same duplication is also present in the page-property index (which is where template data is stored), we can detect that Foo and Foo/doc both have (the same) template data. We may be able to de-duplicate results that way (and pick the one that sorts higher, or the one with a shorter name, aka not the helper page that tends to be a sub page).
+
+And of course {T56140} – which I'd say is the ideal solution. And is quite feasible to implement.",1431057318,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+"VisualEditor: Copying and pasting the first reference on a page, then deleting the pasted reference results in ref ""0""","I was able to produce a reference labelled ""0"" in the VisualEditor using the following steps:
+
+1. Create a simple page with some text and a reference. (I've made an example at [[User:Mr. Stradivarius/ref0]].)
+2. Copy and paste the reference to somewhere else in the page.
+3. Delete the reference from the text that has just been copied and pasted.
+4. The first reference is automatically renumbered to ""0"".
+
+The numbering of the first is fixed (back to ""1"") if you delete the line of text that you were on, but if you add new lines of text the first reference remains laballed ""0"" even if the pasted line is subsequently removed. The numbering still starts at 0 if you add another reference, so you get ref ""0"", ref ""1"", etc.
+
+This is on Firefox 22.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375433040,PHID-USER-rjtk3h6l2quifuajiime,PHID-TASK-m6kobht7lswcgwklm5ra,task_description,resolved
+"VisualEditor: Copying and pasting the first reference on a page, then deleting the pasted reference results in ref ""0""","Confirming that this bug is now fixed, almost certainly in the re-write of copy-and-paste for nodes that happened for the 5 September release. Apologies for the slow triage at my end.",1379656831,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m6kobht7lswcgwklm5ra,task_subcomment,NA
+"VisualEditor: Copying and pasting the first reference on a page, then deleting the pasted reference results in ref ""0""","Also, this is just in the editing window. When the page is saved, the numbering returns to normal.",1375433127,PHID-USER-rjtk3h6l2quifuajiime,PHID-TASK-m6kobht7lswcgwklm5ra,task_subcomment,NA
+"VisualEditor: Firefox up-down cursoring around aliens is broken, takes user to end of page sometimes","When the first line of an article is a hatnote template that generates exactly 1 line of text in the visual editor, pressing down twice takes you to the end of the article. When the hatnote template generates more than one line then pressing down takes you to the end of the first line but no further.
+
+I have been unable to reproduce this with templates other than hatnotes. 
+
+Steps to reproduce (short hatnote):
+1. Load a page with a short hatnote in VE, e.g. [[Laurence of Canterbury]]
+2. Press the down cursor twice
+
+Expected behaviour: you end up on the third line of the page
+Actual behaviour: you end up on the last line of the page
+
+Steps to reproduce (long hatnote):
+1. Load a page with a long hatnote in VE, e.g. [[An American in Paris]]
+2. Press the down cursor three or more times.
+
+Expected behaviour: you end up on the third or fourth etc. line of the page
+Actual behaviour: you end up at the end of the first line of the hatnote.
+
+Sandbox pages to test:
+Long hatnote: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=566827194&veaction=edit
+Short hatnote: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox2&oldid=566827110&veaction=edit
+
+This might be related to bug 51708
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51708",1375432860,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k3hxvwskpoy3zkxaliwa,task_description,resolved
+"VisualEditor: Firefox up-down cursoring around aliens is broken, takes user to end of page sometimes","Have tested this again, and I believe we have fixed this bug as reported, as part of the re-writing of how ContentEditable reacts to cursor events. However, I think I've found another bug semi-related, so will open that.",1380754670,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k3hxvwskpoy3zkxaliwa,task_subcomment,NA
+"VisualEditor: Firefox up-down cursoring around aliens is broken, takes user to end of page sometimes","My testing was in Monobook in Firefox 22 on Linux.
+The original reporter was using Monobook in Firefox 22 on Windows 7.
+Rybec comments that they can reproduce it in some pages (e.g. my sandbox) but not others (e.g. [[Laurence of Canterbury]]) using Firefox ESR on Linux.
+
+It's starting to look like it might be a Firefox-only bug.",1375477103,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k3hxvwskpoy3zkxaliwa,task_subcomment,NA
+"VisualEditor: Firefox up-down cursoring around aliens is broken, takes user to end of page sometimes","I have been unable to reproduce this at all on all of the linked pages, with both Monobook and Vector on Chrome, Win7.",1375475936,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-k3hxvwskpoy3zkxaliwa,task_subcomment,NA
+"The on-page notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices, unlike all the other status notes","Flagged Revisions provides a number of edit notices about the status of the page being edited, but this one (about the status of the transcluded components thereof) isn't. This feels wrong. It also means VisualEditor can't warn people about it.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52280",1375423920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d3wa2dbg66dt5t24advb,task_description,duplicate
+VisualEditor: Link inspector should have bottom margin to avoid cutting the page (UX),"Screenshot of problem
+
+When the link inspector is fairly tall and the space somewhat narrow (e.g. a red link, 10 suggestions in the inspector, and the link itself is towards the bottom of the screen), the box will expand further than the page goes (triggering a scrollbar if needed).
+
+That's fine, except that it is hard to see for the user whether there is more or not. Especially with OSX hiding scroll bars by default.
+
+There should be some bottom margin so that it can be clearly seen that the bottom of the list is the bottom, ans eparated from the bottom of the (now expanded) page.
+
+See attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11124}",1375410180,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pzog36r24v5pdzjqcxdr,task_description,resolved
+VisualEditor: Link inspector should have bottom margin to avoid cutting the page (UX),We have similar logic in the dropdown menus and dialogs already. They never touch the bottom of the window.. No Touching!,1403712107,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pzog36r24v5pdzjqcxdr,task_subcomment,NA
+"VisualEditor: Extending an existing DL-indentation renders correctly in CE, but doesn't come through on save","Pressing enter at the end of a colon indented line and typing more text displays as an indented, but, on save, (and review changes) the colon has not been added to the new line.
+
+Steps to reproduce:
+
+0. Start with a simple colon indented section. (See here: http://en.wikipedia.org/w/index.php?title=User:Markhurd/Sandbox&oldid=566721115 )
+1. Edit with VE.
+2. Click at end of last indented line.
+3. Press Enter. Note this displays as continuing the indentation.
+4. Type some text.
+5. Save. Note that the colon is not included. (You can see it missing with Show Changes.)
+
+My diff: http://en.wikipedia.org/w/index.php?title=User:Markhurd/Sandbox&diff=566721183&oldid=566721115
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375368960,PHID-USER-fgul5wwrgbtdpd5fved3,PHID-TASK-jgayasapvffxzhq5zq6a,task_description,open
+"VisualEditor: Extending an existing DL-indentation renders correctly in CE, but doesn't come through on save",This does seem to be fixed: https://en.wikipedia.org/w/index.php?title=User:Markhurd/Sandbox&diff=662749142&oldid=646642979,1431858171,PHID-USER-fgul5wwrgbtdpd5fved3,PHID-TASK-jgayasapvffxzhq5zq6a,task_subcomment,NA
+"VisualEditor: Extending an existing DL-indentation renders correctly in CE, but doesn't come through on save","Created attachment 13202
+VE shows the new text as indented, but it isn't
+
+I've just reproduced this in Firefox 23/Linux/Monobook. The screenshot shows how VE displayed it, the dif showing what was actually saved is: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=570859913&oldid=570858997
+
+The trailing blank lines are bug 50995, and this may be an artefact of the same bug as the displayed blank lines do not exist in the source.
+
+**Attached**: {F11963}",1377896791,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-jgayasapvffxzhq5zq6a,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"It isn't obvious to all users that clicking on the warning about Wikitext will make it disappear.
+
+For example, PamD at en.wp said:
+""I edited an article and found I'd got the popup saying I'd been using wiki markup, I should go into Edit Source, my edits wouldn't be saved, etc. I knew I'd input a pair of ''s at one time but had then remembered the error of my ways, removed them, and marked the title as italic in VE style, so was pretty confident I hadn't used any wiki markup and went ahead and saved the edit (difficult because the popup was sitting on top of the savepage box).""
+
+The main issue there is Bug 52155, but after being pointed to that bug she replied:
+
+""so if I'd clicked on the box it would have gone away... ? Not obvious!""
+
+It would be good to add an X in the upper right corner to indicate that it can be closed. This wouldn't change the behaviour that clicking anywhere on the box dismisses it, just give a visual indication that it can be done.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51701
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52462",1375356660,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6ytamqsj45kuhfs22bx4,task_description,resolved
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"Change 87034 merged by jenkins-bot:
+Toolbar action widgetization and UI refactoring
+
+https://gerrit.wikimedia.org/r/87034",1380932250,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"Change 87034 had a related patch set uploaded by Jforrester:
+Toolbar action widgetization and UI refactoring
+
+https://gerrit.wikimedia.org/r/87034",1380844342,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"Rephrased bug to not mention ""wikitext message"". Instead focussing on notices that pop out of the toolbar, which are indeed created by VisualEditor.",1380728868,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"These alerts are rendered by a MediaWiki core interface. VisualEditor just calls mw.notify. It does not and should not be modifying those alerts by other means.
+
+Please file a bug in core for this (or move/depends-on this bug).",1380728803,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"en.wp user Mark M comments re the wikitext warning:
+""It wasn't obvious to me how to get rid of the notice. In fact, it popped up and partially cover the ""save"" button in such a way that when I tried to click save, nothing happened, and the notice was still there! For a few seconds I thought I wouldn't be able to save my changes at all, even though I'd removed the wikitext. Fortunately I kept clicking nearby (in frustration) and the notice disappeared. But I would have been helped if there had simply been a ""dismiss"" button, or something similar, that indicates you should click on it to dismiss it. This wasn't obvious to me.""",1376486603,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"There have been two independent requests for this today on en.wp (one reporting an issue on he.wp).
+
+It was also noted that the close indication should be applied to edit notice popus too.",1375816630,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: <references /> not fully populated but {{reflist}} is,"In some cases it seems that <references /> is not fully populating the references list while {{reflist}} does.
+Example at: At https://en.wikipedia.org/w/index.php?title=Christian_Scott&oldid=566681769
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50094",1375341060,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-cjrfpthlsv4urm5hyivq,task_description,declined
+VisualEditor: <references /> not fully populated but {{reflist}} is,Both lists have the same references for me. Please re-open if you think there is still a problem.,1386608699,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cjrfpthlsv4urm5hyivq,task_subcomment,NA
+VisualEditor: <references /> not fully populated but {{reflist}} is,"Hi Chris, what I see there is the entire section being duplicate, in both view and edit mode. I am probably missing something :)",1378988819,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cjrfpthlsv4urm5hyivq,task_subcomment,NA
+VisualEditor: <references /> not fully populated but {{reflist}} is,"Not a duplicate, AFAICT.",1375381795,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cjrfpthlsv4urm5hyivq,task_subcomment,NA
+VisualEditor: <references /> not fully populated but {{reflist}} is,"
+
+%%%*** This bug has been marked as a duplicate of bug 50094 ***%%%",1375381498,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-cjrfpthlsv4urm5hyivq,task_subcomment,NA
+Explore performance gains from progressive (JIT?) de-alienation in VisualEditor,"Random idea that might improve load performance: initially alienate the entire document, then progressively convert and dealienate it. This should bring the editor into view quickly and allow the first paragraph to be edited quickly while the rest of the page is still processing.
+
+Possible pitfall: reference numbering and other crazy stuff in MWReferenceNode
+
+See {T76544} for the same idea, but for content blocks.",1375323540,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vpvtoerhlbprn6ollnkr,task_description,open
+VisualEditor: <tt> annotations should be handled by the <code> annotation code,"en.wp user Cryptic C62 comments:
+""Take a look at the text this page. The first two sentences may appear to be identical. If one activates VE, one will find that the first sentence (which employs <tt>) cannot be edited, but the second one (which employs <code>) can. My question is this: If the editor is supposed to be visually intuitive, why are two (almost) visually identical elements handled differently? ""
+
+The page referred to is: https://en.wikipedia.org/w/index.php?title=User:Cryptic_C62/sandbox&oldid=566625027
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375304640,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-sug5dsmkfrgqkbno76mo,task_description,resolved
+VisualEditor: <tt> annotations should be handled by the <code> annotation code,"Change 77389 merged by jenkins-bot:
+Handle <tt> as textStyle/code
+
+https://gerrit.wikimedia.org/r/77389",1375933535,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sug5dsmkfrgqkbno76mo,task_subcomment,NA
+VisualEditor: <tt> annotations should be handled by the <code> annotation code,"Change 77389 had a related patch set uploaded by Esanders:
+Handle <tt> as textStyle/code
+
+https://gerrit.wikimedia.org/r/77389",1375476734,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sug5dsmkfrgqkbno76mo,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"It is possible to insert a substituted template (by just putting in ""subst:whatever"" as its name). This will be saved correctly (substituted), but the diff shown in the review dialog shows the non-substituted wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53201",1375301760,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-l6tecg3euv7s6vvgap3i,task_description,resolved
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Change 129251 merged by jenkins-bot:
+Apply PST when generating diff
+
+https://gerrit.wikimedia.org/r/129251",1398283390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Change 129251 had a related patch set uploaded by Alex Monk:
+Apply PST when generating diff
+
+https://gerrit.wikimedia.org/r/129251",1398282667,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"VE's API ""diff"" option instantiates its own DifferenceEngine but fails to set the PST option.",1377903454,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Marking as ""minor"" as we don't provide a built-in way for subst: to be added (yet) to transclusion invocations.",1375303837,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Sorry, my bad. I forgot I was using custom JS to generate diffs.",1375303217,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"No, it shows the substituted code.",1375302317,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Isn't this how normal diffs work? If I replace the sandbox with {{subst:test}}, it just shows the addition of the text ""{{subst:test}}"" when you hit show changes.",1375302025,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"en.wp user User:Timwi reports
+
+""On the page [[Earth]], we had the following markup code:
+
+[[File:(filename)|thumb|700px|center| (caption here) |alt= (alt text here) ]]
+
+The VisualEditor parsed this incorrectly and assumed that “alt= (alt text here)” was the ''caption''.
+
+Changing the order of the items fixed this despite having no effect on the rendered page, which indicates that it’s a bug in VisualEditor and not incorrect MediaWiki markup."" http://en.wikipedia.org/w/index.php?title=Earth&diff=566614668&oldid=566595613 
+
+I've done some testing in my sandbox and it seems like the issue is somehow related to the presence of the {{val}} template. I wasn't able to replicate the bug with the {{small}} or {{convert}} templates for example, but I've not done extensive testing with the latter or with any other template.
+
+https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=566618437&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://parsoid-lb.eqiad.wikimedia.org/enwiki/User:Thryduulf/sandbox?oldid=566618437",1375300620,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_description,resolved
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"Done now. Will be deployed tomorrow after a round of RT-testing. Can be reopened, if necessary.",1426634110,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"Change 197120 merged by jenkins-bot:
+T54341: Recover content from non-string tokens for img option alt
+
+[[https://gerrit.wikimedia.org/r/197120]]",1426608678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"Change 197120 had a related patch set uploaded (by Subramanya Sastry):
+WIP: T54341: Recover content from non-string tokens for img option alt
+
+[[https://gerrit.wikimedia.org/r/197120]]
+",1426534930,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"This is a difference in how links are handled in alt-attributes, and nothing to do with templates.
+```
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=Foo ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img alt=""Foo"" resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>Caption here</figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=[[Foo]] ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"">Foo</a> </figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt={{echo|[[Foo]]}} ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""1"":{""wt"":""[[Foo]]""}},""i"":0}}]}'>Foo</a> </figcaption></figure>
+```
+
+However, the PHP parser generates identical HTML for the ""alt=Foo"" and ""alt=[[Foo]]"" cases above.",1425937538,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"This is a difference in how links are handled in alt-attributes, and nothing to do with templates.
+```
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=Foo ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img alt=""Foo"" resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>Caption here</figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=[[Foo]] ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"">Foo</a> </figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt={{echo|[[Foo]]}} ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""1"":{""wt"":""[[Foo]]""}},""i"":0}}]}'>Foo</a> </figcaption></figure>
+```
+
+However, the PHP parser generates identical HTML for the ""alt=Foo"" and ""alt=[[Foo]]"".",1425937523,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"This is a difference in how links are handled in alt-attributes, and nothing to do with templates.
+```
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=Foo ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img alt=""Foo"" resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>Caption here</figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=[[Foo]] ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"">Foo</a> </figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt={{echo|[[Foo]]}} ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""1"":{""wt"":""[[Foo]]""}},""i"":0}}]}'>Foo</a> </figcaption></figure>
+```",1425937447,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"The problem seems to be with the link that the val template emits and Parsoid is somehow barfing on it. Can be reproduced with the following reduced test case:
+``` [[File:Foo.jpg|thumb|Caption here|alt=This {{echo|[[will]]}} break]]```
+Compare with output of
+``` [[File:Foo.jpg|thumb|Caption here|alt=This {{echo|will not}} break]]```",1423003789,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"Never mind. My eyes deceived me. The following snippet still parses incorrectly.
+
+[[File:Solar Life Cycle.svg|thumb|700px|center|The life cycle of the Sun|alt=14 billion year timeline showing Sun's present age at {{val|4.6|ul=byr}}; from {{val|6|u=byr}} Sun gradually warming, becoming a red dwarf at, ""soon"" followed by its transformation into a white dwarf star]]",1406236435,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,Verified fixed in deployed Parsoid version.,1406236095,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375286580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y754cxtupebi6bfunc3e,task_description,invalid
+Broken browser plugins cause cruft to be injected into the page (tracking),"If you don't replace a tracking bug with anything, you lose a useful feature to navigate between tasks…",1540255797,PHID-USER-4z6eerx3m7iocsrcpku5,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),Tracking bugs existed as a workaround to Bugzilla's shortcomings. There's no utility in keeping this around now.,1524218709,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),">>! In T54327#1948228, @Jdforrester-WMF wrote:
+>>>! In T54327#1948146, @Nemo_bis wrote:
+>> How to share the blacklist (or whatever cleanup method VisualEditor is currently using) with other consumers of Parsoid, such as T124152?
+> 
+> They should sub-class VisualEditor, which is tracked in {T105447} which I've now linked that to.
+
+Makes sense. What if someone else, maybe outside MediaWiki, desired to use Parsoid for two-way conversion? Should everyone subclass VisualEditor or is this sort of HTML/wikitext cleanup of more general use?",1453673063,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),">>! In T54327#1948146, @Nemo_bis wrote:
+> How to share the blacklist (or whatever cleanup method VisualEditor is currently using) with other consumers of Parsoid, such as T124152?
+
+They should sub-class VisualEditor, which is tracked in {T105447} which I've now linked that to.",1453306858,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"How to share the blacklist (or whatever cleanup method VisualEditor is currently using) with other consumers of Parsoid, such as T124152?",1453304786,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"What is this tracking, nowadays?",1432053265,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"I wonder if https://ru.wikipedia.org/?diff=65612328 is another instance of this, or if it's a copy-paste bug instead.",1410976801,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"Added #53315 for texts looking like telephone numbers changed in <a href=""tel:..."">...</a>",1377428723,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"On en wikipedia most of these are detected by
+http://en.wikipedia.org/wiki/Special:AbuseFilter/345
+Other common cases include
+myEventWatcherDiv
+QuickiWiki Look Up
+application/x-datavault
+end_of_the_skype_highlighting
+inlineAdmedialink
+_clearly_component
+ktg6us78hf8vdu7
+
+Most are not visible the but ktg6us78hf8vdu7 makes a right mess trying to add javascript links everywhere
+http://en.wikipedia.org/w/index.php?title=Shane_Watson&diff=prev&oldid=568280885",1376399632,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+VisualEditor: Media items are clearing templates (or they're being forced to width:100%?),"Screenshot
+
+Adding an image with caption besides a list creates whitespace in edit mode, see screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/116._Panzer-Division_(Wehrmacht)
+
+**Attached**: {F11788}",1375271820,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-xoiz3tzy2fgdd4xhxob7,task_description,resolved
+VisualEditor: Media items are clearing templates (or they're being forced to width:100%?),"This is caused by bug 51708 – all inline templates assume 100% width, which breaks all floated items.
+
+*** This bug has been marked as a duplicate of bug 51708 ***",1394223928,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xoiz3tzy2fgdd4xhxob7,task_subcomment,NA
+"VisualEditor: Reference defined inside a reference list but of a different group inside template appears as part of the template and also in the appropriate reference list, but blank this time","**Author:** `kwwilliams`
+
+**Description:**
+In http://en.wikipedia.org/w/index.php?title=List_of_record_charts&oldid=566209687, notice how Note 1 gets transformed in the string ""1.0.1.1"" and the actual contents of Note 1 becomes reference 19, which is completely unused in the article body.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53486",1375225080,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ydvvzyrpkompusxbw5gr,task_description,open
+"VisualEditor: Reference defined inside a reference list but of a different group inside template appears as part of the template and also in the appropriate reference list, but blank this time","Clarify the title to explain what I think is happening:
+
+| VisualEditor: Reference defined inside a reference list but of a different group inside template appears as part of the template and also in the appropriate reference list, but blank this time",1377817614,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ydvvzyrpkompusxbw5gr,task_subcomment,NA
+"VisualEditor: Reference defined inside a reference list but of a different group inside template appears as part of the template and also in the appropriate reference list, but blank this time",I can confirm this is still happening.,1377815025,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ydvvzyrpkompusxbw5gr,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","When we edit using the visual editor, we still get
+mw.config.get( 'wgAction' ) === 'view'
+instead of
+mw.config.get( 'wgAction' ) === 'edit'
+
+See also
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070603.html
+which quotes
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070601.html
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+* {T53421}
+* {T55746}
+* {T55441}",1375206000,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-7te6uik6zxfmwlua2dgh,task_description,resolved
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","This is now mostly done, for single edit tab wikis.",1455664404,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","(per https://phabricator.wikimedia.org/T55441#962602)
+
+I agree. I don't think it's realistic or desirable to change the url of the editor. Instead we should (eventually) change the default. We can support permalinks for when the url given is semantically related to VisualEditor, but in most cases that is not the case.
+
+There are many cases where the link itself has no relation to an editor, but we do want to send traffic to VisualEditor for new users (when configured as default):
+* red links generated by the parser.
+* edit links generated by templates.
+* edit links created by extensions and gadgets.
+* third party sites.
+* existing content and discussions.
+
+The majority of those links cannot be feasibly changed, with the exception of those generated by the parser as red links. To change those, the parser would need access to user preferences (which fragments the cache) and the parser would need access the target page content model (which requires additional expensive queries, and is also variable; so it would require cascading cache invalidation).
+
+Instead of changing the url of the ""Edit"" or ""Create"" tab in the interface (and providing secondary links for other editors), it probably makes more sense to hook into EditAction (action=edit) and change the default server-side (based on page content model, and current user preferences). Then, we can use an optional query parameter (e.g. action=edit&editor=visualeditor) in case a direct permanent is wanted. Such as when switching between the editors, or when otherwise relying on exact behaviour (e.g. browser tests and gadgets).",1433993930,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","(In reply to Helder from comment #1)
+> For the sake of solving bug 51421, maybe it could use ""action=vedit""?
+
++1",1397517663,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""",See also bug 53746 comment 3.,1382125536,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","Another reason why the current method is not ideal, taken from
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Categories/reply_(8)
+
+>Lots of template transclusions also offer a specific edit link.
+>Their action uses only the wiki code editor. If both actions
+> ""edit"" and ""editVE"" were merged into a single one (with a simple
+> switch to show either the editable preview or the wiki code) it
+> would be simpler. And the ""Show preview"" button could disappear
+> below the wiki editor (it would just remain a ""Save page"" button),
+> but the ""Save"" button could also show the actual rendering
+> without the limitations of the editable preview.",1381609456,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","For the sake of solving bug 51421, maybe it could use ""action=vedit""?",1375207110,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"When a page has pending edits and it is opened for editing using VisualEditor, there is a dropdown box with a notice about this.  When a page has a template or a file with pending changes is opened for editing, the dropdown box does not appear.
+
+An example on the Russian Wikipedia:
+https://ru.wikipedia.org/wiki/%D0%98%D1%80%D0%B3%D0%B8%D1%88
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52440",1375204500,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-rkr7k7s24b2ie267wdh5,task_description,resolved
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"Change 123875 merged by jenkins-bot:
+Show pending changes notice about unstable transclusions in VE
+
+[[https://gerrit.wikimedia.org/r/123875]]",1422422861,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"(In reply to Alex Monk from comment #6)
+> (In reply to James Forrester from comment #5)
+> > (In reply to Alex Monk from comment #3)
+> > > Shouldn't this appear on the wikitext editor too then?
+> > 
+> > Maybe create a further bug for that in FlaggedRevisions?
+> 
+> I just noticed that it was already made - by you. And it's what this bug is
+> marked as depending on.
+
+Ha. Never mind me. :-)",1396644576,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"(In reply to James Forrester from comment #5)
+> (In reply to Alex Monk from comment #3)
+> > Shouldn't this appear on the wikitext editor too then?
+> 
+> Maybe create a further bug for that in FlaggedRevisions?
+
+I just noticed that it was already made - by you. And it's what this bug is marked as depending on.",1396644489,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"(In reply to Alex Monk from comment #3)
+> Shouldn't this appear on the wikitext editor too then?
+
+Maybe create a further bug for that in FlaggedRevisions?",1396632349,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"Change 123875 had a related patch set uploaded by Alex Monk:
+Show pending changes notice about unstable transclusions in VE
+
+https://gerrit.wikimedia.org/r/123875",1396625665,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,Shouldn't this appear on the wikitext editor too then?,1396622745,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"Yes, this is intentional (as the tool interferes with VisualEditor and will need re-writing/merging into VE to work properly).
+
+The notice above the page having transcluded files or templates with outstanding changes feels like one of the things that should appear in the wikitext page's edit notices (and so on VisualEditor's panel too) - not sure why it doesn't. Is this a Pending Changes bug?",1375216355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"Specifically, not only does the dropdown box not appear, but the notice that was on the page before clicking ""edit"" disappears, leaving absolutely no notice.",1375207442,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+Improve nowiki escaping of template arguments by using global context,"When an unmatched literal square bracket is used in the title of a reference, Parsoid or VisualEditor encloses it in a nowiki tag.
+
+Example on the live wiki: https://en.wikipedia.org/w/index.php?title=Wikipedia&diff=566045928&oldid=566042453#cite_ref-209 (line 360)
+Examples in testing: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=566402676&oldid=566401436
+
+It is possible this is a reappearance of or related to T45067
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T45067}
+{T52331}",1375178760,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-x4ddesfyx6gxnu6ahuf6,task_description,open
+Improve nowiki escaping of template arguments by using global context,"Yes, this is a known problem.  There are two different forms of nowiki escaping that goes on in Parsoid.  One is applied to text strings (the common kind that appears around [[foo]] when typed literally).
+
+The one in this bug report is applied to transclusion parameters to prevent literal characters messing up transclusion parse.
+
+Ex: If {{tpl|foo|bar}} is editd to {{tpl|[[foo|bar]]}}, then the ""[[foo"" and ""bar]]"" have to be wrapped in nowikis to prevent ""[[foo|bar]]"" from being parsed as a wikilink.
+
+The current limitation of this second form of nowiki escaping is that it only checks arguments one at a time.  So, it conservatively escapes ""[foo"" in one argument right now without looking at the global context of all arguments which is why you see the nowiki escapes there.
+
+To be fixed.",1375200325,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-x4ddesfyx6gxnu6ahuf6,task_subcomment,NA
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),"**Author:** `sandrobt.wiki`
+
+**Description:**
+The (visual)edit button in a diff (such as http://it.wikipedia.org/w/index.php?title=Kawakami_Gensai&diff=20609681&oldid=18301858) makes you edit the last version (in the example above the edit button gives the link http://it.wikipedia.org/wiki/Kawakami_Gensai?veaction=edit), whereas clicking on edit source makes you edit the old version (the newest of the two compared versions).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375161360,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pey4kjm5sey6cllpuym2,task_description,resolved
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),"This was fixed some time ago, it appears.",1397598107,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pey4kjm5sey6cllpuym2,task_subcomment,NA
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),As far as I can tell the edit source and edit links point to the same oldid. Is this bug still valid?,1397523999,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-pey4kjm5sey6cllpuym2,task_subcomment,NA
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),This looks to be possibly the same issue as bug 51364,1376475898,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-pey4kjm5sey6cllpuym2,task_subcomment,NA
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),Confirming this -  http://it.wikipedia.org/w/index.php?title=Salamandrina_terdigitata&diff=60451620&oldid=57566108 .,1375291261,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-pey4kjm5sey6cllpuym2,task_subcomment,NA
+VisualEditor: Subpages' link to their parent in the page strapline (#contentSub) get hidden but are still there,"Steps to reproduce:
+
+Go to any page that is a subpage, such as a user sandbox. Observe the link to the parent page, located just under ""From Wikipedia..."". Activate VE. Observe that the aforementioned link disappears.
+
+Found in firefox 22, chrome 28, in both monobook and vector. Screenshot at https://en.wikipedia.org/wiki/File:VE_Phantom_Link.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54325
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58063",1375131300,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jjtln7nquqmd5je6fmy3,task_description,resolved
+VisualEditor: Subpages' link to their parent in the page strapline (#contentSub) get hidden but are still there,"Change 107133 merged by jenkins-bot:
+Hide #contentSub properly
+
+https://gerrit.wikimedia.org/r/107133",1389633321,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjtln7nquqmd5je6fmy3,task_subcomment,NA
+VisualEditor: Subpages' link to their parent in the page strapline (#contentSub) get hidden but are still there,"Change 107133 had a related patch set uploaded by Jforrester:
+Hide #contentSub properly
+
+https://gerrit.wikimedia.org/r/107133",1389626443,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjtln7nquqmd5je6fmy3,task_subcomment,NA
+VisualEditor: Render absolute URLs as links inside the editor,"When you copy & paste a link into VisualEditor, it will not be recognized as a URL, but will appear as plaintext. The MediaWiki parser does render it as a clickable link, of course.
+
+This is annoying especially for references, because you might be confused why your link you're adding as a citation doesn't appear to be clickable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52204",1375129740,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-7wx6pzrxilelrduf5qci,task_description,resolved
+VisualEditor: Render absolute URLs as links inside the editor,"Merging this into 52204 as it's a sub-request.
+
+*** This bug has been marked as a duplicate of bug 52204 ***",1394489652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7wx6pzrxilelrduf5qci,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Adding ""ISBN 0-471-17864-0"" doesn't render the ISBN as a link.  This is more important in the reference tool, but should work on all rich text surfaces.
+
+See also:
+* {T54241}
+* {T63558}",1375057320,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-df6digqa5tkg4x3pko26,task_description,resolved
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Filed T109498 for the remaining ""pasted ISBN"" bit of this bug.",1439925713,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Change 230146 merged by jenkins-bot:
+Detect paste of wikitext and convert it
+
+[[https://gerrit.wikimedia.org/r/230146]]",1439913324,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Change 230146 had a related patch set uploaded (by Jforrester):
+Detect paste of wikitext and convert it
+
+[[https://gerrit.wikimedia.org/r/230146]]
+",1439910967,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Typed and pasted URLs are now merged in core.
+
+*Pasted* RFC/PMID/ISBN links is implemented  (https://gerrit.wikimedia.org/r/230146 is in review).
+
+Currently missing: *typed* RFC/PMID/ISBN links are not autolinked.",1439910724,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Autolink when typing has been merged.  Autolink after pasting is in review, but the functionality is complete.",1439487915,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",">>! In T54204#1522662, @Amire80 wrote:
+>>>! In T54204#1507599, @ssastry wrote:
+>> T107433 (merged as a dupe here) seems to be a major source of nowikis on frwiki as per https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis/Nowiki
+> 
+> In Hebrew as well.
+
+@cscott is working on patches for this ( https://gerrit.wikimedia.org/r/#/c/230146/ and https://gerrit.wikimedia.org/r/#/c/230145/ )",1439133300,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",">>! In T54204#1507599, @ssastry wrote:
+> T107433 (merged as a dupe here) seems to be a major source of nowikis on frwiki as per https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis/Nowiki
+
+In Hebrew as well.",1439132488,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",T107433 (merged as a dupe here) seems to be a major source of nowikis on frwiki as per https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis/Nowiki,1438716820,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",*** Bug 52241 has been marked as a duplicate of this bug. ***,1394489652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","(In reply to comment #5)
+> Magic links are pretty evil.
+
+They are one of many unusual pieces of wiki syntax. And it is quite 'wikipedia' specific functionality which could be dropped from core.
+
+> Explicitly marking links with a parser function
+> is
+> much more sensible.
+
+If the goal is to replace them with a more standard syntax, a 'isbn' interwiki pointing to special:booksources/$1 would be syntax that is more similar and conceptually closer also. Ideally it would render as an internal link when the interwiki points to the local special page.
+
+> I'm not sure supporting magic links in VisualEditor is a
+> good idea.
+
+What is the impact of not supporting these magic links on a) big wikipedias like enwp where these magic works will often be used from a cite template (which can be changed without editing millions of pages) and b) small wikis which are imo more likely to use these magic words in raw wikitext.
+I.e. How many bot edits are needed, and how many tools need to be revised.",1376794728,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",Magic links are pretty evil. Explicitly marking links with a parser function is much more sensible. I'm not sure supporting magic links in VisualEditor is a good idea.,1376787661,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","(In reply to comment #3)
+
+> 
+> Clicking on the non-hyphenated ISBN, however, results in a failed attempt to
+> go
+> directly to the ISBN search page, with this resulting error:
+> 
+> Error
+> 404 – File not found
+> http://en.wikipedia.org/Special:BookSources/9781234567890
+> We could not find the above page on our servers.
+> Did you mean to type
+> http://en.wikipedia.org/wiki/Special:BookSources/9781234567890? You will be
+> automatically redirected there in five seconds.
+> Alternatively, you can visit the Main Page or read more information about
+> this
+> type of error.
+
+The incorrect URI is bug 48915 (it's even worse for non-English wikis as it always suggests a page on en.wp). Although I presume what is wanted is for the ISBN to be edited rather than taking you to the ISBN search page? If so then getting to that page from a right click/ctrl+click would potentially be useful.",1376064405,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","This works for me, but perhaps not as expected.
+
+You can add:
+
+PMIDs:  http://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=563393942&oldid=563393897
+
+ISBNs without hyphenation:  http://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=567704513&oldid=564410882
+
+ISBNs with hyphens:  http://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=567704681&oldid=567704513
+
+Exactly like the classic wikitext editor, these do not display as being links until after they are saved.  They do work correctly when saved.
+
+After they have been saved, if you go back into VisualEditor to edit again, then the PMID and hyphenated ISBNs are not editable or clickable (except to select the whole element).  Changes to them must be made by deleting the whole thing and retyping from scratch.  
+
+Clicking on the non-hyphenated ISBN, however, results in a failed attempt to go directly to the ISBN search page, with this resulting error:
+
+Error
+404 – File not found
+http://en.wikipedia.org/Special:BookSources/9781234567890
+We could not find the above page on our servers.
+Did you mean to type http://en.wikipedia.org/wiki/Special:BookSources/9781234567890? You will be automatically redirected there in five seconds.
+Alternatively, you can visit the Main Page or read more information about this type of error.",1375982678,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","I guess the other Magic links http://www.mediawiki.org/wiki/Markup_spec/BNF/Magic_links
+for RFC and PMID should be included here.",1375941068,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",Discussed at http://en.wikipedia.org/wiki/Wikipedia_talk:VisualEditor#Should_inability_to_edit_ISBNs_be_listed_in_the_limitations_section.3F,1375940866,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+VisualEditor: Invocations of deleted images don't render at all,"**Author:** `wikipedia`
+
+**Description:**
+When a file is deleted and still is being used in an article, this file is shown in the article as a box with a red link in it. Starting VE to remove the link, the link is no more visible and thus cannot be removed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7",1375010460,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pw24nueljk2i343joyw2,task_description,resolved
+VisualEditor: Invocations of deleted images don't render at all,"
+
+*** This bug has been marked as a duplicate of bug 50788 ***",1389632313,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pw24nueljk2i343joyw2,task_subcomment,NA
+VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph,"**Author:** `jonathan_haas`
+
+**Description:**
+Steps to reproduce:
+
+1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit
+2. Position the cursor at the start of the page directly before the bold ""T"".
+3. Hit Backspace (to delete infobox)
+4. Hit Ctrl+Z (undo)
+5. Hit Backspace again
+6. Hit Ctrl+Z again
+Repeat as long as you want
+
+Actual result:
+
+On each Ctrl+Z a paragraph more is selected
+
+Expected result:
+
+Selection stays the same, undo should undo the action and not change the selection
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375008900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3wvoqjxuqinfi7bgkax4,task_description,resolved
+VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph,This was fixed in gerrit 115759 as part of fixing bug 57552.,1394503778,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3wvoqjxuqinfi7bgkax4,task_subcomment,NA
+VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph,"**jonathan_haas** wrote:
+
+Deleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2.
+
+In short: The problem is more hidden, but the underlying issue has not been fixed.",1382445971,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3wvoqjxuqinfi7bgkax4,task_subcomment,NA
+VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph,Reproduced.,1375050421,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-3wvoqjxuqinfi7bgkax4,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference","Removing the content from out of a <ref> .. </ref> should prompt the user that they need to delete the reference.  Perhaps a tooltip, or this might be an opportunity to use a hover trick to give the user something to click to acknowledge they intended to delete the ref.
+
+It shouldnt be possible to save with an empty ref, as that is an error condition.
+
+https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&diff=566133128&oldid=566132993
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50609",1375008300,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-tgtxd532icx4mnfll75r,task_description,resolved
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference","Yes, sorry, this was great. Thanks!",1405038215,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference",Ping. Anyone want to answer my question?,1405038076,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference","So Gerrit change 136496 fixed the existing intended behaviour, but didn't go as far as this bug suggests (it just disables the apply button rather than deleting the reference) - should it be changed to delete the reference still?",1401808848,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference",*** Bug 62399 has been marked as a duplicate of this bug. ***,1401479536,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference",See Gerrit change 81438 and Gerrit change 88618,1401476178,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference",length < 4 is a hack and we probably shouldn't be using it…,1401476091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference","According to ve.ui.MWReferenceDialog.prototype.onDocumentTransact, this apply button is supposed to be disabled when the length is less than 4. But when I empty the box, the length is 10 so nothing is done.
+
+Anyway, I think we should either:
+* Fix that bug (if it is one) and mark this bug as invalid (or repurposed for fixing it), or
+* Replace that with this idea",1401475699,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","If VisualEditor is default, why after clicking on a red link there's 'action=edit' in url and the source editor runs instead of 'veaction' and VE? I've checked it out on the enwiki and plwiki, but it concerns the rest of phase 2 as well and creating a new page in general. Furthermore, it makes inputboxes ('type=create') incompatible with VE and it can be a bothering problem on some wikis.
+
+**See Also**: {T55441}",1374969780,PHID-USER-gf5juv3z3p75bykrcrhf,PHID-TASK-ra3d7l6sbywnzslhiccu,task_description,open
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","This should become feasible after we implement {T223793}. We can probably use a similar mechanism to intercept the targets of inputboxes.
+
+Also, note that a `useve=true` inputbox parameter has been implemented in the meantime: {T89341}.",1558261962,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor",">>! In T54162#2590097, @Elitre wrote:
+> Did SET work affect this...?
+
+Not yet; it will need further work.",1472505814,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor",Did SET work affect this...?,1472457462,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","I don't want to make inputbox suddenly magically different. It's about ordinary users (especially the new sort 'born' after VE deployment) who want to type a new article's name, click on button and voila, start creating their article in VE. In 2 steps, after 1 click, without experience like 'why the markups? oh, I'm switching to VE'. They'd be more likely to give up in this case.
+
+Technically, you may change the default 'action' with 'veaction' or create a new parameter or sth else, it's up to you.",1412440471,PHID-USER-gf5juv3z3p75bykrcrhf,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","You can easily point InputBox to VE with a simple hook so that VE can change 'action' to 'veaction'. But that won't make VE magically support all the additional parameters which InputBox uses (e.g. preload, editintro, summary, minor, etc.)",1396642309,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","Ah, I see a process problem with type=fulltext too
+
+inputbox goes to search results, and search results show a red link, which the user would click on to start a new page. e.g.
+
+https://en.wikipedia.org/wiki/Special:Search/this_article_doesnt_exist
+
+I believe that some enhancement will be needed in the InputBox extension to support creating VE or SE articles.
+https://www.mediawiki.org/wiki/Extension:InputBox",1375056651,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","In the plwiki, we have no important inputbox with 'type=create' in the main nor user namespace, but there are inputboxes in help or project pages which create a new article (for ex. [[pl:Pomoc:Tworzenie nowych haseł#Niniejsza strona]]), and after clicking the button there is 'action=edit&preload=' in url.
+
+Second, whenever we click on a red link in an article (the main), 'action=edit&redlink=1' displays. The default tab is 'Create source', not 'Create'. It's quite surprising for me and for the newbies, I believe.",1375053920,PHID-USER-gf5juv3z3p75bykrcrhf,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor",Could you provide a example of a 'type=create' problem affecting VE?  Is it used on main or user namespace in your wiki?,1375052410,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"An editor on en.wp has requested that Ctrl+Y should initiate the redo action. Presently the shortcut is ctrl+shift+z.
+
+In my experience both shortcuts are used in about 50% of applications (Xubuntu Linux) so it would be ideal if both shortcuts could be used.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374931680,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-yocptvdek2u4pm4ssk5d,task_description,resolved
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"Change 116966 merged by jenkins-bot:
+Add cmd/ctrl+y as alternative shortcut for redo
+
+https://gerrit.wikimedia.org/r/116966",1394054746,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yocptvdek2u4pm4ssk5d,task_subcomment,NA
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"Change 116966 had a related patch set uploaded by Catrope:
+Add cmd/ctrl+y as alternative shortcut for redo
+
+https://gerrit.wikimedia.org/r/116966",1394051814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yocptvdek2u4pm4ssk5d,task_subcomment,NA
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"Add cmd/ctrl+y as alternative shortcut for redo
+https://gerrit.wikimedia.org/r/#/c/116966/",1394038226,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yocptvdek2u4pm4ssk5d,task_subcomment,NA
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"**jonathan_haas** wrote:
+
+Ctrl+Y is the default undo shortcut in Firefox. It's very confusing that it doesn't work in VE using Firefox.",1375020469,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yocptvdek2u4pm4ssk5d,task_subcomment,NA
+VisualEditor: Come up with something better than .offsetOf(),"We overuse both ""index"" and ""offset"" in our vocabulary, and one of the more cringe-worthy results is the rename of .indexOf() to .offsetOf() in AnnotationSet. We should refactor our vocabulary and rename this to something saner.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374887040,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-y2db4ahscixrwviebqhf,task_description,open
+VisualEditor: Adding support to Grammar/Orthography fixes custom wiki defined button to be applied on texts visually on client side,"**Author:** `nzmoihue`
+
+**Description:**
+I think one nice/needed addition to Visual Editor would be supporting custom wiki defined scripts for fixing text [without interfering with wiki text]. For example on Persian Wikipedia we have an edit tool script [1] [2] that wiki users are very depends on it for fixing article texts and without it Visual Editor would be useless for them.
+
+
+ 1. http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%E2%80%8C%D9%BE%D8%AF%DB%8C%D8%A7:%D8%A7%D8%A8%D8%B2%D8%A7%D8%B1%D9%87%D8%A7%DB%8C_%D9%88%DB%8C%D8%B1%D8%A7%DB%8C%D8%B4%DB%8C
+ 2.http://fa.wikipedia.org/wiki/MediaWiki:Gadget-Extra-Editbuttons-Functions.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374875580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7ljydmhlfgrzwegrjhpj,task_description,open
+VisualEditor: Adding support to Grammar/Orthography fixes custom wiki defined button to be applied on texts visually on client side,"I love this idea.
+
+Wikipedias in several languages have such tools, and everywhere it's implemented differently.
+
+The Hebrew Wikipedia has a fully automatic bot making spelling correction on which there's a wide consensus (with over 700 rules), and it also a gadget that adds a button to make semi-automatic edits when fully automatic edits are not reliable enough. I believe that the tool about which Ebrahim is speaking is similar.
+
+If I'm not mistaken, Russian, Belarusian, Portuguese, Catalan and English Wikipedias have such tools, too, though there are definitely differences in implementation. Almost certainly there are more languages that have such tools.
+
+It may be challenging to make a tool that would work equally well for all languages. Different languages have very different requirements. However, acknowledging that at least some languages needs some kind a framework for this and that not being able to use it is a regression for many users, and providing some standard baseline to work with it will be a good start.
+
+What standard baseline? At least, a standard location for a button that would open such a tool. Another thing that would be useful to everybody would be an agreed API for automated or semi-automated searching and replacing in contentedtiable.
+
+A harder thing to do would be to have a standardized format for replacement rules, though this will require at least a bit of research of the current implementations.
+
+(A general comment: The standardized way of marking the text's language, which Moriel is developing in her GSoC project, should be helpful for such tools. They shall only need to work on the parts that are written in the appropriate language.)",1375135304,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7ljydmhlfgrzwegrjhpj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"People would like to be able to edit the language links that are coming from Wikidata in the page settings dialog. A link from there to Wikidata would probably also be a good first step.
+
+**See Also**:
+{T59929}
+{T64005}
+{T74178}",1374859560,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-czxsast2el34thkj2xkj,task_description,open
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"(In reply to Elitre from comment #7)
+> Thanks. So should I file a new one, or...?
+
+Filing a new bug about the Wikidata tool destroying your current edit by navigating away sounds like a good plan, yes, sorry. :-)",1393519722,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"Thanks. So should I file a new one, or...?",1393519677,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"(In reply to Elitre from comment #4)
+> Apparently this is how it currently works? You can add links to Wikidata
+> while in VE, but then you'll miss them because the page will be reloaded?
+
+(In reply to Elitre from comment #5)
+> Sorry, rephrasing: You can add items to Wikidata while in VE, but then
+> you'll miss the other edits you made in that VE session since the page will
+> be reloaded.
+
+Yes, the Wikidata team's sidebar JS tool to add to language links ignores the existence of VE (and so breaks things, as you say).
+
+This bug is talking about being able to edit the language links inside VE, in the language panel of the ""page options"" dialog which is currently read-only. It's also meant to cover more cases and features than the sidebar JS tool currently does.",1393519436,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"Sorry, rephrasing: You can add items to Wikidata while in VE, but then you'll miss the other edits you made in that VE session since the page will be reloaded.",1393509066,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"Apparently this is how it currently works? You can add links to Wikidata while in VE, but then you'll miss them because the page will be reloaded?",1393508934,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"(In reply to comment #1)
+> This would be excellent, but potentially quite a lot of work. Would the
+> Wikidata team be interested in exploring with us how this could be done?
+
+Yes :) I don't yet know if/how we can dedicate development time to this but let's talk.",1380546193,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,bug52383 suggests the opposite approach: please do not include such complex logic in VE which is already slow. be so kind to improve the current implementation within the VE project if you feel its hacky.,1375398625,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"This would be excellent, but potentially quite a lot of work. Would the Wikidata team be interested in exploring with us how this could be done?",1374862588,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+"""loadImages bad"" error on uploading ~85MB .ogv files","**Author:** `molly.white5`
+
+**Description:**
+Twice now I've uploaded .ogv files (made with RecordMyDesktop, if that helps) and gotten a popup that very helpfully informs me, ""loadImages bad"". This appears directly after I choose the file to upload, and I'm guessing it has something to do with the inability to find a thumbnail image? Anyway, at the very least a more descriptive error message might be nice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374796680,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s536bhjhjcxh5wim4rzu,task_description,invalid
+"""loadImages bad"" error on uploading ~85MB .ogv files","I can't find anything that says ""loadimages"" in either today's UploadWizard nor the UploadWizard of July 2013.",1449164913,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-s536bhjhjcxh5wim4rzu,task_subcomment,NA
+"""loadImages bad"" error on uploading ~85MB .ogv files","**molly.white5** wrote:
+
+Yes, it happens at Special:UploadWizard on Commons. I do not seem to be getting the error on test2.
+
+The files were https://commons.wikimedia.org/wiki/File:RefTools_rework.ogv and https://commons.wikimedia.org/wiki/File:VisualEditor_reference_tutorial.ogv, which are 84.02 and 86.73 MB, respectively.",1374880481,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s536bhjhjcxh5wim4rzu,task_subcomment,NA
+"""loadImages bad"" error on uploading ~85MB .ogv files","Hi Molly,
+where does this happen exactly? http://commons.wikimedia.org/wiki/Special:UploadWizard ? Does it also happen on http://test2.wikipedia.org/wiki/Special:UploadWizard ? Which approx. filesize do these files have?",1374852631,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-s536bhjhjcxh5wim4rzu,task_subcomment,NA
+Allow extension options to be specified in API calls,"The rendering of a page can be affected by user extension options (e.g. their choice of renderer for the Math extension) so we should be able to pass through these options to the API.
+
+This is blocking proper support of the Math extension in VisualEditor.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1374764640,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jksvrmf6seb3lzwf6tsr,task_description,open
+Allow extension options to be specified in API calls,"To do something about this, I think we'd need:
+# Put these extension options in ParserOptions, somehow. The extension would also have to depend on the ParserOptions rather than user preferences or the like to determine behavior.
+# Be able to query the options available in ParserOptions, along with their API data types. And be able to set an option generically by name.
+# Then ApiParse and other modules can use this to add relevant parameters for the parser options.",1472056142,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-jksvrmf6seb3lzwf6tsr,task_subcomment,NA
+Allow extension options to be specified in API calls,[Setting normal prio as bug 51698 (blocked by this) is also normal prio.],1395107815,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jksvrmf6seb3lzwf6tsr,task_subcomment,NA
+Allow extension options to be specified in API calls,See bug 51698,1374764852,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jksvrmf6seb3lzwf6tsr,task_subcomment,NA
+VisualEditor: ve.ui.Context#toolbar is null in MediaWiki,"Following the documentation[1] starting at ve.ui.Surface (from ve.instances[0]) one would go to #getContext and access .toolbar. But though that property is defined, it is set to null.
+
+I'm not sure why, but apparently our MediaWiki's init is instantiating its own and is only accessible from ve.init.mw.ViewPageTarget#toolbar (ve.init.mw.targets[0].toolbar).
+
+It probably shouldn't have to instantiate its own one, and certainly not make it inaccessible to the rest of VE.
+
+
+[1] https://doc.wikimedia.org/VisualEditor/master/#!/api/ve.ui.Surface
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374716460,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-27h7itsrfluxqubhrje3,task_description,resolved
+VisualEditor: ve.ui.Context#toolbar is null in MediaWiki,"There used to be a .toolbar property because the context had its own (local) toolbar to show the contextual tools in. This has been replaced with ContextWidget (which isn't a toolbar) which groups ContextItemWidget (which aren't tools), and now there is no .toolbar property.",1412590622,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-27h7itsrfluxqubhrje3,task_subcomment,NA
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out","It seems that Chrome 28 does not display the ""Minor Edit"" and ""Watch This Page"" checkboxes on the save page form. This does work in Firefox 22. Does not seem skin related - Vector and Monobook have the same problem in either browser
+
+Steps to reproduce:
+- Open any page in edit mode.
+- Make a small change, press Save page.
+- (Firefox): There will be checkboxes stating ""Watch this page"" and ""This is a minor edit""
+- (Chrome): Those checkboxes are not present.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374688740,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-egsozcckjwhatubn2cu7,task_description,invalid
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out",Then this is not the bug I thought it was; fixing settings.,1374693622,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-egsozcckjwhatubn2cu7,task_subcomment,NA
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out",Do'h! Logging in does indeed appear to be the problem - I restarted Chrome right before testing a few things iand forgot to log back after i did. Sorry for that - seems to be a storm in a teacup.,1374693512,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-egsozcckjwhatubn2cu7,task_subcomment,NA
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out","(In reply to comment #0)
+> It seems that Chrome 28 does not display the ""Minor Edit"" and ""Watch This
+> Page""
+> checkboxes on the save page form. This does work in Firefox 22. Does not seem
+> skin related - Vector and Monobook have the same problem in either browser
+> 
+> Steps to reproduce:
+> - Open any page in edit mode.
+> - Make a small change, press Save page.
+> - (Firefox): There will be checkboxes stating ""Watch this page"" and ""This is
+> a
+> minor edit""
+> - (Chrome): Those checkboxes are not present.
+Are you sure you're logged in in both browsers? If you're logged out in Chrome, then you'd be getting the expected behavior for anons (which changed recently, because we're not using smarter code that's more consistent with how the old editor does it).",1374693045,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-egsozcckjwhatubn2cu7,task_subcomment,NA
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out",This is actually due to an underlying bug in the new code just pushed out an hour ago; we've just fixed this (reload if it doesn't show).,1374692833,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-egsozcckjwhatubn2cu7,task_subcomment,NA
+VisualEditor: Undo does not invalidate cached wikitext diff content,"English Wikipedia user Atethnekos reports: 
+""If I make 2 changes, review changes, exit review/save dialog, undo last change, and then review changes again, the review shows both changes, though saving only saves the first.""
+
+Steps to reproduce:
+1. Make two changes to a page in VE
+2. Undo one change
+3. Click save and review your changes. 
+-Expected behaviour: Only the first change is shown
+-Actual behaviour: Both changes are shown.
+4. Save the page. Only the first change has been saved.
+
+This means that the review your changes is incorrect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374660840,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-csda6oirljibl6xuzg3w,task_description,resolved
+VisualEditor: Undo does not invalidate cached wikitext diff content,"Yes, this is now fixed, almost certainly as part of the re-write Roan did last month.",1392062273,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-csda6oirljibl6xuzg3w,task_subcomment,NA
+VisualEditor: Undo does not invalidate cached wikitext diff content,Can't replicate.,1391916784,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-csda6oirljibl6xuzg3w,task_subcomment,NA
+VisualEditor: Pending Changes dropdown overlaps toolbar in Monobook,"Reported by Atethnekos on EnWiki, who also provided an image: https://en.wikipedia.org/wiki/File:Platovesample1.png
+
+""When I edit a page with the pending changes revision dropdown, and I am scrolled to the very top, the dropdown and the VE page settings link become mangled.  See highlight in included image.  Firefox 22 on Win7 Pro SP1.""
+
+I can reproduce this in both Firefox 22 and Chrome 28. The issue seems specific to the Monobook skin - Vector renders the pending changes dropdown somewhat lower in both browsers.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374647880,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-tl42tulmp4okf7khych6,task_description,resolved
+VisualEditor: Pending Changes dropdown overlaps toolbar in Monobook,Sorry about this; the good news is that we just fixed this in gerrit 75545 which will go out in about eight hours or so - that drop-down menu will be hidden once you're inside VisualEditor mode (whatever your skin).,1374648228,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tl42tulmp4okf7khych6,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"Wikitext appearing in transclusion dialog
+
+The underlying cause of this might be covered in bug 48231 or bug 51217 or others ... I thought I saw a bug about this, but cant find it now.
+
+[[template:multicol]] with wikisyntax inside it results in the attached screenshot, with wikitext visible in the transclusion dialog as 'Content' blocks.
+
+https://nl.wikipedia.org/wiki/Gebruiker:John_Vandenberg/test?veaction=edit
+
+Section headers & list items also cause this; see the last block here:
+https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=565567699&veaction=edit
+
+If it helps, this issue is present on one of the parsoid topfails:
+
+https://nl.wikipedia.org/wiki/Eerste_divisie_1996/97?veaction=edit
+
+BeginKolommen occurs on nlwp 3047 times.  11362 times in enwp.  8861 times in eswp. 40985 times on itwp!, which is roughly 4% of the content pages.
+
+Confirmed this is happening on every itwp invocation that I edit
+https://it.wikipedia.org/wiki/Speciale:PuntanoQui/Template:Colonne
+e.g.
+https://it.wikipedia.org/wiki/Aeroplano?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11763}",1374638040,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-vb4syhceqgegacimzles,task_description,open
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"(In reply to comment #5)
+> (In reply to comment #4)
+> > > 'nl:Eerste divisie 1996/97' is on the parsoid topfails list
+> > > 
+> > > http://parsoid.wmflabs.org:8001/topfails
+> > > 
+> > Oh, I see. It's not any more now :(
+> 
+> It is on page two of 16
+> 
+> http://parsoid.wmflabs.org:8001/topfails/2
+> 
+Aha! Found it.
+
+> I have no idea if the {{BeginKolommen}} or tables within it have anything to
+> do
+> with the semantic failure; just thought I should mention it.
+That doesn't appear to be the case: looking at the RT diff (which you get to by clicking on the page name), it's mostly related to the tables on the page: http://parsoid.wmflabs.org/_rt/nl/Eerste_divisie_1996/97",1374640898,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"(In reply to comment #4)
+> > 'nl:Eerste divisie 1996/97' is on the parsoid topfails list
+> > 
+> > http://parsoid.wmflabs.org:8001/topfails
+> > 
+> Oh, I see. It's not any more now :(
+
+It is on page two of 16
+
+http://parsoid.wmflabs.org:8001/topfails/2
+
+I have no idea if the {{BeginKolommen}} or tables within it have anything to do with the semantic failure; just thought I should mention it.",1374640614,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"(In reply to comment #3)
+> I think it is impressive that VE handles it
+> 
+This is mostly thanks to Parsoid handling this case very well, and VE simply building a UI around it :)
+
+> 'nl:Eerste divisie 1996/97' is on the parsoid topfails list
+> 
+> http://parsoid.wmflabs.org:8001/topfails
+> 
+Oh, I see. It's not any more now :(
+
+> Here is an itwp example where multicol consumes most of the page, and should
+> probably be removed.
+> 
+> https://it.wikipedia.org/wiki/Campagna_%28comune%29?veaction=edit
+Yes. I just fixed that page.",1374640208,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"I think it is impressive that VE handles it
+
+'nl:Eerste divisie 1996/97' is on the parsoid topfails list
+
+http://parsoid.wmflabs.org:8001/topfails
+
+Here is an itwp example where multicol consumes most of the page, and should probably be removed.
+
+https://it.wikipedia.org/wiki/Campagna_%28comune%29?veaction=edit",1374639358,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"{{BeginKolommen}} generates the beginning of a table, and {{EindeKolommen}} generates the end of that table. All content between those two is treated as one template call. This is expected behavior in the current implementation, and is exactly the same as succession boxes and all other templates that generate openings and closings separately (multipart templates).
+
+It would be nice if we could let users edit these in a nicer way, especially considering that some (but not all) of the wikitext blocks are actually innocuous wikitext that VE could reasonably edit, but right now we can't. This is part of the reason why multipart templates suck.
+
+What is the Parsoid topfail thing you're talking about? There's no link to the failure and it seems unrelated to this issue.
+
+
+Not closing this as INVALID or whatever because this is something we should actually handle better.",1374639024,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"Editing the wikitext appears to function correctly, which is good news.
+https://it.wikipedia.org/w/index.php?title=Matematica&diff=60342095&oldid=59678552",1374638806,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,"The bug 51905 made me realize of a potential problem. When a media, say an image, is inserted, sometimes it may be inserted outside the field of view of the user, and this may lead some users to think that it wasn't inserted at all, causing aborted edits, confusion, frustration, and even bad edits. For example if there is an infobox in the article, or a bunch of images aligned to the right, then if the user inserts an image, in many cases it will be inserted below all this, and the user will not see it without scrolling the screen.
+
+The solution to this potential problem is, I think, fairly simple: make the VisualEditor detect if the image is in the field of view of the user, and if it's not, then scroll the screen so that it is!
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58091",1374614520,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-3wggiaj4uckt3tln426a,task_description,resolved
+Scroll to an item when it is selected e.g. when it has been newly inserted,"Checked all Insert menu options in beta (Chrome, FF35, and Safari).
+
+What was checked 
+
+-  a cursor placed at the top/bottom of a page and Insert
+-  a cursor placed at the bottom of a page - and scroll up and then 'Insert'
+-  'Insert' options for Media Caption
+-  'Undo/Redo' with different cursor positions
+",1427741121,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,"Change 200243 merged by jenkins-bot:
+Scroll the selection into view when it is outside the window
+
+[[https://gerrit.wikimedia.org/r/200243]]",1427668761,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,"Change 200243 had a related patch set uploaded (by Mooeypoo):
+Scroll to newly inserted elements
+
+[[https://gerrit.wikimedia.org/r/200243]]
+",1427494007,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,"A auto-disappearing popup notice ""Your image has been inserted; scroll down to see it."" would help.",1374703747,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,I experienced the same problem in bug 51863.,1374703273,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"When an image file is included directly in an article (i.e not as a thumbnail and not in a frame) with an unclosed <center> tag in the caption causes Visual Editor to not render any page content after the image.
+
+See https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox2&oldid=565498603 for an example.
+
+All the following conditions must be true to see this bug:
+* Image must not be a thumbnail or in a frame
+* The image caption must contain an unclosed html tag specifying text alignment in the caption. Tested with <center>, <p align=""center""> and <div align=""right"">
+* The image placement (left, right or center) must be specified
+
+The bug does not occur with an unclosed italic html tag. I haven't tested with other tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374598740,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gru24gdbzlh5sitams7s,task_description,resolved
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"As we discussed and confirmed on IRC, this is not happening in production right now. So, I am going to mark this resolved-fixed. Please reopen if a similar error shows up.",1380746942,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gru24gdbzlh5sitams7s,task_subcomment,NA
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"Will provisionally mark this as in-review, then (you can see that it's still happening with production Parsoid, though that may be cache errors).",1380746013,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gru24gdbzlh5sitams7s,task_subcomment,NA
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"Unclosed tags in image caption is not that infrequent unfortunately -- the difference between <center> and <i>/<b> tags is that the former is a block tag and the latter is an inline tag. So, any other block tag that is unclosed will cause the same issue. 
+
+That said, I am surprised that this problem showed up in the first place since Parsoid has had support to deal with unbalanced tags for a long time: https://gerrit.wikimedia.org/r/#/c/43384/
+
+This was a bit of a hacky support. More robust and improved support for this is coming in https://gerrit.wikimedia.org/r/#/c/83216/
+
+So, unsure what happened here with this bug.",1380745593,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gru24gdbzlh5sitams7s,task_subcomment,NA
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"Forgot to note that although this combination of conditions is presumably uncommon, it was first observed in the wild at https://en.wikipedia.org/w/index.php?title=Typographer_%28typewriter%29&oldid=565431177",1374599024,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-gru24gdbzlh5sitams7s,task_subcomment,NA
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,"first table at [[Comparison of container formats]] rendered in a 1024px wide window. Firefox 22 on Linux
+
+In VisualEditor the editing window does not horizontally scroll to accommodate wide tables. Table cells and their contents render as if the window did scroll, but as it does not they are truncated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51755
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51820
+
+**Attached**: {F11662}",1374578220,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-d3oejnwggmk2whlojm2x,task_description,resolved
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,This works correctly these days. The page is horizontally scrollable.,1538407902,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-d3oejnwggmk2whlojm2x,task_subcomment,NA
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,it would be nice to have a fix for horizontal scrolling for wide tables,1434875532,PHID-USER-yftvcvsb36qrmx4iohsm,PHID-TASK-d3oejnwggmk2whlojm2x,task_subcomment,NA
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,"en.wp user Cryptic C62 comments:
+""VE does not correctly render any table wider than the screen, nor does it allow horizontal scrolling. This effect seems to extend to any wide element, including math formulas, images, transclusions, and text with non-breaking spaces. Some other findings:
+
+* A horizontal scroll bar does appear when hovering over some elements with a mouseover effect, specifically images and uneditables (Strangely, the scroll bar does not appear when hovering over the {{Details}} template in this example). Scrolling can then occur if you have a clickable mousewheel.
+
+* By placing the text cursor near the visible end of wide text, and pressing the right arrow key, it is possible to sneak the text cursor off of the page.""
+
+Test cases: https://en.wikipedia.org/w/index.php?title=User:Cryptic_C62/sandbox&oldid=567261009",1375714875,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-d3oejnwggmk2whlojm2x,task_subcomment,NA
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,"Comment on attachment 12931
+first table at [[Comparison of container formats]] rendered in a 1024px wide window. Firefox 22 on Linux
+
+Fix MIME type",1374682835,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-d3oejnwggmk2whlojm2x,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"When VisualEditor inserts an image, the thumbnail keywords are written in English: ""File:"", ""thumb"", ""right"" (but see Bug 51851).
+
+This should not, theoretically, be a problem, because the VisualEditor is supposed to make these keywords unimportant and hidden from the end-user. However, while the source editor is still being widely used, this is a problem, especially for right to left languages: it is very hard to edit these English keywords when they are mixed with right-to-left text.
+
+These keywords should be inserted in the language of the wiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374569160,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ah63325mhbgtfpeazbnl,task_description,resolved
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 280792 merged by jenkins-bot:
+T53852: Serialize localized image options
+
+[[https://gerrit.wikimedia.org/r/280792]]",1459883811,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 244254 abandoned by Eranroz:
+Use local keyword for image
+
+Reason:
+See a better patch: https://gerrit.wikimedia.org/r/#/c/244254/
+
+[[https://gerrit.wikimedia.org/r/244254]]",1459809027,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 280792 had a related patch set uploaded (by Arlolra):
+T53852: Serialize localized image options for rtl languages
+
+[[https://gerrit.wikimedia.org/r/280792]]
+",1459469170,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,">>! In T53852#1735891, @Amire80 wrote:
+> General Q: Can the same patch also resolve T104057, a similar issue in ContentTranslation?
+> 
+>>>! In T53852#1735780, @cscott wrote:
+>> * Alternatively, you could do a grep over the most recent dump for that wiki to count frequency of use for each alias, and verify that the term which would be used by this patch matches the most frequent alias.
+> 
+> Sounds more practical and closer to reality.
+> 
+> Parsoid developers, don't you have some kind of a tool that queries lots of dumps quickly? I remember hearing something like this, but maybe I am just imagining.
+
+This used to be part of the parsoid repository but is now its own repo @ https://github.com/wikimedia/dumpgrepper",1445283298,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"General Q: Can the same patch also resolve T104057, a similar issue in ContentTranslation?
+
+>>! In T53852#1735780, @cscott wrote:
+> * Alternatively, you could do a grep over the most recent dump for that wiki to count frequency of use for each alias, and verify that the term which would be used by this patch matches the most frequent alias.
+
+Sounds more practical and closer to reality.
+
+Parsoid developers, don't you have some kind of a tool that queries lots of dumps quickly? I remember hearing something like this, but maybe I am just imagining.
+
+>>! In T53852#1735858, @ssastry wrote:
+> A good compromise to get this moving would be to do this analysis for the top N wikis (N = 10?)
+
+I'd guess that it's more like 50 or so.",1445280165,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,A good compromise to get this moving would be to do this analysis for the top N wikis (N = 10?) -- the expectation is that only a few wikis will need either their messages tweaked or special case exceptions added for them in the code and we can get this going from there.,1445279437,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"@eranroz's code in wikieditor: https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FWikiEditor/8fa9506e20ce5216240531686fa0bd70fdb2a6d8/WikiEditor.hooks.php#L374
+
+I'm proposing a simple process:
+* Make a table with the various options whose serialization will be changed with this patch, both before and after.
+* Send this in an email to the language team for approval.
+** Alternatively, you could do a grep over the most recent dump for that wiki to count frequency of use for each alias, and verify that the term which would be used by this patch matches the most frequent alias.
+* For any languages where this patch does *not* match that wiki's preferred term, file an issue as a blocker for this bug, and resolve it.
+** Either add special cases to this patch, or else export some general siteinfo property (a boolean to ""prefer first alias"" or ""prefer last alias""), or else work with the community to swap the aliases in mediawiki (MessageEn in core, and then perhaps the actual wikipedias need to be checked for customizations that might override this)
+* After this is done, everyone will have objectively agreed that the terms used by this patch are preferable, and this patch can be merged.",1445278545,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"It's not just english, it's also dewiki IIRC.
+
+To unblock this issue, you need to survey all the wikis (not just enwiki and hewiki) and describe how this change will affect them, then get confirmation from the language team that the change is actually ""better"" for all these languages.
+
+We were burned before by changing this prematurely; before we're going to make another change we need to be sure we are actually doing the right thing.",1445277440,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"A note specific for English: This fix will introduce ""thumbnail"" instead of ""thumb""  in parsoid. This side effect is the correct behavior as aliases are defined by the preferred order, and this is the syntax added by the current WikiEditor image dialog. If you prefer ""thumb"" and not ""thumbnail"" (personally I do too) which is shorter - you should swap the aliases in English (MessageEn in core, and enwiki.json in baseconfig) - but this should be a different task.",1444251608,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 244254 had a related patch set uploaded (by Eranroz):
+Use local keyword for image
+
+[[https://gerrit.wikimedia.org/r/244254]]
+",1444247108,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"(In reply to C. Scott Ananian from comment #8)
+> Yes, that is correct.  The patch was merged and then the language-specific
+> parts were reverted because the way it selected the aliases was fragile in
+> LTR languages.  This is still on my to-do list for a proper fix; IIRC the
+> blocking issue is we need to export a simple RTL/LTR flag in siteinfo.
+
+Would it be easier if we just had Parsoid default to the (first?) localised string over the generic wikitext? This presumably doesn't need any MW API changes…",1401220172,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Yes, that is correct.  The patch was merged and then the language-specific parts were reverted because the way it selected the aliases was fragile in LTR languages.  This is still on my to-do list for a proper fix; IIRC the blocking issue is we need to export a simple RTL/LTR flag in siteinfo.",1401220107,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"The above was merged in January, but this bug isn't fixed AFAICT. Also, we should probably use the local wikitext over the English version in all languages, not just RTL ones.",1401215876,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 103082 had a related patch set uploaded by Cscott:
+Edited image attributes should override data-parsoid value.
+
+https://gerrit.wikimedia.org/r/103082",1387811331,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,I'm pretty sure our magic words support already has the appropriate localized keyword alias. We just aren't using it (yet).,1378921869,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"I went over the RTL languages and samples practical Wikipedia articles, and it seems that the first alias is always is always the most frequently used.
+
+Is there anything I can do to help move this forward? It's one of the most requested features.",1377641269,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"For the site info, look for ""rtl"" in http://he.wikipedia.org/w/api.php?action=query&meta=siteinfo&siprop=general&format=json",1376690239,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"We don't actually need to hard-code the list of rtl wikis, as that information is available in the site info returned by the API. It would still be good to check for each current rtl wiki if the first option alias is always a good one.",1376690182,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"In most ltr wikis the English version is actually the most commonly used today, which is why we went with serializing new content with the English defaults.
+
+This is not ideal for rtl languages though, as this leads to a mix of ltr and rtl text.
+
+If you can provide us with a list of rtl language codes and check for each if a common offset in the option aliases is a good default, then we can add a list of rtl languages to the serializer and use the localized defaults for those.",1376689406,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+VisualEditor: Disable 'Use existing reference' on pages without a reference,"Steps to reproduce
+1. start an empty sandbox (https://en.wikipedia.org/wiki/User:John_Vandenberg/mtgg?veaction=edit)
+2. insert reference
+3. use an existing reference
+
+Expected results:
+'Use an existing reference' should be disabled, as there are none to select.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50458",1374557100,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jx64nu32n5cymzvwwjp5,task_description,resolved
+VisualEditor: Disable 'Use existing reference' on pages without a reference,"Change 81964 merged by jenkins-bot:
+Re-build reference search index so they can be used mid-edit
+
+https://gerrit.wikimedia.org/r/81964",1377889945,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx64nu32n5cymzvwwjp5,task_subcomment,NA
+VisualEditor: Disable 'Use existing reference' on pages without a reference,Now fixed in master and will be deployed next week.,1377889832,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jx64nu32n5cymzvwwjp5,task_subcomment,NA
+VisualEditor: Disable 'Use existing reference' on pages without a reference,"Change 81964 had a related patch set uploaded by Trevor Parscal:
+[WIP] Bug 51689, bug 52000 & bug 51848 - Reusing new references
+
+https://gerrit.wikimedia.org/r/81964",1377886576,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jx64nu32n5cymzvwwjp5,task_subcomment,NA
+VisualEditor: Recursive word addition with Google Input Tools in reference tool on Firefox,"Steps to reproduce:
+1. Download and install Google input tools for windows www.google.co.in/inputtools
+2. Open any page in firefox
+3. Open VE
+4. Edit a reference
+5. Type anything in the reference. The word is input by the tools when the word is complete and one presses space/enter
+
+Expected Behaviour:
+The word is input and if the spacebar has been pressed, a space is input too.
+
+What happens instead:
+The word is entered recursively over and over. The space isn't input at all.
+
+System environment:
+Win 7 X64 SP1
+Firefox 15.0.1
+Google input tools for languages hindi and punjabi(gurmukhi script)
+
+The problem didn't seem to arise when using input tools for urdu, though its possible that's just coz the wiki is ltr and urdu is rtl.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374549360,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-6nas4q7uc475euchng3b,task_description,resolved
+VisualEditor: Recursive word addition with Google Input Tools in reference tool on Firefox,Confirming that this is fixed in Firefox 23.0.1 on Win7 X64 SP1 for both punjabi (gurmukhi script) and hindi.,1379503051,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-6nas4q7uc475euchng3b,task_subcomment,NA
+VisualEditor: Recursive word addition with Google Input Tools in reference tool on Firefox,"Marking this as ""FIXED"" on the expectation that it's fixed - please re-open if you find that it is still occurring.",1378958789,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6nas4q7uc475euchng3b,task_subcomment,NA
+VisualEditor: Recursive word addition with Google Input Tools in reference tool on Firefox,"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!",1378943165,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-6nas4q7uc475euchng3b,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Steps to reproduce:
+1. Open any page
+2. Open VE
+3. Type (or copy-paste) ग्र
+5. Press left arrow key
+
+What should happen:
+Cursor should move to the left of the glyph
+
+What happens:
+Cursor stays there
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 28.0.1500.72 m
+
+The problem arises regardless of what follows ग्र . I've tried with space, tab, the letter a, devanagari characters that do not combine with the glyph, like क, and devanagari characters that do combine with the glyph, such as ि to produce ग्रि and ी to produce ग्री
+
+The problem doesn't seem to affect firefox 15.0.1.
+
+In chrome, the problem doesn't arise in the link editing window, or when editing parameter of a template. It does, however, arise when editing a reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374547560,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xckf32rcb2yx56eieafj,task_description,resolved
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press",Have tested quite a lot and this seems fine.,1430334001,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Seems to be fixed now, though probably needs to be tested extensively before closing.",1424612816,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","18:32 < Sid-G> Hi. Can someone confirm if the fix for https://bugzilla.wikimedia.org/show_bug.cgi?id=51846 has been deployed to the wmf cluster?
+
+18:40 < mutante> Sid-G: hi
+18:40 < mutante> i dont know much about ve but yes, it looks deployed
+
+8:40 < mutante> checked one of those changed files on tin
+18:41 < mutante> /php-1.23wmf6/extensions/VisualEditor/modules/ve/ce/ve.ce.Document.js
+18:43 < mutante> Sid-G: and also confirmed on random app server, so not like somebody forgot to deploy
+18:43 < mutante> if it doesnt work it should actually need an additional fix
+
+18:45 < Sid-G> hmm, then i should reopen the bug
+18:45 < mutante> yes
+18:45 < mutante> please do
+
+18:58 < Sid-G> mutante: reopened. Is there an irc chan for VE?
+
+19:15 < legoktm> #mediawiki-visualeditor",1386992085,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press",We'll have to investigate. Sorry this isn't fixed yet!,1386989820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Reopening
+
+System Environment:
+Windows 7 X64 SP1
+Google Chrome 31.0.1650.63 m
+
+Urls:
+Same as in comment 6
+
+Glyphs:
+Same as in comment 0 , comment 1 and comment 6
+
+What happens:
+Crossing the glyphs now requires three keypresses going either left to right or right to left.",1386989489,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Has this been deployed? If it has, it hasn't fixed the problem. Please reopen if this has been deployed. Tried at both urls per comment 6.",1386469991,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Change 80689 merged by jenkins-bot:
+Revert model to use simple UTF-16 code units
+
+https://gerrit.wikimedia.org/r/80689",1385506399,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","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",1384946963,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press",There's code in progress to fix this in gerrit 80689 which is currently a work-in-progress.,1381269313,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Update:
+System Environment:
+Windows 7 X64 SP1
+Google Chrome 29.0.1547.76 m
+
+Tested at https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+न्स seems to now require three keystrokes. All the others listed in Comment 6 above along with ग्र भ्र श्र ष्र still require two keystrokes.",1380971530,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+It seems similar behaviour (both with and without the patch) occurs when a letter is followed by ् + स regardless of whether the glyph appears joined or not.
+
+To be clear, the same problem occurs with this cluster, and the patch works the same.
+
+Results with the patch for all consonants, tested at [1]:
+Glyph(s) -- Number of keystrokes needed (going either left to right or right to left)
+क्स ख्स ग्स घ्स ङ्स च्स छ्स ज्स झ्स ञ्स ट्स ठ्स ड्स ढ्स ण्स त्स थ्स द्स ध्स न्स प्स फ्स ब्स भ्स म्स य्स र्स ल्स व्स श्स ष्स स्स ह्स -- 2
+
+I have not tested the selection per key-press for these, but I expect the results would be same as those in Comment 5
+
+Results without the patch, tested at [2]:
+All of the clusters can be passed with one right arrow key press going from left to right. None can be passed going right to left on any number of left arrow key-presses.
+
+[1]: https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+[2]: https://hi.wikipedia.org/wiki/%E0%A4%B8%E0%A4%A6%E0%A4%B8%E0%A5%8D%E0%A4%AF:Siddhartha_Ghai/sandbox?veaction=edit",1379499369,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","(In reply to comment #4)
+> 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.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Tested this out at [1]. The cursor moves past the glyph on two left arrow keypresses.
+
+I tried selecting the text with the left arrow keypresses. Then I copy-pasted the selected text into an external text editor. It seems the first keypress takes the cursor past र and the second past ग्
+However, visually the caret seems to be unmoved after the first keypress (i.e it does not move past the glyph or into the glyph) and crosses the glyph after the second keypress.
+
+The patch also introduces an unintended side-effect. Crossing the glyph from the left to the right on right arrow keypress also takes two keypresses now. Without the patch, this used to take only one right arrow keypress. This correct behaviour can be currently seen at hindi wikipedia, specifically tested at [2]
+
+So the problem is partially fixed, but with side-effects.
+
+[1]: https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+[2]: https://hi.wikipedia.org/wiki/%E0%A4%B8%E0%A4%A6%E0%A4%B8%E0%A5%8D%E0%A4%AF:Siddhartha_Ghai/sandbox?veaction=edit",1379497039,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","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.",1378943340,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","(In reply to comment #2)
+> Hi,
+> 
+> You are referring problem to windows system based inscript input system , ULS
+> or any hindi devnagari input or any devnagari input including  Marathi and
+> Nepali ?
+> 
+> Regards
+
+The problem is not with the input method. It is with moving around the cursor when using visual editor. So, for example, if any letter followed by ् + र already exists on the wiki and you try to edit the page with visual editor, you can move the cursor across it from left to right, but not from right to left.
+
+As far as I understand the problem, it is specific to devanagari (not hindi), although I haven't specifically gone to mr or ne wikis to verify.",1377345735,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","(In reply to comment #1)
+> Update: Same problem seems to arise for any other letters followed by ् + र
+> to
+> form a combined glyph. Examples:भ्र श्र ष्र etc. It does not seem to arise
+> when
+> the glyph is not combined.
+
+Hi,
+
+You are referring problem to windows system based inscript input system , ULS or any hindi devnagari input or any devnagari input including  Marathi and Nepali ?
+
+Regards",1377236465,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press",Update: Same problem seems to arise for any other letters followed by ् + र to form a combined glyph. Examples:भ्र श्र ष्र etc. It does not seem to arise when the glyph is not combined.,1374618177,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+VisualEditor: Reference dialog re-use search form doesn't recognise uppercase group names,"The re-use tab in the reference dialog allows searching for group names. This was always possible. However, it doesn't work when the group name is uppercase or contains an uppercase character. For example, it works when the group name is ""note"" but not when the group name is ""A"". It doesn't matter if I search for ""a"" or ""A"", it's not found.
+
+Turns out the relevant code is incomplete ever since it was written in 2013, see https://gerrit.wikimedia.org/r/70364. The relevant ticket was {T51733}.",1374525480,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-2ms2vngz2briyomwp2bg,task_description,resolved
+VisualEditor: Reference dialog re-use search form doesn't recognise uppercase group names,"Change #1055393 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Fix reference search not working with uppercase groups/names%%%
+https://gerrit.wikimedia.org/r/1055393",1721641929,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2ms2vngz2briyomwp2bg,task_subcomment,NA
+VisualEditor: Reference dialog re-use search form doesn't recognise uppercase group names,"Change #1055393 had a related patch set uploaded (by Thiemo Kreuz (WMDE); author: Thiemo Kreuz (WMDE)):
+%%%[mediawiki/extensions/Cite@master] Fix reference search not working with uppercase groups/names%%%
+https://gerrit.wikimedia.org/r/1055393",1721382014,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2ms2vngz2briyomwp2bg,task_subcomment,NA
+VisualEditor: Reference dialog re-use search form doesn't recognise uppercase group names,"I'm not sure what's missing here. The group name always was searchable ever since the code was added in June 2013. I just tested it and it works with and without #Citoid. Maybe the code was not deployed when this ticket was written?
+
+https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/70364/27/modules/ve/ui/widgets/ve.ui.MWReferenceSearchWidget.js#123",1708623279,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-2ms2vngz2briyomwp2bg,task_subcomment,NA
+VisualEditor: Transclusion editor template search should additionally find in-string matches,"Split from bug 51436, Original comment was:
+""Also typing a word only shows template names starting with that word, not
+containing it, which is a weird search behaviour.
+
+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).""
+
+A further relevant comment was:
+""This is asking for VisualEditor ... 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.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51670",1374511680,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bcumpuzgy3avff6z7fio,task_description,open
+VisualEditor: Transclusion editor template search should additionally find in-string matches,"**crypticc62** wrote:
+
+Even if in-string searching is used instead of left-string completion, there is still the problem of templates whose names are completely unsearchable, such as {{rp}} and pretty much everything in [[Category:Typing-aid templates]].
+
+What would be very useful is a TemplateData field in which editors can list relevant keywords that users might search for. Perhaps it could be called ""keywords"" or ""tags"". Without something like this, it's not clear to me how new users would ever find the templates they're looking for.",1377222496,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bcumpuzgy3avff6z7fio,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","The VisualEditor's user manual is translatable in Meta, which is a Good Thing. Currently the help link uses Special:MyLanguage. This uses the user's UI language as defined on Meta, which is likely not to be the same as the user's UI language on a non-English site.
+
+As much as possible, the link should point directly to the user manual in the language that the user is using currently for the UI.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374488220,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-likhdovodmty4qer7rsq,task_description,open
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","That is intentional. Given the logged out users and many logged in users by default have English, it prefers the provided language code instead of interface language.",1473747184,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language",">>! In T53797#564658, @Nikerabbit wrote:
+> You could point to Special:MyLanguage/Page/<current ui language>. If the user is logged on mediawiki.org (which is quite likely), their interface language there will still overrule the provided language code :(
+
+That would probably be okay, but if I go to https://ta.wikipedia.org/wiki/Mw:Special:MyLanguage/Help:VisualEditor/User_guide/ta I get Tamil, even though I am logged in and my preference is en.",1473709455,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","(In reply to comment #2)
+> You could point to Special:MyLanguage/Page/<current ui language>. If the user
+> is logged on mediawiki.org (which is quite likely), their interface language
+> there will still overrule the provided language code :(
+
+To do this we'd have to have code that explicitly mangles an i18n string. This feels… deeply wrong. :-(",1375114805,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","You could point to Special:MyLanguage/Page/<current ui language>. If the user is logged on mediawiki.org (which is quite likely), their interface language there will still overrule the provided language code :(",1375086773,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","(In reply to comment #0)
+> The VisualEditor's user manual is translatable in Meta, which is a Good
+> Thing.
+> Currently the help link uses Special:MyLanguage. This uses the user's UI
+> language as defined on Meta, which is likely not to be the same as the user's
+> UI language on a non-English site.
+> 
+> As much as possible, the link should point directly to the user manual in the
+> language that the user is using currently for the UI.
+
+What is the recommended solution for this? Hard-code the link to be https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/<foo>? Wouldn't it be easier for the user's language to properly transfer to MW.org using ULS or whatever?",1374509348,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+VisualEditor: Non-English Wikipedia issues (tracking),"Tracking for VE issues of problems that are specific to a Wikipedia other than English Wikipedia, excluding RTL issues as they are tracked by bug 33126.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T51998}
+{T51999}",1374480780,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-oytsgsispcryv5y4kv3t,task_description,resolved
+VisualEditor: Non-English Wikipedia issues (tracking),Which project/tag was this replaced with?,1432541898,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-oytsgsispcryv5y4kv3t,task_subcomment,NA
+VisualEditor: Non-English Wikipedia issues (tracking),Replaced with projects.,1422425002,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oytsgsispcryv5y4kv3t,task_subcomment,NA
+VisualEditor: Non-English Wikipedia issues (tracking),"Since you dont want to track them, I have put myself as the assignee.
+
+I added issues that appear to be a much higher priority for non-English Wikipedia, or only reproducible on non-English Wikipedia.  If they affect all Wikipedia, remove them.
+
+We have had very few issues raised from non-English Wikis, and many of them had not even been confirmed until I worked through the Unconfirmed list yesterday.",1374528616,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-oytsgsispcryv5y4kv3t,task_subcomment,NA
+VisualEditor: Non-English Wikipedia issues (tracking),"It is not-unreasonable to use a tracking bug for language-specific issues, but almost all of the bugs cited here are not language-specific. Will remove those that are general VisualEditor issues.",1374508727,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oytsgsispcryv5y4kv3t,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","When you type ""[["" in visual editor, there is a ""wiki markup text"" popu (nice touch - Thanks, devs).
+
+However, this warning popup shows at top of page, so it's not visible when the page is scrolled even a few lines.
+
+VE toolbar floats at the top of the browser's page even when we edit at the middle of the article. the warning popu should do the same. 
+
+REPRODUCTION INSTRUCTIONS
+0) open [[en:The Rolling Stones]]
+1) select one of the sections from the TOC
+2) Click ""Edit""
+3) wait, wait, wait, wait...
+4) close the edit notice
+5) type ""[[""
+
+EXPECTED
+1) during the wait (3 above) there is a nice image asking you to wait: this image is expected to be visible
+
+2) when the ""edit notice"" shows up, you expect some clear way to close it.
+
+3) when typing ""[["", you expect the ""wikitext warning"" popup to show up
+
+WHAT ACTUALLY HAPPEN
+
+1) the ""please wait"" image appears, but unfortunately it's outside the screen, so you do not know why the page appears milky, and have no indication that this would eventually end.
+
+2) depending on your luck, clicking on various parts of the page *will* close the edit notice (if you're lucky), or will take you to [[en:Template:Editnotices/Page/The Rolling Stones]] (i.e., another page from the one you are trying to edit) if you're unlucky.
+
+3) the warning popup appears, but it's at the top of the page, so unless you are editing the very first part of the page, you do not see it.
+
+
+COMMENTS:
+1) VE is clever enough to have its toolbar visible even when scrolling down, using ""position:fixed"". same should be done for the ""please wait"" image and for the warning popup(s).
+
+2) the ""1 notice"" and the warning triangle on the toolbar should indicate that they are the gate to hiding the notice: e.g., change the ""1 Notice"" text to ""Hide notice"" when the notice is visible.
+
+3) it seems that the wikitext notice is not yet translated to all languages.
+
+
+peace.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374442980,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j46p5in7q2s26odkx5az,task_description,resolved
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","Sounds like the same thing.
+
+The other bug is older and the discussion on this one is mostly related to bug 50870, so I'll mark this one as a dupe of that one.
+
+*** This bug has been marked as a duplicate of bug 50206 ***",1379436668,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section",(is https://bugzilla.wikimedia.org/show_bug.cgi?id=50206 a dupe?),1379425952,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","(In reply to comment #3)
+> i know that opening a single ticket for 3 different issues is not a good
+> idea, and i apologize for doing something i know is wrong.
+
+As long as you don't do it again, no need to apologise. :-)",1374509581,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","Original bug talked about 3 (somewhat unrelated) things.
+
+The first one turned out to be duplicate of bug 50870, and not specific to VE (i think this is why i did not find it).
+
+However, the 2nd one *is* specific to VE, and i do not think bug 50870 covers it.
+
+so i changed the synopsis of this bug to indicate the 2nd problem, and i'm reopening it.
+
+i know that opening a single ticket for 3 different issues is not a good idea, and i apologize for doing something i know is wrong.
+
+(it's a bit confusing - ""1st"" and ""2nd"", appear as ""2"" and ""1"" in original ticket - i call ""2"" in comment #0 ""first"" because this was the synopsis of original ticket).
+
+peace.",1374506028,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","
+
+*** This bug has been marked as a duplicate of bug 50870 ***",1374449520,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","(In reply to comment #0)
+> 2) depending on your luck, clicking on various parts of the page *will* close
+> the edit notice (if you're lucky), or will take you to
+> [[en:Template:Editnotices/Page/The Rolling Stones]] (i.e., another page from
+> the one you are trying to edit) if you're unlucky.
+> 
+> 
+> peace.
+
+so here is what i mean: if you click on the page outside the ""edit notice"", nothing happens.
+if you click on the edit notice itself, then it depends: 
+some parts of the edit notice are links (including the images), and will take you elsewhere. there is no indication, because the edit notice as a whole has ""cursor: pointer;"" css attribute, so the mouse pointer looks the same everywhere on the edit notice. clicking somewhere which is not a link will close the notice, and clicking somewhere which *is* a link will take you elsewhere. again, there is little indication - e.g., moving the mouse into and out of images does not give any visible sign.
+clicking on the little ""page notice"" link *inside* the notice takes you elsewhere, while clicking on the ""1 notice"" on the toolbar closes the notice.
+very confusing.
+
+(btw: the notice itself seems to be anchored to the toolbar rather than to the page, which is exactly what's needed for the ""please wait"" image and for the wikitext popup).
+
+peace.",1374443710,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+VisualEditor: Structural content inside a <small> should be alienated but this fails because they are inline rather than inline-block,"In an (un)ordered list nested in a table I am unable to edit wikilinks. While hovering above a wikilink the wikilink is an active weblink, instead of showing the icon of the link inspector, see URL.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://test.wikipedia.org/wiki/User:Raymond/nested",1374430980,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-kvei76aer6u2clu7k444,task_description,duplicate
+VisualEditor: Structural content inside a <small> should be alienated but this fails because they are inline rather than inline-block,*** Bug 52285 has been marked as a duplicate of this bug. ***,1385396898,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kvei76aer6u2clu7k444,task_subcomment,NA
+VisualEditor: Structural content inside a <small> should be alienated but this fails because they are inline rather than inline-block,"Block nodes (like lists) in inline positions (like in <small>) get alienated as inline aliens. These inline aliens then don't get shields and phantoms with the right dimensions. One way to fix that could be to make alienInline display:inline-block instead of display:inline, which seems to fix the dimensions of the shield, but we'd have to carefully evaluate that as it would potentially impact a lot of things.",1385394281,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kvei76aer6u2clu7k444,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"From the mailing list
+
+> from:	 planetenxin <planetenxin@web.de> via gmail.com 
+> reply-to:	 Wikimedia developers <wikitech-l@lists.wikimedia.org>
+> to:	 wikitech-l <wikitech-l@lists.wikimedia.org>
+> date:	 Sun, Jul 21, 2013 at 10:15 PM
+> subject:	 [Wikitech-l] Git Proxy Error
+
+> Hi folks,
+> I'm constantly getting the following error on https://git.wikimedia.org/:
+> 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
+>/Alexander
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51656
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49371",1374410040,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-m7yoxj62gdjohzchm7zw,task_description,declined
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"The gitblit software powering git.wikimedia.org is in the process of being replaced by Phabricator Diffusion. See:
+
+{T111465}
+Project: #gitblit-deprecate",1441874873,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Maybe http://git.zx2c4.com/cgit/about/ might be an alternative to gitblit as its main design criterion is speed and caching.,1396988983,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"Just a heads-up: Upstream in https://code.google.com/p/gitblit/issues/detail?id=274 asks ""for discussion with Wikimedia folks on how to improve caching since the current strategy is not ideal"".",1378204045,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"max semenik reported that gitblit should mark critical links with rel=""nofollow""",1376771529,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,mark configured the misc varnish cluster for gitblit: https://gerrit.wikimedia.org/r/#/c/78262/,1376771436,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"browser cache problem reported upstream and fixed, see here:
+https://code.google.com/p/gitblit/issues/detail?id=274",1376771021,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"https://gerrit.wikimedia.org/r/#/c/78919/
+
+As soon as the bot picks up th new copy of the robots.txt file that should take care of it for now.",1376373844,PHID-USER-jtxavgb3caz53o45csni,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,faidon lambiotis restarted it a couple of hours ago withoutout tracing it seems? and now its dead again.,1376345034,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Stupid question: is crawl-delay in robots.txt worth trying?,1376334890,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"before restarting the java process, could you trace it with:
+* jps -l to find out the process id
+* strace to see if it excessivly calls into the operating system
+* jstack
+* kill -QUIT <p> to print the stacktrace
+* jmap -heap <p> to find memory usage
+* jmap -histo:live <p> | head to find excessivly used classes
+* if you have ui, you might try jconsole or http://visualvm.java.net as well
+
+you might want to set the java -XX:+HeapDumpOnOutOfMemoryError parameter when starting, so it writes a heap dump early enough. it can be analyzed with jhat.",1376253536,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,down again at the moment... i think gitblit might behave nicer in case bots overloading it.,1376218114,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Back up again at the moment...,1376185946,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #34)
+> created a bug at gitblit:
+> https://code.google.com/p/gitblit/issues/detail?id=294.
+
+No need for that, I've already been in contact with upstream. It's mainly being overloaded from Googlebot.",1376176292,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,created a bug at gitblit: https://code.google.com/p/gitblit/issues/detail?id=294.,1376168077,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"As reported by OsamaK last night in #wikimedia-tech and again today by rupert THURNER on wikitech-l (and I personally confirmed last evening), git.wikimedia.org is down yet again.
+
+---
+$ time curl https://git.wikimedia.org/
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>
+
+real	12m1.522s
+user	0m0.010s
+sys	0m0.026s
+---",1376146093,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"For the records: https://gerrit.wikimedia.org/r/#/c/78243/
+(By the way: Ariel & Daniel, thanks for keeping this ticket updated.)",1376021981,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,chad fixed up service of robots.txt and we've unblocked the google bot.  Waiting for verification that google has picked up the file and we'll see how performance looks after that.,1375978732,PHID-USER-jtxavgb3caz53o45csni,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,(Resetting severity & priority as long as things are working again.),1375952067,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"merged this:
+
+https://gerrit.wikimedia.org/r/#/c/77909/1/templates/apache/sites/git.wikimedia.org.erb
+
+and:
+
+08:42 mutante: on overloaded antimony: stopped gitblit, ran puppet, blocked Googlebot, restarted apache and gitblit
+08:22 mutante: git.wikimedia.org back
+08:21 mutante: attempted to restart gitblit on antimony 
+
+01:44 < mutante> apergos: oh.. Googlebot-Image/1.0 != Googlebot ?
+01:44 < apergos> no
+01:44 < apergos> googlebot is the one that rate limited
+01:44 < apergos> that should be enough, it's the /zip/ paths primarily that were the problem
+01:44 < mutante> Googlebot-Image is the one still being very active
+01:44 < mutante> ok
+01:44 < apergos> it's minor compared to the rest
+01:44 < mutante> alright
+01:44 < apergos> I did a count from the logs yeasterday
+01:45 < mutante> now YandexBot kicking in :)
+01:45 < apergos> please note it on the bz report so we don't forget
+01:46 < mutante> java CPU usage isn't > 500% anymore though :)",1375951706,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"Turns out that we were serving an empty robots.txt even though there is content. Logs show lots of:
+[Wed Aug 07 21:44:15 2013] [error] [client XXX.XXX.XXX.XXX] proxy: Error reading from remote server returned by /robots.txt
+
+Chad says this is likely due to some fancy proxy rewriting sending everything to gitblit.  In the meantime the google folks have cut back both parallel open connections and req/sec until we have this sorted and can give them the heads up.",1375913787,PHID-USER-jtxavgb3caz53o45csni,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"I'm talking to the folks at google about it, will update as soon as I have more info.",1375906393,PHID-USER-jtxavgb3caz53o45csni,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Google is the one misbehaving.,1375825195,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #24)
+> > Do the misbehaving bots respect robots.txt?
+> 
+> Nope.
+
+Just to be clear, I hope that you block whatever wished and needed except Google (so that we have at least one search engine).",1375823311,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #23)
+> (In reply to comment #22)
+> > So bots aren't going to be allowed to index gitblit anymore since they can't
+> > seem to behave.
+> 
+> Do the misbehaving bots respect robots.txt?
+
+Nope.",1375822950,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #22)
+> So bots aren't going to be allowed to index gitblit anymore since they can't
+> seem to behave.
+
+Do the misbehaving bots respect robots.txt?",1375822567,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,So bots aren't going to be allowed to index gitblit anymore since they can't seem to behave.,1375822451,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #20)
+> Down again?
+
+Indeed. :-(
+
+---
+$ time curl https://git.wikimedia.org/
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>
+
+real	12m2.101s
+user	0m0.010s
+sys	0m0.028s
+---",1375816643,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Down again?,1375791780,PHID-USER-wz5bw3q6zykhqbbeohzq,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Restarted service.,1375681588,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #17)
+> It's again inaccessible (my browser doesn't receive any reply) with antimony
+> at 100 % load.
+
+Confirmed that git.wikimedia.org is inaccessible currently; no idea about antimony's load.
+
+Re-opening this bug as it's no longer resolved. Thank you, Nemo, for commenting here.
+
+---
+$ time curl https://git.wikimedia.org/
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>
+
+real	12m43.815s
+user	0m0.010s
+sys	0m0.024s
+---",1375669136,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,It's again inaccessible (my browser doesn't receive any reply) with antimony at 100 % load.,1375636764,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Closing this as resolved/fixed for now.,1374687493,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"So, it's a little sluggish still but it's at least staying up. Did some more puppetizing and blocked some misbehaving spiders that were causing it to fall over all the time.
+
+Still want to up the heap and see if we can get some better performance out of it.",1374618927,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,I've got some new caching stuff that landed in master just for us :) Looking at turning that on today as well.,1374601182,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #5)
+> For the record, it doesn't seem to be completely down, just really slow to
+> respond.
+
+To me it just serves ""Internal error"" messages. When CPU usage goes down a bit, you may happen to get some content, maybe curl is just being very patient and retrying a lot till that happens.",1374600397,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #10)
+> git.wikimedia.org continues to be broken. This is very frustrating.
+
+You're telling me :(",1374597058,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,We cant take stack trace right now since gitblit is running with Java 6 and we are missing the jstack utility.  That is bug 51859.,1374573819,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,git.wikimedia.org continues to be broken. This is very frustrating.,1374566967,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #8)
+>  14:42 apergos: (btw docs would be nice, is that really the right way to kick
+> it?)
+> 14:42 apergos: shot and restarted gitblit: on antinomy, cd /var/lib/gitblit,
+> java -jar gitblit.jar & (see bug 51769) 
+> 
+> Can we help Ariel out? :)
+
+Peachey88 helpfully created <https://wikitech.wikimedia.org/wiki/Git.wikimedia.org> and <https://wikitech.wikimedia.org/wiki/Gitblit>. Thank you, Peachey88!",1374518718,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot," 14:42 apergos: (btw docs would be nice, is that really the right way to kick it?)
+14:42 apergos: shot and restarted gitblit: on antinomy, cd /var/lib/gitblit, java -jar gitblit.jar & (see bug 51769) 
+
+Can we help Ariel out? :)",1374511097,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,This seems to be an issue again.,1374502907,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"Restarted the service again. Nothing was suspicious in the logs, but CPU was pegged at 100% :\",1374473332,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"For the record, it doesn't seem to be completely down, just really slow to respond. When I tried again, I got:
+
+$ time curl https://git.wikimedia.org
+<!DOCTYPE html PUBLIC ""-//W3C//DTD XHTML 1.0 Strict//EN"" ""http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"">
+<html xmlns=""http://www.w3.org/1999/xhtml"" xml:lang=""en"" lang=""en"" ng-app=""""> 
+
+	<!-- Head -->
+	<head>
+		<meta name=""viewport"" content=""width=device-width, initial-scale=1.0"">
+		<meta http-equiv=""X-UA-Compatible"" content=""IE=Edge"" />
+   		<title>Wikimedia</title>
+		<link rel=""icon"" href=""gitblt-favicon.png"" type=""image/png""/>
+		
+		<link rel=""stylesheet"" href=""bootstrap/css/bootstrap.css""/>
+		<link rel=""stylesheet"" href=""bootstrap/css/iconic.css""/>
+		<link rel=""stylesheet"" type=""text/css"" href=""gitblit.css""/>
+	<link rel=""stylesheet"" type=""text/css"" href=""bootstrap/css/bootstrap-responsive.css"" />
+<style type=""text/css"">
+.navbar-inner {
+background-color: #FBFBFB;
+border-bottom: 1px solid #39688E !important;
+}
+.navbar ul li:focus, .navbar .active {
+border-bottom: 4px solid #9C000F;
+}
+.navbar ul.nav li a {
+color: #002060;
+}
+.navbar ul.nav .active a {
+color: #002060;
+}
+.navbar ul.nav li a:hover {
+color: #002060 !important;
+}
+</style>
+<script type=""text/javascript"" src=""https://www.google.com/jsapi""></script>
+<script type=""text/javascript"" ><!--/*--><![CDATA[/*><!--*/
+google.load(""visualization"", ""1"", {packages:[""corechart""]});
+google.setOnLoadCallback(drawChart);
+function drawChart() {
+var data_ffa5c540 = new google.visualization.DataTable();
+data_ffa5c540.addColumn('string', 'repository');
+data_ffa5c540.addColumn('number', 'commits');
+data_ffa5c540.addRows(85);
+data_ffa5c540.setValue(0, 0, 'mediawiki/core');
+data_ffa5c540.setValue(0, 1, 2.0);
+data_ffa5c540.setValue(1, 0, 'mediawiki/extensions');
+data_ffa5c540.setValue(1, 1, 2.0);
+data_ffa5c540.setValue(2, 0, 'mediawiki/extensions/TranslationNotifications');
+data_ffa5c540.setValue(2, 1, 2.0);
+data_ffa5c540.setValue(3, 0, 'mediawiki/extensions/PollNY');
+data_ffa5c540.setValue(3, 1, 1.0);
+data_ffa5c540.setValue(4, 0, 'mediawiki/extensions/Nuke');
+data_ffa5c540.setValue(4, 1, 1.0);
+data_ffa5c540.setValue(5, 0, 'mediawiki/extensions/LastModified');
+data_ffa5c540.setValue(5, 1, 1.0);
+data_ffa5c540.setValue(6, 0, 'mediawiki/extensions/MoodBar');
+data_ffa5c540.setValue(6, 1, 1.0);
+data_ffa5c540.setValue(7, 0, 'mediawiki/extensions/Validator');
+data_ffa5c540.setValue(7, 1, 1.0);
+data_ffa5c540.setValue(8, 0, 'mediawiki/extensions/Phalanx');
+data_ffa5c540.setValue(8, 1, 1.0);
+data_ffa5c540.setValue(9, 0, 'mediawiki/extensions/MassEditRegex');
+data_ffa5c540.setValue(9, 1, 1.0);
+var chart_ffa5c540 = new google.visualization.PieChart(document.getElementById('chartRepositories'));
+chart_ffa5c540.draw(data_ffa5c540, { title: 'active repositories', colors:['#3810a6','#7110a6','#1068a6','#a61029','#1056a6','#63a610','#a64210','#109ca6','#7610a6','#a61083',], legend: { position:'none' } });
+
+var data_39b7080b = new google.visualization.DataTable();
+data_39b7080b.addColumn('string', 'author');
+data_39b7080b.addColumn('number', 'commits');
+data_39b7080b.addRows(17);
+data_39b7080b.setValue(0, 0, 'jeroendedauw');
+data_39b7080b.setValue(0, 1, 28.0);
+data_39b7080b.setValue(1, 0, 'Ori Livneh');
+data_39b7080b.setValue(1, 1, 12.0);
+data_39b7080b.setValue(2, 0, 'Kunal Mehta');
+data_39b7080b.setValue(2, 1, 6.0);
+data_39b7080b.setValue(3, 0, 'Yuki Shira');
+data_39b7080b.setValue(3, 1, 4.0);
+data_39b7080b.setValue(4, 0, 'legoktm');
+data_39b7080b.setValue(4, 1, 3.0);
+data_39b7080b.setValue(5, 0, 'Hoo man');
+data_39b7080b.setValue(5, 1, 2.0);
+data_39b7080b.setValue(6, 0, 'Santhosh Thottingal');
+data_39b7080b.setValue(6, 1, 2.0);
+data_39b7080b.setValue(7, 0, 'Jeroen De Dauw');
+data_39b7080b.setValue(7, 1, 2.0);
+data_39b7080b.setValue(8, 0, 'Kip');
+data_39b7080b.setValue(8, 1, 2.0);
+data_39b7080b.setValue(9, 0, 'Marius Hoch');
+data_39b7080b.setValue(9, 1, 2.0);
+var chart_39b7080b = new google.visualization.PieChart(document.getElementById('chartAuthors'));
+chart_39b7080b.draw(data_39b7080b, { title: 'active authors', colors:['#a6106c','#71a610','#a1a610','#a61040','#a68010','#a68010','#a67410','#1022a6','#104ca6','#1080a6',], legend: { position:'none' } });
+
+}
+
+/*-->]]>*/</script>
+
+<script type=""text/javascript"" src=""resources/com.gitblit.wicket.ng.NgController/angular.js""></script>
+<script type=""text/javascript"" ><!--/*--><![CDATA[/*><!--*/
+<!-- AngularJS projectsCtrl data controller -->
+function projectsCtrl($scope) {
+	$scope.projectsList = [{""p"":""mediawiki"",""n"":""mediawiki"",""t"":""18 mins ago"",""d"":""2013-07-22"",""i"":"""",""c"":626},{""p"":""labs"",""n"":""labs"",""t"":""5 hours ago"",""d"":""2013-07-21"",""i"":"""",""c"":9},{""p"":""operations"",""n"":""operations"",""t"":""8 hours ago"",""d"":""2013-07-21"",""i"":"""",""c"":72},{""p"":""main"",""n"":""Main Repositories"",""t"":""15 hours ago"",""d"":""2013-07-21"",""i"":""main group of repositories"",""c"":19},{""p"":""pywikibot"",""n"":""pywikibot"",""t"":""21 hours ago"",""d"":""2013-07-21"",""i"":"""",""c"":4},{""p"":""analytics"",""n"":""analytics"",""t"":""2 days ago"",""d"":""2013-07-20"",""i"":"""",""c"":39},{""p"":""wikimedia"",""n"":""wikimedia"",""t"":""3 days ago"",""d"":""2013-07-19"",""i"":"""",""c"":24},{""p"":""integration"",""n"":""integration"",""t"":""3 days ago"",""d"":""2013-07-19"",""i"":"""",""c"":11},{""p"":""qa"",""n"":""qa"",""t"":""3 days ago"",""d"":""2013-07-19"",""i"":"""",""c"":1},{""p"":""apps"",""n"":""apps"",""t"":""4 days ago"",""d"":""2013-07-18"",""i"":"""",""c"":4},{""p"":""wiktionary"",""n"":""wiktionary"",""t"":""4 weeks ago"",""d"":""2013-06-21"",""i"":"""",""c"":1},{""p"":""test"",""n"":""test"",""t"":""8 weeks ago"",""d"":""2013-05-25"",""i"":"""",""c"":2},{""p"":""officeit"",""n"":""officeit"",""t"":""4 months ago"",""d"":""2013-04-08"",""i"":"""",""c"":1},{""p"":""VisualEditor"",""n"":""VisualEditor"",""t"":""6 months ago"",""d"":""2013-01-29"",""i"":"""",""c"":1},{""p"":""glam"",""n"":""glam"",""t"":""10 months ago"",""d"":""2012-10-11"",""i"":"""",""c"":1}];
+}
+
+/*-->]]>*/</script>
+
+<script type=""text/javascript"" ><!--/*--><![CDATA[/*><!--*/
+<!-- AngularJS activeCtrl data controller -->
+function activeCtrl($scope) {
+	$scope.activeList = [{""r"":""mediawiki/extensions.git"",""n"":""extensions"",""p"":""mediawiki/"",""t"":""18 mins ago"",""d"":""2013-07-22"",""i"":"""",""s"":0,""c"":""#7110a6"",""wc"":0},{""r"":""mediawiki/core.git"",""n"":""core"",""p"":""mediawiki/"",""t"":""2 hours ago"",""d"":""2013-07-22"",""i"":"""",""s"":0,""c"":""#3810a6"",""wc"":0},{""r"":""mediawiki/extensions/TranslationNotifications.git"",""n"":""TranslationNotifications"",""p"":""mediawiki/extensions/"",""t"":""2 hours ago"",""d"":""2013-07-22"",""i"":"""",""s"":0,""c"":""#1068a6"",""wc"":0},{""r"":""mediawiki/extensions/LaTeXML.git"",""n"":""LaTeXML"",""p"":""mediawiki/extensions/"",""t"":""5 hours ago"",""d"":""2013-07-22"",""i"":"""",""s"":0,""c"":""#a67b10"",""wc"":0},{""r"":""labs/tools/lolrrit.git"",""n"":""lolrrit"",""p"":""labs/tools/"",""t"":""5 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a6102e"",""wc"":0},{""r"":""mediawiki/extensions/PollNY.git"",""n"":""PollNY"",""p"":""mediawiki/extensions/"",""t"":""7 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61029"",""wc"":0},{""r"":""operations/puppet.git"",""n"":""puppet"",""p"":""operations/"",""t"":""8 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#106ca6"",""wc"":0},{""r"":""mediawiki/extensions/Wikibase.git"",""n"":""Wikibase"",""p"":""mediawiki/extensions/"",""t"":""9 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a310a6"",""wc"":0},{""r"":""mediawiki/extensions/EventLogging.git"",""n"":""EventLogging"",""p"":""mediawiki/extensions/"",""t"":""9 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a631"",""wc"":0},{""r"":""mediawiki/extensions/WikimediaMessages.git"",""n"":""WikimediaMessages"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64510"",""wc"":0},{""r"":""mediawiki/extensions/Wikilog.git"",""n"":""Wikilog"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a6106c"",""wc"":0},{""r"":""mediawiki/extensions/WikiLexicalData.git"",""n"":""WikiLexicalData"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#101da6"",""wc"":0},{""r"":""mediawiki/extensions/WikiForum.git"",""n"":""WikiForum"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a618"",""wc"":0},{""r"":""mediawiki/extensions/WikiEditor.git"",""n"":""WikiEditor"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#8310a6"",""wc"":0},{""r"":""mediawiki/extensions/VisualEditor.git"",""n"":""VisualEditor"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1aa610"",""wc"":0},{""r"":""mediawiki/extensions/Validator.git"",""n"":""Validator"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#109ca6"",""wc"":0},{""r"":""mediawiki/extensions/UserMerge.git"",""n"":""UserMerge"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#2ea610"",""wc"":0},{""r"":""mediawiki/extensions/UploadWizard.git"",""n"":""UploadWizard"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#3110a6"",""wc"":0},{""r"":""mediawiki/extensions/UniversalLanguageSelector.git"",""n"":""UniversalLanguageSelector"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#6510a6"",""wc"":0},{""r"":""mediawiki/extensions/TwnMainPage.git"",""n"":""TwnMainPage"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#8d10a6"",""wc"":0},{""r"":""mediawiki/extensions/Translate.git"",""n"":""Translate"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1099a6"",""wc"":0},{""r"":""mediawiki/extensions/Sudo.git"",""n"":""Sudo"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61060"",""wc"":0},{""r"":""mediawiki/extensions/SemanticMediaWiki.git"",""n"":""SemanticMediaWiki"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a627"",""wc"":0},{""r"":""mediawiki/extensions/SemanticForms.git"",""n"":""SemanticForms"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61013"",""wc"":0},{""r"":""mediawiki/extensions/SemanticDrilldown.git"",""n"":""SemanticDrilldown"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61074"",""wc"":0},{""r"":""mediawiki/extensions/SecurePoll.git"",""n"":""SecurePoll"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61079"",""wc"":0},{""r"":""mediawiki/extensions/RevisionCommentSupplement.git"",""n"":""RevisionCommentSupplement"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#102ca6"",""wc"":0},{""r"":""mediawiki/extensions/Renameuser.git"",""n"":""Renameuser"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a6a3"",""wc"":0},{""r"":""mediawiki/extensions/ProofreadPage.git"",""n"":""ProofreadPage"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#3110a6"",""wc"":0},{""r"":""mediawiki/extensions/Premoderation.git"",""n"":""Premoderation"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#7ea610"",""wc"":0},{""r"":""mediawiki/extensions/Phalanx.git"",""n"":""Phalanx"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#7610a6"",""wc"":0},{""r"":""mediawiki/extensions/PageSchemas.git"",""n"":""PageSchemas"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64510"",""wc"":0},{""r"":""mediawiki/extensions/OpenStackManager.git"",""n"":""OpenStackManager"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a62c"",""wc"":0},{""r"":""mediawiki/extensions/OAuth.git"",""n"":""OAuth"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a636"",""wc"":0},{""r"":""mediawiki/extensions/Nuke.git"",""n"":""Nuke"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1056a6"",""wc"":0},{""r"":""mediawiki/extensions/NewUserMessage.git"",""n"":""NewUserMessage"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1051a6"",""wc"":0},{""r"":""mediawiki/extensions/MoodBar.git"",""n"":""MoodBar"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64210"",""wc"":0},{""r"":""mediawiki/extensions/MobileFrontend.git"",""n"":""MobileFrontend"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#4ca610"",""wc"":0},{""r"":""mediawiki/extensions/MathSearch.git"",""n"":""MathSearch"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a63110"",""wc"":0},{""r"":""mediawiki/extensions/Math.git"",""n"":""Math"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#97a610"",""wc"":0},{""r"":""mediawiki/extensions/MassMessage.git"",""n"":""MassMessage"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#36a610"",""wc"":0},{""r"":""mediawiki/extensions/MassEditRegex.git"",""n"":""MassEditRegex"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61083"",""wc"":0},{""r"":""mediawiki/extensions/Maintenance.git"",""n"":""Maintenance"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#9910a6"",""wc"":0},{""r"":""mediawiki/extensions/LiquidThreads.git"",""n"":""LiquidThreads"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a68810"",""wc"":0},{""r"":""mediawiki/extensions/LinkFilter.git"",""n"":""LinkFilter"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1038a6"",""wc"":0},{""r"":""mediawiki/extensions/LastModified.git"",""n"":""LastModified"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#63a610"",""wc"":0},{""r"":""mediawiki/extensions/InviteSignup.git"",""n"":""InviteSignup"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a67b10"",""wc"":0},{""r"":""mediawiki/extensions/Interwiki.git"",""n"":""Interwiki"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61033"",""wc"":0},{""r"":""mediawiki/extensions/ImageMap.git"",""n"":""ImageMap"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a654"",""wc"":0},{""r"":""mediawiki/extensions/GoogleMaps.git"",""n"":""GoogleMaps"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#83a610"",""wc"":0},{""r"":""mediawiki/extensions/GlobalBlocking.git"",""n"":""GlobalBlocking"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#7610a6"",""wc"":0},{""r"":""mediawiki/extensions/GettingStarted.git"",""n"":""GettingStarted"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#4510a6"",""wc"":0},{""r"":""mediawiki/extensions/FlaggedRevs.git"",""n"":""FlaggedRevs"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#9710a6"",""wc"":0},{""r"":""mediawiki/extensions/ExpandTemplates.git"",""n"":""ExpandTemplates"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61042"",""wc"":0},{""r"":""mediawiki/extensions/EducationProgram.git"",""n"":""EducationProgram"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#65a610"",""wc"":0},{""r"":""mediawiki/extensions/Editcount.git"",""n"":""Editcount"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1036a6"",""wc"":0},{""r"":""mediawiki/extensions/Echo.git"",""n"":""Echo"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64f10"",""wc"":0},{""r"":""mediawiki/extensions/DiscussionThreading.git"",""n"":""DiscussionThreading"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a68d10"",""wc"":0},{""r"":""mediawiki/extensions/Disambiguator.git"",""n"":""Disambiguator"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a63b10"",""wc"":0},{""r"":""mediawiki/extensions/DeleteBatch.git"",""n"":""DeleteBatch"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#104fa6"",""wc"":0},{""r"":""mediawiki/extensions/DataValues.git"",""n"":""DataValues"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64f10"",""wc"":0},{""r"":""mediawiki/extensions/DataTransfer.git"",""n"":""DataTransfer"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61018"",""wc"":0},{""r"":""mediawiki/extensions/ConfirmEdit.git"",""n"":""ConfirmEdit"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a6108d"",""wc"":0},{""r"":""mediawiki/extensions/ConfirmAccount.git"",""n"":""ConfirmAccount"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#7ba610"",""wc"":0},{""r"":""mediawiki/extensions/Configure.git"",""n"":""Configure"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#36a610"",""wc"":0},{""r"":""mediawiki/extensions/Comments.git"",""n"":""Comments"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#8f10a6"",""wc"":0},{""r"":""mediawiki/extensions/Commentbox.git"",""n"":""Commentbox"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a62910"",""wc"":0},{""r"":""mediawiki/extensions/Collection.git"",""n"":""Collection"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a66a10"",""wc"":0},{""r"":""mediawiki/extensions/CheckUser.git"",""n"":""CheckUser"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61045"",""wc"":0},{""r"":""mediawiki/extensions/CentralNotice.git"",""n"":""CentralNotice"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a68d"",""wc"":0},{""r"":""mediawiki/extensions/CentralAuth.git"",""n"":""CentralAuth"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a65e10"",""wc"":0},{""r"":""mediawiki/extensions/Campaigns.git"",""n"":""Campaigns"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#13a610"",""wc"":0},{""r"":""mediawiki/extensions/BookManagerv2.git"",""n"":""BookManagerv2"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#56a610"",""wc"":0},{""r"":""mediawiki/extensions/Babel.git"",""n"":""Babel"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1085a6"",""wc"":0},{""r"":""mediawiki/extensions/ArticleFeedbackv5.git"",""n"":""ArticleFeedbackv5"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a65110"",""wc"":0},{""r"":""mediawiki/extensions/Ads.git"",""n"":""Ads"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a3a6"",""wc"":0},{""r"":""mediawiki/extensions/AbuseFilter.git"",""n"":""AbuseFilter"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#4aa610"",""wc"":0},{""r"":""mediawiki/extensions/APC.git"",""n"":""APC"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#6c10a6"",""wc"":0},{""r"":""openzim.git"",""n"":""openzim"",""p"":"""",""t"":""15 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a66310"",""wc"":0},{""r"":""mediawiki/extensions/WikibaseDataModel.git"",""n"":""WikibaseDataModel"",""p"":""mediawiki/extensions/"",""t"":""15 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#6510a6"",""wc"":0},{""r"":""mediawiki/extensions/WikibaseQueryEngine.git"",""n"":""WikibaseQueryEngine"",""p"":""mediawiki/extensions/"",""t"":""16 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a68f10"",""wc"":0},{""r"":""mediawiki/extensions/UpdateMediaWiki.git"",""n"":""UpdateMediaWiki"",""p"":""mediawiki/extensions/"",""t"":""16 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#2910a6"",""wc"":0},{""r"":""mediawiki/extensions/Serialization.git"",""n"":""Serialization"",""p"":""mediawiki/extensions/"",""t"":""16 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1045a6"",""wc"":0},{""r"":""mediawiki/extensions/WikibaseDatabase.git"",""n"":""WikibaseDatabase"",""p"":""mediawiki/extensions/"",""t"":""16 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a627"",""wc"":0},{""r"":""mediawiki/extensions/Diff.git"",""n"":""Diff"",""p"":""mediawiki/extensions/"",""t"":""17 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a66a10"",""wc"":0},{""r"":""mediawiki/extensions/Ask.git"",""n"":""Ask"",""p"":""mediawiki/extensions/"",""t"":""17 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a67b"",""wc"":0},{""r"":""pywikibot/core.git"",""n"":""core"",""p"":""pywikibot/"",""t"":""21 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#22a610"",""wc"":0}];
+}
+
+/*-->]]>*/</script>
+
+</head>
+
+	<body>
+
+		<!-- page content -->
+		[a metric fuckton of HTML]
+
+		<!-- Override Bootstrap's responsive menu background highlighting -->
+		<style>
+		@media (max-width: 979px) {
+			.nav-collapse .nav > li > a:hover, .nav-collapse .dropdown-menu a:hover {
+				background-color: #002060;
+			}
+			
+			.navbar div > ul .dropdown-menu li a {
+				color: #ccc;
+			}
+		}
+		</style>
+		
+		<!-- Include scripts at end for faster page loading -->
+		<script type=""text/javascript"" src=""bootstrap/js/jquery.js""></script>
+		<script type=""text/javascript"" src=""bootstrap/js/bootstrap.js""></script>		
+	</body>
+</html>
+real	10m1.110s
+user	0m0.018s
+sys	0m0.028s",1374468963,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"It's happening again. :-(
+
+$ time curl https://git.wikimedia.org
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>
+
+real	12m1.110s
+user	0m0.015s
+sys	0m0.021s",1374468155,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+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.",1374450350,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,git.wikimedia.org being down is highly disruptive to support work in #mediawiki.,1374442461,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+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/
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>",1374427922,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+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",1374370800,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-iycnxhmj2yiay4bvfsic,task_description,resolved
+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?",1381630832,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-iycnxhmj2yiay4bvfsic,task_subcomment,NA
+VisualEditor: Bypass browser blacklist,"You can already bypass the blacklist by using ?vewhitelist=1 - sorry, we should document this somewhere!",1377532459,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iycnxhmj2yiay4bvfsic,task_subcomment,NA
+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.",1374372834,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-iycnxhmj2yiay4bvfsic,task_subcomment,NA
+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",1374347580,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4imcgove7xglvcqm25ym,task_description,resolved
+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.",1437778276,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+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?,1430994055,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+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 <pre> 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.",1425550174,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+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...",1425486185,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+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.,1378654619,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+"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",1374332100,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-6gr7275ayzz2al57mitp,task_description,resolved
+"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit",Verified in betalabs.,1416959359,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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]]",1416955369,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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",1416955169,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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.,1395357064,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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.",1390933967,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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.",1378458535,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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. ***,1378458424,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+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",1374320940,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_description,resolved
+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",1386964645,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1386964633,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1386964508,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1386964432,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+Default whitespace for headings should include spaces before/after ==,Yes. Will be deployed today. Closing this bug now.,1386171623,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+Default whitespace for headings should include spaces before/after ==,I assume this is fixed now? Thank you!,1386166246,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1386114683,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1385054475,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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.",1385053828,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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?",1385053073,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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.",1383167033,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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.",1374331135,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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.",1374330631,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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?",1374330299,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+"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}",1374285540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_description,resolved
+"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.",1535731638,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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.",1450389552,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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. ***,1415063196,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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'",1374756959,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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}",1374633830,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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.",1374538584,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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:
+<ref>[http://gypsywaggons.co.uk/varhistory.htm ""History of the Vardo (Gypsy Caravan)""], ValleyStream Media, 2009</ref>
+
+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?",1374296176,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+Parsoid: Output MathJax rendering for Math tags instead of images,"When MathJax is enabled we should render a <span> containing TeX, instead of an image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374264060,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m5725ohwtikdne7f72hd,task_description,invalid
+Parsoid: Output MathJax rendering for Math tags instead of images,MathJax support is discountinued T99369,1442497839,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.,1402834289,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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).",1378528443,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378509011,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378492816,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378428362,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378426992,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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?",1378359915,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378359248,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378354273,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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] <gwicke> do you have a node package?
+[17:03] <pkrautzberger> ah. no. The problem is that MathJax requires a dom  right now. But we plan to liberate parts.
+[17:03] <gwicke> we have a dom
+[17:03] <pkrautzberger> (a lot functionality doesn't make sense outside the DOM).
+[17:04] <gwicke> domino currently
+[17:04] <pkrautzberger> but TeX2MathML conversion could be isolated easily (MathML to SVG not as easily). BTW our internal format is MathML.
+[17:04] <gwicke> it only implements DOM4 in case that makes a difference
+[17:04] <pkrautzberger> I'm not sure if dom4 would be a problem.
+[17:04] <pkrautzberger> but we've seen people use dom runners.
+[17:04] <gwicke> we could also use JSDom for math if that helps
+[17:05] <gwicke> supports the other levels
+[17:05] <gwicke> and script tag execution
+[17:05] <pkrautzberger> well, ideally we could just isolate that from the dom.
+[17:05] <pkrautzberger> but yes, I know someone who got jsdom to work with MathJax.
+[17:06] <gwicke> ah, that sounds promising",1378339833,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+Parsoid: Output MathJax rendering for Math tags instead of images,See bug 52031.,1376614484,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+Parsoid: Output MathJax rendering for Math tags instead of images,Have we filed a bug against the mw api to support this?,1374764072,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1374265056,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1374264665,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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",1374238320,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_description,resolved
+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",1380811545,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380751646,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380747187,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380746244,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380742224,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380644334,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"I have a patch for this one, taking it.",1380644270,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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.",1376614725,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,Can't reproduce on enwp for obvious reasons.,1375060582,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Created attachment 12996
+screenshot of adding a wikipedia: link
+
+**Attached**: {F11284}",1375060388,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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.",1374644195,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1374234180,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-boasjpxas32sxaoibmuy,task_description,resolved
+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.
+",1434487685,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-boasjpxas32sxaoibmuy,task_subcomment,NA
+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.",1374236089,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-boasjpxas32sxaoibmuy,task_subcomment,NA
+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}",1374229560,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-q5ayyohzxfrkbwwrho46,task_description,resolved
+VisualEditor: Search of parameters in transclusion editor should be case insensitive,Done by gerrit 117305.,1394405793,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q5ayyohzxfrkbwwrho46,task_subcomment,NA
+VisualEditor: Search of parameters in transclusion editor should be case insensitive,*** Bug 52950 has been marked as a duplicate of this bug. ***,1377426861,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-q5ayyohzxfrkbwwrho46,task_subcomment,NA
+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.",1374229905,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-q5ayyohzxfrkbwwrho46,task_subcomment,NA
+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}",1374229080,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_description,resolved
+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.,1394073936,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_subcomment,NA
+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.",1375339576,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_subcomment,NA
+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?",1375325672,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_subcomment,NA
+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.",1374700322,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_subcomment,NA
+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",1374224700,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_description,resolved
+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.",1403019840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_subcomment,NA
+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.,1403008896,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_subcomment,NA
+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,1380426562,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_subcomment,NA
+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.)"".",1379948638,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_subcomment,NA
+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",1374197220,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4iqn2br77eamftwdpwfs,task_description,resolved
+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",1405459729,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+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",1405459572,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+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",1397086933,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+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",1397086880,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+VisualEditor: Remove (and stop adding) useless documentation,Note that there is one (exactly one) piece of useful information in that comment: @abstract,1374259388,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+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",1374179400,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-udzfkpaotefzeteimh7e,task_description,declined
+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.",1703380210,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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.",1422061964,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+Page actions are wrong for VisualEditor,@aklapper  Hmm..  This should not be assigned to me.  I'm not sure how that happen.  ,1422052247,PHID-USER-u64h73gx226teqcym3r5,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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?",1421788770,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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).,1392911323,PHID-USER-qb5aoo443n6fezsozhv4,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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.",1392854320,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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).",1382567111,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+Page actions are wrong for VisualEditor,"Yes, good catch.  VE doesn't touch wgPostEdit, which we're using, at all.",1374191192,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+Page actions are wrong for VisualEditor,"**swalling** wrote:
+
+Would this impact page-save-success logging for VE?",1374191007,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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",1374171240,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_description,resolved
+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.",1726475742,PHID-USER-povcbbfr2b6v4te3anc7,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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.",1724605148,PHID-USER-povcbbfr2b6v4te3anc7,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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",1392851785,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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",1392846794,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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!",1392846139,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+Images specified with size foopxpx render at native size,"Yes, 'pxpx' is actually a ""feature"".  See bug 13500.
+
+Working on a fix...",1392845150,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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"".",1385033707,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+Images specified with size foopxpx render at native size,*** Bug 54371 has been marked as a duplicate of this bug. ***,1380930193,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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.",1376614949,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+Images specified with size foopxpx render at native size,*** Bug 51826 has been marked as a duplicate of this bug. ***,1374548109,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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",1374544369,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+Images specified with size foopxpx render at native size,*** Bug 51845 has been marked as a duplicate of this bug. ***,1374544099,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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,1374183991,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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",1374166740,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ufv5laxxz2gup5mbsoae,task_description,resolved
+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.",1429468007,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ufv5laxxz2gup5mbsoae,task_subcomment,NA
+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.",1392229924,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-ufv5laxxz2gup5mbsoae,task_subcomment,NA
+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.""",1374224206,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ufv5laxxz2gup5mbsoae,task_subcomment,NA
+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",1374162360,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-mc4ekk7vrriv5kycc2u2,task_description,resolved
+VisualEditor: Clarify beta explanation text,I think this is now better; closing.,1374257435,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mc4ekk7vrriv5kycc2u2,task_subcomment,NA
+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.",1374162561,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mc4ekk7vrriv5kycc2u2,task_subcomment,NA
+"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",1374158040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63tv3lkov2okxud2zyxo,task_description,resolved
+"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.,1375297757,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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",1375297187,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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",1375233664,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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",1375217200,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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",1375181969,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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' )?,1375098833,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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?",1375098410,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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,1375098204,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+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",1374109200,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gdwu5ick5nfagic7txm6,task_description,resolved
+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.,1380056460,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-gdwu5ick5nfagic7txm6,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"VisualEditor should support adding and editing the code tag (<code></code>).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374109140,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ktldutlvil3ngaxt2l2k,task_description,resolved
+VisualEditor: Support the <code> 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.",1374868236,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 76077 merged by jenkins-bot:
+Code annotation button
+
+https://gerrit.wikimedia.org/r/76077",1374867696,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 76074 merged by jenkins-bot:
+'CodeScript' => 'Code'
+
+https://gerrit.wikimedia.org/r/76074",1374867080,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 76077 had a related patch set uploaded by Esanders:
+Code annotation
+
+https://gerrit.wikimedia.org/r/76077",1374836628,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 76074 had a related patch set uploaded by Esanders:
+'CodeScript' => 'Code'
+
+https://gerrit.wikimedia.org/r/76074",1374836623,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"With the latest master, <code> 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.",1374255093,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 74563 merged by jenkins-bot:
+De-alienate <code>foo</code> blocks (code element)
+
+https://gerrit.wikimedia.org/r/74563",1374195080,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 74563 had a related patch set uploaded by Jforrester:
+De-alienate <code>foo</code> blocks (code element)
+
+https://gerrit.wikimedia.org/r/74563",1374192477,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+"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",1374104340,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kg6wsbien7yipr4dzrul,task_description,resolved
+"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",1675614246,PHID-USER-povcbbfr2b6v4te3anc7,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1538452334,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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).",1538452237,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1452116407,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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 ?,1452116319,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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)",1452057316,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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]]",1452034617,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1450298905,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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. ,1450297840,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.,1450294851,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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/",1450283149,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.
+",1450272250,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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),1450209312,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1449131751,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"Add more mw.hook events for wikipage: diff, categories etc.",Is this resolved? If not what's left to do?,1449100826,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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?",1449062407,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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]]",1448935559,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"Add more mw.hook events for wikipage: diff, categories etc.","Not mentioned yet, but IMHO makes sense, too: `#firstHeading`",1441362498,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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]]
+",1434906198,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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]]
+",1434320070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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 ?",1427484714,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1403380680,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"Add more mw.hook events for wikipage: diff, categories etc.",[Bumping TM as MediaWiki 1.22.0 tarball was released today.],1386383869,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1380208131,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1374111932,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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",1374087720,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_description,resolved
+"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.,1383478009,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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} $).",1383474047,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1377303810,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1377185317,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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.,1375218658,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1375217249,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1375207097,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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.).",1375201616,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1374797897,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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,1374342847,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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.",1374274354,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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.",1374176027,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1374111569,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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).",1374089581,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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. ***,1374088447,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+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}",1374077760,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-ca6crnotrmabx3jkz5wk,task_description,resolved
+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?",1423881296,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+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.",1423765790,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+VisualEditor: Node action icon (e.g. for template) appearing in wrong location,All test cases provided appear to be working now.,1405201255,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+VisualEditor: Node action icon (e.g. for template) appearing in wrong location,*** Bug 60652 has been marked as a duplicate of this bug. ***,1393455560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+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 .,1378477636,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+VisualEditor: Node action icon (e.g. for template) appearing in wrong location,"Created attachment 13252
+An icon far, far away...
+
+**Attached**: {F11878}",1378477567,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+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",1374077220,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_description,resolved
+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. ***,1395360091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_subcomment,NA
+VisualEditor: Abandoning VE load by navigating away before Parsoid load complete throws API error dialog,"\o/
+
+Thanks, Alex and Roan!",1391042211,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_subcomment,NA
+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",1391020997,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_subcomment,NA
+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",1390954780,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_subcomment,NA
+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",1374063480,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-iudy2zuexclkhlwqjbkn,task_description,resolved
+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",1384506400,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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!",1384484254,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1384300982,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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.",1383942790,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1383942688,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1383940906,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1374090597,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),Merged.,1374090551,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1374063814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+"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",1374049980,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-ss6harhqovaxcprykzge,task_description,resolved
+"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.,1374676726,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ss6harhqovaxcprykzge,task_subcomment,NA
+"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",1374676288,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss6harhqovaxcprykzge,task_subcomment,NA
+"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",1374674902,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss6harhqovaxcprykzge,task_subcomment,NA
+"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.,1374478890,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ss6harhqovaxcprykzge,task_subcomment,NA
+"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",1374026460,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7auhm5son76ryeyfeyid,task_description,resolved
+"VisualEditor: Beta notice incorrectly highlights ""Leave feedback"" link when hovering the notice",This was fixed in the toolbar re-write.,1383002871,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7auhm5son76ryeyfeyid,task_subcomment,NA
+"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).,1375825378,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7auhm5son76ryeyfeyid,task_subcomment,NA
+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 <nowiki/>}}) to protect the trailing space?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61049",1374013440,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-573oqdvpm2jqlbzsvzdg,task_description,resolved
+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.,1385385582,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-573oqdvpm2jqlbzsvzdg,task_subcomment,NA
+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",1374012600,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-unahzezsufzzdb4k4beo,task_description,resolved
+Generic first edit tour,"**swalling** wrote:
+
+Tours for 'firstedit' and 'firsteditve' are out in the wild. :)",1381904718,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+Generic first edit tour,This should also have browser tests.,1375132894,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+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.",1374013366,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+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.",1374012824,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+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",1374012729,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+Generic first edit tour,In progress at https://gerrit.wikimedia.org/r/#/c/64981/,1374012685,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+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",1373998440,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-g24bxdialbz5a5bcp4qb,task_description,resolved
+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",1395869325,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g24bxdialbz5a5bcp4qb,task_subcomment,NA
+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",1395866992,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g24bxdialbz5a5bcp4qb,task_subcomment,NA
+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",1373995560,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-kg4p7wmv7m2n5tdejrm4,task_description,resolved
+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.,1437781075,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-kg4p7wmv7m2n5tdejrm4,task_subcomment,NA
+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",1373995771,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-kg4p7wmv7m2n5tdejrm4,task_subcomment,NA
+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",1373980800,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3es7m4cbr63gg2w4l5or,task_description,resolved
+Template search results list should contain each template's descripton,Verified the fix in Betalabs,1429568922,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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]]",1429262905,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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]]
+",1428697842,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+Template search results list should contain each template's descripton,"Thanks for the explanation, I've now reported it as bug 51822.",1374511823,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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.",1374509714,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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?",1374508615,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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.",1374507636,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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).",1374502086,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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.",1374462543,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+"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",1373959860,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-t4nrv75pjo2r4cxn47di,task_description,resolved
+"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",1411169862,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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",1409939258,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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.",1400616978,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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?",1378952753,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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.",1375183561,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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. ***,1375183466,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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.",1374507813,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+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}",1373945100,PHID-USER-fuj45iylbizjg3yhehjt,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_description,open
+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",1603885261,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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?",1535697999,PHID-USER-hvywcttgalazbjxfl3tq,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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 :/",1535663319,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1535650055,PHID-USER-hvywcttgalazbjxfl3tq,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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]]",1535648306,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1535636345,PHID-USER-hvywcttgalazbjxfl3tq,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1483735245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1482964388,PHID-USER-jqjb54lbf7psat6shbcc,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1375214945,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1375206737,PHID-USER-fuj45iylbizjg3yhehjt,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+VisualEditor: Allow AbuseFilter rules to identify VE edits,"s/invisible to VE/invisible to AF/. I swear, I did proofread that. :)",1375206441,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+VisualEditor: Allow AbuseFilter rules to identify VE edits,"s/attempts/happens/, of course.",1375206175,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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 :)",1375206102,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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?",1375203722,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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).,1375203423,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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?",1375203347,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1375201847,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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).",1374075407,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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",1373946577,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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",1373924940,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-erfxy2a7265vjb4b2dj3,task_description,resolved
+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",1377205462,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-erfxy2a7265vjb4b2dj3,task_subcomment,NA
+VisualEditor: Page loading animated image is only LTR,Merged. Will go out with wmf15.,1377205420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-erfxy2a7265vjb4b2dj3,task_subcomment,NA
+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",1377204612,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-erfxy2a7265vjb4b2dj3,task_subcomment,NA
+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",1373909880,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-mo5dvj5do74gbwyx6vrs,task_description,resolved
+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",1383945120,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mo5dvj5do74gbwyx6vrs,task_subcomment,NA
+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",1382632926,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mo5dvj5do74gbwyx6vrs,task_subcomment,NA
+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).""",1375969318,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-mo5dvj5do74gbwyx6vrs,task_subcomment,NA
+"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}",1373906820,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-643scf5lq5v72slluprm,task_description,resolved
+"VisualEditor: Toolbar icons - ""reference"" (bookmark) alternatives or improvements",I'm going to provisionally deem this solved with the new icon.,1401472548,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-643scf5lq5v72slluprm,task_subcomment,NA
+"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.",1373981836,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-643scf5lq5v72slluprm,task_subcomment,NA
+"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)",1373907050,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-643scf5lq5v72slluprm,task_subcomment,NA
+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",1373852760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_description,resolved
+VisualEditor: Improve how we suppress reference warnings in template rendering,"Done and merged, now that wmf12 is deployed everywhere.",1375327521,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+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",1375326645,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+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",1374193845,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+VisualEditor: Improve how we suppress reference warnings in template rendering,https://gerrit.wikimedia.org/r/#/c/73614/,1373886910,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+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",1373852814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+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",1373850240,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-6ana44vgeezadw6ore4y,task_description,resolved
+VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems),This flyout is now much wider.,1393633638,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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. ***,1374162111,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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.",1374079435,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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.",1374030006,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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}",1373886191,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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!",1373883699,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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",1373799300,PHID-USER-7clmfrlb7fwuko4jdjbs,PHID-TASK-yv3kce72452r37igamnp,task_description,resolved
+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],1440343623,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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.,1386877406,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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",1374265649,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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",1374265553,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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.",1373841014,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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'.",1373834454,PHID-USER-7clmfrlb7fwuko4jdjbs,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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.",1373812879,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+VisualEditor: Templated calls to <references /> (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",1373770740,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-a6e5anlp2g7eyftsen6n,task_description,duplicate
+VisualEditor: Templated calls to <references /> (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 <references /> call, and neither does Parsoid unless it re-parses it.
+
+Consequently, we are expanding the syntax for <references /> to make {{reflist}} unnecessary. WONTFIXing this bug.",1385383497,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a6e5anlp2g7eyftsen6n,task_subcomment,NA
+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",1373734200,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-6vanypiuvvogqhl2yqvj,task_description,resolved
+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 ***",1374619928,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6vanypiuvvogqhl2yqvj,task_subcomment,NA
+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.",1373930449,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-6vanypiuvvogqhl2yqvj,task_subcomment,NA
+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?",1373883480,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6vanypiuvvogqhl2yqvj,task_subcomment,NA
+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",1373722680,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-c2zo7myzzju4zjk7el5z,task_description,resolved
+References inside templates don't appear in the reference list in VisualEditor,"This seems to be fixed, although T52474 (which is similar) remains open.",1434419761,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,*** Bug 69066 has been marked as a duplicate of this bug. ***,1407061246,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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.",1392925788,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,Gah.,1380067199,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,This has started happening again. See [[OpenOffice.Org]] and [[Bristol]] for examples.,1379790227,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,"Ok thanks for the quick reply, now reported as bug 52427",1375398248,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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.",1375397689,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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?,1375397290,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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).,1375383745,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,"Sorry, that second possibly related bug should be bug 50749",1373722788,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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",1373722440,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-deqihdmtktthecojw62o,task_description,resolved
+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.,1377829266,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-deqihdmtktthecojw62o,task_subcomment,NA
+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
+
+",1373683500,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_description,declined
+VisualEditor: Samsung browser fails the blacklist,See {T367735},1718626061,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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!",1437858058,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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.",1437831971,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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!)",1437781263,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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!)",1437781197,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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.,1373923134,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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.",1373916976,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+VisualEditor: Samsung browser fails the blacklist,Mobile Safari isnt just iOS.  It is the *default* web browser on many Android phones.,1373764759,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"For VisualEditor, we are continuously-bitten by <references /> 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 <references /> tag.
+
+Points of agreement include:
+* The main requirements are for <references /> 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 <references /> 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",1373662620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_description,resolved
+Support editing <references /> 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]]
+",1505840824,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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]]
+",1505835365,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references> 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 <references/> 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.",1499785680,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,">For VisualEditor, we are continuously-bitten by <references /> 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 <references /> tag.
+
+>Reference incidences (<ref>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 <references /> 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.",1446974679,PHID-USER-o7sy7j32bv4qerbqa3x5,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.,1435699557,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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).,1425310977,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,@thiemowmde mentions T33597,1416834442,PHID-USER-tqvzwasywo4a7bnuwuz4,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.,1416910461,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.,1416910421,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.,1412760097,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 `<references>` 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.",1417405037,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 `<references>` 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.",1417405028,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references> 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.",1412722649,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"See also:
+Bug 31597 - generate class for references list according to the number of refs",1411551743,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+Reason:
+ok done
+
+https://gerrit.wikimedia.org/r/123105",1409791989,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,I picked up the Cite & VE parts of this again.,1409791787,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+Reason:
+Restoring so I can do a rebase to get the VE patch working
+
+https://gerrit.wikimedia.org/r/123105",1409791573,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+https://gerrit.wikimedia.org/r/123093",1409782437,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"Change 120962 restored by Alex Monk:
+Support setting column-width and list-style in <references /> tag
+
+Reason:
+Going to use classes.
+
+https://gerrit.wikimedia.org/r/120962",1409782408,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,Bug 22265 - Allow references to be listed with letters,1405984158,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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"".",1405787640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+Reason:
+Abandoning all related patch sets
+
+https://gerrit.wikimedia.org/r/123093",1405780950,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"Change 120962 abandoned by Alex Monk:
+Support setting column-width and list-style in <references /> tag
+
+https://gerrit.wikimedia.org/r/120962",1405780903,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+https://gerrit.wikimedia.org/r/123105",1405780885,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,See https://gerrit.wikimedia.org/r/#/c/120962/ for more discussion on this.,1401486377,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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…",1401482644,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.",1396389434,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+https://gerrit.wikimedia.org/r/123105",1396388659,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+https://gerrit.wikimedia.org/r/123093",1396387228,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"What? We don't do LATER, and haven't for over a year.",1395858396,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"IMO this should be a WONTFIX or LATER, and instead bug 6019 should be fixed.",1395800703,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references /> tag
+
+https://gerrit.wikimedia.org/r/120962",1395789394,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references /> 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 <references /> 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 <references /> OL – the ""references"" class can be over-ridden locally by wikis if they want to change it further.
+
+
+Is this what others think?",1394727173,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,Can someone sum up exactly what has been agreed to do here?,1394128243,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"(In reply to comment #8)
+> The references tag should support html attributes, than you can write
+> <references class=""***"" /> 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.",1383136097,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.",1383132465,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.",1380273005,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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).
+
+</brain-dump>",1380272763,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,What about the {{reflist}} variants on en.wiki such as {{notelist}}?,1377709374,PHID-USER-zqde3skdzpqiwny4dxt4,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"The plwp infobox <references/> is here:
+https://pl.wikipedia.org/wiki/Szablon:Infobox_uwagi_dodaj",1373764541,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 (<references />s) rather than having them
+> need to invent and use the template.
+> 
+> Reference incidences (<ref>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 <references /> so people won't (often?) have to embed <references /> in templates.  However, I think db's point is that there are other reasons (besides {{reflist}}) that <references /> 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.",1373762484,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 (<h2>, <h3>, ...):
+https://pt.wikipedia.org/wiki/Template:Referências",1373746711,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"The references tag should support html attributes, than you can write <references class=""***"" /> 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.",1373744313,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"(In reply to comment #5)
+> You will become also problems with <ref> 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 (<references />s) rather than having them need to invent and use the template.
+
+Reference incidences (<ref>s) inside templates are an entirely distinct problem for VisualEditor to worry about, and this isn't about that. :-)",1373724517,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"(In reply to comment #5)
+> You will become also problems with <ref> 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 <ref>s *and* <references group=.../>, for example pl.wp infoboxes for football players and some other sportsmen; an example can be seen on [[pl:Carles Puyol]].",1373709172,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"You will become also problems with <ref> 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.",1373700015,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.",1373665020,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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",1373664227,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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"".",1373663834,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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).",1373663426,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+VisualEditor: Remove obsolete retry token logic in mw.Target,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373654940,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-glljlygxsse6ts5nyo5g,task_description,resolved
+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",1376556010,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-glljlygxsse6ts5nyo5g,task_subcomment,NA
+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",1375231529,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-glljlygxsse6ts5nyo5g,task_subcomment,NA
+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)",1373655053,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-glljlygxsse6ts5nyo5g,task_subcomment,NA
+VisualEditor: Remove obsolete retry token logic in mw.Target,"onLoad no longer requires or even considers a token, so this is now obsolete.",1373655001,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-glljlygxsse6ts5nyo5g,task_subcomment,NA
+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",1373650320,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_description,resolved
+Install Notifications (Echo) on the Polish Wikipedia,"I'm pretty sure this can be closed now :) Thanks, Fabrice!",1377773546,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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)",1376107997,PHID-USER-dbudsaorcqut7sg3vvbi,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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.",1376107269,PHID-USER-dbudsaorcqut7sg3vvbi,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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.",1375576048,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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!",1375375348,PHID-USER-dbudsaorcqut7sg3vvbi,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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.",1375362558,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+Install Notifications (Echo) on the Polish Wikipedia,And thanks for responding :) I'll forward this information to the community.,1374710826,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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.",1374710558,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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!",1374710265,PHID-USER-dbudsaorcqut7sg3vvbi,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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""?",1374361726,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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!",1373918592,PHID-USER-dbudsaorcqut7sg3vvbi,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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",1373636880,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-znebtf73mavsnt4zkjtb,task_description,declined
+VisualEditor: Add the capacity for help pages in dialogs,"Instead of help /pages/ we've decided to go with help /popups/, per bug 51798.",1403824508,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-znebtf73mavsnt4zkjtb,task_subcomment,NA
+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",1373603700,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_description,resolved
+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.",1376526837,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1375981140,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1375978000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.,1375306275,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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/,1374985971,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.,1374985901,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1374928594,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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. ***,1374701823,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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. ***,1374677927,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1374529506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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. ***,1374329698,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+Implement way to round-trip tables with fosterable content that migrates out of the table,This looks very similar to bug 50754.,1374306109,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+Implement way to round-trip tables with fosterable content that migrates out of the table,"From IRC:
+[14:44] <gwicke> 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] <gwicke> yeah, I wonder what he is up to
+[14:45] <subbu> in that example, what do we do with the information at all .. itis not helpful since the output still looks corrupt.
+[14:45] <gwicke> 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] <gwicke> we could strip the fostered content from the DOM
+[14:46] <subbu> is it the right thing to do in general?
+[14:46] <gwicke> and rig selser so that it restores it unless the content is touched 
+[14:47] <gwicke> or we can keep it in the DOM, but mark it so that selser does not serialize it
+[14:47] <gwicke> ie, a zero-length dsr
+[14:48] <subbu> yes, the rig-selser bit is missing right now.
+[14:48] <gwicke> subbu: detecting foster-parented content and then excluding it from dsr calculations might already be pretty effective
+[14:49] <gwicke> I guess the gaps in dsr would be spanned by the dsr algorithm
+[14:49] <subbu> yes, that should work.
+[14:49] <gwicke> (the holes where content disappeared)
+[14:50] <subbu> 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] <gwicke> subbu: I'd vote for data-parsoid
+[14:50] <subbu> data-parsoid is fine for internal use.
+[14:50] <gwicke> if the user edits the fostered content, we serialize it
+[14:50] <gwicke> i.e., do the dirty diff then
+[14:51] <subbu> 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] <gwicke> when something adjacent to the former location is edited, we dirty-diff it there
+[14:51] <gwicke> subbu: IMO we should abstract such issues
+[14:52] <gwicke> bot authors would not want to deal with it either
+[14:52] <gwicke> and the DOM should reflect the rendered semantics 
+[14:53] <subbu> dom should reflect rendered semantics for sure.",1374271613,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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<ref name=""futon"" />
+ |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)
+
+... <td id=""pc{{{ProdCode}}}"">{{{ProdCode}}}</td> ...
+
+See what that will do with the parameter passed in from the page.  Here is the expanded source that Parsoid sees:
+
+... <td id=""pc101<ref name=""futon"" />"">101<ref name=""futon"" /></td> ...
+
+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.",1374266416,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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).",1374190969,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.,1374185200,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.",1374184823,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.",1374101827,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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,1374089129,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1374088970,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.",1373606553,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.",1373604215,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1373579640,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_description,open
+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",1650404810,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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  `<div style=""top: left: …""></div>` to  `<svg><rect x= y= …></svg>` 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 `<svg>` tag covering the whole page, but made unclickable with `pointer-events: none`, with `<rect>` or something for individual highlights.
+
+I think we should stick to smaller `<svg>` tags covering just the focusable node (like the current `<div>` 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 `<svg>` 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.)",1526820747,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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]]",1526763872,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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",1462887892,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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.",1416846887,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+Draw VisualEditor's non-CE block highlights using SVG polygons,This is not high priority,1416846552,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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.,1408985768,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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/",1373580320,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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",1373556900,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-f6islnvgxyd3d63sxooo,task_description,resolved
+Re-enable user preference to disable VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 50929 ***",1373557556,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-f6islnvgxyd3d63sxooo,task_subcomment,NA
+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.",1373557227,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-f6islnvgxyd3d63sxooo,task_subcomment,NA
+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",1373507520,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-l5pjiw32hngnewgrmmmy,task_description,declined
+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.",1373610519,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-l5pjiw32hngnewgrmmmy,task_subcomment,NA
+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),1373558667,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-l5pjiw32hngnewgrmmmy,task_subcomment,NA
+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 <yourApiURL>
+
+We should probably print this information when the config request fails. Repurposing this bug for that.",1373556483,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-l5pjiw32hngnewgrmmmy,task_subcomment,NA
+VisualEditor: Newline migration issue,"As discovered in bug 50120, we need to find out what this is and fix it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373503560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ki7bzkbyld2qdm75nyap,task_description,open
+VisualEditor: Newline migration issue,"@Jdforrester-WMF, can we close this? T52120 has been resolved.",1440107033,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ki7bzkbyld2qdm75nyap,task_subcomment,NA
+VisualEditor: Newline migration issue,"@Jdforrester-WMF, can we close this? T52120 has been resolved.",1437781492,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-ki7bzkbyld2qdm75nyap,task_subcomment,NA
+"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",1373500740,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-nphxjkvvi4eszdxix7bq,task_description,open
+"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 <references> tag making {{reflist}} redundant?
+
+https://phabricator.wikimedia.org/maniphest/query/7.xI5WLmYTc1/#R pffers some tasks about //specific// (not: //all//) functionality...",1436532828,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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 <references> tag making {{reflist}} redundant?,1436461261,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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.",1405353588,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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. ***,1405107160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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.,1374270748,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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).,1373774352,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+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",1373497500,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_description,resolved
+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",1645468531,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+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",1644991783,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+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.",1410824403,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+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).",1410216270,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+VisualEditor: Nicer removal of Cite.php's class=error,Hello?,1410125027,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+VisualEditor: Nicer removal of Cite.php's class=error,So what is this about? There's a lot of missing context here.,1406238141,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+"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",1373485620,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-7brx7poui3lgaqmgzlvg,task_description,resolved
+"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.",1393632765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7brx7poui3lgaqmgzlvg,task_subcomment,NA
+"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.",1373855846,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7brx7poui3lgaqmgzlvg,task_subcomment,NA
+"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",1373473020,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-xxykpaxkkgrcn363ntny,task_description,declined
+"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor",I have.,1400626382,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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?",1400188965,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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.",1400188662,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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?",1400187131,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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",1397752290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor",The user is asking to escape VE entirely.,1373474404,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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?",1373474231,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+[[./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",1373422620,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-l4k7rc3z5agm24u46fhj,task_description,resolved
+[[./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",1397109465,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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",1397109230,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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",1396645916,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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.",1395952117,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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}}]]",1395951625,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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",1394483874,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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.",1377447763,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+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",1373398440,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_description,resolved
+VisualEditor: Link editor requires ENTER for input,*** Bug 51177 has been marked as a duplicate of this bug. ***,1377834865,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+VisualEditor: Link editor requires ENTER for input,This is now merged and will be deployed later.,1375304913,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+VisualEditor: Link editor requires ENTER for input,"Change 76839 merged by jenkins-bot:
+Link inspector bug fixes
+
+https://gerrit.wikimedia.org/r/76839",1375304088,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+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",1375222014,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+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.",1374530988,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+VisualEditor: Link editor requires ENTER for input,Is this the same thing as bug 48789?,1374519470,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+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]",1373905446,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+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.",1373757918,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+"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",1373394900,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-4phtoxaof6zm4vyraue4,task_description,open
+"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.,1402590995,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4phtoxaof6zm4vyraue4,task_subcomment,NA
+"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"".",1373428513,PHID-USER-fuj45iylbizjg3yhehjt,PHID-TASK-4phtoxaof6zm4vyraue4,task_subcomment,NA
+"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",1373390040,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-dhlp7wsucyat5r5hizgn,task_description,resolved
+"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]]",1430268574,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]
+",1430236097,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"TemplateData: Provide property ""example"" for template parameters",Checked in betalabs - 'Example (en)' was added to Template documentation editor.,1429042468,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]",1428684541,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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.",1426695980,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]",1425936869,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]
+",1425512054,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]
+",1425501224,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"TemplateData: Provide property ""example"" for template parameters",Any progress?,1393353167,PHID-USER-6majuboi566q3ozbh27r,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+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",1373356200,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-hqedrd262jmefrbeu2zs,task_description,resolved
+VisualEditor: OpenSearch results aren't perfect for checking for page existence,"FIXED by dint of bug 70958 being fixed. Thanks, Timo!",1412977342,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for checking for page existence,*** Bug 54361 has been marked as a duplicate of this bug. ***,1410985568,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+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.",1406658829,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+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.",1406658645,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for checking for page existence,*** Bug 65927 has been marked as a duplicate of this bug. ***,1402016305,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for checking for page existence,*** Bug 52596 has been marked as a duplicate of this bug. ***,1377808859,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+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,1377802895,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+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",1373355240,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-jbywhdnkgf572tjejemv,task_description,resolved
+VisualEditor: Make defaultsort input field wider,Thanks!,1395083036,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+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",1395082709,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+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",1395082320,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+VisualEditor: Make defaultsort input field wider,"Created attachment 14834
+Other dialogs affected by change
+
+**Attached**: {F11659}",1395009220,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+VisualEditor: Make defaultsort input field wider,"Created attachment 14833
+Screenshot of 100% width in default sort field
+
+**Attached**: {F11658}",1395008155,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+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}",1395008084,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+"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",1373336940,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-4thzrxadngq5mhfphtu2,task_description,resolved
+"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,1395350521,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4thzrxadngq5mhfphtu2,task_subcomment,NA
+"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,1394844008,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4thzrxadngq5mhfphtu2,task_subcomment,NA
+"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",1394666490,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4thzrxadngq5mhfphtu2,task_subcomment,NA
+"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",1394412858,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4thzrxadngq5mhfphtu2,task_subcomment,NA
+"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",1373335140,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqk4thl22c326oiwdmgc,task_description,open
+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",1373333700,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_description,resolved
+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",1395274513,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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",1387582091,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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",1387581872,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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",1383139276,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,WIP: https://gerrit.wikimedia.org/r/#/c/84461/,1379374358,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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"".",1378832292,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,*** Bug 51176 has been marked as a duplicate of this bug. ***,1374854828,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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.",1374854811,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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",1373332680,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_description,resolved
+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.,1429467871,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_subcomment,NA
+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.",1377896960,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_subcomment,NA
+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.",1374076751,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_subcomment,NA
+VisualEditor: Backspace from (or deleteing down) into a DL breaks badly,Also note that undo doesn't seem to work on this deletion event.,1373354435,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_subcomment,NA
+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 <sup> (like [10]) and as such isn'y styled correctly (text is too big).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11600}",1373316780,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vqebaloi6mz6p43fpars,task_description,resolved
+VisualEditor: Display references rendered by {{#tag:ref}} in superscript,Fixed and will go out later today.,1373993621,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+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",1373992966,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+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",1373991605,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"(In reply to comment #2)
+> Parsoid incorrectly renders references as <span>s. The ones directly in the
+> main documented are rendered as <sup>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 <span class=""reference""> render as a superscript, or munge it in some other way. Though ideally I'd like us to convince Parsoid to render references as <sup>s the way the PHP parser does.",1373850925,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"Parsoid incorrectly renders references as <span>s. The ones directly in the main documented are rendered as <sup>s by VE, but we don't control the ones in templates and other generated content (and #tag is a ParserFunction).",1373850785,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+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",1373850409,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+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",1373310540,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-cc3yxgxiksoojspiwoxm,task_description,resolved
+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).",1437782973,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-cc3yxgxiksoojspiwoxm,task_subcomment,NA
+VisualEditor: Provide some way of opening external links within templates,*** Bug 66549 has been marked as a duplicate of this bug. ***,1402688065,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cc3yxgxiksoojspiwoxm,task_subcomment,NA
+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, <references />).",1395856047,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-cc3yxgxiksoojspiwoxm,task_subcomment,NA
+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",1373301660,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_description,resolved
+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",1400108562,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1400103345,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1400102698,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+VisualEditor: Clearer message when cancelling out of active edit,"Change 132113 merged by jenkins-bot:
+Add confirmation dialog
+
+https://gerrit.wikimedia.org/r/132113",1400087288,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1399588039,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1399587267,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1399497998,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1398793970,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1375976639,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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.",1374267990,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+VisualEditor: Clearer message when cancelling out of active edit,*** Bug 51655 has been marked as a duplicate of this bug. ***,1374267909,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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"".)",1374208197,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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?",1373519895,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1373299560,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_description,resolved
+VisualEditor: Handle transclusions within a table better,The table will still be broken after an edit as Parsoid doesn't run with context yet.,1404212487,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_subcomment,NA
+VisualEditor: Handle transclusions within a table better,Fixed by gerrit 140439.,1404172723,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_subcomment,NA
+VisualEditor: Handle transclusions within a table better,This might be related to VisualEditor bug 50607 and foster-parenting.,1377030328,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_subcomment,NA
+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.",1374457884,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_subcomment,NA
+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",1373294940,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-bmll3l66rbyvzumaunet,task_description,resolved
+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.,1552091050,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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.",1373340093,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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}",1373339872,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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)?",1373338512,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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}",1373338199,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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.",1373337830,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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.",1373335844,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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!",1373332126,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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",1373295030,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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",1373276400,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_description,resolved
+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)",1374837483,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374835048,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,So you will reopen this bug as soon as VE gets stable? Promised?,1374833237,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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. :-)",1374832672,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374832506,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374831425,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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!",1374830485,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,Fixed in VisualEditor extension itself with https://gerrit.wikimedia.org/r/#/c/75541/,1374826648,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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",1374826585,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374795200,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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?",1374790590,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374520048,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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",1374519857,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374516858,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374516605,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374512041,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.)",1374511815,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374511268,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374510712,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,That would reopen bug 48666 Make VisualEditor a hidden preference.,1374499371,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,*** Bug 51389 has been marked as a duplicate of this bug. ***,1373926494,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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",1373712372,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373576253,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,"Great, thank you.
+
+I'm marking this bug with the ""easy"" keyword accordingly.",1373566995,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373561265,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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?",1373559939,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373559883,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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!",1373557859,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373557628,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,*** Bug 51179 has been marked as a duplicate of this bug. ***,1373557556,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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}",1373534882,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,"This should be in the obvious place, in the editing tab of user preferences, not a gadget.",1373454425,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373357086,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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",1373280320,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+"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",1373273160,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_description,resolved
+"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.",1373328454,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_subcomment,NA
+"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",1373325416,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_subcomment,NA
+"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",1373303244,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_subcomment,NA
+"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?",1373301852,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_subcomment,NA
+"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",1373241780,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-77heb24pfspzzrzifyb6,task_description,open
+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",1373235720,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-e3ikdtgrrubm3iohiewm,task_description,resolved
+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",1393088190,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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",1389062756,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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",1388994313,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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",1388991749,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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.",1388943484,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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.",1388941911,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,Was this fixed by the fix for bug 53436?,1388919466,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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",1373231700,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-opmsqzsgromr47nfku4r,task_description,resolved
+VisualEditor: Label the edit summary box as such,"This was done, ages ago.",1383280539,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-opmsqzsgromr47nfku4r,task_subcomment,NA
+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",1373231160,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-delfcnij7a43xvmu5qyt,task_description,resolved
+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.,1377809024,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+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).",1376076347,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+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.",1376073277,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+VisualEditor: Link dialog lies about existence of page due to case insensitive matching,*** Bug 52251 has been marked as a duplicate of this bug. ***,1376073139,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+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",1376073087,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+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.",1373356246,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+VisualEditor: Link dialog lies about existence of page due to case insensitive matching,"Other examples: [[A]], [[B]], [[To]], [[Hi]]",1373299773,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+"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",1373228820,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_description,resolved
+"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",1392846136,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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",1392396699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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",1392342481,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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",1391110776,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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).",1391108156,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.",1378762522,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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. ***,1378223819,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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. ***,1377814470,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.",1374687986,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.",1374630651,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.,1374417351,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.",1373480495,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.,1373230813,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+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",1373224920,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-yhjup2iu6lr4ysgs743l,task_description,open
+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.",1703172513,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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.,1702660838,PHID-USER-tuy2dac6pfhknbtqmqgh,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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..)
+",1702544238,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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 <ref> 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 <ref> 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",1619846278,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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.",1572174420,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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"". ",1559320456,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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}",1559307018,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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. ",1543310095,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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.",1449854974,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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?",1402685083,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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.",1402684730,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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",1373224800,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-fgcx6r4cq4f3sp3crtxx,task_description,resolved
+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.,1373981883,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fgcx6r4cq4f3sp3crtxx,task_subcomment,NA
+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",1373934858,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fgcx6r4cq4f3sp3crtxx,task_subcomment,NA
+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",1373416527,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fgcx6r4cq4f3sp3crtxx,task_subcomment,NA
+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",1373199360,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_description,resolved
+VisualEditor: Long editnotices are truncated with no way to scroll,This was fixed last week.,1397067646,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+VisualEditor: Long editnotices are truncated with no way to scroll,*** Bug 62408 has been marked as a duplicate of this bug. ***,1397067550,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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).",1384895522,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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",1382972121,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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.",1377829536,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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.""",1377446787,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+VisualEditor: Long editnotices are truncated with no way to scroll,*** Bug 52602 has been marked as a duplicate of this bug. ***,1377446690,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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",1373160600,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-hkpifvkdgtnwuojek3uj,task_description,resolved
+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",1392349574,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+VisualEditor: Remove the disablement of VisualEditor for redirect pages,*** Bug 60425 has been marked as a duplicate of this bug. ***,1390695336,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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",1384373833,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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",1384313403,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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.",1375531656,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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 :)",1375522019,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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.",1373160972,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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?",1373160777,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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",1373160480,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_description,resolved
+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",1400888338,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_subcomment,NA
+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",1400742360,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_subcomment,NA
+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.",1373566655,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_subcomment,NA
+VisualEditor: Editor not triggered on system redirects,*** Bug 51178 has been marked as a duplicate of this bug. ***,1373566618,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_subcomment,NA
+"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",1373152020,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_description,declined
+"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"".",1434589709,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+"VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist",re-opening since I think it works pretty well.,1434060016,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+"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.",1377033706,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+"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.",1373319033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+"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.",1373308626,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+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",1373150220,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5kevizlj2r7opk2fmypx,task_description,resolved
+VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,Done and will be deployed tomorrow.,1374634478,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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",1374620537,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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.",1374606424,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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. ***,1374605494,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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",1374187124,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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. ***,1373932279,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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.",1373185656,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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?",1373183092,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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. ***,1373155212,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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?",1373155090,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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 <h1> 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",1373144520,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_description,resolved
+mediawiki.notification: Notification area should remain visible when scrolled down,*** Bug 48689 has been marked as a duplicate of this bug. ***,1381254374,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374689170,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+mediawiki.notification: Notification area should remain visible when scrolled down,"@se4598, thanks for the report, I7444bf55 should fix this. Sorry!",1374689138,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374687551,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374679819,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374679699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374678751,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374678540,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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.",1374636514,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374636426,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+mediawiki.notification: Notification area should remain visible when scrolled down,*** Bug 51785 has been marked as a duplicate of this bug. ***,1374449520,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1373984219,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1373982414,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+mediawiki.notification: Notification area should remain visible when scrolled down,*** Bug 51432 has been marked as a duplicate of this bug. ***,1373982177,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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 = $('<div>').appendTo($content)
+    $n = $('<div>').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 )",1373281154,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+mediawiki.notification: Notification area should remain visible when scrolled down,"Heh, I though they behave in this way. Seems like an obvious enhancement.",1373147615,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1373147590,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+"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",1373067480,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-jza5e4mrwocbbyclpgux,task_description,open
+"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.",1373067634,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-jza5e4mrwocbbyclpgux,task_subcomment,NA
+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",1373062140,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-qx22rnw4roeugdfib5hc,task_description,resolved
+VisualEditor: Clean up 'cache': 'false',Done in Roan's clean-up of API usage.,1393640938,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qx22rnw4roeugdfib5hc,task_subcomment,NA
+"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}",1373006760,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-x7y27baxwalxutuxi24u,task_description,resolved
+"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.",1642379774,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-x7y27baxwalxutuxi24u,task_subcomment,NA
+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",1373006100,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_description,resolved
+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]]",1431794211,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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]]
+",1431655294,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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 ",1429126077,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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.",1429123960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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?",1429122908,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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.",1425420366,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,Marking as Resolved.,1421801167,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,"This task is open but has two ""verified-in-phaseX"" projects associated. Could someone clarify?",1421800777,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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.",1419299453,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,"[15:09] <gwicke> 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] <gwicke> while still matching CSS etc so that it renders as expected
+[15:09] <RoanKattouw> Right
+[15:09] <RoanKattouw> I guess I could hack tolerance for that into VE's type system
+[15:10] <RoanKattouw> I think it's kind of an abuse of a type but I see why you'd do it
+[15:10] <RoanKattouw> You want to have a single unified thing to easily identify error nodes
+[15:11] <gwicke> yeah; there is a chance that querySelectorAll also supports typeof
+[15:12] <gwicke> [typeof~=mw:Error]
+[15:12] <RoanKattouw> Exactl
+[15:12] <RoanKattouw> y
+[15:12] <gwicke> which is more efficient than [data-mw] and then decoding each & look for errors
+[15:14] <gwicke> RoanKattouw, I think you are already giving mw:Placeholder a high precedence
+[15:14] <gwicke> could mw:Error have a similarly high precedence?
+[15:15] <RoanKattouw> gwicke: No, mw:Placeholder is unrecognized
+[15:15] <RoanKattouw> Any unrecognized type matching /^mw:/ triggers immediate alienation
+[15:15] <RoanKattouw> For mw:Error we'd need the reverse
+[15:15] <gwicke> yeah, but aren't you handling typeof=""mw:Placeholder mw:Image"" already?
+[15:15] <RoanKattouw> 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] <gwicke> (by letting the placeholder win)
+[15:16] <RoanKattouw> No, the placeholder doesn't win
+[15:16] <gwicke> ah, I see
+[15:16] <RoanKattouw> The rules for ""special"" type prefixes (for ve-mw, that's only /^mw:/ ) are as follows:
+[15:16] <gwicke> that's a problem
+[15:16] <RoanKattouw> A class matches if:
+[15:16] <RoanKattouw> * It specifies some type that's present on the element
+[15:17] <RoanKattouw> * It specifies ALL mw: types that are present on the element
+[15:17] <RoanKattouw> (i.e. both of those have to be true)
+[15:17] <RoanKattouw> Additionally, we don't currently have a facility for saying ""I recognize either mw:Foo or mw:Foo+mw:Error""
+[15:17] <RoanKattouw> You can only do AND, not OR
+[15:17] <gwicke> RoanKattouw: I see, that makes mw:Error harder to handle for you
+[15:18] <RoanKattouw> I mean, I can do it
+[15:18] <RoanKattouw> By introducing the concept of ignored types or whatever I want to call it
+[15:18] <RoanKattouw> I could even make mw:Placeholder one
+[15:18] <RoanKattouw> Then placeholderized images could be handled
+[15:18] <RoanKattouw> Handlers for node types still have the option to trigger alienation by returning null
+[15:18] <gwicke> we already have mw:Image and mw:ExpandedAttrs
+[15:19] <gwicke> and all permutations of images of course
+[15:19] <RoanKattouw> 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] <RoanKattouw> Right, mw:ExpandedAttrs is another good candidate for an ignored typer
+[15:19] <RoanKattouw> It can apply to anything
+[15:19] <RoanKattouw> And sometimes we need to alienate and sometimes we don't
+[15:19] <RoanKattouw> Hmm, maybe the jargon should be ""universal type""
+[15:19] <gwicke> yup, so the general ability to match that kind of thing is needed in any case
+[15:20] <RoanKattouw> Yeah
+[15:20] <RoanKattouw> I will file a bug about this",1393456951,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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?",1393455910,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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?,1393439521,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,*** Bug 52186 has been marked as a duplicate of this bug. ***,1389632313,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,"So currently redlink images are returned as <meta typeof=""mw:Placeholder"">. 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.",1389631702,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,*** Bug 51968 has been marked as a duplicate of this bug. ***,1377623981,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,"Yes, this is a bit of a mess.",1373155845,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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",1372987020,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-2liv3ois3nnjarqe73d5,task_description,resolved
+VisualEditor: Browser blacklist issues (tracking),Replaced by #VisualEditor-Initialisation.,1422424851,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2liv3ois3nnjarqe73d5,task_subcomment,NA
+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.",1415031694,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2liv3ois3nnjarqe73d5,task_subcomment,NA
+VisualEditor: Browser blacklist issues (tracking),"I'm going to add MSIE to the list, given that we really should get it working again.",1373041481,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2liv3ois3nnjarqe73d5,task_subcomment,NA
+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",1372986900,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-zzmgok2p56thwvxkpnrv,task_description,resolved
+VisualEditor: Firefox 11 and 12 also need to be blacklisted,This is now merged.,1373048811,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373048537,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373048483,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373048462,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373048390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373041365,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+"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",1372980600,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-snnn2o47ucaywt5ufim7,task_description,resolved
+"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.",1410034029,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-snnn2o47ucaywt5ufim7,task_subcomment,NA
+"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.",1375182193,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-snnn2o47ucaywt5ufim7,task_subcomment,NA
+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",1372978080,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-smutmksr4slgk2o54suc,task_description,resolved
+VisualEditor: Add Amazon Silk browser to blacklist,"Change 72108 merged by jenkins-bot:
+Blacklist Amazon Silk
+
+https://gerrit.wikimedia.org/r/72108",1391811948,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1391810830,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1391459065,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1391392671,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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...",1391382294,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1373041368,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1373039832,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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. :-)",1373036364,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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*",1373036277,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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.",1373033179,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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 <math> 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",1372977300,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-ubeo6o33vz5bavixyf3q,task_description,resolved
+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. :-)",1412608037,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ubeo6o33vz5bavixyf3q,task_subcomment,NA
+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 ***",1412589972,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ubeo6o33vz5bavixyf3q,task_subcomment,NA
+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",1372926900,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-joexgd3r5nmcwbofqrlr,task_description,resolved
+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.",1399419769,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-joexgd3r5nmcwbofqrlr,task_subcomment,NA
+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.",1399419638,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-joexgd3r5nmcwbofqrlr,task_subcomment,NA
+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)",1381626499,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-joexgd3r5nmcwbofqrlr,task_subcomment,NA
+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.",1373950590,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-joexgd3r5nmcwbofqrlr,task_subcomment,NA
+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",1372923480,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-ftkzim4nufm7ey6vnaq5,task_description,resolved
+VisualEditor: Generated blocks that create images directly aren't converted to use MW's skin,"I believe that this is now long-fixed, yes.",1660956979,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ftkzim4nufm7ey6vnaq5,task_subcomment,NA
+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?",1660948019,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ftkzim4nufm7ey6vnaq5,task_subcomment,NA
+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 <figure> rather than <div class=""thumb""> 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?",1373158925,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ftkzim4nufm7ey6vnaq5,task_subcomment,NA
+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)",1372894740,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2p76xxlh44jpmzqza6ge,task_description,open
+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.",1430333636,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2p76xxlh44jpmzqza6ge,task_subcomment,NA
+Separate ve.init and ve.platform,I think @Krinkle should rewrite it.,1430159784,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2p76xxlh44jpmzqza6ge,task_subcomment,NA
+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.",1430159393,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-2p76xxlh44jpmzqza6ge,task_subcomment,NA
+"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",1372883940,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-ibes2uplyibrsadgodld,task_description,resolved
+"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.",1385377902,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ibes2uplyibrsadgodld,task_subcomment,NA
+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",1372872180,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-3jrxscvn6apol6nbrw66,task_description,resolved
+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. :-),1372901827,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3jrxscvn6apol6nbrw66,task_subcomment,NA
+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.,1372880015,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3jrxscvn6apol6nbrw66,task_subcomment,NA
+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.",1372878719,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3jrxscvn6apol6nbrw66,task_subcomment,NA
+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",1372878612,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3jrxscvn6apol6nbrw66,task_subcomment,NA
+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",1372850220,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-72xdyaasptqyeuovlab3,task_description,open
+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}.",1603447176,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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.",1454246269,PHID-USER-bd4kgtavgiydswld34tj,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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.,1453877263,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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.",1453857840,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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...",1452890347,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+TemplateData: Parse wikicode and/or HTML in interface text,*** Bug 51311 has been marked as a duplicate of this bug. ***,1375191068,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+TemplateData: Parse wikicode and/or HTML in interface text,Please don't mark older bugs as duplicates of newer ones.,1375191065,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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 ***",1375187353,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+TemplateData: Parse wikicode and/or HTML in interface text,Is this the same as Bug 51311?,1375183810,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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",1372836600,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-itj4sdz77n2m7ganhvyr,task_description,resolved
+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.",1380437291,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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.,1380428239,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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. ***,1377831826,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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. ***,1375772188,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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).",1373581739,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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.",1373581336,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+"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",1372819920,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-ce2w6vrcycpoidffw23e,task_description,resolved
+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}",1372815240,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_description,resolved
+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.",1443085392,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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?",1443035363,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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]].",1440832509,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418395634,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418395428,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418391485,PHID-USER-ipgdr6xrndwpztdrubk4,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418391287,PHID-USER-ipgdr6xrndwpztdrubk4,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418195999,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418195570,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1410701090,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1381353945,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1381297658,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!).",1381268160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1380390102,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1380388534,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1380074042,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1380073592,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1378958879,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1378943135,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1377510579,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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! :)",1377508996,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1377501235,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1377207897,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.,1377206906,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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?",1377206495,PHID-USER-ipgdr6xrndwpztdrubk4,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1377206285,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1377205809,PHID-USER-ipgdr6xrndwpztdrubk4,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1377202366,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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",1377164934,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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",1377027661,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1376936141,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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)",1376553611,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1376085848,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.,1376070283,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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).,1376067911,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1376063216,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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 .",1374283399,PHID-USER-ipgdr6xrndwpztdrubk4,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1373767362,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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",1373675877,PHID-USER-dgjw4xb5i5zdwsiwvli5,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1373024925,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1373005232,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1372981869,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1372975898,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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).,1372970105,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.,1372965335,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,It also comes to Chrome on Win7.,1372823539,PHID-USER-mndznmqvm6ihjfmb6xap,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+"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",1372801620,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-du5yifaebt3zb2zhinvr,task_description,resolved
+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 </re>.  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",1372799760,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-5ftakv5wuzkf73akgiop,task_description,resolved
+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.,1392747780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ftakv5wuzkf73akgiop,task_subcomment,NA
+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.",1372814647,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5ftakv5wuzkf73akgiop,task_subcomment,NA
+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.",1372814416,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ftakv5wuzkf73akgiop,task_subcomment,NA
+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.",1372800411,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-5ftakv5wuzkf73akgiop,task_subcomment,NA
+"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",1372797900,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_description,resolved
+"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output",Fixed by gerrit 140439.,1404172672,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"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. ***,1385374740,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"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.",1384938909,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"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.",1378399018,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"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&section=1 ?,1378374796,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output","This is because the HTML looks like <td typeof=""mw:Transclusion"" about=""#mwt139"">...</td><td about=""#mwt139"">...</td> and so the group of table cells is considered a template, and so the CE rendering is wrapped in a <div>. 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.",1372872684,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+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",1372780080,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-65s4zvg7e6km2enogisy,task_description,resolved
+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.",1377030097,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+Templates that create multiple table cells don't work,This seems to be related to bug 44498.,1375195683,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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",1373659290,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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?",1373236010,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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],1372934113,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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.",1372797568,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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.",1372797193,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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"",
+  }",1372794694,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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.",1372791643,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+Templates that create multiple table cells don't work,and Parsoid. ;),1372788419,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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 .",1372788394,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+Templates that create multiple table cells don't work,My apologies for assuming that these two issues were related. Re-titling.,1372782463,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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)""?",1372782364,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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).",1372782107,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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 ***",1372781089,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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",1372767420,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-spssyaufehg6a576inro,task_description,resolved
+VisualEditor: Reconsider CSS content munging,"Indeed we did, this was done by the invaluable Ed in ee5b69772963c5d3f17b15742023cf33fc5dd48a.",1429615698,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-spssyaufehg6a576inro,task_subcomment,NA
+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?",1429478089,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-spssyaufehg6a576inro,task_subcomment,NA
+VisualEditor: Reconsider CSS content munging,"CSS content munging in general is a real pain, and we should find a way around it.",1385376106,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-spssyaufehg6a576inro,task_subcomment,NA
+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",1372734720,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-kazpxbs6hxscszn2mj4j,task_description,resolved
+VisualEditor: round-trip adjacent and nested annotations,This has been fixed for some time in the DM. Marking as such.,1380845963,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kazpxbs6hxscszn2mj4j,task_subcomment,NA
+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",1372742791,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-kazpxbs6hxscszn2mj4j,task_subcomment,NA
+./ 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",1372724400,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-xduyhafmy6kenmdf7cuh,task_description,resolved
+./ still appearing in links.,"
+
+*** This bug has been marked as a duplicate of bug 50720 ***",1373020641,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-xduyhafmy6kenmdf7cuh,task_subcomment,NA
+./ 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)",1372936732,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-xduyhafmy6kenmdf7cuh,task_subcomment,NA
+./ still appearing in links.,The visualeditor-needcheck tag also suggests that there was an issue in VE round-tripping. Reassigning to VE for investigation.,1372727544,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-xduyhafmy6kenmdf7cuh,task_subcomment,NA
+./ 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?",1372726643,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-xduyhafmy6kenmdf7cuh,task_subcomment,NA
+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",1372715400,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-focb5kxme3jxk4n6xklr,task_description,open
+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",1372706340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eqiuslxuu3t7bxl7vmwb,task_description,open
+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. :-)",1387398780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eqiuslxuu3t7bxl7vmwb,task_subcomment,NA
+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",1374867310,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eqiuslxuu3t7bxl7vmwb,task_subcomment,NA
+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",1374549781,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eqiuslxuu3t7bxl7vmwb,task_subcomment,NA
+VisualEditor: Close icon shown at 2x size and so truncated,"Screenshot
+
+See screenshot - monobook, windows 7, firefox 22.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11469}",1372699920,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-potyqd62zizy6tkvf2ak,task_description,declined
+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.",1377830355,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-potyqd62zizy6tkvf2ak,task_subcomment,NA
+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}",1372698960,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_description,invalid
+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.",1578935420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.),1578869465,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.",1372712317,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.,1372711488,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.",1372700082,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.",1372699315,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.",1372699118,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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//",1372670160,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-rou7bduh6enhafdxh2lv,task_description,resolved
+VisualEditor: Link input widget is not oriented for RTL,The current layout is good. There's a mistake in my image. Marking as FIXED.,1374495347,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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)' >",1374445202,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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",1373483413,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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",1372981428,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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.",1372741169,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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}",1372670380,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+"VisualEditor: <u><u> 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",1372631880,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-7n67l5aimznnhmya4iwf,task_description,open
+"VisualEditor: <u><u> 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?",1416189671,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-7n67l5aimznnhmya4iwf,task_subcomment,NA
+"VisualEditor: <u><u> 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.",1372685856,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-7n67l5aimznnhmya4iwf,task_subcomment,NA
+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",1372620960,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_description,resolved
+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",1394672072,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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",1394667684,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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 <small>Parsoid returned 504</small> or
+> <small>Parsoid not available</small> 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.",1394667530,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),We'll help. :-),1391913718,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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),1391879277,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373502193,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373482219,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373481412,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373481211,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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 <small>Parsoid returned 504</small> or <small>Parsoid not available</small> after the general call-to-action?",1373335525,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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).,1373334999,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373133953,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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),1372684698,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+"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}",1372620660,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-n26jfot72gcfg6mgq6wx,task_description,open
+"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.",1721046082,PHID-USER-k5wpqok2x66oei3wguaf,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.,1526397283,PHID-USER-qdbrv6swdxlgemqwwbuw,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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  `<ref name=""Author Date"">Author Date, page 123.</ref>` (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=data<ref>Source</ref>}}`:  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 <references /> 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.
+",1478851254,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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? ",1446421308,PHID-USER-ddcrbue3iyorn42wkwbo,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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? ",1446421206,PHID-USER-ddcrbue3iyorn42wkwbo,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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? ",1446420835,PHID-USER-ddcrbue3iyorn42wkwbo,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.,1440781886,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ",1440781461,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1430945384,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1430229351,PHID-USER-cbmsqiuerftutmt523wv,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1421203877,PHID-USER-ufjbf3qatjamiwoal5fp,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.""
+",1419470550,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1407719768,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1402332002,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1401416868,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1385381556,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1383003781,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1377843814,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1377823296,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. :-)",1377823070,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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 <references> rendering and editing.",1377822959,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1377822665,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.
+
+<ref>{{foo}}</ref> 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.",1377821853,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1377819846,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1377819444,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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 <ref> because of localization issues.,1374930557,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1374880234,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372714617,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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",1372714324,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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",1372713484,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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",1372712260,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372700420,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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 :/.,1372699735,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372699677,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372696659,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.,1372696532,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372695038,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372633730,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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 :/,1372626164,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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""?",1372622488,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372622399,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","How it actually looks
+
+**Attached**: {F11401}",1372621957,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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//",1372620753,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","How it should look
+
+**Attached**: {F11400}",1372620731,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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",1372612320,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-xnsrcsuce62r2yfruwso,task_description,declined
+"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.,1378550137,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xnsrcsuce62r2yfruwso,task_subcomment,NA
+"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.",1374461315,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-xnsrcsuce62r2yfruwso,task_subcomment,NA
+"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).",1372612642,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-xnsrcsuce62r2yfruwso,task_subcomment,NA
+"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).",1372612568,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-xnsrcsuce62r2yfruwso,task_subcomment,NA
+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",1372555020,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-op3amukih656hqtejh6j,task_description,resolved
+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.,1383280412,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-op3amukih656hqtejh6j,task_subcomment,NA
+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.",1372558387,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-op3amukih656hqtejh6j,task_subcomment,NA
+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",1372554420,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-nopdefkge3ym2od7ufrd,task_description,resolved
+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.",1414004857,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nopdefkge3ym2od7ufrd,task_subcomment,NA
+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.",1373397301,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nopdefkge3ym2od7ufrd,task_subcomment,NA
+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 :
+<templatedata>
+{
+        ""description"": ""תבנית כלשהי."",
+        ""params"": {
+                ""שם"": {
+                        ""label"": ""שם"",
+                        ""type"": ""string/wiki-user-name"",
+                        ""required"": true,
+                        ""description"": ""שם של משתמש"",
+                        ""aliases"": [""1""]
+                }
+        },
+        ""sets"": [
+                {
+                        ""label"": ""Date"",
+                        ""params"": [""שנה"", ""חודש"", ""יום""]
+                }
+        ]
+}
+</templatedata>
+It is very hard to edit such syntax as above. (<templatedata> 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",1372540320,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-ttobixbmawcbongmnatf,task_description,resolved
+TemplateData: Creating TemplateData blocks should be direction neutral,"This is now effectively ""solved"" through general availability of the GUI to edit TemplateData.",1415310061,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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,1390051584,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1389930776,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1389887269,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+TemplateData: Creating TemplateData blocks should be direction neutral,How about marking it as a duplicate of bug 51734?,1389874215,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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?",1389807290,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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",1389753678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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",1379736870,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1375130859,PHID-USER-x7g37sf6tkkrewspco2q,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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?",1375122927,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1375122853,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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)",1375122782,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1375122472,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.,1374862129,PHID-USER-x7g37sf6tkkrewspco2q,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1374664108,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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).",1374619504,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.,1374619335,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1374353774,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+TemplateData: Creating TemplateData blocks should be direction neutral,"Timo, thoughts?",1372689806,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+Wikitext list after implicit <td> 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",1372512240,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-itqhk6koq7bmakcn2wvo,task_description,resolved
+Wikitext list after implicit <td> not properly recognized,"Change 71744 merged by jenkins-bot:
+(Bug 50420) Recognize sol-content in implicit <td> after a <tr>
+
+https://gerrit.wikimedia.org/r/71744",1372829524,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> not properly recognized,"Change 71744 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 50420) Recognize sol-content in implicit <td> after a <tr>
+
+https://gerrit.wikimedia.org/r/71744",1372809900,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> not properly recognized,"Ok, renamed the bug to reflect the repurposing.",1372701474,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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",1372701241,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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.",1372651321,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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",1372650827,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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 <td> into an explicit <td> on serialization is a semantic error.
+
+Reduced test case:
+
+{|
+|-
+*a
+|}
+
+This cannot be fixed by selser since on editing the list item, the <td> 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.",1372565331,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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.",1372565021,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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.",1372518582,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+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}",1372468740,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-hoazjhp6o63s5rrky5qa,task_description,resolved
+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.",1377828038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hoazjhp6o63s5rrky5qa,task_subcomment,NA
+VisualEditor: Reference list display being cut off in some pages,Could this be the same as bug 52371?,1377443863,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hoazjhp6o63s5rrky5qa,task_subcomment,NA
+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?",1374463011,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-hoazjhp6o63s5rrky5qa,task_subcomment,NA
+"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",1372462920,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-5wuwyofe6l5k2cmqjzad,task_description,declined
+"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.",1384202462,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5wuwyofe6l5k2cmqjzad,task_subcomment,NA
+"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.",1384202215,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5wuwyofe6l5k2cmqjzad,task_subcomment,NA
+"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",1372459800,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_description,resolved
+"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)",Now fixed and deployed.,1375423094,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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",1375414255,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.",1375284716,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.",1374262304,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.""",1374250805,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.""",1374250111,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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?",1372583668,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.",1372471069,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+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",1372453440,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_description,duplicate
+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.",1396302080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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. ***,1385381652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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. ***,1377830806,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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. ***,1373164008,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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.",1372456631,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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",1372429740,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_description,resolved
+VisualEditor: Do not add size for standard thumbnail images when inserting them,Done in gerrit 114420.,1393446774,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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.",1376561973,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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).,1373230571,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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"".",1373228305,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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.",1373228269,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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.",1373227900,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+VisualEditor: Do not add size for standard thumbnail images when inserting them,*** Bug 50766 has been marked as a duplicate of this bug. ***,1372966971,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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. 
+",1372421640,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ssksx6n4c7yondhu6cpg,task_description,stalled
+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. ",1708553338,PHID-USER-bommaimh4fl3xvg3ays6,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,A 7 year old task isn't UBN,1600590692,PHID-USER-2wquu5nwbdqcuzo5qiuf,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"> Quoted Text
+
+",1600590184,PHID-USER-mjtmg5ramyrkn7pbwxmq,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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",1595500486,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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",1595500463,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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",1595500429,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1554885642,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 <path_to_wiki>/maintenance/runJobs.php"".",1543413652,PHID-USER-gowqth4c6x65hhbw4z4u,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1542979491,PHID-USER-gowqth4c6x65hhbw4z4u,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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. ",1542198870,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1428122408,PHID-USER-3bnjvlq3zbpzzxdh4g4g,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,*** Bug 69647 has been marked as a duplicate of this bug. ***,1408689531,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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).",1376401137,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1376122026,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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).",1376033464,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1373338145,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372817050,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"Observation:
+
+- Edite <templatedata> 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.",1467215528,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"Observation:
+
+- Edite <templatedata> 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.",1372807585,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372802966,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372802403,PHID-USER-jdkjcyuluyy456zxyufo,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 (<templatedata>) 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",1372798204,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372774328,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"The extension page says:
+
+""The TemplateData extension works through having a <templatedata> 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).",1372748147,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372739834,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.,1372694998,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 <templatedata> 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.",1372559871,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 )",1372513536,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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?",1372457003,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.,1372456502,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372455968,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372455886,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372454024,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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?",1372451744,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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?",1372451659,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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?""",1372423465,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"Belay that, {{tracked}} works.",1372423444,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 <https://test.wikipedia.org/wiki/Section_edit_links_bug2>. 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",1372420380,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ogwe6d555gi7xn3bq357,task_description,open
+Templates that create part (but not all) of a table cell don't work,"Screenshot
+
+See screenshot; Windows 7, Firefox 21.0, on https://en.wikipedia.org/wiki/Rage_Against_the_Machine?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50589
+
+**Attached**: {F11166}",1372417680,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bcblwti2swge5nlt24om,task_description,resolved
+Templates that create part (but not all) of a table cell don't work,"This bug was raised five months earlier.
+
+*** This bug has been marked as a duplicate of bug 44498 ***",1374455443,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"Similar hack, but now on the table itself, instead of a table cell. See the Infobox of WikiProject Aircraft:
+
+https://en.wikipedia.org/wiki/BAC_One-Eleven",1373226373,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"FYI, we are considering a post-processing work-around in Parsoid that lets this class of templates render as expected, but might not let users edit those templated cells.
+
+Our longer-term goal is to move towards more self-contained templates. This won't happen over night, and we'll need the help of the editor community and bot authors.",1372783809,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"Bug 50589 is a different issue, so I reopened it and added detail there.",1372782144,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"**kwwilliams** wrote:
+
+50589 has been marked as a duplicate of this bug. I'm certain it's related, but I'm not certain it's a duplicate. *If* it is a duplicate, marking it as ""wontfix"" isn't an acceptable answer. 
+
+singlechart *does* return the leading | or !, depending on whether it has been ask to generate a row or a header row. It generates two row cells, separated by a |.",1372781691,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,*** Bug 50589 has been marked as a duplicate of this bug. ***,1372781089,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,*** Bug 50567 has been marked as a duplicate of this bug. ***,1372781074,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"I don't have precise figures right now, but know enough to be sure that a bot will be needed. This bot pass should also fix some other issues listed in http://www.mediawiki.org/wiki/Parsoid/limitations. Do you know a bot author who might be potentially interested in a task like this? We have it on our TODO list, but did not have the time to tackle it before the release.",1372733221,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"(In reply to comment #4)
+> 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.",1372726569,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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",1372722914,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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",1372722454,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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.,1372720867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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. ***,1372720818,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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}",1372416900,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-hadccnndpx3xlfcdq5x6,task_description,resolved
+VisualEditor: Hatnote templates not displaying properly,"Fair play; marking as duplicate.
+
+%%%*** This bug has been marked as a duplicate of bug 49784 ***%%%",1375118083,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-hadccnndpx3xlfcdq5x6,task_subcomment,NA
+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 <div>, 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.",1374878501,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hadccnndpx3xlfcdq5x6,task_subcomment,NA
+VisualEditor: Hatnote templates not displaying properly,"How the hatnote appears in subsequent VE loads.
+
+**Attached**: {F11148}",1372416940,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-hadccnndpx3xlfcdq5x6,task_subcomment,NA
+VisualEditor: Hatnote templates not displaying properly,"How the hatnote appears in ""read"" mode
+
+**Attached**: {F11146}",1372416924,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-hadccnndpx3xlfcdq5x6,task_subcomment,NA
+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",1372414260,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bygkpi2cds2ycjzl4xyf,task_description,invalid
+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.",1429468968,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-bygkpi2cds2ycjzl4xyf,task_subcomment,NA
+"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.
+
+",1372412940,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-o63tibhphh5vfhjwesdx,task_description,open
+"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,1606394741,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1545161395,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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]]",1544646870,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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]]",1533659632,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1521578028,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1521578012,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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?",1456992621,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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?
+",1456946077,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1456940930,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","I have literally no idea, it was in 2014.",1456932039,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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?,1456923888,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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}
+",1456797038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1408649657,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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 ***",1372427548,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+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",1372412100,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_description,invalid
+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).",1377906050,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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",1375794547,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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) >>",1375793484,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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. <nowiki>{{fixed}}</nowiki>, 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) >>",1375793232,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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.",1374492238,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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.",1374490962,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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"".",1373874288,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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).
+
+</brain dump>",1373369674,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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",1373069621,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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).",1373026126,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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?""",1372958401,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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)",1372947691,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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.",1372944786,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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",1372411380,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vipia63usd432ltaseq6,task_description,declined
+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.",1423750227,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vipia63usd432ltaseq6,task_subcomment,NA
+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",1372389360,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_description,resolved
+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. :-)",1404356560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+VisualEditor: Title is not updated on save if DISPLAYTITLE changed,So this appears to actually be working now.,1404250963,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1404249536,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1403537537,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1403134891,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1403133467,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+VisualEditor: Title is not updated on save if DISPLAYTITLE changed,Patch reverted; re-opening.,1403122919,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1403058210,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1402607917,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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.,1402607843,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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.",1402590458,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1374040482,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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).",1372778502,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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}",1372537609,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+"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}",1372367280,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_description,declined
+"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.,1438990382,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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.,1438983806,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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.",1438974040,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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.",1404214069,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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. ***,1402552906,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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.",1378727693,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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",1372797445,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+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",1372344120,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-yelwyuxn7ull4zzjha5n,task_description,resolved
+VisualEditor: VE won't load on empty page containing only a magic word,"Fixed in the above commit, which we will push out today.",1373905170,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yelwyuxn7ull4zzjha5n,task_subcomment,NA
+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",1373905132,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yelwyuxn7ull4zzjha5n,task_subcomment,NA
+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",1373886485,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yelwyuxn7ull4zzjha5n,task_subcomment,NA
+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.,1372349806,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yelwyuxn7ull4zzjha5n,task_subcomment,NA
+"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",1372335660,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_description,resolved
+"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]]",1427409486,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_subcomment,NA
+"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]]
+",1427406328,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_subcomment,NA
+"VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message",*** Bug 51812 has been marked as a duplicate of this bug. ***,1374702151,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_subcomment,NA
+"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}",1372490316,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_subcomment,NA
+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",1372331940,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_description,resolved
+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. ***,1403995088,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_subcomment,NA
+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",1403746149,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_subcomment,NA
+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",1403731077,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_subcomment,NA
+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. :-)",1402549673,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_subcomment,NA
+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}",1372302300,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-s6tr75wkga6yoxhfytgb,task_description,resolved
+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.",1404168653,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-s6tr75wkga6yoxhfytgb,task_subcomment,NA
+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.,1393633426,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-s6tr75wkga6yoxhfytgb,task_subcomment,NA
+VisualEditor: enwiki template {{columns-list}} looks particularly-broken at high zoom/low width,I wonder if this is related to bug 50036?,1372325604,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-s6tr75wkga6yoxhfytgb,task_subcomment,NA
+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",1372302060,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-g7bv7yb2notx65burp7i,task_description,open
+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.",1374495419,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g7bv7yb2notx65burp7i,task_subcomment,NA
+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. ***,1374495310,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g7bv7yb2notx65burp7i,task_subcomment,NA
+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",1372267920,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_description,resolved
+VisualEditor: User personal links appear above VE dialogs,This was fixed in the deployment earlier this week.,1373077152,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_subcomment,NA
+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!,1372269171,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_subcomment,NA
+VisualEditor: User personal links appear above VE dialogs,"Created attachment 12650
+Screenshot showing issue (extracted from Word docx file)
+
+**Attached**: {F11829}",1372269063,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_subcomment,NA
+VisualEditor: User personal links appear above VE dialogs,"**rachelqa99** wrote:
+
+screenshot
+
+//attachment screenshotve.docx ignored as obsolete//",1372267984,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_subcomment,NA
+"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",1372262940,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yv5u43sg36sflqbgt5oh,task_description,resolved
+"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",1391818168,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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",1391210012,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.,1387723690,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.",1375369955,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.",1374762733,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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. ***,1374488278,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.,1374011002,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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",1373931722,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.,1373921680,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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. ***,1373472822,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.",1372332875,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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"".",1372323018,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+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",1372254900,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-4pmiosnpdta6wvmtogmm,task_description,resolved
+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.,1373031803,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+Jenkins: migrate qunit jobs from master to gallium,"Change 72083 merged by Hashar:
+tie qunit jobs to slaves
+
+https://gerrit.wikimedia.org/r/72083",1373031569,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+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",1373030886,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+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",1373029884,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+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",1373029751,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+"VisualEditor: Non-primary edit tab <li> 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}",1372251780,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_description,resolved
+"VisualEditor: Non-primary edit tab <li> should have class=""collapsible""","Change 123503 merged by jenkins-bot:
+Give the edit tab <li> closest to the collapsed tabs menu class=collapsible
+
+https://gerrit.wikimedia.org/r/123503",1396639943,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_subcomment,NA
+"VisualEditor: Non-primary edit tab <li> should have class=""collapsible""","Change 123503 had a related patch set uploaded by Alex Monk:
+Give the edit tab <li> closest to the collapsed tabs menu class=collapsible
+
+https://gerrit.wikimedia.org/r/123503",1396487823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_subcomment,NA
+"VisualEditor: Non-primary edit tab <li> 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 <li> and it will magically work.",1372252025,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_subcomment,NA
+"VisualEditor: Non-primary edit tab <li> should have class=""collapsible""","Created attachment 12643
+Screenshot: High zoom
+
+**Attached**: {F11767}",1372251857,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_subcomment,NA
+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",1372231980,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-rl6rjnnqsrrmwprvwrmk,task_description,resolved
+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 ***",1372270074,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rl6rjnnqsrrmwprvwrmk,task_subcomment,NA
+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",1372220460,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cypsptchtj5tr3ktdvxq,task_description,resolved
+VisualEditor: Possible to have links nested inside links,Merged and we'll push this to production in the next hour or so.,1372260507,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cypsptchtj5tr3ktdvxq,task_subcomment,NA
+VisualEditor: Possible to have links nested inside links,Related URL: https://gerrit.wikimedia.org/r/70644 (Gerrit Change I1cab7f3cc4fc9589eced01ad38c59fe5b9622a57),1372260143,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cypsptchtj5tr3ktdvxq,task_subcomment,NA
+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.",1372221303,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cypsptchtj5tr3ktdvxq,task_subcomment,NA
+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",1372192080,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-flrq364icuczabc3nb2z,task_description,resolved
+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",1412209365,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-flrq364icuczabc3nb2z,task_subcomment,NA
+"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}",1372175760,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-nctiyee24idgcp7llspj,task_description,open
+"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,1606768378,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1545161536,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1478109985,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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?",1477067771,PHID-USER-ijhuwuyd44xnfjon2ztf,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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. ***,1394074105,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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 <div
+> class=""mw-columns-2""> .. </div>. 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.",1374272400,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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 <div class=""mw-columns-2""> .. </div>. 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.",1374267053,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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. ***,1374014309,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1373440193,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1373054528,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1372789939,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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. ***,1372789775,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","Something like <div class=""mw-columns-2""> .. </div> 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.",1372780602,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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]]",1372779956,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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. ***,1372427548,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1372212497,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+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",1372164120,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-nu54imdjney5p47v7jx7,task_description,resolved
+VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,I think this was resolved in Gerrit change 127388,1397915597,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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..?",1381109369,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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. ***,1372796056,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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.",1372796032,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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.",1372728297,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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?",1372176869,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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.",1372172844,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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",1372162920,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-f2jkrvqamprej6vbtifd,task_description,open
+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.",1372693967,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f2jkrvqamprej6vbtifd,task_subcomment,NA
+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"".",1372498760,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-f2jkrvqamprej6vbtifd,task_subcomment,NA
+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",1372158120,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eirxrxhok3puf5mpvsgj,task_description,open
+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).",1373553594,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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),1372424049,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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.",1372420020,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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)",1372169071,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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?",1372163402,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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",1372102560,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-coeco2n4cfz4d24eek2p,task_description,resolved
+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
+==<nowiki/>==
+```
+
+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 `<nowiki/>` in a heading at the end. I could not reproduce this on testwiki today. Closing as resolved.",1521857381,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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.",1521842541,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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.",1521842221,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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.",1443020040,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+VisualEditor: Can't copy/paste header from start of document without losing formatting,*** Bug 54728 has been marked as a duplicate of this bug. ***,1381157444,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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.",1381148291,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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",1372091520,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gvpsurapr2wpn6mmysso,task_description,resolved
+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.,1372120126,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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],1372118250,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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),1372113630,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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<noinclude>|Example.svg</noinclude>}}}}}}}}|right|{{Str number/trim|{{{3|{{{width|250px}}}}}}}}px|{{{2|{{{caption<noinclude>|Caption goes here.</noinclude>}}}}}}]]
+
+->
+
+<figure class=""mw-halign-right"" typeof=""mw:Image"" data-parsoid=""…"">
+  <a href=""./File:Chloroplast_II.svg"" data-parsoid=""…""><img resource=""./File:Chloroplast_II.svg"" src=""…"" height=""344"" width=""360"" data-parsoid=""…""></a>
+  <figcaption class=""mw-figcaption"" data-parsoid=""{}"">Structure of a typical higher-plant chloroplast</figcaption>
+</figure>
+
+(The <figcaption> shouldn't be set, and also there should be an alt="""" set.)",1372110890,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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.",1372096750,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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.",1372096339,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","https://en.wikipedia.org/w/index.php?title=AES11&diff=prev&oldid=561340674
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T57769}
+{T61647}",1372085880,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_description,resolved
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",Split that into {T96395} as it's mobile-specific.,1429293419,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",It looks like this is still happening: https://en.wikipedia.org/w/index.php?diff=655361654,1428430329,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",Indeed.,1427847427,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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).",1427822170,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",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?,1427820191,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",The same fix as for T51452 - verified in beta.,1427153983,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output <p> instead of <h#>
+
+[[https://gerrit.wikimedia.org/r/162310]]",1426893387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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",1424197331,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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",1411496967,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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",1377222680,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",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.,1377203188,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","<< 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) >>",1375953600,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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?",1375792751,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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.",1374611501,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",*** Bug 51829 has been marked as a duplicate of this bug. ***,1374609807,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","""Encourage"" yes...",1373990534,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","(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.",1373987840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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).",1373987554,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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)?",1373987470,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",%%%*** Bug 51417 has been marked as a duplicate of this bug. ***%%%,1373938091,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",*** Bug 50313 has been marked as a duplicate of this bug. ***,1373154763,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+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",1372078500,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ui3plx4slven33rbf4id,task_description,resolved
+Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,"'[[' triggers Link insertion; '{{' - inserts Template.
+
+Verified in beta/test2/production",1418076035,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,ZOMG!,1418036506,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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]]",1416966721,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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",1416964645,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,This is no longer catastrophically expensive to do. Yay.,1416960372,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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.",1372879524,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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 ""<gallery>"" into a Bugzilla bug title and expect it to say ""<gallery>"" 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.",1372786202,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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.,1372349396,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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)",1372091407,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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",1372035540,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-zkfo43fncbploqynkreq,task_description,resolved
+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.,1373929765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zkfo43fncbploqynkreq,task_subcomment,NA
+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",1373929587,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-zkfo43fncbploqynkreq,task_subcomment,NA
+VisualEditor: Reflist columns parameter getting ignored/changed for display,Can't reproduce (not anymore at least). Can you?,1373929392,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zkfo43fncbploqynkreq,task_subcomment,NA
+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}",1372035240,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-xeya3bpycvyi4743gzho,task_description,resolved
+VisualEditor: clicking on a template in the reference inspector causes odd blue shadowing,*** Bug 49768 has been marked as a duplicate of this bug. ***,1373155495,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xeya3bpycvyi4743gzho,task_subcomment,NA
+VisualEditor: clicking on a template in the reference inspector causes odd blue shadowing,"
+
+%%%*** This bug has been marked as a duplicate of bug 49818 ***%%%",1372118661,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-xeya3bpycvyi4743gzho,task_subcomment,NA
+VisualEditor: Unreferenced section template not displaying properly,"See screenshot; problem with the template or with the parsing of it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372033980,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_description,resolved
+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 ***",1373155344,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+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.",1372083906,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+VisualEditor: Unreferenced section template not displaying properly,Try https://en.wikipedia.org/wiki/Riddler#Fictional_character_biography,1372083632,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+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)",1372083538,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+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}",1372034067,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+"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",1371995700,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vrnyctiie6ntzdrqt77a,task_description,resolved
+"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.",1642380969,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vrnyctiie6ntzdrqt77a,task_subcomment,NA
+"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, <i>Foo <sup>Bar</i> Baz</sup> 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.",1372000762,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vrnyctiie6ntzdrqt77a,task_subcomment,NA
+"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.)""",1371996216,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vrnyctiie6ntzdrqt77a,task_subcomment,NA
+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",1371977520,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-d42ybmk2s2iavorgwpdd,task_description,declined
+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",1379404668,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+Set $wgWellFormedXml = false by default,I note btw that the tidy config is also set to produce XHTML.,1375782777,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+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.",1375143938,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+Set $wgWellFormedXml = false by default,"(In reply to comment #2)
+> You could just use <script>if(jQuery)jQuery.ready()</script>, it would be
+> shorter than what you have currently: <script>window.jQuery &&
+> jQuery.ready();</script>
+
+<script>if(window.jQuery)jQuery.ready()</script>, 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.",1372758238,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+Set $wgWellFormedXml = false by default,"You could just use <script>if(jQuery)jQuery.ready()</script>, it would be shorter than what you have currently: <script>window.jQuery && jQuery.ready();</script>
+
+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.",1372740996,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+Set $wgWellFormedXml = false by default,Related URL: https://gerrit.wikimedia.org/r/70036 (Gerrit Change I4155c74042d22527dc5c9460a4af8b7b1adb36cc),1371978337,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+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",1371896940,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-fcxjzl7orc3z55j4k4z4,task_description,resolved
+VisualEditor: cannot reposition typing cursor using the mouse in edit summary,Fixed and deployed; sorry for this.,1372007051,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fcxjzl7orc3z55j4k4z4,task_subcomment,NA
+VisualEditor: cannot reposition typing cursor using the mouse in edit summary,A fix to bug 49927 might also fix this.,1371899709,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-fcxjzl7orc3z55j4k4z4,task_subcomment,NA
+"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"".",1371864600,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-457x6imtkd7rswr4kl6x,task_description,duplicate
+"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.",1408114605,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder",*** Bug 69568 has been marked as a duplicate of this bug. ***,1408096620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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)",1394228553,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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.",1372888485,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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",1372882958,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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. ~~~~",1372881473,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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",1371851820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-busqmj37jbvye6nty5bt,task_description,resolved
+"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",1403052458,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"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",1403008691,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 49486 has been marked as a duplicate of this bug. ***,1380609083,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"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.,1380324429,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"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.",1380151994,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 52364 has been marked as a duplicate of this bug. ***,1375319436,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 50359 has been marked as a duplicate of this bug. ***,1373663953,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"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.,1373663569,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 50183 has been marked as a duplicate of this bug. ***,1372183302,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+VisualEditor: Closing a dialog scrolls you up to the top of the document,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1371844500,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_description,resolved
+VisualEditor: Closing a dialog scrolls you up to the top of the document,Fixed and being deployed right now.,1372264572,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_subcomment,NA
+VisualEditor: Closing a dialog scrolls you up to the top of the document,Related URL: https://gerrit.wikimedia.org/r/70614 (Gerrit Change I8cc12ba7845eebc6199fbcd2d355bf0d5f38264b),1372248326,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_subcomment,NA
+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.",1372246033,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_subcomment,NA
+VisualEditor: Closing a dialog scrolls you up to the top of the document,This is a regression because I fixed dialog close re-focusing.,1372245042,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_subcomment,NA
+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",1371833340,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-pcf2yvjdcefbppv4nmdv,task_description,resolved
+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).",1373160219,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pcf2yvjdcefbppv4nmdv,task_subcomment,NA
+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",1371829500,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-4tagph3in7nb7kiwdldq,task_description,resolved
+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.,1399325038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4tagph3in7nb7kiwdldq,task_subcomment,NA
+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.",1371862821,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-4tagph3in7nb7kiwdldq,task_subcomment,NA
+"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'.
+",1371816900,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-ynxqancujipoqcvx5723,task_description,open
+"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).",1706714108,PHID-USER-jqjb54lbf7psat6shbcc,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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.",1598465114,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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.",1498746227,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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.",1498680522,PHID-USER-53x4y44yt43qjivfzsqf,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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:
+
+<p data-parsoid=""…"">This was <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw=""{'target':{'wt':'formatnum:1234567890','function':'formatnum'}"" data-parsoid=""…"">1,234,567,890</span> years ago.</p>
+
+… so maybe we'd want to special-case on 'function':'formatnum' so that they're easier to edit?",1371827641,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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.
+",1371806460,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_description,declined
+"Window title for ""Creating"" should support parser functions","(If they're wontfix, then let's decline them.)",1428960831,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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. ",1428691205,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"Window title for ""Creating"" should support parser functions","(No ""Parse error at position 0"" since T54479 was fixed.)",1428685485,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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.",1428685233,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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.",1393633921,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"Window title for ""Creating"" should support parser functions",This seems solved now on dewp. Good to close from my side.,1372530530,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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]]).",1371813154,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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",1371799440,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-uebopddiz3ehqfkg326y,task_description,resolved
+"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.",1373328441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uebopddiz3ehqfkg326y,task_subcomment,NA
+"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",1373325381,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uebopddiz3ehqfkg326y,task_subcomment,NA
+"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",1373300386,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uebopddiz3ehqfkg326y,task_subcomment,NA
+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",1371789600,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gk2mpik33dhlthfx6ji5,task_description,resolved
+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.",1377546664,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1377035685,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1376947589,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1376675597,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1376671455,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+Parsoid not correctly rendering bold/italic text,*** Bug 52254 has been marked as a duplicate of this bug. ***,1376606358,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+Parsoid not correctly rendering bold/italic text,See also bug 47326.,1374604512,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+Parsoid not correctly rendering bold/italic text,Just dropping this in for cross-referencing: bug 13227 (this bug made me remember that one).,1373766179,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+Parsoid not correctly rendering bold/italic text,"Taking this one, on subbu's suggestion.",1373301911,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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""",1373281341,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1371780960,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6j7kkh226srwx4yd3xob,task_description,declined
+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.,1530904214,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6j7kkh226srwx4yd3xob,task_subcomment,NA
+"VisualEditor: Rename internal use of ""Reference list"" to ""References list""","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371780900,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pg2baotfmhrts6ap3fmf,task_description,resolved
+"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",1408584637,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pg2baotfmhrts6ap3fmf,task_subcomment,NA
+"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",1408473225,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pg2baotfmhrts6ap3fmf,task_subcomment,NA
+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",1371759600,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-io6oush42k3uezzajdmy,task_description,declined
+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.",1389653066,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+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.",1385157948,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+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 ;)",1385137357,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,Greg: Was that a question to hashar?,1385134227,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,"So now ""all"" that is needed is to have this in a cronjob that mails the output to...?",1383761840,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,https://gerrit.wikimedia.org/r/#/c/70836/ adds a script to verify the extensions syncronization.,1372350237,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+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.
+$",1372349620,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+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.",1372349226,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,"Campaigns not updating, bug 50261",1372348299,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,"Vector was not updated either, might have caused bug 49911",1372090121,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+"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",1371753840,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-js3thiqf6n5putzp4qaq,task_description,resolved
+"Parsoid should have template parameter key/value whitespace of "" = "" not ""=""",This has now been done in Parsoid.,1372007229,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-js3thiqf6n5putzp4qaq,task_subcomment,NA
+"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.",1371793447,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-js3thiqf6n5putzp4qaq,task_subcomment,NA
+"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.",1371777646,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-js3thiqf6n5putzp4qaq,task_subcomment,NA
+"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",1371722040,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-fzpzl3u4tnchcdvuauzd,task_description,declined
+"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.",1393526293,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fzpzl3u4tnchcdvuauzd,task_subcomment,NA
+"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.",1371777288,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fzpzl3u4tnchcdvuauzd,task_subcomment,NA
+"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?",1371775521,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fzpzl3u4tnchcdvuauzd,task_subcomment,NA
+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",1371681900,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_description,resolved
+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",1395081900,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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",1395081559,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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.",1395081362,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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).",1395080439,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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?",1395077436,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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?",1395072264,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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.",1395071686,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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",1393637954,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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.,1392847659,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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?).,1387811244,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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
+<span typeof=""mw:Image"" ><a href=""./File:VisualEditor-logo.svg""><img src=""http://vewiki/MediaWiki/images/thumb/1/12/VisualEditor-logo.svg/300px-VisualEditor-logo.svg.png"" resource=""./File:VisualEditor-logo.svg"" width=""300"" height=""105""></a></span>
+[subbu@earth lib] node parse --html2wt < /tmp/img.html
+[[File:VisualEditor-logo.svg|300x300px]]",1385081773,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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],1372934020,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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.",1372214663,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+Images: New images get a link=… set whether or not they need it,*** Bug 49848 has been marked as a duplicate of this bug. ***,1372214626,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+Images: New images get a link=… set whether or not they need it,Related URL: https://gerrit.wikimedia.org/r/70551 (Gerrit Change I75dbbfdd248a6f5696252ef3a2d7ca6ede0fa156),1372198165,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+Images: New images get a link=… set whether or not they need it,"<span typeof=""mw:Image"" ><a href=""./File:VisualEditor-logo.svg"" data-parsoid=""{'a':{'href':'./File:VisualEditor-logo.svg'}}""><img src=""http://vewiki/MediaWiki/images/thumb/1/12/VisualEditor-logo.svg/300px-VisualEditor-logo.svg.png"" resource=""./File:VisualEditor-logo.svg"" width=""300"" height=""105""></a></span>
+
+serialises to:
+
+[[File:VisualEditor-logo.svg|300x105px]]
+
+Whereas
+
+<span typeof=""mw:Image"" ><a href=""./File:VisualEditor-logo.svg""><img src=""http://vewiki/MediaWiki/images/thumb/1/12/VisualEditor-logo.svg/300px-VisualEditor-logo.svg.png"" resource=""./File:VisualEditor-logo.svg"" width=""300"" height=""105""></a></span>
+
+(removed data-parsoid from <a> tag)
+
+serialises to:
+
+[[File:VisualEditor-logo.svg|link=File:VisualEditor-logo.svg|300x105px]]",1371815879,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+Images: New images get a link=… set whether or not they need it,This looks like a Parsoid issue:,1371815790,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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",1371667800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q46agi2mree3c3qnk2y4,task_description,invalid
+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.",1377905614,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q46agi2mree3c3qnk2y4,task_subcomment,NA
+VisualEditor: Quick transclusion dialog UX improvements,Have un-trackered-this;,1377900084,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q46agi2mree3c3qnk2y4,task_subcomment,NA
+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",1373390839,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q46agi2mree3c3qnk2y4,task_subcomment,NA
+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).",1372115134,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-q46agi2mree3c3qnk2y4,task_subcomment,NA
+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",1371653940,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-ju3g2oypj6sg3qneywp4,task_description,resolved
+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.,1373519486,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ju3g2oypj6sg3qneywp4,task_subcomment,NA
+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.  :)",1372611006,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ju3g2oypj6sg3qneywp4,task_subcomment,NA
+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",1371640200,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-fismtah5nhz3jechnxci,task_description,resolved
+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? 
+",1426194482,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1426093128,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),{F56750}?,1425633018,PHID-USER-tjeabpzbwsqw3xciydvb,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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]]",1425595128,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ",1425336374,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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]]
+",1425335832,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1415129033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. :-)",1407754116,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1405114018,PHID-USER-mcyovqjor52nj3se4lq7,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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"". :-)",1405095333,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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?,1405090910,PHID-USER-mcyovqjor52nj3se4lq7,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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?",1405021766,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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'?",1405021269,PHID-USER-mcyovqjor52nj3se4lq7,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1393529166,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1393271674,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1376642559,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1376609977,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1375472168,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1375471087,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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?",1374978010,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1374447614,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.,1374427617,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.,1374261491,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1374086311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1373895714,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1373646789,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1373610238,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1373225859,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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... ?""",1373225304,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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,1372445837,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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 <div style=""display:none;"">something</div> hidden, or what about <div class=""hidden"">something</div> when [[MediaWiki:Common.css]] contains .hidden{display:none;} ?",1372441452,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1371790287,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1371755069,PHID-USER-evwol34rsld7viokxokd,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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",1371595680,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_description,resolved
+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]]",1463387273,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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]]
+",1463310979,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 72045 has been marked as a duplicate of this bug. ***,1413312100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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.",1412202934,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 52032 has been marked as a duplicate of this bug. ***,1395357259,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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 <span> 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.",1386022898,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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 <span> 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).",1386022755,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 50610 has been marked as a duplicate of this bug. ***,1385375646,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 54893 has been marked as a duplicate of this bug. ***,1380746310,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,%%%*** Bug 50363 has been marked as a duplicate of this bug. ***%%%,1375118083,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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.",1371595810,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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",1371592380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_description,resolved
+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",1372553711,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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).",1372548881,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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",1372547853,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+VisualEditor: Template dialog should look up TemplateData for newly-added templates,Done in the above commit.,1372462774,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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",1372462602,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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",1372455529,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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).",1372411786,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+"VisualEditor: Images, when resized, appear on top of (rather than underneath) other UI elements","Screenshot
+
+See associated screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11694}",1371583860,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-sbmvrc3jz243m2e4aqmd,task_description,resolved
+"VisualEditor: Images, when resized, appear on top of (rather than underneath) other UI elements","Now fixed, I believe.",1372016119,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sbmvrc3jz243m2e4aqmd,task_subcomment,NA
+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",1371579720,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-2nqdcy26wu7c3ct3pti6,task_description,open
+VisualEditor: Rename [big|small]Stack variables in ve.dm.Surface,"To something which describes their function, not form.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371571320,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vaw5sbbofozchqbqlxfo,task_description,resolved
+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",1386729691,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vaw5sbbofozchqbqlxfo,task_subcomment,NA
+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",1386534617,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vaw5sbbofozchqbqlxfo,task_subcomment,NA
+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",1371521220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jdjfrc2gvkcmr2dyxdhz,task_description,resolved
+VisualEditor: You can't select text in the save dialog,This was fixed in wmf8.,1371775703,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jdjfrc2gvkcmr2dyxdhz,task_subcomment,NA
+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}",1371465120,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_description,resolved
+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.",1372863371,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+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).",1372859288,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+VisualEditor: Link duplicated,This isn't necessarily the same issue. Is it reproduceable?,1372858764,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+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,1372851661,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+VisualEditor: Link duplicated,"We fixed this as part of the DM tweaks, I believe.",1372017902,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+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",1371404760,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-e2zkvddmlxs36w5rmyck,task_description,resolved
+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.,1383959019,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e2zkvddmlxs36w5rmyck,task_subcomment,NA
+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.",1383957760,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-e2zkvddmlxs36w5rmyck,task_subcomment,NA
+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.",1371437921,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e2zkvddmlxs36w5rmyck,task_subcomment,NA
+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.
+",1371315660,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-3z252ihuxf33ir4how73,task_description,resolved
+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]]
+",1506354915,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1506353477,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,Adding the tag per https://www.mediawiki.org/w/index.php?title=Topic:Tys3st4u4fbxis43 .,1506344878,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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}",1505939521,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505921950,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505920720,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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&section=new",1505920852,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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&section=new",1505920393,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1505905997,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505764754,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505749186,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505747261,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1505512035,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505511929,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.,1499341318,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]",1483474747,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1483203829,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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 ]]).",1481256401,PHID-USER-aklqcs2xae5ghg6icqmd,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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}",1481076359,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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,1466772802,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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?",1466694115,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,A note from @tpt that this is pretty important for successful #proofreadpage integration.,1466693905,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1434985826,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1434985691,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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!",1434967229,PHID-USER-wtbw6n3qdyre3vir7o3z,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1434831191,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,"I've merged the above, and copied the details into the description above.",1434824570,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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)",1424027843,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,Editintro/preloud are parts of inputbox extension? Or how it is related?,1424000855,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,Indeed.,1421917704,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1419623366,PHID-USER-rbfsfm2cvpr37oz3wxju,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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",1371313740,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6welutlbuxohheakxhlf,task_description,resolved
+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. ***,1373162765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6welutlbuxohheakxhlf,task_subcomment,NA
+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.,1372109956,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6welutlbuxohheakxhlf,task_subcomment,NA
+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),1372109122,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6welutlbuxohheakxhlf,task_subcomment,NA
+"""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",1371298920,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ccjs4p2cgeia2i67aibl,task_description,resolved
+"""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",1376116309,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ccjs4p2cgeia2i67aibl,task_subcomment,NA
+"""View source"" is missing on protected LQT pages",Related URL: https://gerrit.wikimedia.org/r/68860 (Gerrit Change I99c17acea0be7b0ef650959e5e280ca5e9154b2a),1371306935,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ccjs4p2cgeia2i67aibl,task_subcomment,NA
+"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",1371297660,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-fbmrhc7yiidum6n27xww,task_description,open
+"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.",1371429262,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fbmrhc7yiidum6n27xww,task_subcomment,NA
+"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.",1371426645,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-fbmrhc7yiidum6n27xww,task_subcomment,NA
+"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.)",1371422468,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fbmrhc7yiidum6n27xww,task_subcomment,NA
+"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.",1371297776,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-fbmrhc7yiidum6n27xww,task_subcomment,NA
+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",1371261480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-esg6d3iurlxoqoaozlgc,task_description,resolved
+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,1372103132,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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,1372103030,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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?",1372098253,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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.,1372093892,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"From <https://en.wikipedia.org/w/index.php?title=Wikipedia:Administrators%27_noticeboard&oldid=560544063#VisualEditor_-_A.2FB_test_launch_on_18_June>:
+
+---
+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.",1371610389,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"I fully agree with MZMcBride :
+* I think it's ethically questionable to run experiments on users in this manner
+* There are still severe bugs in VisualEditor at this time, so it shouldn't be deployed more widely
+
+And I've more concerns about this kind of experiments :
+* There are still a lot of minor/major bugs in VisualEditor at this time, I don't expect new users to have to handle them when discovering Wikipedia edition.
+* There are still major limitations on what can be done with VisualEditor (templates, references, ...). What will be the experience for new users if they can only edit some parts of articles ?
+
+I believe this kind of experiment should only be done when VisualEditor is fully functional (when users can do almost every modification they want) and without major bugs left.",1371286353,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"(In reply to comment #0)
+> 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.",1371266626,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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.",1371263231,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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.",1371262864,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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),1371262367,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,Has en.wikipedia been notified?,1371262231,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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),1371262153,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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",1371258900,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_description,resolved
+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",1373582616,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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.",1373486407,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+VisualEditor: Show VisualEditor tag in diffs,"Change 72317 merged by jenkins-bot:
+Show change tags on diffs
+
+https://gerrit.wikimedia.org/r/72317",1373483242,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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.)",1373226492,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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.",1373162088,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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.",1373150736,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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?",1373145320,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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",1373144622,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+VisualEditor: Show VisualEditor tag in diffs,"Core change request created as bug 49656. Until that's done this is a ""later"", sadly.",1371419564,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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",1371201120,PHID-USER-4jecvpv4h62htut6pxez,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_description,resolved
+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.",1453749454,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 58662 has been marked as a duplicate of this bug. ***,1389025443,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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.,1377961711,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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",1377957239,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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.",1377491236,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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",1374250703,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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"".",1374241350,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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",1374238606,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 51354 has been marked as a duplicate of this bug. ***,1373968970,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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. ***%%%",1372424196,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 50345 has been marked as a duplicate of this bug. ***,1372403231,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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.",1372351337,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 50293 has been marked as a duplicate of this bug. ***,1372351064,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 49704 has been marked as a duplicate of this bug. ***,1371699225,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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. :-),1371429357,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 49643 has been marked as a duplicate of this bug. ***,1371409196,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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,1371204225,PHID-USER-m2yck6646cdt5t6zkta4,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+VisualEditor: Review behaviour in CE with <p><br /></p>s,"Need to review and get working so we can ask Parsoid to re-enable these (stop them being wrapped as <mw:Placeholder>s) - bug 47403 comment 3.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1371181020,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-txjmg5opo7xccxwery5r,task_description,open
+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",1371162780,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-mmsz5huxzdhmzpx6zlmd,task_description,open
+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).",1371163018,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mmsz5huxzdhmzpx6zlmd,task_subcomment,NA
+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",1371162120,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fruuvllzbsjlpilalc3q,task_description,resolved
+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]]
+",1433773169,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fruuvllzbsjlpilalc3q,task_subcomment,NA
+VisualEditor: Can't paste into a selection covering the end of the document,Merged and will go out with wmf8 from Thursday 20 June.,1371233886,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fruuvllzbsjlpilalc3q,task_subcomment,NA
+VisualEditor: Can't paste into a selection covering the end of the document,Related URL: https://gerrit.wikimedia.org/r/68629 (Gerrit Change I7497b5195961e46718c7382409a66b7eec1162a9),1371207127,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fruuvllzbsjlpilalc3q,task_subcomment,NA
+"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",1371158700,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_description,resolved
+"VisualEditor: Dialogs are quite big, maybe they could be smaller",We changed the sizes of dialogs a few months ago.,1399324736,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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",1372037113,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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...",1371167576,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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)",1371167012,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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.",1371166679,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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.",1371160792,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+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",1371107160,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-dlisjakdxxdx6ulkcllp,task_description,resolved
+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.",1416502788,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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?,1416499941,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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.,1371688878,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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.",1371688489,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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}",1371422675,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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}",1371294885,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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.",1371145548,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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}",1371060180,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-pq2jmdduyi27pmzdn6fs,task_description,resolved
+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!",1371437544,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pq2jmdduyi27pmzdn6fs,task_subcomment,NA
+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:  <h3 data-parsoid='{""dsr"":[4514,4534,3,3]}'></h3>
+
+Serializes to ===<nowiki/>=== 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",1370981700,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cdvhznmmt4p6jcin6skh,task_description,resolved
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,These look like cached code issues. Closing absent further issues.,1428879414,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1428038357,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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}
+
+
+
+",1428015629,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"No other edits with `==<nowiki/>==` for the moment, I will send an other comment if I see one",1428007868,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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 `==<nowiki/>==` that are more recent?",1427995437,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1427990524,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"Deleting headings is clean now
+
+Beta {F103264}
+vs
+current production(wmf22)
+{F103266}",1427153835,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output <p> instead of <h#>
+
+[[https://gerrit.wikimedia.org/r/162310]]",1426893388,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1424197333,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,*** Bug 70368 has been marked as a duplicate of this bug. ***,1415886608,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1412538863,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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).,1370983752,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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).",1370982732,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1370954520,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sit6vtslr7r2fqfrzugp,task_description,resolved
+VisualEditor: Grunt leaves behind temporary html file if tests fail,Related URL: https://gerrit.wikimedia.org/r/68631 (Gerrit Change I5079d00a63d43276a12dd78c306bb3819470631d),1371209624,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sit6vtslr7r2fqfrzugp,task_subcomment,NA
+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",1370952120,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-2qasjtis6bukznlqh6fa,task_description,open
+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?",1371157225,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2qasjtis6bukznlqh6fa,task_subcomment,NA
+"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",1370950980,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-4rqn2y6kag5uml6nligz,task_description,resolved
+"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)",Fix deployed.,1372103155,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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],1372100461,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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),1372095883,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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.",1372016595,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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.",1372016463,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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.",1372016204,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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",1372008424,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+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",1370912280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yt5y3btrqqtcxanvipk4,task_description,invalid
+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.",1493662142,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yt5y3btrqqtcxanvipk4,task_subcomment,NA
+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' ] );""",1371579540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yt5y3btrqqtcxanvipk4,task_subcomment,NA
+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.",1370966116,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-yt5y3btrqqtcxanvipk4,task_subcomment,NA
+Images: Handle templated image options containing pipes,"Some perverse templates such as {{Largethumb}} return a string with several options separated by pipes (""thumb|<number>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",1370889600,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_description,resolved
+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.
+",1586539013,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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. ",1448822406,PHID-USER-mcyovqjor52nj3se4lq7,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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.",1445266289,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,"Nothing to be here for this quarter .. So, I am removing the VE Q3 blocker part.",1426264942,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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 <figure> 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.",1424980985,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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.",1422665790,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,All patches merged; resetting bug status,1398408280,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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?,1392422070,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1392413844,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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.",1391708056,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1391639487,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1375218314,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1375215680,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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).",1374636592,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,~ 1 in 225 nlwp articles (0.45%) have this bug.  This bug affects the whole page.,1374635889,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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}}'.",1374627506,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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.",1374598056,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1374571791,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,https://gerrit.wikimedia.org/r/67853 (Gerrit Change Ic7652979ec3d5fa35995aac9362c812ab4ede173) | change APPROVED and MERGED [by jenkins-bot],1370890352,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,Related URL: https://gerrit.wikimedia.org/r/67853 (Gerrit Change Ic7652979ec3d5fa35995aac9362c812ab4ede173),1370889698,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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 <nowiki> 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",1370887500,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-oqao2yl4prg5uecpylkw,task_description,resolved
+VisualEditor: Misc. issues,Marking as such.,1371227728,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"The <nowiki> 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.",1371227543,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+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.",1370992657,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"The <nowiki> 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 <nowiki> 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)",1370984493,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"Expansion wtf (warning: large diff):
+
+https://en.wikipedia.org/w/index.php?title=Breast_cancer&diff=558696523&oldid=558695500",1370895676,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+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)
+> <Gallery> 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.",1370895167,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"<nowiki> funkiness:
+
+https://en.wikipedia.org/w/index.php?title=Louis-J%C3%A9r%C3%B4me_Gohier&curid=2785680&diff=558445883&oldid=542944471",1370894826,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"Misspelling trap:
+
+https://en.wikipedia.org/w/index.php?title=Pepsi_Next&curid=35519554&diff=559230837&oldid=559223494",1370889236,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"<Gallery> funkiness:
+
+https://en.wikipedia.org/w/index.php?title=British_Rail_Class_50&curid=1448622&diff=559199747&oldid=558786539",1370888839,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+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 <https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=visualeditor>.
+
+
+<nowiki> corruption:
+
+https://en.wikipedia.org/w/index.php?title=Black_Country_Communion&curid=25818560&diff=559205644&oldid=547680063
+
+
+<nowiki/> weirdness:
+
+https://en.wikipedia.org/w/index.php?title=Lightning_(software)&diff=prev&oldid=559252596
+
+
+Possible unintentional HTML comment removal; <nowiki> corruption:
+
+https://en.wikipedia.org/w/index.php?title=Underworld_(band)&diff=prev&oldid=559255806",1370888558,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+"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.
+",1370728680,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-bhc7xmtcptcglmeqxvai,task_description,open
+"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). :-)",1459673675,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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. ",1459672642,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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 <ref>s */
+span.mw-ref a::after {
+  content: counter(mw-Ref,decimal);
+} 
+```",1459667425,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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.",1459667268,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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.",1459666387,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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.,1413330448,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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 <ref group=lower-alpha> 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.",1407177406,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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. ***,1379788309,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+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",1370654940,PHID-USER-7e4yonmruupxzg23swum,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_description,resolved
+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.",1376684880,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"Change 79321 merged by jenkins-bot:
+Add tyv.wikipedia to projects with visualeditor
+
+https://gerrit.wikimedia.org/r/79321",1376665033,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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",1376653964,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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/",1376639564,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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",1376621641,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,RT ticket created for addition of lucene search indexes https://rt.wikimedia.org/Ticket/Display.html?id=5588,1376196871,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Done!,1376196328,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"Change 68188 merged by jenkins-bot:
+(bug 49328) Create Wikipedia in Tyvan language
+
+https://gerrit.wikimedia.org/r/68188",1376194827,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,*** Bug 52691 has been marked as a duplicate of this bug. ***,1376116627,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"Change 78332 merged by jenkins-bot:
+Add tyv to langlist
+
+https://gerrit.wikimedia.org/r/78332",1376020675,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"Change 78332 had a related patch set uploaded by Reedy:
+Add tyv to langlist
+
+https://gerrit.wikimedia.org/r/78332",1376020621,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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
+> <https://meta.wikimedia.org/w/index.php?diff=5529039&oldid=5528970>, 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 <http://incubator.wikimedia.org/wiki/Talk:Wp/tyv/%D0%9A%D0%BE%D0%BB_%D0%B0%D1%80%D1%8B%D0%BD#Localization> 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.",1374941968,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"It should not be chosen arbitrarily. It is chosen according to what was requested on the Meta request, here <https://meta.wikimedia.org/w/index.php?diff=5529039&oldid=5528970>, 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.",1374927661,PHID-USER-7e4yonmruupxzg23swum,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #15)
+> (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 Видибилиином?",1374916375,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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 ""Видибилиином"".",1374916112,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1374767554,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1374065889,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1374061512,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.)",1373968444,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1373963779,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1373941142,PHID-USER-7e4yonmruupxzg23swum,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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?):
+> <https://incubator.wikimedia.org/wiki/Talk:Wp/tyv/
+> %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:
+> <https://incubator.wikimedia.org/w/index.php?title=Wp/tyv/
+> %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.",1373939223,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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?): <https://incubator.wikimedia.org/wiki/Talk:Wp/tyv/%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: <https://incubator.wikimedia.org/w/index.php?title=Wp/tyv/%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.",1373897829,PHID-USER-7e4yonmruupxzg23swum,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,@MF-Warburg: Would you please tell us /what the hell/ is going on here? Your request was totally different from comment 6.,1373883715,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #5)
+> 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.",1373863960,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.)",1373863597,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Waiting for Reedy to do some on-server magic.,1373803738,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Any problems with this request?,1373788651,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Related URL: https://gerrit.wikimedia.org/r/68188 (Gerrit Change I7e9a1193500b7e09a29dab1d833c712db9453422),1371051069,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Related URL: https://gerrit.wikimedia.org/r/68188 (Gerrit Change I7e9a1193500b7e09a29dab1d833c712db9453422),1371051066,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,[I guess that's more of a site request than a language setup bug? Also changing priority.],1370682017,PHID-USER-hxjysvdvogekpjub3nd3,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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",1370622300,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ticw62p4dy4nr4dhvsrq,task_description,resolved
+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.,1402688105,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ticw62p4dy4nr4dhvsrq,task_subcomment,NA
+VisualEditor: Sometimes ignores changing a wikilink with an underscore to one with a space,"Is this a Parsoid issue?
+
+<p><a href=""./Main_page"" rel=""mw:WikiLink"" data-parsoid=""{&quot;a&quot;:{&quot;href&quot;:&quot;./Main_page&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;Main_page&quot;},&quot;stx&quot;:&quot;simple&quot;,&quot;dsr&quot;:[0,13,2,2]}"">Main page</a></p>
+
+serialises to
+
+[[Main_page]]
+
+whereas
+
+<p><a href=""./Main_page"" rel=""mw:WikiLink"">Main page</a></p>
+
+serialises to
+
+[[Main page]]
+
+which is what we want",1371168271,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ticw62p4dy4nr4dhvsrq,task_subcomment,NA
+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}",1370617380,PHID-USER-pts53ljtnbn3jhkllas6,PHID-TASK-7ci67c3uih3tuev7ghu3,task_description,resolved
+VisualEditor: Images' selection blocks can overlap the toolbar and prevent saving/etc.,The problem seems to be fixed in the current version. Thank you!,1373649909,PHID-USER-pts53ljtnbn3jhkllas6,PHID-TASK-7ci67c3uih3tuev7ghu3,task_subcomment,NA
+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}",1370620359,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7ci67c3uih3tuev7ghu3,task_subcomment,NA
+VisualEditor: Provide full grapheme cluster boundary detection,"Per Ed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370532360,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3qm4izjirylpzskf6mlm,task_description,resolved
+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.",1371423759,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3qm4izjirylpzskf6mlm,task_subcomment,NA
+VisualEditor: Provide full grapheme cluster boundary detection,Related change: https://gerrit.wikimedia.org/r/#/c/68864/,1371420521,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3qm4izjirylpzskf6mlm,task_subcomment,NA
+"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}",1370371920,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-inqexk3a4klng6im6ld7,task_description,resolved
+"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!",1395021940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1394910439,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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}",1394901722,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1394900638,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1394889750,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","Argh, yes, Kaldari got his comment in before mine. :-)",1371858127,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1371858070,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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. ***,1371857901,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1370806025,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?",Thanks for the catch!,1370539736,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.)",1370479896,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Since MediaWiki allows images that are clearly separated out, we should see if we can use `<figure>` and `<figcaption>`.  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}",1370315820,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-jjld4d5wjqxkuihohuzl,task_description,resolved
+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",1637266651,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1634321226,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1634244096,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1634243825,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1634059807,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1633537791,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633480989,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633480028,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633479766,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633476238,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633475767,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633475698,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633471391,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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?",1633450464,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633448058,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633448046,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633447156,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633446229,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Deployment to Meta broke global user pages appearing on wikis that still use the legacy `<div>`-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.",1633422992,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Deployment to Meta broke global user pages appearing on wikis that still use the legacy `<div>`-based output, see T292498.
+",1633422717,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633046282,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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] <thcipriani@deploy1002> Synchronized wmf-config/InitialiseSettings.php: Config: [[gerrit:724861|Disable legacy media dom on a few more wikis (T51097)]] (duration: 01m 08s)",1633026053,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633025810,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1632960717,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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} )",1632754354,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 ?",1632753845,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1631051594,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1631051550,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1631050915,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1631050878,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1630606208,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 ]]),1630083005,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 ]]),1630082994,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1630082949,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629928616,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1629924997,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1629924192,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1629924129,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1629923807,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629923159,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,I also see all the VE JS being loaded (with debug=true).. that's not normal.... ,1629922678,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629921914,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629919335,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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] <urbanecm@deploy1002> Synchronized wmf-config/InitialiseSettings.php: e6df0803e4eaca91bd725bcd376b260b97917de3: Disable legacy media dom on a few more wikis (T51097) (duration: 01m 05s)",1629915383,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629914814,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629844175,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.
+",1628004330,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1627999846,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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. ",1627999455,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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. ",1627999353,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]
+```
+```
+<figure class=""mw-halign-right djtest"" typeof=""mw:Image/Thumb""><a href=""/wiki/File:Onion_diagram.svg"" title=""""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/300px-Onion_diagram.svg.png"" decoding=""async"" width=""300"" height=""197"" srcset=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/450px-Onion_diagram.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/600px-Onion_diagram.svg.png 2x"" data-file-width=""875"" data-file-height=""575""></a><figcaption>In this example onion, we test image placement.</figcaption></figure>
+```
+
+```
+<div class=""thumb tright""><div class=""thumbinner"" style=""width:302px;""><a href=""/wiki/File:Onion_diagram.svg"" class=""image"" title=""""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/300px-Onion_diagram.svg.png"" decoding=""async"" width=""300"" height=""197"" class=""djtest thumbimage"" srcset=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/450px-Onion_diagram.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/600px-Onion_diagram.svg.png 2x"" data-file-width=""875"" data-file-height=""575""></a>  <div class=""thumbcaption""><div class=""magnify""><a href=""/wiki/File:Onion_diagram.svg"" class=""internal"" title=""Enlarge""></a></div>In this example onion, we test image placement.</div></div></div>
+```",1627999209,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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,
+
+```
+<figure class=""mw-halign-right"" typeof=""mw:Image/Thumb""><a href=""/wiki/File:Onion_diagram.svg""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/300px-Onion_diagram.svg.png"" decoding=""async"" width=""300"" height=""197"" srcset=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/450px-Onion_diagram.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/600px-Onion_diagram.svg.png 2x"" data-file-width=""875"" data-file-height=""575""></a><figcaption>In this example onion, we test image placement.</figcaption></figure>
+```
+
+However, on mediawikiwiki, after similarly purging we get on https://www.mediawiki.org/wiki/Parsoid
+
+```
+<div class=""thumb tright""><div class=""thumbinner"" style=""width:514px;""><a href=""/wiki/File:Parsoid_HTML-RDFa_content_model.svg"" class=""image""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/2/2e/Parsoid_HTML-RDFa_content_model.svg/512px-Parsoid_HTML-RDFa_content_model.svg.png"" decoding=""async"" width=""512"" height=""362"" class=""thumbimage"" data-file-width=""512"" data-file-height=""362""></a>  <div class=""thumbcaption"">Artist's impression of the Parsoid HTML5 + RDFa wiki runtime</div></div></div>
+```",1625002036,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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] <urbanecm@deploy1002> Synchronized wmf-config/InitialiseSettings.php: 5ec855d14b31a9392274c2bfe2e21e2ad44986bc: Enable Parsoid inspired media structure on test wikis (T51097) (duration: 00m 59s)",1624921541,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1624921358,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1624655511,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1624580053,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Change 701449 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] Add <figure> to the never suppressing group in BlockLevelPass%%%
+https://gerrit.wikimedia.org/r/701449",1624563463,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Change 701449 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[mediawiki/core@master] Add <figure> to the never suppressing group in BlockLevelPass%%%
+https://gerrit.wikimedia.org/r/701449",1624562043,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,https://gerrit.wikimedia.org/r/c/507512 is the only open patch remaining.,1617354427,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1610568452,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1608245687,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1608047326,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"From an accessibility standpoint, there may be reasons to emit a descriptive `<figcaption>` 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) `<p>` 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.)",1608046662,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"From an accessibility standpoint, there may be reasons to emit a descriptive `<figcaption>` 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) `<p>` 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.",1608046292,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1608045476,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1608002858,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1608002549,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1608000898,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607994875,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.
+",1607984896,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.
+",1607984532,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.
+",1607984390,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1607983473,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607716556,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607713852,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607705268,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607629897,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1556663538,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1556663464,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Change 505645 **merged** by jenkins-bot:
+[mediawiki/core@master] Allow <figure-inline> attributes through Sanitizer
+
+[[https://gerrit.wikimedia.org/r/505645]]",1556305851,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 <figure-inline> attributes through Sanitizer
+
+[[https://gerrit.wikimedia.org/r/505645]]",1555952830,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1511202815,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 <figure> 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? :))",1483413867,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 <figure> 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?
+",1483413836,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,@niedzielski: cool.,1449265385,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1449261814,PHID-USER-6tlavgtsosjuvizsej53,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1449198930,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Thanks, @niedzielski!",1449198765,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1449194986,PHID-USER-6tlavgtsosjuvizsej53,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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}
+
+ ",1449179179,PHID-USER-6tlavgtsosjuvizsej53,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1437515671,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1437392905,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.,1436994247,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 `<figure>` 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 `<div>` 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.",1435616576,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 `<figure>` 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 `<div>` 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.",1435616550,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1427474703,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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)?",1427411748,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1427275316,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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).",1427274219,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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!),1427250080,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]
+",1426227143,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]
+",1426227102,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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, <figure> and <figcaption> could be thrown in around the existing <div>s and <span>s without changing the styles, assuming there's no default styles that override stuff.",1380740509,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+VisualEditor: Reference lists should update more intelligently (i.e. less often),"Currently a reference list (<references /> 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.",1370299680,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ebn2j76ougc2mnfqb4fp,task_description,open
+Enable VisualEditor alpha on all Wikipedias,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1370286120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nlxbzrcehkp3h36untox,task_description,resolved
+Enable VisualEditor alpha on all Wikipedias,Done on 2013-06-06.,1370741034,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nlxbzrcehkp3h36untox,task_subcomment,NA
+Enable VisualEditor alpha on all Wikipedias,Related URL: https://gerrit.wikimedia.org/r/67151 (Gerrit Change I98eb9f4979ae8d1dc2fdca4d812feaee28672444),1370466138,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nlxbzrcehkp3h36untox,task_subcomment,NA
+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",1370181480,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rhsntkwc7ofl6qzz7kt4,task_description,resolved
+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.",1372809190,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rhsntkwc7ofl6qzz7kt4,task_subcomment,NA
+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.",1370851448,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rhsntkwc7ofl6qzz7kt4,task_subcomment,NA
+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",1370056740,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_description,resolved
+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.,1370467182,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+Piping used unnecessarily when modifying an existing link,https://gerrit.wikimedia.org/r/66880 (Gerrit Change I6abef05522192f667d483b4eb4e05de771496c28) | change APPROVED and MERGED [by jenkins-bot],1370467094,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+Piping used unnecessarily when modifying an existing link,Related URL: https://gerrit.wikimedia.org/r/66880 (Gerrit Change I6abef05522192f667d483b4eb4e05de771496c28),1370297438,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+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.",1370295580,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+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
+<a rel='mw:WikiLink' href='./Foo' data-parsoid='{""a"":{""href"":""./Foo""},""sa"":{""href"":""Foo""},""stx"":""simple""}'>Foo</a>
+<a rel=""mw:WikiLink"" href=""./Foo"" data-parsoid='{""a"":{""href"":""./Foo""},""sa"":{""href"":""Foo""},""stx"":""piped""}'>Foo</a>
+[subbu@earth lib] node parse --html2wt < /tmp/x
+[[Foo]]
+[[Foo|Foo]]",1370294863,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+"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",1369958460,PHID-USER-kc6qx3zohjybu3nzffu3,PHID-TASK-n3tckyz3ypiasbv7mmov,task_description,resolved
+"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).",1393380862,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",Is there anything left to do here?,1390957000,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1378356950,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1378325288,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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.",1378325065,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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 ?",1376398189,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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.",1376398041,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",Now fixed and deployed.,1375423076,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375414268,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375401594,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375397553,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375395744,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375395639,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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.",1375394378,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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 ),1374948629,PHID-USER-myojicphhrv5eiqtoq52,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1374804903,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1374515509,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",--> VisualEditor,1370441741,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+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",1369942140,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-3ovbcuxkngbjxrroevib,task_description,resolved
+VisualEditor: Formatting styles drop down menu rendered behind the page title,*** Bug 49430 has been marked as a duplicate of this bug. ***,1370970446,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ovbcuxkngbjxrroevib,task_subcomment,NA
+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.,1370632871,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ovbcuxkngbjxrroevib,task_subcomment,NA
+VisualEditor: MWTemplateDialog should visually distinguish between wikitext and template name,"Screenshot while editing template with wikitext-generated target
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F11029}",1369920600,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-caprohhe57u5cvvih5r4,task_description,duplicate
+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: <foo>"" rather than just ""<foo>""? Making the name italics?",1369926881,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-caprohhe57u5cvvih5r4,task_subcomment,NA
+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",1369888320,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2qamjq3crlikvr3nahtr,task_description,resolved
+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.,1372007590,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2qamjq3crlikvr3nahtr,task_subcomment,NA
+VisualEditor: Cut-Paste of paragraphs seems broken in Firefox,Firefox 21.0,1370319799,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-2qamjq3crlikvr3nahtr,task_subcomment,NA
+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.",1369904030,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2qamjq3crlikvr3nahtr,task_subcomment,NA
+VisualEditor: Make ve.dm.Transaction chainable,"tx push
+tx push
+tx push
+tx push
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369777440,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lsb2vshfs5s363qn5xmf,task_description,declined
+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",1369760400,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mmm6poefxi4xoohquyi4,task_description,resolved
+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]]",1487999288,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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]]
+",1487969442,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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 #.",1439831900,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,This has been deployed.,1418855804,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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]]",1418149485,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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",1417716645,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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",1414795698,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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.,1411654695,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1374161731,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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,1374106464,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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.",1374075574,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1374074905,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1373852602,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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,1373646156,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1373646127,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1373590970,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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],1372934117,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1372104211,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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.",1371782235,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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}",1369744440,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_description,resolved
+Parsoid should support <translate> and <tvar> 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.",1451432369,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Change 261293 merged by jenkins-bot:
+T50891: Register <translate> and <tvar> natively
+
+[[https://gerrit.wikimedia.org/r/261293]]",1451423865,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Change 261293 had a related patch set uploaded (by Arlolra):
+T50891: Register <translate> and <tvar> natively
+
+[[https://gerrit.wikimedia.org/r/261293]]
+",1451345650,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1449004296,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,Any update on this?,1448940120,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Since <translate> 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 <translate> 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.",1422567418,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> 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.,1422482506,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> 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.",1422112321,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1412577526,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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*.",1399802210,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1399802137,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,No patch any more. :-(,1399715908,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1397663477,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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
+> > <translate> 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:
+<h2><span class=""mw-headline"" id=""Culture"">Culture</span><mw:editsection page=""Pupu"" section=""1"">Culture</mw:editsection></h2>
+
+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?",1382781712,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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
+> <translate> 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.",1382742193,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,Editing translatable pages via API seems to work now.,1382609272,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1382609061,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Issues I have found:
+
+* [MAJOR] Disabling edit section links does not work for headings inside <translate> 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.",1382608843,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1382608576,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 = '~<tvar\|([^>]+)>(.*?)</>~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.",1382602468,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"**gmaruzz** wrote:
+
+bump",1382525422,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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=<translate>foo</translate> works and does not crash.
+
+https://meta.wikimedia.org/w/api.php?action=parse&text=<translate><!--T:1-->foo</translate> 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.",1382026260,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1382022809,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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?",1381997259,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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?",1381334518,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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).",1381334222,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> and <tvar> 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 <translate> and <tvar> relies on), and that will bomb.
+
+One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",1381332394,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> and <tvar> 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.",1381331649,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.,1381311581,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 ""<translate> and <tvar>""",1381308196,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"That patch won't work well with Parsoid, see the comment in the patch set.",1381173268,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,I don't deserve the credit for Niklas's fix. :-),1381161087,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1380976648,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1380973744,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,I think I already did it yesterday.,1380972312,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1380903233,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1380870838,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1380324098,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1378773198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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?",1378772376,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Niklas: If VE has to support editing for <translate>, <tvar>, 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.",1378754413,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.,1378751046,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1378750854,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,Ping.,1377214396,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.,1375385299,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1375380363,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,@Niklas are there issues with registering them?,1375380132,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,*** Bug 52408 has been marked as a duplicate of this bug. ***,1375378489,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate>, <tvar>, <language> 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.",1375378361,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,<translate> and <tvar> are not a normal extension tags. Please explain why I should register them.,1369809699,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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/<ext-name-here> 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.",1369765885,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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/<ext-name-here> type. All other unknown tags are pass through as plain text.
+
+The problem is that mediawiki does not report <translate> 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 <translate> as a registered extension?",1369761569,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> 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?",1369745248,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+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",1369733100,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_description,declined
+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.",1551737186,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_subcomment,NA
+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'.",1404778634,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_subcomment,NA
+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
+} );",1404777075,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_subcomment,NA
+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.",1369734288,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_subcomment,NA
+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",1369598340,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-cxhnj4waa436ovh4o7lz,task_description,resolved
+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.",1372007435,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cxhnj4waa436ovh4o7lz,task_subcomment,NA
+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 </small> 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",1369561740,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-c3wc4a6vunygqboimdkx,task_description,resolved
+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.",1642380960,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-c3wc4a6vunygqboimdkx,task_subcomment,NA
+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.",1371986974,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-c3wc4a6vunygqboimdkx,task_subcomment,NA
+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 <b> tags. Currently it fails compare custom attributes like ""style"" when attempting to merge equal annotation sequences.",1371986731,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-c3wc4a6vunygqboimdkx,task_subcomment,NA
+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.,1371986436,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-c3wc4a6vunygqboimdkx,task_subcomment,NA
+VisualEditor: Write test cases for ElementLinearData#getAnnotationIndexesFromOffset,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369560000,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7lzwyjbh5q62jpz2njvq,task_description,open
+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",1369423680,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-ftjpfhlr3dsluwcrrpaa,task_description,resolved
+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.,1372007371,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ftjpfhlr3dsluwcrrpaa,task_subcomment,NA
+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}",1369425726,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-ftjpfhlr3dsluwcrrpaa,task_subcomment,NA
+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",1369411380,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-jzom4aa22nn3mtwtm74t,task_description,resolved
+VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),Now tracked in #VisualEditor-MediaWiki-Links instead.,1422402760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),*** Bug 57716 has been marked as a duplicate of this bug. ***,1395197341,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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.,1378765753,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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.""",1375961000,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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]].",1375212875,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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)",1375181899,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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),1373539718,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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.",1371118580,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+"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 <template> tags or any of the special attributes/types found on http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec
+
+If Parsoid doesn't detect these and escape/handle them somehow, Parsoid will mislead clients like VisualEditor and/or incorrectly serialize them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369392240,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-e53ehyegovylp4gigsvo,task_description,open
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","One more thing that would be good to fix:
+
+Currently, the tokenizer unconditionally escapes typeof and about attributes to data-x-typeof and data-x-about. But, if RDFa attrs from wikitext will also get escaped in this manner. Not sure if RDFa is actually used in wikitext, but that support does exist in MW. So, the escaping could be refined to leave alone any typeof and about attrs that wont confuse Parsoid and clients.
+
+Related FIXME comments from the sanitizer (ext.core.Sanitizer.js) from https://gerrit.wikimedia.org/r/#/c/81569/ that I am pasting here:
+```
+// SSS FIXME: There is a test in mediawiki.environment.js that doles out
+// and tests about ids. There are probably some tests in mediawiki.Util.js
+// as well. We should move all these kind of tests somewhere else.
+----
+// Bypass RDFa/whitelisting checks for Parsoid-inserted attrs
+// Safe to do since the tokenizer renames about/typeof attrs.
+// unconditionally. FIXME: The escaping solution in tokenizer
+// maybe aggressive. There is no need to escape typeof strings
+// that or about ids that don't resemble Parsoid types/about ids.
+```
+
+Any fix made here should also verify that the sanitization code in sanitizeTagAttrs properly strips dangerous values from unescaped typeofs even when Parsoid updates them with parsoid typeofs.
+
+```
+Ex: <tag typeof=""dangerous-text"">..</tag> gets updated by Parsoid parser to <tag typeof=""mw:ParsoidTypeof dangerous-text"">..</tag> which should then be handled by the sanitizer to yield <tag typeof=""mw:ParsoidTypeof"">...</tag>
+```",1421187810,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","One more thing that would be good to fix:
+
+Currently, the tokenizer unconditionally escapes typeof and about attributes to data-x-typeof and data-x-about. But, if RDFa attrs from wikitext will also get escaped in this manner. Not sure if RDFa is actually used in wikitext, but that support does exist in MW. So, the escaping could be refined to leave alone any typeof and about attrs that wont confuse Parsoid and clients.
+
+Related FIXME comments from the sanitizer (ext.core.Sanitizer.js) from https://gerrit.wikimedia.org/r/#/c/81569/ that I am pasting here:
+
+----
+// SSS FIXME: There is a test in mediawiki.environment.js that doles out
+// and tests about ids. There are probably some tests in mediawiki.Util.js
+// as well. We should move all these kind of tests somewhere else.
+----
+// Bypass RDFa/whitelisting checks for Parsoid-inserted attrs
+// Safe to do since the tokenizer renames about/typeof attrs.
+// unconditionally. FIXME: The escaping solution in tokenizer
+// maybe aggressive. There is no need to escape typeof strings
+// that or about ids that don't resemble Parsoid types/about ids.
+----
+
+Any fix made here should also verify that the sanitization code in sanitizeTagAttrs properly strips dangerous values from unescaped typeofs even when Parsoid updates them with parsoid typeofs.
+
+Ex: <tag typeof=""dangerous-text"">..</tag> gets updated by Parsoid parser to <tag typeof=""mw:ParsoidTypeof dangerous-text"">..</tag> which should then be handled by the sanitizer to yield <tag typeof=""mw:ParsoidTypeof"">...</tag>",1378248584,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","Patch landed as suggested in comment 5. However, Subbu mentioned that, ""we still need to deal with complexity that templates bring.""
+
+Ex: <div {{echo|about}}=""foo"">bar</div>",1375117004,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","Change 74586 merged by jenkins-bot:
+Protect Parsoid-generated attributes.
+
+https://gerrit.wikimedia.org/r/74586",1374946962,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","Or we could write a DOM postprocessor stage that was a bit smarter about which RDFa it unwrapped.  ie, it would unwrap the first example from comment 5, but not the final example there, since it would be able to see that there's parsoid RDFa inside the div which would be broken.  Or other options.",1374529924,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","If we do go that route, the fixup for rendering would have to be in client-side JS since we may not use different cached content for editing vs rendering -- or so it seems to me at this time without any sense of how user RDFa markup will need to be supported in MW content.",1374529662,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","[Discussed this on IRC with subbu]
+
+To support case 3 from comment 1 and 2, rather than *strip* the attributes, I suggest encapsulating them instead.  For example, if the user authors:
+
+<div about=""http://dbpedia.org/resource/Albert_Einstein"" typeof=""foaf:Person"">
+  <span property=""foaf:name"">Albert Einstein</span>
+  <span property=""foaf:givenName"">Albert</span>
+</div>
+
+..instead of stripping the RDFa, we're just going to rename the attributes, to:
+
+<div data-user-about=""http://dbpedia.org/resource/Albert_Einstein"" data-user-typeof=""foaf:Person"">
+  <span data-user-property=""foaf:name"">Albert Einstein</span>
+  <span data-user-property=""foaf:givenName"">Albert</span>
+</div>
+
+That ensures that the user content is safe for Parsoid and VE to manipulate.  In the future we can re-enable the RDFa in the output with a DOM post-processing (""render"") pass.  For example, the user content:
+
+<div about=""http://dbpedia.org/resource/Albert_Einstein"" typeof=""foaf:Person"">
+{{Albert Einstein}}
+</div>
+
+might have all sorts of Parsoid RDFa markup inside the {{Albert Einstein}} expansion, which the about=""http://dbpedia.org/resource/Albert_Einstein"" attribute would screw up the context for.  But for rendering to the web, the Parsoid cruft could be elided and the user's RDFa markup unwrapped.",1374529246,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","Change 74586 had a related patch set uploaded by Arlolra:
+Protect Parsoid-generated attributes.
+
+https://gerrit.wikimedia.org/r/74586",1374213999,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.",[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934056,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","1) Is not an issue, as prefix is  not allowed in the PHP sanitizer (and not in our sanitizer either).
+
+2) Is something for later. The risk here is mainly crashes during serialization.
+
+3) Should be supported. We only want to protect our own values where necessary. The typeof attribute for example is multi-valued, so we only need to strip mw:-prefixed user-supplied values. The about attribute on the other hand is single-valued, so we need to override user-supplied values unconditionally where necessary.",1371511977,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","There are three interconnected issues:
+1)
+  <span prefix=""mw: http://evil.bad"">
+is valid wikitext, which would create malformed Parsoid DOM.  We should sanitize the wikitext (but that has to happen *before* we create the DOM, since otherwise we can't tell which prefix attributes are good and which are evil.)
+
+2) VE needs to prevent users from authoring content which sets prefix attributes, etc.  Currently it does so, but it would be nice to make Parsoid more robust against malformed DOM, and/or to add layers of protection so that front ends aren't solely responsible for sanitizing user input.
+
+3) Longer term we should probably think about use cases where the user wants to deliberately author RDFa markup on their content, and ensure that they are able to do so in a safe way.
+
+This bug is primarily about #1 (the short term issue) and I'll tackle it tomorrow.",1371511478,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","On my user page https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29 and now on a test page https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29/VE_bugs every time I try to add a new section VE goes haywire
+
+1. Edit (with VE)
+2. Click at start of first heading (""welcomecreation..."")
+3. Press Enter, it prepends new heading (good)
+4. Press up arrow to move up to this new blank heading.
+5. Start typing the heading, e.g. press 'X'
+6. That was wrong, so press Backspace (or left arrow)
+
+Result:
+The text of the heading underneath leaps above the new heading, joining text above it.
+I can edit other parts of the document, but whenever I return to my new heading to add or backspace, the caret jumps elsewhere.
+If I undo enough times, VE undoes to a state where the new header displays below the existing header. The document looks different to what it did before, but [Review and save] is grayed out.
+
+I created a new document https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29/VE_bugs and similar stuff happens in that.
+
+This is in Firefox 21 on Ubuntu, and mediawiki.org's VE as of today.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369264200,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-pds66u5f24d37usiicgj,task_description,resolved
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one",This should now be fixed; we will push this to production this afternoon.,1372370158,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","Change 70864 merged by jenkins-bot:
+Don't advance cursor when adding new line at start of node
+
+https://gerrit.wikimedia.org/r/70864",1372368223,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","Change 70918 merged by jenkins-bot:
+If cursor is obscured by toolbar, on keypress scroll to cursor.
+
+https://gerrit.wikimedia.org/r/70918",1372368220,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","Change 70918 had a related patch set uploaded by Robmoen:
+If cursor is obscured by toolbar, on keypress scroll to cursor.
+
+https://gerrit.wikimedia.org/r/70918",1372366669,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","Change 70864 had a related patch set uploaded by Robmoen:
+Don't advance cursor when adding new line at start of node
+
+https://gerrit.wikimedia.org/r/70864",1372359928,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","(In reply to comment #5)
+> Sounds good, though I note it's different than e.g. pressing Enter at the
+> start of the first of a set of bullet points, which adds another bullet rather
+> than a plain paragraph. A foolish consistency is the Hobnobs of little minds :)
+
+Yeah, I've been wondering whether to make these consistent for a little bit.",1371520609,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","(In reply to comment #4)
+> (In reply to comment #3)
+> > * If you press Enter with the caret at start of heading, you get a plain
+> > paragraph before (maybe OK but not what I'd expect and not how most WYSIWYG
+> > editors work)
+> 
+> This is intentional - if you have header 1\nheader 2\nheader 3\n and click
+> before header 3 and press return, you should be able to type content
+> (paragraph) by default.
+
+Sounds good, though I note it's different than e.g. pressing Enter at the start of the first of a set of bullet points, which adds another bullet rather than a plain paragraph. A foolish consistency is the Hobnobs of little minds :)",1371520249,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","(In reply to comment #3)
+> These days the behavior on mediwiki.org (with Firefox 21.0 Ubuntu 13.04) is
+> different and a little better.
+> * If you press Enter with the caret at start of heading, you get a plain
+> paragraph before (maybe OK but not what I'd expect and not how most WYSIWYG
+> editors work)
+
+This is intentional - if you have header 1\nheader 2\nheader 3\n and click before header 3 and press return, you should be able to type content (paragraph) by default. WYSIWYG editors often get this wrong, thinking that context is the most important thing, because they don't know what style ""normal"" content is. We do, and so we should do this right. (Also, VE isn't intending to be a WYSIWYG editor, just a visual one that is more and WYSIWYM editor at times.)
+
+> * The caret moves between the first and second character of the heading
+> (definitely wrong).
+
+Yeah, sorry about that; we should get that fixed soon.",1371504819,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","These days the behavior on mediwiki.org (with Firefox 21.0 Ubuntu 13.04) is different and a little better.
+* If you press Enter with the caret at start of heading, you get a plain paragraph before (maybe OK but not what I'd expect and not how most WYSIWYG editors work)
+* The caret moves between the first and second character of the heading (definitely wrong).
+But the document doesn't get out of order, your typing always appears at the caret, and what you see is what is saved. Progress!",1371501393,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","**brassratgirl** wrote:
+
+I'm getting a similar bug while trying to edit a userpage subpage, with the addition that it's blanking out the existing text. See https://en.wikipedia.org/wiki/User:Phoebe/chopo
+
+1) edit existing text, all is fine. 
+2) move cursor below existing paragraph, attempt to type new heading
+3) cursor jumps to above existing paragraph, types up there
+4) this results in uneditable blank spaces 
+5) and, on save, all text below blank spaces is gone. 
+
+My conclusion is that editing user pages is, for whatever reason, totally haywire. I have screenshots if needed. 
+
+Firefox 20.0 on Ubuntu 12.04",1369610854,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","In Chromium (25.0.1364.160 Ubuntu 13.04) not logged in, the same step 3 adds blank line above (not styled as a heading) and moves the caret to the second character in the existing heading.",1369264433,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,"On wikis where certain ""topicons"" are moved out of the mw-content-text wrapper into the root of #content the VisualEditor toolbar shows a weird blank space.
+
+The icons in question are invisible due to float overlap, but they do push down the toolbar and occupying space to the right of the ""Save and review"" button thus pushing it and the rest of ve-ui-toolbar-actions to the left.
+
+To reproduce this situation, run the following one or more times:
+
+    $('#content').prepend(
+        '<div class=""mw-topicon"" style=""display: block; width: 20px; height: 20px; background: pink; float: right; margin-left: 3px;"">x</div>'
+    );
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369263840,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nmn7dlmg7l34754u4bwb,task_description,resolved
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,Related URL: https://gerrit.wikimedia.org/r/64989 (Gerrit Change Ic5f73ac1eb8c41b891dd1c67b71795cb6c456141),1369264080,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nmn7dlmg7l34754u4bwb,task_subcomment,NA
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,"Created attachment 12375
+What it looks like with clear:both patch applied
+
+The icons become visible again and the actions toolbar (right hand side of the toolbar) is no longer pushed to the left but flush to the right again.
+
+**Attached**: {F10554}",1369264016,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nmn7dlmg7l34754u4bwb,task_subcomment,NA
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,"Created attachment 12374
+Current misalignment when there are extra elements in #content
+
+Such as the case currently on https://de.wikipedia.org/wiki/Berlin
+
+**Attached**: {F10553}",1369263963,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nmn7dlmg7l34754u4bwb,task_subcomment,NA
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,"Created attachment 12373
+What the toolbar usually looks like
+
+Note absence of space between the Vector tabs and the toolbar, and the Save button is flush to the right.
+
+**Attached**: {F10552}",1369263925,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nmn7dlmg7l34754u4bwb,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"If you have some text with an annotation (e.g. bold, italics or a link) and copy in some text, the annotation is closed off, the text is insert as plain text, and then the annotation is restarted.
+
+I think users will expect ""paste as current style"" over ""paste as plain text"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369247880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ezht24x5cf4eytaekvqk,task_description,resolved
+VisualEditor: Paste of content does not use the context's annotation,"This seems to work as expected these days. I just tried pasting various annotated things into various other things, and everything behaves fine, with the annotations being merged. 
+
+https://en.wikipedia.org/w/index.php?title=User:Matma_Rex/sandbox&diff=773983701&oldid=773982287
+{F7268038}
+
+(Although in the meantime I discovered we're //too// good at this, merging some annotations that don't make sense, see {T162278}.)",1491408734,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"I definitely expect that text pasted into the middle of a link will still be part of the link.  `[[Link|Li]]HardToType[[Link|nk]]` is never what I want, and if you end up with that, it's hard to repair (unlike a missing or extra bit of bold text).  Since the {T130735} in Safari, then ""just (magically know about and remember to) use plain-paste"" isn't a viable solution.",1458752469,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,*** Bug 69653 has been marked as a duplicate of this bug. ***,1408272633,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,Normal paste (rich paste) should preserve the formatting of the pasted content (even if that means plain). Plain text paste should take the formatting of the target.,1381156824,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"erm, yes. Sorry.",1374776898,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"(In reply to comment #3)
+> An editor at the English Wikipedia comments that the ability to copy and
+> paste
+> a link is "" definitely not an [sic] luxury feature but core functionality.""
+> 
+> I am inclined to agree.
+
+That's presumably meant for bug 33105 which is about copying and pasting rich content, rather than this one?",1374775928,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"An editor at the English Wikipedia comments that the ability to copy and paste a link is "" definitely not an [sic] luxury feature but core functionality.""
+
+I am inclined to agree.",1374767136,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"LibreOffice uses additive annotations, so pasting italic text into bold text results in bold+italic text. Google drive uses our current functionality.",1369294390,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,*** Bug 48159 has been marked as a duplicate of this bug. ***,1369247921,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Clicking Notices button or closing its dialog scrolls user back to the top,"Whenever you're scrolled down in a document and close or re-open the Notices flyout, the user is brought back to the top of the page (instead of staying where they are, like any other toolbar button would).
+
+The toolbar floats and follows the user as they view the document, it is expected that interacting with it does not change the scroll offset. Most buttons abide by this except for Notices.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369144860,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7jfh3i424pezp3um3zzy,task_description,resolved
+VisualEditor: Clicking Notices button or closing its dialog scrolls user back to the top,This is now fixed.,1370972881,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7jfh3i424pezp3um3zzy,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"The newsletter update states that Visual Editor is now functioning in the content namespaces at MW, which includes the extension: and manual: namespaces (and it does).  That said, the default text for ""MediaWiki:Visualeditor-preference-enable"" just states user and main at that wiki. I am presuming that this is a WikimediaMessages update somewhere
+
+As a temporary measure I have created [[mw:MediaWiki:Visualeditor-preference-enable]] that mentions the extra two namespace.
+
+As a note the mention of {{MediaWiki:Visualeditor-extensionnamespacepagelink}} and {{MediaWiki:Visualeditor-manualnamespacepagelink}} failed, so I didn't link, and we will need to look to how these extra namespaces are going to be linked, and documented.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369100100,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-q322vvsm62gyx2idxtx2,task_description,resolved
+Mediawikiwiki: Make VisualEditor a hidden preference,"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",1374826591,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"Change 73565 had a related patch set uploaded by Helder.wiki:
+(bug 50929) Remove 'visualeditor-enable' from $wgHiddenPrefs
+
+https://gerrit.wikimedia.org/r/73565",1374499697,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"Then someone opened Bug 50929 - User preference to disable VisualEditor
+
+The related change is  https://gerrit.wikimedia.org/r/#/c/73565/
+
+
+That effectively would reopen this bug 48666.",1374499317,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"(In reply to comment #8)
+> my intention was not to offend or attack, it was to draw attention that, to
+> the best of my understanding, hiding the user option did not actually address
+> the actual bug.
+
+The 'actual' bug was, effectively, that ""the temporary description of a temporary configuration option does not automatically expand based on a different configuration variable's setting"".
+
+However, the cause for complaint was ""the temporary description of a temporary configuration option on MW.org is wrong and confusing"", you are correct.
+
+> i think that bug 51411 you created is perfect, and once it's fixed/addressed,
+> everything will be fine.
+
+It's exceedingly unlikely to be addressed, because (a) programmatic writing of human-readable descriptions is very delicate and not something we generally do, and (b) as we have said a great many times, this is about a configuration variable that exists purely for the duration of the alpha, to provide a way to ""opt in"". Availability of VE is a system-level configuration, not a user-level preference. By the time the software is actually marked for release by anyone outside WMF (when we remove the ""here be dragons"" labels), the underlying issue will be moot.",1373987046,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"my intention was not to offend or attack, it was to draw attention that, to the best of my understanding, hiding the user option did not actually address the actual bug.
+
+i think that bug 51411 you created is perfect, and once it's fixed/addressed, everything will be fine.
+
+regarding the rewording of the synopsis: i am aware that it's common practice. actually, quite a few of the bugs i opened myself received this treatment. 
+in all the cases i can recall, the rewording was for the better. 
+my complain was not about the fact the synopsis was reworded, per se, but rather about the new description, which i do not think is a good one. 
+
+
+regarding my presumption: i am not sure if i understand your comment about this bug being specific to ""mediawiki.org"". 
+does this mean it's limited to wikimedia projects? if this is what you mean, i do not think you are correct. 
+this issue (the original one, that is) pertains to any wiki that uses the mediawiki software with visualeditor (new synopsis and your fix not withstanding).
+
+peace.",1373986460,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"(In reply to comment #6)
+> (In reply to comment #2)
+> > Simplest solution to this problem. :-)
+> 
+> an excellent case where ""simplest"" is very far from ""correct"" or ""best"".
+
+I disagree.
+
+> in addition to being a bad solution, this change only affects enwiki,
+
+Not true.
+
+> while the (original) bug is generic to all projects that install VE (and
+> even non-projects, i.e., ""3rd party"" wikis).
+
+The message is over-rideable, which is an entirely-adequate solution for most third parties. The initial request was, in my opinion, asking for a solution that didn't require a local over-ride, and met the intent of the team anyway (as part of removing VisualEditor as a local user preference, which was temporarily implemented for the opt-in alphas and is going away).
+
+> as a side, together with this wrong and bad solution, James Forrester also
+> changed the synopsis of the bug: from the original (""underlying text for
+> VisualEditor in preferences [editing] tab & variable names?""), to ""Make
+> VisualEditor a hidden preference"", i.e., instead of outlining the problem,
+> the bug synopsis now spells the ""solution"".
+
+This is perfectly standard practice here.
+ 
+> this is wrong on several levels: it creates the impression that the bug
+> originator (billinghurst) asked to hide the preference, which he didn't, of
+> course,
+
+Again, this is normal; comment 0 is the location to find what the originator wanted.
+
+> and it hides the actual problem from someone reading this bug - only
+> by digging in the history i was able to make sense of Comment #1, which looks
+> now completely disjoint from the bug synopsis.
+
+I'm sorry that you were confused.
+
+> wrong or bad solutions to problems is something that can and does happen in
+> every project. that's just life. 
+> changing the synopsis the way it was changed is not something that can or
+> should happen.
+
+I strongly disagree.
+
+> without digging too deeply, i'm going to revert the synopsis to the original
+> one, and reopen -
+
+Which I have reverted, and opened a new bug, bug 51411, for your concerns.
+
+> presuming the problem affects more then just enwiki
+
+Your presumption is wrong. Note that the title you over-ride explicitly mentioned ""Mediawikiwiki"" (i.e., MediaWiki.org).",1373933935,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"(In reply to comment #2)
+> Simplest solution to this problem. :-)
+
+an excellent case where ""simplest"" is very far from ""correct"" or ""best"".
+
+in addition to being a bad solution, this change only affects enwiki, while the (original) bug is generic to all projects that install VE (and even non-projects, i.e., ""3rd party"" wikis).
+
+as a side, together with this wrong and bad solution, James Forrester also changed the synopsis of the bug: from the original (""underlying text for Visual editor in preferences [editing] tab & variable names?""), to ""Make VisualEditor a hidden preference"", i.e., instead of outlining the problem, the bug synopsis now spells the ""solution"". 
+this is wrong on several levels: it creates the impression that the bug originator (billinghurst) asked to hide the preference, which he didn't, of course, and it hides the actual problem from someone reading this bug - only by digging in the history i was able to make sense of Comment #1, which looks now completely disjoint from the bug synopsis.
+
+wrong or bad solutions to problems is something that can and does happen in every project. that's just life. 
+changing the synopsis the way it was changed is not something that can or should happen.
+
+without digging too deeply, i'm going to revert the synopsis to the original one, and reopen - presuming the problem affects more then just enwiki, and also, with the hope that Bug 50929  (basically a request to undo this change) will be fixed soon.
+
+peace.",1373914200,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,Now done.,1372715431,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"Change 70652 merged by jenkins-bot:
+Make 'visualeditor-enable' pref hidden on wikis where VE is default
+
+https://gerrit.wikimedia.org/r/70652",1372714295,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,Related URL: https://gerrit.wikimedia.org/r/70652 (Gerrit Change Ica186b9374ddaa0f2f6b2a84e5dff851011b68a4),1372265133,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,Simplest solution to this problem. :-),1369159470,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"(In reply to comment #0)
+> The newsletter update states that Visual Editor is now functioning in the
+> content namespaces at MW, which includes the extension: and manual:
+> namespaces (and it does).  That said, the default text for
+> ""MediaWiki:Visualeditor-preference-enable"" just states user and main at that
+> wiki.
+
+It probably shouldn't default to saying only some namespaces and not changing when the wiki config adds it to other namespaces. Moving this bug to the VisualEditor product.",1369156791,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"{{foo}} -> Template:Foo
+{{:foo}} -> foo
+{{:user:Foo}} -> User:Krinkle
+{{Template:foo}} -> Template:Foo
+etc.
+
+VisualEditor needs the name of the page that ends up being transcluded by the template invocation.
+
+From conversation with Gabriel I gather that currently the entire tranclusion system (at least in production) is deferred to the PHP parser (including the invocation itself). Which means Parsoid is unable to determine it itself right now.
+
+Gabriel suggested Parsoid will provide the name the best it can for simple cases that don't dynamically construct the page name (e.g. not something like:
+ {{ {{getTemplateName|x=foo}} | bar }}
+).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369093620,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kjq6yunjdamvcihfi3va,task_description,resolved
+Parsoid: DOM for template objects should expose template name,https://gerrit.wikimedia.org/r/65622 (Gerrit Change I3b2fbf3b533b14680d2b881ac9fb43218d4f023a) | change APPROVED and MERGED [by jenkins-bot],1370460530,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"Latest proposal that is now pending review and merge (based on discussions on IRC).
+
+All transclusions now have ""mw:Transclusion"" typeof.
+
+data-mw.target.href will point to the template source page, if the template target is known statically.  Will not be set set if target is templated.
+
+data-mw.target.function will provide the name of the parser-function/magic-word, if the function target is known statically.  Will not be set otherwise.",1370456625,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,Related URL: https://gerrit.wikimedia.org/r/65622 (Gerrit Change I3b2fbf3b533b14680d2b881ac9fb43218d4f023a),1369577963,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"Given that transclusion targets can be dynamic ({{ {{echo|lc}}:FOO}} and such), it wont be possible to always provide a statically determined tpl/pf target.  In the general case, the user shouldn't be editing parameters for these dynamic cases without knowing that the tpl. target is specific to the current editing session and arbitrary editing of the parameters might break the transclusion in other scenarios (day-of-week or month-of-year based selection of tpl targets).
+
+So, if we cannot always provide the template or parser function target, it seems we shouldn't add that to the typeof field and leave the typeof as: ""mw:Object/Transclusion/Template"" or ""mw:Object/Transclusion/ParserFunction"" and rely on the data-mw.target json property to communicate info about the target (fully resolved url, if static OR html with transclusion wrappers, if templated).",1369480864,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"https://en.wikipedia.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=functionhooks doesn't expose the flag.
+
+We were thinking of replacing mw:Object/Template with mw:Object/Transclusion to make it clear that the object being annotated is a transclusion.  We want to retain a Transclusion type so all transclusions can be recognized for those cases where you dont need to distinguish between types.  But, I suppose we could make this: ""mw:Object/Transclusion/Template"" or ""mw:Object/Tranclusion/ParserFunction"".  Right now, the target is not part of this, since this is a type but we are being inconsistent since extensions provide the target name as part of the typeof.  So, we should probably make all those typeofs consistent in some way.
+
+Since this is not necessary for July, let us take a bit more time to work through these (and any other) details rather than make a quick fix.",1369475889,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"(In reply to comment #7)
+> We were just looking at the wiki config to see if we can recognize something
+> as
+> a parser function (instead of a template) and ran into trouble:
+> 
+> * Looks like parser functions usage comes in 2 flavours: (a) with the
+> #-prefix:
+> ex: {{#if ..}}, etc. (b) without the #-prefix: ex: {{lc:...}}
+> * config.functionhooks provides a list of parser functions, but that list
+> doesn't distinguish between (a) and (b) above.  So, the functionhooks list
+> has
+> an entry for ""lc"" and an entry of ""if"" (not #if).
+> 
+This is controlled by the SFH_NO_HASH flag in CoreParserFunctions.php. Is this flag not exposed in config.functionhooks?
+
+> If
+> knowing that something is a parser function is essential for VE, then we
+> could
+> implement this check and maybe add a flag in data-mw or add some other way of
+> marking up a parser function.  data-mw.target.isPF = true possibly?
+It's not essential for July, but it's required in order to be able to support Wikidata editing. For that purpose, we'd like for parserfunctions to be marked as something like typeof=""mw:Object/ParserFunction/#if"" , as opposed as a template with a special data-mw bit (we could deal with the latter too, but the former would be much more convenient).",1369473754,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"We were just looking at the wiki config to see if we can recognize something as a parser function (instead of a template) and ran into trouble:
+
+* Looks like parser functions usage comes in 2 flavours: (a) with the #-prefix: ex: {{#if ..}}, etc. (b) without the #-prefix: ex: {{lc:...}}
+* config.functionhooks provides a list of parser functions, but that list doesn't distinguish between (a) and (b) above.  So, the functionhooks list has an entry for ""lc"" and an entry of ""if"" (not #if).
+
+So, ostensibly we could have tested if (a) the name starts with a # in which case it is a parser function; OR (b) the name (lc/if/padleft) is present in config.functionhooks.
+
+But (b) gets us into trouble because you also have templates like ""if"".  So, {{if...}} ought to be treated as a template and not a parser function.
+
+We could then use an additional check to see if there is a "":"" in the name to distinguish between {{lc:foo}} and {{lc|foo}}.
+
+This could work, but seems a bit hacky and maybe fragile wrt edge cases. If knowing that something is a parser function is essential for VE, then we could implement this check and maybe add a flag in data-mw or add some other way of marking up a parser function.  data-mw.target.isPF = true possibly?",1369471610,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"This looks sane to me, and won't change much with the url patch. Transclusions are all treated the same in Parsoid. Would you like us to split on the colon and provide a special-case 0th parameter if something looks like a parser function?",1369469460,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"(In reply to comment #4)
+> We are exposing an 'url' format for static targets now. In a follow-up patch
+> we
+> plan to make that editable, and remove the 'wt' value for static targets. For
+> templated targets we will initially still return 'wt', but in the longer term
+> we will expose either 'url' for static targets or 'html' for templated ones.
+So while discussing WikiData integration today, we noticed that parser functions aren't recognized very well. {{#property:capital|of=Germany}} returns {'target':{'wt':'#property:captial'}, 'params':{'of':'Germany'}}
+
+Will this by improved in this URL change you're talking about?",1369404962,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"We are exposing an 'url' format for static targets now. In a follow-up patch we plan to make that editable, and remove the 'wt' value for static targets. For templated targets we will initially still return 'wt', but in the longer term we will expose either 'url' for static targets or 'html' for templated ones.",1369318288,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,https://gerrit.wikimedia.org/r/64987 (Gerrit Change I3145a4168a2347cecc573dcc07bb4128962a5b11) | change APPROVED and MERGED [by jenkins-bot],1369318124,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,Related URL: https://gerrit.wikimedia.org/r/64987 (Gerrit Change I3145a4168a2347cecc573dcc07bb4128962a5b11),1369254139,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,Related URL: https://gerrit.wikimedia.org/r/64651 (Gerrit Change Ie0114a81eead86d7a3b3e3a7a5b10d25c457b524),1369099672,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),"Toolbar in VE floats to position of last BranchNode but should instead just use the bottom of the document or something.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369088700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-djl2633o2ndbnj77h5l2,task_description,resolved
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),Fix merged and will go out with next push.,1371688425,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-djl2633o2ndbnj77h5l2,task_subcomment,NA
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),Related URL: https://gerrit.wikimedia.org/r/69478 (Gerrit Change I1c7662f2b6f1ced6f80dec16c6ed69a8cc0c06c8),1371642471,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-djl2633o2ndbnj77h5l2,task_subcomment,NA
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),"(In reply to comment #1)
+> So the problem is that it lets it go too far or not far enough? I can imagine
+> it somehow, but steps to reproduce the bug would nice.
+
+Doesn't got far enough.
+
+Steps to reproduce: find a document with a very long single BranchNode at the end (or create one). Use VE. Notice that the tool bar slips off the page when you get below the bottom.",1370883741,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-djl2633o2ndbnj77h5l2,task_subcomment,NA
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),"So the problem is that it lets it go too far or not far enough? I can imagine it somehow, but steps to reproduce the bug would nice.",1370851349,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-djl2633o2ndbnj77h5l2,task_subcomment,NA
+VisualEditor: Provide clean way to clone a linmod slice,"Complete with its own sub-store and everything, for consumption by a subsurface.
+
+Right now Trevor is committing crimes against humanity to make this work (converting to DOM then back to linmod again)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369072260,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-g4wwasypneek2xwppnuc,task_description,resolved
+VisualEditor: Provide clean way to clone a linmod slice,Provided by gerrit I38d63e31.,1412608772,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g4wwasypneek2xwppnuc,task_subcomment,NA
+VisualEditor: Provide clean way to clone a linmod slice,ve.dm.Document#cloneSliceFromRange addresses this,1412590792,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-g4wwasypneek2xwppnuc,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs:
+
+1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).
+
+2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.
+
+These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character.
+
+A good start would be to abstract out away calls to string.split( '' ) into a single function like this:
+
+  ve.splitCharacters = function ( value ) {
+      return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs
+  };
+
+The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed.
+
+Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases.
+
+This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369029300,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_description,resolved
+"VisualEditor: Data model needs characters, not code points",Marking this as merged; follow-up in bug 49257.,1370532382,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points",*** Bug 49233 has been marked as a duplicate of this bug. ***,1370531722,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","Ed's main block of code is merged and will go out with wmf5; keeping this open for follow-up, and removing milestone of tomorrow.",1369497594,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes.
+
+The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",1369309137,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points",Related URL: https://gerrit.wikimedia.org/r/64965 (Gerrit Change I8d936fb15d82f73cd45fac142c540a7950850d55),1369248049,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","(In reply to comment #3)
+> Another major issue is that window.getSelection (which is what we use to get
+> cursor position, via Rangy) calculates using number of codepoints, not
+> characters, so this would need to be translated.
+
+Which would be done in ve.ce.getOffsetFromTextNode",1369049395,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","Another major issue is that window.getSelection (which is what we use to get cursor position, via Rangy) calculates using number of codepoints, not characters, so this would need to be translated.",1369048633,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g.
+
+Data: ['F','o','o']
+
+Transaction:
+  Retain: 3
+  Replace:
+    Remove: ''
+    Insert: '<accent>'
+
+Would become:
+
+Transaction:
+  Retain: 2
+  Replace:
+    Remove: 'o'
+    Insert: 'o<accent>'",1369046846,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","A related question is when invalid UTF-16 is checked and how errors are handled. 
+
+I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",1369029854,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Toolserver has the local table toolserver.wiki on all databases that provides metadata about the wikis including the server the wiki's database is kept on:
+
+```
+| mysql> SELECT * FROM toolserver.wiki LIMIT 5;
+| +----------------+------+------------+------------------+------+---------+-----------+--------------+--------------+---------------+--------+-------------+
+| | dbname         | lang | family     | domain           | size | is_meta | is_closed | is_multilang | is_sensitive | root_category | server | script_path |
+| +----------------+------+------------+------------------+------+---------+-----------+--------------+--------------+---------------+--------+-------------+
+| | aawikibooks_p  | aa   | wikibooks  | NULL             |    3 |       0 |         1 |            0 |            0 | NULL          |      3 | /w/         |
+| | aawiki_p       | aa   | wikipedia  | NULL             |    6 |       0 |         1 |            0 |            0 | NULL          |      3 | /w/         |
+| | aawiktionary_p | aa   | wiktionary | NULL             |    1 |       0 |         1 |            0 |            1 | NULL          |      3 | /w/         |
+| | abwiki_p       | ab   | wikipedia  | ab.wikipedia.org |  807 |       0 |         0 |            0 |            0 | NULL          |      3 | /w/         |
+| | abwiktionary_p | ab   | wiktionary | NULL             |    0 |       0 |         1 |            0 |            1 | NULL          |      3 | /w/         |
+| +----------------+------+------------+------------------+------+---------+-----------+--------------+--------------+---------------+--------+-------------+
+| 5 rows in set (0.00 sec)
+
+| mysql>
+```
+
+Most of the information can probably be extracted from operations/mediawiki-config, but I don't know which sources there are authoritative.
+
+See also: {T50625}",1369024500,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-6qqicftxiu35fghejuwg,task_description,resolved
+Provide wiki metadata in the databases similar to toolserver.wiki,"Added a meta_p.legacy view that has the same column name and order as toolserver.wiki for legacy purposes.
+
+Please note that the semantics of the 'server' columns differs and there may be other subtle differences with the toolserver's table not immediately evident.  Unless the same code base has to run on both labs and the toolserver for the interval while it still has replication, transitioning to use meta_p.wiki is preferable.",1377719047,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"It would be possible, but probably unhelpful: from what I understand, the server column is numeric whereas I provide actual host names.  Keeping the column named the same with changed semantics seems to be asking for trouble IMO (i.e.: better a select fails than return a string that is misinterpreted as an integer by code with poor error checking).",1377636605,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Would be a problem to rename slice to server, in order to match the column name of toolserver?
+
+The name column looks good to me from a quick look, btw.",1377636490,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"I did not want to rely on the existence of bool, which isn't ANSI; mysql ""helpfully"" translated my numeric(1) to decimal(1,0).",1377636432,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"decimal(1,0) ? This seems strange. Shouldn't those is_* and has_* be BOOL aka. TINYINT(1) ?",1377636291,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"I've added a table with automatically maintained meta information
+about the replicated databases: meta_p.wiki (which is available on every
+shard).
+
++------------------+--------------+------+-----+---------+-------+
+| Field            | Type         | Null | Key | Default | Extra |
++------------------+--------------+------+-----+---------+-------+
+| dbname           | varchar(32)  | NO   | PRI | NULL    |       |
+| lang             | varchar(12)  | NO   |     | en      |       |
+| name             | text         | YES  |     | NULL    |       |
+| family           | text         | YES  |     | NULL    |       |
+| url              | text         | YES  |     | NULL    |       |
+| size             | decimal(1,0) | NO   |     | 1       |       |
+| slice            | text         | NO   |     | NULL    |       |
+| is_closed        | decimal(1,0) | NO   |     | 0       |       |
+| has_echo         | decimal(1,0) | NO   |     | 0       |       |
+| has_flaggedrevs  | decimal(1,0) | NO   |     | 0       |       |
+| has_visualeditor | decimal(1,0) | NO   |     | 0       |       |
+| has_wikidata     | decimal(1,0) | NO   |     | 0       |       |
++------------------+--------------+------+-----+---------+-------+
+
+There is a lingering issue with the 'name' column which seems to
+improperly encode the Wiki name when non-ascii characters are involved;
+that will get fix once I manage to beat some sense into mysql.
+
+Most columns are self-explanatory, and I can add a few more depending on
+demand.  In the meantime, (dbname, slice) provides the much requested
+mapping between databases and slices.",1377636000,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Yes, but you need to populate that table from /somewhere/.  :-)",1373664795,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,API is per wiki. toolserver.wiki is a meta table.,1373651612,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"(In reply to comment #4)
+> In addition, I think we should only rely on MediaWiki's API for this
+> information (with user authentication, as necessary).
+
+This is particularly important in that some extensions may have hard-to-evaluate effect on some configuration values (namespaces and usergroups being the more obvious cases).
+
+I should say that any necessary configuration value that cannot be fetched through the API should be /added/ to the API rather than fetched through an alternative scheme.
+
+-- Marc",1370202628,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"I think we should have a discussion about what the current ""toolserver"" database is, what we want in the future, and whether we care about breaking backward compatibility.
+
+Some of the design decisions in some of the database tables could probably be re-thought, but only if we're willing to break the current interfaces.
+
+In addition, I think we should only rely on MediaWiki's API for this information (with user authentication, as necessary). This is the cleanest and sanest way to accurately get this information, as far as I know.",1370195310,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Do we want a database table consisting of three columns: wiki, config_variable_name, and config_variable_value (as a serialized blob)?",1370194918,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"(In reply to comment #1)
+> Played around with:
+> 
+> | include ($MediaWikiRepoPath . ""/includes/Defines.php"");
+> | include ($WmfConfigRepoPath . ""/wmf-config/InitialiseSettings.php"");
+> | var_dump ($wgConf->settings);
+> 
+> but it doesn't yield for example information about de.wikipedia.org.
+
+Some experiments:
+
+$ php maintenance/eval.php 
+> $wgDBname='zhwiki';
+
+> $wmfRealm='production';
+
+> $mwConfigDir=""$IP/../operations/mediawiki-config"";
+
+> $wmfConfigDir=""$mwConfigDir/wmf-config"";
+
+> function getRealmSpecificFilename($p){global $IP,$wmfConfigDir;return str_replace($p,$IP,$wmfConfigDir);}
+
+> function wmfLoadInitialiseSettings($c){global $wmfConfigDir;require(""$wmfConfigDir/InitialiseSettings.php"");}
+
+> require(""$wmfConfigDir/wgConf.php"");
+
+> list($site,$lang)=$wgConf->siteFromDB($wgDBname);
+
+> $wikiTags=array();
+
+> $mwConfigDirHandle=opendir($mwConfigDir);
+
+> while(($f=readdir($mwConfigDirHandle))!==false){if(pathinfo($f,PATHINFO_EXTENSION)==='dblist'&&in_array($wgDBname,array_map('trim',file(""$mwConfigDir/$f"")))){$wikiTags[]=pathinfo($f,PATHINFO_FILENAME);}}
+
+> $dbSuffix = ( $site === 'wikipedia' ) ? 'wiki' : $site;
+
+> $wgConf->loadFullData();
+
+> $globals = $wgConf->getAll( $wgDBname, $dbSuffix,array('lang'    => $lang,'site'    => $site,'stdlogo' => ""//upload.wikimedia.org/$site/$lang/b/bc/Wiki.png""), $wikiTags );
+
+> print_r($globals);
+Array
+(
+    [wgLegacyEncoding] => 
+    [wgCapitalLinks] => 1
+    ...
+)
+
+>",1369467985,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Played around with:
+
+| include ($MediaWikiRepoPath . ""/includes/Defines.php"");
+| include ($WmfConfigRepoPath . ""/wmf-config/InitialiseSettings.php"");
+| var_dump ($wgConf->settings);
+
+but it doesn't yield for example information about de.wikipedia.org.",1369450706,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+"VisualEditor, CodeEditor, etc: User experience of editing page source directly","There are now at least three ways to edit a page via index.php (not including other crazy things like Wikidata). I couldn't find a bug tracking this user experience issue, so I'm filing this one.
+
+The three ways I'm initially focused on are:
+
+* directly editing the wikitext (which can appear as an ""edit source"" page tab when VisualEditor is enabled);
+* VisualEditor [https://www.mediawiki.org/wiki/VisualEditor]; and
+* CodeEditor [https://www.mediawiki.org/wiki/Extension:CodeEditor] (automatic for pages in the Module namespace and soon the CSS/JS pages as well; has a toggle in the edit toolbar).
+
+In particular to switch to editing the source, I'm worried about divergent approaches in the user interface. For example, a page tab v. a toggle in the edit toolbar.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1368935460,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-xka4cwtxxzprt6337pfw,task_description,invalid
+"VisualEditor, CodeEditor, etc: User experience of editing page source directly","This 2013 task with no updates in a decade does not seem to be tracking any actionable problem per Aklapper's comment above, so closing.",1725936323,PHID-USER-escte3psz5yfd2nj3jzr,PHID-TASK-xka4cwtxxzprt6337pfw,task_subcomment,NA
+"VisualEditor, CodeEditor, etc: User experience of editing page source directly",Slightly unclear what the bug to fix is here (and hence when it can be considered fixed). Could you elaborate?,1369397664,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xka4cwtxxzprt6337pfw,task_subcomment,NA
+"VisualEditor, CodeEditor, etc: User experience of editing page source directly","oh, and we can also add wikEd to that list :D",1368959990,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-xka4cwtxxzprt6337pfw,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"VE drops things like <i></i>, which Parsoid sometimes uses to preserve strange things.
+
+I think a solution might be to store this as an inline node or as a meta item.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368896280,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-njbgmmjxybp3rk2azuui,task_description,resolved
+VisualEditor: Empty annotations are dropped,"This works for single annotations, but not for nested ones. See https://gerrit.wikimedia.org/r/#/c/69343/ for a failing test case.",1371582191,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,Split new items out to bug 49497; closing this one.,1371065118,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"Above change fixes issue with annotations being dropped, but we still need to fix empty annotations not rendering (e.g. <span style=""display: block; background: red; width: 100px; height: 100px;""></span>), either here or in a new bug.",1371062712,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,Related URL: https://gerrit.wikimedia.org/r/68213 (Gerrit Change I0f3a194f629b054f193a61af105733a555775d79),1371062522,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"That would be nice, yes, but I don't think it's critically important.",1370298323,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"(Actually it's a yes/no question, both cases relate to the same behaviour.)",1369419847,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"(In reply to comment #1)
+> Should the inline node disappear if saved next to similarly annotated text,
+> 
+> e.g.
+> '<i><emptyAnnotation /></i><i>Foo</i>' => '<i>Foo</i>'
+> 
+> or more complex:
+> 
+> '<i><emptyAnnotation /></i><b><i>Foo</i></b>' => '<i><emptyAnnotation
+> /><b>Foo</b></i>'
+> ?
+
+I believe the latter, but Roan was going to answer this.",1369248022,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"Should the inline node disappear if saved next to similarly annotated text,
+
+e.g.
+'<i><emptyAnnotation /></i><i>Foo</i>' => '<i>Foo</i>'
+
+or more complex:
+
+'<i><emptyAnnotation /></i><b><i>Foo</i></b>' => '<i><emptyAnnotation /><b>Foo</b></i>'
+?",1368980503,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: [Regression] Cursor should move to end of inserted contents after paste,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368891000,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wggr7br64lqzvnsbmef2,task_description,resolved
+VisualEditor: [Regression] Cursor should move to end of inserted contents after paste,Merged and will go out with wmf5.,1369092019,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wggr7br64lqzvnsbmef2,task_subcomment,NA
+VisualEditor: [Regression] Cursor should move to end of inserted contents after paste,Related URL: https://gerrit.wikimedia.org/r/64484 (Gerrit Change Ia2a2120cb75aa86374b594ae3f484c5161028919),1368891842,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wggr7br64lqzvnsbmef2,task_subcomment,NA
+VisualEditor: Paste is broken,"Throws an exception on line 564 of ve.ce.Surface, ve.getWindow is undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368890520,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jslagmridhbcpdvjclho,task_description,resolved
+VisualEditor: Paste is broken,Merged in master; will go out as part of wmf5.,1368978729,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jslagmridhbcpdvjclho,task_subcomment,NA
+VisualEditor: Paste is broken,Related URL: https://gerrit.wikimedia.org/r/64483 (Gerrit Change I31dc071328123b57b778aa1b21f0e1daf6405e5c),1368890997,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jslagmridhbcpdvjclho,task_subcomment,NA
+VisualEditor: 'Review and save' disabled after undo on oldid page,"'Review and save' is enabled on loading an old version of a page (as it should) but becomes disabled briefly after the first transaction is committed, and again if you undo to the top of the stack.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368819600,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-kayythzbd2m7qbeafhrw,task_description,resolved
+VisualEditor: 'Review and save' disabled after undo on oldid page,Merged; will go out with wmf5.,1368885016,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kayythzbd2m7qbeafhrw,task_subcomment,NA
+VisualEditor: 'Review and save' disabled after undo on oldid page,Related URL: https://gerrit.wikimedia.org/r/64372 (Gerrit Change I67c011ac655d4e553f9467cab10a875aaac61d03),1368820898,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kayythzbd2m7qbeafhrw,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more","When ""deselecting"" the text field of the visual editor (e.g. by clicking into the summary field) it seems to somehow loose focus.
+
+It's then not possible to directly select text (with the mouse) anymore. One needs to first click one time into the text field to be able to normally select text again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368796920,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-namz3nhksthhosxp6pjt,task_description,resolved
+"Text field seems to lose focus, selection not possible any more","I d'not know why I ever wrote VisualEditor but this definitely is about CodeEditor. And it definitely is fixed now!
+
+Thanks for bringing it up again (I remember you adding the PATCH_TO_REVIEW) but it wasn't merged back then so I couldn't test if the bug was really fixed) so we can close it for good.",1395789580,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more","Wait, this is in the CodeEditor extension group, but people are talking about the 'visual editor'. Did the reporter originally file it under the wrong Extension ?
+
+Eduard, can you clarify please ?",1395786171,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more",This seems fixed with: https://gerrit.wikimedia.org/r/104510,1388485715,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more",Is this the same issue as bug 50722?,1373479425,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more","I think I can replicate this bug, but I'm not sure I entirely understand the whole problem.
+
+If I select some text in the CodeEditor box, then click into another input element on the page to move focus there, then click back into to the CodeEditor, the cursor position within the text area does not change to the place I just clicked at and the selected text remains selected. I would expect it to deselect all text and move the cursor position to where the mouse cursor is. Major -> Minor",1368807619,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more",I'm using Firefox 21 on Windows 7.,1368803015,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more",Could you please provide browser information?,1368802912,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear in category suggestions when you've not picked one that exists","It should only appear when you're matching to a single, extant category - it doesn't appear for a new category, but appears (with no content) where you match more than one, which is confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368749040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ppxeze2biaiay2bq2ned,task_description,resolved
+"VisualEditor: ""Move this category here"" should not appear in category suggestions when you've not picked one that exists",This is fixed.,1370567377,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ppxeze2biaiay2bq2ned,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category","It's a no-op, and is confusing. (But is it more confusing to list it?)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1368745380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-isog5p3qki3pp25ezf63,task_description,resolved
+"VisualEditor: ""Move this category here"" should not appear for the last category",https://gerrit.wikimedia.org/r/68130 (Gerrit Change If48e001b92c217bee0a35b6da41d1c1ff0e3271c) | change APPROVED and MERGED [by jenkins-bot],1371002078,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category",Related URL: https://gerrit.wikimedia.org/r/68130 (Gerrit Change If48e001b92c217bee0a35b6da41d1c1ff0e3271c),1371001967,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category",Related URL: https://gerrit.wikimedia.org/r/68130 (Gerrit Change If48e001b92c217bee0a35b6da41d1c1ff0e3271c),1371001964,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category",Now merged.,1370986001,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category",Related URL: https://gerrit.wikimedia.org/r/67922 (Gerrit Change I93ce05f7cbb28313a3f0827539f0528c366aeb7e),1370905247,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+mw.hook listeners for GuidedTour for shouldSkip,"Investigate how mw.hook could be useful for GuidedTour.  One idea is subscribing to state changes for shouldSkip.  For instance, UploadWizard has an AJAX-type interface where you go from step to step without changing pages.
+
+If we could listen to those steps, we could trigger the shouldSkip check (by calling guiders.resume or maybe another method that only checks this).
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1368612900,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-xj7stom4ugsmlhxmz6az,task_description,resolved
+mw.hook listeners for GuidedTour for shouldSkip,"Change 116228 merged by jenkins-bot:
+Refactor and add non-linear tours, with tests
+
+https://gerrit.wikimedia.org/r/116228",1402332994,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xj7stom4ugsmlhxmz6az,task_subcomment,NA
+mw.hook listeners for GuidedTour for shouldSkip,"Change 116228 had a related patch set uploaded by Mattflaschen:
+WIP: Refactor and add non-linear tours, with tests
+
+https://gerrit.wikimedia.org/r/116228",1397707892,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xj7stom4ugsmlhxmz6az,task_subcomment,NA
+mw.hook listeners for GuidedTour for shouldSkip,"This is done for VisualEditor.  I made this a tracking bug, and opened a separate one (bug 51985) for UploadWizard.",1374693237,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-xj7stom4ugsmlhxmz6az,task_subcomment,NA
+mw.hook listeners for GuidedTour for shouldSkip,I'm working on a change set right now that uses mw.hook for VE like this.,1373067339,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-xj7stom4ugsmlhxmz6az,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"We now have nginx SSL proxies in front of the beta caches (Bug T38648). We still have to fix the certificate (that is *.wmflabs.org for now).
+
+We need certificates generated by 'Labs CA' for the entries listed in role::protoproxy::ssl::beta and some more.  I guess the easiest would be to create *.beta.wmflabs.org cert that will also contains the following DNS entries:
+
+*.wikimedia.beta.wmflabs.org
+*.wikibooks.beta.wmflabs.org
+*.wikinews.beta.wmflabs.org
+*.wikipedia.beta.wmflabs.org
+*.wikiquote.beta.wmflabs.org
+*.wikisource.beta.wmflabs.org
+*.wikiversity.beta.wmflabs.org
+*.wikivoyage.beta.wmflabs.org
+*.wiktionary.beta.wmflabs.org
+
+And the mobile ones:
+
+*.m.wikimedia.beta.wmflabs.org
+*.m.wikibooks.beta.wmflabs.org
+*.m.wikinews.beta.wmflabs.org
+*.m.wikipedia.beta.wmflabs.org
+*.m.wikiquote.beta.wmflabs.org
+*.m.wikisource.beta.wmflabs.org
+*.m.wikiversity.beta.wmflabs.org
+*.m.wikivoyage.beta.wmflabs.org
+*.m.wiktionary.beta.wmflabs.org
+
+*.zero.wikipedia.beta.wmflabs.org
+
+**See Also**:
+{T56065}
+{T70387}
+{T71269}",1368604800,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_description,resolved
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Can this ticket be made public nowadays?  There is now T182927 and it seemed like a duplicate.
+
+Edit: ignore this, this comment was meant to be on T97593)",1513299970,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Can this ticket be made public nowadays?  There is now T182927 and it seemed like a duplicate.,1513299825,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Thanks to @Krenair (with reviews from @BBlack ) we got SSL on beta cluster.  That is quite an achievement.
+
+The last remaining patch has been merged in. I believe there is nothing left to do there.",1472656512,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 247587 merged by BBlack:
+beta: Use Let's Encrypt cert
+
+[[https://gerrit.wikimedia.org/r/247587]]",1472654942,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"So that is now pending review / merge of https://gerrit.wikimedia.org/r/247587 //beta: Use Let's Encrypt cert// which is already on beta cluster.
+",1472038753,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Convince someone with ops rights to merge the patch,1472028326,PHID-USER-mvx4x7ywk2flsaku2dbk,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,That is really neat @AlexMonk-WMF !  Is there anything left to do?,1472027977,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 302409 merged by jenkins-bot:
+deployment-prep: Swap config to HTTPS
+
+[[https://gerrit.wikimedia.org/r/302409]]",1470134583,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 302409 had a related patch set uploaded (by Alex Monk):
+deployment-prep: Swap config to HTTPS
+
+[[https://gerrit.wikimedia.org/r/302409]]
+",1470134511,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 247587 had a related patch set uploaded (by Alex Monk):
+beta: Use Let's Encrypt for upload, and new self-signed SSL certificate for most of text
+
+[[https://gerrit.wikimedia.org/r/247587]]
+",1470107265,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,This is now working for meta.wikimedia.beta.wmflabs.org and deployment.wikimedia.beta.wmflabs.org (and their mobile variants) as well as upload.beta.wmflabs.org. I'll try to handle all other domains tomorrow.,1470123240,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,This is now working for meta.wikimedia.beta.wmflabs.org and deployment.wikimedia.beta.wmflabs.org (and their variants) as well as upload.beta.wmflabs.org. I'll try to handle all other domains tomorrow.,1470107154,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Its puppetized now, should not be hard anymore. We already use it in prod.",1464824261,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,It may or may not be a strict blocker but we should probably wait for {T132812},1460745558,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#2210861, @csteipp wrote:
+> Ftr, I'd love to see us move in the direction of the let's encrypt model, where it's a straightforward, automated process for servers to get a valid cert for their identity. Whether it's LE specifically, or one of the projects that makes an LE-like api that organizations can run to automatically get certificates from their preferred CA.
+> 
+> I think we're going to need more of these (mysql and kafka servers / clients in the near term), and I'd like to get to the point where we're dealing with short lived certs wherever possible.
+
+That might be hard as we're not exposing those servers directly to the internet. I suppose we could use an internal CA and run our own Let's Encrypt-like setup, but this is all far outside the scope of this task :)",1460741823,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#2210736, @Krenair wrote:
+>>>! In T97593#2115226, @Krenair wrote:
+>> I am also wondering what the best way is to put the Let's Encrypt client onto the beta servers. Could we install it on the deployment-cache-text04 and deployment-cache-upload04 instances and have them get their own certificates? They're all running jessie and there is a letsencrypt package available.
+
+Ftr, I'd love to see us move in the direction of the let's encrypt model, where it's a straightforward, automated process for servers to get a valid cert for their identity. Whether it's LE specifically, or one of the projects that makes an LE-like api that organizations can run to automatically get certificates from their preferred CA.
+
+I think we're going to need more of these (mysql and kafka servers / clients in the near term), and I'd like to get to the point where we're dealing with short lived certs wherever possible.",1460741344,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T97593#2115226, @Krenair wrote:
+> I am also wondering what the best way is to put the Let's Encrypt client onto the beta servers. Could we install it on the deployment-cache-text04 and deployment-cache-upload04 instances and have them get their own certificates? They're all running jessie and there is a letsencrypt package available.
+
+>>! In T97593#2116454, @Krenair wrote:
+> I checked this in deployment-cache-upload04 today. It's from jessie-backports and depends on lots of things from there, so you end up with something like:
+> `sudo apt-get install letsencrypt python-cryptography=1.1.1-1~bpo8+1 python-pyasn1=0.1.9-1~bpo8+1 python-openssl=0.15.1-2~bpo8+1`
+> (I did not actually allow this to continue, would like someone else to review since I'm not used to messing with package versions like this)
+
+>>! In T97593#2210712, @Krenair wrote:
+> ops have started using it in production for (ubuntu|apt|mirrors).wikimedia.org and it might be puppetised soon. (see T132450)",1460740489,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T97593#2115226, @Krenair wrote:
+> I am also wondering what the best way is to put the Let's Encrypt client onto the beta servers. Could we install it on the deployment-cache-text04 and deployment-cache-upload04 instances and have them get their own certificates? They're all running jessie and there is a letsencrypt package available.
+
+>>! In T97593#2116454, @Krenair wrote:
+> I checked this in deployment-cache-upload04 today. It's from jessie-backports and depends on lots of things from there, so you end up with something like:
+> `sudo apt-get install letsencrypt python-cryptography=1.1.1-1~bpo8+1 python-pyasn1=0.1.9-1~bpo8+1 python-openssl=0.15.1-2~bpo8+1`
+> (I did not actually allow this to continue, would like someone else to review since I'm not used to messing with package versions like this)",1460738908,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I'm going around a few tasks on this subject trying to merge/close everything together (this one, T70387, T75919, T97593). I'm going to see if I can get Let's Encrypt working for this.",1457835537,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I'm going around a few tasks on this subject trying to merge everything together (this one, T70387, T75919, T97593). I'm going to see if I can get Let's Encrypt working for this.",1457835416,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#1951388, @faidon wrote:
+> Can someone repeat why we can't just flatten the beta hostnames and just procure a *.beta.wmflabs.org certificate?
+
+Presumably because that would make beta less similar to production and less useful for testing things where the domain structure is relevant (e.g. CentralAuth shared cookies).",1453575790,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#527689, @Krinkle wrote:
+> Would it be an option to flatten our subdomains?
+> 
+> We'd only need beta.wmflabs.org and *.beta.wmflabs.org to be in the certificate
+> 
+> (at e.g. DigiCert, those wildcards are $1425 for 3 years includes root and *)
+> 
+> For example:
+> 
+> * beta.wmflabs.org
+> * bits.beta.wmflabs.org
+> * wikimedia.beta.wmflabs.org
+> * commons-wikimedia.beta.wmflabs.org
+> * wikipedia.beta.wmflabs.org
+> * en-wikipedia.beta.wmflabs.org
+> * nl-wikibooks.beta.wmflabs.org
+> * en-m-wikibooks.beta.wmflabs.org
+> * en-m-wikinews.beta.wmflabs.org
+
+I've asked the same a few times and I don't remember the response. Can someone repeat why we can't just flatten the beta hostnames and just procure a *.beta.wmflabs.org certificate?",1453369421,PHID-USER-ktuojnvco4fpzmyhzyaf,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Yeah, beta.wmflabs.org was in the private beta. Don't know if it can actually work with our setup though.",1449227020,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Let's Encrypt is in Public Beta now. Everyone can get free certificates from them now.
+
+[1] https://letsencrypt.org/2015/12/03/entering-public-beta.html
+[2] User Guide for getting certs using Let's Encrypt client: https://letsencrypt.readthedocs.org/en/latest/",1449209519,PHID-USER-arjqb24x4oae7awzpfp6,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#1669896, @Chmarkine wrote:
+> [[ https://letsencrypt.org/ | Let's Encrypt ]] provides free trusted(*) DV non-wildcard certs. We have 31 domains lists [[ http://meta.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix | here ]]. If you think it's plausible, we can obtain 31 certs (one for each domain) from Let's Encrypt at zero cost. 
+> 
+> (*) They will have their CA certificate cross-signed by IdenTrust next month, so the certs they issued won't be trusted until then.
+
+Let's Encrypt has received the cross-signature, so its certificates are now trusted by all major browsers.
+
+[1] https://letsencrypt.org/2015/10/19/lets-encrypt-is-trusted.html",1445334021,PHID-USER-arjqb24x4oae7awzpfp6,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#1670596, @Lixxx235 wrote:
+> Chmarkine, there's always StartCom/StartSSL which has free certs, and they're already trusted by default in all major browsers. 
+
+Yes. But StartCom charges $24.9 for each certificate revocation.
+
+https://www.startssl.com/?app=43",1443105776,PHID-USER-arjqb24x4oae7awzpfp6,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#1670596, @Lixxx235 wrote:
+> Chmarkine, there's always StartCom/StartSSL which has free certs, and they're already trusted by default in all major browsers. 
+
+Yes. But StartCom charges $25 for each certificate revocation.",1443105592,PHID-USER-arjqb24x4oae7awzpfp6,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Chmarkine, there's always StartCom/StartSSL which has free certs, and they're already trusted by default in all major browsers. ",1443100193,PHID-USER-2hzxflhh7cwlrnz74x6y,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I think we'd also want upload.beta.wmflabs.org, maybe stream.wmflabs.org, all of the m./zero. variants? What about mx.beta.wmflabs.org?",1443097851,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"[[ https://letsencrypt.org/ | Let's Encrypt ]] provides free trusted(*) DV non-wildcard certs. We have 31 domains lists [[ http://meta.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix | here ]]. If you think it's plausible, we can obtain 31 certs (one for each domain) from Let's Encrypt at zero cost. 
+
+(*) They will have their CA certificate cross-signed by IdenTrust next month, so the certs they issued won't be trusted until then.",1443084427,PHID-USER-arjqb24x4oae7awzpfp6,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"one more reason we should have this is to avoid needing https://gerrit.wikimedia.org/r/237523  (T105794, T112195)",1441924507,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,@ArielGlenn: there's an NDA'd task at T97593 which Brandon is driving.,1439306906,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,@ArielGlenn: there's an NDA's task at T97593 which Brandon is driving.,1439306268,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,@greg  so what's the decision; there's also https://phabricator.wikimedia.org/T75919 and https://phabricator.wikimedia.org/T70387   Self-signed certs in beta or not?  ,1439287610,PHID-USER-jtxavgb3caz53o45csni,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Is T70387 a duplicate of this?,1429298534,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Matthew Flaschen from comment #93)
+> If cost is the issue, did we consider setting up our own certificate
+> authority (chained to an existing root)?  It's an upfront cost, but as I
+> understand it that means no per-cert cost.
+> 
+> Google and Microsoft both have them, just to name a couple.
+
+Getting a delegated signing certificate is a huge deal actually. Once you have one, any certificate you sign is trusted by all who trust your upstream signer. The x509 protocol does not make it possible to construct a trusted signing certificate that is restricted to a particular domain. As such, any trusted signer who issues delegate signing certificates must impose strict practices and regular audits of those practices on any delegate organization.",1406914396,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I can think of three significant problems with self-signed certificates:
+
+1. It trains people to ignore SSL warnings, which means they ignore them when it's a legit problem.
+2. It causes problems with automated tests (not clear if all of these have been worked around).
+3. It's a real pain when testing manually because you have to visit https://bits.beta.wmflabs.org/ (and maybe also upload.beta.wmflabs.org) manually in Firefox.
+
+FWIW, https://en.wikipedia.beta.wmflabs.org isn't working at all (not even invalid) right now (can't connect), but I assume that's temporary
+
+If cost is the issue, did we consider setting up our own certificate authority (chained to an existing root)?  It's an upfront cost, but as I understand it that means no per-cert cost.
+
+Google and Microsoft both have them, just to name a couple.",1398901677,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"This bug seems to be drifted away from the initial comment.
+(In reply to Antoine ""hashar"" Musso from comment #0)
+> We need certificates generated by 'Labs CA' for the entries listed in
+> role::protoproxy::ssl::beta and some more.  I guess the easiest would be to
+> create *.beta.wmflabs.org cert that will also contains the following DNS
+> entries:
+
+So
+
+(In reply to Greg Grossmeier from comment #91)
+> Won't Fix'ing this for now.
+> A) We have self-signed certs in place on Beta
+
+We still don't have valid self-signed certs for beta since eqiad migration as far as I know. At least nginx refuses to starts because of cert mismatch. As I was told in bug 63538 that this (certs) is handled here, I REOPEN. Please generate new (self-signed) certs.",1398877580,PHID-USER-jcypqodpdpbcicgwgh7j,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Won't Fix'ing this for now.
+
+A) We have self-signed certs in place on Beta
+B) Real certs are expensive
+C) There hasn't been any team come with a specific use case where buying the real certs would make sense.
+
+Feel free to reopen if any of the above changes.",1398876875,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org," > I'm afraid it can't and *.wmflabs.org is not *.beta.wmflabs.org (only one
+> level of wildcard possible). But ask RobH to make sure.
+
+Ah indeed my bad. Sorry :-]",1397643671,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Antoine ""hashar"" Musso from comment #86)
+star.wmflabs.org would cover the entries:
+
+ bits.beta.wmflabs.org
+ upload.beta.wmflabs.org
+ wikidata.beta.wmflabs.org
+
+I'm afraid it can't and *.wmflabs.org is not *.beta.wmflabs.org (only one level of wildcard possible). But ask RobH to make sure.",1397643379,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"for *.wmflabs.org, the self-signed cert has recently been replaced with one from RapidSSL , at first the chained file, which is created by puppet was wrong, the above changes should have fixed that.",1397643103,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+
+https://gerrit.wikimedia.org/r/#/c/111386/
+https://gerrit.wikimedia.org/r/#/c/126008/1",1397643019,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+The beta cluster has for Varnish instances with a Nginx HTTPS proxy installed.  Nginx refuses to start because the star.wmflabs.org certificate is invalid:
+
+root@deployment-cache-bits01:~# /etc/init.d/nginx start
+Starting nginx: nginx: [emerg]
+  SSL_CTX_use_PrivateKey_file(""/etc/ssl/private/star.wmflabs.org.key"")
+  failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)
+ nginx: configuration file /etc/nginx/nginx.conf test failed
+
+
+To fix it we would need a few certificates to be installed on the instances via the role::protoproxy::ssl::beta puppet class in manifests/role/protoproxy.pp
+
+star.wmflabs.org would cover the entries:
+
+ bits.beta.wmflabs.org
+ upload.beta.wmflabs.org
+ wikidata.beta.wmflabs.org
+
+We would need *.wikimedia.beta.wmflabs.org and *.wikipedia.beta.wmflabs.org certs as well.",1397642712,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Greg Grossmeier from comment #84)
+> * Setup was(is?) annoying because of the lack of easy way to secure these
+> private certs from other non-WMF root labs users.
+
+I thought comment 65 and comment 67 said the ""access to private keys without an NDA"" part was solved.
+
+Antoine said he did the sudo configuration (see comment 67); I'm not sure if it's checked yet.",1397014720,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(Lowering priority and unassigning from self)
+
+Status, afaict:
+* Price was annoying, but we've identified the 7 we want (comment 77, comment 79, and comment 83).
+* Setup was(is?) annoying because of the lack of easy way to secure these private certs from other non-WMF root labs users.
+
+Marc/RobH: Let me know if I have that wrong and if there's anything else we can do right now.",1396547005,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"wikidata.beta.wmflabs.org might be nice, since I know a few gadgets go cross domain to it.
+
+I think the dewiki community also wanted to have de.wikipedia.beta.wmflabs.org, but unless we get a discount for buying them at one time, it would probably be good to wait until we have browser tests running against that wiki.",1393026432,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Greg Grossmeier from comment #80)
+
+> 
+> For the avoidance of doubt: we're not doing them all, just a subset. SSL
+> certs are a racket and expensive.
+
+Oh, missed that above. Makes sense :)",1393024173,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Yeah, we can't do all; we can't even reasonably all the necessary wildcards to cover the whole matrix.
+
+I have six now; any more?",1393024132,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Kunal Mehta (Legoktm) from comment #78)
+> http://meta.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix is the full
+> list.
+
+For the avoidance of doubt: we're not doing them all, just a subset. SSL certs are a racket and expensive.",1393023963,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,http://commons.wikimedia.beta.wmflabs.org/ is important,1393023530,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"http://meta.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix is the full list.
+
+There are some weird ones like 'ee-prototype'.",1393023457,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"login.wikipedia.beta.wmflabs.org
+meta.wikipedia.beta.wmflabs.org
+en.wikipedia.beta.wmflabs.org
+bits.beta.wmflabs.org
+upload.beta.wmflabs.org (for some icons on meta/login)
+
+That's all I can see from the network calls.
+
+Antoine/Chris/Chris: confirm?",1393023342,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Because of the necessity to have a default CA sign this, we need to buy individual certificates.  Please provide a definite list of domain names, and I'll get that ball rolling.",1393019538,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I think we do want it, on a limited set of subdomains to keep the cost down.
+
+Beta's:
+- loginwiki (so we can check SUL interactions)
+- metawiki (so OAuth works correctly and securely)
+- another wiki, maybe enwiki? (to catch other SUL login/wgSecureLogin issues)
+- Oh, and to make enwiki work, the bits domain would also need a cert",1390496204,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"We have stopped running browser tests over https. 
+
+I think we still want SSL for labs, but I don't know of anyone actively working on that right now.",1390487679,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #72)
+> Still highest priority.  We want to get that done while I am in SF, hopefully
+> this afternoon (PST time).
+
+Sorry, was referring to another bug :-/
+
+
+Regarding SSL certificates on beta, I am not sure what the status is.  Maybe Greg/Chris would know.  We might have a workaround now or simply stopped running browser tests over HTTPS.",1390442784,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Still highest priority.  We want to get that done while I am in SF, hopefully this afternoon (PST time).",1390420537,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Greg and RobLa: RT ticket states you wanted to discuss how to proceed here.
+Any updates (or should this not be highest priority)?",1390406116,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Would it be an option to flatten our subdomains?
+
+We'd only need beta.wmflabs.org and *.beta.wmflabs.org to be in the certificate
+
+(at e.g. DigiCert, those wildcards are $1425 for 3 years includes root and *)
+
+For example:
+
+* beta.wmflabs.org
+* bits.beta.wmflabs.org
+* wikimedia.beta.wmflabs.org
+* commons-wikimedia.beta.wmflabs.org
+* wikipedia.beta.wmflabs.org
+* en-wikipedia.beta.wmflabs.org
+* nl-wikibooks.beta.wmflabs.org
+* en-m-wikibooks.beta.wmflabs.org
+* en-m-wikinews.beta.wmflabs.org",1387423868,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Reason in comment 16 is past (testing of new default HTTPS access), but warning message in Selenium probably still justifies highest prio? (for four months now)
+
+(In reply to comment #68)
+> The related ticket is https://rt.wikimedia.org/Ticket/Display.html?id=6116
+
+To summarize the RT ticket: Prices offered by SSL vendors felt out of scope.
+
+Greg and RobLa: RT ticket states you wanted to discuss how to proceed here.
+Any updates?",1387200913,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Buying certs is pending approval according to RobH a few days ago.  The related ticket is https://rt.wikimedia.org/Ticket/Display.html?id=6116,1384430488,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+I have cleaned up permissions on the deployment-prep labs project (ie: beta cluster).
+
+The project admins are now limited to people from the Wikimedia ops and mw-core teams.
+
+Root access has been limited to people having signed a non disclosure agreement with Wikimedia.
+
+
+The reason for this change is to let us put real SSL certificates on the Varnish caches which would let us support HTTPS on the beta cluster.  We want to keep access to the certificates restricted, hence the change.
+
+
+Please review the list of admins and sudo policy for the deployment-prep project on:
+
+https://wikitech.wikimedia.org/wiki/Special:NovaProject
+https://wikitech.wikimedia.org/wiki/Special:NovaSudoer",1383836540,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"> 1. Remove projectadmin permissions from volunteers
+
+I also just removed TheDJ since he didn't have an NDA on file and he didn't respond to my email asking if he wanted to sign one.
+
+> 2. Clean up sudo policies to disallow root on varnish systems (that will have
+> real certs)
+
+Apparently the sudo policies are set up at https://wikitech.wikimedia.org/wiki/Special:NovaSudoer. It looks like most of them have sudo enabled for ""ALL"" hosts. I imagine disabling their root privileges on varnish systems just entails unchecking some of these hosts. Unfortunately, I'm not sure which of these hosts are varnish systems. Is it all 4 of the deployment-cache hosts? Any others?
+
+> 3. Buy * certs
+
+Good to hear that's in progress.",1383677201,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #46)
+> Summary of IRC conversation:
+> 
+> 1. Remove projectadmin permissions from volunteers
+
+{{DONE}}, see list of members at: https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep
+
+> 2. Clean up sudo policies to disallow root on varnish systems (that will have
+> real certs)
+
+Not sure what needs to happen here. Tips/Pointers? I think Antoine had some ideas?
+
+> 3. Buy * certs
+
+In progress: https://rt.wikimedia.org/Ticket/Display.html?id=6116",1383162153,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"So I took the bug thinking the cert was blocking everything, however that is not the case.
+
+I will handle the purchase of the certificate, but I am not claiming any ownership over any other part of this process =]
+
+We get purchase approvals within our closed ticketing system, RT#6116.  (I've set Hashar as requestor for that ticket.)  Once its purchased I'll post in here as well.",1383072339,PHID-USER-xy6c3ul27f336aaedx2d,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,unassigning from Ryan to reflect reality.,1383070552,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #46)
+> 2. Clean up sudo policies to disallow root on varnish systems (that will have
+> real certs)
+
+I assume this means that non-admins should not have sudo on these machines?",1383070383,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #58)
+> Anyway, this isn't blocked on ops. In comment 46 I listed the steps that need
+> to be taken, and they can be taken by anyone that has projectadmin in
+> deployment-prep. Someone needs to take ownership of this situation and run
+> with it.
+
+I think the problem is that no one is quite sure how to do those things. I'm not sure otherwise I would JFDI.",1383070340,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Secure login is disabled,1383070174,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Well, disabling secure login is easy - much better to have a couple of tests failing than not be able to run them at all.",1383069987,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"If MobileFrontend doesn't work without HTTPS it's broken. That's a different bug, though.
+
+Anyway, this isn't blocked on ops. In comment 46 I listed the steps that need to be taken, and they can be taken by anyone that has projectadmin in deployment-prep. Someone needs to take ownership of this situation and run with it. It will take us a matter of days to get SSL certs and we can start that process now, but until the other steps are taken there's no major point in doing so.",1383069913,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,This actually makes beta labs unusable for me and the rest of the mobile team. Mobile is dependent on https - it's been like this since login was first introduced. It is not easy to disentangle.,1383069706,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,No I don't. It currently redirect to HTTPS for me in Safari and fails to load completely in Firefox.,1383069532,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #54)
+> Although I have no idea why the HTTP version doesn't load.
+
+It does for me, both in browsers and using curl.  Is it possible you have HTTPS Everywhere or something enabled?",1383017052,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Any progress on this? It's been 2 weeks and we still can't do acceptance testing on beta labs.
+
+And no we can't not use https:
+http://en.m.wikipedia.beta.wmflabs.org/wiki/Main_Page
+Although I have no idea why the HTTP version doesn't load.",1383006331,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+Should be Real Soon Now: https://bugzilla.wikimedia.org/show_bug.cgi?id=55804",1381967050,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #51)
+> I guess the first part of my comment is redundant with what you already know.
+> Mostly, I wanted to convey that our automation testing is broken, in case
+> that
+> affects prioritizing.
+
+Is it possible for now to not use https? That's what other projects have done for now to workaround the issue.",1381966770,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I guess the first part of my comment is redundant with what you already know. Mostly, I wanted to convey that our automation testing is broken, in case that affects prioritizing.",1381966629,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #49)
+> Currently getting a cert warning when trying to go to:
+> https://deployment.wikimedia.beta.wmflabs.org/
+> This is breaking our automation tests for mobile.
+
+Heh. Did you read the ticket any before posting this? :)",1381966170,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Currently getting a cert warning when trying to go to:
+https://deployment.wikimedia.beta.wmflabs.org/
+This is breaking our automation tests for mobile.",1381965216,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,It's going to be an all-inclusive * cert for beta.,1381438407,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,please don't forget about wikidata.beta.wmflabs.org,1381437836,PHID-USER-lzhljhpbm3qfphvqyill,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Summary of IRC conversation:
+
+1. Remove projectadmin permissions from volunteers
+2. Clean up sudo policies to disallow root on varnish systems (that will have real certs)
+3. Buy * certs
+
+Any volunteer that would like to have projectadmin in the project or root on the varnish systems will need an NDA.",1381437765,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 87045 merged by jenkins-bot:
+Labs: Turn off secure login on loginwiki due to untrusted SSL
+
+https://gerrit.wikimedia.org/r/87045",1381250687,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #42)
+> (In reply to comment #40)
+> 
+> > I'm still not opposed to getting a proper cert, but that requires some
+> > infrastructure and permissions changes in deployment-prep...
+> 
+> Since we've been going around on this since May, what would be the next step
+> to
+> make that happen?
+
+Maybe create another project with limited access and move the ssl terminators there. You should realize that other than advising I'm not really doing anything in beta...",1380729147,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #41)
+> (In reply to comment #29)
+> > There's also the option which had been discussed before: make a new labs
+> > project whose sole purpose would be to do SSL termination and would then
+> > relay
+> > to varnish.
+> > 
+> > Then *that* project would have the NDA req instead of the core beta project.
+> 
+> That's the dynamichttp proxy, which has been running silently for a while now
+> :)
+
+They want to have the same https infrastructure as production, which makes sense ;)",1380729060,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #40)
+
+> I'm still not opposed to getting a proper cert, but that requires some
+> infrastructure and permissions changes in deployment-prep...
+
+Since we've been going around on this since May, what would be the next step to make that happen?",1380728062,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #29)
+> There's also the option which had been discussed before: make a new labs
+> project whose sole purpose would be to do SSL termination and would then
+> relay
+> to varnish.
+> 
+> Then *that* project would have the NDA req instead of the core beta project.
+
+That's the dynamichttp proxy, which has been running silently for a while now :)",1380727770,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Has anyone considered creating a CA (http://pages.cs.wisc.edu/~zmiller/ca-howto/), generating a * cert, and adding that certificate to the browser's trust? Is that a possibility using the selenium service we're using?
+
+I'm still not opposed to getting a proper cert, but that requires some infrastructure and permissions changes in deployment-prep...",1380727437,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #33)
+> But I can't find prefershttps in Preferences to turn that off.
+
+So it turns out it only displays if wgSecureLogin is on, but it defaults true either way.  The gotcha is that it wasn't not on for Labs, *except* loginwiki.  However, loginwiki is not taken into account by the Preferences logic.  
+
+I believe the above should workaround that by disabling wgSecureLogin on loginwiki as well.  However, I haven't tested it, since I don't have a realistic CentralAuth environment.
+
+This is just intended to be temporary until there's an SSL setup on Beta that is trusted out-of-the-box by browsers.",1380704544,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 87045 had a related patch set uploaded by Mattflaschen:
+Labs: Turn off secure login on loginwiki due to untrusted SSL
+
+https://gerrit.wikimedia.org/r/87045",1380704074,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Calm down, what we need is to use the 'Labs CA' certificate authority to generate all the certificates we need, then add that authority as a trusted one in the browsers.
+
+I would do it myself if I had access to the 'Labs CA'.",1380701912,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #35)
+> (In reply to comment #33)
+> > (In reply to comment #32)
+> > > (In reply to comment #19)
+> > > > For those playing along at home: The Beta Cluster currently does not have
+> > > > https by default turned on for this very reason (it broke browser tests).
+> > > 
+> > > This is no longer the case.
+> > 
+> > Correction: it's enabled by default, but only for logged in users.
+> > 
+> > But I can't find prefershttps in Preferences to turn that off.
+> 
+> This means, for instance, that VisualEditor is entirely untestable on Beta
+> Labs. Yay fun. :-(
+
+That is not true, VisualEditor works just fine on beta labs, we found Bug 54791 on beta labs with an automated browser test just this week.  Beta labs is as healthy as it has ever been, and it is running the master branch with database updates all maintained automatically.  Varnish on beta is configured properly, and is working well. 
+
+What does not work on beta labs without a real SSL cert are: 
+
+* tests for IE10 are busted : https://saucelabs.com/jobs/a29bcd975ac6483195b3bd56a64fec6a
+
+* having to visit https://bits.beta.wmflabs.org manually over and over again to get styling to work in every browser is a drag",1380665184,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #33)
+> (In reply to comment #32)
+> > (In reply to comment #19)
+> > > For those playing along at home: The Beta Cluster currently does not have
+> > > https by default turned on for this very reason (it broke browser tests).
+> > 
+> > This is no longer the case.
+> 
+> Correction: it's enabled by default, but only for logged in users.
+> 
+> But I can't find prefershttps in Preferences to turn that off.
+
+This means, for instance, that VisualEditor is entirely untestable on Beta Labs. Yay fun. :-(",1380657576,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+Yes. Using beta continues to be a hassle, and in the near future the SSL issue is going to be a big problem.",1380641833,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #32)
+> (In reply to comment #19)
+> > For those playing along at home: The Beta Cluster currently does not have
+> > https by default turned on for this very reason (it broke browser tests).
+> 
+> This is no longer the case.
+
+Correction: it's enabled by default, but only for logged in users.
+
+But I can't find prefershttps in Preferences to turn that off.",1380587930,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #19)
+> For those playing along at home: The Beta Cluster currently does not have
+> https by default turned on for this very reason (it broke browser tests).
+
+This is no longer the case.
+
+(In reply to comment #24)
+> Let's deploy SSL either correctly or not-at-all to beta.
+
+Agreed.  I think turning SSL completely off on beta would be better than the current situation.  It's not good for people to get in the habit of ignoring certificate warnings.
+
+Of course, fixing it properly with a valid cert is best.",1380587514,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Bumping this with a note that this affects our ability to run automated tests with IE10 only.  (Demo on request) Other versions of IE seem to be OK with the current situation on labs, but I haven't found a way around IE10's paranoia. 
+
+It would be good to have some sort of solution for this in advance of support for IE10 in VisualEditor.",1379432509,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Hm. That isn't a bad idea. If we were to do that, I'd want to move the ssl terminators and the caching layer there, and strip private IP info at that layer. Then we can change beta's privacy policy to that of the projects.",1377728033,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"There's also the option which had been discussed before: make a new labs project whose sole purpose would be to do SSL termination and would then relay to varnish.
+
+Then *that* project would have the NDA req instead of the core beta project.",1377727232,PHID-USER-7ey733eainlhx5xqp4d3,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #25)
+> As I've mentioned in the past, I'm totally fine with getting an SSL cert for
+> beta, assuming we ensure every project member in deployment-prep has a signed
+> NDA.
+> 
+> In the future Yuvi's proxy will handle load balancing, HTTPS and such. We'll
+> be
+> able to drop the NDA requirement (and the SSL cert) once we have that.
+
+Not every deployment-prep member is capable of signing an NDA anyway.",1377726168,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Ah. Indeed. Well, let's treat deployment-prep like tools and require NDAs for all roots...",1377725772,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #25)
+> In the future Yuvi's proxy will handle load balancing, HTTPS and such.
+> We'll able to drop the NDA requirement (and the SSL cert) once we have that.
+
+I dont think we should use  Yuvi proxy for beta since the point of the project is to closely reproduce production. Currently the SSL connections are handled by nginx proxies, whenever varnish supports it, they will land on the varnish frontends.",1377725574,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Understandable for manual testing. I just wanted to make sure the automated tests weren't actually blocked, since there's ways to relatively easily workaround the issue.
+
+As I've mentioned in the past, I'm totally fine with getting an SSL cert for beta, assuming we ensure every project member in deployment-prep has a signed NDA.
+
+In the future Yuvi's proxy will handle load balancing, HTTPS and such. We'll be able to drop the NDA requirement (and the SSL cert) once we have that.",1377724502,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Ryan, it's possible to work around the problem, but the issue is that, for manual testing, it's too easy to blame the SSL problem for things that might be totally unrelated.  Let's deploy SSL either correctly or not-at-all to beta.",1377721482,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"My original requests was to generate certificates for the beta wildcards domains using the 'Labs CA' certificate authority.  By adding that authority certificate in the browser (or accepting it), that should make the browser trust all the generated certs.",1377721422,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,The automated tests were OK I think with maybe some small exceptions.  The hassle was having to visit all the hosts (e.g. bits) in your browser in order to use any beta wikis.,1377718091,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Is it not possible to disable certificate checking on the automated browser tests until we get a proper certificate? I remember this being possible years ago when I built a selenium cluster...,1377717965,PHID-USER-xs3vxsmgivmm2tuyxsrb,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Mostly it makes using beta labs manually a real hassle.,1377716121,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,For those playing along at home: The Beta Cluster currently does not have https by default turned on for this very reason (it broke browser tests).,1377713093,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"We should probably disable default https on beta until we have the opportunity to fix this up properly.  The proper fix, from what I understand, is pretty complicated, and isn't something we can do with just a day or two of elbow grease.",1377712492,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"There's no interface with firefox, either. The workaround is to manually go to https://bits.beta.wmflabs.org/ and accept the certificate there.",1377088410,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,It seems to me that being able to test the new [[m:HTTPS]] stuff on beta is a rather high priority; otherwise beta should be fixed for its other uses by reverting the HTTPS redirect on it.,1377084434,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Apparently the beta labs now forcefully redirect to https, which means all beta sides are unusable for me (Chrome) because there is no obvious way to accept the certificate for bits, so no resources are being loaded.",1377078117,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,*** Bug 46621 has been marked as a duplicate of this bug. ***,1377077926,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,*** Bug 49533 has been marked as a duplicate of this bug. ***,1377077878,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,*** Bug 53113 has been marked as a duplicate of this bug. ***,1377028391,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Alex: turning ssl certificate verification off when doing automated testing is reasonably common because lots of folks don't run with valid certs and don't have a good infrastructure for distributing their self signed certs.  That isn't to say it is a good practice, just a common one.",1376416702,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Upping priority (a tiny bit) as we really need the beta cluster (hosted on labs) to be as similar to production as possible for automated testing. This is needed for that (specifically for SUL2, kinnnnnda important ;) ).",1376408675,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"All browsers should force you to navigate that warning, unless you've somehow changed their configuration to somehow completely break that security feature.",1375118567,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"in the configurations we're using, other browsers don't require an automated test to negotiate a warning screen, see the screen shot on Bug 52121",1375112625,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,The other browsers don't like it either. Why is IE so special to you?,1375112429,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,We need beta labs to work for IE in default configurations for test purposes. See Bug 52121,1375110403,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,*** Bug 52121 has been marked as a duplicate of this bug. ***,1374916134,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Did not block the creation of a login wiki bug 51622
+
+But it does prevents us from using SUL2 on beta which is bug 51580",1374694229,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Moving out from RT to ""Labs"" > ""Infrastructure"", per Ryan :)",1369121097,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,RT #5184,1369038519,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Mailled labs-l to find out who can generate the cert. http://lists.wikimedia.org/pipermail/labs-l/2013-May/001212.html,1368605321,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,"We need a public API end point integrating with the general MediaWiki API that provides at least the following functionality:
+
+* HTML DOM retrieval per page and revision. Basically the /en/Foo?oldid=<n> end point.
+* HTML DOM expansion: POST a DOM (or fragment), return re-expanded DOM
+* HTML DOM saving: POST a modified DOM and a summary, and save it as a new revision.
+
+As long as we are using Wikitext as our storage format, saving requires a conversion to HTML and a separate save step. The individual steps should *internally* be exposed to other users including the VisualEditor extension. There is probably no need to expose the HTML2WT conversion. We should instead aim to provide an HTML-only public interface.
+
+The integration should use an URL schema that makes it easy to map some or all of the functionality to a stand-alone (non-PHP) backend to avoid PHP startup costs in the future.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368578460,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpywcmlyfhgff4artepd,task_description,resolved
+Expose a parsoid public web API end point in the MediaWiki API,"@anomie Seems like it was mis-tagged, sorry about that. Will remove the project.",1426257850,PHID-USER-hxwwywcyzpooynxuo7a2,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,So this was in #MediaWiki-API but didn't actually have anything to do with that project?,1426257574,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Now resolved with https://rest.wikimedia.org/ entering beta production.,1426214472,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,"Lowering the priority as this is now live:
+
+http://parsoid-lb.eqiad.wikimedia.org/
+https://parsoid-prod.wmflabs.org/  (also supports spdy)",1386109005,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Once https://gerrit.wikimedia.org/r/#/c/93527/ is merged we'll provide interim access to our internal Parsoid cluster through front-end caches at http://parsoidcache.svc.eqiad.wikimedia.org/. This implements our internal https://www.mediawiki.org/wiki/Parsoid#The_Parsoid_web_API. In the longer term it will be replaced with a more general MediaWiki content API that we are still working on.,1384293539,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,"The PHP parser output is exposed through action=parse:
+
+http://en.wikipedia.org/w/api.php?action=parse&redirects&prop=text%7Cdisplaytitle&format=xml&page=FOOBAR",1378248026,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Marco and I are taking this on.,1377273791,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Bumped the prority. We should get to this after Wikimania.,1375927194,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Building prod. tools based on Parsoid output (for example to produce offline snasphots) needs this MW API. http://parsoid.wmflabs.org/ can only be a temporary solution...,1373488881,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,"(In reply to comment #0)
+> * HTML DOM saving: POST a modified DOM and a summary, and save it as a new
+> revision.
+
+Just to clarify, we don't need this for June/July (we're doing it in VisualEditor currently) - though it's a nice-to-have. :-)
+
+The real focus for us is the HTML DOM expansion, which we will want ASAP for templates and other generated content blocks.",1368669141,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Currently the VisualEditor linkes like this: [[Glas|Glases]]
+The German-language Wikipedia prefers this though: [[Glas]]es
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51438
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49940
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52240",1368551520,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-arvnl4rgkbslvicqgsmj,task_description,open
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#4223170, @Bencemac wrote:
+> @Cirdan I mean it should fix the [[ https://tools.wmflabs.org/checkwiki/cgi-bin/checkwiki.cgi?project=enwiki&view=only&id=64 | existing ones ]]. So if somebody edit an article with `[[text|text]]`, the software would fix that (like AWB does). It could slowly but surely solve the problem.
+
+As @Cirdan says, Parsoid and the visual editor try very hard to avoid changing wikitext that already exists in the article. Different wikis have different conventions, and the most reliable way to respect those conventions is to avoid digging into bits of wikitext that don't relate directly to what the user has done.
+
+The visual editor is not intended to be a general purpose wikitext cleanup tool. As you suggest, AWB is good for that.",1527075466,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"I'm not a VE developer, but from what I learned from reporting Parsoid bugs, the VE/Parsoid try very hard to //not// alter existing wikitext. This is where quite a few of the copy & paste bugs come from.
+
+I believe syntax cleaning should be done by bots which are controlled by the local community, not through VE.",1527054738,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"@Cirdan I mean it should fix the [[ https://tools.wmflabs.org/checkwiki/cgi-bin/checkwiki.cgi?project=enwiki&view=only&id=64 | existing ones ]]. So if somebody edit an article with `[[text|text]]`, the software would fix that (like AWB does). It could slowly but surely solve the problem.",1527015724,PHID-USER-qdbrv6swdxlgemqwwbuw,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#4223073, @Bencemac wrote:
+> @Esanders I think the idea (Visual Editor should fix automatically `[[text|text]]`) could be a goal and it would have an own task. This task is related, but it is not exactly what I suggested.
+
+The problem with `[[text|text]]` was resolved in {T153107}. If it has re-appeared, that task should be re-opened. From what you wrote in [[T195215#4220491]], the problem is link trail detection/generation, which is what this task is about.",1527015152,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"@Esanders I think the idea (Visual Editor should fix automatically `[[text|text]]`) could be a goal and it would have an own task. This task is related, but it is not exactly what I suggested.",1527013628,PHID-USER-qdbrv6swdxlgemqwwbuw,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"There are several similar reports.
+
+One thing is shortening the overall link to make it easier to spot and read in wikitext, it is less cluttered, and that is a good reason to enforce use of linktrail.
+
+Use of linktrail can also be troublesome. Assume a link using one inflected word, where the inflection goes in the linktrail. Then the links are changed to another page title, but that page title has another inflection. To detect this and change it accordingly with the current bot frameworks are pretty difficult.
+
+In English plural of `book` is `books`, but in Norwegian this is `bok`and `bøker`. 
+
+Note that use of linktrail is an indication of a deeper problem. It should be possible for the writer to inflect the links themselves. That is instead of [[book]]s they should be able to write [[books]].
+
+The page titles are usually of a normalized form, and rewriting a link into this normalized form is pretty strightforward. In some cases there are alternate normalized forms, but as long as all of them identify the same page there should be no real problem. Only if different inflections targets different pages would there be a problem.",1517057368,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"There are several similar reports.
+
+One thing is shortening the overall link to make it easier to spot and read in wikitext, it is less cluttered, and that is a good reason to enforce use of linktrail.
+
+Use of linktrail can also be troublesome. Assume a link using one inflected word, where the inflection goes in the linktrail. Then the links are changed to another page title, but that page title has another inflection. To detect this and change it accordingly with the current bot frameworks are pretty difficult.
+
+Note that use of linktrail is an indication of a deeper problem. It should be possible for the writer to inflect the links themselves. The page titles are usually of a normalized form, and rewriting a link into this normalized form is pretty strightforward. In some cases there are alternate normalized forms, but as long as all of them identify the same page tere should be no real problem. Only if different inflections targets different pages would there be a problem.",1517056634,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"There are several similar reports.
+
+One thing is shortening the overall link to make it easier to spot and read in wikitext, it is less cluttered, and that is a good reason to enforce use of linktrail.
+
+Note that use of linktrail is an indication of a deeper problem. It should be possible for the writer to inflect the links themselves. The page titles are usually of a normalized form, and rewriting a link into this normalized form is pretty strightforward. In some cases there are alternate normalized forms, but as long as all of them identify the same page tere should be no real problem. Only if different inflections targets different pages would there be a problem.",1517055772,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"There are several similar reports,.
+
+One thing is shortening the overall link to make it easier to spot and read in wikitext, it is less cluttered, and that is a good reason to enforce use of linktrail.
+
+Note that use of linktrail is an indication of a deeper problem. It should be possible for the writer to inflect the links themselves. The page titles are usually of a normalized form, and rewriting a link into this normalized form is pretty strightforward. In some cases there are alternate normalized forms, but as long as all of them identify the same page tere should be no real problem. Only if different inflections targets different pages would there be a problem.",1517055748,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Since there was another [[ https://de.wikipedia.org/w/index.php?diff=173370165&oldid=173263938&title=Wikipedia:Technik/Text/Edit/VisualEditor/R%C3%BCckmeldungen | complaint]] on the de-wp VE feedback page, I'm reviving this bug report. [[ https://de.wikipedia.org/w/index.php?diff=173369735&oldid=159649392 | Here ]] the previously correctly formatted link 
+```
+[[Baudenkmal]]e
+```
+was converted to
+```
+[[Baudenkmal|Baudenkmale]]
+```
+
+Is there any hope that this problem will be fixed soon? If that's not possible, a brief explanation of why it is difficult (which we can relay to our community when this question comes up) would be helpful.",1517047661,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Since there was another [[ https://de.wikipedia.org/w/index.php?diff=173370165&oldid=173263938&title=Wikipedia:Technik/Text/Edit/VisualEditor/R%C3%BCckmeldungen | complaint]] on the de-wp VE feedback page, I'm reviving this bug report. [[ https://de.wikipedia.org/w/index.php?diff=173369735&oldid=159649392 | Here ]] the previously correctly formatted link 
+```
+[[Baudenkmal]]e
+```
+was converted to
+```
+[[Baudenkmal|Baudenkmale]]
+```
+
+Is there any hope that this problem will be fixed soon?",1517047576,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#2874249, @Cirdan wrote:
+> Thanks for the clarification. This specific case of this bug understandably decreases acceptance of the VisualEditor on de-wp, whereas the general problem regarding trailing characters is generally seen as acceptable. I asked several complaining users to provide more diffs of this specific case which I will add here.
+
+Let us unmerge T153107, retitle it, and add diffs there. [[Foo|Foo]] shouldn't be happening and is either a regression or a corner case in the HTML or something else going on that we have some missed all this while.",1481751088,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Thanks for the clarification. This specific case of this bug understandably decreases acceptance of the VisualEditor on de-wp, whereas the general problem regarding trailing characters is generally seen as acceptable. I asked several complaining users to provide more diffs of this specific case which I will add here.",1481750714,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#2870576, @Cirdan wrote:
+>> VE is an HTML editor. What kind of clean-up of HTML do you expect VE to do that would affect this?
+> 
+> Not HTML, but apparently editing pages with the VE creates links like 
+> ```
+> [[Target|Target]]
+> ```
+> in the Wikitext. I would assume that before Wikitext is saved (or delivered to the user), this is automatically cleaned to
+> ```
+> [[Target]]
+> ```
+
+Parsoid currently has code to generate simple links where necessary, but, clearly there was a bug that affected the diff you highlighted in T153107. But, in general, Parsoid does generate [[Foo]] instead of [[Foo|Foo]].",1481664094,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"> VE is an HTML editor. What kind of clean-up of HTML do you expect VE to do that would affect this?
+
+Not HTML, but apparently editing pages with the VE creates links like 
+```
+[[Target|Target]]
+```
+in the Wikitext. I would assume that before Wikitext is saved (or delivered to the user), this is automatically cleaned to
+```
+[[Target]]
+```
+",1481663806,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#2870216, @Cirdan wrote:
+>>> How is it possible that the parser does not detect two identical strings as identical?
+>> Your question assumes that it is looking for that. I don't know whether it is.
+> 
+> I just looked through what I believe to be the relevant parts of the source code, and it indeed seems that this is not how Parsoid handles this. I haven't looked at the VE implementation though. Is there no general cleanup at the end of a VE editing session?
+
+VE is an HTML editor. What kind of clean-up of HTML do you expect VE to do that would affect this?",1481662022,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">> How is it possible that the parser does not detect two identical strings as identical?
+> Your question assumes that it is looking for that. I don't know whether it is.
+
+I just looked through what I believe to be the relevant parts of the source code, and it indeed seems that this is not how Parsoid handles this. I haven't looked at the VE implementation though. Is there no general cleanup at the end of a VE editing session?
+
+",1481658837,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#2870045, @Cirdan wrote:
+> Jdforrester-WMF, thanks for merging T153107. Could you elaborate how these two are related?
+
+They are both issues where Parsoid is apparently creating wikitext sub-optimally.
+
+> How is it possible that the parser does not detect two identical strings as identical?
+
+Your question assumes that it is looking for that. I don't know whether it is.",1481657441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Jdforrester-WMF, thanks for merging T153107. Could you elaborate how these two are related? How is it possible that the parser does not detect two identical strings as identical?",1481657102,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,See also Change-Id: I78c8fc87be1777f63c84f8945ead1cc54161fb76,1374487741,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372933998,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"(In reply to comment #1)
+> Parsoid issue, moving to Parsoid.
+> 
+> Would like some input from James as to what he believes the behavior should
+> be (piped links always? linktrails where possible? configurable either way?).
+
+Canonically, linktrails should be preferred where possible (so, whenever a case-sensitive substring; except when on a $wgCapitalLinks=true, where it's a tad more complicated). I believe that linkheads should also be preferred where possible for the languages for which that applies.",1368771151,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Parsoid issue, moving to Parsoid.
+
+Would like some input from James as to what he believes the behavior should be (piped links always? linktrails where possible? configurable either way?).",1368770935,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+VisualEditor: Green striped area doesn't align properly in Monobook,"When VisualEditor comes across a part of a page it can't edit, it adds a green striped area. However, VisualEditor seems to have very bad aim in Monobook. Screenshots forthcoming.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368498360,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-vgio4d23zmdnqxwyja3n,task_description,resolved
+VisualEditor: Green striped area doesn't align properly in Monobook,We did a bit of a re-write of how the phantoms appear in the last push; glad this fixed it. :-),1370362551,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vgio4d23zmdnqxwyja3n,task_subcomment,NA
+VisualEditor: Green striped area doesn't align properly in Monobook,This appears to be fixed.,1370356051,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-vgio4d23zmdnqxwyja3n,task_subcomment,NA
+VisualEditor: Green striped area doesn't align properly in Monobook,"Created attachment 12310
+VisualEditor using the Monobook skin on mediawiki.org; incorrect behavior
+
+https://www.mediawiki.org/wiki/MobileFrontend/Photo_upload/Analysis?useskin=monobook&veaction=edit
+
+**Attached**: {F10761}",1368498533,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-vgio4d23zmdnqxwyja3n,task_subcomment,NA
+VisualEditor: Green striped area doesn't align properly in Monobook,"Created attachment 12309
+VisualEditor using the Vector skin on mediawiki.org; correct behavior
+
+https://www.mediawiki.org/wiki/MobileFrontend/Photo_upload/Analysis?useskin=vector&veaction=edit
+
+**Attached**: {F10760}",1368498417,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-vgio4d23zmdnqxwyja3n,task_subcomment,NA
+Enable VisualEditor on all content namespaces on mediawiki.org,"Currently VisualEditor is only enabled on the user/main namespaces on mediawiki.org. It'd be nice if it were enabled on all namespaces on mediawiki.org.
+
+Perhaps test.wikipedia.org and test2.wikipedia.org as well.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1368497580,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-azvy6g4nbj2z6hw5ydsm,task_description,resolved
+Enable VisualEditor on all content namespaces on mediawiki.org,Now complete.,1369075886,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-azvy6g4nbj2z6hw5ydsm,task_subcomment,NA
+Enable VisualEditor on all content namespaces on mediawiki.org,Related URL: https://gerrit.wikimedia.org/r/63621 (Gerrit Change I1c18ff72265ed4a33c5114141d5d97301e85c2e3),1368499865,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-azvy6g4nbj2z6hw5ydsm,task_subcomment,NA
+VisualEditor: Round-trip failures,"Bad diff from VisualEditor on mediawiki.org, 2013-05-13
+
+Go to <https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals>. Click ""edit"". VisualEditor form loads. Add a space after the sentence ""that drive editor engagement;"". Remove the space. Click ""Review and save"".
+
+Expected behavior: a diff showing no changes at all (space was added to the end of the line and then removed).
+
+Current behavior: see attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10742}",1368496740,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6r6iwczgdw2x3g22idm6,task_description,resolved
+VisualEditor: Round-trip failures,"We did a bunch of changes to avoid dirty-diffs with Parsoid; though there may be a few outstanding, I think we've got most of them licked, so closing.",1371867377,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+VisualEditor: Round-trip failures,Seems to have been fixed since the filing of this bug. Can you still reproduce this?,1371865706,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+VisualEditor: Round-trip failures,"(In reply to comment #2)
+> Are Parsoid/VisualEditor versions exposed somewhere?
+
+[[mw:Special:Version]] :-) In general, VisualEditor is branched for production at the same time as MediaWiki core right now (so, fortnightly for the rest of this month, thereafter weekly); Parsoid is updated in production more frequently but less regularly, as it's a manual process.
+
+> Or alternately, is there a public wiki running the most up-to-date version
+> of VisualEditor?
+
+No, I don't think so (but isn't beta meant to run master of everything?). Perhaps I should make a bug to build one in Labs.
+
+> I really don't like wasting my time filing bugs that no longer exist. :-/
+
+The perils of testing software that gets a dozen or so bugs fixed each week, sadly. In this particular case, I'm assuming that it's a Parsoid bug that was fixed (as I can't see anything in our git log that would suggest a VE fix changing this behaviour). Sorry!",1368979421,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+VisualEditor: Round-trip failures,"(In reply to comment #1)
+> I played around a bit locally while on the plane and tried to reproduce on
+> master from the screenshot.
+
+Blergh. I can still definitely reproduce this issue on mediawiki.org following the steps in comment 1.
+
+Are Parsoid/VisualEditor versions exposed somewhere? Or alternately, is there a public wiki running the most up-to-date version of VisualEditor? I really don't like wasting my time filing bugs that no longer exist. :-/",1368906585,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+VisualEditor: Round-trip failures,"I played around a bit locally while on the plane and tried to reproduce on master from the screenshot. I didn't reproduce your bug, but I found bug 48605 instead. Now that I have an internet connection again, I'll take a proper look at this bug once I've caught up on sleep.",1368896354,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+"VisualEditor: Categories with multiple ""../""s in their hrefPrefix broken","VisualEditor added ""../"" inside [[Category:QA]], breaking the link. I swear I didn't touch the category itself. I was just editing an unrelated paragraph.
+
+See https://www.mediawiki.org/w/index.php?title=Groups%2FProposals%2FFeatures_testing&diff=689563&oldid=689504
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368466500,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dga3eyvqthuwtl6xayui,task_description,resolved
+"VisualEditor: Categories with multiple ""../""s in their hrefPrefix broken","(In reply to comment #2)
+> We're going to put this into wmf4 with a Lightning Deploy this afternoon
+> rather
+> than wait for wmf5; thanks for the catch, Quim!
+This is now done.",1368487340,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dga3eyvqthuwtl6xayui,task_subcomment,NA
+"VisualEditor: Categories with multiple ""../""s in their hrefPrefix broken","We're going to put this into wmf4 with a Lightning Deploy this afternoon rather than wait for wmf5; thanks for the catch, Quim!",1368471008,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dga3eyvqthuwtl6xayui,task_subcomment,NA
+"VisualEditor: Categories with multiple ""../""s in their hrefPrefix broken",Related URL: https://gerrit.wikimedia.org/r/63496 (Gerrit Change I84d2b23a05585890b2d5023c7c7f38a43889fd7f),1368468797,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dga3eyvqthuwtl6xayui,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,"Any plans of having JSCover (JavaScript code coverage analysis) being integrated and run by Jenkins (in away that is usable for core and extensions as well)?
+
+[1] http://tntim96.github.io/JSCover/
+
+[2] http://tntim96.github.io/JSCover/example-qunit/out/jscoverage.html?test/index.html
+
+[3] http://tntim96.github.io/JSCover/manual/manual.xml#automatingPhantomJS
+
+[4] http://tntim96.github.io/JSCover/manual/manual.xml#automatingAnt
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1368310740,PHID-USER-ldehclaehsvglrqxywsj,PHID-TASK-irkp2njalgjutggxseff,task_description,declined
+Jenkins: Set up JavaScript code coverage analysis,"JSCover didn't work out very well.
+
+I've standardised on istanbul[1] for the moment. There are qunit[2] and karma[3] integrations. Both of which we've been using for OOjs and VisualEditor these past few months.
+
+They have command-line and HTML reporters.
+
+[1]
+http://gotwarlost.github.io/istanbul/
+https://github.com/gotwarlost/istanbul
+
+[2]
+https://github.com/asciidisco/grunt-qunit-istanbul
+
+[3]
+https://github.com/karma-runner/karma-qunit
+https://github.com/karma-runner/karma-coverage",1411761995,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,Javascript coverage is still something we need. Nobody looked at integrating it in Jenkins yet though.,1383584273,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,I'm not sure this will get any attention in a foreseeable future therefore closing this one.,1383363539,PHID-USER-txixdzq7tyya37eageyl,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,"**tntim96** wrote:
+
+The JSCover JAR (JSCover-all.jar) is all custom code and only includes the Rhino library (i.e. no Jetty, Log4J, Apache-commons or other library dependencies).
+
+Also, there is no HTML parser. When a JavaScript file is requested via JSCover's web or proxy server, JSCover instruments the specified JavaScript only. 
+
+Whether the HTML is generated dynamically or not doesn't affect JSCover in proxy-mode. 
+
+For proxy documentation, take a look at:
+http://tntim96.github.io/JSCover/manual/manual.xml#gettingStartedProxy
+
+...and a working proxy example at:
+https://github.com/tntim96/JSCover-samples/blob/master/src/test/java/jscover/webdriver/jasmine/WebDriverUnderscoreProxyTest.java
+
+Let me know if there are any changes required to JSCover that would assist you.",1378180020,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,"Both jscoverage and the new fork JSCover seem to have quite a nasty (though from a quick look, hard to avoid) implementation that involves instrumenting files. 
+
+Though that in and of itself isn't a problem, it does this by running a static file server and proxying javascript files through its instrumentor and using some kind of HTML parser (another Java class dependency) to catch inline scripts even (not sure).
+
+This isn't going to work straight up with MediaWiki since we generate HTML dynamically (e.g mediawiki-core/index.php) and load things through ResourceLoader.",1374001877,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,I think we want QUnit tests on a few more extensions before adding code coverage. Thus lowering priority.,1371757672,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Single newlines have no effect on the way a wiki page is displayed.
+So they should be ignored in a WYSIWYG editor.
+
+Example: Third line at http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services#Specification_progress_.26_TC_members",1368091860,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-o45i4q2kievixjidhsk7,task_description,open
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","On enwiki, one of the common uses of this is when people have a big {{Cite}} template and hit enter after it for readability.
+
+One thing having this character visible does is encourage experienced editors to delete it.
+
+When I was a newer editor, I had no idea what this character meant and it took me awhile to figure it out.
+
+Anyway, I think leaving it as is (current behavior) or removing it from being seen in the visual editor without changing any wikitext would be acceptable options. I don't think ""silently strip"" is a good option.
+",1657957730,PHID-USER-qydb7ytmqqctg7dn7fqa,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","That sounds very project-specific.  In my experience, line breaks (shown as '↵' in VisualEditor) on enwiki often mean that someone has copied and pasted the text from another document (e.g., written the text offline in a word processor).  It only rarely seems to be done intentionally.
+
+(Also, what if a line break someday stopped being interpreted as a space?)",1501341568,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Additional [[ https://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/R%C3%BCckmeldungen#Zeichen_.27.E2.86.B5.27_taucht_in_Abs.C3.A4tzen_im_VisualEditor_auf.2C_wird_aber_nicht_erkl.C3.A4rt | feedback from a German editor]] regarding this issue:
+""Wikipedians delete the '↵' in VisualEditor and replace it with a space. But this character '↵' only indicates that a break was added to the source for better readability, which is automatically translated into a space. It's often used in long citation blocks, for example. This' ↵'-character makes the Wikitext / source text more readable. The good readability of the source text in the source editor (Edit window) is still one of the quality indicators explicitly mentioned in our guidelines for good articles. The meaning in the VisualEditor is only that the user should insert a new text not to the left but to the right of the '↵' character. Just simply so that the line break in the source text remains directly behind the left character. But, when looking at the instructions, this subtlety is not mentioned. Also, no warning is displayed when you delete the '↵' character in the VisualEditer. Apparently the character can not be inserted in the VirtualEditor any more, if it was deleted. [...] I would hope that there is a warning when deleting the character or a tooltip when the mouse is hovering above the character. Thank you.""",1501320721,PHID-USER-kuuo2hpmktiqobsevyw6,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","@Jdforrester-WMF let me try to rephrase to see if I understand, the
+carriage return symbol is shown in VE because a wikitext editor has
+included a line break in the editing environment to increase readability of
+the wikitext, however this does not affect the presentation of the content
+in read mode, and is meaningless and confusing to VE editors.
+
+However there is a worry (by whom?) that not showing the character at all
+would make it much easier for a VE editor to accidentally remove the
+character because it has no visual representation. On the other hand
+visualizing it as an actual line-break causes inconsistency between edit
+and read modes (which currently exists in wikitext/read more)
+
+Is that summary clear and factual?
+
+
+
+*Jared Zimmerman * \\  Director of User Experience \\ Wikimedia Foundation
+
+M +1 415 609 4043 \\ @jaredzimmerman <http://loo.ms/g0>",1425063560,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",">>! In T50290#1074137, @Jaredzimmerman-WMF wrote:
+> Unless I'm misunderstanding Whatamidoing, I think they mean that we copy
+> line breaks in as actual linebreaks, so that reading and editing look the
+> same and no one actually sees that carriage return symbol ever.
+
+Yes, you're entirely missing the point here.
+
+* Actual reader-visible new paragraphs (from two new lines after each other in wikitext) are shown as new paragraphs.
+* Actual reader-visible line breaks (from a <br /> tag) are shown as line breaks.
+
+This is about how to represent the reader-invisible nonsense wikitext single new line. See T50290#499295 for details; nothing's changed here since May 2013.",1425062104,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Unless I'm misunderstanding Whatamidoing, I think they mean that we copy
+line breaks in as actual linebreaks, so that reading and editing look the
+same and no one actually sees that carriage return symbol ever.
+
+
+
+*Jared Zimmerman * \\  Director of User Experience \\ Wikimedia Foundation
+
+M +1 415 609 4043 \\ @jaredzimmerman <http://loo.ms/g0>",1425061938,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",">>! In T50290#1074123, @Whatamidoing-WMF wrote:
+> I like the idea of showing it as a line break.  This might make more sense to less-technical people that have just copy-pasted text out of another document (one of the apparent causes) than the insertion of an unexpected symbol.
+
+I'm not a fan of making VE less like the reading experience, though.",1425061657,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",I like the idea of showing it as a line break.  This might make more sense to less-technical people that have just copy-pasted text out of another document (one of the apparent causes) than the insertion of an unexpected symbol.,1425061578,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 57454 has been marked as a duplicate of this bug. ***,1415882814,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 68811 has been marked as a duplicate of this bug. ***,1406754254,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 65324 has been marked as a duplicate of this bug. ***,1401419217,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Indeed not WYSIWYG, but I happen to love this feature. I practically always remove these links when I see them. I'd say WONTFIX.",1400608205,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 50641 has been marked as a duplicate of this bug. ***,1394482866,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 61569 has been marked as a duplicate of this bug. ***,1393537023,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","(In reply to comment #2)
+> Newline characters are more debatable, because some people use them to make
+> wikicode more readable.
+
+...and I remmember some people use them to make diffs more readable[citation needed].",1372607697,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Example of TAB characters:
+http://en.wikipedia.org/wiki/Refrigerator#Production_by_country",1368684670,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Same for TAB characters, which are shown as ➞
+
+TAB characters have no meaning in wikicode, and I can't imagine anyone entering them for any purpose (plus they are difficult to enter in an HTML form).
+I have never seen a case where they are intended (please point me to any example if I am mistaken).
+
+I personally think TABs are a case where silent stripping would be acceptable.
+
+---
+
+Newline characters are more debatable, because some people use them to make wikicode more readable.",1368684616,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","(In reply to comment #0)
+> Single newlines have no effect on the way a wiki page is displayed.
+> So they should be ignored in a WYSIWYG editor.
+> 
+> Example: Third line at
+> http://en.wikipedia.org/wiki/
+> Content_Management_Interoperability_Services#Specification_progress_.
+> 26_TC_members
+
+Yeah, this is a bit of a mess. In wikitext (except in some circumstances like <pre>s), \n is a whitespace character, rendered as either a space or as nothing depending on the things around it, but \n\n is ""</p><p>"".
+
+We could:
+
+* Silently strip non-conformant wikitext syntax like this on ingest, but this would mean that VisualEditor would not play well with other, wikitext-based users.
+
+* Show the newline as a line break in VisualEditor - in a way that (a) doesn't look like a new paragraph/context has started, and (b) doesn't look like <br />s will look, either, and in some way conveys the fact that it's different.
+
+* (Current behaviour) Show the newline as a special kind of character in VisualEditor - in a way that (a) doesn't look like a 'real' new line, because it isn't.
+
+* Silently not show the new line as such (but instead as… a space?), which is prone to having users accidentally alter them without intention, again causing problems for intermixed VisualEditor and wikitext editor sessions.
+
+What are your thoughts?",1368110457,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
+Put the cursor somewhere in the text.
+Type ""Enter"" 2 times.
+Type ""Backspace"" 2 times.
+
+Expected: as original
+Actually: The newlines remain
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368089280,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-2f2dgqt54eqesg4exgwo,task_description,resolved
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox",This is now fixed in live.,1370445778,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","Just reproduced on Firefox 21.0 / fresh install of Ubuntu Linux 2013.04
+Nothing special appears in the web console.",1369662058,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox",Browser information highly welcome. Reopening for the time being.,1369661193,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","When will the master fixes be deployed?
+The situation is now horrible in production, with so many bugs that I am wondering whether it is even worth reporting them...",1369635503,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","I just tried, it is a worse problem now, text is lost.",1369277166,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","**orbit** wrote:
+
+I'm not able to reproduce this one either. I experience other problems relating to Enter and Backspace on Firefox (fixed in Master) but not what you've described. I'm going to close this ticket, but please reopen if you have additional information.",1369260407,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+PostEdit: Core-ify this,"As discussed with Steven W. just now, we should move this into MW core (so, amongst other things, VisualEditor can depend on it and not have to re-invent the wheel).
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=16066",1368050160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ju6nd3s77iuekvlfhra5,task_description,resolved
+PostEdit: Core-ify this,"That's a cherry-pick back to wmf5, so no wikis that currently have PostEdit will lose it when we disable the extension.",1370051316,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,Related URL: https://gerrit.wikimedia.org/r/66316 (Gerrit Change I01cfc0630c3a505af82922844b5e70c1d61f3c1d),1370051236,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,"(In reply to comment #1)
+> Related URL: https://gerrit.wikimedia.org/r/66137 (Gerrit Change
+> I01cfc0630c3a505af82922844b5e70c1d61f3c1d)
+
+Merged.",1370049933,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,"Just for posterity, I'm noting bug 16066 here.",1369960333,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,"(In reply to comment #2)
+> I should note that one extension depending on another is *not* a legitimate
+> reason for moving the dependency into the core. That said, I still agree with
+> the merging of this extension since it's a trivial feature.
+
+Yes, I agree completely. There had already been wide agreement that this should be moved into core; the VisualEditor requirement is just a spur.",1369941490,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,"(In reply to comment #0)
+> As discussed with Steven W. just now, we should move this into MW core (so,
+> amongst other things, VisualEditor can depend on it and not have to re-invent
+> the wheel).
+
+I should note that one extension depending on another is *not* a legitimate reason for moving the dependency into the core. That said, I still agree with the merging of this extension since it's a trivial feature.",1369941304,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,Related URL: https://gerrit.wikimedia.org/r/66137 (Gerrit Change I01cfc0630c3a505af82922844b5e70c1d61f3c1d),1369937979,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","We use textarea which means that browsers don't suggest text from previous uses.
+
+**See Also**:
+{T53903}
+{T54859}
+{T54085}",1368048660,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rc4yhxp2tlzilezhonck,task_description,resolved
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Do we consider this fixed now then ?,1561123591,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",It works nicely!,1558647083,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",It looks nice!,1558647068,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5135349, @Esanders wrote:
+> The above patch stops the first item being highlighted automatically. You can test the effect on live by pasting `ve.init.target.saveDialog.editSummaryInput.lookupHighlightFirstItem = false;` into the console after the save dialog has opened.
+
+This worked nicely. Thanks much!
+
+>>! In T50274#5209037, @matmarex wrote:
+> @izno Now done in <https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VisualEditor/+/512227>. I think we were still waiting for MediaWiki to be updated to use the new version of OOUI of something.
+
+Coolio.",1558646270,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",@izno Now done in <https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VisualEditor/+/512227>. I think we were still waiting for MediaWiki to be updated to use the new version of OOUI of something.,1558639964,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5136148, @Esanders wrote:
+>>>! In T50274#5135937, @Izno wrote:
+>> BTW since you're in the area there's a TODO there that was waiting on what is now a task that you closed a week or two ago.
+> 
+> Sorry, I'm not sure what you're referring to, can you provide a link?
+
+```lang=javascript
+	// HACK: Disable pending animation. Should be made an upstream option (T220204)
+	// Parent method
+```
+
+{T220204}
+",1556156399,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5136148, @Esanders wrote:
+>>>! In T50274#5135937, @Izno wrote:
+>> BTW since you're in the area there's a TODO there that was waiting on what is now a task that you closed a week or two ago.
+> 
+> Sorry, I'm not sure what you're referring to, can you provide a link?
+
+```lang=php
+	// HACK: Disable pending animation. Should be made an upstream option (T220204)
+	// Parent method
+```
+
+{T220204}
+",1556156352,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5135937, @Izno wrote:
+> BTW since you're in the area there's a TODO there that was waiting on what is now a task that you closed a week or two ago.
+
+Sorry, I'm not sure what you're referring to, can you provide a link?",1556142593,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5135349, @Esanders wrote:
+> The above patch stops the first item being highlighted automatically. You can test the effect on live by pasting `ve.init.target.saveDialog.editSummaryInput.lookupHighlightFirstItem = false;` into the console after the save dialog has opened.
+
+BTW since you're in the area there's a TODO there that was waiting on what is now a task that you closed a week or two ago.",1556136821,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Change 506191 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] EditSummaryWidget: Don't highlight first automatically
+
+[[https://gerrit.wikimedia.org/r/506191]]",1556126337,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",The above patch stops the first item being highlighted automatically. You can test the effect on live by pasting `ve.init.target.saveDialog.editSummaryInput.lookupHighlightFirstItem = false;` into the console after the save dialog has opened.,1556125232,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Change 506191 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] EditSummaryWidget: Don't highlight first automatically
+
+[[https://gerrit.wikimedia.org/r/506191]]",1556125155,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5135228, @LucasWerkmeister wrote:
+> Is it possible to opt out of this feature until that’s fixed?
+
+No, but it shouldn't be too hard to fix. In the meantime you can press escape before ctrl+enter.
+
+",1556124739,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5106435, @Trizek wrote:
+> Great feature. <3 
+> Can we have a way to delete misspelled sentences? Thanks!
+
+The edit summaries are pulled from the API and old edit summaries are immutable so I don't see an easy fix for this without using another storage system. Suggestions welcome.",1556124638,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5107339, @Izno wrote:
+> My only problem: when I have entered a summary, the drop down appears. When I hit the hotkeys for save, the system will complete the summary with the top item whatever the value of my original summary was. (This is not how it works in old WTE.)
+
+This is a //big// problem for me as well. My most common summary on talk pages or project discussion pages is just “reply”, but the first suggestions are all like “reply (something something)”, “reply, something else”, etc. When I press Ctrl+Enter out of habit – for years, VisualEditor has trained me that Ctrl+Enter in the summary field means “save” – then it will “complete” my edit summary with some gibberish that makes no sense in the current context, and if I don’t notice it I’ll save an edit with a nonsense summary.
+
+Is it possible to opt out of this feature until that’s fixed?",1556123623,PHID-USER-7raa3vx5zsq6a56gil3q,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5107851, @Whatamidoing-WMF wrote:
+>>>! In T50274#5106435, @Trizek wrote:
+>> Great feature. <3 
+>> Can we have a way to delete misspelled sentences? Thanks!
+> 
+> No.  But if you make 200 more edits, it'll automagically go away.  The tool only looks back at your most recent 200 edit summaries.
+
+So I have to be patient. And be careful: I've already accidentally entered some bad summaries while editing. :/",1555530842,PHID-USER-fptvc452oby6t6mwcy2u,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5107874, @Whatamidoing-WMF wrote:
+> 
+> (In the meantime, the workaround is to hit the Escape key.)
+
+(And then hit Ctrl + Enter again.)",1555098678,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5107874, @Whatamidoing-WMF wrote:
+> @Esanders, Izno's problem is going to drive me nuts.  When there's an exact match, it needs to use that exact match, and not suggest something longer.  If I've typed `r`, and the options it finds are 35 instances of `r` and one of `Re-ping` in my last 200 edit summaries, then it should definitely be suggesting `r` and not the other longer one. 
+> 
+> (In the meantime, the workaround is to hit the Escape key.)
+
+(And then hit Ctrl + Enter again.)",1555098668,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","@Esanders, Izno's problem is going to drive me nuts.  When there's an exact match, it needs to use that exact match, and not suggest something longer.  If I've typed `r`, and the options it finds are 35 instances of `r` and one of `Re-ping` in my last 200 edit summaries, then it should definitely be suggesting `r` and not the other longer one. 
+
+(In the meantime, the workaround is to hit the Escape key.)",1555094625,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","@Esanders, Izno's problem is going to drive me nuts.  When there's an exact match, it needs to use that exact match, and not suggest something longer.  If I've typed `r`, and the options it finds are 35 instances of `r` and one of `Re-ping` in my last 200 edit summaries, then it should definitely be suggesting `r` and not the other longer one. ",1555094590,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5106435, @Trizek wrote:
+> Great feature. <3 
+> Can we have a way to delete misspelled sentences? Thanks!
+
+No.  But if you make 200 more edits, it'll automagically go away.  The tool only looks back at your most recent 200 edit summaries.",1555094341,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I agree, this is well done.
+
+My only problem: when I have entered a summary, the drop down appears. When I hit the hotkeys for save, the system will complete the summary with the top item whatever the value of my original summary was. (This is not how it works in old WTE.)
+
+The particular issue was that I wanted a summary of ""clean table"", but after having entered the entire thing in it removed the exact match and attempted to add the lengthier summary after hitting cntrl + enter, and then chose //not// to save. (The biggest win for me is that the hotkeys should always save regardless of the current value of the dropdown.)
+
+{F28628688}
+
+{F28628692}
+
+{F28629206}
+
+Happy to split this to a different task if it seems like a significant chunk of additional work...
+",1555081974,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I agree, this is well done.
+
+My only problem: when I have entered a summary, the drop down appears. When I hit the hotkey for save, the system will complete the summary with the top item whatever the value of my original summary was. (This is not how it works in old WTE.)
+
+The particular issue was that I wanted a summary of ""clean table"", but after having entered the entire thing in it removed the exact match and attempted to add the lengthier summary after hitting cntrl + shift + s, and then chose //not// to save. (The biggest win for me is that the hotkeys should always save regardless of the current value of the dropdown.)
+
+{F28628688}
+
+{F28628692}
+
+{F28629206}
+
+Happy to split this to a different task if it seems like a significant chunk of additional work...
+",1555080996,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I agree, this is well done.
+
+My only problem: when I have entered a summary, the drop down appears. When I hit the hotkey for save, the system will complete the summary with the top item whatever the value of my original summary was. (I am fairly certain this was not the behavior with non-VE editor.
+
+The particular issue was that I wanted a summary of ""clean table"", but after having entered the entire thing in it removed the exact match and attempted to add the lengthier summary after hitting cntrl + shift + s, and then chose //not// to save. (The biggest win for me is that the hotkeys should always save regardless of the current value of the dropdown.)
+
+{F28628688}
+
+{F28628692}
+
+{F28629206}
+
+Happy to split this to a different task if it seems like a significant chunk of additional work...
+",1555080704,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Great feature. <3 
+Can we have a way to delete misspelled sentences? Thanks!",1555059406,PHID-USER-fptvc452oby6t6mwcy2u,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Good job!,1555047671,PHID-USER-4nsetzljuvrlickb5xoz,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Wonderful and seems to be done,1555019166,PHID-USER-timi4nkerc272muhuatw,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Change 495451 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Edit summary autocomplete
+
+[[https://gerrit.wikimedia.org/r/495451]]",1554399877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5016202, @Esanders wrote:
+> It doesn't appear to work yet in Chrome/FF: https://codepen.io/edg2s/pen/eXGdVM
+
+Nor in Safari.",1552404027,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",It doesn't appear to work yet in Chrome/FF: https://codepen.io/edg2s/pen/eXGdVM,1552338121,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5012835, @gerritbot wrote:
+> Change 495451 had a related patch set uploaded (by Esanders; owner: Esanders):
+> [mediawiki/extensions/VisualEditor@master] Edit summary autocomplete
+> 
+> [[https://gerrit.wikimedia.org/r/495451]]
+
+Why doesn't this make use of T50274#4048873 ? It looks like Firefox, Webkit, and Chromium all support autocomplete (even though [[https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea | Mozilla.org]] indicates otherwise, the link to the Chromium indicates the bug is fixed since Jan 2018)...",1552151736,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Change 495451 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Edit summary autocomplete
+
+[[https://gerrit.wikimedia.org/r/495451]]",1552137996,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Proposed in [[https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Editing/Autocomplete_summaries_in_VisualEditor|Community Wishlist Survey]],1543326392,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","According to https://developer.mozilla.org/en-US/Firefox/Releases/59#HTML Firefox now supports autocompletion of textareas, so it should actually be possible to have native autocomplete suggestions, at least in Firefox.",1521014264,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Proposed to #community-wishlist-survey-2017 ,1510324177,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#3234411, @Schnark wrote:
+> But neither will give results for users not logged in. Even if they have a static IP, `mw.user.getName()` will only return `null`.
+
+There are a bunch of features that don't work for logged-out users; I'd not worry too much about that.",1493924564,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#2137790, @Esanders wrote:
+> Fetch and filter recent commit messages:
+> 
+> https://gist.github.com/edg2s/f7db01d240ad3c83d183
+
+I don't think that `list: 'recentchanges'` is the best approach, as it will only give you summaries from the last month. When you are not very active, these are very few, so won't help much. In my script https://de.wikipedia.org/wiki/Benutzer:Schnark/js/veSummary.js, I instead decided to use `list: 'usercontribs'` instead.
+But neither will give results for users not logged in. Even if they have a static IP, `mw.user.getName()` will only return `null`.",1493889939,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","A solution could also be HTML5 `contenteditable`, at least its support in browsers is acceptable. (see [[ http://stackoverflow.com/questions/13324822/autocomplete-with-contenteditable-div-instead-of-textarea-doesnt-seem-to-work | StackOverflow question about this topic ]])",1482075467,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","A solution could also be HTML5 `contenteditable`, at least its support in browsers is acceptable. (see [[ http://stackoverflow.com/questions/13324822/autocomplete-with-contenteditable-div-instead-of-textarea-doesnt-seem-to-work | StackOverflow question to this topic ]])",1482075451,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","A solution could also be HTML5 `contenteditable`, at least its support in browsers is acceptable. (see [[ http://stackoverflow.com/questions/13324822/autocomplete-with-contenteditable-div-instead-of-textarea-doesnt-seem-to-work | StackOverflow question to the topic ]])",1482075440,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(Actually, Chrome does support autocomplete=""street-address"", huh. But that doesn't really help us here, it doesn't remember and autocomplete values in textareas on its own and there doesn't seem to be a way to make it do that.)",1481761162,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","It's not possible to make <input> wrap. If anything, it could be possible to make <textarea> have autocomplete (nothing in the spec prohibits it, the attribute [[ https://html.spec.whatwg.org/multipage/forms.html#the-textarea-element| is valid on textarea]] and the new 'autocomplete' values include [[https://html.spec.whatwg.org/multipage/forms.html#attr-fe-autocomplete-street-address| one that is only valid on multiline content]]). But no browser seems to actually support this.",1481760141,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(That was https://gerrit.wikimedia.org/r/#/c/212795/, it tried to dynamically swap between <input type=text> and <textarea>.)",1481759634,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Bartosz had a go at this a few years ago, but then I pointed out some IME issues and he gave up. I think my API approach is probably the simplest.",1481759433,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","How plausible would it be to use `input` but magically make it word wrap, even though the HTML spec says it mustn't?",1481754213,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Raising priority now that we have the same problem in VE source mode (NWE).,1481754015,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I have a (very hackish) user script for providing access to previous edit summaries: https://de.wikipedia.org/wiki/Benutzer:Schnark/js/veSummary.js If anybody wants to use code from there to fix this in VE itself, feel free to do so.",1473756944,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Fetch and filter recent commit messages:
+
+https://gist.github.com/edg2s/f7db01d240ad3c83d183",1458492511,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I think this should be low priority. Only power users need quick access to commonly used edit summaries, and these power users will by definition know OS-wide tools like autohotkey or ditto which can do the job much more comfortably.",1387232471,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","The main threads in VE/F:
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_05#Edit_summaries_have_no_.27memory.27
+and
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_06#Predictive_texting_in_edit_summaries
+and
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_06#Edit_summaries_-_menu_of_recently-used.3F
+and
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Speed.2C_Edit_Summary.2C_and_Limitations
+
+
+
+Closely related are:
+
+Bug 42139 (""There is no preview of edit summaries"") - Wanted, so that we can test WP:shortcut links etc are correctly-targeted.
+
+Bug 50961 (""Provide simultaneous access to editor and edit summary"") - So that we don't have to remember everything we did, after a multitask edit.",1374776456,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #8)
+> A suggested list populated with recent edit summaries will be really useful
+> when VE is extended to talk namespace.
+
+We're not planning to make VisualEditor work with talk pages, but instead this will be done by Flow (which will use VisualEditor for editing content).
+
+That said, we still think this would be valuable, and it's definitely in our plans.",1373481862,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","A suggested list populated with recent edit summaries will be really useful when VE is extended to talk namespace. Almost every time I close an RfD as something other than delete, I make an edit to the redirect's talk page with the summary ""Noting old RFD"" or ""Note old RFD and tag for relevant WikiProjects"" (depending whether they are already tagged or not).",1373479736,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #6)
+> (In reply to comment #1)
+> > ...or implement our own autocomplete?
+> 
+> However, just brainstorming, to address Raimond's use-case in comment 3, it
+> may
+> be possible to query the most recent X edit summaries a user has used and
+> implement a suggestion feature based on those. That might cover the repeated
+> edits use-case.
+
+That's pretty much what I meant. The autocomplete would populate from recent commit messages, or they would just be shown in a dropdown.",1371146265,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #1)
+> ...or implement our own autocomplete?
+
+It depends what the use-case is. Personally, I like the current multi-line input and my browser stopped remembering my inputs for <input>s long ago (perhaps when I switched from Firefox to Chrome).
+
+However, just brainstorming, to address Raimond's use-case in comment 3, it may be possible to query the most recent X edit summaries a user has used and implement a suggestion feature based on those. That might cover the repeated edits use-case.",1371079046,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Rephrased bug summary. ""textbox"" doesn't exist. There is ""input"" and ""textarea"" both are ""form fields"".",1370829536,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #3)
+> Browser's autosuggestion/complete is the most used function during editing
+> Wikipedia, especially when I do similar edits. Every time I test the VE is
+> miss this function because the field is a textarea instead of an input field.
+> It's really annoying to type every time the summary instead of selecting out of
+> previous summaries.
+
+Sure, but this functionality isn't possible for proper editable surfaces with rich text, links and other HTML items that these fields will allow.",1368992892,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Browser's autosuggestion/complete is the most used function during editing Wikipedia, especially when I do similar edits. Every time I test the VE is miss this function because the field is a textarea instead of an input field. It's really annoying to type every time the summary instead of selecting out of previous summaries.",1368991970,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #1)
+> ...or implement our own autocomplete?
+
+Possibly. Given that we are intending to replace this wikitext field with a full VE micro-surface (with the limited scope that log entries allow), that might be a bit fiddly, though. There's also not currently a useful API to query ""useful edit summaries"" from. Marking as a longer-term consideration.",1368979017,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",...or implement our own autocomplete?,1368903301,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: Alienation shield for images in table are not the right size, so images are still clickable","Images in a table are incompleted alienated and still clickable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Liste_der_Hochh%C3%A4user_in_Deutschland",1368003600,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-x7lpmfetdbteus26qx4l,task_description,resolved
+"VisualEditor: Alienation shield for images in table are not the right size, so images are still clickable","(In reply to comment #0)
+> Images in a table are incompleted alienated and still clickable.
+
+This is fixed by the new image code which will be coming very soon (but is delayed to finish editing image properties). Marking as a dupe of that bug.
+
+*** This bug has been marked as a duplicate of bug 37870 ***",1369093449,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-x7lpmfetdbteus26qx4l,task_subcomment,NA
+VisualEditor: Don't close/re-open annotation when pasting text into a comparable context,"Not sure whether this is ContentEditable, DataModel or LinearModel.
+
+When pasting italicised text (from elsewhere on the same page) into an already italicised sentence we currently close, re-open, close, re-open that annotation.
+
+Steps to reproduce problem:
+* start with:
+  <p><i>Original text here.</i></p><p><i>Something else there.</i></p>
+* select ""else""
+* copy
+* select ""text""
+* paste to replace
+* end state:
+  <p class=""ve-ce-branchNode""><i class=""ve-ce-TextStyleAnnotation ve-ce-TextStyleItalicAnnotation"">Original </i><i class=""ve-ce-TextStyleAnnotation ve-ce-TextStyleItalicAnnotation"">else</i><i class=""ve-ce-TextStyleAnnotation ve-ce-TextStyleItalicAnnotation""> here.</i></p>
+
+Now this wouldn't be a major issue (merely inefficient) if it weren't for bug 48194 in Parsoid.
+
+Real example:
+* Intended edit: https://www.mediawiki.org/w/index.php?title=Watchlist_wishlist&diff=686477&oldid=686247
+* Actual edit as seen in the Review and save dialog of VisualEditor (and saved as-is): https://www.mediawiki.org/w/index.php?title=Watchlist_wishlist&diff=686475&oldid=686247
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1367894520,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-altic2tebpor7cfydf6y,task_description,resolved
+VisualEditor: Don't close/re-open annotation when pasting text into a comparable context,*** Bug 48489 has been marked as a duplicate of this bug. ***,1368726943,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-altic2tebpor7cfydf6y,task_subcomment,NA
+VisualEditor: Don't close/re-open annotation when pasting text into a comparable context,Confirmed on mediawiki.org,1368554438,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-altic2tebpor7cfydf6y,task_subcomment,NA
+VisualEditor: Don't close/re-open annotation when pasting text into a comparable context,"Timo, can you confirm this in master? I think it's been fixed by Ed's change to how annotations are compared…",1368228767,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-altic2tebpor7cfydf6y,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,"* Create an English article with a <ref> tag at the end of a paragraph
+* Set $wgLanguageCode = 'en-rtl';
+* View the article. You'll see something like ]My text[1 (this rendering seems wrong)
+* Edit the article in VE. The non-contiguous reference causes problems:
+** The phantom is rendered wrongly so it's not visible
+** When you select the reference, the selection looks really strange
+
+Should we wrap things in a <bidi> tag or whatever to ensure better rendering?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367879940,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ix6ll4i6ezero6wug475,task_description,resolved
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,Merged; closing.,1369783170,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,Assigning to Moriel then. :-),1367887908,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,"And it was Roan who suggested, and Krinkle who participating in the attempt of helping me understand.. THANKS for that!",1367883167,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,Related URL: https://gerrit.wikimedia.org/r/62540 (Gerrit Change I319285d23a4f0a0522cc793f1a6661cda31a1ebf),1367882987,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,"This is a CSS fix in the Cite extension. https://gerrit.wikimedia.org/r/#/c/61634/
+
+As Krinkle suggested, I'm fixing a small detail again (position 'top') but updating the Cite extension should fix this problem. I'll link the new correction to this bug and submit the fix shortly.",1367881902,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: JS error on (null) diffing [[BMW 801]] but only if debug=false,"Make a null edit (space and backspace), then trigger a diff. JS error thrown in Firefox but not Chrome:
+
+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
+
+However, for debug=true, no such error occurs. Is this just going to be a transient RL issue?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1367874000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bdvf6u5xglbisa5hqfhd,task_description,resolved
+VisualEditor: JS error on (null) diffing [[BMW 801]] but only if debug=false,*** Bug 48193 has been marked as a duplicate of this bug. ***,1368023940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bdvf6u5xglbisa5hqfhd,task_subcomment,NA
+VisualEditor: JS error on (null) diffing [[BMW 801]] but only if debug=false,"This has been fixed for me in FF since yesterday evening. From chatting with Roan last night I think it was a deployment / ResourceLoader issue.
+
+Resolving as fixed.",1367972703,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bdvf6u5xglbisa5hqfhd,task_subcomment,NA
+VisualEditor: JS error on (null) diffing [[BMW 801]] but only if debug=false,Happens in Chromium 26.0.1410.43 too.,1367874746,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-bdvf6u5xglbisa5hqfhd,task_subcomment,NA
+VisualEditor: Throttle or otherwise handle large copy-paste input,"I watched a user using Chrome paste a 32400-character buffer of special characters into VE.  Chrome became unresponsive. 
+
+This user then did that in multiple tabs and the entire computer became unresponsive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367867040,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-o742mr6hjh6wsdblaanj,task_description,open
+VisualEditor: Throttle or otherwise handle large copy-paste input,Marking as an enhancement with normal priority (nice-to-have).,1367870640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o742mr6hjh6wsdblaanj,task_subcomment,NA
+VisualEditor: Serve interface components as SVGs over PNGs to any browser which supports it,"(Provided we are happy with the rendering quality)
+
+Currently we only serve SVGs when window.devicePixelRatio > 1.
+
+On suggested test for SVG support is:
+
+document.createElementNS && document.createElementNS( 'http://www.w3.org/2000/svg', 'svg' ).createSVGRect
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367837220,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pgpcd7rvhd6x44lw4xo5,task_description,resolved
+VisualEditor: Serve interface components as SVGs over PNGs to any browser which supports it,Merged for wmf4.,1368135541,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pgpcd7rvhd6x44lw4xo5,task_subcomment,NA
+VisualEditor: Serve interface components as SVGs over PNGs to any browser which supports it,Related URL: https://gerrit.wikimedia.org/r/62959 (Gerrit Change Iafe8cd290fb195369776f51a96b6de4a51577b89),1368095219,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pgpcd7rvhd6x44lw4xo5,task_subcomment,NA
+VisualEditor: Serve interface components as SVGs over PNGs to any browser which supports it,Let's do this. Trevor says we're happy with the rendering quality and the device load for desktop; I suggest keeping the PNGs around for mobile clients.,1368050588,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pgpcd7rvhd6x44lw4xo5,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,"As the title says: when the VisualEditor is active, the drop down menu (p-caction) under Vector skin is dropped down behind the VE toolbar, making it impossible to click on. May be a simple z-index issue.",1367661720,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-6kpwltejynowd5ns5iud,task_description,resolved
+VisualEditor: Vector drop down menu hidden behind toolbar,Merged; thanks Kaldari! Will go out in wmf4.,1368205844,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,Assigning given that Kaldari's fixing it in core for us. :-),1368150497,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,Related URL: https://gerrit.wikimedia.org/r/63099 (Gerrit Change I61daea50209d040f7e0f71207a4e90998c15083f),1368146651,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,"Unfortunately, this was caused by the fix to bug 37158.
+https://gerrit.wikimedia.org/r/#/c/31288",1368144377,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,Also brought up here: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=553770320#Notifications_gadget.27s_z-index,1367845014,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,"This also holds true for Echo, which also has z-index -100.",1367842628,PHID-USER-t4cbxxxhiswoecybwxy2,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Table captions were alienated so looked wrong and couldn't be edited,"Expected layout
+
+I included two screenshots, illustrating the problem.
+
+Apple Safari 6, Mountain Lion
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/Meurchin
+
+**Attached**: {F10895}",1367650560,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-hg7swbc4ekjgxojfr5bz,task_description,resolved
+VisualEditor: Table captions were alienated so looked wrong and couldn't be edited,This is fixed in master (see gerrit 60940) and will be deployed to the English Wikipedia on Monday as part of the wmf3 roll-out. You can see how it should work in a test page on MediaWiki.org: https://www.mediawiki.org/wiki/VisualEditor:TableCaptionTest,1367681845,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hg7swbc4ekjgxojfr5bz,task_subcomment,NA
+VisualEditor: Table captions were alienated so looked wrong and couldn't be edited,"Created attachment 12258
+Content edit result
+
+**Attached**: {F10896}",1367650645,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-hg7swbc4ekjgxojfr5bz,task_subcomment,NA
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"In Firefox 20.0.1:
+
+1. Edit a page that has a bulleted list.
+2. Place the cursor on the first bullet item.
+3. Click the ""Bullet List"" button. The first bullet item loses its bullet. (Correct.)
+4. Click the ""Bullet List"" button a second time. The first bullet comes back (correct), but there is now a blank line displayed below it.
+
+Similarly, if you remove & add a bullet in the middle of the list, you get blank lines above AND below the item.
+
+Similarly, if you do this with a numbered list, the blank line breaks the numbering: the list items below the blank line start over from ""1"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367598960,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-yr7732vg2ebd5ndyalb6,task_description,open
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"FWIW, I also just checked OpenOffice.org, and they also simply remove and restore the bullet, keeping a single bulleted list.",1368137966,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-yr7732vg2ebd5ndyalb6,task_subcomment,NA
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"(In reply to comment #2)
+> Interesting point. I think nontechnical end-users will have a different
+> perspective, however. Both Microsoft Word and Google Docs will produce a
+> single bulleted list as the result. Your users are going to be accustomed to
+> that behavior.
+
+Possibly.
+
+> When an end-user clicks the button the first time, and the bullet disappears,
+> they won't be thinking that ""a bulleted list has become two lists."" They'll
+> simply think ""a bullet symbol has been removed.""
+
+Not two lists - they'll have a paragraph and a list.
+
+I'll make sure we do some real-world tests with non-technical people to come to a decision on this.",1368135721,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yr7732vg2ebd5ndyalb6,task_subcomment,NA
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"Interesting point. I think nontechnical end-users will have a different perspective, however. Both Microsoft Word and Google Docs will produce a single bulleted list as the result. Your users are going to be accustomed to that behavior.
+
+When an end-user clicks the button the first time, and the bullet disappears, they won't be thinking that ""a bulleted list has become two lists."" They'll simply think ""a bullet symbol has been removed.""",1368130302,PHID-USER-o5tv5cyrple4fn5xqopm,PHID-TASK-yr7732vg2ebd5ndyalb6,task_subcomment,NA
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"(In reply to comment #0)
+> In Firefox 20.0.1:
+> 
+> 1. Edit a page that has a bulleted list.
+> 2. Place the cursor on the first bullet item.
+> 3. Click the ""Bullet List"" button. The first bullet item loses its bullet.
+> (Correct.)
+> 4. Click the ""Bullet List"" button a second time. The first bullet comes back
+> (correct), but there is now a blank line displayed below it.
+> 
+> Similarly, if you remove & add a bullet in the middle of the list, you get
+> blank lines above AND below the item.
+> 
+> Similarly, if you do this with a numbered list, the blank line breaks the
+> numbering: the list items below the blank line start over from ""1"".
+
+Yes, because otherwise we'd be unexpectedly merging a <p> with a following <ul> (or whatever). You can always actively choose to merge the lists from this position by deleting the blank line between the lists (technically, this is a slug).
+
+This is the deliberately-chosen behaviour for this. I take it you'd expect lists to instead automatically merge, and you'd have to split them rather than the other way around? X followed by X is not generally a direct reverse step (that's what undo is for), but you expected it to work that way around?",1368127673,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yr7732vg2ebd5ndyalb6,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"The indent and outdent buttons are always grayed out.
+
+(reported at http://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Alpha2013-04#Link_einbinden_.2F_Einzug)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367512920,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-hvvrpcxmtlfovm73otnw,task_description,open
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"Hi,
+
+is this task still active? Indenting (of text) is a much requested feature on my companies wiki.",1542962428,PHID-USER-a5b43na73s7s5vqzeaur,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"(In reply to Spinningspark from comment #6)
+
+Sorry, posted this in wrong place.  It was intended for bug 59849",1412132162,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"I don't know if this is related, or whether it should be a new bug.  In this edit:
+
+https://en.wikipedia.org/w/index.php?title=User:Spinningspark/Work_in_progress/Mobility_analogy&diff=626824709&oldid=626823704
+
+VE adds a number of spurious indents.  The intended edit was to swap over the order of two blocks of text containing math markup.  Very frustrating that the problem could not even be fixed from within VE since indenting does not function in general.",1412131984,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,*** Bug 51530 has been marked as a duplicate of this bug. ***,1395359458,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"(In reply to comment #3)
+> Would this also allow the tab key to be used for paragraph indenting (like
+> for lists), or should that be filed as a separate bug report?
+
+That'd be the same (the tab and shift-tab keys are bonded to these buttons), so no need for a separate bug report.",1375765565,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"**mcdevitd** wrote:
+
+Would this also allow the tab key to be used for paragraph indenting (like for lists), or should that be filed as a separate bug report?",1375725373,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"This would be lovely (as a nice-to-have) to get done for the beta.
+
+In practical terms, it means that <p>Foo</p> gets wrapped into <dl><dd><p>Foo</p></dd></dl> and vice versa; all the DM/Parsoid plumbing is there, just needs the indent/outdent commands to be aware of how to operate in the paragraph/preformatted context.",1368836909,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"These are for list indenting currently, and do not (yet) do text block indenting. Setting as an enhancement, likely to be after the 'beta' is released.",1367545334,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Support language variant conversion labels,"Conversion labels shown
+
+The conversion labels (i.e. { } ) for wikis like zhwiki is shown when editing using the VisualEditor.
+
+Those labels should be hidden, or otherwise newbies using the editor will break them easily.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F10580}",1367389920,PHID-USER-ixwg3kf22idjy7x4ncxf,PHID-TASK-maehbrz5znwar2qitk5b,task_description,duplicate
+VisualEditor: Support language variant conversion labels,"This is a mess; Parsoid currently has no support for the language variant conversion syntax in wikitext, but when it does (bug 41716) we should work on this to make it easy to set the different variants.
+
+Sorry that we are not really ready yet for zh; I feel that this is a blocker to deployment in zh, so until it's fixed I think VisualEditor will remain in alpha opt-in deployment there for now.",1367435394,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-maehbrz5znwar2qitk5b,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"From the fall out of bug 47457's resolution:
+
+(bug 47457 comment #63 by Liangent)
+> (bug 47457 comment #54 by Krinkle)
+> > Change-Id: Ic3d0c937268d0943d2f770f3ca18bcf4e1eed346
+> 
+> This fix causes breakage of any user of site scripts which assume that
+> they're
+> loaded before $(document).ready(). Maybe someone can move jQuery.ready() call
+> to a position just before </body> and after all other script references?
+
+(bug 47457 comment #64 by matma.rex)
+> And it also breaks the old 'mwCustomEditButtons' interface to add custom
+> buttons to the old edit toolbar, which apparently everyone and their dog are
+> using across the wikis. (Since the user JS is loaded from the bottom queue,
+> but
+> the toolbar script either from the top or using inline <script> tags with
+> $.ready inside.)
+> 
+> Reopening. Moving the jQuery.ready() call after the bottom queue seems like a
+> good idea.
+
+
+(bug 47457 comment #66 by Brad Jorsch)
+> (bug 47457 comment #63 by Liangent)
+> > Maybe someone can move jQuery.ready() call to a position just before 
+> > </body> and after all other script references?
+> 
+> (bug 47457 comment #64 by matma.rex)
+> > Moving the jQuery.ready() call after the bottom queue seems like a good idea.
+> 
+> We tried that, see patchset 5 in https://gerrit.wikimedia.org/r/#/c/61057/5.
+> It didn't work.
+> 
+> But unless the browsers were delaying the DOMContentLoaded event until after
+> the async-loaded scripts in the bottom queue were loaded, I don't know how
+> this wasn't already a problem. Krinkle, any ideas?
+
+A few important questions I'd like answered:
+
+@Liangent: Can you given an example where it matters for a user script whether the document becomes ready before or after they are loaded? The user scripts are loaded from the bottom of the <body> before </body>. Practically the document is already ready at this point, just $(document).ready() hasn't fired yet. Any user script code that isn't wrapped in $(document).ready() will still execute at exactly the same time. Any user script code that *is* wrapped in $(document).ready() will now execute immediately after loading instead of... immediately after loading. Exactly the same, not?
+
+@Matma.rex: You mean the fact that the deprecated mwCustomEditButtons global (unlike the mw.toolbar interface) is inspected only once by mediawiki.action.edit.js, namely at the domready event. And if it is triggered before the user script, adding to that array will become a no-op.
+
+Though there is a lot of usage of this feature, lets not forget the context:
+
+* The mwCustomEditButtons interface is for the classic toolbar (aka ""Monobook editor"", though Vector users can also disable WikiEditor to get to it). This is already a large minority of users.
+* The mwCustomEditButtons interace has been deprecated in favour of mw.toolbar.addButton, which I created especially for the legacy toolbar users last year to address the many declined bug reports for mwCustomEditButtons which could not be otherwise addressed because mwCustomEditButtons is beyond repair, it is a flawed concept and it keeps breaking for many reasons.
+
+I don't think anything related to mwCustomEditButtons can justify a change of any kind unless it comes at absolutely no overhead and downside.
+
+@Brad Jorsch: It seems that the Firefox bug with document.write being disabled before DOMContentReady is worse than we thought. It is disabled even before the end of the </body> has been reached. We found through trial-and-error that placing it after the main content but before the bottom queue worked.
+
+As Brad pointed out, $.ready being triggered earlier makes no difference for the bottom queue because they are loaded asynchronously, they always execute without blocking the parser or the DOM ready event. In fact (while designing this) Roan and I made very sure to test this across the entire board of browsers we even remotely support (IE6-10, FF2-17, Chrome10-23, Opera9-11.x). And in any browser that we couldn't load it async, we scheduled the addScript to after dom-ready manually (only in Opera).
+
+However note that the user scripts (like the site scripts) are *not* loaded through mw.loader because we still support legacy global scope for them. They are loaded by a hardcoded script tag in the DOM. Which means they are blocking and used to block dom-ready, and now they run after dom-ready (well, they still block dom-ready, but we trigger that callback queue earlier).
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50310",1367327220,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nvh5ejbvixlonbrch4jd,task_description,declined
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #10)
+...
+> I'd recommend we add some code to mediawiki.action.edit to periodically check
+> mwCustomEditButtons. Then immediately deprecate it (not removing it, just
+> marking it as deprecated) and phasing it out over the following weeks (I'd
+> like
+> to add it to the js-deprecations train roll-out in May which will introduce
+> mw.log.deprecate and console.warn messages that users can use to easily see
+> if
+> they are using something that is deprecated).
+
+I requested this on bug 50310 so we don't forget.",1372357726,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"Closing this as wontfix.
+
+The classic edit toolbar has long been deprecated. The default was replaced with WikiEditor on Wikimedia in a 2010 deployment. And since a few releases it is now bundled with new MediaWiki releases as well.
+
+Since then development has started on [[mw:VisualEditor]] which will be launched soon.
+
+Despite all that, I've spend a fair amount of effort over the last months to come up with a brand new API for the classic edit toolbar: mw.toolbar because mwCustomEditButtons is fundamentally flawed and cannot be repaired and kept up with the latest technologies.
+
+Any and all issues you may have with mwCustomEditButtons are from hereon invalid. Please use mw.toolbar instead. Note that mw.toolbar has nothing to do with WikiEditor or VisualEditor, it is a new API for the classic editor you are so familiar with.
+
+I can't make any promises for how long the classic toolbar and this new mw.toolbar will be supported, but at least it has been renewed to work with all the latest technologies so it should be a relatively cheap burdon for us to maintain.
+
+So, long story short: Change:
+
+> if ( wgAction === 'edit' ) {
+>     mwCustomEditButtons[mwCustomEditButtons.length] = {...};
+> }
+
+to:
+
+> if ( mw.toolbar ) {
+>     mw.toolbar.addButton( { ... } );
+> }
+
+If there are any bugs with that, please file a new bug report and be sure to mention ""mw.toolbar"" in its subject. I'll do my best to address if/when there are any issues.",1370831532,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"We fixed it with Nemo on IRC. For the record, this was because the script ran on all pages (not just edit ones). The simplest way to fix that was to wrap the button definitions in ""if ( mw.toolbar ) { ... }"".",1370805496,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #9)
+> billinghurst, this has nothing to do with switching to the new toolbar;
+> mw.toolbar.addButton works with and is intended for the old one, and the
+> change
+> is just a simple find and replace:
+> 
+>   Find:         mwCustomEditButtons[mwCustomEditButtons.length] = { ... }
+>   Replace with: mw.toolbar.addButton({ ... })
+> 
+> Just be careful about braces and parentheses.
+> 
+> Here's an example diff:
+> https://nl.wikipedia.org/w/index.php?title=Gebruiker:Romaine/vector.js&diff=37497149&oldid=37497060
+
+This solution didn't work for long, it just broke all JavaScript for me on Meta (most prominently, [[m:WM:LS]]) with:
+
+Timestamp: 09/06/2013 20:03:03
+Error: TypeError: mw.toolbar is undefined
+Source File: https://bits.wikimedia.org/meta.wikimedia.org/load.php?debug=false&lang=it&modules=user&only=scripts&skin=monobook&user=Nemo+bis&version=20130601T024617Z&*
+Line: 1
+
+[MediaWiki 	1.22wmf5 (bad4d50)]",1370801419,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #11)
+> (In reply to comment #9)
+> > billinghurst, this has nothing to do with switching to the new toolbar;
+> > mw.toolbar.addButton works with and is intended for the old one, and the
+> > change
+> > is just a simple find and replace:
+> > 
+> >   Find:         mwCustomEditButtons[mwCustomEditButtons.length] = { ... }
+> >   Replace with: mw.toolbar.addButton({ ... })
+> > 
+> > Just be careful about braces and parentheses.
+> > 
+> > Here's an example diff:
+> > https://nl.wikipedia.org/w/index.php?title=Gebruiker:Romaine/vector.
+> > js&diff=37497149&oldid=37497060
+> 
+> Thanks. This innovation had escaped me, and clearly a whole community that
+> was
+> using mwCustomEditButtons. I will relay this to the enWS community, and fix
+> our
+> help pages.
+> 
+> Can you recommend that right page to watch for these changes.  I thought
+> that I
+> had watched all the relevant pages where Krinkle does these components,
+> however, it is clear that this change wasn't evident for active changes.
+
+Clearly it was a long time ago as I have since found reference that it was broken in 1.18, but somehow it didn't break for all. Weird.",1367383460,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #9)
+> billinghurst, this has nothing to do with switching to the new toolbar;
+> mw.toolbar.addButton works with and is intended for the old one, and the
+> change
+> is just a simple find and replace:
+> 
+>   Find:         mwCustomEditButtons[mwCustomEditButtons.length] = { ... }
+>   Replace with: mw.toolbar.addButton({ ... })
+> 
+> Just be careful about braces and parentheses.
+> 
+> Here's an example diff:
+> https://nl.wikipedia.org/w/index.php?title=Gebruiker:Romaine/vector.
+> js&diff=37497149&oldid=37497060
+
+Thanks. This innovation had escaped me, and clearly a whole community that was using mwCustomEditButtons. I will relay this to the enWS community, and fix our help pages.
+
+Can you recommend that right page to watch for these changes.  I thought that I had watched all the relevant pages where Krinkle does these components, however, it is clear that this change wasn't evident for active changes.",1367382951,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #7)
+> So how hard would it be to get the site&user scripts to run first, then
+> $.ready, then the rest of the bottom queue? Then we could kill off
+> mwCustomEditButtons after announcing it properly and revert the change
+> (unless
+> there is a considerable number of other scripts this would break).
+> 
+> [Disclaimer: I know next to nothing about ResourceLoader internals.]
+
+site&user script run after the bottom queue by design. Just like the cascading stylesheets, they are intended and designed to allow overriding/customising things after everything else.
+
+Though presence of code will not make a difference (since bottom queue is async), the loading is affected.
+
+Code in site and/or user scripts that are wrapped in mw.loader.using would trigger additional http requests instead of tagging along on the already pending request for the bottom queue (this is ResourceLoader internals).
+
+I'd recommend we add some code to mediawiki.action.edit to periodically check mwCustomEditButtons. Then immediately deprecate it (not removing it, just marking it as deprecated) and phasing it out over the following weeks (I'd like to add it to the js-deprecations train roll-out in May which will introduce mw.log.deprecate and console.warn messages that users can use to easily see if they are using something that is deprecated).
+
+Then we can safely remove mwCustomEditButtons in the 1.22 release.
+
+(In reply to comment #6)
+> (In reply to comment #5)
+> > Rephrasing bug to be about mwCustomEditButtons to avoid mixed subjects.
+> 
+> See my comment above. There may be other similar structures existing there.
+
+Possible indeed, though unlikely as most legacy things have been phased out. Examples are welcome :)",1367355163,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"billinghurst, this has nothing to do with switching to the new toolbar; mw.toolbar.addButton works with and is intended for the old one, and the change is just a simple find and replace:
+
+  Find:         mwCustomEditButtons[mwCustomEditButtons.length] = { ... }
+  Replace with: mw.toolbar.addButton({ ... })
+
+Just be careful about braces and parentheses.
+
+Here's an example diff: https://nl.wikipedia.org/w/index.php?title=Gebruiker:Romaine/vector.js&diff=37497149&oldid=37497060",1367338720,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"As a comment mwCustomEditButtons functionality is used at English Wikisource. And for numbskulls like myself it is far easier to code snippets to implant code than the alternate means. I repeatedly failed to master mw.toolbar.addButton, gave up walked away, too much to do, too much to customise.
+
+The old toolbar allows for easy nulling out of buttons not required, or not prioritised, and the easy addition of little bits of personal functionality, and the new toolbar makes these things hard (IMO).  Don't blame us that we find the older tool to work better; has the requisite functionality, and meets our simple needs. We are not WP, our requirements are different, our tasks are different, our namespaces are different.
+
+I am happy to try again to be less stupid to see if I can create a core set of tools that could be used, and allow users to plug them in as they see fit, however, it isn't my core skill set. Definitely an area where better guidance would be of use.
+
+PLUS as the 'new' toolbar is still considered a BETA FEATURE (see preferences), why would we be expected to move. Stridency against us simple editors seems a little harsh. Some of us just want to get on with our tasks, and chasing and understanding the backend changes isn't easy.",1367338360,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"So how hard would it be to get the site&user scripts to run first, then $.ready, then the rest of the bottom queue? Then we could kill off mwCustomEditButtons after announcing it properly and revert the change (unless there is a considerable number of other scripts this would break).
+
+[Disclaimer: I know next to nothing about ResourceLoader internals.]",1367337892,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #5)
+> Rephrasing bug to be about mwCustomEditButtons to avoid mixed subjects.
+
+See my comment above. There may be other similar structures existing there.",1367336991,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"Rephrasing bug to be about mwCustomEditButtons to avoid mixed subjects.
+
+So in summary: mwCustomEditButtons is very ugly and undocumented. But it used to be the only way to add buttons to the toolbar. Though (as pointed out by various comments) it is a coincidence that most existing usages have survived without causing errors, but it is the case.
+
+How mwCustomEditButtons works now:
+* Initialise to empty array from top queue
+* Hook in document ready
+* Iterate through array (e.g. items added before the page load) and call mw.toolbar.addButton for each one.
+
+The state is that most existing usages of mwCustomEditButtons happen from a site or user script at run-time in the global scope. And this works fine because they are blocking script tags.
+
+Now that $.ready() (the jquery callback list, not the event itself) is triggered before site/user script load (the site/user script still load from the bottom) it means the code that iterates through the legacy array will not get any of the items because they're not in the array yet at that time.",1367336363,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #0)
+> @Liangent: Can you given an example where it matters for a user script
+> whether
+> the document becomes ready before or after they are loaded? The user scripts
+> are loaded from the bottom of the <body> before </body>. Practically the
+> document is already ready at this point, just $(document).ready() hasn't
+> fired
+> yet. Any user script code that isn't wrapped in $(document).ready() will
+> still
+> execute at exactly the same time. Any user script code that *is* wrapped in
+> $(document).ready() will now execute immediately after loading instead of...
+> immediately after loading. Exactly the same, not?
+
+Let me give a (almost) real world example (difference explained below):
+
+We have some gadgets (technically some gadgets, but socially one gadget; not using [ResourceLoader]). The first is the gadget itself, which registers some global states as data/options, then $(document).ready() its execution code. All gadgets below are modifiers for the gadget which change those global states so when the main body of the gadget is executed, the modified global states are visible to it. But now...
+
+Difference from real world: addOnloadHook() is used there instead of $(document).ready() so it finally escaped :)",1367335235,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"Created attachment 12209
+Test case for the browser issue with setTimeout and document.write
+
+I've attached my test case for the browser issue with setTimeout and document.write. Note that it should be served from a webserver that is not behind a proxy server, so the flush calls result in it slowly counting 0-9.
+
+**Attached**: {F10516}",1367334847,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #0)
+> @Brad Jorsch: It seems that the Firefox bug with document.write being
+> disabled before DOMContentReady is worse than we thought. It is disabled even
+> before the end of the </body> has been reached. We found through
+> trial-and-error that placing it after the main content but before the bottom
+> queue worked.
+
+But it works from synchronously-processed scripts, even just before </body>.
+
+I've done some more testing on this Firefox situation. More specifically, it seems that *any* document.write called from a setTimeout callback will replace the document, even if it fires during <head>. And this even avoids the check (since Gecko 2.0 (Firefox 4.0)) that is supposed to disable document.write when called from async-loaded scripts.[1]
+
+ [1]: https://developer.mozilla.org/en-US/docs/HTML/Element/script#attr-async
+
+The following browsers seem to be affected by this issue: Firefox 20, IE8, IE10, Chrome 24, Chrome 26, Opera 12.14.
+
+The following browsers seem to *not* be affected by this issue: Safari 5.1 (Windows)
+
+So runScript() should probably be forcing async when it calls addScript(), since it is called from a setTimeout in addEmbeddedCss(), as another layer of fix for bug 47457.
+
+
+> As Brad pointed out, $.ready being triggered earlier makes no difference for
+> the bottom queue because they are loaded asynchronously, they always execute
+> without blocking the parser or the DOM ready event.
+
+In fact, this should make the behavior for the bottom queue *more* predictable. Previously, depending on whether the async-loaded scripts for the bottom queue loaded extremely quickly (e.g. from cache) and whether the browser then decided to process them before firing DOMContentLoaded, they might sometimes be fired before $.ready and sometimes after. Now they'll always be after, no matter what the browser does.
+
+> However note that the user scripts (like the site scripts) are *not* loaded
+> through mw.loader because we still support legacy global scope for them. They
+> are loaded by a hardcoded script tag in the DOM. Which means they are
+> blocking and used to block dom-ready
+
+I suppose that's where these complaints about mwCustomEditButtons and other such are coming from, if someone coded something assuming pre-ready directly in a user script or site script. OTOH, scripts loaded from the site or user scripts loaded via mw.loader.load() already had the issue (thanks to the fix for bug 34542 defaulting that sort of thing to async), so it only half-worked at best before bug 47457 anyway.",1367334391,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #0)
+> @Matma.rex: You mean the fact that the deprecated mwCustomEditButtons global
+> (unlike the mw.toolbar interface) is inspected only once by
+> mediawiki.action.edit.js, namely at the domready event. And if it is
+> triggered
+> before the user script, adding to that array will become a no-op.
+
+Yes, precisely.
+
+
+> Though there is a lot of usage of this feature, lets not forget the context:
+
+> * The mwCustomEditButtons interface is for the classic toolbar (aka ""Monobook
+> editor"", though Vector users can also disable WikiEditor to get to it). This
+> is
+> already a large minority of users.
+
+Yeah, my guesstimate is a few hundred power-users across all of the Wikimedia wikis. (I just searched for 'mwCustomEditButtons' in user pages on a few large projects, and tried to account for inactive ones.)
+
+
+> * The mwCustomEditButtons interace has been deprecated in favour of
+> mw.toolbar.addButton, which I created especially for the legacy toolbar users
+> last year to address the many declined bug reports for mwCustomEditButtons
+> which could not be otherwise addressed because mwCustomEditButtons is beyond
+> repair, it is a flawed concept and it keeps breaking for many reasons.
+> 
+> I don't think anything related to mwCustomEditButtons can justify a change of
+> any kind unless it comes at absolutely no overhead and downside.
+
+I realize that this is deprecated, and agree that it's broken by design. But killing it should be preceded by some release notes and some Wikimedia announcements (or just fixing users' JavaScript for them, since there are comparatively few of them).
+
+I have reopened the previous bug because of the combination of Liangent's comment (which I didn't verify myself) and at least two users complaining about this on #wikimedia-tech today, including one who was kind and persistent enough to help me confirm that this was what broke the functionality ([[nl:User:Romaine]]).
+
+So I'm all for removing this legacy compatibility, but let's do it right instead of as a side-effect of an unrelated fix.",1367328242,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+"VisualEditor: For images, ensure that the HTML structure rendered in VE is the same as output by PHP parser so that styles/scripts work as expected and images look normal","Screenshot in edit mode
+
+Images on pages are normally included using the ""thumb"" syntax:
+
+[[File:Foo.jpg|thumb|description]]
+
+In the edit mode no thumb frame is shown, see screenhots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/thumb
+
+**Attached**: {F10382}",1367185320,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-fsl2ocvagc2ct7mjj527,task_description,resolved
+"VisualEditor: For images, ensure that the HTML structure rendered in VE is the same as output by PHP parser so that styles/scripts work as expected and images look normal","This was fixed by gerrit 64367 which is now merged, but is 'experimental' and so will not go out for a short while. Marking as fixed within wmf5, though.",1369093729,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsl2ocvagc2ct7mjj527,task_subcomment,NA
+"VisualEditor: For images, ensure that the HTML structure rendered in VE is the same as output by PHP parser so that styles/scripts work as expected and images look normal","For now we are going to fix it in VE directly. Parsoid will deliver us figure tags for block images and span tags for inline images, but VE is going to render div soup for block and image wrapped in an anchor for inline (maybe with few exceptions).",1368216297,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-fsl2ocvagc2ct7mjj527,task_subcomment,NA
+"VisualEditor: For images, ensure that the HTML structure rendered in VE is the same as output by PHP parser so that styles/scripts work as expected and images look normal","Hijacking this bug slightly. :-)
+
+(This will probably be solved with an upstream bug with Parsoid for a post-parser to transform, but could be done in VE instead. Either way are messy; long term answer is for Parsoid-output to be the ""read"" HTML too, and have skins and scripts target that structure.)",1367544520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsl2ocvagc2ct7mjj527,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Simple test case, see URL:
+
+* foo
+: bar
+
+adds a newline in edit mode. When removing this newline in edit mode the : is killed by the parser.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/Finissage
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60535",1367166420,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-v7tsixpel4mikkpah73h,task_description,resolved
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","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.
+
+This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion.
+
+(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'? I will also copy to bug 55336.",1405114275,PHID-USER-mcyovqjor52nj3se4lq7,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Initial version of this now merged and being deployed tomorrow. I think we'll want to revisit the styling and behaviour, but this will do for now.",1394077374,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 116742 abandoned by Esanders:
+Vector style tweaks for collapsible slugs
+
+https://gerrit.wikimedia.org/r/116742",1394042895,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 109307 merged by jenkins-bot:
+Collapse block slugs and expand on hover/focus
+
+https://gerrit.wikimedia.org/r/109307",1394040062,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 116742 had a related patch set uploaded by Esanders:
+Vector style tweaks for collapsible slugs
+
+https://gerrit.wikimedia.org/r/116742",1393942167,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 109307 had a related patch set uploaded by Esanders:
+Collapse block slugs, and expand on hover/focus
+
+https://gerrit.wikimedia.org/r/109307",1390581550,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. 
+
+Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall.
+
+I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",1381008272,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**jonathan_haas** wrote:
+
+(In reply to comment #15)
+> Why don't we just suppress the delete key when pressing it would delete the
+> object the slug is associated with?
+
+This would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout.
+
+I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.",1380964477,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes. Here is the latter: bug 55336",1380963747,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. 
+
+Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior.
+
+Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result.
+
+That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Today JohnCD asked again about this and I got another report from fr.wp, https://fr.wikipedia.org/w/index.php?title=Osmium&diff=96605232&oldid=93301425 .
+Hoping this gets some love soon :)",1379004776,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",*** Bug 52172 has been marked as a duplicate of this bug. ***,1375047891,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Created attachment 12988
+Copy of http://i.imgur.com/39QQi8U.png
+
+Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-)
+
+**Attached**: {F10355}",1374960319,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Suggestion:
+http://i.imgur.com/39QQi8U.png",1374926957,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**JohnCD67** wrote:
+
+This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",1374396945,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**joedecker** wrote:
+
+I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused.  
+
+As a separate question, can you undo deletion of slugs?  If not, I think that would explain another set of problems others and I have observed.",1374361883,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",Gotcha. A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).,1373913566,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","(In reply to comment #4)
+> Does this include the line of whitespace right at the start of articles?
+
+Yes.",1373913377,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","(In reply to comment #5)
+> It looks like this bug was fixed somehow. I cannot longer reproduce it on
+> dewiki.
+
+Yes, we removed the slugs between lists because we felt they were no longer needed given the new editing tools, but they remain more widely.",1373913366,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",It looks like this bug was fixed somehow. I cannot longer reproduce it on dewiki.,1373909882,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",Does this include the line of whitespace right at the start of articles?,1373879923,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",*** Bug 50295 has been marked as a duplicate of this bug. ***,1373854867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",*** Bug 50797 has been marked as a duplicate of this bug. ***,1373046915,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go.
+
+Re-purposing this bug to talk about that. :-)",1367169998,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+VisualEditor: Coordinate template on dewiki not alienated,"Coordinate template on dewiki not alienated. Shown as active hyperlink to the toolserver.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Breslauer_Platz_%28K%C3%B6ln%29",1367154120,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-lfunc2bgbzuuwhfvjpdv,task_description,declined
+VisualEditor: Coordinate template on dewiki not alienated,It looks like this is handled properly now. Reopen if you still experience this problem.,1374527977,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-lfunc2bgbzuuwhfvjpdv,task_subcomment,NA
+VisualEditor: Coordinate template on dewiki not alienated,"Interesting! The content (which is not labelled as an alien) is floated out from within a div (which is ve-ce-alienInlineNode). Inez/Christian, ideas?",1367173682,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfunc2bgbzuuwhfvjpdv,task_subcomment,NA
+Enable VisualEditor on viwiki,"Per community request; will throw in a change on Monday.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1367123340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vdic7routqydx75tmmbb,task_description,resolved
+Enable VisualEditor on viwiki,This is now deployed. Marking as fixed.,1367270838,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vdic7routqydx75tmmbb,task_subcomment,NA
+Enable VisualEditor on viwiki,Change in gerrit 61382.,1367247999,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vdic7routqydx75tmmbb,task_subcomment,NA
+Enable VisualEditor on viwiki,Request was via e-mail but http://vi.wikipedia.org/wiki/WP:TL#Tr.C3.ACnh_so.E1.BA.A1n_th.E1.BB.8B_gi.C3.A1c is an announcement on the wiki that this is coming for testing.,1367247981,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vdic7routqydx75tmmbb,task_subcomment,NA
+Enable VisualEditor on viwiki,"Any link to the community request, for the records?",1367225301,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vdic7routqydx75tmmbb,task_subcomment,NA
+VisualEditor: Toolbar tooltip text throbs when un-floated,"If you scroll down from the top of the page with the edit notice open and then scroll back up, the text content of the notice 'throbs' a little. I think it has to do with the dynamic addition / removal of the 've-ui-toolbar-wrapper-floating' class on ve-ui-toolbar-wrapper.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1367030520,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-dv6pxr32mobwf3arakop,task_description,declined
+VisualEditor: Toolbar tooltip text throbs when un-floated,Hi Ori. Can you please respond to James' comment?,1397939050,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dv6pxr32mobwf3arakop,task_subcomment,NA
+VisualEditor: Toolbar tooltip text throbs when un-floated,"Ori, I can't reproduce this locally (on Chrome, Safari or Firefox) - what browser were you using?",1367126151,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dv6pxr32mobwf3arakop,task_subcomment,NA
+VisualEditor: A lot of time needed to load <math> blocks?,"I tested it on the [[Bayes' theorem]] which has <Math></Math> inside the article with chrome 28 and it couldn't load the page!.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367021760,PHID-USER-dswbdv7ibhsefllcqarz,PHID-TASK-pzrh6lxoqsxowrm5mt6k,task_description,declined
+VisualEditor: A lot of time needed to load <math> blocks?,Resolving as WORKSFORME as I cannot reproduce and there's been no further information about how to get this effect. Feel free to re-open if you have additional data to help us find out what went wrong for you.,1367548087,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pzrh6lxoqsxowrm5mt6k,task_subcomment,NA
+VisualEditor: A lot of time needed to load <math> blocks?,I'm afraid I can't reproduce this - is this using MathJax? When I load the page https://en.wikipedia.org/wiki/Bayes'_theorem?veaction=edit (in Chrome or Firefox) I always get the <math> blocks rendered as PNGs instantly. Can you give some more information? A screenshot of the failed (partial?) rendering would be particularly useful.,1367293923,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pzrh6lxoqsxowrm5mt6k,task_subcomment,NA
+VisualEditor: No warning is shown when saving a page without an edit summary despite user preference,"No warning is shown when saving a page without an edit summary even when the ""Prompt me when entering a blank edit summary"" preference is enabled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367008860,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-bltbr6dun3s6724ee3wt,task_description,resolved
+VisualEditor: No warning is shown when saving a page without an edit summary despite user preference,Merged and will go out with wmf5.,1369092004,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bltbr6dun3s6724ee3wt,task_subcomment,NA
+VisualEditor: No warning is shown when saving a page without an edit summary despite user preference,Related URL: https://gerrit.wikimedia.org/r/64313 (Gerrit Change Idba707abaea8b08a94f7fa4d5bc5b1e35261a572),1368800999,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bltbr6dun3s6724ee3wt,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),"When I edit an article in the English Wikipedia and hover over a template or an image, green diagonal stripes appear over it, meaning that it can't be edited.
+
+These green stripes don't appear in the Hebrew Wikipedia.
+
+See the URL for a demo.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://he.wikipedia.org/wiki/ASCII",1367005440,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_description,resolved
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),"**orbit** wrote:
+
+Yep, CSSJanus indeed. I've added /*@noflip*/ to the phantoms container to ensure proper positioning.",1367280330,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),https://gerrit.wikimedia.org/r/61516 (Gerrit Change Id7662362d117d6c5719b9b98d7a0dbf62e9ba3ff) | change APPROVED and MERGED [by jenkins-bot],1367280189,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),Related URL: https://gerrit.wikimedia.org/r/61516 (Gerrit Change Id7662362d117d6c5719b9b98d7a0dbf62e9ba3ff),1367280048,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),"Indeed, works in debug mode.
+
+It's just a wild guess for now, but it may have something to do with CSSJanus.",1367006685,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),It might be a cache issue - works just fine in debug mode - https://he.wikipedia.org/w/index.php?title=ASCII&debug=true,1367006326,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),I'm able to reproduce at least in Chrome.,1367005802,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Moving the cursor using an arrow makes templates and footnote numbers disappear,"Steps:
+
+1. Go to the URL.
+2. Start editing the page using the VisualEditor.
+3. Move the cursor using the keyboard arrow keys forward (right).
+
+Observed:
+
+When you get to the ""Done"" template and go on moving the cursor, the whole template disappears.
+
+The same happens when you get to the reference number on the second line (""[1]"").
+
+The cursor must probably skip over them and definitely not make them disappear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/VisualEditor:Disappearing_template",1367005140,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-gfh3zyqmntwzuisuy7o2,task_description,resolved
+VisualEditor: Moving the cursor using an arrow makes templates and footnote numbers disappear,And actually the desired behavior is not skipping over - it is selecting it (so you can delete if you want) - give it a try in Chrome.,1367005498,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-gfh3zyqmntwzuisuy7o2,task_subcomment,NA
+VisualEditor: Moving the cursor using an arrow makes templates and footnote numbers disappear,I have a good reason to believe that this occurs only in Firefox and I just fixed it here: https://gerrit.wikimedia.org/r/#/c/61055/. If you get it in other browser then pelase reopen this bug.,1367005458,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-gfh3zyqmntwzuisuy7o2,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"Having users using different languages to post feedback on different pages on the same site makes it difficult to manage.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1366981200,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-xdguppbr4wppxkti274y,task_description,resolved
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"Change 74064 merged by jenkins-bot:
+Remove 'visualeditor-feedback-link' from RL module
+
+https://gerrit.wikimedia.org/r/74064",1374012412,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,Fixed. Sorry about this. Will be deployed this afternoon.,1374012385,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"Change 74064 had a related patch set uploaded by Krinkle:
+Remove 'visualeditor-feedback-link' from RL module
+
+https://gerrit.wikimedia.org/r/74064",1374010123,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"(In reply to comment #11)
+> (In reply to comment #10)
+> > pl.wiki is on 1.22wmf8 but my feedback was posted to a non-existing page with
+> > Italian title (I have Italian UI), [[pl:Wikipedia:VisualEditor/Commenti]]:
+> > https://pl.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> > Commenti&oldid=36959657
+> 
+> Confirmed, this is also happening to me. Did the code get broken somehow?
+
+Somewhere between https://gerrit.wikimedia.org/r/#/c/68216/ and its parent (I can't seem to find the commit that added it) the message was added in VisualEditor.php's resource module definition. Which caused the message from VisualEditorMessagesModule (in content-language) to be overridden at run time by the one from ResourceLoader for user language.",1374010028,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"(In reply to comment #10)
+> pl.wiki is on 1.22wmf8 but my feedback was posted to a non-existing page with
+> Italian title (I have Italian UI), [[pl:Wikipedia:VisualEditor/Commenti]]:
+> https://pl.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Commenti&oldid=36959657
+
+Confirmed, this is also happening to me. Did the code get broken somehow?",1373852430,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"pl.wiki is on 1.22wmf8 but my feedback was posted to a non-existing page with Italian title (I have Italian UI), [[pl:Wikipedia:VisualEditor/Commenti]]: https://pl.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Commenti&oldid=36959657",1372603756,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,Merged and will go out in wmf5.,1369088720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,*** Bug 48645 has been marked as a duplicate of this bug. ***,1369068249,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,Related URL: https://gerrit.wikimedia.org/r/64498 (Gerrit Change I3804e6f91015ef9b8ae5196efb37475d714cd7d5),1368898661,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"(In reply to comment #5)
+> Yes, that would fix this particular problem; my question is more as to
+> whether
+> the core tool should default for target link to be in the content language.
+
+Based on what I see in the usage given above, you're giving a Title to core feedback tool, which points to a certain page, instead of a message name to core with feedback page name in that message.",1368814496,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"Yes, that would fix this particular problem; my question is more as to whether the core tool should default for target link to be in the content language.",1368813996,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"But there is:
+
+modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js:
+		'title': new mw.Title( ve.msg( 'visualeditor-feedback-link' ) ),
+
+shouldn't something like:
+
+new mw.Title( ve.msg( 'visualeditor-feedback-link' ).inContentLanguage() )
+
+be used?",1368813782,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"(In reply to comment #2)
+> I'm not sure what ""core MW feedback tool"" means, but I was talking about the
+> feedback feature for [[Wikipedia:VisualEditor/Feedback]].
+
+Yes, this is a core MediaWiki feature, it just happens to be used by VisualEditor:
+
+  resources/mediawiki/mediawiki.feedback.js",1368813471,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"I'm not sure what ""core MW feedback tool"" means, but I was talking about the feedback feature for [[Wikipedia:VisualEditor/Feedback]].",1368813368,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,(Is this a bug in the core MW feedback tool?),1368809941,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+[mediawiki.feedback.js] Feedback should follow redirect,"I tried to edit MediaWiki:Visualeditor-feedback-link on zhwp but it doesn't affect the feedback target page at all. Is that even the correct message to change?
+
+I then turn the target page into a redirect, but feedback are still sent to that page without following the redirect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366979940,PHID-USER-hoj4lurwi6bejyjy5qlp,PHID-TASK-xjswbfq6vvdy4oyl6qub,task_description,resolved
+[mediawiki.feedback.js] Feedback should follow redirect,Fixed in 96c4e453ecfaba9cc5dca904301981e9d6e3492b (https://gerrit.wikimedia.org/r/#/c/143171/).,1419984894,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xjswbfq6vvdy4oyl6qub,task_subcomment,NA
+[mediawiki.feedback.js] Feedback should follow redirect,"(In reply to comment #0)
+> I tried to edit MediaWiki:Visualeditor-feedback-link on zhwp but it doesn't
+> affect the feedback target page at all. Is that even the correct message to
+> change?
+
+Yes, that is the correct message; you can set it for all zh-hans or zh-hant projects at [0] and [1] and it will respect it (once the software is updated).
+
+[0] - https://translatewiki.net/w/i.php?title=Special:Translate&language=zh-hans&group=ext-visualeditor
+[1] - https://translatewiki.net/w/i.php?title=Special:Translate&language=zh-hant&group=ext-visualeditor
+
+> I then turn the target page into a redirect, but feedback are still sent to
+> that page without following the redirect.
+
+You're right; this is a bug in the feedback tool, which is part of MediaWiki core. Moving the bug there.",1366986213,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xjswbfq6vvdy4oyl6qub,task_subcomment,NA
+VisualEditor: using non-ASCII characters in the VisualEditor edit summary insertion can make the remaining character count negative,"Try typing non-ASCII characters in the VisualEditor edit summary field. For example, just type the Russian letter ж continuously. Towards the end it won't stop at 0, but at -1. Example screenshot from the Hebrew Wikipedia: http://j.mp/ZoQKX6 .
+
+This should be handled in a cleaner way. Either disallow typing anything that would go beyond zero, or allow all text to go beyond zero, as in Twitter or MoodBar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1366970520,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-pruvovx7b4nd6obededc,task_description,resolved
+VisualEditor: using non-ASCII characters in the VisualEditor edit summary insertion can make the remaining character count negative,Merged; will go out with wmf5.,1368885077,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pruvovx7b4nd6obededc,task_subcomment,NA
+VisualEditor: using non-ASCII characters in the VisualEditor edit summary insertion can make the remaining character count negative,"Fixed in https://gerrit.wikimedia.org/r/#/c/64342/
+
+To clarify, we aren't letting people go over the limit, we just aren't updating the counter after keyup. (If you get to -1 then press an arrow key, you'll see you're actually under the limit).",1368812163,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pruvovx7b4nd6obededc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,"Steps:
+
+1. Write some text in VisualEditor in the Hebrew Wikipedia.
+
+2. Select a word.
+
+3. Press the link button in the toolbar. A small link insertion panel appears.
+
+Observed: The direction of the <input> element for the link is ltr.
+
+Expected: The direction of the <input> element for the link is supposed to be rtl.
+
+Comment: It does make sense to set ltr direction by default for external links (http://www.example.com). For internal links the default direction should be the same as that of that Wikipedia's content language.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366970040,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-bwileoq2fxrn6ez262yc,task_description,resolved
+VisualEditor: Link inspector input text always has LTR direction,Merged in Moriel's fix (thanks!).,1367529320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,Related URL: https://gerrit.wikimedia.org/r/61960 (Gerrit Change Ic13b9c3b155ce2979298cac9518c7419b9d45bac),1367480866,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,Moriel wants to take a stab at this one; assigning.,1367377382,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,"(In reply to comment #1)
+> Eurgh. That's a real mess of a user interaction - in an RTL locale, it starts
+> as RTL, but then you type enough of a string that looks a bit like
+> ""http?://www"" it magically switches to LTR?
+
+This is not such a mess as a matter of fact. This works very well in GMail chat, for example. If you start typing Hebrew characters, it switches the input box to RTL and vice versa. It also goes further: if you type a few Hebrew characters, and then a lot of Latin characters, it switches to LTR.
+
+BUT -and this is very important- it is not forced: the user can switch the direction later manually. In most Windows browsers it's done using Ctrl-Shift, in Firefox on Windows and GNU/Linux it's done using Ctrl-Shift-X. I don't know about Mac browsers, but it's probably something similar. (I do know that it's impossible on Chrome in Linux, which is why I almost never use it.)
+
+> What about when your wiki page that
+> you're internally linking to is [[http://www.amazon.com]] - do you show as
+> LTR
+> even though it's actually an internal link? How does this get handled in
+> other
+> software?
+
+Same as above, essentially. One thing that could help here would be a possibility to specify the language of the page and of the title, as in bug 34514. But that's extra icing. For a link insertion dialog it is enough to do automatic detection with a possibility to override manually.",1367300169,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,"(In reply to comment #0)
+> Comment: It does make sense to set ltr direction by default for external
+> links (http://www.example.com). For internal links the default direction should
+> be the same as that of that Wikipedia's content language.
+
+Eurgh. That's a real mess of a user interaction - in an RTL locale, it starts as RTL, but then you type enough of a string that looks a bit like ""http?://www"" it magically switches to LTR? What about when your wiki page that you're internally linking to is [[http://www.amazon.com]] - do you show as LTR even though it's actually an internal link? How does this get handled in other software?",1367286968,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+"VisualEditor: VE tab is on the left (not right) of the ""edit source"" tab in RTL languages","
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1366932480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k5ivcykbmehlps6rrqj3,task_description,resolved
+"VisualEditor: VE tab is on the left (not right) of the ""edit source"" tab in RTL languages","
+
+*** This bug has been marked as a duplicate of bug 48017 ***",1368639099,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k5ivcykbmehlps6rrqj3,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,"If users can't edit in nowiki blocks, they will make accidental wikitext-like items and be forever unable to edit them in future.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366930860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_description,resolved
+VisualEditor: Support editing nowiki blocks,*** Bug 51950 has been marked as a duplicate of this bug. ***,1374879593,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,Done and merged.,1374262258,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,"Change 74107 merged by jenkins-bot:
+Add a node class for mw:Nowiki
+
+https://gerrit.wikimedia.org/r/74107",1374261100,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,"Change 74107 had a related patch set uploaded by Catrope:
+Add a node class for mw:Nowiki
+
+https://gerrit.wikimedia.org/r/74107",1374027032,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,"Theoretically users should never know something's been <nowiki>'ed - possibly we could just silently drop them and Parsoid re-applies them automatically on save?
+
+(This assumes we can rely on Parsoid to do this with no or very few false negatives - false positives, which we already have a little of, wouldn't be a huge problems for VE users.)",1366931455,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,*** Bug 47677 has been marked as a duplicate of this bug. ***,1366930915,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"The 'cancel' message is used confusingly.
+
+I only noticed it recently. I know of two places where it is used, though there may be more:
+
+1. As a link near the ""Show changes"" button when editing a page.
+
+2. As a button near the ""Review and save"" button in the VisualEditor.
+
+In both cases it's better to say something like ""Exit without saving"". The ""Cancel"" button is usually used in dialog boxes and not in editors' user interfaces.
+
+The message may be used in other places and in extensions, so it's probably better not to change it. For these actions a new message should be created, or maybe even two messages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1366929720,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-h6knxqbqokuwzylojsm7,task_description,declined
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',Indeed. :-),1406470421,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"Hehe, it was removed eventually :)",1406457643,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"Deciding to WONTFIX this, per discussion above. Hopefully it will be more understandable anyway, given the forthcoming changes to the save dialog.",1368804205,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"I read your concern, Amir, and my opinion is similar to that of James. In computer interaction, clicking a button that says Cancel will end the current action (in this case editing a page) without actually committing the changes that the actor made. I see no deviation from that paradigm in the two use cases you describe.
+
+I think we shoild close this issue without implementing the suggestion made.",1366959308,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"Worry that this is a bit long for users, and ""cancel"" is used in the dialog sense (they entered an editor, this cancels that edit) but I can see your point.
+
+(BTW, your two descriptions are for the same button, unless I'm missing something?)",1366934934,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Take a look at the URL.
+
+When you see the output page, the list has three items. If you edit it in the source editor, you'll see that there's an extra empty item in the end of the list. If you edit it in the VisualEditor, you'll see it rendered.
+
+The VisualEditor behavior actually makes more sense to me. Gabriel Wicke suggested on IRC to open this issue at the PHP parser.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/VisualEditor:Empty_list_item",1366928220,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-cv5eyk43xupkutrvi7fo,task_description,resolved
+Empty list items goes missing in the PHP parser when tidy is enabled,"The goal of fixing templates to not emit empty list items in the first place ( T49673#1827449 ) is not in sight. For now, the core part of this ticket has been addressed. Empty elements no longer go missing with Tidy which means we can replace Tidy without worry about breaking rendering because of this.
+
+Longer term, we should migrate to a CSS3 fix of li:empty { display:none; } and remove the mw-empty-elt class.",1494287494,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"It would be easier to fix such templates if we finally got around to allowing blank lines between list items without breaking the list. This has been requested very often, although unfortunately the narrower, more sensible proposals on the subject (e.g. T11342, T35918, T15223) have been closed as duplicates in favour of the more aggressive proposal T3115.",1448405507,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"It would be easier to fix such templates if we finally got around to allowing blank lines between list items without breaking the list. This has been requested very often, although unfortunately the narrower, more sensible proposals on the subject (e.g. T11342, T35918) have been closed as duplicates in favour of the more aggressive proposal T3115.",1448346652,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,">>! In T49673#1776557, @Jonesey95 wrote:
+> I don't have the gerrit skills to parse the code to understand whether this change will allow a page to emit a tracking category specific to monitor articles and templates that need to be updated. If it will, some instruction would be helpful. If it currently will not, please make whatever code modification is necessary to allow a page to emit such a tracking category. Thank you. 
+
+There's no tracking category at the moment. I wanted to assess it myself, to determine the size of the problem, before creating task lists for others to work through.
+
+[[https://www.mediawiki.org/wiki/User:Tim_Starling/Empty-li-log|Here is a log sample]] from parsoid listing some supposedly empty <li> elements. I have analysed some of them.
+
+[[https://en.wikipedia.org/w/index.php?title=Template:Europe_topic&oldid=675002623&action=edit |Here is a notable example]] of a template which depends on empty li removal. This navbox template allows the removal of countries from Europe depending on parameters. For example if you consider Germany to not be part of Europe, you can use {{Europe topic|DE=}} to make a navbox which omits the relevant list item. Note that you can't just take the asterisk inside the #if, because that would create paragraph breaks between adjacent list items. It could be done by taking the line break inside the #if, or by removing all the line breaks and using HTML-style <li> input.
+
+",1448343599,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Change 253514 merged by jenkins-bot:
+Add 'mobile' target to 'mediawiki.raggett' module
+
+[[https://gerrit.wikimedia.org/r/253514]]",1447723607,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Change 253514 had a related patch set uploaded (by Legoktm):
+Add 'mobile' target to 'mediawiki.raggett' module
+
+[[https://gerrit.wikimedia.org/r/253514]]
+",1447721409,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"The CSS trick for do not display element with //mw-empty-li// class works only for Desktop, not in mobile version.
+
+It's possible in this transitory period hide the empty list elements also in mobile site? Thanks
+
+See [[https://it.wikipedia.org/w/index.php?title=Discussioni_progetto:Coordinamento/Template&oldid=76516793#Errore di visualizzazione da mobile | discussion ]] (in italian) and [[https://it.m.wikipedia.org/wiki/Kriszti%C3%A1n_Adorj%C3%A1n|example]].",1447669730,PHID-USER-6ji4nw2pi3dgjy7tgmhp,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"This tasks seems to be related to a lot of odd looking [[Template:Authority control]] templates that use //hlists// which suddenly started showing rows of dots between entries
+
+# Commons issues and the fix was discussed at https://www.mediawiki.org/wiki/Talk:Snippets/Horizontal_lists
+# Czech Wiki opted for rewriting the template https://cs.wikipedia.org/wiki/%C5%A0ablona:Autoritn%C3%AD_data?diff=13027629&oldid=12931367
+# Other wikis were spared because they already rewrote the template in Lua
+",1447161101,PHID-USER-j4jntnatcouoxfrk74sh,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"I don't have the gerrit skills to parse the code to understand whether this change will allow a page to emit a tracking category specific to monitor articles and templates that need to be updated. If it will, some instruction would be helpful. If it currently will not, please make whatever code modification is necessary to allow a page to emit such a tracking category. Thank you. ",1446519651,PHID-USER-7cpk77uy2iq7bxf6hac6,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Change 246148 merged by jenkins-bot:
+Client-side migration for empty li preservation
+
+[[https://gerrit.wikimedia.org/r/246148]]",1446075996,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Change 246148 had a related patch set uploaded (by Tim Starling):
+Client-side migration for empty li preservaton
+
+[[https://gerrit.wikimedia.org/r/246148]]
+",1444793336,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"I'm going to introduce a migration tool to fix this bug, roughly following @cscott's suggestion, which is to preserve empty <li> tags through Tidy, but to add a class to those preserved elements which will be styled with display:none. It is believed that there are some templates which are producing empty list items because it is convenient for them as a way of omitting the list item for empty input. After the display:none hack is introduced, a user script would allow the expected changes to be visible to template maintainers. There is also a proposed change to log affected templates: https://gerrit.wikimedia.org/r/#/c/246106
+
+After a suitable migration period, the display:none rule would be removed, and list items would be visible as is desired by the multiple reporters of this bug.
+
+The empty <li> tags would be preserved through tidy by adding a datafld attribute, exploiting special case behaviour in Tidy's CanPrune() which was intended to fix http://sourceforge.net/p/tidy/bugs/337/
+",1444792377,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,*** Bug 52374 has been marked as a duplicate of this bug. ***,1386112687,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+VisualEditor: Sequential floated images are stacking,"**Author:** `owen`
+
+**Description:**
+Looking at [[Principality of Stavelot-Malmedy]] in the Visual Editor, immediately after the heading ""Development and the High Middle Ages"" there are two images floated right.
+
+In Read mode, these images are given `float: right; clear: right;`. In VE mode, however, the `clear: right;` appears to be missing, so the images are stacking up.
+
+In case it makes a difference, I'm running Chrome 26.0.1410.64 m, on 64-bit Windows 7 Home Premium (Build 7601, Service Pack 1).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.org/wiki/Principality_of_Stavelot-Malmedy",1366925940,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eaknwofmb4d2xflpnx7d,task_description,resolved
+VisualEditor: Sequential floated images are stacking,"This was fixed by gerrit 64367 which is now merged, but is 'experimental' and
+so will not go out for a short while. Marking as fixed within wmf5, though.",1369093844,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eaknwofmb4d2xflpnx7d,task_subcomment,NA
+VisualEditor: Sequential floated images are stacking,"This is because Parsoid outputs completely different HTML for images (using <figure> and what not) that doesn't match the MediaWiki CSS.
+
+This will be fixed once we change the ce.MWThumbImageNode rendering to match the MW rendering rather than the Parsoid rendering, and move image support out of the experimental list.",1366927394,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-eaknwofmb4d2xflpnx7d,task_subcomment,NA
+VisualEditor: Sequential floated images are stacking,"Confirmed - the DM layer for alien items (like images) apparently respects the CSS and is meant to pass it through, but CE isn't?",1366926217,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eaknwofmb4d2xflpnx7d,task_subcomment,NA
+[TUX] Page view doesn't fit long page titles,"A long title all mixed
+
+Long titles get compressed until they become unreadable, see URL and screenshot.
+
+--------------------------
+**Version**: master
+**Severity**: minor
+**URL**: https://meta.wikimedia.org/w/index.php?title=Special:Translate&language=de&group=page-Wikimedia+Blog%2FDrafts%2FTry+out+the+alpha+version+of+the+VisualEditor%2C+now+in+15+languages&filter=&action=page
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45924
+
+**Attached**: {F10857}",1366899360,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-7rd7dea5gzp4xsh4amok,task_description,declined
+[TUX] Page view doesn't fit long page titles,"So, on Vector this looks okay. On Monobook it looks like in the Vector screenshot above. Vector overrides the line-height for h1, Monobook doesn't. So the rule from Translate applies:
+``` 
+.tux-messagelist .tux-message-pagemode .tux-pagemode-translation {
+	color: #222;
+	font-size: 16px;
+	line-height: 1.5em;
+	padding-left: 20px;
+}
+```
+
+Since it is still readable and Monobook is not my favorite skin, I'm inclined to decline this as not worth fixing in Translate. It would be nice of Monobook also set the line-height when overriding font-size for headings.",1607413610,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-7rd7dea5gzp4xsh4amok,task_subcomment,NA
+[TUX] Page view doesn't fit long page titles,"Created attachment 12173
+Same long title just partly overlapping in another browser
+
+**Attached**: {F10858}",1366899451,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-7rd7dea5gzp4xsh4amok,task_subcomment,NA
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)","1. Parsoid not running, VisualEditor enabled on to-be-created page X
+2. Enter a few words 
+3. ""Review and Save""
+4. Loader keeps spinning indefinitely
+
+Request:
+
+action=visualeditor&paction=serialize&html=%3Cp+data-ve-changed%3D%22%7B%26quot%3Bcontent%26quot%3B%3A7%7D%22%3Edfgdg%3C%2Fp%3E&page=Sandbox%2F1&oldid=0&token=%2B%5C&format=json
+
+Response:
+
+{""visualeditor"":{""result"":""success"",""content"":false}}
+
+No errors.
+
+Note this bug could also be reported as ""Loader keeps spinning forever when creating a new page and trying to review/save it""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366757460,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jrrnahwoyus5omqe5ox7,task_description,resolved
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)",Merged into master; will go out with wmf5.,1368638813,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jrrnahwoyus5omqe5ox7,task_subcomment,NA
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)",Related URL: https://gerrit.wikimedia.org/r/63861 (Gerrit Change I6bdd177bc9b5a0af9107cf08d8e46470c6778e12),1368631835,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jrrnahwoyus5omqe5ox7,task_subcomment,NA
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)","(In reply to comment #1)
+> Related URL: https://gerrit.wikimedia.org/r/60613 (Gerrit Change
+> Icdf64a792c13a326f494e051be47f2946928d142)
+
+This fixed the visible problem described below:
+
+(In reply to comment #0)
+> as ""Loader keeps spinning forever when creating a new page and
+> trying to review/save it""
+
+The error is now handled by stopping the spinner (as we always do after an aborted load) and display the error.
+
+The error message in my case was ""No Wikitext content in response from server"" triggered from ve.init.mw.Target.onSerialize's patch where there are no errors and eventually finds this by type-checking the content property.
+
+Lowering priority. Todo tasks:
+
+* Don't return status ""success"" if content is missing, but use status ""error"".
+
+* Make it not just status ""error"" but actually trigger a proper API response.error property with a more direct error, namely that the Parsoid server is unavailable.",1366762868,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jrrnahwoyus5omqe5ox7,task_subcomment,NA
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)",Related URL: https://gerrit.wikimedia.org/r/60613 (Gerrit Change Icdf64a792c13a326f494e051be47f2946928d142),1366761720,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jrrnahwoyus5omqe5ox7,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit musical scores,"As a VisualEditor plugin inside the extension, provide a visual way for users to create and edit musical scores.
+
+This would be a (very) major undertaking, even if there is an existing JavaScript-based visual Lilypond score editor, or failing that, a visual score editor with a different output format which would need to be converted to Lilypond. A brief search found a few promising leads for ABC editors, but mostly based in Flash.
+
+Still, hopefully not just a pipedream. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366688580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_description,open
+Create a VisualEditor plugin tool to add/edit musical scores,"Note that as of November 2015 there is a nice previewing editor for Scores, but it's still based on the Lilypond or ABC source format rather than a visual one.",1459667871,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit musical scores,">>! In T49528#1003822, @Tgr wrote:
+> Just adding a text editor with a preview button, like e.g. [[ http://lilybin.com/ | lilybin.com ]] does it, does not sound that hard.
+
+Indeed, but this task is asking for a visual drag-and-drop sheet music editor.
+
+> I wonder if that could even be a generic fallback option for tag-based parser extensions without a dedicated editor plugin.
+
+That's already provided in VisualEditor.",1422635139,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit musical scores,"Just adding a text editor with a preview button, like e.g. [[ http://lilybin.com/ | lilybin.com ]] does it, does not sound that hard. I wonder if that could even be a generic fallback option for tag-based parser extensions without a dedicated editor plugin.",1422602902,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit musical scores,"See also
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-June/069973.html",1371406501,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"On VE load, do an ""originalHtml == serialise(linmod(originalHtml)"" or whatever and fail out of the VE if false; ideally, also allow the user to submit a failure report for debugging purposes (this will need to get checked through with legal).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366667700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inty44ufbm7rwhc55mom,task_description,resolved
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,Written and about to be deployed.,1372387346,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"Change 70106 merged by jenkins-bot:
+mw.ViewPageTarget: Add sanity check for DOM roundtrip
+
+https://gerrit.wikimedia.org/r/70106",1372387306,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"Change 70106 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Add sanity check for DOM roundtrip
+
+https://gerrit.wikimedia.org/r/70106",1372381883,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"Any news on this? 
+
+Having some automated general sanity checks on the returned wikitext (for example size, check if it starts with a doctype) would also be good, especially now that users don't see a diff by default any more. If any of the automated sanity checks fail, you should probably ask the user to review changes before saving. This should catch most major article corruption issues before they happen.",1371496468,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,Pulling.,1370449877,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,Roan's offered to do this one on his flight. Marking as such.,1368766983,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"We are diffing on the DOM on the way in, but while debugging a text diff is useful too.
+
+Order preservation is not guaranteed in the DOM4 spec afaik, but is implemented and supported nevertheless using the attributes collection and numerical indexing: https://developer.mozilla.org/en-US/docs/DOM/Node.attributes",1367265092,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"We wouldn't be doing string-based comparisons, we'd be doing DOM-based comparisons. That's what Parsoid should be doing too, IMO.
+
+If comparisons are DOM-based, quoting style and attribute order don't matter. In general, I don't believe there's a way to read or write attribute order in the DOM.",1367264016,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"A common issue currently is changes in attribute order and a change of quoting style for JSON attributes. It would be great if VE could preserve the order of attributes. 
+
+For the quoting, we have some smart quoting code that you could reuse. Alternatively, you can compare the innerHTML of the original DOM with the exported DOM as that implicitly changes JSON attribute quoting to the verbose style.",1367256333,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","The ""language conversion blocks"" are a wikitext feature that allow users to define text content in parallel scripts. The most high profile is in Chinese, which has two major writing systems and automated conversion between them, but there are 28 others, some of which are not automated conversion (so VE will need to not just mark the text with an appropriate <span>, but allow the user to understand when they have edited text that needs editing twice or thrice (possibly in scripts they cannot/do not want to use?) - see https://meta.wikimedia.org/wiki/Wikipedias_in_multiple_writing_systems
+
+Documentation of the feature (focussed on the syntax) is here: https://www.mediawiki.org/wiki/Writing_systems/Syntax
+
+Parsoid will need to add support for this first, which is {T43716}.",1366380120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_description,resolved
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis",">>! In T49411#3691289, @Deskana wrote:
+> I believe there's still more outstanding here, right?
+
+Yes, see  {T43716} - phase 1 support is complete, which brings VE to parity with the PHP parser -- in both cases, as soon as you start to edit the page you're confronted with the raw un-converted text (not the text in your preferred variant).
+
+VE can do better (in theory) -- that's ""phase 3"" of T43716.  But that's probably another bug.  Since VE is now at parity with PHP source editing, I think this task can be resolved, and we'll open specific bugs for deficiencies in the current UX (ie, T182910).  I'll open a new task for the VE side of Parsoid's phase 3, once we get there, but that's a new feature.",1513281041,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","I believe there's still more outstanding here, right?",1508260389,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 361921 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Inspectors for editing LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/361921]]
+",1505493098,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 358396 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Context item for LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/358396]]
+",1502461750,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 356739 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Display LanguageConverter markup in VisualEditor
+
+[[https://gerrit.wikimedia.org/r/356739]]
+",1500998488,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis",See https://www.mediawiki.org/wiki/Parsoid/Language_conversion#Testing_LanguageConverter_with_Parsoid_and_VisualEditor for setup & test hints.,1498753539,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 361921 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):
+[mediawiki/extensions/VisualEditor@master] WIP: Dialog for editing LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/361921]]
+",1498674768,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 358396 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):
+[mediawiki/extensions/VisualEditor@master] Node inspector for LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/358396]]
+",1497285783,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","@deskana sure:  Theres's fully-functioning Parsoid support in https://gerrit.wikimedia.org/r/140235 (T43716 phase 1).  VE currently ""alienates"" these blocks, which means they are invisible and uneditable but round-trip fine if you don't touch them.
+
+I'm currently working on some basic support for displaying/editing the language converter rules in VE (which is what this task is about).  Very rough start of a patch above; there are some representation issues to work out.  VE is a little weak on directly editing generated content.  I'll copy some discussion with @Catrope here:
+
+(05:17:05 PM) cscott-free: Roan: is there any precedent in VE for an inline BranchNode ?
+(05:17:30 PM) cscott-free: that is, a Node that behaved like an annotation: you could edit inside it, and it was laid out inline.
+(05:17:43 PM) RoanKattouw: No I don't think so
+(05:18:01 PM) RoanKattouw: There are inline nodes like images
+(05:18:14 PM) cscott-free: yes, but they are ve.ce.LeafNodes, not allowed to have any contents
+(05:18:22 PM) RoanKattouw: But no inline nodes that have children
+(05:18:33 PM) cscott-free: even BlockImage is a LeafNode, and you have to click into the inspector to edit the caption
+(05:18:38 PM) RoanKattouw: Yeah
+(05:18:52 PM) RoanKattouw: So, I would like us to have inline editing of image captions
+(05:19:01 PM) RoanKattouw: But it wouldn't be done that way
+(05:19:09 PM) RoanKattouw: What is the application you have in mind?
+(05:19:34 PM) cscott-free: I tried to use toDataElement to convince the dm that my `<span>` was actually an annotation, but that didn't work quite right with generated content.
+(05:20:24 PM) cscott-free: `-{R|foo}-` is a silly sort of `<nowiki>`, right?  But it's represented by Parsoid as `<span typeof=""mw:LanguageVariant"" data-mw-variant='{....text:""foo""}'></span>`
+(05:20:43 PM) RoanKattouw: What does that syntax mean again?
+(05:21:01 PM) cscott-free: It just means ""protect `foo` from language conversion""
+(05:21:09 PM) RoanKattouw: Aha OK
+(05:21:20 PM) cscott-free: but there are other similar forms
+(05:21:22 PM) RoanKattouw: Does it also output Foo?
+(05:21:25 PM) cscott-free: yes
+(05:21:37 PM) RoanKattouw: Then shouldn't the span be not empty?
+(05:21:49 PM) cscott-free: well... maybe.
+(05:22:16 PM) RoanKattouw: I mean, at least for display purposes you would want that, right?
+(05:22:22 PM) cscott-free: see https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec/Language_conversion_blocks#Alternative_2
+(05:22:45 PM) RoanKattouw: Also, am I allowed to have annotations inside?
+(05:22:56 PM) RoanKattouw: Can part of foo be bold, or a link?
+(05:23:01 PM) cscott-free: yes, you can have annotations inside
+(05:22:56 PM) cscott-free: the idea is that eventually we'll do the actual language conversion client-side, and so we'd fill the empty spans with the correct thing based on the currently-selected variant
+(05:23:12 PM) RoanKattouw: Oh, I see
+(05:23:30 PM) RoanKattouw: So it behaves kind of like a reference then
+(05:23:42 PM) RoanKattouw: Or a mix between that and an auto numbered link
+(05:23:43 PM) cscott-free: in other cases, there might be more than one possible output in there, and I only want to see one of them (at a time)
+(05:23:49 PM) RoanKattouw: Right
+(05:24:10 PM) RoanKattouw: So the content isn't text then, it's HTML
+(05:24:14 PM) cscott-free: yeah
+(05:24:38 PM) cscott-free: and it's got the usual ""could be block, could be inline"" thing that MWTransclusionNode deals with
+(05:24:55 PM) RoanKattouw: That's a tricky one, I'd recommend picking edsanders and David's brains too
+(05:25:12 PM) RoanKattouw: The fact that it can be block is very annoying
+(05:25:23 PM) RoanKattouw: That makes it hard to make it an annotation
+(05:26:01 PM) cscott-free: RoanKattouw: yes, and it's something I'd eventually like to fix on the PHP side.  But there are a few cases like -{zh-cn:==Foo==;zh-tw:==Bar==}-
+(05:26:15 PM) cscott-free: which should really be rewritten as == -{zh-cn:Foo;zh-tw:Bar}- ==
+(05:27:19 PM) cscott-free: usual annoying story about balance, templates, markup boundaries, etc.
+(05:26:14 PM) RoanKattouw: Right
+(05:25:13 PM) cscott-free: At any rate, I guess the easiest way to get started here is to implement it as a 'boring' LeafNode and not allow direct editing, you'll have to use an inspector
+(05:27:15 PM) RoanKattouw: If it's only annotated text, then you could make it an annotation that would have to do some magic to generate its own content and feed the right content back into data-mw
+(05:29:03 PM) cscott-free: yeah, with an annotation i just hit a roadblock in ve.dm.Converter:getDomSubtreeFromData which doesn't give me a way to return the annotation *and* the data contained as an array from toDataElement, the way that nodes can
+(05:29:30 PM) cscott-free: so I might patch that and handle the case where toDataElement returns an array of length > 1 from toDataElement
+(05:29:45 PM) cscott-free: but figured I'd check to make sure I wasn't missing something obvious first
+(05:30:01 PM) RoanKattouw: Yeah you'll have to invent something new here
+(05:30:16 PM) RoanKattouw: In both directions
+(05:30:31 PM) RoanKattouw: Or add pre- and post-processing steps
+(05:30:15 PM) cscott-free: I might also just give in an generate explicit <span typeof=""mw:LanguageVariant/raw"">foo</span> for some of these cases
+(05:30:24 PM) cscott-free: which would be a more direct analog of <nowiki>
+(05:30:43 PM) RoanKattouw: Also look at how nowiki works on the way out
+(05:31:07 PM) RoanKattouw: It's not really the same, it drops the annotation, but it might give you ideas
+(05:31:04 PM) cscott-free: If you did -{foo<div>bar}- then I *think* the usual HTML5 treebuilding would split the <span> over the <div> and you'd effectively get -{foo}-<div>-{bar}-
+(05:31:32 PM) cscott-free: that works for the ""raw output"" case, but things get really hairy if there are multiple alternatives.
+(05:31:38 PM) RoanKattouw: Well if the resulting HTML is too weird, you can just alienate it
+(05:32:25 PM) RoanKattouw: Which might even happen automatically because of special treatment of the mw: prefix and protections against misnesting
+(05:33:13 PM) cscott-free: yeah, right now VE is alienating everything which is fine but because the <span>s are empty the result is that the content goes missing
+(05:33:43 PM) cscott-free: again, maybe an indicator that this whole ""empty span to be filled with converted output"" idea isn't all that hot.  we'll see.
+(05:34:20 PM) cscott-free: anyway, I think using a Node and just dealing with non-direct editing is the way to go for the crappy-first-draft.
+(05:34:32 PM) cscott-free: although i'm curious how you planned to allow direct figure caption editing
+(05:41:02 PM) RoanKattouw: cscott: Basically, make captions work the way references work, with their contents being in an internalList item or subdocument, then create a surface on that subdoc and embed it in the image frame
+(05:41:22 PM) RoanKattouw: The subdocuments thing is a refactor I started in 2014 and never finished
+(05:42:25 PM) RoanKattouw: You could also do it without changing the DM representation if you are able to make a surface for a subset of the document
+(05:42:54 PM) RoanKattouw: But the change in representation would allow inline images to retain captions
+(05:44:55 PM) cscott-free: Yeah, I just would want to be able to cursor seamlessly ""into"" the embedded subdoc.",1496353510,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 356739 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):
+[mediawiki/extensions/VisualEditor@master] WIP: Specialized inspector for LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/356739]]
+",1496351770,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis",@cscott Any updates for us on this since it's reopened? :-),1496332721,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+VisualEditor: MWTemplateNode should serialize original HTML if unchanged,"If we get an MWTemplateNode and the user doesn't change it, then in the data->DOM conversion we should serialize it back out the way it came in, including all the other nodes (the template contents) that we normally discard.
+
+Discarding these nodes when the user did change the template (i.e. the attributes changed) is fine and encouraged, but if we also do it when nothing changed, Parsoid's DOM diff algorithm will notice that we changed something in the DOM, causing selective serialization not to skip the template while it should.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366341300,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ctzq3dsxntnt7zcuqb4y,task_description,resolved
+VisualEditor: MWTemplateNode should serialize original HTML if unchanged,Related URL: https://gerrit.wikimedia.org/r/60110 (Gerrit Change I2bbb5d2d6a90c4eb87fa129671112c92a9b931e7),1366474230,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ctzq3dsxntnt7zcuqb4y,task_subcomment,NA
+VisualEditor: Caption tags are stripped from tables when VE converts data model to DOM,"1. Go to: http://ve-change-marking.instance-proxy.wmflabs.org/wiki/Test2
+2. Open page in VisualEditor
+3. Open browser console.
+4. Run ve.dm.converter.getDomFromData( ve.instances[0].documentModel.store, ve.instances[0].documentModel.data.data ).body.outerHTML
+5. You get the following output:
+--------------
+<body><table data-parsoid=""{&quot;tsr&quot;:[0,3],&quot;dsr&quot;:[0,49,3,2]}"">
+This is a caption
+<tbody data-parsoid=""{&quot;dsr&quot;:[24,47,0,0]}""><tr data-parsoid=""{&quot;tsr&quot;:[24,26],&quot;startTagSrc&quot;:&quot;|-&quot;,&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[24,46,2,0]}"">
+<td data-parsoid=""{&quot;tsr&quot;:[27,28],&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[27,46,1,0]}"">Table cell content</td></tr>
+</tbody></table></body>
+----------------
+
+Notice the missing <caption> .. </caption> tags.
+So, when Parsoid gets this, the caption is fostered out and shows up as a diff.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366256040,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bflgm4moy2wypdjtiaao,task_description,resolved
+VisualEditor: Caption tags are stripped from tables when VE converts data model to DOM,...which has already been merged.,1366298405,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bflgm4moy2wypdjtiaao,task_subcomment,NA
+VisualEditor: Caption tags are stripped from tables when VE converts data model to DOM,https://gerrit.wikimedia.org/r/59780,1366298361,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bflgm4moy2wypdjtiaao,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"See bug 45808 for the corresponding Parsoid bug.
+
+Currently editing a redirected page (say ""OLPC"") causes the following Bad Things to happen.
+
+a) the edited page content is saved back to ""OLPC"", overwriting the original #REDIRECT
+
+b) the page content is from ""One Laptop Per Child"", but with an added {{Redirect:OLPC}} template at the top; this extra template gets saved back with the rest of the edits.
+
+In bug 45808, Parsoid will return a special <meta> or <link> tag in the body for redirected pages.  This bug is for the corresponding VE support to recognize that tag and provide a user-friendly interface for editing redirects.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47329",1366223100,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_description,resolved
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"(In reply to Gerrit Notification Bot from comment #10)
+
+Neat! Is there documentation about this panel and/or a place to test it?",1392359125,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Change 95213 merged by jenkins-bot:
+Let users set #REDIRECT and __STATICREDIRECT__ status
+
+https://gerrit.wikimedia.org/r/95213",1392349578,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Change 95213 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT
+
+https://gerrit.wikimedia.org/r/95213",1384373838,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Change 95103 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT, __NOTOC__, & __FORCETOC__
+
+https://gerrit.wikimedia.org/r/95103",1384313396,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,It is also possible to fail to convert a non-redirect page into a redirect (e.g following a merge).,1372791338,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"This is likely obvious to everyone, but:  We need a way to create redirects in VisualEditor from redlinks.
+
+VE is currently (02 July 2013) turned off for editing redirect pages at en.wikipedia.org.  However, it's still possible to create these pages using VE, which end up nowiki-ed and broken.",1372755903,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,Assigning to Jiabao Wu as discussed on bug 48489 comment 4.,1368806633,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Redirect editing disabled by https://gerrit.wikimedia.org/r/64275, will need to be re-enabled when this bug is addressed.",1368789997,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Some quick advice on this one:
+
+* There'll need to be code in DM and UI; the code in Parsoid which it will interact with has just been merged into their master.
+* I'd suggest looking at how {{DEFAULTSORT}} works as a starting point - see https://gerrit.wikimedia.org/r/#/c/61374/ for the DM side.
+* On the UI side, you'd want to create a new panel in the meta-data dialog (""Page settings"" is probably the best name, though that's also the display name of the dialog, but we can fiddle with that later) into which you'd put a checkbox with an associated text box for a page name, with auto-suggest (like the link inspector has).",1368772067,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,There's now a spec for redirects in the DOM: http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Redirects,1366225893,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"This is probably a post-July task; have split off a ""don't fail horribly"" bug as bug 47329, linked.",1366224646,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Since at 2013-04-05 04:29:46 UTC, Zuul no more receives events from Gerrit. It uses a CLI command such as:
+
+    ssh -p 29418  jenkins-bot@manganese.wikimedia.org gerrit stream-events
+
+I did stream-events using both the jenkins-bot user and my own account 'hashar'. While submitting a new patchset or posting a comment: nothing is reported.
+
+The end effect is that no jobs are triggered in Jenkins.
+
+--------------------------
+
+Summary (13/12/2017)
+
+The sshd daemon (Mina) would lost connection on one way connections and hitting some kind of timeout.  That affected Zuul which idles with a `gerrit stream-events`.
+
+Gerrit sshd.idleTimeout got set to 10 days as a workaround https://gerrit.wikimedia.org/r/#/c/58126/
+
+Gerrit patch:
+
+https://gerrit-review.googlesource.com/c/gerrit/+/44472 ([[ https://gerrit.googlesource.com/gerrit/+/79b91bfe746121a81a785bdd3b24df2096410c55 | 79b91bfe ]]) is the Gerrit patch.
+",1365152280,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_description,resolved
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #24)
+> We previously rolled back to a gerrit that exposed the problem again :-(
+> 
+
+To expand on this, last week when we tried upgrading to 2.7-rc1-424-gef469ac we hit a bunch of problems so we rolled back. However, I rolled too far back to 2.6-rc0-144-gb1dadd2.war instead of 2.6-rc0-154-gfcdb34b which lacked the SSH timeout fix mentioned above.",1370873901,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"We previously rolled back to a gerrit that exposed the problem again :-(
+
+In case we ever do this again: To keep the zuul<->gerrit connection
+alive, it suffices to have at least one event fed to zuul each 10
+minutes.
+
+So for example clone our gerrit-ping repo.
+Restore
+  https://gerrit.wikimedia.org/r/#/c/58060/
+Fetch patch set 1.
+And run
+
+  while true ; do date ; ssh gerrit.wikimedia.org gerrit review -m ""'recheck'"" --verified 0 75be73703978e75a25d5e3bb5685c51580af3060 ; sleep 240 ; done
+
+in a shell (I had ssh configured to automatically supply username and gerrit port).
+
+Gerrit 2.6-rc0-154-gfcdb34b is the first version that we deployed and
+contained the fix.",1370873749,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,*** Bug 49330 has been marked as a duplicate of this bug. ***,1370869884,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #21)
+> Lowering priority and severity since we have a workaround now.
+
+Now actually doing so for priority too.",1368525775,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Lowering priority and severity since we have a workaround now.,1365494859,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,*** Bug 47004 has been marked as a duplicate of this bug. ***,1365449902,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Deployed the upstream patch just now.,1365422685,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #12)
+> (In reply to comment #10)
+> > https://gerrit-review.googlesource.com/#/c/44351/
+> > got submitted to upstream gerrit.
+> > 
+> 
+> It hasn't been reviewed / merged yet however. How long are we willing to
+> wait?
+> Can we apply it to our fork for now?
+> 
+> Jenkins being down is causing lots of workflow problems throughout the
+> different projects.
+
+We don't have a fork, we use vanilla Gerrit :)
+But yes, I'm looking into deploying this now rather than waiting on upstream to merge.",1365417296,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Until we can deploy a new gerrit build, we prevent timeouts by forcing a
+recheck on
+https://gerrit.wikimedia.org/r/#/c/58060/
+every 4 minutes.",1365413039,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Related URL: https://gerrit.wikimedia.org/r/58063 (Gerrit Change I431ff970596aae03b3ab5276303ed18574892b13),1365411081,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Related URL: https://gerrit.wikimedia.org/r/58060 (Gerrit Change Ie0b3b0a5d77a2192abd09a934e780b8e622a1edd),1365410487,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Related URL: https://gerrit.wikimedia.org/r/58059 (Gerrit Change Ie0b3b0a5d77a2192abd09a934e780b8e622a1edd),1365408553,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"For the context:
+
+Zuul is a python daemon running on gallium. It establish a ssh connection as jenkins-bot on manganese.wikimedia.org and runs the 'gerrit stream-events' command.   It expect JSON object to be returned.
+
+Looking at the Zuul log (fgrep GerritWatcher /var/log/zuul/zuul.log), it does emit a stacktrace every 10 minutes:
+
+
+2013-04-08 05:50:48,028 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:00:53,176 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:10:58,266 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:21:03,383 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:31:08,472 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:41:13,594 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:51:18,687 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 07:01:23,782 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+
+A full trace is:
+
+
+2013-04-08 00:12:10,016 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+Traceback (most recent call last):
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 68, in _run
+    self._listen(stdout, stderr)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 52, in _listen
+    self._read(stdout)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 39, in _read
+    data = json.loads(l)
+  File ""/usr/lib/python2.7/json/__init__.py"", line 326, in loads
+    return _default_decoder.decode(s)
+  File ""/usr/lib/python2.7/json/decoder.py"", line 366, in decode
+    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
+  File ""/usr/lib/python2.7/json/decoder.py"", line 384, in raw_decode
+    raise ValueError(""No JSON object could be decoded"")
+ValueError: No JSON object could be decoded
+
+
+Which is stream-events sending some invalid JSON, most probably something like ""Connection timed out after 10 minutes"".    It seems Zuul properly reconnect the ssh connection.
+
+
+Whenever the stream-events for Zuul, it is also blocked for any other user even on a fresh new connection.  For example, I could run the stream-events command using my own account, fill a comment in Gerrit and I get no event on the channel.",1365407692,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #10)
+> https://gerrit-review.googlesource.com/#/c/44351/
+> got submitted to upstream gerrit.
+> 
+
+It hasn't been reviewed / merged yet however. How long are we willing to wait? Can we apply it to our fork for now?
+
+Jenkins being down is causing lots of workflow problems throughout the different projects.",1365397526,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Raising importance, this needs fixing ASAP. We need testing. Not just to save work, but because we (and by design and intention) rely on it automatically happen and performing the merge action on approval.
+
+Also the lack of postmerge events is blocking (auto-deploy for certain projects).",1365391228,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Although I cannot reliably reproduce the problem, the culprit seems to
+be gerrit's version bump of Apache SSHD to 0.6.0, which comes with
+closing of idle ssh connections.
+
+Upon 10 minutes of inactivity, gerrit disconnects Zuul, and Zuul has
+to reconnect. Gerrit accepts the connection, but sometimes refuses to
+stream events over the new connection. There seems to be some race
+condition in gerrit when Zuul reconnects.
+
+We can mitigate the problem by having at least 1 commit every 10
+minutes... Go, programmers go :-))
+
+To also have a solution until we get that commit density 24/7,
+https://gerrit-review.googlesource.com/#/c/44351/
+got submitted to upstream gerrit.
+
+(We cannot simply downgrade gerrit to the last known good version, as
+that would require database schema downgrading, which currently is not
+supported by gerrit)",1365379934,PHID-USER-pntojlcbclwhuip53bix,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Stuck again but this time show-queue gives me:
+
+Task     State                 Command
+------------------------------------------------------------------------------
+5229a073                       git-upload-pack '/mediawiki/extensions/VisualEditor' (shirayuki)
+aad42f27 07:18:57.201          inside-wmf/mediawiki/extensions/FundraisingEmailUnsubscribe
+------------------------------------------------------------------------------
+
+Logged a message on IRC about it and pinged ops list.",1365319742,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Changing back to git/gerrit. Zuul has no issue, it is Gerrit holding the events and not emitting them.",1365318838,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"The Zuul log is full of the following:
+
+2013-04-06 17:02:55,441 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+Traceback (most recent call last):
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 68, in _run
+    self._listen(stdout, stderr)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 52, in _listen
+    self._read(stdout)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 39, in _read
+    data = json.loads(l)
+  File ""/usr/lib/python2.7/json/__init__.py"", line 326, in loads
+    return _default_decoder.decode(s)
+  File ""/usr/lib/python2.7/json/decoder.py"", line 366, in decode
+    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
+  File ""/usr/lib/python2.7/json/decoder.py"", line 384, in raw_decode
+    raise ValueError(""No JSON object could be decoded"")
+ValueError: No JSON object could be decoded",1365268135,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Restarted again, since stram-events hung. The output from the queue is kind of weird & concerning:
+
+$ ssh gerrit.wikimedia.org gerrit show-queue -w
+Task     State                 Command
+------------------------------------------------------------------------------
+9c0dc448                       com.google.gerrit.sshd.commands.StreamEvents$3@6435207f
+85d6cd95                       com.google.gerrit.sshd.commands.StreamEvents$3@5be8a53e
+c54125b8                       com.google.gerrit.sshd.commands.StreamEvents$3@6b8b896
+a0d428db                       com.google.gerrit.sshd.commands.StreamEvents$3@495e834c
+0323c3c0                       com.google.gerrit.sshd.commands.StreamEvents$3@5bfe1835
+49cc90ac                       com.google.gerrit.sshd.commands.StreamEvents$3@6e76ec2
+e9bf84a4                       com.google.gerrit.sshd.commands.StreamEvents$3@44188618
+4617a0ff                       com.google.gerrit.sshd.commands.StreamEvents$3@260bb495
+5e8f7686                       com.google.gerrit.sshd.commands.StreamEvents$3@4a7cb5b6
+fe9f4ab9 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@40811f5d
+3e416208 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7194d12c
+1e449e17 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5d3233c0
+de9a86cc waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7efe402f
+9ea40e12 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@ae3b20d
+bea9d2e8 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6abe7910
+be3472ba waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6130d9f5
+5e4a1628 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4e3595ac
+1915a152 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@417de5ee
+3943c55a waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1ff57751
+9938b1f3 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5a31e6f7
+f911ad68 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2329064
+593eb9dd waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@f04a851
+9982f1fc waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@30828dd9
+665afa9e waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2c6c773b
+066e9e41 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@507d946
+23f714d9 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4b2eba70
+0ff474d2 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@68d2359f
+6fc0906b waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@40be8f7c
+835cc5a8 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1ebe3719
+63619163 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5a135a13
+c3563d8b waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2c7ec398
+a35b09b3 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@365b46fa
+0370d533 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2290e2f7
+e36ca160 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5624d7db
+436a4d46 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@cd7970c
+23671980 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1dfd9b6a
+63fd11f8 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@74e65b87
+83fda551 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3f833806
+5d722e74 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3fd3327d
+bd77aa62 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4297cd47
+9d7c2648 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7c261278
+bdab2a74 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2786c3f5
+baa810b1 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@ab1e19
+7f44cb17 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6244fba6
+bf4ec337 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@194923d6
+df493731 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@10cfc392
+ff2f5b61 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4649853e
+1f334fd3 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4cacd7f
+7f160b2c waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1ee581b1
+046d445a waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6da59b4f
+64b8c066 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@137797c6
+848db42c waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@108d5226
+4926f573 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2e0c4547
+8bfdc551 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1e794f4e
+2b8db900 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2e459983
+6b02d146 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@27984fef
+cb073d54 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5b617f30
+ab0c4979 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5de5572e
+eb0d6177 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@45a5965c
+0b11d594 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7a3295bc
+783069a2 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@a7e838
+46810952 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@f7eb4de
+267e5542 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7bbebd2a
+868b8174 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@27754fde
+c694199b waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6ce8c0f
+6688cd79 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@624d3046
+c6e3b962 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@479462c4
+06f1d196 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5ee05692
+554535c0 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3830aedd
+b235a762 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4284bfd
+f23f9f40 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@399c7615
+923ae350 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4f0c7a3f
+d244dbcb waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7ac6658a
+3249b7e2 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@773485fe
+7253af98 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3c2de6a4
+1246f3d4 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@698137d9
+5250eb8b waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5a53bbe7
+5288eb78 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2f556905
+cc3d20e4 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1061df8a
+2c32bc16 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2279bdac
+0c2fb8ac waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@669378e2
+0c5a59a0 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@66280ecb
+6c4e75e4 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4fe365d2
+4c4b71d4 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@99ae56d
+f650f82e waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@184c5c08
+e71cc87a waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3d2e1dae
+d36dcb8e 12:18:22.186          push gerritslave@formey.wikimedia.org:/var/lib/gerrit2/review_site/git/mediawiki/extensions/FundraisingEmailUnsubscribe.git
+da7faee1 19:42:45.214          Log File Compressor
+------------------------------------------------------------------------------
+  88 tasks",1365250715,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #4)
+> Ariel restarted Gerrit on manganese. That unbroken the stream-events thus
+> cleaning the issue.
+
+Thanks. Lowering priority.",1365156991,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Ariel restarted Gerrit on manganese. That unbroken the stream-events thus cleaning the issue.
+
+I am leaving this bug open for monitoring / investigation.  There must be some regression in Gerrit since we upgraded it yesterday.",1365154819,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Restarted Zuul just in case: nothing. Definitely on Gerrit side.,1365154404,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Gerrit has been upgraded with https://gerrit.wikimedia.org/r/#/c/57508/
+Which got merged on Apr 4, 2013 20:29 (UTC).
+
+Apparently Gerrit got restarted at 20:44 (UTC), the Zuul log shows errors 500 at that time.
+
+The last event received by Zuul was on 2013-04-05 04:26:56 (UTC) then the JSON events cant be decoded / are not received:
+
+2013-04-05 04:29:46,092 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+Traceback (most recent call last):
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 68, in _run
+    self._listen(stdout, stderr)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 52, in _listen
+    self._read(stdout)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 39, in _read
+    data = json.loads(l)
+  File ""/usr/lib/python2.7/json/__init__.py"", line 326, in loads
+    return _default_decoder.decode(s)
+  File ""/usr/lib/python2.7/json/decoder.py"", line 366, in decode
+    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
+  File ""/usr/lib/python2.7/json/decoder.py"", line 384, in raw_decode
+    raise ValueError(""No JSON object could be decoded"")
+ValueError: No JSON object could be decoded",1365154348,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,This is a major regression in our development workflow.,1365153289,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+VisualEditor: Normalize all preservation to use HTML store,"All HTML preservation should be changed to store the full HTML of the node/annotation and use the HTML store. This means removing the html/* attributes from nodes, and the strange things (original tag name and attributes) we put in annotations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364432880,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pi36geznysiuvpgm2xg5,task_description,invalid
+VisualEditor: Normalize all preservation to use HTML store,Roan tells me we went in a different direction with this.,1370307483,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pi36geznysiuvpgm2xg5,task_subcomment,NA
+VisualEditor: Normalize all preservation to use HTML store,This also needs corresponding changes in the CE code for whitelisted rendering.,1364433518,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pi36geznysiuvpgm2xg5,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,"Though T41598 will mean that VisualEditor will be able to edit infoboxes as they are now (alongside other templates), in the near-future Wikidata will replace a great many of the entries in these infoboxes with Wikidata queries (syntax still to be locked down).
+
+For the VisualEditor to be truly useful for users in this context, users should be able to:
+* add, review, modify and remove references to existing Wikidata queries;
+* add or amend arbitrary Wikidata queries for the above; and
+* do so in both VisualEditor-mode contexts (paragraphs of text etc.) and wikitext-mode contexts (like the template dialog as it will initially be).
+
+--------------------------
+**See Also**:
+{T41598}",1364168100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wlq23wlr4vjsce4a5eom,task_description,open
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,Is this task related to {T131661} or vice versa?,1461569518,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,"[[ https://de.wikipedia.org/wiki/Wikipedia_Diskussion:Wikidata#Listenerstellung | Here ]] I made a detailed proposal for a mechanism to edit Wikidata claims in every mode you can view a page. (wikitext, visual editor, preview, view).
+
+If you are interested, I can transakte it form German to English.",1461510555,PHID-USER-4z6eerx3m7iocsrcpku5,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,"[[ https://de.wikipedia.org/wiki/Wikipedia_Diskussion:Wikidata#Listenerstellung | Here ]] I made a detailed proposal for a mechanism to edit Wikidata claims in every mode you can view a page. (wikitext, visual editor, preview, view)",1461510510,PHID-USER-4z6eerx3m7iocsrcpku5,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,I consider this very important. We'll unfortunately not be able to dedicate resources to this in the near future. Does your team have them? We should discuss in this case how exactly this should all look like in the end.,1383578295,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,[replacing wikidata keyword by adding CC - see bug 56417],1383221707,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+VisualEditor: Annotation API fixes,"* Make toHTML() return real DOM nodes, we don't need the weird construction for CE any more
+* Pass in the content so it's possible to have rules like ""if the annotation only covers whitespace, strip it""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363986660,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ywpcq2rcuhvgvzt5k6zj,task_description,resolved
+VisualEditor: Annotation API fixes,It's a T39835 issue.,1428423652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ywpcq2rcuhvgvzt5k6zj,task_subcomment,NA
+VisualEditor: Annotation API fixes,"I didn't know whether to reopen this or add a note to T39835, but looks like it's still possible to [[ https://fr.wikipedia.org/w/index.php?title=Asselin_(entreprise)&curid=8746091&diff=113502024&oldid=112208671 | create an empty wikilink ]]? ",1428045874,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ywpcq2rcuhvgvzt5k6zj,task_subcomment,NA
+VisualEditor: Annotation API fixes,Now done.,1366141186,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ywpcq2rcuhvgvzt5k6zj,task_subcomment,NA
+[Regression] VisualEditor: Error in load() leaves page in dimmed state (Uncaught TypeError: Cannot call method 'removeAllListeners' of null),"Steps to reproduce issue:
+* MediaWiki + VisualEditor (no Parsoid)
+* Edit page (dims the page while loading)
+* Error pops up (parsoidserver-http-curl-error)
+* Cancel
+
+Expected:
+ Page undims.
+
+Actual:
+ Page still dimmed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363973460,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qe3ooothxjpeykl2xzld,task_description,resolved
+[Regression] VisualEditor: Error in load() leaves page in dimmed state (Uncaught TypeError: Cannot call method 'removeAllListeners' of null),"Change-Id: I91ad2b110c2c523a4bb367407e3f33a953328ab4
+
+That should fix it for now (quick fix). I'm now going to look into how much of this can be refactored to avoid this in the first place. It's all a bit too fragile.",1363976526,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qe3ooothxjpeykl2xzld,task_subcomment,NA
+[Regression] VisualEditor: Error in load() leaves page in dimmed state (Uncaught TypeError: Cannot call method 'removeAllListeners' of null),"Caused by I7769bd5a5b79f1ab36f258ef9f2be583ca503ce6.
+
+In the refactoring Trevor moved the initialisation of the DOM element for the save/cancel buttons from the ve.init.mw.ViewPageTarget constructor to ve.init.mw.ViewPageTarget#setupToolbarButtons, which isn't called until after a successful load.
+
+So, when #load() is called from #activate() and fails a loadError is emitted. onLoadError then calls #deacativate() which calls #tearDownToolbarButtons()
+
+But tearDownToolbarButtons is unable to call this.toolbarCancelButton.removeAllListeners because the button doesn't exist yet because setupToolbarButtons was never called.",1363976008,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qe3ooothxjpeykl2xzld,task_subcomment,NA
+VisualEditor: Trying to auto select a word just after an alien node causes an exception in rangy.,"1. Load the 'aliens' example document.
+2. Place the cursor in front of the first 'Lorem' and hit the link button.
+3. Observe the exception
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363548060,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2a3roys3zrsyau3jssx7,task_description,resolved
+VisualEditor: Trying to auto select a word just after an alien node causes an exception in rangy.,Marking as fixed for -04-01 as it wasn't for -03-18.,1364223708,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2a3roys3zrsyau3jssx7,task_subcomment,NA
+VisualEditor: Trying to auto select a word just after an alien node causes an exception in rangy.,Looks to be fixed in master now. Not sure which commit did it....,1364218671,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2a3roys3zrsyau3jssx7,task_subcomment,NA
+VisualEditor: Trying to auto select a word just after an alien node causes an exception in rangy.,"Ed, I can't reproduce it the way you described it. Please note that around first 'Lorem' (first paragraph) there is no alien (inline nor block).",1363801281,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-2a3roys3zrsyau3jssx7,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"**Author:** `lukebenes`
+
+**Description:**
+I see from [http://en.wikivoyage.org/wiki/Wikivoyage:Accommodation_listings The Accomodations Listing suggested style you want people to continue to use the wikitravel tags. But I do not see any tools to automate the process. 
+
+If you look at the Add and Edit Listing Feature listing like those that can be found [http://wikitravel.org/en/Wikitravel:Small_city_article_template#Sleep here] and [http://wikitravel.org/en/Trat#Sleep here]? You'll see there is a tool to edit these tag. 
+
+This tags is extremely useful to organize data and make quick edits. For example, I have fixed many incorrect phone numbers and addresses using this helpful tool. Please consider adding this feature the MediaWiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1363453140,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tqro35vsrplftuemdxbd,task_description,declined
+Create a VisualEditor plugin tool to add/edit Listings,"{T354997}
+
+Listings nowdays are just template calls, which VisualEditor has reasonable tools to edit.",1719889959,PHID-USER-escte3psz5yfd2nj3jzr,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,">>! In T48225#2501154, @T.seppelt wrote:
+> Since listings are highly structured and can be shared across several Wikivoyage language versions, Wikidata editing should be implemented before rolling this out.
+
+Certainly, I think storing this data in Wikidata would be a good move. I'm not absolutely sure it should happen first, but I suppose it depends on who wants to work on what. :-)",1469817709,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"Since listings are highly structured and can be shared across several Wikivoyage language versions, Wikidata editing should be implemented before rolling this out. I added T141345 for this. 
+
+Note also that there is https://en.wikivoyage.org/wiki/Wikivoyage:Listing_editor, a tool especially designed for editing listings.",1469686526,PHID-USER-yyjb72nqrow4ij7mzhhm,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"Note that, in my view, this is not a blocker for enabling the visual editor on Wikivoyages for all users. This is because almost no uses of `<listing>`s are done directly in wikitext, but instead through a template, which could do with some TemplateData love, but is supported fine already.
+
+If you think I'm wrong please shout. :-)",1459668127,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"**lukebenes** wrote:
+
+Have you taken a look at WP:HOTCAT?
+
+http://en.wikipedia.org/wiki/Wikipedia:HC
+
+HotCat is a JavaScript program that helps registered users easily remove, change and add categories to Wikipedia pages. This is very similar to the functionality that we need for the Listing Editor.",1371640823,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"This is about the Listings extension which is unique (in Wikimedia land) to Wikivoyage - https://www.mediawiki.org/wiki/Extension:Listings
+
+It creates the following tags:
+
+<buy>
+<do>
+<drink>
+<eat>
+<listing>
+<see>
+<sleep>
+
+They are used to provide structured mark-up and hinting of recommendations for WV listings of places to go.
+
+Sorry for the confusion. :-)",1364934457,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"We weren't talking about any extension. This report was filed against MediaWiki core. Happy to move it to the right place, as long as we know what is the right place.
+
+Luke, are you saying those tags were created in the Wikitravel times? If so, it would be useful to know how did they handle them.",1364933198,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"Actually, on reflection this should live in the Extension we're talking about, and block against a tracker for such creations in VE itself. Sorry to mess this around.",1364926961,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"Looking at our roadmap, the implementation of this feature looks more like a candidate for a VisualEditor plugin. 
+
+MediaWiki core features must be generic enough for different wikis and must be reviewed and integrated by core maintainers. Visual Editor plugins can be developed by anybody and it is perfecty ok to have them for very specific purposes e.g. a Wikivoyage plugin.",1364925993,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"**lukebenes** wrote:
+
+There is a discussion about this feature on the wikivoyage site here:
+http://en.wikivoyage.org/wiki/Wikivoyage:Roadmap/Improved_editing_interface",1363529899,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+VisualEditor: Clean up inconsistent documentation of event emissions,"Some events are undocumented (like ve.dm.Surface.prototype.change, which emits multiple events but documents none), most have the event name without quotes, but some have single quotes (ve.dm.Surface.addInsertionAnnotation) or double quotes (ve.ui.Toolbar.prototype.onContextChange). Parameters sometimes are documented and sometimes aren't, there's no clear distinction between ""parameters aren't documented"" and ""there aren't any"", and in no case do we document the types and descriptions of event parameters, we only ever document their names.
+
+We probably also don't document events with @event nearly as often as we should. It's a huge mess.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362706560,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ynwo2pb45ypgaglir47z,task_description,resolved
+VisualEditor: Clean up inconsistent documentation of event emissions,Change-Id: Id879aa769b2c72d86a0322e75dddeb868211ce28,1363763464,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ynwo2pb45ypgaglir47z,task_subcomment,NA
+VisualEditor: Clean up inconsistent documentation of event emissions,Working on it.,1363762434,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ynwo2pb45ypgaglir47z,task_subcomment,NA
+VisualEditor: VE should be able to be 'default' for some namespaces and by user preference elsewise/in others,"Right now VE is either 'default' for some given namespaces, or enabled but only exposed by user preference for some namespaces; it should be possible to have a mixed-installation for testing/etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362704940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jps6ok65jqx3whi4rc2h,task_description,invalid
+VisualEditor: VE should be able to be 'default' for some namespaces and by user preference elsewise/in others,"(In reply to comment #1)
+> If enabled by default, can be disabled by preference?
+
+Currently, yes, though we'll remove this preference when we go from ""opt-in"" to ""opt-out"" in July.
+
+However, this bug isn't really necessary any more as we've just last week switched VE to default-on for Main, User and also the VisualEditor namespaces on mediawikiwiki. Closing as we no longer need this.",1367604375,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jps6ok65jqx3whi4rc2h,task_subcomment,NA
+VisualEditor: VE should be able to be 'default' for some namespaces and by user preference elsewise/in others,"If enabled by default, can be disabled by preference?",1367604125,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jps6ok65jqx3whi4rc2h,task_subcomment,NA
+VisualEditor: split paragraphs in a listItem should not be considered 'wrapper' paragraphs,"Start a list item and type 'a', now hit shift-enter and type b.
+
+Expected diff:
+*a<p>b</p>
+
+Actual diff:
+*ab
+
+The paragraph created when you create the list has internal.generated = 'wrapper'. This property gets copied when you split the list. Two wrapper paragraphs next to each other apparently get merged into one.
+
+The only way wikitext can have two paragraphs in a list is with HTML so extra paragraphs must be full HTML paragraphs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362418080,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-u7qyhofavuvw7qvhg5w6,task_description,resolved
+VisualEditor: split paragraphs in a listItem should not be considered 'wrapper' paragraphs,Fixed by https://gerrit.wikimedia.org/r/#/c/52046/,1363373310,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-u7qyhofavuvw7qvhg5w6,task_subcomment,NA
+[TUX] Browser support matrix,"Create a list of supported browsers and document it.
+
+Also make sure that TUX actually works with those browsers.
+
+--------------------------
+**Version**: master
+**Severity**: enhancement
+**URL**: http://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix",1362144360,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_description,resolved
+[TUX] Browser support matrix,"We will follow MediaWiki's browser support matrix for Modern (Grade A). With increasing number of linters, and since this area of code is not rather stable, it is much less likely that we introduce issues that would not work on some of the supported browsers.",1607415848,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,"On (c), https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4381 mentions IE, Firefox, Safari and Chrome, but no versions.",1408803169,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,"https://www.mediawiki.org/wiki/Compatibility was recently updated and may serve as starting point; there is no need to restate the obvious, but it's useful to highlight any deviation from common expectations.
+
+As far as I can see, Special:Translate and others have some browser tests, but:
+a) I have no idea how comprehensive they are; it would be useful to file bugs for any missing one which should be added;
+b) I don't know for sure whether they're used or how and where the outcomes are reported, though I think there is some degree of usage as part of the monthly [[mw:MLEB]] release;
+c) I have absolutely no idea about the browsers used for such tests.
+
+Is anyone able to shed some light on these questions, or point to someone who knows?",1408802235,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,Any updates on this?,1382785247,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,"Harsh: 
+Do you plan to work on this any time soon?
+Do you need any input from the QA/browsertesting team (that would mean adding chrismcmahon@ and zfilipin@ to the CC list of this bug report)?",1373281412,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,"We had triaged this bug last month and Harsh Kothari had wanted to work on this. I'm adding him on cc for this bug.
+
+Harsh, would you be working on this any time soon? Thanks.",1370235510,PHID-USER-ttw4tpoosxc4pbmskrla,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,Runa: this has been assigned you a month ago. Could you provide a status updated and whether you are currently working on this?,1369473003,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,This is very much related to getting automated integration testing. Currently the scenarios are at http://etherpad.wikimedia.org/i18n-qa (ULS only so far). We should get at least 20 or so tests for TUX.,1362421102,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+VisualEditor: Implement remaining wrap(each) methods in SurfaceFragment,"unwrapNodes & rewrapNodes are not implemented, and wrapNodes doesn't calculate selections correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361910180,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fsxicsfwrmjxla4crdyz,task_description,resolved
+VisualEditor: Implement remaining wrap(each) methods in SurfaceFragment,Answer: yes. Marking as fixed.,1368042225,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsxicsfwrmjxla4crdyz,task_subcomment,NA
+VisualEditor: Implement remaining wrap(each) methods in SurfaceFragment,Isn't this now (long) done?,1367028640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fsxicsfwrmjxla4crdyz,task_subcomment,NA
+"Checkstyle report unable to fetch context, showing ""No description available. Please upgrade to latest checkstyle version.""","e.g. https://integration.mediawiki.org/ci/job/mwext-Scribunto-jslint/233/checkstyleResult/file.984307183/type.1174449419/
+
+It does that almost everywhere (including VisualEditor and MediaWiki core). Sometimes it does work though, weird.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1361834280,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jbdbttk2lguhy7gmvjn2,task_description,declined
+"Checkstyle report unable to fetch context, showing ""No description available. Please upgrade to latest checkstyle version."""," Timo said it had a very confusing output due to :
+- our builds not chaining because of different patchsets being run
+- disabled checks being listed anyway
+
+Checkstyle plugin is no more used. Closing the bug.",1372185531,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jbdbttk2lguhy7gmvjn2,task_subcomment,NA
+"Checkstyle report unable to fetch context, showing ""No description available. Please upgrade to latest checkstyle version.""","Unassigning self, I suspect that is either:
+
+- JSHint does not add a description of the error in its XML output
+- Jenkins Checkstyle plugin is missing description for JSHint errors
+
+Most probably an upstream issue.",1362978350,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jbdbttk2lguhy7gmvjn2,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"MW-specific code should be split from the VisualEditor itself; mediawiki/extensions/VisualEditor.git should only be the MW-specific items (integration; MW-specific plugins; MW-specific plugin overloading).
+
+Target repository for VE itself already exists: VisualEditor/core.git
+
+(Future plugins should be under VisualEditor/plugin/….git.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1361756160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_description,resolved
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,Now complete.,1387564647,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 102842 merged by jenkins-bot:
+Use submodule for VisualEditor core
+
+https://gerrit.wikimedia.org/r/102842",1387563773,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 102842 had a related patch set uploaded by Jforrester:
+Use submodule for VisualEditor core
+
+https://gerrit.wikimedia.org/r/102842",1387507385,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 102825 merged by jenkins-bot:
+Update .gitreview and remove MW-specific things
+
+https://gerrit.wikimedia.org/r/102825",1387492495,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 102825 had a related patch set uploaded by Jforrester:
+Update .gitreview and remove MW-specific things
+
+https://gerrit.wikimedia.org/r/102825",1387491726,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 101845 merged by jenkins-bot:
+Split ext.visualEditor.mwcore out of ext.visualEditor.core
+
+https://gerrit.wikimedia.org/r/101845",1387316087,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 101845 had a related patch set uploaded by Jforrester:
+Split ext.visualEditor.mwcore out of ext.visualEditor.core
+
+https://gerrit.wikimedia.org/r/101845",1387214862,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,https://gerrit.wikimedia.org/r/71755 addresses part of this by splitting files between modules/ve/ and modules/ve-mw/,1372875122,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Generalize logic in ve.FormatAction,"* Rules for ""heading should not be in list"" in CE rather than DM
+* Function that isolates and unwraps things until they conform to the CE rules
+** FormatAction does these things, but is hardcoded for lists
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361475480,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-q2sq3hniv3ip4n5l2tv4,task_description,resolved
+VisualEditor: Generalize logic in ve.FormatAction,Reassigning to Ed because he's already doing this anyway.,1362528092,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-q2sq3hniv3ip4n5l2tv4,task_subcomment,NA
+VisualEditor: Refactor ve.FormatAction.splitAndUnwrap to use SurfaceFragment,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361474880,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lfnwgg3zbq7kwd5zrvyd,task_description,resolved
+VisualEditor: Refactor ve.FormatAction.splitAndUnwrap to use SurfaceFragment,Merged.,1361839902,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfnwgg3zbq7kwd5zrvyd,task_subcomment,NA
+VisualEditor: Refactor ve.FormatAction.splitAndUnwrap to use SurfaceFragment,https://gerrit.wikimedia.org/r/#/c/50834/,1361834711,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-lfnwgg3zbq7kwd5zrvyd,task_subcomment,NA
+VisualEditor: Implement remaining wrapAll methods in SurfaceFragment,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361474340,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zcg333mt7cdvw4jrhfyr,task_description,resolved
+VisualEditor: Implement remaining wrapAll methods in SurfaceFragment,Merged.,1361839869,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zcg333mt7cdvw4jrhfyr,task_subcomment,NA
+VisualEditor: Implement remaining wrapAll methods in SurfaceFragment,Finished off in https://gerrit.wikimedia.org/r/#/c/50824/,1361832639,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zcg333mt7cdvw4jrhfyr,task_subcomment,NA
+VisualEditor: Implement remaining wrapAll methods in SurfaceFragment,Partially fixed in https://gerrit.wikimedia.org/r/#/c/50429/,1361572627,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zcg333mt7cdvw4jrhfyr,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"**Author:** `visionary.incident`
+
+**Description:**
+I cannot input japanese consecutive characters in the beginning of the line.
+
+Firefox version is 18.0.2 .
+
+For example
+
+inputed
+あああああ
+
+outputed
+ああ
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361473320,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_description,resolved
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,I suspect this is no longer broken. Please re-test.,1423750103,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"Just as a note, we are refactoring the Surface code in ContentEditable to make this fixable, hence the delay.",1381271546,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,*** Bug 53064 has been marked as a duplicate of this bug. ***,1377348845,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"Inez, is there an update on this bug?",1367547839,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"Only works if the line has no text.
+Confirmed on bullet-type lines too.",1364125968,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,I was able to confirm it (using Katakana) in Chrome on MacOS. Apparently it depends on the speed of typing (Selenium test for it is going to be interesting).,1361476901,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: Increase test coverage of ve.FormatAction,"We currently have 0 tests for ve.FormatAction.*
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361404500,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sgmrkdjbdkbtrt6o6mwh,task_description,resolved
+VisualEditor: Increase test coverage of ve.FormatAction,Merged.,1361566138,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sgmrkdjbdkbtrt6o6mwh,task_subcomment,NA
+VisualEditor: Increase test coverage of ve.FormatAction,https://gerrit.wikimedia.org/r/#/c/50137/,1361410249,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sgmrkdjbdkbtrt6o6mwh,task_subcomment,NA
+VisualEditor: Fix dependency issues between ve.js and ve.init.platform,"In ve.js, function ve.msg:
+// TODO: Fix dependency issues between ve.js and ve.init.platform
+
+I don't know how this should be fixed exactly, Timo put this comment in in 407de829dd8f2e51c22a8378dc70c79fc6645d1e . I did notice that running the VE tests from Special:JavaScriptTest doesn't work because ve.msg() errors out with 've.init.platform' undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361311500,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zkyntw7nvnjqikzefrbn,task_description,resolved
+VisualEditor: Fix dependency issues between ve.js and ve.init.platform,Change-Id: I47d7d92495974572194700c98a219d22ecbfaf4b,1364960892,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zkyntw7nvnjqikzefrbn,task_subcomment,NA
+VisualEditor: Fix dependency issues between ve.js and ve.init.platform,"This is currently blocking us from enabling QUnit for extension VisualEditor as the race-condition is happening consistently in Chrome, Safari and PhantomJS.
+
+I tracked it down to the calls to ve.msg from the global scope, such as:
+
+
+@@ ve.ce.Surface.static.$phantomTemplate = $ (.. ) .attr( {
+		'title': ve.msg( 'visualeditor-aliennode-tooltip' ),",1364959167,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zkyntw7nvnjqikzefrbn,task_subcomment,NA
+VisualEditor: Fix dependency issues between ve.js and ve.init.platform,"(In reply to comment #0)
+> In ve.js, function ve.msg:
+> // TODO: Fix dependency issues between ve.js and ve.init.platform
+> 
+> I don't know how this should be fixed exactly, Timo put this comment in in
+> 407de829dd8f2e51c22a8378dc70c79fc6645d1e . I did notice that running the VE
+> tests from Special:JavaScriptTest doesn't work because ve.msg() errors out
+> with
+> 've.init.platform' undefined.
+
+Indeed, that's the reason why. They sometimes fail, and sometimes work.
+
+It appears to be a race-condition and/or absent dependency that should be fixed or lazy-loaded or something else to make sure one has the other.",1361312943,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zkyntw7nvnjqikzefrbn,task_subcomment,NA
+AutoLoader adds $IP to network share path,"**Author:** `kevinrose`
+
+**Description:**
+I am running under IIS with the files stored on network storage.
+I get an error from line 1142 in includes\AutoLoader.php when the $filename being passed is already a network share. Specifically in my case it then adds $IP a second time.
+
+Here are the variables from my situation:
+
+From debugging we know that:
+$IP is set to ""\\server\share\mediawiki""
+
+The offending class being loaded in LocalSettings.php:
+
+require_once(""$IP/extensions/WikiEditor/WikiEditor.php"" );
+
+After line 1142 $filename = ""\\server\share\mediawiki\\server\share\mediawiki\extensions\WikiEditor\WikiEditor.php""
+
+Line 1140 checks if the first character is a / (root), or the second character is a : (windows local drive).
+
+To work around the problem I added a third check, that the second character is a slash (windows network share):
+
+		if ( substr( $filename, 0, 1 ) != '/' && substr( $filename, 1, 1 ) != ':' && substr( $filename, 1, 1 ) != '\\') {
+
+--------------------------
+**Version**: 1.20.x
+**Severity**: normal",1360770540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_description,declined
+AutoLoader adds $IP to network share path,"Since nobody cared too much for the last seven years, we assume nobody cares too terribly much. And even if we fixed it, we couldn't test it.",1586895753,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"Tagging CPT as potentially interested party in Autoloader and third-party usees of it. I'm not sure if the above is still applicable, or whether running MediaWiki on Windows from a network share is supported or not. If not, we should probaby document that. If we do, then the above bug seems easily fixable as described in the last comment.",1586730716,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"**kevinrose** wrote:
+
+I forgot about this bug - upgraded my mediawiki to latest snapshot of 1.22 and the issue came back.
+
+The issue isn't related to a particular extension, but to the use of the AutoLoader.  Above the samples were with WikiEditor. This time I came across it with VisualEditor which uses AutoLoader.
+
+
+In 1.22 latest snapshot 7/16/2013 line 1148-1152 of file includes\AutoLoader.php:
+
+		# Make an absolute path, this improves performance by avoiding some stat calls
+		if ( substr( $filename, 0, 1 ) != '/' && substr( $filename, 1, 1 ) != ':' ) {
+			global $IP;
+			$filename = ""$IP/$filename"";
+		}
+
+
+
+This handles the case where $filename is a linux full path (starting at /) or a windows full path (with the drive letter i.e. c:) but does not handle the case of a network share on windows (\\server\path)
+
+Again fix in first message does address this:
+
+if ( substr( $filename, 0, 1 ) != '/' && substr( $filename, 1, 1 ) !=
+':' && substr( $filename, 0, 2 ) != '\\\\')
+
+Adjusted to look specifically for two forward slashes in case there's some other case where one forward slash is ok?",1373980934,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"**michael** wrote:
+
+I experienced the same issue after upgrading to the latest version of GearHost.com's cloudsites platform, which too changed from local drive storage to a network share. Like the original poster, I found the same behavior. Additionally, though, I found that commenting the require_once(""$IP/extensions/WikiEditor/WikiEditor.php"" ); line would temporarily resolve the issue and allow MediaWiki to load, which suggests some dependency between require_once and the autoloader. I applied a similar change to the autoloader file which allowed to uncomment the require_once line successfully. I am running MediaWiki 1.19.1.",1373591943,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,Please confirm that this is a MediaWiki related problem. Otherwise this issue should be closed.,1362546459,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"I think you're confusing ""require"" with ""autoloading"".
+
+The require_once() call you mention:
+> require_once(""$IP/extensions/WikiEditor/WikiEditor.php"" );
+
+that isn't a class but an extension file. This is your own code and placed in your LocalSettings.php, correct?
+
+AutoLoader isn't involved there.
+
+
+> After line 1142 $filename =
+> ""\\server\share\mediawiki\\server\share\mediawiki\extensions\WikiEditor\WikiEditor.php""
+
+Line 1142/1145 of which file? Assuming AutoLoader.php, why is WikiEditor listed in your autoloader configuration?",1360798922,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"**kevinrose** wrote:
+
+Sorry to avoid confusion - the actual error is at line 1145 when the incorrect $filename tries to get required.",1360770629,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"[Very much a longer-term enhancement.]
+
+Parsoid doesn't currently have support for passing on an authenticated user's read right when fetching the wikitext (because the API doesn't support that yet).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1359492240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_description,resolved
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Change 91111 merged by jenkins-bot:
+Support private wikis by forwarding Cookie: headers to Parsoid
+
+https://gerrit.wikimedia.org/r/91111",1383678031,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),Closing again.,1382479475,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Change 91111 had a related patch set uploaded by Jforrester:
+Support private wikis by forwarding Cookie: headers to Parsoid
+
+https://gerrit.wikimedia.org/r/91111",1382404256,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Cookies are now forwarded, and caching is disabled if a cookie is set. Closing this bug as fixed. A content API will have to do its own auth.",1381966182,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Change 85414 merged by jenkins-bot:
+Bug 44483: Forward Cookie header to API
+
+https://gerrit.wikimedia.org/r/85414",1381965890,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"(In reply to comment #4)
+> Random idea:
+> 
+> Could Parsoid be made private (already is, though last I checked it still
+> has a
+> public IP) and use an internal API instead of the public API. Then the
+> responsibility for user rights lays in MediaWiki land, and when the request
+> is
+> in Parsoid we can assume it is authenticated and thus Parsoid can have
+> unrestricted access.
+
+That is what we'll have to do in the longer term once we store HTML. Parsoid might not even be involved in that case, only the content API / storage is. See https://www.mediawiki.org/wiki/User:GWicke/Notes/Storage for the current WIP on that.",1381260438,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Random idea:
+
+Could Parsoid be made private (already is, though last I checked it still has a public IP) and use an internal API instead of the public API. Then the responsibility for user rights lays in MediaWiki land, and when the request is in Parsoid we can assume it is authenticated and thus Parsoid can have unrestricted access.",1380024239,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Change 85414 had a related patch set uploaded by GWicke:
+WIP Bug 44483: Forward Cookie header to API
+
+https://gerrit.wikimedia.org/r/85414",1379754726,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),*** Bug 44313 has been marked as a duplicate of this bug. ***,1360207511,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),Passing on the cookie header from the VisualEditor extension to Parsoid and then from Parsoid back to the API might be enough to enable this. Definitely worth a try.,1359588905,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+VisualEditor: Parsoid (?) issues in deleting text on [[W:User:Edinwiki]],"Deleting multiple lines of selected text
+
+When trying to delete a line of added text, the editor failed. See screenshot.
+
+When reviewing the changes I get an empty ""Latest revision"" and empty ""Your text"". Tried with Chrome and Firefox. When saving, the changes are not committed either.
+
+When trying to delete two lines (see screenshot on the right side), only one line is marked for deletion:
+
+    - Mostly active on [[:bs:Korisnik:Edinwiki|bs-wiki]].
+
+When selecting multiple lines in the same way, it seems that each time only the first line is selected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/wiki/User:Edinwiki
+
+**Attached**: {F10938}",1359113220,PHID-USER-qaslvze35cdv2crgkxjb,PHID-TASK-zjrdtyysctdr2ogcnult,task_description,resolved
+VisualEditor: Parsoid (?) issues in deleting text on [[W:User:Edinwiki]],This is now fixed given the Parsoid update. Sorry for the delay!,1366396774,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zjrdtyysctdr2ogcnult,task_subcomment,NA
+VisualEditor: Parsoid (?) issues in deleting text on [[W:User:Edinwiki]],This appears to be a Parsoid issue - to recheck when Parsoid service is updated in live.,1360207666,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zjrdtyysctdr2ogcnult,task_subcomment,NA
+VisualEditor: Link inspector doesn't function properly when opened in location surrounded by word boundaries,"1. Type 2 spaces
+2. Move the cursor between the two spaces
+3. Press link button or (command|control)+k
+4. Type text for target (if in mw integration you can also choose a suggested target)
+5. Press enter (or click outside the inspector, or press esc)
+6. See that the target text was inserted, but not annotated
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1358470200,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-3otirho2qtinxa5jdm5c,task_description,resolved
+VisualEditor: Link inspector doesn't function properly when opened in location surrounded by word boundaries,Gerrit patch merged.,1360613038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3otirho2qtinxa5jdm5c,task_subcomment,NA
+VisualEditor: Link inspector doesn't function properly when opened in location surrounded by word boundaries,Patched in: https://gerrit.wikimedia.org/r/#/c/47822/,1360198986,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-3otirho2qtinxa5jdm5c,task_subcomment,NA
+VisualEditor: Cursor jumps when backspacing character after alien node,"Steps to reproduce:
+1. Find a paragraph that has an inline node (alien or entity) in it, but not at the end
+2. Move the cursor to the end of the paragraph
+3. Repeatedly press backspace
+4. When there is only one remaining character after the inline node, pressing backspace will remove that character (correct) and move the cursor to the beginning of the line (bad)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1358461560,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-suuligy6idoz5fgoqmha,task_description,resolved
+VisualEditor: Cursor jumps when backspacing character after alien node,I believe that this is now fixed with the new deletion model.,1371780950,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-suuligy6idoz5fgoqmha,task_subcomment,NA
+"Include git submodules, by default, or optionally","Some extensions, such as Extension:GuidedTour, require git submodules.
+
+It would be a very useful enhancement if ExtensionDistributor included these in the download, by default or optionally.
+
+--------------------------
+**Version**: master
+**Severity**: enhancement
+**URL**: https://www.mediawiki.org/wiki/Extension_talk:ExtensionDistributor#Doesn.27t_do_submodules",1358310660,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_description,resolved
+"Include git submodules, by default, or optionally","New tarball generator has been deployed, which now includes submodules.",1406830829,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","(In reply to Kunal Mehta (Legoktm) from comment #3)
+> I've set up an API endpoint for VisualEditor on labs:
+> http://tools.wmflabs.org/extdist/?version=REL1_23&ext=VisualEditor
+> 
+> I don't see any submodules in GuidedTour?
+
+Correct, we forked Guiders so there's no longer a submodule.",1406255839,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","Once we switch to the new labs tarball generator, this will be fixed.",1405547330,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","Change 146430 abandoned by Legoktm:
+Support having multiple API endpoints
+
+Reason:
+We're going to just point everything to labs instead.
+
+https://gerrit.wikimedia.org/r/146430",1405544052,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","I've set up an API endpoint for VisualEditor on labs: http://tools.wmflabs.org/extdist/?version=REL1_23&ext=VisualEditor
+
+I don't see any submodules in GuidedTour?",1405427591,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","Change 146430 had a related patch set uploaded by Legoktm:
+Support having multiple API endpoints
+
+https://gerrit.wikimedia.org/r/146430",1405427302,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","Yeah, we need this for VE too.
+
+Github doesn't support submodules, but it's easy to do this on labs (I already wrote a script to do it). Just requires a few changes to the extension...",1405423855,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+VisualEditor: Diff viewer in weird state after Parsoid error,"Steps to reproduce:
+1. Open VE on a page
+2. Make changes
+3. Stop Parsoid
+4. Click ""Review and save""
+5. Get an error dialog about Parsoid being down. Click ""Cancel"".
+
+The box that's supposed to show the diff is left empty, but the ""Something's wrong"" and ""Looks good to me"" buttons are still there. I can dismiss the box with the up arrow to go back to editing, but we should be doing this (or at least *something*) automatically on failure.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1357693020,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5medlyzpqf3k4z7hksir,task_description,invalid
+VisualEditor: Diff viewer in weird state after Parsoid error,"Yeah, we completely switched around the fetching logic here so that this is now INVALID; sorry.",1392756925,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5medlyzpqf3k4z7hksir,task_subcomment,NA
+VisualEditor: Diff viewer in weird state after Parsoid error,"Everything about this seems different now... ""Review and save"" I guess has become ""Save page"", and you only get an error about Parsoid being down when you then click ""Review your changes"". This dialog offers only an ""OK"" button which simply stops the loading of the review dialog. I don't see an empty diff or ""Something's wrong""/""Looks good to me"" buttons.
+
+Is this bug still valid?",1392560898,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-5medlyzpqf3k4z7hksir,task_subcomment,NA
+Create API to expose editnotices,"Editnotices for pages are not currently exposed in the API, but are expected to be used by any interface of a Wikipedia  editor. This implies that the information should be easily retrievable.
+
+It should be noted that the VisualEditor api has it's own private implementation of listing all edit notices that should be presented to users: https://en.wikipedia.org/w/api.php?action=visualeditor&format=json&paction=metadata&page=List_of_emoticons&uselang=en&oldid=846338965
+
+This should probably be moved to core as well as be exposed via restbase or something similar.
+
+--------------------------
+**Version**: 1.21.x
+**Severity**: enhancement",1357492860,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_description,resolved
+Create API to expose editnotices,"Change 921405 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] Add 'preloadcontent' and 'editintro' in API prop=info%%%
+https://gerrit.wikimedia.org/r/921405",1684594877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+Create API to expose editnotices,"Change 921405 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/core@master] [WIP] Fix 'preload' and add 'editintro' in API prop=info%%%
+https://gerrit.wikimedia.org/r/921405",1684519036,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+Create API to expose editnotices,"Change 74963 abandoned by Umherirrender:
+Api: Add editnotices to prop=info
+
+https://gerrit.wikimedia.org/r/74963",1378323091,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+Create API to expose editnotices,"Change 74963 had a related patch set uploaded by Umherirrender:
+Api: Add editnotices to prop=info
+
+https://gerrit.wikimedia.org/r/74963",1374408099,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+Create API to expose editnotices,"I wonder whether it would be better for prop=info to return the names of the messages containing the notice instead of parsing them itself. The client could parse these using action=parse if it wants HTML.
+
+The main drawback to parsing them in prop=info is that parsing is expensive; prop=revisions, for example, will error out if asked to parse more than one revision, and if we'd add editnotices with parsed output to prop=info we'd have to do something similar there.
+
+
+On a side note, I still don't understand what happened with r48276. Per-page edit noticed were half removed, but the removal wasn't finished even after this was pointed out, and then they were added back 2.5 years later.",1359054060,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","The Translate extension has very nice info icons which bring users from the interface/feature they're seeing to the relevant (translatable) help page on mediawiki.org (all components are documented). See for instance [[ https://meta.wikimedia.org/wiki/Special:PageTranslation | m:Special:PageTranslation ]].
+
+This is a huge task, but it should be done for core as well.
+
+The problem is of course that there's no real(istic) plan to get such help pages done in the next few decades, as they continue to live either on Meta for copyright reasons or even on local wikis for the same + [[ https://meta.wikimedia.org/wiki/Not_my_wiki | m:Not my wiki]] syndrome. This part of the problem should be discussed on wiki, probably the talk of the project.
+
+--------------------------
+**URL**: https://www.mediawiki.org/wiki/Project:PD_help
+**See Also**:
+{T19557}
+{T14306}
+{T46286}",1357145040,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_description,resolved
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I am afraid the lack of a doc in ##mw:## is the major problem here.
+
+Code fragments are distributed over many PHP units, and not really accessible to Wiki maintainers.",1516972788,PHID-USER-3imz37uve2wfuuub5eq6,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","You can still use MediaWiki:Whatlinkshere-helppage to override the default help link on Special:WhatLinksHere (and similar for all other special pages). You can also use such messages for override/add help links for namespaces (e.g. MediaWiki:Namespace-0-helppage) and page actions (e.g. MediaWiki:History-helppage).
+
+I don't know if this is properly documented anywhere, I just looked up how it works in source code.
+
+The default value is unfortunately not shown on these pages, due to the way we use these messages. Perhaps this could be changed to make these messages behave more normally, but as a consequence, users with non-default interface language would not see the local override (currently they do).
+
+Almost all of the built-in help links go to MediaWiki.org. There are only three exceptions: the help links for history action, Special:Import and Special:RecentChanges all go to MetaWiki. Presumably the documentation pages for these on MediaWiki.org are inferior.",1516912596,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Tried to figure out why some special page has a link to a local help page, and some has help pages at Meta and some at Mediawiki, but the previous -helppage system messages does not make sense anymore? Where is the doc for this?
+
+A local help page for WhatLinksHere has no -helppage link, so tried to move the help page to check if there was some checks on page existence, but no change, the local page is still in use somehow.",1516536097,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Imho it is understandable, when there is a link to a help page for an action or feature that a specific wiki does not offer, or at least not to the general viewer, that they want the help link not shown. Thus we should possibly make help pages very modular and independent of one another and avoid cross-linking them for the things that are based on different user rights that can be assigned individually to users or groups. Also, help links should only appear on pages where the individual feature is available.
+
+I do not know whether that is good and sufficient. At least, it contradicts the idea of offering the user a good and comprehensive Overview.
+
+Last not least, we can have wikis copy the common help pages wholesale or individually as need be, and use their local copies which they can edit to their needs.",1435734085,PHID-USER-pkzunphfdvlecngun3iz,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1411185, @Nikerabbit wrote:
+> It seems a bit blanket statement to say all of those help link are unhelpful. I would argue they are more helpful than harmful and thus there is no need to be able do disable them altogether.
+
+Maybe, maybe not. That's a third party wiki view. I can see it both ways; especially for a wiki that's not open to the public for editing, but is for public viewing. YMMV. Literally just passing on what I was told.",1435610712,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",It seems a bit blanket statement to say all of those help link are unhelpful. I would argue they are more helpful than harmful and thus there is no need to be able do disable them altogether.,1435605086,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I've just had a third-party wiki wondering what the point of this is, and as such, how to disable it
+
+```
+[15:31:40] <AA-Andrew> I can't really see how it's helpful for it to Link to a media wiki help page though 
+```
+
+Of course, hiding it with CSS isn't really disabling it, you're still loading the various assets.
+
+Should there be some sort of config flag for it? I'm not sure...",1435588663,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Ok, we can call this done for now. We should now go look for extension help pages on mediawiki.org and start adding links from their special pages.",1433346304,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","* https://gerrit.wikimedia.org/r/194418 (branch master): #mw1.26, #mw1.26wmf9
+",1433203246,PHID-USER-n4kveqwjjlpsb6ydn73h,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194418 merged by jenkins-bot:
+Add help link for 8 more special pages
+
+[[https://gerrit.wikimedia.org/r/194418]]",1433202431,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 211100 merged by jenkins-bot:
+Allow to customise addHelpLink() target via system message
+
+[[https://gerrit.wikimedia.org/r/211100]]",1431721124,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Once 8082c5f4f0a6c44bca1797470723089bc1d1ff03 is merged, this can be closed. Adding new help pages and links will then be an ongoing process as part of [[Project:PD Help]], as well as an easy matter of customisation by local wikis where needed.",1431687767,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 211100 had a related patch set uploaded (by Nemo bis):
+Allow to customise addHelpLink() target via system message
+
+[[https://gerrit.wikimedia.org/r/211100]]
+",1431686968,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 208378 merged by jenkins-bot:
+Allow to customise addHelpLink() target via system message
+
+[[https://gerrit.wikimedia.org/r/208378]]",1431686573,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 208378 had a related patch set uploaded (by Nemo bis):
+Allow to customise addHelpLink() target via system message
+
+[[https://gerrit.wikimedia.org/r/208378]]
+",1430566779,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1231734, @Multichill wrote:
+> Already disabled on dewp (https://de.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.css&diff=140838650&oldid=140486784). 
+
+And i am inclined to switch this of on commons... It is not helpful. It is not linking to the commons policy's, but to some MW page.
+
+",1430042303,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Just had a look at http://git.wikimedia.org/blob/mediawiki%2Fcore.git/0a33db75cb2afd0879512b7a3cc2ec5b63d9ae5e/includes%2FOutputPage.php#L1408 . Hardcoded url? No message? Are you serious?
+
+Already disabled on dewp (https://de.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.css&diff=140838650&oldid=140486784). 
+
+Including some help is a good idea, but the implementation should be improved so that the url is not hardcoded.",1429810113,PHID-USER-cw4amt4ewxdze5qcjdca,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1139342, @Nemo_bis wrote:
+>>>! In T45591#1139318, @matmarex wrote:
+>> Outstanding patches:
+>> * https://gerrit.wikimedia.org/r/#/c/194418/ ""[WIP] Add link to Meta-Wiki help pages from several special pages""
+> 
+> This is the one which needs most discussion/help.
+
+The pages in question are:
+* https://meta.wikimedia.org/wiki/Help:User_contributions
+* https://meta.wikimedia.org/wiki/Help:Export
+* https://meta.wikimedia.org/wiki/Help:Import
+* https://meta.wikimedia.org/wiki/Help:Linksearch
+* https://meta.wikimedia.org/wiki/Special:MyLanguage/Help:Recent_changes
+* https://meta.wikimedia.org/wiki/Help:Related_changes
+* https://meta.wikimedia.org/wiki/Help:Watching_pages
+* https://meta.wikimedia.org/wiki/Help:What_links_here",1429700039,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",https://commons.wikimedia.org/wiki/Commons:Village_pump#Help_topicons_linking_to_external_help_pages_soon_displayed_everywhere.3F,1429699178,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",Thanks Legoktm! If there is interest in a backport I can work on https://gerrit.wikimedia.org/r/#/c/194418/ this week.,1428562052,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 202968 merged by jenkins-bot:
+Add help link to three rather important pages
+
+[[https://gerrit.wikimedia.org/r/202968]]",1428541016,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 202968 had a related patch set uploaded (by Legoktm):
+Add help link to three rather important pages
+
+[[https://gerrit.wikimedia.org/r/202968]]
+",1428540221,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194414 merged by jenkins-bot:
+Add help link to three rather important pages
+
+[[https://gerrit.wikimedia.org/r/194414]]",1428540082,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1159175, @PerfektesChaos wrote:
+> Local confguration needs more emphasis.
+> * At least a system message should be taken into account by the implementation.
+
+This is valid point which can have it's own task.
+
+> * Icons might be cultural dependant (CJK, arabic, hebrew) and should be configurable per system message – a greek question mark is a semicolon.
+
+This can also be a separate task. We already do localised images in couple of places. I do disagree though that it needs to be configurable per system message.
+
+> Rather than maintaining system messages for each page by each project, a wikifarm with a wikibase could make use of that knowledge. (Okay, WMF might be the only one, but is among the top ten websites)
+
+This can already be achieved with the approach WikimediaMessages is using if we implement overrides with system messages.
+
+> I would like to see in CommonSettings.php something like
+
+Your proposal sounds very complicated, we already have standard way to handle these as explained above.
+
+> I wonder whether the entire helppage link business should stay in core or should be turned into an extension.
+
+It was just moved to core so that each extension does not implement a different way to do it. Definitely not to be moved to an extension.
+",1427541261,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","This is an interesting feature for small WMF wikis and external sites, but would confuse users on wikis with well equipped user guidance (e.g. English or German Wikipedia).
+* Most confusing are two offers, which might happen in German Wikipedia right now.
+* Local pages often provide local policies (deletion!) and specific links to related project pages which cannot be achieved with a world wide non-WMF general explanation.
+* https://www.wikidata.org/wiki/Q395887 shows present local support just for one issue. I count 60 existing local pages. (The 61st would be: mw:Help:Moving_a_page)
+
+Local confguration needs more emphasis.
+* At least a system message should be taken into account by the implementation.
+* Icons might be cultural dependant (CJK, arabic, hebrew) and should be configurable per system message – a greek question mark is a semicolon.
+
+Rather than maintaining system messages for each page by each project, a wikifarm with a wikibase could make use of that knowledge. (Okay, WMF might be the only one, but is among the top ten websites)
+
+I would like to see in CommonSettings.php something like
+  $wgHelpPages = array()
+That may be used explicitly to hard-code page links by any other site.
+
+However, one entry could look like
+  $wgHelpPages['special-movepage']['item'] = 395887;
+
+For performance reasons evaluation of the wikibase item is probably not desirable each time a special page is requested by readers.
+* Every 24h or once a week that array might be populated and refreshed like:
+```
+  lang=php
+  $wgHelpPages['special-movepage']['pages'] = array(
+            'alswiki' => 'Hilfe:Artikel verschieben',
+            'dewiki' => 'Hilfe:Seite verschieben',
+            'enwiki' => 'Wikipedia:Moving a page',
+            ...
+```
+* Time scheduling and triggering the update might be controlled by something like
+```
+  $wgHelpPages['UpdateInterval'] = 24;
+```
+* The same entries might be provided manually by external sites which happen to have their own guidance, but no wikibase and no update service.
+I wonder whether the entire helppage link business should stay in core or should be turned into an extension.
+* A (help/any) page mapping and linking mechanism might be used in many fields, not only with special pages.
+* Various configurations done with system message today might migrate towards wikibase in the future.
+* The MW TemplateData gadget e.g. could be equipped by https://www.wikidata.org/wiki/Q14505594 rather than [[MediaWiki:templatedata-helplink-target]].
+",1427533210,PHID-USER-3imz37uve2wfuuub5eq6,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1139318, @matmarex wrote:
+> Outstanding patches:
+> * https://gerrit.wikimedia.org/r/#/c/194418/ ""[WIP] Add link to Meta-Wiki help pages from several special pages""
+
+This is the one which needs most discussion/help. MediaWiki help pages can't lack coverage of RecentChanges and Watchlist... either they are rewritten on MediaWiki.org or we should change the rules to adopt/incorporate Meta-Wiki docs.",1427048506,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Outstanding patches:
+* https://gerrit.wikimedia.org/r/#/c/194418/ ""[WIP] Add link to Meta-Wiki help pages from several special pages""
+* https://gerrit.wikimedia.org/r/#/c/194414/ ""Add help link to three rather important pages""",1427047744,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1129825, @Spage wrote:
+> FWIW the icon is reachable, https://bits.wikimedia.org/static-1.25wmf21/resources/lib/oojs-ui/themes/mediawiki/images/icons/help.svg, so `url(../../lib/oojs-ui/themes/mediawiki/images/icons/help.svg)` works. I guess there's no cleaner path to library resources.
+
+True, but we were never doing that in the past (I think we even have duplicate copies of some files used in mediawiki/core, in different directories). We never had `url(…)` paths that refer to parent directory, and I think we should keep it this way, easier to figure out what depends on what.
+
+
+>> as the work on making the icons available has stalled a bit.
+> ?  They're all available if you use OOjs UI ([[ https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/#icons-mediawiki-vector-ltr | cool demo ]]). If we're making them available to non-OOjs UI code I look forward to documenting how-to.
+
+Yes. From T92551: ""Map to .mw-icon-<whatever> classes in addition to .oo-ui-icon-<whatever>"".
+
+>>! In T45591#1134815, @Nemo_bis wrote:
+> * Personally I prefer a more ""standard"" (i.e. common) blue, but it doesn't matter.
+> * VE is not ""standard"", both are icons taken from extensions and [[https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/410|made by WMF]].
+
+OOjs UI's icons are supposed to become ""MediaWiki UI"" icons, and thus be pronounced //the// standard ones. There are bumps along the way because the OOjs UI team (subset of WMF Editing) and the MediaWiki UI team (subset of WMF Design) have been disagreeing about which icons should be a part of this set, and how they should be drawn. You can see the current status at https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/#icons-mediawiki-vector-ltr – this has both the old OOjs UI icons (known from VisualEditor) and the new MediaWiki UI icons (known from Flow), and it is quite obvious that these are separate sets. (The 'help' icons comes from the old set, since for some reason it was not considered for including in the new one.) The current status is that Trevor is ~~beating some sens~~working with the designers to iron it out.",1427025201,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 197667 merged by jenkins-bot:
+mediawiki.helplink: Use a SVG PNG icon
+
+[[https://gerrit.wikimedia.org/r/197667]]",1426960241,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","One small question on https://gerrit.wikimedia.org/r/#/c/197667/2
+
+FWIW, aside trivia:
+* There's also a SVG version of the current help.png, but it's not a native one (014b5632fcc6a4200d519cf7f86e94c09639af8f).
+* Personally I prefer a more ""standard"" (i.e. common) blue, but it doesn't matter.
+* VE is not ""standard"", both are icons taken from extensions and [[https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/410|made by WMF]].",1426843326,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","One small question on https://gerrit.wikimedia.org/r/#/c/197667/2
+
+FWIW, aside trivia:
+* There's also a SVG version of the current help.png, but it's not a native one.
+* Personally I prefer a more ""standard"" (i.e. common) blue, but it doesn't matter.
+* VE is not ""standard"", both are icons taken from extensions and [[https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/410|made by WMF]].",1426843280,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1104151, @matmarex wrote:
+> Indeed, it seems that a ""Help"" icon was not considered for the new icon set.
+That's {T90414}
+
+> VisualEditor / OOjs UI has a icon for this, though: {F72837,size=full,layout=inline}. If you need it now, the file will have to be just copied into mediawiki/core,
+
+FWIW the icon is reachable, https://bits.wikimedia.org/static-1.25wmf21/resources/lib/oojs-ui/themes/mediawiki/images/icons/help.svg, so `url(../../lib/oojs-ui/themes/mediawiki/images/icons/help.svg)` works. I guess there's no cleaner path to library resources.
+
+> as the work on making the icons available has stalled a bit.
+?  They're all available if you use OOjs UI ([[ https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/#icons-mediawiki-vector-ltr | cool demo ]]). If we're making them available to non-OOjs UI code I look forward to documenting how-to.",1426705079,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 197667 had a related patch set uploaded (by Bartosz Dziewoński):
+mediawiki.helplink: Use standard SVG PNG icon
+
+[[https://gerrit.wikimedia.org/r/197667]]
+",1426699777,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194411 merged by jenkins-bot:
+Add help link to three other ""minor"" special pages
+
+[[https://gerrit.wikimedia.org/r/194411]]",1426689800,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1103929, @matmarex wrote:
+>>>! In T45591#1102455, @Krinkle wrote:
+>> I imagine if this is not changed it will need to be reverted and further worked upon for the next deployment window.
+> 
+> That strikes me as somewhat of an overreaction.
+
+It needs improvement before deployment. It wasn't my feature to implement and would not have been merged as-is in that case. As such, a revert is just returning status quo and enforcing quality criteria.",1425998891,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Indeed, it seems that a ""Help"" icon was not considered for the new icon set.
+
+VisualEditor / OOjs UI has a icon for this, though: {F72837,size=full,layout=inline}
+
+https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/themes/mediawiki/images/icons/help.svg
+https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/themes/mediawiki/images/icons/help.png
+
+Presumably that could be used. If you need it now, the file will have to be just copied into mediawiki/core, as the work on making the icons available has stalled a bit. (It is MIT-licensed, like the rest of OOjs UI.)",1425991017,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Are you talking about the blue ""?"" for 'help'?
+
+For what is worth, WikiFont has an icon from @violetto called [[ https://commons.wikimedia.org/wiki/File:Sun_help.svg | Sun help ]]. I couldn't find any incon with ""?"" in the collection.
+
+Needless to say, in Commons there are many SVGs of question mark signs in a blue circle, but... See https://commons.wikimedia.org/wiki/File:Blue_question_mark_icon.svg & friends.",1425990691,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I agree the icon needs to be improved. Do you have suggestions for a SVG-ready icon to use?
+
+That's the icon closest to a ""standard"" that we currently have in the codebase for this purpose: it's used in a MediaWiki extension already, for several special pages. We must improve it before we extend its usage to more visible places, of course.",1425988211,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1102455, @Krinkle wrote:
+> I imagine if this is not changed it will need to be reverted and further worked upon for the next deployment window.
+
+That strikes me as somewhat of an overreaction. If the icon irks you, then it's a one-line change to remove it. It would be almost as easy to replace it with a different one, too.",1425983414,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1088866, @gerritbot wrote:
+> Change 157497 merged by jenkins-bot:
+> Add top help link to MediaWiki.org in several pages via indicator
+> 
+> [[https://gerrit.wikimedia.org/r/157497]]
+
+This uses a non-standard icon that doesn't match the any skin and did not go through Design. It also does not have an SVG or High-resolution version available. Thus regressing from our state of having HiDPI-friendly pages by default.
+
+The icon would be okay for a local gadget, but not MediaWiki core.
+
+I don't know further context, but I imagine if this is not changed it will need to be reverted and further worked upon for the next deployment window.",1425947370,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 195045 merged by jenkins-bot:
+Don't require JavaScript for addHelpLink styles
+
+[[https://gerrit.wikimedia.org/r/195045]]",1425752905,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 195045 had a related patch set uploaded (by Nemo bis):
+Don't require JavaScript for addHelpLink styles
+
+[[https://gerrit.wikimedia.org/r/195045]]
+",1425749895,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Switching order needs to be checked for each call in core.
+
+Hiding with css would work, but not tested yet.",1425673270,PHID-USER-qaoxfiqu6bxhd5ehlwhc,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Or we can switch the order. Did you try CSS, though?",1425670025,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","on de.wikipedia.beta.wmflabs.org we have changed the id, but it does not override it, see http://de.wikipedia.beta.wmflabs.org/wiki/Spezial:Verschieben/MediaWiki:Movepage-summary for the place where the wrong help link is shown and http://de.wikipedia.beta.wmflabs.org/wiki/MediaWiki:Movepage-summary for the message where the indicator is used.
+
+This seems to be happen because OutputPage::setHelpLink is called later than SpecialPage::outputHeader and than override the indicator (""In case of duplicate keys, existing values are overwritten.""). OutputPage::setIndicators needs a explicit not-overwrite-option which than can be used from OutputPage::addHelpLink.",1425668089,PHID-USER-qaoxfiqu6bxhd5ehlwhc,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","> What about wikis already have such a help link in the UI like dewiki (see https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/MediaWiki:Specialpage-helplink&limit=500&hidelinks=1 for all usages)
+
+They should switch to the usage of indicators, using the same ID. This *should* suppress the default link.
+
+> What about the local help pages like linked from https://www.wikidata.org/wiki/Q395887?
+> Why hard linking to mw.org? There should be a way to allow the local community to override the target of the help page.
+
+Local help pages are available on very few languages, but sure, customisation should be possible for wikis which care about it. Are the provided CSS class+id and the indicator system insufficient for customisation?",1425667651,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","> What about wikis already have such a help link in the UI like dewiki (see https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/MediaWiki:Specialpage-helplink&limit=500&hidelinks=1 for all usages)
+
+They should switch to the usage of indicators, using the same ID. This *should* suppress the default link.
+
+> What about the local help pages like linked from https://www.wikidata.org/wiki/Q395887?
+> Why hard linking to mw.org? There should be a way to allow the local community to override the target of the help page.
+
+Local help pages are available on very few languages, but sure, customisation should be possible for wikis which care about it. Are the provided CSS classes and the indicator system insufficient for customisation?",1425667627,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","> What about wikis already have such a help link in the UI like dewiki (see https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/MediaWiki:Specialpage-helplink&limit=500&hidelinks=1 for all usages)
+
+They should switch to the usage of indicators, using the same ID. This *should* suppress the default link.
+
+> What about the local help pages like linked from https://www.wikidata.org/wiki/Q395887?
+> Why hard linking to mw.org? There should be a way to allow the local community to override the target of the help page.
+
+Local help pages are available on very few languages, but sure, customisation should be possible for wikis which cared about it. Are the provided CSS classes and the indicator system insufficient for customisation?",1425667449,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I told you there were many. ;-) Even more ambitious, various actions or special cases thereof:
+* https://meta.wikimedia.org/wiki/Help:Diff
+* https://meta.wikimedia.org/wiki/Help:Edit_conflict
+* https://meta.wikimedia.org/wiki/Help:Image_page
+* https://meta.wikimedia.org/wiki/Help:Preview
+* https://meta.wikimedia.org/wiki/Help:Redirect
+* https://meta.wikimedia.org/wiki/Help:View_source
+
+Not sure how to split this conversation/epic. As long as it's just me talking with myself, one report and 3-4 patches probably suffice. ;-) But fixing or rewriting 15 help pages on something like half of a wiki's daily operation is unlikely to be one man's work, while being something we must to at some point.",1425514666,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194418 had a related patch set uploaded (by Nemo bis):
+Add link to Meta-Wiki help pages from several special pages
+
+[[https://gerrit.wikimedia.org/r/194418]]
+",1425513524,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194414 had a related patch set uploaded (by Nemo bis):
+Add help link to three rather important pages
+
+[[https://gerrit.wikimedia.org/r/194414]]
+",1425511854,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194411 had a related patch set uploaded (by Nemo bis):
+Add help link to three other ""minor"" special pages
+
+[[https://gerrit.wikimedia.org/r/194411]]
+",1425510977,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I'm very happy. :) As for closure let's see: I'm considering many more possible targets for core, I'll send more patches.",1425501388,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Fixed by Nemo for a number of core special pages, which will now have a ""Help"" link in the page indicator area (https://www.mediawiki.org/wiki/Help:Page_status_indicators). The newly added `OutputPage::addHelpLink()` method can be used by extensions to provide identical functionality for their own special pages.",1425486074,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157497 merged by jenkins-bot:
+Add top help link to MediaWiki.org in several pages via indicator
+
+[[https://gerrit.wikimedia.org/r/157497]]",1425485755,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157497 had a related patch set uploaded (by Nemo bis):
+Add top help link to MediaWiki.org in several pages via indicator
+
+[[https://gerrit.wikimedia.org/r/157497]]
+
+#patch-for-review",1424441232,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157496 abandoned by Nemo bis:
+Function to add a top (right) icon link to help page
+
+Reason:
+Superseded by indicators
+
+[[https://gerrit.wikimedia.org/r/157496]]",1417711881,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","(In reply to Bartosz Dziewoński from comment #10)
+> I did that as a note-to-self to implement this later. But okay.
+
+That's appreciated, and it would be useful if bug 23796 had preserved its original bug summary (with its current summary split to some other bug), but as is it was very confusing.",1411574653,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",I did that as a note-to-self to implement this later. But okay.,1411574311,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","(In reply to Bartosz Dziewoński from comment #8)
+> The implementation proposed by Nemo looks like it would benefit from having
+> bug 23796 solved first, so I'm marking this as such.
+
+With its current summary I see no relation whatsoever.",1411573973,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","The implementation proposed by Nemo looks like it would benefit from having bug 23796 solved first, so I'm marking this as such.",1411573690,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157497 had a related patch set uploaded by Nemo bis:
+Add top help link to MediaWiki.org in several pages
+
+https://gerrit.wikimedia.org/r/157497",1409482959,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157496 had a related patch set uploaded by Nemo bis:
+Function to add a top (right) icon link to help page
+
+https://gerrit.wikimedia.org/r/157496",1409482951,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","[[mw:Category:Help]] was made almost completely translatable (and usually revamped a bit in the process).
+
+I count the following places which have a documentation page and don't link it: Special:Block, Special:MergeHistory, Special:MovePage, Special:NewPages, Special:NewImages, Special:Preferences, Special:Search, action=protect, Special:RecentChanges, action=delete, Special:AllMessages, Special:Undelete, Special:Watchlist; and in extensions, Special:MassMessage, Special:TemplateSandbox, Special:AbuseFilter.
+
+Where to start?",1409433404,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","(In reply to comment #3)
+> Speaking of implementation method, the interwiki prefix mediawikiwiki can be
+> used when necessary: ""new"" wikis have it by default, where ""new"" means after 
+> 2007-03-29 (bug 9440 / r20825 / 98333f458046102ee140f4be86fe4d2c6facae2f ).
+
+To clarify the ""when necessary"": personally, for now I'm following the path of last resistance, i.e. I use wikilink where there is already a wikilink and external where there is already an external link.
+The separate bug 54835 addresses/proposes the standardisation.",1380650218,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Speaking of implementation method, the interwiki prefix mediawikiwiki can be used when necessary: ""new"" wikis have it by default, where ""new"" means after  2007-03-29 (bug 9440 / r20825 / 98333f458046102ee140f4be86fe4d2c6facae2f ).",1378569913,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","(In reply to comment #1)
+> I for one would prefer an ""if the local page does not exist, then
+> transparently
+> deliver the central page from www.mediawiki.org"" approach for help pages
+
+Sure, that's a possibility too. It's a choice of implementation method, let's leave it to code review. :)
+(Target pages would probably be customisable in system messages anyway, so the result would be the same: wikis could have their own pages if they really wanted.)",1366030055,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I for one would prefer an ""if the local page does not exist, then transparently deliver the central page from www.mediawiki.org"" approach for help pages, mainly resembling the way, pictures are handled and included from Commons if needed.
+
+Also, when user on a wiki are about to create a new help page following a red link to the help: namespace, they should most preferrably be stirred towards the central www.mediawiki.org help page creation in their language.",1366029168,PHID-USER-pkzunphfdvlecngun3iz,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Parser misinterprets en.wikipedia Infobox (inline ""style"" attribute ends up in text nodes)","Screenshot of bug and edit screens
+
+Native parser rendering:
+the Netherlands
+
+Parsoid/VisualEditor rendering:
+style=""font-size: larger; font-weight: bold"" | the Netherlands
+
+[[Flag of the Kingdom of the Netherlands]]:
+{{Infobox flag
+| Name = the Netherlands
+...
+
+[[Template:Infobox flag]]:
+> {| class=""infobox"" style=""width: 22em; font-size:88%; text-align:left; line-height: 1.5em""
+|+ style=""font-size: larger; font-weight: bold"" | <br>{{{Name|{{PAGENAME}}}}}
+|-
+...
+
+
+See attachment for rendering.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10351}",1357121460,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-iwk4mxubemdjw56l5wqu,task_description,resolved
+"Parser misinterprets en.wikipedia Infobox (inline ""style"" attribute ends up in text nodes)",Fixed by https://gerrit.wikimedia.org/r/#/c/44170/.,1358293142,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-iwk4mxubemdjw56l5wqu,task_subcomment,NA
+VisualEditor: Mouse leaving a phantom and also the .ve-surface DIV area causes phantom to remain,"Hovering over an uneditable element in VisualEditor makes the element be covered by green stripes until the mouse is moved away, but when the cursor moves directly to the sidebar or the right margin, the stripes stay there until some part of the .ve-surface is hovered over.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1356609300,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-ojc6pzmsefmlfjvvupqg,task_description,resolved
+VisualEditor: Mouse leaving a phantom and also the .ve-surface DIV area causes phantom to remain,"**orbit** wrote:
+
+Fixed here: https://gerrit.wikimedia.org/r/#/c/50309/",1361487636,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ojc6pzmsefmlfjvvupqg,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"From user report (but I've had this myself):
+
+| HotCat is a popular gadget and any conflict with it should be avoided. For
+| example, use VisualEditor on [[User:This, that and the other/sandbox/Schfoof]]
+| with HotCat enabled. The HotCat bar appears in the wrong place. (It probably
+| shouldn't appear at all.)
+|
+| …
+|
+| The conflict now appears to be fixed... very strange.
+
+Given that it appears and also doesn't appear between refreshes - i.e., on the same page with the same version of the VE and HC code bases in the same accounts in the same browsers - I'm assuming it's some sort of race-condition, but I'm not sure.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1356129540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pxuflqdxigvalopfqw3z,task_description,declined
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"I can't reproduce this issue... If anyone still sees this, please reopen.",1414009552,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"Created attachment 14685
+HotCat showing up in the content editable surface
+
+(from bug 55759 attachment 13500 by Chris McMahon)
+
+**Attached**: {F9984}",1393411345,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"(In reply to comment #4)
+> Created attachment 13512 [details]
+> VE iframe has gadget code before VE is invoked
+I don't think that's related at all. Gadget CSS is expected in the iframe. It should be in the <head> instead of the <body> but that's a separate issue (bug 56630).
+
+//attachment invisible_iframe_contents.png ignored as obsolete//",1383697299,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"Created attachment 13512
+VE iframe has gadget code before VE is invoked
+
+//attachment invisible_iframe_contents.png ignored as obsolete//",1381945871,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,*** Bug 55759 has been marked as a duplicate of this bug. ***,1381877657,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"(In reply to comment #1)
+> Is this related?
+> 
+> ""We seem to have lost the plus and minus options of Hotcat that were one of
+> the closest to WYSIWYG features of this site. Please can they be
+> incorporated into visual editor. ϢereSpielChequers 13:46, 4 July 2013 (UTC)""
+
+That's unrelated to VisualEditor; enwiki's community switched off HotCat as a default gadget, so people who want to keep using it will need to manually switch it back on.",1372947996,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"Is this related?
+
+""We seem to have lost the plus and minus options of Hotcat that were one of the closest to WYSIWYG features of this site. Please can they be incorporated into visual editor. ϢereSpielChequers 13:46, 4 July 2013 (UTC)""",1372946751,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Add a (small) left margin to the CE so that users can select whole lines at once,"From a user suggestion:
+
+| Normally word processors and text editors have a left margin, allowing
+| whole lines to be selected. There would normally be a small gap of a few
+| pixels between the left column of text and the left margin, allowing a
+| ""margin of error"" for regular text selection. To the left of this gap,
+| any clicks select entire lines, and any drags up or down select many
+| lines at once. 
+|
+| I don't know if there is a need for the complete left margin
+| functionality in VisualEditor, but certainly, the editing area shouldn't
+| stop at the exact edge of the letters. Perhaps the padding on the VE
+| container needs to be increased with a compensating decrease in the
+| margin - or maybe that's totally wrong, but you get the idea.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1356128220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3d7wihxirj5lu7swsg43,task_description,declined
+VisualEditor: Add a (small) left margin to the CE so that users can select whole lines at once,"After discussion with the team, we feel that this doesn't make sense because this is mostly a feature that makes sense in line-based editors (generally, for code), and VE is not one of these.",1369426246,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3d7wihxirj5lu7swsg43,task_subcomment,NA
+VisualEditor: Add a (small) left margin to the CE so that users can select whole lines at once,"For the first part, some IDEs do this (e.g. Sublime), but LO, Google Docs & gedit don't. The downside is it reduces the target zone for placing the cursor at the start of a line.
+
+For the second part, we already have left padding into which you can click to position the cursor at the start of the line.",1369228231,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3d7wihxirj5lu7swsg43,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,"In https://en.wikipedia.org/w/index.php?title=Lynn_Hill&oldid=528045441 (and other versions), go into VE, go to the bottom, delete the list item (and so the list) from the External links section.
+
+ve.instances[0].documentModel.data confirms that the model has this removed - ""/heading"" object followed by the alienated table from the ""{{Authority control}}"" template - but on diff Parsoid thinks that there is no change in this area. Is this is a Parsoid, or is change marking broken (or both)?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355510820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_description,resolved
+VisualEditor: Deleting content between a heading and an alien fails?,"A few more selser fixes later this should now be fixed. Repeating the test case above certainly suggests it works, so please reopen if there still are issues.",1359143154,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,(Needs verification with VE),1357343579,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,"Likely fixed by the DOM diffing functionality that landed in https://gerrit.wikimedia.org/r/#/c/41816/. Barring bugs, we now no longer depend on change markers for selective serialization to work.",1357343521,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,"I believe this ties in directly to what Gabriel is doing, so I'll add him and we can have a big bugzilla CCing party.",1355950575,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,"This is probably a selser (Parsoid) issue. There is no change marking for removals, selser detects these based on DSR discontinuities.
+
+Provisionally CCing Mark, once I get time to investigate this properly and figure out what's going on, I'll move/reassign this bug as appropriate.",1355950118,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit imagemaps,"<imagemap>....</imagemap> is unparsed but shown as plain wikitext:
+https://en.wikipedia.org/wiki/User:Raymond/imagemap
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/imagemap",1355487780,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-7akqsunetgzvscos7y7g,task_description,open
+Create a VisualEditor plugin tool to add/edit imagemaps,"> <imagemap>....</imagemap> is unparsed but shown as plain wikitext
+
+Apparently at this point it is shown as an uneditable image.
+
+An imagemap editor seems almost the same use case as an [[ https://commons.wikimedia.org/wiki/Help:Gadget-ImageAnnotator | ImageAnnotator ]] annotation editor.",1422606911,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-7akqsunetgzvscos7y7g,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"Support <syntaxhighlight> tag too. It is a synonym to <source> which works already
+
+https://en.wikipedia.org/wiki/User:Raymond/source
+
+See https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/SyntaxHighlight_GeSHi.git;a=blob;f=SyntaxHighlight_GeSHi.php#l67 for the definiton of the parser hooks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/source",1355486220,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-q2kd7nc4teibu2d6yujb,task_description,resolved
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"Change 214078 merged by jenkins-bot:
+Add VisualEditor support
+
+[[https://gerrit.wikimedia.org/r/214078]]",1435183387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"Change 214078 had a related patch set uploaded (by Jforrester):
+Add VE support for syntax highlighting
+
+[[https://gerrit.wikimedia.org/r/214078]]
+",1432909766,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"Change 114529 had a related patch set uploaded by Jforrester:
+[WIP] Add VisualEditor support
+
+https://gerrit.wikimedia.org/r/114529",1404758239,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,Re-opening as this is now unmerged.,1404758207,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"This is now complete and merged, as gerrit 68615, and will go out (as an experimental option) to MediaWiki.org tomorrow. Congratulations, Tongbo!",1380739351,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Parsoid: Second column heading missing of table with template-generated header,"Screenshot showing the regular view, visualeditor view and wikitext
+
+Steps to reproduce problem:
+* Open VisualEditor on https://en.wikipedia.org/wiki/Buri_Ram_Airport
+
+Expected result:
+Table has header on both columns.
+
+Actual result:
+Header of second column is missing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9595}",1355443620,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-woqw5jwyjb5eshocsjdw,task_description,resolved
+Parsoid: Second column heading missing of table with template-generated header,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372933991,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-woqw5jwyjb5eshocsjdw,task_subcomment,NA
+Parsoid: Second column heading missing of table with template-generated header,Patch committed for review in https://gerrit.wikimedia.org/r/46465.,1359416789,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-woqw5jwyjb5eshocsjdw,task_subcomment,NA
+Parsoid: Second column heading missing of table with template-generated header,"Appears to be a failed template expansion, so probably a Parsoid bug - Gabriel, thoughts?",1357598990,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-woqw5jwyjb5eshocsjdw,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,"Try editing the page [[:en:Buri_Ram_Airport]] with VisualEditor. Mouse over the infobox. There's an element that sticks above the alien marking, because it has a z-index attribute.
+
+I don't know how best to fix this, I assume it would be bad to simply set z-index=1000 and be on your way, but it's an inconsistent appearance and something to be fixed eventually.
+
+I suspect this may also be a good beginner bug, so if someone from the VE team can mark this as easy, then we can leave it for a newcomer.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.org/wiki/Buri_Ram_Airport",1355441880,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_description,resolved
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,Change-Id: I889074a659483ce3d48380be5f50f80abb573286,1355696389,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,"You guys have no concept of leaving a simple bug for new contributors? :)
+
+Not to worry, I'll go find more. Thanks Rob!",1355515857,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,Patch in https://gerrit.wikimedia.org/r/38669,1355446597,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,"The following CSS rule exists:
+
+> .ve-ce-alienBlockNode, .ve-ce-alienInlineNode,
+> .ve-ce-alienBlockNode *, .ve-ce-alienInlineNode * {
+>   position: relative !important;
+>   top: 0 !important;
+>   left: 0 !important;
+>   bottom: 0 !important;
+>   right: 0 !important;
+> }
+
+They have position relative, so the z-index within is relative and constraint within the alien.
+
+However that isn't the case. This is because the top node (alienBlockNode, not alienBlockNode *) needs z-index: 0; to complete this feature. It is the combination of z-index: 0; and position: relative; that makes it work.
+
+It was presumably forgotten because it needs to be on a separate rule (not inside the one above, since that would set z-index: 0; on all blocks, thus destroying the order of elements within the alien).",1355442376,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,"Sorry, setting web browser in case it matters.",1355441973,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Math is editable, but only as plain LaTeX like in the wikitext editor: https://en.wikipedia.org/wiki/User:Raymond/Math
+
+{F199473}
+Figure 1: Current non visual visual editor",1355386860,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-nspbk6goaacnxvuhl4ff,task_description,open
+Create a visual VisualEditor plugin tool to add/edit maths blocks,">>! In T45058#6101704, @BoldLuis wrote:
+> I suggest a way to implement Mediawiki links in Phabricator.  ~~~~
+
+**[offtopic]** @BoldLuis: Please use the Preview at the bottom, below the comment field, before submitting a comment. See T251657. Thanks :)
+
+Please also avoid unnecessary full quotes of previous comments when not needed.",1588406096,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,">>! In T45058#6101704, @BoldLuis wrote:
+> I suggest a way to implement Mediawiki links in Phabricator.  ~~~~
+
+**[offtopic]** @BoldLuis: Please use the Preview at the bottom, below the comment field, before submitting a comment. See T251657. Thanks :)",1588406072,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Good!!!. 
+
+>>! In T45058#475499, @SalixAlba wrote:
+> Created attachment 13550
+> Screenshot of editing a math block
+> 
+> Some small tweaks are needed to the dialog box. Editing the last equation at https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+> there are a a few problems
+> 
+> 1) The dialog obscures the actual equation
+> 2) The dlalog is too small to see the whole source text of the equation
+> 
+> This could be solved the making the dialog, moveable and resizeable.
+> 
+> **Attached**: {F10189}
+
+",1588386108,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,">>! In T45058#475389, @Jdforrester-WMF wrote:
+> (In reply to comment #3)
+>> Are there any news on this?
+> 
+> Jiabao was accepted as a GSoC student and will be working on this with us. Updates are going to be added at [[mw:User:Jiabao wu/GSoC 2013 Project Work]].
+
+I suggest a way to implement Mediawiki links in Phabricator.  ~~~~",1588382922,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor.]
+
+
+  - I suggest Math Editor, a full visual math editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition. See:** 
+https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/ . Just some ideas ;-)",1588368331,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor.]
+
+
+  - I suggest Math Editor, a full visual math editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition. See:** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588368277,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor.]
+
+
+  - I suggest Math Editor, a full visual math editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588368213,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+
+  - I suggest Math Editor, a full visual math editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588368120,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+
+  - I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588368041,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http//en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+
+  - I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367857,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula_Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http//en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+
+  - I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367830,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula_Help:Displaying a formula Wikipedia Help:Displaying a formula]
+[http//en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a calculator. If you put / in the visual box in your keyboard, it would put the wikitext: \frac . It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367699,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying a formula Help:Displaying a formula]
+[http//en.wikipedia.org/wiki File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a calculator. If you put / in the visual box in your keyboard, it would put the wikitext: \frac . It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367619,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying a formula Help:Displaying a formula]
+[http//en.wikipedia.org/wiki File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a calculator. If you put / in the visual box in your keyboard, it would put the wikitext: \frac . It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or math handwriting recognition [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367587,PHID-USER-7j4dq3ggca7kka2g3siq,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,I added a screenshot so that the task becomes easier to understand,1437349341,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"I was already wondering... yes when you wonder...there might be a good reason for that;-)
+Thanks for the clarification. So you mean something like
+http://saskatoon.cs.rit.edu/min_instructions/",1437349029,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"No. By ""plain wikitext"" the filer means ""in LaTeX rather than visually"", hence the title of this task.",1437348608,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"I tested
+
+```
+Math is unparsed but shown as plain wikitext: https://en.wikipedia.org/wiki/User:Raymond/Math
+```
+and i could edit without issues. I could see a renderd formula when visiting this page
+https://en.wikipedia.org/wiki/User:Raymond/Math?veaction=edit
+Ok it had the png rendering and not the MathML rendering, but I think this is a seperate bug.",1437347647,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,">>! In T45058#932936, @matmarex wrote:
+> This has been fixed a looong time ago, or needs a better summary to explain what's missing.
+
+Happy?",1418933302,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"This has been fixed a looong time ago, or needs a better summary to explain what's missing.",1418920884,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"**physik** wrote:
+
+I'm happy to see the interest in the Math extension.
+It would be really great to get some code reviews. There are a lot of unmerged improvements that are already implemented that wait for a code review.
+https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/Math,n,z
+The fromula editor for math is one example. The code for Math 2.0 that was finished in beginning of October 2013 is still waiting for review and not moving forward at all. That's really a very sad situation. (Sorry for the spamming)",1393519044,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to PiRSquared17 from comment #28)
+> I'm not sure we need to reinvent the wheel.  Aren't there already libre JS
+> formula editors that can export to LaTeX?  I just found one from Google:
+> http://mathdox.org/formulaeditor/
+
+Who is talking about re-inventing the wheel?",1393518234,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,I'm not sure we need to reinvent the wheel.  Aren't there already libre JS formula editors that can export to LaTeX?  I just found one from Google: http://mathdox.org/formulaeditor/,1393518034,PHID-USER-omdcggvudfkuawipp23i,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to Richard Morris from comment #26)
+> I hope the LaTeX editor is not going to be short term. This is the preferred
+> input method for the mathematical community. By all means develop a GUI but
+> please make sure you can still use a LaTeX input method.
+
++1",1393517762,PHID-USER-omdcggvudfkuawipp23i,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,I hope the LaTeX editor is not going to be short term. This is the preferred input method for the mathematical community. By all means develop a GUI but please make sure you can still use a LaTeX input method.,1392761006,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,*** Bug 61498 has been marked as a duplicate of this bug. ***,1392741898,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to Andre Klapper from comment #21)
+> It's a bit unclear to me which further steps are required to get this ticket
+> closed (probably creating dependency tickets for the items in comment 19?).
+
+No, the issues in comment 19 only refer to the short-term LaTeX editor. This bug is asking for a fully-featured visual interactive editor for formulae – will merge bug 61498 back into this.",1392741889,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Bug 57437 is to ""Allow the VE dialog for math elements to be movable and resizable"", which is already a blocker for this ticket. This assigned to a google code-in student, Theopolisme, who I suspect is no longer working on that bug.
+
+I've create bug 61497 to cover up the jumbled up formula in comment 16.
+
+I think Jiabao original plan was to create a GUI I've added a bug for this as bug 61498.
+
+Dialog overlapping the equation might be resolved by bug 57437 or it could possibly resolved by changing the way it is initially displayed.",1392740544,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"**physik** wrote:
+
+From what I see
+https://gerrit.wikimedia.org/r/#/c/105647/ and
+https://gerrit.wikimedia.org/r/#/c/105648/
+need to be resolved before we can make progress on that.",1392739625,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Seems that Jiabao is not currently working on this ticket, hence resetting ASSIGNED status. 
+It's a bit unclear to me which further steps are required to get this ticket closed (probably creating dependency tickets for the items in comment 19?).",1392729667,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,OK I've created bug 57437 for the tweaks to the dialog and assigned it to Theopolisme. Hope that OK.,1385146178,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"There are different problems reported here, and we should have separate reports for each. Then we will tie each bug report to a Google Code-in task:
+
+* The dialog overlaps the equation: the solution might be a combination of setting a default position with less chances of overlapping and/or allowing the dialog to be moved to a different position?
+
+* The dialog is sometimes too small: the solution might be to make the dialog resizable?
+
+* #Comment 16 deserves an own bug report but, haven't tested this plugin myself, I can't describe the problem or propose solutions.
+
+Richard, would you like to create these reports?
+
+I'm going to pull http://www.google-melange.com/gci/task/view/google/gci2013/5861921152565248 in order to create 2 GCI tasks or more. Theopolisme, you can try to work on these issues now, or you can wait until the plan is more defined (and Jiabao is back, or we have found a co-mentor able to help you).",1385134282,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Just a bit of background: Theopolisme is a Google Code-in student working on a task related to #comment 15 that was created by Jiabao:
+
+http://www.google-melange.com/gci/task/view/google/gci2013/5861921152565248
+
+Jiabao has been silent in the past days. Your help is welcome while she comes back. Thank you!",1385084439,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"@Richard/others: Thinking about making the dialog draggable and resizable...
+
+The solution I initially think of is installing jquery.ui and then adding some parameters to OO.ui.Window that allow it to be made resizable and/or draggable. However, if I recall correctly one of the principles of OOJS was to be self-contained... so would this be wrong? Could someone else with a bit more firsthand experience chime in here?",1385074537,PHID-USER-wgpse4towjiaqbzotzgo,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Also editing the last equation at https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+
+if you actually make a change to the text of the equation the displayed equation becomes very jumbled. Any vertical positioning is lost, and text from different lines are overlaid on top of each other.
+
+This happens with Chrome on a Mac, I can't seem to edit equations at all with firefox or safari.",1382509541,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Created attachment 13550
+Screenshot of editing a math block
+
+Some small tweaks are needed to the dialog box. Editing the last equation at https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+there are a a few problems
+
+1) The dialog obscures the actual equation
+2) The dlalog is too small to see the whole source text of the equation
+
+This could be solved the making the dialog, moveable and resizeable.
+
+**Attached**: {F10189}",1382508786,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"If you have open tasks or bugs left, one possibility is to list them at https://www.mediawiki.org/wiki/Google_Code-In and volunteer yourself as mentor.
+
+We have heard from Google and free software projects participating in Code-in that students participating in this programs have done a great work finishing and polishing GSoC projects, many times mentores by the former GSoC student. The key is to be able to split the pending work in little tasks.
+
+More information in the wiki page. If you have questions you can ask there or you can contact me directly.",1382470549,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"GSoC ""soft pencils down"" date was yesterday and all coding must stop on 23 September. Has this project been completed?",1379434494,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Its important that it will be possible to enter the raw latex and that the text input area is large enough to enter a large formula. Editing the formula for atan2 at https://www.mediawiki.org/wiki/VisualEditor:TestMath now give a multi line box, but its still a bit small and wraps the formula. 
+
+It may be an idea to use a different size box for inline formula which tend to be short and display formula which tend to be larger. $ vrs $$ in latex syntax, I don't know how you would distinguish this in VE.
+
+The need for latex input was discussed at https://www.mediawiki.org/wiki/User_talk:Jiabao_wu and came up again at http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=570517247&oldid=570514963",1377691093,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,Possibly related: https://en.wikipedia.org/wiki/Wikipedia_talk:Flow#Mathematics_under_Flow,1376190076,PHID-USER-omdcggvudfkuawipp23i,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to comment #7)
+> @Richard this plugin won't be dependent on bug 36496 (MathJax as default).
+> Texvc-compatible syntax remains the internal/wikitext format. MathJax
+> provides
+> a live-preview within VE to enable visual editing. (Of course, a future
+> iteration might use MathJax to save MathML and SVG alongside the TeX.)
+
+Have removed the dependency.
+
+(In reply to comment #8)
+> Is this connect with http://www.mediawiki.org/wiki/VisualEditor:TestMath?
+
+Yes; that's the work being done by Jiabao Wu as part of Google Summer of Code. See https://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Project_Work for updates.",1373926378,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"@Richard I don't know which VE version is running there. I think I should point out that this is a GSoC project in the middle of development, not anywhere near production ready, frequently breaking etc.",1373924458,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,Is this connect with http://www.mediawiki.org/wiki/VisualEditor:TestMath? If so its a nice start but I'm having trouble editing a large formula for arctan2 at the bottom?,1373914340,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"@Richard this plugin won't be dependent on bug 36496 (MathJax as default). Texvc-compatible syntax remains the internal/wikitext format. MathJax provides a live-preview within VE to enable visual editing. (Of course, a future iteration might use MathJax to save MathML and SVG alongside the TeX.)",1373910001,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"**physik** wrote:
+
+I think a combination of MathML and MathJax would be optimal.
+See https://gerrit.wikimedia.org/r/#/c/69298/",1373790125,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Wondering how the rendering is going to happen? Is it going to use MathJax which is the only game in town at the moment? The default texvc render won't be up to the job as it need to recreate an image for every keystroke. MathML based renders have basically failed with poor browser support. 
+
+If you use MathJax deployment will be a problem unless bug 36496 is fixed.",1373785257,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to comment #3)
+> Are there any news on this?
+
+Jiabao was accepted as a GSoC student and will be working on this with us. Updates are going to be added at [[mw:User:Jiabao wu/GSoC 2013 Project Work]].",1370657625,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,Are there any news on this?,1370656180,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"**jiabao.foss** wrote:
+
+(In reply to comment #1)
+> This will require Parsoid to be finished and expose ParserHooks to get
+> alienated, and then a VE node handler to be written. The first bit is
+> relatively easy, but the second is a very significant undertaking, so
+> prioritising as ""lowest"".
+
+Hello James, I have designed and written my proposal for a plugin that will fix this bug. http://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Application
+
+I am not yet familiar with the VE architecture so I need some help understanding it and your comments. Is my design close to what it needed for a ""node handler"" for the maths elements in a wiki page. Also currently I have two modules named doc reader and doc writer. It would be helpful to know more about how these can interact with the document in visual editor.
+
+The design that I proposed of the User Interface for my plugin be similar to that of google docs. I am wondering if this is closer to what the community wants and needs for VisualEditor. Or if it would be better to stay closer to the existing way special characters are inserted in the traditional wikitext editor.
+
+Thanks,
+Jiabao",1367240312,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"This will require Parsoid to be finished and expose ParserHooks to get alienated, and then a VE node handler to be written. The first bit is relatively easy, but the second is a very significant undertaking, so prioritising as ""lowest"".",1355432140,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+VisualEditor: Review window behind article,"**Author:** `jnichols`
+
+**Description:**
+I can only see the very top few lines of the review-and-save window, the notices window, and the edit summary window. The rest of them seem to be behind the article window. I can scroll down the review window, looking at it three lines at a time in the little area between the top of the article and the tabs. The notices window and the edit summary windows don't scroll, which means I can't get down to the final ""save"" button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1355378580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-63cm7igyhb5qdw236lct,task_description,declined
+VisualEditor: Review window behind article,"sorry for the criticism, and WORKSFORME is better, of course!",1366181978,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"Sorry for the lack of response; I reviewed this bug quite a few times in the months since it was reported, and each time was unable to reproduce (but quite clearly this was a repeatable bug, given the screenshot and two independent reports).
+
+This was not a 'blocker' in the sense that we use it, though obviously for a (seemingly very small) number of installations/situations it was a serious bug.
+
+Glad to hear that it works for you now; unfortunately, as we don't know what the root cause was, we can't proove that it's not going to re-occur. Thus I feel it would be inappropriate to assign it as ""FIXED"", so I will instead mark as ""WORKSFORME"".",1366178124,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"It is possible that the bug has been resolved, I had reported it, but cannot reproduce it. Closing as ""probably fixed"".
+
+A minor criticism on bug management: at the time when Jeffery and I reported this, it was a totally debilitating bug, a blocker. Simply not investigating the bug 4 months, seemingly never testing it, but then reducing the severity to ""minor"" seems odd.",1366174654,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"I can confirm with newest Chrome. Problem only happened to me on the mediawiki.org VE test page, where the en.wikipedia VE works fine.",1355400423,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"**jnichols** wrote:
+
+Screenshot of problem
+
+**Attached**: {F10179}",1355382411,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"**jnichols** wrote:
+
+User:Arctic.gnome VisualEditor Screenshot
+
+//attachment Arctic.gnome VisualEditor Screenshot.JPG ignored as obsolete//",1355382188,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,Could you take a screenshot and attach it to this ticket?,1355380463,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+"VisualEditor: edits marked as ""minor"" without explicit user selection","See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Marking_edits_as_minor for the report and http://en.wikipedia.org/w/index.php?title=Ginger_nut&diff=527654509&oldid=526997552 as an example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355346240,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dmuriij6wzg4f6nemlx3,task_description,resolved
+"VisualEditor: edits marked as ""minor"" without explicit user selection",Add to deployment milestone.,1357594475,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dmuriij6wzg4f6nemlx3,task_subcomment,NA
+"VisualEditor: edits marked as ""minor"" without explicit user selection",https://gerrit.wikimedia.org/r/38480,1355363288,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dmuriij6wzg4f6nemlx3,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"There is only one notice, but it says there are 2!
+
+See the screenshot and also
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=527687053&oldid=527683727
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61335
+
+**Attached**: {F10115}",1355324760,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_description,resolved
+VisualEditor: Deal with en.wikipedia.org's edit notice system,I just fixed it with https://en.wikipedia.org/w/index.php?title=MediaWiki:Common.css&diff=624714120&oldid=624708988,1410207320,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"This is still occuring.  Pages with no edit notices pop up with ""1 notice"" when VE is launched.  It is not even useful in providing a link to where I *can* add an edit notice.",1407760794,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Fixed on-wiki.,1394664023,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"Change 118369 merged by jenkins-bot:
+mw.Target: Add class ""mw-ve-editNotice"" to edit notices
+
+https://gerrit.wikimedia.org/r/118369",1394662517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"Change 118369 had a related patch set uploaded by Krinkle:
+mw.Target: Add class ""mw-ve-editNotice"" to edit notices
+
+https://gerrit.wikimedia.org/r/118369",1394662319,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"Looks like we do have a replacement class that isn't too generic:
+
+ .ve-ui-mwNoticesPopupTool-item ...
+
+Though it is an internal class, not one I'd recommend we promote as an API for wikis to use. Let's use that as a temporary replacement, and add another one soon for the long term.",1394661278,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"(In reply to Erik Moeller from comment #10)
+> Regression; this is happening again on en.wp.
+
+The system is an en.wikipedia hack, and can't be fixed from within VisualEditor without it knowing more than it should about English Wikipedia.
+
+It comes down to their Editnotice system explicitly creating an edit notice to tell sysops ""there are no edit notices on this page, click here to create one"", which they present as... an edit notice.
+
+Thus MediaWiki, and by extend VisualEditor, show it as an edit notice.
+
+Last year I put a system in place that allows them to hide these using a css class.
+
+(In reply to Minh Nguyễn from comment #12)
+> I've proposed a client-side workaround at [[MediaWiki talk:Common.css#Edit
+> notices and VisualEditor]].
+
+That css was adopted by en.wikipedia as of https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.css&diff=562641575&oldid=560030040 and that fixed it for them, last year with this:
+
+/**
+ * Hide the redlink generated by {{Editnotice}},
+ * this overrides the "".sysop-show { display: none; }"" above that applies
+ * to the same link as well.
+ */
+.ve-init-mw-viewPageTarget-toolbar-editNotices-notice .editnotice-redlink {
+    display: none !important;
+}
+
+
+Commit https://gerrit.wikimedia.org/r/#/c/90378/ accidentally removed this class, thus the above CSS rule no longer applies.
+
+The CSS proposed by Minh on [[MediaWiki talk:Common.css#Edit
+> notices and VisualEditor]] is a bit too generic in my opinion, I would recommend against that.",1394660986,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,*** Bug 55951 has been marked as a duplicate of this bug. ***,1394495869,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,*** Bug 61335 has been marked as a duplicate of this bug. ***,1394490038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,I've proposed a client-side workaround at [[MediaWiki talk:Common.css#Edit notices and VisualEditor]].,1392880263,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Bug 55951 is possibly a duplicate?,1392836682,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Regression; this is happening again on en.wp.,1387305797,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Tagging with deploy-train cycle.,1357578650,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,*** Bug 43460 has been marked as a duplicate of this bug. ***,1356713507,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"(In reply to comment #6)
+> Change-Id: I65447da8b88a9bae9c24ff155544ff66b3fe9100
+Merged by Trevor",1355360215,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Change-Id: I65447da8b88a9bae9c24ff155544ff66b3fe9100,1355358427,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"The only thing we need in core for en.wikipedia to drop this (assuming they still actively want to have these red links) is to show a red link to where the edit notice can be edited/created. Once that is in core, the enwiki's template doesn't have to generate it and thus the actual edit notice will be empty.
+
+As a workaround, I'll work on implementing a small jQuery plugin to calculate the visible text in an element. Then we can simply iterate over the edit notices in VE and ignore the ones with no visible text.",1355345877,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"So, as a way around this, could we have a hacky exception? Or should we push upstream and suggest that core editnotices are adjusted so that every wiki has enwiki's system? (Presumably this would need a new Editnotice: namespace if they want general availability.)",1355339876,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"It counts 2 because there are 2. One from VisualEditor (the default alpha-warning) and one from en.wikipedia.org.
+
+English Wikipedia has this self-invented wikitext-organised edit notice system. Long story short, it means there is never not a notice. It always shows something.
+
+In this case the edit notice that it loads is the following html:
+
+<div id=""editnotice-area"" class=""editnotice-area"" style=""clear: both; width: 100%;""><div class=""editnotice-namespace"" style=""width: 100%;"">  </div><div class=""editnotice-link editnotice-redlink sysop-show accountcreator-show"" style=""clear: both; float: right; margin: 0px 0.8em; padding: 0; line-height: 1em; display: none;""> <small><a href=""/w/index.php?title=Template:Editnotices/Page/You_Can%27t_Make_a_Heart_Love_Somebody&amp;action=edit&amp;redlink=1"" class=""new"" title=""Template:Editnotices/Page/You Can't Make a Heart Love Somebody (page does not exist)"">Page notice</a></small> </div><div style=""clear: both;""></div> </div>
+
+English Wikipedia uses Template:Editnotices to maintain their notices (embedded from a one-liner in the MediaWiki namespace) since they don't want to restrict it to sysops. Aside from that they want to advertise this template and make it easy to find. So when there is no edit notice, the template outputs a link to create one. This is not created by MediaWiki nor by VisualEditor.
+
+However it isn't a mini-notice with a red link for most users. It is only visible to sysops and account creators (via the CSS class sysop-show and accountcreator-show), so for regular users it is just empty.",1355339266,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"It looks to me like it counts the edit notice as such even when none is present?
+
+Separately but relatedly, it would probably be nicer to have features such as adding edit notices in the proposed metadata flyout, as opposed to showing a red link notice to users with the right to create notices.",1355336986,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"Yes, I just came to report the same. Confirming that VisualEditor on the English Wikipedia currently states there are two notices when only one is visible.",1355327320,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Like this: https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=615802&oldid=615801
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355298420,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-bbycowhblqb7wl5ri2sh,task_description,open
+Automatically convert external links to local resources to local wiki links if possible,,1604534063,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,,1604532057,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,*** Bug 57019 has been marked as a duplicate of this bug. ***,1397764105,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to Liangent from comment #11)
+> (In reply to James Forrester from comment #10)
+> > No, all edits - this is the same as [http://fr.wikipedia.org/wiki/Foo Bar]
+> > being automatically converted by Parsoid to [[:fr:Foo|Bar]] which it already
+> > does.
+> 
+> I feel there're still some deliberate use cases of external local links, for
+> example, to prevent Echo notifications (see [[Template:Noping]]).
+
+Users making hacks around bugs in Echo sounds like something we should fix in Echo so users don't have to do it, though. :-)",1397756178,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to James Forrester from comment #10)
+> No, all edits - this is the same as [http://fr.wikipedia.org/wiki/Foo Bar]
+> being automatically converted by Parsoid to [[:fr:Foo|Bar]] which it already
+> does.
+
+I feel there're still some deliberate use cases of external local links, for example, to prevent Echo notifications (see [[Template:Noping]]).",1397743062,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to Liangent from comment #9)
+> (In reply to James Forrester from comment #8)
+> > Feels like this has consensus that we should convert newly-added
+> > [http://en.wikipedia.org/wiki/foo] links to [[foo]] automatically; I think
+> > that this should be done inside Parsoid, so moving there.
+> 
+> But only for VisualEditor edits? if Parsoid is going to be used in other
+> stuff eg. bots.
+
+No, all edits - this is the same as [http://fr.wikipedia.org/wiki/Foo Bar] being automatically converted by Parsoid to [[:fr:Foo|Bar]] which it already does.",1397742161,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to James Forrester from comment #8)
+> Feels like this has consensus that we should convert newly-added
+> [http://en.wikipedia.org/wiki/foo] links to [[foo]] automatically; I think
+> that this should be done inside Parsoid, so moving there.
+
+But only for VisualEditor edits? if Parsoid is going to be used in other stuff eg. bots.",1397730019,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Feels like this has consensus that we should convert newly-added [http://en.wikipedia.org/wiki/foo] links to [[foo]] automatically; I think that this should be done inside Parsoid, so moving there.",1397673447,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Also, when users create a new article and want to link back to it immediately, they end up attaching ""?venotify=created"" to the external link they're copy/pasting, and this is something VE will need to strip before converting the URL to a wikilink.",1395682999,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"I think maybe it should just recognize when a url points to an existing Wikipedia article, and offer that as an internal link option, similarly to the way that you get an internal link option for the article titled [[http://en.wikipedia.org/wiki/foo]]. That latter behavior represents a tiny edge case, though, as there are very few articles that start with http://. If there is ever going to be some sort of 'advanced' mode for links, then options to use external links to existing articles and internal links to articles starting http* should be hidden away there. In the vast majority of cases, users intend to create internal links if the article exists, and do not intend to create internal links to pages starting http*.
+
+Incidentally, we want to add the same functionality to the EducationProgram extension for when users paste in a url to the article form: bug 44397.",1377277696,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"I'd go for ""prevent"". (Also, it would be really nice to have it soon).",1377094454,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Seeing a few of these in the feed. Warn, perhaps? (In the link inspector dialog.)",1372610363,PHID-USER-n6a5asuonlcdc2xmndl2,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to comment #2)
+> Sometimes it is done deliberately, e.g. at
+> https://en.wikipedia.org/w/index.php?title=English_Wikipedia&oldid=558847653
+> . 
+> In that case, they do use olids (permalinks), which is a way you could
+> distinguish if you wanted to do the auto-replacement.
+
+We could do an always-replace for [http://foo/wiki/* $1], but that feels like a fragile regexp. :-(",1371420809,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Sometimes it is done deliberately, e.g. at https://en.wikipedia.org/w/index.php?title=English_Wikipedia&oldid=558847653 .  In that case, they do use olids (permalinks), which is a way you could distinguish if you wanted to do the auto-replacement.",1371258257,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Ask, or just silently replace? But then it will 'dirty diff' if this has been done deliberately. Also, to do this, link inspector will need to have a concept of canonical URLs and optional other URLs for this context, which is messy as hell.",1355343159,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+VisualEditor: Retries when badtoken happened should request new tokens,"When I'm using VisualEditor, session failed for unknown reason. The VisualEditor then keep asking whether I want to try again but it always tries with the old token and error ""badtoken"" keeps coming.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355292720,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-kgk6kmve6lavlyhdrvmv,task_description,resolved
+VisualEditor: Retries when badtoken happened should request new tokens,Merged and will go out with wmf5.,1369080457,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kgk6kmve6lavlyhdrvmv,task_subcomment,NA
+VisualEditor: Retries when badtoken happened should request new tokens,Related URL: https://gerrit.wikimedia.org/r/64492 (Gerrit Change Ib43d1938ffa24bc8d1dc76a300e16e486dabd928),1368896118,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kgk6kmve6lavlyhdrvmv,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"Right now, the Save button starts disabled, but when the transaction depth is non-zero it's enabled. This means that two actions that reverse each other (rather than being formally undone) let the user make a 'null edit', which MW then silently accepts.
+
+Ideally, the Save/Create button should be disabled if dm state is identical to page when it was loaded (except for the special-case of oldid pages, where it should always be enabled). Roan suggests a string comparison of the current and original HTML is the least-bad option, given the lack of hash functions in JavaScript.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43270",1355199480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m3nqsseg45psoqx36exc,task_description,resolved
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,I'd suggest that once that change has been merged this bug can be closed.,1363363213,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"Fixed the zero-history case, and the onbeforeunload issue: https://gerrit.wikimedia.org/r/#/c/53988/",1363363142,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"After some more investigation is appears that comparing html might not do the trick. Doing something trivial like typing and deleting may not leave the html in it's original state. We currently have change markers (although these are queued up for deletion), but also hidden things like pawn characters and maybe other things in the future.
+
+We can still implement the transaction stack check which we don't have at the moment, but telling you if there is a non-zero diff may have to be a job for Parsoid.",1363281542,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"Agree on the window.onbeforeunload.
+
+Not totally enamoured with the idea of a modal alert telling users off for behaviour that is currently silently failing (in core wikitext editor, if you make a null save it'll look like it saved, but no new entry in the history log).
+
+Possibly we could over-ride the edit-success box to say ""You made no changes so nothing was saved"" or something similar? We should probably talk to E3 to see if this is something they'd want to see happen in core anyway...",1363280830,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"Right now the Save button becomes enabled after the first transaction is applied and never goes back to disabled, even if the first transaction is undone. While this isn't ideal, doing a full HTML comparison on pretty much every keystroke may be a bit of an unnecessary overhead. Even doing an transaction stack comparison is a little unnecessary.
+
+The real problem here is the creation of null edits and that only needs to be addressed when the save button is pressed. This could trigger an alert (""You haven't made any changes"") and reset the button to disabled. We should also run this check in the window.onbeforeunload handler so people can leave the page nag-free if they undo their edits.",1363254743,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: HTML entities following double-bracket links are not displayed correctly,"Try to VE-edit this page: http://www.mediawiki.org/wiki/VisualEditor:Extension:ConfirmAccount
+
+Compare: http://parsoid.wmflabs.org/mw/VisualEditor:Extension:ConfirmAccount
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355068140,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-log2ro3sq5p5acp2puga,task_description,declined
+VisualEditor: HTML entities following double-bracket links are not displayed correctly,"This works now, ""&nbsp;"" isn't spelled out any more, and the nbsp is rendered as a <span class=""ve-ce-MWEntity""> in the editor as it's supposed to be. There are probably some selection issues with the nbsp's and with the ampersands encoded as &amp; but that's due to a different bug.",1361383659,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-log2ro3sq5p5acp2puga,task_subcomment,NA
+VisualEditor: HTML entities following double-bracket links are not displayed correctly,"Indeed. The wikitext source reads:
+
+ [[File:Bulbgraph.png|18px|Note|link=]]&nbsp;'''Note''':
+
+The html rendering:
+
+ <img> Note:
+
+VisualEditor:
+
+ <img>&nbsp;Note:
+
+Where ""&nbsp;"" are all separate, selectable and editable characters.
+
+They do roundtrip properly though.",1355070979,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-log2ro3sq5p5acp2puga,task_subcomment,NA
+VisualEditor: Selecting multiple empty paragraphs results in selection decreasing by one line per poll interval,"Steps to reproduce:
+Edit a page with VisualEditor.
+Press return key a few times.
+Select those empty lines with mouse or shift+arrows.
+Watch in awe as the selected lines decrease one per polling interval.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354835520,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-7cmqtr6tlqrqawji66zc,task_description,resolved
+VisualEditor: Selecting multiple empty paragraphs results in selection decreasing by one line per poll interval,Fixed here: https://gerrit.wikimedia.org/r/#/c/37364/,1354844641,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-7cmqtr6tlqrqawji66zc,task_subcomment,NA
+VisualEditor: Link inspector suggestions highlight multiple items if they have the same label,"Reproduce:
+
+1. Make a link to http://www.google.com
+2. Click out of the link
+3. Inspect the link
+4. Both new page and external link are selected
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354583100,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-sqz4vnvgzmxmvjkrplhx,task_description,resolved
+VisualEditor: Link inspector suggestions highlight multiple items if they have the same label,Patched in https://gerrit.wikimedia.org/r/#/c/36799/ and merged.  Marking resolved.,1354652046,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-sqz4vnvgzmxmvjkrplhx,task_subcomment,NA
+VisualEditor: Context menu shows up in the wrong place on load if document starts with link,"When a document starts with a link, the animation on the page cause the context's location to be incorrect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354572300,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jprjjnlynxuoul2du4w2,task_description,resolved
+VisualEditor: Context menu shows up in the wrong place on load if document starts with link,Fixed in gerrit 36653,1354573861,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jprjjnlynxuoul2du4w2,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,"https://www.mediawiki.org/w/index.php?title=VisualEditor%3APre&diff=609875&oldid=609874
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353980580,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nhhyjbko2xftjs44uuqt,task_description,resolved
+VisualEditor: Leading newlines in <pre>s get eaten,"Parsoid fixes have landed, issue confirmed fixed in VE as well.",1354757611,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,The VE portion of this is fixed in https://gerrit.wikimedia.org/r/36692 . The Parsoid portion of this is bug 42666 and bug 42667.,1354584256,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,"The approach we're taking now is that VE will work around this in cases where there are semantically meaningful newlines in the <pre> (i.e. >=1 newline read from the DOM) by adding a newline. That only leaves the ambiguity between <pre>Foo</pre> and <pre>\nFoo</pre> , which is syntactic, not semantic, and will be handled by Parsoid using round-trip data.",1354566475,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,"(In reply to comment #1)
+> We can work around this in the converter by setting a flag on these pre's on
+> the way in and checking for it on the way out.
+...or not, grah. Because of the way the DOM API works, I have no way of detecting this from within a browser.",1354563233,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,"Mark and I looked at this and discovered it was because VE round-trips the HTML in question through the browser's HTML parser, which turns ""<pre>\n"" into ""<pre>"". Shockingly, this is actually mandated by the HTML spec.
+
+We can work around this in the converter by setting a flag on these pre's on the way in and checking for it on the way out.",1354155689,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+"VisualEditor: After clicking out of link inspector, pressing enter removes wrong text","1. Type the text ""Foo bar baz""
+2. Select ""bar""
+3. Click the link toolbar button
+4. Click between the a and the z (""ba|z"") to cause the inspector to close
+5. Press enter
+
+Expected result: paragraph is split with ""z"" in a new paragraph
+Actual result: ""bar"" is removed, paragraph is split with ""baz"" in a new paragraph
+
+Occurs in both Firefox and Chrome. Isn't reproducible 100% of the time.
+
+Theory:
+1. User changes selection to ba|z
+2. SurfaceObserver notices and adjusts its selection
+3. Link inspector notices and triggers annotation on a fragment with a different range (the link)
+4. Some bug in SurfaceObserver or SurfaceFragment causes SO to believe the current selection is now the link
+5. User presses enter, SO removes what it believes is the selection
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353378540,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ca4ckkjl6hs65faqueyf,task_description,resolved
+"VisualEditor: After clicking out of link inspector, pressing enter removes wrong text",Fixed in recent inspector rewrite: I38995d4101fda71bfb2e6fe516603507ce820937 and Ibf6b26de299e54ae8688a2653bf5d5538927f8c3,1353971697,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-ca4ckkjl6hs65faqueyf,task_subcomment,NA
+VisualEditor: Zero-length selection in link should show inspector icon,"This currently works for selections within links, but not for zero-length selections. Except if you hit bug 42275, then the inspector icon will appear on every zero-length selection, anywhere, and will chase you forever and ever.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353376860,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-uv4cfp2ue45fk333wtws,task_description,resolved
+VisualEditor: Zero-length selection in link should show inspector icon,Fixed in I38995d4101fda71bfb2e6fe516603507ce820937 and Ibf6b26de299e54ae8688a2653bf5d5538927f8c3,1353971560,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-uv4cfp2ue45fk333wtws,task_subcomment,NA
+VisualEditor: Zero-length selection in link should show inspector icon,This was resolved in the recent inspector rewrite.,1353971278,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-uv4cfp2ue45fk333wtws,task_subcomment,NA
+VisualEditor: Zero-length selection in link should show inspector icon,"This bug seems to only be triggered by newly created links, not by links that were already present on the page.",1353379521,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-uv4cfp2ue45fk333wtws,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"The VisualEditor interface does not currently recognize page protection. If a user visits a protected page (a page to which he or she does not have access to edit), VisualEditor will still display a working edit form and the first click of the ""Save page"" button will work. It will produce a dialog box that will present a second ""Save page"" button that does not work. Ideally, VisualEditor would not let a user get this far without indicating that the page is uneditable.
+
+Related to this, there's no warning for administrators that a page is protected when they're editing the page. This may be a separate bug, however.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352958960,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_description,resolved
+VisualEditor: Don't offer Edit button when user cannot edit page,"Yeah, well, different ""protection"" levels for VE and non-VE editors feels like the wrong kind of solution.",1354127087,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"That's not a problem I guess, but I noticed while implementing it that it was a matter of removing the code that explicitly ignored the presence of the edit button for sysops.
+
+Change-Id: I3fe29c52b743837c2e1d66f25ccdca6115b8bd25",1354126324,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"If we do that it means we can no longer pseudo-restrict ""Edit source"" on a different level than ""VisualEditor Edit"".
+
+e.g. on MediaWiki.org we protected the namespace with sysop, but allowed users to edit it with VE.",1354067377,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"I suppose the lazy solution (use the presence of a button outputted by server side) is sufficient, especially given that if someone games it, saving will still fail. Its only for the UI.",1354054378,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"And for the current page, I suppose wgRestrictionEdit and wgUserGroups could be used.",1353124274,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,We have mw.user.getRights()[async] now in core as well.,1353124198,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,We should be able to detect in JS whether the user has the edit permission for this page. One way we can detect this is by checking whether the user gets an edit tab or a view source tab.,1353115536,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Internal page links touched by VisualEditor contain underscores,"Currently when a user uses the link dialog box tool thing in VisualEditor to specify where certain text should link to, if the user specifies an internal page as the target, the wikitext for the link will use underscores.
+
+For example, I highlight some text in VisualEditor with my mouse and then click the link icon. A ""Hyperlink"" dialog box appears and I enter ""MediaWiki on IRC"" into the text input area. I hit the ""return"" key on my keyboard to make the dialog box disappear and now I have a blue link in my VisualEditor interface. If I then save this page and look at its wikitext source, I see:
+
+[[MediaWiki_on_IRC|fffffffff]]
+
+Internal links are using underscores. This is wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49310",1352957940,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-wydq63k4j2l2fgeenwfb,task_description,resolved
+VisualEditor: Internal page links touched by VisualEditor contain underscores,"This was an issue in VE's internal link handling code, not in Parsoid. Although the original reason for the code working the way it did (normalizing to underscores) was indeed to make Parsoid happy, as I found out the hard way when I tried to fix this by just normalizing to spaces instead.
+
+Fixed in https://gerrit.wikimedia.org/r/34253",1353380505,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wydq63k4j2l2fgeenwfb,task_subcomment,NA
+VisualEditor: Internal page links touched by VisualEditor contain underscores,Possibly a Parsoid issue?,1353018108,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wydq63k4j2l2fgeenwfb,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"The current VisualEditor interface has a ""Save page"" dialog box with an edit summary input field. However, this edit summary input field accepts wikitext, but has no preview feature for what the rendered wikitext will look like. This is a regression from the standard (non-VisualEditor) interface.
+
+Roan said that there be a mini-editor or mini-parser or something stuck in the edit summary area at some point.
+
+**See Also**: {T62535}",1352957640,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-f4bx3pmct7c24xmmqmka,task_description,resolved
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"Change 112490 merged by jenkins-bot:
+Show preview of edit summary in review screen
+
+https://gerrit.wikimedia.org/r/112490",1392851241,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"Change 112490 had a related patch set uploaded by Alex Monk:
+Show preview of edit summary in review screen
+
+https://gerrit.wikimedia.org/r/112490",1392057409,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"To clarify, when the diff is shown ('Review your changes' dialog pane) we want to parse the entered summary and display it, probably above the diff.",1392053170,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"(In reply to comment #1)
+> As Max says, to be resolved by the dialog being a mini-VE surface.
+
+So this has been assigned to me but I think I need a few pointers. Firstly, where can I find the code for mini-surfaces?",1392042811,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"From Bug 53729:
+A De.WP user suggested to include a preview for the edit summary. Report:
+
+https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=122207411#Vorschau_f.C3.BCr_Zusammenfassung_und_Quellen",1380545717,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,*** Bug 53729 has been marked as a duplicate of this bug. ***,1380545659,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"User:Elizium23 at en.wp comments that the current save dialog ""permits entry of an edit summary with newlines, however, no newlines are preserved in the edit summary when it is saved to the Wiki. This is confusing, because I just used a WYSIWYG editor, but what I see in the edit summary is not what I get.""
+
+While, AIUI, the current dialog is only temporary the issue of newlines (and presumably bold, italic, etc) will be applicable to the new ""surface"" unless that doesn't permit these features or edit summaries are upgraded to support them.",1373483224,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"Per bug 51125 (which has been merged into this one), we should show the edit summary if provided in the ""Review your changes"" tab",1373481003,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,*** Bug 51125 has been marked as a duplicate of this bug. ***,1373480869,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"As Max says, to be resolved by the dialog being a mini-VE surface.",1353018028,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: Pressing a list button when covering a selection of a list should unlist only that portion,"Pressing a list button on: 
+
+1. Foo
+2. Bar
+   * Baz
+   * Bang
+     1. Boom
+3. Bing!
+
+with a selection of Bang and Boom should produce:
+
+1. Foo
+2. Bar
+   * Baz
+     Bang
+     Boom
+3. Bing!
+
+(i.e. the selected LIs should be down-converted into a <P> of the most local parent list).
+
+Also, out-dent should stop a list nest level 1, not 0.",1352498880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hh227cldfkbylq2gwxw3,task_description,open
+VisualEditor: Pressing a list button when covering a selection of a list should unlist only that portion,Need to discuss desired behaviour. Not sure we should implement as described above.,1363026409,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-hh227cldfkbylq2gwxw3,task_subcomment,NA
+VisualEditor: Pressing a list button when covering a selection of a list should unlist only that portion,Assigning to Ed; this is to be done after the list code cleanup that he's doing already.,1361381610,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hh227cldfkbylq2gwxw3,task_subcomment,NA
+"VisualEditor: ""List"" buttons causes whole list to be de-listed, or converted to other list type, when only part of it is selected","Expected behaviour is that the part of the list that is selected is transformed, and the rest of the list is left as it was.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352482200,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ugjwuslvzh6eo2ldgto4,task_description,resolved
+"VisualEditor: ""List"" buttons causes whole list to be de-listed, or converted to other list type, when only part of it is selected",Fixed in gerrit 36675,1354579506,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ugjwuslvzh6eo2ldgto4,task_subcomment,NA
+Highlighting syntax within editing window by default,"**Author:** `IJethrobot`
+
+**Description:**
+Having read <https://bugzilla.wikimedia.org/show_bug.cgi?id=16268> and <https://bugzilla.wikimedia.org/show_bug.cgi?id=11627>, this enhancement proposal is sufficiently different and is based on different discussion.
+
+There is a wide consensus of editors who would like to see syntax highlighting in the standard editing window turned on by default, particularly for references, for wiki markup.  This consensus has been reached in two discussions on en.wiki, one at the Village Pump <http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_92#Differentiating_reference_syntax_in_the_editing_window.> and one in a Request For Comments that was a part of Centralized Discussion for 30 days:  <http://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment/Syntax_differentiation_in_editing_window>.  Given the course of the discussion, and the overwhelming support for this functionality, I decided to submit this proposal to bugzilla.  
+
+Many participants in the above discussions expressed that adding a syntax highlighter would make editing a more accessible experience for newer users.  In fact, direct feedback from new editors has suggested that this has been a problem (e.g. <http://en.wikipedia.org/wiki/Special:FeedbackDashboard/46104>).  They are also unsatisfied with 
+
+Previous proposals have stated that implementing this internally is not possible.  However, this is incorrect; there are at least some examples of non-external editors that work or could work reasonably well:
+- jsfiddle:  <http://jsfiddle.net/> (with implementation: <http://doc.jsfiddle.net/>)
+- AceWikiEditor:  <http://no.wikipedia.org/wiki/Hjelp:AceWikiEditor>
+- en.wikipedia user RememberTheDot's syntax highlighter: <http://meta.wikimedia.org/wiki/User:Remember_the_dot/Syntax_highlighter> (which I use).
+
+The only thing I would have liked to see more of in the above discussions were persons who might be able to discuss a specific implementation.  Some discussion of that is here: <http://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment/Syntax_differentiation_in_editing_window#Implementation>.  Such discussion would be helpful here, given the above information on how it may be viable to implement this internally.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1352053440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_description,declined
+Highlighting syntax within editing window by default,"**IJethrobot** wrote:
+
+Thanks.  I didn't know this could be implemented by a local admin.",1352058432,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"Won't get into core, since VisualEditor is where resources are dedicated in this area (unless a volunteer picks it up, which i doubt will happen).
+
+Default gadget seems like the simplest and most effective solution. And devs won't have to deal with all the people complaining which will inevitably follow if this is turned on by default.",1352058259,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"**thewub.wiki** wrote:
+
+If there's consensus on a particular javascript implementation, and it's been thoroughly tested, then it can be done by a local administrator - see https://en.wikipedia.org/wiki/Wikipedia:Gadget#Default_gadgets
+
+Suggest closing this bug since it doesn't require any developer intervention.",1352057194,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"**IJethrobot** wrote:
+
+Right, but I figured in order to turn something on by default for all users, it would need to come here.  Also, a specific implementation would need to be decided upon.",1352054522,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"You know that the existing javascript solutions could be installed as default gadgets, right?",1352054231,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"**IJethrobot** wrote:
+
+Screenshot of AceWikiEditor as an example of syntax highlighting.
+
+**Attached**: {F10235}",1352054136,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"**IJethrobot** wrote:
+
+Example of syntax highlighting using AceWikiEditor
+
+//attachment url.txt ignored as obsolete//",1352054020,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"Splitting this off from bug 27311 (in light of bug 27683 comment 5).
+
+MediaWiki core should have a ""create a redirect"" form. The current system is painfully unintuitive. It requires first figuring out how to create a page at all and then figuring out that you need special ""#REDIRECT [[ ]]"" syntax. Some people make the argument that this toughens people up and prepares them for the wikitext world. I believe that a form really wouldn't kill us here.
+
+Moving a page is sort of a form for making a redirect, but that requires a page already existing. In this bug, we want a form, in MediaWiki core, for creating a redirect. Special:CreatePage or Special:CreateRedirect or something.
+
+This bug might be a dupe of bug 27311, but we can't really know until someone actually implements one or the other.
+
+**See Also**: T29311 T59315",1351128360,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-s6nknz73d36vzlhe7o7x,task_description,open
+Create simple interface for adding a page redirect to MediaWiki core,"(In reply to comment #4)
+> Can someone elaborate on some of the most common use cases for creating
+> redirects to give a bit more background to this for new users not as
+> familiar.
+> 
+> Also, is this a band aid? do we need to step back and think about the reason
+> redirects are created in the first place? Does mediawiki support the concept
+> of
+> page aliases? Does the redirected page need to continue to exist as a regular
+> wikipage after the redirect has happened?
+
+[[m:Help:Redirect]] contains the necessary educational material for the topic.",1385448204,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"**swalling** wrote:
+
+(In reply to comment #4)
+> 
+> Also, is this a band aid? do we need to step back and think about the reason
+> redirects are created in the first place? Does mediawiki support the concept
+> of
+> page aliases? Does the redirected page need to continue to exist as a regular
+> wikipage after the redirect has happened?
+
+Yes, I think the redirected page should exist as a regular wikipage after the redirect has happened. This allows any editor to un-redirect something without needing a special form or other interface, edit the redirect easily, etc. 
+
+Consider this real case from English Wikipedia:
+
+* Someone originally made ""Deforestation in Brazil"" a redirect to the Deforestation section in Amazon Rainforest. This isn't bad, but they're not actually aliases of each other precisely. This happens more than you'd think.
+* Later, someone un-redirected Deforestation in Brazil, and expanded it to be a large independent article. This was made easy by the fact that redirects are still wiki pages. Otherwise, there'd have to be new background processes to re-make a redirect as a wiki page. 
+
+Part of the challenges with the current implementation, which involves using somewhat arcane markup, will be solved by VisualEditor.",1385165137,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"Can someone elaborate on some of the most common use cases for creating redirects to give a bit more background to this for new users not as familiar.
+
+Also, is this a band aid? do we need to step back and think about the reason redirects are created in the first place? Does mediawiki support the concept of page aliases? Does the redirected page need to continue to exist as a regular wikipage after the redirect has happened?",1385164557,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"(In reply to comment #2)
+> Thanks to Daniel Friesen for pointing out that
+> https://www.mediawiki.org/wiki/Extension:CreateRedirect exists.
+
+Right. This bug is about MediaWiki core, though.",1364956227,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,Thanks to Daniel Friesen for pointing out that https://www.mediawiki.org/wiki/Extension:CreateRedirect exists.,1364928187,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"I can see plenty of Wikimedia and other MediaWiki users happy with this feature.
+
+It would be good to know whether there is a buy in from the Core maintainers or whether they think this should be handled by an extension. A rough idea of the estimated work would be useful too. It sounds like a potential candidate for http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects
+
+PS: found thanks to https://www.mediawiki.org/wiki/Bug_management/Triage/20130307",1362675063,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"resources/mediawiki/mediawiki.feedback.js is a little-known built-in software feedback feature that's used by a couple of extensions, notably UploadWizard and VisualEditor.
+
+It posts feedback to a wiki page. It used to also post user-agent information for debugging alongside the feedback. The user-agent information from posted feedback was removed in:
+
+https://gerrit.wikimedia.org/r/#/c/26417/
+
+While the fact that user-agent information is published was disclosed, there was concern that it would be preferable to add an explicit checkbox. The following text has been vetted by legal:
+
+[ ] I understand that my user agent information includes information about my exact browser and operating system version and will be shared publicly alongside my feedback. I agree to provide feedback in accordance with the Terms of Use. 
+
+On WMF sites, that would link to https://wikimediafoundation.org/wiki/Terms_of_Use - not sure we have a standard MW message that would apply here.
+
+--------------------------
+**Version**: 1.21.x
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33365",1350950160,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-6vw3aq5up3oho4pbayyr,task_description,resolved
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Change 192749 merged by jenkins-bot:
+Refactoring mw.Feedback to work with OOUI elements
+
+[[https://gerrit.wikimedia.org/r/192749]]",1425407946,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Change 32700 abandoned by Jforrester:
+Feedback includes browser info, given user permission
+
+Reason:
+Being done as part of Id1967a83a.
+
+[[https://gerrit.wikimedia.org/r/32700]]",1424890020,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Change 192749 had a related patch set uploaded (by Mooeypoo):
+[wip] Refactoring mw.Feedback to work with OOUI elements
+
+[[https://gerrit.wikimedia.org/r/192749]]
+",1424829663,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to James Forrester from comment #9)
+> When you post on a talk page you write every byte that gets inserted (except
+> for ==s for new sections and PST substitutions).
+
+Now that you mention that, I'd say that if you're not logged in, your IP address is also included on the page history.",1410702866,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to James Forrester from comment #9)
+> When you post on a talk page you write every byte that gets inserted 
+
+Definitely not,
+
+> (except
+> for ==s for new sections and PST substitutions). 
+
+as you say yourself,
+
+> That's very different from
+> auto-inserting
+
+and how about the preload parameter?
+If pre-save transform is consider radically different from preload, we could use a new magic word OMGREALLYSCARYPRIVATEDATABUTPLEASESHAREIFYOUWANTTOHELPTHESOFTWARE.",1410702649,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to Nemo from comment #8)
+> (In reply to James Forrester from comment #7)
+> > Though that sounds attractive, I'm told that that would not be appropriate,
+> > informed consent.
+> 
+> How is it different from posting on a talk page? Surely such a difference
+> can be eliminated.
+
+When you post on a talk page you write every byte that gets inserted (except for ==s for new sections and PST substitutions). That's very different from auto-inserting private data (their user agent string) and hoping that they recognise it as such and remove it if they're not comfortable with that level of privacy intrusion.",1409691151,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to James Forrester from comment #7)
+> Though that sounds attractive, I'm told that that would not be appropriate,
+> informed consent.
+
+How is it different from posting on a talk page? Surely such a difference can be eliminated.",1409689188,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to Nemo from comment #6)
+> However I think there ought to be a much simpler solution: why can't the
+> dialog just add the requested user-agent information in the text area?
+> Instead of being blank, the ""message"" could be prefilled with ""~~~~ (using
+> Firefox 30)"" or similar (when configured to do so). The user would have a
+> very obvious way to remove the information by deleting it from the message;
+> if they don't, it will be covered by
+> https://meta.wikimedia.org/wiki/Privacy_policy#Because_You_Made_It_Public
+
+Though that sounds attractive, I'm told that that would not be appropriate, informed consent.",1409669215,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"I very much agree this is needed, especially for https://commons.wikimedia.org/wiki/Commons:Upload_Wizard_feedback where many sections are made of little use for lack of any browser information.
+
+However I think there ought to be a much simpler solution: why can't the dialog just add the requested user-agent information in the text area? Instead of being blank, the ""message"" could be prefilled with ""~~~~ (using Firefox 30)"" or similar (when configured to do so). The user would have a very obvious way to remove the information by deleting it from the message; if they don't, it will be covered by https://meta.wikimedia.org/wiki/Privacy_policy#Because_You_Made_It_Public",1409668075,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,Patch in Gerrit (link in comment 2) still needs review.,1374738778,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,Patch amended with form validation and requirement of checkbox being ticked.,1355279781,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Posting here my review about the proposed label associated to the new checkbox:
+
+(...) The message is associated to a checkbox saying 2 very different things:
+1. Willing and knowledge about sharing browser information
+2. Acceptance of Terms of Use
+
+This makes me think that I HAVE TO mark the checkbox in order to actually submit my feedback, and that along my feedback the User Agent will be visible, and if I don't mark that checkbox it means I don't agree with the Terms of Use and feedback won't be submitted.
+
+This is not what actually happens: Leaving the check unmarked still allows the user to submit the feedback, but without providing the User Agent information.
+
+If the actual behavior is the desired one, the message needs to be split, or at least provide clear ""feedback"" that the checkbox is totally unrelated to Terms of Use acceptance.",1354970468,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Change https://gerrit.wikimedia.org/r/#/c/32700/ 
+Better ideas on msgs?",1352546161,PHID-USER-w6tinhtsh44tn3tgzjtw,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"I have a change ready for this, will push soon.",1352541550,PHID-USER-w6tinhtsh44tn3tgzjtw,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+VisualEditor: Cursor misplaced after clicking on nowiki block,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Click within the nowiki block
+3) Press Left
+Problem: Cursor is now at top of page
+
+Repeating from step 2, the cursor then appears in various places.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350626220,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-rdvinxanauxpvzlynziw,task_description,resolved
+VisualEditor: Cursor misplaced after clicking on nowiki block,Fixed given the alienation re-write.,1360206039,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdvinxanauxpvzlynziw,task_subcomment,NA
+VisualEditor: Cursor misplaced after clicking on nowiki block,Confirmed.,1350939028,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdvinxanauxpvzlynziw,task_subcomment,NA
+VisualEditor: Clicking at the left of a wikicode block does not put the cursor there.,"With this wikicode
+
+= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+
+Problem: Clicking at the left of the wikicode block does not put the cursor there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350615240,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-ncyndehe2estt3jwmggo,task_description,resolved
+VisualEditor: Clicking at the left of a wikicode block does not put the cursor there.,Fixed (https://gerrit.wikimedia.org/r/#/c/48964/).,1360795517,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-ncyndehe2estt3jwmggo,task_subcomment,NA
+VisualEditor: Clicking at the left of a wikicode block does not put the cursor there.,"@James: at this moment we don't have a way to select node yet, so I'm not sure what you are seeing.
+@Nicolas: we might not be able to find solution to this problem soon. However - you should be able to get in front of nowiki block by using your arrow keys.",1360363357,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-ncyndehe2estt3jwmggo,task_subcomment,NA
+VisualEditor: Clicking at the left of a wikicode block does not put the cursor there.,"Confirmed - instead, the nowiki'ed block is selected; the cursor appears to have its location updated though the caret isn't painted.",1350928425,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ncyndehe2estt3jwmggo,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"See https://www.mediawiki.org/w/index.php?title=VisualEditor:LinkTrailReEditBug&diff=594998&oldid=594997&vewhitelist
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350557700,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-stsksyo6vo24yafdejoq,task_description,resolved
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"mw.org is not running current master- it is still on the December code version. So this is to be expected. http://parsoid.wmflabs.org/ runs the latest code.
+
+We need to work out some issues with selective serialization before we can deploy a new version to the mw.org / enwiki backend. You'll see the fix for this bug in production after that deploy.",1360171044,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"(In reply to comment #6)
+> (In reply to comment #5)
+> > It was fixed by a rework of the link serializer I did earlier this month.
+> > That
+> > code is not yet deployed on mw.org. You can verify that it is fixed in
+> > Parsoid
+> > by following Roan's instructions in comment 2. You can also do
+> > 
+> > echo '<p><a href=""Foo"" rel=""mw:WikiLink"">foo</a></p>' | nodejs parse
+> > --html2wt
+> 
+> OK I'll retest it on Feb 4.
+
+Bug persists.
+
+https://www.mediawiki.org/w/index.php?title=VisualEditor:LinkTrailReEditBug&diff=641685&oldid=641684",1360146725,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"(In reply to comment #5)
+> It was fixed by a rework of the link serializer I did earlier this month.
+> That
+> code is not yet deployed on mw.org. You can verify that it is fixed in
+> Parsoid
+> by following Roan's instructions in comment 2. You can also do
+> 
+> echo '<p><a href=""Foo"" rel=""mw:WikiLink"">foo</a></p>' | nodejs parse
+> --html2wt
+
+OK I'll retest it on Feb 4.",1359427311,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"It was fixed by a rework of the link serializer I did earlier this month. That code is not yet deployed on mw.org. You can verify that it is fixed in Parsoid by following Roan's instructions in comment 2. You can also do
+
+echo '<p><a href=""Foo"" rel=""mw:WikiLink"">foo</a></p>' | nodejs parse --html2wt",1359426754,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"(In reply to comment #3)
+> Current output is [[foo]].
+
+I assume this was fixed a while ago because you didn't specify a commit.
+
+But this bug still exists on mw.org. See https://www.mediawiki.org/w/index.php?title=VisualEditor:LinkTrailReEditBug&diff=637012&oldid=637011
+
+I noticed that it's impossible to select a part of a word, click ""Edit link"", then trash the link (the whole word is unlinked instead), but it's still possible to select some characters, then click ""Clear formatting"" to unlink those characters.",1359423539,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,Current output is [[foo]].,1359411632,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"This is a Parsoid bug.
+
+To reproduce: paste <p><a href=""Foo"" rel=""mw:WikiLink"">foo</a></p> into http://parsoid.wmflabs.org/_html/ . This should serialize to [[foo]], or maybe [[Foo|foo]], but not [[Foo]].",1354571718,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,This is especially broken for the second and third case because stray characters are added.,1350557782,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","See [[mw:VisualEditor:ThisPageDoesNotExist]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1350557100,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-y6wx3bzrwdh7htuo432k,task_description,resolved
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong",Code now live in master.,1354565326,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","(In reply to comment #4)
+> (In reply to comment #3)
+> > Fixed in Id88a160621093e4db4cf01c0fa34793cc1a929b4.
+> 
+> Is it fixed in monobook too? 
+
+Yes, it looks fine for me in Monobook.",1354433584,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","(In reply to comment #3)
+> To reproduce this bug:
+> * Set $wgVectorUseIconWatch = true
+> * Log in (to have the ""watch"" right)
+> 
+> It is currently inserted before ""ca-history"". But on new pages there is no such
+> link, so it falls back to appending to the end.
+> 
+> Fixed in Id88a160621093e4db4cf01c0fa34793cc1a929b4.
+
+Is it fixed in monobook too? see comment 1.",1354432539,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","To reproduce this bug:
+* Set $wgVectorUseIconWatch = true
+* Log in (to have the ""watch"" right)
+
+It is currently inserted before ""ca-history"". But on new pages there is no such link, so it falls back to appending to the end.
+
+Fixed in Id88a160621093e4db4cf01c0fa34793cc1a929b4.",1354413186,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","For what it's worth, in Monobook it's even goofier.",1352956851,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","Old summary: VisualEditor: Position of replacement Edit tab is wrong (to the right of 'Watch' (the star) rather than left)
+
+Updated summary: VisualEditor: Position of ""Create"" tab is wrong (to the right of 'Watch' [the star] rather than left)
+
+I believe the updated bug summary better reflects the issue in this bug.",1352956815,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,"It might be impossible to implement, but I am sure many users will wonder why it does not work, so here is the idea:
+
+1) Select some text with the mouse
+2) Press the mouse over the selected text
+3) While staying pressed, move the mouse to somewhere else, then release the mouse button.
+
+Expected: The text is cut-pasted from origin to destination.
+Actual: Nothing happens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350544500,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-qfmwammnoff7cszevjw6,task_description,resolved
+VisualEditor: Click-dragging of media items to move them,"Images drag-and-drop positioning is now merged (in gerrit 69279) and will go live shortly; for non-media items, I've split that off as bug 49981, and am closing this.",1371851883,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,Gerrit 69279 is drag-and-drop moving for images.,1371587614,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,What's the movement on this? Not trying to rush you guys - we have some users wondering :).,1371206697,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,*** Bug 49486 has been marked as a duplicate of this bug. ***,1371058332,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,"I can see that work has started on this, with the mouse cursor changing to a ""move that item"" cursor, and the text caret trying to follow it (despite having some trouble at it sometimes).
+The text does not get moved yet, but I guess the issue is progressing :-)",1366963980,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,Probably possible (at least in Chrome and Firefox).,1360363728,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,"Good catch as an expected editing mode; in other examples of this, it could work as either a ""live"" cut-and-paste, or just flashing a caret where the new content would go.",1350580555,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+"VisualEditor: Add support for adding dir/lang attributes to paragraphs and similar arbitrary elements (div, p, lists etc.)","In MediaWiki pages it is frequently required to write some text in a different languages, and possibly also with different directionality. For example, an quotation in English in an article in the Hebrew Wikipedia.
+
+With the plain wikitext editor this can be achieved using HTML, for example <span lang=""en"" dir=""ltr"">. In some Wikipedias there are templates that do this.
+
+There must be a way to do this using the VE GUI. For example, the user can select the text in a different language, open a dialog with ""Language properties"" and select ""English language"" and ""Directionality: Left-to-right"".
+
+For reference and further details:
+https://www.mediawiki.org/wiki/VisualEditor/Bidirectional_text_requirements
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350148140,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-o7xyvob3g2jy33fpbism,task_description,open
+"VisualEditor: Add support for adding dir/lang attributes to paragraphs and similar arbitrary elements (div, p, lists etc.)",<span> is done. Reopening for <div>.,1375256608,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-o7xyvob3g2jy33fpbism,task_subcomment,NA
+"VisualEditor: Add support for adding dir/lang attributes to paragraphs and similar arbitrary elements (div, p, lists etc.)","
+
+*** This bug has been marked as a duplicate of bug 47759 ***",1373002468,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o7xyvob3g2jy33fpbism,task_subcomment,NA
+"VisualEditor: Add support for adding dir/lang attributes to paragraphs and similar arbitrary elements (div, p, lists etc.)",*** Bug 41010 has been marked as a duplicate of this bug. ***,1350158076,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-o7xyvob3g2jy33fpbism,task_subcomment,NA
+"VisualEditor: Only show minor edit option if user has ""minoredit"" right","Right now the ""This is a [minor edit]"" text in the save dialog appears whether or not you are logged in, which is incorrect behaviour compared to the current editor's save process, and is meaningless (anons can't have edits marked as minor).
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1349380320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hyy5m6djppnbb3qc32pu,task_description,resolved
+"VisualEditor: Only show minor edit option if user has ""minoredit"" right",Landed in master.,1354577109,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hyy5m6djppnbb3qc32pu,task_subcomment,NA
+"VisualEditor: Only show minor edit option if user has ""minoredit"" right",Change-Id: Ie09bb5c8bdbfbb3ec0d4983b74d0697b941153e0,1354419900,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hyy5m6djppnbb3qc32pu,task_subcomment,NA
+"VisualEditor: Only show minor edit option if user has ""minoredit"" right",This is integration more than UI.,1353015719,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hyy5m6djppnbb3qc32pu,task_subcomment,NA
+VisualEditor: Link inspector: Width of suggested titles too short,"The width of suggested titles in the link inspector is too short for practical purposes, see: http://imgur.com/cJEnn
+
+In production wikis like en.wp this will be an issue with titles that are long and hard to disambiguate, e.g. ""List of countries by GDP (nominal) per capita"" vs. ""List of countries by GDP (PPP) per capita"", which would both be abbreviated to ""List of cou...per capita"".
+
+Perhaps the dropdown could dynamically expand in a similar manner to the search box suggestions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1349129640,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-evrtetuy2zbr3a7t4zhq,task_description,resolved
+VisualEditor: Link inspector: Width of suggested titles too short,"Styled suggestion dropdown into a single column which is a much more space conscious approach for displaying longer page titles vs the two column.
+
+Changed in https://gerrit.wikimedia.org/r/36227
+
+Possible enhancement:
+Some additional room could be gained for long titles within a specific namespace by grouping suggestions by namespace and trimming the namespace from the titles.   The label for that group would indicate the namespace for the suggested page.",1354305102,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-evrtetuy2zbr3a7t4zhq,task_subcomment,NA
+VisualEditor: High-res icons don't display if small screen is resized to large,"Broken out from bug 37849: window.devicePixelRatio is checked when loading stuff, and then either a stylesheet for 1.0x PNGs or one using scalable SVGs gets loaded depending on the ratio.
+
+This leads to being stuck with the 1.0x PNGs if you started editing on a low-resolution screen, then moved the window (or detached an external monitor) and moved it to a high-resolution screen.
+
+Per bug 37849 comment 9 there are probably two ways to fix this:
+
+1) Detect resolution changes (window.onresize?) and switch the stylesheet based on the updated window.devicePixelRatio
+
+or
+
+2) Always use SVG icon set if SVG is supported in the browser.
+
+Note that Firefox doesn't yet support window.devicePixelRatio, but it's about to come in in nightlies, before actual HiDPI support for Mac OS X :) -- https://bugzilla.mozilla.org/show_bug.cgi?id=564815
+
+IE 10 doesn't support window.devicePixelRatio at all, which is a bit annoying although it does support SVG and high-resolution screens eg on Windows 8. We can leave that as a corner case for the moment, though use of SVG at all resolutions would conveniently work around it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1347307920,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-yssbwa6yqsenmbrxptpp,task_description,invalid
+VisualEditor: High-res icons don't display if small screen is resized to large,"This is now invalid, as we actually provide the SVGs by default to every browser that doesn't fail on them (yay).",1368811438,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yssbwa6yqsenmbrxptpp,task_subcomment,NA
+VisualEditor: High-res icons don't display if small screen is resized to large,Mark as enhancement; this is nothing like a priority ahead of December. :-),1349115924,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yssbwa6yqsenmbrxptpp,task_subcomment,NA
+VisualEditor: High-res icons don't display if small screen is resized to large,"Keywords spam: High-density HiDPI Retina toolbar icons don't display if window opened on low-res screen, then moved to high-res.",1347385994,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yssbwa6yqsenmbrxptpp,task_subcomment,NA
+"VisualEditor: Links in the CE surface should have the ""cursor:pointer;"" CSS attribute","Suggested by a user.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1346774040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a3lcwcpnaonnbhuser76,task_description,declined
+"VisualEditor: Links in the CE surface should have the ""cursor:pointer;"" CSS attribute","(In reply to comment #2)
+> A pointer implies that clicking will follow the link, when in fact it places
+> a text cursor, hence cursor:text (as it is) is more appropriate. Both LO/OO
+> and Google Docs use cursor:text for links.
+> 
+> WONTFIX unless I have misunderstood the point.
+
+Agreed.",1380214425,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a3lcwcpnaonnbhuser76,task_subcomment,NA
+"VisualEditor: Links in the CE surface should have the ""cursor:pointer;"" CSS attribute","A pointer implies that clicking will follow the link, when in fact it places a text cursor, hence cursor:text (as it is) is more appropriate. Both LO/OO and Google Docs use cursor:text for links.
+
+WONTFIX unless I have misunderstood the point.",1380200003,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-a3lcwcpnaonnbhuser76,task_subcomment,NA
+"VisualEditor: Links in the CE surface should have the ""cursor:pointer;"" CSS attribute",Clarifying - I think this was meant to be about links in the CE surface rather than in the link inspector in any way.,1354669539,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-a3lcwcpnaonnbhuser76,task_subcomment,NA
+Scap doesn't build use correct extension versions on deployment of new versions,"I've been noticing this for a while, but I'm not quite sure why...
+
+I have put in a copy of the ExtensionMessages file from the old version to the newer one, but that uses $IP...
+
+
+On the first run of scap after adding a new version, we get a weird output:
+
+Updating ExtensionMessages-1.20wmf10.php...
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeEditor/CodeEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPage/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/E3Experiments/Experiments.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Echo/Echo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EducationProgram/EducationProgram.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GeoData/GeoData.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Interwiki/Interwiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LastModified/LastModified.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MwEmbedSupport/MwEmbedSupport.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PageTriage/PageTriage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RandomRootPage/Randomrootpage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Renameuser/Renameuser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Scribunto/Scribunto.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TimedMediaHandler/TimedMediaHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TranslationNotifications/TranslationNotifications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaIncubator/WikimediaIncubator.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaShopLink/WikimediaShopLink.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+Updating LocalisationCache for 1.20wmf10... done
+Updating ExtensionMessages-1.20wmf11.php...
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeEditor/CodeEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPage/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/E3Experiments/Experiments.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Echo/Echo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EducationProgram/EducationProgram.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GeoData/GeoData.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Interwiki/Interwiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LastModified/LastModified.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MwEmbedSupport/MwEmbedSupport.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PageTriage/PageTriage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RandomRootPage/Randomrootpage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Renameuser/Renameuser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Scribunto/Scribunto.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TimedMediaHandler/TimedMediaHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TranslationNotifications/TranslationNotifications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaIncubator/WikimediaIncubator.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaShopLink/WikimediaShopLink.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+Updating LocalisationCache for 1.20wmf11... done
+
+
+
+Upon the second run, it seems to work fine (but necessitates 2 runs of scap)..
+
+Will post output when I get round to it
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1346688240,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-e6xtogl4rredgvs524aw,task_description,resolved
+Scap doesn't build use correct extension versions on deployment of new versions,"Obsolete somewhat. I'm not sure whether it's specifically ""fixed"", but I've got a way of doing it so I only need to run it once",1357150957,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-e6xtogl4rredgvs524aw,task_subcomment,NA
+Scap doesn't build use correct extension versions on deployment of new versions,Reedy: Is that still an issue or is this obsolete now?,1356115303,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-e6xtogl4rredgvs524aw,task_subcomment,NA
+Scap doesn't build use correct extension versions on deployment of new versions,"reedy@fenari:/home/wikipedia/common$ scap rebuild 1.20wmf11 localisation cache
+Checking syntax...
+Copying to fenari...ok
+MediaWiki 1.20wmf10: Compiling texvc...ok
+MediaWiki 1.20wmf11: Compiling texvc...ok
+Done
+Updating ExtensionMessages-1.20wmf10.php...
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeEditor/CodeEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPage/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/E3Experiments/Experiments.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Echo/Echo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EducationProgram/EducationProgram.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GeoData/GeoData.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Interwiki/Interwiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LastModified/LastModified.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MwEmbedSupport/MwEmbedSupport.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PageTriage/PageTriage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RandomRootPage/Randomrootpage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Renameuser/Renameuser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Scribunto/Scribunto.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TimedMediaHandler/TimedMediaHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TranslationNotifications/TranslationNotifications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaIncubator/WikimediaIncubator.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaShopLink/WikimediaShopLink.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+Updating LocalisationCache for 1.20wmf10... done
+Updating ExtensionMessages-1.20wmf11.php...
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CodeEditor/CodeEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ContactPage/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/E3Experiments/Experiments.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Echo/Echo.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/EducationProgram/EducationProgram.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/GeoData/GeoData.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Interwiki/Interwiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LastModified/LastModified.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MwEmbedSupport/MwEmbedSupport.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/PageTriage/PageTriage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/RandomRootPage/Randomrootpage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Renameuser/Renameuser.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Scribunto/Scribunto.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TimedMediaHandler/TimedMediaHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TranslationNotifications/TranslationNotifications.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikimediaIncubator/WikimediaIncubator.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikimediaShopLink/WikimediaShopLink.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+Updating LocalisationCache for 1.20wmf11... done",1346692642,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-e6xtogl4rredgvs524aw,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345842600,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mwak57g5crp4aezvpr7x,task_description,resolved
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"This has now (finally!) OK to merge, and has been.",1375140242,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"Change 69856 merged by jenkins-bot:
+Use postEdit mw.hook for save notifications
+
+https://gerrit.wikimedia.org/r/69856",1375140192,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"Change 69855 merged by jenkins-bot:
+Allow postEdit hook to be triggered asynchronously
+
+https://gerrit.wikimedia.org/r/69855",1373927497,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"**swalling** wrote:
+
+%%%*** Bug 50642 has been marked as a duplicate of this bug. ***%%%",1372834231,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),Related URL: https://gerrit.wikimedia.org/r/69856 (Gerrit Change Id4a8bc22c09a552ef79670b0d4fc4a70df07ec33),1371818834,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),Related URL: https://gerrit.wikimedia.org/r/69855 (Gerrit Change I778b18bc051c51de355e122d8d4517b5a651ed4c),1371818082,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"(In reply to comment #8)
+> In VE, saving an edit does not cause you to reload the page, so we
+> can't use the mechanism.
+
+It would only require a very modest refactoring to make the 'postEdit' hook triggerable by VE.",1371661499,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"Looking at the code
+
+https://git.wikimedia.org/blob/mediawiki%2Fcore.git/HEAD/resources%2Fmediawiki.action%2Fmediawiki.action.view.postEdit.js
+
+it appears this extension is not designed to work asynchronously. It expects a cookie to have been set, then fires immediately on page load. In VE, saving an edit does not cause you to reload the page, so we can't use the mechanism.",1371643840,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),*** Bug 43091 has been marked as a duplicate of this bug. ***,1368638967,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"OK, after talking with Steven, [[mw:Extension:PostEdit]] is going to be moved in MW core at which point we can depend on it, and not re-implement the wheel. This means that users will get the same styling and text of messages whether they save via the wikitext editor or VisualEditor; yay.",1368050225,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"I agree 100% that we need a notification and I'm glad that there was some testing that went into it. VisualEditor currently uses the notification bubble stuff in MediaWiki for this, and I think it's an especially good example of a place where it's needed because the save occurs without very much else changing on the page (not even going to a different URL)
+
+Thank you for the clarification, I wanted to make sure we didn't have people changing the notification styles to match that until we had considered a few things first.",1348079663,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"**swalling** wrote:
+
+(In reply to comment #3)
+> Can you expand on ""previously A/B tested""?
+
+I don't want to replicate the entirety of the documentation here on Bugzilla. See the Meta link above for all details, and especially the results subpage. 
+
+The summary is that we tested this for all new registered editors on English Wikipedia for two weeks. The simple confirmation we're suggesting be implemented was the most successful when looking at  a variety of metrics, from sheer volume of edits to quality indicators like revert rates. 
+ 
+> This design is nice, but completely out of place.
+
+To be clear here: I'm _not_ suggesting this exact design be implemented in VisualEditor. I just provided the screengrab so you wouldn't have to guess what the previously tested version looked like. :) 
+ 
+> 1. That is not a safe location to put a notification because it may obscure
+> navigation controls.
+> 2. The size is out of proportion with the rest of the UI
+> 3. The colors and shading are out of sync with the rest of the UI
+> 
+> I would like to see us make notifications work together with the skin, not just
+> succeed at getting people's attention because they are sufficiently loud.
+> Blending in can be detrimental to the function of a notification, but making it
+> look out of place just causes other problems.
+
+I'm not sure if your critique is in the context of the current editor or only VisualEditor, but in addition to my comment above, I'd like to reiterate that this was an experiment, not a permanent implementation. The question we asked was: does it make a measurable difference to new editors to get a confirmation? The answer is a resounding yes. 
+
+To respond on the first point: it didn't much matter that it obscures navigation, because in our implementation of the attached design, it only persists on screen for three seconds.",1348078664,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"Can you expand on ""previously A/B tested""?
+
+This design is nice, but completely out of place.
+
+1. That is not a safe location to put a notification because it may obscure navigation controls.
+2. The size is out of proportion with the rest of the UI
+3. The colors and shading are out of sync with the rest of the UI
+
+I would like to see us make notifications work together with the skin, not just succeed at getting people's attention because they are sufficiently loud. Blending in can be detrimental to the function of a notification, but making it look out of place just causes other problems.",1348077585,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"**swalling** wrote:
+
+Confirmation previously A/B tested
+
+**Attached**: {F10123}",1348004857,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"**swalling** wrote:
+
+To follow up on this:
+
+* We've got requirements and implementation ideas for the current state of the editing experience: https://www.mediawiki.org/wiki/Confirmation_message
+* A/B testing documentation, including results and data: https://meta.wikimedia.org/wiki/Research:Post-edit_feedback
+
+Consistent confirmation messages are a pretty obvious usability enhancement for an editor, especially one where the update to a page is not always visually obvious. When we A/B tested this against a control and variant of the text, a plain ""your edit was saved"" with the design described in the links led to a significant increase in the productivity of new editors. 
+
+I've listed some requirements for incorporating this into MediaWiki as it exists, but haven't specified anything for VisualEditor. I would say that the essential elements for either system is that it included an icon, the text we tested, and that it is visible when editing any part of the page (i.e. it's not hidden if a section anchor is present).",1348004754,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Depends on VisualEditor having a (stable) API. As soon as it is considered stable enough, we can implement support for it in the Cite extension using whatever hook/api it offers.
+
+Also needs detection since there are (obviously) wikis that have Cite but not VisualEditor. So probably some conditionally loaded module.",1345821600,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-q7nnm3osibolbwwipfib,task_description,resolved
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Change 254041 merged by jenkins-bot:
+VisualEditor: Move code for Cite into this repo
+
+[[https://gerrit.wikimedia.org/r/254041]]",1454605559,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Change 254041 had a related patch set uploaded (by Jforrester):
+[WIP] Move VisualEditor code for Cite into this repo
+
+[[https://gerrit.wikimedia.org/r/254041]]
+",1447901269,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Change 248014 merged by jenkins-bot:
+References: Don't load ext.visualEditor.mwreference if Cite is not installed
+
+[[https://gerrit.wikimedia.org/r/248014]]",1445527977,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Change 248014 had a related patch set uploaded (by Esanders):
+References: Don't load ext.visualEditor.mwreference if Cite is not installed
+
+[[https://gerrit.wikimedia.org/r/248014]]
+",1445510346,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,Re-prioritising.,1403630802,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"(In reply to Andre Klapper from comment #3)
+> In Bug 13127 comment 34 anomie wrote
+> ""Since Parsoid has reimplemented the Cite extension in their own code, any
+> fixes to Cite are going to be very difficult to get merged unless someone
+> wants to do all the work twice, once in PHP and once in nodejs.""
+
+That's a totally different issue about Parsoid's Cite vs Cite.php; this bug is about the location of code currently in the VisualEditor-MediaWiki repo that should be moved to the Cite extension's repository, like we did for <math> etc. Not sure if there's a bug about that?
+
+
+> James: Quim wondered if this means that all Cite bugs.docs can be eventually
+> and officially deprecated.
+
+That's a question for the mythical other bug (but I'd say no).
+
+
+> Any vague timeframe for this ticket, assuming that Trevor still works on
+> this?
+
+I'd want it to settle down a little more before the code was transitioned, but probably in a few months' time.",1399054655,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"In Bug 13127 comment 34 anomie wrote
+""Since Parsoid has reimplemented the Cite extension in their own code, any fixes to Cite are going to be very difficult to get merged unless someone wants to do all the work twice, once in PHP and once in nodejs.""
+
+James: Quim wondered if this means that all Cite bugs.docs can be eventually and officially deprecated.
+
+Any vague timeframe for this ticket, assuming that Trevor still works on this?",1399036675,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Adding 'javascript' keyword, because I think this is JavaScript related...",1364291788,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"After discussion with Timo, clarifying what this is.",1364248542,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"See module's code at https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/WikiEditor.git;a=blob;f=modules/jquery.wikiEditor.dialogs.config.js;h=76a3a57e27b6b7d87266171c26baf2a82d9f703a;hb=e7a0484eb56d72e5326282a54288580fdfcd144f
+
+The if conditions at lines 201 and 203 must probably be corrected.
+
+from :  if ( page.missing )
+to   :  if ( page.missing !== undefined )
+
+and
+
+from :  if ( page.invalid )
+to   :  if ( page.invalid !== undefined )
+
+This code checks the api query result,
+which, for instance, has
+    page.missing === """"
+if queried title doesn't exist.
+
+As it is, the ""Insert link"" dialog shows ""Page exists""
+for every title inserted in the ""Target page or URL:"" field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344312120,PHID-USER-6dh2mmgw4sia7dmkixtb,PHID-TASK-xwuorocthdcw4tqbqq2f,task_description,resolved
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"Thank you!
+
+Next time, I'll try to search a bit more, before entering a bug.",1344442901,PHID-USER-6dh2mmgw4sia7dmkixtb,PHID-TASK-xwuorocthdcw4tqbqq2f,task_subcomment,NA
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"This has already been fixed and was merged in July 31st.  
+https://gerrit.wikimedia.org/r/#/c/17019/",1344362215,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-xwuorocthdcw4tqbqq2f,task_subcomment,NA
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"We also encountered this bug in the VisualEditor.
+
+Assigning to Rob who already fixed this in VisualEditor, we should be able to
+apply the same fix to WikiEditor.",1344312908,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xwuorocthdcw4tqbqq2f,task_subcomment,NA
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"(In reply to comment #0)
+
+Sorry for the link. I split the server part, so that could be read.
+
+https://gerrit.wikimedia.org
+
+/r/gitweb?p=mediawiki/extensions/WikiEditor.git;a=blob;f=modules/jquery.wikiEditor.dialogs.config.js;h=76a3a57e27b6b7d87266171c26baf2a82d9f703a;hb=e7a0484eb56d72e5326282a54288580fdfcd144f",1344312646,PHID-USER-6dh2mmgw4sia7dmkixtb,PHID-TASK-xwuorocthdcw4tqbqq2f,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","To reproduce, go to http://www.mediawiki.org/wiki/VisualEditor:Sandbox?veaction=edit , blank the page, save, then you get ""Error saving data to server: ..."" without too much explaination.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50475
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43147
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63149",1344201000,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_description,open
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","I agree that ""Something went wrong"" isn't very helpful.  What would be helpful is an explanation of what to do.  For example, if it's hopeless and you've just lost all of your work, then acknowledging that it's hopeless would save people the time and stress of trying to save it.",1438467773,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","For what is worth, Catalan Viquipedia users confused about an error message from Parsoid:
+
+  Alguna cosa no ha funcionat
+
+  parsoidserver-http: HTTP 500
+
+  Descarta
+
+""Something didn't work""  :)
+
+https://ca.wikipedia.org/wiki/Topic:Shssmsofmcgkqhmv",1432706998,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","I just hit this message (was about to reported a semi-dupe) on enwiki. I got the below variant:
+
+```
+Error loading data from server: parsoidserver-http-bad-status:
+404: No pages were returned from the API request for $article.
+Would you like to retry?"" (yes/no)
+```
+
+I hit yes and it worked. So... why not just retry without asking me first?
+
+If it fails again (or for X times, whatever) then give a more generalized ""ooops, sorry 'bout that"" message with a ""click here for more info"" dropdown (with the message I just pasted, minus the ""would you like to retry?"" bit, of course).",1419389820,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","With the above patch, the former message:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500. Would you like to retry?
+
+… turns into:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500: Page Fetch failure for ""BADURL"": Error: getaddrinfo
+    ENOTFOUND. Would you like to retry?
+
+Which is not ideal, but at least describes things a bit.",1409684371,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","Change 157775 merged by jenkins-bot:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409681806,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","Change 157775 had a related patch set uploaded by Jforrester:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409669828,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","Perhaps call it the ""editing server""? As in ""Sorry, we could not save your changes to the editing server"" and ""Sorry, we could not get a copy of the page from the editing server"" etc.?",1345759375,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","I'm not really sure what else the message should say. If we talk about parsoid, the user will be pretty confused. Are there any suggestions?",1345756907,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"**Author:** `jack`
+
+**Description:**
+Sometimes, it is necessary to fully protect a page which is already semi-protected. Often, the reason for the different protections is different (vandalism and edit warring is a common example), and will have different expiry times. However, if I choose to fully protect a page for a short amount of time, any semi-protection that is set to last longer (or indefinitely) will be erased. It would be helpful if full and semi protection could operate independently of one another, so that a week of full protection would not affect a month of semi-protection.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1344094140,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ciiqin6dnqycnrlibykn,task_description,duplicate
+Full protection expiry should not affect semi-protection,"The other shouldn't have been done by its lonesome, but yes, they probably should be merged at this point.",1731696684,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,See https://meta.wikimedia.org/wiki/Community_Wishlist/Wishes/Restore_long_term_protection_when_short_term_protection_expires for a Wishlist item covering this request.,1731668353,PHID-USER-ksxcfwf6vvnfvopbps4h,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,It looks like {T142209} has more details and discussion about how this could be implemented - any concerns with me merging this task into that one? As I understand it they're the same proposal.,1731668106,PHID-USER-ksxcfwf6vvnfvopbps4h,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"Simply allowing multiple, overlapping protections on a page would solve for this and other use cases. ",1725209723,PHID-USER-7rhaupbuiqkqvy5zashf,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"Instead of semiprotection being restored after temporary full protection expires, ANY longer-term protection should be restored when ANY shorter-term protection expires. That way full protection could fall back to an already existing ECP or semi, or ECP protection could fall back to an already-existing  semiprotection.
+
+Automatic restoring of prior protections might be more manageable by a bot, however.",1725209199,PHID-USER-rkee2nybd3w4nkcil7cf,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"I wrote today on meta (https://meta.wikimedia.org/w/index.php?title=User_talk:TBolliger_(WMF)&diff=18279440&oldid=17799915 ) folllowing text, not knowing of this feature request:
+
+---
+
+̈́`Disclaimer`: ... in last 10 years I saw a lot of mediawiki tinkering which surely spent a lot of man-hours, really man-years and not so much of improvement to end users, meaning Wikipedia volunteers.
+
+https://meta.wikimedia.org/wiki/Community_health_initiative/Per-user_page,_namespace,_and_upload_blocking - This is the first really good idea **I saw** in years, and now //I think// I have an idea for another one good improvement.
+
+* **Description of problem/current mediawiki behavior**: after lock of page expires, page is unlocked, meaning - no protection at all.
+* **Description of wanted mediawiki behavior**: after lock of page to sysop level (full protection) expires, page should either go to **previous** level of protection (e.g. semi-protected), if such exists, or it should be possible to set next protection state of page after full protection expires, when locking the page to set period of time.
+** **Comments**: temporary solution could be using the bot with sysop flag with accompanying tasklist page (list of pages that should be protected at which times).
+** **Answer to above comment**: that is not good software design. It should be designed better, smarter, in the first place. (//Yeah, right.// :)
+
+Maybe this idea already is written somewhere, maybe not. I have no clue. But it's written here and now.
+
+---
+
+Well, I'm glad that this feature request already exist, as that shows that other people also thought about this. I'm not glad about priority of this feature, because, IMO, this needed to be done long before VisualEditor was even first thought of. :)
+
+I copy-pasted this to let everybody know that maybe powers that decide what is important and what isn't ignored this feature request by chance, as there are lot of feature requests already. This is not critical, but implementing this could spare sysops and patrollers some time, and plug one hole in mediawiki by smart design.",1533678395,PHID-USER-3hahyxmftu2sew3v6v6w,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"(In reply to Technical 13 from comment #4)
+> Technically, I think to implement this, each protection level would have to
+> be given it's own column in the table with an expiration date
+
+That's not actually how the existing page_restrictions table is structured.
+
+What would probably have to happen is that they unique index would have to change from (pr_page,pr_type) to (pr_page,pr_type,pr_level). And then various bits of code would need to be adjusted to deal with this.
+
+> and the highest level of non-expired protection would be applied.
+
+It's not necessarily possible to decide that one protection level is ""higher"" than another. For example, you probably know that enwiki created a new ""templateeditor"" protection level. What if enwiki decided they also wanted a special protection level for policy pages, and created a ""policyeditor"" protection level.[1] Which would be higher, ""templateeditor"" or ""policyeditor""?
+
+So what would have to happen is that a page with multiple protection levels active at once could be edited only by editors who could edit through each protection level individually.
+
+There does seem to already be some support along these lines in the code, for example Title::getRestrictions() is defined to return an array of restrictions and Title::checkPageRestrictions() checks whether the user is allowed to edit through all of them. But I don't know for sure whether everything everywhere will correctly handle it.
+
+And despite Title handling multiple restriction levels for an action, there's doesn't seem to be support for the different restriction levels expiring at different times (e.g. Title::getRestrictionExpiry() assumes there's only one relevant time). And then there are the UI issues too, with making a sensible protection form dealing with different restriction levels expiring at different times.
+
+
+ [1]: Yes, this example is *incredibly* unlikely. But it illustrates the point.",1392304060,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"Technically, I think to implement this, each protection level would have to be given it's own column in the table with an expiration date and the highest level of non-expired protection would be applied.  I'm not sure how hard it would be to implement, but think it is a good idea.",1392264323,PHID-USER-qgqq35kbi5wss2tlgmhg,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"**cu.faoil.wp** wrote:
+
+I would also like to see this implemented (sysop on German language wiki). There are many pages that are prone to vandalism and should be semiprotected by default, so it would be good to be able to specify whether the page should go back to being semiprotected or not when setting it to be fully protected for any amount of time.",1353350414,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,This would be nice :). Not sure how it'd work (or if it's possible without a lot of effort) but I'm verifying the enhancement.,1345886882,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"**davidswikipediaemail** wrote:
+
+It would definitely be nice if this could be fixed. I'm not an admin, but I could see where this could be problematic.",1344895736,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Bugzilla products could use a re-examination,"The current set of Bugzilla products doesn't make any sense to me. It's a hodgepodge of arbitrary projects, extensions, and other vague or broad categories. It'd be nice to rearrange the products to be a bit more sane. This will help bug filers and developers alike.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://bugzilla.wikimedia.org/enter_bug.cgi
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43459
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53986",1343952060,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-fwiz7o6xh4rtopisteba,task_description,declined
+Bugzilla products could use a re-examination,"Wikimedia has migrated from Bugzilla to Phabricator. Learn more about it here: https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla - This task does not make sense anymore in the concept of Phabricator, hence closing as declined.",1416786026,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,s/malicious/pernicious/ (a comment on #mediawiki confirmed my suspicion that the inaccurate translation of the Italian word I had in mind is... pernicious).,1381953881,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"I'm adding bug 55807 as blocker, because that bug adds a malicious incentive to this organisational antipattern.",1381953374,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #15)
+> Low hanging fruit? What about moving all the Wikimedia mobile apps under a
+> same
+> umbrella called ""Wikimedia mobile apps"":
+> 
+> * Commons App
+> * Wiki Loves Monuments
+> * Wikipedia App
+
++1. We already did this once! See bug 41922.",1379955370,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"Low hanging fruit? What about moving all the Wikimedia mobile apps under a same umbrella called ""Wikimedia mobile apps"":
+
+* Commons App
+* Wiki Loves Monuments
+* Wikipedia App",1379955103,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #8)
+> I'm gonna go ahead and mark this bug as easy. It really just needs someone to
+> sit down and figure out/write down a sensible hierarchy at
+> <https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy> and
+> then get it implemented (or implement it themselves, if a current Bugzilla
+> admin takes this on). That shouldn't be very difficult to do.
+
+You misunderstood the meaning of the ""easy"" keyword. This keyword is for new developers, to find bugs to start their first commits. While ""writting a list"" is easy, the problem is ""figuring out"" what to put on that list, and a new developer is definitively not the right person to do that. Removing keyword.",1379092634,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #12)
+> For specific cases yes, however we're not after creating pieces of cake that
+> have the same sizes (components with approx. the same amount of bug reports,
+> products with approx. the same amount of components), but after a useful
+> structure that is a good compromise between development teams' areas and
+> reporters finding the right place. :)
+
+Of course! Thanks to your report and stealing some things from comment 10, I've expanded [[mw:Requests_for_comment/Bugzilla_taxonomy]]; this should also clarify other idea I expressed above.",1352477317,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #11)
+> (In reply to comment #4)
+> We also have products which then have only a single component, e.g. the ""* App""
+> products (which are very messy).
+
+What exactly is messy about the *App products?
+
+> (In reply to comment #10)
+> is someone able to generate some compact chart with, ideally, a
+> tree of all products and their components, each with its number of bugs?
+
+Not easily. Once https://bugzilla.mozilla.org/show_bug.cgi?id=385643 gets fixed (Bugzilla 4.4/4.6) it wouldn't show the number of reports.
+
+Huge product×component table for *open* tickets only: 
+https://bugzilla.wikimedia.org/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Analytics&product=CiviCRM&product=Commons+App&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s+Tools&product=Logwood&product=MediaWiki&product=MediaWiki+extensions&product=Monuments+database&product=mwEmbed&product=Parsoid&product=Security&product=Spam&product=Tools&product=VisualEditor&product=WikiLoves+Monuments+Mobile&product=Wikimedia&product=Wikimedia+Labs&product=Wikimedia+Mobile&product=Wikipedia+App&product=Wikisource+App&product=Wiktionary+App&product=Wiktionary+tools&resolution=---&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap
+
+> Products without components can probably be merged as components of a single
+> products, huge components could be split, etc.
+
+For specific cases yes, however we're not after creating pieces of cake that have the same sizes (components with approx. the same amount of bug reports, products with approx. the same amount of components), but after a useful structure that is a good compromise between development teams' areas and reporters finding the right place. :)",1352471913,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #4)
+> The reason was people wanted to be able to have components, which you can't do
+> when an extension is already a component.
+
+We also have products which then have only a single component, e.g. the ""* App"" products (which are very messy).
+
+(In reply to comment #10)
+> MW components have many too labels that are very specific, sometimes the more
+> general component exists, sometimes it doesn't.
+
+To start with, is someone able to generate some compact chart with, ideally, a tree of all products and their components, each with its number of bugs?
+Products without components can probably be merged as components of a single products, huge components could be split, etc. It's really hard to move <s>tanks</s> bullets in https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy without seeing the Risk! map.",1352470858,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"MW components have many too labels that are very specific, sometimes the more general component exists, sometimes it doesn't. Some examples:
+* DjVU 
+* change tagging
+* contenthandler
+* Page (editing|deleting|protection)
+* patrolling
+* redirects
+* resource loader
+* templates
+* user blocking
+
+Some components I think there should be:
+* Parser
+* Content handling related (various actions, diffs, etc)
+* User related
+* Scripts, styles and images (aka ResourceLoader)
+* Logging & history & recent changes
+* Unit tests
+* Maintenance scripts
+* Special pages
+* Language (I18n & l10n)
+* File handling
+* Skins",1349880111,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"For planning the structure you are certainly right, but the actual implementation part requires quite some preparation and planning (mostly because of limitations in Bugzilla).
+Only one example: Massmoving reports from one product to another requires exactly the same Versions / Target Milestones to exist for both products beforehand. Without that you cannot massmove (plus you would lose information). Other option in this case is to split up the reports in several sets with the same Version info and then to massmove each set, but that also takes time.
+
+Adding this comment as I planned and implemented a complete product / component reorg in a Bugzilla 2.22 instance of similar size (amount of bug reports) three years ago, and it took weeks of planning (though not full-time). Maybe Bugzilla 4.x has seen some improvements though in this area - haven't checked lately.",1347375464,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"I'm gonna go ahead and mark this bug as easy. It really just needs someone to sit down and figure out/write down a sensible hierarchy at <https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy> and then get it implemented (or implement it themselves, if a current Bugzilla admin takes this on). That shouldn't be very difficult to do. And don't worry: if you start on this project and head in the wrong direction, people will quickly speak up. :-)",1347333069,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #5)
+> I'm unclear how the use of categories would impact the bug-filing workflow. I
+> guess it would just add an additional click-through step?
+
+Bug filing:
+https://bugzilla.wikimedia.org/enter_bug.cgi would not show the available products as the very first page, but instead the available categories. The products of the chosen classification are listed on the (then) second page.
+
+Bug searching:
+https://bugzilla.wikimedia.org/query.cgi would show an additional list of classifications left to the current list of products.
+
+Bug viewing:
+https://bugzilla.wikimedia.org/show_bug.cgi is not affected.",1344443924,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy,1344289541,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #4)
+> I've said it before and I'll say it again: we need to move them up a level,
+> making extensions a category, individual extensions as products, which then
+> allows them to have components.
+
+I just clarified with Chad that we don't use categories currently, for those wondering.
+
+I'm unclear how the use of categories would impact the bug-filing workflow. I guess it would just add an additional click-through step?",1344289187,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #2)
+> I agree. Why are Visual editor, Huggle, mwEmbed products, Various mobile things
+> products? Visual editor should be considered an extension to start with, etc.
+> 
+
+The reason was people wanted to be able to have components, which you can't do when an extension is already a component.
+
+I've said it before and I'll say it again: we need to move them up a level, making extensions a category, individual extensions as products, which then allows them to have components.",1344271523,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"There is another abstraction level which is currently not in use in Mediawiki Bugzilla: Classifications (a product can be part of one classification). 
+Not that I propose using it here, just FYI.
+
+From an ""expectations"" point of view I personally wonder which extensions are ""3rd party / community"" ones and which ones are ""official"", assuming that it might make a difference in response times on reports, etc (as volunteers have a higher fluctuation rate and abandoning maintainership feels more likely).",1344252877,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"I agree. Why are Visual editor, Huggle, mwEmbed products, Various mobile things products? Visual editor should be considered an extension to start with, etc.
+
+I think there should be the following:
+*MediaWiki - for core stuff
+
+*MediaWiki extensions - for extension.
+**The following products should probably be here:
+**Cortando
+**mwEmbed
+
+*Wikimedia - for site config issues, and issues that specificly pertain to Wikimedia's use of MediaWiki, or other web applications installed by Wikimedia
+**Should also include:
+**CiviCRM
+**Analytics
+**DataSets
+**Wikimedia Labs (Arguably its debatable if labs belongs with the rest of the Wikimedia bugs, I lean on the side it does, but I suppose I could see an argument for it being its own product)
+
+*MediaWiki applications and tools - for things that interact with MediaWiki.
+**The following should be moved here:
+**Huggle
+**Wikimedia Mobile (or extension depending on what that tracks)
+**Wikipedia App
+**Wiktionary App
+**WikiLoves Monuments Mobile
+**Tools
+**Monumounts DB (this one is questionable if it belongs here)
+
+*Security (It should be on its own for permission reasons)
+
+*Spam
+
+---
+
+So that would bring it down to 6 products, with 2 (Security and spam) being kind of fake products",1344003404,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"Cleaning up the bug product descriptions would be nice too. Eliminating the typos, making the punctuation consistent, etc.",1343952268,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],MediaWiki bugs to be fixed for WMF deployment,1343681340,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-dox25wyrywoe37jydxge,task_description,invalid
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"@greg: agreed, I prefer the project/tag over a tracking bug.",1427763864,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],">>! In T40865#1159225, @mmodell wrote:
+> @greg: By ""next train release"" do you mean the new branch that gets created on wednesday or any train deployment in general? 
+
+The perpetual next release. This bug was used by Reedy to have a place to look for bugs to be pushed out with the train.
+
+We now also have #WMF-Server-Backports, which we should probably use in lieu of this tracking bug, which is what https://www.mediawiki.org/wiki/Backporting_fixes says anyway...
+
+If that sounds ok with you (@mmodell) then let's just close this bug, bid it farewell and thank it for its use over the years...",1427748663,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"@greg: By ""next train release"" do you mean the new branch that gets created on wednesday or any train deployment in general? ",1427539819,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],">>! In T40865#1076036, @Nemo_bis wrote:
+>> What are we going to do with this task now?
+> 
+> Maybe Mukunda has opinions. :)
+
+@mmodell: how would you like to deal with ""things (like config patches) people want to be included in the next train release"".
+
+There's already #wmf-server-backports which we aren't using much at all yet.",1427484400,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"> What are we going to do with this task now?
+
+Maybe Mukunda has opinions. :)",1425168031,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],What are we going to do with this task now?,1423883371,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],Cleared backlog of next-deployment changes that have since been processed.,1417566587,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"(In reply to comment #16)
+> Greg, are we still using this tracking bug?  If not, let's just close this.
+
+Reedy is, and intends to, keep an eye on it. Andre and others are using it actively. I less so, but Andre usually beats me to the punch.
+
+There's also the request for backport flag, which is being used (9 confirmed requests, last one sept 25th). Slight overlap, but not much, really (this one being for ""things that should be done at next train start"" and backport flags being for ""this needs to happen now, now."").",1381948247,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"(For reference, Greg and Reedy say that we do.)",1381947940,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"Greg, are we still using this tracking bug?  If not, let's just close this.",1378310071,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],42512 blocks Nov 28 deployment to commons,1354128453,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"(In reply to comment #12)
+> (In reply to comment #2)
+> > This must not have any unresolved dependencies before a new wmf-branch is
+> > created and deployed.
+> 
+> Rob, just to know: is this an actual decision or just a generic hope?
+> 1.20wmf12 has been deployed to all non-Wikipedia projects without resolving
+> blockers. en.wiki is scheduled for Monday and it's completely unclear what's
+> supposed to happen before and after such deployment.
+
+I'm not sure that is a question, if it is that is a problem. Though we already knew that. Obviously we do have the principle of blocking bugs. The question is where they are listed (in this case on this bug), and secondly it is important that before deployment stuff here doesn't have loose ends.
+
+We can't demand bugs to be fixed by just dumping them on this bug, what I think is a reasonable demand however is that there are no unresolved blockers at the deployment window. Meaning either they are fixed, or removed from the blocker list. But not ignored and let to rot, which is very frustrating but current practice (!).
+
+From spending time in the office I know that's not the case they're not ignored. People do go over this blocker list and decide to either backport a fix, write a new patch or decide it is not important enough. The problem is that result is then not communicated back down to where it belongs: The bug itself and therewith the blocker list here.
+
+It can happen that a decision is made that a bug is not blocking enough, but then it should simply be removed as blocker (with a rationale in the bug comment) and either:
+* assigned to a person to work on soon after deployment
+* or if not important right now and no person available as assignee, put on a milestone for later (e.g. 1.20 release)
+* or if no milestone, adjust the overall priority.",1348244262,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],Boldly adding bug 38158 as a blocker. (I hope I'm not doing anything wrong.),1348241902,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"(In reply to comment #2)
+> This must not have any unresolved dependencies before a new wmf-branch is
+> created and deployed.
+
+Rob, just to know: is this an actual decision or just a generic hope?
+1.20wmf12 has been deployed to all non-Wikipedia projects without resolving blockers. en.wiki is scheduled for Monday and it's completely unclear what's supposed to happen before and after such deployment.",1348215547,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 39841 has been marked as a duplicate of this bug. ***,1348078058,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 37346 has been marked as a duplicate of this bug. ***,1348078033,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 38803 has been marked as a duplicate of this bug. ***,1348078024,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 29068 has been marked as a duplicate of this bug. ***,1348077968,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 36464 has been marked as a duplicate of this bug. ***,1348077960,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 36465 has been marked as a duplicate of this bug. ***,1348077949,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 36664 has been marked as a duplicate of this bug. ***,1348077939,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 36974 has been marked as a duplicate of this bug. ***,1348077921,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 39515 has been marked as a duplicate of this bug. ***,1348077881,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"Renaming this bug to be a generic ""rolling tracking"" bug for each wmf deployments.
+
+This must not have any unresolved dependencies before a new wmf-branch is created and deployed. After deployments, dependencies can be purged. Using a tracking bug instead of a milestone so that it can work cross-product (Tasks for configuration in Wikimedia, bugs in MediaWiki core, stuff in extensions, VisualEditor etc.).",1348077861,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"Note to tracking bug readers: don't take the summaries too literally, some (or most) of the tracked issues are actually handled after deployment; always check the server admin log and [[Special:Version]] carefully.",1347688250,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+VisualEditor: Use prefix when accessing parsoid,"Use a prefix when accessing parsoid. See https://gerrit.wikimedia.org/r/#/c/15626/ for details.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343673300,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-wvifmqwchjuqimprw5ls,task_description,resolved
+VisualEditor: Use prefix when accessing parsoid,Done in https://gerrit.wikimedia.org/r/#/c/19417/,1345485579,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wvifmqwchjuqimprw5ls,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"This sounds to me like it might be hideously complicated, but putting it in here - e.g. a link to [http://foo.com] gets an external link notification icon on its right on the English Wikipedia, and this should show up as appropriate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33084
+https://bugzilla.wikimedia.org/show_bug.cgi?id=37901",1343330820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdz73xd47uv2yacm4zi7,task_description,resolved
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),Marking this back as FIXED (as it has been fixed in Vector for a while).,1409609753,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 151395 merged by jenkins-bot:
+Use .mw-body in skins
+
+https://gerrit.wikimedia.org/r/151395",1409603434,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 151395 had a related patch set uploaded by Jforrester:
+Use .mw-body in skins
+
+https://gerrit.wikimedia.org/r/151395",1408200759,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 153740 abandoned by Catrope:
+Scope external link styling rules to #content rather than #bodyContent
+
+Reason:
+Yeah, that looks much better, thanks guys.
+
+https://gerrit.wikimedia.org/r/153740",1408143297,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 153740 had a related patch set uploaded by Catrope:
+Scope external link styling rules to #content rather than #bodyContent
+
+https://gerrit.wikimedia.org/r/153740",1407893356,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"(In reply to Spinningspark from comment #6)
+> I'm not seeing this as entirely fixed.  The redlink issue has been fixed but
+> there are still other colour issues:
+> 
+> * Visited redlinks are not shown in the visited redlink colour, they are
+> shown in the redlink colour.
+> * External links are not shown in the external links colour, they are shown
+> in the internal links colour.
+> * Link icons are omitted: external, secure, pdf etc.
+> 
+This caught my attention because external link icons have been working for me for a while. Turns out they work in Vector but not in Monobook. This appears to be a bug in Monobook, it's scoping link icon CSS to the wrong div (#bodyContent instead of #content).",1407893056,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"I'm not seeing this as entirely fixed.  The redlink issue has been fixed but there are still other colour issues:
+
+* Visited redlinks are not shown in the visited redlink colour, they are shown in the redlink colour.
+* External links are not shown in the external links colour, they are shown in the internal links colour.
+* Link icons are omitted: external, secure, pdf etc.
+
+The raison d'etre of VE is that it is WYSIWYG while editing.  Not having links in the right colour defeats this and can lead to mistakes.",1407764010,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),Verified the fix in production,1400012359,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),Verified the fix in Betalabs and test2,1399406719,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 130769 merged by jenkins-bot:
+Style external links and their suggestions with the right color
+
+https://gerrit.wikimedia.org/r/130769",1398904004,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 130769 had a related patch set uploaded by Jforrester:
+Style external links and their suggestions with the right color
+
+https://gerrit.wikimedia.org/r/130769",1398901923,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Applying the same CSS may be difficult, but internal vs external links should be rendered differently somehow.",1373671765,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+"VisualEditor: Long preformatted nodes display content splitting words at exactly browser width, not word-wrapped","From user submission. See also https://mediawiki.org/wiki/File:VE_-_sentence_break_pre_formatted_text.png
+
+{F117608,size=full}
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1340916420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ca53s4wb5hmrmn3k5jlh,task_description,resolved
+"VisualEditor: Long preformatted nodes display content splitting words at exactly browser width, not word-wrapped",Merged and will go out with wmf5.,1369428648,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ca53s4wb5hmrmn3k5jlh,task_subcomment,NA
+"VisualEditor: Long preformatted nodes display content splitting words at exactly browser width, not word-wrapped",Related URL: https://gerrit.wikimedia.org/r/65332 (Gerrit Change I9b5e3b3e62b52c86743ee345b1cc31beec0a061e),1369427242,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ca53s4wb5hmrmn3k5jlh,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"From bug T35091:
+
+- The UI of the visual editor should have a change to the user's interaction
+with link creation to make it harder to accidentally create things like
+<a>foo</a>bar.
+
+I'm not quite sure what the ui change should be. Perhaps something like making
+it so that when you try to create a link the selection might be altered to
+cover the full word. Something that would require the user to force the editor
+to use the selection that would create a <nowiki/> instead of just accepting it
+as-is.
+
+Whatever the case, we do not want the user who partially selects a run of text
+and turns it into a link to inadvertently create a <nowiki/> when they likely
+intended to make a link of the whole thing.",1340654460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_description,open
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I think users wouldn't try to partially-select for linking if [[apple]]s worked with VE.
+And one half of fixing that would be to search for ""Apple"" for links suggestions if ""Apples"" isn't found.
+If the user then selects ""Apple"" in the suggestions, the correct
+
+```
+<a href=Apple>apples</a> -> ""[[apple]]s""
+```
+link would be created.
+
+And if ""Apple"" is found (because a redirect from ""Apples"" to ""Apple""), since it can be detected as a part of ""Apples"", the correct link can be created too.",1488146470,PHID-USER-mapumhlp3gw5qefhvafn,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I think users wouldn't try to partially-select for linking if [[apple]]s worked with VE.
+And one half of fixing that would be to search for ""Apple"" for links suggestions if ""Apples"" isn't found.
+If the user then selects ""Apple"" in the suggestion, the correct
+
+```
+<a href=Apple>apples</a> -> ""[[apple]]s""
+```
+link would be created.
+
+And if ""Apple"" is found (because a redirect from ""Apples"" to ""Apple""), since it can be detected as a part of ""Apples"", the correct link can be created too.",1488146450,PHID-USER-mapumhlp3gw5qefhvafn,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I think users wouldn't try to partially-select for linking if [[apple]]s worked with VE.
+And one half of fixing that would be to search for ""Apple"" for links suggestions if ""Apples"" isn't found.
+If the user then selects ""apple"" in the suggestion, the correct
+
+```
+<a href=Apple>apples</a> -> ""[[apple]]s""
+```
+link would be created.
+
+And if ""Apple"" is found (because a redirect from ""Apples"" to ""Apple""), since it can be detected as a part of ""Apples"", the correct link can be created too.",1488146295,PHID-USER-mapumhlp3gw5qefhvafn,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to Krinkle)
+> VisualEditor: Make it hard for users to partially-select some text for linking
+> →
+> VisualEditor: Make it easier to select a link in its entirety (instead of part it)
+
+This isn't actually the bug as filed (or the problem). It's already trivially easy to select an existing link in its entirety (you don't even need to select it); this bug is about when you've made a selection of text which doesn't have a link and are making it into one.
+
+Reverting and making a little clearer.",1403712091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"Sorry, that second link should be bug 48789",1374776714,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #10 and comment #8)
+These issues should be solved by making it easy to explicitly set the link and the display text independently and unambiguously in the link dialog as is asked for in bug 50945 and bug 47879",1374776628,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #9)
+> (In reply to comment #7)
+> > What is the status of this bug? Currently it is not possible to link or
+> > unlink part of a word, nor to unlink part of a multi-word link.
+> 
+> That's a very worrying problem - what browser are you using that makes this
+> impossible? Does it happen on every page? When you say ""impossible"", do you
+> mean that:
+> 
+> * the link inspector doesn't open when fired on a partial selection,
+> * setting the link on a partial selection doesn't cause a link to be added,
+> * on saving the link on the partial selection, it doesn't turn into the
+> expected wikitext, or
+> * something else that I've not covered?
+> 
+> I can very much add and remove links to parts of words using the link
+> inspector, and remove parts of existing links using the ""clear formatting""
+> button. Hence the issue.
+
+The behaviour has changed since the last depot it seems. Currently when using Firefox 22 on Xubuntu Linux:
+*Selecting part of a word and pressing ctrl+k means I can link only the selected part (previously ctrl+k was selecting the whole word and then opening the link dialog). This currently works as it should.
+*Unlinking part of a word or multi-word link is not possible with the link tool: 
+**If there is the link [[Background]] and I select ""ground"" and press ctrl+k the selection is changed to ""Background"" and then the link dialog opens
+**If there is the link [[Woolwich Arsenal station]] and I select ""station"" and press ctrl+k the selection is changed to ""Woolwich Arsenal station"" and then the link dialog opens. (This has not changed since my previous comment)
+*Selecting part of a linked word or phrase and removing the formatting does remove the link only on the selection, but also removes any and all other formatting on that selection. Per Bug 51757 this is not desirable.",1374776463,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #8)
+> I fail to see the purpose of nowikiing the remainder of a partially linked
+> word.  If I link ""LC circuit"" in the string ""LC circuits"" then I expect the
+> UI
+> to create ""[[LC circuit]]s"", not ""[[LC circuit]]</nowiki>s"".  That latter
+> behaviour is entirely useless in any normal editing scenario I can think of.
+> 
+> The selection should not be expanded automatically.  The UI should assume the
+> editor knows what they are doing unless there is evidence to the contrary. 
+> When I make a partial selection like this it means I want the UI to offer ""LC
+> circuit"" as the link target and display ""LC circuits"" as the link text.
+
+That may be what you expect, with your deep understanding of wikitext, but it's very far from how normal visual editors work and so would be very confusing to users who are not immersed in the fine points of link trails.
+
+More fundamentally, making a change in one place that magically affects another is a bad user experience. Why would this magic happen with links but not, say, adding bold? Why would this happen down-word but not up (except on wikis with linkhead instead of/as well as linktrail)? Etc.",1374773573,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #7)
+> What is the status of this bug? Currently it is not possible to link or
+> unlink part of a word, nor to unlink part of a multi-word link.
+
+That's a very worrying problem - what browser are you using that makes this impossible? Does it happen on every page? When you say ""impossible"", do you mean that:
+
+* the link inspector doesn't open when fired on a partial selection,
+* setting the link on a partial selection doesn't cause a link to be added,
+* on saving the link on the partial selection, it doesn't turn into the expected wikitext, or
+* something else that I've not covered?
+
+I can very much add and remove links to parts of words using the link inspector, and remove parts of existing links using the ""clear formatting"" button. Hence the issue.",1374773288,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I fail to see the purpose of nowikiing the remainder of a partially linked word.  If I link ""LC circuit"" in the string ""LC circuits"" then I expect the UI to create ""[[LC circuit]]s"", not ""[[LC circuit]]</nowiki>s"".  That latter behaviour is entirely useless in any normal editing scenario I can think of.
+
+The selection should not be expanded automatically.  The UI should assume the editor knows what they are doing unless there is evidence to the contrary.  When I make a partial selection like this it means I want the UI to offer ""LC circuit"" as the link target and display ""LC circuits"" as the link text.",1374772448,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"What is the status of this bug? Currently it is not possible to link or unlink part of a word, nor to unlink part of a multi-word link.",1374519862,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I really do not understand (my interaction with this bug was due to searching whether another bug was already reported). 
+
+I understand that ""[[Automatic|auto]]mobile"" will create a link on automobile, whereas ""[[Automatic|auto]]<nowiki />mobile"" creates a link only on auto. 
+
+However, the html conversion should work:
+<a href=Automatic>Auto</a>mobile -> ""[[Automatic|auto]]<nowiki />mobile""
+<a href=Automatic>Automobile</a> -> ""[[Automatic|automobile]]""
+and
+<a href=Auto>Automobile</a> -> ""[[Auto]]mobile"" (checking for true substring).
+
+If the discussion is about whether to preserve
+[[Automatic|auto]]mobile
+over
+[[Automatic|automobile]]
+then I believe it should not be preserved, the first is unnecessarily complicated. These are things that are possible to ""clean-up"", particularly if, as you plan for the future, you clean-up only those parts that have been edited.",1355435460,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #4)
+> I would warn about automatic changes here. Partially linked words are a
+> standard feature of Wikipedia, especially to link the singular substring of
+> plural words in languages that generally allow that.
+> 
+> A nice-to-have feature may be to provide a dialogue box asking: ""you have
+> only
+> marked a part of the word -  do you want to link the entire word?"".
+> 
+> I consider this a low priority enhancement however.
+
+We're talking here about creating links as <a href=Foo>Fooian</a>, and whether or not they convert to ""smart"" wikitext ([[Foo]]ian) or to the more boring form ([[Foo|Fooian]]). We're not talking about automatic changes - if the link hasn't been edited, it shouldn't be changed.
+
+I don't think that the style of wikitext that people create using the VisualEditor (as opposed to not breaking others' wikitext) is hugely important, but if you want that to be a specific change, you could create a new bug for Parsoid (which is responsible for the HTML->wikitext conversion).
+
+This is specifically about creating a link (to whatever target) on some selection of part of a word, which then on being saved is converted unintentionally. I.e.: 
+
+Automobile -> <a href=Automatic>Auto</a>mobile -> [[Automatic|auto]]mobile
+
+… whereas it should end up somehow as [[Automatic|auto]]<nowiki />mobile, or we should stop users for creating it.",1355434765,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I would warn about automatic changes here. Partially linked words are a standard feature of Wikipedia, especially to link the singular substring of plural words in languages that generally allow that.
+
+A nice-to-have feature may be to provide a dialogue box asking: ""you have only marked a part of the word -  do you want to link the entire word?"".
+
+I consider this a low priority enhancement however.",1355396945,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #2)
+> (In reply to comment #1)
+> > I like the idea of expanding the selection (altering it) to cover the full
+> > word, however it still have to be possible to link just a part of the word (not
+> > sure how).
+> 
+> Link a whole word then unlink a part?
+
+It is not very intuitive, but maybe we don't need this particular action to be intuitive.",1340669953,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #1)
+> I like the idea of expanding the selection (altering it) to cover the full
+> word, however it still have to be possible to link just a part of the word (not
+> sure how).
+
+Link a whole word then unlink a part?",1340669538,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I like the idea of expanding the selection (altering it) to cover the full word, however it still have to be possible to link just a part of the word (not sure how).",1340659184,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Support media (tracking),"I know this isn't ready yet, but that's why we need a bug in the bug tracker. :)
+
+Steps to repro:
+* create a new page in classic editor
+* include [[Image:Wiki.png]]
+* edit in visual editor
+* save
+
+Expected:
+Image should display in edit mode. After saving, nothing should have changed.
+
+Actual:
+Image becomes invisible in edit mode. After saving, it turns into literal HTML:
+<img src=""http://upload.wikimedia.org/wikipedia/commons/b/bc/Wiki.png"" alt=""Wiki.png"" height width=""200px""></img>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340471220,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_description,resolved
+VisualEditor: Support media (tracking),">>! In T39870#997795, @Jdforrester-WMF wrote:
+> Replaced with projects.
+
+Which ones? I definitely can't watch the entire VisualEditor-MediaWiki-plugins component.",1422430004,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),Replaced with projects.,1422425089,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),Related URL: https://gerrit.wikimedia.org/r/68223 (Gerrit Change I547e06dcdb92e19f0159660314187c4f1a62f3ed),1371066070,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),*** Bug 48254 has been marked as a duplicate of this bug. ***,1369093449,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),Turn back into the tracker for the overall enhancement.,1340575601,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),Tested in Firefox 16 nightly.,1340471400,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,"If I input ~~~, it's converted to my signature. If I input <nowiki>~~~</nowiki>, the nowiki tag is escaped and wrapped and ~~~ is still PST'ed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340390580,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-vpi6cxw7fpw4iujs76of,task_description,resolved
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,Patch committed in https://gerrit.wikimedia.org/r/37996,1355190239,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,"We don't recognize tildes in the tokenizer yet, which would also be the reason why they are not yet escaped. Tildes are already included in syntactic stops used by urltext, but there is no production actually matching them. Should be relatively easy to add.
+
+For regular Wikitext->HTML parsing, those tildes need to be converted back to plain text however (essentially ignored), as they are normally only processed in a pre-save transform. 
+
+An alternative (and arguably simpler) solution would be a simple regexp-based escape rule in escapeWikitext.",1344292658,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,"Actually a Parsoid issue, moving.",1344290780,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,Tweaking summary so it's clear this is about how multiple-tilde strings are handled on save.,1340417044,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,Not sure this isn't intended behaviour. Roan?,1340413000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,Mass-moving items into VisualEditor product,1340402739,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away","After an error message, the spinner is still there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340390280,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_description,resolved
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Merged into master.,1354834279,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Patch in: I6a697dc6bddeebecf4e2ab26805bee9f3754c714,1354832426,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",*** Bug 42125 has been marked as a duplicate of this bug. ***,1354054812,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Pushing to next milestone as they did not make it to master by yesterday.,1352832077,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Bug 39057,1344201043,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away","(In reply to comment #3)
+> Are there steps to reproduce this bug?
+
+Go to http://www.mediawiki.org/wiki/VisualEditor:Sandbox?veaction=edit , blank the page, save, then you get ""Error saving data to server: ..."" without too much explaination (this should be another bug) in an alert() box. After closing the box, ""Save page"" button keeps disabled with a spinner running.",1344200963,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Mass-moving items into VisualEditor product,1340402744,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Are there steps to reproduce this bug?,1340400677,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away","(In reply to comment #1)
+> (In reply to comment #0)
+> > After an error message, the spinner is still there.
+> 
+> What? Please write a proper bug description or I'm simply going to mark this
+> bug ""invalid.""
+
+See the new title.",1340395551,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away","(In reply to comment #0)
+> After an error message, the spinner is still there.
+
+What? Please write a proper bug description or I'm simply going to mark this bug ""invalid.""",1340394443,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+Throw a clean error when user is blocked,"When you attempt to edit something using VisualEditor but you're blocked, in Chrome a ""Error loading data from server: error. Would you like to retry?"" dialog appears instead of the expected MediaWiki:Blockedtext or MediaWiki:Globalblocking-ipblocked error message(s).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340309160,PHID-USER-wqc7ciyvfzunj3l2tvjt,PHID-TASK-usdc5jwsnmb44rymudwh,task_description,invalid
+Throw a clean error when user is blocked,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341826,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-usdc5jwsnmb44rymudwh,task_subcomment,NA
+Throw a clean error when user is blocked,"I can only reproduce this via the proxy site that the reporter was using was broken in that accessing /w/api.php gave a 404. That same proxy site had similar issues with other URLs as well, and threw a few dozen 404s for every page load.
+
+Closing this as INVALID, feel free to reopen if this or a similar issue can be reproduced without using a proxy site.",1340311908,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-usdc5jwsnmb44rymudwh,task_subcomment,NA
+Search does not find some pages,"**Author:** `saibotrash`
+
+**Description:**
+A search for Dateiverschieber https://commons.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Dateiverschieber&fulltext=Search&ns8=1&redirs=1&profile=advanced should find [[commons:MediaWiki:RenameRequest.js]]
+
+But it does not. Similarly for other query strings. The word is on that page since at least three months.
+
+It works for other, even older pages.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**Whiteboard**: cirrus-fixed
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52782",1339634040,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4h4phdyks6plprfkjwnh,task_description,declined
+Search does not find some pages,"Verified that this bug no longer exists in CirrusSearch, as the third search result for that query for me is RenameRequest.js. As we're migrating from Lucene to CirrusSearch, I'm closing this bug as RESOLVED WONTFIX.",1391825471,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"This results in VisualEditor returning empty searches even when the exact, complete file name is given as the search term.
+
+At Commons' own Special:Search, searching for the exact, complete file name produces self-contradictory results:
+
+  There were no results matching the query.
+  There is a page named ""File:GreatNurse.jpeg"" on this wiki",1376417868,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"(In reply to comment #0)
+> A search for Dateiverschieber
+> https://commons.wikimedia.org/w/index.
+> php?title=Special%3ASearch&profile=advanced&search=Dateiverschieber&fulltext=
+> Search&ns8=1&redirs=1&profile=advanced
+> should find [[commons:MediaWiki:RenameRequest.js]]
+> 
+> But it does not. 
+
+Confirming for this example.",1360582360,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"**ForoaW** wrote:
+
+Related problems/reports:
+* [https://bugzilla.wikimedia.org/show_bug.cgi?id=6090]
+* [https://bugzilla.wikimedia.org/show_bug.cgi?id=35691]
+* [https://bugzilla.wikimedia.org/show_bug.cgi?id=30595]",1343294906,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"At the Commons Village Pump thread linked in the previous message: 
+*http://commons.wikimedia.org/wiki/Commons:Village_pump#Is_there_something_wrong_with_the_search_engine.3F
+
+LX suggests: ""since we can't trust files to be indexed on upload, we should probably have a scheduled low-priority process to rebuild the index periodically.""",1343204106,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"I came here to file a new request, and I am quite surprised to see that nobody really cares about such a major feature being broken.
+Another example. This search http://commons.wikimedia.org/w/index.php?search=chimurenga&title=Special%3ASearch does not return http://commons.wikimedia.org/wiki/File:Lettera27_-_Rucera_Seethal_(Chimurenga_magazine_staff).jpg or http://commons.wikimedia.org/wiki/File:Lettera27_-_Chairmaine_(Chimurenga_magazine).jpg .
+As suggested by another user at http://commons.wikimedia.org/wiki/Commons:Village_pump#Is_there_something_wrong_with_the_search_engine.3F , a Google search instead returns 58 more results.
+Too bad you can not use an external search to perform mass operations such as adding or removing categories. I am part of a GLAM team. Search is vital for us as well.",1343115053,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"Interestingly there are results for ""Request renaming of an image"" or ""rAbort"".",1339659271,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"**Author:** `questpc`
+
+**Description:**
+I developed my extension in 1.18wmf1 then in 1.20 master. One of ResourceLoader modules, defined by extension has the following dependency:
+
+			'dependencies' => 'mediawiki.jqueryMsg',
+
+The 'mediawiki.jqueryMsg' module and it's script is present in 1.18wmf1, 1.19, 1.20 master, but I was really surprised that in 1.18.2 it does not exists so the page scripts where my extension module is requested were broken with the following Chrome console errors:
+
+Uncaught Error: Unknown dependency: mediawiki.jqueryMsg load.php:9427
+Uncaught TypeError: Cannot read property 'options' of undefined GmapFunc:255
+Uncaught TypeError: Cannot read property 'tokens' of undefined GmapFunc:260
+
+Can I try to catch the client-side error in load.php? I don't know how. Instead, I implemented the following server-side method to check whether the dependent modules actually exists:
+
+	static protected function checkAllModulesExists() {
+		$allModules = array_keys( self::$mapModules );
+		foreach ( self::$mapModules as $moduleName => $moduleDefinition ) {
+			if ( !array_key_exists( 'dependencies', $moduleDefinition ) ) {
+				continue;
+			}
+			if ( is_array( $moduleDefinition['dependencies'] ) ) {
+				$allModules += $moduleDefinition['dependencies'];
+			} else {
+				# We do not check for multiple matches in values:
+				# it would only decrease performance in this case.
+				$allModules[] = $moduleDefinition['dependencies'];
+			}
+		}
+		$nonExistantModules = array_diff(
+			$allModules,
+			self::$out->getResourceLoader()->getModuleNames()
+		);
+		if ( count( $nonExistantModules ) > 0 ) {
+			throw new MWException( 'Cannot find requested module(s): ' .
+				implode( ',', $nonExistantModules ) .
+				' in ' . __METHOD__
+			);
+		}
+	}
+
+Which produces the following page message, at least (that is more informative than Chrome console message):
+
+Cannot find requested module(s): mediawiki.jqueryMsg in GMFn::checkAllModulesExists
+
+It would be nice if ResourceLoader itself checked the dependencies of added modules.
+
+--------------------------
+**Version**: 1.18.x
+**Severity**: normal
+**Whiteboard**: aklapper-moreinfo",1337677620,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-w23sfro3gylh7zauvhcz,task_description,declined
+ResourceLoader does not check dependencies for existance,"I see... Pity.
+As we cannot retest, closing as per comment 1.",1376496553,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"**questpc** wrote:
+
+Andre, MediaWiki is unpopular framework here in Russia. Our education system receives much smaller financing comparing to first world countries. Grants and charities are also very small, infrequent and hard to get. Non-commercial work is self-prohibitive because the life is expensive and wages are small (not in Moscow, at least). So I was not getting enough of freelancer MediaWiki job. Thus I was forced to move to Drupal then to my own framework. Sometimes I do small MediaWiki work but not so often and I lost deep knowledge of MediaWiki internals I had back in 1.15-1.17 times (API, FileRepo, early versions of ResourceLoader).
+
+But of course previous lack of good scripting and lack of VisualEditor also contributed to low popularity of MediaWiki here in Russia. Hope it will get more popular again.
+
+The site is now running 1.22wmf1. It was not my personal site but a freelancer job.",1368802542,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"(In reply to comment #1)
+> Modules can be dynamically registered. This should be checked in mediawiki.js
+> instead. I believe this has been fixed in 1.19 or 1.20, could you confirm?
+
+Dmitriy: Still running 1.18, or have you upgraded in the meantime?
+If the latter, cxould you answer above question?",1368800186,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"**questpc** wrote:
+
+I think Extension:UploadWizard also was using this module and it should be supported in 1.18.2 as well.
+
+Is there a graceful way of catching these errors at client side in 1.20? However, 1.20 includes the forementioned module.",1338185899,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"Modules can be dynamically registered. This should be checked in mediawiki.js instead.
+
+I believe this has been fixed in 1.19 or 1.20, could you confirm?",1338160804,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"NOTE: this request may be superseded by {T78046}.
+
+From bug 31406 comment 0:
+> A lot of work has gone into making it possible to use MathJax to view
+> TeX on Wikipedia.  Probably more than 20,000 article use TeX (or
+> whichever variant of TeX Wikipedia uses).  I have corresponded with
+> Robert Miner, MathJax Project Director and Vice President or Research
+> and Development at Design Science, Inc. about the fact that MathJax
+> could now be used.  I told him that possibly in coming months MathJax
+> would be adopted as the default means of viewing TeX on Wikipedia.
+
+As I understand it, Michael Hardy was proposing MathJax as the **default** math mode, but since setting $wgMathUseMathJax = true on Wikimedia wikis doesn't imply that it would be the default mode, I'm opening this bug to track what still needs to be done. This will also helps to separate the blockers of a ""experimental deployment"" (which is already done) and the blockers of a ""full deployment"" of MathJax on WMF wikis.
+
+If I understood it correctly, this would be the new setting:
+ $wgDefaultUserOptions['math'] = 2;
+
+Fell free to move some blockers/dependencies from bug 31406 to this one as needed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48036",1336073820,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-5os74s4qlwnokutpo36w,task_description,invalid
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"Please comment on that bug
+https://phabricator.wikimedia.org/T78046",1429892857,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),The only report currently marked as blocker is T37186 and is being discussed there. Going through the #Math component may find some more blockers.,1429892276,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),What's the status of this now? It's been a while since it was last discussed. Are the reasons to not use MathJax just as valid now?,1429891729,PHID-USER-oy47h3fy4yjggdu33qvo,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"**physik** wrote:
+
+In the meantime the situation has changed. So it might be better to create a new bug instead of updating this.",1413742990,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"A first good step might be to resolve bug 48036 (opt-in for unregistered visitors). That way, people can vote with their feet.",1373922516,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"**physik** wrote:
+
+(In reply to comment #9)
+> I think physikerwelt idea of semantic processing of mathematics is a nice
+> idea
+> and fit with the foundations wider goals. However it a bit off topic for this
+> bug. I've created a new bug 51381 which the details where it can be explored
+> in
+> more details.
+
+Thanks... sorry for the off topic... if I just said use
+ $wgDefaultUserOptions['math'] = 7
+that would be somehow pointless.
+By the way 2 is html (deprecated) and mathjax is 6.
+
+7 includes 6 since you it can be combined with MathJax (as you can see in the demo) but it must not. The advantage to use MathJax based on MathML is that it is reasonably fast. (To my mind that's not the case if you use MathJax without MathML). Furthermore you can display MathML without a need of JavaScript support.
+
+A visual editor that is based on MathML would be easier to implement and handle than one that is based on TeX. But I would double think about doing so, since than the Tex source is gone. (OK the same holds for the visual editor in general.)
+
+To stick to the topic, which is not visual editor:
+
+I fully support the initiative to switch the rendering mode.
+However, I think we should find a well defined process for doing so.
+One opportunity could be:
+1. Collect the alternatives
+2. Compare and benchmark them
+3. Discuss the results
+4. Make a decision (Maybe even vote oOo)
+
+This sounds a bit lengthy... but due to the fact that this bug is open for more than a year now... that might be really quick.",1373921609,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),I think physikerwelt idea of semantic processing of mathematics is a nice idea and fit with the foundations wider goals. However it a bit off topic for this bug. I've created a new bug 51381 which the details where it can be explored in more details.,1373912686,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"@Richard, the GSoC project for a math-editor component is coming along nicely. The approach is along the lines of the wyiswhat editor http://oerpub.github.io/Aloha-Editor/. The OERpub folks have done some testing (with regular school teachers) see http://kefletcher.blogspot.com/2013/05/testing-editor-designs.html. 
+
+@Martin I think texvc's restricted TeX fits very well within the concept of Wikitext and texvc has (unfortunatly) proven to be ""stable, secure and long term supported"". Of course I'm biased, but I think MathJax solves the issues you describe (well except the ominous ""along with all the JS issues"" -- not sure what you're referring to). If all you're after is MathML and SVG output, then the MathJax-driven VE plugin could easily produce those as well. 
+
+This is getting off topic, but I would add: we need more rather than less client-side rendering of scientific content. Server side rendering is inherently static, in fact, MathML (which is really just the math equivalent of text) feels a lot like HTML 1 at this point -- barely acceptable, static rendering in the browser. E.g., mathapedia and mathbox show what the future of math on the web might be.",1373911389,PHID-USER-nnhp4dmr6oozfejddbom,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"**physik** wrote:
+
+PS: There is a demo at 
+http://demo.formulasearchengine.com
+
+you can click on 
+http://demo.formulasearchengine.com/index.php/Special:Random
+
+to get a random page of the english wikipedia... the pages are not cached so it might take about 20 seconds, especially if images has to be loaded from commons",1373792662,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"**physik** wrote:
+
+I think it is really important to have a stable, secure, and long term supported way of math rendering.
+As I'm working on integrating LaTeXML a rendering engine that converts tex to MathML I was running into a couple of issues.
+First, Wikipedia uses texvc and not tex, therefore I had to create a list of special user defined commands. MathJax has this list as well.
+To my mind it's a suboptiomal solution especially with regard to long term support. I propose to come up with a grammar that can be used by a wide audience (e.g. antlr) and convert that into native php code. This grammar converts texvc to tex and eliminates all commands that are not allowed.
+Second, there are some security aspects, i.e. that someone could put code that is a potential security risk for the visitors. Texvc eliminates this security risk by       returning pictures only. On the other side as texvc is a potential security risk for the server, since the rendering must take place on the same machine as the core server works.
+LaTeXML can use a separate server, but if there is an attack to the network the traffic could be redirected to another server. Therefore the output of LaTeXML must be checked again before returning it to the users browser.
+If the users browser supports mathml only bugs in the browsers mathml implementation can be a security risk. If not MathJaX is needed to convert MathML to whatever, which comes along with all the Javascript issues.
+As a result I think that it would be good to seperate the tasks somehow.
+The Wikimedia Math extension php code should convert texvc to tex and ensure that only valid tex is passed to the rendering engine.
+Than a standard rendering engine can be used and the final result can be validated according to standard methods. e.g. validate MathML out against the W3C MathML scheme.
+In summer 2012 I proposed the LaTeXML render at CICM 2012, now it's avalible as opt-in[1].
+
+[1] http://arxiv.org/abs/1304.5475",1373791916,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"So we have a problem. We need to discuss maths on our talk page. Its a central part of building the encyclopedia. Now Flow is going to be introduced for our talk pages which will not allow standard wikicode as only the VisualEditor is allowed. Hence the VE must have math support, that is Bug 43058 must be fixed. 
+
+Now a maths visual editor is a herculanean task but central to that is a render. MathJax could potentially do it, texvc cannot as you would have generate a new image on the fly with each key stroke. Any other system is just going to be an ugly kludge. 
+
+In reply to Erik's comment. You have a tradeoff between the time it take javascript to render, with the time it takes to download all the images for the equations. It can take a considerable time to download a maths heavy page like Help:Formula. I would say they just about balance each other.",1373784725,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"(In reply to comment #3)
+> I don't think that this is likely to happen in the near future. MathJax is
+> significantly slower to render even on high end computers and would likely
+> cause unacceptable slowness on math-intense pages for users of low-end
+> machines.
+
+Just to mention one of the blocker bugs, it also has no localisation (bug 35038).
+
+> I'm inclined to close this as WONTFIX for the time being. I'd suggest looking
+> into ways to expose the MathJax user preference a bit more so that
+> math-interested users can discover it more easily. For example, we could
+> integrate the right-click menu that MathJax exposes with the PNG rendering
+> mode.
+
+Closing this per Erik (blocker bugs are easily overlooked, status is clearer to readers). Reopening is cheap when issues are solved.",1370592663,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"I don't think that this is likely to happen in the near future. MathJax is significantly slower to render even on high end computers and would likely cause unacceptable slowness on math-intense pages for users of low-end machines.
+
+I'm inclined to close this as WONTFIX for the time being. I'd suggest looking into ways to expose the MathJax user preference a bit more so that math-interested users can discover it more easily. For example, we could integrate the right-click menu that MathJax exposes with the PNG rendering mode.",1336522265,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"* Adding (open) bugs which are currently marked as blockers for bug 31406
+* Removing ""shell"" keyword for now, since the blockers would need to be fixed first",1336074752,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"PS: Remember that when MW 1.19 went live, it caused the default option ""HTML if very simple or else PNG"" to be replaced by ""Always render PNG"", and there were complains about that because the old default was better than PNG in some sense. So this bug would be the way to ""restore"" the previous ""better than PNG"" default.",1336074581,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+#mw-content-text is incorrectly placed on preview,"The id #mw-content-text, as I understand it, is normally attached to the .mw-content-ltr/rtl div so that the element directly holding the content is accessible through javascript. However, during preview, the ID is instead attached to a different element, which has #wikiPreview as a child element, which then has an ID-less (and thus inaccessible) .mw-content-ltr/rtl div holding the content. #mw-content-text should consistently be the content-holding div.
+
+--------------------------
+**Version**: 1.19
+**Severity**: normal",1336042080,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-e5n7wa77tt6s4carpjsv,task_description,resolved
+#mw-content-text is incorrectly placed on preview,"Looking at the preview page now, it has all the correct CSS rules applies. It inherits a `direction` from a `dir=""…""` element, and it is presented within an element that has `mw-content-ltr/rtl` classes applied.
+
+Is is still true today that this element does not have an ID of `#mw-content-text`. That element is elsewhere on the page, and has to be for compatibility with other code. It cannot be the same element because when previewing an edit, `#mw-content-text` is for the edit form (which is in your user language), whereas the `.mw-content-ltr#wikiPreview` element is for the page content (which is in the content language).
+
+These unfortunately cannot be the same.
+
+Focussing on the original use case, I believe you want to find the parts of the wiki content no matter whether it is a preview, oldid, or page view. Is that right? For that use case, we have `mw.hook('wikipage.content')` whicih will run for page views, previews, Live Preview, post-edit VisualEditor, Flow, Translate, Upload form, etc. anywhere where wikitext or templates may render.
+
+See [JS docs](https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.hook).
+",1588452442,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-e5n7wa77tt6s4carpjsv,task_subcomment,NA
+#mw-content-text is incorrectly placed on preview,"**alexsm333** wrote:
+
+Related issue (I think):
+
+API action=parse does not return div.mw-content-ltr
+so all ""ajax preview"" userscripts miss some global CSS,
+one example is "".mw-content-ltr .magnify {float: right}""
+for thumb images.",1337977920,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-e5n7wa77tt6s4carpjsv,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Raw TeX commands are displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1334738220,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_description,resolved
+MathJax doesn't work in LivePreview,"I see i forgot to close this one. This is basically working now, though there apparently is a bug, reported in T90808.",1424939822,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"For LivePreview, it depends on bug 24134 which isn't fixed yet, because I still need to finish https://gerrit.wikimedia.org/r/#/c/131346/. The patch that was merged was just one of the prerequisites. 
+
+VE is a separate issue.",1404905044,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,I just tested and it still doesn't seem to work (PNG images are shown).,1404903170,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Patch was merged a while ago - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?",1404896416,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Change 124064 merged by jenkins-bot:
+MathJax: Listen for wikipage.content hook
+
+https://gerrit.wikimedia.org/r/124064",1396886827,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Change 124064 had a related patch set uploaded by TheDJ:
+MathJax: Listen for wikipage.content hook
+
+https://gerrit.wikimedia.org/r/124064",1396718329,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"A specific problem is that after a session in VisualEditor a full refresh is not done and MathJax is not rerun, so the raw latex code is displayed. Apparently according to bug 51565 gadgets should listen to ""wikipage.content"". I have heard rumours that the fix to bug 48560 will fix this problem.
+
+This ha come up at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=593049936",1391069604,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Both Ajaxpreview and wikEd now use the renderTex() command to render MathJax in their ajax based preview modes:
+
+Example: https://en.wikipedia.org/w/index.php?title=User%3AJs%2Fpreview2.js&diff=558032369&oldid=520879456
+
+Soon to be improved by making use of https://gerrit.wikimedia.org/r/56762",1370210310,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"(For the record, there is now a fix in progress for bug 30713 which is a dependency here.)",1367254012,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,MathJax module now has a $().renderTex command that can be run to render domelements that contain tex commands. A preview hook can use this to postprocess the preview output.,1367143537,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Re-opening as this needs two things:
+* Be able to get modules loaded that extensions add to the page (bug 24134)
+* Be able to run code for ""article loaded"" when the article html is loaded. Usually this is document-ready which is how we do it now, but in case of preview we have multiple ""article loaded"" points within the lifecycle of a single page. This will be made possible by 30713.",1344752641,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"
+
+*** This bug has been marked as a duplicate of bug 24134 ***",1344752405,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"
+
+*** This bug has been marked as a duplicate of bug 33399 ***",1334802665,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"More or less the same as in bug 33399. If JavaScript features in LivePreview don't work for core features one can't expect it to work for extensions.
+A hook system as suggested in bug 23580 would be the best way to fix this bug.
+See also bug 35478.",1334742752,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+"VisualEditor: Backspace, cursor, among others not working in the insert link dialog","See title. Maybe it's due to handling the keydown event and return'ing false or preventing default, I don't know.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1333706040,PHID-USER-d2y3fvmumrowgb4efuvo,PHID-TASK-mo2gxuiaaf5jb54y7zdh,task_description,resolved
+"VisualEditor: Backspace, cursor, among others not working in the insert link dialog",Fixed in new version.,1340403895,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mo2gxuiaaf5jb54y7zdh,task_subcomment,NA
+"VisualEditor: Backspace, cursor, among others not working in the insert link dialog",Mass-moving items into VisualEditor product,1340402734,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mo2gxuiaaf5jb54y7zdh,task_subcomment,NA
+content-holding <div> should only contain the page text,"**Author:** `a.d.bergi`
+
+**Description:**
+The new bidirectionality-improving div should only contain the parsed page content, nothing else. This is perfect when viewing articles, and helps scripts a lot when extracting that content.
+
+But I think it is only needed for article views. For example in diff mode, it contains 
+```lang=html
+ <form id=""mw-fr-reviewform"">
+ <div id=""mw-fr-diff-headeritems"">
+ <table class=""diff"">
+ <hr class=""diff-hr""/>
+ <h2 class=""diff-currentversion-title"">
+```
+ ...and then the real content
+
+Also, in edit mode the `<div id=""mw-content-text"">` contains
+```lang=html
+ <div id=""editnotice-ns-0""/>
+ <div id=""mw-edit-longpage-hint"">
+ <div id=""wikiPreview"" class=""ontop"" style=""display: none;""/>
+ <form id=""editform"">
+```
+None of them is really content-text, I suspect. I think it would be better to have the div only appear (maybe empty) in the `#wikiPreview`.
+
+Also, it for example broke my script which tried to
+```lang=javascript
+document.getElementById(""bodyContent"").insertBefore(newElement, document.getElementById(""editform""));
+```",1331837760,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xad4cjfvysvak3tdxloe,task_description,resolved
+content-holding <div> should only contain the page text,"Thanks, that helps a lot. I wasn't even clear on what I should be looking for in the first place . and just found this task because it was mentioned in a comment somewhere possibly relevant...",1554995075,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#5102699, @Isarra wrote:
+> Can someone clarify for me if this is why ParserOptions::setWrapOutputClass() no longer takes 'false' as an option (this being the only sane way I could find to disable the entire wrapper when running parser->parse on a thing)?
+
+""This"" being what? This task is the reason that method exists in the first place. You can disable wrapping by using the `clearWrapperDivClass()` method or the `wrapperDivClass` option of the `getText()` method in ParserOutput.
+
+The reason false was deprecated is {T181846} (git blame is your friend...).",1554945467,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#5102699, @Isarra wrote:
+> Can someone clarify for me if this is why ParserOptions::setWrapOutputClass() no longer takes 'false' as an option (this being the only sane way I could find to disable the entire wrapper when running parser->parse on a thing)?
+
+""This"" being what? This task is the reason that method exists in the first place. You can disable wrapping by using the `clearWrapperDivClass()` method or the `wrapperDivClass` option of the `getText()` method in ParserOutput.",1554945368,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"And if this is why, this is the relevant patch that this is causing problems for: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CollaborationKit/+/502902 Is there some other way I should be doing this?
+Note that this isn't wikitext; merely contains arbitrary amounts of it.
+
+Or if this is the wrong thing, can someone point me to the correct task(s)?",1554932622,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Can someone clarify for me if this is why ParserOptions::setWrapOutputClass() no longer takes 'false' as an option (this being the only sane way I could find to disable the entire wrapper when running parser->parse on a thing)?
+
+I ask because I'm calling parser->parse on several things individually and we're just wrapping the final result in the relevant classes, and having each bit wrapped is causing other problems, but I can't figure out how to properly disable that now...",1554931704,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 352835 abandoned by Anomie:
+Add mw-parser-output to indicators container
+
+Reason:
+I'll let someone else figure out those details.
+
+[[https://gerrit.wikimedia.org/r/352835]]",1521477204,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVwNxIhIQMK9DA-FLPfy} [2017-05-15T20:20:02Z] <subbu> Updated Parsoid to a182c227 (T141226, T164792, T37247, T153107, T163091, T164006, T161151, T162920, T163549)",1494879605,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 352711 merged by jenkins-bot:
+[mediawiki/services/parsoid@master] Add mw-parser-output class to Parsoid's output
+
+[[https://gerrit.wikimedia.org/r/352711]]
+",1494425384,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 352835 had a related patch set uploaded (by Anomie; owner: Anomie):
+[mediawiki/core@master] Add mw-parser-output to indicators container
+
+[[https://gerrit.wikimedia.org/r/352835]]
+",1494339677,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"At svwiki we have
+  - https://sv.wikipedia.org/wiki/MediaWiki:Gadget-ProtectionIndicators.js 
+  - https://sv.wikipedia.org/wiki/MediaWiki:Gadget-GroupIndicators.js 
+  - https://sv.wikipedia.org/wiki/MediaWiki:Gadget-BlockIndicator.js
+to convey information about protected pages, groups and blocked users in a reliable way, unlike templates that anyone can add or remove. This is not user-generated content, so if you're going to do this, I would prefer if you can just wrap the individual indicators that come from the wikitext, not the container for all indicators.",1494280430,PHID-USER-2wcuxlzgvwfnnxqqqk67,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 352711 had a related patch set uploaded (by Subramanya Sastry; owner: Subramanya Sastry):
+[mediawiki/services/parsoid@master] Add mw-parser-output class to Parsoid's output
+
+[[https://gerrit.wikimedia.org/r/352711]]
+",1494279302,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Good question. I'd say yes, since indicators are user-generated content. It'd probably be a good idea to add the class to the indicators' wrapper element.",1494277050,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Here's a late annoying question – should contents of page status indicators (`<indicator name=""…""></indicator>` in wikitext; https://www.mediawiki.org/wiki/Help:Page_status_indicators) be wrapped in this new wrapper? ",1494276408,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#3181097, @Anomie wrote:
+> I don't know whether #VisualEditor and #Flow will get fixed up by that, though, or if they'll need some other work. I tried to set them up in mediawiki-vagrant, but neither actually functioned.
+
+Now that the patch is merged and on Beta Labs, I was able to confirm that neither VE's editing area nor Flow's comments are getting wrapped in the new class. Filed T164790 and T164791 for those extensions.",1494274545,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Note this won't be included in 1.30.0-wmf.1, but should be in 1.30.0-wmf.2.",1494273236,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350634 merged by jenkins-bot:
+[mediawiki/core@master] Wrap parser output in <div class=""mw-parser-output"">
+
+[[https://gerrit.wikimedia.org/r/350634]]
+",1494222103,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#3230407, @Krinkle wrote:
+> It's not clear to me why a separate class is needed here. How is `mw-parser-output` semantically different from `mw-body-content`?
+
+`.mw-body-content` includes a lot more than just the parser output, for example the edit form, the diff tables, and so on, and so wouldn't fix the complaints about those being affected by TemplateStyles.
+
+Also `.mw-body-content` is added by the skin. Of the 42 skins in extensions/skins, it looks like only 12 have any mention of it.[1] Of the skins on enwiki, Monobook and Vector have it while CologneBlue and Modern don't.
+
+[1]: Based on a grep for `mw-body-content`
+
+> I assume that `mw-parser-output` would solely be applied to output that literally comes from the parser, no exception.
+
+That's the plan.
+
+> 1. Is it valid for MediaWiki core interface styles and skin styles to ever target `mw-parser-output`? I propose no, they must use `mw-body-content` instead.
+
+I doubt there'd be reason for them to.
+
+> 2. Do we support outputting `mw-parser-output` on a MediaWiki-powered HTML response without being a descendant of `mw-body-content`? I propose no, an element with `mw-parser-output` must either also have `mw-body-content` or be a descendant of an element with that class.
+
+Since 70% of skins in Gerrit don't even wrap the main content of the page in `mw-body-content`, yes, we support that. I have no objection to someone deciding to fix that somehow, but let's not let it block this.
+
+> This leaves the question: What is the risk of allowing TemplateStyles to target `mw-body-content`?
+
+For affecting things it shouldn't affect, largely the same as it targeting `#mw-content-text` since in Monobook and Vector `#mw-content-text` is a child of `.mw-body-content`.
+
+For not affecting things is should affect, pretty large since 70% of skins in Gerrit don't wrap the main page content in that class.
+
+> The answer, as I understand it, is that we have some interface components (like page heading, categories, notices/banners, Translate extension controls, FlaggedRevs extension controls) that should be styled the same way as page content (e.g. their headings and links etc.) but don't always come straight out of the parser. And presumably we want to avoid these elements from being styled by a template on the current page.
+
+Yes, that seems accurate.
+
+> * Would it be appropiate to instead have these common styles use `mw-body` instead of `mw-body-content` in their CSS? E.g. for skin headings, links etc. Thus turning mw-body-content into the proposed `mw-parser-output`.
+
+Only if we kill `mw-body-content` from all skins and start adding it in core in the way the current patch adds `mw-parser-output`. I'd rather pick a new name than try to make major changes to an old one.
+
+Again, `mw-body` is added by skins. It looks like 15 of 42 skins in Gerrit don't add it, but all four of the skins on enwiki do.[2]
+
+[2]: Based on a grep for `mw-body($|[^a-z-])`
+
+> * Given that firstHeading is partially provided by Parser. And banners are entirely parsed by the parser. Will the class name apply there?
+
+Currently, it is not applied to firstHeading. I don't have banners on my local wiki to test, but if they use `Parser::parse()` rather than something like `Message::parse()` they would. Or whatever generates the banner could always add the wrapper itself if necessary.
+
+> If yes, then the current page has the ability to affect the notices, which are supposed to be restricted. If not, then notices cannot use templates properly. Perhaps it makes sense to have mw-parser-output be a dynamically generated class instead of a fixed name (e.g. mw-parser-output-123), so that TemplateStyles can be restricted to the correct context only?
+
+Hmm, that's not a bad idea. OTOH, callers that didn't want the default `mw-parser-output` could always use `ParserOptions->setWrapOutputClass()` to set something else.
+
+> * Besides elements provided by the parser (first heading, and site notices), is there a problem with moving the Translate and FlaggedRevs extension controls out of mw-body-content? Or more specifically, is there a problem with removing mw-body-content from `#bodyContent` in Vector and instead applying it to the relevant child nodes only?
+
+Just that it would be a major redefinition of what exactly `.mw-body-content` applies to.",1493824662,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"It's not clear to me why a separate class is needed here. How is `mw-parser-output` semantically different from `mw-body-content`?
+
+I assume that `mw-parser-output` would solely be applied to output that literally comes from the parser, no exception. However while that is a clear use case, the use case for styling that output seems slightly wider. Because the purpose of `mw-body-content` right now is for anything that is meant to be styled the same way as page content.
+
+While these are different technical purposes, I'd like to make sure we avoid cases where one set `mw-parser-output` to mimic certain styles, or alternatively where one would have to target both in CSS to make sure it always applies.
+
+A few questions to help narrow it down:
+
+1. Is it valid for MediaWiki core interface styles and skin styles to ever target `mw-parser-output`? I propose no, they must use `mw-body-content` instead.
+2. Do we support outputting `mw-parser-output` on a MediaWiki-powered HTML response without being a descendant of `mw-body-content`? I propose no, an element with `mw-parser-output` must either also have `mw-body-content` or be a descendant of an element with that class.
+
+This leaves the question: What is the risk of allowing TemplateStyles to target `mw-body-content`? The answer, as I understand it, is that we have some interface components (like page heading, categories, notices/banners, Translate extension controls, FlaggedRevs extension controls) that should be styled the same way as page content (e.g. their headings and links etc.) but don't always come straight out of the parser. And presumably we want to avoid these elements from being styled by a template on the current page.
+
+In that case I have a few more questions:
+
+* Would it be appropiate to instead have these common styles use `mw-body` instead of `mw-body-content` in their CSS? E.g. for skin headings, links etc. Thus turning mw-body-content into the proposed `mw-parser-output`. One problem with this is that Parsoid prefers to only use mw-body-content, and not mw-body, and still load Vector styles and have a page that looks like it was cut out from a Vector-skin page view but without the skin wrapping. Applying mw-body has the side effect of needlessly reserving space for the sidebar and such. Although it would be trivial to fix Vector to move these styles to a vector-specific class name on the same element since strictly speaking this should not have been applied to mw-body in the first place.
+
+* Given that firstHeading is partially provided by Parser. And banners are entirely parsed by the parser. Will the class name apply there? If yes, then the current page has the ability to affect the notices, which are supposed to be restricted. If not, then notices cannot use templates properly. Perhaps it makes sense to have mw-parser-output be a dynamically generated class instead of a fixed name (e.g. mw-parser-output-123), so that TemplateStyles can be restricted to the correct context only?
+
+* Besides elements provided by the parser (first heading, and site notices), is there a problem with moving the Translate and FlaggedRevs extension controls out of mw-body-content? Or more specifically, is there a problem with removing mw-body-content from `#bodyContent` in Vector and instead applying it to the relevant child nodes only?",1493780638,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"It's not clear to me why a separate class is needed here. How is `mw-parser-output` semantically different from `mw-body-content`?
+
+I assume that `mw-parser-output` would solely be applied to output that literally comes from the parser, no exception. However while that is a clear use case, the use case for styling that output seems slightly wider. Because the purpose of `mw-body-content` right now is for anything that is meant to be styled the same way as page content.
+
+While these are different technical purposes, I'd like to make sure we avoid cases where one set `mw-parser-output` to mimic certain styles, or alternatively where one would have to target both in CSS to make sure it always applies.
+
+A few questions to help narrow it down:
+
+1. Is it valid for MediaWiki core interface styles and skin styles to ever target `mw-parser-output`? I propose no, they must use `mw-body-content` instead.
+2. Do we support outputting `mw-parser-output` on a MediaWiki-powered HTML response without being a descendant of `mw-body-content`? I propose no, an element with `mw-parser-output` must either also have `mw-body-content` or be a descendant of an element with that class.
+
+This leaves the question: What is the risk of allowing TemplateStyles to target `mw-body-content`? The answer, as I understand it, is that we have some interface components (like page heading, categories, notices/banners, Translate extension controls, FlaggedRevs extension controls) that should be styled the same way as page content (e.g. their headings and links etc.) but don't always come straight out of the parser. And presumably we want to avoid these elements from being styled by a template on the current page.
+
+In that case I have a few more questions:
+
+* Would it be appropiate to instead have these common styles use `mw-body` instead of `mw-body-content` in their CSS? E.g. for skin headings, links etc. Thus turning mw-body-content into the proposed `mw-parser-output`. One problem with this is that Parsoid prefers to only use mw-body-content, and not mw-body, and still load Vector styles and have a page that looks like it was cut out from a Vector-skin page view but without the skin wrapping. Applying mw-body has the side effect of needlessly reserving space for the sidebar and such. Although it would be trivial to fix Vector to move these styles to a vector-specific class name on the same element since strictly speaking this should not have been applied to mw-body in the first place.
+
+* Given that firstHeading is partially provided by Parser. And banners are entirely parsed by the parser. Will the class name apply there? If yes, then the current page has the ability to affect the notices, which are supposed to be restricted. If not, then notices cannot use templates properly.
+
+* Besides elements provided by the parser (first heading, and site notices), is there a problem with moving the Translate and FlaggedRevs extension controls out of mw-body-content? Or more specifically, is there a problem with removing mw-body-content from `#bodyContent` in Vector and instead applying it to the relevant child nodes only?",1493780529,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350635 merged by jenkins-bot:
+[mediawiki/extensions/MobileFrontend@master] Update tests for core change If4eb5bf7
+
+[[https://gerrit.wikimedia.org/r/350635]]
+",1493750516,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#3219054, @dr0ptp4kt wrote:
+> you most likely want to double check that CSS selector expressions keep working in reading and, to the extent they're employed in the experiences you engineer, editing contexts. There may be no problem, but I would be remiss to not note it.
+
+As far as selectors, you're probably good unless you're using the direct-decendent `>` selector. Potentially more interesting would be things like MobileFrontend that try to chop up the parser output (although for MobileFrontend specifically I already submitted [[https://gerrit.wikimedia.org/r/#/c/350635/|this patch]]).",1493326380,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Yeah, ok, thanks.",1493326352,PHID-USER-2wcuxlzgvwfnnxqqqk67,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Flow or anything else that might want to put two ""pages"" of content in one HTML document. For example, a side-by-side comparison of the rendered text might make sense somewhere, maybe for translation or something.",1493326250,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,Does it have to be a class (instead of an id) because of Flow?,1493325907,PHID-USER-2wcuxlzgvwfnnxqqqk67,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350636 merged by jenkins-bot:
+[mediawiki/extensions/Wikibase@master] Update tests for core change If4eb5bf7
+
+[[https://gerrit.wikimedia.org/r/350636]]
+",1493324256,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Adding @bearND, @Mholloway, @JoeWalsh, @Jdlrobson, @MarkTraceur for visibility - you most likely want to double check that CSS selector expressions keep working in reading and, to the extent they're employed in the experiences you engineer, editing contexts. There may be no problem, but I would be remiss to not note it.
+
+CC @Fjalapeno",1493322933,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350636 had a related patch set uploaded (by Anomie; owner: Anomie):
+[mediawiki/extensions/Wikibase@master] Update tests for core change If4eb5bf7
+
+[[https://gerrit.wikimedia.org/r/350636]]
+",1493318866,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350635 had a related patch set uploaded (by Anomie; owner: Anomie):
+[mediawiki/extensions/MobileFrontend@master] Update tests for core change If4eb5bf7
+
+[[https://gerrit.wikimedia.org/r/350635]]
+",1493318862,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350634 had a related patch set uploaded (by Anomie; owner: Anomie):
+[mediawiki/core@master] Wrap parser output in <div class=""mw-parser-output"">
+
+[[https://gerrit.wikimedia.org/r/350634]]
+",1493318859,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Maybe you could have a ParserOption for it, so that the parser tests can still pass without too much trouble? Have the wrapper be on by default, but turn it off for parser tests. Other than that, I think it should be fine to add it to Parser::parse(). Write the patch and we'll see what happens.",1493270839,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"I've become interested in this thanks to TemplateStyles. Currently, TemplateStyles scopes all styles to the `id=""mw-content-text""` element to prevent styles from accidentally messing with site UI. I just now loaded a random page in VE and noticed that its content being edited is not within that element, so the template styles won't be applied in the editor. This isn't good.
+
+At the same time, we have this bug complaining that the `id=""mw-content-text""` element sometimes contains more than just the page output, for example it contains the diff tables, the edit form, category text, image metadata, and so on. The `mw-content-ltr` and `mw-content-rtl` classes mentioned here do slightly better, they don't hold the diff tables but do hold parts of category lists, the entire Flow page, and so on. And having to target multiple classes would bloat TemplateStyles's output.
+
+It looks like the most straightforward option to getting just the parser output to be wrapped in some sort of container is to do just that: stick some code like this in near [[https://phabricator.wikimedia.org/source/mediawiki/browse/master/includes/parser/Parser.php;d038e889f72d17bbf03d2098111c928571c2c72d$592|this line in the Parser]]:
+``` lang=php
+        # Wrap non-interface ParserOutput in a class
+        if ( !$this->mOptions->getInterfaceMessage() ) {
+            $text = Html::rawElement( 'div', [ 'class' => 'mw-parser-output' ], $text );
+        }
+```
+I don't know whether #VisualEditor and #Flow will get fixed up by that, though, or if they'll need some other work. I tried to set them up in mediawiki-vagrant, but neither actually functioned.
+
+
+If we don't do that, we may be able to get by with a few more changes where ParserOutput is used.
+* `OutputPage::addParserOutputText()`, either before or after the 'OutputPageBeforeHTML' hook call, will catch most cases.
+** We'll probably need to copy the interface flag into the ParserOutput so that can only wrap the non-interface ParserOutputs.
+* `EditPage::doPreviewParse()` needs to wrap its HTML too.
+* Possibly the ""Empty content container for LivePreview"" in `EditPage::displayPreviewArea()` should have the class added.
+* `TemplateSandbox::templateSandboxPreview()` where it basically duplicates `EditPage::getPreviewText()`
+* `Translate::getDocumentationBox()` where it displays the qqq message
+* Wherever in Flow that it generates the `flow-post-content` div.
+* VisualEditor would probably need to add the class to its wrapper div, probably the same one that already has the 'mw-content-ltr' class.",1492117803,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"**a.d.bergi** wrote:
+
+> > Also, it for example broke my script which tried to
+> >  document.getElementById(""bodyContent"").insertBefore(newElement,
+> > document.getElementById(""editform""));
+> 
+> Please elaborate what you mean here.
+
+I have a script that inserted some edit tools into #bodyContent, right before #editform. Since r111647 that doesn't work, as #editform now is a child of #mw-content-text.
+
+OK, it was a minor issue and very easy to fix. I only wanted to mention that some tools may be broken that make assumptions about the child nodes of mw.util.$content, which might be quite common.",1332166667,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"(In reply to comment #0)
+> Also, it for example broke my script which tried to
+>  document.getElementById(""bodyContent"").insertBefore(newElement,document.getElementById(""editform""));
+
+Please elaborate what you mean here.",1467403389,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"(In reply to comment #0)
+> Also, it for example broke my script which tried to
+>  document.getElementById(""bodyContent"").insertBefore(newElement,
+> document.getElementById(""editform""));
+
+Please elaborate what you mean here.",1332165373,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+"VisualEditor: Undoing ""Clear formatting"" does not work","Clicking ""Undo"" after using the ""Clear formatting"" button does not work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1330562220,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-oeyka3jairvoviqejllv,task_description,resolved
+"VisualEditor: Undoing ""Clear formatting"" does not work",Mass-moving items into VisualEditor product,1340402754,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oeyka3jairvoviqejllv,task_subcomment,NA
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,"* Open up https://test.wikipedia.org/wiki/Special:VisualEditorSandbox
+* click-and-drag to select...
+* ...keep dragging down to the bottom of the window and beyond
+
+Expected behavior:
+Document should scroll so we can keep selecting stuff.
+
+Actual behavior:
+Document does not scroll; cannot select anything further by mouse.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://test.wikipedia.org/wiki/Special:VisualEditorSandbox
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51669",1328824440,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-voh6lpuq6qwl3jpaliry,task_description,resolved
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,Noting bugs closed in the 2012-10-15 release.,1351534198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-voh6lpuq6qwl3jpaliry,task_subcomment,NA
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341855,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-voh6lpuq6qwl3jpaliry,task_subcomment,NA
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,Fixed with new version of VE (built-in behaviour).,1340401398,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-voh6lpuq6qwl3jpaliry,task_subcomment,NA
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,We had this working in a demo before. I know it can be done with the document.onmousemove events we get.,1329154427,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-voh6lpuq6qwl3jpaliry,task_subcomment,NA
+Window resizing crashes VisualEditor if too small,"In certain browsers (including Chrome and IE9), if one resizes the window to smaller than a certain size, the VisualEditor will crash.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1328532960,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-47m3opkl4tk6r424d6ee,task_description,resolved
+Window resizing crashes VisualEditor if too small,Noting bugs closed in the 2012-10-15 release.,1351534204,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-47m3opkl4tk6r424d6ee,task_subcomment,NA
+Window resizing crashes VisualEditor if too small,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341861,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-47m3opkl4tk6r424d6ee,task_subcomment,NA
+Window resizing crashes VisualEditor if too small,Fixed with new version of VE (built-in behaviour).,1340401269,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-47m3opkl4tk6r424d6ee,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"**Author:** `aokomoriuta`
+
+**Description:**
+When I don't have skipcaptcha right, page translation with external link got error.
+Can we pass CAPTCHA test in translation function?",1328258040,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_description,open
+Special:Translate unable to save where CAPTCHA is required,"For searchers: this bug often comes with ""Saving the translation failed: The modification you tried to make was aborted by an extension hook"" warnings.
+https://www.mediawiki.org/wiki/Thread:Extension_talk:Translate/_%27Saving_the_translation_failed:_The_modification_you_tried_to_make_was_aborted_by_an_extension_hook%27_and_Documentation_problems/reply
+https://www.mediawiki.org/w/index.php?title=Help%3AExtension%3ATranslate%2FConfiguration&diff=1236716&oldid=1229427",1414140259,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,ContentTranslation implemented a (after the fact) solution: https://gerrit.wikimedia.org/r/#/c/146426/,1405494153,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"If this works only with FancyCaptcha, this is already a good start.",1380581640,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"(In reply to comment #9)
+> So, it seems it's possible to deal with with the extension:ConfirmEdit
+> through
+> the API:
+> https://bugzilla.wikimedia.org/show_bug.cgi?id=50356#c3
+
+Note, that comment mentions only FancyCaptcha [which is the least used component of ConfirmEdit: few wikis other than WMF use it].",1378369248,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"So, it seems it's possible to deal with with the extension:ConfirmEdit through the API:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50356#c3
+
+Would that be possible for extension:Translate to deal with it?",1378368406,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"(In reply to comment #7)
+> I'm also impacted by this issue and I agree, if the API does not provide the
+> necessary tools then it seems to me complicated to deal with this. How does
+> the
+> VisualEditor? He is impacted?
+
+It was: bug 50356 / https://gerrit.wikimedia.org/r/#/c/71160/ .",1378366693,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"I'm also impacted by this issue and I agree, if the API does not provide the necessary tools then it seems to me complicated to deal with this. How does the VisualEditor? He is impacted?",1378365600,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,*** Bug 42161 has been marked as a duplicate of this bug. ***,1353012086,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"ConfirmEdit can be configured per namespace, you can just disable it on translations: namespace with $wgCaptchaTriggersOnNamespace as a (partial) workaround?",1328450883,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"**qbphcqdw** wrote:
+
+%%%*** Bug 34197 has been marked as a duplicate of this bug. ***%%%",1328365291,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,It is not easy to fix since all edits go through the API through normal saving mechanism.,1328329139,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"**aokomoriuta** wrote:
+
+To avoid this error, I can edit the message directly (Translating:XXX) instead of editing through Special:Translate.
+So as First Aid, it seems good to modify the error message in Special:Translate ""Saving failed. Please report this error."" to ""You need edit this message directly to pass CAPTCHA."".",1328272304,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"Nice find. Will look into this. To avoid actual spamming, I think we should only allow this if there are no warnings on the translation, ie changed links that would cause fuzzy markings.",1328261459,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Spell check not working in VisualEditor interface,"**Author:** `utsavsabharwal`
+
+**Description:**
+I wrote following line and was expecting the editor to help me with the spell of gud and notify me about invalid word 'Yra' but it dint :(
+
+""Yra Utsav is gud boy ""
+
+I am using Chromium 15.0.874.106 (Developer Build 107270 Linux) Ubuntu 11.10
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1325686140,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-arr3l5eisybqnti6pj5e,task_description,resolved
+Spell check not working in VisualEditor interface,Noting bugs closed in the 2012-10-15 release.,1351534201,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341859,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,Fixed with new version of VE (built-in behaviour).,1340398658,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,"(In reply to comment #1)
+> Browser's native spell checker probably won't work with visual editor...
+
+Is this still the case?",1340395213,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,"**utsavsabharwal** wrote:
+
+Is there any possible way user can check for spells while using VE?",1325711769,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,Browser's native spell checker probably won't work with visual editor...,1325704678,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","See URL for an example.
+
+Revision 97771495 is flagged as ""automatically checked"" though the previous version isn't. I think this is what happened:
+
+1. The base version is the version from 17:14 (CET), a flagged version.
+2. Elmar Nolte (with autoreview right) starts to edit.
+3. The IP starts to edit and saves first. The revision is not flagged.
+4. Elmar Nolte saves. The software detects an edit conflict which is resolved automatically. So no warning is shown. The FR extension still sees this edit based on the previous flagged version and flags the new revision as automatically checked.
+
+But in fact Elmar Nolte's revision is based on the unflagged revision by the IP and should not be flagged automatically.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://de.wikipedia.org/w/index.php?title=Emanuel_Semper&action=history&uselang=en",1325581020,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-sx2ogxi3akejlbpibw6h,task_description,resolved
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","Change 72265 merged by Demon:
+Various edit conflict handling fixes
+
+https://gerrit.wikimedia.org/r/72265",1374014464,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","Change 72265 had a related patch set uploaded by Aaron Schulz:
+Various edit conflict handling fixes
+
+https://gerrit.wikimedia.org/r/72265",1373136660,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","Neither edit is tagged as such, so no.",1373096935,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict",Does this require VisualEditor to reproduce?,1373095980,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","Reopening: This happened again in https://de.wikipedia.org/w/index.php?title=Allgemeines_b%C3%BCrgerliches_Gesetzbuch&action=history
+
+There are three relevant edits (all times in CEST):
+
+(1) IP at 20:42:00
+(2) IP at 20:42:31
+(3) Botulph at 20:42:49
+
+Edit (3) was started after (1), but before (2), and is just a revert of edit (1) via the ""undo"" function. The edit conflict with edit (2) was automatically resolved, but (3) was automatically checked, though of course it shouldn't.",1373095755,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","(In reply to comment #4)
+> Are there any other known instances?
+
+I tried to reproduce it on http://de.wikipedia.beta.wmflabs.org/w/index.php?title=Testseite&action=history, but apart from the fact that at first my login cookie get lost everything worked as expected. So I'm closing this bug for now.",1329122473,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict",Are there any other known instances?,1328915576,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","(In reply to comment #2)
+> Was Elmar editing the page for 55+ seconds for such a small change? I suppose
+> it's possible.
+
+I think 55+ seconds for: starting link dialog from WikiEditor, messing around, inserting the link, clicking preview, testing the link, wondering why it doesn't work, deciding to save anyway is not very long, so definitely possible.",1326098197,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","(cur | prev) 2011-12-31T16:16:56‎ Elmar Nolte (Talk | contribs)‎ (1,701 bytes) (undo) [automatically checked]
+(cur | prev) 2011-12-31T16:16:01‎ 91.39.161.225 (Talk)‎ (1,542 bytes) (kat, nd, pd) (undo)
+(cur | prev) 2011-12-31T16:14:59‎ Elmar Nolte (Talk | contribs)‎ (1,162 bytes) (undo) [automatically checked]
+
+Was Elmar editing the page for 55+ seconds for such a small change? I suppose it's possible.",1326091809,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict",maybeMakeEditReviewed() already checks for this (https://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/FlaggedRevs/backend/FlaggedRevs.hooks.php?revision=106746&view=markup). I'm not sure how this can happen.,1326072983,PHID-USER-bmbmvb2e5bg6ztcangbq,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"- it is documented at [[ https://www.mediawiki.org/wiki/Repositories_with_Ruby_code | Repositories with Ruby code ]] page?
+- is ruby syntax check running after every commit?
+- is rubocop  running after every commit?
+- is browser test jenkins job created? (optional)
+
+Repositories:
+
+gerrit
+
+|name|ruby|rubocop|
+|mediawiki/core|1.9.3|0.32.1|
+|mediawiki/extensions/ArticleFeedbackv5|1.9.3|0.26.1|
+|mediawiki/extensions/CentralAuth|1.9.3|0.29.1|
+|mediawiki/extensions/CentralNotice|1.9.3|0.29.1|
+|mediawiki/extensions/CirrusSearch|1.9.3|0.26.1|
+|mediawiki/extensions/ContentTranslation|1.9.3|0.29.1|
+|mediawiki/extensions/Echo|1.9.3|0.29.0|
+|mediawiki/extensions/Flow|1.9.3|0.32.1|
+|mediawiki/extensions/Gather|1.9.3|0.34.1|
+|mediawiki/extensions/GettingStarted|1.9.3|0.29.1|
+|mediawiki/extensions/Math|1.9.3|0.27.0|
+|mediawiki/extensions/MobileFrontend|1.9.3|0.29.1|
+|mediawiki/extensions/MultimediaViewer|1.9.3|0.29.1|
+|mediawiki/extensions/PageTriage|1.9.3|0.26.1|
+|mediawiki/extensions/PdfHandler|1.9.3|0.26.1|
+|mediawiki/extensions/PoolCounter|1.9.3|0.27.1|
+|mediawiki/extensions/QuickSurveys|1.9.3|0.29.1|
+|mediawiki/extensions/Translate|1.9.3|0.26.1|
+|mediawiki/extensions/TwnMainPage|1.9.3|0.26.1|
+|mediawiki/extensions/UniversalLanguageSelector|1.9.3|0.29.1|
+|mediawiki/extensions/UploadWizard|1.9.3|0.29.1|
+|mediawiki/extensions/VisualEditor|1.9.3|0.32.1|
+|mediawiki/extensions/WikiLove|1.9.3|0.26.1|
+|mediawiki/extensions/ZeroBanner|1.9.3|0.26.1|
+|mediawiki/extensions/ZeroPortal|1.9.3|0.26.1|
+|mediawiki/ruby/api|1.9.3|0.29.1|
+|mediawiki/selenium|1.9.3|0.29.1|
+|mediawiki/vagrant|1.9.3|0.33.0|
+|oojs/ui|2.0|0.27.1|
+|operations/puppet|1.9.3|0.33.0|
+|VisualEditor/VisualEditor|1.9.3|0.29.1|
+
+github
+
+|name|ruby|rubocop|
+|amire80/commons_upload|2.2.0|0.33|
+|amire80/screenshot.git|2.2.0|?|
+|wmde/WikidataApiGem|1.9.3|-|
+|wmde/WikidataBrowserTests|1.9.3|0.32.1|",1416490011,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_description,resolved
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237373 merged by jenkins-bot:
+Run Ruby syntax check for mediawiki/vagrant in experimental pipeline
+
+[[https://gerrit.wikimedia.org/r/237373]]",1442085611,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237375 merged by jenkins-bot:
+Run Ruby syntax check for operations/puppet in experimental pipeline
+
+[[https://gerrit.wikimedia.org/r/237375]]",1442085294,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237638 merged by jenkins-bot:
+Ruby Ruby syntax check and RuboCop for PoolCounter
+
+[[https://gerrit.wikimedia.org/r/237638]]",1442084457,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237638 had a related patch set uploaded (by Zfilipin):
+Ruby Ruby syntax check and RuboCop for PoolCounter
+
+[[https://gerrit.wikimedia.org/r/237638]]
+",1441974783,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237375 had a related patch set uploaded (by Zfilipin):
+Run Ruby syntax check for operations/puppet in experimental pipeline
+
+[[https://gerrit.wikimedia.org/r/237375]]
+",1441893216,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237373 had a related patch set uploaded (by Zfilipin):
+Run Ruby syntax check for mediawiki/vagrant in experimental pipeline
+
+[[https://gerrit.wikimedia.org/r/237373]]
+",1441892621,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 200863 abandoned by Zfilipin:
+WIP Run Ruby syntax check and/or RuboCop for repositories with Ruby code
+
+[[https://gerrit.wikimedia.org/r/200863]]",1441891623,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,,1442423278,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,,1428487153,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 200863 had a related patch set uploaded (by Zfilipin):
+WIP Ruby Ruby syntax check and/or RuboCop for repositories with Ruby code
+
+[[https://gerrit.wikimedia.org/r/200863]]
+",1427811423,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Feel free to add a step by step tutorial for ruby repositories, we have a few already: https://www.mediawiki.org/wiki/Continuous_integration/Tutorials . ",1427809449,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,"At the moment, we have a couple of jenkins jobs:
+
+  - [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-VisualEditor-language-screenshot-linux-firefox/ | browsertests-VisualEditor-language-screenshot-linux-firefox ]]
+  - [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-VisualEditor-language-screenshot-linux-firefox-sauce/ | browsertests-VisualEditor-language-screenshot-linux-firefox-sauce ]]
+
+The first job runs local firefox and fails randomly.
+
+Options:
+
+- check if any of the headless environment variables helps
+- check if any of the reuse browser environment variables helps
+- check if switching to local chromium helps
+
+The second job run a remote browser on sauce labs, but it does not support Chinese and Japanese fonts (at least), but only on linux host.
+
+- check if running the job on windows (or mac) helps.",1416327470,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tig5qf53lxx7q22k3ipg,task_description,resolved
+browsertests-VisualEditor-language-screenshot jenkins job failing,"It was moved to run on Mac, and now runs successfully.",1424769575,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,"Some more context:
+
+Already reported as [bug 71602 - mediawiki_selenium always use the same default xvfb display 99](https://bugzilla.wikimedia.org/show_bug.cgi?id=71602), which explains how our jobs ends up killing each other XVFB (typical race condition).
+
+Dan fixed it with https://gerrit.wikimedia.org/r/#/c/164704/ ( b6af34a40e ) which is included in mediawiki_selenium 0.4.1.
+
+The jobs need to be bumped to that library version and use the appropriate env variables as described above.",1416479930,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,"The job has `BROWSER=firefox` and `HEADLESS=false`, I am not sure what happens exactly in some case.  We probably want to set `HEADLESS=true` and set HEADLESS* env variables to avoid killing the XVFB.
+
+The relevant code for 0.4.1 is:
+
+http://git.wikimedia.org/blob/mediawiki%2Fselenium/0.4.1/lib%2Fmediawiki_selenium%2Fsupport%2Fhooks.rb#L27
+
+See also the `README.md` doc under ""Headless mode"" section: http://git.wikimedia.org/blob/mediawiki%2Fselenium/0.4.1/README.md
+
+I think we want:
+
+```
+lang=sh
+HEADLESS=true
+HEADLESS_DESTROY_AT_EXIT=false
+```
+
+That will default to use display 99, we have an XVFB listening on 99 already.
+
+If we want the headless gem to spawn a new xvfb on a different display port, we can use `HEADLESS_REUSE=false` which will make it spawn a new xvfb on a different display port.  But that is probably not needed.",1416479618,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,">>! In T1321#23186, @hashar wrote:
+> Can you confirm you have mediawiki_selenium 0.4.1 +
+
+Yes.
+
+```
+00:03:37.335 Installing mediawiki_selenium 0.4.1
+00:03:37.335 0:  mediawiki_selenium (0.4.1) from /mnt/jenkins-workspace/workspace/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/LANGUAGE_SCREENSHOT_CODE/ar/label/gems/2.0.0/specifications/mediawiki_selenium-0.4.1.gemspec
+```
+
+From:
+
+https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/LANGUAGE_SCREENSHOT_CODE=ar,label=contintLabsSlave%20&&%20UbuntuTrusty/1/console
+",1416477168,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,Related commit: https://gerrit.wikimedia.org/r/#/c/174660/,1416476604,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,"Can you confirm you have mediawiki_selenium 0.4.1 +
+
+And:
+
+    export HEADLESS_DESTROY_AT_EXIT=false
+
+See https://bugzilla.wikimedia.org/show_bug.cgi?id=71602#c6",1416332893,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"It's not immediately clear which projects should be in the actual message. As things are looking now, just team and project is OK, but maybe tags should also be added.
+
+See https://github.com/legoktm/wikibugs2/commit/f2d91f6e6a1d8ccba54041d3376ed7719585c8d3 -- all tags should be reported to the IRC bot, not just projects.
+
+
+See also:
+ -  T1209 - Add 'team' (purple) to output
+ - T1122 - Don't include closed projects in wikibugs2 output",1416306634,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_description,resolved
+Team (and other non-project) tags should be available for filtering,{icon umbrella},1423341471,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"Change 184864 merged by jenkins-bot:
+Disentangle tag lists for filtering vs display
+
+[[https://gerrit.wikimedia.org/r/184864]]",1421233290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"Change 184864 had a related patch set uploaded (by Yuvipanda):
+Disentangle tag lists for filtering vs display
+
+[[https://gerrit.wikimedia.org/r/184864]]
+
+#patch-for-review",1421229729,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"VE now works, thanks.",1418937435,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"Change 179088 merged by jenkins-bot:
+T1316: Also report {icon umbrella} projects
+
+[[https://gerrit.wikimedia.org/r/179088]]",1418755053,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"Change 179088 had a related patch set uploaded (by Merlijn van Deen):
+T1316: Also report {icon umbrella} projects
+
+[[https://gerrit.wikimedia.org/r/179088]]
+
+#patch-for-review",1418283449,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,Argh. Should we remove the umbrella for now?,1418252786,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,I have been told that this is what causes tasks in #VisualEditor not to be reported on #mediawiki-visualeditor since the project has gained the umbrella icon. What do we do to fix that?,1418251394,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"> ...but should not be reported in-channel in the channel list.
+
+As said in my comment above, if you filter out tasks belonging to Team projects, it is likely that you will miss many tasks. ",1417376464,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"As discussed on IRC, I see no reason why ""team"" type of projects cannot be used to handle tasks themselves, and I see no reason to treat them differently than ""suitcase"" projects. If we don't use team projects for managing the team backlog, then the only reason to create a team project would be to handle some special permissions.",1416308316,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"We don't have any real need for 1.23wmf* and 1.24wmf* deployment branches anymore. They should probably be changed to tags.
+
+Chad, do you have a script for doing this? Timo seemed to think you had from before...
+
+-----
+**EDIT**: Krinkle used the following script for individual repositories at [https://github.com/Krinkle/dotfiles/tree/master/hosts/KrinkleMac/bin](https://github.com/Krinkle/dotfiles/tree/db0e65f/hosts/KrinkleMac/bin):
+{P3455}
+{P531}",1416143148,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-f7bxhifsd4lp32e2eisz,task_description,resolved
+Remove old wmf/* deployment branches (recurring chore),This is done.,1494861695,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),So I think the last thing to do here is to automate this a bit. I'm going to add it to `scap clean`,1486674812,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),,1486674758,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),,1468868164,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Done for all extensions, skins and vendor. No more extraneous tags. No more branches other than the currently active series, `1.28.0-wmf.N`",1468544824,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"I agree, all those old tags and branches aren't very useful after a while.",1468527573,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"One liner for all extensions and skins meta repos:
+```
+lang=bash
+# Delete all remote branches matching wmf/ that aren't 1.28-based
+git submodule foreach ""git branch -r | grep -Eo 'wmf/.*' | grep -v '1.28' | xargs -I {} git push origin :{}""
+# Delete all (remote) tags named wmf/* 
+git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git push origin :{} ||:""
+# Delete the tags locally too, so we don't re-push them.
+git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git tag -d {}""
+```
+
+Just gotta swap `1.28` for whatever branch you're wanting to retain (the current one, obviously).
+
+Just ran this for all skins and the vendor directory. Finishing up extensions now.
+
+Let's please not reintroduce these tags. And get better (via the child task) at cleaning up the branches automatically.",1468532493,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"One liner for all extensions and skins meta repos:
+```
+lang=bash
+  # Delete all remote branches matching wmf/ that aren't 1.28-based
+  git submodule foreach ""git branch -r | grep -Eo 'wmf/.*' | grep -v '1.28' | xargs -I {} git push origin :{}""
+  # Delete all (remote) tags named wmf/* 
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git push origin :{} ||:""
+  # Delete the tags locally too, so we don't re-push them.
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git tag -d {}""
+Just gotta swap `1.28` for whatever branch you're wanting to retain (the current one, obviously).
+```
+
+Just ran this for all skins and the vendor directory. Finishing up extensions now.
+
+Let's please not reintroduce these tags. And get better (via the child task) at cleaning up the branches automatically.",1468532469,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"One liner for all extensions and skins meta repos:
+  git submodule foreach ""git branch -r | grep -Eo 'wmf/.*' | grep -v '1.28' | xargs -I {} git push origin :{}""
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git push origin :{} ||:""
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git tag -d {}""
+Just gotta swap `1.28` for whatever branch you're wanting to retain (the current one, obviously).
+
+Just ran this for all skins and the vendor directory. Finishing up extensions now.
+
+Let's please not reintroduce these tags. And get better (via the child task) at cleaning up the branches automatically.",1468530442,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"One liner for all extensions and skins meta repos:
+  git submodule foreach ""git branch -r | grep -Eo 'wmf/.*' | grep -v '1.28' | xargs -I {} git push origin :{}""
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git push origin :{}""
+Just gotta swap `1.28` for whatever branch you're wanting to retain (the current one, obviously).
+
+Just ran this for all skins and the vendor directory. Finishing up extensions now.
+
+Let's please not reintroduce these tags. And get better (via the child task) at cleaning up the branches automatically.",1468527268,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Also we should prune old branches for extensions/skins/vendor too, I only do it for core right now.",1468427386,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Actually, I'd like to repurpose this as ""Just kill old branches."" The tags are useless and clutter shit up which is why I nuked all of them a few weeks ago.",1468427366,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Ran `convert-wmf-branches 1.26` on repos `mediawiki/core` and `mediawiki/extensions/{VisualEditor,NavigationTiming}`.",1444186214,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"(Re-opening, since there are still plenty of extensions with them, and it will happen again every release cycle)",1433778273,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),Maybe the make-wmf-branch could be taught how to convert obsolete branches to tags? This way the conversion will be part of the process and we could close this task.,1430388828,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"I've ran the script for 1.25 on mediawiki/core and the following mediawiki extension repositories I have checked out:
+```
+CategoryTree
+CentralNotice
+CirrusSearch
+Cite
+Citoid
+CodeReview
+Collection
+ContentTranslation
+CvnDB
+Echo
+EventLogging
+Flow
+Gadgets
+GlobalCssJs
+GlobalUserPage
+GuidedTour
+ImageMetrics
+Interwiki
+Math
+MobileFrontend
+MultimediaViewer
+ParserFunctions
+Scribunto
+Sentry
+SyntaxHighlight_GeSHi
+TemplateData
+Thanks
+Translate
+UniversalLanguageSelector
+VisualEditor
+WikiEditor
+WikimediaEvents
+ZeroBanner
+```",1429293156,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),if there's no harm in keeping the tags around it sounds like a good idea to have them,1418979797,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Updated the script and published to P531. It now works for both MediaWiki core and extensions. And it also removes the branches afterward (instead of requiring manual action via Gerrit dashboard). Note that this requires Gerrit administrator permissions to run.
+
+{P531}",1429291127,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Tried the following on `mediawiki/extensions/TemplateData` as test. Seems to work fine.
+
+```
+#!/usr/bin/env bash
+remote='origin'
+versions=('1.23' '1.24')
+git remote update $remote
+git remote prune $remote
+for version in ""${versions[@]}""; do
+	refs=`git for-each-ref --format='%(refname)' refs/remotes/${remote}/wmf/${version}wmf*`
+	for ref in $refs; do
+		branch=$(echo $ref | cut -d '/' -f 4-6)
+		git push origin "":$branch""
+	done
+done
+git remote update $remote
+git remote prune $remote
+```",1418224167,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Tried the following on `mediawiki/extensions/TemplateData` as test. Seems to work fine.
+
+```
+#!/usr/bin/env bash
+remote='origin'
+version='1.23'
+git remote update $remote
+git remote prune $remote
+refs=`git for-each-ref --format='%(refname)' refs/remotes/${remote}/wmf/${version}wmf*`
+for ref in $refs; do
+	branch=$(echo $ref | cut -d '/' -f 4-6)
+	git push origin "":$branch""
+	if [[ $? == 0 ]]; then
+		echo ""... deleted $branch""
+	else
+		echo ""Could not delete $branch""
+	fi
+done
+git remote update $remote
+git remote prune $remote
+```",1418223467,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),I have no real strong opinions about keeping them around.,1417915635,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"@hashar At this point this is only happening to wmf branches. After a MediaWiki core wmf-branch is abandoned, we definitely wouldn't be backporting patches for an individual extension's wmf-branch as the relevant wmf-branch wouldn't be deployed anymore (and couldn't as you'd have to update the submodule pointer in the MediaWiki core branch that no longer exists).
+
+For release branches this is different. Extension authors may maintain their extensions' release branch beyond MediaWiki core's end-of-life data for a release. But so far we haven't purged any release branches.
+
+@Reedy @Chad As for wmf-branches in extensions, I'd like to remove them instead of converting to tags. Do we need them for anything? The submodule pointers from the wmf-branches in mediawiki-core refer to commits, not branches. Having said that, should we keep them even in MediaWiki core? It's not like we'd revert back an entire major release in production.",1417907159,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"That might break zuul-cloner which expects to checkout branches which is used for {T1350} among others. (link: https://www.mediawiki.org/wiki/RFC/Extensions_continuous_integration ).
+
+I have filled {T76088} to investigate whether zuul-cloner will be able to consider tags instead of branches.",1417035950,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),I don't see any reason we couldn't. It would be running the same script essentially for all of our submodules,1417024817,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),Can this also be done for extensions as well?,1417021844,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"I created tags for `wmf/1.23wmf*` and `wmf/1.24wmf*` and deleted the branches.
+
+Script:
+
+```
+#!/usr/bin/env bash
+remote='origin'
+version='1.24'
+git remote update $remote
+git remote prune $remote
+refs=`git for-each-ref --format='%(refname)' refs/remotes/${remote}/wmf/${version}wmf*`
+for ref in $refs; do
+	branch=$(echo $ref | cut -d '/' -f 4-6)
+	git tag $branch $ref > /dev/null 2>&1
+	if [[ $? == 0 ]]; then
+		echo ""... tagged $branch""
+	else
+		echo ""Could not (re)create $branch""
+	fi
+done
+echo
+echo ""Ask a Gerrit admin to delete wmf/$version branches via https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/core,branches""
+echo
+echo ""... publishing tags""
+git push $remote --tags
+git remote update $remote
+git remote prune $remote
+```",1417017368,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Nope, no script for that.",1416152277,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,Something like PACE minimal or barbershop http://github.hubspot.com/pace/docs/welcome/,1415512766,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-ok2zr74rwqedp7qc3cko,task_description,resolved
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Ed reviewed and merged the changaes, and the new loading indicator can now be seen on Beta, e.g. <https://en.m.wikipedia.beta.wmflabs.org/wiki/Digital_object_identifier>. It will go live on production sites next week, 18-20 June, per the usual train deployment schedule.",1560458973,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Sure, he's alright ;) (or any engineer who has the time to look at it)",1560369147,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,code review from @Esanders? ,1560369041,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,I'm waiting for code review of the two patches linked at T217784#5179052.,1560348693,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,@matmarex what's the status of this now?,1560259122,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,👍to upload the version without the intermediate stage and add in the subtle slide down transition. ,1559750692,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Sure, done. (I'll note that this makes the editor switch dropdown inaccessible until both the editor code and the content has loaded.)",1559747247,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Looking at the animation again, I see that have you an intermediate stage once the editor switcher and publish button are available that truncates the loading message:
+|1|2|3
+|{F29232417}|{F29232426}|{F29232430}
+
+While I can see the advantage of showing progress being made by showing elements as they become available, I think the fact there is no transition from 1 to 2 and the truncation of the message means we should probably just go straight from 1 to 3.
+
+CC @iamjessklein ",1558701430,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Fine by me if that was the intention.
+
+I think this just leaves Ed's question about whether the placeholder toolbar should slide in (like the real toolbar does currently), or if it should appear instantly (as seen in the videos I posted: T1181#5179055).",1558550713,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,">>! In T1181#5179055, @matmarex wrote:
+> I am not entirely sure if you wanted the new design to remove the old blue progressbar? For now I removed it, but I feel like now it's less obvious when the loading actually completed – previously the large blue progressbar disappearing made it more noticeable, now it's only a small grey spinner that is replaced by the page title.
+
+In my opinion the text going from disabled/gray to enabled/black is the obvious indication that the editor has loaded (and also a more contextual indicator than what's happening with the header).",1558396952,PHID-USER-cjbkqgaozso5gfp3xv2n,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Migrating comments from gerrit:
+
+> Ed: Shouldn't the fake toolbar slide in though? I think it should...
+> 
+> Bartosz: I don't think it should. It appears instantly. Other overlays in MF do not have any animations like this; we only added it because it was appearing after a delay.
+> 
+> Ed: Ok, let's run this past Jess. I don't think we necessarily need to model our behaviour on what the rest of MF does, especially in this case as although VE is technically an overlay, it does its best to pretend it isn't.
+
+(ping @iamjessklein)",1558128761,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,The videos are showing the slower end of our expected loading times (~5s). I think the median load time is less than 2s and for quick loads a progress bar can feel a bit heavy. Unfortunately we can't know ahead of time how long the page will take to load.,1557839010,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"@iamjessklein I'd be interested to hear how the current take on the spinner came together. Although it might have been used in Foundation products, it has never been a standard widget as stated in T75972.
+I really like the progress made on the ticket, but share @matmarex' take on the spinner being less noticeable and think an indeterminate progressbar underneath the toolbar could be a viable alternative.
+
+Let me know about your thoughts…",1557838642,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"@iamjessklein I'd be interested to hear how the current take on the spinner came together. Although it might have been used in Foundation products, it has never been a standard widget as stated in T75972.
+I really like the progress made on the ticket, but share @matmarex' take on the spinner being less noticeable and think an indeterminate progressbar underneath the toolbar could be a viable alternative.",1557838620,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I implemented this, see patches on T217784#5179052. A few videos showing how it looks like (with artificially slowed down loading):
+
+{F29047838}
+
+{F29047839}
+
+{F29047837}
+
+I am not entirely sure if you wanted the new design to remove the old blue progressbar? For now I removed it, but I feel like now it's less obvious when the loading actually completed – previously the large blue progressbar disappearing made it more noticeable, now it's only a small grey spinner that is replaced by the page title.",1557802458,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"This is a modified rendering of the current overlay, so using the correct icons/fonts/sizes:
+
+{F28464346,size=full}",1553525562,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"*When we implement it,  let's test the longest message on the narrowest screen with an ellipsis and then troubleshoot
+* +1 to CSS
+
+So, it looks like this ticket is ready to move over into ""Ready for Pickup"" - for engineers. ",1553521801,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"> I wasn't clear on the value of the ... after the word Loading Editor. Is this a semantic thing that I'm missing?
+
+It is just commonly used affordance to indicate that the action is ongoing. It is already used in some places in MediaWiki (e.g. `""apisandbox-loading"": ""Loading information for API module \""$1\""..."",`, `""unwatching"": ""Unwatching..."",`, `""importstart"": ""Importing pages..."",`)
+
+> I defer to you on CSS vs. gif - I suspect the CSS would decrease loading time and if that's true, +1
+
+Not sure which is fewer bytes, but the CSS will look better on high DPI devices.
+
+> Re: spacing - I was thinking the spacing between the close button and divider and the divider and start of spinner would be the same and then the space between the spinner and text would be 1/3 of that space. In the image below, I've used two gifs( for the close button and spinner) so the sizes aren't 100% accurate
+
+Sounds good.",1553518050,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"@Esanders
+
+* Good call on spinner+message reading as one, but practically speaking, they are different elements.
+* The text is not bold, it just appears that way due to the contrast with the opacity of the overlay
+* I wasn't clear on the value of the ... after the word Loading Editor. Is this a semantic thing that I'm missing? 
+* I defer to you on CSS vs. gif - I suspect the CSS would decrease loading time and if that's true, +1
+* Re: spacing - I was thinking the spacing between the close button and divider and the divider and start of spinner would be the same and then the space between the spinner and text would be 1/3 of that space. In the image below, I've used two gifs( for the close button and spinner) so the sizes aren't 100% accurate
+* We should default to what is currently used for close button and text
+
+Whenever we do implement this, please shoot my way for a design review before shipping.
+
+{F28449899 width = 300}",1553343533,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Side note: we've historically used a gif for that loading spinner, but we could just as easily do it in CSS: https://loading.io/css/",1553272276,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Minor nitpicks for when we implement:
+* The text looks like it might be bold, it probably shouldn't be
+* The spacing between the spinner are the text should be reduced. If the spinner has the same spacing either side as the close icon, it looks like there are three separate componenets: close, spinner, message, whereas I think it should look more like: close, spinner+message
+* We can probably probably have a text ellipsis after the message, i.e. ""❋ Loading editor...""",1553272162,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I've iterated a bit in freehand and here's my latest proposal:
+
+{F28443955 width=300}
+
+**Notes:**
+
+* ""Editor wird geladen"" is German for ""Loading Editor""
+* The spinner animates indeterminately 
+* The height of the toolbar is 48px  here, there seems to be some back and forth about the height size though, so we should probably decouple that and resolve the issue over in T209015
+* In the event of text overflow, the string should be truncated with ellipsis 
+* This designed has been positively reviewed by @alexhollender and @cmadeo 
+
+Thoughts? Can I have 👍 or 👎 @Volker_E @Esanders ",1553270954,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"An ellipsis is a (as in one) typographic character with three dots, `…` vs `...` – depending on the font the three dots might look widely stretched, in any case they are always typographically wrong.",1553016488,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I'm not a big fan of the loading dots being used inline. They have only been used once before which is in CX (see T75972) where they are centred on the screen with more padding and at a larger size.
+
+I think it also looks odd because the three dots are based on the horizontal ellipsis in typography, and these would usually appear after text (although in this context I'm not sure that would help).
+
+In an inline context I would be more accustomed to seeing the rotating spinner used elsewhere in MobileFrontend, similar to:
+
+{F28420760}
+
+The only other animation I can think of seeing inline is an actual ellipsis, e.g. `Loading.` -> `Loading..` -> `Loading...` (repeat), but I'm not sure if this approach translates well to every script.",1553006434,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I'm thinking something pretty basic, keep the background color white and the close button on the left to have parody with the actual toolbar. In this instance, I've added the 3 loading dots as well.
+
+{F28420543 width = 300}",1553000312,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,This relates to T214477,1551721039,PHID-USER-ujgufealwngqoe65jj3h,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,Related to {T99274},1483649011,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,Thanks.,1422851460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I didn't tag it easy, but I've removed it.",1422851437,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Is this really ""easy""?",1422849721,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"The goal is to have good descriptions in the most relevant videos at https://www.youtube.com/user/watchmediawiki
+Links to all past tech talk videos: https://www.mediawiki.org/wiki/Tech_talks#Past_tech_talks
+
+Step 1: Add one-line bio of the speaker(s) of the video
+Step2: Go through the video and extract relevant links
+Step3: Add the new description to commons
+
+Template for the description:
+-Speaker Name (Their one-line bio)
+-Summary
+-Relevant links
+
+
+| Youtube video | Description in Youtube | Description in Commons | Embedded in Wikimedia pages
+| [[ https://www.youtube.com/watch?v=Qo4XIzCJZVs | Tech Talk: New readership data]] | Done | [[ https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm#.7B.7Bint:filedesc.7D.7D | Done]] | 
+|[[https://www.youtube.com/watch?v=_yr5z9Ix2f8 | Phabricator for Wikimedia projects]] | Done | [[https://commons.wikimedia.org/wiki/File:Phabricator_for_Wikimedia_projects.webm | Done]] | |
+| [[https://www.youtube.com/watch?v=ltEL-kPURKs |Automated citations in Wikipedia]] |Done | [[https://commons.wikimedia.org/wiki/File:Tech_Talk_-_Automated_citations_in_Wikipedia_-_Citoid_and_the_technology_behind_it.webm#.7B.7Bint:filedesc.7D.7D | Done]] | 
+| [[https://www.youtube.com/watch?v=sWiDimlK4bE |  Introduction to Free and Open Source Licensing at Wikimedia]] | Done | [[https://commons.wikimedia.org/wiki/File:Tech_Talk_-_Introduction_to_Free_and_Open_Source_Licensing_at_Wikimedia.webm | Done]] | |
+",1415224479,PHID-USER-vcyz3oe6mrt5w42lpqeh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_description,resolved
+Add documentation links to TechTalk Youtube Videos ,"Similarly to {T142728}, I think this task has run its course. Thank very much for your help @husn_shujaat!
+
+@Rfarrand @srishakatux from now any any new Tech Talk should have beforehand a proper plan for
+
+* being published in YouTube with a proper title, description, and whatever information will make them easier to be found
+* being published in Commons short after the event with the same
+* being embedded in the right wiki pages so they can be found by the people checking that documentation.
+
+I hope you will agree with this sensible plan not to increase our ""communication debt"" with Tech Talks.",1505207051,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,Imported as https://codein.withgoogle.com/tasks/5210795455545344/,1481282294,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@srishakatux this is perfect! Thank you :),1481280158,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@Aklapper @husn_shujaat I created a playlist for 'Tech talks' on our Youtube channel. All tech talks now lie here https://www.youtube.com/playlist?list=PLeoTcBlDanyMPuVYBZYbEORNezmemiAhv. I've created a GCI task about adding documentation for tech talk videos: https://codein.withgoogle.com/dashboard/tasks/5210795455545344/preview/. I haven't published it yet, but I have tried to frame the description as such that we could have several instances of it, where each student could choose to work on two videos at one time. If this sounds good, I will create a similar task with some additions for the one on CREDIT showcase and update the instance count to 5ish. 
+",1481242457,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@Aklapper @husn_shujaat I created a playlist for 'Tech talks' on our Youtube channel. All tech talks now lie here on Youtube https://www.youtube.com/playlist?list=PLeoTcBlDanyMPuVYBZYbEORNezmemiAhv. I've created a GCI task about adding documentation for tech talk videos: https://codein.withgoogle.com/dashboard/tasks/5210795455545344/preview/. I haven't published it yet, but I have tried to frame the description as such that we could have several instances of it, where each student could choose to work on two videos at one time. If this sounds good, I will create a similar task with some additions for the one on CREDIT showcase and update the instance count to 5ish. 
+",1481242383,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Ah, right. I'll put the page with links in the description.
+Yeah, they can add the description in the commons, I'll put it to youtube :)",1480277022,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Ah, right. I'll put the page with links in the description.",1480276983,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Alright, so this would refer to Commons only...  :)
+So as a student, how exactly would I find a video that still needs some documentation links added?",1480273284,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"If I was a student, what will I have to do after extracting relevant links? Where I am expected to add a one-line bio of the speaker?
+The thing is: We need to clearly communicate expectations to students, to avoid misunderstandings or wrong expectations on both sides :)",1480273179,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@Aklapper Take my place for the time being. Go through the video and extract the relevant links. Add a one-line bio of the speaker. :)
+The summary is usually already there.
+This all goes into the description of the video in commons",1480272846,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Aklapper Take my place for the time being. Go through the video and extract the relevant links. Add a one-line bio of the speaker. :),1480272735,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@husn_shujaat: If this was a GCI task, what exactly would be expected from a GCI student here? :)",1480271701,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I wonder if I could put this as a Google Code-In task.
+Like, 1 task would include 1 video and so this could be a recurring task.",1480178943,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,I wonder if I could put this as a Google Code-In task.,1480178732,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@husn_shujaat do you want to keep working on this task during this quarter?,1475577364,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Aklapper that worked! thanks :),1474125573,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#2554781, @husn_shujaat wrote:
+> When I add link of a speaker's profile, there is usually a ')' at its end, and youtube's code refuses to include that in the URL, so we end up with an invalid page. What to do?
+
+@husn_shujaat: Instead of entering `https://wikimediafoundation.org/wiki/User:Slaporte_(WMF)` could you try encoding the brackets by using `https://wikimediafoundation.org/wiki/User:Slaporte_%28WMF%29` maybe? Just an idea how to work around...",1473623568,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"You are right! I have tried to edit the description using Markdown syntax or HTML but it won't work either.
+
+Well... then I think it is better not to specify those wrong links and point to their team pages instead. Team pages are going to be more informative than most user pages anyway.",1471300768,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"There is tiiiiny bit problem at youtube. When I add link of a speaker's profile, there is usually a ')' at its end, and youtube's code refuses to include that in the URL, so we end up with an invalid page :/ 
+See https://www.youtube.com/watch?v=sWiDimlK4bE
+What to do?",1471289121,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,Good idea. You can [[ https://www.mediawiki.org/wiki/Phabricator/Help#Creating_a_task | create the task ]] yourself. Let me know if you have any questions.,1470826083,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Good idea. I'll get the two at commons done. 
+But I think we should create a seperate task for CREDITs . 
+Let this one be for tech talks only.",1470748299,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"A related comment:
+
+>>! In T85593#2514784, @Qgil wrote:
+> Here is another approach to this task: let's focus on assuring that current and future presentations are properly published in their related mediawiki.org pages. At least we will avoid making this problem bigger.
+
+We could apply the same idea to new videos produced. For instance, there was a [[ https://www.mediawiki.org/wiki/CREDIT_showcase | CREDIT showcase ]] last week:
+
+Stream: https://www.youtube.com/watch?v=BOj6nDbdPMA
+Stas: small WDQS GUI updates - https://www.mediawiki.org/wiki/Wikidata_query_service
+
+",1470645931,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"A related comment:
+
+>>! In T85593#2514784, @Qgil wrote:
+> Here is another approach to this task: let's focus on assuring that current and future presentations are properly published in their related mediawiki.org pages. At least we will avoid making this problem bigger.
+
+We could apply the same idea to new videos produced. For instance, there was a CREDIT showcase last week:
+
+Stream: https://www.youtube.com/watch?v=BOj6nDbdPMA
+Stas: small WDQS GUI updates - https://www.mediawiki.org/wiki/Wikidata_query_service
+
+",1470645903,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@Aklapper Sorry for missing your pings here, yes! I can give permissions to the YouTube channel. So can Byron, Quim, Chris, James A, & Tilman. 
+Happy to add anyone you want me to. ",1469031343,PHID-USER-vcyz3oe6mrt5w42lpqeh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Rfarrand: Do you know? ^^^,1468934021,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ," In T1119#2194307, @Qgil wrote:
+> while we figure out (this week, I expect) your permissions on MediaWiki's YouTube account.
+
+I'm wondering who knows about these permissions and how to go ahead when it comes to allowing more people to update description of existing Youtube videos.
+@Rfarrand maybe?",1468934009,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Rfarrand: Do you know? ^^^,1468933954,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#2194307, @Qgil wrote:
+> while we figure out (this week, I expect) your permissions on MediaWiki's YouTube account.
+
+I'm wondering who knows about these permissions and how to go ahead when it comes to allowing more people to update description of existing Youtube videos. 
+@Rfarrand maybe?",1467887357,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"So, finally my exams are over. 
+I just got done with https://commons.wikimedia.org/wiki/File:Phabricator_for_Wikimedia_projects.webm ",1465718887,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Qgil Thank you so much! :),1460733621,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,Of course @husn_shujaat ! First thing first. I wish you best luck with the exams.,1460699038,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I have my exams starting next week, I'm just too busy.
+I was wondering if I can resume working on this task from June 10 (that's when my exams end)
+Is that OK?",1460669665,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Yes, I'm totally ok with it. 
+I'll now start with https://www.youtube.com/watch?v=_yr5z9Ix2f8 ",1460462260,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"You can edit the list by clicking the ""Edit Task"" link above.
+
+A couple of wiki pages mentioned in the video itself is a good guidance. Let's go for more?
+
+I think it is good to do more videos available in Commons while we figure out (this week, I expect) your permissions on MediaWiki's YouTube account. Are you OK with this?",1460363313,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"That list is very helpful, thanks!
+
+I need help in deciding which tech talk video should be on which wiki page?
+For the start, let's just consider 'The readership data' one.
+So far, @Qgil embedded it in [[https://meta.wikimedia.org/wiki/Research:Characterizing_Wikipedia_Reader_Behaviour| here]] and I embedded it [[https://www.mediawiki.org/wiki/Reading/Mexico_Readers_Research|here]]. Is there any where else where the video should go?",1460311365,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,,1460311302,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,,1460311163,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Thanks so much for this work! Its great. Just a few links for you in case this helps. 
+1) I try to keep this updated with all tech talks, however I have missed a few recently. I will go back and update soon: https://www.mediawiki.org/wiki/Tech_talks
+2) Here is a collection of all of the tech talks we have done in case any are missing:
+https://www.youtube.com/user/watchmediawiki
+
+Let me know if I can help you!",1460133925,PHID-USER-vcyz3oe6mrt5w42lpqeh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Thank you! :)
+I'll see to adding the speaker's description.
+
+I will embed the videos, but I can't get how to put the links to [[ https://commons.wikimedia.org/wiki/Special:WhatLinksHere/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm | this page]]?
+Do you think I should just embed the videos in the links mentioned in the description (except for [[ https://phabricator.wikimedia.org/T113066
+ | T113066 ]] of course)? Will those be enough?
+
+The idea of the table is a great way of keeping track of our progress.",1460027710,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"This is very good! I made [[ https://commons.wikimedia.org/w/index.php?title=File%3ATech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm&type=revision&diff=192443093&oldid=192413368 | some edits ]] to link to the speaker user profile in mediawiki.org, to add some relevant links to the description, and to simplify the format of the list of links (we try to avoid HTML in wikitext when possible).
+
+It would be useful to add a one line description of the speaker, which you can usually borrow from their user profiles.
+
+Finally, clicking at [[ https://commons.wikimedia.org/wiki/Special:WhatLinksHere/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm | What links here ]] one can see that there is no relevant page linking to this video in the entire collection of Wikimedia wikis. This is not useful! You can improve this situation by finding the relevant pages, and embedding the video there.
+
+Let me do this once to provide an example: https://meta.wikimedia.org/w/index.php?title=Research%3ACharacterizing_Wikipedia_Reader_Behaviour&type=revision&diff=15506568&oldid=15428580 (I did it with the regular ""Edit"" / VisualEditor link and the Tech Talk video was already the second result suggested as media, maybe your good description is starting to work semantically?).  :)
+
+I was thinking that we could maintain a table in the description of this task to track progress, along these lines:
+
+| YouTube video | Description in YouTube | Description in Commons | Embedded in Wikimedia pages |
+|  [[ https://www.youtube.com/watch?v=Qo4XIzCJZVs | Tech Talk: New readership data ]] |  | [[ https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm#.7B.7Bint:filedesc.7D.7D | DONE ]] | ",1460010114,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Is this okay?
+https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm#.7B.7Bint:filedesc.7D.7D
+",1459987699,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,,1459987687,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,,1459987409,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"OK!
+I'll start with the description at commons.
+The youtube video is linked at commons but not the other way round.
+I think it's a good idea to have the youtube link at the source in commons as it is in this video.
+
+P.S: It was me who liked it :D",1459981017,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Great! Let's move onto the videos. It makes sense to start with the Tech Talks. We can work on a specific one, and then when we are happy about it, we can apply the same formula to the rest.
+
+I propose to start with this one:
+
+* https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm
+* https://www.youtube.com/watch?v=Qo4XIzCJZVs
+
+After almost three weeks, it has 77 views and 1 like in YouTube, 28 views in Commons. Let's see whether we can drive more YouTube attention there. :)
+
+Since it is available in Commons, we can edit the description there at will, and when we are happy about it we can copy it to YouTube. OK?",1459972680,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Great! Let's move onto the videos. It makes sense to start with the Tech Talks. We can work on a specific one, and then when we are happy about it, we can apply the same formula to the rest.
+
+I propose to start with this one:
+
+* https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm
+* https://www.youtube.com/watch?v=Qo4XIzCJZVs
+
+After almost three weeks, it has 77 views and 1 like. Let's see whether we can drive more YouTube attention there. :)
+
+Since it is available in Commons, we can edit the description there at will, and when we are happy about it we can copy it to YouTube. OK?",1459972614,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Great! Let's move onto the videos. It makes sense to start with the Tech Talks. We can work on a specific one, and then when we are happy about it, we can apply the same formula to the rest.
+
+I propose to start with this one:
+
+* https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm
+* https://www.youtube.com/watch?v=Qo4XIzCJZVs
+
+Since it is available in Commons, we can edit the description there at will, and when we are happy about it we can copy it to YouTube. OK?",1459972505,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Pleasure is all mine!
+>  in an ideal world these videos should be in https://commons.wikimedia.org, and that information would be very interesting to have in the their description pages. You have the choice of detailing this information both in YouTube (since it might attract more viewers) and Commons (the canonical location of these videos), or you can have it only in Commons, and link to there from the YouTube page. Up to you, whatever you think is more feasible.
+
+Yes, I can do that, it'll only take copy/paste to put description in both places.
+
+It's a yes from me on this template (speaker, summary, links). 
+Do you think we can move on to the videos?
+",1459963584,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Thank you @husn_shujaat !
+
+> * Speaker/Credits
+
+Yes, the main speakers are enough. All the better if we could link to their user page in mediawiki.org.
+
+> Summary
+
+Yes, paying attention to keywords that might bring more on-topic viewers to these videos.
+
+> IRC (channel)
+
+Hm. I would not get too obsessed about this. Usually the simultaneous chat is interesting only during the tech talk, but not after that.
+
+> Relevant links (All the webpages mentioned in the video, for example, link of T113066 should be in the description of Tech Talk: New readership data...) We could also mention the time of when these links/webpages were shown.
+
+If you are ready to do this work, then this will be excellent indeed. One thought though: in an ideal world these videos should be in https://commons.wikimedia.org, and that information would be very interesting to have in the their description pages. You have the choice of detailing this information both in YouTube (since it might attract more viewers) and Commons (the canonical location of these videos), or you can have it only in Commons, and link to there from the YouTube page. Up to you, whatever you think is more feasible.
+
+As soon as we agree on the description, the next step will be to agree on which videos should get priority. Not all of them are equally relevant, and you should be able to focus your time on the videos that matter most.",1459930927,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Thanks for assigning this to me, I was looking for such tasks. 
+The plan looks good to me.
+
+I saw some techtalks videos and their descriptions give some good ideas for templates.
+ 
+  -   Speaker/Credits
+  -   Summary
+  - IRC (channel)
+  - Relevant links (All the webpages mentioned in the video, for example, link of [[ https://phabricator.wikimedia.org/T113066 | T113066]] should be in the description of [[ https://www.youtube.com/watch?v=Qo4XIzCJZVs | Tech Talk: New readership data...]]) We could also mention the time of when these links/webpages were shown.
+
+
+
+
+
+
+
+
+ 
+
+",1459897322,PHID-USER-k7tm37wvr4juk56sjsxf,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@husn_shujaat based on T85593#2170408 I think this is a good task for you. I'm taking the liberty to steal it from @Rfarrand and assign it to you. I'm scheduling it for our currently quarterly milestone. 
+
+The goal is to have good descriptions in the most relevant videos at https://www.youtube.com/user/watchmediawiki
+
+As a first objective, I propose that you define a template for these descriptions. What information should it have, and any special format? It doesn't need to be anything complex. In fact, the simpler the better, as long as the basic information is provided. 
+
+Once we agree on the template, let's discuss on which videos would need to get it first (we have many videos, and not all of them are equally interesting nowadays).
+
+Please confirm this plan works for you, and feel free to suggest improvements.  :) Thank you!",1459888234,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#1761755, @Aklapper wrote:
+> @Rfarrand: [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner | Want to give this a shot ?]]
+
+@Rfarrand: Ping. (Though I'm not sure how S' last comment is related, or if that would be separate here.)",1447260630,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#1648391, @Qgil wrote:
+> I wonder whether Google Code-in could be of any help here.
+
+I think it could if @rfarrand defines a good ""generic"" (cloneable) [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Requirements_of_a_task | beginner task ]], like 
+""Wikimedia occassionally hosts [[ https://www.mediawiki.org/wiki/Tech_talks | Tech talks]] (FIXME: That page does not even explain what a Tech Talk is). Go to this link which is a list of Wikimedia TechTalk videos on Youtube. Pick one video, thoroughly understand which topic the Tech Talk video is about, identify a number of key terms you would associate with the Tech Talk topic, [[ https://www.mediawiki.org/wiki/Help:Searching | search ]] for documentation wiki pages on Wikimedia sites (meta.wikimedia.org, mediawiki.org, potentially commons.wikimedia.org and en.wikipedia.org, wikimediafoundation.org, FIXME: any others?) which are strongly related to the Tech Talk's topic, and provide a list of links to these wiki pages plus information which video you chose"". 
+(The action of updating the Youtube description requires special permissions so that's out of scope for GCI I'd say.)
+
+@Rfarrand: [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner | Want to give this a shot ?]]
+
+**Edit:** I hadn't seen Spage's last comment when I wrote my comment.",1446042167,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#1648391, @Qgil wrote:
+> I wonder whether Google Code-in could be of any help here.
+
+I think it could if @rfarrand defines a good ""generic"" (cloneable) [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Requirements_of_a_task | beginner task ]], like 
+""Wikimedia occassionally hosts [[ https://www.mediawiki.org/wiki/Tech_talks | Tech talks]] (FIXME: That page does not even explain what a Tech Talk is). Go to this link which is a list of Wikimedia TechTalk videos on Youtube. Pick one video, thoroughly understand which topic the Tech Talk video is about, identify a number of key terms you would associate with the Tech Talk topic, [[ https://www.mediawiki.org/wiki/Help:Searching | search ]] for documentation wiki pages on Wikimedia sites (meta.wikimedia.org, mediawiki.org, potentially commons.wikimedia.org and en.wikipedia.org, wikimediafoundation.org, FIXME: any others?) which are strongly related to the Tech Talk's topic, and provide a list of links to these wiki pages plus information which video you chose"". 
+(The action of updating the Youtube description requires special permissions so that's out of scope for GCI I'd say.)
+
+@Rfarrand: [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner | Want to give this a shot ?]]",1446040603,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I created [[ https://www.mediawiki.org/wiki/Template:Tech_talk_video |  Template:Tech talk video]] `{{Tech talk video| link=` //youtube link// `| date=` //date//  `| title=` //talk title// `}}` that outputs
+* ""[[ https://www.youtube.com/watch?v=sWiDimlK4bE | Watch ]] 2015-10-19 [[https://www.mediawiki.org/wiki/Tech_talks | Tech talk ]] on ""Free and open source licensing at Wikimedia"".
+
+then just add this to the relevant pages that had tech talks. Maybe also use this template on the Tech talks page itself, though that has extra links.
+Done on MediaWiki-Vagrant, Performance team, Phabricator -- check https://www.mediawiki.org/wiki/Special:WhatLinksHere/Template:Tech_talk_video
+",1446012991,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I created [[ https://www.mediawiki.org/wiki/Template:Tech_talk_video |  Template:Tech talk video]] `{{Tech talk video| link=` //youtube link// `| date=` //date//  `| title=` //talk title// `}}` that outputs
+* ""[[ https://www.youtube.com/watch?v=sWiDimlK4bE | Watch ]] 2015-10-19 [[https://www.mediawiki.org/wiki/Tech_talks | Tech talk ]] on ""Free and open source licensing at Wikimedia"".
+
+then just add this to the relevant pages that had tech talks. Maybe also use this template on the Tech talks page itself.",1446010567,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"How about:
+
+Create a template `{{Tech talk |` //youtube link// `|` talk title `|` //date// `}}` that outputs
+* ""[[ https://www.youtube.com/watch?v=sWiDimlK4bE | Watch ]] 2015-10-19 [[https://www.mediawiki.org/wiki/Tech_talks | Tech talk ]] on ""Free and open source licensing at Wikimedia""
+
+then add this to the relevant pages that had tech talks. Maybe also use this template on the Tech talks page itself.",1445975648,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,I wonder whether Google Code-in could be of any help here.,1442480574,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I mean, linking to the videos from the project pages. For instance, a link from https://www.mediawiki.org/wiki/MediaWiki-Vagrant to the last Tech Talk about MediaWiki Vagrant.",1417463915,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I have the youtube videos linked from the tech talk pages - I just have not linked to documentation on each talk from YouTube. It might actually take a little while to dig around and find all of the documentation/project pages. 
+
+Past tech talks listed with YouTube links: https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event/TechTalks",1417458354,PHID-USER-vcyz3oe6mrt5w42lpqeh,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,This task is missing a description. The other way round ould be done as well: link to Tech Talk videos from the corresponding wiki pages.,1417445008,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"https://www.mediawiki.org/wiki/2015_MediaWiki_User_Survey
+
+https://docs.google.com/forms/d/1j2ThONROvc0bGY5d3yx4tJln4Aa2Fs130j5OlHbjW14/viewform
+
+Presentation reporting preliminary results.
+
+https://commons.wikimedia.org/wiki/File:2015_MediaWiki_User_Report.pdf",1415210988,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-54hi6wjvnjjmrztmmiki,task_description,resolved
+Create a survey that MediaWiki users can use to provide us with information,"Exciting news and great job!
+",1438269463,PHID-USER-psxtq4r4r73pqtniajr2,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Exciting news and great job!
+
+----- Original Message -----
+From: ""Ckoerner"" <no-reply@phabricator.wikimedia.org>
+To: alexis@everybody.org
+Sent: Thursday, July 30, 2015 10:33:27 AM
+Subject: [Maniphest] [Commented On] T1114: Create a survey that MediaWiki users can use to provide us with information
+
+Ckoerner added a comment.
+
+Phew!
+It's been a few weeks since Wikimania and I'm just now getting my bearings.
+
+As of this morning we have 127 responses to our survey. That's a great accomplishment. Does anyone want to send out another reminder to the various mailing lists? One last hurrah?
+
+I'll close the survey tomorrow (Friday) at the end of the day (20:00 CST).
+
+Then we should put together a final report (maybe just an update of our presentation from Wikimania) with stats.
+
+I can work on making the data available publicly - anonymized of course.
+
+Then what?
+
+Might I suggest we take the feedback from the survey, add it to our wishlist, and start to prioritize?
+
+
+TASK DETAIL
+  https://phabricator.wikimedia.org/T1114
+
+EMAIL PREFERENCES
+  https://phabricator.wikimedia.org/settings/panel/emailpreferences/
+
+To: Ckoerner
+Cc: Krenair, RichardHeigl, RHeigl, Ckoerner, cicalese, Spage, Aklapper, Mglaser, Palexis, MarkAHershberger, Qgil, Legoktm, Malyacko, P.Copp",1438267912,PHID-USER-psxtq4r4r73pqtniajr2,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Phew!
+It's been a few weeks since Wikimania and I'm just now getting my bearings. 
+
+As of this morning we have 127 responses to our survey. That's a great accomplishment. Does anyone want to send out another reminder to the various mailing lists? One last hurrah? 
+
+I'll close the survey tomorrow (Friday) at the end of the day (20:00 CST).
+
+Then we should put together a final report (maybe just an update of our presentation from Wikimania) with stats.
+
+I can work on making the data available publicly - anonymized of course.
+
+Then what?
+
+Might I suggest we take the feedback from the survey, add it to our wishlist, and start to prioritize?",1438266804,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"The survey has been sent to mediawiki-l
+
+http://hexm.de/MWSurvey
+
+Alternate link: https://docs.google.com/forms/d/1j2ThONROvc0bGY5d3yx4tJln4Aa2Fs130j5OlHbjW14/viewform
+
+Please share and provide suggestions on where else to promote. We will leave it open for a little more than 2 weeks, closing on Friday, July 31st.
+
+Woo!",1436977074,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,Great! Will you be posting information for remote participation in the Stakeholders' meetup?,1436973359,PHID-USER-mpmiy5j6qf3u6jazgvcy,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"We (Mark, Marcus, and myself) are at the hackathon in Mexico City. We've created a page to host a brief introduction to the survey (and eventually the results) on Mediawiki.org.
+
+https://www.mediawiki.org/wiki/2015_MediaWiki_User_Survey
+
+",1436972925,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Ok, we're at the Hackathon at Wikimania and talked about the question about how frequently you update. 
+
+We've reworded it to ask, ""Which MediaWiki update cycle is closest to what you use?""
+",1436972088,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Sorry, I didn't mean for this to be a blocker. Despite the fact that the major/point release schedule is not currently accurate in terms of time, it is a driver for updating. I update when a new security-related point release or major release is available, regardless of whether that is every month or every six months. So, the time-based answers were not a good fit for my situation. But, some folks might use a more time based approach to updating. I think adding answers based upon release availability to the time based answers to the question would be a good solution, helping us to determine what the drivers are for updating. I don't recall if there was an ""other"" answer, but that could also help. But, I whatever you choose, this should not stop the survey from moving forward.",1436971582,PHID-USER-mpmiy5j6qf3u6jazgvcy,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"I'm stuck on the 'How frequently do you update"" question. Since the major/point release schedule isn't the most accurate, will responses tell us anything useful? Can we combine the two in a graceful way? ",1436802165,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Yes, that was why I was mentioning it. It was difficult to answer the question with a strict timeframe. We update whenever there is a release available to update to, but that does not appear to happen on schedule at this point.",1436560974,PHID-USER-mpmiy5j6qf3u6jazgvcy,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Ckoerner writes:
+
+> Which is more important to know. That folks update to major/point
+> releases or that they're updating with any sort of frequency? Do you
+> think we should combine the two answer types?
+
+No comment on either of those points, but I would point out that there
+have been questions on mediawiki-l about the lack of point releases.",1436559274,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@RHeigl Thanks for the OK and the correction.
+
+@Cicalese I can move the links to the thank you page. Good idea.
+
+As for the upgrade question, you have an interesting point. The release schedule for MediaWiki is major releases every 6 months and point releases monthly. 
+
+https://www.mediawiki.org/wiki/Version_lifecycle#Release_policy
+
+Which is more important to know? That folks update to major/point releases or that they're updating with any sort of frequency? Do you think we should combine the two answer types?",1436543850,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@RHeigl Thanks for the OK and the correction.
+
+@Cicalese I can move the links to the thank you page. Good idea.
+
+As for the upgrade question, you have an interesting point. The release schedule for MediaWiki is major releases every 6 months and point releases monthly. 
+
+https://www.mediawiki.org/wiki/Version_lifecycle#Release_policy
+
+Which is more important to know. That folks update to major/point releases or that they're updating with any sort of frequency? Do you think we should combine the two answer types?",1436543832,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@RHeigl Thanks for the OK and the correction.
+
+@Cicalese I can move the links to the thank you page. God idea.
+
+As for the upgrade question, you have an interesting point. The release schedule for MediaWiki is major releases every 6 months and point releases monthly. 
+
+https://www.mediawiki.org/wiki/Version_lifecycle#Release_policy
+
+Which is more important to know. That folks update to major/point releases or that they're updating with any sort of frequency? Do you think we should combine the two answer types?",1436543820,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"It looks great! Thank you so much for your work on this, @ckoerner!
+
+I have two very minor suggestions, but I think it is good to go regardless, even without any changes. For the ""how often do you upgrade"" question, I wanted to answer in a less time constrained manner: ""every time there is a point release"", ""every time there is a security-related point release"" or ""every time there is a major release"". And, would it be possible to move the links from the page with the Submit button (where it is tempting to click them and lose the survey results) to the Thank You page?",1436523899,PHID-USER-mpmiy5j6qf3u6jazgvcy,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Checked it. Great!
+You have my OK :-))
+
+Thank you very much!
+
+Just found a typo: Are you(r) sites public or private? 
+
+",1436517688,PHID-USER-lmzb6z33itjcncao6utg,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@krenair Fixed! Thank you.
+
+@mglaser Hmm. Good point. I've changed it to a multi-select.",1436477807,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"On the third page, I am asked how many MediaWiki sites I run. I selected more than one. In the follwing question about my MW version, I have to pick one. However, I run a range of versions. This might probably be better if I could select multiple options here.  
+
+Otherwise it's ok for me",1436476334,PHID-USER-qfsdosrnxswxjuku752n,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"On the third page, I am asked how many MediaWiki sites I run. I selected more than one. In the follwing question about my MW version, I have to pick one. However, I run a range of versions. This might probably be better if I could select multiple options here.  ",1436475867,PHID-USER-qfsdosrnxswxjuku752n,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"And "" I contribute patches and pug fixes""",1436475560,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Typo on ""What would yo like to see most improved in the community around MediaWiki?""",1436477846,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Tyop on ""What would yo like to see most improved in the community around MediaWiki?""",1436475537,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,Might be worth separating people who are actually running this week's WMF branches from those who are running really old WMF branches.,1436475081,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"The survey has been created!
+
+Please review. If you **are OK** with sending, please let me know. If you are **not OK** with sending, please let me know.
+
+I will not publish or send this until I have **at least 4 responses **in the affirmative. I don't want to send it out with the //assumption //everyone is OK with it! :)
+
+http://goo.gl/forms/XCYIdNT2gI",1436474996,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@cicalese
+
+> 3.What would you like to see improved in MediaWiki?
+> 4.What is the most important thing the Mediawiki community should be focused on?
+
+My thought was to have one question about the software itself and the other be about the community. Fishing for answers like, ""I think VisualEditor should work on the Apple Newton."" as opposed to, ""I think there should be more inclusion of people from the southern hemisphere at events.""
+
+Does that make sense? Do you think I should reword those? How does this sound?
+
+ - What would you like to see most improved in MediaWiki the software?
+ - What would yo like to see most improved in the community around MediaWiki?
+
+The other suggestions are spot on, thank you.
+
+@mglaser
+
+> When did you last update your MediaWiki? To which version (LTS version, newest release, newest patch version, or other?)
+
+
+In the longer survey I had a separate question regarding frequency. How about we keep both questions to keep it quantitative.
+
+> How many extensions do you use?
+
+I'm curious about extension usage. Is everyone using just WMF-led extensions? What's the usage of third-party extensions like?
+
+How about, ""Of the extensions you use, which are your Top Five?"" And then have 5 blanks where they can enter the name of the extension?
+
+
+Here's an updated draft based upon the feedback.
+
+
+# How long have you been using MediaWiki?
+# How many MediaWiki sites do you manage?
+# Are your sites public or private?
+# How many end users are there of your MediaWiki sites?
+# What MediaWiki version are you currently using?
+# How frequently do you update your MediaWiki installations and extensions?
+# Of the extensions you use, which are your Top Five?
+
+# Why do you use MediaWiki?
+# What would you like to see most improved in MediaWiki the software?
+# What would yo like to see most improved in the community around MediaWiki?
+# Do you make contributions to the MediaWiki community?
+# What barriers, if any, do you think exist to participation in the MediaWiki community? What can we do to help?
+
+",1436392964,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Thanks, Chris, for this list, this is good stuff. 
+
+A few comments that come to my mind:
+
+> 5. What MediaWiki version are you currently using?
+I think it is more interesting how frequently they update. So the question could be rephrased to 
+> 5. When did you last update your MediaWiki? To which version (LTS version, newest release, newest patch version, or other?)
+
+And the questions about extensions:
+> 6. How many extensions do you use?
+I am not so sure why we would be interested in that. Maybe rephrase it: 
+> 6. Did you modify your MediaWiki? How (add existing extensions, change skin, write new extensions)?
+
+In addition to @cicalese's comment,
+> 5. What barriers, if any, do you think exist to participation in the MediaWiki community?
+maybe we could ask how to help:
+> 5. What barriers, if any, do you think exist to participation in the MediaWiki community? What can we do to help?",1436223135,PHID-USER-qfsdosrnxswxjuku752n,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"This is a good short list. Perhaps the following two questions are similar enough to be combined into one:
+
+3.What would you like to see improved in MediaWiki?
+4.What is the most important thing the Mediawiki community should be focused on?
+
+And, the following two questions are thematically related and could benefit from being beside each other:
+
+2.Do you make contributions to the MediaWiki community?
+5.We're striving to increase the participation of MediaWiki users outside of Wikimedia Foundation-led initiatives. What do you think is the biggest barrier to participation?
+
+Perhaps 5 could be simplified to:
+
+5. What barriers, if any, do you think exist to participation in the MediaWiki community?
+
+Thanks for pulling this together!",1436213073,PHID-USER-mpmiy5j6qf3u6jazgvcy,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Ok, how about this as a proposal. I've removed a few questions to shorten things down to 12 questions. These are what I feel (which is neither right or wrong) on what are the important questions to ask this go round. This would assume that we keep the 4 demographic questions.
+
+ # How long have you been using MediaWiki?
+ # How many MediaWiki sites do you manage?
+ # Are your sites public or private?
+ # How many end users are there of your MediaWiki sites?
+ # What MediaWiki version are you currently using?
+ # How many extensions do you use?
+ # Of those extensions which are your Top Five?
+
+
+ # Why do you use MediaWiki?
+ # Do you make contributions to the MediaWiki community?
+ # What would you like to see improved in MediaWiki?
+ # What is the most important thing the Mediawiki community should be focused on? 
+ # We're striving to increase the participation of MediaWiki users outside of Wikimedia Foundation-led initiatives. What do you think is the biggest barrier to participation?",1436208493,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Ok, how about this as a proposal. I've removed a few questions to shorten things. This would assume that we keep the 4 demographic questions.
+
+ # How long have you been using MediaWiki?
+ # How many MediaWiki sites do you manage?
+ # Are your sites public or private?
+ # How many end users are there of your MediaWiki sites?
+ # What MediaWiki version are you currently using?
+ # How many extensions do you use?
+ # Of those extensions which are your Top Five?
+
+
+ # Why do you use MediaWiki?
+ # Do you make contributions to the MediaWiki community?
+ # What would you like to see improved in MediaWiki?
+ # What is the most important thing the Mediawiki community should be focused on? 
+ # We're striving to increase the participation of MediaWiki users outside of Wikimedia Foundation-led initiatives. What do you think is the biggest barrier to participation?",1436208455,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Regarding community surveys, this one from the Drupal community was insightful. 
+
+https://www.drupal.org/node/1399056
+
+Of note, their survey was at around 13 questions, in addition to 4 'demographic' questions.",1436202436,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,Dang. You are absolutely correct. We're at 20 + questions. What if we paired that down to say 10? I'll ask you and anyone else reading - what are the big 10 questions we want to ask? Think more about the answers. What top 10 things about MediaWiki users do we want to know? How do we ask questions that provide those answers?,1435689410,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Left my comments on the talk page.  One more, though: I feel like we don't want to bog dow the respondents just yet with too many questions.  I think @rheigl has worked on these beofe and it''d be good to know how we can make this as effective as possible.",1435678045,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Given that Wikimania is a scant two weeks away I spoke to @cicalese and offed to help finish the survey work. I have a draft of the questions here and need your feedback!
+
+http://mwstake.org/mwstake/wiki/MediaWiki_Usage_Questions
+
+Once I have a few people (I'm looking at you!) review these questions and the language around them I will create a working survey.
+
+As I mentioned earlier (T1114#1341595) I have some suggestions on the distribution of the survey. 
+
+  - What other opportunities exist that we can leverage to distribute? 
+  - What do we need to do to get approval/permission to use the channels mentioned?
+  - Does something like this need to be reviewed by the WMF in some capacity?
+
+If we want to have a window for folks to respond we must act quickly. As of today we have two weeks until Wikimania begins. I would think getting this in front of Mediawiki users ASAP would provide us with more insightful and complete information than if we wait any longer.
+
+Please review (and share) this draft. I propose a goal of sending this out by **the end of this week** - July 4th.
+",1435608698,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"We are using Google Forms for our hackathon surveys, so nothing against this option. Still, you might want to check alternatives at {T94807}.",1435596615,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Given that our budget is 0, I propose we use a Google Doc to capture the information. Any alternative suggestions?",1435596409,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,T951 is related as the survey will further our understanding of who (and how) is using MediaWiki.,1434057589,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Once we have a survey put together how do we get it in front of MediaWiki using people? A few ideas, but I'd love some more.
+* Email to mediawiki, mediawiki-enterprise, semantic-mediawiki (dev and user), mailing lists
+* Sharing on social media
+* See if the folks at WikiApiary will help. Maybe a site banner or something for a week or two
+* See if the folks behind MediaWiki.org can help. Maybe a banner as well",1433519592,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@cicalese , I put a page up on mwstake to start gathering these questions. I wanted to dump what was in my brain somewhere. Since this is your thing, feel free to delete it all. :)
+
+http://mwstake.org/mwstake/wiki/MediaWiki_Usage_Questions",1432751989,PHID-USER-xd3dshn3ykvvbsxmqbg6,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@Spage, you are right. Tag removed.",1426579800,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@Qgil, how is this part of the Documentation project? The survey is of users of the MediaWiki software. Are you thinking the survey could pose questions like ""Are you an [] admin [] MediaWiki hacker?"" ""How could MediaWiki documentation for admins / users / developers be improved?""",1426567793,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Broad outline of the survey:
+
+* How long have you been using MW?
+* What do you use it for?
+** Documentation?
+** Coordination?
+* How could MediaWiki distribution be improved?",1423849016,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"> Need to develop the questions and find a place to host this survey.
+
+@MarkAHershberger: Where was the scope of the survey discussed and where can that discussion be found (link)?
+Currently it feels like no-one finding this task here could help because the scope feels a bit vague. Please clarify...",1423754105,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,Thanks for the pointer!  That is helpful.,1418935381,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Phabricator does have a polling and questionnaire application..
+
+I don't know if there is a standard place to do this otherwise, but it's a pretty straight forward app that is in phab-01 to look at https://phab-01.wmflabs.org/vote/",1415636830,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"New report as of 2017/06/21. eventstreams is tracked at {T160644} already
+
+```
+root@graphite1001:/var/lib/carbon/whisper# du -hcs /var/lib/carbon/whisper/* | grep G | sort -rn
+433G	/var/lib/carbon/whisper/eventstreams
+199G	/var/lib/carbon/whisper/servers
+199G	/var/lib/carbon/whisper/instances
+137G	/var/lib/carbon/whisper/ores
+71G	/var/lib/carbon/whisper/MediaWiki
+50G	/var/lib/carbon/whisper/zuul
+46G	/var/lib/carbon/whisper/varnishkafka
+35G	/var/lib/carbon/whisper/frontend
+```",1415116064,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_description,resolved
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Resolving this old task, individual big users are tracked separately ",1501145271,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 358910 merged by Filippo Giunchedi:
+[operations/puppet@production] role: cleanup CI data in graphite
+
+[[https://gerrit.wikimedia.org/r/358910]]
+",1498668831,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"@ArielGlenn thanks! yeah the eventstreams/rdkafka task is T160644, `instances` is also supposed to move to labmon in T143405",1498568715,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Seen today: icinga-wm: PROBLEM - carbon-cache too many creates on graphite1001 is CRITICAL: CRITICAL: 1.67% of data above the critical threshold [1000.0]
+
+Mostly rdkafka plus some 'instances' metrics, I spot checked a couple log files: /var/log/carbon/carbon-cache\@{a,b,c}/creates.log",1498477488,PHID-USER-jtxavgb3caz53o45csni,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVzee3oNZYjxCLpCzLVP} [2017-06-25T09:00:53Z] <elukey> Executing 'sudo -u _graphite find /var/lib/carbon/whisper/eventstreams/rdkafka -type f -mtime +15 -delete' on graphite1001 to free some space (/var/lib/carbon filling up) - T1075",1498381253,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 358910 had a related patch set uploaded (by Filippo Giunchedi; owner: Filippo Giunchedi):
+[operations/puppet@production] role: cleanup zuul data in graphite
+
+[[https://gerrit.wikimedia.org/r/358910]]
+",1497429261,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 358903 merged by Filippo Giunchedi:
+[operations/puppet@production] graphite: introduce graphite::whisper_cleanup
+
+[[https://gerrit.wikimedia.org/r/358903]]
+",1497428873,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 358903 had a related patch set uploaded (by Filippo Giunchedi; owner: Filippo Giunchedi):
+[operations/puppet@production] graphite: introduce graphite::whisper_cleanup
+
+[[https://gerrit.wikimedia.org/r/358903]]
+",1497427583,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 197509 merged by Filippo Giunchedi:
+diamond: stop collecting disk IO stats for partitions
+
+[[https://gerrit.wikimedia.org/r/197509]]",1426697366,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 197509 had a related patch set uploaded (by Filippo Giunchedi):
+diamond: stop collecting disk partitions stats
+
+[[https://gerrit.wikimedia.org/r/197509]]
+",1426679729,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"still occurring, big jump in disk used on graphite1001 some weeks ago:
+
+{F99837}
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs * | sort -h
+0       irc
+2.3M    test
+5.6M    deploy
+12M     gerrit
+18M     VisualEditor
+54M     jvm_memory
+108M    scap
+186M    ocg
+195M    eventlogging
+249M    parsoid
+318M    carbon
+978M    HHVM
+1.3G    ve
+2.3G    kafka
+2.4G    restbase
+3.3G    statsd
+4.1G    cassandra
+4.7G    swift
+6.2G    frontend
+13G     mw
+42G     zuul
+46G     varnishkafka
+58G     jobrunner
+78G     MediaWiki
+78G     reqstats
+341G    servers
+680G    total
+```
+
+so `servers` is the biggest offender, which could match up with the growth of turning up MW in codfw (on average ~380MB/server, i.e. ~380 metrics/server)
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs servers/* | sort -h | tail -20
+1.3G    servers/ms-be1015
+1.3G    servers/ms-be2001
+1.3G    servers/ms-be2002
+1.3G    servers/ms-be2003
+1.3G    servers/ms-be2004
+1.3G    servers/ms-be2005
+1.3G    servers/ms-be2006
+1.3G    servers/ms-be2007
+1.3G    servers/ms-be2008
+1.3G    servers/ms-be2009
+1.3G    servers/ms-be2010
+1.3G    servers/ms-be2011
+1.3G    servers/ms-be2012
+1.3G    servers/ms-be2013
+1.3G    servers/ms-be2015
+1.4G    servers/ms-be2014
+2.1G    servers/labstore2001
+2.6G    servers/labstore1002
+4.0G    servers/labstore1001
+341G    total
+```
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs servers/labstore1001/* | sort -h
+4.5M    servers/labstore1001/vmstat
+5.6M    servers/labstore1001/loadavg
+12M     servers/labstore1001/cpu
+16M     servers/labstore1001/memory
+61M     servers/labstore1001/network
+81M     servers/labstore1001/diskspace
+3.8G    servers/labstore1001/iostat
+4.0G    total
+```
+
+the `iostat` hierarchy seems the biggest offender, 48% of total `servers`
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs servers/*/iostat | sort -h | tail -10
+996M    servers/ms-be2012/iostat
+1.1G    servers/ms-be2003/iostat
+1.1G    servers/ms-be2011/iostat
+1.1G    servers/ms-be2013/iostat
+1.1G    servers/ms-be2014/iostat
+1.1G    servers/ms-be2015/iostat
+2.0G    servers/labstore2001/iostat
+2.6G    servers/labstore1002/iostat
+3.8G    servers/labstore1001/iostat
+229G    total
+```
+
+and we count both partitions and underlying devices, however just the partitions accounts for ~half of the total `iostat` space:
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs servers/*/iostat/sd*[0-9] | tail -5
+31M     servers/zirconium/iostat/sda1
+31M     servers/zirconium/iostat/sda2
+31M     servers/zirconium/iostat/sdb1
+31M     servers/zirconium/iostat/sdb2
+127G    total
+```
+
+so I think it makes sense to consider just disks i.e. sd* but not the partitions within those (sw raid and lvm would still be graphed of course)",1426677880,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"downgrading to normal since we've mitigated the biggest growth.
+still pending zuul patching which now has over 93k disting metrics and totalling 100+ GB",1421082509,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,Jenkins no more emits to statsd under `jenkins.ci` which can now be deleted entirely.,1416489149,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,">>! In T1075#22258, @fgiunchedi wrote:
+> I think there might be some value in having those, but not as many. Note that also zuul metrics are basically duplicating those in jenkins, not sure exactly what generates those, zuul itself?
+> 
+> ```
+> /var/lib/carbon/whisper/jenkins/ci/mwext-CentralNotice-testextension/FAILURE/count.wsp
+> /var/lib/carbon/whisper/zuul/pipeline/test/job/mwext-CentralNotice-testextension/FAILURE/count.wsp
+> ```
+
+I finally looked at the usage of Graphite jenkins.ci metrics. Turns out they are not used from anywhere. The bug report to add them was:  Jenkins: report metrics to statsdhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55412 .
+
+The reason was to generate graphs of the executors queues, but it turns out the Java plugin does not collect them ( https://bugzilla.wikimedia.org/show_bug.cgi?id=55988 ).  So instead I added a Ganglia monitor which runs a python script to collect data out of the Jenkins REST API.
+
+
+I have uninstalled the plugin ( T1278 ), still have to restart Jenkins but it is not an ideal time to do (there is some long running jobs going on which I don't want to abort).  Whenever Jenkins is restarted, we can delete the whole 'jenkins.ci.' metrics hierarchy and reclaim the disk space.
+
+
+For Zuul, the metrics are used to generate dashboards on the Zuul status page at https://integration.wikimedia.org/zuul/ , so we need to keep them. That being said, we probably do not need metrics for each jobs / results, unfortunately Zuul does not have support to finely select which metrics to send.  Can be patched and proposed upstream.",1416413857,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,">>! In T1075#22258, @fgiunchedi wrote:
+>>>! In T1075#22250, @hashar wrote:
+>> We can most probably remove the Statsd plugin from Jenkins. I have created the sub task {T1278}
+> 
+> I think there might be some value in having those, but not as many. Note that also zuul metrics are basically duplicating those in jenkins, not sure exactly what generates those, zuul itself?
+
+@hashar any ideas on this?",1416409425,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,">>! In T1075#22250, @hashar wrote:
+> We can most probably remove the Statsd plugin from Jenkins. I have created the sub task {T1278}
+
+I think there might be some value in having those, but not as many. Note that also zuul metrics are basically duplicating those in jenkins, not sure exactly what generates those, zuul itself?
+
+```
+/var/lib/carbon/whisper/jenkins/ci/mwext-CentralNotice-testextension/FAILURE/count.wsp
+/var/lib/carbon/whisper/zuul/pipeline/test/job/mwext-CentralNotice-testextension/FAILURE/count.wsp
+```",1415968699,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,We can most probably remove the Statsd plugin from Jenkins. I have created the sub task {T1278},1415968381,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"also note that the zuul/jenkins stats are pushed twice, e.g.
+
+```
+/var/lib/carbon/whisper/jenkins/ci/mwext-CentralNotice-testextension/FAILURE/count.wsp
+/var/lib/carbon/whisper/zuul/pipeline/test/job/mwext-CentralNotice-testextension/FAILURE/count.wsp
+```
+
+and account for ~half of all metrics created daily.
+
+I took a look at the jenkins statsd plugin and it seems fairly easy to change it not to differentiate timings based on the build status but only on the job name:
+
+```
+diff --git a/src/main/java/org/jenkinsci/plugins/statsd/StatsdListener.java b/src/main/java/org/jenkinsci/plugins/statsd/StatsdListener.java
+index 2409d1b..ce00eb0 100644
+--- a/src/main/java/org/jenkinsci/plugins/statsd/StatsdListener.java
++++ b/src/main/java/org/jenkinsci/plugins/statsd/StatsdListener.java
+@@ -46,7 +46,8 @@ public class StatsdListener extends RunListener<Run> {
+         jobName = jobName.replaceAll(""\\/"", ""-"");
+         jobName = jobName.replaceAll(""[^a-zA-Z_\\-0-9]"", """");
+ 
+-        String metricName = prefix + '.' + jobName + '.' + result;
++        String metricResultName = prefix + '.' + jobName + '.' + result;
++        String metricTimingName = prefix + '.' + jobName;
+ 
+         LOGGER.log(Level.INFO, ""StatsdListener: config: "" + config);
+         LOGGER.log(Level.INFO, ""StatsdListener: job: "" + jobName + "", result: "" + result +
+@@ -54,8 +55,8 @@ public class StatsdListener extends RunListener<Run> {
+ 
+         try {
+             StatsdClient statsd = new StatsdClient(host, port);
+-            statsd.increment(metricName);
+-            statsd.timing(metricName, (int)duration);
++            statsd.increment(metricResultName);
++            statsd.timing(metricTimingName, (int)duration);
+         } catch (UnknownHostException e) {
+             LOGGER.log(Level.WARNING, ""StatsdListener Unknown Host: "", e);
+         } catch (IOException e) {
+```",1415967660,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,">>! In T1075#18973, @fgiunchedi wrote:
+> another potential avenue of investigation from hashar
+> 
+> 
+> ```
+>>    I have some examples related to continuous integration:
+> 
+>>   A) jenkins.ci , emitted by Jenkins, metrics namespaced as follow:
+> 
+>>     - job_name (roughly 4000 jobs)
+>>     - build status (4: success, failure, aborted, unstable)
+> 
+>>    Each having percentiles, count, max, mean, rate etc (12 entries)
+> 
+> 
+> good catch! looks like these shouldn't get additional metrics calculated by statsd, that would cut it by 12x. definitely worth investigating what's going on
+> 
+> ```
+
+so the solution here would be to separate build status from build time, status is fine being a different metric but build-time shouldn't be tied to the status as a metric, that greatly reduces the number of metrics",1415270623,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"to find out what files have been created recently we can exploit the fact that carbon-cache logs whenever it creates a new file. reqstats is there but seems a minority:
+
+```
+root@tungsten:/var/log/upstart# zgrep  -F 'creating ' /var/log/upstart/carbon_cache-*.gz | cut -d' ' -f8 | sort | grep -i reqstats
+/var/lib/carbon/whisper/reqstats/2_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/5yojb4_en_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/Mai_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/Mai_wikipedia_org/tp50.wsp
+/var/lib/carbon/whisper/reqstats/Mai_wikipedia_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/action_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/bn_m__wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/crsio_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/crsio_org/tp50.wsp
+/var/lib/carbon/whisper/reqstats/crsio_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/during_World_War_IIwikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/edits/2013_wikipedia_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/edits/EN_wikipedia_org/edit.wsp
+/var/lib/carbon/whisper/reqstats/edits/action_wikipedia_org/edit.wsp
+/var/lib/carbon/whisper/reqstats/edits/fa_m_wikivoyage_org/submits.wsp
+/var/lib/carbon/whisper/reqstats/edits/mai_wikipedia_org/edit.wsp
+/var/lib/carbon/whisper/reqstats/edits/title_wikipedia_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/el_wikiipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/en_wikiquosity_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/hi__wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/mai_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/norb_rulez_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/pap_m_wikibooks_org/tp50.wsp
+/var/lib/carbon/whisper/reqstats/philipminhparish_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/sfair_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/wpDestFile_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_NL_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_echolalie_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_ietf_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_ja_wikiipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_sugarlabs_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_urbansim_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_veteranosracingferrol_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_wikimania_org/tp50.wsp
+/var/lib/carbon/whisper/reqstats/www_wikimania_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/www_za_wikiversity_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/zh_wikipedia_orgzh_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/zhqvcrgkqodjbfyeuxdqaiqzx_org/pageviews.wsp
+root@tungsten:/var/log/upstart# 
+```",1415207611,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"another potential avenue of investigation from hashar
+
+
+```
+>    I have some examples related to continuous integration:
+
+>   A) jenkins.ci , emitted by Jenkins, metrics namespaced as follow:
+
+>     - job_name (roughly 4000 jobs)
+>     - build status (4: success, failure, aborted, unstable)
+
+>    Each having percentiles, count, max, mean, rate etc (12 entries)
+
+
+good catch! looks like these shouldn't get additional metrics calculated by statsd, that would cut it by 12x. definitely worth investigating what's going on
+
+```",1415188804,PHID-USER-wr3pospifdaxghmtobvr,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+unable to obtain stable firefox connection in 60 seconds,"This error message happens [[ https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox/LANGUAGE_SCREENSHOT_CODE=nl,label=contintLabsSlave%20&&%20UbuntuTrusty/29/consoleFull | intermittently ]]:
+
+  unable to obtain stable firefox connection in 60 seconds (127.0.0.1:7055) (Selenium::WebDriver::Error::WebDriverError)
+
+Looks like it is a known problem:
+
+https://code.google.com/p/selenium/issues/detail?id=4967
+https://github.com/leonid-shevtsov/headless/issues/33
+",1415110910,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ufnfo3vpfoqevod6gugb,task_description,declined
+unable to obtain stable firefox connection in 60 seconds,"That is a duplicate of {T1321}
+
+See there for full explanations and details on how to fix it up.",1416479903,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ufnfo3vpfoqevod6gugb,task_subcomment,NA
+unable to obtain stable firefox connection in 60 seconds,Related commit: https://gerrit.wikimedia.org/r/#/c/170023/,1415114465,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-ufnfo3vpfoqevod6gugb,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Thanks to @Dzahn we have been collecting the number of [[ https://www.mediawiki.org/wiki/Talk:Community_metrics#Bugzilla_stats | active Bugzilla users every month ]] for almost two years now. It would be useful to collect this data --or any approximation-- on a monthly basis:
+
+[x] Number of accounts created 
+[ ] Number of users logging 
+[x] Number of users performing any action in Maniphest 
+
+Extended Play
+
+It would be interesting to know whether it is possible to extract these values as well (total and past month):
+
+[x] Number of task creators
+[ ] Number of comment posters
+[x] Number of task //closers//
+[ ] Number of workboard movers
+
+[x] Number of tasks created
+[x] Number of tasks closed
+[x] Median age in days of open tasks by priority
+
+Very Extended Play
+
+Then we could open two parallel ways:
+* Other metrics per app: who is subscribing to Projects, who uses Differential...
+* Filter these metrics by project, with a possibility to aggregate projects (i.e. let's count only the engineering projects)
+
+The extended plays are inspirational only. This task can be closed as soon as we can publish monthly metrics for total amount of users and active in the past month.
+
+**First report, sent on January 1st (for the record)**
+
+> Hi Community Metrics team,
+>
+> this is your automatic monthly Phabricator statistics mail.
+> 
+> Number of accounts created in (2014-12): 395
+> Number of active users (any activity) in (2014-12): 619
+> Number of task authors in (2014-12): 384
+> Number of users who have closed tasks in (2014-12): 213
+> Number of tasks created in (2014-12): 3424
+> Number of tasks closed in (2014-12): 2529
+> Number of tasks in the shell project closed as resolved,fixed in (2014-12): 12
+>
+> Number of open and stalled tasks in total: 18125
+>
+> Median age in days of open tasks by priority:
+> Unbreak now: 115
+> Needs Triage: 147
+> High: 199
+> Normal: 437
+> Low: 686
+> Needs Volunteer: 536
+>
+> TODO: Numbers which refer to closed tasks might not be correct, as described in T1003.
+",1414696282,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_description,resolved
+Monthly report of total / active Phabricator users,"@MelodyKramer: The file to edit is https://phabricator.wikimedia.org/source/operations-puppet/browse/production/modules/phabricator/templates/community_metrics.sh.erb
+If you feel like writing and proposing a patch in Gerrit: See https://www.mediawiki.org/wiki/Gerrit/Getting_started . The repo in this case is `operations/puppet.git`, the file is `modules/phabricator/templates/community_metrics.sh.erb`, and you'd have to replace the command `git checkout master` by `git checkout production` in this very case. And if you don't feel like I can also give it a shot. :)",1509552480,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Ah, thanks @Aklapper - is it possible to get that link (or the information contained within) added to the monthly email update I receive? I'm not sure who mans the wheels on that. ",1509550992,PHID-USER-w5dqcsw7esxdqy3say2e,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"@MelodyKramer: I nowadays dump //two// of these numbers at [[ https://meta.wikimedia.org/wiki/Technical_Collaboration/Metrics#Project_management_.28Phabricator.29 | meta:Technical_Collaboration/Metrics#Project_management_.28Phabricator.29 ]].
+(Beforehand I dumped two of these numbers at [[ https://www.mediawiki.org/wiki/Community_metrics | mw:Community_metrics ]] but the [[ https://www.mediawiki.org/w/index.php?title=Community_metrics&action=history | page scope was too blurry ]] so I split wikimedia.biterg.io documentation, displaying of some graphs with data copied out of other systems, and a link hub to random metrics pages in Wikimedia into three separate pages.)
+
+(And the usual disclaimer when it comes to interpreting numbers: ""New Phab accounts"" does not mean ""active Phab accounts"" for more than half of these accounts.)",1509550274,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Hello! I just received the monthly stats email ([Wikitech-l] Phabricator monthly statistics - 2017-10) and I'm wondering if there's a way to show a 3 or 6 month trend. I do not know from the email if new Phab users have slowed down to a trickle or doubled...and the same holds true for active users and other metrics. This is a very very low-priority ask, but I would love to see additional stats added that compare the current figures to the past 3 or 6 months, so we can learn more about the ongoing nature of the userbase. Thank you! Mel ",1509547181,PHID-USER-w5dqcsw7esxdqy3say2e,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Trying to get some comparable numbers pre and post-migration. It seems that the sum of MediaWiki (including VisualEditor and MobileFrontend) and Wikimedia products is what mapped best from Bugzilla to Phabricator. Some numbers (I hate IRC invisible characters with passion, btw):
+
+```
+# Number of active users in MediaWiki and Wikimedia products
+# January 2015
+$ curl -s 'http://bots.wmflabs.org/~wm-bot/logs/%23mediawiki-feed/%23mediawiki-feed.tar.gz' | tar xzf - -O --wildcards '201501*' | grep wikibugs | grep -E '(MediaWiki|MobileFrontend|VisualEditor|Wikimedia)' | grep -Eo ' [(][^)]{0,3}10[^)]+' | sort | uniq -c | wc -l
+473
+# October 2014
+$ ... --wildcards '201410*' ...
+462
+```",1422873038,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"I would like to propose some changes in the data ranges used in this report, but before let's agree on {T86630}. You opinions are welcome there.",1421141894,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Thank you very much! 
+
+>>! In T1003#963841, @Dzahn wrote:
+> Number of accounts created in (2014-11): 299
+> Number of active users (any activity) in (2014-11): 443
+
+These are the two numbers I really care about for November. Look credible...
+
+> Number of task authors in (2014-11): 284
+> Number of users who have closed tasks in (2014-11): 115
+
+These are also interesting. Do you think that they can be trusted?
+
+It is no problem if the stats on tasks are messed up in the month of the Bugzilla migration. Even for December (with the RT migration) I'm not expecting to read much there in task related stats.
+
+Having a continuity of user related stats is great. Thank you again.
+
+
+> Number of tasks created in (2014-11): 1916
+> Number of tasks closed in (2014-11): 814
+> Number of tasks in the shell project closed as resolved,fixed in (2014-11): 4
+> 
+> Number of open and stalled tasks in total: 18296
+> 
+> 
+> Is that sufficient? It was easier to make than the lower part.
+
+",1420752643,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,andre__ added the address as allowed sender to wikitech-l. That means the list should now receive stats starting on Feb 1st.,1420752009,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"As requested in comments above i have added wikitech-l to the recipients of this mail. More specifically wikitech-l is now one of the recipients that receive communitrymetrics@ mail which is the sender of this as configured in the puppet phabricator role.
+
+Now we need one of the admins of wikitech-l to allow that sender as a ""non-member"".  Admins of wikitech-l are demon, aklapper and platonides.",1420751162,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#961937, @KartikMistry wrote:
+> Is it possible to get teamwise statistics? (eg: Language Engineering) (Just wishlist) :)
+
+Separate tickets with specific criteria can be created. Such tickets will be wishlist/needs volunteer though; I don't think that I should spend much more time fiddling with Phabricator database schemes and SQL queries.",1420744097,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"I doubt the November numbers because ""Number of open and stalled tasks in total"" is 18296 while it was 18125 in December. This really goes into details how metadata was migrated so I would not use any November numbers. Number of tasks created in Dec is 3424 - Number of tasks closed in Dec is 2529 = +895, but 18125-18296 =  -171. And as written in that script, the numbers are not entirely correctly for December either (and I encourage anybody who wants to investigate the SQL and Phab'sDB structure to fix that).",1420743975,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#963724, @Dzahn wrote:
+> 
+> Yes, let me try to make one for November manually. I will attach it here.
+
+I can give you this part:
+
+Number of accounts created in (2014-11): 299
+Number of active users (any activity) in (2014-11): 443
+Number of task authors in (2014-11): 284
+Number of users who have closed tasks in (2014-11): 115
+Number of tasks created in (2014-11): 1916
+Number of tasks closed in (2014-11): 814
+Number of tasks in the shell project closed as resolved,fixed in (2014-11): 4
+
+Number of open and stalled tasks in total: 18296
+
+
+Is that sufficient? It was easier to make than the lower part.",1420742737,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#961920, @Qgil wrote:
+> The report send on January 1 looks good! Thank you very much. I have [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-January/079999.html | forwarded it to wikitech-l ]], wondering whether there is a way to sending it there automatically.
+
+Yes, i can send it to wikitech by just adding the list address as a recipient. But one of the list admins has to also list the sender address in list settins somewhere as a verified ""non-member"" or we have to subscribe a fake user, otherwise the list will reject mail from an address it doesn't recognize as a subscribed member.
+
+> 
+> Also, would it possible to generate one report for November 2014? It's the month of the Bugzilla migration and any data needs to be taken with a big grain of salt. Still, having Bugzilla data until October and Phabricator data from December, it would be good to cover November for posterity.
+
+Yes, let me try to make one for November manually. I will attach it here.
+",1420740255,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#961937, @KartikMistry wrote:
+> Is it possible to get teamwise statistics? (eg: Language Engineering) (Just wishlist) :)
+
+We are no thee yet (at all), but see T28.",1420710699,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,Is it possible to get teamwise statistics? (eg: Language Engineering) (Just wishlist) :),1420701318,PHID-USER-abr5ge6gl2ovg7jokpst,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"The report send on January 1 looks good! Thank you very much. I have [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-January/079999.html | forwarded it to wikitech-l ]], wondering whether there is a way to sending it there automatically.
+
+Also, would it possible to generate one report for November 2014? It's the month of the Bugzilla migration and any data needs to be taken with a big grain of salt. Still, having Bugzilla data until October and Phabricator data from December, it would be good to cover November for posterity.",1420700674,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,♥! Thanks Dzahn!,1419343197,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"resolving per: ""This task can be closed as soon as we can publish monthly metrics for total amount of users and active in the past month.""",1419342160,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Quim said:  ( for some reason I can't hit ""quote"" on his comment)
+>Is it possible to add these to the report?
+>Number of accounts created
+
+This has been added now with  https://gerrit.wikimedia.org/r/#/c/181564/
+
+""Number of accounts created in (2014-11): 299""
+",1419341992,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Change 181564 merged by Dzahn:
+phab metrics: add number of accounts created
+
+[[https://gerrit.wikimedia.org/r/181564]]",1419341847,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Change 181564 had a related patch set uploaded (by Dzahn):
+phab metrics: add number of accounts created
+
+[[https://gerrit.wikimedia.org/r/181564]]
+
+#patch-for-review",1419341700,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#939636, @Aklapper wrote:
+> @dzahn: Does that require a separate ticket, or how to proceed?
+
+It does, but it already exists. I reopened T78311 with the additional requirement and it's linked here as a blocker.",1419252608,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#852987, @Dzahn wrote:
+> Access denied for user 'phstats'@...  [...] This requires a change in DB GRANTS.
+
+@dzahn: Does that require a separate ticket, or how to proceed?",1419252523,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>>! In T1003#851249, @Aklapper wrote:
+>> Uh, //daily//? The idea was monthly (see topic), otherwise the queries using INTERVAL 1 MONTH would likely create some weird results. :)
+
+The cron job is changed now to run on the 1st of every month:
+
+Puppet Name: phabstatscron_communitymetrics
+0 0 1 * * /srv/phab/tools/community_metrics.sh
+
+The third field is ""day of the month"".
+
+
+",1418816090,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>>! In T1003#851249, @Aklapper wrote:
+>> Uh, //daily//? The idea was monthly (see topic), otherwise the queries using INTERVAL 1 MONTH would likely create some weird results. :)
+
+The cron job is changed now to run on the 1st of every month:
+
+# Puppet Name: phabstatscron_communitymetrics
+0 0 1 * * /srv/phab/tools/community_metrics.sh
+
+The third field is ""day of the month"".
+
+
+",1418816067,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#852435, @Aklapper wrote:
+> but using $sql_name in the script won't work here as that is on the ""phabricator_user"" DB instead.
+
+Access denied for user 'phstats'@...  The phstats user (and also the phuser user) don't have access to the ""phabricator_user"" database, only to the ""phabricator_maniphest"" database. This requires a change in DB GRANTS.",1418815860,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#852435, @Aklapper wrote:
+>>>! In T1003#851771, @chasemp wrote:
+>> can I get on this list?
+> 
+> You need to bribe mutante.
+
+No, there's no need for bribes. It's an exim alias defined in the private puppet repo.
+
+@palladium:~/private/modules/privateexim/files/wikimedia.org
+
+commit 38f50add7650b9ab524a7a7202bf6a3226a9d695
+
+done:  dzahn: add Chase to communitymetrics@ alias",1418814889,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"```
+Hi Community Metrics team,
+
+this is your automatic monthly Phabricator statistics mail.
+
+Number of active users (any activity) in (2014-11): 433
+Number of task authors in (2014-11): 269
+Number of users who have closed tasks in (2014-11): 115
+Number of tasks created in (2014-11): 1841
+Number of tasks closed in (2014-11): 814
+Number of tasks in the shell project closed as resolved,fixed in (2014-11): 4
+
+Number of open and stalled tasks in total: 17463
+
+Median age in days of open tasks by priority:
+Unbreak now: 130
+Needs Triage: 143
+High: 206
+Normal: 444
+Low: 683
+Needs Volunteer: 545
+
+TODO: Numbers which refer to closed tasks might not be correct, as described in T1003.
+
+Yours sincerely,
+Fab Rick Aytor
+
+(via community_metrics.sh on iridium at Tue Dec 16 15:50:10 UTC 2014)
+```
+
+>>! In T1003#851249, @Aklapper wrote:
+>>>! In T1003#850735, @Dzahn wrote:
+>> let me know if you don't receive it daily from now on
+> 
+> Uh, //daily//? The idea was monthly (see topic), otherwise the queries using INTERVAL 1 MONTH would likely create some weird results. :)
+
+-->   https://gerrit.wikimedia.org/r/#/c/180444/
+
+",1418814706,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#851771, @chasemp wrote:
+> can I get on this list?
+
+You need to bribe mutante.
+
+>>! In T1003#851812, @Qgil wrote:
+> Is it possible to add these to the report?
+
+Should be. A bit late so dropping that here instead of cooking up a Gerrit patch directly:
+
+>> Number of accounts created
+
+SELECT COUNT(id) FROM user WHERE FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+but using $sql_name in the script won't work here as that is on the ""phabricator_user"" DB instead.
+
+>> Number of users logging
+
+Already covered by ""Volume of contributors (any activity) in last month"" already, I think? If not, what's the 𝝙? 
+There's a ""dateMotified"" column but not sure what that really refers to, probably not helpful.",1418788051,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Is it possible to add these to the report?
+
+> Number of accounts created
+> Number of users logging
+
+And I agree with @Nemo_bis, sending this email to wikitech-l every month would be great.",1418767726,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,can I get on this list?,1418767095,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,This is just great. I'm so happy. Thank you!,1418766184,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#850735, @Dzahn wrote:
+> let me know if you don't receive it daily from now on
+
+Uh, //daily//? The idea was monthly (see topic), otherwise the queries using INTERVAL 1 MONTH would likely create some weird results. :)",1418754282,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"needed one more small fix:
+
+https://gerrit.wikimedia.org/r/#/c/180193/
+
+but now it works, puppet applied it and i tested it.
+
+the communitymetrics@ mail alias should now receive this. (currently qgil and aklapper)
+
+i ran it once manually for you to get it now without having to wait for the cronjob.
+
+let me know if you don't receive it daily from now on",1418745354,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"merged PS10 https://gerrit.wikimedia.org/r/#/c/177792/
+
+puppet-compiler: http://puppet-compiler.wmflabs.org/558/change/177792/html/iridium.eqiad.wmnet.html
+
+on iridium:
+
+Notice: /Stage[main]/Role::Phabricator::Main/Phabricator::Logmail[communitymetrics]/Cron[phabstatscron_communitymetrics]/ensure: created
+Notice: /Stage[main]/Role::Phabricator::Main/Phabricator::Logmail[communitymetrics]/File[/srv/phab/tools/community_metrics.sh]/ensure: created
+",1418744156,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Change 177792 merged by Dzahn:
+phabricator: community metrics stats mail
+
+[[https://gerrit.wikimedia.org/r/177792]]",1418743166,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#850592, @Aklapper wrote:
+> Works locally. Now waiting for Daniel to trigger another test email to me.
+
+yep, works for me. i ran it on iridium and triggered the test email
+",1418741492,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"I've added a few more patchsets / revisions to https://gerrit.wikimedia.org/r/#/c/177792/ :
+* worked around (fixed?) the two empty SQL query results by setting an empty column name via AS ' '
+* added the way more performant ""median age of open tasks by priority"" queries (see last comment)
+* removed backticks surrounding one variable to not get an invalid SQL query error for the median-age queries when calling those SQL queries from a bash script, works also as expected without them
+* as the new median-age queries' output is a float instead of an integer, cut the .0000 resp .5000 suffixes so there's no ""invalid arithmetic operator"" syntax error anymore
+
+Works locally. Now waiting for Daniel to trigger another test email to me.",1418740899,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#850332, @Aklapper wrote:
+> * For unknown reasons (those SQL queries work locally, maybe the  //cut -d "" "" -f3// in the script itself but hard to imagine), the following two values in that email are just empty: 
+> ** Number of tasks created in (2014-11): 
+> ** Number of open and stalled tasks in total: 
+
+when i run the query for ""tasks created"" directly on the database i get this:
+
+
+```
+MariaDB MISC m3 localhost phabricator_maniphest > SELECT COUNT(*) FROM maniphest_task WHERE 
+    ->     FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
++----------+
+| COUNT(*) |
++----------+
+|     1841 |
++----------+
+
+```
+
+in the script the variable $result_taskscreated"" becomes this though:
+
+""created: COUNT(*)
+1841"" 
+
+i added the "" , but the variable contains COUNT(*) and the line break and then the actual value.",1418734902,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Status update:
+* Daniel triggered a ""Phabricator monthly statistics"" test email to my account last week.
+* For unknown reasons (those SQL queries work locally, maybe the  //cut -d "" "" -f3// in the script itself but hard to imagine), the following two values in that email are just empty: 
+** Number of tasks created in (2014-11): 
+** Number of open and stalled tasks in total: 
+* Daniel had to kill the queries I had pasted above under //Median age of open tasks by priority// as they have a horrible runtime. Yesterday I created 2500 tasks in local Phab instance and it already took 50-75sec so I stole [[ http://stackoverflow.com/questions/1291152/simple-way-to-calculate-median-with-mysql/7263925#7263925 | a better query from stackoverflow ]]. Output difference is small enough as we're talking about days here. Comparison below.
+** Output isn't an integer though, hence the //epochnow-mediantasksopen_needsvolunteer_epoch// part in https://gerrit.wikimedia.org/r/#/c/177792/7/modules/phabricator/templates/community_metrics.sh.erb to calculate the delta between current time and the output value might bark if it expects integers? Don't know, didn't have time to test with an actual similar shell script yet and my bash script times are long ago.
+```
+MariaDB [phabricator_maniphest]> SELECT x.dateCreated from maniphest_task x, maniphest_task y WHERE (x.priority = ""80"" AND x.status = ""open"") GROUP BY x.dateCreated HAVING SUM(SIGN(1-SIGN(CAST(y.dateCreated AS SIGNED)-CAST(x.dateCreated AS SIGNED))))/COUNT(*) > .5 LIMIT 1;                           +-------------+
+| dateCreated |
++-------------+
+|  1418715703 |
++-------------+
+1 row in set (59.33 sec)
+
+MariaDB [phabricator_maniphest]> SELECT avg(t1.dateCreated) as median_val FROM (SELECT @rownum:=@rownum+1 as `row_number`, d.dateCreated FROM maniphest_task d, (SELECT @rownum:=0) r WHERE (d.priority = ""80"" AND d.status = ""open"") ORDER BY d.dateCreated) as t1, (SELECT COUNT(*) AS total_rows FROM maniphest_task d WHERE (d.priority = ""80"" AND d.status = ""open"")) as t2 WHERE 1 AND t1.row_number IN ( floor((total_rows+1)/2), floor((total_rows+2)/2));
++-----------------+
+| median_val      |
++-----------------+
+| 1418715752.0000 |
++-----------------+
+1 row in set (0.24 sec)
+```",1418733503,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#844983, @kevinator wrote:
+> This might be a cheap way to get a visualization of the data.
+
+Thanks. We might play with this once we have the actual queries in place and their text output working.",1418733497,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"When I saw the wiki with [[ https://www.mediawiki.org/wiki/Talk:Community_metrics#Bugzilla_stats | number of active bugzilla users ]],  I wondered if you knew about the graph extension that lets you embed graphs into wiki pages.  This was also an excuse for me to play with the extension:
+
+bugzilla users: https://www.mediawiki.org/wiki/Talk:KLeduc_(WMF)/test_graph_extension
+the data: https://www.mediawiki.org/wiki/Talk:KLeduc_(WMF)/test_graph_extension_data
+the extension: https://www.mediawiki.org/wiki/Extension:Graph
+
+This might be a cheap way to get a visualization of the data.
+",1418420262,PHID-USER-p3bvg5sos3lhe33uou2s,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Change 177792 had a related patch set uploaded (by Nemo bis):
+phabricator: community metrics stats mail
+
+[[https://gerrit.wikimedia.org/r/177792]]
+
+#patch-for-review",1418297404,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"> start humble with sql queries
+
+Speaking of which. As the Bugzilla weekly report is no more :[, this update could be sent directly to wikitech-l and called ""Phabricator monthly report"", with an expectation that new content might be added to it later (or not).",1418297353,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#821248, @chasemp wrote:
+> There is a ""Fact"" app that is pretty young, but it may make more sense to put our time into that https://secure.phabricator.com/fact/
+
+Upstream told us clearly that it's not worth for us to try to step in to improve Fact or surroundings, before they do some homework in the background. This is one of the reasons why I'm proposing to start humble with sql queries. See https://secure.phabricator.com/T1562#80158 and below.",1417802170,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,https://gerrit.wikimedia.org/r/#/c/177792/,1417798749,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"There is a ""Fact"" app that is pretty young, but it may make more sense to put our time into that https://secure.phabricator.com/fact/",1417787422,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Let's have a separate ticket for some stats app in Phab.
+To avoid confusion:
+This ticket was originally about the cronjob that once a month sent an email with a single number to Quim and me: The number of active users in Bugzilla in the last month.
+We want that for Phab too as we like to have some basic metrics.
+
+As Phab's reporting tools are a bit limited currently and as we have not ported the backend of korma.wmflabs.org to support Phab (see T28) we're now missing some more statistics that we had on korma.
+Hence as a poor man's solution, I'd like to extend that cronjob script by some more sql queries, for the time being. Some of them provide data that we had on korma, though now in a non-visual way, but better than nothing for the time being.
+
+Let's have a potential future ""Stats"" app in Phab either handled in T28, or in a separate ticket. :)",1417783219,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,we could probably create a 'stats' app in phabricator that would provide a simple ui for executing these queries and displaying the data in a reasonably nice way. It would be a significant amount of work but not huge or difficult.,1417647785,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"> Volume of tasks in the ""shell"" project resolved/fixed in last month, requested by Guillaume
+
+Hmm, no, I can't https://phabricator.wikimedia.org/conduit/method/maniphest.query/ see supporting that query either. Meh.
+
+This query seems to work locally for me, but it has the same problem as the other ""closed"" queries above:
+
+SELECT COUNT(DISTINCT objectPHID) FROM maniphest_transaction JOIN maniphest_nameindex JOIN edge WHERE (maniphest_nameindex.indexedObjectName=""shell"" AND maniphest_nameindex.indexedObjectPHID=edge.dst AND edge.src=maniphest_transaction.objectPHID) AND (transactionType=""status"" AND (oldValue=""\""open\"""" OR oldValue=""\""stalled\"""") AND newValue=""\""resolved\"""") AND FROM_UNIXTIME(maniphest_transaction.dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');",1417647449,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Note to myself: Add another query for ""shell requests closed in last month"" for Guillaume as the UI does not offer that and add Guillaume to recipients. (I've also had two other ideas how to get that data but for this one I know it'll work.)",1417618555,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#793868, @Dzahn wrote:
+> Once we are at the point where we have more specific SQL queries you want to be executed and results mailed to people, ping me and I can puppetize that similar to how the BZ mails worked in the past. 
+
+@Dzahn: I hereby ping you. :) 
+If you could put the above SQL queries (which at least worked locally here for me) into a monthly cronjob email like the previous ""bugzilla stats - 2014-10"" ones (we can test now by triggering the one for November), that would be lovely. 
+The last query listed here needs to be included several times to also cover those other x.priority values available.
+And I can probably finetune&review a patch in Gerrit...",1417437909,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Bringing the useful queries here...
+
+>>! In T28#793720, @Aklapper wrote:
+> I'm not patient enough to read API references for Conduit to find out if I can do what I want, so I played with SQL. 
+> Below queries are on the ""phabricator_maniphest"" database and //obviously need a second pair of eyes//.
+> 
+>> Volume of tasks created in last month
+> SELECT COUNT(*) FROM maniphest_task WHERE FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+>> Volume of tasks closed in last month
+> 
+> SELECT COUNT(DISTINCT objectPHID) FROM maniphest_transaction WHERE (transactionType=""mergedinto"" OR (transactionType=""status"" AND (oldValue=""\""open\"""" OR oldValue=""\""stalled\"""") AND (newValue=""\""resolved\"""" OR newValue=""\""invalid\"""" OR newValue=""\""declined\""""))) AND FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+> //Not sure about this one - need to make objectPHID value describing the task ID to be distinct because otherwise every status editwarring counts but not sure if DISTINCT picks the first or the last entry? Other option is to compare with ""maniphest_task.phid"" and ""maniphest_task.status"" but that one has a ""duplicate"" status while in ""maniphest_transaction.transactionType"" that's not a status, see query above.)//
+> 
+>> Volume of tasks open in total
+> 
+> SELECT COUNT(*) FROM maniphest_task WHERE (status = ""open"" OR status = ""stalled"");
+> 
+>> Volume of contributors (any activity) in last month
+> 
+> SELECT COUNT(DISTINCT authorPHID) FROM maniphest_transaction WHERE FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+>> Volume of authors in last month
+> 
+> SELECT COUNT(DISTINCT authorPHID) FROM maniphest_task WHERE FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+>> Volume of resolvers in last month
+> 
+> SELECT COUNT(DISTINCT authorPHID) FROM maniphest_transaction WHERE (transactionType=""mergedinto"" OR (transactionType=""status"" AND (oldValue=""\""open\"""" OR oldValue=""\""stalled\"""") AND (newValue=""\""resolved\"""" OR newValue=""\""invalid\"""" OR newValue=""\""declined\""""))) AND FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+> //Same problem with this query as above for closed tasks.//
+> 
+>> Median age of open tasks by priority (excluding Needs Volunteer)
+> 
+> SELECT x.dateCreated from maniphest_task x, maniphest_task y WHERE (x.priority = ""80"" AND x.status = ""open"") GROUP BY x.dateCreated HAVING SUM(SIGN(1-SIGN(CAST(y.dateCreated AS SIGNED)-CAST(x.dateCreated AS SIGNED))))/COUNT(*) > .5 LIMIT 1;
+> 
+> //Output is a unix epoch of the average *ticket creation time* for that prio so still need to do the math to subtract from today's timestamp and convert to days. x.priority values are: 100=UnbreakNow, 80 = High; 50 = Normal; 90 = NeedsTriage; 25 = Low; 10 = NeedsVolunteer/Lowest. And those two casts in the query are needed to [[ http://dev.mysql.com/doc/refman/5.5/en/out-of-range-and-overflow.html | avoid an overflow ]], at least on my machine.//
+> 
+> Wondering if a dirty monthly script [[ http://git.wikimedia.org/blob/operations%2Fpuppet.git/7cc72ccf87ff2da41009f47727b8461771011634/modules%2Fbugzilla%2Ftemplates%2Fscripts%2Fbugzilla_community_metrics.sh.erb | like the one we had for Bugzilla ]] would give the Engineering Community Team at least basic insight, not expecting shiny stuff like we had on korma to appear soon?
+
+To me this is a no brainer. That dirty monthly script was very useful, and I'm missing it already.",1417295754,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,I'm afraid I pasted some useful queries for this ticket in T28#793720 instead.,1417217249,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Once we are at the point where we have more specific SQL queries you want to be executed and results mailed to people, ping me and I can puppetize that similar to how the BZ mails worked in the past. ",1417214765,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Looking at the metrics proposed in the description, what do you think we could obtain in relation to these dates?
+
+* Opening of the production instance
+* Right before closing for the Bugzilla migration
+* Right after the migration
+* End of November
+* and then, end of every month
+
+We have our #Engineering-Community quarterly review on mid January. I want to bring Phabricator metrics there, because it would be useful, and because it is assured that Lila & co will ask for them.",1417034599,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"After having a very quick look at the database scheme: 
+In the ""phabricator_user"" database, the ""user"" table has ""id"" and ""phid"" columns to identify users. There's also ""dateModified"" and ""dateCreated"" (new registrations) columns with values stored in Unix epoch format (to base timespan queries against). The ""user_log"" table also has a ""dateModified"" column for any user's actions, stored in Unix epoch format. 
+Also wondering if the ""maniphest_transaction"" and ""maniphest_transaction_comment"" tables from the ""phabricator_maniphest"" databases could provide activity data. Need to play more if I find time.",1415566541,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Let's track progress on the migration of this team to Phabricator. Feel free editing this task description.
+
+[ ] Team member assigned to this task
+[ ] Link(s) to the current projects in Mingle, Trello, other
+[ ] (optional) Have you scheduled a team meeting with @Qgil to discuss the migration? (yyyy-mm-dd)
+[ ] Blockers of the migration identified: (list the task numbers between {curly brackets})
+[ ] Planned date for the migration/creation of a first real project: yyyy-mm-dd
+[ ] Do you plan to have all your projects moved by the end of 2014? Yes/No, and if not, why
+(...)
+[ ] More than half of our team members and ongoing sprints are working in Phabricator now (yyyy-mm-dd)
+[ ] All our projects have been moved to Phabricator. Mission completion! (yyyy-mm-dd)",1414050574,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_description,resolved
+Migration of Research & Data to Phabricator,yup,1433943903,PHID-USER-qb5aoo443n6fezsozhv4,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Can we Close Resolved, then?",1433938999,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,Research team is in Phab.  Per @DarTar the remaining Trello boards do not need to be migrated.,1433459928,PHID-USER-boqv2doznygy3kwrkyly,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Thanks, @Spage!
+
+I think that we are done with the Research and Data board from Trello.
+
+We need to groom the Research and Data backlog board and migrate what survives....grooming is scheduled for Thurs 2015-05-21.
+
+@DarTar - does that sound correct?",1431720054,PHID-USER-boqv2doznygy3kwrkyly,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I migrated the Trello columns Completed - In Progress - Incoming requests (external) - Time sensitive - Blocked, and I think Grace has dragged the Phab tasks into shape. Are we done?
+
+𝄞 //We are Phamily, I got all my sisters with me// ♬  – Sister Sledge",1431651486,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I migrated the Trello columns Completed - In Progress - Incoming requests (external) - Time sensitive - Blocked and I think Grace has dragged the Phab tasks into shape. Are we done?
+
+𝄞 //We are Phabily, I got all my sisters with me// ♬  – Sister Sledge",1431651440,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"@Spage  Please migrate Incoming requests (external) and In Progress sequentially and check with me after each import.
+
+Then I can manually create cards fromTime Sensitive and Blocked in Trello in Phab myself.",1431642342,PHID-USER-boqv2doznygy3kwrkyly,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Thanks, @Spage!
+
+I have created column for Staged (ready to execute) in Phab Research and Data board:
+
+1.  moved cards relevant cards from backlog to Staged (ready to execute) column
+2.  reviewed each card and replicated Trello comments that didn't make it over to Phab Research and Data tasks 
+
+Please migrate the next Trello swim lane.",1431625752,PHID-USER-boqv2doznygy3kwrkyly,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I migrated ""Staged (ready to execute)"", e.g. Trello card [[ https://trello.com/c/BNf0xY6P/632-mid-article-recommendation-for-content-translation | mid Article recommendation for Content Translation ]] became T99040. Details on [[ https://www.mediawiki.org/wiki/Phabricator/Trello_to_Phabricator/Research_import | Trello to Phabricator/Research import ]] page.
+
+@ggellerman, @DarTar, step 4 above. Try creating the equivalent column in phabricator and dragging cards, look for obvious errors beyond the missing features mentioned in {T821}, let me know if it's OK to migrate the rest.",1431590979,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"@qgil Search-and-Discovery-Research-and-Data-Sprint is not related to my team, it's an internal board used by the S/D team.
+
+@spage the following are done (copied you)
+
+  # Need list of user name mappings Trello -> Phabricator
+  # Heads up migration is starting
+
+",1431563367,PHID-USER-qb5aoo443n6fezsozhv4,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @ggellerman:
+
+The main Trello board to migrate is [[ https://trello.com/b/k5N0ivoM/research-and-data | Research and Data ]]. Dario moved the one column in the Trello  ""Research and Data - backlog"" board to migrate into this.
+
+# ☑ Need list of user name mappings Trello -> Phabricator
+# ☑Heads up migration is starting
+# ☑ spage migrate one column, probably ""Staged (ready to execute)""
+# ☑ Grace and Dario look at it
+# ☑ Heads up the entire migration is happening
+# ☑ spage migrates the rest
+# ☑ Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research workboard, have tags for specific Research projects like VisualEditor //Xxx research//
+, and then filter the workboard by these tags (workboard > Filter > Advanced Filter... > Projects ) to see the status of particular projects.",1431650926,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @ggellerman:
+
+The main Trello board to migrate is [[ https://trello.com/b/k5N0ivoM/research-and-data | Research and Data ]]. Dario moved the one column in the Trello  ""Research and Data - backlog"" board to migrate into this.
+
+# ☑ Need list of user name mappings Trello -> Phabricator
+# ☑Heads up migration is starting
+# ☑ spage migrate one column, probably ""Staged (ready to execute)""
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research workboard, have tags for specific Research projects like VisualEditor //Xxx research//
+, and then filter the workboard by these tags (workboard > Filter > Advanced Filter... > Projects ) to see the status of particular projects.",1431591048,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @ggellerman:
+
+The Main Trello board to migrate is [[ https://trello.com/b/k5N0ivoM/research-and-data | Research and Data ]]. Dario moved the one column in the Trello  ""Research and Data - backlog"" board to migrate into this.
+
+# ☑ Need list of user name mappings Trello -> Phabricator
+# ☑Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research workboard, have tags for specific Research projects like VisualEditor //Xxx research//
+, and then filter the workboard by these tags (workboard > Filter > Advanced Filter... > Projects ) to see the status of particular projects.",1431575761,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @ggellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# ☑ Need list of user name mappings Trello -> Phabricator
+# ☑Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research board, have tags for specific Research projects, and then filter the workboard to show the tasks in particular projects.",1431575206,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @GraceGellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# Need list of user name mappings Trello -> Phabricator
+# Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research board, have tags for specific Research projects, and then filter the workboard to show the tasks in particular projects.",1431558673,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @GraceGellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# Need list of user name mappings Trello -> Phabricator
+# Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have a big Research board, and then filter ",1431558481,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @GraceGellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# Need list of user name mappings Trello -> Phabricator
+# Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# 
+
+Their plan is to have a big Research board, and then filter ",1431558428,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @GraceGellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# Need list of user name mappings Trello -> Phabricator
+# Heads up migration is starting
+# spage migrate one column
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# 
+
+Their plan is to have a big Research board, and then filter ",1431558313,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I just learned about #Search-and-Discovery-Research-and-Data-Sprint
+
+Progress!",1431002533,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Hi, I'm preparing the Phabricator migration statistics for the #Engineering-Community quarterly review. Currently {T434} reports that your situation with Phabricator is 
+
+  0	  Not started
+
+Is this accurate?",1427461738,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"@Qgil yes we'll definitely need this, I think we're not yet ready though (we need to review the other blockers first and I want to make sure we don't start creating duplicate cards until we're completely ready for the migration).",1425496849,PHID-USER-qb5aoo443n6fezsozhv4,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"If/when you decide to move to Phabricator entirely, will you need migration of Trello cards to Phabricator tasks, aka someone to run {T821}?",1425032994,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I removed Analytics-Engineering because their migration is complete.
+
+Note that ""Restricted Project"" in the task description refers to Analytics Research & Data. Someone tweaked its permissions.
+
+Who should be the owner of this task? It would be good to have a point of contact.",1419856213,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,@Ironholds has started a discussion about [[ https://lists.wikimedia.org/pipermail/analytics/2014-December/002894.html | Analytics Research & Data migrating to Phabricator ]] in the Analytics mailing list. It's a very interesting post that could be extrapolated to most WMF tech teams.,1418591948,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Hi Quim -- we really need the sprint extension to confirm our migration. If this doesn't meet our needs, we'll need to revisit our use of Phabricator.
+
+R&D does not have plans to move off of Trello at this time.
+
+No more teams within Analytics.
+
+-Toby",1418062562,PHID-USER-ud7f5gp5h3uqup6viq4e,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Here are Research & Data Trello boards:
+
+https://trello.com/b/k5N0ivoM/research-and-data
+https://trello.com/b/UcQSC5Au/research-and-data-backlog
+https://trello.com/b/CSltHJXs/research-and-data-archive",1418055207,PHID-USER-boqv2doznygy3kwrkyly,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"In relation to T434,
+
+#Analytics-Engineering looks pretty active. Can we consider this team fully migrated to Phabricator, or are there still tasks / sprints / projects active elsewhere?
+
+#research-and-data seems to be still 100% in Trello. Can you provide a link to access their board(s), please?
+
+Are there more teams within in Analytics?
+
+PS: T1322 is planned for this Wednesday.",1418050182,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"In relation to T434,
+
+#Analytics-Engineering looks pretty active. Can we consider this team fully migrated to Phabricator, or are there still tasks / sprints / projects active elsewhere?
+
+#research-and-data seems to be still 100% in Trello. Can you provide a link to access their board(s), please?
+
+PS: T1322 is planned for this Wednesday.",1418050131,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"As discussed, the scrumbugz style burndowns are blockers for our migration (T1322)
+
+We're excited for this feature! Let us know if we can help.",1417457241,PHID-USER-ud7f5gp5h3uqup6viq4e,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"As per T434 , in the following days I plan to scan the levels of use of Phabricator by all the WMF product & engineering teams. Please keep the description of this task up to date.",1417075841,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Deliver (global version of) VisualEditor newsletter #9 for 2014,,1414000841,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zfix24cb4ecmeq3x62k4,task_description,resolved
+Write VisualEditor newsletter #9 for 2014,,1414000792,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-4kmfp6xox5jr7cpq77bb,task_description,resolved
+Write VisualEditor newsletter #9 for 2014,Checking in to see if this needs to be modified or closed?,1422295464,PHID-USER-v7pv6vw32wp56vc4wyt7,PHID-TASK-4kmfp6xox5jr7cpq77bb,task_subcomment,NA
+Work on the VisualEditor newsletter for November 2014,,1413980113,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-eka3irpvy3o5kqmxjf5b,task_description,resolved
+Work on the VisualEditor newsletter for November 2014,"Change 496060 **merged** by jenkins-bot:
+[pywikibot/core@master] [tests] Fix flake8-tuple T801 error
+
+[[https://gerrit.wikimedia.org/r/496060]]",1552650409,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eka3irpvy3o5kqmxjf5b,task_subcomment,NA
+Work on the VisualEditor newsletter for November 2014,"Change 496060 had a related patch set uploaded (by Xqt; owner: Xqt):
+[pywikibot/core@master] [tests] Fix flake8-tuple T801 error
+
+[[https://gerrit.wikimedia.org/r/496060]]",1552428207,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-eka3irpvy3o5kqmxjf5b,task_subcomment,NA
+Severity information is not being migrated,"We agreed that the Severity information would be printed in the task description, since we decided not to have such field in Phabricator. Currently this information is missing in bugzillapreview. See for instance https://bugzilla.wikimedia.org/show_bug.cgi?id=57540 (Severity: critical)",1413672057,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oymg4uxerfmmmfg76vbm,task_description,resolved
+Severity information is not being migrated,"Available Severity values in Bugzilla are
+* blocker
+* critical
+* major
+* normal
+* minor
+* trivial
+* enhancement
+and there is no conversion; this will just be added to the task description in Phabricator. Severity cannot be unspecified.",1416401407,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"I'm not sure I understand your request. So the only problem here is that you expect that the ""Severity: "" text string is documented in /versus_Bugzilla, reflecting all the possible values, including the case where it is unspecified, right? 
+
+I expect the answer to be
+
+* blocker
+* critical
+* major
+* normal
+* minor
+* trivial
+* enhancement
+* unspecified
+
+I will ask.
+
+The way to retrieve this information is a search query.",1416389124,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Reopen because [[Phabricator/Help]] is silent on severity and [[Phabricator/versus Bugzilla]] only says «Also note that Severity, Version, URL, Whiteboard, and other fields will not be available in Phabricator, because we have decided to discontinue them. The related data available in Bugzilla reports will be added to the description of the task.» Users need documented workarounds to access the information in question, such as the translation between previous and future values that Aklapper implied in https://phabricator.wikimedia.org/T695#12650",1416387949,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"I'm having issues trying to reconcile contradictory indications:
+> Let's drop the string values of ""severity"" (and ""whiteboard"" seems also not to be in yet, looking at bugzilla_create.py) as plain text in the initial description.
+(apparently done) vs.
+> you could always query tasks in project X with the string ""Severity: Critical""
+
+What's the current status? Are we sure that users were actually able to understand how the imported tasks will look like as regards ""Severity"", even though the import was changed after the bugzilla preview? (Cf. T552 which declined the creation of a final preview.)
+
+>>! In T695#13006, @Jdforrester-WMF wrote:
+> Actually, those are indeed untriaged and should be marked as such. :-)
+
+So, if the others are triaged, this leaves us with 568 triaged tickets which received a non-default severity. https://bugzilla.wikimedia.org/buglist.cgi?bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=minor&bug_severity=trivial&bug_severity=enhancement&list_id=359859&priority=Immediate&priority=Highest&priority=High&priority=Normal&priority=Low&priority=Lowest&product=OOjs&product=OOjs%20UI&product=VisualEditor&query_format=advanced&resolution=---
+How is that triaging work being preserved?",1416387680,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,">>! In T695#12650, @Aklapper wrote:
+> [offtopic]
+> 
+> In T695#12014, @Jdforrester-WMF wrote:
+>> I'm not particularly keen to re-triage 2,000 bugs in VE/OOUI/wikitext editor and others…
+> 
+> I would recommend at some point rather sooner than later to (mass-)prioritize those open VE tickets in Bugzilla with Priority=Unprioritized even if that would only be a rough categorization (e.g. set Priority=lowest for open tickets with Priority=unprioritized && Severity=enh|trivial|minor and Priority=low for Priority=unprioritized && Severity=normal|major or whatever works). Otherwise you will end up with a large list of ""Needs triage"" tickets after the Phab migration. Also note that Target Milestones will be migrated which offers another way to plan.
+
+Actually, those are indeed untriaged and should be marked as such. :-)",1413923431,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Trust you and resolve it.  :)
+
+>>! In T695#12822, @chasemp wrote:
+> This is currently:
+> 
+> {F368}
+
+Good!
+
+> What to do w/ this ticket now?
+
+Trust you and resolve it.  :)",1413914978,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"This is currently:
+
+{F368}
+
+
+What to do w/ this ticket now?",1413914778,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"[offtopic]
+
+In T695#12014, @Jdforrester-WMF wrote:
+> I'm not particularly keen to re-triage 2,000 bugs in VE/OOUI/wikitext editor and others…
+
+I would recommend at some point rather sooner than later to (mass-)prioritize those open VE tickets in Bugzilla with Priority=Unprioritized even if that would only be a rough categorization (e.g. set Priority=lowest for open tickets with Priority=unprioritized && Severity=enh|trivial|minor and Priority=low for Priority=unprioritized && Severity=normal|major or whatever works). Otherwise you will end up with a large list of ""Needs triage"" tickets after the Phab migration. Also note that Target Milestones will be migrated which offers another way to plan.",1413878015,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Good catch, sorry for the inconsistency. Let's drop the string values of ""severity"" (and ""whiteboard"" seems also not to be in yet, looking at bugzilla_create.py) as plain text in the initial description.
+
+http://www.bugzilla.org/docs/4.4/en/html/api/Bugzilla/WebService/Bug.html#get
+
+Clueless cargo cult patch in https://gerrit.wikimedia.org/r/#/c/167548/",1413804613,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"What do you want t do with this information? If you want to search candidates for next sprints, and you want to use the Severity information to help you, you could always query tasks in project X with the string ""Severity: Critical"", and that should provide you the sample you are looking for.
+
+I don't think workboards are the right tool for this task. Are you planning to have a VisualEditor workboard where each column corresponds to a severity level? Besides, Workboards are good to handle dozens of tasks anyway, not hundreds.",1413761318,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,">>! In T695#12009, @Qgil wrote:
+> The Severity field is gone for good (and yes, we can document better this fact). This task is simply about adding to the description the Severity value of the Bugzilla reports imported.
+
+I understood that it would be replaced with project board prioritisation. If that's not going to be automatically filled in it's going to be a serious pain. I'm not particularly keen to re-triage 2,000 bugs in VE/OOUI/wikitext editor and others…",1413760753,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"The Severity field is gone for good (and yes, we can document better this fact). This task is simply about adding to the description the Severity value of the Bugzilla reports imported.",1413760435,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Indeed, must not be dropped. See also https://phabricator.wikimedia.org/T102#11218",1413727805,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Hm, actually...
+
+T102#1539 says:
+> I would not migrate Severity as a custom field, but as a searchable text string in the task description.
+
+However, {T259} says
+> Severity: To be dropped, T102
+
+and consequently, https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Bugzilla_data_migrated says 
+> Severity - Not migrated
+
+Considering that we agreed that the latter is the canonical reference, the script works as specified. However, I believe something got lost in the requirements? If we add ""Hardware/OS"" to the description, we might as well add Severity.",1413672681,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Currently these fields are being always printed in the bugzillapreview:
+
+> URL: none
+> Version: unspecified
+> See Also: none
+> Hardware/OS: unknown/unknown
+
+See for instance https://bugzillapreview.wmflabs.org/T6408
+
+If these fields contain just the defaults, they don't offer any information and are pure noise. Can we migrate these fields only when they have specific information (not the default)?
+
+**DECISION**
+
+Fields to always keep in the initial description of a Phab task, no matter what the value is set to:
+* Version
+* Severity
+Fields to drop from the initial description of a Phab task only if set to default value ""All"":
+* Platform/Hardware
+* OS
+Fields to drop from the initial description of a Phab task only if value is entirely empty:
+* URL
+* Whiteboard
+* See Also",1413671789,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-zmu5pfwidjokjny4bfvu,task_description,resolved
+"Print URL, Version, etc only when they contain data",">>! In T694#779001, @Nemo_bis wrote:
+> I'm still seeing ""unspecified"" though. https://phabricator.wikimedia.org/T54136
+
+Consistent with the decision in the description:
+
+> DECISION
+>
+> Fields to always keep in the initial description of a Phab task, no matter what the value is set to:
+> 
+> Version
+> Severity",1416841319,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","I'm still seeing ""unspecified"" though. https://phabricator.wikimedia.org/T54136",1416841090,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","> I compared data of tickets https://bugzillapreview.wmflabs.org/T204 https://bugzillapreview.wmflabs.org/T716 https://bugzillapreview.wmflabs.org/T828 https://bugzillapreview.wmflabs.org/T939 https://bugzillapreview.wmflabs.org/T924 https://bugzillapreview.wmflabs.org/T941 with Bugzilla and all looks perfect to me. Great great great!
+
+All 404 now, but thanks for fixing this, will make things much prettier.",1416388466,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","I compared data of tickets https://bugzillapreview.wmflabs.org/T204 https://bugzillapreview.wmflabs.org/T716 https://bugzillapreview.wmflabs.org/T828 https://bugzillapreview.wmflabs.org/T939 https://bugzillapreview.wmflabs.org/T924 https://bugzillapreview.wmflabs.org/T941 with Bugzilla and all looks perfect to me. Great great great!
+
+Leaving it to Chase to close this ticket as resolved.",1415209917,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Whoops, my thumb must have slipped on the bus.",1415209853,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#19030, @chasemp wrote:
+> Fields not shown:
+> 
+> https://bugzillapreview.wmflabs.org/T11
+
+Looks great. Thank you!",1415208243,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Fields not shown:
+
+https://bugzillapreview.wmflabs.org/T11
+
+",1415205713,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Ignore my last comment; Chase already fixed this in https://git.wikimedia.org/commit/phabricator%2Ftools.git/a0822790ea39f53020ddfdc782e2577ba9ed4289
+
+I think this can be closed, leaving that to Chase.",1415043062,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",@chasemp: https://gerrit.wikimedia.org/r/#/c/170679/,1415014517,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","To summarize the proposal that I can live with: 
+* For ""OS"" and ""hardware"" fields, drop if the value is set to ""All""
+* for ""URL"", ""Whiteboard"", ""See Also"": Drop if field is entirely empty",1414763438,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","> I would go so far as to say that the default values (even ""Severity""==""normal"") should just be dropped, since chances are, no human ever cared enough about it to change it.
+
+Some triagers do, especially correcting by setting the hard to discover ""enhancement"" value. Severity information was explicitly requested in T695 hence I'd always keep it.
+
+> What about keeping Version and Severity in all cases, and the rest only when there is a value different than the default?
+
+I think I've gotten tired of discussing so I can live with that and what Quim proposes here. 
+Wondering if ""the values can be inferred by their absence"" should be ""documented"" on https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla though.
+
+More numbers for completeness, talking about 72760 tickets in Bugzilla:
+* ""Platform"" (Hardware) field ever changed (!) to current default ""All"": [[ https://bugzilla.wikimedia.org/buglist.cgi?f1=rep_platform&o1=changedto&query_format=advanced&v1=All | 2524 tickets ]]
+* ""OS"" field ever changed to current default ""All"": [[ https://bugzilla.wikimedia.org/buglist.cgi?f1=op_sys&o1=changedto&query_format=advanced&v1=All | 2502 tickets ]]
+* In both cases I can imagine that many reporters religiously filled out all fields just describing which OS and Browser s/he used though totally irrelevant for the actually reported bug (and hence set back to default ""All"" when somebody cared about metadata)
+* ""Severity"" field ever changed to current default ""Normal"": [[ https://bugzilla.wikimedia.org/buglist.cgi?f1=bug_severity&o1=changedto&query_format=advanced&v1=Normal | 2109 tickets ]]
+* (Default) Values for ""Version"" are per product and not global, hence no simple numbers.",1414694780,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","What about keeping **Version** and **Severity** in all cases, and the rest only when there is a value different than the default? Reasoning below.
+
+>>! In T694#16895, @Aklapper wrote:
+> 1) We have 4 dropdown fields with pre-defined values. By nature these fields must have one selected pre-defined value set: 
+>  * Version
+
+In fact Version is a hybrid: many products/components don't have a concept of version, and Bugzilla forces the related reports to have the only possible value: ""unspecified"" ([[ https://bugzilla.wikimedia.org/enter_bug.cgi?product=Analytics | example ]]). [[ https://bugzilla.wikimedia.org/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Analytics&product=Commons+App&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s+Tools&product=Logwood&product=Mathoid&product=MediaWiki&product=MediaWiki+extensions&product=MediaWiki+skins&product=MediaWiki-Vagrant&product=MobileFrontend&product=mwEmbed&product=OCG&product=OOjs&product=OOjs+UI&product=openZIM&product=Parsoid&product=Pywikibot&product=QRpedia&product=Spam&product=Tool+Labs+tools&product=Unofficial+Apps&product=Utilities&product=VisualEditor&product=Wiki+Loves+Monuments&product=WikiLoves+Monuments+Mobile&product=Wikimedia&product=Wikimedia+Labs&product=Wikimedia+Mobile&product=Wikipedia+App&product=Wiktionary+tools&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=LATER&resolution=DUPLICATE&resolution=WORKSFORME&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&version=.5&version=1.0.0+%28Android%29&version=1.0.3+%28Android%29&version=1.1.1+%28Android%29&version=1.3.x&version=1.4.x&version=1.5.x&version=1.6.x&version=1.7.x&version=1.8.x&version=1.9.x&version=1.10.x&version=1.11.x&version=1.12.x&version=1.13.x&version=1.14.x&version=1.15.x&version=1.16.x&version=1.17.x&version=1.18.x&version=1.19&version=1.19.0&version=1.19.1&version=1.19.2&version=1.19.3&version=1.19.4&version=1.19.5&version=1.19.6&version=1.19.7&version=1.19.8&version=1.19.9&version=1.19.10&version=1.19.11&version=1.19.12&version=1.19.13&version=1.19.14&version=1.19.15&version=1.19.16&version=1.19.17&version=1.19.18&version=1.19.19&version=1.19.20&version=1.20.x&version=1.21.x&version=1.22&version=1.22.0&version=1.22.1&version=1.22.2&version=1.22.3&version=1.22.4&version=1.22.5&version=1.22.6&version=1.22.7&version=1.22.8&version=1.22.9&version=1.22.10&version=1.22.11&version=1.22.12&version=1.23&version=1.23.0&version=1.23.1&version=1.23.2&version=1.23.3&version=1.23.4&version=1.23.5&version=1.23rc&version=1.24rc&version=1.25-git&version=2.0.21&version=2.1.19&version=2.1.21&version=2.1.22&version=2.1.23&version=3.0.0&version=3.0.1&version=3.0.2&version=3.0.3&version=3.0.4&version=3.0.5&version=3.0.6&version=3.1.0&version=3.1.0+%28iOS%29+%2F+1.1+%28Android%29&version=3.1.1&version=3.1.1+%28iOS%29&version=3.1.2&version=3.1.2+%28iOS%29&version=3.1.3&version=3.1.4&version=3.2.0&version=3.2+%28iOS%29+%2F+1.2+%28Android%29&version=Alpha&version=Android+%28alpha%29&version=Android+%28stable%29&version=Beta&version=Beta+%28Android%29&version=Beta+%28iOS%29&version=compat+%281.0%29&version=core+%282.0%29&version=iOS+%28alpha%29&version=iOS+%28stable%29&version=master&version=REL1_18+branch&version=REL1_19+branch&version=REL1_20+branch&version=REL1_21+branch&version=REL1_22+branch&version=REL1_23+branch&version=Stable&version=trunk&version=wmf-deployment&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap | 22572 reports (31%) have a version other than ""unspecified"" or ""--"" ]]. Well, ok.
+
+>  * Platform/Hardware
+
+[[ https://bugzilla.wikimedia.org/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Analytics&product=Commons+App&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s+Tools&product=Logwood&product=Mathoid&product=MediaWiki&product=MediaWiki+extensions&product=MediaWiki+skins&product=MediaWiki-Vagrant&product=MobileFrontend&product=mwEmbed&product=OCG&product=OOjs&product=OOjs+UI&product=openZIM&product=Parsoid&product=Pywikibot&product=QRpedia&product=Spam&product=Tool+Labs+tools&product=Unofficial+Apps&product=Utilities&product=VisualEditor&product=Wiki+Loves+Monuments&product=WikiLoves+Monuments+Mobile&product=Wikimedia&product=Wikimedia+Labs&product=Wikimedia+Mobile&product=Wikipedia+App&product=Wiktionary+tools&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=LATER&resolution=DUPLICATE&resolution=WORKSFORME&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&rep_platform=Macintosh&rep_platform=PC&rep_platform=Smartphone&rep_platform=Tablet+PC&rep_platform=Other&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap | 4789 reports (6.6%) have a value other than ""All"" ]]. In most cases the hardware is not even relevant, and sometimes reporters specify their hardware just because. I'm fine with migrating the values that were defined, but printing ""Platform/Hardware: All"" in 67.000 tasks is not very useful to the purpose of the task.
+
+>  * OS
+
+[[ https://bugzilla.wikimedia.org/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Analytics&product=Commons+App&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s+Tools&product=Logwood&product=Mathoid&product=MediaWiki&product=MediaWiki+extensions&product=MediaWiki+skins&product=MediaWiki-Vagrant&product=MobileFrontend&product=mwEmbed&product=OCG&product=OOjs&product=OOjs+UI&product=openZIM&product=Parsoid&product=Pywikibot&product=QRpedia&product=Spam&product=Tool+Labs+tools&product=Unofficial+Apps&product=Utilities&product=VisualEditor&product=Wiki+Loves+Monuments&product=WikiLoves+Monuments+Mobile&product=Wikimedia&product=Wikimedia+Labs&product=Wikimedia+Mobile&product=Wikipedia+App&product=Wiktionary+tools&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=LATER&resolution=DUPLICATE&resolution=WORKSFORME&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&op_sys=Windows+8.1&op_sys=Windows+8&op_sys=Windows+7&op_sys=Windows+Vista&op_sys=Windows+Server+2008&op_sys=Windows+Server+2003&op_sys=Windows+XP&op_sys=Windows+NT&op_sys=Windows+2000&op_sys=Windows+ME&op_sys=Windows+98&op_sys=Mac+OS+X+10.9&op_sys=Mac+OS+X+10.8&op_sys=Mac+OS+X+10.7&op_sys=Mac+OS+X+10.6&op_sys=Mac+OS+X+10.5&op_sys=Mac+OS+X+10.4&op_sys=Mac+OS+X+10.3&op_sys=Mac+OS+X+10.2&op_sys=Mac+OS+X+10.1&op_sys=Mac+OS+X+10.0&op_sys=Mac+System+9.x&op_sys=Linux&op_sys=FreeBSD&op_sys=NetBSD&op_sys=OpenBSD&op_sys=Solaris&op_sys=other&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap | 4930 reports (6.8%) have an OS other than the default ""All""]]. Same reasoning as Platform/Hardware. 
+
+>  * Severity
+
+Nothing to say, I agree it should be always specified. It was a relevant field and we are getting rid of it.
+
+> 2) We have 3 free-form text fields which can be entirely empty:
+
+OK. Since I had the calculator at hand, and just to have an idea about the impact...
+
+>  * URL
+
+18% have something
+
+>  * Whiteboard
+
+3.1% have something
+
+>  * See Also
+
+7.6% have something",1414622233,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",Concur with @RobLa-WMF.,1414620033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#16896, @Dzahn wrote:
+> a key without a value is not the same as a key that doesn't exist
+
+Technically, correct.  Practically, *shrug*.  Look at this:
+> URL: none
+> Version: unspecified
+> Severity: normal
+> Whiteboard: none
+> Hardware/OS: unknown/unknown
+> See Also: none
+
+Sure, the keys might exist, but it's academic.  I would go so far as to say that the default values (even ""Severity""==""normal"") should just be dropped, since chances are, no human ever cared enough about it to change it.  It's complete clutter, and in the case that someone really cares, the values can be inferred by their absence.
+",1414617802,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",a key without a value is not the same as a key that doesn't exist,1414616933,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","We are discussing two different types of Bugzilla fields which will be dropped as ""text only"" in the initial description of a Phab ticket imported from Bugzilla (as listed [[ https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Bugzilla_data_migrated | here ]]):
+
+1) We have 4 dropdown fields with pre-defined values. By nature these fields must have one selected pre-defined value set: 
+ * Version
+ * Platform/Hardware
+ * OS
+ * Severity
+2) We have 3 free-form text fields which can be entirely empty:
+ * URL
+ * Whiteboard
+ * See Also
+
+As a compromise between ""correct and complete conversion of Bugzilla data"" vs. ""readability of initial descriptions"" (I know my wording is oversimplifying): 
+Can we agree on 
+1) keeping dropdown fields with pre-defined values (as ""Version: unspecified"" or ""OS: All"" in Bugzilla could be considered information to transfer/preserve)
+2) dropping completely empty free-form text fields from being listed in the initial description of a Phab task (as an empty Whiteboard or See Also field  in Bugzilla could be considered no information to transfer/preserve)
+?",1414616541,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",I agree with James.  Let's just not print the unused fields.,1414465151,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#14606, @chasemp wrote:
+> In regards to the principle of progressive disclosure, this not a phabricator or migration issue.  
+> 
+> https://bugzilla.wikimedia.org/show_bug.cgi?id=68559 looks like this:
+> 
+> {F420}
+> 
+> phabricator looks like
+> 
+> {F422}
+> 
+> 
+> Bugzilla chooses to display fields that have no set value, I assume because an unset field is not the same thing as //no data//.  The current approach is the least surprise approach as it most closely preserves the set of data, set and unset, in the original bug report.  Not liking it is fine, not wanting it shown on issues people are actively working on where the value of this data can be examined is fine.  It can be removed from any description, but the default migrated description would be missing valuable context without it.
+
+I agree that Bugzilla is also crap at this. :-) However, we can and should do better.",1414426713,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",Just for the records I don't have a strong opinion here and don't see an issue with 'empty' values being exposed (or not) in Phab's initial comment...,1414426597,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","In regards to the principle of progressive disclosure, this not a phabricator or migration issue.  
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68559 looks like this:
+
+{F420}
+
+phabricator looks like
+
+{F422}
+
+
+Bugzilla chooses to display fields that have no set value, I assume because an unset field is not the same thing as //no data//.  The current approach is the least surprise approach as it most closely preserves the set of data, set and unset, in the original bug report.  Not liking it is fine, not wanting it shown on issues people are actively working on where the value of this data can be examined is fine.  It can be removed from any description, but the default migrated description would be missing valuable context without it.
+",1414177375,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#14544, @Qgil wrote:
+> One possibility could be: based on the proof of concept that bugzillapreview is, we trust the script, and we will instruct it not to print the unnecessary fields.
+
+So far I've seen no issues at all in the import in terms of missing content, so this seems sensible.",1414170927,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","One possibility could be: based on the proof of concept that bugzillapreview is, we trust the script, and we will instruct it not to print the unnecessary fields.",1414169587,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#12394, @chasemp wrote:
+> We looked at this and decided it is more confusing to have different fields per ticket as it begs the question did this just fail in migration or is it truly not set?  Since descriptions can be cleaned up easily anywhere people do not like this in regards to an active task I am going to mark this as declined.
+
+Although I can understand that decision in the context of the migration, I think it's a huge mistake. This violates the principle of progressive disclosure, and so increases the confusion for non-expert and new members when they're reading each task imported from a Bugzilla bug — tasks which will be around for years to come. Instead, they will all need to be manually updated to remove this cruft. This doesn't feel very respectful of people's time.",1414166587,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Reopening this task only to make sure that people see it before creating a duplicate.
+
+By the way, even if I reported this task, I fully agree with the decision. Makes sense.",1414165839,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",We looked at this and decided it is more confusing to have different fields per ticket as it begs the question did this just fail in migration or is it truly not set?  Since descriptions can be cleaned up easily anywhere people do not like this in regards to an active task I am going to mark this as declined.,1413842621,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Create use cases for two test cluster (""Beta Cluster"" and the yet-to-be-created and yet-to-be-named cluster)","
+Over the past two years, a growing number of teams have come to rely on having unreleased software available for use in the beta labs cluster shared test environment.  The ways that teams use beta labs has become more sophisticated, more diverse, and more important.  Disruption of service or unexpected system behavior on beta labs is therefore quite expensive across all of WMF and the development community. 
+
+At the same time, we need a shared test environment where we can test big risky system-wide software changes in a realistic test environment.
+
+A little history:
+
+Two years ago beta labs was a hodgepodge of symlinks, old versions of core and some extensions, and not much else.  There were no policies at all governing its use. Over time we made it so that beta always ran the latest version of the master branch of code. As beta became more valuable, we instituted one policy there: the only code allowed on beta labs was for extensions and features that already existed in the production cluster. Beta labs has never been a ""wild west"" environment, we have always controlled closely what software runs there. My vision was that beta labs would become the system of record for testing WMF software, and this sort of control is required for beta labs to be such a system.
+
+But as our software matured, it became more feasible to implement large-scale system-wide changes. Beta labs was the only reasonable environment in which to test such large-scale changes.  So we changed the policy: we would allow non-production software on beta labs only if that software had a scheduled release to the production environment. Our first such project in beta labs was CirrusSearch, the next was the Flow extension, then HHVM after that.  Besides these, we have also had some experiments with existing beta labs infrastructure like changing the Varnish cache and changing the database master-slave relationship. 
+
+Every one of these system-wide changes on beta labs has caused significant disruption, down time, and problems for automated testing. 
+
+But that was okay at the time.  Beta labs has always been primarily a target for automated browser tests, and very few teams used it in any meaningful way early in its history. 
+
+But that situation has changed dramatically over the last year or so.  As we discovered when HHVM testing brought down all of beta labs for extended periods of time, almost all of WMF relies on beta labs in one way or another to do their work, from testing bleeding-edge software changes, to public demonstrations of new features, to community engagement.
+
+So we need test environments to serve the parties addressed by both of our previous beta labs policies.  We need to support the latest unreleased changes to software that already exists in production; but we also need a realistic test environment for *unreleased* software with the potential to disrupt the entire cluster.
+
+So I propose two beta-labs-like test environments.  These test environments will not differ in the software features they offer, nor in their nominal response to users, but only in the policies governing their use. 
+
+Both environments would: 
+
+* be updated automatically with the master branch of core and extensions
+* have their databases updated automatically as they are today
+* be the target of automated browser test builds
+* be available to the public as beta labs is today
+* serve as the system of record for software testing and software changes
+
+Conservative beta labs would follow our original maintenance policy: no software or systems in place other than those already released to production.  This would very likely be the existing beta labs cluster, so as to disrupt the teams using it already as little as possible.   The aim of this system would be to supply as reliable a user experience as possible given that the system will be running the master branch of all production code and nothing other than production code. 
+
+Liberal beta labs would follow our amended maintenance policy: software with a projected release to production would be in use here.  If it is not in production already, liberal beta labs would be the place to make it work.  Liberal beta labs might host major changes to cross-cutting systems such as
+
+* Search (affects Core, MobileFrontend, VisualEditor, etc.)
+* System optimizations (HHVM, new caching schemes, major db changes, etc.)
+* New extensions (especially those requiring untested db updates)
+* Any system-wide config change needing testing
+* Potentially, this system could host experiments not destined for a production release, but that exist for research purposes
+
+Testing HHVM proved that we are stretching the capacity and capability of beta labs beyond what we can reliably support.  Having a conservative beta labs test environment for features bound for production would serve our existing users, while having a liberal beta labs test environment where we can manipulate the entire system would serve our future users.
+
+
+",1409872045,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-oh6abcadhuy4bmoaictt,task_description,resolved
+"Create use cases for two test cluster (""Beta Cluster"" and the yet-to-be-created and yet-to-be-named cluster)",//importing issue status//,1410486531,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-oh6abcadhuy4bmoaictt,task_subcomment,NA
+"Create use cases for two test cluster (""Beta Cluster"" and the yet-to-be-created and yet-to-be-named cluster)","**greg** wrote on `2014-09-07 21:15:42 (UTC)`
+
+Copy/pasted to https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Second_Beta_Cluster for historical purposes.",1410486531,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-oh6abcadhuy4bmoaictt,task_subcomment,NA
+"Create use cases for two test cluster (""Beta Cluster"" and the yet-to-be-created and yet-to-be-named cluster)","**cmcmahon** wrote on `2014-09-05 21:38:54 (UTC)`
+
+I think this essay answers the task",1410486531,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-oh6abcadhuy4bmoaictt,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Proposed statuses:**
+
+| **Status name in Phab** | **Explanation** | **Resembling in Bugzilla** |
+| open | Default state | {UNCONFIRMED, NEW, ASSIGNED, REOPENED, PATCH_TO_REVIEW*} {} |
+| stalled | Stalled |  |
+| resolved | A change that fixes the task has been merged. | {RESOLVED, VERIFIED, CLOSED} FIXED |
+| invalid | This is not a task, or it is out of scope in Wikimedia Phabricator. | {RESOLVED, VERIFIED, CLOSED} INVALID |
+| declined | Bad idea, can not be reproduced, missing information has not been provided, or an acceptable alternative exists. | {RESOLVED, VERIFIED, CLOSED} {WONTFIX, LATER, WORKSFORME} |
+| //(marked as duplicate)// | | RESOLVED DUPLICATE |
+
+*For PATCH_TO_REVIEW, create a project and add it to Phab tasks. See T169.
+
+---
+---
+For historical reasons: Initial task description:
+
+By default, Phabricator offers OPEN, RESOLVED, WONTFIX, INVALID as statuses (and we can resolve tasks as duplicates).
+Custom statuses can be added via /config/edit/maniphest.statuses/
+
+Subtasks I see here:
+ * Bugzilla also offers WORKSFORME (CANNOT_REPRODUCE). DO we want this?
+ * NEEDINFO/NEEDS_MORE_INFO: marking an item as not actionable is a recurring request for Bugzilla, see https://bugzilla.wikimedia.org/show_bug.cgi?id=36064
+ * INVALID sounds harsh so we might want to bikeshed on a better wording.",1401463475,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xs7dd22v62cbr3tksryr,task_description,resolved
+Decide which task statuses we want to have in Maniphest,"Stalled, then. Moving on. Thanks!",1415632137,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"FWIW I would just go w/ stalled.  We already use it in one of the originating import system cases, and if it is truly an issue we can revisit at a later date.",1415631087,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"""Paused"" is an alternative, sometimes appropriate, other times it's not: ""Paused"" feels more voluntarily put in waiting than ""Stalled"" does. But sometimes that's exactly what we want/mean.
+
+I don't particularly care that much, and I don't want to get into bikeshedding over this. All of this is better than the more specific ""Needs info"" IMHO.",1415628312,PHID-USER-hovi6c77qompv5qd7gtz,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"The (small) problem I see with ""Stalled"" is that it is a bit of an idiom that might confuse our international and/or non-tech userbase.
+
+A synonym of Stalled that would rhyme with Resolved, and Declined is ""Paused"". The more I see it, the better I prefer it over ""Waiting"". What do you think?
+
+Whatever it is, will be decided latest by our meeting on Monday.  :)",1415575943,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"In my brain ""Needs info"" vaguely translates to ""blocked on somebody or something"" which is close enough to ""Stalled"" or ""Waiting"". Both works for me.
+
+We need to document that well, otherwise people might come up with interpretations like ""I'm waiting for a developer to take a look at this and fix this!!!"" or such. ;)",1415381073,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"I agree that ""Needs Info"" can be renamed to something more generic. Also, we put a lot of effort trying to reduce the number of options for Status and other selectors compared to Bugzilla, and this is why you can feel my resistance to add a new status. Nothing against RT practices personally.
+
+So what about ""Waiting"". This would mark tasks as ""Open, Waiting"", showing clearly that even if the task is assigned and has ""Unbreak Now!"" priority (hypothetical extreme case"", the owner explicitly cannot do anything but wait for another event. Then we can define the reason for the wait via tags or workboard columns, tbd and in the ways that works better for every team.
+
+@aklapper, does this work for you?",1415379886,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"Hmm, maybe, we can experiment with it.
+
+I do think that ""Needs Info"" is a rather specific case of a status for a ticket which can't progress, wouldn't it be better to use something more generic (like stalled)?",1415378433,PHID-USER-hovi6c77qompv5qd7gtz,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"Have you considered using column workboards for these specific conditions? Then the label of the column appears in the description of the task. Like here, above, you can see ""(Need Discussion)"" now, you would have al the flexibility to decide other conditions your tasks are stuck on i.e. ""Stalled"".
+
+Also for what is worth, I have been thinking about proposing tags like ""2015-03"" to denote tasks that need to be acted upon at a certain point in the future, but not now.",1415378213,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"In RT we actually use ""Stalled"" sometimes, with meaning which is quite different from ""Needs Info"". Needs Info implies we're waiting on someone to provide info to be able to make progress with a bug.
+
+""Stalled"" for us can mean things like:
+
+- Waiting on a 3rd party to do/implement/deliver something (vendor or whatever)
+It's not really ""needs info"", it's also not blocked on a task we can resolve ourselves, but we can't make progress on this task either
+
+or
+- We're going to do this, we keep track of it, but the right time (or some other precondition) for it hasn't come yet
+For example, ""decommission server X at date Y."" Of course, in some such cases, being able to list the precondition (such as a defer date) in ticket metadata would be even better.
+
+Since ""Stalled"" is more generic than ""Info"" and can be used for a wider variety of things, we'd still like to have this status available for our projects...
+
+
+
+
+
+",1415376893,PHID-USER-hovi6c77qompv5qd7gtz,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,This one is implemented as well. Sorry for the noise.,1410984349,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,//importing issue status//,1410485871,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-08-18 21:20:42 (UTC)`
+
+Re last comment: We renamed some statuses in this fab.wmflabs.org instance to ""implement""/reflect the decisions made in T359, and we realized that when a status (in this case the previously existing WONTFIX) goes away, Phab resets a task's status to unknown. Next time we know better, and I fixed that manually now to not run into inconsistencies for T336.",1410485871,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-08-18 21:16:06 (UTC)`
+
+Currently we can see messages talking about tasks moving `from ""Unknown Status"" to ""Declined""`. See for instance at the end of T432. What is this ""Unknown Status""? Looks like it's ""Open"", although maybe there is another factor in play.",1410485871,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-08-15 11:45:56 (UTC)`
+
+Great! 
+
+Task completed? I volunteer documenting this in https://www.mediawiki.org/wiki/Phabricator/Help",1410485870,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-08-14 19:57:33 (UTC)`
+
+tinker...tinker...tinker...I got it to work I think.
+
+I updated the values on this install to match what i have for prod.  this install is kinda of a pain since everthing is a one-off and I can't just use the same config.
+
+anyhoo -- check it out.",1410485870,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-08-14 12:00:39 (UTC)`
+
+Ooops, sorry for resolving accidentally.",1410485870,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-08-14 12:00:11 (UTC)`
+
+Maybe this refers to the value, being different to the string shown in the UI? This instance is showing ""Resolved"", ""Wontfix"", ""Invalid"" in upper case.
+
+If this is the case, we could have ""needsinfo"" as value and ""Needs Info"" as UI string.",1410485869,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-08-13 20:13:01 (UTC)`
+
+trying just ""stalled"" as a needs info alternative",1410485869,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-08-13 20:12:41 (UTC)`
+
+ran into a problem here:
+
+needs_info is a not a valid possible status
+
+%%%[Core Exception/Exception] Key ""needs_info"" is not a valid status constant. Status constants must be 1-12 characters long and contain only lowercase letters (a-z) and digits (0-9). For example, ""open"" or ""closed"" are reasonable choices.%%%",1410485869,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Nemo_bis** wrote on `2014-07-25 19:01:48 (UTC)`
+
+>>! In T359#73, @aklapper wrote:
+> I'd STILL appreciate if no wrong data was entered. ;) Fixed.
+
+After http://fab.wmflabs.org/transactions/detail/PHID-XACT-TASK-xukns75c3p24el7/ it's ok; I have merely copied the official descriptions from mediawiki.org, UNCONFIRMED and REOPENED are practically equivalent now so they should be in the same group.",1410485868,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-24 12:31:01 (UTC)`
+
+I assume good faith when editing the description, but I'd STILL appreciate if no wrong data was entered. ;) Fixed.",1410485868,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-24 11:32:59 (UTC)`
+
+James, I think the statuses and their descriptions listed at the top of this task satisfy your concerns. I agree that we cannot just delete all what is marked Invalid. In fact, Phabricator doesn't bring any need to change the current policy for deleting reports in Bugzilla.
+
+>>! In T359#63, @jdforrester wrote:
+> * ""truly invalid"" – spam reports
+
+These will indeed be unpublished/deleted as soon as they are detected. Maybe we can have a ""Spam"" project in order to allow users to report spam. Then the right team with the right permissions can unpublish them.
+
+> * ""misplaced"" – things filed in Bugzilla which aren't dealt with in Bugzilla
+> * ""overtaken by changes"" – things asking for changes that made sense at the time but don't now
+
+""This is not a task, or it is out of scope in Wikimedia Phabricator."" Clearly ""Invalid"". Will stay.
+
+> * ""mistaken"" – things which are this way by design (more often labelled WONTFIX).
+
+""Bad idea, cannot be reproduced, missing information has not been provided, or an acceptable alternative exists."" Clearly Declined. Will stay.
+",1410485868,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-24 11:17:36 (UTC)`
+
+True! I was looking at the general advanced search instead of Maniphests' advanced search. Problem solved, then.",1410485867,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-24 11:14:45 (UTC)`
+
+>>! In T359#67, @Nemo_bis wrote:
+>> (marked as duplicate)
+> 
+> Can this status be searched?
+
+See ""Status"" section on http://fab.wmflabs.org/maniphest/query/advanced/ - there is an explicit ""Duplicate"" checkbox.",1410485867,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-24 10:37:59 (UTC)`
+
+The status that appears at the top of merged tasks is ""Closed, Duplicate"", so it should be as searchable (or not, see below) as the rest of statuses.
+
+As far as I can see, users can only search tasks by status Open/Closed. At least I can't see a checkbox for the different Closed statuses at the Advanced Search. Querying ""Merged into"" will get you pretty close ([[ https://secure.phabricator.com/search/query/HY2OHkK_zrvW/ | I hope this URL works ]]).
+",1410485867,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Nemo_bis** wrote on `2014-07-24 01:02:24 (UTC)`
+
+> (marked as duplicate)
+
+Can this status be searched?",1410485866,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**jdforrester** wrote on `2014-07-23 16:14:19 (UTC)`
+
+>>! In T359#45, @qgil wrote:
+> |invalid| no historical value will be purged eventually (spam, etc)
+
+This is a pretty big change in semantics – right now, INVALID and WONTFIX are used to distinguish between different shades of declines. I'd roughly categorise them as:
+
+* ""truly invalid"" – spam reports
+* ""misplaced"" – things filed in Bugzilla which aren't dealt with in Bugzilla
+* ""overtaken by changes"" – things asking for changes that made sense at the time but don't now
+* ""mistaken"" – things which are this way by design (more often labelled WONTFIX).
+
+We'll need to make sure people are careful not to use ""invalid"" the way they've been using INVALID. Maybe purging isn't the best idea",1410485866,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-17 23:13:16 (UTC)`
+
+>>! In T359#58, @scfc wrote:
+> A recurring problem in Bugzilla with PATCH_TO_REVIEW as a status is that, as it is used as a flag, when a patch is merged/abandoned, one has to go through all the comments to see if this was the only patch to have triggered setting the flag in the first place (and if it previously was UNCONFIRMED, NEW or ASSIGNED).  A Phabricator replacement should take into account that there is a n:m relationship between bugs and patches and ensure that the UI provides a clear picture of the existence of open patches.
+
+In phase 1 (ie: after we've only transitioned Bugzilla to Phab, not Gerrit), that's out of scope.
+
+For phase 2 (ie: after we've also transitioned Gerrit), that will be implicit in that fact that we use Phabricator :)
+
+You can see a good example of what that looks like on the upstream Phabricator instance where a Task has many Diffs associated with it, and you can quickly see how many are merged/open: https://secure.phabricator.com/T2772",1410485866,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**scfc** wrote on `2014-07-17 22:55:59 (UTC)`
+
+A recurring problem in Bugzilla with PATCH_TO_REVIEW as a status is that, as it is used as a flag, when a patch is merged/abandoned, one has to go through all the comments to see if this was the only patch to have triggered setting the flag in the first place (and if it previously was UNCONFIRMED, NEW or ASSIGNED).  A Phabricator replacement should take into account that there is a n:m relationship between bugs and patches and ensure that the UI provides a clear picture of the existence of open patches.",1410485865,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-17 17:01:14 (UTC)`
+
+@greg...I will forgo my speech on projects and organization :D
+
+But really it's that all projects function as tags at the basic level.  So we make a patch_to_review project and add and remove as appropriate for filtering.",1410485865,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-17 16:31:00 (UTC)`
+
+>>! In T359#55, @Rush wrote:
+> @greg, would it work for you if there was an automated tag for issues in this state for now instead?
+> 
+> so you could go do phab.wm.com/tag/patch_to_review and see all tasks in this status.
+> 
+> That way we don't end up with an unused ticket status in the future, and since it's automated we can ensure consistency.
+
+For me, yeah, probably. How are tags added/removed? I can't seem to find it in ""Edit task""",1410485864,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-17 14:48:37 (UTC)`
+
+@greg, would it work for you if there was an automated tag for issues in this state for now instead?
+
+so you could go do phab.wm.com/tag/patch_to_review and see all tasks in this status.
+
+That way we don't end up with an unused ticket status in the future, and since it's automated we can ensure consistency.",1410485864,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-16 23:33:21 (UTC)`
+
+>>! In T359#52, @qgil wrote:
+> Bugzilla has so many ASSIGNED reports where it is not true that ""someone is actively working on this, check the assignee field for who"".
+
+fwiw: I actively use that as a means to track work my team is doing. Some other projects/components don't have people tending the garden actively.",1410485864,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-16 18:53:44 (UTC)`
+
+so seems like we can mimic this gerrit bot that notifies bugzilla with phab, but without a PATCH_TO_REVIEW  status that step would be replaced by another comment linking to the merged patch?",1410485863,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-16 18:46:35 (UTC)`
+
+Bugzilla has so many ASSIGNED reports where it is not true that ""someone is actively working on this, check the assignee field for who"".
+
+I'd rather have us rely on Open + Assigned To + workboard OR the assignee commenting about their intentions (so nobody else steps on their toes).",1410485863,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-16 17:24:13 (UTC)`
+
+>>! In T359#50, @aklapper wrote:
+>> ""someone is actively working on this, check the assignee field for who""
+> 
+> That's what workboards are for, IMHO?
+
+If the task is in one and only one project, and that project uses workboards (not all will), sure. But if there's any deviation from that, no, not really.",1410485863,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-16 17:13:05 (UTC)`
+
+> The PATCH_TO_REVIEW status in BZ is a hack, I believe,
+
+Yes, it's done by https://gerrit-review.googlesource.com/#/admin/projects/plugins/its-bugzilla set up by qchris and setting up a status looked like the most visible way (in additional to the comment created by that plugin). See http://lists.wikimedia.org/pipermail/wikitech-l/2012-December/065046.html and https://gerrit.wikimedia.org/r/#/c/69843/ for historical data.
+
+> ""someone is actively working on this, check the assignee field for who""
+
+That's what workboards are for, IMHO?",1410485862,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-16 16:53:22 (UTC)`
+
+>>! In T359#48, @Rush wrote:
+> @aklapper can you help me understand more about what you mean by gerrit patch notifications?
+> 
+> I know there is some interaction between bugzilla and gerrit, but haven't used it myself.  
+
+Basically, since there is no tight integration between Gerrit and BZ, all we have is a bot that comments on BZ bugs when there's a new related patch, eg https://bugzilla.wikimedia.org/show_bug.cgi?id=67270#c26 and when said patch is merged eg https://bugzilla.wikimedia.org/show_bug.cgi?id=67270#c27 (and similar message for abandoned). When it comments that there's a related patch, it also changes the STATUS to PATCH_TO_REVIEW.
+
+You get the fancy behavior by including ""Bug: 12345"" at the bottom of the change commit message (right before the change-id gerrit needs at the very bottom).
+
+I personally think there should be an ""in-progress"" or whatever status as well, that says ""someone is actively working on this, check the assignee field for who"". The Gerrit bot could set that status when it has a related patch. (We basically use ""ASSIGNED"" in BZ for that now.)
+
+The PATCH_TO_REVIEW status in BZ is a hack, I believe, because BZ doesn't have a nice way of querying bugs that have linked Gerrit commits associated with a bug. ie: the issue that will be solved when we also transition code review to Phab from Gerrit.",1410485862,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-16 15:25:24 (UTC)`
+
+@aklapper can you help me understand more about what you mean by gerrit patch notifications?
+
+I know there is some interaction between bugzilla and gerrit, but haven't used it myself.  
+",1410485862,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-16 15:01:29 (UTC)`
+
+Since those Gerrit patch notifications are created by a bot, here we could apply the idea of Open + project ""Patches For Review"".
+
+The same bot could remove that project if the patch is merged/abandoned.",1410485861,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-16 13:28:23 (UTC)`
+
+Assuming that ""Declined"" covers both ""sorry but we really could not reproduce"" and ""we are against fixing it"", this is probably the smallest set of statuses one could come up with. Thank you Quim. :)
+
+One aspect left: **Gerrit patch notifications** in Phab in T277 (as long as we have not killed Gerrit in T42): I have no idea yet if or how we want to implement the behavior of the ""Patch to review"" status in Bugzilla. Another status, temporarily until we've fixed T42? (as I have a hard time to imagine notifications triggering changes to a column in a project's workboard, as the naming scheme of columns in per project)",1410485861,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-16 10:38:30 (UTC)`
+
+Ok, we can forget about tag-projects for Day one (and therefore the migration). They can always be added to the process at a later stage if somebody misses them or has a better idea of what to do with them.
+
+I agree that Unreproducible is a variant of Needs Info.
+
+>>! In T359#43, @Rush wrote:
+|open| default state
+|needs_info| stalled
+|resolved| closed
+|invalid| no historical value will be purged eventually (spam, etc)
+|declined|we have decided not too -- even though we could
+
+I agree with these statuses; descriptions to be fine tuned.",1410485861,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-15 20:01:46 (UTC)`
+
+andre as usual you come up with good stuff.
+
+@qgil...I really liked your thoughts, over the evening yesterday tho I became less convinced people would actually do it :)  I think it's a really cool idea within domains for people to utilize, ops could do this for their own stuff, andre could do it too.  Anyone who can ensure their own consistency it would work out for, but I don't feel like the 
+workflow of a task lends itself to the status+project combo being a good default mindset sort for the big 3 or 4 or even 5 cases.  
+
+I think the real difference tho is I don't view invalid as a subset of declined.  I do look at declined tasks as having value in a historical sense, and invalid tasks are really waiting to be purged out when they become cumbersome enough.
+
+I don't see a difference between unreproducible and declined.  Do we not decline as unreproducible?  But in general, if it's a broad enough brush to be it's own bucket.  Fine with me.
+
+I also think, unreproducible could be a form of needs_info.  that probably makes the most sense to me.
+
+Needs triage is a priority right?  Not a status.
+
+needs_info seems kind of odd, why not the suggested [incomplete]
+
+That means the status's would be something like:
+
+|open| default state
+|needs_info| stalled
+|resolved| closed
+|invalid| no historical value will be purged eventually (spam, etc)
+|declined|we have decided not too -- even though we could
+
+-> 
+
+|unreproducible| needs more info to reproduce?  should be merged with needs_info?
+
+
+invalid and declined here are also taking the place of reject which exists in rt.  we do get spam there as well.  
+
+Also, really liking andre's 'resembling' identities for the categories.",1410485860,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-15 17:09:46 (UTC)`
+
+**Generally speaking:** It's all about ""keep it simple and stupid"" vs ""I want to categorize everything"" and finding a good compromise. Before commenting, everybody should question themselves whether they do care a lot about expressing a reason //via task status// and if they really query for tickets and differentiate on that status, or if they can also survive having the reason in a project workboard column or comment only which is harder to search for.
+
+Regarding the proposal to **set projects in addition to the ""Declined"" status**, I've in the meantime gotten afraid that people won't do that. I cannot exactly prove it and the quote refers to fixed issues, but: ""Of course, the developer could change the issue category after resolution---but this happens rarely. In many cases there exists no real motivation to change the issue category once the cause for a problem is found and fixed."" from http://www.st.cs.uni-saarland.de/softevo/bugclassify/paper/icse2013-bugclassify.pdf page 396.
+
+**A status called ""Invalid"":** There are opinions in Mozilla ( http://eaves.ca/2011/07/27/lessons-for-open-source-communities-an-example-for-bug-tracking-more-efficient/ and https://bugzilla.mozilla.org/show_bug.cgi?id=592533 ) that average users who incorrectly filed a support request (configuration, on-wiki gadget issues) as a task/bug report and who are not used to dev workflows/terms, that ""invalid"" can feel derogative, but I really cannot come up with a better term after looking at other issue trackers and their terms, so I naively call it ""Invalid here"" instead of ""Invalid"".
+
+I am probably less afraid of **cluttering the status field** if people //really// want to differentiate reasons for closing. The ~dozen of Bugzillas I sometimes interact with have 5-9 statuses and 6-13 resolutions. Combining that in one field in Phab, I think we're not too bad if we ended up with 7 or 8 task statuses.
+
+**Summary:**
+* Needs Triage
+* Open
+* Needs Info
+* Resolved
+* Invalid Here (resembling ""Invalid"", ""Nothing for a Phab task"", ""Spam"", ""Support request"", ""On-Wiki issue"", ""Upstream it"", ""Works as intended"" etc.)
+* Declined (resembling ""Wontfix"", ""Out of scope"", ""Actively against fixing this"", ""Overcome by events"" etc.)
+* Unreproducible (resembling ""Works for me"", ""Insufficient data"", ""Feedback Timeout"", ""Your computer got hacked by an interwebs virus that displays ads on Wikipedia"" etc.)
+and
+* ""Verified"" as an optional workboard column per $project if $project wants it.",1410485860,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-14 17:01:42 (UTC)`
+
+>>! In T359#40, @Rush wrote:
+> are you suggesting a literal ""out of scope"" project that tasks are added to for this? or that there is a ticket state for which the option would be ""declined - out of project scope'.
+
+The former, but using the project just as a tag. Those tasks will be declined. We can forget about them. No team, sprint, dashboard, etc, will be assigned to those. You can always make elaborate queries if you need them: which tasks were ""Declined"" (Status) as ""Out Of Scope"" (tag-project) in ""Visual Editor"" (project-project)?
+
+> Work-for-me is a terrible state for a ticket to be in as it doesn't mean anything.
+
+Following the proposal above, the migration script should convert Bugzilla's WORKSFORME reports in Declined + project ""Non Reproducible"" tasks. In Bugzilla WORKSFORME sometimes is used as ""what you see as a bug is correct behavior in my eyes"", which is different than ""Non Reproducible"". I would still apply the same rule and leave the old bugs Rest In Peace.
+
+> resolved fixed is less good than resolved closed
+
+For the sake of the migration skip, I would treat both as equal.
+
+> The only thing I feel is a strong point is that invalid is a distinct state for a ticket to be in outside of normal resolution, and it is important to distinguish between this isn't possible and we are not doing this
+
+Declined + project ""Invalid"" for the migration? No matter what, they are still declined tasks. I just want to avoid if possible to have an option in the Status that will not be used in the 92% of cases (if we have to trust Bugzilla stats). Besides, if we dig deeper in the current INVALID reports we will find different reasons to reach to that resolution, including out of scope, spam, poorly written, and more. 
+
+Having one ""Declined"" resolution and specific tag projects allow us to be (optionally) more precise without cluttering the Status field.",1410485859,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-14 16:00:34 (UTC)`
+
+> 
+> Bugzilla-Phabricator mapping:
+> 
+> | Bugzilla | Phabricator |
+> | ----- | ----- |
+> | UNCONFIRMED (default) | Open + Needs Triage (default) |
+> | NEW | Open |
+> | ASSIGNED | Open + Assigned To |
+> | PATCH_TO_REVIEW | Open + Code Revisions |
+> | NEED_INFO | Needs Info |
+> | RESOLVED FIXED | Resolved |
+> | RESOLVED INVALID | Declined |
+> | RESOLVED WONTFIX | Declined + project ""Out Of Scope"" |
+> | RESOLVED WORKSFORME | Declined + project ""Non Reproducible"" |
+> | RESOLVED DUPLICATE | (merged) |
+
+I think this is a stupid question on my part, but are you suggesting a literal ""out of scope"" project that tasks are added to for this? or that there is a ticket state for which the option would be ""declined - out of project scope'.  The first I don't think will work across the gamut just because it's too big of a bucket to be meaningful across all the projects / teams / workflows, etc,.  The second seems like a very specific category of declined? 
+
+Declined does seems more diplomatic than won't fix :)
+
+Work-for-me is a terrible state for a ticket to be in as it doesn't mean anything.  It just means two people had different experiences.  It doesn't mean something needs more work, and it doesn't mean something _doesn't_ need more work.  It's not a task or issue state so much as it could be the genesis of an open/closed state, yet is neither.  It doesn't seem meaningful, and could literally be a less valuable version of NEEDS_INFO.
+
+INVALID = this cannot be done.
+
+And, dear god please forgive me for even bikeshedding to this degree, but resolved fixed is less good than resolved closed (phab default).  Closed is wide enough to include hey we talked about it and decided it's a no, but good question.  Fixed implies changes...maybe only to me...whereas an issue can definitely be moved out of an open state without anything being modified other than a requesters state of mind :)
+
+I think in some cases for resolved subtypes we are trying to cram a lot of information into this basic ticket state that doesn't necessarily fit there.  We could conceivably make a separate ticket field to indicate the resolved reasoning as in.
+
+Resolved....
+
+RATIONALE...wonfix/invalid/fixed/foo/bar/whatever/
+
+The only thing I feel is a strong point is that invalid is a distinct state for a ticket to be in outside of normal resolution, and it is important to distinguish between this isn't possible and we are not doing this",1410485859,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-14 15:13:43 (UTC)`
+
+@Rush was faster than me. I was also about to say that workboards offer all the degrees you need between Open and Resolved.",1410485859,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-14 15:03:38 (UTC)`
+
+could verified be a workboard status rather than a full on issue status?  
+
+some of the team specific workflow can be handled at the alternative abstraction layer I think",1410485858,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-14 14:26:09 (UTC)`
+
+Hmm, same VERIFIED question goes to the VE team, actually (@jdforrester).
+
+<Lydia_WMDE> we do use it for basically acceptance confirmation. ie ideally dev sets it to resolved fixed and then i go and set it to verified. doesn't entirely work atm though
+<andre> the question is probably ""what would you lose if it wasn't available anymore"". Plus VE and Wikidata seem to be the only teams using VERIFIED.
+<Lydia_WMDE> we would lose a second stage of review/confirmation.
+<Lydia_WMDE> so i can live without it but i think we should have it
+<andre> does anybody ever query for VERIFIED specifically (or excluding that from RESOLVED tickets)? What if this was just added as a comment instead?
+<Lydia_WMDE> i query for all resolved fixed ones to go through them and verify
+<andre> so if you could query for resolved tickets and exclude those which have a ""has been verified"" comment, would that also work? :D
+<Lydia_WMDE> doesn't feel very nice/clean
+<andre__> I'm wondering if adding a ""Wikidata verified"" (or so) project instead might work. Need to think about it.",1410485858,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-14 14:16:53 (UTC)`
+
+VERIFIED status in Bugzilla is being used by the Wikidata team - wondering how important it is to them in their development workflow, and if they could live without it for the sake of keeping it simple and stupid. I've pinged Lydia on IRC as I couldn't find an account here.",1410485858,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-14 12:43:56 (UTC)`
+
+@parent5446, if I'm not mistaken, in Bugzilla reports are by default UNCONFIRMED until some action makes them NEW. The equivalent default status in Phabricator is Open + Needs Triage. ""Needs Info"" is a status that must be set manually, therefore it cannot be the default for all new tasks.
+
+@aklapper, adding projects to declined tasks should be optional, and done when such projects help the task and the reporter somehow. Also, adding one tag-project can save you the work of typing a manual comment.
+
+If ""should be fixed in upstream"" means ""we won't work on it"", then it can be Declined + project Upstream, and additionally we could even add a project for the specific upstream e.g. ""Elasticsearch"" if that helps us tracking tasks. We can also have tasks that must be fixed upstream, but our maintainers are planning to work on them, as it is the case already now here with certain Phabricator tasks.",1410485857,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-14 11:30:27 (UTC)`
+
+@qgil: Thanks, this looks really really good indeed (though I wonder a little bit with regard to workflow how tedious it'll be to change task status to Declined plus also add a ""Out Of Scope"" / ""Non reproducible"" project to that task). I guess that ""Out of scope"" would also cover ""should be fixed in upstream"" as it's ""not our bug"".",1410485857,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**parent5446** wrote on `2014-07-11 14:19:18 (UTC)`
+
+@qgil, that looks pretty good. There's just a small error in your mapping table. UNCONFIRMED should map to ""Needs Info"", since, like you mentioned earlier, triage has more to do with the maintainers deciding the priority rather than the bug needing more information.",1410485857,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-11 13:44:43 (UTC)`
+
+Revisiting this topic, I think we can use better the possibilities of Phabricator that were limitations in Bugzilla, requiring all these different types of statuses.
+
+What about this:
+
+* Open 
+* Needs Info
+* Resolved 
+* Declined + optional tag project
+
+""Open"" means that a task is actionable. The rest is defined by its current priority and details like having someone assigned to it, or visible activity in the form of mockups, patches...
+
+""Needs Info"" deserves an own status to raise attention. These tasks may be declined (automagically?) if no info is received after some period.
+
+""Resolved"" means that the task is considered completed.
+
+""Declined"" means that the maintainers are removing the task from the plate. Reasons will differ, but the end result is the same: reporters and other contributors must do some homework if they want to reactivate them. Project tags can be used optionally to catalog tasks that might interest someone. Think of projects like ""Non Reproducible"" or ""Out Of Scope"".
+
+Bugzilla-Phabricator mapping:
+
+| Bugzilla | Phabricator |
+| ----- | ----- |
+| UNCONFIRMED (default) | Open + Needs Triage (default) |
+| NEW | Open |
+| ASSIGNED | Open + Assigned To |
+| PATCH_TO_REVIEW | Open + Code Revisions |
+| NEED_INFO | Needs Info |
+| RESOLVED FIXED | Resolved |
+| RESOLVED INVALID | Declined |
+| RESOLVED WONTFIX | Declined + project ""Out Of Scope"" |
+| RESOLVED WORKSFORME | Declined + project ""Non Reproducible"" |
+| RESOLVED DUPLICATE | (merged) |",1410485856,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**parent5446** wrote on `2014-07-10 17:35:20 (UTC)`
+
+>>! In T359#21, @scfc wrote:
+> This doesn't make sense to me.  In Bugzilla, INVALID is used when someone complains that ""expr 2 + 2"" doesn't output 5 (and it shouldn't), WORKSFORME when the complaint is that it doesn't output 4, but for the triager it does, and WONTFIX if someone wants ""expr 2.1 + 1.9"" to work, but the developers consider this outside the scope of expr.
+
+Agreed with this. WONTFIX, WORKSFORME, and INVALID are all three different, distinct resolutions, each representing a different community consensus concerning the bug reported.
+
+Also, keep in mind that in Bugzilla, all of those (as well as FIXED and DUPLICATE) are not separate statuses, but rather all kept under the umbrella of RESOLVED. In reality, Bugzilla only has five statuses: UNCONFIRMED, NEW, ASSIGNED, PATCH_TO_REVIEW, and RESOLVED (we don't really use VERIFIED, so I left it out). With that in mind, ASSIGNED is really unnecessary in both Bugzilla and Phabricator, and PATCH_TO_REVIEW also is not necessary in Phabricator.
+
+That brings us down to just three statuses: UNCONFIRMED, NEW, and RESOLVED. If there was a way to sub-categorize statuses in Phabricator, that would make things a lot simpler. In the end, though, I think it is necessary to keep the various sub-categories of RESOLVED (there names could be changed; I don't care about the naming).",1410485856,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-06-02 20:26:02 (UTC)`
+
+>>! In T359#22, @avive wrote:
+>>>! In T359#8, @greg wrote:
+>> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+> 
+> Workboards kinda-sorta-coulda support this:
+> {F6450}
+
+Interesting.... That's a hack, but yeah, that could do it.",1410485856,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-06-02 20:25:20 (UTC)`
+
+[removing not useful part of this comment]
+
+Bugzilla is still officially canonical, for the record.",1410485855,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-06-02 18:30:11 (UTC)`
+
+CC'ing those top 10 bug closers listed on http://korma.wmflabs.org/browser/its.html who have an account here:
+
+Are any specific thoughts on task/ticket statuses in Phabricator, based on your experience in Bugzilla?",1410485855,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**avive** wrote on `2014-05-31 20:40:59 (UTC)`
+
+>>! In T359#8, @greg wrote:
+> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+
+Workboards kinda-sorta-coulda support this:
+{F6450}",1410485854,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**scfc** wrote on `2014-05-31 02:25:24 (UTC)`
+
+>>! In T359#16, @qgil wrote:
+> The problem with making ""Needs Info"" equivalent to ""Needs triage"" is that it is difficult to know who to blame. While ""Needs triage"" means that the ball is in the field of the triagers / maintainers, ""Needs Info"" shows that it is he reporter who need to do some homework.
+
+""Need(s) info"" (as a concept) isn't necessarily limited to the reporter.  It can also be used to indicate that input from ops, legal, design, etc. is needed.  In general, it should move a bug from the dashboard of the assignee to that of the designated person.
+
+>>! In T359#12, @qgil wrote:
+> What you are saying is that we can keep the current behavior, just changing the strings:
+
+> * Open --> Open
+> * Resolved --> Resolved
+> * Wontfix --> Not a Bug
+> * Invalid --> Needs Info
+> [...]
+
+This doesn't make sense to me.  In Bugzilla, INVALID is used when someone complains that ""expr 2 + 2"" doesn't output 5 (and it shouldn't), WORKSFORME when the complaint is that it doesn't output 4, but for the triager it does, and WONTFIX if someone wants ""expr 2.1 + 1.9"" to work, but the developers consider this outside the scope of expr.
+
+Also, IMHO in general if Phabricator has a different (default) set of statuses, I would be very hesitant to change them without a very good reason as it will introduce another little unnecessary hurdle for contributors.",1410485854,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**swalling** wrote on `2014-05-30 21:18:28 (UTC)`
+
+Think about the best, most beloved issue trackers currently in use (Trello, for instance). Then compare to Bugzilla, which everyone except random volunteers, Platform, and VisualEditor have pretty much abandoned as their canonical issue tracker. 
+
+Trello and most other good trackers: only two states: archived/resolved or open.
+Bugzilla: too many status, priority, target and other state options to bother counting. 
+
+This should be indicative how you're overcomplicating things. ",1410485854,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**jdforrester** wrote on `2014-05-30 21:02:13 (UTC)`
+
+Steven – Please warn if you're forking the conversation so I don't have to respond in two places! :-)
+
+I agree with Quim and disagree with Steven re. the appropriacy of not having a NEEDSINFO state in terms of user interaction.
+
+I also disagree with Steven re. polluting the ""RESOLVED"" status space with bugs that are not resolved but instead weren't appropriate bugs for whatever reason (like problems with gadgets, configuration mistakes, or issues with a localisation string or whatever else is a problem not tracked in Phabricator).",1410485853,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**swalling** wrote on `2014-05-30 19:31:31 (UTC)`
+
+>The problem with making ""Needs Info"" equivalent to ""Needs triage"" is that it is difficult to know who to blame. While >""Needs triage"" means that the ball is in the field of the triagers / maintainers, ""Needs Info"" shows that it is he reporter >who need to do some homework
+
+Someone needs to be responsible for shepherding a task forward. Adding complexity to the state of tasks doesn't really help. They need to just step up and manage the state of the task. This is why we have maintainers, product managers, bugmeister, and other people in these roles. ",1410485853,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-05-30 19:25:02 (UTC)`
+
+The problem with making ""Needs Info"" equivalent to ""Needs triage"" is that it is difficult to know who to blame. While ""Needs triage"" means that the ball is in the field of the triagers / maintainers, ""Needs Info"" shows that it is he reporter who need to do some homework.",1410485853,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**swalling** wrote on `2014-05-30 19:19:46 (UTC)`
+
+We should strive for absolutely simplicity and as small a number of states as possible. The more choices we provide the more confusing things are for all users. My thoughts, also replicated on the Product list are thus...
+
+> [Updated] proposed set from @jdforrester: 
+>
+>OPEN
+>RESOLVED
+>DECLINED (rather than WONTFIX)
+>NOTABUG (rather than INVALID, also replacing WORKSFORME)
+>NEEDSINFO (consistent with not using ""_""s, INCOMPLETE sounds like it's about the task, not the request)
+
+I don't think we need INVALID/NOTABUG or NEEDSINFO.
+
+INVALID is required when Bugzilla has a ""Resolved fixed"" status. (If something is not a bug, you can't mark it as fixed.)  We just have a resolved state now, and an issue is resolved whether we fix it with a patch or if we investigate and it was never an issue to begin with. 
+
+NEEDSINFO is just adding additional state complexity to Needs Triage. Either leave something in Needs Triage, or triage is as lowest possible priority, while requesting more info. If someone can't provide more info, then mark it as Resolved. 
+
+Declined is definitely better than WONTFIX. I will keep thinking on options there, but would be comfortable using that language. ",1410485852,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-05-30 19:04:51 (UTC)`
+
+What you are saying is that we can keep the current behavior, just changing the strings:
+
+* Open --> Open
+* Resolved --> Resolved
+* Wontfix --> Not a Bug
+* Invalid --> Needs Info
+
+> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+
+Remove the task from ""MediaWiki"" but keep it in ""MediaWiki 1.23.0""?",1410485852,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**jdforrester** wrote on `2014-05-30 18:34:42 (UTC)`
+
+[Updated] proposed set:
+
+  - OPEN
+  - RESOLVED
+  - DECLINED (rather than WONTFIX)
+  - NOTABUG (rather than INVALID, also replacing WORKSFORME)
+  - NEEDSINFO (consistent with not using ""_""s, INCOMPLETE sounds like it's about the task, not the request)
+
+Will validate these with other Product people.
+
+(Do we want to represent PATCH_FOR_REVIEW or DEPLOYED states somehow?)",1410485852,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-05-30 16:27:05 (UTC)`
+
+>>! In T359#10, @jdforrester wrote:
+>>>! In T359#8, @greg wrote:
+>> I don't find ""works for me"" useful. If anything, it should be called ""works, period"" aka ""not a bug"". The ""for me"" part bothers me.
+> 
+> I agree that it's a bit sucky; normally it's used for
+> 
+> 1. ""this is a fault you're experiencing due to something else not in our control"",
+> * ""this may be a fault, but you've given insufficient information to reproduce"", or occasionally
+> * ""this was fixed since it was filed but I don't know exactly how so, so I'm not going to mark as FIXED""
+> 
+> … so use case (2) is no longer needed if we add ""INCOMPLETE"" or ""NEEDSINFO"" or whatever, and case (1) //could// be marked as ""NOTABUG""/""INVALID""; for case (3) we could just be more lax about marking things as FIXED even when we don't know for sure that they are.
+
+Agreed. Or even NotABug for that last one. Doesn't really matter in the long run.
+
+>> I also find ""won't fix"" not useful. If it's not a bug, mark it as such. If it's way low priority, set the priority as such. Since we can have multiple projects in use by a team to track sprints and such, the product owner argument of ""I want a clean backlog"" doesn't apply.
+> 
+> I strongly disagree, and I think the term ""bug"" rather than ""task"" skews this.
+> 
+> There are totally ""valid"" requests for new features or feature enhancements which are incompatible with the direction that we want to take a product (//e.g.// ""Change the FOSS policy for Tool Labs so I can run Windows on it"" or ""Let me upload MPEG files to Commons"" or ""I want to have a button in VisualEditor to block the last editor if there are spelling mistakes""). ""Lowest"" priority for these is totally wrong – these are ""No, we will not do this ever, and we will work to stop other people doing this if they try"".
+
+Those all read like NotABug to me. ""Won't Fix"" is just a special type of NotABug. One that has reasoning based in 'product' versus 'actual code breakage.' It's the same thing in the end.
+
+>> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+> 
+> Yeah, deployment/release statuses would be a lovely nice-to-have, but maybe for post-initial-switch?
+
+Def.",1410485851,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**jdforrester** wrote on `2014-05-30 16:13:58 (UTC)`
+
+>>! In T359#8, @greg wrote:
+> My suggestion for day 1:
+> * Open
+> * Not a bug (instead of ""invalid"")
+> * Incomplete (or Needs more info)
+> * Fixed
+> 
+> I don't find ""works for me"" useful. If anything, it should be called ""works, period"" aka ""not a bug"". The ""for me"" part bothers me.
+
+I agree that it's a bit sucky; normally it's used for
+
+1. ""this is a fault you're experiencing due to something else not in our control"",
+* ""this may be a fault, but you've given insufficient information to reproduce"", or occasionally
+* ""this was fixed since it was filed but I don't know exactly how so, so I'm not going to mark as FIXED""
+
+… so use case (2) is no longer needed if we add ""INCOMPLETE"" or ""NEEDSINFO"" or whatever, and case (1) //could// be marked as ""NOTABUG""/""INVALID""; for case (3) we could just be more lax about marking things as FIXED even when we don't know for sure that they are.
+
+
+> I also find ""won't fix"" not useful. If it's not a bug, mark it as such. If it's way low priority, set the priority as such. Since we can have multiple projects in use by a team to track sprints and such, the product owner argument of ""I want a clean backlog"" doesn't apply.
+
+I strongly disagree, and I think the term ""bug"" rather than ""task"" skews this.
+
+There are totally ""valid"" requests for new features or feature enhancements which are incompatible with the direction that we want to take a product (//e.g.// ""Change the FOSS policy for Tool Labs so I can run Windows on it"" or ""Let me upload MPEG files to Commons"" or ""I want to have a button in VisualEditor to block the last editor if there are spelling mistakes""). ""Lowest"" priority for these is totally wrong – these are ""No, we will not do this ever, and we will work to stop other people doing this if they try"".
+
+
+> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+
+Yeah, deployment/release statuses would be a lovely nice-to-have, but maybe for post-initial-switch?",1410485851,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-05-30 15:58:06 (UTC)`
+
+My suggestion for day 1:
+* Open
+* Not a bug (instead of ""invalid"")
+* Incomplete (or Needs more info)
+* Fixed
+
+I don't find ""works for me"" useful. If anything, it should be called ""works, period"" aka ""not a bug"". The ""for me"" part bothers me.
+
+I also find ""won't fix"" not useful. If it's not a bug, mark it as such. If it's way low priority, set the priority as such. Since we can have multiple projects in use by a team to track sprints and such, the product owner argument of ""I want a clean backlog"" doesn't apply.
+
+Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)",1410485851,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"I don't see a tracking of severity distinct from priority. Considering that priority has no universal meaning, but only a per-component meaning (at best), this seems very inappropriate for a disperse project like ours.
+http://c2.com/cgi/wiki?DifferentiatePriorityAndSeverity
+
+Moreover, the main use we make of ""Priority"" in bugzilla, i.e. how hard/expensive a bug is, is already covered by ""Points"".
+
+----
+
+**See also**: {T93499}",1397888043,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_description,declined
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"@Nemo_bis: You seem to mix up Severity (which had unhelpful non-discrete inconsistent values in Bugzilla like ""blocker"", ""critical"", ""major"", ""normal"", ""minor"", trivial"" and even ""enhancement"") and Task Types for categorization (think ""bug report"" vs ""feature request"").",1567372368,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,">>! In T102#11219, @Nemo_bis wrote:
+> Moreover, it's a huge culture shift. For countless years we've stressed how priority has a relative value (very subject to interpretations and context-sensitive) while severity has at least some very clear and relevant boundaries like feature request vs. bug. If the intention is to change this culture, just renaming or removing a field will not work: people will just talk past each other, each fitting the tool to their own view.
+
+It only took five years but eventually it happened: T93499, T224417#5215068. Maybe in five more years we'll be back to the place where we started, with all the bugzilla functions restored although in a messier way. :)",1567068538,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"For the records, T204138 added a `Risk` field.",1536782988,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"T109492 is rather unrelated to any ""severity"" (except for when you interpret new functionality or maintenance as always either less or more severe than the other one).",1440664451,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"Giving up on the Severity field has caused all sorts of negative consequences, in my opinion. Perhaps this decision should be revised in light of new superstructure which is being added (partly) to compensate the lack of such information, like T109492.",1440662013,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"As Priority was mentioned (though this is about Severity): Story points express estimated complexity and are not directly related to priority. I agree that priority is relative and that severity //in theory// has boundaries if well defined but I don't see a ""change to this culture"". I rather see an overcategorization via many many fields in Bugzilla that are only used by a small number of users hence I challenge the usefulness. One of the fields I consider pretty much useless is ""Severity"", explained above. In this ticket we discussed usecases for the severity field and didn't find many.",1413388287,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"I've read this discussion before, but I still don't understand the decision: either I forgot, or it was uncomprehensible. I'd like a summary of the reasoning to be added to the description of this task and/or documented, because I suspect some of the reasons may have been superseded by other decisions in the meanwhile.
+
+In its current setup, AFAICS, this instance has *three* manual ways to define priority: addition to a project (meaning a group is in theory working on it), workboard (which often says things like ""on hold"", ""next in our plate"" etc.) and points (how expensive is it). This is very confusing and inconsistent with the stated goals of this whole exercise, in particular with the idea of getting rid of the divide between priority field in bugzilla and sprint/roadmap assignments in mingle/trello.
+
+It's not even internally consistent, for instance ""Need volunteer"" is not a level (can't be sorted by any ordering method together with the others https://en.wikipedia.org/wiki/Total_order ), rather a tag/flag i.e. a project, or a workboard within an existing project, or just an expensive task which has no resources yet. So we already have a ""priority"" field which cannibalises other areas of maniphest.
+
+Moreover, it's a huge culture shift. For countless years we've stressed how priority has a relative value (very subject to interpretations and context-sensitive) while severity has at least some very clear and relevant boundaries like feature request vs. bug. If the intention is to change this culture, just renaming or removing a field will not work: people will just talk past each other, each fitting the tool to their own view. Besides, I don't see why we'd need or want to go this direction yet: for instance, there's been a lot of talk lately (mostly around https://meta.wikimedia.org/wiki/Community_Engagement_%28Product%29/Process_ideas and the countless related threads) about regressions vs. newly introduced bugs vs. feature request, and about *increasing* our ability to distinguish among them and measure them. And now we go in the opposite direction, dropping even ""enhancement"" vs. [trivial/minor/normal/major/critical] bug? Again, confusing.
+
+I'm not saying decision-makers here didn't know or consider all of this, they probably did: but I'm unable to tell, or to understand the decision. If you can't, or don't, explain the decision addressing all the topics above, then whatever you decided will not be applied in the reality of the issue tracker.",1413362360,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,//importing issue status//,1410485361,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-08-18 12:50:42 (UTC)`
+
+No replies to last comment, hence assuming that searching for the terms ""crash"" or ""NPE"" (favorized by the mobile app developers) seems to be sufficient for the ""critical severity"" case.
+
+Closing as DECLINED as we don't plan to copy the Severity field from Bugzilla to Maniphest.",1410485361,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-08-10 19:50:00 (UTC)`
+
+Remaining question: Is there interest in converting the ""crasher"" severity to a project/tag in Phabricator, similar to a keyword now in Bugzilla? Do people query explicitly for crashers in Bugzilla by querying for critival severity?",1410485360,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**mmodell** wrote on `2014-08-07 14:19:50 (UTC)`
+
+Also, FWIW: Phabricator has task dependencies to express ""blockers"" in much more useful and informative way... ""T1 blocks T2"" is much more useful than ""severity: blocker"" - that just says it's blocking _something_ but what's blocked?",1410485360,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-07-30 11:21:22 (UTC)`
+
+**tl;dr**
+
+Priority + Impact Tags + Effort points + Sprints is a better combination to plan our work. I would not migrate Bugzilla's Severity field as a custom field in our Phabricator.
+
+In detail:
+
+Considering that we are discussing the steps required before Day 1.
+
+Considering that Severity is supposed to be helpful to plan future sprints or the next task that you will work on.
+
+Considering that we have these priority options agreed for Day 1 (T436):
+
+* Needs Triage
+* Unbreak Now!
+* High
+* Medium
+* Needs Volunteer
+
+And considering that Bugzilla has these Severity options:
+
+* Blocker: 	 Blocks further development and/or testing work.
+* Critical: 	 Crashes, loss of data (internally, not your edit preview!) in a widely used and important component.
+* Major: 	 Major loss of function in an important area.
+* Normal: 	 Default/average.
+* Minor: 	 Minor loss of function, or other problem that does not affect many people or where an easy workaround is present.
+* Trivial: 	 Cosmetic problem like misspelled words or misaligned text which does not really cause problems.
+* Enhancement:    Request for a new feature or change in functionality for an existing feature.
+
+I still think that a Severity/Impact field forced onto all tasks is an overkill that will create more noise than usefulness. Our Bugzilla is a tangible proof. Think also that our Phabricator will not only be open for bugs but for all kinds of tasks. I would not migrate Severity as a custom field, but as a searchable text string in the task description.
+
+If a bug is a ""Blocker"", causes ""Crash"" or ""Data Loss"" (Blocker / Critical in Bugzilla) then we can project-tag them that way, being more specific and not making assumptions like ""It crashes, therefore it has a severe impact on many people"". If a bug blocks development, crashes applications, and destroys data in a bad way, it will be ""Unbreak Now"" or ""High"" priority, a candidate in any sprint planning meeting until it is solved.
+
+Discussing severity/impact Major-Normal, Normal-Minor, and Minor-Trivial is not very different from discussing priority High-Medium or Medium-Needs Volunteer. Basically you are discussing whether a problem is annoying enough to be considered by you / your team soon, some day in the future, or never.
+
+And Enhancement is out this equation anyway, as Andre says.",1410485360,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-07-29 22:14:35 (UTC)`
+
+>>! In T168#60, @aklapper wrote:
+>>>! In T168#57, @jdforrester wrote:
+>> As a product manager, I need an orthogonal way to represent how major an issue/problem/improvement a task is for users, distinct from whatever priority I have currently given it (""priority"") and how difficult it is for engineers to do (""points"").
+>> 
+>> This is vital when considering which tasks should go in each sprint, and reconsidering longer-term prioritisation. It is particularly important for triaging tasks reported by users and others, to gauge which ones to triage first.
+> 
+> How often do tasks go into a sprint which have lower impact (minor or trivial, in current Bugzilla terms)?
+
+All the time. Normally large-impact changes are intentionally rationed per release – both because there's often a strong correlation between size of impact and size of work, but also because we don't want to make too many large changes for users at once. Also, there's a need for balance for both scale and type of workload between individual team members, and within each engineer's workload.
+
+> With regard to longer-term prioritisation: Would that mean it's more likely that you add tasks to a future sprint which had a lower priority but a higher impact/severity?
+
+Yes, though I'd be likely (but not guaranteed) to raise the priority based on impact as well. In general, higher-priority items would be expected to be put into the sprint ahead of equivalent lower-priority ones.
+
+> If so, I'd interpret that as using Severity/Impact to ""subclassify"" tasks sharing the same lower Priority, to bump Priority later based on Severity/Impact. It's a pattern that can also be observed in Eclipse Bugzilla (according to page 4 in http://herraiz.org/papers/english/msr84cp-herraiz.pdf ).
+
+That's a possible analysis, though I think that it's used more as a signal rather than a raw sub-priority field.",1410485359,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-07-29 22:02:35 (UTC)`
+
+>>! In T168#57, @jdforrester wrote:
+> As a product manager, I need an orthogonal way to represent how major an issue/problem/improvement a task is for users, distinct from whatever priority I have currently given it (""priority"") and how difficult it is for engineers to do (""points"").
+> 
+> This is vital when considering which tasks should go in each sprint, and reconsidering longer-term prioritisation. It is particularly important for triaging tasks reported by users and others, to gauge which ones to triage first.
+
+How often do tasks go into a sprint which have lower impact (minor or trivial, in current Bugzilla terms)?
+
+With regard to longer-term prioritisation: Would that mean it's more likely that you add tasks to a future sprint which had a lower priority but a higher impact/severity? If so, I'd interpret that as using Severity/Impact to ""subclassify"" tasks sharing the same lower Priority, to bump Priority later based on Severity/Impact. It's a pattern that can also be observed in Eclipse Bugzilla (according to page 4 in http://herraiz.org/papers/english/msr84cp-herraiz.pdf ).",1410485359,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-07-29 21:51:47 (UTC)`
+
+>>! In T168#56, @Waldir wrote:
+> I stand by my proposal to have a severity/impact dual-axis priority measure, with the highest priority items at the top right of the resulting space.
+
+I'd like to see this in practice somewhere. It could work but I haven't see any tool implementing this.
+
+> I agree the current definition of severity isn't ideal, but it's certainly a good start.
+
+I don't see how it's ""a good start"".
+
+> For example, the ""important area to whom"" question can be defined, say, in terms of the WMF's strategic goals, or the Engineering team
+
+If the several stakeholders can somehow agree on something, okay. Again, designers might have a different interpretation of ""major issue"" than a performance engineer (maybe a bad example if it's unlikely that one bug report will touch both design and performance).
+
+> getting rid of the ""unspecified"" value
+
+(The Severity field in Bugzilla has no ""unspecified"" value - that's the Priority field.)
+
+> and assigning a mid-range value by default (maybe ""enhancement"", based on the 60% number cited above?) could help here.
+
+Enhancement will be expressed by the ""Priority"" value ""Wishlist"" in Phabricator. Also, ""enhancement"" is unrelated to any Severity/Impact. Instead it is a boolean value on its own. (That enhancement request to replace the joystick by a steering wheel in the car that we produce can be pretty severe if all other competitors ship that already and if we'd go bankrupt). It is wrong that Bugzilla has ""enhancement"" as a value in its Severity field.
+
+> I proposed impact as a measure of how many people the issue annoys.
+
+I don't see how ""many people"" can be defined. Estimation must be based on something, otherwise I'd call it wild guessing.
+
+> I just think two reasonably objective measures with sane defaults are better than a single, subjective priority measure that we often won't be able to agree on
+
+I miss how to concretely achieve such ""objective measures"" because currently we don't have them. If you can draw such concrete values and add them to the discussion here, that would be awesome. Right now it feels like ""things aren't great, we can improve them"" but I don't see a clear and specific proposal. And I miss why it's ""better"" - usecases.",1410485358,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-07-29 21:32:21 (UTC)`
+
+I also completely disagree with @aklapper about getting rid of some measure of severity/impact, as already stated.
+
+As a product manager, I need an orthogonal way to represent how major an issue/problem/improvement a task is for users, distinct from whatever priority I have currently given it (""priority"") and how difficult it is for engineers to do (""points"").
+
+This is vital when considering which tasks should go in each sprint, and reconsidering longer-term prioritisation. It is particularly important for triaging tasks reported by users and others, to gauge which ones to triage first.",1410485358,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Waldir** wrote on `2014-07-29 20:45:25 (UTC)`
+
+**tl;dr** I stand by my proposal to have a severity/impact dual-axis priority measure, with the highest priority items at the top right of the resulting space.
+
+I agree the current definition of severity isn't ideal, but it's certainly a good start. Nothing prevents us from working up it. For example, the ""important area to whom"" question can be defined, say, in terms of the WMF's strategic goals, or the Engineering team; and ""trivial"" could be removed since it's a measure of effort, not severity. Other improvements are certainly possible.
+
+Then there's the issue of us actually making use of it; getting rid of the ""unspecified"" value and assigning a mid-range value by default (maybe ""enhancement"", based on the 60% number cited above?) could help here.
+
+> So I guess I believe that impact (severity? frequency?) influences priority
+I proposed impact as a measure of how many people the issue annoys. Severity can be measured separately, as mentioned above, and frequency isn't really a factor in our case: bugs that appear to occur randomly are usually just those that occur under a (yet unknown) set of conditions. Instead, a simple scale based on an rough estimation of how many users are affected could work well.
+
+> An uncommon feature request won't happen and will be lowest priority as long as nobody works on it, and if somebody considers a feature crucial, s/he will assign it to her/him and its priority will be raised.
+
+These (mostly the first) seem to me like effects of an ""impact"" metric. The second scenario is true whatever the priority defined for the bug so it's irrelevant if we want a measure that's as objective as possible (i.e. predicts how soon the issue is addressed). Using the criteria that are already implicitly in use, as Quim mentions above, seems like the best way to do this.
+
+Note that I don't mean to simply cling to my previous position; I just think two reasonably objective measures with sane defaults are better than a single, subjective priority measure that we often won't be able to agree on, and tokens which depend strongly on the number of stakeholders that actually participate on the bug tracker (which historically has been very low and biased toward the more tec).",1410485358,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-07-28 20:33:10 (UTC)`
+
+I take the silence as people agreeing on my last comment. If not, please raise your voice before it's too late.",1410485357,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-07-15 23:51:33 (UTC)`
+
+**<tl;dr>:** My current position is that we do not need a general Severity or Impact field, but I'm welcome to hear more arguments, and I'd be fine with defining clear, isolated usecases for queries (and how they support our software development processes) that we might want to implement in some way (e.g. a ""crasher"" project, or via defining tokens as mentioned by Mukunda).
+
+**Long version:**
+
+Severity is only objective and informative if its values are clearly defined (see https://www.mediawiki.org/wiki/Bugzilla/Fields#Severity for our attempt which isn't too great) **and** if it is consistently used. Both is often not the case.
+
+Currently in Bugzilla, ""normal"" severity can mean anything. For ""major"", ""Major loss of function in an important area"" already has two subjective terms - what's important to you and me? An issue can be ""minor"" or ""trivial"" severity (what's the difference?) to fix when it's a typo, still a typo can trigger a crasher (defined as ""critical"" severity in Bugzilla and hence conflicting).
+
+While Wikimedia Bugzilla is one of those instances which set ""unspecified"" severity by default, it's been shown that reporters often keep the default value set by ignoring yet another field (see http://ansymo.ua.ac.be/~alamkan/wp-content/papercite-data/pdf/lamkanfi2010msr.pdf page 2), hence up to 60% of reports in some Bugzillas are misclassified as people did not find the ""enhancement"" value hidden in there and instead write ""RFE"" in the bug summary (see page 4 of https://www.st.cs.uni-saarland.de/softevo/bugclassify/paper/icse2013-bugclassify.pdf ).
+
+Currently I don't even believe currently that differentiating feature requests/enhancement and bugs make much sense because it's often impossible to draw the line (I won't drop the four quotes from papers now). An uncommon feature request won't happen and will be lowest priority as long as nobody works on it, and if somebody considers a feature crucial, s/he will assign it to her/him and its priority will be raised. So I guess I believe that impact (severity? frequency?) influences priority, among other things like ""cost of fixing"" and ""risk of fixing"" (which we didn't express via fields so far either in Bugzilla, but we got points in Phabricator). For the records, I stole these criteria from http://www.ericsink.com/articles/Four_Questions.html.
+
+If you like querying for critical and blocker bugs not just for academical reasons (though again I must warn that any bug report numbers depend first on ""the number of users using the software, and the convenience with which those users can register new bugs"" and only to lesser extend on ""the absolute number of bugs present in the software"", to quote page 26-27 from Karl Fogel's ""Producing Open Source Software"" from 2006), I would honestly love to know the usecase, and we could for example set up a ""crasher"" project, cross-codebase, or play with tokens.
+
+(PS: Yes, I like to base decisions to some extend on science as we're not the first people running into these questions.)",1410485357,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**mmodell** wrote on `2014-07-15 22:35:23 (UTC)`
+
+Phabricator's tokens are a perfectly good way to represent ""impact"" - people can individually assign tokens to express the impact that a given bug is having on them and the tokens are prominently displayed on the task with representative icons. We just need to assign some meanings to the tokens, more explicitly than they currently have in the UI.",1410485357,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Waldir** wrote on `2014-07-15 17:08:44 (UTC)`
+
+>>! In T168#50, @qgil wrote:
+> Do we really gain clarity by adding a parameter of ""Severity""? A ""Normal"" problem annoying many people will get a ""Medium"" / ""High"" priority and will be schedule in a foreseeable sprint. A ""Major"" or even ""Critical"" problem around a corner case of the likes of ""only in PostgreSQL"" will in practice fall under ""Needs Volunteer"" no matter what.
+> 
+> In other words, maybe what happens is that ""severity"" is not as objective and informative as it sounds, and what really counts is how relevant it is for those who actually can complete a task.
+
+After thinking about this some more, I'd say that ""severity"" is actually both objective and informative (it means essentially ""how much this breaks things""). On the contrary, I'd argue that what's not objective is Bugzilla's ""priority"" (i.e. timing-priority, or ""this needs to be done soon""). That should essentially be the final arbiter of what to do next, but it should be defined based on objective components, not as a subjective single-axis. Your comment goes to the core of this: the ""how many people are annoyed by this"" factor (i.e. ""impact"") is central to how we make decisions, yet it's nowhere represented in the systems we use.
+
+So perhaps instead of a single, subjective ""priority"" measure, we should keep bugzilla's two-axis system, but replacing ""priority"" with ""impact"", with impact having a stronger weight in the priority calculation. That would solve the problems you point out: a low-severity, high-impact problem will have higher priority than a high-severity, low-impact one, which is what we already observe today. And an issue with a ""blocker"" severity could then be untackled for years without diluting the meaning of severity, because we're explicitly acknowledging it's a low-impact one.",1410485356,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-07-10 17:39:30 (UTC)`
+
+Revisiting this discussion under the assumption that we would have these levels of Priority (see {T436}):
+
+> * Needs Triage
+> * Unbreak Now!
+> * High
+> * Medium
+> * Needs Volunteer
+
+Do we really gain clarity by adding a parameter of ""Severity""? A ""Normal"" problem annoying many people will get a ""Medium"" / ""High"" priority and will be schedule in a foreseeable sprint. A ""Major"" or even ""Critical"" problem around a corner case of the likes of ""only in PostgreSQL"" will in practice fall under ""Needs Volunteer"" no matter what.
+
+In other words, maybe what happens is that ""severity"" is not as objective and informative as it sounds, and what really counts is how relevant it is for those who actually can complete a task. I'd rather have a simple axis (Priority) driving what is scheduled in forthcoming sprints, and then community discussion and negotiation on whether e.g. a ""Needs Volunteer"" task will be taken by a team as ""Medium"", and from there to a sprint.
+
+Otherwise we end up in situations where ""critical"" and ""blocker"" bugs [[ https://bugzilla.wikimedia.org/buglist.cgi?bug_severity=blocker&bug_severity=critical&chfield=%5BBug%20creation%5D&chfieldto=2y&list_id=328275&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s%20Tools&product=Logwood&product=MediaWiki&product=MediaWiki%20extensions&product=MediaWiki%20skins&product=MediaWiki-Vagrant&product=MobileFrontend&product=mwEmbed&product=OOjs&product=OOjs%20UI&product=openZIM&product=Parsoid&product=Pywikibot&product=QRpedia&product=Spam&product=Tool%20Labs%20tools&product=Unofficial%20Apps&product=Utilities&product=VisualEditor&product=Wiki%20Loves%20Monuments&product=WikiLoves%20Monuments%20Mobile&product=Wikimedia&product=Wikimedia%20Labs&product=Wikimedia%20Mobile&product=Wikipedia%20App&product=Wiktionary%20tools&query_format=advanced&resolution=--- | sit around for years ]], diluting the meaning of those terms. ",1410485356,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**swalling** wrote on `2014-07-02 20:16:52 (UTC)`
+
+> Ok, then I rephrase my question: is there a document (or more) summarising what's the current expectation of their meaning for those who use them?
+
+Points are used in the same way they're understood in other Agile contexts. If you're looking for documentation, all you need do is Google around. 
+
+TL;DR summary: You assign points to a task to estimate the time and effort involved in a task. You can then track how many points you completed over a given sprint (i.e. a two week period), and adjust expectations about the team's capacity in the next sprint. In other words, it helps you more accurately guess how much you can reasonably get done. 
+
+",1410485356,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Nemo_bis** wrote on `2014-07-02 20:08:33 (UTC)`
+
+> I think we should feel free to innovate.
+
+For instance by removing this field: I agree with comment #44
+
+> the two teams that use them have repeatedly said they are a critical day-0 blocker for them.
+
+Ok, then I rephrase my question: is there a document (or more) summarising what's the current expectation of their meaning for those who use them?",1410485355,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-06-30 19:46:13 (UTC)`
+
+>>! In T168#46, @Waldir wrote:
+> Merging //target milestone// and //(timing) priority// sounds like a good idea in combination with the above, since it'd provide a concrete, straightforward way to define urgency.
+
+I completely and absolutely disagree. ""Milestone"" is something like ""Alpha release 244: 2014-06-30"" or ""1.23"", and is used for short-term planning (what are we working on this week?) and retrospective listing (what did we work on in week x?). It's not a long-term planning thing at all, and trying to merge the priority concept with a short-term planning framework is doomed to failure.
+",1410485355,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Waldir** wrote on `2014-06-25 19:49:40 (UTC)`
+
+My two cents: I've been thinking a lot recently about how to define task priorities (in general) in an objective way. I looked at [bugzilla's model](https://www.mediawiki.org/wiki/Bugzilla/Fields#Importance) for inspiration, and found the terms used (importance, priority and severity) to be somewhat vague. Thinking of ""priority"" as ""urgency"", and of ""severity"" as ""impact"", allowed me to grasp their meaning (and how they relate to each other) more intuitively.
+
+Granted, ""severity"" is good enough a term, but ""impact"" is more common and can stand for both positive and negative impact, while severity is mostly negative thing. ""Priority"" definitely feels more objective when defined as ""urgency"". ""Priority"" and ""importance"" (and ""points"") are terms that should be avoided, IMO, since their meaning is not universal.
+
+Essentially, I agree with what @aklapper said in T168#14, except that I'd use the terms **urgency**, **impact** and **effort**, to mean ""timing-priority"", ""importance-priority"" and ""difficulty-priority"". Merging //target milestone// and //(timing) priority// sounds like a good idea in combination with the above, since it'd provide a concrete, straightforward way to define urgency. Impact can be defined in terms of how many people are affected, and how often (e.g. readers/editors/admins, vs. on every page view/only on a specific subset of pages/only when using parameters x and y). Effort can be just a rough estimate of hours needed to code up the required change (anything too big to be estimated should become a tracking issue anyway).",1410485355,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-06-16 18:59:59 (UTC)`
+
+>>! In T168#44, @qgil wrote:
+>>>! In T168#43, @jdforrester wrote:
+>> ""Most"" people at WMF Engineering don't use points; I'd imagine that third party and volunteer developers have even less reason to  have particular expectations of their use in the MediaWiki world, so I think we should feel free to innovate.
+> 
+> Or we could just remove them until we find a good use for them. This is a custom field that someone added, not a Phabricator feature out of the box.
+
+""Most"" !== all; the two teams that use them have repeatedly said they are a critical day-0 blocker for them.",1410485354,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-06-16 18:39:23 (UTC)`
+
+>>! In T168#43, @jdforrester wrote:
+> ""Most"" people at WMF Engineering don't use points; I'd imagine that third party and volunteer developers have even less reason to  have particular expectations of their use in the MediaWiki world, so I think we should feel free to innovate.
+
+Or we could just remove them until we find a good use for them. This is a custom field that someone added, not a Phabricator feature out of the box.
+
+",1410485354,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-06-16 18:24:58 (UTC)`
+
+>>! In T168#42, @Nemo_bis wrote:
+>> data on severity into the ""points"" field in some fashion (Blocker -> 13, Critical -> 8, Major -> 5, … or whatever).
+> 
+> This doesn't fit my (very limited) understanding of what agile points are. Is there a good concise document summarising what's the current expectation of their meaning for most people in Wikimedia/MediaWiki?
+
+""Most"" people at WMF Engineering don't use points; I'd imagine that third party and volunteer developers have even less reason to  have particular expectations of their use in the MediaWiki world, so I think we should feel free to innovate.",1410485354,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Nemo_bis** wrote on `2014-06-15 09:29:26 (UTC)`
+
+> Priority and severity fields are just too fine-grained to be useful in seriously prioritizing tasks.
+
+I agree on this, but mostly because the recent addition of ""Highest"", ""Immediate"" and ""Lowest"" is disputable.
+
+> data on severity into the ""points"" field in some fashion (Blocker -> 13, Critical -> 8, Major -> 5, … or whatever).
+
+This doesn't fit my (very limited) understanding of what agile points are. Is there a good concise document summarising what's the current expectation of their meaning for most people in Wikimedia/MediaWiki?",1410485353,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-06-02 13:02:14 (UTC)`
+
+> I don't think a severity field per se is a useful addition,
+
++1.
+
+> and instead we should probably import the data on severity into the ""points"" field in some fashion (Blocker -> 13, Critical -> 8, Major -> 5, … or whatever).
+
+So in Phab we'd have priority, points, and columns to express 'things'.
+
+For general understanding and refering to the Severity field values in Bugzilla: Currently a bug report in Bugzilla about a crasher is critical by definition, but would be low priority if circumstances to reproduce required special rights in some rather uncommon volunteer-supported database backend (or such; to come up with one vague example). 
+Bugzilla's //critical// severity could also be expressed by a //crash// project or so; //enhancement// is already expressed via priority (instead of severity) in Phabricator. Bugzilla severities like //trivial// or //minor// don't make sense (a trivial typo could still trigger a critical crasher) and feel like sufficiently expressed by Bugzilla's //easy// keyword which would end up as another project in Phabricator.",1410485353,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-30 21:08:00 (UTC)`
+
+>>! In T168#36, @swalling wrote:
+> I'd //really really// like to try leaving the Phabricator defaults alone in terms of priority. When prioritizing Growth's last sprint in Phabricator, I found the list of current values to be very useful. Any tinkering we do is kind of bikeshedding here, IMO.
+
+I agree. I don't think a severity field //per se// is a useful addition, and instead we should probably import the data on severity into the ""points"" field in some fashion (Blocker -> 13, Critical -> 8, Major -> 5, … or whatever).
+
+
+> One of the great problems of Bugzilla is that there is just too much bullshit to deal with. Priority //and// severity fields are just too fine-grained to be useful in seriously prioritizing tasks. The same goes for Target Milestone etc... almost zero people seriously use these fields or rely on them now. 
+
+Remember that the milestones will be replaced by (sub)projects, which will be used to recording sprint activity. I'm assuming you //do// want to continue having sprints in Growth? Certainly, other teams are going to. :-)",1410485352,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-30 21:05:04 (UTC)`
+
+>>! In T168#34, @qgil wrote:
+> a casual call for opinions at wikitech-l might be interesting as well, especially if we plan to change the current Bugzilla status quo.
+
+I agree that we should definitely set out in detail what we plan to do in an e-mail to wikitech-l once we've got an idea. Maybe it's a bit premature now? Many people find it easier to find issues with a strawman/proposal than just to answer in a vacuum.
+",1410485352,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-05-30 19:33:55 (UTC)`
+
+I also think we can keep the default values and then use projects for whatever else (Easy, Security, Regressions, Sprint Candidates, etc). Custom fields bring unnecessary clutter for all tasks, most of them not needing such level of detail.",1410485352,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**swalling** wrote on `2014-05-30 19:19:29 (UTC)`
+
+I'd //really really// like to try leaving the Phabricator defaults alone in terms of priority. When prioritizing Growth's last sprint in Phabricator, I found the list of current values to be very useful. Any tinkering we do is kind of bikeshedding here, IMO. 
+
+One of the great problems of Bugzilla is that there is just too much bullshit to deal with. Priority //and// severity fields are just too fine-grained to be useful in seriously prioritizing tasks. The same goes for Target Milestone etc... almost zero people seriously use these fields or rely on them now. ",1410485351,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-05-30 00:29:56 (UTC)`
+
+>>! In T168#28, @TheDJ wrote:
+> Can we set the visibility of fields ? Then we can at least import it and initial hide it for everyone, then argue about how to follow up :)
+
+I'd argue before importing the data. What is stopping us from having this discussion?
+
+If we create the custom field, place there the severity data, and then hide it, such data will be ""lost"" from the users point of view. If we decide not to have it beforehand, or to have something else, the such data can appear in the task description as plain text.
+
+@aklapper and @jdforrester, I think you two should weigh in with an official position from the Phabmaster & PM team, if possible at all.
+
+Edited: a casual call for opinions at wikitech-l might be interesting as well, especially if we plan to change the current Bugzilla status quo.",1410485351,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**TheDJ** wrote on `2014-05-29 16:15:27 (UTC)`
+
+I'm trying this on my own instance, and i'm thus not sure if we are looking at the exact same thing, but the options is intended to be as flexible as https://fab.wmflabs.org/config/edit/differential.fields/ I presume, so I think the maniphest.fields option is currently awaiting to get the same treatment.
+
+https://secure.phabricator.com/T5011 indicates as much.",1410485351,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-29 15:33:57 (UTC)`
+
+>>! In T168#30, @aklapper wrote:
+>> Can we set the visibility of fields ?
+> 
+> Admins can add custom fields at http://fab.wmflabs.org/config/edit/maniphest.custom-field-definitions/
+> 
+> Docs in https://secure.phabricator.com/book/phabricator/article/custom_fields/ say ""The fields will then appear in the other config option for the application (for example, in maniphest.fields) and you can enable, disable, or reorder them."" so //disabling// should be possible. Haven't tried; if it does not fit our needs a hackish workaround would be using ""display: none"" CSS which I'd like to avoid.
+
+This seems a little limited unless I'm missing something – http://fab.wmflabs.org/config/edit/maniphest.fields/ lets you adjust what fields tasks have, but the only field shown (presumably, the only optional field?) is story points – I don't immediately see a way to remove other default fields. Also, it's not clear if removing the field disables it or just fails to show it, and of course it might behave differently for the built-in field for story points compared to a new field we added…
+
+BTW, editing what values the built-in fields have is trivial – see for example http://fab.wmflabs.org/config/edit/maniphest.statuses/ where (if you're an admin) you can edit the task status values available, or http://fab.wmflabs.org/config/edit/maniphest.priorities/ for the task priority values.",1410485350,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-05-28 17:00:37 (UTC)`
+
+> Can we set the visibility of fields ?
+
+Admins can add custom fields at http://fab.wmflabs.org/config/edit/maniphest.custom-field-definitions/
+
+Docs in https://secure.phabricator.com/book/phabricator/article/custom_fields/ say ""The fields will then appear in the other config option for the application (for example, in maniphest.fields) and you can enable, disable, or reorder them."" so //disabling// should be possible. Haven't tried; if it does not fit our needs a hackish workaround would be using ""display: none"" CSS which I'd like to avoid.",1410485350,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**TheDJ** wrote on `2014-05-23 18:15:22 (UTC)`
+
+Can we set the visibility of fields ? Then we can at least import it and initial hide it for everyone, then argue about how to follow up :)",1410485350,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-05-11 09:25:00 (UTC)`
+
+> It was, however, the sole proposal moved
+
+Because I wasn't paying enough attention.  :) 
+
+If we have a Severity field in Day 1, we will have it in Day 10.000. If there is a time to challenge our current classification of bug/task status, this time is now.
+
+Then again, while I do have a strong opinion about the need to revisit this topic and find an agreement now, I don't have any strong opinion about the decision itself. Whatever works for Andre will work for me.",1410485349,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-11 07:39:32 (UTC)`
+
+> To be precise, this was ""a proposal"" and not ""the proposal"".
+
+It was, however, **the** sole proposal moved, and reached unanimous approval (if not agreement), especially that this shouldn't be a block for Day 1 and could instead be changed later.
+",1410485349,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-05-10 23:26:56 (UTC)`
+
+To be precise, this was ""a proposal"" and not ""the proposal"". I the topic of priority/severity/importance deserves a good community discussion, in my opinion. We have a chance to improve the current system, if needed. After the migration will be too late. 
+
+If we discuss and reach to the conclusion that changing the current approach is not needed, fine. However, deciding after a few minutes of discussion in an afternoon doesn't look sensible to me. ",1410485349,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-10 15:06:41 (UTC)`
+
+The proposal in a meeting at the Zürich Hackathon was to mirror Bugzilla's existing `severity` field in Phabricator when we set it up, alongside the `priority` one.",1410485348,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-04-23 21:03:14 (UTC)`
+
+For what is worth, there is an interesting discussion about Important vs Urgent in the context of Phabricator at https://secure.phabricator.com/T4807",1410485348,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-04-22 07:05:18 (UTC)`
+
+.... so I don't consider ""No severity field"" a bug per se. Missing functionality to describe or categorize something would be a bug if it's considered important enough to categorize. :)",1410485348,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-04-22 07:03:29 (UTC)`
+
+I'd like to see a broader discussion first if anybody would like to have a ""Severity"" field (or maybe ""Impact"" which would be a better name). Priority, Severity and Target Milestone in Bugzilla often feel like unneeded complication.
+
+Two examples refering to potential shortcomes of Bugzilla's concept:
+JamesF once mentioned
+  - ​Timing-priority == ""this needs to be done soon""
+  - Importance-priority == ""this is affecting lots of people / lots of actions / has major impact""
+  - Difficulty-priority == ""this is really hard to do""​
+RobLa once thought of merging Target Milestone and Priority - both should describe when / how urgent an issue should get fixed, so (simplified) high priority would be TM = next release, normal priority = release after, low priority = not planned.",1410485347,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-04-22 00:59:21 (UTC)`
+
+Marked as resolved for the purpose of this RfC. If we want Severity field we can have it.",1410485347,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-04-19 16:14:25 (UTC)`
+
+If we need a field for severity, we can create it through Phabricator's configuration options.",1410485346,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"DECISION: We will use `phabricator.wikimedia.org` as the domain for the service.
+
+cnames for any shortened version
+
+----
+
+We need to decide a domain (and therefore a name) for the Phabricator instance in Wikimedia.
+
+Do we want to use something around the ""Phabricator"" brand or do we prefer to go for a descriptive alternative, or a totally invented name?
+
+We have used bugzilla.wikimedia.org and gerrit.wikimedia.org, therefore phabricator.wikimedia.org cannot be too wrong. Still, it is long, and I'm personally not convinced of relying so much on product names.",1397747363,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-iltgxch7wxmytcatl3vo,task_description,resolved
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,">>! In T82#808118, @Quiddity wrote:
+> searching for fl294 didn't work.
+
+It does. Go to Maniphest's advanced search and enter ""fl294"" in the Reference field. :)
+I admit it's not [[ https://www.mediawiki.org/wiki/Phabricator/Help#Searching_for_items | documented ]] though; Bugzilla felt like a more common usecase.
+
+> Where is the setting up task? Thanks :)
+
+It's T178",1417649605,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,">>! In T82#1216, @flimport wrote:
+> **aklapper** wrote on `2014-05-16 22:04:24 (UTC)`
+> 
+> This ticket is resolved when it comes to //deciding// what the URL should be. I wondered whether to keep this open for actually setting up that subdomain, but I guess that's sufficiently covered by T294.
+
+That ticket seems to be from the older phablabs test instance, and searching for fl294 didn't work. Where is the setting up task? Thanks :)",1417635269,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,//importing issue status//,1410485245,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**aklapper** wrote on `2014-06-13 15:51:17 (UTC)`
+
+Makes sense. Thanks for setting this up. 
+
+For the records, reference to current setup of Bugzilla cert and CNAMEs: https://rt.wikimedia.org/Ticket/Display.html?id=5011",1410485244,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**Rush** wrote on `2014-06-13 15:49:24 (UTC)`
+
+just a note, this idea comes into contact with the real world as I need to request SSL certificates that have to reflect these names.  If anyone wants a shortened version in addition to phab.wm.org now is the time to suggest :)",1410485244,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**Rush** wrote on `2014-06-13 15:48:07 (UTC)`
+
+I'm sorry I didn't see this ticket earlier.  So the external facing URL has a standard.  We typically use the full service url (graphite.wikimedia.org / bugzilla.wikimedia.org) and do not do shortened url's for the main A record.  That being said we do use cnames for shorter versions.  We have bugs.wikimedia.org for bugzilla for example.  
+
+Since this is the operations standard I am going to change the title url to be: phabricator.wikimedia.org
+
+...with the intention of mimicking the bugs.wm.org behavior for phab.wm.org
+
+should satisfy both and still maintain the standard?",1410485244,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**aklapper** wrote on `2014-05-16 22:04:24 (UTC)`
+
+This ticket is resolved when it comes to //deciding// what the URL should be. I wondered whether to keep this open for actually setting up that subdomain, but I guess that's sufficiently covered by T294.",1410485243,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**jdforrester** wrote on `2014-05-10 14:59:48 (UTC)`
+
+`phab.wikimedia.org` appears to be the clear winner; let's proceed on this basis.",1410485243,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**aklapper** wrote on `2014-05-03 22:40:40 (UTC)`
+
+""collabtools"" doesn't convince me either and the generic tech term ""forge"" isn't common enough yet, so I guess we could stick to phab.wikimedia.org (because we can).",1410485243,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**qgil** wrote on `2014-04-17 19:56:15 (UTC)`
+
+Alright, so maybe after all we are talking about 
+
+fab.wikimedia.org
+
+or
+
+phab.wikimedia.org",1410485242,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**jdforrester** wrote on `2014-04-17 19:25:10 (UTC)`
+
+This is and always will be a secondary location for task management for Wikimedia compared to the wikis – fundamentally, work by volunteers happens primarily on-wiki, and calling this something not specific to code and technical makes it look like we're normalising off-wiki work – an exception that is rare.
+
+Calling this `tasks` would strongly suggest that this is where the vast majority of tasks by volume (editing pages, patrolling edits, uploading images, discussing improvements, blocking users,…) happens, and I think that this would be a mistake.
+
+`ph` would intrude into the reserved https://en.wikipedia.org/wiki/ISO_3166-2 and https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 spaces for chapters.",1410485242,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**qgil** wrote on `2014-04-17 18:46:47 (UTC)`
+
+Agreed on the .wikimedia.org part.
+
+One ""problem"" with code. and other tech. references is that non-coding non-tech projects might be interested as well. This is not just an hypothesis; @MissGayle and @philippe have been playing around already, and I don't see why we couldn't recommend this environment just to any project needing to organize tasks that may or may not have a connection with code.
+
+Being also very pragmatical: if more WMF teams, chapters, etc would find this tool interesting it would be easier to find resources to maintain it properly.
+
+Anyway, more ideas:
+
+tasks.wikimedia.org (like projects, without the double meaning)
+
+ph.wikimedia.org  (just because we can)",1410485242,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**jdforrester** wrote on `2014-04-17 15:50:09 (UTC)`
+
+[Commence bike-shedding]
+
+I think ""`projects.wikimedia.org`"" is confusing with regard to which projects (Wikipedia and Wiktionary are projects of the Wikimedia movement; Military History is a [wiki]project of the English Wikipedia; //etc.//).
+
+I approve of hosting off `.wikimedia.org` rather than `.mediawiki.org` because we do rather more than just MediaWiki development nowadays (most notably operations work, but also //e.g.// VisualEditor), and we should be consistent with `git.wikimedia.org`, `bugzilla.wikimedia.org`, `rt.wikimedia.org` and so on.
+
+Personally I like `code.wikimedia.org` as it's simple and direct, and doesn't interfere with potential chapter domain names, but could be argued around.",1410485241,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**qgil** wrote on `2014-04-17 15:09:38 (UTC)`
+
+  projects.wikimedia.org
+
+?",1410485241,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Document benefits for Bugzilla users,"**Document moved to https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/versus_Bugzilla -- you are welcome to edit and discuss there.**
+
+As a bugzilla volunteer user, I want to know what I'm supposed to gain from the migration to phabricator, which is bound to add work I've not asked for.",1397721605,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-pf7labc5tuafvfstlptu,task_description,resolved
+Document benefits for Bugzilla users,//importing issue status//,1410485129,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**qgil** wrote on `2014-04-27 03:53:40 (UTC)`
+
+Actually, I wanted to see what happens when you copy text in Phabricator and paste it in MediaWiki using VisualEditor...  :)
+
+https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/versus_Bugzilla
+
+Resolving the task here, if you want to improve the document let's do it there.",1410485129,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**qgil** wrote on `2014-04-27 03:10:15 (UTC)`
+
+I have been solving the task in its own description. Please have a look and edit at will. On Monday I will public the content in mediawiki.org... where?",1410485128,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**Nemo_bis** wrote on `2014-04-19 18:59:59 (UTC)`
+
+> Nemo, could you take the lead in this task, please?
+
+I still found none. I'm editing the task description for now, space is plenty for what I found.",1410485128,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**qgil** wrote on `2014-04-19 16:17:50 (UTC)`
+
+I agree that having such document would be useful, but it would be even more useful in a wiki page closer to the RfC. Nemo, could you take the lead in this task, please? I will help editing.",1410485128,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**Nemo_bis** wrote on `2014-04-17 08:36:11 (UTC)`
+
+Ideas can be found in https://bugzilla.wikimedia.org/buglist.cgi?bug_severity=enhancement&component=Bugzilla&list_id=305582&product=Wikimedia&query_format=advanced&resolution=--- : list the enhancement requests that phabricator would satisfy",1410485127,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Currently, {{int:}} is (ab)used to localize content, either directly by showing a localised message or by using e.g. [[ https://commons.wikimedia.org/w/index.php?title=Special%3ASearch&search=MediaWiki%3ALang&fulltext=1 | MediaWiki:Lang ]] to achieve conditional transclusion à-la {{sometemplate/{{int:lang}}}}. However, Parsoid always assumes content language for this parser function. This is generally not a problem for VisualEditor where it even makes sense to display a ""canonical"" version of text, but page views on multilingual projects like meta and commons are different because these sites rely heavily on user language to display content in it. A few examples:
+
+
+  - File description pages, compare https://commons.wikimedia.org/wiki/File:Sao_Paulo_Railway.jpg?uselang=en vs. https://commons.wikimedia.org/wiki/File:Sao_Paulo_Railway.jpg?uselang=fr
+  - Talk page templates, compare https://commons.wikimedia.org/wiki/Commons:Bistro?uselang=fr vs. https://commons.wikimedia.org/wiki/Commons:Bistro?uselang=en
+  - Esoteric templates, e.g. https://commons.wikimedia.org/w/index.php?title=Template:Localized_link&action=edit or even in Lua: https://commons.wikimedia.org/wiki/Module:Fallback
+
+We need to develop a strategy to mitigate thiese problems for Parsoid-based pageviews.",1419990114,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-uoqsiopafkhtpu2r5hem,task_description,open
+Parsoid page views: need to do something about {{int:}},"Handling your second question first, and picking one of the results from `grep -F '{{int:' languages/i18n/en.json` at random:
+```
+""resetpass-expired-soft"": ""Your password has expired and needs to be changed. Please choose a new password now, or click \""{{int:authprovider-resetpass-skip-label}}\"" to change it later."",
+```
+There isn't recursive expansion here.  The Parsoid output for the wikitext:
+```
+{{int:resetpass-expired-soft}}
+```
+is/will be (roughly, there are some slight tweaks coming in how the first argument of parser functions such as `int` are represented [gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/820243)):
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}' />
+ </span>
+</p>
+```
+That is, a span wrapper representing the parser function invocation, containing an empty span representing ""a localized message"" which is not expanded.
+
+This is the user-independent output which is stored in the parser cache.
+
+Later, when the content is taken out of the parser cache and postprocessed with a specific user/user language, we get:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""Skip\"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+That is, we expand the UX message completely before substituting it for the span.  This is similar to what we do for templates, which are similarly flattened when expanded in Parsoid output.
+
+This is partly an artifact of how Parsoid interacts with the legacy parser, which is still used for message parsing and template expansion.  In the future (when using Parsoid natively for message parsing) we might not flatten the output before embedding, but there's no real issue introduced by that:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""
+      <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""authprovider-resetpass-skip-label"",""params"":[]}}'>
+         Skip
+       </span>
+      \"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+
+The issue of ""wikitext occurring inside parameters"" is also similar to how that issue is handled in templates.  In general we treat parameters as raw strings, and don't represent the ""parsed"" form of the parameter in the HTML.  Visual Editor may know that some parameters are ""really"" wikitext, and can provide a rich editing widget for them; the `{{int}}` parser function will be given type hints in a similar way (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TemplateData/+/819740).
+
+For the other question, I'm not entirely sure what you mean by ""translatable template"".  Could you elaborate?",1663948453,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Handling your second question first, and picking one of the results from `grep -F '{{int:' languages/i18n/en.json` at random:
+```
+""resetpass-expired-soft"": ""Your password has expired and needs to be changed. Please choose a new password now, or click \""{{int:authprovider-resetpass-skip-label}}\"" to change it later."",
+```
+There isn't recursive expansion here.  The Parsoid output for the wikitext:
+```
+{{int:resetpass-expired-soft}}
+```
+is/will be (roughly, there are some slight tweaks coming in how the first argument of parser functions such as `int` are represented [gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/820243)):
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}' />
+ </span>
+</p>
+```
+That is, a span wrapper representing the parser function invocation, containing an empty span representing ""a localized message"" which is not expanded.
+
+This is the user-independent output which is stored in the parser cache.
+
+Later, when the content is taken out of the parser cache and postprocessed with a specific user/user language, we get:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""Skip\"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+That is, we expand the UX message completely before substituting it for the span.  This is similar to what we do for templates, which are similarly flattened when expanded in Parsoid output.
+
+This is partly an artifact of how Parsoid interacts with the legacy parser, which is still used for message parsing and template expansion.  In the future (when using Parsoid natively for message parsing) we might not flatten the output before embedding, but there's no real issue introduced by that:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""
+      <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""authprovider-resetpass-skip-label"",""params"":[]}}'>
+         Skip
+       </span>
+      \"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+
+The issue of ""wikitext occurring inside parameters"" is also similar to how that issue is handled in templates.  In general we treat parameters as raw strings, and don't represent the ""parsed"" form of the parameter in the HTML.  Visual Editor may know that some parameters are ""really"" wikitext, and can provide a rich editing widget for them; the {{int}} parser function will be given type hints in a similar way (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TemplateData/+/819740).
+
+For the other question, I'm not entirely sure what you mean by ""translatable template"".  Could you elaborate?",1663948402,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Handling your second question first, and picking one of the results from `grep -F '{{int:' languages/i18n/en.json` at random:
+```
+""resetpass-expired-soft"": ""Your password has expired and needs to be changed. Please choose a new password now, or click \""{{int:authprovider-resetpass-skip-label}}\"" to change it later."",
+```
+There isn't recursive expansion here.  The Parsoid output for the wikitext:
+```
+{{int:resetpass-expired-soft}}
+```
+is/will be (roughly, there are some slight tweaks coming in how the first argument of parser functions such as `int` are represented [gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/820243)):
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}' />
+ </span>
+</p>
+```
+That is, a span wrapper representing the parser function invocation, containing an empty span representing ""a localized message"" which is not expanded.
+
+This is the user-independent output which is stored in the parser cache.
+
+Later, when the content is taken out of the parser cache and postprocessed with a specific user/user language, we get:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""Skip\"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+That is, we expand the UX message completely before substituting it for the span.  This is similar to what we do for templates, which are similarly flattened when expanded in Parsoid output.
+
+This is partly an artifact of how Parsoid interacts with the legacy parser, which is still used for message parsing and template expansion.  In the future we might not flatten the output before embedding, but there's no real issue introduced:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""
+      <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""authprovider-resetpass-skip-label"",""params"":[]}}'>
+         Skip
+       </span>
+      \"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+
+The issue of ""wikitext occurring inside parameters"" is also similar to how that issue is handled in templates.  In general we treat parameters as raw strings, and don't represent the ""parsed"" form of the parameter in the HTML.  Visual Editor may know that some parameters are ""really"" wikitext, and can provide a rich editing widget for them; the {{int}} parser function will be given type hints in a similar way (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TemplateData/+/819740).
+
+For the other question, I'm not entirely sure what you mean by ""translatable template"".  Could you elaborate?",1663948191,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Handling your section question first, and picking one of the results from `grep -F '{{int:' languages/i18n/en.json` at random:
+```
+""resetpass-expired-soft"": ""Your password has expired and needs to be changed. Please choose a new password now, or click \""{{int:authprovider-resetpass-skip-label}}\"" to change it later."",
+```
+There isn't recursive expansion here.  The Parsoid output for the wikitext:
+```
+{{int:resetpass-expired-soft}}
+```
+is/will be (roughly, there are some slight tweaks coming in how the first argument of parser functions such as `int` are represented [gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/820243)):
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}' />
+ </span>
+</p>
+```
+That is, a span wrapper representing the parser function invocation, containing an empty span representing ""a localized message"" which is not expanded.
+
+This is the user-independent output which is stored in the parser cache.
+
+Later, when the content is taken out of the parser cache and postprocessed with a specific user/user language, we get:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""Skip\"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+That is, we expand the UX message completely before substituting it for the span.  This is similar to what we do for templates, which are similarly flattened when expanded in Parsoid output.
+
+This is partly an artifact of how Parsoid interacts with the legacy parser, which is still used for message parsing and template expansion.  In the future we might not flatten the output before embedding, but there's no real issue introduced:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""
+      <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""authprovider-resetpass-skip-label"",""params"":[]}}'>
+         Skip
+       </span>
+      \"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+
+The issue of ""wikitext occurring inside parameters"" is also similar to how that issue is handled in templates.  In general we treat parameters as raw strings, and don't represent the ""parsed"" form of the parameter in the HTML.  Visual Editor may know that some parameters are ""really"" wikitext, and can provide a rich editing widget for them; the {{int}} parser function will be given type hints in a similar way (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TemplateData/+/819740).
+
+For the other question, I'm not entirely sure what you mean by ""translatable template"".  Could you elaborate?",1663868311,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},">>! In T85581#8245592, @cscott wrote:
+> @Tacsipacsi see https://www.mediawiki.org/wiki/Specs/HTML/2.6.0#Internationalization
+
+Thanks for the link! However, there are two issues with this spec for the translatable template use case:
+* It specifies how to set the MediaWiki message to be used for translation. However, a translatable template is not a MediaWiki message, for a reason: MediaWiki messages don’t work the wiki way – only admins and other privileged groups can edit them. This is a necessary precaution in case of interface elements, as they’re highly visible, and local editing to them is usually unnecessary anyway thanks to Translatewiki. Translatable templates, in contrast, are much less visible, so the risk is lower, but they can’t be edited on Translatewiki, so the need is higher.
+* It //doesn’t// specify the level of wikitext markup support within the messages to be used, or how to handle recursive i18n. The second example shows that simple HTML tags (`<code>` in this case) should be okay in placeholder elements, but what about more complicated constructs, like parser functions/tags, magic words or templates? Translatable templates usually build on other, often quite complicated, templates/modules. What if a translatable message itself contains something translatable? (`grep -F '{{int:' languages/i18n/en.json | wc -l` gives 32, and this is just MediaWiki core. This pattern is used every now and then in extensions as well; and it’s used all the time in translatable templates. In templates, often the inner template is translated into the user language, but the outer one falls back to English. While this may lead to mixed-language output, it makes sure that as much content is available in the user’s language as possible, so IMO it should be kept this way.) What if this translatable message containing a reference to another translatable message happens to be in an attribute? `<span>`s should not normally occur in attributes, but this use case should be supported. What if a //parameter// is, or contains, another translatable message? This is probably even more common when working with MediaWiki messages (i.e. not in the template world) than messages directly containing references to other messages.",1663691053,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"@ihurbain this is probably related to the Internationalization work done for {T309024}.
+
+@Tacsipacsi see https://www.mediawiki.org/wiki/Specs/HTML/2.6.0#Internationalization",1663600740,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},@ihurbain this is probably related to the Internationalization work done for {T309024}.,1663600657,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},">>! In T85581#951449, @GWicke wrote:
+> Some of the use cases for {{int:}} like commons metadata will probably go away soonish with the move to wikidata. The remaining ones seem to be typically individual transclusions, often really small ones (like the 'thanks' template). 
+It doesn’t mean the problem would also go away. Compare https://commons.wikimedia.org/w/index.php?title=Symphyotrichum_novi-belgii&uselang=la and https://commons.wikimedia.org/w/index.php?title=Symphyotrichum_novi-belgii&uselang=la&veaction=edit – “Basionymum” vs “Basionym”. The text is read from [[https://www.wikidata.org/wiki/Q810198|d:Q810198]], yet it changes from German to English when I open the page in VisualEditor (i.e. switch from legacy parser output to Parsoid output).
+
+>>! In T85581#7567938, @cscott wrote:
+> I think the story for Parsoid will be some general purpose markup for 'translatable content' in the main parsoid edit views path, and then a postprocessing step to do the per-user localization.
+Would that mean that the cache would contain all translations in some encoded form? It’d blow up. `{{Assessments}}` (used on the above file description page), for example, is translated into 69 languages. The description page of this particular file is probably never viewed in the majority of those languages, so currently those languages are not cached. However, if you want them to be present in an intermediate representation, they //will// be cached.",1648826327,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"I think the story for Parsoid will be some general purpose markup for 'translatable content' in the main parsoid edit views path, and then a postprocessing step to do the per-user localization.  This is still missing functionality, but {T267059} and T266666 have laid some of the groundwork.",1639434736,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},">>! In T85581#951449, @GWicke wrote:
+> I think it's worth thinking about moving more of the remaining work to the client. We could compile a list of such elements in each page after parse, and then deliver translations to be applied client-side to users who requested it. This should be a good performance win if translations are small relative to the overall page size. It would reduce the per-language storage needs on the server to fragments rather than entire pages. It might even be possible to share such fragments between pages if we can establish that the output does not depend on the actual page name.
+
+However, this will not work when {{int}} is used in esoteric templates to control transclusion.",1423001175,PHID-USER-aasrweh54ew7py3agvg2,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"@ssastry We could pass a language in as a parameter (and then forward that to expandtemplates), but would also need to store that separately, effectively replicating the current parser cache fragmentation.
+
+Some of the use cases for {{int:}} like commons metadata will probably go away soonish with the move to wikidata. The remaining ones seem to be typically individual transclusions, often really small ones (like the 'thanks' template). 
+
+I think it's worth thinking about moving more of the remaining work to the client. We could compile a list of such elements in each page after parse, and then deliver translations to be applied client-side to users who requested it. This should be a good performance win if translations are small relative to the overall page size. It would reduce the per-language storage needs on the server to fragments rather than entire pages. It might even be possible to share such fragments between pages if we can establish that the output does not depend on the actual page name.
+
+In any case, I think the current result of returning the content language is tolerable in the short term. There are bigger issues to tackle right now.",1420065446,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"@ssastry We could pass a language in as a parameter, but would also need to store that separately, effectively replicating the current parser cache fragmentation.
+
+Some of the use cases for {{int:}} like commons metadata will probably go away soonish with the move to wikidata. The remaining ones seem to be typically individual transclusions, often really small ones (like the 'thanks' template). 
+
+I think it's worth thinking about moving more of the remaining work to the client. We could compile a list of such elements in each page after parse, and then deliver translations to be applied client-side to users who requested it. This should be a good performance win if translations are small relative to the overall page size. It would reduce the per-language storage needs on the server to fragments rather than entire pages. It might even be possible to share such fragments between pages if we can establish that the output does not depend on the actual page name.
+
+In any case, I think the current result of returning the content language is tolerable in the short term. There are bigger issues to tackle right now.",1420065398,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Hmm .. interesting ... this could be tricky. How do we get user state into the parsing because without user state, it will return the default lang.
+
+```
+[subbu@earth lib] echo ""{{int:lang}}"" | node parse --normalize --dump tplsrc --prefix commonswiki
+=================================
+pf_int
+---------------------------------
+en
+---------------------------------
+
+<p>en</p>
+```",1420064873,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"Pasting from Excel into Chrome works.  Highlighting that content in Chrome and then pasting it into IE works.
+
+Pasting the content straight from Excel into IE11 doesn't work.
+
+How can I enable pasting straight from Excel?",1419973446,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-fddzs2tnied2swcs624k,task_description,invalid
+Pasting Excel cells into Internet Explorer doesn't work,IE11 is no longer supported.,1681402595,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,Reported: T228010,1563177232,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"Broken with Firefox, too.
+
+If I paste from Excel while editing a page in VE in Firefox, it's not pasted as a table at all, but just as text. If I paste into Chrome, it's pasted as table cells.
+
+If I paste from Google Spreadsheets into Firefox, it also works.
+
+Should it be a separate task?",1563176443,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,Not getting any crazy font tags with Excel2016 + Edge12.,1457452953,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,Appears to work with Excel2016 + Edge12.,1457452916,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"No, I was right.  I just removed all <font> tags and their children.",1420075603,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"hrm.... maybe I was wrong.  looks like it is already stripped by this point.
+",1420069459,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"Tracked down to a call in ve.js: ve.createDocumentFromHtml.
+
+Using my trusty console.log() -- who needs a debugger!?! -- I saw that before this call the text I want is there, but after it isn't:
+
+			// If there were no problems, let CE do its sanitizing as it may
+			// contain all sorts of horrible metadata (head tags etc.)
+			// TODO: IE will always take this path, and so may have bugs with span unwapping
+			// in edge cases (e.g. pasting a single MWReference)
+			htmlDoc = ve.createDocumentFromHtml( this.$pasteTarget.html() );
+",1420068558,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"From IRC:
+
+  <edsanders> hexmode, paste sanitization happens in
+            ve.ce.Surface.prototype.beforePaste
+  <edsanders> ve.ce.Surface.prototype.afterPaste
+  <edsanders> and ve.dm.ElementLinearData.prototype.sanitize
+  <edsanders> we have sanitization rules
+  <edsanders> which are strict for MediaWiki and loose for VisualEditor core
+",1420067366,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"I'll have to take a look at how the converter is handling it at the moment to see how to fix it, but I'm on holiday at the moment.",1419983538,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"So, how do I strip it?  Where would I put that in the VE code?",1419979075,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,Wow that IE html is bad. Font tags as a child of table!,1419979014,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"Sorry for being an idiot -- I was pasting into the wrong box.
+
+On Chrome, I get:
+
+  <table border=""0"" cellpadding=""0"" cellspacing=""0"" width=""270"" style=""border-collapse:
+   collapse;width:203pt""><tbody><tr height=""80"" style=""height:60.0pt"">
+    <td height=""80"" align=""right"" width=""58"" style=""height:60.0pt;width:44pt"">226</td>
+    <td width=""212"" style=""width:159pt"">LexWiki</td></tr></tbody></table>
+
+
+In IE, I get:
+  <table width=""270"" style=""width: 203pt; border-collapse: collapse;"" border=""0"" cellspacing=""0"" cellpadding=""0""><font face=""Times New Roman"">
+   </font><colgroup><col width=""58"" style=""width: 44pt; mso-width-source: userset; mso-width-alt: 2121;""><font face=""Times New Roman"">
+   </font><col width=""212"" style=""width: 159pt; mso-width-source: userset; mso-width-alt: 7753;""><font face=""Times New Roman"">
+   </font><tbody><tr height=""80"" style=""height: 60pt;""><font face=""Times New Roman"">
+  
+    </font><td width=""58"" height=""80"" align=""right"" style=""border: 0px black; width: 44pt; height: 60pt; background-color: transparent;""><font face=""Calibri"">226</font></td><font face=""Times New Roman"">
+    </font><td width=""212"" style=""border: 0px black; width: 159pt; background-color: transparent;""><font face=""Calibri"">LexWiki</font></td><font face=""Times New Roman"">
+  
+   </font></tr><font face=""Times New Roman"">
+  </font></tbody></table>
+
+In FF, I get:
+
+  <table border=""0"" cellpadding=""0"" cellspacing=""0"" width=""270""><colgroup><col width=""58""><col width=""212""></colgroup><tbody><tr height=""80"">
+    <td style=""height:60.0pt;width:44pt"" align=""right"" height=""80"" width=""58"">226</td>
+    <td style=""width:159pt"" width=""212"">LexWiki</td>
+  </tr></tbody></table>
+",1419978835,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"It doesn't seem to matter which browser I use.  Chrome, FF, and IE all give: ""226 LexWiki ""
+
+Pasting the same thing into a VE page on chrome gives a table with two cells.",1419974167,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,What HTML do you get if you past into a CE box? http://edg2s.github.io/content-editable-sandbox/,1419973695,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"This is similar to T53472.
+
+Some languages or writing systems require combining diacritics.
+In theory most characters with diacritics can be input with combining diacritics, for example é (e + combining acute) is equivalent to é (eacute). **For some combinations in some languages only the use of combining diacritics is possible, for exemple ɔ́ (open o + combining acute).**
+
+When typing or pasting text with combining diacritics the following occurs:
+  - the first character after a combining diacritics is duplicated on a new line below the cursor.
+  - pressing backspace pushes the characters after the first combining diacritics to that line below, the cursor jumps to the end of the newline and the first character that was duplicated jumps behind the cursor as well.
+  - pressing backspace gets stuck a the combining diacritics, erasing the duplicated character last, after the characters that jumped and the line return but not erasing the combining diacritics and its base character.
+
+For example, typing
+
+```
+té
+```
+is fine.
+But typing other characters becomes:
+
+```
+tél
+l
+```
+then
+
+```
+télévision
+l
+```
+
+Pressing backspace with the cursor at the end of the first line:
+
+```
+té
+élvisio
+```
+with the cursor before the o, but the next backspace will delete the o and the cursor jumps before the i.
+
+The expected result should be the word ""télévision"" and pressing backspace should delete the character before the cursor or the character cluster before the cursor.",1419151474,PHID-USER-i5at67w766dqxs6ncxam,PHID-TASK-juwxek3lh7qnt55hfhfo,task_description,resolved
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 456507 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (8097e44c1)
+
+[[https://gerrit.wikimedia.org/r/456507]]",1535669341,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 456509 abandoned by Jforrester:
+Update VE core submodule to master (8097e44c1)
+
+Reason:
+Bartosz pushed Ieec61133d.
+
+[[https://gerrit.wikimedia.org/r/456509]]",1535667696,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 456509 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (8097e44c1)
+
+[[https://gerrit.wikimedia.org/r/456509]]",1535667557,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 456507 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (8097e44c1)
+
+[[https://gerrit.wikimedia.org/r/456507]]",1535667455,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 451669 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] ve.dm.Document: Remove incorrect handling for combining characters in #fixupInsertion
+
+[[https://gerrit.wikimedia.org/r/451669]]",1535665072,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"If you want to test this and can't easily insert combining characters from the keyboard, here is a U+0301 Combining Acute Accent for your copy-paste convenience:
+
+`́`
+
+Tasks T182404 and T198719 may be duplicates of this bug (this needs to be tested).",1533836066,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 451669 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[VisualEditor/VisualEditor@master] [WIP] ve.dm.Document: Remove incorrect handling for combining characters in #fixupInsertion
+
+[[https://gerrit.wikimedia.org/r/451669]]",1533835960,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,Also impacts Flow.,1477073412,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"I could see the issue for diacritics characters that are entered with Shift key(both in production and betalabs):
+
+For example, using 'US extended' keyboard, 
+1) type t, after t type e
+2) then use Option+Shift+e to apply an accent mark to e,
+3)  type l (letter 'el')
+
+tél
+l
+
+Then the letter l will be duplicated and placed on the next line. There will be some issues with deleting as described.
+
+Note: Entering so called precomposed diactrics characters does not seem to present an issue. Additional info at:
+http://superuser.com/questions/339359/insert-a-character-with-multiple-accents-on-an-extended-mac-keyboard-layout
+
+
+ ",1419292625,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Text in Templates is not found by VisualEditor's Find / Search,"Found when investigating T62451 - a page consists entirely of text entered via Templates fields: https://pt.wikibooks.org/w/index.php?title=C%C3%A1lculo_(Volume_1)/An%C3%A1lise_de_fun%C3%A7%C3%B5es_elementares_(2)&redirect=no&veaction=edit 
+
+Text is not searchable via VE Find, but can be searched via browser Find.",1418936627,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-hvyzq7c5neh3uqybtctf,task_description,duplicate
+convert the RTL blocking bug T2745 into a tag,"The RTL blocking/tracking bug T2745 can be converted into a Phabricator tag.
+
+It also has some ""sub-tracker"" bugs, for example T35126, which is for RTL bugs in VisualEditor. These can eliminated as well. They should have the RTL tag and the appropriate project tag.",1418744270,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_description,resolved
+convert the RTL blocking bug T2745 into a tag,"Requested project #RTL has been created: https://phabricator.wikimedia.org/project/profile/1280/
+
+T2745 has been updated accordingly and closed as declined.
+
+Please encourage interested people to visit the project and to join the project as {icon users} members, and to [[ https://www.mediawiki.org/wiki/Phabricator/Help#Receiving_updates_and_notifications | subscribe themselves to the project ]] in order to receive updates!
+
+[[ https://www.mediawiki.org/wiki/Phabricator/Project_management | Recommended practices for project and workboard management in Phabricator ]] are available.
+
+And if for some reason you ever want to rename the project, please check [[ https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Renaming_projects | the guidelines ]] first.
+
+I also created H32 for automatically adding #i18n to #RTL tasks.
+
+Enjoy!",1433255137,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,">>! In T78670#1325274, @Aklapper wrote:
+> My remaining question still stands:
+>> We can make Herald automatically add the #i18n tag whenever a future #RTL tag is added to a task. Does that sound reasonable?
+> 
+> Someone please answer.
+
+Yes.",1433162289,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,"My remaining question still stands:
+> We can make Herald automatically add the #i18n tag whenever a future #RTL tag is added to a task. Does that sound reasonable?
+
+Someone please answer.",1433156310,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,"We can make Herald set the #i18n tag whenever a future #RTL tag is added to a task. Does that sound reasonable?
+
+BiDi could be an additional hashtag.
+
+For converting tracking tasks to projects there is now [[ https://www.mediawiki.org/wiki/Phabricator/Project_management/Tracking_tasks | documentation ]] available.",1425053100,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,">>! In T78670#936776, @Aklapper wrote:
+> Any naming proposal? ""RTL-bidirectional"" or such? Tag project description text could link to https://www.mediawiki.org/wiki/Directionality_support ?
+
+Just ""RTL"" or ""bidi"" should be enough, if it's possible to make something very short.
+
+Linking to https://www.mediawiki.org/wiki/Directionality_support is OK.
+
+> And I've always wondered (already in Bugzilla) how this collides or not with the existing i18n tag - is RTL always a subset of i18n?
+
+Indeed, all RTL bugs are i18n bugs, but i18n includes many more topics. If there is a way to organize a hierarchy of bugs that will automatically infer that all RTL bugs are i18n bugs, it would be a nice thing to have.
+
+RTL could be a Bugzilla tag like i18n is from the start, but somehow RTL issues ended up being tracked by a blocking bug. Now would be a good time to clean that up :)",1419071629,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,">>! In T78670#936776, @Aklapper wrote:
+> I like the idea but converting looks rather cumbersome, see my general comment in T75703#936775.
+
+https://phabricator.wikimedia.org/maniphest/query/bKU3kGuAWKFB/#R  :)",1419022517,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,">>! In T78670#936776, @Aklapper wrote:
+> I like the idea but converting looks rather cumbersome, see my general comment in T75703#936775.
+
+https://phabricator.wikimedia.org/maniphest/query/stlzyr5F2Ks3/#R  :)",1419021897,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,"I like the idea but converting looks rather cumbersome, see my general comment in T75703#936775.
+
+Any naming proposal? ""RTL-bidirectional"" or such? Tag project description text could link to https://www.mediawiki.org/wiki/Directionality_support ?
+
+And I've always wondered (already in Bugzilla) how this collides or not with the existing i18n tag - is RTL always a subset of i18n?",1419018095,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"The screenshots that are uploaded by the latest builds of the VisualEditor language screenshot job have pixelated fonts.
+
+Compare:
+* Current, pixelated: https://upload.wikimedia.org/wikipedia/commons/f/fe/VisualEditor_Toolbar_Headings-en.png
+* Older, non-pixelated: https://upload.wikimedia.org/wikipedia/commons/archive/f/fe/20141203163056!VisualEditor_Toolbar_Headings-en.png
+
+This may be happening because on the clients where the test jobs run there is a problem with the screen driver or maybe fonts anti-aliasing is disabled. Either the configuration of this client machines must be fixed, or the tests must run on a different platform, maybe Mac. (But it must be tested that they have fonts for all the languages, in particular Arabic, Japanese and Hebrew.)",1418732838,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_description,resolved
+VisualEditor language screenshots come out with pixelated fonts,"Change 184587 merged by jenkins-bot:
+Deleted Jenkins job that was running VisualEditor screenshots using a local browser
+
+[[https://gerrit.wikimedia.org/r/184587]]",1421143290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"Change 184587 had a related patch set uploaded (by Zfilipin):
+Deleted Jenkins job that was running VisualEditor screenshots using a local browser
+
+[[https://gerrit.wikimedia.org/r/184587]]
+
+#patch-for-review",1421142699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"Change 183480 merged by jenkins-bot:
+Run VisualEditor screenshot job on a Mac
+
+[[https://gerrit.wikimedia.org/r/183480]]",1421142263,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"This patch fixes the pixelation. Thank you. When it's merged and the new non-pixelated screenshots are uploaded to Commons, this bug can be marked as resolved.",1420724515,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"Change 183480 had a related patch set uploaded (by Zfilipin):
+Run VisualEditor screenshot job on a Mac
+
+[[https://gerrit.wikimedia.org/r/183480]]
+
+#patch-for-review",1420717978,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor screenshots-taking tests should link to the job that uploaded them from the file description page,VisualEditor screenshots-taking tests (currently language_screenshots.feature) upload the files to Commons. It would be useful to have a link from the file description page to the Jenkins job that uploaded the file so it would be easier to debug the problems in it if there are any.,1418732537,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-msm6dhxj4earcc46fnei,task_description,open
+make-wmf-branch doesn't play nice with existing extension branches,"```
+'git' 'clone' '-q' 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git' 'VisualEditor'
+Total 73708 (delta 49816), reused 73204 (delta 49799)
+cd VisualEditor
+'git' 'checkout' '-q' '-b' 'wmf/1.25wmf12'
+'git' 'commit' '-a' '-q' '-m' 'Creating new wmf/1.25wmf12 branch'
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+git exit with status 1
+```",1418240952,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-5uacgwuqg3wsvpphjet4,task_description,declined
+make-wmf-branch doesn't play nice with existing extension branches,"`branch.py`, the successor to `make-wmf-branches` and `make-extension-branches` handles this. Declining as the titular script is EOL.",1526375741,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-5uacgwuqg3wsvpphjet4,task_subcomment,NA
+make-wmf-branch doesn't play nice with existing extension branches,`make-extension-branches` skips when the branch already exists; we should probably duplicate that code.,1418241372,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5uacgwuqg3wsvpphjet4,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I tried to set up the MediaWiki Vagrant environment according to the steps described here: http://www.mediawiki.org/wiki/MediaWiki-Vagrant 
+I used the most current VirtualBox and Vagrant.
+When I tried to do vagrant up: mount.nfs: access denied by server while mounting. 
+
+Find the complete error here: {F20641}",1418226811,PHID-USER-pxdyvyvhcyeu5efcjcgj,PHID-TASK-p72kac32ipfr5e6rjj23,task_description,declined
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","Declining for now per inactivity and the task being filed in 2014 with Ubuntu 14, which is a long time ago now.",1624383762,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#841751, @Mvolz wrote:
+> I have full disk encryption, but vagrant used to work for me (about 6 months ago?) and it's the same computer although I'm now on 14.04 instead of 13.* , since then- is this a new thing, that it's known not to work on fully encrypted disks but just on Trusty Tahr specifically?
+
+I'm using Vagrant and NFS with full disk encryption (not home directory).  However, I'm on Debian.",1504035811,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003
+
+**EDIT:** Spoke too soon again. If NFS is enabled the initial provisioning hangs on
+    ==> default: Notice: /Stage[main]/Apt/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+
+**EDIT2:** When NFS shares were off, I got LXC to work on Fedora 25. (they happened to be off when I set up LXC; I don't know what would happen if it was enabled on initial provisioning) NFS worked after reenabling NFS shares, but I felt LXC was faster without NFS, so I turned it back off.
+",1480901786,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003
+
+**EDIT:** Spoke too soon again. If NFS is enabled the initial provisioning hangs on
+    ==> default: Notice: /Stage[main]/Apt/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+
+**EDIT2:** After turning off NFS shares, I got LXC to work on Fedora 25. NFS worked after reenabling NFS shares, but I felt LXC was faster without NFS, so I turned it back off.
+",1480901745,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+~~When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:~~
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003
+
+**EDIT:** Spoke too soon again. If NFS is enabled the initial provisioning hangs on
+    ==> default: Notice: /Stage[main]/Apt/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+
+
+",1480894570,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+~~When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:~~
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+~~ from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003 ~~
+
+Spoke too soon again. If NFS is enabled the initial provisioning hangs on
+    ==> default: Notice: /Stage[main]/Apt/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+
+
+",1480894512,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003
+
+",1480879453,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I just encountered the same issue on Lubuntu 15.10 (Vagrant 1.8.1, VirtualBox 5.0.16 r105871).
+
+Using `vagrant config nfs_shares off` solved it for me",1459503528,PHID-USER-m7etbwqrv6cfrg5ymrwx,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",I just encountered the same issue on Lubuntu 15.10 (Vagrant 1.8.1 ,1459503431,PHID-USER-m7etbwqrv6cfrg5ymrwx,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I'm getting the same mount.nfs: access denied by server while mounting error.
+
+",1449213525,PHID-USER-ie5zvlm4dg5baq5cgxu4,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I'm getting a similar NFS 'access denied' on Fedora 23 alpha, no disk or home-dir encryption:
+
+{F1567690}",1439824812,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",I wonder if there is a way we can detect the use of ecryptfs and either give a better error message/warning to the user or just automatically disable nfs like we do for Windows.,1418502257,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.,1418502344,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",'access denied' also happens on Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.,1418501870,PHID-USER-pdlnbp2w5h2rej2hikwj,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#841751, @Mvolz wrote:
+> Additional info:
+> 
+> I have full disk encryption, but vagrant used to work for me (about 6 months ago?) and it's the same computer although I'm now on 14.04 instead of 13.* , since then- is this a new thing, that it's known not to work on fully encrypted disks but just on Trusty Tahr specifically?
+
+NFS was made the default disk sharing option on 2014-05-23 (<https://gerrit.wikimedia.org/r/#/c/134995/>).  The ability to easily turn this off due to encryption was added on 2014-08-14 (<https://gerrit.wikimedia.org/r/#/c/154153/>).
+
+> I was able to complete vagrant up with NFS shares off, but unfortunately still with errors. 
+> 
+> While there is a server running at http://127.0.0.1:8080/ I get File not found: /vagrant/mediawiki/index.php. Alas! 
+> 
+> Output of vagrant up:
+> 
+> Stderr from the command:
+> 
+> stdin: is not a tty
+> Error: composer install --optimize-autoloader returned 1 instead of one of [0]
+
+This composer failure looks to be the root cause of the rest of the failures. Running `PUPPET_DEBUG=1 vagrant provision | tee puppet.log` or manually running `composer install --optimize-autoloader` in /vagrant/mediawiki may lead to more information on the reason for this failure.",1418315007,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","Additional info:
+
+I have full disk encryption, but vagrant used to work for me (about 6 months ago?) and it's the same computer although I'm now on 14.04 instead of 13.* , since then- is this a new thing, that it's known not to work on fully encrypted disks but just on Trusty Tahr specifically?
+
+I was able to complete vagrant up with NFS shares off, but unfortunately still with errors. 
+
+While there is a server running at http://127.0.0.1:8080/ I get File not found: /vagrant/mediawiki/index.php. Alas! 
+
+Output of vagrant up:
+
+Stderr from the command:
+
+stdin: is not a tty
+Error: composer install --optimize-autoloader returned 1 instead of one of [0]
+Error: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: change from notrun to 0 failed: composer install --optimize-autoloader returned 1 instead of one of [0]
+Error: /usr/local/bin/multiversion-install wiki admin --dbname wiki --dbpass vagrant --dbuser root --pass vagrant --scriptpath /w --server http://127.0.0.1:8080 --confpath /vagrant/settings.d/wikis/wiki 
+ returned 1 instead of one of [0]
+Error: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_setup]/returns: change from notrun to 0 failed: /usr/local/bin/multiversion-install wiki admin --dbname wiki --dbpass vagrant --dbuser root --pass vagrant --scriptpath /w --server http://127.0.0.1:8080 --confpath /vagrant/settings.d/wikis/wiki 
+ returned 1 instead of one of [0]
+Warning: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_include_extra_settings]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Mediawiki::Extension::Browsertests[VisualEditor]/Browsertests::Bundle[VisualEditor_browsertests_bundle]/Ruby::Bundle[VisualEditor_browsertests_bundle]/File[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/.bundle/config]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Mediawiki::Extension::Browsertests[VisualEditor]/Browsertests::Bundle[VisualEditor_browsertests_bundle]/Ruby::Bundle[VisualEditor_browsertests_bundle]/Exec[bundle_install_VisualEditor_browsertests_bundle]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Codeeditor/Mediawiki::Extension[CodeEditor]/Git::Clone[mediawiki/extensions/CodeEditor]/Exec[git_clone_mediawiki/extensions/CodeEditor]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Parserfunctions/Mediawiki::Extension[ParserFunctions]/Git::Clone[mediawiki/extensions/ParserFunctions]/Exec[git_clone_mediawiki/extensions/ParserFunctions]: Skipping because of failed dependencies
+Warning: /Stage[main]/Mediawiki/Exec[copy_LocalSettings]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Cite/Mediawiki::Extension[Cite]/Git::Clone[mediawiki/extensions/Cite]/Exec[git_clone_mediawiki/extensions/Cite]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Git::Clone[mediawiki/extensions/VisualEditor]/Exec[git_clone_mediawiki/extensions/VisualEditor]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Templatedata/Mediawiki::Extension[TemplateData]/Git::Clone[mediawiki/extensions/TemplateData]/Exec[git_clone_mediawiki/extensions/TemplateData]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Wikieditor/Mediawiki::Extension[WikiEditor]/Git::Clone[mediawiki/extensions/WikiEditor]/Exec[git_clone_mediawiki/extensions/WikiEditor]: Skipping because of failed dependencies
+Warning: /Stage[main]/Browsertests/Mediawiki::User[Selenium_user]/Exec[mediawiki_user_Selenium_user]: Skipping because of failed dependencies
+Warning: /Stage[main]/Mediawiki::Parsoid/Mediawiki::Extension[Parsoid]/Git::Clone[mediawiki/extensions/Parsoid]/Exec[git_clone_mediawiki/extensions/Parsoid]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Geshi/Mediawiki::Extension[SyntaxHighlight_GeSHi]/Git::Clone[mediawiki/extensions/SyntaxHighlight_GeSHi]/Exec[git_clone_mediawiki/extensions/SyntaxHighlight_GeSHi]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Wikieditor/Mediawiki::Extension[WikiEditor]/Mediawiki::Settings[WikiEditor]/File[/vagrant/settings.d/puppet-managed/10-WikiEditor.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Codeeditor/Mediawiki::Extension[CodeEditor]/Mediawiki::Settings[CodeEditor]/File[/vagrant/settings.d/puppet-managed/10-CodeEditor.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Cite/Mediawiki::Extension[Cite]/Mediawiki::Settings[Cite]/File[/vagrant/settings.d/puppet-managed/10-Cite.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Mediawiki::Settings[VisualEditor]/File[/vagrant/settings.d/puppet-managed/10-VisualEditor.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Templatedata/Mediawiki::Extension[TemplateData]/Mediawiki::Settings[TemplateData]/File[/vagrant/settings.d/puppet-managed/10-TemplateData.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Geshi/Mediawiki::Extension[SyntaxHighlight_GeSHi]/Mediawiki::Settings[SyntaxHighlight_GeSHi]/File[/vagrant/settings.d/puppet-managed/10-SyntaxHighlight_GeSHi.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Parserfunctions/Mediawiki::Extension[ParserFunctions]/Mediawiki::Settings[ParserFunctions]/File[/vagrant/settings.d/puppet-managed/10-ParserFunctions.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Mediawiki::Parsoid/Mediawiki::Extension[Parsoid]/Mediawiki::Settings[Parsoid]/File[/vagrant/settings.d/puppet-managed/10-Parsoid.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Scribunto/Mediawiki::Extension[Scribunto]/Git::Clone[mediawiki/extensions/Scribunto]/Exec[git_clone_mediawiki/extensions/Scribunto]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Scribunto/Mediawiki::Extension[Scribunto]/Mediawiki::Settings[Scribunto]/File[/vagrant/settings.d/puppet-managed/10-Scribunto.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Mediawiki::Jobrunner/Service[jobrunner]: Skipping because of failed dependencies
+Warning: /Stage[main]/Apache/Service[apache2]: Skipping because of failed dependencies
+
+
+
+",1418310778,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","Sputniza, does doing
+
+vagrant config nfs_shares off
+
+then
+
+vagrant reload
+
+Work for you? ",1418300540,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#837045, @Mvolz wrote:
+> exportfs: /home/marielle/Code/vagrant does not support NFS export
+
+This last error message sounds like /home/marielle is an encrypted partition. The only fix for this is to disable the use of nfs for your Vagrant shares. We have a command in our plugin that makes that pretty easy: `vagrant config nfs_shares off`",1418230398,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I am getting the same error on Ubuntu 14.04 with the most recent version of vagrant and virtualbox 4.3.12r93733
+
+nfsd running
+exportfs: duplicated export entries:
+exportfs: 	10.11.12.13:/home/marielle/Code/vagrant
+exportfs: 	10.11.12.13:/home/marielle/Code/vagrant
+exportfs: /home/marielle/Code/vagrant does not support NFS export
+
+default: Mounting NFS shared folders...
+The following SSH command responded with a non-zero exit status.
+Vagrant assumes that this means the command failed!
+
+mount -o 'noatime,rsize=32767,wsize=32767,async' 10.11.12.1:'/home/marielle/Code/vagrant' /vagrant
+
+Stdout from the command:
+
+
+
+Stderr from the command:
+
+stdin: is not a tty
+mount.nfs: access denied by server while mounting 10.11.12.1:/home/marielle/Code/vagrant
+",1418227215,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I am getting the same error on Ubuntu 14.04 with the most recent version of vagrant:
+
+nfsd running
+exportfs: duplicated export entries:
+exportfs: 	10.11.12.13:/home/marielle/Code/vagrant
+exportfs: 	10.11.12.13:/home/marielle/Code/vagrant
+exportfs: /home/marielle/Code/vagrant does not support NFS export
+==> default: Mounting NFS shared folders...
+The following SSH command responded with a non-zero exit status.
+Vagrant assumes that this means the command failed!
+
+mount -o 'noatime,rsize=32767,wsize=32767,async' 10.11.12.1:'/home/marielle/Code/vagrant' /vagrant
+
+Stdout from the command:
+
+
+
+Stderr from the command:
+
+stdin: is not a tty
+mount.nfs: access denied by server while mounting 10.11.12.1:/home/marielle/Code/vagrant
+",1418227076,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"Due to a combination of factors, we haven't been able to line up a good mentorship for @memeht in the #Performance-Metrics-Dashboard project yet. This has caused a delay in her start on this program. This needs to be solved urgently. @Qgil is working on this. ",1418208428,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xgh4sxdhab2hhybxk42k,task_description,resolved
+Sort out Performance Metrics Dashboard mentorship,"@Memeht is now more than busy with @ssastry and @jdforrester-wmf. I will continue acting as ""generic mentor"". This task is resolved now. Thank you Chrsity for your patience, and thank you Subbu and James for stepping in!",1421403221,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"Yesterday @Memeht and I had our weekly meeting. She is busy with tasks, she has questions that can find answers in the Analytics mailing list and the Parsoid IRC channel. I'm supporting her as generic mentor for now, but this is a task that I'm doing reactively when she has questions. I think this is going as good as it could during the Winter holidays, considering the situation in which we were just ten days ago.  :)",1419930584,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"@Jdforrester-wmf has volunteered to find a project for @memeht and mentor her, as soon as he is back from vacation in January. In the meantime, he proposed this task: {T84949}
+
+For the period between now and James' return, @ssastry has created {T85232}, a task that he is happy to mentor.
+
+While these tasks were defined, I started the routing of weekly meetings with Christy, and I also pointed her to look at [[ https://www.mediawiki.org/wiki/Annoying_little_bugs | annoying little bugs ]], in the case she finished with the interim work.
+
+The situation is far from ideal, but I'm personally happy for having reached to this point during these pre-holidays dates, and I'm very thankful for Subbu's and James' help.",1419359486,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"@Memeht, altough it is being extremely difficult to find a mentor available in these pre-vacation days, we are narrowing down the area where your work is welcome: improving the metrics for VisualEditor, a key feature in the modernization of Wikipedia and wiki editing in general. Here you have some pointers:
+
+* https://www.mediawiki.org/wiki/Editing (note that two former interns work in this team, @mvolz and @MSchottlender-WMF)
+* https://www.mediawiki.org/wiki/VisualEditor (check ""Statistics"" under ""See also"")
+* https://www.mediawiki.org/wiki/Editing_performance
+
+I will create some tasks under #Performance-Metrics-Dashboard",1418947048,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"@Memeht, altough it is being extremely difficult to find a mentor available in these pre-vacation days, we are narrowing down the area where your work is welcome: improving the metrics for VisualEditor, a key feature in the modernization of Wikipedia and wiki editing in general. Here you have some pointers:
+
+* https://www.mediawiki.org/wiki/Editing (note that two former interns work in this team, @mvolz and @MSchottlender-WMF)
+* https://www.mediawiki.org/wiki/VisualEditor (check ""Statistics"" under ""See also"")
+* https://www.mediawiki.org/wiki/Editing_performance
+
+I will create some tasks under #Performance-Metrics-Dashboard
+
+<James_F> edit-reportcard.wmflabs.org needs lots of work.
+<James_F> But it will take 3–4 hours for me to specify what might be good there.
+<James_F> Saying ""make it better"" isn't helpful for her, I imagine.
+<James_F> https://phabricator.wikimedia.org/T84926 and https://phabricator.wikimedia.org/T84927 are very basic starts.",1418946148,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","Steps to reproduce:
+
+1. Set language to Indonesian (id).
+2. Open page in VisualEditor.
+3. Insert a table, or select an existing one.
+4. Click on the ""▾"" (down arrow) indicator next to the first cell.
+5. Notice that the words end with … rather than spelling out the entire text.
+
+Proposed solution:  Make the menu wider, because some languages require more space than English.
+",1418189274,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-55xswnakobrdktp5xg5z,task_description,resolved
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","Change 236871 merged by jenkins-bot:
+Slightly increase width of table context
+
+[[https://gerrit.wikimedia.org/r/236871]]",1441743811,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","Change 236871 had a related patch set uploaded (by Esanders):
+Slightly increase width of table context
+
+[[https://gerrit.wikimedia.org/r/236871]]
+",1441741345,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)",Think this is now resolved. Tried fr/pl/de/id/etc. and they all seemed to work.,1441740277,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)",Could anybody provide a pointer to the corresponding LESS file(s) so someone could give this a shot? Cannot find the right place. Thanks.,1437052509,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","Could anybody provide a pointer to the corresponding LESS file(s)? 
+I'm kind of curious if I can fix this but cannot find the right place. Thanks :)",1429645479,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","The three options are truncated in most languages I tried in Firefox 36:
+{F55266}
+Still wondering what exactly in oojs-ui makes it calculate
+```<div style=""height: auto; margin-left: -29.5px; width: 150px;"" class=""oo-ui-popupWidget-popup"">```
+(someone with more LESS skills could provide a pointer please?). 
+Not defining/calculating a ""width"" value would solve the problem (but would it create others? Don't think so).",1425512492,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"See screenshot:
+
+{F20260}",1418156016,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_description,resolved
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"Change 179551 merged by jenkins-bot:
+Hide extra space at the top of the single transclusion dialogs
+
+[[https://gerrit.wikimedia.org/r/179551]]",1422924744,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"The transitions are currently broken, and I think a bit OTT given we are transitioning the width of the entire dialog. I suggest just display:none-ing them.",1422662415,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"Change 179551 had a related patch set uploaded (by Alex Monk):
+Hide extra space at the top of the single transclusion dialogs
+
+[[https://gerrit.wikimedia.org/r/179551]]
+
+#patch-for-review",1418418129,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"It's because of how we try to hide the template page label on single transclusion dialogs (e.g. templates, citations): https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/45518019eb8b668df42a5b3886be8031f578fdee/modules/ve-mw/ui/styles/dialogs/ve.ui.MWTransclusionDialog.css#L55-L61
+
+We use all of that instead of display:none so we can fade it out (see transition lines above).
+
+Just need to work out why it still takes up room.",1418336451,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"Seems the same in Apex to me. It's a hidden oo-ui-labelElement-label containing the template name, above the template page description.",1418327934,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"https://wikimediafoundation.org/w/index.php?title=Special:Search&search=please%20check%20back&fulltext=Search&profile=all
+
+The search results here include files from Wikimedia Commons. This is kind of weird. It might be helpful if the Commons search results are of media that's actively used/referenced on the local wiki, but otherwise it's just kind of strange and unexpected to include a foreign wiki's search results alongside the local wiki's, especially without a clear opt-out mechanism.
+
+See also: {T94856}",1417909769,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-gbf4krxvukazedeyc7t6,task_description,resolved
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"Thanks for the deploy, @Krenair and @ThCipriani. Closing as resolved.",1441035308,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1589458, @Jdforrester-WMF wrote:
+> Oh, interesting. When? This probably explains the complete breakage of media inserting on officewiki we had to fix a few weeks ago… 
+
+It was done in [[https://gerrit.wikimedia.org/r/#/c/204536/|this patch]], so April 2015.",1441035254,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1576570, @Deskana wrote:
+>>>! In T76957#1576565, @Jdforrester-WMF wrote:
+>> Won't this break VisualEditor for inserting images on Foundationwiki?
+> 
+> Inserting images from Commons using VisualEditor seems to work just fine on officewiki, and officewiki already had this config change applied to it.
+
+Oh, interesting. When? This probably explains the complete breakage of media inserting on officewiki we had to fix a few weeks ago… 
+",1441035072,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"Change 234040 merged by jenkins-bot:
+Remove files from Commons from search results on wikimediafoundation.org
+
+[[https://gerrit.wikimedia.org/r/234040]]",1441034644,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1576565, @Jdforrester-WMF wrote:
+> Won't this break VisualEditor for inserting images on Foundationwiki?
+
+No, what VE does is look up the actual file repositories set up on the local wiki and searches each one separately, I don't think it relies on local search to include foreign file repository results.",1440617366,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1576565, @Jdforrester-WMF wrote:
+> Won't this break VisualEditor for inserting images on Foundationwiki?
+
+No, what VE does is look up the actual file backends set up on the local wiki and searches each one separately, I don't think it relies on the local search backend to include foreign repository results.",1440617330,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1576565, @Jdforrester-WMF wrote:
+> Won't this break VisualEditor for inserting images on Foundationwiki?
+
+Inserting images from Commons using VisualEditor seems to work just fine on officewiki, and officewiki already had this config change applied to it. Given that, I find it unlikely that this will affect VisualEditor on foundationwiki.",1440615698,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,Won't this break VisualEditor for inserting images on Foundationwiki?,1440615464,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"Change 234040 had a related patch set uploaded (by Deskana):
+Remove files from Commons from search results on wikimediafoundation.org
+
+[[https://gerrit.wikimedia.org/r/234040]]
+",1440615300,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1462538, @Krenair wrote:
+> Getting community consensus on foundationwiki sounds interesting. Who needs to approve this?
+
+Well, Discovery owns search across all of our sites, and I'm the PM for Discovery, so why don't we say me? :-)",1440615156,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,Getting community consensus on foundationwiki sounds interesting. Who needs to approve this?,1437249304,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"We can now use ""file:local:cat"" for searching local files. See https://gerrit.wikimedia.org/r/#/c/204536/",1429202861,PHID-USER-lsveyqlsb4acoowxr5yj,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Upstream reports: https://secure.phabricator.com/T6102 and https://secure.phabricator.com/T8510
+
+**Workaround by valhallasw: 
+Execute `JX.TypeaheadSource.prototype.setMaximumResultCount(100)` in the javascript console (or a userscript)** to get more results displayed. Userscripts at P2444 (Chrome) and P2445 (Firefox)
+
+When typing in the ""projects"" field in the ""edit task"" or ""edit search"" view, phabricator offers up to 5 suggestions/completions. But sometimes, the exact match for what I just typed is not included in this list. This makes it impossible for me to enter these projects anywhere (for me, this happens for ""wikidata"" - I see ""wikidata.org"" etc, but not ""wikidata""). Interestingly, these suggestions look different for other users (with the same input, they do get ""wikidata"", though it's only in the 4th slot), so it seems the ranking in the suggester is user-specific (projects that I am a member of get boosted, or some such). 
+
+In any case: exact matches should always win. If I enter a full name and hit enter, this should always work if a project by this name exists.
+
+I'm setting this to ""high"" since it makes it pretty much impossible for me to work with phab.
+
+PS: I suppose the same issue exists for all fields that use the suggester/tag logic, but I did not run into any problems with other fields yet.
+
+{F39253}",1417710278,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-h64673nwftdciwancqe4,task_description,resolved
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#3040513 in February 2017, @Aklapper wrote:
+> Upstream task https://secure.phabricator.com/T8510#202060 is only still open because
+> * #Maps and #Discovery entered in the global search bar aren't in first position,
+I cannot reproduce this problem anymore.
+> * The ""In Any"" and ""Not In"" options [[ https://secure.phabricator.com/T8510#200936 | are not always offered ]] for exact project name matches in the ""Tags"" field of Maniphest's Advanced Search form. **Workaround:** Explicitly write `not(wikidata)` to get `Not in: Wikidata`.
+I'd always recommend to use `not(project`) and `any(project)`.
+I documented this in https://www.mediawiki.org/w/index.php?title=Phabricator%2FSearch&type=revision&diff=2818193&oldid=2806870
+
+As I am not aware of any further problems I am closing this task as resolved.",1530265110,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Upstream task https://secure.phabricator.com/T8510#202060 is only still open because
+* #Maps and #Discovery entered in the global search bar aren't in first position,
+* The ""In Any"" and ""Not In"" options [[ https://secure.phabricator.com/T8510#200936 | are not always offered ]] for exact project name matches in the ""Tags"" field of Maniphest's Advanced Search form. **Workaround:** Explicitly write `not(wikidata)` to get `Not in: Wikidata`.
+
+In general the situation has improved a lot since this task was created, hence lowering its priority.",1487596072,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I have tested with #visualeditor, which wouldn't show up before due to all the related subprojects. Now it appears in the first position. Good!",1479467748,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"In the search bar in the toolbar at the top of the screen, searching for ""Maps"" brings up Maps as the third option. Searching for ""Discovery"" brings up Discovery as the second option. 
+
+When editing a task and entering tags, autocomplete does bring up Maps and Discovery as the first items. 
+
+This task was originally filed for the editing case, so although I personally think both cases should be fixed, it seems the remaining issues should be captured in a separate task.  ",1479415206,PHID-USER-pmfo3xmfjado5j3dqmio,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"https://secure.phabricator.com/T8510#199629 states this should be pretty much resolved. 
+We're now running that version here, with an [[ https://secure.phabricator.com/rPb02f64f6eecd1d3b7b1c573f108d5a2c8f35497f | additional backported patch ]] on top. And so far it looks like a great improvement!
+
+Testing in the `Tags` field on https://phabricator.wikimedia.org/maniphest/query/advanced/ , some stuff surprised me:
+* Entering `Labs not` displays `Not In: Labs` as 4th item. 
+* Entering `labs not in` only displays `Not In: Labs-Infrastructure` but not `Not In: Labs`
+* Entering `Wikidata` now shows the `Wikidata` project as the first result. \o/
+* I have not been successful yet in getting `Not in: Wikidata` offered somehow. Entering `wikidata in` I only get three options related to the `MediaWiki-extensions-WikibaseMediaInfo` project.
+
+If anyone has examples of exact matches **not** getting offered first, please add them to this task.",1479412808,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"The original request was ""exact matches should always win"", which I interpret as saying they should always be the top match. And I agree. I'm frustrated that for some reason it seems like that change isn't going to be made. 
+
+If this task is closed (which I wouldn't object to at this point), I really think it should be ""declined"", not ""resolved"".  It's really not resolved/fixed. But at least in most cases the exact match seems to be shown in the list. Even if it's at the bottom rather than the top. ",1477605918,PHID-USER-pmfo3xmfjado5j3dqmio,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"The original request was ""exact matches should always win"", which I interpret as saying they should always be the top match. And I agree. I'm frustrated that for some reason it seems like that change isn't going to be made. 
+
+If this task is closed (which I wouldn't object to at this point), I really think it should be ""declined"", not ""resolved"".  It's really not resolved/fixed. But in most cases the exact match seems to be shown in the list. Even if it's at the bottom rather than the top. ",1477605894,PHID-USER-pmfo3xmfjado5j3dqmio,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"The original request was ""exact matches should always win"", which I interpret as saying they should always be the top match. And I agree. I'm frustrated that for some reason it seems like that change isn't going to be made. 
+
+If this task is closed (which I wouldn't object to at this point), I really think it should be ""declined"", not ""resolved.  It's really not resolved/fixed. But in most cases the exact match seems to be shown in the list. Even if it's at the bottom rather than the top. ",1477605870,PHID-USER-pmfo3xmfjado5j3dqmio,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I think I see the issue- by searching wikidata on the general form, #wikidata is not on top. I think that is a different issues than entering ""wikidata"" in a project-specific form (like creating a new ticket)- and not necessarily something we want (needs discussion). I would suggest to close this one as resolved and not increase the scope of it. If I write `#wikidata` or `#wikidata-query` on this very same same test form, I get exact results as expected while I am writing.
+
+Then create a new subtask, if needed, of T146843 as that is related to improve general search results, and not to auto-complete (which seems mostly fine).",1476699449,PHID-USER-gzd4fguky5ixnvz46fvu,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@lydia_pintscher to me it looks like it's fixed now. At least for the cases I've tried, #Wikidata was always at the top or at least in the list.
+{F4611530}",1476698805,PHID-USER-t4sxxglz6yyrgxeib43i,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"At least for ""Wikidata"" the situation is still bad unfortunately.",1476447894,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I see some issues, but is the original complain still valid?
+{F4602448}
+{F4602447}",1476433532,PHID-USER-gzd4fguky5ixnvz46fvu,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Removing Phabricator (2016-06-29) project since https://secure.phabricator.com/T8510 is still open and no time frame for that to be fixed.,1468242410,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I think the last one might be because there are a ton of additional hashtags on some of the wikidata related projects, causing them to win out in the relevance scoring.
+
+For example:
+
+#mediawiki-extensions-wikibaseclient has the following 'additional hashtags':
+
+`#MediaWiki-extensions-WikidataClient`, `#mediawiki-extensions-wikidataclient`, `#MediaWiki-extensions-Wikibase-Client`, `#MediaWiki-extensions-Wikibase+Client`, `#mediawiki-extensions-wikibase+client`",1466070166,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"For the records, https://secure.phabricator.com/T6102 is fixed upstream; https://secure.phabricator.com/T8510 not yet. 
+
+Status of three testcases, after latest deployment on 2016-06-15:
+
+**Discovery** (which has numerous additional hashtags):
+* ✔ Using ""Change Project Tags"" under ""Actions"" above the field to add a Comment and entering ""Discovery"", the 2nd item among the 5 proposals is ""Discovery"".
+* ✔ Using the global search in the upper right corner, ""Discovery"" is the 2nd item among the 10 proposals.
+* ✔ Using the ""Tags"" field on https://phabricator.wikimedia.org/maniphest/query/advanced/ and entering ""Discovery"", it is the 2nd item among the 5 proposals.
+
+**Labs** (which has no additional hashtags):
+* ✔ Using ""Change Project Tags"" under ""Actions"" above the field to add a Comment and entering ""Labs"", it is the 1st item among the 5 proposals.
+* ✔ Using the global search in the upper right corner, ""Labs"" is the 7th item among the 10 proposals.
+* ✔ Using the ""Tags"" field on https://phabricator.wikimedia.org/maniphest/query/advanced/ and entering ""Labs"", it is the 1st item among the 5 proposals.
+
+
+**Wikidata** (which has no additional hashtags):
+* ✔ Using ""Change Project Tags"" under ""Actions"" above the field to add a Comment and entering ""Wikidata"", it is the 1st item among the 5 proposals.
+* ✔ Using the global search in the upper right corner, ""Wikidata"" is the 10th item among the 10 proposals.
+* ✗ Using the ""Tags"" field on https://phabricator.wikimedia.org/maniphest/query/advanced/ and entering ""Wikidata"", it is **NOT** among the 5 proposals:
+{F4171138}",1466069281,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"(This is a test, clicking the search button, typing ""Wikidata"", and selecting it from the long list.)",1465982367,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#2382047, @Sjoerddebruin wrote:
+> … it's not possible to add the project Wikidata to tasks.
+
+Click the search button then select it.
+
+",1465980520,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Nothing seems to be changed, it's still not possible to add the project Wikidata to tasks.",1465980500,PHID-USER-pr6rfjdcmkknkex6dgn5,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Problem seems to became more worse, it's not possible to add the project Wikidata to tasks.",1465980343,PHID-USER-pr6rfjdcmkknkex6dgn5,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"More fixes coming this week, hopefully this one is fully fixed after the update.",1465668833,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"https://secure.phabricator.com/T8510 is not fully fixed yet, and this can still be reproduced trying to add ""Wikidata"" for example.",1465494314,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#1334152, @Nemo_bis wrote:
+> I'd also expect exact match of secondary hashtags to win.
+> 
+> {F173832}
+
+Was this supposed to happen, after T135068? It didn't.",1465492331,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@Qgil: Thanks for pointing to that. It looks like they're going to sort the projects by displayed name, which should at least fix the Discovery case.
+
+I still think their fix is ""wrong"", in the sense that I believe that an exact match should always win, no matter what order the results appear in. But it should be ""good enough"", at least for the cases I'm aware of. ",1464383656,PHID-USER-pmfo3xmfjado5j3dqmio,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Allegedly fixed upstream: https://secure.phabricator.com/T8510#177463,1464295052,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,@ksmith: I totally agree that this is a problem and also that the upstream task may not be exactly applicable. I only linked it because it seemed somewhat relevant. ,1464231555,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@mmodell : It is not clear to me that the upstream task would actually fix this issue. I think we should either get this case explicitly called out in that task, or we should file a new upstream task.  
+
+As a specific reproducible example, in case anyone needs one: Entering Discovery in the Tags field  still does not offer #Discovery, which has been frustrating us for over a year. 
+",1464148795,PHID-USER-pmfo3xmfjado5j3dqmio,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"There is still one upstream task[1] that remains open, unlike most of the related tasks about this issue which have been closed as either resolved or invlaid, without totally resolving the underlying problems. 
+
+[1]: https://secure.phabricator.com/T7858",1464050933,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I use a greasemonkey script to get around this problem.  This overrides the suggestion-limiter to 100. 
+It's documented onwiki at https://www.mediawiki.org/wiki/Team_Practices_Group/Phabricator_tips/Maniphest#Autocomplete_limit
+and quick install at https://openuserjs.org/scripts/quiddity-wp/wikimedia_phabricator_suggestion_expander
+
+However, it's only partially successful in some instances, such as the new ""Actions"" dropdown menus, and I haven't had time to investigate/fix it. (I assume z-index... but that's all a little outside my familiarity.)
+{F4036179}",1463779832,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Things got worse with the subprojects: {F3625114},1457861656,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Still an issue. Example: Enter [[ https://phabricator.wikimedia.org/project/profile/1174/ | discovery ]] (the primary name of a project) in the Projects field on https://phabricator.wikimedia.org/maniphest/query/advanced/ , the five proposals do not include the ""Discovery"" project itself.
+
+I've created https://secure.phabricator.com/T8510",1434023342,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I'd also expect exact match of secondary hashtags to win.
+
+{F173832}",1433347649,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Yes, can confirm.",1432157106,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"This is not working for me, as described as part of T99739. I don't feel bold enough to reopen it myself, but believe that it should be reopened. 
+",1432136871,PHID-USER-pmfo3xmfjado5j3dqmio,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"This is not fixed for me by https://secure.phabricator.com/rP49ee09be3f453386c91820e990d6916887206eb6
+At least not in a way that I would have expected:
+{F166948}
+Can someone confirm?",1432074282,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,It works!!!,1424277155,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#1024884, @JanZerebecki wrote:
+> Why not deploy the fix
+
+-> T86772",1423497288,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Why not deploy the fix, that was merged upstream a month ago?",1423495096,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"At least you could type ""#Wikidata_"" and get the result. But yes, mentioning the project in comments/descriptions is simpler and cleaner.",1423478770,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"how would renaming to ""#Wikidata_"" work around the issue? Alphabetical sorting isn't the problem, as far as I can tell.",1423478544,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#1019339, @Qgil wrote:
+> What about renaming Wikidata to #Wikidata_ , as an interim solution?
+
++1, if it's technically possible.
+
+This is an intuitive solution. By ""intuitive"" I mean that I tried adding ""#Wikidata"" to a task before I gave up and asked @Lydia_Pintscher for help :)",1423472330,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"What about renaming Wikidata to #Wikidata_ , as an interim solution?",1423173349,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Any idea when this will go live here? It is super annoying for Wikidata :(,1422958874,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Fixed upstream: https://secure.phabricator.com/T6102,1420849323,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"No.
+
+And my patch hasn't landed locally, so you won't see its effects yet.",1419526487,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"> 1) Open https://phabricator.wikimedia.org/maniphest/task/create/
+> 2) Type ""MediaWiki"" in ""Projects"" field
+>
+> I. Observed: first option offered is ""DataTypes""
+> II. Expected: first options offered start with ""MediaWiki""
+
+Chad, does your upstream patch reverse the ""normal"" behaviour and favour frequent words over non-frequent ones, or something like that. For instance, when I type ""Pha"" I'm most likely looking for #Phabricator or #Phabricator.org, not for § Phabricator Sprint Extension [2014-12-11]",1419498934,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@Jdlrobson, when this task is fixed (hopefully soon), you can expect the same results that you get typing ""mobile"" in the header search field. At least for me these are 
+
+# Mobile
+# Mobile-Apps
+# Mobile-Web
+# Blocked-on-Mobile-Apps
+# ...
+
+This sorting makes total sense.",1418939943,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"As described in T75737 by valhallasw, as a workaround for the time being, please execute
+
+```
+JX.TypeaheadSource.prototype.setMaximumResultCount(100)
+```
+
+in the javascript console (or a userscript).",1418649214,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,I'm reopening this for the time being.,1418292044,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@daniel, can you at least select ""Wikidata"" now?
+
+I have commented in the related upstream task: https://secure.phabricator.com/T6102#87052",1418283692,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#838951, @chasemp wrote:
+> We may need to reindex search...
+
+Not for a change like that. We will anyway after [[ https://secure.phabricator.com/D10955 | Upstream D10955 ]] or something like it lands anyway.",1418244321,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,We may need to reindex search...,1418244150,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Not convinced this really got fixed - bypassing the browser cache, going to  ""edit task"" here and literally entering ""wikidata"" in the project field, that project is still shown as the fourth one to me. 
+
+Not sure if there's some caching server-side?
+
+How are the results for others?",1418242661,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Great! Resolving. According to T76522, the next upgrade should happen latest by next Wednesday.",1417766074,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Thanks for the pointer! Reading the relevant code was fun :)
+That should indeed fix it, please update soon... ",1417730686,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"In theory this was fixed upstream on November 17: https://secure.phabricator.com/T6102
+
+I don't recall when exactly we upgraded our instance, but it was around that time. Maybe @chasemp or @aklapper can tell whether the related diff made it to our instance or not? If not, we are planning to upgrade one of these days (to install the Sprint app, among other things).",1417721698,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Provide real-time collaboration in VisualEditor-MediaWiki,"Exceptionally hard, many issues, yada yada yada.
+
+Still, this would be an excellent thing to provide our users.",1417568581,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mto5lbev7aopkjbicd5f,task_description,open
+Provide real-time collaborative editing in VisualEditor,"This is about VisualEditor-core, not VisualEditor-MediaWiki for which there are a bunch of issues that would need to be solved first.",1417568021,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lddwevjhaszbxshxxywi,task_description,open
+Convert hyphens to en dashes when written in VisualEditor,"I dont know, how is it in English punctuation, but suprisinglly hyphen mark, which is naturally present on all keyboards is not so much used in the texts. Wikipedia is based especially on texts so it would be a nice feature to VE to have a choise to replace hyphen by En dash, which is much more need in the text at times when you hit hyphen bar.
+
+Now we should insert that symbol, by inserting the symbol - that is in fact not known to not skilled newbies. On the other side, it slow down the skilled editors. If they want to write a clear text from the beggining, the have to stop, insert en dash and continue.",1417305712,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_description,declined
+Convert hyphens to en dashes when written in VisualEditor,">>! In T76275#802670, @Jdforrester-WMF wrote:
+>>>! In T76275#802653, @Juandev wrote:
+>> Yes, I am suggesting that James. Em dash is also not so broadly used, so I would not take care of it.
+> 
+> OK. That's pretty easy to do, but it might be irritating (and we don't have a way to make sequence substitutions only work on some wikis or for some users), so I'd appreciate some other input on whether this is a good idea.
+
+Not a good idea. Hyphen is quite often used legally (eg. in names) and semi-legally (instead of minus), so enforcing its converting to en/em dash is wrong. Also other pars of wikitext can contain hyphens (data-* attributes, classnames, id's, template names etc. etc...)
+
+I barely remember there was a task about convertig -- to en dash and --- to em dash on page save (so the next user would see the proper Unicode character in editbox next time), but I can't find it ATM.
+
+WONTFIXing this because of the reasons above and in favour of the mentioned task.",1454199276,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+Convert hyphens to en dashes when written in VisualEditor,">>! In T76275#802653, @Juandev wrote:
+> Yes, I am suggesting that James. Em dash is also not so broadly used, so I would not take care of it.
+
+OK. That's pretty easy to do, but it might be irritating (and we don't have a way to make sequence substitutions only work on some wikis or for some users), so I'd appreciate some other input on whether this is a good idea.",1417559998,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+Convert hyphens to en dashes when written in VisualEditor,"Yes, I am suggesting that James. Em dash is also not so broadly used, so I would not take care of it.",1417559639,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+Convert hyphens to en dashes when written in VisualEditor,"Just to note - VE preserves hyphen, en-dash, and em-dash typed with regular keyboard shortcuts(on Mac - Option+- for en-dash and Shift+Option+- for em-dash).
+hyphen -
+en-dash –
+em-dash —",1417475354,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+Convert hyphens to en dashes when written in VisualEditor,"What are you suggesting? That if I type ""foo-bar"" it changes it to ""foo–bar""? What about em-dash? Should ""foo - bar"" be changed to ""foo — bar""?",1417474814,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to","The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to. It should probably include the ""continue"" message as a parameter.",1416988401,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_description,resolved
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to",Thanks to David for merging.,1417197627,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to","Change 176298 merged by jenkins-bot:
+Mention the ""Continue"" label as a parameter in visualeditor-recreate
+
+[[https://gerrit.wikimedia.org/r/176298]]",1417195377,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to","Change 176298 had a related patch set uploaded (by Amire80):
+Mention the ""Continue"" label as a parameter in visualeditor-recreate
+
+[[https://gerrit.wikimedia.org/r/176298]]
+
+#patch-for-review",1417120693,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to","Thanks, but I'd prefer to have it embedded. (A patch is ready.)",1417120659,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to",The message is <ooui-dialog-process-continue>. I've updated the qqq to reflect this.,1417034694,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"Load VisualEditor file from modules.json as a manifest, rather than tediously copying it into extension.json",,1416971459,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7blxbh53cp3cws3rmqek,task_description,duplicate
+VisualEditor: Calling buildNodeTree() manually should not be needed,"We explicitly call buildNodeTree() in a few places. Ideally, we would not need to do this outside of ve.dm.Document.
+
+Suspect calls (excluding dm.Document, excluding tests):
+
+lib/ve/src/ce/ve.ce.Surface.js
+1000:			doc.buildNodeTree();
+1711:		doc.buildNodeTree();
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416338280,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3iyil63ecpynuu65ebug,task_description,open
+VisualEditor: Calling buildNodeTree() manually should not be needed,"The node tree is lazily evaluated by buildNodeTree the first time you call getDocumentNode. In the examples your provide (paste and drag-drop) we call buildNodeTree after sanitisation has occurred, as sanitisation happens on the data model array.",1416340739,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3iyil63ecpynuu65ebug,task_subcomment,NA
+VisualEditor: DOM Exception (no user-facing loss of functionality?) after a long editing session,"After a prolonged session of editing in Safari, the following error was displayed: 
+
+[Error] Error: QuotaExceededError: DOM Exception 22 DOMException
+	log (load.php, line 150)
+	flush (load.php, line 173)
+
+
+No degradation in responsiveness/functionality was noticed. Should we handle this exception?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1416273720,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-v5jcyw7wftxsu6hvvjts,task_description,open
+VisualEditor: DOM Exception (no user-facing loss of functionality?) after a long editing session,"We should find out what this is before WONTFIXing, at least.",1416342245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v5jcyw7wftxsu6hvvjts,task_subcomment,NA
+VisualEditor: Discrepancy in displaying text with <mark>  in Edit and Read modes,"Read mode - all text is highlighted
+
+1. In VE type some text. Hit enter for the second line.
+
+Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling.
+ 
+2. Open Edit source(Keep changes) and add <mark> as in the sample below: 
+
+<mark>
+Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling. 
+
+3. Save - in Read mode all text on the page will be highlighted with the yellow background. 
+
+4. Switch to Edit mode again - only the first line will be displayed as highlighted. 
+
+The screenshots are attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14967}",1416269700,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-bzsupfbaq25gtun2byod,task_description,resolved
+VisualEditor: Discrepancy in displaying text with <mark>  in Edit and Read modes,This has been fixed when Parsoid and MediaWiki were updated to use the same HTML5 parsing algorithm (T89331).,1558272914,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-bzsupfbaq25gtun2byod,task_subcomment,NA
+VisualEditor: Discrepancy in displaying text with <mark>  in Edit and Read modes,"Created attachment 17155
+Edit mode - only the first line is highlighted
+
+**Attached**: {F14968}",1416269795,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-bzsupfbaq25gtun2byod,task_subcomment,NA
+VisualEditor: ve-ce-focusableNode-dropMarker is displayed as a horizontal line when Gallery is dragged-drop to Media Caption,"dragging gallery to Media
+
+1. VE: insert media(a picture) and a gallery.
+
+2. Attempt to drag a gallery into Media and drop - a horizontal vertical line will be displayed. The screen recording is attached.  
+
+e.g.
+<div class=""ve-ce-focusableNode-dropMarker"" style=""width: 1048px;"">
+
+
+Note: happens *only* with dragging  a gallery.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14943}",1416263460,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-aiczpu2ygn72rpiek6xz,task_description,resolved
+VisualEditor: ve-ce-focusableNode-dropMarker is displayed as a horizontal line when Gallery is dragged-drop to Media Caption,"This doesn't seem to be a problem any more. It was probably caused by some exception in drag-and-drop code preventing it from cleaning up the marker after the content was dropped, but it would be a lot of effort to try to reproduce that now.",1577744177,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-aiczpu2ygn72rpiek6xz,task_subcomment,NA
+VisualEditor: ve-ce-focusableNode-dropMarker is displayed as a horizontal line when Gallery is dragged-drop to Media Caption,"Those thin lines are visible only in VE - they are not preserved upon saving, so the priority is Low.",1423275582,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-aiczpu2ygn72rpiek6xz,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"User:Tacsipacsi at the Hungarian Wikipedia reports issues with ""the new buttons"" and provides the following log:
+
+```
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/index.html
+HTML style attribute
+Invalid value for property: zoom
+Line 1:
+  display:inline;margin:0;border:0;padding:1px;width:1px;zoom:1
+  -------------------------------------------------------------^
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/oojs-ui-mediawiki.svg.css
+Linked-in stylesheet
+Invalid value for property: -webkit-transform
+Line 957:
+    -webkit-transform: translateZ(0px);
+  -------------------------------------^
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/oojs-ui-mediawiki.svg.css
+Linked-in stylesheet
+Invalid value for property: -o-transform
+Line 960:
+    -o-transform: translateZ(0px);
+  --------------------------------^
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/oojs-ui-mediawiki.svg.css
+Linked-in stylesheet
+Invalid value for property: transform
+Line 961:
+    transform: translateZ(0px);
+  -----------------------------^
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/styles/demo.css
+Linked-in stylesheet
+Declaration syntax error
+Line 197:
+   width: calc(100% - 40px);
+  --------------------------^
+```
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416245640,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jugonrend4wlvekztr4d,task_description,resolved
+OOjs UI: trouble with CheckboxInputWidget in Opera,"OK, I can go with it.",1424979350,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"Hmm. I can reproduce that now – when I double-click on the checkbox label (which results in text being selected), the checkbox appears in incorrect state, and fixes itself when I mouse away. This looks like a browser bug, and it doesn't seem to be easily resolvable – honestly, I'm not sure if it's worth worrying about.
+
+(It also doesn't seem to affect OOjs UI checkboxes – the ones used mostly in VisualEditor – but only MediaWiki UI checkboxes – the ones used on the login page, for example.)
+
+As for the CSS errors, they are harmless – MediaWiki uses certain technically invalid constructs to support both old browsers (mostly IE 6) and experimental features of new browsers . Error handling in CSS is well-defined and therefore these are not a problem.",1424973444,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"@matmarex: I tested again and the error is that there isn’t disappear until I move the cursor from the box. I don’t get any error messages while trying to click on the checkbox. I get the following //error//s while loading the page (not including //information//s):
+```
+lines=12
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s/BetaFeatures/resources/images/feature-discussion.svg?2014-09-30T20:31:40Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s/BetaFeatures/resources/images/feature-discussion.svg?2014-09-30T20:31:40Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /BetaFeatures/resources/images/feature-information.svg?2014-09-30T20:31:40Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /BetaFeatures/resources/images/feature-information.svg?2014-09-30T20:31:40Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: filter
+Line 1:
+  sform:scaleX(-1);-webkit-transform:scaleX(-1);transform:scaleX(-1);filter:FlipH;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ources/skins/vector/../../images/badge-silver-star.png?2014-09-30T20:46:40Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ources/skins/vector/../../images/badge-golden-star.png?2014-09-30T20:46:40Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  px solid #aaaaaa;background-color:#f9f9f9;padding:5px;display:-moz-inline-block;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  padding:5px;display:-moz-inline-block;display:inline-block;display:table;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  lay:-moz-inline-block;display:inline-block;display:table;zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  lerybox{vertical-align:top;display:inline-block}ul.gallery,li.gallerybox{zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -align:top;display:inline-block}ul.gallery,li.gallerybox{zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  style:none;list-style-type:none;list-style-image:none;vertical-align:middle !ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  e-height:1.15em;padding:0 .4em;border-left:1px solid #AAA;margin:0.1em 0;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ding:0 .4em;border-left:1px solid #AAA;margin:0.1em 0;zoom:1;display:inline !ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  sources/src/mediawiki.legacy/images/checker.png?2014-08-30T22:43:20Z) repeat!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ter/resources/src/mediawiki.legacy/images/question.svg?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ter/resources/src/mediawiki.legacy/images/question.svg?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  style:none;list-style-type:none;list-style-image:none;vertical-align:middle !ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  eight:1.25em;border-left:1px solid #AAA;margin:0.125em 0;padding:0 0.5em;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -left:1px solid #AAA;margin:0.125em 0;padding:0 0.5em;zoom:1;display:inline !ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  er/resources/src/mediawiki.legacy/images/feed-icon.svg?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  er/resources/src/mediawiki.legacy/images/feed-icon.svg?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  x{border:1px solid;padding:.5em 1em;margin-bottom:1em;display:-moz-inline-block;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  5em 1em;margin-bottom:1em;display:-moz-inline-block;display:inline-block;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ottom:1em;display:-moz-inline-block;display:inline-block;zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  ht:1.6em;margin-left:0}li.gallerybox{vertical-align:top;display:-moz-inline-box;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  op;display:-moz-inline-box;display:inline-block}ul.gallery,li.gallerybox{zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  inline-box;display:inline-block}ul.gallery,li.gallerybox{zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /resources/src/mediawiki.legacy/images/ajax-loader.gif?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ster/resources/src/mediawiki.legacy/images/spinner.gif?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  l:lang(glk) li,ol:lang(kk-arab) li,ol:lang(mzn) li{list-style-type:-moz-persian;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  k-arab) li,ol:lang(mzn) li{list-style-type:-moz-persian;list-style-type:persian}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  rsian;list-style-type:persian}ol:lang(ckb) li{list-style-type:-moz-arabic-indic;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  }ol:lang(ckb) li{list-style-type:-moz-arabic-indic;list-style-type:arabic-indic}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  type:arabic-indic}ol:lang(hi) li,ol:lang(mr) li{list-style-type:-moz-devanagari;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  i) li,ol:lang(mr) li{list-style-type:-moz-devanagari;list-style-type:devanagari}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  tyle-type:devanagari}ol:lang(as) li,ol:lang(bn) li{list-style-type:-moz-bengali;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  lang(as) li,ol:lang(bn) li{list-style-type:-moz-bengali;list-style-type:bengali}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  :-moz-bengali;list-style-type:bengali}ol:lang(or) li{list-style-type:-moz-oriya;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  le-type:bengali}ol:lang(or) li{list-style-type:-moz-oriya;list-style-type:oriya}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  esources/src/mediawiki.legacy/images/help-question.gif?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  es/src/mediawiki.legacy/images/help-question-hover.gif?2014-08-30T22:43:20Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  dits a{unicode-bidi:embed}.mw-jump,#jump-to-nav{overflow:hidden;height:0;zoom:1}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -anchor{font-weight:normal;margin-left:-14px;width:14px;filter:alpha(opacity=0);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  headline-anchor,.mw-body h6:focus .mw-headline-anchor{filter:alpha(opacity=100);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  und-color:#f9f9f9;padding:5px;font-size:95%}#toc,.toc{display:-moz-inline-block;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  %}#toc,.toc{display:-moz-inline-block;display:inline-block;display:table;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  lay:-moz-inline-block;display:inline-block;display:table;zoom:1;*display:inline;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-ltr.svg?2014-11-14T23:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-ltr.svg?2014-11-14T23:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-ltr.svg?2014-11-14T23:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-ltr.svg?2014-11-14T23:33:20Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-rtl.svg?2014-11-14T23:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-rtl.svg?2014-11-14T23:33:20Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  sizing:border-box;box-sizing:border-box;-webkit-appearance:none;*display:inline;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  border-box;box-sizing:border-box;-webkit-appearance:none;*display:inline;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  );border-bottom-color:#cccccc;outline:none}.mw-ui-button:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  none}.mw-ui-button:hover::-moz-focus-inner,.mw-ui-button:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  lor:#2a62cc;outline:none}.mw-ui-button.mw-ui-progressive:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  :hover::-moz-focus-inner,.mw-ui-button.mw-ui-progressive:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  sive:focus::-moz-focus-inner,.mw-ui-button.mw-ui-primary:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  mary:hover::-moz-focus-inner,.mw-ui-button.mw-ui-primary:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  or:#008c6e;outline:none}.mw-ui-button.mw-ui-constructive:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  hover::-moz-focus-inner,.mw-ui-button.mw-ui-constructive:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  lor:#a7170f;outline:none}.mw-ui-button.mw-ui-destructive:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  :hover::-moz-focus-inner,.mw-ui-button.mw-ui-destructive:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: -webkit-transition
+Line 1:
+  ""] + label::before{-webkit-transition:0.2s cubic-bezier(0.175,0.885,0.32,1.275);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: -o-transition
+Line 1:
+  0.175,0.885,0.32,1.275);-o-transition:0.2s cubic-bezier(0.175,0.885,0.32,1.275);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: transition
+Line 1:
+  er(0.175,0.885,0.32,1.275);transition:0.2s cubic-bezier(0.175,0.885,0.32,1.275);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  sources/src/mediawiki.ui/components/images/checked.svg?2014-11-27T01:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  sources/src/mediawiki.ui/components/images/checked.svg?2014-11-27T01:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  rc/mediawiki.ui/components/images/checked_disabled.svg?2014-11-27T01:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  rc/mediawiki.ui/components/images/checked_disabled.svg?2014-11-27T01:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  em;position:relative;z-index:1}.mw-body .mw-indicator{display:-moz-inline-block;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  :1}.mw-body .mw-indicator{display:-moz-inline-block;display:inline-block;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  indicator{display:-moz-inline-block;display:inline-block;zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  .org/static-master/skins/Vector/images/bullet-icon.svg?2015-02-14T02:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-image
+Line 1:
+  AAAAXRSTlMAQObYZgAAABNJREFUCB1jYEABBQw/wLCAgQEAGpIDyT0IVcsAAAAASUVORK5CYII=) \9;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  g/static-master/skins/Vector/images/bullet-icon.png?2014-08-07T15:20:00Z) \9!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/user-icon.svg?2014-12-24T12:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/user-icon.svg?2014-12-24T12:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  .org/static-master/skins/Vector/images/search-fade.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  -placeholder{color:#999}div#simpleSearch #searchInput::-webkit-search-decoration
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  it-search-decoration,div#simpleSearch #searchInput::-webkit-search-cancel-button
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  earch-cancel-button,div#simpleSearch #searchInput::-webkit-search-results-button
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  -results-button,div#simpleSearch #searchInput::-webkit-search-results-decoration
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s.org/static-master/skins/Vector/images/search-ltr.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s.org/static-master/skins/Vector/images/search-ltr.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/tab-break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/tab-break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/tab-normal-fade.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  static-master/skins/Vector/images/tab-current-fade.png?2014-08-07T15:20:00Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/tab-break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/tab-break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/arrow-down-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/arrow-down-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  c-master/skins/Vector/images/arrow-down-focus-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  c-master/skins/Vector/images/arrow-down-focus-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  0;display:block;width:26px;padding-top:3.1em;margin-top:0;margin-top:-0.8em !ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  org/static-master/skins/Vector/images/unwatch-icon.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  org/static-master/skins/Vector/images/unwatch-icon.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s.org/static-master/skins/Vector/images/watch-icon.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s.org/static-master/skins/Vector/images/watch-icon.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/unwatch-icon-hl.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/unwatch-icon-hl.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  rg/static-master/skins/Vector/images/watch-icon-hl.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  rg/static-master/skins/Vector/images/watch-icon-hl.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  atic-master/skins/Vector/images/watch-icon-loading.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  atic-master/skins/Vector/images/watch-icon-loading.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Unrecognized function
+Line 1:
+  -color:#f6f6f6;background-image:-moz-linear-gradient(top,#fff 50%,#f6f6f6 100%);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: background-image
+Line 1:
+  -color:#f6f6f6;background-image:-moz-linear-gradient(top,#fff 50%,#f6f6f6 100%);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Unrecognized function
+Line 1:
+  kground-image:-webkit-gradient(linear,left top,left bottom,color-stop(50%,#fff),
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Unrecognized function
+Line 1:
+  dient(linear,left top,left bottom,color-stop(50%,#fff),color-stop(100%,#f6f6f6))
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Unrecognized function
+Line 1:
+  ient(linear,left top,left bottom,color-stop(50%,#fff),color-stop(100%,#f6f6f6));
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: background-image
+Line 1:
+  ient(linear,left top,left bottom,color-stop(50%,#fff),color-stop(100%,#f6f6f6));
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  org/static-master/skins/Vector/images/portal-break.png?2014-08-07T15:20:00Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -master/skins/Vector/images/external-link-ltr-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -master/skins/Vector/images/external-link-ltr-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: zoom
+Line 2:
+  olor:#FFC0C0;color:black}   .mw-navigation-hint{overflow:hidden;height:0;zoom:1}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 2:
+  kins/Vector/skinStyles/../images/preferences/break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 2:
+  kins/Vector/skinStyles/../images/preferences/break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 2:
+  skins/Vector/skinStyles/../images/preferences/fade.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: unicode-bidi
+Line 4:
+  15px;float:right} .mw-editsection{white-space:nowrap; unicode-bidi:-moz-isolate;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: unicode-bidi
+Line 4:
+  tion{white-space:nowrap; unicode-bidi:-moz-isolate;unicode-bidi:-webkit-isolate;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: unicode-bidi
+Line 4:
+  ap; unicode-bidi:-moz-isolate;unicode-bidi:-webkit-isolate;unicode-bidi:isolate}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 4:
+  ditor/modules/ve-mw/init/styles/images/loading-ltr.gif?2014-09-30T20:46:40Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 8:
+  s/src/jquery.tipsy/images/tipsy.png?2014-04-21T16:58:20Z) no-repeat top left!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+HTML style attribute
+Invalid value for property: zoom
+Line 1:
+  display:inline;margin:0;border:0;padding:1px;width:1px;zoom:1
+  -------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: zoom
+Line 8:
+  ;position:relative;padding-top:15px;padding-bottom:10px; overflow:hidden;zoom:1}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 12:
+  urces/css/../images/cog-sprite.png?2015-01-24T06:23:20Z) no-repeat right top!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 12:
+  anguageSelector/resources/css/../images/cog-sprite.svg?2015-01-24T06:23:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 12:
+  anguageSelector/resources/css/../images/cog-sprite.svg?2015-01-24T06:23:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 4:
+  tificationsPage-ltr.png?2014-09-30T20:35:00Z) no-repeat 20px 15px !important!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 4:
+  y/../icons/Settings.png?2014-09-30T20:35:00Z) no-repeat 20px 15px !important!ie}
+  --------------------------------------------------------------------------------^
+```",1424970486,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"@Tacsipacsi If that happens only the first time when you check a checkbox, then that's possible, since the image will now only be loaded when necessary (previously it was preloaded). Otherwise that should not happen, and I can't reproduce the problem myself (using Opera 12.17 on Windows 7).",1424955729,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"@matmarex: I tried it and it works, but it has a bit (sometimes several seconds) delay. Is it normal? If not, can it be fixed?",1424374555,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"The issue has now been fixed, and the fix will be included in MediaWiki version 1.25wmf19. According to https://www.mediawiki.org/wiki/MediaWiki_1.25/Roadmap, that version will be deployed to Wikipedias on 4 March. You can try out the fix at beta labs (http://en.wikipedia.beta.wmflabs.org/).",1424354295,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"The issue is caused by the combination of the SVG background and the border-radius. One solution can be seen in 2b8f46c6. An other solution is to remove the CSS border completely and draw the border in the SVG instead. I once tested this and it works fine in all browsers including Opera 12.
+
+Personally I'm oscillating between two extremes:
+
+* Don't reinvent the wheel. A checkbox is a checkbox. All CSS hacks (opacity: 0, empty clip regions) to force individual styles on otherwise native form elements are horrible and should have never been invented.
+
+* Opera 12 is dead. It's performance on sites like Twitter is horrible. People should just stop using it. I did.",1416489605,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"(In reply to Bartosz Dziewoński from comment #2)
+> The solution is to stop serving SVG to Opera 12, like Thiemo has figured out
+> and did it for this new checkbox style back when it was part of BetaFeatures
+
+Note that this doesn't even cause the rendering to worsen – while Opera 12 has excellent support for the SVG format itself, it has rather lousy support for SVGs as background-images – if you zoom in, you can see the pixels appear just as if it was a PNG image. (I never tested this on a high DPI screen, but I would expect the effect to be the same.)",1416343322,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"Assuming this is about Opera 12, then this is a Opera bug where SVG background-image sometimes disappears in presence of border-radius and the right phase of the moon. If you restart your browser, you'll probably be able to see the checkmark (for a while).
+
+The solution is to stop serving SVG to Opera 12, like Thiemo has figured out and did it for this new checkbox style back when it was part of BetaFeatures (2b8f46c6dfbbe9a66029820f2b524b3aaf8fcddd). That is, however, currently impossible with the current build and ""shipping"" process of OOUI.
+
+It might also be possible to come up with a magic combination of styles that makes it all work correctly. I couldn't come up with any, but I didn't spend too much time poking at this.",1416343161,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"The problem is that there's no visual difference between the checked and unchecked status of the buttons. I tested and I can use it, but I don't know whether it's in checked or unchecked state. It generated lots of ""warnings"" beside the ""errors"" in the previous comment what I didn't attach to the error report, say if you need it.",1416251839,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+VisualEditor: FlaggablePageView::setPageContent() called incorrectly,"ApiVisualEditorEdit.php:142, $view->setPageContent() should be passing 2 parameters
+
+	public function setPageContent( &$outputDone, &$useParserCache ) {
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1416057420,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-zivj5224uzhg27lsf7rt,task_description,resolved
+VisualEditor: FlaggablePageView::setPageContent() called incorrectly,"Change 173749 merged by jenkins-bot:
+Stop warnings about calling FlaggablePageView::setPageContent with no parameters
+
+https://gerrit.wikimedia.org/r/173749",1416246459,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zivj5224uzhg27lsf7rt,task_subcomment,NA
+VisualEditor: FlaggablePageView::setPageContent() called incorrectly,"Change 173749 had a related patch set uploaded by Alex Monk:
+Stop warnings about calling FlaggablePageView::setPageContent with no parameters
+
+https://gerrit.wikimedia.org/r/173749",1416187758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zivj5224uzhg27lsf7rt,task_subcomment,NA
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,"Inserted table with caption
+
+Steps to reproduce: 
+
+1 VE - Insert a media
+2. In Media Settings box insert a table and add a caption to a table. Click Insert.
+
+The media will be inserted with a table and the table caption will be displayed below the table. The screenshot is attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F15354}",1416001080,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3p6vhaawgb7sqodrhouz,task_description,resolved
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,"Change 264600 merged by jenkins-bot:
+Fix caption-side for tables inside figcaptions
+
+[[https://gerrit.wikimedia.org/r/264600]]",1453061211,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3p6vhaawgb7sqodrhouz,task_subcomment,NA
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,"Change 264600 had a related patch set uploaded (by Esanders):
+Fix caption-side for tables inside figcaptions
+
+[[https://gerrit.wikimedia.org/r/264600]]
+",1453051505,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3p6vhaawgb7sqodrhouz,task_subcomment,NA
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,This is an upstream issue with how Parsoid styles <figcaption>s. This rule is inherited by the table's <caption>.,1452965311,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3p6vhaawgb7sqodrhouz,task_subcomment,NA
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,Found in test2 and beta.,1416002871,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3p6vhaawgb7sqodrhouz,task_subcomment,NA
+VisualEditor: Ctrl-v of text into a pre-formatted area ends up with <br> added to each line,"I was inserting log lines into a preformatted area.  It looked fine on the page, but after saving, there were clearly extra spaces added.  Went into wikitext to remove them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415998020,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-3gb5fng3mdx3cf25e4jj,task_description,invalid
+VisualEditor: Ctrl-v of text into a pre-formatted area ends up with <br> added to each line,"I couldn't reproduce this. It's likely to have been fixed, either by changes in our code or by improvements in the browsers. If you can still reproduce, please reopen, and please add more details (where you're copying from and where you're pasting to, and your browser/OS).",1655736850,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3gb5fng3mdx3cf25e4jj,task_subcomment,NA
+VisualEditor: Ctrl-v of text into a pre-formatted area ends up with <br> added to each line,"There are several issue with copy/paste into pre-formatted area - e.g.https://phabricator.wikimedia.org/T74456.
+Prioritizing for now as low.",1423321723,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3gb5fng3mdx3cf25e4jj,task_subcomment,NA
+VisualEditor: Tables inside references aren't allowed in wikitext (but are in VE and Parsoid),"Tables in References list
+
+Should we allow inserting tables in Basic citation? 
+
+1. VE - insert Cite->Basic 
+
+When inserting Basic citation the dialog box shows all toolbar options in Reference dialog box including tables. 
+
+2. Insert a table from the Reference dialog box for the Basic citation. Type some text in that table. 
+
+The reference list accommodate the table but does not how any table structure - see the attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15121}",1415840100,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ezoyokghacndpxr47zrb,task_description,open
+VisualEditor: Drag-and-drop of a block image into a table slices the table rather than inserting inside the cell,"dragging block images split tables
+
+The bug is split from 72995
+
+Dragging an image and placing the insert cursor outside a table will split the table.
+
+See the at attached screen recording.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15063}",1415813220,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-gygrr56itpwtjglimrdq,task_description,resolved
+VisualEditor: Drag-and-drop of a block image into a table slices the table rather than inserting inside the cell,I think this has been fixed since we introduced block drop targets,1452965061,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gygrr56itpwtjglimrdq,task_subcomment,NA
+VisualEditor: Drag-and-drop of a block image into a table slices the table rather than inserting inside the cell,"It seems that formulae(display:block;) cannot be dragged into a table but are perfectly draggable over the page, including a caption of a table. 
+
+Should we make formulae draggable to tables?",1415903110,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-gygrr56itpwtjglimrdq,task_subcomment,NA
+VisualEditor: Paste from Word to Firefox inserts garbage,"Cut 'n paste from a MS Word document into FF inserts several HTML comments which appear in VE as circled exclamation marks.  Hovering reveals the lengthy MSIE-specific comments.
+
+Note that pasting the same thing into Chrome does not end up with the lengthly comments.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415765760,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-72pzweoqmhairfkznqk6,task_description,declined
+VisualEditor: Paste from Word to Firefox inserts garbage,">>! In T75292#1258930, @nshahquinn-wmf wrote:
+> @MarkAHershberger, just for clarity, could you attach a Word doc which shows this behavior?
+
+Unfortunately closing this Phabricator task as no further information has been provided.
+
+@MarkAHershberger: After you have provided the information asked for and if this still happens, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks!",1590761121,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-72pzweoqmhairfkznqk6,task_subcomment,NA
+VisualEditor: Paste from Word to Firefox inserts garbage,"@MarkAHershberger, just for clarity, could you attach a Word doc which shows this behavior?",1430776412,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-72pzweoqmhairfkznqk6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Not logged in warning
+
+In test2 and in Betalabs a warnings gets displayed ""You are not logged in..."". The page displays a user status as being logged in in the upper right corner.(see the attached screenshot).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14878}",1415667240,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-4aaydfvos3g3vz7sutt6,task_description,open
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Thx, @matmarex for following up!  Yes, presently the issue is reproducible exactly as you described. And yes, before (in 2014) there were no additional warning (popup) before publishing. 
+
+There are several points: 
+(1) The major motivation for filing this bug was that users don't see their status changed (they are displayed as being logged in). When they see the warning and, at the same time, see that they  are still logged-in, what they are supposed to do?  Dismiss the warning and reload the page, then to click to log in  - these are quite non-trivial steps. Also, their editing efforts might be lost (I know that it's not the case, but users might not be so sure). 
+
+Btw, the options in the warning popup before publishing are different for for Suggested edits. A user is given an option to login (makes more sense to me): 
+
+{F41417596}
+
+(2) With temp users the issue described in the task won't be an issue, that's why I still think that this task might be closed. 
+{F41417587}
+
+(3) (out of scope of Editing context) The case when a user's status as being logged in is displayed, but, in fact, a user is logged out is present in different context. The most recent case with UploadWizard process - the warning there is barely noticeable and the logged-in status is still displayed.  
+{F41417610}
+
+",1698776965,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Oh, I see, I didn't read the task very carefully… I agree this is still a problem (although I also agree it's probably uncommon in production).
+
+More practical steps to reproduce (without waiting for login session to expire) are:
+# View a page as a logged-in user
+# In another browser tab, log out
+# In the original browser tab, click ""Edit"" to open VE
+
+{F41417244}
+
+If you continue and try to save your edit, you will get a warning about it when publishing changes, which I think decently explains what's going on: (I'm not sure if we had this back in 2014)
+
+{F41417246}
+
+Maybe VE could detect this situation and show this warning earlier.",1698767278,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,">>! In T75250#9279424, @matmarex wrote:
+> I can't reproduce this today.
+
+Thanks @matmarex for looking into it! The issue is still present in beta (at least) - to reproduce a user needs to be logged in and to wait for a user session expired. I recently ran into this issue on `commons beta`.  It might be that production handles sessions differently and, since there were no complaints, I agree that the issue may be closed for now. ",1698338451,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,I can't reproduce this today.,1698235646,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,Adding screenshots {F54279}{F54277},1425420254,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Re-checked after my user rights were changed to authorized. The captcha  does not appear anymore and the edits are saved. 
+However, the message ""You are not logged...""  still appears - although the page still displays me as logged in.",1423598026,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Since I do not have a way to manipulate session timeouts, we need to wait for timeout to occur naturally...
+
+1. Open VE and wait for an hour-and-half.
+2. Try to edit the page.
+3. In betalabs I receive a captcha in Save dialog box - entering the captcha(s) does not seem to be working.
+4. Switch to Read and then back to Edit - the message ""You are not logged...""  appears.
+
+ 
+Console shows:
+""[Edit] Missing property ""user.id"""" load.php:37
+<anonymous> load.php:37
+mw.trackSubscribe/<() load.php:154
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/self.fireWith() load.php:46
+jQuery.Callbacks/self.fire() load.php:46
+mw.track() load.php:153
+<anonymous> load.php:219
+ve.trackSubscribe/<() load.php:41
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/self.fireWith() load.php:46
+jQuery.Callbacks/self.fire() load.php:46
+ve.track() load.php:41
+ve.init.mw.TargetEvents.prototype.trackSaveError() load.php:215
+oo.EventEmitter.prototype.emit() load.php:58
+ve.init.mw.Target.prototype.onSaveError/<() load.php:197
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/self.fireWith() load.php:46
+.Deferred/</deferred[tuple[0]]() load.php:47
+mw.Api.prototype.ajax/xhr<() load.php:26
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/self.fireWith() load.php:46
+done() load.php:135
+.send/callback()    ",1423529844,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,Cannot reproduce issue.,1415672303,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Inconsistent behavior in Chrome compared to FF, on applying  a link or language annotation to a gallery.","Environment- test2, beta
+
+Just like media files , the gallery also does not take link or any annotations. But the behavior is inconsistent in Chrome when compared to FF.
+
+Tested in Chrome 38 and FF 33.1.
+
+1> In a blank page, insert a Gallery with some caption
+2> Click to highlight the gallery and while it is still highlighted, select to insert link.
+3> In FF, the link inspector opens above the Gallery.
+In Chrome, the link inspector opens and closes in a split second.
+
+The same thing happens when trying to language annotations to a Gallery.
+1> > insert a Gallery with a file name and caption
+2> Click to highlight the gallery and while it is still highlighted, select to apply language.
+3> In FF, the langauge inspector opens below  the Gallery.
+
+In Chrome, the language inspector opens and closes instantly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1415642340,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-rf55v7fmqwvlp6c7uvg6,task_description,open
+"VisualEditor:[Regression wmf7] Inconsistent behavior in Chrome compared to FF, on applying  a link or language annotation to a gallery.",Confirmed  - and as in bug 73226 - an inserted Gallery should be the first element on a page to display the described issue.,1415643472,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-rf55v7fmqwvlp6c7uvg6,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited.
+
+For example, create a page with the following wikitext:
+```
+<gallery>
+>>
+</gallery>
+```
+Example: https://en.wikipedia.org/w/index.php?title=User:Matma_Rex/sandbox&oldid=826934821
+
+This renders as an empty gallery (`<ul class=""gallery mw-gallery-traditional""></ul>`).
+
+In VE, it displays a placeholder, but it seems that it can't be clicked to focus it:
+{F13935446}
+When focussed using arrow keys, it displays a completely mispositioned context menu:
+{F13935448}
+Trying to use the ""Edit"" button causes a JS error in the console:
+```
+TypeError: Cannot read property 'toggleHighlighted' of undefined
+    at VeUiMWGalleryDialog.ve.ui.MWGalleryDialog.onHighlightItem (https://en.wikipedia.org/w/extensions/VisualEditor/modules/ve-mw/ui/dialogs/ve.ui.MWGalleryDialog.js?22058:591:7)
+    at https://en.wikipedia.org/w/extensions/VisualEditor/modules/ve-mw/ui/dialogs/ve.ui.MWGalleryDialog.js?22058:342:13
+    at fire (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3317:31)
+    at Object.add [as done] (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3376:7)
+    at VeUiMWGalleryDialog.<anonymous> (https://en.wikipedia.org/w/extensions/VisualEditor/modules/ve-mw/ui/dialogs/ve.ui.MWGalleryDialog.js?22058:341:9)
+    at https://en.wikipedia.org/w/resources/lib/oojs-ui/oojs-ui-windows.js?f9a29:748:28
+    at mightThrow (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3583:29)
+    at process (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3651:12)
+```",1415641200,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-5m22o74uyj2fr46ck3hv,task_description,resolved
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Change 413253 **merged** by Jforrester:
+[mediawiki/extensions/VisualEditor@master] ve.ce.MWGalleryNode: Ensure we always have a focusable element
+
+[[https://gerrit.wikimedia.org/r/413253]]",1519259604,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Change 413252 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.ui.MWGalleryDialog: Handle galleries with 0 items
+
+[[https://gerrit.wikimedia.org/r/413252]]",1519259491,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Change 413253 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.ce.MWGalleryNode: Ensure we always have a focusable element
+
+[[https://gerrit.wikimedia.org/r/413253]]",1519248599,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Change 413252 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.ui.MWGalleryDialog: Handle galleries with 0 items
+
+[[https://gerrit.wikimedia.org/r/413252]]",1519248598,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"This is not reproducible as originally written, due to changes in the gallery inspector, but a similar issue is still present. I updated the description.",1519245771,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Confirmed. 
+
+In addition to the scenario described abotve: 
+
+If "">>"" is entered  - the gallery will be saved as 
+
+<gallery>
+>>
+</gallery>  
+
+
+If, say, ""caption"", will be surrounded with << and >>, then the inserted Gallery becomes invisible, but in Edit source it will be: 
+
+<gallery>
+<<Caption>>
+</gallery>",1415642531,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,Also found in FF 33.1.,1415641254,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Inserting media, while Gallery inspector is open, makes the cursor active in the main editor","Environment- test2, beta
+
+1> Select to insert a gallery.Type in  some caption in the resulting  dialog.
+2> Click done. 
+3> open the gallery inspector again and while it is open, select Insert -> Media.
+4> After the Media Search dialog opens notice the cursor instead of being active in the dialog's input field , is active in the main editor. See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1415637000,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-qe5zfxyv76gy6qgn6hwf,task_description,resolved
+"VisualEditor:[Regression wmf7] Inserting media, while Gallery inspector is open, makes the cursor active in the main editor",Checked in betalabs and production.,1423522560,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-qe5zfxyv76gy6qgn6hwf,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Inserting media, while Gallery inspector is open, makes the cursor active in the main editor",Confirmed  - an inserted Gallery should be the first element on a page to display tye described behavior with a cursor.,1415639173,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-qe5zfxyv76gy6qgn6hwf,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Inserting media, while Gallery inspector is open, makes the cursor active in the main editor",http://youtu.be/m6BeEEnrKtc . Also found in FF 33.1.,1415637301,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-qe5zfxyv76gy6qgn6hwf,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Uncaught TypeError: Cannot read property 'nodeType' of undefined ,on deleting the content in the Gallery inspector and clicking done","screenshot of JS error
+
+Enviornment- test2, beta
+
+1> Select to insert a gallery. When the inspector opens just type in some text.
+2> Now highlight the gallery and click on the gallery context menu. The gallery inspector opens.
+3> delete the content in the dialog and then press done.Generates JS error Uncaught TypeError: Cannot read property 'nodeType' of undefined in the console.See screenshot.
+
+Same behavior found in FF 33.1. 
+JS error - TypeError: currentNode.children[(nao.offset - 1)] is undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14822}",1415632380,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-w4wbehbgyvkgen7rk24r,task_description,resolved
+"VisualEditor:[Regression wmf7] Uncaught TypeError: Cannot read property 'nodeType' of undefined ,on deleting the content in the Gallery inspector and clicking done",Confirmed -  the error displayed in JS console is exactly as the attached screenshot presents.,1415636725,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-w4wbehbgyvkgen7rk24r,task_subcomment,NA
+VisualEditor: Support discontiguous table selections,"We currently sort of support this is that row/col deletion skips over merged cells, but the user should probably be able to create such a selection themselves. The current canonical form of a table selection is [fromCol,fromRow,toCol,toRow] so this would need to be changed/extended. There are also a lot of places where we assume the selection to be rectangular.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1415623800,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ffnapmr2ezee3boihytc,task_description,open
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,"I dug deeper after filing bug 73201.
+
+1. Type ""abcdef"".
+2. Make ""ab"" italic.
+3. Make ""ef"" italic.
+4. Make ""bcde"" a link.
+
+Result:   ''a[[bcde|b]]''[[bcde|cd''e'']]''f''
+Expected: ''a''[[bcde|''b''cd''e'']]''f''
+
+The result doesn't seem to depend on the order of operations here.
+
+VisualEditor should avoid splitting link annotations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415553420,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_description,duplicate
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,Do we need to file a task which requests that?,1436721864,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_subcomment,NA
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,Note that this remains the case even post {T105239} as Parsoid's `scrubWikitext` model doesn't aggressively merge links ahead of other styles.,1436552315,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_subcomment,NA
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,This is essentially also a duplicate of bug 50098; marking as a subsidiary though in case there are specific concerns.,1415618286,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_subcomment,NA
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,"(In reply to Bartosz Dziewoński from comment #0)
+> 3. Make ""ef"" italic.
+
+Actually, you can skip this step, and still get the ""split link"" effect.",1415553626,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_subcomment,NA
+VisualEditor: Tables Caption - moving a cursor with keyboard forces a cursor to the begininng of the page,"1. Open a page in VE and insert a table with a caption. Make sure that you have some chunk of text above the inserted table or a block of some content, so the page needs to be scrolled down to the table.
+
+2. Place a cursor in the table caption and press the right arrow on a keyboard to navigate to the end of the caption. Press one more time - the page scrolls up and the cursor is placed at the beginning of the page. 
+
+Note: moving a cursor with the left arrow to the beginning of the caption and pressing it one more time will simply place it at the last character of a previous sentence.",1415228580,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-n4z3dix5blkhrgq34wbj,task_description,resolved
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","This task is about [VisualEditor](https://www.mediawiki.org/wiki/VisualEditor). See its [user guide](https://www.mediawiki.org/w/index.php?title=Help:VisualEditor/User_guide) for general information.
+
+In the VisualEditor, click the ≡ icon, click ""Options"", and choose ""Page Settings"".
+If someone puts an invalid page name / page title in the ""Target page for [redirection](https://www.mediawiki.org/wiki/Help:Redirects)"" field (like the page name ""Talk:"" or a page name with a pipe character `|` in it), and tries to apply the changes, an exception is caused and the editor is locked up. 
+
+The ""Apply Changes"" button should be disabled when the input is not valid (like in e.g. the ""Insert ➙ Media"" dialog when file dimensions are invalid). 
+
+You are expected to provide a patch in Wikimedia Gerrit. See https://www.mediawiki.org/wiki/Gerrit/Tutorial for how to set up Git and Gerrit.",1415132640,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_description,resolved
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","Change 470914 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Blocked apply if redirect address is invalid
+
+[[https://gerrit.wikimedia.org/r/470914]]",1541110624,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","Change 470914 had a related patch set uploaded (by Flutterish; owner: Flutterish):
+[mediawiki/extensions/VisualEditor@master] Blocked apply if redirect address is invalid
+
+[[https://gerrit.wikimedia.org/r/470914]]",1541021017,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",https://codein.withgoogle.com/tasks/5265052258009088/,1540301191,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",I would like to mentor this task in #Google-Code-in-2018.,1540269636,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","This is still a problem. Typing in an invalid page title (e.g. ""A<B"") and trying to apply the changes causes an exception and locks up the editor. The button should be disabled when the inputs are not valid (like in e.g. the media dialog when file dimensions are invalid).",1540269625,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",">>! In T74971#1486465, @Krenair wrote:
+> Right now it shows the red outline around the textbox when you try to do this. Do we want to block it from saving somehow? Show a warning and automatically set it back to the previous value?
+
+Sounds good.",1442345069,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",Right now it shows the red outline around the textbox when you try to do this. Do we want to block it from saving somehow? Show a warning and automatically set it back to the previous value?,1438035786,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","So I looked into the code - MWTitleInputWidget (used for redirects and templates) vs. MWLinkTargetInputWidget (links)
+I think a lot of the request/response handling code in MWLinkTargetInputWidget should probably be shared, it shows a lot of things in the result like title validity ('legality'), existence of the exact query, external links, exact matches, etc.",1421805281,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","I was testing with characters like <>, pipes, etc.
+
+```#REDIRECT [[Talk:]]```
+
+comes up for ""Talk:"", but gets rendered as a numbered list element with a broken link by the MW parser.",1421804635,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",```#REDIRECT [[MediaWiki:Badtitletext]]```,1421804505,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again","Betalabs
+
+The down arrow to bring up the context menu for Categories is not center aligned.
+
+Compare the screenshots from Betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14800}",1415128320,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_description,resolved
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again",Verified the fix in production,1415834628,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again",Verified the fix in test2,1415227775,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again",Verified the fix in Betalabs,1415218436,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again","Change 171165 merged by jenkins-bot:
+Fix indicator alignment in MWCategoryItemWidget
+
+https://gerrit.wikimedia.org/r/171165",1415149290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again","Change 171165 had a related patch set uploaded by Catrope:
+Fix indicator alignment in MWCategoryItemWidget
+
+https://gerrit.wikimedia.org/r/171165",1415148810,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again","Created attachment 17015
+test2
+
+**Attached**: {F14802}",1415128414,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Environment- production, beta
+
+1> Cite -> Basic. Type a name in the “Use this Group”. Type some text in the sub-editor to make the insert button active and click to insert.
+2> Cite -> Re Use. Select the Reference from the list.
+3> Notice a label shows up with General References and the Group name momentarily, before the reference gets inserted to the main editor. See the screencast(pause it at 0.07).
+
+In beta, it appears on the top-left corner of the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1415027160,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-27d4zngimys4mtw4fiz5,task_description,resolved
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","I can't reproduce this today, I think it has been genuinely fixed at some point in the past 8 years. The interface now looks completely different from the video.",1664897272,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Created attachment 17173
+screen recording
+
+**Attached**: {F15375}",1416431756,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","The bug exists in beta, test, and production. I've attached the screenrecording - it shows the issue somewhat slower than in the previous attachment.",1416430169,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","It turned out that Chrome displays the issue even better than FF. So, better see it there.",1416429768,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Elena, so it does not appear in Betalabs?",1416429502,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Re-tested it  - the bug still exists in test2 and production. The best way to reproduce it 
+
+- use FF
+- when inserting a Basic citation do not use General references- type some other name there",1416429381,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Yes, I saw it again in test2 - it's still not 100% reproducible. 
+
+Now for Re-use references in test2, I got
+Uncaught TypeError: Cannot read property 'length' of undefined VM1516:174ve.ui.MWReferenceDialog.useReference VM1516:174ve.ui.MWReferenceDialog.onSearchSelect VM1516:172oo.EventEmitter.emit VM1507:6ve.ui.MWReferenceSearchWidget.onResultsSelect VM1516:158oo.EventEmitter.emit VM1507:6OO.ui.SelectWidget.selectItem VM1507:147OO.ui.SelectWidget.chooseItem VM1507:148OO.ui.SelectWidget.onMouseUp",1415817517,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Reopen this issue.Steps to reproduce are the same as above.
+
+See screencast at http://youtu.be/bhaPQLNC4ZU(pause it at 0.05).",1415724673,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",Verified in test2.,1415233257,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","It looks as the issue is gone  - checked it in betalabs on Safari, FF, Chrome, and IE11.",1415127115,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",Provisionally marking as such.,1415054660,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",I think I might have fixed this in https://gerrit.wikimedia.org/r/170784 (which is the fix for bug 72783).,1415054360,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",Difficult to reproduce - I caught it once in betalabs Chrome. Maybe it related to network connectivity?,1415054312,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",Difficult to reproduce - I caught it once in betalabs Chrome. Maybe it related to network connectivity?,1415054284,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",http://youtu.be/a8rgrcU7Bns,1415027383,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor:  References inside galleries being displayed separately, inside the gallery, instead of in the correct <references /> block at the end of the page","Open a page containing some refs, and then a gallery that contains <ref> tags but no <references /> block inside the gallery.  (The references block can be elsewhere on the page.)  For example:
+```
+==Section==
+Hello world.<ref>First footnote</ref>
+
+==Gallery==
+<gallery>
+File:Example.jpg|An image<ref>A footnote for the image</ref>
+</gallery>
+
+==References==
+<references />
+```
+
+In read mode, everything looks right:
+
+> Section
+> Hello world.[1]
+> 
+> Gallery
+> An image[2]
+> 
+> References
+> 1. ^ First footnote
+> 2. ^ A footnote for the image
+
+In VisualEditor, you get this:
+
+> Section
+> Hello world.[1]
+> 
+> Gallery
+> An image[1]
+> 1. ^ A footnote for the image
+> 
+>References
+> 1. ^ First footnote
+
+{F15268}
+
+VisualEditor seems to be inserting a ref block into the gallery, even though none exists at that point on the page.  Also, it restarts the numbers for the gallery.",1414858200,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-afkiouif3sgwwazwgdpk,task_description,duplicate
+"VisualEditor:  References inside galleries being displayed separately, inside the gallery, instead of in the correct <references /> block at the end of the page","Reproducible in Parsoid:
+```
+$ echo -e ""<gallery>\nFile:foo.jpg|A <ref group=""n"">ref one</ref>\n</gallery>"" | node parse
+…
+<ul class=""gallery mw-gallery-traditional"" typeof=""mw:Extension/gallery"" data-mw='{""name"":""gallery"",""attrs"":{},""body"":{""extsrc"":""\nFile:foo.jpg|A &lt;ref group=n>ref one&lt;/ref>\n""}}' data-parsoid='{""dsr"":[0,62,2,2]}' about=""#mwt3"">
+<li class=""gallerybox"" style=""width: 155px"">
+<div style=""width: 155px"">
+<div class=""thumb"" style=""width: 150px;"">
+<div style=""margin:35.5px auto;""><a href=""/wiki/File:Foo.jpg"" class=""image""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/120px-Foo.jpg"" width=""120"" height=""79"" srcset=""//upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/180px-Foo.jpg 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/240px-Foo.jpg 2x"" data-file-width=""300"" data-file-height=""197""/></a></div>
+</div>
+<div class=""gallerytext"">
+<p>A <sup id=""cite_ref-1"" class=""reference""><a href=""#cite_note-1""><span>[</span>n 1<span>]</span></a></sup></p>
+</div>
+</div>
+</li>
+</ul><span about=""#mwt3"">
+</span><p about=""#mwt3""><br/>
+<strong class=""error mw-ext-cite-error"">Cite error: There are <code>&lt;ref group=n></code> tags on this page, but the references will not show without a <code>{{reflist|group=n}}</code> template (see the <a href=""/wiki/Help:Cite_errors/Cite_error_group_refs_without_references"" title=""Help:Cite errors/Cite error group refs without references"">help page</a>).</strong>
+<link rel=""mw:PageProp/Category"" href=""./Category:Pages_with_missing_references_list#Main%20Page""/></p>
+```
+
+Could this be caused by using the <gallery>'s contents as a whole page, thus confusing Cite.php?
+",1427117290,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-afkiouif3sgwwazwgdpk,task_subcomment,NA
+"VisualEditor:  References inside galleries being displayed separately, inside the gallery, instead of in the correct <references /> block at the end of the page",Blocked by T49344?,1421377783,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-afkiouif3sgwwazwgdpk,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,"Screenshot
+
+Steps to reproduce
+
+1.Insert a table
+2.Insert a caption ""text2""
+3.Make the caption a bullet point to create a slug above it
+4.Now add some other text in that slug ""text1""
+5.Save the page
+
+Observed Result:
+The order of ""text1"" and ""text2"" gets reversed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15176}",1414786140,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-64flnckmn275gswhshoe,task_description,resolved
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,This looks like it is fixed either in #visualeditor in some way or due to Remex. I followed the steps in the video as best as possible with the current VE design and the text appeared in the expected locations.,1534452609,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,"As mentioned in [[ https://phabricator.wikimedia.org/T76100 | T76100 ]], this was fixed in 2015, in tidy-html5.",1505777544,PHID-USER-vscvrah3yt5mw4fhroiz,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,Re-tested and confirmed that this still happens (unsurprisingly).,1469839886,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,Apparently this is a bug with HTMLTidy.,1415203267,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,"Still works on my local machine.
+
+The wikitext produced is:
+{|
+|+
+Foo
+* Bar
+!-
+|
+|}
+
+which looks problematic but locally renders fine as
+
+<table><caption>Foo<ul><li>bar...
+
+but on production and betalabs renders as
+
+<ul><li>bar</li></ul><table><caption>Foo...",1415202452,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,"Created attachment 17004
+video capture
+
+Still reproducible, see the video capture
+
+**Attached**: {F15177}",1415045853,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,Works for me in Chrome & FF.,1415024615,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+Tables - adding formatted headings  to <visualeditor-table-caption> displays Uncaught TypeError,"1. In VE highlight any portion of an inserted table and add <visualeditor-table-caption>.  
+
+2. Without typing any text in the caption, select any format for headings format - Uncaught TypeError will be displayed.
+
+Uncaught TypeError: Cannot read property 'nodeType' of undefined VM8471:495ve.ce.Document.getNodeAndOffset VM8471:495ve.ce.Surface.focus VM8471:538ve.ui.FormatAction.convert VM8471:661ve.ui.Surface.execute VM8471:629ve.ui.Command.execute VM8471:645ve.ui.Tool.onSelect VM8471:638OO.ui.ToolGroup.onPointerUp VM8471:66OO.ui.PopupToolGroup.onPointerUp VM8471:91jQuery.event.dispatch load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141030T0…:65elemData.handle 
+
+3. Attempt to delete the added caption displays: 
+
+Uncaught Error: Unbalanced set of replace operations found (program):321ve.dm.TransactionProcessor.processors.replace (program):321ve.dm.TransactionProcessor.executeOperation (program):314ve.dm.TransactionProcessor.process (program):314ve.dm.Document.commit (program):390ve.dm.Surface.changeInternal (program):366ve.dm.Surface.change (program):365ve.dm.SurfaceFragment.change (program):370ve.dm.SurfaceFragment.delete (program):380ve.ce.Surface.handleLinearDelete (program):578ve.ce.Surface.onDocumentKeyDown (program):546ve.EventSequencer.callListener (program):257ve.EventSequencer.onEvent (program):254(anonymous function) (program):252jQuery.event.dispatch load.php:65elemData.handle
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414771500,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-7jjbl4wy6ynwsfmld2oj,task_description,resolved
+Tables - adding formatted headings  to <visualeditor-table-caption> displays Uncaught TypeError,Verified the fix in production.,1416435285,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-7jjbl4wy6ynwsfmld2oj,task_subcomment,NA
+Tables - adding formatted headings  to <visualeditor-table-caption> displays Uncaught TypeError,Verified the fix in test2.,1415909982,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-7jjbl4wy6ynwsfmld2oj,task_subcomment,NA
+Tables - adding formatted headings  to <visualeditor-table-caption> displays Uncaught TypeError,Fixed in master.,1415883590,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7jjbl4wy6ynwsfmld2oj,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page woth VE
+2.Add a basic reference
+3.Re -use that reference
+4.Open the reference dialog for the re-used reference
+5.Open the dropdown for the Use this group comb box 
+
+Observed Result:
+Cannot see any groups names there as its getting cut off
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15043}",1414701900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nkev4xvcykpxkczstis2,task_description,resolved
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box",Verified the fix in production,1415835051,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nkev4xvcykpxkczstis2,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box",Verified the fix in Betalabs and test2,1415061470,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nkev4xvcykpxkczstis2,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box","**gerritadmin** wrote:
+
+Change 170176 merged by jenkins-bot:
+Add forgotten $overlay pass-through in MWReferenceDialog
+
+https://gerrit.wikimedia.org/r/170176",1414796058,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nkev4xvcykpxkczstis2,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box","**gerritadmin** wrote:
+
+Change 170176 had a related patch set uploaded by Catrope:
+Add forgotten $overlay pass-through in MWReferenceDialog
+
+https://gerrit.wikimedia.org/r/170176",1414705857,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nkev4xvcykpxkczstis2,task_subcomment,NA
+VisualEditor: No indication in the toolbar what text styles are active because they're in a menu,"screenshot
+
+Screenshot show my cursor within a string of bold text. However the toolbar menu button doesn't change to indicate that text-formatting is currently active. 
+
+This is particularly a problem if I place my cursor at the *end* of a string of bold/formatted text, as I cannot know at-a-glance, whether the text I'm about to type will come out formatted in some way.
+
+In many other programs/sites (eg. gmail, gdoc), there is always an onscreen indicator (usually the button appears ""pressed""), which helps me understand whether text-formatting is active or not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14998}",1414695900,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-kcaluu7rsxygp57ew5gr,task_description,open
+VisualEditor: No indication in the toolbar what text styles are active because they're in a menu,"The button also appears pressed in VisualEditor, it's just that it's pushed down to a sub-menu so it's not obvious. This is the same as e.g. Google Mail's editing interface, but it can be a bit perplexing, yes.",1414773893,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kcaluu7rsxygp57ew5gr,task_subcomment,NA
+"VisualEditor: Switching out the image clears the ""link"" parameter","Steps to reproduce:
+* Went to my user page, mw:User:Adamw .
+* Clicked ""Edit"" to use the VisualEditor.
+* Clicked the thumbnail at the top, to edit.
+* Clicked the image title to open the editor dialog.
+* Clicked ""Choose a different image"".
+* Pasted the name of an image into the search field, and selected my image.
+* Apply changes.
+* Save chages to page.
+
+This all seemed to go swimmingly, until I looked at the diff:
+
+https://www.mediawiki.org/w/index.php?title=User%3AAdamw&diff=1246151&oldid=1041988
+
+The ""link"" parameter is missing.
+
+Client system: Linux, FF 32.0.3
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1414657080,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-bxani2nv3phs5oyyziql,task_description,open
+"VisualEditor: Switching out the image clears the ""link"" parameter","(In reply to Adam Wight from comment #1)
+> I gave it a second try, and went to add the missing parameter with VE.  It
+> was not supported anywhere...
+
+Indeed. This is an exceptionally rare piece of wikitext we don't support yet.",1414692926,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bxani2nv3phs5oyyziql,task_subcomment,NA
+"VisualEditor: Switching out the image clears the ""link"" parameter","I gave it a second try, and went to add the missing parameter with VE.  It was not supported anywhere...",1414657229,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-bxani2nv3phs5oyyziql,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations","Environment- test2, beta, production
+
+1> insert an external link to a blank page. Number generated for this link is “1”.
+2> hit enter a couple of times, to move the cursor down
+3> Click to insert media ,in the media settings dialog enter  the same external link in the caption sub-editor.Click to insert.
+4> notice the auto-numbers generated beside the external links.Number generated for the link in media is “2”.
+5> Save the page. And notice that the media file external link’s auto-number has now changed to #1 and the external link in the page is #2.
+
+See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1414507740,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-lecf6oguwzmplvfamo26,task_description,open
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations","This feels like we should fix this in MediaWiki rather than in VisualEditor. Alternatively, we could just wait for Parsoid HTML for read mode to come along, which fixes this that way instead. Meh.",1415055839,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations",Confirmed in betalabs - the steps to reproduce the bug are exactly as described by Ritu.,1414802758,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations","Created attachment 16928
+Numbers change after saving the document
+
+**Attached**: {F15282}",1414508298,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations","Created attachment 16927
+Auto numbers generated before saving the page.
+
+**Attached**: {F15281}",1414508236,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations",See screenshots.,1414508161,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+Editing has become awfully slow,"Timing response editing at enwiki
+
+The save operation has become very slow lately, and it seems to have accelerated this month, possibly in the middle of this month (October).
+
+I did a test edit and the first POST request with submit action took 20562 ms, aka the ""save"". The later GET request on the page took 12627 ms. Some users report edit delays in the order of a minute or more.
+
+This is on a 75Mbps symmetric fiber line, using HTTPS, with Firefox browser on Ubuntu 14.10. Other users have experienced this problem on other platforms and browsers, and both when they are logged in and not logged in.
+
+Preferences for my part is pretty standard, I can make an export if necessary, but as this is reported from several users editing at several sites I don't think this has anything to do with preferences.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Whiteboard**: aklapper-moreinfo
+
+**Attached**: {F15172}",1414441560,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-p67up43jsphy5tblzmnk,task_description,declined
+Editing has become awfully slow,"No reply from @jeblad. :(
+
+Hence closing as declined.",1426776217,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,@jeblad: Still an issue?,1424082908,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,"This is very worrisome and I should not have let it slip my attention. @jeblad, what is the current status?",1422000181,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,Hmm. Would be good to know if that happened again.,1416222248,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,"This is about 1-2 weeks prior to the bug. It seems like the response time is back to normal now. A POST after an edit is 7.853 s and the following GET is 5.381 s. Slow but not awfully slow.
+
+I tested this (both now and the previous report) with classic editing, I don't know how the other users were editing.
+
+Last edit on [[w:no:Bagn]].[1] Previous edit on [[w:en:Norway]].[2]
+
+I suspect some heavy background processing slowed the system to a crawl, and it is now done.
+
+[1] https://no.wikipedia.org/w/index.php?title=Bagn&diff=13509266&oldid=13254424
+[2] https://en.wikipedia.org/w/index.php?title=Norway&diff=631363149&oldid=631261705",1415693274,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,"Sorry for the late response.
+
+(In reply to jeblad from comment #0)
+> reported from several users editing at several sites
+
+Any links? Which timeframe is this about?
+
+Does this only refer to ""classic"" editing or VisualEditor or both?",1415195320,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,"For a discussion at nowiki, see https://no.wikipedia.org/w/index.php?title=Wikipedia:Tinget&oldid=13483198#Hva_er_det_som_skjer_her_.3F.3F.3F.3F",1414441827,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+"VisualEditor:[Regression wmf5] Inserting a Link target after a text,instead gets added in between the typed text.","Environment- beta, test2,production
+
+1>In a blank page in VE,type in some text in paragraph format.
+2>Enter a space and select to insert a link. Type in some text in the link input box and keep the inspector open.
+3>Now while the inspector is open, click on to add a bullet/numbered list.
+4>Notice the list gets added and deleted quickly and the link target gets inserted in between the text(right before the last character of the previously typed text). See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1414422900,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3ptsttym6kp4s3cf6ppu,task_description,resolved
+"VisualEditor:[Regression wmf5] Inserting a Link target after a text,instead gets added in between the typed text.",This seems to have been fixed.,1508929909,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-3ptsttym6kp4s3cf6ppu,task_subcomment,NA
+"VisualEditor:[Regression wmf5] Inserting a Link target after a text,instead gets added in between the typed text.","Confirmed in test2 - it happens for sure, but not quite noticeable. It's somewhat more noticeable in FF than in Chrome.",1415057606,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3ptsttym6kp4s3cf6ppu,task_subcomment,NA
+"VisualEditor:[Regression wmf5] Inserting a Link target after a text,instead gets added in between the typed text.",http://youtu.be/RwVvvlI9rcI,1414423053,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3ptsttym6kp4s3cf6ppu,task_subcomment,NA
+VisualEditor: Don't allow whitespace-only comments to be inserted,"screenshot of the comment popup
+
+Environment- test2,beta,production
+
+1> In VE, select to insert a comment.
+2> When the dialog opens just enter space in the text area and click Done.
+3> Notice the comment popup’s appearance (appears to be smaller, than the regular size).See screenshot.
+4> Click on the popup. Notice the Edit comment box's textarea is empty  with no space taken up for the whitespace characters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15118}",1414421400,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-nosrxhvqlznucmrj62x4,task_description,resolved
+VisualEditor: Don't allow whitespace-only comments to be inserted,"Change 205567 merged by jenkins-bot:
+ve.ui.WhitespacePreservingTextInputWidget: Trim whitespace in input
+
+[[https://gerrit.wikimedia.org/r/205567]]",1429663674,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nosrxhvqlznucmrj62x4,task_subcomment,NA
+VisualEditor: Don't allow whitespace-only comments to be inserted,"Change 205567 had a related patch set uploaded (by Bartosz Dziewoński):
+ve.ui.WhitespacePreservingTextInputWidget: Trim whitespace in input
+
+[[https://gerrit.wikimedia.org/r/205567]]
+",1429610641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nosrxhvqlznucmrj62x4,task_subcomment,NA
+VisualEditor: Don't allow whitespace-only comments to be inserted,"Confirmed - a Comment with white spaces can be saved. Generally
+
+- it is not possible to create an empty comment
+- if all text is deleted from the comment - it cannot be saved
+- leading and trailing white spaces are not preserved upon saving 
+
+If you re-open the saved Comment with white spaces and click Done - the comment will be recognized as an empty comment and deleted.",1415058127,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-nosrxhvqlznucmrj62x4,task_subcomment,NA
+Escape brackets in URLs of new/changed links,"It would be nice if the VisualEditor dialogs were able to escape (percent-encode) URLs as this one in a way that makes them work in wikitext.
+
+Currently it fails to do so both when changing an existing URL https://it.wikipedia.org/w/index.php?title=PAGEPress_Publications&diff=68792069&oldid=68792024 and when adding it from scratch. I had to manually use urlencode: as usual in wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: http://doaj.org/search?source={%22query%22:{%22filtered%22:{%22query%22:{%22query_string%22:{%22query%22:%22Italy%22,%22default_operator%22:%22AND%22}},%22filter%22:{%22bool%22:{%22must%22:[{%22term%22:{%22_type%22:%22journal%22}},{%22term%22:{%22index.publisher.exact%22:%22PAGEPress%20Publications%22}}]}}}}}",1414071720,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-4z3rc5r4dabblz4yjn64,task_description,open
+Escape brackets in URLs of new/changed links,"> I am not sure what Parsoid should do here.
+
+Nor do I. :) The VisualEditor dialog should percent-encode URLs (feature request); whether such an operation involves Parsoid I don't know.",1425571434,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-4z3rc5r4dabblz4yjn64,task_subcomment,NA
+Escape brackets in URLs of new/changed links,"I am not sure what Parsoid should do here. When given a string that is a parameter to a transclusion, Parsoid doesn't know that the string happens to be a uri.
+
+Parsoid does handle escapable characters in links correctly where it is clear that the entire string is a url (as below).
+
+[subbu@earth lib] echo '<a rel=""mw:ExtLink"" href=""http://foo.bar?q=[foo]&s=[bar]"">baz</a>' | node parse --html2wt
+[http://foo.bar?q=&#x5B;foo&#x5D;&s=&#x5B;bar&#x5D; baz]
+
+Am I missing something?",1422988055,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-4z3rc5r4dabblz4yjn64,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Type a text
+3.Apply a link on the text
+4.Reopen the link inspector for it
+
+Observed Result:
+The link suggestions are appearing in a broken way .See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15372}",1414017480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fkh5and23bnoi3f25rdh,task_description,resolved
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,I cannot reproduce this on my mobile device.,1429569157,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,"In an actual mobile device,it appears broken for a split second, then again gets back to normal after that.",1415220722,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,"Created attachment 17044
+broken in FF
+
+It is still appearing broken in Firefox
+
+**Attached**: {F15373}",1415219884,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,Appears to now be fixed having tested with an iPad against Beta Labs.,1415147816,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,Cannot reproduce.,1415068539,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+"VisualEditor: Banish the TOC and section edit link controls from the main page settings page, and show the display title one instead","Fram says that the ""Page settings"" item should be the three items most commonly wanted by encyclopedia article editors:
+
+* redirect
+* disambiguate
+* displaytitle
+
+and that all the other options should be ""Advanced settings"" (or not displayed at all as described in {T74396}).
+",1414016400,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-dggw3rzo3qdyf7wa5for,task_description,open
+"VisualEditor: Banish the TOC and section edit link controls from the main page settings page, and show the display title one instead","(In reply to WhatamIdoing from comment #0)
+> Fram says that the ""Page settings"" item should be the three items most
+> commonly wanted by encyclopedia article editors:
+> 
+> * redirect
+> * disambiguate
+> * displaytitle
+
+Where's the data to prove this prioritisation is accurate? (That's not to say the current list is good, but it's based on the MediaWiki manuals for ""simple"" controls.)
+
+(I've re-written the title to make it an actual ask.)",1414016788,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dggw3rzo3qdyf7wa5for,task_subcomment,NA
+VisualEditor: Provide a way to configure per-wiki which meta dialog items are available for each namespace,"Under ""Advanced settings"" in the Page options menu, there are two items:
+
+  ""Let this page be indexed by search engines""
+
+and
+
+  ""Show a tab on this page to add a new section"" 
+
+that should never be changed for Wikipedia articles.  (This will differ for other projects; both of these might be appropriate at Meta, for example.)
+
+Could these options be hidden at projects where they should not be used?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414016220,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-kt5s3xm5kkxkenmgo25a,task_description,open
+VisualEditor: Provide a way to configure per-wiki which meta dialog items are available for each namespace,"Do-able. Hard and messy, but do-able.",1414016548,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kt5s3xm5kkxkenmgo25a,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"Environment- beta.
+
+1> In VE, insert a comment. Click done.
+2> click to undo while the comment is still highlighted. Notice the label on the Comment  first changes to read “Comment” from the actual comment text, before removing it. See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413903900,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_description,resolved
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,Verified the fix in test2.,1416440487,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,Verified the fix in beta.,1416348293,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"**gerritadmin** wrote:
+
+Change 173808 merged by jenkins-bot:
+Make changes to comment node before apply staging stack
+
+https://gerrit.wikimedia.org/r/173808",1416248155,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"**gerritadmin** wrote:
+
+Change 173808 had a related patch set uploaded by Esanders:
+Make changes to comment node before apply staging stack
+
+https://gerrit.wikimedia.org/r/173808",1416231589,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"(In reply to Alex Monk from comment #3)
+> This seems to be because the first undo you make only clears the comment
+> -text- change. The second undo actually removes the comment node itself.
+> This makes sense since you make the comment node and it goes in the document
+> first, then later insert some text into it.
+> ContextItemWidget#getDescription falls back to the tool's title if the text
+> was falsey (so, an empty string), which is why you see 'Comment' rather than
+> an empty box. This also seems reasonable.
+> 
+> We should probably be removing an empty comment node from the document if
+> it's left there due to undo... Currently this only appears to be done if you
+> have an open comment inspector with no text and then click outside it (see
+> CommentInspector#getTeardownProcess).
+
+This sounds like it was caused by Ed's ""staging empty comment node"" change. That code should ensure that the creation of the comment node and setting the value are one entry in the undo stack.",1414015326,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"This seems to be because the first undo you make only clears the comment -text- change. The second undo actually removes the comment node itself. This makes sense since you make the comment node and it goes in the document first, then later insert some text into it.
+ContextItemWidget#getDescription falls back to the tool's title if the text was falsey (so, an empty string), which is why you see 'Comment' rather than an empty box. This also seems reasonable.
+
+We should probably be removing an empty comment node from the document if it's left there due to undo... Currently this only appears to be done if you have an open comment inspector with no text and then click outside it (see CommentInspector#getTeardownProcess).",1414014355,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,Confirmed in Beta(test2 and production do not have that issue).,1413915756,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,http://youtu.be/ws3ObsyZijc,1413904190,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf4] Language context menu appears outside the Content Editor,"Language context menu appearing outside the editor
+
+Environment-test2, beta
+
+1> Insert some Language in RTL direction.
+2> insert a comment in the language text, right before the last word. Notice the word moves to the start of line.
+3> Now place the cursor at the end of the last char in the langauge text, notice the language context menu appears outside the editor on the top left of page.See screenshot.
+
+It happens only when the cursor is at the last character.
+
+Refer bug 71320 screencast, in case the above steps sound confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15040}",1413828000,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-33nc2htx3qd2h333vhm6,task_description,resolved
+VisualEditor: [Regression wmf4] Language context menu appears outside the Content Editor,Fixed by Ed.,1414003086,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-33nc2htx3qd2h333vhm6,task_subcomment,NA
+VisualEditor: [Regression wmf4] Language context menu appears outside the Content Editor,Confirmed test2 and Betalabs on Chrome.,1413835085,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-33nc2htx3qd2h333vhm6,task_subcomment,NA
+VisualEditor: Create a meta dialog panel for setting page status indicators,"Not quite sure how this will work (and how it will know which ones are available), but this would probably be rather useful.
+
+https://www.mediawiki.org/wiki/Help:Page_status_indicators is no longer blank. :-)
+",1413586320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u5halrjaknddtmd56on4,task_description,open
+VisualEditor: Create a meta dialog panel for setting page status indicators,"PSI's can contain arbitrary wikitext so ideally their contents would be editable in a SurfaceWidget, however I suspect in most situations they will be transcluded onto the page and therefore not editable at all.",1415402400,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-u5halrjaknddtmd56on4,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Advanced media dialog is shown with horizontal scrollbars because button labels don't fit.
+
+{F15974499}",1413560700,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-44vu7zrafitz5rmbpcac,task_description,resolved
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,That'll do it.,1523287949,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Change 422138 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.ui.MWMediaDialog: Use dropdown for image type selector
+
+[[https://gerrit.wikimedia.org/r/422138]]",1522926143,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Change 422138 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.ui.MWMediaDialog: Use dropdown for image type selector
+
+[[https://gerrit.wikimedia.org/r/422138]]",1522154486,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Reciting myself from T190462:
+> No regression to my knowledge. We once discussed a compromise as solution in T112982 with Ed being against the proposal. We'd need a constructive idea…
+I was hoping for inputs by @Esanders – if spilling one button on next line seems insufficient, how about calculating the available horizontal size and putting all of them underneath each other when above?
+",1522112167,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Finally, this has also become a problem in English.",1522107799,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"This is still a problem with the new dialog and the new design, I updated the screenshot.",1422093725,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Well, given that we're replacing this dialog with a new design which will be wider (as we'll have now drawer), and it's only in the ""advanced"" section, it's maybe not worth worrying for now? Eh.",1413563517,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,Not really.,1413563107,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,Can we improve the translations?,1413562188,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"Un-used function. Clean-up is good. Etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413498240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tp7hcgumrrewgducy7rw,task_description,resolved
+VisualEditor: Remove ve.bind(),"**gerritadmin** wrote:
+
+Change 171002 merged by jenkins-bot:
+[BREAKING CHANGE] Remove the ve.bind function
+
+https://gerrit.wikimedia.org/r/171002",1415909089,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"**gerritadmin** wrote:
+
+Change 171002 had a related patch set uploaded by Jforrester:
+[BREAKING CHANGE] Remove the ve.bind function
+
+https://gerrit.wikimedia.org/r/171002",1415128593,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"**gerritadmin** wrote:
+
+Change 169644 merged by jenkins-bot:
+Remove more references to ve.bind
+
+https://gerrit.wikimedia.org/r/169644",1414703073,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"**gerritadmin** wrote:
+
+Change 169644 had a related patch set uploaded by Alex Monk:
+Remove more references to ve.bind
+
+https://gerrit.wikimedia.org/r/169644",1414547161,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"<James_F> Krinkle: Thoughts on actually removing ve.bind rather than just removing its use?
+<Krinkle> James_F: Not just yet. Maybe in 1-2 weeks time?
+<James_F> Krinkle: For whom do you think we should wait?
+<Krinkle> James_F: documentation, community, etc.
+<James_F> Krinkle: Eh.
+<Krinkle> James_F: We may not have a public API yet, but that doesn't mean it's cool to break stuff without at least giving them the chance to fix is.
+<Krinkle> random google search: https://www.mediawiki.org/wiki/VisualEditor/Adding_instrumentation_how-to
+
+resolved later",1413500943,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Screenshot
+
+Steps to reproduce:
+
+1.Open any page with VE in Betalabs using Firefox
+2.Go to Insert>Media
+3.Search for any image and select it to add it in the page
+
+
+Observed Result:
+The image gets added to the page but in the console there is an error:
+
+Image corrupt or truncated: http://upload.wikimedia.org/wikipedia/commons/1/1b/Ko_BuWe.jpg
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15306}",1413421680,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-di2oqisjl4wdsto2nyxu,task_description,resolved
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Deeming as resolved, then.",1418946432,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs",I haven't seen it recently.,1415644575,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs",Rummana/Elena: Have either of you seen this issue recently?,1415643712,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","(In reply to James Forrester from comment #15)
+> Did we decide to declare this a ""ghost in the machine"" and move on?
+
+If Roan didn't notice the cause in the above debug, I'm not sure who ask to look deeper. It seems the wrong request is being made, right?",1414511160,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Did we decide to declare this a ""ghost in the machine"" and move on?",1414448349,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","After additional investigation with Roan.
+
+Revised steps to reproduce:
+ 
+1. In test2 in FF - make sure that you just switched fro Read mode to Edit, or just refresh the browser window.
+
+2. Insert - Media, type 'artist'(without quotes) to display search results.
+
+3. In Console panel you'll see: 
+
+Image corrupt or truncated: https://upload.wikimedia.org/wikipedia/commons/d/db/Artist_drive.JPG
+
+
+In Network panel you'll see that instead of a thumbnail img - 112x149 and https://upload.wikimedia.org/wikipedia/commons/thumb/d/db/Artist_drive.JPG/112px-Artist_drive.JPG, 
+
+the request was made for for 1536x2048 img and
+GET  https://upload.wikimedia.org/wikipedia/commons/d/db/Artist_drive.JPG
+
+The Staus code: 206(not always).
+
+Request/Response headers:
+
+Request headers:
+Host: upload.wikimedia.org
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0
+Accept: image/png,image/*;q=0.8,*/*;q=0.5
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate
+Referer: https://test2.wikipedia.org/w/index.php?title=ET_page&redirect=no&veaction=edit
+Cookie: GeoIP=US:San_Francisco:37.7898:-122.3942:v4
+Connection: keep-alive
+
+Response headers: 
+Accept-Ranges:""bytes""
+Access-Control-Allow-Origin:""*""
+Access-Control-Expose-Headers:""Age, Date, Content-Length, X-Content-Duration, X-Cache, X-Varnish""
+Age:""1652""
+Connection:""keep-alive""
+Content-Length:""2115604""
+Content-Range:""bytes 32419-2148022/2148023""
+Content-Type:""image/jpeg""
+Date:""Thu, 23 Oct 2014 23:43:46 GMT""
+Etag:""6eaae0b7e042739bd4a04e686eab8dea""
+Last-Modified:""Mon, 07 Oct 2013 01:54:56 GMT""
+Server:""nginx/1.1.19""
+Via:""1.1 varnish, 1.1 varnish""
+X-Cache:""cp1048 hit (2), cp1048 frontend miss (0)""
+X-Object-Meta-Sha1base36:""8x65i07x23pfu6j7h8yl33asimaupwx""
+X-Object-Meta-Sha1base36:""8x65i07x23pfu6j7h8yl33asimaupwx""
+X-Timestamp:""1381110895.66655""
+X-Trans-Id:""txc9084137ff28405983d9c-0054498c3f""
+X-Varnish:""431922781 428031845, 3387585776""
+
+
+If you attempt to insert again the same image -  Request URL will be correct:
+https://upload.wikimedia.org/wikipedia/commons/thumb/d/db/Artist_drive.JPG/112px-Artist_drive.JPG",1414178459,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","As far I could see, there were no errors in header request/response. However, 
+
+there is one small thing(may be nothing): 
+
+Image corrupt or truncated: https://upload.wikimedia.org/wikipedia/commons/3/37/African_Bush_Elephant.jpg African_Bush_Elephant.jpg
+
+
+<img class=""ve-ce-focusableNode-highlight-relocatable-marker"" src=""data:image/gif;base64,R0lGODlh…EKAAEALAAAAAABAAEAAAICTAEAOw==""></img>
+
+And the issue still is not reproducible 100% of the time.",1413845423,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Can you look into the contents of the HTTP response (in the Firebug network tab, or a network analysis tool like Fiddler) and check if the content is damaged somehow?",1413833054,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","(In reply to etonkovidova from comment #10)
+> The issue was reproduced in test2.
+
+Which confirms this is not a ""Beta Cluster stability"" issue.",1413829866,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs",The issue was reproduced in test2.,1413829787,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs",I was able to reproduce the bug in FF 33. Look at the attached screenshot:  Screen Shot 2014-10-20 at 11.06.46 AM,1413829275,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Created attachment 16823
+error message for inserted picture
+
+**Attached**: {F15309}",1413828863,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","The two images mentioned in the FF console in the screenshots:
+https://commons.wikimedia.org/wiki/File:Ko_BuWe.jpg
+https://commons.wikimedia.org/wiki/File:Zwaardstootplaat-Rijksmuseum_AK-MAK-1056.jpeg
+
+The first file was loaded directly from Commons, the other from beta Commons.
+
+I don't see why this would be a MediaViewer issue. (Was its appearence somehow correlated with using MediaViewer? MV can cause some oddities on Beta because it sometimes tries to preload thumbnails before they exist, and the resulting 404 gets cached - but this error is not related to that in any way I can see.) Some ideas:
+
+- some sort of local issue? Happens deterministically, but no one else could reproduce...
+- could be an actual image loading error: Firefox seems to emit this error if it fetches the content for an image file and it turns out not to be a valid image. Maybe the file gets truncated somehow (there were a lot of HTTP errors on beta after the HHVM switch, see e.g. bug 72162 - based on Rummana's screenshot, the file is not necessarily served by beta though, so such an error seems unlikely)
+- https://bugzilla.mozilla.org/show_bug.cgi?id=941823 mentions FF errors with large files - the ones mentioned in the bug are in the 100MP range though, while the two files in the screenshots are 10MP
+- there are claims that FF throws this error if you change the src of an image before it is fully loaded (e.g. http://stackoverflow.com/questions/11928878/detect-image-corrupt-or-truncated-in-firefox )
+
+All in all, I would close this as worksforme if no one can reproduce and there are no reports of this happening in the wild.",1413824009,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","From Gergo: https://bugzilla.mozilla.org/show_bug.cgi?id=646090
+
+So, some image is corrupt (or just has had it's file extension changed, which is considered ""corrupt""). Neither Mark H nor Gergo can repro. Rummana is the only person who can right now, right?
+
+Rummana: can you repro with a clean Firefox profile?",1413822680,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","I also can't reproduce this problem (MediaViewer issue?) in Chrome, Safari or Firefox? The error as state would be from the MW media fetching/thumbnailing API it sounds like?",1413569866,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","See also: http://stackoverflow.com/questions/11727219/image-corrupt-or-truncated-in-firefox
+
+This probably isn't a Beta Cluster problem(?) so I'm moving to VE (feel free to move to where ever it really needs to be) on the assumption its a problem in the code (and I don't want it to not be addressed because it's 'hidden' in the Beta Cluster component).",1413501060,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Created attachment 16792
+Screenshot
+
+Hey Greg! I just added the following image in the same page you used, and got the error:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/0.7358261884200304#mediaviewer/File:Zwaardstootplaat-Rijksmuseum_AK-MAK-1056.jpeg
+
+**Attached**: {F15308}",1413497307,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Created attachment 16790
+Console log in Iceweasel 32.0.3
+
+I can't repro in Iceweasel 32.0.3. I've attached my console log with other warnings though :)
+
+Done on http://en.wikipedia.beta.wmflabs.org/wiki/0.7358261884200304
+
+**Attached**: {F15307}",1413494861,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","I don't see any such error in the Firefox 32 browser console when inserting the ""Ko_BuWe"" image in VisualEditor on http://en.wikipedia.beta.wmflabs.org.
+
+Also, why is this under ""MediaWiki General""?",1413459610,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Open any citation dialog like Cite>Website/book
+
+Observed Result:
+The fields inside Citations dialog are appearing at a much smaller size
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15293}",1413419940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6hvnj3pserezpnqsws3j,task_description,resolved
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,Verified the fix in production,1415835088,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"Created attachment 16987
+Screenshot
+
+Is it okay if the width appears this way in tablet?
+
+**Attached**: {F15295}",1414793420,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,It's not meant to. This is wide enough for tablets and phones.,1414793146,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"Created attachment 16986
+Screenshot
+
+Its still not taking full width .Reopening it.
+
+**Attached**: {F15294}",1414792710,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"confirmed in betalabs. 
+
+Previously it was: 
+oo-ui-textInputWidget {
+	.	
width: 20em;
+}
+
+
+After the fix: 
+.oo-ui-textInputWidget {
+
+	.	
width: 100%;
+	.	
max-width: 50em;
+
+}",1414713131,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"**gerritadmin** wrote:
+
+Change 169968 merged by jenkins-bot:
+Set input/menu widgets to have a max-width expanding to 100% rather than hard-coded
+
+https://gerrit.wikimedia.org/r/169968",1414627725,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"**gerritadmin** wrote:
+
+Change 169968 had a related patch set uploaded by Jforrester:
+Set input/menu widgets to have a max-width expanding to 100% rather than hard-coded
+
+https://gerrit.wikimedia.org/r/169968",1414627517,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"This is almost certainly because of the MediaWiki theme; maybe that now actually sets fields' default width, and the previous theme wasn't?",1413817229,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+Collaborative spelling dictionary building tool,"* Originally proposed at at https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_9#Collaborative_spelling_dictionary_building_tool
+* Currently ongoing work: https://www.mediawiki.org/wiki/Collaborative_spelling_dictionary/Progress
+
+There are extensive spelling dictionaries for the major languages of the world: English, Italian, French and some others; at various degrees of coverage, Mozilla has over a hundred, LibreOffice dozens. They help make Wikipedia articles in these languages more readable and professional and provide an opportunity for participation in improving spelling. Many other languages, however, don’t have spelling dictionaries. One possible way to build good spelling dictionaries would be to employ crowdsourcing, and Wikipedia editors can be a good source for this, but this approach will also require a robust system in which language experts will be able to manage the submissions: accept, reject, filter and build new versions of the spelling dictionary upon them. This can be done as a MediaWiki extension integrated with VisualEditor, and possibly use Wikidata as a backend.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413107460,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_description,open
+Collaborative spelling dictionary building tool,"(In reply to Quim Gil from comment #4)
+> There is a question that as far as I can see hasn't been answered:
+> 
+> > How would such a thing interact with the wiktionary community. Would it
+> > harvest data from them or be a sub project somehow, or is it planned to be
+> > entirely separate?
+> 
+> https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079022.html
+
+In the initial phase of development, the project will aim at making a spelling dictionary for VE. Once this has been achieved, it can then be integrated into Wiktionary later on. 
+This way, it won't remain totally independent of the Wiktionary community forever, rather, it shall aim at improving and increasing the span of the same.",1415377547,PHID-USER-vktcpyhhgydpo36f44uz,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+Collaborative spelling dictionary building tool,"There is a question that as far as I can see hasn't been answered:
+
+> How would such a thing interact with the wiktionary community. Would it
+> harvest data from them or be a sub project somehow, or is it planned to be
+> entirely separate?
+
+https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079022.html",1415292669,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+Collaborative spelling dictionary building tool,"(In reply to Daniel Naber from comment #2)
+> I'm not sure, but http://www.dicollecte.org/home.php?prj=fr might do
+> something similar. It should probably be evaluated before starting this
+> project.
+
+This is something very similar to what the project aims to accomplish, just that dicollecte is specific to French. The project takes this up as a challenge (that only the most popular languages have a solid base of spelling dictionaries) and aims to establish spelling dictionaries for lesser popular languages as well.",1414524987,PHID-USER-vktcpyhhgydpo36f44uz,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+Collaborative spelling dictionary building tool,"**misc2006** wrote:
+
+I'm not sure, but http://www.dicollecte.org/home.php?prj=fr might do something similar. It should probably be evaluated before starting this project.",1414334292,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+Collaborative spelling dictionary building tool,"Hello everyone!
+
+I read through this project idea and am interested in working on this. 
+Presently what I understand is that the project requires an admin panel to be built such that the suggestions that come through crowdsourcing can be verified by the administrator. This panel will be ready with rights like approving, rejecting, filtering to be given to the administrator so as to ensure only valid words/spellings to be accepted.
+
+Please correct me if I'm wrong.
+
+Also, it would be great if I could be redirected to some bugs that might help me better understand this project.
+
+Thanks!",1413110409,PHID-USER-vktcpyhhgydpo36f44uz,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+VisualEditor: Some file permissions are causing lintian warnings,"Dear Sir or Madam,
+
+0) Context
+
+DEB packages of `mediawiki' and many of its extensions, are prepared as part of the WP-MIRROR project (see <https://www.mediawiki.org/wiki/Wp-mirror>). 
+
+1) Lintian
+
+During the build process, `lintian' performs a great number of sanity checks, including seeing if each file has file permissions appropriate to its file type.
+
+When `lintian' sees a non-executable file with 755 permissions, rather than 644, `lintian' will throw a warning like:
+
+W: wp-mirror-mediawiki-extensions: executable-not-elf-or-script usr/share/wp-mirror-mediawiki/extensions/VisualEditor/modules/ve-mw/ui/styles/images/broken-image.png
+
+2) Files which should have permissions set to 644
+
+VisualEditor/modules/ve-mw/tests/browser/Gemfile
+VisualEditor/modules/ve-mw/ui/widgets/ve.ui.MWMediaResultWidget.js
+VisualEditor/modules/ve-mw/ui/widgets/ve.ui.MWMediaSearchWidget.js
+
+3) Technical details
+
+DEB standards version: 3.9.6
+GIT branch: wmf/1.24wmf22
+
+Sincerely Yours,
+Kent
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1413006660,PHID-USER-k3cyvvb2psrntxfcuyyr,PHID-TASK-ch2annsbdighe2sljgvb,task_description,resolved
+VisualEditor: Some file permissions are causing lintian warnings,"Change 166275 merged by jenkins-bot:
+Sort out some odd file permissions
+
+https://gerrit.wikimedia.org/r/166275",1413081041,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ch2annsbdighe2sljgvb,task_subcomment,NA
+VisualEditor: Some file permissions are causing lintian warnings,"Change 166275 had a related patch set uploaded by Alex Monk:
+Sort out some odd file permissions
+
+https://gerrit.wikimedia.org/r/166275",1413079320,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ch2annsbdighe2sljgvb,task_subcomment,NA
+VisualEditor: Some file permissions are causing lintian warnings,"https://bugzilla.wikimedia.org/show_bug.cgi?id=71928 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71930 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71931 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71932 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71933 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71934 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71935 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71936 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71937 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71938 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71939 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71940 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71941 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71942 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71943 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71944",1413070450,PHID-USER-nzp74jejkvrdzynpcb2o,PHID-TASK-ch2annsbdighe2sljgvb,task_subcomment,NA
+"VisualEditor: Add an ""open"" button for link nodes too","I'm editing, and I see a plain, unlabeled, auto-numbered link to an external website.  It says ""[2]"".  I can't open that link without exiting VisualEditor.  The link dialog has an option to ""Add label"" but not ""Open link"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412902140,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-7yvphvp4wfoejotflqgu,task_description,resolved
+"VisualEditor: Add an ""open"" button for link nodes too","**gerritadmin** wrote:
+
+Change 168007 merged by jenkins-bot:
+MWLinkNodeInspector: Provide an open button here too
+
+https://gerrit.wikimedia.org/r/168007",1413947057,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7yvphvp4wfoejotflqgu,task_subcomment,NA
+"VisualEditor: Add an ""open"" button for link nodes too","**gerritadmin** wrote:
+
+Change 168007 had a related patch set uploaded by Jforrester:
+MWLinkNodeInspector: Provide an open button here too
+
+https://gerrit.wikimedia.org/r/168007",1413938165,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7yvphvp4wfoejotflqgu,task_subcomment,NA
+Support PDF export on private wikis,"mwlib is able to fetch credentials to access content on private wikis, though with some issues.
+
+* http://web.archive.org/web/20110800000000/http://code.pediapress.com/wiki/ticket/747
+** Credentials not used to fetch license page 
+** new – ralf – normal – major – 23 months
+** Needs someone with a private wiki able to set $wgCollectionLicenseURL for testing; not relevant for OCG?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412805660,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-25wimjgt4tsdfufivzhc,task_description,declined
+Support PDF export on private wikis,The [Offline Content Generator](https://www.mediawiki.org/wiki/Offline_content_generator) (OCG) software is dead.,1611522574,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"As already announced in [[ https://meta.wikimedia.org/wiki/Tech/News/2017/37 | Tech News ]], OfflineContentGenerator (OCG) will not be used anymore after October 1st, 2017 on Wikimedia sites. OCG will be replaced by Electron. [[ https://www.mediawiki.org/wiki/Special:MyLanguage/Reading/Web/PDF_Functionality | You can read more on mediawiki.org. ]]",1505380686,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"(In reply to C. Scott Ananian from comment #3)
+> Is the concrete feature request here that we support HTTP authentication
+> (basic? digest?) when contacting the wiki's api.php endpoint?
+
+It depends on what we're asking from the API: are we asking anything that requires read privileges?",1414516085,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"Is the concrete feature request here that we support HTTP authentication (basic? digest?) when contacting the wiki's api.php endpoint?
+
+Have you tried using the 'http://username:password@host/...' format when configuring the API endpoint URL?",1414514286,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"(In reply to C. Scott Ananian from comment #1)
+> This should work, using the instructions for setting up Parsoid to point at
+> a private wiki: 
+
+Nice. But doesn't OCG also contact the web API?",1412831954,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"This should work, using the instructions for setting up Parsoid to point at a private wiki: 
+https://www.mediawiki.org/wiki/Parsoid/Setup#Configuration
+https://www.mediawiki.org/wiki/Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis
+
+This could stand to be tested and documented better.",1412806048,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"translate syntax in VE
+
+Translated text should probably not display with syntax in VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14987}",1412653560,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-ddqlzrwdgysvh766ik7s,task_description,resolved
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"As described, this doesn't happen any more. VE + Translate still sucks, but that isn't not this ticket.",1608232349,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"(In reply to James Forrester from comment #4)
+> No, it means the ghastly mess that is {{TNTNTNTNTTNT}} :-)
+
+The screnshot seems to be about this excerpt:
+
+<translate>
+<!--T:21-->
+More details at {{ll|Social media|Social media}}.
+</translate>
+
+{{ll}} only creates a link to Special:MyLanguage (which is not even in Translate now). (In the Translate docs we recommend to use Special:MyLanguage directly, but what can you do.)
+So the summary currently mentions the only thing which is not in the screenshot. :)",1414866828,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"No, it means the ghastly mess that is {{TNTNTNTNTTNT}} :-)",1412812126,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"I assume you mean translate tags as shown in the screenshot, because ""translate templates"" don't exist.",1412750511,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"Yeah, the Translate extension fundamentally doesn't work with VisualEditor in its current form, as I understand it. Much sadness.",1412716773,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,see https://www.mediawiki.org/wiki/Communication?veaction=edit,1412653611,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Allow in-line editing/suggesting/flagging of TemplateData when labels are unclear,"unclear fields in an infobox template
+
+some labels are not clear, or have not been given ""human readable"" aliases, providing a way for end users to flag these, or even submit suggestions or edit them directly could help clean these up quickly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14733}",1412370540,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-frzymdkyeby2og65igsx,task_description,declined
+VisualEditor: Allow in-line editing/suggesting/flagging of TemplateData when labels are unclear,"Closing this to clean up our boards. Not to decline the idea. This is still a possibility. But this ticket is very old and probably not very helpful, even when someone attempts to implement this. The dialog looks very different now and usually displays an easy to follow link to the template where the documentation can be edited.",1654869001,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-frzymdkyeby2og65igsx,task_subcomment,NA
+VisualEditor: Allow in-line editing/suggesting/flagging of TemplateData when labels are unclear,"This could get very tricky, but could be useful.",1412376526,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-frzymdkyeby2og65igsx,task_subcomment,NA
+"VisualEditor Mobile: Does not load at all on IE 11 (unknown dependency ""ext.visualEditor.iehacks"")","VisualEditor Mobile does not load at all on IE 11 right now (unknown dependency ""ext.visualEditor.iehacks"", gets stuck displaying the loading spinner).
+
+Either the module needs mobile target, or we need to stop trying to load it on mobile.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412367420,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-j7ic5u4qfl3yfcnkaw35,task_description,resolved
+"VisualEditor Mobile: Does not load at all on IE 11 (unknown dependency ""ext.visualEditor.iehacks"")","**gerritadmin** wrote:
+
+Change 164649 merged by jenkins-bot:
+Add mobile target to 'ext.visualEditor.iehacks' module
+
+https://gerrit.wikimedia.org/r/164649",1412380482,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-j7ic5u4qfl3yfcnkaw35,task_subcomment,NA
+"VisualEditor Mobile: Does not load at all on IE 11 (unknown dependency ""ext.visualEditor.iehacks"")","**gerritadmin** wrote:
+
+Change 164649 had a related patch set uploaded by Bartosz Dziewoński:
+Add mobile target to 'ext.visualEditor.iehacks' module
+
+https://gerrit.wikimedia.org/r/164649",1412367777,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-j7ic5u4qfl3yfcnkaw35,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"CommentInspector doesn't update its size when the textarea gets resized, only if it's closed and reopened. Split off from bug 71310.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1412021640,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_description,resolved
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"**gerritadmin** wrote:
+
+Change 163674 merged by jenkins-bot:
+ve.ui.CommentInspector: Update size when the textarea gets resized
+
+https://gerrit.wikimedia.org/r/163674",1412817094,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,Spoke too soon.,1412116117,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"**gerritadmin** wrote:
+
+Change 163738 merged by jenkins-bot:
+WindowManager: Emit 'resize' event when a window is resized
+
+https://gerrit.wikimedia.org/r/163738",1412115751,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"**gerritadmin** wrote:
+
+Change 163738 had a related patch set uploaded by Bartosz Dziewoński:
+WindowManager: Emit 'resize' event when a window is resized
+
+https://gerrit.wikimedia.org/r/163738",1412027038,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"**gerritadmin** wrote:
+
+Change 163674 had a related patch set uploaded by Bartosz Dziewoński:
+[WIP] ve.ui.CommentInspector: Update size when the textarea gets resized
+
+https://gerrit.wikimedia.org/r/163674",1412023540,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","When one creates a redirect without filling an edit summary, MediaWiki automatically uses an edit summary to identify that the edit created a redirect. That's very useful. But the autosummary doesn't work if the user fills the edit summary. It also doesn't work when the user edits a redirected page to make it a normal page, by removing the #REDIRECT syntax.
+
+Redirections are very special edits that would be good to have them tagged for review on recent changes and watchlists.
+
+With AbuseFilter one could write some tricky filters to tag those edits, but that's far from ideal.
+
+My proposal is to have at least 2 new tags:
+* One to tag when a redirect is created
+* One when a redirect is removed (not by page deletion, but by removing the #REDIRECT)
+
+It would be nice to also have a tag for when a redirect target is changed (pointing the redirect to another article) and also when a redirect is edited without changing the redirect (like for example adding a category, a comment, or simply content that won't be viewed anyway).
+
+A slight limitation of tags (as I understand) is that they won't display the redirect target as the autosummary does, but that's not important, I think. The autosummary would do the job when present.",1411573320,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-sei7okmjt6zw6r54dwus,task_description,resolved
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 194458 abandoned by Krinkle:
+Implement redirect-related and other tags in mediawiki core
+
+Reason:
+Closing for now due to inactivity and to clear review dashboards. The associated ticket appears to have been resolved without this commit.
+
+Feel free to re-open at any time.
+
+[[https://gerrit.wikimedia.org/r/194458]]",1535313488,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 390224 merged by jenkins-bot:
+[mediawiki/core@master] Add new core tags
+
+[[https://gerrit.wikimedia.org/r/390224]]
+",1512067410,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 390224 had a related patch set uploaded (by Catrope; owner: Petar.petkovic):
+[mediawiki/core@master] Add new core tags
+
+[[https://gerrit.wikimedia.org/r/390224]]
+",1511896667,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 311683 abandoned by Cenarium:
+Implement redirect-related and other tags in mediawiki core
+
+Reason:
+I ended up removing the dependencies directly in I2e48bd458fc8d7c289f04dc276f9287516e0b987 so I have only one commit to maintain.
+
+[[https://gerrit.wikimedia.org/r/311683]]",1474575790,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 211497 had a related patch set uploaded (by Cenarium):
+Implement redirect-related and other tags in mediawiki core
+
+[[https://gerrit.wikimedia.org/r/211497]]
+",1474574411,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 311683 had a related patch set uploaded (by Cenarium):
+Implement redirect-related and other tags in mediawiki core
+
+[[https://gerrit.wikimedia.org/r/311683]]
+",1474371254,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1640971, @daniel wrote:
+> what's the status of this? Can we get the patches merged?
+> Hm, seems to be a long chain...
+Lots of dependencies indeed...
+For automated tags, we need a user-friendly drop down menu instead of an input box (since internal tag names are in english and obtuse, e.g. core-move-crossnamespace). It's 211497.
+For the dropdown menu, we need to overhaul the caching so that a list of tags can be efficiently fetched. It's 218265.
+Before overhauling the caching, we need to make several related performance improvements. It's 201905.
+218777 is not essential to this (I might put it in another branch).
+
+>>! In T73236#1641141, @TTO wrote:
+> @daniel, if you have time, Cenarium and I would really appreciate a second opinion on some of these patches, particularly 201905. Anomie is too busy, and I personally have some doubts about `ChangeTagsContext` and would like someone's else's point of view.
+Yes, I would appreciate reviews.
+I've created `ChangeTagsContext` so that the `ChangeTag` class can't be provided with arbitrary hitcounts or tag definitions, in a way that doesn't require unnecessary duplications when multiple `ChangeTag` instances are involved.",1442338021,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@daniel, if you have time, Cenarium and I would really appreciate a second opinion on some of these patches, particularly 201905. Anomie is too busy, and I personally have some doubts about `ChangeTagsContext` and would like someone's else's point of view.",1442319875,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","*bump*
+what's the status of this? Can we get the patches merged?
+
+Hm, seems to be a long chain...
+* https://gerrit.wikimedia.org/r/#/c/194458/
+* https://gerrit.wikimedia.org/r/#/c/211497/7
+* https://gerrit.wikimedia.org/r/#/c/218265/4
+* https://gerrit.wikimedia.org/r/#/c/218777/3
+* https://gerrit.wikimedia.org/r/#/c/201905/28
+",1442312657,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","ArchCom approves: this seems pretty uncontroversial. We have added some reviewers to the patch. If the review doesn't go forward, let us know.",1434573574,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","[[ https://gerrit.wikimedia.org/r/#/c/194458/ | Change 194458 ]] pretty well does what's requested on this bug, so I'd say it could be closed once it's merged",1433445861,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@Cenarium, @Ciencia_Al_Poder: do you think it would be useful to have a discussion on IRC about this soon? Or would you say the patch sets you mentioned would be sufficient to close this? Is there anything more to discuss?",1433368988,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Did anyone work on this task at #wikimedia-hackathon-2015? If do, please share an update. If not, remove the label.",1433137363,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@daniel
+I dunno what you intend to discuss, but FYI the patch set in https://gerrit.wikimedia.org/r/194458 when combined with https://gerrit.wikimedia.org/r/#/c/190656/ allows to resolve T92621, and when also combined with https://gerrit.wikimedia.org/r/#/c/211656/, allows to resolve T14363 as well (from recent changes, not from new pages where performance issues make this impossible IMO).
+",1432521189,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",See {T92621},1432156301,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1283464, @daniel wrote:
+> @Cenarium, @Ciencia_Al_Poder: We (the ArchCom) thinks it may be nice to discuss this RFC at the hackathon in Lyon. Will you be attending?
+
+Me neither",1431629884,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1283464, @daniel wrote:
+> @Cenarium, @Ciencia_Al_Poder: We (the ArchCom) thinks it may be nice to discuss this RFC at the hackathon in Lyon. Will you be attending?
+
+No I won't be attending. What is it in particular that you want to discuss ?",1431624111,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@Cenarium, @Ciencia_Al_Poder: We (the ArchCom) thinks it may be nice to discuss this RFC at the hackathon in Lyon. Will you be attending?",1431550556,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",@Cenarium: We (the ArchCom) thinks it may be nice to discuss this RFC at the hackathon in Lyon. Will you be attending?,1431550512,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","> Should we deactivate the feature by default in mediawiki core ?
+
+Yes.
+
+> (And enable it on WMF wikis.)
+
+That requires a separate discussion IMHO.",1431409004,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1272896, @Nemo_bis wrote:
+> Do we have statistics on how many (non-Wikimedia) wikis consider cross-namespace redirects to be a problem?
+
+I don't think so.
+
+Should we deactivate the feature by default in mediawiki core ?
+(And enable it on WMF wikis.)",1431110020,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",Do we have statistics on how many (non-Wikimedia) wikis consider cross-namespace redirects to be a problem?,1431108703,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@daniel I haven't implemented any of the controversial aspects.
+
+The first one being the ability to activate / deactivate these tags directly from Special:Tags, which would require a database change. So we don't need a RFC on this at the moment, but we might revisit this issue if it turns out after implementation that there are requests from the wiki communities for such a feature.
+
+The second one is how to handle these tags for display in a drop down menu. I've given up the controversial idea of having a localizable tag name, instead having a separate message for it which can also be used to prevent the tag from appearing in the drop down menu. I haven't had feedback yet on this proposed solution so I can't say if a RFC might be needed, but I don't see which alternatives we have.",1431100816,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@Cenarium do you think this should be an RFC? See https://www.mediawiki.org/wiki/Requests_for_comment/Process for the process. If not, feel free to remove the @MediaWiki-RfCs tag.",1430339538,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Assigning to RFC queue, since I think the ArchCom should have a look at this.",1430323269,PHID-USER-5dqihbanu3caaj7pigif,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 194458 had a related patch set uploaded (by Cenarium):
+Core-defined automatically added tags
+
+[[https://gerrit.wikimedia.org/r/194458]]
+",1428219966,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I've uploaded a patch set for T91535.
+
+Concerning this request, while I still think we should always endeavor to allow as much onwiki customization as possible, I plan on uploading a patch set that simply uses a config variable as originally suggested by TTO.",1428177574,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Okay, let's get back to what is being requested here and in many other places, and most importantly //why// it is requested. The //only// reason this feature is requested is, ultimately, the constraints imposed by the condition limit of the abuse filter. If no such restriction existed, every one of these tags would already exist as global or local filters. But since the restriction exist, and for good reason, this can't happen.
+
+Log-only and tag-only filters are always the ones that get sacrificed first; it has been like that since the introduction of AbuseFilter, see [[https://en.wikipedia.org/wiki/Wikipedia_talk:Edit_filter/Archive_3#Filter_Reduction|this June 2009 discussion]], and is [[https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Edit_filter&oldid=649616762#Condition_limit|just as true today as it was back then]] (the same holds on other wikis and even more for global filters). There's no change in sight, even if the condition limit can be legitimately criticized, some kind of limit must still exist.
+
+Pretty much all of the potential autotags were added by now deleted abuse filters : [[https://en.wikipedia.org/wiki/Special:AbuseFilter/8|self-redirects]], [[https://en.wikipedia.org/wiki/Special:AbuseFilter/27|making/changing redirects]], [[https://en.wikipedia.org/wiki/Special:AbuseFilter/27|replacing content]], and so on. These can be easily inserted from mediawiki core, most of these edits already create automatic edit summaries. I was even thinking we may want to merge autosummaries and autotags in a single function, since the special casing is very similar.
+
+What end users need is to have these easy autotags defined in core, so that abuse filters can focus instead on more complex tagging or other actions (warn, prevent edits). Therefore, this feature request amounts to a core-implemented tag-only AbuseFilter. The customization aspect is integral to AbuseFilter, and so it should be integral to this feature request. We should start from a level of customization that exactly matches the level of customization afforded by AbuseFilter, and narrow it down only when truly necessary for the implementation.
+
+Now with regard to extensions, I wasn't mentioning visual editor at random here, as I said we had to create filters to keep track of visual editor bugs, see [[https://en.wikipedia.org/wiki/Special:AbuseFilter/577|AF 577]], enabled for months, which, however silly that might look, checked for insertions of ♙, ☃ or ↵, so not exactly adding the letter ""A"" or ""B"", but close ! Same problems occurred with wikilove and other extensions. These filters aren't cheap, extensions should rather make these debugging tags on their end. Some wikis may also want more involved autotags than those defined in core. So I wanted to let this possibility open for future implementation (so we don't tie our hands).
+
+I was thinking of a hook that takes the same params as the autotags function and alters the autotags. If we had a config variable, the extension could add the extra tags to it and let end users do the activation/deactivation. Without it, the extension needs to provide a way for users to make the activation/deactivation. This means a user interface, so more work on the extension's side, when it can be done at Special:Tags. That being said, I'll keep this for later and only focus on core-defined tags for now. So basically the list of tags is hard-coded at ChangeTags.php instead of being provided as a config variable.",1425582205,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1089637, @Legoktm wrote:
+> I haven't followed all of the discussion here, but the patch seems drastically overcomplicated from what we need, which is a way for core to define tags (and then apply them). I would recommend just having a static function which returns core provided tags, similar to the one for extensions.
+That one is already implemented in ContentHandler (I'll need to update it).
+> I don't think there's a solid usecase for being able to disable core provided tags, so we can probably leave that out of the initial implementation.
+I agree it isn't essential to allow un-defining the autotags in the initial implementation, so I'll ditch the config variable, which is by far the most complicated aspect. Users and extensions will thus be unable to unset core tags, or only for the later though a hook that we might implement later on, if needed.
+
+>>! In T73236#1090941, @TTO wrote:
+> I like the idea of namespacing the tags. It's not currently done by most extensions, but it would be a good precedent to set. For example, `mw-redirected` or `mw-redirect-removed`. As I said, users should never have to interact with these names, except in the first column of Special:Tags and when using the API.
+I'm just pointing out here that the solution of parsing the tag description for display may be quite remote and more complex than it seems, we would need to rewrite tag filtering, abuse filter's handling of tags and many other things. What can we do in the mean time ? We shouldn't force users to use English text or arcane internal ids in order to filter recent changes. This effectively means that for many users in English language wikis and most users in other language wikis, those tags are completely useless everywhere except when accessed directly from Special:Tags. Note that localization wouldn't be a problem for external clients for those special purpose tags like it would be for visualeditor, and if needed they could retrieve the id by checking the wfmessage.
+>> In core, admins control the tags, not extensions, so they should also be able to rename them (in case of conflict, for example). 
+> 
+> Not really. What we're developing here is essentially another tag-applying extension (using automated logic to apply tags, just like OAuth, AbuseFilter, VisualEditor et al) but built into MW core. So this feature should behave like an extension, not like the newly-added manual tagging stuff in core. When extensions apply tags using automated logic, they have control over their tags' names etc. Likewise, when core uses automated logic to apply tags, core should control the tags. Extensions are free to provide a way to turn tags on and off; core can do the same (or, as Legoktm says, not).
+Except admins have complete control on extensions like AbuseFilter, and this autotagging feature is nothing but a core-implemented tag-only AbuseFilter (which makes it much more efficient), that's the request at any rate. If it isn't customizable enough, or end users can't understand the purpose, it won't get used.
+> What you are trying to create is a weird hybrid of extension-based tagging and manual tagging, which seems to be the main bone of contention here.
+I'll give up on the optionally defined part which can be addressed later on if needed. I still consider the i18n issue unresolved, but I'll ditch the localized messages for now.",1425523869,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I am in full agreement that localising tag names, which are purely meant as internal IDs, is wrong. The only place users should see these names in the UI is in the first column of Special:Tags. This is not currently the case - the tag filter input box and the AbuseFilter edit page being the most obvious places where the raw tag name is used - but the solution is to use the `tag-$tag` system message in those places, not to localise the internal ID. 
+
+Not only that, but it leads to difficulty for external consumers of the recentchanges API, as well as problems when trying to provide default tag description messages. 
+
+I like the idea of namespacing the tags. It's not currently done by most extensions, but it would be a good precedent to set. For example, `mw-redirected` or `mw-redirect-removed`. As I said, users should never have to interact with these names, except in the first column of Special:Tags and when using the API.
+
+> In core, admins control the tags, not extensions, so they should also be able to rename them (in case of conflict, for example). 
+
+Not really. What we're developing here is essentially another tag-applying extension (using automated logic to apply tags, just like OAuth, AbuseFilter, VisualEditor et al) but built into MW core. So this feature should behave like an extension, not like the newly-added manual tagging stuff in core. When extensions apply tags using automated logic, they have control over their tags' names etc. Likewise, when core uses automated logic to apply tags, core should control the tags. Extensions are free to provide a way to turn tags on and off; core can do the same (or, as Legoktm says, not).
+
+What you are trying to create is a weird hybrid of extension-based tagging and manual tagging, which seems to be the main bone of contention here.",1425517721,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I haven't followed all of the discussion here, but the patch seems drastically overcomplicated from what we need, which is a way for core to define tags (and then apply them). I would recommend just having a static function which returns core provided tags, similar to the one for extensions.
+
+I don't think there's a solid usecase for being able to disable core provided tags, so we can probably leave that out of the initial implementation.
+
+",1425497726,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1088558, @Anomie wrote:
+>> I'm indeed referring to the tag's name. IMO, it's a must have since it appears when filtering recent changes & co.
+> 
+> And yet no tag-using extension does this. Why should core?
+Extension-controlled tags are a different issue altogether, allowing admins to change the name for 'visualeditor' would cause issues, since we don't have a good rename mechanism yet. Localizing now would mean breaking the tags so it may no longer be worth it. But from now on, I think they should definitely use for new tags a localized name, that admins can't modify. In core, admins control the tags, not extensions, so they should also be able to rename them (in case of conflict, for example). Using a reserved prefix, as I suggested earlier, is not user friendly in light of the second point which I had overlooked initially.
+>> Especially when we'll have a user-friendly way of doing so with a drop-down menu and/or auto-completion or some hybrid of these (T27909 and T23383).
+> 
+> A dropdown menu should display the texts from the ""Appearance on change lists"" column on Special:Tags, making that a non-issue.
+> 
+> Auto-completion might take some more thought, but I still maintain that if i18n is needed then ""Appearance on change lists"" is the column to use rather than trying to have two layers of i18n.
+There would be only one layer of i18n in either case, since the tag appearance is the tag name by default. Using the tag appearance in a drop down would not be appropriate in many contexts : too verbose (some are quite long), parsing issues from wikitext (links, fonts, etc). A dropdown with 100+ entries isn't user friendly either so autocompletion is pretty much needed. The current filtering system, which relies on the tag name, should also be preserved, so switching to its parsed appearance would be quite an issue, not to mention consistency. Realistically, I think using the tag name is the only viable approach.
+>> The use case for VisualEditor is abundant, we could have at least a dozen of optional tags (for adding templates, images, categories, whatever) that could be activated or deactivated when needed as a debugging tool or to track certain types of edits.
+> 
+> I think you're going overboard with adding individual tags for adding and removing templates, images, categories, and so on. What next, ""Added the letter A"", ""Added the letter B""?
+Visual editor has the tendency of creating bugs when adding certain elements - a way of tracking them would be nice. I was not referring to a specific template, just adding a template (any template).
+>>>> - make it possible for admins to make the activation
+>>> 
+>>> Why is this a desired feature?
+>> The question is rather ""Why should we prevent use of this existing feature for those tags ?"" (see below).
+> 
+> Except it's not an existing feature. You're shoehorning it in.
+Tags activated by a config variable aren't an existing feature //at all//, whereas tags activated by admins already exist, although in a different context. This just extends this existing mechanism to the present context.
+>>>> - allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+>>> 
+>>> Where is this being stored? I see absolutely nothing about it in your WIP patch.
+>> It's not in this patch but the one for T89553, i.e. commit [[https://gerrit.wikimedia.org/r/#/c/190656/|980656]].
+> 
+> In which case that has nothing to do with this task: there's no requirement for using your overcomplicated proposal to accomplish this bullet point.
+It is a requirement. Not being able to patrol articles recently expanded from redirects, recently moved into mainspace and such makes those tags pretty much useless in the first place. (How could one know if each item has been dealt with ?) The initial request ([[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_117#Proposed_technical_change:_show_pages_expanded_from_redirects_on_Special:NewPages_and_Special:NewPagesFeed|link]]) was to have these appear at Special:NewPages so that it can be patrolled, but this can't be done so making them patrollable in recent changes is pretty much the only way of implementing this feature request. So we need to have these tags in valid_tag so we can store relevant data. Extension defined tags would store the data on their own end, but for core or user defined tags it's the only sensible way.
+Again it's not overcomplicated, using a second config variable would be just as complicated, and couldn't even match this requirement.
+>> True... I don't understand this objection, admins can activate tags not already defined by an extension or already activated, in the very current and live implementation of ChangeTags. The action and user interface both exist.
+> 
+> Yes, that exists. This whole new class of tags that can be activated by the same mechanism //doesn't// already exist.
+That whole new class of tags that can be activated with a config variable //doesn't// already exist, either. The difference is, the mechanism (config variable) doesn't even exist, whereas admin activation exists already so we might as well use it here too.
+
+Even if you object to the i18n issue, a config variable to define the tags still makes most sense since it can be modified as needed by extensions or wikis. And not adding these tags to the valid_tag table when activating them makes it impossible to customize the tag for the wiki. Admins can't make them patrollable or not as needed, so it's not even worth implementing, a bot-added tag would be better since tagged changes could be patrolled.",1425491671,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1085301, @Cenarium wrote:
+>>>! In T73236#1083545, @Anomie wrote:
+>> As far as I can tell from your non-functional WIP patch, you might be referring to trying to localize the internal tag names. That seems pointless when the tags are already localized for display where applicable.
+> I'm indeed referring to the tag's name. IMO, it's a must have since it appears when filtering recent changes & co.
+
+And yet no tag-using extension does this. Why should core?
+> Especially when we'll have a user-friendly way of doing so with a drop-down menu and/or auto-completion or some hybrid of these (T27909 and T23383).
+
+A dropdown menu should display the texts from the ""Appearance on change lists"" column on Special:Tags, making that a non-issue.
+
+Auto-completion might take some more thought, but I still maintain that if i18n is needed then ""Appearance on change lists"" is the column to use rather than trying to have two layers of i18n.
+
+> The use case for VisualEditor is abundant, we could have at least a dozen of optional tags (for adding templates, images, categories, whatever) that could be activated or deactivated when needed as a debugging tool or to track certain types of edits.
+
+I think you're going overboard with adding individual tags for adding and removing templates, images, categories, and so on. What next, ""Added the letter A"", ""Added the letter B""?
+
+>>> - make it possible for admins to make the activation
+>> 
+>> Why is this a desired feature?
+> The question is rather ""Why should we prevent use of this existing feature for those tags ?"" (see below).
+
+Except it's not an existing feature. You're shoehorning it in.
+
+>>> - allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+>> 
+>> Where is this being stored? I see absolutely nothing about it in your WIP patch.
+> It's not in this patch but the one for T89553, i.e. commit [[https://gerrit.wikimedia.org/r/#/c/190656/|980656]].
+
+In which case that has nothing to do with this task: there's no requirement for using your overcomplicated proposal to accomplish this bullet point.
+
+>>> Again, letting admins do the activation is much easier to implement,
+>> 
+>> False.
+> At least it's what I found out when actually trying to implement the thing (assuming a config variable is used to define tags, IMO a requirement).
+
+That's not very convincing, all things considered.
+
+>>> the current implementation of tags already allows it,
+>> 
+>> False.
+> True... I don't understand this objection, admins can activate tags not already defined by an extension or already activated, in the very current and live implementation of ChangeTags. The action and user interface both exist.
+
+Yes, that exists. This whole new class of tags that can be activated by the same mechanism //doesn't// already exist.",1425482408,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1083545, @Anomie wrote:
+>>>! In T73236#1083158, @Cenarium wrote:
+>> Ok, here's why we need a config variable to define optional tags IMO, it allows to:
+>> - have a neat and efficient 'isset' check instead of ugly 'in_array'
+> 
+> You've given no evidence that this is impossible with any solution other than yours. Or, for that matter, that this is an issue that should drive the implementation.
+I can't imagine and rebut every possible implementation, I would need more specifics, keeping in mind the constraints below.
+
+>> - easily define the wfmessage they should use
+> 
+> The messages used by tags are already clearly defined by how tags work.
+> 
+> As far as I can tell from your non-functional WIP patch, you might be referring to trying to localize the internal tag names. That seems pointless when the tags are already localized for display where applicable.
+I'm indeed referring to the tag's name. IMO, it's a must have since it appears when filtering recent changes & co. How could non-English speakers use these tags to filter recent changes if they can't even understand their purpose? Especially when we'll have a user-friendly way of doing so with a drop-down menu and/or auto-completion or some hybrid of these (T27909 and T23383). The appearance of tags when applied to specific edits is a different issue, it can be very different from the actual tag's name and contain wikitext or links. We have no need to make a default for it, since it's already the tag's name. We may want to make a default for the tag description to further describe its intent, but it would only be seen from Special:Tags directly, not from the tag input box.
+>> - easily unset the default autotags in case an extension wants to provide more specific ones (e.g. with more special casing, usergroups checks, etc, making many of the default ones redundant).
+> 
+> This seems like a requirement without a use case. And if some extension were to want to do this, it hurts nothing for the core tag to remain defined despite being deactivated in LocalSettings.php.
+It does. There are already dozens of defined tags on many wikis. Special:Tags takes quite a while to load on enwiki. If an extension like 'ImprovedBuiltInAutoTags' were to add a dozen or more of tags that would be more customizable than the default core autotags and therefore supersede them, and may also check for things like wikitext errors, the list of tags would become excessively long and confusing with all the redundancies. The use case for VisualEditor is abundant, we could have at least a dozen of optional tags (for adding templates, images, categories, whatever) that could be activated or deactivated when needed as a debugging tool or to track certain types of edits.
+>> Now for activation, doing this with the valid_tag table allows to:
+>> - avoid a second config variable
+> 
+> No need for this if you give up your idea of having the ability to not-even-define core tags.
+Not just this, also localization.
+>> - make it possible for admins to make the activation
+> 
+> Why is this a desired feature?
+The question is rather ""Why should we prevent use of this existing feature for those tags ?"" (see below). If an autotag can be activated by simply clicking on a button named 'activate'/'aktivigi'/'activar'/'rakendama'/'ενεργοποιώ'/ the appropriate translation for the wiki (or asking an admin to do it), isn't it going to be much easier to activate the tag than having to file a phabricator request for it, in English, specifying the config variables that should be set ? We would have to describe how to make the request at Special:Tags, and casual users would have to be motivated enough to find out about config variables and such complexities. I'm pretty sure requests would be sparse, not because of lack of interest but because of excessive complexity in making them. There's already eight autotags implemented just in this patch set, more will be added in core progressively, even more by extensions, so making requests to activate them every time doesn't look viable to me. And as I mentioned earlier, wikis may want to disable one if more specific abusefilter or bot tags are enabled, then reactivate it in case of issues.
+Or are you suggesting that we should make autotags active by default ? I wouldn't recommend it, as this would result in a flurry of users expressing their discontent at being unexpectedly tagged, complaints of redundant tags, wikis requesting opt out and such. This feature should be optional and opt-in, but very easily so. Plus, there wouldn't be much sense in activating by default a bunch of tags if nobody actually check them out at Special:Tags.
+>> , without a single line of code needed since everything already exists
+> 
+> False, unless you're counting LocalSettings.php as code.
+I didn't imply more code would be needed here, just pretty much the same, same complexity.
+>> - have more use for this vastly underused table
+> 
+> Why is this a requirement?
+Not a requirement per se.
+>> - allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+> 
+> Where is this being stored? I see absolutely nothing about it in your WIP patch.
+It's not in this patch but the one for T89553, i.e. commit [[https://gerrit.wikimedia.org/r/#/c/190656/|980656]]. It's in a new field vt_importance of the change_tag table. Tags marked as 'important' would make changes tagged by it patrollable. I'll update the patch in a couple of days, since there is support for this feature on enwiki. Take the autotag 'un-redirects' for example, it should be possible for admins to mark this tag as 'patrollable', this way users will be able to patrol ""articles expanded from redirects"", which can't be done from Special:NewPages. Same for the autotag 'cross namespace moves', which will allow to patrol ""pages moved into mainspace"". Both are frequently requested features. So admins should be able to mark these two autotags as patrollable (and others too), and to store this data the valid_tag table is a perfect fit. See also T91425 which concerns Special:ProblemChanges.
+>> Again, letting admins do the activation is much easier to implement,
+> 
+> False.
+At least it's what I found out when actually trying to implement the thing (assuming a config variable is used to define tags, IMO a requirement). Thinking about it, I forgot to update the canActivateTag function (which shouldn't count inactive optional tags), I'll upload a new patch set. But nothing more is needed, if a config variable were used instead, analog checks would have to be done. And we would have to find some way to store the above data, since we couldn't use the valid_tag table.
+>> the current implementation of tags already allows it,
+> 
+> False.
+True... I don't understand this objection, admins can activate tags not already defined by an extension or already activated, in the very current and live implementation of ChangeTags. The action and user interface both exist.
+>> on the other hand using a second config variable would be a hassle to implement and fuzzy to maintain.
+> 
+> Claim is based on a faulty premise, and probably also false.
+I still don't see how to store the data for patrolling / problem changes besides using the valid_tag table. And having to maintain a second config variable in parallel seems bothersome to me.",1425433184,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1083158, @Cenarium wrote:
+> Ok, here's why we need a config variable to define optional tags IMO, it allows to:
+> - have a neat and efficient 'isset' check instead of ugly 'in_array'
+
+You've given no evidence that this is impossible with any solution other than yours. Or, for that matter, that this is an issue that should drive the implementation.
+
+> - easily define the wfmessage they should use
+
+The messages used by tags are already clearly defined by how tags work.
+
+As far as I can tell from your non-functional WIP patch, you might be referring to trying to localize the internal tag names. That seems pointless when the tags are already localized for display where applicable.
+
+> - easily unset the default autotags in case an extension wants to provide more specific ones (e.g. with more special casing, usergroups checks, etc, making many of the default ones redundant).
+
+This seems like a requirement without a use case. And if some extension were to want to do this, it hurts nothing for the core tag to remain defined despite being deactivated in LocalSettings.php.
+
+> Now for activation, doing this with the valid_tag table allows to:
+> - avoid a second config variable
+
+No need for this if you give up your idea of having the ability to not-even-define core tags.
+
+> - make it possible for admins to make the activation
+
+Why is this a desired feature?
+
+> , without a single line of code needed since everything already exists
+
+False, unless you're counting LocalSettings.php as code.
+
+> - have more use for this vastly underused table
+
+Why is this a requirement?
+
+> - allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+
+Where is this being stored? I see absolutely nothing about it in your WIP patch.
+
+> Again, letting admins do the activation is much easier to implement,
+
+False.
+
+> the current implementation of tags already allows it,
+
+False.
+
+> on the other hand using a second config variable would be a hassle to implement and fuzzy to maintain.
+
+Claim is based on a faulty premise, and probably also false.",1425410962,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Ok, here's why we need a config variable to define optional tags IMO, it allows to:
+- have a neat and efficient 'isset' check instead of ugly 'in_array'
+- easily define the wfmessage they should use
+- easily unset the default autotags in case an extension wants to provide more specific ones (e.g. with more special casing, usergroups checks, etc, making many of the default ones redundant).
+I can't think of any other reasonable way of defining these tags.
+
+Now for activation, doing this with the valid_tag table allows to:
+- avoid a second config variable
+- make it possible for admins to make the activation, without a single line of code needed since everything already exists
+- have more use for this vastly underused table
+- allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+Again, letting admins do the activation is much easier to implement, the current implementation of tags already allows it, on the other hand using a second config variable would be a hassle to implement and fuzzy to maintain.",1425406520,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I've updated [[https://gerrit.wikimedia.org/r/#/c/193040/|commit 193040]] with various redirect-related tags including those suggested here.
+
+>>! In T73236#1076852, @Anomie wrote:
+> Extensions already have hooks to use.
+> 
+> I see no good reason to support wikis wanting to not-even-define built-in tags.
+
+If the ListDefineTags hook is used, we can't simply define the source as 'optional'. Yet extensions should also be able to define optional tags. In the implementation I made, I use the config variable to not only define the tags but also to provide the relevant message giving the name of the tag (for internationalization purposes). It also allows a simple 'isset' check. A config variable to define all optional tags actually makes implementation easier. Wikis with lots of extensions may have lots of default optional tags, some of them may be irrelevant to them, so they may want to unset some, although it's not essential, just a bonus. And activation by admins is very easy to implement. So I don't see the need to think of other solutions, unless there is a serious issue with this implementation.",1425279494,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Extensions already have hooks to use.
+
+I see no good reason to support wikis wanting to not-even-define built-in tags.",1425252648,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1076767, @Anomie wrote:
+>>> Why are you assuming that the tags couldn't show up as defined but not active when the config setting for applying them is turned off?
+>> 
+>> To do that we would need two distinct config variables
+> 
+> No we wouldn't. We'd need one config variable to activate the feature, and //non-config// logic somewhere to define the tags and conditionally activate them.
+
+Maybe, but if we did that, wouldn't it be more complicated, especially for extensions ? And how about wikis not wanting some built-in tags defined at all (whether from core or extensions) ?
+I don't see the issue since in this case, it's actually very easy to allow admins to activate or not - we've already got everything that we need.",1425248495,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1076763, @Cenarium wrote:
+>>>! In T73236#1069817, @Anomie wrote:
+>> Why are you assuming that the tags couldn't show up as defined but not active when the config setting for applying them is turned off?
+> 
+> To do that we would need two distinct config variables
+
+No we wouldn't. We'd need one config variable to activate the feature, and //non-config// logic somewhere to define the tags and conditionally activate them.",1425246730,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1069817, @Anomie wrote:
+> Why are you assuming that the tags couldn't show up as defined but not active when the config setting for applying them is turned off?
+
+To do that we would need two distinct config variables : one to list defined tags, one to make them active. This is just as complicated as letting admins activate them or not : it requires checking the config variable for active tags instead of checking the valid_tag table.
+
+>>! In T73236#1069290, @TTO wrote:
+> The fact is, configuration settings that affect the entire wiki belong in `$wg` variables. As far as I know, nowhere in MediaWiki or the WMF-installed extensions is there a way to modify global configuration state from the wiki (perhaps with the exception of Global Groups).
+I agree that //defining// the optional built-in tags is a config issue, but //activating// them is not. It should be just as easy for admins to activate or deactivate an optional tag as to make an abuse filter tag or not.
+
+I'll implement the redirect-related tags in a new patch set.",1425246544,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1068996, @Cenarium wrote:
+> Config only isn't satisfactory, since those tags should not be active by default, but if we don't define them in config, they don't appear at Special:Tags so how can users of the wiki be even aware of their existence ?
+
+Why are you assuming that the tags couldn't show up as defined but not active when the config setting for applying them is turned off?",1424962595,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","The fact is, configuration settings that affect the entire wiki belong in `$wg` variables. As far as I know, nowhere in MediaWiki or the WMF-installed extensions is there a way to modify global configuration state from the wiki (perhaps with the exception of Global Groups).
+
+The long-term plan is to actually get rid of the `$wg` scheme altogether, which would allow for the creation of an on-wiki configuration interface. This way, configuration settings would be stored in the DB (or CDB/similar file) rather than a PHP file, and stewards would be able to alter global wiki configuration settings from within the MediaWiki interface. See https://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database_2 and T28992.
+
+>>! In T73236#1068996, @Cenarium wrote:
+> but if we don't define them in config, they don't appear at Special:Tags so how can users of the wiki be even aware of their existence ? 
+
+That's a broader issue with configuration variables in general. People seem to manage to find them in general, see T65388 for a request to change a non-obvious setting.",1424940345,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1065778, @Anomie wrote:
+>>>! In T73236#1064690, @TTO wrote:
+>> Your point about reserving a ""mw-"" namespace for core tags is a good idea. However I don't think we need the added complexity of ""optional tags"". ""Built-in tags"" (just a temporary name I made up for tags added by MW core) could be turned on and off in the wiki's configuration settings
+> 
+> I agree with this, now that we have regular SWAT windows getting a configuration setting changed isn't very difficult, so the added complexity of having an on-wiki page for admins to directly do this seems unwarranted.
+
+Config only isn't satisfactory, since those tags should not be active by default, but if we don't define them in config, they don't appear at Special:Tags so how can users of the wiki be even aware of their existence ? I agree with the idea of using a config variable, rather than a hook, but it should only define the tag, not make it active. Users are thus informed of the availability of those tags, and admins can then make them active or not as needed.
+
+I've made a proof of concept implementation in [[https://gerrit.wikimedia.org/r/#/c/193040/|commit 193040]], which uses cross namespaces moves as an example (easier to implement). Since the user interface for activation already exists, it isn't complex to implement, they can be activated the same way as user-defined tags.",1424923494,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1064690, @TTO wrote:
+> Your point about reserving a ""mw-"" namespace for core tags is a good idea. However I don't think we need the added complexity of ""optional tags"". ""Built-in tags"" (just a temporary name I made up for tags added by MW core) could be turned on and off in the wiki's configuration settings
+
+I agree with this, now that we have regular SWAT windows getting a configuration setting changed isn't very difficult, so the added complexity of having an on-wiki page for admins to directly do this seems unwarranted.",1424876178,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","It wouldn't really be core/extension adding to valid_tag but the tag manager that activates it. Config variables may be slightly less complicated to implement but it also makes it much harder to activate / deactivate a built-in tag.
+I'd like this to be doable on wiki, since there's likely to be some interplay between these tags and those added by filters or bots, the later two offering more specific options (only certain users, namespaces, page size constraints, etc) that could supersede the built-in tag but since their reliability is limited (bot failure, condition limits...), and not all wikis would have the resources to implement these, or only intermittently, the built-in tags would be a handy default/fallback that should be readily available.
+
+Another reason for this is patrolling of tagged changes... As I'm planing it, extension-defined tags would use a hook to define patrollable tags. So the behavior would be configured by the extension (for example visual editor would only list 'visualeditor-needcheck' as patrollable). On the other hand, the 'patrollable' status of user-defined tags would be stored in a field vt_important of the valid_tag table that admins could modify from Special:Tags. So if active built-in tags are not stored in valid_tag, how do we store the patrollable status of these ? As you mentioned there, a config variable would be unsatisfactory... doing this from Special:Tags is much easier.
+
+If we add support for this class of 'optional' tags that can be defined and applied by core or extensions, but whose activation is up to tag managers, the built-in mediawiki tags would only be one aspect of it. Extensions could provide various optional tags without having to create a user interface for their activation/deactivation. It's kind of hybrid, but it allows much more control for end users, and valid_tag allows to store extra info for customization.",1424848563,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Your point about reserving a ""mw-"" namespace for core tags is a good idea. However I don't think we need the added complexity of ""optional tags"". ""Built-in tags"" (just a temporary name I made up for tags added by MW core) could be turned on and off in the wiki's configuration settings using something like
+
+```
+$wgUseBuiltInTags = true; // have 'em all
+$wgUseBuiltInTags = array( 'mw-redirected', 'mw-redirect-removed' ); // list the ones that are wanted
+$wgUseBuiltInTags = false; // none
+```
+
+Extensions would be able to provide their own configuration variables, which could behave in a similar fashion, or differently, depending on the requirements of that extension.
+
+I should point out that only manually defined tags are present in the `valid_tag` table. Extensions do not add to this table, and neither should core.
+",1424831516,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I'd suggest to implement those in core, but with a hook so that they can be disabled and more of the same type can be added by extensions. IMO, these tags should be optional so I would make it their defining characteristic. They should probably not be enabled by default, it would be up to admins to enable them or not at Special:Tags (and they could subsequently disable them if they want).
+
+They would be listed at Special:Tags via a 'ListOptionalTags' hook (core tags included). It should be possible for tag managers to activate and deactivate those tags (implemented by adding or removing them from the valid_tag table), but not for users to apply them to edits. Before applying those tags, MediaWiki core or extensions would check that the tag is defined in the valid_tag table (i.e. activated).
+
+So basically three categories of tags :
+- User-defined tags : defined and activated by tag managers, directly applied by users
+- Extension-defined tags : defined, activated and applied by extensions
+- Optional tags : defined by core/extensions, activated by users, and applied by core/extensions
+We may also reserve a namespace for those defined in core, such as ""mw-"".",1424831163,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1056437, @TTO wrote:
+> I wonder if it would be best to do this as a core feature, an extension (perhaps something like `SimpleTags`), or a Wikimedia-specific hook?
+
+Core feature or extension, not a hook IMO.",1424708404,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I wonder if it would be best to do this as a core feature, an extension (perhaps something like `SimpleTags`), or a Wikimedia-specific hook?",1424519841,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","The un-redirect part would be helpful for [[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_117#Proposed_technical_change:_show_pages_expanded_from_redirects_on_Special:NewPages_and_Special:NewPagesFeed|this request]], particularly when combined with patrolling of tagged changes from T89553. This is a frequently requested feature, along with pages moved into mainspace.",1424477330,PHID-USER-znn4xfvlp7e7mr2g3tvl,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""","Screenshot
+
+Steps to reproduce:
+
+1.Open a blank page with VE
+2.Insert an image as the first item of the document
+3.Save the page
+4.Reopen the page
+5.The image gets highlighted, now try to delete the image
+
+
+Observed Result:
+The following error appears in the console:
+Uncaught Error: offset was inside a handlesOwnChildren node
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14961}",1411497900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_description,resolved
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""",Verified the fix in production,1412885663,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""",Verified the fix in test2,1412370570,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""",Verified the fix in Betalabs,1411688615,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""","Change 162884 merged by jenkins-bot:
+Be more cautious about placing the cursor
+
+https://gerrit.wikimedia.org/r/162884",1411676932,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""","Change 162884 had a related patch set uploaded by Esanders:
+Be more cautious about placing the cursor
+
+https://gerrit.wikimedia.org/r/162884",1411652949,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""",It happens for reflist too.Though thats not something common to encounter to have reflist at the beginning of a page,1411498048,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"The VisualEditor section of BetaFeatures appears before the introduction
+
+In my experimental setup, the VisualEditor section in the beta features appears as first item, just before the introductory text about beta features.
+
+It appears that in the LocalSettings.php I load the VisualEditor extension before the BetaFeatures extension, and exchange the order results in a good placement of the VE as BF (normal order).
+
+--------------------------
+**Version**: master
+**Severity**: minor
+
+**Attached**: {F14687}",1411229760,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-nmmwisceyjh3lm2bamkh,task_description,resolved
+BetaFeatures: the VisualEditor section appears before the introduction,Re-close. Thanks!,1411236943,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Change 161685 merged by jenkins-bot:
+Check the existence of BetaFeatures before adding the 'visualeditor-enable' preference
+
+https://gerrit.wikimedia.org/r/161685",1411236745,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Thanks for merging, Bartosz.
+
+I propose a patch for the second solution also, I find it better to check the existence of BetaFeatures.",1411235714,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Change 161685 had a related patch set uploaded by Seb35:
+Check the existence of BetaFeatures before adding the 'visualeditor-enable' preference
+
+https://gerrit.wikimedia.org/r/161685",1411235581,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Change 161677 merged by jenkins-bot:
+Unset the preference key before adding it
+
+https://gerrit.wikimedia.org/r/161677",1411234703,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Oh, I misread your solution 1. That also makes sense. Thanks for the patch!",1411234582,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Change 161677 had a related patch set uploaded by Seb35:
+Unset the preference key before adding it
+
+https://gerrit.wikimedia.org/r/161677",1411232797,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Yeah. VE should just check for the presence of 'BetaFeatures' class, instead of relying on the order. You can just use class_exists() for that. Want to submit a patch?",1411232436,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Since the VisualEditor registers its preference 'visualeditor-enable' in the standard GetPreferences and in the BF’s GetBetaFeaturePreferences, one is be cancelled.
+
+If BF is loaded before VE (and hence BF’s GetPreferences is before VE’s GetPreferences), VE takes care and don’t add again the 'visualeditor-enable'.
+
+But if VE is loaded before BF, VE’s GetPreferences first adds its 'visualeditor-enable' then VE’s GetBetaFeaturePreferences erases the previous value and remplaces it by the 'visualeditor-emable' in the BF syntax, but by *keeping* the same place in the $prefs array, so the PreferencesForm loads it in a ""wrong"" order.
+
+Two non-exclusive solutions:
+1. in BF, unset the $prefs[$key] before adding it, to restart the order (tested, it works)
+2. in VE in onGetPreferences function, add a second condition before adding the 'visualeditor-enable' preference ""!AutoLoader::loadClass( 'BetaFeatures' )"" (tested, it works)",1411231646,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","See the 6 hidden comments I placed in https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/SandboxVE&action=edit .
+Only 2 of them are visible when VEditing, https://en.wikipedia.org/wiki/User:Elitre_(WMF)/SandboxVE?veaction=edit .
+Reported on fr.wp, see for example that they are missing from sections Personagges and Liens externes in https://fr.wikipedia.org/w/index.php?title=Détective_Conan&veaction=edit .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1411214460,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mfpswg7xbkj64zruzhyd,task_description,resolved
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","@jdforrester-WMF, comments won't show up if placed among a list of external links (see https://de.wikipedia.org/w/index.php?title=Benutzerin:Elitre_(WMF)/sandbox&veaction=edit&vesection=1 ). Should this task be re-opened?",1432289295,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor",(Filed as T90517.),1424800252,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Ooh, thank you, that was helpful. I can reproduce only if the reference is at the end of paragraph, and you add the comment after it. Adding a comment before a reference, or adding it after and typing some more text, works correctly. I can also reproduce in production, so that must be a separate issue too.",1424738559,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Hmm, I am able to reproduce it consistently.Nope thats a different case, I am not adding anything into a slug.Attaching the screen capture if it helps
+{F45842}",1424737964,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","@Ryasmeen, can you elaborate? I can't reproduce that, neither in labs nor prod – I can open an existing article in VE, place the cursor after a citation (like ""[1]""), insert a comment there, and save the page with the comment appearing in the source code (I didn't actually save, but ""Review your changes"" shows it). There is currently a separate issue with inserting things into slugs (T89192) – are you sure you're not running into that?",1424737299,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not getting added after template,gallery,math node and table",1424728461,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not getting added after template,gallery and table",1424727818,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not getting added after template and table",1424726491,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not getting added after template",1424725977,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not gettiing added after template",1424725965,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Comment added after citation node is not getting added , nothing in review changes section after adding it.",1424725093,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Comment added after citation not is not getting added , nothing in review changes section after adding it.",1424725074,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Change 192051 merged by jenkins-bot:
+Generate CommentNodes more leniently
+
+[[https://gerrit.wikimedia.org/r/192051]]",1424523439,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","The patch above correctly displays all six comments in the example from task description.
+
+> (this could be blamed on Parsoid's funny output, though – the <!-- --> is outside the <p></p>) 
+
+Filed as T90321.",1424490492,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Change 192051 had a related patch set uploaded (by Bartosz Dziewoński):
+Generate CommentNodes more leniently
+
+[[https://gerrit.wikimedia.org/r/192051]]
+
+#patch-for-review",1424490119,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Am I missing something obvious, or is this actually pretty simple?
+
+The logic for this behavior is in Converter and ve.dm.CommentNode.static.toDataElement, we only generate a content node if converter.isExpectingContent() (=we're inside one of BlockquoteNode, HeadingNode, ParagraphNode, PreformattedNode, and expecting text). Therefore no comment will appear in VE for comments placed between block-level elements – paragraphs, tables, floated images, box-like templates, headings – and more confusingly, for comments placed at the beginning of a line containing a paragraph, for example (this could be blamed on Parsoid's funny output, though – the <!-- --> is outside the <p></p>) or at the beginning of a table cells and list items (and this is all our fault).
+
+But! we already have logic to control which elements can be nested inside which (for example, table rows may only contain table cells; ordered list may only contain list items). And we already have logic to wrap things that are not block-level in paragraphs. Looks like we could easily use that.
+
+I implemented it, played with it, and encountered no problems. Patch incoming.",1424488847,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","The reason for this is that we're currently very conservative about which comments we deem to be ""safe"" to display, because there are some ""unsafe"" ones, like comments placed between two table rows. We haven't yet refined the logic for this, so right now a lot of comments are erroneously identified as unsafe.",1411409916,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+VisualEditor: Paste from Microsoft Word converting spaces to line breaks,"original Word source causing issues
+
+Some spaces in Word documented are being converted into line breaks when pasting into VE.
+
+Example: https://www.mediawiki.org/wiki/User:Rosencrantz/Paste
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15305}",1411157280,PHID-USER-evwol34rsld7viokxokd,PHID-TASK-lsebojbccynjbxj4wazk,task_description,open
+VisualEditor: [Regression] The #contentSub should not be removed during loading phase,"1. View https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License
+2. Observe whitespace between heading, subtitle and first paragraph
+3. Click Edit beta
+
+Expected:
+* Table of contents slide up and content remains in the same position and dims.
+
+Actual:
+* The content shift upwards due to #contentSub being display-none'ed. This element is empty by default (also on English Wikipedia) but it does have a line height and thus affects flow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1410983640,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rd24i5biuj4r7i3jeier,task_description,resolved
+VisualEditor: [Regression] The #contentSub should not be removed during loading phase,"(In reply to Krinkle from comment #0)
+> 1. View https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License
+> 2. Observe whitespace between heading, subtitle and first paragraph
+> 3. Click Edit beta
+> 
+> 
+
+For comparison, here's a redirect page where the element is non-empty:
+
+https://en.wikipedia.org/wiki/GNU_Library_General_Public_License",1410983956,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rd24i5biuj4r7i3jeier,task_subcomment,NA
+VisualEditor: [Regression] The #contentSub should not be removed during loading phase,//**content hidden as private in Bugzilla**//,1410983936,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rd24i5biuj4r7i3jeier,task_subcomment,NA
+VisualEditor: [Regression] The #contentSub should not be removed during loading phase,"Caused by I2d6157708bd7b4c3a7c647 which fixed bug 52243 and bug 54325.
+
+Perhaps we should use ""visibility: hidden;"" instead of ""opacity: 0;"" ?",1410983876,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rd24i5biuj4r7i3jeier,task_subcomment,NA
+"VisualEditor: [Regression] In Transclusion (multi-template) dialog, moving a template past a content block then focuses the content block, not the selected template","Environment- Production, Test2, beta
+
+1> open the transclusion for any citation (book/news/journal).
+2> add a content and a template  below the citation in the modal.
+3> Now highlight the Citation and click to move the citation down.
+4> Notice that although the citation moves down and the Content moves up, but now the highlight moves to the content instead of staying at the Citation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1410797520,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ouvl42pvdoq34kfphg3u,task_description,open
+"VisualEditor: [Regression] In Transclusion (multi-template) dialog, moving a template past a content block then focuses the content block, not the selected template",Possibly caused by our changes to focussing in dialogs recently?,1410806753,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ouvl42pvdoq34kfphg3u,task_subcomment,NA
+"VisualEditor: [Regression] In Transclusion (multi-template) dialog, moving a template past a content block then focuses the content block, not the selected template","Created attachment 16472
+Highlight jumps to the next item following the Citation, that is content
+
+**Attached**: {F14730}",1410797644,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ouvl42pvdoq34kfphg3u,task_subcomment,NA
+"VisualEditor: [Regression] In Transclusion (multi-template) dialog, moving a template past a content block then focuses the content block, not the selected template","Created attachment 16471
+citation highlighted
+
+**Attached**: {F14729}",1410797579,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-ouvl42pvdoq34kfphg3u,task_subcomment,NA
+VisualEditor: Duplicate resize handles appear on unhighlighted image nodes after resize,"1. Select image node at <https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet#Media_files>
+2. Resize an image
+3. While a new thumb is generated and fetched from Commons, highlight a different image.
+
+## Unexpected behaviour
+
+Observe, after the thumbnail fetch has completed the dimmed pixelated thumbnail preview will be replaced with a sharp opaque rendering. Unexpected is that this new rendering results in the appearance of a new resize handle at its bottom right corner.
+
+This new highlight and resize handle aren't supposed to exist and aren't properly kept up to date either (when reflowing the document they mostly stay behind and only update during more general regenerations).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1410640380,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5l7l3b3s6yrlk2ddzysl,task_description,resolved
+VisualEditor: Duplicate resize handles appear on unhighlighted image nodes after resize,I can't reproduce this anymore. Looks like it was fixed.,1530904132,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5l7l3b3s6yrlk2ddzysl,task_subcomment,NA
+VisualEditor: Duplicate resize handles appear on unhighlighted image nodes after resize,"Still reproducible on latest master. On fast networks it's harder to reproduce but there's no doubt we're missing some state integrity in our handling for that callback.
+ 
+{F41807}",1424113319,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5l7l3b3s6yrlk2ddzysl,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"```
+review/jdlrobson/mantleview x ~/Sites/w/extensions/MobileFrontend $ vagrant provision
+==> default: Running provisioner: lsb_check...
+==> default: Running provisioner: puppet...
+Running Puppet with site.pp...
+Warning: Could not retrieve fact ipaddress
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+The following SSH command responded with a non-zero exit status.
+Vagrant assumes that this means the command failed!
+
+FACTER_fqdn='mediawiki-vagrant.dev' FACTER_forwarded_port='8080' FACTER_shared_apt_cache='/vagrant/cache/apt/' FACTER_environment='vagrant' FACTER_port_fragment=':8080' FACTER_share_owner='502' FACTER_share_group='20' FACTER_provider_name='virtualbox' puppet apply --templatedir /vagrant/puppet/templates --verbose --config_version /vagrant/puppet/extra/config-version --fileserverconfig /vagrant/puppet/extra/fileserver.conf --logdest /vagrant/logs/puppet/puppet.20f0fbdd9.log --logdest console --write-catalog-summary --modulepath '/tmp/vagrant-puppet-1/modules-0:/etc/puppet/modules' --hiera_config=/tmp/vagrant-puppet-1/hiera.yaml --manifestdir /tmp/vagrant-puppet-1/manifests --detailed-exitcodes /tmp/vagrant-puppet-1/manifests/site.pp || [ $? -eq 2 ]
+
+Stdout from the command:
+
+
+
+Stderr from the command:
+
+Warning: Could not retrieve fact ipaddress
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+```",1410541620,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-y4soahtd3ne6ieogzdqn,task_description,declined
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,We can safely decline this. The base VM memory has been bumped a couple of times since this was opened and roles can now define an increase to memory if necessary.,1478539905,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"Has anyone seen this problem in the last two years?
+Or should this task get declined?",1478167283,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"I know that some of the OOM issues during provisioning were happening during Ruby gem compilation (usually ffi). It probably wasn't the root cause—more likely the compounding effect of less base VM RAM and more memory required by the base MW dependencies (HHVM)—but it's worth noting that there have been far fewer reported cases since we switched to using system packages. [1][2]
+
+[1] https://gerrit.wikimedia.org/r/#/c/158564/
+[2] https://gerrit.wikimedia.org/r/#/c/156207/",1411754521,PHID-USER-7bifphmxtcqgvdofuzla,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,It hasn't happened to me in a while (maybe correlated to less Flow coding?)... soon as it does I'll be back here.,1411748673,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"I'll also add the easiest way to trigger the error is to try and load the hhvm debugger, 
+
+    hhvm -m debug --debug-host ::1
+
+always fails for me with not enough memory if it booted with 1G due to reading the wrong settings.yml",1411746321,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"I've had this happen several times, not because of applications eating ram but because of https://bugzilla.wikimedia.org/show_bug.cgi?id=70304
+
+I have to reload vagrant from the appropriate directory and it starts up with my configured 4G instead of 1G",1411746188,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"Jon, poke. Any progress in reproducing and determining which application is eating your instance RAM?",1411745597,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"(In reply to Jon from comment #2)
+> Nothing looked suspect. Is there any particular commands you would like me
+> to run?
+
+# Top 20 processes by resident memory size
+$ ps -e -orss=,args= | sort -b -k1,1nr | head -20
+
+# Free/used ram
+$ free -m
+
+# Job queue status
+$ mwscript showJobs.php --wiki=wiki --group",1410542901,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"I'm using Flow, MobileFrontend and VisualEditor. I notice this seems to correlate when I have a Flow page with over 20 posts and I continuously keep hitting.
+
+Nothing looked suspect. Is there any particular commands you would like me to run?",1410541944,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"(In reply to Jon from comment #0)
+> Warning: Could not retrieve fact ipaddress
+> Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+> Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+
+Any idea what's eating all the ram in your VM? Redis full of unprocessed jobs perhaps?",1410541844,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+"VisualEditor: After removing the Template:Top,trying to place cursor on content throws TypeError: Cannot read property 'Left'/'right'/'start' of null","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a template Top, specify a bg color code so you can see the effect better on CE.I tried with #FFFFE0
+3.Now click on Insert and Save the page
+4.You will see the entire content after that template (until references list) gets added as a Content section for that template and inherits the styling specified in the template parameters.
+5.Reopen the page
+6.Reopen the transclusion dialog for that template
+7.Click on the Delete icon to remove the template ""Top"" to just retain the usual format of the text.
+8.Click on ""Apply Changes""
+9.Now when you are back to CE, try to place your cursor on the content which was part of that template
+
+Observed Result:
+It throws the following error on each click:
+
+
+Uncaught TypeError: Cannot read property 'right' of null
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 85 is out of bounds 
+
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14694}",1410203160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-krueh2a24bjyg7r3twut,task_description,open
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","The Sub-heading 4 font as shown in the Text Style drop-down does not match with the other Sub-headings in it.
+
+Screenshot:
+{F25185708}
+(old screenshot: F15333)
+
+Task: Update the styles for VisualEditor's ""Format"" dropdown when using the [MonoBook](https://www.mediawiki.org/wiki/Skin:MonoBook) [skin](https://www.mediawiki.org/wiki/Manual:Skins), so that the text size for headings inside the dropdown is the same as their size on the page.",1410188100,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-dx4wusevsujq7v5py7nu,task_description,resolved
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","Change 470992 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update the styles for VisualEditor's ""Format"" dropdown
+
+[[https://gerrit.wikimedia.org/r/470992]]",1541107212,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","Change 470992 had a related patch set uploaded (by Bjornskjald; owner: Bjornskjald):
+[mediawiki/extensions/VisualEditor@master] Update the styles for VisualEditor's ""Format"" dropdown
+
+[[https://gerrit.wikimedia.org/r/470992]]",1541070910,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)",https://codein.withgoogle.com/tasks/6745215428722688/,1540311144,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)",https://codein.withgoogle.com/dashboard/tasks/6745215428722688/,1540273504,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)",I would like to mentor this task in #Google-Code-in-2018.,1540253252,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","This is still a problem, the font size in the menu doesn't match the font size in the page content:
+{F25185698} {F25185708}
+Looks like VE's styles were never updated after the change to heading font sizes in MW: {237787cbadaadf31f5d71733ee8bac5b463ba292}.
+
+(this may look like my fault, but it's not, I was not on the VE team then yet ;) )",1534794823,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","Confirmed - Sub-headings(started with Sub-heading 1) are decreasing proportionally like this: 130, 115, 100(for Sub-heading 3). However, for Sub-heading 4 - it has font-size: 80% instead of 85%. 
+
+Look at the attached screenshot where Sub-heading 4 has font-size: 85% - it looks much more proportional relative to other Sub-headings.",1415403886,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","Created attachment 17076
+monobook Sub-heading 4 with font-size 85%
+
+**Attached**: {F15334}",1415403808,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+VisualEditor:  Please add a 'close' box to the wikitext warning,"It's not obvious to everyone that you can click the wikitext warning to make it go away.  Please add an 'X' or something that makes it look like you should click on it if you don't want it to be there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410155760,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-vussyglstlop2mytex2t,task_description,resolved
+VisualEditor:  Please add a 'close' box to the wikitext warning,"Adding close buttons / etc. to MediaWiki's notice system is bug 40307. Merging this into that rather than duplicating.
+
+*** This bug has been marked as a duplicate of bug 40307 ***",1410207810,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vussyglstlop2mytex2t,task_subcomment,NA
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,"A thing that happens to me frequently is that I paste the title of another article. When this happens, it's formatted as a heading. This is correct HTML-wise, but it's never what I mean - I usually mean to paste it as plain text or as a link.
+
+It would be nice if the VE vould guess it.
+
+A long shot, I know, but it happens to me a lot and I wanted to write it down :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410095760,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-347gkxmboadsdufxjprl,task_description,duplicate
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,"One could debate whether copying within a heading should write plain text to the clipboard, but then there is a common edge case where you select the whole heading, i.e. <h1>|word|</h1>. It's probably 50/50 what the user intends to happen when they paste. CTRL+SHIFT+V does what you need here, but maybe there could be a way to surface this after the fact (""this text was just pasted with formatting - click here to remove"").",1457948632,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-347gkxmboadsdufxjprl,task_subcomment,NA
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,"In the public weekly triage on 2015-04-29, we discussed this task. We decided that this task is not the right approach as stated, so we rejected it for the quarter's blocking list.",1430334671,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-347gkxmboadsdufxjprl,task_subcomment,NA
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,">>! In T72519#768508, @Jdforrester-WMF wrote:
+> So this is ""if paste is an <h1> with id of firstHeading, instead paste a <p>""? OK.
+
+Well, this is the most frequent DWIM-style thing I can think of. Happens to me almost every time I edit an article.
+
+I can imagine other DWIMmy things, but resolving just the <h1> issue would be a huge improvement for me.
+
+And it probably shouldn't be a <p>, but simply match the surrounding markup, whether it's <h2>, link, etc.",1416846337,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-347gkxmboadsdufxjprl,task_subcomment,NA
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,"(In reply to Amir E. Aharoni from comment #0)
+> A thing that happens to me frequently is that I paste the title of another
+> article. When this happens, it's formatted as a heading. This is correct
+> HTML-wise, but it's never what I mean - I usually mean to paste it as plain
+> text or as a link.
+> 
+> It would be nice if the VE vould guess it.
+> 
+> A long shot, I know, but it happens to me a lot and I wanted to write it
+> down :)
+
+So this is ""if paste is an <h1> with id of firstHeading, instead paste a <p>""? OK.",1414011970,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-347gkxmboadsdufxjprl,task_subcomment,NA
+VisualEditor: Be able to make block-level edits (e.g. language of a <div> / <ol> not a <span>),"We'll need a way of editing these for the rare but useful block-level editing concepts that sometimes crop up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410033900,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-repvwi7xaiozmntsb6ul,task_description,open
+VisualEditor/WikiEditor: Consistent terminology,"The terminology between WikiEditor (aka ""Advanced toolbar"") and VisualEditor MUST be consistent so people will not get confused.
+
+For example in VisualEditor there is ""Cite"" menu, while in WikiEditor it is called ""Reference"" (Cite options in enwiki is only a gadget). It is super important, so we can guide new editors with same terminology. If you don't like the old terminology in some cases - use new one, but fix the WikiEditor to use it too.
+
+
+[Longer story]
+Today I participated in a workshop for new editors. We told the new editors they should use either VE or classic wikitext, and gave them printed instructions what to do, and they got confused of it...
+[The first time ever for me to open terminology bug, yay :)]
+
+Suggested terminology
+| VE | classic edit (including WikiEditor) | Suggestion | Description
+| Review your changes | Show changes | Show changes 
+| Cite | Reference | Reference | Cite may have disambig with quote. Both buttons are actually for adding reference/source
+| Media | Embedded file (title), Insert file (dialog title) | Media | Media is more specific than file (e.g it doesn't mean you can upload article as txt file)
+| Heading, Sub-heading 1, Sub-heading 2... | Heading, Level 2, Level 3 | Heading, Sub-heading 1, Sub-heading 2... 
+| Search pages (in link dialog) | Target page (in link dialog) | Target page 
+| External link (link dialog) | URL (link dialog) | External link | Not sure what is better. URL seems to be more technical",1409923320,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-jseusuuyitcemiu5pnrs,task_description,open
+VisualEditor: Vector's styling for H2 headers (with a line underneath) does not expand to full width when the context of the surrounding changes,"Screen cast of the sequence
+
+When editing a page with an infobox on the side, header lines that ended on the infobox does not expand to full width if content added above them pushes them down below the infobox. 
+
+The opposite works thouhg, i.e. deleting content so a header lines move up shortens the header line so that they do not overlap the infobox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14886}",1409835480,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-xissc7qsu7tkv7xx7nkr,task_description,resolved
+VisualEditor: Vector's styling for H2 headers (with a line underneath) does not expand to full width when the context of the surrounding changes,This appears to have been fixed some time ago.,1525335811,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-xissc7qsu7tkv7xx7nkr,task_subcomment,NA
+"VisualEditor: Cursor jumps to the start of the line, if link and Language style text present.","screenshot
+
+1> open a page in VE, insert a link. And after a space or two, insert some Language style text. 
+2> Now place the cursor at the end of the line and move along the line, the cursor jumps to the start of the line when it reaches the first character of the language style text .See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14760}",1409756940,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-xigwlc2e3gsxx4kbk5ix,task_description,open
+"VisualEditor: Cursor jumps to the start of the line, if link and Language style text present.","Confirmed. The structure of a line is like the following:
+*link* some text *lang text*
+
+A cursor that moves from left to right(placed at the beginning of *link*) will go through the inserted link, then the text, and then through language style text. 
+
+A cursor that is placed at the end of  *lang text* and then moved from right to left, will jump to the beginning of the line - which is a bug. 
+
+There is a workaround for editing the text between a link and lang style text  - just place a cursor inside it.",1415827729,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xigwlc2e3gsxx4kbk5ix,task_subcomment,NA
+"VisualEditor: Cursor jumps to the start of the line, if link and Language style text present.",Environment- test2,1409757265,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-xigwlc2e3gsxx4kbk5ix,task_subcomment,NA
+"VisualEditor: Cursor jumps to the start of the line, if link and Language style text present.","so if i want to edit some text present in between a link and the language style text, i cannot do it.",1409757227,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-xigwlc2e3gsxx4kbk5ix,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors","{F14756}
+1> open a page in VE, insert a comment.
+2> Click to edit the comment and insert a link. Notice the link icon is selected in the toolbar, although no link gets inserted in the comment . Try the above steps, with Formula and text styles like Underline, Strikethrough. See screenshots.
+
+",1409755980,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_description,open
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors","I disagree. Disabling the surface (greyed out, like we do for dialogs) suggests the surface isn't active. Disabling individual tools (greyed out, like we do when the selection is a table range) suggests the tool can't work where the user believes the cursor is currently.",1447284297,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors"," Inspectors are non-modal so opening them keeps the selection in the surface, and so you can still use all the tools.
+
+Disabling the tools would suggest that the surface selection is no longer active which is not true.",1447284182,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors","Confirmed - as the attached screenshots indicate - link, and some style formats - e.g. Bold, Italic, Underline - make an impression that they can be applied to  Comments or Formulas. 
+
+IN fact, clicking Formatting options or insert link have no effect on inserted Comments or Formulas.",1415407832,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors",Environment-test2,1409757305,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors","Created attachment 16353
+screenshot2
+
+**Attached**: {F14757}",1409756023,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"Screenshot of embeded video
+
+I think it would be better to distinguish better videos and pictures:
+a) in media selection
+b) in the text itself
+
+a) if Id like to add video, I am not able to determine, which previous in media selections are videos and which not. Thus I must go to Wikimedia Commons anyway and add it like a unique filename.
+
+b) attached screenshot shows, I add somethink and it still looks like an image - even its a video file.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14720}",1409651580,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-4g6i4gjynjlxlyawm244,task_description,open
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"This is really two bugs, and should be split, but leaving for now…",1409670292,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"(In reply to Andre Klapper from comment #1)
+> Created attachment 16341 [details]
+> Screenshot from Firefox 31, no problems
+> 
+> Which browser and version is that (such information is always welcome)? No
+> problems here to get the ""Play"" button overlay with Firefox 31 on Linux, see
+> screenshot.
+
+But there is a small difference. Your screenshot is from ""read"" verstion, mine is from ""edit"".
+
+ 
+> Still, what's the usecase of knowing in VisualEditor if it's a video or
+> image? That you don't want to add another video if there is already one?
+
+Well, you want to know if you are adding video or image.
+
+**Attached**: {F14721}",1409662629,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"Sigh. VE! Confirming. I should get more coffee. 
+Sorry for all the noise. Ignore my last two comments please.
+
+Still, what's the usecase of knowing in VisualEditor if it's a video or image? That you don't want to add another video if there is already one?",1409658692,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,[Rephrasing bug summary; please insert browser & version there],1409658541,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"Created attachment 16341
+Screenshot from Firefox 31, no problems
+
+Which browser and version is that (such information is always welcome)? No problems here to get the ""Play"" button overlay with Firefox 31 on Linux, see screenshot.
+
+**Attached**: {F14721}",1409658504,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: There should be a link to the template page even if template description is available,"When a template doesn't have a description in TemplateData, a link is shown to the template's page in the Template namespace (using the visualeditor-dialog-transclusion-no-template-description message).
+
+This link is very useful.
+
+I don't see such a link when a template does have a description. Compare, for example, how adding {{Reflist}} is different from adding {{LGBT Welcome}}.
+
+For advanced users the description in TemplateData is not a replacement for the whole page, so there should always be a link to the template page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409644740,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-clgmrlcl24aptweuxikz,task_description,duplicate
+Make the CAPTCHA more visible when saving,"1. Sign up with a new username to a Wikimedia site.
+2. Edit an article and add an external link.
+3. Try saving.
+
+After entering an edit summary and pressing the button in the dialog, the dialog remains and the CAPTCHA is shown in its bottom. At least on my machine, I need to scroll down in the dialog to actually see the CAPTCHA. I saw new users puzzled over this - they thought that they already pressed the save button and couldn't understand why is the dialog still there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409596440,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_description,resolved
+Make the CAPTCHA more visible when saving,"Change 479197 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Move save error messages above save footer
+
+[[https://gerrit.wikimedia.org/r/479197]]",1546534542,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"|Before |After
+| {F27784473}|{F27784482}",1546532815,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"Change 479197 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Move save error messages above save footer
+
+[[https://gerrit.wikimedia.org/r/479197]]",1544619390,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"The order was switched in https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VisualEditor/+/335223/ when adding a slide transition, putting the messages under the footer - we should switch them back.",1544619356,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"VisualEditor doesn't have any magic way to bypass it, are you sure it saved successfully and that nothing else changed?",1462550661,PHID-USER-mvx4x7ywk2flsaku2dbk,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,">>! In T72266#1384881, @jayvdb wrote:
+> So the steps as an anon (should be the same?) are:
+> 1. Edit using VE as an anon http://enwp.org/User:Elitre/Sandbox?veaction=edit
+> 2. Add an EL http://blah.com/foo
+> 3. step through the save process
+I received a captcha when using the source editor but not with the visual editor.",1462504877,PHID-USER-ibbxmosfonhbbhdgkv52,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,">>! In T72266#1384974, @Amire80 wrote:
+> Try it on a smaller screen. A lot of people still use 1024×768 or even smaller screens.
+> 
+
+I get exactly the same result in an 800x600 window
+
+{F181476}
+
+> How about putting it above the edit summary or instead of it?
+
+My suggestion, would be to highlight the text-input-box, which is currently hard to detect underneath the CAPTCHA. 
+Not that the current wikitext version is much better...
+{F181482}
+
+
+Sidenote: There's also {T54133} which if implemented will help reduce the size of that entire save window (and also fix T50274 - the missing autocomplete dropdown of previously used editsummaries (if someone let's their browser remember form-history. madness!))
+
+",1434820094,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"Try it on a smaller screen. A lot of people still use 1024×768 or even smaller screens.
+
+How about putting it above the edit summary or instead of it?",1434791299,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,">>! In T72266#1384881, @jayvdb wrote:
+
+Hey, thanks a lot for testing!
+
+> So the steps as an anon (should be the same?) are:
+
+I assume so, since the captcha is triggered then as well.
+
+> 1. Edit using VE as an anon http://enwp.org/User:Elitre/Sandbox?veaction=edit
+> 2. Add an EL http://blah.com/foo
+> 3. step through the save process
+> 
+> It should show
+> ""Warning:
+> CAPTCHA: To edit this page, please enter the words that appear below in the box (more info):""
+> 
+> And image appears below it.
+> 
+> Ive tried in twice on Chrome and once on Firefox. Two times it worked; once when I tried it on Chrome (Fedora 20; 43.0.2357.81), the warning appeared and the image didnt.
+> 
+> The warning should not be shown until the image is shown, and if the image doesnt arrive, it should display an error message.
+
+I think this is a different issue then? (and maybe one with javascript?) Amir says that he needs to scroll down to see the captcha. In all my tests, the captcha is always immediately visible (as in Nick's second screenshot).
+Which OS do you have? Mine is Win 7 (I'll test in my Macbook Air later). 
+
+> 
+> Also, it never shows the 'refresh' link to get another CAPTCHA, which is often necessary when the CAPTCHA is unreadable.  I checked and the 'source editor' has that.  Probably a separate bug.
+
+",1434790656,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"The CAPTCHA is appearing in the visible area, for me. Only the previously visible licensing info (which needs to have been read before clicking ""Save"" anyway!) gets scrolled out of view:
+
+{F181350}
+{F181349}
+
+So possibly this particular task needs to be retitled or refined?
+
+I've confirmed there's no refresh. Filed as {T103227}",1434788475,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"So the steps as an anon (should be the same?) are:
+1. Edit using VE as an anon http://enwp.org/User:Elitre/Sandbox?veaction=edit
+2. Add an EL http://blah.com/foo
+3. step through the save process
+
+It should show
+""Warning:
+CAPTCHA: To edit this page, please enter the words that appear below in the box (more info):""
+
+And image appears below it.
+
+Ive tried in twice on Chrome and once on Firefox. Two times it worked; once when I tried it on Chrome (Fedora 20; 43.0.2357.81), the warning appeared and the image didnt.
+
+The warning should not be shown until the image is shown, and if the image doesnt arrive, it should display an error message.
+
+Also, it never shows the 'refresh' link to get another CAPTCHA, which is often necessary when the CAPTCHA is unreadable.  I checked and the 'source editor' has that.  Probably a separate bug.",1434786518,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"I haven't been successful so far in finding a way to replicate (I tested several times in these months and couldn't replicate in IE, FF, Opera or Chrome. TBH, rather than creating a new account, I just use incognito window because I was testing a report from an IP user).
+I'm inclined to think that this may have been fixed by some design changes, but if it's still occurring for any of you and you can please post details of how you manage to reproduce it, I'd be happy to mark it as a ""blocker"". ",1434783341,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"I see closed tasks T52356 and T64766, but no other tasks relating to CAPTCHA, either open or closed.  Is this well covered by test scenarios?",1434768391,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"If VE is going to be rolled out to new editors, surely this must be a high priority?
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29#Gradually_enabling_VisualEditor_for_new_accounts",1434767314,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Bugzilla: Create keyword for usability,"The design and accessibility keywords aren't sufficient to cover cases where usability is the main hurdle.
+
+Be it an existing implementation that is hard to use and needs input to improve it, or a new feature/bug that is blocked on having an intuitive interface.
+
+In cleaning up bugs I often see this word in the title but would be interested in giving it its own keyword for interested parties (especially the Wikimedia UX team) to look at.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1409582520,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cqzkozq3w62lx7y4ycf7,task_description,declined
+Bugzilla: Create keyword for usability,My main question was how/why the design keyword is not sufficient and what's the differentiation that users would need to understand to set those two keywords correctly.,1409601718,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-cqzkozq3w62lx7y4ycf7,task_subcomment,NA
+Bugzilla: Create keyword for usability,"(In reply to Andre Klapper from comment #1)
+> I'm against this.
+> I have not seen a single bugtracker where users understood the narrow frame
+> of ""usability"". Instead, everything was randomly tagged with that keyword.
+> ""The server was down so I couldn't use it, hence a usability issue"" style.
+> 
+> In my understanding, an intuitive interface needs proper design. 
+> If the ""design"" keyword is not sufficient, please elaborate why that is the
+> case.
+
+One could make the same argument about lots of components and keywords (accessibility, design, javascript, parser, i18n; VisualEditor; Page editing; Any of those will be affected by other factors). I don't see how it's relevant that users may use it incorrectly. That happens all the time. That's why we triage bugs.
+
+Anyway, not my problem.",1409588985,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cqzkozq3w62lx7y4ycf7,task_subcomment,NA
+Bugzilla: Create keyword for usability,"I'm against this.
+I have not seen a single bugtracker where users understood the narrow frame of ""usability"". Instead, everything was randomly tagged with that keyword. ""The server was down so I couldn't use it, hence a usability issue"" style.
+
+In my understanding, an intuitive interface needs proper design. 
+If the ""design"" keyword is not sufficient, please elaborate why that is the case.",1409588491,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-cqzkozq3w62lx7y4ycf7,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","**Author:** `bsitu`
+
+**Description:**
+It throws invalid workflow exception
+
+---
+See {T88908}.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1409272980,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_description,resolved
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","I think some assumptions may be wrong here: Flow doesn't need Parsoid because we integrate with VE.
+
+As you may know, Flow is (currently) able to store content in either wikitext or html.
+In production, we chose to store data in html, so that we need less resources to keep recompiling the wikitext to html when the page needs to be displayed.
+Parsoid is indeed resource-intensive, but less so than the alternative of converting all wikitext to html for every request.
+
+In this scenario (storing html), we need Parsoid to make it possible to edit things (in wikitext) that have been stored in html: plain old PHP parser can't convert html to wikitext.
+Since we recently added VE integration, Flow also needs Parsoid to convert from VE back to wikitext editor.
+The reason we *need* Parsoid (in production) is not VE, but wikitext-editing. Actually, we wouldn't need Parsoid if we *only* supported VE (we could just store VE's html output).
+
+If you don't want to use Parsoid, you (currently) can, but:
+* you have to store content in wikitext & convert to html for every request (will need lots more CPU, depending on amount of requests)
+* you can't use VE (since we can't convert the html back to wikitext)
+
+We currently still support wikitext storage/non-Parsoid (in part because we simply have to: jenkins isn't set up to let us connect to Parsoid yet) although it's suboptimal (see above).
+We must face that it's a burden to maintain & we just can't test everything all the time. Things may be broken from time to time.
+
+We don't need Parsoid because we have resources to burn, or because we want to push VE; those 2 would be easier without Parsoid & compromising on other things.
+We choose to use Parsoid because it is the best (only) solution to be more conservative on resources (store in html) & still support editing one's post in wikitext.
+
+AFAIK, there are no concrete plans to abandon wikitext storage/non-Parsoid support yet.
+I think we can put this discussion to rest at least until we can contact Parsoid on jenkins, which may or may not be awhile.
+I'm also going to close {T88908}",1429770288,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1230034, @Mattflaschen wrote:
+>>>! In T72148#1205755, @Arcane21 wrote:
+>> Parsoid is extremely resource intensive, even on small setups, and while the WMF may be able to easily ignore this, many smaller non WMF setups would not be able to do so, and I have to confess I'm greatly interested in introducing Flow to the Orain wiki farm (which I serve at as a staff member), but I'd rather we not have to have to acquire much more resources than we use currently to support Flow.
+> 
+> To determine whether it's overly resource-intensive, you would have to compare it to other software that does the same thing: Bidirectional conversion of editable HTML to wikitext.
+> 
+> The reason node.js was used for Parsoid is that investigation showed it was //far// more performant than the same thing would be in PHP.  There's no identical implementation of the current Parsoid in PHP (since no one chose to write one).  However, this has almost certainly not changed.
+> 
+>>>! In T72148#1211295, @FastLizard4 wrote:
+>> With a tool like VisualEditor, it's obvious why Parsoid needs to be required, but I don't see why Flow by itself //needs// to have access to the powerful parsing tools Parsoid provides, especially given that Parsoid is still experimental and is rapidly changing.
+> 
+> Though VisualEditor is not required (either for wiki operators installing Flow or for individual Flow end users), VE is a key part of the vision for Flow (that's why we use Parsoid to begin with).  That means, for example, we now use VE for previewing (so no preview without Parsoid). 
+
+As to the first issue, I understand that, but we don't WANT to have, need, or require VE at this time, just Flow, mostly because we don't want to be shackled to Parsoid, which we discovered would not scale well to our current resource infrastructure. The WMF can easily use it because frankly they've got resources to burn and them some, but Parsoid (the service backend) is costly to maintain in terms of memory and processor cycles, and while it may be a magical engine that solves a lot of the WMF's problems, it's a resource hog otherwise, and while it works great for VE and the WMF, and I don't dispute that, we and I'm certain almost every single smaller userbase with far less resources to burn does not want to be forced to use something that only the WMF is happy with.
+
+Forgive me if this sounds harsh, but I believe the WMF seems to be proceeding on the somewhat arrogant assumption that if they like something, the rest of the world should easily be able to adapt and emulate it if they want the same, even though the resources needed to maintain it aren't as plentiful on setups far smaller than the WMF's.
+
+Further, as you pointed out, Flow does not currently require it, and while Visual Editor needing Parsoid made sense from the get go (given its intended design and purpose), forcing Flow to conform to the same when it is not strictly required strikes me a little more than railroading non-WMF end users into using something they don't want simply because it make WMF users happy to do so.
+
+As to the second rebuttal, it merely proves my first point: VE is the WMF's baby, and the WMF is intent on forcing everything that hooks into it to use the same standards and nothing else, despite the inconvenience this places on those who do not wish the added expense of Parsoid when the optional hook in feature does not strictly require it.
+
+I understand the WMF wants to make their lives easier, and as a staff member on a wiki server setup myself, I'm sympathetic from an engineering standpoint. However, as an end user of MediaWiki and someone who has to help install, configure, and adjust settings on our setup to work nicely with anything we add, this would be expense in resources to add when as you pointed out it's not a strict requirement, and on a personal note, if adding Flow was merely adding the extension and running the update script without needing a backend that has no real reason to manacled to an extension that was not designed to strictly need it in the first place, I see no reason to make those like myself and others have to suffer Parsoid's presence at our expense when that could be avoided.
+
+I respectfully remind the WMF MediaWiki is global software, and that I feel the WMF should be mindful not all wiki farms and setups are as wealthy in processor and memory resources to burn to maintain the same configurations as the WMF, and since Parsoid is not needed for Flow (which has a negligible resource footprint without Parsoid in tests I have run so far), I see no reason to force others to use Parsoid only when they don't have to.
+
+I'm not opposed to a dual operation standard, in which Parsoid enabled setups can benefit if Parsoid is installed, but if it's not, then it should retain the non Parsoid mode for those who frankly have no desire or intention to ever use or enable Visual Editor.",1429761445,PHID-USER-iy4yqj4ftn74e3b5fy3e,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1205755, @Arcane21 wrote:
+> Parsoid is extremely resource intensive, even on small setups, and while the WMF may be able to easily ignore this, many smaller non WMF setups would not be able to do so, and I have to confess I'm greatly interested in introducing Flow to the Orain wiki farm (which I serve at as a staff member), but I'd rather we not have to have to acquire much more resources than we use currently to support Flow.
+
+To determine whether it's overly resource-intensive, you would have to compare it to other software that does the same thing: Bidirectional conversion of editable HTML to wikitext.
+
+The reason node.js was used for Parsoid is that investigation showed it was //far// more performant than the same thing would be in PHP.  There's no identical implementation of the current Parsoid in PHP (since no one chose to write one).  However, this has almost certainly not changed.
+
+>>! In T72148#1211295, @FastLizard4 wrote:
+> With a tool like VisualEditor, it's obvious why Parsoid needs to be required, but I don't see why Flow by itself //needs// to have access to the powerful parsing tools Parsoid provides, especially given that Parsoid is still experimental and is rapidly changing.
+
+Though VisualEditor is not required (either for wiki operators installing Flow or for individual Flow end users), VE is a key part of the vision for Flow (that's why we use Parsoid to begin with).  That means, for example, we now use VE for previewing (so no preview without Parsoid). ",1429757327,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",Changing my token to make clear my opinion is the same as @Arcane21's one.,1429284851,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","This issue has been fixed for awhile now. AFAIK, everything currently works in wikitext storage.",1429264967,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","I definitely see both sides of the argument here.  I agree that, in most cases, maintaining two versions of key parts of a single piece of software is quite costly.  However, as a small wiki operator myself, I feel that at this point, restricting Flow to Parsoid-only would only hurt wide adoption, because at this point, Parsoid is still rather experimental (definitely at least ""Beta"" software).
+
+With a tool like VisualEditor, it's obvious why Parsoid needs to be required, but I don't see why Flow by itself //needs// to have access to the powerful parsing tools Parsoid provides, especially given that Parsoid is still experimental and is rapidly changing.  At least until Parsoid becomes stable and ready for mass release, I would say that giving sysadmins the opportunity to be able to use Flow without needing Parsoid is important, even if it does increase the cost of Flow development.",1429150349,PHID-USER-q6nnw3r5axkpgj5uftsh,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1205608, @Mattflaschen wrote:
+>>>! In T72148#1179439, @Arcane21 wrote:
+>> I strongly disagree with dropping non Parsoid support. Parsoid is incredibly costly, and while I would love to switch my LQT enabled wiki to Flow, I have no desire to install costly backend software to do so, nor would many smaller non WMF wikis with more limited resources, and if it means it performs less optimally, I would consider that an acceptable compromise to retain non Parsoid functionality.
+> 
+> Costly in what way, exactly?
+> 
+> * Requires a lot of man-hours to install?
+> * Difficult to maintain?
+> * Requires high-end services or equipment to run?
+> 
+> Maybe there's a way Parsoid could be easier for you to use.
+> 
+> The main reason we want to remove support for non-Parsoid is that it is costly (mainly in software engineer time) to maintain two versions of key parts of the code.
+
+Parsoid is extremely resource intensive, even on small setups, and while the WMF may be able to easily ignore this, many smaller non WMF setups would not be able to do so, and I have to confess I'm greatly interested in introducing Flow to the Orain wiki farm (which I serve at as a staff member), but I'd rather we not have to have to acquire much more resources than we use currently to support Flow.
+
+I have also tested Parsoid on a localhost configuration, and I found Parsoid absorbed over half a gigabyte of resources just to function (on a Windows setup, have not fully evaluated this on a Linux at present), and I'm not sanguine on trying to use Parsoid on a wider scale given this resource drain on a small scale.
+
+Also, while I understand keeping around two sets of code is indeed costly to the WMF, I do not see the harm in maintaining such code if it means the extension can be used on non Parsoid enabled setups, as, to be blunt, the WMF provided MediaWiki to the world for everyone to use, and while I understand the WMF wants to tailor this software to fit it's current needs, it could be of great benefit to non-WMF users, and I see no good reason to throw those use cases under the bus just to make one organization happy.
+
+Also, since it is intended to succeed LiquidThreads, and many LQT users on non-WMF setups may wish to migrate to Flow like my organization, I don't see the point in making their task in doing so harder by forcing them to add backend software that consumes a ton of overhead just to use the successor to LQT.",1428984868,PHID-USER-iy4yqj4ftn74e3b5fy3e,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1179439, @Arcane21 wrote:
+> I strongly disagree with dropping non Parsoid support. Parsoid is incredibly costly, and while I would love to switch my LQT enabled wiki to Flow, I have no desire to install costly backend software to do so, nor would many smaller non WMF wikis with more limited resources, and if it means it performs less optimally, I would consider that an acceptable compromise to retain non Parsoid functionality.
+
+Costly in what way, exactly?
+
+* Requires a lot of man-hours to install?
+* Difficult to maintain?
+* Requires high-end services or equipment to run?
+
+Maybe there's a way Parsoid could be easier for you to use.
+
+The main reason we want to remove support for non-Parsoid is that it is costly (mainly in software engineer time) to maintain two versions of key parts of the code.",1428979580,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","I strongly disagree with dropping non Parsoid support. Parsoid is incredibly costly, and while I would love to switch my LQT enabled wiki to Flow, I have no desire to install costly backend software to do so, nor would many smaller non WMF wikis with more limited resources, and if it means it performs less optimally, I would consider that an acceptable compromise to retain non Parsoid functionality.
+
+LQT was thrown under the bus, more or less, because the WMF found Flow to be a better long term solution, and I would rather the WMF take more time to ensure non Parsoid fallback compatibility (which is advantageous to the WMF if Parsoid fails for some reason) than to eliminate any failsafes and disadvantage any other wikis wishing to use Flow.",1428100837,PHID-USER-iy4yqj4ftn74e3b5fy3e,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","I strongly disagree with dropping non Parsoid support. Parsoid is incredibly costly, and while I would love to switch my LQT enabled wiki to Flow, I have no desire to install costly backend software to do so, nor would many smaller non WMF wikis with more limited resources, and if it means it performs less optimally, I would consider that an acceptable compromise to retain non Parsoid functionality.",1428100573,PHID-USER-iy4yqj4ftn74e3b5fy3e,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1072830, @Ricordisamoa wrote:
+>>>! In T72148#730402, @coren wrote:
+>> In my specific usecase I was able to switch to html format at little cost or effort; but it would seem to me that a hard dependency on Parsoid is going to severely restict the number of non-WMF sites who can deploy that otherwise very valuable extension.
+>> 
+>> I don't get to set priorities on dev time, but I'm pretty sure that dropping wikitext markup would be a Bad Idea™
+> 
+> Sure. Medium and small-sized wikis may just want a better discussion system without being willing to install Parsoid or VisualEditor.
+
+The problem is, no one is testing the non-Parsoid configuration much.  As far as I know, there is no automated browser testing for that configuration.  And I don't even know of anyone regularly using wikis with the non-Parsoid configuration and reporting back (informally or formally).
+
+It's better to have one well-tested path, then two paths, one of which sorta works but has random breakage that doesn't immediately get caught.  This also requires maintaining extra code.
+
+That's why we are leaning towards eliminating it ({T88908}).",1425182896,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1072844, @EBernhardson wrote:
+> MediaWiki is moving to soa, parsoid will likely be one of several services wikis require for various features.  The best solution is going to be working with the SOA team to ensure making services available works with your use case.
+
+The effort in librarization is valuable, but it seems that just running a simple MediaWiki is going to get harder and harder...",1425045094,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","MediaWiki is moving to soa, parsoid will likely be one of several services wikis require for various features.  The best solution is going to be working with the SOA team to ensure making services available works with your use case.",1425010728,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#730402, @coren wrote:
+> In my specific usecase I was able to switch to html format at little cost or effort; but it would seem to me that a hard dependency on Parsoid is going to severely restict the number of non-WMF sites who can deploy that otherwise very valuable extension.
+> 
+> I don't get to set priorities on dev time, but I'm pretty sure that dropping wikitext markup would be a Bad Idea™
+
+Sure. Medium and small-sized wikis may just want a better discussion system without being willing to install Parsoid or VisualEditor.",1425008341,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","**gerritadmin** wrote:
+
+Change 169711 had a related patch set uploaded by Matthias Mullie:
+(bug 70148) Fix new topic creation with wikitext storage
+
+https://gerrit.wikimedia.org/r/169711",1414593342,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","In my specific usecase I was able to switch to html format at little cost or effort; but it would seem to me that a hard dependency on Parsoid is going to severely restict the number of non-WMF sites who can deploy that otherwise very valuable extension.
+
+I don't get to set priorities on dev time, but I'm pretty sure that dropping wikitext markup would be a Bad Idea™",1409285431,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","https://www.mediawiki.org/wiki/Extension:Flow#Dependencies mentions this bug, and emphasizes the html format with Parsoid is what WMF uses and tests.
+
+We could drop wgFlowCoptentFormat = wikitext if it makes life easier...",1409279767,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+data labels in imageinfo API don't make sense,"The data currently returned by the imageinfo API assigns the author to ""artist"" and the source to ""credit"". Both of these are incorrectly labeled. In particular these labels make it difficult to figure out the proper attribution for the image, as it sounds like you should use ""credit"", but you should actually use ""artist"".
+
+https://en.m.wikipedia.org/w/api.php?action=query&format=json&prop=imageinfo&titles=File%3ALiber_Eliensis%2EPNG&iiprop=url%7Cextmetadata
+
+--------------------------
+**Version**: master
+**Severity**: normal",1408730400,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-5fxfxopay5yizt3sptbe,task_description,declined
+data labels in imageinfo API don't make sense,"I'll be bold and decline. With file metadata being migrated to WikibaseMediaInfo, I see little value on working on CommonsMetadata.",1603828394,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Change 231505 abandoned by Gergő Tisza:
+Rename extmetadata labels to be more intuitive
+
+Reason:
+Structured media info will obsolete this extension (or at least its current output data structure) soon.
+
+[[https://gerrit.wikimedia.org/r/231505]]",1531993101,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Tgr's patch has been sitting in Gerrit for four months without comments / review. 
+How to proceed / who to review?",1450267728,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Change 231505 had a related patch set uploaded (by Gergő Tisza):
+Rename extmetadata labels to be more intuitive
+
+[[https://gerrit.wikimedia.org/r/231505]]
+",1439545311,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"@Tgr: I would suggest changing:
+* Artist to Author
+* Credit to FileSource (https://gerrit.wikimedia.org/r/#/c/107368)
+* ImageDescription to FileDescription
+And possibly:
+* UsageTerms to LicenseLongName",1437767921,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"@Tgr: I would suggest changing:
+* Artist to Author
+* Credit to FileSource (https://gerrit.wikimedia.org/r/#/c/107368)
+* ImageDescription to FileDescription
+The rest look fine to me.",1437767838,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Still, the first step should be to come up with the names :)",1434557212,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"MedaViewer, OCG, MobileFrontend/mobile apps, VisualEditor are the big ones AFAIK. There are a bunch of gadgets, bots and other tools - [[ https://github.com/search?utf8=%E2%9C%93&q=extmetadata+imageinfo&type=Code&ref=searchresults | this search ]] should find the ones on GitHub. We could also just log useragents for a while.",1434557093,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"https://gerrit.wikimedia.org/r/#/c/107368/ mentions updaing ""all known clients"". Do we already have a list? A first step seems to make one.",1434543973,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Announce it on [[http://lists.wikimedia.org/pipermail/mediawiki-api-announce/|mediawiki-api-announce]], if you can't maintain BC for the old names.",1418056473,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Given how much the structured data project lags behind, I would be inclined to fix this now. @Anomie, is there any guidance on how such a breaking change to the API should be handled?",1417810294,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"See T59189#605222 for the rationale behind the field names. In hindsight, I agree it was the wrong decision, but I am not sure it is worth changing all the field names now - the API has other serious limitations and will be eventually superseded by the structured data API when wikibase will be introduced to Commons.",1508863651,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"See bug 57189 comment 1 for the rationale behind the field names. In hindsight, I agree it was the wrong decision, but I am not sure it is worth changing all the field names now - the API has other serious limitations and will be eventually superseded by the structured data API when wikibase will be introduced to Commons.",1408741667,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Not an API bug, it's just returning what deeper layers of MediaWiki give it. It sounds like you want the CommonsMetadata extension.",1408732994,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+MediaWiki should not expose any UI elements which require JavaScript when it is off (tracking),"**Author:** `gryllida`
+
+**Description:**
+from bug 54730#c3
+>The general design principle in MediaWiki is to only show functional user interface elements (for example, unprivileged users are not shown a delete tab or a protect tab)
+
+I would like MediaWiki to not expose any features which require JavaScript when it is off.
+
+This means, for instance, not showing visual editor's edit tab, bug 69779  (noting 'requires javascript' where necessary in the beta tab).
+
+I hope to succeed in making this a tracking bug for enforcing the above-quoted design for the ""no JS enabled"" case.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: enhancement",1408616100,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-srm34yak2agbaxyhgjji,task_description,resolved
+MediaWiki should not expose any UI elements which require JavaScript when it is off (tracking),"It certainly should not expose dead links (e.g. it would be bad if you saw a VE edit link, and clicking it did nothing).  We're fixing a similar issue in a non-deployed feature right now, in fact.
+
+My understanding is that with bug 69779, you are requesting that ""this feature requires js"" is shown especially when JS is disabled.  This makes sense, and the current intended behavior (as far as I can tell from reading the code) is that it shows only when JS is disabled.  As far as I can tell, it *does* show when JS is disabled.  You have not replied there to my latest comment and screenshot.
+
+There is a glitch where it *also* shows when JS is enabled (bug 69823) in some cases.
+
+Note, I don't think this preference behavior is clearly described by ""not expose any features"".  We want to make them aware (could be described as ""expose"") of JS-only features, but make it clear such feature can not be used without JS.
+
+Tweaking the title and adding a depends accordingly.",1408676859,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-srm34yak2agbaxyhgjji,task_subcomment,NA
+MediaWiki should not expose any UI elements which require JavaScript when it is off (tracking),[There are probably quite some open tickets already that could be marked as blocking this one],1408620867,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-srm34yak2agbaxyhgjji,task_subcomment,NA
+MediaWiki should not expose any UI elements which require JavaScript when it is off (tracking),"**gryllida** wrote:
+
+Which is probably stupid (visualeditor already does not show the edit tab when js is off; I misread earlier)",1408616344,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-srm34yak2agbaxyhgjji,task_subcomment,NA
+"VisualEditor:  Categories go at the bottom, so please place the cursor above the categories","Especially when there are only categories on the page, it does not appear to be possible to put text above the categories.  The result is things like this:
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=122314&oldid=51987
+
+which is not normally wanted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1408562280,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-zk5ndm764k2ntbyz65kz,task_description,open
+"VisualEditor:  Categories go at the bottom, so please place the cursor above the categories","The saved page will display the text above categories. Only ""Difference between revisions"" misleadingly places the typed text under the categoreis.  ",1424825560,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-zk5ndm764k2ntbyz65kz,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Alternative: {T254277}
+
+If the ""View history"" tab changes size such that becomes too large where it before was not, an endless animation loop of collapse-expand-collapse-etc can be triggered. A resize could be caused by an ordinary zoom (frequently resizing the pixel width of the element by a few pixels), by a change in browser text size preferences (likely to significantly change the width), or by a user script modifying the text content of the element.
+
+This appears to be caused by expandCondition in Vector.js using a cached version of the element's width (collapsibleTabs.data's expandedWidth passed as the eleWidth argument), while collapseCondition is checking .width() each time.
+
+This happens when you enable `Editing mode: show both tabs is enabled in preferences` in VisualEditor and visit https://www.mediawiki.org/wiki/User:Martin_Urbanec?uselang=fr at certain screen resolutions. Demonstrated in image below:
+{F5061717}
+
+== Solutions
+
+#### Option 1 - Remove the animation and fix the collapsibletabs code:
+
+Rationale: The animation plays at times when it's not meaningful, eg. after page load. The tabs should be collapsed immediately, without animation.
+About half of the code is removed, including callbacks, resulting in a simple, less error-prone logic.
+Analysis of the bug, solution:  T71729#6183821 **Remove animation**
+
+#### Option 2 - Keep the animation, fix the collapsibletabs code:
+
+Rationale: Keeps the old functionality (animation) while safeguarding against the oscillation.
+Solution:  T71729#6183821 **Easy fix**
+
+#### Option 3 - Make the tabs responsive
+
+Rationale: No more collapsing, the tabs wrap into any number of rows.
+Mostly CSS solution with a one-liner resize event handler.
+Solution detailed: T71729#6183822 
+
+
+
+== Update 2020-05-30
+
+This bug resurfaced as a more prominent regression after the #mw1.35.0-wmf.34 deployment:
+{T253819}
+The difference is: the ""More"" (""Plus"" / ""Mehr"") menu is //not// visible:
+{F31848748}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408416060,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_description,resolved
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",I can't replicate this any more. Please reopen with new replication steps if it's still occurring. I know there was lots of other related issues but they would likely benefit from a dedicated task at this point.,1633640757,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","(The previous patch fixes the latest issue where this problem occurred all the time; the older issue where this problem occurs rarely ""if a tab's width changes after initial page load"" still exists.)",1604911876,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",[Resetting assignee due to inactive user account],1604831127,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://sal.toolforge.org/log/fQ44ZnUBgTbpqNOm4WWZ} [2020-10-26T18:43:25Z] <catrope@deploy1001> Synchronized php-1.36.0-wmf.14/skins/Vector/: Fix logic in collapsibleTabs code (T71729) (duration: 00m 58s)",1603737805,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 636377 **merged** by jenkins-bot:
+[mediawiki/skins/Vector@wmf/1.36.0-wmf.14] Fix logic in collapsibleTabs code
+
+https://gerrit.wikimedia.org/r/636377",1603737506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 636377 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
+[mediawiki/skins/Vector@wmf/1.36.0-wmf.14] Fix logic in collapsibleTabs code
+
+https://gerrit.wikimedia.org/r/636377",1603734524,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 636068 **merged** by jenkins-bot:
+[mediawiki/skins/Vector@master] Fix logic in collapsibleTabs code
+
+https://gerrit.wikimedia.org/r/636068",1603474357,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 636068 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
+[mediawiki/skins/Vector@master] Fix logic
+
+https://gerrit.wikimedia.org/r/636068",1603472347,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",oh.. whoops.,1603472288,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","`mw.util.showPortlet( 'p-cactions' )` reveals the portal. If it's not displaying  I suspect 6d967ed4a8c is more to blame here.
+",1603471990,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","`mw.util.showPortlet( '#p-cactions' )` doesn't seem to be revealing the more menu as it should do so I suspect 6d967ed4a8c is more to blame here.
+",1603471940,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","The current issue is distinct and maybe we should file a separate task. Whenever any tabs should be collapsed into the ""More"" menu, and the menu isn't already visible, it doesn't actually appear, and the tabs animate back and forth forever.
+
+I did a git-bisect and this bug seems to have been introduced in {711a41812aac6fe91432d3733805f3d96b7b90a0}, although I haven't tried to figure out what about that code causes it.",1603471691,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This is an extremely large number of duplicates, for a task that has been sitting here quietly for years with barely anyone ever noticing the problem.
+
+Could something have changed recently in Vector to make this scenario more common?",1603471088,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","To clarify the reading web team that I am tech lead for,  who are the maintainers of this skin (and legacy version) talked through this task yesterday in our team time meeting. It was agreed that we don't want to make any changes to legacy mode at this point so we will keep the code for now. In general we are not working on legacy bugs as part of the desktop improvements project - the project is considered frozen with the exceptions of changes that aid the new modern experience we are building. We decided to retain the collapsible tabs code and this bug. In future we'd like to rewrite and improve this code but right now we don't believe that fits into our current goals.
+
+I am thus punting this back to the backlog. This task about fixing the existing bug remains stalled on a decision in T254277 which we hope to revisit further into the project. If we decide not to review it, we may decide to rewrite it or simply continue to maintain it as we do now (in which case this task can be unstalled and worked on).
+",1591380797,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Thanks for the explanation, @matmarex. I believe the Readers-Web-Team is a developer team, at least in the context of DI, so calling it a maintenance team was very confusing to me.
+
+>>! In T71729#6194759, @Jdlrobson wrote:
+> The maintenance team has no interest in working or review patches for this task right now 
+@Jdlrobson  I was trying to understand this sentence. As you are the one reviewing the patches mostly (at least mine), referring to yourself wouldn't be confusing.
+I understand you prefer to axe the tab collapsing instead of fixing it. I've detailed why that's not feasible currently and for quite some time. 
+As I said if and **when** this patch is requested, I'll do it.
+
+> ... is likely to be wasted effort and I know you don't like to do that. 
+
+We should chat sometime so you can get to know me better. I've seen many times in the months we've been collaborating that my values and motivations are misunderstood or assumed to be something it is not.",1591374434,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","There is no ""maintenance team"", Jon was just referring to the Readers Web team (including himself), who maintain the Vector skin.",1591362627,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6195375, @Aklapper wrote:
+>>>! In T71729#6194862, @Demian wrote:
+>> Is that the release engineering team?
+> No it's not.
+Which one it is? Can I ask?
+",1591363925,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6195375, @Aklapper wrote:
+>>>! In T71729#6194862, @Demian wrote:
+>> Is that the release engineering team?
+> No it's not.
+Which one it is? Should I guess or can I ask?
+",1591350026,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6194862, @Demian wrote:
+> Is that the release engineering team?
+
+No it's not.
+
+> Spikes? Do you mean the 3 regressions in one week?
+
+No but [spikes](https://phabricator.wikimedia.org/maniphest/query/MlM0ymF.hVn7/#R).",1591344701,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6194759, @Jdlrobson wrote:
+> @demian please don't work on this task. Any effort expended here right now is likely to be wasted effort 
+Thanks for informing me. This is what I expected.
+
+> The maintenance team has no interest in working or review patches for this task right now 
+maintenance team? Never heard of them. Is that the release engineering team?
+
+> after our recent spikes.
+Spikes? Do you mean the 3 regressions in one week? (T249372)
+",1591316243,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",@demian please don't work on this task. Any effort expended here right now is likely to be wasted effort and I know you don't like to do that. The maintenance team has no interest in working or review patches for this task right now after our recent spikes.,1591313755,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","3 different solutions detailed above and in the description. I'll do the patch in a day, if it is decided to accept any of these fixes.",1591311231,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 601368 abandoned by Jdlrobson:
+[legacy] Drop the collapsibleTabs code
+
+Reason:
+To be reconsidered at a later date.
+
+[[https://gerrit.wikimedia.org/r/601368]]",1591291387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",I've opened up T254277 to propose removing this code.,1591127145,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Solution
+
+> The code is definitely not going to be run in the new Vector and is pretty complex for what it does. 
+
+It's mostly essential complexity for the functionality that was intended. The code is actually good for practicing code reading skills: one aspect of mediawiki code that I appreciate is that a big percentage of the code is diligently written and formatted, resulting in very well readable code. Above the average of what I usually encounter.
+
+I see 3 solutions. 
+**1st solution** completely removes this code (collapsing tabs). In this case the tabs will wrap in narrow windows. With the SearchBox moved to the header this will affect windows narrower by about 320px than in legacy, but still not avoidable, it can still happen at above 900px width:
+{F31850806}
+Therefore the tabs row needs a proper responsive layout that can wrap properly. This means having `#left-navigation` and `#right-navigation` only in `#mw-head`. With the personal menu moved to the header this will be the case. I've submitted numerous patches in the past months to do this refactor and layout with flexbox.
+
+Further complication will be to move the content down when the tabs wrap. With the tabs being absolute positioned now, this would require JS. A compromise that I wouldn't do, but it's an acceptable compromise, imho.
+Alternatively, the tabs can be positioned above the content with flexbox (problem with some basic browsers that should be auto-updated), or the tabs can be before the content in the HTML.
+
+**2nd solution** only removes the animation, but does collapse the tabs: I've detailed this as ""Easy fix"" in the Analysis section, above.
+
+> The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.
+
+For legacy 2 solutions can be applied: **2nd solution** which only removes the animation (""Easy fix""), **3rd solution** that keeps the animation (""complicated fix""), both detailed in Analysis section, above.
+
+I'm happy to submit a patch for any of these solutions, if you wish.",1591163582,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Solution
+
+> The code is definitely not going to be run in the new Vector and is pretty complex for what it does. 
+
+It's mostly essential complexity for the functionality that was intended. The code is actually good for practicing code reading skills: one aspect of mediawiki code that I appreciate is that a big percentage of the code is diligently written and formatted, resulting in very well readable code. Above the average of what I usually encounter.
+
+I see 3 solutions. 
+**1st solution** completely removes this code (collapsing tabs). In this case the tabs will wrap in narrow windows. With the SearchBox moved to the header this will affect windows narrower by about 320px than in legacy, but still not avoidable, it can still happen at above 900px width:
+{F31850806}
+Therefore the tabs row needs a proper responsive layout that can wrap properly. This means having `#left-navigation` and `#right-navigation` only in `#mw-head`. With the personal menu moved to the header this will be the case. I've submitted numerous patches in the past months to do this refactor and layout with flexbox.
+
+Further complication will be to move the content down when the tabs wrap. With the tabs being absolute positioned now, this would require JS. A compromise that I wouldn't do, but it's an acceptable compromise, imho.
+Alternatively, the tabs can be positioned above the content with flexbox (problem with some basic browsers that should be auto-updated), or the tabs can be before the content in the HTML.
+
+**2nd solution** only removes the animation, but does collapse the tabs: I've detailed this as ""Easy fix"" in the Analysis section, above.
+
+> The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.
+
+For legacy 2 solutions can be applied: 2nd solution which only removes the animation (""Easy fix""), 3rd solution that keeps the animation (""complicated fix""), both detailed in Analysis section, above.
+
+I'm happy to submit a patch for any of these solutions, if you wish.",1591163563,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Solution
+
+> The code is definitely not going to be run in the new Vector and is pretty complex for what it does. 
+
+It's mostly essential complexity for the functionality that was intended. The code is actually good for practicing code reading skills: one aspect of mediawiki code that I appreciate is that a big percentage of the code is diligently written and formatted, resulting in very well readable code. Above the average of what I usually encounter.
+
+I see 3 solutions. 1st one completely removes this code (collapsing tabs). In this case the tabs will wrap in narrow windows. With the SearchBox moved to the header this will affect windows narrower by about 320px than in legacy, but still not avoidable, it can still happen at above 900px width:
+{F31850806}
+Therefore the tabs row needs a proper responsive layout that can wrap properly. This means having `#left-navigation` and `#right-navigation` only in `#mw-head`. With the personal menu moved to the header this will be the case. I've submitted numerous patches in the past months to do this refactor and layout with flexbox.
+
+Further complication will be to move the content down when the tabs wrap. With the tabs being absolute positioned now, this would require JS. A compromise that I wouldn't do, but it's an acceptable compromise, imho.
+Alternatively, the tabs can be positioned above the content with flexbox (problem with some basic browsers that should be auto-updated), or the tabs can be before the content in the HTML.
+
+2nd solution only removes the animation, but does collapse the tabs: I've detailed this as ""Easy fix"" in the Analysis section, above.
+
+> The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.
+
+For legacy 2 solutions can be applied: 2nd solution which only removes the animation (""Easy fix""), 3rd solution that keeps the animation (""complicated fix""), both detailed in Analysis section, above.
+
+I'm happy to submit a patch for any of these solutions, if you wish.",1591079087,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Solution
+
+> The code is definitely not going to be run in the new Vector and is pretty complex for what it does. 
+
+It's mostly essential complexity for the functionality that was intended. The code is actually good for practicing code reading skills: one aspect of mediawiki code that I appreciate is that a big percentage of the code is diligently written and formatted, resulting in very well readable code. Above the average of what I usually encounter.
+
+I see 3 solutions. 1st one completely removes this code (collapsing tabs). In this case the tabs will wrap in narrow windows. With the SearchBox moved to the header this will affect windows narrower by about 320px than in legacy, but still not avoidable, it can still happen at above 900px width:
+{F31850806}
+Therefore the tabs row needs a proper responsive layout that can wrap properly. This means having `#left-navigation` and `#right-navigation` only in `#mw-head`. With the personal menu moved to the header this will be the case. I've submitted numerous patches in the past months to do this refactor and layout with flexbox.
+
+Further complication will be to move the content down when the tabs wrap. With the tabs being absolute positioned now, this would require JS. A compromise that I wouldn't do, but it's an acceptable compromise, imho.
+Alternatively, the tabs can be positioned above the content with flexbox (problem with some basic browsers that should be auto-updated), or the tabs can be before the content in the HTML.
+
+2nd solution only removes the animation, but does collapse the tabs: I've detailed this as ""Easy fix"" in the Analysis section, above.
+
+> The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.
+
+For legacy 2 solutions can be applied: 2nd solution which only removes the animation (""Easy fix""), 3rd solution that keeps the animation (""complicated fix""), both detailed in Analysis section, above.
+",1591079035,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Analysis
+
+I think this requires a bit more thought. A quick look at the code reveals one design mistake that starts the infinite cycle: [[ https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/601368/5/resources/skins.vector.legacy.js/collapsibleTabs.js#b147 | line 147 ]] calling
+`rAF( $.collapsibleTabs.handleResize );`
+after the animation (hiding/showing ONE tab) finishes. I assume to hide another tab, if necessary.
+* The immediate issue: does not check if the direction changes (hide -> show -> hide). **Easy fix**: on resize event save direction, on animation end check the direction is the same for the next tab to be hidden/shown.
+** **Remove animation.** It's even easier to fix if the animation is removed: a loop can do (hide -> get size -> repeat if needed) in one cycle, the recalculation after the animation becomes unnecessary, which is the source of the design error.
+* The design issue: the number of hidden tabs should be decided **only once**, upon receiving the `resize` event. 
+** That's a more **complicated fix**, `collapseCondition` needs to be replaced by a logic that iterates the tabs and marks for hiding as many tabs as necessary to fit the available width.
+** Without animation it's unnecessary to be this elaborate.
+",1591163748,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Analysis
+
+I think this requires a bit more thought. A quick look at the code reveals one design mistake that starts the infinite cycle: [[ https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/601368/5/resources/skins.vector.legacy.js/collapsibleTabs.js#b147 | line 147 ]] calling
+`rAF( $.collapsibleTabs.handleResize );`
+after the animation (hiding/showing ONE tab) finishes. I assume to hide another tab, if necessary.
+* The immediate issue: does not check if the direction changes (hide -> show -> hide).
+** **Easy fix**. It's even easier to fix if the animation is removed: a loop can do (hide -> get size -> repeat if needed) in one cycle, the recalculation after the animation becomes unnecessary, which is the source of the design error.
+* The design issue: the number of hidden tabs should be decided **only once**, upon receiving the `resize` event. 
+** That's a more **complicated fix**, `collapseCondition` needs to be replaced by a logic that iterates the tabs and marks for hiding as many tabs as necessary to fit the available width.
+** Without animation it's unnecessary to be this elaborate.
+",1591163606,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Analysis
+
+I think this requires a bit more thought. A quick look at the code reveals one design mistake that starts the infinite cycle: [[ https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/601368/5/resources/skins.vector.legacy.js/collapsibleTabs.js#b147 | line 147 ]] calling
+`rAF( $.collapsibleTabs.handleResize );`
+after the animation (hiding/showing ONE tab) finishes. I assume to hide another tab, if necessary.
+* The immediate issue: does not check if the direction changes (hide -> show -> hide).
+** Easy fix. It's even easier to fix if the animation is removed: a loop can do (hide -> get size -> repeat if needed) in one cycle, the recalculation after the animation becomes unnecessary, which is the source of the design error.
+* The design issue: the number of hidden tabs should be decided **only once**, upon receiving the `resize` event. 
+** That's more complicated, `collapseCondition` needs to be replaced by a logic that iterates the tabs and marks for hiding as many tabs as necessary to fit the available width.
+** Without animation it's unnecessary to be this elaborate.
+",1591079028,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6183507, @Jdlrobson wrote:
+> ""with a valid purpose."" 
+> Just because something has existed for a long time doesn't mean a good decision was made. :)
+That's a good summary of my opinion on many decisions in MediaWiki :-) Some of which I've already discussed previously, hoping you'd say the same there ;-)
+
+However, in this case I referred exactly to a functionality, not a decision. Tabs can get pretty long (see for ex. [[ https://commons.wikimedia.org/wiki/User:Aron_Manning?useskin=vector | user pages imported from meta ]] with a ""View on meta.wikimedia.org"" tab), just cutting this code will result in:
+{F31850773}
+At 1200px width!
+
+I don't think that can be released to the public. There is a gap to be filled after cutting this code that needs to be planned, designed and implemented. I estimate that will take weeks. In the situation where a recently introduced regression needed fixing, this approach was unfeasible, this is why I've downvoted the patch immediately.
+
+Other than that, I think this code was fickle, and the animation might have looked good when Vector was created, but it's unusual today, so I agree it needs to be revisited. TBH I wanted to get rid of the animation for a long time, I dislike it that much. However, whether cutting it entirely is a good decision, depends on what's the alternative and I sense an ""`rm -rf *` removes all bugs"" approach that will certainly result in another disappointment for the users (aka. community).
+",1591079018,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","""with a valid purpose."" 
+Just because something has existed for a long time doesn't mean a good decision was made. :)
+
+The code is definitely not going to be run in the new Vector and is pretty complex for what it does. The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.",1591053536,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","@Jdlrobson the collapsibleTabs code existed for years with a valid purpose. I think removing it will raise some eyebrows at best, or cause further breakages at worst.
+Shouldn't we focus on fixing what's been broken by T249372 and T253912 and can be fixed easily, without any complications?",1591029296,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 601368 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
+[mediawiki/skins/Vector@master] Drop the collapsibleTabs code
+
+[[https://gerrit.wikimedia.org/r/601368]]",1591028881,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This code is clearly problematic and clearly hard to maintain it.
+
+Given Vector is not a responsive skin I honestly feel we should remove this code. Optimising the experience of Wikipedia at that resolution is not solving any problem except adding code complexity for a small gain.",1591025288,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","@Demian: ??? Leaving tickets open when tickets don't get completely fixed.
+
+(PS: I don't think that pinging after less than 24h on a weekend is constructive.)",1590998359,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",@Demian: ??? Leaving tickets open when tickets don't get completely fixed.,1590996544,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",@Aklapper Can you please answer the above //relevant// question?,1590959077,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6179380, @Aklapper wrote:
+> Again: This is definitely not Unbreak Now ([""Something is broken and needs to be fixed immediately, setting anything else aside.""](https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities)). Please stop setting that priority.
+Apparently there's no agreement on that: if the image of Wikimedia matters then it needs to be fixed immediately. That being said it does not matter until the next SWAT window, which is on Monday. If you don't agree, I'm happy to discuss this, but please do so off-ticket, it's off-topic here.
+
+@Aklapper the fix I've submitted is for a new regression introduced in wmf.34, which was reported in a wave of recent tickets that were closed as duplicates. //Those// look similar, but in fact aren't duplicates of //this// bug from 2014. This causes quite some confusion as people believe these are the same issue, furthermore the original bug won't be fixed by the patch, thus the ticket cannot be closed, leading to further confusion. What solution do you propose to untangle this?
+",1590896861,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6179380, @Aklapper wrote:
+> Again: This is definitely not Unbreak Now ([""Something is broken and needs to be fixed immediately, setting anything else aside.""](https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities)). Please stop setting that priority.
+Apparently there's no agreement on that: if the image of Wikimedia matters then it needs to be fixed immediately. That being said it does not matter until the next SWAT window, which is on Monday. If you don't agree, I'm happy to discuss this, but please do so off-ticket, it's off-topic here.
+
+@Aklapper the fix I've submitted is for a new regression introduced in wmf.34, which was reported in a wave of recent tickets that were closed as duplicates. //Those// look the similar, but in fact aren't duplicates of //this// bug from 2014. This causes quite some confusion as people believe these are the same issue, furthermore the original bug won't be fixed by the patch, thus the ticket cannot be closed, leading to further confusion. What solution do you propose to untangle this?
+",1590896812,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Again: This is definitely not Unbreak Now ([""Something is broken and needs to be fixed immediately, setting anything else aside.""](https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities)). Please stop setting that priority.",1590879547,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","With a fix ready to be merged and considering the loss of prestige caused by this bug, I think it now matches the [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | ""Unbreak Now"" ]] criteria.
+CC the participants from the sister hotfix: @Niedzielski @Jdlrobson 
+
+This missed the wmf.34 train though...",1590878921,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","With a fix ready to be merged and considering the loss of prestige caused by this bug, I think it matches the [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | ""Unbroken Now"" ]] criteria.
+CC the participants from the sister hotfix: @Niedzielski @Jdlrobson 
+
+This missed the wmf.34 train though...",1590853408,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","With a fix ready to be merged and considering the loss of prestige caused by this bug, I think it matches the [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | ""Unbroken Now"" ]] criteria.
+CC the participants from the sister hotfix: @Niedzielski @Jdlrobson 
+",1590853190,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Hotfix:  https://gerrit.wikimedia.org/r/600358
+
+Related regression: {T253912}
+
+Broken by:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/589395/39/resources/skins.vector.legacy.js/vector.js#32
+Reverted in CSS but not JS:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/599468
+
+I think this can be ""Unbroken Now""
+Won't fix the elusive bug from 2014, though. This is a new regression.",1590851708,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Hotfix:  https://gerrit.wikimedia.org/r/600358
+
+Related regression: {T253912}
+
+Broken by:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/599468
+not reverting:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/589395/39/resources/skins.vector.legacy.js/vector.js#32
+
+I think this can be ""Unbroken Now""
+Won't fix the elusive bug from 2014, though. This is new.",1590851433,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Related regression: {T253912}
+
+Broken by:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/599468
+not reverting:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/589395/39/resources/skins.vector.legacy.js/vector.js#32
+
+I think this can be ""Unbroken Now""
+Won't fix the elusive bug from 2014, though. This is new.",1590850983,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Related regression: {T253912}
+
+Broken by:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/599468
+not reverting:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/589395/39/resources/skins.vector.legacy.js/vector.js#32
+
+I think this can be ""Unbroken Now""",1590850855,PHID-USER-724ccjw2eq65o2te67qg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 600358 had a related patch set uploaded (by Aron Manning; owner: Aron Manning):
+[mediawiki/skins/Vector@master] Hotfix: Cannot rename `.emptyPortlet` to `.vector-menu-empty` yet. JS follow-up.
+
+[[https://gerrit.wikimedia.org/r/600358]]",1590850502,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","@dbarratt No. I did take a brief look at the code, but it's not something I feel I would be able to fix. 
+
+I was trying to be helpful and setting the priority as an ""experienced community member"" as described at  https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities since the task is unassigned, the situation has obviously changed since it was assessed as Low, and it looks bad to have such a highly visible task described as ""Low priority"". However I'll change it to Needs Triage so someone else can figure it out.",1590848865,PHID-USER-grgqimagqq3ankitlzm5,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","See: https://www.mediawiki.org/wiki/Phabricator/Project_management#Priority_levels
+
+@Pcoombe Are you (or your team) planning to work on this?",1590847212,PHID-USER-g5rqg2k7irztdonlursm,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","See: https://www.mediawiki.org/wiki/Phabricator/Project_management#Priority_levels
+
+@Pcoombe Are you planning to work on this?",1590847098,PHID-USER-g5rqg2k7irztdonlursm,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",This does not meet the criteria for an Unbreak Now!,1590846988,PHID-USER-g5rqg2k7irztdonlursm,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",Also happens on main page of dewiki at a zoom level of 133 percent when not logged in.,1590846618,PHID-USER-7sfnmvwpvh3etwtqk5pg,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",Boldly raising priority: given the number of duplicates this seems to have become much more common recently. Also seen a mention (with video) on Reddit https://www.reddit.com/r/softwaregore/comments/gtbdwu/cant_fit_all_the_buttons_in_the_frame_wikipedia/,1590843472,PHID-USER-grgqimagqq3ankitlzm5,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","That will be deployed next week, per the usual schedule. This task is not entirely fixed -- the tabs will still expand and collapse once on page load if you're using an unfortunate screen resolution. But correcting that is more difficult :/",1484268689,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 331919 merged by jenkins-bot:
+collapsibleTabs: Stop the tabs from collapsing back and forth forever
+
+[[https://gerrit.wikimedia.org/r/331919]]",1484268219,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This doesn't fix the issue entirely, but it should reduce it to mildly annoying. The tabs might still collapse back-and-forth once, but after that happens the code will update some internal calculations, and it should prevent the tabs from flapping forever.",1484260478,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 331919 had a related patch set uploaded (by Bartosz Dziewoński):
+collapsibleTabs: Stop the tabs from collapsing back and forth forever
+
+[[https://gerrit.wikimedia.org/r/331919]]
+",1484260214,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This has also been reported to us in OTRS, and I can easily reproduce it (at least in incognito mode) on local file description pages like https://de.wikipedia.org/wiki/Datei:Otzenrathpano2.jpg?uselang=de. So I'd also like to echo that this issue is easy to run into at the moment, which makes me wonder if this should really be treated as a low-priority issue.",1483643129,PHID-USER-x44asswe5g7265gs7ue4,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Grabbing some popcorn and selecting the `<li id=""ca-edit"">` element in Firefox' dev tools, things seem to happily jump around between three states: `display: list-item` with `right: 0px` not being applied, replaced by `display: block` with `left: 0px` not being applied and vice versa; plus only very occasionally also the 3rd screenshot with `div.vectorTabs` not being in the game at all:
+{F5228098}
+F5228098",1483536304,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I'm getting this on my non-existent user page (which is copied from Meta) at mediawiki.org in Firefox 50, with ""Show me both editor tabs"" enabled.  I can't trigger it without this setting.  With that setting, on a non-existent userpage, there are three long descriptions in tabs at the top of the page, and the last hides and un-hides repeatedly.  
+
+My browser window right now is about 1428 pixels wide.  To trigger it in English, I need to zoom in twice.  The default zoom triggers it in Russian.  Zooming in once or twice triggers it with the UI set to German.  So (the point of this message) if you aren't seeing it in your browser, then you might try enabling two tabs, switching to a couple of different languages with `?uselang=xx`, and/or zooming in and out a couple of steps.
+",1483466065,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I'm getting this on my non-existent user page (which is copied from Meta) at mediawiki.org in Firefox 50, with ""Show me both editor tabs"" enabled.  I can't trigger it without this setting.  With that setting, on a non-existent userpage, there are three long descriptions in tabs at the top of the page, and the last hides and un-hides repeatedly.  
+
+My browser window right now is about 1428 pixels wide.  To trigger it in English, I need to zoom in twice.  The default zoom triggers it in Russian.  Zooming in once or twice triggers it with the UI set to German.  So (the point of this message) if you aren't seeing it in your browser, then you might try enabling  switching to a couple of different languages with `?uselang=xx` or zooming in and out a couple of steps.
+",1483466015,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I noticed the problem today for the first time on my PC (Chromium), before I had experienced it only on the tablet. It happened with a user page on de.wiki that derived from meta, a similar case as the above mentioned.",1483199629,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I've tried to reproduce locally without success
+
+`File:Opening Karte_Gemeinde_Gommiswald_2013.png?uselang=de` with private browsing, with latest master of MediaWiki and Vector, with InstantCommons enabled, and adding this to LocalSettings.php to mimick the addition of the third tab (to avoid installing VisualEditor):
+
+```
+function test_onSkinTemplateNavigation_Universal( &$sktemplate, &$links ) {
+        $links['views']['whatever'] = [
+                'class' => 'collapsible',
+                'text' => 'Lokalen Beschreibungsquelltext hinzufügen',
+                'href' => '#'
+        ];
+
+        if ( isset( $links['views']['edit'] ) ) {
+                $links['views']['edit']['primary'] = true;
+        }
+}
+
+$wgHooks['SkinTemplateNavigation::Universal'][] = 'test_onSkinTemplateNavigation_Universal';
+```
+
+In one tab, dewiki page, in other tab my local wiki. On dewiki the bug happens, on my local wiki it doesn't. Texts and dimensions of the tabs are the same. The generated HTML for both (before running JavaScript) is equivalent.
+
+So the only variable that is left here that might cause the problem is Visual Editor. But why?",1483199227,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","> Judging by the number of reports, this has started happening more frequently for some reason.
+Indeed.
+
+As I don't get the effect in the link of the initial description here is an other example: 
+https://de.wikipedia.org/wiki/Datei:Karte_Gemeinde_Gommiswald_2013.png.
+The animation-loop happens from the start (without changing window-width).
+
+Firefox v.50: `1173px` to `1428px`
+Chromium v.53: `1113px` to `1341px`  (witch are quite average widths)",1483154649,PHID-USER-xjpggc6wz3et2e52c3my,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",Might have been caused by https://phabricator.wikimedia.org/rSVEC1f26153a5d77584508f8bbd10478e8d8021ccb42,1482943473,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Judging by the number of reports, this has started happening more frequently for some reason.",1482938453,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","As far as I can tell (T108588#1640647) FlaggedRevs prevents VE from using the desired labels for editing tabs on server side, thus forcing VE to modify them on client side, triggering this bug.",1481966449,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","No, FlaggedRevs doesn't do that, and is not affected. To my knowledge, VisualEditor is the only tool that's causing this.",1481894379,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#2878053, @Jdforrester-WMF wrote:
+> This is not VE-specific, right? Anything that adjusts the tabs after the PHP layer is done with it, like FlaggedRevs and some gadgets, has this problem?
+
+True, the VE-specific bug (see T71729#1611561) is T108588",1481834873,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This is not VE-specific, right? Anything that adjusts the tabs after the PHP layer is done with it, like FlaggedRevs and some gadgets, has this problem?",1481833225,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I got this today when reviewing changes from article's history one by one and the FlaggedRevs' ""Pending edits"" tab probably interfered.",1444670842,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#1611561, @Ciencia_Al_Poder wrote:
+>If that's not supported, VisualEditor shouldn't be doing that, right?
+
+Indeed. That JavaScript is there in case the server failed to do it correctly (or in case of cached html). Looks like the ru.wikipedia.org configuration is not supported correctly by the server-side equivalent of that code.
+
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/667d8d9935/VisualEditor.hooks.php#L136-L175
+
+> ```lang=php
+>	$tabMessages = $config->get( 'VisualEditorTabMessages' );
+>	..
+>	if ( .. ) {
+>		$editTabMessage = $tabMessages[$action . 'localdescriptionsource'];
+>	} else {
+>		$editTabMessage = $tabMessages[$action . 'source'];
+>	}
+> ```",1441464903,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",,1441465277,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",,1441464832,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Well, that VE thing seems to be tracked on T108588 instead",1441460883,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#1027038, @Krinkle wrote:
+> Changing the value of existing tabs is not supported. Can you provide an example or use case where this happens?
+> 
+> Such customisations (if desired) should be done upstream as part of Vector, or at least done server-side (e.g. by changing the MediaWiki namespace message for it, or by creating a hook in your LocalSettings configuration).
+
+Reported again in T111601, Cokersed shows a nice video of it http://elric.ga/files/out-1.ogv
+
+I see that on initial page load, there are 2 ""edit"" tabs with the same text: `Править`. Then, once the page finishes loaded, the text of the ""not-ve edit"" is changed to `Править вики-текст`
+
+I've inspected a bit of JS and I see that it seems to be changed by #VisualEditor
+
+https://ru.wikipedia.org/static/1.26wmf21/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.DesktopArticleTarget.init.js
+
+```
+			// Alter the edit tab (#ca-edit)
+			if ( $( '#ca-view-foreign' ).length ) {
+				if ( tabMessages[ action + 'localdescriptionsource' ] !== null ) {
+					$caEditLink.text( mw.msg( tabMessages[ action + 'localdescriptionsource' ] ) );
+				}
+			} else {
+				if ( tabMessages[ action + 'source' ] !== null ) {
+					$caEditLink.text( mw.msg( tabMessages[ action + 'source' ] ) );
+				}
+			}
+```
+
+If that's not supported, Visual Editor shouldn't be doing that, right?",1441459500,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#1027038, @Krinkle wrote:
+> Changing the value of existing tabs is not supported. Can you provide an example or use case where this happens?
+> 
+> Such customisations (if desired) should be done upstream as part of Vector, or at least done server-side (e.g. by changing the MediaWiki namespace message for it, or by creating a hook in your LocalSettings configuration).
+
+Given T108588, does VisualEditor change the tabs on client-side? If so, this definitely isn't ""Lowest"" priority.",1439222763,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Changing the value of existing tabs is not supported. Can you provide an example or use case where this happens?
+
+Such customisations (if desired) should be done upstream as part of Vector, or at least done server-side (e.g. by changing the MediaWiki namespace message for it, or by creating a hook in your LocalSettings configuration).",1423540184,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"VisualEditor:  Please show the file name in the media dialog, and make it easy to copy it","Steps to reproduce:
+
+1.  Open a page that contains an image that has a really long or complicated name.
+
+2.  Think, ""Hey, I could use that image over at ______ article, too.""
+
+3.  Click on the image.  What's its name?  Well, it starts off as File:Foo bar baz bat... but who knows what the rest of it is.
+
+
+It would be nice to be able to see the entire name of the image and to copy that name as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408405260,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gfvkr44kb7p4gblp7hfj,task_description,resolved
+"VisualEditor:  Please show the file name in the media dialog, and make it easy to copy it","I added `[[File:Diederich Graminaeus (1550-1610). Beschreibung derer Fürstlicher Güligscher ec. Hochzeit (Johann Wilhelm von Jülich-Kleve-Berg ∞ Jakobe von Baden-Baden, Hochzeit in Düsseldorf im Jahre 1585), Köln 1587, Ringrennen am 18. Juni 1585 in Pempelfort.jpg]]` to my page, loaded it in VE and looked at the media dialog. I could see and copy the whole thing, so I assume this got resolved at some point.",1437955553,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gfvkr44kb7p4gblp7hfj,task_subcomment,NA
+"VisualEditor:  Please show the file name in the media dialog, and make it easy to copy it","Being able to copy it from the tooltip would work for me, for example.",1409469981,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gfvkr44kb7p4gblp7hfj,task_subcomment,NA
+"VisualEditor: ""New template"" is a confusing window title","When adding a template to a page, the window title is ""New template"". This is quite confusing. Some users complained that it sounds like creating a whole new template.
+
+Please consider retitling it to something like ""Add a template"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1408366140,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-kz7ltfye5vll22zw4wk3,task_description,resolved
+"VisualEditor: ""New template"" is a confusing window title","Change 155448 merged by jenkins-bot:
+Re-label inserting mode of transclusion dialog from ""New template"" to ""Add a template""
+
+https://gerrit.wikimedia.org/r/155448",1408586844,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kz7ltfye5vll22zw4wk3,task_subcomment,NA
+"VisualEditor: ""New template"" is a confusing window title","Change 155448 had a related patch set uploaded by Jforrester:
+Re-label inserting mode of transclusion dialog from ""New template"" to ""Add a template""
+
+https://gerrit.wikimedia.org/r/155448",1408571374,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kz7ltfye5vll22zw4wk3,task_subcomment,NA
+Investigate lenient handling of quotes in xml-tag attribute values,"https://en.wikipedia.org/wiki/Dachshund#Coat_and_color has a complex gallery tag:
+
+<gallery widths=""200px"" heights=""200px"" perrow=""5"" caption= ""There are three types of dachshund, which can  be classified by their coats: short-haired, called ""smooth""; long-haired; and wire-haired"">
+File:Wirehaired_Dachshund.jpg|A wire-haired dachshund
+File:Kurzhaardackel.jpg|A short-haired dachshund
+Std Dachshund 600.jpg|A long-haired standard dachshund
+File:Piebald.jpg|A piebald dachshund
+File:Red-merle smooth Dachshund.jpg|A dapple dachshund</gallery>
+
+
+It's being displayed as raw wikitext in VisualEditor on desktop.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66065",1408231860,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-tunsh3had56hubhfkhlt,task_description,duplicate
+Investigate lenient handling of quotes in xml-tag attribute values,"We now have a bunch of tasks that are all about how best to handle broken attribute strings. Parsoid will not always match the PHP parser on this, and this is no longer a high priority task for us. At this point, tt seems reasonable to have these be fixed up in wikitext.",1422920342,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-tunsh3had56hubhfkhlt,task_subcomment,NA
+Investigate lenient handling of quotes in xml-tag attribute values,*** Bug 66065 has been marked as a duplicate of this bug. ***,1408572797,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-tunsh3had56hubhfkhlt,task_subcomment,NA
+Investigate lenient handling of quotes in xml-tag attribute values,"I imagine this is probably not that uncommon since template args and template content may use the same quotes and thus break the html tags. We've seen a few different instances of this bug now. So, maybe worth investigating what it takes to handle this form of broken wikitext a bit more leniently.",1408568812,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-tunsh3had56hubhfkhlt,task_subcomment,NA
+Investigate lenient handling of quotes in xml-tag attribute values,"This is invalid wikitext – you can't use raw "" characters inside the caption of a gallery. Parsoid works just fine if you replace them with ' characters instead:
+
+<gallery widths=""200px"" heights=""200px"" perrow=""5"" caption= ""There are three
+types of dachshund, which can  be classified by their coats: short-haired,
+called 'smooth'; long-haired; and wire-haired"">
+File:Wirehaired_Dachshund.jpg|A wire-haired dachshund
+File:Kurzhaardackel.jpg|A short-haired dachshund
+Std Dachshund 600.jpg|A long-haired standard dachshund
+File:Piebald.jpg|A piebald dachshund
+File:Red-merle smooth Dachshund.jpg|A dapple dachshund</gallery>
+
+I've fixed this in the article, but am moving the bug to Parsoid in case they want to comment/merge into a wider bug about escaping bad wikitext?",1408272080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tunsh3had56hubhfkhlt,task_subcomment,NA
+"VisualEditor: Keyboard shortcut dialog style differs between standalone and MW, ugly line wraps in MW","The keyboard shortcut styling is substantially different between the standalone demo and the MW integration in terms of font size. In MW, the font size is so much bigger that some shortcuts awkwardly break across lines. For instance, ""Ctrl+Shift+V"" is split with the ""V"" being on a line by itself. In SA, the font size is smaller (for the headings and the shortcuts, but not the descriptions) so this problem doesn't happen, but there the font feels a bit *too* small.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1408173420,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-y3iolseqcvefdxx6knc3,task_description,resolved
+"VisualEditor: Keyboard shortcut dialog style differs between standalone and MW, ugly line wraps in MW","Change 155539 merged by jenkins-bot:
+Define kbd font-family explicity in case environment overrides
+
+https://gerrit.wikimedia.org/r/155539",1408636142,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y3iolseqcvefdxx6knc3,task_subcomment,NA
+"VisualEditor: Keyboard shortcut dialog style differs between standalone and MW, ugly line wraps in MW","Change 155539 had a related patch set uploaded by Esanders:
+Define kbd font-family explicity in case environment overrides
+
+https://gerrit.wikimedia.org/r/155539",1408628545,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y3iolseqcvefdxx6knc3,task_subcomment,NA
+"VisualEditor: Keyboard shortcut dialog style differs between standalone and MW, ugly line wraps in MW","Ed likes fiddling with this dialog, so… :-)",1408272673,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y3iolseqcvefdxx6knc3,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","When I go to ""Enable Hovercards"" to change my settings, it always defaults to ""Read Quickly"", even when I explicitly change it to ""Monitor or Edit"", save, then re-open the dialog to check the setting.
+
+Tested in Firefox/Iceweasel 30.0
+
+--------------------------
+**See Also**: {T71576}",1408052580,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-csz2uil7ibkp5pr2bftr,task_description,invalid
+"When changing Hovercards settings, does not default to my current setting",Thanks @Mattflaschen-WMF. I've updated that page to indicate that Navigation Popups takes precedence when both are enabled.,1470747666,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","No longer applicable.
+
+It's now just Disable/Enable.
+
+There is another issue now (but it may be by design so I'm not filing yet): If you have the Navigation popups enabled, it always takes precedence.  Before, I think there was a way to switch back to Hovercards without explicitly disabling NAVPOP.
+
+This is still documented at https://www.mediawiki.org/wiki/Beta_Features/Hovercards : ""The Hovercards settings panel enables logged-out users to disable it entirely, and enables logged-in users to choose between Hovercards, Navigation popups, or disabling both."", but that might just be a doc bug.",1470700163,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting",@Mattflaschen-WMF I believe the options have changed. Would you please update the task Description as appropriate?,1470341779,PHID-USER-srhlj2447vmpmrfhqnfa,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","(In reply to Prateek Saxena from comment #3)
+> I had forgotten why we had added the settings in the first place while we 
+> were having our conversation. After speaking with Nick I remembered that 
+> we'll be making it a default feature (for all logged in and logged out users) 
+> on a few wikis that have shown interest.
+
+It can still be a normal preference on those wikis, defaulted to true.  E.g. VisualEditor has multiple modes, including one where a regular preference is shown, and another where a beta feature is shown.
+
+> Which is why we'll have to keep it the way it is. This pattern is being used 
+> by ReferencePopups too which is a gadget that is enabled by default for all 
+> users.
+
+Gadgets have very different UX considerations, since they can not use normal preferences.
+
+Note, currently (in production) I see both popups (I think this is meant to be fixed by https://gerrit.wikimedia.org/r/#/c/141668/ , not yet deployed) and no ""Disable HoverCards"" link when in ""Read quickly mode"".  This is arguably inconsistent, although you still have another way of disabling it (the gear).",1408583920,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting",I apologize for the confusion. I've been causing too many of them lately.,1408531481,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","(In reply to Matthew in comment #2)
+
+> We also talked about possible parts of the solution, including dropping ""Turn Previews off"" and relying on the standard BetaFeatures UI for disabling beta features.
+
+I had forgotten why we had added the settings in the first place while we were having our conversation. After speaking with Nick I remembered that we'll be making it a default feature (for all logged in and logged out users) on a few wikis that have shown interest. 
+
+Which is why we'll have to keep it the way it is. This pattern is being used by ReferencePopups too which is a gadget that is enabled by default for all users.
+
+
+
+(In reply to Matthew in comment #0)
+
+> When I go to ""Enable Hovercards"" to change my settings, it always defaults to ""Read Quickly""
+
+I think this is justified. The link says ""/Enable/ hovecards"" and not ""Open settings"" so it is correct for it to select that option.",1408531435,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","This may not make sense to fix in isolation.
+
+Prateek and I talked about some broader areas where the current UI may be confusing.
+
+We also talked about possible parts of the solution, including dropping ""Turn Previews off"" and relying on the standard BetaFeatures UI for disabling beta features.  That then simplifies the internal preferences needed, which opens up possibilities.",1408423647,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting",This is tested on English Wikipedia on 1.24wmf16.,1408052991,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+VisualEditor: Provide ability to deal easily with dead links,"I met User:Zoony at Wikimania and he said that something which he'd love to see in VE is a way to deal easily with dead (rotten) links.
+He suggested that a right click could launch a menu which provides access to several options, from searching on a search engine in a different tab (to try to fix one) to pasting the {{dead link}} template.
+(More info about ways to deal with dead links at https://en.wikipedia.org/wiki/Wikipedia:Link_rot#Repairing_a_dead_link ).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408030140,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mjskqwel42qqecgndgvg,task_description,open
+VisualEditor: Provide ability to deal easily with dead links,"We wouldn't use right click for touch compatibility, but links have a complex context area now which we can add too:
+{F2667021,size=full}",1444335666,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mjskqwel42qqecgndgvg,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Ideas of things to scan for:
+
+* Any request resulting in an error response (404 Not Found, 500 Internal Error, etc.).
+* Uncaught JavaScript exceptions.
+* Network requests made to third-party domains (images, stylesheets, scripts, xhr, etc.)
+
+From comment 13 at {T71445} :
+> However it would be great to have automated tests running after changes in common.js and gadgets. Such general tests can at least validate no external resource is loaded, or no invalid syntax is added.
+> The simplest option is to run it outside MW (such as a script in labs that runs X times a day), but an extension to do it while editing would be even better...
+> 
+> BTW
+> I just runned a simple phantomjs script on all wikipedia languages to catch simple errors:
+> 
+> testing als
+> ERROR: ReferenceError: Can't find variable: ta
+> TRACE:
+> -> https://als.wikipedia.org/w/index.php?title=MediaWiki:If-pt-login.js&action=raw&ctype=text/javascript&dontcountme=s: 9
+> 
+> testing kk
+> ERROR: TypeError: 'null' is not an object (evaluating 'document.getElementById('mw-vector-current-variant').innerHTML=wgULS(""Кирил"",""Latın"",""توتە"")')
+> TRACE:
+> -> https://bits.wikimedia.org/kk.wikipedia.org/load.php?debug=false&lang=kk&modules=site&only=scripts&skin=vector&*: 9
+> 
+> 
+> anyone wants to fix them? :)
+> 
+
+From comment 14 at T71445:
+> Example for errors across wikis
+> Maybe it is a bit off-topic but here are some cases of errors across wikis in simple read/edit transaction using phantomJS
+
+See also:
+* {T71519}
+* {T106770}",1407983460,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_description,resolved
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,Obsoleted by {T226986}.,1691360468,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,:( unfortunately slimerjs is basically dead at this point. I should rewrite it on top of selenium.,1615221757,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"In the meanwhile I noticed that the current Jenkins job cited here is failing for all the wikis:
+
+> ```
+> name=aa.wikibooks.org.log
+> ERROR: aa.wikibooks.org: JSON errorGecko error: it seems /usr/bin/firefox is not compatible with SlimerJS.
+> See Gecko version compatibility. If version is correct, launch slimerjs
+> with --debug=true to see Firefox error message
+> from (https://aa.wikibooks.org/wiki/Main_Page)
+> ```
+>
+> ```
+>name=en.wikipedia.org.log
+>ERROR: en.wikipedia.org: JSON errorGecko error: it seems /usr/bin/firefox is not compatible with SlimerJS.
+>See Gecko version compatibility. If version is correct, launch slimerjs
+>with --debug=true to see Firefox error message
+> from (https://en.wikipedia.org/wiki/Main_Page)
+>```
+> ...
+> https://integration.wikimedia.org/ci/job/audit-resources/lastSuccessfulBuild/artifact/log/",1615214055,PHID-USER-hphk5jxfxfgl64tpfacw,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592584225,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"I think in terms of implementation that's probably good enough.
+
+Does its output go to something we can alert on? And/or does it tell someone/something when it fails?",1590104706,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,So https://integration.wikimedia.org/ci/job/audit-resources/ has been running for 2 years now. What else do we need/want?,1590104473,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,">>! In T71519#4002895, @eranroz wrote:
+> IMO this page is more targeted for extension developers with different skills (git/gerrit/php). I added documentation here: https://www.mediawiki.org/w/index.php?title=Gadget_kitchen&type=revision&diff=2725392&oldid=2718404  I
+> 
+> @Legoktm   - I couldn't find the relevant job in https://integration.wikimedia.org/ci - can you please add a link there (""where??"")
+
+It wasn't actually being run yet...the jenkins job is now https://integration.wikimedia.org/ci/job/audit-resources/ and I just kicked off a test run.",1526269823,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Change 413684 **merged** by jenkins-bot:
+[integration/config@master] Add docker image to run audit-resources
+
+[[https://gerrit.wikimedia.org/r/413684]]",1526267796,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,">>! In T71519#4000631, @Elitre wrote:
+>>>! In T71519#3982243, @eranroz wrote:
+>> Thanks @Legoktm well done and daily jenkins job is good idea to track it regularly. you can mark it as resolved.
+>> 
+>> (and some words to end this phab task from where it started T71445 : we should think how to use this utility as part of community ""code review"" process - so if we can trigger the job on wiki edit in .js files or document it somewhere as part of ""community code review"" process  )
+> 
+> Integrate with https://www.mediawiki.org/wiki/Review_queue? (not sure how official/followed that is.)
+IMO this page is more targeted for extension developers with different skills (git/gerrit/php). I added documentation here: https://www.mediawiki.org/w/index.php?title=Gadget_kitchen&type=revision&diff=2725392&oldid=2718404  I
+
+@Legoktm   - I couldn't find the relevant job in https://integration.wikimedia.org/ci - can you please add a link there (""where??"")
+",1519672148,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,">>! In T71519#3982243, @eranroz wrote:
+> Thanks @Legoktm well done and daily jenkins job is good idea to track it regularly. you can mark it as resolved.
+> 
+> (and some words to end this phab task from where it started T71445 : we should think how to use this utility as part of community ""code review"" process - so if we can trigger the job on wiki edit in .js files or document it somewhere as part of ""community code review"" process  )
+
+Integrate with https://www.mediawiki.org/wiki/Review_queue? (not sure how official/followed that is.)",1519640045,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Change 413684 had a related patch set uploaded (by Legoktm; owner: Legoktm):
+[integration/config@master] Add docker image to run audit-resources
+
+[[https://gerrit.wikimedia.org/r/413684]]",1519374344,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Thanks @Legoktm well done and daily jenkins job is good idea to track it regularly. you can mark it as resolved.
+
+(and some words to end this phab task from where it started T71445 : we should think how to use this utility as part of community ""code review"" process - so if we can trigger the job on wiki edit in .js files or document it somewhere as part of ""community code review"" process  )",1519021658,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"OK, so I opted for the initial solution that was proposed, using phantomjs to go over a bunch of URLs. Except instead of phantomjs, it's using slimerjs which has roughly the same API, but uses Firefox. It currently generates a per-wiki debug log, and then a single ""error"" log that contains any external resource loading violations plus JavaScript errors. I'd like to split those into two logs. We can have jenkins run this daily, and email to lists of people depending on what type of error it is (external resource or JS exception).
+
+Using 8 threads for each wiki's home page on the default skin took about 15 minutes total to run.",1519020999,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Change 412618 **merged** by Legoktm:
+[integration/audit-resources@master] Initial commit
+
+[[https://gerrit.wikimedia.org/r/412618]]",1519020089,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Change 412618 had a related patch set uploaded (by Legoktm; owner: Legoktm):
+[integration/audit-resources@master] Initial commit
+
+[[https://gerrit.wikimedia.org/r/412618]]",1519020038,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"...and mentioning {T106770} here.
+Not sure if that is a hard requirement and should be a dependency (subtask) here though",1500632004,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Replaced ""PhantomJS"" by ""automated browser tests"" in the task summary.
+
+Reading through the comments here and trying to summarize the perfect world:
+* run tests on all Wikimedia sites (gather from sitematrix)
+* run tests on mainpage, editing page etc (via predefined urls), with debug=true
+* allow test to be logged in
+* enable / cover all available gadgets on the site
+* cover MediaWiki:common.js on the site
+* cover skins on the site
+* maybe cover stuff like MediaWiki:Mobile.js or MediaWiki:Minerva.js or MediaWiki:Vector.js ?) on the site
+* cover detecting code that calls 3rd party domains
+I assume there is consensus to run such a test as a Jenkins job?
+
+Also wondering if this could potentially be a Hackathon project. If e.g. legoktm's script can be used as a base.
+
+For the records, aforementioned https://integration.wikimedia.org/ci/view/BrowserTests/view/Core/ and https://integration.wikimedia.org/ci/view/BrowserTests/view/-Dashboard/ are 404s nowadays. No idea if similar things are available on https://integration.wikimedia.org/ci/view/Default/ ...",1493642305,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,">>! In T71519#1567266, @hashar wrote:
+> @krinkle mentioned that PhantomJS is based on a completely outdated Webkit version
+
+Yeah, we're rewriting asset-check on top of Chromium for that reason. Similar to what I did with our QUnit infrastructure in Jenkins. The APIs are similar though, so it's not that much work. See T106770.",1440425911,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,See also {T101497},1440425176,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"@krinkle mentioned that PhantomJS is based on a completely outdated Webkit version that no more reflect the current browsers hitting the sites.  So I guess we can rephrase this task as being a smoke test for the production sites using modern browsers (chromium/firefox).
+
+We have a bunch of browser tests hitting production already ( https://integration.wikimedia.org/ci/view/BrowserTests/view/-Dashboard/ )  and even a test suite for MediaWiki core although it is only hitting beta https://integration.wikimedia.org/ci/view/BrowserTests/view/Core/
+
+
+Potentially we could come up with a set of tests defined somewhere (maybe integration/config) that are a shared responsibility, run continuously and spam everyone whenever something fails.  Will need to describe what kind of smoke tests we are interested to exercise though.
+
+",1440423674,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,Looks like this is more something for Jenkins to run than something that needs production server access...,1440016771,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"The webperf project has an asset-check deamon (see [""Webperf"" on Wikitech](https://wikitech.wikimedia.org/wiki/Webperf#asset-check)) that frequently (every 5 minutes) views a bunch of different endpoints in a PhantomJS browser and collects metrics. We can extend this to cover any metrics needed here.
+
+It currently publishes the metrics to Ganglia only which isn't very accessible. See T105354 for moving this to Graphite so we can build a dashboard for it and just in general to allow people to query the data more easily.
+
+See the [checkAssets() in webperf/asset-check.js](https://github.com/wikimedia/operations-puppet/blob/4ba5e62018ede8929025fb7a2a156c76527860e1/modules/webperf/files/asset-check.js#L61-L97) for an overview of the data currently collected.",1480981511,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"The webperf project has an asset-check deamon (see [""Webperf"" on Wikitech](https://wikitech.wikimedia.org/wiki/Webperf#asset-check)) that frequently (every 5 minutes) views a bunch of different endpoints in a PhantomJS browser and collects metrics. We can extend this to cover any metrics needed here.
+
+It currently publishes the metrics to Graphite only which isn't very accessible. See T105354 for moving this to Graphite so we can build a dashboard for it and just in general to allow people to query the data more easily.
+
+See the [checkAssets() in webperf/asset-check.js](https://github.com/wikimedia/operations-puppet/blob/4ba5e62018ede8929025fb7a2a156c76527860e1/modules/webperf/files/asset-check.js#L61-L97) for an overview of the data currently collected.",1436458429,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"There's also the VE production browser test that ensures that all wikis with VisualEditor installed actually let you get to VE successfully:
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-production-linux-firefox-sauce/
+
+(The fy.wikipedia.org one is just a regular test suite failure; the kk.wikipedia.org one looks like a local sysop has broken JS there.)",1408096409,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Seems we have two versions :-]  If you guys could unify the effort and have the resulting code hosted in Gerrit, I would be more than happy to write a Jenkins job that runs the script  once per hour and spam some place (mail/IRC...).",1408018640,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"here is my version used for error checking:
+https://github.com/eranroz/wiki-js-error-log/blob/master/testwiki.js",1407988684,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"(In reply to MZMcBride from comment #0)
+> ...
+> testing als
+> ERROR: ReferenceError: Can't find variable: ta
+> TRACE:
+>  ->
+> https://als.wikipedia.org/w/index.php?title=MediaWiki:If-pt-login.
+> js&action=raw&ctype=text/javascript&dontcountme=s: 9
+> ...
+FIXED:
+https://als.wikipedia.org/wiki/MediaWiki:If-pt-login.js?diff=584752",1407984199,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"<http://tools.wmflabs.org/legobot/wmf_js_scanner.js> checks for any JS errors being thrown on the main page (as an anonymous user) as well as the inclusion of any external resources.
+
+Ideally such a tool would be able to login, visit a few pages (including ?action=edit), enable and disable individual gadgets and change skins.",1407983853,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"The idea here is to use a tool such as PhantomJS (a headless WebKit browser) to hit a bunch of pre-defined URLs and report JavaScript errors.
+
+In addition to strictly checking errors, checking fetches of content on domains outside of Wikimedia's control (e.g., Google Analytics) would also be nice.",1407983729,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","Scan down these to find lots of garbage, including lines like:
+
+</xml><![endif]--><!--[if gte mso 9]><xml>
+
+or 
+
+<!--[if gte mso 9]><xml>
+
+https://fr.wikipedia.org/w/index.php?title=Catherine_Lemorton&curid=1711917&diff=105874955&oldid=105753648
+
+
+https://fr.wikipedia.org/w/index.php?title=Paul_C%C3%A8re&curid=8199909&diff=106116894&oldid=106116223
+
+https://fr.wikipedia.org/w/index.php?title=Paul_C%C3%A8re&curid=8199909&diff=106116209&oldid=106116068 
+
+https://fr.wikipedia.org/w/index.php?title=Andr%C3%A9_Grassi&curid=5857691&diff=106069630&oldid=105919440 
+
+https://fr.wikipedia.org/w/index.php?title=Capitulaire_de_Coulaines&curid=1578466&diff=106053129&oldid=90262123 
+
+https://fr.wikipedia.org/w/index.php?title=Charles_Ateba_Eyene&curid=7794227&diff=105959949&oldid=105470353
+
+
+This may be helpful in finding others:
+
+https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Modifications_r%C3%A9centes&days=30&from=&tagfilter=balise+HTML+interdite
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69821
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61371",1407974760,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ydyactq6zkhdtz4zvqql,task_description,resolved
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","This now looks to be fixed; I pasted the contents of a couple of the diffs show above into the HTML clipboard, and then back out into VisualEditor (simulating a copy from Microsoft Office), and the unwanted cruft was all magically removed.",1427402940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)",The comments were dealt with in T71821,1417005560,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)",Maybe Outlook is kind of part of Microsoft Office nowadays anyway. :),1408802811,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","Isn't mso Microsoft Office, rather than Outlook?",1408752973,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","(In reply to Alex Monk from comment #1)
+> People copying in things from MS Word, it seems:
+> http://www.equalserving.com/what-the-heck-is-msonormaltable-and-how-did-it-
+> get-in-my-post/
+
+Yes, probably, but this problem is new in VE: the first occurrence I've been able to find in frwiki is in August 1st. Nothing previously.",1408447733,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","People copying in things from MS Word, it seems: http://www.equalserving.com/what-the-heck-is-msonormaltable-and-how-did-it-get-in-my-post/",1408046482,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+VisualEditor:  Page options icon is confusing,"From John Broughton:
+
+It would be easier to remember what this menu does, and to tell others about it (say, in the User Guide) if the icon for it were the text “Page” (with a down-arrow) rather than three horizontal lines. This menu icon approach is used for the “Insert” and “Cite” menus, which helps users immediately understand (and/or remember) what type of items are on the menu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407972420,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gho3zvnxqkwy4kgvoeo4,task_description,declined
+VisualEditor:  Page options icon is confusing,"Prateek, I don't remember seeing any complaints about this for a long while.  Maybe people are used to it now?",1515105150,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gho3zvnxqkwy4kgvoeo4,task_subcomment,NA
+VisualEditor:  Page options icon is confusing,With {T177432} progressing this should get resolved as we're using an article icon with settings cog.,1514960744,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-gho3zvnxqkwy4kgvoeo4,task_subcomment,NA
+VisualEditor:  Page options icon is confusing,"//Page options// is a vague thing and so gets a vague icon {icon frown-o}. We could use the typical {icon cog} or {icon cogs} but that might get confused as settings for the editor itself. The same might be true for {icon sliders} too, plus we're using both those icons for items within the menu.
+
+Other options might be {icon wrench}, {icon tachometer} or {icon file-o}.
+
+***
+
+@Whatamidoing-WMF, the {icon bars} icon while confusing has become quite popular as a //more options// icon, do you still find it difficult while communicating to users?",1504791222,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-gho3zvnxqkwy4kgvoeo4,task_subcomment,NA
+Enable Visual Editor for Math by default,"**Author:** `physik`
+
+**Description:**
+I'm using the vagrant role visual-editor for my wiki.
+After enabling the visual editor role I could not edit formulae... The message is available in source mode only.
+I see that the visual editor for math is not super fancy now, but it should be somehow stable?
+If not this can become a tracking bug to trace of the bugs that need to be resolved.
+
+--------------------------
+**Version**: master
+**Severity**: minor",1407933840,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5kt2ttqsqdttw35wyuft,task_description,invalid
+Enable Visual Editor for Math by default,"**physik** wrote:
+
+I think my version is not very old...
+/vagrant/mediawiki/extensions/VisualEditor$ git log -1
+commit f5681d490016a8c3213bbdceae859d784dbb5359
+Author: Translation updater bot <l10n-bot@translatewiki.net>
+Date:   Tue Aug 12 21:40:40 2014 +0200
+
+    Localisation updates from https://translatewiki.net.
+
+    Change-Id: I8e86d5dcaa3204893733734acf1439414656fc0f
+I'm not aware of any configuration option that disables VE-support in the Math extension.",1407944696,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5kt2ttqsqdttw35wyuft,task_subcomment,NA
+Enable Visual Editor for Math by default,"Umm. This was done in gerrit I0dd1c85a four months ago… are you running very very old code, or have you got the Maths extension configured in a way that breaks the VisualEditor plugin?",1407941455,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5kt2ttqsqdttw35wyuft,task_subcomment,NA
+Enable Visual Editor for Math by default,"**physik** wrote:
+
+Visual editor for math disabled
+
+**Attached**: {F14708}",1407934224,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5kt2ttqsqdttw35wyuft,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"**Author:** `ronnirubin`
+
+**Description:**
+Re bug 68101
+
+> Load VE. Say ""Foobar"" is the first word on the page.
+> If you click on the link tool, by mistake or not, without selecting anything before, Foobar will automatically become a link to the Foobar page (it doesn't help that pressing ESC doesn't abort the action, the link gets applied anyway, as we know).
+
+ESC _should not_ exit and save; it should either exit without saving, or revert the change (in this case, the link) without exiting.  I was going to set the Severity to ""blocker"", as it would block installation on en.Wikipedia, but that would be wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407776940,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ufpvladvj4hbtquskrvo,task_description,resolved
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,This was fixed a while ago.,1561738917,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"Yeah, that's {T52868}.",1454692497,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"Not sure if I'm adding further confusion :) 
+(and I think this task didn't keep T101176 into account?)
+but from what I'm reading at the German Wikipedia,
+some would find it desirable that ESC allowed to leave the ""blue"" link area after a link is added and placed the cursor just at the right so that people can quickly start typing again.
+
+Currently, hitting ESC right after choosing a link target doesn't close the link tool - it prompts the ""Are you sure?"" dialog to leave the page entirely.
+Also, to get out of the blue area just via the keyboard, you need to hit the right arrow twice (which doesn't seem much intuitive).",1454528383,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"Unfortunately I agree with BOTH of you. 
+I am often confused by the behaviour of the link dialogue and am often looking for the ""insert"" or ""confirm"" button. ""Done"" doesn't seem right to me somehow. 
+On the other hand, James is right too. The behaviour of all the formatting icons on the toolbar is that as soon you press them, the action takes place. So, highlighting a word and pressing ""bold"" will cause the text to go bold immediately, not after a second 'confirmation click'. 
+Nevertheless, despite intellectually understanding the link dialogue design, I keep stumbling on it - it gets in the way and I have to consciously think about it - which is not good behaviour for a labor-saving device.",1410168235,PHID-USER-b653jige5ek3oq53yron,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"This is a mistaken understanding of what the button does, and what the window is for.
+
+* The link button *creates* a link if there is none there already.
+* Once the link is created, we then also pop up a link editing window 
+* This is to let you change the link to point to a different place, or remove it.
+* Pressing escape closes the editing window, leaving you with the link you created.
+
+This is intentional design. Escape isn't ""applying"" anything, but it's probably not very clear. Maybe design would like to comment?",1409670135,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+Highlight that you can incrementally adjust the edit summary,"When editing in VisualEditor, you can click ""save"", add some text to the edit summary, click ""resume editing"", edit some more, and repeat. This kind of incremental summary is a fairly common request from editors who add to the summary field when they make each successive change in an edit. 
+
+So we actually have the capability they're requesting, but it's not well designed for this use case
+",1407758940,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-jy7hdkzqail6eg6yzt7t,task_description,open
+Highlight that you can incrementally adjust the edit summary,See also (merge one into other?) {T52961},1432250894,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-jy7hdkzqail6eg6yzt7t,task_subcomment,NA
+Highlight that you can incrementally adjust the edit summary,"Actually, I didn't realise you could do that which makes this much less of a problem that I thought it was.  Still, it's a bit clunky. I can't, for instance, start writing the edit summary first (I have to edit something first to make the save button go live).  There are many situations where one has ""dirty"" data on the clipboard carried from somewhere else and intended for the edit summary.  Have to remember not to copy-paste anything else before dumping it in the edit summary field.",1407786922,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-jy7hdkzqail6eg6yzt7t,task_subcomment,NA
+Highlight that you can incrementally adjust the edit summary,"I believe that what SpinningSpark is actually requesting is to have the edit summary visible and editable on the main screen.  Right now, you can fill out the edit summary incrementally, but you have to click on the Save button and then cancel saving each time.",1407781480,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jy7hdkzqail6eg6yzt7t,task_subcomment,NA
+VisualEditor: Find a way to make the link button is more discoverable,"**Author:** `che`
+
+**Description:**
+Yesterday I tried VisualEditor for the first time, after nine years of editing wikitext. I took me several minutes to find out how to make a link. I have tried text styles drop-down (as it has an underlined letter, which I associated with hyperlinks), the the ""insert"" drop-down, which included several useful objects, but not the hyperlink option. I have tried typing ""[["", which has shown me a warning that wiki syntax does not work, but did not tell how to create a link in VisualEditor. Then I went through citation and list-formatting menus, before finally stumbling onto the link button, which is sort of grey, and the only button in the line that has no drop-down arrow. In retrospect, I guess I though it is some kind of separator.
+
+Some things that might have made my life easier:
+- a bit more obvious link button
+- having another link option in ""insert"" menu (with the same icon, so I could discover it on the toolbar afterwards)
+- having mr. Clippy's ""It looks like you're attempting to use wikitext"" message point me to the VisualEditor equivalent of what I'm trying to do (by showing the icon or highlighting the button on toolbar)
+
+Alternatively, interpreting wikitext in VisualEditor might make life easier for users experienced with it's syntax, but that might be a stupid idea.
+
+In any way, thank you for your work on VisualEditor. You're pushing as all forward towards a better future :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407676140,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7loco2tyuhwahwjzohkg,task_description,declined
+VisualEditor: Find a way to make the link button is more discoverable,"The link button is prominent enough. I do not agree that making it more prominent would be a good idea.
+
+Also, since this bug was filed, typing `[[` does now open the link dialogue.",1519404429,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-7loco2tyuhwahwjzohkg,task_subcomment,NA
+VisualEditor: Find a way to make the link button is more discoverable,"The current link button is very similar to what is used in Google Docs and Gmail. It also has the same keyboard shortcut - Ctrl-K.
+
+Adding a button to the insert menu is not bad, but may increase clutter unnecessarily.
+
+Interpreting wikitext such as identifying that the editor is typing [[ would be nice DWIM for a lot of people, but unnecessary for others. I wouldn't make it a priority.",1408350501,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-7loco2tyuhwahwjzohkg,task_subcomment,NA
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode","For example, if you open the link tool on a blank page, there is nothing to ""Remove"" and nothing to ""Open"", so those buttons should be grayed out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407652020,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ym3q5jy7edmc533tzdy5,task_description,resolved
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode","(In reply to Alex Monk from comment #3)
+> Maybe relabel it ""Cancel"" instead in this case?
+
+Maybe.",1416255867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ym3q5jy7edmc533tzdy5,task_subcomment,NA
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode","Maybe relabel it ""Cancel"" instead in this case?",1416183190,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ym3q5jy7edmc533tzdy5,task_subcomment,NA
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode","(In reply to WhatamIdoing from comment #0)
+> For example, if you open the link tool on a blank page, there is nothing to
+> ""Remove"" and nothing to ""Open"", so those buttons should be grayed out.
+
+1. Click into a blank spot (e.g. the cursor is at '|' in ""Foo | Bar"")
+2. Enter a search term and select a link target
+
+At this point, the only way to not insert this link is to click ""Remove""; disabling it would mean that to not insert the link, you would have to empty the search box and then click ""Done"" (confusing) or outside the inspector (not possible in mobile).
+
+Maybe we could come up with a different label, or maybe we don't care about this edge case enough?",1414086706,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ym3q5jy7edmc533tzdy5,task_subcomment,NA
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode",Open button was bug 70015,1414083209,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ym3q5jy7edmc533tzdy5,task_subcomment,NA
+"VisualEditor:Text style drop-down overridden by edit comment, in Monobook skin.","screenshot
+
+environment- test2
+
+1> open page in VE, insert a comment.
+2> Click to edit the comment.
+3> Now click on the Text Style Menu, notice the  text style drop-down opens with edit comment dialog overriding it . Please see screenshot.
+
+Only on Monobook skin, same issue found in FF.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14206}",1407445440,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-fvmxjg6y2457g7m277ut,task_description,resolved
+"VisualEditor:Text style drop-down overridden by edit comment, in Monobook skin.",Issue Resolved on test2.,1409668410,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-fvmxjg6y2457g7m277ut,task_subcomment,NA
+"VisualEditor:Text style drop-down overridden by edit comment, in Monobook skin.",Think that this may have been fixed by gerrit 156723.,1409247899,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fvmxjg6y2457g7m277ut,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"screenshot
+
+1> Open a page in VE, the skin is Monobook.
+2> Insert a link.
+3>While the link icon is visible, move the cursor to the beginning of the link. The link icon looks broken. See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14152}",1407422460,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-cid7l2qphwhjkog4ga2f,task_description,resolved
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,Issue not fixed on test2.,1410182118,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"(In reply to Ritu Swain from comment #6)
+> Issue not fixed on test2.
+
+Yes, this code will be deployed to test2 on 2014-09-04 so for now it will still be broken, sorry.",1409669028,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,Issue not fixed on test2.,1409668630,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,Think that this may have been fixed by gerrit 156723.,1409247941,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,[editing bug summary],1407493009,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"(In reply to Andre Klapper from comment #2)
+> What does ""is broken"" or ""look broken"" mean exactly here?
+
+As the cursor moves on the link,the tip (""^"") of the link icon moves along.But when you move it to the first character of the link, the tip(""^""), it appears not to be part of the link icon anymore . Please see attached screenshot.",1407442326,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"What does ""is broken"" or ""look broken"" mean exactly here?",1407425757,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"Similar behavior found with the other icons as well, like - Comment,Language.",1407422917,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VE's beta help adds a question mark to 'Switch to source editing',"VE's help icon popup includes this ""visualeditor-beta-warning"" text:
+
+... To switch back to source editing at any time without losing your changes, open the dropdown next to ""Cancel"" and select ""Switch to source editing?"".""
+
+The last message is 'visualeditor-mweditmodesource-title'.  But the item in the dropdown is actually visualeditor-mweditmodesource-tool, which is ""Switch to source editing"" without a question mark. Trivial to fix.
+
+(Also ""Cancel"" is gone from the VE UI, I filed bug 69201.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1407357360,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-h725ojkqatxs3kupeh7s,task_description,resolved
+VE's beta help adds a question mark to 'Switch to source editing',"Change 152913 merged by jenkins-bot:
+Fix use of visualeditor-mweditmodesource-title instead of …-tool
+
+https://gerrit.wikimedia.org/r/152913",1407959178,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h725ojkqatxs3kupeh7s,task_subcomment,NA
+VE's beta help adds a question mark to 'Switch to source editing',"Change 152913 had a related patch set uploaded by Jforrester:
+Fix use of visualeditor-mweditmodesource-title instead of …-tool
+
+https://gerrit.wikimedia.org/r/152913",1407508641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h725ojkqatxs3kupeh7s,task_subcomment,NA
+Add a proper way in MobileFrontend to load custom editors,"Currently the MobileFrontend provides two editors : one using wikitext and one based on the VisualEditor. It would be nice to have a proper editor loader in order to allow to the creation of customized editors by other extensions (an use case may be an editor for Wikisource Page: pages).
+
+**See Also**:
+* {T67165}",1407330780,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_description,stalled
+Add a proper way in MobileFrontend to load custom editors,"This already exists.
+
+You can use the hook 'SkinMinervaDefaultModules'
+
+Inside the hook you can replace the editing module with your own module.
+
+e.g.
+
+$modules['editor'] = array( 'mycustomeditor' )
+
+Can you try this and see if it works for you?",1410913173,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_subcomment,NA
+Add a proper way in MobileFrontend to load custom editors,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/1GD5dpRW",1408025121,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_subcomment,NA
+Add a proper way in MobileFrontend to load custom editors,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/pWbLQ2ga",1407417610,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_subcomment,NA
+Add a proper way in MobileFrontend to load custom editors,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/3iclM3PZ",1407330909,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_subcomment,NA
+VisualEditor: ResourcesTest::testUnsatisfiableDependencies: The module 'mobile.editor.ve' must not have target 'desktop',"With attachment 16112:
+
+119) ResourcesTest::testUnsatisfiableDependencies
+The module 'mobile.editor.ve' must not have target 'desktop' because its dependency 'ext.visualEditor.mobileViewTarget' does not have it
+Failed asserting that an array contains 'desktop'.
+
+/srv/vagrant/mediawiki/tests/phpunit/structure/ResourcesTest.php:98
+/srv/vagrant/mediawiki/tests/phpunit/MediaWikiTestCase.php:133
+/srv/vagrant/mediawiki/tests/phpunit/MediaWikiPHPUnitCommand.php:42
+/srv/vagrant/mediawiki/tests/phpunit/phpunit.php:160
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406848200,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-d3rxpccf3znjcbyhsazz,task_description,resolved
+VisualEditor: ResourcesTest::testUnsatisfiableDependencies: The module 'mobile.editor.ve' must not have target 'desktop',Not re-encountered in over a year.,1438385391,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d3rxpccf3znjcbyhsazz,task_subcomment,NA
+VisualEditor: ResourcesTest::testUnsatisfiableDependencies: The module 'mobile.editor.ve' must not have target 'desktop',Hmm. mobile.editor.ve is defined in MobileFrontend but without a mobile target (!?)… How does mobile.editor.ve get used in mobile?,1406908192,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d3rxpccf3znjcbyhsazz,task_subcomment,NA
+VisualEditor: dm.Document seems to not get the right lang and dir settings inside the Media Dialog in insert mode,"… so instead it falls back to the built-in defaults (en and ltr), but really it shouldn't ever get to this position.",1406764980,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7upi3shakwholt2fwmgg,task_description,open
+VisualEditor: dm.Document seems to not get the right lang and dir settings inside the Media Dialog in insert mode,Is this now fixed?,1449024310,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7upi3shakwholt2fwmgg,task_subcomment,NA
+VisualEditor: Metas at the end of a link annotation's anchor cause it to be split; should instead change with it,"(Taken from bug 52127.)
+
+Previously, before comments were node-ified, editing
+
+  [[Foo|Bar<!--Foo!-->]]
+
+… to point to ""Baz"" would create the wikitext:
+
+  [[Baz|Bar]][[Foo|<!--Foo!-->]]
+
+… whereas it should have done
+
+  [[Baz|Bar<!--Foo!-->]]
+
+… (i.e., meta items inside annotations should get changed when the annotation changes, not keep their existing ones).
+
+
+As comments are (mostly) now nodes, this doesn't apply to them, but will apply to other meta items like {{DISPLAYTITLE:Foo}} or whatever broken items might exist.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406598120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfafbeovak6pyjwejllz,task_description,resolved
+VisualEditor: Metas at the end of a link annotation's anchor cause it to be split; should instead change with it,"So, it turns out we fixed this at some point in the past ~3 years anyway – tested on 1.31.0-wmf.17:
+
+https://www.mediawiki.org/w/index.php?title=User:Jdforrester_(WMF)/T70779&diff=2703642&oldid=2703641
+
+However, it still works after the re-unification of data and meta-data, tested on 0c9fb65fbe:
+
+https://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Jdforrester_(WMF)/T70779&diff=375632&oldid=375631
+
+… hurrah?",1517251219,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lfafbeovak6pyjwejllz,task_subcomment,NA
+VisualEditor: Reconsider template tool tabbing behaviour to go to the next field (not the info or remove buttons),"This is possibly by design, but I found it unexpected:
+
+Use the Cite tool with any example having multiple fields to fill in, e.g. Website or Book.
+
+Enter a field. Hit TAB.
+
+I would expect the cursor to go to the next editable field, but instead the cursor highlights first the Field description icon, then the Remove field icon, and only after that moves to the next editable field.  The user must tab three times to put the cursor into the next editable field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406581620,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-63upowwh7qb6xl3mg3rx,task_description,declined
+VisualEditor: Reconsider template tool tabbing behaviour to go to the next field (not the info or remove buttons),">>! In T70768#720791, @Jdforrester-WMF wrote:
+> Yeah, this is intentional
+
+Specifically, we did it in response to T67474.
+",1431983918,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-63upowwh7qb6xl3mg3rx,task_subcomment,NA
+VisualEditor: Reconsider template tool tabbing behaviour to go to the next field (not the info or remove buttons),*** Bug 69512 has been marked as a duplicate of this bug. ***,1414084060,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-63upowwh7qb6xl3mg3rx,task_subcomment,NA
+VisualEditor: Reconsider template tool tabbing behaviour to go to the next field (not the info or remove buttons),"Yeah, this is intentional, but maybe we should look again in case there is a way to provide the accessibility we need without being unhelpful to keyboard users.",1406582743,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-63upowwh7qb6xl3mg3rx,task_subcomment,NA
+VisualEditor: Increase indentation is not working when the list is wrapped around a left aligned image,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+4.Add a numbered list or bullet list after that
+5.Make the image left aligned 
+6.When the list gets wrapped on the right side of the image,place the cursor on one item in the list
+7.Try increasing the indentation
+
+Observed Result:
+Nothing happens.No indentation is added to the listed item.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406243820,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6k4njahaswdgisg5ovok,task_description,duplicate
+"VisualEditor: Reconsider the ""Insert"" menu because it doesn't always insert","Use case:
+
+1. On a page with a heading and some text. Put cursor at start of the paragraph after the heading.
+2. Insert a template (ends up selecting it after finishing insertion)
+3. ""Insert"" another template.
+
+Expected:
+
+A dialog should appear with the ability to decide which template to insert etc.
+
+Actual:
+
+A dialog appears to edit the selected transclusion that is already on the page.
+
+
+After being genuinely confused for a minute I realised that the confusion came from the menu label being ""Insert"". A while back, the ""Template"" button was separate on the toolbar (or under ""More"" or ""Tools"" whatever it was). Back then, like still the case with Links and Text Style, it was more natural to assume it will edit and not create a template when a template is selected already because the button would be rendered in an ""active"" (pressed-down) state (like for links and text style). However, the menu was then relabelled to ""Insert"" and the items in the ""Insert"" menu do not have an ""active"" state to help correlate with the currently selected item on the page.
+
+Perhaps we should bring back the ""active"" state for the Insert menu items, for consistency with other buttons on the toolbar.
+
+Or make it actually insert a new one at/before the current cursor position, which would mean that to edit a transclusion users then need to use the context menu instead.",1406168400,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-53ehcwcdlxysbyk5zh6q,task_description,open
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor","Might be related to bug 68492.
+
+> Discontiguous selection is not supported. rangy-core-1.3.js:2842
+>> (anonymous function) rangy-core-1.3.js:2842
+>> (anonymous function) rangy-core-1.3.js:2852
+>> (anonymous function) rangy-core-1.3.js:327
+>> init rangy-core-1.3.js:249
+>> loadHandler rangy-core-1.3.js:365
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406167740,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-el77qq7juolzlky357jd,task_description,resolved
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor",*** Bug 69616 has been marked as a duplicate of this bug. ***,1412803537,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-el77qq7juolzlky357jd,task_subcomment,NA
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor",Fixed now because we don't use Rangy any more.,1412591488,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-el77qq7juolzlky357jd,task_subcomment,NA
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor","**timdown** wrote:
+
+It's coming from a perfectly reasonable feature test in Rangy that is upsetting non-standard behaviour in Chrome. I've reluctantly put in a hideous browser sniff to work around it in the latest Rangy release.",1406934521,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-el77qq7juolzlky357jd,task_subcomment,NA
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor",*** Bug 68771 has been marked as a duplicate of this bug. ***,1406584229,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-el77qq7juolzlky357jd,task_subcomment,NA
+VisualEditor: Don't use Range.detach (is now a no-op in Chrome per revised DOM spec),"Chrome emits this notice when using VisualEditor anywhere.
+
+> 'Range.detach' is now a no-op, as per DOM (http://dom.spec.whatwg.org/#dom-range-detach).
+
+
+Looks like more than the typical deprecation, because it's been replaced with a no-op. No idea if we/Rangy are relying on it doing something. Could cause all kinds of weird state inconsistencies.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406167560,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cj3vl62yqcs5xpvo2hyk,task_description,resolved
+VisualEditor: Don't use Range.detach (is now a no-op in Chrome per revised DOM spec),"As we've now dumped Rangy, this is now FIXED.",1410404341,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cj3vl62yqcs5xpvo2hyk,task_subcomment,NA
+VisualEditor: Don't use Range.detach (is now a no-op in Chrome per revised DOM spec),"(In reply to Tim Down from comment #1)
+> Rangy has no reliance on Range.detach now. The latest release does not use
+> it at all.
+Unfortunately we still use the Rangy position plugin, which appears to have been unmaintained for a while. So we're stuck with our current version of rangy for now. Ideally I would like us to migrate away from the position plugin, then to a more recent version of Rangy. But I need to do a code audit to see is being used where.",1406935989,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cj3vl62yqcs5xpvo2hyk,task_subcomment,NA
+VisualEditor: Don't use Range.detach (is now a no-op in Chrome per revised DOM spec),"**timdown** wrote:
+
+Rangy has no reliance on Range.detach now. The latest release does not use it at all.",1406934562,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-cj3vl62yqcs5xpvo2hyk,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,"Environment- Betalabs
+
+Steps to Reproduce-
+
+For Chrome-
+1> Logged in and trying to switch to VE interface by clicking on ""Edit beta"" tab shows the spinner for a while and remains in the read mode.
+2> Now click on ""Edit Source"" tab opens the Wikieditor interface.
+3> Click on ""Edit beta"" tab again, takes you to the Read only mode instead.
+
+For FF-
+1>Logged in and trying to switch to VE interface by clicking on ""Edit beta"" tab shows the pop-up with message ""Error loading data from server: readonly: The wiki is currently in read-only mode. Would you like to retry?"", with the spinner in the background forever.
+
+For Safari-
+1>Logged in and trying to switch to VE interface by clicking on ""Edit beta"" tab shows the pop-up with message ""Error loading data from server: readonly: The wiki is currently in read-only mode. Would you like to retry?""
+
+This issue is related to Bug 59010 and Bug 60765.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406041440,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-jaospgjrwtyxcof7isza,task_description,open
+VisualEditor: Consider changing behaviour on launch when the database is locked,See also T53547,1542651968,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,See also T111217,1542651858,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,"When trying to save wikitext during a DB lock, you can just copy-paste your wikitext, save it to a text file, and paste it back when the wiki comes up again later on. I guess with VE you can still do that by using ""switch to wikitext"", but it's not nearly as obvious.",1406118852,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,"By the way, bug 68349 is tracking the issue which has turned on read-only mode. This bug can be used to look into how VE is handling it poorly and/or inconsistently.",1406052764,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,I think they mean that they can't open VE on any *.beta.wmflabs.org wiki. Those are part of the deployment-prep project in labs. The database there are read-only at the moment: no edits can be made.,1406048177,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,"Where exactly is ""in betalabs""? All instances there or which one(s)?",1406047537,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Without making any change , go to page options next to ""Save Page"" button
+3.Select the option ""Switch to source editing""
+
+Observed Result:
+The confirmation dialog to keep ot discard changes appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14213}",1405710600,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_description,resolved
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears",Verified the fix in production,1407188752,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears",Verified the fix in test2,1406324839,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears",Verified the fix in Betalabs,1406160327,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears","Change 147646 merged by jenkins-bot:
+Don't confirm if there's no changes when switching to edit source mode through the page options menu
+
+https://gerrit.wikimedia.org/r/147646",1406075190,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears","Change 147646 had a related patch set uploaded by Alex Monk:
+Don't confirm if there's no changes when switching to edit source mode through the page options menu
+
+https://gerrit.wikimedia.org/r/147646",1405715505,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Open link inspector
+3.Type something in the text field to bring up the suggestions
+4.Select one suggestion from the drop down
+5.Place the cursor at the end of the link target name in the field
+6.Press backspace to delete it
+
+Observed Result:
+Instead of deleting the link target , it takes user to the CE closing the inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405635060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_description,resolved
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487702,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Needs re-testing.,1430336168,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Can't reproduce this issue. Is it Safari-only?,1429567863,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"(In reply to Alex Monk from comment #7)
+> Can't reproduce...
+
+Can reproduce here.",1415220540,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Can't reproduce...,1415067744,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"Yeah, I sat down with Maryana and showed her how to reproduce it.",1407967453,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"I am still getting it following the exact same steps on Betalabs ,test2 and en.wiki. Infact, Roan and I reproduced it several times last week on master.",1407967354,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"I just tested this out, and I'm not seeing any issues with backspacing text in link inspector on test2 or mediawiki.org on an iPad 2 – did it get fixed somehow?",1407965137,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Double tapping on backspace takes to a blank page,1407183602,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,This is still happening in Betalabs,1406930911,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Fixed.,1406747579,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","This was mentioned on the ""[QA] Failing MobileFrontend browser tests"" thread in July. I have seen a few more  ""getaddrinfo: Name or service not known (SocketError)"" errors with Flow browser tests, and then today we got four of them. :-(
+
+See https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/65/
+
+All three tests failures in https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/65/ at Jul 16, 2014 6:26:46 PM (UTC?) were with this error.
+
+15 minutes earlier, https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/72/ also failed with ""getaddrinfo: Name or service not known (SocketError)"". The other test failure was an action that took longer than 5 seconds to complete.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405546200,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-szhiff6d7luj5xmsrczv,task_description,invalid
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","As far as I can see, this is no longer a problem. The last Flow build has 17 failed scenarios, but all of them are `timed out after 5 seconds, waiting for ... to become present (Watir::Wait::TimeoutError)`
+
+https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/590/consoleFull
+
+Closing this as invalid. Please reopen if the problem is still reproducible.",1427725948,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","(In reply to Chris McMahon from comment #3)
+> This is very likely fixed with
+
+""fixed with what"" ? HHVM improvements?
+
+Anyway, this remains a problem. From e-mail to qa mailing list:
+>>>
+Echo and Flow tests were all green Saturday Sept 6 for the first time \o/
+
+But then 4 out of 6 Flow test runs today (
+  Sep 7, 2014 8:33:11 PM
+  Sep 7, 2014 6:51:45 PM    
+  Sep 7, 2014 6:13:05 PM
+  Sep 7, 2014 3:54:07 AM
+UTC times I think)
+<<<
+Tthere was another getaddrinfo failure Sep 8, 2014 3:45:56 AM, see 
+<https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/185/>",1410159268,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","
+This is very likely fixed with",1406300559,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","Seems to be a 90 second timeout for a Flow job as well, but without the big red error message at the top of the Sauce page: https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/72/testReport/junit/(root)/Topic%20collapsing/Topics_only_view/",1405546521,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""",In at least one case this was caused by SauceLabs not receiving any command for 90 seconds: https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/lastCompletedBuild/testReport/(root)/VisualEditor%20general%20text%20markup%20features/VisualEditor_general_markup__outline_example_____Superscript____sup_General_Markup_VisualEditor_Test__sup____/,1405546411,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+VisualEditor: there is no way to change the template name without re-filling all the params,"There are templates that have a different name, but the same parameters. For example, the many lang-XX templates. If I see that the parameter text is correct, but an incorrect template was used, and the template should be {{lang-ru}} and not {{lang-be}}, I can simply change the template name. In VE I need to delete the whole template and re-add it. This is silly, but tolerable, for a template with one parameter, but there are such templates with more parameters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1405488660,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-jbzu5w4c3nerq2feaawm,task_description,open
+VisualEditor: there is no way to change the template name without re-filling all the params,Somewhat similar to T97936? To be able to chnage template name easily.,1449875494,PHID-USER-4j7xntcqqwei7izzlfnd,PHID-TASK-jbzu5w4c3nerq2feaawm,task_subcomment,NA
+VisualEditor: there is no way to change the template name without re-filling all the params,"Ideally if the templates are identical but for one piece of information ('be' vs. 'ru') then the template should be used directly ({lang|ru|…}} vs {{lang-ru|…}}, not via accessor methods, which would make this moot. But yes.",1405533424,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jbzu5w4c3nerq2feaawm,task_subcomment,NA
+VisualEditor: Suppress being able to click on links in the error messages from mis-placed local wiki customisations,"window with message
+
+Calling message [[:en:Wikipedia:Edit filter]] 
+
+For example message ""redrect to itself"" (this filtermessage in ru-wiki; in en-wiki is no such call filter, but may work with other message)
+* Edit page in VE
+* Copy page title
+* [Ξ] → Page settings → check ""Redirect this page to"" → past page title (page name of this article)
+* Press Save page (in interface) → Save page (in floating window)
+
+* Start showing Edit filter message (1 image 1)
+* Clik on link in this message - new page open in this floating window and this window i can't close or go back to message (image 2)
+
+Link should open in a new window
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows 8.1
+**Platform**: PC
+
+**Attached**: {F14349}",1405438800,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-uav3b7isy6kd7g73ifwt,task_description,resolved
+VisualEditor: Suppress being able to click on links in the error messages from mis-placed local wiki customisations,"This is no longer a problem.
+
+* We no longer use iframes for dialogs, which caused the funny page-in-page effect.
+* Any links in customizable error messages are automatically changed to open in a new browser window/tab when clicked.",1562026815,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-uav3b7isy6kd7g73ifwt,task_subcomment,NA
+VisualEditor: Suppress being able to click on links in the error messages from mis-placed local wiki customisations,"This is caused by an unsuitable use of a template to provide links without a target=""_window"". Maybe we should prevent clicking on the links instead?",1405448152,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uav3b7isy6kd7g73ifwt,task_subcomment,NA
+VisualEditor: Suppress being able to click on links in the error messages from mis-placed local wiki customisations,"Created attachment 15941
+window after click on link
+
+**Attached**: {F14350}",1405438878,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-uav3b7isy6kd7g73ifwt,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","Invoke VE from iOS Safari on tablet,
+
+Make changes to page in VE 
+
+Open second tab, load another website, 
+
+Switch back to tab with VE instance, page is reloaded, and changes are lost",1405412400,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-tkjl47hcghbp2eadvr32,task_description,resolved
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",The work done in T57370 is probably sufficient to solve this problem.,1520342734,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","Having poked about with this both locally and in production, I think we can declare this done alongside T57370. Assigning to Ed because he did a lot of the work, both recently and over the past few years.",1519854251,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","#Performance-Team is for any task worked on by the performance team. (Known issues in software we maintain, and improvements anywhere else if we're involved.)
+
+#Performance is a generic tag for other projects to track known problems causing bad performance. (Not usually improvements/enhancements.) In addition, projects with their own subproject or workboard column for performance, normally don't also tag with Performance (similar to Tech Debt). I've untagged this and others with #VisualEditor-Performance.",1494453011,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","#Performance-Team is for any task worked on by the performance team. (Known issues in software we maintain, and improvements anywhere when we assiset on the matter.)
+
+#Performance is a generic tag for all other projects to track known problems causing bad performance. (Not usually improvements/enhancements.) In addition, projects with their own subproject or workboard column for performance, normally don't also tag with Performance (similar to Tech Debt). I've untagged this and others with #VisualEditor-Performance.",1494452258,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","I don't know, what is the difference between //VisualEditor-Performance// and //Performance//, but //Performance// is used in similar VE issues and here is missing",1494450065,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",Auto-save issue is T57370,1439375732,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",Also the beahviour is the same on both devices: the tab is only expunged when the device runs out of memory.,1439125042,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","A long term solution would be to store editing state in localStorage. I think there's an existing bug for that.
+
+The best we can do at the moment is warn the user. The most likely time they'll switch is if they're using Citoid, and they go to get a URL to copy.
+",1439124589,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",">>! In T70017#782815, @Eloquence wrote:
+> What is the behavior in Chrome/Android?
+
+Similar, but not 100% reproducible, I think it depends on how much memory the tab is using, which probably corresponds to the size of the article you're editing. chrome might also just try to keep more than one tab alive concurrently ",1416871042,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",">>! In T70017#782815, @Eloquence wrote:
+> What is the behavior in Chrome/Android?
+
+From what I remember of our testing, it's the same, controlling for RAM size. Mostly this is a performance / resource use issue.",1416871006,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",What is the behavior in Chrome/Android?,1416870939,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","""don't close me bro""",1408659536,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","(In reply to Jared Zimmerman (WMF) from comment #4)
+> This might not be able to resolved as the bug is written (stop safari from
+> reloading) but the current experience for the user in unacceptable. We need
+> a solution. possibly server side drafts or using localstorage on the device.
+> Feel free to rewrite the bug, but we can't ignore this issue.
+
+Well, this is what Apple wants to happen. We already say to the browser ""don't just close me"". Apple has decided in its wisdom to ignore that. We can try to take steps to make it less-terrible, but the underlying issue can't be fixed except upstream…",1408657375,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","This might not be able to resolved as the bug is written (stop safari from reloading) but the current experience for the user in unacceptable. We need a solution. possibly server side drafts or using localstorage on the device. Feel free to rewrite the bug, but we can't ignore this issue.",1408560637,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","Unfortunately, on investigation, this is something that we can't avoid; it's the built-in behaviour of Safari that we have no control over, sadly. Marking as ""WONTFIX"" but it's more ""CANTFIX"".",1408560322,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","Yep, I know this one might be difficult but it obviously makes doing references on mobile basically impossible. glad to see we're prioritizing this.",1408383575,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","This is ""normal"" behaviour from Safari, but we need to investigate if we can prevent (or at least discourage) it somehow.",1406748019,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+One-click system for setting user preferences,"This was an interesting comment from WhatamIdoing on T69826, so I thought I'd split it out for its own discussion.
+
+> Changing default user preferences means overriding the choices of 
+> registered editors who actually want the feature (including thousands of 
+> editors who voluntarily opted-in before MediaViewer was made avaialble 
+> by default).  
+> 
+> It's too bad that MediaWiki doesn't have a good one-click system for 
+> changing prefs, like a ""Click here to enable X"" button or pop-up.  It'd be 
+> so much easier than telling hundreds of users ""Go to Special:Preferences, 
+> click to this tab, scroll halfway down, find this item, tick the box, scroll 
+> all the way down, save the page.""
+
+--------------------------
+**See Also**:
+* {T34811}
+* {T69883}",1405075320,PHID-USER-uia2q3o33h5pb5lf7exz,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_description,open
+One-click system for setting user preferences,"As GET requests (navigating to a URL) now have to be read-only, this feature would at best be two clicks. The link would need to take you to a page that had a confirm button that triggered the POST request to update your preference.
+
+The only way to make this one click would be to use JavaScript, but then you aren't talking about a simple wiki link.",1668241823,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"(In reply to WhatamIdoing from comment #5)
+> I think I can:
+> 
+> Tell me the exact wikitext I need to type to tell an editor at the English
+> Wikipedia's Help Desk these things:
+> 
+> ""Click HERE to disable MediaViewer""
+
+Don't write ""click here"".
+
+http://www.w3.org/QA/Tips/noClickHere
+
+[…]
+
+> ""Click HERE to set your gender to female""
+
+whatever ajax appears should be clear on privacy implications (value is published) and what exactly it's used for. (software strings not stats, etc) also, remember a11y, aria, etc.",1407204968,PHID-USER-7ey733eainlhx5xqp4d3,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"I think I can:
+
+Tell me the exact wikitext I need to type to tell an editor at the English Wikipedia's Help Desk these things:
+
+""Click HERE to disable MediaViewer""
+
+""Click HERE to opt into the Beta Feature VisualEditor""
+
+""Click HERE to set your default image size to 300 px""
+
+""Click HERE to set your gender to female""
+
+""Click HERE to turn on Twinkle""
+
+""Click HERE to turn off Navpops""
+
+""Click HERE to set your default image size to 300 px""
+
+""Click HERE to set your gender to female""",1405140553,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"(In reply to James Forrester from comment #3)
+> I think you have mis-understood this request; it's asking for a consistent,
+> MW-provided system to do this that works the same way for all preferences
+
+The WebAPI works for all preferences. Can you clarify the requirements, as you're so sure about them?",1405125973,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"(In reply to Nemo from comment #2)
+> I don't understand this bug. We have plenty of one-click preference change
+> systems, which alter the preferences via WebAPI. As one prominent example,
+> see [[mw:ULS]].
+
+I think you have mis-understood this request; it's asking for a consistent, MW-provided system to do this that works the same way for all preferences, and which each feature can trivially provide, not specific ad-hoc hacks like ULS etc. use which mean users have to learn them each time.",1405125178,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"I don't understand this bug. We have plenty of one-click preference change systems, which alter the preferences via WebAPI. As one prominent example, see [[mw:ULS]].
+I recommend filing a separate bug for each preference you want one such control for, specifying if it can also supplant the Special:Preferences checkbox (cf. bug 32811; keep bug 31882 in mind).
+
+Unless requirements for this request to be considered fulfilled are clarified, I propose RESOLVED WORKSFORME.",1405125064,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"Thanks for filing this.
+
+I should note that what would be most functional is a system that lets me post a link (meaning a wikilink or a URL) that represents the command.  I want anyone to be able to do this, not just the devs.  Something like:
+
+""Click [[Special:ChangePreferences/scary-code-name-for-pref |here]] to toggle the tickbox for that pref""
+
+(or whatever format is necessary) would be great.",1405094928,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+"TemplateData: Deprecated param w/out description text ""no description"" isn't in italic grey","**Author:** `gabrasca2`
+
+**Description:**
+VisualEditor deprecated text
+
+When a param is indicated as ""deprecated"": true and it has no description, in the TemplateData parameters table the text ""no description"" isn't in italic grey.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14398}",1404988140,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-53i433yt4zo2nejhcsxm,task_description,resolved
+"TemplateData: Deprecated param w/out description text ""no description"" isn't in italic grey","Verified in beta with http://en.wikipedia.beta.wmflabs.org/wiki/Template:ET_test
+",1422561370,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-53i433yt4zo2nejhcsxm,task_subcomment,NA
+"TemplateData: Deprecated param w/out description text ""no description"" isn't in italic grey","Change 184440 merged by jenkins-bot:
+Show ""no description"" in italic grey also for deprecated parameters
+
+[[https://gerrit.wikimedia.org/r/184440]]",1421459215,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-53i433yt4zo2nejhcsxm,task_subcomment,NA
+"TemplateData: Deprecated param w/out description text ""no description"" isn't in italic grey","Change 184440 had a related patch set uploaded (by Ricordisamoa):
+Show ""no description"" in italic grey also for deprecated parameters
+
+[[https://gerrit.wikimedia.org/r/184440]]
+
+#patch-for-review",1421097785,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-53i433yt4zo2nejhcsxm,task_subcomment,NA
+VisualEditor: Making an image Frame-left/Frame-right redraws the highlight beyond CE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it frame-left or frame-right.
+
+Observed Result:
+
+The highlight for the image goes beyond the page
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14208}",1404864480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ysnk6kht23okwwdp5gp5,task_description,open
+[DO NOT USE] Support non-image media (tracking) [superseded by #VisualEditor-MediaWiki-Media],We currently don't. We should.,1404850380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6hasow53qizwpe3vbpsp,task_description,resolved
+[DO NOT USE] Support non-image media (tracking) [superseded by #VisualEditor-MediaWiki-Media],Merged into #VisualEditor-MediaWiki-Media.,1422403165,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6hasow53qizwpe3vbpsp,task_subcomment,NA
+[DO NOT USE] Support non-image media (tracking) [superseded by #VisualEditor-MediaWiki-Media],*** Bug 67689 has been marked as a duplicate of this bug. ***,1404851265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6hasow53qizwpe3vbpsp,task_subcomment,NA
+"VisualEditor: While inserting an image for the first time, the label for the button in Media Settings dialog should be ""Insert {image|animation|audio|video}"" instead of ""Apply Changes""","Right now while inserting an image, the button that shows up in the Media Settings dialog is ""Apply Changes"", it should be ""Insert"" instead , since there is no change here rather insertion.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1404849960,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-swo2rxiy6wgm2jbww3gv,task_description,resolved
+"VisualEditor: While inserting an image for the first time, the label for the button in Media Settings dialog should be ""Insert {image|animation|audio|video}"" instead of ""Apply Changes""","Checked in test2/production - for inserting a new media, the button will be always 'Insert'.  Marking as Resolved/Verified.",1422409223,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-swo2rxiy6wgm2jbww3gv,task_subcomment,NA
+"VisualEditor: While inserting an image for the first time, the label for the button in Media Settings dialog should be ""Insert {image|animation|audio|video}"" instead of ""Apply Changes""","Expanded, made dependent on bug 67690 for us to be able to tell media types apart.",1404850446,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-swo2rxiy6wgm2jbww3gv,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Copied from my Russian Wikipedia talk page: https://ru.wikipedia.org/wiki/%D0%9E%D0%B1%D1%81%D1%83%D0%B6%D0%B4%D0%B5%D0%BD%D0%B8%D0%B5_%D1%83%D1%87%D0%B0%D1%81%D1%82%D0%BD%D0%B8%D0%BA%D0%B0:Keegan_(WMF)#Bug_report_11
+
+I filled TemplateData for Шаблон:Малая планета
+
+early, template with comments inserted in articles
+{{Малая планета
+<!-- Основной блок -->
+ | param        = 
+<!-- Орбитальные характеристики -->
+ | param        = 
+<!-- Физические характеристики -->
+ | param        = 
+}}
+now if i deleted comments https://ru.wikipedia.org/w/index.php?title=(87)_Сильвия&diff=64040824&oldid=62184664 then i can see parameters in VE editor
+but if comments still in text then VE editor for template staying on ""Загрузка..."" (""Load..."") and don't show parameters. sample: (25143) Итокава
+Sunpriat 08:40, 6 июля 2014 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1404797580,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-zrsnll62nd3qae3uw3jx,task_description,resolved
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Change 169732 merged by jenkins-bot:
+Bug 67657: Add normalized parameter names to templates
+
+https://gerrit.wikimedia.org/r/169732",1414693263,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Marc, thanks for the clarification. I think the name 'paramWT' contributed to my confusion. It sounds more like the value to me. How about 'key.wt'? That could be extended with key.html etc in the future.
+
+We should definitely include the wikitext for the key, as there is no good way to properly handle editing otherwise. VE shouldn't just pretend that a parameter was not templated, when it was. Those comments also often contain information that the user might be interested in.",1414683407,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Gabriel, 'wt' still contains the original wikitext for the parameter value as it's always done, we're just adding a new paramWt attribute that only shows up if the original parameter name wikitext is different from the actual parameter name that would be used in expansion.
+
+I think the example was a little confusing because the comment in the param name is the same as the param value, sorry for that. Another example, this time with html in it too:
+
+> {{ec<!--tpl comment-->ho|unnamed param value|1<!--param name comment-->2=Param ''value''}}
+
+> {
+> 	'parts': [ {
+> 			'template': {
+> 				'target': {
+> 					'wt': 'ec<!--tpl comment-->ho',
+> 					'href': '../Template:Echo'
+> 				},
+> 			'params':
+> 			{
+> 				'1': {
+> 					'wt': ""unnamed param value"",
+>                                       'html': 'unnamed param value'
+> 				}
+> 			},
+> 			{
+> 				'12': {
+> 					'paramWt': '1<!--param name comment-->2',
+> 					'wt': ""Param ''value''"",
+>                                       'html': 'Param <i>value</i>'
+> 				}
+> 			},
+> 			'i': 0
+> 		}
+> 	} ]
+> }
+
+If paramWt isn't actually needed by VE, maybe we could even not output it at all in data-mw, as it's also kept in data-parsoid…",1414662288,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)",I'm not a fan of making 'wt' return something that's not the original wikitext. How will the need for a normalized name evolve with the 'html' parameter format? It's relatively straightforward to ask for .textContent.,1414624831,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","This looks fine to me. We don't really need paramWt in VE anyway, we don't really care that there was a comment in there, as long as Parsoid can preserve it when the template is edited. So with your proposed change, we wouldn't even have to change anything, because we'd just ignore (and preserve) paramWt.",1414622939,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","In the patch I've uploaded, the normalized parameter name is used as the entry for the parameter info and the original parameter wikitext only appears if different, in the 'paramWt' attribute. So James' example would output as
+
+> {
+> 	'parts': [ {
+> 			'template': {
+> 				'target': {
+> 					'wt': 'ec<!--Ho-->ho<!--Ha!-->',
+> 					'href': '../Template:Echo'
+> 				},
+> 			'params':
+> 			{
+> 				'12': {
+> 					'paramWt': '1<!--Foo!-->2',
+> 					'wt': 'Foo'
+> 				}
+> 			},
+> 			'i': 0
+> 		}
+> 	} ]
+> }
+
+Will that be enough, or should the paramWt be included for each parameter? Most of them will be the same anyway and that would increase page size a lot…",1414599796,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Change 169732 had a related patch set uploaded by Marcoil:
+Bug 67657: Add normalized param names to templates
+
+https://gerrit.wikimedia.org/r/169732",1414599557,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","So… this is asking if Parsoid would consider making the 'params' block of their API give a 'normalised' version of the parameter name, possibly with a 'target' version as well like they do with templates' names?
+
+E.g.:
+
+Wikitext
+
+> {{ec<!--Ho-->ho<!--Ha!-->|1<!--Foo!-->2=Foo}}
+
+
+Current Parsoid output:
+
+> {
+> 	'parts': [ {
+> 			'template': {
+> 				'target': {
+> 					'wt': 'ec<!--Ho-->ho<!--Ha!-->',
+> 					'href': '../Template:Echo'
+> 				},
+> 			'params':
+> 			{
+> 				'1<!--Foo!-->2': {
+> 					'wt': 'Foo'
+> 				}
+> 			},
+> 			'i': 0
+> 		}
+> 	} ]
+> }> 
+
+Requested Parsoid output:
+
+> {
+> 	'parts': [ {
+> 			'template': {
+> 				'target': {
+> 					'wt': 'ec<!--Ho-->ho<!--Ha!-->',
+> 					'href': '../Template:Echo'
+> 				},
+> 			'params':
+> 			{
+> 				'12': {
+> 					'target': '1<!--Foo!-->2',
+> 					'wt': 'Foo'
+> 				}
+> 			},
+> 			'i': 0
+> 		}
+> 	} ]
+> }
+
+… or similar?",1405108181,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","For comparison, Parsoid already strips out html comments from the template title. It should do so for parameter names as well (in addition to trimming whitespace).",1404936594,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Created attachment 15885
+Screenshot of bug.
+
+Screenshot for editing the following on on https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet?veaction=edit
+
+{{Wikimedia engineering project information
+| name        =VisualEditor<!-- This HTML comment should not get deleted or modified. -->
+| description <!-- ignored comment describing the parameter -->= Creating a visual editor for MediaWiki, other platforms and the Web at large
+| logo        =VisualEditor-logo.svg
+| ..
+}}
+
+**Attached**: {F14096}",1404935921,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Hm.. it sounds like the bug report says that html comments inside TemplateData conflict with VisualEditor.
+
+However I think this might've been a confusion in translation. I think the reported problem is that when the wikitext has html comments in the transclusion, that Parsoid/VE is including those as part of the template name.
+
+E.g. that when invoking:
+
+{{ Echo
+| 1 <!-- One -->  = Foo
+}}
+
+That the transclusion dialog and/or Parsoid is saying there is a parameter called ""! <!-- One -->"", and renders that as actual text in the label for the UI.
+
+Rephrasing bug accordingly. I think this is something that should be normalised by Parsoid as VisualEditor shouldn't need to know what html comments mean in wikitext.",1404935846,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","The inspector for <syntaxhighlight /> node immediately closes after opening on Opera 12. I don't yet know why, but I am going to find out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404473940,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3vjexhza3sstfguvlk4h,task_description,declined
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","Seems to have been fixed at some point, I can no longer reproduce.",1416090593,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip",Also affects the comment inspector in standalone.,1410962848,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","Ooh. It only closes itself when opened by clicking the context tooltip. Opening it by double-clicking the node or by pressing Enter when it's selected keeps the inspector open.
+
+After editing it, when the context tooltip is displayed again, clicking it also will always work correctly. Fascinating.",1410962687,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","(In reply to Bartosz Dziewoński from comment #1)
+> * On Opera 12 `rangy.getSelection( this.getElementDocument() ).anchorNode` is
+>   null, but on other browsers it returns the .ve-ce-surface-paste element
+
+Oh, and I forgot the best part: not always. Sometimes the selection is the same as on other browsers. I've somehow caused that several times when debugging, but I have absolutely no idea how.",1404480728,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","When you try opening the inspector:
+
+* The 'focusout' event is eventually fired on .ve-ce-surface-paste
+* ve.ce.Surface.prototype.onFocusChange is called
+* On Opera 12 `rangy.getSelection( this.getElementDocument() ).anchorNode` is
+  null, but on other browsers it returns the .ve-ce-surface-paste element
+* Therefore `hasFocus` is false instead of true
+* The document gets blurred, which triggers the inspector to hide some ten
+  levels of abstraction down.
+
+
+No idea why the selection gets lost. Perhaps the inspector should reselect?",1404480463,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+VisualEditor: Changing language of a <syntaxhighlight /> node doesn't load styles for new language,"Changing language of a <syntaxhighlight /> node doesn't load styles for new language. 
+
+SyntaxHighlight_GeSHi defines a module for each supported language (in the format ""ext.geshi.language.$lang""), VE should ensure that the appropriate module is present. Not sure how the content is updated, but the information about required modules should be provided in the ParserOutput and by the action=parse API.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58388",1404435480,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-24czob2fjkxcqpu77r5w,task_description,resolved
+VisualEditor: Changing language of a <syntaxhighlight /> node doesn't load styles for new language,"* https://gerrit.wikimedia.org/r/214078 (branch master): #mw1.26wmf12
+",1435186822,PHID-USER-n4kveqwjjlpsb6ydn73h,PHID-TASK-24czob2fjkxcqpu77r5w,task_subcomment,NA
+VisualEditor: Changing language of a <syntaxhighlight /> node doesn't load styles for new language,"Change 214078 merged by jenkins-bot:
+Add VisualEditor support
+
+[[https://gerrit.wikimedia.org/r/214078]]",1435183387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-24czob2fjkxcqpu77r5w,task_subcomment,NA
+VisualEditor: Changing language of a <syntaxhighlight /> node doesn't load styles for new language,"Change 214078 had a related patch set uploaded (by Jforrester):
+Add VE support for syntax highlighting
+
+[[https://gerrit.wikimedia.org/r/214078]]
+",1432909764,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-24czob2fjkxcqpu77r5w,task_subcomment,NA
+VisualEditor: [Regression wmf12] The highlight for centered images is taking 100% width,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it centre aligned
+4.Keep it selected
+
+Observed Result:
+The highlight for the centered image is taking 100% width
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14351}",1404427980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-57aftv3xzvmq2c2u7ztm,task_description,resolved
+VisualEditor: [Regression wmf12] The highlight for centered images is taking 100% width,"Ha. Yes, fixed by Ed as part of his FocusableNode fixes.",1410804238,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-57aftv3xzvmq2c2u7ztm,task_subcomment,NA
+VisualEditor: [Regression wmf12] The highlight for centered images is taking 100% width,Can't reproduce. Must have been fixed in the meantime.,1410804157,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-57aftv3xzvmq2c2u7ztm,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Go to Insert>Media
+
+Observed Result:
+""No results found"" message appearing even before entering a search term inside Media Settings dialog
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14200}",1404338520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lyvz6pfbh5iamln4kped,task_description,resolved
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",Verified the fix in production,1411070175,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",Verified the fix in test2,1410554364,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",Verified the fix in Betalabs,1409960770,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 158584 merged by jenkins-bot:
+Abort promises before sending new ones in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/158584",1409957781,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 158584 had a related patch set uploaded by Mooeypoo:
+[wip] Abort promises before sending new ones in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/158584",1409894768,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Okay, it seems the problem is half fixed with the above commit. Now the ""No results"" message no longer appears on top of found results. However, it does seem to pop up and then disappear between searches. 
+
+I'm going to investigate the issue further.",1409886865,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 158530 merged by jenkins-bot:
+Hide ""no results"" messaage in media search widget
+
+https://gerrit.wikimedia.org/r/158530",1409872157,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 158530 had a related patch set uploaded by Mooeypoo:
+Hide ""no results"" messaage in media search widget
+
+https://gerrit.wikimedia.org/r/158530",1409871525,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",*** Bug 70273 has been marked as a duplicate of this bug. ***,1409669754,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","As I mentioned in the dup bug, it's seen in Firefox. In Chrome I see the 'no results' found flicker slightly, but the main issue is in Firefox.",1408660473,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","And I still can't see the issue there. I load ""Insert media"" and I see the search image page empty / processing and then ""No results found"".
+
+I don't see ""No results found"" before the search is done, I only see it after the page searched for a moment and found nothing (as intended)
+
+Tested on Chrome Version 36.0.1985.143 and Firefox 31.0
+
+What am I missing here?",1408660170,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","As in the duplicate bug, page is http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit 
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69877",1408659614,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","I can't replicate this. If you're still seeing this, can you give me the page this is still happening on?",1408659152,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",*** Bug 69877 has been marked as a duplicate of this bug. ***,1408657052,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","I just noticed this is again appearing in Betalabs, when you first open Media Settings dialog and the page name is in the search field,the ""No Result Found"" appears.Also, it appears when you click on ""Change Image"" button",1407353031,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","This is fixed in Betalabs but not on test2, moving it to the next sprint.",1407191690,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 150001 merged by jenkins-bot:
+Use $.when() in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/150001",1406787239,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 150001 had a related patch set uploaded by Mooeypoo:
+Use to $.when() in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/150001",1406575985,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Oops. 
+
+Wrong fix to the wrong bug (ignore the above comment)",1406389505,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",This is fixed by this change: https://gerrit.wikimedia.org/r/#/c/149392/,1406389451,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+VisualEditor:  Parameter data doesn't always end up in the right parameter box in Firefox,"Report from Jay8g about a bug that may be very hard to reproduce:
+
+""After adding a parameter in the (advanced) template dialog, the focus briefly shifts to the previously added (edited) parameter before going to the one just added. This has led to me occasionally (about one in ten parameter additions) typing (generally just one character) in the wrong box""
+
+""I would type something *immediately* after clicking the parameter button and it would only happen occasionally""
+
+
+Jay's running Firefox 30 on Windows 7.  I've been unable to reproduce this, but I probably haven't tried enough times or been fast enough.  I've been wondering whether this might be easier to reproduce on an old, slow computer.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404324840,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-7qab3gnaeczpqu366xpc,task_description,open
+VisualEditor:  Parameter data doesn't always end up in the right parameter box in Firefox,"The issue is confirmed - it is most noticeable in FF35 on Windows. I've attached a screencast for FF35 on Mac - the problem is noticeable as ""jumpiness"" of parameters in Template dialog. 
+
+Important - to reproduce the bug, add parameter that will be placed **after** previously entered parameter, e.g. after parameter AA add parameter ZZ. Then you can see more clearly that the cursor will be placed momentarily into the previous field.
+
+{F56327}",1425599467,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-7qab3gnaeczpqu366xpc,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,"When we try to add this template:
+
+http://en.wikipedia.org/wiki/User:Jay8g/sandbox/Template:Airline fleet table/Start
+
+the TemplateData does not appear in the dialog.
+
+If we add the doc subpage directly:
+
+http://en.wikipedia.org/wiki/User:Jay8g/sandbox/Template:Airline fleet table/Start/doc 
+
+then TemplateData appears.
+
+We have already made at least three null edits to the template.  I assume that the problem is due to the namespace, but it's not bug 52609, because the template itself adds correctly to the page:  
+
+{{User:Jay8g/sandbox/Template:Airline fleet table/Start}}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404322800,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-3shl4mcz2khwbu4uvoja,task_description,declined
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,AFAWCT this should work… marking as such.,1405559011,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,Possibly. I had to fiddle around with things like that to check that this was actually working on my machine.,1404762915,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,"(In reply to Alex Monk from comment #2)
+> I don't think this is valid... I can't reproduce it on my machine (with
+> different pages)
+
+Could it be a caching issue?",1404762864,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,I don't think this is valid... I can't reproduce it on my machine (with different pages),1404762624,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,"(In reply to WhatamIdoing from comment #0)
+> We have already made at least three null edits to the template.  I assume
+> that the problem is due to the namespace, but it's not bug 52609, because
+> the template itself adds correctly to the page:  
+> 
+> {{User:Jay8g/sandbox/Template:Airline fleet table/Start}}
+
+I'm pretty sure it was still fine adding to the page in bug 52609.",1404322953,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,"This may be related to bug 42986:  VisualEditor and Parsoid autoconvert URLs in the external link format to local links, including for interlanguage and other interwiki links.
+
+This means that if you paste https://outreach.wikimedia.org/wiki/Example in as your link on one of the Wikipedias, it gets saved as [[outreach:Example]].  
+
+This is fabulous and should be kept. 
+
+However, if the local wiki doesn't recognize the converted prefix for the link, then the result is a redlink.  At the moment, office.wiki doesn't know about the existence of outreach.wiki, but links are converted anyway.  
+
+The result is that pasting https://outreach.wikimedia.org/wiki/Example as a link on office.wiki gets saved as [[outreach:Example]], and when you click on the resulting redlink, it takes you to the non-existent page https://office.wikimedia.org/wiki/Outreach:Example  
+
+This is not so fabulous.  
+
+The most flexible system is to find out which wikis are known locally, and only convert those.  The most immediate solution is probably to tell office.wiki where to find outreach.wiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404235020,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ibnihv52xnshteoxrd3r,task_description,open
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,"> It's because ""Outreach"" is a namespace name on officewiki. So this is not a MW bug, but a bug probably in Parsoid.
+
+I'd call that a bug in officewiki configuration. They shouldn't use a name reserved for an interwiki in their local namespaces...",1429713699,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-ibnihv52xnshteoxrd3r,task_subcomment,NA
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,"It's because ""Outreach"" is a namespace name on officewiki. So this is not a MW bug, but a bug probably in Parsoid. It shouldn't auto-convert external links to interwikis when the interwiki matches the name or alias of a local namespace.",1405408442,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-ibnihv52xnshteoxrd3r,task_subcomment,NA
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,"This is done in Parsoid, and should normally use the wiki-local interwiki table.
+
+It is listed in https://office.wikimedia.org/w/api.php?action=query&meta=siteinfo&siprop=interwikimap&format=json, so the Parsoid behavior looks correct. Interestingly it is listed twice though: once as 'outreach', and once at 'outreachwiki'. When I manually change the wikitext link to [[outreachwiki:Example]], it is rendered as expected.
+
+So to me this looks either like a configuration issue in officewiki. It could also be a bug in the PHP parser, which only recognizes one of two configured interwiki prefixes.",1404342253,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ibnihv52xnshteoxrd3r,task_subcomment,NA
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,Does this happen in VE or Parsoid? If the latter it should be moved.,1404339857,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ibnihv52xnshteoxrd3r,task_subcomment,NA
+VisualEditor: Prompt for edit summary preference breaks the save dialog,"If a user has the preference ""Prompt me when entering a blank edit summary"" selected, VisualEditor's save dialog has to be closed and reopened to work. The ""Save"" button is greyed out even when an edit summary is entered.
+
+To reproduce:
+1. Enable Preferences>Editing>tick Prompt me when entering a blank edit summary
+2. Attempt to save a VE edit and the prompt for an edit summary comes up, with save not an option
+3. Enter an edit summary
+4. Save is still not an option
+5. Exit out of the dialog by clicking X and click save again
+6. You can now save your edit with an edit summary
+
+Firefox 30 on Mac OS X Mavericks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404185940,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_description,resolved
+VisualEditor: Prompt for edit summary preference breaks the save dialog,"Change 143326 merged by jenkins-bot:
+After showing missing edit summary error, mark the dialog as not pending anymore
+
+https://gerrit.wikimedia.org/r/143326",1404232141,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_subcomment,NA
+VisualEditor: Prompt for edit summary preference breaks the save dialog,This was probably an oversight on my part in Gerrit change 135945,1404226652,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_subcomment,NA
+VisualEditor: Prompt for edit summary preference breaks the save dialog,"Change 143326 had a related patch set uploaded by Alex Monk:
+After showing missing edit summary error, mark the dialog as not pending anymore
+
+https://gerrit.wikimedia.org/r/143326",1404226461,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_subcomment,NA
+VisualEditor: Prompt for edit summary preference breaks the save dialog,Sounds like we need to code in that the you-must-set-an-edit-summary message is a recoverable error.,1404187302,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_subcomment,NA
+MediaWiki:Visualeditor-wikitext-warning-link should link mediawiki.org,"On translatewiki.net I see a red link in messages and this page won't exist on most wikis, just link https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Formatting by default. See blocked bug for example and remember, Brion veto'ed the simple solution i.e. interwiki link [[mediawikiwiki:Special:MyLanguage/Help:Formatting]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404044760,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-difb2qmugpstitptxrln,task_description,resolved
+MediaWiki:Visualeditor-wikitext-warning-link should link mediawiki.org,"Heh, WP:BEANS applies. Thanks.",1417038167,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-difb2qmugpstitptxrln,task_subcomment,NA
+MediaWiki:Visualeditor-wikitext-warning-link should link mediawiki.org,"Change 175886 merged by jenkins-bot:
+Point wikitext markup link in warning to MW.org
+
+[[https://gerrit.wikimedia.org/r/175886]]",1416966201,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-difb2qmugpstitptxrln,task_subcomment,NA
+MediaWiki:Visualeditor-wikitext-warning-link should link mediawiki.org,"Change 175886 had a related patch set uploaded (by Jforrester):
+Point wikitext markup link in warning to MW.org
+
+[[https://gerrit.wikimedia.org/r/175886]]
+
+#patch-for-review",1416956749,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-difb2qmugpstitptxrln,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"Key events fire without key codes (understandable as you can 'swipe' whole words) and backspace fires no key[up|down|press] event at all.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403994660,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_description,open
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"There is a still  bug where no events are fired if the cursor is in an empty span, and deleting across a paragraph.",1539445981,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,Looks like on latest Chrobile/iOSafari we get input+beforeinput events with an inputType of 'deleteContentBackward'. This should be enough to fix this (assuming we can preventDefault).,1539363966,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"Note that Android 4.4's WebView is based on the Chromium engine, and unlike the standalone Chrome app it only gets updated with the OS. Might want to check whether the  stock Android browser on non-Google-branded 4.4.x devices is also affected. (Nexus devices seem to leave out the AOSP default browser in favor of Chrome, but I see a customized version on Samsung Galaxy branded devices for instance.)",1404400580,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"OS update is not an issue, just app.",1404381778,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"(In reply to Ed Sanders from comment #6)
+> It looks like the above commit to Chrome for Mobile has been merged, which
+> solves the most serious case (no event fired at all).
+
+It doesn't ""solve"" it perfectly, as OS update lag for Android devices is notoriously slow (or non existent), and app update take-up is apparently poor. Is there a sane work-around we could do?
+
+> We are still left with the general problem of IME deletion.
+
+Yeah. :-(",1404353204,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"It looks like the above commit to Chrome for Mobile has been merged, which solves the most serious case (no event fired at all). We are still left with the general problem of IME deletion.",1404340111,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"""No key event is generated when the BACKSPACE key is pressed outside of composition, in other words, when AdapterInputConnection.deleteSurroundingText is called. In the reported bug, since the text field is empty, thus IME is not in the composition mode, thus pressing the BACKSPACE key triggers deleteSurroundingText and thus no key event is generated.
+
+A cl that generates key events in deleteSurroundingText with a dummy keycode is under review at https://codereview.chromium.org/348413003/.""",1403996659,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"Not quite true, see http://jsbin.com/alAKaNaZ/5
+
+Backspace fires a keydown with keyCode 0 (same as every other key event) but not when whitespace is deleted.
+
+See https://code.google.com/p/chromium/issues/detail?id=184812",1403996593,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"See https://code.google.com/p/chromium/issues/detail?id=118639 for pitchfork waving, including a complaint from the Microsoft Office Web Apps team who are having the same problem.",1403995499,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"There is an 'input' event which fires, but this doesn't solve the problem of prevent the default backspace behaviour.",1403995446,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,Oy.,1403994743,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"Setup- FF 30.0. 
+Steps to Reproduce-
+1>Launch the FF browser.  And go to your user page in Beta labs.
+2>Click on “Edit Source” tab.  Click anywhere on the Wikitext Editor pane.
+3>Now while the cursor is still blinking in the editor pane, press the keyboard shortcut for the VE editor tab which is “Alt+Shift+v”.  
+
+Actual Result-When the keyboard shortcut for the VE editor tab i,e. “Alt+Shift+v” is pressed, it just scrolls the window down, while the Wikitext Editor pane is still open and instead the “Show Changes” button gets highlighted(which apparently has the same keyboard shortcut combination).  The same behavior was observed in test2 environment for FF browser. But in Safari and Chrome no such similar behavior was found.
+
+Expected Result-When pressed the keyboard shortcut of “Alt+Shift+v” should access the Edit beta tab and open the VE pane.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**: {T54701}",1403905980,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3gt4ltdm5464h2so4dbt,task_description,duplicate
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"Just to on the safe side, this is not the same as T114793?",1459687141,PHID-USER-4j7xntcqqwei7izzlfnd,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"I'd like to see meta-V in read mode be VisualEditor, and meta-V in wikitext editor be the diff.",1445014779,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"We could have a different accesskey from action=edit (or just a new one in general), but that seems like it would confuse people.",1410125531,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"(In reply to Alex Monk from comment #2)
+> The 'Show changes' button has accesskey=v, so there's a conflict. Chrome
+> just goes for the first one on the page and breaks the 'Show changes'
+> shortcut, Firefox moves between the two. Not sure what we should do about
+> that.
+
+Oh, yeah, that thing. *sighs* I guess this would get fixed with a switch to a single edit tab, but I'm not sure what we could do in advance of that.",1405008025,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"The 'Show changes' button has accesskey=v, so there's a conflict. Chrome just goes for the first one on the page and breaks the 'Show changes' shortcut, Firefox moves between the two. Not sure what we should do about that.",1404943447,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"Yeah, Ctrl+Alt+v (on a Mac) works fine for me in read mode, but not in wikitext edit mode, where it just selects the tab… Something odd here.",1404773531,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Deleting a block item highlights the previous line,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which contains a block item like reflist or image
+2.Delete the image
+
+Observed Result:
+A highlight appears from the end of the previous line covering up the rest of the line.
+
+Instead of highlighting, upon deleting the block item the cursor should just appear at the end of the previous line.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14275}",1403901720,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_description,resolved
+VisualEditor: Deleting a block item highlights the previous line,Verified the fix in production,1405027416,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_subcomment,NA
+VisualEditor: Deleting a block item highlights the previous line,Verified the fix in betalabs and test2,1404771578,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_subcomment,NA
+VisualEditor: Deleting a block item highlights the previous line,"Change 142806 merged by jenkins-bot:
+Fix up selection after deletion if at non-content offset
+
+https://gerrit.wikimedia.org/r/142806",1403990939,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_subcomment,NA
+VisualEditor: Deleting a block item highlights the previous line,"Change 142806 had a related patch set uploaded by Esanders:
+Fix up selection after deletion if at non-content offset
+
+https://gerrit.wikimedia.org/r/142806",1403968234,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_subcomment,NA
+"VisualEditor: Block items converted to inline initially show a flash of highlight trying to select the previous line, and then the selection normalises to just the item","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it Frameless-Left or Basic-Left
+4.Now uncheck the wrapping option.
+
+
+Observed Result:
+The previous line gets highlighted for a split second then the highlight goes away.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403901180,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-pz2ixq5zf5t25xrb4rxy,task_description,resolved
+"VisualEditor: Block items converted to inline initially show a flash of highlight trying to select the previous line, and then the selection normalises to just the item",Can't reproduce. Very old bug so probably been fixed.,1701963876,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-pz2ixq5zf5t25xrb4rxy,task_subcomment,NA
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,"1. Create a page with {{echo|foo}} in the text somewhere
+2. Observe that the word ""foo"" is highlighted and clickable and all those good things
+3. Inspect ""foo"", and change the parameter to ""bar""
+4. Click the rerendering
+
+Note that there is no highlight, you're able to select parts of the word (!), it's not inspectable, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403824740,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_description,resolved
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,"Change 140439 merged by jenkins-bot:
+[BREAKING CHANGE] Remove generated content node wrappers
+
+https://gerrit.wikimedia.org/r/140439",1404170273,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_subcomment,NA
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,Confirmed fix,1403906711,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_subcomment,NA
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,"Change 140439 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Remove generated content node wrappers
+
+https://gerrit.wikimedia.org/r/140439",1403906694,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_subcomment,NA
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,What about after https://gerrit.wikimedia.org/r/140439 ?,1403827630,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_subcomment,NA
+VisualEditor should support redirects to sections on a page,"Steps to reproduce:
+
+1.  Go to Page settings and tick the box to make a redirect.
+
+2.  Type in not just a page title, but also a section:  Example#Foo
+
+3.  Now what?  If I click ""Example"" in the list, it deletes the #Foo part.
+
+
+It turns out that if you click outside the page settings dialog, that it actually will accept this, but it looks impossible.
+
+Then when you ""apply changes"", the redirect isn't visible on the page (T63861) so you can't tell whether it worked or did anything at all.",1403805420,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-eegih6kooypkdgwbf43y,task_description,resolved
+VisualEditor should support redirects to sections on a page,"This seems to work the right way these days. If you input a title+section, the same is shown as the first element of the suggestions (but only if a page by that title exists). {F7052264}",1490714782,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-eegih6kooypkdgwbf43y,task_subcomment,NA
+VisualEditor should support redirects to sections on a page,"So, when you have a title+section link in the text box, and the suggestions show the page name that's currently in there, an extra suggestion should be added for the full title+current section? I think anything more than that would be T52881",1481110936,PHID-USER-mvx4x7ywk2flsaku2dbk,PHID-TASK-eegih6kooypkdgwbf43y,task_subcomment,NA
+VisualEditor should support redirects to sections on a page,This very likely would use some (magical) technology that would be needed to fix {T52881}.,1481055579,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eegih6kooypkdgwbf43y,task_subcomment,NA
+VisualEditor:  Broken Kloutify browser extension injects garbage into the page,"https://en.wikipedia.org/w/index.php?title=Lobstick&curid=43120379&diff=614082884&oldid=614013920
+
+The user edited the page twice, resulting in two copies of this:
+
+<div id=""kloutify""><div></div><div id=""kloutify-score"">10</div></div>
+
+at the top of the page.  The ""10"" is visible on the page.
+
+http://kloutify.com/ says that this can be installed on Firefox, Chrome, and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403562600,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ruav2ogzbcqvzadctvdr,task_description,resolved
+VisualEditor:  Broken Kloutify browser extension injects garbage into the page,"Change 163968 merged by jenkins-bot:
+Blacklist div[id = kloutify] as well
+
+https://gerrit.wikimedia.org/r/163968",1412114701,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ruav2ogzbcqvzadctvdr,task_subcomment,NA
+VisualEditor:  Broken Kloutify browser extension injects garbage into the page,"Change 163968 had a related patch set uploaded by Alex Monk:
+Blacklist div[id = kloutify] as well
+
+https://gerrit.wikimedia.org/r/163968",1412114584,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ruav2ogzbcqvzadctvdr,task_subcomment,NA
+VisualEditor: Offer ability to save without exiting (for saving your work in the middle of an editing session),"Opening VisualEditor can be slow for some pages/some users.  Please offer the option of saving without exiting.
+
+(Original suggestion:  https://en.wikipedia.org/w/index.php?diff=613298543&oldid=613210959)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403195460,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jaeqm7s2wtu2hyzgjf62,task_description,open
+VisualEditor: Offer ability to save without exiting (for saving your work in the middle of an editing session),"There is now T57370, but that is only for the purpose of crash recovery, and only if the exact same tab is reopened, which does not satisfy this use case.",1525335642,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-jaeqm7s2wtu2hyzgjf62,task_subcomment,NA
+VisualEditor: Offer ability to save without exiting (for saving your work in the middle of an editing session),Interesting idea.,1403220029,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jaeqm7s2wtu2hyzgjf62,task_subcomment,NA
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)","Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Type a text 
+3.Tap on the ""Return"" key from the keyboard
+
+Observed Result:
+Instead of adding a newline and moving the cursor to it, it deletes the preceding text.
+
+Device:Nexus 7(Android 4.4.2)
+Environment:Production (en.wiki) and Betalabs",1403049840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_description,open
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)",The current Android version of Nexus 7 is 6.0.1 (Marshmallow). Shall the task description be updated to reflect that?,1604088026,PHID-USER-bf7nnwcm4i6wicvxtb77,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_subcomment,NA
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)","This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592584225,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_subcomment,NA
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)","The previous comments don't explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status.
+
+//(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}. If this task is stalled on an upstream project, then the #upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task needs retesting, then the #testme tag should be added. If this task is either out of scope and nobody should ever work on this, or nobody else managed to reproduce the problem described in this task, then this task should have the ""Declined"" status.)//",1590761764,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_subcomment,NA
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)",Needs re-testing.,1430336368,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),"Steps to reproduce:
+
+1.Open any page with Mobile VE in Nexus 7(Android 4.4.2)
+2.Type a text
+3.Save the page
+
+Observed Result:
+The edit does not get saved
+
+Device:Nexus 7(Android 4.4.2)
+Environment: Production (en.wiki) and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403047800,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xttfxhpiryw6znoqo7lj,task_description,resolved
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),"Checked this issue , in en.wiki and test2 , not happening anymore. closing this one.",1430339892,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),"Was this specifically with that device, and not any others tested?",1429567642,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),Seems to be a mis-tag.,1405008111,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),"Change 145222 had a related patch set uploaded by BryanDavis:
+[WIP] Enable HHVM debugging REPL
+
+https://gerrit.wikimedia.org/r/145222",1404968989,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),Try to recheck in case this was a deployment issue?,1404330034,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+"VisualEditor Mobile: Tapping at the end of each link, does copy-paste of preceding link text in Nexus 7(Android 4.4.2)","Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Tap at the end of a link
+
+Observed Result:
+The link gets copied at the position your cursor was on and it will keep continue doing that everytime you place your cursor at the end of extended link.
+
+See the screenshot attached
+
+Device: Nexus 7(Android 4.4.2)
+Environment:Production (en.wiki) and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403047020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-lrdaa764ev2rnhtfh6c7,task_description,duplicate
+"VisualEditor Mobile: Tapping at the end of each link, does copy-paste of preceding link text in Nexus 7(Android 4.4.2)",Needs re-testing.,1430336075,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lrdaa764ev2rnhtfh6c7,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Right now the HTML created for
+- headings specified using Wikitext (e.g. ""=="")
+- headings created using HTML tags (e.g. ""<h2>"")
+look basically the same.
+
+- Both have a wrapping heading element (without class or id)
+- Both contain a <span> of class ""mw-headline""
+
+The only (but major) difference is that sections created by Wikitext are editable and therefore contain an additional <span> of class ""mw-editsection"".
+
+It would be nice if there was an easy possibility to directly differentiate those types of headers on a CSS level (e.g. by an additional class applied to the parent <h*> element)
+
+
+This would make it much easier to create custom CSS and JS since often one would only want to style ""true"" (that is editable) article headers created by Wikitext instead of custom created headers that are mostly used for design of e.g. project pages.
+Right now such CSS and JS often erroneously styles all headers the same, regardless of how the headers were created, often resulting in unintentional appearance.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: enhancement",1402834020,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_description,open
+Make it possible to distinguish Wikitext headings and HTML headings,"It does seem a bit strange though to simultaneously push for all media files to have a convoluted `typeof`-based syntax and for headings to not have `typeof`-based syntax. Though I do think that `<figure>` conversion as implemented was a massive mistake and we ended up with a lot of CSS bloat because of it that could’ve been avoided if classes were used, so I don’t have a problem with using them generally.",1735855955,PHID-USER-3ljmcrqixyljk2wy63jb,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"I forgot to note this here at the time, but I talked to some folks from the Content Transform team after I proposed these patches, who didn't like them very much because the semantic meaning of these attributes wasn't clear and it would also require changes to the Parsoid HTML spec with backwards-compat implications. Their counterproposal was adding some class name or some other attribute to only the ""raw"" HTML headings instead (internal Slack link: https://wikimedia.slack.com/archives/C024Z8K9CAU/p1705359054223579 – sorry, not publicly accessible). I'd be happy with that too, I just didn't get around to trying to implement it.
+
+Substantially the same idea was also proposed in T13555#9896561 by @Od1n.",1722710671,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990778 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/extensions/DiscussionTools@master] Detect HTML headings using 'typeof=""mw:Heading""'%%%
+Reason:
+%%%I'm not working on this at the moment.%%%
+https://gerrit.wikimedia.org/r/990778",1709839372,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990777 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/extensions/VisualEditor@master] Allow 'typeof=""mw:Heading""' on Parsoid headings%%%
+Reason:
+%%%I'm not working on this at the moment.%%%
+https://gerrit.wikimedia.org/r/990777",1709839365,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990776 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/services/parsoid@master] Add 'typeof=""mw:Heading""' to wikitext headings%%%
+Reason:
+%%%I'm not working on this at the moment.%%%
+https://gerrit.wikimedia.org/r/990776",1709839359,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990775 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/core@master] Add 'typeof=""mw:Heading""' to wikitext headings%%%
+Reason:
+%%%I'm not working on this at the moment.%%%
+https://gerrit.wikimedia.org/r/990775",1709839354,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990778 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/DiscussionTools@master] Detect HTML headings using 'typeof=""mw:Heading""'%%%
+https://gerrit.wikimedia.org/r/990778",1705357839,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990777 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Allow 'typeof=""mw:Heading""' on Parsoid headings%%%
+https://gerrit.wikimedia.org/r/990777",1705357829,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990776 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/services/parsoid@master] Add 'typeof=""mw:Heading""' to wikitext headings%%%
+https://gerrit.wikimedia.org/r/990776",1705357823,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990775 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/core@master] Add 'typeof=""mw:Heading""' to wikitext headings%%%
+https://gerrit.wikimedia.org/r/990775",1705357816,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"It is possible (if inadvisable) to have whitespace at the start of a paragraph in HTML; to readers it is mostly invisible. In MediaWiki, because whitespace at the start of a paragraph has magic meaning, Parsoid `<nowiki />`s it. To avoid users doing this accidentally, it might be nice to design a way to flag to the user what they've done when they create these.",1402788000,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g2k2n2sjdlne5edkxabr,task_description,resolved
+Spaces at the start of a paragraph aren't very obvious,"Thanks, Guillaume! I'll be watching.",1434448096,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,">>! In T68628#1366507, @Elitre wrote:
+> Even on Office wiki? If not, I have a diff from June 12th about that.
+
+I had the same question earlier today, and @Jdforrester-WMF said it might be related to JavaScript that was cached in the user's browser. It may take a few weeks for the issue to completely disappear.",1434390205,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"Even on Office wiki? If not, I have a diff from June 12th about that.",1434389638,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"VisualEditor now strips leading whitespace by design, so this task has become obsolete. Closing.",1434389028,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"It's still happening:  https://en.wikipedia.org/w/index.php?diff=660662487&oldid=657477479  The original had only one space between paragraphs, but I usually add two in wikitext (""English spacing""), so there may have been two spaces at the time that I hit return to split the paragraphs.",1430691888,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"This issue came up 4 times out of 100 reviewed diffs, and accounted for ⅔ of problematic diffs on the English Wikipedia this week ( T94767#1225878 ). I see this being a possible point of contention during a wider roll-out.
+
+Based on those numbers, I'm re-nominating this issue as a blocker for further discussion.",1429725232,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"{T78137} sounds like an interesting approach.
+
+I tested now and it seems like the leading spaces can still be created and displayed in the editor, but magically disappear when the MediaWiki page is saved.",1429614294,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"@Jdforrester-WMF by the way, was this officially rejected as blocker, or was the blocker tag removed for another reason?",1428429815,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,">>! In T68628#1150309, @Jdforrester-WMF wrote:
+> 
+> I have reverted the title change because it is **completely** wrong. ""Remove nowikied spaces at the beginning of a paragraph unless the user manually inserted them"" means ""please corrupt pages on load"", and is absolutely the wrong this to do. VisualEditor is not in the business of ""fixing"" pages. If you click edit, then click save without making changes, there should never ever be any difference, or we've failed.
+
+That's not at all what I meant. I didn't suggest we fix unrelated spaces; I thought the accompanying description (which you moved to T93935) made that clear. Sorry for the misunderstanding.",1428429657,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"I'm having second thoughts about my earlier all-clear.  It's possible that this problem only arises if the wikitext uses French spacing (two spaces after the full stop).  If that's the case—if it strips one space but leaves the second—then my test yesterday is inadequate, because I didn't check what the wikitext looks like.",1427410533,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"I've restored this task back to what it's about, which is a **design** issue about discouraging odd user behaviour, and has essentially nothing to do with `<nowiki />`s, which are already dealt with in multiple other tasks.
+",1427312907,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,">>! In T68628#1150358, @Whatamidoing-WMF wrote:
+> This appears to be fixed now (same browser/same article test).
+> 
+> I think that a title of ""Stop adding nowiki'd spaces at the start of newly
+> split paragraphs"" would capture the ask better.  I don't really want to see
+> the spaces (although that would be better than having them present but
+> invisible); I want the stray spaces to not be present in the first place.
+
+That's a different task, which I have created: {T93935}.",1427312590,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"This appears to be fixed now (same browser/same article test).
+
+I think that a title of ""Stop adding nowiki'd spaces at the start of newly
+split paragraphs"" would capture the ask better.  I don't really want to see
+the spaces (although that would be better than having them present but
+invisible); I want the stray spaces to not be present in the first place.",1427312389,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,">>! In T68628#1146900, @gpaumier wrote:
+> Are there any valid use cases for keeping those white spaces at the beginning of a paragraph? Otherwise I think we should just remove them. If we don't want to remove them automatically on save, then as @Whatamidoing-WMF suggested in T68628#967908 , we should at least remove the space when editing, so that the nowikied space is added //only if// the user explicitly inserts it.
+
+I have reverted the title change because it is **completely** wrong. ""Remove nowikied spaces at the beginning of a paragraph unless the user manually inserted them"" means ""please corrupt pages on load"", and is absolutely the wrong this to do. VisualEditor is not in the business of ""fixing"" pages. If you click edit, then click save without making changes, there should never ever be any difference, or we've failed.",1427312461,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"I have reverted the title change because it is **completely** wrong. ""Remove nowikied spaces at the beginning of a paragraph unless the user manually inserted them"" means ""please corrupt pages on load"", and is absolutely the wrong this to do. VisualEditor is not in the business of ""fixing"" pages. If you click edit, then click save without making changes, there should never ever be any difference, or we've failed.",1427312066,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,,1427236528,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,,1427236492,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"Are there any valid use cases for keeping those white spaces at the beginning of a paragraph? Otherwise I think we should just remove them. If we don't want to remove them automatically on save, then as @Whatamidoing-WMF suggested in T68628#967908 , we should at least remove the space when editing, so that the nowikied space is added //only if// the user explicitly inserts it.",1427236470,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"The nowikied space also persists if a user then removes the newline. See https://en.wikipedia.org/w/index.php?diff=653301980 for an example in which:
+* an existing nowikied space at the beginning of a paragraph now lives in the middle of a paragraph;
+* a new nowikied space was added at the beginning of a paragraph.",1427236275,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"I'm adding Parsoid to this, because Subbu thought that it might be solvable there.",1424153311,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"This is still happening.  I'm still not doing anything exceptional:  I put my cursor in between two sentences and press the Return key.  This still should not be happening. If I want to start a paragraph with a space, then I should have to actually press the space bar.
+
+https://en.wikipedia.org/w/index.php?diff=prev&oldid=641792115",1420862401,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"No, they actually are not shown.  
+
+Download the screenshot and pull it into Preview on your Mac. Zoom in six times, scroll way over to the red ovals, and use ""Tools:Annotate:Line"" to draw a vertical line down the leading edge of those paragraphs.  Hold down your shift key to keep the line straight.  Set the line to the thinnest option in the toolbar.  
+
+Now count the pixels between your line and the beginnings of each letter on those paragraphs.  The straight edge on the 'r' of 'raised', the 'E' of 'Experience', and the 'M' of 'Modern' are very convenient for this.  
+
+There is no visible difference.  Where I drew my line, I found exactly one pixel between my line and the start of each character.  Something that does not display as even a single pixel on a reasonably typical laptop is properly described as ""not shown"".",1410805643,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,They actually are shown – but it's very hard to see them. Re-wording.,1403742784,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"Created attachment 15656
+Nowiki tags enclose spaces, but no spaces are shown in VisualEditor
+
+**Attached**: {F13610}",1402788280,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"Highlighting entire paragraphs and applying or removing list formatting should consistently apply or remove formatting, currently some items are ignored.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42115",1402434120,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_description,declined
+VisualEditor: Reconsider list functions' application and clearing,"(In reply to Jared Zimmerman (WMF) from comment #4)
+> I'd love for us to do a set of user tests around this. Just because
+> word/gdocs/openoffice does something doesn't mean it is the correct thing to
+> do. Not saying we got it wrong, but I think hearing specific feedback on
+> this from users might be useful. 
+
+Absolutely. Just flagging that we've already spent many dozens of hours going back and forth about this with users and designers. It's not remotely a green field. :-)
+
+> I agree that a table or a link isn't ""formatting"" in this sense, but lists
+> don't fit as neatly into that category for me, I'd love to hear from users.
+
+Definitely.",1403745763,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"@abbey, can you create a card in the backlog to help the VE team validate some of the assumptions around formatting behavior best practices please.",1403745535,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"I'd love for us to do a set of user tests around this. Just because word/gdocs/openoffice does something doesn't mean it is the correct thing to do. Not saying we got it wrong, but I think hearing specific feedback on this from users might be useful. 
+
+I agree that a table or a link isn't ""formatting"" in this sense, but lists don't fit as neatly into that category for me, I'd love to hear from users.",1403745437,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"(In reply to Jared Zimmerman (WMF) from comment #2)
+> Nested list items…
+> 
+> Shouldn't clear formatting clear nested list items styles as well? That
+> would be my expectation.
+
+No. Lists, tables, blockquotes, headers, preformatted etc. are all considered ""structural"" changes rather than ""styles"".
+
+Right now the selection-action behaviour for links is modelled after a number of different editors with some insanely complex edge-cases (e.g. applying ""make numbered list"" to a selection covering some numbered list items, some paragraphs, some nested bullet list sub-items, and some partials of the above).",1403744085,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"Nested list items…
+
+Shouldn't clear formatting clear nested list items styles as well? That would be my expectation.",1403743131,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"(In reply to Jared Zimmerman (WMF) from comment #0)
+> Highlighting entire paragraphs and applying or removing list formatting
+> should consistently apply or remove formatting, currently some items are
+> ignored.
+
+Which items?",1403742919,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","For list of repositories see https://www.mediawiki.org/wiki/Repositories_with_Ruby_code
+
+For more information see https://www.mediawiki.org/wiki/Manual:Coding_conventions/Selenium#expect_or_should
+
+Still not implemented in:
+
+- mediawiki/extensions/ArticleFeedbackv5
+- mediawiki/extensions/CirrusSearch
+- mediawiki/extensions/ContentTranslation
+- mediawiki/extensions/Flow
+- mediawiki/extensions/Gather
+- mediawiki/extensions/MultimediaViewer
+- mediawiki/extensions/PdfHandler
+- mediawiki/extensions/Translate
+- mediawiki/extensions/TwnMainPage
+- mediawiki/extensions/UniversalLanguageSelector
+- mediawiki/extensions/UploadWizard
+
+```
+$ grep --include *.rb  -R -F '.should' .
+
+mediawiki/vagrant/mediawiki/extensions/ArticleFeedbackv5/tests/browser/features/step_definitions/aftv5_steps.rb:    page.yes_element.when_present.should be_visible
+...
+mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/page_steps.rb:    result.status.should eq 200
+...
+mediawiki/vagrant/mediawiki/extensions/ContentTranslation/tests/browser/features/step_definitions/basic_mt_steps.rb:  on(ContentTranslationPage).translation_editor_element.text.should == text
+...
+mediawiki/vagrant/mediawiki/extensions/Flow/tests/browser/features/step_definitions/description_steps.rb:    page.description.content.should eq(content)
+...
+mediawiki/vagrant/mediawiki/extensions/Gather/tests/browser/features/step_definitions/recent_collections_steps.rb:  on(GatherRecentPage).collection_one_hundred_element.should exist
+...
+mediawiki/vagrant/mediawiki/extensions/MultimediaViewer/tests/browser/features/step_definitions/mmv_options_steps.rb:  on(E2ETestPage).mmv_options_menu_disable_element.should be_visible
+...
+mediawiki/vagrant/mediawiki/extensions/PdfHandler/tests/browser/features/step_definitions/pdf_steps.rb:  on(PdfPage).download_as_pdf_element.should exist
+...
+mediawiki/vagrant/mediawiki/extensions/Translate/tests/browser/features/step_definitions/manage_translator_sandbox_steps.rb:	on(UserPage).babel_box_has_languages?(languages).should be_true
+...
+mediawiki/vagrant/mediawiki/extensions/TwnMainPage/tests/browser/features/step_definitions/signed_in_and_approved_user_steps.rb:		page.number_of_translators_element.should be_visible
+...
+mediawiki/vagrant/mediawiki/extensions/UniversalLanguageSelector/tests/browser/features/step_definitions/accept_language_steps.rb:  on(MainPage).main_page_element.text.should == text
+...
+mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/chunked_upload_steps.rb:  on(UploadPage).continue_element.when_present(300).should be_visible
+...
+```
+
+",1402321140,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_description,declined
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",Because of {T139740} this is unlikely to ever get done.,1495811105,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","A tool like these could automate the process:
+
+http://xinminlabs.github.io/synvert/rules/
+https://github.com/yujinakayama/transpec",1446720289,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Removed release-engineering, since it does not belong there.
+Removed patch-for-review, since all related patches (as far as I can see) are merged or abandoned.",1436283720,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",Removed,1427714305,PHID-USER-t4rpicnsgzxayalzj6k6,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","@jagori79 are you working on this? If not, please remove yourself from ""assigned to"". Thanks.",1427291727,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","@Physikerwelt: no problem. I think it would be a lot of noise if we created 20 or so subtasks, but it is something to consider for the future tasks.",1426863595,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Sorry for closing this bug. I thought it was only about the Math extension, because the project Math was specified. I think in the future it might be better to add subtasks for each extension.",1426862947,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186947 merged by jenkins-bot:
+Use rspec-expectations ""expect"" syntax instead of ""should"" syntax
+
+[[https://gerrit.wikimedia.org/r/186947]]",1426861426,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",,1443645049,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",,1426858450,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186949 merged by jenkins-bot:
+Change RSpec 2 should syntax to RSpec 3 expect syntax
+
+[[https://gerrit.wikimedia.org/r/186949]]",1424517099,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 187269 merged by jenkins-bot:
+RSpec 3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/187269]]",1424516577,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 179072 merged by jenkins-bot:
+Refactor code for RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/179072]]",1424115983,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","I was not able to test this for the Math Extension:
+See my comment in gerrit:
+""
+I could not test the effects of this change. I tried to run the tests on labs-vagrant instance following the guide at https://www.mediawiki.org/w/index.php?title=Quality_Assurance/Browser_testing/Running_tests#Running_VisualEditor_browser_tests_via_labs-vagrant However, even on master I get the following output https://gist.github.com/physikerwelt/5761056c077c02a8c636
+""",1422524733,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 187269 had a related patch set uploaded (by Jagori79):
+RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/187269]]
+
+#patch-for-review",1422486258,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186949 had a related patch set uploaded (by Jagori79):
+Changing should to expect syntax
+
+[[https://gerrit.wikimedia.org/r/186949]]
+
+#patch-for-review",1422362252,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186947 had a related patch set uploaded (by Jagori79):
+RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/186947]]
+
+#patch-for-review",1422360779,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186947 had a related patch set uploaded (by Jagori79):
+RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/186947]]
+
+#patch-for-review",1422359801,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",@Cmcmahon can you do a code review for this change?,1422094796,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 179072 had a related patch set uploaded (by Physikerwelt):
+Refactor code for RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/179072]]
+
+#patch-for-review",1418281843,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 146712 abandoned by Jagori79:
+WIP [BrowserTest] Use rspec-expectations expect syntax instead of should syntax
+
+Reason:
+I am abandoning this change as already been implemented for Visual Editor.I will make the expect syntax changes on other codebase as suggested by Chris on the QA mailing list.
+
+[[https://gerrit.wikimedia.org/r/146712]]",1417655722,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Thanks,Yes,will work on the other repositories.",1417091501,PHID-USER-t4rpicnsgzxayalzj6k6,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","If the change you were working on is already implemented, it probably makes sense to abandon your commit. We have plenty of other repositories where the change should be implemented. :)
+
+https://github.com/wikimedia/mediawiki-selenium#links",1416995330,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Zeljko:I see the changes already implemented for Visual editor code,should I abandon the part which I was working on :https://gerrit.wikimedia.org/r/#/c/146712/
+
+I had restored it .",1416908094,PHID-USER-t4rpicnsgzxayalzj6k6,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 146712 restored by Jagori79:
+WIP [BrowserTest] Use rspec-expectations expect syntax instead of should syntax
+
+Reason:
+Restoring
+
+[[https://gerrit.wikimedia.org/r/146712]]",1416907322,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 146712 abandoned by Zfilipin:
+WIP [BrowserTest] Use rspec-expectations expect syntax instead of should syntax
+
+Reason:
+No activity on the commit in months. Please restore if you plan to work on this.
+
+https://gerrit.wikimedia.org/r/146712",1415097965,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 147423 merged by jenkins-bot:
+Use rspec-expectations expect syntax instead of should syntax
+
+https://gerrit.wikimedia.org/r/147423",1405696369,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 147423 had a related patch set uploaded by Zfilipin:
+Use rspec-expectations expect syntax instead of should syntax
+
+https://gerrit.wikimedia.org/r/147423",1405685794,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 146712 had a related patch set uploaded by Jagori79:
+WIP [BrowserTest] Use rspec-expectations expect syntax instead of should syntax
+
+https://gerrit.wikimedia.org/r/146712",1405498000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","(In reply to Željko Filipin from comment #1)
+> Pick a repository:
+> 
+> https://github.com/wikimedia/mediawiki-selenium#links
+> 
+> Replace all expect syntax with should syntax.
+
+  Editing the above line to :
+   > Replace all should syntax with expect syntax.",1402752239,PHID-USER-t4rpicnsgzxayalzj6k6,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","@Zeljko: I am not able to assign the bug to myself.Could you please look into it.
+I cannot see the ""Edit"" link.",1402562879,PHID-USER-t4rpicnsgzxayalzj6k6,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",,1443640356,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",,1402321835,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"We should have a sane way of including screenshots with skins and displaying them in the UI. These would be useful on Special:Preferences, in the installer when it will ask you which skin to choose, on Special:Version…
+
+I coded up something that works but is probably not a good idea at https://gerrit.wikimedia.org/r/#/c/138110/ – this would just add support for a new key to $wgExtensionCredits.
+
+One interesting issue is, what resolution should we expect the screenshot to be?
+
+Another one is, how do we display it? Unless we want to push the whole thing through ResourceLoader CSS handling (which would be extremely silly), we need to know the URL path where the screenshot is available (relative to $wgStylePath?). This is not obvious :(
+
+**See Also**: {T70331}
+
+----
+
+**The new convention**:
+* Every skin can include screenshots in the screenshots/ directory, which will be shown in the installer (and possibly elsewhere in the future).
+* It should include at least one 1280x800px screenshot, plus any extra screenshots if your skin looks different at different screen resolutions or with different configuration options.
+* You should disable any extensions or uncommon configuration options when taking the screenshots.
+* Make sure not to include any copyrighted content in the screenshots – here's some public domain content you can use:
+** Page content: P5878
+** Site logo: the MediaWiki logo (`$wgLogo = ""/w/resources/assets/mediawiki.png"";`)
+** Images: [[https://commons.wikimedia.org/wiki/File:Turner,_J._M._W._-_The_Fighting_Téméraire_tugged_to_her_last_Berth_to_be_broken_(edit).jpg|1]] [[https://commons.wikimedia.org/wiki/File:Bierstadt_Albert_Indian_Summer_Hudson_River.jpg|2]] [[https://commons.wikimedia.org/wiki/File:Meisje_met_de_parel.jpg|3]]
+**Examples**:
+{F9028486,float} {F9028461,float} {F9028439,float}
+
+----",1402099020,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ro4iqgaoik67vus6rg36,task_description,resolved
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"No. I almost did it, but to upload them there, you'd have to find out the right license for every single one separately, and that was more effort than I was willing to put into it. The skins can each have different licenses, they're not all on GPL like MediaWiki.",1512230552,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"This task has been pointed from {T179709}, where we are trying to take screenshots of skins that doesn't have one yet in their mediawiki.org skin page. Have the pictures taken during the work done for this task been inserted on mw.org?",1512169724,PHID-USER-aswxykknolbbycawydkz,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"It would be good to write this up as a seleniumJS script (see VisualEditor/build/screenshots.js), because skins change.",1502651765,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,Also documented at https://www.mediawiki.org/wiki/Manual:Skinning_Part_2#Screenshots,1502485233,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"With these patches merged, 24 skins out of 42 in our version control have screenshots.
+
+The others ones are read-only repos, immediately fatal when enabled, don't seen to have any styles at all, or have other big problems.
+
+| Skin | Status |
+| -- | -- |
+| apex | {icon check, color=green}
+| Athena | 
+| Blueprint | 
+| BlueSky | {icon check, color=green}
+| BlueSpiceSkin | 
+| Bouquet | {icon check, color=green}
+| CologneBlue | {icon check, color=green}
+| CustomPage | 
+| Daddio | {icon check, color=green}
+| DeskMessMirrored | {icon check, color=green}
+| Dusk | {icon check, color=green}
+| DuskToDawn | 
+| Empty | 
+| erudite | {icon check, color=green}
+| Example | {icon check, color=green}
+| Gamepress | 
+| GreyStuff | {icon check, color=green}
+| HasSomeColours | 
+| Mask | {icon check, color=green}
+| Material | 
+| mediawiki-strapping | 
+| Metrolook | {icon check, color=green}
+| MinervaNeue | {icon check, color=green}
+| Modern | {icon check, color=green}
+| MonoBook | {icon check, color=green}
+| Nimbus | {icon check, color=green}
+| Nostalgia | {icon check, color=green}
+| p2wiki | 
+| Poncho | 
+| Refreshed | 
+| Schulenburg | 
+| Splash | {icon check, color=green}
+| Synagonism | 
+| Tempo | {icon check, color=green}
+| Timeless | {icon check, color=green}
+| Tomas | 
+| Truglass | {icon check, color=green}
+| Vector | {icon check, color=green}
+| VectorV2 | 
+| webplatform | {icon check, color=green}
+| WoOgLeShades | 
+| WPtouch | {icon check, color=green}
+",1502482673,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371548 merged by jenkins-bot:
+[mediawiki/skins/Timeless@master] Add skin screenshots for the installer
+
+[[https://gerrit.wikimedia.org/r/371548]]
+",1502482195,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371537 merged by jenkins-bot:
+[mediawiki/skins/MonoBook@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371537]]
+",1502481680,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371538 merged by jenkins-bot:
+[mediawiki/skins/Nimbus@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371538]]
+",1502481679,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371539 merged by jenkins-bot:
+[mediawiki/skins/Nostalgia@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371539]]
+",1502481678,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371540 merged by jenkins-bot:
+[mediawiki/skins/Splash@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371540]]
+",1502481561,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371541 merged by jenkins-bot:
+[mediawiki/skins/Tempo@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371541]]
+",1502481560,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371542 merged by jenkins-bot:
+[mediawiki/skins/Truglass@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371542]]
+",1502481557,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371544 merged by jenkins-bot:
+[mediawiki/skins/webplatform@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371544]]
+",1502481545,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371545 merged by jenkins-bot:
+[mediawiki/skins/WPtouch@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371545]]
+",1502481489,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371546 merged by jenkins-bot:
+[mediawiki/skins/GreyStuff@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371546]]
+",1502481384,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371536 merged by jenkins-bot:
+[mediawiki/skins/Modern@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371536]]
+",1502481383,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371534 merged by jenkins-bot:
+[mediawiki/skins/Metrolook@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371534]]
+",1502481297,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371530 merged by jenkins-bot:
+[mediawiki/skins/Dusk@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371530]]
+",1502481204,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371529 merged by jenkins-bot:
+[mediawiki/skins/DeskMessMirrored@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371529]]
+",1502481201,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371528 merged by jenkins-bot:
+[mediawiki/skins/Daddio@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371528]]
+",1502481173,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371527 merged by jenkins-bot:
+[mediawiki/skins/CologneBlue@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371527]]
+",1502481172,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371526 merged by jenkins-bot:
+[mediawiki/skins/Bouquet@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371526]]
+",1502481171,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371548 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Timeless@master] Add skin screenshots for the installer
+
+[[https://gerrit.wikimedia.org/r/371548]]
+",1502481037,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371533 merged by jenkins-bot:
+[mediawiki/skins/Mask@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371533]]
+",1502481012,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371532 merged by jenkins-bot:
+[mediawiki/skins/Example@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371532]]
+",1502480942,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371531 merged by jenkins-bot:
+[mediawiki/skins/erudite@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371531]]
+",1502480856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371543 merged by jenkins-bot:
+[mediawiki/skins/Vector@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371543]]
+",1502480855,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371535 merged by jenkins-bot:
+[mediawiki/skins/MinervaNeue@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371535]]
+",1502480731,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371546 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/GreyStuff@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371546]]
+",1502480464,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371545 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/WPtouch@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371545]]
+",1502480286,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371544 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/webplatform@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371544]]
+",1502480273,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371543 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Vector@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371543]]
+",1502480260,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371542 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Truglass@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371542]]
+",1502480252,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371541 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Tempo@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371541]]
+",1502480240,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371540 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Splash@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371540]]
+",1502480228,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371539 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Nostalgia@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371539]]
+",1502480215,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371538 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Nimbus@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371538]]
+",1502480206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371537 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/MonoBook@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371537]]
+",1502480188,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371536 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Modern@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371536]]
+",1502480179,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371535 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/MinervaNeue@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371535]]
+",1502480171,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371534 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Metrolook@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371534]]
+",1502480158,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371533 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Mask@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371533]]
+",1502480146,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371522 merged by jenkins-bot:
+[mediawiki/skins/BlueSky@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371522]]
+",1502480131,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371532 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Example@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371532]]
+",1502480127,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371531 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/erudite@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371531]]
+",1502480119,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371530 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Dusk@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371530]]
+",1502480106,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371529 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/DeskMessMirrored@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371529]]
+",1502480094,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371525 abandoned by Bartosz Dziewoński:
+Add skin screenshot for the installer
+
+Reason:
+Whoops, duplicate.
+
+[[https://gerrit.wikimedia.org/r/371525]]",1502480085,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371528 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Daddio@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371528]]
+",1502480083,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371524 abandoned by Bartosz Dziewoński:
+Add skin screenshot for the installer
+
+Reason:
+Whoops, duplicate.
+
+[[https://gerrit.wikimedia.org/r/371524]]",1502480079,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371527 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/CologneBlue@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371527]]
+",1502480074,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371521 merged by jenkins-bot:
+[mediawiki/skins/apex@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371521]]
+",1502480057,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371526 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Bouquet@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371526]]
+",1502480056,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371525 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/BlueSky@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371525]]
+",1502480050,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371524 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/apex@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371524]]
+",1502480002,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371522 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/BlueSky@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371522]]
+",1502479669,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371521 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/apex@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371521]]
+",1502479593,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,<3,1502474625,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"| MinervaNeue | {F9036540} | {F9036540,layout=link}",1502474050,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,@matmarex probably needs MobileFrontend to be installed. It's still a bit weird in that way. :(,1502466933,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"I tried to include it, but it's shown me some error message so I skipped it. Maybe I'll look at it again later and try to actually read what the error says. I don't think it's a major problem if it's inconsistent; I won't be taking screenshots of all skins forever so they will soon enough become inconsistent anyway.",1502466327,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,Can #MinervaNeue get in on the screenshot  action? I cam generate one but it's  likely to be inconsistent..,1502461519,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,You're awesomeeeee <3,1502422602,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Here are 24 screenshots for all the skins in our version control that I could effortlessly get to work and that did not have obvious huge rendering issues. They're at 1280x800px.
+
+All of the content on the screenshots is in the public domain:
+* The textual content is just a lot of copy-paste of Lorem ipsum: P5878
+* The site logo (where shown) is the MediaWiki logo (`$wgLogo = ""/w/resources/assets/mediawiki.png"";`)
+* The images are classic art ([[https://commons.wikimedia.org/wiki/File:Turner,_J._M._W._-_The_Fighting_Téméraire_tugged_to_her_last_Berth_to_be_broken_(edit).jpg|1]] [[https://commons.wikimedia.org/wiki/File:Bierstadt_Albert_Indian_Summer_Hudson_River.jpg|2]] [[https://commons.wikimedia.org/wiki/File:Meisje_met_de_parel.jpg|3]])
+
+I'm going to commit these to the repos, and upload them to Commons, later (or tomorrow).
+
+| apex | {F9028408} | {F9028408,layout=link} |
+| Blueprint | {F9028411} | {F9028411,layout=link} |
+| BlueSky | {F9028404} | {F9028404,layout=link} |
+| Bouquet | {F9028414} | {F9028414,layout=link} |
+| CologneBlue | {F9028412} | {F9028412,layout=link} |
+| Daddio | {F9028423} | {F9028423,layout=link} |
+| DeskMessMirrored | {F9028449} | {F9028449,layout=link} |
+| Dusk | {F9028426} | {F9028426,layout=link} |
+| erudite | {F9028422} | {F9028422,layout=link} |
+| Example | {F9028429} | {F9028429,layout=link} |
+| GreyStuff | {F9028433} | {F9028433,layout=link} |
+| Mask | {F9028436} | {F9028436,layout=link} |
+| Metrolook | {F9028435} | {F9028435,layout=link} |
+| Modern | {F9028439} | {F9028439,layout=link} |
+| MonoBook | {F9028462} | {F9028462,layout=link} |
+| Nimbus | {F9028468} | {F9028468,layout=link} |
+| Nostalgia | {F9028465} | {F9028465,layout=link} |
+| Splash | {F9028475} | {F9028475,layout=link} |
+| Tempo | {F9028466} | {F9028466,layout=link} |
+| Timeless | {F9028461} | {F9028461,layout=link} |
+| Truglass | {F9028482} | {F9028482,layout=link} |
+| Vector | {F9028486} | {F9028486,layout=link} |
+| webplatform | {F9028483} | {F9028483,layout=link} |
+| WPtouch | {F9028485} | {F9028485,layout=link} |
+",1502422314,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,Change https://gerrit.wikimedia.org/r/371080 (fd8d75c1fd26e9ca0976111f1b3861935a53f84b) makes this possible. I guess we should take a bunch of screenshots and include them now? :o,1502394934,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"A full preview sounds a bit sketchy on the site, but would it potentially be possible to do the full preview somewhere else? Have a screenshot available with the skin, also have an optional link to a testwiki preview (like maybe just set up an entire toollabs wiki or whatever you call it for that)... this wouldn't cover all skins, but for ones included with the tarball and even in gerrit and crap it would be pretty straight forward to set up.
+
+Would be a bit harder to maintain, though.",1443459705,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"We wouldn't want it to get too complicated, both on the admin and on the user end, but I dunno.
+
+If nothing else, having a small thumbnail just so there's something visual at all would certainly be useful, but we can't expect the thumbnail/screenshot to do much beyond that. So... er... there should be both. We should have both things - a more immediate preview mechanism, and a small thumbnail for initial eye-catching and later locating in the list.",1403463945,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"I actually agree with Isarra somewhat - a preview is better than a screenshot. That said the current experience is terrible. Previewing the preference page for one makes no sense - it would be far better to see something in the main namespace rendered via the chosen skin.
+
+Tumblr does a great job in its theme interface. You can select and search for skins and they instantly get applied so it's easy to flick between them and see the skin in the context of an ipsum lorem article.
+
+This could be a great opportunity to break skins out of Special:Preferences - maybe Special:Preferences/Skin and just provide a good simple interface for skin switching - maybe a drop down at the top and an Ipsum lorem article rendered below. When we have templating in core we could even do this rendering via JavaScript :-).",1403463675,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"What's wrong with ?useskin? 
+
+Except in the installer. That would need something fancier, or something. Unless there'd be some way to safely automatically include them temporarily for preview... er...
+
+I don't know where I was going with that.",1402125627,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+VisualEditor: Citation dialog changes title after opening,"1. Click Cite -> Newspaper
+2. A dialog opens; while it's opening, the title is ""Newspaper""
+3. Once it finishes opening, the title changes to ""Cite news""
+
+This is more visible on a slower system or with an artificially lengthened opening animation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401752160,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mlrh4edb5aomh7cflcn2,task_description,open
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Click somewhere outside the page where the VE toolbar will get disabled
+4.Now click on the image.
+
+Observed Result:
+Clicking on the image tries to select the image first then cursor moves to the beginning of the document.
+
+Environment :Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401300060,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xbd775tm7a2kficmtwfv,task_description,resolved
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it",Verified the fix in en.wiki running wmf 8,1402684945,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it",Verified the fix in Betalabs and test2,1402344939,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it","Change 136013 merged by jenkins-bot:
+Don't fix selection on document focus if focusedNode is set
+
+https://gerrit.wikimedia.org/r/136013",1401391092,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it","Change 136013 had a related patch set uploaded by Esanders:
+Don't fix selection on document focus is focusedNode is set
+
+https://gerrit.wikimedia.org/r/136013",1401365615,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it","Created attachment 15500
+video capture of the bug
+
+**Attached**: {F13645}",1401300263,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+VisualEditor: Undo/redo should not (?) remain active when surface is blurred,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to the Media Settings dialog of the image
+4.Type something in the caption field
+5.Now place the cursor in the Alternative Test field
+6.Observe that, the ""Undo"" button in the toolbar is still active
+7.Click on the undo button
+
+Observed Result:
+It clears the text inside the caption field , this is a bit confusing , since the cursor was pointing to text inside Alternative Text and but it started clearing out the content inside caption field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400887980,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3bxysrz3mthjheir6p4n,task_description,declined
+VisualEditor: Undo/redo should not (?) remain active when surface is blurred,"This is because the undo and redo buttons remain active when the surface is blurred. I know this is intentional, but maybe it should be revisited.",1401303039,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-3bxysrz3mthjheir6p4n,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"**Author:** `wiki.nihiltres`
+
+**Description:**
+I noticed today that dialogs are delayed or fail to work some of the time in VE, using Safari 5.1.10 on Mac OS 10.6.8. The first click on a button that produces a dialog, or first few clicks, don't seem to do anything, but clicking on the button a while later has the normal effect, suggesting something's taking a while to load.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Mac OS X 10.6
+**Platform**: Macintosh",1400793900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gmtmxwco32y632mfebna,task_description,resolved
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Patch merged; assuming this is fixed / worked around by greylisting. If not, please reopen.",1583082370,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Change 135154 merged by jenkins-bot:
+Move Safari 5.x to greylist because dialogs aren't working well
+
+https://gerrit.wikimedia.org/r/135154",1400902028,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Change 135154 had a related patch set uploaded by Jforrester:
+Move Safari 5.x to greylist because dialogs aren't working well
+
+https://gerrit.wikimedia.org/r/135154",1400891973,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Yes, Confirmed on MAC OSX 10.6 and Safari 5.1. This is happening while opening any dialog for the first time , it does not open even if I try clicking on it multiple times, once I clicked on some other buttons from the toolbar both the dialogs open at the same time",1400890916,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Odd. Rummana, can you test this and confirm behaviour?",1400794112,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Steps to reproduce:
+
+1.  Open any page that contains the {{coord}} template on en.wp  See, e.g., https://en.wikipedia.org/wiki/Harton,_North_Yorkshire 
+
+
+Results:
+
+The coordinates template, which should be in the top right corner, displays in the far left—so far to the left that only the last few characters are visible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400782860,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_description,open
+VisualEditor:  Coordinates template is displaying in the wrong place,"The previous comments don't explain who or what (task?) exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status, as tasks should not be stalled (and then potentially forgotten) for six years for unclear reasons.
+
+//(Smallprint, as general orientation for task management:
+If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead.
+If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}.
+If this task is stalled on an upstream project, then the #upstream tag should be added.
+If this task requires info from the task reporter, then there should be instructions which info is needed.
+If this task needs retesting, then the #testme tag should be added.
+If this task is out of scope and nobody should ever work on this, or nobody else managed to reproduce the situation described here, then it should have the ""Declined"" status.
+If the task is valid but should not appear on some team's workboard, then the team project tag should be removed while the task has another active project tag.)//
+",1604263405,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,Just FYI to Chris!,1522080495,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,">>! In T67648#4080803, @matmarex wrote:
+>>>! In T67648#4079369, @TheDJ wrote:
+>> %%% this will move the coordinates from below the H2 line to above it.. I expect resistance :)
+> 
+> You can still keep the `position: absolute; ...` for `<span id=""coordinates"">` if preserving the exact positioning is required, even when it's in an indicator.
+
+Good point, i'll see about experimenting with that somewhere this week.",1522075465,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,">>! In T67648#4079369, @TheDJ wrote:
+> %%% this will move the coordinates from below the H2 line to above it.. I expect resistance :)
+
+You can still keep the `position: absolute; ...` for `<span id=""coordinates"">` if preserving the exact positioning is required, even when it's in an indicator.",1522075391,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"For now https://en.wikipedia.org/w/index.php?title=MediaWiki:Monobook.css&diff=832362097&oldid=813457383 and https://en.wikipedia.org/w/index.php?title=MediaWiki:Vector.css&diff=832362332&oldid=813450031 less problematic, without the need to resort to moving it.
+
+@Jc86035 BTW. it can already use Kartographer (some wiki's do, and i think en.wp even has a sandbox version of it). But i'm not wasting my precious free time on weeks of discussion with the princesses to convince them to switch.",1521991082,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"If resistance would be an issue (and I think that's not unlikely), I think it would be better to wait for Community Tech to convert the module to use Kartographer, since GeoHack would then not be needed for coordinates on Earth. Then any visual change as a result of changing the GeoHack styling would affect far fewer pages.",1521989181,PHID-USER-zcjbttnvrligppi7hwnx,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"If resistance would be an issue (and I think that's not unlikely), I think it would be better to wait for Community Tech to convert the module to use Kartographer, since GeoHack would then not be needed for coordinates on Earth. Then any visual change would effect far fewer pages.",1521989156,PHID-USER-zcjbttnvrligppi7hwnx,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,this will move the coordinates from below the H2 line to above it.. I expect resistance :),1521988912,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"I don't know Lua, but I think something like [[https://en.wikipedia.org/w/index.php?diff=832258813&oldid=819658303|this]] might do it. See [[https://en.wikipedia.org/wiki/Module_talk:Coordinates#Convert_to_indicator|Module talk:Coordinates#Convert to indicator]].",1521926075,PHID-USER-32xfxqjy2iw66kf33xjy,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"More precisely, updating that scary template is something that I think a technically competent person, e.g., @Jc86035 @MaxSem @TheDJ or @JJMC89, should look into.  `:-)`",1521828281,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,@Whatamidoing-WMF is this something you'd like to look into?,1521819544,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Yes, the best solution here is for the English Wikipedia community to change {{Coord}} in that way. On its face this looks like a simple change, but this is a widely-used and complicated template, so some care will no doubt be needed. Any gadgets or tools depending on the output of this template may also need to be updated (e.g. the map popup). I don't think it is feasible to solve this on the VE side (and we won't need to do anything if the template is changed).",1521662847,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,">>! In T67648#4066986, @matmarex wrote:
+> Just for reference, since this task doesn't have a screenshot, here's how it currently looks: {F15921704}
+> 
+> VisualEditor does its best attempt to position the template where requested by the CSS (`position: absolute; top: 0; right: 0;`), but for boring technical reasons (""stacking contexts"") it can't escape the editing surface: {F15921712}
+> 
+> English Wikipedia should migrate the {{Coord}} template to use the `<indicator>` parser tag to position it in the top-right corner (see https://www.mediawiki.org/wiki/Help:Page_status_indicators). Many other templates there already use it, for example everything derived from [[ https://en.wikipedia.org/wiki/Template:Top_icon | {{Top icon}} ]]. VisualEditor will display such templates as if they were invisible (like e.g. [[ https://en.wikipedia.org/wiki/Template:Use_British_English | {{Use British English}} ]]), with a greyed-out puzzle icon and template name.
+> 
+> {F15921725}
+
+So, are we saying that the solution here is a simple recommendation to the community, or is there anything we technically would need to implement on our side? TY.",1521635636,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Just for reference, since this task doesn't have a screenshot, here's how it currently looks: {F15921704}
+
+VisualEditor does its best attempt to position the template where requested by the CSS (`position: absolute; top: 0; right: 0;`), but for boring technical reasons (""stacking contexts"") it can't escape the editing surface: {F15921712}
+
+English Wikipedia should migrate the {{Coord}} template to use the `<indicator>` parser tag to position it in the top-right corner (see https://www.mediawiki.org/wiki/Help:Page_status_indicators). Many other templates there already use it, for example everything derived from [[ https://en.wikipedia.org/wiki/Template:Top_icon | {{Top icon}} ]]. VisualEditor will display such templates as if they were invisible (like e.g. [[ https://en.wikipedia.org/wiki/Template:Use_British_English | {{Use British English}} ]]), with a greyed-out puzzle icon and template name.
+
+{F15921725}",1521585347,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Yes, this is because we give the document padding instead of margin to make the margins clickable.",1442587966,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Today in (try here: https://en.wikipedia.org/wiki/Burpengary_Creek?veaction=edit ) it is on the far right, so far right that there is no margin between the final character and the scrollbar, as Elitre described.  However, it's also one line too low, which means that it makes the last few words of the first paragraph very difficult to read.
+
+",1438972845,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"I tried as well, and what happens for me in FF and Chrome is that the template moves completely to the right and there is no margin between the E and the scrollbar.",1425652624,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Cannot reproduce the problem anymore on https://en.wikipedia.org/wiki/Harton,_North_Yorkshire?veaction=edit even after hovering over the Coord template and clicking it. Same for Quiddity's other two links. Coord stays on the right where it belongs in Firefox 36 on Fedora 21.
+
+Should this task be closed as resolved / declined?",1425489265,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"The above example is still basically the same. Possibly different, is that the template only moves to the far-left *after* I mouseover the template. (Firefox and Chrome).
+
+However, at other articles, it moves to different places. 
+e.g. https://en.wikipedia.org/wiki/Happy_Valley,_Victoria after I mouseover the link, it moves downwards by ~1cm, so that it overlaps the infobox.
+e.g.2. https://en.wikipedia.org/wiki/Happy_Valley,_South_Australia after I mouseover the template, it moves to the far-left, but also far-down the page (underneath the ==References== section).",1403198616,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"This is related to T52855 about parser functions and magic words.
+
+When I have a sentence on a page like this:
+
+   Choose the ""{{int:visualeditor-dialogbutton-reference-tooltip}}"" item in the ""{{int:visualeditor-toolbar-insert}}"" menu. 
+
+I want to be able to:
+
+(1) copy and paste; 
+(2) edit; and
+(3) create
+
+the {{int:foo}} parts.  
+
+Right now, I can only copy them for re-use elsewhere on the page if I select a bigger block of text (so ""{{int:visualeditor-toolbar-insert}}"", but not just {{int:visualeditor-toolbar-insert}}).
+
+I can't edit them at all; it's an uneditable alienated text block.  Given the long strings of similar names for some of these items, it would be really handy to be able to copy and paste something like {{int:visualeditor-toolbar-insert}} and only need to change the ""insert"" bit to ""cite-label"", or to fix a typo in the name.
+
+It would also be nice to have a sensible system for creating these things.  At the moment, it can only be done through this sequence:  Insert > Template, ""Other options"", Content, type in the wikitext, and Insert transclusion. 
+
+However, my main concern is just being able to edit existing ones.",1400780640,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_description,resolved
+VisualEditor: Support editing {{int:name}} blocks,"@Whatamidoing-WMF, I'm sure it's //possible//, but generally we shouldn't introduce behavioral inconsistencies without a good reason. Whatever the decision on changing the name of a  transclusion is, it should probably apply to all types of transclusions. ",1438369981,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"I believe that has already been filed and declined for templates, although I can't find it.  Do you want to handle transcluded magic words and the like differently from transcluded templates?  (Is that even feasible?)",1438367554,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"@Whatamidoing-WMF, fair point. Do you want to file a separate task for changing the name of an existing transclusion?",1438203212,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"It is still not possible to edit them, e.g., to fix a typo.  You have to delete them and re-create them.  This is perhaps not surprising, since you can't fix a typo in a template name, either.",1438120805,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,">Update: I can insert parser functions by adding a ""template"" named (for example) ""int:vector-view-edit"". It says there's no TemplateData, but it adds it.
+
+Given that it's now possible to easily transclude and move interface messages, I'm closing this. I've opened T106755 for the low-priority challenge of making it more user-friendly.",1437690670,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"Update:  I can insert parser functions by adding a ""template"" named (for example) ""int:vector-view-edit"".  It says there's no TemplateData, but it adds it.",1405532364,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+"Move the reference, reference list and citation systems into the Cite extension's repo","I spent a lot of time wondering why my citations were not rendering properly.
+
+VisualEditor shows a cite menu which behaves strangely if the Cite extension not enabled.
+
+Should this throw an error or not show the citation tool when the Cite extension is not installed?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400766240,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-njmo4dxth5kyk5lgw2it,task_description,duplicate
+"Move the reference, reference list and citation systems into the Cite extension's repo",Well technically we should move all the reference code to the Cite extension...,1416784874,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-njmo4dxth5kyk5lgw2it,task_subcomment,NA
+"Move the reference, reference list and citation systems into the Cite extension's repo","Yeah, this is a bit of a crummy situation. We should fix this.",1400775918,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-njmo4dxth5kyk5lgw2it,task_subcomment,NA
+Serializing images without data-parsoid normalizes image names incorrectly,"If you parse wikitext like `[[File:Ulmer M?nster-1024409.jpeg|frame]]` , Parsoid will produce a <figure> structure with href=""./File:Ulmer_M%3Fnster-1024409.jpeg"" (which is correct, the question mark is urlencoded) and resource=""./File:Ulmer_M%3Fnster-1024409.jpeg"" (not sure whether this is correct).
+
+When VisualEditor takes this information to build an inline image equivalent (taking the href and the resource, and dropping everything else including data-parsoid) we get [[File:Ulmer_M%3Fnster-1024409.jpeg|link=]] back. Note the space changed to an underscore and ? changed to %3F. There was information in data-parsoid to keep this from happening, but in this transformation VE discards it.
+
+```
+$ echo '[[File:Ulmer M?nster-1024409.jpeg|frame]]' | node tests/parse.js --apiURL=http://localhost/w/api.php
+<!DOCTYPE html>
+<html prefix=""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/""><head prefix=""mwr: http://localhost/wiki/Special:Redirect/""><meta property=""mw:parsoidVersion"" content=""0""/><link rel=""dc:isVersionOf"" href=""//localhost/wiki/Main_Page""/><title></title><base href=""//localhost/wiki/Main_Page""/></head><body data-parsoid='{""dsr"":[0,42,0,0]}'><figure class=""mw-default-size"" typeof=""mw:Image/Frame"" data-parsoid='{""optList"":[{""ck"":""framed"",""ak"":""frame""}],""dsr"":[0,41,2,2]}'><a href=""./File:Ulmer_M%3Fnster-1024409.jpeg"" data-parsoid='{""a"":{""href"":""./File:Ulmer_M%3Fnster-1024409.jpeg""},""sa"":{},""dsr"":[2,39,null,null]}'><img resource=""./File:Ulmer_M%3Fnster-1024409.jpeg"" src=""//localhost/w/images/f/f1/Ulmer_M%3Fnster-1024409.jpeg"" height=""1024"" width=""764"" data-parsoid='{""a"":{""resource"":""./File:Ulmer_M%3Fnster-1024409.jpeg"",""height"":""1024"",""width"":""764""},""sa"":{""resource"":""File:Ulmer M?nster-1024409.jpeg""}}'/></a></figure>
+</body></html>
+
+$ echo '<p><span typeof=""mw:Image"" class=""mw-default-size""><span><img src=""//localhost/w/images/f/f1/Ulmer_M%3Fnster-1024409.jpeg"" resource=""./File:Ulmer_M%3Fnster-1024409.jpeg"" width=""764"" height=""1024""></span></span></p>' | node tests/parse.js --html2wt
+[[File:Ulmer_M%3Fnster-1024409.jpeg|link=]]
+```
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400706840,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-fscihqnuuufaxytwhfkf,task_description,open
+Serializing images without data-parsoid normalizes image names incorrectly,This is a low-priority issue since Parsoid has access to data-parsoid always via the old HTML (either explicitly reparsed or via RESTBase).,1583899287,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-fscihqnuuufaxytwhfkf,task_subcomment,NA
+Serializing images without data-parsoid normalizes image names incorrectly,It looks like we aren't percent-decoding & underscore-removing the resource properly in the serializer. This also seems to be the case for block images.,1401305509,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fscihqnuuufaxytwhfkf,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,"1. go to article on en.m.wiki
+2. invoke WTE type characters
+3. shake phone, [undo/cancel] dialog is displayed
+4. choose undo
+
+expected : typed characters should be removed
+actual : typing is not undone
+
+5. once undo works, shaking phone again should trigger [redo/cancel] which should restore undone action.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400704140,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-o53zljq5pyonvqfryedx,task_description,resolved
+iOS: Shake to undo on mobile does not undo or redo typing,"Just testing on iphone, and ipad, in VE and WTE, issue is no longer present. closing. ",1418251044,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,@Jaredzimmerman-WMF Works for me. Tested in Mobile Safari on iPhone.,1418250424,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,@Jdforrester-WMF this behaviour should be supported by both editors on mobile devices which support this gesture. Its isn't actually WTE specific. ,1418163852,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,What about #VisualEditor is there to do on this task?,1418163380,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,"@Jdlrobson why is this non-actionable, can you please comment as to what is needed to unblock this?  ",1418160265,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,WikiTextEditor (e.g. not VE),1402524590,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,"**jgonera** wrote:
+
+What is WTE?",1402524550,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,If you didn't mean to shake the OS already shows a dialog with [undo/cancel] this is a standard part of the OS that you can't turn off.,1400707709,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,(Also what happens if I didn't mean to shake...? - happens to me all the time - had to disable it in Google Maps),1400705249,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,Please talk to Maryana about scheduling and prioritizing this feature request.,1400705221,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/pNCKv65l",1400704222,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,It's impossible to create a new page / new content without this. :-(,1400686140,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_description,open
+VisualEditor Mobile: Allow formatting editing,"Terminology. Bah.
+
+Well, yeah, those are missing. It's an open question whether we really want to support article creation in the short term over other use cases, but that's a different discussion...",1535400949,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,">>! In T67586#4535966, @Deskana wrote:
+> Formatting (e.g. bold, italics) can be added and edited in the mobile visual editor. Am I misunderstanding this task, or is it just so old that these features didn't exist back then?
+
+This is about formatting (headings), not styling (bold, italics). You can't make an article without being able to make sections (not least, a references section).",1535400395,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,"Formatting (e.g. bold, italics) can be added and edited in the mobile visual editor. Am I misunderstanding this task, or is it just so old that these features didn't exist back then?",1535400306,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,Just that - finding a place for it to go.,1439141540,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,What else do we need to do here other than add the formatting menu to MobileViewTarget?,1430597202,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/5i7pUTTK",1400692790,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"Quora has a lovely feature in its visual editor: paste a URL and it's immediately and automatically converted in a smart way.
+
+* If it's a link to another answer on Quora, it is given an appropriate title.
+* If it's a link to YouTube, the video is embedded.
+* If it's a link to some other website, the page's HTML <title> is inserted and automatically linked. (There may be other special cases, but you get the idea.)
+
+After the link is thus inserted, the user can edit the text or click another button to make the actual URL appear or to make the URL just plain text.
+
+I'd love such a feature in VE. It's especially relevant for newbies who link to other Wikipedia articles with full http links as if they were external. For external links, getting the title automatically is usually better than having a plain URL (in fact, there are some bots that automatically insert such titles). And pasting a Commons URL can embed the media as such.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400608680,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-twvr5rqlyoly5q6lv355,task_description,resolved
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"Pasting URLs now does sensible things, even converting to internal links when appropriate. Mostly thanks to work by @cscott.",1444743744,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"(In reply to Amir E. Aharoni from comment #4)
+> I meant not only external links, but pages in the same wiki, too. It's
+> anecdotal, but I see newbies adding http urls to other Wikipedia article
+> instead of using square brackets, and this should be DWIMmier.
+
+Those already get converted to internal (well, interwiki) links, though…",1415799211,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"I meant not only external links, but pages in the same wiki, too. It's anecdotal, but I see newbies adding http urls to other Wikipedia article instead of using square brackets, and this should be DWIMmier.",1415798449,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"Hmm. Right now we're taking newly-created external links and displaying them as auto-numbered link nodes; having this as a secondary mode to fetching the <title> could work, but… I'm not sure.",1414693734,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"This could potentially inform the VE UI for citoid;
+
+I.e. we could have have one reference dialog, (i.e. the basic reference dialog) and then if a user pastes a link *into* the reference dialog, that inserts the citation guessed from the link. And then keep the drop down menu for individual templates in the ref dialog.
+
+This does take some user discovery; however, I see this commonly being done with references already- i.e. a ref tag containing only an unformatted url. So it seems people are already just pasting links into the ref field and this is a natural enhancement of that work flow. 
+
+This, by the way, is what both G+ and Facebook do for links as well, not just Quora. So there may be already some user comfort with a pasted link becoming formatted in some fashion.",1414580483,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"Interesting idea. We've got some work planned to do this kind of thing for citations (you feed it a URL, it inserts a nice <ref>{{cite web|…}}</ref> block), and links to internal or interwiki targets get auto-converted on save (so [[:en:Foo|Bar]] not [https://en.wikipedia.org/wiki/Foo Bar]), but we don't do this for pasting into the surface. Maybe something we could do in the future?",1400609128,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Font is too small in dialogs in standalone VE,"Compare the keyboard shortcut help dialog (Ctrl+/) in the standalone demo vs the MW integration. The one in standalone has a smaller font size.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400109240,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6qrknx6d4rhbi2dfof45,task_description,resolved
+VisualEditor: Font is too small in dialogs in standalone VE,Fixed in gerrit 141089.,1405375966,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6qrknx6d4rhbi2dfof45,task_subcomment,NA
+BetaFeatures: Provide an anchor link for each beta feature,"Add anchor links to each feature so that a user could send someone directly to a feature. For example, https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures#VisualEditor
+",1400101980,PHID-USER-flenunkasbjk4topxvaj,PHID-TASK-i5g7enpuggt3etks6uiw,task_description,open
+BetaFeatures: Provide an anchor link for each beta feature,"(In reply to Kaity Hammerstein from comment #0)
+> Add anchor links to each feature so that a user could send someone directly
+> to a feature. For example,
+> https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-
+> betafeatures#VisualEditor
+
+I don't think double anchors like that even work?
+
+In my patch the links are created like https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures-betafeatures-vector-compact-personal-bar
+
+Where ""betafeatures-vector-compact-personal-bar"" is the preference key used for the CPB BF in VectorBeta. So for VE it would be ""visualeditor-enable"".",1400136694,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-i5g7enpuggt3etks6uiw,task_subcomment,NA
+BetaFeatures: Provide an anchor link for each beta feature,"Change 133419 had a related patch set uploaded by Legoktm:
+Add an anchor for individual features
+
+https://gerrit.wikimedia.org/r/133419",1400136515,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-i5g7enpuggt3etks6uiw,task_subcomment,NA
+VisualEditor Mobile: The Link inspector icon remains highlighted in the toolbar for mobile VE even if no new link has been added,"Screenshot
+
+Steps to reproduce:
+
+1.Open a blank page with mobile VE
+2.Click on the link inspector icon
+3.Without adding any text just close the inspector
+
+Observed Result:
+The link inspector icon in the toolbar remains highlighted where as there is no link added in the CE
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13539}",1400097300,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-uktdpzihh2lhvffqgb4d,task_description,resolved
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Edit something
+3.Switch to edit source mode
+4.Save the page from edit source mode
+
+Observed Result:
+The message  ""The page has been restored"" appearing on top of the page instead of 
+""your edit was saved""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14068}",1400002440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6qhvami4rv442prsl2cd,task_description,resolved
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there",Verified the fix in production,1400794695,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there",Verified the fix on test2,1400268685,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there",Verified the fix on Betalabs,1400103762,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there",Should be fixed now.,1400103339,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there","Change 133363 merged by jenkins-bot:
+Only send useful oldid while switching to wikitext editor if it's specifically requested
+
+https://gerrit.wikimedia.org/r/133363",1400103223,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there","Change 133363 had a related patch set uploaded by Alex Monk:
+Only send useful oldid while switching to wikitext editor if it's specifically requested
+
+https://gerrit.wikimedia.org/r/133363",1400102777,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"A ""Request desktop site"" option exists in Chrome and Firefox on Android, and maybe in some other browsers too.
+
+I believe what that option affects is just a user-agent string, and does not change other behaviors of the browser. However (for example in Firefox), with ""Request desktop site"" on, VisualEditor works happily, while with that option off, VisualEditor refuses to load.
+
+We should check whether VE actually works in these browsers, and have it whitelisted or blacklisted, regardless of whether that option is on or off.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: normal",1399982340,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ixtz4sysk7h76zhcsyps,task_description,resolved
+jquery.client should support detecting Firefox Mobile,I think this was fixed in T101483. Please reopen if this is incorrect.,1599505179,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"If I understand correctly:
+* When users of Firefox Mobile use ""Request desktop site"", it uses a user agent header jQuery Client recognises as desktop Firefox. And VE supports that. And that browser supports VE. All is good.
+* When users of Firefox Mobile use the default mode, it uses a user agent header jQuery Client doesn't yet recognise properly (version=mobile). VE doesn't whitelist that. But it seems otherwise that browser would support VE.
+
+I'm not sure that working around the intentionally faked user-agent header will be feasible. It would leave us in a hard to maintain state.
+
+I'd recommend, instead:
+* jQuery Client should detect the name and version of Firefox Mobile properly.
+* VisualEditor whitelists Firefox Mobile (from that version and up).
+
+",1426117677,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"If I understand correctly:
+* When users of Firefox Mobile use ""Request desktop site"", it uses a user agent header jQuery Client recognises as desktop Firefox. And VE supports that. And that browser supports VE. All is good.
+* When users of Firefox Mobile use the default mode, it uses a user agent header jQuery Client doesn't yet recognise properly (version=mobile). VE doesn't whitelist that. But it seems otherwise that browser would support VE.
+
+I'm not sure that working around the intentionally faked user-agent header will be feasible and would leave us with a to maintain scenario.
+
+I'd recommend, instead:
+* jQuery Client should detect the version of Firefox Mobile properly.
+* VisualEditor whitelists Firefox Mobile (from that version and up).
+
+",1426117624,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"If I understand correctly:
+* When users of Firefox Mobile use ""Request desktop site"", it uses a user agent header jQuery Client recognises as desktop Firefox. And VE supports that. And that browser supports VE. All is good.
+* When users of Firefox Mobile use the default mode, it uses a user agent header jQuery Client doesn't yet recognise properly (version=mobile). VE does not support that. But it seems otherwise that browser would support VE.
+
+I'm not sure that working around the intentionally faked user-agent header will be feasible and would leave us with a to maintain scenario.
+
+I'd recommend, instead:
+* jQuery Client should detect the version of Firefox Mobile properly.
+* VisualEditor whitelists Firefox Mobile (from that version and up).
+
+",1426117582,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"If I understand correctly:
+* When users of Firefox Mobile use ""Request desktop site"", it uses a user agent header jQuery Client recognises as desktop Firefox. And VE supports that. And that browser supports VE. All is good.
+* When users of Firefox Mobile use the default mode, it uses a user agent header jQuery Client doesn't yet recognise properly (version=mobile). VE does not support that. But it seems otherwise that browser would support VE.
+
+In that case, I'd recommend:
+* jQuery Client should detect the version of Firefox Mobile properly.
+* VisualEditor whitelists Firefox Mobile (from that version and up).
+
+I'm not sure that working around the intentionally faked user-agent header will be feasible and would leave us with a to maintain scenario.",1426117560,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"So it's a jquery.client issue: for Chrome and Firefox on Android, profile().name should always be ""firefox"" or ""chrome"" respectively, with .version set correctly, no matter how user configures the browser.
+
+Currently in Chrome, profile().platform is ""linux"". Maybe we can use ""android"" there to signify the browser is running on Android.",1399985804,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"It seems there're two places where UA matters, summarized below:
+
+Browser | Option | profile().name | profile().version | Tab shown | Warning shown
+---------------------------------------------------------------------------------
+Firefox |   On   |    android     |      mobile       |    No     |      N/A
+Firefox |  Off   |    firefox     |       29.0        |    Yes    |      No
+Chrome  |   On   |    android     |       4.4.2       |    Yes    |      Yes
+Chrome  |  Off   |    chrome      |   34.0.1847.114   |    Yes    |      No
+
+Firefox with the option on is being detected as browser ""android"" version ""mobile"" is the most problematic thing here, because it completely disables VE.",1399985467,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"By having Firefox hit my own webserver, I caught UA below. Not sure whether it can be different from the one returned by navigator.userAgent.
+
+""Request desktop site"" off:
+
+Mozilla/5.0 (Android; Mobile; rv:29.0) Gecko/29.0 Firefox/29.0
+
+JSON.stringify($.client.profile({userAgent:'Mozilla/5.0 (Android; Mobile; rv:29.0) Gecko/29.0 Firefox/29.0',platform:''}))
+""{""name"":""android"",""layout"":""gecko"",""layoutVersion"":29,""platform"":""unknown"",""version"":""mobile"",""versionBase"":""0"",""versionNumber"":0}""
+
+""Request desktop site"" on:
+
+Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0
+
+JSON.stringify($.client.profile({userAgent:'Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0',platform:''}))
+""{""name"":""firefox"",""layout"":""gecko"",""layoutVersion"":20100101,""platform"":""unknown"",""version"":""29.0"",""versionBase"":""29"",""versionNumber"":29}""",1399983335,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"(In reply to Liangent from comment #2)
+> (In reply to James Forrester from comment #1)
+> > Do you mean ""make jquery.client detect for Firefox mobile""? If so, that's a
+> > very different bug to how you've written this one. :-)
+> 
+> Hmm? so it's already special cased in jquery.client for Chrome mobile, so
+> there's no such issue in Chrome, without any change in VE side (I haven't
+> really tested)?
+
+I don't know. Your bug report seems to suggest that Firefox Mobile is getting detected as a failing browser, and telling Firefox Mobile to pretend to be Firefox makes it work fine. That's a sign that it's failing jquery.client's test cases.
+
+Do you have an example UA string? https://developer.mozilla.org/en-US/docs/Gecko_user_agent_string_reference suggests that it should be putting out ""Mozilla/5.0 (Android; Mobile; rv:13.0) Gecko/13.0 Firefox/13.0"".",1399982939,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"(In reply to James Forrester from comment #1)
+> Do you mean ""make jquery.client detect for Firefox mobile""? If so, that's a
+> very different bug to how you've written this one. :-)
+
+Hmm? so it's already special cased in jquery.client for Chrome mobile, so there's no such issue in Chrome, without any change in VE side (I haven't really tested)?",1399982719,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"Do you mean ""make jquery.client detect for Firefox mobile""? If so, that's a very different bug to how you've written this one. :-)",1399982480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+VisualEditor: Clearing float from a template like {{-}} doesn't work,"In the linked article, the content is not cleared after floats of the tables when using the template {{-}} which transcludes as:
+<br style=""clear:both;"">
+
+This is caused by the inline-block behavior of .ve-ce-mwTransclusionInlineNode
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=List_of_top_100_Major_League_Baseball_strikeout_pitchers&oldid=608135239
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57372",1399971600,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-cfsuxmmxpeev6stnegu6,task_description,resolved
+VisualEditor: Clearing float from a template like {{-}} doesn't work,"Confirmed, now seems fixed (tested in Safari 8.0.4).",1427402228,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cfsuxmmxpeev6stnegu6,task_subcomment,NA
+VisualEditor: Clearing float from a template like {{-}} doesn't work,"This problem seems fixed, as far as I can assess...",1427402002,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-cfsuxmmxpeev6stnegu6,task_subcomment,NA
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,"The ""notices"" thing (exclamation mark in a triangle) disappears from VE toolbar if you open a page for editing, close VE, then open it again (on the same page).
+
+To reproduce:
+1. Click ""Edit"" (or ""Edit beta"") on any page to open VisualEditor
+2. Click ""Cancel"" to close it
+3. Click ""Edit"" again
+
+The toolbar will no longer have the ""notices"" item.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399921320,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-cbra3savyka36yjom4gn,task_description,resolved
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,"Gerritadmin seems to be missing, I uploaded Gerrit change 133537",1400184171,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cbra3savyka36yjom4gn,task_subcomment,NA
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,"Aha, yes, when the only warning is the browser warning I also get this. However, if e.g. you try to edit the Main Page of enwiki you get the other two notices (protected page and edit notice) each time.
+
+Renaming.",1399961766,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cbra3savyka36yjom4gn,task_subcomment,NA
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,"I tested on Opera Next 22 and Opera 12 with the same effect. Maybe this is related to the ""You're using an unsupported browser"" popup?",1399940658,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-cbra3savyka36yjom4gn,task_subcomment,NA
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,What browser does this occur in? Opera? It works fine for me in Chrome and Firefox…,1399928299,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cbra3savyka36yjom4gn,task_subcomment,NA
+VisualEditor: References as part of a file description are misnumbered,"In https://en.wikipedia.org/w/index.php?title=Female_promiscuity&oldid=607751101 references [74], [75] and [76] show up as 1, 2 and 3 in VE in the references box, with the rest of the reference numbers ""pushed down"", but with their original numbering in the main VE editing interface.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399921200,PHID-USER-n27daagbl3wqf3ghr4nk,PHID-TASK-3m3hkpshul72ld2jnj3z,task_description,resolved
+VisualEditor: References as part of a file description are misnumbered,This seems to work correctly these days.,1688060841,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3m3hkpshul72ld2jnj3z,task_subcomment,NA
+VisualEditor: References as part of a file description are misnumbered,"They now show as references [73], [74] and [75] (off-by-one error?)",1421784712,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3m3hkpshul72ld2jnj3z,task_subcomment,NA
+VisualEditor: References as part of a file description are misnumbered,"They now show as references [73], [74] and [75] (off-by-one error?0",1406594865,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3m3hkpshul72ld2jnj3z,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),"See link provided above.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Anaconda,_Montana&diff=prev&oldid=608235426",1399915320,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hhbsyblnnelojfdxms2h,task_description,declined
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),apparently worksforme is the correct resolution for this situation,1407403982,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),So is this unconfirmed then?,1406846549,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),"(In reply to Richard Morris from comment #1)
+> Not quite sure it was a plugin, it could have been user error, cut and
+> pasting the wrong thing. The user did correct them self in the next edit.
+
+If they'd pasted the HTML raw it would have refused (<iframe>s etc. are blocked on paste); maybe they tried to paste it as a link target?",1399916704,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),"Yeah, it could be. James had confirmed my theory and that's why I filed it anyway. But I noticed the revert and was really glad about it. Success, right? :)",1399916495,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),"Not quite sure it was a plugin, it could have been user error, cut and pasting the wrong thing. The user did correct them self in the next edit.",1399915799,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+Support for Parsoid-based extracts,"This is important since the extracts are currently generated with the old API which doesn't guarantee valid xhtml5. That prevents third-party developers using less forgiving markup environments from fetching the extracts to build tools on top of them, e.g. https://github.com/waldyrious/primerpedia/issues/20
+
+I'd work on this myself but I really don't have the background to understand the code in ApiQueryExtracts.php on my own (even after taking a look at VisualEditor's ApiVisualEditor.php to check an example implementation of a request to Parsoid, as suggested by Mark Traceur).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399764120,PHID-USER-uazrhtptdqudzoqfefsc,PHID-TASK-egjhqqohru7fvy2225t5,task_description,duplicate
+Support for Parsoid-based extracts,Thanks for the feedback! We'll hopefully be prioritising this soon as part of the [[ https://www.mediawiki.org/wiki/Beta_Features/Hovercards | page previews/Hovercards ]] roll out... so watch this space!,1493660695,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"I need to be able to get the formatted extracts either via the old api.php or the new REST service. If a new endpoint is created providing such extracts with well-formed HTML, yes, that would work for me.",1493657792,PHID-USER-uazrhtptdqudzoqfefsc,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"TextExtracts could provide xml well formedness via php (we have a library in #MobileFrontend doing exactly that). Is there any other reason you specifically want this in REST?
+
+I suspect we will end up creating a rest endpoint to solve the epic. I've included well formed HTML as a requirement. Does this feel less broad now?",1493654331,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,">>! In T67169#3221431, @Jdlrobson wrote:
+> I think this task is exactly the same as what we are talking about in T113094 and its subtasks ?
+
+Yes, it looks like it, although the title/description of that issue is a little too broad for me to be comfortable calling this a dupe (particularly the line ""we either need to write a bunch of tests and fix up TextExtracts **//or//** build a new Parsoid based api specifically for the purpose of Hovercards"" -- this bug is specifically about the latter, due to the need for xml well-formedness).",1493551495,PHID-USER-uazrhtptdqudzoqfefsc,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"Thanks for clarifying @waldyrious .
+We are considering switching to HTML extracts for Page previews so watch this space.
+I think this task is exactly the same as what we are talking about in T113094 and its subtasks ?
+",1493396675,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"IIUC, that is not exactly what this request is about: [[ https://github.com/waldyrious/primerpedia/blob/gh-pages/primerpedia.js | currently I'm using ]] a request like https://en.wikipedia.org/w/api.php?action=query&prop=extracts&exintro&indexpageids=true&format=json&generator=random&grnnamespace=0&format=json, which returns a html-formatted extract. The problem is that the html is not guaranteed to be valid, hence it fails if embedded in a xhtml page (or any other context where well-formed xml is required).
+
+The REST API, in contrast, only returns plaintext extracts at the moment. I could use them, but that's a workaround (avoiding rich formatting altogether) rather than a fix.
+
+Is there any way to use the REST API to get an extract including the (rendered, not wikicode) basic formatting used in the actual article? For example bold, italics, and perhaps links as well.",1493372670,PHID-USER-uazrhtptdqudzoqfefsc,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"IIUC, that is not exactly what this request is about: [[ https://github.com/waldyrious/primerpedia/blob/gh-pages/primerpedia.js | currently I'm using ]] a request like https://en.wikipedia.org/w/api.php?action=query&prop=extracts&exintro&indexpageids=true&format=json&generator=random&grnnamespace=0&format=json, which returns a html-formatted extract. The problem is that the html is not guaranteed to be valid, hence it fails if embedded in a xhtml page (or any other context where well-formed xml is required).
+
+The REST API, in contrast, only returns plaintext extracts at the moment. I could use them, but that's a workaround (avoiding rich formatting altogether) rather than a fix.
+
+Is there any way to use the REST API to get an extract that preserves the basic formatting (bold, italics, and perhaps links as well) used in the actual article?",1493372609,PHID-USER-uazrhtptdqudzoqfefsc,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"IIUC, that is not exactly what this request is about: [[ https://github.com/waldyrious/primerpedia/blob/gh-pages/primerpedia.js | currently I'm using ]] a request like https://en.wikipedia.org/w/api.php?action=query&prop=extracts&exintro&indexpageids=true&format=json&generator=random&grnnamespace=0&format=json, which returns a html-formatted extract. The problem is that the html is not guaranteed to be valid, hence it fails if embedded in a xhtml page (or any other context where well-formed xml is required).
+
+The REST API, in contrast, only returns plaintext extracts at the moment. I could use them, but that's a workaround (avoiding rich formatting altogether) rather than a fix.
+
+Is there any way to use the REST API to get an html-formatted extract?",1493372514,PHID-USER-uazrhtptdqudzoqfefsc,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"I believe this is resolved?
+Is this what you were asking for: https://en.wikipedia.org/api/rest_v1/page/summary/Bavaria ?
+",1493322490,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Set up dev.wikimedia.org portal,"There's a few (not too many!) things that need a home, and I think this is a good time to start work on what will become the main entry point for developers to learn about Wikimedia (wiki) projects and Wikimedia (software) products.
+
+developer.wikimedia.org
+
+The initial portal wouldn't be unlike some of these:
+* https://developers.google.com/
+* https://developers.facebook.com/
+* https://dev.twitter.com/
+
+Here's are some very specific use cases that have come up during the Zurich Hackathon that I think would be best served with this:
+
+- Where do I find out about the existence of:
+  * gdash.wikimedia.org
+  * graphite.wikimedia.org
+  * noc.wikimedia.org
+  * doc.wikimedia.org
+  * git.wikimedia.org
+  * wikitech.wikimedia.org
+  * irc.wikimedia.org
+  ( * stream.wikimedia.org/rc )
+
+  Current solution: None
+
+  Current workaround for regulars:
+    https://wikitech.wikimedia.org/wiki/Category:Services
+
+- Where would I find out about xml dumps?
+
+  Current solution: None
+
+  Current workaround for regulars:
+    http://dumps.wikimedia.org/backup-index.html
+
+- Where would I find out about pageview count data?
+
+  Current solution: None
+
+  Current workaround for regulars:
+    http://dumps.wikimedia.org/
+      http://dumps.wikimedia.org/other/
+        http://dumps.wikimedia.org/other/pagecounts-raw/
+
+I'm sure the people from the ""Data API & Hub"" table from Zurich Hackathon 2014 have more specific stories and use cases. 
+
+This hub would act as delegate for the following cases (pointing to things on another domain or the same, some of which should probably move to it eventually):
+
+* Products
+  Such as:
+
+  - MediaWiki
+    -> Homepage
+    -> Source code (git repo)
+    -> Documentation (separate portal, on mediawiki.org for now, ultimately linking back to developer.wikimedia.org/mediawiki/{js,php,api} for documentation of individual classes and apis.
+        We already have JS and PHP docs autogenerated for MediaWiki.
+        Docs the API are still hardcoded on mediawiki.org and api.php/help
+        exclusively, we should get API and Hooks documentation onto
+        doc.wikimedia.org as well.
+        See https://www.mediawiki.org/wiki/Requests_for_comment/Documentation_overhaul
+
+  - VisualEditor
+    -> Source code
+    -> Demo(s)
+    -> Documentation
+
+* Data and APIs
+  (APIs that are not related to MediaWiki or individual user-facing products, but Wikimedia services in general, MediaWiki's API is one small part of that)
+
+  Such as:
+
+  * page view counts
+  * xml dumps
+  * OAuth?
+  * irc.wikimedia.org
+  ( * stream.wikimedia.org/rc )
+  * ""See also: Wikidata""
+
+* Communications
+  - (e.g. link to tech blog, as currently linked from noc.wikimedia.org)
+  - mailing lists
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=29936",1399646220,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yrfd4dhbbio3uikl5u33,task_description,declined
+Set up dev.wikimedia.org portal,"This task has been lingering for five years. 
+The domain mentioned in the summary has existed for years (resolved).
+However, the content/workflow/thoughts in the task description do not (not resolved).
+
+I'm boldly decline this (very #epic broad) task in favor of the #Wikimedia-Developer-Portal project which allows a better breakdown of subtasks. 
+See https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal for more info (still going to take me 2-3 more weeks to sort out the very basics though - patience please!)",1597919448,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,please also see T246945 which might conflict with this effort and introduce yet another place for documentation rather than having a single place for developers to go to,1590062421,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Would this task be a good topic for the #wikidev17 ? If so, the deadline to submit new proposals is next Monday, October 31: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation",1477574862,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"I have detached this proposal from {T101441} and #web-APIs-Hub because the latter has defined its scope within web APIs only (which happens to be the scope of the Google, Facebook, Twitter examples given above).
+
+Being Wikimedia also the umbrella of hundreds of open source projects, we have a more complex picture. What should be the one and only home to find about all of them? In short, my opinion is to make http://mediawiki.org that home, linking wherever it is needed.",1439046147,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"#Engineering-Community with the help of @spage are committing to this goal for the next quarter: {T101441}.
+
+I think it is time to conciliate that goal with this task, and to find the best relationship with both that we can achieve by the end of September.",1434014667,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 197272 merged by BBlack:
+dev.wm.org - Increase HSTS max-age to 1 year
+
+[[https://gerrit.wikimedia.org/r/197272]]",1426599931,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 197272 had a related patch set uploaded (by Chmarkine):
+dev.wm.org - Increase HSTS max-age to 1 year
+
+[[https://gerrit.wikimedia.org/r/197272]]
+",1426564386,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 195338 merged by BBlack:
+Enable HSTS on dev.wm.org max-age=7 days
+
+[[https://gerrit.wikimedia.org/r/195338]]",1426025069,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 195338 had a related patch set uploaded (by Chmarkine):
+Enable HSTS on dev.wm.org max-age=7 days
+
+[[https://gerrit.wikimedia.org/r/195338]]
+",1425929398,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,">>! In T67074#1013909, @Qgil wrote:
+> We have decided to [[ https://phabricator.wikimedia.org/maniphest/query/zZr63xHvTU8d/#R | prioritize the creation of some actual content ]] under the existing API: namespace in mediawiki.org.
+
+Yes, content, then a portal page on mw.org featuring that content based on [[ https://www.mediawiki.org/wiki/dev.wikimedia.org#Structure |  wireframe ideas ]]. Once it's at ""better than draft"" status, dev.wikimedia.org can have a redirect to this, and doc.wikimedia.org can link to it.",1423521438,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,We have decided to [[ https://phabricator.wikimedia.org/maniphest/query/zZr63xHvTU8d/#R | prioritize the creation of some actual content ]] under the existing API: namespace in mediawiki.org.,1423039843,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"needs Apache config, then obviously some files to upload.. ",1421789349,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 181398 merged by Dzahn:
+add dev.wikimedia.org
+
+[[https://gerrit.wikimedia.org/r/181398]]",1420466525,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 181398 had a related patch set uploaded (by Qgil):
+add dev.wikimedia.org
+
+[[https://gerrit.wikimedia.org/r/181398]]
+
+#patch-for-review",1419253513,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,https://gerrit.wikimedia.org/r/#/c/181398/,1419250219,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"**sumanah** wrote:
+
+Removing myself from cc on this as I prepare to leave Wikimedia Foundation.",1411502025,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Let's merge this discussion with the work done at https://www.mediawiki.org/wiki/dev.wikimedia.org. Sorry for the duplicity of spaces, which will go away when we merge Bugzilla with Phabricator.
+
+We have settled on http://dev.wikimedia.org -- see 
+
+Name for the 'developer hub'
+http://fab.wmflabs.org/T488 
+
+and 
+
+URL of the Developer Hub
+http://fab.wmflabs.org/T490
+
+(In reply to Bawolff (Brian Wolff) from comment #6)
+> Why not just have dev.wikimedia.org redirect to a page on mediawiki.org.
+> That way people can update it as appropriate easily.
+
+Yes, this is the current plan that you can help fine tuning:
+
+Technology selection for the Developer Hub
+http://fab.wmflabs.org/T491
+
+How to redirect from dev.wikimedia.org
+http://fab.wmflabs.org/T558",1409036097,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"(In reply to Krinkle from comment #0)
+> 
+> developer.wikimedia.org
+> 
+> The initial portal wouldn't be unlike some of these:
+> * https://developers.google.com/
+> * https://developers.facebook.com/
+> * https://dev.twitter.com/
+
+* https://developer.github.com/
+* https://developer.yahoo.com/
+* http://dev.windows.com/
+* http://www.bing.com/dev
+
+
+https://developers.google.com/
+https://developers.google.com/maps/documentation/javascript/tutorial
+https://developers.google.com/maps/documentation/javascript/examples/map-simple",1408973486,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Why not just have dev.wikimedia.org redirect to a page on mediawiki.org. That way people can update it as appropriate easily.
+
+
+>- Where do I find out about the existence of:
+[..]
+>  * graphite.wikimedia.org
+
+Not much point telling people about the existence of a service they are not allowed access to.",1400968272,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"(In reply to Krinkle from comment #0)
+> * Data and APIs
+> 
+>   Such as:
+> 
+>   * page view counts
+>   * xml dumps
+>   * OAuth?
+
+Discovered today that there is such a thing as https://frdata.wikimedia.org
+ as well. To be documented at  https://wikitech.wikimedia.org/wiki/frdata.wikimedia.org.",1400967990,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Topic related with a session scheduled for tomorrow at 10:30 in the Wikimedia Hackathon:
+
+How does the data and developer hub fit into the current documentation
+https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Schedule#Saturday_May_10",1399653842,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Initial implementation proposal:
+
+ - static html wrapped in a lightweight php router for header/footer and nice url handling (e.g. no need to repeat too much for each subdirectory, it can be handled automatically using data and available directories (js,php,api,demo) and versions (master,REL1_23,etc.)), using twitter bootstrap (like doc.wikimedia.org)
+ - all in git (wikimedia/dev-docroot.git?)
+ - deployed via git-deploy
+
+The server for it only needs to be behind misc-lb-eqiad and be a git-deploy target. The main changes would come in from people via gerrit/git and deployed periodically.
+
+Changes to the auto-generated docs would be build by gallium, and somehow pushed to the web server (they wouldn't be in dev-docroot.git).",1399647886,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"I'm in full support of this. 
+
+As someone working on this https://www.mediawiki.org/wiki/API_Documentation_&_Developer_Hub, I would like this very much.",1399646680,PHID-USER-xtudulsp3haty5uagokz,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"I think all of doc.wikimedia.org can migrate to appropriate paths on this domain.
+
+Like:
+- dev.wikimedia.org/mediawiki/doc/js
+- dev.wikimedia.org/mediawiki/doc/php
+- dev.wikimedia.org/mediawiki/doc/api
+- dev.wikimedia.org/visualeditor/doc
+- dev.wikimedia.org/visualeditor/demo
+- dev.wikimedia.org/oojs-ui/doc
+- dev.wikimedia.org/oojs-ui/demo
+- dev.wikimedia.org/oojs/doc",1399646574,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+"VisualEditor:  If you insert a gallery into a list, the list formatting remains visible but is removed in wikitext","Intention:
+Add an image gallery at the top of a section.
+
+Steps to Reproduce:
+1. Open a page that has a list at the top of the section.  
+
+2. Place your cursor at the top of the list, and Insert > Gallery.
+
+
+Actual Results:  
+The bullet remains visible.  The text of the list item is on the next line, but indented.
+
+However, when you save, the list formatting (the asterisk at the start of the line) has been removed.
+
+Expected Results:  
+The gallery would be inserted before the list.  That is,
+
+* List item
+
+would turn into 
+```
+<gallery>File:Example.jpg
+File:Example2.jpg</gallery>
+
+* List item
+```
+instead of into
+
+```
+ <gallery>File:Example.jpg
+File:Example2.jpg</gallery>List item
+```
+(Notice the stray space at the start of the line.)
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=92775&oldid=92716",1399497480,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ijh5ohctbismuiczyzo7,task_description,open
+"VisualEditor:  If you insert a gallery into a list, the list formatting remains visible but is removed in wikitext","Unlike legacy parser which breaks the list (T11996), Parsoid well supports `<gallery>` inside list item: wikitext-to-html [[https://meta.wikimedia.org/w/index.php?title=User:Pols12/Sandbox&oldid=26371690&useparsoid=1 | seems to work correctly]].
+However, this bug seems to indicate there is an issue with html-to-wiktext, since VisualEditor rendering is correct:
+
+```lang=html
+<li id=""mwBQ"" class=""ve-ce-branchNode"">
+  <div class=""ve-ce-branchNode-slug ve-ce-branchNode-blockSlug"">…</div>
+  <ul class=""ve-ce-branchNode gallery ve-ce-focusableNode"">
+    <li class=""ve-ce-branchNode gallerybox"">
+      <div class=""thumb"" style=""width: 150px; height: 150px;"">…</div>
+      <a href=""#"" class=""oo-ui-element-hidden"">…</a>
+      <div class=""ve-ce-branchNode ve-ce-activeNode gallerytext"">…</div>
+    </li>
+  </ul>
+  <p class=""ve-ce-branchNode ve-ce-contentBranchNode ve-ce-paragraphNode ve-ce-generated-wrapper"">List item</p>
+</li>
+```
+which should be parsed as 
+```lang=wikitext
+* <gallery>
+…
+</gallery> List item",1710098493,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-ijh5ohctbismuiczyzo7,task_subcomment,NA
+"VisualEditor:  If you insert a gallery into a list, the list formatting remains visible but is removed in wikitext",Update:  This is still happening.  https://en.wikipedia.org/w/index.php?diff=852318770&oldid=852318749&diffmode=source,1532748970,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ijh5ohctbismuiczyzo7,task_subcomment,NA
+"VisualEditor:  If you insert a gallery into a list, the list formatting remains visible but is removed in wikitext","This sort of happens if you insert a references list, which gives you this:
+
+* 
+<references />List item
+
+
+but not for images, math, templates, etc.",1399500501,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ijh5ohctbismuiczyzo7,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"From MediaWiki.org:
+
+> I would like to have an omnibar in VE. This is a single text field where
+> a user can search for things they want to do, instead of clicking a
+> button you can invoke omnibar with a keyboard shortcut and then search
+> for the task you want to do. This would be helpful to easier access those
+> buttons which don't have shortcuts now. Like managing category, inserting
+> reference, changing to source editor etc.
+
+Seems like it could be a lot of work to implement – for example, internationalisation of such controls might be hard – but it might be particularly useful for power users (or for controls that don't have a keyboard shortcut, as the proposer notes).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399309080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-myea7wfzzuri5j6zmpgx,task_description,resolved
+VisualEditor: Provide an omnibar for quick keyboard access to tools,">>! In T66905#8947788, @Sebastian_Berlin-WMSE wrote:
+> Ctrl+shift+p doesn't work for me (backslash does). This is on Ubuntu 22.04 and Firefox 114. What happens instead is that a private window is opened, which is the normal behaviour in Firefox.
+
+Filed as T341603",1689097619,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Ctrl+shift+p doesn't work for me (backslash does). This is on Ubuntu 22.04 and Firefox 114. What happens instead is that a private window is opened, which is the normal behaviour in Firefox.",1687241247,PHID-USER-fgieaqsdluipfhgequws,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"@John_Broughton yes, that’s expected. It should be removed if you chose something from the menu, and otherwise stick around (e.g. if you actually wanted to type a backslash). You can trigger it without entering a character by pressing {cmd/ctrl}-shift-p if you prefer to avoid that.",1687207492,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"When I'm in Visual Editor, and type a ""\"", I see this toolbar. However, the ""\"" is inserted into the text of the page being edited, as is illustrated at https://commons.wikimedia.org/wiki/File:Visual_editor_toolbar_search_feature.png  Is that the expected behavior? 
+",1687207174,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,">>! In T66905#8935569, @DLynch wrote:
+> @Trizek-WMF It's already out, but your comment made me notice that it's broken this week, so https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/930637 will fix that.
+
+Now I get why I couldn't use it. :)
+
++1 to @Quiddity. Documentation is important, and much more efficient than a one-time announcement or serendipity. ",1686914696,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"It would be best if the image was part of the official documentation, and could be linked to as part of the text within Tech News, rather than just a footnote. Perhaps someone from the Editing team could add it to https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide wherever is appropriate? I'm not sure how your (great!) multilingual screenshot system works, nor where within that page to locate a new section mentioning the feature, hence haven't attempted to add it myself. Thanks!",1686858294,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"@Trizek-WMF It's already out, but your comment made me notice that it's broken this week, so https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/930637 will fix that.",1686844111,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,When this (cool) feature will be on wikis? ,1686824741,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"There isn't, but here's a screenshot: https://commons.wikimedia.org/wiki/File:Visual_editor_toolbar_search_feature.png",1685447252,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Thanks for the draft wording for Tech News!
+Is there a wiki-page the entry could link to, showing an image or text-description of the feature?",1685050127,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921682 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Register a HelpCompletionAction group alias for cite%%%
+https://gerrit.wikimedia.org/r/921682",1684950708,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 922577 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (12333c596)%%%
+https://gerrit.wikimedia.org/r/922577",1684936842,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 922577 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (12333c596)%%%
+https://gerrit.wikimedia.org/r/922577",1684859894,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921683 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] HelpCompletionAction: rename and clean up commandGroups to toolGroups%%%
+https://gerrit.wikimedia.org/r/921683",1684766260,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921677 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Add fuzzy bar to the help dialog%%%
+https://gerrit.wikimedia.org/r/921677",1684766235,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921683 had a related patch set uploaded (by DLynch; author: DLynch):
+%%%[VisualEditor/VisualEditor@master] Clean up the cite group alias since it's moving to the extension%%%
+https://gerrit.wikimedia.org/r/921683",1684664237,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921682 had a related patch set uploaded (by DLynch; author: DLynch):
+%%%[mediawiki/extensions/Cite@master] Register a HelpCompletionAction group alias for cite%%%
+https://gerrit.wikimedia.org/r/921682",1684664209,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921677 had a related patch set uploaded (by DLynch; author: DLynch):
+%%%[VisualEditor/VisualEditor@master] Add fuzzy bar to the help dialog%%%
+https://gerrit.wikimedia.org/r/921677",1684661116,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Adding for tech news, suggested description: ""VisualEditor now includes a toolbar search popup that can be triggered by typing `\` or pressing `ctrl/cmd + shift + p`, which will let you quickly access most tools available inside the editor.""",1684665297,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Adding for tech news, suggested description: ""VisualEditor now includes a command search popup that can be triggered by typing `\` or pressing `ctrl/cmd + shift + p`, which will let you quickly access most tools available inside the editor.""",1684661044,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Post-merge tagging these patches:
+* https://gerrit.wikimedia.org/r/#/c/744905
+* https://gerrit.wikimedia.org/r/#/c/921462
+* https://gerrit.wikimedia.org/r/#/c/921588
+* https://gerrit.wikimedia.org/r/#/c/745282",1684658065,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"I want to use the HTML code <mark> in the newsletter and still be able to edit the draft page in VisualEditor.  Right now, adding <mark> produces nowiki tags, and opening a page with <mark> already on it prevents editing the marked text (alienated content).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398362520,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-5ho3axzxyziic5a47eop,task_description,open
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"I had seen that, but given that it didn't mention the word ""text"" and that elsewhere you were so strongly against the idea, I had to assume it was actually about the page color.
+The ability to set a text background in whatever color we want (#FC0FC0, in my case) will IMHO make using <mark> unnecessary.",1415296452,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"(In reply to Elitre from comment #7)
+> No! Google Docs allows highlighting text in the color I want. Please make
+> that happen somehow?
+
+That's not highlighting with <mark>, that's setting text background colour which is bug 73041.",1415231587,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),No! Google Docs allows highlighting text in the color I want. Please make that happen somehow?,1415227751,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"(In reply to Elitre from comment #5)
+> I'm unhappy. I demand the ability to pick my favorite color when
+> highlighting.
+
+Talk to W3C. ;-)",1415227351,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),I'm unhappy. I demand the ability to pick my favorite color when highlighting.,1415227094,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"(In reply to Elitre from comment #3)
+> Will this only allow marking the text in yellow?
+
+It will mark the text with <mark>. It's up to users' browsers to decide how to show it as marked, but yes, all major browsers ape the neon-lemon-yellow highlighter colour to show this currently.",1415226752,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),Will this only allow marking the text in yellow?,1415221139,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"Change 141605 merged by jenkins-bot:
+Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
+
+https://gerrit.wikimedia.org/r/141605",1404154589,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"Change 141605 had a related patch set uploaded by Jforrester:
+Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
+
+https://gerrit.wikimedia.org/r/141605",1403568483,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+"VisualEditor: Make MW toolbar integrate into the new ""floating toolbar"" beta feature when enabled","Right now it's a horrible mess. :-(
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398113460,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-swkths2fnka7qjw7zpsv,task_description,invalid
+"VisualEditor: Make MW toolbar integrate into the new ""floating toolbar"" beta feature when enabled",Said feature was killed off.,1493662390,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-swkths2fnka7qjw7zpsv,task_subcomment,NA
+"VisualEditor: VE-core, OOjs and OOjs-UI update scripts share commonalities but don't share code","We should merge them together where appropriate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1397873640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-brrtew2a7sjhjj6dapyh,task_description,open
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Read mode
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add a bullet list
+3.Add an image as a bullet point 
+4.Save the page
+5.Reopen the page 
+
+
+Observed Result:
+The bullet point appears on the read mode but not inside VE, but when you type something in that position the bullet point appears again.
+
+See the screenshot attached
+
+Page:
+http://en.wikipedia.beta.wmflabs.org/wiki/After_switch
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13837}",1397863440,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_description,resolved
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,Verified the fix in production.,1398988023,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,Verified the fix on test2,1398906351,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Change 127387 merged by jenkins-bot:
+Remove unnecessary overflow:hidden from block slug style
+
+https://gerrit.wikimedia.org/r/127387",1398107347,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Change 127387 had a related patch set uploaded by Esanders:
+Remove unnecessary overflow:hidden from block slug style
+
+https://gerrit.wikimedia.org/r/127387",1397865770,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Caused by a bug in Chrome, reported upstream: https://code.google.com/p/chromium/issues/detail?id=365024",1397865735,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Created attachment 15139
+Inside VE
+
+**Attached**: {F13838}",1397863503,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: Broken appearance when window is too small in Internet Explorer,"just ugh
+
+See attached screenshot.  Green Highlight is the cursor bar -- showing the cursor and the top of the page is somehow ending up under the heading instead of just below it.  Red hightlight is the outline of the (not showing) warning about using an unsupported browser.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13658}",1397146020,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-hrp2vnudp6cwigusycqf,task_description,declined
+VisualEditor: Broken appearance when window is too small in Internet Explorer,"This doesn't happen for me in IE10. The cursor does go under the toolbar, but that is a general issue (there's a lot of scrolling weirdness in IE still). I can't reproduce the invisible notice.",1409957935,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hrp2vnudp6cwigusycqf,task_subcomment,NA
+VisualEditor: Broken appearance when window is too small in Internet Explorer,"Fixed in IE11, at least.",1409099795,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hrp2vnudp6cwigusycqf,task_subcomment,NA
+VisualEditor: Keyboard shortcuts help page should use kbd elements,"This page should be using the html5 element <kbd> to represent the keyboard keys.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1397136240,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-qez6iozv44a6hxiwzacj,task_description,resolved
+VisualEditor: Keyboard shortcuts help page should use kbd elements,"Change 125212 merged by jenkins-bot:
+Put CommandHelpDialog keyboard shortcuts in kbd not div elements
+
+https://gerrit.wikimedia.org/r/125212",1397239055,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qez6iozv44a6hxiwzacj,task_subcomment,NA
+VisualEditor: Keyboard shortcuts help page should use kbd elements,"Change 125212 had a related patch set uploaded by Jforrester:
+Put CommandHelpDialog keyboard shortcuts in kbd not div elements
+
+https://gerrit.wikimedia.org/r/125212",1397145373,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qez6iozv44a6hxiwzacj,task_subcomment,NA
+"Provide easy, backend way for extensions to show PostEdit notifications with custom content","I've recently been working on an extension, and it would be nice for it to show a PostEdit success box when it successfully completes an operation. However, doing this at the moment would mean loading a Javascript file, the PHP setting a JS config var for whether to display the PostEdit box or not, JS checking this variable, JS getting a message for the text to display, etc.
+
+What would really be useful would be a way, just in PHP, for extensions to specify that a PostEdit box should be shown, with the text to display. The code would then ensure that JS to show the box is loaded on the page (which would possibly also save resources over the above method).
+
+I am not entirely sure how this would be best implemented, but possibly something like wfShowPostEdit( $text ), that could be easily called in an extension's code. Something like this would make it many more times easier for extensions to show PostEdit boxes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1397069820,PHID-USER-xpto4uqv737bawfiy53m,PHID-TASK-tefwphwiw2bjgqazm5r5,task_description,declined
+"Provide easy, backend way for extensions to show PostEdit notifications with custom content","I think what you're looking for is `mw.notify()`.
+
+See also <https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.plugin.notify>. Be sure to load the `mediawiki.notify` module (or add it as dependency to your script).
+
+There are various examples in MediaWiki core that use this. Including the ajax modules for patrol and watch actions. E.g. click the watch star on a page when logged-in.",1457647347,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tefwphwiw2bjgqazm5r5,task_subcomment,NA
+"Provide easy, backend way for extensions to show PostEdit notifications with custom content","Yeah, it would be nice extensions to be able to show their own messages, depending on their function.
+
+(Sorry about the categorisation stuff, still pretty unexperienced here :) )",1397075634,PHID-USER-xpto4uqv737bawfiy53m,PHID-TASK-tefwphwiw2bjgqazm5r5,task_subcomment,NA
+"Provide easy, backend way for extensions to show PostEdit notifications with custom content","MediaWiki 1.21 provides a wgPostEdit variable (bug 43270) depending on mediawiki.action.view.postEdit. 
+Per bug 48276, the VisualEditor extension depends on it, but looks like you'd like to define your own strings to display here?",1397074968,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tefwphwiw2bjgqazm5r5,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","On every page there is an icon of a pencil.
+
+It is linked to #editor/0.
+
+I.e. there is no way to edit any other section than section 0.
+
+Maybe it was assumed that /0 meant the whole page.
+
+Anyway one must manually change the url to /1, /2 etc.",1396838700,PHID-USER-awbqewknju4hbrnah6pm,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_description,duplicate
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","@Jdlrobson @Niedzielski, thoughts:
+
+It seems like there are possibly two confusing things going on here:
+
+**1) Articles with empty lead sections**
+-I find the fact that this page/article doesn't have a lead section to be slightly confusing. It took me a bit to understand how that was happening in the first place. Maybe this is just because I'm inexperienced with Wikis.
+-I wonder how common this situation is where the lead section is totally blank (I took a look around at some talk pages and other non-article namespace pages...it seems like often even when there is no text in the lead section there is still some stuff, e.g. a template, in there)
+-I wonder if people in this situation are intending to have empty lead sections, or if they don't realize that starting the article/page with a heading causes this slightly awkward situation
+-Do we have an opinion on whether or not it's ""okay"" to start an article/page with a heading? I suppose we could discourage it, or at least alert people so that there's a bit more awareness of what's going on here
+
+**2) The fact that on mobile you can only edit one section at a time**
+-agreed it's confusing that the edit pen for the lead section is located on top of the article, but then again the lead section doesn't have a heading like the other sections do so it'd be impossible to match the pattern used in subsequent sections
+-I wonder if this one section at a time editing is confusing to people in general, or only when they find themselves editing an empty lead section
+
+That being said, I wonder if there's something relatively cheap we can do with the empty state here? e.g.
+
+{F16725187}",1522970368,PHID-USER-cjbkqgaozso5gfp3xv2n,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button",This is being handled as part of the Fixed Header / Winter Beta feature https://www.mediawiki.org/wiki/Winter,1397843948,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","In the case of VE this does mean edit the entire page.
+On tablets/desktops we may make this mean the entire page.
+
+cc'ing Jared in case he can comment on the long term strategy.",1397843273,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","This is currently by design to make editing easier on a mobile screen by optimising for section editing.
+
+We are currently exploring full page edits in our work on VisualEditor. This may or may not get addressed as part of that.",1396981946,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","Maybe if there is nowhere else to put it, have that row be:
+Pencil (edit whole article), upload, watch, Pencil+0 (edit section 0)",1396934169,PHID-USER-awbqewknju4hbrnah6pm,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","The star watchlist icon applies to the entire article, so one assumes the same with the edit icon appearing in the same row. I didn't test the upload icon.",1396934041,PHID-USER-awbqewknju4hbrnah6pm,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","Ah... I get it!
+To edit section | use pencil at
+0 | top left
+1 | side right
+2 | side right
+3 | side right
+4 | side right
+
+Who would have ever guessed!
+
+One assumes instead:
+
+To edit section | use pencil at
+entire article | top left
+0 | side right
+1 | side right
+2 | side right
+3 | side right
+4 | side right",1396933316,PHID-USER-awbqewknju4hbrnah6pm,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","**jgonera** wrote:
+
+Are there no pencil icons in sections when you unfold them? If no, can you provide a URL?",1396891012,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1909",1396839008,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+VisualEditor: Switch action=opensearch calls to list=prefixsearch where appropriate,"Gerrit af6d9ab introduced list=prefixsearch which can be used as a generator, which action=opensearch can't be. This would allows us to avoid taking the output of opensearch and turning around to make follow-up API requests for e.g. pageprops to see if they are redirects or whatever.
+
+We shouldn't do this switch until MW1.23 is released, at least, however.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1396659720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6zm5srh6har3jnrlfrt6,task_description,resolved
+VisualEditor: Switch action=opensearch calls to list=prefixsearch where appropriate,"Change 134632 merged by jenkins-bot:
+Switch action=opensearch call to list=prefixsearch where appropriate
+
+https://gerrit.wikimedia.org/r/134632",1401323903,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6zm5srh6har3jnrlfrt6,task_subcomment,NA
+VisualEditor: Switch action=opensearch calls to list=prefixsearch where appropriate,"Change 134632 had a related patch set uploaded by Alex Monk:
+Switch action=opensearch calls to list=prefixsearch where appropriate
+
+https://gerrit.wikimedia.org/r/134632",1400689052,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6zm5srh6har3jnrlfrt6,task_subcomment,NA
+Add Vietnamese (vi) input method,"(In reply to Minh Nguyễn from bug 5309 comment #45)
+> many Vietnamese Wikipedia users rely on an IME script embedded via
+> a gadget, but gadgets are disabled at [[Special:UserLogin/signup]]. We’d
+> need to port the (rather complex) IME to ULS to keep the signup form
+> accessible.
+
+We definitely should! It shouldn't be hard, jquery.ime only needs a comma separated list of input keys -> result character pairs.
+https://github.com/wikimedia/jquery.ime/wiki/Technical-Specification#input-method-definition
+If you can't prepare such a table, can you ask other vietnamese users?
+
+--------------------------
+**Version**: master
+**Severity**: enhancement
+**See Also**:
+https://github.com/wikimedia/jquery.ime/issues/342",1396517460,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_description,open
+Add Vietnamese (vi) input method,"As noted in T286863#7287345, @MikePlantilla has begun work on a jquery.ime-based reimplementation of Vietnamese IME.
+
+In case it helps, the AVIM Firefox extension’s repository has [a battery of automated tests](https://github.com/1ec5/avim/blob/master/tests/corpus.js) that ensures [the entire corpus](https://github.com/1ec5/hunspell-vi/blob/master/dictionaries/vi-DauCu.dic) of words in the Free Vietnamese Dictionary Project can be typed using a variety of tone mark placements. I put together this integration test because the core AVIM code is difficult to reason about and impossible to unit test, but it would be applicable to any IME implementation. Feel free to rig it to test your implementation.",1629178059,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"As noted in T286863#7287345, @MikePlantilla has begun work on a jquery.ime-based reimplementation of Vietnamese IME.
+
+In case it helps, the AVIM Firefox extension’s repository has [a battery of automated tests](https://github.com/1ec5/avim/blob/master/tests/corpus.js) that ensures [the entire corpus](https://github.com/1ec5/hunspell-vi/blob/master/dictionaries/vi-DauCu.dic) of words in the Free Vietnamese Dictionary Project can be typed using a variety of tone mark placements. Feel free to rig it to test your implementation.",1629177986,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"As noted in T286863#7287345, @MikePlantilla has begun work on a jquery.ime-based reimplementation of Vietnamese IME.
+
+In case it helps, the AVIM Firefox extension’s repository has [a battery of automated tests](https://github.com/1ec5/avim/blob/master/tests/corpus.js) that ensures [the entire corpus](https://github.com/1ec5/hunspell-vi/blob/master/dictionaries/vi-DauCu.dic) of words in the Free Vietnamese Dictionary Project can be typed using a variety of tone mark placements.",1629177880,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"(In reply to Nemo from comment #3)
+> (In reply to Minh Nguyễn from comment #2)
+> > I'd be happy to try and port AVIM to jquery.ime, but it may take awhile.
+> 
+> That would be wonderful! Please assign this bug to yourself when you start
+> working on it.
+
+Indeed, this would be wonderful. I'll gladly help with that. It shouldn't be very hard. jqeury.ime had pretty good docs for developers. Please contact me if you need any assistance.",1398158005,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"(In reply to Minh Nguyễn from comment #2)
+> I'd be happy to try and port AVIM to jquery.ime, but it may take awhile.
+
+That would be wonderful! Please assign this bug to yourself when you start working on it.
+
+> Fortunately, most of the complexity relates to text selection handling,
+> which should be handled by jquery.ime already.
+
+Nice. If other features are missing and block the port, please file them as soon as possible at https://github.com/wikimedia/jquery.ime/issues .",1396523951,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"Forgot to link [[vi:MediaWiki:Gadget-AVIM.js]] and [[vi:MediaWiki:Gadget-AVIM portlet.js]].
+
+I'd be happy to try and port AVIM to jquery.ime, but it may take awhile. Fortunately, most of the complexity relates to text selection handling, which should be handled by jquery.ime already.",1396521328,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"Unfortunately, it isn't quite that simple. Vietnamese users expect IME-like functionality, not just a keyboard layout. For instance, with the [[Telex (IME)]] input method, ""Vietje"" should become ""Việt"", ""truongwf"" should become ""trường"", and if you're indecisive enough, ""masfsfsfsfrxj"" should become ""mạ"". ""Wasshington"" should become ""Washington"" rather than ""Wáington"" or ""Wahíngton"".
+
+Much of this can be accomplished with regular expressions, but it might be easier to shoehorn an existing Vietnamese IME into jquery.ime. AVIM.js is very reliable and is available under an MIT license, but no one really understands the core code. bogo.js [1] is much cleaner but much more limited and only available under the MPL. Mudim [2] is a bit cleaner and is GPL2-licensed but has its own limitations, like an input buffer (not ideal for Vietnamese) and poor support for VIQR.
+
+We'll definitely need support for a few input method-specific preferences, particularly tone mark placement (xóa vs. xoá) and spelling rule enforcement (Wahíngton vs. Washington).
+
+AVIM works pretty well with VisualEditor and other features, so at the Wikimedia wikis, the only real benefit to ULS integration would be getting an IME on Special: pages. (The current workaround is to install a system IME or browser extension, or to use a bookmarklet.) I wouldn't recommend adopting a simplistic keyboard layout even as a stopgap measure, because then it'd be forced upon the Vietnamese wikis and literally no one would want to use it.
+
+Full disclosure: I maintain a Firefox extension based on AVIM.js [3], but these comments are more from the perspective of a Vietnamese Wikipedian.
+
+[1] https://github.com/lewtds/bogo.js
+[2] https://code.google.com/p/mudim/
+[3] http://avim.1ec5.org/en/",1396520914,PHID-USER-sxpswmchfwxkuo2wszeo,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"targetFn.super = originFn;
+
+triggers a JS error in IE 8, and presumably in older versions of IE as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396274940,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-avlkvijmssa6on3rse52,task_description,resolved
+OOjs: Should be parseable by ES3 engines,"Change 124360 merged by jenkins-bot:
+core: Use bracket notation for 'super' for ES3 compatibility
+
+https://gerrit.wikimedia.org/r/124360",1403116763,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"(In reply to Tisza Gergő from comment #12)
+> (In reply to Krinkle from comment #10)
+> > I know for a fact that ""throws"" is perfectly safe (for I did extensive
+> > research to verify it's safety going back to IE6 before adopting it un
+> > QUnit).
+> 
+
+We don't use throws outside unit tests (it's a method name for QUnit) and as said,
+it's perfectly safe back to IE6.",1403114342,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"(In reply to Krinkle from comment #10)
+> I know for a fact that ""throws"" is perfectly safe (for I did extensive
+> research to verify it's safety going back to IE6 before adopting it un
+> QUnit).
+
+It would be easy to fix, though: it is only used by sinon.js which supplies aliases for all ES3-incompatible function names. For throws() it is throwsException(), I think.",1403113010,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"(In reply to Gilles Dubuc from comment #9)
+> That plan looks good to me. Since this bug is still marked as low priority,
+> I imagine that you guys won't get around to it for at least a few months.
+> 
+> Since we're starting to work on UploadWizard and using OOJS for it will
+> probably be on our todo list, would you be comfortable letting us implement
+> ES3 support for OOJS the way you've just described? With you guys providing
+> active review on it, so that we're not blocked waiting for too long?
+> 
+> That's assuming that we'll decide to keep UploadWizard ES3-compatible, but I
+> want to see what our options will be.
+
+Sorry for not seeing this comment earlier; this looks to now essentially be done. We'll need to merge the ES3-parsability (gerrit 124360), release a new version of OOjs, and pull it into MediaWiki, with the new ES5 shim (gerrit 139308).
+
+
+(In reply to Krinkle from comment #10)
+> Enabling 'es3: true' in jshintrc shows that we're supposed to avoid ""throws""
+> (qunit), ""super"" (oojs) and ""static"" (oojs).
+> 
+> I know for a fact that ""throws"" is perfectly safe (for I did extensive
+> research to verify it's safety going back to IE6 before adopting it un
+> QUnit).
+> 
+> Running a test shows that ""static"" is safe as well. It's only ""super"".
+
+Is there a way we can get jshint to add an ""es3-actual"" flag so we can ensure that ES5-syntax-isms don't accidentally creep back into the codebase automatically?",1403107696,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"Enabling 'es3: true' in jshintrc shows that we're supposed to avoid ""throws"" (qunit), ""super"" (oojs) and ""static"" (oojs).
+
+I know for a fact that ""throws"" is perfectly safe (for I did extensive research to verify it's safety going back to IE6 before adopting it un QUnit).
+
+Running a test shows that ""static"" is safe as well. It's only ""super"".
+
+Test suite:  http://fiddle.jshell.net/bsz74/show/light/
+
+(source: http://jsfiddle.net/bsz74/)
+
+Test results via browserstack.com:
+* Windows 7 / IE 9: all pass
+* Windows 7 / IE 8: 1 failure (super)
+* Windows XP / IE 8: 1 failure (super)
+* Windows XP / IE 7: 1 failure (super)
+* Windows XP / IE 6: 1 failure (super)
+* Windows XP / Opera 12.10: all pass
+* Windows XP / Firefox 3: all pass
+* Windows XP / Safari 4: 1 failure (super)
+* Windows XP / Safari 5.0: 1 failure (super)
+* Windows XP / Safari 5.1: all pass
+* OSX 10.6 Snow Leopard / Safari 4: 1 failure (super)
+* OSX 10.6 Snow Leopard / Safari 5.0: 1 failure (super)
+* OSX 10.6 Snow Leopard / Safari 5.1: all pass
+* OSX 10.6 Snow Leopard / Firefox 4: all pass
+* iPhone 3GS / iOS 3: 1 failure (super)
+* iPhone 4 / iOS 4.0: 1 failure (super)
+* iPhone 4S / iOS 5.0: all pass",1403076951,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"That plan looks good to me. Since this bug is still marked as low priority, I imagine that you guys won't get around to it for at least a few months.
+
+Since we're starting to work on UploadWizard and using OOJS for it will probably be on our todo list, would you be comfortable letting us implement ES3 support for OOJS the way you've just described? With you guys providing active review on it, so that we're not blocked waiting for too long?
+
+That's assuming that we'll decide to keep UploadWizard ES3-compatible, but I want to see what our options will be.",1399544882,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"If .super were the only issue, then that could work. However that isn't the case.
+
+For one, there are a few more properties that aren't allowed in old browsers.
+
+And two, it isn't so much the property name but the functionality it provides that is missing in those browsers. Just a few off the top of my head:
+
+- Object.create
+- Array.isArray
+- JSON.stringify
+- Reliable hasOwnProperty (as used by isPlainObject)
+- Reliable typeof for native functions (as used by clone)
+
+Fixing .super will make the parser die slightly later, that's all.
+
+Fixing .super and the other properties will make the parser never die in IE8, but it will fail upon execution. Though execution is fine as long as you have a proper feature test (like VE has) before initialising too much.
+
+The ES5 methods OOjs uses (Object.create, Array.isArray, etc.) are perfectly polyfillable. I've always been very careful in OOjs to not adopt ES5 features that are fundamentally new language constructs that are cannot polyfill.
+
+However, just to explain that there is a little more to it. The exception you saw is just the tip of a small floe of ice. A small floe, but it won't melt on its own.
+
+So here's what I'd propose (in no particular order) for the medium to long term:
+
+- Make OOjs parseable in ES3 engines.
+
+- Document that OOjs is ES3 parser compatible, but does require ES5 features to be present. Consumer is responsible for providing a polyfill of their choosing if they need to support older browsers (write for the future, not the past).
+
+- Ship an ES5 shim in MediaWiki core which can be used as a dependency of oojs. And is conditionally loaded based on a quick feature test in a ResourceLoader dependency function that adds the dependency conditionally (this conditional dependency creation is a new feature in ResourceLoader's client js, however is not yet exposed on the server-side).
+
+
+This all of course is for OOjs core. OOjs UI makes much stronger use of browser behaviour (because it renders visually, polyfilling is generally not an option, it requires rigorous testing and adding of quirks and workaround for old browsers).
+
+For the short term:
+
+- OOjs currently requires ES5. *Do not load* this module in older browsers. It is the responsibility of the consuming code to feature test the environment before loading everything. This is why VisualEditor doesn't throw up in IE8.",1398786356,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"Change 124360 had a related patch set uploaded by Jforrester:
+core: Avoid an IE8 bug causing a fatal error when loaded on that platform
+
+https://gerrit.wikimedia.org/r/124360",1396892502,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"In case super still needs to be read/written for backwards compatibility, the syntax obj['super'] might work. Described here:
+http://tiffanybbrown.com/2013/09/10/expected-identifier-bug-in-internet-explorer-8/
+but a cursory search of the ES3 spec also suggests that this is valid.
+
+(I note that UploadWizard is apparently being converted to OOjs UI. Doing this while declaring IE 6-8 is not supported seems like a pretty horrible idea to me.)",1396573962,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"That fact could be made clearer in OOjs's README.md or a similar prominent place. I'm not sure that Mark knew this caveat at the time he embarked our project on the OOjs train. I think it would be very easy for another project to miss that fact as well. Resources.php is a really odd place if it's the sole warning.
+
+Full support aside, the fix to this bug is simply renaming ""super"". Seems like a quick win for potentially making Media Viewer available to more than 1 in 20 visitors who currently can't use it. I would have submitted a patch, but since this is the name of an important feature in your framework, I'd rather let you pick the new name.
+
+I understand that advanced WYSIWIG VE stuff is hard to do in ES3 and older, so ruling those browsers out for VE makes sense considering the effort/reward ratio. But what OOjs provides doesn't seem to me like it justifies ignoring 5%+ of our visitors, particularly if you're pushing for foundation-wide use of that framework (seems to be the reason why we ended up using it, anyway), since most features developed by the foundation don't do things as advanced as VE where older browsers are hard to support.
+
+I'm pretty sure that this bug right here is the only thing preventing OOjs ES3 support, at least for the subset of OOjs features that Media Viewer is using. I recall using Media Viewer fine in IE 6, 7 and 8 in January/February, which seems consistent with the timeline, considering that the code triggering the bug seems to have been introduced in March.
+
+If you fix this, you'll be getting continuous free help from us as a consumer of these frameworks when it comes to older IE support, because we'll be keeping an eye on it and submitting bug reports and patches when issues arise.",1396504506,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"ES3 compatibility isn't yet supported for OOjs, as stated in Resources.php.",1396461118,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"http://jsfiddle.net/PKdPz/1/embedded/result/
+
+browserstack/IE9: Pass
+browserstack/IE8: Fail
+     > Expected identifier
+
+Error details:
+ User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
+Timestamp: Wed, 2 Apr 2014 01:04:33 UTC
+
+ Message: Expected identifier
+ URI: http://fiddle.jshell.net/PKdPz/1/show/light/
+ Line: 33
+ Char: 7
+ Code: 0",1396400735,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Reserved_Words,1396278224,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"I think it could be as simple as renaming ""super"" to something else. It's most likely erroring because it's considered a reserved name.",1396276331,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),"The needcheck tag on it.wp recently detected half a dozen dirty diffs like this one: https://it.wikipedia.org/w/index.php?title=Respirazione_olotropica&curid=856162&diff=65014587&oldid=64980151 .
+
+This seems to be due to a broken browser plugin, NortonInternetSecurityBF .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396015020,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-g5funys7osn7lmrgyu2r,task_description,resolved
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),We believe that this is now worked around.,1427402671,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),https://no.wikipedia.org/w/index.php?title=Bruker:Bredekg%C3%A5rd&diff=13459686&oldid=13459676,1413390853,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114019,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113113,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),*** Bug 70537 has been marked as a duplicate of this bug. ***,1410130325,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+Show VisualEditor button label conditionally for GettingStarted tours,"Show the VisualEditor appendix conditionally for GettingStarted tours.  This is the same as {T63321}, but for GettingStarted tours.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1395868740,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-7o7uuh5g6ufbb6vnjvbo,task_description,declined
+Show VisualEditor button label conditionally for GettingStarted tours,"#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.",1703380311,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-7o7uuh5g6ufbb6vnjvbo,task_subcomment,NA
+VisualEditor: Automatically generate an edit summary for the user,"On stack overflow there is a nice feature that guess edit summary for user based on what they changed. So that when you edit something edit summary isn't empty, but contains things like:
+
+Replace ""foo"" with ""bar""
+
+OR
+
+Inserted 20 words, removed 2 lines in paragraph ""blah""
+
+OR
+
+Punctuation fixes
+
+User is still able to modify it afterwards but this already save so much time. It would be nice if Visual Editor would do the same, so that users who do minor edits wouldn't need to bother with writing the summary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52859",1395865740,PHID-USER-ppytiem7rcsbnstfsrvq,PHID-TASK-buuem2aad2voq2wmr3vg,task_description,duplicate
+VisualEditor: Automatically generate an edit summary for the user,*** Bug 70285 has been marked as a duplicate of this bug. ***,1409665309,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-buuem2aad2voq2wmr3vg,task_subcomment,NA
+VisualEditor:  Web Thunder Helper Plugin (download) leaves garbage in pages,"See https://en.wikipedia.org/w/index.php?title=User:MGMT90018_Turnover/sandbox&curid=42095125&diff=599418792&oldid=599219453
+The ""Web Thunder"" plugin script from xunlei.com leaves the following litter at the top and bottom of pages:
+
+<embed id=""xunlei_com_thunder_helper_plugin_d462f475-c18e-46be-bd10-327458d045bd"" type=""application/thunder_download_plugin"" height=""0"" width=""0"" />
+
+<embed id=""xunlei_com_thunder_helper_plugin_d462f475-c18e-46be-bd10-327458d045bd"" type=""application/thunder_download_plugin"" height=""0"" width=""0"" />
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395856260,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ncw7c5qs6xrgoatblkas,task_description,resolved
+VisualEditor:  Web Thunder Helper Plugin (download) leaves garbage in pages,"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114016,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ncw7c5qs6xrgoatblkas,task_subcomment,NA
+VisualEditor:  Web Thunder Helper Plugin (download) leaves garbage in pages,"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113148,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ncw7c5qs6xrgoatblkas,task_subcomment,NA
+"VisualEditor: Link can be applied on Cite Web/Book/Newspaper/Journal templates (but not reference nodes), which is confusing","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add a text then a Cite>Website/Book/Newspaper/Journal just after that 
+3.Now select both the text and the cite
+4.Apply link on it
+
+Observed Result:
+The link also gets applied on the Cite
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Reference_numbering?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13245}",1395787260,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-4sxb362teoe7szw6jzp3,task_description,open
+"VisualEditor: Link can be applied on Cite Web/Book/Newspaper/Journal templates (but not reference nodes), which is confusing",For templates we may need to have some kind of function that dynamically determines whether the template is linkable :(,1401925015,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4sxb362teoe7szw6jzp3,task_subcomment,NA
+"VisualEditor: Link can be applied on Cite Web/Book/Newspaper/Journal templates (but not reference nodes), which is confusing","This is hard to fix. Blacklisted annotation types are done on a per-node-type basis. Normal references are of type 'mwReference', but citations are of type 'mwTransclusionInline', and I don't think it's a good idea to make all templates unlinkable.",1401924989,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4sxb362teoe7szw6jzp3,task_subcomment,NA
+VisualEditor: IE9 doesn't load new page when when re-editing a page modified in another browser,"To reproduce:
+
+1. Load a page in IE in the visual editor.
+2. Load the same page in another browser, make a change, and save it.
+3. Load the page view in IE, confirm you can see the edit.
+4. Click ""Edit"" to enable the visual editor.  Old content appears in the editor.
+5. Quit IE and restart.  Load page to edit in VE.  See new content in the editor.
+
+Initially I thought this was simply a server configuration issue (and maybe it still is), but I tested the same thing in FF and got the new page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395704460,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-gyj6luke5ayhahap6efm,task_description,invalid
+VisualEditor: IE9 doesn't load new page when when re-editing a page modified in another browser,"Sounds like it may have been resolved in another task, so resolving invalid. Please reopen if this is still an issue",1436996751,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gyj6luke5ayhahap6efm,task_subcomment,NA
+VisualEditor: IE9 doesn't load new page when when re-editing a page modified in another browser,"Krenair writes:
+
+> Is this still a problem? Sounds like IE is caching wrongly?
+
+I doubt this is a problem now since {{T74480}} is resolved.",1436995874,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-gyj6luke5ayhahap6efm,task_subcomment,NA
+VisualEditor: IE9 doesn't load new page when when re-editing a page modified in another browser,Is this still a problem? Sounds like IE is caching wrongly?,1436994533,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-gyj6luke5ayhahap6efm,task_subcomment,NA
+VisualEditor: IE9 places cursor inside ce=false table cell,"With the following wikitext:
+
+  __NOTOC__ 
+
+  This is a test
+
+  {|
+  |-
+  | valign=""top"" | 
+  == Header  ==
+  * point one
+  * point two
+  ...
+
+VE starts up with the cursor on ""This"".  Pressing down once in FF ends up with the cursor on the ""Header"" line.  In IE, it ends up on the ""point one"" line.  Pressing up once in IE then puts the cursor on the ""Header"" line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395703680,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-selst62j4vfcyd5gk5mu,task_description,declined
+VisualEditor: IE9 places cursor inside ce=false table cell,IE9 support has been dropped: T162277,1491506647,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-selst62j4vfcyd5gk5mu,task_subcomment,NA
+VisualEditor: IE9 places cursor inside ce=false table cell,Cursoring into a table cell in IE9 now takes you inside the cell and lets you edit it. This is still wrong: it should create a table selection highlighting the first cell.,1460637599,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-selst62j4vfcyd5gk5mu,task_subcomment,NA
+VisualEditor: IE9 places cursor inside ce=false table cell,"(In reply to Roan Kattouw from comment #1)
+> This is working as expected now. Pressing down once puts the cursor at the
+> beginning of ""Header"" on my Windows 7 machine in IE10.
+
+...but of course this bug was filed against IE9. I'm blind.",1409961316,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-selst62j4vfcyd5gk5mu,task_subcomment,NA
+VisualEditor: IE9 places cursor inside ce=false table cell,"This is working as expected now. Pressing down once puts the cursor at the beginning of ""Header"" on my Windows 7 machine in IE10.",1409961194,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-selst62j4vfcyd5gk5mu,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","From the console:
+
+ SCRIPT70: Permission denied 
+ Main_Page, line 1 character 1
+
+Filing to track this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1395701760,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-rblj4bx5jecyxjn2maza,task_description,resolved
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","Change 283427 merged by jenkins-bot:
+Fix access of iframe-created document in IE9
+
+[[https://gerrit.wikimedia.org/r/283427]]",1461009288,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","Change 283427 had a related patch set uploaded (by Esanders):
+Fix access of iframe-created document in IE9
+
+[[https://gerrit.wikimedia.org/r/283427]]
+",1460636680,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","The iframe which is used to create the document is discarded and IE9 garbage collects it and wipes the document, even though we keep a pointer to the document.",1460636101,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","For the record, I haven't experienced this problem in weeks of messing around with VE in IE in either IE10 or IE11.",1409961388,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","Updated to latest VE (which shares MW's JQuery?) and saw the problem again.  Clicked IE's ""Start debugging"" in IE9 and wasn't able to reproduce it.
+
+Returned to page, clicked IE's ""Stop debugging"" and then clicked VE's ""Edit"".  Spinner went into infinite loop.
+
+Now, what are the dev tools setting up to cause this behavior?",1397145638,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","Created attachment 14910
+diff of changes to update jquery
+
+**Attached**: {F13122}",1395795363,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated",Got past part of the permission problem without messing with the registry (yay!) by looking at newer jQuery code and seeing how it avoided use of iframe.  It is now stopping in setUpSurface.,1395795311,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated",*** Bug 63043 has been marked as a duplicate of this bug. ***,1395784399,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","So after poking around for a bit I was able to get past this error with the following registry key set to ""1"":
+
+  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN
+  \FeatureControl\FEATURE_PROTOCOL_LOCKDOWN\iexplore.exe
+
+Isn't IE support fun?
+
+Now the save button (bug #63043) changes color but clicking it results in ""SCRIPT70: Permission denied"" that IE's debugger says comes from the following line in jquery.js:
+
+    proxy=function(){
+        return fn.apply(context,args.concat(core_slice.call(arguments)));
+    };
+
+Hints on registry keys from http://stackoverflow.com/questions/5352057/script70-permission-denied-ie9
+
+Looks like there may be some help in the newer versions of jquery: http://bugs.jquery.com/ticket/13936",1395784324,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),"Typing return to generate a new paragraph in FF works.  Filing this to ask for a pointer to figure out how I might track it down and fix it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1395701460,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_description,resolved
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),WFM in 9. 8 is not supported.,1460637023,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),"I was testing against IE8 or 9.  I've since upgraded that machine to 11, so it isn't available now.",1410029146,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),Works in IE10 too. Which version of IE did you observe this in?,1409961424,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),"Fixed in IE11, at least.",1409099678,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),still needs some tracking down for a reproducible case.,1395770447,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: User should be able to add gallery inside reference,"Right now, Users can add image inside reference dialog box, similarly they should be able to add gallery inside it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395687900,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7jtvwd2g3x4hb6rhdnxy,task_description,open
+VisualEditor: User should be able to add gallery inside reference,I'm not sure that's something we want to encourage?,1445614649,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-7jtvwd2g3x4hb6rhdnxy,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395097920,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rsayshdqztdym7km5qd3,task_description,resolved
+"VisualEditor: Get rid of $.proxy, use native .bind()",Removal of this function is punted to bug 72156.,1413498289,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 167055 merged by jenkins-bot:
+Replace calls to ve.bind( fn, ... ) with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/167055",1413497045,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 167055 had a related patch set uploaded by Alex Monk:
+Replace calls to ve.bind( fn, ... ) with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/167055",1413488877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 166155 merged by jenkins-bot:
+Replace calls to OO.ui.bind( fn, ... ) with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/166155",1413483227,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 166155 had a related patch set uploaded by Alex Monk:
+Replace calls to OO.ui.bind( fn, ... ) with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/166155",1412984168,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Alex Monk from comment #15)
+> (In reply to Krinkle from comment #14)
+> > VisualEditor core, and OOjs UI.
+> 
+> Me and Krinkle spoke about this and think it would be a better idea to defer
+> this for now. PhantomJS is not implementing Function#bind (like we would
+> expect) and that's necessary for the tests to succeed. In other repos we get
+> around this by loading es5-shim but in these ones we should be able to rely
+> on ES5 properly.
+
+With I64a0bd96b in VE-core and If2da01a25 in OOUI this is no longer a blocker.",1412975453,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Krinkle from comment #14)
+> VisualEditor core, and OOjs UI.
+
+Me and Krinkle spoke about this and think it would be a better idea to defer this for now. PhantomJS is not implementing Function#bind (like we would expect) and that's necessary for the tests to succeed. In other repos we get around this by loading es5-shim but in these ones we should be able to rely on ES5 properly.",1405360443,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Alex Monk from comment #13)
+> (In reply to Krinkle from comment #7)
+> > We now have the polyfill for Function.prototype.bind provided by MediaWiki
+> > so this should be easier to do now.
+> 
+> Heh.
+> 
+> Anyway, is there anything else to do here?
+
+VisualEditor core, and OOjs UI.",1405001970,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Krinkle from comment #7)
+> We now have the polyfill for Function.prototype.bind provided by MediaWiki
+> so this should be easier to do now.
+
+Heh.
+
+Anyway, is there anything else to do here?",1405001884,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 144840 merged by jenkins-bot:
+Replace ve.bind( fn, ... ) calls with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/144840",1405001506,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Krinkle from comment #10)
+> Why? How is this different from the other ES5 methods we've been using
+> already? VisualEditor nor OOjs UI support ES3 engines afaik.
+> 
+> MediaWiki itself does, and OOjs core does (for other consumers of OOjs). But
+> we don't (we user .super which breaks IE's ES3 parser, Array.isArray,
+> Object.keys etc.)
+> 
+> mw-ve, ve-core, oojs-ui, and oojs all share a requirement for ES5
+> environments beyond just the polyfillable methods.
+
+oojs-core supports ES3 engines but requires an ES5 shim. The same would apply to OOjs UI and/or VisualEditor core if and when we decide to support older browsers.",1404931697,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Why? How is this different from the other ES5 methods we've been using already? VisualEditor nor OOjs UI support ES3 engines afaik.
+
+MediaWiki itself does, and OOjs core does (for other consumers of OOjs). But we don't (we user .super which breaks IE's ES3 parser, Array.isArray, Object.keys etc.)
+
+mw-ve, ve-core, oojs-ui, and oojs all share a requirement for ES5 environments beyond just the polyfillable methods.",1404930429,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()",If we're going to replace ve.bind it should be done in ve core first so we'll need a polyfill there. In ve-mw we can omit that polyfill as mw loads it's own.,1404930088,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 144840 had a related patch set uploaded by Alex Monk:
+Replace ve.bind( fn, ... ) calls with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/144840",1404858922,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()",We now have the polyfill for Function.prototype.bind provided by MediaWiki so this should be easier to do now. Simply replace all uses of $.proxy(fn..) and ve.bind(fn) in the modules/ directory with calls to fn.bind(..).,1404774724,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Sorry, I got bit busy with my other project.",1403335083,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()",Ping on this bug again – do you need any support/advice/help?,1400888892,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","> (In reply to James Forrester from comment #1)
+> > Tony, are you planning to take on this bug?
+> 
+> I plan to. But is there anything like bind() is only present in modern
+> browsers ?
+
+Indeed, Function.prototype.bind is new in ECMAScript 5, which VisualEditor requires. Or rather, VE requires ECMAScript 3 syntax engine and an environment that somehow provides certain ES5 features, which can potentially be polyfilled. We don't yet (and that is by design), adopt any ES5 syntax or ES5 features that can't be polyfilled.
+
+This is already guarded against using the feature test in our mw integration init[1], so you can rely on this without having to worry about old browsers.
+
+(In reply to Roan Kattouw from comment #3)
+
+I'd recommend #2 for consistency (we do the same with other ES5 features we've adopted) and minor performance micro optimisation (extra global and property, extra callstack because it has to be a proxy calling bind, unlike Array.isArray is can't be assigned to ve.bind by reference because bind needs to be bound itself) and because we're already using '.bind' in a few places.
+
+But keeping ve.bind with a small wrapper to bind using bind seems fine for backwards compatibility with ve plugins in the wild. But I'd recommend we don't use this in core.
+
+[1] https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/7e52a1ab2ab514/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js#L74-L93",1395199898,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","We don't use $.proxy() directly in the VE code base, instead we set ve.bind = $.proxy; and use ve.bind().
+
+Yes, this.keyup.bind() exists in modern browsers. It doesn't exist in older browsers, but we don't really care because VE doesn't support browsers that old for lots of other reasons anyway.
+
+There are two ways we could approach this. I'll ask Krinkle which one he thinks is best before we proceed.
+
+#1 is to migrate uses of ve.bind( this.foo, this ); to this.foo.bind( this ); across the code base, then deprecate and later remove ve.bind(). This would be pretty laborious.
+
+#2 is to change ve.bind() to a wrapper that uses native .bind(). This will change every single function binding in the entire codebase to use native bind instantaneously.
+
+My guess it's probably best to do #2 first, then #1 later, but I'd like Krinkle to weigh in on this.",1395166498,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to James Forrester from comment #1)
+> Tony, are you planning to take on this bug?
+
+I plan to. But is there anything like bind() is only present in modern browsers ? 
+will replacing, say 
+this.$element.on( 'keypress', $.proxy( this.keyup, this ) )
+with 
+this.$element.on( 'keypress', this.keyup.bind(this)) will do the trick ?",1395165708,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Tony, are you planning to take on this bug?",1395164794,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+VisualEditor: Clean up SurfaceObserver usage,"ve.ce.Surface contains a bunch of calls to stopTimerLoop() and startTimerLoop() that are unnecessary and seem to have been added based on the false assumption that JavaScript can be multithreaded.
+
+There are also duplicate calls to pollOnce that seem unneeded, or only exist to update state post-modification. We should audit these.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395097080,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2gy2ywwq2p5i63mtdvsz,task_description,open
+VisualEditor: Its possible to input a fraction value (with decimal point) in image size which results into showing wrong size in the review changes section,"Setting decimal value
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a new image
+3.Set the image size to a long value which becomes a number with scientific notation 
+4.Now start deleting the value from right to left
+5.Once you have deleted the scientific notation (e) and the number becomes a value with decimal point , click on ""Apply Changes""
+
+Observed Issue 1: it accepts that decimal value
+
+6.Click on Save Page and go to ""Review your Changes""
+
+Observed Issue 2: The size value showing in the review changes section are completely different that what was set in step 5
+
+See the screenshots attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=17marchff&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13038}",1395095100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5rr6tldo3g3davlgjzkz,task_description,resolved
+VisualEditor: Its possible to input a fraction value (with decimal point) in image size which results into showing wrong size in the review changes section,Verified the fix in production,1400012238,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5rr6tldo3g3davlgjzkz,task_subcomment,NA
+VisualEditor: Its possible to input a fraction value (with decimal point) in image size which results into showing wrong size in the review changes section,This doesn't happen anymore with the new MediaSizeWidget and the DimensionsWidget; they don't allow for decimal values at all.,1399571426,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-5rr6tldo3g3davlgjzkz,task_subcomment,NA
+VisualEditor: Its possible to input a fraction value (with decimal point) in image size which results into showing wrong size in the review changes section,"Created attachment 14843
+The discrepancy in review changes section
+
+**Attached**: {F13040}",1395095198,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5rr6tldo3g3davlgjzkz,task_subcomment,NA
+VisualEditor:  What you put into the template editor is not what it gives back (more Babel box bugs),"Intention:
+Edit a Babel box that I'd just created.
+
+Steps to Reproduce:
+1. Create a Babel box using the workaround described in bug 62740 {T64740}.
+
+2. Apply changes.
+
+3. Select the transclusion and click the puzzle icon to edit it again.
+
+4. It looks confusingly different.
+
+
+Expected Results:  
+If it can't add the function, then how is it able to edit it?  And if it can edit it, then why can't it add it normally?
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1395083820,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gpxl6tetek6gnjsolbm6,task_description,open
+VisualEditor:  What you put into the template editor is not what it gives back (more Babel box bugs),"Created attachment 14840
+Screenshot showing editing of Babel box
+
+**Attached**: {F13026}",1395083945,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gpxl6tetek6gnjsolbm6,task_subcomment,NA
+VisualEditor:  What you put into the template editor is not what it gives back (more Babel box bugs),"Created attachment 14839
+Screenshot showing creation of Babel box
+
+**Attached**: {F13025}",1395083916,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gpxl6tetek6gnjsolbm6,task_subcomment,NA
+VisualEditor:  Create a sensible system for adding Babel boxes (parser functions),"Intention:
+Add a Babel box
+
+Steps to Reproduce:
+1. Go to Insert > Template
+
+2. Type in #babel:en
+
+3. Click ""Add template"".
+
+4. Nothing happens.
+
+
+Expected Results:  
+Either it ought to Just Work™, or it ought to produce an error message about VisualEditor not supporting parser functions yet (see bug 50855).
+
+Reproducible: Always
+
+Workaround:  Go to complex transclusion mode; add ""Content""; paste in wikitext source code for the parser function.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49996",1395078720,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-d27naw46rmmwvpednony,task_description,open
+VisualEditor:  Create a sensible system for adding Babel boxes (parser functions),"Created attachment 14836
+Screenshot showing exactly what was in the template name field when it didn't work
+
+**Attached**: {F13013}",1395079025,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-d27naw46rmmwvpednony,task_subcomment,NA
+VisualEditor: Merge the media editing and gallery editing dialogs,Moved out of T40129's wishlist into its own bug.,1394835240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hkmxueiu32djdjwjf6qe,task_description,declined
+VisualEditor: Merge the media editing and gallery editing dialogs,">>! In T64677#2710576, @Tchanders wrote:
+> I suspect the real problem is that the media dialog is more mature, so a better solution in my opinion would be to work on improving the gallery dialog.
+
+Makes sense to me.",1519404558,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-hkmxueiu32djdjwjf6qe,task_subcomment,NA
+VisualEditor: Merge the media editing and gallery editing dialogs,"I'm not sure I agree with doing this, since media and galleries have such different functionalities. E.g. a media item is only chosen once, whereas galleries can be extended, pruned, rearranged, etc. The media display options are quite different from the gallery display options too, and a media item might not even be an image. I think a single dialog that incorporated all of this would lead to a confusing user experience, with too many alternative workflows and options being disabled according to whether whether media or gallery behaviour was required.
+
+I suspect the real problem is that the media dialog is more mature, so a better solution in my opinion would be to work on improving the gallery dialog.
+
+",1476304111,PHID-USER-abybinou47zwmsranndg,PHID-TASK-hkmxueiu32djdjwjf6qe,task_subcomment,NA
+VisualEditor: Be able to set a over-ride link target (link=…) in the media edit dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-co3ofwxr32imhzpdqgr6,task_description,open
+"VisualEditor: Centred images can appear in VE as overlapped by another image, then can't be selected","screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image 
+3.Insert another image just after it which is smaller than the previous one
+4.Now align the first one to the left
+5.Now align the second one to Centre 
+
+Observed Result:
+
+The smaller image overlaps with the previous bigger one in VE.If you save it and reopen the editor, you wont be able to see the image to select it.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Widthnullagainalways
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62850
+
+**Attached**: {F13301}",1394666940,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-36q4opdcfxqgzrfpkocm,task_description,resolved
+"VisualEditor: Centred images can appear in VE as overlapped by another image, then can't be selected",I can't reproduce this issue anymore. We must have accidentally fixed it.,1521586640,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-36q4opdcfxqgzrfpkocm,task_subcomment,NA
+"VisualEditor: Centred images can appear in VE as overlapped by another image, then can't be selected",See also {T104540}.,1465387417,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-36q4opdcfxqgzrfpkocm,task_subcomment,NA
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE","Steps to reproduce:
+
+1.Open a page in VE
+2.Edit the page
+3.Switch to Edit Source mode
+
+Observed Result:
+In the console : an error is appearing :""Uncaught TypeError:Cannot read property cleardiff of null"".
+However, it does not hamper the functionality of switching/saving the page
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394564520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jyohwwldty3v4wbuw5lo,task_description,resolved
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE",Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1395350548,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jyohwwldty3v4wbuw5lo,task_subcomment,NA
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE",Verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&veaction=edit,1394843693,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jyohwwldty3v4wbuw5lo,task_subcomment,NA
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE","Change 118331 merged by jenkins-bot:
+Fix JS error trying to access this.saveDialog from switch to source mode code path
+
+https://gerrit.wikimedia.org/r/118331",1394672171,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jyohwwldty3v4wbuw5lo,task_subcomment,NA
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE","Change 118331 had a related patch set uploaded by Catrope:
+Fix JS error trying to access this.saveDialog from switch to source mode code path
+
+https://gerrit.wikimedia.org/r/118331",1394651238,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jyohwwldty3v4wbuw5lo,task_subcomment,NA
+Possibly unintended splitting of a table into two tables using VE,"Isn't VisualEditor supposed to be able to edit only the content of the table cells but not change the table structure? If so, I believe this should not happen:
+https://pt.wikipedia.org/w/index.php?diff=38365876&uselang=en
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394487120,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-jq2yekad4c4aywwp7b2x,task_description,resolved
+Possibly unintended splitting of a table into two tables using VE,"Table editing has changed dramatically since this bug was filed (for example, the visual editor //can// now change the table structure), so I'm closing. Reopen if you can still reproduce.",1437696255,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-jq2yekad4c4aywwp7b2x,task_subcomment,NA
+Possibly unintended splitting of a table into two tables using VE,I'm setting this task's status to stalled as long as clear steps to reproduce are not known (plus this issue is now a year old).,1425508205,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jq2yekad4c4aywwp7b2x,task_subcomment,NA
+Possibly unintended splitting of a table into two tables using VE,"I'm not sure how the anonymous user managed to do that.
+
+Since the edit was marked with ""Tag: VisualEditor"", I assume the user didn't change to the wikitext editor after he started his changes (in that case it would be marked as ""VisualEditor: Switched"", I think).",1421679090,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-jq2yekad4c4aywwp7b2x,task_subcomment,NA
+Possibly unintended splitting of a table into two tables using VE,"Any specific steps that resulted in a broken table? And the table was edited **only** in VE? 
+
+",1421451161,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-jq2yekad4c4aywwp7b2x,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","It seems to be possible to get the Parsoid HTML/RDF output through the standard Mediawiki API, but I can't figure out how.
+
+For example, this fails:
+https://en.wikipedia.org/w/api.php?action=visualeditor&paction=parse&page=Main_Page&oldid=598252063
+
+An example would be really helpful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61017",1394363280,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_description,resolved
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","Change 166519 merged by jenkins-bot:
+Mark action=visualeditor as an internal API
+
+https://gerrit.wikimedia.org/r/166519",1413246504,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","Change 166519 had a related patch set uploaded by Jforrester:
+Mark action=visualeditor as an internal API
+
+https://gerrit.wikimedia.org/r/166519",1413246389,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","I took the upstream bug in MW core, might as well take this as well.",1409874589,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use",Have filed bug 62905 in MW's API to make this possible.,1395361895,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","I see some kind of contradiction in proposing an API on one side  action=visualeditor @https://en.wikipedia.org/w/api.php and on the other side telling ""this is a private API"".
+
+I fully understand that this is a work in progress, and thank you very much for you explanation Gabriel. But, IMO the current VE related API status is really puzzling for someone which is not embeded in the Parsoid/VE project.
+
+Why not simply remove this documentation (action=visualeditor) as long as this is not really working for everybody?
+
+NB: Regarding the Parsoid/API integration work itself, I think there is an other bug open somewhere about that.",1394531723,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","(In reply to James Forrester from comment #2)
+> Should this be the Parsoid bug for that, then?
+
+My understanding is that this bug is about the VE API. http://parsoid-lb.eqiad.wikimedia.org/ links to the documentation at https://www.mediawiki.org/wiki/Parsoid#The_Parsoid_web_API, which has at least one example. This bug can probably be closed, but good to wait for Emmanuel's input.",1394473837,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","(In reply to Gabriel Wicke from comment #1)
+> The VE interface is private and not intended as a public / stable Parsoid
+> API. It just proxies to http://parsoid-lb.eqiad.wikimedia.org/ and adds some
+> more VE-specific information that is not needed if all you are interested in
+> is the content. As it spins up an extra PHP worker it is also slower than
+> accessing the Parsoid API directly.
+> 
+> The Parsoid API will be integrated in a new REST content API in the longer
+> term. The URL will change at some point later this year, but the principle
+> will remain the same.
+
+Should this be the Parsoid bug for that, then?",1394471745,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","The VE interface is private and not intended as a public / stable Parsoid API. It just proxies to http://parsoid-lb.eqiad.wikimedia.org/ and adds some more VE-specific information that is not needed if all you are interested in is the content. As it spins up an extra PHP worker it is also slower than accessing the Parsoid API directly.
+
+The Parsoid API will be integrated in a new REST content API in the longer term. The URL will change at some point later this year, but the principle will remain the same.",1394465623,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+VisualEditor:  Advanced transclusion editor for complex templates eats parameters,"If you have a complex transclusion (e.g., a succession box), and you try to rearrange the order of the items, and if one or more of those items is a template that contains a parameter, then some or all of the parameter-containing templates will silently disappear.
+
+See https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_1#Add_content_and_other_transclusion_mysteries for complaints.
+
+
+Diffs of resulting problems:
+
+https://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=596891776&oldid=596891699
+
+https://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=597044161&oldid=596891923
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394238840,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-foq2smoax4kgl2mj4anq,task_description,open
+VisualEditor:  Advanced transclusion editor for complex templates eats parameters,"Tested it in test2. 
+
+- By rearranging templates via moving them in Transclusion box, I was not able to separate template parameters - e.g. to make {{s-bef|before = [[Leonardo Domenici]]}}  --> {{s-bef|before = }}.
+ - Also tried the exact steps on https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_1#Add_content_and_other_transclusion_mysteries:
+""Example: here all I did was use the ""up"" button four times: ""up"" the lowest ""content"", ""up"" the lowest s-aft, ""up"" the lowest ""content"" again, try to ""up"" the lowest s-aft again. Result when you want to save it: the s-aft has simply vanished :-)""
+
+It was non-reproducible  - either the issue is resolved or I am not inventive enough :(  I'd like someone else to take a look at the issue - hence I've assigned some priority to it.",1426618431,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-foq2smoax4kgl2mj4anq,task_subcomment,NA
+VisualEditor: Empty references created in wikitext editor should be allowed to edit in VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with wikitext editor
+2.Insert an empty reference for example: empty reference<ref />
+3.Save the page
+4.Now open the page with VE
+
+Observed Result:
+It does not let you edit the empty reference you just added and shows an error ""This reference is defined in a template or other generated block and for now can only be edited in source mode""
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Newpagereference?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12863}",1394220660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nhzlsr5aycf5vf4abhj6,task_description,open
+VisualEditor: Empty references created in wikitext editor should be allowed to edit in VE,"I just tried at http://en.wikipedia.beta.wmflabs.org/wiki/0.24595949980612886 and the reference can be edited now, but shows the ""disallowed"" cursor on hover.",1422564675,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nhzlsr5aycf5vf4abhj6,task_subcomment,NA
+"VisualEditor: Save dialog throws ""Uncaught TypeError: Cannot read get getModel of undefined"" (IE9)","Screenshot of bug.
+
+Encountered in IE9 using BrowserStack ""Windows 7/IE9"" using latest MediaWiki and VisualEditor master via a tunnel. Could either be a browser bug we have to work around, or something on our end applicable to other browsers as well.
+
+* Edit a simple document.
+* Add two characters at the start.
+* ""Save page"" enables itself.
+* Click it.
+
+Uncaught exception:
+
+> “Unable to get value of property ‘getModel’: object is null or undefined”.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13345}",1394128380,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vtqdjdocmtgvoothuoyh,task_description,resolved
+"VisualEditor: Save dialog throws ""Uncaught TypeError: Cannot read get getModel of undefined"" (IE9)",Works now.,1461148540,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vtqdjdocmtgvoothuoyh,task_subcomment,NA
+"VisualEditor: Save dialog throws ""Uncaught TypeError: Cannot read get getModel of undefined"" (IE9)","> I get bug 63039 first:
+Which is T65039 and has a patch for review.",1460637918,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vtqdjdocmtgvoothuoyh,task_subcomment,NA
+"VisualEditor: Save dialog throws ""Uncaught TypeError: Cannot read get getModel of undefined"" (IE9)","I'm unable to reproduce this bug because before it even gets anywhere, I get bug 63039 first:
+
+> ""SCRIPT70: Permission denied"", /Main_Page, line 1 character 1",1412209087,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vtqdjdocmtgvoothuoyh,task_subcomment,NA
+VisualEditor: Weird repetition when using the editor in IE9,"Screenshot of bug.
+
+Encountered in IE9 using BrowserStack ""Windows 7/IE9"" using latest MediaWiki and VisualEditor master via a tunnel. Could either be a browser bug we have to work around, or something on our end applicable to other browsers as well.
+
+
+* Load up the ""Worksheet"" page.
+* Trying to put the cursor in the first paragraph and add text.
+
+It repeats the first sentence many times and causes various weird scroll/focus events to occur all over the document.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13343}",1394128140,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n3l4te5qxvaeoc3fey5b,task_description,declined
+VisualEditor: Weird repetition when using the editor in IE9,IE9 support has been dropped: T162277,1491506596,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-n3l4te5qxvaeoc3fey5b,task_subcomment,NA
+VisualEditor: Weird repetition when using the editor in IE9,"Haven't yet narrowed down, vague subject for now.",1394128538,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n3l4te5qxvaeoc3fey5b,task_subcomment,NA
+VisualEditor:  Why doesn't the Insert menu in the main editor have the same order as the Insert menu in the Image caption editor?,"Open VisualEditor.  Click 'Insert'.  First item in the main Insert menu:  Reference.  
+
+Open (or insert) and image.  Under the Caption, click 'Insert'.  First item:  Language.
+
+Reference is still the most important item, and should be listed first.  (Should ""image"" even be listed at all?  It works, if you only go one deep, but...)
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1394058960,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-s24smc5kqzdyl5pvlpcz,task_description,resolved
+VisualEditor:  Why doesn't the Insert menu in the main editor have the same order as the Insert menu in the Image caption editor?,"Change 117101 merged by jenkins-bot:
+Make the order of insert tools consistent in dialogs
+
+https://gerrit.wikimedia.org/r/117101",1394060524,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-s24smc5kqzdyl5pvlpcz,task_subcomment,NA
+VisualEditor:  Why doesn't the Insert menu in the main editor have the same order as the Insert menu in the Image caption editor?,"Change 117101 had a related patch set uploaded by Catrope:
+Make the order of insert tools consistent in dialogs
+
+https://gerrit.wikimedia.org/r/117101",1394059854,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-s24smc5kqzdyl5pvlpcz,task_subcomment,NA
+VisualEditor:  Why doesn't the Insert menu in the main editor have the same order as the Insert menu in the Image caption editor?,"So in general, the menus are supposed to be different for exactly the reason you hinted at: there are things you can't do in an image caption or in a reference. That said, the order should probably be consistent. This is likely to just be an oversight (the lists are maintained completely separately, which is kind of horrible) rather than anything intentional, but I'll double-check with James to make sure.",1394059451,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-s24smc5kqzdyl5pvlpcz,task_subcomment,NA
+VisualEditor: Shortcut system should support shifted punctuation characters,"Right now there is no way to express Ctrl+? in the trigger system. Attempting to type that on my keyboard registers as Ctrl+Shift+/ , but that's only because my keyboard layout is such that ? is above /. There should be a way to express Ctrl+? independent of the keyboard layout.
+
+This may not be easy to do because Trevor tells me that charCode is less reliable than keyCode, so we may not be able to detect this correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394056560,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-y76rhjbfn2sjvcyboyko,task_description,open
+"VisualEditor: Allow enablement of VE on pages whose titles are matched by regexps, editable through an interface message","Pages like:
+* documentation - [[Template:Terminal/doc]]
+* Wikipedia namespace = [[Wikipedia:Manual of Style]]
+
+Note that on many wikis there are custom subpages (like /doc) or namespaces which visual editing should be configurable.
+I suggest MediaWiki interface - [[MediaWiki:Visualeditor-editable-pages]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393669740,PHID-USER-b27lopawgf2h6utuuqyi,PHID-TASK-wx2s3qbnx44xiegmal63,task_description,open
+"VisualEditor: ""TypeError: $domNode.closest(...).data(...) is undefined"" appears while dragging an image inside Media Settings and Reference dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open a reference dialog or Media Settings for an image
+3.Insert two images inside that dialog.
+4.Now drag one of them
+
+Observed Result:
+
+Observe that, the shadow of the image appears from the corner of CE instead of the dialog.Also an error appears after dragging the image shadow over itself:
+TypeError: $domNode.closest(...).data(...) is undefined
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=New_pageon%24&gettingStartedReturn=true&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13253}",1393553040,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-kg4z3siwsfs5p4zwouaz,task_description,open
+Slashes in titles should be escaped when generating links,"**Author:** `vigna`
+
+**Description:**
+Some Wikipedia pages contain slashes in their title, e.g., ""/b/"" or ""/dev/null"". Such slashes should be escaped to %2F when they are not meant to separate paths components, as per RFC 1738/3986. Instead, for instance,
+
+http://en.wikipedia.org/w/index.php?title=B/&redirect=no
+
+contains an A element
+
+<a href=""/wiki//b/"" title=""/b/"">/b/</a>
+
+that should written
+
+<a href=""/wiki/%2Fb%2F"" title=""/b/"">/b/</a>
+
+
+This causes 2 problems:
+
+1) The URL above does not conform to the RFCs. This is a minor issue but it might rise other problems in the future.
+
+2) If the slash is initial, the URI is not normalized as per RFC. E.g., in Java
+
+bsh % print(URI.create(""wiki//b/"").normalize());
+wiki/b/
+
+This might be a problem with crawlers, which usually normalize URLs to reduce the number of duplicates.
+
+
+
+Note that %2F-escaped slashes work perfectly, and 
+
+http://en.wikipedia.org/wiki/%2Fb%2F
+
+brings you exactly to /b/'s page. Bug 8254 seems to say the opposite, but it's a few years old.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1393411620,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-er23tg3bi4off4fieogn,task_description,open
+Slashes in titles should be escaped when generating links,"**vigna** wrote:
+
+What I mean is that the Wikipedia text contains links like [[/b/]]. That is, the user will input the title of a page. But then some code will turn this title into a link: it shouldn't be http://en.wikipedia.org/wiki//b/, but rather http://en.wikipedia.org/wiki/%2Fb%2F . 
+
+Maybe the page above wasn't a good example. Consider
+
+http://en.wikipedia.org/wiki/Cory_Doctorow
+
+The reference entry for /usr/bin/god in the ""Other"" section is
+
+* ''[[/usr/bin/god]]'' (novel; Tor Books)
+
+The link generated by the Wikimedia software (or whoever is in charge :) is
+
+<a href=""/wiki//usr/bin/god"" title=""/usr/bin/god"">/usr/bin/god</a>
+
+This should be
+
+<a href=""/wiki/%2Fusr%2Fbin%2Fgod"" title=""/usr/bin/god"">/usr/bin/god</a>",1393418640,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-er23tg3bi4off4fieogn,task_subcomment,NA
+Slashes in titles should be escaped when generating links,"Thanks for taking the time to report this!
+
+It's not entirely clear to me what ""should be escaped when generating links"" mean. The user (when using classic text wikipage editing) or VisualEditor (when using VE for wikipage editing) cannot knowwhich kind of slash is meant.
+
+Or did you mean ""when generating wiki page titles"" instead?",1393417411,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-er23tg3bi4off4fieogn,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"The button for the ""More settings"" menu has no tooltip.  Should it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393309920,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-255bhdoqq2fqddmttfct,task_description,resolved
+VisualEditor: Add a tooltip to the page menu button,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755283,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755266,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,Verified the fix in test2,1394229751,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,Verified the fix in betalabs,1393889599,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"Change 116145 merged by jenkins-bot:
+Add tooltip to page options menu widget in the toolbar
+
+https://gerrit.wikimedia.org/r/116145",1393637749,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"Change 116145 had a related patch set uploaded by Jforrester:
+Add tooltip to page options menu widget in the toolbar
+
+https://gerrit.wikimedia.org/r/116145",1393615663,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"Yes:  the three-bars icon, which is currently called ""More settings"" at mw:Help:VisualEditor/User_guide.",1393610658,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"Do you mean the page menu (Options, Page settings, Advanced settings, …)?",1393537115,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","Intention:
+Blank a page (prior to setting a redirect).
+
+Steps to Reproduce:
+1. Select all (Command-a).
+2. Press the delete key.
+3. Save > Review changes.
+
+Actual Results:  
+Categories, defaultsort keys, and page protection templates are not removed.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)&diff=914307&oldid=904077",1393268400,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jd374nh4jydelfvamhck,task_description,open
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)",https://en.wikipedia.org/w/index.php?action=edit&oldid=665564885 is the most interesting version of this that I've seen for a while.  It kept parts of a subst'd template.,1434928717,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","(In reply to James Forrester from comment #3)
+> On this one I'm minded to WONTFIX, but I could be argued around. What are
+> the reasons for letting people remove content they can't see with select-all?
+
+As WhatamIdoing says, redirecting, for example for merging. This may be achieved using some special scenario. (And hey, blanking must point at something special in any case.)
+
+Copying here the description from bug 67200 which was closed as dupe:
+
+Deleting the text from the article and converting it to a redirect page still leaves all the categories in it, as well as Other Stuff such as magic words and invisible templates.
+
+This is a regression in comparison to the source editor, where the editor could just delete everything and be sure that categories, magic words, invisible templates and everything else is gone.
+
+Just redirecting an article shouldn't necessarily remove everything, because it's actually possible that the editor wants to leave the article in a category. Some projects, including enwiki, have categories, templates etc. in redirect pages. But probably some kind of a warning should be shown.",1403885859,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)",*** Bug 67200 has been marked as a duplicate of this bug. ***,1403885598,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","I'm not sure that select-all is the right way to remove them, but there should be some way to remove them, and a way to find out that they are present.",1393274944,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","(In reply to Bartosz Dziewoński from comment #1)
+> All kinds of other things too, see also bug 52036 and bug 60830. I think we
+> need a tracking bug for this or a large WONTFIX.
+
+I've merged bug 52036 and bug 60830 into their respective causes (both of those are things we will fix with those corrections), and narrowed this to just be about meta-data – things that don't display because they never create any content.
+
+On this one I'm minded to WONTFIX, but I could be argued around. What are the reasons for letting people remove content they can't see with select-all?",1393271801,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","Perhaps we should have a special process for redirects that handles 100% blanking, or at least inquires or warns about it.  (You might want cats for redirects, but probably not a default sort key).",1393271800,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","All kinds of other things too, see also bug 52036 and bug 60830. I think we need a tracking bug for this or a large WONTFIX.",1393268518,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+VisualEditor: Adding gallery as Heading creates inconsistency between readmode and VE mode,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a heading
+3.Select the text of the heading and insert a gallery
+4.The gallery gets added as part of the heading
+5.Save the page and observe the page content in the readmode
+
+Observed Result:
+
+In readmode , the heading text and caption of the gallery gets repeated immediately following the heading section.Also gallery is not showing up as part of the heading where as in wikitext editor it is inside ==heading== and also in VE
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+https://test2.wikipedia.org/w/index.php?title=Totalnewheading
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13262}",1393026840,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-manrmfmqhbwpodlyqqk2,task_description,resolved
+VisualEditor:  Instapaper plug-in injects div tags into pages,"Instapaper is ""a simple tool for saving web pages to read later on your iPhone, iPad, Android, computer, or Kindle.""  It adds div tags to the top and bottom of pages edited in VisualEditor.  
+
+See https://en.wikipedia.org/w/index.php?title=Major_Arcana_%28album%29&diff=589184449&oldid=589116581 for an example.  It added this to the top and the bottom:
+
+<div id=""sendToInstapaperResults""></div>
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=Major_Arcana_%28album%29&diff=589184449&oldid=589116581",1393018260,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-y2vqmyz5nwnjkvcn4rft,task_description,resolved
+VisualEditor:  Instapaper plug-in injects div tags into pages,"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114022,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y2vqmyz5nwnjkvcn4rft,task_subcomment,NA
+VisualEditor:  Instapaper plug-in injects div tags into pages,"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113140,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y2vqmyz5nwnjkvcn4rft,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode","Pages in View mode contain a convenient link to the related ""Data item"" (in the sidebar, under Tools). However, in the classic edit mode such links disappears. It is a convenient link for editors, and there is no reason why it should disappear.
+
+PS: the link is kept in VisualEditor since the ""page"" actually doesn't change.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45687",1393014300,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_description,resolved
+"""Data item"" link in sidebar disappears in classic edit mode",Big Thank You!,1414582859,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode","Change 167233 merged by jenkins-bot:
+Always show link to wikibase item in toolbox
+
+https://gerrit.wikimedia.org/r/167233",1414582089,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode","Change 167233 had a related patch set uploaded by Hoo man:
+Always show link to wikibase item in toolbox
+
+https://gerrit.wikimedia.org/r/167233",1413566411,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode","(In reply to Lydia Pintscher from comment #1)
+> Hoo: Should this get the easy keyword?
+
+Don't think so... doesn't seem like the hook we currently use for this supports this :/",1395149218,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode",Hoo: Should this get the easy keyword?,1395063814,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"http://korma.wmflabs.org/browser/bugzilla_response_time.html should answer these questions:
+
+How long does it take to give a first response to reporters of Low-Immediate / trivial-blocker bugs? How long until acknowledged bugs are resolved? Are we using the importance parameters consistently? Are we improving?
+
+* Average time for an accepted bug report between bug creation date and PATCH_TO_REVIEW status being set
+* Average time for an accepted bug report between PATCH_TO_REVIEW status being set and RESOLVED FIXED status being set.
+* Average time for an accepted bug report between bug creation date and first comment by not the reporter her/himself.
+
+https://www.mediawiki.org/wiki/Community_metrics#Bugzilla_response_time
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392848400,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_description,resolved
+Key performance indicator: Bugzilla response time,"I'm marking this task as Resolved because @acs and @sduenas worked hard on it, and the only piece left was better descriptions. Now there is no point in working on them...
+
+People interested in Maniphest metrics can watch and contribute to {T1003}. It's a modest start.",1417699948,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,">>! In T63561#807103, @Nemo_bis wrote:
+>>>! In T63561#802548, @Jdforrester-WMF wrote:
+>> Should this be changed into a Phabricator-focussed metric?
+> 
+> Yes, but AFAIK pretty much everything is impossible for korma given phabricator has no APIs, see T28. Perhaps mark all issue tracker-related tasks in this component as stalled?
+
+Can you not use https://phabricator.wikimedia.org/conduit/ for API access, or am I missing something?
+
+",1417626891,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,">>! In T63561#802548, @Jdforrester-WMF wrote:
+> Should this be changed into a Phabricator-focussed metric?
+
+Yes, but AFAIK pretty much everything is impossible for korma given phabricator has no APIs, see T28. Perhaps mark all issue tracker-related tasks in this component as stalled?",1417613803,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,Should this be changed into a Phabricator-focussed metric?,1417557831,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #29)
+> What if you try without me explaining you how, so we test how usable is this?
+
+I like!
+
+My first guess: Click on a canvas and use Ctrl key && mouse scroll wheel. But the standard zoom behavior of browser takes over. That idea probably came from using PDF viewers too much.
+
+Second guess: I mark a timeframe by clicking the left mouse button, dragging it horizontally while keeping it clicked, like in an audio editor.
+
+Bingo.
+
+I also highly appreciate that the y axis zoom is adjusted automatically!
+And clicking for a bit longer on the canvas seems to reset the zoom.
+
+Big kudos!",1400069447,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #9)
+> Is there a way to zoom the x and/or y axis (also see bug 61810)?
+
+Now you can zoom. What is you try without me explaining you how, so we test how usable is this?  :)",1400014165,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"The graphs are now considered ready:
+
+http://korma.wmflabs.org/browser/bugzilla_response_time.html
+
+We are still missing better strings, but this is a task for me. I'm taking the bug. Help / patches welcome.
+
+https://www.mediawiki.org/wiki/Community_metrics#Global_Pending_List still mentions ""Zoom feature for graphs"" a a nice-to-have improvement. If this item is still open when we close this bug, we will open a new bug report for it.",1395856237,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"This is our first approach to the zoom feature. There are some bugs to fix, though. 
+
+http://korma.wmflabs.org/browser/zoom_test.html",1395253199,PHID-USER-pgf5ibzmrl3xdc6hrj63,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Santi, only fyi: on the topic of removing tracking bugs, there is bug 2007, where all of them are identified.",1394572873,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Santi, thank you! The ""Total"" line is already useful now. I hope the fact of scanning only key Wikimedia projects will reduce the very high peaks, making the rest more readable.
+
+One option to make the Total line more visible could also be to make it thicker than the rest (just in case this is easier than changing the color).
+
+Andre, we agreed to Bitergia that they would focus on the graphs and we will focus on the content. Most of it can be ""edited"" indirectly via pull requests at https://github.com/Bitergia/mediawiki-dashboard/blob/master/browser/bugzilla_response_time.html",1394385156,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Looks good to me; thanks!
+
+(In reply to Santiago Dueñas from comment #21)
+> I've also include some help messages to clarify what the charts mean. Please
+> have a look to the message and let me know whether you understand them or
+> not, or if you want to change some terms, for instance, tickets to
+> bugs/reports, etc.
+
+* Typo: ""Unnatended Tickets""
+* Typo: ""had no actions by ohters than the reporter.""
+* Clicking on the explanation button (qm_15.png icon; ""?"" in a square) in the
+  four last of the six graphs scrolls up to the top of the page in FF27.
+* Unattended vs uncommented: I'd still love to see an explanation of the
+  difference to make sure that everybody understands, maybe in the header in 
+  brackets, like ""Unattended tickets (no activity by anybody else than 
+  reporter)"" and ""Uncommented tickets"" (no comments by anybody else than
+  reporter)"" or so?
+
+> I still have to add the number of bugs in the info boxes and filter those 
+> components that are not key projects.
+
+I think I'll reevaluate after we have this functionality in place (plus zooming, maybe).",1394369963,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #22)
+> Remaining tasks:
+> 
+> (In reply to Quim Gil from comment #19)
+> > * the number of bugs will be also displayed in the dialog with data.
+> > 
+> > Then the canonical list of products / reports that Andre just posted must be
+> > implemented.
+> 
+> We also agreed to add a black line t each graph showing the absolute median,
+> regardless of severity/priority, excluding ""Lowest"" as the graphs do now.
+
+Added but I still have to check how to change the colors of the charts.
+
+> 
+> We left this for later:
+> 
+> > Also, Andre was asking about the possibility to zoom graphs to visualize
+> > only a certain period. I *believe* I have seen this functionality in
+> > VizGrimoire but I'm not sure. In any case, it is something that we would
+> > consider only when we have the points above solve, if we still need it.",1394367598,PHID-USER-pgf5ibzmrl3xdc6hrj63,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Remaining tasks:
+
+(In reply to Quim Gil from comment #19)
+> * the number of bugs will be also displayed in the dialog with data.
+> 
+> Then the canonical list of products / reports that Andre just posted must be
+> implemented.
+
+We also agreed to add a black line t each graph showing the absolute median, regardless of severity/priority, excluding ""Lowest"" as the graphs do now.
+
+We left this for later:
+
+> Also, Andre was asking about the possibility to zoom graphs to visualize
+> only a certain period. I *believe* I have seen this functionality in
+> VizGrimoire but I'm not sure. In any case, it is something that we would
+> consider only when we have the points above solve, if we still need it.",1394063058,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #20)
+> Santi, yesterday Andre and me agreed that the information provided by the
+> ""Time to close"" graphs isn't very useful to us. Not only the very high peaks
+> make the rest impossible to analyze. The main problem is that those reports
+> don't tell us much about the trends, what should we do better, what is the
+> call to action.
+> 
+
+The other day Jesus and I were discussing about it and we find that these charts are not useful if we do not include bugs that are still opened, unattended or uncommented. Tomorrow we can talk about it during the confcall.
+
+> The graphs about the age of reports open without action do show trends and
+> where should we improve. In fact Andre is missing already the ones based on
+> priority. 
+> 
+> For all these reasons we propose to have these graphs, in this order:
+> 
+> Age of reports without any action by priority & severity
+> 
+> Age of reports without any comment by priority & severity
+> 
+> Age of reports unresolved by priority & severity
+> 
+> 
+
+Added.
+
+I've also include some help messages to clarify what the charts mean. Please have a look to the message and let me know whether you understand them or not, or if you want to change some terms, for instance, tickets to bugs/reports, etc.
+
+I still have to add the number of bugs in the info boxes and filter those components that are not key projects.
+
+> If you still think it makes sense to have graphs of the age of
+> closed/actioned/commented reports let's discuss, but after we leave this KPI
+> ready for this iteration. It's already March and there is still a lot to do.
+> Thank you!
+
+Ok!
+
+BTW, sorry with the delay with this. To get the ""age"" data from actions and comments was tricker than I thought.",1393990384,PHID-USER-pgf5ibzmrl3xdc6hrj63,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Santi, yesterday Andre and me agreed that the information provided by the ""Time to close"" graphs isn't very useful to us. Not only the very high peaks make the rest impossible to analyze. The main problem is that those reports don't tell us much about the trends, what should we do better, what is the call to action.
+
+The graphs about the age of reports open without action do show trends and where should we improve. In fact Andre is missing already the ones based on priority. 
+
+For all these reasons we propose to have these graphs, in this order:
+
+Age of reports without any action by priority & severity
+
+Age of reports without any comment by priority & severity
+
+Age of reports unresolved by priority & severity
+
+
+If you still think it makes sense to have graphs of the age of closed/actioned/commented reports let's discuss, but after we leave this KPI ready for this iteration. It's already March and there is still a lot to do. Thank you!",1393957111,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"After a conversation with Santi, we agreed on these changes:
+
+* focus on severity, removing all the graphs about priority and keeping the page sane; the former is more objective and stable, the latter is more subjective and changeable
+
+* Santi will try to draw the graphs calculating the severity of the reports at a given time; it seems to be easy but we'll see
+
+* the ""median age of open reports"" graphs will go at the beginning: reports without any action, reports without any comment, reports unresolved
+
+* the ""media age of reports acted upon"" will follow with a clear explanation: median age of reports when they get a first action, when they get a first comment, when they get a resolution
+
+* the number of bugs will be also displayed in the dialog with data.
+
+Then the canonical list of products / reports that Andre just posted must be implemented.
+
+Then we will see whether we still get those high peaks converting the rest in planes or not.
+
+Also, Andre was asking about the possibility to zoom graphs to visualize only a certain period. I *believe* I have seen this functionality in VizGrimoire but I'm not sure. In any case, it is something that we would consider only when we have the points above solve, if we still need it.",1393521221,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Santiago Dueñas from comment #14)
+> > > Should I make [[wikitech:Key_Wikimedia_software_projects]] a table and add
+> > > the corresponding Bugzilla product/component in the second column? 
+> 
+> A table sounds good. They're easy to parse and edit. But if I can suggest
+> something, I prefer to have product/component in separated columns
+
+Done: https://wikitech.wikimedia.org/w/index.php?title=Key_Wikimedia_software_projects&diff=101721&oldid=90993
+
+I hope I'll remember to update when I change Bugzilla's taxonomy. :)
+
+(And as a side-effect of (re-)investigating Bugzilla taxomony of Fundraising I found & filed bug 62002.)",1393521021,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Santiago Dueñas from comment #16)
+> I've added some new charts that try to show this.
+
+Thanks! They feel more helpful than the ""Time to close by..."" charts.
+
+> These charts have some problems:
+> 
+> - A peak that goes down doesn't implies you are closing the oldest bugs. It
+> can means that there are more bugs that were open recently, decreasing the
+> median. You can see this behaviour in Feb 2011. The median of Unprioritized
+> bugs is 530 days because there's only one bug that were opened 530 days ago.
+> The next month, the median goes down to 282 days because another bug was
+> opened in Mar 2011 and at the end of that month none of them were closed.
+
+Probably overhead and not a good idea, but could the overlay also display on how many items the calculated value is based on?
+
+> - Take into account that we are using the current priority of a bug. I think
+> that for these kind of charts, it makes more sense to take the priority of
+> the bug at that time, but it raises another problem: changes in lines might
+> be produced by changes in the priority. If you change the priority of a bug,
+> the old priority line will decrease while the new one will increase.
+
+Yeah, that's what I meant in comment 10 - but let's revisit the ""when to query the priority/severity value of a report"" aspect later.",1393515355,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"> (In reply to Santiago Dueñas from comment #4)
+> > In this case, the peak is from bug 27320.
+> 
+> > It was submitted on Feb 2011 (that's why it is shown at that point in the
+> > chart) but its first action was made two years later (April 2013). Its
+> > current priority is Immediate.
+> 
+> I think we have a problem of perspective. Your perspective seems to be
+> data-centric: ""how old were the bugs created at this point of time when they
+> received their first action?"" We actually care about our own perspective as
+> bugtriagers (yes, we are so self-centered people)  :) : ""how old are today
+> the open bugs that haven't received any action yet""? And last month? And a
+> year ago?
+> 
+> We want to see whether we are processing those bugs faster or slower than
+> before, whether we succeed addressing more important bugs faster or not. In
+> this sense, I wouldn't expect high peaks emerging, since the highest
+> increase from month to month can only be 31 days (unless you reopen hundreds
+> of very old bugs, an unlikely scenario that would reflect a legitimate
+> higher peak).
+> 
+> Let's agree on these points before tying to solve anything else, please.
+
+I've added some new charts that try to show this.
+
+These new ones are in top of the page and are ""Time opened by Priority (median)/(average)"". Former ""Time opened"" charts are now ""Time to close by Priodity (median)/(average). If you go down, you will see same charts but by Severity.
+
+Let's focus on ""Time opened by Priority (median)"". It shows how old your opened bugs were at a certain point in time, in median.
+
+If you select the first point with data, Aug 2004, it means that those bugs that remained open at the end of August were submitted (opened) in median around 15 days ago for most of the priorities. If you go to the next point, Sep 2004, it means the bugs that remain open (those from August that are not closed yet and those from September) were opened X days ago by priority, an so on.
+
+These charts have some problems:
+
+- A peak that goes down doesn't implies you are closing the oldest bugs. It can means that there are more bugs that were open recently, decreasing the median. You can see this behaviour in Feb 2011. The median of Unprioritized bugs is 530 days because there's only one bug that were opened 530 days ago. The next month, the median goes down to 282 days because another bug was opened in Mar 2011 and at the end of that month none of them were closed.
+
+- High lines can hide or shadow your work on new bugs. If you are closing new bugs very fast and you also have old opened bugs, you won't see any change in the lines.
+
+- Take into account that we are using the current priority of a bug. I think that for these kind of charts, it makes more sense to take the priority of the bug at that time, but it raises another problem: changes in lines might be produced by changes in the priority. If you change the priority of a bug, the old priority line will decrease while the new one will increase.
+
+One possible solution to these problems is combine these with historgrams or distribution charts.",1393428864,PHID-USER-pgf5ibzmrl3xdc6hrj63,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #12)
+> (In reply to Andre Klapper from comment #9)
+> > For my better understanding (and maybe others who might have the same
+> > problem):
+> > ""Time to first action by Priority"" - How is an ""action"" defined?
+> 
+> It means that someone (else, not the reporter) has changed priority,
+> severity, etc. That the bug has some history of changes, although afaik a
+> first comment is not counted (Santi must confirm). See Bug 13162, which tops
+> the list, it hasn't seen any change since it was submitted in 2008.
+> 
+> (It belongs to the MultiBoilerplate extension which afaik is not part of the
+> Key Wikimedia projects, a way to fine tune the list of products/components
+> we scan is to remove those that show up in the top results.)
+> 
+
+Action means changes + comments done by someone, but not by the reporter. In this context, ""Time to first action"" means how long it took that someone (not the submitter or reporter) for the first time, made a change on any the bug's parameters or posted a first comment. 
+
+This is the definition that Alvaro gime me but we can change it to ""Time to first change"", if you prefer.
+
+> > Is ""Time to
+> > first comment"" a subset, or disjunct?
+
+""Time to first comment"" is a subset of ""Time to first action"".
+
+> > So: Could the framework query changes to the ""Priority"" value of one report
+> > (via the ""bugs_activity"" database table in Bugzilla) and could one report be
+> > broken into/represented in several lines, each line showing for how long the
+> > report had that specific priority set?  I think this would make the lines
+> > more meaningful. (Same might apply to Severity).
+> 
+> Following on Comment 7, this would be translated as
+> 
+> ""How old are today the open bugs that haven't received any action yet,
+> organized by their priority/severity today""? And last month (based on the
+> priority/severity they had last month)? And a year ago (based on the
+> priority/severity they had last year)?
+> 
+> As said, if Santi sees a quick way to fix this let's do it. Otherwise let's
+> open an enhancement request for the next iteration.
+>
+
+Definitely. I can try something but I prefer to close the definition and meaning of the current charts before moving to new ones.",1393346880,PHID-USER-pgf5ibzmrl3xdc6hrj63,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #13)
+> (In reply to Andre Klapper from comment #11)
+> > Should I make [[wikitech:Key_Wikimedia_software_projects]] a table and add
+> > the corresponding Bugzilla product/component in the second column? 
+> > Or what's the prefered format to parse it in a machine-readable way? :-/
+> 
+> Santi: Could you answer this please?
+
+A table sounds good. They're easy to parse and edit. But if I can suggest something, I prefer to have product/component in separated columns, in order to pass them as parameters to our tool.",1393345013,PHID-USER-pgf5ibzmrl3xdc6hrj63,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #11)
+> Should I make [[wikitech:Key_Wikimedia_software_projects]] a table and add
+> the corresponding Bugzilla product/component in the second column? 
+> Or what's the prefered format to parse it in a machine-readable way? :-/
+
+Santi: Could you answer this please?",1393344862,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #9)
+> For my better understanding (and maybe others who might have the same
+> problem):
+> ""Time to first action by Priority"" - How is an ""action"" defined?
+
+It means that someone (else, not the reporter) has changed priority, severity, etc. That the bug has some history of changes, although afaik a first comment is not counted (Santi must confirm). See Bug 13162, which tops the list, it hasn't seen any change since it was submitted in 2008.
+
+(It belongs to the MultiBoilerplate extension which afaik is not part of the Key Wikimedia projects, a way to fine tune the list of products/components we scan is to remove those that show up in the top results.)
+
+> Is ""Time to
+> first comment"" a subset, or disjunct? Would changing the status from
+> REOPENED to NEW count as an action already?
+
+A bug REOPENED has been RESOLVED before, therefore it was acted upon already.
+
+(In reply to Andre Klapper from comment #10)
+> If I interpret comment 4 directly, one bug report remains in one line
+> (color) in the current model, based on gathering its *current* priority
+> value?
+
+Yes, this is not optimal but, unless it is easy to fix, I would leave it as such for the current iteration. We want to complete this KPI (well, the 5 KPIs) in this quarter, and Marc is already around the corner.
+ 
+> So: Could the framework query changes to the ""Priority"" value of one report
+> (via the ""bugs_activity"" database table in Bugzilla) and could one report be
+> broken into/represented in several lines, each line showing for how long the
+> report had that specific priority set?  I think this would make the lines
+> more meaningful. (Same might apply to Severity).
+
+Following on Comment 7, this would be translated as
+
+""How old are today the open bugs that haven't received any action yet, organized by their priority/severity today""? And last month (based on the priority/severity they had last month)? And a year ago (based on the priority/severity they had last year)?
+
+As said, if Santi sees a quick way to fix this let's do it. Otherwise let's open an enhancement request for the next iteration.
+
+I bet the current way of counting is still useful: for instance, if many urgent bugs were unnoticed for a long time, this will affect the time to address urgent issues, and it will show that we are slow addressing issues that were potentially urgent before we looked at them.
+
+I'm leaving the rest to Santi, but let's not deviate on the current focus es defined in Comment 7. We need to deliver a good iteration soon, and we have still many fonts open here.",1393256563,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #8)
+> > Last list I made was bug 54469 comment 6.
+> 
+> Interesting, but... you could have updated
+> [[wikitech:Key_Wikimedia_software_projects]] instead, which is the canonical
+> place to track changes to the key Wikimedia projects.
+
+Uhm. I cannot remember exactly, but I guess I was worried about the format I should use but did not ask explicitly. :(
+Should I make [[wikitech:Key_Wikimedia_software_projects]] a table and add the corresponding Bugzilla product/component in the second column? 
+Or what's the prefered format to parse it in a machine-readable way? :-/",1393194334,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Concentrating on ""Time to ... by Priority/Severity"" in this comment. Need to understand better, hence dropping some late night beer comments + thoughts.
+
+== Bug report priority changes vs. data gathering/representation in graph
+
+""Time to fix (TTF)""-related expectations per priority are covered in http://www.mediawiki.org/wiki/Bugzilla/Fields#Priority - an ""Immediate priority"" report should have a shorter TTF median than a ""Low prio"" report.
+
+In my opinion, TTF entirely depends to the moment a report receives priority triaging - either an initial triage or a retriage. Retriage means that Priority (and less often Severity, though from default ""Normal"" to ""Enhancement"" might be the one big exception here) of a report can change.
+
+If I interpret comment 4 directly, one bug report remains in one line (color) in the current model, based on gathering its *current* priority value?
+
+An open report that was low priority for three years and then suddenly became highest priority (e.g. due to other infrastructure changes creating the side effect that the bug is way more visible) and two weeks later closed as RESOLVED FIXED with priority still set to ""highest"" should probably not be shown as ""highest priority bug that took three years and two weeks to get closed"" as it's misleading.
+
+So: Could the framework query changes to the ""Priority"" value of one report (via the ""bugs_activity"" database table in Bugzilla) and could one report be broken into/represented in several lines, each line showing for how long the report had that specific priority set?  I think this would make the lines more meaningful. (Same might apply to Severity).
+
+
+== (Neglectable?) data artefacts on bug report metadata
+
+Can I assume that *all* bug reports are used as data source, hence also all resolutions (including WONTFIX, INVALID)?
+This might be a rather neglectable artefact, but correcting report metadata (priority, component, etc) after resolving a report (e.g. as WONTFIX, INVALID etc) often does not happen: 
+""Of course, the developer could change the issue category after resolution - but this happens rarely. In many cases there exists no real motivation to change the issue category once the cause for a problem is found and fixed."" (Herzig, Just, and Zeller: ""It's not a bug, it's a feature: how misclassification impacts bug prediction"", 2013, page 396, at http://www.st.cs.uni-saarland.de/softevo/bugclassify/paper/icse2013-bugclassify.pdf when the server is not down.)
+
+
+== Time to change ""Unprioritized"" to different priority (likely ignorable)
+
+As the default priority of a report is always ""Unprioritized"", I wonder whether median time between creation of a bug report and changing the priority from ""Unprioritized"" to a different value would be any helpful. 
+I am not convinced myself though: This is likely covered by ""Time to first action by Priority"" which might be enough for us.
+Anyway, just in case, two potentially problematic aspects for data gathering:
+* Not all teams use Priority in Bugzilla. Some use Mingle etc. instead.
+* Some tickets get closed so quickly that they remain ""Unprioritized"".",1393193797,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"For my better understanding (and maybe others who might have the same problem):
+""Time to first action by Priority"" - How is an ""action"" defined? Is ""Time to first comment"" a subset, or disjunct? Would changing the status from REOPENED to NEW count as an action already?
+
+Smaller issue in all graphs but only on this page:  After ""Feb 2013"", the month name header in the overlay popup becomes ""undefined"" (instead of ""Mar 2013"" etc).
+
+> The main problem here is with those big peaks in median charts. The 
+> useful data is lost at the bottom of the chart and you can only see
+> flat lines. We have to think about how to manage these cases.
+
+Does the rendering allow a cut-off parameter, e.g. ""only render lowest 40% of y axis""? Could images have double the height? Is there a way to zoom the x and/or y axis (also see bug 61810)?
+Not convinced by these ideas, but still some thoughts.",1393183040,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #2)
+> (In reply to Quim Gil from comment #1)
+> > * We need to scan only the Bugzilla products and components corresponding to
+> > https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects . Andre,
+> > did you have a list somewhere mapping these?
+> 
+> Last list I made was bug 54469 comment 6.
+
+Interesting, but... you could have updated [[wikitech:Key_Wikimedia_software_projects]] instead, which is the canonical place to track changes to the key Wikimedia projects.
+
+Maybe we can simplify things a bit? (but still document them in the wiki page)
+
+Entire products:
+
+Analytics
+Commons App
+Cortado (???)
+Datasets
+MediaWiki
+MediaWiki‑Vagrant
+MobileFrontend
+OOjs
+OOjs UI
+openZIM
+Parsoid
+Pywikibot
+QRpedia
+Security (can we extract anything from here anyway?)
+Tools (???)
+VisualEditor
+Wiki Loves Monuments
+Wikimedia
+Wikimedia Labs
+Wikipedia App 
+
+Then someone should map the components under ""MediaWiki extensions"" with [[wikitech:Key_Wikimedia_software_projects]]. Maybe it is easier to have the full list of components under ""MediaWiki extensions"" in Bugzilla and then remove those extensions not deployed here. It's not a big deal if there is a bit of mismatch. We can always fine tune.
+
+Andre, can you help Santi with this?",1393120176,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Let's focus first on these graphs:
+
+(In reply to Santiago Dueñas from comment #5)
+> now we show ""Time opened"" by median and average.
+
+There is still something odd here. See for instance ""Time opened by Priority (average)""
+
+In August 2004, apparently one month after opening the Bugzilla instance, we have about Low and Lowest bugs with a median of 1000 days. How can this be? I expect a graph that says that after 30 days of Bugzilla a bug can be 30 days old at most.
+
+
+> The main problem here is with those big peaks in median charts.
+
+Before trying to address the visualization problems of those high peaks, I still must understand the algorithm that generates them. You say...  
+
+(In reply to Santiago Dueñas from comment #4)
+> In this case, the peak is from bug 27320.
+
+> It was submitted on Feb 2011 (that's why it is shown at that point in the
+> chart) but its first action was made two years later (April 2013). Its
+> current priority is Immediate.
+
+I think we have a problem of perspective. Your perspective seems to be data-centric: ""how old were the bugs created at this point of time when they received their first action?"" We actually care about our own perspective as bugtriagers (yes, we are so self-centered people)  :) : ""how old are today the open bugs that haven't received any action yet""? And last month? And a year ago?
+
+We want to see whether we are processing those bugs faster or slower than before, whether we succeed addressing more important bugs faster or not. In this sense, I wouldn't expect high peaks emerging, since the highest increase from month to month can only be 31 days (unless you reopen hundreds of very old bugs, an unlikely scenario that would reflect a legitimate higher peak).
+
+Let's agree on these points before tying to solve anything else, please.",1393019867,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Santiago Dueñas from comment #5)
+> The main problem here is with those big peaks in median charts. The useful
+> data is lost at the bottom of the chart and you can only see flat lines. We
+> have to think about how to manage these cases.
+
+Scale in log base 10?",1393009986,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #3)
+> The main problem I have with these graphs is that they show plenty of lines
+> going up and down, but no clear message. 
+> 
+> When answering ""Time to closed by Priority"", I think we should actually
+> answer ""Median time of open bugs"". This would provide more stable lines
+> without huge jumps between months, where we can see
+> 
+> * whether we are increasing or decreasing the median time for open bugs
+> * the differences of time response for higher and lower priority bugs
+> 
+> I think this change will make all the graphs a lot more useful.
+> 
+> Then we can organize better those six graphs:
+> 
+> Time to closed by Priority
+> Time to closed by Severity
+> 
+> Then time to first action, then time to first comment.
+> 
+
+I think you are right.
+
+Please have a look at the new charts that I've just uploaded. Instead of ""Time to close"" now we show ""Time opened"" by median and average. I've also included the median for first action and first comment.
+
+The main problem here is with those big peaks in median charts. The useful data is lost at the bottom of the chart and you can only see flat lines. We have to think about how to manage these cases.
+
+Average charts are still there for comparing with the median ones. We can remove them whenever you want.
+
+> It would be good to have also a line for the median of the total of bugs,
+> regardless of priority/severity, to see how good are we doing overall.
+> 
+
+Good point. I'm going to add it.
+
+> One more thing, since we are considering ""Lowest"" almost as an equivalent of
+> WONTFIX-for-maintainers (we assign Lowest priority when nobody is planning
+> to act on a report), we might need to consider them as resolved-wontfix if
+> they distort too much the results. We will see.
+
+I had it into account for top issues and ""Time opened"" so these data is already filtered.",1393009656,PHID-USER-pgf5ibzmrl3xdc6hrj63,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #2)
+> (In reply to Quim Gil from comment #1)
+> > * We need to scan only the Bugzilla products and components corresponding to
+> > https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects . Andre,
+> > did you have a list somewhere mapping these?
+> 
+> Last list I made was bug 54469 comment 6.
+> 
+> > Andre, you are the main stakeholder of this page.
+> 
+> Noted.
+> 
+> One data issue in the graphs:
+> http://korma.wmflabs.org/browser/bugzilla_response_time.html shows
+> ""avg_fa_Immediate:788.7567"" for Feb 2011. That is impossible as the
+> ""Immediate"" priority was only introduced on Nov 30, 2012:
+> http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064746.html
+> I have not investigated other peaks yet (also because I don't have data
+> handy when which priority and severity was introduced in this Bugzilla).
+
+It is shown that way because we take the current/final priority of a bug to classify them into group due to the priority can change during the life of bug.
+
+In this case, the peak is from bug 27320.
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=27320.
+
+It was submitted on Feb 2011 (that's why it is shown at that point in the chart) but its first action was made two years later (April 2013). Its current priority is Immediate.
+
+Another possibility is to select the initial state but most of the bugs (aroung 90%) fall in Unprioritize or Normal priorities. Selecting intermediate states doesn't make any sense because we would need infinite charts to show the data.",1393008607,PHID-USER-pgf5ibzmrl3xdc6hrj63,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"The main problem I have with these graphs is that they show plenty of lines going up and down, but no clear message. 
+
+When answering ""Time to closed by Priority"", I think we should actually answer ""Median time of open bugs"". This would provide more stable lines without huge jumps between months, where we can see
+
+* whether we are increasing or decreasing the median time for open bugs
+* the differences of time response for higher and lower priority bugs
+
+I think this change will make all the graphs a lot more useful.
+
+Then we can organize better those six graphs:
+
+Time to closed by Priority
+Time to closed by Severity
+
+Then time to first action, then time to first comment.
+
+It would be good to have also a line for the median of the total of bugs, regardless of priority/severity, to see how good are we doing overall.
+
+One more thing, since we are considering ""Lowest"" almost as an equivalent of WONTFIX-for-maintainers (we assign Lowest priority when nobody is planning to act on a report), we might need to consider them as resolved-wontfix if they distort too much the results. We will see.",1392924663,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #1)
+> * We need to scan only the Bugzilla products and components corresponding to
+> https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects . Andre,
+> did you have a list somewhere mapping these?
+
+Last list I made was bug 54469 comment 6.
+
+> Andre, you are the main stakeholder of this page.
+
+Noted.
+
+One data issue in the graphs:
+http://korma.wmflabs.org/browser/bugzilla_response_time.html shows ""avg_fa_Immediate:788.7567"" for Feb 2011. That is impossible as the ""Immediate"" priority was only introduced on Nov 30, 2012: http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064746.html
+I have not investigated other peaks yet (also because I don't have data handy when which priority and severity was introduced in this Bugzilla).",1392905142,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"The main problems discussed so far:
+
+* We need to scan only the Bugzilla products and components corresponding to https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects . Andre, did you have a list somewhere mapping these?
+
+* The graphs miss a legend describing what is being calculated. Documentation in the wiki page linked above would be useful too.
+
+* The data calculated is the average, but the median is preferred.
+
+* The graphs start in Jan 2002 but there is no data until Jul 2004.
+
+* Proper labels.
+
+I still must put more time to dive into these graphs and see whether they provide the answers we are looking for, or they could be improved. Andre, you are the main stakeholder of this page.",1392849320,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Intention:
+Change an ISBN.
+
+Steps to Reproduce:
+1. Open a page with a pre-existing ISBN number (using the magic word).
+
+2. Click in the link and open the link inspector.
+
+3. Correct the numbers in the ISBN.
+
+4. Close the link inspector.
+
+
+
+Actual Results:  
+The link label does not change.  This is not surprising, given VisualEditor's approach to links, but it is sometimes unfortunate; see https://fr.wikipedia.org/w/index.php?title=Massimo_Introvigne&diff=100272017&oldid=94374615
+
+However, the link itself does not change, and if you have done nothing else, it is not possible to save the page, because you have supposedly made no changes.
+
+Expected Results:  
+Ideal behavior:
+
+Changing ""ISBN 1234567890"" to ""ISBN 1234567891"" simply updates the plain wikitext magic word.
+
+Possibly acceptable behavior:
+
+Changing ""ISBN 1234567890"" to ""ISBN 1234567891"" updates the link to [[Special:BookSources/1234567891|ISBN 1234567891]].
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52204",1392846900,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-mnf2geb333qld3ax5dkc,task_description,resolved
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Change 233669 merged by jenkins-bot:
+Specialized inspector for ISBN magic links
+
+[[https://gerrit.wikimedia.org/r/233669]]",1441132464,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Change 233669 had a related patch set uploaded (by Cscott):
+Specialized inspector for ISBN magic links
+
+[[https://gerrit.wikimedia.org/r/233669]]
+",1440714140,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Change 233669 had a related patch set uploaded (by Cscott):
+WIP: Specialized inspector for ISBN magic links
+
+[[https://gerrit.wikimedia.org/r/233669]]
+",1440533743,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","@krenair it's mostly orthogonal to this bug, but we just changed the `rel` type of ISBN links to `mw:WikiLink`.  I agree that it is more consistent that way.
+
+The VE UX issue still exists: VE should detect edits to ISBN/RFC/PMID links and somehow keep the text and the link in sync.  I don't know the best way to do that within the VE codebase.",1440082534,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links",">>! In T63558#1365108, @Elitre wrote:
+> @ssastry, are the problems described in [[ https://phabricator.wikimedia.org/T63558#677094 | this comment]] also possibly due to Parsoid? Thank you!
+
+Looking at [[Special:BookSources/9782981011206|ISBN 978-2-9810112-1-]]<nowiki/>3 .. that looks like VE issues to me. The ""3"" is not part of the link text so, Parsoid is forced to add a nowiki to preserve HTML semantics. As for editing link text not chaning the underlying link, that is also a VE UX issue.",1434380446,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","@ssastry, are the problems described in [[ https://phabricator.wikimedia.org/T63558#677094 | this comment]] also possibly due to Parsoid? Thank you!",1434365599,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","The Parsoid output does not look quite right to me:
+```<a href=""./Special:BookSources/0345318641"" rel=""mw:ExtLink"" data-parsoid='{""stx"":""magiclink"",""dsr"":[16,34,0,0]}'>ISBN 0-345-31864-1</a>```
+ExtLink? That href is for a WikiLink...",1429356029,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","The Parsoid output does not look quite right here:
+```<a href=""./Special:BookSources/0345318641"" rel=""mw:ExtLink"" data-parsoid='{""stx"":""magiclink"",""dsr"":[16,34,0,0]}'>ISBN 0-345-31864-1</a>```
+ExtLink? That href is for a WikiLink...",1429356018,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Other recent examples of ISBN problems caused by VE (awful syntax, link incoherent with displayed ISBN, nowiki added) :
+https://fr.wikipedia.org/w/index.php?title=Bassin_s%C3%A9dimentaire&diff=prev&oldid=104307942
+https://fr.wikipedia.org/w/index.php?title=Louis-Jos%C3%A9_Houde&diff=104782988&oldid=104262388
+
+This is a recurring problem on frwiki.",1403533505,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+GUI for VisualEditor Math plugin,"The original plan for the math plugin was to create a equation editor GUI, similar to that in Google Docs.
+https://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Application
+
+This would have ability to insert mathematical symbols and create structures like integrals, matrices etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392740220,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-grsmbxc6xcqg4so4enlg,task_description,resolved
+GUI for VisualEditor Math plugin,"
+
+*** This bug has been marked as a duplicate of bug 43058 ***",1392741898,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-grsmbxc6xcqg4so4enlg,task_subcomment,NA
+VisualEditor: Avoid mentioning wikitext on MediaWiki error messages (this confuses users who use VisualEditor instead of wikitext),"Consider VisualEditor as the default editing method, and suppose you are a new user arriving at one of the articles currently listed under
+[[Category:Pages with missing references list]]
+(or its equivalents in other languages).
+
+Somewhere in the page there will be messages such as these:
+* There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page).
+
+* There are <ref group=$1> tags on this page, but the references will not show without a {{reflist|group=$1}} template (see the help page).
+
+But since your few edits were made using VisuaEditor, you have no idea what are ""<ref>"", ""<ref group=$1>"" and ""{{reflist|group=$1}}"".
+
+There are many other messages like that which are exposed to (inexperienced) users (either by MediaWiki core or one of its extensions). They should try to describe the problem avoiding talking about the wiki syntax, which will not make sense if VisualEditor is the only way someone is able to edit.
+
+
+This bug report was inspired by the following feedback:
+https://pt.wikipedia.org/wiki/WP:Editor_Visual/Comentários?oldid=38180789#fonte.2C_pede_sempre.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392546660,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-q6kl2cnzpurtdprt2z7l,task_description,open
+VisualEditor: Avoid mentioning wikitext on MediaWiki error messages (this confuses users who use VisualEditor instead of wikitext),"I'm not sure this is a VisualEditor-specific bug, but yes, MediaWiki and its extensions' messages make occasional assumptions of the use of wikitext. This is much more acute due to local communities' over-ridden messages, which much more frequently make this mistake.",1393537441,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q6kl2cnzpurtdprt2z7l,task_subcomment,NA
+VisualEditor: CSS to add numbers to reference list items it vertically misaligned (should be top not bottom?),"Screenshot
+
+Number of reflist vertically misaligned, see screenshot
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://de.wikipedia.org/w/index.php?title=Wolfgang-Hahn-Preis_K%C3%B6ln&veaction=edit
+
+**Attached**: {F13043}",1392490020,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-ojcdgofuxpjixghndf6z,task_description,resolved
+VisualEditor: CSS to add numbers to reference list items it vertically misaligned (should be top not bottom?),This appears to have been fixed some time ago.,1525335436,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-ojcdgofuxpjixghndf6z,task_subcomment,NA
+VisualEditor: CSS to add numbers to reference list items it vertically misaligned (should be top not bottom?),"**santosh.cool.reddy** wrote:
+
+Looks like german pages are not using current visual editor. In english which uses https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide doesn't show such errors.",1394889473,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ojcdgofuxpjixghndf6z,task_subcomment,NA
+VisualEditor: CSS to add numbers to reference list items it vertically misaligned (should be top not bottom?),"**santosh.cool.reddy** wrote:
+
+I had a look into this bug. I suggest style of ve-ce-mwTransclusionInlineNode must be ""inline"" not ""inline-block"" to clear this bug.",1394815686,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ojcdgofuxpjixghndf6z,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"This is with Translate 2014-02-04.
+
+I've created a testcase which you can see by visiting https://www.mediawiki.org/w/index.php?title=User:SamB/tvar_bug&oldid=907218&action=edit&section=1 and clicking the ""preview"" button.
+
+Notice how all of the Translate markup shows up in the Preview because the <translate> tag isn't in this section?  That's kind of annoying.
+
+{F31698682}",1392487980,PHID-USER-3bnjvlq3zbpzzxdh4g4g,PHID-TASK-td6bfetp5r2m3jb36nd3,task_description,resolved
+Section preview in new wikitext editor shows Translate markup,"As suggested by @Arlolra, I reverted  https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/808926/ (as well as https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/837636 to get parsedoc back) on my local wiki to re-test the preview with Parsoid. Things work as I expected - the tags are tranformed into <meta> tags and are not visible in the preview. The old <tvar> syntax doesn't break either. Consequently, I'm considering this issue resolved.",1675189578,PHID-USER-ut3yptb7r45gfpwp33qn,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"This issue is technically not triggering anymore, because section editing with the new wikitext editor are back on the legacy parser (see T154844 / https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/808926/). That said, we may want to keep an eye on it because we probably want to check that it indeed works for section preview when Parsoid becomes the default path for read views. My educated guess there is that it *should* work because of the work we've done on T261181, which transforms these translate/tvar tags into <meta> tags, that shouldn't be displayed, but there may be some corner cases on the detection of the annotation (in particular with the deprecated `<tvar|name>var</>` syntax) outside of a full context.",1675188824,PHID-USER-ut3yptb7r45gfpwp33qn,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,Just noting that there will be inconsistency with section preview in the old wikitext editor where Translate is hiding the tags using ParserBeforeInternalParse hook.,1616139116,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,">>! In T63422#660916, @Aklapper wrote:
+> I don't really see a bug here - unclosed tags are probably just displayed like that by the parser, plus this just applies to the preview. 
+> Not sure if that's something to fix in the Translate codebase.
+
+I'm going to agree with this",1616099628,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,Perhaps the Parsing team can have a look to provide an answer.,1586273756,PHID-USER-hqyy4wr7smuc4rzaoio5,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,Feedback whether this is fixable there would be appreciated.,1585553144,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"Sorry for the delay. That is the screenshot with legacy 2010 wikitext editor:
+{F31712035}
+
+I have just tried with 2017 NWE. Indeed, with this editor, <translate> tags are displayed:
+{F31712065}",1585505319,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"Can you post a screenshot?
+
+I believe this was fixed in {T168743}, but the new wikitext editor is probably still broken because it does previews differently.",1584973908,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"@Nikerabbit That’s strange, even with oldid, I can’t reproduce this bug at home: all <translate> tags, balanced or not, are removed from previewing, while editing a section.
+
+When I edit the full page, all translate tags are displayed if one closing tag is missing. But they are all removed (even successive closing tags) if I edit only a section.",1584973480,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"I can’t reproduce with the given testcase. I think this is fixed, isn’t it?
+
+EDIT: except if translate tags are unbalanced, but the same issue would produce with any unbalanced wikitext, I think",1584908152,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"I can’t reproduce with the given testcase. I think this is fixed, isn’t it?",1584908086,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"I don't really see a bug here - unclosed tags are probably just displayed like that by the parser, plus this just applies to the preview. 
+Not sure if that's something to fix in the Translate codebase.",1396271561,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,"screenshot
+
+steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to the Media Settings of the image
+4.Set the image to frameless and none as position
+5.Now select the image
+
+Observed Result:
+ Image highlight box is appearing at the top left corner of the page
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=14thfebchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12967}",1392406080,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nbibeqvqnm42dfuywhy4,task_description,resolved
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,Verified the fix on:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox,1394758473,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,Verified the fix in test2,1394154128,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,Verified the fix in betalabs,1393636588,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,"Change 116116 merged by jenkins-bot:
+Don't show phantoms for hidden protected items
+
+https://gerrit.wikimedia.org/r/116116",1393615067,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,"Change 116116 had a related patch set uploaded by Esanders:
+Don't show phantoms for hidden protected items
+
+https://gerrit.wikimedia.org/r/116116",1393603609,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,*** Bug 56608 has been marked as a duplicate of this bug. ***,1393541505,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"See for instance
+https://fr.wikipedia.org/w/index.php?title=Philippe_Juvin&diff=101226971&oldid=101177693 .
+The edit added `<span style=""font-size:12.0pt;font-family:""Times New Roman"",""serif""; mso-fareast-font-family:Calibri;mso-ansi-language:EN-GB;mso-fareast-language: EN-US;mso-bidi-language:AR-SA"">` to a newly added reference.
+It was reported by NicoV at fr.wp, I haven't had a chance to see if it can be reproduced or how yet.
+
+**See Also**:
+* {T60689}
+* {T71821}
+* {T71513}
+* {T75292}",1392375360,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-r5hdqedtma6idm3jhqfo,task_description,resolved
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"Copy paste sanitisation has improved significantly since 2014, so closing. If this is still happening, please re-open.",1701962897,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"The previous comments don't explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status.
+
+//(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}. If this task is stalled on an upstream project, then the #upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task needs retesting, then the #testme tag should be added. If this task is either out of scope and nobody should ever work on this, or nobody else managed to reproduce the problem described in this task, then this task should have the ""Declined"" status.)//",1590761765,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"Yeah, probably...",1410806073,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,My guess is that https://cs.wikipedia.org/w/index.php?title=%C4%8Cesk%C3%A1_akademie_v%C4%9Bd_a_um%C4%9Bn%C3%AD&diff=11859116&oldid=11475316 is copy/paste issue as well?,1410805955,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"<span style=""... mso-...""> It's a copy/paste from Microsoft Office => Word
+
+mso + wysiwyg on google => general trouble",1410469468,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"If you look at the history of the same article, you'll see several edits with the same kind of problems (references added with unwanted formatting: span
+I saw the same kind of problem on other articles, but can't find them right now.
+
+https://fr.wikipedia.org/w/index.php?title=Philippe_Juvin&action=history
+https://fr.wikipedia.org/w/index.php?title=Philippe_Juvin&diff=prev&oldid=101128645
+https://fr.wikipedia.org/w/index.php?title=Philippe_Juvin&diff=prev&oldid=100741981",1392381141,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"Anyway, I tested and couldn't reproduce it.",1392376103,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"(It reminds me of Bug 58689, but the tag is different.)",1392375763,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"Intention:
+Whenever a new VE feature is launched it seems as though existing translations are not included.
+
+Steps to Reproduce:
+1. Go to https://sv.wikipedia.org/wiki/Bonsai?uselang=de&veaction=edit
+2. Click on media settings for the first image
+3. Click advanced settings (Erweiterte Einstellungen)
+
+Actual Results:  
+2. Alt_text dialogue reads ""Alternative text""
+3. Position dialogues read ""Position: Left, right, center, none ""
+
+Expected Results:  
+2. Alt_text dialogue reads ""Alternativtext"" (per https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-alttext-section/de)
+3. Should also be all in german (per e.g. https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-position-left/de)
+
+Reproducible: Always
+
+This is not just an issue with the above features (or with uselang=de) but rather happens at every launched VE feature. Since the translations have normally been done before there is no reason why they should not be included as part of the pushing of any new feature.
+
+The VE translations also seem to take longer to go live then translations in other parts of the interface (seems to happen only when there are other VE updates).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64230",1392370920,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_description,invalid
+New VisualEditor translations not appearing in production as quickly as for other features(?),Almost certainly obsolete.,1723522286,PHID-USER-escte3psz5yfd2nj3jzr,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),We'd need to check if the fix for bug 67805 fixed this as well.,1405948295,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"(In reply to Elitre from comment #7)
+> I wonder if bug 64230 is related?
+
+Seems possible; adding as a see-also.
+
+(In reply to Andre Klapper from comment #6)
+> James: As this is assigned to you, do you plan to investigate?
+
+No; unassigning.",1401726082,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),I wonder if bug 64230 is related?,1401725162,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"James: As this is assigned to you, do you plan to investigate?",1401709302,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"James: As this is assigned to you, do you plan to investigate?",1396871270,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"I am not sure if this counts as an example or not.
+A French Wikipedian reported he spotted a few untranslated messages in the interface. I checked, and the French equivalent for both of them did exist on TranslateWiki. While https://translatewiki.net/wiki/MediaWiki:Visualeditor-dialog-transclusion-multiple-mode/fr is quite recent, https://translatewiki.net/wiki/MediaWiki:Visualeditor-dialogbutton-template-tooltip/fr was created last year. The interface tells me these are the correct messages, but they still won't show up. So I just created the related MediaWiki message locally, but I don't think this should be the solution.",1395064954,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"Time difference between VE and non-VE items I've got no source for rather than a general impression (thus ""seems"" in my statement). In general though we are talking about weeks before the translations appear.
+
+The main issue for me would be why existing translations are not included with the launch of new features? For the above case both de and sv translations existed before the features went live, yet they were not included until 1+ week later. Surely the point of making the messages translatable before they go live is to avoid users having to encounter untranslated strings.",1394535978,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),Anybody having an idea how to investigate this?,1394534423,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"(In reply to Lokal_Profil from comment #0)
+> Intention:
+> Whenever a new VE feature is launched it seems as though existing
+> translations are not included.
+> 
+> Steps to Reproduce:
+> 1. Go to https://sv.wikipedia.org/wiki/Bonsai?uselang=de&veaction=edit
+> 2. Click on media settings for the first image
+> 3. Click advanced settings (Erweiterte Einstellungen)
+> 
+> Actual Results:  
+> 2. Alt_text dialogue reads ""Alternative text""
+> 3. Position dialogues read ""Position: Left, right, center, none ""
+> 
+> Expected Results:  
+> 2. Alt_text dialogue reads ""Alternativtext"" (per
+> https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-
+> alttext-section/de)
+> 3. Should also be all in german (per e.g.
+> https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-
+> position-left/de)
+> 
+> Reproducible: Always
+> 
+> This is not just an issue with the above features (or with uselang=de) but
+> rather happens at every launched VE feature. Since the translations have
+> normally been done before there is no reason why they should not be included
+> as part of the pushing of any new feature.
+> 
+> The VE translations also seem to take longer to go live then translations in
+> other parts of the interface (seems to happen only when there are other VE
+> updates).
+
+Translations of VE items should go live at the same time as non-VE items (as they are done by the same process) – if not, this sounds like a localisation update bug. Moving there to see if anyone has any ideas.",1394477005,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+VisualEditor:  Babel box not updated correctly upon editing,"Intention:
+Remove extraneous items from a Babel box
+
+Steps to Reproduce:
+1. Click on the Babel box to edit it. 
+2. Remove unwanted parameters (with trashcan icon).
+3. Apply changes.
+
+Actual Results:  
+Three items were correctly removed, but two that were kept were not displayed in VisualEditor.  (See screenshot to compare diff to VisualEditor's display.)
+
+Expected Results:  
+The transcluded {{#babel:en}} function would display correctly. 
+
+Reproducible: Yes
+",1392340440,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rzxhwx6c7jxhiti6ntu6,task_description,open
+VisualEditor:  Babel box not updated correctly upon editing,This is still a problem.,1532748248,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rzxhwx6c7jxhiti6ntu6,task_subcomment,NA
+VisualEditor:  Babel box not updated correctly upon editing,"Created attachment 14584
+Babel box bug:  ""Review changes"" does not match what's displayed in the lower right corner.
+
+**Attached**: {F12886}",1392340499,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-rzxhwx6c7jxhiti6ntu6,task_subcomment,NA
+VisualEditor: Clear formatting remains selected even after re-applying the styles from the menu,"Highlighted clear formatting option
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text and apply some text styles from the toolbar like ""Bold"", ""Italic""
+3.Now select ""Clear Formatting:
+4.Again reapply these formats
+
+Observed Result:
+Observe that, the though the text formats are reapplied the ""Clear formatting"" option remains selected.
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/11thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13203}",1392147360,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ee2cihypua6u4gysreal,task_description,resolved
+VisualEditor: Clear formatting remains selected even after re-applying the styles from the menu,Verified the fix on production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1397859484,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-ee2cihypua6u4gysreal,task_subcomment,NA
+VisualEditor: Clear formatting remains selected even after re-applying the styles from the menu,This was fixed last month.,1397787388,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ee2cihypua6u4gysreal,task_subcomment,NA
+Flow: default-thumbnail-size preferences are not being followed,"All thumbnails, eg [[File:example.jpg|thumb]], are displaying as 220px (which is the usual wikimedia/mediawiki default, per bug 21117). 
+
+If I change my ""Thumbnail size"" preferences (to 300px for example) at https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-rendering then the thumbnails in existing Flow posts do not change accordingly.
+
+The same applies to new posts that I make, or posts that I edit: all thumbnails are 220px regardless.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391825160,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-b3kyg6embdoi5bsozap4,task_description,declined
+Flow: default-thumbnail-size preferences are not being followed,Original patch (in VE) is closed - shutting this one down as well,1409929682,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-b3kyg6embdoi5bsozap4,task_subcomment,NA
+Flow: default-thumbnail-size preferences are not being followed,"Possibly this is a WONTFIX, per bug 47804 (""VisualEditor: ""Thumb"" images should display in wiki default thumb size""). Which seems reasonable, but if so, it should be documented.",1393448397,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-b3kyg6embdoi5bsozap4,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,"broken link inspector UI
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image
+3.Go to some other tab/window
+4.After an idle time (~5 mins) come back to VE
+5.Open any inspector like galley/link/Math
+
+Observed Result:
+
+All the inspectors are appearing with broken UI
+
+See the screenshots attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://test2.wikipedia.org/wiki/Test2chromefeb7th?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70580
+
+**Attached**: {F12858}",1391822100,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2vwr5t63vss7tgocwalj,task_description,resolved
+VisualEditor: All inspectors get broken after VE tab is idle for a while,Bah.,1429482768,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,"I'm imagining so, too.",1429482758,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,Probably long fixed…,1429482620,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,Has anyone run into this issue recently?,1424831007,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,"Seems to be fixed. Formula/Gallery inspectors have a slight problem with displaying their border in full-screen view(test2 only), otherwise - betalabs/production display all inspectors correctly after various idle time intervals - 5-20 min.",1419380234,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,"Created attachment 14530
+Formula inspector UI
+
+**Attached**: {F12859}",1391822134,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: Block format=xml from action=visualeditor API,"Given url:
+http://en.wikipedia.org/w/api.php?action=visualeditor&page=Berlin&paction=parse
+
+Return this:
+<?xml version=""1.0""?>
+<api servedby=""mw1193"">
+  <error code=""internal_api_error_MWException"" info=""Exception Caught: Internal error in ApiFormatXml::recXmlPrint: (notices, ...) has integer keys without _element value. Use ApiResult::setIndexedTagName()."" xml:space=""preserve"" />
+</api>
+
+I guess, I make something wrong, but the error message does not really help me to understand what goes wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62452",1391769780,PHID-USER-nwa6c3hm5nmv7ixrih4p,PHID-TASK-6xksishkejfbmz5cphbk,task_description,resolved
+VisualEditor: Block format=xml from action=visualeditor API,"Change 119912 merged by jenkins-bot:
+Block non-JSON API access to VisualEditor, as it won't work
+
+https://gerrit.wikimedia.org/r/119912",1395870545,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6xksishkejfbmz5cphbk,task_subcomment,NA
+VisualEditor: Block format=xml from action=visualeditor API,"Change 119912 had a related patch set uploaded by Jforrester:
+Block non-JSON API access to VisualEditor, as it won't work
+
+https://gerrit.wikimedia.org/r/119912",1395362773,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6xksishkejfbmz5cphbk,task_subcomment,NA
+VisualEditor: Block format=xml from action=visualeditor API,The action=visualeditor API is purely designed for JSON access; we should inform the user that XML / etc. won't work instead of dying horribly.,1395362761,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6xksishkejfbmz5cphbk,task_subcomment,NA
+VisualEditor: Spin out UnicodeJS,"If nothing else, it should probably be in the /lib directory rather than /modules (which will save us a directory's depth of file paths).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391306880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kyycecb3ijdvy6pujf74,task_description,resolved
+VisualEditor: Spin out UnicodeJS,Done at Wikimania 2014.,1416343480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kyycecb3ijdvy6pujf74,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,,1391281200,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-yjftwp5bygch5jgawu3q,task_description,open
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,This is a Parsoid/RESTBase issue. For caching purposes they don't serve different content based on user preferences.,1448666007,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,"At least this should be forward compatible and support the MathML rendering mode... maybe it's not optimal to classify this as ""Low"" priority.",1442510715,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,"Sure, but the non-MathJax rendering options are also ignored.",1442506944,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,MathJax is no longer supported. See T99369,1442497325,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,*** Bug 64572 has been marked as a duplicate of this bug. ***,1402295506,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,"The title change seems to have repurposed this bug. The original title 
+VisualEditor: Math formulas don't display correctly after save (until page is reloaded)  was a dupe of bug 36060 a dependant of bug 51565.
+
+The current title does not describe current behaviour:
+
+With VisualEditor formulae editing beta feature OFF. Formula are displayed as PNG's and can't be edited.
+
+With VisualEditor formulae editing beta feature ON. Formula are initially displayed as PNG's they can be edited. As soon as they are edited they switch to MathJax display but with very garbled output due to Bug 61497.",1398717771,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+VisualEditor: Providing clearer errors about invalid media item sizes on new Media Settings>Advanced Settings,"Right now, if I add an image for example:https://test2.wikipedia.org/wiki/File:Foo.jpg
+
+Initially in VE from Insert>Media it renders as 229x150.
+If a user attempts to resize it to 350x350 , it will show a message that ""Size Values are invalid""  as it has exceeded the original dimension values.But unless user knows those original dimensions , he or she might keep trying with different values not knowing what should be the input limit.
+
+I think it will be better if we can have more clearer indication in the message saying something like ""the size values are invalid since it has exceeded original dimension""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391216220,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-m2mltnucijghdtio7lex,task_description,open
+VisualEditor: Providing clearer errors about invalid media item sizes on new Media Settings>Advanced Settings,"(In reply to comment #2)
+> Should those block the 'apply' button, or just give an indication that the
+> size itself won't be applied, giving the user the option to apply the rest
+> of the properties?
+
+The second – see bug 60602.",1391663516,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2mltnucijghdtio7lex,task_subcomment,NA
+VisualEditor: Providing clearer errors about invalid media item sizes on new Media Settings>Advanced Settings,"Should those block the 'apply' button, or just give an indication that the size itself won't be applied, giving the user the option to apply the rest of the properties?",1391662714,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-m2mltnucijghdtio7lex,task_subcomment,NA
+VisualEditor: Providing clearer errors about invalid media item sizes on new Media Settings>Advanced Settings,"We should probably have several errors:
+
+* ""Size can be up to <width>x<height> pixels."" (if too big for media)
+* ""Size must be positive whole numbers."" (if not valid, e.g. negative or ""hello"")
+* ""Size is limited to <maxsize> pixels."" (if SVGMaxSize reached)",1391661265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2mltnucijghdtio7lex,task_subcomment,NA
+"VisualEditor:  Character set in mathematical symbols is out of order (degree, seconds, minutes)","Reproducible: Always
+
+http://mediawiki.org/wiki/MediaWiki:Visualeditor-specialcharinspector-characterlist-insert should have the logical order of degrees, minutes, seconds, not with seconds in the middle.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1391106240,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-mcubwbacjd3vavyugrkq,task_description,resolved
+"VisualEditor:  Character set in mathematical symbols is out of order (degree, seconds, minutes)","Change 138304 merged by jenkins-bot:
+Re-order special character mathematical symbols to be degrees, minutes, seconds
+
+https://gerrit.wikimedia.org/r/138304",1402335952,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mcubwbacjd3vavyugrkq,task_subcomment,NA
+"VisualEditor:  Character set in mathematical symbols is out of order (degree, seconds, minutes)","Change 138304 had a related patch set uploaded by Jforrester:
+Re-order special character mathematical symbols to be degress, minutes, seconds
+
+https://gerrit.wikimedia.org/r/138304",1402296161,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mcubwbacjd3vavyugrkq,task_subcomment,NA
+OOjs UI: Constructive button has odd green border when disabled,"I'm not sure, but I think this is a regression (it didn't use to be this way).
+
+A button that is flagged as constructive and currently disabled has a green border around its otherwise grey button. When hovering the button the border becomes grey, so it doesn't seem intentional that the border is green (otherwise it should have a hover implementation as well).
+
+This is most visible when opening VisualEditor, the save button has emits this behaviour.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390859100,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4hlmsxmf5qswcobid4c5,task_description,resolved
+OOjs UI: Constructive button has odd green border when disabled,"Change 122879 merged by jenkins-bot:
+apex/button: Reset border-color of disabled button when not hovered
+
+https://gerrit.wikimedia.org/r/122879",1396400208,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4hlmsxmf5qswcobid4c5,task_subcomment,NA
+OOjs UI: Constructive button has odd green border when disabled,"Change 122879 had a related patch set uploaded by Krinkle:
+apex/button: Reset border-color of disabled button when not hovered
+
+https://gerrit.wikimedia.org/r/122879",1396380543,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4hlmsxmf5qswcobid4c5,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**Author:** `gryllida`
+
+**Description:**
+Script viewer software should support sections and section editing, using one-line comments (or special formatting therein) for heading syntax.
+
+---------------------------------------------
+
+/* Foo */
+
+Foo.prototype.bar = function(){
+...
+};
+Foo.prototype.baz = function(){
+...
+};
+
+^^^^^ everything above is in the Foo section
+
+/* Foo 2 */ <---------- this becomes a heading
+
+Foo2.prototype.bar = function(){
+...
+};
+
+Foo2.prototype.baz = function(){
+...
+};
+
+^^^^^ everything above is in the foo 2 section
+
+
+---------------------------------------------
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50962",1390727760,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2vt7ams74ruy224ob3kr,task_description,resolved
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"This seems effectively solved by the SyntaxHighlight extension and its integration for VisualEditor ({T49742}).
+
+{F35040371 height=200}
+
+Source code: [ve.ui.MWSyntaxHighlightDialog.js](https://github.com/wikimedia/mediawiki-extensions-SyntaxHighlight_GeSHi/blob/607afd5b4828af627447ed05ebc74829641706bf/modules/ve-syntaxhighlight/ve.ui.MWSyntaxHighlightDialog.js)",1649198234,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"We actually have a geshi module that does this in the CodeEditor codebase, but it's only the editor mockup, it's not actually able to make changes to the wikitext right now.
+
+Because you seem to be interested in similar functionality, I have fixed up the module in this patch: https://gerrit.wikimedia.org/r/#/c/127451/
+
+Making it fully work would be quite some additional work still, but it's not as far away as I initially figured. The biggest problem is that we need to make sure not to implement everything a dozen times (live preview, editpage, visual editor and inline code editor).",1398258317,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**gryllida** wrote:
+
+There are two reasons behind this.
+
+1) Usually people contain different objects in different files. On wiki, browsing (or simply creating) different files and subfiles of a JS file is far from intuitive. It could make sense to add support for sections.
+
+2) Inline (POD-like) documentation would benefit readability. See i.e. http://juerd.nl/site.plp/perlpodtut .
+
+In other words, CodeEditor should be capable of editing any <source> block on a page without entering edit mode for the entire page. I am renaming the bug title accordingly.",1395793964,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"Can I ask why ?
+
+I mean a section in Javascript is usually not a self-contained unit, it only has meaning icw all the other stuff. So I'm trying to understand why you would want to edit it in that way. Can you clarify how this helps you to edit code ?",1395784846,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**gryllida** wrote:
+
+https://test.wikipedia.org/wiki/User:Gryllida/common.js
+a stupid ugly workaround
+
+https://test.wikipedia.org/wiki/User:Gryllida/afch2/v2
+with sections
+
+syntax highlight ok, code-editor does not pick it up",1391082175,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"See also
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43008#c2",1391079604,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**gryllida** wrote:
+
+(Or Lua script.)",1390862418,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**gryllida** wrote:
+
+Whatever I see when reading or editing [[Special:MyPage/common.js]]. (There is one extension which highlights the code when reading it, and another extension which is responsible for the code editor; I don't know which one this bug falls under, since both of them would have to support editing a section of a JS or CSS script.)",1390862387,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"Hi, what is ""Script viewer""? Is this [[mw:Extension:CodeEditor]]?",1390822843,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Dragging and dropping text (as an alternative to keyboard or context menu copy and paste commands) inside CodeEditor does not work.
+
+Since this is basic functionality in every other editor I know this should also be supported by CodeEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://github.com/ajaxorg/ace/issues/1879",1390684080,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-35qnbteoopi7ow3gqvxx,task_description,resolved
+CodeEditor's drag and drop only works after a small delay,I carnt set multiple assigned to by TheDj is also included.,1422657344,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,I cArnt set multiple assigned to by TheDj is also included.,1422657328,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 144780 merged by Brion VIBBER:
+Ace: Update to 2015-01-28
+
+[[https://gerrit.wikimedia.org/r/144780]]",1422657048,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 144780 had a related patch set uploaded (by Paladox):
+Ace: Update to 08-07-2014
+
+[[https://gerrit.wikimedia.org/r/144780]]
+
+#patch-for-review",1418639731,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 144780 had a related patch set uploaded by TheDJ:
+Ace: Update to 08-07-2014
+
+https://gerrit.wikimedia.org/r/144780",1404853195,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,Fixed upstream. I'll schedule an update of the code sometime next week.,1404475578,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 121044 abandoned by TheDJ:
+Remove CodeEditor delay in drag & drop of text
+
+Reason:
+Fix added upstream.
+
+https://gerrit.wikimedia.org/r/121044",1404475516,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Has been fixed upstream (thanks Derk-Jan):
+https://github.com/ajaxorg/ace/commit/63f43da96a1bd2b9894c371fb0feed7e38ef34d6
+
+Let's wait until this fix makes it into MediaWiki's CodeEditor extension...",1403901473,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,Very nice! Thank you for the submission.,1403363117,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,https://github.com/ajaxorg/ace/pull/2012,1403362973,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,i still need to wrap this in some platform dependent if constructs.,1403253798,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 121044 had a related patch set uploaded by TheDJ:
+Remove CodeEditor delay in drag & drop of text
+
+https://gerrit.wikimedia.org/r/121044",1395839162,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"So as answered in the linked upstream bug it seems this delay is actually configurable.
+
+Nighwing wrote:
+You can disable dragDelay by setting editor.setOption(""dragDelay"", 0)
+
+Can somebody familiar with CodeEditor implement this? I can't see a reason to keep the delay at this point.",1395836631,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,Thank you for clarifying Eduard !,1395793382,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Upstream bug is https://github.com/ajaxorg/ace/issues/1879
+
+Let's hope it is easy fixable and not some sort of technical limitation.",1395791458,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"No this definitely is about CodeEditor!
+
+And while I just wanted to write that this is definitely not fixed I just realized during some additional testing that it actually is working... but only somehow.
+
+I don't know if I have a very special way of dragging/dropping but actually dragging only starts after a small delay (note that after clicking highlighted text the cursor only changes to the move cursor after approx. 100 ms). If you start moving the mouse before it will just create a new selection.
+However when normally dragging/dropping I start moving the mouse right away. Moving the mouse over the highlighted text, clicking, then *waiting* and only after waiting beginning to move the mouse is just counterintuitive and different from every other program I know.
+
+Since it therefore doesn't seem to be specific to MediaWiki's implementation (Ace's web demo ""works"" exactly the same) I'll report a bug for Ace directly however. I'll update this bug with the respective info then.",1395790507,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"This works for me in the beta at least: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Module:HtmlBuilder&action=edit
+
+It might be that the reporter is actually talking about VisualEditor, which indeed does not seem to support drag and drop of text.",1395787108,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),This should especially useful as new images may not appear in the API search results due to caching.,1390585980,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_description,resolved
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 617434 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@REL1_35] Follow-up I0a1a889: Show user uploads in gallery dialog
+
+https://gerrit.wikimedia.org/r/617434",1596141663,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 617434 had a related patch set uploaded (by Bartosz Dziewoński; owner: Esanders):
+[mediawiki/extensions/VisualEditor@REL1_35] Follow-up I0a1a889: Show user uploads in gallery dialog
+
+https://gerrit.wikimedia.org/r/617434",1596141357,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 617490 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Follow-up I0a1a889: Show user uploads in gallery dialog
+
+https://gerrit.wikimedia.org/r/617490",1596129003,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 617490 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Follow-up I0a1a889: Show user uploads in gallery dialog
+
+https://gerrit.wikimedia.org/r/617490",1596123964,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 210831 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWMediaDialog: Show user uploads when no query provided
+
+https://gerrit.wikimedia.org/r/210831",1594647105,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 589343 **merged** by jenkins-bot:
+[mediawiki/core@master] mw.widgets.MediaSearchWidget: Show user uploads when query empty
+
+https://gerrit.wikimedia.org/r/589343",1594567921,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 210831 restored by Esanders:
+MWMediaSearchWidget: Show user uploads
+
+[[https://gerrit.wikimedia.org/r/210831]]",1587052040,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 589343 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/core@master] mw.widgets.MediaSearchWidget: Show user uploads when query empty
+
+[[https://gerrit.wikimedia.org/r/589343]]",1587051894,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 210831 abandoned by MarkAHershberger:
+MWMediaSearchWidget: Show user uploads
+
+[[https://gerrit.wikimedia.org/r/210831]]",1492468066,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"@Jdforrester-WMF I see the #Design tag was added but just wanted to make it explicit, I assume correctly from T154234#3072200 that this task is currently blocked on a design for showing user uploads in the Media insertion dialog so that <https://gerrit.wikimedia.org/r/210831> can be reworked to implement that?",1488594068,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 210831 had a related patch set uploaded (by Esanders):
+WIP Show recent uploads in MWMediaSearchWidget
+
+[[https://gerrit.wikimedia.org/r/210831]]
+",1450311354,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Jdforrester-WMF writes:
+
+> This is a functionality task. The search results caching task was
+> resolved by the switch to ElasticSearch months ago.
+
+Just to be clear, though, this is something I would see in any browser,
+right?  I've seen it in multiple browsers and across reboots so it isn't
+a local caching problem.",1424962321,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),">>! In T62398#1067311, @MarkAHershberger wrote:
+> This issue (can't see recent uploads in the selection) was pointed out to me by a client.  At first I thought this was an IE caching problem, but I'm glad  to see it has been spotted elsewhere.
+
+This is a functionality task. The search results caching task was resolved by the switch to ElasticSearch months ago.",1424895969,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"This issue (can't see recent uploads in the selection) was pointed out to me by a client.  At first I thought this was an IE caching problem, but I'm glad  to see it has been spotted elsewhere.",1424895867,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 109670 had a related patch set uploaded by Esanders:
+WIP Show recent uploads in MWMediaSearchWidget
+
+https://gerrit.wikimedia.org/r/109670",1391099540,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Re: search caching, 'File:Three_sided_football_pitch.svg' is still not showing up in search results, an hour after uploading.",1390595356,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Yes there will be edge cases where the username on commons is different, but that is an edge case.
+
+We can fill in the first row with recent uploads if found (which solves the case of ""most users don't upload"") and then fill with page title.",1390595056,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Currently we show the name of the article. Lots of users have mentioned that this is helpful (albeit limited utility for non-English users until we implement Wikidata-based item searching instead of string searching).
+
+Walking away from this benefit from the somewhat-dubious benefit of your own uploads (most users don't upload, and we'd have no way to check for your ""own"" uploads on foreign repos) feels like a regression.",1390593864,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),We can just show recent uploads when no search term is entered.,1390593454,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"(In reply to comment #0)
+> This should be relatively simple compared to full UploadWizard integration,
+
+… but turns a simple search interface into a (multi-tabbed?) optional series of interfaces. :-(
+
+> new images may not appear in the API search results due to caching.
+
+{{cn}}
+
+The exceptional amount of work put into the new search system has this as its most significant user-facing improvement.",1390587311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+VisualEditor:  Unclosed <dl> and <div> tags caused by absent {{refend}} template cannot be repaired,"Intention:
+Remove a line that appears in the last section of a page, underneath a section that has an unclosed/unpaired {{refbegin}} template.
+
+Steps to Reproduce:
+1. Open https://en.wikipedia.org/w/index.php?oldid=592187387 in VisualEditor.
+
+2. Try to select anything after the ==Bibliography== section, e.g., anything in the ==External links== section.
+
+Actual Results:  
+The cursor knows only two positions:  before the refbegin template, and in the slug at the bottom of the page.  You can't select or edit anything in between.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390579800,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-otqxqq3jfgirvkvr5ko2,task_description,resolved
+VisualEditor:  Unclosed <dl> and <div> tags caused by absent {{refend}} template cannot be repaired,"No reply. Assuming this is done. If not, then please reopen.",1617657078,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-otqxqq3jfgirvkvr5ko2,task_subcomment,NA
+VisualEditor:  Unclosed <dl> and <div> tags caused by absent {{refend}} template cannot be repaired,"Seven years later, on https://en.wikipedia.org/w/index.php?title=Chemotherapy&veaction=edit&oldid=592187387 , this shows some transclusion info on the right:
+{F32426376}
+
+Good enough? 
+Tasks shouldn't be stalled forever.",1604399234,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-otqxqq3jfgirvkvr5ko2,task_subcomment,NA
+VisualEditor:  Unclosed <dl> and <div> tags caused by absent {{refend}} template cannot be repaired,I'm not sure what else you could expect VE to do here.,1414812075,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-otqxqq3jfgirvkvr5ko2,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"Steps to reproduce:
+
+- create a simple page with just this text: <syntaxhighlight lang=""xml"">></syntaxhighlight>
+- example page: https://test2.wikipedia.org/wiki/Codez
+- when the page is saved, only this is displayed, as expected: >
+
+- edit the page with visual editor
+- edit the text using syntaxhighlight editor
+- for example, add just this: <
+- see attached screen shot #1
+
+- use ""back"" icon to see how the text will look like
+- I was expecting to see this as page text: ><
+- instead, the preview says page text is: &gt;&lt;
+- see attached screen shot #2
+
+- when the page is saved, the text is displayed correctly: ><
+- see attached screen shot #3
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1390390860,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-yagspunhz2cfycrqyzbn,task_description,resolved
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"This is actually the same issue as bug 57429, let's merge the bugs.
+
+*** This bug has been marked as a duplicate of bug 57429 ***",1404486826,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,*** Bug 66456 has been marked as a duplicate of this bug. ***,1404435630,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"Created attachment 14357
+screen shot #3
+
+**Attached**: {F12969}",1390390978,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"Created attachment 14356
+screen shot #2
+
+**Attached**: {F12968}",1390390950,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"Created attachment 14355
+screen shot #1
+
+**Attached**: {F12966}",1390390931,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Steps to reproduce:
+
+1.Open a page which has a gallery inside it with VE
+2.Select the gallery and open the gallery inspector
+3.Close the gallery inspector 
+
+Observed Result:
+
+The ""Save page"" button of the page gets enabled although no change has been made in the gallery inspector
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Thedomtest
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1390348020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fpau7gga5ngffxkbjtka,task_description,resolved
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Change 342240 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor] Update gallery actions in response to changes
+
+[[https://gerrit.wikimedia.org/r/342240]]
+",1489520603,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fpau7gga5ngffxkbjtka,task_subcomment,NA
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Change 342240 had a related patch set uploaded (by Tchanders):
+[mediawiki/extensions/VisualEditor] Update gallery actions in response to changes
+
+[[https://gerrit.wikimedia.org/r/342240]]
+",1489518688,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fpau7gga5ngffxkbjtka,task_subcomment,NA
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Change 315449 abandoned by Tchanders:
+WIP Update gallery dialog actions to reflect presence of changes
+
+Reason:
+This was split into two patches
+
+[[https://gerrit.wikimedia.org/r/315449]]",1489164701,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fpau7gga5ngffxkbjtka,task_subcomment,NA
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Change 315449 had a related patch set uploaded (by Tchanders):
+WIP Update gallery dialog actions to reflect presence of changes
+
+[[https://gerrit.wikimedia.org/r/315449]]
+",1476233341,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fpau7gga5ngffxkbjtka,task_subcomment,NA
+Fully alphabetize Wikimedia configuration file visualeditor.dblist,"https://noc.wikimedia.org/conf/visualeditor.dblist
+
+This should be fully alphabetized, in my opinion. While people with intimate knowledge of Wikimedia's structure can likely discern and explain the current order, it seems like a lot more overhead than any value provided. A simple alphabetical index is easier to maintain (including insertion), it's more consistent with the other lists of databases (as far as I know), etc.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1390266360,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-wljhvk4gfcklidyyzcbh,task_description,declined
+Fully alphabetize Wikimedia configuration file visualeditor.dblist,"Why? It's a list of 300 dbnames; no-one sane is going to read it, just grep through it.
+
+The current structure is sorted {public/private,project,alphabetical}. This is to prevent accidental mis-configuration. Eventually VE will be on for all wikis, but then we'll just delete this dblist.
+
+If dblists supported comments it'd probably be easier to see, I agree, but that is not this bug.",1390321562,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wljhvk4gfcklidyyzcbh,task_subcomment,NA
+Client-side previewing,"I'm not sure how well these would work, but at least here in China, it is slow to wait for previews of musical scores for each modification. If you could add client-side support to Score, perhaps via:
+
+* http://code.google.com/p/abcjs/
+* https://github.com/incompleteopus/vexabc
+
+...I wonder whether client-side rendering support (ideally in SVG in case notes could be synchronized with the music play-back in the future) could be added, if not now, then maybe after the main Mediawiki WYSIWYG interface stabilizes?
+
+And support for the emerging Web Audio standard would be awesome for client-side audio play-back as well...
+
+Also, with ABC seeming (to my quick glance) more like an open standard than Lilypond, might it make sense to make ABC the default?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1390051560,PHID-USER-gljzp3uzec5ukggh6xdk,PHID-TASK-fpifldug4t73yao6kw5o,task_description,duplicate
+Client-side previewing,"#visualeditor implements similar support to your examples. Also, both ABC and Lilypond are open, but Lilypond is more flexible and has `abc2ly`. ABC doesn't have vice-versa :)",1502063966,PHID-USER-u66bgsaukythpwcdyjdu,PHID-TASK-fpifldug4t73yao6kw5o,task_subcomment,NA
+"Separate UploadWizard's data-handling, interface, and other controlling methods and put generally-applicable code into MediaWiki","In the past few years we've worked really hard to bring UploadWizard to a usable state, and now that we have a Multimedia team framework to actually do some good work on it, and we have the impetus to start making the upload pipeline way better, let's do it the right way: Let's make this project the organized, well-engineered machine it should have been in the first place.
+
+I would particularly emphasize code conventions being followed, jshint conformance, an eye towards an MVC-like structure (nothing strict, but as a general goal...), building toward libraries that can be used elsewhere, and a variety of different possible interfaces.
+
+Ideally none of the upload steps will be entangled unnecessarily with other steps, and we will be able to untangle them when necessary and put them in different pages or tools.
+
+Ideally we will use the brilliant work- and complexity-reducing technology (oojs, oojs-ui, jQuery promises, moment.js) that other projects have started using in recent times.
+
+It is an absolute *must* that we build tests for this system as we are building it, if we want this to be a generally useful set of tools for other projects. Same for documentation.
+
+The leaders in LOC for active frontend projects deployed on the cluster are* VisualEditor, UploadWizard, Flow, and MultimediaViewer (in no particular order). Let's start bringing the upload pipeline projects closer to the high standards that other projects are holding themselves to.
+
+* According to an unscientific survey based on guesswork
+
+See https://www.mediawiki.org/wiki/Requests_for_comment/More_general_frontend_uploading_tools for more.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62513",1389627360,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-gtvhfsoc4hivpuvxra7b,task_description,resolved
+"Separate UploadWizard's data-handling, interface, and other controlling methods and put generally-applicable code into MediaWiki",`<prtksxna> James_F: I think mw.Upload and mw.ForeignStructuredUpload resolved this.`,1442332652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gtvhfsoc4hivpuvxra7b,task_subcomment,NA
+VisualEditor: Work correctly in Draft namespace (tracking),"This is a tracking bug for any problems in VisualEditor associated with the Draft: namespace at the English Wikipedia.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389304860,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-t7jppwsetf7fxoydv5qc,task_description,resolved
+VisualEditor: Work correctly in Draft namespace (tracking),Indeed. All known issues fixed. Marking as such.,1415031855,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t7jppwsetf7fxoydv5qc,task_subcomment,NA
+VisualEditor: Work correctly in Draft namespace (tracking),It seems slightly silly to have a whole tracking bug lying around to track one single bug...,1414807490,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-t7jppwsetf7fxoydv5qc,task_subcomment,NA
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","It's not clear how the ""Tag the edit for further review"" option for AbuseFilter rules would work for Flow. Maybe it would add something to the Special:RecentChanges entry for FLow.
+
+This is mentioned in https://www.mediawiki.org/wiki/Flow/Administration_notes
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**: {T64750}",1389145320,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_description,open
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","See here for an example of where AF tags appear:
+https://en.wikipedia.org/w/index.php?title=User:Quiddity_%28WMF%29/sandbox&action=history
+https://en.wikipedia.org/w/index.php?title=Special:Contributions/Quiddity_%28WMF%29&dir=prev&offset=20140107194435&limit=2&target=Quiddity+%28WMF%29
+""(Tag: VisualEditor)""
+
+documentation at:
+https://en.wikipedia.org/wiki/Wikipedia:Tags
+(and more linked in the navbox at the top)",1389212921,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_subcomment,NA
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","We may be able to get this tag indication into the presentation of Flow changes in RecentChanges, Watchlist, Special:Log and history.",1389208749,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_subcomment,NA
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","FWIW, I took a very quick look at that code in AbuseFilter yesterday - this is pretty much what it does for article edits.
+
+AFAICT, when running a filter is matched and it needs to tag, something is added to array AbuseFilter::$tagsToSet, which is then read from a hook triggered when saving recentchanges for an article edit (RecentChange_save)",1389186155,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_subcomment,NA
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","**bingle-admin** wrote:
+
+The WMF core features team tracks this bug on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/flow/cards/701, but people from the community are welcome to contribute here and in Gerrit.",1389145528,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"On wiki's with Scribunto installed, when viewed in the mobile site, the exception ""Uncaught Error: Unknown dependency: ext.scribunto"" is thrown which prevents any further JavaScript from running.
+
+This is because the module is not registered on mobile.
+
+It also depends on jquery.ui.dialog code which pulls in the entire jquery.ui library - we certainly do not want on mobile where JavaScript load should be as tiny as possible.
+
+I doubt we'd want to run this code on mobile thus the use of addInlineScript needs to be avoided since the module doesn't exist in the mobile environment. At the very least it should be wrapped with a try catch so say it is acceptable to fail.
+
+Seems to have been introduced by https://gerrit.wikimedia.org/r/#/c/5617/1,publish
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389142380,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-4aq45pqxrqjz2qfggqde,task_description,resolved
+Scribunto pulls in jquery.ui.dialog for error reporting,"Change 109262 abandoned by TheDJ:
+Conditionally load jquery.ui.dialog for Scribunto errors
+
+Reason:
+Fixed with: https://gerrit.wikimedia.org/r/#/c/118944/
+
+https://gerrit.wikimedia.org/r/109262",1396790729,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,I'd still advise you to move away from jquery.ui but this is not effecting mobile now so I am happy.,1395858075,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Change 118944 merged by jenkins-bot:
+Don't try to inline load ext.scribunto on mobile
+
+https://gerrit.wikimedia.org/r/118944",1395857889,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Change 118944 had a related patch set uploaded by Hoo man:
+Don't try to (inline load) ext.scribunto if it isn't registered
+
+https://gerrit.wikimedia.org/r/118944",1394938224,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Change 109262 had a related patch set uploaded by TheDJ:
+Conditionally load jquery.ui.dialog for Scribuntu errors
+
+https://gerrit.wikimedia.org/r/109262",1390525326,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Updated summary since of course it doesn't pull in the whole of jQuery UI, it pulls in jquery.ui.dialog and (implicitly) its 7 dependencies, so 8 out of the 17 JavaScript files in resources/jquery.ui/",1390427962,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"let's just dynamically load it, it's simple and not too many 'normal' users are using it anyways. When OOjs is more mature, we can just switch it over.",1390427852,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"One problem with alert() is that it's not HTML, so you couldn't click on the source file links which appear in the Scribunto backtraces.
+
+(In reply to comment #1)
+> Okay this doesn't look so bad now as it seems to only become a problem when a
+> ScribuntoError occurs (I'm not sure how often this occurs on wiki's - I've
+> only managed to replicate this locally). 
+
+You can replicate it on the pages in this category:
+
+https://en.wikipedia.org/wiki/Category:Pages_with_script_errors
+
+It looks like there are currently no such pages in the main namespace, so the impact of this bug on readers of en.m.wikipedia.org is negligible.
+
+There's a bug in Scribunto which causes jquery.ui.dialog and the hidden category to be added even if no errors are emitted into the final HTML, say due to the error being sent to the condition of a {{#iferror:}}. At one point, there were tens of thousands of pages in [[Category:Pages with script errors]] for no obvious reason, possibly due to that bug. So, it would have affected mobile readers at that time. That could be reported separately if it's not already.
+
+> However it seems bizarre to me that the
+> entire jQuery UI library would be loaded simply for error reporting...
+
+I think error reporting is the most important feature in Scribunto, it's central to the usability of Lua scripting. So I don't think it's bizarre that it loads libraries. It's just somewhat inefficient. 
+
+I would be fine with a lightweight DIY thing, or with dynamic loading of jquery.ui.dialog on click of the error message, with a spinner.",1390427209,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"OOjs is in core, but if you want to make dialogs, you probably need OOjs UI as well, which is still only in VisualEditor.",1390427077,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"(In reply to comment #4)
+> * Remove the dialog code from Scribunto and just use a JS alert in the
+> meantime. Alerts are pretty unfriendly (since they take over the browser,
+> stop
+> JS execution, etc.), but since it's such a limited use, it might be OK for a
+> short-term fix.
+
+I believe some browsers are starting to block alters entirely.
+
+(In reply to comment #5)
+> As stated the correct thing to do would be to start using OO.js which is in
+> core.
+
+Patches welcome. Or even links to examples.",1390425282,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"In case I was clear please do not follow Ryan's suggestion of 
+""Make jquery.ui and jquery.ui.dialog loadable on mobile by giving them the
+'mobile' target in the module definition (and make sure they are only loaded
+when there is an error)""
+
+An alert would make more sense, using jQuery UI is overkill for this use case imo.",1390425155,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"jQuery UI != jQuery
+Use jQuery by all means of a jQuery plugin for this - you do not need a huge library the size of jQuery UI.
+
+jQuery UI is totally unsuitable for mobile. Please do not load it to simply use I'd guess about 2% of the library..
+
+As stated the correct thing to do would be to start using OO.js which is in core.",1390425066,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"For desktop, jQuery UI is fine (at least until OO.js is more widely adopted). The only problem is that mobile doesn't want to load jQuery UI unless absolutely necessary, and Scribunto is used on both desktop and mobile.
+
+There are two possible short-term solutions:
+* Make jquery.ui and jquery.ui.dialog loadable on mobile by giving them the 'mobile' target in the module definition (and make sure they are only loaded when there is an error)
+* Remove the dialog code from Scribunto and just use a JS alert in the meantime. Alerts are pretty unfriendly (since they take over the browser, stop JS execution, etc.), but since it's such a limited use, it might be OK for a short-term fix.",1390422361,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,What's the point of having jQuery if we're not supposed to use it?,1390420768,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Realistically, Scribunto does not require the full jQuery UI. I feel that it should roll its own ""script error"" popup, since jQuery UI Dialogs were not really designed for this use.",1390303199,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,Okay this doesn't look so bad now as it seems to only become a problem when a ScribuntoError occurs (I'm not sure how often this occurs on wiki's - I've only managed to replicate this locally). However it seems bizarre to me that the entire jQuery UI library would be loaded simply for error reporting...,1389142792,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+VisualEditor: Toolbar doesn't float properly in standalone demo,"It either snaps to the top left of the screen (instead of lining up with the surface), or it tries to render with 0 width (especially if you switch page)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389017880,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-tb2ge6debarxu3vvlo2k,task_description,resolved
+VisualEditor: Toolbar doesn't float properly in standalone demo,*** Bug 60183 has been marked as a duplicate of this bug. ***,1390864797,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tb2ge6debarxu3vvlo2k,task_subcomment,NA
+VisualEditor: Toolbar doesn't float properly in standalone demo,"Change 109489 merged by jenkins-bot:
+Attach container to DOM before initialising target in demo
+
+https://gerrit.wikimedia.org/r/109489",1390863488,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tb2ge6debarxu3vvlo2k,task_subcomment,NA
+VisualEditor: Toolbar doesn't float properly in standalone demo,"Change 109489 had a related patch set uploaded by Esanders:
+Attach container to DOM before initialising target in demo
+
+https://gerrit.wikimedia.org/r/109489",1390692956,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tb2ge6debarxu3vvlo2k,task_subcomment,NA
+VisualEditor: Toolbar doesn't float properly in standalone demo,"I can't find a cause using git-bisect.
+
+VisualEditor.git goes back to 20 Dec 2013, which already exhibits the problem.
+
+Bisecting in mediawiki/extensions/VisualEditor.git also led to nothing as the problem was never present there to begin with.
+
+I suspect the problem may be caused by us having removed a stylesheet in the repo split that is now in the ve-mw only, but should be under ve/ve instead.",1389820688,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tb2ge6debarxu3vvlo2k,task_subcomment,NA
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,"Intention:
+Rearrange the sections on a page
+
+Steps to Reproduce:
+1. Select the entire last section
+2. Cut (Command-X) the section
+3. Paste it elsewhere
+
+Actual Results:  
+The formatting for the section heading (not the formatting for the last line) remains at the end of the page.
+
+
+Expected Results:  
+The last line should either disappear entirely (be replaced by a slug) or be set to default/Paragraph styling
+
+Reproducible: Always
+
+Removing the blank section heading produced its own problems; look for the next bug report.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=Celebrity_branding&diff=589156664&oldid=583130311
+**See Also**:
+{T52100}
+{T57769}",1388853360,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_description,resolved
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,Verified in beta.,1427238826,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_subcomment,NA
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,"Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output <p> instead of <h#>
+
+[[https://gerrit.wikimedia.org/r/162310]]",1426893387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_subcomment,NA
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,"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",1424197332,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_subcomment,NA
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,"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",1411496974,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_subcomment,NA
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that","In edit mode
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Now add a reference to the page
+3,Add a bullet or numbered list
+4.Add references list from Insert>References list
+5.Save the page
+
+Observed Result:
+The references list appeared as a bulleted item or numbered item of the preceding list
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12662}",1388433240,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dztchev2qtofstunypcs,task_description,open
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that",The MW behavior described here is reported as a bug in T27939.,1664896979,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dztchev2qtofstunypcs,task_subcomment,NA
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that","I was able to reproduce this bug today and figured it was already reported earlier. My observation is pretty much the same as above.
+
+{F4452302}",1473459726,PHID-USER-vyft7xsn4ggkthnt52s2,PHID-TASK-dztchev2qtofstunypcs,task_subcomment,NA
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that","Eww, MW, why do we hate you so? This. This is why.",1394504318,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dztchev2qtofstunypcs,task_subcomment,NA
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that","Created attachment 14193
+In read mode
+
+**Attached**: {F12663}",1388433340,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-dztchev2qtofstunypcs,task_subcomment,NA
+VisualEditor: Any changes made to an article by other users since switching into VE aren't reflected when switching back to read mode,"Steps to reproduce:
+
+1.Open an article in read mode in two different tabs of same browser or in two different browsers.
+
+2.Now edit the page using one browser or tab
+
+3.Save the change
+
+4.Now open the same article with VE using another browser or tab
+
+5.Click on ""cancel""
+
+Observed Result:
+After step 4 the change made in step 2 by another browser or tab are correctly reflected in the edit mode .
+
+But after pressing cancel on step 5 , it has been observed that the readmode is still not showing the change done in step 2 unless user refreshes it.
+
+It will be better if both Edit mode and Read mode shows consistent content even if the change is made by other user/browser session
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1388174160,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-wqxkbe4urxqrr546bvml,task_description,open
+VisualEditor: document.activeElement can change unexpectedly while typing in VE editor,"**Author:** `jhall`
+
+**Description:**
+After observing some strange results from an automated Ruby test for cursor movement in the Visual Editor CE surface, we did some digging, and it appears that while a user is typing away happily and making and edit, the document.activeElement flip-flop several times.  
+
+I'm assuming this is unintentional behavior, thus the bug ticket.
+
+Repro steps:
+
+1)  Visit this page: https://test2.wikipedia.org/wiki/User:Selenium_user/cursor_test_page_chromedriver_bug
+2)  Click into VE editing mode.
+3)  With cursor placed immediately in front of the letter ""a"" in the word ""after"", press the right arrow key several times in succession. 
+4)  When your right-arrow-clicking brings you to the reference, the document.activeElement switches from ""ve-ce-documentNode ve-ce-branchNode noime"" to ""ve-ce-surface-paste""
+
+I'm assuming that when the user is typing in the ""editing box"", the document.activeElement should not be changing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57552",1388165580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dsrtx3tiu5iommxo6ovz,task_description,declined
+VisualEditor: document.activeElement can change unexpectedly while typing in VE editor,This is intentional. We move the selection the paste target so we can intercept copy events. Users should not care what document.activeElement is set to.,1701962577,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dsrtx3tiu5iommxo6ovz,task_subcomment,NA
+VisualEditor: document.activeElement can change unexpectedly while typing in VE editor,"**jhall** wrote:
+
+Java program used to generate the blow-by-blow in the previous attachment
+
+**Attached**: {F12401}",1388165960,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dsrtx3tiu5iommxo6ovz,task_subcomment,NA
+VisualEditor: document.activeElement can change unexpectedly while typing in VE editor,"**jhall** wrote:
+
+Blow-by-blow of document.activeElement as right arrow key is pressed many times in succession
+
+**Attached**: {F12400}",1388165821,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dsrtx3tiu5iommxo6ovz,task_subcomment,NA
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,"Steps to reproduce:
+
+1.Open a page with VE in Chrome
+2.Copy a hiero
+3.Open another page in FF
+4.Paste the hiero into it
+
+Observed Result:
+An empty template table appears.The resulting wikitext is:
+{|
+
+|
+{|
+
+|
+
+|}
+
+|}
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=26th_paste_ff&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388094480,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3e33c6y5allxgx2h75vj,task_description,resolved
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,WFM. Likely fixed at some point in the last two years.,1453424212,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3e33c6y5allxgx2h75vj,task_subcomment,NA
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,Is this still occurring?,1439321293,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3e33c6y5allxgx2h75vj,task_subcomment,NA
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,"While doing hiero copy-paste from  a page opened in FF to another page in FF, the following wikitext appears:
+
+{| class=""mw-hiero-table mw-hiero-outer"" dir=""ltr""
+
+|
+{| class=""mw-hiero-table""
+
+|
+
+|}
+
+|}",1388094678,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3e33c6y5allxgx2h75vj,task_subcomment,NA
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,"Created attachment 14174
+Screenshot in the edit mode
+
+**Attached**: {F12372}",1388094586,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-3e33c6y5allxgx2h75vj,task_subcomment,NA
+"VisualEditor:  Use colorful icons, or provide an option to use colorful icons / themes","Gryllida suggests that VisualEditor have colorful icons.  Alternatively, the existing monochrome icons could be kept, but editors could be given the option of choosing a Microsoft-style ""theme"" to change the appearance of the icons.  
+
+In addition to being fun, it is possible that other icon styles would improve accessibility for some users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1387824900,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-sk77bsakmg2v6bm4lawd,task_description,declined
+Left and right arrow keys jump to images if image has previously been viewed in Media Viewer,"I have enabled the experimental Media Viewer feature on Wikipedia, and when I click on an image, left and right scroll through the images on the page in full-window mode.
+
+However, when editing a page in Visual Editor, this keeps happening (that is, images from the article keep appearing in full-window mode) when I am trying to move around with the cursor keys.
+
+VisualEditor should disable this ""feature"", as it's obviously not wanted when editing a page!
+
+I use the Chromium browser.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Linux
+**Platform**: PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58266",1387747020,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-kz6xwcltn5xmr2ey75r7,task_description,resolved
+Left and right arrow keys jump to images if image has previously been viewed in Media Viewer,"Yeah, I don't see why this would still have been an issue on December 22, there should be no way to get this issue to happen anymore.
+
+If someone else sees this issue, speak up quick, but please be willing to discuss it with us relatively quickly, ideally on IRC, so we can nail it down.
+
+Thanks!",1389379350,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-kz6xwcltn5xmr2ey75r7,task_subcomment,NA
+Left and right arrow keys jump to images if image has previously been viewed in Media Viewer,"This should have been fixed in Media Viewer with bug 58266 being closed (the code was deployed to all wikis on 12 December), but if you're still encountering it that's not good.
+
+Does it still break in this manner? What happens if you refresh?",1388917874,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kz6xwcltn5xmr2ey75r7,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Intention:
+Move a section of a page by cutting it out of one place and pasting it into the right place.
+
+Steps to Reproduce:
+1.  Close an unwanted browser tab.
+2.  Select several paragraphs in VisualEditor.
+3.  Press Command-x to cut (not just copy) the material.
+4.  Notice that the just-closed browser window has reappeared.  (Command-z/Undo in Safari reopens a tab that you just closed.)
+
+
+
+Reproducible: Always
+
+I am unable to reproduce this in Firefox, presumably because selecting text within VisualEditor seems to clear (or otherwise make unavailable) the 'undo' buffer.  So even if VisualEditor is telling Firefox to undo something, Firefox believes that there there's nothing to undo.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57217",1387498860,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_description,resolved
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156776 merged by jenkins-bot:
+Remove unnecessary execCommand('undo') from onCut
+
+https://gerrit.wikimedia.org/r/156776",1409230172,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156776 had a related patch set uploaded by Esanders:
+Remove unnecessary execCommand('undo') from onCut
+
+https://gerrit.wikimedia.org/r/156776",1409227881,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156733 abandoned by Catrope:
+Avoid undo when processing a cut event.
+
+Reason:
+Duplicate of https://gerrit.wikimedia.org/r/156593
+
+https://gerrit.wikimedia.org/r/156733",1409183885,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156593 restored by Catrope:
+Avoid undo when processing a cut event.
+
+Reason:
+Whoops, obviously this isn't a duplicate of itself...
+
+https://gerrit.wikimedia.org/r/156593",1409183878,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156593 abandoned by Catrope:
+Avoid undo when processing a cut event.
+
+Reason:
+Duplicate of https://gerrit.wikimedia.org/r/156593
+
+https://gerrit.wikimedia.org/r/156593",1409183861,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156733 had a related patch set uploaded by Catrope:
+Avoid undo when processing a cut event.
+
+https://gerrit.wikimedia.org/r/156733",1409183761,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156593 had a related patch set uploaded by Catrope:
+Avoid undo when processing a cut event.
+
+https://gerrit.wikimedia.org/r/156593",1409165641,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"**aditya** wrote:
+
+Pushed a patch to gerrit. 
+
+https://gerrit.wikimedia.org/r/#/c/156593/",1409164825,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"**aditya** wrote:
+
+Patch to prevent undo on cut
+
+Here's a patch that avoids the 'undo' execCommand and fixes the issue for me in Chromium 36.0.1985.125 (Linux).
+
+I'm assuming that the timeout was originally intended to let the code in that block be safely executed only after the browser manipulated (deleted) the selection. It appears that this no longer works and the code is processed before the text is actually deleted.
+
+Therefore this change uses preventDefault() to not let the browser do it's thing, and directly handles the entire removal with a transaction.
+
+This is my first patch to VE, sorry if I made any obvious mistakes. :)
+
+**Attached**: {F12701}",1409160577,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,Ick. This feels like a pretty poor browser bug here…,1408642368,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+"Disable ""Beta"" suffixes on tabs for VisualEditor opt-in wikis","On opt-in wikis, users already have to explicitly choose to be able to use VisualEditor, and they get a warning the first time they do so. Adding beta suffixes all over the UI is a leftover from opt-out status and only appropriate in wikis that are opt-out, and where communities explicitly request such notices to be present.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387305900,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-vfujufijqzs5z2vprlzj,task_description,resolved
+"Disable ""Beta"" suffixes on tabs for VisualEditor opt-in wikis","Change 112590 merged by jenkins-bot:
+Disable 'beta' label in tab for the VE opt-in wiki (enwiki)
+
+[[https://gerrit.wikimedia.org/r/112590]]",1426001948,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vfujufijqzs5z2vprlzj,task_subcomment,NA
+"Disable ""Beta"" suffixes on tabs for VisualEditor opt-in wikis","Change 112590 had a related patch set uploaded (by Jforrester):
+Disable 'beta' label in tab for the VE opt-in wiki (enwiki)
+
+[[https://gerrit.wikimedia.org/r/112590]]
+",1425512003,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vfujufijqzs5z2vprlzj,task_subcomment,NA
+"Disable ""Beta"" suffixes on tabs for VisualEditor opt-in wikis","Change 112590 had a related patch set uploaded by Jforrester:
+Disable 'beta' label in tab for the VE opt-in wiki (enwiki)
+
+https://gerrit.wikimedia.org/r/112590",1392069493,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vfujufijqzs5z2vprlzj,task_subcomment,NA
+VisualEditor: Outline widget in booklet layout responds to mouse up events even if they started elsewhere,"These should probably only respond to click events although it seems they currently support the click and drag functionality of a drop down box. If you are editing a textarea in the right hand panel and you click and drag from right to left to select all the text you will often end up with your mouse over the outline widget. Releasing your mouse here will cause you to jump to a random page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387298340,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-it6zs5tx5bzoz3374bjq,task_description,resolved
+VisualEditor: Outline widget in booklet layout responds to mouse up events even if they started elsewhere,Fixed by https://gerrit.wikimedia.org/r/#/c/133284/,1416325755,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-it6zs5tx5bzoz3374bjq,task_subcomment,NA
+VisualEditor: Links should do pre-annotations in both directions (not just down-page but also up-page),"When editing Wikipedia, I have repeatedly run into the following issue: 
+
+The article contains a link and I want to change the beginning of the link text (not the link's target), usually because it is upper case and I want it lower case. So I use VisualEditor to delete the first letter of the link and replace it with its lower case version. The result is unexpected: the first letter is not marked up as part of the link, but this is very hard to see.
+
+The source code is transformed from [[Link]] to l[[Link|ink]]. Links like the latter are almost never contained in human-created wikitext.
+
+Suggestion: link text should be ""magnetic"", so that changes at either end will automatically inherit the link markup.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1387231020,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-atsl3fekbsgfq2jon2lc,task_description,resolved
+VisualEditor: Links should do pre-annotations in both directions (not just down-page but also up-page),"With the new style of link editing, the problem I described above has gone away. So this can task can be closed.",1517159814,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-atsl3fekbsgfq2jon2lc,task_subcomment,NA
+VisualEditor: Links should do pre-annotations in both directions (not just down-page but also up-page),"@AxelBoldt, the style of link editing has been changed so that the whole link is highlighted.  This makes it easier to tell when you're addding something to the link.  Do you still think that this would be desirable?",1517094679,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-atsl3fekbsgfq2jon2lc,task_subcomment,NA
+Flow: support VisualEditor VE editing of header & topics (tracking),"VisualEditor is currently disabled as an editor in Flow:
+  $wgFlowEditorList = array( 'none' );  // EXPERIMENTAL prepend 'visualeditor'
+
+when we re-enable it, the VE bugs we discovered will probably still apply.
+
+The WMF core features team plans the ""VisualEditor integration"" story in  Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/28
+
+--------------------------
+**Version**: master
+**Severity**: minor",1386884340,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-whjfcbb2dp7dyl7hx24q,task_description,resolved
+Flow: support VisualEditor VE editing of header & topics (tracking),"**bingle-admin** wrote:
+
+The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/619, but people from the community are welcome to contribute here and in Gerrit.",1386884545,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-whjfcbb2dp7dyl7hx24q,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"After pasting a block of <syntaxhighlight> in to a target surface, I had to save and then reload the page before the syntax highlighting styling was applied. 
+
+https://www.mediawiki.org/w/index.php?title=User:TheDJ/sandbox&oldid=841358
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67515",1386843900,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_description,resolved
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"Change 311839 merged by jenkins-bot:
+VE: Ensure ext.pygments module gets loaded when a user adds a syntax highlight node
+
+[[https://gerrit.wikimedia.org/r/311839]]",1474412031,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"Change 311839 had a related patch set uploaded (by Alex Monk):
+VE: Ensure ext.pygments module gets loaded when a user adds a syntax highlight node
+
+[[https://gerrit.wikimedia.org/r/311839]]
+",1474410284,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,Still an issue.,1435184824,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"Change 214078 merged by jenkins-bot:
+Add VisualEditor support
+
+[[https://gerrit.wikimedia.org/r/214078]]",1435183387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"Change 214078 had a related patch set uploaded (by Jforrester):
+Add VE support for syntax highlighting
+
+[[https://gerrit.wikimedia.org/r/214078]]
+",1432909767,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,related: https://gerrit.wikimedia.org/r/#/c/162123/,1417604677,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"With the dependency fixed, this just needs VisualEditor loading the appropriate modules defined by SyntaxHighlight (one for each language) at appropriate times.",1399233172,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,Confirmed.,1393530933,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Templated tables seem to fail in copy paste,"https://www.mediawiki.org/wiki/Manual:Code?veaction=edit
+
+Copy one of the tables there. You get an error in fixupInsertion
+
+[Error] TypeError: 'undefined' is not an object (evaluating 'source.clone')
+	copy (load.php, line 94)
+	getClonedElement (load.php, line 39)
+	fixupInsertion (load.php, line 120)
+	fixupInsertion (load.php, line 119)
+	newFromDocumentInsertion (load.php, line 71)
+	afterPaste (load.php, line 299)
+	(anonymous function) (load.php, line 294)
+	proxy (load.php, line 10)
+
+This does not seem related to bug 58318. The table also doesn't render as it should in the original surface, with slugs above and below it inside the table. Possibly caused by the usage of templates for row construction.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386843540,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-wus5sgrv22omy4zu47lx,task_description,resolved
+VisualEditor: Templated tables seem to fail in copy paste,Fixed by gerrit 140439.,1404172527,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wus5sgrv22omy4zu47lx,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted","I'm not sure if this was done on purpose, but when selecting text containing some formatting in some or all of the selected text (e.g. part of a link and some text after it, or part of a bolded string) the toolbar shows the ""Clear formatting"" button highlighted (similarly to how the ""Bold"" icon is highlighted when selecting bolded text).
+
+The toolbar is supposed to reflect current state of selected text. Showing the ""Clear formatting"" button already activated seems like an impossible state (it would theoretically mean some hypothetical ""clear"" annotation is applied to the selected text, which is incorrect. The only case in which that would technically be correct is if you apply text that is already cleared of formatting).
+
+This highlighting for the ""Clear formatting"" button is confusing from a UX point of view. I would associate it with how ""bold"" is highlighted when bolding is applied.
+
+When encountering this strange UX behaviour earlier today, it took me a while to figure out what it is supposed to mean (longer than it should for an intuitive editor). I don't think this is because I'm familiar with VisualEditor's previous state, but more in general.
+
+I think the correct approach would be to never highlight the clear formatting button in the toolbar, and have it be an ""apply"" button, you select text, and then activate (not deactivate) ""clear formatting"".
+
+This concept also exists in other popular editors.
+
+Alternatively, though that would be a new concept for people to learn, perhaps change the icon to something that means the opposite of no formatting, so that it being turned on for selected text, and being able deactivate it, like it currently does, actually makes sense as an action take.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386821400,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_description,resolved
+"VisualEditor: ""Clear formatting"" should never be highlighted",That bit is now fixed too AFAICT.,1402332266,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted","This now happens again. If you:
+
+1. Select an image
+2. Click Bold. This bolds the caption (this is a separate bug)
+3. Select something else, then select the image again (otherwise the clear formatting button doesn't get enabled)
+3. Click Clear Formatting.
+4. Observe that Clear Formatting is now depressed.
+
+Obviously there are lots of other weird things going on, but it seems that the only way that Clear Formatting button manages to not be depressed is by assuming that it will always successfully clear all formatting and therefore be disabled next.",1395274339,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted",This was done in the changes to the toolbar.,1390025219,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted","Created attachment 14069
+When using the link inspector, ""Link"" and ""Clear formatting"" are active
+
+**Attached**: {F12008}",1386821596,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted","Created attachment 14068
+Selecting text spanning across a link shows ""Clear formatting"" active
+
+**Attached**: {F12007}",1386821531,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+Flow: Create a separate preference for the Visual Editor (opt-in/out) for Flow pages,"VisualEditor is currently not usable or well-tested in Flow. (Per feedback at http://ee-flow.wmflabs.org/w/index.php?title=Talk:Flow_bugs&workflow=050a7c69647ff00fc8b1fa163e68c4ac&action=view)
+
+Please create a separate preference (opt-in/out) for the VisualEditor within Flow pages, so that editors who are happily using/testing VE, will still be able to use Flow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386101640,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-yzw2lh4x4ig5iyfc2jnv,task_description,invalid
+Flow: Create a separate preference for the Visual Editor (opt-in/out) for Flow pages,Experimental VE has been pulled from Flow for awhile - should be revisited once we properly reimplement VE,1409847331,PHID-USER-kms5nmb5gvqzcdep3cnl,PHID-TASK-yzw2lh4x4ig5iyfc2jnv,task_subcomment,NA
+Flow: Create a separate preference for the Visual Editor (opt-in/out) for Flow pages,"**bingle-admin** wrote:
+
+The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/573, but people from the community are welcome to contribute here and in Gerrit.",1386102270,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yzw2lh4x4ig5iyfc2jnv,task_subcomment,NA
+VisualEditor: Add ability to edit local language links (non-Wikidata ones),"Though bug 52105 covers Wikidata-bourne language link editing, there are cases where local language link editing is still needed:
+
+* for Wikimedia wikis not (yet) hooked into Wikidata;
+* for Wikimedia wikis which cannot (yet) be hooked into Wikidata (e.g. [[en:Maggie Simpson]] vs. [[de:Die Simpsons (Familie)#Maggie Simpson]]); and 
+* for MediaWiki installs without a Wikibase server (almost all third party users).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52105",1386087840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5om5dvvhar7j76c2fnz,task_description,open
+"Global, better URL to citation conversion functionality","**Author:** `vladjohn2013`
+
+**Description:**
+Global, better URL to citation conversion functionality
+
+Suppose, in Wikipedia, all that needed to be done to generate a perfect citation was to provide a URL? That would be a tremendous step toward getting a much higher percentage of text in Wikipedia articles to be supported by inline citations.
+
+There are already expanders (for the English Wikipedia, at least) that will convert an ISBN, DOI, or PMID, supplied by an editor, into a full, correct citation (footnote). These are in the process of being incorporated into the reference dialog of the VisualEditor extension, making it almost trivial (two clicks, paste, two clicks) to insert a reference.
+
+For web pages, however, the existing functionality seems to be limited to a Firefox add-on. Its limits, besides the obvious requirement to use that browser (and to install the add-on), include an inability to extract the author and date from even the most standard pages (e.g., New York Times), and the lack of integration with MediaWiki.
+
+For a similar approach, using a different plug-in/program, see this Wikipedia page about Zotero.
+
+A full URL-to-citation engine would use the existing Cite4Wiki (Firefox add-on) code, perhaps, plus (unless these exist elsewhere) source-specific parameter specifications. For example, the NYT uses ""<meta name=""author"" content=""NICK BILTON"" />"" for its author information; that format would be known by the engine (via a specifications database). Each Wikipedia community would be responsible for coding these (except for a small starter set, as examples), in the way that communities are responsible for TemplateData for the new VisualEditor extension.
+
+(Project idea suggested by John Broughton.)
+
+URL:https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Global.2C_better_URL_to_citation_conversion_functionality
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385913900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_description,resolved
+"Global, better URL to citation conversion functionality","Resolving, then. Check #Citoid for details.",1423649593,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality",This is being addressed by [[ https://www.mediawiki.org/wiki/Citoid | Citoid ]] ,1423614294,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","John- thank you for the links, they were very helpful!
+
+The project for an engine to provide citations to VE was approved for the May 2014 round for OPW. Extension is tentatively called https://www.mediawiki.org/wiki/Extension:CiteURLEngine although I'm not set on the name. 
+
+Since you mention NYTimes, they're proving to be quite problematic because they treat scrapers as logged out users (so scrapers get redirected to a log-in page), and they've also disallowed caching by Google so you can't use the cached page as a back-up solution. If anyone has any ideas let me know!",1398180001,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","Marielle - I'd be happy to work with you on nailing down the specs, and I'd also be happy to assist with QA (testing). If you do decide to create a bot to clean up naked urls in references/citations, I can also assist you with getting permission to run the bot at en.wikipedia.org (per [[WP:BOTREQ]]). 
+
+However, I can't offer technical assistance - it's been far too many years since I did programming, in languages that aren't particularly useful today.
+
+Finally, I note that the list of existing tools, at https://www.mediawiki.org/wiki/Improving_URL_citations_on_WikiMedia_(OPW_Project) , omits a significant number of things.  
+
+See https://en.wikipedia.org/wiki/Help:Citation_tools for a more comprehensive list, and also see https://en.wikipedia.org/wiki/Wikipedia:EIW#Citetools .",1394664371,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","Hi,
+
+This project was listed as a possible project for the FOSS Outreach Program for Women and I'd very much like to work on it.
+
+I've written a very rough proposal here: https://www.mediawiki.org/wiki/Improving_URL_citations_on_WikiMedia_(OPW_Project)
+
+However, I would need a mentor to help nail down the specs of the project and then oversee it. I don't to step on anyone's toes regarding the project Erik mentioned (a WMF web service to provide citations to both the visual editor and the wikitext editor)- it sounds like some of what I proposed might replicate that. I'd be happy to work on this from that angle as well but I'm not sure what other people have done already.
+
+Is there anyone on this thread that could mentor such a project? Thanks!
+
+-Marielle",1394553539,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","We are, in fact, investigating this in the context of VisualEditor, specifically the possibility of setting up a WMF web service for this that can be used by VisualEditor and wikitext editors alike to quickly generate citations. It'd be ideal to be able to share code with Zotero which has a comprehensive suite of URL-to-citation translators already.",1387360625,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","**vladjohn2013** wrote:
+
+This proposal has been listed at https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects and we are filing a report to gather community feedback and share updates.",1385913933,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","Intention:
+Add a category to a page
+
+Steps to Reproduce:
+1. Open the page in VisualEditor and choose the categories tool.
+2. Type the full name of the category, including the namespace:  Category:Example
+
+
+Actual Results:  
+VisualEditor adds a non-existent, malformed category named [[Category:Category:Example]].
+
+Expected Results:  
+That VisualEditor would recognize that ""Category:Example"" already contained the namespace, and thus omit the duplication.  Ideally, at non-English wikis, it would recognize and remove both the local name for the namespace and the English name, since both are typically valid (e.g., strip out both ""Kategorie"" and ""Category"" at the German Wikipedia).
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385856300,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-f7abfvzj2vf4lqry7phg,task_description,open
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","Also there's the problem of either (a) only doing this hack for English, or (b) having to hold in VE a copy of all of the translations of Category:, and know which one to remove when (removing Catégorie: on French, but not on English, and so on).",1386361041,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","(In reply to comment #4)
+> Do any [[Category:Category:Foo]] pages exist?  I haven't seen one.
+
+On all ten million MediaWiki wikis out there? Quite probably…
+
+J.",1386360951,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in",Do any [[Category:Category:Foo]] pages exist?  I haven't seen one.,1386359880,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","There is [[Category:Category theory]], it might be worth checking as a corner case.",1386285245,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","What to do when there's a category called ""Category:Foo"" and another called ""Foo"". Do we strip or not?",1386041139,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","[new feature or ""nice-to-have"" => severity=enhancement]",1385979158,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+VisualEditor:  Wikitext warning needs to be updated to refer to switching to wikitext editor without losing unsaved changes,"Intention:
+The wikitext warning says:
+
+""Click ""Edit source"" to edit the page in wikitext mode – unsaved changes will be lost.""
+
+This need to be changed to reference the new ability to switch to the source editor without losing unsaved changes, at least (currently) for non-Firefox users.
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57699",1385604180,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-3pikq7qftwx2jwebgh76,task_description,resolved
+VisualEditor:  Wikitext warning needs to be updated to refer to switching to wikitext editor without losing unsaved changes,"Change 133637 merged by jenkins-bot:
+Update wikitext-warning to refer to 'Switch to source editing'
+
+https://gerrit.wikimedia.org/r/133637",1400523894,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3pikq7qftwx2jwebgh76,task_subcomment,NA
+VisualEditor:  Wikitext warning needs to be updated to refer to switching to wikitext editor without losing unsaved changes,I uploaded Gerrit change 133637 for this,1400200917,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-3pikq7qftwx2jwebgh76,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"Intention:
+When you open VisualEditor for the first time, you get a message that says you can switch to wikitext, but that unsaved changes will be lost:
+
+""You can keep using the wikitext editor by clicking the ""Edit source"" tab instead – unsaved changes will be lost.""
+
+This is not always true, since (currently for non-Firefox users) it is possible to switch to wikitext using the new menu item without losing any changes.
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57462
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57700",1385604120,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ookmj2wjll2ptshhb67g,task_description,resolved
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"Change 133639 merged by jenkins-bot:
+Update beta warning to refer to 'Switch to source editing'
+
+https://gerrit.wikimedia.org/r/133639",1400523863,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,I uploaded Gerrit change 133639 for this,1400200902,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,The switch option appears to be currently working for IPs as well.,1399462468,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"(Actually, it's still broken for IPs.)",1393936033,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"(BTW the switch option is now working with any browser AFAIK, or at least it is with FF.)",1389085568,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"Any message of the interface can be changed locally in the MediaWiki namespace, so anybody can fix that. But the message only refers to the Edit source main tab, so it is always true that if you click that your changes will be lost.",1389085230,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor: Features not yet available in a certain browser (but working in others) should be grayed out/unselectable,"Pretty much what the title says.
+James thinks this might eventually be done at some point, so this is a reminder.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385499300,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-25ulackf33wigk7bvnyg,task_description,invalid
+VisualEditor: Make jquery.byteLimit more user friendly and cleaner in usage,"Currently:
+
+* byteLimit() will internally do all kinds of event binding to get notice of changes.
+* We have our own 'change' callback for InputWidget elements.
+* in mw.ViewPageTarget we use our 'change' event, our own getValue, manually run it through byteLength (not byteLimit), in order to get the current length that we assume byteLimit got to as well.
+* When the length is exceeded by user input, byteLImit internally will start chopping off characters (or rather, cancel user events after it hit the limit, and falls back to chopping off characters until it fits again).
+
+Problems:
+* Mimics the change event.
+* Duplicates logic for byteLength outside byteLimit, this will fail if the logic changes, and already fails if the byteLimit has a filter callback.
+
+Ideally: byteLimit (standalone)
+* Its own on('change') - so we don't have to mimic it
+* Ability to retrieve byte length as perceived by byteLimit - so we don't have to reverse engineer it
+* Option to disable the chopping off (instead, more like Twitter where the underlying user interface element will allow new characters, but it will have an event like 'length-exceeded' and 'length-satisfied' or 'length-recovered' so we dan display a nicer user interface (e.g. make the number negative and red)
+
+
+or:
+
+Ideally: byteLimit (utility mixin)
+* Option to feed it change events instead of having it listen on its own.
+* Get back from each event – the current state (length exceeded or not, and what the length is, having taken the filter in account).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385472600,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cptw6scnn4zompkjhwyq,task_description,declined
+VisualEditor: Make jquery.byteLimit more user friendly and cleaner in usage,"Code has improved since then and is now more abstract and re-usable, which VE already makes use of in ve.ui.MWSaveDialog.
+
+Re-use of the additional abstraction layer ""byteLimit""  on top of ""byteLength"" no longer makes sense as it seems undesirable from a UX perspective to artificially limit how much one can type. Rather, VE allows the user to type more while drafting the edit summary and then shows visually when the limit is exceeded and disallows submission until fixed.
+
+This is much better than hard limiting the size of the input field which makes editing of the edit summary much harder due to not having any wiggle room to move things around or copy/pasting etc to tune it.",1554174106,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cptw6scnn4zompkjhwyq,task_subcomment,NA
+VisualEditor: Fire a hook before the page is saved,"Some Wikipedias have hooks for the source editor that process the wikitext before it is saved. The only thing to currently do this for the Visual Editor seems to be to hook in the 'wikipage.content' event and do an API edit that processes the text as intended.
+
+Instead, the visual editor should offer a different event, such as visualeditor.beforesave, that would allow such processing to take place when saving the content.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385385360,PHID-USER-2trxtywh5ma4onasf4kq,PHID-TASK-dakuttxcpl6bkvpemnmx,task_description,declined
+VisualEditor: Fire a hook before the page is saved,"Re-evaluating – if you want a client-side hook, this is a WONTFIX (both for specific reasons to this bug to do with catastrophic performance hits, and also because events are not a sane way to go).
+
+If you want a VE-specific server-side (PHP) hook on wikitext save, we could do that more reasonably (as MediaWiki's too far down that road to pull back).",1397675923,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dakuttxcpl6bkvpemnmx,task_subcomment,NA
+VisualEditor: Fire a hook before the page is saved,"Ideally, there would be an event for each of these stages :) 
+
+Realistically, in order to reuse existing code, the best time would probably be when the Wikitext is ready to be saved (since that would be the equivalent for pressing the ""Save"" button). Of course, the callback needs to be able to give the modified wikitext back to VE.",1385395263,PHID-USER-2trxtywh5ma4onasf4kq,PHID-TASK-dakuttxcpl6bkvpemnmx,task_subcomment,NA
+VisualEditor: Fire a hook before the page is saved,"What stage of the save do you want? 
+
+* HTML is ready to be saved
+* HTML is converted to wikitext
+* Wikitext is back from Parsoid and is ready to be saved
+* VE just sent the wikitext to MW API
+* VE just got the confirmation token back from MW API
+* …",1385394655,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dakuttxcpl6bkvpemnmx,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","When a user clicks on Switch to source editing option from the settings drop down it tells user that switching to source editing will keep the changes made in the document.But if a user attempts to switch from the tab it does not retain those changes.This seemed confusing to me because when user uses the ""switch to source editing"" , the ""Edit Source"" tab is selected ,indicating the same destination for both action.
+
+If a user can switch to source editing in multiple ways, i think it is better both ways have similar mechanism of handling the changes to have uniform experience.
+Specially when switching from tab is one click away compared to the ""[]switch to source editing"" option.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57699
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42141",1385165520,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rwqvw5qcvrnogk334awp,task_description,resolved
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab",Verified the fix in production,1405028027,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab",Verified the fix in test2,1404769383,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab",Verified the fix in Betalabs,1404243442,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Change 143203 merged by jenkins-bot:
+Don't offer to retain changes when switching to wikitext editor by tab if no changes have been made
+
+https://gerrit.wikimedia.org/r/143203",1404176682,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Change 143203 had a related patch set uploaded by Alex Monk:
+Don't offer to retain changes when switching to wikitext editor by tab if no changes have been made.
+
+https://gerrit.wikimedia.org/r/143203",1404172800,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Change 142064 merged by jenkins-bot:
+Offer to retain changes when switching to the wikitext editor
+
+https://gerrit.wikimedia.org/r/142064",1404171633,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Change 142064 had a related patch set uploaded by Alex Monk:
+Offer to retain changes when switching to the wikitext editor
+
+https://gerrit.wikimedia.org/r/142064",1403727961,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab",I personally think that this bug report is a duplicate of bug 42141.,1391403189,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","This is possible, but would be ugly, because we'd need to replace the existing two-choice option (switch or don't switch) with a custom three-choice one (switch and keep changes, switch without changes, don't switch)… Maybe.",1385394909,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","[Removing ""[Suggestion]"" from summary; setting severity field to ""enhancement"" instead]",1385226568,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Created attachment 13890
+Inside Edit Source tab
+
+**Attached**: {F12699}",1385165849,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Repro:
+
+1. Create a page with text below:
+
+<math>
+\begin{matrix}
+x & y \\
+z & v
+\end{matrix}
+</math>
+
+2. Default rendering, in PHP parser and Parsoid (VE initial state):
+
+x y
+z v
+
+3. VE edit this matrix, change v to uv.
+
+4. Edited block becomes:
+
+x amp; y
+z amp; uv
+
+(After saving it works fine)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54577",1385141220,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-pvooclgjtrwgebkle3fj,task_description,resolved
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)",Thanks Bartosz!,1405470041,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Should be fixed.
+
+Like in wikitext, it will now be impossible to input '</tag>' in the inspector in VisualEditor: it will be converted to '&lt;/tag>' when the inspector is closed.",1405463766,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Change 144158 merged by jenkins-bot:
+ve.ce.MWExtensionNode: Don't escape content of wikitext tags on preview
+
+https://gerrit.wikimedia.org/r/144158",1405462152,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Change 144157 merged by jenkins-bot:
+ve.ui.MWExtensionInspector: Prevent from setting impossible content
+
+https://gerrit.wikimedia.org/r/144157",1405462148,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Change 144158 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ce.MWExtensionNode: Don't escape content of wikitext tags on preview
+
+https://gerrit.wikimedia.org/r/144158",1404490445,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Change 144157 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ui.MWExtensionInspector: Prevent from setting impossible content
+
+https://gerrit.wikimedia.org/r/144157",1404490440,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Just for ""fun"", some informative examples that show what happens when you try too hard with {{#tag:}}. Two of these actually cause UNIQ markers to appear in output, which is rather bad in general. The behavior may differ depending on the tag used.
+
+
+<syntaxhighlight lang=php>$a;</syntaxhighlight>
+
+<syntaxhighlight lang=php></syntaxhighlight></syntaxhighlight>
+
+<syntaxhighlight lang=php>&lt;/syntaxhighlight></syntaxhighlight>
+
+{{#tag:syntaxhighlight|</syntaxhighlight>|lang=php}}
+
+<syntaxhighlight lang=php><syntaxhighlight lang=php>$a;</syntaxhighlight></syntaxhighlight>
+
+{{#tag:syntaxhighlight|<syntaxhighlight lang=php>$a;</syntaxhighlight>|lang=php}}
+
+{{#tag:syntaxhighlight|&lt;syntaxhighlight lang=php>$a;</syntaxhighlight>|lang=php}}
+
+{{#tag:syntaxhighlight|<nowiki><syntaxhighlight lang=php>$a;</syntaxhighlight></nowiki>|lang=php}}",1404487657,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Basically, ve.ce.MWExtensionNode.prototype.generateContents builds an XML element object for given tag name (for example 'math'), given attributes (none in this case) and given contents (for example 'a < b'), and then serializes it to a string to ensure that everything is correctly escaped.
+
+The problem is that MediaWiki XML-like tags don't expect their contents to be escaped. Serializing such a node generates ""<math>a &lt; b</math>"", while wikitext expects ""<math>a < b</math>"".
+
+(An interesting corollary is that a MediaWiki XML-like tag 'foo' may not contain the string '</foo>' in any form nor encoded in any way, unless the code of the extension handling the tag specifically parses nested <nowiki/> tags or something. You can cheat – {{#tag:foo|</foo>}} – but then you still can't include the string '<foo></foo>' because it gets double-parsed.)
+
+(Fun fact: the above behavior is the reason why <source/> was renamed to <syntaxhighlight/> some years ago.)
+
+We should not escape the contents at all and instead do something clever if the input text contains '</foo>'. VE and wikitext are both designed to never disallow the user from doing stupid things, so I'm not sure what can be done if we don't just prevent the user from saving that. Maybe selectively HTML-escape /<\/\s*foo\s*>/ when closing the inspector?",1404487482,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)",*** Bug 60332 has been marked as a duplicate of this bug. ***,1404486826,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","This problem is actually common for everything that uses MWExtensionNode. The problem is that ve.ce.MWExtensionNode.prototype.generateContents makes some bold assumptions about wikitext syntax that are not true.
+
+The fix from bug 54577 didn't actually fix much, it just changed what the problem is.",1404486795,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)",*** Bug 60113 has been marked as a duplicate of this bug. ***,1404431099,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+VisualEditor: <visualeditor-dialog-beta-welcome-content> does not mention new switch to wikicode feature,"**Author:** `raincity471`
+
+**Description:**
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1385125920,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ccqdyfu36me32igrajec,task_description,declined
+VisualEditor: <visualeditor-dialog-beta-welcome-content> does not mention new switch to wikicode feature,"I'm not sure it's worth trying to explain this minor and not-hugely-useful feature. I think it would just add to the confusion.
+
+Remember that this is the first ever interface users will see when using VisualEditor – it's important that we don't over-load them with too much information, or that we drown out the important information for them to learn by hiding it amongst a sea of less-important and un-important information.
+
+WONTFIXing.",1385136050,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ccqdyfu36me32igrajec,task_subcomment,NA
+VisualEditor: <visualeditor-dialog-beta-welcome-content> does not mention new switch to wikicode feature,"**raincity471** wrote:
+
+Screenshot of the intro screen with affected sentence highlighted
+
+Outdated sentence circled in red.
+Screenshot saved ‎22 ‎November ‎2013, ‏‎13:37:15 (UTC) after a bit of editing in the GIMP. VE beta 0.1.0 running MediaWiki 1.23wmf4 (c066033), Firefox 25.0 in private mode (so no copyright problems with addons).
+Firefox 25 is licensed under the Mozilla Public License 2.0. VisualEditor is licensed under the Massachusetts Institute of Technology license. MediaWiki is licensed under the GNU GPL version 2 or later.
+
+**Attached**: {F12597}",1385128202,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ccqdyfu36me32igrajec,task_subcomment,NA
+VisualEditor: <visualeditor-dialog-beta-welcome-content> does not mention new switch to wikicode feature,"**raincity471** wrote:
+
+A new feature has been added to VisualEditor which allows editors to switch from VE to wikitext editing without losing their changes (see Bug 50687). The VE intro dialogue (shown to users the first time they open VE) still says you may switch from VE to ""edit source"" using the tab at the top and that changes will be lost. The new feature should be mentioned, maybe something like:
+
+""You can keep using the wikitext editor by clicking the options button (three horizontal lines next to the cancel button) in the top-right corner and then ""switch to source editing"". Unsaved changes will not be lost.""",1385126471,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ccqdyfu36me32igrajec,task_subcomment,NA
+VisualEditor: Adjacent floating tables are offset by vertical space because of intervening <span>,"Reproducible: Always
+
+Fram reports that when you try to VEdit pages like
+https://en.wikipedia.org/wiki/List_of_top_100_Major_League_Baseball_strikeout_pitchers
+https://en.wikipedia.org/wiki/List_of_Major_League_Baseball_players_with_2,500_games_played
+or https://en.wikipedia.org/wiki/List_of_top_300_Major_League_Baseball_home_run_hitters ,
+what you get is not exactly what you saw :) (see the tables and the following sections.)
+
+Ssastry furtherly diagnosticated: ""Looks like some VE-clientside rendering issues with empty spans between multiple floating tables.""
+Doesn't look specific to a browser or skin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65249",1385068980,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-upqk35oo5h6sa55ff7w5,task_description,duplicate
+Enable VisualEditor on svwiktionary,"We would like to have VisualEditor enabled on some part of svwiktionary.
+
+Suggested namespace: User namespace.
+
+Rationale:
+
+We're doing a proof-reading project[1] where we'll need to do lots of style edits (mainly update italics and bold).
+
+The idea is to extract useful information from the dictionary/thesaurus ""Ord för ord""[2] and create new entries and improve existing ones using the information.
+
+
+[1] https://sv.wiktionary.org/wiki/Wiktionary:Projekt/Ord_f%C3%B6r_ord
+[2] http://runeberg.org/ordforord/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1385045940,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-xiyv4jixkvbxe2phirwu,task_description,resolved
+Enable VisualEditor on svwiktionary,This should now be fixed; sorry for the mis-configuration.,1386126509,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Change 98871 merged by jenkins-bot:
+Disable VisualEditor in content namespaces on svwiktionary
+
+https://gerrit.wikimedia.org/r/98871",1386116304,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Change 98871 had a related patch set uploaded by Jforrester:
+Disable VisualEditor in content namespaces on svwiktionary
+
+https://gerrit.wikimedia.org/r/98871",1386102272,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"(In reply to comment #9)
+> I noticed that it's enabled in the main namespace too, but that doesn't make
+> sense. We use lots of templates and very well-defined lists that just don't
+> work well with VisualEditor.
+> 
+> Can you please disable it for the main namespace?
+
+Hmm, that's odd; it's configured for just the User namespace, per this bug – will investigate why it's working elsewhere too.
+
+> If possible, you could enable it for the project namespace instead (but not
+> on pages with __NEWSECTIONLINK__).
+
+Not sanely possible - we don't enable VisualEditor on pages which are signed, as that's what Flow is for, and too much of the project namespace is randomly signed (even with an expensive check for __NEWSECTIONLINK__), sorry. :-(",1386087168,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"I noticed that it's enabled in the main namespace too, but that doesn't make sense. We use lots of templates and very well-defined lists that just don't work well with VisualEditor.
+
+Can you please disable it for the main namespace?
+
+If possible, you could enable it for the project namespace instead (but not on pages with __NEWSECTIONLINK__).",1386081623,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"This is now live - you can opt in to test VisualEditor using the Beta Features link in your personal tools at the top of the page, or through the Preferences link in the ""Beta Features"" tab.
+
+If there are any issues, please shout!",1386022164,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Change 97711 merged by jenkins-bot:
+Enable VisualEditor as opt-in on svwiktionary
+
+https://gerrit.wikimedia.org/r/97711",1386021544,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Change 97711 had a related patch set uploaded by Jforrester:
+Enable VisualEditor as opt-in on svwikitionary
+
+https://gerrit.wikimedia.org/r/97711",1385463709,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Sorry for the slow reply – we can do this if wanted.
+
+Just user namespace is entirely possible if that's what you want.
+
+Will do a patch now.",1385463048,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,I was just providing info about what's written in public; James and the VE development team has the final word and is free to change plans. :),1385462658,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"I was thinking that it might be possible to enable it on svwiktionary earlier, since I thought it would be low-risk to enable it for the user namespace only, not adding any new requirements.
+
+Anyway, I take that as a ""no"" in the short-term (this year).",1385402559,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"https://www.mediawiki.org/wiki/VisualEditor#Timeline says ""VisualEditor may be offered to users at non-Wikipedia projects, such as Commons or Wiktionary, after deployment to the Wikipedias has completed. No timeline has been set for this.""",1385396895,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Thank you for your interest in Visual Editor.
+
+[ Adding James Forrester and Trevor Pascal as CC to get feedback on this matter. ]",1385062535,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+VisualEditor: Long links are not shown in full in the link searcher,"When a long string (24 characters or more) gets added in the link tool (a typical long URL, or a just a long article title), the external and internal link options get shortened with ""..."" in the middle. This can make it hard to know whether you put in the right string or not, and there doesn't seem to be much downside to displaying the full link targets for at least moderately longer strings.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69574",1384795860,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-7fbhbqnohmq5xaiuz462,task_description,open
+VisualEditor: Long links are not shown in full in the link searcher,"(In reply to comment #0)
+> When a long string (24 characters or more) gets added in the link tool (a
+> typical long URL, or a just a long article title), the external and internal
+> link options get shortened with ""..."" in the middle. This can make it hard to
+> know whether you put in the right string or not, and there doesn't seem to be
+> much downside to displaying the full link targets for at least moderately
+> longer strings.
+
+The downside is that the link needs to fit on the screen for the user to read it. :-)
+
+I'm not happy with the idea of a hugely-wide search results pane masking much of the screen unnecessarily, but I also think that expanding and contracting as needed could be a bit of an eyesore…",1384844593,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7fbhbqnohmq5xaiuz462,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"On this page [1], the ""Open questions"" section ends with a line that has starts with <s> but later has another <s> instead of </s>. The strikethrough ends with the second tag anyway, when the page is being viewed normally. With VisualEditor, however, the strikethrough formatting continues to the end of the page.
+
+[1] = https://www.mediawiki.org/w/index.php?title=Wikipedia_Education_Program&oldid=821826
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384790520,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-rg7ifjxavegjy63g4nhz,task_description,declined
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"Tidy is going away and RemexHTML will be used on all wikis sometime mid next year. In that context, all these pages will look broken in RemexHTML as well and the relevant broken markup on these pages has to be fixed. We have added [[https://www.mediawiki.org/wiki/Help:Extension:Linter/multiple-unclosed-formatting-tags|a special linter category to aid that effort. ]]",1513635570,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"(Tracking bug for Tidy being a piece of junk is bug 2542, by the way.)",1396786527,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"This comment is basically a +1/me too. The same issue exhibits on https://en.wikipedia.org/w/index.php?title=Actor_model&oldid=602988700 but with a <tt> rather than a <s>. After some discussion with thedj on IRC he suggested I'd file here anyway, if only to indicate it might be somewhat prevalent in the wild.
+
+Personally, I think this is a bug in tidy rather than in VE, and the most reasonable behaviour would be for tidy to conform to prevalent browser behaviour/the HTML spec, and to emit a warning about the likely location of the breakage (where tidy now closes the element)",1396785653,PHID-USER-n27daagbl3wqf3ghr4nk,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"This is a difference between tidy used by MediaWiki in production and the HTML5 spec. Tidy closes unclosed formatting elements eagerly, while the HTML5 spec demands that formatting elements are restored in most cases.
+
+We are considering to prevent formatting elements from bleeding out of transclusions (see bug 50536) for reasons of correctness and performance, but so far we don't have plans to generally move away from HTML5-compliant (and MediaWiki without tidy) behavior for this.
+
+We can detect unclosed tags and provide information for fix-ups in the wikitext though. That is partly tracked in bug 50547. I thought that we had another bug for this, but don't currently find it. Will add a link to bug 50547 when I find it.",1386120327,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"Also, when I removed the entire section that included the offending strikethrough tags, the VE still showed strikethrough on the remainder of the page.
+
+When I open it again in VE after the edit [1], it appears as expected.
+
+[1] = https://www.mediawiki.org/w/index.php?title=Wikipedia_Education_Program&diff=821838&oldid=821826",1384790892,PHID-USER-nyv6rqxnzdy3oe323a3d,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+VisualEditor: Allow users to set/edit __STATICREDIRECT__ status in the page metadata panel,"Checkbox flag, redirect pages only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7cbywnlba7fvo6mhudvs,task_description,resolved
+VisualEditor: Allow users to set/edit __STATICREDIRECT__ status in the page metadata panel,Verified the fix in test2,1393021669,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-7cbywnlba7fvo6mhudvs,task_subcomment,NA
+VisualEditor: Allow users to set/edit __STATICREDIRECT__ status in the page metadata panel,"Change 95213 merged by jenkins-bot:
+Let users set #REDIRECT and __STATICREDIRECT__ status
+
+https://gerrit.wikimedia.org/r/95213",1392349581,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7cbywnlba7fvo6mhudvs,task_subcomment,NA
+VisualEditor: Allow users to set/edit __STATICREDIRECT__ status in the page metadata panel,"Change 95213 had a related patch set uploaded by Jforrester:
+Let users set #REDIRECT and __STATICREDIRECT__ status
+
+https://gerrit.wikimedia.org/r/95213",1384754847,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7cbywnlba7fvo6mhudvs,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTITLECONVERT__ (and __NOTC__) status in the page metadata panel,"Checkbox flag, pages on variant wikis only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qu2aqxrmqddq2le4yre5,task_description,resolved
+VisualEditor: Allow users to set/edit __NOTITLECONVERT__ (and __NOTC__) status in the page metadata panel,"Change 126015 merged by jenkins-bot:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1398123277,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qu2aqxrmqddq2le4yre5,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTITLECONVERT__ (and __NOTC__) status in the page metadata panel,"Change 126015 had a related patch set uploaded by Alex Monk:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1397579976,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qu2aqxrmqddq2le4yre5,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTITLECONVERT__ (and __NOTC__) status in the page metadata panel,"Change 95726 had a related patch set uploaded by Jforrester:
+[WIP] Create remaining meta items in DM
+
+https://gerrit.wikimedia.org/r/95726",1384754699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qu2aqxrmqddq2le4yre5,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOCONTENTCONVERT__ (and __NOCC__) status in the page metadata panel,"Checkbox flag, pages on variant wikis only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ckkuvwdfjtbnqb4u7jpk,task_description,resolved
+VisualEditor: Allow users to set/edit __NOCONTENTCONVERT__ (and __NOCC__) status in the page metadata panel,"Change 126015 merged by jenkins-bot:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1398123274,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ckkuvwdfjtbnqb4u7jpk,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOCONTENTCONVERT__ (and __NOCC__) status in the page metadata panel,"Change 126015 had a related patch set uploaded by Alex Monk:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1397579981,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ckkuvwdfjtbnqb4u7jpk,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOCONTENTCONVERT__ (and __NOCC__) status in the page metadata panel,"Change 95726 had a related patch set uploaded by Jforrester:
+[WIP] Create remaining meta items in DM
+
+https://gerrit.wikimedia.org/r/95726",1384754703,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ckkuvwdfjtbnqb4u7jpk,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOGALLERY__ status in the page metadata panel,"Checkbox flag, category namespace only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zwu3t35ebtuycwppeq65,task_description,resolved
+VisualEditor: Allow users to set/edit __NOGALLERY__ status in the page metadata panel,"Change 126015 merged by jenkins-bot:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1398123269,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zwu3t35ebtuycwppeq65,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOGALLERY__ status in the page metadata panel,"Change 126015 had a related patch set uploaded by Alex Monk:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1397579990,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zwu3t35ebtuycwppeq65,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOGALLERY__ status in the page metadata panel,"Change 95726 had a related patch set uploaded by Jforrester:
+[WIP] Create remaining meta items in DM
+
+https://gerrit.wikimedia.org/r/95726",1384754694,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zwu3t35ebtuycwppeq65,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,"Trinary state (default, NEWEDITSECTION, NONEWEDITSECTION), all pages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2jvygydrgf5vwtxvhwak,task_description,resolved
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,Verified the fix in test2,1393021067,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-2jvygydrgf5vwtxvhwak,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,"Change 95725 merged by jenkins-bot:
+Let users set __NEWEDITSECTION__ & __NONEWEDITSECTION__ status
+
+https://gerrit.wikimedia.org/r/95725",1392866615,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2jvygydrgf5vwtxvhwak,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,"Change 95725 had a related patch set uploaded by Jforrester:
+Let users set __NEWEDITSECTION__ & __NONEWEDITSECTION__ status
+
+https://gerrit.wikimedia.org/r/95725",1392350212,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2jvygydrgf5vwtxvhwak,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,"Change 95725 had a related patch set uploaded by Jforrester:
+Let users set __NEWEDITSECTION__ & __NONEWEDITSECTION__ status
+
+https://gerrit.wikimedia.org/r/95725",1384754373,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2jvygydrgf5vwtxvhwak,task_subcomment,NA
+VisualEditor: Allow users to set/edit __INDEX__ and __NOINDEX__ status in the page metadata panel,"Trinary state (default, INDEX, NOINDEX), all pages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-knrygben5z6uuprlfcd4,task_description,resolved
+VisualEditor: Allow users to set/edit __INDEX__ and __NOINDEX__ status in the page metadata panel,"Change 95724 merged by jenkins-bot:
+Let users set __NOINDEX__ & __INDEX__ status
+
+https://gerrit.wikimedia.org/r/95724",1392861031,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knrygben5z6uuprlfcd4,task_subcomment,NA
+VisualEditor: Allow users to set/edit __INDEX__ and __NOINDEX__ status in the page metadata panel,"Change 95724 had a related patch set uploaded by Jforrester:
+Let users set __NOINDEX__ & __INDEX__ status
+
+https://gerrit.wikimedia.org/r/95724",1392350168,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knrygben5z6uuprlfcd4,task_subcomment,NA
+VisualEditor: Allow users to set/edit __INDEX__ and __NOINDEX__ status in the page metadata panel,"Change 95724 had a related patch set uploaded by Jforrester:
+Let users set __NOINDEX__ & __INDEX__ status
+
+https://gerrit.wikimedia.org/r/95724",1384754285,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knrygben5z6uuprlfcd4,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOEDITSECTION__ status in the page metadata panel,"Checkbox flag on/off, all pages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cvzyzrek2t2cvehwvzle,task_description,resolved
+VisualEditor: Allow users to set/edit __NOEDITSECTION__ status in the page metadata panel,"Change 95723 had a related patch set uploaded by Jforrester:
+Let users set __NOEDITSECTION__ status
+
+https://gerrit.wikimedia.org/r/95723",1384754197,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cvzyzrek2t2cvehwvzle,task_subcomment,NA
+Image searched for does not come back in results but does exist on server,"**Author:** `anjana1`
+
+**Description:**
+OS: Win 8
+Browser: Fire Fox 24 and Chrome 31.0
+
+Not able to insert an image in VE mode on Beta. The image (A nice pic.jpg) which is on commons is not seen in the list while trying to upload it using the ""Media"" in the toolbar (found in ""More"" pulldown menu)in ""Edit Beta mode"".
+
+The same image is uploadable using wikitext syntax [[File:A Nice pic.jpg]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Whiteboard**: cirrus-fixed",1384575840,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k62fxro4rxguo7ka2mon,task_description,declined
+Image searched for does not come back in results but does exist on server,This is fixed in Cirrus as far as I know. Inclined to WONTFIX for lsearchd as a result.,1398881638,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-k62fxro4rxguo7ka2mon,task_subcomment,NA
+Image searched for does not come back in results but does exist on server,"Re-titling this and putting back into the Wikimedia / Search area, as that's where the issue lies; I believe that the new search system fixes this issue, but will leave it for the experts to opine.",1393039167,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k62fxro4rxguo7ka2mon,task_subcomment,NA
+Image searched for does not come back in results but does exist on server,"**anjana1** wrote:
+
+Steps to reproduce:
+
+Pre-requisites: Create an account in http://en.wikipedia.beta.wmflabs.org
+
+1. Login with username and password into http://en.wikipedia.beta.wmflabs.org/wiki/User:<username>
+2. On the topmost right-hand side of the page, click on ""preferences""
+3. Click on the ""Beta Features"" tab and select ""VisualEditor""
+4. Click on ""Save"" at the end of the page. You must see a message saying ""Your preferences have been changed"".
+5. Click on <your username>. Your username will be found on the topmost right-hand side of the page.
+6. Click on ""Edit beta"" , found on the top right-hand side next to ""Edit Source"".
+7. On the toolbar, click on ""More"" pull-down menu and click on ""Media""
+8. Search for ""A nice picture.jpg"". [Here, we are looking for an image of ""cave 26,ajanta caves""]
+9. The intended image is not found.
+
+
+But, this can be found with wikitext i.e, without VisualEditor.
+1. Click on ""Edit Source""
+2. Type [[File:A nice picture.jpg]] on the page.
+3. Click on ""Save Page"" tab at the bottom of the page.
+4. Result: You will be able to see the intended image.",1384793674,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-k62fxro4rxguo7ka2mon,task_subcomment,NA
+Image searched for does not come back in results but does exist on server,"Thanks for taking the time to report this!
+
+Could you please provide exact steps, click by click, to reproduce the problem, so anybody else could follow these steps and get the same results?",1384692376,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-k62fxro4rxguo7ka2mon,task_subcomment,NA
+"VisualEditor: External links that point to the local wiki should be changed into internal links, not interwikis","Reported by Mattho69 on frwiki [1].
+
+If I try to add a link to a Wikipedia article using its full form (http://fr.wikipedia/org/wiki/…), it is saved as an interwiki (see [2]) instead of a local wikilink. 
+
+I notice that it only happens with HTTP links, not with HTTPS ones (see [3]), which are not converted (maybe separate bug ?).
+
+[1] https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis#:fr:
+[2] https://fr.wikipedia.org/w/index.php?title=Utilisateur:Ltrlg/tests&diff=98243431&oldid=98197987
+[3] https://fr.wikipedia.org/w/index.php?title=Utilisateur:Ltrlg/tests&diff=98243523&oldid=98243431
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45209
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61672",1384363680,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-jb2rslshvyhiqokerp5m,task_description,resolved
+"VisualEditor: External links that point to the local wiki should be changed into internal links, not interwikis","
+
+*** This bug has been marked as a duplicate of bug 42986 ***",1397764105,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jb2rslshvyhiqokerp5m,task_subcomment,NA
+"VisualEditor: Improve message for parameters that have no TemplateData (say ""undocumented"" instead of ""unknown"")","When adding parameters of some templates like this:
+https://cs.wikipedia.org/wiki/%C5%A0ablona:Citace_elektronick%C3%A9_monografie
+ it sais ""unknown parametr"" even the parametr is valid and works afterwords. 
+
+This information is confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1384164360,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-he2d3umv5r6rhdzphakm,task_description,open
+"VisualEditor: Improve message for parameters that have no TemplateData (say ""undocumented"" instead of ""unknown"")","There are very many templates where the TemplateData description is incomplete and some parameters are just not documented. Some better description than unknown would be good - perhaphs ""undocumented"".",1519683820,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-he2d3umv5r6rhdzphakm,task_subcomment,NA
+"VisualEditor: Improve message for parameters that have no TemplateData (say ""undocumented"" instead of ""unknown"")","Right now, manually adding a parameter that's not described by TemplateData shows a message saying that the parameter is ""unknown"", which is a little odd if it then seems to work.",1384842902,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-he2d3umv5r6rhdzphakm,task_subcomment,NA
+"VisualEditor: Improve message for parameters that have no TemplateData (say ""undocumented"" instead of ""unknown"")",What would be the exact steps to follow in order to reproduce this problem?,1384181553,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-he2d3umv5r6rhdzphakm,task_subcomment,NA
+VisualEditor: Appending to a line shows additions before end of line in diff,"Steps to reproduce:
+1. Find a page that already has a category
+2. Edit in VE, and add a category
+3. Review changes
+
+Expected results:
+The diff is
+```
++**[[Category:New cat]]**
+```
+
+Actual results:
+The diff is
+```
+-[[Category:Old cat]]
++[[Category:Old cat**]][[Category:New cat**]]
+```
+With the chunk between the stars viewed as added.
+
+This also happens in the source editor, but it is less common that people will append a category to an existing category as that is against all style guidelines.  However the Visual Editor is doing just that.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1384146180,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-p4ulxppdivzqqe2umxe7,task_description,resolved
+VisualEditor: Appending to a line shows additions before end of line in diff,"I cannot reproduce this anymore with VE visual mode; the category gets added in a separate new line. Maybe this got fixed in T135667.
+Please reopen if you can still reproduce.",1565560030,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-p4ulxppdivzqqe2umxe7,task_subcomment,NA
+VisualEditor: Allow users to set/edit other behavioural flags in the page metadata panel,"Checkboxes (disabled for some/most namespaces), setting:
+
+__NEWSECTIONLINK__
+  <meta property=""mw:PageProp/newsectionlink"">
+
+__NONEWSECTIONLINK__
+  <meta property=""mw:PageProp/nonewsectionlink"">
+
+__NOGALLERY__
+  <meta property=""mw:PageProp/nogallery"">
+
+__HIDDENCAT__
+  <meta property=""mw:PageProp/hiddencat"">
+
+__NOCONTENTCONVERT__
+  <meta property=""mw:PageProp/nocontentconvert"">
+
+__NOCC__
+  <meta property=""mw:PageProp/nocc"">
+
+__NOTITLECONVERT__
+  <meta property=""mw:PageProp/notitleconvert"">
+
+__NOTC__
+  <meta property=""mw:PageProp/notitleconvert"">
+
+__NOEDITSECTION__
+  <meta property=""mw:PageProp/noeditsection"">
+
+__NOINDEX__
+  <meta property=""mw:PageProp/noindex"">
+
+__INDEX__
+  <meta property=""mw:PageProp/index"">
+
+__STATICREDIRECT__
+  <meta property=""mw:PageProp/staticredirect"">
+
+… and possibly others.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384101720,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3p46j5ufygre5dauey6h,task_description,invalid
+VisualEditor: Allow users to set/edit other behavioural flags in the page metadata panel,Split out as bug 57166 ++,1384755174,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3p46j5ufygre5dauey6h,task_subcomment,NA
+VisualEditor: Allow users to set/edit other behavioural flags in the page metadata panel,"Similar to bug 56867 comment 1 I think these would be better handled as pairs of radio buttons, e.g.
+
+Show this category on member pages: * Yes * No
+Show a gallery of images in this category: * Yes * No
+Show a new section link in the tab par for this page: * Yes * No
+Allow search engines to index this page: * Yes * No
+
+Defaults would be set per namespace as at present.",1384186519,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3p46j5ufygre5dauey6h,task_subcomment,NA
+VisualEditor: Allow users to set/edit __FORCETOC__ status in the page metadata panel,"A checkbox, greyed out when there are more than 2 headings(?), setting:
+
+  <meta property=""mw:PageProp/forcetoc"">
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384101180,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3gsbzhqvjcq7g3i67lcq,task_description,resolved
+VisualEditor: Allow users to set/edit __FORCETOC__ status in the page metadata panel,"Change 95103 merged by jenkins-bot:
+Let users set __NOTOC__ & __FORCETOC__ status
+
+https://gerrit.wikimedia.org/r/95103",1388919569,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3gsbzhqvjcq7g3i67lcq,task_subcomment,NA
+VisualEditor: Allow users to set/edit __FORCETOC__ status in the page metadata panel,"Change 95103 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT, __NOTOC__, & __FORCETOC__
+
+https://gerrit.wikimedia.org/r/95103",1384313414,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3gsbzhqvjcq7g3i67lcq,task_subcomment,NA
+VisualEditor: Allow users to set/edit __FORCETOC__ status in the page metadata panel,"Perhaps better than this and bug 56866 would be a radio button/dropdown with three options for TOC:
+Include an automatic table of contents on this page:
+* Never
+* When there are three or more headings (default)
+* Always
+
+If different wikis (can) have different settings for the number of headings before a TOC then the middle option will need to read that setting.
+
+I say ""automatic"" above as manual TOC templates such as [[template:Compact ToC]] should always override this setting.",1384185420,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3gsbzhqvjcq7g3i67lcq,task_subcomment,NA
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"PageTriage UI editing User page
+
+seen on beta enwiki:
+
+* log in as a user with PageTriage privileges e.g. Selenium_user
+* visit http://en.wikipedia.beta.wmflabs.org/wiki/Special:NewPagesFeed
+* visit your user page
+
+PageTriage UI appears
+
+PageTriage UI should not appear on User pages
+PageTriage UI should not appear in the editor
+
+see screen shot
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12047}",1383850080,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-evnlmsxi5llkdqpags37,task_description,resolved
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"Change 133379 merged by jenkins-bot:
+Hide PageTriage curation toolbar while VE is open
+
+https://gerrit.wikimedia.org/r/133379",1400108645,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-evnlmsxi5llkdqpags37,task_subcomment,NA
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"Change 133379 had a related patch set uploaded by Alex Monk:
+Hide PageTriage curation toolbar while VE is open
+
+https://gerrit.wikimedia.org/r/133379",1400106032,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-evnlmsxi5llkdqpags37,task_subcomment,NA
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"
+I don't believe I logged a bug against PageTriage at the time.",1400105734,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-evnlmsxi5llkdqpags37,task_subcomment,NA
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"(In reply to Chris McMahon from comment #0)
+> PageTriage UI should not appear on User pages
+
+Was a bug logged against PageTriage for that?",1400104778,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-evnlmsxi5llkdqpags37,task_subcomment,NA
+Flow: Agora CSS issues in IE8,"I visited a Flow page in IE8, which is 8% of WMF audience according to https://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix (and more elsewhere I think).
+
+Screenshot https://saucelabs.com/jobs/2a2680aeb681420381a5652ddf5fdca2/0001screenshot.png?auth=fc4f7362b9615cfceee0744b0f4bc93a
+
+There are issues with Flow's local Agora CSS override in IE8:
+* Gray backgrounds on secondary buttons (they should appear without any button border).
+* Buttons aren't rounded.
+* Thank icon goes away on mouseover.
+* ""Start a new topic"" text field and textarea both have no blue bar on focus.
+* Textarea has no placeholder (see http://www.jacklmoore.com/notes/form-placeholder-text/ ,also there's a jquery.placeholder in core, and Matt Flaschen had a placeholder patch for Login forms).
+* Green [Add topic] button text looks poor.
+
+For now this is a Flow bug, but at some point a version of this CSS will migrate to core (bug 54360).  https://gerrit.wikimedia.org/r/#/c/93584 may already have relevant LESS workarounds.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**URL**: http://ee-flow.wmflabs.org/wiki/User_talk:Spage",1383785580,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-akhhxseet47blrfcikb5,task_description,declined
+Flow: Agora CSS issues in IE8,5 years later and IE8 is not longer a supported client.,1523277647,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-akhhxseet47blrfcikb5,task_subcomment,NA
+Flow: Agora CSS issues in IE8,status ?,1409576638,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-akhhxseet47blrfcikb5,task_subcomment,NA
+Flow: Agora CSS issues in IE8,"Possibly relevant, a current discussion on WP:VPT, describing odd problems with IE8 that supposedly only started on Nov 2nd.
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Unable_to_do_anything_through_IE8",1383850053,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-akhhxseet47blrfcikb5,task_subcomment,NA
+Flow: Agora CSS issues in IE8,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/413, but people from the community are welcome to contribute here and in Gerrit.",1383805211,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-akhhxseet47blrfcikb5,task_subcomment,NA
+Flow must respect the per-wiki VE opt-in/out configuration,"VE on beta labs and on prod is opt-in, but VE on test2wiki/mw.o is enabled by default for everyone, including anons. Flow must appropriatly offer VE as configured by the wiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383758160,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-hzlysdp33ce6zpzmy3wm,task_description,invalid
+Flow must respect the per-wiki VE opt-in/out configuration,"We're not using VE anymore; if/when we do, we can reopen.",1390958975,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-hzlysdp33ce6zpzmy3wm,task_subcomment,NA
+Flow must respect the per-wiki VE opt-in/out configuration,Less pressing now that editing in Flow with VisualEditor is disabled by default (gerrit 99721).,1386620084,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-hzlysdp33ce6zpzmy3wm,task_subcomment,NA
+Flow must respect the per-wiki VE opt-in/out configuration,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/411, but people from the community are welcome to contribute here and in Gerrit.",1383805197,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-hzlysdp33ce6zpzmy3wm,task_subcomment,NA
+VisualEditor: Hover effect inconsistent for Help icon,"Noticed on mediawiki.org, currently at 1.23wmf2 (88c7b3f)
+
+On hover, the Help icon in the VisualEditor toolbar gets both the light gray border with all corners rounded, and the darker gray border that, if I look at the Menu icon for reference, should probably only appear when the button is pressed, not just hovered.
+
+Furthermore, the dark gray border only has the left corners rounded.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1383656340,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-6rvja2kia3oue26e5a2q,task_description,declined
+VisualEditor: Hover effect inconsistent for Help icon,"This doesn't appear to be a problem anymore (not even on MonoBook, which still uses the original toolbar design), or I'm misunderstanding your description. In the future, please file bugs with screenshots. :(",1487210805,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6rvja2kia3oue26e5a2q,task_subcomment,NA
+VisualEditor: Hover effect inconsistent for Help icon,"The behaviour is correct because the help icon is actually in a group with the notification icon, however the notification icon is hidden when there are no notifications. This is also the cause of the rounded corners problem, as the CSS renderer doesn't match the last-child rule if the next child is hidden.
+
+Solutions:
+* Group help and notifications with the hamburger menu. This avoids the rounded corners problem, and the issue of the colours looking wrong because it is a set of one, but is hacky.
+* Destroy the notifications icon when not in use. This would involve a bit of a rewrite as in theory it's possible to push notifications after load and the button should appear when this happens.
+* Ungroup help and notifications. This avoids all the problems here.",1383669904,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6rvja2kia3oue26e5a2q,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"As the preferred way to access the `wg*` variables in JavaScript is to use mw.config.get()/.set(), accessing them as globals (i.e. as members of window) should show deprecation notices in debug mode, just like it is done for the functions from wikibits.js.",1383558360,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-f2wyattehq3ovuellsm6,task_description,resolved
+Show deprecation notices when accessing wg* JavaScript globals,"Change 133162 merged by jenkins-bot:
+mw.config: Show deprecation notices when accessing globals
+
+[[https://gerrit.wikimedia.org/r/133162]]",1420428513,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"Change 133162 had a related patch set uploaded (by Krinkle):
+mw.config: Show deprecation notices when accessing globals
+
+[[https://gerrit.wikimedia.org/r/133162]]
+
+#patch-for-review",1417496573,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"Change 133162 had a related patch set uploaded by Gerrit Patch Uploader:
+Show deprecation notices when accessing wg* JavaScript globals
+
+https://gerrit.wikimedia.org/r/133162",1400013433,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,mw.log.deprecate warnings are now visible when not in debug mode too.,1394235254,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"I just tried, and found that mw.log.deprecate can be called multiple times for the same variable without any problems. So mw.config.set could just call it, and whenever a wg* variable is changed via mw.config.set the global value would be updated, too. Only the other way round wouldn't work (or require some extra code instead of mw.log.deprecate).",1383817024,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"(In reply to comment #3)
+> (In reply to comment #1)
+> > mw.config.get('wg*') is currently basically a wrapper for window.wg*. To make
+> > such deprecation notices possible we'd have to duplicate the values, which
+> > could cause them to get out-of-sync if something modified them after page
+> > load.
+> 
+> Is this an actual issue? Once they are set, they shouldn't be changed anyway.
+> So using a new object for mw.config.values instead of window and copying the
+> variables over when they are set the first time using mw.log.deprecate
+> shouldn't break more than replacing some of the wikibits.js functions with
+> $.noop will break.
+
+Apparently VisualEditor sets one, see bug 56532.",1383677840,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"(In reply to comment #1)
+> mw.config.get('wg*') is currently basically a wrapper for window.wg*. To make
+> such deprecation notices possible we'd have to duplicate the values, which
+> could cause them to get out-of-sync if something modified them after page
+> load.
+
+Is this an actual issue? Once they are set, they shouldn't be changed anyway. So using a new object for mw.config.values instead of window and copying the variables over when they are set the first time using mw.log.deprecate shouldn't break more than replacing some of the wikibits.js functions with $.noop will break.
+
+(In reply to comment #2)
+> Hm, how would deprecation actually work? Can we add getters on the window
+> object?
+
+Yes, if you don't believe it, have a look at wikibits.js.",1383641734,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"Hm, how would deprecation actually work? Can we add getters on the window object?",1383588507,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"mw.config.get('wg*') is currently basically a wrapper for window.wg*. To make such deprecation notices possible we'd have to duplicate the values, which could cause them to get out-of-sync if something modified them after page load.",1383560942,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+VisualEditor: unintended ref change resulting in a dirty diff,"https://en.wikipedia.org/w/index.php?title=Guilt_(emotion)&diff=579908396&oldid=576819947
+
+I only intended to edit the ""See also"" section. VisualEditor edited a <ref> without my knowledge or consent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383422400,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-tfngbl2qu7djqip3dbd3,task_description,resolved
+VisualEditor: unintended ref change resulting in a dirty diff,"I [[ https://en.wikipedia.org/w/index.php?title=User%3ANeil_P._Quinn-WMF%2Fsandbox&diff=656821548&oldid=656821441 | repeated ]] @MZMcBride's testcase, and I didn't see any dirt. Closing. ",1429226399,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-tfngbl2qu7djqip3dbd3,task_subcomment,NA
+VisualEditor: Faked keys don't trigger triggers,"If you're not pressing a ""\"" key, OO's trigger doesn't see a ""\"" key being pressed. This includes if you magically simulate a ""\"" key with another key combination, like ""AltGr + 8"" on French keyboards. Should we support that?
+
+Split from bug 53682.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383283800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zx4tbcdiu47yjmwyniwx,task_description,open
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,"I want to be able to test and give feedback for VisualEditor, so I've opted in on the English Wikipedia.
+
+VisualEditor has bugs, but identifying bugs caused in your own edits can be annoying.
+
+When I make an edit using VisualEditor, I want to be able to verify the edit (double-check VisualEditor's behavior) by viewing a diff of the changes. (Unlike when I'm editing wikitext, where I'll only preview and not use ""show changes"" to view a diff.) Clicking ""Review your edits"" in VisualEditor's user interface is tedious and interrupts my workflow.
+
+It might be nice to implement showing the diff post-save for advanced users who simply want to be able to report an issue with VisualEditor. Or perhaps we could restore the previous behavior where a diff was automatically shown. This is an advanced user option, so it could be JavaScript config or similar. It should not be a user preference or anything that's user-facing. This feature would hopefully make reporting issues easier: rather than needing to request a diff from VisualEditor or navigate to the page history to check a diff link there, you would simply be presented with a diff.
+
+In addition, if we're implementing an advanced user auto-diff option, perhaps we can also add a ""report an issue"" link to more easily file a bug? (Or search for relevant bugs.)
+
+Filing as a Sunday afternoon thought.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382894520,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_description,declined
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,This is probably no longer needed now that most VisualEditor bugs messing up your edits have been fixed (and the few that haven't are known).,1696087493,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_subcomment,NA
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,"Triaging (but doing this as a gadget might make more sense, given this need is going to be short-term and our aversion to preference bloat).",1387221515,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_subcomment,NA
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,"Hey guys. The ""report an issue"" link has been there for a while: click on the question mark, then ""Leave feedback"". You can even choose if you want to file a bug here or add your request to the feedback page. HTH.",1385420445,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_subcomment,NA
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,"(In reply to comment #0)
+> Or perhaps we
+> could restore the previous behavior where a diff was automatically shown.
+
+I don't recall an core mediawiki option for post-save diffs; have I forgotten?
+I would love an pref 'Show diff after page save' in core, which when combined with 'Do not show page content below diffs' would mean my browser doesn't automatically fetch a new version of the page, which could be quite large.
+
+Or, do you mean a pre-launch VisualEditor behaviour where a diff was automatically shown?  Was it pre-save or post-save?",1384145015,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_subcomment,NA
+"VisualEditor: Wikitext warning not triggered when editing image captions, references","Wikitext added to image captions is nowikied in the same way that markup added to the page body is. e.g. https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=578947711&oldid=574091986 however the wikitext warning is not generated.
+
+To reproduce:
+1. Load any page with an image in VE
+2. Edit the image caption
+3. Add any wiki markup in the caption (tested with bold, italic and links)
+
+Expected behaviour: The wikitext warning pops up.
+Action behaviour: Nothing happens
+
+If popping up the warning while in the image caption dialog is not possible, then it should do so immediately the dialog is closed. Displaying it at the same time would be preferable though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53839",1382877060,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-esodzvlhnrqwgbidaff4,task_description,resolved
+"VisualEditor: Wikitext warning not triggered when editing image captions, references","Change 138761 merged by jenkins-bot:
+Show wikitext warnings in the reference and media caption dialogs
+
+https://gerrit.wikimedia.org/r/138761",1403125231,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-esodzvlhnrqwgbidaff4,task_subcomment,NA
+"VisualEditor: Wikitext warning not triggered when editing image captions, references","Change 138761 had a related patch set uploaded by Alex Monk:
+Show wikitext warnings in the reference dialog
+
+https://gerrit.wikimedia.org/r/138761",1402445473,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-esodzvlhnrqwgbidaff4,task_subcomment,NA
+"VisualEditor: Wikitext warning not triggered when editing image captions, references","I started looking at this. It's annoying because the code to do the wikitext detection is already there and working for the main surface. It would be trivial to do the absolutely wrong way (i.e. copy the existing code to the reference surface or image caption surface and just change the reference to the Surface object), but it's a pain to fix the proper way.
+
+One of the problems lies in the differences between normal surfaces (i.e. the main one) and surface widgets. It was suggested that we could implement MWSurfaceWidget which does the wikitext warning, but the main surface is not a widget and would still need it's own version of the code.
+
+Also, we can't just shove the wikitext detection code in the ve.ui.Surface class and guard it with some config, because the Surface code lives in VE core which does not deal with MediaWiki features (wikitext) - the VE MediaWiki extension deals with that.
+
+Roan suggested we could make the main surface be a surface widget and then create an MWSurfaceWidget, but that apparently has issues involving toolbar floating (I'm not familiar with this, perhaps it could be fixed in some way).
+
+I think that for now, we can probably change the wikitext detection function to accept a surface parameter, then make it static somewhere and have each wikitext-free surface to set up an event handler for it.",1402442853,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-esodzvlhnrqwgbidaff4,task_subcomment,NA
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.","Please rephrase the message ""Visualeditor-preference-enable"". Currently it says: ""Enable VisualEditor (only in the main and user namespaces)""
+
+With https://gerrit.wikimedia.org/r/#/c/90923/ the VE was enabled in NS_FILE, NS_HELP, NS_CATEGORY namespaces too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1382807280,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-iun6kcufna6ud4g23brk,task_description,resolved
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.",*** Bug 52188 has been marked as a duplicate of this bug. ***,1385396577,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iun6kcufna6ud4g23brk,task_subcomment,NA
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.","Change 92340 merged by jenkins-bot:
+Re-word visualeditor-preference-enable to not specify NSes
+
+https://gerrit.wikimedia.org/r/92340",1382982294,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iun6kcufna6ud4g23brk,task_subcomment,NA
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.","Change 92340 had a related patch set uploaded by Jforrester:
+Re-word visualeditor-preference-enable to not specify NSes
+
+https://gerrit.wikimedia.org/r/92340",1382981666,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iun6kcufna6ud4g23brk,task_subcomment,NA
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.",Good catch!,1382807414,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-iun6kcufna6ud4g23brk,task_subcomment,NA
+VisualEditor: Remove unused CSS classes,"For instance, there's a rule for .oo-ui-toolbar-bottom but no code adding that class to anything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382592120,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dwai2fmvvprbgn2msyx6,task_description,open
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"see page 
+
+https://test2.wikipedia.org/wiki/User:Selenium_user/cursor_test_page2?veaction=edit
+
+In Chrome, hit down-arrow 3 times to get to the line that begins with text 'Invisible'
+
+In Firefox, it takes 4 times hitting down-arrow to get to that line.  The first time hitting down-arrow does nothing
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382561640,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_description,resolved
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,There are no slugs after lists anymore either.,1423751013,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"Well, this now doesn't happen because Firefox doesn't get the surface selected on open.",1421282698,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"Change 92331 merged by jenkins-bot:
+[browser test] don't run cursor test pending Bug 56068 and review
+
+https://gerrit.wikimedia.org/r/92331",1382979490,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"Change 92331 had a related patch set uploaded by Cmcmahon:
+[browser test] don't run cursor test pending Bug 56068 and review
+
+https://gerrit.wikimedia.org/r/92331",1382978699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"as of Oct 28, the first right-arrow keyed also does nothing, and the first down-arrow keyed continues to do nothing.   Keying right-arrow had worked before.",1382970830,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"Not occurring in FF18, but is in FF24; divergent behaviour from Chrome, where this works as expected.",1382632069,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"
+this is causing browser test failures",1382562148,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Remove dual-type support for categories and language links,"Per https://gerrit.wikimedia.org/r/#/c/90339/ we should remove the dual-type support once it's been long enough since Parsoid has renamed the types.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382468760,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ly3c2pbora5rvknhb3sm,task_description,resolved
+VisualEditor: Remove dual-type support for categories and language links,Re-opened as this will need to be co-ordinated with Parsoid to do a cache purge.,1386302494,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ly3c2pbora5rvknhb3sm,task_subcomment,NA
+VisualEditor: Remove dual-type support for categories and language links,"Change 99310 merged by jenkins-bot:
+Remove dual-type support for Languages and Categories
+
+https://gerrit.wikimedia.org/r/99310",1386284494,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ly3c2pbora5rvknhb3sm,task_subcomment,NA
+VisualEditor: Remove dual-type support for categories and language links,"Change 99310 had a related patch set uploaded by Jforrester:
+Remove dual-type support for Languages and Categories
+
+https://gerrit.wikimedia.org/r/99310",1386211170,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ly3c2pbora5rvknhb3sm,task_subcomment,NA
+"VisualEditor: VE blanks syntax-highlight extension block after editing contents with ""<>"" popup","screenshot
+
+VE blanks syntax-highlight extension block after editing contents with ""<>"" popup. :(
+
+If you open the popup back up the source is there, but the preview in the editor is empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Manual:CORS?veaction=edit
+
+**Attached**: {F12120}",1382271180,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-2ns4vqzbqzflsbtpszu5,task_description,resolved
+"VisualEditor: VE blanks syntax-highlight extension block after editing contents with ""<>"" popup","Ha, yeah, we fixed this ages ago, I believe.",1411404775,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2ns4vqzbqzflsbtpszu5,task_subcomment,NA
+"VisualEditor: VE blanks syntax-highlight extension block after editing contents with ""<>"" popup","Does this still happen? I cleaned up various issues with extension blocks some months ago, and I never ran into this.",1411399735,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2ns4vqzbqzflsbtpszu5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"On English Wikipedia, the VE is now not offered for anons & people who have not enabled a user pref.
+
+However if the user loads a URL that invokes VE (i.e. includes ?veaction=edit), it would be nice if VE loaded irrespective of user preferences.  If ?veaction=edit in the URL isnt explicit enough to bypass some checks, ?veaction=edit&debug=true should just do it.
+
+That would streamline testing in many browsers, as we wouldnt need to log in on each browser - which is a bugger because logging into a second browser causes the first browser to be logged out.(bug 49890)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51765
+https://bugzilla.wikimedia.org/show_bug.cgi?id=19415",1382133000,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_description,resolved
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"Change 97701 merged by jenkins-bot:
+Make veaction=edit work regardless of user preference
+
+https://gerrit.wikimedia.org/r/97701",1386027834,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"Change 97701 had a related patch set uploaded by Jforrester:
+Make veaction=edit work regardless of user preference
+
+https://gerrit.wikimedia.org/r/97701",1385459614,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"(In reply to comment #2)
+> It is not a regression. Fixing.
+Removing the code-update-regression keyword; it sounds like you intended to do that.",1382136351,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"(In reply to comment #0)
+> On English Wikipedia, the VE is now not offered for anons & people who have
+> not enabled a user pref.
+
+Indeed.
+
+> However if the user loads a URL that invokes VE (i.e. includes
+> ?veaction=edit), it would be nice if VE loaded irrespective of user
+> preferences. If ?veaction=edit in the URL isnt explicit enough to bypass some
+> checks, ?veaction=edit&debug=true should just do it.
+
+Possibly, but I feel that this conflicts with the expressed will of the community (to prevent anonymous users from being able to use VisualEditor).
+
+> That would streamline testing in many browsers, as we wouldnt need to log in
+> on each browser - which is a bugger because logging into a second browser
+> causes the first browser to be logged out.(bug 49890)
+
+Understood the use-case (I have the issue too).
+
+(In reply to comment #1)
+> p.s. anon VE testing via URL params used to work.
+
+Because it was enabled for all anons; when the configuration was changed, this feature was disabled. It is not a regression. Fixing.",1382135173,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,p.s. anon VE testing via URL params used to work.,1382133712,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+"VisualEditor: When indenting a list as a block, instead of putting it inside its own type, use <dl><dd>s","example of a number list attempting to be indented
+
+This may be similar to https://bugzilla.wikimedia.org/show_bug.cgi?id=48010
+
+In the VisualEditor, entire lists cannot be indented. For example, to get an entire list to appear slightly indented, a user would type in wikitext:
+
+:* First
+:** First sub one
+:** First sub two
+:** First sub three
+:* Second
+:** Second sub one...
+
+Whereas the VisualEditor is attempting to enter this wikitext:
+
+** First
+*** First sub one
+*** First sub two
+*** First sub three
+** Second
+*** Second sub one...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12745}",1381942020,PHID-USER-2mvmxqtefj5cyyzm7jks,PHID-TASK-vmns7e2rmymfweongzav,task_description,open
+VisualEditor: Adding an image at the top of a list puts the image inside the list,"=Steps to reproduce=
+Start with a section whose contents are: 
+```
+ ==Heading==
+ * Alice
+ * Bob
+ * Chris
+```
+Place the cursor just before the 'A' in 'Alice' and insert an image.
+
+The image will be placed inside the first list item:
+```
+==Heading==
+* [[File:Example.jpg]]Alice
+* Bob
+* Chris
+```
+
+Editors almost never place images inside list items so they are likely to expect this to produce the following wikitext instead:
+```
+==Heading==
+[[File:Example.jpg]]
+* Alice
+* Bob
+* Chris
+```
+
+See https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=577354576&oldid=577352415 for an example (look for the image of the apple).",1381880400,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-lv7k67pbkstmigdp3rd7,task_description,open
+VisualEditor: Adding an image at the top of a list puts the image inside the list,"This isn't about the VisualEditor, it is about the PHP Parser?",1488543425,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-lv7k67pbkstmigdp3rd7,task_subcomment,NA
+VisualEditor: Adding an image at the top of a list puts the image inside the list,"Same thing happen at the bottom of the list.
+Example at [[ https://no.wikipedia.org/w/index.php?title=%C3%98vre_Vang_kirke&oldid=17205263 | w:no:Øvre Vang kirke ]].
+
+Note that preview in VisualEditor/WikitextEditor seems to do it right. Or at least different.
+
+It is not enough to add a newline to break out of the list.",1488543289,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-lv7k67pbkstmigdp3rd7,task_subcomment,NA
+VisualEditor: Adding an image at the top of a list puts the image inside the list,"Same thing happen at the bottom of the list.
+Example at [[ https://no.wikipedia.org/w/index.php?title=%C3%98vre_Vang_kirke&oldid=17205263 | w:no:Øvre Vang kirke ]].",1488543193,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-lv7k67pbkstmigdp3rd7,task_subcomment,NA
+VisualEditor: Don't encourage users to set a group for reference lists (as that's only rarely used),"Maybe I havent understood, but I think it is not necessary to push user to add group to Reference list. Most of the references are used as a references. Other groups may be insert as an option. If you force it, it blocks to add references.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381816620,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-lcf23f43lwbo3lfwkrca,task_description,resolved
+VisualEditor: Don't encourage users to set a group for reference lists (as that's only rarely used),"In the fix for bug 59180 we made the group have a placeholder (default text) that says ""General references"" (in English), which should discourage this enough – marking as FIXED, though happy to discuss better ways to improve this if you want to re-open (or create a new bug).",1392860457,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lcf23f43lwbo3lfwkrca,task_subcomment,NA
+VisualEditor: Don't encourage users to set a group for reference lists (as that's only rarely used),"Well,
+
+I think this may cause also the following problem:
+
+At this page:
+https://cs.wikipedia.org/wiki/Angus_MacLise
+There is one reference in group ""p"", but the VE engine sais here:
+https://cs.wikipedia.org/wiki/Angus_MacLise#Pozn.C3.A1mky
+
+there is no group p!",1383465560,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-lcf23f43lwbo3lfwkrca,task_subcomment,NA
+VisualEditor: Don't encourage users to set a group for reference lists (as that's only rarely used),"The ""group"" parameter is necessary if you have multiple reference lists, which is uncommon but is used some times. Re-wording to make clearer.",1381874206,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lcf23f43lwbo3lfwkrca,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"In the software at Wikisource it not possible to have paragraphs (by inserting empty lines) in references similar to the normal text. See: https://en.wikisource.org/wiki/User:Aschroet/test. In the normal HTML view the empty lines are just ignored and only one text block is shown. Even more interesting is the behavior in case when the text is exported by ""Download as PDF"". There, the paragraphs are created but not in a correct way.
+
+The usage of <nowiki><p></nowiki> helps for the HTML view but not for PDF. The usage if <nowiki><br /></nowiki> works but does not generate real paragraphs but only newline in HTML and PDF.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: minor",1381677300,PHID-USER-nrfhx7zwxqc7nau5uyyz,PHID-TASK-uysfedps55fdczhfrfys,task_description,open
+No paragraphs/linebreaks in references by inserting empty lines,"Change 574116 **abandoned** by Thiemo Kreuz (WMDE):
+[mediawiki/services/parsoid@master] Replace new lines with <br> tag in references
+
+Reason:
+Please create a new Phabricator ticket to let the Parsoid and VisualEditor teams know what's going on. I'm closing this proposal for now because it is almost certainly not a valid way forward, and to free up our review queues. You can link it from the ticket, and it can be reopened later if it turns out it's a valid way forward.
+
+https://gerrit.wikimedia.org/r/574116",1593768715,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"IMO the editor should add <br> tags when the VE user press Enter inside <ref>. Because presently the behavior is not ""WYSIWYG"" (loss of new lines after saving the page), and, personally, I have an intensive use of references with different paragraphs.",1588259976,PHID-USER-rfidgdbrpqooabqr372x,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"I'm afraid this is not a bug, but an intentional feature of both the #mediawiki-parser and the #Cite extension.
+
+First, references are meant to be text (technically: inline elements). When <ref> tags are rendered, the text is enclosed in <span class=""reference-text"">. However, we are not limiting the features that can be used in <ref>. This is mostly for historical reasons. Cite is old. Users are free to use all wikitext features in <ref>, but we do not and can not guarantee they are all rendered exactly the same as in other contexts.
+
+The fact an empty line in a <ref> does not create a paragraph is, strictly speaking, unrelated to <ref>. The same happens outside of references. Example wikitext:
+```lang=html
+* <span>This does
+
+not render as two paragraphs.</span>
+```
+
+This creates a single list item without any line breaks. As said above, I believe this is intentional and not a bug. If this behavior is going to change, we certainly can't just add a hack to some arbitrary <ref> code, but would need to fix this in all existing Parsers.
+
+Note we can't use <p> elements in a list.",1582385531,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Change 574116 had a related patch set uploaded (by Pastakhov; owner: Pastakhov):
+[mediawiki/services/parsoid@master] Replace new lines with <br> tag in references
+
+[[https://gerrit.wikimedia.org/r/574116]]",1582325512,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Change 572301 abandoned by Pastakhov:
+Replace new lines with <br> tag in <ref> (patch for v0.11.0) Do Not Merge!
+
+[[https://gerrit.wikimedia.org/r/572301]]",1581706113,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Change 572301 had a related patch set uploaded (by Pastakhov; owner: Pastakhov):
+[mediawiki/services/parsoid@master] Replace new lines with <br> tag in <ref> (patch for v0.11.0) Do Not Merge!
+
+[[https://gerrit.wikimedia.org/r/572301]]",1581705808,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Background:
+
+This issue manifests itself most often when using ""bundled references"" - https://en.wikipedia.org/wiki/Wikipedia:Citing_sources#Bundling_citations - where a single citation calls up multiple sources. Semantically references are a list and what we really ought to be doing is for the bundled references to be a nested list within one item of the overall list. However, the visual presentation of references is often the dominant factor among editors and they try to make each reference in the bundle display on a new line. This is sometimes implemented by inserting a raw <p> tag into the wikitext to create a paragraph and that is (i) semantically incorrect; and (ii) an annoyance for users of screen readers. Using <br> is similarly problematical.
+
+In any case, inserting a blank line does not cause bundled references to display on separate lines as would be expected, hence this bug.",1431350026,PHID-USER-cctxaafy3x73lcil6bsc,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"This bug causes an accessibility issue for screen reader users like myself, allbeit a minor one, because it makes it difficult to create HTML paragraphs that are semantically correct, as discussed at:
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Manual_of_Style/Accessibility&oldid=661776586#.7B.7Bparagraph_break.7D.7D",1431307598,PHID-USER-sufjfnou23bahju6b5me,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"> In the software at Wikisource it not possible to have paragraphs (by inserting empty lines) in references similar to the normal text....
+
+The same type of DIV-ish [[https://en.wikisource.org/w/index.php?title=User:Aschroet/test&diff=5172643&oldid=4604940 | hack]] folks used for BLOCKQUOTE works for one or more newlines wrapped within REF tags as well.
+
+I'm under the impression the ''paragraphStack'' approach in the parser was always at fault when it came to this (or at least plays a role in one reported instance or another). Seems like it should lead off with a closing P tag instead of a BR to me (resulting in an empty P tag at worst).
+
+... but I don't know enough about this stuff to be sure about much truth be told.",1419191897,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"My mind doesn't always understand itself either.
+
+Currently, newlines inside <ref> tags or Image/File brackets are ignored.  This was also the case for <blockquote> and various quote templates.  
+
+Due to Visual Editor's logic, VE was *not* ignoring newlines in <blockquote> or the quote templates.  The solution to fix whether newlines should or shouldn't be ignored was bug 6200.  6200 fixed the parser code so newlines are *not* ignored by anyone.
+
+The question is, does VE respects newline characters in <ref> and Image/File brackets?  I ask the question because:
+1) Bug 6200 languished for eight years until the problem showed up in VE
+2) If VE is not ignoring the newlines, this too becomes a VE vs parser issue.
+3) To show a past precedent of newlines being ignored and the bug being fixed.",1381957895,PHID-USER-xw5m756eevennryab5gb,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,bgwhite: Not sure if the VisualEditor codebase itself thinks or will answer your questions here. Maybe you want to rephrase for humans.,1381922477,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"This problem has been going on for awhile for ref tags.  
+
+Until today, newlines did not work correctly in blockquotes and various blockquote type templates (bug 6200).  The bug was finally fixed today on enwiki after 8 1/2 years and 2 years after a patch was submitted.  The reason for finally fixing it was because Virtual Editor thought newlines should actually work like newlines.  Silly VE.
+
+Does VE think newlines should actually work in ref tags?
+https://en.wikipedia.org/wiki/Mormons, ref 110 uses a newline. 
+
+Newlines also don't work in Image/File brackets.  Does VE think newlines should actually work there too?
+https://en.wikipedia.org/wiki/Angular_momentum, second to last image is an example.",1381902538,PHID-USER-xw5m756eevennryab5gb,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"For the example, in Wikisource we convert orignial sources to digital texts. Footnotes as e.g. in https://de.wikisource.org/wiki/Seite:Die_Gartenlaube_%281865%29_703.jpg (sorry, i usually work in German wikisource) are mapped to <ref> blocks. Since they are from time to time a little bit longer there are paragraphs inside the footnodes. 
+
+Yes, <br /> enforces a line break but not indent of the following sentence.
+
+I am just wondering why there is a different treatment in references than in the normal text for ""normal"" paragraphs.",1381701183,PHID-USER-nrfhx7zwxqc7nau5uyyz,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Thanks for taking the time to report this!
+
+What is an example/real usecase to use paragraphs in references?
+
+As you wrote, a workaround is to insert a <br> to enforce a linebreak.
+
+[Resetting component, as ""Export/Import"" refers to ""Special:Export and Special:Import"" only.]",1381683169,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+VisualEditor: Broken link creation workflow,"I'm not sure exactly how I cause this bug but I've seen it twice now.
+
+Works somewhat like this:
+Click anywhere in the textarea and ensure there is whitespace before the cursor and nothing highlighted.
+
+Click the link button
+enter text, save it.
+
+The link doesn't get added anywhere and now clicking the link button to create a new link has no effect.
+
+I get JavaScript exception:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 6306
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381361640,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-epe55jgajl2jerw3siyg,task_description,declined
+VisualEditor: Broken link creation workflow,Can't replicate. Closing for now.,1396470649,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-epe55jgajl2jerw3siyg,task_subcomment,NA
+VisualEditor: Broken link creation workflow,"Yes, that exception only throws from one place, and the high number looks like it's trying to find a position beyond the end of the document, but I can't reproduce.",1382530303,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-epe55jgajl2jerw3siyg,task_subcomment,NA
+VisualEditor: Broken link creation workflow,Yeh I know.. I was hoping the Javascript exception would help debug somewhat. I managed to make it happen twice but haven't done so recently. Any clues from that exception to when it might occur?,1382468176,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-epe55jgajl2jerw3siyg,task_subcomment,NA
+VisualEditor: Broken link creation workflow,"This is difficult to look into without steps to reproduce. Let us know if you see it again, and how.",1382453865,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-epe55jgajl2jerw3siyg,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","On editing a page on mediawiki.org
+
+Navigated to
+https://www.mediawiki.org/wiki/Manual:Coding_conventions/CSS?veaction=edit#Less
+
+Looking in the console I see:
+Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist. 
+
+The save button is disabled.
+I only noticed this after doing a long edit :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://www.mediawiki.org/wiki/Manual:Coding_conventions/CSS?veaction=edit",1381190760,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ghws2ohsdojmmph4ub27,task_description,open
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Patch to disable SyntaxHighlight is now merged, so this problem will be suppressed with the production push tomorrow morning; restoring to ""ASSIGNED"".",1381370904,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Change 88901 merged by jenkins-bot:
+Remove SyntaxHighlight from the experimental set
+
+https://gerrit.wikimedia.org/r/88901",1381361800,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Change 88901 had a related patch set uploaded by Catrope:
+Remove SyntaxHighlight from the experimental set
+
+https://gerrit.wikimedia.org/r/88901",1381361398,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","This was because of breakage in MWSyntaxHighlightNode, and that page 1) contains such a node and 2) is on mw.org where MWSyntaxHighlightNode is actually enabled. This is experimental code that's only enabled on mw.org and nowhere else (although it will be available everywhere else as an opt-in once we get BetaFeatures going).",1381358788,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Oh, sorry, it's something about that page in particular - confirmed on Chromium 28, Ubuntu GNU/Linux 12.04",1381355681,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","WFM, Chromium 28 on Ubuntu GNU/Linux 12.04",1381355602,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist. load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%2Cs…:155
+ve.dm.Converter.getDomSubtreeFromData load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%2Cs…:155
+ve.dm.Converter.getDomFromData load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%2Cs…:148
+(anonymous function) load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.by…:94",1381190952,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""",Google Chrome Version 30.0.1599.69 and https://www.mediawiki.org/w/index.php?title=Manual:Coding_conventions/CSS&oldid=797048,1381190885,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""",ve.dm.Converter.js:1401,1381190833,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+VisualEditor: Clean up phantom mouse event code in ve.ce.ProtectedNode,"Currently, the mouse event handling in phantoms is:
+```lang=js
+// mouseenter on the protectednode
+ve.ce.ProtectedNode.prototype.onProtectedMouseEnter = function () {
+	if ( !this.root.getSurface().dragging ) {
+		this.createPhantoms();
+	}
+};
+
+// mousemove on the surface, bound by createPhantoms and unbound by clearPhantoms
+ve.ce.ProtectedNode.prototype.onSurfaceMouseMove = function ( e ) {
+	var $target = $( e.target );
+	if (
+		!$target.hasClass( 've-ce-protectedNode-phantom' ) &&
+		$target.closest( '.ve-ce-protectedNode' ).length === 0
+	) {
+		this.clearPhantoms();
+	}
+};
+
+// mouseout on the surface, bound by createPhantoms and unbound by clearPhantoms
+ve.ce.ProtectedNode.prototype.onSurfaceMouseOut = function ( e ) {
+	if ( e.toElement === null ) {
+		this.clearPhantoms();
+	}
+};
+```
+Issues:
+* the mousemove handler seems to permit moving the mouse directly to a different ProtectedNode without causing the phantoms to be cleared
+* the mouseout handler uses e.toElement, which is a poorly documented property that's allegedly IE-only
+* it's generally very difficult to reason about what this code does or convince oneself that it does something reasonable
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381185960,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mf6ollxu3yqurw4viu55,task_description,resolved
+VisualEditor: Clean up phantom mouse event code in ve.ce.ProtectedNode,"ProtectedNode became FocusableNode, and phantoms became highlights.
+
+
+> the mousemove handler seems to permit moving the mouse directly to a different ProtectedNode without causing the phantoms to be cleared
+
+This seems to be fixed in {138a7f862f24f66452ec2fd805ac43c53fbb583b}.
+
+> the mouseout handler uses e.toElement, which is a poorly documented property that's allegedly IE-only
+
+Big rewrite in {e1b0e33df7796ed41028aa04355b302e6559445b} changed that to use e.relatedTarget, which is legit, and basically the same (according to <http://help.dottoro.com/ljltrsom.php>).
+
+> it's generally very difficult to reason about what this code does or convince oneself that it does something reasonable
+
+This is still true, but I'm not sure if it's fixable :)
+
+
+>>! In T57448#597087, @Catrope wrote:
+> What's even worse is that if somehow another ProtectedNode does manage to show other phantoms, they will replace the first node's phantoms (because of the way ce.Surface manages phantoms), but if for some reason clearPhantoms() isn't called, the first node will continue to track the now-detached phantoms and reposition them when a transaction occurs.
+
+This might still be a problem.",1579119330,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mf6ollxu3yqurw4viu55,task_subcomment,NA
+VisualEditor: Clean up phantom mouse event code in ve.ce.ProtectedNode,"What's even worse is that if somehow another ProtectedNode does manage to show other phantoms, they will replace the first node's phantoms (because of the way ce.Surface manages phantoms), but if for some reason clearPhantoms() isn't called, the first node will continue to track the now-detached phantoms and reposition them when a transaction occurs.",1381186300,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mf6ollxu3yqurw4viu55,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Right now the way that you add a template through the VisualEditor is by choosing the Transclusion option from the toolbar.
+
+'Transclusion' is programmer jargon. Regular people have no idea what that means. 'Template' is a somewhat ambiguous term, but at least it matches all of our documentation and the name of the namespace. It is also less scary sounding.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381170240,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-t7swuomd63q7e3mou7kp,task_description,resolved
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","> 'Transclusion' is programmer jargon. Regular people have no idea what that means.
+
+ =/",1420450176,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","> 'Transclusion' is programmer jargon. Regular people have no idea what that means.
+
+=/",1398701048,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","(In reply to Helder from comment #5)
+> Created attachment 15228 [details]
+> Transclusion vs. Template
+> 
+> I'm still seeing a few ""transclusion"" in the dialogs, on English Wikipedia.
+
+Transclusion dialog != template dialog; transclusion = multiple template dialog.
+
+**Attached**: {F11988}",1398700163,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Created attachment 15228
+Transclusion vs. Template
+
+I'm still seeing a few ""transclusion"" in the dialogs, on English Wikipedia.
+
+**Attached**: {F11988}",1398683755,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Change 117151 merged by jenkins-bot:
+Re-label ""Transclusion"" button to ""Template"", as that's now the default
+
+https://gerrit.wikimedia.org/r/117151",1394075228,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Change 117151 had a related patch set uploaded by Jforrester:
+Re-label ""Transclusion"" button to ""Template"", as that's now the default
+
+https://gerrit.wikimedia.org/r/117151",1394073856,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions",*** Bug 58163 has been marked as a duplicate of this bug. ***,1393525848,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Eh. Maybe. We've been talking about this for months and months (surprised that there's not an extant bug for this). The problem is that though ""transclusion"" is indeed confusing and a surprising word, it has the advantage of being correct, and  ""template"" is even more confusing (and just jargon from a different well).",1381171497,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+VisualEditor: Wikitext diff is not regenerated if VE content is the same but the page has subsequently changed,"+++ This bug was initially created as a clone of Bug #55392 +++
+
+VE caches the diff, which means if no content is changed, the user is shown
+a) a stale diff and is allowed to proceed with saving the page, which means they are then
+b) the page with their saved changes only
+The user is unaware that they have overwritten another persons changes.
+
+Steps to reproduce:
+1. Create a page with some two lines
+   https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=573748285
+2. Open the page in two VE windows
+3. In the second window, alter the first line and save
+   https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=576079696
+5. In the first window, alter the first line and review changes
+   (the diff only shows the first line being modified
+    against the page contents from step 3)
+6. In the second window, add some lines and save
+   https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=576079807
+7. In the first window, review changes, and cancel the save
+   (the diff is the same as in step 5; the VE page content doesnt change)
+8. In the first window, save
+
+Expected results:
+In step 7, the diff should be refreshed even though the page content has not been modified.
+
+Actual results:
+The diff from step 5 is displayed in step 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55392",1381115640,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-kfr2fhuhxwwkvqg5jwuw,task_description,open
+VisualEditor: Wikitext diff is not regenerated if VE content is the same but the page has subsequently changed,"At bug 55392 comment 3 James says that in core mediawiki functionality ""you can't edit conflict with yourself, and new edits silently over-write"", which could mean this bug is also the correct behaviour.  Need to retest with two different users.",1399697381,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-kfr2fhuhxwwkvqg5jwuw,task_subcomment,NA
+VisualEditor: Wikitext diff is not regenerated if VE content is the same but the page has subsequently changed,This might be a Parsoid issue?,1381118185,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-kfr2fhuhxwwkvqg5jwuw,task_subcomment,NA
+VisualEditor: The link suggestor should suggest links from the current namespace ahead of named links,"If the user is editing a content namespace, the link dialog should search the current namespace first, then all other content namespaces, when looking for link targets.
+
+Steps to reproduce
+1. https://www.mediawiki.org/wiki/Manual:Page_table?veaction=edit
+2. Write and select 'archive table'
+3. Open link dialog
+
+Expected results:
+Link target 'manual:archive table' automatically found
+
+Actual results:
+Link target 'archive table' (new page) is automatically provided
+
+The same is needed for Wikisource which has, e.g. an Author: content namespace.
+
+Wikipedias with a content namespace listed in InitialiseSettings.php:
+Arabic Wikipedia : T22623
+  https://ar.wikipedia.org/wiki/%D8%AE%D8%A7%D8%B5:%D9%81%D9%87%D8%B1%D8%B3_%D8%A8%D8%A7%D8%AF%D8%A6%D8%A9/%D9%85%D9%84%D8%AD%D9%82:
+Spanish Wikipedia : T41866
+  https://es.wikipedia.org/wiki/Especial:P%C3%A1ginasPorPrefijo/Anexo:
+North Frisian Wikipedia: T40023
+  (Wikisource inside Wikipedia)
+Croatian Wikipedia: T42732
+  https://hr.wikipedia.org/wiki/Posebno:Prefiks_indeks/Dodatak:
+Portuguese Wikipedia:
+  https://pt.wikipedia.org/wiki/Especial:%C3%8Dndice_por_prefixo/Anexo:
+
+(and more potential ones listed at T41866)
+
+As an aside, in 'Help' namespace, which isnt set as a content namespace, it would be nice to search within that namespace when linking, but that is a more blurry line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T71780}
+{T57390}
+{T64917}
+{T71716}",1381111920,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cfrutsorovcrc76vfomh,task_description,open
+"VisualEditor: Inserted objects (references, templates, images) should not be selected after insertion","**Author:** `Wikifram`
+
+**Description:**
+When you add a reference, it is automatically selected (blue), instead of having the cursor positioned directly after it (or better still, with a space after the ref and the cursor after that). The effec is that if you enter a ref and then start typing (which is rather normal editing behaviour), your ref immediately gets removed (overwritten) again, which makes it rather pointless. 
+
+I think that it is much more often the intention to continue typing after adding a ref, than to have it highlighted, so please change the default behaviour.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1380869940,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4yohlm5rptv4jnlli5mk,task_description,resolved
+"VisualEditor: Inserted objects (references, templates, images) should not be selected after insertion","Change 100522 merged by jenkins-bot:
+Don't select nodes inserted by a dialog, but drop cursor after
+
+https://gerrit.wikimedia.org/r/100522",1386793552,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4yohlm5rptv4jnlli5mk,task_subcomment,NA
+"VisualEditor: Inserted objects (references, templates, images) should not be selected after insertion","Change 100522 had a related patch set uploaded by Catrope:
+Don't select nodes inserted by a dialog, but drop cursor after
+
+https://gerrit.wikimedia.org/r/100522",1386641138,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4yohlm5rptv4jnlli5mk,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","When the text of a link is changed in VisualEditor, the link target does not change. This results in many, many edits which are entirely well-intentioned but for a patroller look like vandalism. E.g. a user tries to fix the wrong date `[[2000]]` and ends up with `[[2000|2001]]` - an erroneous link that is basically impossible to catch in visual view. (Some examples: [[https://de.wikipedia.org/w/index.php?title=Osmium(IV)-oxid&diff=prev&oldid=122526489|diff]], [[https://hu.wikipedia.org/w/index.php?title=Lengyelorsz%C3%A1g_f%C3%B6ldrajza&diff=19527995&oldid=18755093|diff]]) This is a major problem; even highly experienced users fall prey to this, and new editors all the more (and then they get treated as vandals by the patrollers who are not familiar with VE and have no idea what's going on).
+
+Maybe there could be some sort of notice asking whether the editor also wants to correct the actual target in case they change the displayed part of a wikilink (T55973#2792012 has a nice mockup).
+
+On-wiki reports:
+[[https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=123123378#Wikilink-Korrektur|Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07#Wikilink-Korrektur]]
+[[https://hu.wikipedia.org/wiki/Wikipédia:Kocsmafal_(egyéb)/Archív250#VisualEditor-hiba%3A_megtévesztő_belső_hivatkozások_létrehozása|Wikipédia:Kocsmafal_(egyéb)#VisualEditor-hiba: megtévesztő belső hivatkozások létrehozása]]
+
+See Also:
+* {T59506}
+* {T55973}",1380841680,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-muxtuy47vttbiujlra5y,task_description,open
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#6657213, @Tgr wrote:
+>>>! In T56947#6654187, @Esanders wrote:
+>> The volume in the above mentioned edit filter (T56947#2098243) would be a good metric for success. It might be useful to have it on more high volume wikis.
+> 
+> Note that the filter only catches changes to dates (which is a good way to avoid false positives, but it avoids the vast majority of true positives too). So it's a good way of measuring whether problematic edits become less frequent, but not a good way of measuring how frequent they are, in an absolute sense.
+
+In addition to the abuse filter, I also generate twice a month a dump analysis which gets a bit more than the filter (same as in my post above) :
+
+
+  - On [[ https://en.wikipedia.org/wiki/Wikipedia:CHECKWIKI/WPC_526_dump | enWP ]]
+  - On [[ https://fr.wikipedia.org/wiki/Projet:Correction_syntaxique/Analyse_526 | frWP ]]
+
+",1606769955,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#6657213, @Tgr wrote:
+>>>! In T56947#6654187, @Esanders wrote:
+>> The volume in the above mentioned edit filter (T56947#2098243) would be a good metric for success. It might be useful to have it on more high volume wikis.
+> 
+> Note that the filter only catches changes to dates (which is a good way to avoid false positives, but it avoids the vast majority of true positives too). So it's a good way of measuring whether problematic edits become less frequent, but not a good way of measuring how frequent they are, in an absolute sense.
+
+In addition to the abuse filter, I also generate dump twice a month a dump analysis which gets a bit more than the filter (same as in my post above) :
+
+
+  - On [[ https://en.wikipedia.org/wiki/Wikipedia:CHECKWIKI/WPC_526_dump | enWP ]]
+  - On [[ https://fr.wikipedia.org/wiki/Projet:Correction_syntaxique/Analyse_526 | frWP ]]
+
+",1606769924,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#6654173, @Esanders wrote:
+> Since this was last discussed we added the label editing field to mobile VE.
+> 
+> I think bringing that interface over to desktop would make these mistakes much less common as whenever you edit the link target, the link label is shown in an editable field right next to it.
+> 
+> By removing the existing edit label button that just puts the cursor into the surface, we would also push label editors to the same interface. Complex annotated labels could still be edited in the surface.
+
+I think that would be an improvement for experienced users as well, the current desktop approach for changing the label doesn't work that well. (This is worse for external links, where you end up with an uneditable `[1]` that you cannot change at all without involving the mouse, but normal links have some annoying mechanics as well.)
+
+>>! In T56947#6654187, @Esanders wrote:
+> The volume in the above mentioned edit filter (T56947#2098243) would be a good metric for success. It might be useful to have it on more high volume wikis.
+
+Note that the filter only catches changes to dates (which is a good way to avoid false positives, but it avoids the vast majority of true positives too). So it's a good way of measuring whether problematic edits become less frequent, but not a good way of measuring how frequent they are, in an absolute sense.",1606769045,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",The volume in the above mentioned edit filter (T56947#2098243) would be a good metric for success. It might be useful to have it on more high volume wikis.,1606653159,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Since this was last discussed we added the label editing field to mobile VE.
+
+I think bringing that interface over to desktop would make these mistakes much less common as whenever you edit the link target, the link label is shown in an editable field right next to it.
+
+By removing the existing edit label button that just puts the cursor into the surface, we would also push label editors to the same interface. Complex annotated labels could still be edited in the surface.",1606652304,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",And 2021: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Editing/Unintentional_false_links_in_VE,1606651924,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",Relevant Community Wishlist entry: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Editing/Avoid_VisualEditor_edits_changing_only_the_link_text_or_only_the_link_target,1543306882,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",T55973#2792012 may interest some of the followers of that task.,1479143554,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","On frwiki, the problem appeared in the following pages between the February and March dump, I haven't checked what is the proportion of VE edits.
+Problems with only [[1990|2000]] are not listed here but can be found with the abuse filter
+https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Journal_du_filtre_antiabus&wpSearchFilter=241
+
+* [[3 Mustaphas 3]]: <nowiki>[[1990 en musique|1986]]</nowiki>
+* [[Alexandra Lacrabère]]: <nowiki>[[2016 en handball|2014]]</nowiki>
+* [[Alexondra Lee]]: <nowiki>[[2012 au cinéma|1998]]</nowiki>
+* [[Anaïs Delva]]: <nowiki>[[2014 à la télévision|2015]]</nowiki>
+* [[Andra Akers]]: <nowiki>[[1978 à la télévision|1979]]</nowiki>
+* [[Andy Samberg]]: <nowiki>[[2016 au cinéma|2013]]</nowiki>
+* [[Annapolis]]: <nowiki>[[2010 aux États-Unis|2000]]</nowiki>
+* [[Anne-Violaine Brisou]]: <nowiki>[[2010 en sports équestres|2009]]</nowiki>
+* [[Arthur Brown (musicien)]]: <nowiki>[[1992 en musique|1993]]</nowiki>
+* [[Baudouin Taslé d'Héliand]]: <nowiki>[[2011|2016]]</nowiki>, <nowiki>[[2011|2015]]</nowiki>, <nowiki>[[2011|2013]]</nowiki>, <nowiki>[[2011|2012]]</nowiki>
+* [[Billy Talent]]: <nowiki>[[2001 en musique|1999]]</nowiki>
+* [[Boris Tokarev (acteur)]]: <nowiki>[[1967 au cinéma|1976]]</nowiki>
+* [[Bruno Léandri]]: <nowiki>[[2014|2015]]</nowiki>
+* [[Carlos Edwards]]: <nowiki>[[2008 en football|2011]]</nowiki>, <nowiki>[[2014 en football|2011]]</nowiki>
+* [[Cesare Danova]]: <nowiki>[[1980 à la télévision|1981]]</nowiki>
+* [[Chair de poule (film)]]: <nowiki>[[2015 au cinéma|2016]]</nowiki>
+* [[Charles Chaynes]]: <nowiki>[[1995 en musique|1958]]</nowiki>
+* [[Charlie Rowe]]: <nowiki>[[2006 à la télévision|200]]</nowiki>
+* [[Claude Mann]]: <nowiki>[[2014 au théâtre|2015]]</nowiki>
+* [[Claude Scasso]]: <nowiki>[[2015 à la télévision|2016]]</nowiki>
+* [[Claudio Lemmi]]: <nowiki>[[2007 au théâtre|2008]]</nowiki>, <nowiki>[[2006 au théâtre|2007]]</nowiki>, <nowiki>[[2011 au théâtre|2012]]</nowiki>
+* [[Club Atlético San Lorenzo de Almagro]]: <nowiki>[[2016 en football|2015]]</nowiki>
+* [[Construction navale]]: <nowiki>[[1631|1931]]</nowiki>
+* [[Coupe de Tunisie de football (FFF)]]: <nowiki>[[1921 en sport|1922]]</nowiki>
+* [[Courrier international]]: <nowiki>[[2014|2015]]</nowiki>
+* [[Croc-Blanc]]: <nowiki>[[1992 au cinéma|1991]]</nowiki>
+* [[David Zucker]]: <nowiki>[[1993 au cinéma|1983]]</nowiki>
+* [[Dominika Minicz]]: <nowiki>[[2001 en sport|2003]]</nowiki>
+* [[Drowning Pool]]: <nowiki>[[2013 en musique|2016]]</nowiki>
+* [[Du Caurroy]]: <nowiki>[[1750|1850]]</nowiki>
+* [[Dunkerque Handball Grand Littoral]]: <nowiki>[[1992 en handball|1978]]</nowiki>
+* [[Déborah Heissler]]: <nowiki>[[2005 en littérature|2004]]</nowiki>
+* [[En dépit des étoiles]]: <nowiki>[[2016 en littérature|2013]]</nowiki>
+* [[Ermin Šiljak]]: <nowiki>[[1999 en football|1998]]</nowiki>, <nowiki>[[2000 en football|2001]]</nowiki>
+* [[François Guérin (réalisateur)]]: <nowiki>[[2011 au cinéma|2000]]</nowiki>
+* [[Frédéric Gaillard]]: <nowiki>[[2006 en football|2008]]</nowiki>
+* [[Fury Records]]: <nowiki>[[1957 en musique|1987]]</nowiki>, <nowiki>[[1957 en musique|1987]]</nowiki>
+* [[Fédération camerounaise de football]]: <nowiki>[[2012|2013]]</nowiki>
+* [[Gaëtan Vassart]]: <nowiki>[[2015 au théâtre|2016]]</nowiki>
+* [[Georges Beuret]]: <nowiki>[[1800|1803]]</nowiki>
+* [[Gianluigi Buffon]]: <nowiki>[[1987 en football|1997]]</nowiki>
+* [[Grand Corps Malade]]: <nowiki>[[2014 en littérature|2012]]</nowiki>
+* [[Guerre FISA-FOCA]]: <nowiki>[[1978 en sport automobile|1979]]</nowiki>
+* [[Heidi]]: <nowiki>[[1937 au cinéma|1973]]</nowiki>
+* [[Hervé Jolly]]: <nowiki>[[1990 au cinéma|1991]]</nowiki>, <nowiki>[[1991 au cinéma|1990]]</nowiki>
+* [[Hot Rod (rappeur)]]: <nowiki>[[2010 en musique|2011]]</nowiki>
+* [[Houari Ferhani]]: <nowiki>[[2013 en football|2014]]</nowiki>
+* [[Hugo Moulinier]]: <nowiki>[[2008 en sport|2013]]</nowiki>
+* [[Ion Ansotegui]]: <nowiki>[[2003 en football|2016]]</nowiki>
+* [[Ismaël Bangoura]]: <nowiki>[[2013 en football|2016]]</nowiki>
+* [[Jaime Penedo]]: <nowiki>[[2005 en football|2006]]</nowiki>
+* [[James LeGros]]: <nowiki>[[2015 au cinéma|2016]]</nowiki>
+* [[Jamie Lee Curtis]]: <nowiki>[[1983 au cinéma|1984]]</nowiki>
+* [[Jardin botanique de Liège]]: <nowiki>[[2010|2016]]</nowiki>
+* [[Jason Bard]]: <nowiki>[[1939 en bande dessinée|1969]]</nowiki>
+* [[Jean Arp]]: <nowiki>[[2005|2014]]</nowiki>
+* [[Jean Sagols]]: <nowiki>[[1988 à la télévision|1989]]</nowiki>
+* [[Jean-Paul Daoust]]: <nowiki>[[2015 en littérature|2016]]</nowiki>
+* [[Joe Stone]]: <nowiki>[[2015 en musique|2013]]</nowiki>
+* [[John Kenneth Galbraith]]: <nowiki>[[1979 en littérature|1980]]</nowiki>
+* [[Jon Abrahams]]: <nowiki>[[2004 au cinéma|2005]]</nowiki>, <nowiki>[[2007 au cinéma|2009]]</nowiki>, <nowiki>[[2008 au cinéma|2009]]</nowiki>, <nowiki>[[2013 au cinéma|2014]]</nowiki>
+* [[Jovan Ćurčić]]: <nowiki>[[1995 en football|1976]]</nowiki>, <nowiki>[[1996 en football|1977]]</nowiki>
+* [[Jérôme L'Hotsky]]: <nowiki>[[2013 au cinéma|2012]]</nowiki>
+* [[Kaamelott]]: <nowiki>[[2015 en bande dessinée|2017]]</nowiki>
+* [[Kaisa Alanko]]: <nowiki>[[2013 en sport|2016]]</nowiki>
+* [[Katé-Mé]]: <nowiki>[[1995 en musique|1996]]</nowiki>
+* [[Khalid Karami]]: <nowiki>[[2002 en football|2004]]</nowiki>, <nowiki>[[2011 en football|2005]]</nowiki>, <nowiki>[[2001 en football|2005]]</nowiki>, <nowiki>[[2012 en football|2011]]</nowiki>
+* [[Kora Jazz Band]]: <nowiki>[[2015 en musique|2014]]</nowiki>
+* [[Krawatencross]]: <nowiki>[[2004 en cyclisme|2016]]</nowiki>, <nowiki>[[2004 en cyclisme|2016]]</nowiki>
+* [[L'Amour des trois oranges (opéra)]]: <nowiki>[[1950 en musique classique|1961]]</nowiki>
+* [[La Garçonnière (film, 1960)]]: <nowiki>[[1995 en littérature|1996]]</nowiki>
+* [[La Guerre de Caliban]]: <nowiki>[[2015 en littérature|2016]]</nowiki>
+* [[Lamine Ndao]]: <nowiki>[[2011 en football|2013]]</nowiki>, <nowiki>[[2011 en football|2013]]</nowiki>
+* [[Laurent Bouhnik]]: <nowiki>[[1999 au cinéma|1998]]</nowiki>
+* [[Laurent Courtiaud]]: <nowiki>[[2010 au cinéma|2011]]</nowiki>
+* [[Liste des présidents de la République d'Angola]]: <nowiki>[[1992|1979]]</nowiki>
+* [[Lorie Pester]]: <nowiki>[[2005 au cinéma|2004]]</nowiki>
+* [[Luke Grimes]]: <nowiki>[[2018 au cinéma|2017]]</nowiki>
+* [[Léon Cordes]]: <nowiki>[[1969|1974]]</nowiki>, <nowiki>[[1977|1974]]</nowiki>
+* [[M. Chapoutier]]: <nowiki>[[1879|1808]]</nowiki>
+* [[Malika Wagner]]: <nowiki>[[2010 en littérature|2016]]</nowiki>
+* [[Marc Renard]]: <nowiki>[[2008 en littérature|2016]]</nowiki>
+* [[Marcilio]]: <nowiki>[[2014 en sport|2042]]</nowiki>
+* [[Marco Motta]]: <nowiki>[[2016 en football|2015]]</nowiki>
+* [[Marilyne Canto]]: <nowiki>[[1977 au cinéma|1978]]</nowiki>
+* [[Meaghan Rath]]: <nowiki>[[2015 à la télévision|2016]]</nowiki>
+* [[Mickey 3D]]: <nowiki>[[1999 en musique|1998]]</nowiki>, <nowiki>[[2015 en musique|2006]]</nowiki>, <nowiki>[[2015 en musique|2009]]</nowiki>, <nowiki>[[2015 en musique|2010]]</nowiki>, <nowiki>[[2015 en musique|2010]]</nowiki>, <nowiki>[[2015 en musique|2016]]</nowiki>
+* [[Mini-Star]]: <nowiki>[[1982 en musique|1983]]</nowiki>
+* [[NGC 271]]: <nowiki>[[1798|1785]]</nowiki>
+* [[Nicky Jam]]: <nowiki>[[2015|2014]]</nowiki>, <nowiki>[[2015|2014]]</nowiki>
+* [[Néstor Ortigoza]]: <nowiki>[[2011 en football|2010]]</nowiki>, <nowiki>[[2011 en football|2012]]</nowiki>
+* [[Pascal Brissy]]: <nowiki>[[2003 en littérature|2001]]</nowiki>
+* [[Patrick Béthune]]: <nowiki>[[2002 au cinéma|2009]]</nowiki>
+* [[Patrick Timsit]]: <nowiki>[[2016|2017]]</nowiki>
+* [[Paul Barge (1941- )]]: <nowiki>[[1970 à la télévision|1980]]</nowiki>
+* [[Petr Zelenka]]: <nowiki>[[2005 au cinéma|2015]]</nowiki>
+* [[Peugeot 305]]: <nowiki>[[1989|1990]]</nowiki>
+* [[Pierre Douglas]]: <nowiki>[[1979 au cinéma|1975]]</nowiki>
+* [[Princes et Princesses]]: <nowiki>[[1999 au cinéma|2000]]</nowiki>
+* [[Raouf Benguit]]: <nowiki>[[2008 en football|2013]]</nowiki>, <nowiki>[[2015 en football|2014]]</nowiki>
+* [[Raphaël Didjaman]]: <nowiki>[[2012|2015]]</nowiki>, <nowiki>[[2012|2016]]</nowiki>
+* [[Raymond Ochoa]]: <nowiki>[[2013 au cinéma|2015]]</nowiki>
+* [[Reem Kherici]]: <nowiki>[[2014 au cinéma|2016]]</nowiki>
+* [[Rencontres d'Arles]]: <nowiki>[[1985 en photographie|1982]]</nowiki>
+* [[Rick Hoffman]]: <nowiki>[[2010 à la télévision|2000]]</nowiki>
+* [[Rihanna]]: <nowiki>[[2005 en musique|2004]]</nowiki>
+* [[Robert Walser (écrivain)]]: <nowiki>[[1916 en littérature|1917]]</nowiki>
+* [[Rocky Balboa (film)]]: <nowiki>[[2014 au cinéma|2015]]</nowiki>
+* [[Romain Dumas]]: <nowiki>[[2014 en sport|2015]]</nowiki>
+* [[Santigold]]: <nowiki>[[2015 en musique|2016]]</nowiki>
+* [[Slobodan Rajković]]: <nowiki>[[2005 en football|2006]]</nowiki>
+* [[Srđan Ristić]]: <nowiki>[[2001 en sport|2006]]</nowiki>, <nowiki>[[2008 en sport|2009]]</nowiki>, <nowiki>[[2010 en sport|2014]]</nowiki>
+* [[Swamp Thing]]: <nowiki>[[2013 en bande dessinée|2014]]</nowiki>, <nowiki>[[2013 en bande dessinée|2015]]</nowiki>
+* [[Sylvain Marchal]]: <nowiki>[[2015 en football|2016]]</nowiki>
+* [[Taken (série télévisée)]]: <nowiki>[[2007 au cinéma|2015]]</nowiki>
+* [[Tallac Records]]: <nowiki>[[2012 en musique|2135]]</nowiki>
+* [[Thierry Westermeyer]]: <nowiki>[[2004 en musique|2001]]</nowiki>
+* [[Umberto Eco]]: <nowiki>[[2000 en littérature|1988]]</nowiki>, <nowiki>[[2004 en littérature|2009]]</nowiki>
+* [[Under Two Flags]]: <nowiki>[[1867 en littérature|1897]]</nowiki>
+* [[Université de La Rochelle]]: <nowiki>[[2008|2016]]</nowiki>
+* [[VfL Wolfsbourg]]: <nowiki>[[2005 en football|2015]]</nowiki>
+* [[Villa La Reine Jeanne]]: <nowiki>[[1928|1933]]</nowiki>
+* [[Villiers-Saint-Georges]]: <nowiki>[[2001 en France|2008]]</nowiki>, <nowiki>[[2008 en France|2014]]</nowiki>
+* [[Vladimir Venguerov]]: <nowiki>[[1954 au cinéma|1945]]</nowiki>
+* [[William Séry]]: <nowiki>[[2013 en football|2014]]</nowiki>
+* [[Yann Arthus-Bertrand]]: <nowiki>[[2012 en littérature|2015]]</nowiki>, <nowiki>[[2012 en littérature|2015]]</nowiki>
+* [[Yuma (Arizona)]]: <nowiki>[[2008|2010]]</nowiki>
+* [[Yusef Lateef]]: <nowiki>[[2005|1989]]</nowiki>
+* [[Zakaria Haddouche]]: <nowiki>[[2011 en football|2013]]</nowiki>
+* [[Álvaro Magalhães]]: <nowiki>[[1980 en football|1981]]</nowiki>
+* [[Éditions À la carte]]: <nowiki>[[2012 en Suisse|2016]]</nowiki>
+",1457426012,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Elitre 
+Yes.
+
+For the 1st and 3rd, I know, but there are only a few articles in these cases (5 of them exactly in total). And they appear at the beginning of the list, because they are recognized as special and my bot didn't flag them with {{Lien à corriger}}... So none of them appear in the dedicated category ""Article avec un lien à corriger"", and are not counted in the ""more than 6.000 articles""
+
+For the 2nd, I never said that all errors were due to VE, but most of them are. We are still talking about thousands of VE mistakes
+",1457350363,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Elitre 
+Yes.
+
+For the 1st and 3rd, I know, but there are only a dozen of articles in these cases. And they appear at the beginning of the list, because they are recognized as special and my bot didn't flag them with {{Lien à corriger}}... So none of them appear in the dedicated category ""Article avec un lien à corriger"", and are not counted in the ""more than 6.000 articles""
+
+For the 2nd, I never said that all errors were due to VE, but most of them are. We are still talking about thousands of VE mistakes
+",1457349845,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","(Just a quick comment about the query linked above:
+it includes links to pages [[ https://fr.wikipedia.org/w/index.php?title=Accident_ferroviaire_de_Zoufftgen&type=revision&diff=104207507&oldid=104207037 | which are not years and not added by mistake]];
+it includes pages where [[ https://fr.wikipedia.org/w/index.php?title=1._FC_Neubrandenburg_04&action=edit&oldid=62013397 | the visual editor was never used, and the mistake is almost certainly a typo]];
+it includes pages where [[ https://fr.wikipedia.org/w/index.php?title=Nombre_de_Markov&action=edit&oldid=12476390 | the visual editor was never used, and the editor seems to have made a deliberate choice about the link target]].
+There may be more, I'm not going to dig deeper though.)",1457349108,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF
+In addition to the abuse filter that was put in place last year, I've also recently run a bot on a dump from frwiki to find the incorrect links to pages related to years like [[2000|2015]] or [[2000 en musique|2015]].
+Result is at https://fr.wikipedia.org/wiki/Projet:Correction_syntaxique/Analyse_526
+
+Analysis on February dump found more than 6.000 articles with this kind of problem (and it's only for years related links, we are probably missing the majority of incorrect links)
+
+I've then run a bot to add a warning after each problematic link with a template
+https://fr.wikipedia.org/wiki/Mod%C3%A8le:Lien_%C3%A0_corriger
+It displays a warning message and puts the article in a tracking category
+https://fr.wikipedia.org/wiki/Cat%C3%A9gorie:Article_avec_un_lien_%C3%A0_corriger
+
+It helped reduce the number of articles with this problem to about 5.400 articles
+
+This shows that this problem is far from being anedoctic (and I don't know how to evaluate how many articles have the same problem, but not for links related to years)",1457221150,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Maybe whenever someone changes the link text which initially was the same as the link target, and the new link text is the name of an existing article, show a small warning in some easy-to-notice color in the link widget saying ""[click here] to update the link target as well""?",1457220558,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","+1 to //that ""better"" method is live, and we still have this problem//.
+",1457220364,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF
+Only for links to years which are easy to detect by a filter and (almost ?) always an error
+https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Filtre_antiabus/241",1432644594,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",@NicoV:  Isn't there an edit filter on the French Wikipedia that would show every time this happens?,1432576409,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#1294934, @Neil_P._Quinn_WMF wrote:
+>>>! In T56947#1294891, @Amire80 wrote:
+>> I may be missing something, but to me it's pretty obvious that changing the blue text ""2010"", which happens to point to [[2010]], to ""2015"" must change the link target to [[2015]].
+> 
+> @Amire80, are you suggesting that when a link has the same text and target (e.g. [[2010]]), changing the text should automatically change the target? Consider that this would make it //impossible// to change, for example, [[Impressionism]] to [[Impressionism|Impressionist]].
+
+It won't be impossible if the inspector is shown, as it already is. An editor who really wants to change the text, but leave the target, can use the inspector to change it.
+
+What I'm saying is that common sense tells me that when when the text and the target are the same and the text is changed, the target should be changed by default automatically. It makes little sense to alert the user that the target should be changed, because it's likely that that's what the user wants anyway, and double work should be avoided. It there's any alert, then it should be about the opposite: that maybe the user wants to //keep// the target.",1432121178,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Another pretty common mistake I find is people modifying [[Wikipedia]] to [[Wikipedia|Wiki]]pedia (probably a drag and drop problem).
+Sometimes I see also [[Wikipedia|wikipedia]] or [[wikipedia|Wikipedia]] (VE seems to ignore first letter is case insensitive).
+Finally I seldom (let's say less than 20 occurrences per month) find [[Wikipedia|Wikipedia]], still wrong but easy to fix via bot.",1432052602,PHID-USER-irgoyfmq4qktx4ueexfk,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#1294891, @Amire80 wrote:
+> I may be missing something, but to me it's pretty obvious that changing the blue text ""2010"", which happens to point to [[2010]], to ""2015"" must change the link target to [[2015]].
+
+@Amire80, are you suggesting that when a link has the same text and target (e.g. [[2010]]), changing the text should automatically change the target? Consider that this would make it //impossible// to change, for example, [[Impressionism]] to [[Impressionism|Impressionist]].",1431984454,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","I may be missing something, but to me it's pretty obvious that changing the blue text ""2010"", which happens to point to [[2010]], to ""2015"" must change the link target to [[2015]].",1431982566,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF, to what //extent// do we still have this problem? Now, anytime your cursor is within a link range, you get a big popup showing the target, along with a helpful picture in many cases; I'm not sure how much more visible it's possible to make the target without making it severely distracting.
+
+At any rate, if it still is a major problem and we decide it needs to be addressed, I feel strongly that a more fundamental design change, not a reminder popup, would be the right solution. When a user type `<ref>`, for example, we don't bring up a comment saying: ""Did you mean to add a reference?"". We just pop up the citation dialog.",1431981263,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF, to what //extent// do we still have this problem? Now, anytime your cursor is within a link range, you get a big popup showing the target, along with a helpful picture in many cases; I'm not sure how much more visible it's possible to make the target without making it severely distracting.",1431981065,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF, to what extent do we still have this problem? Now, anytime your cursor is within a link range, you get a big popup showing the target, along with a helpful picture in many cases; I'm not sure how much more visible it's possible to make the target without making it severely distracting.",1431981051,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#1266454, @Whatamidoing-WMF wrote:
+> Okay, that ""better"" method is live, and we still have this problem.  
+> 
+> We need people (especially experienced editors) to be warned that this is happening.  When they see [[2010]], and they change the visible ""2010"" part to say ""2015"", they expect the result to be [[2015]], not [[2010|2015]].
+> 
+> Solutions could be a soft warning, like asking ""Do you want to change the destination link to match?"", but sirens and flashing lights and a blinking banner that says something like ""DANGER, WILL ROBINSON!  IT LOOKS ALL RIGHT ON YOUR SCREEN, BUT THE ACTUAL LINK IS STILL SECRETLY GOING TO THE ORIGINAL PAGE!!"" would be good, too.
+
+imo, solution should not be ""soft warning"". solution should be something like
+""internal links are not directly editable on page. when editor tries to edit an internal link, popup the ""link"" tool instead"".
+
+peace.",1431449887,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Okay, that ""better"" method is live, and we still have this problem.  
+
+We need people (especially experienced editors) to be warned that this is happening.  When they see [[2010]], and they change the visible ""2010"" part to say ""2015"", they expect the result to be [[2015]], not [[2010|2015]].
+
+Solutions could be a soft warning, like asking ""Do you want to change the destination link to match?"", but sirens and flashing lights and a blinking banner that says something like ""DANGER, WILL ROBINSON!  IT LOOKS ALL RIGHT ON YOUR SCREEN, BUT THE ACTUAL LINK IS STILL SECRETLY GOING TO THE ORIGINAL PAGE!!"" would be good, too.",1430942372,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",This will be done better via {T88337}.,1424911487,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Merged in a bunch of duplicates. T63558 might be another one (not sure).
+Proposing for potential VE Q3 Blocker due to the numerous duplicates (but feel free to punt).",1424371535,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","I am a bit of a VE ambassador in the Hebrew Wikipedia and an experienced user asked me about this today. I know there are over a thousand other bugs and I don't mean to nudge, but this keeps coming up and I am curious whether this is considered as a needed feature on a product design level.",1409122552,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",*** Bug 57506 has been marked as a duplicate of this bug. ***,1400106756,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Changing links is unintuitive -- user changes link text, but that dosen't change link target --see also this diff https://et.wikipedia.org/w/index.php?title=Joel_Luhamets&diff=3899205&oldid=3861224",1398576932,PHID-USER-hxt4ak6xrngllg2dof3u,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: Make the isRedirect disable check look at the revision being considered, not current revision","When a page is currently a redirect, but has none-redirect versions in its history those versions should be editable in VE but are not. e.g. https://en.wikipedia.org/w/index.php?title=Equality_Acts&oldid=570457856
+
+To reproduce:
+1. Load any page that is not a redirect in the source editor
+2. Change the page into a redirect and save
+3. View any revision prior to the redirect
+
+Expected behaviour: Old version is editable in VE
+Action behaviour: No option is given to edit in VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50878",1380813300,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-yuoxq5n2ii32plugotg4,task_description,invalid
+"VisualEditor: Make the isRedirect disable check look at the revision being considered, not current revision","We no longer stop editing of isRedirect pages, so marking as INVALID now.",1398706803,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yuoxq5n2ii32plugotg4,task_subcomment,NA
+"VisualEditor: Make the isRedirect disable check look at the revision being considered, not current revision","I'm not sure how easy this would be to do... It appears to be based on MediaWiki core's wgIsRedirect, which would need fixing to work out whether the current revision is a redirect (instead of the latest revision of the current page). I'm not sure core even has a function to work that out at the moment. Even in the database, the field to determine if something is a redirect is in the page table instead of the revision table.",1390956621,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-yuoxq5n2ii32plugotg4,task_subcomment,NA
+"VisualEditor: Make the isRedirect disable check look at the revision being considered, not current revision","Will be superseded by bug 50878 once bug 47328 is implemented, but could be done sooner if someone is keen.",1380834030,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yuoxq5n2ii32plugotg4,task_subcomment,NA
+Ability to change preferences without leaving current page,"When a user goes to change a preference, they are usually in one of the following states:
+1. On a page that the preference would affect, and they wish to change the preference and have the change be effective asap.
+2. About to go to a page, and know they need to change a preference in order that it is rendered the way they want.
+
+An example of both of those scenarios is bug 52355, where a user wants to enable the VisualEditor on the current page, or enable it on the next page they visit (especially if it is a redlink).
+
+Currently the typical workflow is
+0. The user on a mediawiki page
+1. Load special:preferences
+2. Change the preference and Save (which loads preferences panel again)
+3. Press 'Back' button twice
+4. Reload or click a link
+
+Desired workflow:
+1. Open a pref panel in the current page
+2. Change the pref and close the panel
+3. The changes become effective immediately, if that can be achieved without reloading the page and/or loosing any user data, or a small notice displayed near the preferences panel button to inform the users their changes will be effective by reloading.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52355",1380686940,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-is3n3dhxo4ti5nzgooot,task_description,open
+New keywords for dataloss and corruption,"All products occasionally cause the user to have their work disappear.  It could be the browser crashes, or the UI in a window becomes locked up.  The VisualEditor is having more than its fair share of these at the moment, and it would be good to track them with a keyword.
+
+There are quite a few Parsoid/VisualEditor bugs that are behind 'corruption' of the wiki database.  'corruption' probably isnt the best name for the keyword.  It would include all the nowiki and pawn bugs, but also some parsoid round-trip issues.  These are not always high priority/severity, if they are rare or impossible in a 'normal configuration'.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1380675360,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_description,declined
+New keywords for dataloss and corruption,Closing for the time being as per comment 6. Feel free to reopen if there are more requestees / more arguments.,1384462331,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"In case that you are so far the only person interested in this, I recommend to use the Whiteboard field instead of introducing keywords - only difference to keywords is that anybody can use it for tagging (so using a ""personal namespace"" might be considered, e.g. I use the whiteboard for ""aklapper-moreinfo"" entries), and that it is not limited to entries globally defined on the server (like for keywords).
+I'm saying this because I prefer to keep the list of keywords small (as otherwise nobody can remember them anymore and does not set them, seen that problem in many other Bugzillas) and cross-product.",1382106411,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"Yes I am intetested in building lists. I could use tracking bugs, but we have this funky keywords feature in bugzilla where dataloss and corruption typically go.
+
+Precisely because dataloss and corruption are orthogonal to severity and priority, these keywords would allow periodic review of these bugs that havent been resolved due to prioritisation and open adhoc system.
+
+My intentions are to help the mediawiki product and extensions and users.",1381793776,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"(In reply to comment #1)
+> Refering to a potential database corruption keyword, what are your
+> intentions?
+> Are you just interesting to find a list of all such issues more quickly?
+> Would this keyword somehow help developers to keep track?",1381767050,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"(In reply to comment #2)
+> IMO severity and dataloss are orthogonal.  Not all critical are dataloss
+> cases,
+> and some dataloss are not critical.  The definition of critical includes a
+> reasonable caveat 'in a widely used and important component'.
+
+I agree, it does not always fit, but in most cases.
+Question is: How exact and specific do we need to tag information in Bugzilla, and for the sake of who? :)",1380708699,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"A discussion is happening over at https://www.mediawiki.org/wiki/Talk:Bugzilla/Fields
+
+IMO severity and dataloss are orthogonal.  Not all critical are dataloss cases, and some dataloss are not critical.  The definition of critical includes a reasonable caveat 'in a widely used and important component'.
+
+I would consider bug 52187 to be a dataloss problem, and that its severity of normal is a reasonable assessment.  But that doesnt change the fact that real users are loosing their data.
+
+IMO bug 54591 would be corruption, but unlikely to be critical as it isnt a standard operation to add a math element and put nothing in it, and it is easily fixable.",1380704888,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"Loss of data is severity=critical by definition ( https://www.mediawiki.org/wiki/Bugzilla/Fields#importance ) hence I don't see a need for a keyword.
+
+Refering to a potential database corruption keyword, what are your intentions? Are you just interesting to find a list of all such issues more quickly? Would this keyword somehow help developers to keep track?",1380701068,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"this is like bug 46893.
+
+ $ cd extensions/VisualEditor/modules/ve-mw/test/browser
+ $ bundle exec cucumber features/visual_editor_bullets.feature
+
+If the tests progress, eventually they print out a lot of
+
+*** DEPRECATION WARNING
+*** You are calling a method named class_name at /home/spage/projects/core/extensions/VisualEditor/modules/ve-mw/test/browser/features/step_definitions/visual_editor_bullets_steps.rb:81:in `block in <top (required)>'.
+*** This method does not exist in page-object so it is being passed to the driver.
+*** This feature will be removed in the near future.
+*** Please change your code to call the correct page-object method.
+*** If you are using functionality that does not exist in page-object please request it be added.
+
+*** DEPRECATION WARNING
+*** You are calling a method named select_text at /home/spage/projects/core/extensions/VisualEditor/modules/ve-mw/test/browser/features/step_definitions/visual_editor_bullets_steps.rb:14:in `block in <top (required)>'.
+*** [same last 4 lines]
+
+The lines deprecated by the former are all of the form
+  SOME_element.class_name.{should, should_not} match /disabled/
+where the HTML has CSS class=""ve-ui-widget ve-ui-tool ve-ui-tool-outdent ve-ui-widget-disabled"".  I don't know the page-object equivalent to retrieving the CSS class (attribute( 'class' ), but maybe instead the code could use page-object's disabled? and enabled? methods.
+
+The latter deprecation is odd since the test specifically requires ""watir-webdriver/extensions/select_text""
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**Whiteboard**: gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks",1380084600,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-al543vpnemdlnqyld3n4,task_description,resolved
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"After a quick look at VisualEditor Jenkins jobs[0], looks like this is fixed. Please reopen if you see the problem again.
+
+0: https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/",1414406388,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"(In reply to Chris McMahon from comment #4)
+> Cheezy actually fixed this but hasn't updated the page-object gem yet
+> https://github.com/cheezy/page-object/issues/192
+
+Željko / Chris: Is this still a valid ticket one year after? Has Cheezy updated it in the meantime or is this still a task suitable for new contributors?",1414345430,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"If you need more information (and you probably do), feel free to ask questions
+here, at #wikimedia-qa freenode IRC channel or at QA mailing list:
+
+https://lists.wikimedia.org/mailman/listinfo/qa",1386004101,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,Cheezy actually fixed this but hasn't updated the page-object gem yet https://github.com/cheezy/page-object/issues/192,1382721432,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,See also bug 46893,1382712015,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"And here:
+
+https://wmf.ci.cloudbees.com/job/VisualEditor-test2.wikipedia.org-linux-firefox/119/console",1382711956,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"Still not fixed:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-test2.wikipedia.org-linux-chrome/96/console",1382711467,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+VisualEditor: Allow inspectors to be left-aligned?,"Non-embedded inspectors are generally positioned to the bottom right of the node they're inspecting. In cases where we're dynamically altering the node, however (like the live preview feature for math), it probably makes more sense to position that kind of inspector at the bottom left. Then if the dimensions of the node change, the inspector will move around a bit less.
+
+Thoughts? Other ideas to tackle this issue?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1380073020,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vnxcxik6c5qmqlw52xaj,task_description,resolved
+VisualEditor: Allow inspectors to be left-aligned?,Fixed a while ago,1442494980,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vnxcxik6c5qmqlw52xaj,task_subcomment,NA
+Flow: misleading exception is thrown if the parsoid service is down,"If the parsoid service is down (`sudo service parsoid stop`, or update extension/Parsoid and forget/fail `npm install`), then viewing flow pages fails with exception
+
+   Parser only supports wikitext to HTML conversion
+
+   Backtrace:
+
+   #0 /srv/mediawiki/extensions/Flow/includes/ParsoidUtils.php(24): Flow\ParsoidUtils::parser('html', 'wikitext', '<p>It's a long ...')
+
+This is true, but it masks the real problem that parsoid has to work, and didn't.  ParsoidUtils::convert has a try-catch block around using parsoid, and if that fails it will fall back to using parser. It would be helpful for wiki operators if the exception message included the parsoid failure, e.g.
+   Parser only supports wikitext to HTML conversion (and parsoid earlier failed with exception ""VisualEditor is unavailable"")
+
+Now that I've figured out what's going on, this has become a low-priority bug :-)
+
+--------------------------
+**Version**: master
+**Severity**: minor",1380001740,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-vpzdercihud4opsstlu6,task_description,resolved
+Flow: misleading exception is thrown if the parsoid service is down,https://gerrit.wikimedia.org/r/#/c/92633/,1386220039,PHID-USER-r5pzlcquei6f4hb53rfg,PHID-TASK-vpzdercihud4opsstlu6,task_subcomment,NA
+Flow: misleading exception is thrown if the parsoid service is down,Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/264,1380310267,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-vpzdercihud4opsstlu6,task_subcomment,NA
+VisualEditor: Allow re-positioning of selected media items using arrow keys,"When an image is selected it should be possible to position it using the cursor keys.
+
+up/down should move it one line up/down. Whether left/right should move it one character or one word at a time I'm not sure about. Possibly shift/ctrl should modify this?
+
+This would be useful for fine control and for systems with laggy mouse behaviour (not uncommon on slow connections in my experience).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51665",1379954340,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-b2btpgodq22ee3ay6bt2,task_description,open
+VisualEditor: Allow re-positioning of selected media items using arrow keys,We probably can't use arrow keys (because that's over-riding expected behaviour of moving the cursor) but we could use Ctrl+→ etc. potentially.,1380072535,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-b2btpgodq22ee3ay6bt2,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"When a pre-formatted paragraph with long lines is displayed in VE it word wraps. However it doesn't word-wrap in display mode (T2260), meaning that you have no idea that you need to add manual line breaks until after you have saved.
+
+See https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&oldid=573792519#Section_number_three (rendered) and https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&oldid=573792519&veaction=edit&section=2 (in VE)
+
+The word wrapping in VE is actually better than what happens in read mode, but the two should not be different. Fixing T2260 would be better, but as it's been open since 2004 adjusting VE to match the current behaviour seems more realistic :/
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=260",1379694420,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_description,resolved
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"Change 205177 merged by jenkins-bot:
+Do not wrap <pre> nodes
+
+[[https://gerrit.wikimedia.org/r/205177]]",1429559989,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"Change 205177 had a related patch set uploaded (by Bartosz Dziewoński):
+Do not wrap <pre> nodes
+
+[[https://gerrit.wikimedia.org/r/205177]]
+",1429476381,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"We have `pre.ve-ce-branchNode { white-space: pre-wrap; }` added per T40043, because Chrome/Safari will otherwise //also// wrap the text, not just between words, but anywhere (this affects any `<pre>` inside a  `contenteditable=""true""` node). I did some searching and found https://bugs.webkit.org/show_bug.cgi?id=35935; it appears that we can set `word-wrap: normal;` to override this behavior.
+
+We also need to remove `overflow: hidden` from the surface to get regular sane horizontal scrolling behavior. It doesn't //seem// to be necessary…",1429476284,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,,1429475491,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,,1429475153,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"Created attachment 17130
+Read - no word wrapping
+
+**Attached**: {F11732}",1415999787,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"Created attachment 17129
+Preformatted text in Edit- word wrapping is present
+
+**Attached**: {F11731}",1415999734,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,Alternatively we could fix this bug in MediaWiki…,1415881181,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Provide a dialog with a list of all keyboard short-cuts (on Ctrl+? or similar?),"See e.g. http://www.impressivewebs.com/demo-files/question-mark-js/ - similarly used in Reddit etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379661360,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5xysqxijiml4iixxb7sd,task_description,resolved
+VisualEditor: Provide a dialog with a list of all keyboard short-cuts (on Ctrl+? or similar?),https://gerrit.wikimedia.org/r/#/c/107153/,1390677098,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5xysqxijiml4iixxb7sd,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for searching for pages (some don't come up),"Screenshot of link inspector not listing a matching page
+
+When opening the link inspector on a link to dab page [[Department of Foreign Affairs and Trade]], the link inspector shows two items: the dab page, and the page [[Department of Foreign Affairs and Trade (Ireland)]].  It does not list [[Department of Foreign Affairs and Trade (Australia)]].  The unlisted page is not a new page.
+
+Steps to reproduce:
+1. https://en.wikipedia.org/w/index.php?title=Heidi_Bootle&oldid=573475141
+2. Open Visual Editor
+3. Click on Department of Foreign Affairs and Trade
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51013
+
+**Attached**: {F11697}",1379640720,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cqgpkdfnpdapeshycn57,task_description,duplicate
+VisualEditor: OpenSearch results aren't perfect for searching for pages (some don't come up),"Actually, merging this into bug 51013 for actioning.
+
+*** This bug has been marked as a duplicate of bug 51013 ***",1410985568,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cqgpkdfnpdapeshycn57,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for searching for pages (some don't come up),*** Bug 67150 has been marked as a duplicate of this bug. ***,1406753647,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cqgpkdfnpdapeshycn57,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for searching for pages (some don't come up),*** Bug 62804 has been marked as a duplicate of this bug. ***,1395185089,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cqgpkdfnpdapeshycn57,task_subcomment,NA
+VisualEditor: Enwiki's {{divstyleamber}} (used in a parameter) turns into mw:ExpandedAttrs in Parsoid which VE doesn't handle yet.,"Although it can't be used in articles, it is widely used elsewhere, including userpages.
+If you try and VEdit https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=573626556 you'll notice that this reflects in reference numbering being incorrect, since the ones in the divbox will be ignored.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54803",1379590260,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dxrqwnd4epgrwlipk5o2,task_description,open
+VisualEditor: Enwiki's {{divstyleamber}} (used in a parameter) turns into mw:ExpandedAttrs in Parsoid which VE doesn't handle yet.,"Another issue:
+<<Open a page with {{divbox|amber|test|Test content.}} Click on the divbox, open the template dialogue. Click on ""apply changes"". Divbox disappears.>>
+
+If you want to test this, VEdit https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=573628652 .",1379591181,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dxrqwnd4epgrwlipk5o2,task_subcomment,NA
+VisualEditor: Enwiki's {{divstyleamber}} (used in a parameter) turns into mw:ExpandedAttrs in Parsoid which VE doesn't handle yet.,"My previous comment was related to a page containing <div style=""{{divstyleamber}}"">Content.</div>, which can not be edited.",1379591096,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dxrqwnd4epgrwlipk5o2,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Incorrect reversed display of non Latin characters
+
+Please see the attached image and Bugs #54308 & #54309.
+
+By this time I resigned to utilize the advanced toolbar and after making an attempt, I feel very cynical because this effort is totally useless. There is a lot to be said for programmers and developers learning to proofread a chapter or so of text, to see how their ideas are working in the real world.
+
+In the first place, It takes several steps to hide the header to gain additional viewing space or access various features. 
+
+Finally, The non-Latin characters, like Hebrew and Arabic were inserted from left to right. For those who don't understand, that's the equivalent of displaying Latin characters from right to left, as in: . . . . L K J I H G F E D C B A
+
+In view of my previous posts, please consider correcting this ASAP.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11606}",1379579460,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-yj6unjc6sotp4kv2mflx,task_description,resolved
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 414961 **merged** by jenkins-bot:
+[mediawiki/extensions/WikiEditor@master] Use display:inline-block for special character buttons
+
+[[https://gerrit.wikimedia.org/r/414961]]",1520269897,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415286 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] fetchSpecialCharList: Set directionality
+
+[[https://gerrit.wikimedia.org/r/415286]]",1519948593,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415374 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (f5c88eb30)
+
+[[https://gerrit.wikimedia.org/r/415374]]",1519932738,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415374 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (bdb1a680a)
+
+[[https://gerrit.wikimedia.org/r/415374]]",1519848137,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415281 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] SpecialCharacterPage: Allow setting lang/dir via special attributes property
+
+[[https://gerrit.wikimedia.org/r/415281]]",1519846076,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415286 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] fetchSpecialCharList: Set directionality
+
+[[https://gerrit.wikimedia.org/r/415286]]",1519825824,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415281 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] SpecialCharacterPage: Allow setting lang/dir via special attributes property
+
+[[https://gerrit.wikimedia.org/r/415281]]",1519825655,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"I set the CSS float to right for RTL languages.
+
+If this is done for WikiEditor, then it must also be updated in the VE special character editor. There is will be easier: the lang and dir attributes must simply set on the `<div>` that wraps all the characters `<span>` tags.",1519718525,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 414961 had a related patch set uploaded (by Amire80; owner: Amire80):
+[mediawiki/extensions/WikiEditor@master] Order right-to-left alphabets from right-to-left in the special character selector
+
+[[https://gerrit.wikimedia.org/r/414961]]",1519718250,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"**yesod22** wrote:
+
+Hi. The only input I can give is that as a bi-lingual english hebrew speaker being forced with the option of having english displayed RTL or hebrew displayed LTR is CERTAINLY not desired. I'd much prefer having each language displayed in it's natural order - as it's supposed to be.
+
+The idea of displaying Hebrew or Arabic from LTR because that's the expectation of an english speaker reminds me of a joke by Louis CK on how the pilgrims named the natives ""Indians"" despite the fact that they had nothing to do with India :-) (see youtube). A language should be displayed in it's order - not in the order of what a non-native speaker would like it to be :-)
+
+blessings, Daniel",1380213955,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Michael M., Please point me to the page on en.Wikipedia where RTL characters show up correctly. I just implemented the WikiEditor on en. Wikipedia and RTL characters were displayed in LTR order. Then, I am curious as to how do you know what is the expectation of the users???",1379680638,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Reopening: I looked at en.wikipedia and de.wikipedia. Both have a set of special characters *below* the editbox, which isn't part of MediaWiki, but developed by the communities. In both cases the characters of RTL languages are shown from right to left, so even if this behavior of WikiEditor is intended (which I doubt), it is wrong based on the expectation of its users.",1379664481,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Andre, the user's language settings should not affect the character sets. They should be displayed in their natural order regardless of the user's language preferences.",1379623385,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Confirming what you see. Hebrew letters Alef and Bet are on the left. 
+
+I am pretty sure that this is intended and that it depends on your personal language settings in https://en.wikisource.org/wiki/Special:Preferences#mw-prefsection-personal-i18n because depending on your ""primary"" language you are used to either expect the first letter on the left (LTR) or on the right (RTL).
+
+It's the same the other way round: 
+Looking at the Cyrillic character section with the interface language set to Hebrew (by simply adding &uselang=he to the URL), I also get the Russian alphabet from right to left, while Russian is a left to right language.",1379586269,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+VisualEditor: ResizableNode should show numeric dimensions when resizing.,"In a status bar/next to the cursor/on the image
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379549160,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-db7owolkladsvbupsv7m,task_description,resolved
+VisualEditor: ResizableNode should show numeric dimensions when resizing.,"Change 85970 merged by jenkins-bot:
+Show a label with the current dimensions while resizing
+
+https://gerrit.wikimedia.org/r/85970",1382007456,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-db7owolkladsvbupsv7m,task_subcomment,NA
+VisualEditor: ResizableNode should show numeric dimensions when resizing.,"Change 85970 had a related patch set uploaded by Esanders:
+Show a label with the current dimensions while resizing
+
+https://gerrit.wikimedia.org/r/85970",1380109182,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-db7owolkladsvbupsv7m,task_subcomment,NA
+VisualEditor: ResizableNode should show numeric dimensions when resizing.,"Created attachment 13376
+Screenshot of implementation
+
+**Attached**: {F11558}",1380109052,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-db7owolkladsvbupsv7m,task_subcomment,NA
+"VisualEditor: VE ""edit"" link in section edit links of a remote file tries to create a new page on local wiki, not remote section","Example image: https://www.mediawiki.org/wiki/File:MassMessage_submitted.png
+
+Clicking on ""edit"" takes you to <https://www.mediawiki.org/wiki/File:MassMessage_submitted.png?veaction=edit&vesection=1>
+
+Clicking on ""edit source"" tags you to <https://commons.wikimedia.org/w/index.php?title=File:MassMessage_submitted.png&action=edit&section=1>
+
+The 'edit' link should take you to commons and somehow gracefully fallback on the wikitext editor since VE is not enabled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://www.mediawiki.org/wiki/File:MassMessage_submitted.png
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62071",1379486100,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-wwi2e2vktmnorzseurla,task_description,resolved
+"VisualEditor: VE ""edit"" link in section edit links of a remote file tries to create a new page on local wiki, not remote section","Change 130082 merged by jenkins-bot:
+Don't change section edit links on foreign file description pages
+
+https://gerrit.wikimedia.org/r/130082",1398711188,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wwi2e2vktmnorzseurla,task_subcomment,NA
+"VisualEditor: VE ""edit"" link in section edit links of a remote file tries to create a new page on local wiki, not remote section","Change 130082 had a related patch set uploaded by Alex Monk:
+Don't change section edit links on foreign file description pages
+
+https://gerrit.wikimedia.org/r/130082",1398697756,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wwi2e2vktmnorzseurla,task_subcomment,NA
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"**Author:** `swalling`
+
+**Description:**
+Screenshot
+
+If you start ?tour=firstedit and then click veaction=edit, you get the wikitext-related Preview step unattached (see screenshot).
+
+This is a low priority issue, because users should only be getting the wikitext 'firstedit' tour if VE is not available. I am filing just in case the opposite situation might happen, i.e. users start a ?tour=vefirstedit, click Edit source, then get the VE tour step. If that's impossible, then this can be ignored for now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11439}",1379459220,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-7sgyl2imvttq6da7zqhg,task_description,open
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"If you look at firstedit tour definition, you'll see that shouldSkip is set to call isEditing() Calling gt.isEditing() checks to see if you are either editing with wikitext or if the VisualEditor is loaded.  However the tour step loads before ve is actually loaded.
+
+IMO: isEditing needs to return true if VisualEditor is loading or loaded.  
+Locally this fixes the bug for me.  I probably will make a patch for this.",1399496465,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-7sgyl2imvttq6da7zqhg,task_subcomment,NA
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"Change 84735 had a related patch set uploaded by Mattflaschen:
+Declare tour as requiring wikitext, but it doesn't work yet.
+
+https://gerrit.wikimedia.org/r/84735",1379495165,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7sgyl2imvttq6da7zqhg,task_subcomment,NA
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"I was wrong about it being an easy fix.  As far as I can tell, this never worked (wikitext tours not being loaded for VisualEditor).  There are two different scenarios, which don't work for different reasons.
+
+However, it will work in the other direction (which is probably why I didn't catch this bug earlier): If it's a VE tour it will not show in the wikitext editor.
+
+I will fix this properly, but it looks like it may require some refactoring to do right.",1379495139,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-7sgyl2imvttq6da7zqhg,task_subcomment,NA
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"Oh, I forgot the showConditionally.  This is a trivial fix, and I'll do it tonight.",1379459453,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-7sgyl2imvttq6da7zqhg,task_subcomment,NA
+Tech metrics missing IRC channels,"Currently there are only 4 IRC channels being scanned at 
+
+http://korma.wmflabs.org/browser/irc-repos.html
+
+https://meta.wikimedia.org/wiki/IRC/Channels#MediaWiki_and_technical contains the list of tech channels
+
+#pywikipediabot should be added as well in order to keep consistency with https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379440500,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ylv5ntuga7adnifnjbdx,task_description,resolved
+Tech metrics missing IRC channels,Thanks! Closing.,1445360976,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Ok, channels are updated.
+
+Having a JSON file with the list of channels and log place would be awesome :).
+
+@Aklapper, from my side feel free to close the task if you prefer to have further discussion about automation in another ticket.",1445360460,PHID-USER-kiwupwbdc2fe6dzsojnq,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Also note my last comment at https://github.com/benapetr/wikimedia-bot/pull/49#issuecomment-149596883
+It would be trivial for this to all be in json format too but I would leave that for @petrb to implement!",1445354068,PHID-USER-u7w6n5ecde66oujx33pe,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1735259, @Aklapper wrote:
+>>>! In T56230#1734947, @Dicortazar wrote:
+>> is there a way to automatically retrieve the list of available channels?.
+> 
+> for ""automatically retrieve the list of channels **which are logged by wm-bot**"" I have asked its maintainer and will update this task once I've received an answer.
+
+<addshore> the list is not on github! You manage the setting per channel through the bot!
+<addshore> http://bots.wmflabs.org/~wm-bot/dump/systemdata.htm
+<addshore> that has all of the info on it, updated every 20 mins
+<addshore> there isn't a structured form currently though",1445353892,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1737513, @Qgil wrote:
+> Do we need to remove deprecated channels?
+
+No, so I've canceled https://github.com/Bitergia/mediawiki-repositories/pull/8
+
+>>! In T56230#1736157, @Dicortazar wrote:
+> we just need to add the listed channels in that irc_channels.conf file and we would be done here :).
+
+Awesome! Feel free to close this longstanding task after merging https://github.com/Bitergia/mediawiki-repositories/pull/9
+
+We (I?) can create separate tasks to discuss whether to get certain channels logged by wm-bot (""mediawiki-i18n"", ""mediawiki-parsoid"", ""mediawiki-scripts"", ""wikimedia-cep"", ""wikimedia-design"", ""wikimedia-ect"", ""wikimedia-perf"", ""wikimedia-qa"", ""wikimedia-search"", ""pywikibot"") and after deciding, getting them added to korma later.",1445331981,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"This depends on your needs. I mean, as we're not automatically retrieving IRC channels information, we can keep as many channels as you want.
+
+The irc_channels.conf file is more a place to centralize requirements from Korma than an automated place to retrieve IRC info. On the other hand, as we successfully automated Gerrit projects, the Gerrit .conf file is a place where automatically info is updated, added and removed.",1445329859,PHID-USER-kiwupwbdc2fe6dzsojnq,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Do we need to remove deprecated channels? Isn't their information useful to
+count contributions of related users in those channels?",1445329360,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"@Aklapper, what I've done so far is to manually add them to the infrastructure (this is indeed a script deleting, removing, adding URLs, tar.gz, etc) and I wanted to add that list of TRACKED channels once the process if finished and correct (still running).
+
+And yes, as you comment, we just need to add the listed channels in that irc_channels.conf file and we would be done here :).",1445286147,PHID-USER-kiwupwbdc2fe6dzsojnq,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1735971, @Dicortazar wrote:
+> Based on info provided by @Aklapper, I've added all of them
+
+Thank you. 
+I think we're cool with this list for now; adding any further potential channels would first require making them logged on the Wikimedia side of things.
+
+@Dicortazar: For my understanding of the infrastructure: where did you ""add"" them? Any URL to some public diff? I guess the next and last step for one of us is to provide a pull request to `mediawiki-repositories/irc_channels.conf` adding those TRACKED channels and after merging that pull request we are done here?",1445284658,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Based on info provided by @Aklapper, I've added all of them, but mediawiki that was already in the list.
+
+So, the list is as follows:
+
+* ""mediawiki"": TRACKED
+* ""mediawiki-i18n"": 
+* ""semantic-mediawiki"": TRACKED
+* ""mediawiki-parsoid"":
+* ""mediawiki-visualeditor"": TRACKED
+* ""mediawiki-scripts"":
+* ""wikimedia-tech"": TRACKED
+* ""wikimedia-dev"": TRACKED
+* ""wikimedia-toolserver"": TRACKED
+* ""wikimedia-labs"": TRACKED
+* ""wikimedia-labs-nagios"":
+* ""wikimedia-ai"": TRACKED
+* ""wikimedia-analytics"": TRACKED
+* ""wikimedia-cep"":
+* ""mediawiki-core"": TRACKED
+* ""wikimedia-collaboration"": TRACKED
+* ""wikimedia-databases"": TRACKED
+* ""wikimedia-design"":
+* ""wikimedia-ect"":
+* ""wikimedia-fundraising"": TRACKED
+* ""wikimedia-mobile"": TRACKED
+* ""wikimedia-multimedia"": TRACKED
+* ""wikimedia-operations"": TRACKED
+* ""wikimedia-perf"":
+* ""wikimedia-qa"":
+* ""wikimedia-releng"": TRACKED
+* ""wikimedia-research"": TRACKED
+* ""wikimedia-search"":
+* ""wikimedia-teampractices"": TRACKED
+* ""huggle"": TRACKED
+* ""pywikibot"":
+* ""wikidata"" TRACKED",1445281870,PHID-USER-kiwupwbdc2fe6dzsojnq,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1734947, @Dicortazar wrote:
+> I'll close that pull request since the place to add/remove repositories takes place at https://github.com/Bitergia/mediawiki-repositories
+
+Thanks! Good to know.
+
+> On the other hand, is there a way to automatically retrieve the list of available channels?.
+
+I'm afraid that technically speaking the answer is no. However for ""automatically retrieve the list of channels **which are logged by wm-bot**"" I have asked its maintainer and will update this task once I've received an answer.
+
+> Finally, the list of updated repos analyzed by Korma are found at http://korma.wmflabs.org/browser/data/json/irc-repos.json
+
+""wikimedia-toolserver"" is irrelevant nowadays, I've created https://github.com/Bitergia/mediawiki-repositories/pull/8 to remove it.
+
+> For the rest of the non TRACKED IRC channels, there's missing information in some cases at https://meta.wikimedia.org/wiki/IRC/Channels about where the logs are stored.
+
+Taking the list of channels which are not listed in our configuration yet, and which I'd be interested in, and which I could find public logs for in folders which saw recent updates:
+* ""mediawiki"" - https://bots.wmflabs.org/~wm-bot/logs/%23mediawiki/
+* ""mediawiki-visualeditor"" - https://bots.wmflabs.org/~wm-bot/logs/%23mediawiki-visualeditor/
+* ""wikimedia-ai"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-ai/
+* ""mediawiki-core"" - https://bots.wmflabs.org/~wm-bot/logs/%23mediawiki-core/
+* ""wikimedia-collaboration"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-collaboration/
+* ""wikimedia-databases"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-databases/
+* ""wikimedia-multimedia"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-multimedia/
+* ""wikimedia-releng"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-releng/
+* ""wikimedia-research"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-research/
+* ""wikimedia-teampractices"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-teampractices/
+* ""wikidata"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikidata/
+
+Removing myself as assignee here as I don't know how the ""grab those logs"" infrastructure works exactly.",1445272505,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"And regarding to the rest of IRC channels. Do we have logs for all of them?
+
+The following ones were the ones added in the GitHub change:
+
+* ""mediawiki"": TRACKED
+* ""mediawiki-i18n"": 
+* ""semantic-mediawiki"": TRACKED
+* ""mediawiki-parsoid"":
+* ""mediawiki-visualeditor"":
+* ""mediawiki-scripts"":
+* ""wikimedia-tech"": TRACKED
+* ""wikimedia-dev"": TRACKED
+* ""wikimedia-toolserver"": TRACKED
+* ""wikimedia-labs"": TRACKED
+* ""wikimedia-labs-nagios"":
+* ""wikimedia-ai"":
+* ""wikimedia-analytics"": TRACKED
+* ""wikimedia-cep"":
+* ""mediawiki-core"":
+* ""wikimedia-collaboration"":
+* ""wikimedia-databases"":
+* ""wikimedia-design"":
+* ""wikimedia-ect"":
+* ""wikimedia-fundraising"": TRACKED
+* ""wikimedia-mobile"": TRACKED
+* ""wikimedia-multimedia"":
+* ""wikimedia-operations"": TRACKED
+* ""wikimedia-perf"":
+* ""wikimedia-qa"":
+* ""wikimedia-releng"":
+* ""wikimedia-research"":
+* ""wikimedia-search"":
+* ""wikimedia-teampractices"":
+* ""huggle"": TRACKED
+* ""pywikibot"":
+* ""wikidata""
+
+For the rest of the non TRACKED IRC channels, there's missing information in some cases at https://meta.wikimedia.org/wiki/IRC/Channels about where the logs are stored.",1445267841,PHID-USER-kiwupwbdc2fe6dzsojnq,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"I've commented on the GitHub repo.
+
+As a summary: I'll close that pull request since the place to add/remove repositories takes place at https://github.com/Bitergia/mediawiki-repositories
+
+On the other hand, is there a way to automatically retrieve the list of available channels?.
+
+Finally, the list of updated repos analyzed by Korma are found at http://korma.wmflabs.org/browser/data/json/irc-repos.json, but there are some more than the initial four: ""wikimedia-operations"", ""mediawiki"", ""wikimedia-dev"", ""wikimedia-labs"", ""wikimedia-mobile"", ""wikimedia-toolserver"", ""wikimedia-tech"", ""wikimedia-analytics"", ""wikimedia-fundraising"", ""semantic-mediawiki"", ""huggle""
+",1445265939,PHID-USER-kiwupwbdc2fe6dzsojnq,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1557951, @Dicortazar wrote:
+> I'll check that list and update those channels in Korma.
+
+@Dicortazar: Clean pull request now in https://github.com/Bitergia/mediawiki-dashboard/pull/62",1443943426,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"(let's keep the discussion of this task focused on IRC channels, not mixing it with code repositories)",1440097412,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Thanks for this update!
+
+I'll check that list and update those channels in Korma.
+
+@Dzahn and @Aklapper, I'm still working on the feature to automate the list of repositories to be tracked by Korma at {T104845}. In summary this will provide a list of repositories per data source and a black list for each of them.
+
+Thus, anyone interested in tracing new repositories or in adding some of them to the black list, should modify such lists and pull request a change.
+
+A first version of the files are available at GitHub in https://github.com/Bitergia/mediawiki-repositories. Those are old versions, so we shouldn't change those a lot.
+
+So, if we keep that workflow, @Aklapper, my suggestion is to add a new config file to the GitHub repo (irc_channels.conf) with the correct list of repositories (sorted). I can do this in any case with the new list you provided. This will help to centralized those lists of repos.
+
+Comments are welcome in any case :). It's a bit complex task to automate and trace repositories, but this could be an interesting feature for all of us :).",1440091921,PHID-USER-kiwupwbdc2fe6dzsojnq,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"So that updated list would be https://github.com/Bitergia/mediawiki-dashboard/pull/59/files (and obviously my GitHub workflow skills are still improvable, sigh)",1440085780,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1443372, @Dzahn wrote:
+> How do you add channels to korma?
+
+Editing `/browser/data/json/irc-repos.json` in https://github.com/Bitergia/mediawiki-dashboard",1436531313,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,How do you add channels to korma?,1436481722,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Once {T96371} is closed, we may want to work on this task again.
+
+We can discuss this during this Friday conf call and leave it as June task.",1432652217,PHID-USER-kiwupwbdc2fe6dzsojnq,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,%%%*** Bug 60079 has been marked as a duplicate of this bug. ***%%%,1395751080,PHID-USER-lepsd737p6wqwsowcou2,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,IRC channels are not that critical. Normal priority.,1380233157,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Ooops, actually Nemo is (again) right:
+
+https://meta.wikimedia.org/wiki/IRC/Channels#MediaWiki_and_technical
+https://meta.wikimedia.org/wiki/IRC/Channels#Tools",1379541015,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Check the URL above. I'm proposing only the ""MediaWiki and technical"" section plus #pywikipediabot",1379513170,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"There are 261 Wikimedia IRC channels. We want to gather all those channels?
+
+I think it is not a big issue to configure and implement it, but it could be an important delay and resource consuming in the update process because logs are included in one big file per channel and the incremental support can not be implemented.
+
+http://bots.wmflabs.org/~wm-bot/logs/
+
+Is there any other place with logs for IRC channels?",1379498684,PHID-USER-lepsd737p6wqwsowcou2,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"InstantCommons does not work on Vagrant if you enable the 404 handler for images (the `thumb_on_404` role does that and most multimedia roles include it). The problem is related to thumbnail caching; similar to T101565, but the default wiki (`127.0.0.1`) is also affected.
+
+As a workaround, caching can be disabled by creating `/vagrant/settings.d/10-DisableThumbnailCaching.php` with
+```
+<?php
+$wgUseInstantCommons = false;
+$wgForeignFileRepos[] = array(
+	'class' => 'ForeignAPIRepo',
+	'name' => 'wikimediacommons',
+	'apibase' => 'http://commons.wikimedia.org/w/api.php',
+	'fetchDescription' => true,
+	'descriptionCacheExpiry' => 0,
+	'apiThumbCacheExpiry' => 0,
+);
+```
+",1379384100,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_description,resolved
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Please reopen or file a new bug if you can reproduce.,1468099239,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,IIRC yes but much harder to trigger than it used to be. But I'm may be wrong - I only vaguely remember what this was about.,1457652757,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,@Tgr is this still an ongoing problem?,1457644136,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223480 abandoned by Gergő Tisza:
+Use 404 handler for all wikis when the role is enabled
+
+Reason:
+There doesn't seem to be a way to do this correctly.
+
+[[https://gerrit.wikimedia.org/r/223480]]",1436559679,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223493 merged by jenkins-bot:
+Fix thumb on 404 role for multiwiki reality
+
+[[https://gerrit.wikimedia.org/r/223493]]",1436391322,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223477 merged by jenkins-bot:
+Fix thumb rewrite rules
+
+[[https://gerrit.wikimedia.org/r/223477]]",1436327387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223493 had a related patch set uploaded (by BryanDavis):
+Fix thumb on 404 role for multiwiki reality
+
+[[https://gerrit.wikimedia.org/r/223493]]
+",1436327281,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223480 had a related patch set uploaded (by Gergő Tisza):
+Use 404 handler for all wikis when the role is enabled
+
+[[https://gerrit.wikimedia.org/r/223480]]
+",1436318919,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223477 had a related patch set uploaded (by Gergő Tisza):
+Fix thumb rewrite rules
+
+[[https://gerrit.wikimedia.org/r/223477]]
+",1436317320,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"From the Apache docs:
+> REQUEST_FILENAME
+> The full local filesystem path to the file or script matching the request, if this has already been determined by the server at the time REQUEST_FILENAME is referenced. Otherwise, such as when used in virtual host context, the same value as REQUEST_URI. Depending on the value of AcceptPathInfo, the server may have only used some leading components of the REQUEST_URI to map the request to a file.
+
+So apparently the problem is that Apache does not map the URI to the filesystem path before checking whether the file exists. If I disable the rewrite rule, the thumbnail appears correctly.",1436316316,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Probably even more broken on other wikis since the 404 handler config rule seems to only be applied to the default wiki (and the one created by the `commonswiki` role which has its own apache rules).,1436313920,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Contents of `/etc/apache2/site-confs/devwiki/50-thumb-php-on-404.conf`:
+```
+RewriteEngine On
+
+# call thumb.php for thumb images not on disk
+RewriteCond %{REQUEST_FILENAME} !-f
+RewriteCond %{REQUEST_FILENAME} !-d
+RewriteRule ^/images/thumb/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/[^/]*([0-9]+)px-.*$ /w/thumb_handler.php [PT,QSA,B]
+
+
+# call thumb.php for thumb archive images not on disk
+RewriteCond %{REQUEST_FILENAME} !-f
+RewriteCond %{REQUEST_FILENAME} !-d
+RewriteRule ^/images/thumb/archive/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/[^/]*([0-9]+)px-.*$ /w/thumb_handler.php [PT,QSA,B]
+```
+
+Contents of `/etc/apache2/site-confs/devwiki/50-devwiki-images.conf`:
+```
+# vim: filetype=apache sts=4 sw=4 autoindent
+#
+# This file is managed by Puppet.
+#
+<Directory /srv/images>
+    Require all granted
+    Header set Access-Control-Allow-Origin ""*""
+</Directory>
+
+Alias /images /srv/images
+```
+
+Apache log with `LogLevel alert rewrite:trace6`:
+```
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace2] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] init rewrite engine with requested uri /images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg, referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace3] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] applying pattern '^/$' to uri '/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg', referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace3] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] applying pattern '^/images/thumb/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/[^/]*([0-9]+)px-.*$' to uri '/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg', referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace4] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] RewriteCond: input='/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg' pattern='!-f' => matched, referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace4] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] RewriteCond: input='/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg' pattern='!-d' => matched, referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace2] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] rewrite '/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg' -> '/w/thumb_handler.php', referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace2] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] forcing '/w/thumb_handler.php' to get passed through to next API URI-to-filename handler, referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+```
+
+The thumbnail is at `/srv/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg`. I don't get why the `!-f` rule matches, somehow the alias does not get applied?",1436313779,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Still (or again) broken. Commons API is used without a problem, the image is thumbnailed, but Apache redirects the request to `thumb.php` even though the thumbnail exists and seems to be in the right place. (`thumb.php` cannot handle remote images, that's T27958.)",1436313023,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Can't reproduce this anymore. https://gerrit.wikimedia.org/r/217769 might have fixed it.,1435366189,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Same for me. This is actually impacting my ability to code review certain changes... :-/,1435087748,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Enabling the multimedia role on a fresh MW-Vagrant box still produces broken thumbnails for me. (""//Error generating thumbnail: The source file 'XXX' does not exist.//"")",1419909145,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"@Eloquence, @tgr Is this still a problem?",1419899284,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Bulk unassigning bugs from Ori.,1416260174,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"In the latest MediaWiki Vagrant with the multimedia role enabled, InstantCommons does not successfully generate thumbnails for me. The issue goes away if I comment out the thumb-php-on-404 handler, so I suspect it's an issue with the rewrite rule. CCing Bryan since he wrote that template.",1401153590,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"I can confirm that Gergo's workaround does the trick, even for a Vagrant newbie like me.
+
+So even if we can't fix this in code right away, at least we have a solution for making this work temporarily.
+
+Thanks for this!",1394693207,PHID-USER-dbudsaorcqut7sg3vvbi,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Bawolff: I could reproduce this with the multimedia vagrant role enabled, which in theory should enable 404-based image handling.",1394665838,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Workaround:
+
+<?php
+$wgUseInstantCommons = false;
+$wgForeignFileRepos[] = array(
+    'class' => 'ForeignAPIRepo',
+    'name' => 'wikimediacommons',
+    'apibase' => 'http://commons.wikimedia.org/w/api.php',
+    'fetchDescription' => true,
+    'descriptionCacheExpiry' => 0,
+    'apiThumbCacheExpiry' => 0,
+);
+
+I started to track this down some weeks ago but ran out of time and had to give up. The issue was MediaWiki getting confused about which local directory to use for the thumb cache IIRC.",1394665237,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"This is a known issue of using thumb.php directly instead of from a 404 handler. (Not sure how ""known"" in any case, not new)",1380304952,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Oddly, if I insert an image from Commons through VisualEditor it appears to work ok inline.
+
+If I insert one in source, I get ""Error creating thumbnail: Invalid thumbnail parameters"".
+
+whaaaaaat?",1380304811,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter","(Hopefully other reporters will improve the title and description if necessary!)
+The French Wikipedia has a number of templates which usually ask for some kind of clarification about a whole passage of text (see https://fr.wikipedia.org/wiki/Mod%C3%A8le:Refnec#Exemples ).
+So users are asking that, when they select that text and launch the template inspector, the text is already recognized as a ""parameter"" for that template.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379367180,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_description,open
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter",I think a better way to solve this would be to somehow allow templates to be treated as 'annotations' in VE (like bold style or links).,1403885820,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_subcomment,NA
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter","This feature would be very helpful for other common templates in articles. For example, the {{Colonnes}} template on French wiki, or its equivalent {{columns-list}} template on English wiki to put text/lists on several columns.
+
+https://en.wikipedia.org/wiki/Template:Columns-list",1379522740,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_subcomment,NA
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter","I think it's not only the French wiki that may use this... On English wiki, the equivalent of {{Refnec}} and its ""1"" parameter is {{Citation needed span}} and its ""text"" parameter.
+
+Maybe a way of implementing this would be the following :
+* Add an information in TemplateData to be able to tell which parameter should be initialized with the selected text
+* When you insert a template with VE, if the TemplateData as such configuration, use the selected text to initialize the parameter",1379367849,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_subcomment,NA
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter",And I think that such a functionality would need to be able to remove the template by replacing it with its first parameter.,1379367567,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_subcomment,NA
+VisualEditor: Duplicating categories (and possibly also something else),"NicoV reports this diff,
+https://fr.wikipedia.org/w/index.php?title=Blood_Lad&diff=96657484&oldid=96506947 .
+Assuming the user deleted the infobox without realizing it, I did not manage to reproduce the duplication of categories inside a reference tag (line 38); if I just copy/paste them they get nowikied, so it shouldn't be a vandalism.  
+
+CCing subbu and gwicke here. T52120 and T54238 come to mind, but I'm not sure if it's really a dupe.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+T54238
+T52120
+T76715
+T89618",1379347920,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_description,resolved
+VisualEditor: Duplicating categories (and possibly also something else),Think this was all fixed,1415881087,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_subcomment,NA
+VisualEditor: Duplicating categories (and possibly also something else),"https://fr.wikipedia.org/w/index.php?title=Bello_de_Carcassonne&diff=107097528&oldid=107091155 duplicated two categories and added others, but not within a ref tag.  It also added a blank (== ==) section heading after the misplaced cats.",1409788705,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_subcomment,NA
+VisualEditor: Duplicating categories (and possibly also something else),"Yes Gabriel, I tried to behave like a vandal :) and wanted to paste templates and categories into the reference, to understand if this was what the user had actually done.
+But as you can see here https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve&diff=96710198&oldid=96710142 my result is different, in that the pasted content generated nowiki tags, so the duplication in the article is not a result of copy/pasting that content into the reference editor.",1379350998,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_subcomment,NA
+VisualEditor: Duplicating categories (and possibly also something else),"(In reply to comment #0)
+> NicoV reports this diff,
+> https://fr.wikipedia.org/w/index.
+> php?title=Blood_Lad&diff=96657484&oldid=96506947
+> .
+> Assuming the user deleted the infobox without realizing it, I did not manage
+> to
+> reproduce the duplication of categories inside a reference tag (line 38); if
+> I
+> just copy/paste them they get nowikied, so it shouldn't be a vandalism.
+
+Can you clarify what you mean with 'just copy/paste them'? Do you mean copy/pasting wikitext into VE?",1379350615,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","Change in MediaWiki:Editing notice to a links does not  parse
+
+Hi,
+
+
+When I tried to add a internal link (related to [[Special:Preferences#mw-prefsection-editing]])  to MediaWiki:Editing, it did not parse as shown in attachment.  
+
+
+*Exact edit  difference which I tried https://mr.wikipedia.org/w/index.php?title=मिडियाविकी%3AEditing&diff=1200554&oldid=44085 the result is shown in the attachment.
+
+
+*The purpose of edit was to request users to give a try to VisualEditor and report input issues . (Issues related to usability of Marathi Devnagari script are very crucial to us )
+
+
+I am not sure whether this a normal limitation of MediaWiki messages  and so not sure whether this will be accepted as a bug.
+
+But still prefered to report this bug since it is simmiller problem of parsing which I observed in Bug no 45195 also and just prefered to keep developers informed.
+
+Thanks and regards
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal
+**Whiteboard**: aklapper-moreinfo
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45195
+
+**Attached**: {F11186}",1379172900,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-43yopxeqsvyzzvqfuavz,task_description,invalid
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","The issue in comment 0 was about a link not being parsed and instead [[]] is literally shown. My confusion probably arised from the fact that you had changed https://mr.wikipedia.org/w/index.php?title=मिडियाविकी:Editing already, so I asked how to see this problem myself and to provide steps.
+
+MediaWiki:Editing neither exists on en.wp or fr.wp and was removed in 2007.
+
+As the issue was originally about https://mr.wikipedia.org/w/index.php?title=%E0%A4%AE%E0%A4%BF%E0%A4%A1%E0%A4%BF%E0%A4%AF%E0%A4%BE%E0%A4%B5%E0%A4%BF%E0%A4%95%E0%A5%80%3AEditing&diff=1200554&oldid=44085 which is totally wrong HTML I don't see any valid bug reported here.
+
+If the problem still happens with *valid* HTML, please reopen this bug report and link to the revision of MediaWiki:Editing that shows the problem. Thanks.",1379943675,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","Created attachment 13341
+additional example of message MediaWiki:Editing
+
+(In reply to comment #3)
+
+Additional example of how MediaWiki message MediaWiki:Editing works.
+
+**Attached**: {F11189}",1379766935,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","Created attachment 13340
+MediaWiki:Editing example en wikipedia
+
+(In reply to comment #3)
+
+Which language you used for The Tokyo article ? Here is an example from eglish wikipedia
+
+**Attached**: {F11188}",1379766277,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","Created attachment 13332
+Editing The Tokyo article
+
+(In reply to comment #2)
+> *[[MediaWiki:Editing]] message (Current text:Editing $1) is visible at the
+> top of every wiki page when you  are editing any wiki page.
+
+No, not for me.
+
+**Attached**: {F11187}",1379686080,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","(In reply to comment #1)
+> How to see what's on the screenshot? This is missing steps... 
+
+*[[MediaWiki:Editing]] message (Current text:Editing $1) is visible at the top of every wiki page when you  are editing any wiki page.
+
+* So the given screen shot will be visible on all wiki pages while editing if you save the given edit diff https://mr.wikipedia.org/w/index.php?title=मिडियाविकी%3AEditing&diff=1200554&oldid=44085 on any test wiki
+
+
+** (My impression is MediaWiki messages work simmiller to Templates. If template:ABC is having internal link [[PQR]] and template:ABC is included in Template:XYZ usually internal link [[PQR]] of template:ABC will parse through Template:XYZ , What I suppose/doubt is,  If MediaWiki:ABC has internal link  [[PQR]] and MediaWiki:ABC is getting included in MediaWiki:XYZ unlike templates MediaWiki messages are not parsing internal link of another MediaWiki message.That is my pure guess you(Developers) are the right people to inform what is supposed to be expected behaviour for MediaWiki messages,and the reported behaviour is matching with expected behaviour or not)
+
+
+Also, 
+>    <small><small><small /><small /> 
+> does not look like valid HTML to me.
+
+*https://mr.wikipedia.org/w/index.php?title=%E0%A4%AE%E0%A4%BF%E0%A4%A1%E0%A4%BF%E0%A4%AF%E0%A4%BE%E0%A4%B5%E0%A4%BF%E0%A4%95%E0%A5%80:Sitenotice&diff=prev&oldid=1201270 It is the same text parsing through the internal links in different MediaWiki message.
+
+HTML may be having minor issue on layout side but parsing of internal link is different issue I suppose.
+
+Rgds",1379606319,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","How to see what's on the screenshot? This is missing steps... Also, 
+   <small><small><small /><small /> 
+does not look like valid HTML to me.",1379340953,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"Transclusion dialog: ""unknown parameter"" is confusing if TemplateData doesnt exist","If adding w:cs:template:commonscat, it might be confusing for newbies even for older wikipadians to set parameters. As in this case parameters or numbers, but VE sais that such parameters are unknown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50735",1379064360,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-qyjx6fdbrrh3weriir7z,task_description,resolved
+"Transclusion dialog: ""unknown parameter"" is confusing if TemplateData doesnt exist","Merging with bug 50735.
+
+*** This bug has been marked as a duplicate of bug 50735 ***",1381342230,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qyjx6fdbrrh3weriir7z,task_subcomment,NA
+"Transclusion dialog: ""unknown parameter"" is confusing if TemplateData doesnt exist","If I can paraphrase Juan's bug report, ..
+
+In the transclusion dialog, template 'add parameter' screen, for a template without templatedata (such as cs:wp template commonscat),...
+
+Dont say 'Unknown parameter'.
+
+If there is no templatedata, VE doesnt know about any parameters, so it should not offer warnings that are essentially bogus when it is given a parameter name.  The user cant use this 'Unknown parameter' information, so it is scary.  Further to that, VE _does_ know that numeric parameters names (like '1', '2', etc) are valid parameter name, so warning 'Unknown parameter' is false in that case.
+
+Juan, if you want to add templatedata to that template, see https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/TemplateData  and
+https://en.wikipedia.org/w/index.php?title=Template:Commons_category/doc&action=edit
+
+The VE UI for templates without templatedata needs a usability overhaul. Some simple suggestions to improve usability while keeping the current UI structure:
+1. say 'This template does not have VE compatible parameter data', and link to the relevant template:blah page
+2. dont say 'No unused parameters' because that message is also misleading
+3. Instead of 'Unknown parameter' for '1', say 'parameter number 1' or 'first parameter'
+4. pre-populate the template form with a parameter '1', place the user in the parameter value field, but allow the user to rename the parameter name in the left hand list.
+
+A more difficult suggestion is to rethink the way the numbered parameter UI works.  Putting numbers in a UI, without any explanation, is not intuitive or discoverable.  How does a newbie know to enter '1'?  The template documentation pages usually say to put in {{foo|blah}} ; they dont say {{foo|1=blah}} so the typical user doesnt know about '1'.",1380616208,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-qyjx6fdbrrh3weriir7z,task_subcomment,NA
+"Transclusion dialog: ""unknown parameter"" is confusing if TemplateData doesnt exist",The steps to reproduce are unclear to me. Also see https://www.mediawiki.org/wiki/How_to_report_a_bug,1379323419,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-qyjx6fdbrrh3weriir7z,task_subcomment,NA
+VisualEditor: Zero width no-break space is added to the end of the article (in a slug) in the editing element (but not the document),"I am trying to run the test at https://gerrit.wikimedia.org/r/#/c/83966/
+
+In the end it is trying to compare the text that was typed with the text that actually appears on the screen. The test fails, because the Zero width no-break space (U+FEFF) character is added to the string that appears on the screen.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378949100,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-mgmwirwldz45agzrgg3n,task_description,open
+VisualEditor: Zero width no-break space is added to the end of the article (in a slug) in the editing element (but not the document),Presumably this is ve.ce.BranchNode.$blockSlugTemplate.,1406595885,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mgmwirwldz45agzrgg3n,task_subcomment,NA
+Autocomplete for (local) image names,"It'd be nice if WikiLove had a javascripty autocomplete for image names (at least local ones)
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1378778340,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-ta7jealrbrncqvj3zzez,task_description,open
+Autocomplete for (local) image names,"(In reply to comment #1)
+> Any possibility of sharing a UI module with VisualEditor here, rather than
+> having two implementations of a media selection browser?
+
+Works for me. Though, ideally would go into core. WikiLove (optionally) depending on VisualEditor could be a potential problem
+
+MassMessage has a simple similar implementation of this, with based on resources/mediawiki/mediawiki.searchSuggest.js in core",1378840970,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-ta7jealrbrncqvj3zzez,task_subcomment,NA
+Autocomplete for (local) image names,"Any possibility of sharing a UI module with VisualEditor here, rather than having two implementations of a media selection browser?",1378839938,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-ta7jealrbrncqvj3zzez,task_subcomment,NA
+Reduce VisualEditor's memory usage,"Editing of large pages can use a significant amount of memory; a spotcheck that Max did on [[United States]] showed an increase of 121MB usage in Chrome while editing the page.
+
+This is a concern for us for mobile in particular, as today's mobile devices have the amount of memory of computers from several years ago -- most have 1GB or 512MB (or even less), which has to house the operating system, background apps, the web browser, and the *entire* article with a richly annotated DOM.
+
+Possible techniques for reducing memory usage were proposed at the VE mobile meeting yesterday:
+
+* Section editing -- if we only have to load up a single section at a time, large pages won't use up nearly as much memory. Note that on mobile we already divide the page up into sections surrounded by <div>s that can be replaced with the editable surface; the other sections on page might not even be open.
+
+* Limit full annotation processing to areas under active editing -- apparently it should be possible to delay some of the HTML processing on sections or even paragraphs that have not yet been edited. This might also save memory, but needs to be looked into.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378411260,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-aag3cwflmkojbhxxal5q,task_description,open
+Reduce VisualEditor's memory usage,"This is a high-level tracker bug rather than a blocker; it needs child bugs with more specifics to be nominated as blockers. Consequently, we decided to remove it from the Q3 blockers list at the triage on 2015-02-11.",1423879177,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,"More specific criteria and numbers are welcome / required here.
+Also, should the ""Epic"" tag be added here?",1423743458,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,">>! In T55825#558826, @brion wrote:
+> Feel free to move this to 'general' and we'll hang some mobile-specific bugs off it that are more directly actionable.
+
+Have any mobile-specific bugs been identified since 09/2013? Adding task numbers is welcome.",1423686484,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,"(In reply to comment #2)
+> Feel free to move this to 'general' and we'll hang some mobile-specific bugs
+> off it that are more directly actionable.
+
+{{Done}}",1378416264,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,Feel free to move this to 'general' and we'll hang some mobile-specific bugs off it that are more directly actionable.,1378415457,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,"Not sure this is a Mobile-specific bug, but yes, very important to make progress here. I think there's likely to be some produce trade-offs that are more appropriate for the Mobile than Desktop experience, though, so certainly some of it will be…",1378414642,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),"Users seem to expect that the feedback link will automatically supply information, especially the title of the article they're working on.  I'd also like to have the version number they were actually using (cacheing issues) and a link to the user's contibutions.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: enhancement",1378397100,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-dyxvwjhctefty5l6omxi,task_description,open
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),"The core feedback tool is (I think intentionally) very generic. If VE needs additional functionality, it should probably extend it.",1383301933,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dyxvwjhctefty5l6omxi,task_subcomment,NA
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),The feedback tool isn't specific to VisualEditor - moving to the general group for others to see and comment.,1383281154,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dyxvwjhctefty5l6omxi,task_subcomment,NA
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),"(In reply to comment #1)
+> Google has a feedback tool for Google+ which lets you ""screenshot"" the page
+> you
+> are on and highlight what you think is wrong. Something like that would be
+> really cool.
+
+That would be good, but possibly a bit more complicated for us. I wrote [[Wikipedia:Screenshots of Wikipedia]] to help people include screenshots in on-wiki bug reports, so linking prominently to that would be a very easy first step.",1380546133,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dyxvwjhctefty5l6omxi,task_subcomment,NA
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),"Google has a feedback tool for Google+ which lets you ""screenshot"" the page you are on and highlight what you think is wrong. Something like that would be really cool.",1378408265,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-dyxvwjhctefty5l6omxi,task_subcomment,NA
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","Right now external paste always writes the clipboard as formatted; in some cases, users will want to ""Paste Unformatted"".
+
+On Mac, there's a standard shortcut for this of Cmd+Shift+V - I'm assuming that Ctrl+Shift+V would be sensible as well.
+
+Would we also need a button? What about for the other standard 3 (Cut/Copy/Paste)?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378335600,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2uz6thdqdeegj4cxnbup,task_description,resolved
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","Change 88224 merged by jenkins-bot:
+Plain text paste with paste special
+
+https://gerrit.wikimedia.org/r/88224",1385500068,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2uz6thdqdeegj4cxnbup,task_subcomment,NA
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","Change 88224 had a related patch set uploaded by Esanders:
+Plain text paste with paste special
+
+https://gerrit.wikimedia.org/r/88224",1381178929,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2uz6thdqdeegj4cxnbup,task_subcomment,NA
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","(In reply to comment #1)
+> ctrl+shift+v in Open Office is ""paste special"", which gives lots of
+> non-default
+> options so it doesn't seem out of line. Not sure a separate button is needed
+> but if button=shortcut then shift+button should = shift+shortcut
+
+We don't need a button to have a shortcut (but we do for users without a keyboard, or with a limited keyboard that can't do shortcuts, like tablet users).
+
+> In general I think its best to cut/copy richly to the clipboard and let the
+> target deal with the formatting. I don't know whether this view is common or
+> uncommon though,
+
+I agree personally, but people have asked for it a few times and it's a not-hard change for us to make when pasting from the clipboard.",1378337286,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2uz6thdqdeegj4cxnbup,task_subcomment,NA
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","ctrl+shift+v in Open Office is ""paste special"", which gives lots of non-default options so it doesn't seem out of line. Not sure a separate button is needed but if button=shortcut then shift+button should = shift+shortcut
+
+In general I think its best to cut/copy richly to the clipboard and let the target deal with the formatting. I don't know whether this view is common or uncommon though,",1378336500,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-2uz6thdqdeegj4cxnbup,task_subcomment,NA
+"VisualEditor: On opening a reference which includes a single template and nothing else, also open that template's dialog","When you open an existing reference in VE that only consists of one template the main use case should be that you want to edit that template. But now you need to first select it and then klick on the puzzle piece.
+
+Instead I suggest that in that case, you get forwarded to the template editor directly after choosing to open the reference editor without having to do it manually.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378220100,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-jldo3wo4jenhs2iglbfo,task_description,resolved
+"VisualEditor: On opening a reference which includes a single template and nothing else, also open that template's dialog",This was done (for citation templates) in the new citation system.,1401472643,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jldo3wo4jenhs2iglbfo,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"The VisualEditor and ULS MediaWiki extensions have recently been blessed with QA browser tests.  We would need them to be in the Contint Jenkins and triggered by Zuul whenever a patchset is submitted as well as in the gate-and-submit pipeline.
+
+That needs several step:
+
+- describe the jobs in Jenkins
+- add the triggers in Zuul configuration
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1378194900,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_description,resolved
+[EPIC] trigger browser tests from Gerrit (tracking),As far as I know this is resolved a long time ago. Please reopen if there is anything left to be done.,1496054383,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Have to make the following extension to trigger the job on patchset proposal:
+
+CentralAuth
+CentralNotice
+Math
+PageTriage
+WikiLove
+",1488879529,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Change 341506 merged by jenkins-bot:
+[integration/config] Add experimental mwext-mw-selenium-jessie
+
+[[https://gerrit.wikimedia.org/r/341506]]
+",1488877980,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Change 341506 had a related patch set uploaded (by hashar):
+[integration/config] Add experimental mwext-mw-selenium-jessie
+
+[[https://gerrit.wikimedia.org/r/341506]]
+",1488877553,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"@dduvall made it possible to trigger selenium tests when a new patchset is triggered which unblocked a few tasks.
+
+Originally we had this blocked on T47499 which comes from Bugzilla and was the parent tracking task / epic for the #continuous-integration-scaling project.  It has progressed and we are not so far from having the jobs run on Nodepool.  That is {T137112} which is more specific than the legacy epic task and better reflect the intention.",1465249476,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"For mediawiki/extensions/VisualEditor no browser tests are run for patch upload nor merge, so it probably still needs to be done, possibly also for a few other closed blockers.",1450969250,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),">>! In T55697#1646493, @Jdlrobson wrote:
+> The description is a little confusing. Does VisualEditor do this already? I can't see the selenium job on a per commit basis....
+
+Still interested in the answer to this.
+",1450907160,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),The description is a little confusing. Does VisualEditor do this already? I can't see the selenium job on a per commit basis....,1442430477,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),I have closed a few tasks that were requesting browser tests to be triggered on patch proposal. There is no point in keeping them open until we are actually ready to trigger such jobs.,1427208701,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Per a discussion we had in the Releng weekly checkin, triggering browser tests from Gerrit would need the disposable VMs. We would also need to setup MediaWiki and the required backend services such as Parsoid (and more as needed).",1424944811,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"(In reply to Matthew Flaschen from comment #7)
+<snip>
+> What's the status of this?  Are there any projects that have browser tests
+> triggering on each change (even if non-voting)?
+> 
+> If not, can you outline the blockers?
+
+It is not hold, mostly because we lack resources to do the integration / make them faster.  On top of my head:
+
+* make them faster
+* runnable in parallel and aggregate the results
+* rethink the way we setup the environment to run the browser tests, it is currently a huge shell snippet which is copy pasted in different place
+
+
+Feel free to take the leadership. Zeljkof and Nik Everett would be able to assist.  I can offer reviews / guidances as well.",1415887484,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"(In reply to Antoine ""hashar"" Musso from comment #6)
+> This is no more a top priority.  We have most browsertests run twice per day
+> instead.
+> 
+> We will eventually managed to get them added in Gerrit, but there is a bit
+> more work that needs to be done first.
+
+What's the status of this?  Are there any projects that have browser tests triggering on each change (even if non-voting)?
+
+If not, can you outline the blockers?",1412275069,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"This is no more a top priority.  We have most browsertests run twice per day instead.
+
+We will eventually managed to get them added in Gerrit, but there is a bit more work that needs to be done first.",1405076783,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Quick status update:
+
+- ULS has browser tests being triggered albeit lot of tests ends up being
+- MobileFrontend has a patch that has browser tests passing locally against a freshly installed wiki. Pending review / merge then I will add the browser tests.
+- VisualEditor browser tests depends on some work to be done to safely start and stop a Parsoid daemon for each test.
+
+I am focusing this week on integrating Parsoid daemon in Jenkins",1386705460,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),The Jenkins jobo template in https://gerrit.wikimedia.org/r/#/c/86868/ would let us trigger tests.,1385379924,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),See also the Wiki page https://www.mediawiki.org/wiki/Continuous_integration/Browser_tests,1379694650,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),We will go with ULS first since we have a good experience interacting with the i18n team and they are in European timezone just like Zeljko and I.,1378225513,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"raise priority, add 'tracking' in summary.",1378225359,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+VIsualEditor: Allowing editing of attributes in MWAlienExtensionNode,"Need some UI to add/remove/edit the key value pairs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377906360,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-342y4tkwn6enbyuyqjn3,task_description,open
+VIsualEditor: Allowing editing of attributes in MWAlienExtensionNode,"As an update, this is done for editing, but not adding/removing.",1394479039,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-342y4tkwn6enbyuyqjn3,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, use ""Root#sets"" data to allow addition and/or completion of parameter > sets","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377905220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bjxf522olmedsdx6rpbc,task_description,open
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Adam Cuerden says,  ""I believe the VE team intends to have a some one click solutions in the near future, including adding templates of your choice to a bar? Although I'd hope there'd also be a few automatic lists you could choose to pull up - cleanup templates, etc.""
+
+So, it would be really comfy for users if the template editor, beyond being able to let them select what they need by typing the name, asked ""Which kind of template do you want to add?"" and provided lists of the most used/popular ones, divided per set (cleanup templates, citation templates and so on).
+Or just a way to store one's most used choices.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T52458}",1377873180,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_description,open
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"T209797 requests a specific subset of this, in a specific format, as part of semi-automated tool interfaces, for wikisource as well as VE.",1732669010,PHID-USER-t5o36keuho36mcmrau5j,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,CommTech is planning to address some of this with [[ https://phabricator.wikimedia.org/T367428  | Favorite Templates ]] ,1729696706,PHID-USER-gijtkzcktagsduwnkeo6,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The infobox could be suggested based on some categories of the article, specifically or generally, for example writer or just biography.",1715092406,PHID-USER-ygejgcs65h5nr3ssbueb,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Editing/Quickly_add_favorite_and_related_templates,1676201310,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/98c44ac3c7/wiki/Main_Page?veaction=edit",1675175353,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Editing/Quickly_add_infobox,1675173851,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Editing/Select_templates_by_categories,1606394588,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"CCing WMDE Technical Wishes team (https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Templates)
+
+@ecohen @Lena_WMDE @thiemowmde ",1585845044,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,Any clue on this?,1574156168,PHID-USER-g73uduhwmggntmexighn,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"> Um... A lot of it actually is defined locally on the wiki and won't work without non-trivial JSON configuration that maps it to local templates.
+
+Yes, I'm comparing them to templates that are 100% defined on wiki.
+
+> Infoboxes are very common, but unlike citations they are usually inserted only once when the article is created
+
+Yes, so as an editing tool, no particular template comes close to cite in terms of frequency of use (although I'm sure there are wiki-by-wiki examples where this is the case).
+
+> and VE is for some reason perceived more as a page editing tool than a page creation tool
+
+I don't see it this way either, but edits >> creations.
+
+I think this conversation belongs on T96710.",1558269856,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5192906, @Esanders wrote:
+>>>! In T55590#5192101, @Amire80 wrote:
+>> There is no good reason for this differentiation. Many templates could be first-class features like ""Cite"", although global templates should probably implemented first.
+> 
+> I think the distinction at the moment is that the Cite tools relate to extension functionality defined in the code, specifically templates wrapped in a <ref>, and the Citoid tool allows automatic population of those templates.
+
+Um... A lot of it actually //is// defined locally on the wiki and won't work without non-trivial JSON configuration that maps it to local templates.
+
+My theory is that Cite got its own button because the English Wikipedia community, unlike most others, enforces citations very strongly, and new citations are needed in new edits all the time. Infoboxes are very common, but unlike citations they are usually inserted only once when the article is created, and VE is for some reason perceived more as a page editing tool than a page creation tool. (//I// don't perceive it as such, and I use VE for creating pages whenever I can, but my impression is that a lot of people don't think of VE as a page creation tool.)
+
+> ""Suggested templates"" on the other hand are 100% defined on-wiki: the names of the templates to use, the implementation of the templates, and the metadata, so I think it's appropriate to think about these differently.
+
+Sure, but please do keep in mind that some day, better earlier than later, at least some templates should become global. When this finally happens, we can probably also have global JSON configuration for popular templates.",1558190892,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5192101, @Amire80 wrote:
+> There is no good reason for this differentiation. Many templates could be first-class features like ""Cite"", although global templates should probably implemented first.
+
+I think the distinction at the moment is that the Cite tools relate to extension functionality defined in the code, specifically templates wrapped in a <ref>, and the Citoid tool allows automatic population of those templates.
+
+""Suggested templates"" on the other hand are 100% defined on-wiki: the names of the templates to use, the implementation of the templates, and the metadata, so I think it's appropriate to think about these differently.
+
+That said there are certainly cases on a wiki by wiki basis where it would make sense to promote certain templates to the toolbar, and that is covered by T96710.
+
+",1558172962,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"I think curating locally is a good step, as different Wikipedias have different customs on this. Basque Wikipedia, for example, has 6 main templates that would cover around 80% of articles (statistics invented now)",1558126751,PHID-USER-g73uduhwmggntmexighn,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"This development looks good as a step forward. It's certainly better to have a cross-wiki uniform way for listing community curated things, than having local hacks on wikis.
+
+It shouldn't be a permanent solution, however. Some problems with it that need a deeper solution. For example, ""Cite"" has its own whole first-class button, and all the other templates will be hidden in this new list behind Insert -> Template, even though many templates are as useful and common as Cite is. There is no good reason for this differentiation. Many templates could be first-class features like ""Cite"", although global templates should probably implemented first.
+
+But still, it's a step in the right direction.",1558126633,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5191516, @Trizek-WMF wrote:
+> That's the list of most popular (aka most used templates), right?
+
+No, it will be a community-curated list, defined on-wiki in a JSON message file. Otherwise you'd probably end up with useless crap like `{{!}}`.",1558114037,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5191516, @Trizek-WMF wrote:
+> That's the list of most popular (aka most used templates), right?
+
+No, it will be a fixed list, defined on-wiki in a JSON message file. Otherwise you'd probably end up with useless crap like `{{!}}`.",1558113546,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5191516, @Trizek-WMF wrote:
+> That's the list of most popular (aka most used templates), right?
+
+No, it will be a fixed list, defined on-wiki in a JSON message file.",1558113274,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"That's the list of most popular (aka most used templates), right?",1558112406,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Here's how it looks on my local install:
+{F29090517,size=full}",1558112173,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"@Whatamidoing-WMF tells me that English Wikivoyage would be a good candidate for a potential test: ""they have 6 templates they use all the time"". I think French Wikipedia would be a good candidate too. ",1558112074,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T223534#5189267, @Theklan wrote:
+> I think the first one would work.
+
+
+
+>>! In T223534#5189303, @Esanders wrote:
+> For anyone interested working  on this, the code would go in `ve.ui.MWTemplatePlaceholderPage`, and would need to do the following:
+> # Fetch the JSON data for the local wiki using mw.message, see `ve.ui.Citoid.init.js` for an example of this.
+> # Get the template descriptions for the listed templates using the API, see the request that the search box uses
+> # Append a list of mw.widgets.TitleOptionWidgets to the page
+
+
+
+>>! In T223534#5190232, @Trizek wrote:
+> I'll give my eternal reconnaissance as a community member to whoever achieves that task. This is something we miss since a while on French Wikipedia. 
+> 
+> Also, that task is probably a duplicate of {T96710}.
+
+
+
+>>! In T223534#5190242, @Theklan wrote:
+> @Trizek-WMF it is similar, but this would be adding the most usual ones, as we are working with 6 automated templates that are highly used.
+
+
+
+>>! In T223534#5191300, @Esanders wrote:
+> I think T96710 is asking for a similar feature, but adding buttons to the toolbar, not the template dialog.
+
+",1558109768,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T223534#5189252, @Esanders wrote:
+> I think for a first pass on this we can allow wikis to define a list of most common templates on wiki, e.g.
+> ```lang=json,name=MediaWiki:Template-directory.json
+> [
+>   ""Biografia infotaula automatikoa"",
+>   ...
+> ]
+> ```
+> 
+> This could then be fetched by the template dialog and show in the space below the search input:
+> 
+> {F29083664,width=350}
+> 
+> 
+> In the future we would probably want to make this more flexible, such as by grouping templates together, e.g.
+> ```lang=json,name=MediaWiki:Template-directory.json
+> [
+>   {
+>     ""group"": ""Infoboxes"",
+>     ""templates"": [
+>       ""Biografia infotaula automatikoa"",
+>       ...
+>     ]
+>   }
+> ]
+> ```
+> 
+> which would necessitate a slightly more complex UI.
+
+",1558109701,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T223534#5189228, @Theklan wrote:
+> When we click in the insert template button we get a white pop-up where we must figure out what the correct template is. In Basque wikipedia we are using a reduced automatic templates system, so it would be very useful to have them listed just below, so you can click them and choose.
+> 
+> Most useful infoboxes:
+> 
+> * {{biografia infotaula automatikoa}}
+> * {{artelan infotaula automatikoa}} < for artworks
+> * {{Eraikin infotaula automatikoa}} < buildings
+> * {{Hiri orokor infotaula}} < cities
+> * {{Probintzia orokor infotaula}} < administrative units up from cities
+> * {{taxotaula automatikoa}} < taxobox
+
+",1558109622,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Change 510943 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Allow popular templates to be listed in the template dialog
+
+[[https://gerrit.wikimedia.org/r/510943]]",1558109586,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,{T109253} looks like a similar request.,1510330562,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#1673809, @Elitre wrote:
+> @James_F, is this something a gadget could easily achieve?
+
+It could, but I'd rather avoid people adding new things to the toolbar //ad hoc//. We really need a design for this that can scale.",1443172692,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"@James_F, is this something a gadget could easily achieve?",1443171649,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Mmm... I don't know if it's a //blocker//, but it is quite desirable.",1434708828,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"I suggest that per Amire80, cross-wiki templates be made a blocker bug for this feature.
+
+It's just too much widely duplicated work to do otherwise.",1434682068,PHID-USER-rtxvf2yd2qd3qmsps3bk,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,It would really be appreciated in wikipedia's sister projects to have a costumizable common templates dropdown as there is with the citation tool.,1429796328,PHID-USER-igg6dsz3ijszcxvvirgp,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The more I use VE, the more I miss such a feature.
+
+The challenge with it is that it's badly project-specific, so community editors will need an easy way to customize this list, but something like this already done for citation templates, so it should be possible for other templates as well.
+
+This is one issue for which it's REALLY worth poking around Wikimedia projects in different languages to ask them what would they like in such a feature, and what current features they currently have that are similar to this. For example, the Hebrew Wikipedia has the Templateslist script ( https://he.wikipedia.org/wiki/MediaWiki:Templateslist.js ), which adds a dropdown with common templates to the Vector editing toolbar, and users there complain that they don't want to use VE because VE doesn't have such a list.
+
+I'm not rushing - this requires proper research, understanding and design, but it should be somewhere in the roadmap.",1434455793,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The more I use VE, the more I miss such a feature.
+
+The challenge with it is that it's badly project-specific, so community editors will need an easy way to customize this list, but something like is already done for citation templates, so it should be possible for other templates as well.
+
+This is one issue for which it's REALLY worth poking around Wikimedia projects in different languages to ask them what would they like in such a feature, and what current features they currently have that are similar to this. For example, the Hebrew Wikipedia has the Templateslist script ( https://he.wikipedia.org/wiki/MediaWiki:Templateslist.js ), which adds a dropdown with common templates to the Vector editing toolbar, and users there complain that they don't want to use VE because VE doesn't have such a list.
+
+I'm not rushing - this requires proper research, understanding and design, but it should be somewhere in the roadmap.",1420149875,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The more I use VE, the more I miss such feature.
+
+The challenge with it is that it's badly project-specific, so community editors will need an easy way to customize this list, but something like is already done for citation templates, so it should be possible for other templates as well.
+
+This is one issue for which it's REALLY worth poking around Wikimedia projects in different languages to ask them what would they like in such a feature, and what current features they currently have that are similar to this. For example, the Hebrew Wikipedia has the Templateslist script ( https://he.wikipedia.org/wiki/MediaWiki:Templateslist.js ), which adds a dropdown with common templates to the Vector editing toolbar, and users there complain that they don't want to use VE because VE doesn't have such a list.
+
+I'm not rushing - this requires proper research, understanding and design, but it should be somewhere in the roadmap.",1416866083,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,*** Bug 69787 has been marked as a duplicate of this bug. ***,1408571387,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The main priority is a (very limited) suggestion of quick-inserting templates when in a reference, which is bug 50458.
+
+This is certainly a possibility, but would probably want to be context-specific (so it only suggests clean-up templates when your cursors is at the top of the page; only suggests stubs when at the bottom; etc.).",1377908590,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Created attachment 13203
+A very quick mockup for quick access buttons
+
+One idea I've had is to use some of the empty vertical space on the right of the dialog for some quick access buttons. See attachment for a 2 minute mockup of how this might look. The labels I've used in the mockup are not necessarily the right ones, they're just ones I quickly thought of.
+
+Either the buttons could be set to allow one-click access to certain templates, or to be drop-down lists of similar related ones. Possibly the two could be combined - click to get the top item in the list, or click and hold for a moment to open the drop down for short list (almost certainly no more than 10, probably less than that) of similar ones.
+
+Selecting any of these would have the same effect as typing the name into the search field, selecting it, and clicking to add the template.
+
+A second idea would be to change the transclusion editor button from a simple button to a combined button/drop down as I described above. Here you could only have a single list but it could be longer. Selecting a template from this list would load the transclusion editor with that template preloaded into it.
+
+Some way of customising either/both lists (beyond recently used) would be useful too.
+
+**Attached**: {F11786}",1377900016,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","As discussed at bug 50452 comment 9 it would be very useful for a page to have associated metadata about its title.
+
+For most pages and by default* this would be identical to the all-lowercase rendering of its stored title, but where pages correctly start with a lowercase letter (on wikis where the first character is case insensitive), contain special characters or conflict with interwikis/namespaces, etc. the metadata would record the correct page title. It could also be used for titles that should be italicised.
+e.g. on en.wp:
+Page Title         - Correct Title
+[[IPad]]           - iPad
+[[Benzo(a)pyrene]] - Benzo[a]pyrene
+[[Pilot No. 5]]    - Pilot #5
+[[D Ream]]         - D:Ream
+[[Computer]]       - computer [indicating a common noun]
+[[Amy Studt]]      - Amy Studt [indicating the title is proper noun]
+[[Animal Farm]]    - <i>Animal Farm</i> [italicised proper noun, the tags are not literal]
+
+The displayed title would be taken from this metadata and as such would effectively supercede the DISPLAYTITLE magic word and the [[template:correct title]] family of templates (and the equivalents on other wikis).
+
+VisualEditor and any other tools that aid linking would be able to read the metadata and use it to determine what the default displayed name should be when linking to that article.
+
+*Actually the default should be configurable as I guess languages like German that capitalise common nouns may want the default to be capitalised and the upper/lower case distinction probably doesn't make sense in all scripts.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50452
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56868
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49076",1377811860,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_description,open
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)",">The advantage of storing this metadata is that it allows for a large amount of
+>semantic information about the title which can be used not only for linking but
+>potentially for customised display options and doubtless more that I haven't
+>thought of.
+
+That's certainly true. 
+-----
+
+My initial reaction is that the user is probably in a better position to decide how to capitalize/italicize the title in a given context than software would be, but if such formatting of titles is consistent, I suppose it could make sense to automatically do it.
+
+>I'm told that it needs to be moved out of templates for VE to support.
+
+It should not need that to *use* the data. To effectively edit the displaytitle data, it may need that.
+
+>I don't
+>know why.
+>More philosophical, but I was under the impression that the long term goal was
+>to separate metadata from content?
+
+Some folks have that goal. Personally I think that doing so would reduce the power of mediawiki significantly, although my opinion may be a minority one. (And probably offtopic for this bug report)",1378773876,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","(In reply to comment #4)
+> > 
+> > The idea is not just to store what the title should be displayed as when it
+> > doesn't match the default, but to record what the title actually is in all
+> > cases. Presently there is afaik no way to tell that for example [[Parish
+> > ale]]
+> > is a common noun, [[Parish Walk]] is a proper noun and [[Parish Bar]] is a
+> > proper noun that should be italicised.
+> 
+> *Does it really make sense to store what type of word the title is, instead
+> of just how to display it. 
+
+Sorry that was my poor explanation. For tools (such as VisualEditor) to offer a sensible default for the display of a link the tool needs to know how the title should be displayed. In mid sentence:
+*The vicar drank some [[parish ale]] and declared it ""rather good""
+*The vicar competed in the 2013 [[Parish Walk]], raising money for the church roof.
+*The vicar enjoyed listening to the ''[[Parish Bar]]'' album while driving.
+
+At present only the last of these has need of a {{DISPLAYTITLE}} because the unitalicised format with an initial capital letter is correct when it appears as a page title. This tells us nothing about how it should be used in other contexts, and the DISPLAYTITLE for the third example tells us nothing about capitalisation mid-sentence. In other words we want to store the information about how the title should be used in all cases, not just when it doesn't match the default.
+
+It seems to me that there are three options for how to structure this metadata. 
+The first is to simply store the format, e.g. ""title: ''Parish Bar''"" or ""title: parish ale"".
+The second is to define classes of titles and how they are displayed and assign each article title to one such class. e.g. for Parish Walk ""title class: proper noun"" and for Parish Bar: ""title class: musical album title""
+The third option is to store a class (without that defining the display) and the display: ""title: ''Parish Bar''; class: musical album title"".
+
+The classes and (associated) displays would need to be configurable per wiki for either of those options to work.
+
+I've also realised that separate fields would be good for ""title"" and ""disambiguator"", e.g. for the article at [[Mercury (element)]]: ""title: mercury""; ""disambiguator: element""; class: ""common noun"" or for [[Wellington, Somerset]]: ""title: Wellington""; ""disambiguator: Somerset""; ""class: place name""
+
+The advantage of storing this metadata is that it allows for a large amount of semantic information about the title which can be used not only for linking but potentially for customised display options and doubtless more that I haven't thought of.
+
+> *What problem (Other than perhaps ideological) does moving the data out of
+> templates actually solve?
+I'm told that it needs to be moved out of templates for VE to support. I don't know why.
+More philosophical, but I was under the impression that the long term goal was to separate metadata from content?",1378772376,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","
+> 
+> The idea is not just to store what the title should be displayed as when it
+> doesn't match the default, but to record what the title actually is in all
+> cases. Presently there is afaik no way to tell that for example [[Parish
+> ale]]
+> is a common noun, [[Parish Walk]] is a proper noun and [[Parish Bar]] is a
+> proper noun that should be italicised.
+
+I don't think I properly understand the problem this is trying to solve. To be honest it sounds like a solution looking for a problem.
+
+Basically what I'm asking:
+*Does it really make sense to store what type of word the title is, instead of just how to display it. Mapping types of words -> how to display them sounds like something that would vary a lot by culture (Or even in english wikis that have different traditions)
+*What problem (Other than perhaps ideological) does moving the data out of templates actually solve?",1378768930,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","(In reply to comment #1)
+> I'm confused. Is this asking to move {{DISPLAYTITLE:...}} out of wikitext?
+> 
+> Displaytitle is a form of metadata, and it gets stored in the db separately,
+> and can be queried separately, etc.
+
+Chris has it right - it's effectively asking to implement DISPLAYTITLE properly, rather than DISPLAYTITLEIFNEEDEDTOBEANOVERRIDE.",1378766620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","According to James F at  bug 50452 comment 9 ""for this to be used in VisualEditor it would need to be a proper feature and not one hacked into a template""
+
+The idea is not just to store what the title should be displayed as when it doesn't match the default, but to record what the title actually is in all cases. Presently there is afaik no way to tell that for example [[Parish ale]] is a common noun, [[Parish Walk]] is a proper noun and [[Parish Bar]] is a proper noun that should be italicised.",1378283614,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","I'm confused. Is this asking to move {{DISPLAYTITLE:...}} out of wikitext?
+
+Displaytitle is a form of metadata, and it gets stored in the db separately, and can be queried separately, etc.",1377892939,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","If you start to add a link, and change your mind (e.g., you realized that you have the wrong word selected), there is no way to simply cancel adding a link.  You have to remove the link with the trashcan icon.
+
+Steps to reproduce:
+
+1. Select any word.
+2. Press ctrl-K to enter link tool.
+3. Attempt to cancel the link by closing the unwanted link tool dialog box using Esc key or the < button.
+4. Discover that VisualEditor linked the word anyway.
+
+If the Escape key and ""Cancel"" button are worthless for escaping/going back/cancelling, then they shouldn't be present or have any effect.
+
+({T93749} altered this to re-add the cancel/close button.)",1377799620,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-reeypst4562edb7eoqfi,task_description,resolved
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","Change 209695 merged by jenkins-bot:
+Only apply annotations if 'done' is clicked
+
+[[https://gerrit.wikimedia.org/r/209695]]",1433183692,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","Change 209695 had a related patch set uploaded (by Jforrester):
+Only apply annotations if 'done' is clicked
+
+[[https://gerrit.wikimedia.org/r/209695]]
+",1432909435,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","We now have a ""Remove"" button, which is nice, but since the link is automatically created when you open the inspector, most people don't know that if you did nothing and want nothing to make the link, then you still need to ""Remove"" the link that you didn't know you already made.",1430939284,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","Maybe we should label the ""cancel"" button ""remove"" or somesuch? I don't know…",1429559622,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing",*** Bug 56431 has been marked as a duplicate of this bug. ***,1395197399,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","I'm not sure that the < button is going to be interpreted as ""close and apply"".  It looks to me a lot more like a ""get me out of here"" or ""go back (to how things were)"" button.  I think that it ought to be treated the same as an Escape key.",1378763198,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","I'm getting very frustrated with the current behaviour of the link tool in this regard.
+
+When I am in the link dialog and I press escape I want the dialog to exit and leave the page in the state it was in before I loaded the dialog, ignoring any changes I have made and whether I was adding or modifying a link.
+
+The current behaviour of the < button (close and apply the current state) and the rubbish bin (close and remove link) are correct. 
+
+There also though needs to be a button/icon though that closes and cancels all changes made (this is bug 52462).",1378124944,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","This is due to fixing bug 51065; we can either have one or the other, but not both. I'm minded to stick with the behaviour as it now is, as it's less confusing that the previous form was.
+
+Consequently, marking as WONTFIX. Very happy to be argued around to the opposite behaviour, however.",1377834959,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"The Parsoid team is considering a simplification of the different mw:ExtLink/* variants to just a single mw:ExtLink type. 
+
+For most types this should not make much of a difference to VE, but for auto-numbered external links ([http://example.com]) it might, so I am looking for your input. I did some testing on https://www.mediawiki.org/wiki/User:GWicke/TestNumberedLinks. Changes to the text lead to corruption as in this diff:
+
+https://www.mediawiki.org/w/index.php?title=User%3AGWicke%2FTestNumberedLinks&diff=772988&oldid=772987
+
+There also does not seem to be any automatic re-numbering when a numbered link is changed into a plain external link.
+
+What are you plans for the handling of numbered links?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377728940,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_description,resolved
+VisualEditor: Provide a way for users to edit auto-numbered external links,*** Bug 57755 has been marked as a duplicate of this bug. ***,1386000770,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Change 98114 merged by jenkins-bot:
+Make autonumbered external links inspectable
+
+https://gerrit.wikimedia.org/r/98114",1385801891,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Change 98114 had a related patch set uploaded by Catrope:
+Make autonumbered external links inspectable
+
+https://gerrit.wikimedia.org/r/98114",1385662180,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,*** Bug 57419 has been marked as a duplicate of this bug. ***,1385489060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Though the code in gerrit 90432 is merged, that just adjusts how VisualEditor works with auto-numbered links to support Parsoid's changed behaviour - this bug remains undone. Resetting to ASSIGNED.",1382368642,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Change 90432 merged by jenkins-bot:
+Add a node type for numbered external links
+
+https://gerrit.wikimedia.org/r/90432",1382353256,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Change 90432 had a related patch set uploaded by Catrope:
+Add a node type for numbered external links
+
+https://gerrit.wikimedia.org/r/90432",1382043276,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"I guess that means that we can go ahead and drop the explicit numbering in Parsoid in favor of pure CSS. We will also drop the /Numbered typeof suffix along with the other mw:ExtLink suffixes.
+
+You will then get empty links with typeof=""mw:ExtLink"" as in this example.",1377816806,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"
+* Supports:
+  - http://caniuse.com/#feat=css-sel3 (CSS3 :empty)
+  - http://caniuse.com/#feat=css-counters (counter-increment)
+  - http://caniuse.com/#feat=css-gencontent (:before)
+
+* Test case: http://jsfiddle.net/wTNc4/
+  - Works fine in IE9: http://cl.ly/image/2r2L1F3U2X0r
+
+I wonder why it didn't work for James?",1377816701,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"(In reply to comment #5)
+> Please test this test with IE as well. I am hopeful that it works with IE >=
+> 8.
+
+In IE9 you get ""not empty"" but none of the other four links.
+
+In IE10 and IE11 you get all five links as expected.",1377816286,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Yeah, you need the UI for the creation of empty links. But there is no need to deal with renumbering etc in VE, which simplifies things a lot.
+
+Please test this test with IE as well. I am hopeful that it works with IE >= 8.",1377814874,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"(In reply to comment #3)
+> With a href set this actually works as expected in FF and Chrome:
+
+[…]
+
+> So it seems that we can actually implement auto-numbered links in pure CSS.
+
+That's great. :-)
+
+We will still need a way of creating an auto-numbered external link (rather than just being able to copy and alter them), but that's our problem. :-)",1377814131,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"With a href set this actually works as expected in FF and Chrome:
+
+<html><head>
+<style>
+body {
+    counter-reset: numberedlink;
+}
+a[typeof~=""mw:ExtLink""]:empty:after {
+    content: ""["" counter(numberedlink) ""]"";
+    counter-increment: numberedlink;
+}
+</style>
+</head>
+<body>
+<a href=""test"" typeof=""mw:ExtLink""></a>
+<a href=""test"" typeof=""mw:ExtLink"">not empty</a>
+<a href=""test"" typeof=""mw:ExtLink""></a>
+<a href=""test"" typeof=""mw:ExtLink""></a>
+<a href=""test"" typeof=""mw:ExtLink""></a>
+</body>
+</html>
+
+So it seems that we can actually implement auto-numbered links in pure CSS.",1377813350,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,See http://www.w3.org/TR/css3-content/ for the relevant spec.,1377811927,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Maybe this could even be handled in CSS, somewhat like this example:
+
+<html><head>
+<style>
+body {
+    color: red;
+    counter-reset: numberedlink;
+}
+a[typeof~=""mw:ExtLink""]:empty:before {
+    content: ""["" counter(numberedlink) ""]"";
+    counter-increment: numberedlink;
+}
+</style>
+</head>
+<body>
+<a typeof=""mw:ExtLink""></a>
+<a typeof=""mw:ExtLink""></a>
+<a typeof=""mw:ExtLink""></a>
+<a typeof=""mw:ExtLink""></a>
+</body>
+</html>
+
+Problems in this simple experiment:
+
+* Links are not clickable, and (maybe related)
+* the content can only be generated :before and :after, but not inside the empty link.",1377811764,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: trouble with Template:Hlist,"Reporting user comment, some formatting is mine:
+<<I made this http://en.wikipedia.org/wiki/User:Atethnekos/sandbox4 as a demonstration. 
+1) If the hlist template is used in an infobox or a table like on the page, when I go to VE, the list will end up be extended far into the page. 
+2) If it's used with [[File:Image]] as on the page, the list will end up being cut off, and then some weird things will happen if I try to click on the hlist template (e.g., the page will be extended to right and my browser will give a horizontal scroll bar). FF 23.0.1 Win7--Atethnekos 19:33, 25 August 2013 (UTC) >>
+
+I edited his sandbox a couple of times. In this version http://en.wikipedia.org/w/index.php?title=User:Atethnekos/sandbox4&oldid=570256245&veaction=edit the pics of the masks are moved to the left: the caption of the first one is not cut out, but you can't edit the pics at all since VE will consider them as a non editable block.
+I can't reproduce the horizontal bar and I can correctly edit the hlist template inside the mask pic caption with both FF and Chrome.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377521880,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-l6w6nyonc7ci3mnehffx,task_description,resolved
+VisualEditor: trouble with Template:Hlist,"The previous comments don't explain what/who exactly this task is //stalled// on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)).
+
+> the list will end up be extended far into the page.
+Does not seem to happen anymore:
+
+{F31846960}
+
+> If it's used with [[File:Image]] as on the page, the list will end up being cut off, and then some weird things will happen if I try to click on the hlist template (e.g., the page will be extended to right and my browser will give a horizontal scroll bar).
+
+Cannot reproduce in Firefox 76.
+
+>  but you can't edit the pics at all since VE will consider them as a non editable block.
+
+If I understand correctly then I cannot reproduce:
+
+{F31846963}
+
+{F31846962}
+
+If this still happens then please follow https://www.mediawiki.org/wiki/How_to_report_a_bug (clear steps to reproduce; what's expected; what happens instead; in separate sections) and reopen this ticket.
+
+For the records, wiki text test case here is
+```
+{{Infobox philosopher
+|image = File:NAMA Masque esclave.jpg
+|caption = Geloius: copy of portrait bust by [[Silanion]]
+|name = Geloius
+|birth_place = [[Athens]]
+|main_interests  = {{hlist |nullus |primus |secundus |tertius |quartus |quintus |sextus |septus |octavus |nonus |decimus |et ceterus }}
+}}
+```
+
+",1590760929,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-l6w6nyonc7ci3mnehffx,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"Same as #51959, but it keeps hapenning on frwiki: some texts that look like telephone numbers are changed in <a href=""tel:..."">...</a>.
+
+http://fr.wikipedia.org/w/index.php?title=Les_Visiteurs_(film,_1993)&diff=95954243&oldid=95559259
+
+http://fr.wikipedia.org/w/index.php?title=Transformers_3_:_La_Face_cach%C3%A9e_de_la_Lune&diff=96093057&oldid=95089445
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: other
+**Platform**: Other
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51959",1377428640,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-26knsdpm5excrpowc3dw,task_description,resolved
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,On re-testing this is now fixed.,1430334450,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"(In reply to Elitre from comment #10)
+> So, James, is this what we are going to do, adding this line? Thanks.
+
+Yes, experimentation as to what triggers Safari to break things, and what changes cause it to stop breaking, is needed.",1398787080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"So, James, is this what we are going to do, adding this line? Thanks.",1396944069,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"The answer appears to be to have:
+
+  <meta name = ""format-detection"" content = ""telephone=no"">
+
+… in the <head> of the page. Unfortunately, we probably don't want to switch this off for all MediaWiki pages, so instead we will need to experiment to see if JS inserting it into there makes the behaviour go away.",1395762161,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"(In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #5)
+> Hmmm, it seems I was close enough ;)
+> 
+> ""In Safari on iOS, telephone number detection is on by default"" according to
+> [1]. There it says that adding <meta name=""format-detection""
+> content=""telephone=no""/> would prevent that autolink feature, that may
+> interfere with the content editable component of the editor.
+> 
+> ----
+> 
+> [1]
+> https://developer.apple.com/library/safari/featuredarticles/
+> iPhoneURLScheme_Reference/Articles/PhoneLinks.html
+
+That URL is no longer valid. This is the new one:
+
+https://developer.apple.com/library/ios/featuredarticles/iPhoneURLScheme_Reference/PhoneLinks/PhoneLinks.html",1393672711,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"And, yes, I really think that VE/Parsoid should find a way to detect changes from browser extensions and neutralize them, otherwise it will be an endless battle to have every extension modified, updated, ...",1377442673,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"(In reply to comment #4)
+> This might be a bug in Safari rather than VE, but even if it is it would be
+> useful for VE (or Parsoid?) to detect the changes and neutralise them. It is
+> unlikely that Wikipedia would need href=tel: links but I can see they might
+> be
+> useful in environments like the contact pages on the Foundation wiki, so
+> stripping such links completely mightn't be the optimal solution?
+
+Isn't the <a> tag deactivated on the Foundation wiki also, as it is on Wikipedia ?
+On Wikipedia, the <a href=""tel:..."">...</a> doesn't produce a link because MediaWiki renders the <a> tag as text.
+
+Even if ""tel:"" was needed on any wiki, it would be better handled as an external link [tel:... ...] than as a <a> tag.",1377442583,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"Hmmm, it seems I was close enough ;)
+
+""In Safari on iOS, telephone number detection is on by default"" according to [1]. There it says that adding <meta name=""format-detection"" content=""telephone=no""/> would prevent that autolink feature, that may interfere with the content editable component of the editor.
+
+----
+
+[1] https://developer.apple.com/library/safari/featuredarticles/iPhoneURLScheme_Reference/Articles/PhoneLinks.html",1377441939,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"Bug 51959 was also iPad/Safari and I've not seen any reports of it being reproducible on any other system so I've adjusted the bug summary accordingly.
+
+This might be a bug in Safari rather than VE, but even if it is it would be useful for VE (or Parsoid?) to detect the changes and neutralise them. It is unlikely that Wikipedia would need href=tel: links but I can see they might be useful in environments like the contact pages on the Foundation wiki, so stripping such links completely mightn't be the optimal solution?",1377441370,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"For the first one, iPad with Safari.
+No answer for the seconde one.",1377440082,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"May it be caused by a Skype plugin for the browser, that usually make those telephone-looking numbers into a clickable link to make a call through Skype?
+
+http://stackoverflow.com/questions/3032427/how-to-prevent-phone-numbers-to-be-converted-into-skype-links",1377431900,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"I can't reproduce it on either page using Firefox 23 / Linux.
+
+Do you know what OS/browser those editors were using?",1377431452,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"EverNote Web Clipper has a problem with the editable area and inserts:
+
+<style id=""_clearly_component__css"" type=""text/css"">#next_pages_container { width: 5px; hight: 5px; position: absolute; top: -100px; left: -100px; z-index: 2147483647 !important; } </style><div id=""_clearly_component__next_pages_container""></div>
+
+Triggering: https://en.wikipedia.org/wiki/Special:AbuseFilter/345
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377255600,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-pxgyjw5isiqywctk5c7e,task_description,resolved
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114013,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113100,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"Derk-Jan, did you hear back from Evernote?",1406844430,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,Evernote support ticket #253866,1385645050,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"I submitted a report with Evernote trough their API developers platform.
+
+http://dev.evernote.com/support/faq.php#filebug
+
+Not totally the right forum, but I suspect that was the easiest way to get developer level support.",1377256101,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Hieroglyphics tool inserts a new line at the cursor whether or not you actually insert a hieroglyphics block,"Screeshot of post hiero editor
+
+Safari 6
+
+I opened the editor inline, didn't do anything, pressed the back arrow, the editor closed and inserted a newline.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11956}",1377250800,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ur6ykzlvrepzlje7qdsa,task_description,open
+Support Clipboard Based Image Upload,"**Author:** `lucashokanson`
+
+**Description:**
+It would be extraordinarily useful to mimic Imgur.com's clipboard based uploader.  Upon visiting the upload page, you would simply Paste - command/control v or click a button to use your clipboard's contents.  This would then upload the file and return to you the standard file:____ page.  
+
+In addition to this, if this functionality is built it, it would even more useful to streamline this into the page editor as well. A simple button click could pop up a prompt and upon upload return the proper image reference in your article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=37932
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65670",1377203100,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-jbmwpl35zyrkzdw4hfwx,task_description,duplicate
+Support Clipboard Based Image Upload,I'm going to move this to upload wizard I suppose.,1377203439,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-jbmwpl35zyrkzdw4hfwx,task_subcomment,NA
+Support Clipboard Based Image Upload,"There's an ambition to add this to VisualEditor in time - see bug 37932, which I've added as a see also - but not sure on plans for doing this for the regular wikitext editor.",1377203318,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jbmwpl35zyrkzdw4hfwx,task_subcomment,NA
+VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users),"In Chrome, edit any page in https://test2.wikipedia.org
+
+Click Transclusion, type 's' into input box.
+Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""
+
+In Firefox, edit any page in https://test2.wikipedia.org
+
+Click Transclusion, type 's' into input box.
+Result is a list of suggestions that begin with ""Succession box"" and ""South America""
+
+This suggests that at least one list of Template suggestions is absolutely incorrect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-gi6xthiyrxw7c2mnmgvl,task_description,declined
+VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users),*** Bug 70219 has been marked as a duplicate of this bug. ***,1416339245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gi6xthiyrxw7c2mnmgvl,task_subcomment,NA
+VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users),"This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit). Not sure if this is a ""bug"" per se…",1387245600,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gi6xthiyrxw7c2mnmgvl,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned <div>s used to create pie charts(!) to break,"https://he.wikipedia.org/wiki/%D7%A8%D7%90%D7%A9%D7%95%D7%9F_%D7%9C%D7%A6%D7%99%D7%95%D7%9F?veaction=edit
+
+The template on the left has a pie chart (see in view mode in the extendable green section) -- but in edit mode it's all jumbled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+{T53932}
+{T53166}",1377192840,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-s55lzef3gmpfhhdexj66,task_description,resolved
+VisualEditor: CSS munging causing absolutely-positioned <div>s used to create pie charts(!) to break,"The issue as filed was resolved long time ago (see parent bug T52577), I filed T96667 to track the issue of oversized highlights.",1429615765,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-s55lzef3gmpfhhdexj66,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned <div>s used to create pie charts(!) to break,"There are no screenshots here to show how it used to be broken, but it seems almost correct now. Only the highlight is displayed incorrectly.
+
+(The infobox also looks a bit borked, which is a Parsoid issue I filed as T96529.)
+
+{F117709}",1429478036,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-s55lzef3gmpfhhdexj66,task_subcomment,NA
+"VisualEditor: Hieroglyphics tool operating on a selection replaces the content, rather than appending the hieroglyphics block","Testing the hieroglyphics feature on MW.org just now:
+
+1. Open VE and select some text
+2. Click ""Hieroglyphics"" button
+
+Why can I ""apply"" hieroglyphics to a run of text, as if it was a kind of formatting? Doesn't make any sense.
+
+3. Type some hiero codes (e.g. G26-t:Z4-A40) in the box
+4. Leave the popup (by clicking away/clicking the < button)
+
+The popup goes blank and can't be dismissed (Firefox 23).
+Also notice that no hieroglyphics are seen.
+
+5. Review changes.
+
+The hiero tag successfully appears in the wikitext, even though it is invisible in VE.
+
+Sorry for three issues in one bug, but I guess you guys can figure this out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1376996400,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cq2sis2akuochldidpvr,task_description,declined
+"VisualEditor: Hieroglyphics tool operating on a selection replaces the content, rather than appending the hieroglyphics block",I can't reproduce any of these issues in Chrome or Firefox. Please re-open with details if you can.,1386337120,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cq2sis2akuochldidpvr,task_subcomment,NA
+"VisualEditor: Hieroglyphics tool operating on a selection replaces the content, rather than appending the hieroglyphics block","The second and third issues are now fixed. However, you can still ""apply"" hieroglyphics (and LaTeX) to a run of text: this behavior is confusing and nonsensical.",1379825433,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cq2sis2akuochldidpvr,task_subcomment,NA
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page","Some users on en.wp consider it a bug that VE shows the top of the page after you edit a ""section"", and demand instead that, as VE auto-scrolls to the relevant section when you click Edit, it does the same after you save. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376995620,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-unso5k7lgj5lojo4gz7w,task_description,resolved
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page","Yes, it does seem to. There could still be some polishing done to make it smoother, but it does work, so this task is resolved.",1541160256,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-unso5k7lgj5lojo4gz7w,task_subcomment,NA
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page","It seems to work in recent versions of VisualEditor, isn’t it?",1541159845,PHID-USER-2nopae2cxuamwcbndaih,PHID-TASK-unso5k7lgj5lojo4gz7w,task_subcomment,NA
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page",*** Bug 54645 has been marked as a duplicate of this bug. ***,1392058252,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-unso5k7lgj5lojo4gz7w,task_subcomment,NA
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page","Not sure, is https://bugzilla.wikimedia.org/show_bug.cgi?id=52566 a dupe?",1384269494,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-unso5k7lgj5lojo4gz7w,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","If you have the preference set to ""Edit pages on double click"", then double-clicking on a word while you're already in VisualEditor tries to re-open the page so you can edit it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Double-click_asks_if_you_want_to_leave_page",1376935080,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_description,resolved
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","Change 162968 merged by jenkins-bot:
+Stop ""Edit pages on double click"" from affecting VE
+
+https://gerrit.wikimedia.org/r/162968",1411685541,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","Change 162968 had a related patch set uploaded by Alex Monk:
+Stop ""Edit pages on double click"" from affecting VE
+
+https://gerrit.wikimedia.org/r/162968",1411676447,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""",Is this now fixed given the above being merged?,1411664311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","Change 150391 merged by Bartosz Dziewoński:
+Make mediawiki.action.view.dblClickEdit recheck preference
+
+https://gerrit.wikimedia.org/r/150391",1411663651,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","Change 150391 had a related patch set uploaded by Alex Monk:
+Add JS hook to allow extensions to prevent double click from changing to action=edit
+
+https://gerrit.wikimedia.org/r/150391",1406667468,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""",fwiw 'Enable section editing by right clicking on section titles' is active within VE,1380693722,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","For variety, I confirmed on Chrome/Linux ;-)",1380693472,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","This was reported in Mozilla 23 on Windows 8, and I reproduced it in Safari 6 on Mac OS 10.7.5, so it's probably universal.",1376935250,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Show ""Review changes"" link in the toolbar all the time, or available somehow (on hover?) rather than just through save dialog","I am editing a page and something untoward happens.  To review changes, I now have to click ""Save page"", which is sort of like a sign above a circular saw saying, ""To unplug, please saw through wall.  Thank you for your cooperation.""
+
+:p
+
+Perhaps hovering over the ""save page"" button could drop down alternative actions, such as ""save draft of changes"", ""review..."" etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376812680,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-jacp3aj4vm5u6h6b4chc,task_description,open
+"VisualEditor: Show ""Review changes"" link in the toolbar all the time, or available somehow (on hover?) rather than just through save dialog","Firstly, hover is something we avoid using in VisualEditor as it means the functionality isn't available for those using a touch interface. I don't think this is ""major"" - closer to ""minor"" - but either way it's an enhancement.
+
+Also, there's an existing bug to show what changes you've made as you enter them (e.g. by highlighting the background of the new text, like Microsoft Word's ""tracked changes"" view): bug 37931.",1376952013,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jacp3aj4vm5u6h6b4chc,task_subcomment,NA
+VisualEditor: Broken Foxlingo Firefox extension injects javascript into page,"See reported diff on fr.wp
+https://fr.wikipedia.org/w/index.php?title=Debra_Winger&action=historysubmit&diff=95823433&oldid=94552186
+
+The js is from Foxlingo but the liberal sprinkling of nowikis is from VE or Parsoid.
+
+PrimeHunter at en.wp reports that a Google search for FoxlingoJS reveals several other internet forums are suffering the same problems.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1376582220,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nfvv4eym3zcif2i7nb4d,task_description,resolved
+VisualEditor: Broken Foxlingo Firefox extension injects javascript into page,"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114004,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nfvv4eym3zcif2i7nb4d,task_subcomment,NA
+VisualEditor: Broken Foxlingo Firefox extension injects javascript into page,"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113130,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nfvv4eym3zcif2i7nb4d,task_subcomment,NA
+VisualEditor: Populate the edit summary for simple changes,"At T53903,  Elitre said:
+
+> A user at it.wp wonders: if VE could pre-populate the summary box, could it
+> also auto-add the text that was added, in case of very short additions? i.e.,
+> if someone added a parameter to a template, could it automatically detect
+> what was added and write it in the edit summary? Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**: T53903, T50274",1376506380,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-dy2dbpcxtagget43fzoa,task_description,open
+VisualEditor: Populate the edit summary for simple changes,See also T3307 & T14411,1606235062,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dy2dbpcxtagget43fzoa,task_subcomment,NA
+VisualEditor: Add help page for all keyboard shortcuts,"GMail's keyboard shortcuts help page
+
+Similar to GMail's modal when '?' is pressed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F11100}",1376487180,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_description,resolved
+VisualEditor: Add help page for all keyboard shortcuts,"Change 98517 merged by jenkins-bot:
+Keyboard shortcuts MW integration
+
+https://gerrit.wikimedia.org/r/98517",1389823722,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_subcomment,NA
+VisualEditor: Add help page for all keyboard shortcuts,"Change 107153 merged by jenkins-bot:
+Keyboard shortcuts dialog
+
+https://gerrit.wikimedia.org/r/107153",1389821946,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_subcomment,NA
+VisualEditor: Add help page for all keyboard shortcuts,"Change 107153 had a related patch set uploaded by Esanders:
+WIP Keyboard shortcuts dialog
+
+https://gerrit.wikimedia.org/r/107153",1389625063,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_subcomment,NA
+VisualEditor: Add help page for all keyboard shortcuts,"Change 98517 had a related patch set uploaded by Esanders:
+WIP Keyboard shortcuts dialog
+
+https://gerrit.wikimedia.org/r/98517",1385994018,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_subcomment,NA
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page","At https://en.wikipedia.org/w/index.php?title=Judi_Dench&curid=85432&diff=568314406&oldid=568147939 the article was top and tailed with
+<embed type=""application/x-datavault"" width=""0"" height=""0"" />
+
+Searching seems to suggest the most likely cause is the ""DataVault"" password manager browser plugin
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1376392740,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_description,resolved
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page","Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114025,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_subcomment,NA
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page","Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113124,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_subcomment,NA
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page","Did you get anything back, Derk-Jan?",1397835827,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_subcomment,NA
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page",I've send an email to their support department. Let's hope it helps.,1376470329,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_subcomment,NA
+"VisualEditor: Add support for making some templates directly ""visually editable"", as if they were tables (e.g. infoboxes)","A user at it.wp asks if, in the long term, it will be possible to edit templates directly (i.e., infoboxes), without the transclusion dialog, as if one was changing something in a table. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376386200,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-fnziglwvvwpmlxekyjvk,task_description,resolved
+"VisualEditor: Add support for making some templates directly ""visually editable"", as if they were tables (e.g. infoboxes)","
+
+*** This bug has been marked as a duplicate of bug 50182 ***",1394074105,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fnziglwvvwpmlxekyjvk,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,"<< http://en.wikipedia.org/wiki/File:GreatNurse.jpeg is a headshot of Virginia Henderson that was uploaded to Commons yesterday. VisualEditor's image feature can't find it, and won't accept file names that it doesn't believe exist. WhatamIdoing (talk) 00:17, 13 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=37578",1376382300,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-zckv7xwfgl4cxjix23f5,task_description,declined
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,*** Bug 52218 has been marked as a duplicate of this bug. ***,1383282089,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,Marking WONTFIX as this is inherently fixed by CirrusSearch and lsearchd has been end of life'd and won't be improved further.,1383013054,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,*** Bug 54777 has been marked as a duplicate of this bug. ***,1382572188,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,"The good news: CirrusSearch is updated a few seconds after a page is added, changed, or deleted.
+The bad news: it isn't ready yet!",1377001750,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,The image now comes up in the search result - this is probably a delay in the speed with which the search index is updated.,1376952277,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"At https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=568194420#I_can.27t_edit_the_references it has been proposed that it would be helpful to editors if they could edit references in the reference list, as well as where they appear inline.
+
+""As just about every object you see on a page is directly editable with the VE, of course having the reflist not editable is counter-intuitive. ""
+
+This proposal would make T54736 either unnecessary or just a ""workaround""/interim measure, depending on the timescale to implement.
+
+--------------------------
+
+#2 in the 2023 wishlist: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Citations/Allow_citations_to_be_edited_in_the_references_section_with_VisualEditor
+",1376315340,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_description,resolved
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by Novem Linguae using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/d94eddd976/w/ ]]~~",1713878505,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 950231 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Don't warn that reference list is uneditable%%%
+https://gerrit.wikimedia.org/r/950231",1692430973,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by Novem Linguae using patch(es) linked to this task:
+[[ https://patchdemo.wmflabs.org/wikis/d94eddd976/w ]]",1692417223,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 950231 had a related patch set uploaded (by Novem Linguae; author: Novem Linguae):
+%%%[mediawiki/extensions/Cite@master] Don't warn that reference list is uneditable%%%
+https://gerrit.wikimedia.org/r/950231",1692416810,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by ESanders (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/e045f72283/w/ ]]~~",1686069577,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> Citations and footnotes can now be edited directly in the references section using VisualEditor.
+
+I wouldn't describe it like this (which I think is how the wish was described). You can't edit the citations in-place, like you can a image caption, but you can launch the editing dialog for each reference from the list. Maybe:
+
+> Citation and footnote editing can now be started from the reference list when using the visual editor.
+
+The changes are in wmf10 which is on mediawiki.org (e.g. https://www.mediawiki.org/w/index.php?title=Composer&veaction=edit&section=10) and would already be on Wikipedias but for the train being blocked at the moment (T330216).
+
+There is no documentation at the moment, just the text description.",1685118600,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"For Tech News, please confirm if this is an accurate summary, below? 
+> Citations and footnotes can now be edited directly in the references section using VisualEditor. This feature request was voted #2 in the 2023 Community Wishlist Survey.
+And confirm the timing: Will it be on the deployment train next week, or live on Monday, or other/later?
+And is there a documentation page that it should link to, or just plaintext? 
+Thanks.",1685048120,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 922153 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Fix ref list click-to-edit on mobile%%%
+https://gerrit.wikimedia.org/r/922153",1684782321,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 922153 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/Cite@master] Fix ref list click-to-edit on mobile%%%
+https://gerrit.wikimedia.org/r/922153",1684776138,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 903311 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Launch reference editors from ve.ce.MWReferencesListNode%%%
+https://gerrit.wikimedia.org/r/903311",1684340605,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,This will also supersede T54736 and T183170.,1684327960,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/e045f72283/wiki/Douglas_Adams?veaction=edit",1683044836,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by ESanders (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/6247694800/w/ ]]~~",1683044705,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/6247694800/wiki/Douglas_Adams?veaction=edit",1683043472,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by ESanders (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/0f949bd767/w/ ]]~~",1683043303,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/0f949bd767/wiki/Douglas Adams?veaction=edit",1682683909,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Currently it works like that (both in Chrome and FF):
+
+| 1. before click | 2. first click | 3. second click |
+| {F36934541} | {F36934544} | {F36934546} |
+
+So first click could just change highlighted ref. That would work similar to tables and templates I guess.
+
+> but there is nothing to show after a single click (or any other interaction to be had, e.g. drag/drop).
+
+You could always show an edit button like with templates.",1680201324,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> Looks quite promising :-). One note: at the moment in the demo, after saving the changes, the script jumps to the link in the article. If it's not obvious, I think it would be good to stay where you started...
+
+Yes - this will require some more upstream changes to fix.
+
+> I assume 1st click should only select as with other templates
+
+These aren't real focusable templates, it's just a CSS hover and JS click handler. It could be changed to double click, but there is nothing to show after a single click (or any other interaction to be had, e.g. drag/drop).
+
+We have previously implemented this single click -> dialog interaction with the categories list.",1680189296,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> Looks quite promising :-). One note: at the moment in the demo, after saving the changes, the script jumps to the link in the article. If it's not obvious, I think it would be good to stay where you started...
+
+Yes - this will require some more upstream changes to fix.
+
+> I assume 1st click should only select as with other templates
+
+These aren't real focusable templates, it's just a CSS hover and JS click handler. It could be changed to double click, but there is nothing to show after a single click (or any other interaction to be had, e.g. drag/drop).",1680187061,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> WIP UI: https://patchdemo.wmflabs.org/wikis/6689bcdde2/wiki/Douglas_Adams?veaction=edit&section=26
+
+Looks quite promising :-). One note: at the moment in the demo, after saving the changes, the script jumps to the link in the article. If it's not obvious, I think it would be good to stay where you started...
+
+Hm... And I think double click is not working correctly. When I click [64] and then click [66] the edit window opens. I assume 1st click should only select as with other templates. I assume that is part of the WIP, but reporting just to be sure :)",1679967370,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,Esanders is a god,1679953834,PHID-USER-2xdbwtk2vlfbk2k6hhbh,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,WIP UI: https://patchdemo.wmflabs.org/wikis/6689bcdde2/wiki/Douglas_Adams?veaction=edit&section=26,1679937874,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 903311 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/Cite@master] Launch reference editors from ve.ce.MWReferencesListNode%%%
+https://gerrit.wikimedia.org/r/903311",1679937793,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,">>! In T54750#8727283, @Whatamidoing-WMF wrote:
+> Once it becomes possible to edit `<references />`, will editing through `{{reflist}}` require rich editing of templates?
+
+Probably not – we already have a special-case support for templates that generate a reflist. Since we already treat it like a ""real"" references list, any new features should work here as well. For example, note how in https://en.wikipedia.org/wiki/Holcocera_immaculella?veaction=edit (random article) the references are labelled like this: {F36929304} …and not like this: {F36929306} …despite being generated from a `{{Reflist}}` markup.
+
+----
+
+However, supporting references defined using `{{reflist|refs= ... }}` would require rich editing of templates. For example <https://en.wikipedia.org/wiki/Bali#cite_ref-Foley_128-0>. We already detect those and disable editing in visual mode, and presumably something similar woul happen inside this new feature: {F36929314}",1679923162,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Once it becomes possible to edit `<references />`, will editing through `{{reflist}}` require rich editing of templates?",1679850024,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,">>! In T54750#8641368, @DLynch wrote:
+>> Even if we switch to just using (2) this will mean that references are re-numbered when switching from read mode to edit mode.
+> 
+> I think we're stuck with the references renumbering in the reflist if the user edits any of them anyway, so it might be better to do it up-front and have them stay consistent throughout the entire session.
+
+It takes ~800ms to render the list on [[Barack Obama]], hence not doing it up-front. Also on he.wiki, the initial rendering is the only rendering with content.",1677604414,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,">>! In T54750#8641368, @DLynch wrote:
+>> Even if we switch to just using (2) this will mean that references are re-numbered when switching from read mode to edit mode.
+> 
+> I think we're stuck with the references renumbering in the reflist if the user edits any of them anyway, so it might be better to do it up-front and have them stay consistent throughout the entire session.
+
+It takes ~800ms to render the list on [[Barack Obama]], hence not doing it up-front.",1677604047,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> Even if we switch to just using (2) this will mean that references are re-numbered when switching from read mode to edit mode.
+
+I think we're stuck with the references renumbering in the reflist if the user edits any of them anyway, so it might be better to do it up-front and have them stay consistent throughout the entire session.",1677168505,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"I was thinking that a quick path forward would be for the reference list to offer a button that opened up a variant on the reuse dialog. In its context item would be the easiest place.
+
+{F36866803}",1677168143,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Following on from David's point, there are two ways the the reference list is rendered in the VisualEditor surface:
+1. **Using the HTML of the ref list supplied by Parsoid**: This will include all references, included those defined inside templates (e.g. infoboxes), but the numbers will not necessarily map to those in VE's data model, so mapping from these references to editable references will be hard.
+2. **Generating a reference list by iterating over references in the document model**: This will //exclude// references defined inside templates, but can easily be mapped back to the reference data in VE's data model. This list could be edited directly, or be used to launch a reference editor relatively easily.
+
+(1) is used on the first load mostly for performance reasons (implemented in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Cite/+/411101) as it's a lot quicker to use the pre-generated HTML; rebuilding the reference list can be pretty slow on large pages. It also helps on wikis where most references are defined in templates, such as he.wiki.
+
+Even if we switch to just using (2) this will mean that references are re-numbered when switching from read mode to edit mode.
+
+From a UI perspective, we will need a way of showing the reference list context, probably by not embedding it but also thinking about where a user can click to show it (as clicking the reference list contents would now let you edit the list in some way)
+
+{F36865507}
+{F36865505}",1677088390,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Copying my comment in from the other ticket, since I think it remains relevant here:
+> The major hangup on this is that it's going to expose the challenges with VE seeing references that're defined within templates. (Because of the current lack of a centralized way to edit references, this is only really visible to users from the ""reuse citation"" part of the cite dialog, where such references don't appear.) I suspect that if we accept having those ones greyed out in the list with a ""this can't be edited here"" tooltip, the rest of this should be fairly simple to do -- unless I'm not thinking of something, it's ""just"" hooking up a few bits of already-existing functionality and doing some UI work to expose them.",1676585194,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,[[https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Questions_techniques/semaine_28_2016#Impossibilt.C3.A9_d.27apporter_des_corrections_dans_les_sections_Notes_et_r.C3.A9f.C3.A9rences|New feedback from a user]] (a beginner) who wants to change a reference rom the reflist while editing with VE. ,1468426292,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,The alphabetising problem could perhaps be reduced by making the references only limitedly editable. i.e. Only individually editable in a dialog that allows for the editing of the template/parameters only.,1376323496,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Adam Cuerdon comments:
+    I'd suggest popping up a note telling the user what he or she is doing at least the first time, though. Something like ""This reference is used to document the source of text in the article. You can also edit it by clicking on the number after the text. Please make sure that you don't accidentally break documentation with your edit. Thanks for your work!""
+    We don't want to have a situation where newbies, for example, try to alphabetise the list, say.
+
+Personally, I'm not sure ""documentation"" is the right word, but otherwise it seems like a good suggestion.",1376321914,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","en.wp user JmCor reports that in Firefox on Windows 7 the shortcut ""<shift><alt>V (show the changes), which stopped working when the Visual Editor was introduced: currently, <shift><alt>V simply positions the cursor on the ""Show the changes"" button.""
+
+I can confirm this also occurs in Firefox 23 on Linux.",1376130000,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-txrorpbrj6b5ssangri4,task_description,open
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",">>! In T54701#6404011, @Sunpriat2 wrote:
+> Additionally https://www.mediawiki.org/wiki/Extension:FlaggedRevs add one more tab ""Pending changes"" which is also assigned ""v"" key. Any but unique replacement for short keys will be more convenient to activate instantly.
+
+See {T335652}
+
+>>! In T54701#8587857, @Pols12 wrote:
+> What about using`E` as accesskey for visual__**E**__ditor? From Read view, it opens wikitext editor. Pressing once again, it would switch to VisualEditor.
+
+I’d rather not change a conflicting access key to another conflicting one. The idea of @jhsoby seems better to me, although it doesn’t fix all conflicts either: filtering out `edit` and `submit` would fix this task, filtering out `history` would help fixing T26977, but there’s no way to fix T335652 with this approach, as both access keys should be available in read view.",1682937197,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","What about using`E` as accesskey for visual__**E**__ditor? From Read view, it opens wikitext editor. Pressing once again, it would switch to VisualEditor.",1675606822,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",Would it be possible to just disable the VE accesskey if the `wgAction` is `edit` or `submit`?,1649588052,PHID-USER-jqjb54lbf7psat6shbcc,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Additionally https://www.mediawiki.org/wiki/Extension:FlaggedRevs add one more tab ""Pending changes"" which is also assigned ""v"" key. Any but unique replacement for short keys will be more convenient to activate instantly.",1598121058,PHID-USER-fhwkrjgsdwt5sqn3xaq7,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Additionally ruWP has one more tab ""Pending changes"" which is also assigned ""v"" key in https://www.mediawiki.org/wiki/Extension:FlaggedRevs . Any but unique replacement for short keys will be more convenient to activate instantly.",1598120799,PHID-USER-fhwkrjgsdwt5sqn3xaq7,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Additionally ruWP has one more tab ""Pending changes"" which is also assigned ""v"" key in https://www.mediawiki.org/wiki/Extension:FlaggedRevs",1598120539,PHID-USER-fhwkrjgsdwt5sqn3xaq7,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","@AhmadF.Cheema reports problems with this in detail at https://www.mediawiki.org/wiki/Topic:Veyo7xqvss4jz8d8
+
+Also, {T156141} seems similar.",1582684702,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Yes Ed, but only when you're on the content page.",1464613495,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",alt+shift+v appears to launch VE now we have editor switching (from duplicate T130899),1459265003,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","(In reply to Lejonel from comment #4)
+> In other namespaces focus is always on ""show changes""
+> button, but the shortcut does not actually click the button. That is because
+> the HTML still contains a hidden ""visual edit"" tab with the same shortcut.
+
+This is changing (bug 64142)",1400371890,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","**dng032** wrote:
+
+Results of testing in Wikipedias about a week ago:
+
+(""Positions"" means that focus changes to the ""Show changes"" button, but does not actually show the changes)
+
+Catalan : positions
+German : shows dif
+French : positions
+Greek : positions
+English : shows dif
+Spanish : shows dif
+Hungarian : positions
+Italian : warns about not saving
+Japanese : shows dif
+Portuguese : positions
+Russian : positions
+Simple English : positions
+Chinese : shows dif
+
+Sorry for being late to react and for not retesting recently. ~~~~",1398663027,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Maybe Visual editor does not need an access key while the normal editor is used? Then one possible solution is to just remove 'v' as access key for visual editor when using the normal wiki editor.
+
+I think removing the access key there should not cause any problems for most users, for two reasons:
+
+1. Since currently ""show changes"" in wiki editor has the same acces key, neither of the access keys work as they should.
+2. In most use cases for Visual editor a user starts visual editting when they are seeing an actual page, not when they are looking at the page in the wiki editor.",1397937991,PHID-USER-axibsactcdotqkfh3mfe,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",*** Bug 52969 has been marked as a duplicate of this bug. ***,1397676026,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",Suggestions for a different shortcut for VisualEditor (or show changes) welcome.,1397675426,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","This is because the same shortcut is used for multiple actions in the same page. 
+
+For me in Firefox in namespaces with visual editor enabled pressing alt+shift+v once focuses on the ""show changes"" button, pressing again focus on ""visual edit"" tab"" and further key pressing just changes the focus between the two. In other namespaces focus is always on ""show changes"" button, but the shortcut does not actually click the button. That is because the HTML still contains a hidden ""visual edit"" tab with the same shortcut.",1377281265,PHID-USER-axibsactcdotqkfh3mfe,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","**dng032** wrote:
+
+(In reply to comment #2)
+> This is definitely related to VisualEditor - the shortcut works when
+> VisualEditor is disabled (Safari on Mac 6, Firefox 23 on Linux) and in
+> Konqueror on Linux which VE is not enabled for.
+> 
+> Changing component to VisualEditor accordingly
+
+jmCor: still Windows 7, Firefox 22.0. The component change did not fix the bug on my machine.",1376531065,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","This is definitely related to VisualEditor - the shortcut works when VisualEditor is disabled (Safari on Mac 6, Firefox 23 on Linux) and in Konqueror on Linux which VE is not enabled for.
+
+Changing component to VisualEditor accordingly",1376338921,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Adding James to the CC as this might be an artefact of VE, even though it affects the source editor.",1376130189,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+VisualEditor: Tool to set/unset text as a variable (<var>),"The <var> tag is used in many articles for variables, and there are css styling rules for it. An example article is Shading
+http://en.wikipedia.org/w/index.php?title=Shading
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376027640,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-rafmsmstj5wsl5tvqzu5,task_description,open
+VisualEditor: Tool to set/unset text as a variable (<var>),"Change 141605 merged by jenkins-bot:
+Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
+
+https://gerrit.wikimedia.org/r/141605",1404154586,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rafmsmstj5wsl5tvqzu5,task_subcomment,NA
+VisualEditor: Tool to set/unset text as a variable (<var>),"Change 141605 had a related patch set uploaded by Jforrester:
+Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
+
+https://gerrit.wikimedia.org/r/141605",1403568489,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rafmsmstj5wsl5tvqzu5,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"VisualEditor needs a tool to set/unset font colour.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375956720,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-iwu723btthb7y2jwtq7u,task_description,open
+VisualEditor: Tool to set/unset text color,{F57733391},1732295481,PHID-USER-zij24c7higfq2voiyf5y,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"Just an idea on how it may look like (a bit inspired by BlueSpice)
+
+{F41702256}
+
+""Custom color"" click will open a browser tool to select a custom color (browser tool allows to enter html code so no need to have a separate control for that)
+
+End by analogy -- for colorizing table cells:
+
+{F41702286}
+
+This one would change color for the whole cell (not just for background) -- it might be helpful when people create tables and use color as an additional layer of information. For example like in Ubuntu versions table:
+
+{F41702296}
+",1705756442,PHID-USER-37di5uhqpe6nihfhk2xf,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"Just an idea on how it may look like (a bit inspired by BlueSpice)
+
+{F41702256}
+
+""Custom color"" click will open a browser tool to select a custom color (browser tool allows to enter html code so no need to have a separate control for that)",1705755713,PHID-USER-37di5uhqpe6nihfhk2xf,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,[[ https://www.mediawiki.org/wiki/Topic:U1chcv4o6odr18kt | Here's a new request for this. ]],1509959939,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"(In reply to Elitre from comment #8)
+> Would we need to file a separate bug for background text color?
+
+Background colour isn't really a thing we want to encourage. :-) That would be a distinct piece of work; created as bug 73041.
+
+If you meant surface colouring for objects like table cells or <div>s, that's another piece of work again - bug 52180	for table cells, possibly that bug will need to be split for the wider work.
+
+If you mean the ""highlight"" / ""mark"" tool, that's yet another one - bug 64376.",1415217870,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,Would we need to file a separate bug for background text color?,1415188300,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"(Copied from
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Textcolor)
+
+Hi there :-)
+Just wondering, why there is no feature for ""coloring Text"". In know, there is a way, to use 'span', but im looking for a feature, with a WYSIWYG-Editor. Any advices, ideas?
+
+Thanks :-)",1400881060,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"(In reply to comment #5)
+> I think this will be difficult to implement well. I see two concerns:
+> 
+> * extraneous (noöp) <span>s being left behind in the wikimarkup; and
+
+This is the same as bug 37835 and is trivial for us to trim out.
+
+> * <span>s that specify the color black (bad for accessibility, etc.).
+
+Yes, though we already give people loads of tools that they can (and frequently do) abuse. Technology should serve the community and we should make tools that let them do their job, rather than dictate that they can't do something (or, in this case, that they can but it's hard).
+
+> There may be some generic ""clear formatting"" button/apparatus to be used to
+> mitigate the second point, but I'm still wary.
+
+There's already a ""clear formatting"" button provided - it would apply its magic to this too.",1383008984,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"I think this will be difficult to implement well. I see two concerns:
+
+* extraneous (noöp) <span>s being left behind in the wikimarkup; and
+* <span>s that specify the color black (bad for accessibility, etc.).
+
+There may be some generic ""clear formatting"" button/apparatus to be used to mitigate the second point, but I'm still wary.",1383008076,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"(In reply to comment #2)
+> Any pros/cons of handling this by wrapping colored text in span with
+> appropriate value of style tag?
+
+Yeah, that's what we'll want to do.
+
+We'll want to supply a generic <span> editor (which lets you edit the style=""…"" tag as raw CSS) at some point, but we'd want to do something about colour sooner (and nicer), I think.",1376123060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,*** Bug 51409 has been marked as a duplicate of this bug. ***,1376120681,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,Any pros/cons of handling this by wrapping colored text in span with appropriate value of style tag?,1376115461,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"Do we want to do this as a general colour-picker widget, possibly?",1376115172,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,"**Author:** `sandrobt.wiki`
+
+**Description:**
+Here is how to reproduce it, when trying to add a link to the page ""Maria"" on en.wiki.
+
+1) Select the add link icon and type ""maria""
+2) Select ""Maria"", which is at the end of the suggested list
+3) Press Enter or the ""<"" button
+4) Save
+
+The link is added to Mariah Carey (which was on the top of the suggested list).
+Cf. https://en.wikipedia.org/w/index.php?title=User:Sandrobt/prova&diff=prev&oldid=567641122
+
+Note that this doesn't happen if in 2) you had typed ""Maria"" (which is the exact title of the page you want to link to).
+Cf. https://en.wikipedia.org/w/index.php?title=User:Sandrobt/prova&diff=next&oldid=567641169
+
+The same problem appears in similar situations in it.wiki (for example when adding a link to ""Sega"" you need to type it exactly like that, since the first option is always SEGA) 
+
+I'm using Firefox 22.0 on Mac OS X 10.6.8.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375943460,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ga36aloq6psrxy7t2mlx,task_description,resolved
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,In fixing bug 50452 we have changed the behaviour slightly regarding this - not sure if it's still necessary to keep this open?,1378766470,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ga36aloq6psrxy7t2mlx,task_subcomment,NA
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,"This happens in every case where:
+* the input text case INsensitively matches an entry >= 2nd in the list, AND
+* the input text case sensitively does NOT match the title of any in the list, AND
+* the user selects the case insensitive match
+
+It doesn't matter whether the text was entered in the link dialog or selected on the editing surface.",1378424550,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ga36aloq6psrxy7t2mlx,task_subcomment,NA
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,"**sandrobt.wiki** wrote:
+
+Ok, note taken. Though, a bug that inserts the wrong link in a pretty large variety of situation, despite selecting the correct one and without giving any clue of having done so, is a pretty seriuos problem and has probably alredy produced quite a lot of wrong wikilinks.",1375945790,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ga36aloq6psrxy7t2mlx,task_subcomment,NA
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,"[resetting severity, see http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity ]",1375945480,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ga36aloq6psrxy7t2mlx,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"if the template does not contain explicit ""templatedata"", the API call should return auto-generated ""templatedata"" structure, distilled from the template itself.
+
+
+it's trivial to do - basically parse the template, extract parameter names (including order based, aka 1,2,3), and return ""default"" templatedata where every param is of type string, without any special attributes (default, required, etc.)
+
+this 15-line enhancement will make VE suddenly useful for templates, without detracting anything from current functionality.
+
+we did this in hewiki with ""template param wizard"" (the equivalent of VE template editor, for the old wikitext editor), and it enhanced the wizard's functionality tenfold.
+
+regretfully i can't submit a patch - hopefully someone else will be able to do so.
+
+peace.
+
+--------------------------
+
+**See Also**:
+{T54135} / https://bugzilla.wikimedia.org/show_bug.cgi?id=52135",1375804800,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_description,duplicate
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"Change 257684 abandoned by Eranroz:
+Guess parameters when templatedata is missing
+
+[[https://gerrit.wikimedia.org/r/257684]]",1483655816,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"Change 257684 had a related patch set uploaded (by Eranroz):
+Guess parameters when templatedata is missing
+
+[[https://gerrit.wikimedia.org/r/257684]]
+",1449605074,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,">>! In T54581#1271501, @Krinkle wrote:
+> .... Possibly with a warning outputted alongside the object. Similar to how MediaWiki's query api communicates things like ""warnings"", ""normalized"", and ""badrevids"".
+
+maybe so, but maybe it should not be ""warning"". 
+a new field can be added to the record returned by the API, e.g. ""synthetic"" or somesuch, to indicate tempaltedata was generated synthetically, and the template itself does not contain ""templatedata"" tag.
+
+peace.
+
+",1431449493,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"The TemplateData editor now supports scanning the template source code and inferring a list of parameter names to bootstrap the documentation editor.
+
+We can use the same logic server-side to provide a basic TemplateData object for templates lacking it. Possibly with a warning outputted alongside the object. Similar to how MediaWiki's query api communicates things like ""warnings"", ""normalized"", and ""badrevids"".",1431058046,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"for many many simple templates, just getting the list of parameter names is enough for even moderately experienced editors. 
+the editor may even be well familiar with the template, but she does not necessarily remembers the exact name (case sensitive) of every parameters.
+
+
+regarding your 2nd use case: are you aware that this tool (prepopulate templatedata editor) is already written and working?
+
+written by wmf volunteer (intern? gsoc student? not sure), [[mw:. User:Mooeypoo]], and works on hewiki for quite some time. 
+this tool already includes ""import parameters from template"" button - last time i checked, it was working quite well. 
+
+see [[mw:MediaWiki:Gadget-templatedata-core.js]], function ""importtemplateparams()""
+
+if your comment meant to describe it rather than suggesting to build it, i apologize for the confusion.
+
+bottom line: having templatedata is good, but when it does not exist, just seeing the list of parameters (including unpopulated) is hugely perferrable to not seeing them.
+
+peace.",1400794505,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"So this ""guess template data"" parser would be useful in two cases:
+
+* Consumers of TemplateData (e.g. VisualEditor)
+
+They could pass a parameter to the API of TemplateData to trigger this parser as fallback. The generated data would presumably be flagged in some way to allow consumers to identify them as such.
+
+* TemplateDate editor
+
+A button to prefill the template data (e.g. use the default data as a start and edit from there). This should not be misused to populate <templatedata> tags on a bunch of pages, this is only useful if users provide data beyond what is inferred (the inferred data is unlikely to ever be satisfactory as at best it can provide which parameters exist and maybe which are optional).",1400616454,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"(In reply to comment #4)
+> i did it long ago, and published it on
+> [[en:Wikipedia:WikiProject_User_scripts/Scripts#Scripts]]. the script page on
+> enwiki is [[en:User:קיפודנחש/TemplateParamWizard]].
+
+See also
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_103#Template_Parameter_Wizard
+(mentioned on bug 39598 comment 1)
+
+> -- ""Choices"": this allows the designer to declare that a certain parameter
+> has
+> a fixed set of ""legal"" values. very useful when the template uses a parameter
+> as an input for {{#switch:
+
+Bug 51375.
+
+> -- ""Depends on"": only expose this field if some other field is not empty.
+
+Bug 50407.",1383413267,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"The status was recently changed to ""Assigned"", but the ""Assigned to"" field was left as ""Nobody"". 
+is Mr. (or Ms.) ""Nobody"" a new developer on the team?
+
+peace.",1377790501,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"Thanks so much for the nice words, but... 
+This entry is about templatedata, not templatewizard.
+
+the information i brought above relating to TW was meant as ""what templatedata can learn from TW"" - if you'd like to discuss TW and its use on enwiki, it should be discussed on enwiki, not here.
+
+peace.",1375977047,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"Thank you so much. It works beautifully. I couldn't test it in Hebrew WP because it is situated in the edit toolbar which was disabled by me because I feel more comfortable to type everything with my keyboard. But anyway, the gadget's performance is smooth even while editing large article like ""United States"" in English WP. The only few issues I can think of right now after tried it a bit are, I don't feel the toolbar is the proper place for the gadget icon. It deserves a more visible location in the edit page. The other thing I hope to improve is that I need to select the whole markups of existing template from ""{{"" to ""}}"" in order to edit it in the Wizard. For large infobox template which has lot of parameters filled, it could be little bit inefficient to trigger. I suggest the end of the selection of the markup extends to the first vertical bar near the template name, so only selecting like this ""{{templatename|"", works the same way as ""{{templatename|foo|bar}}"".",1375976428,PHID-USER-xnvlg7y5phtzugavv6wj,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"i did it long ago, and published it on [[en:Wikipedia:WikiProject_User_scripts/Scripts#Scripts]]. the script page on enwiki is [[en:User:קיפודנחש/TemplateParamWizard]]. the script source itself is practically identical to the hewiki one, except maybe some recent enhancement(s) to the hewiki script (for instance, by default, the wizard does not leave empty parameters on the page, but some users asked for this as an option, so now the hewiki script learned to support on more option).
+
+
+the wizard uses a similar construct to ""templatedata"", but instead of having this information on the template page, it uses a subpage with a fixed name (in enwiki, this fixed name is ""Parameters"", so for Template:Foo, the templatedata equivalent will be in Template:Foo/Parameters).
+
+when the subpage does not exist, the wizard extracts the list of parameter names from the template itself, with some fixed attributes (for instance, in this case it assumes that each parameter is ""multiline"")
+
+i believe there are several people on enwiki who actually use this (at least there were) - you probably want to ask them about their experience (something like
+
+https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=TemplateParamWizard+intitle%3Ajs&fulltext=Search&ns2=1&redirs=1&profile=advanced
+
+
+
+the wizard supports some attributes that, to the best of my knowledge, ""templatedata""/VE do not support yet, which i think would be good ideas:
+
+-- ""Extended"": this allows the designer to designate some fields as ""secondary"", which means they are not visible when the form opens. if there is at least one ""Extended"" parameter, the form will grow a new checkbox ""Show all fields"", which allows the user to show/hide the ""Extended"" fields.
+
+-- ""Choices"": this allows the designer to declare that a certain parameter has a fixed set of ""legal"" values. very useful when the template uses a parameter as an input for {{#switch:
+
+-- ""Depends on"": only expose this field if some other field is not empty. very useful for templates with many repetitions (e.g., [[en:Template:Track listing]]: you make ""title4"" depend on ""title3"", and then ""note4"", ""writer4"", ""lyrics4"", ""music4"", ""extra4"", ""length4"", and finally ""title5"" all depend on ""title4""). without this feature, the wizard is much less useful for templates of this type.
+
+
+peace.",1375969237,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,Hi kipod. I can't understand Hebrew language and I have some trouble to test it in Hebrew Wikipedia. Can you translate the gadget to English Wikipedia under your own userspace? Thank you.,1375948802,PHID-USER-xnvlg7y5phtzugavv6wj,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"https://he.wikipedia.org/wiki/Mediawiki:Gadget-TemplateParamWizard.js
+
+the function is called buildParamsRaw() (""data"" is the raw template page).
+
+i cannot guarantee that it always works flawlessly, but the wizard works on hewiki  for a while now (more than a year), and i did not get any bug reports (i did have some bug reports for previous versions).
+
+i think it is possible to intentionally create a legal template that will give bad results there: specifically, this function does not take ""nowiki"" and ""noinclude"" tags into account.
+
+OTOH, it uses only 9 out of the budget of 15, so you have 6 lines to augment those shortcomings...
+
+more seriously: i assumed the codebase already have non-negligible amount of logic that can be used to distill the parameter list of a template. 
+
+(full disclosure: i too did not believe it can be done without tons of code - Eran Roz showed me the light)",1375942161,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"I very much look forward to a link to the part of the hewiki wizard that implements this logic. I very much doubt it can be done (or done well) in 15 lines of code, and I very much doubt it's trivial or even easy to do it well.",1375931029,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+VisualEditor: Allow replacing file by changing the file name,"To replace a file it is currently neccessary to delete the file from the page and insert the new one.
+
+It would be easier to replace the filename only. This avoids to add caption and file options again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375804620,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-atfd2medq2qoyjgabdcf,task_description,resolved
+VisualEditor: Allow replacing file by changing the file name,"
+
+*** This bug has been marked as a duplicate of bug 51033 ***",1402608867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-atfd2medq2qoyjgabdcf,task_subcomment,NA
+VisualEditor: Allow replacing file by changing the file name,"I'm not sure there's a great way to merge the experience of adding a media item and the one for editing one, but this seems a reasonable extension.",1383281015,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-atfd2medq2qoyjgabdcf,task_subcomment,NA
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","When VisEd is activated from a section edit link, the focus of the display normally stays on that section.  However, if the user activates from a section edit link while on a diff link (has to be diff of current version), the focus shifts to the top of the page as if the whole page edit link had been pressed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375747320,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-cvljbzolxfeydqmcoo2c,task_description,resolved
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","Change 131415 merged by jenkins-bot:
+Generate PHP VE edit section with correct parameter, vesection
+
+https://gerrit.wikimedia.org/r/131415",1399312738,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cvljbzolxfeydqmcoo2c,task_subcomment,NA
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","Thanks, Matt!",1399312671,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cvljbzolxfeydqmcoo2c,task_subcomment,NA
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","Change 131415 had a related patch set uploaded by Mattflaschen:
+Generate PHP VE edit section with correct parameter, vesection
+
+https://gerrit.wikimedia.org/r/131415",1399259020,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cvljbzolxfeydqmcoo2c,task_subcomment,NA
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","This is just a special case.  The general issue is that VE does not navigate to the section when a section edit is initiated with a fresh page load (it does when it uses the AJAX switch to editing without a page load).  For example, https://en.wikipedia.org/w/index.php?title=Earth&veaction=edit&section=6 .  It appears in this case because VE (there is a comment to this effect) uses a new page load to start section editing when it's showing the latest diff (to deal with another issue).
+
+This applies any time the user is sent directly to edit a section via VE.  For the Growth team's current project, we will allow the user to click ""Sign up and edit"" (including for sections).  This works using the normal signup page, with the returnto and returntoquery parameters.  That means we can not do an AJAX switch.
+
+Besides login/signup, there are other (albeit less common) reasons you might want to link directly to a section edit URL.",1399258028,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-cvljbzolxfeydqmcoo2c,task_subcomment,NA
+"When a link goes to a redirect, show the final destination as a tooltip (title attribute)","Wikis use lots of shortcuts on the talk pages, and it can be quite frustrating for the uninitiated to figure out what WP:MOS, WP:N etc. mean, especially when several are used at once.
+
+Having to click on the link to see that its about the 'Manual of Style' or 'Notability' would be unnecessary, if the same information was available in the tooltip when hovering the link.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1375731240,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-btbym6mlgax3tzzbkzr4,task_description,open
+"When a link goes to a redirect, show the final destination as a tooltip (title attribute)","I was thinking when reading.
+
+Now that you mention it, it would probably be useful for VisualEditor as well, but I think that can be its own bug.
+
+(updating the summary to clarify)",1375791803,PHID-USER-pwsgofaoir7tnszvfzqi,PHID-TASK-btbym6mlgax3tzzbkzr4,task_subcomment,NA
+"When a link goes to a redirect, show the final destination as a tooltip (title attribute)","In which exact situation should the tooltip be shown? 
+Is this about reading? Editing?",1375790948,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-btbym6mlgax3tzzbkzr4,task_subcomment,NA
+VisualEditor: Copying of styles to dialog frame is dirty,"Screenshot where it works (VE copied it from <style>)
+
+When VE copies styles into the frame, in the case of copying from a friendly <link> tag (e.g. one that is readable, we inspect it and copy the contents over, as opposed to a foreign one we have to fetch again from the iframe).
+
+In that case, the css we manage to extract from the remote <link> appears to be dirty and neither strictly or effectively roundtrips. Both the actual css it copied and the effective values are different.
+
+For example, in the case of ""background: none;""  it gets dirtied to ""background-image: none; background-position: initial initial; background-repeat: initial initial;"". Which means it no longer overrides background-color.
+
+Now, in some browsers background: none (old IE iirc) is indeed interpreted as the above, and it would be reasonable behaviour of it expands it to what it interprets it as.
+
+However in the case of Chrome, it does't just normalise but actually gives us values that don't match. See attached screenshots.
+
+The side effects (e.g. broken styles) are currently (e.g. MediaWiki context) most visible in debug mode because then almost everything is loaded through <link> and as such subject to this bug. In production mode most things are loaded by ResourceLoader and thus evaluated inline. However it is a bug both in production as well, it is just a matter of time before we find random broken styles.
+
+
+- Figure out if we can get the contents without normalisation
+
+- Perhaps fallback indefinitely to always using <link href> for remote stylesheets, thus costing a few extra http requests inside the dialog, but that might be the only way we can for now.
+
+- Figure out how many things are affected and in which browsers. Maybe we can get it fixed upstream reasonably fast (these seem to be genuine bugs in the browser).
+
+- If there's only a few properties subject to dirty normalisation, we could consider changing our stylesheets to avoid those properties. E.g. instead of background: none; use background-color: none; (something less ambiguous, and probably correct in this case, though it is a bug still because it works in Chrome normally, but not after roundtripping to an iframe).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F11259}",1375487160,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f3cdxehcze5c6igk2koe,task_description,resolved
+VisualEditor: Copying of styles to dialog frame is dirty,Effectively fixed for dialogs by expedient of not doing this any more…,1415062594,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f3cdxehcze5c6igk2koe,task_subcomment,NA
+VisualEditor: Copying of styles to dialog frame is dirty,"Has the bug:
+- Chrome 29 beta
+- Chrome 30 canary
+- Safari 6.0.5
+
+Does not have the bug:
+- Firefox 22 stable
+- Firefox Aurora 24.0a2",1375487416,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f3cdxehcze5c6igk2koe,task_subcomment,NA
+VisualEditor: Copying of styles to dialog frame is dirty,"Created attachment 13055
+Screenshot where it is dirty and broken (VE copied it from <link>)
+
+**Attached**: {F11260}",1375487204,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-f3cdxehcze5c6igk2koe,task_subcomment,NA
+VisualEditor: Media selector should suggest media used on other language versions of the page,"en.wp user Wouterstomp suggests that the media selector should also suggest images that are used on other language versions of the article, not just based on the page title.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T53031}",1375461120,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dv44kcirtbdcglt6wfni,task_description,open
+VisualEditor: Media selector should suggest media used on other language versions of the page,"This could be very useful, but would need us to move more of the media item usage data out of local wikis and into a central repository (probably Wikidata), which has been discussed a few times but I don't know how soon it might get done, sorry.",1375487609,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dv44kcirtbdcglt6wfni,task_subcomment,NA
+VisualEditor: Media settings dialog should show a preview of the media item,"Wouterstomp at en.wp has requested that the media settings dialog shows a tumbnail/preview of the image so you can refer to it while writing the caption.
+
+I would add to this that ctrl+click on this preview image should load the media description page in another tab/window.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375459860,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-zpdzyjmznhwuqu7y5wnu,task_description,open
+VisualEditor: Media settings dialog should show a preview of the media item,"(In reply to comment #2)
+> I don't think the original commenter had particularly thought of that, as the
+> only thing you can currently do is write a caption. The idea being that you
+> can refer back to the image when writing it. This will be even more useful
+> I guess when you can used this dialog to write alt text.
+> 
+> My gut feeling is that a live preview would be nice but not essential.
+> Possibly implement a static preview and then see if anybody asks for it to be
+> made into a live preview. Assuming a live view is more than trivially harder
+> to implement than a static one.
+
+I believe that the hard stuff here will be in showing anything at all (and, particularly, anything that looks like how it will render in the page). Will check about live-updating, though.",1375783156,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zpdzyjmznhwuqu7y5wnu,task_subcomment,NA
+VisualEditor: Media settings dialog should show a preview of the media item,"I don't think the original commenter had particularly thought of that, as the only thing you can currently do is write a caption. The idea being that you can refer back to the image when writing it. This will be even more useful I guess when you can used this dialog to write alt text.
+
+My gut feeling is that a live preview would be nice but not essential. Possibly implement a static preview and then see if anybody asks for it to be made into a live preview. Assuming a live view is more than trivially harder to implement than a static one.",1375486837,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-zpdzyjmznhwuqu7y5wnu,task_subcomment,NA
+VisualEditor: Media settings dialog should show a preview of the media item,"Is this meant to be a preview of the media item as it will render in the page (i.e., a live-updated view of the configuration options from the dialog)?",1375482852,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zpdzyjmznhwuqu7y5wnu,task_subcomment,NA
+VisualEditor: Disallow (discourage?) placing references inside section headers,"<<This is not really a VE bug (it is possible in the standard editing mode as well), but it is something that happens more often in VE, and that perhaps can be automatically disabled in VE as well; inserting references inside section headers. This is never needed or wanted (it is ugly, and the thing that needs to be referenced should be in the text of the section, not only in the title anyway). Example (spam, but the principle applies): http://en.wikipedia.org/w/index.php?title=Miniature_pig&diff=prev&oldid=566703074 . Fram (talk) 07:31, 2 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375436160,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-beeof7d2r6t7gnezbj7a,task_description,open
+"VisualEditor: Always show dialog icons for nodes (transclusion, media, reference, etc.)","A user at en.wp asks:
+""Why hide the puzzle and content icons until mouse-over? In general, if a function is active, it should be always shown - no idea, what hiding tries to achieve here.""
+
+Personally I think this could be very confusing for links, but it should be ok for templates and media.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375434180,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nbkquo5siurqmbtxqe3i,task_description,declined
+"VisualEditor: Always show dialog icons for nodes (transclusion, media, reference, etc.)","On reflexion, I'm going to mark this as WONTFIX per my reasoning in comment 1 - this would massively dominate the interface on most real-world pages and make it unusable.",1393632819,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nbkquo5siurqmbtxqe3i,task_subcomment,NA
+"VisualEditor: Always show dialog icons for nodes (transclusion, media, reference, etc.)","yeah, the only way round that I can think of at the moment would be to have some sort of toggle between the current behaviour (default) and a display all mode. That would be useful for identifying at a glance where things are on a page, particularly with locating any invisible templates. It's not something I personally see as being of huge value, but I'm not everybody.",1375510577,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-nbkquo5siurqmbtxqe3i,task_subcomment,NA
+"VisualEditor: Always show dialog icons for nodes (transclusion, media, reference, etc.)","Templates and images aren't necessarily very big (think for example about the 20px-wide images that decorate some lists, either directly or as tables).
+
+When a node is smaller than a threshold, it displays the node icon as a pop-out (like an inspector menu); if we showed them all the time it could massively crowd-out the text of the page.
+
+Also, I worry that it would obstruct part of the template so you wouldn't know whilst editing exactly what was going to appear for users (if the menu icon was unhelpfully placed).",1375490038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nbkquo5siurqmbtxqe3i,task_subcomment,NA
+"VisualEditor: If an added category is a redirect to another, suggest adding the target instead","If category:A is redirected to category:B 
+when user adds category:A it should switch it automatically to category:B like mediawiki:gadget-Hotcat.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375383960,PHID-USER-dswbdv7ibhsefllcqarz,PHID-TASK-ykcis27ybwjtiim3musu,task_description,resolved
+"VisualEditor: If an added category is a redirect to another, suggest adding the target instead","Change 118218 merged by jenkins-bot:
+Follow redirects in the category widgets
+
+https://gerrit.wikimedia.org/r/118218",1397702683,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ykcis27ybwjtiim3musu,task_subcomment,NA
+"VisualEditor: If an added category is a redirect to another, suggest adding the target instead","Change 118218 had a related patch set uploaded by Alex Monk:
+Follow redirects in the category widgets
+
+https://gerrit.wikimedia.org/r/118218",1394582184,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ykcis27ybwjtiim3musu,task_subcomment,NA
+"VisualEditor: If an added category is a redirect to another, suggest adding the target instead","So the redirect comes up as a suggestion, but when we add it, the redirect is resolved and the target added?",1394563520,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ykcis27ybwjtiim3musu,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","The sentence ""This page was last modified on … "" (message lastmodifiedat) is not updated after an edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48560",1375374540,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_description,resolved
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved",Verified in production.,1416427771,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Verified in test2 and betalabs. The timestamp for ""This page was last modified on 5 November 2014, at 23:54."" seems to reflect accurately editing&saving events.",1415231839,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Change 170264 merged by jenkins-bot:
+Update ""page was last modified on date, at time"" footer line when saving
+
+https://gerrit.wikimedia.org/r/170264",1414733101,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Change 170264 had a related patch set uploaded by Alex Monk:
+Update ""page was last modified on date, at time"" footer line when saving
+
+https://gerrit.wikimedia.org/r/170264",1414715367,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved",(... I had assumed this was for the LastModified extension without checking the message name.),1414707773,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Change 170184 abandoned by Alex Monk:
+Expose getLastModifiedText function
+
+Reason:
+oops
+
+https://gerrit.wikimedia.org/r/170184",1414707699,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Change 170184 had a related patch set uploaded by Alex Monk:
+Expose getLastModifiedText function
+
+https://gerrit.wikimedia.org/r/170184",1414707232,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Same problem as bug 48560 (the page isn't re-painted when the edit is saved, just the contents <div>, and this sits outside that).",1375473428,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","The cog to the side of the ""Languages"" sidebar section does, in fact, not let you change anything about that section.
+
+### Concerns
+
+* The ULS ""cog"" is visually associated with the ""Languages"" sidebar section, despite being unrelated, other than (confusingly) relating to the word ""Language"" in some way. The placement of this cog should be reconsidered.
+
+* The ""Language"" sidebar does not currently have a way to quickly edit its contents. (Unlike HotCat for categories). It can be changed by performing a full page edit (via the main ""Edit"" button on top). Alternatively, the links can (sometimes) be edited using the ""Edit links"" placed at the end of the link, which relates to Wikidata.
+
+### Background
+
+There are three things related here:
+
+1. Edit language links on current page: This is part of the content for the current page, and can be edited by clicking ""Edit"" and changing them in VisualEditor (under ""Page Settings  > Languages""), or by using the source editor.
+
+2. Edit language links associated with current page's Wikidata item: These are stored on Wikidata and can be edited by using the ""Edit links"" button at the bottom of ""Languages"" sidebar section.
+
+{F11931}
+
+3. User interface language: This is the language used for the interface of the software, names of input fields, sections, buttons, etc. This can be changed in three ways currently:
+
+| Preferences | ""Preferences"" among the personal tools. Available on all pages, all wikis. leading to Special:Preferences.  {F14222596} {F14222603}
+|--
+| ULS (personal)| The ULS link (language name) among the person tools. Available on all pages, but only certain wikis have it enabled. Leading to a ULS dialog dedicated to language selection.  {F14222782} {F14222792}
+|--
+| ULS (cog)| The ULS cog, aside the ""Languages"" section in the sidebar. Available only on content pages, all wikis. Leads to a different ULS dialog, one that also has other features, but among them language selection. {F11929} {F14223046}
+|--
+
+
+### Original task description
+
+>>! this-does-not-edit-languages wrote:
+>
+> languages should be editable out of a link besides languages. see attachment for a wheel which opens something else, on top of languages. clicking below drops you into wikidata. to really edit the languages one has to go to page settings! very confusing.
+>
+>
+> **Attached**: {F11929}",1375354680,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-zatiesduw4yvsu33o45q,task_description,open
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Little comment 1: Since the task was filed in 2013, another element was added to most pages near the languages in the sidebar: ""//X// more"", opening the compact language links panel. I am adding the #uls-compactlinks tag here, because even though this project didn't exist when the bug was filed, it is totally relevant in the context. I am also adding the #wikidata tag, because it has a lot to do with it.
+
+Little comment 2: The following two tasks at least partially overlap with this one:
+# {T53355}
+# {T53431}
+
+----
+
+So, we now have two or three elements near the languages list:
+# The cog, near the ""Languages"" title:
+-- Coming from the ULS extension. Used for choosing UI language, and configuring webfonts and keyboards. It was put there back in 2012 when the first version of ULS was developed. Of course, the association between the ""Languages"" title, familiar to most wiki editors (and possibly to many readers) was a factor in choosing this location.
+# The Wikidata link at the bottom:
+-- It has the text ""Add links"" when the page is not linked to versions in other languages. Clicking it opens a dialog for adding the links without leaving the page.
+-- It has the text ""Edit links"" when the page is linked to versions in other languages. Clicking it goes to the item page in Wikidata.
+# The Compact Language Links ""''X'' more"" button:
+-- Appears only on pages with 9 links or more, and only if the Compact Language Links preference is enabled. (It was in beta for a long time, but now it is default in Wikipedia in all languages, and in most other Wikimedia projects.)
+-- Clicking it opens a ULS panel with all the languages in which the page is available.
+
+----
+
+This is not ideal.
+
+This is not ideal for a lot of reasons:
+# Generally, three elements near the language the list //feel// like a bit too much.
+# The cog is at the top, but the things that it includes are //probably// needed by fewer people. I'm saying ""probably"", because I don't have the numbers, but we can try to obtain them. Fonts and keyboards configuration is important in some languages, but completely unnecessary in a lot of others (at least in the current implementation; I have a lot of ideas for redoing webfonts support, but they are far from being implemented, and they are way beyond the scope of this task). One thing I'm sure of is the the other two elements are needed by users in wikis in all languages, and the cog—only in some.
+# The language selector in ""Display settings"" under the cog includes all the languages, but it only selects the UI language. Even though the panel explicitly says what does it do, I suspect that some people—possibly a lot—select the UI language instead of the article language. I've seen it happening to a lot of people in workshops for new editors.
+# As a follow up to the previous point: Changing the UI language is not currently available to logged-out users. The panel says so, and some people may even think that they can only read an article in another language if they log in. It may sound crazy, but it may be true.
+# The title is not always actually ""Languages"". It is ""Languages"" in some wikis, but in others it is ""In other languages"", ""This page in other languages"", or something else.
+# ""Add links"" and ""Edit links"" have the same location, but different text, and completely different behavior. I suspect that a lot of editors will appreciate //editing// wikidata sitelinks (i.e. languages) in a dialog similar to the one that is used for initial linking, thus making the functionalities similar. I've been hearing comments like this from a lot of users in a lot of languages for years.
+# This is more of a guess than the previous point, but I further suspect that a lot of editors will appreciate a link to the Wikidata item page in a convenient location, possibly near the language list. ""Edit links"" is such a link already, but that's not what its title says. There is also a ""Wikidata item"" link buried elsewhere in the sidebar, which does largely the same thing. As an editor, it's one of the very few sidebar links that I actually use, although I might be very different from a lot of other people. This requires proper research.
+# The ""''X'' more"" button appears in some cases, but not always.
+# The language selector (ULS) and the language editor (WikidataClient's dialog) are related in their functionality, but they have a completely different interface design. It would be nice to bring their appearance closer to each other.
+
+----
+
+That's a lot of different issues. There's material here for a lot of different tasks and subtasks. Fixing them is desirable. It won't happen overnight, and it will require //proper// design work, and not just editors' or developers' intuition. It will probably require collaboration between Wikidata developers and WMF's Language team developers.
+
+But yes, it's about time to start resolving it.
+
+To @Krinkle's question—no, there's no proper roadmap at the moment. This very long comment is, hopefully, the first attempt to think of such a roadmap.",1521568306,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Little comment 1: Since the task was filed in 2013, another element was added to most pages near the languages in the sidebar: ""//X// more"", opening the compact language links panel. I am adding the #uls-compactlinks tag here, because even though this project didn't exist when the bug was filed, it is totally relevant in the context. I am also adding the #wikidata tag, because it has a lot to do with it.
+
+Little comment 2: The following two tasks at least partially overlap with this one:
+# {T53355}
+# {T53431}
+
+----
+
+So, we now have two or three elements near the languages list:
+# The cog, near the ""Languages"" title:
+-- Coming from the ULS extension. Used for choosing UI language, and configuring webfonts and keyboards. It was put there back in 2012 when the first version of ULS was developed. Of course, the association between the ""Languages"" title, familiar to most wiki editors (and possibly to many readers) was a factor in choosing this location.
+# The Wikidata link at the bottom:
+-- It has the text ""Add links"" when the page is not linked to versions in other languages. Clicking it opens a dialog for adding the links without leaving the page.
+-- It has the text ""Edit links"" when the page is linked to versions in other languages. Clicking it goes to the item page in Wikidata.
+# The Compact Language Links ""''X'' more"" button:
+-- Appears only on pages with 9 links or more, and only if the Compact Language Links preference is enabled. (It was in beta for a long time, but now it is default in Wikipedia in all languages, and in most other Wikimedia projects.)
+-- Clicking it opens a ULS panel with all the languages in which the page is available.
+
+----
+
+This is not ideal.
+
+This is not ideal for a lot of reasons:
+# Generally, three elements near the language the list //feel// like a bit too much.
+# The cog is at the top, but the things that it includes are //probably// needed by fewer people. I'm saying ""probably"", because I don't have the numbers, but we can try to obtain them. Fonts and keyboards configuration is important in some languages, but completely unnecessary in a lot of others (at least in the current implementation; I have a lot of ideas for redoing webfonts support, but they are far from being implemented, and they are way beyond the scope of this task). One thing I'm sure of is the the other two elements are needed by users in wikis in all languages, and the cog—only in some.
+# The language selector in ""Display settings"" under the cog includes all the languages, but it only selects the UI language. Even though the panel explicitly says what does it do, I suspect that some people—possibly a lot—select the UI language instead of the article language. I've seen it happening to a lot of people in workshops for new editors.
+# As a follow up to the previous point: Changing the UI language is not currently available to logged-out users. The panel says so, and some people may even think that they can only read an article in another language if they log in. It may sound crazy, but it may be true.
+# The title is not always actually ""Languages"". It is ""Languages"" in some wikis, but in others it is ""In other languages"", ""This page in other languages"", or something else.
+# ""Add links"" and ""Edit links"" have the same location, but different text, and completely different behavior. I suspect that a lot of editors will appreciate //editing// wikidata sitelinks (i.e. languages) in a dialog similar to the one that is used for initial linking, thus making the functionalities similar. I've been hearing comments like this from a lot of users in a lot of languages for years.
+# This is more of a guess than the previous point, but I further suspect that a lot of editors will appreciate a link to the Wikidata item page in a convenient location, possibly near the language list. ""Edit links"" is such a link already, but that's not what its title says. There is also a ""Wikidata item"" link buried elsewhere in the sidebar, which does largely the same thing. As an editor, it's one of the very few sidebar links that I actually use, although I might be very different from a lot of other people. This requires proper research.
+# The ""''X'' more"" button appears in some cases, but not always.
+# The language selector (ULS) and the language editor (WikidataClient's dialog) are related in their functionality, but they have a completely different interface design. It would be nice to bring their appearance closer to each other.
+
+----
+
+That's a lot of different issues. There's material here for a lot of different tasks and subtasks. Fixing them is desirable. It won't happen overnight, and it will require //proper// design work, and not just editors' or developers' intuition.
+
+But yes, it's about time to start resolving it.
+
+To @Krinkle's question—no, there's no proper roadmap at the moment. This very long comment is, hopefully, the first attempt to think of such a roadmap.",1521567896,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links",">>! In T54383#4015867, @Krinkle wrote:
+> The main thing I'm unsure about is why the cog is placed near the ""Languages"" sidebar section. Especially given we already have two other interfaces for editing the user language. Do I understand correctly that the intention is to (eventually) migrate all wikis away from the ""cog"" icon in favour of the ULS dialog trigger from the personal tools? The dialogs have different designs, but seem similar in purpose. And I can't actually find a wiki/page combination that shows both, which leads me to believe it is a configuration option, of which the personal-tools placement seems preferable as it avoids confusion with the purpose of the ""Language links"" sidebar section.
+> 
+> Can someone confirm this? And/or point to a roadmap of some sort related to this?
+
+The different ways in which language selection is provided are the result of trying to keep a single area related to language where the default selection is about content (plus backwards compatibility). I'll try to elaborate and add some context:
+
+**Our goal and what we learned about the user needs**
+
+We want to provide the ability to select both, the content language and the UI language. During our user research we identified that many users don't have a very clear distinction of both concepts (or don't make a careful evaluation on which part a language selector they find is going to change). The most common expectation was to change the content (or both, content + UI). That is, if a user finds a selector with a list of languages and selects Italian, the user expects the content of the page to become in Italian, and it would be unexpected to see that only a few menus (the UI) change to Italian instead.
+
+Based on the above, we tried to follow the guideline of presenting the option to change the UI language in a less prominent way than the content language selection. That is providing a default selector for changing the content language, and less prominent advanced options in case you wanted to specifically change the UI only.
+
+**Why there are two different solutions**
+
+We had two different kinds of wikis. Some wikis are multilingual, like Commons. Other wikis are a group of individual monolingual wikis linking to one another, like Wikipedia in each language. For multilingual wikis we presented a language selector on the personal toolbar on top. The selector let's you pick the content language and provides advanced options at the bottom to change other aspects such as the UI language. This was working well, and having the language selection on top was easy to discover.
+
+However, monolingual wikis had already an established way to change the content language (technically, to jump to the equivalent page in a wiki of a different language) using the interlanguage links. At that time, we decided to keep the interlanguage links to avoid pushing for too much change at once (although we may want to revisit that in the future). With the constraint of keeping the interlanguage links where they were, placing the UI selector on top was problematic because (a) it created two separate areas for language selection, and (b) the most prominent one (on top) was not about content but UI. So we decided to have a single area dedicated to languages, keeping interlanguage links where they were as the most prominent language selection, and provide advanced options in a less prominent way as advanced settings.
+",1521215850,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","I've updated the task description with some background information.
+
+The main thing I'm unsure about is why the cog is placed near the ""Languages"" sidebar section. Especially given we already have two other interfaces for editing the user language. Do I understand correctly that the intention is to (eventually) migrate all wikis away from the ""cog"" icon in favour of the ULS dialog trigger from the personal tools? The dialogs have different designs, but seem similar in purpose. And I can't actually find a wiki/page combination that shows both, which leads me to believe it is a configuration option, of which the personal-tools placement seems preferable as it avoids confusion with the purpose of the ""Language links"" sidebar section.
+
+Can someone confirm this? And/or point to a roadmap of some sort related to this?",1519942423,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","This is generally a valid feature request, and this is something that ULS and VE developers should consider some time in the not-so-far future.",1395398464,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Sorry, I meant to move this to ULS (as it's mostly a ULS design question) when it was filed some weeks ago.",1377534431,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","(In reply to comment #11)
+> my english is not good enough to understand the ""incidentally, ...""
+> paragraph. what does that mean in terms of coding?
+
+We may write more code to let you use bits of VisualEditor (like the dialogs) outside of the editor.",1375485860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","my english is not good enough to understand the ""incidentally, ..."" paragraph. what does that mean in terms of coding?",1375482575,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","(In reply to comment #8)
+> oh, you are right, it is just code to parse and display it in page settings
+> *blush*, sorry for confusion. coming back to the original suggestion: why not
+> improve the hacky gadget in the frame of the VE project, instead of including
+> it in the VE?
+
+The hacky gadget, as I recall:
+
+* Doesn't let you set non-Wikidata language links (as needed on non-Wikipedia wikis)
+* Doesn't let you set local language links to over-ride the ones from Wikidata (as needed on Wikipedia sometimes e.g. for [[Maggie Simpson]])
+* Doesn't let you change/remove other languages' links without making you leave the site and going to Wikidata to use the tools there
+* Doesn't let you create new Wikidata entities for the page
+* Is based on local code that may differ between wikis (making VisualEditor work differently in different places)
+
+We agreed with the Wikidata team a few months ago that replacing this was a worthwhile thing to do.
+
+Incidentally, on the wider point, we're very keen to start moving away from editing being a monolithic block of actions that have to take place together, and instead letting users ""curate"" quickly - whether that's changing categories, language links, workflow action items (like ""needs wikifying"" or ""nominate for deletion"") or other tasks - without having to enter the editor.
+
+HOWEVER, that's not really the point of this bug, is it?",1375480011,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","""about the cog not letting you change settings of other languages"" refers to the small wheel symbol in the side bar close to ""Languages"". 
+It is created by the MediaWiki extension ""UniversalLanguageSelector"" (ULS) so that would be the codebase to change for that aspect, not VE's code.",1375466130,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","oh, you are right, it is just code to parse and display it in page settings *blush*, sorry for confusion. coming back to the original suggestion: why not improve the hacky gadget in the frame of the VE project, instead of including it in the VE?
+
+the ""about the cog not letting you change settings of other languages"" and ""ULS"" i did not understand. what would you mean by this?",1375446015,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","(In reply to comment #6)
+> _remove_ the code to edit language links from the already complicated VE.
+
+There is no code to edit language links in VisualEditor. What are you talking about?",1375401899,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","james, bug 52105 is the exact opposite of the suggestion here. the visual editor team should, imo, leave the hacky gadget, or improve the hacky gadget with something which is not called hacky any more.
+
+and, _remove_ the code to edit language links from the already complicated VE.",1375397942,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Being able to edit language links is bug 52105 (specifically, for Wikidata ones). This would replace the current hacky gadget.
+
+The other part of this bug (about the cog not letting you change settings of other languages) would be an issue with ULS, not VisualEditor, I think?",1375384179,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","> i see, you do not know this beast as well
+
+I admit I don't know every single option of software running on Wikimedia servers by heart, plus sometimes bug reporters paraphrase things. That's why I appreciate good steps to reproduce to understand the problems that you're facing.
+
+Now that I can reproduce I agree that it's slightly confusing. 
+However the bug summary does not describe the problem but one potential solution, hence changing the bug summary to: 
+""VE > Page Settings > Languages"" functionality expected where ULS' ""Language Settings"" cog is
+
+> and all people are happier.
+
+On a general note: If you have not run a survey in your neighborhood and beyond (as other neighborhoods might have different needs and expectations), generalizations feel like http://en.wikipedia.org/wiki/Wikipedia:WEASEL and might diminish the impact & interest in your suggestions how to improve Wikimedia, which would be a pity.",1375383652,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","wikidata at the bottom
+
+attached page settings at the right, with languages. and wikidata at the bottom. and i see, you do not know this beast as well and do _not_ expect the language code there. just remove this language link code and all people are happier.
+
+**Attached**: {F11931}",1375364945,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","page settings at the right
+
+**Attached**: {F11930}",1375364802,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Why would you want to edit languages, in order to understand the problem that you report here? To add links to articles with the same topic in other languages? That is exactly what Wikidata is for.
+
+With regard to the wheel ""which opens something else"", this is part of your language and input text settings. 
+See http://www.mediawiki.org/wiki/File:ULS_Usability_testing_summary.pdf for the Usability tests that led to this design.
+
+> to really edit the languages one has to go to page settings!
+
+I cannot find anything called ""Page Settings"" on for example http://en.wikipedia.org/wiki/Berlin . Please provide exact steps to reproduce.",1375355187,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+VisualEditor: pasting with middle-click in X-Windows doesn't work when automatic scrolling is enabled,"On Unix systems with an X-Windows desktop middle-clicking usually pastes text that was last selected with the mouse.
+
+It doesn't work in the VisualEditor in Firefox if automatic scrolling is enabled in the preferences.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375295280,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-lusbxefwae6sj2xokbvm,task_description,open
+VisualEditor: pasting with middle-click in X-Windows doesn't work when automatic scrolling is enabled,How on Earth does Firefox's automatic scrolling feature interact with its pasting feature? Gah. :-),1375299597,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lusbxefwae6sj2xokbvm,task_subcomment,NA
+VisualEditor: Selecting with Shift-arrow selects the heading after a list item,"Go to https://www.mediawiki.org/wiki/User:Amire80/be-bullet-heading?veaction=edit, which contains the wikitext:
+```
+* list item 1
+* list item 2
+* list item 3
+
+==Heading==
+paragraph text
+```
+Press Shift-↓ (down arrow) three times.
+
+The first time, the first list item is selected.
+The second time, the second list item is selected.
+The third time, the third list item AND the heading are selected.
+
+Selecting the heading should require a forth press of Shift-↓.",1375294800,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-tddypvggbabpq3kxu4cc,task_description,declined
+VisualEditor: Selecting with Shift-arrow selects the heading after a list item,"Pressing shift+down moves your cursor down visually in the browser. This is just how native selection works in the browser (for example, in read mode, select the first 'l' in 'list item 1', then press shift down, and the same thing happens).
+
+Without completing re-implenting our own version of cursor movement, we couldn't fix this even if we wanted to.",1701961099,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-tddypvggbabpq3kxu4cc,task_subcomment,NA
+VisualEditor: Selecting with Shift-arrow selects the heading after a list item,Verified in Firefox 41.0a2 on OS X.,1437770551,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-tddypvggbabpq3kxu4cc,task_subcomment,NA
+VisualEditor: Display of several float:left-ed tables side-by-side inserts slugs that break them up,"Screenshot of the bug as provided by user
+
+Depending on the display format, VE fails to get the display of several tables properly in line. See also attachment; test page here:
+
+http://de.wikipedia.org/wiki/Benutzer:Stefan_Knauf/Dateidurchsuchungsprogramm.cpp
+
+Report:
+
+http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121040382#VisualEditor_ist_nicht_WYSIWYG
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11761}",1375227780,PHID-USER-wswkm7jrcwes3tc7o34k,PHID-TASK-wgyduwg7w4wdsktqalds,task_description,open
+VisualEditor: Display of several float:left-ed tables side-by-side inserts slugs that break them up,"Ugh, this is because we put block slugs between these tables, and the tables are floated left.",1375228215,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-wgyduwg7w4wdsktqalds,task_subcomment,NA
+VisualEditor: Reject (or at least loudly warn about) edits that contain pawns or other obvious placeholders,"Rather than simply quietly inserting pawns and other placeholder characters into the page text, VisualEditor should do a sanity-check pre-save and either outright reject or loudly warn about edits that will insert such characters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375118160,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-sfwbwm73nkcseqpbk5if,task_description,declined
+VisualEditor: Reject (or at least loudly warn about) edits that contain pawns or other obvious placeholders,"The problem of inserting pawns and such is ancient history now, so building a system to detect them is not a good use of time.",1508930263,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-sfwbwm73nkcseqpbk5if,task_subcomment,NA
+VisualEditor: Reject (or at least loudly warn about) edits that contain pawns or other obvious placeholders,"I suggest piggybacking on the existing sanity check code: display the ""your edit may be corrupted"" warning in the save dialog and tag the edit with visualeditor-check.",1375118282,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-sfwbwm73nkcseqpbk5if,task_subcomment,NA
+Allow users to customise keyboard shortcuts,"What it says on the in. Like in most desktop applications, it should be possible for users to customise the keyboard shortcuts to their liking. Including in VisualEditor and source editor.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1374931980,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-hsvzb36avth2iqas7oad,task_description,open
+Allow users to customise keyboard shortcuts,Removed VE reference from the title because it's simply not part of MediaWiki core.,1374938852,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-hsvzb36avth2iqas7oad,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**Author:** `KilliondudeWP`
+
+**Description:**
+The edit summary box currently uses a textarea input box. Current functionality has the return key starting a new line in the textarea, but upon save the edit summary is truncated into one line in the page history (line breaks are turned into spaces). Thus, the textarea box is misleading.
+
+A more sane option would be to use a single line text input box, where the enter key processes the edit rather than starts a new line.
+
+See T40042 and T42034, and specifically T42034#467450.
+",1374899820,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y2wr4truqmwwemxh72yk,task_description,declined
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1465077, @matmarex wrote:
+> even worse in VE than in wikitext editor because the input field is narrower.
+
+Putting a (wider) summary box in the main editor UI would solve {T52961} as well.",1437402576,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Such input box will still not wrap the typed text, which is terrible enough by itself for users, and even worse in VE than in wikitext editor because the input field is narrower.",1437401367,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,How about making it an input box and just set `padding-bottom` to make it //feel// like a textarea?,1437399200,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"As discussed on the patch, assuming that we want the text to wrap, this is **not actually possible to do** for most languages, and an English-only half-solution would be inappropriate. Browsers are really letting us down here.
+
+As I understand, there are two reasons why we would want this, which have separate tasks:
+* {T106325}
+* {T50274}
+
+We should focus on resolving these, which should be possible regardless of the underlying text field used.",1437391823,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Change 212795 abandoned by Bartosz Dziewoński:
+[WIP] TextInputWidget: Allow wrapped singleline inputs
+
+Reason:
+This is not going to be compatible with different text input methods.
+
+[[https://gerrit.wikimedia.org/r/212795]]",1437391169,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"The idea may or may not actually be a good one. It's definitely interesting. The gist is that we dynamically swap the <input type=text> for a <textarea>. It has some funny behavior but sort of works.
+
+The patch above makes it impossible to type a newline into the field, and should let it display the automatic browser's autocompletion when it is single-line. Ed mentioned that it can break with IMEs if you're typing a word and it changes from input to textarea in the middle of it.",1432313088,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Change 212795 had a related patch set uploaded (by Bartosz Dziewoński):
+Allow wrapped singleline inputs
+
+[[https://gerrit.wikimedia.org/r/212795]]
+",1432312920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"I think I have a pretty good idea on how to implement this, I'll try to do some pre-hackathon hacking on it today.",1432288471,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1302510, @Whatamidoing-WMF wrote:
+> I care whether it **behaves like** the wikitext edit summary in terms of interacting with my web browser.  I want to type a complex edit summary once, and have that edit summary automagically re-appear whenever I start typing it on my next edit.  If you can give me that useful function while making the box a perfect square, then I'm satisfied.  I need the function, not the appearance. 
+
+Yup. IIUC, changing the textarea to a text input line, will solve {T50274} (possibly that should be listed as blocked by this?)
+
+Re: keeping it visually highlighted - do note that the textarea has the bright blue border now, when the field is active, which it is automatically when opened, (but not shown in matmarex's screenshot above), and I think that could be sufficient. 
+
+
+",1432250744,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"I've said this in several places, but I repeat it here:  I don't care what size or shape the edit summary box is on my computer screen.  
+
+I care whether it **behaves like** the wikitext edit summary in terms of interacting with my web browser.  I want to type a complex edit summary once, and have that edit summary automagically re-appear whenever I start typing it on my next edit.  If you can give me that useful function while making the box a perfect square, then I'm satisfied.  I need the function, not the appearance. ",1432241088,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"The last thing I heard is that making the edit summaries any bigger required redesigning //the database// (yes, //that// database), not merely the user interface.",1432240831,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1302437, @awight wrote:
+> Okay, I understand where that's coming from.  On the other hand, sometimes it's really helpful to have a brief summary sentence, then a few more paragraphs of relevant things which fall into the ""why"" category and are therefore more appropriate in a summary or the Talk page than in the main article.
+
+Well, edit summaries are limited to around 200 characters. Changing that limit would involve redesigning the UI, which is doable, but is a fairly big undertaking that should only be done if there's some specific need to change this. I don't think there's a need for that.
+
+> How would you suggest we broaden this discussion?  I'm not sure this is the right place, and donno if wikitech-l is the best mailing list, cos we should involve editors.
+
+I expect that the product folks in the VisualEditor Team will take our input then make an appropriate decision. :-)",1432238326,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Okay, I understand where that's coming from.  On the other hand, sometimes it's really helpful to have a brief summary sentence, then a few more paragraphs of relevant things which fall into the ""why"" category and are therefore more appropriate in a summary or the Talk page than in the main article.
+
+How would you suggest we broaden this discussion?  I'm not sure this is the right place, and donno if wikitech-l is the best mailing list, cos we should involve editors.",1432237819,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1302396, @awight wrote:
+> @Deskana, I'm curious why you say that,
+>> We want users to be fairly brief with their edit summaries
+
+Edit summaries are intended to be quite brief summaries of the edits. I don't think encouraging users to write a lot of text in there is a good idea.",1432236841,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"@Deskana, I'm curious why you say that,
+> We want users to be fairly brief with their edit summaries",1432236748,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1296269, @matmarex wrote:
+> For comparison. The last one looks positively //tiny//.  We'd need to come up with something smart if we were to make it single-line.
+
+That's not necessarily a bad thing. We want users to be fairly brief with their edit summaries, and bigger boxes are more likely to encourage them to write more. Smaller boxes encourage the opposite.
+
+That said, we'd have to be sure that the user's attention isn't drawn to the wrong place; in the last screenshot, the box is so small that the user's attention may not immediately be drawn to that text box. You could try try making the font in the box slightly larger, and slightly increasing the width of the dialogue to compensate.
+
+",1432068967,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"For comparison. The last one looks positively //tiny//.  We'd need to come up with something smart if we were to make it single-line.
+
+| Current edit summary field | {F166629,size=full} |
+| -- |
+| Wikitext editor edit summary field | {F166627,size=full} |
+| -- |
+| Proposed edit summary field (single-line) | {F166624,size=full} |
+| -- |
+",1432045895,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Just merged in very similar task arguing that enter should submit the summary field. (On a similar note, I've proposed using meta + enter as a general shortcut for submitting dialogs in T98105.)
+
+Good points in the comments:
+
+@matmarex:
+>This could be confusing since the summary text field looks like a multiline text input, possibly causing users to accidentally submit with incomplete summaries (which can't be corrected afterwards).
+>
+>It could be interesting to try something else – maybe pressing Enter twice to submit the form, maybe Ctrl+Enter? We should probably do some research.
+>
+>...
+>
+>* Facebook: comments to posts on the timeline are normally single-line (pressing Enter in the text field submits a comment), but you can make them multi-line by pressing Ctrl+Enter or Shift+Enter (or by copy-pasting text with newlines). Pressing Enter submits the comment even if it is multi-line.
+>* My bank has these ""wrapped single-line"" inputs in some fields and pressing Enter always does nothing in them. Accidentally submitting a form could potentially have dire consequences there.
+
+@Deskana:
+>For the advanced user, the current approach where enter adds new lines is counterintuitive. The advanced user not only knows that edit summaries cannot be multi-line, but it also feels wrong because they're also used to enter submitting their edit.
+>
+>For the new user, the current approach feels misleading, as you're giving the user an expectation that edit summaries can be multi-lined when in fact they cannot. This user has no expectations about enter submitting the edit, so probably doesn't care too much about that.
+>
+>I think the best approach would be to make the edit summary box single-line, and make enter submit the edit.",1431978382,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"(In reply to Spinningspark from comment #10)
+
+However, the input box should be large enough to accomodate the maximum permitted length of edit summary, even if that means using two lines.",1411393509,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"(In reply to Amir E. Aharoni from comment #9)
+> Is it possible to meet in the middle: To show it as a textarea, but to allow
+> saving using Enter/Return? And maybe provide autocomplete?
+
+That will lead to another problem: newbies will accidentally save before they have finished entering the summary.
+
+The fact is, the edit summary *is not* a text area and should not be displayed as such.  It can only ever be a single line of text.  That is what should be shown.  Enter should initiate a save.",1411391908,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Is it possible to meet in the middle: To show it as a textarea, but to allow saving using Enter/Return? And maybe provide autocomplete?",1409247587,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Bug 48274 seems to cover the same ground, and was one of the first things I found problematic with VE: those of us who do a lot of regular work on many different articles usually have a set of standardised edit summaries which can convey a lot of useful information, with links, to help other editors. The autocomplete facility provided by browsers for a one-line input box worked well.",1375521561,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**JohnCD67** wrote:
+
+Killiondude's comment 1 is an significant usability point - for repetitive tasks it is very helpful that the browser pops up a list of suggestions to click on, which is context-sensitive and based on previous usage. I did not realise how helpful that was until with VE I found myself having to type the full edit summary each time.",1375440006,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"(In reply to comment #5)
+> > Sure, but collapsing the box down to a single line would de-emphasise the
+> > edit summary, however, and turn it back into ""a mysterious text box"" that
+> > uses ""feel free to skip"".
+> 
+> Why would it?
+> 
+> It's still hidden behind a modal dialog. I will wager that editors still feel
+> forced to fill it in simply because it is there.
+
+The numbers went up when we switched from inputbox to textarea. Expecting them not to fall when we reverse that change seems unlikely to me.",1375423283,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**sk8er_97456** wrote:
+
+> Sure, but collapsing the box down to a single line would de-emphasise the
+> edit
+> summary, however, and turn it back into ""a mysterious text box"" that uses
+> ""feel
+> free to skip"".
+
+Why would it?
+
+It's still hidden behind a modal dialog. I will wager that editors still feel forced to fill it in simply because it is there.",1375418475,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"(In reply to comment #3)
+> I seriously doubt that that is the reason you have a higher incidence of edit
+> summaries. What you did in parallel to making it a textarea was that you hid
+> the ""Save page"" final submit button behind a dialog that prominently presents
+> the box for an edit summary. Users no longer feel free to skip a mysterious
+> text box and click ""Save page"" right away, the look and feel of the modal
+> dialog forces them to consider filling it out in full before proceeding.
+> That's why you're getting more edit summaries.
+
+Sure, but collapsing the box down to a single line would de-emphasise the edit summary, however, and turn it back into ""a mysterious text box"" that uses ""feel free to skip"".",1375415740,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**sk8er_97456** wrote:
+
+I seriously doubt that that is the reason you have a higher incidence of edit summaries. What you did in parallel to making it a textarea was that you hid the ""Save page"" final submit button behind a dialog that prominently presents the box for an edit summary. Users no longer feel free to skip a mysterious text box and click ""Save page"" right away, the look and feel of the modal dialog forces them to consider filling it out in full before proceeding. That's why you're getting more edit summaries.",1375414773,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"By making the summary a textarea rather than an inputbox we've seen a radically-greater number of editors (especially, anonymous and new editors) entering edit summaries for their edits. I think we should think very seriously about the impact of such a change before just making it.",1375388426,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**KilliondudeWP** wrote:
+
+Another issue brought up with having a text area box is that previously entered summaries are not suggested. Most browsers suggest prior terms entered into text input boxes, this allowing editors to choose from their (frequently) used summaries.
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Improvements&oldid=566754323#Autofill_edit_summary",1375384096,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","Steps to reproduce
+1. Create a page with a linefeed
+2. Edit it in VE
+3. Copy the block containing the ↵
+4. In a new VE window, paste
+
+Expected results:
+VE smartly removes the ↵
+
+Actual results:
+The ↵ is pasted into the second VE as a literal character
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53828",1374849360,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-bmgl5fdektu6pj27wpm4,task_description,resolved
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","Just want to capture that in many cases the user could want the ↵ to mean ""break this line and create a new line""
+
+I don't think this is 100% of the time, but enough that we should think about it.",1378923579,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-bmgl5fdektu6pj27wpm4,task_subcomment,NA
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","Change 83222 merged by jenkins-bot:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",1378923311,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bmgl5fdektu6pj27wpm4,task_subcomment,NA
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","Change 83222 had a related patch set uploaded by Esanders:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",1378548144,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bmgl5fdektu6pj27wpm4,task_subcomment,NA
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","References are also pasted as [1], etc",1374849508,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-bmgl5fdektu6pj27wpm4,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"As perhaps a simpler case of copy and paste from 'external sources', pasting richtext that copied from the same wiki should work seamlessly.
+
+In many cases, the 'html' already has the metadata needed. e.g. the image, or text-with-wikilinks, even the categories, should be paste-able
+
+https://en.wikipedia.org/wiki/Pelham_Parkway
+
+With a tiny bit of additional html attributes, the navbox templates ({{Parkways in New York City}} & {{Bronx streets}}) could be copied as they are self-contained units - no parameter were used to invoke them.
+
+Again with a bit of markup, the Infobox pasted into a VE session, but only the shell transclusion could set up - the parameters would need to be entered by the user in the VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51547",1374842820,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jg5w64dq46rdbpyabqp7,task_description,open
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,This should be largely addressed as we transition to #parsoid-read-views.,1700062714,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"NB Firefox throws away RDFa properties when copying, so this won't be possible without JavaScript intercepting copy events, as it stands:
+
+https://jsfiddle.net/L9q81y02/2/",1535732717,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"NB Firefox throws away RDFa properties when copying, so this won't be possible without JavaScript intercepting copy events, as it stands.",1390316714,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,*** Bug 52787 has been marked as a duplicate of this bug. ***,1383280378,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"(In reply to comment #2)
+> This is a separate problem James.  This is about copying from a non-VE wiki
+> page on the same wiki.  That is very different from copying from another VE,
+> or another website.  As I eluded to in my initial enhancement request,
+> additional HTML needs to be emitted into the read version of the wiki page in
+> order that a VE could pick up the name of the template to use when pasting it
+> into a VE.
+
+Oh, sorry, I missed your comment about adding RDFa/etc. hinting to highlight what DOM elements are what.
+
+""Tiny"" is not remotely the correct word - this will require us to replace the entire read DOM with the same output as Parsoid provides VisualEditor, which is vaguely scheduled to be considered for research/analysis in about a year's time (this is so far off in the distance there isn't even a bug for it yet). Recasting.",1374881208,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"This is a separate problem James.  This is about copying from a non-VE wiki page on the same wiki.  That is very different from copying from another VE, or another website.  As I eluded to in my initial enhancement request, additional HTML needs to be emitted into the read version of the wiki page in order that a VE could pick up the name of the template to use when pasting it into a VE.",1374880786,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"This is not simpler. This is the same. The problem is not taking in rich text (from any source), it's inserting it sanely into VisualEditor's ContentEditable surface, sadly. Merging.
+
+*** This bug has been marked as a duplicate of bug 33105 ***",1374880349,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+"VisualEditor: Paste in Firefox with privacy option enabled behaves strangely: rich text appears, but in reality paste has failed","The paste operation on Firefox behaves strangely when dom.event.clipboardevents.enabled = false
+(which is exposed in the UI of several extensions)
+
+When disabled, rich text appears to have been pasted into VE, with links in blue (but the link isnt editable), but in reality the paste has failed to change the underlying data in VE.
+
+If the user starts typing, the pasted richtext disappears.
+
+If the user saves immediately after the paste, the richtext remains visible in the VE, but the save only adds blank lines instead.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374841620,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-yluaahg4ge2upl35udiq,task_description,open
+"VisualEditor: Paste in Firefox with privacy option enabled behaves strangely: rich text appears, but in reality paste has failed",[[ https://pl.wikipedia.org/w/index.php?title=Wikipedia:Kawiarenka/Kwestie_techniczne&diff=prev&oldid=74782151 | September 2024 report from pl.wikipedia ]] - need to confirm about:config settings of the reporter,1727568654,PHID-USER-qduasitr62ffvc5eiivd,PHID-TASK-yluaahg4ge2upl35udiq,task_subcomment,NA
+VisualEditor: Transclusion dialog should also display the actual parameter name as well as the display name,"When you start a new transclusion dialog for a template which has the templatedata specified it shows a list of the parameters with the label on the left and the actual parameters in grey on the right. This is good for power users who know the parameters. 
+
+When you choose a parameter which has a value specified you can see the label, but you can't see what the actual parameter is. This would be quite handy and could use the same grey style as in the list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374838980,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-i65x4dklyvkvelmyu7om,task_description,open
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"Wikipedias in some languages, among them Polish, Russian, Ukrainian and Hebrew, have a gadget that shows a list of frequent edit summaries near the edit summary field in source editing mode.
+
+Here are the source samples:
+
+Polish: https://pl.wikipedia.org/wiki/MediaWiki:Gadget-edit-summaries.js
+Hebrew: https://he.wikipedia.org/wiki/MediaWiki:Gadget-Summarieslist.js
+
+Many users in the Hebrew Wikipedia complained about the lack of this gadget in the VisualEditor. This could be an enhancement request, but given that for several languages it's an integral part of the editing interface for these languages, it's a regression for them.
+
+Adding this as a feature should be very easy, given that it's quite simple and the existing gadgets' code can be reused. Localization and customization for every project can be done on a MediaWiki page with a list of summaries for that project.
+
+--------------------------
+**See Also**:
+{T50274}",1374828360,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-odseemabxyqbdz2dgloa,task_description,resolved
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,Task was to update gadgets which is done. Please re-file if you think this functionality needs to be upstreamed.,1561117513,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"The relevant gadgets currently seem to support VE (And so does the english wikipedia version of this gadget). Do we keep this open as a core VE improvement ? 
+
+I'd think that considering the experiences with iOS mobile App canned edit summaries some thorough UX analysis and creative thinking would have to go into this to make such a thing useful for both inexperienced and seasoned editors honestly.",1496828368,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"Yes, and FWIW, the he.wikipedia veteran editors welcomed this change, done by @eranroz (thanks, Eran).
+
+It's available in the mobile apps in all languages, and I wonder - can @deskana provide any info about whether the mobile editors use it and like it? And what do the recent changes patrolers in different languages think about it?",1420985690,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"Both of the gadgets linked have been extended to also work with VisualEditor, by the way.",1420984413,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"(In reply to comment #1)
+> I'm reminded of bug 48274.
+
+It's somewhat related, but definitely not the same. What I'm talking about are very frequent summaries in a project. Every project community decides what it needs, but usually it's common generic stuff like ""spelling"", ""adding links"", ""wikification"", ""removing unreferenced content"", ""copyediting"" etc.",1374829478,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,I'm reminded of bug 48274.,1374828543,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","Steps to reproduce:
+1. Open VE on a sandbox
+2. In a different window, delete the sandbox
+3. In the VE window, change the text in the sandbox and save the page
+
+Expected results:
+Something similar to the SE, which asks ""
+User xxx (talk) deleted this article after you started editing it, with a reason of:
+
+    blah 
+
+Please confirm that you really want to recreate this article."" with a checkbox
+
+Actual results:
+Backend error message is displayed, and there is no option to ignore this error.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374805260,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-pyseattqnc7yj362nndp,task_description,resolved
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","Change 169976 merged by jenkins-bot:
+Catch pagedeleted errors and give the ability to re-create the page
+
+[[https://gerrit.wikimedia.org/r/169976]]",1416944580,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pyseattqnc7yj362nndp,task_subcomment,NA
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","Change 169976 had a related patch set uploaded by Alex Monk:
+Catch pagedeleted errors and give the ability to re-create the page
+
+https://gerrit.wikimedia.org/r/169976",1414630160,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pyseattqnc7yj362nndp,task_subcomment,NA
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","I currently get this error in Parsoid:
+
+TypeError: Cannot read property 'length' of null
+    at Object.result.parse (eval at <anonymous> (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.tokenizer.peg.js:97:44), <anonymous>:18347:34)
+    at PegTokenizer.tokenizeAsync (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.tokenizer.peg.js:135:25)
+    at PegTokenizer._processText (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.tokenizer.peg.js:124:8)
+    at PegTokenizer.process (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.tokenizer.peg.js:38:7)
+    at ParserPipeline.process (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.parser.js:439:21)
+    at ParserPipeline.processToplevelDoc (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.parser.js:455:21)
+    at SSP.parseOriginalSource (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.SelectiveSerializer.js:143:17)
+    at TemplateRequest.<anonymous> (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.Util.js:1266:3)
+    at TemplateRequest.g (events.js:180:16)
+    at Object.processSome [as _onImmediate] (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.ApiRequest.js:123:17)
+worker 11363 died (1), restarting.",1397917595,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-pyseattqnc7yj362nndp,task_subcomment,NA
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","The response is now:
+
+| Error: The page has been deleted since you fetched its timestamp
+
+I guess we should inherit this message, however. Changing to an enhancement.",1385395630,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pyseattqnc7yj362nndp,task_subcomment,NA
+VisualEditor: Make ve.ce.MWBlockImageNode.prototype.getCssClass nicer,"It should look at the attributes directly rather than take them as parameters. We should move the folding of all sorts of types into 'default' or 'none' in there. We should set the CSS class in one place rather than two different ones.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374792420,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-onafhjfu75ziw55sv6d6,task_description,open
+Merge Poem extension into MediaWiki core,"The Poem extension has almost as much extension setup as it has functionality. Bundling it with MediaWiki is silly, it should simply be merged into core.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement
+**Whiteboard**: migrate Poem extension bugs to core post-resolution",1374788640,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bdnotllyeea37ihjkmr3,task_description,open
+Merge Poem extension into MediaWiki core,"For clarity I have split the work plan in my previous comment to a new task, {T194651}.",1526299289,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"We had an IRC discussion in #mediawiki-parsoid about this. 
+
+* We'll get rid of the special handling of `:`, but preserve the existing appearance by using CSS. So end users won't notice a change, unless they have custom CSS rules with selectors like `div.poem > span` or `.mw-poem-indented`, which will not work anymore. This will address T123216.
+* The compact attribute is going to be killed. (We didn't actually discuss this, but everyone appears to agree that it is useless.) This will address T16910.
+* We'll try to solve the T124144 <hr> issue as well. Existing patches for that task will be insufficient to deal with the problem when <pre> is used. 
+* Once those things are done, @ssastry suggested to follow this plan:
+** get feedback from Wikisource
+** do visual diffs if required as part of that
+** merge the patch https://gerrit.wikimedia.org/r/#/c/328887/
+** evaluate if there is anything we want to deprecate via linter (e.g. intra-line whitespace)
+** reevaluate whether we want to merge this into core as <lines> as the original proposal stood
+
+This is arguably the wrong task for this work, since we are not actually merging the extension (yet) - the current flurry of work is a precursor to that.",1522959725,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"So, looking at https://gerrit.wikimedia.org/r/328887 it seems that, if that patch is merged, the primary difference between `<poem>` and `<pre>` handling in core is:
+* `<poem>` generates an empty span with `margin-left:1em` for wikitext like `: foo`.  But I think we could probably tweak the CSS so that the rendering of the standard parser output for `:foo` (aka, `<dl><dd>foo</dd></dl>` is the same.
+* `<poem>` respects leading whitespace, but compresses intraline whitespace.  This is currently being done by a combination of CSS and manually substituting leading whitespace with `&nbsp;`.  In order to clean this up, the easiest thing would be to stop compressing intraline whitespace.  We'd either do that for a new `<lines>` tag (and merge the `<lines>` semantics into core) or else do a wikilint type project to simply removing inadvertent intraline whitespace.  Depending on how prevalent it is, the latter might not be too hard.
+
+What else am I missing?",1522871580,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Also, it would be nice if we could have some more attention on https://gerrit.wikimedia.org/r/330896/. This is an obscure bug in the PHP parser that is only triggered by certain wikitext content generated by a tag extension (it can't be triggered by user-entered wikitext), and it blocks the re-implementation of `<poem>` using the `<pre>` tag.",1521288301,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I think https://gerrit.wikimedia.org/r/106861 is probably still relevant today (or if there is no appetite for merging into core, then the changes can be rebased on top of the extension, as seen in https://gerrit.wikimedia.org/r/#/c/328887/). I seem to recall that it fixes a number of bugs in the Poem implementation, not all of which are tracked in Phabricator. Although this was 4 years ago, so I might be wrong.",1521293089,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I think https://gerrit.wikimedia.org/r/106861 is probably still relevant today (or if there is no appetite for merging into core, then the changes can be rebased on top of the extension). I seem to recall that it fixes a number of bugs in the Poem implementation, not all of which are tracked in Phabricator. Although this was 4 years ago, so I might be wrong.",1521288123,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"This zombie bug has lurched to life again because of {T188478}.
+
+Any chance we can come up with a sane semantics for `<poem>`/`<lines>` so that we aren't plunged into eternal darkness by trying to make a Parsoid extension bug-for-bug compatible with `<poem>`?  We have fancy new linting tools that (in theory) could help auto-migrate uses of `<poem>` if we can agree on a better replacement.",1521232200,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 abandoned by TTO:
+Merge Poem extension into core
+
+Reason:
+I don't intend to pursue this anymore. However, reviewers here might be interested in https://gerrit.wikimedia.org/r/328887 and https://gerrit.wikimedia.org/r/328888 .
+
+[[https://gerrit.wikimedia.org/r/106861]]",1482494427,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I'm not really interested in this anymore. Instead, I might try getting the automatic line numbering functionality requested in T15644 into the Poem extension, which would make the Poem extension a bit bigger and more worthwhile.",1482474275,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,">>! In T54061#1672245, @cscott wrote:
+> In particular, I'm interested in hearing more from @GOIII about:
+>> . . .
+> Lets get a spec for `<lines>` written down in such a way that we can discuss issues like this:
+
+> * Should the tags be forced to be on their own lines?  (The current implementation doesn't force this.)
+Depends. Will the new tag mimic the standard behavior of a <DIV> attribute's //display:block// or the behavior of a <P> attribute's //display:block// under the wiki mark-up/parser/parsoid? 
+
+The whole damnblasted issue comes back first and formost to the auto insertion of an opening <P> tag at every seemingly first detected line start. That's the current quirk; whether or not content placement starts after //or// under the poem tag. In other terms using the basic underlying html when it comes to the <poem> tag, it's ....
+
+<poem>First line
+<p>second line</br>
+third line</br>
+last line</p></poem>
+
+... versus ...
+
+<poem>
+<p>First line</br>
+second line</br>
+third line</br>
+last line</p>
+</poem>
+
+The 2nd version is //closer// to reflecting normal/expected behavior based on the ""substitution"" of <poem> for <div> but its still not quite right because of the attributes <p> automatically follows as defined elsewhere by some number of .css files 'handed down' by mediawiki by default. The optimal ""underlying"" html should behave as a true DIV tag (//display:block//) should and there should be no <P> element or behavior anywhere in play here.
+
+Taking the same two possible placements of content start (immediately after or immediately under) as above but substituting <div> for <poem>, the ""underlying"" html should go something like this ... 
+
+<div class=poem>First line</br>
+second line</br>
+third line</br>
+last line</br></div>
+
+... versus ...
+
+<div class=poem>
+First line</br>
+second line</br>
+third line</br>
+last line</br>
+</div>
+
+Obviously, consensus still needs to be reached whether or not there should be a </br> at the end of the 'last line' found immediately before the closing tag, but regardless of //after// or //under// placement by the contributor, both render the same. The takeaway here should be __killing the presence and/or behavior of that mark-up induced opening <p> tag for any of this to truly be worthwhile imho__.
+ 
+> * Can you write `<lines class=""foo"">`?  Does this override the default ""poem"" and ""mw-lines"" classes, or add to them?  Is this sufficient for the different styling @GOIII describes?  (The current implementation doesn't allow extra classes.)
+Imho, manually adding a class= statement should add or enhance the default. 
+
+> * What should the Parsoid representation be?
+Not sure what exactly you're looking for here
+
+> * What if somebody writes `<pre class=""poem mw-lines"">` in wikitext?  That's valid wikitext.  Should Parsoid try to re-serialize this as a `<lines>` tag?
+Probably not as the <pre> tag introduces background-color and borders which is not likely to be in high demand as far as Wikisource goes. I can't speak for other projects however.
+
+I'm not even sure the current <pre> scheme follows the ""new"" css3 properties of //white-space: pre-wrap// or //white-space: pre-line// for that matter. 
+
+> * Generally styles hard-coded by mediawiki core are prefixed.  The `poem` class is not.
+I would hope the accepted practices and/or appropriate procedures would dictate this.
+
+> * If `<poem>` is aliased to `<lines>`, are we going to break all of wikisource overnight?
+Building an all encompassing testbed on //test2.wikipedia.org// to experiment against prior to roll out seems like the logical way to address such concerns in my view. 
+
+> * Is a recursive parse strategy really appropriate?  It means that `<lines>` and `<pre>` are going to grow additional inconsistencies on the edge cases.  For example, `'''foo<lines>bar'''bat` could get rather confused about its `<b>`s. 
+I'd need more clarity re: the direction ultimately taken regarding the earlier points to reply here 
+
+",1443489871,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"In particular, I'm interested in hearing more from @GOIII about:
+> force the opening and closing poem tags to always reside on their own lines
+and
+> ways to use empty inline-blocks to ''handle'' not only stanza spacing; but indentation and eol padding as well. Making attribute manipulation easier through the opening (margin-top) or closing (margin-bottom) tags of Line itself could dramatically cut down on stuff like that.
+Lets get a spec for `<lines>` written down in such a way that we can discuss issues like this:
+* Should the tags be forced to be on their own lines?  (The current implementation doesn't force this.)
+* Can you write `<lines class=""foo"">`?  Does this override the default ""poem"" and ""mw-lines"" classes, or add to them?  Is this sufficient for the different styling @GOIII describes?  (The current implementation doesn't allow extra classes.)
+* What should the Parsoid representation be?
+* What if somebody writes `<pre class=""poem mw-lines"">` in wikitext?  That's valid wikitext.  Should Parsoid try to re-serialize this as a `<lines>` tag?
+* Generally styles hard-coded by mediawiki core are prefixed.  The `poem` class is not.
+* If `<poem>` is aliased to `<lines>`, are we going to break all of wikisource overnight?
+* Is a recursive parse strategy really appropriate?  It means that `<lines>` and `<pre>` are going to grow additional inconsistencies on the edge cases.  For example, `'''foo<lines>bar'''bat` could get rather confused about its `<b>`s. ",1443122831,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"From Parsoid's perspective, the biggest problem with `<lines>` is unclear semantics.
+
+I suggest that this patch go through the RFC process first.  Let's write up a document which describes exactly how we want `<lines>` to behave.  We should also discuss deployment strategy in the RFC -- should we turn off support in core until Parsoid and VE also support it?  Or implement stopgap support which doesn't allow editing sections which contain `<lines>` (treating it an an ""unknown extension""), or what?
+
+And what is our strategy for migrating existing `<poem>` content to `<lines>`?  Is there an automatic translation?  Or are some details of the semantics going to trip us up when we try to convert existing content?
+
+As @GOIII states, our paragraph handling in the wikitext parser is already extremely complex, and there are a lot of existing workarounds which depend on details of `<poem>` in order to obtain specific effects in poetry.  If we're going to create a new feature, let's make sure it can actually handle all the things that folks want it to do, without crazy hacks.",1443121493,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"> **Merge Poem extension into MediaWiki core**
+Well now.... I've found the most interesting patch to watch for 2015.  If //$paragraphStack// is going to have a [greater] role when it comes to Poem's application - I'm sure no harm can ever come of it.
+</sarcasm off>
+
+Seriously - I hope whenever this move goes through, its given a week of vetting on test/test2 before its deployed to the usual suspects in a formal build. And, while I'm of like mind in the assessment it should have never existed in the manner that it has to date & the //Line//s alternative would be the best route to follow - there are sooo many people that depend on it on an almost daily basis just on Wikisource alone that I would not have the nuts to screw around with it like this.
+
+Truthfully, the issues with the tag to date have mostly been over the User:s response on occasion to the parser's `<p><br /></p>` effect compounded by the esoteric formatting typically done via template are both really where the ''blame'' should go than anything found in the extension itself. Admittedly, the choice //not// to force the opening and closing poem tags to always reside on their __own lines__ upon save & rendering starting on day-one with it's introduction sure hasn't helped matters either.
+
+I implore you to mirror `.mw-body`s definition of `P` rather than the one(s) found in `Elements.css` -- those values are all long usurped by the time the page finishes loading its 1st click-in of the session. You'll find that `0.1`//em// less between the two definitions in //margin-top// is hard to catch initially... until the `1.5`em `line-height` setting is replaced [again?]  -- setting it  [back?] to //inherit// that is.
+
+The last thing that comes mind would be more of an enhancement (like in T15644) than a bug . //Had// Poem been crafted to force it's tags to their own line/line-starts, the closing tag of the previous stanza would ''land'' right above the opening tag of the stanza that followed more often than not. This would be desirable because the ''gap'' between verses or stanzas are rarely as small as the predefined paragraph's are. Contributor's frequently came up with all sorts of ways to use empty inline-blocks to ''handle'' not only stanza spacing; but indentation and eol padding as well. Making attribute manipulation easier through the opening (//margin-top//) or closing (//margin-bottom//) tags of //Line// itself could dramatically cut down on stuff like that.",1420497073,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"> **Merge Poem extension into MediaWiki core**
+Well now.... I've found the most interesting patch to watch for 2015.  If //$paragraphStack// is going to have a [greater] role when it comes to Poem's application - I'm sure no harm can ever come of it.
+</sarcasm off>
+
+Seriously - I hope whenever this move goes through, its given a week of vetting on test/test2 before its deployed to the usual suspects in a formal build. And, while I'm of like mind in the assessment it should have never existed in the manner that it has to date & the //lines// alternative would be the best route to follow - there are sooo many people that depend on it on an almost daily basis just on Wikisource alone that I would not have the nuts to screw around with it like this.
+
+Truthfully, the issues with the tag to date have mostly been over the User:s response on occasion to the parser's `<p><br /></p>` effect compounded by the esoteric formatting typically done via template are both really where the ''blame'' should go than anything found in the extension itself. Admittedly, the choice //not// to force the opening and closing poem tags to always reside on their __own lines__ upon save & rendering starting on day-one with it's introduction sure hasn't helped matters either.
+
+I implore you to mirror `.mw-body`s definition of `P` rather than the one(s) found in `Elements.css` -- those values are all long usurped by the time the page finishes loading its 1st click-in of the session. You'll find that `0.1`//em// less between the two definitions in //margin-top// is hard to catch initially... until the `1.5`em `line-height` setting is replaced [again?]  -- setting it  [back?] to //inherit// that is.
+
+The last thing that comes mind would be more of an enhancement (like in T15644) than a bug . //Had// Poem been crafted to force it's tags to their own line/line-starts, the closing tag of the previous stanza would ''land'' right above the opening tag of the stanza that followed more often than not. This would be desirable because the ''gap'' between verses or stanzas are rarely as small as the predefined paragraph's are. Contributor's frequently came up with all sorts of ways to use empty inline-blocks to ''handle'' not only stanza spacing; but indentation and eol padding as well. Making attribute manipulation easier through the opening (//margin-top//) or closing (//margin-bottom) tags of //Line// itself could dramatically cut down on stuff like that.",1420453788,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"> **Merge Poem extension into MediaWiki core**
+Well now.... I've found the most interesting patch to watch for 2015.  If //$paragraphStack// is going to have a [greater] role when it comes to Poem's application - I'm sure no harm can ever come of it.
+</sarcasm off>
+
+Seriously - I hope whenever this move goes through, its given a week of vetting on test/test2 before its deployed to the usual suspects in a formal build. And, while I'm of like mind in the assessment it should have never existed in the manner that it has to date & the //lines// alternative would be the best route to follow - there are sooo many people that depend on it on an almost daily basis just on Wikisource alone that I would not have the nuts to screw around with it like this.
+
+Truthfully, the issues with the tag to date have mostly been over the User:s response on occasion to the parser's `<p><br /></p>` effect compounded by the esoteric formatting typically done via template are both really where the ''blame'' should go than anything found in the extension itself. Admittedly, the choice //not// to force the opening and closing poem tags to always reside on their __own lines__ upon save & rendering day-one sure hasn't helped matters.
+
+I implore you to mirror `.mw-body`s definition of `P` rather than the one(s) found in `Elements.css` -- those values are all long usurped by the time the page finishes loading its 1st click-in of the session. You'll find that `0.1`//em// less between the two definitions in //margin-top// is hard to catch initially... until the `1.5`em `line-height` setting is replaced [again?]  -- setting it  [back?] to //inherit// that is.
+
+The last thing that comes mind would be more of an enhancement (like in T15644) than a bug . //Had// Poem been crafted to force it's tags to their own line/line-starts, the closing tag of the previous stanza would ''land'' right above the opening tag of the stanza that followed more often than not. This would be desirable because the ''gap'' between verses or stanzas are rarely as small as the predefined paragraph's are. Contributor's frequently came up with all sorts of ways to use empty inline-blocks to ''handle'' not only stanza spacing; but indentation and eol padding as well. Making attribute manipulation easier through //line// itself could dramatically cut down on stuff like that.",1420453542,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 had a related patch set uploaded (by TTO):
+Merge Poem extension into core
+
+[[https://gerrit.wikimedia.org/r/106861]]
+
+#patch-for-review",1419905484,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #42)
+> (In reply to comment #38)
+>> A Global Message Delivery to all Wikisource Scriptoriums/Village pump is
+>> higly recommended
+> 
+> MZMcBride, could you advise how feasible this would be?
+
+I think a mention in [[m:Tech/News]] is sufficient here. Nothing is breaking, as I understand it, so this news is purely informational: ""In addition to <poem>, you can also now use <some other tag name>.""
+
+If you really want to send a global message, you can use [[m:MassMessage]].",1406091878,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to James Forrester from comment #49)
+> I don't particularly mind it being merged into core from an ""editing"" POV,
+> but it is ""yet another feature"" in MediaWiki core which we're meant to be
+> making leaner, faster and more flexible, which this roughly feels like it
+> goes against.
+> 
+> The Parsoid-land changes aren't too hard to handle, I believe, so that
+> shouldn't block this.
+
+It's also another one of those features that will come in at least slightly handy on almost every wiki, though. It's deployed on a significant percentage of wikis, and on those on which it isn't deployed, the users probably wish it were deployed when they run into situations that call for its use. https://wikiapiary.com/wiki/Extension:Poem
+
+Admittedly, it's not as important as, say, ParserFunctions or Cite (both of which should probably be merged to the core, by the way). But it's not very harmful, either.",1406061505,PHID-USER-h3izjiozzysppsokit7l,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to Kunal Mehta (Legoktm) from comment #48)
+> (In reply to Tpt from comment #45)
+> > Yes, you have right with ""mw-lines"".
+> > 
+> > I understand your concern with differing functionality that would require
+> > two buttons in the editing interface (it's the major concern I see). I think
+> > we should have feedback from the VisualEditor team.
+> 
+> James, do you/your team have an opinion?
+
+I don't particularly mind it being merged into core from an ""editing"" POV, but it is ""yet another feature"" in MediaWiki core which we're meant to be making leaner, faster and more flexible, which this roughly feels like it goes against.
+
+The Parsoid-land changes aren't too hard to handle, I believe, so that shouldn't block this.",1406060775,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to Tpt from comment #45)
+> Yes, you have right with ""mw-lines"".
+> 
+> I understand your concern with differing functionality that would require
+> two buttons in the editing interface (it's the major concern I see). I think
+> we should have feedback from the VisualEditor team.
+
+James, do you/your team have an opinion?",1406017589,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 restored by Legoktm:
+Merge Poem extension into core
+
+Reason:
+I think this is a valuable changeset that should be pursued.
+
+https://gerrit.wikimedia.org/r/106861",1406016597,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 abandoned by Krinkle:
+Merge Poem extension into core
+
+Reason:
+Closing for now to clear pending review dashboard. Feel free to re-open when you can work on it.
+
+https://gerrit.wikimedia.org/r/106861",1405886331,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Yes, you have right with ""mw-lines"".
+
+I understand your concern with differing functionality that would require two buttons in the editing interface (it's the major concern I see). I think we should have feedback from the VisualEditor team.",1392368977,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"That's a very good suggestion, Tpt. I would be inclined to call the CSS class something more like ""mw-lines"" or similar, to comply with modern class naming standards.
+
+However I wonder if it is really a good idea to provide differing functionality, however minor, between <poem> and <lines>?",1392368471,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"As I believe that <poem> tag will be kept as an alias forever, it may be interesting to make <poem> and <lines> semantic a little bit different:
+- <lines> would be presentational only and the output will have the ""lines"" class as in <pre class=""lines"">
+- <poem> has the same presentational effect as <lines> but use the ""poem"" class to specify that the content is a poem as in <pre class=""lines poem"">
+
+It won't break sites CSS because the current pages only use the poem tags. If wikis wants to use their custom CSS for <poem> tag with all <lines> tags, they will only have to change ""poem"" by ""lines"" in their rules.",1392367071,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #37)
+> (In reply to comment #31)
+> > 1) In comment 29, Jesús Martínez Novo made a good suggestion to more widely
+> > publicize the new <lines> name before it gets committed.  
+> > A mailing list thread might be a good way to
+> > kick off this discussion.
+> 
+> I'll post one.
+
+http://lists.wikimedia.org/pipermail/wikitech-l/2014-February/074337.html
+
+No replies, so I assume no-one is concerned.
+
+(In reply to comment #38)
+> A Global Message Delivery to all Wikisource Scriptoriums/Village pump is
+> higly recommended
+
+MZMcBride, could you advise how feasible this would be?",1392363249,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #40)
+> The <poem/> tag usage on texts that does not contains poems, only the need to
+> parse line breaks in a different behaviour, isn't the feature itself provided
+> by the extension, only a very interesting side effect.
+
+Please read the preceding comments in this bug report. The reason why this tag is going to be made available under the name <lines> is to emphasise that is not only used for poems, but for other texts that require the preservation of line breaks. This is not merely a ""side effect"", but the key feature of this tag.
+
+> IMHO before merging Extension:Poem into core it firstly needs to addresses
+> all
+> expected behaviours in their original expected feature,
+
+A merge of an extension into core, means taking the extension's existing functionality, and placing it in MediaWiki core. It does not mean we add extra features at the same time.
+
+The Poem extension only provides poem-related (line break preservation) functionality, so that is all that core is getting in this merge. This is not the place to discuss other ""original expected features"".",1392079227,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"The <poem/> tag usage on texts that does not contains poems, only the need to parse line breaks in a different behaviour, isn't the feature itself provided by the extension, only a very interesting side effect.
+
+It looks to me like in very old MediaWiki versions without file undeletion support: media deletion at that time resulted in less disk space being used. But that aren't the feature, only a side effect.
+
+IMHO before merging Extension:Poem into core it firstly needs to addresses all expected behaviours in their original expected feature, ie to provide quickly and in easy ways alternatives to format text portions based in a given form of language.",1392077997,PHID-USER-gu24fgh5wu7isjb4g5b7,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #38)
+> In the time that <poem/> tag arised on Wikisources, we have also asked for a
+> <prose/> tag (See bug 6810).
+
+That is an entirely separate issue. The presence or absence of a <prose> tag is not going to affect the resolution of this bug.
+
+> As you can see on [3] and [4], the formatting isn't the same currently
+> adopted
+> in <poem/> tag, so the current consensus to set <poem/> as an alias for a new
+> tag name isn't viable.
+
+I don't understand your point here. What has this got to do with the <poem> tag?",1392076482,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"A Global Message Delivery to all Wikisource Scriptoriums/Village pump is higly recommended, since this extension was firtly developed to Wikisource wikis and latter enabled on all Wikimedia wikis [1] [2].
+
+In the time that <poem/> tag arised on Wikisources, we have also asked for a <prose/> tag (See bug 6810).
+
+Unfortunately at that time the developers picked what was most easy to then instead of what is more user intuitive (sorry, but <poem>foo</poem> and {{prose start}}foo{{prose end}} don't makes sense to newcomers (#c6).
+
+As you can see on [3] and [4], the formatting isn't the same currently adopted in <poem/> tag, so the current consensus to set <poem/> as an alias for a new tag name isn't viable.
+
+[1] - https://wikitech.wikimedia.org/wiki/Server_admin_log/Archive_7#June_23
+
+[2] - https://wikitech.wikimedia.org/wiki/Server_admin_log/Archive_10#February_7
+
+[3] - https://en.wikisource.org/wiki/Template:Prose
+
+[4] - https://fr.wikisource.org/w/index.php?title=MediaWiki:Common.css (classe prose : PERIMÉE, utiliser text )
+
+[[:m:User:555]]",1392048878,PHID-USER-gu24fgh5wu7isjb4g5b7,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #31)
+> 1) In comment 29, Jesús Martínez Novo made a good suggestion to more widely
+> publicize the new <lines> name before it gets committed.  
+> A mailing list thread might be a good way to
+> kick off this discussion.
+
+I'll post one.
+
+> 2) In the comments on the patch, '----' was brought up as the last remaining
+> way that the current <lines> implementation differs from 'indent-pre'
+> handling.
+>  I'd like to resolve this discrepancy: I really really *really* don't want to
+> complicate the parser more with Yet Another Slightly Different Way to handle
+> preformatted content.
+
+Let me expand a bit here: <poem> is designed for the treatment of poetry. I don't know what indent-pre was designed for, but one assumes it was intended for general-purpose, preformatted text, such as command line outputs and plain-text tables. The two use-cases are somewhat different.
+
+I went through and found the following differences. There are probably many others.
+
+* For some reason, indent-pre doesn't handle ----. Presumably this is so
+  preformatted tables, etc (e.g. those copied out of the MySQL monitor)
+  still appear correctly. This consideration is not relevant for <poem> and
+  so ---- is parsed inside these tags. Indeed, ---- within <poem> is quite
+  common at Wikisource.
+
+* Indents using : are ignored within indent-pre (presumably because they
+  don't make a whole lot of sense in a preformatted context). In <poem>,
+  indents are handled specially (using a fixed-width <span> to give 1em
+  indentation per : character), and line-initial spaces are transformed
+  to &nbsp;, to cope with the special formatting of some poetry.
+
+* Wikitext {| |} tables are available within <poem>, whereas indent-pre is
+  aborted as soon as a table is found.
+
+* Indent-pre formatting is aborted whenever a block-level tag is
+  encountered on the line. Block-level formatting is, however, available
+  inside <poem> (although this is only useful for stuff like <table>, since
+  the appearance of tags like <p> is affected quite badly by the <pre>
+  environment).
+
+* Indent-pre is not available inside <blockquote>, for unclear reasons.
+  <poem> works fine inside <blockquote>, just as anywhere else.
+
+* <poem> allows the application of a custom class/ID/style. The use of a
+  tag also allows extra attributes to be used - I have a patch in the works
+  that adds line numbering support to <poem>, which makes use of several
+  additional tag attributes (see bug 13644).
+
+I don't think it is correct to speak of ""resolving"" these discrepancies. As you can see, most of them seem to exist for a reason, and most involve idiosyncrasies in the existing indent-pre behaviour, any changes to which would disrupt existing wikitext.
+
+(Note, when I talk about <poem> above, I'm talking about the new implementation in Gerrit. The old extension sometimes does things differently.)
+
+> 3) I'd also like to review the code coverage issues a little more, to ensure
+> that we're sharing code (and CSS rules) to the maximum extent possible.
+
+I think this is up to you, Scott, and others in the know.",1391835029,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #31)
+> 1) In comment 29, Jesús Martínez Novo made a good suggestion to more widely
+> publicize the new <lines> name before it gets committed.  We almost
+> inadvertently introduced a conflict with <verbatim>, I'd like some greater
+> certainty that the new <lines> name proposal has been seen by a larger number
+> of editors/extension authors.  A mailing list thread might be a good way to
+> kick off this discussion.
+
+Will a post to wikitech-l suffice? Or is more needed in your opinion? I can probably handle the communication portion of this, just please be explicit with what you would consider sufficient.
+
+> 2) In the comments on the patch, '----' was brought up as the last remaining
+> way that the current <lines> implementation differs from 'indent-pre'
+> handling.
+
+Okay, I figured out what you mean here. At [[testwiki:Bug 52061#Indent-Pre (""Preceding space"")]] a ""----"", the wikitext equivalent of a horizontal rule (<hr>), is not current expanded when there's a leading space.
+
+In my opinion, this behavior (preceding space + unexpanded horizontal rule) is a separate issue that should be filed as a separate bug report (if one doesn't exist already) and is not a blocker to merging Gerrit change 106861. If you feel differently, can you please elaborate? (Also, can you please search for a relevant bug report and/or file one?)
+
+> 3) I'd also like to review the code coverage issues a little more, to ensure
+> that we're sharing code (and CSS rules) to the maximum extent possible.  This
+> is to ensure that point #2 continues to hold in the future, and we don't
+> accidentally introduce subtle incompatibilities by changing only one side of
+> a code path.
+
+Sure, code review is ongoing at Gerrit change 106861. If you have additional suggestions for technical changes, feel free to leave them on Gerrit. :-)",1391830615,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Instead of finding similarities between poem and indent-pre, which is moot since the indentation already breaks all markup that depends on being on the first column of the line, we may look at similarities between poem and normal wikitext.
+
+It's practically the same. The only difference is that poem treats newlines as <br/>, while normal text simply ignore newlines or convert them into paragraphs when there's a combination of newlines.",1390939202,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #31)
+> I'd like to resolve this discrepancy: I really really *really* don't want to
+> complicate the parser more with Yet Another Slightly Different Way to handle
+> preformatted content.
+
+There's nothing really new here :) We're just sending a <pre> tag to the parser, after all. The change to the parser itself is minuscule, and arguably it is a fix for a long-standing bug that was never exposed until now.
+
+(In reply to comment #33)
+> (07:34:41 PM) subbu: so, we were wrong .. <poem> is not indent-pre with
+> classes then.
+
+I'm glad you're aware of this! As I said in Gerrit, the similarities are purely coincidental.",1390875527,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"From chat:
+
+(07:32:52 PM) subbu: i just checked the updated wiki page .. and  <hr> and colon-indents seem different in <poem> vs. indent-pre .. probably all wikitext elements that occur in SOL position but are strict about not having any leading ws.
+(07:33:16 PM) cscott-free: how many of those are there?
+(07:33:36 PM) subbu: i suppose <poem> just calls regular parse on embedded content and then wraps it in wrapper with the right css classes
+(07:33:43 PM) subbu: tables are fine with leading space.
+(07:34:05 PM) subbu: headings, lists, hr dont work if there is leading WS, iirc.
+(07:34:41 PM) subbu: so, we were wrong .. <poem> is not indent-pre with classes then.
+(07:35:10 PM) cscott-free: but should it be?  i don't like the idea of adding a bunch of new special cases to the parser.
+(07:35:48 PM) subbu: cscott, it cannot be without breaking <poem> behavior OR breaking existing pages that have leading space before :*;#=- chars
+(07:35:59 PM) cscott-free: if we can at least parameterize it, such that indent-pre has SOL markers turned off, and <poem> has SOL markers turned on, that would make me happier.
+(07:36:14 PM) cscott-free: rather than poem just being gratuitously different in random ways.
+(07:36:24 PM) subbu: ya, you are talking of refactoring code in the parser.
+(07:36:30 PM) subbu: and reusing it.
+(07:36:56 PM) cscott-free: subbu: i'm certainly talking about reusing more parser code, rather than implementing <poem> as a brand new crazy thing.
+(07:37:25 PM) cscott-free: i'm tired of having weird corner cases everywhere.
+(07:37:50 PM) cscott-free: there should be some principled way we can describe how indent-pre and <poem> are similar.
+(07:37:57 PM) subbu: maybe spend some time, how <poem>/<lines> would fit in parsoid land and that can inform the discussion of how the core code can be restructured .. but refactoring/restructure that seems like a lot of work as well.
+(07:38:33 PM) cscott-free: in a nutshell that's why i don't want <poem> merged too quickly.  i'd like to understand better how it all fits in.
+(07:38:53 PM) cscott-free: and probably to do some dumpGrepping to figure out how much we can change indent-pre and/or <poem> without breaking too much stuff.",1390869777,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,I added a few more test cases to [[testwiki:bug 52061]] -- leading colons are also parsed differently inside <poem>.,1390847758,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I think I just saved this patch from a premature +2.
+
+I'd like to summarize what still needs to be done here:
+
+1) In comment 29, Jesús Martínez Novo made a good suggestion to more widely publicize the new <lines> name before it gets committed.  We almost inadvertently introduced a conflict with <verbatim>, I'd like some greater certainty that the new <lines> name proposal has been seen by a larger number of editors/extension authors.  A mailing list thread might be a good way to kick off this discussion.
+
+2) In the comments on the patch, '----' was brought up as the last remaining way that the current <lines> implementation differs from 'indent-pre' handling.  I'd like to resolve this discrepancy: I really really *really* don't want to complicate the parser more with Yet Another Slightly Different Way to handle preformatted content.
+
+3) I'd also like to review the code coverage issues a little more, to ensure that we're sharing code (and CSS rules) to the maximum extent possible.  This is to ensure that point #2 continues to hold in the future, and we don't accidentally introduce subtle incompatibilities by changing only one side of a code path.
+
+Does anyone else have any remaining issues they'd like to see resolved before this is merged?",1390846375,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Regarding my use of ""indent-pre"" above -- I'm looking at this mostly from the perspective of parser maintenance.  As [[testwiki:bug 52061]] demonstrates, the desired behavior of <poem>/<lines> is the same as the existing behavior of 'indent-pre', although the implementation in the original patch was very different.  I would like to try to avoid adding a bunch of new hair (and crazy interactions) with the new feature, and instead try to reuse the existing indent-pre handling code so that all the corner cases were consistent.
+
+In fact, assuming this gets merged, it might be cleaner in the future to document the ""indent pre"" behavior as ""an implicit <lines> surrounding the indented region"".  This would reduce confusion because ""indent pre"" and ""<pre>"" are actually quite different in their handling of embedded wikitext, etc.
+
+I like the name <lines>, btw.",1390666581,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"lines sounds good, or <preservelines>
+
+That said, maybe it would be more user friendly to use a mediawiki.org page to discuss the tag name, so ideas can be better exposed and have more opinions (remember one have to explicitly register an account here to post a comment).
+
+About <poem> itself, I don't know why is a different name really needed. What are other use cases for this? I've just only used it for poem and lyrics (which is basically the same).",1390653738,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I like <lines>, the name puts the focus on the individual ""lines"" of the content, which is also what the tag is doing. Nice lateral thinking, Michael :)",1390648436,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #22)
+> (In reply to comment #16)
+> > <verbatim> is a misleading name since it still parses wikitext in its
+> > content.
+> > It is only verbatim for text-content. 
+> 
+> I do see what you mean here. The problem is, we have so far been unable to
+> come
+> up with a better name! <poem> is inappropriate as too specific/narrow.
+> 
+
+What about <lines>? The tag just just preserves the lines in its content, and it seems generic enough for what is used.",1390646698,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #25)
+> Since this is going to be merged into core/php-parser, presumably, you
+> control
+> this behavior and where in the parser pipeline the outer wrapping <pre> tag
+> is
+> generated? I haven't looked at the parser changes to answer that or how easy
+> this is since I haven't really hacked the php parser. Maybe Scott can answer
+> that more readily. 
+
+I think I've got this part sorted.",1390611047,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"That is right reg. CSS.
+
+Since this is going to be merged into core/php-parser, presumably, you control this behavior and where in the parser pipeline the outer wrapping <pre> tag is generated? I haven't looked at the parser changes to answer that or how easy this is since I haven't really hacked the php parser. Maybe Scott can answer that more readily. 
+
+At least with Parsoid, that is what we will consider outputting for this new tag unless VE folks find a <div> tag simpler than a marked up <pre> tag (seems unlikely).",1390609860,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"What you are saying makes sense. Presumably the CSS for .poem would have to ""neutralise"" the monospace/gray formatting normally applied to pre tags.
+
+My main question is, if we output a <pre> tag from the tag hook, will wikitext inside that tag still get parsed, as it should be?",1390609332,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #22)
+
+> (In reply to comment #20)
+> > IMO the <poem> tag should be rendered as <pre
+> > class=""poem""> and it has exactly the behavior of indent-pre (with an extra
+> > HTML
+> > class and without the necessity to write the leading indentation).
+> 
+> A few questions about this statement:
+> 
+> * The gray box/monospaced font of <pre>/indent-pre would have to be removed
+> for
+>   <poem> blocks.
+> * What are the existing differences between <poem> and indent-pre?
+> * <pre> does not render identically to indent-pre, so could you explain how
+>   rendering poems using <pre class=""poem""> would help?
+
+We weren't very clear about what we were discussing there. 
+
+What Scott meant is that the patch should generate <pre class=""poem""> .. </pre> for the HTML of the <verbatim>..</verbatim> (or <pre-text> or whatever tag name is picked) instead of generating <div class=""poem"">..</div>. It is cleaner and the ouput is semantically closer to the intention of the <verbatim> tag.",1390608896,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #16)
+> <verbatim> is a misleading name since it still parses wikitext in its
+> content.
+> It is only verbatim for text-content. 
+
+I do see what you mean here. The problem is, we have so far been unable to come up with a better name! <poem> is inappropriate as too specific/narrow.
+
+> Is there another way of achieving this
+> without adding a new tag?
+
+The <poem> tag is already in wide use. I don't see the problem with adding a tag for this functionality.
+
+(In reply to comment #20)
+> IMO the <poem> tag should be rendered as <pre
+> class=""poem""> and it has exactly the behavior of indent-pre (with an extra
+> HTML
+> class and without the necessity to write the leading indentation).
+
+A few questions about this statement:
+
+* The gray box/monospaced font of <pre>/indent-pre would have to be removed for
+  <poem> blocks.
+* What are the existing differences between <poem> and indent-pre?
+* <pre> does not render identically to indent-pre, so could you explain how
+  rendering poems using <pre class=""poem""> would help?",1390608255,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I agree reg. output being <pre class='poem'> .. </pre>
+
+However, maybe make it possible for the editor to provide a css-class rather than hardcode class=""poem"" into the tag?
+
+For standard <poem> content,
+<pre-text>
+... 
+</pre-text>
+
+And for other uses,
+<pre-text class=""fancy-css"">
+...
+</pre-text>",1390589947,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I further updated [[testwiki:bug 52061]] to show the difference between <poem> and <pre class=""poem"">.  IMO the <poem> tag should be rendered as <pre class=""poem""> and it has exactly the behavior of indent-pre (with an extra HTML class and without the necessity to write the leading indentation).",1390588717,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #17)
+> I don't know what you mean by indent-pre.
+
+Subbu clarified that this means the preceding space trick. I updated [[testwiki:bug 52061]].",1390587244,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Please, don't use <verbatim>!!. It's already been in use by a Wikia extension [1]
+
+----
+
+[1] http://community.wikia.com/wiki/Help:Verbatim_tags",1390587154,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #16)
+> From what I can tell, looking at output, this is ""indent-pre"" - ""indent"" +
+> CSS-class. Given that indent-pre provides all the formatting functionality, I
+> presume the missing ability of adding CSS-classes onto indent-pre is the
+> primary reason for this new tag? Is there another way of achieving this
+> without adding a new tag?
+
+I don't know what you mean by indent-pre.
+
+I created a test page at [[testwiki:bug 52061]] to demonstrate the poem tag's functionality.",1390586895,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"<verbatim> is a misleading name since it still parses wikitext in its content. It is only verbatim for text-content. 
+
+From what I can tell, looking at output, this is ""indent-pre"" - ""indent"" + CSS-class. Given that indent-pre provides all the formatting functionality, I presume the missing ability of adding CSS-classes onto indent-pre is the primary reason for this new tag? Is there another way of achieving this without adding a new tag?",1390586336,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #10)
+> Regarding the tag name, is <poem> ever actually used for things besides
+> poems?
+
+I looked at some examples in de.wikipedia. Apart from poems and poem-like texts (prayers etc.) there are things like inscriptions and dialogs, which use <poem>. And of course, as it is a wiki, some stupid things like quotes even without any line break in them.",1389605473,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Sure, let's go with verbatim.
+
+Siebrand also noted on Gerrit change 106861 that if/when this gets merged, we'll need to migrate the Poem extension bugs to core.",1389459951,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,I'd also prefer <verbatim> as the name.,1389446044,PHID-USER-3qsavo6roa5h32xcsgng,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,I'm wondering if people would prefer <verbatim> as the name of this tag?,1389432065,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 had a related patch set uploaded by TTO:
+Merge Poem extension into core
+
+https://gerrit.wikimedia.org/r/106861",1389413873,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"The compact feature has always seemed quite buggy (or at least bizarrely unintuitive) and I wonder if we would really hurt much by killing it altogether.
+
+Regarding the tag name, is <poem> ever actually used for things besides poems? I usually use <pre> for other cases.",1389061208,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #8)
+> I am thinking something like <verbatim>, <asis> (""as is""), <nocollapse>,
+> <pretext>/<pre-text> (as in <pre> but for text, not code), <keepbreaks>
+> [...]
+
+Okay, I'll paint this bikeshed. I like verbatim or pretext. How about one of those?
+
+> 2. The attribute ""compact"" seems to actually make the display less compact.
+> See the testcase at [[mw:Extension:Poem]]. I think we need a new name/alias for
+> this too. However, I have no idea what it is actually meant to be used for...
+
+I'm not sure ""compact"" is needed... do people use it? If so, are there examples of it in the wild?",1389057399,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"OK, I'm taking a look at this. The merge looks easy enough, but I need advice.
+
+Poem has two major nomenclature issues:
+
+1. The tag should have another name besides <poem>. In comment 6 <nobreak> was suggested, but Poem does the reverse - it preserves line breaks. I am thinking something like <verbatim>, <asis> (""as is""), <nocollapse>, <pretext>/<pre-text> (as in <pre> but for text, not code), <keepbreaks> ......... ?? Any better ideas?
+
+2. The attribute ""compact"" seems to actually make the display less compact. See the testcase at [[mw:Extension:Poem]]. I think we need a new name/alias for this too. However, I have no idea what it is actually meant to be used for...",1388220804,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #6)
+> (In reply to comment #5)
+> > If you merge it to core, please call it something other than <poem>. Other
+> > than that I couldn't care less :D
+> 
+> I think we must keep the name ""<poem>"" for backward-compatibility, but it
+> should definitely have a saner alias (""<nobreak>"" or something).
+
+The main name of the feature should be something else, <poem> can be an alias for backwards-compatibility.",1374862476,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #5)
+> If you merge it to core, please call it something other than <poem>. Other
+> than that I couldn't care less :D
+
+I think we must keep the name ""<poem>"" for backward-compatibility, but it should definitely have a saner alias (""<nobreak>"" or something).",1374855121,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"If you merge it to core, please call it something other than <poem>. Other than that I couldn't care less :D",1374849740,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Poem was merged into core back in 2008, but subsequently reverted; see http://www.mediawiki.org/wiki/Special:Code/MediaWiki/43520.
+I must say, however, that I totally agree with the original report and Poem (along with some obvious stuff like CheckUser, RenameUser, etc.) should be in core; maybe it should've been there from day one, even.",1374843237,PHID-USER-mlp7cjyksjzemkdr5ued,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Steps to deprecate an extension (apart from actual code changes):
+
+* Turn off extension for testwiki in InitialiseSettings.php and make sure nothing breaks (1 deployment cycle)
+* Turn off extension for all wikis in InitialiseSettings.php and make sure nothing breaks (1 deployment cycle)
+* Remove extension from CommonSettings.php, wmf-config/extension-list, and make-wmf-branch/default.conf (1 deployment cycle)
+* Move/deprecate MediaWiki documentation
+* Get component removed from Bugzilla, migrate any existing bugs
+* Have project removed from Gerrit (not immediately of course)",1374792408,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #1)
+> Anytime an extension is created or deprecated it's a logistical pain in the
+> ass.
+
+Can you elaborate on this? It seems pretty easy to me.",1374789622,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I'm cool with merging it into core, although I probably wouldn't call it 'easy'. Anytime an extension is created or deprecated it's a logistical pain in the ass. Also, I would prefer to have this idea vetted on Wikitech-l before someone actually goes through the trouble of doing it.",1374789414,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"VE should work as expected without clipboard access.  Currently it only half initalises.
+
+1. Install Kill Evil in Chrome or similar
+2. Edit any page
+
+(https://chrome.google.com/webstore/detail/kill-evil/epieehnpcepgfiildhdklacomihpoldk)
+
+Result:
+https://en.wikipedia.org/wiki/File:Missing-ui-ve.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374713100,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cn7rkjg6saedlg6no5bg,task_description,declined
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),The extension in question doesn't exist anymore. I still don't think we need to support any future extension that kills essential web APIs.,1718626265,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"People disable these features for good reason; a nice error message, or even an ugly error message, would be helpful to let them know why VE wont load.",1462884959,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"@Esanders I agree, but perhaps we should also be better about error handling in general when an app such as VE fails to launch. There is no problem with not supporting Kill Evil, but I think there is a problem of ending up in a half initiated state with no user feedback right ?
+
+I think that is an area that we could be better at (be it VE, UploadWizard or what not).",1462883974,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),This little used extension kills APIs that are essential for VE to work.,1462883110,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),Sorry for very slow triage.,1390417139,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"When 'Kill Evil' addon exists, there are two failures to load modules, and then an exception which halts the VE initialisation half way.
+
+Module 'WrappedSelection' failed to load: Module 'WrappedSelection' failed to load: No means of selecting a Range or TextRange was found rangy-core-1.3.js:105
+
+Module 'Position' failed to load: required module 'WrappedSelection' not supported rangy-core-1.3.js:105
+
+Uncaught TypeError: Object #<WrappedSelection> has no method 'refresh' rangy-core-1.3.js:3035
+
+WrappedSelection rangy-core-1.3.js:3035
+getSelection rangy-core-1.3.js:3084
+ve.ce.Surface.showSelection ve.ce.Surface.js:1325
+ve.ce.Surface.onChange ve.ce.Surface.js:747
+oo.EventEmitter.emit oo.js:421
+ve.dm.Surface.change ve.dm.Surface.js:402
+ve.dm.SurfaceFragment.select ve.dm.SurfaceFragment.js:448
+ve.ui.Surface.initialize ve.ui.Surface.js:81
+(anonymous function) ve.init.mw.ViewPageTarget.js:1098
+proxy load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.t…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130725T023359Z:775
+
+in ve.ui.Surface method initialize, the following invocation should probably be skipped if those rangy modules have failed to load.
+
+   // By re-asserting the current selection and forcing a poll we force selection to be something
+   // reasonable - otherwise in Firefox, the initial selection is (0,0), causing bug 42277
+   this.model.getFragment().select();",1374728047,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),This isn't a fancy thing. You can't do things like bold the selection if you can't access information about what is actually selected.,1374714907,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),That too ;-)  Making the bug more general.  Hopefully VE is able to be at least partially functional without all those fancy things.,1374714190,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"That's more likely caused by the ""getSelection and onselectstart/onmousedown"" part of that extension.",1374713556,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"A very common chess template on many Wikipedias recommends using '|=' , and most instances of chess boards use this syntax
+https://en.wikipedia.org/wiki/Template:Chess_diagram#Standard_diagram
+https://de.wikipedia.org/wiki/Vorlage:Schachbrett#Standarddiagramm
+
+On German Wikipedia, editing the template strips the '=' signs.  This article is on the parsoid topfails
+https://de.wikipedia.org/wiki/Edward_Lasker?veaction=edit
+http://parsoid.wmflabs.org:8001/topfails/1
+
+There are 900 uses of these chess templates on German Wikipedia.
+https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/Vorlage:Schachbrett&limit=750
+https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/Vorlage:Schachbrett-klein&limit=115
+A few more of
+https://de.wikipedia.org/wiki/Vorlage:Schachbrett-10x10
+https://de.wikipedia.org/wiki/Vorlage:Schachbrett-8x10
+https://de.wikipedia.org/wiki/Vorlage:Schachbrett-Chaturanga
+
+The syntax is used on many other WPs, incl. eswp, frwp, plwp and ruwp
+https://es.wikipedia.org/wiki/Plantilla:Diagrama_de_ajedrez#Diagrama_est.C3.A1ndar
+https://fr.wikipedia.org/wiki/Mod%C3%A8le:Diagramme_d%27%C3%A9checs
+https://fr.wikipedia.org/wiki/Alexandre_Alekhine
+https://pl.wikipedia.org/wiki/Szablon:SzachyDiagram
+https://ru.wikipedia.org/wiki/%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:%D0%A8%D0%B0%D1%85%D0%BC%D0%B0%D1%82%D0%BD%D0%B0%D1%8F_%D0%B4%D0%B8%D0%B0%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B0
+
+On English, the VE UI can go into massive layout problems, but the UI issues may all be due to the Parsoid issue.
+https://en.wikipedia.org/wiki/French_Defence?veaction=edit
+The number of uses on enwp appears to be in the same ballpark as dewp
+https://en.wikipedia.org/w/index.php?title=Special:WhatLinksHere/Template:Chess_diagram&limit=900
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+{T55226}
+{T53166}
+{T73404}",1374655260,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-73q6sosb7r2syig35llq,task_description,resolved
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"There are no screenshots here to show how it used to be broken, but it seems to behave correctly now.",1429477499,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,Also at https://fr.wikipedia.org/w/index.php?title=Tour_(%C3%A9checs)&diff=96381943&oldid=95391142 .,1378286809,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"Moving to visual editor in case there is something about the Parsoid output that is causing broken layout in the ""|="" form of chess-board syntax.  Please assign to Parsoid if there is a bug here in our output.",1375205944,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"Hmm .. strange.  When I copied both forms of the syntax into a file and parse it with Parsoid, the html renders just fine.  Curious why it breaks in VE however.
+
+Verifiable here: http://parsoid.wmflabs.org/_wikitext/
+
+Paste this there and scroll down past the literal html and you'll see this rendered correctly there.
+
+------------------------------------------------
+{{Infobox chess opening
+|openingname = French Defence
+|image = {{Chess diagram|=
+|
+|
+|=
+  |rd|nd|bd|qd|kd|bd|nd|rd|=
+  |pd|pd|pd|pd|  |pd|pd|pd|=
+  |  |  |  |  |pd|__|__|__|=
+  |  |  |__|  |__|__|__|__|=
+  |  |  |__|  |pl|__|__|__|=
+  |  |  |__|__|__|__|__|__|=
+  |pl|pl|pl|pl|__|pl|pl|pl|=
+  |rl|nl|bl|ql|kl|bl|nl|rl|=
+|
+}}
+|moves=1.e4 e6
+|ECO=C00–C19
+|birth =
+|nameorigin = London vs. Paris correspondence match (1834–36)
+|parentopening = [[King's Pawn Game]]
+|AKA =
+|chessgid=39913&move=2&moves=e4.e6&nodes=21720.39913
+}}
+------------------------------------------------",1375137900,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"An alternative 'pretty' syntax that doesnt cause breakages is:
+
+https://de.wikipedia.org/w/index.php?title=Edward_Lasker&diff=120835751&oldid=120194113
+
+The html comments are visible in the parameters of the template dialog, but it stops the dirty diffs if this |= syntax is not desirable.",1374655563,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"Several users on the English Wikipedia, most recently Salix, have requested that the parameters for templates should be in the recommended order not alphabetical order. 
+
+For example in {{tracklist}} it lists ""Track10"" before ""Track2"", and in the various citation templates, ""First"" and ""Last"" should be adjacent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374654480,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3r7ax46g5ehieydsuuvm,task_description,resolved
+VisualEditor: Template parameters should be in TemplateData recommended order,"Change 107428 merged by jenkins-bot:
+Use paramOrder data for ordering template parameters
+
+https://gerrit.wikimedia.org/r/107428",1389754734,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"Change 107428 had a related patch set uploaded by Trevor Parscal:
+Use paramOrder data for ordering template parameters
+
+https://gerrit.wikimedia.org/r/107428",1389730796,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,Resolved in Ic3eb665389380c8e3dd6562b059c2f6655a22588,1389730752,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"After filling/testing a couple of templates in ca.wikipedia.org, it looks like the current behavior is the following:
+
+* Required fields are sorted by the order they are listed in the template data.
+* Optional files are sorted alphabetically.
+
+Please sort everything following the same sequence used in the template data. Usually this is the same order used in the ""old"" documentation, which in turn tends to follow the order in which the information is presented.",1386640799,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"The dependency has been fixed.
+
+Is the importance of this still ""Low enhancement""?",1384434926,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,*** Bug 53891 has been marked as a duplicate of this bug. ***,1380655447,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"(In reply to comment #4)
+> There is a good case for imposing some ordering on the template parameters.
+> Often you find some parameters naturally group together. Take for example
+> http://en.wikipedia.org/wiki/Template:Infobox_single/doc There are various
+> parameters which group together:
+> *Ones relating to the image (Cover, Alt, Caption and Border)
+> *Ones to do with the single chronology (Last single, This single, Next
+> single)
+> for infoboxes a prefered order would generally be the order they appear in
+> the
+> template.
+
+Yeah, that sounds a totally reasonable thing to add. Making a bug now…",1377903725,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"There is a good case for imposing some ordering on the template parameters. Often you find some parameters naturally group together. Take for example http://en.wikipedia.org/wiki/Template:Infobox_single/doc There are various parameters which group together:
+*Ones relating to the image (Cover, Alt, Caption and Border)
+*Ones to do with the single chronology (Last single, This single, Next single)
+for infoboxes a prefered order would generally be the order they appear in the template.",1377903377,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"There is no such thing as ""TemplateData recommended order""; the JSON block is unordered and can't be relied upon. Does this imply that we should have a ""parameter order"" value for TemplateData?",1377900547,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"Another example is [[pl:Template:Związek chemiczny infobox]] on pl.wp (infobox for chemical compounds) which has a lot of parameters which should be shown together, but which are not always alphabetically one after another. These groups are for example:
+
+* gęstość + gęstość źródło + stan skupienia w podanej g + g warunki niestandardowe (density, source for density, state of matter for this density, non-standard environment conditions for the density)
+* rozpuszczalność w wodzie + rww źródło + rww warunki niestandardowe (solubility in water, source, non-standard environment conditions)",1375226159,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"An example of this is {{Taxobox}} which has 100+ parameters. There are about 10 recommended parameters which go at the top the list and the rest of the parameters have a strict ordering depending on taxonomic hierarchy. Kingdom, Phylum, Class,	Order, Family, Subfamily, Genus, Species. An example of use is http://en.wikipedia.org/wiki/Formica which gives the fields in a confusing alphabetial order (latin names are used for the fields).
+
+A second problem is the order when no templatedata is specified. In the article http://en.wikipedia.org/wiki/Where_Does_This_Door_Go?veaction=edit
+if you open up the dialog for the {{tracklist}} the parameters are listed in the order track1, track10, track11 ... track15 track2 track3 ... track9. Ideally they would be in strict numerical ordering. This would require a smarter sorting algorithm than just alphabetical. 
+
+Another note is that case insensitive sort is better than case sensitive sort as templates often have the same parameter with different capitalization, 'Image' and 'image'.",1374674837,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"Removing the last reference on a page, with <references/> present, causes the waring:
+
+There are no references with the group """" on this page.
+
+That should be 
+
+There are no references on this page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374580740,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_description,resolved
+VisualEditor: Warning for blank reference list is confusing,"Change 86656 merged by jenkins-bot:
+Add specific message for empty ref group list
+
+https://gerrit.wikimedia.org/r/86656",1380747909,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"Change 86656 had a related patch set uploaded by Esanders:
+Add specific message for empty ref group list
+
+https://gerrit.wikimedia.org/r/86656",1380577840,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"I agree with John: Most pages dont used grouped references. It would be much more intuitive to say that there are no references at all. Several users in the Hebrew Wikipedia complained about it, and I imagine that it's the same in all languages.",1374823191,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"In the use-case for this bug, there are no references of any group, so why mention groups at all.  IMO the UI shouldnt talk about groups unless it is necessary.  Most pages dont used grouped references.",1374612826,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"(In reply to comment #0)
+> Removing the last reference on a page, with <references/> present, causes the
+> waring:
+> 
+> There are no references with the group """" on this page.
+> 
+> That should be 
+> 
+> There are no references on this page.
+
+No. You can have dozens of <ref group=""foo"">s and no <ref>s and get that message.
+
+Perhaps a special-case of ""There are no references without a group on this page."" for the null-group instance?",1374591288,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Allow per-wiki/-namespace disabling of formatting styles e.g. page title,"On the English Wikipedia the page title formatting level is never used in article space, although I understand it is used on some other wikis. It might be that other wikis do not use a dfferent page style.
+
+Accordingly it would be nice to be able to remove/suppress/disable this item from the list on a per namespace (or, less ideally, per wiki) to avoid confusion to new editors. 
+
+Unless this is absolutely trivial to implement, please regard it as a low priority enhancement request.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374576000,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-7abqyeltz5gnkmdn4t4n,task_description,open
+VisualEditor: Allow per-wiki/-namespace disabling of formatting styles e.g. page title,"Sadly not trivial, but yes, this level of flexible configuration would be nice.",1374591912,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7abqyeltz5gnkmdn4t4n,task_subcomment,NA
+VisualEditor: Display name of transclusions as a tool-tip when selected,"At en.wp a user comments:
+""The tooltip with a ""puzzle"" icon that appears when clicking on a template should contain the name of the template used. This would allow readers to be aware of which template they're about to change and would make the Templates interface [[self-documenting]], teaching by example the existence of the most common templates.
+
+For example, the next screenshot would contain the word ""Chembox"" besides the puzzle icon:""
+
+Screenshot: [[File:VisualEditor - Template editing 1.png]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51827",1374512400,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-25n5vcma7cdemv6yuhj7,task_description,resolved
+VisualEditor: Display name of transclusions as a tool-tip when selected,"(In reply to Alex Monk from comment #3)
+> Don't we have this now? What to do about this bug?
+
+Yes, fixed by Trevor's new context menus as of 6 months or so ago.",1416249978,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-25n5vcma7cdemv6yuhj7,task_subcomment,NA
+VisualEditor: Display name of transclusions as a tool-tip when selected,Don't we have this now? What to do about this bug?,1416190833,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-25n5vcma7cdemv6yuhj7,task_subcomment,NA
+VisualEditor: Display name of transclusions as a tool-tip when selected,"(In reply to comment #1)
+> What would this do when multiple templates (or other transclusions) are used
+> in
+> the scope of one transclusion block, like the succession boxes?
+
+I can think of three logical options:
+
+1. The name of the first template and some indication (perhaps an asterisk?) that there are multiple translcusions in the block, e.g. ""s-start *""
+
+2. a list of all the items in the transclusion, e.g. for [[Alan Williams]]:
+
+s-start
+s-par
+s-bef
+s-ttl
+s-aft
+s-end
+
+Note that above, each template is listed only once, even for multiple occurrences, showing repeats is possible also.
+
+3. The names of the first and last templates with an indication (probably an ellipsis) that there are omitted elements, e.g. ""s-start ... s-end"" or
+s-start
+...
+s-end
+
+The horizontal format I'd guess might be easiest to program but would only work for templates with short names.
+
+In either 1 or 3 there could be a way to click to see the templates that are omitted. However I'm not sure how useful that would be, so my suggestion would be to just leave passive provision for it to be added later without difficulty should it be requested.",1383349090,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-25n5vcma7cdemv6yuhj7,task_subcomment,NA
+VisualEditor: Display name of transclusions as a tool-tip when selected,"What would this do when multiple templates (or other transclusions) are used in the scope of one transclusion block, like the succession boxes?",1383282851,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-25n5vcma7cdemv6yuhj7,task_subcomment,NA
+VisualEditor: Double-clicking on an image in the image finder inserts it twice,"If you open up the image finder, identify an image you want and /double/ click on it, the image finder closes and the selected image is inserted twice.
+
+Debian/Iceweasel 17.0.7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374511980,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-hkdfdeny5avjlyz74jqn,task_description,resolved
+VisualEditor: Double-clicking on an image in the image finder inserts it twice,I believe we fixed this yonks ago; sorry for slow response.,1395355791,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hkdfdeny5avjlyz74jqn,task_subcomment,NA
+VisualEditor: Double-clicking on an image in the image finder inserts it twice,Also in Chrome 28/Windows 7.,1374681230,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-hkdfdeny5avjlyz74jqn,task_subcomment,NA
+VisualEditor: Double-clicking on an image in the image finder inserts it twice,"Screenshot
+
+**Attached**: {F11569}",1374512097,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-hkdfdeny5avjlyz74jqn,task_subcomment,NA
+VisualEditor: Note that Wikidata exists in the description text above the read-only language links section in the meta dialog,"In the site settings dialog you can see a list of language/interwiki links for the current article. There is a explanation text saying those can only be edited in the wikitext editor. Because of Wikidata this is now no longer true for most articles. The text should be adapted and maybe link to the corresponding Wikidata item?
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1374504240,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-mztpccwdq5aifemh7iim,task_description,resolved
+VisualEditor: Note that Wikidata exists in the description text above the read-only language links section in the meta dialog,"\o/
+thanks!",1385506631,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-mztpccwdq5aifemh7iim,task_subcomment,NA
+VisualEditor: Note that Wikidata exists in the description text above the read-only language links section in the meta dialog,"Change 97516 merged by jenkins-bot:
+Note language links need to be edited on Wikidata
+
+https://gerrit.wikimedia.org/r/97516",1385506442,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mztpccwdq5aifemh7iim,task_subcomment,NA
+VisualEditor: Note that Wikidata exists in the description text above the read-only language links section in the meta dialog,"Change 97516 had a related patch set uploaded by Jforrester:
+Note language links need to be edited on Wikidata
+
+https://gerrit.wikimedia.org/r/97516",1385392603,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mztpccwdq5aifemh7iim,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","I could only find one major button that leads to the help pages - the one at the top toolbar. Ideally, there should be help buttons in every context - dialog boxes, inspector, plugins, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T53237}",1374488460,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-qeadal5vtjyli2cuuxzk,task_description,open
+"There should be help links in every context - dialog boxes, inspectors, etc.","We disagree with the premise; instead, there should only be help links where they are useful to explain the complexity of a control to the user. Most of this is already done, and the focus areas for this release don't have this level of complexity required. Consequently, we decided to remove this from the Q3 blockers list at the triage meeting on 2015-02-11.",1423879363,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","They are definitely in the i18n system, for example https://meta.wikimedia.org/wiki/MediaWiki:Visualeditor-dialog-meta-categories-defaultsort-help/en",1423690069,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","The relevant documentation about messages (i18n system) appears to include 
+* https://www.mediawiki.org/wiki/Help:System_message
+* https://www.mediawiki.org/wiki/Localisation#Adding_new_messages
+* https://www.mediawiki.org/wiki/Localisation_file_format
+* https://www.mediawiki.org/wiki/Help:System_message#Finding_messages_and_documentation
+
+The last of these says ""How each message is used by MediaWiki, variables available, parameters used, limitations, et cetera is explained with the complete documentation in the qqq pseudo-language files"", with a link to here:
+
+* https://translatewiki.net/w/i.php?title=Special%3ATranslate&task=reviewall&group=core&language=qqq&limit=5000&tux=0
+
+On that page, if I change the Group field to any of the four VisualEditor groups, and then look for the messages that James added to all items related to one VE menu, I can't find those messages. Should I be looking somewhere else, or are the messages not in the i18n system?",1423689769,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",">>! In T53798#1029938, @John_Broughton wrote:
+> * The content of contextual help should be similar to templates: visible to everyone, each on separate page, with a related talk pages, but not necessarily editable by anyone but an admin. What //isn't// needed is some programmer-added contextual help; what is needed is a //system// so that creating and modifying contextual help is done by members of Wikipedia communities. [For example, pages could be named something like this: Help:VisualEditor/ContextHelp///label//, where ""label"" is a unique name for where the contextual help will appear.
+
+MediaWiki already solved this problem long ago with the i18n system and the MediaWiki: system namespace. Either look at the changes made to the i18n/en.json file, or search for the text you want changed, to find out which page in the MediaWiki namespace an admin needs to change. These MediaWiki pages can also have related talk pages.
+
+
+>>! In T53798#1029938, @John_Broughton wrote:
+> * Contextual help should be able to include links - because linking to the relevant section (or anchor point - see WP:EIW, for example) is important when the (relatively short) contextual help isn't sufficient.
+
+I think we could allow that, but we'd need to change OO.ui.FieldLayout to accept HTML for the 'help' configuration, and then make VE-MW parse the help messages.
+",1423651331,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",">>! In T53798#1029938, @John_Broughton wrote:
+> * The content of contextual help should be similar to templates: visible to everyone, each on separate page, with a related talk pages, but not necessarily editable by anyone but an admin. What //isn't// needed is some programmer-added contextual help; what is needed is a //system// so that creating and modifying contextual help is done by members of Wikipedia communities. [For example, pages could be named something like this: Help:VisualEditor/ContextHelp///label//, where ""label"" is a unique name for where the contextual help will appear.
+
+MediaWiki already solved this problem long ago with the i18n system and the MediaWiki: system namespace. Either look at the changes made to the i18n/en.json file, or search for the text you want changed, to find out which page in the MediaWiki namespace an admin needs to change. These MediaWiki pages can also have related talk pages.
+
+
+>>! In T53798#1029938, @John_Broughton wrote:
+> * Contextual help should be able to include links - because linking to the relevant section (or anchor point - see WP:EIW, for example) is important when the (relatively short) contextual help isn't sufficient.
+
+I think we could allow that, but we'd need to change OO.ui.FieldLayout to accept HTML for the 'help' configuration.
+",1423651288,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Those who noticed the contextual help on the meta (page settings) menu - I'm not one of them - apparently didn't think it was worth commenting at WP:VE/F, or its equivalent at mediawiki.org. That may because contextual help was added to the VE menu //least used.// Or because no one was overwhelmed by the wording in the contextual help popups. Or because there was no obvious way to suggest improvements in wording. Regardless of the reasons, the lack of a response should absolutely not be taken to be a polling of the user community.
+
+More generally:
+
+* Contextual help absolutely is needed. The lack of this is one of the major weaknesses of wikitext editing. I don't think user feedback is needed to confirm this need. But if there is any doubt, then I suggest posting this the question (""Should VE menu items have contextual help?) at one or both Feedback pages. 
+* The content of contextual help should be similar to templates: visible to everyone, each on separate page, with a related talk pages, but not necessarily editable by anyone but an admin. What //isn't// needed is some programmer-added contextual help; what is needed is a //system// so that creating and modifying contextual help is done by members of Wikipedia communities. [For example, pages could be named something like this: Help:VisualEditor/ContextHelp///label//, where ""label"" is a unique name for where the contextual help will appear.
+* Contextual help should be able to include links - because linking to the relevant section (or anchor point - see WP:EIW, for example) is important when the (relatively short) contextual help isn't sufficient.",1423633543,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 186108 merged by jenkins-bot:
+MWMediaDialog: Add contextual help for controls
+
+[[https://gerrit.wikimedia.org/r/186108]]",1422488523,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 186108 had a related patch set uploaded (by Jforrester):
+MWMediaDialog: Add contextual help for controls
+
+[[https://gerrit.wikimedia.org/r/186108]]
+
+#patch-for-review",1421798146,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",Did we get any feedback?,1416183267,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","The page settings (""meta"") dialog now has a complete set of contextual help. Will wait for further user feedback before doing the rest of the dialogs.",1410831140,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 160371 merged by jenkins-bot:
+Add contextual help to all remaining meta dialog controls
+
+https://gerrit.wikimedia.org/r/160371",1410831074,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 160371 had a related patch set uploaded by Jforrester:
+Add contextual help to all remaining meta dialog controls
+
+https://gerrit.wikimedia.org/r/160371",1410744289,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 159104 merged by jenkins-bot:
+Provide contextual help for the page settings dialog's controls
+
+https://gerrit.wikimedia.org/r/159104",1410208908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",First one done. We'll seek feedback on this approach and then roll out for the rest of the dialogs.,1410208838,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 159104 had a related patch set uploaded by Alex Monk:
+Provide contextual help for the page settings dialog's controls
+
+https://gerrit.wikimedia.org/r/159104",1410200618,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 159095 merged by jenkins-bot:
+Make help button for FieldLayout frameless again
+
+https://gerrit.wikimedia.org/r/159095",1410199152,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 159095 had a related patch set uploaded by Alex Monk:
+Make help button for FieldLayout frameless again
+
+https://gerrit.wikimedia.org/r/159095",1410199015,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",It looks like some work was done in Gerrit change 147751 and then reverted,1407980699,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","So for adding these to the page settings controls, it should now just be a case of adding the new messages and using them as the config.help for each setting's FieldLayout. James, are you planning to do this?",1405636684,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",So I suppose now the job is to start writing copy…,1405452080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 142468 merged by jenkins-bot:
+Allow FieldLayouts to have help text
+
+https://gerrit.wikimedia.org/r/142468",1405449958,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 142468 had a related patch set uploaded by Alex Monk:
+Allow FieldLayouts to have help text
+
+https://gerrit.wikimedia.org/r/142468",1403828245,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","As a start, maybe add the (?) icon next to each of the page settings controls so we can give some blurb for users? I'm happy to write the copy on the commits. :-)",1402608232,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","**turingt** wrote:
+
+Maybe, the way to make the target page configurable can be creating a fixed redirect page for each link, so that we can change the redirect target.",1378729186,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","At https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=572181319#Inserting_reference there are comments that the instruction manual is too difficult to find, and requests that contextual help be added to the various dialogs. 
+
+These help links should obviously open in a new window/tab, and the target needs to be configurable on wiki as help pages are not static and get split/merged/reorganised over time.",1378729025,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+VisualEditor: TemplateData-provided parameters in list should show description in tooltip,"The description of a parameter in the list of parameters does not always fit in the width of the editing add-parameter box, particularly in firefox (where the font size is apparently larger in than chrome) and when users are using large fonts for accessibility reasons. Where this is the case (or always) the description should be shown in a tooltip on hover or when selected by up/down keyboard prior to insertion.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50354
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51436
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62142",1374419280,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rggykpwnizk34bvpsjp6,task_description,open
+"Broken table, repeated section in diff after VisualEditor edit","I recently ran across [https://en.wikipedia.org/w/index.php?title=Polycarbonate&diff=prev&oldid=564618311 this edit].  It seems as though they were trying to fix a spelling correction and inadvertently destroyed a table and had an entire section get repeated.
+
+There was a little [https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Strange_Diff discussion about the diff on the Visual Editor feedback page], where it was mentioned that the diff ""is very strange and [the commenter didn't] recall seeing anything similar"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374416280,PHID-USER-2qzpsivaeuezrxqtzhwn,PHID-TASK-ing4zbhpdsfypnokceeg,task_description,resolved
+"Broken table, repeated section in diff after VisualEditor edit","This was fixed a very long time ago (around August last year), but I didn't spot this report until just now; my apologies.",1412977739,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ing4zbhpdsfypnokceeg,task_subcomment,NA
+"Broken table, repeated section in diff after VisualEditor edit","The problem is that the table wikitext is buggy there.  It is missing a closing tag (in reality, it is missing a newline break.  |-|} .. See https://en.wikipedia.org/w/index.php?title=Polycarbonate&action=edit&oldid=563700122)
+
+The PHP parser output for this is also broken (see https://en.wikipedia.org/w/index.php?title=Polycarbonate&oldid=563700122#Manufacturers_and_brands and where the table has ended up).
+
+We could improve Parsoid to detect some scenarios like this, but it is currently lower priority.  Fixing the table by adding a line break between ""|-"" and ""|}"" should fix the issue for now.
+
+Sample wikitext snippet for our use later:
+
+{|
+|foo
+|-|}
+abc",1374506456,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ing4zbhpdsfypnokceeg,task_subcomment,NA
+"VisualEditor: Have a ""remove from page"" button in media settings dialog","An English Wikipedia user familiar with the transclusion dialog expected thatthe way to remove an  image from the article was using a remove option in the media dialog. Such an option does not exist, and they couldn't work out another way of removing the image other than selecting and deleting the characters around and including the slug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374362700,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-apnlro5ql64fbmr7qoty,task_description,declined
+"VisualEditor: Have a ""remove from page"" button in media settings dialog",It's (now?) very simple to delete an image by clicking on it and pressing delete. Pushback welcome.,1437787301,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-apnlro5ql64fbmr7qoty,task_subcomment,NA
+sees unreviewed pages despite their ns isn't reviewable,"After https://pl.wikipedia.org/w/index.php?title=Pomoc:VisualEditor/Skr%C3%B3ty_klawiszowe&oldid=37098556&diff=cur this edit it sees unreviewed pages and distinguishes between stable and unreviewed versions despite a) on this page, both versions are autoreviewed b) even if points [[Wikipedia:VisualEditor/Nawigacja]] (transcluded) out as pending rewiev - the project namespace is not reviewable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374328320,PHID-USER-gf5juv3z3p75bykrcrhf,PHID-TASK-npzavnntwnz6xylar7kw,task_description,open
+VisualEditor: Set correct text annotation buttons for ka (მ/კ),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4uk2cqp2bkhf3so3ifse,task_description,resolved
+VisualEditor: Set correct text annotation buttons for ka (მ/კ),Done and will be deployed tomorrow.,1374633775,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4uk2cqp2bkhf3so3ifse,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ka (მ/კ),"Change 74979 merged by jenkins-bot:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374632702,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4uk2cqp2bkhf3so3ifse,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ka (მ/კ),"Change 74979 had a related patch set uploaded by Esanders:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374428015,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4uk2cqp2bkhf3so3ifse,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for os (Б/???),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jfjnga5p64vzxczhpota,task_description,resolved
+VisualEditor: Set correct text annotation buttons for os (Б/???),Done and will be deployed tomorrow.,1374633751,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jfjnga5p64vzxczhpota,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for os (Б/???),"Change 74979 merged by jenkins-bot:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374632700,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jfjnga5p64vzxczhpota,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for os (Б/???),"Change 74979 had a related patch set uploaded by Esanders:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374428013,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jfjnga5p64vzxczhpota,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ru/ky (Ж/K),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ateveyfcbqb3i4wfvvxx,task_description,resolved
+VisualEditor: Set correct text annotation buttons for ru/ky (Ж/K),Done and will be deployed tomorrow.,1374633741,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ateveyfcbqb3i4wfvvxx,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ru/ky (Ж/K),"Change 74979 merged by jenkins-bot:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374632698,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ateveyfcbqb3i4wfvvxx,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ru/ky (Ж/K),"Change 74979 had a related patch set uploaded by Esanders:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374428011,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ateveyfcbqb3i4wfvvxx,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for nl (V/C),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hlwmurrr6a42vwsh4edb,task_description,resolved
+VisualEditor: Set correct text annotation buttons for nl (V/C),Done and will be deployed tomorrow.,1374634218,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hlwmurrr6a42vwsh4edb,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for nl (V/C),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632635,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlwmurrr6a42vwsh4edb,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for nl (V/C),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412448,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hlwmurrr6a42vwsh4edb,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for eu (L/E),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-52xvekcadppljx7wxtjw,task_description,resolved
+VisualEditor: Set correct text annotation buttons for eu (L/E),Done and will be deployed tomorrow.,1374633960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-52xvekcadppljx7wxtjw,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for eu (L/E),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632633,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-52xvekcadppljx7wxtjw,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for eu (L/E),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412437,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-52xvekcadppljx7wxtjw,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for es (N/C),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ztoidsuy5fwdvtm6hoxa,task_description,resolved
+VisualEditor: Set correct text annotation buttons for es (N/C),Done and will be deployed tomorrow.,1374633947,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ztoidsuy5fwdvtm6hoxa,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for es (N/C),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632626,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ztoidsuy5fwdvtm6hoxa,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for es (N/C),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412439,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ztoidsuy5fwdvtm6hoxa,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for pt (N/I),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-evgaeiyun2bs3jdkzmuq,task_description,resolved
+VisualEditor: Set correct text annotation buttons for pt (N/I),Done and will be deployed tomorrow.,1374633901,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-evgaeiyun2bs3jdkzmuq,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for pt (N/I),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632624,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-evgaeiyun2bs3jdkzmuq,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for pt (N/I),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412443,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-evgaeiyun2bs3jdkzmuq,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for gl (N/C),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-64zcrx2xmqdtz5ns3ivt,task_description,resolved
+VisualEditor: Set correct text annotation buttons for gl (N/C),Done and will be deployed tomorrow.,1374633878,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-64zcrx2xmqdtz5ns3ivt,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for gl (N/C),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632631,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-64zcrx2xmqdtz5ns3ivt,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for gl (N/C),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412445,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-64zcrx2xmqdtz5ns3ivt,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for it (G/C),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ganyn24uk5sn6pp36vou,task_description,resolved
+VisualEditor: Set correct text annotation buttons for it (G/C),Done and will be deployed tomorrow.,1374633829,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ganyn24uk5sn6pp36vou,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for it (G/C),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632629,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ganyn24uk5sn6pp36vou,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for it (G/C),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412452,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ganyn24uk5sn6pp36vou,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for fr (G/I),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-buz4r3nu6zcrowjeto7w,task_description,resolved
+VisualEditor: Set correct text annotation buttons for fr (G/I),Done and will be deployed tomorrow.,1374633813,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-buz4r3nu6zcrowjeto7w,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for fr (G/I),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632620,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-buz4r3nu6zcrowjeto7w,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for fr (G/I),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412454,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-buz4r3nu6zcrowjeto7w,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for hu (B/D),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4e4lr7gjx3fhin7zieit,task_description,resolved
+VisualEditor: Set correct text annotation buttons for hu (B/D),Done and will be deployed tomorrow.,1374633800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4e4lr7gjx3fhin7zieit,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for hu (B/D),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632622,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4e4lr7gjx3fhin7zieit,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for hu (B/D),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412441,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4e4lr7gjx3fhin7zieit,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","At the moment wikimarkup being entered into the VE triggers a notice warning the user that it won't work - this notice then has to be actively dismissed. It'd be nice if, should the user remove the problematic markup, the notice would vanish.
+
+I'm popping this in as a low-priority enhancement: I appreciate the VE team has active breakage to focus on.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52386
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70168",1374265800,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_description,resolved
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","That area of code could do with some rethinking, but this is basically done.",1391815339,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","Change 110295 merged by jenkins-bot:
+Hide wikitext warning notification when the user removes the markup
+
+https://gerrit.wikimedia.org/r/110295",1391813698,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","Change 110295 had a related patch set uploaded by Alex Monk:
+Hide wikitext warning notification when the user removes the markup
+
+https://gerrit.wikimedia.org/r/110295",1391045818,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","(In reply to comment #3)
+> There's an issue with this though, in that the popup hovers over the 'Save
+> page' button so I couldn't actually click 'Save page' very easily. It wasn't
+> at
+> all clear to me that clicking anywhere on the popup would close it.
+
+You aren't the first person to say that - see bug 52386",1380727372,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","(In reply to comment #2)
+> The popup should also be closed automatically after the ""save page"" button
+> has
+> been pressed. At that point it's clear that the user is not going to remove
+> any
+> markup that still remains (for whatever reason) so the notice serves no other
+> purpose and just gets in the way of the edit summary dialog.
+
+There's an issue with this though, in that the popup hovers over the 'Save page' button so I couldn't actually click 'Save page' very easily. It wasn't at all clear to me that clicking anywhere on the popup would close it.",1380724444,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","The popup should also be closed automatically after the ""save page"" button has been pressed. At that point it's clear that the user is not going to remove any markup that still remains (for whatever reason) so the notice serves no other purpose and just gets in the way of the edit summary dialog.",1375812069,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup",%%%*** Bug 52155 has been marked as a duplicate of this bug. ***%%%,1375381691,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+VisualEditor: Move-dragging a media item shows the copy cursor on Mac/Safari,"If I move an image around, I see the ""copy"" cursor, even though I'm just moving.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374262740,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ujehggdfeqiirechz6c2,task_description,resolved
+VisualEditor: Move-dragging a media item shows the copy cursor on Mac/Safari,"Created attachment 13903
+cursor image
+
+Oh, the screenshot doesn't show the cursor, but I added an example image of the cursor type instead.
+
+Safari Mac Version 7.0 (9537.71) just dragging around a thumbnailed image throughout the text shows this problem for me. It changes from the move cursor to the copy cursor.
+
+**Attached**: {F11318}",1385421258,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ujehggdfeqiirechz6c2,task_subcomment,NA
+VisualEditor: Move-dragging a media item shows the copy cursor on Mac/Safari,"Nope, I still see this problem. Initially it's the move cursor, but as soon as i move the cursor somewhere between the lines, i get the copy cursor.
+
+Screenshot attached.",1385420891,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ujehggdfeqiirechz6c2,task_subcomment,NA
+VisualEditor: Move-dragging a media item shows the copy cursor on Mac/Safari,The cursor I get in Safari (the same as in Firefox and Chrome) is the move cursor (a four-pointed cross). Marking as WORKSFORME. Possibly a config issue with your system?,1385387607,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ujehggdfeqiirechz6c2,task_subcomment,NA
+VisualEditor: Section edit links don't work like wikitext where the section is transcluded from elsewhere,"http://it.wikipedia.org/wiki/Template:Cassetto is AFAIK the Italian version of Hidden (it shouldn't be used in articles).
+
+http://it.wikipedia.org/wiki/Utente:Superchilum features a cassetto named Tudù which transcludes the subpage Utente:Superchilum/do.
+
+If you try and edit the first section in that cassetto, Varie, with the classic editor, you correctly manage to edit the /do subpage; VE instead only allows editing the main userpage.
+
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374231000,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-wcreo2gxsoyscsxloyxc,task_description,resolved
+VisualEditor: Section edit links don't work like wikitext where the section is transcluded from elsewhere,"The example page linked here no longer has any section edit links on it, so I can't test this exact case, but I believe we fixed this issue in 2017 with {b7dd6077b8cab3740cb84b5c003ad272ff09ab8f} (related to T153176).",1663955476,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wcreo2gxsoyscsxloyxc,task_subcomment,NA
+Editing window does not scroll when dragging,"When dragging an item in the visual editor (tested with image and text), the editing window does not scroll up or down when you reach the top or bottom of the window. This means you have to make several consecutive drag and drop actions to move an item within a long article/section. Per Bug 51665 the image must be separately selected before you are able to drag it (i.e. each movement requires two mouse clicks).
+
+**See Also**:
+{T36307}
+{T75240}",1374226320,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_description,open
+Editing window does not scroll when dragging,"I tested moving an image again today, and this is the result on my Air Os X in https://en.wikipedia.org/wiki/Victor_Diaz_Lamich?veaction=edit, using the trackpad.
+In Chrome, maximized window, using Lamich’s plane pic:
+*I click on it and drag it down to put it at the bottom of the article, a green “+"" icon appears to guide me (good!). Nothing happens if I hover my pointer around the bottom of the page; down arrow does nothing; the side scrollbar doesn’t appear.
+*The two-fingers scroll gesture does work when the pointer is on the side scrollbar, so I manage to put the pic at the bottom of the article.
+*Now trying to put it back where it was, so I click and drag it again. Nothing happens if I hover around the top of the page or hit the up arrow, but the page does scroll if instead I move the pointer /on/ the toolbar (scroll gesture while on the side scrollbar also works). There may be a problem with the focus though, but at least the pic is where I want it to be.
+
+In Safari, maximized window, using the same pic:
+*Dragging the pic doesn’t show the green + icon, but a line instead. Dragging it toward the bottom of the screen achieves nothing. 
+*The two-fingers scroll gesture works on the entire surface of the page, and it’s the only way to get to the bottom of the page, and then on the top again. Hovering on the toolbar while dragging accomplishes nothing in Safari; it shows the green + icon though, in the area of the tab name.
+*Dragging and pressing the up and down arrows doesn’t seem to work. In the rare cases when it does, both the up and the down keys will actually move the pic toward the top of the page, one line at the time (holding the key never works in my experience).
+ ",1430228132,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"Yes, OS X 10.9.5 Chrome and Windows 7 with IE 11- objects cannot be dragged beyond the bottom or the top of the page - the page does not scroll up. In IE 11, sometimes it's possible to drag beyond the bottom of a page but never beyond the top of editing area. ",1419959778,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,I'm on OS X 10.10.1 (14B25) with Chrome 40.0.2214.45 beta (64-bit) and the issue is present. ,1419920556,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,This appears to be OS-specific.  I do not have this problem (either scrolling up or down) on Mac OS 10.8.5; I know that at least two editors have this problem on Windows 8.,1419882579,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"So I'm not sure I'm adding to the right bug, but I don't seem to be able to drag templates or images beyond the bottom of the window (and even beyond the top when I tested this the other way around) with the mouse.
+I tried this in https://de.wikipedia.org/wiki/Benutzer:Elitre_%28WMF%29/sandbox with Chrome and Firefox.",1416241422,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"Just tested this, I can scroll up, with some difficulty ( by positioning the cursor on the top toolbar), but scrolling down does not seem possible. 
+
+Additionally, in most drag and drop interfaces I can be dragging and use a two finger, gesture based scroll while dragging, this does not work on VE (Chrome Version 39.0.2171.52 beta (64-bit) / OS X 10.10 )",1415828928,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,This was fixed over the Summer.,1415807780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"I found this a problem to. When additing using just a touchpad or not having a scroll option on the mouse, you have a difficulties to move and object.",1407176990,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,*** Bug 63170 has been marked as a duplicate of this bug. ***,1404761224,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"Problem encounter at FF 24.0 Windows Vista. As I cant add a template, per this bug:
+http://imgbin.org/index.php?page=image&id=15296
+
+I have to use the method of placing the template on the top and scroll down. Thus this behaviour is blocking me in activity in VE.",1381053810,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"(In reply to comment #4)
+> the ""challenge"" was to get
+> the ""language"" template back at the bottom of the page. You can't do this by
+> dragging, even if you stay in the same window.
+
+I think I know what you mean and I have filed a report about it at Bug 54756. Good catch! Thank you.
+
+Also, setting the priority back to Normal since this is usually decided by the developer or team working on a specific report. Thank you for your understanding.",1380428104,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"**Wikifram** wrote:
+
+While the above is correct insofar that dragging beyond the page boundaries doesn't work (apparently not an urgent problem?), the ""challenge"" was to get the ""language"" template back at the bottom of the page. You can't do this by dragging, even if you stay in the same window. You can use some unintuitive workarounds (which you can find for yourselves), but the basic functionality doesn't work, just like most of the basic functionality of MW 1.22wmf19. has anyone tested ''anything'' in this release related to VE? Anything at all? Since it was ""very"" easy to find many problems with it in half an hour of testing. Back to the drawing boards please.",1380382559,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"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 
+
+The users poses ""a challenge"" consisting in dragging the <languages /> bar at [[mw:Groups]] from the bottom of the page to the top, which implies dragging.
+
+A more probable use case it to move pictures from one section to another.",1380324332,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,Confirmed that this also occurs on Firefox 22 and Chrome 28 on Windows 7,1374228554,PHID-USER-ohetl546bwt5ac2szu5w,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,Forgot to note this is on Firefox 22 on Xubuntu Linux,1374226368,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near","If you want to move an image to the start of a section in Visual Editor the logical course of action is to drag it to before the first character of the first word of the section.
+
+A user of Firefox 21 reports this does not work at all, in my testing in Firefox 22 it appears to work only occasionally.
+
+The counter-intuitive dragging the image to after the last character of the section title does work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54756
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65883",1374225180,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-32x2jdddgorx6i4qqszg,task_description,resolved
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near","Change 139674 merged by jenkins-bot:
+Block item drag and drop
+
+https://gerrit.wikimedia.org/r/139674",1403049871,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near",*** Bug 51292 has been marked as a duplicate of this bug. ***,1403005130,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near","Change 139674 had a related patch set uploaded by Esanders:
+Block item drag and drop
+
+https://gerrit.wikimedia.org/r/139674",1402926269,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near",*** Bug 54756 has been marked as a duplicate of this bug. ***,1381246558,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near","I'm a little confused as to what the request is here - do you feel that VisualEditor should, when dragging, magically create (and destroy) places to put the cursor, so you can drag content there? Assuming this, I've re-titled, but please correct if I've misunderstood.
+
+We've deliberately decided against that in the past as a confusing behaviour, hence why there are all the extra blank lines (""slugs"") for the ""possible place you could put the cursor which aren't actually there"" concept.
+
+We could do this, but I'm not sure. Also, it adds behaviour that is possible using a mouse but not the keyboard (dragging is not done in the keyboard, instead cut/paste is), which is a little uncomfortable given the intent of VisualEditor.
+
+We've considered adding an ""outline mode"" which would have all the slugs shown, possibly including these ones, and an ""editor mode"" where no slugs at all would show, which could be one alternative to this request.",1381246309,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near",There is a similar problem when you try to drag elements to the end of the editable content area - see Bug 54756.,1380428336,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"A user on English Wikipedia requests that templates such as navigation boxes that display as collapsed by default when viewing should display as collapsed by default when editing.
+
+""Currently, navigation boxes are always uncollapsed when editing. This can be quite annoying when having to deal with big ones like {{The Beatles}}, e.g. on ""I'm a Loser"", also it might be confusing editors into believing that this part of a page can easily be edited.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374223320,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_description,open
+VisualEditor: Surface should respect the default state of collapseable templates,"And worse, they are often 'autocollapse' which means they won't benefit from this. I am going to propose a change on en.wp soon, to limit the usage of autocollapse to ONLY navboxes, so at least other parts of the pages will not have this problem. But i'm not sure how to get social buy-in for completely removing autocollapse behaviour of navboxes.",1526025290,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"Navboxes and probably almost everything else still use `class=""collapsible""`…",1525985062,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,">>! In T53664#4198427, @matmarex wrote:
+> This should now magically work for elements made collapsible using `class=""mw-collapsible""`, as a result of 8cdfcc5fd4b, which refactored that code to hide them using only CSS. 
+
+Does that make this fixed, or are there elements we'd want to support which use a different class/mechanism?",1525983346,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"This should now magically work for elements made collapsible using `class=""mw-collapsible""`, as a result of 8cdfcc5fd4b, which refactored that code to hide them using only CSS. ",1525981957,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"Created attachment 13417
+Related render problems
+
+This is a related problem, which would not be noticable if it was not for this bug.
+
+https://en.wikipedia.org/w/index.php?title=Anarchism&veaction=edit
+
+When in normal view mode (not VE), expand all of those sidebars
+A large area of whitespace opens up above ""Internal issues and debates"", and the images appear there.
+
+In the VE, that whitespace is filled with text, which causes the images to be pushed further down in the content, eventually slipping into the References section, and on Firefox the images even overlaps the References section.
+
+I haven't investigated what is causing the VE vs non-VE rendering differences, but collapse is clearly the reason this rendering difference is a significant problem that all VE users face, rather than a minor glitch that only appears when the user is silly enough to alter all sidebars to be expanded.
+
+**Attached**: {F11253}",1380600089,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"(In reply to comment #1)
+> First of all, this requires fixes for bug 51565 to be deployed, and then we
+> need to fix the NavFrame and CollapsibleTable scripts in
+> en:wp:MediaWiki:Common.js to use the same hooks.
+
+That change has been made on enwp by TheDJ/hartman (cc'd)
+
+https://en.wikipedia.org/w/index.php?title=MediaWiki:Common.js&diff=570114240&oldid=569893356
+
+The templates are yet not collapsing; is there more development needed in VE product or in Common.js ?
+
+I think 'collapse' need more special handling in VE (possibly even in parsoid); in order to be WYSIWYG.
+1. The user can change the collapse state of templates in the VE dialog editor, and that change should be reflected in the VE after the changes are applied.
+2. The user should be able to collapse and uncollapse a collapse-able template in order 
+2.1 to visualise how the page will look in each mode
+2.2 hide/unhide collapse-able templates that are consuming precious screen real estate (this should be a separate enhancement)
+
+Perhaps this feature should be dependent on bug 30352.",1380598815,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"First of all, this requires fixes for bug 51565 to be deployed, and then we need to fix the NavFrame and CollapsibleTable scripts in en:wp:MediaWiki:Common.js to use the same hooks.",1374261760,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,,1374158760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tv63msunrr34jh3gj3an,task_description,resolved
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529488, @Danny_B wrote:
+>>>! In T53613#2529467, @Jdforrester-WMF wrote:
+>> Actually, VE will have one until it's banned in wikitext, not just ""not easily accessible"".
+> 
+> So ban it then. The request for it has been around for ages.
+
+At the bare minimum you'll need to run a three-month-long community RfC on meta with convincing arguments that explain as to why they all need to replace `<big>` with `<span style=""font-size: bigger;"">` and so on. There are, from a quick search, over 70k pages with at least one of these on the English Wikipedia alone; the transition will be quite a lot of work.
+
+It's not remotely worth it to spend that much in terms of WMF resources. If you want to try, you're welcome, but I seriously doubt you'll get sufficient consensus (and even then it'd probably need to be a configuration option so that third party wikis can address the breaking change in slower time).
+
+Not of this is germane to this ticket, however.",1470435796,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529467, @Jdforrester-WMF wrote:
+> Actually, VE will have one until it's banned in wikitext, not just ""not easily accessible"".
+
+So ban it then. The request for it has been around for ages. Not even speaking that it has been deprecated ages ago even in XHTML we used before, and it is obsolete in HTML5.",1470435420,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529467, @Jdforrester-WMF wrote:
+> Actually, VE will have one until it's banned in wikitext, not just ""not easily accessible"".
+
+So ban it then. The request for it has been around for ages.",1470435319,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529443, @matmarex wrote:
+> ""WT"" is VisualEditor team's jargon for ""wikitext"". Wikitext editor's toolbar has buttons for this: {F4339790}
+> 
+> I'll note that there's a task to remove them: T40487. You could probably file a similar one for VisualEditor. But as long as one has them, the other should too.
+
+Thanks for explanation.
+
+So why instead of adding it to Visual Editor not removing it from WikiEditor then (which should be obviously easier)?",1470435100,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529443, @matmarex wrote:
+> ""WT"" is VisualEditor team's jargon for ""wikitext"".
+
+Correct (though we didn't invent it).
+
+> Wikitext editor's toolbar has buttons for this: {F4339790}
+> 
+> I'll note that there's a task to remove them: T40487. You could probably file a similar one for VisualEditor. But as long as one has them, the other should too.
+
+Actually, VE will have one until it's banned in wikitext, not just ""not easily accessible"".",1470434945,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"""WT"" is VisualEditor team's jargon for ""wikitext"". Wikitext editor's toolbar has buttons for this: {F4339790}
+
+I'll note that there's a task to remove them: T40487. You could probably file a similar one for VisualEditor. But as long as one has them, the other should too.",1470434546,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"What does WT stand for?
+
+What do you call feature-parity in this case?",1470432701,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2528664, @Danny_B wrote:
+> We have headers and table captions providing semantically correct way how to emphasize headlining text. What is the use case of using big text elsewhere?
+
+Off-topic. VE and WT are designed to have feature-parity. If you think we should ban users from using these, file a task.",1470432011,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,We have headers and table captions providing semantically correct way how to emphasize headlining text. What is the use case of using big text elsewhere?,1470426148,PHID-USER-xqqqgn2dels45flxw5kb,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"Change 141617 merged by jenkins-bot:
+Provide tools to make text bigger or smaller
+
+[[https://gerrit.wikimedia.org/r/141617]]",1470421624,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"Change 141617 had a related patch set uploaded (by Jforrester):
+Provide tools to make text bigger or smaller
+
+[[https://gerrit.wikimedia.org/r/141617]]
+",1469233591,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"Change 141617 had a related patch set uploaded by Jforrester:
+Provide tools to make text bigger or smaller
+
+https://gerrit.wikimedia.org/r/141617",1403574866,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as subscript,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374158700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f6ao6kmtchv7v27bft42,task_description,resolved
+VisualEditor: Tool to set/unset text as subscript,Now merged into master; will be deployed (as experimental) in the next push (so will be available on MediaWiki.org) - we will make this available to production wikis next week when we re-work the toolbar.,1376619792,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f6ao6kmtchv7v27bft42,task_subcomment,NA
+VisualEditor: Tool to set/unset text as subscript,"Change 78495 merged by jenkins-bot:
+Create a subscript tool
+
+https://gerrit.wikimedia.org/r/78495",1376619387,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f6ao6kmtchv7v27bft42,task_subcomment,NA
+VisualEditor: Tool to set/unset text as subscript,"Change 78495 had a related patch set uploaded by Steven Zhang:
+Add subscript tool
+
+https://gerrit.wikimedia.org/r/78495",1376120249,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-f6ao6kmtchv7v27bft42,task_subcomment,NA
+VisualEditor: Tool to set/unset text as subscript,"An editor at en.wp has noted that subscript is requried to be able to correctly edit some articles, ""ECG leads, e.g. V4"" was the example given.",1374927410,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-f6ao6kmtchv7v27bft42,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374158700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdzse5grzzixnnifzj2z,task_description,resolved
+VisualEditor: Tool to set/unset text as superscript,Now merged into master; will be deployed (as experimental) in the next push (so will be available on MediaWiki.org) - we will make this available to production wikis next week when we re-work the toolbar.,1376619787,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"Change 78490 merged by jenkins-bot:
+Create a superscript tool
+
+https://gerrit.wikimedia.org/r/78490",1376619344,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"Change 78490 had a related patch set uploaded by Steven Zhang:
+Add a superscript tool
+
+https://gerrit.wikimedia.org/r/78490",1376116614,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"As explained elsewhere, this is trivial to do but would make the toolbar (even more) unwieldy for all users, and so I de-prioritised it whilst waiting for a way to have lots of these icons available without filling everyone's screens with buttons most of them don't want to touch.
+
+We're working right now on a first draft which we think will help with the clutter, at which point making these tools is a work of minutes.",1375304078,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"A user at en.wp has noted the lack of a tool to set superscript means that the article [[Spiral Dynamics]] cannot be completely edited in VE.
+
+The ability to set superscript and subscript are essential features for writing about many articles in the science, maths and technology fields, so it should be a core competence of the VisualEditor rather than a low-priority enhancement.",1375263490,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as strikethrough,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374158700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ascdutdvqb4aq6opfuse,task_description,resolved
+VisualEditor: Tool to set/unset text as strikethrough,Done by Peter C. at Wikimania 2013 Hacking Days. Yay.,1375865291,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ascdutdvqb4aq6opfuse,task_subcomment,NA
+VisualEditor: Tool to set/unset text as strikethrough,"Change 78019 merged by jenkins-bot:
+Create strikethrough text style button
+
+https://gerrit.wikimedia.org/r/78019",1375865057,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ascdutdvqb4aq6opfuse,task_subcomment,NA
+VisualEditor: Tool to set/unset text as strikethrough,"Change 78019 had a related patch set uploaded by Peter.C:
+Create strikethrough text style button
+
+https://gerrit.wikimedia.org/r/78019",1375863283,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ascdutdvqb4aq6opfuse,task_subcomment,NA
+VisualEditor: Tool to set/unset text as underlined,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374158700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dwpuhdlnvzi2y7re3asf,task_description,resolved
+VisualEditor: Tool to set/unset text as underlined,Now merged into master; will be deployed (as experimental) in the next push (so will be available on MediaWiki.org) - we will make this available to production wikis next week when we re-work the toolbar.,1376619782,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dwpuhdlnvzi2y7re3asf,task_subcomment,NA
+VisualEditor: Tool to set/unset text as underlined,"Change 78488 merged by jenkins-bot:
+Create an underline tool
+
+https://gerrit.wikimedia.org/r/78488",1376619184,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dwpuhdlnvzi2y7re3asf,task_subcomment,NA
+VisualEditor: Tool to set/unset text as underlined,"Change 78488 had a related patch set uploaded by Steven Zhang:
+Create an underline tool
+
+https://gerrit.wikimedia.org/r/78488",1376114307,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dwpuhdlnvzi2y7re3asf,task_subcomment,NA
+"VisualEditor: Show two editing/view source tabs at all times, even if you can't edit page because it's protected","When viewing an article you have permission to edit, you see two tabs at the top - ""Edit"" and ""Edit source"". When viewing an article you don't have permission to edit, you see only one - ""view source"".
+
+This is not good UI design There needs to always be the same number of tabs displayed. Ideally there should be tabs to ""view source"" and ""view visual source"" (with better wording though!), see Bug 51547.
+
+If a read-only editor is not possible or not available then that tab needs to pop up a message saying that editing is restricted currently/until xx:xx for <log entry> and that they can view the wikitext source if they want (linked to an explanation what that means).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374077880,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-qh3lrsa2vheyfhks3klm,task_description,declined
+"VisualEditor: Show two editing/view source tabs at all times, even if you can't edit page because it's protected","Comment... I think it might be useful to have the suggested ""view visual source"" tab, primarily to enable copying content such as references between protected and non-protected articles. However, I do grok the additional layers of complexity this would entail...",1427495377,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-qh3lrsa2vheyfhks3klm,task_subcomment,NA
+"VisualEditor: Show two editing/view source tabs at all times, even if you can't edit page because it's protected","A ""read-only editor"" is the view mode… I'm not really sure there's much value in going down the route, but instead we'd want to combine the two edit tabs together (except for users with VisualEditor disabled).",1385386552,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qh3lrsa2vheyfhks3klm,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","There should be a view-source equivalent for the visual editor so that people can see the page in VE as if the could edit it. It should allow them to interrogate things like template, so they can find out which template is producing what they see and how it does that. ~~When VE can cope with copy+paste, then~~ this will also allow them to copy and paste the relevant image/template/whatever to whatever article they are working on.
+
+**See Also**:
+* T54004
+* T54091",1374077700,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_description,resolved
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages",">>! In T53547#4983051, @matmarex wrote:
+>>>! In T53547#4977960, @Schnark wrote:
+>>> Additionally, if the user has NWE enabled, the old wikitext editor is still used for protected pages (but NWE loads after switching to visual and back).
+>> And if the user doesn't have NWE enabled, switching back to wikitext gives an error: ""Error loading data from server: readonly.""
+> This doesn't happen for me locally, only on Beta, which has been stuck in readonly mode for two weeks now.
+
+My comment was wrong anyway, as I actually did have NWE enabled. But whatever, switching now works on Beta as expected, both with NWE and without.",1551172044,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages",">>! In T53547#4977960, @Schnark wrote:
+>> Additionally, if the user has NWE enabled, the old wikitext editor is still used for protected pages (but NWE loads after switching to visual and back).
+> And if the user doesn't have NWE enabled, switching back to wikitext gives an error: ""Error loading data from server: readonly.""
+This doesn't happen for me locally, only on Beta, which has been stuck in readonly mode for two weeks now.",1551137528,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages",">>! In T53547#4977107, @matmarex wrote:
+> You can only access it by switching from old wikitext editor
+Or  by using `veaction=edit`.
+
+> Additionally, if the user has NWE enabled, the old wikitext editor is still used for protected pages (but NWE loads after switching to visual and back).
+And if the user doesn't have NWE enabled, switching back to wikitext gives an error: ""Error loading data from server: readonly.""",1550913707,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","Read-only VE is now available, but rather sneaky. You can only access it by switching from old wikitext editor:
+
+{F28266181}
+
+I think we should consider some more obvious ways to access it. Should we have another tab for it, called ""View in editor"" or something?
+
+Additionally, if the user has NWE enabled, the old wikitext editor is still used for protected pages (but NWE loads after switching to visual and back).
+
+----
+
+After we settle on this, we should probably brag about this in Tech News (#user-notice). Something like ""You can now open the visual editor in read-only mode on protected pages to see how they are made or copy citations to other pages"".",1550868857,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","Change 489416 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Load VE in read-only mode on protected pages
+
+[[https://gerrit.wikimedia.org/r/489416]]",1550868092,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","Change 489416 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Load VE in read-only mode on protected pages
+
+[[https://gerrit.wikimedia.org/r/489416]]",1549749958,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","The ability to load VE at all on protected pages was removed in https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VisualEditor/+/350471/. As a result you can only open the wikitext view source page.
+
+Ideally you would be able to open VE in read-only mode as this bug describes.",1542299795,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","(In reply to comment #0)
+> There should be a view-source equivalent for the visual editor so that people
+> can see the page in VE as if the could edit it.
+
+This could get quite complex, but do-able if it's worth it.
+
+> It should allow them to interrogate things like template, so they can find out
+> which template is producing what they see and how it does that.
+
+I can sort-of see the value here, but it's not great.
+
+> When VE can cope with copy+paste, then this will also allow them to copy and
+> paste the relevant image/template/whatever to whatever article they are working
+> on.
+
+We're probably going to want to do this with ""read mode"" HTML rather than build something like that (so, you copy something from the action=read and paste into veaction=edit and you get the template/etc. magically working).
+
+Marking as ""low"" priority given difficulty and relatively low value for users; happy to be convinced otherwise.",1375300513,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","I had OpenODBC's iODBC plugin installed in Safari (latest release, always). After any edit, EMBED tags would be inserted at the top and bottom of the article. This did not occur with the source editor, or any other editable widget, like this one I'm typing in now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51423",1374057480,PHID-USER-5tluooawvjfhtqywnxag,PHID-TASK-h64w6lawxsfffv5qe4yw,task_description,resolved
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114000,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113106,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page",Can't see a link to a bug filed upstream -> rm upstream keyword,1400336197,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","(In reply to PiRSquared17 from comment #10)
+> This is now assigned to James Forrester.
+
+No it isn't. Above line clearly says:
+
+Assigned To: 	 VE team bugs – take if you're interested!",1395876859,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page",This is now assigned to James Forrester. Will a special test for this specific text be added? What can be done to fix this bug? Seems more like an upstream issue IMHO.,1395865021,PHID-USER-omdcggvudfkuawipp23i,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","PiRSquared17 is right. This is not VE's fault. It only occurs in VE because of the way it sets up the editing area, which your plugin doesn't recognise as not to touch.
+
+No and no.",1375284998,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","""This is not VE's fault.""
+
+I am not at all certain of this. This problem ONLY occurs in VE. It does not occur in the source editor, or any other text editor across the whole wide web.
+
+Something in VE is triggering this plugin to insert code. The plugin and the code it's inserting, is perfectly valid.",1375274462,PHID-USER-5tluooawvjfhtqywnxag,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page",You could write an AbuseFilter to prevent edits like this. This is not VE's fault. There is a problem with the extension. Has anyone notified the author of said extension?,1375240617,PHID-USER-omdcggvudfkuawipp23i,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","(In reply to comment #5)
+> From my understanding, using this bug targetedly it is possible for Browser
+> Add-Ons to insert malicious code in Wikipedia pages. The Wikipedia user will
+> not even notice. I put importance to ""immediate"", in case I'm wrong please
+> undo
+> my change.
+
+embed is not one of the allowed html tags when $wgRawHtml is disabled, so the embed tag is escaped as a security measure.  No malicious injection is possible via this bug.
+
+The now archived discussion is
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29/Archive_114#Is_this_me_or_the_editor.3F
+
+Examples:
+https://en.wikipedia.org/w/index.php?title=The_Road_%282009_film%29&diff=prev&oldid=563739949
+https://en.wikipedia.org/w/index.php?title=The_Road_%282009_film%29&diff=prev&oldid=564586766
+https://en.wikipedia.org/w/index.php?title=Informix_Wingz&diff=prev&oldid=564587579",1375131440,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","**wikipedia** wrote:
+
+From my understanding, using this bug targetedly it is possible for Browser Add-Ons to insert malicious code in Wikipedia pages. The Wikipedia user will not even notice. I put importance to ""immediate"", in case I'm wrong please undo my change.",1375128154,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","It is adding
+<embed type=""application/iodbc"" width=""0"" height=""0"" />",1374448472,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page",Have you reported it to the author yet?,1374165651,PHID-USER-omdcggvudfkuawipp23i,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","Actually my post over on the Village Pump *appears* to have turned up several other examples of plugins having the same problem. Not much more I can add though...
+
+http://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)
+
+Look for ""Is this me or the editor?"" (I can't get the section link to work)",1374086422,PHID-USER-5tluooawvjfhtqywnxag,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","Have you reported this upstream (i.e., to the author of the extension)? I don't this it's VE's fault, although I've seen similar stuff with another extension (FoxLingo):
+[[m:en:Wikipedia:VisualEditor/Feedback/Archive_2013_07#Inserting_weird_script_tag_stuff]].
+
+Actually, might be a more general bug, as these diffs have many similarities. I wonder if any other browser extensions do this.",1374078408,PHID-USER-omdcggvudfkuawipp23i,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+Rewrite VisualEditor's converter to be bottom-up,"The data->DOM converter should construct its DOM bottom-up, the way https://gerrit.wikimedia.org/r/74058 already does for annotations. This would enable us to do some cool things like:
+
+* Pass childDomElements to nodes and meta items (already done for annotations)
+* Pass data content in addition to DOM content?
+* Allow nodes and meta items to unwrap themselves by returning an empty array (already done for annotations)
+** We could implement unwrapping of generated wrapper paragraphs using this feature
+* Possibly change the API so that instead of returning an array of DOM elements, the toDomElements function is responsible for appending its children.
+** This could replace handlesOwnChildren, and enable model types with complex output
+
+For DOM->data it's not as straightforward. We could experiment with bottom-up (outside-in, really) building there too, but it would be a bit less clear how things would work, and whether the copying involved would affect performance (although I believe we may already do a fair bit of copying around as it is).
+
+
+This may be my pet project for my flight to Wikimania, or I may end up doing this sooner if there's time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374029040,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bevtevpkvtmwwlk2gved,task_description,open
+Rewrite VisualEditor's converter to be bottom-up,Ping on this bug.,1402554326,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bevtevpkvtmwwlk2gved,task_subcomment,NA
+Rewrite VisualEditor's converter to be bottom-up,"(In reply to comment #0)
+> * Possibly change the API so that instead of returning an array of DOM
+> elements, the toDomElements function is responsible for appending its
+> children.
+> ** This could replace handlesOwnChildren, and enable model types with complex
+> output
+> 
+This would also enable partial unwrapping of annotations, e.g. <p><a> Foo </a></p> -> <p> <a>Foo</a> </p>",1374029309,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-bevtevpkvtmwwlk2gved,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"Right now, ce.MWInternalLinkAnnotation obtains a DM rendering to get the computed href. We should factor out href computation so that this isn't needed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374014700,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_description,resolved
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"Change 90953 merged by jenkins-bot:
+Get rid of dmRendering hack in ve.ce.MWInternalLinkAnnotation
+
+https://gerrit.wikimedia.org/r/90953",1382986514,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"Change 90953 had a related patch set uploaded by Catrope:
+Get rid of dmRendering hack in ve.ce.MWInternalLinkAnnotation
+
+https://gerrit.wikimedia.org/r/90953",1382383432,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Change 86065 had a related patch set uploaded by Catrope:
+> > Resolve rendered URLs according to the provided <base>
+> > 
+> > https://gerrit.wikimedia.org/r/86065
+> This change tried to just get rid of href computation, but that's not good
+> enough. It does need to actually be computed.
+
+The most recent version of this change actually makes the hack worse, in order to partly fix bug 48915. Once that bug is fixed properly, this hack can be removed.",1380241008,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"(In reply to comment #1)
+> Change 86065 had a related patch set uploaded by Catrope:
+> Resolve rendered URLs according to the provided <base>
+> 
+> https://gerrit.wikimedia.org/r/86065
+This change tried to just get rid of href computation, but that's not good enough. It does need to actually be computed.",1380240303,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"Change 86065 had a related patch set uploaded by Catrope:
+Resolve rendered URLs according to the provided <base>
+
+https://gerrit.wikimedia.org/r/86065",1380161666,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"If someone is clicking on ""Mobile View"" and then back to ""Desktop"", a stopMobileRedirect cookie is left behind. This cookie will disable central notices on all wikimedia sites perpetually
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374004080,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_description,declined
+Switching to mobile view and back leaves cookie behind,"I'm marking this as wontfix.
+
+While I see your point about not setting the stopMobileRedirect cookie for devices that wouldn't normally get automatically redirected (eg a desktop browser), we don't have a reliable way to detect that, so without rearchitecting, we can't really achieve this. Ultimately, we've been attempting to simplify how MobileFrontend works - partly for performance/caching reasons and partly for codebase sanity, and I do not think this usecase is compelling enough to warrant additional complexity.
+
+I suspect Jon is right that with some CSS magic you may be able to resolve the specific issues you're running into with the banners. Otherwise, we should have a bigger discussion about how best for you guys to achieve what you need from within CentralNotice.",1376950515,PHID-USER-jh2oguhshocanixqvlfk,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"Is that zoomed in?
+Does it disappear when you scroll?
+Is it fixed position or absolute?
+
+How can one access that banner on a phone - is there a url? Looks like with a few tweaks to the css that should be easy render correctly on a desktop view on a mobile screen...",1374866409,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"**mwalker** wrote:
+
+Illustration of why desktop banners should not be served to mobile users
+
+Adam got this whilst browsing on the desktop site on his phone whilst logged out.
+
+**Attached**: {F11712}",1374861806,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"""With CentralNotice not filtering; true mobile users who choose to use the
+desktop site may be presented with a banner that doesn't work on small screens
+- e.g. the buttons are too small to hit with a finger.""
+
+This is a non-issue
+The banner will be exactly the same size for users viewing the desktop site on a mobile device.",1374098687,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"**mwalker** wrote:
+
+(In reply to comment #4)
+> You want to show a banner on the desktop site (en.wikipedia.org and friends)
+> when viewed in a mobile phone?
+
+Nope -- we want to show a banner on the desktop site to a desktop user who has previously used the mobile interface.
+
+> Could you clarify ""Removing the filtering comes at the expense of potentially
+> exposing users to banners that don't work particularly well on small
+> screens.""
+
+With CentralNotice not filtering; true mobile users who choose to use the desktop site may be presented with a banner that doesn't work on small screens - e.g. the buttons are too small to hit with a finger.
+
+> Does this effect the mobile site (en.m.wikipedia.org and friends) in anyway?
+
+No. Only the desktop site (and the transition of a desktop user between that and the mobile site and back.)
+
+> I'm also unclear how this effects the VisualEditor roll out... (you mention
+> this in the CentralNotice fix).
+
+VE is only involved because we spotted it with a VE banner (they want to show to everyone so we're getting lots of interesting CN bugs.)
+
+> The stopMobileRedirect cookie exists for a reason - if a user of the mobile
+> site wants to see the desktop site this stops them from being redirected on
+> every visit.
+
+Yep, understood. The feature request is more to not return 'desktop' devices to the desktop site after having viewed the mobile site with a stopMobileRedirect cookie.
+
+> We could only set the stopMobileRedirect cookie if the user is on a mobile
+> phone but this is messy and I don't see what value the work put in to achieve
+> this would gain. Does anything really need to change in MobileFrontend now?
+
+Meh; don't know. This is an edge case... It's more related to if we have more things that are device dependent using the cookie to determine if someone is on a big device or not.",1374091987,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"Just to check I understand the problem correctly:
+You want to show a banner on the desktop site (en.wikipedia.org and friends) when viewed in a mobile phone?
+Was there any reason you didn't do this before? I don't really understand the logic... ResourceLoader disables JavaScript on older phones so these banners should work perfectly fine.
+
+Could you clarify ""Removing the filtering comes at the expense of potentially exposing users to banners that don't work particularly well on small screens."" - if a mobile views the desktop site on their phone they will either use a modified viewport [1] and the banner will look exactly the same as desktop, or if there is no viewport the entire website will be unreadable so I'd be surprised they'd even be in desktop mode.
+
+Does this effect the mobile site (en.m.wikipedia.org and friends) in anyway?
+
+I'm also unclear how this effects the VisualEditor roll out... (you mention this in the CentralNotice fix).
+
+The stopMobileRedirect cookie exists for a reason - if a user of the mobile site wants to see the desktop site this stops them from being redirected on every visit.
+
+We could only set the stopMobileRedirect cookie if the user is on a mobile phone but this is messy and I don't see what value the work put in to achieve this would gain. Does anything really need to change in MobileFrontend now?
+
+[1] http://www.quirksmode.org/mobile/viewports2.html",1374082443,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"Change 73999 merged by jenkins-bot:
+(Bug 51465) No Longer Filtering Mobile Devices
+
+https://gerrit.wikimedia.org/r/73999",1374005801,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"Change 73999 had a related patch set uploaded by Mwalker:
+(Bug 51465) No Longer Filtering Mobile Devices
+
+https://gerrit.wikimedia.org/r/73999",1374004590,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"**mwalker** wrote:
+
+Fundraising's initial response is going to be just to just remove the filtering -- however, it would be a good feature for mobile frontend if that cookie was somewhat smarter (enough to remove itself when not needed / or track where it came from originally: varnish vs url click.)
+
+Removing the filtering comes at the expense of potentially exposing users to banners that don't work particularly well on small screens.",1374004272,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+"VisualEditor: Use a ""broken link"" icon as the ""remove"" button in the link inspector, instead of a rubbish bin","There is consensus for a change to this element here: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Dustbin_icon_not_intuitive_for_.22unlink.22
+
+To summarize - the garbage can icon to remove a link is not intuitive.  Users may be unsure of its function, or believe it will remove the highlighted text, rather than just the link.  Most other editing UI's employ a broken link for this function, so it will be more familiar.
+
+Suggested improvement:
+
+*Replace ""Garbage Can/Dustbin"" with a ""broken link"" icon (example:http://us.fotolia.com/id/49483380)
+
+*Replace current rollover text ""Remove"" with ""Unlink""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374002400,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-ygze3evr6iu2qv2rw7yu,task_description,invalid
+"VisualEditor: Use a ""broken link"" icon as the ""remove"" button in the link inspector, instead of a rubbish bin","We've decided instead to remove the use of icons here as it's too confusing, and instead will use just the label.",1403977522,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ygze3evr6iu2qv2rw7yu,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"See:
+http://en.wikipedia.org/w/index.php?title=User%3ACananian&diff=564446937&oldid=564446873
+
+I was adding a heading (after a <!-- ... --> comment) and the diff stuck a <br> inside the ==heading==.
+
+I'm assigning this bug to VE for the moment, but it could be a parsoid bug.  I need to see the intermediate parsoid HTML generated for the change to tell one way or the other.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1373986620,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gqdob64njr6frqrzr75a,task_description,resolved
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Parsoid now normalizes this HTML to strip <br> from headings - the code is now in production.,1447795442,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Change 253050 merged by jenkins-bot:
+T53444: Strip <br>s from headings via new HTML normalization routine
+
+[[https://gerrit.wikimedia.org/r/253050]]",1447461206,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Change 253050 had a related patch set uploaded (by Subramanya Sastry):
+T53444: Strip <br>s from headings via new HTML normalization routine
+
+[[https://gerrit.wikimedia.org/r/253050]]
+",1447455845,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"If you want an example of how that happens on a private wiki, see above line 114 [[ https://office.wikimedia.org/w/index.php?title=Community_Engagement_(Product)/Editing&diff=prev&oldid=158096 | here ]]. It doesn't involve hidden comments.",1444058682,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Unless it advances the consistency of parsing, I am not convinced this is worth a lot of effort beyond normalization during serialization. The WYSIWYG behavior is clearly an edge-case since wikitext does not support multi-line headings. So, if VE folks are with it, I am fine with it.",1443736308,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"WYSIWYG is tricky here.  In this case, the user clearly saw the entire paragraph, including the newline, being styled as part of the heading.  If we handle this during normalization, then the result after saving will not be consistent with what the user saw during editing.
+
+@Jdforrester-WMF It's //possible// that existing-tidy wouldn't remove `<p><!--comment--></p>` because of the embedded comment.  Currently PHP elides all the comments, so it hands tidy the string `<p></p>` which tidy happily removes.  So it's possible we could finesse this somehow, for example by emitting a stub comment from the PHP parser.  Investigation needed.",1443735812,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Maybe worth handling this in the normalization routines.,1443735363,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Would fixing the PHP Parser require us to have replaced Tidy first, then?",1443714586,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"The original document was serialized with the `<br/>`:
+```
+$ (echo 'foo' ; echo; echo '<!--comment-->'; echo; echo 'bar') | tests/parse.js  --normalize=parsoid
+
+<p>foo</p>
+<!--comment-->
+<p><br/> bar</p>
+```
+I wonder if we should be generating `<p><!--comment--></p>` for that case, instead of the `<br/>` embedded inside the next paragraph.  Our current behavior is consistent with PHP:
+```
+$ (echo 'foo' ; echo; echo '<!--comment-->'; echo; echo 'bar') | php maintenance/parse.php --quiet
+<p>foo
+</p><p><br />
+bar
+</p>
+```
+...but it's certainly not ideal from an editing perspective.  Maybe PHP should change here as well, although I'm guessing the reason it is putting the `<br/>` inside the `<p>` is because otherwise `tidy` would strip the ""empty"" `<p>` tag.
+
+In any case, given this input DOM, VE's behavior is strange but understandable -- when you put your cursor between the exclamation mark and the last written line, VE is placing its internal insertion point between the `<p>` and the `<br/>`, so any heading conversion applies to the entire `<p>` contents, including the embedded `<br/>`.  The result that VE passes back to parsoid is then unsurprising:
+```
+<p id=""mwAQ"">some text</p> <!-- hidden comments FTW --><h2>Foo<br id=""mwAw""> moar text here</h2>
+```
+and Parsoid gives a faithful serialization of this as wikitext.",1443713401,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"The page is nominated for deletion, but [[https://en.wikipedia.org/w/index.php?title=Sabaragamuwa_Province_(Sri_Lanka)_bus_routes&diff=next&oldid=654323182| here's another example]].",1427805964,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Providing steps.
+1) Start with [[ https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=223541 | a new or a blank page ]].
+2) In wikitext mode, [[ https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=223541 | write something on the first line, leave a blank line, write a hidden comment, leave a blank line, write something else ]], then Save.
+3) Now enter VE mode. Notice the hidden comment is correctly displayed as an exclamation mark; there is now a carriage return sign at the beginning of the last line. 
+4) Put the cursor in the blank line between the comment and the last written line. You can now write any word, select it and turn it into a heading or a subheading; notice the entire line below, including the carriage return sign, also becomes part of said heading/subheading.
+5) Save. [[ https://test.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=223543&oldid=223542 | You now have wikitext for the heading/subheading you just made, showing up in plain sight ]]. You can also notice that the carriage return character was turned into a br tag.
+
+Reproducible: Always.
+Tested in Win 8 with the latest versions of Chrome, Firefox, IE, Opera (the last two while logged out). ",1425651893,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Providing steps.
+1) Start with [[ https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=223541 | a new or a blank page ]].
+2) In wikitext mode, [[ https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=223541 | write something on the first line, leave a blank line, write a hidden comment, leave a blank line, write something else ]], then Save.
+3) Now enter VE mode. Notice the hidden comment is correctly displayed as an exclamation mark; there is now a carriage return sign at the beginning of the last line. 
+4) Put the cursor in the blank line between the comment and the last written line. You can now write any word, select it and turn it into a heading or a subheading; notice the entire line below, including the carriage return sign, also becomes part of said heading/subheading.
+5) Save. [[ https://test.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=223543&oldid=223542 | You now have wikitext for the heading/subheading you just made in plain sight ]]. You can also notice that the carriage return character was turned into a br tag.
+
+Reproducible: Always.
+Tested in Win 8 with the latest versions of Chrome, Firefox, IE, Opera (the last two while logged out). ",1425651818,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"No reproduction steps in > 18 months. If you can give some more details, please re-open.",1425599536,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"(BTW, I really couldn't play that vid on YouTube.)",1380121710,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"The steps are clear in AzaToth's video, but I can't reproduce that either: have you fixed something about ↵ being displayed, this week?",1380121219,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Does anyone have any steps to reproduce? I can't reproduce in Firefox or Chrome whilst playing around…,1380069203,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Also reported at https://fr.wikipedia.org/w/index.php?title=Cabinet_des_estampes_et_des_dessins_de_Strasbourg&curid=1591028&diff=96701784&oldid=96701717,1379352540,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Also reported at http://mr.wikipedia.org/w/index.php?title=%E0%A4%9F%E0%A4%BE%E0%A4%95%E0%A4%A3%E0%A4%95%E0%A4%BE%E0%A4%B0_(%E0%A4%B8%E0%A4%AE%E0%A4%BE%E0%A4%9C)&curid=66935&diff=1193242&oldid=1193112 .,1375704033,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,*** Bug 52021 has been marked as a duplicate of this bug. ***,1374767614,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"AzaToth made a screencast at http://youtu.be/G_xXETTVgO0 showing the issue.
+
+Gwicke filed bug 50683 on the parsoid side -- we shouldn't allow newlines in a heading when we serialize to wikitext.
+
+But there's still a VE issue -- where is the ↵ coming from (visible in AzaToth's screencast).  VE shouldn't be putting the newline inside the heading.",1373987836,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"See also https://www.mediawiki.org/w/index.php?title=User%3AGWicke&diff=723931&oldid=655405
+
+So the <!-- ... --> comment doesn't seem to have anything to do with it.",1373987078,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"```
+[subbu@earth:~/work/wmf/parsoid] echo '<a rel=""mw:WikiLink"" href=""./Foobar"">:foobar</a>' | php bin/parse.php --html2wt
+[[:foobar]]
+
+[subbu@earth:~/work/wmf/parsoid] echo '<a rel=""mw:WikiLink"" href=""./Foobar"">:foobar</a>' | php bin/parse.php --html2html --body_only
+<p data-parsoid='{""dsr"":[0,11,0,0]}'><a rel=""mw:WikiLink"" href=""./Foobar"" title=""Foobar"" data-parsoid='{""stx"":""simple"",""a"":{""href"":""./Foobar""},""sa"":{""href"":"":foobar""},""dsr"":[0,11,2,2]}'>foobar</a></p>
+```",1373984340,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_description,open
+Leading colon in link label is wrongly removed from wikitext,"(In reply to comment #11)
+> My point is mainly that VE could easily understand when the punctuation is
+> added by mistake, because the label and the target link will be different. So
+> if the target does not feature a punctuation mark, but the label does, that
+> was probably not wanted. 
+
+Unfortunately we have to handle the case when it was intentional, so we can't just blindly auto-correct it. Also the definition of what is punctuation becomes much more complex when you are dealing with thousands of languages.",1379678052,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"This is a Parsoid bug (the colon part, at least):
+
+<a rel=""mw:WikiLink"" href=""./Foobar"">:foobar</a>
+
+serialises to:
+
+[[:foobar]]
+
+which converts back to
+
+<a rel=""mw:WikiLink"" href=""./Foobar"">foobar</a>",1379677931,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"I am leaving aside the semicolon issue, covered elsewhere.
+About what I reported in Comment 5:
+
+1) Type "":foobar""
+2) select all of this, from the colon (included) to the final r
+3) click on the linking tool, and make this a link to the article ""foobar""
+4) save.
+*outcome: the colon is included in the link; the link is working but the colon is invisible (and I think this is certainly not desirable).
+
+Please note that this also happens to "": foobar"", that is, if the colon and the typed word are separated by a space.
+
+
+1) Type ""foobar:""
+2) select all of this, from the f to the colon, including it
+3) click on the linking tool, and make this a link to ""foobar""
+4) save.
+*outcome: the colon is included in the link, it is visible, the link works fine (and I think this is not good code).
+
+Please note that when a piped link is created instead (for example if foobar is a link to Foobar2000), the colons will be part of the link in every case and they will all be visible.
+
+My point is mainly that VE could easily understand when the punctuation is added by mistake, because the label and the target link will be different. So if the target does not feature a punctuation mark, but the label does, that was probably not wanted. 
+
+HTH.",1379619273,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"This is indeed reproducable, and not just with semi-colons, but it is not this bug. I've reported it separately as bug 54332 including how to reproduce it.",1379606034,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,Can you leave some step-by-step instructions to reproduce the bug for clarification?,1379604129,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"About semicolons, we got another feedback that I managed to reproduce, see https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=573644513&oldid=573644268 .
+I wrote French; and turned that into a wikilink, including the semicolon.
+Then I added some text between the end of the word and the semicolon. The result is that we now have two wikilinks to the same word, and a nowiki tag in the middle.",1379599394,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"Yes Ed, in both cases I selected the colon and the word and then used the link tool. I know that you can get the first result also in the source editor, but the second one definitely does not produce a working link with the source editor, and anyway I was not really sure if it makes sense having a wikilink which includes a colon and then makes it invisible. If you think none of these behaviours should be prevented or worked on anyway, please just re-close this. Thanks.",1379512496,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"Can you explain how those cases were created. From what I can see colons don't extend link annotations, but if you select over a colon and use the link tool you're going to end up with weird stuff like that anyway.",1379507908,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"I am reopening this since I noticed that colons at least still get included in the links: here https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=573483719&oldid=573483114 the line beginning with ""Performance problems: VisualEditor"" has the colon included in the wikilink of the lattest word; the link works fine but you don't get to see the colon at all.
+https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=573483774 Here instead it is included in the wikilink to Issues, and I am not sure it's desirable either. Thanks.",1379507107,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"(In reply to comment #3)
+> Links are no longer getting extended automatically when any text is added at
+> the end, including commas, semicolons, etc. Possibly a result of the fix for
+> bug 51463
+
+Indeed, this was fixed in that.",1377830517,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"Links are no longer getting extended automatically when any text is added at the end, including commas, semicolons, etc. Possibly a result of the fix for bug 51463",1377448214,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"(In reply to comment #1)
+> instead of just the former (perhaps some kind of inline block wrapper around
+> the link, e.g. like Apple does in Mail and Calendar when text contains a
+> reference to a contact. It looks like ""Foo { bar } quux."" Where bar has a
+> rounded bubble around it when hovered and the cursor can be placed inside or
+> outside the bubble.
+
+)
+
+http://xkcd.com/859/",1373984998,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"I don't think we should explicitly disallow such symbol to be used in the label (might lead to other strange side-effects and inconsistencies).
+
+However it does give another use case for bug 51438 (T55973). Having a better way to edit the label might reduce the cases where this happens. Perhaps we could make it possible to put the cursor inside the link (after the last character) and outside the link.
+
+So that one can be in either of these positions:
+
+ * Foo <a>bar|</a>
+ * Foo <a>bar</a>|
+
+instead of just the former (perhaps some kind of inline block wrapper around the link, e.g. like Apple does in Mail and Calendar when text contains a reference to a contact. It looks like ""Foo { bar } quux."" Where bar has a rounded bubble around it when hovered and the cursor can be placed inside or outside the bubble.",1589732305,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"I don't think we should explicitly disallow such symbol to be used in the label (might lead to other strange side-effects and inconsistencies).
+
+However it does give another use case for bug 51438. Having a better way to edit the label might reduce the cases where this happens. Perhaps we could make it possible to put the cursor inside the link (after the last character) and outside the link.
+
+So that one can be in either of these positions:
+
+ * Foo <a>bar|</a>
+ * Foo <a>bar</a>|
+
+instead of just the former (perhaps some kind of inline block wrapper around the link, e.g. like Apple does in Mail and Calendar when text contains a reference to a contact. It looks like ""Foo { bar } quux."" Where bar has a rounded bubble around it when hovered and the cursor can be placed inside or outside the bubble.",1373984857,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"Currently, if you use TemplateData for a template without any parameters, you still have to create an empty ""params"" in the JSON (not really important), but you also end up with a ""Template parameters"" table with just the title line (Parameter	Description	Type	Default	Status).
+
+Rather than displaying an empty table, I think it would be better to display no table at all, or a simple message saying that no parameters are defined for this template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1373960160,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_description,resolved
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"The fix in beta:
+ {F45817}
+
+vs test2:  
+{F45819}",1424732585,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"Change 191518 merged by jenkins-bot:
+Display a message when no parameters are defined
+
+[[https://gerrit.wikimedia.org/r/191518]]",1424310514,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"Change 191518 had a related patch set uploaded (by Mooeypoo):
+Display a message when no parameters are defined
+
+[[https://gerrit.wikimedia.org/r/191518]]
+
+#patch-for-review",1424308343,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"It would also be useful if you could set ""no parameters"" in the TemplateData so that VisualEditor does not suggest adding a parameter for these templates.",1421330757,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,*** Bug 62417 has been marked as a duplicate of this bug. ***,1398711170,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Seeing this more often now with VE and think it may be a couple different issues (not all on our side) but want to see what we can do to stop it and or lessen impact. This is currently being added to the security queue because I'm a bit concerned about some of the symptoms and worry it could be an injection vulnerability (see below). If we rule out a security concern I'm obviously happy with it being moved.
+
+Editors are making a normal edit and div's are being inserted like 
+
+<div id=""myEventWatcherDiv"" style=""display:none;""></div>
+
+often at the start and end of the page. 
+
+Googling around it seems they may be inserted by a common 3rd party plugin (divX?) but it is in no way clear. It also seems to be interacting weirdly with VE because it isn't only being inserted it's inserting WITHOUT <nowiki> tags which is what you'd expect if someone put a div in (see https://en.wikipedia.org/w/index.php?title=User:Jalexander/sandbox&diff=564465081&oldid=553572859 ). Could it be being injected somehow around VE and/or parser? 
+
+Examples:
+https://en.wikipedia.org/w/index.php?title=Spank!_The_Fifty_Shades_Parody&diff=prev&oldid=564448990
+http://en.wikipedia.org/w/index.php?title=Kendra_Morris&diff=prev&oldid=564426900
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51521",1373954100,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_description,resolved
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",">>! In T53423#1031831, @Aklapper wrote:
+> This task has #VE-deploy-2014-10-02 but is still open. Should this be retargetted?
+
+No.",1427402641,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",This task has #VE-deploy-2014-10-02 but is still open. Should this be retargetted?,1423677807,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Still seems to be happening, e.g. https://fr.wikipedia.org/?diff=108255165",1413485794,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114007,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113155,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Has anyone here managed to actually get this to happen in their browser yet? James tried the DivX plugin in Safari on his Mac and couldn't get it to insert the bad content.,1407403424,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #16)
+> Sorry meant http://en.wikipedia.org/wiki/Special:AbuseFilter/345
+
+Thanks - though we should probably silently remove on save inside VisualEditor, like Inez suggests.",1380214635,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Sorry meant http://en.wikipedia.org/wiki/Special:AbuseFilter/345,1380184705,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Detected and warning issued by the abuse filter http://en.wikipedia.org/wiki/Special:AbuseFilter/485,1380184623,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",for the record it happened in fr.wp : https://fr.wikipedia.org/w/index.php?title=Les_Fourmis_%28Werber%29&diff=96415737&oldid=89791930,1378394111,PHID-USER-h66anukl4e5enszrrt3t,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",@James: Should we go for silent remove on safe? Also we can start tracking it with information about logged in vs. logged out user.,1377119871,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","I am also curious to know why it only happens to anonymous editors - at least, all the occurrences I have seen so far.",1377119586,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",On it.wp as well: http://it.wikipedia.org/w/index.php?title=Tank_Palamara&diff=60582899&oldid=60582688,1375696065,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Silently remove on save. Hacking blacklist will prevent people from saving and many of them are not technical enough to understand why - bad bad user experience.,1375286948,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #8)
+> As a workaround for now we could make VE remove those divs from the HTMLDOM
+> that it is sending to MW API for serializing. @James: Should we do it?
+
+You mean, have a blacklist of items to just silently remove on save? Could work as a quick hack.",1375286359,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",As a workaround for now we could make VE remove those divs from the HTMLDOM that it is sending to MW API for serializing. @James: Should we do it?,1374964307,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #6)
+> Making this public since I don't see this having any security impact. Then
+> the
+> community can also give input into how they want to see it handled.
+
+Thanks Chris",1374014416,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Making this public since I don't see this having any security impact. Then the community can also give input into how they want to see it handled.,1374014345,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #2)
+> It's certainly a type of edit we really don't
+> want but more importantly I'm confused about how it's getting inserted and
+> avoiding the normal VE/parser work flow which should <nowiki> it (instead of
+> actually inserting it in as a div like it is now).
+It's possible that the plugin inserts it in all <iframe>s. We use <iframe>s internally for encapsulating HTML documents.",1374013982,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #2)
+> I'm confused about how it's getting inserted and
+> avoiding the normal VE/parser work flow which should <nowiki> it (instead of
+> actually inserting it in as a div like it is now).
+
+It looks like it's bypassing the browser's events model and just inserting into the DOM, hence the issue. JS like VE isn't able to notice things outside the JS events model, sadly.",1374013882,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #1)
+> Hi James, the google consensus seems to be that a DivX plugin is inserting
+> that. 
+> 
+> http://padawan.info/en/2011/03/wtf-is-this-myeventwatcherdiv-doing-in-my-web.
+> html
+> 
+> I'm guessing that VE's interface suddenly looks like something the plugin was
+> expecting to use in the browser, and so it silently adds the div.
+> 
+> We could add an abusefilter rule to block those edits, but that seems a
+> little drastic.
+
+Ideally we'd want a global AbuseFilter rule that just silently dropped the content from the edit, but that's not a feature AF currently does. :-)
+
+Blocking is a bit strong, though possibly likely to happen from the community if we just warn users and they ignore. The only fix (other than getting the upstream plugin crap fixed, which seems unlikely) is to do the auto-drop in VE, which is icky too.",1374013806,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","yeah, that seems to be the consensus I could find too (which is very very weird... because I can't for the life of me find a 'legitimate' reason it should insert that into any page it can edit.. oh well certainly not the weirdest plugin BS I've seen). 
+
+Actually I don't think that's very drastic to do, the community almost certainly would agree and I'd pass it off to them (though they'll likely blame us for it which is never fun). It's certainly a type of edit we really don't want but more importantly I'm confused about how it's getting inserted and avoiding the normal VE/parser work flow which should <nowiki> it (instead of actually inserting it in as a div like it is now).",1374013674,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Hi James, the google consensus seems to be that a DivX plugin is inserting that. 
+
+http://padawan.info/en/2011/03/wtf-is-this-myeventwatcherdiv-doing-in-my-web.html
+
+I'm guessing that VE's interface suddenly looks like something the plugin was expecting to use in the browser, and so it silently adds the div.
+
+We could add an abusefilter rule to block those edits, but that seems a little drastic.",1374013374,PHID-USER-doeppszazlm3r7xah4il,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","In view mode, [[Template:Top icon]] places the featured star or good article at the top right hand corner.
+
+After loading a FA or GA or English Wikipedia, the featured star or good article icon appears where the template is, which is often down the bottom.  This is perfectly acceptable except for the 'where did it go?' feeling, but maybe a plugin could come up with a better UI design for topicons, geocoords, etc.
+
+Also templates without any real estate (like {{Use dmy dates}} and {{Use Australian English}}) 'disappear' entirely.
+
+https://en.wikipedia.org/wiki/Angels_Brought_Me_Here?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51322",1373941680,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ee572n6mn4yah76xipnp,task_description,open
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","Now that bug 23796 is fixed, we ""just"" need to work out a way to let the user set/unset these (bug 72199) and then trap clicks on this area to open the meta dialog, I think?",1414441807,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","This is a rather more general problem with the Vector skin (there's desire to have flag icons from the content, but no ability other than a hack that's unsupportable in VisualEditor).",1380753138,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","Bug 51322 fixed issues that were 'solely metadata', but these actually do produce elements, the problems that remain for these elements are:
+1: incorrectly positioned
+2: their template edit button, when selected is visually placed far from the content, making it difficult to find. bug 50854
+3: if they were correctly positioned, they are 'decoupled' from their anchor point  which is a problem with templates producing floating content as well. bug 50907",1375717076,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","The meta-templates bug 51322 has been marked as fixed, but the issue of top icons is still ongoing.",1375710059,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable",'templates without any real estate' has been raised already as bug 51322 (meta templates).,1374037304,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","It is easy to delete these hidden templates without noticing.
+
+e.g. delete the '↵' on Angels Brought Me Here.",1374035331,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","The 'templates without any real estate' problem is raised here:
+
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Time_for_an_essay
+
+I'm not sure if a separate bug has been raised, or even should be.  The top icons and templates without any real estate all need a special UI, probably under 'page settings'.",1374034932,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+VisualEditor: Automatically build the option description for visualeditor-enable,"Forked from the original request at bug 48666 which was solved by making the preference hidden, as intended.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373933760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fe5263dfospwtagdlyvz,task_description,resolved
+VisualEditor: Automatically build the option description for visualeditor-enable,"Change 130075 merged by jenkins-bot:
+Add dynamically generated list of namespaces to visualeditor-enable preference
+
+https://gerrit.wikimedia.org/r/130075",1398712510,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fe5263dfospwtagdlyvz,task_subcomment,NA
+VisualEditor: Automatically build the option description for visualeditor-enable,"Change 130075 had a related patch set uploaded by Alex Monk:
+Add dynamically generated list of namespaces to visualeditor-enable preference
+
+https://gerrit.wikimedia.org/r/130075",1398694222,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-fe5263dfospwtagdlyvz,task_subcomment,NA
+"VisualEditor: Create i18n toolbar icon for bold for Portuguese, Spanish and Galician","As in Bug T53330, I would like to request the icon for ""Bold"" to be an ""N"" (from ""Negrito"") in Portuguese (""pt"" and ""pt-br"").
+",1373919300,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-gguvte4hcswafvyrrjsm,task_description,resolved
+"VisualEditor: Create i18n toolbar icon for bold for Portuguese, Spanish and Galician",This was fixed and deployed yesterday.,1374771717,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gguvte4hcswafvyrrjsm,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"Use case:
+* The user opens VisualEditor
+* The user types something that looks like wikitext
+* VE notices and displays an mw.notify bubble with autoHide:false
+* The user leaves VE by clicking on the Read tab
+* The editor is torn down and we go back to view mode, but the bubble persists
+
+I would like to be able to remove this bubble when the editor is torn down, but mw.notification doesn't expose an API for this. There is a .close() method on Notification, but there's no way to get the Notification object created by mw.notify().
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1373853480,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mjeduabrtvm33uiu3e4a,task_description,resolved
+mw.notify notifications can't be removed/hidden programmatically,"Change 74407 merged by jenkins-bot:
+mediawiki.notification: Expose close method to hide a Notification
+
+https://gerrit.wikimedia.org/r/74407",1382187742,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"Change 74407 had a related patch set uploaded by Alex Monk:
+Return Notification object from mw.notification.notify
+
+https://gerrit.wikimedia.org/r/74407",1374170832,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"(In reply to comment #2)
+> I'd say that this is expected behavior and a ""feature"" of the shorthand. Just
+> like you can't have a message parsed by just doing mw.msg(), you have to use
+> mw.message().whatever() instead.
+> 
+> Alex's solution makes sense at a glance.
+Returning the Notification object would fix this, yes. Unfortunately, that change is still pending review.",1374170547,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"I'd say that this is expected behavior and a ""feature"" of the shorthand. Just like you can't have a message parsed by just doing mw.msg(), you have to use mw.message().whatever() instead.
+
+Alex's solution makes sense at a glance.",1373910457,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"I had this problem in Gerrit change 5130. Had to depend on mediawiki.notification, add a 'return notif' to the mw.notification.notify function and use that instead of mw.notify.",1373855119,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+"VisualEditor: Deleting new line icon (""↵"") between two links has no effect (?)","If an article has 
+
+[external link]
+[external link]
+
+It is rendered in VE as:
+
+[external link]↵[external link]
+
+Selecting the ↵ and pressing delete causes the ↵ to be removed, however the link break is not removed, and saving says that there are no changes.
+
+Example:
+https://en.wikipedia.org/wiki/Otis_%28album%29?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373850900,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-pkpe26l4yvkcclna5vl6,task_description,resolved
+"VisualEditor: Deleting new line icon (""↵"") between two links has no effect (?)","This appears to work correctly now.
+
+(The article no longer has this wikitext now, but I tried on an older version: https://en.wikipedia.org/w/index.php?title=Otis_(album)&oldid=512105119&veaction=edit – be sure to only preview changes and do not accidentally save the article.)",1429478513,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-pkpe26l4yvkcclna5vl6,task_subcomment,NA
+"VisualEditor: Deleting new line icon (""↵"") between two links has no effect (?)",Possibly a Parsoid bug?,1385384555,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pkpe26l4yvkcclna5vl6,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"The way VisualEditor handles links with square brackets, but no explicit anchor, can be confusing.  These links are generally discouraged on English Wikipedia, but still occasionally used.
+
+An example is https://en.wikipedia.org/w/index.php?title=User:Superm401/Sandbox&veaction=edit&oldid=564175896 .  The wikitext for this is just [http://example.com], which renders as a linked [1] (or whatever number it is in the page)
+
+However, you should edit the latest version of a page for testing this.  When you edit an oldid page, you won't be able to reproduce the ""Save page"" disable behavior I mention below.
+
+VisualEditor lets you backspace to remove the characters one by one, which does not really reflect the model of how the link works.  After one or more is removed, ""Save page"" un-greys.  However, when you go to review the changes, it says, ""Could not start the review because your revision matches the latest version of this page.""
+
+It does let you remove the link entirely, but to do so you need to explicitly remove each character (not just backspace once to delete the whole thing).
+
+Do a fresh load of the edit page (separate test).  Then, click the chain icon next to the link.  Then, press enter twice to exit the link dialog.  This time, review changes works.  The wikitext becomes:
+
+[http://example.com <nowiki>[1]</nowiki>]
+
+It probably should not change the link if you simply enter the link dialog and press enter without changing anything.  Also, forcing it to text like this is inconsistent with what happens if you delete the right bracket (see above).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373772420,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-67wpkhw2f4styiyn7rfv,task_description,resolved
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to Matthew Flaschen from comment #9)
+> Is it possible to convert an auto-numbered link to one with arbitrary text
+> (that's what the second part of the bug title refers to)?
+
+Yes, that's been possible for a while. In https://meta.wikimedia.org/wiki/Tech/News/2014/27?veaction=edit for example, click on one of the auto-numbered links to edit it, then click ""add label"" to convert it to a ""normal"" link.",1410238428,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,Is it possible to convert an auto-numbered link to one with arbitrary text (that's what the second part of the bug title refers to)?,1410235672,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"Change 143346 merged by jenkins-bot:
+Make it possible to create autonumbered external links from link inspector
+
+https://gerrit.wikimedia.org/r/143346",1409962256,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to Bartosz Dziewoński from comment #6)
+> (In reply to James Forrester from comment #2)
+> > You cannot …
+
+[…]
+
+> > * … convert an auto-numbered external link to a real external link; or
+> 
+> You can do that from ve.ui.MWLinkNodeInspector now, I don't know when it was
+> implemented.
+
+Yes, that was fixed a month or so ago with the creation of MWLinkNodeInspector.",1404237321,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to James Forrester from comment #2)
+> You cannot …
+> 
+> * … create an auto-numbered external link; 
+
+My patch https://gerrit.wikimedia.org/r/143346 implements this.
+
+> * … convert an auto-numbered external link to a real external link; or
+
+You can do that from ve.ui.MWLinkNodeInspector now, I don't know when it was implemented.
+
+> * … ""clear formatting"" on an auto-numbered external link.
+> 
+> I think the first two are valuable, but the third isn't, because we're
+> planning to remove the function of removing links and other rich styling
+> from the ""clear formatting"" function button.
+
+I don't think treating it as ""formatting"" makes sense anyway.",1404233558,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"Change 143346 had a related patch set uploaded by Bartosz Dziewoński:
+Make it possible to create autonumbered external links from link inspector
+
+https://gerrit.wikimedia.org/r/143346",1404233443,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to Matthew Flaschen from comment #3)
+> (In reply to Matthew Flaschen from comment #0)
+> > VisualEditor lets you backspace to remove the characters one by one, which
+> > does not really reflect the model of how the link works.
+> 
+> This is fixed.  It now highlights on first backspace, and erases on second,
+> which I think is handled the same as similar things.
+
+Yeah, sorry, forgot to say ""we've done a bunch of work on auto-numbered external links since this bug was filed, so most of this is fixed, however…"" at the top. :-)",1394498598,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to Matthew Flaschen from comment #0)
+> VisualEditor lets you backspace to remove the characters one by one, which
+> does not really reflect the model of how the link works.
+
+This is fixed.  It now highlights on first backspace, and erases on second, which I think is handled the same as similar things.",1394490729,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"Current status:
+
+You can …
+
+* … edit the target of an auto-numbered external link to a different external link; and 
+* … edit the target of an auto-numbered external link to an internal link, and the anchor will automatically be set as the internal link value.
+
+
+You cannot …
+
+* … create an auto-numbered external link; 
+* … convert an auto-numbered external link to a real external link; or
+* … ""clear formatting"" on an auto-numbered external link.
+
+I think the first two are valuable, but the third isn't, because we're planning to remove the function of removing links and other rich styling from the ""clear formatting"" function button. Re-titling, setting priority.",1394479965,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"Also, if you highlight it, then use ""Clear formatting"", it does nothing.  I'm not sure what it should do (nowiki the URL?), but if it does nothing it should be greyed out.",1373772660,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"From English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):
+
+It's not a high priority, but still, a suggestion: the default search text, for an image search, is the complete page name. So, for example, if someone is editing a draft article, at User:WhateverEditorName/Article name, the default search text is ""WhateverEditorName/Article name"". It would be better if the default ignored the final slash and all text to the left of it; in this case, it would mean the default search would be ""Article name"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373722680,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-dokktb23gmzzq6sf5ts5,task_description,resolved
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"Change 137151 merged by jenkins-bot:
+Use subpage only for media search string
+
+https://gerrit.wikimedia.org/r/137151",1401919831,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"Change 137151 had a related patch set uploaded by Mooeypoo:
+Use subpage only for media search string
+
+https://gerrit.wikimedia.org/r/137151",1401825558,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"(In reply to comment #5)
+> No, not everyone has the editbugs permission.
+
+See bug 40497 for the editbugs problem.",1374841877,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"No, not everyone has the editbugs permission. Andre can give you it, CCing him.",1374840313,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"Ah, I see. :) I don't actually know if everyone has the rights to do so - bugzilla is a strange and wondrous land to me.",1373808017,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"You missed my main point in the title : it's text ""before"" the / that should be ignored, not the text ""after"" ;-)
+
+I don't see how I can change bug titles. Are you sure everyone has the rights to do so ?
+The only things I can do is add a comment, add an attachment, ...",1373807242,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"I've changed it. Titles are editable in bugzilla, much like wikitext. :)",1373806617,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"Bug title is incorrect, it would rather be something like ""Default search text for images should ignore text before /""",1373793904,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Maxthon mobile browser click on link opens the link,"When using the Maxthon browser, clicking on a link (wiki or external) opens the link instead of allow ther to alter the link object.
+
+After the linked page is opened, returning to the VE shows the link object icon which alllows the link to be altered.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373671080,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-d2aeownijzkra4jifb23,task_description,declined
+VisualEditor: Maxthon mobile browser click on link opens the link,"Unfortunately closing this Phabricator task as no further information has been provided.
+
+After you have provided the information asked for and if this still happens, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks!
+",1598732594,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d2aeownijzkra4jifb23,task_subcomment,NA
+VisualEditor: Maxthon mobile browser click on link opens the link,"5.5 years later, is this still an issue? If it is, please provide Maxthon browser version information and a URL to reproduce. Thanks!",1590943358,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d2aeownijzkra4jifb23,task_subcomment,NA
+VisualEditor: Maxthon mobile browser click on link opens the link,It works better than Google Chrome. :P  See bug 51270.,1373672761,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-d2aeownijzkra4jifb23,task_subcomment,NA
+VisualEditor: Maxthon mobile browser click on link opens the link,Sounds like we may need to blacklist the Maxthon browser. :-(,1373671579,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d2aeownijzkra4jifb23,task_subcomment,NA
+VisualEditor: Initial (PHP-rendered) template display misaligned in Firefox,"Copied from English Wikipedia:
+
+Editing Gol Transportes Aéreos Flight 1907#Criminal proceedings I added two cleanup templates, {{update}} and {{prose}}. In the visual editor the two templates were differently left-aligned and different lengths, despite saving and displaying correctly. Reopening the page in the visual editor, the templates appear at their correct size and alignment, but do appear with an apparent blank line between them. Thryduulf (talk) 14:04, 12 July 2013 (UTC)
+
+See screenshot: 
+http://en.wikipedia.org/wiki/File:Visual_Editor_screenshot_-_templates_not_aligned.png
+
+****
+I could replicate this on Firefox (Windows 7) but not Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1373654340,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-sazwqzfkazbagnggd2du,task_description,resolved
+VisualEditor: Initial (PHP-rendered) template display misaligned in Firefox,Looks fine to me now?,1421778486,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sazwqzfkazbagnggd2du,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","I was following Sherry's kind advices in my sandbox at enwp http://en.wikipedia.org/wiki/User:Elitre_(WMF)/Sandbox:
+<<you can create an {{Infobox person}}, with parameters like ""name"" and ""occupation"".  Within those parameters, you can type the wikicode for any templates you want.  For example, you can give it a name parameter of ""Alice Expert((citation needed|date=July 2013}}"", which later gets processed properly as a template. >>
+An infobox appeared (well, a box with my sandbox title, actually), I saved, ""your edit was saved"" message appeared, the box isn't in the page anymore.
+Tried again, same thing. No trace of my activity in the history. Win 7, Vector, both Chrome and FF.
+
+Thanks,
+E.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52640",1373644020,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_description,resolved
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","Change 150419 merged by jenkins-bot:
+Don't show PostEdit message if we made a null edit
+
+https://gerrit.wikimedia.org/r/150419",1406681112,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","Change 150419 had a related patch set uploaded by Alex Monk:
+Don't show PostEdit message if we made a null edit.
+
+https://gerrit.wikimedia.org/r/150419",1406673673,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't",Confirmed that this is still broken for VisualEditor (and not for wikitext editing).,1401997911,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","**swalling** wrote:
+
+(In reply to comment #3)
+> This is the same behaviour as the wikitext editor. We really should fix this
+> there first if we're changing behaviour for VisualEditor, so that they match.
+> 
+> CC'ed Steven - is there interest in changing for this case in core?
+
+As far as I know, this problem is solved for the wikitext editor. We should not be showing the post-edit confirmation on null edits. I just re-tested this to confirm with a null edit to an article. Is there something special about Elitre's case that I should try to replicate?",1385406579,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","This is the same behaviour as the wikitext editor. We really should fix this there first if we're changing behaviour for VisualEditor, so that they match.
+
+CC'ed Steven - is there interest in changing for this case in core?",1385399707,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","It might be worth adding that this actually works for Sherry:
+http://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&action=history .",1373648223,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","It must be the ""template within a template"" thing, because it will save without that part. 
+Thanks,
+E.",1373644172,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+VisualEditor: Suppression of Cite error in templates still paints a phantom,"Screenshot
+
+Previously we had an issue that the cite extension would throw an error if you had a reference inside a template. That message is now suppressed, but only suppressed - it generates a substantial visual artefact on mouseover that previously contained the error message. See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11227}",1373635140,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-v6t7ev5julnky6rafmtd,task_description,resolved
+VisualEditor: Suppression of Cite error in templates still paints a phantom,I believe that this has been fixed for some time; I cannot replicate now.,1392426157,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v6t7ev5julnky6rafmtd,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"A few users at itwp requested that the list of articles you can choose as a wikilink target supports right-click on each title to view the page in another tab; and that disambiguation pages in the same list appear differently (maybe italicized as it currently happens in MediaWiki special pages?) Thanks!
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373580540,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_description,resolved
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,Verified the fix in test2 and production.,1416433806,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,The fix is verified in betalabs(beware of a difference between Link and Simple link!). The fix applies to the Link.,1415399485,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"Change 171488 merged by jenkins-bot:
+Matching pages from suggestions in link dialog now actually work as links
+
+https://gerrit.wikimedia.org/r/171488",1415310550,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"Change 171488 had a related patch set uploaded by SuchetaG:
+Matching pages from suggestions in link dialog now actually work as links
+
+https://gerrit.wikimedia.org/r/171488",1415237098,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"(In reply to Roan Kattouw from comment #3)
+> Both this and bug 50646
+Forget about bug 50646, my mistake, that one was about links in a different context. Comment #3 is still valid for this bug though.",1415226493,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"Both this and bug 50646 should be fixed by making the link suggestions real links, i.e. real <a> tags whose hrefs point to the pages they're suggesting.
+
+To do that, you'd need MWLinkTargetInputWidget to use a specialized subclass of MenuItemWidget; right now it creates plain MenuItemWidgets. Eventually that specialized subclass could be enriched to contain an image and a description etc., per the new designs for the link inspector. We could also use this new widget in MWTitleInputWidget.",1415054253,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"Bug 50240 asks for disambiguation pages to be distinguished in the list, so I'm retitling this one to focus on being able to open the targets with ctrl+click/right click. A user at en.wp has requested this functionality as well.",1378728231,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"You can use right click or ctrl+click on the links once inserted into the page, but per Bug 48915 this currently leads to the wrong namespace for links other than those to and from the article namespace.",1375706305,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+"VisualEditor: Context menu should appear in floated element, not in float origin","Screenshot of problem
+
+When a page contains multiple floated blocks after one another that each have a context menu (e.g. both transclusion) the ones after the first get the context menu in the wrong place. Namely on the second ""line"" of the article instead of where the element actually is (much further down).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11059}",1373540820,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-xtmuxxa5rnveu7aqbphi,task_description,resolved
+"VisualEditor: Context menu should appear in floated element, not in float origin","This works correctly these days:
+
+https://en.wikipedia.org/wiki/Wangbangsan?veaction=edit
+
+{F18142544}
+{F18142546}",1525988938,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-xtmuxxa5rnveu7aqbphi,task_subcomment,NA
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"Go to https://en.wikipedia.org/wiki/Mohammad_Azharuddin - look at the infobox image. Then hit ""edit"". I have no idea what's happening, but it shouldn't be.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+{T53932}
+{T55226}",1373539980,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_description,resolved
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"The issue as filed was resolved long time ago (see parent bug T52577), I filed T96667 to track the issue of oversized highlights.",1429615750,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_subcomment,NA
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"There are no screenshots here to show how it used to be broken, but it seems almost correct now. Only the highlight is displayed incorrectly.
+
+https://en.wikipedia.org/w/index.php?title=Mohammad_Azharuddin&oldid=564025381&veaction=edit
+
+{F117707}",1429477738,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_subcomment,NA
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"There are no screenshots here to show how it used to be broken, but it seems almost correct now. Only the highlight is displayed incorrectly.
+
+{F117707}",1429477722,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_subcomment,NA
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"The image displayed is the same, https://en.wikipedia.org/wiki/File:Mohammad_Azharuddin_Sangeeta_Bijlani.jpg. But it is cropped by CSS (using https://en.wikipedia.org/wiki/Template:Css_Image_Crop) and VE don’t let the image be cropped correctly…",1373541156,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","If would be nice for power users to have an option to disable the popup warning that occurs when you are trying to leave the edit mode while you have done some editing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373395140,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-7oml5hricm47p3yxxcje,task_description,resolved
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","Change 126994 merged by jenkins-bot:
+Check useeditwarning preference before showing warning when browsing away from editor
+
+https://gerrit.wikimedia.org/r/126994",1397849065,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","Change 126994 had a related patch set uploaded by Alex Monk:
+Check useeditwarning preference before showing warning when browsing away from editor
+
+https://gerrit.wikimedia.org/r/126994",1397746746,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","Change 126977 abandoned by Alex Monk:
+Add preference to disable leaving warning while editing
+
+Reason:
+gah, missed that one.
+
+https://gerrit.wikimedia.org/r/126977",1397745885,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","The preference 'useeditwarning' already exists, but this bug is about VisualEditor, maybe the VisualEditor does not respect the core preference or implement it's own edit warning.",1397744974,PHID-USER-qaoxfiqu6bxhd5ehlwhc,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning",Note that such a preference existed before and was removed when this functionality was merged into core from the Vector extension (bug 46514).,1397743302,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","I'd argue this is unwanted feature mania. If the warning doesn't make sense, remove it. If it does, leave it.",1397743017,PHID-USER-w5a723w3wes6jd5wskgg,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","Change 126977 had a related patch set uploaded by Alex Monk:
+Add preference to disable leaving warning while editing
+
+https://gerrit.wikimedia.org/r/126977",1397742780,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","As mentioned in IRC, we should make this a core feature for MW and just re-use that preference rather than have a VE-specific one.",1373395795,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning",See http://youtu.be/gqqswqLd5Yw for what I mean,1373395370,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Editor requests support for adding non-breaking spaces (&nbsp;), keyboard shortcut?
+
+From MediaWiki Feedback:
+
+How do I enter a no-break space (& nbsp;) into the source text via the keyboard? Something like Ctrl+Space would be nice … And, BTW, can I see the difference between a regular space and a no-break space?
+
+Troubled @sset Work • Talk • Mail‎18:03, 8 July 2013
+
+--------------------------
+Alternative: {T70429}",1373383320,PHID-USER-ttyyrgsrkyonct7hizgv,PHID-TASK-33ykzddzyqsfzj3qavxw,task_description,resolved
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Test wiki on [[ http://localhost/patchdemo | Patch demo ]]  by Ed using patch(es) linked to this task was **deleted**:
+
+~~[[ http://localhost/patchdemo/wikis/bca3f56df9aa1ff71991cf889062e980/w/ ]]~~",1689773252,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"This should be fixed now, and the change will be deployed to Wikimedia wikis next week.
+
+Here's how the final version works:
+* On every operating system and keyboard layout, VisualEditor should support the built-in shortcut to insert a non-breaking space – e.g. Opt+Space on macOS, or various Linux keyboard layouts like those mentioned in T53045#5133074. (We'd appreciate if you could test with your favorite operating system / browser / language / keyboard layout / input method, as it's impossible for us to verify all combinations.)
+* In addition to that, on PC, we also support the Ctrl+Shift+Space shortcut to insert a non-breaking space.
+* These shortcuts insert the `&nbsp;` entity, in new wikitext editor as well as in the visual editor.",1618344115,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 255937 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Add command to insert non-breaking space%%%
+https://gerrit.wikimedia.org/r/255937",1618340744,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 676162 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (5d0701ea3)%%%
+https://gerrit.wikimedia.org/r/676162",1617229406,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 676162 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (5d0701ea3)%%%
+https://gerrit.wikimedia.org/r/676162",1617227930,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 665132 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Detect NBSPs being inserted deliberately by IMEs%%%
+https://gerrit.wikimedia.org/r/665132",1617227748,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Test wiki on [[ http://localhost/patchdemo | Patch Demo ]]  by Ed using patch(es) linked to this task was **deleted**:
+
+~~[[ http://localhost/patchdemo/wikis/ccf0f0ed62e0183bcd8312eb45d1ce97/w/ ]]~~",1615050934,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Test wiki **created** on [[ http://localhost/patchdemo | Patch Demo ]] by Ed using patch(es) linked to this task:
+
+http://localhost/patchdemo/wikis/bca3f56df9aa1ff71991cf889062e980/w/",1615049225,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Test wiki **created** on [[ http://localhost/patchdemo | Patch Demo ]] by Ed using patch(es) linked to this task:
+
+http://localhost/patchdemo/wikis/ccf0f0ed62e0183bcd8312eb45d1ce97/w/",1615047467,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 665132 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] Detect NBSPs being inserted deliberately by IMEs
+
+https://gerrit.wikimedia.org/r/665132",1613669036,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 255937 **restored** by Bartosz Dziewoński:
+[mediawiki/extensions/VisualEditor@master] Add command to insert non-breaking space, triggered by Ctrl+Space (PC) / Opt+Space (Mac)
+
+https://gerrit.wikimedia.org/r/255937",1613074784,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"I have a related remark. Even though the editor does not provide itself a keyboard shortcut to insert no-break spaces, your keyboard layout might allow you to write no-break spaces. If you’re in this case, an editor-provided keyboard shortcut to insert no-break spaces is completely unneeded.
+
+The ‘French (alternative)’ keyboard layout (it’s its name on Linux) allows to insert no-break spaces with AltGr-Shift-Space. Personally I use the ‘Bépo’ keyboard layout (a Dvorak-like for French) which allows to type no-break spaces with Shift-Space. But it doesn’t work in the VisualEditor (both in visual and wikitext modes): it inserts a normal space. However it works with the classic (2013?) wikitext editor. It is very weird, because I can type no-break spaces everywhere else on my system, except in some rich-text web editors (I have the same problem with WordPress). I’m very curious about the source of that bug. It might be something else though, that would need its own bug report.
+
+You can test the ‘French (alternative)’ keyboard layout easily on Linux by typing `setxkbmap fr oss` in a terminal. (Under Windows you must install it: use [[ http://mjulier.free.fr/clavier/clavier_fr-ossc.zip | this archive ]] linked from [[ https://fr.wikipedia.org/wiki/Aide:Lettres_accentu%C3%A9es#Avec_des_dispositions_de_clavier_am%C3%A9lior%C3%A9es | this Wikipedia page ]].)
+
+Actually… OK, I just figured out it’s a Firefox bug with the `contenteditable=""true""`. Typing no-break spaces does work in Chromium.",1556057434,PHID-USER-2fha2mym5lty6djs2qfl,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"I have a related remark. Even though the editor does not provide itself a keyboard shortcut to insert no-break spaces, your keyboard layout might allow you to write no-break spaces. If you’re in this case, an editor-provided keyboard shortcut to insert no-break spaces is completely unneeded.
+
+The ‘French (alternative)’ keyboard layout (it’s its name on Linux) allows to insert no-break spaces with AltGr-Shift-Space. Personally I use the ‘Bépo’ keyboard layout (a Dvorak-like for French) which allows to type no-break spaces with Shift-Space. But it doesn’t work in the VisualEditor (both in visual and wikitext modes): it inserts a normal space. However it works with the classic (2013?) wikitext editor. It is very weird, because I can type no-break spaces everywhere else on my system, except in some rich-text web editors (I have the same problem with WordPress). I’m very curious about the source of that bug. It might be something else though, that would need its own bug report.
+
+You can test the ‘French (alternative)’ keyboard layout easily on Linux by typing `setxkbmap fr oss` in a terminal. (Under Windows you must install it: use [[ http://mjulier.free.fr/clavier/clavier_fr-ossc.zip | this archive ]] linked from [[ https://fr.wikipedia.org/wiki/Aide:Lettres_accentu%C3%A9es#Avec_des_dispositions_de_clavier_am%C3%A9lior%C3%A9es | this Wikipedia page ]].)",1556057144,PHID-USER-2fha2mym5lty6djs2qfl,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"@Nnemo: +1 for Ctrl-Shift-Space which also works on LibreOffice.
+
+>>! In T53045#1244827, @Nnemo wrote:
+> # « The safe places for french quotes » do not work in the visual editor — this is a bug, by the way. 
+
+//All// the safe places fail in the visual editor. I sometimes have line breaks before colons, semicolons, etc.
+
+>>! In T53045#1757181, @Esanders wrote:
+> Or you could somehow annotate the whole word as nowrap. Arguably <nowrap>100 °C</nowrap> would be clearer than 100&nbsp;°C
+
+Forget `<nowrap>`. There’s an already existing HTML4 `<nobr>` tag. To me it would be relevant that MediaWiki supports it; MDN says it’s non-standard (while it’s supported by all browser engines), that may be the reason. The behavior you were looking for can still be obtained with code like what [[ https://en.wikipedia.org/wiki/Template:Nowrap | this template ]] uses.",1556056383,PHID-USER-2fha2mym5lty6djs2qfl,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),">>! In T53045#1953183, @Nnemo wrote:
+> Regarding Ctrl Space on PC, would Ctrl Shift Space work as well? It would be good.
+
+Yes, that patch actually used both of these combinations, but space in the commit summary is limited ;)",1453407360,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),">>! In T53045#1837188, @gerritbot wrote:
+> Change 255937 had a related patch set uploaded (by Bartosz Dziewoński):
+> Add command to insert non-breaking space, triggered by Ctrl Space (PC) / Opt Space (Mac)
+> 
+> [[https://gerrit.wikimedia.org/r/255937]]
+
+Option Space on Mac is a good combination. Regarding Ctrl Space on PC, would Ctrl Shift Space work as well? It would be good.
+",1453407233,PHID-USER-fjve3gq5wsmaaccti7pb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"If those are blockers, can they be listed as such?",1453297794,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 255937 abandoned by Bartosz Dziewoński:
+Add command to insert non-breaking space, triggered by Ctrl Space (PC) / Opt Space (Mac)
+
+Reason:
+This doesn't seem to be moving forward. And last time I checked, non-breaking spaces in VE-MW (implemented as MWEntity) had a bunch of problems like T119838, T119839, T119840; so we wouldn't really want to point users towards them without fixing that first.
+
+[[https://gerrit.wikimedia.org/r/255937]]",1453297689,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),I also think CTRL+space is quite a high profile shortcut to assign to a relatively uncommon feature.,1448822067,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 255937 had a related patch set uploaded (by Bartosz Dziewoński):
+Add command to insert non-breaking space, triggered by Ctrl Space (PC) / Opt Space (Mac)
+
+[[https://gerrit.wikimedia.org/r/255937]]
+",1448820160,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),">>! In T70429#1224015, @Esanders wrote:
+> Or you could somehow annotate the whole word as nowrap. Arguably <nowrap>100 °C</nowrap> would be clearer than 100&nbsp;°C
+",1445953865,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),">>! In T53045#1232726, @Ltrlg wrote:
+> Inserting only the character is not persistent: there is at least one browser which replaces non-breaking spaces with normal spaces in `<textearea>`s (may be Firefox? don’t remember). See [[https://fr.wikipedia.org/w/index.php?diff=114391750&oldid=114391708|this diff]] for an example of such a replacement (I read unfortunately more talk pages than articles and don’t remember an recent example in ns-0).
+
+//Sometimes//, a replacement of non-breaking spaces with normal spaces in the text area occurs (occurred). This is (was) caused by a bug of Firefox, that was fixed years ago. Now, this happens rarely, because people having a fossil Firefox are rare. Over time, such replacements will be rarer and rarer.
+
+>>! In T53045#1232726, @Ltrlg wrote:
+> Of course there are safe places (before colons, inside French quotations marks) where MediaWiki does not require a special space to render a non-breaking one and where it would make no difference.
+
+These safe places exist. //But ://
+
+# I think that these safe places are a setup specific to the site fr.wikipedia.org, and do not apply in the general case of a MediaWiki. I may be wrong here. 
+# These safe places do not work in links. 
+# These safe places do not work in wikicode. 
+# « The safe places for french quotes » do not work in the visual editor — this is a bug, by the way. 
+",1430308930,PHID-USER-fjve3gq5wsmaaccti7pb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Inserting only the character is not persistent: there is at least one browser which replaces non-breaking spaces with normal spaces in `<textearea>`s (may be Firefox? don’t remember). See [[https://fr.wikipedia.org/w/index.php?diff=114391750&oldid=114391708|this diff]] for an example of such a replacement (I read unfortunately more talk pages than articles and don’t remember an recent example in ns-0).
+
+Of course there are safe places (before colons, inside French quotations marks) where MediaWiki does not require a special space to render a non-breaking one and where it would make no difference.",1429827478,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Inserting only the character is not persistent: there is at least one browser which replaces non-breaking spaces with normal spaces in `<textearea>`s (may be Firefox? don’t remember). See [[https://fr.wikipedia.org/w/index.php?diff=114391750&oldid=114391708|this diff]] for an example of such a replacement (I read unfortunately more talk pages than articles and don’t remember an recent example in ns-0).
+
+Of course there are safe places (before colons, inside French quotations marks) where MediaWiki does not require the a special space to render a non-braking one and where it would make no difference.",1429827443,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"For this feature, something would need to be clarified :
+
+What would the keyboard combination insert in the wikicode ?
+
+# The character non-breaking space 
+# The HTML entity ##&nbsp;## 
+
+These are two different things.
+
+For this feature, I would recommend inserting the character non-breaking space. Inserting the non-breaking space character leaves the wikicode natural and readable. Well, as readable as the wikicode already is. ;-) 
+
+",1429807031,PHID-USER-fjve3gq5wsmaaccti7pb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"For this feature, I suggest Ctrl Shift Space rather than Ctrl Space.
+
+Reasons :
+
+# Ctrl Space is already taken for Spotlight on Mac. 
+# The Word feature for entering a non-breaking space is pressing Ctrl Shift Space. 
+
+The Word feature is quite well known. Having an inconsistency here would confuse users.
+",1429806239,PHID-USER-fjve3gq5wsmaaccti7pb,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),Related: https://phabricator.wikimedia.org/T70429,1425904145,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ability to switch image used whilst maintaining the caption and other settings,"You should be able not only to change image caption, but select another image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54285",1373372220,PHID-USER-s2t4lzis4swnj7hbvkgn,PHID-TASK-cq56uabry7nuedxb56e6,task_description,resolved
+VisualEditor: Ability to switch image used whilst maintaining the caption and other settings,*** Bug 52580 has been marked as a duplicate of this bug. ***,1402608867,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cq56uabry7nuedxb56e6,task_subcomment,NA
+VisualEditor: Ability to switch image used whilst maintaining the caption and other settings,*** Bug 53409 has been marked as a duplicate of this bug. ***,1377621974,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-cq56uabry7nuedxb56e6,task_subcomment,NA
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title","Try to add image to http://uk.wikipedia.org/wiki/29er_(%D0%B2%D0%B5%D0%BB%D0%BE%D1%81%D0%B8%D0%BF%D0%B5%D0%B4) 
+
+It suggests no images for article ""29er (велосипед)"", but it will if you search by Commonscat template parameter or english interwiki
+
+--------------------------
+**See Also**:
+{T54464}",1373372040,PHID-USER-s2t4lzis4swnj7hbvkgn,PHID-TASK-faz57akdhnnsrbbitdmo,task_description,open
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title","It probably should be tagged with it. Sorry, VE tasks are often not consistently tagged (other than with the #visualeditor tag).",1551212560,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-faz57akdhnnsrbbitdmo,task_subcomment,NA
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title","@matmarex thanks for finding this, I did look before filing but this task wasn't tagged with #visualeditor-media, is that the right tag? ",1551207441,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-faz57akdhnnsrbbitdmo,task_subcomment,NA
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title","I don't think this would require T68108. It seems possible to implement today (although maybe inefficient…)
+* Given a page e.g. https://en.wikipedia.org/wiki/The_Fighting_Temeraire, look up its Wikidata entry e.g. https://www.wikidata.org/wiki/Q257580
+* Given the Wikidata entry, look up the Commons gallery/category using the 'commons' sitelink, or the category using the ""Commons category"" (`P373`) property
+* Given the Commons category, show search results from it (maybe using [[https://www.mediawiki.org/wiki/Help:CirrusSearch#Intitle_and_incategory|incategory:]] search)",1551206616,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-faz57akdhnnsrbbitdmo,task_subcomment,NA
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title",I think doing this via Wikidata identity would be a better way forward.,1385398709,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-faz57akdhnnsrbbitdmo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,"Two editors have commented independent in different place over the weekend on English Wikipedia about how they wish they could access the edit summary while using the VE instead of on save, because they track their changes as they go.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373304120,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_description,open
+VisualEditor: Provide simultaneous access to editor and edit summary,@Sadads has suggested that the Tab key be used to switch between the article and the edit summary window.,1482427198,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,(Aaand there's an exception for that. See T114857.),1444222841,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,"(Although they won't be able to do so if they enabled the warning that doesn't allow to save without providing an edit summary, as noted at de.wiki. )",1444153431,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,"On a related note: There's also no edit summary in the diff view (""review you changes""), just a save button. This tempts users to save without leaving an edit summary.",1443996374,PHID-USER-ctff2aq5r64yvikejdwo,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,"Think this is also happening on PL.WP. 
+
+""Jeśli w okienku z polem służącym do opisu dokonanej zmiany klikniemy w link dotyczący sposobu opisywania zmian zostaniemy przekeierowani do strony Wikipedii z opisem tychże skrótów, jednak strona ta wyświetla się w tym samym małym okienku. Uniemożliwia to powrócenie to opisu modyfikacji a jednocześnie uniemożliwia zapisanie dokonanej zmiany w danym artykule. Michał (dyskusja) 11:36, 5 lis 2013 (CET)""
+
+https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#B.C5.82.C4.85d_w_okienku_opisu_zmian.",1383663034,PHID-USER-brn4v5ta45bnw4f5as3h,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,+1. This is a particularly useful feature of the old editor.,1374780006,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Reduce padding in editnotice popup because some existing edit notices already have some margin,"An editor from pt.wikipedia writes:
+
+[E]ditnotices seems strange inside the flyout because there's a weird padding inside the popup, without the padding the templates would look nicer (there´s already padding in most edinotices templates by default). Dianakc (talk) 23:56, 6 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373302800,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-yxjf5ed7ojxtui2z6sss,task_description,open
+VisualEditor: Reduce padding in editnotice popup because some existing edit notices already have some margin,"(In reply to comment #2)
+> Hi James,
+> 
+> I don't know what mean you by normal edit notices :) A simple 100% div, with
+> background color but without padding would look weird inside the flyout.
+> We are rethinking the editnotices design/content and right now they look
+> somewhat awkward within this asymmetrical padding. If someone ever need a
+> margin it can be done within the editnotices itself, but this mandatory
+> padding
+> limits the design a lot.
+
+Normal edit notices are text only (or bold/italics/links). Adding any further styling, including <span>s, <div>s, images, etc. is likely to break in a variety of situations and isn't really intended behaviour for the tool.",1379846011,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yxjf5ed7ojxtui2z6sss,task_subcomment,NA
+VisualEditor: Reduce padding in editnotice popup because some existing edit notices already have some margin,"Hi James,
+
+I don't know what mean you by normal edit notices :) A simple 100% div, with background color but without padding would look weird inside the flyout.
+We are rethinking the editnotices design/content and right now they look somewhat awkward within this asymmetrical padding. If someone ever need a margin it can be done within the editnotices itself, but this mandatory padding limits the design a lot.",1375490603,PHID-USER-2u4zc7zmyw5qldxupou6,PHID-TASK-yxjf5ed7ojxtui2z6sss,task_subcomment,NA
+VisualEditor: Reduce padding in editnotice popup because some existing edit notices already have some margin,"(In reply to comment #0)
+> An editor from pt.wikipedia writes:
+> 
+> [E]ditnotices seems strange inside the flyout because there's a weird padding
+> inside the popup, without the padding the templates would look nicer (there´s
+> already padding in most edinotices templates by default). Dianakc (talk)
+> 23:56,
+> 6 July 2013 (UTC)
+
+I'm not sure that it's a better solution to get editors to make edit notices in uneditable HTML boxes, rather than the padding be system-level. The padding is designed to take normal edit notices; if you make fancy ones that break, the onus is generally on you. :-)
+
+Note that we're planning on having setting/editing/removing page-level edit notices built into VisualEditor in the next few months, which will make enwiki's solution available to all wikis.",1373303074,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yxjf5ed7ojxtui2z6sss,task_subcomment,NA
+Messing up Math formulas,"Several concerns noted about VisualEditor messing with math formulas when (evidently) the user was not attempting to edit the formula at all.
+
+https://en.wikipedia.org/w/index.php?title=Raising_and_lowering_indices&curid=11325244&diff=563062676&oldid=560490441
+
+https://en.wikipedia.org/w/index.php?title=Regression_analysis&curid=826997&diff=563265603&oldid=561802206
+
+https://en.wikipedia.org/w/index.php?title=Bipartite_double_cover&curid=21241712&diff=563327691&oldid=554035797
+
+I'm not sure if this is related to an existing bug or a different kind of thing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373289300,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-tlllnzr2q3k5zu3yv6nh,task_description,resolved
+Messing up Math formulas,"**cbm.wikipedia** wrote:
+
+This is a duplicate of bug 50291. It is a round tripping error in VisualEditor.
+
+%%%*** This bug has been marked as a duplicate of bug 50291 ***%%%",1373592757,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-tlllnzr2q3k5zu3yv6nh,task_subcomment,NA
+Messing up Math formulas,"The changes don't actually change the visual output. Just the way italics (used to mark variables) and superscript and subscript tags interact. So it might change ''e''<sup>''x''</sup> to ''e<sup>x</sup>'' you could say the former is better semantically. Other cases will split a complex superscript into two separate subscripts  ''K''<sub>''n'',''n''</sub> into ''K<sub>n</sub>''<sub>,''n''</sub>, visually the same but worse semantically.
+
+Marking as low priority as no visible change.",1373290493,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-tlllnzr2q3k5zu3yv6nh,task_subcomment,NA
+"VisualEditor: License text in save dialog is light gray, giving it a 'disabled' appearance","The save dialog uses a gray color on a very small text. This isn't good for contrast, and gives it rather 'light' color which might communicate a 'disabled' state to some users, which you don't want with a license text.
+
+Just as with Special:UserLogin, I think we should switch to a slightly darker gray on small text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373232780,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-3ydcw352v55xv74m7jhi,task_description,resolved
+"VisualEditor: License text in save dialog is light gray, giving it a 'disabled' appearance",This has been [[ https://phabricator.wikimedia.org/rEVED48db1c16f81091f62d82539b2a41fede49ba7915 | changed to `#54595d` in wmf/1.29.0-wmf.7 ]] and fulfills WCAG 2.0 level AAA conformance.,1483659684,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-3ydcw352v55xv74m7jhi,task_subcomment,NA
+"VisualEditor: License text in save dialog is light gray, giving it a 'disabled' appearance",The meta-design of the save process for wikitext and for VisualEditor are being reviewed by Design and by Legal right now; hopefully there'll be an update soon enough.,1385380440,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3ydcw352v55xv74m7jhi,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"Perhaps when the [[WP:Tutorial]] on enwiki is updated for VE, we will want to enable VE on the tutorial sandboxes.
+
+Also, when VE is enabled for anonymous editors, we might want to turn on VE in the enwiki [[WP:Sandbox]], because otherwise anons won't have anywhere to play with VE (they cannot create user pages).
+
+Perhaps a category (similar to the way AFTv5 does it) or MediaWiki page (like Echo blacklist) would be the way to do it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373193180,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-cudr7dbtubp7jj3ldgha,task_description,open
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"It’s great that enabling VE in Wikipedia namespace is less risky now, but I think the current feature request (enabling it more granularly than on the namespace level) is still valid, exactly because of the limitations (risks) you’ve mentioned.",1722169176,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"Turning VE on at Wikipedia: namespace was a problem as some pages at this namespace are used for discussions. The visual editor is not designed to handle discussions, but Discussion tools are. Now that DT is available everywhere,[[ https://www.mediawiki.org/wiki/Help:VisualEditor/FAQ#WPNS |  it is possible to enable VE at namespaces that are used for discussions, with limitations ]]. ",1721988681,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"This is a huge pain point, newbies cannot try out the tool in the sandbox that was created specifically for them…
+
+>>! In T52883#5193760, @matmarex wrote:
+> You can put a big blue button or something with such a link on sandbox pages, see e.g. <https://de.wikipedia.org/wiki/Wikipedia:Spielwiese>.
+This has three issues:
+* The link is not where it is on other pages. On the one side, it’s more prominent, which is good, but on the other side, it’s inconsistent, which is bad.
+* It uses an external link, which means that
+** the domain name is fixed, it’s `de.wikipedia.org` even if the user browses through `de.m.wikipedia.org` (i.e. mobile view); if they’re not redirected back to the mobile site automatically, they find themselves in a totally different interface than where they were;
+** a new page load is initiated upon clicking, in contrast to the usual VE loading, where the page isn’t entirely reloaded.",1624489831,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"Also, note that the &veaction=edit URL parameter can now also be used to open VE on pages where it's normally not available (T221892). You can put a big blue button or something with such a link on sandbox pages, see e.g. <https://de.wikipedia.org/wiki/Wikipedia:Spielwiese>.",1558194860,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"If we ever do it, I think it should be done using a double-underscore keyword placed on the page (or in a transcluded template), e.g. `__VISUALEDITOR__`. This would be analogous to e.g. the `__NEWSECTIONLINK__` keyword.",1558194738,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"While bug 55900 now allows logged-out users to invoke VE in the namespaces where it is already available, in the meantime I hope communities created temporary sandboxes in one of said namespaces :) (The Italian one did, it's basically a subpage of mine).",1388962544,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"For the record: on ptwiki we also have a few sandboxes on Project namespace:
+[[pt:Special:PrefixIndex/WP:Página_de_testes/]]",1373856039,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"**Author:** `KilliondudeWP`
+
+**Description:**
+1) Have categories on a page with a stub tag underneath - https://en.wikipedia.org/w/index.php?title=Rosebud_Ranch&oldid=563208475 (note that this is SOP on enwiki per https://en.wikipedia.org/wiki/Wikipedia:ORDER#ORDER )
+
+2) Edit the categories using VE to deleted one and modify another - https://en.wikipedia.org/w/index.php?title=Rosebud_Ranch&diff=563208669&oldid=563208475
+
+3) End up with newly formed category underneath the stub template as well as some line breaks taken out. 
+
+I reported this in #mediawiki-visualeditor while everyone was sleeping. This is something that might just need an enwiki fix since we like to put stub tags under categories.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+* {T51143}
+* {T55508}
+* {T74048}",1373181360,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zg7dy72bmhpynpamskgq,task_description,open
+VisualEditor: Place page meta-data in expected order,"There's also an inconsistency in how VE inserts `{{DEFAULTSORT}}` and categories.
+
+If you edit the page's properties to add a `{{DEFAULTSORT}}`, apply, then edit the properties again to add a category, then the `{{DEFAULTSORT}}` is added before the category, as is usually expected based on community guidelines.
+
+However, if you do the sequence in the other order (add a category first, apply, then edit the properties again to add a `{{DEFAULTSORT}}`), then the `{{DEFAULTSORT}}` is added //after// the categories.
+
+Since the user doesn' t have a way to specify or change that order, VE should be consistent in how it outputs them in the wikitext.
+",1428688398,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,*** Bug 51714 has been marked as a duplicate of this bug. ***,1377833797,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"The reasons behind [[WP:ORDER]] are:
+1) We want ""stub categories"" to appear Last in the list of categories.
+2) We want 2 blank lines preceding stub-templates, for whitespace. (Other ways of achieving this are more complex, or don't work for articles with multiple stub-templates.)
+See example of both factors, at http://en.wikipedia.org/w/index.php?title=Milo_McCarger&oldid=532917627
+
+
+(To quote the [[WP:ORDER]] reference here, for ease of access: ""While categories are entered on the editing page ahead of stub templates, they appear on the visual page in a separate box after the stub templates. One of the reasons this happens is that every stub template generates a stub category, and those stub categories appear after the ""main"" categories. Another is that certain bots and scripts are set up to expect the cats, stubs and ILLs to appear in that order, and will reposition them if they don't. Therefore, any manual attempt to change the order is doomed unless the bots and scripts are also altered."")",1373650166,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"(In reply to comment #2)
+> The problem here is not specifically ""stub templates"", but the general idea
+> that some items of content - in this case, on one wiki, a sub-type of
+> template that is trivially-identifiable to humans but not necessarily so for
+> software - should have its own special ordering when the page is
+> re-serialised. The explanation for why this (relatively new?) policy change
+> for enwiki seems to be absent [...]
+
+This practice has been documented at [[WP:LAYOUT]] for at least a few years. It's been standard practice since before then. There's a note in the current version of that document that explains that it's due to a battle with bots (notable AutoWikiBrowser, as I recall). Because most people add stub categories with AWB or similar scripts, the conventions those tools use become (or rather, became) wiki conventions.
+
+I agree with the general point that we should move this type of information (whether a page is a stub and if so, what kind of stub) to a metadata area.",1373422161,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,Moving back to VE as this is handled in VE until we move metadata out of the body.,1373400958,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"In the medium term I'd like to move metadata like categories out of the page and into a header section (see bug 49143).
+
+In the meantime, we serialize metadata wherever the VE places it in the DOM.",1373400711,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"I've re-titled this bug to ""Provide a way for Parsoid to know that some types of some content on some wikis go after the meta-data, not in the body of the document"", which I think captures the 'ask' here most generally. I believe that currently, Parsoid puts all content first, followed by meta-data in the order ""Magic words (e.g. DEFAULTSORT) > Categories > Language links"", which is MediaWiki standard style.
+
+The problem here is not specifically ""stub templates"", but the general idea that some items of content - in this case, on one wiki, a sub-type of template that is trivially-identifiable to humans but not necessarily so for software - should have its own special ordering when the page is re-serialised. The explanation for why this (relatively new?) policy change for enwiki seems to be absent, unlike for the other elements; it adds complexity without justifying why, as far as I can see.
+
+I think it is unlikely that we will change things so that Parsoid has an understanding of what kinds of content it is dealing with, much less a concept of per-wiki settings for where the content should be positioned. Just because the English Wikipedia likes things one way doesn't mean we should impose those standards on everyone else - for example, another wiki might like their categories at the top, or their semi-structured data template (like PERSONDATA) at the very bottom, or… any one of countless other possible orderings that don't effect readers. Remember that VisualEditor is currently available on 300 wikis, and is being developed for all ~900 Wikimedia wikis, the ~300,000 Wikia wikis, and numerous other wikis as well.
+
+This is not saying that this request is impossible, that the barriers are insurmountable, that it will never be done, or that our mind is set for ever on this matter. However, coming up with a system for specifying this on a per-wiki basis, and justifying us spending (significant) developer time adding complexity and confusion to the code and the user interfaces is going to be challenging. This is time that would otherwise be spent on fixing bugs, on editing tables, on a better reference dialog, on supporting language variants as used in (e.g.) Chinese. I don't think that we can prioritise this above these other issues; sorry.",1373395467,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"This is not minor, unless enwiki has agreed to abandon the long-established rules set out in http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Layout#Order_of_sections . I have just added a category to [[Permyak Salty Ears]] (it's a sculpture I was stub-sorting), and it has been put below the stub tag and interwiki link, and not adjacent to two existing categories. 
+
+There are also rules for the top of the article: navigational hatnotes go before anything else. Not in VE. WP:AWB sorts these out misplaced elements as part of ""General fixes""; Twinkle can put a newly-added maintenance tag within the {{tl|multiple issues}} tag. It is very disappointing that VE seems incapable of offering the same level of helpfulness as these existing systems have offered for years.",1373371153,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"When I edited an internal link and pasted in Work_breakdown_structure#Terminal_element as the new link target, the link editor widget thought that it was a new page, because it didn't understand that the # referenced an anchor within that page.
+
+However, that was just a harmless warning - it did work. So I am classifying this as minor severity, because it is merely an incorrect warning message that could confuse editors.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373173500,PHID-USER-bug3zrlooz3bdmi4fyl7,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_description,resolved
+VisualEditor: Link input widget should suggest section links,Filed remaining work as T367739,1718627142,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by ESanders (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/dacb60851e/w/ ]]~~",1713878088,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 975293 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Link inspector: Use searchFragments feature in TitleWidget%%%
+https://gerrit.wikimedia.org/r/975293",1701967466,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 975292 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] TitleWidget: Allow searching for section fragments%%%
+https://gerrit.wikimedia.org/r/975292",1701967461,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"3 & 4 are fixed. 1 is more complicated as it requires more interaction between VE and this core component (VE needs to override the list of available sections, rather than use an API call). I think that should probably be fixed later.",1701100973,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,">>! In T52881#9352286, @gerritbot wrote:
+> Change 976691 had a related patch set uploaded (by Sophivorus; author: Sophivorus):
+> %%%[mediawiki/extensions/ParserFunctions@REL1_39] Backport fix of implicit conversion to int%%%
+> https://gerrit.wikimedia.org/r/976691
+
+Tagged the wrong bug, sorry.",1700655480,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 976691 had a related patch set uploaded (by Sophivorus; author: Sophivorus):
+%%%[mediawiki/extensions/ParserFunctions@REL1_39] Backport fix of implicit conversion to int%%%
+https://gerrit.wikimedia.org/r/976691",1700655252,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Thanks for the feedback.
+1 sounds useful and should be fixable.
+I think points 2-3 can be addressed later in follow ups.
+4 should be fixed, we should replace underscores when normalising.
+5: if you start typing # immediately you get no page name. Removing the page name could arguably be a Parsoid job, or something we should leave in if the user types it explicitly, but we could remove it locally.",1700639837,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Really nice UX! 🙂
+Some minor limitations I noted:
+- Added/edited headings in the current editing session are not reachable.
+- Since selecting the target page with directional keys does not fill the text input (what a browser URL bar usually does), in order to link an external section without fully typing the target page name, you have to first add a link to the page name, then edit it to add the fragment.
+- For local page section suggestions, a middle click opens the page in visual editing mode rather than reading mode like for external sections.
+- It does not recognize underscore as space equivalent; so copying the fragment from a URL looks like it is not an existing section.
+- For local sections, the resulting wikitext uselessly adds page name before fragment. (T239847)",1700257312,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+[[ https://patchdemo.wmflabs.org/wikis/dacb60851e/wiki/Douglas Adams?veaction=edit ]]",1700234169,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 975293 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Link inspector: Use searchFragments feature in TitleWidget%%%
+https://gerrit.wikimedia.org/r/975293",1700233938,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 975292 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/core@master] TitleWidget: Allow searching for section fragments%%%
+https://gerrit.wikimedia.org/r/975292",1700233858,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"When adding links to sections in the current page, the UI may be a third tab in the Link popup (after the ""Search pages"" and ""External link"" tabs) called ""Section link"" (or similar). In this tab, the existing section titles would be listed (possibly in a hierarchical TOC fashion) and clicking on a section would add a link to that section.",1529619847,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"{T112898} has been fixed but `[[#section|text]]` just inserted is still red (all the same, it displays correctly for links which were already present before loading VisualEditor).",1470731559,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,*** Bug 61428 has been marked as a duplicate of this bug. ***,1401417280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"(In reply to comment #11)
+> John reports today that ""It used to be possible, in VE, to link to another
+> section of a page (say, Bank#History). Now, when section information is
+> added,
+> in the Link/Hyperlink dialog box, VE just deletes it when the user presses
+> [return] or exits (in any way) that dialog box.""
+
+Noting for posterity that that was bug 53219, which has now been fixed.",1377527665,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"John reports today that ""It used to be possible, in VE, to link to another section of a page (say, Bank#History). Now, when section information is added, in the Link/Hyperlink dialog box, VE just deletes it when the user presses [return] or exits (in any way) that dialog box.""",1377170602,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"The VE software has changed (at least a week ago, maybe longer) for this issue. Now pressing [Return] does not remove the ""#Whatever"" text that the user typed, for the section link. So this bug is now primarily a display issue.
+
+(In reply to comment #7)
+> This isn't just a display problem, and it is NOT an enhancement - it's a real
+> defect because editors are unlikely to take the time - as I did - to figure
+> out
+> how to make section links work.
+> 
+> Here's what happens now: The editor finds an article to link to (good UI;
+> much
+> better than the wikitext editor); then he/she starts typing the section link
+> (#whatever). The link name turns red (that's the display issue), and it
+> doesn't
+> suggest section names (that would be a really slick enhancement; if you do
+> this
+> well, people are going to love you). Instead, when the editor is done typing
+> the section information, one of four things can happen:
+> 
+> * The editor presses Enter/Return (per the user guide), and the section
+> information is REMOVED by VE. That is clearly a defect in the software.
+> 
+> * The editor presses the close icon (<) (per the user guide), and the section
+> information is REMOVED by VE. That is clearly a defect in the software.
+> 
+> * The editor clicks somewhere else on the page, and the section information
+> is
+> REMOVED by VE. That is clearly a defect in the software.
+> 
+> * The editor clicks on the area ABOVE the input box, the area containing the
+> word ""Hyperlink"", and VE is happy, and saves the section information. (I'm
+> going to add that to the user guide, but that wouldn't do nearly as much good
+> as changing, in the software, what happens in the first three situations,
+> above.",1375822006,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,The suggestion of the sections that can be linked are also requested at it.wp.,1375739703,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,*** Bug 51445 has been marked as a duplicate of this bug. ***,1374029473,PHID-USER-fwlidikyeorzj35hufwu,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"This isn't just a display problem, and it is NOT an enhancement - it's a real defect because editors are unlikely to take the time - as I did - to figure out how to make section links work.
+
+Here's what happens now: The editor finds an article to link to (good UI; much better than the wikitext editor); then he/she starts typing the section link (#whatever). The link name turns red (that's the display issue), and it doesn't suggest section names (that would be a really slick enhancement; if you do this well, people are going to love you). Instead, when the editor is done typing the section information, one of four things can happen:
+
+* The editor presses Enter/Return (per the user guide), and the section information is REMOVED by VE. That is clearly a defect in the software.
+
+* The editor presses the close icon (<) (per the user guide), and the section information is REMOVED by VE. That is clearly a defect in the software.
+
+* The editor clicks somewhere else on the page, and the section information is REMOVED by VE. That is clearly a defect in the software.
+
+* The editor clicks on the area ABOVE the input box, the area containing the word ""Hyperlink"", and VE is happy, and saves the section information. (I'm going to add that to the user guide, but that wouldn't do nearly as much good as changing, in the software, what happens in the first three situations, above.",1373991618,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,Worth noting here the comments on bug 50945 about cases where display text != link text (piped links),1373526525,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,*** Bug 51121 has been marked as a duplicate of this bug. ***,1373520194,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"(In reply to comment #3)
+> When reporting the duplicate bug (sorry, this one didn't come up in my
+> search)
+
+Don't worry, it's my fault for not triaging earlier. :-)
+
+> I wondered whether this was related to Bug 33094
+
+I don't believe so (though we should get that fixed soon too, of course).",1373518375,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"When reporting the duplicate bug (sorry, this one didn't come up in my search) I wondered whether this was related to Bug 33094",1373476336,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,*** Bug 51118 has been marked as a duplicate of this bug. ***,1373475138,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"* The link inspector needs to understand that if Foo exists, linking to Foo#Bar isn't a red link
+* Ideally the link inspector should have introspection of articles' sections so that it can suggest which headings to link to
+* This should also work for naked (local) section links - i.e., linking to just #Bar on the local page.",1373475114,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+Difficult for users to know what exact version of each extension is running on the cluster,"This bug was cloned from bug 50120.
+
+(In reply to bug 50120 comment #5)
+> We believe that this is now fixed (due to fixes in Parsoid). Please re-open
+> if it recurs.
+
+How do you know what version of VisualEditor or Parsoid is running? Looking at Erik's comment (bug 50120 comment 6), I try to go to [[Special:Version]] to figure out what exact versions of Parsoid and VisualEditor are running (for debugging purposes and to figure out if this problem is still present in the latest bleeding edge code) and I find that Parsoid and VisualEditor are both marked as version 0.1.0. Not quite helpful for debugging. Splitting this issue out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373161140,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-grvae3imieydt4li7k7h,task_description,resolved
+Difficult for users to know what exact version of each extension is running on the cluster,"With bug 53972 now fixed, this is now fixed in Beta Labs (see http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version for git hashes against each extension), and for VisualEditor specifically (which was the original locus of this suggestion) it's also available at the bottom of the ""help"" menu.",1404841447,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-grvae3imieydt4li7k7h,task_subcomment,NA
+Difficult for users to know what exact version of each extension is running on the cluster,"(In reply to comment #1)
+> Could we switch on the configuration we have on beta labs for Special:Version
+> for other wikis? (Perhaps as a page option - ?showversions=true or whatever,
+> so as to avoid confusing users.)
+
+I'm not sure of the history here, but perhaps it could show the extra info only for logged-in users?",1373217143,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-grvae3imieydt4li7k7h,task_subcomment,NA
+Difficult for users to know what exact version of each extension is running on the cluster,"(In reply to comment #0)
+> This bug was cloned from bug 50120.
+> 
+> (In reply to bug 50120 comment #5)
+> > We believe that this is now fixed (due to fixes in Parsoid). Please re-open
+> > if it recurs.
+> 
+> How do you know what version of VisualEditor or Parsoid is running? Looking
+> at
+> Erik's comment (bug 50120 comment 6), I try to go to [[Special:Version]] to
+> figure out what exact versions of Parsoid and VisualEditor are running (for
+> debugging purposes and to figure out if this problem is still present in the
+> latest bleeding edge code) and I find that Parsoid and VisualEditor are both
+> marked as version 0.1.0. Not quite helpful for debugging. Splitting this
+> issue
+> out.
+
+This is a cluster configuration issue; it's trivial to find out which version of VisualEditor is running in Beta Labs, as each MW extension is shown in http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version with the date and a link to the git.wikimedia.org page of the currently-running commit. I don't think bumping version numbers on extensions with every deployment is a great idea, however.
+
+(Note that this doesn't help for Parsoid, however, as it's not actually an MW extension, despite the confusing repo name.)
+
+For ultra-power-users like me, I ""just"":
+
+* Find from Special:Version which branch the site I'm interested in is on
+* Look up in gerrit any changes to that branch since it was cut https://gerrit.wikimedia.org/r/#/q/status:merged+project:mediawiki/core+branch:wmf/1.22wmf8,n,z
+* Find the latest time the extension was updated in there based on commit title (hopefully helpful), or if never, from the original cut commit
+* Take that commit ID (in this case, ""11453371c637b50cd3f37e80893d9a80b0c044a5"") and sling it into gerrit (in this case, https://gerrit.wikimedia.org/r/#/q/11453371c637b50cd3f37e80893d9a80b0c044a5,n,z gives the result).
+* Success! Umm.
+
+However, this isn't remotely a great solution for even quite serious developers on staff or in the community, let alone regular users who might want to file bugs.
+
+Could we switch on the configuration we have on beta labs for Special:Version for other wikis? (Perhaps as a page option - ?showversions=true or whatever, so as to avoid confusing users.)",1373162213,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-grvae3imieydt4li7k7h,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"**Author:** `gigs`
+
+**Description:**
+I see that a cancel button has been added, which is an improvement, but the escape key should also cancel edit mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373132460,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-biusmqvxgixprlg4xp34,task_description,resolved
+Escape key inside the main editor should cancel VE mode and return to action=view,"@Alex42 Thanks for reporting this. I filed a separate task about it: {T302096}. This task is from almost 9 years ago, and the cause of the new problem is almost certainly not related.",1645206828,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"This feature worked as expected until now. The last time i remember it working correctly is a few month ago.
+
+But now it is broken and **no dialog** ""Are you sure?"" is shown any more, when pressing Esc key once. Yesterday i lost a [[ https://de.wikipedia.org/w/index.php?title=Kreditkarte&curid=18081&diff=220309975&oldid=217344355 | hour of work ]].
+
+Tested in main view of VisualEditor on fr-, de- and en-wiki with Firefox 97.0 (64-Bit) on Win10.
+
+See also this disussion: [[ https://en.wikipedia.org/wiki/User_talk:Nick_Moyes#ESC_key_in_VisualEditor | en-wiki:User_talk:Nick_Moyes#ESC_key_in_VisualEditor ]]",1645197042,PHID-USER-iaar5nh25gcynskxgwrr,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"This feature worked as expected until now. The last time i remember it working correctly is a few month ago.
+
+But now it is broken and **no dialog** ""Are you sure?"" is shown any more, when pressing Esc key once. Yesterday i lost a [[ https://de.wikipedia.org/w/index.php?title=Kreditkarte&curid=18081&diff=220309975&oldid=217344355 | hour of work ]].
+
+Tested in main view of VisualEditor on fr-, de- and en-wiki with Firefox 97.0 (64-Bit) on Win10.",1645177521,PHID-USER-iaar5nh25gcynskxgwrr,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"It is a somewhat traumatic experience when you press Esc too hard in a dialog (or try to use Esc to cancel text selection etc) and VE shows a helpful ""would you like me to irrecoverably throw away the result of your last three hours of work? Y/N"" dialog. It's probably not easy to confirm by accident but it's still a pretty bad feeling. Has this been through any user testing at all?",1545717996,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"The discussion above makes sense and I think the <escape> key feature as currently implemented is probably helpful to some people.  But as a user who heavily uses <esc> to get out of ""insert ..."" dialogs and so on, it's alternately scary and annoying that a hitting (any) key too many times threatens to cancel my changes without saving.
+
+I'm not sure what improvements to suggest.  On second thought...  There doesn't seem to be a Cancel button, which makes it arch-surprising that a keyboard shortcut would do so.  What about changing the behavior of <esc> to ""Save Changes"" instead?  This seems consistent and friendly.",1481102923,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"The discussion above makes sense and I think the <escape> key feature as currently implemented is probably helpful to some people.  But as a user who heavily uses <esc> to get out of ""insert ..."" dialogs and so on, it's alternately scary and annoying that a hitting the key too many times will threaten to cancel my changes without saving.
+
+I'm not sure what improvements to suggest.  On second thought...  There doesn't seem to be a Cancel button, which makes it arch-surprising that a keyboard shortcut would do so.  What about changing the behavior of <esc> to ""Save Changes"" instead?  This seems consistent and friendly.",1481102889,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,Verified in betalabs.  Escape key will bring a warning message  box 'Are you sure?',1417633671,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,">>! In T52868#805066, @Jdforrester-WMF wrote:
+> Resolution is determined by QA for features and bugs.
+
+Huh?",1417575813,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,Resolution is determined by QA for features and bugs.,1417573056,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Change 175869 merged by jenkins-bot:
+Cancel VE when escape key pressed
+
+[[https://gerrit.wikimedia.org/r/175869]]",1417566802,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Change 175868 merged by jenkins-bot:
+Dialog: Only handle escape events when open
+
+[[https://gerrit.wikimedia.org/r/175868]]",1416953583,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Change 175869 had a related patch set uploaded (by Alex Monk):
+Cancel VE when escape key pressed
+
+[[https://gerrit.wikimedia.org/r/175869]]
+
+#patch-for-review",1416953386,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Change 175868 had a related patch set uploaded (by Alex Monk):
+Dialog: Only handle escape events when open
+
+[[https://gerrit.wikimedia.org/r/175868]]
+
+#patch-for-review",1416953163,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"(In reply to WhatamIdoing from comment #11)
+> I'm a bit worried about this.  What if I'm in a template dialog and
+> accidentally press Esc twice/too long?  If this triggered the ""Do you really
+> wnt to exit?"" confirmation, it might be okay.  However, I suspect that this
+> might not have the ultimate effect that was intended.
+
+Comment 10 asks for the unsaved changes warning to be shown. If we do that, I think it'll be fine. Pressing escape while a dialog is open will dismiss that dialog with a safe action (the cancel/never mind action). So if you press escape again when the unsaved changes warning is visible, that'll dismiss the warning with the safe action, which is ""never mind, I want to continue editing"". So if you press Esc a bunch of times or hold it too long, you'll end up in a loop of the unsaved changes warning appearing and being dismissed.",1407973255,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"I'm a bit worried about this.  What if I'm in a template dialog and accidentally press Esc twice/too long?  If this triggered the ""Do you really wnt to exit?"" confirmation, it might be okay.  However, I suspect that this might not have the ultimate effect that was intended.",1407972909,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Yes, pressing escape when in a dialog should close that level of the dialog (if more than one) or the dialog if it's at the top level of the dialog. If a change was confirmed then it should remain when closed, if a change was unconfirmed it should be cancelled. 
+
+With no dialogs open, escape should exit VE but should ask for confirmation before doing so if there are unsaved changes. That dialog should have keyboard actions such that enter confirms you want to leave and escape indicates that you don't want to leave and take you back to the VE. This will stop people losing work if they hit esc accidentally or too many times.",1374027650,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,Clarify title so it's clear we all agree.,1373394497,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"**gigs** wrote:
+
+Agreed, that's how I envisioned it.",1373382255,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"I'd like to note that really this should only happen iff someone is exclusively in edit mode. IOW, if someone has opened the template inspector, close that. Link inspector, close that - so on and so forth.",1373361187,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"On macs, cancel is usually cmd-.
+
+Wouldn't mind having that in VE.",1373228712,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"I think this isn't a bad idea, though I'm a little troubled if this causes unexpected behaviour for users of some browsers.",1373145156,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"**gigs** wrote:
+
+OK, but my next question is: What form fields are people going to be interacting with when in the main Visualeditor?  The only form field I see is the search box.",1373143309,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Opera does that; it's useful enough that I expected other browsers to behave similarly. IE8 resets the value to the default (for both inputs and textareas). And Firefox apparently doesn't do anything, like you said.",1373139445,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"**gigs** wrote:
+
+What browsers?  Not Chrome or Firefox.  I don't have IE here to test with, but I doubt it does it either.
+
+http://www.w3schools.com/jquery/tryit.asp?filename=tryjquery_event_blur_alert",1373136114,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,The escape key is used by browsers to defocus (blur) currently focused form element. Reusing it for this would be really annoying.,1373132960,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+VisualEditor: Transclusions editor should support parser functions and variables,"Parser function syntax is generally {{#function_name : expr1 | expr2 | expr3 | ...}}
+
+Currently VE sees this as a template with name ""#function_name : expr1"" and arguments ""1 = expr2"", ""2 = expr3"", etc. This makes it impossible to edit expr1 in VE.
+
+Same for parserfunctions like urlencode and template messages. The transclusions editor should be able to handle them, preferably by invisibly detecting them and failing that with a special, user-selected mode. Until we can, we should show an explanatory message when the user attempts to add one. 
+
+**See also:**
+{T54607}",1373104140,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-5tthiu6szwn225okbzla,task_description,open
+VisualEditor: Transclusions editor should support parser functions and variables,"So yeah. Matma Rex has merged T249860 with this task. Also, I will add details about this task on [[ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor | Wikipedia:VisualEditor ]].",1587917120,PHID-USER-wmk4bsljm5c77zhckwcj,PHID-TASK-5tthiu6szwn225okbzla,task_subcomment,NA
+VisualEditor: Transclusions editor should support parser functions and variables,"If Parsoid doesn't automatically tell VE whether something is a template or not, could it not be done by looking at the format of the string (e.g. {{# is never a template) or comparing it to a list of parser functions?",1435260148,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-5tthiu6szwn225okbzla,task_subcomment,NA
+VisualEditor: Transclusions editor should support parser functions and variables,"Many of the parser functions are rarely used in the main namespace (#if, ...), but some of them are really important even in the main namespace. For example {{formatnum:...}} is probably used a lot there.",1373465761,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-5tthiu6szwn225okbzla,task_subcomment,NA
+VisualEditor: Transclusions editor should support parser functions and variables,"Yes, we need a special form of editing transclusions which aren't templates; I can't recall whether Parsoid gives us sufficient information to recognise these as different except for introspection.",1373160763,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5tthiu6szwn225okbzla,task_subcomment,NA
+VisualEditor: Provide integration as an API service,"Original Bug title: 
+Provide an API to activate VE on arbitrary textareas for Gadgets and user scripts and document it at [[:mw:VisualEditor/API]]
+
+Please also create a mailing-list for those API updates.
+
+Issue:
+Since users will not be able to understand Wiki-Markup, please provide and API for turning-on VisualEditor on <textarea>s. Example use case would be the Translate Extension where translators still have to enter wiki-markup or LiquidThreads or whatever is adding Wiki-Markup to a page.
+
+Providing an API to Gadget authors and other tools is an important matter; nearly all edits are made through gadgets at certain pages; thus it is not just an ""enhancement"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373053800,PHID-USER-fgjrqsoj4hk6ezzjdea4,PHID-TASK-x25765urrimfm7ul6ci4,task_description,open
+VisualEditor: Provide integration as an API service,"This is a quite considerable piece of work; marking as ""low"" absent a huge push for this.",1373058098,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-x25765urrimfm7ul6ci4,task_subcomment,NA
+VisualEditor: Transclusion display garbled after removing parameter (CSS caching issue),"narrow display
+
+Seen in Chrome at least
+
+* click Transclusion
+* add a Template; add-parameter display is fine
+* add a parameter to the template
+* click Remove parameter
+
+resulting display is too narrow and does not display fully
+
+* add a new parameter in the garbled display
+
+display of parameter value show echoed/ghost characters as user types into parameter input
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11254}",1373044920,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-7fduwzpt3wlf2h5imzyr,task_description,resolved
+VisualEditor: Transclusion display garbled after removing parameter (CSS caching issue),confirmed,1373062937,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-7fduwzpt3wlf2h5imzyr,task_subcomment,NA
+VisualEditor: Transclusion display garbled after removing parameter (CSS caching issue),"I believe that this was due to a CSS caching issue (which we will more generally fix with bug 49420), and should now be gone - can you confirm?",1373062869,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7fduwzpt3wlf2h5imzyr,task_subcomment,NA
+VisualEditor: Transclusion display garbled after removing parameter (CSS caching issue),"Created attachment 12763
+ghost characters while typing
+
+**Attached**: {F11255}",1373044974,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-7fduwzpt3wlf2h5imzyr,task_subcomment,NA
+"VisualEditor: Add class name to protected pages, to allow for specific CSS styling of edit area","The wikitext editor <textarea> element has a CSS class ""mw-textarea-protected"" when a protected page is being edited. This can be used to provide custom styling for this textarea, mainly in order to alert sysops that they are editing a fully protected page.
+
+A similar CSS class name should somehow be provided for VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372998120,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-u5vpeaoeulxl7k3l2bmg,task_description,resolved
+"VisualEditor: Add class name to protected pages, to allow for specific CSS styling of edit area","Change 130665 merged by jenkins-bot:
+Add class name to protected pages, to allow for specific CSS styling of edit area
+
+https://gerrit.wikimedia.org/r/130665",1398891701,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u5vpeaoeulxl7k3l2bmg,task_subcomment,NA
+"VisualEditor: Add class name to protected pages, to allow for specific CSS styling of edit area","Change 130665 had a related patch set uploaded by Alex Monk:
+Add class name to protected pages, to allow for specific CSS styling of edit area
+
+https://gerrit.wikimedia.org/r/130665",1398887540,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u5vpeaoeulxl7k3l2bmg,task_subcomment,NA
+"VisualEditor: Show a different cursor when Ctrl (Cmd on Mac) is held down, as the interaction will be different","If you Ctrl+Click a link in the VE, it'll open (discovered through trial and error). Presumably the cursor when hovering over links while Ctrl is depressed should be the hand icon, rather than the typing icon.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372938780,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-wvxangmpnag4krm3mcnl,task_description,resolved
+"VisualEditor: Show a different cursor when Ctrl (Cmd on Mac) is held down, as the interaction will be different",Browsers do this automatically now (tested Chrome + FF).,1701797038,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-wvxangmpnag4krm3mcnl,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Screenshot
+
+See screenshot; not sure this is how it's meant to look, but it's how it looks. If there are no unused parameters it seems like the box notifying you of such should overwrite, rather than sit under, the search box - that's unnecessary functionality if all available parameters exist.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54094
+
+**Attached**: {F11039}",1372936920,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-d6zgk46zgybexfzzc4pr,task_description,resolved
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?",This interface has been replaced as a part of <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/VisualEditor_template_dialog_improvements>.,1724097630,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","This is still an issue, although now the message reads ""No unused fields"".
+{F34066618}",1611947721,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Just noting that bug 54094 (which was marked as a duplicate) is about the ""Unknown parameter"" message which appears (briefly) after the user has typed in '1'/'2' but not pressed enter yet.
+
+(In reply to comment #5)
+> Yes, ""No more known parameters"" would work. 
+> 
+> Not essential, but if it's not too much work, including a link to an
+> explanation (that there may be unknown parameters and that these can be used)
+> and/or the template documentation (if there isn't one provided elsewhere on
+> that view) would be good. Obviously both should open in a new window/tab.
+
+That is essentially bug 49772.",1382338192,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?",*** Bug 54094 has been marked as a duplicate of this bug. ***,1381342230,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Yes, ""No more known parameters"" would work. 
+
+Not essential, but if it's not too much work, including a link to an explanation (that there may be unknown parameters and that these can be used) and/or the template documentation (if there isn't one provided elsewhere on that view) would be good. Obviously both should open in a new window/tab.",1377907592,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Urk. Tis true. In particular, I'm thinking of scenarios where you have an infinite number of parameters (templates that merely order and format a set of inputted data, for example). ""No more known parameters"" would work.",1377906608,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","(In reply to comment #2)
+> Possibly? Offering people the ability to do something when the system knows
+> it won't end in what they want probably isn't the direction we want to be
+> going in, however.
+
+But the system doesn't 'know' that. TemplateData is hinting, not a binding-contract-of-doom. It's (intentionally) possible to add parameters that aren't in the hinting, because the hinting is out-of-date or doesn't cover this ""secret"" parameter, or because the name of your parameter is generated (e.g. {{CURRENTDAY}}=Easter Egg! or something more useful). Remember that there's almost no end to the level of flexibility that WT allows users…",1377905124,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Possibly? Offering people the ability to do something when the system knows it won't end in what they want probably isn't the direction we want to be going in, however.",1377904852,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Possibly we could say ""No known parameters"" and ""No more known parameters"" to make it clearer?",1377904599,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+VisualEditor: Drop mw:ExtLink/URL,"Since Parsoid has dropped it in bug 46027
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372936500,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6lutt2i5yzl6odq5e46s,task_description,resolved
+VisualEditor: Drop mw:ExtLink/URL,"Change 71974 merged by jenkins-bot:
+Drop mw:ExtLink/URL support
+
+https://gerrit.wikimedia.org/r/71974",1373310810,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6lutt2i5yzl6odq5e46s,task_subcomment,NA
+VisualEditor: Drop mw:ExtLink/URL,"Change 71974 had a related patch set uploaded by Esanders:
+Drop mw:ExtLink/URL support
+
+https://gerrit.wikimedia.org/r/71974",1372936758,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-6lutt2i5yzl6odq5e46s,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**Author:** `lunarjam.mcgahan`
+
+**Description:**
+MS Word document describing and illustrating the bug
+
+See attached document. O/S is iOS 6.1.3
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: other
+
+**Attached**: {F11914}",1372904400,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uejijc4imv5i4n5hfjzf,task_description,resolved
+VisualEditor: Location map template does not display correctly,"I checked the links that were given as examples to illustrate the problem - it does not seem that the issue is present anymore in wmf.2. 
+
+Also, I checked how the specific example (given in the ticket description) renders in iPad  - both in Chrome emulator and on real device - the issue is not present anymore. 
+(btw, there is a typo in the template code - should be `E` not `N` - I pasted the sample without correcting it to document the issue in its original form) 
+```
+{{Location map|South Australia|label=Macumba Station
+  |position=left
+  |lat_deg=27.25082|lat_dir=S
+  |lon_deg=135.6533|lon_dir=N
+  |caption=Location in South Australia}}
+```
+I am closing the ticket - if there are still some problems it'd be a good idea to create a new specific task.  ",1525739028,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,">>! In T52714#589573, @TheDJ wrote:
+> the technology of absolute positioning that is use by these templates and replace them with something more sustainable.
+
+Split to T120809",1449570666,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Link to a few other templates that run into trouble due to this problem.
+
+https://en.wikipedia.org/wiki/Template:Chess_diagram
+https://en.wikipedia.org/wiki/Template:Quote_box (with curly quotes option on)",1385032387,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Yes, exactly, the elements themselves. The HTML DOM elements. Not the pretty picture that translates into, nor the ugly wikicode language that generates them.",1384946588,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**Wikifram** wrote:
+
+(In reply to comment #14)
+> And i'm slightly offended by your attack on me as a person. A volunteer who
+> probably spends more time on en.wp than doing development.
+
+I haven't attacked you as a person, for all I know you may be a wonderful person. I have attacked your comment as a developer here, and what I see as the mindset of many developers here when working as a developer. 
+
+(In reply to comment #14)
+> > are so wrong that I feel it may be hard to explain to you what is the problem with it.
+> 
+> I think you assumed that I meant the elements/templates themselves. You
+> assumed
+> incorrect.
+
+I didn't ""assume"" anything, I read what you wrote: ""Ideally, we would
+just get rid of absolute positioned elements"". Usually, when people write ""get rid of elements"", they mean ""the elements themselves"", not ""keep the elements but get rid of the technology used"". Don't blame your errors on others please. I have no problem with someone correcting his position or retracting earlier statements, and I'm not the type to claim for all eternity that you want to get rid of these elements if you clarify that that was not what you intended; but then just state that what you said was not what you meant, not that the problem lies with the reader who ""assumed"" something incorrectly.",1384945064,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"> are so wrong that I feel it may be hard to explain to you what is the problem with it.
+
+I think you assumed that I meant the elements/templates themselves. You assumed incorrect. I meant the technology of absolute positioning that is use by these templates and replace them with something more sustainable. They currently also break in mobile and are very sensitive to skin changes for instance. The technique used to place them is problematic (and has been known to be problematic for many years, it's part of why I consolidated those hacks into https://en.wikipedia.org/wiki/Template%3ATop_icon, so that we could replace them at some point). The same technique has also been used for several spam attacks on the wiki.
+
+And i'm slightly offended by your attack on me as a person. A volunteer who probably spends more time on en.wp than doing development.",1384941212,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**Wikifram** wrote:
+
+The DJ, thanks for your response, but I fear that it is again symptomatic of the incorrect view you and other devs seem to have. VisualEditor is ''not'' the goal, it is a means to make editing easier. Comments like ""Ideally, we would just get rid of absolute positioned elements (.topicon, coordinates, FA/GA etc icons), but that's probably going to be near impossible."" are so wrong that I feel it may be hard to explain to you what is the problem with it. There is absolutely ''nothing'' ideal about getting rid of these elements, they are a very useful aspect of maps and other position-defined elements. If VE can't handle these, then VE has to change or an alternative method that can be used in view mode and VE mode needs to be found. But ""VE can't handle this, so we should get rid of these elements""? No, that's the opposite mindset of what we actually need. 
+
+As for ""nor is it extremely visible to the uninitiated."", have you looked at pages like [[:en:FC Barcelona]] or [[:en:ant]]? I think most of the ""uninitiated"" would notice some differences in the display between [[:fr:Azincourt]] and [https://fr.wikipedia.org/wiki/Azincourt?veaction=edit this] (cause this bug happens on all wikis, not just here...) 
+
+This bug happens on about 1 in 5 pages. I don't see how this can be both ""low"" and ""minor"" in importance, either one should be a lot higher (a minor aspect that affects an awful lot of pages on all wiki versions is a lot more important than a minor aspect that only affects a few hundred pages, obviously). On a fair number of pages (e.g. the football kit ones, 25000 on enwiki alone, but also e.g. [https://fi.wikipedia.org/wiki/Paris_Saint-Germain?veaction=edit here]), this bug (assuming it is the same one) is very pronounced, so not so minor anyway.",1384938669,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"By investigating the railway template problem, I think I identified 3 Parsoid bugs that were contributing to those problems on those pages. Most important is bug 57258. The others were bug 57251 and bug 57252.
+
+These are very distinct issues from the location map issue.",1384880301,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"For Location map, this is caused solely by:
+
+.ve-ce-protectedNode, .ve-ce-protectedNode * {
+position: relative !important;
+top: 0 !important;
+left: 0 !important;
+bottom: 0 !important;
+right: 0 !important;
+}
+
+Disabling it returns both the markers and the coordinates back to their original position. However, that also makes all content outside of the main box (you can click title coordinates that are generated by an info box).
+
+Conclusion, this was probably done to counter the effects of absolute positioned elements and causes 'fallout' for relative positioned elements. One way to fix this is with a bit of JS.
+
+var elements = $("".ve-ce-protectedNode"").filter(function() {
+      if( $(this).css(""position"") === ""absolute"" ) {
+            $(this).addClass(""evilabsoluteitems"");
+      }
+});
+
+And then assign the above css only to those elements. This is probably a rather 'expensive' operation. Ideally, we would just get rid of absolute positioned elements (.topicon, coordinates, FA/GA etc icons), but that's probably going to be near impossible. A third option might be to add a classname to all these elements that VE can recognize and then apply this styling to it.
+
+The question of the railway template seems more complex. I have a suspicion that there is actually a coding error in those templates, since I see problems with columns/rows counts on those pages. That would also explain why they take long to render in parsoid, it likely makes it complex to render the pages.",1384872097,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Probably a separate problem, which may already be filed in buzila, but here are a few railway templates that have extreme layout issues.
+https://en.wikipedia.org/w/index.php?title=Ontario_Northland_Railway&veaction=edit
+https://en.wikipedia.org/w/index.php?title=Brunswick%E2%80%93Magdeburg_railway&veaction=edit
+https://en.wikipedia.org/w/index.php?title=East_Lancashire_Railway&veaction=edit
+https://en.wikipedia.org/w/index.php?title=Channel_Tunnel&veaction=edit
+https://en.wikipedia.org/w/index.php?title=Ravenglass_and_Eskdale_Railway&veaction=edit",1380613476,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+Map of Loyalsock State Forest in VE on Chrome 22 Win7
+
+**Attached**: {F11916}",1374667210,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+VE display of a railway line in Chrome 22 on Win7
+
+**Attached**: {F11915}",1374667025,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+Also does nasty things to railway line diagrams - see [[South Maitland Railway]].",1374666736,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+For an example of a similar but not identical problem see the map in [[Loyalsock State Forest]]",1374665426,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Another fairly large set of 'CE-munging-absolutely-positioned-CSS bug'.  Is there an open bug for that?
+
+https://en.wikipedia.org/wiki/Template:Football_kit",1374665092,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"It also appears in other cases, such as this circle which should be over right-most persons face.
+https://de.wikipedia.org/wiki/Selbstbildnis_%28Leonardo_da_Vinci%29?veaction=edit",1374662867,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Problem confirmed on Firefox and Chrome, and can be seen at
+
+https://en.wikipedia.org/wiki/Macumba_Station?veaction=edit
+
+And most other pages (lots and lots) that use
+
+https://en.wikipedia.org/wiki/Template:Location_map
+
+also confirmed for uses of the German template, so I am guessing most other wikis will have the same problem
+
+https://de.wikipedia.org/wiki/Vorlage:Positionskarte
+
+https://en.wikipedia.org/wiki/Azincourt?veaction=edit
+https://de.wikipedia.org/wiki/Albany_%28New_York%29?veaction=edit
+
+I cant find another bug that mentions location maps.",1374538983,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+This bug also occurs in Chrome Version 27.0.1453.116 m on Windows 7.",1372992263,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,This looks like a CE-munging-absolutely-positioned-CSS bug.,1372904578,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+Compatiblity between the two editors,"Very often I find that there are some tools that both these editors (VE and the old editor) that I would want to use on the same article. But there is no way to do so.
+
+It would be a very useful feature of the VE if there was some way (direct, or indirect; like through the show preview button) for editors opening an article in VE to be able to edit the same article in the old editor without having to save it or discard the changes made.
+
+Such a feature could also come in handy for other editors who have started editing through VE but couldn't understand the interface/needed to switch because they realised VE could not do an action they wanted
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372890000,PHID-USER-65pjzcmoby2fsgzdrfjq,PHID-TASK-xucom3pjxavt6vbh6mcr,task_description,resolved
+Compatiblity between the two editors,"This is the same as bug 47779
+
+*** This bug has been marked as a duplicate of bug 47779 ***",1373855340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+Compatiblity between the two editors,"Oops - just realized there was an external link in his comments.
+
+The picture he mentions in his last sentence can be found here:
+http://en.support.files.wordpress.com/2009/07/visual_editor2.png?w=688",1373301423,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+Compatiblity between the two editors,"Another editor adds:
+If you want to switch (say you started in Visual, but you want to switch to source to get something fancy working), you have to either discard your changes or save a partial edit in visual and create a second edit in source. What I want to see is a means of switching between the two at will within the same edit. Wordpress does something similar where you can type up a blog post to switch between visual rendering and HTML source using tabs surrounding the edit window. You can switch between visual and HTML at will and each will be updated. I want to see the same thing with the Wikipedia VisualEditor. -Thunderforge (talk) 21:32, 6 July 2013 (UTC)
+
+AND
+
+They don't necessarily have to both be visible at the same time (in fact, that might be somewhat confusing and perhaps wouldn't work well on mobile devices and tablets if the VisualEditor is going to be used there). But I would like some way to switch between the two without having to discard an edit. Again, the tabs on the edit window that Wordpress uses are one excellent way to do this: they allow the edit space to be swapped out, providing a compact way to easily switch. A picture of it can be found here. -Thunderforge (talk) 21:40, 6 July 2013 (UTC)",1373301385,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+Compatiblity between the two editors,"Examples of articles where I need to use both? That would be any article where I'm trying to manipulate citations (move/add/append/improve) or with templates; as well as doing some general editing.
+
+
+Example of what I want? A button saying ""View this in the old editor"", and clicking on that gets you the same article, including any changes you made, in the old editor. Alternately, you could display the same button in the preview mode when you're viewing the article",1372935534,PHID-USER-65pjzcmoby2fsgzdrfjq,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+Compatiblity between the two editors,Can you provide some more specific examples?,1372931394,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"Copied:
+For logged in user, can there be a formatting preference to display [edit | edit source] as [edit source | edit]? --J. D. Redding 18:47, 3 July 2013 (UTC)
+
+The user finds it frustrating that he keeps inadvertently selecting ""edit""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56337",1372879860,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-kpw2y2iowrttt6zxpjia,task_description,invalid
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"(In reply to comment #5)
+> I don't think a user preference is appropriate here.
+> 
+> Given the resolution of bug 50540, I'm not sure there's anything actionable
+> here.
+
+Concurred; closing as INVALID.",1380214284,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"I don't think a user preference is appropriate here.
+
+Given the resolution of bug 50540, I'm not sure there's anything actionable here.",1380209341,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,A better solution would be the one suggested at bug 50540.,1373324983,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"I agree that we need to resolve this somehow, since the current hover interface has also been pointed out as a problem on touch devices (e.g. tablets).",1373324915,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"I think it is a fairly high priority. It would keep a lot of users (such as me) from turning off the visual editor altogether. Many people are turning off the VE due to this problem. More and more people are saying this here:
+[[Wikipedia:VisualEditor/Feedback]]
+
+I want instant direct access to the ""edit source"" link. I want the ""edit"" link to be the one that is hidden. 
+
+Better yet would be an option to display both links directly without any hover effects. When I want to click either link I do not want to waste one millisecond finding the link, or thinking I may screw up again, and hit the wrong link. 
+
+Think gaming, ping, lag time, and even slightly experienced Wikipedia editors wanting to get things done faster.",1372897059,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"We can do this, but I don't think it's as high priority as a number if others. Marking as such.",1372886254,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.","what it says on the tin; if you remove the first character from [[foo]] to change it to [[moo]], what you actually end up with is m[[oo]].
+
+See also:
+* T52745
+* T52945
+* T55495
+* T52452",1372872240,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-oqqiylk3iqavc5qnj32p,task_description,resolved
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.","This was fixed by the work on link cartouches (the blue highlights that appear when you place the cursor or select text inside a link) in T91285.
+{F32358209}",1600713579,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-oqqiylk3iqavc5qnj32p,task_subcomment,NA
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.","In the weekly triage meeting on 2015-05-06, we discussed this task. We acknowledge that this industry standard manner of operation for editors can lead to some poor outcomes, but as written this isn't actionable and we feel that the issue is not as high priority as the other user-facing work that we need to get done this quarter, so we rejected it as a piece of work for Q4.",1430945493,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oqqiylk3iqavc5qnj32p,task_subcomment,NA
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.","comment from Elitre on bug 53210:
+Seems I had written about it in an unrelated bug, sorry. This happens on itwp:
+in order to do this
+http://it.wikipedia.org/w/index.php?title=DNasi_attivata_da_caspasi&diff=60101664&oldid=60089990
+I had to delete the word and link it back again. Our guidelines about style
+require pages in that section to appear with the capital letter, so we need to
+be able to fix that easily.
+
+It is also reported on en.wp, the user states <<When trying to correct a
+lower-case letter to a capital letter at the beginning of a link, I deleted the
+lower-case letter and found I couldn't type a capital letter and have it become
+part of the link, nor could I seem to extend the link over the capital.
+Eventually, I typed the capital after the lower-case letter and then deleted
+the lower-case letter. It might be good to have some way to extend a link over
+adjoining letters/words/text. Mount Flatten (talk) 05:31, 22 August 2013 (UTC)
+>>
+Thanks.
+
+ps. Might be related to https://bugzilla.wikimedia.org/show_bug.cgi?id=50745",1377445735,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-oqqiylk3iqavc5qnj32p,task_subcomment,NA
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.",*** Bug 53210 has been marked as a duplicate of this bug. ***,1377445650,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-oqqiylk3iqavc5qnj32p,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","ve.init.mw.Platform.js currently hard-codes searching from Commons, even if the wiki doesn't actually load images from Commons. We should do this based on wiki config instead.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372865220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_description,resolved
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","Change 102377 merged by jenkins-bot:
+Use image sources from the fileRepo API
+
+https://gerrit.wikimedia.org/r/102377",1388900839,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","Change 102377 had a related patch set uploaded by Mooeypoo:
+Use image sources from API's fileRepo
+
+https://gerrit.wikimedia.org/r/102377",1387334234,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","This can now be done by using the new meta=filerepoinfo API query, which was introduced into core in gerrit 85344.",1380757856,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","**humpface** wrote:
+
+This was very frustrating for my work's internal wiki.  First, I didn't want any Instant Common images (and thanks to James, I was able to remove the line of code).  However, since I disabled the use of Instant Commons ($wgUseInstantCommons = false;), I was still able to search through the Instant Commons but after saving, everything showed up as a broken link.
+
+Suggestion:
+- Tie the JSON mediaSources object in ve.init.ms.Platform.js to the $wgUseInstantCommons (i.e., if Commons is turned off in LocalSettings.php, then a user can't search through the images).",1380067695,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","(In reply to comment #1)
+> Ideally we'd avoid hardcoding Commons entirely and instead of exporting
+> isInstantCommons, we'd export fileRepos.
+
+Indeed; that was what I was thinking when I wrote this bug. Title modified to be clearer.",1374157001,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","Ideally we'd avoid hardcoding Commons entirely and instead of exporting isInstantCommons, we'd export fileRepos. That should be almost as easy to do and would fix other things as well:
+
+* Wikis where their repo is Commons but through their own wgForeignFileRepos setting (e.g. like on WMF where we use more fine-tuned configuration that does essentially the same, or wikis that configure it but don't use wgUseInstantCommons because they want to set different parameters (e.g. disable repo[fetchDescription] or use a non-default repo[cacheExpiry]).
+
+* Wikis with more than 2 repositories.
+
+* Wikis working with other repos (e.g. a wiki farm might have their own commons-like thing).
+
+Especially reason #1 since we do use InstantCommons in production but not the default settings through the UseInstantCommons toggle. We could hardcode some detection and export ""isUsingCommonsAsARepoSomehow"", but might as well take a few more minutes and figure out how to just export an array of api urls.
+
+
+[] https://www.mediawiki.org/wiki/Manual:$wgUseInstantCommons#Details",1374150733,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"Not sure the technical term, but: if I hover over, for example, the bugzilla ""search bugs"" link, it shows as a URL in the bottom left of firefox, allowing me to identify the destination. The same is true in articles in read mode. It'd be good to have this functionality in the VisualEditor, or some other way of more prominently identifying where links are going to: hovering over every. single. one. doesn't really work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372840860,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_description,declined
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,Re-marking as WORKSFORME.,1415226643,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"As for the issue of browsers not displaying the link target in the status bar when you hover them: that's a browser problem. Neither Firefox nor Chrome appears to do this for links in a contentEditable.
+
+However, since the filing of this bug we do have a better way than tooltips links to show their targets: when you put your cursor in a link, the context menu now shows the target of the link rather than just a link icon.
+
+So, WONTFIX?",1415226397,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"Removing See Also and unassigning; I thought this was about link suggestions in the dropdown in the link inspector, but it doesn't appear to be.",1415226144,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"(In reply to comment #1)
+> Links are now displaying page URL.Checked in FireFox 20
+
+They are not in Firefox 25.0 on Fedora 19 in VE edit mode for me on https://en.wikipedia.org/w/index.php?title=Wikimedia_Foundation&veaction=edit",1384254853,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"Links are now displaying page URL.Checked in FireFox 20 and Chrome Version 26.0.1410.65 using MAC OS X 10.8.5.
+Therefore changing the status to resolved-worksforme for now.
+If you experience this problem again,please reopen the bug.",1384220252,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"I imagine this is mostly due to Firefox's JS engine, but I commonly run across articles that take an extremely long time to load the new VisualEditor interface. For example, ""Domestic violence"" and ""Feminism"" take about 30 seconds. Really long articles like ""World War II"" take over a minute. The interface loads in about half that time in Safari. I'm using Firefox 21.
+
+Comparative loading figures:
+
+| Article | FF 32, 2014-09 | Cr 37, 2014-09
+|--|--|--|--|--
+| Barack Obama | 17.6s | 17.2s
+|--
+| Cat | 16.4s | 16.0s
+|--
+| Beyoncé Knowles | 25.4s | 7.5s
+|--
+| India | 26.8s | 5.6s
+|--
+| Richard Nixon | 9.9s | 5.6s
+|--
+| Europe | 28.3s | 7.1s
+|--
+| English language | 18.2 | 8.0s
+|--
+
+
+| Article | FF 34.05 2014-12 |Cr 39 2014-12
+|--|--|--|--|--
+| Barack Obama | 13.23s | 10.61s
+|--
+| Cat | 11.59s |5.82s
+|--
+| Beyoncé Knowles | 8.01s|5.13s
+|--
+| India | 8.90s |5.64s
+|--
+| Richard Nixon | 8.85s|6.36s
+|--
+| Europe | 10.31s|6.52s
+|--
+| English language |6.98s|5.45s
+|--
+",1372802220,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ysfxvsvtwjpipqsulyul,task_description,resolved
+Improve VisualEditor's loading performance in Firefox,"Yeah; let's claim this as Resolved, in as much as it can be.",1595844165,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! From the **task description**:
+> | Article | FF 32, 2014-09 | Cr 37, 2014-09
+> |--|--|--|--|--
+> | Barack Obama | 17.6s | 17.2s
+> |--
+> | Cat | 16.4s | 16.0s
+> |--
+> | Beyoncé Knowles | 25.4s | 7.5s
+> |--
+> | India | 26.8s | 5.6s
+> |--
+> | Richard Nixon | 9.9s | 5.6s
+> |--
+> | Europe | 28.3s | 7.1s
+> |--
+> | English language | 18.2 | 8.0s
+> |--
+> 
+> 
+> | Article | FF 34.05 2014-12 |Cr 39 2014-12
+> |--|--|--|--|--
+> | Barack Obama | 13.23s | 10.61s
+> |--
+> | Cat | 11.59s |5.82s
+> |--
+> | Beyoncé Knowles | 8.01s|5.13s
+> |--
+> | India | 8.90s |5.64s
+> |--
+> | Richard Nixon | 8.85s|6.36s
+> |--
+> | Europe | 10.31s|6.52s
+> |--
+> | English language |6.98s|5.45s
+> |--
+> 
+
+Six years later – some updated numbers. I couldn't find any  record of how the above was measured. I'm measuring the below based on the `timing.ve.mwTarget.performance.system.activation` metric. Method: open article while logged-in, click Edit, wait for loading to complete, and only then open the console and run `mw.trackSubscribe('timing', console.log)`. I then close the console, close the editor, hard refresh, and measure it once more. Numbers were trimmed to 1 decimal without rounding.
+
+Setup: MacBook Pro with macOS 10.15 Catalina. Using unthrottled latest stable Firefox, Chrome, and Safari.
+
+| Article | FF 78 2020-07 | Cr 83 2020-07 | Saf 13 2020-07
+|--|--|--|--|--
+| Barack Obama | 8.0s, 7.9s | 4.9s, 4.6s | 9.4s, 8.9s
+|--
+| Cat | 4.2s, 4.1s | 2.8s, 2.4s | 3.8s, 3.7s
+|--
+| Beyoncé Knowles|5.6s, 5.2s| 4.2s, 4.0s | 5.7s, 5.2s
+|--
+| India | 6.2s, 6.1s| 4.3s, 4.1s | 8.0s, 7.7s
+|--
+| Richard Nixon | 4.2s, 4.2s | 3.5s, 3.2s | 4.9s, 4.5s
+|--
+| Europe|6.0s, 5.9s | 5.6s, 4.7s| 5.8s,  5.0s
+|--
+| English language | 4.9s, 4.6s | 3.8s, 3.6s | 4.3s, 4.3s
+|--
+
+The load times have shrunk a lot across the board. It's also interesting to see that while Safari generally feels faster than either Chrome or Firefox when browsing day-to-day, with the specific payload of initialising VisualEditor it's more or less on part with Firefox, with Chrome still being notably faster.
+
+Having said that, I would say overall that the differences are now small enough to not need a ticket specifically about Firefox. And that generally speaking we are still consistently taking more than one second to load popular articles which would be great to bring down, but that's outside the scope of this task and it's certainly much much better than it was six years ago.",1595631881,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! In T52616#3769993, @Elitre wrote:
+> T171093 ?
+
+That's for a performance review, which isn't technically the same as making performance improvements. I don't particularly object to merging this into that, but I don't think it's quite right.",1510937642,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! In T52616#3769774, @Deskana wrote:
+> I actually don't see a more general task for improving performance of the visual editor anywhere, so I guess I'll just leave this as it is for now.
+
+T171093 ?",1510933858,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! In T52616#3769774, @Deskana wrote:
+> I actually don't see a more general task for improving performance of the visual editor anywhere, so I guess I'll just leave this as it is for now.
+
+Good idea actually: I was telling myself that there is plenty of computers which will not receive the update son (or will never receive an update), and we still have to improve performances for them.",1510930415,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"I actually don't see a more general task for improving performance of the visual editor anywhere, so I guess I'll just leave this as it is for now.",1510930305,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! In T52616#3769691, @Trizek-WMF wrote:
+> Firefox 57 really improves that issue (I can notice it even with my good computer which had a fast enough Firefox). Maybe reconsider that task?
+
+Yeah, I doubt we'll work specifically on improving Firefox 57 performance directly, and instead choose to work on performance more generally. I can merge this into a more general task. In the unlikely event we do decide to work directly on Firefox 57 in the future, this can be reopened.",1510930006,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,Firefox 57 really improves that issue (I can notice it even with my good computer which had a fast enough Firefox). Maybe reconsider that task?,1510929558,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"This is really a tracker bug more than a specific call-to-action, so we decided in the meeting to remove it from the Q3 blockers list at the triage on 2015-02-11.",1423878817,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"Those are pretty major performance improvements, much more than I was expecting. Odd.",1418255283,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"Added the new data, one thing to note is if you check chrome before firefox, or check only firefox, the results are almost the same for firefox. but if you check chrome after firefox, it is faster, i guess due to caching. So, more food for thought.",1418243212,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"Could you compare loading times for these articles now, three months later?",1418241832,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"(In reply to matanya from comment #1)
+> I'm using firefox 32 and did some tests on this on en,wikipedia, and beta
+> en, which runs HHVM, but is on a virt cluster.
+
+Comparing the time to execute of anything between beta and prod is comparing nothing of value. Different hardware, different cluster sizes (for cache, execute and db) and different code.",1410306789,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"Adding timings in chromium 37 for comparison:
+
+
+Article name:Barack Obama
+beta en: 8.1s
+en : 17.2s
+
+Article name: Cat
+beta en: 7.7s
+en: 16.0s
+
+Article name:Beyoncé Knowles
+beta en: 5.1s
+en: 7.5s
+
+Article name: India
+beta en: 4.8s
+en : 5.6s
+
+Article name: Richard Nixon
+beta en:3.6s
+en: 5.6s
+
+Article name:Europe
+beta en: 5.7s
+en: 7.1s
+
+Article name: English language
+beta en:3.5s
+en: 8.0s",1410306686,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,adding Ori for possible HHVM implications,1410305231,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"I'm using firefox 32 and did some tests on this on en,wikipedia, and beta en, which runs HHVM, but is on a virt cluster.
+
+Article name:Barack Obama
+beta en: 41.7s
+en : 17.6s
+
+Article name: Cat
+beta en: 31.7s
+en: 16.4s
+
+Article name:Beyoncé Knowles
+beta en: 16.9s
+en: 25.4s
+
+Article name: India
+beta en: 36.4s
+en : 26.8s
+
+Article name: Richard Nixon
+beta en:16.2s
+en: 9.9s
+
+Article name:Europe
+beta en: 26.8s
+en: 28.3s
+
+Article name: English language
+beta en:23.7s
+en: 18.2
+
+I think although it is a small test it does show the trend. 
+
+The computer running this test is an i7 quad core from the 3rd gen with 8G of ram, so shouldn't be any issue on this front. 
+
+Would be glad to provide any other info needed.",1410305084,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+VisualEditor: Reduce whitespace in transclusion dialog,"A contributor requests the following:
+
+I'm sure this is far down the list of problems, but I think the transclusion editor (and other bits with similar display) have way too much white space. For each parameter one gets two blank lines for every one line with parameter name. That is annoying and when templates have dozens of parameters, as many infoboxes and citation templates do, it creates a lot of extra scrolling to find what one is looking for. I'd suggest reducing the whitespace between parameter names by half. Dragons flight (talk) 18:18, 2 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372791060,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-rhordq7y2ulyxaighkvm,task_description,resolved
+VisualEditor: Reduce whitespace in transclusion dialog,We did this as part of the transclusion dialog tweaks in August; sorry for the slowness to update.,1385375733,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rhordq7y2ulyxaighkvm,task_subcomment,NA
+VisualEditor: Link inspector should preview the linked page (à la Navigation Popups),"Disambiguations and other oddities can mean that the first link you select in a typeahead search may not actually be right. You then have to follow the link (which is hard in edit mode) and go looking again.
+
+Being able to get a short preview of the selected link target, similar to what Navigation Popups gadget does when hovering over links, would go miles (kilometers) towards making link selection *awesomer*.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59208",1372786320,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-wzei4tpax7kpf3oq25mp,task_description,resolved
+VisualEditor: Link inspector should preview the linked page (à la Navigation Popups),This is effectively now solved with the link image/data preview,1431047236,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wzei4tpax7kpf3oq25mp,task_subcomment,NA
+VisualEditor: Link inspector should preview the linked page (à la Navigation Popups),"It probably shouldn't be the highest priority, but as an editor, I would like something like this. In fact, I'd find it far more useful than Hovercards: When I'm reading an article and want to know more about a topic to which there is a link, I usually middle-click it to open it in a new tab and read it a bit later, so I don't really need Hovercards. As I am editing, however, it would be useful for me to add a link and  be more sure as to where is the link leading. Is [[Washing Machine]] leading to the article about the appliance or about the Sonic Youth album? Is [[AC/DC]] leading to an article about electrical engineering or about a band? These are real situation in which I found myself recently, and in both of them I had to open a new tab to make sure.
+
+So I would love to see something more than just the title when I'm linking. It doesn't even have to be a full-blown Hovercard - just the first few words are likely to be enough. (Although reusing the Hovercards code makes sense, too.)",1401698735,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-wzei4tpax7kpf3oq25mp,task_subcomment,NA
+VisualEditor: Link inspector should preview the linked page (à la Navigation Popups),"I'm not sure this is needed once bug 50240 is fixed, but we should re-consider it then. Also, some form of interaction that doesn't need hover would be needed for touch-screen devices, like mobile.",1377023920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wzei4tpax7kpf3oq25mp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"The template inspector's parameters contain the contents of each parameter, and also a line break, which represents, well, the break between two parameters. When modifying a param, it's all too easy to remove the line break, which results in user-unfriendly things like https://en.wikipedia.org/w/index.php?title=Kidz_Bop_20&diff=prev&oldid=562494239
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69682",1372775700,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-drqb66ingqes5mea47vp,task_description,resolved
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"Agreed, looks fixed.  I can no longer reproduce the problem I had before on $wgEnableCanonicalServerLink (I tried to test with the same exact changes on my sandbox).",1421036273,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"…and in fact, this appears to have been fixed already? The leading and trailing newlines from wikitext source are not displayed in the fields in the template dialog, and can not be removed. However, newly inserted template parameters (and newly inserted templates) do not have ""smart whitespace"" added (this overlaps with T71682 a bit).",1420986164,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"The whitespace around the value of parameters should just be preserved (and not shown in the text field at all). This can't be difficult to do, can it?",1420984596,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"The bug is open for more than a year, and we get ugly diffs and ugly wikitext. Please increase its severity.
+
+If it isn't possible or it is hard to know whether a template is ""inline template"" or ""multiline template"", at least allow manual indication for it (using TemplateData?)",1408794928,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,(inspector->dialog; inspector is the context menu with buttons to open a dialog),1373539573,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,Confirmed (https://www.mediawiki.org/w/index.php?title=Manual:$wgEnableCanonicalServerLink&diff=728104&oldid=667291).,1373408374,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"If you create a new reference, you can specify a name - great! If you try to modify an existing reference to add a name... https://en.wikipedia.org/wiki/File:VEReferenceEdit.jpg oops.",1372760160,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_description,open
+VisualEditor: Be able to name references manually in the reference dialog,"Just noting that there's lots of libraries out there that do this kind of thing.  Google for ""slugify"".",1723306099,PHID-USER-vipegwlyd4ievw2wqspk,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 891513 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Make auto-generated reference names like name="":0"" visible in VE%%%
+https://gerrit.wikimedia.org/r/891513",1677179166,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 891513 had a related patch set uploaded (by Thiemo Kreuz (WMDE); author: Thiemo Kreuz (WMDE)):
+%%%[mediawiki/extensions/Cite@master] Make auto-generated reference names like name="":0"" visible in VE%%%
+https://gerrit.wikimedia.org/r/891513",1677151684,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 743057 **abandoned** by Chlod Alejandro:
+%%%[mediawiki/extensions/Cite@master] [WIP] Add field for changing reference name%%%
+Reason:
+%%%Abandoning this, since as of the way VisualEditor is written right now, it is immensely difficult to switch from counter-based reference names to name-based reference names, or perhaps I simply lack the required prior knowledge of how to make it possible in VisualEditor. Leaving this for someone else to do, hopefully some of the code here might still be useful.%%%
+https://gerrit.wikimedia.org/r/743057",1670504338,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 740171 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Verify key before removing node from InternalList%%%
+https://gerrit.wikimedia.org/r/740171",1666189710,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by Chlod using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/2274ae27f1/w/ ]]~~",1665052298,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by Chlod using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/2274ae27f1/w",1665051508,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 740171 had a related patch set uploaded (by Samtar; author: Chlod Alejandro):
+%%%[VisualEditor/VisualEditor@master] Verify key before removing node from InternalList%%%
+https://gerrit.wikimedia.org/r/740171",1665051130,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Is there any progress on this? I note (now, having not seen it before) the proposal for an alternative at https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Status_report_1#Named_References_in_VE which really doesn't look very helpful: if several of the refs in an article are to sources found on google books, or to a collection of articles written over time in one newspaper, or to journals from a particular online publisher, the editor will still have to struggle among a large set of semi-meaningless references (which of the umpteen ncbi refs in https://en.wikipedia.org/wiki/Oxford%E2%80%93AstraZeneca_COVID-19_vaccine would be ncbi-12?)  It surely cannot be that difficult for an algorithm, faced with a reference in a citation template, to do something like: ""Is there a ""last"" or ""last1"" field? If so, use it as ref name, adding number if needed for disambiguation (or, better, adding year if present, then number if needed); if no ""last1"", then use first word (or 2 words, or 10 chars) of  ""title"" field, similarly. If all else fails, use the domain name as proposed.""",1656964617,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 743057 had a related patch set uploaded (by Chlod Alejandro; author: Chlod Alejandro):
+%%%[mediawiki/extensions/Cite@master] Add field for changing reference name%%%
+https://gerrit.wikimedia.org/r/743057",1638420663,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"This has been proposed as part of the 2019 Community Wishlist:   https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Citations/VisualEditor:_Allow_references_to_be_named  It's too early to know whether it will make the top 10 (voting will be open until the 30 November 2018), but it's currently among the more popular items, which suggests that solving this problem has widespread community support. ",1543192104,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"My first thought is that this wont remain opaque to VE forever and so what is required is a workaround that exposes to VE some aspects about the contents of templates like `{{columns-list}}` even if cannot be edited yet. 
+For example, the template could expose metadata like: 
+```
+References included:  'Smith' 'Jones' 'Patel'
+```
+where each of those is the `name=` parameter of a reference used inside it. 
+
+This would allow VE to display and error along the lines of ""Cannot rename reference ""Jones"" - used in uneditable block. It would also prevent the naming of a new reference with a conflicting name.
+
+It may also be useful for T52474 and similar tasks.
+
+How significant this would be to program I haven't the foggiest though.",1542746748,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"My first thought is that this wont remain opaque to VE forever and so what is required is a workaround that exposes to VE some aspects about the contents of templates like `{{columns-list}}` even if cannot be edited yet. 
+For example, the template could expose metadata like: 
+```
+References included:  'Smith' 'Jones' 'Patel'
+```
+where each of those is the `name=` parameter of a reference used inside it. 
+
+This would allow VE to display and error along the lines of ""Cannot rename reference ""Jones"" - used in uneditable block. It would also prevent the naming of a new reference with a conflicting name.
+
+How significant this would be to program I haven't the foggiest though.",1542746648,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,">>! In T52568#4743919, @Thryduulf wrote:
+> When this is implemented it needs to take account of reused references: 
+> i.e. if `<ref name=""Smith"">...</ref>` is renamed to `<ref name=""Jones"">...</ref>`
+> then all instances of `<ref name=""Smith"" />` need to be automatically changed to `<ref name=""Jones"" />`
+
+This is actually a very good point, and I think this actually makes changing the name impossible in some cases. (But it should be possible to allow setting the name for newly created references.)
+
+Consider a page like this:
+```
+Lorem ipsum dolor sit amet, consectetur adipisicing elit.<ref name=""example"">http://example.com/</ref>
+
+{{columns-list|
+* [[George Washington]]
+* [[John Adams]]<ref name=""example"" />
+}}
+
+<references />
+```
+
+If you were to use VE to change the `name` of this reference, we would not be able to update the reuse inside the `{{columns-list}}` template, because the entire template is ""opaque"" – VE doesn't know about anything inside of it, it just displays the content.",1542650803,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,">>! In T52568#4743919, @Thryduulf wrote:
+> When this is implemented it needs to take account of reused references: 
+> i.e. if `<ref name=""Smith"">...</ref>` is renamed to `<ref name=""Jones"">...</ref>`
+> then all instances of `<ref name=""Smith"" />` need to be automatically changed to `<ref name=""Jones"" />`
+
+This is actually a very good point, and I think this actually makes changing the name impossible in some cases. (But it should be possible to set the name for newly created references.)
+
+Consider a page like this:
+```
+Lorem ipsum dolor sit amet, consectetur adipisicing elit.<ref name=""example"">http://example.com/</ref>
+
+{{columns-list|
+* [[George Washington]]
+* [[John Adams]]<ref name=""example"" />
+}}
+
+<references />
+```
+
+If you were to use VE to change the `name` of this reference, we would not be able to update the reuse inside the `{{columns-list}}` template, because the entire template is ""opaque"" – VE doesn't know about anything inside of it, it just displays the content.",1542650702,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"When this is implemented it needs to take account of reused references: 
+i.e. if `<ref name=""Smith"">...</ref>` is renamed to `<ref name=""Jones"">...</ref>`
+then all instances of `<ref name=""Smith"" />` need to be automatically changed to `<ref name=""Jones"" />`
+
+Thought will need to be given to the interaction of this and section editing. ",1542139214,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"If we try to name a reference by only using a numeral, the system rejects it and says that numeral only reference names are not permitted.
+I feel it is bogus that Visual Editor gets around this by adding a colon: e.g. - :17
+That kind of reference name is wrong and unhelpful.
+I hope that the ability to manually name references, or at least the ability to manually approve the generated name is restored.",1511145285,PHID-USER-wwyujao3kjfasgvrx6nk,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"> If you create a new reference, you can specify a name - great! 
+
+It's no longer possible to specify a name even when creating a new reference.",1484857993,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"At the triage meeting on 11 March it was agreed that this is too complex and imprecise to keep as a Q3 objective, but that a much more on-point task, {T92432}, could be done instead.",1426548049,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Here's another idea for an automatically suggested (but still editable) ref name that would work with manually formatted citations:  
+
+Use the longest text string is in the citation, appending numbers as necessary to keep the names unique.  You might end up with a lot of refs named ""September"", but it in many cases it will pick up the most significant keyword in the source's title.",1425493648,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"The citoid extension could definitely come up with an automated reference name, but that should be filed as a separate issue as a feature request :). For editing citations, the extension uses the same reference dialog as the rest of VE. ",1424976215,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,Perhaps Citoid could suggest a ref name.,1424975287,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,*** Bug 57459 has been marked as a duplicate of this bug. ***,1414104088,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Useful for default would be to read from the parameters of the cite template if provided. The following would be a useful preference order I think 
+1. Lastname and Year (e.g. Smith2013)
+2. Author and year (e.g. Bob Smith2013)
+3. Lastname and serial number (e.g. Smith001)
+4. Title (first 3 words) and year (e.g. FreddieStarrAte1986)
+5. domain, underscore, page name (If only a bare url is given) (e.g. bbc_magazine-23969607)
+6. fist alphabetic string in reference (when neither a template or a url) and a string of four digits from the reference (e.g. Jones1999)
+7. fist alphabetic string in reference and a serial number (when neither a template or a url and no sequence of four digits is present) (e.g. Brown001)",1378935773,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"It would even be convenient if VisualEditor suggested a unique label for the ref, perhaps using the first alphabetic string of characters in the ref (usually the first author's last name).",1378918158,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Editor APerson at en.wp, is asking for this and suggests that the name of a reference could be set in the ""Options"" section along with the group name.",1375511477,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Actually, it even looks like the ability to name a reference has been removed from the reference creation interface. Expanding the scope of this request accordingly.
+
+Being able name references is an important step to allow compatibility with the classic wikitext editor: human-readable names are much easier to use than names like "":5"".",1374250436,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: {{clear}} template phantom generated too large,"See http://en.wikipedia.org/wiki/United_States_v._Windsor right above the 'Dissents' heading. Clear template covers most of quote box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50395",1372738560,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-32cvx6zgypptrjsr7sri,task_description,resolved
+VisualEditor: {{clear}} template phantom generated too large,"I can no longer reproduce this, nor the issue in either of the duped bugs (T53872, T54431). (Note that you need to look at older versions of the articles, as the problematic markup was changed since the bugs were filed.)
+
+For future reference, here's a copy Jalexander's screenshot above: {F117777}",1429479438,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-32cvx6zgypptrjsr7sri,task_subcomment,NA
+VisualEditor: {{clear}} template phantom generated too large,*** Bug 52431 has been marked as a duplicate of this bug. ***,1395360523,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-32cvx6zgypptrjsr7sri,task_subcomment,NA
+VisualEditor: {{clear}} template phantom generated too large,*** Bug 51872 has been marked as a duplicate of this bug. ***,1377830855,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-32cvx6zgypptrjsr7sri,task_subcomment,NA
+VisualEditor: {{clear}} template phantom generated too large,"Covers most of the box appears to be for latest chrome (what I have). Other report below from FF:
+
+http://i.imgur.com/rAJqIsa.png from FF23 (huge, on top of whole quote box and appears to be pushing other content away too)",1372739147,PHID-USER-f6l3bchko2ogbi4poj24,PHID-TASK-32cvx6zgypptrjsr7sri,task_subcomment,NA
+Direct link in revision history to report VisualEditor errors for specific change,"https://en.wikipedia.org/w/index.php?title=Colorado_River&diff=562465192&oldid=562442392
+
+When I go here, I have several options for what I can do with the edit:
+
+> Revision as of 19:24, 1 July 2013 (edit) (undo) (thank)
+
+I'd like another option that says ""(this edit was made with VisualEditor and introduced a problem; report it here)"" or something like that. A JavaScript gadget would be dandy, but I'm not picky about the implementation details.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1372734540,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-clyi3kkewgt6by3dskxa,task_description,declined
+Direct link in revision history to report VisualEditor errors for specific change,"This is probably not needed these days. VisualEditor no longer introduces errors in articles, certainly not at a rate that would demand a prominent action to report them.",1729515165,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-clyi3kkewgt6by3dskxa,task_subcomment,NA
+Direct link in revision history to report VisualEditor errors for specific change,"Rephrasing summary to reflect what the report is about (""Make it easier"" is vague and impossible to define when it's fixed).",1372760577,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-clyi3kkewgt6by3dskxa,task_subcomment,NA
+"VisualEditor: ""Drag to move image"" is buggy in Safari 6","Screenshot of oddly collapsed resizable area
+
+Not sure whether it is specific to Safari 6 but it seems a bit buggy.
+
+Sometimes when holding down the mouse button the cursor won't change from a  ""move"" cursor to a ""drag/add"" cursor (as if it is a regular hover, ""move"" until it hits the edge of the image and then becomes a regular pointer).
+
+Also when dragging and dropping sometimes it seems to separate the image itself and the thumb container is left behind (!).
+
+When resizing it seems to sometimes (sorry, can't be move specific yet) collapse into a single dot (see screenshot).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11549}",1372721760,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7b3ttjryq7h2dwfsiked,task_description,resolved
+"VisualEditor: ""Drag to move image"" is buggy in Safari 6",Seems to now be fixed.,1385379064,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7b3ttjryq7h2dwfsiked,task_subcomment,NA
+"VisualEditor: ""Drag to move image"" is buggy in Safari 6","Created attachment 12723
+Screenshot of misplaced image inspector
+
+It also seems to take about a second for it to apply when releasing the mouse, so the user can continue to drag it else where and then after about 2 seconds into the second drag the image moves back and actually moves to where the first drag put it. It is at this point that the inspector stays behind when dropping near another image (see screenshot).
+
+**Attached**: {F11550}",1372721910,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7b3ttjryq7h2dwfsiked,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"http://parsoid.wmflabs.org/en/User:Adjwilley/sandbox10?oldid=562331693
+
+Relevant wikitext:
+
+*{{Cite book| last=Fádil-i-Mázindarání | first= Asadu'lláh | authorlink = Mírzá Asadu’llah Fádil Mázandarání | year=1967 | title=Asráu'l-Á<u>th<u>ár, Vol.I| pages= 453 | publisher=Bahá'í Publishing Trust, Tehran | url = http://www.h-net.org/~bahai/areprint/authors/mazandarani/asrar.htm | ref=harv}}
+
+(note the <u> isn't opened then closed, but double-opened)
+
+Output HTML (with data-*, about and a few others stripped):
+
+<li><span typeof=""mw:Transclusion""><a rel=""mw:WikiLink"" href=""..."">Fádil-i-Mázindarání, Asadu'lláh</a> (1967). <a rel=""mw:ExtLink"" href=""...""><i>Asráu'l-Á<u>th<u>ár, Vol.I</u></u></i></a><u><u>. Bahá'í Publishing Trust, Tehran. p.<span typeof=""mw:Entity"">&nbsp;</span>453.</u></u></span><u><u><span class=""Z3988""><span style=""display:none;""><span typeof=""mw:Entity"">&nbsp;</span></span></span></u></u></li><u><u>
+
+<li>(next item here, note how we're still inside of <u><u>)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372721640,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tl2v542il5zhvqmae5zl,task_description,resolved
+Unclosed formatting elements leaking out of transclusions,"Parsoid output and core output matches on this at this point since we are all in a HTML5 post-Tidy world. 
+
+```
+[subbu@earth:~/work/wmf/parsoid] echo '<ul><li>{{1x|<u>}}</li><li>foo</li></ul>' | php bin/parse.php --normalize
+<ul>
+<li><u></u></li>
+<li><u>foo</u></li>
+</ul>
+
+[subbu@earth:~/work/wmf/parsoid] echo '<ul><li><u></li><li>foo</li></ul>' | php ../mediawiki/maintenance/parse.php
+<ul><li><u></u></li><li><u>foo</u></li></ul><p><u>
+</u></p>
+```
+
+Here is Parsoid's unnormalized output and wt2wt resluts:
+```
+[subbu@earth:~/work/wmf/parsoid] echo '<ul><li>{{1x|<u>}}</li><li>foo</li></ul>' | php bin/parse.php --body_only
+<ul data-parsoid='{""stx"":""html"",""dsr"":[0,40,4,5]}'><li data-parsoid='{""stx"":""html"",""dsr"":[4,23,4,5]}'><u about=""#mwt1"" typeof=""mw:Transclusion"" data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""dsr"":[8,18,null,null],""pi"":[[{""k"":""1""}]]}' data-mw='{""parts"":[{""template"":{""target"":{""wt"":""1x"",""href"":""./Template:1x""},""params"":{""1"":{""wt"":""&lt;u>""}},""i"":0}}]}'></u></li><li data-parsoid='{""stx"":""html"",""dsr"":[23,35,4,5]}'><u data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""autoInsertedStart"":true,""dsr"":[27,30,0,0]}'>foo</u></li></ul>
+
+[subbu@earth:~/work/wmf/parsoid] echo '<ul><li>{{1x|<u>}}</li><li>foo</li></ul>' | php bin/parse.php --wt2wt
+<ul><li>{{1x|<u>}}</li><li>foo</li></ul>
+```
+As for the formatting leaking out of transclusions, the tree builder doesn't care about transclusion boundaries and it is unclear how much we ought to worry about it. Selser will still prevent that leakage from serializing back in most cases, but yes, if some of that content is edited, it will cause some minor dirty diffs.
+
+We aren't going to add extra complexity to identify these leaked formatting elements and then expand the scope of the template (likely by migrating the meta-end tag to a different place in the DOM tree).
+
+Since we have the Linter flagging ""syntax  errors"" like this ( https://www.mediawiki.org/wiki/Help:Lint_errors/multiple-unclosed-formatting-tags ), I am inclined to call this resolved since the best strategy here is to fix the wikitext lint errors.",1590072108,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,Is this still an issue? Last activity was 12 months ago…,1416945130,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"Re-titling to reflect our plan [1] to avoid the leaking and match PHP parser semantics instead.,
+
+[1]: https://www.mediawiki.org/wiki/Parsoid/DOM_notes",1386112099,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"https://www.mediawiki.org/w/index.php?title=VisualEditor/Basic_example_worksheet&oldid=751458&veaction=edit
+
+""Foo <tt>bar<tt>\n == Heading == * Lists""",1375204287,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"Change 73369 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 50536) Improved handling of tree-builder fixup
+
+https://gerrit.wikimedia.org/r/73369",1373586328,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"The template encapsulation does not catch all template-affected content, so is not correct really. Alternatively we should be able to undo the leak to match the PHP parser's semantics. That would remove the need for extending the encapsulation in this case.",1373576627,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"No, the tpl encapsulation looks correct to me.  The tree builder correction in this case is quite broad and it would be hard to detect auto-correction as well.  On this last example, there are no autoInserted* flags except on the innermost <u> tag.  As long as we are using a html5 compliant tree builder, our options are a little limited on this kind of html without doing more complicated tracking/analyses.  I am not convinced those are worth the trouble and headaches.",1373053934,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"Since this is a plain transclusion this is pretty much the behavior I would expect. The formatting is processed in accordance with the HTML spec.
+
+I suspect tidy has a heuristic that closes the <u> at some point in contrast with the HTML spec.
+
+Something that looks broken on the Parsoid side is the missing encapsulation for formatting that spans list items:
+
+echo '<ul><li>{{echo|<u>}}</li><li>foo</li></ul>' | node parse
+<body><ul>
+  <li><u about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""1"":{""wt"":""<u>""}},""i"":0}'></u></li>
+  <li><u>foo</u></li>
+</ul>
+<u>
+</u></body>
+
+(reformatted the above a bit and removed data-parsoid for clarity)
+
+We should in theory be able to detect that the leaked <u>s were completely auto-inserted by the treebuilder. Maybe we can use that information to extend the encapsulation for cases like this one.",1372727019,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,Diff showing resulting VE breakage: https://en.wikipedia.org/w/index.php?title=User:Adjwilley/sandbox10&curid=38366631&diff=562462441&oldid=562331693 . I'm not sure if the categories being dropped is on the VE or Parsoid side yet.,1372721716,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"There should be an edit notice whenever someone tries to use VE which says something like ""Slower computers or users trying to use older markup should try editing in the older Editor."" and link to the older editor. Otherwise we're directly cutting off plenty of editors who can't figure it out, and would have relatively slow internet.
+
+P.S. My internet is slow enough to not give a satisfactory VE experience, and I consider myself to have decent Indian speed internets
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372710300,PHID-USER-65pjzcmoby2fsgzdrfjq,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_description,open
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"Change 135046 abandoned by Alex Monk:
+Attempt to detect slow machines and show an edit notice
+
+Reason:
+This is seemingly impossible for me to get right, and just not worth the effort
+
+https://gerrit.wikimedia.org/r/135046",1401411908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"Change 135046 had a related patch set uploaded by Alex Monk:
+Attempt to detect slow machines and show an edit notice
+
+https://gerrit.wikimedia.org/r/135046",1400859196,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"We discussed how to do this in #mediawiki-visualeditor a bit. Some quotes:
+
+<Krinkle> when a certain amount of time has passed (potentially taking the document complexity in account as well, avoid measuring network by accident), set a boolean flag, which in getEditnotices() will make it include/exclude that notice accordingly
+<Krenair> I'm wondering what operation we should measure and what timing shows a reasonable speed
+<Krinkle> Krenair: one or more of the actions in the setup of the surface (parsing of html into data DOM, conversion to linenar data model, building of CE etc.)
+
+<Krenair> but those operations will all take different times depending on document length/complexity :/
+<Krinkle> Krenair: Yes, but avoiding I mean, taking into account
+<Krinkle> e.g. not `timespend > maxtime`, but something like `timespent/doc-size > maxratio`
+<Krinkle> RoanKattouw might have some math ideas that are more useful
+<Krinkle> However, we should probably do some research and see how slow the 'too slow' browsers really are.
+<Krinkle> We might be able to measure it with a very simple operation at a small scale (e.g. create an iframe and attach it, just a random unused iframe), that that one operation is measurable enough, we can do it that way.
+<Krenair> Hm. This is getting increasingly out of the 'MediaWiki integration' part
+<Krinkle> The function calls are all in viewpagetarget in setupSurface
+<Krinkle> though ideally this would probably be in ve-core, seems a useful statistis
+
+Roan, could you comment on this when you have time please?",1399321807,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,Timo thinks we can measure performance and display an edit notice if it's slow.,1398879851,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"The plan is to get rid of the beta welcome dialog relatively soon (in the next few months), however…",1398792650,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"So we already have the beta welcome dialog, I think we should add something like ""Users of slow computers should consider doing this."" after the ""You can keep using the wikitext editor by clicking the ""Edit source"" tab instead – unsaved changes will be lost.""",1398792405,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"When I add a link to the title of the page, it is displayed as a normal link instead of a <strong class=""selflink"">.
+
+Same problem while editing a page with a 'selflink' already present.
+
+The contributor doesn’t see the article as it will be after saving.",1372684440,PHID-USER-5pyvkdz65d5h5vxebodc,PHID-TASK-75qcblrq4xxtwfp5s76f,task_description,resolved
+VisualEditor: Links to current page should show as bold,"Change 345526 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Follow-up I88d45aad2: Fix selflink detection
+
+[[https://gerrit.wikimedia.org/r/345526]]
+",1490882209,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 345526 had a related patch set uploaded (by Esanders):
+[mediawiki/extensions/VisualEditor@master] Follow-up I88d45aad2: Fix selflink detection
+
+[[https://gerrit.wikimedia.org/r/345526]]
+",1490871596,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 342084 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Render self-links as if they were <strong>s
+
+[[https://gerrit.wikimedia.org/r/342084]]
+",1490865420,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 341775 abandoned by Esanders:
+Render self-links as <strong class=""selflink"">, not <a ...>
+
+Reason:
+See I88d45aad2aaa45e71b433350986b19764603a1f2
+
+[[https://gerrit.wikimedia.org/r/341775]]",1490864792,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 341774 abandoned by Esanders:
+Allow links to be constructed with custom elements
+
+Reason:
+See I88d45aad2aaa45e71b433350986b19764603a1f2
+
+[[https://gerrit.wikimedia.org/r/341774]]",1490864784,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 342084 had a related patch set uploaded (by Jforrester):
+[mediawiki/extensions/VisualEditor] Render self-links as if they were <strong>s
+
+[[https://gerrit.wikimedia.org/r/342084]]
+",1489091254,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 341775 had a related patch set uploaded (by Esanders):
+[mediawiki/extensions/VisualEditor] Render self-links as <strong class=""selflink"">, not <a ...>
+
+[[https://gerrit.wikimedia.org/r/341775]]
+",1488968700,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 341774 had a related patch set uploaded (by Esanders):
+[VisualEditor/VisualEditor] Allow links to be constructed with custom elements
+
+[[https://gerrit.wikimedia.org/r/341774]]
+",1488968529,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,">>! In T52497#561368, @Jdforrester-WMF wrote:
+> bug 37901
+
+aka T39901 in Phabricator numbering
+
+",1488968489,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"This will need bug 37901 (a general CSS hinting system for links) to be implemented, which is planned for later this quarter. Hinting that links should be red (non-existent), bold (current), purple (stubs), orange (redirects) etc. will need to be supported in that service.",1375235157,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"**crypticc62** wrote:
+
+For those who might be wondering why selflinks would ever appear in an article: Many pages make use of navigation boxes, such as Template:Extreme Sports. Each navbox usually links to all of the articles that it will be transcluded to. So, with several hundred navboxes, each appearing on at least a dozen pages, we can expect selflinks to appear on several thousand articles.",1375234921,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Suppose an article contains two lines in Paragraph formatting, and we want to turn the first one into Heading formatting. Select the entire first line (Cursor at beginning of line, Shift-CursorDown) then choose Heading formatting from the selection box at the top. Result: both lines are turned into Headings, not just the first. (Bold and italics formatting changes work correctly and affect only the current line.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372508580,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-jktlvnskifhm2sbbalki,task_description,resolved
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Line with cursor gets heading(or other) formatting applied
+
+{F41659137}",1704734922,PHID-USER-sbs2thr232mk3iv6jwal,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Change 981374 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (402570007)%%%
+https://gerrit.wikimedia.org/r/981374",1701976844,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Change 981374 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (402570007)%%%
+https://gerrit.wikimedia.org/r/981374",1701971212,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Change 980439 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Don't convert empty-selected paragraphs%%%
+https://gerrit.wikimedia.org/r/980439",1701968690,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Change 980439 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] Don't convert empty-selected paragraphs%%%
+https://gerrit.wikimedia.org/r/980439",1701796908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","In Microsoft Word, both character-level styling and paragraph-level formatting are only applied to the one line that was selected either with Cursor-at-beginning-plus-Shift-Cursor-down or with a triple-click. In three of these four scenarios, VE behaves as Word.
+
+As far as I can see, applying character-level styling to a line selected with Cursor-at-beginning-plus-Shift-Cursor-down does not become a pre-annotation on the following line (neither in Word nor in VE): the styling is not applied if I insert text at the beginning of that line.",1455301413,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","This is the same behaviour as in other rich editors.
+
+By selecting in the manner you've stated (""Cursor at beginning of line, Shift-CursorDown"") you've selected the current text, the current line, AND the newline into the place before the first character.
+
+If you mark the text as bold (which is character-level) the boldness becomes a ""pre-annotation"" on the second line before the first character (so typing anything at that point will become bold).
+
+However, changing the format (rather than styling) of some text applies to the entire paragraph (because that's how HTML works) – i.e., the entire second line gets this applied.
+
+We could theoretically apply different behaviour for styling and formatting, so we apply over a newline for the first but not the second, but that might be more unexpected?",1385471045,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)",This issue exists for all kind of formatting from the Headings pull-down menu.,1383081754,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Add a way to mark a parameter to be dependent on an other paramter. For example :
+We have following parameters:
+""foo1_bar"", ""foo1_baz"", ""foo1_quux"" 
+...
+ ""fooN_bar"", ""fooN_baz"", ""fooN_quux""
+
+fooX_bar required fooX_baz to be used as well, it doesn't require fooX_quux to be used, but if fooX_quux is used, then fooX_bar must have been defined as well
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372464000,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-2xs7662hh3qdt5fonxnb,task_description,open
+TemplateData: Add a way to express dependencies between parameters,"The previous comments don't explain who or what (task?) exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status, as tasks should not be stalled (and then potentially forgotten) for years for unclear reasons.
+
+//(Smallprint, as general orientation for task management:
+If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead.
+If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}.
+If this task is stalled on an upstream project, then the #upstream tag should be added.
+If this task requires info from the task reporter, then there should be instructions which info is needed.
+If this task needs retesting, then the #testme tag should be added.
+If this task is out of scope and nobody should ever work on this, or nobody else managed to reproduce the situation described here, then it should have the ""Declined"" status.
+If the task is valid but should not appear on some team's workboard, then the team project tag should be removed while the task has another active project tag.)//",1604270588,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,,1453561129,PHID-USER-25bxvdt2svnidzfzjpk7,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,,1453561068,PHID-USER-25bxvdt2svnidzfzjpk7,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Well, I have another case: In German Wikipedia we have Template:Charteintrag, where not only such dependencies are required (eg if “POS_xy” then also “WO_xy”), but even the parameter names depend heavily on earlier added parameters. If I enter 1=x and 2=y, the possible parameters following are POS_x (with WO_x) and POS_y (with WO_y), but of course not eg POS_z! At the moment TemplateData is totally useless with this template, I fear.",1441831007,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"[Moved from bug 60358 discussion.]
+
+(In reply to Helder from bug 60358 comment #10)
+> (In reply to James Forrester from bug 60358 comment #9)
+> > (In reply to Helder from bug 60358 comment #8)
+> > > (In reply to James Forrester from bug 60358 comment #6)
+> > > > (In reply to Ricordisamoa from bug 60358 comment #5)
+> > > > > or a set of fields may be mutually exclusive (and yet one of them would
+> > > > > be required).
+> > > > 
+> > > > That doesn't make sense. ""Required"" means ""the template will die horribly if
+> > > > you don't include this"". It is *not* a ""we'd like you to fill this in"" –
+> > > > that's what ""suggested"" is for. Most templates will have no 'required'
+> > > > fields.
+> > > 
+> > > It seems perfectly valid for a template to require that ""either A or B be
+> > > provided"" and the user should be able to delete one of them if it is not
+> > > needed.
+> > 
+> > This feels like a pretty edge case (and suggests that we should consider
+> > whether the template should be re-written to be less anti-human); maybe file
+> > a TemplateData bug to ask for a way to express this relationship?
+> 
+> This kind of relationship between parameters was requested on bug 50407.
+
+Well, as I see it, this bug only asks for param-level relationships – if A also B; if C not D; etc.
+
+Should we extend it for shared-param relationships (exactly one of A, B and C are required; D is an alias for E if F is set but is an alias for G if F is not set; …), or should we create a new bug? (BTW, this feels like a potentially ever-expanding system could be created, and we'd probably say this adds too much complexity for the value.)",1409778173,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Change 73708 abandoned by Krinkle:
+Add depends and conflicts parameters
+
+Reason:
+Closing for now to clear review backlog. Can be re-activated when the feature request is accepted.
+
+https://gerrit.wikimedia.org/r/73708",1404942538,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"at en.wp a user has given the example of [[template:for]] where parameter 3 is optional unless parameter 4 is specified, when it becomes mandatory.
+
+They expected that VisualEditor would give them a warning about using parameter 4 without parameter 3. Obviously this is not possible until TemplateData can define such relationships.",1377689591,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"(In reply to comment #3)
+> Note that as for a parameter ""going together with"" other parameters, this is
+> what a ""Set"" is for.
+> 
+> Though Sets are merely suggestive and allow for overlap, it us a lot easier
+> to
+> work with from a user interface perspective.
+Set doesn't make any sense for parameters like ""author1, author2, ..., authorN""
+> 
+> Though TemplateData is generic and should not be tailored specific for
+> VisualEditor, right now I'd recommend we hold off on this change until we
+> find
+""depends"" and ""conflicts"" are pretty much not tailored for VE at all (Though I could agree, sets are).
+> out and/or verify that this can be properly represented in a user interface
+> without making it too complex.
+The most important thing is that common templates can be modeled correctly without ending up with too many false choices, or hiding true choices because they couldn't be modeled correctly.",1373912959,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Note that as for a parameter ""going together with"" other parameters, this is what a ""Set"" is for.
+
+Though Sets are merely suggestive and allow for overlap, it us a lot easier to work with from a user interface perspective.
+
+Though TemplateData is generic and should not be tailored specific for VisualEditor, right now I'd recommend we hold off on this change until we find out and/or verify that this can be properly represented in a user interface without making it too complex.",1373912431,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Change 73708 had a related patch set uploaded by AzaToth:
+Add depends and conflicts parameters
+
+https://gerrit.wikimedia.org/r/73708",1373830886,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,See also [[User:קיפודנחש/TemplateParamWizard#Depends on]].,1372589692,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"https://en.wikipedia.org/w/index.php?title=Stand-your-ground_law&diff=562005779&oldid=561464750 is a good example (hat-tip to MatMaRex)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50120",1372445760,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-poawg73ix2eh7lpylhyd,task_description,resolved
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),Done and will be deployed tomorrow.,1374634250,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),This should be fixed now. Rejoice!,1374519751,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Change 72233 merged by jenkins-bot:
+Array.prototype.splice polyfill for Opera
+
+https://gerrit.wikimedia.org/r/72233",1374518403,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Change 72233 had a related patch set uploaded by Matmarex:
+Array.prototype.splice polyfill for Opera
+
+https://gerrit.wikimedia.org/r/72233",1373066976,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"function testSpliceBroken() {
+	var n = 256;
+	var a = [];
+	a[n] = 'a';
+	
+	a.splice( n+1, 0, 'b' );
+	
+	return a[n] != 'a';
+};
+
+This yields 'true' on Opera.
+
+That's probably the bizarrest browser bug I've ever seen, and it seems to be the root cause of this.",1373052337,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Funnily, my testing shows that the categories are only moved inside the reference if it contains a template. Inserting an empty or text-only reference results in the cateogires eing killed entirely.",1373035435,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Eh, it seems to be Opera-specific after all, I can't reproduce on Firefox (but it reproduces reliably in Opera).",1372504054,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"(In reply to comment #1)
+> Another is
+> https://pl.wikipedia.org/w/index.
+> php?title=Waldemar_Kasta&diff=36944980&oldid=36944831
+
+Bartosz,
+
+Both these corruptions were by you - were both of them made using Opera? If so, I'm happy to mark this bug out to you (but please clean up after yourself when editing using a blacklisted browser).",1372472137,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Very strange, looks like metadata is being moved somehow. Do we have any information about what the editors did to provoke this?",1372468169,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),Another is https://pl.wikipedia.org/w/index.php?title=Waldemar_Kasta&diff=36944980&oldid=36944831 .,1372445852,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Template:Listen (and similar sound files) doesn't render the TMH aspects correctly,"Screenshot
+
+Firefox 21.0, Windows 7 - see screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49896
+
+**Attached**: {F11161}",1372417620,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-6fjqaicfdcw65wigvygy,task_description,resolved
+VisualEditor: Template:Listen (and similar sound files) doesn't render the TMH aspects correctly,"Looks perfect now.
+{F26621568}",1539835123,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6fjqaicfdcw65wigvygy,task_subcomment,NA
+VisualEditor: Template:Listen (and similar sound files) doesn't render the TMH aspects correctly,"It looks better today than in that screenshot, but still a bit funny:
+https://en.wikipedia.org/wiki/Rage_Against_the_Machine?veaction=edit&section=3#1992–2000%3A_Mainstream_success
+{F26280267}
+…But I am 99% sure it will be fixed completely by T201081 (which will swap from using a `<video>` with a fake thumbnail to using `<audio>`). We should test this after that is deployed.
+
+Note that it will display using the HTML5 `<audio>` player in your browser, rather than actual TMH interface. I think attempting to load TMH here is unnecessary, since you can't interact with the element to play it, anyway.",1538513327,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-6fjqaicfdcw65wigvygy,task_subcomment,NA
+VisualEditor: Template:Listen (and similar sound files) doesn't render the TMH aspects correctly,This looks like it is caused by bug 49896.,1375050061,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-6fjqaicfdcw65wigvygy,task_subcomment,NA
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol","This is a legacy of wiki-syntax, where all external links have to begin with the protocol. It would be nice to make the VE link inspector smarter than this.
+
+""www.google.com"" is almost certainly meant to be an external link - if there is an article by this name, then it could be shown in the link inspector dropdown as well, but the option for ""External link"" definitely needs to be there. Even something like ""royal.gov.uk"" should be recognised as a URL.
+
+Requiring ""http://"" or some other protocol at the start is confusing for the newbie, as the protocol component of URLs is generally ignored nowadays.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372414560,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-qdoykgze5mrfb2vlwluc,task_description,open
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol","So we now have a separate external link input, but it shows URLs without a protocol as invalid :/",1439170185,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qdoykgze5mrfb2vlwluc,task_subcomment,NA
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol",">>! In T52360#542816, @Krinkle wrote:
+> We solved this to some degree in WikiEditor with the link dialog in that extension. We can probably re-use some of that logic.
+
+https://github.com/wikimedia/mediawiki-extensions-WikiEditor/blob/master/modules/jquery.wikiEditor.dialogs.config.js#L131
+
+By looking for www.? Yeah, that doesn't work. phabricator.wikimedia.org should be recognised, as well as the bug creator's suggestion of royal.gov.uk.
+
+Sounds like {T76398} would fix this by having the user deal with it instead.",1417555457,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-qdoykgze5mrfb2vlwluc,task_subcomment,NA
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol",*** Bug 56490 has been marked as a duplicate of this bug. ***,1402609062,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qdoykgze5mrfb2vlwluc,task_subcomment,NA
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol",We solved this to some degree in WikiEditor with the link dialog in that extension. We can probably re-use some of that logic.,1373369726,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qdoykgze5mrfb2vlwluc,task_subcomment,NA
+VisualEditor: FlaggedRevs status box causes blank space down the right side of CE content div,"Screenshot of bug
+
+1. Go to [[de:Special:PendingChanges]]
+2. Visit one of the linked articles and edit it in VE
+
+Notice the wide right margin, caused by the floating FlaggedRevs status box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11085}",1372388280,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-q7kvrcess52gstbba6tv,task_description,resolved
+VisualEditor: FlaggedRevs status box causes blank space down the right side of CE content div,"Indeed, probably fixed a while ago…",1405449142,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-q7kvrcess52gstbba6tv,task_subcomment,NA
+VisualEditor: FlaggedRevs status box causes blank space down the right side of CE content div,Seems fixed?,1405410026,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-q7kvrcess52gstbba6tv,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","At the moment adding categories (through ""page settings"") involves turning away from the actual content. This is a problem because a lot of categories are dependent on the actual content, which needs to be referred back to - birth or death years, college, etc, etc.
+
+Suggestion is:
+* Show the existing categories in the standard skin location (at the bottom of the page, in Vector)
+* Make the categories editable there, in some way.
+
+----
+Original onwiki comments were [[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_6#Categories_-_display_them.2C_please |archive 6]] 
+> I can see categories when I read an article. I can see them below the editing paraphernalia when I'm in Edit Source. But in VE I can only see them by clicking ""Page Settings"", which (a) takes a click and (b) means I can't see any of the article content (eg the hard-to-remember-the-spelling district name, the birth date, etc which I might want to use in creating categories, having seen that they aren't already there). Please display the categories in or around the article, not just as ""Page settings"".
+and [[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_7#Categories:_please_display_them_in_VE_-_not_the_right_bug |archive 7]]:
+> I want to be able to see the categories when I've got an article open in VE: just as I can see them when reading the article, or when editing it in Edit Source. I don't want to have to click on ""Page Data"" to find out whether or not it's already got categories.
+
+--------------------------
+See also: {T67518}
+
+merged duplicates: {T53153} and {T71506}
+",1372262760,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_description,open
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat",">>! In T52239#1562999, @John_Broughton wrote:
+> It would be a definite improvement if the user could reach categories either via a top menu, or by scrolling to the bottom of the page. As several people have pointed out, there are disadvantages of the user being able to do only one of these, and - of course - there is no reason, from a programming viewpoint, why there can't be two paths to the same dialog.
+> 
+> So yes, I support (a) making existing categories visible at the bottom of a page, when in editing mode, (b) having something at the bottom of the page that, when clicked, will open the dialog where categories can be added or deleted, and (c) leaving that dialog accessible via the Pages options menu.
+
+This sounds like a good path forward. It gives two paths to one dialog rather than two different dialogs. Hopefully, we can also extend the bottom-of-the-page experience to the read mode at some point.",1440439943,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","It would be a definite improvement if the user could reach categories either via a top menu, or by scrolling to the bottom of the page. As several people have pointed out, there are disadvantages of the user being able to do only one of these, and - of course - there is no reason, from a programming viewpoint, why there can't be two paths to the same dialog.
+
+So yes, I support (a) making existing categories visible at the bottom of a page, when in editing mode, (b) having something at the bottom of the page that, when clicked, will open the dialog where categories can be added or deleted, and (c) leaving that dialog accessible via the Pages options menu.",1440205952,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","I was pointed to this bug because of a feedback comment. I mostly see discussion about category editing on the page itself. Another feature hotcat offers is to navigate the category-tree, so it is quite simple to put an article in a subcat, or to bring it to a category above it. Can that feature be considered as well?",1438716633,PHID-USER-roxczeg7vc6hdylglkpt,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","How about extracting the categories editor and making it a beta feature as ""HotCatoid""?",1438159829,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","Just reinforcing @whatamidoing-wmf's point. This is one of those features where some user feedback would be welcome indeed, to see whether we are planning to put the right effort in the right feature. My totally subjective impression is that editors seem to be happy with HotCat, where you don't need to deal with wikitext at all. IMHO HotCat's UI could welcome some enhancements, but editing categories at the bottom of the page (where categories are found) seems to be unproblematic.",1438123638,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","Just reinforcing @whatamidoing-wmf's point. This is one of those features where some user feedback would be welcome indeed, to see whether we are planning to put the right effort in the right feature. My totally subjective impression is that editors seem to be happy with HotCat, where you don't need to deal with wikitext at all. IMHO UI could welcome some enhancements, but editing categories at the bottom of the page (where categories are found) seems to be unproblematic.",1438122984,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","This has been discussed several times on wiki, and none of the experienced editors have mentioned concerns about having to scroll all the way to the end of the page.  However, if you're worried about that, then you could leave an item in the toolbar that either jumps to the end of the page, or that does exactly what it does now.",1438120605,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat",">>! In T52239#1477765, @Jdforrester-WMF wrote:
+> Certainly I think this should only happen at the bottom of the page, not the window, yes.
+
+In that case, we'd either be duplicating controls (if we leave the current category interface in) or removing the ability to edit categories without a bunch of scrolling (if we take the current interface out).  ",1437699559,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","Certainly I think this should only happen at the bottom of the page, not the window, yes.",1437699244,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","I'm not sure this would actually be easier for the user. Currently, you can edit categories whenever you want without losing your place in the article; if we just stuck a category widget at the end of the document, you'd have to scroll all the way to the bottom every time you wanted to use it.
+
+We could prevent that by putting the widget in a static flyout at the bottom of the window (as opposed to at the bottom of the //document//). But that means taking more screen space with the interface and splitting the editing tools between two different locations. ",1437698404,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat",*** Bug 69506 has been marked as a duplicate of this bug. ***,1414806319,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","pamdavies7: It is not ""such a big ask"" and the problem is well understood. This is an enhancement request with low priority because there are currently more important things to do, but this will be handled at some point.
+In case you have a tech background, patches are welcome: http://www.mediawiki.org/wiki/Developer_access",1373886151,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","To expand on my point of 07-07: if I'm stub-sorting an article which already has categories, a common technique is to look at a key existing category, see if it has a stub category, if not then go to its parent category, and onwards up the tree (particularly useful in biological taxa etc which are so hierarchic); another technique is to assign a broad stub category and then look at the sub-categories of the stub-category, as being much quicker than going to the full stub listings. Neither of these approaches is possible with VE - I have to either open the article a second time in another tab, or quit VE and do it in Edit Source. 
+
+Please just display clickable links for the categories while I'm editing the article in VE. Is it such a big ask?",1373883409,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","I've been told that [Wikipedia:VisualEditor/Feedback#Categories:_please_display_them_in_VE_-_not_the_right_bug my request] is covered by this bug, so I'll restate it here: please make the categories visible when I'm editing in VE. I can see them when I read an article, or while I'm editing in Edit Source, and I shouldn't have to click on ""Page Data"" to find out whether the article has been categorised or not.",1373238366,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","We've discussed (but there's no bug for it - until now) duplicating the editing of categories in a box at the bottom of the article that would look similar to/the same as the category box in Vector (but with hidden categories shown, and inherited categories not shown). We'd have to properly design this, of course, so it may take a little time.
+
+There's also a proposal to make the dialogs themselves smaller - bug 49549 - and draggable - bug 49969.",1372270719,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","See the screenshot. I get that it's sort of a one-sided diff in a <poem> box, but it isn't particularly useful to review since no tweaks made by the VE that are problematic could be picked out; one would have to review the entire article, in markup.
+
+I'm not sure if there's a better way to work it or if the answer is just to kill it for new page creations, but.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372171920,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-h6w322yrax25ai4skgpq,task_description,declined
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","Closing since (1) we don't have a clear suggestion here, (2) some power editors clearly find the tool useful, and (3) it would be needlessly confusing to normally have a ""review your changes"" button, but take it away when you're creating a page. I've opened T106926 for the main design inconsistency between the two flavors of the dialog. ",1437786780,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","(Oliver Keyes, where's the screenshot?)
+
+Currently on enwiki and mediawiki.org [Review your changes] on a new page displays the wiki text in a <pre> tag, so the wiki markup continues way off to the right side and is almost unusable.
+
+If VE just gave it a style ""ve-review-newpage"" and give it something like
+   white-space: pre-wrap;
+it would be somewhat usable. Or you could use a poem-like div, from comment #0 it sounds like VE used that in June.
+
+Cheers,
+
+(In reply to comment #0)
+> See the screenshot.
+Where? I see no attachments.",1373922321,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","I disagree; albeit as a power-user, I check the resultant wikitext quite often when I'm doing complex things with templates and parser functions (especially the kind that are subst:'ed).
+
+This will be somewhat moot when we have an HTML-based ""review your changes"" available as well, but that's some months off at this point. :-( Rewording.",1372172512,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","I guess the ask is ""can we come up with a better way of handling things, or alternately not load the option to review on new page creations?"" The wikitext editor handles it this way, yes. The wikitext editor sucks at it, and shouldn't be providing that button in that scenario ;p.",1372172349,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour",This is the exact same behaviour as the wikitext editor; I'm not sure what the 'ask' is?,1372172147,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+VisualEditor: sizing of footnote tags (e.g. [12]) inconsistent.,"See https://en.wikipedia.org/wiki/Joe_Flacco?veaction=edit - for example, references 24 and 25 under the section ""2012 season: Super Bowl MVP"". It looks like one of them is using Template:R, which may explain the problem, but I'm not sure if the icon not rendering properly is a template problem or a VE problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372081320,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yifg3bkbmsq2tzfrga4q,task_description,resolved
+VisualEditor: sizing of footnote tags (e.g. [12]) inconsistent.,"Also in https://en.wikipedia.org/wiki/Michelle_%28song%29 sourced to the sfn template, it looks like.",1372125037,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-yifg3bkbmsq2tzfrga4q,task_subcomment,NA
+VisualEditor: sizing of footnote tags (e.g. [12]) inconsistent.,"From that article, references 25 and 26 (from {{r}} and <ref> respectively) generate:
+
+{{r}} ->
+
+<span about=""#mwt97"" class=""reference"" data-mw=""…"" rel=""dc:references"" typeof=""mw:Transclusion  mw:Extension/ref"" data-parsoid=""…"">[25]</a></span>
+
+<ref> ->
+
+<span about=""#mwt99"" class=""reference"" data-mw=""…"" id=""…"" rel=""dc:references"" typeof=""mw:Extension/ref"" data-parsoid=""…""><a href=""…"">[26]</a></span>
+
+Is this just because the CSS isn't being applied when it's ""mw:Transclusion  mw:Extension/ref"" as opposed to just ""mw:Extension/ref""?",1372084163,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yifg3bkbmsq2tzfrga4q,task_subcomment,NA
+VisualEditor: Editing of headings is broken in IE10,"Edit [[User:This, that and the other/sandbox/VE6]] in VE using IE10:
+
+1. Try modifying the heading text. You have to double-click on the heading to be able to modify it. Hopefully this stupid IE behavior can be worked around.
+
+2. Double-click, and modify the heading text. ""Save page"" button is still disabled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372059540,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-rstmsueangena7h4cdaj,task_description,resolved
+VisualEditor: Editing of headings is broken in IE10,This was fixed by undoing MW's overflow:hidden style on headings in https://gerrit.wikimedia.org/r/#/c/144104,1409961747,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-rstmsueangena7h4cdaj,task_subcomment,NA
+"VisualEditor: Broken layout of inspector menu, link inspector (others?) in Monobook","link icon not square
+
+See attachments. Reproduced in Chrome and Firefox by the original reporter, and me.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11416}",1372005420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p5tj36n2mckefr5apd2o,task_description,resolved
+"VisualEditor: Broken layout of inspector menu, link inspector (others?) in Monobook","This has been fixed, AFAICT.",1404168883,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p5tj36n2mckefr5apd2o,task_subcomment,NA
+"VisualEditor: Broken layout of inspector menu, link inspector (others?) in Monobook","Created attachment 12611
+overlapping recycle bin
+
+**Attached**: {F11417}",1372005461,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p5tj36n2mckefr5apd2o,task_subcomment,NA
+"OutputPage: Don't output mw.loader.state ""loading"" and mw.loader.state ""ready"" for the same module","It looks like we currently output both for some modules.
+
+Current output on a wiki with user and site css/js enabled[1] but empty:
+
+<script>if(window.mw){
+mw.loader.state({""site"":""loading"",""user"":""loading"",""user.groups"":""loading""});
+}</script>
+<script>if(window.mw){
+mw.loader.load([""mediawiki.action.view.postEdit"",""mediawiki.user"",""mediawiki.hidpi"",""mediawiki.page.ready"",""mediawiki.searchSuggest"",""mediawiki.page.watch.ajax"",""ext.vector.collapsibleNav"",""ext.visualEditor.viewPageTarget"",""skins.vector.js""],null,true);
+}</script>
+<script>if(window.mw){
+mw.loader.state({""site"":""ready""});
+}</script>
+<script>if(window.mw){
+mw.loader.state({""user"":""ready""});
+}</script>
+<script>if(window.mw){
+mw.loader.state({""user.groups"":""ready""});
+}</script>
+
+The first one with ""loading"" is always output. The last 3 with ""ready"" are output by OutputPage::makeResourceLoaderLink if $module->isKnownEmpty is true.
+
+We should probably optimise this to just output ""ready"" in the first place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371976440,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-r3jcy4x4njr5hh24ytpk,task_description,resolved
+"OutputPage: Don't output mw.loader.state ""loading"" and mw.loader.state ""ready"" for the same module","> resourceloader: Refactor module links output 
+>
+> Change-Id: I91754ce5fae3d05b4bfa7372372eba81ee2fc579",1412588792,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-r3jcy4x4njr5hh24ytpk,task_subcomment,NA
+"OutputPage: Don't output mw.loader.state ""loading"" and mw.loader.state ""ready"" for the same module","This looks fixed for me, because at the moment I will get directly
+mw.loader.state({""site"":""ready"",""user"":""ready"",""user.groups"":""ready""});
+when there is no site or user js page (bug 46857?).",1408907579,PHID-USER-qaoxfiqu6bxhd5ehlwhc,PHID-TASK-r3jcy4x4njr5hh24ytpk,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"https://www.mediawiki.org/wiki/Help:Magic_words#Variables
+
+{{CURRENTYEAR}}, {{CURRENTMONTH}], etc. - possibly a pop-up inserter with a brief description of what each do (and their current value?)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62740",1371860100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dljoa7k34bkwqsbvudos,task_description,open
+VisualEditor: Provide a way for users to insert variable magic words,"Change 278429 abandoned by Alex Monk:
+[WIP] Add MagicWord::getDocs and i18n messages for documentation of magic words
+
+[[https://gerrit.wikimedia.org/r/278429]]",1484005244,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Change 140445 abandoned by Alex Monk:
+[WIP] Allow TemplateData to output information about magic words
+
+[[https://gerrit.wikimedia.org/r/140445]]",1483653103,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Change 278429 had a related patch set uploaded (by Alex Monk):
+[WIP] Add MagicWord::getDocs and i18n messages for documentation of magic words
+
+[[https://gerrit.wikimedia.org/r/278429]]
+",1458351113,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Change 140445 had a related patch set uploaded (by Jforrester):
+[WIP] Allow TemplateData to output information about magic words
+
+[[https://gerrit.wikimedia.org/r/140445]]
+",1456023513,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Change 140445 had a related patch set uploaded by Alex Monk:
+[WIP] Allow TemplateData to output information about magic words
+
+https://gerrit.wikimedia.org/r/140445",1403119862,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,2014-06-16 22:00:29	<Krinkle>	but we'll need to implemetn support for the colon argument in Parsoid and VisualEditor DM first.,1403110567,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"(In reply to Alex Monk from comment #5)
+> Apparently some of the magic words involving 'colon arguments' will need
+> Parsoid/VE DM support.
+
+Does Parsoid not split out the zeroth argument or something? If so, is there a bug that this can be made semi-dependent on?",1403060528,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,Apparently some of the magic words involving 'colon arguments' will need Parsoid/VE DM support.,1402958830,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"(In reply to Alex Monk from comment #3)
+> Actually, maybe we should just have VE query
+> api.php?action=query&meta=siteinfo&siprop=magicwords, then load a
+> documentation message for it in the given language.
+
+no, ignore this",1402945015,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Actually, maybe we should just have VE query api.php?action=query&meta=siteinfo&siprop=magicwords, then load a documentation message for it in the given language.",1402761433,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"So we need to:
+
+* Alter TemplateData to provide documentation for magic words
+* Add extra field to template insert dialog for the addition of magic words.",1402696798,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,Feel like taking this on? It'd be a step towards fixing bug 50855 in general… Big fun challenge. :-),1402608512,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Table of Contents should be a draggableNode and insert __TOC__ as needed,"It should be possible for users to modify the location of the TOC (see bug 49224 for getting it shown and updated as they edit), and the system should insert a __TOC__ identifier (that should be silently dropped by Parsoid when not needed?).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371859800,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zgftkji5nk4n25cdqxjy,task_description,open
+"VisualEditor: No way to identify destination, rather than link text, of links","Because the VE splits up the destination of a link and the text displayed for it (quite rightly) it's impossible, in VE mode, to identify where links point to without source editing. This is kind of a problem for disambiguation issues, for example. Is there any way that this could somehow be hunt-down-able?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371790440,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-e3ncbibtfnsjabzzzce6,task_description,resolved
+"VisualEditor: No way to identify destination, rather than link text, of links","It's nice, but doesn't really address the workflow in comment 3.
+
+(In reply to James Forrester from comment #3)
+> However, this doesn't work well if you know there's one link to [[foo|xxx]]
+> somewhere on the page and you want to change it to [[bar|xxx]], I agree.",1402566355,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links",This is now done with the new context widget system.,1402550246,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links","No, hovering over each link is not the answer: if I'm looking at a large article and want to find and amend the link which is pointing to some particular other page (perhaps in connection with cleaning up dab pages etc), I want to be able to use something like ctrl-F ""Find"" as I can at present: once the article is open in Edit Source, the hidden text is searchable.
+
+As an example, look at [[User:PamD/sandbox for VE]] and find the link to [[Dunmallet]]. Now imagine if that page was the length of [[London]] and you needed to find a similar piped link.
+
+Might also be an issue if people want to find (and check parameters of, or amend, etc) one particular template which is used on a page, but doesn't ""show up"" in the visible article. And probably various other scenarios. ~~~~",1373190367,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links","(In reply to comment #0)
+> Because the VE splits up the destination of a link and the text displayed for
+> it (quite rightly) it's impossible, in VE mode, to identify where links point
+> to without source editing. This is kind of a problem for disambiguation
+> issues, for example. Is there any way that this could somehow be
+> hunt-down-able?
+
+Hover over the link; that's the target, not the anchor, that comes up in the pop-up tooltip. 
+
+However, this doesn't work well if you know there's one link to [[foo|xxx]] somewhere on the page and you want to change it to [[bar|xxx]], I agree.",1372015806,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links","The workflow of ""this article has DAB issues, it's pointing to [disambiguation page], I should point it to [proper page], now to find the link that's pointing to the disambig- shit.""",1371791889,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links","You can just click the floating ""chain"" icon to see the name of the destination article. 
+
+What does this bug relate to in particular? Was there some use case where this isn't working/isn't possible?",1371791727,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","User:JohnCD at English Wikipedia writes the following:
+""If you enter, for instance, ""Welcome"" in the new template box, on clicking ""Apply changes"" you see the result; but if you enter ""subst:welcome"" you see only {{subst:welcome}}, though after clicking ""Save page"" the result is correct. Should there be a check-box for ""subst"" in the New template dialogue, (a) to save typing it out, (b) to arrange the correct display?""
+
+James F. suggested this would be good to enter as an enhancement request, since template substitution should be supported.
+
+Maggie
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66281",1371756600,PHID-USER-joqqkabmjmvxeucx4ni2,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_description,open
+"Support ""substituting"" templates in transclusion dialog","@matmarex , the [[ https://en.wikipedia.org/wiki/Module:Unsubst | unsubst module ]] can be used in most cases to prevent inexperienced editors from accidentally using substitution erroneously. Beyond that, a better version of TemplateData would allow for instruction about substitution for each template.
+
+For now, I think allowing substitution in VE is still a worthwhile goal, even if it has to remain a somewhat advanced/hidden feature to avoid improper use.",1668563742,PHID-USER-tl3o6dlackm57f3qrt4b,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 855565 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] ParsoidHandler: remove subst feature from wt2html%%%
+https://gerrit.wikimedia.org/r/855565",1668101234,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","For context about this patch: @daniel discovered that feature in Parsoid while doing some refactoring, and we discovered that we were not using it. All it does is to add `subst:` to template invocations, before calling existing APIs for pre-save transform and for parsing. That doesn't seem useful even if we wanted to add substing templates to VE (we could easily add this prefix and call the APIs ourselves).
+
+We're not planning to work on this task apart from this at the moment. The main obstacle is designing the interface so that people wouldn't damage articles by using it without understanding what it does.",1668093586,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 855565 had a related patch set uploaded (by Daniel Kinzler; author: Daniel Kinzler):
+%%%[mediawiki/core@master] ParsoidHandler: remove subst feature from wt2html%%%
+https://gerrit.wikimedia.org/r/855565",1668086122,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Yes, that's the goal.  There is no timeline for when the work might be done.",1623088652,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Am I right in understanding that this ticket seeks to make it possible to use subst when adding a template to a page in VisualEditor, or is that another task?",1622827126,PHID-USER-tl3o6dlackm57f3qrt4b,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Parsoid's API supports substing. But, VE folks need to figure out what they exactly need to support user feature requests. I'm going to untag Parsoid here. @Esanders @matmarex @JTannerWMF: please take a look and retag Parsoid with an updated description if you need anything from us.",1590034383,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Another request for this, this time from @Hoefsldyla :  https://www.mediawiki.org/wiki/Topic:Uq6vtaf8wk0z30zh
+",1548380239,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","[[ https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=0&oldid=123998059#Subst_dans_le_mod.C3.A8le_ouvrage | New feedback ]] concerning that task (here, need to subst: a date on a template included with VE).",1457356882,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",">>! In T51904#1406296, @Krenair wrote:
+> I'm not sure the parsoid API from T73161 is quite what we were looking for. The idea had been to allow the user to mark a template to be substituted upon save, but with this we'd have to substitute an entire transclusion (immediately?)
+
+If you look at this task's description, it asks for being able to do a subst when inserting a template from the template dialog box. Also, according to the description, susbt already works when saving.",1435560829,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","If I have misunderstood this feature and how it would work inside VE, then we should talk more on IRC sometime to get clarity about how this would / should work and update it here, and we can make appropriate updates to the API.",1435360448,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",">>! In T51904#1406342, @Krenair wrote:
+> Substituting things directly on the client? That sounds like we'd run into more issues involving unbalanced html fragments?
+
+Yes, subst directly on the client. In VE, as far as I understand, you cannot add transclusions that generate unbalanced HTML since you have to ask Parsoid for an expansion and you get balanced DOMs always.
+
+So, as far as I can imagine, this subst feature in VE will have to be in-edit substitution of DOMs rather than on-save substitution of arbitrary wikitext.",1435360176,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",">>! In T51904#1406342, @Krenair wrote:
+> Substituting things directly on the client? That sounds like we'd run into more issues involving unbalanced html fragments?
+
+Yes, subst directly on the client. In VE, as far as I understand, you cannot add transclusions that generate unbalanced HTML since you have to ask Parsoid for an expansion and you get balanced DOMs always.
+
+So, as far as I can imagine, this subst feature in VE, it will have to be in-edit substitution of DOMs rather than on-save substitution of arbitrary wikitext.",1435360150,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",Substituting things directly on the client? That sounds like we'd run into more issues involving unbalanced html fragments?,1435359746,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","But yes, you would have to substitute transclusions immediately, rather than ""on-save"" as with the wikitext PST mode of operation.",1435359430,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",">>! In T51904#1406296, @Krenair wrote:
+> I'm not sure the parsoid API from T73161 is quite what we were looking for. The idea had been to allow the user to mark a template to be substituted upon save, but with this we'd have to substitute an entire transclusion (immediately?)
+
+But, whenever a user edits a transclusion, you are querying the API to fetch the expansion. So, you would enable the subst parameter alongwith the query instead of marking up individual transclusions for 'at-save' substitution. Once substed, the transclusion itself goes away and the editor can further tweak that output if required.",1435359220,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","I'm not sure the parsoid API from T73161 is quite what we were looking for. The idea had been to allow the user to mark a template to be substituted upon save, but with this we'd have to substitute an entire transclusion (immediately?)",1435358724,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 153895 abandoned by Alex Monk:
+Add a subst property to template data which adds ""subst:"" to the target
+
+Reason:
+I'm not actually planning to work on this commit. The associated VE commit will continue to depend on this however.
+
+https://gerrit.wikimedia.org/r/153895",1412721735,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 153934 had a related patch set uploaded by Alex Monk:
+Provide a checkbox on template page of transclusion dialog to substitute when saving
+
+https://gerrit.wikimedia.org/r/153934",1407964061,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 153895 had a related patch set uploaded by Alex Monk:
+Add a subst property to template data which adds ""subst:"" to the target
+
+https://gerrit.wikimedia.org/r/153895",1407963687,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Subst:ing isn't working (again?  still?).  
+
+If you follow the (soon-to-be-blanked) directions in the user guide, you get the text typed in, with no display, no expansion, and no processing.  The result is that the exact wikitext of your template displays on the page, exactly as if it had been nowiki'd, but without the nowiki tags.
+
+https://en.wikipedia.org/w/index.php?diff=620566012&oldid=618729009",1407626540,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Not only in insert dialogue. Template text should be inserted and rerendered page immediately.
+for example:
+-[[:en:Template:Accent]]
+-[[:ru:Шаблон:Ударение]]
+
+i do
+-te|xt
+-insert/template - subst:Ударение
+
+i see in VE
+-te{{subst:Ударение}}xt
+(after saving the page text in read mode looks normally: téxt)
+
+
+I want to see in VE
+-téxt
+
+if possible it should be a new method ""template (with parameters) to text ()"" with no return to template
+for example:
+-""insert/subst"" or ""insert/template"" and in dialogue check-box for ""subst""
+-open TemplateData for ""template"" (now for ""subst:template"" TemplateData not shown)
+-press Add template
+-template is executed and generate new text which is inserted same as ctrl+v
+-the new text (or all page) rendered (may consist any other template inside it)",1406716486,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",*** Bug 59182 has been marked as a duplicate of this bug. ***,1389931233,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","(In reply to comment #4)
+> (In reply to comment #3)
+> > (In reply to comment #2)
+> > > This is effectively a subset of bug 49833 which seems to be part tracking,
+> > > part bugs, part enhancement requests
+> > 
+> > … part mess. :-(
+> > 
+> > Not sure why you turned it into a tracker after Krinkle mis-named it; I don't
+> > think it helps at all. I might undo that.
+> 
+> Sorry, that would be my misunderstanding of Krinke's intentions and then
+> trying to be helpful. :(
+
+Not your fault at all. :-) All fixed now, anyway.",1378227406,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","(In reply to comment #3)
+> (In reply to comment #2)
+> > This is effectively a subset of bug 49833 which seems to be part tracking,
+> > part bugs, part enhancement requests
+> 
+> … part mess. :-(
+> 
+> Not sure why you turned it into a tracker after Krinkle mis-named it; I don't
+> think it helps at all. I might undo that.
+
+Sorry, that would be my misunderstanding of Krinke's intentions and then trying to be helpful. :(",1377908456,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","(In reply to comment #2)
+> This is effectively a subset of bug 49833 which seems to be part tracking,
+> part bugs, part enhancement requests
+
+… part mess. :-(
+
+Not sure why you turned it into a tracker after Krinkle mis-named it; I don't think it helps at all. I might undo that.",1377899956,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","This is effectively a subset of bug 49833 which seems to be part tracking, part bugs, part enhancement requests",1377897429,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",Lots of important templates need subst. On en {{prod}} and {{afd}} both need to be subst.,1377871154,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"It seems that the server part of this is already correct.  The client just needs to add printable=1 to requests for JS-wrapped CSS should include printable=1, when the page is in print mode (printabable=yes).
+
+This is necessary to make sure that screen CSS is omitted and print CSS is not wrapped in @media print for this use case.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal",1371510780,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-uou7qnzilekcbteofdw4,task_description,declined
+ResourceLoader does not process media queries for printable view with JS-added CSS,"Given {T24256} was resolved, that means the printable mode is essentially no longer discoverable/advertised to users. I'm closing this task in favour of T167956.",1507244402,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"I think {T24256} is definitely better than simply dropping the link entirely (although we'd have to hide it for no-JS).  A feature is only useful if users know about it, and I think having the link exposes the fact that our pages look reasonably good when printed.",1433302393,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"I do know that the ""printable"" link, in the past had surprising amount of traffic for other websites. As in: without it, people don't know how to print (yes, i know, i know...)
+
+So if we do remove the printable mode, then having the JS enabled print mode link is probably quite desirable I suspect.",1433165098,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"> Given that we should support printing the view page directly, perhaps it makes sense to remove the ""Printable"" mode from MediaWiki? 
+
+{T24256}",1433112549,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,">>! In T51722#569487, @Mattflaschen wrote:
+> [..]
+> That illustrates that the print styles apply to the current DOM, not the original HTML source.  So even if the JS doesn't run in printable=yes, all the print styles still need to be correct in case they just print directly (without using printable view).
+
+I agree. In fact, I suspect users that print pages would just print directly. It seems counterintuitive to first open a ""Printable version"".
+
+Given that we should support printing the view page directly, perhaps it makes sense to remove the ""Printable"" mode from MediaWiki? The interface to print pages is part of the web browser. Having a control for it seems redundant.
+
+If we want to keep it, we could collect analytics on popularity of printable=yes views in relation to [print events](http://tjvantoll.com/2012/06/15/detecting-print-requests-with-javascript/) (from both printable, and regular mode).",1433110472,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"Not actively working on this, so putting it back in the pool, but I think the original issue holds.  It seems we should either:
+
+1. Pass printable to load.php on printable=yes pages.
+2. Not run JS on printable=yes pages (as Krinkle says was the case earlier).",1393371920,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"Change 69276 abandoned by Krinkle:
+ResourceLoader: Pass printable parameter to load.php.
+
+Reason:
+Closing for now.
+
+https://gerrit.wikimedia.org/r/69276",1393321150,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"(In reply to comment #2)
+> Which is wrong, those things are not supposed to be loaded on a print page
+> (to avoid e.g. collapsible buttons, ""[show]"", etc.). Though some of those are
+> hidden by CSS, it'd be better for them to not initialise in the first place.
+
+Well, if we do that, we need to find an equally simple way to debug the print CSS.  There are extensions that are supposed to do it (e.g. https://addons.mozilla.org/en-US/firefox/addon/web-developer/), but it shows the screen *and* print styles.  There's probably a good way to do it, just need to find it.
+
+More importantly to the average user, we may want to run some JS on the printable=yes view.  People sometimes read in that view, and there's some stuff that works in that bare-bones mode.
+
+For instance, the reference popups on enwiki (https://en.wikipedia.org/wiki/MediaWiki:Gadget-ReferenceTooltips.js) currently work there, and it seems useful.  You can even get the popup to print with some finagling.
+
+That illustrates that the print styles apply to the current DOM, not the original HTML source.  So even if the JS doesn't run in printable=yes, all the print styles still need to be correct in case they just print directly (without using printable view).",1371531290,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"We didn't pass this to the client and on to load.php because printable pages shouldn't run run any load queue.
+
+http://mediawiki.dev/?printable=yes gives me:
+> #top:
+> mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax""]);
+> #bottom:
+> mw.loader.load([""mediawiki.action.view.postEdit"",""mediawiki.user"",""mediawiki.hidpi"",""mediawiki.page.ready"",""mediawiki.searchSuggest"",""mediawiki.page.watch.ajax"",""ext.vector.collapsibleNav"",""ext.vector.collapsibleTabs"",""ext.visualEditor.viewPageTarget"",""skins.vector.js""],null,true);
+
+
+Which is wrong, those things are not supposed to be loaded on a print page (to avoid e.g. collapsible buttons, ""[show]"", etc.). Though some of those are hidden by CSS, it'd be better for them to not initialise in the first place.
+
+I think this is a regression. If memory serves, not so long ago there were no mw.loader calls on the printable view. Perhaps a change in Skin caused them to be inserted unconditionally?
+
+Either way, if there is no other way around it, then the proposed change is good, but I'd prefer to prevent the client-side loader from being set up in the first place (so only the <link only=styles> will run).",1371523555,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,Related URL: https://gerrit.wikimedia.org/r/69276 (Gerrit Change I691588c39da7fadeac1ca2ace2c1b769fc4e1bd6),1371519777,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+VisualEditor: Diff is done with current revision instead of old revision when editing an old revision,"When I am editing an old revision of a page and then view the diff before saving it is the diff between the current version of the page and my edited version it seems. I was expecting to see the diff between the old revision and my edited version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371475440,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-xnegl5h6ucwhzlod3aip,task_description,declined
+VisualEditor: Diff is done with current revision instead of old revision when editing an old revision,"Oh I wasn't aware the wikitext-editor is doing the same. Then I guess you can close it. It should probably be consistent.
+
+And yes the message could probably be improved.",1371542654,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-xnegl5h6ucwhzlod3aip,task_subcomment,NA
+VisualEditor: Diff is done with current revision instead of old revision when editing an old revision,"This is the same behaviour as the wikitext editor. :-)
+
+Theoretically we could have diff-against-current and diff-against-starting-point, but that could be a bit messy.
+
+Do you think the message (""review your changes"" in VE against ""review changes"" in wikitext) is confusing and should be changed?",1371488556,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xnegl5h6ucwhzlod3aip,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly","Screenshot
+
+See on https://en.wikipedia.org/wiki/Brainbuster for example, at the bottom - screenshot attached. Reproduced in Chrome, Firefox and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11473}",1371464940,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-msldrstq5fb4d2d5owxm,task_description,resolved
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly",Seems to be fixed - confirmed in test2/production.,1422408680,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly",I believe that this was fixed by Ed's work on this last week.,1402549729,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly","(In reply to comment #2)
+> I had wondered whether the fix for bug 54446 would solve this too, but at
+> least in Firefox 24.0 on Linux it is still evident.
+
+Yeah, this is actually a rather more fundamental issue (the ""next"" item from the data model's point of view, if not the user's, is indeed a link). Sorry.",1380324768,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly","I had wondered whether the fix for bug 54446 would solve this too, but at least in Firefox 24.0 on Linux it is still evident.",1380323919,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly","This only seems to happen with an image at the start of the lead section and seems unaffected by the presence of a template,
+
+Test case: 
+https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=567508072&veaction=edit
+
+Real-world example:
+https://en.wikipedia.org/w/index.php?title=Boden_Professor_of_Sanskrit_election%2C_1860&oldid=567473898&veaction=edit",1375863022,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,"See also: T51633, T52341",1371431700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oipcbzqxlofc3iyaefws,task_description,open
+<title> of editing page doesn't respect DISPLAYTITLE,See also {T88117},1427239342,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,Moving to MW core.,1416183397,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,"If I'm right that it's consistent with core, this bug should be moved there.",1398979991,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,"I think this is about VE changing the <title> to ""Editing IPod"", which doesn't respect displaytitle? If so, this is consistent with core's behaviour...",1398776732,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,"Current bug summary: ""VisualEditor: Title doesn't respect DISPLAYTITLE"".
+
+I'm not sure what this means. Looking at the links below, I see various issues, but none related to the <h1>. The <title> is a bit weird, but it's weird without VisualEditor as well.
+
+* https://en.wikipedia.org/wiki/IPod?veaction=edit
+* https://test.wikipedia.org/wiki/IPod?veaction=edit
+
+Further clarification (including links) would be helpful here.",1371441334,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,"Some suggestions of improvements to the media insertion dialog; this is mostly a brain-dump which we might turn into a tracker later:
+
+- a way of accessing the file page, on Commons or elsewhere
+- a more clear highlighting
+- maybe slightly enlarging the image
+- double-click to insert
+- filter by: …
+-* media type
+-* language (mostly specific to audio/video but also maps/diagrams)
+-* length (audio/video)
+-* resolution (image/video)
+-* video bit-depth (image/video)
+-* audio bit-depth (video/audio)
+-* sample rate (audio)
+-* format
+-* licence
+-* local vs. Commons
+
+Notes:
+
+The image size is based on the largest default thumbnail (the dialog asks for the 300x300px image and then shows it at 150x*px size). Changing this would need to have discussions with Ops about load on the image renderers and possibly changing the default sizes globally.
+
+The filtering will have to wait for Solr faceted search, if that's indeed coing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51032",1371425280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_description,resolved
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,"The first part of this is now done by the wonderful Structured Data team's work on #sdaw-mediasearch, which they've now integrated into VisualEditor. The initial work has address the most pressing problem of language; I expect that the faceted search ideas might come later. Thank you!",1613688042,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_subcomment,NA
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,"It makes more sense to combine all the media-related bugs into bug 37870 as a tracker, and use this for its original intent, to be about structured data about files and using that for inserting.",1394082888,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_subcomment,NA
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,I'm marking a few other improvement suggestions filed as bugs as blockers so they don't get lost.,1377625064,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_subcomment,NA
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,"It'd be nice to be able to search only by file name, if you know the title or know that that the file you want has a particular word in its name.  ""Intitle:apple"" cuts the number of images by 70%, which is a big help when there are ~12K files returned on that search.",1377191107,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_subcomment,NA
+VisualEditor: Empty annotations which display are hidden as alienMetas,"Per Ed's comment on T50605:
+
+> Above change fixes issue with annotations being dropped, but we still need to fix empty annotations not rendering (e.g. `<span style=""display: block; background: red; width: 100px; height: 100px;""></span>`), either here or in a new bug.
+
+This is the new bug. :-)
+",1371065040,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cka2ffmhei6ufmfdjpyi,task_description,open
+VisualEditor: VE crash mid-edit in IE9,"**Author:** `and.radiate`
+
+**Description:**
+Using alpha version as of 11JUN13. Did a small edit on Wikipedia English article ""Nagato-class battleship"" (deleting 3 letters from [Japanese] to form [Japan] in second sentence under section 5.1 World War II. Then scrolled down; after originally displayed area scrolled off screen, the screen went black in the TAB.  Other TABs in IE remained operative.  Back arrow did not produce any results on black screen or URL showing for the Wikipedia TAB.  Reloaded http://en.wikipedia.org in TAB with black screen; successfull load and correct operation thereafter.  Could not reproduce the error.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370999220,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-e6ljc4wlzprcqdkdk7fk,task_description,resolved
+VisualEditor: VE crash mid-edit in IE9,"No reproduction steps in three years, over which time it's been significantly changed. I'm marking this as Resolved for now.",1465404791,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e6ljc4wlzprcqdkdk7fk,task_subcomment,NA
+VisualEditor: VE crash mid-edit in IE9,and.radiate: Have you seen this problem again with a more recent VE version?,1408109540,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-e6ljc4wlzprcqdkdk7fk,task_subcomment,NA
+"VisualEditor: Font weight is removed from ""article"" tab in Monobook","VisualEditor is removing the font weight from the ""article"" tab when using Monobook on the English Wikipedia.
+
+Steps to reproduce:
+
+* Go to <https://en.wikipedia.org/wiki/Canada_Goose_(clothing)>
+
+* Click ""edit this page"".
+
+* The ""article"" tab loses its boldness.
+
+* Clicking the ""cancel"" button does not restore the boldness.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370896140,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-qf4dixqxm23hinqfnhhq,task_description,resolved
+"VisualEditor: Font weight is removed from ""article"" tab in Monobook","Change 130085 merged by jenkins-bot:
+Fix tab selection on monobook
+
+https://gerrit.wikimedia.org/r/130085",1398881455,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qf4dixqxm23hinqfnhhq,task_subcomment,NA
+"VisualEditor: Font weight is removed from ""article"" tab in Monobook","Change 130085 had a related patch set uploaded by Alex Monk:
+Fix tab selection on monobook
+
+https://gerrit.wikimedia.org/r/130085",1398699745,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qf4dixqxm23hinqfnhhq,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"E.g. [[:fr:Foo]] or [[m:Foo]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1370631180,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u7fscppwehap7w2btqmk,task_description,resolved
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"As Roan says, external links are now silently converted to interwikis when appropriate by Parsoid, so this is totally possible, and has been since we fixed it in November.",1396028566,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"This is kind of possible now, by creating external links.",1385136692,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"I just tried adding a link with [[:w:eo]] and got this:
+http://www.mediawiki.org/w/index.php?title=Language_portal%2FWikimania2013%2FEvent_Report&diff=768410&oldid=768371
+
+[Changed the title to avoid confusion with interlanguage links.]",1377094621,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,*** Bug 50889 has been marked as a duplicate of this bug. ***,1374331394,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"It's actually already possible to create interwiki links by including the interwiki prefix in the link editor; example with wikitech: https://www.mediawiki.org/w/index.php?diff=729932 .
+
+Interwiki links that have been created this way with VisualEditor can still be edited the same way as long as the page isn't saved.
+
+Since this works for new and newly-added interwiki links, I'm not sure why they're blacklisted / green-striped in subsequent edits.",1373532188,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,*** Bug 49545 has been marked as a duplicate of this bug. ***,1371150585,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: Toolbar button text doesn't line up vertically,"See http://imgur.com/wmAeHRD
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370522640,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-262uhvu3ikqle2l6ewsw,task_description,invalid
+VisualEditor: Toolbar button text doesn't line up vertically,No longer applicable,1392388033,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-262uhvu3ikqle2l6ewsw,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"This is bad, though in a relatively edge case of lanklinks outside the main namespace.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370489100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpzuaoygi6lx5pro226s,task_description,resolved
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"Change 127419 merged by jenkins-bot:
+Use wgPageName instead of wgTitle when fetching language links
+
+https://gerrit.wikimedia.org/r/127419",1398108169,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"Change 127419 had a related patch set uploaded by Catrope:
+Use wgPageName instead of wgTitle when fetching language links
+
+https://gerrit.wikimedia.org/r/127419",1397886324,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),*** Bug 50565 has been marked as a duplicate of this bug. ***,1381266333,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"(In reply to comment #1)
+> This description is a bit cryptic, so .. is bug 50565 a dup of this bug?
+
+It is, yes; sorry for crypticness. Hope it's a little better now.",1381266327,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"This description is a bit cryptic, so .. is bug 50565 a dup of this bug?",1381108150,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"Users and categories should not be auto-completed based on page names (API action=opensearch) but instead based on their own respective query modules (list=allusers, list=allcategories) because the existence of a description page is optional and neither a subset nor superset of the database tables.
+
+* Pages can exist for inexistent objects.
+* Objects often don't have an associated page.
+
+718db58f introduced category editing with autocompletion from opensearch (with hardcoded 'Category:' prefix). This should be switched to using list=allcategories instead.
+
+That way the input field will no longer include results for inexistent categories, and no longer omit results for existing categories lacking a description page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65517",1370113020,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qh6gg46z66xqohu77fjn,task_description,resolved
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,*** Bug 65956 has been marked as a duplicate of this bug. ***,1401483580,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"Change 135782 merged by jenkins-bot:
+Suggest categories that exist but don't necessarily have pages
+
+https://gerrit.wikimedia.org/r/135782",1401321989,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"Change 135782 had a related patch set uploaded by Alex Monk:
+Suggest categories that exist but don't necessarily have pages
+
+https://gerrit.wikimedia.org/r/135782",1401295064,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"(In reply to comment #1)
+> Though I commend the effort for correctness, I don't think that this has ever
+> even been brought up in the HotCat feedback. It would be nice though.
+> 
+> However, an empty category (page only), is still a valid category in most
+> workflows (you have to start somewhere), so I think that excluding them is no
+> more correct than including categories without pages...
+
+(Whilst not defending the current MediaWiki behaviour) the way you start a new category is either:
+* Create the description page
+* Add pages to it from wikitext with [[Category: <name> ]]
+or:
+* Implicitly create it by adding pages to it from wikitext with [[Category: <name> ]]
+
+The same is true for HotCat, afaik you can use a category that doesn't exist yet. The page is optional and the 'Category' table row will be created once there are items in it (though it doesn't delete the row if there are no more children in it, so you can still have category pages for categories that don't ""exist"" but do exist in the database).
+
+Either way I think it is more likely for a user to want to add a page to a category that is used on another page (which may or may not have a description page yet) then for a user to first create a category page and then add a page to it. Especially on established wikis.
+
+I agree it doesn't really make sense but this is how MediaWiki works. We could change MediaWiki core to also create category rows immediately when the page is created.
+
+We could do 2 ajax requests for every autocomplete action but that seems a bit too much, and given the choice between the two I think completing based on existing categories instead of category description pages, the former is more likely and also has larger volume (there are more categories than there are description pages, there are relatively few category pages for categories that don't exist, ideally a wiki would have none of them).",1372102674,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"Though I commend the effort for correctness, I don't think that this has ever even been brought up in the HotCat feedback. It would be nice though.
+
+However, an empty category (page only), is still a valid category in most workflows (you have to start somewhere), so I think that excluding them is no more correct than including categories without pages...",1370372523,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+"VisualEditor: On save, warn the user about inconsistent header indexes","It would be very nice if the Ve would warn you about inconsistencies in header levels (when you are skipping a level for instance)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1370005980,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-i4fozwumgivhnul7k3yd,task_description,open
+"VisualEditor: On save, warn the user about inconsistent header indexes","Nice idea.
+
+Possible rules:
+
+* Use of H1 in the main namespace
+* Use of Hn+1 not inside an Hn
+* Others?",1370633090,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-i4fozwumgivhnul7k3yd,task_subcomment,NA
+VisualEditor: Whitespace characters should not take a pre-annotation unless they have non-whitespace after them in the annotation,"In https://de.wikipedia.org/w/index.php?title=Anna_Zaja&curid=7691608&diff=118985342&oldid=118754158 a missing space was added after the name, but it should not be inside the bold part.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://de.wikipedia.org/w/index.php?title=Anna_Zaja&curid=7691608&diff=118985342&oldid=118754158",1369820460,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-6lw5ypbid2gpphswv2j6,task_description,open
+VisualEditor: Whitespace characters should not take a pre-annotation unless they have non-whitespace after them in the annotation,"Rephrased to ""Whitespace characters should not take a pre-annotation unless they have non-whitespace after them in the annotation"". This means that we have to evaluate whether pre-annotation should take place on insertion against both the content and the context, but then re-evaluate on the first non-WS character in a potential pre-annotation. This could get messy.",1372026701,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-6lw5ypbid2gpphswv2j6,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Situation:
+* ResourceLoader wraps modules in closures
+* MediaWiki developers put a closure in each file
+* As a result loading 1 module with 2 files will have 3 closures
+
+```
+mw.loader.implement( 'foo', function ( $ ) {
+  --- foo.a.js
+  ( function ( $, mw ) { 
+    ...
+  }( jQuery, mediaWiki ) )
+
+  --- foo.b.js
+  ( function ( $, mw ) { 
+    ...
+  }( jQuery, mediaWiki ) )
+} );
+
+inside mw.loader#execute:
+
+  script( jQuery );
+```
+
+It has been suggested we add ""mw"" to ResourceLoader's closure and get rid of the per-file closure.
+
+The downside of doing that would be that they are less safe to use ""standalone"". e.g. a jquery plugin would be using $ directly, which, outside MediaWiki ResourceLoader context is bad.
+
+There is also the pending refactoring of ResourceLoader debug mode to not be completely different and near useless by executing in the global scope.
+",1369733580,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-knvyif3q5u66km5ufvcb,task_description,resolved
+ResourceLoader: Remove obsolete closures from files,"Change 534762 **merged** by jenkins-bot:
+[mediawiki/core@master] mediawiki.util: Remove redundant file closures
+
+[[https://gerrit.wikimedia.org/r/534762]]",1567876799,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 534762 had a related patch set uploaded (by Fomafix; owner: Fomafix):
+[mediawiki/core@master] Remove redundant closure for module 'mediawiki.util'
+
+[[https://gerrit.wikimedia.org/r/534762]]",1567756299,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 518951 had a related patch set uploaded (by Fomafix; owner: Fomafix):
+[mediawiki/extensions/CentralNotice@master] Remove redundant closure for all packageFiles with own directory
+
+[[https://gerrit.wikimedia.org/r/518951]]",1561457574,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 512519 had a related patch set uploaded (by Fomafix; owner: Fomafix):
+[mediawiki/core@master] Remove redundant closure for all modules with packageFiles
+
+[[https://gerrit.wikimedia.org/r/512519]]",1558862601,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 501993 **merged** by jenkins-bot:
+[mediawiki/core@master] Remove redundant closure for all packageFiles with own directory
+
+[[https://gerrit.wikimedia.org/r/501993]]",1554861690,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 501993 had a related patch set uploaded (by Fomafix; owner: Fomafix):
+[mediawiki/core@master] Remove redundant closure for all packageFiles with own directory
+
+[[https://gerrit.wikimedia.org/r/501993]]",1554628343,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 501960 **merged** by jenkins-bot:
+[mediawiki/core@master] mediawiki.Title: Remove redundant closure
+
+[[https://gerrit.wikimedia.org/r/501960]]",1554594846,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Effectively fixed by T133462, which makes this a possibility regardless of debug mode.
+
+I'm closing this as resolved as it is now possible with T133462 to lint a file as a ""module"" (similar to Node.js) without needing a closure. The only reason our files had closures is for compatibility with debug mode. And for modules using packageFiles, debug mode has been fixed to not change the execution scope.
+
+This does mean we can remove them from files not loaded as part of a module bundle that uses packageFiles, but it seems good enough for me.
+
+Maybe as part of  T85805, we will make it possible for legacy modules, but that's TBD, and separate from this task.",1554583100,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 501960 had a related patch set uploaded (by Krinkle; owner: Krinkle):
+[mediawiki/core@master] mediawiki.Title: Remove redundant closure
+
+[[https://gerrit.wikimedia.org/r/501960]]",1554582926,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Note that this bug isn't blocked on implementing global variable mappings.
+
+This bug basically says:
+
+* Closures added by ResourceLoader are not merely a by-product of the deferred loading. They are part of the eco system and to be relied on.
+* Drop the tradition that each .js file should be loadable raw and standalone and instead embrace the dynamic build system.
+
+The main thing blocking this is debug mode. We need to refactor debug mode to not load raw files (bug 62605). Instead it should merely keep them deminified. Ideally with support for source maps (bug 45514).",1404778084,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"
+-- 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
+} );",1404777088,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Also:
+
+
+modules['bar'] = {
+  scripts: ['bar.a.js', 'bar.b.js'],
+  globals: {
+    ba: Bar
+  }
+};
+
+mw.loader.implement( 'foo', function ( $, mw, ba ) {
+  --- bar.a.js
+    ...
+
+  --- bar.b.js
+  ...
+} );",1369733723,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","Go to some long article (so long that it won't fit on one screen in your browser), start the visual editor, scroll down, then use up-arrow to walk all the way back up to the top of the article. It's not possible: the first lines of the article remain obscured by the visual editor's menu bar; the only way to make them visible is using the scroll bar or with PageUp.
+
+
+This is Windows 7, Firefox 16.0.2, Chrome 26.0.1410.64 m, Mediawiki 1.22wmf4 (646544a), VisualEditor 0.1.0
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369410540,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-4bokg6oohi7iw7rzhciv,task_description,declined
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","IE9, Firefox 16.0.2, Chrome 26.0.1410.64 not supported anymore.",1680797355,PHID-USER-tuy2dac6pfhknbtqmqgh,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","IE9, Firefox 16.0.2, Chrome 26.0.1410.64 now supported anymore.",1680797345,PHID-USER-tuy2dac6pfhknbtqmqgh,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer",Apparently IE is affected too (see bug 63778).,1404175752,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","Go to some long article, scroll all the way down, click to make the blinking cursor visible. Now press and hold the cursor-up key to go all the way back to the top. Upon release of the cursor-up key, the cursor will be invisibly placed behind the toolbar. Another press/release of the cursor-up key is necessary to make it visible again.",1394913857,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer",I believe that this was fixed some time ago as part of the toolbar fixes - please re-open if not.,1386037710,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","I am now seeing the following behavior on mediawiki.org, using both Firefox and Chrome:
+
+Editing a long article with the VisualEditor, scrolling down, and then pressing and holding CursorUp will scroll back to the top, but not quite: the very first line of the article remains obscured by the toolbar. I have to release and repress CursorUp to see that line.",1373636974,PHID-USER-zzvqlvm6i6kml4tfnqvq,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer",This is now merged and will go out later today.,1373491493,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","Change 73015 merged by jenkins-bot:
+Bind listener to keyup to capture arrows & better math for scrolling.
+
+https://gerrit.wikimedia.org/r/73015",1373491380,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","Change 73015 had a related patch set uploaded by Robmoen:
+Bind listener to keyup to capture arrows & better math for scrolling.
+
+https://gerrit.wikimedia.org/r/73015",1373484943,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","(In reply to comment #0)
+> Go to some long article (so long that it won't fit on one screen in your
+> browser), start the visual editor, scroll down, then use up-arrow to walk all
+> the way back up to the top of the article. It's not possible: the first lines
+> of the article remain obscured by the visual editor's menu bar; the only way
+> to make them visible is using the scroll bar or with PageUp.
+
+I can't reproduce this as written (for wmf6 or wmf7 on Mac or Linux, don't have Windows to test on). We did change the behaviour of the toolbar a little in wmf5, which may explain.
+
+However, it /is/ possible using the cursor keys to put the cursor underneath the toolbar when scrolled down so that the user can't see where it is. Will change this bug to reflect that, but feel free to revert if you can reproduce.",1371167210,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+VisualEditor: Cursor position does not match point of insertion (when inline annotation has padding),"Steps to reproduce bug:
+
+* Edit a page and add the following content: `Hello ""<code>world</code>"".`
+* Place cursor before the first quote, then use the arrow keys to move right (after the quote, before W for world).
+* Insert a character.
+
+Expected:
+
+The place where the character appears, and the position of the blinking cursor should be the same. In actually, this is not the case.
+
+The cursor is blinking **inside** the code annotation (close to the W, within the padded area of the code block).
+
+The added character appeared **outside** the code annotation (close to the quote, outside the padded area of the code block).
+
+Screenshot of problem (from May 2013):
+{F10475}
+
+Video capture (July 2018):
+{F23391729}",1369144560,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4iulhoim62acub7cms4q,task_description,open
+VisualEditor: Cursor position does not match point of insertion (when inline annotation has padding),"Back in 2013, a similar issue exited with links and their labels. Both issues were cause due to a limitation that exists in browsers by default (there is only 1 logical position, and where it happens to be is browser-dependent).
+
+However, the link annotation issue has since been fixed by the introduction of virtual positions within the VisualEditor surface to decide whether the user is inside or outside a node. Perhaps the same could be applied to the code annotation?",1530906618,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4iulhoim62acub7cms4q,task_subcomment,NA
+VisualEditor: Cursor position does not match point of insertion (when inline annotation has padding),"Back in 2013, a similar issue exited with links and their labels. Both issues were cause due to a limitation that exists in browsers by default (there is only 1 logical position, and where it happens to be is browser-dependent).
+
+However, the link annotation issue has since been fixed by the introduction of virtual positions within the VisualEditor surface to decide whether the user is inside or outside a node. Perhaps the same could be applied to other annotations?",1530906360,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-4iulhoim62acub7cms4q,task_subcomment,NA
+VisualEditor: Cursor position does not match point of insertion (when inline annotation has padding),"**orbit** wrote:
+
+Yeah, this is reproducible. No adjustment to margin or padding of the alien (the code element) is able to fix this issue though. We're using native browser selection rendering, and this is a side-effect.
+
+One possible future fix would be to allow the cursor to be placed at the first and last offset of protected nodes (contenteditable would have to be set to true) to give the desired cursor rendering. Any keypress would have to first fixup the selection.
+
+I think this is likely a minor occurrence and making such a dramatic change to protectedNodes is out-of-scope for now.",1369267184,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4iulhoim62acub7cms4q,task_subcomment,NA
+VisualEditor: Check for and warn user on unexpected badtoken event says they're now logged out,"When ever the user does a load, save, diff (, other?) action with the server, we should check for whether the new edit token is an anonymous one when we're expecting the user to be logged in, so we can warn the user that they're now logged out (to prevent them asking for their IP to be over-sighted, etc.).
+
+There's potentially utility in doing this in core (for the wikitext editor) as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369077780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-owjlus7kvzpryeunybdk,task_description,resolved
+VisualEditor: Check for and warn user on unexpected badtoken event says they're now logged out,"This feature has been implemented soon after this task was filed, in July 2013, in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/73446, and still exists today with minor changes.
+
+{F37480899}
+
+(I found this task because we're revisiting the messages for IP Masking: T343848.)",1692047069,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-owjlus7kvzpryeunybdk,task_subcomment,NA
+VisualEditor: Check for and warn user on unexpected badtoken event says they're now logged out,Bug 48657 is the request for the same functionality in core's wikitext editor.,1369078265,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-owjlus7kvzpryeunybdk,task_subcomment,NA
+"VisualEditor: Category sort key setting not done on click out, only on return","In the Category inspector, start setting an over-ride for a category's sort key, but instead of pressing return, click out; no sort key is set. If you change and click ""apply"", it seems like it should apply but doesn't, confusingly.
+
+Thoughts?
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1368745320,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lunpphbvjkp5qsin6ywz,task_description,resolved
+"VisualEditor: Category sort key setting not done on click out, only on return",Now merged.,1370985956,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lunpphbvjkp5qsin6ywz,task_subcomment,NA
+"VisualEditor: Category sort key setting not done on click out, only on return",Related URL: https://gerrit.wikimedia.org/r/67920 (Gerrit Change I256d2b21bc2306959f6d6a0373386054b21dadfe),1370904596,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lunpphbvjkp5qsin6ywz,task_subcomment,NA
+VisualEditor: Auto-selection covers adjacent text over punctuation,"This seems weird to me, but it still might be intentional.
+
+If you put the caret immediately after a sentence ending in a period (e.g. the last sentence of the lede from https://en.wikipedia.org/w/index.php?title=Kono_Statement_of_1993&oldid=546398254&veaction=edit), then click the Link button, it tries to link the last word, including the punctuation.
+
+I would expect it to let you create an new link, without assuming any existing anchor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368583260,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-3tivkrvvx7tiwvalguwy,task_description,resolved
+VisualEditor: Auto-selection covers adjacent text over punctuation,Merged in master; will go out as part of wmf5.,1368978683,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tivkrvvx7tiwvalguwy,task_subcomment,NA
+VisualEditor: Auto-selection covers adjacent text over punctuation,Related URL: https://gerrit.wikimedia.org/r/64481 (Gerrit Change I2408229cddd876ff8fe55a9eddf9bac87a61457e),1368888486,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3tivkrvvx7tiwvalguwy,task_subcomment,NA
+VisualEditor: Auto-selection covers adjacent text over punctuation,"Bug.
+
+Because null (the value we get for the end of the sentence) is silently converted to the string 'null' by RegExp#test (!?) and so we think it's an 'ALetter' which triggers the ALetter-MidNumLet-ALetter rule for mid-word punctuation, and so no break is returned.",1368888212,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-3tivkrvvx7tiwvalguwy,task_subcomment,NA
+VisualEditor: Auto-selection covers adjacent text over punctuation,"This is indeed intentional (and took some time to get right). If the cursor is in, or directly adjacent to, a word, so that you can link a word quickly as a keyboard user without having to use a mouse or do keyboard-based shift-selection.
+
+However, this is meant to not trigger when you're not in the ""context"" of a word, so it does some fancy language-dependent Unicode whitespace detection; it should be doing this for punctuation but apparently isn't, so referring to Ed to investigate.",1368727707,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3tivkrvvx7tiwvalguwy,task_subcomment,NA
+VisualEditor: Image in template gets cut off,"When editing http://de.wikipedia.org/wiki/Wikidata the top of the Wikimedia logo in the template at the bottom of the page is cut off. (It might also be hidden behind the grey bar or something.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368550980,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-qglalluk4kbrg2flbvzv,task_description,resolved
+VisualEditor: Image in template gets cut off,"Not happening for me in Chrome or FF. Assuming this was a browser bug that has since been fixed, but please re-open if it is still happening.",1701795362,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+VisualEditor: Image in template gets cut off,"This happens in any article that uses the following template with an image, which is lots and lots and lots
+https://de.wikipedia.org/wiki/Vorlage:Navigationsleiste
+
+https://de.wikipedia.org/wiki/Bezirk_Altona?veaction=edit
+
+And the German template appears on many other languages as well.
+https://bar.wikipedia.org/wiki/Wikibooks?veaction=edit",1374479589,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+VisualEditor: Image in template gets cut off,"We aim to render templates as similarly as possible, but there are some exceptions at this time. One such exception is that protected elements and their child elements positioned as 'absolute' or 'fixed' will be changed to relative. Protected elements are usually non-text or generated elements like images or templates.
+
+Specifically in this case the CSS rule for elements that match '.ve-ce-alienNode, .ve-ce-alienNode *' is being used to set all elements relative. In a more recent version of the code this rule is now renamed to '.ve-ce-protectedNode, .ve-ce-protectedNode *' but it's effect is the same.
+
+We should probably be only applying relative positioning to elements that are actually positioned 'absolute' or 'fixed', because it's currently being applied to an element that's positioned 'static'.",1368729636,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+VisualEditor: Image in template gets cut off,"Created attachment 12328
+screenshot of the issue in chromium in kubuntu
+
+**Attached**: {F10816}",1368728163,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+VisualEditor: Image in template gets cut off,I cannot reproduce this using either Firefox or Chrome - which browser(s) does this appear in? Do you have a screenshot I could see? Does it still appear?,1368727833,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"It should be possible to edit a part of a MediaWiki page such as a section or paragraph via VisualEditor without loading the entire article into the editor. This would be especially useful on mobile devices. This ticket is designated to serve as the parent task for all work related to such a goal.
+
+The parsing-related work can be seen at [[https://phabricator.wikimedia.org/project/view/3331/|Parsoid: Section-Editing-Support board]].",1368497160,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-wdo3c45xgv7mte4en6az,task_description,open
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Not sure how related these are, but task watchers may be interested in {T209955} and children. (My uneducated observation is that the one doesn't necessarily sort the ""performance"" aspect of this one.)",1605882637,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I am just tyring to get the gnarly dependency graph look a bit more sane .. and AFAIK, this task isn't dependent on read views since you've all embarked on this work in previous years already. If my edit is in error, feel free to add the dependency back.",1595628476,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#6218951, @valerio.bozzolan wrote:
+> Is this task also about supporting `action=edit&section=new` in VisualEditor?
+
+I don't think we have plans to add that, sorry.",1592252834,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,Is this task also about supporting `action=edit&section=new` in VisualEditor? Thank you.,1591964176,PHID-USER-hphk5jxfxfgl64tpfacw,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Thanks. I take your word for it that editing a section on the same page
+will be *faster* than loading the section editor on a fresh screen. The
+design intent is to reduce client load by putting as little of the page as
+practical in edit mode.",1552558162,PHID-USER-axuerq3wmxtfm6tav6bu,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Just as a comment, this task is for ""section editing inline with read mode"", a cooler/faster system than T76541 (which is section editing on its own page). Not sure if that's clear here.",1552409670,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,We need to further explore the approach. ,1537375112,PHID-USER-hqyy4wr7smuc4rzaoio5,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#4559824, @Jdforrester-WMF wrote:
+>>>! In T50429#4559065, @deryckchan wrote:
+>>>>! In T50429#4558267, @kaldari wrote:
+>>> Currently the main blocker (although it may not be a hard blocker) is parsing support for managing state that is page-level (mainly for reference management). @dchan  is [[ https://gerrit.wikimedia.org/r/#/c/VisualEditor/VisualEditor/+/433753/ | exploring doing some of the subtree editing business on the client side ]] as something of a stop-gap solution. The Parsing team's [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ | work on server-side ref management ]] will probably be a better long-term solution (see T146072). They are hoping to have that work wrapped before the end of 2018. Anything to add @ssastry, @dchan, @DLynch, @Esanders?
+>> 
+>> What's the worst that can happen if we let VE load a section of a page, ignoring page-wide state variables? We have made do with section edit page previews, which ignore the effects of other parts of the page on the section you're editing, without too many issues for over a decade.
+> 
+> From a product feature perspective, the citation functionality that people most like about VE wouldn't work (it's entirely page-level content). With the stop-gap work Ryan mentions, it will, mostly, but //e.g.// citations from this section but also used elsewhere won't be editable, which will be very confusing.
+> 
+> From a product reliability perspective, there's the risk of catastrophic page corruption from section-spanning structures (people putting headings in a table, using headings via a template, or using templates that open a div but don't close it, or…), and even if that is somehow(?!) avoided, it'll be at best confusing when some section edit buttons refuse to load.
+
+
+Parsoid currently provides <section> wrappers around HTML and these section wrappers also have editable / uneditable markers on them based on the well-formedness of the wikitect that generated them. So, a section edit scenario, if the section is opened for editing, Parsoid guarantees that the content in there does not contain HTML tags that had an incorrect overlap elsewhere. So, if you open such a section for editing (and just that section), and since VE doesn't introduce bad markup, you are unlikely to cause page corruption.
+
+As for dealing with global state, we have two separate work-in-progress patches
+* https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ frees clients from having to worry about global state, i.e. what happens if you delete a named ref that is used elsewhere. That patch requires clients to mark deleted references with a 'deleted' marker in the data-mw property instead of actually deleting the refences. Parsoid then handles updating state appropriately.
+* https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/441151/ adds support for subtree editing. It effectively takes the desired subtree and computes a ""closure"" of that subtree wrt global state so that the subtree now behaves like a self-contained high-level document. This depends on the previous patch for handling named references.
+
+As part of the patches above, we are adding extension API endpoints to make this support generic, since for example, there is also templatestyles, which has page-level global state when templatestyle uses are deduplicated.
+
+It will take a little while to work through all the details to completion, test, etc. but that is the generic direction we are going towards on the Parsoid end.",1536249606,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Thanks James, that sounds reasonable. I think Ryan's proposal is a fine
+solution - we can allow sections to be edited while freezing references
+that are reused elsewhere on the page, preventing them from being deleted.
+
+If a section cannot be edited, I think users will find it reasonable when
+they see an error like ""This section cannot be edited on its own because it
+depends on [another section of the page / name of transcluded page]. Please
+try editing [the whole page / link to transcluded page] instead.""",1536166546,PHID-USER-axuerq3wmxtfm6tav6bu,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#4559065, @deryckchan wrote:
+>>>! In T50429#4558267, @kaldari wrote:
+>> Currently the main blocker (although it may not be a hard blocker) is parsing support for managing state that is page-level (mainly for reference management). @dchan  is [[ https://gerrit.wikimedia.org/r/#/c/VisualEditor/VisualEditor/+/433753/ | exploring doing some of the subtree editing business on the client side ]] as something of a stop-gap solution. The Parsing team's [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ | work on server-side ref management ]] will probably be a better long-term solution (see T146072). They are hoping to have that work wrapped before the end of 2018. Anything to add @ssastry, @dchan, @DLynch, @Esanders?
+> 
+> What's the worst that can happen if we let VE load a section of a page, ignoring page-wide state variables? We have made do with section edit page previews, which ignore the effects of other parts of the page on the section you're editing, without too many issues for over a decade.
+
+From a product feature perspective, the citation functionality that people most like about VE wouldn't work (it's entirely page-level content). With the stop-gap work Ryan mentions, it will, mostly, but //e.g.// citations from this section but also used elsewhere won't be editable, which will be very confusing.
+
+From a product reliability perspective, there's the risk of catastrophic page corruption from section-spanning structures (people putting headings in a table, using headings via a template, or using templates that open a div but don't close it, or…), and even if that is somehow(?!) avoided, it'll be at best confusing when some section edit buttons refuse to load.",1536161053,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#4558267, @kaldari wrote:
+> Currently the main blocker (although it may not be a hard blocker) is parsing support for managing state that is page-level (mainly for reference management). @dchan  is [[ https://gerrit.wikimedia.org/r/#/c/VisualEditor/VisualEditor/+/433753/ | exploring doing some of the subtree editing business on the client side ]] as something of a stop-gap solution. The Parsing team's [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ | work on server-side ref management ]] will probably be a better long-term solution (see T146072). They are hoping to have that work wrapped before the end of 2018. Anything to add @ssastry, @dchan, @DLynch, @Esanders?
+
+What's the worst that can happen if we let VE load a section of a page, ignoring page-wide state variables? We have made do with section edit page previews, which ignore the effects of other parts of the page on the section you're editing, without too many issues for over a decade.",1536140954,PHID-USER-axuerq3wmxtfm6tav6bu,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Thanks @kaldari! As I understand it the fundamental differences between T76541 and T146072 are:
+
+- With T76541 , the browser has all the document-level data (meta / internal list items, in VE parlance) at its disposal, but at a cost of the whole document being received and parsed (though not rendered, which greatly improves speed and memory usage).
+
+- With T146072 , the browser only has to receive and render a single section that effectively behaves like a small, simple document, but at a cost of not having all the document-level data at its disposal.
+
+It seems there's substantial overlap where either may be adequate to achieve certain functionality, but that the tasks are actually complementary – there are use cases that would need one or the other. For instance, T76541 would be needed to suggest existing citations when adding a new reference, or to keep reference numbering accurate while editing; but you would clearly want T146072 for certain microedit-style approaches that step rapidly between documents.",1536114562,PHID-USER-lliyevigiycjbybglftk,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,Are you aware of the VEForAll extension? https://www.mediawiki.org/wiki/Extension:VEForAll,1536110041,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Currently the main blocker (although it may not be a hard blocker) is parsing support for managing state that is page-level (mainly for reference management). @dchan  is [[ https://gerrit.wikimedia.org/r/#/c/VisualEditor/VisualEditor/+/433753/ | exploring doing some of the subtree editing business on the client side ]] as something of a stop-gap solution. The Parsing team's [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ | work on server-side ref management ]] will probably be a better long-term solution (see T146072). They are hoping to have that work wrapped before the end of 2018. Anything to add @ssastry, @dchan, @DLynch, @Esanders?",1536108865,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#979728, @Jdforrester-WMF wrote:
+> It's entirely do-able for the developers of SemanticMediaWiki to create a VisualEditor integration for each of the fields in a form. Indeed, it's one of the use-cases we built VisualEditor around.
+
+I have been poking around the VE and (recently) Semantic Forms looking for a place where I can dig in.  This may be it.  I can't promise anything, but knowing this is a place that needs work and that some of my users could use it helps.
+
+Knowing other people want it doesn't hurt, either.",1421355867,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"It's entirely do-able for the developers of SemanticMediaWiki to create a VisualEditor integration for each of the fields in a form. Indeed, it's one of the use-cases we built VisualEditor around. However, it'd be a bunch of work and it's nothing we're planning to do at the Wikimedia Foundation (we don't support Semantic MediaWiki either). So effectively this is a ""no"" for your question.
+
+This task is talking about using VisualEditor to edit parts of a single-content-block page, not a page made up via collections of different pieces of information.",1421340191,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I've been using Semantic Forms for more than 4 years now. It used to support the FCKEditor extension (and branch SMW+ supported the WYSIWYG extension).
+But the decision to stop using FCKEditor going forward was at least related to the promise of a cleaner integration with VisualEditor (Yaron Koren would be able to
+comment more accurately on that).  I believe that was decided around 2012.
+
+I'm now with a new company, and I've been tasked with evaluating Atlassian Confluence.  It supports bare pages, but also form-based pages.  The only significant feature it has over
+Semantic Mediawiki / Forms installation is WYSIWYG editing.  I can't stick with MW 1.16 / FCKEditor as I did at my previous company, so it looks like we'll to go with 
+Confluence... which is a shame to me, since I know how versatile the mediawiki environment is.
+
+It doesn't seem like the work-arounds being considered would support being about do do WYSIWYG editing in a text field or the free text area of a Semantic Form.  
+//If that's the case//, it would be nice if this could be marked WONTFIX, and a new issue created that discusses compensating for the lack of an edit section as we
+know it in Mediawiki.
+
+Or, it's 2015, the solution is about to be released any day now, and I'll shut up (I can do that last one anyway).",1421340016,PHID-USER-v7p53gf64fwttu5ylooz,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I've been using Semantic Forms for more than 4 years now. It used to support the FCKEditor extension (and branch SMW+ supported the WYSIWYG extension).
+But the decision to stop using FCKEditor going forward was at least related to the promise of a cleaner integration with VisualEditor (Yaron Koren would be able to
+comment more accurately on that).  I believe that was decided around 2012.
+
+I'm now with a new company, and I've been tasked with evaluating Atlassian Confluence.  It supports bare pages, but also form-based pages.  The only significant feature it has over
+Semantic Mediawiki / Forms installation is WYSIWYG editing.  I can't stick with MW 1.16 / FCKEditor as I did at my previous company, so it looks like we'll to go with 
+Confluence... which is a shame to me, since I know how versatile the mediawiki environment is.
+
+It doesn't seem like the work-arounds being considered would support being about do do WYSIWYG editing in a text field or the free text area of a Semantic Form.  
+''If that's the case'', it would be nice if this could be marked WONTFIX, and a new issue created that discusses compensating for the lack of an edit section as we
+know it in Mediawiki.
+
+Or, it's 2015, the solution is about to be released any day now, and I'll shut up (I can do that last one anyway).",1421339932,PHID-USER-v7p53gf64fwttu5ylooz,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to Tim Starling from comment #49)
+> > * Editing by section blocks users from editing other areas at the same time
+> > that the notice flaws in after they've entered editing, for very limited
+> > added-value.
+> 
+> For large articles, I think the added value would be very large indeed.
+> People don't want to wait tens of seconds to make a small correction, and
+> it's likely that VE performance causes many edits to be abandoned.
+> 
+> Perhaps there are other solutions for the performance issue, but it seems to
+> me that this is a fairly obvious approach, especially for bandwidth
+> reduction.
+
+For what it's worth...
+
+I did a non-scientific poll and asked the Hebrew Wikipedia community what are the people's reasons to avoid VE. Precisely this suggestion came up several times.",1408623631,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"No, it definitely shouldn't be a preference – instead, it should be possible for everyone to ""expand"" the editing area from the one section to the entire article.",1404067177,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Another thought on the preference: currently clicking on a section edit gives a pre-filled edit summary including the section.  Whether this happens should depend on the same preference.  If I have ""section-editing"" set to yes, I would get the pre-filled edit summary and other sections hidden; if I have it set to no, I would get no pre-filled edit summary, and I would see the whole article, as happens now.  This would help avoid the (common) situation where the edit summary is misleading when a section edit is clicked.",1403957632,PHID-USER-ufjbf3qatjamiwoal5fp,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Re comment 52: I agree that show/hide would be nice for the uneditable sections.
+
+More importantly, if this behaviour is implemented, please make it a preference option.  I often use ""edit beta"" on one section in order to fix a problem I see in the section just above it; I'd hate to lose that capability.",1403956163,PHID-USER-ufjbf3qatjamiwoal5fp,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Mike Christie has a suggestion:  Edit the whole page, but only display the chosen section.  
+
+By this I don't think he means ""discard"" everything except the section, but instead just to cover up the other parts.  We're already scrolling to the chosen section, so this would add maybe a gray or white block over everything above that (or perhaps collapse it), and ideally everything below it, too.  
+
+This would help people who are using section editing to keep them focused on their chosen tasks, rather than because of beliefs about performance or edit conflicts.",1403929593,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Comment 46 ignored comment 44, hence making the priority value reflect reality again. If there are further good arguments to give this higher priority, feel free to convince the *developers* to set a higher priority again.",1394027896,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #49)
+> 
+> Yes, the existing feature prevents users from editing other sections on the
+> page, which sucks. That could presumably be addressed in VE: a separate
+> content-editable region could be created by each section edit click, to be
+> saved in bulk.
+
+
+i agree with Tim's comment wholeheartedly, except the last paragraph: preventing the user from editing outside the section doesn't ""suck"". it's a great feature.
+
+when editing a section, we have automatically generated edit summary with the section name. for users that use wikitext editor, you pretty much know, when you see the very common ""/* section name */ optional comment"" edit summary, that the edit is indeed confined to the section whose name appears in the comment.
+
+but with VE, because of the wrong (IMHO) way bug 50872 was handled, a user can press the ""sectionedit"" link of some section, then edit anywhere on the page, and the summary will still show the section name of the click. this makes the summary practically useless: when looking at the history, seeing a section name in the summary tells me nothing - i don't care which button Joe pressed, i care which content was changed, and the summary does not tell me that anymore.[1]
+
+
+since the most urgent issue ATM for VE is unacceptable performance on longer articles with slower machines, true section edit would be (as Tim notes) a very very desirable feature. 
+
+how about this: i think that the cases where a section is not balanced, in terms of html tags (the case described in comment 2) is very rare. how about falling back to full article edit in those rare cases? [2]
+true, it means that those cases would be even slower, but i believe that those are a negligible minority. the vast majority of the sections *are* balanced, and will gain greatly (performance wise) from the ability to edit a single section.
+
+
+peace.
+
+---------------------------------------------
+
+[1] this can be handled by undoing the solution for bug 50872, and solving bug 51903 instead (i.e., create the summary by analyzing the diff instead of the button the user clicked), but the best thing, IMO, would be to support true ""section edit"" for VE.
+
+
+[2] this means: get the section content from the server, and if it ""does not make sense"", like the example in comment #2, get and edit the whole page.",1375911862,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #2)
+> {|
+> ! Foo !! Bar
+> |-
+> === Section 1 ===
+> |-
+> | Foo || bar
+> === Section 2 ===
+> |-
+> | Foo || bar
+> |}
+> 
+> Coming up with a solution to this is would be a significant piece of
+> engineering effort for marginal utility.
+
+The section editing feature in the old parser works by excluding all sections headings where the heading is not a child of the document root. The previous section thus runs on past the excluded heading. This means that a section can always be represented as a set of adjacent DOM subtrees. It seems to me that the same solution could be implemented in VE. 
+
+The definition of ""children of the document root"" would change somewhat, since it is a different kind of DOM, so the number of excluded sections would be larger, but it would still be a better solution than what we have now.
+
+> * The reasons we brought in section-editing originally were two-fold - to
+> skip
+> past confusing wikitext in other areas to find the item you actually wanted
+> to
+> edit (not an issue in the context of VisualEditor), and to avoid edit
+> conflicts
+> using the page-based diffs at the time (not an issue for ~ 7 years since Tim
+> re-wrote the diff tool).
+
+Section editing has never had any special case to help with edit conflicts -- it was always dealt with using the generic three-way merge feature, which, for the record, I did not write.
+
+I think the main two reasons for implementing section editing were bandwidth and avoiding the need to scroll. Erik's original post on the subject suggests as much:
+
+http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/3433
+
+Note that it was implemented at a time when 56k modems were still common -- I had one at the time, and I was certainly glad of the performance improvement.
+
+> * Editing by section blocks users from editing other areas at the same time
+> that the notice flaws in after they've entered editing, for very limited
+> added-value.
+
+For large articles, I think the added value would be very large indeed. People don't want to wait tens of seconds to make a small correction, and it's likely that VE performance causes many edits to be abandoned.
+
+Perhaps there are other solutions for the performance issue, but it seems to me that this is a fairly obvious approach, especially for bandwidth reduction.
+
+Yes, the existing feature prevents users from editing other sections on the page, which sucks. That could presumably be addressed in VE: a separate content-editable region could be created by each section edit click, to be saved in bulk.",1375745889,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"james, we tried your sections within a table example from above here:
+https://en.wikipedia.org/wiki/Wikipedia_talk:VisualEditor/Known_problems#section_in_a_table
+and we could not create something useful.",1375590809,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"note blocks section edit
+
+**Attached**: {F10744}",1375517586,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"upgrading this to ""highest"" as this is the main reason for item 1 (slow loading), item 2 (slow scrolling) and item 6 (no section editing) of https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Known_problems. personally i think this should be _the only_ ""immediate"". why?
+
+i tried it at https://en.wikipedia.org/wiki/Jos%C3%A9_Mourinho.
+* 1 click and 15 secs to edit
+* 1 click to make go a away a note (see attachment)
+* 1 click to edit summary
+* 1 click and 20 secs to review changes
+* 1 click to return to save form
+* 1 click and 40 secs to save
+* 5* pg down to go to the section just edited
+
+section edit with the text editor takes:
+* 1 click and 2 secs to open
+* 1 click and 2 secs to preview
+* 1 pg-down to find the save button
+* 1 click and 10 secs to save",1375516381,PHID-USER-2ccnbnjo2s2q3diidydr,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"This:
+""but I cannot justify spending donor funds to that extent""
+just turned into:
+""we're hoping to be able to undertake it some time towards the start/middle of next calendar year""
+
+Which sure sounds like a priority change, so I'm not sure if my flag change was psychic-magic or precipitative-magic, but either way, it now seems like the correct priority status.  I've tried communicating other ways:
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Section_editing_will_never_be_implemented
+(""Any update from the dev discussion?"") but got no answer, and the known problems page still says ""not planned"".
+
+Anyway, it's good to hear that you are now planning to do this.  I'm sure it will be worth it for low-bandwidth editors.",1375369864,PHID-USER-und42bbibe2hhp4rbyu3,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #43)
+> I'm upgrading this to ""normal"" since it's listed at #4 on
+> https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Known_problems and I'm
+> not
+> seeing any good case for low/lowest made here.
+
+The ""priority"" field doesn't mean ""how much do people want it"", it's ""how soon are the developers likely to get to do it"".
+
+As I explained above, this will require a series of major changes in Parsoid and a huge re-write of MediaWiki's skins system as we switch over to use Parsoid's generated HTML for read pages, and is many (many) months away - we're hoping to be able to undertake it some time towards the start/middle of next calendar year.
+
+Magically changing the status of the priority doesn't make this complex work happen any quicker. There is no value in edit-warring over Bugzilla statuses, so I'm going to leave this as is, but please don't make changes like this.",1375301261,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I'm upgrading this to ""normal"" since it's listed at #4 on https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Known_problems and I'm not seeing any good case for low/lowest made here.",1375243706,PHID-USER-und42bbibe2hhp4rbyu3,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"**joedecker** wrote:
+
+This is quite serious for slow connections.",1372953307,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Ah, the disappearing double-links are Bug 50731.",1372952558,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Ah, I see the ""edit|edit source"" links on sections have turned back into just ""edit"" links, which edit the wikitext. Thank you :-)",1372936067,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I appreciate the VE is a hard problem  - but now you have an interface that *lies* to the user. It claims visual section editing is possible, but the PM for the VE has stated this functionality will not be funded.
+
+So, is the interface lying to the user this bug, or should it be a separate bug?
+
+If lying to the user is considered a feature, what is it for?",1372922447,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Oh, and sorry to be pedantic, but in the original context, ""marginal utility"" was not referring to a specific semi-solution as far as I can see:
+
+>> I don't seem to be able to section edit with VisualEditor.
+> To edit a section, we would need to get its HTML from Parsoid - but a section
+isn't guaranteed to be balanced HTML ...
+> Coming up with a solution to this is would be a significant piece of
+engineering effort for marginal utility.
+
+Thank you for confirming now that you *do* see utility in stopping the waste of bandwidth and slowing of load time.  Even if you think it is too difficult.",1372852730,PHID-USER-und42bbibe2hhp4rbyu3,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"> the core developers of this are not intending to work on this issue any time soon
+That's exactly what befuddles me, and seems like a poor judgement.  If it's anywhere near as big a task as you envisage, then I can't expect a volunteer to take it up.  So I conclude that realistically it will never be done.
+
+> having the entire document available, but just not editable
+Ok, I agree that would be useless, possibly of negative value. You're right that this is not what I'm asking for.
+
+>Parsoid that loaded and edited only one section at a time would be a mammoth piece of work
+Obviously I'm not a mediawiki programmer, so I speak from ignorance here.  But I don't understand why Parsoid can't just be given a shorter piece of wikitext to parse, along with the section number it is starting at.  Since the old editor is quite capable of serving up a correct section of the wikicode to the user, I don't see why the same wikicode can't be given to Parsoid.  Please can you get a third and fourth opinion on the feasibility of this.  Someone in your team may be able to think of a way around the problems you envisage.
+
+> I've edited Wikipedia (and other wikis) since 2001, including over heroically-terrible connexions
+So have you now also tried VisualEditor on those heroically-terrible connections?  I'm willing to bet that you will feel the weight of this problem.
+
+>I cannot justify spending donor funds
+The whole goal of VisualEditor is to improve accessibility and the editing experience for lower-tech editors right?  Well, the sad truth is that low-tech and globally underrepresented editor communities are strongly correlated with low bandwidth access.  Section editing in a long article gives an order of magnitude speed gain to those editors.  If you cannot do this for the target audience, I fear that VisualEditor will not serve those who need it the most.
+
+I really hope you will discuss this with more people before confining it to the dustbin.",1372839855,PHID-USER-und42bbibe2hhp4rbyu3,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"
+> Solving what you're actually asking for (a form of VisualEditor/Parsoid that
+> loaded and edited only one section at a time) would be a mammoth piece of
+> work,
+> albeit with some usefuless as you describe.
+> 
+> > James, please try regular editing on a slow connection if you haven't done
+> > this before, I'm pretty sure you'll end up editing the section source.
+> 
+> I've edited Wikipedia (and other wikis) since 2001, including over
+> heroically-terrible connexions through the years; I am very aware of the
+> impact
+> that our current site has on low-bandwidth users, even without VisualEditor,
+> but I cannot justify spending donor funds to that extent when there are more
+> pressing demands on the resources of the VisualEditor team.
+
+My first thought is what were people thinking when they thought that using a visual editor to edit a whole page at a time would not slow things down a lot for many users? I am not a developer though, and hindsight is 20/20. 
+
+Whatever it costs to make a visual editor that edits a section at at time would be worth it. The WMF spends money on far less important things. I have been saying this for years. 
+
+I think millions of dollars more a year should be spent on developer salaries just for the visual editor, and the coordination of vast armies of volunteer developers to work on the visual editor. Another spending priority would be developer money for cross-wiki watchlists.",1372837803,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #34)
+> I can't believe that section editing is marked as a ""lowest priority""
+> ""enhancement""!
+
+""Enhancement"" means ""the software doesn't do this, and isn't as-written meant to do this""; it's not a judgement on whether it should.
+
+""Lowest priority"" means ""the core developers of this are not intending to work on this issue any time soon""; bugs are always open to other developers coming and working on them, which frequently happens.
+
+""Lowest"" is a very clear way of me marking the bug as something that can be taken up without fear of duplication of work by a developer new to the code. (This is known as avoiding ""cookie licking"".)
+
+> This is incredibly important to me.
+
+I appreciate that it is important to some editors, but I have to balance all requested features, changes and bugs with VisualEditor against one another, and in my judgement this is, relatively, an edge case.
+
+> The way it's currently set up wastes bandwidth and slows load time relative
+> to the old editor. Both of these are important when making a quick-fix edit.
+
+I agree with that; I recommend using the wikitext editor for exactly these use cases by power users if they prefer.
+
+> Hardly ""marginal utility"". 
+
+That specifically refers to finding a solution which you don't want.
+
+A simpler solution - involving having the entire document available, but just not editable except for the section the user asked for - is do-able, but in that case, the benefits you're looking for (low bandwidth, fast loading time, low load on local computers) would not be present; hence, marginal utility.
+
+Solving what you're actually asking for (a form of VisualEditor/Parsoid that loaded and edited only one section at a time) would be a mammoth piece of work, albeit with some usefuless as you describe.
+
+> James, please try regular editing on a slow connection if you haven't done
+> this before, I'm pretty sure you'll end up editing the section source.
+
+I've edited Wikipedia (and other wikis) since 2001, including over heroically-terrible connexions through the years; I am very aware of the impact that our current site has on low-bandwidth users, even without VisualEditor, but I cannot justify spending donor funds to that extent when there are more pressing demands on the resources of the VisualEditor team.
+
+> I'm quite supportive of visual editor in general, but if this is not going
+> to be fixed, I may have to turn back.
+
+I'm sorry that that is the case, and hope that it does not come to that. Sorry if my explanation here is insufficient.",1372812826,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I can't believe that section editing is marked as a ""lowest priority"" ""enhancement""!  This is incredibly important to me.  The way it's currently set up wastes bandwidth and slows load time relative to the old editor.  Both of these are important when making a quick-fix edit.  Hardly ""marginal utility"".  James, please try regular editing on a slow connection if you haven't done this before, I'm pretty sure you'll end up editing the section source.  I'm quite supportive of visual editor in general, but if this is not going to be fixed, I may have to turn back.",1372805196,PHID-USER-und42bbibe2hhp4rbyu3,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,%%%*** Bug 50592 has been marked as a duplicate of this bug. ***%%%,1372793232,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Just a note (for users not following the other bugs) that we have just merged a change along the lines of bug 49666 - there will be both an ""edit"" and an ""edit source"" link on every section, with the edit link taking the user into VisualEditor, scrolled down to that section.
+
+This enhancement request (to have VE appear just for a section within a wider page) is not impossible, and we're keen to explore what impact it has, but very hard, and blocked on Parsoid's HTML being used as the basis for MW's read pages, so may take some time.",1372281418,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,Related URL: https://gerrit.wikimedia.org/r/69984 (Gerrit Change I4b9c47fd65a700a81c880144247fec524edff7e5),1371931754,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #18)
+> I commented at
+> http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/
+> Feedback#Now_unable_to_edit_sections_by_old_method
+> that it would be ideal to have section-edit links for [edit] and [edit
+> source].
+> 
+>  ie.
+> Sandbox [edit]
+>  replaced with:
+> Sandbox [edit] [edit source]
+> 
+> I believe this would prevent a LOT of complaints in the short term, and it
+> would permit a lot of us to continue being active beta testers
+> (section-editing
+> is my most frequent type of edit), that it should be High priority, if at all
+> possible. Thanks.
+
+I have created this as bug 49666.",1371430370,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #25)
+> It would be wonderful if the ""edit source"" links or icons for sections also
+> showed up inside the Visual Editor. The Visual Editor could treat ""edit
+> source"" links or icons as uneditable links. But the link would still work. So
+> people could click ""edit source"" links or icons to open source editing of a
+> section.
+
+I have created this as bug 49665.",1371430207,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #20)
+> I read the discussion, and it seems nobody mentioned what i think is the
+> ""real""
+> bug here: we have the ""edit source"" link, that drops you back to wikitext
+> editor. The correct behavior for ve should obviously be to drop you to a
+> section edit if the hser entered edit state through an edit section link. 
+> 
+> Peace.
+
+I have created this as bug 49664.",1371429995,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Bartosz (comment 26). If I am reading bug 43133 right it sounds way too complicated. What I am suggesting is a simple ""edit source"" link to source mode editing of a section. Nothing fancy like floating windows, etc. tied in any way to the Visual Editor. 
+
+One clicks out of the Visual Editor altogether. This means that edits to the source wikitext in a section are treated the same no matter how one got to that wikitext edit window. This avoids integration conflicts, additional edit conflicts, or anything complicated. 
+
+Same for clicking on stuff Visual Editor can't edit. One is sent to source mode for the section where that stuff is found. Nothing more. 
+
+For transcluded templates one still has to go to the bottom of the source-mode edit window for the whole page. That is where the list of transcluded templates is found. It would be nice if one could see such a list at the bottom of source-mode edit windows for sections too.",1371347020,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Timeshifter, this sounds very much like what is described at bug 43133.",1371343969,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I like kipod's ideas (comment 22). I think to more fully support section editing means to make it easy to choose either editor at any time. 
+
+Let me explain. If the Bartosz patch is implemented (comment 24), or some variation of it, there will be ""edit"" and ""edit source"" links or icons on every section. 
+
+It would be wonderful if the ""edit source"" links or icons for sections also showed up inside the Visual Editor. The Visual Editor could treat ""edit source"" links or icons as uneditable links. But the link would still work. So people could click ""edit source"" links or icons to open source editing of a section. 
+
+People could go to source mode editing at anytime, even from inside the Visual Editor. That would be so convenient and so useful. 
+
+Later on, this functionality could be extended to anything the Visual Editor can't edit. People could click on templates, tables, etc. inside the Visual Editor and go directly to source mode editing of that section. Or they could right-click templates, tables, etc. to go to a new tab in source mode for that section.",1371341581,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I submitted the patch above to show two links side-by-side, in the form of ""[edit] [edit source]"", similarly to how the article tabs are done.",1371319506,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,Related URL: https://gerrit.wikimedia.org/r/68868 (Gerrit Change I13bbb9549c999bb7301bbcf530706a813184425d),1371319421,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #21)
+> (In reply to comment #20)
+> > I read the discussion, and it seems nobody mentioned what i think is the
+> > ""real""
+> > bug here: we have the ""edit source"" link, that drops you back to wikitext
+> > editor. The correct behavior for ve should obviously be to drop you to a
+> > section edit if the hser entered edit state through an edit section link. 
+> > 
+> 
+> It does do so (in its own way). If you click a section-edit link, it
+> currently
+> enters VE edit-mode, and scrolls down to the section you clicked on, and
+> places
+> the cursor at the beginning of the section-header.
+
+
+no it doesn't. what i meant is that if you click on the ""edit"" section link, and then see something that requires wikitext editing and click ""edit source"", you are dropped into ""old"" editor _for the whole page_. this means that there is no way to execute the old ""section edit"" in the wikitext editor. removing this existing functionality is a regression, and fixing it should be easy.
+
+""fixing it"" meas that if you open the editor through a ""section edit"" link and then press ""edit source"", you will be in the exact same state as someone who has VE disabled and pressed the edit section link.
+
+failing to fix this causes editors to disable VE (i know for a fact that i am not the only one who disabled VE because of this very reason).
+
+peace.",1371315010,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #20)
+> I read the discussion, and it seems nobody mentioned what i think is the
+> ""real""
+> bug here: we have the ""edit source"" link, that drops you back to wikitext
+> editor. The correct behavior for ve should obviously be to drop you to a
+> section edit if the hser entered edit state through an edit section link. 
+> 
+
+It does do so (in its own way). If you click a section-edit link, it currently enters VE edit-mode, and scrolls down to the section you clicked on, and places the cursor at the beginning of the section-header.",1371313187,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I read the discussion, and it seems nobody mentioned what i think is the ""real"" bug here: we have the ""edit source"" link, that drops you back to wikitext editor. The correct behavior for ve should obviously be to drop you to a section edit if the hser entered edit state through an edit section link. 
+
+Peace.",1371301719,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #17)
+> (In reply to comment #16)
+> > Matthew. You are incorrect. There has been a recent change. 
+> 
+> You're right that the section editing default has changed for people who
+> opted
+> in to VE.
+> 
+> However, if you've never changed any editing preferences (most registered
+> users), you are still using the old editor by default.  That will change,
+> assuming the random test works well and VE continues to improve.
+
+I think Timeshifter means the ""which will soon be all users"" part, and I agree that it would be very unfortunate. Quiddity's solution seems like the best one, and IMO should be implemented before the A/B test on en.wp.",1371288142,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I commented at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Now_unable_to_edit_sections_by_old_method
+that it would be ideal to have section-edit links for [edit] and [edit source].
+
+ ie.
+Sandbox [edit]
+ replaced with:
+Sandbox [edit] [edit source]
+
+I believe this would prevent a LOT of complaints in the short term, and it would permit a lot of us to continue being active beta testers (section-editing is my most frequent type of edit), that it should be High priority, if at all possible. Thanks.",1371264453,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #16)
+> Matthew. You are incorrect. There has been a recent change. 
+
+You're right that the section editing default has changed for people who opted in to VE.
+
+However, if you've never changed any editing preferences (most registered users), you are still using the old editor by default.  That will change, assuming the random test works well and VE continues to improve.",1371259513,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Matthew. You are incorrect. There has been a recent change. 
+Please read comment 13 by James Forrester above. Here is the relevant part: 
+
+""as of today, we have switched over to the 'beta' behaviour for VisualEditor in a number of regards, including section edit links - i.e., default behaviour for users with VisualEditor (which will soon be all users) is that section edit links will take you into VisualEditor, scrolled to that section, with the cursor at the start of it.""",1371257851,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #14)
+> Many registered editors don't edit enough to know much about preferences. 
+> ...
+
+Editors who haven't changed their preferences are still using the wikitext editor.
+
+> Worst of all, what was once an interesting option has now become an imposed
+> encumbrance. There is no way to edit in source mode now without effort.
+> Registered editors are forced to use VE. They can only opt-out of VE section
+> editing. They must go here: 
+> [[Special:Preferences#mw-prefsection-editing]]
+> 
+> Please return section editing of source wikitext as the default. Make this VE
+> section editing gimmick the option in preferences. Make it opt-in, not
+> opt-out. 
+
+It is opt-in.  So far, the defaults have not changed in any way.  You can sign up for a temporary test account and see for yourself.
+
+If you don't change any preferences, editing remains wikitext only.  And you can change back (and forth) at any time.  That means the defaults are not being imposed on anyone.
+
+I understand your point.  VisualEditor is a work in progress.  However, it's a work in progress that's currently 100% opt-in, and James has already said he will consider two section edit links.",1371256729,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Many registered editors don't edit enough to know much about preferences. This is a bad idea. There are already many complaints here: 
+[[Wikipedia:VisualEditor/Feedback]]
+
+This could cause many editors, who already do not edit much, to edit less because their edits get reverted soon after using Visual Editor. VE messes up many things. I have seen it myself, and so I do not use VE. I have to check a WHOLE-PAGE preview diff for errors it inserts before I save some other minor thing I edited. Minor typos and other things that used to take me a few seconds to fix now take a long time with the Visual Editor. 
+
+Visual Editor needs to edit SECTIONS, too. Not the whole page. So this fix is not a fix. Visual Editor still does not support section editing. It still only edits the whole page. 
+
+Worst of all, what was once an interesting option has now become an imposed encumbrance. There is no way to edit in source mode now without effort. Registered editors are forced to use VE. They can only opt-out of VE section editing. They must go here: 
+[[Special:Preferences#mw-prefsection-editing]]
+
+Please return section editing of source wikitext as the default. Make this VE section editing gimmick the option in preferences. Make it opt-in, not opt-out. 
+
+The WMF does not have anywhere near a consensus or approval or any other type of community process sanction that justifies imposing beta VE. Especially when it is as buggy and beta as it is now. VE was actually an interesting option until this latest forced imposition of beta VE.",1371255945,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #12)
+> OK. Now that I finally get it, and see that everyone (logged in or not)
+> currently gets source editing of sections, let us not remove section editing
+> of source wikitext when VisualEditor is fully implemented! That would make many
+> editors very unhappy.
+
+Just to update on this point: as of today, we have switched over to the 'beta' behaviour for VisualEditor in a number of regards, including section edit links - i.e., default behaviour for users with VisualEditor (which will soon be all users) is that section edit links will take you into VisualEditor, scrolled to that section, with the cursor at the start of it.
+
+For the mean time (until VisualEditor is out of beta, when it will be much less likely that users will want to use wikitext editor often), there's a user preference (defaulted to off) that will redirect these section edit links back to the wikitext editor; this is in Special:Preferences > Editing > Beta features.
+
+I'm open to seeing if there's a way of giving people two section edit links without being confusing in the medium/long term, but that's a discussion for later. :-)",1371180404,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"OK. Now that I finally get it, and see that everyone (logged in or not) currently gets source editing of sections, let us not remove section editing of source wikitext when VisualEditor is fully implemented! That would make many editors  very unhappy. 
+
+I sometimes like to open up a section in a new tab for editing. So I can switch between tabs to alternate between how the section currently looks, and how my preview looks. This also helps me in finding stuff in the wikitext. I can use browser find in both tabs to help me find where I need to edit. 
+
+This can be very necessary when editing references, tables, navigation boxes, image captions, and other such wikitext. Images that are right-floating, for example, can be difficult to find in the wikitext otherwise.",1371076044,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #10)
+> OK. I see that section editing is currently enabled for anonymous users too
+> on Wikipedia. I am almost always logged in, and so I must have been confused by
+> the preference ""Enable section editing via [edit] links"".
+
+That is in fact the preference, but it's checked by default (as well as always on for anons).",1371073574,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"OK. I see that section editing is currently enabled for anonymous users too on Wikipedia. I am almost always logged in, and so I must have been confused by the preference ""Enable section editing via [edit] links"". I see now that it is about the URLs. See 
+[[Help:Section#Section_editing]].
+
+I would hate to lose section editing of source wikitext if VisualEditor is enabled for section editing. That would be a serious step backwards for the reasons I and others have discussed.",1371073277,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #8)A section
+> preview is much faster. I have been editing Wikipedia since 2005, and at one
+> point I had forgotten that section editing is not a given for all editors. We
+> are wasting a lot of editors time by not enabling it by default.
+
+Wikitext section editing is enabled by default.",1371073015,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"See discussion here:
+[[Wikipedia:VisualEditor/Feedback]] and go to the section titled ""VisualEditor not enabled for section editing"". That talk section will end up in the archives eventually. Do an archive search then. 
+
+Load time will still be an important factor with VisualEditor. That reason alone justifies continuing with section editing. 
+
+If VisualEditor is enabled for section editing, then it will also be necessary to enable ""edit source"" somehow for sections too. So people can choose between the two. Just like at the top of page. If the developers are worried about cluttering up each section with both ""edit"" and ""edit source"" links, then there needs to be some icon next to ""edit"" that will be the link for ""edit source"". The clickable icon will have a popup tooltip saying ""edit source"".
+
+I use section editing for almost all my editing, whether in short or long articles. Do you have section editing enabled? If not, you might try it. It speeds up editing immensely for me, and many others. See: 
+[[Special:Preferences#mw-prefsection-editing]] and ""Enable section editing via [edit] links"". It would be better if it were enabled by default for all editors, whether logged in, or not. 
+
+Many people will still use wikitext source editing. There will long be a need until every single bug is fixed in VisualEditor. I can tell you this from years of experience with the Wikia visual editor. Many, if not most, regular editors on Wikia avoid it due to its continuing bugginess. 
+
+When using source editing I don't know why anybody would want to wade through paragraphs of irrelevant stuff to get to the paragraph and section one is interested in editing. Especially if you make multiple edits, and use multiple previews. Why wait long periods of time for full-page previews? A section preview is much faster. I have been editing Wikipedia since 2005, and at one point I had forgotten that section editing is not a given for all editors. We are wasting a lot of editors time by not enabling it by default. Since there are fewer and fewer editors we need to make their editing more and more efficient.
+
+Anonymous editors do much of the editing on Wikipedia, and many will prefer to edit the source wikitext for all the reasons previously discussed. Many anonymous editors are experienced Wikipedia editors, and will not tolerate having to only use VisualEditor. So never get rid of the option for source editing. Let me repeat: WIKIA, WIKIA, WIKIA. Bugs are seemingly never-ending and ever-growing with visual editors.",1371065466,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #6)
+> One of the things I'm pondering is if we should relabel the edit section
+> links to have two links, one to VE and the other to wikitext. Possibly ""[_edit_
+> _*_]"" or somesuch.
+
+I think that might be too much clutter when VE rolls out to everyone.  But while it's opt-in, it will definitely encourage me to test it, since I use the edit section link a lot.",1369114201,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #5)
+> Err, whoops. Sorry, yeah, completely missed that paragraph.
+
+:-)
+
+> If the default editor behavior is a switch that controls parts of the
+> interface like this (I didn't realize that), is this testable now anywhere?
+> A Labs wiki or something?
+
+No; we should do that.
+
+One of the things I'm pondering is if we should relabel the edit section links to have two links, one to VE and the other to wikitext. Possibly ""[_edit_ _*_]"" or somesuch.",1368980861,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #4)
+> I mentioned it too, you know :-) - see:
+> 
+> (In reply to comment #2)
+> | The behaviour in VisualEditor when running as the default editor is for the
+> | edit section links to take you into VE for the entire page, with the view
+> | moved down to the anchor of that section (note, this is not how it appears
+> | right now on the various Wikipedias, but will be once they have the 'beta'
+> | enabled).
+
+Err, whoops. Sorry, yeah, completely missed that paragraph.
+
+If the default editor behavior is a switch that controls parts of the interface like this (I didn't realize that), is this testable now anywhere? A Labs wiki or something?",1368848488,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #3)
+> Krinkle briefly mentioned an idea where section edit links might load the
+> full VisualEditor form and then jump down to the specific section. This might
+> be an approach to consider.
+
+I mentioned it too, you know :-) - see:
+
+(In reply to comment #2)
+| The behaviour in VisualEditor when running as the default editor is for the
+| edit section links to take you into VE for the entire page, with the view
+| moved down to the anchor of that section (note, this is not how it appears
+| right now on the various Wikipedias, but will be once they have the 'beta'
+| enabled).",1368825534,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"There must be a recognition that editing large articles is burdensome and that section editing has (had) _enormous_ value.
+
+Even with JavaScript disabled, the parser continues to take a significant amount of time to parse a large article. And while modern browsers on modern hardware don't have as many issues, rendering large articles can also be taxing.
+
+VisualEditor adds to this burden by piling on a lot of JavaScript. The idea that wanting to edit only a section of [[GE]] or [[Iraq War]] stems from wanting to skip past confusing wikitext or avoid edit conflicts misses the point, I think. Though I realize that VisualEditor uproots many principles of the current editing workflow/paradigm.
+
+Krinkle briefly mentioned an idea where section edit links might load the full VisualEditor form and then jump down to the specific section. This might be an approach to consider.",1368825331,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #0)
+> I don't seem to be able to section edit with VisualEditor.
+
+There are three issues here:
+* To edit a section, we would need to get its HTML from Parsoid - but a section isn't guaranteed to be balanced HTML, for example (commonly-used):
+
+{|
+! Foo !! Bar
+|-
+=== Section 1 ===
+|-
+| Foo || bar
+=== Section 2 ===
+|-
+| Foo || bar
+|}
+
+Coming up with a solution to this is would be a significant piece of engineering effort for marginal utility.
+
+* The reasons we brought in section-editing originally were two-fold - to skip past confusing wikitext in other areas to find the item you actually wanted to edit (not an issue in the context of VisualEditor), and to avoid edit conflicts using the page-based diffs at the time (not an issue for ~ 7 years since Tim re-wrote the diff tool).
+
+* Editing by section blocks users from editing other areas at the same time that the notice flaws in after they've entered editing, for very limited added-value.
+
+
+The behaviour in VisualEditor when running as the default editor is for the edit section links to take you into VE for the entire page, with the view moved down to the anchor of that section (note, this is not how it appears right now on the various Wikipedias, but will be once they have the 'beta' enabled).
+
+I'm not convinced that this is a WONTFIX, but I'm similarly not convinced that we should spend our time fixing this rather than, say, making VisualEditor and Parsoid work on Wikisource, or other things we could be doing with our limited resources.",1368814282,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Thoughts:
+
+It strikes me that this might not be overly difficult - if VE is just using H<n> elements to represent sections anyway, then it should be relatively simple to change the edit URL to ""javascript:"", and add some JavaScript events to them that call the VE setup and, once it's done, brings the specified section to the top of the user's screen.
+
+I won't mark this as easy, because I don't think it is. I wish we had an ""intermediate"" keyword.",1368812060,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on","How to reproduce:
+
+1. Enable the ""Mark all edits minor by default"" option in the preferences.
+2. Edit a page in the VisualEditor.
+3. Press ""Review and save"", then ""Looks good to me"".
+4. The edit summary entering bubble appears.
+
+Observed:
+
+* The ""This is a minor edit"" box is not checked.
+
+Expected:
+
+* The ""This is a minor edit"" box is checked.
+
+Comment: The saved revision IS correctly marked as minor. It's just the check box that appears incorrectly.
+
+GWT scenario for Cucumber:
+Given that I am editing an article while the minordefault preference is on
+When I am saving the article
+Then the ""This is a minor edit"" box is checked
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368250560,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-lxnhaohtjgjw5zamlish,task_description,resolved
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on",Merged into master; will go out with wmf5.,1368638598,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lxnhaohtjgjw5zamlish,task_subcomment,NA
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on",Related URL: https://gerrit.wikimedia.org/r/63844 (Gerrit Change Ib5cdcb9433be5ff7b9179d3833f42e5c3453285a),1368621284,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lxnhaohtjgjw5zamlish,task_subcomment,NA
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on","(In reply to comment #1)
+> You know, if minoredit preference was killed, this wouldn't be an issue...
+
+I couldn't agree more :)",1368250904,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-lxnhaohtjgjw5zamlish,task_subcomment,NA
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on","You know, if minoredit preference was killed, this wouldn't be an issue...",1368250852,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-lxnhaohtjgjw5zamlish,task_subcomment,NA
+Allow extensions to automatically generate jsduck documentation on doc.wikimedia.org,"Core now has jsduck documentation on https://doc.wikimedia.org/mediawiki-core/master/js/ .  It would be useful to provide a standardized mechanism for extensions to have their jsduck documentation automatically added under doc.wikimedia.org as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48244",1368220260,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-cci6rbbarnfeumyquutn,task_description,resolved
+Allow extensions to automatically generate jsduck documentation on doc.wikimedia.org,"Marking this fixed.  The general functionality is there.  For GuidedTour specifically, https://gerrit.wikimedia.org/r/#/c/118428/ and https://gerrit.wikimedia.org/r/#/c/118426/ are in progress.",1394685438,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-cci6rbbarnfeumyquutn,task_subcomment,NA
+Allow extensions to automatically generate jsduck documentation on doc.wikimedia.org,"It looks like VisualEditor and MultimediaViewer are both doing so now.  i don't know if they're one-offs or there's a general process.
+
+However, I would like to do the same for GuidedTour.  Currently, we have it at http://growthdoc.wmflabs.org/GuidedTour/ .",1393639541,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-cci6rbbarnfeumyquutn,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,"Wikitext edit has page title ""Editing Foobar"", as opposed to reading-mode's ""Foobar"". For people with a number of tabs open, it'd be great for them to get a handle on where they are by updating the window title to prepend ""Editing "" to it (and remove it on save).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1368044160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jhka5utrurrafo6ytxhv,task_description,resolved
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,"Yes, re-using 'editing' & 'creating' messages.
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > And 'Creating'.
+> 
+> Ah, yes. Presumably they're existing MW messages to steal, avoiding
+> duplication
+> of i18n efforts?.",1368885209,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,Merged; will go out with wmf5.,1368885131,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,Related URL: https://gerrit.wikimedia.org/r/64325 (Gerrit Change I9dcc8ec2c37a7ff9cff6cedb7bdb1fed1bdc4deb),1368807251,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,"(In reply to comment #1)
+> And 'Creating'.
+
+Ah, yes. Presumably they're existing MW messages to steal, avoiding duplication of i18n efforts?.",1368804528,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,And 'Creating'.,1368804345,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"It would be helpful to have a built-in method in Scribunto/Lua that allows retrieving a list of the categories used on a page.
+
+For example, <https://en.wikipedia.org/wiki/Einar_Schleef> would return a list that includes:
+
+* German dramatists and playwrights
+* 1944 births
+* 2001 deaths
+
+As these categories are included on this page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**: {T20596}",1367867880,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_description,resolved
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@SD0001 Thank you! One more hesitant suggestion: I was looking for something to link the term ""edit notices"" to, and found the page https://www.mediawiki.org/wiki/Manual:Interface/Edit_notice - I wonder if it would be worth adding an example there for this new capability? (~~Or perhaps the Scribunto requirement makes this unfeasible?~~ EDIT: (I'm probably wrong here, I see it's default with 1.34+))",1723770787,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@SD0001 Thank you! One more hesitant suggestion: I was looking for something to link the term ""edit notices"" to, and found the page https://www.mediawiki.org/wiki/Manual:Interface/Edit_notice - I wonder if it would be worth adding an example there for this new capability? (Or perhaps the Scribunto requirement makes this unfeasible?)",1723768444,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@Quiddity I have documented the new property in the [[https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Title_objects|Lua reference manual]]. Suggested blurb for tech news:
+
+> Page categories are now accessible in Lua modules via `categories` property of [[https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Title_objects|mw.title objects]]. This enables use cases like category-specific editnotices.",1723746686,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@SD0001 Hi, I'm wondering if you're able to help answer any of the requests in my comment above? (Or anyone familiar, who sees this!) But I also guess you may still be traveling/recovering/catching-up from Wikimania, so no rush if it needs to wait a week or two! Thanks.",1723675356,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Hi, this sounds great, and thank you Pppery for adding the user-notice tag. Two requests, and a note:
+1. Please could someone **suggest some wording for a Tech News entry**? -- I've read the comments above, and the linked gerrit patch, but I'm still uncertain how to clearly describe the new function(s?) that will be available to editors. 
+  * Here's a rough-guess attempt (and structure example): 
+  * ""Editors can now use Lua code to get a listing of categories used in a page. This enables [example use-case?]. The [link]documentation has details and examples[/link] of how this new function can be used.
+2. Please could someone write (or link us to any existing) **permanent documentation for the new function(s)**? -- I.e. It seems like it would be good to have a page-section on MediaWiki-wiki for any details and examples. That will also make it possible to have a shorter Tech News entry that simply links to those details/examples!
+* Note: I see the gerrit commit-msg says ""//This enables category-specific editnotices (T85372) and other use-cases.//"" -- Maybe that task needs an update (of some sort)? Or to be highlighted in the docs/TN entry if it's already available due to this task's resolution?
+Thanks!",1723058925,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Change #919459 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Scribunto@master] Expose page categories to Lua%%%
+https://gerrit.wikimedia.org/r/919459",1723049408,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I struggled to get proxying to work on the second test wiki I created, but I was able to still test the specific use case of category editnotices on the first test wiki and that functions correctly. We probably need more use cases tested before the change can be implemented.",1714666635,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I struggled to get proxying to work on the second test wiki I created, but I was able to still test the specific use case of category editnotices and that functions correctly. We probably need more use cases tested before the change can be implemented.",1714666610,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by Awesome Aasim using patch(es) linked to this task:
+[[ https://patchdemo.wmflabs.org/wikis/29fac70752/w ]]",1714661371,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,Okay I will just initialize a new wiki with proxying from EN Wikipedia.,1714661181,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9746242, @Awesome_Aasim wrote:
+> One can you enable proxying articles from en.wiki?
+
+No, I don’t think it’s possible to enable proxying after creating the patch demo. If important, you can create a new patch demo with proxying enabled; otherwise, just copy the necessary pages with an edit summary linking to the enwiki page.
+
+> And second, can you give the test account admin and interface-admin so I can test a specific use case (category based editnotices) with the Lua categories?
+
+You can log in with the user name `Patch Demo` and the password `patchdemo1` and give yourself admin rights (or just use that account directly). This is a standard account that works on any Patch Demo wiki.",1714139068,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@Novem_Linguae I created a test account called ""Test"" on the test wiki you created on patch demo. I want to know if you can do a couple of things: One can you enable proxying articles from en.wiki? And second, can you give the test account admin and interface-admin so I can test a specific use case (category based editnotices) with the Lua categories?",1714074781,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"There is very much an error with this. Page is not in A so gets put in A, but now that the page is in A the parser function says that we are now in A and does not category link. This is a less obvious self reference loop. The page should detect that it is getting categorization information about itself, do a parse, and after recursing one down say ""template loop detected: A"" and throw the page into ""pages with template loops"". Something similar to what happens when you construct an actual template loop like this:{F47620082}",1713574509,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9730478, @Awesome_Aasim wrote:
+> https://patchdemo.wmflabs.org/wikis/878c4bb105/wiki/A says that the page is in A, even though it clearly is not from the category bar. This might be the ""unstable parses"" that matmarex was alluding to.
+
+I don't see an issue. By the logic you have, page should be categorised to Category:A if it wasn't already in it. Once this is done, the page is //now// in Category:A and is indicated as such. 
+
+I think we have established already that there are no ""unstable parses"". Purging the page any number of times doesn't change its categorisation. ",1713559024,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Thank you. I just tested out the categories and specifically the undefined behavior which would result in a template loop for any other parser function.
+
+https://patchdemo.wmflabs.org/wikis/878c4bb105/wiki/A says that the page is in A, even though it clearly is not from the category bar. This might be the ""unstable parses"" that matmarex was alluding to.
+
+Can we maybe find a way to detect these template loops and throw an error in the Lua code if one occurs?",1713550469,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,@Awesome_Aasim You can do so: https://toolhub.wikimedia.org/tools/patchdemo,1712727381,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by Novem Linguae using patch(es) linked to this task:
+[[ https://patchdemo.wmflabs.org/wikis/878c4bb105/w ]]",1712709797,PHID-USER-jab5bp3ivtzmobfdxoa7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,Might we be able to get this on a test wiki so we can ensure that there aren't any problems with the patch?,1712694065,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9595853, @SD0001 wrote:
+> The proposed patch reads the categories from the db, sidesteping any ""cross-communication"" concerns. The tradeoff is that the categories reflect the ones produced by the last parsed version of the page, so if someone adds some categories and invokes this function on the current page in the same edit, the page is temporarily saved with lua returning outdated result, which gets fixed on the next purge or edit[0]. 
+
+I view this as a feature, not a bug -- it breaks a possible cycle and avoids doing a full parse of the page just to extract categories.",1711390959,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,I am also going to backtrack from what I was saying about the template loop issue. Instead of forbidding categorization... why not just add the page to the Category:Pages with template loops category?,1710298174,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@SD0001 IMHO I think any effort to expose categories to Lua is better than nothing at all.
+
+A more robust editnotice load module I worked on testwiki https://test.wikipedia.org/wiki/Module:Editnotice_load uses some hackery to get the categories from the (preprocessed) wikitext, it takes forever to load on large pages, like on this fork of Taylor Swift from enwiki: https://test.wikipedia.org/w/index.php?title=Taylor_Swift&action=edit
+
+I don't think the result is even cached when used in interface messages, is it...",1710298027,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"The proposed patch reads the categories from the db, sidesteping any ""cross-communication"" concerns. The tradeoff is that the categories reflect the ones produced by the last parsed version of the page, so if someone adds some categories and invokes this function on the current page in the same edit, the page is temporarily saved with lua returning outdated result, which gets fixed on the next purge or edit[0]. 
+
+However, per @aaron on gerrit:
+> It's strange for this to use the categories of the previous parsed revision. It's also not well defined to use the currently-being-parsed revision either.
+>
+> It's one thing to depend on page existence, current revision text, or current revision metadata, but depending on the parsed current revision of another page (let alone the same page) to generate the parsed output feels overly ""higher-order"".
+
+This is something which does seem unprecedented in MediaWiki, although I'm not certain if it's a bad thing. As it stands, there are a lot of Scribunto feature requests where the only straightforward implementation is to use db data generated by the last parsed revision. 
+
+| **Feature** | **Ticket** | **Workaround** |
+| Reading categories (this ticket) | T50175 | [[https://en.wikipedia.org/wiki/Module:Mainspace_editnotice|Module:Mainspace_editnotice]], function blp_notice |
+| Reading local short description | T216356 | [[https://en.wikipedia.org/wiki/Module:GetShortDescription|Module:GetShortDescription]] |
+| Checking if page is a disambiguation page | T71441 | [[https://en.wikipedia.org/wiki/Module:Disambiguation|Module:Disambiguation]] |
+ 
+Current workarounds generally try processing the raw getContent(), which is worse.
+
+----
+[0]: Even this minor annoyance is not unfixable. I earlier tried fixing it by using VARY_REVISION output flag. This doesn't quite work as it causes a re-purge before the link tables are updated. Instead, we could use a custom parser output flag which triggers the LinksUpdateComplete hook to re-purge once the link table is up to date.
+",1709558536,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I like the idea of forbidding Scribunto output from adding new categories once categories have been read, but the implementation of that could be fraught.  Parsoid will parse the scribunto code as a separate ""top level document"" so in theory we could zero-out ParserOutput::$mCategories() after the Scribunto code has returned. This still works even if the categories were placed in ParserOutput by parsing `[[Category:Foo]]` as wikitext.  Seems like a pretty big hammer, though, for a problem we'd hope wouldn't arise in practice.
+",1702407148,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9164846, @Awesome_Aasim wrote:
+> Here is a solution: only fill getCategories() for the page all the way up to the point of execution.
+
+The problem is that the page may not be parsed in the same order each time, so this “all the way up to the point of execution” may change from parse to parse, without any edits.
+
+> then we can also get that in the following scenario. Suppose we have the page ""Foo"" check to see if ""Foobar"" is in the page ""Bar"" and if so does nothing, and if not writes ""Foobar"". Now say ""Bar"" does the same for ""Foo"". Now the order of execution determines which page has ""Foobar"" and which one does not.
+
+Actually, not:
+* `mw.title:getContent()` returns the raw wikitext, without any parsing. This either contains or doesn’t contain `Foobar`; this fact can be changed only through an edit.
+* `frame:expandTemplate()` uses the parser to get the preprocessed content, and the parser errors out, adding the page to [[https://en.wikipedia.org/wiki/Category:Pages_with_template_loops|Category:Pages with template loops]], when it notices this kind of recursion.",1697358959,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9164846, @Awesome_Aasim wrote:
+> There might actually be a better solution than this. If a module accesses category information, just prohibit population of categories by that module period. That is, if the module is like the first two scenarios, it would just do nothing and maybe add the module to a special page. This is something that can be checked after the module is done executing. For now, this might be a good solution until some way to detect these two scenarios is reliably determined. It would allow for category editnotices to work while preventing the two scenarios above from arising.
+
+Categories are added by literal category links in the wikitext emitted by a module, unfortunately. Disabling categories might be fairly easy to do for any invoked module function that generates a complete category link that goes straight into the wikitext of the article, because it could be as easy as a search and replace in the parser code that receives the output of the module function, but a module can be used to generate only part of a category link, like `[[Category:{{#invoke:example|emit_category_that_page_is_not_in}}]]`. But there are often be multiple layers of expansion past the module invocation, for instance when a template contains `{{#invoke:module name|function name|...}}`. Text generated by a module invocation could also be put into a template that then puts the text in a category link.
+
+I'm not familiar with the parsing infrastructure, but I imagine to solve some of these problems, the parser would have to track which 'contaminated"" text ultimately had something to do with invocations of modules that looked up category information for the current page, and in the final expanded text disable any category links that contain any of this contaminated text. That could be quite an invasive change to the parser because of all the levels of expansion that wikitext goes through. There would also be false positives, because a template or module can take in contaminated text but totally ignore it and just generate the same thing whether the contaminated text is there or not. This change could lead to annoying results: suppose a module that is widely used suddenly starts looking up categories when it doesn't need to; then any templates or modules that depend on the module would stop generating category links even though they didn't do anything wrong with the category information. Then editors would have to look through the dependency tree and figure out which module was the culprit for the suddenly disappearing category links.",1694639124,PHID-USER-ckzurwd36svqc4arsqvb,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9164846, @Awesome_Aasim wrote:
+> There might actually be a better solution than this. If a module accesses category information, just prohibit population of categories by that module period. That is, if the module is like the first two scenarios, it would just do nothing and maybe add the module to a special page. This is something that can be checked after the module is done executing. For now, this might be a good solution until some way to detect these two scenarios is reliably determined. It would allow for category editnotices to work while preventing the two scenarios above from arising.
+
+Categories are added by literal category links in the wikitext emitted by a module, unfortunately. Disabling categories might be fairly easy to do for any invoked module function that generates a complete category link that goes straight into the wikitext of the article, because it could be as easy as a search and replace, but a module can be used to generate only part of a category link, like `[[Category:{{#invoke:example|emit_category_that_page_is_not_in}}]]`. But there are often be multiple layers of expansion past the module invocation, for instance when a template contains `{{#invoke:module name|function name|...}}`. Text generated by a module invocation could also be put into a template that then puts the text in a category link.
+
+I'm not familiar with the parsing infrastructure, but I imagine to solve some of these problems, the parser would have to track which 'contaminated"" text ultimately had something to do with invocations of modules that looked up category information for the current page, and in the final expanded text disable any category links that contain any of this contaminated text. That could be quite an invasive change to the parser because of all the levels of expansion that wikitext goes through. There would also be false positives, because a template or module can take in contaminated text but totally ignore it and just generate the same thing whether the contaminated text is there or not. This change could lead to annoying results: suppose a module that is widely used suddenly starts looking up categories when it doesn't need to; then any templates or modules that depend on the module would stop generating category links even though they didn't do anything wrong with the category information. Then editors would have to look through the dependency tree and figure out which module was the culprit for the suddenly disappearing category links.",1694639064,PHID-USER-ckzurwd36svqc4arsqvb,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9164846, @Awesome_Aasim wrote:
+> There might actually be a better solution than this. If a module accesses category information, just prohibit population of categories by that module period. That is, if the module is like the first two scenarios, it would just do nothing and maybe add the module to a special page. This is something that can be checked after the module is done executing. For now, this might be a good solution until some way to detect these two scenarios is reliably determined. It would allow for category editnotices to work while preventing the two scenarios above from arising.
+
+Categories are added by literal category links in the wikitext emitted by a module, unfortunately. Disabling categories might be fairly easy to do for any invoked module function that generates a complete category link that goes straight into the wikitext of the article, because it could be as easy as a search and replace, but a module can be used to generate only part of a category link, like `[[Category:{{#invoke:example|emit_category_that_page_is_not_in}}]]`. But there are often be multiple layers of expansion past the module invocation, for instance when a template contains `{{#invoke:module name|function name|...}}`. Text generated by a module invocation could also be put into a template that then puts the text in a category link.
+
+I'm not familiar with the parsing infrastructure, but I imagine to solve some of these problems, the parser would have to track which 'contaminated"" text ultimately had something to do with invocations of modules that looked up category information for the current page, and in the final expanded text disable any category links that contain any of this contaminated text. That could be quite an invasive change to the parser because of all the levels of expansion that wikitext goes through. There would also be false positives, because a template or module can take in contaminated text but totally ignore it and just generate the same thing whether the contaminated text is there or not. That could be a bit obnoxious if a module that is widely used suddenly starts looking up categories when it doesn't need to, any templates or modules that depend on the module could stop generating category links even though they didn't do anything wrong with the category information.",1694638874,PHID-USER-ckzurwd36svqc4arsqvb,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I kind of see the issue as well a little that Matmarex has put forth. It is the classical paradox of self reference. If the page populates Category:Foo when it is not in Category:Bar, and the page populates Category:Bar when it is in Category:Foo, then which category would be populated? It would require us to know the final execution state in order to further populate. Here is a solution: only fill getCategories() for the page all the way up to the point of execution.
+
+But then for two pages, we have the problem of timing. The order in which categories are populated would then depend on when the page was parsed. I can see how it can lead to ""unstable parses"" regarding categories, but then we can also get that in the following scenario. Suppose we have the page ""Foo"" check to see if ""Foobar"" is in the page ""Bar"" and if so does nothing, and if not writes ""Foobar"". Now say ""Bar"" does the same for ""Foo"". Now the order of execution determines which page has ""Foobar"" and which one does not.
+
+There might actually be a better solution than this. If a module accesses category information, just prohibit population of categories by that module period. That is, if the module is like the first two scenarios, it would just do nothing and maybe add the module to a special page. This is something that can be checked after the module is done executing. For now, this might be a good solution until some way to detect these two scenarios is reliably determined. It would allow for category editnotices to work while preventing the two scenarios above from arising.",1694632731,PHID-USER-bzspc5im4mzxblgdl3e7,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Although @Izno only mentions “cross-communication between templates”, I’m pretty sure he meant specifically templates transcluded on a page accessing output of templates transcluded at other parts of the same page – otherwise, it’s just a simple template transclusion, which was, is, and going to be, supported, of course. Templates transcluded on a page accessing output of templates transcluded at other parts of the same page is where issues come up: previews of parts of the page (e.g. sections or – in case of VisualEditor and other Parsoid-based things – individual templates) may be different from what a full-page parse produces, and parallel parsing of different parts of the page may cause race conditions.",1684739405,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Yes, I tested it. It works in editnotices; it did cause a template loop on the page itself yeah. But the main complaint from Izno seems to be about cross-template communication, not about accessing info about the current page; and this definitely works if the page given is not the current page.",1684731135,PHID-USER-3ffkgjb7rllliblvxdy2,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Did you test these? Unless you have countermeasures (is it possible at all?), or unless `{{FULLPAGENAME}}` isn’t actually the title of the current page (which is the case e.g. in edit notices), both `frame:expandTemplate` and `{{:{{FULLPAGENAME}}}}` would definitely cause infinite template recursion, not only potentially cause unstable parses.",1684656255,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#8865219, @Izno wrote:
+> `getContent` does not expand templates. I'm pretty sure the PHP implementation of `getCategories`
+
+`frame:expandTemplate` allows this though. In fact, just using e.g. `{{#invoke:string|find|{{:{{FULLPAGENAME}}}}|Category:X1}}`, you can check if the categories of the current (or any) page include X1 without even using Lua to get the page content. So this actually adds zero additional functionality (it just makes things faster, since transcluding the page is very slow to parse) and I don't think it actually needs any restrictions. The infinite loops mentioned should already be possible through this method.",1684626769,PHID-USER-3ffkgjb7rllliblvxdy2,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"There are also opportunistic limk updates of the page is ""dynamic"", but yes it is limited.",1684558154,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#8865315, @matmarex wrote:
+> Every time one of these pages are parsed, the state of its category will flip. This seems bad. As one side effect of this, I think everyone watching the pages will see a message about category changes on their watchlist. 
+
+... which should motivate one of those users to fix up the ungodly mess! This should only happen when the parse is a result of an edit though, as LinksUpdate isn't run otherwise.",1684557228,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,You can definitely already do this - e.g. make the category used depend on the current time or something. It does seem like this might make the problem worse though.,1684526427,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I see a slightly different problem – this feature may produce ""unstable"" parses. Consider the scenario:
+* Page A has a template that adds category X if another page B has a category Y
+* Page B has a template that adds category Y if page A does not have the category X
+Every time one of these pages are parsed, the state of its category will flip. This seems bad. As one side effect of this, I think everyone watching the pages will see a message about category changes on their watchlist. There may be other bad side effects.
+
+Even when it doesn't produce an infinite loop like this, you may end up with pages that may need to be parsed multiple times until they reach a stable state. This actually seems even worse. Imagine a vandalism that requires multiple pages to be purged in exactly correct order to be reverted.
+
+I don't know if that's necessarily a deal breaker, but I know that I wouldn't want to be responsible for this :)",1684512883,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I dont think it falls afoul of that as long as it is reflecting DB state (current contents of categorylinks) and not currently parsed page.
+
+Although maybe shouldnt work for current page as that would be confusing",1684512620,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#8858120, @SD0001 wrote:
+> It doesn't enable communication between templates any more than getContent() already allows.
+
+`getContent` does not expand templates. I'm pretty sure the PHP implementation of `getCategories`
+
+```lang=php
+$page = MediaWikiServices::getInstance()->getWikiPageFactory()->newFromTitle( $title );
+...
+$categoryTitles = $page->getCategories();
+```
+
+gets all categories, which may be in templates. So I am pretty sure your statement is not a true statement.
+
+>  Besides, it's often useful - such as for citation modules to decide if dates should be formatted as dmy or mdy. 
+I am not concerned about its utility though -- I think the utility is pretty clear, enabling one path of cross-communication between templates, exactly as you say. I am instead raising a point that previous maintainers of Scribunto have drawn a line in the sand about, and which may have particular implications regarding this extension's support of Parsoid. The maintainers (whoever that may be since Anomie stopped participating in MediaWiki development) should decide whether it's a legitimate objection or not and whether I've identified the issue correctly or not, though if you don't think that's what those two lines are doing, I'm happy to be informed otherwise.",1684509817,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"It doesn't enable communication between templates any more than getContent() already allows. Besides, it's often useful - such as for citation modules to decide if dates should be formatted as dmy or mdy. ",1684311499,PHID-USER-52k2lmr37woy42l6kdmv,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"This change strikes me as enabling communication between separate templates, something which has been a no-no in this extension.",1684256661,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Change 919459 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/Scribunto@master] Expose page categories to Lua%%%
+https://gerrit.wikimedia.org/r/919459",1684006243,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,There's https://www.mediawiki.org/wiki/Extension:CategoryToolbox but I don't how suitable the code is.,1682931513,PHID-USER-3ffkgjb7rllliblvxdy2,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,%%%*** Bug 59111 has been marked as a duplicate of this bug. ***%%%,1397790380,PHID-USER-gljzp3uzec5ukggh6xdk,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,I'd just like to make the explicit suggestion that the categories be exposed be on title objects (see http://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Title_objects ) as they contain other information about a given page.,1397790345,PHID-USER-gljzp3uzec5ukggh6xdk,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"many + signs
+
+Tested: 
+
+In OpenOffice, create a small table with text in cells a1, a2, b1, b2, c2. 
+
+Copy only the rows of the table. 
+
+Paste into VE. 
+
+* the view immediately in VE is of unusable information and some ""+"" characters apparently indicating cell boundaries. 
+
+Version:1.0StartHTML:0000000155EndHTML:0000000881StartFragment:0000000475EndFragment:0000000864➞➞➞➞➞➞➞➞➞➞➞➞➞a1➞➞➞b1➞➞➞➞➞➞➞➞➞➞a2➞➞➞b2➞➞➞c2➞➞➞
+
+* the view in the ""Review your changes"" panel is of a swath of white space with the contents of the table interspersed.
+
+* User tendency is to copy entire contents of rows, yielding many empty cells.  VE dutifully tracks these empty cells and displays an enormous number of ""+"" symbols in the immediate view and mostly empty space in the ""Review your changes"" view.
+
+* Upon save, no table is in the page when pasting from OpenOffice.
+
+Other anomalous results are reported when pasting from the Apple Pages application.  From another user: 
+
+""...number of cells didn't match the number of columns. Since they don't match, tried to delete the cells in order to recover the blank page, but they won't delete.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11079}",1367866200,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-4fybw5go6fyidok4tmp7,task_description,resolved
+VisualEditor: Support pasting of HTML from external sources,"Change 86664 merged by jenkins-bot:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1385500075,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"Change 86664 had a related patch set uploaded by Esanders:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1381157527,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"(In reply to comment #2)
+> I think users will expect that pasting things like tables from other editors
+> and sources into VE to more or less Just Work.
+
+That is bug 41193 (and yes, getting that to work would be lovely). This is about corruption of the clipboard from OpenOffice, which is a distinct problem whether or not we get the pasted-formatting working in time for the 'beta'.",1367874654,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"
+I think users will expect that pasting things like tables from other editors and sources into VE to more or less Just Work.",1367867550,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"* Editing of table structure isn't exactly supported right now
+
+* I'm curious what OpenOffice puts on the clipboard. It may well be that the root cause is ""OpenOffice puts unreasonable things on the clipboard when copying a table""",1367866569,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+Sync source and editor like TeXShop,"**Author:** `mstankus`
+
+**Description:**
+In TeXShop, you can click on a piece of content (for example,
+a word) and choose sync and you are sent directly to the 
+part of the source corresponding to that word. It would be great
+if that could happen for wikis.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1367686680,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zolq2daof5tqslp44gue,task_description,declined
+Sync source and editor like TeXShop,"(In reply to comment #2)
+> Write now, you decide what is wrong, click on edit and then
+> search through markup for the word was misspelled or phrase
+> which needs to be checked. 
+
+This will mostly get fixed by VisualEditor which you can already try out:
+http://blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/
+
+Closing as WORKSFORME.",1368010283,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zolq2daof5tqslp44gue,task_subcomment,NA
+Sync source and editor like TeXShop,"**mstankus** wrote:
+
+Write now, you decide what is wrong, click on edit and then
+search through markup for the word was misspelled or phrase
+which needs to be checked. 
+
+  An alternate approach would be to allow someone to mark 
+a word with a mouse, right click, choose ""edit wiki page""
+and then have the computer open the editor AND move
+the cursor to the part of the markup relevant to that 
+word in the text. It looks through the mark up for you
+and saves everyone time.",1367964649,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zolq2daof5tqslp44gue,task_subcomment,NA
+Sync source and editor like TeXShop,"I don't know what TeXShop is, so ""like in TeXShop"" is not helpful.
+Still I don't understand what is requested here. I click a word in the content of a wiki page (preferably in ""Edit"" mode), and I am send to which source, and why?
+Could you come up with a specific example and exact steps to reproduce, plus the current outcome and the expected outcome? Thanks.",1367833876,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-zolq2daof5tqslp44gue,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","The close icon as defined by the [[ https://wikimedia.github.io/WikimediaUI-Style-Guide/visual-style_icons.html | WikimediaUI icon principles ]]. OOUI is already featuring the correct icon.
+
+| | Product | Description | Code | Screenshot | Screenshot after
+| | -- | -- | -- | -- | --
+| {icon check color=green} | OOUI | [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=icons&theme=wikimediaui&direction=ltr&platform=desktop#widgets-mediawiki-vector-ltr | Uses the correct icon ]] |  | {F9379666} | 
+| {icon check color=green} | Post-Edit Feedback popup | Uses the Unicode × glyph with hover behavior | Extension:PostEdit outputs CSS generated content `×` with style rules. | {F7451633} | {F26525706} 
+| {icon check color=green} | Recent CentralNotice banners | ""x in a circle"" icon, no `:hover` behavior | Extension:CentralNotice outputs an img tag showing :$wgNoticeCloseButton which defaults to [[https://upload.wikimedia.org/wikipedia/foundation/2/20/CloseWindow19x19.png|CloseWindow19x19.png]] | {F26525761} | 
+| - | ~~Visual Editor Feedback dialog~~ | As of 2017-09 not an issue any more => converted to OOUI | | {F9404470} | 
+| {icon check color=green} | ULS | ~~Thicker stroke “x” SVG, no :hover behavior~~ | Extension:UniversalLanguageSelector custom `.uls-icon-close` class | {F9362244} | {F9404483}
+| {icon check color=green} | Extension:GuidedTour | different icon with different size |  `.guider_close` |  | 
+| {icon exclamation-triangle color=red} | Extension:MultimediaViewer | bolder, less contrast; Exempt from amending is the main close icon as it would need a full icon redesign. Will be revisited after T177432 |  | {F10595012} | 
+| {icon check color=green} | Extension:GettingStarted | different icon with different size and lighter grey |  `.mw-gettingstarted-cta-close` | {F10172642} | {F10188673}
+| {icon check color=green} | Extension:PagePreviews | different icon, bolder and bigger | | {F10318266} | {F10319955}
+| {icon check color=green} | Extension:Translate | ~~Similar to ULS, different icon though, as it's minimally smaller in layout~~ | `.grid .tux-message-editor .close` | {F9405760} | 
+
+
+The differences make WMF wikis feel unpolished.
+
+--------------------------
+Original report: 
+**Version**: 1.22.0",1367638620,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_description,resolved
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 389542 **merged** by jenkins-bot:
+[mediawiki/extensions/MultimediaViewer@master] Remove special color treatment of close icon on confirmation
+
+[[https://gerrit.wikimedia.org/r/389542]]",1517946899,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",OH from @RHo: “We can finally close the close icon”,1517337678,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376851 **merged** by jenkins-bot:
+[mediawiki/extensions/CentralNotice@master] Use consistent close icon
+
+[[https://gerrit.wikimedia.org/r/376851]]
+",1517271747,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 394076 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/core@master] mw.postEdit: Use mw.notify to display message
+
+[[https://gerrit.wikimedia.org/r/394076]]
+",1512061260,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 389542 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/MultimediaViewer@master] Remove special color treatment of close icon on confirmation
+
+[[https://gerrit.wikimedia.org/r/389542]]
+",1509995888,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 385250 merged by jenkins-bot:
+[mediawiki/extensions/Popups@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/385250]]
+",1509555770,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 385250 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/Popups@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/385250]]
+",1508444481,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 384094 merged by jenkins-bot:
+[mediawiki/extensions/GettingStarted@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/384094]]
+",1507942239,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 384191 merged by jenkins-bot:
+[mediawiki/extensions/GuidedTour@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/384191]]
+",1507941006,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 384191 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/GuidedTour@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/384191]]
+",1507939773,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 384094 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/GettingStarted@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/384094]]
+",1507923417,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",Possible regression: {T178111},1507846952,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376873 merged by jenkins-bot:
+[mediawiki/core@master] postEdit: Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/376873]]
+",1505254455,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376869 merged by jenkins-bot:
+[mediawiki/extensions/Translate@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/376869]]
+",1504966688,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376873 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/core@master] postEdit: Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/376873]]
+",1504936447,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376869 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/Translate@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/376869]]
+",1504923664,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376851 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/CentralNotice@master] Use consistent close icon
+
+[[https://gerrit.wikimedia.org/r/376851]]
+",1504911061,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376648 merged by jenkins-bot:
+[mediawiki/extensions/UniversalLanguageSelector@master] Use consistent close icon
+
+[[https://gerrit.wikimedia.org/r/376648]]
+",1504857338,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376648 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/UniversalLanguageSelector@master] Use consistent close icon
+
+[[https://gerrit.wikimedia.org/r/376648]]
+",1504828559,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Just to give an update
+
+https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_icon_set gives a list of places the old icon is used, probably based off of this report, but the page has not been updated for 2 years, so it is likely out of date. 
+
+https://doc.wikimedia.org/oojs-ui/master/demos/#icons-apex-ltr gives what I believe to be the most recent icons (using apex). Based on the attached screenshot, that is indeed what Wikipedia uses in the edit feedback
+
+{F4913849}
+
+If someone could investigate other places and help to figure out to what extent this is still an issue, that'd be great",1480546272,PHID-USER-4h2udy357ze7pb3oqlp3,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","{F187901}
+
+This icon is used for all of these instances mentioned above:
+
+https://upload.wikimedia.org/wikipedia/commons/5/56/PEF-1-Cropped.png
+https://upload.wikimedia.org/wikipedia/commons/3/37/CentralNotice_banner_2013-05-03.png
+https://upload.wikimedia.org/wikipedia/commons/3/37/CentralNotice_banner_2013-05-03.png
+
+---
+
+{F187902}
+{F187903}
+
+This icon is used specifically to clear input fields. 
+
+---
+
+I hope this helps. Let me know if I'm not answering any other questions mentioned. I'll provide info around specs soon.",1435682114,PHID-USER-tjeabpzbwsqw3xciydvb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",@Galorefitz: Sorry that nobody has replied yet. I've also brought up your question on the mailing list now: https://lists.wikimedia.org/pipermail/design/2015-June/002325.html,1435674260,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","I am new here and was wondering if I could contribute to resolving this ticket.
+
+I went through the conversation and had a few doubts:
+1. Are we to switch from icons to glyphs, everywhere? Or just make the icons consistent, for now?
+2. Already pointed out, but not answered,
+
+>>! In T50067#526717, @Aklapper wrote:
+> As Jared added the ""easy"" keyword to this ticket: What is the prefered approach and expected implementation for a potential new code contributor? 
+> Which specific 'close' icon to use everywhere?
+> What is the complete list of codebases which are affected?
+",1431636628,PHID-USER-v3ap2mbgahzlhkciw4ai,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","James, there are still many many interfaces especially with smaller dialogs (language switching, fundraising banners, etc) which use icons for dismiss, this is true on mobile as well due to space constraints, I'd prefer to get consistency in these places then we can investigate in which interfaces we should expand beyond just an icon. But for places we're CURRENTLY using an icon, that icon should be consistent.",1414441471,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","(In reply to Andre Klapper from comment #9)
+> As Jared added the ""easy"" keyword to this ticket: What is the prefered
+> approach and expected implementation for a potential new code contributor? 
+> Which specific 'close' icon to use everywhere?
+> What is the complete list of codebases which are affected?
+> 
+> This ticket got a bit messy so I got lost. Summarizing is highly welcome.
+
+From what I understand, the current guidance is ""never ever ever use an icon for workflow functionality"", per user testing outcomes. This is why VE switched over to simple words instead (""Done""/""Cancel""/etc.)",1414441300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","As Jared added the ""easy"" keyword to this ticket: What is the prefered approach and expected implementation for a potential new code contributor? 
+Which specific 'close' icon to use everywhere?
+What is the complete list of codebases which are affected?
+
+This ticket got a bit messy so I got lost. Summarizing is highly welcome.",1414344333,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","8. Besides #2 (an 'X' in a circle), other fund-raising banners use the plain 7px 'x' image donate/Small-black-close.png for their close iocn, e.g. http://meta.wikimedia.org/w/index.php?title=Main_Page&banner=B13_0725_trn_Cntrl_nd_yyYY&force=1",1376346995,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","(In reply to comment #4)
+> 1. Located in core (probably /skins/common/images/)
+
+In the past I've tried to use core image resources in CSS files together with @embed without success. I think that desperately needs fixing to go onward with the unification.
+
+> 3. Available in a large size and a small size
+
+I would consider having SVG version too a must.",1372850261,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","7. Extension:GuidedTour uses a square [X] icon, no hover, for its .x_button style. <https://bits.wikimedia.org/static-1.22wmf3/extensions/GuidedTour/modules/externals/mediawiki.libs.guiders/mediawiki.libs.guiders.submodule/x_close_button.jpg>",1368227877,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",I checked in a smaller version of the closewindow19x19.png image in change I0e170305.,1367693472,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","There are also currently 2 close window images in core (besides jQuery UI):
+
+1. https://bits.wikimedia.org/static-1.22wmf3/skins/common/images/closewindow.png
+
+2. https://bits.wikimedia.org/static-1.22wmf3/skins/common/images/closewindow19x19.png
+
+I don't think #1 is used anywhere any more (but would be worth checking).
+
+I believe #2 is the same image as the one used in CentralNotice and similar to the Agora design.
+
+If we want developers to standardize on one close icon it needs to have the following properties:
+
+1. Located in core (probably /skins/common/images/)
+2. Works for any background (light, dark, grey, etc.)
+3. Available in a large size and a small size
+4. Conforms to design guidelines
+
+closewindow19x19.png is probably the best bet since it meets 3 of the 4 criteria. All we need to do is create a smaller version for use in small UI elements. Then we can start standardizing everything on that. We can override the jQuery UI close box in resources/jquery.ui/themes/default/.",1367693407,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",Related URL: https://gerrit.wikimedia.org/r/62237 (Gerrit Change I0e1703057e45297d6728cb635c58183aa37103da),1367693310,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","4. The Universal Language Selector extension uses its own chunky X icon with no hover behavior. jquery.uls styles icon-close with background of https://bits.wikimedia.org/static-1.22wmf3/extensions/UniversalLanguageSelector/lib/jquery.uls/images/close.svg
+
+5, 6. The Translate and VisualEditor extensions also have close.svg icons for CSS backgrounds, each slightly different.",1367641625,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","1. is a design from late 2012.
+
+2. matches https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_Icon_Set#General edits in 2012 which says ""Dismiss - an 'X' in a circle.""
+
+3. came from jquery.ui work in 2010.",1367639602,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"""Leave feedback"" link has confusing scope","Component: UI
+
+The speech bubble icon and ""Leave feedback"" link in Visual Editor look like they apply to the page being edited.  I was expecting a Talk: tool.
+
+It would be more clear if the text were ""Report bug in Visual Editor"", but that's annoyingly verbose.  Which is sort of the intention here, I assume ;)  Normally, this link would get buried in a dropdown menu or something, IMO.
+
+The problem is exacerbated if you are sort of blind and zoom in your browser a lot, because the VE feedback link becomes very prominent once the toolbar is wrapped.
+",1367214840,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-necjrhau4bastnyumud5,task_description,resolved
+"""Leave feedback"" link has confusing scope","Yep, from what I recall of the past and my understanding of the report, the issue looks solved.",1419610136,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-necjrhau4bastnyumud5,task_subcomment,NA
+"""Leave feedback"" link has confusing scope","The link is now neatly tucked inside a dropdown menu. There's no screenshot on this bug, so I can only guess that it wasn't like this before. This probably resolves the issue sufficiently.
+
+{F23347}",1419186729,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-necjrhau4bastnyumud5,task_subcomment,NA
+"""Leave feedback"" link has confusing scope","Adding many blockers of bug 38638 to the list of ""easy"" bugs, to mark them as candidates for [[mw:Google Code-in]] tasks (gci2013). If you think this bug is not suitable, remove the keyword.",1384864550,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-necjrhau4bastnyumud5,task_subcomment,NA
+"""Leave feedback"" link has confusing scope",The feedback link isn't a VisualEditor item but part of MediaWiki core. Moving bug appropriately.,1367275669,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-necjrhau4bastnyumud5,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","Screenshot of page in view mode
+
+Show thumbnail in user preference size in edit mode.
+
+1. Set user preference to 300 pixel: ""Thumbnail size:"" of https://de.wikipedia.org/wiki/Spezial:Einstellungen?uselang=en#mw-prefsection-rendering
+
+2. Edit page with image included as standard thumb.
+
+Thumbnail is shown in a smaller size instead of the user preference size.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/thumb
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50379
+
+**Attached**: {F10384}",1367185680,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-pwct3nalejruvwpszxyi,task_description,resolved
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","We have now implemented displaying default images in local wiki default size, and explicitly *not* user-preference size.
+
+This is because the editing surface should encourage users to make the right kind of edits for all users, not just themselves. If a page has an image at default and a second at 300px, and a user with a default of 400px resizes one of the images to fit in with the other, a user with a default of 200px (e.g. an anonymous user) will get a different experience and may try to revert (or the change will have a different effect to what was intended).
+
+I'm therefore re-titling this bug to just refer to local wiki size, and marking as FIXED. Happy to discuss further.",1393447280,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","Change 114420 merged by jenkins-bot:
+Set up wiki-default image size
+
+https://gerrit.wikimedia.org/r/114420",1393446711,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","Change 114420 had a related patch set uploaded by Mooeypoo:
+[wip] Set up wiki-default image size
+
+https://gerrit.wikimedia.org/r/114420",1392873520,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","French Wikipedians would like VE to follow the local convention that thumbnails are only displayed with the ""upright"" option (https://en.wikipedia.org/wiki/Wikipedia:Extended_image_syntax#Size).",1389017980,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","User preference and wiki-default sizes specify the maximum width of an image, regardless of dimensions or aspect ratio, but VE scales the images to fit in a 190px by 212px box.
+
+This means that some images, particularly tall thin ones such as full-length portraits, get rendered at very different sizes in VE edit mode to view mode, with consequential impact on the layout of surrounding content.",1380667642,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size",*** Bug 52487 has been marked as a duplicate of this bug. ***,1380666480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size",Confirmed with Gabriel (Parsoid team) that this [should|is going to be] solved in VE.,1368216779,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","Created attachment 12197
+Screenshot in edit mode with smaller thumbnail
+
+**Attached**: {F10385}",1367185755,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Review your changes"" pop-over overlaps sidebar in monobook skin","Review your changes
+
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F10352}",1367136660,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-fs4ayby7t52qjcroab4t,task_description,declined
+"VisualEditor: ""Review your changes"" pop-over overlaps sidebar in monobook skin",Meh. I guess I'll never use VE.,1370328889,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-fs4ayby7t52qjcroab4t,task_subcomment,NA
+"VisualEditor: ""Review your changes"" pop-over overlaps sidebar in monobook skin","Exactly what is the problem? The fact that the VisualEditor dialog overlaps the Monobook sidebar, or that the searchbox/logo in the Monobook sidebar overlap the VisualEditor dialog?
+
+The VisualEditor dialog overlapping is pretty much inevitable since it has a minimum width. If your screen is too narrow it has no where to go (short of a scrollbar, which I think give a worse user experience).
+
+If it were always overlapping it would be a more pressing problem, but right now it only overlaps if you activate the review dialog, in which case your focus is more likely to be on the dialog than on the sidebar (e.g. if we need to choose, it is the obvious choice).",1370298705,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fs4ayby7t52qjcroab4t,task_subcomment,NA
+VisualEditor: Tools to set/unset text with annotations (tracker),"Given that these all exist in DM, it's ""just"" a question of making a set of icons for each function and adding it to the tool bar (and then working out what to do with a toolbar with eight such icons when we wanted two.
+
+Have left off from the existing list in ve.dm.TextStyleAnnotation.js:
+
+* span - as that'll need to be a distinct bug given the complexity (it'll need at least an inspector, possibly a dialog)
+* strong/em - should we just silently use these instead of b/i (or vice versa)? Either way, it feels confusing to give the user both options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367087820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nkytk4yj27kjhhclg73g,task_description,declined
+VisualEditor: Tools to set/unset text with annotations (tracker),All now in #VisualEditor-EditingTools.,1422405518,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nkytk4yj27kjhhclg73g,task_subcomment,NA
+VisualEditor: Tools to set/unset text with annotations (tracker),Related URL: https://gerrit.wikimedia.org/r/64801 (Gerrit Change I51f2605e7d8e2bab1d641f02244d5cd24f505676),1369136660,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nkytk4yj27kjhhclg73g,task_subcomment,NA
+VisualEditor: Tools to set/unset text with annotations (tracker),"Icons for these are now merged into master; the outstanding work here is relatively light, except for the overall design issue about the toolbar having too many buttons.",1369094298,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nkytk4yj27kjhhclg73g,task_subcomment,NA
+VisualEditor: Tools to set/unset text with annotations (tracker),Related URL: https://gerrit.wikimedia.org/r/64475 (Gerrit Change I2f317e1dda2c2e2fceac401768c732dae02e83ce),1368875872,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nkytk4yj27kjhhclg73g,task_subcomment,NA
+VisualEditor: Report that the save dialog omits the save description entry box on hewiki/Windows/Firefox,"Cannot reproduce in Firefox/Mac or Chrome/Mac; asking user to reconfirm.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**Platform**: PC",1366931820,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xc3udo6fxmbjckxyjow3,task_description,invalid
+VisualEditor: Report that the save dialog omits the save description entry box on hewiki/Windows/Firefox,I asked the user. he meant to a local script which isn't supported by VE.,1367254280,PHID-USER-u7udgblfyop6qd5wxot6,PHID-TASK-xc3udo6fxmbjckxyjow3,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,"As suggested by Timo - currently we have 'wmgUseVisualEditor' and 'wmgVisualEditorParsoidPrefix' which both need to be defined for each wiki we're putting VE on, which is a bit annoying (and prone to mistakes) - when we have all 295 Wikipedias with it switched on, it will be even worse. We should probably clean this up a bit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366731840,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-em5ivp4uf7qvneztv3ep,task_description,resolved
+VisualEditor: Clean up the way that VE must be configured per wiki,This is now done and live in production.,1369920023,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,"(In reply to comment #1)
+> We could replace wgUseVisualEditor with a visualeditor.dblist file, and
+> change the Parsoid prefixes to be equal to $wgDBname.
+
+$wgUseVisualEditor (or wmgUseVisualEditor) seems fine to me, not sure if a dblist would make things easier.
+
+Getting rid of having to configure wmgVisualEditorParsoidPrefix for each wiki would be great (or at least setting it dynamically/automatically from CommonSettings.php).",1369145278,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,Related URL: https://gerrit.wikimedia.org/r/64493 (Gerrit Change I621e98da3be4f787e294d97b350b92d217f43a00),1368896205,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,"(In reply to comment #1)
+> We could replace wgUseVisualEditor with a visualeditor.dblist file, and
+> change the Parsoid prefixes to be equal to $wgDBname.
+
+That sounds like a start, but we're going to want to run some wikis in nothing (no preference to switch on - just not in the .dblist file?), some in alpha (opt-in, limited namespaces) and some in beta (default, all ""content"" even-numbered namespaces that won't break - e.g. MediaWiki:, Template:, Schema:, ? others). Would we want two .dblist files? And some magic juice to decide what namespaces were safe?",1368770741,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,"We could replace wgUseVisualEditor with a visualeditor.dblist file, and change the Parsoid prefixes to be equal to $wgDBname.",1368770161,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Always submit Parsoid bugs over https,"Please write your bugs report to http://parsoid.wmflabs.org/_bugs/ only with https to avoid a secure hole.
+
+Please see this as a blocker for the coming roll out. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366641360,PHID-USER-a6jwrurphpx6yl4coupk,PHID-TASK-zdwyyiwstl6uz4rcbn5g,task_description,invalid
+VisualEditor: Always submit Parsoid bugs over https,"We're scrapping this feedback system, so marking as INVALID.",1370629791,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zdwyyiwstl6uz4rcbn5g,task_subcomment,NA
+VisualEditor: Always submit Parsoid bugs over https,"Comment from bug 47507 comment 1:
+
+| No data goes over the wire that is personally-identifying, so I would
+| disagree that this is a blocker; however, yes, this is good practice and we
+| should try to do thi[s] (especially, to avoid unexpected mix-mode for users).",1366668178,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zdwyyiwstl6uz4rcbn5g,task_subcomment,NA
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,"It seems <syntaxhighlight is working just fine, but it's old deprecated 'redirect' <source is not recognized by VE, as can be seen in the link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/wiki/User:TheDJ/Sandbox",1366465260,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-2izho3en3c7veqknv2wr,task_description,resolved
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934095,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2izho3en3c7veqknv2wr,task_subcomment,NA
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,"
+
+*** This bug has been marked as a duplicate of bug 47579 ***",1366790189,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-2izho3en3c7veqknv2wr,task_subcomment,NA
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,"This is probably something Parsoid needs to handle (or, rather, SyntaxHighlight with the Parsoid functionality to cope with 'redirects' between extension tags). Gabriel, does this sound right to you?
+
+@Raimond - bug 43126 is about editing these blocks; this is just about displaying them correctly.",1366471273,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2izho3en3c7veqknv2wr,task_subcomment,NA
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,Dupe of bug 43126?,1366465834,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-2izho3en3c7veqknv2wr,task_subcomment,NA
+VisualEditor: VE tab missing oldid when using edit source on an oldid,"https://en.wikipedia.org/w/index.php?title=Phil_Thompson&action=edit&oldid=535300833
+
+Note that in this mode, the VE tab is missing the oldid
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Phil_Thompson&action=edit&oldid=535300833",1366464180,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-v3h2ouiwohdu44mwy2g6,task_description,declined
+VisualEditor: VE tab missing oldid when using edit source on an oldid,"All of the tabs in this mode go to current, not oldid, so I think this is something that either should be fixed upstream in MW core (in which case, VE should just magically work), or be left as is, given that users will expect the current behaviour.",1368809793,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3h2ouiwohdu44mwy2g6,task_subcomment,NA
+VisualEditor: VE tab missing oldid when using edit source on an oldid,"In this mode without the VE, the wikitext edit tab doesn't go to the oldid, it goes to the curid page; I think we're going to have to think about how to let users get the VE from here.
+
+Timo, any thoughts?",1366471108,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v3h2ouiwohdu44mwy2g6,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab text should be ""Create source"" or similar when page is non-existent","Currently the ""Edit source"" button's label is the same whether the page is extant or not. This should change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1366394700,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lr6aehasmla6m24l7lfy,task_description,resolved
+"VisualEditor: ""Edit source"" tab text should be ""Create source"" or similar when page is non-existent",Merged; will go out with wmf5.,1368885140,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lr6aehasmla6m24l7lfy,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab text should be ""Create source"" or similar when page is non-existent",Related URL: https://gerrit.wikimedia.org/r/64276 (Gerrit Change Iafba040cb8eb53017f38f2099a473e0e43e2ec46),1368791290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lr6aehasmla6m24l7lfy,task_subcomment,NA
+Use JSDuck syntax for inline examples in code documentation,"That is https://github.com/senchalabs/jsduck/wiki/Inline-examples
+
+For instance:
+
+resources/js/ext.translate.editor.js
+9:       * Example usage:
+
+resources/js/ext.translate.proofread.js
+107:     * Example usage:
+
+resources/js/ext.translate.pagemode.js
+10:      * Example usage:",1365665640,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nqzemfntve3l7ortesoj,task_description,declined
+Use JSDuck syntax for inline examples in code documentation,"JSDuck's `@example` syntax is for a live demo of running code. For OOjs UI and VisualEditor this can be useful in places for classes and methods that are largely about their visual and interactive rendering (not about the shape return value itself). However I'm not sure that's useful in the case of the Translate extension.
+
+To render code examples with syntax highlighting, just use three backticks (or indentation) to create a code section in JSDuck's markdown rendering. Closing this task as it doesn't seem actionable right now.
+
+Right now Translate documentation isn't rendered/published anywhere, so in its current form the code examples are readable as-is. If they are published, one of the three examples will need to be indented for it to be preformatted correctly.",1487992074,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nqzemfntve3l7ortesoj,task_subcomment,NA
+Use JSDuck syntax for inline examples in code documentation,"Example of how usage example is used:
+
+https://doc.wikimedia.org/VisualEditor/master/#!/api/ve.init.sa.Target
+
+(especially notice the live preview)
+
+https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.html",1379593886,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-nqzemfntve3l7ortesoj,task_subcomment,NA
+"VisualEditor: ""Report problem"" button should give some feedback","- Edit an article on the English Wikipedia in the VE
+
+- Click ""Review and save""
+
+- Click ""Something is wrong""
+
+- Enter text into the field and click ""report problem""
+
+Nothing happens - either the error report is not sent, or the fact that it was sent is not conveyed to the user.
+
+Reproduced three times in a current Chromium version (Chromium/25.0.1364.160) on Ubuntu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1365661620,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-tz5is7r52hxlpbizafzp,task_description,resolved
+"VisualEditor: ""Report problem"" button should give some feedback","The HTTPS element of this is now seemingly fixed in production. On submission, the user gets a ""Your problem has been reported. Thank you."" message. Marking as closed.",1366397733,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tz5is7r52hxlpbizafzp,task_subcomment,NA
+"VisualEditor: ""Report problem"" button should give some feedback","To clarify, Gabriel checked the log and the reports I sent indeed do not seem to have made it through.
+
+And I agree that a ""thank you"" alert would be nice, but I would already have been happy if the ""Report a problem"" dialog box would just have closed after clicking the ""Report problem"" button. Instead, nothing happened at all...",1365716252,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-tz5is7r52hxlpbizafzp,task_subcomment,NA
+"VisualEditor: ""Report problem"" button should give some feedback",IIRC posting from Wikipedia pages accessed via https has always been broken because of client-side security restrictions for subrequests. I think this is an instance of that problem.,1365715063,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-tz5is7r52hxlpbizafzp,task_subcomment,NA
+"VisualEditor: ""Report problem"" button should give some feedback","The reports go to a private log that Gabriel monitors. :-)
+
+We're likely to kill the feature in the medium-term anyway, but a ""Thank you for your report"" JS alert wouldn't go amiss.
+
+Timo, thoughts?",1365714340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tz5is7r52hxlpbizafzp,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"An automatic tracking category for pages with errors in <math> (when parsed by texvc) would help finding these pages and fixing the errors.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1365503760,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_description,resolved
+Add tracking category to pages with errors in <math>,"I see nobody answers. I am closing the task by myself. If there is a problem, reopen it.
+
+Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].",1467323599,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"The discussion was moved to [[https://en.wikipedia.org/wiki/MediaWiki_talk:Math-tracking-category-error|here]].
+",1467219463,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"No problem.
+",1467218718,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,Thank you. I have posted an edit request at that page on en.wiki.,1467210767,PHID-USER-7cpk77uy2iq7bxf6hac6,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.
+Second of all, there is no link for this case help, because it's too obvious.
+1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.
+2. Put there for example a code:
+{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]
+3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.
+4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment).
+5. Save the page.
+6. Open one page with a math error in good namespace for editing. Make sure the category is there.
+7. Open one page with a math error in bad namespace for editing. Make sure the category is not there.
+8. If there is a problem, replace "":"" with ""-"" in the code and try again.
+9. When you are sure it works, run a nulledit bot on the current category content.
+10. Done.
+ ",1467195164,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.
+Second of all, there is no link for this case help, because it's too obvious.
+1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.
+2. Put there for example a code:
+{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]
+3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.
+4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment).
+5. Save the page.
+6. Open one page with a math error in good namespace. Make sure the category is there.
+7. Open one page with a math error in bad namespace. Make sure the category is not there.
+8. If there is a problem, replace "":"" with ""-"" in the code and try again.
+9. When you are sure it works, run a nulledit bot on the current category content.
+10. Done.
+ ",1467194961,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"I would love to do it myself (for everyone, not just in my own vector.js). @IKhitron, do you have a link to instructions on how to take care of it on en.wiki? Thanks.",1467177192,PHID-USER-7cpk77uy2iq7bxf6hac6,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"I meant one line in wiki code, @SalixAlba and @Jonesey95, not jawascript.
+",1467148543,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors  will remain.
+
+If its really a problem this bit of javascript in your vector.js will hide most of the talk pages.
+
+  jQuery( document ).ready( function( $ ) {	
+    	if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") {
+		$("".mw-category-group a"").each(function(ind,ele) {
+			var title = ele.innerHTML;
+			if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") 
+			 || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) {
+				root = ele.parentElement;
+				$(root).css({""display"":""none""});
+				console.log(ele.innerHTML);
+			}
+		})
+	   }
+     }",1467141776,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"But @Jonesey95, you can do it in a minute by yourself.
+",1467135776,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"":
+
+""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories.""
+
+The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",1467130992,PHID-USER-7cpk77uy2iq7bxf6hac6,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"@Aklapper? Or maybe @Quiddity? Thanks.
+",1466776616,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,It looks like this is fixed in T134872 by https://gerrit.wikimedia.org/r/292576 We can probably close this as a duplicate. ,1466691225,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,So we now seem to have [[Category:Pages with math errors]] on en wiki at least. ,1466630074,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"Hello, @Aklapper. It works. I think you need close this task as resolved.
+",1466629083,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,I think we would need comunity consensus for enabling the MathSearch extension in production... and a lot of cleanup work... sinc it's currently more desinged as demo/proof of concept.,1437662084,PHID-USER-4sfm3grxdo6hnogm4iqe,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"**physik** wrote:
+
+(In reply to Richard Morris from comment #2)
+> This error is made worse by the difference between the syntax used in
+> MathJax and texvc. In
+> http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE
+> a unicode character was used in a formula, the editor was probably using
+> MathJax so the error did not show up. There seem to be a few such errors. A
+> google search
+> https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.
+> org+-Talk%3A
+> can be used to find some.
+
+Bug 72240 will make it better again. I'll try to migrate this feature from MathSearch to the Math extension.",1413745226,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"This error is made worse by the difference between the syntax used in MathJax and texvc. In
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE
+a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A
+can be used to find some.",1376979625,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"**physik** wrote:
+
+This is already a feature of the MathSearch extension.",1365506334,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+VisualEditor: Part of MetaList should be moved into Document,"Per IRC discussion between me and Trevor:
+
+* Move list of MetaItems to dm.Document
+* Keep MetaList (possibly rename it) with current API, wraps around list of items in Document
+* MetaList takes a surface, and can make changes using that surface
+* MetaItem.remove method will have to be removed, because it can't call back into the surface
+
+(This is for post-July)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1365460200,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-r3vxaorhac46omf45tpw,task_description,open
+VisualEditor: Any transaction which results in metadata being merged won't rollback cleanly,"Take the document:
+
+<!-- meta -->content<!-- data -->
+
+If you remove all of ""content"", the two comments now have to share an offset in the metadata array but this process is not recorded in the transaction. As a result, when the commit is rolled-back the comments aren't re-split so the resulting doc is:
+
+content<!-- meta --><!-- data -->
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1365265140,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-vebapwqy2gnmj6e46row,task_description,resolved
+VisualEditor: Any transaction which results in metadata being merged won't rollback cleanly,Related URL: https://gerrit.wikimedia.org/r/57850 (Gerrit Change I4edad1c2dd37c723bff2792bab7d694ef17a86dc),1365266744,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-vebapwqy2gnmj6e46row,task_subcomment,NA
+"Remove ""sleep"" from tests","We are using `sleep` in several places. Sleep is evil. The code should be refactored so the sleep is removed.
+
+There are more robust ways to wait for something to happen than using sleep:
+
+http://watirwebdriver.com/waiting/
+https://github.com/cheezy/page-object/wiki/Ajax-Calls
+
+```
+$ grep --include *.rb  -R -F 'sleep' .
+
+./wmde/WikidataBrowserTests/tests/browser/features/support/env.rb:  sleep env_no * 4 # sleep time to give webdriver time to setup
+./wmde/WikidataBrowserTests/tests/browser/features/support/modules/entity_module.rb:    sleep(1.0 / 3) while execute_script('return jQuery.active') != 0
+./wmde/WikidataBrowserTests/tests/browser/features/support/modules/entity_module.rb:    sleep 1
+
+./mediawiki/selenium/features/step_definitions/environment_steps.rb:    sleep 0.3
+
+./mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/general_steps.rb:  sleep(Integer(seconds))
+./mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/search_steps.rb:    sleep(5)
+./mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/search_steps.rb:    sleep 1
+
+./mediawiki/vagrant/mediawiki/extensions/Gather/tests/browser/features/step_definitions/common_steps.rb:  sleep 5
+./mediawiki/vagrant/mediawiki/extensions/Gather/tests/browser/features/step_definitions/edit_collection_steps.rb:  sleep 5
+
+./mediawiki/vagrant/mediawiki/extensions/MobileFrontend/tests/browser/features/step_definitions/editor_ve_steps.rb:    sleep 2 # this gets around a race condition bug in ChromeDriver where both the confirm and the toast are in the page at once, and Chrome reports either ""stale element reference: element is not attached to the page document"" or ""Element does not exist in cache""
+./mediawiki/vagrant/mediawiki/extensions/MobileFrontend/tests/browser/features/step_definitions/notification_steps.rb:  sleep 1
+./mediawiki/vagrant/mediawiki/extensions/MobileFrontend/tests/browser/features/step_definitions/notification_steps.rb:  sleep seconds.to_i
+
+./mediawiki/vagrant/mediawiki/extensions/MultimediaViewer/tests/browser/features/step_definitions/mmv_download_steps.rb:  sleep 1
+
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:  sleep 0.5 # Sleep because of annoying JS animation happening in the date picker
+
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/media_interface_steps.rb:    sleep 1
+```
+
+
+
+
+
+
+
+",1365078180,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_description,declined
+"Remove ""sleep"" from tests",Unlikely to ever be resolved because of {T139740}.,1495812867,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","We can keep this open.  I actually just added a sleep to a test because I needed to get on with other things, and I should return to fix it at some point.",1405701499,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","(In reply to Andre Klapper from comment #18)
+> Are there more tests containing sleep or is this fixed?
+> 
+> Tony: Are you still working on this or should the assignee be reset to
+> default?
+I think there are a few more sleep keywords to be removed. Sorry, but I dont think I will be able to continue on this right now. Resetting to default assignee for the time being.",1405688273,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Are there more tests containing sleep or is this fixed?
+
+Tony: Are you still working on this or should the assignee be reset to default?",1405687592,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",All patches merged => resetting status from PATCH_TO_REVIEW to NEW,1394711816,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 109471 merged by jenkins-bot:
+Removed sleep variable from TwnMainPage tests
+
+https://gerrit.wikimedia.org/r/109471",1390904723,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Cirrus has two sleeps:
+1.  It waits for some suggestions not to appear.  Without reworking the error handling in the javascript I can't remove this.  I don't feel up to reworking that right now.
+2.  It sleeps between the creation of two pages that it uses to test searches that prefer pages with recent edits.  If I could backdate edit times then I wouldn't need it but I can't at this point.
+
+In total Cirrus sleeps 35 seconds because each of the above is executed once.  It could be better but it could be worse.",1390833772,PHID-USER-2rnfxoezl66afpa7w7in,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 109471 had a related patch set uploaded by 01tonythomas:
+Removed sleep variable from TwnMainPage tests
+
+https://gerrit.wikimedia.org/r/109471",1390656466,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 108916 merged by Cmcmahon:
+Replaced sleep with page-object gem waiting API
+
+https://gerrit.wikimedia.org/r/108916",1390407465,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 108918 merged by jenkins-bot:
+Removed sleep with waiting API in browsertests
+
+https://gerrit.wikimedia.org/r/108918",1390403834,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 108918 had a related patch set uploaded by 01tonythomas:
+Removed sleep with waiting API in browsertests
+
+https://gerrit.wikimedia.org/r/108918",1390402787,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 108916 had a related patch set uploaded by Zfilipin:
+Replaced sleep with page-object gem waiting API
+
+https://gerrit.wikimedia.org/r/108916",1390401099,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","(In reply to comment #8)
+> Tony and I have paired on getting his environment set up to work on this.
+I will put my status in [QA] once I have made my environment ready.",1389959040,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Tony and I have paired on getting his environment set up to work on this. Tony, if you still are interested in working on this, feel free to assign the bug to yourself. Let me know if you need help.",1389957541,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443702073,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1389430912,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Tony Thomas:  just removing the code is not enough.  The tests have to be made to wait properly for whatever it is they are waiting for.  
+
+Using sleep() is either an interim step that never got completed, or else the person writing the test could not think of a better way to wait for whatever the test needs.  
+
+So the tests need to be updated in a thoughtful way so that they wait correctly without using sleep() but also without failing mistakenly.",1389377877,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","(In reply to comment #3)
+> Sleep statements found:
+> 
+Removing the code from the following places will do ?",1389377680,PHID-USER-b3xlpjqyzhcppjoumu63,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443702056,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1386004108,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443701949,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1384961357,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443702034,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1384960949,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443701981,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1381410981,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+VisualEditor: mw.ViewPageTarget tabLayout should be configurable as part of mw-config,"mw.ViewPageTarget tabLayout is currently hard-coded, which means that we can't have VE work in replace mode on one wiki and add mode on another.
+
+[No doubt other aspects of the integration configuration should not be hard-coded.]
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1365032760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-iciq5e24fktvreyuptk3,task_description,resolved
+VisualEditor: mw.ViewPageTarget tabLayout should be configurable as part of mw-config,Related URL: https://gerrit.wikimedia.org/r/66881 (Gerrit Change I3fcb0c2903ae62d61ff789b5504e0ea23932121b),1370298230,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-iciq5e24fktvreyuptk3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Page: pages are not plain wikitext pages but are split into three textareas: header, footer and body and a proofreading level tag (note 1).
+So, an adaptation of the VisualEditor to these pages is needed in order to make edition of the pages work.
+
+The UI need to be tweaked in order to allow the splitting of the main textarea into three and the edition of the Proofreading level at the save of page as it works currently for wikitext editing (example: https://en.wikisource.org/w/index.php?title=Page:La_Fontaine_-_The_Original_Fables_Of,_1913.djvu/20&action=edit ).
+
+An other useful (but less important thing) things is to add modules to the Visual Editor to support specific tags used by Wikisource like <pages>, <section> and <poem>.
+
+note 1: structure of the page as save in the database:
+<noinclude><pagequality level=""LEVEL"" user=""LAST PROOFREADER"" />HEADER<div class=""pagetext"">BODY<noinclude>FOOTER</noinclude>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey
+
+This proposal received 41 support votes, and was ranked #23 out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Wikisource#Visual_Editor_adapted_for_Wikisource",1364329860,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-v7kj4prknc3sujshfgg3,task_description,resolved
+Create a VisualEditor plugin to integrate with ProofreadPage,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVgmueGyHQCSeVEJeq-D} [2016-11-02T20:27:45Z] <arlolra> updated Parsoid to version 173d7e32 (T149241, T119228, T141723, T141905, T147742, T48580, T133320)",1478118471,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Change 295707 merged by jenkins-bot:
+Allow extensions to handle specific contentmodels.
+
+[[https://gerrit.wikimedia.org/r/295707]]",1476648660,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Change 295707 had a related patch set uploaded (by Cscott):
+Allow extensions to handle specific contentmodels.
+
+[[https://gerrit.wikimedia.org/r/295707]]
+",1466695881,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,Parsoid support for extensions implementing their own contentmodels at https://gerrit.wikimedia.org/r/295707 ,1466695854,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2398307, @Osnard wrote:
+> Is there already a place/time made out to work on this during the Hackathon?
+
+Table in Room 12 if you're not there!",1466599379,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Change 284681 merged by jenkins-bot:
+Sectioned edit target for page namespace
+
+[[https://gerrit.wikimedia.org/r/284681]]",1466598809,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,Is there already a place/time made out to work on this during the Hackathon?,1466584161,PHID-USER-khiuzivvgcimpgvedbzf,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"when trying to insert > pages get a 404 error ;' trying to switch to code hangs.
+when refresshing and repeating it saves properly. on chrome browser 
+{F4145216}",1465443442,PHID-USER-uclm66q7d2hquzahxskz,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"when trying to insert > pages get a 404 error
+{F4145216}",1465443336,PHID-USER-uclm66q7d2hquzahxskz,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"@DannyH, you should subscribe to this :-)",1461661097,PHID-USER-jhzyhftzsmppvszocqg2,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2232258, @coren wrote:
+>>>! In T48580#2228508, @jayvdb wrote:
+>> Is it safe to assume this feature will not suddenly become active and in use in production once code from this task is merged?
+> 
+> It will certainly remain as a beta feature for quite some time, requiring explicit activation.
+
+Well why not activate it on https://test2.wikipedia.org at the very least? The ProofreadPage extension is already 'enabled' there and nobody really uses it for proofreading; just for testing &/or illustrative purposes.
+
+If not, please remember to make the beta ""option"" available there as well.",1461460533,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2228508, @jayvdb wrote:
+> Is it safe to assume this feature will not suddenly become active and in use in production once code from this task is merged?
+
+It will certainly remain as a beta feature for quite some time, requiring explicit activation.",1461417141,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Is it safe to assume this feature will not suddenly become active and in use in production once code from this task is merged?  Sorry that I need to ask ... but I have been unpleasantly surprised in the past (definitely not referring to the developers active on this or related task), and I hope to avoid that occurring in this case.
+
+I think WS folk would like to play with it a little in a test bed before it becomes active somehow, and will need longer than a few days as the deploy process moves from beta/test/prod.
+
+I certainly would be happy to do some QA work on it, if given a decent window to work with.  i.e. I cant make any promises to help if the approach is: it is merged, and will be deployed in three days, happy hunting.",1461270188,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Change 284681 had a related patch set uploaded (by Esanders):
+WIP Sectioned edit target for page namespace
+
+[[https://gerrit.wikimedia.org/r/284681]]
+",1461240057,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2214028, @Ankry wrote:
+> We are still waitng for Page namespace support which is the main editing namespace for most wikisources. Moreover, many new wikisourcians edit **only** in the Page namespace. The general trend is to have articles in main namespace automatically or semi-automatically generated basing on data from Index and Page namespaces. So having VE support in main namespace may be a nice feature, but mostly useless.
+
+Indeed.  Having VE there at all was a preliminary requirement, not the end result.  :-)",1461168206,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"i noted some buggy interaction for the insert > pages, initially rather than subsequenly editing pages template https://www.mediawiki.org/wiki/VisualEditor/Feedback",1461083185,PHID-USER-uclm66q7d2hquzahxskz,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,i noted some buggy interaction for the insert > pages initially rather than subsequenty editing pages template https://www.mediawiki.org/wiki/VisualEditor/Feedback,1461083004,PHID-USER-uclm66q7d2hquzahxskz,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,i noted some buggy interaction for the insert > pages initially rather than editing pages https://www.mediawiki.org/wiki/VisualEditor/Feedback,1461082519,PHID-USER-uclm66q7d2hquzahxskz,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2213983, @Qgil wrote:
+> What is missing to consider this task Resolved?
+
+We are still waitng for Page namespace support which is the main editing namespace for most wikisources. Moreover, many new wikisourcians edit **only** in the Page namespace. The general trend is to have articles in main namespace automatically or semi-automatically generated basing on data from Index and Page namespaces. So having VE support in main namespace may be a nice feature, but mostly useless.
+",1460986863,PHID-USER-2ji2k3idgmipacu4ftck,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"What is missing to consider this task Resolved?
+
+I am trying to summarize the progress on this task at https://meta.wikimedia.org/wiki/Wikimedia_Blog/Drafts/WIP_Wikimedia_Hackathon_2016_post#The_connection_with_the_Community_Wishlist. Is there any beautiful screenshot in Commons that we can reuse?",1460985360,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,This was deployed in the new Single Edit Tab mode.  The basic explanation is at https://www.mediawiki.org/wiki/VisualEditor/Single_edit_tab if anyone is looking for information.,1460150503,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Insert -> Pages -> there is no ""onlysection"" attribute
+
+Z.",1460051560,PHID-USER-zg5ljrw5inhmynt7vcfd,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,works well in chrome and firefox. saved first new article.,1460048163,PHID-USER-uclm66q7d2hquzahxskz,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2173976, @Jdforrester-WMF wrote:
+> Clarification: This will be for all Wikisources, not just frws. :-)
+
+Oh, yeah.  Good point.  It will be available (selectable from the beta features selector) on all Wikisources.
+",1459688948,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2172585, @coren wrote:
+> @Jdforrester-WMF is planning to turn the configuration switch on April 7.
+> 
+> At that point, Visual Editor will become available as a beta feature on fr.wikisource.org for all content namespaces except Page (that's the next part being worked on now).
+
+Clarification: This will be for all Wikisources, not just frws. :-)
+",1459667947,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Current status: we now have a proper design for Page namespace that is in progress but - as a first step - we now have usable mainspace editing with Visual Editor (including the transclusion tag).  This is currently working on a test server, and is scheduled for the deployment train Tueseday, Apr 5 (and deployed on group 1 that inlcludes the Wikisources on Apr 6).
+
+@Jdforrester-WMF is planning to turn the configuration switch on April 7.
+
+At that point, Visual Editor will become available as a beta feature on fr.wikisource.org for all content namespaces except Page (that's the next part being worked on now).
+",1459604047,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"> I will be in Jerusalem, and will concentrate on coordinating work on this task while there (as well as hack on it myself).
+Great! I'll be in Jerusalem too and willing to work on it.",1456517911,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"I will be in Jerusalem, and will concentrate on coordinating work on this task while there (as well as hack on it myself).",1456515851,PHID-USER-h75guknmwivm6x37iute,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"IMPORTANT:  **If you are a community developer interested in working on this task:** The [[ https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2016 | Wikimedia Hackathon 2016 ]] (Jerusalem, March 31 - April 3) focuses on #Community-Wishlist-Survey projects. There is some budget for sponsoring volunteer developers. THE DEADLINE TO REQUEST TRAVEL SPONSORSHIP IS TODAY, JANUARY 21. Exceptions can be made for developers focusing on Community Wishlist projects until the end of Sunday 24, but not beyond. If you or someone you know is interested, please [[ https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2016 | REGISTER NOW ]].",1453388008,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,@Jdforrester-WMF are you able to add some guidance here?,1426811015,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"What can we do, as community members, to raise the priority of this? It is **really** important for Wikisource to have the VE active within the Page namespace. It is probably the most needed feature of Wikisource projects, and it would be an important testbed for the VE itself: Wikisource books are heavily formatted, much more than Wikipedia articles. ",1426782168,PHID-USER-jhzyhftzsmppvszocqg2,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"(In reply to comment #2)
+> This data should be in a queryable format. The current format sucks and should
+> be abandoned. If there's not already a bug filed about this, please file one.
+Done (bug 46724). But before doing anything on this direction, a refactoring of the wikitext edition interface is needed because the current system is closely based on this storage format (bug 46578).",1364657586,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"(In reply to comment #0)
+> note 1: structure of the page as save in the database:
+> <noinclude><pagequality level=""LEVEL"" user=""LAST PROOFREADER"" />HEADER<div
+> class=""pagetext"">BODY<noinclude>FOOTER</noinclude>
+
+This data should be in a queryable format. The current format sucks and should be abandoned. If there's not already a bug filed about this, please file one.
+
+(In reply to comment #1)
+> How would we go with looking to put the user into the API?  That information
+> would be useful to present through the 'page information' so it is
+> presentable via 'action=info'.  At the moment one has to pull the page data to
+> get the user info, while the proofread status is already captured. Well that
+> is my limited understanding of the data.
+
+action=info is part of index.php, not api.php. That is, the info action is part of the (graphical) user interface, not part of the MediaWiki API. This bug should just be about a single issue. Adding this type of information to the info action can be a dependent bug of this bug. There may be such a page filed already, maybe.
+
+Basically, once the data is queryable, both the info action and the MediaWiki API modules can pull the data out easily. But that's at least three separate bugs (and probably many more).",1364449830,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"How would we go with looking to put the user into the API?  That information would be useful to present through the 'page information' so it is presentable via 'action=info'.  At the moment one has to pull the page data to get the user info, while the proofread status is already captured. Well that is my limited understanding of the data.",1364377774,PHID-USER-bmenasgfntvftznu6wxs,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Inline comments would be powerful addition to AFT.  It would be something like
+https://en.wikipedia.org/wiki/Stet_%28software%29 integrated into MediaWiki.
+
+I think it would help people make useful comments that could more
+quickly be acted on/resolved.
+
+I realize this would be a large enhancement, but I think it's worth considering at some point in the future.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: http://annotator.wmflabs.org/
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49603",1363903320,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_description,resolved
+Implement inline comment support using OKFN annotator,No reply. Hence closing.,1511275456,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,">>! In T48440#529613, @Parent5446 wrote:
+> https://gerrit.wikimedia.org/r/79839
+> https://gerrit.wikimedia.org/r/78251
+> 
+> Once they are merged, the extension has most of the features implemented. The only thing not implemented is threading, which would be too difficult because OKFN does not natively support it.
+
+>>! In T48440#529622, @Mattflaschen-WMF wrote:
+> Yeah, I consider this complete.
+
+So should this task be closed as resolved? (The item is mentioned on https://www.mediawiki.org/wiki/Outreach_programs/Possible_mentors - that's how I got here)",1504334003,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"If you have open tasks or bugs left, one possibility is to list them at https://www.mediawiki.org/wiki/Google_Code-In and volunteer yourself as mentor.
+
+We have heard from Google and free software projects participating in Code-in that students participating in this programs have done a great work finishing and polishing GSoC projects, many times mentores by the former GSoC student. The key is to be able to split the pending work in little tasks.
+
+More information in the wiki page. If you have questions you can ask there or you can contact me directly.",1382470782,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**tilgovi** wrote:
+
+Nice to see this worked out well!
+
+As for replies, I've got a threading plugin that handles most of this. I'm looking to upstream it for Annotator 2.0.
+
+I'll also take the feedback about not showing annotations immediately into mind. Nothing stops the integrator from overriding the .annotator-hl styles, but something more direct and programmatic might make sense.
+
+Once again, reach out any time in #annotator on freenode or the annotator-dev list and I'll keep watching this bug.",1379459763,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"The GSoC project has the ""Prototyping"" word very visible. Wikimedia requirements for deployment are out of scope. The fact that they are being discussed already now indicates that this prototyping phase seems to be a success. :)
+
+Let's get through the GSoC evaluation and let's talk about further steps after that.",1379455722,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Bug 52156 (history) is also a blocker (to be clear, this is an extra, not part of the required prototype deliverables) to WMF (and probably most third parties) deployment.  It's not strictly UI, but it's definitely user-visible (to experienced users who understand history).",1379454874,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**swalling** wrote:
+
+(In reply to comment #54)
+> Yeah, I consider this complete.  I think we will be able to get those two
+> merged, but I don't think either are hard requirements (though the annotation
+> tab is pretty useful, because otherwise you get annotations everywhere all
+> the
+> time).
+
+I think bug 52064 is the only big UI/UX blocker for actually deploying this to a Wikimedia wiki. Showing annotations by default on every view is likely to annoy folks. 
+
+Otherwise, I think even things like bonafide threading support can be put on hold for later release. Overall, agreed with Matt that this product is nearly done. Very good work for a GSoC project. :)",1379450646,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Yeah, I consider this complete.  I think we will be able to get those two merged, but I don't think either are hard requirements (though the annotation tab is pretty useful, because otherwise you get annotations everywhere all the time).
+
+As Tyler noted, there's not really reply support.  However, if you comment on the same text, it puts the annotation underneath.
+
+The other item that is not implemented (mainly since we did not prioritize it) is including the date.
+
+However, there have been other items implemented that were not listed under Required Deliverables, so I think it balances out.  E.g.
+
+* Update and delete
+* Proper DB setup (including AnnotationRepository for testability), including SQLite support and updates.
+* Logged out user support (under review; Required Deliverables mentions usernames, but not IPs)
+* PHP unit tests (this is the third change under review, which I would like to get merged).",1379449034,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"There are two open patches right now:
+
+https://gerrit.wikimedia.org/r/79839
+https://gerrit.wikimedia.org/r/78251
+
+Once they are merged, the extension has most of the features implemented. The only thing not implemented is threading, which would be too difficult because OKFN does not natively support it.",1379447594,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"GSoC ""soft pencils down"" date was yesterday and all coding must stop on 23 September. Has this project been completed?",1379434950,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #49)
+> Just tried the demo and it works well. Great work Richa and mentors! Just a
+> couple of comments:
+
+Thanks. :)
+
+> - When I edited the page all annotations were gone, I reverted to the
+> previous edition but the annotations didn't reappear.
+
+Yes, handling page changes is one of the trickier things that there may or may not be time for this summer.
+
+However, we do want to fix the issue where the wrong annotations appear when you look at an old version of the page from the history (bug 51728).
+
+> - I assume that these annotations will be displayed in the newly deployed
+> Visual Editor. Would it be possible to update the text anchor as the text is
+> being changed? Annotations in Google Docs have this behaviour, however I am
+> not sure if it would be too complex to mimic that feature.
+
+There is no VE support so far.
+
+> - In the ""recent changes"" page I didn't see any notification of my actions, I
+> understand that it could be meant this way?
+
+We may have time to add logging, but you're right there is no history or logging yet.
+ 
+> And I also loved that you can select several sections of text and create one
+> annotation for all those sections. If the annotation link could be displayed
+> (maybe with a 3rd icon, an anchor displaying the link), that would be a great
+> addition for external websites linking to/highlighting particular fragments,
+> or conversations in the talk page pointing to fragments.
+
+That's a possibility at some point.",1374381107,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #49)
+> Just tried the demo and it works well. Great work Richa and mentors! Just a
+> couple of comments:
+> - When I edited the page all annotations were gone, I reverted to the
+> previous
+> edition but the annotations didn't reappear.
+It looks for annotations for the latest revision since i am using the latest revision id. There is already a bug filed for this https://bugzilla.wikimedia.org/show_bug.cgi?id=51728 .
+> - I assume that these annotations will be displayed in the newly deployed
+> Visual Editor. Would it be possible to update the text anchor as the text is
+> being changed? Annotations in Google Docs have this behaviour, however I am
+> not
+> sure if it would be too complex to mimic that feature.
+> - A minor glitch: when I delete an annotation I get the message ""sorry we
+> could
+> not destroy this annotation"", however the annotation is indeed deleted.
+
+The destroying of annotations is still under review. https://gerrit.wikimedia.org/r/74150 so the annotations are not actually deleted currently.
+> - In the ""recent changes"" page I didn't see any notification of my actions, I
+> understand that it could be meant this way?
+> 
+> And I also loved that you can select several sections of text and create one
+> annotation for all those sections. If the annotation link could be displayed
+> (maybe with a 3rd icon, an anchor displaying the link), that would be a great
+> addition for external websites linking to/highlighting particular fragments,
+> or
+> conversations in the talk page pointing to fragments.
+> 
+> Micru",1374337939,PHID-USER-y3lag4tcfivaet2fsuln,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Just tried the demo and it works well. Great work Richa and mentors! Just a couple of comments:
+- When I edited the page all annotations were gone, I reverted to the previous edition but the annotations didn't reappear.
+- I assume that these annotations will be displayed in the newly deployed Visual Editor. Would it be possible to update the text anchor as the text is being changed? Annotations in Google Docs have this behaviour, however I am not sure if it would be too complex to mimic that feature.
+- A minor glitch: when I delete an annotation I get the message ""sorry we could not destroy this annotation"", however the annotation is indeed deleted.
+- In the ""recent changes"" page I didn't see any notification of my actions, I understand that it could be meant this way?
+
+And I also loved that you can select several sections of text and create one annotation for all those sections. If the annotation link could be displayed (maybe with a 3rd icon, an anchor displaying the link), that would be a great addition for external websites linking to/highlighting particular fragments, or conversations in the talk page pointing to fragments.
+
+Micru",1374323153,PHID-USER-my5s6nat437le6q5fq7d,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"You can now also use the simpler URL, http://annotator.wmflabs.org",1374301337,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"There is now a test wiki for this, http://annotator.instance-proxy.wmflabs.org/ .  If you're interested in testing it, create an account, then try annotating http://annotator.instance-proxy.wmflabs.org/wiki/Lorem_ipsum .
+
+Currently, you must be logged in, both to see annotations and to make them (bug 51722).",1374299983,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"We've made a Bugzilla component.  This will still be the main bug, tracking the initial key functionality.",1374286335,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**nick** wrote:
+
+That GitHub compare url has the sense of the comparison the wrong way round: http://github.com/okfn/annotator/compare/master...wip",1374046255,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**nick** wrote:
+
+(In reply to comment #43)
+
+Hi all,
+
+Sorry not to have weighed in earlier. I'm really glad to see you're using Annotator, and hope I can help out with any problems you might have.
+
+> I'm a little unclear about the relationship of 'read' and 'index', and how
+> the URLs work.
+
+Yes, this is a bit messy. Read and index are implicitly the same endpoint at the moment, and index is just ""read"" with a null ID. Obviously this is horrible, but it turns out that it doesn't matter that much as an index endpoint that returns all annotations is almost never useful anyway, so...
+
+> It seems like this may be a moot point if we use loadFromSearch.  However, I
+> would expect there to be an 'index' url for consistency.
+
+...the vast majority of real implementations use loadFromSearch. If you're interested, current work in progress on Annotator 1.3/2.0 (http://github.com/okfn/annotator/compare/wip...master) is revisiting some of this stuff, and the four endpoints that need implementing by a store are now create/update/delete/query, and the index endpoint is gone.
+
+But, to answer your concrete question: use loadFromSearch and ignore the existence of the ""index"" endpoint.",1374046180,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"I was wondering if someone from the OKFN team could answer a couple quick questions.
+
+I'm a little unclear about the relationship of 'read' and 'index', and how the URLs work.
+
+https://github.com/okfn/annotator/wiki/Storage#index says index returns ""a list of all annotation objects"".  First, I'm wondering if that is supposed to be limited to the current page's annotations.  Maybe that's up to us.
+
+However, the plugin docs (https://github.com/okfn/annotator/wiki/Store-Plugin) have no mention of index, nor do I see a way to override the URL.
+
+https://github.com/okfn/annotator/wiki/Storage#read says it's a straight-forward method that takes an ID and returns a single annotation.
+
+But the plugin docs (Store-Plugin) say, ""read: GETs all annotations. Called when plugin loads or .loadAnnotations() is called. Server should return an array of annotations serialised as JSON.""
+
+Looking at the Coffee code, it seems read is called to get a list, but never explicitly called for a single annotation (although there is a commented out line doing that).  However, since we're using the recommended 303 redirect, it's implicitly used for creations.
+
+The list part is confirmed by testing.  It loads http://127.0.0.1:9090/w/api.php?action=annotator-read&id=:id, which is a bit weird.  I think this is related to https://github.com/okfn/annotator/issues/186
+
+It seems like this may be a moot point if we use loadFromSearch.  However, I would expect there to be an 'index' url for consistency.",1373666058,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"See also:
+* [[Wikipedia:Village_pump_(idea_lab)/Archive_3#Sticky_Notes_for_Easier_Editing]]
+* [[Wikipedia:Sticky notes]]",1372611691,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**tilgovi** wrote:
+
+We're right here watching, Rob :)
+
+I would recommend just focusing on upstream okfn/annotator. We're cranking hard to get everything relevant pushed upstream.
+
+Richa, don't hesitate to reach out if you want help testing or have any questions about the annotator code.",1372372816,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**azaroth42** wrote:
+
+
+Just to recommend the hypothes.is version of annotator, and to point to the Open Annotation specification for the implementation:
+
+http://www.openannotation.org/spec/core/
+
+and 
+
+http://www.w3.org/community/openannotation/
+
+Hope that helps, and looking forwards to seeing the outcomes. Happy to answer any Open Annotation questions that may come up!",1372368533,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Gerrit is ready and all my github changes are imported. 
+https://git.wikimedia.org/log/mediawiki%2Fextensions%2FAnnotator.git
+The basic skeleton of where to call the annotations is ready. Now i am starting with the storage of comments. Here are some of my points:
+1. Going through the idea of custom table implementation and storing comments in a separate table which takes account of the revision id, user and the range.
+2. Creating classes 'create', 'update', 'read', 'delete' for annotations. https://github.com/okfn/annotator/wiki/store-plugin#urls
+3. Modify the above urls of OKFN as:
+prefix: 'api.php'
+create: '?action=create', etc.",1371452038,PHID-USER-y3lag4tcfivaet2fsuln,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,Just a note that i have made a repo on github https://github.com/richajain/Prototyping-inline-comments and have done some initial commits. I will be updating this with the progress done at regular time.,1370539929,PHID-USER-y3lag4tcfivaet2fsuln,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**tilgovi** wrote:
+
+Just popping in to subscribe to CC on this. I'm actively maintaining and improving Annotator for Hypothes.is and am happy to answer any questions or work with you all to close any gaps we need to in order to store annotations in mediawiki.",1369945974,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #35)
+> I saw they allow overriding the URL syntax
+> (https://github.com/okfn/annotator/wiki/Store-Plugin#urls), so the main
+> concern
+> is probably less used methods like PUT and DELETE, which needs investigation
+> on
+> both sides (OKFN and MW).
+
+AFAIK, if you submit a PUT/DELETE request to the API, it will probably just treat it as a GET request, although I could be wrong and have not tested this.",1369942866,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #33)
+> (In reply to comment #32)
+> > Someone may have made a RESTful wrapper of a MW API, or have advice on doing
+> > so.
+> 
+> I sure hope this exists. The API interface is terrible right now.
+
+I saw they allow overriding the URL syntax (https://github.com/okfn/annotator/wiki/Store-Plugin#urls), so the main concern is probably less used methods like PUT and DELETE, which needs investigation on both sides (OKFN and MW).",1369942576,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"From Matt's email:
+> The high-level concept of RevisionDelete applies, but I don't think
+> directly using it is a good fit.  What happens if one comment on a page
+> is a violation, but the next consecutive 999 are fine?  With RevDel, I
+> think you'd have to remove the bad one, then suppress all 1000 (correct
+> me if I'm wrong) containing the bad one, leaving no history of how the
+> good 999 developed.
+
+I was thinking one page per comment.
+
+> True, but there's existing code (the main one I'm thinking of is AFTv5)
+> to learn from.  Another reason not to use a page is that it constrains
+> changes.  Once we publish the JSON page, there could be bots that rely
+> on it, rather than the API.  If we just use JSON internally, that gives
+> us flexibility.
+
+If we use pages, we could still use JSON only internally. We'd implement a new Content type for annotations and still provide an API module for accessing comments.
+
+All that said, I understand the concern with using articles as a storage medium, so I would be fine with either way. I just wanted to make sure we weren't ditching the idea without due consideration.",1369942104,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #32)
+> Someone may have made a RESTful wrapper of a MW API, or have advice on doing
+> so.
+
+I sure hope this exists. The API interface is terrible right now.",1369936634,PHID-USER-ea6gwat27oulytc5tvsy,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Richa Jain has been accepted for Google Summer of Code for this project.  She is currently investigating OKFN and the store plugin.  The below are some thoughts as a starting point:
+
+OKFN provides documentation on writing a plugin for storing annotations (https://github.com/okfn/annotator/wiki/Store-Plugin)?  The most straightforward approach seems to be implementing that as a MW extension.
+
+https://github.com/okfn/annotator-store is an example of how one store works, though of course the MW extension example will be different.
+
+One issue is that the API is RESTful.  It lets you set a custom prefix, but the syntax is a little different than MW normally uses.  
+
+One way to do this is to make a normal MW-style API subclass (like https://www.mediawiki.org/wiki/API:Extensions#Creating_API_modules_in_extensions), then hook into the URL routing code to translate the OKFN-style RESTful URLs to calls to the API.
+
+Someone may have made a RESTful wrapper of a MW API, or have advice on doing so.  It's probably also worth looking at the hooks (https://www.mediawiki.org/wiki/Manual:Hooks)",1369893630,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+(In reply to comment #30)
+going by the description, it perfectly fits the bill! I mean it has all the methods of firefox available in IE. But the documentation is really very poor man. Its going to take me a while to make heads and tails of this :(",1369104663,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #29)
+> going a little off topic here, I think internet explorer cannot be supported
+> in any efficient way, cause of the way text ranges are implemented in it. 
+> 
+> Both ofkn and pundit are not supported in IE. I ve been going through the
+> code of OFKN for a while now and this dawned upon me just now.
+
+In the VisualEditor project we have similar needs for cross-browser range selection and manipulation, and we have used the Rangy library - https://code.google.com/p/rangy/ - which has worked out well for us. Not sure if this is helpful for you?",1369060957,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+going a little off topic here, I think internet explorer cannot be supported in any efficient way, cause of the way text ranges are implemented in it. 
+
+Both ofkn and pundit are not supported in IE. I ve been going through the code of OFKN for a while now and this dawned upon me just now.",1369002502,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Another tool for inspiration? http://www.thepund.it/
+
+Java backend but ""The Pundit client is a Javascript application based on the Dojo Toolkit http://dojotoolkit.org/ . It works closely with the Pundit server API, allowing the end-user to annotate any kind of web contents.""
+
+Apparently related with Europeana and funded by the EU. Sounds like open source but after a very few clicks couldn't find sources (busy day etc).",1367946207,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,Just a note to say that Anthony Chen has submitted a GSoC proposal related to this project: https://www.mediawiki.org/wiki/User:N3c/GSoC_Proposal,1367618047,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+I seem to have butt into the conversation .. I didn't read the comments yet. 
+Apologizes .. 
+
+Anyways keeping with the conversation, since you guys are discussing interfaces, please checkout my prototype
+
+http://adityasastry.in.cp-2.webhostbox.net/index.php?title=Special:BlankPage
+
+Instead of the in-page along with article display, I would propose a movable popout as the readability might suffer when you try to squeeze in the comments interface into the article.",1367180341,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #23)
+> Hey,
+> My name is Aditya and am interested in pursuing this as my GSOC project.
+
+Thank you for your interest.
+
+> Implementing this for some other theme is very easy. We just need to add a
+> DIV in the theme's php file.
+
+Note that this is being proposed as an extension.  Thus, you should not need to modify the core skin definition.",1367162727,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+
+2)Databases
+Allow me to make a very bold statement here that  json/xml are ill suited for a project of this nature.
+Justification:
+1) There are many helper classes already written for MediaWiki like sanitizer class(which depends on the databases) load balancer class(Incase one wants to distribute the comments data) and few other classes which implement functionality which is critically needed. Incase one wants to go the XML/JSON way one needs to implement them as well.
+
+2) Maintenance will become an issue.
+
+3)When migrating between hosts one needs to manually select the xml/json files and move them around. MYSQL supports one click export and import functionality for all the tables.
+
+I will be making a prototype for databases as well in a couple of days.
+And here's my idea. Each article is stored as a WikiText string, so as illustrated by my UI the selected text's starting and ending indexes are caught and the article page name is also caught. These three attributes will be used as indexes into a table ""Comments"" 
+
+When parsing this wikitext, based on the starting and ending indexes the text will be marked and a link will be provided next to it to access the comments as I have shown.
+
+I will be implementing this functionality by tuesday. But for the sake of proposal I will be not using any of the MediaWiki classes for now so you people could test drive it once and based on your feedback I will be making ammendments to my proposal, so please review my work so far :)",1367141303,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+Hey,
+My name is Aditya and am interested in pursuing this as my GSOC project.
+
+After going through the requirements, leaving apart any additional features required. I have outlined two major aspects of this project.
+
+1) Designing the UI.
+2) Designing the database.
+
+I just want to present my perspective on these two things before I start drafting my proposal. I want to hear your opinion on this.
+
+1)UI
+When it comes to designing the UI. I think it will be better if we go with a custom build rather than using a ready-made component, cause MediaWiki uses themes and each component should match the theme and a ready made component leaves very little margin for customization ( in-case its a opensource component, then it might as well be modified, but the person designing the theme need to be not only versed with the code of the MediaWiki but as well as the source code of the component, hence I believe a ready made component would constrain the customizability of MediaWiki.
+
+http://adityasastry.in.cp-2.webhostbox.net/index.php?title=Special:BlankPage
+This is a UI mockup I came up with. Its a prototype for a prototype :P I have made an implementation of this for VECTOR theme, but I have placed the CSS and JS for this in the common skins shared.css and the JS in vector.js as of for now.
+Implementing this for some other theme is very easy. We just need to add a DIV in the theme's php file.",1367140627,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Just a note to say that Richa Jain has submitted a GSoC / OPW proposal related to this report:
+
+https://www.mediawiki.org/wiki/User:Rjain/Proposal-Prototyping-inline-comments
+
+There is another student that has submitted a proposal. I will announce it here as soon as there is a public URL.",1366901402,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Slightly related: http://homes.cs.washington.edu/~travis/reflect/
+
+With old MediaWiki extension code available: http://www.mediawiki.org/wiki/Extension:Reflect
+
+Depends on LiquidThreads, so I don't expect many possibilities of reuse as-is but perhaps you want to have a look.",1366507980,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #19)
+> http://okfnlabs.org/annotator/ is maybe (with some adaptations) a relevant
+> option.
+
+Also http://hypothes.is (they seem to build on top of okf's annotator: https://github.com/hypothesis/h#development)",1365784493,PHID-USER-uazrhtptdqudzoqfefsc,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,http://okfnlabs.org/annotator/ is maybe (with some adaptations) a relevant option.,1365528421,PHID-USER-5paybpgtxjrhikdos3p5,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"This is the end result we are after:
+
+Wikipages optionally looking like this (famous examples picked for reference only):
+
+http://gplv3.fsf.org/comments/lgpl-draft-1.html (few comments)
+
+http://gplv3.fsf.org/comments/gplv3-draft-2.html (really busy)
+
+
+That view would include the possibility to add comments. There is a sandbox to play without registration at
+
+http://www.co-ment.com/see/
+
+And a lite version at https://lite.co-ment.com/
+
+
+PS: group permissions to be taken into account? Maybe not in a prototype for a GSOC student but I can imagine that the same levels of protection (open, registered users, autoconfirmed...) would be desired. For Wikimedia wikis I would require login, a nice reason to register. But this is going too far...  :)
+
+Also, spam check? Posting external URLs possible or not? Well, this can be endless and again we should define the scope for a GSOC prototype.",1364319150,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"From where I'm coming from, it has nothing to do with the first option (HTML comments/warnings to editors).
+
+It is meant as a collaboration tool, essentially your second option.  I don't see it as a replacement for long free-form discussion (""this article needs more reliable sources...""/""it has an undue weight is the following areas""...), but a targeted form of collaboration around small areas of the article, like co-ment.
+
+I agree a first pass (on MediaWiki.org, etc.) would be useful regardless, even if not all the code could necessarily be integrated into the permanent solution.  It would allow trying out implementations and UI ideas.
+
+I agree it would probably have to be one interface at first (and maybe ever), and VisualEditor/Parsoid probably makes more sense.
+
+There would probably have to be limited threading, but flat (these people commented on this excerpt in this chronological order) would probably be sufficient.  If it gets too elaborate, talk it to the talk page/Flow.
+
+To keep it concise, I would suggest just the username and date (perhaps auto-formatted to e.g. ""3 hours ago"" for recent comments), rather than a signature.  I suggest it should show IPs for anons.
+
+I'm not envisioning using LQT, since it seems like if we want to integrate at some point, Flow would be a better candidate.
+
+It would be most useful attached to pages, automatically invalidating a comment when an excerpt is altered.  But ""attached to revision"" is probably more realistic for the first implementation.",1364318830,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"So, to my mind there are two options here, and I can't quite understand which is being discussed (it appears both):
+
+* Is this about surfacing to the editors in some nice way post-VisualEditor roll-out the existing comments for editors - I.e. ""<!-- PLEASE DO NOT CHANGE OBAMA'S NAME -->"" at the top of the Barack Obama article on enwiki? If so, great, and this should probably be moved to the VisualEditor product space. This is definitely needed for VE, but I worry that the scope for functionality is not huge, and it might be limiting.
+
+* Is this about building an additional persistent/semi-persistent un-threaded/semi-threaded discussion space on top of pages/revisions(?) like Co-ment and Google Docs? If so, that sounds fun, and something that we're also looking at building for VisualEditor (as part of the real-time collaboration system, potentially), but I wouldn't want us to get in the way of someone building a first pass for GSoC. Doing this for both VE and wikitext at the same would be a really hard UI challenge (they're very different interface concepts), so perhaps limiting it to just one of them for now? Also, there needs to be a really serious discussion about how this would work from a product perspective (threading? how much? how signed? using LQT? why not? where stored? attached to revisions? To pages? to sections of said revision/page? how? etc.) lest it become mammoth. OTOH, this would be very cool as well.
+
+Apologies for the confusion on my part. :-)",1364317551,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"I've linked this bug from https://www.mediawiki.org/w/index.php?title=Feature_map&diff=663816&oldid=566850 where the FSF feature was reported.
+
+(In reply to comment #11)
+> Are all annotations willing the be seen publicly by default? We won't go for
+> private annotations, but maybe people want to have notes-to-self? Like ToDo
+> post-its for editors, or notes for students preparing their school work.
+
+Looks outside the scope of the request. It's indeed the sort of thing the word ""annotation"" is usually used for, so let's not call this proposal ""annotations"" maybe?",1364283676,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"More context:
+
+Commons has annotations in images:
+http://commons.wikimedia.org/wiki/Commons:Image_annotations
+
+Munaf mentioned annotations at
+http://www.mediawiki.org/wiki/Micro_Design_Improvements#Annotations",1364279754,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"James Forrester has indicated that this may be within the scope of VisualEditor, and that he would be receptive to the feature being implemented as part of GSOC.  I've CCed him.",1364277673,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"To follow up, I have decided to act as mentor should the project be selected.
+
+I think annotation is a valid term, although comment is also commonly used (e.g. LibreOffice, Google Docs).  co-ment seems to use both terms.
+
+There should probably be some kind of permalink that shows the comment, but initially that might just be a link to the revision (especially if comments aren't preserved on edit in the first implementation).
+
+I don't think they should be shown to readers by default.  It would have to be a toggle of some kind.  It would be nice to make this available in VisualEditor mode (either just that, or both).
+
+The notes to self idea needs further thought.  I see the primary use of the extension as collaborative work, but then again people do use userpage for drafts too.
+
+If this project moves forward, we may want to continue speccing it out on mediawiki.org.",1364276995,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"A bit of context and braindumping:
+
+http://openannotation.org/
+http://www.openannotation.org/wiki/index.php/Web_Page_Clients_List
+
+Maybe ""annotations"" is the label we are looking for? Wikipedia articles are not scholarship texts, and inline comments won't be scholrship annotations. Then again... aren't they structurally the same? Point to a specific portion of text and connect a comment, a signature, a timestamp, maybe a link.
+
+Another aspect is My Annotations, as part of My Contributions.
+
+I guess annotations will need a unique deeplink? 
+
+And do we get those annotations by default, or should users activate an ""Annotated view""? Maybe the latter, it looks like too much extra bytes and clutter for the majority of people interested in the first paragraph and some factoids.
+
+Bonus:
+Are all annotations willing the be seen publicly by default? We won't go for private annotations, but maybe people want to have notes-to-self? Like ToDo post-its for editors, or notes for students preparing their school work. Those would be as public as our User pages: public for those knowing where to look but out of default searches / views.",1364271952,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"This feature request is being considered for 
+
+https://www.mediawiki.org/wiki/Summer_of_Code_2013#Project_ideas
+
+Question: is there a potential mentor willing to help potential students interested in this project?",1364081939,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,This sounds much more like a separate extension than an enhancement to ArticleFeedback.,1363987812,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Such articles tend to be protected on some level, though, and the same reasons would probably have to apply to this as well.",1363911693,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #4)
+> But why would that many people be commenting on the same thing?
+
+Think of a controversial article that asserted a true, verifiable, but controversial fact.  It would probably perennially attract comments to the sentence stating the fact.  So at the very least there would have to be easy filtering/mark as resolved/mark as rejected.
+
+I agree it doesn't *have* to be Wikipedia-scalable, but it's certainly far more useful if it is.
+
+Note, implementers should also consider looking at the co-ment code.",1363911476,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Right, I guess my point was just that wikipedia is not as extreme as folks often make out, sorry. If the thing is well-engineered and scales properly it should work for everyone, which would be perfect.",1363910784,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"If it's not the problem, all the better. I'm just saying that we shouldn't hamper this potential GSOC project with Wikipedia-centric issues if they are not issues for the 98% of MediaWikis out there.",1363910387,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #3)
+> Then again it is not a trivial project at all. If we propose this we should
+> put
+> apart key aspects of Wikipedia like 5.000 editors commented on the same
+> sentence, performance issues, scalability... Perhaps the project could
+> consist
+> in recycling as much stet code as possible and plug it to a MediaWiki
+> backend.
+
+But why would that many people be commenting on the same thing? There are only so many parts of an article worth commenting on, and only so many points to be made, and a flat out discussion would belong on a talkpage (or equivalent), not in the comments themselves.
+
+As it is people tend to distribute what they work on and edit. Yes, many, many people edit wikipedia and such, and a lot of people may edit the same article, but it doesn't happen all at once. Comments, even if they do span multiple revisions, will only span so many before they cease to apply.
+
+Just look at gerrit as a tiny example - plenty of folks comment on plenty of things, but I've rarely seen more than one or two people comment inline on any one patchset. It's only useful for so many things, and once someone made a point there's no use making it again.",1363909988,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Regadless of Wikipedia & Wikimedia plans, this looks like an extension that would be useful and welcomed in other MediaWikis out there. Well, I know that in the GPLv3 drafting times I really wanted to have that in the MediaWiki based project we were running...
+
+Then again it is not a trivial project at all. If we propose this we should put apart key aspects of Wikipedia like 5.000 editors commented on the same sentence, performance issues, scalability... Perhaps the project could consist in recycling as much stet code as possible and plug it to a MediaWiki backend.",1363909447,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"See http://lists.wikimedia.org/pipermail/ee/2013-March/000263.html (beginning of thread), in particular http://lists.wikimedia.org/pipermail/ee/2013-March/000276.html (about some of the UI/UX challenges).
+
+The AFT team is not planning on implementing this, at least for the time being.
+
+It is a candidate for a Google Summer of Code Project (mentioned at https://www.mediawiki.org/wiki/Talk:Summer_of_Code_2013#List_of_project_ideas_25327), among other possibilities.",1363906883,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,This could also potentially be done as a separate extension.,1363903597,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"Various users find them inappropriate in #mediawiki because it is a support channel, not as much a developer discussion channel (#wikimedia-dev).
+
+Whether to move them there or to a dedicated channel isn't clear yet.
+
+See discussions on bug 46282 and bug 46144.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1363699500,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b7iac2xw43i4wyam3nwq,task_description,resolved
+Move wikibugs and gerrit-wm out of #mediawiki,https://github.com/valhallasw/pywikibugs is the source for people who want to make modifications.,1398601535,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"Wikibugs is dead, pywikibugs reports to #wikimedia-dev.",1398197924,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"(In reply to Krinkle from comment #11)
+> Re-opened since bug 46144 is still unresolved.
+
+You didn't re-open this bug. It's now a tracking bug that's marked resolved/fixed with an open dependency. Hrm.",1393636938,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,Re-opened since bug 46144 is still unresolved.,1366375213,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"06.45 -!- Nemo_bis changed the topic of #wikimedia-dev to: MediaWiki and Wikimedia software development | Support: #mediawiki | Technical help for Wikimedia wikis: #wikimedia-tech | Wikimedia operations: #wikimedia-operations
+
+It used to be ""Developers' talk about WMF's #mediawiki projects"" or very similar ones (the key being WMF) since the beginning of time (creation as -usability).",1366174392,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"https://gerrit.wikimedia.org/r/#/c/57752/ , https://gerrit.wikimedia.org/r/#/c/57753/ merged.
+
+00.31 -!- gerrit-wm [~gerrit-wm@manganese.wikimedia.org] has quit [Remote host closed the connection]
+00.32 < mutante> bot is moving per merged changes
+00.32 < James_F> Yup. :-)
+00.32 < James_F> (Yay.)
+
+(CEST)",1366172907,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,Related URL: https://gerrit.wikimedia.org/r/58661 (Gerrit Change I588f2eba8fba9603f33386e54e90c03e2bb5f5f0),1365657530,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"(In reply to comment #6)
+> Ori submitted I10a02bfe to get this done when there is approval.
+
+I'd say, why can't we do both? Lets first move it out of #mediawiki. That is something we all agree upon.
+
+We'll keep it in regular talk channels for now (#wikimedia-dev).
+
+If we believe that it is disturbing even in a developer-oriented channel (which I'm sure it won't) then we can choose to create a separate channel, but going all the way at once is unnecessary and only creates more chaos.",1365475852,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,Ori submitted I10a02bfe to get this done when there is approval.,1365203853,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"I wrote this before: Could we move this debate to its target audience somehow, as I'm afraid that it won't be seen in this Bugzilla report?
+I understand that's hard for IRC, but maybe a generic mailing list or RFC? 
+I don't see much sense battling here.",1363769474,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"(In reply to comment #3)
+> #wikimedia-dev is not Wikimedia deployment specific development. It is
+> development of software used by Wikimedia, which all of MediaWiki is
+> obviously part of at least as long as either MediaWiki is a Wikimedia
+> Foundation project and Wikipedia.org runs on MediaWiki. Regardless of
+> whether our staff maintains it or not.
+
+This is insane. Are you hearing yourself?
+
+>> I'd much prefer #mediawiki-feeds.
+> 
+> For what reason? Because you don't want to see it in channels that you're in?
+
+Because it's the least bad option (other than keeping the bots in #mediawiki).
+
+> In that case we move it out of channels not meant for developers only
+> (#mediawiki) and into #wikimedia-dev where it is reasonable to ask you to use
+> /ignore if you don't like it.
+
+This doesn't make any sense. What's accomplished here?
+
+> If you do find them useful, then how are they useful in a separate channel?
+> You'd have to manually check up there to see for anything. I don't think that
+> works well in practice. The whole idea of being exposed to other people's
+> activities casually (without actively looking for it) wouldn't exist anymore
+> then I believe.
+
+That's a reason to either keep the bots in #mediawiki or not. Moving them to a separate discussion channel solves nothing.
+
+> Besides, what about the channels for operations, visualeditor, parsoid,
+> mobile.
+> They all have bots related to their activities, because it makes sense to
+> have it in the same channel so you're exposed to each others activities and
+> can jump into things when they come by. Separating it out is
+> counter-intuitive.
+
+What about them? You're the one conflating gerrit-wm and wikibugs and then complaining about the two being conflated. wikibugs is only in #mediawiki and was the subject of its own discussion before you created this bug. gerrit-wm is in multiple channels already and serves a different purpose from wikibugs.",1363752509,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"(In reply to comment #2)
+> I don't think #wikimedia-dev should exist.
+> Moving MediaWiki development bots to a Wikimedia channel is pretty wrong.
+> 
+
+#wikimedia-dev is not Wikimedia deployment specific development. It is development of software used by Wikimedia, which all of MediaWiki is obviously part of at least as long as either MediaWiki is a Wikimedia Foundation project and Wikipedia.org runs on MediaWiki. Regardless of whether our staff maintains it or not.
+
+#wikimedia-dev should exist by all means, it isn't specific but broad. Perhaps too broad, but that's why we have specific channels for teams that prefer their own area:
+- operations, visualeditor, parsoid, mobile, i18n.
+
+A #mediawiki-dev could exist leaving #wikimedia-dev with only non-MediaWiki related dev stuff, but that would be rather narrow. There is no justification to split it up right now I think. It isn't too crowded and splitting it up would go at the cost of more decentralisation and less integrated communication.
+
+> I'd much prefer #mediawiki-feeds.
+
+For what reason? Because you don't want to see it in channels that you're in?
+
+In that case we move it out of channels not meant for developers only (#mediawiki) and into #wikimedia-dev where it is reasonable to ask you to use /ignore if you don't like it.
+
+If you do find them useful, then how are they useful in a separate channel? You'd have to manually check up there to see for anything. I don't think that works well in practice. The whole idea of being exposed to other people's activities casually (without actively looking for it) wouldn't exist anymore then I believe.
+
+Besides, what about the channels for operations, visualeditor, parsoid, mobile. They all have bots related to their activities, because it makes sense to have it in the same channel so you're exposed to each others activities and can jump into things when they come by. Separating it out is counter-intuitive.",1363709152,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"I don't think #wikimedia-dev should exist.
+
+Moving MediaWiki development bots to a Wikimedia channel is pretty wrong. I'd much prefer #mediawiki-feeds.",1363707120,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"Aggregating various arguments that apply generally to moving them out (as opposed to moving any specific bot):
+
+(Quote bug 46282 comment #0)
+> The only times I've found it useful is when I was live reviewing and wanted
+> to point someone to a change/comment I made.
+
+(Quote bug 46282 comment #1)
+> Use /ignore in your favorite IRC client. Works well.
+
+(Quote bug 46282 comment #2)
+> I disagree with ""it's completely useless"", but in this case, when someone
+> knows he is going to spam the channel and has op on #mediawiki, he should
+> have quieted [the bot] before sending all those changes.
+
+(Quote bug 46282 comment #6)
+> We're going to move both. Need puppet changes.
+
+
+(Quote bug 46144 comment 5)
+> We actively had a user saying ""This channel obviously isn't for support...two
+> pages of scrollback and I've spotted 2 real people."" This is a bad thing,
+> contrary to what you may think.
+> 
+> We've had *contributors* complaining about the bot(s) for the past couple of
+> months/years.
+> 
+> I really don't think two/three people saying ""I LIKE THE BOT IN #MEDIAWIKI SO
+> LEAVE IT THE HELL ALONE"" trumps the wider problems here...that the bot
+> *needs*
+> to go.
+
+(Quote bug 46144 comment 8)
+> Lets take this the mailing list again...
+> 
+> (But my two cents)
+> If we kick any single bot, Gerrit produces a-lot more cruft lately than
+> wikibugs... I, as having pointed out would prefer them all in a separate
+> channel that is moderated and only the bots are voiced.
+
+(Quote bug 46144 comment 19)
+> (Quote bug 46144 comment 18)
+> > That's not a valid reason, imho. We need a way to tone down what it reports,
+> > if
+> > it's going to stay...the rate of bug reporting & commenting is many times
+> > greater than it once was. It's definitely gotten noisier over the years,
+> > which
+> > has reduced its utility.
+> 
+> Reduced it's utility -> in the main support channel. The bot *is* useful, I
+> just think it drowns out conversation these days.
+
+(Quote bug 46144 comment 26)
+> What about moving them to #wikimedia-dev instead of #mediawiki?
+> 
+> I think most (actively involved) developers that are on IRC aren't disturbed
+> by
+> the feed. If they really must they're experienced enough to not be afraid of
+> a
+> simple /ignore.
+> 
+> Though I speak only for myself, I believe those that do want the feed, would
+> prefer it to be in context of regular conversation, not in a separate
+> channel.
+> 
+> It's where random bits of interesting things come by from (e.g. discussing a
+> change, proposing and and then someone does it or files a bug about it).
+> 
+> It doesn't work when in a separate channel.
+> 
+> See also #mediawiki-parsoid, #mediawiki-visualeditor, #wikimedia-operations,
+> #wikimedia-mobile etc. (and same for third parties such as #jquery-dev and
+> webkit).
+> 
+> The problem is mainly with #mediawiki being a support channel instead of dev
+> channel, not with having notifications in a human-occupied irc channel in
+> general.",1363699938,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"wikibugs has gone missing from #mediawiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://www.mediawiki.org/wiki/Git/IRC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=28402",1363319760,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hd4snxw47ckt4oowe3xb,task_description,resolved
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #31)
+> @Nemo, this bug is about wikibugs. Though some related change has been
+> merged,
+> wikibugs is not yet run from puppet so that change is irrelevant until that
+> is
+> activated.
+
+Current status is also discussed in https://gerrit.wikimedia.org/r/#/c/54984",1381952272,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"As this came up in the IRC office hour today, wondering whether to go via an RFC for this.",1373991340,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #39)
+> Whose blood do I sacrifice to have this happen?
+
+How about this, instead:
+
+(In reply to comment #21)
+> We could schedule an IRC meeting, announce it ia wikitech-l mailing list, and
+> tally votes/opinions on a wiki page.",1371792126,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #40)
+> Chad's?
+
+No, not me. I tried to move it out of #mediawiki, but people yelled at me. I don't care about this bot anymore.
+
+Removing myself from CC.",1371783597,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Chad's?,1371778738,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Whose blood do I sacrifice to have this happen?,1371739659,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,(Updating summary to make it easier to search this bug),1367252699,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Sooo... it's still in #mediawiki, and not in #wikimedia-dev. Does it need additional poking?
+
+[Personally I prefer the bots in #mediawiki, but it sounds like I've lost this fight. :)]",1367252671,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"sorry, one last time",1366673117,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,..,1366671790,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"test - wikibugs bot, please report in new channel, after having to kill concurrent bot instances started by old script",1366670542,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,moved to #wikimedia-dev,1366670045,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #31)
+> @Nemo, this bug is about wikibugs. Though some related change has been
+> merged, wikibugs is not yet run from puppet so that change is irrelevant
+> until that is activated. wikibugs is still in #mediawiki. Reopening.
+
+At the time the bug was closed, #mediawiki was blessèdly-free of bots. :-)",1366381582,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"@Nemo, this bug is about wikibugs. Though some related change has been merged, wikibugs is not yet run from puppet so that change is irrelevant until that is activated. wikibugs is still in #mediawiki. Reopening.",1366375128,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"https://gerrit.wikimedia.org/r/#/c/57752/ , https://gerrit.wikimedia.org/r/#/c/57753/ merged.
+
+00.31 -!- gerrit-wm [~gerrit-wm@manganese.wikimedia.org] has quit [Remote host closed the connection]
+00.32 < mutante> bot is moving per merged changes
+00.32 < James_F> Yup. :-)
+00.32 < James_F> (Yay.)
+
+(CEST)",1366172918,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Note that wikibugs is now 30 % less chatty, as bug 28402 was fixed (bug 28402 comment 8). It would maybe deserve a second chance. :)",1365658133,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Related URL: https://gerrit.wikimedia.org/r/58661 (Gerrit Change I588f2eba8fba9603f33386e54e90c03e2bb5f5f0),1365657518,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Ori submitted I10a02bfe to get this done when there is approval.,1365203841,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"What about moving them to #wikimedia-dev instead of #mediawiki?
+
+I think most (actively involved) developers that are on IRC aren't disturbed by the feed. If they really must they're experienced enough to not be afraid of a simple /ignore.
+
+Though I speak only for myself, I believe those that do want the feed, would prefer it to be in context of regular conversation, not in a separate channel.
+
+It's where random bits of interesting things come by from (e.g. discussing a change, proposing and and then someone does it or files a bug about it).
+
+It doesn't work when in a separate channel.
+
+See also #mediawiki-parsoid, #mediawiki-visualeditor, #wikimedia-operations, #wikimedia-mobile etc. (and same for third parties such as #jquery-dev and webkit).
+
+The problem is mainly with #mediawiki being a support channel instead of dev channel, not with having notifications in a human-occupied irc channel in general.",1363699186,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"de duping title, These are two issues that really should be discussed separately.",1363699112,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,*** Bug 46282 has been marked as a duplicate of this bug. ***,1363698855,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #22)
+> Right
+> now, wikibugs is reporting CC changes, when it used to not report those.
+
+This is what I just linked: bug 28402 aka bug 43130, which has a patch that someone needs to commit/review.",1363626815,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #18)
+> That's not a valid reason, imho. We need a way to tone down what it reports,
+> if it's going to stay...the rate of bug reporting & commenting is many times
+> greater than it once was. It's definitely gotten noisier over the years,
+> which has reduced its utility.
+
+I believe I already said as much somewhere around here, but wikibugs _is_ producing more noise lately, as it was broken by the recent Bugzilla upgrade and nobody has fixed it (or deployed the fixes to it, I can't remember). Right now, wikibugs is reporting CC changes, when it used to not report those.",1363626526,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"We could schedule an IRC meeting, announce it ia wikitech-l mailing list, and tally votes/opinions on a wiki page.",1363618310,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Could we move this debate to its target audience somehow, as I'm afraid that it won't be seen in this Bugzilla report? 
+I understand that's hard for IRC, but maybe a generic mailing list or RFC?",1363618174,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #18)
+> That's not a valid reason, imho. We need a way to tone down what it reports,
+> if
+> it's going to stay...the rate of bug reporting & commenting is many times
+> greater than it once was. It's definitely gotten noisier over the years,
+> which
+> has reduced its utility.
+
+Reduced it's utility -> in the main support channel. The bot *is* useful, I just think it drowns out conversation these days.",1363617531,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"That's not a valid reason, imho. We need a way to tone down what it reports, if it's going to stay...the rate of bug reporting & commenting is many times greater than it once was. It's definitely gotten noisier over the years, which has reduced its utility.",1363617489,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Bumping importance back down; wikibugs belongs on #mediawiki as it's always been. Recommend WONTFIX.,1363617399,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Upping priority, adjusting summary, reopening.",1363617125,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"I've created bug 46282 about kicking gerrit-wm instead, per myself & p858snake.",1363616978,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #13)
+> wikibugs appears to be in #mediawiki right now and is happily reporting bug
+> updates...
+
+This required me unquieting and unbanning the bot and Tim re-adding the bot to the channel.
+
+(In reply to comment #9)
+> Moving it's easier said than done, since it's not puppetized properly, but
+> that can be worked around.
+
+It's pretty easy. You change ""mediawiki"" to something else (e.g., ""mediawiki-feeds"").
+
+> Long term--wouldn't improvements to wm-bot be a good idea too?
+
+Absolutely. In the short-to-medium term, STOP KICKING THE BOT ON A WHIM.",1363375114,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,wikibugs appears to be in #mediawiki right now and is happily reporting bug updates...,1363368845,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #11)
+> (In reply to comment #7)
+> > Hashar kicked it yesterday... Adding hashar to CC.
+> 
+> I have not kicked wikibugs out of any IRC channel. Additionally, I have ZERO
+> interest in wikibugs nowadays nor am I able to do anything about it. Sorry.
+
+Ah it was ^demon. Sorry for my bad memory.",1363358615,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #7)
+> Hashar kicked it yesterday... Adding hashar to CC.
+
+I have not kicked wikibugs out of any IRC channel. Additionally, I have ZERO interest in wikibugs nowadays nor am I able to do anything about it. Sorry.",1363353592,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #8)
+> If we kick any single bot, Gerrit produces a-lot more cruft lately than
+> wikibugs... I, as having pointed out would prefer them all in a separate
+> channel that is moderated and only the bots are voiced.
+
+This. wikibugs is useful, it tends to notify about semi-interesting things that are happening (unless it notifies that someone CC'd himself on something, but that's another bug).
+
+gerrit-wm tends to spam about changes being merged to wmf branches.",1363347600,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #6)
+> (In reply to comment #5)
+> Lets move it into #mediawiki-feed or another channel then. It provides a
+> better
+> service than wm-bot does (comment 1), and people find it useful. If the
+> specific channel that it's in is a problem, move the bot, don't just kill it.
+
+Moving it's easier said than done, since it's not puppetized properly, but that can be worked around.
+
+Long term--wouldn't improvements to wm-bot be a good idea too?",1363346924,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Lets take this the mailing list again...
+
+(But my two cents)
+If we kick any single bot, Gerrit produces a-lot more cruft lately than wikibugs... I, as having pointed out would prefer them all in a separate channel that is moderated and only the bots are voiced.",1363346843,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Hashar kicked it yesterday... Adding hashar to CC.,1363346799,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #5)
+ 
+> We've had *contributors* complaining about the bot(s) for the past couple of
+> months/years.
+
+So then lets fix the problem, not just shut off a service people find useful.
+> 
+> I really don't think two/three people saying ""I LIKE THE BOT IN #MEDIAWIKI SO
+> LEAVE IT THE HELL ALONE"" trumps the wider problems here...that the bot
+> *needs*
+> to go.
+
+Lets move it into #mediawiki-feed or another channel then. It provides a better service than wm-bot does (comment 1), and people find it useful. If the specific channel that it's in is a problem, move the bot, don't just kill it.",1363346711,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"We actively had a user saying ""This channel obviously isn't for support...two pages of scrollback and I've spotted 2 real people."" This is a bad thing, contrary to what you may think.
+
+We've had *contributors* complaining about the bot(s) for the past couple of months/years.
+
+I really don't think two/three people saying ""I LIKE THE BOT IN #MEDIAWIKI SO LEAVE IT THE HELL ALONE"" trumps the wider problems here...that the bot *needs* to go.",1363346397,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,*** Bug 46139 has been marked as a duplicate of this bug. ***,1363338334,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,15 04:19:44 -!- wikibugs [~wikibugs@mchenry.wikimedia.org] has joined #mediawiki,1363321422,PHID-USER-7ey733eainlhx5xqp4d3,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"15 04:03:39 < Susan> Can someone please take a look at <https://bugzilla.wikimedia.org/show_bug.cgi?id=46144>?
+15 04:16:04 < jeremyb_> Susan: i did
+15 04:16:18 < Susan> Helpful.
+15 04:16:19 < jeremyb_> (a while ago)
+15 04:16:29 < jeremyb_> Susan: it was kicked. people didn't like the spamming
+15 04:16:37 < Susan> I don't like people.
+15 04:16:39 < Susan> I think we're even.
+15 04:16:41 < jeremyb_> there was a user trying to get help and had trouble because of the flood
+15 04:16:52 < jeremyb_> (wasn't my decision i only saw the scrollback)
+15 04:17:03 < jeremyb_> Susan: anyway, there's #mediawiki-feed for now
+15 04:17:10 < Susan> It's a terrible replacement.
+15 04:17:15 < Susan> As it's missing wikibugs.
+15 04:17:28 < jeremyb_> it has wm-bot providing a similar service
+15 04:17:31 < jeremyb_> i witnessed it
+15 04:17:50 < jeremyb_> and you've been there too
+15 04:18:34 < jeremyb_> Susan: at some point we should either let it back into #mediawiki or configure it to not join (and remove the ban). also we could maybe get wikibugs to join #mediawiki-feed if you really care
+15 04:18:48 < Susan> I do really care.",1363321307,PHID-USER-7ey733eainlhx5xqp4d3,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"wm-bot in #mediawiki-feed is not an acceptable replacement for wikibugs.
+
+For example, Quim added a comment here: bug 35508 comment 14.
+
+wm-bot reported this:
+
+<wm-bot> [bugzilla] (--- - created by: Sumana Harihareswara | priority: enhancement - Normal assignee Chad H.) [Bug 35508] List of Gerrit users - https://bugzilla.wikimedia.org/show_bug.cgi?id=35508
+
+I realize that this is a limitation of Bugzilla's RSS feed, but the output is still almost useless.",1363321220,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+VisualEditor: Transaction with replaceMetadata then replace at the same offset doesn't rollback cleanly,"This is kind of a ridiculous case, but it cost me an hour of debugging time, so documenting it here for posterity. It won't be a practical issue until we start composing transactions together.
+
+Consider:
+
+var data = ve.dm.example.withMeta,
+    oldDoc = new ve.dm.Document( ve.copyArray( data ) ),
+    newDoc = new ve.dm.Document( ve.copyArray( data ) ),
+    tx = new ve.dm.Transaction();
+tx.pushRetain( 11 );
+tx.pushReplaceMetadata( [], [ { metadata element here } ] );
+tx.pushReplace( [] , [ 'a', 'b', 'c' ] );
+ve.dm.TransactionProcessor.commit( newDoc, tx );
+ve.dm.TransactionProcessor.rollback( newDoc, tx );
+
+After running this, you'd expect oldDoc.metadata and newDoc.metadata to be equal, but they're not:
+
+> oldDoc.metadata[11].length;
+4
+> newDoc.metadata[11].length;
+5
+
+When the transaction is rolled back, the metadata element that was added was never removed. I think this is because the content insertion pushes the metadata back, and then when the rollback tries to remove the metadata again, it can't find it. When the metadata replacement and content replacement are swapped, it works fine, so that's my workaround for now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1363300500,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2imau6pf732mnvgzug5k,task_description,invalid
+VisualEditor: Transaction with replaceMetadata then replace at the same offset doesn't rollback cleanly,There are no more metadata ops since T56299.,1682006049,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2imau6pf732mnvgzug5k,task_subcomment,NA
+"VisualEditor: Redesign naming of canHaveChildren, ContentBranchNode, etc.","Trevor complained the naming of these things doesn't make sense, so let's sit down and come up with a strategy for renaming this stuff at some point.",1363284960,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-o7nh4k5ffcmrnlrox5vs,task_description,open
+VisualEditor: Allow testing dom<->data conversion with and without MW-specific nodes registered,"TODO comment in ve.dm.Converter.test.js:
+
+// TODO: this is a hack to make normal heading/preformatted
+// nodes the most recently registered, instead of the MW versions
+
+It's not entirely clear to me how we should fix this. Maybe once we hard-split the VE and MWVE code bases and each of these has its own test suite, then we won't have to worry about this as much.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363131420,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-2jnxk3ykpceaf3icyoim,task_description,resolved
+VisualEditor: Allow testing dom<->data conversion with and without MW-specific nodes registered,This was fixed in gerrit 70753.,1372874201,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2jnxk3ykpceaf3icyoim,task_subcomment,NA
+"VisualEditor: When Parsoid is down, error message is parsoidserver-http-200","When the Parsoid server is down completely (e.g. because you forgot to start it), the error message VE gives you is ""parsoidserver-http-200"". It's kind of ridiculous that it's presenting an error with 200, but it's also a lie: 200 wasn't the response code we got from Parsoid, we got no response whatsoever.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362783660,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6g7xrokkwj7xvlcpixpd,task_description,resolved
+"VisualEditor: When Parsoid is down, error message is parsoidserver-http-200",https://gerrit.wikimedia.org/r/#/c/53165/,1363011611,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6g7xrokkwj7xvlcpixpd,task_subcomment,NA
+VisualEditor: Add static name property to CE nodes,"DM nodes have a static name property which is used by the nodeRegistry. CE nodes currently have their names written out at least twice. It also creates unnecessary complexity when inheriting CE nodes as the parent constructor cannot be used (as it contains the parent's name hard coded).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362405720,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qrmj2zvtj5xzsxn37rp3,task_description,resolved
+VisualEditor: Add static name property to CE nodes,Related URL: https://gerrit.wikimedia.org/r/52545 (Gerrit Patch-Set: Ibf31de16ab28ad58209c1443cd74f93dda278998/7),1362697441,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qrmj2zvtj5xzsxn37rp3,task_subcomment,NA
+VisualEditor: Add static name property to CE nodes,Fixed with https://gerrit.wikimedia.org/r/#/c/52545/,1362610508,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qrmj2zvtj5xzsxn37rp3,task_subcomment,NA
+VisualEditor: Kill global functions in test suites,"Functions like runConverterTests() and what not are often global functions in the test file. These should be un-global-ified somehow.
+",1361566080,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ynic2zitioz5lqrrxvlq,task_description,open
+VisualEditor: Kill global functions in test suites,"Found a few:
+
+- ve.dm.ModelRegistry.test
+* function checkForPickMe
+
+- ve.dm.Transaction.test
+* function runBuilderTests
+* function runConstructorTests",1369152667,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ynic2zitioz5lqrrxvlq,task_subcomment,NA
+VisualEditor: Kill global functions in test suites,I can't find these any more. Resolved?,1369145400,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ynic2zitioz5lqrrxvlq,task_subcomment,NA
+VisualEditor: SurfaceFragment methods don't document their chainability properly,"The hallmark of chainability in VE, dm.SurfaceFragment, doesn't actually use @chainable to document the chainability of most of its methods.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361494680,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lshlhzbjuwcfnblbdwsc,task_description,resolved
+VisualEditor: SurfaceFragment methods don't document their chainability properly,Change-Id: Ib950422ddb78d7b91545399a6053e82ae2dbd932,1361614307,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-lshlhzbjuwcfnblbdwsc,task_subcomment,NA
+VisualEditor: newFromWrap() should perform validation,"ve.dm.Transaction.newFromWrap() currently doesn't check that the transaction it generates will be valid. That is, it will ensure that things are unwrapped correctly, but it doesn't check that the result doesn't end up violating parent/child restrictions.
+
+It's not entirely clear to me whether we should try to rectify that or throw an exception, but either of those is better than generating a transaction that, when applied, will make the document nonconformant.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1361325660,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-dxxwsml3j6lvywpngjgf,task_description,open
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"When a user saves a page, VE should check for references (<ref>s) created without the de-referencing block (<references /> or {{reflist}} or...) and intervene:
+
+* prompt them to fix before saving (out of the notices area?);
+* refuse to save before fixed (grey out the save button?); or
+* auto-fix for them (insert a ""== References ==\n<references />"" section just above the categories), though this (a) sucks, (b) enforces a particular wiki's style on other wikis in code, and (c) would be difficult to internationalise
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54906
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51260",1361220060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bw6slpyeq2u23y3ltra6,task_description,invalid
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"This probably doesn't really matter any more, since the absence of a references template will simply cause the references to display at the end of the page.",1508927932,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"The last thing I want us to be doing is adding more error messages. I really think that we can get away with actually fixing the error for people. 
+
+I'd rather see us put it in the wrong place and someone have to fix it than us give the user an error they probably don't know how to fix. 
+
+Can we do a quick audit of major sites and where they put the reference list? I worry we're worrying a bit too much about about negative feedback that might not be as big a deal as we might think.",1383182051,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"(In reply to comment #4)
+> The auto-fix option in comment 0 has been requested today by en.wp user
+> Mahitgar. If the issues noted can be overcome, then it would be the most
+> user-friendly way forward.
+> 
+> Regarding those issues, it is not obvious why this ""sucks"" - please could you
+> elucidate?
+> 
+> Internationalisation of the section title could (I guess easily) be achieved
+> by
+> inserting the contents of a MediaWiki page instead of something defined in
+> code. e.g. the equivalent of
+> 
+> ==={{subst:MediaWiki:Refsection title}}===
+> <{{subst:MediaWiki:Reflist function name}} />
+> 
+> 
+> This doesn't solve the option of imposing en.wp style on other wikis though.
+
+Blindly putting the references section at the end of the article seems to not be great (it'd be after the ""external links"" and ""see also"" sections, and after any stub or thematic templates).",1376520004,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"The auto-fix option in comment 0 has been requested today by en.wp user Mahitgar. If the issues noted can be overcome, then it would be the most user-friendly way forward.
+
+Regarding those issues, it is not obvious why this ""sucks"" - please could you elucidate?
+
+Internationalisation of the section title could (I guess easily) be achieved by inserting the contents of a MediaWiki page instead of something defined in code. e.g. the equivalent of
+
+==={{subst:MediaWiki:Refsection title}}===
+<{{subst:MediaWiki:Reflist function name}} />
+
+
+This doesn't solve the option of imposing en.wp style on other wikis though.",1376323198,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,*** Bug 51910 has been marked as a duplicate of this bug. ***,1375192364,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"Bug 50779 makes it easy to accidentally delete the references list, so this should check for its presence every save not just when references have been added.",1375180866,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"Currently this would require scanning for the exact html it outputs as the <span style=""color:red;"">...</a> tag. Which can be tricky to do reliably.
+
+Though the Cite extension could perhaps be the first to give their elements some kind of standard attribute for parse errors, it should probably do more like the TemplateData extension: Refuse to save without it and show a warning there instead. Then the API will return to VE with a nice { error: .. } block containing a error code which we can use to fetch a localised message.",1371776892,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"Using a more extensive default $linkTrail regex was tried in 416c84480 (although I don't know why it used `\p{L&}` rather than `[[:alpha:]]` or `\p{L}`), but this was reverted in 5b97a5bb due to {T17035}. We could probably try that again (without the apostrophe, see T16655) now that we require a more modern version of PHP with a more modern version of PCRE. It may not work correctly for alphabets other than Latin.
+
+----
+
+Please have a look at 
+https://www.wikidata.org/wiki/MediaWiki:Gadget-rightsfilter/hu
+where the link has the form [[:hu:Reguláris kifejezés|regex]]alapú
+and ""ú"" is not linked.
+This is a multilingual project, so all letters should be included into links, or at least all Hungarian letters. :-)",1361209560,PHID-USER-4c6srusxkc3xljf73qq6,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_description,open
+The default (English) link trail ($linkTrail) only matches [a-z],">>! In T47126#2509560, @Verdy_p wrote:
+> link trails are just a minor facility for **lazy** English contributors using the Wiki code editor.
+
+Those links can be used in many languages. In German Wikipedia they are used exceedingly!
+",1471883260,PHID-USER-co4khfkxwku2c5tgvhnc,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"\p{Latin} would not be sufficient to avoid breaking words. There are languages needing other characters within Latin, notably with combining sequences. See for example Vietnamese that could use letters with two diacritics ! See also Chinese pinyin text, and some African languages.
+
+In fact the minimum would require adding all combining characters (really needed to avoid breaking default grapheme clusters), all joiner controls, digits (including their wide versions used in CJK contexts because p{Latin} also includes wide letters), and a few punctuations (and the soft hyphen, but probably not the minus-hyphen).
+
+Handling the ASCII apostrophe is complex (even more complex in MediaWiki due to its use to markup bold and italic styles: an initial parsing of these wiki syntax would be needed to know if these are apostrophes or markup...).
+
+Note also that the apostrophe mays also be used as a quote (this is covered in more details in Unicode word breakers), and that this concerns not only the the ASCII apostrophe but also the rounded apostrophe.
+
+Again, it is really needed to look at the Unicode standard :
+
+# a MUST-HAVE in all cases, for all languages first requires not breaking any combining sequences before any characters with a non-zero combinining class and not even before CGJ), and to ensure that canonically equivalent strings will always break identically (needed for strict process conformance as required by the standard in all algorithms).
+#  the rules for default grapheme clusters breakers (this adds some unbreakable sequences for Latin text), these rules are language-neutral (there are a few rules to take for Latin text, notably ""spacing diacritics"", and joiners; we could exclude here some ""letterlike"" symbols that are not really Latin).
+#  the rules for word breakers (even if we consider only Latin-written languages): these rules however are language-sensitive (English is simple at this step but not all Latin-written languages, here there's the case for apostrophes, hyphens...)
+
+In summary, it will be much more complex than just a regular expression: it requires a specific parser code (look at ICU implementation).",1470057925,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],Hungarian was cited because the current conservative linktrail rules break Hungarian words. `\p{L}` or `\p{L&}` would work well for Hungarian (I imagine the latter was used to avoid affecting CJK languages; no idea how well that works). Even `\p{Latin}` would be fine.,1470035748,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],For years it was corrected in the other direction. It would be mad to change this now.,1470008927,PHID-USER-4z6eerx3m7iocsrcpku5,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"I don't think that ""cleanup"" operations such as automated replacement of [[Dog|dogs]] to [[dog]]s are useful. In fact they are counterproductive (and in fact unnecessary for the Visual Editor that should completely avoid using these link trails).
+
+My opinion is we **should deprecate** these old link trails and in fact correct the other ways (link trails are just a minor facility for **lazy** English contributors using the Wiki code editor.
+
+In fact, even the Wiki editor should better automatically convert these trails (only [a-z]) to regular links without them. It would also simplify the parsers for bots and analysers. Contributors should always use regular links, that are in fact more readable, and more explicit about the effective range of text covered by links.",1469974285,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"I don't think that ""cleanup"" operations such as automated replacement of [[Dog|dogs]] to [[dog]]s are useful. In fact they are counterproductive (and in fact unnecessary for the Visual Editor that should completely avoid using these link trails).
+
+My opinion is we **should deprecate** these old link trails and in fact correct the other ways (link trails are just a minor facility for **lazy** editors using the Wiki code editor.
+
+In fact, even the Wiki editor should better automatically convert these trails (only [a-z]) to regular links without them. It would also simplify the parsers for bots and analysers. Contributors should always use regular links, that are in fact more readable, and more explicit about the effective range of text covered by links.",1469974218,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"I can say that link trails work well in Polish, which has fairly complex conjugation and declension rules. I'd make a wild guess that it works in around 50% of cases (in English it's more like 99%, as you say). There is a very popular gadget on Polish Wikimedia projects that applies wikitext code cleanup, and one of the cleanups it does is converting things like `[[Dog|dogs]]` to `[[dog]]s`. I would be very sad if we wanted to get rid of them.",1469663792,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"I can say that link trails work well in Polish, which has fairly complex conjugation and declension rules. I'd make a wild guess that it works in around 50% of cases (in English it's more like 99%, as you say). There is a very popular gadget that applies wikitext code cleanup, and one of the cleanups it does is converting things like `[[Dog|dogs]]` to `[[dog]]s`. I would be very sad if we wanted to get rid of them.",1469663654,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"Note als othat a few languages written in the Latin script also use ""agglutination"" for creating very long custom ""words"" by using many prefixes/inffixes/suffixes (and often some internal mutations). Such extension may break for example in Finnish or Hungarian (Hungarian was cited at top of this bug).
+
+Any way I don't think that link trails are a very good idea: users can't control it easily (and should not have to include some arbitrarty separation toklen such as ""nowiki/>"" to limit these trails. Link trails were added only for lazy English writers that want to create links to a singural noun, by placing the final ""s"" of the displayed plural in the trail, or for placing some common suffixes (""ed"", ""s"") of conjugated verbs (but it does not work when there are more complex mutations such as ""*y -> *ies"").
+
+This concept of link trails does not even exist in HTML. And anyway with the Visual Editor, we much less need it now as it is simpler to edit links separately of their visible text content.
+",1469663399,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"> Such link trails should contain only letters or digits in the same script as the last string script used within the inner text of the link and only if that script is alphabetic or an abjad, but probably not Indic abugidas and not any sinographic script (a good question is: can we extend some kanas after a kanji in the inner text of the link (I don't think so), but we can probably extend runs of kanas.
+
+There are some rules for semi-sensible word breaking in CJK languages. VisualEditor implements some of them to be able to e.g. extend selection to the word around cursor when inserting an internal link. I'm not sure if they're simple enough to implement as a regexp; @dchan can probably advise.",1469663161,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"In my opinion [[:alpha:]] or \p{L} would be wrong for Chinese and Thai at least ! they would produice overlong links sticked side by side everywhere and covering most contents in all paragraphs. In Wikipedia, almost all the text of paragraphs would be blue except the start of paragraphs without significant words.
+
+Such link trails should contain only letters or digits in the same script as the last string script used within the inner text of the link and only if that script is alphabetic or an abjad, but probably not Indic abugidas and not any sinographic script (a good question is: can we extend some kanas after a kanji in the inner text of the link (I don't think so), but we can probably extend runs of kanas.
+
+The Unicode rule of matching identifiers is not usable for this (we are not in the context of a programminc language but within a context of use by a natural language, so the punctuation/spacing rules are very different).
+
+If we want a regexp, for now let's focus only in Latin, Greek, Cyrillic, Arabic, Hebrew, and possibly Hangul, breaking the run if there's any change of script (but not if these are ""weak"" digits belonging to all scripts). Extending the regexp for other scripts should be tested first (the hint here is to look at existing rules existing in CLDR for *word breakers* and look at the Unicode standard covering this complex aspect. And may be include also the line breakers to restrict more the link trails to get shorter runs.
+
+However this should not be very language specific: it should better be script-specific.
+
+",1469662578,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"Historical note: Using a more extensive regex was tried in 416c84480 (although I don't know why it used `\p{L&}` rather than `[[:alpha:]]` or `\p{L}`), but this was reverted in 5b97a5bb due to {T17035}. We could probably try that again (without the apostrophe, see T16655) now that we require a more modern version of PHP with a more modern version of PCRE.",1469628163,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"""Is this strange behaviour something we want to preserve, or is it just a historical quirk?""
+Or just survived tests, as a rare case.",1469625591,PHID-USER-4c6srusxkc3xljf73qq6,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"Essentially I think the linktrail for `en` should include all Latin-alphabet characters in the regex. Would `/^(\p{Latin}+)(.*)$/` work?
+
+Although, oddly enough, most uppercase letters are left out of the linktrails. For the Hungarian example above, only accented uppercase letters are matched, not regular ones. Most languages don't include any uppercase letters in their linktrail  string. Is this strange behaviour something we want to preserve, or is it just a historical quirk?",1469625378,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"No, this is a perfectly valid bug. Unfortunately ""link trails"" are currently specified per-language, and the link trail for English doesn't include any accented characters. For example it's defined like this for Hungarian: `$linkTrail = '/^([a-záéíóúöüőűÁÉÍÓÚÖÜŐŰ]+)(.*)$/sDu';`, but these characters will only work on a Hungarian-language wiki.",1469624271,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],OK. Thanks for the detailed explanation.,1469598638,PHID-USER-4c6srusxkc3xljf73qq6,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Link|Links]]"") is just an **old (deprecated) trick** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583675,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Target|Links]]"") is just an **old (deprecated) trick** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583643,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Target|Links]]"") is just an ***old (deprecated) trick*** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583625,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Target|Links]]"") is just an ***old (deprecated) trick*** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583610,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Target|Links]]"") is just an old **trick*** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583362,PHID-USER-haxgydpauf444oiywhg2,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],This seems to be problem on all multilingual projects...,1450788845,PHID-USER-l6fch4yy6jwf3du42zrz,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"It could also be that the content language is still English in some cases, but it doesn't seems so form the content source.",1361275352,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],This is link trails and it is part of the localization that would be very difficult to get right for everyone. In this case I would say put what you want to use for the page part into the link and do not depend on the link trails.,1361274313,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,"This test works in Chrome, but in Firefox it fails with:
+
+Expected: 	
+
+""a<b>b<span typeof=\""mw:Entity\"" class=\""ve-ce-leafNode ve-ce-MWEntityNode\"" contenteditable=\""false\"">c</span>d<div class=\""ve-ce-leafNode ve-ce-alienNode ve-ce-alienInlineNode\"" contenteditable=\""false\""><tt>e</tt></div></b>""
+
+Result: 	
+
+""a<b>b<span class=\""ve-ce-leafNode ve-ce-MWEntityNode\"" typeof=\""mw:Entity\"" contenteditable=\""false\"">c</span>d<div class=\""ve-ce-leafNode ve-ce-alienNode ve-ce-alienInlineNode\"" contenteditable=\""false\""><tt>e</tt></div></b>""
+
+(the difference is in the order of the class and typeof attributes)
+
+We should probably implement DOM comparison instead of string comparison in the ce.ContentBranchNode test suite.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1360374780,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_description,resolved
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,"Related: https://gerrit.wikimedia.org/r/#/c/240722/ in MW, where we need to decode data-mw and parse body.html, sometimes recursively :/",1443111671,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_subcomment,NA
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,https://gerrit.wikimedia.org/r/#/c/240693/,1443111590,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_subcomment,NA
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,"This specific case is fixed in https://gerrit.wikimedia.org/r/#/c/57240 by using equalDomElement. However, another case has appeared: recent code introduced full HTML preservation in mw:Image and the attribute order in the HTML serialization matters there too, so now that test passes in Chrome but fails in Firefox (getDataFromDom test 4).",1365033745,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_subcomment,NA
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,"Not sure if it is caused by the javasript object keys. May be related to how WebKit/Geck order the element attributes when serialising the html.
+
+If the former:
+ ve.getHash or assert.deepEqual
+
+If the latter:
+ assert.equalDomElement",1361569492,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_subcomment,NA
+VisualEditor: Clean up duplication of Mac/PC command/ctrl in all command registrars,"Should perhaps have some kind of magic alias ""trigger"" that maps to meta/ctrl respectively.
+
+The flexibility of being able to bind something to ctrl on mac, and to meta on pc is useful but in the most common case we don't to do that.
+
+And we're currently duplicating this internal logic at the cost of decentralisation. So plugin authors providing Tools need to duplicate this logic also, meaning more maintenance when we change this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1359158880,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-fbrnpd67ntdl7dxrvivk,task_description,open
+Only tag edits via GettingStarted if the user is actually new,"The GettingStarted extension is tagging edits of new users (bug 43191). These tags should be temporary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1359154380,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-o2degjsneil7pojmpiav,task_description,resolved
+Only tag edits via GettingStarted if the user is actually new,"**swalling** wrote:
+
+https://gerrit.wikimedia.org/r/#/c/65337/ was merged, and henceforth only users who aren't autoconfirmed will get their GettingStarted edits tagged.",1369959989,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,Related URL: https://gerrit.wikimedia.org/r/65337 (Gerrit Change I3bc2235ac9d5ae1060c86df03663dcb8a6966a38),1369431985,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,"(In reply to comment #4)
+> It sounds like you have a general problem with permanent tags. 
+
+It sounds like you didn't read comment 3.",1368574939,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,"**swalling** wrote:
+
+(In reply to comment #3)
+> The general trend of permanently tagging edits should be examined. Other
+> sites
+> engage in similar practices (such as Facebook marking mobile posts), but
+> whether this is a good thing or whether it should be encouraged is up for
+> debate.
+> 
+> In this case, I don't think permanently marking someone's first edits after
+> you've secretly tagged them as part of an experiment that they didn't opt in
+> to
+> is a good idea. Do other bad tags exist? Yes, but those aren't really
+> relevant
+> here.
+
+It sounds like you have a general problem with permanent tags. 
+
+I think our actual enhancement is to not tag edits of users who aren't new anymore if they make further edits via Special:GettingStarted, e.g. if you're autoconfirmed don't tag their edit, even if if comes via GettingStarted. That's an enhacement we should make, but it's not the same thing as altering MediaWiki tags so they're there one minute and gone the next. That's unexpected and broken behavior according to how tags currently work in all other cases. 
+
+I've changed the bug title to reflect what we're actually going to do around tagging in GettingStarted, to ensure that the tag is accurate.",1368565460,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,"The general trend of permanently tagging edits should be examined. Other sites engage in similar practices (such as Facebook marking mobile posts), but whether this is a good thing or whether it should be encouraged is up for debate.
+
+In this case, I don't think permanently marking someone's first edits after you've secretly tagged them as part of an experiment that they didn't opt in to is a good idea. Do other bad tags exist? Yes, but those aren't really relevant here.",1359156311,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,This proposal is a specific case of https://bugzilla.wikimedia.org/show_bug.cgi?id=18670 .,1359155975,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,"I'm not yet convinced this is a problem.  There are a variety of permanent tags (edit filter, VisualEditor, etc.).  In all cases, it's a good-faith tag of the edit.
+
+Edit filter tags are permanent, even though they sometimes wrongly flag an edit as harmful.  It's just understood that the situation will be cleared up, and editors will move on.
+
+Similarly, the fact that a user made a Special:GettingStarted edit doesn't even mean they're necessarily new.  It's understood and accepted that established users can also have this tag on their edits if they use the page.
+
+It indicates how they made it.  It certainly is not a marker of whether the edit is productive.  And it doesn't really say anything about the user, let alone the user's future work.",1359155274,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I encountered many times now on wikis (usually the small wikis) that there are 100s of local MediaWiki pages with translations from before translatewiki.net covered that language.
+
+And even after twn covered it, there may have been local improvements that over time make it into twn, but then the local page stales.
+
+To avoid translations from going out of sync (the longer we wait with this, the harder it is to clean them up as the difference between an override and an outdated translation becomes harder to tell), and also to avoid migration issues when messages change.
+
+Lets run this asap.
+
+--------------------------
+//EDIT//: deleteEqualMessages.php has been completed on the following wikis:
+{P1988}",1358039640,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_description,resolved
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSrzRPvwY2u4JUTPlju} [2018-07-18T05:11:41Z] <Krinkle> mwscript deleteEqualMessages.php --wiki dewiki (1 page) - T45917",1531890702,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSrzN-hwY2u4JUTPljt} [2018-07-18T05:11:27Z] <Krinkle> mwscript deleteEqualMessages.php --wiki ruwiki (4 pages) - T45917",1531890688,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSrzKYowY2u4JUTPljs} [2018-07-18T05:11:13Z] <Krinkle> mwscript deleteEqualMessages.php --wiki frwiki (5 pages) - T45917",1531890673,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSryx3NoDEJc1hAykSQ} [2018-07-18T05:09:32Z] <Krinkle> mwscript deleteEqualMessages.php --wiki metawiki (deleted 1 page) - T45917",1531890573,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSrywV9oDEJc1hAykSP} [2018-07-18T05:09:26Z] <Krinkle> mwscript deleteEqualMessages.php --wiki test2wiki (deleted 2 pages) - T45917",1531890567,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVsHFYbVlCyyDMEPvX-7} [2017-03-25T20:08:22Z] <Krinkle> Ran mwscript deleteEqualMessages.php on public wikis (T45917) - deleted 5 pages across 5 wikis",1490472503,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVruLkTylCyyDMEPvWIy} [2017-03-21T00:04:54Z] <Krinkle> mwscript deleteEqualMessages.php on public wikis (T45917)",1490054696,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> if dry run, where to publish it. (https://people.wikimedia.org/~krinkle/ maybe?)
+
+That would be ok. On the other hand, this list already proves that LocalisationUpdate is needed and must be faster, to avoid accumulating translator frustration and unnecessary technical debt (see ruwiki example: https://ru.wikipedia.org/w/index.php?title=MediaWiki%3ACreate-local&type=revision&diff=84144899&oldid=84144800 https://translatewiki.net/w/i.php?title=MediaWiki%3ACreate-local%2Fru&type=revision&diff=7293894&oldid=5453967 ).",1489915878,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#3083680, @Amire80 wrote:
+>>>! In T45917#3083285, @Nemo_bis wrote:
+>> So if anything we should have a cronjob with a dry run, which triggers an alert somewhere when messages get translated locally. [..]
+> 
+> I regularly check Special:AllMessages //in languages that I know//. I wish it was done in all languages, but I alone don't have the capacity to do it manually. [..]
+
+If I understand correctly, you're looking for instances of where the translation is overridden and not equal - e.g. to find potential improvements that could be upstreamed. I'm not sure how to automate that since many of those will be semi-permanent local modifications that are specific to the wiki.
+
+However if we want to find out about translations that were once local overrides but are now redundant (presumably due to it being upstreamed), I could run the maintenance script that this task is about, from a cron on terbium.
+
+It's only been 10 days, but there are already plenty of translations detected again that are now equal:
+```
+foreachwikiindblist 'all - private' deleteEqualMessages.php | tee out-deleteEqualMessages-allwikis-dry.log
+-----------------------------------------------------------------
+aawiki
+-----------------------------------------------------------------
+aawiki:  Checking for pages with default message...
+aawiki:  ... fetching message info for content language
+aawiki:  done.
+-----------------------------------------------------------------
+```
+Filtered output:
+```lines=5
+$ grep '*' out-deleteEqualMessages-allwikis-dry.log 
+bnwiki:  * [[মিডিয়াউইকি:Cite references link many format backlink labels]]
+cebwiki:  * [[MediaWiki:Loginreqlink]]
+commonswiki:  * [[MediaWiki:Kartographer.js]]
+donatewiki:  * [[MediaWiki:Donate interface-problemsdonating]]
+donatewiki:  * [[MediaWiki:Fundraiserlandingpage-wmch-landing-page]]
+elwiki:  * [[MediaWiki:Ep-addstudents-btn]]
+elwiki:  * [[MediaWiki:Ep-user-roles-message-additional]]
+guwikisource:  * [[મીડિયાવિકિ:Common.js]]
+guwikisource:  * [[મીડિયાવિકિ ચર્ચા:Common.js]]
+guwikisource:  * [[મીડિયાવિકિ:Proofreadpage quality3 category]]
+hrwiktionary:  * [[MediaWiki:Prefs-personal]]
+mkwiki:  * [[МедијаВики:Searchresults-title]]
+plwiki:  * [[MediaWiki:Wm-license-cc-wiki-link]]
+plwiki:  * [[MediaWiki:Wikieditor-toolbar-tool-link-int-target]]
+plwiki:  * [[MediaWiki:Wikieditor-toolbar-tool-link-int-text]]
+plwiki:  * [[MediaWiki:Geodata-broken-tags-category]]
+ruwiki:  * [[MediaWiki:Create-local]]
+trwiki:  * [[MediaWiki:Autosumm-blank]]
+trwiki:  * [[MediaWiki:Group-interface-editor]]
+trwiki:  * [[MediaWiki:Grouppage-interface-editor]]
+trwikibooks:  * [[MediaWiki:Autosumm-blank]]
+trwikiquote:  * [[MediaWiki:Autosumm-blank]]
+trwikisource:  * [[MediaWiki:Autosumm-blank]]
+trwiktionary:  * [[MediaWiki:Autosumm-blank]]
+trwiktionary:  * [[MediaWiki tartışma:Autosumm-blank]]
+ukwikivoyage:  * [[MediaWiki:Group-uploader]]
+ukwikivoyage:  * [[MediaWiki:Group-uploader-member]]
+ukwikivoyage:  * [[MediaWiki:Wikibase-otherprojects-wikipedia]]
+ukwikivoyage:  * [[MediaWiki:Interlanguage-link-wikipedia]]
+ukwikivoyage:  * [[MediaWiki:Interlanguage-link-commons]]
+```
+
+I'm open for ideas on whether to schedule this periodically, as dry run or not, and if dry run, where to publish it. (<https://people.wikimedia.org/~krinkle/> maybe?)",1489809250,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#3083285, @Nemo_bis wrote:
+> So if anything we should have a cronjob with a dry run, which triggers an alert somewhere when messages get translated locally. It could be one useful signal of an insufficient frequency of localisation updates, due to broken LocalisationUpdate or other reasons. (In general, we already know that the updates must be daily; but contingent data points are still useful.)
+
+This.
+
+I regularly check Special:AllMessages //in languages that I know//. I wish it was done in all languages, but I alone don't have the capacity to do it manually. I very frequently find not only translation mistakes, but also reasons to fix the original English message, and of course this happens not only when the local customization is the same as the original message, but also when it's different.
+
+It's good to have local translation in the MediaWiki space as a quick fix for particularly bad translation mistakes, or for actually-needed local customizations, but it must not be relied upon as a an actual way to translate the interface, even temporarily. (And even though I'm saying ""actually-needed local customization"", these should actually always raise the question of whether this thing should be done through a message at all, but that's a separate topic.)",1488969396,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","So if anything we should have a cronjob with a dry run, which triggers an alert somewhere when messages get translated locally. It could be one useful signal of an insufficient frequency of localisation updates, due to broken LocalisationUpdate or other reasons. (In general, we already know that the updates must be daily; but contingent data points are still useful.)",1488962701,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","That's what I'm saying. The usual reason people were editing the messages was because LU was broken, or there was a long time between deploys.
+
+I'm not even suggesting we encourage people to edit the MW namespace like that",1488923437,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I agree with @nemo_bis why force people to do something they dont want to, especially if we have the ability to do it ourselves. ",1488922841,PHID-USER-ct4qymje4lpxby255tze,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> People that don't want to wait for train deploys and/or LocalisationUpdate?
+
+Forcing such people to edit the MediaWiki namespace would be a broken system.",1488922637,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#3081939, @Nemo_bis wrote:
+>> Any reason we can't cronjob it, say monthly?
+> 
+> This is supposed not to be a recurring task on each wiki: if it's needed regularly, then something is wrong.
+
+People that don't want to wait for train deploys and/or LocalisationUpdate?",1488922530,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> Any reason we can't cronjob it, say monthly?
+
+This is supposed not to be a recurring task on each wiki: if it's needed regularly, then something is wrong.",1488922193,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","It'd be interesting to see the scale of this in relation to T158360...
+
+Any reason we can't cronjob it, say monthly?",1488917248,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","@MarcoAurelio Thanks. Yeah, my thoughts exactly. This should be re-run from time to time as upstreaming happens all the time.
+
+Meanwhile, as always, feel free to ask here or on IRC for a run on a specific wiki (or set of wikis).",1488916953,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","@MarcoAurelio Thanks. Yeah, my thoughts exactly. This should be re-run from time to time as upstreaming happens all the time.
+
+Meanwhile, as always, feel free to ask here on IRC for a run on a specific wiki (or set of wikis).",1488916940,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","@MarcoAurelio Thanks. Yeah, my thoughts exactly. This should be re-run from time to time as upstreaming happens all the time.",1488916895,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","We should do this once or twice a year. Nice job, thanks.",1488893219,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVqnN6AAHQCSeVEJfRZs} [2017-03-07T05:22:04Z] <Krinkle> foreachwikiindblist 'all - closed - private' deleteEqualMessages.php (T45917) - purge upstreamed translations from remaining wikis",1488864127,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVqm0BIAlCyyDMEPvRe-} [2017-03-07T03:28:58Z] <Krinkle> foreachwikiindblist closed deleteEqualMessages.php (T45917) - purge upstreamed translations from closed wikis",1488857338,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVpoVYifQMK9DA-FKjFz} [2017-02-23T00:18:40Z] <Krinkle> mwscript deleteEqualMessages.php --wiki simplewikibooks (T45917)",1487809120,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVnODfVMHQCSeVEJfEH0} [2017-01-24T01:18:58Z] <Krinkle> mwscript deleteEqualMessages.php --wiki gotwiki (T45917)",1485220738,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",@Krinkle: Maybe https://meta.wikimedia.org/wiki/Steward_requests/Miscellaneous#All_local_mediawiki_messages_on_got.wikipedia.org_should_be_deleted is of interest here. Thanks.,1485096966,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVlreqFoHQCSeVEJe_Xe} [2017-01-04T21:55:15Z] <Krinkle> mwscript deleteEqualMessages.php --wiki nowikinews (T45917)",1483566916,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVlreoZdHQCSeVEJe_Xd} [2017-01-04T21:55:08Z] <Krinkle> mwscript deleteEqualMessages.php --wiki nowiki (T45917)",1483566909,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2822892, @MarcoAurelio wrote:
+> Can angwiki be run next? Thanks.
+
+:white_check_mark: Done!",1480114888,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2822892, @MarcoAurelio wrote:
+> Can angwiki be run next? Thanks.
+
+Done :)",1480104613,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVidG31FHQCSeVEJeyWR} [2016-11-25T20:09:34Z] <Krinkle> mwscript deleteEqualMessages.php --wiki angwiki (T45917)",1480104574,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Can angwiki be run next? Thanks.,1480071561,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhFB-pNQMK9DA-FJhuN} [2016-11-08T17:41:36Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki ptwikinews (T45917)",1478626896,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhEvj7xQMK9DA-FJhrT} [2016-11-08T16:21:08Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki kkwiki (T45917)",1478622068,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhBM2zgHQCSeVEJesuz} [2016-11-07T23:50:39Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki jawikinews (T45917)",1478562639,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhBIxJ3HQCSeVEJesuW} [2016-11-07T23:32:47Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki jawikibooks (T45917)",1478561567,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhBEtxkHQCSeVEJestw} [2016-11-07T23:15:04Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki gawiktionary (T45917)",1478560505,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVd9IhIcfIH_7EDsrdXG} [2016-09-30T22:06:07Z] <Krinkle> Re-run mwscript deleteEqualMessages.php on all wikis it was previously run on (T45917) ",1475273167,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570454, @MuhammadShuaib wrote:
+> @Dereckson, Will you export for me urwiki mediawiki messeges which do not exist on translatewiki? I can help which messeges to be imported to translatewiki. 
+
+Thanks, this is important work. :)",1471807228,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Here the list of messages to export:
+
+{P3863}
+
+You need to clean it: remove any Wikipedia or Wikimedia message.
+
+The goal is to:
+  - translate on wiki Wikimedia/Wikipedia messages
+  - translate on TranslateWiki universal messages
+
+",1471799443,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","@Dereckson, Will you export for me urwiki mediawiki messeges which do not exist on translatewiki? I can help which messeges to be imported to translatewiki. ",1471792632,PHID-USER-xfrkgxsnlepm7r3bx43d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVatnr1JpirJUPGy-ySY} [2016-08-21T15:01:16Z] <Dereckson> Run deleteEqualMessages maintenance script on urwiki (T45917)",1471791677,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570412, @Dereckson wrote:
+> We can sorry :)
+
+Thanks, Okay, I wish to delete those messeges which have same value on both wiki. ",1471791515,PHID-USER-xfrkgxsnlepm7r3bx43d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",We can sorry :),1471791402,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570408, @Dereckson wrote:
+> We can't start to delete messages with the same values on ur. and TranslateWiki if you wish.
+> 
+> That would delete 297 messages with the (identical) translation already on TranslateWiki.
+
+You can't? :)",1471791369,PHID-USER-xfrkgxsnlepm7r3bx43d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","We can't start to delete messages with the same values on ur. and TranslateWiki if you wish.
+
+That would delete 297 messages with the (identical) translation already on TranslateWiki.",1471791248,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","We can't start to delete messages with the same values on ur. and TranslateWiki if you wish.
+
+That would delete 297 messages.",1471791220,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",We can't start to delete messages with the same values on ur. and TranslateWiki.,1471791155,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570406, @Dereckson wrote:
+> Yes but that's exactly the problem.
+> 
+> TranslateWiki manages the translation for EVERY wiki un Urdu (and you can set every installation of MediaWiki in Urdu just adding ?uselang=ur).
+> 
+> Wikimedia and Wikipedia specific translations should be done on wiki.
+> 
+> Universal translations should be done on TranslateWiki.
+> 
+> So yes, we can export translations from ur.wikipedia to import them to TranslateWiki, but there is a need to know what messages to import, what not.
+
+In that case, Will you delete mediawiki: messeges on ur.wiki? Because now we are translating on translatewiki. ",1471790490,PHID-USER-xfrkgxsnlepm7r3bx43d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Yes but that's exactly the problem.
+
+TranslateWiki manages the translation for EVERY wiki un Urdu (and you can set every installation of MediaWiki in Urdu just adding ?uselang=ur).
+
+Wikimedia and Wikipedia specific translations should be done on wiki.
+
+Universal translations should be done on TranslateWiki.
+
+So yes, we can export translations from ur.wikipedia to import them to TranslateWiki, but there is a need to know what messages to import, what not.",1471790303,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570356, @Dereckson wrote:
+> The issue is how to sort them between Wikimedia-specific messages and universal messages for every wikis?
+
+I want it for specific wiki, ur.wiki",1471787975,PHID-USER-xfrkgxsnlepm7r3bx43d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",The issue is how to sort them between Wikimedia-specific messages and universal messages for every wikis?,1471784540,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Is this possible to move mediawiki: namespace translations to translatewiki.net? Previously we had translated huge amount of mediawiki software strings locally. Some have been outdated but many of them are useful. And now we would like to continue translate on translatewiki. ,1471752189,PHID-USER-xfrkgxsnlepm7r3bx43d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVafiUcdX4d8bmU7pfbN} [2016-08-18T21:23:09Z] <Dereckson> Run deleteEqualMessages maintenance script on eswikibooks, eswikiquote, eswikisource, eswiktionary and eswikiversity (T45917)",1471555389,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Done.
+
+{P3852}",1471555245,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I'm handling the es part, then I'll reassign the task to Krinkle for review and closure.",1471554376,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Doing a quick check, I've encountered the same problems at the rest of Spanish language projects, as such I propose to run the script on:
+
+* eswikibooks
+* eswikiquote
+* eswikisource
+* eswiktionary
+* eswikiversity
+
+Thank you.",1471552138,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Requesting the script to be run on es.wikisource as per https://es.wikisource.org/w/index.php?title=Especial%3ATodosLosMensajes&prefix=&filter=modified&lang=es&limit=5000
+
+Lots of local messages equal to the source in TWN.
+
+Thank you!",1471551990,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVUIBSXNgCrwkbTdmSYI} [2016-05-31T18:13:23Z] <Krinkle> mwscript deleteEqualMessages.php --wiki hrwikibooks (T45917)",1464718403,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVUDAGmt1EdYBLP_75C3} [2016-05-30T18:50:06Z] <Krinkle> mwscript deleteEqualMessages.php --wiki nvwiki (T45917)",1464634207,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTknVjG1EdYBLP_72u_} [2016-05-24T21:13:17Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki mrwiki (T45917)",1464124398,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTkYTJ_gCrwkbTdmPef} [2016-05-24T20:07:35Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki diqwiki (T45917)",1464120456,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTkVf57sSQjJM_mrtuk} [2016-05-24T19:55:21Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki cywiktionary (T45917)",1464119721,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTkTHRTgCrwkbTdmPdj} [2016-05-24T19:44:56Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki warwiki (T45917)",1464119096,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTjg8HA1EdYBLP_72ig} [2016-05-24T16:05:43Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki fiwikinews (T45917)",1464105943,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQM0ZS2D0x0K5Df_Smj} [2016-04-12T23:32:22Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki elwiki (T45917)",1460503942,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHoFN2gCrwkbTdl-Hq} [2016-04-11T23:20:28Z] <Krinkle> mwscript deleteEqualMessages.php --wiki idwiki (T45917)",1460416828,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHmQ5I1EdYBLP_7mNA} [2016-04-11T23:12:31Z] <Krinkle> mwscript deleteEqualMessages.php --wiki zh_classicalwiki (T45917)",1460416352,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHOvKAD0x0K5Df_R_k} [2016-04-11T21:29:44Z] <Krinkle> mwscript deleteEqualMessages.php --wiki bgwikiquote (T45917)",1460410184,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHOuy9gCrwkbTdl-ET} [2016-04-11T21:29:42Z] <Krinkle> mwscript deleteEqualMessages.php --wiki frwikibooks (T45917)",1460410183,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHDv3n1EdYBLP_7mIC} [2016-04-11T20:41:43Z] <Krinkle> mwscript deleteEqualMessages.php --wiki plwiki (T45917)",1460407304,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQDoTWOD0x0K5Df_RpN} [2016-04-11T04:42:57Z] <Krinkle> mwscript deleteEqualMessages.php --wiki shwiki (T45917)",1460349777,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQCZCaKD0x0K5Df_RoZ} [2016-04-10T22:56:38Z] <Krinkle> mwscript deleteEqualMessages.php --wiki srwiki (T45917)",1460328999,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQCP56LgCrwkbTdl9qq} [2016-04-10T22:16:44Z] <Krinkle> mwscript deleteEqualMessages.php --wiki yowiki (T45917)",1460326604,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQCLBWxgCrwkbTdl9qj} [2016-04-10T21:55:24Z] <Krinkle> mwscript deleteEqualMessages.php --wiki trwikimedia (T45917)",1460325324,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVPepXiHD0x0K5Df_P7O} [2016-04-04T00:21:39Z] <Krinkle> mwscript deleteEqualMessages.php --wiki ruwiki (T45917)",1459729299,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVPeRhqty3uubrspqdd0} [2016-04-03T22:37:29Z] <Krinkle> mwscript deleteEqualMessages.php --wiki eswiki --lang-code ca (T45917)",1459723049,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVPeRglHy3uubrspqddz} [2016-04-03T22:37:25Z] <Krinkle> mwscript deleteEqualMessages.php --wiki eswiki (T45917)",1459723046,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVPLTHP8y3uubrspqcNy} [2016-03-31T06:11:38Z] <Krinkle> mwscript deleteEqualMessages.php --wiki zh_min_nanwiki (T45917)",1459404699,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVOnA0SngCrwkbTdl4Pi} [2016-03-24T05:05:22Z] <Krinkle> mwscript deleteEqualMessages.php --wiki zhwikiquote (T45917 , P1988)",1458795922,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> Has this now all been done and resolved?
+
+Not that I know.",1452678979,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Has this now all been done and resolved?,1452622160,PHID-USER-lumvg23bxmfbvekr2fbo,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#1841781, @Jdforrester-WMF wrote:
+> What is left to do here?
+
+Running on all wikis.",1449002935,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",What is left to do here?,1448988458,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+rowiki: 432 pages
+zhwiktionary: 143 pages
+fywiktionary: 65 pages
+pmswiki: 391 pages
+```",1441593011,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+rowiki: 432 pages
+zhwiktionary: 143 pages
+fywiktionary: 65 pages
+```",1441556987,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+rowiki: 432 pages
+zhwiktionary: 143 pages
+```",1440638349,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+rowiki: 432 pages
+```",1440638311,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+```",1440615416,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+```",1440521878,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Maybe it can be used to clean old translations such as [[https://meta.wikimedia.org/w/index.php?title=Special%3AAllMessages&prefix=&filter=modified&lang=eu&limit=5000|these ones]] at Meta? (included other langs). Thread opened at Babel.,1439156148,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran it for a two more wikis after inspecting the dry-run:
+
+```
+cewiki: 243 pages
+sawiki: 58 pages
+```",1434167492,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran it for these wikis:
+```
+mediawikiwiki
+* [[MediaWiki:Wikilove-barnstar-resilient-desc]]
+* [[MediaWiki:Wikilove-barnstar-tireless-desc]]
+* [[MediaWiki:Code-referenced]]
+* [[MediaWiki:Rss-item]]
+
+nlwiki
+* [[MediaWiki:Logentry-block-block]]
+* [[MediaWiki:Logentry-block-unblock]]
+* [[MediaWiki:Centralauth-uwbr-name]]
+* [[MediaWiki:Centralauth-uwbr-registration]]
+* [[MediaWiki:Centralauth-uwbr-editcount]]
+* [[MediaWiki:Centralauth-uwbr-intro]]
+* [[MediaWiki:Sandboxlink-subpage-name]]
+* [[MediaWiki:Sandboxlink-portlet-label]]
+
+commonswiki: 0
+metawiki: 0
+```",1431010787,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#1152012, @Krenair wrote:
+> Is there a reason we haven't done this on all wikis now?
+
+No good one. It's fine to proceed.",1427358499,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Is there a reason we haven't done this on all wikis now?
+
+{P436}",1427334122,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for commonswiki per my own request there as sysop (could've deleted them by hand):
+
+
+> 279 pages in the MediaWiki namespace override messages.
+> 1 pages are equal to the default message (+ 0 talk pages).
+> 
+> List:
+> * [[MediaWiki:Visualeditor-ca-editsource]]",1409147479,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Spread over the past two weeks, mwscript deleteEqualMessages.php was ran[1] on the following wikis while performing other routine maintenance and interface fixes:
+
+abwiki
+afwiki
+afwikiquote
+alswiki
+bat-smgwiki
+bpywiki
+cswiki
+cswikiversity
+cswiktionary
+cvwiki
+lnwiki
+nahwiktionary
+newwiki
+nlwiki
+rowiktionary
+simplewiki
+sqwiki
+suwiki
+tlwiki
+
+[1] https://wikitech.wikimedia.org/wiki/Server_admin_log",1399337202,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to Nemo from comment #26)
+> Thanks! I'd suggest to avoid touching talk pages, so that the operation is
+> truly no-op. Those talk pages are unlikely to exist but wikis have different
+> policies on the matter.
+
+Good point. We have orphan tools to detect those and are indeed not always trivial/uncontroversial. Will keep them from now on.",1398283925,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Thanks! I'd suggest to avoid touching talk pages, so that the operation is truly no-op. Those talk pages are unlikely to exist but wikis have different policies on the matter.",1398282173,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran mwscript deleteEqualMessages.php --delete --delete-talk on the following wikis:
+
+* afwiki
+* amwiki
+* brwiki
+* euwiktionary
+* gvwiki
+* hrwiki
+* hrwiktionary
+* iawiki
+* miwiki
+* mlwiki",1398281729,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Done!
+
+$ mwscript deleteEqualMessages.php --wiki wuuwiki --delete
+
+Checking for pages with default message...
+... fetching message info for content language
+352 pages in the MediaWiki namespace override messages.
+110 pages are equal to the default message (+ 0 talk pages).
+
+...deleting equal messages (this may take a long time!)...
+* [[MediaWiki:Sitematrix]]
+* [[MediaWiki:Cite]]
+* [[MediaWiki:Searchfulltext]]
+* [[MediaWiki:Createarticle]]
+* [[MediaWiki:Categorytree-mode-categories]]
+* [[MediaWiki:Categorytree-expand]]
+* [[MediaWiki:Categorytree-no-pages]]
+* [[MediaWiki:Sitesupport]]
+* [[MediaWiki:Fri]]
+* [[MediaWiki:January-gen]]
+* [[MediaWiki:March-gen]]
+* [[MediaWiki:May-gen]]
+* [[MediaWiki:September-gen]]
+* [[MediaWiki:October-gen]]
+* [[MediaWiki:November-gen]]
+* [[MediaWiki:Mypage]]
+* [[MediaWiki:History short]]
+* [[MediaWiki:Print]]
+* [[MediaWiki:Mainpage]]
+* [[MediaWiki:Nstab-template]]
+* [[MediaWiki:Logout]]
+* [[MediaWiki:Userlogout]]
+* [[MediaWiki:Notloggedin]]
+* [[MediaWiki:Loginerror]]
+* [[MediaWiki:Loginsuccesstitle]]
+* [[MediaWiki:Wrongpassword]]
+* [[MediaWiki:Bold sample]]
+* [[MediaWiki:Bold tip]]
+* [[MediaWiki:Savearticle]]
+* [[MediaWiki:Loginreqtitle]]
+* [[MediaWiki:Loginreqlink]]
+* [[MediaWiki:Yourdiff]]
+* [[MediaWiki:Nohistory]]
+* [[MediaWiki:Nextrevision]]
+* [[MediaWiki:Rev-delundel]]
+* [[MediaWiki:Prevn]]
+* [[MediaWiki:Prefs-personal]]
+* [[MediaWiki:Prefs-rc]]
+* [[MediaWiki:Prefs-watchlist]]
+* [[MediaWiki:Prefs-watchlist-days]]
+* [[MediaWiki:Prefs-watchlist-edits]]
+* [[MediaWiki:Saveprefs]]
+* [[MediaWiki:Searchresultshead]]
+* [[MediaWiki:Savedprefs]]
+* [[MediaWiki:Yourlanguage]]
+* [[MediaWiki:Badsig]]
+* [[MediaWiki:Userrights-user-editname]]
+* [[MediaWiki:Rclistfrom]]
+* [[MediaWiki:Diff]]
+* [[MediaWiki:Hist]]
+* [[MediaWiki:Show]]
+* [[MediaWiki:Minoreditletter]]
+* [[MediaWiki:Newpageletter]]
+* [[MediaWiki:Uploadbtn]]
+* [[MediaWiki:Uploadnologin]]
+* [[MediaWiki:Uploaderror]]
+* [[MediaWiki:Uploadlog]]
+* [[MediaWiki:Uploadlogpagetext]]
+* [[MediaWiki:Filedesc]]
+* [[MediaWiki:Uploadedfiles]]
+* [[MediaWiki:Uploadwarning]]
+* [[MediaWiki:Savefile]]
+* [[MediaWiki:Destfilename]]
+* [[MediaWiki:Uploadnewversion-linktext]]
+* [[MediaWiki:Download]]
+* [[MediaWiki:Listredirects]]
+* [[MediaWiki:Randompage]]
+* [[MediaWiki:Statistics]]
+* [[MediaWiki:Brokenredirects]]
+* [[MediaWiki:Popularpages]]
+* [[MediaWiki:Mostlinked]]
+* [[MediaWiki:Mostlinkedcategories]]
+* [[MediaWiki:Mostimages]]
+* [[MediaWiki:Shortpages]]
+* [[MediaWiki:Longpages]]
+* [[MediaWiki:Listusers]]
+* [[MediaWiki:Newpages-username]]
+* [[MediaWiki:Log]]
+* [[MediaWiki:Emailsend]]
+* [[MediaWiki:Emailsent]]
+* [[MediaWiki:Emailsenttext]]
+* [[MediaWiki:Watchthispage]]
+* [[MediaWiki:Unwatchthispage]]
+* [[MediaWiki:Created]]
+* [[MediaWiki:Confirm]]
+* [[MediaWiki:Deletionlog]]
+* [[MediaWiki:Rollback]]
+* [[MediaWiki:Rollback short]]
+* [[MediaWiki:Rollbackfailed]]
+* [[MediaWiki:Protectlogpage]]
+* [[MediaWiki:Restriction-edit]]
+* [[MediaWiki:Restriction-move]]
+* [[MediaWiki:Undeletepage]]
+* [[MediaWiki:Mycontris]]
+* [[MediaWiki:Blocklink]]
+* [[MediaWiki:Blocklogpage]]
+* [[MediaWiki:Movepagebtn]]
+* [[MediaWiki:Cantmove-titleprotected]]
+* [[MediaWiki:Thumbnail-more]]
+* [[MediaWiki:Newimages]]
+* [[MediaWiki:Variantname-zh-tw]]
+* [[MediaWiki:Watchlistall2]]
+* [[MediaWiki:Namespacesall]]
+* [[MediaWiki:Descending abbrev]]
+* [[MediaWiki:Table pager next]]
+* [[MediaWiki:Table pager prev]]
+* [[MediaWiki:Table pager first]]
+* [[MediaWiki:Table pager limit]]
+* [[MediaWiki:Autoredircomment]]
+* [[MediaWiki:Version]]
+
+done!",1395422702,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",This was requested to be run on wuuwiki: https://meta.wikimedia.org/w/index.php?title=Steward_requests/Miscellaneous&oldid=7913568#Remove_useless_system_messages_on_wuu_wikipedia,1395422161,PHID-USER-omdcggvudfkuawipp23i,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Krinkle, are you still planning to work on this?",1395223025,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","The short version of the long story (that is partially outlined in previous comments by all of you) is that it:
+
+* Was never consistent to be begin with.
+* It has changed over time.
+  So we can't reliably know now what to do with a message. You'd have to account
+  for deployment dates for different wikis and assume a community member
+  intentionally left a message override untouched knowing the new behaviour.
+  More likely it was forgotten about and is actually still assuming the old logic. 
+* It can vary by message whether it is blankable or disableable.
+
+If the code calls isBlank first (like Sitenotice) then it can be blanked with '' without leaving a gap in the interface because the feature checks it first.
+
+If the code calls isDisabled first, and then falls back or something, then it can be blanked with '' or '-' and it will use the default.
+
+However by far the default behaviour for the majority of messages is that if you create a local page, it replaces the message with that page. And if you put '' or '-' in it, it will appear as a gap in the interface.
+
+Either way, those pages are there with empty content for a reason, so it doesn't make sense to delete them en mass as part of this maintenance script.",1381358925,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Blanking a message no longer disables it (bug 14176), so all pre-12.06.2013 blankings should be transformed in deletions.",1381349348,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I'm confused by comment #12 and #13 then, I understood from them that '' no longer meant default.",1381346722,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #16)
+> > Even the ""redundant"" messages getting deleted makes me a little sad, given
+> > how useful some of that page history can be (including being linked from active
+> > bug reports). But I understand that it's better future-proofing. Alas.
+> 
+> I remember blanking some MediaWiki messages precisely to use the default but
+> keep the history.
+> Maybe the script should edit the messages to whatever is used now to mean
+> ""use
+> the default"" (""-"" ?) when there are several edits to the page.
+
+Sometimes '', sometimes '-' (handled by Message:isBlank and Message::isDisabled) however those are not generic APIs. The message system does not use these methods. They are available for local code to use if they want to.
+
+So there's no way of knowing whether an individual message ""supports"" that behaviour, and even then we currently have some use '' and some use '-' ('' is a safe bet for both).",1381345858,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #15)
+> I've run this on a single wiki where I'm also a local sysop (nlwiki) and
+> noticed the script has a minor flaw.
+> 
+> It incorrectly deleted MediaWiki:Sitenotice.
+
+Fixed in I5b416cda25a3641862df9919c46ae59ad5d5d6e0.",1381345737,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> Even the ""redundant"" messages getting deleted makes me a little sad, given
+> how useful some of that page history can be (including being linked from active
+> bug reports). But I understand that it's better future-proofing. Alas.
+
+I remember blanking some MediaWiki messages precisely to use the default but keep the history.
+Maybe the script should edit the messages to whatever is used now to mean ""use the default"" (""-"" ?) when there are several edits to the page.",1381345333,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I've run this on a single wiki where I'm also a local sysop (nlwiki) and noticed the script has a minor flaw.
+
+It incorrectly deleted MediaWiki:Sitenotice (if it is empty), which is undesirable. So we should probably change the script to make an exception for empty messages.
+
+Those are most unlikely to change anyway because there is no message content to update or change, it is empty.",1381345054,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #13)
+> (In reply to comment #12)
+>> If a script to delete empty messages existed in the past, we could've run it
+>> once globally after we reverted the feature to have blank messages mean
+>> default. But it has been to long to do this now.
+> 
+> What do you mean too long? It's been today for Wikipedias (1.22wmf7). Blank
+> message has always meant ""equal to default"", so it doesn't seem out of scope
+> for the script, which should be run by third parties before upgrading to
+> MediaWiki 1.22.
+
+Not always. The behavior has switched a few times now.
+
+There's no good answer here. It's impossible to determine intent simply by page_len being equal to 0. I tend to agree with Krinkle that it's better to be cautious here.
+
+Even the ""redundant"" messages getting deleted makes me a little sad, given how useful some of that page history can be (including being linked from active bug reports). But I understand that it's better future-proofing. Alas.
+
+> [...] [[MediaWiki 1.22]] [...]
+
+You mean [[mw:MediaWiki 1.22]], of course.",1371778016,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #12)
+> If a script to delete empty messages existed in the past, we could've run it
+> once globally after we reverted the feature to have blank messages mean
+> default. But it has been to long to do this now.
+
+What do you mean too long? It's been today for Wikipedias (1.22wmf7). Blank message has always meant ""equal to default"", so it doesn't seem out of scope for the script, which should be run by third parties before upgrading to MediaWiki 1.22.
+If you consider it out of scope I'd file a bug for another script to be created, but nobody would be working on it so it would become too late so I'll just add a warning on [[MediaWiki 1.22]] and let sysops sort it out manually.",1371761038,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #11)
+> (In reply to comment #10)
+> > Related URL: https://gerrit.wikimedia.org/r/64991 (Gerrit Change
+> > I2680413c276365a44c935a6f6fdd740daa86341e)
+> 
+> Merged a month ago.
+> 
+> Given bug 14176 (bug 49793), the script should also delete blank messages and
+> be run as soon as possible; unless a separate script is prepared and run for
+> that only.
+
+Since blank messages no longer mean showing the default, deleting them seems inappropriate.
+
+Yes, there are likely some pages out there that are blank and currently causing bugs due the message being empty instead of the default. However it would be a mistake to unconditionally delete all blank pages in the MediaWiki namespace.
+
+For maintenance scripts like deleteEqualMessages it is important that they do not affect the interface. It should only delete things that are non-controversial.
+
+If a script to delete empty messages existed in the past, we could've run it once globally after we reverted the feature to have blank messages mean default. But it has been to long to do this now. And one could also argue that it was dangerous even then because there might be existing pages that are blank for other reasons.",1371758984,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #10)
+> Related URL: https://gerrit.wikimedia.org/r/64991 (Gerrit Change
+> I2680413c276365a44c935a6f6fdd740daa86341e)
+
+Merged a month ago.
+
+Given bug 14176 (bug 49793), the script should also delete blank messages and be run as soon as possible; unless a separate script is prepared and run for that only.",1371757399,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Related URL: https://gerrit.wikimedia.org/r/64991 (Gerrit Change I2680413c276365a44c935a6f6fdd740daa86341e),1369264493,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Related URL: https://gerrit.wikimedia.org/r/62159 (Gerrit Change I2680413c276365a44c935a6f6fdd740daa86341e),1367596599,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #7)
+> (In reply to comment #6)
+> > I could run it, but I'd like to not execute my own request without a little
+> > more consensus from people.
+> > 
+> > They aren't permanent or hidden actions in any way (regular wiki deletions,
+> > it's a bot basically), but they would be a horror to undo.
+> > 
+> 
+> Can you dry run it and make a list of the pages that will be deleted so they
+> can be reviewed before deletion?
+
+I'm not sure what there is to review regarding individual pages. They all follow the same description, whatever reasoning one would use about them doesn't specify for any particular page:
+
+ Pages in the MediaWiki namespace that exist and override a system message
+ of which the wiki page contents are equal to the system message of the site
+ language (in other words, there is no longer a reason fo the override page
+ to exist).
+
+Deleting these pages has no visible effect as the effective value of the interface message will still be the same.
+
+The advantage is saving maintenance work later on by not having to update these messages when the software upgrades, and for consistency across wikis.
+
+A common scenario is the following:
+* 3 wikis in language x
+* 1 of the wikis overrides a message (making an improvement)
+* the message is fixed in translatewiki
+* the message update is deployed
+* users of all 800 wikis using language x now see the new version of the message
+* another update is made to the message and deployed
+* all wikis use it, except the wiki where the first change came from which is now out of sync without it being intentionally so.
+
+
+Alright, I'm biased as it was my own idea. But that doesn't mean the script itself has to be controversial. I'll run this next week if no objections are raised before then.",1365712467,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","**Thehelpfulonewiki** wrote:
+
+(In reply to comment #6)
+> I could run it, but I'd like to not execute my own request without a little
+> more consensus from people.
+> 
+> They aren't permanent or hidden actions in any way (regular wiki deletions,
+> it's a bot basically), but they would be a horror to undo.
+> 
+
+Can you dry run it and make a list of the pages that will be deleted so they can be reviewed before deletion?",1362516836,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I could run it, but I'd like to not execute my own request without a little more consensus from people.
+
+They aren't permanent or hidden actions in any way (regular wiki deletions, it's a bot basically), but they would be a horror to undo.
+
+I wouldn't know why someone would disagree, but then again, there've only been a few people involved so far that all agreed.",1362512294,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","**Thehelpfulonewiki** wrote:
+
+Any progress on running this?",1362038010,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",See bug 43915.,1358895498,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #2)
+> Can the old [[User:MediaWiki default]] be used for this task?
+
+The script I wrote uses that user and ensures it is in the bot group  (that is, add if not present) before it runs.
+
+(In reply to comment #2)
+> I understand this is going to affect messages pre-betawiki.
+
+No, it is not.
+
+(In reply to comment #2)
+> However I  what would happen with messages that we decided to customize
+
+Nothing.",1358895477,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Can the old [[User:MediaWiki default]] be used for this task? (Please note that since it does not run since 2006 it has been deflagged from the bot group from some projects).
+
+I understand this is going to affect messages pre-betawiki. However I wonder what would happen with messages that we decided to customize localy. Those should not be deleted as they're likely going to be recreated later... Only a minor issue, though.",1358729054,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","This is a subset of the general task ""clean-up local messages"".
+What we have now:
+[[mw:Localisation#Old_local_translation_system]]
+https://toolserver.org/~robin/?tool=cleanuplocalmsgs",1358041581,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+Batch Parsoid's API requests,"We should amortize per-request overheads by batching API requests.
+
+AFAIK there is no generic batching support in the API currently, and adding it would probably be a bit too time-consuming for now. Instead we can add a unique string as a separator, for example something like 
+
+<nowiki>d41d8cd98f00b204e9800998ecf8427e</nowiki>
+
+This would work for for action=expandtemplates and action=parse which are the main workarounds we currently use. In the longer term we should switch to explicit methods that don't involve parsing wikitext, which is probably also a good moment to add real batching support.
+
+Decisions about batch sizes could be based on wikitext source size initially (based on the assumption that templates with a bazillion parameters also take longer to expand). A fixed number of templates per batch would be another simple alternative. Really fancy batching could use stats of previous processing times (returned by the PHP preprocessor per transclusion and stored in HTML).
+
+Ideally we would also enforce separation between batched requests to avoid non-deterministic behavior for stateful extensions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1357943520,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_description,resolved
+Batch Parsoid's API requests,"@ssastry, good point re load. Added the parse request rate for completeness. Also agreed re needing more data.",1443744632,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"@ssastry, good point re load. Added the parse request rate for completeness.",1443744450,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"@subbu, good point re load. Added the parse request rate for completeness.",1443744437,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"You need to account for the spikiness in the load too. see http://grafana.wikimedia.org/#/dashboard/db/parsoid-timing-wt2html (zoom out to a 7-day window and look how the request rate was much closer to 200 reqs / sec last few days compared to < 150 reqs / sec earlier in the week (before batching was enabled). I am fairly confident that parsing latencies haven't been affected adversely based on monitoring this last couple days. But, I think we have to wait and watch this over the next couple weeks before we have a truer picture. 
+
+On the other hand, if you look at ganglia graphs for the API cluster, you do see a reduction in network traffic in/out of it (despite the higher parse load on the Parsoid end) + a downward trend in the load there.",1443743973,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th, around 16:14 UTC. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}
+
+Smoothed parse request rate:
+{F2652092}",1443744961,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th, around 16:14 UTC. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}
+
+Smoothed parse request rate:
+{F2652078}",1443744831,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th, around 16:14 UTC. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}
+
+Parse request rate:
+{F2652035}",1443744407,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th, around 16:14 UTC. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443744243,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443743533,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443743341,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443743180,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"12-hour median latencies as seen by RESTBase in the last days:
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443743150,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Change 227208 merged by jenkins-bot:
+Batch MW parser and imageinfo API requests
+
+[[https://gerrit.wikimedia.org/r/227208]]",1439607321,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Change 227208 had a related patch set uploaded (by Tim Starling):
+Batch MW parser and imageinfo API requests
+
+[[https://gerrit.wikimedia.org/r/227208]]
+",1438000591,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Sounds good to me since it looks like it keeps complexity down implementing this since the code can be customized to Parsoid's needs. But, once this is all ironed out and live, we should update docs for 3rd party Parsoid installs about requirement (unless batching can be made optional on the Parsoid end).",1437963707,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"@tstarling +1 from me. Your rationale covers all the things I would have brought up (and more). Sorry for being slow, @ssastry is vacationing and I'm not sure if @cscott's been following this thread.",1437781827,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,@tstarling +1 from me. Your rationale covers all the things I would have brought up (and more). Sorry for being @ssastry is vacationing and I'm not sure if @cscott's been following this thread.,1437781808,PHID-USER-gxcjmjpejlhfnrquksm2,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"No response, so I committed the MW extension to https://gerrit.wikimedia.org/r/#/c/226670/
+
+Still ironing out a couple of issues on the client side. A changeset will appear soon.",1437781171,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Please comment on the idea of doing batch parsing in an extension instead of in a core API module. I'd like to know if it sounds like a good idea before I create the Gerrit repository.
+
+The reasons for doing this were:
+* Simpler design, due to the smaller number of clients/stakeholders. Code size is only 135 physical lines, with no internal API calls, compared to 800 for action=parse and 218 for action=expandtemplates.
+* Allows the action=parse and action=expandtemplates modules to be easily combined. No need to break my head trying to think about generic Lua frontend batch processing APIs which allow arbitrary actions to be combined.
+* An API for parsoid use only can easily be policed for misuse or DoS, e.g. with IP-based access control. No need for restrictive server-side batch size limits which may interfere with optimal performance.
+* Expedient output format, based on b/c with action=parse and action=expandtemplates, which allows the client to share code with the fallback case.
+* Forking the API provides an easy path towards more aggressive integration with the MW parser, for example output annotation hooks.
+
+The proposed extension name is ParsoidBatchAPI.",1437369948,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"I've written a client-side ""batcher"" class hierarchy, and a MediaWiki extension which does server-side batches of mixed parse and preprocess operations. The impact on both client and server CPU time is substantial, as expected from the discussion on T88915. For [[List of 20th-century classical composers]] with a batch size of 50, node CPU time went from 54s to 29s, and HHVM CPU time went from 216s to 70s.
+
+The impact on latency can't easily be measured in my current test setup.
+
+Unfortunately, it was necessary to treat each item in the batch as a distinct parse operation, with clearState(), since Parsoid wishes to know which categories are generated by which templates. This causes a number of useful caches to be discarded at the start of each batch item. This may be the reason why the HHVM CPU time is still 70s, even though running the text through expandtemplates as a whole takes only 10s. Increasing the batch size from 50 to 500 only reduced the HHVM CPU time to 65s.
+
+If clearState() was not done, it would not be easy to determine which template caused the addition of a given category. Consider the case of a template which is invoked with no arguments, which causes a tracking category to be added. If this template is invoked more than once in a parse operation, the expansion cache will prevent ParserOutput::addCategory() from being called on the second and subsequent invocations. This implies that the expansion cache would need to be disabled or rewritten to support this Parsoid use case.",1437368829,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"We should also keep in mind the effect of batching on overall system reliability. In {T97204} I advocate for tight timeouts in backend services, combined with no client retries when encountering a server timeout. In general, batching makes it harder to establish tight timeouts on end points. We should thus limit it to end points where each batch action has a very predictable processing time, and the overall batch will always complete within a reasonable timeout (< 60s).",1429996047,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"We should also keep in mind the effect of batching on overall system reliability. In {T97204} I advocate for tight timeouts in backend services, combined with no client retries when encountering a server timeout. In general, batching makes it harder to establish tight timeouts on end points. We should thus limit it to end points where each batch action has a very limited processing time, and the overall batch will always complete within a reasonable timeout (< 60s).",1429995562,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,I concur.,1424214020,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"It is good thing to reduce the load on the API cluster, but I don't think this task should be a VE Q3 blocker. 
+
+Right now,
+(a) Parsoid tracks all edits -- so there is going to be no change in Parsoid parsing load (and hence API load) even if VE is enabled everywhere (assuming edit rate stays the same).
+(b) The current load on the API cluster is not problematic that forces us to work on this for VE deployment.
+
+So, I suggest that this task be removed from the VisualEditor Q3 Blockers workboard since there are other more higher priority issues to fix in Parsoid land.",1424212155,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,">>! In T45888#978615, @tstarling wrote:
+> The main reason I am leaning towards the internal batcher is because some of the queues will have very little traffic on them, e.g. queues for small wikis. This makes for some uncomfortable tradeoffs when you try to set the dispatch timeout. Consider that parse operations are observed to take ~10s and issue ~100 API requests -- this implies a mean interval between requests on the order of 100ms, and a timeout of at least that much if there is to be any throughput benefit from batching at all. That is quite a long time to wait. From a throughput perspective, the optimal dispatch timeout may be more than 1s.
+
+The amount of batching we can achieve on the long tail is bounded by the maximum latency penalty we are willing to introduce. A global batcher can combine requests from different API clients (not just parsoid), and should thus result in lower average latencies by filling up batches quickly (or reaching a given batching ratio with a lower maximum latency penalty).
+
+Also keep in mind that with selective re-expansion of templates those requests will become less common, which will make the single-client batch even less effective, as there are just less requests to combine within the time window.
+
+> Also, note that Parsoid currently performs API requests with keep-alive disabled. With default socket options, this implies a limit of 470 API requests per second per client server before local port exhaustion occurs, as in T75949. Batching internally, without the involvement of TCP, avoids this limit.
+
+The number of connections has not been an issue in practice & would not change. On the proxy we could also enable [SPDY support](https://github.com/indutny/node-spdy), which reduces the number of connections to one per client & removes some per-request overhead. That said, I think the `Connection: close` bit can be removed. It was a work-around from an early node version IIRC, and is no longer needed.",1421339610,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,">>! In T45888#978615, @tstarling wrote:
+> The main reason I am leaning towards the internal batcher is because some of the queues will have very little traffic on them, e.g. queues for small wikis. This makes for some uncomfortable tradeoffs when you try to set the dispatch timeout. Consider that parse operations are observed to take ~10s and issue ~100 API requests -- this implies a mean interval between requests on the order of 100ms, and a timeout of at least that much if there is to be any throughput benefit from batching at all. That is quite a long time to wait. From a throughput perspective, the optimal dispatch timeout may be more than 1s.
+
+The amount of batching is bounded by the maximum latency penalty we are willing to introduce. A global batcher can combine requests from different API clients (not just parsoid), and should thus result in lower average latencies by filling up batches quickly (or reaching a given batching ratio with a lower maximum latency penalty).
+
+Also keep in mind that with selective re-expansion of templates those requests will become less common, which will make the single-client batch even less effective, as there are just less requests to combine within the time window.
+
+> Also, note that Parsoid currently performs API requests with keep-alive disabled. With default socket options, this implies a limit of 470 API requests per second per client server before local port exhaustion occurs, as in T75949. Batching internally, without the involvement of TCP, avoids this limit.
+
+The number of connections has not been an issue in practice & would not change. On the proxy we could also enable [SPDY support](https://github.com/indutny/node-spdy), which reduces the number of connections to one per client & removes some per-request overhead. That said, I think the `Connection: close` bit can be removed. It was a work-around from an early node version IIRC, and is no longer needed.",1421339535,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"The two main implementation options are: a batcher internal to parsoid, and a shared node.js batcher service. The internal batcher would operate roughly as follows:
+
+* Instead of having the token handlers directly dispatch HTTP requests, they would send their requests to a batcher service, which would be local to the current parse operation. The batcher API would be slightly different to the HTTP API, since it needs to be able to easily aggregate titles, and the batcher will take over responsibility for HTTP protocol details such as timeouts.
+* If the batch is full, the request can be dispatched on the next attempted queue insertion.
+* If Parsoid returns to the event loop with requests queued in the batch but not sent, the request could permanently hang. So in relevant code paths prior to returning to the event loop, Parsoid needs notify the batcher, giving it a last chance to check if there are any batch requests queued so that it can dispatch them.
+* Additionally, a timeout would be prudent, allowing Parsoid to recover from accidental return to the event loop without notification.
+
+Gabriel suggested an external batcher which, if I understand his proposal correctly, would operate as follows:
+
+* One cluster-wide batch queue per (wiki, action) tuple. 
+* Requests to the proxy would be held in the batch queue until either it fills, or some specified timeout (e.g. 10ms) is reached. Then the batch query would be sent to the MW backend.
+* While a request is waiting in the batch queue, and while it is waiting for the backend response, the client connections, one per item, would be held open. Responses would be sent to these clients after the batch query returns from the backend.
+* This architecture avoids the need for significant changes inside Parsoid.
+
+The main reason I am leaning towards the internal batcher is because some of the queues will have very little traffic on them, e.g. queues for small wikis. This makes for some uncomfortable tradeoffs when you try to set the dispatch timeout. Consider that parse operations are observed to take ~10s and issue ~100 API requests -- this implies a mean interval between requests on the order of 100ms, and a timeout of at least that much if there is to be any throughput benefit from batching at all. That is quite a long time to wait. From a throughput perspective, the optimal dispatch timeout may be more than 1s.
+
+Explicit notification of the idle event avoids severe tradeoffs between batch size and latency. It can be implemented in either the internal or external design. But the need for idle event notification would reduce the attractiveness of the external batcher -- it would make the service stateful and its advantages in simplicity on the Parsoid side would be reduced. There is a risk that idle events could be lost anyway, and a timeout incurred, due to exhaustion of the client connection limit (globalAgent.maxSockets).
+
+Also, note that Parsoid currently performs API requests with keep-alive disabled. With default socket options, this implies a limit of 470 API requests per second per client server before local port exhaustion occurs, as in T75949. Batching internally, without the involvement of TCP, avoids this limit.",1421295841,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"The two main implementations are: a batcher internal to parsoid, and a shared node.js batcher service. The internal batcher would operate roughly as follows:
+
+* Instead of having the token handlers directly dispatch HTTP requests, they would send their requests to a batcher service, which would be local to the current parse operation. The batcher API would be slightly different to the HTTP API, since it needs to be able to easily aggregate titles, and the batcher will take over responsibility for HTTP protocol details such as timeouts.
+* If the batch is full, the request can be dispatched on the next attempted queue insertion.
+* If Parsoid returns to the event loop with requests queued in the batch but not sent, the request could permanently hang. So in relevant code paths prior to returning to the event loop, Parsoid needs notify the batcher, giving it a last chance to check if there are any batch requests queued so that it can dispatch them.
+* Additionally, a timeout would be prudent, allowing Parsoid to recover from accidental return to the event loop without notification.
+
+Gabriel suggested an external batcher which, if I understand his proposal correctly, would operate as follows:
+
+* One cluster-wide batch queue per (wiki, action) tuple. 
+* Requests to the proxy would be held in the batch queue until either it fills, or some specified timeout (e.g. 10ms) is reached. Then the batch query would be sent to the MW backend.
+* While a request is waiting in the batch queue, and while it is waiting for the backend response, the client connections, one per item, would be held open. Responses would be sent to these clients after the batch query returns from the backend.
+* This architecture avoids the need for significant changes inside Parsoid.
+
+The main reason I am leaning towards the internal batcher is because some of the queues will have very little traffic on them, e.g. queues for small wikis. This makes for some uncomfortable tradeoffs when you try to set the dispatch timeout. Consider that parse operations are observed to take ~10s and issue ~100 API requests -- this implies a mean interval between requests on the order of 100ms, and a timeout of at least that much if there is to be any throughput benefit from batching at all. That is quite a long time to wait. From a throughput perspective, the optimal dispatch timeout may be more than 1s.
+
+Explicit notification of the idle event avoids severe tradeoffs between batch size and latency. It can be implemented in either the internal or external design. But the need for idle event notification would reduce the attractiveness of the external batcher -- it would make the service stateful and its advantages in simplicity on the Parsoid side would be reduced. There is a risk that idle events could be lost anyway, and a timeout incurred, due to exhaustion of the client connection limit (globalAgent.maxSockets).
+
+Also, note that Parsoid currently performs API requests with keep-alive disabled. With default socket options, this implies a limit of 470 API requests per second per client server before local port exhaustion occurs, as in T75949. Batching internally, without the involvement of TCP, avoids this limit.",1421295823,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Request batching appears to be simple to implement (~100 lines according to @gwicke) and would cause a substantial decrease in API cluster CPU load. By switching it on only for requests initiated by the job queue, there would be no effect on user latency.
+
+> The problem with general batching is that state in MediaWiki is not very well defined. Several extensions for example keep internal state between calls to tag hooks, and resetting that state between individual requests in a batch would probably produce a similar overhead as the regular per-request setup (30+ms).
+
+No, parser state in MediaWiki is very well-defined, it is defined as the data which is cleared by Parser::clearState(). Extensions which keep internal state hook this function in order to clear their state. MediaWiki is reasonably well-optimised for clearing the parser state, since message parsing does so, often tens of times per request. The overhead is orders of magnitude smaller than the request setup time.
+
+> The current performance numbers combined with several optimizations aimed at avoiding API requests lessened the need for API request batching on our end.
+
+Parsoid is still by far the largest API consumer by CPU time.
+
+> Speeding up individual API requests is a general architectural goal, and should be addressed in that context. Closing this bug as WONTFIX on our end.
+
+I am familiar with MW setup time optimisation, and compared to that large, ongoing effort, Parsoid request batching looks like low-hanging fruit.",1421212316,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"The current performance numbers combined with several optimizations aimed at avoiding API requests lessened the need for API request batching on our end.
+
+Speeding up individual API requests is a general architectural goal, and should be addressed in that context. Closing this bug as WONTFIX on our end.",1370996729,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Adding custom batching support just for template expansion and extension tag calls would really be a workaround, and would add complexity to both clients and the server. If the performance of API requests could be improved in general, we could and should probably avoid that complex workaround in favor of the general solution.
+
+In the longer term, our HTML storage and incremental re-parsing / expansion plans should reduce the number of template expansions and extension calls to a fraction of the level we'll produce initially. The round-trip testing we are currently performing is already close to the edit rate of the English Wikipedia and did not create any issues on the API cluster. A Parsoid installation tracking all edits on all wikis would probably create 2-3 times the number of API requests, which are probably still doable for the current API cluster.
+
+Overall it seems to be a good idea to hold off on a custom batching solution until it is clear that it is really needed and general API performance improvements are not possible.",1361472978,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"For us, the main use cases are template expansion using the PHP preprocessor and the expansion of extension tags. Currently, both of these are only available with a detour through the PHP parser (action=expandtemplates and action=parse respectively), so we'd like to add direct API end points to perform these actions.
+
+A general batching mechanism would probably accept a posted JSON array with each member being an object containing the API arguments for one action (action etc). The return value would be a JSON array with results corresponding to the request array. Instead of relying on positions in an array the client could also supply UIDs for requests which are then mirrored in the result. This could be achieved with an reqid member in each request object.
+
+The problem with general batching is that state in MediaWiki is not very well defined. Several extensions for example keep internal state between calls to tag hooks, and resetting that state between individual requests in a batch would probably produce a similar overhead as the regular per-request setup (30+ms).
+
+In Parsoid, we can work around this issue for our specific use cases by maintaining a whitelist of stateless extensions which can be mixed in a batch without producing non-deterministic output. Non-whitelisted extensions would need to be expanded in a single action=parse request containing all extension tags for that particular extension in page order.",1359928307,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"action=query was built specifically to support batching, but other actions might choose not to implement it. Could you give a very specific example of
+* How the final api request should look like?
+* What do you expect in return.",1359927005,PHID-USER-esrrkc2rlizdlae443wg,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","From user suggestion:
+
+| Heading 1 is very rare on enwiki, and indeed on most other installations.
+| Where it is used (mostly on project discussion pages), it does not usually
+| need to be edited. VisualEditor should not offer it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1356129180,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-whtfrzztibmjwea3vy7l,task_description,resolved
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",This is now merged and will go out later today.,1372274701,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",Related URL: https://gerrit.wikimedia.org/r/69801 (Gerrit Change I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9),1371765581,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",Related URL: https://gerrit.wikimedia.org/r/69801 (Gerrit Change I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9),1371765577,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","I believe that the current list of titles  will quickly be a problem if VE is rolled out to unexperienced users on wikipedia: they will probably use Heading 1 because they don't know it shouldn't be used in 99.9...% of edits.
+When I tried to add a section, I used Heading 1 by default and only changed back to Heading 2 when I saw that the new title was bigger than what I'm used to.
+
+If you think <h1> titles should be kept in VE, it should be separated from the other titles (after other ones). Eventually, would it be possible to make that configurable on a per wiki basis if some wiki really use <h1> as a normal title ?",1371736146,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","> Lots of wikis (e.g.meta) use H1s quite liberally.
+
+I didn't know that, and it seems bad practice. Could you point to some examples? Maybe there is a use case I'm completely overlooking.
+
+
+> | H1: Title
+> | H2: Heading
+> | H3: Sub-heading
+> | H4: Sub-heading
+> | H5: Sub-heading
+> | H6: Sub-heading
+
+I'm not so happy about the name ""Title"", and it being at the top of that list. I would much rather see it buried somewhere at the bottom, maybe as the very last option, and something like ""Duplicate page title"", or at least something that makes it abundantly clear that it is not something that is meant to be used.",1371622689,PHID-USER-n27daagbl3wqf3ghr4nk,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","AzaToth's suggestion is to label as follows:
+
+| H1: Title
+| H2: Heading
+| H3: Sub-heading
+| H4: Sub-heading
+| H5: Sub-heading
+| H6: Sub-heading
+
+The differentiation between H3 - H6 would be only styling. Not sure how I feel about this, but it's certainly ""correct"".",1371598971,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","(In reply to comment #12)
+> Kill the H1s from the editor please. They should really be considered
+> deprecated in the wiki syntax, and aren't something that people should be
+> able to create by accident.
+
+VE is meant to be able to edit all content that's valid. Lots of wikis (e.g. meta) use H1s quite liberally. Discouraging use is fine, but preventing use feels wrong. (Also, what the hell should VE do when it encounters an H1 in the wild, if they were 'disabled'?)",1371598575,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","Kill the H1s from the editor please. They should really be considered deprecated in the wiki syntax, and aren't something that people should be able to create by accident.",1371598260,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","(In reply to comment #10)
+> Instead of messing around with the numbers and having [heading 3 = <h4>], why
+> not rename them ""Heading"", ""Subheading"", and ""Sub-subheading"".
+
+So:
+
+| H1: Title
+| H2: Heading
+| H3: Sub-heading
+| H4: Sub-sub-heading
+| H5: Sub-sub-sub-heading
+| H6: Sub-sub-sub-sub-heading
+
+It might get a bit ridiculous, but I like the idea.",1371160524,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","**ypnypn9** wrote:
+
+(In reply to comment #9)
+> It is unfortunate that wikitext currently allows h1 elements. It shouldn't.
+> It should be the end aim for the visual editor to have feature parity with
+> wikitext, but at the current point it makes it natural to select a heading 1
+> when you really never want to do that. I would prefer to see it not available
+> in the visual editor at all, but as a compromise, I could live with renaming
+> Header 1 to Pageheader, and move it all the way to the bottom of markup
+> elements, and rename header 2 to header 1, etc. That way we don't lose an
+> option in the visual editor that is available in wikitext, and at the same
+> time reduce the chance of people thinking it is an option they may want to
+> choose for a header, which it is not.
+
+Instead of messing around with the numbers and having [heading 3 = <h4>], why not rename them ""Heading"", ""Subheading"", and ""Sub-subheading"".",1371160398,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","It is unfortunate that wikitext currently allows h1 elements. It shouldn't. It should be the end aim for the visual editor to have feature parity with wikitext, but at the current point it makes it natural to select a heading 1 when you really never want to do that. I would prefer to see it not available in the visual editor at all, but as a compromise, I could live with renaming Header 1 to Pageheader, and move it all the way to the bottom of markup elements, and rename header 2 to header 1, etc. That way we don't lose an option in the visual editor that is available in wikitext, and at the same time reduce the chance of people thinking it is an option they may want to choose for a header, which it is not.
+
+At the same time, we may want to think about abandoning the option to make h1 headers in wikitext too, but that makes for a different discussion which should take place in a different place than this bug.",1370004773,PHID-USER-n27daagbl3wqf3ghr4nk,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","Does this really have much to do with the VE to begin with ? It's already allowed. I agree that such is a bad thing but that's a separate story. I guess at most, we could make the H1 option 'non visisble' unless the current element already is exactly of that type.
+
+What would be nice, was if the VE would have more 'guided' heading building. It could warn you about inconsistencies in header levels for instance.",1370000141,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",*** Bug 48955 has been marked as a duplicate of this bug. ***,1369927169,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","**rogerchrisman** wrote:
+
+(In reply to comment #5)
+> (In reply to comment #4)
+> > Agree--Visual Editor should not use <h1> HTML tags for headings at all
+> > because
+> > MediaWiki uses <h1> HTML for page name and headings are subordinate to page
+> > name. Heading-1 should create <h2> HTML tags, Heading-2 <h3> HTML tags,
+> > Heading-3 <h4> HTML tags, etc. Newcomers don't know this. Visual Editor
+> > should
+> > simply do this correctly without editors needing to know or think about it at
+> > all. Offering <h1> HTML in Visual Editor will cause confusion and misuse
+> > among
+> > the very people Visual Editor is designed to empower. They just want it to
+> > work
+> > right.
+> 
+> Except ""Heading 1"" is actually create-able on any wiki page (""= Foo =""), it's
+> just discouraged. This is a tension between what the software /lets/ users do
+> and what they /should/ do. I'm not convince that hard and fast global rules
+> are
+> always appropriate.
+
+This is not about convincing anyone ""that hard and fast global rules are
+always appropriate."" This is about getting it right for MediaWiki and MediaWiki users. Having ""Heading-1"" create wrong first level headings is wrong because orrect first level headings are <h2> in MediaWiki, subordinate to the page name <h1> that _is_ 'hard and fast' coded into the wiki page generator because that works well, always has, and is correct HTML. Users should not need to think about HTML at all. VisualEditor should just work right, not wrong. I know = Foo = gives <h1>Foo</h1>. That is an unfortunate wiki markup parser bug. If the VisualEditor team is too week to fix this bug by removing <h1> from the editor, they may implement ""Header-0 _deprecated_"" as <h1> (and link ""_deprecated_"" to a mediawiki.org page explaining why it is deprecated and why nevertheless included in VisualEditor). That is the obvious easy way out. However, VisualEditor has no need nor obligation to implement the deprecated and seldom used = Foo =. So remove it now and save everyone the mind drain of ""Header-0 _deprecated_"". VisualEditor is NOT an HTML editor. It is a MediaWiki page editor.",1366174196,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","(In reply to comment #4)
+> Agree--Visual Editor should not use <h1> HTML tags for headings at all
+> because
+> MediaWiki uses <h1> HTML for page name and headings are subordinate to page
+> name. Heading-1 should create <h2> HTML tags, Heading-2 <h3> HTML tags,
+> Heading-3 <h4> HTML tags, etc. Newcomers don't know this. Visual Editor
+> should
+> simply do this correctly without editors needing to know or think about it at
+> all. Offering <h1> HTML in Visual Editor will cause confusion and misuse
+> among
+> the very people Visual Editor is designed to empower. They just want it to
+> work
+> right.
+
+Except ""Heading 1"" is actually create-able on any wiki page (""= Foo =""), it's just discouraged. This is a tension between what the software /lets/ users do and what they /should/ do. I'm not convince that hard and fast global rules are always appropriate.",1366153968,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","**rogerchrisman** wrote:
+
+Agree--Visual Editor should not use <h1> HTML tags for headings at all because MediaWiki uses <h1> HTML for page name and headings are subordinate to page name. Heading-1 should create <h2> HTML tags, Heading-2 <h3> HTML tags, Heading-3 <h4> HTML tags, etc. Newcomers don't know this. Visual Editor should simply do this correctly without editors needing to know or think about it at all. Offering <h1> HTML in Visual Editor will cause confusion and misuse among the very people Visual Editor is designed to empower. They just want it to work right.",1366006598,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","**rogerchrisman** wrote:
+
+Agree--Visual Editor should not use <h1> HTML tags for headings at all because MediaWiki uses <h1> HTML for page name and headings are subordinate to page name. Heading-1 should create <h2> HTML tags, Heading-2 <h3> HTML tags, Heading-3 <h4> HTML tags, etc. Newcomers don't know this. Visual Editor should simply do this correctly without editors needing to know or think about it at all. Offering <h1> HTML in Visual Editor will cause confusion and misuse among the very people Visual Editor is designed to empower. They just wont it to work right.",1366006439,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",May want to cover content namespaces in general (but provide some way of getting them). Also to consider preventing H6s (and H5s?).,1360376924,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",*** Bug 44780 has been marked as a duplicate of this bug. ***,1360376842,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**Author:** `turb`
+
+**Description:**
+When cookies are disabled, VisualEditor loads indef. It would better to either 1) be able to use it without cookies (I suppose that's not possible) or 2) display an adequate error message.
+
+Tested on Firefox 17.0.1 with Cookie Monster 1.1.0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1355742780,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zborcq5aeddm5rc2upgl,task_description,resolved
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**turb** wrote:
+
+(In reply to comment #7)
+> Afaik the bad token handling has been solved for the save process. The load
+> process no longer requires a token.
+> 
+> Can you confirm this now works fine?
+
+Yes, it does work fine now, even with Cookie Monster preventing cookies to be set.",1380306403,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"Afaik the bad token handling has been solved for the save process. The load process no longer requires a token.
+
+Can you confirm this now works fine?",1380304934,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**turb** wrote:
+
+(In reply to comment #5)
+> Does normal editing (through the old, non-visual editor) work for you on
+> mediawiki.org when not whitelisted?
+
+Yes, it works.",1357831603,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"(In reply to comment #3)
+> (In reply to comment #2)
+> > (In reply to comment #1)
+> > > Can you confirm whether VE always fails to load with Cookie Monster and
+> > > always
+> > > loads successfully without Cookie Monster?
+> > And could you also confirm that you're able to edit *as a logged-in user*
+> > using
+> > the regular non-visual editor?
+> 
+> I forgot to mention I was testing on VisualEditor:Test in mediawiki.org, that
+> was not whitelisted in Cookie Monster. When I did whitelisted it, the page
+> reloaded and VE was now working.
+> 
+> I just removed again mediawiki.org from whitelist, and VE now loads without
+> end.
+> 
+Does normal editing (through the old, non-visual editor) work for you on mediawiki.org when not whitelisted?",1357671274,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**turb** wrote:
+
+Note: after some tests, VE does work with Chrome and IE9, with totally disabled cookies.",1355821721,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**turb** wrote:
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > Can you confirm whether VE always fails to load with Cookie Monster and
+> > always
+> > loads successfully without Cookie Monster?
+> And could you also confirm that you're able to edit *as a logged-in user*
+> using
+> the regular non-visual editor?
+
+I forgot to mention I was testing on VisualEditor:Test in mediawiki.org, that was not whitelisted in Cookie Monster. When I did whitelisted it, the page reloaded and VE was now working.
+
+I just removed again mediawiki.org from whitelist, and VE now loads without end.
+
+VE do work for me in en.wikipedia.org (that is of course whitelisted). I don't know if anonymous users can contribute with cookies disabled (for the day it will be activated for them).",1355821184,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"(In reply to comment #1)
+> Can you confirm whether VE always fails to load with Cookie Monster and
+> always
+> loads successfully without Cookie Monster?
+And could you also confirm that you're able to edit *as a logged-in user* using the regular non-visual editor?",1355819420,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"You can't have *all* cookies disabled, otherwise you wouldn't be able to log in and enable the VE preference. I'm guessing this might be a badtoken error (in which case I'm pretty sure we do actually show an error message, rather than load forever; and in which case you're probably also unable to edit through the regular UI), or it might be something entirely unrelated to cookies.
+
+Can you confirm whether VE always fails to load with Cookie Monster and always loads successfully without Cookie Monster?",1355819348,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+Undo/Redo doesn't work in Chrome/Chromium/Firefox for WikiEditor 0.3.1 in MW 1.19.2,"**Author:** `kartiksinghal`
+
+**Description:**
+I am using WikiEditor 0.3.1 in my mediawiki (1.19.2) installation and found that for some weird reason, undo/redo (Ctrl+Z and Ctrl+Shift+Z) doesn't work in the editor with Chrome, Chromium and Firefox browsers; while it works for Rekonq and default KDE webbrowser.
+
+I found T33780 - a slightly different but probably relevant bug report.
+
+Also, undo works just fine in default VisualEditor in Chrome.
+
+Interesting point to notice is that Undo/Redo work fine even on WikiEditor used on Wikipedia, but not in my mediawiki instance, looks like some good changes not pushed to upstream yet.
+
+I also tried test2.wikipedia.org, it works fine there as well.
+
+--------------------------
+**Version**: REL1_19-branch
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=31780",1355717820,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-5sshjiczpsr7gablgejn,task_description,invalid
+Undo/Redo doesn't work in Chrome/Chromium/Firefox for WikiEditor 0.3.1 in MW 1.19.2,This has probably already been fixed. I have no issues with undo/redo in Firefox on my local wiki running MW 1.23 and WikiEditor from master.,1417536426,PHID-USER-2uu3axihtun5w4v24nqz,PHID-TASK-5sshjiczpsr7gablgejn,task_subcomment,NA
+VisualEditor: Parsoid diff failure errors are not very descriptive,"Parsoid diff failure errors are not very descriptive - ""error loading data from server: unsuccessful request: diff failed."" but not why (in this case, it was because the target oldid had been deleted subsequent to the user pressing save, but a more graceful message would be good.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44354
+https://bugzilla.wikimedia.org/show_bug.cgi?id=39057
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63149",1355530860,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rmktbubqqol74vvmg4zn,task_description,resolved
+VisualEditor: Parsoid diff failure errors are not very descriptive,"With the above patch, the former message:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500. Would you like to retry?
+
+… turns into:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500: Page Fetch failure for ""BADURL"": Error: getaddrinfo
+    ENOTFOUND. Would you like to retry?
+
+Which is not ideal, but at least describes things a bit. Marking this as FIXED.",1409684401,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rmktbubqqol74vvmg4zn,task_subcomment,NA
+VisualEditor: Parsoid diff failure errors are not very descriptive,"Change 157775 merged by jenkins-bot:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409681803,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rmktbubqqol74vvmg4zn,task_subcomment,NA
+VisualEditor: Parsoid diff failure errors are not very descriptive,"Change 157775 had a related patch set uploaded by Jforrester:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409669834,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-rmktbubqqol74vvmg4zn,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","For content which is alienated, provide a way for users to get a wikitext editing window for just the wikitext for that item. This allows users to modify content that does not have an inspector yet, and for ""power users"", make tweaks in an environment that is familiar to them, without overwhelming other users. Ideally, this would be syntax-highlighted and pretty and helpful, but anything at all would be a start. :-)
+
+This will require some serious magic in Parsoid to identify the causal wikitext and allow partial document retrieval, and so this is very much in the ""enhancement"" pile for now; putting in UI as it's an inspector, but it will have impacts all the way down through DM.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355508900,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_description,resolved
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")",Fixed by Ed last year in https://gerrit.wikimedia.org/r/#/c/78035/,1414135494,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","**suitongbowgn** wrote:
+
+(In reply to comment #9)
+> (In reply to comment #8)
+> > There are quite a lot of extensions where the content should probably be
+> > treated as a simple block of text. <math>, <source>, <pre>, <poem> basically
+> > just have plain text ending with the appropriate closing tag.
+> 
+> Sort of. Ideally there will one day be a visual math editor, a visual music
+> editor, and we already have [[mw:Extension:CodeEditor]] (which is even
+> deployed
+> to certain wikis) for JavaScript and CSS, which will likely cover <pre> and
+> <source>/<syntaxhighlight> blocks.
+> 
+> I suppose <poem> and <nowiki> blocks can use a simple editor. :-)
+
+For <math> please see bug 43058. I believe it is already available via VisualEditor experimental code.
+For <syntaxhighlight> please see bug 47742. The code is currently under code review and will be available via VE experimental code in the future.",1375162399,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","(In reply to comment #8)
+> There are quite a lot of extensions where the content should probably be
+> treated as a simple block of text. <math>, <source>, <pre>, <poem> basically
+> just have plain text ending with the appropriate closing tag.
+
+Sort of. Ideally there will one day be a visual math editor, a visual music editor, and we already have [[mw:Extension:CodeEditor]] (which is even deployed to certain wikis) for JavaScript and CSS, which will likely cover <pre> and <source>/<syntaxhighlight> blocks.
+
+I suppose <poem> and <nowiki> blocks can use a simple editor. :-)",1375159143,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","There are quite a lot of extensions where the content should probably be treated as a simple block of text. <math>, <source>, <pre>, <poem> basically just have plain text ending with the appropriate closing tag.
+
+Some partial fix of this would be a great step in allowing VE to be used on some large classes of article.",1375133975,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")",*** Bug 51131 has been marked as a duplicate of this bug. ***,1373482421,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")",*** Bug 47742 has been marked as a duplicate of this bug. ***,1366998592,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")",Moved to Lowest as this has a huge dependency on Parsoid which they are unlikely to implement; depending on their reconsideration in a while.,1360206963,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","(In reply to comment #3)
+> +1, I imagine this feature as a toggle button, which switches the main view
+> between its current rendering containing uneditable blocks, to a hybrid
+> rendered + wikitext view in which the VE-opaque stuff is displayed as raw
+> source.
+
+Actually, we'll probably have inspector buttons on alienated nodes that trigger a float-over IFRAME quasi-window (in the same way that we do for the link inspector) for the individual item, rather than have a different editing mode (disrupting the entire editing flow feels wrong), but these decisions have yet to be taken.",1357696093,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","+1, I imagine this feature as a toggle button, which switches the main view between its current rendering containing uneditable blocks, to a hybrid rendered + wikitext view in which the VE-opaque stuff is displayed as raw source.
+
+The VE is great, but I have not found it to be usable for anything beyond the most trivial copy-editing, because of this issue.",1357694232,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","(In reply to comment #1)
+> It should be noted that a lot of this is already supported. I don't think
+> it's
+> perfect, and VE would have to perform some acrobatics to get it working, but
+> you could essentially make it work if you set the wikitext source on the
+> element, then serialized the DOM and re-parsed it to get the visual
+> representation back.
+> 
+The wikitext is currently exposed in the data-parsoid attribute, but the contents of that attribute are supposed to be private and VE isn't supposed to look at them, just preserve them. There were earlier hacks in VE that extracted information from data-parsoid to work around Parsoid issues (specifically, we had to look at sHref for links and stx==html for list items), but Gabriel has been glaring at me every time I did that.
+
+So to make the wikitext editable, it would have to be moved to a more public place, or data-parsoid would have to be declared semi-public. Either way, we need to spec how Parsoid is going to present the wikitext to VE and what VE is allowed to do with it.
+
+> James_F and I chatted about this for some time, and I'm pretty sure that's
+> one
+> of the saner ways to do it (unless you wanted to simply ignore the visual
+> portion of ""VisualEditor"" and submit the alien's changes only when the user
+> is
+> done editing.
+Yeah, you probably don't want to continuously rerender as the user types, that would get crazy. But as you say, you'd want to reparse the entered wikitext so you can rerender it and give the user visual feedback. That should be interesting to implement.",1355819784,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","It should be noted that a lot of this is already supported. I don't think it's perfect, and VE would have to perform some acrobatics to get it working, but you could essentially make it work if you set the wikitext source on the element, then serialized the DOM and re-parsed it to get the visual representation back.
+
+James_F and I chatted about this for some time, and I'm pretty sure that's one of the saner ways to do it (unless you wanted to simply ignore the visual portion of ""VisualEditor"" and submit the alien's changes only when the user is done editing.",1355522188,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Poem blocks,"<poem>....</poem> is unparsed but shown as plain wikitext:
+https://en.wikipedia.org/wiki/User:Raymond/poem
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/poem",1355479800,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-j5lt672qs5xqtdfzq6de,task_description,open
+Create a VisualEditor plugin tool to add/edit Poem blocks,"(In reply to comment #3)
+> (a) and (b), I guess. See bug 52061. I was going through a list of bugs in
+> the Poem component, since they will all need to be moved once the change
+> is merged (hoping it *is* merged, of course). Sorry if I'm getting too far
+> ahead of myself, but this bug did seem like an odd one out, so I moved it
+> out here.
+
+Moving back to Poem, then. The bug can be moved the MediaWiki/editing or whatever later, when bug 52061 is closed-fixed.
+
+> (In reply to comment #2)
+> > > so I'm punting back to VisualEditor.
+> > 
+> > Why? It's not VisualEditor's problem that an extension hasn't been updated
+> > yet…
+> 
+> Well, if Poem is to become a MediaWiki core feature, then it will turn into
+> something for the VE team to worry about.
+
+No, not really. It'll remain the responsibility of some code's maintainer, whoever that is (you?). In the absence of an obvious maintainer, that's the ""Platform team"", which sucks, but is rather outwith this bug report.
+
+The VE team build VE and some of the MW-specific VE tools. We're not going to make an editor for EasyTimeline, and we're not going to make one for Poem, for the same reason. :-)
+
+> Also, if I may point it out, the WikiHiero extension is seemingly supported
+> in VisualEditor core. The extension itself knows nothing about VE. is that
+> an anomaly?
+
+Yes; the code's yet to be moved into that repo. Give me a spare 10 minutes. :-)",1389573042,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j5lt672qs5xqtdfzq6de,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Poem blocks,"(a) and (b), I guess. See bug 52061. I was going through a list of bugs in the Poem component, since they will all need to be moved once the change is merged (hoping it *is* merged, of course). Sorry if I'm getting too far ahead of myself, but this bug did seem like an odd one out, so I moved it out here.
+
+(In reply to comment #2)
+> > so I'm punting back to VisualEditor.
+> 
+> Why? It's not VisualEditor's problem that an extension hasn't been updated
+> yet…
+
+Well, if Poem is to become a MediaWiki core feature, then it will turn into something for the VE team to worry about.
+
+Also, if I may point it out, the WikiHiero extension is seemingly supported in VisualEditor core. The extension itself knows nothing about VE. is that an anomaly?",1389572502,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-j5lt672qs5xqtdfzq6de,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Poem blocks,"(In reply to comment #1)
+> This is not a bug/enhancement in the Poem extension itself,
+
+False. The Poem extension fails to register a VisualEditor enhanced editor for itself. This is a problem with that extension. See also bug 43115, bug 43118, bug 43127, etc.
+
+> so I'm punting back to VisualEditor.
+
+Why? It's not VisualEditor's problem that an extension hasn't been updated yet…
+
+> If I've got this wrong, please don't move the bug back to Poem, as this
+> component is hopefully going to be removed soon.
+
+Please justify this.
+
+All MW extensions that are deployed on the WMF cluster (and many that aren't) have a Bugzilla component, by policy. Are you saying that:
+
+ (a) you want us to remove this extension from the cluster,
+ (b) you want us to merge this extension into MW core, or
+ (c) you want us to break our existing policy for this extension?",1389567907,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j5lt672qs5xqtdfzq6de,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Poem blocks,"This is not a bug/enhancement in the Poem extension itself, so I'm punting back to VisualEditor.
+
+If I've got this wrong, please don't move the bug back to Poem, as this component is hopefully going to be removed soon.",1389521779,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-j5lt672qs5xqtdfzq6de,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Timelines,"<timeline>....</timeline> is unparsed but shown as plain wikitext:
+https://en.wikipedia.org/wiki/User:Raymond/timeline
+
+**See Also**:
+{T29157}",1355477160,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-xk6tqgbthziuxrrlpn37,task_description,declined
+Create a VisualEditor plugin tool to add/edit Timelines,"Same as {T29157}, EasyTimeline is legacy and will eventually be replaced in favor of the Graph extension (T137291). As such it does not make sense to invest in a VisualEditor plugin that will eventually be made obsolete when timelines are migrated to Graph.",1479204677,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-xk6tqgbthziuxrrlpn37,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Timelines,I'd advise against work on this task; see {T137291} for the likely disposition of the extension.,1465386511,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xk6tqgbthziuxrrlpn37,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Timelines,"Not a duplicate; bug 27157 is about making a stand-alone interactive visual tool to create and edit EasyTimelines, whereas this is specifically about doing it inside VisualEditor (and so not for wikitext users).",1403569577,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xk6tqgbthziuxrrlpn37,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Timelines,"I think this is a duplicate of bug 27157. Please revert if I'm wrong.
+
+*** This bug has been marked as a duplicate of bug 27157 ***",1403559016,PHID-USER-omdcggvudfkuawipp23i,PHID-TASK-xk6tqgbthziuxrrlpn37,task_subcomment,NA
+VisualEditor: Switch over edit-success notice to use the deployed one,"On successful save, VE informs the user with a notification; however, this is not the same as the one deployed to the English Wikipedia (and elsewhere?). We should just inherit that, if possible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1355431920,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tnwafiqbhbl7tln47v6a,task_description,resolved
+VisualEditor: Switch over edit-success notice to use the deployed one,"
+
+*** This bug has been marked as a duplicate of bug 39632 ***",1368638967,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tnwafiqbhbl7tln47v6a,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"//This task is about PHP errors, for fatals, see T89169.//
+
+-------
+
+Although we get PHP warnings in the apache syslogs, we don't really get much information about it:
+
+Dec 13 18:30:43 10.0.11.48 apache2[9987]: PHP Warning:  preg_match() expects parameter 2 to be string, array given in /usr/local/apache/common-local/php-1.21wmf6/extensions/FundraiserLandingPage/FundraiserLandingPage.php on line 96
+Dec 13 18:30:43 10.0.2.198 apache2[24462]: PHP Warning:  preg_match() expects parameter 2 to be string, array given in /usr/local/apache/common-local/php-1.21wmf6/extensions/FundraiserLandingPage/FundraiserLandingPage.php on line 96
+
+We could do with recording more information (to a different log file on fluorine), like we do for both the fatal log and the exception logs
+
+-------
+
+Patches: <https://gerrit.wikimedia.org/r/#/q/message:T45086>
+
+Checklist:
+
+* [x] Improve de-duplication and message counting by ensuring `normalized_message` does not include the exception_id. – Pending review: https://gerrit.wikimedia.org/r/374895
+* [x] Introduce $wgPropagateErrors to avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [x] Enable $wgPropagateErrors in Beta Cluster. https://gerrit.wikimedia.org/r/c/409171/
+* [x] Enable $wgPropagateErrors in production Cluster.
+* [x] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+",1355424060,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_description,resolved
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Nice! That concludes a multiple years project :-],1551739179,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Thanks for pushing this through the finish line @Krinkle!,1551733519,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 494042 **merged** by Herron:
+[operations/puppet@production] logstash: Remove filter for unused 'exception-json' channel
+
+[[https://gerrit.wikimedia.org/r/494042]]",1551729558,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 494042 had a related patch set uploaded (by Krinkle; owner: Krinkle):
+[operations/puppet@production] logstash: Remove filter for unused 'exception-json' channel
+
+[[https://gerrit.wikimedia.org/r/494042]]",1551628735,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Pushing back. But would be nice to finish up at some point, but not now. To anyone else that happens to run into it: feel free to take it.",1539744093,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Last remaining check box:
+
+> [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`.",1539743995,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"I wasn't aware of `$wgPropagateErrors`, indeed we no more need errors to be spurts to HHVM stdout (which is `type:hhvm`).  That is a nice improvement to the logging and tracking errors :]",1539675476,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWZvyp40zCcrHSwq9kpb} [2018-10-13T23:37:21Z] <krinkle@deploy1001> Synchronized wmf-config/InitialiseSettings.php: T45086 - I4857e8ac (duration: 00m 51s)",1539473842,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 423338 **merged** by jenkins-bot:
+[operations/mediawiki-config@master] Set $wgPropagateErrors to false in production
+
+[[https://gerrit.wikimedia.org/r/423338]]",1539473248,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"@Tgr Yeah, take of small chunk of say 2 hours and then correlate as you describe. Keep in mind that T200960 was/is causing serious loss of data all over the place, including between these two channels. It's close to being fixed, so best to look at [Grafana](https://grafana.wikimedia.org/dashboard/db/logstash?orgId=1) and find a comfortable period of time range where there was 0 packet loss (which until last week, was never).",1533749486,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Hm, not sure why I didn't find it. Thanks Krinkle.
+
+What would be the next step here? Get a full list of all `type:hhvm` errors, filter out the ones which are also found in `type:mediawiki channel:error`, make sure that the rest are not propagated PHP errors, then enable `$wgPropagateError` in production?",1525164989,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#4166452, @Tgr wrote:
+> Seems like some PHP errors are only logged in the HHVM channel (T193339). Not sure whether they end up there with a mechanism that $wgPropagateError would affect.
+
+At T193339, the following sample is referenced from `type:hhvm`:
+
+```
+2018-04-29T09:25:59
+t  _type	hhvm
+t  host	mw1315
+t  level	NOTICE
+t  message	Notice: Undefined index: 0 in /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php on line 1498
+```
+
+Looking in `type:mediawiki` (dashboard ""mediawiki-errors"" with INFO and DEBUG un-disabled) I do find the same error trending
+
+```name=Trending
+Count: 16,672
+Message:
+[{exception_id}] {exception_url} ErrorException from line 1498 of /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php: PHP Notice: Undefined index: 0  	
+```
+
+And the exact duplicate (based on timestamp, host and message):
+<https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-2018.04.29/mediawiki?id=AWMQuSfhpesmgM3l0MzT&_g=h@b6494f7>
+
+```name=Sample,lines=10
+@timestamp	2018-04-29T09:25:59
+t  _type	mediawiki
+t  host		mw1315
+t  level	INFO
+t  server	ar.wikipedia.org
+t  url		/w/api.php
+[..]
+t  exception.message	PHP Notice: Undefined index: 0
+t  exception.trace	#0 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php(1498): MWExceptionHandler::handleError(integer, string, string, integer, array, array)
+#1 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php(955): AbuseFilter::takeConsequenceAction(string, array, Title, AbuseFilterVariableHolder, string, integer)
+#2 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php(1105): AbuseFilter::executeFilterActions(array, Title, AbuseFilterVariableHolder)
+#3 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilterHooks.php(119): AbuseFilter::filterAction(AbuseFilterVariableHolder, Title)
+#4 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilterHooks.php(52): AbuseFilterHooks::filterEdit(RequestContext, WikitextContent, string, Status, string, boolean)
+#5 /srv/mediawiki/php-1.32.0-wmf.1/includes/Hooks.php(177): AbuseFilterHooks::onEditFilterMergedContent(RequestContext, WikitextContent, Status, string, User, boolean)
+#6 /srv/mediawiki/php-1.32.0-wmf.1/includes/Hooks.php(205): Hooks::callHook(string, array, array, NULL)
+#7 /srv/mediawiki/php-1.32.0-wmf.1/includes/EditPage.php(1679): Hooks::run(string, array)
+#8 /srv/mediawiki/php-1.32.0-wmf.1/includes/EditPage.php(1998): EditPage->runPostMergeFilters(WikitextContent, Status, User)
+#9 /srv/mediawiki/php-1.32.0-wmf.1/includes/EditPage.php(1506): EditPage->internalAttemptSave(NULL, boolean)
+#10 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiEditPage.php(392): EditPage->attemptSave(NULL)
+#11 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(1579): ApiEditPage->execute()
+#12 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(504): ApiMain->executeAction()
+#13 /srv/mediawiki/php-1.32.0-wmf.1/extensions/VisualEditor/includes/ApiVisualEditorEdit.php(69): ApiMain->execute()
+#14 /srv/mediawiki/php-1.32.0-wmf.1/extensions/VisualEditor/includes/ApiVisualEditorEdit.php(382): ApiVisualEditorEdit->saveWikitext(Title, string, array)
+#15 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(1579): ApiVisualEditorEdit->execute()
+#16 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(535): ApiMain->executeAction()
+#17 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(506): ApiMain->executeActionWithErrorHandling()
+#18 /srv/mediawiki/php-1.32.0-wmf.1/api.php(83): ApiMain->execute()
+#19 /srv/mediawiki/w/api.php(3): include(string)
+#20 {main}
+```",1525143540,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Seems like some PHP errors are only logged in the HHVM channel (T193339). Not sure whether they end up there with a mechanism that $wgPropagateError would affect.,1524994832,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 423338 had a related patch set uploaded (by Gergő Tisza; owner: Gergő Tisza):
+[operations/mediawiki-config@master] Set $wgPropagateErrors to false in production
+
+[[https://gerrit.wikimedia.org/r/423338]]",1522576116,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWGLan1EL7tQ11ghvNrW} [2018-02-12T19:07:47Z] <niharika29@tin> Synchronized wmf-config/InitialiseSettings-labs.php: Stop PHP errors from going to the hhvm channel T45086 (duration: 00m 56s)",1518462467,PHID-USER-j4uyesgqhubl2dywl4xd,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 409171 **merged** by jenkins-bot:
+[operations/mediawiki-config@master] Stop PHP errors from going to the hhvm channel
+
+[[https://gerrit.wikimedia.org/r/409171]]",1518462280,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338911 **merged** by jenkins-bot:
+[mediawiki/core@master] Make it possible to not propagate errors to PHP
+
+[[https://gerrit.wikimedia.org/r/338911]]",1518130976,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 409171 had a related patch set uploaded (by Gergő Tisza; owner: Gergő Tisza):
+[operations/mediawiki-config@master] Stop PHP errors from going to the hhvm channel
+
+[[https://gerrit.wikimedia.org/r/409171]]",1518126418,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 374895 merged by jenkins-bot:
+[mediawiki/core@master] exception: Support message normalisation for structured logging
+
+[[https://gerrit.wikimedia.org/r/374895]]
+",1504804114,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 374895 had a related patch set uploaded (by Krinkle; owner: Krinkle):
+[mediawiki/core@master] exception: Support message normalisation for structured logging
+
+[[https://gerrit.wikimedia.org/r/374895]]
+",1504129234,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Checklist (//EDIT: Moved to task description.//)
+",1518121066,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+* [x] Fix de-duplication and message counting by ensuring `normalized_message` does not include the exception_id. – Pending review: https://gerrit.wikimedia.org/r/374895",1505203383,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+* [ ] Fix de-duplication and message counting by ensuring `normalized_message` does not include the exception_id. – Pending review: https://gerrit.wikimedia.org/r/374895",1504129256,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+* [ ] Fix de-duplication and message counting possible by ensuring `normalized_message` does not include the exception_id. – Pending review: https://gerrit.wikimedia.org/r/374895",1504129247,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+* [ ] Fix de-duplication and message counting possible by ensuring `normalized_message` does not include the exception_id.",1504128813,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`",1504128659,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Since 9eafbebdd882a562171fd0e46dcd5a9ec1e55cf8 has been deployed, some new error logs are surfacing \O/  An example is {T158770}  :-}
+",1487774255,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"The `error` channel (with severity=ERROR or maybe WARNING) should be added added to fatalmonitor on logstash, I suppose?",1487734726,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,[[https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-2017.02.22/mediawiki/?id=AVpjaHVDlL3ktRIGM6p7|Example error]]. See T136849#3045285 for comments on the format. (Except `exception.trace` seems different here. Or just has random errors in different ways than for other exceptions.),1487726805,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338820 merged by jenkins-bot:
+Route PHP warnings from the handler into udp2log
+
+[[https://gerrit.wikimedia.org/r/338820]]",1487639339,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338911 had a related patch set uploaded (by Gergő Tisza):
+Make it possible to not propagate errors to PHP
+
+[[https://gerrit.wikimedia.org/r/338911]]
+",1487638133,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338901 had a related patch set uploaded (by Gergő Tisza):
+Do not mix suppressed errors with non-suppressed ones
+
+[[https://gerrit.wikimedia.org/r/338901]]
+",1487633673,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338821 merged by jenkins-bot:
+MWExceptionHandler::handleError: Set log severity based on error level
+
+[[https://gerrit.wikimedia.org/r/338821]]",1487632148,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041561, @Tgr wrote:
+> The point is that the handler should not return false on errors which PHP would only log but not abort on, so that warnings don't get duplicated.
+
+Ok, I'm finally getting what you are working towards. Thanks for sticking with me. :) It would need some config flag as you mentioned in T45086#3041550 since the default behavior of the logging system is discard everything.",1487620029,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041550, @Tgr wrote:
+>>>! In T45086#3041541, @bd808 wrote:
+>> By not returning false and instead handling everything internally in the custom handler, the handler itself becomes responsible for deciding when to abort the request.
+> 
+> Yes, and it's a trivial decision (assuming we want to replicate the existing behavior): just abort on `*_ERROR`, unless PHP error reporting is turned off. So would there be any disadvantage to doing that? We could abort via exceptions which is more useful (HHVM can log the trace when the script aborts with an error but normal PHP can't), plus generally have better logging, at the cost of higher log volume / manual setup needed. It should probably be configurable and off by default but for WMF servers (and anyone else who cares enough about error logging to fine-tune it) it seems like a win.
+
+If the handler returns false then $php_errormsg is not set (based on code inspection). Grep shows it being used by PEAR Net/Socket, it calls @ini_set('track_errors', 1).",1487619640,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041557, @bd808 wrote:
+> How is raising an unhandled exception functionally different than passing control back to the default error handler? Is this an attempt to get more data into the PHP runtime's error log or less? I'm confused about the goal here.
+
+The point is that the handler should not return false on errors which PHP would only log but not abort on, so that warnings don't get duplicated. For errors which need the script to abort, IMO just push them to the exception channel (ie. don't log in the error handler but throw an exception) because that behaves nicer with non-log-based debugging (e.g. the developer would see a stack trace instead of just an error message, the user would see an exception hash that they can report). But logging and returning false, or just `die`ing, are also viable alternatives, the primary issue is log duplication for non-fatals.",1487619367,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041550, @Tgr wrote:
+>>>! In T45086#3041541, @bd808 wrote:
+>> By not returning false and instead handling everything internally in the custom handler, the handler itself becomes responsible for deciding when to abort the request.
+> 
+> Yes, and it's a trivial decision (assuming we want to replicate the existing behavior): just abort on `*_ERROR`, unless PHP error reporting is turned off. So would there be any disadvantage to doing that? We could abort via exceptions which is more useful (HHVM can log the trace when the script aborts with an error but normal PHP can't), plus generally have better logging, at the cost of higher log volume / manual setup needed. It should probably be configurable and off by default but for WMF servers (and anyone else who cares enough about error logging to fine-tune it) it seems like a win.
+
+How is raising an unhandled exception functionally different than passing control back to the default error handler? Is this an attempt to get more data into the PHP runtime's error log or less? I'm confused about the goal here.",1487618837,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041541, @bd808 wrote:
+> By not returning false and instead handling everything internally in the custom handler, the handler itself becomes responsible for deciding when to abort the request.
+
+Yes, and it's a trivial decision (assuming we want to replicate the existing behavior): just abort on `*_ERROR`, unless PHP error reporting is turned off. So would there be any disadvantage to doing that? We could abort via exceptions which is more useful (HHVM can log the trace when the script aborts with an error but normal PHP can't), plus generally have better logging, at the cost of higher log volume / manual setup needed. It should probably be configurable and off by default but for WMF servers (and anyone else who cares enough about error logging to fine-tune it) it seems like a win.",1487618437,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338821 had a related patch set uploaded (by BryanDavis):
+MWExceptionHandler::handleError: Set log severity based on error level
+
+[[https://gerrit.wikimedia.org/r/338821]]
+",1487618087,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041483, @bd808 wrote:
+> One way to provide granularity without creating N log channels would be to actually use the PSR3 log level in the generated log events:
+
+I would still put suppressed logs into their own channel because the way we seem to be using suppression is usually to prevent the program from being stopped and not so much to suppress logging, so having severity information for suppressed events seems useful. I agree about the rest (I actually wrote the patch yesterday but apparently forgot to submit it).",1487617990,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Is someone actually saying the log volume is too high? It looks to me like it's blocked on nobody giving a crap since 2015. Suppressed errors were removed from the stream in https://gerrit.wikimedia.org/r/#/c/177096/,1487617790,PHID-USER-k6tmz5ylx4rzfl3bitse,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041502, @Tgr wrote:
+>>>! In T158270#3041160, @bd808 wrote:
+>> We [return false from the error handler] that because it's the correct way for a default `set_error_handler()` to function. If we swallowed the errors there without returning false then `$php_errormsg` would not be populated and all errors would be handled as though the `@` suppression operator was applied to every line in the codebase.
+> 
+> We don't seem to use `$php_errormsg` anymore, so as far as I can see all that would do is to switch error logginrg to Monolog instead of the PHP/HHVM log files. (Assuming we die / throw an exception for errors which would interrupt program execution when unhandled.) Isn't that a good thing? It seems counterproductive to have the same error in logstash both as a Monolog event with traces etc. and a mostly useless HHVM record. Or are we worried about Monolog being more fragile / less reliable than logfiles/syslog?
+
+I think you are confusing the log data that we collect in WMF production and how PHP/HHVM work. The error handler must either abort the execution of the request or not. By not returning false and instead handling everything internally in the custom handler, the handler itself becomes responsible for deciding when to abort the request. If the handler returns (i.e. doesn't abort the request somehow) then it is functionally the same as applying `@` suppression to all lines in all scripts.",1487617740,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338820 had a related patch set uploaded (by Tim Starling):
+Route PHP warnings from the handler into logstash
+
+[[https://gerrit.wikimedia.org/r/338820]]
+",1487617563,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T158270#3041160, @bd808 wrote:
+> We [return false from the error handler] that because it's the correct way for a default `set_error_handler()` to function. If we swallowed the errors there without returning false then `$php_errormsg` would not be populated and all errors would be handled as though the `@` suppression operator was applied to every line in the codebase.
+
+We don't seem to use `$php_errormsg` anymore, so as far as I can see all that would do is to switch error logginrg to Monolog instead of the PHP/HHVM log files. (Assuming we die / throw an exception for errors which would interrupt program execution when unhandled.) Isn't that a good thing? It seems counterproductive to have the same error in logstash both as a Monolog event with traces etc. and a mostly useless HHVM record. Or are we worried about Monolog being more fragile / less reliable than logfiles/syslog?",1487617325,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041403, @Tgr wrote:
+> What's the current state of this task? Is it blocked in the log volume being too high? There are a few things we could do about that:
+> * only log warnings (at least initially), not notices
+> * sample
+> * send suppressed errors to a separate channel which can be blackholed
+> * cut down the number of warnings/notices in production (a lot of that has been happening recently, so maybe it's worth doing another experiment and reassess the situation?)
+
+One way to provide granularity without creating N log channels would be to actually use the PSR3 log level in the generated log events:
+* suppressed -> debug
+* E_STRICT -> debug
+* E_NOTICE, E_USERNOTICE, E_DEPRECATED, E_USER_DEPRECATED -> info
+* E_WARNING, E_CORE_WARNING, E_COMPILE_WARNING, E_USER_WARNING -> warning
+* E_RECOVERABLE_ERROR -> error
+
+It would be a pretty simple patch to MWExceptionHandler to allow the caller of `MWExceptionHandler::logError()` to specify a severity level and then to adjust `MWExceptionHandler::handleError()` to set an appropriate level. The current implementation in `MWExceptionHandler::logError()` emits all events as severity `error`.",1487616845,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"What's the current state of this task? Is it blocked in the log volume being too high? There are a few things we could do about that:
+* only log warnings (at least initially), not notices
+* sample
+* send suppressed errors to a separate channel which can be blackholed
+* cut down the number of warnings/notices in production (a lot of that has been happening recently, so maybe it's worth doing another experiment and reassess the situation?)",1487615460,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"@bd808 Thanks!
+
+Looks like we're not using `error-json` in Logstash yet. For PHP Notice and Warning events, Logstash uses the apache2/hvvm source still (which doesn't have stack traces). Currently blocked on T88732.",1429806541,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"@bd808 Thanks!
+
+Looks like we're not using `error-json` in Logstash yet. For PHP Notice and Warning events, Logstash uses the apache2/hvvm source still (which doesn't have stack traces).",1425357563,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"@bd808 Thanks!
+
+Looks like we're not using `error-json` in Logstash yet. For PHP Notice and Warning events, Logstash uses the apache2 error_log source still (which doesn't have stack traces).",1424825151,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 177096 merged by jenkins-bot:
+exception: Hide suppressed errors in 'error' log, flag in 'error-json'
+
+[[https://gerrit.wikimedia.org/r/177096]]",1421111660,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 177095 merged by jenkins-bot:
+exception: Implement error-json log
+
+[[https://gerrit.wikimedia.org/r/177095]]",1420489388,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 177096 had a related patch set uploaded (by Krinkle):
+exception: Hide suppressed errors in 'error' log, flag in 'error-json'
+
+[[https://gerrit.wikimedia.org/r/177096]]
+
+#patch-for-review",1418054876,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 177095 had a related patch set uploaded (by Krinkle):
+exception: Implement error-json log
+
+[[https://gerrit.wikimedia.org/r/177095]]
+
+#patch-for-review",1418054865,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"As of 399ba2fecf, MediaWiki has a new debug log group called ""error"" (similar to ""exception"" log we've had for years).
+
+Its entries are PHP Notices, PHP Warnings etc.. These always went (and still go) to PHP stderr (and apache's error log), but are historically lacking stack traces. 399ba2fecf hooks into PHP's error handler and produces a stack traces and forwards it to the new log.
+
+@Reedy and I enabled ([[ https://gerrit.wikimedia.org/r/#/c/173649/ | b4ace9661a ]]) this in production at Amsterdam Hackathon 2014 but it was disabled ([[ https://gerrit.wikimedia.org/r/#/c/173655/ | 82139373383c ]]) as it generated too much data on `fluorine` (1.5G in under 15 minutes).",1416970686,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"As of 399ba2fecf, MediaWiki has an new debug log group called ""error"" (similar to ""exception"" log we've had for years).
+
+Its entries are PHP Notices, PHP Warnings etc.. These always went (and still go) to PHP stderr (and apache's error log), but are historically lacking stack traces. 399ba2fecf hooks into PHP's error handler and produces a stack traces and forwards it to the new log.
+
+@Reedy and I enabled ([[ https://gerrit.wikimedia.org/r/#/c/173649/ | b4ace9661a ]]) this in production at Amsterdam Hackathon 2014 but it was disabled ([[ https://gerrit.wikimedia.org/r/#/c/173655/ | 82139373383c ]]) as it generated too much data on `fluorine` (1.5G in under 15 minutes).",1416970656,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"I wonder if we should close this. There's going to need to be some work to port this log into logstash, but that should be a different task. Also, knowing how much disk space it's going to use over a 24 hour period would be useful. The logs should certainly be very compressible...",1416933804,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"The ability to log backtraces in php errors was added in https://gerrit.wikimedia.org/r/#/c/173642/ .
+It was enabled in production in https://gerrit.wikimedia.org/r/#/c/173649/ and disabled again in https://gerrit.wikimedia.org/r/#/c/173655/ , because it was using ""up 680M in under a minute"".
+
+Having backtraces enabled is a huge help. So they should be enabled permanently and also sent into logstash.",1416852549,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Grabbing stack traces for warnings should be possible with a custom error handler and debug_backtrace() or ErrorException. It should probably be put behind a feature flag of some sort so that deployments that don't care about tracking warnings don't incur the performance penalty of generating the backtrace.,1404420413,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,The above might be from xdebug..,1384192111,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"PHPUnit dumps warnings to the console...
+
+Warning: Invalid argument supplied for foreach() in /var/www/wiki/mediawiki/core/includes/objectcache/SqlBagOStuff.php on line 232
+
+Call Stack:
+    0.0009     245936   1. {main}() /var/www/wiki/mediawiki/core/tests/phpunit/phpunit.php:0
+    2.0765   14629624   2. MediaWikiPHPUnitCommand::main() /var/www/wiki/mediawiki/core/tests/phpunit/phpunit.php:119
+    2.0767   14641960   3. MediaWikiPHPUnitCommand->run() /var/www/wiki/mediawiki/core/tests/phpunit/MediaWikiPHPUnitCommand.php:64
+    2.0767   14642440   4. PHPUnit_TextUI_Command->run() /var/www/wiki/mediawiki/core/tests/phpunit/MediaWikiPHPUnitCommand.php:80
+    7.3004   87363544   5. PHPUnit_TextUI_TestRunner->doRun() /usr/share/php/PHPUnit/TextUI/Command.php:176
+    7.3094   87684904   6. PHPUnit_Framework_TestSuite->run() /usr/share/php/PHPUnit/TextUI/TestRunner.php:349
+    7.4141   87686664   7. PHPUnit_Framework_TestSuite->run() /usr/share/php/PHPUnit/Framework/TestSuite.php:705
+   22.3535  178137936   8. PHPUnit_Framework_TestSuite->run() /usr/share/php/PHPUnit/Framework/TestSuite.php:705
+   22.3537  178139472   9. PHPUnit_Framework_TestSuite->runTest() /usr/share/php/PHPUnit/Framework/TestSuite.php:745
+   22.3537  178139952  10. MediaWikiTestCase->run() /usr/share/php/PHPUnit/Framework/TestSuite.php:775
+   22.3586  178141408  11. ApiQueryContinueTest->addDBData() /var/www/wiki/mediawiki/core/tests/phpunit/MediaWikiTestCase.php:109
+   23.4059  178284240  12. ApiTestCase->editPage() /var/www/wiki/mediawiki/core/tests/phpunit/includes/api/query/ApiQueryContinueTest.php:47
+   23.4063  178285904  13. WikiPage->doEditContent() /var/www/wiki/mediawiki/core/tests/phpunit/includes/api/ApiTestCase.php:56
+   23.5032  178306552  14. Title->getUserPermissionsErrors() /var/www/wiki/mediawiki/core/includes/WikiPage.php:1904
+   23.5032  178306736  15. Title->getUserPermissionsErrorsInternal() /var/www/wiki/mediawiki/core/includes/Title.php:1820
+   23.5140  178309936  16. Title->checkPermissionHooks() /var/www/wiki/mediawiki/core/includes/Title.php:2338
+   23.5142  178310696  17. wfRunHooks() /var/www/wiki/mediawiki/core/includes/Title.php:1946
+   23.5142  178310696  18. Hooks::run() /var/www/wiki/mediawiki/core/includes/GlobalFunctions.php:4032
+   23.5167  178312136  19. call_user_func_array() /var/www/wiki/mediawiki/core/includes/Hooks.php:199
+   23.5167  178312848  20. PageTranslationHooks::lockedPagesCheck() /var/www/wiki/mediawiki/core/includes/Hooks.php:199
+   23.5168  178312984  21. SqlBagOStuff->get() /var/www/wiki/mediawiki/extensions/Translate/tag/PageTranslationHooks.php:777
+   23.5168  178313336  22. SqlBagOStuff->getMulti() /var/www/wiki/mediawiki/core/includes/objectcache/SqlBagOStuff.php:200",1384189180,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"Visual Editor sometimes creates nowiki markup around simple square text brackets. Interestingly, it does that only in some cases, and not in others. For the same structure, it can also handle the text with nowiki, but does it in others. Text case:
+
+ The example below shows that in some cases this is done, in others not:
+
+# Remains unchanged: Test text for the VisualEditor: [[Link target|These are ['''just''' normal brackets]]].
+# Superflous nowiki-tags added on editing: Test text for the VisualEditor: [[Link target|These are '''just''' [normal brackets]]].
+
+
+Edit with Visual Editor to see the effect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T54268}",1355402040,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_description,resolved
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934108,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"Much of this is now resolved. [foo] is no longer nowiki-escaped, but [''foo''] is due to the apostrophes.
+
+There is still some room for (minor) improvement by moving the nowiki inside the brackets, although in some cases it is actually easier to read to wrap an entire line in nowiki instead of several nested nowikis.",1362174611,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"Note about the lost ""'''"" in the example above: that is a different bug unrelated to nowiki-escaping -- it should be fixed after the ongoing serializer refactor is complete.",1362171505,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"https://gerrit.wikimedia.org/r/49190 added URL validation in the tokenizer
+based on the wiki's configured URL protocols. This now makes the nowiki escaping more precise and fixes the snippet in this bug report.
+
+[subbu@earth lib] echo '[[Link target|These are '''just''' [normal brackets]]]' | node parse --wt2wt
+[[Link target|These are just [normal brackets]]]
+
+However, this wont be visible in the VE yet till a new deploy of Parsoid (another couple weeks, I expect).",1362171374,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"The problem is that till templates are expanded, it is hard to know whether the content of a ""[..]"" is going to a link or not.  That is the reason the tokenizer defers decisions for all [..] content till all templates are expanded so it can all be handled in a single place.
+
+But, there is another ticket for addressing this a bit more selectively which should address nowiki situations like this: https://bugzilla.wikimedia.org/show_bug.cgi?id=44449 --",1359472114,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"I believe adding illogical nowiki markup is somewhat irritating to existing editors.
+
+Perhaps a simple solution: Is there any justification for the tokenizer to consider an opening [ as a token? I believe only [http://, [https://, [irc://, [ircs://, [ftp://, [news://, [mailto: and [gopher:// should be external link tokens.",1359448382,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"One underlying issue is that our tokenizer is relatively liberal in what it accepts as an external link target, while a stricter validation is applied after templates etc are expanded. Our wikitext escaper also makes use of the tokenizer (plus some regexps), but does not (yet) consider external links that turn out to have invalid targets.
+
+Current output:
+
+echo ""[[Link target|These are '''just''' [normal brackets]]]"" | nodejs parse --wt2wt
+[[Link target|These are '''just'''<nowiki> [normal brackets]</nowiki>]]",1359415346,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"(In reply to comment #2)
+> and the fact that the last
+> ""]"" is outside the link.  
+
+The first ] is inside the link and the last 2 are the closing link.
+
+I agree that there may be more pressing matters, but compare that in one case:
+
+[[Link target|These are ['''just''' normal brackets]]
+
+the parser already works correct (does not add superfluous nowiki). Only if there is no formatting inside single square brackets it adds nowiki. I suspect this is not very logical.
+
+(... and annyoing on the live testing on en.wikipedia.)",1355510254,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"The nowiki-escaping is related to how Parsoid parses the text: [[Link target|These are ['''just''' normal brackets]]] and the fact that the last ""]"" is outside the link.  The nowiki escaping strategy is safe (but conservative) and tries not to accidentally create a wikilink when a ""]"" precedes a regular link bracket.  We (Parsoid team) should fix the parse first, add new tests, and then update the nowiki escaping.",1355508117,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"This appears to be a Parsoid bug; adjusting to reflect that.
+
+If you use the RT form - http://parsoid.wmflabs.org/_rtform/ - on the above string:
+
+[[Link target|These are '''just''' [normal brackets]]]
+->
+[[Link target|These are '''just'''<nowiki> [normal brackets]</nowiki>]]
+
+However, it generates correct HTML; for the other string:
+
+[[Link target|These are ['''just''' normal brackets]]]
+->
+<p data-parsoid=""{&quot;dsr&quot;:[0,54]}""><a rel=""mw:WikiLink"" href=""./Link_target"" data-parsoid=""{&quot;tsr&quot;:[0,53],&quot;a&quot;:{&quot;href&quot;:&quot;./Link_target&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;Link target&quot;},&quot;stx&quot;:&quot;piped&quot;,&quot;dsr&quot;:[0,53]}"">These are [<b data-parsoid=""{&quot;tsr&quot;:[25,28],&quot;dsr&quot;:[25,35]}"">just</b> normal brackets</a>]</p>
+
+Whereas canonical HTML from the PHP parser is:
+
+<p><a href=""/wiki/Link_target"" title=""Link target"">These are [<b>just</b> normal brackets]</a></p>
+
+[i.e., the closing not-used-for-a-link square bracket is inside the link, not outside it - however, this is probably a separate bug; happy to re-file.]",1355507224,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+"VisualEditor: Suppress ""Web link"" section in link inspector suggestion list if a wiki page link already exists","Present situation: the Visual Editor, when clicking on an existing Wiki-Link, provides the chain-link icon which in turn opens a dialogue which contains a pick list. In the pick list two sections exist: ""Existing page"" (value e.g. ""Pretoria"") and ""Web link"" (e.g. ""http://Pretoria""). 
+
+The present dialogue is good enough for creating new links. However, for existing links it is somewhat confusing to offer a nonsense http:// link as an equally valid alternative to an existing or previously confirmed wiki page.
+
+I suggest to keep the present behaviour for new links, but for existing wiki-page-links suppress the ""web link"" part of the pick list. It will still be possible to enter URLs directly in the dialogue box, the enhancement is only about suppressing it in the pick list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43841",1355397960,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-3cu7p6qfbrrfjek7shaw,task_description,invalid
+"VisualEditor: Suppress ""Web link"" section in link inspector suggestion list if a wiki page link already exists","This refers to behaviour that has now changed such that this is no longer actionable, so marking as INVALID.",1367544076,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3cu7p6qfbrrfjek7shaw,task_subcomment,NA
+"VisualEditor: Suppress ""Web link"" section in link inspector suggestion list if a wiki page link already exists","I am not proposing ANY changes to creating a new link. So when you mark the text wikipedia.org, yes you should be provided with page and the url in the picklist.
+
+My suggestion is about the confusion that occurs when the link already exists and already points to an internal page. I believe that then the chance that users want to validly change it to an external http URL are very small and not worth the confusion. The enhancement is about avoiding visual clutter and avoiding accidental mis-selections. And in those cases where you do want to change an external link to an internal one: you can still do it, only not with the pick list.
+
+I am not sure I understand the timing issues you mention, since the web page suggestions are always non-sense suggestions, just prefixing the text with http, so it seems easily suppressible. The ajax responsible for possible pages is a different story, but the visibility of that is not under discussion.",1355435857,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-3cu7p6qfbrrfjek7shaw,task_subcomment,NA
+"VisualEditor: Suppress ""Web link"" section in link inspector suggestion list if a wiki page link already exists","Not convinced that this is correct; yes, you /can/ have a valid page at a web site, but still want to link to the external one. For the most trivial example, ""amazon.com"" is both an article (on enwiki) and a valid external link. Therefore I'm minded to WONTFIX this.
+
+Also, I'd note that there are timing issues (as the list is created before the suggestions are returned), but those are minor.",1355434976,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3cu7p6qfbrrfjek7shaw,task_subcomment,NA
+mediawiki.action.view.dblClickEdit.dblClickEdit should trigger ca-edit click instead opening URL directly,"To account for editors that don't open a new page, simulate a click instead of using window.location directly.
+
+That way editors such as VisualEditor will get the edit event and initiate the editor.
+
+VisualEditor works without this as it updates the ca-edit url with ?veaction=edit, so it'll work. But still, going through a useless reload is... useless.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355360100,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5tc7u6hpj3ir3jtg2fhh,task_description,resolved
+mediawiki.action.view.dblClickEdit.dblClickEdit should trigger ca-edit click instead opening URL directly,Code has been merged.,1358469835,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5tc7u6hpj3ir3jtg2fhh,task_subcomment,NA
+mediawiki.action.view.dblClickEdit.dblClickEdit should trigger ca-edit click instead opening URL directly,"mediawiki.action.view.dblClickEdit and mediawiki.action.view.rightClickEdit modules respectively.
+
+Change-Id: Ie8a35700bc9e74b24f234ea682ad25375e18bda4",1355379612,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-5tc7u6hpj3ir3jtg2fhh,task_subcomment,NA
+VisualEditor: Strange duplication of content after multiple save attempts,"Reported at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Error_saving_data_to_server:_error: the parsoid appears to time out(?) and reports that there's an error, while actually saving the page. Meanwhile, a second attempt at saving has the same problem, /also/ saves...but adds random duplication of sentence fragments. See 
+https://en.wikipedia.org/w/index.php?title=Cologne&diff=next&oldid=527666838
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355347080,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-vus23yeu76aembddoyxe,task_description,resolved
+VisualEditor: Strange duplication of content after multiple save attempts,I believe that this is now fixed given the changes in Parsoid and in how VE talks to it; marking as such.,1366665489,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-vus23yeu76aembddoyxe,task_subcomment,NA
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active","When using the VisualEditor and having the Preference ""Edit pages on double click (requires JavaScript)"" on, the Editor is stopped as soon as one tries to select a word  (= double click)or paragraph (= triple click). The javascript for ""Edit pages on double click (requires JavaScript)"" needs to be modified to check whether in VisualEditor mode or not (all works ok when in normal editing mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1355333220,PHID-USER-grpjkpfolt5gz4ljlbfg,PHID-TASK-3hi7my5pvgnqne4eigdb,task_description,resolved
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active","This has been fixed by Ie8a35700bc9e in mediawiki core.
+
+In the current configuration however out tabLayout is in ""add"" more (when this bug was reported, we were still in ""replace"" mode).
+
+In ""add"" mode we add an extra tab for ""VisualEditor"", so the original ""Edit"" is still there, which is the default. And double-clicking in the content area will (as it should) trigger the original editor.
+
+If/when we enable the ""replace"" mode again, since this bug is fixed, double-clicking will trigger VisualEditor as expected.
+
+So, although it can't be seen right now, as the feature is not activated right now, this bug as been fixed.
+
+To verify, edit ve.init.mw.ViewPageTarget.js and set `this.tabLayout = ""replace"";`.",1361748640,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3hi7my5pvgnqne4eigdb,task_subcomment,NA
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active",Bumping; didn't make it to 2013-01-16.,1358461249,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3hi7my5pvgnqne4eigdb,task_subcomment,NA
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active",The surface should just bind a click handler and prevent the event from bubbling up to the handler that mediawiki.action.view.dblClickEdit attaches to $content.,1355375630,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-3hi7my5pvgnqne4eigdb,task_subcomment,NA
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active","Immediate solution is to suppress the JS when VE is active, but not when in read mode.
+
+Longer-term, this should be refactored so that users have a ""default"" editor, and this kind of thing triggers whichever one you've chosen.",1355344807,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3hi7my5pvgnqne4eigdb,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: this.registry[name].static is undefined""","When trying to use VisualEditor on the English Wikipedia at <https://en.wikipedia.org/wiki/James_Mackay,_Baron_Mackay_of_Clashfern>, I get the following error in my browser's console:
+
+---
+[11:35:31.120] TypeError: this.registry[name].static is undefined @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Cjquery.multiSuggest%7Crangy&skin=monobook&version=20121212T032708Z&*:207
+---
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355330220,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-zivm3qjikccdl4xebglv,task_description,declined
+"VisualEditor: Fix ""Uncaught TypeError: this.registry[name].static is undefined""","Cannot reproduce this without a deep stack trace; also, this is from three months ago, and we're unlikely to still have the same issue.",1364318088,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zivm3qjikccdl4xebglv,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: this.registry[name].static is undefined""",Max - any update on this? Can you reproduce when using debug=true (so we might have a hope of finding the underlying cause)?,1360206346,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zivm3qjikccdl4xebglv,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: this.registry[name].static is undefined""","I can't reproduce this, can you still? Did you do anything special to make this happen?",1355341942,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zivm3qjikccdl4xebglv,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'typePattern' of undefined""","When I try to use VisualEditor with <https://en.wikipedia.org/wiki/User:Trevor_Parscal>, I get the following error in my browser console: Uncaught TypeError: Cannot read property 'typePattern' of undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355327040,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-lin2kfpz66zdn3l3uhx2,task_description,declined
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'typePattern' of undefined""","Cannot reproduce this without a deep stack trace; also, this is from three months ago, and we're unlikely to still have the same issue.",1364318060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lin2kfpz66zdn3l3uhx2,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'typePattern' of undefined""","Also, which browser, etc.? :-)",1355343913,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lin2kfpz66zdn3l3uhx2,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'typePattern' of undefined""","Works for me; can you still reproduce this? Did you just load the editor, or did you do something to make this happen?",1355341841,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-lin2kfpz66zdn3l3uhx2,task_subcomment,NA
+Enable Visual editor on test client,"Enable VisualEditor on test client and check if the two extensions do not interfere with each other.
+
+They should not interfere with each other except for the additional parser function(s) introduced by Wikibase client.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355287440,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-ewbthsndzjv2jnkqp2ly,task_description,declined
+Enable Visual editor on test repo,"Enable VisualEditor on test repo and check if the two extensions do not interfere with each other.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355285580,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-dc5kyuqpkf3s6kddlzao,task_description,declined
+Enable Visual editor on test repo,"Note that VisualEditor will attempt to add edit links in the caction for pages in main namespace, but with Wikibase using main namespace for items this will be conflicting.
+
+It is possible to enable VisualEditor for specific namespaces so a work around should be pretty simple.",1355285813,PHID-USER-vlni4mhyozor7ghqnfkl,PHID-TASK-dc5kyuqpkf3s6kddlzao,task_subcomment,NA
+"VisualEditor: Avoid triggering ""XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.""","Feedback is one-way, we don't need to read the reponse (and we can't, due to origin policy). So we should convert this into a regular POST without XHR so that it doesn't error.
+
+Apparently though the current method does work for one-way (the request isn't blocked in Chrome).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355277780,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-tq6ygkwi32qnc2l6vv5h,task_description,invalid
+"VisualEditor: Avoid triggering ""XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.""","We're scrapping this feedback system, so marking as INVALID.",1370629685,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tq6ygkwi32qnc2l6vv5h,task_subcomment,NA
+"VisualEditor: Avoid triggering ""XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.""","I'm watching this bug.  Parsoid does support CORS headers via a configuration in localsettings.js (although maybe not yet on this particular response), so if you do decide to fix this on the parsoid end let me know.",1366316690,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-tq6ygkwi32qnc2l6vv5h,task_subcomment,NA
+"VisualEditor: Avoid triggering ""XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.""",De-prioritising and pulling from target milestone.,1361816423,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tq6ygkwi32qnc2l6vv5h,task_subcomment,NA
+VisualEditor: Integration in production should not ignoreHidden on user preference,"In VisualEditor.hooks.php the function to evaluate whether or not to show the VisualEditor has ignoreHidden set true on the user preference check; this should be false in production.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1355190000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ffowylul32ecwhb6soji,task_description,resolved
+VisualEditor: Integration in production should not ignoreHidden on user preference,Related URL: https://gerrit.wikimedia.org/r/61035 (Gerrit Change Idebb147ee03ad956cd0f3826c304db65eed1e34e),1366995915,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ffowylul32ecwhb6soji,task_subcomment,NA
+VisualEditor: Integration in production should not ignoreHidden on user preference,Fixed and being deployed today.,1366929861,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ffowylul32ecwhb6soji,task_subcomment,NA
+VisualEditor: Integration in production should not ignoreHidden on user preference,Related URL: https://gerrit.wikimedia.org/r/60911 (Gerrit Change Iec91b30422017ce9d71bc71b2cbeb71688e0d18f),1366920806,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ffowylul32ecwhb6soji,task_subcomment,NA
+VisualEditor: Integration in production should not ignoreHidden on user preference,Related URL: https://gerrit.wikimedia.org/r/60899 (Gerrit Change I0e55faca4eabe910d9b4d8ca8c6b4b0bd42e8539),1366916775,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ffowylul32ecwhb6soji,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"On a site such as the English Wikipedia, editors often create redirects for misspelled versions of page titles so that readers can have an easier time accessing the content they're after. For example, if a reader enters ""Barrack Obama"" or ""Dave Chapelle"" or ""Steve Carrell"" into the search bar, they'll be redirected automatically to ""Barack Obama"" or ""Dave Chappelle"" or ""Steve Carell"" (respectively) automatically. This is a good thing.
+
+However, these redirects can be problematic when editors insert this text into a page in the form of a link and don't get any feedback that the text they've entered is a misspelling (that it's likely wrong and not the text they intended to insert). In fact, the user gets the opposite feedback: they get feedback (a blue link) indicating that they've inserted an appropriate, working link.
+
+These misspelled redirects can be tagged with templates such as ""{{R from misspelling}}"" which generally automatically categorize them.
+
+I'm not sure what the appropriate behavior here is. I believe that continuing to allow users to insert links to misspelled words or phrases unknowingly is a bug and should be addressed somehow.
+
+There are a few options here, but I'm curious to read what others think about this. The goal here is to reduce the number of misspelled links that are added to a page by giving the user warning or notice that they've tried to insert a misspelled link (e.g., [[Hilary Clinton]] or [[Stephen Spielberg]]).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Linked_misspellings
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=13595",1355001180,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-nnoorqwvduraaxjx3s3c,task_description,open
+Redirects mask incorrect spellings (misspellings) in articles,"(In reply to John Broughton from comment #5)
+> (In reply to John Mark Vandenberg from comment #4)
+> 
+> I think we've wandered off topic, for which I'll take some responsibility.
+> The issue is NOT links to redirect pages, which (typically as hatnotes) can
+> be absolutely correct. Rather, the problem is wikilinks to redirect pages
+> **that are marked as being for misspellings**.
+
+Thanks for clarifying your solutions are for misspelling redirects only.
+
+What I was focusing on was the underlying problem that the software does not have a good way to determine which redirects are marked as misspellings?  And the concept of misspelling is IMO too complex to be built into the mediawiki layer.
+
+Surely not by looking for [[Template:R from misspelling]] or [[Category:Redirects from misspellings]] (as was done for disambiguation pages)
+
+__MISSPELLING__ ?  That would be equally odd.
+
+Bug 13595 is an interesting idea that records per-redirect custom messages to be used in one context (above target article), but the same approach may be used to provide custom messages to other contexts (such as in VE).
+
+Another approach may be to add misspellings to Wikidata, preferably as a misspellings attribute on the target Qs (similar to labels), rather than have redirects as distinct items in Wikidata (as was done for dab pages).",1399700412,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"(In reply to John Mark Vandenberg from comment #4)
+
+I think we've wandered off topic, for which I'll take some responsibility. The issue is NOT links to redirect pages, which (typically as hatnotes) can be absolutely correct. Rather, the problem is wikilinks to redirect pages **that are marked as being for misspellings**. So, let me reword the four alternatives I gave, above, to (hopefully) make this clearer.
+
+In articlespace (only):
+
+1. The software adds an administrative category, ""Articles with wikilinks to redirect pages for misspellings"", when an article is saved that has one or more of these problematical links.
+
+2. Links to redirect pages for misspellings are shown in yellow, both when previewing an edit and after saving the page. (With VisualEditor, the yellow coloring would appear immediately after typing the wikilink, which is ideal.) However, the editor can save the page with the (problematical) wikilink still on it.
+
+3. The software issues a warning when an editor tries to save a page with a link to a redirect page used to fix a misspelling, but allows the editor to override this. (Misspelled wikilinks need to be highlighted, of course; the software could also make it easy to accept a spelling change, since the redirect page points to the correct spelling of the article being linked to)
+
+4. The software issues a warning when an editor tries to save a page with a link to a redirect page for a misspelling, and prevents the editor from overriding this. (Misspelled wikilinks need to be highlighted, of course.)
+
+** Addendum:** 
+
+I'll also note that since we're concerned with *what the reader sees*, we should ignore wikilinks where a pipe is used, since the software can't (easily) determine if what the reader sees is correct:  [[wikilink to redirect|possibly correctly spelled text]].",1399698286,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"(In reply to John Broughton from comment #3)
+> Google translate didn't turn Comment 2 into anything meaningful for me, so
+> here are four alternative solutions, which could be implemented in the
+> software, one or more of which may already have been suggested above (in
+> Polish).
+> 
+> ...
+> 
+> Alternatives #1, #2, and #3 are compatible; all could be implemented
+> together. Alternative #4 is problematical in that an editor who is doing a
+> minor change might be blocked from saving that change even though he/she had
+> nothing to do with creating the wikilinks that go to redirects, and he/she
+> may not understand how to correct this. (Think of a relatively new editor,
+> or an IP editor.)
+> 
+> Implementing #1 would be invisible to the reader; #2 might cause a bit of
+> confusion.
+
+These solutions all presume that *every* link to a redirect is problematic.  If that is what the software presumes, it will cause more problems than it solves.  There are many instances where a link to a redirect page is appropriate.  If they are categorised into a maintenance category, some idiot will try to 'fix' them.  If it is more difficult to link to redirects using the VE UI, competent editors will complain bitterly.
+
+> *** Or someone could just create a bot that notifies editors that they've
+> made a mistake with their wikilink - as does DPL bot, for links to
+> disambiguation pages. ***
+
+This would be helpful, and the bot author could adapt the logic to understand when links to redirects are desirable.  For redirects categorised as spelling mistakes, a bot could also fix them automatically.",1399683919,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"Google translate didn't turn Comment 2 into anything meaningful for me, so here are four alternative solutions, which could be implemented in the software, one or more of which may already have been suggested above (in Polish).
+
+In articlespace (only):
+
+1. The software adds an administrative category, ""Articles with wikilinks to redirect pages"", when an article is saved that has one or more problematical links.
+
+2. Links to redirect pages are shown in yellow, both when previewing an edit and after saving the page. (With VisualEditor, the yellow coloring would appear immediately after typing the wikilink, which is ideal.) However, the editor can save the page with the (problematical) wikilink still on it.
+
+3. The software issues a warning when an editor tries to save a page with a link to a redirect page, but allows the editor to override this. (Problem wikilinks need to be highlighted, of course.)
+
+4. The software issues a warning when an editor tries to save a page with a link to a redirect page, and prevents the editor from overriding this. (Problem wikilinks need to be highlighted, of course.)
+
+Alternatives #1, #2, and #3 are compatible; all could be implemented together. Alternative #4 is problematical in that an editor who is doing a minor change might be blocked from saving that change even though he/she had nothing to do with creating the wikilinks that go to redirects, and he/she may not understand how to correct this. (Think of a relatively new editor, or an IP editor.)
+
+Implementing #1 would be invisible to the reader; #2 might cause a bit of confusion.
+
+*** Or someone could just create a bot that notifies editors that they've made a mistake with their wikilink - as does DPL bot, for links to disambiguation pages. ***",1371419572,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"The solution on pl.wiki is not to create redirects from misspelings. The ""Did you mean"" feature catches these well enough, and educates the reader on his mistake.
+
+(Policy: https://pl.wikipedia.org/wiki/Wikipedia:Przekierowanie#Stosowanie_przekierowa.C5.84 , last paragraph)",1355001897,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,This is a serious problem on some wikis (thousands of misspelled links): <https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Linked_misspellings>.,1355001544,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+VisualEditor: Links should not be allowed to be created spanning only whitespace,"Select some whitespace and open the link inspector and create the link.
+The SurfaceFragment.trimRange method is not trimming the space if the range only contains space.
+
+The correct behavior should be to trim the space then insert the location text into the document.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354917180,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-2mqmky2wjztbg6g74ags,task_description,resolved
+VisualEditor: Links should not be allowed to be created spanning only whitespace,"Patch in https://gerrit.wikimedia.org/r/37541
+This is DM stuff so Trevor or Roan will need to review.",1354917532,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-2mqmky2wjztbg6g74ags,task_subcomment,NA
+VisualEditor: Page creation should have a customized save button,"Similar to bug 41865
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354749120,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-mzqqlikp4a7wrk4foid4,task_description,resolved
+VisualEditor: Page creation should have a customized save button,Merged,1354758526,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-mzqqlikp4a7wrk4foid4,task_subcomment,NA
+VisualEditor: Page creation should have a customized save button,Fixed in gerrit 37144.,1354750343,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mzqqlikp4a7wrk4foid4,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**Author:** `bugzilla.wikimedia.org.76374`
+
+**Description:**
+curl -I 'http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.wikimediaShopLink.core%7Cjquery.client%2Ccookie%2CmwExtension%7Cmediawiki.cldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cutil%7Cmediawiki.language.data%2Cinit%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup&skin=vector&version=20121203T183954Z&*'
+curl: (52) Empty reply from server
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1354560840,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6ih3cdrbybmct3lwinv,task_description,resolved
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out",">>! In T44653#480329, @Nemo_bis wrote:
+> Every time I look (e.g. on webpagetest.org), I always find one or two ""failing"" load.php calls however I test it. Usually it's the CentralNotice taking too much
+
+From looking at the original description I tend to think it was a CentralNotice issue indeed. On the other hand, bannercontroller stuff was refactored in the meanwhile.",1490687031,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Closing for now as most likely the original cause can no longer cause a page to take 12 seconds to load given the following major changes that have happened since then.
+
+* Switch to HTTPS and HTTP/2 made bits re-use the same connection instead of establishing a new connection, thus speeding things up and reducing the changes that a connection gets cut off.
+ * {T96848}
+ * {T94896}
+ * {T95448}
+ * ..
+* Since then, bits itself has been folded into the main domains entirely, further optimising this re-use: 
+ * {T107430}
+* Since then, we've also reduced the number of requests that block rendering and page-ready
+ * {T107399}",1490658160,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","@Nemo_bis: I'm asking anybody in the CC list as someone might have faced the same problem in that IP range. 
+If I had asked anybody specifically, I would have prefixed a name. :)",1435685379,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","> Does this problem still happen nowadays?
+
+Who are you asking? The reporter is one of those made into ghosts by the bugzilla murder.",1435684764,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","
+Does this problem still happen nowadays?",1435675753,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","> We no longer use bits to serve this content. So this can probably be closed now ?
+
+What makes you think the issue was caused by the fact of being served from that domain?",1435039204,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out",We no longer use bits to serve this content. So this can probably be closed now ?,1435011660,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Here is a Chrome plugin that provides a workaround:
+
+https://chrome.google.com/webstore/detail/wikipedia-speedup/ppmagkdpdaaabpmdppckemgkngkpchdl?hl=en",1415214025,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","(In reply to Macavity from comment #19)
+> This happens reliably on the IP range my ISP uses (looks like
+> 86.141.0.0/16), when jqueryMsg is in the query string:
+> 
+> This times out:
+
+Works for me as I get a cached response /* cache key: enwiki:resourceloader:filter:minify-js:7:519abda9a1640250a7c561ccfd0f22f8 */
+I don't see ongoing CentralNotice campaigns for UK.",1414919322,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","This happens reliably on the IP range my ISP uses (looks like 86.141.0.0/16), when jqueryMsg is in the query string:
+
+This times out:
+
+http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin%7Cext.uls.init%2Cinterface%2Cpreferences%2Cwebfonts%7Cext.visualEditor.viewPageTarget.init%7Cjquery.accessKeyLabel%2CbyteLength%2Cclient%2Ccookie%2CmwExtension%2CtabIndex%2Cthrottle-debounce%2Ctipsy%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.language.init%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cmmv.base%2Chead%7Cskins.vector.js&skin=vector&version=20141031T180422Z&*
+
+This returns:
+
+http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin%7Cext.uls.init%2Cinterface%2Cpreferences%2Cwebfonts%7Cext.visualEditor.viewPageTarget.init%7Cjquery.accessKeyLabel%2CbyteLength%2Cclient%2Ccookie%2CmwExtension%2CtabIndex%2Cthrottle-debounce%2Ctipsy%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.language.init%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cmmv.base%2Chead%7Cskins.vector.js&skin=vector&version=20141031T180422Z&*",1414918068,PHID-USER-klksrqr4iars7szz53kl,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Every time I look (e.g. on webpagetest.org), I always find one or two ""failing"" load.php calls however I test it. Usually it's the CentralNotice taking too much, I don't see what can be done in this component.",1404555792,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Correct, comment 14 - comment 17 are a different issue.",1368105953,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Yeah, bits was having issues earlier today. https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&oldid=69483 and http://status.wikimedia.org/8777/156486/Static-assets-(CSS/JS) seem to confirm this. I think separate issues are getting mixed in to a single bug, though.",1368059296,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","And little bit more. In my case it is maybe just only DNS updating problem. In my home ip bits.wikimedia.org resolves to  91.198.174.233, 2620:0:862:ed1a::a,  bits.esams.wikimedia.org.
+
+In .kapsi.fi where everything is working fine bits.wikimedia.org resolves to  2620:0:861:ed1a::a, 208.80.154.234, bits-lb.eqiad.wikimedia.org",1367994507,PHID-USER-pmmyhpxkzmo6lbo5bcqo,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","This seems to something like my ongoing Wikipedia/Wikimedia problem. In last 12 hours most of queries to http://bits.wikimedia.org from my home IP are failed, but not all. However https://bits.wikimedia.org seems to work normally. I also asked in community portal of fiwiki if wikipedia has been slow and answer was  it has been worked normally.
+
+Commands asked:
+
+--- CLIP ----
+curl -i http://bits.wikimedia.org/
+curl: (7) Failed to connect to 2620:0:862:ed1a::a: Network is unreachable
+
+--- CLIP ----
+curl -i https://bits.wikimedia.org/
+HTTP/1.1 200 OK
+Server: nginx/1.1.19
+Date: Wed, 08 May 2013 05:45:54 GMT
+Content-Type: text/html
+Content-Length: 178
+Connection: keep-alive
+Last-Modified: Thu, 12 Aug 2010 16:12:20 GMT
+ETag: ""b2-48da2a1772100""
+X-Varnish: 693529009
+Via: 1.1 varnish
+Accept-Ranges: bytes
+X-Varnish: 1488468153
+Age: 0
+Via: 1.1 varnish
+X-Cache: strontium miss (0), cp3021 miss (0)
+
+<html>
+	<head><title>bits and pieces</title>
+		<meta http-equiv=""refresh"" content=""1;url=http://www.wikimedia.org/"" />
+	</head>
+<body>
+bits and pieces live here!
+</body>
+</html>
+
+--- CLIP ----
+curl -i http://bits.wikimedia.org/geoiplookup
+HTTP/1.1 200 geoiplookup
+Server: Varnish
+Content-Type: text/javascript
+Content-Length: 111
+Last-Modified: Wed, 08 May 2013 05:58:57 GMT
+Cache-Control: private, max-age=86400, s-maxage=0
+Accept-Ranges: bytes
+Date: Wed, 08 May 2013 05:58:57 GMT
+X-Varnish: 2987799549
+Age: 0
+Via: 1.1 varnish
+Connection: close
+X-Cache: cp3022 miss (0)
+
+Geo = {""city"":""REMOVED"",""country"":""FI"",""lat"":""REMOVED"",""lon"":""REMOVED"",""IP"":""91.153.84.229"",""netmask"":""24""}
+
+--- CLIP ----
+traceroute bits.wikimedia.org
+traceroute to bits.wikimedia.org (91.198.174.233), 30 hops max, 60 byte packets
+ 1  kotiboksi.Elisa (192.168.100.1)  0.662 ms  0.861 ms  1.079 ms
+ 2  tkueur1.fi.elisa.net (91.153.48.1)  14.876 ms  15.553 ms  15.781 ms
+ 3  ge1-0-0.tkubra-p1.fi.elisa.net (139.97.9.13)  13.879 ms  15.328 ms  16.106 ms
+ 4  so7-2-0.esptnl-p1.fi.elisa.net (139.97.6.1)  19.842 ms  21.924 ms  22.199 ms
+ 5  ip-rr.hkika234.fi.elisa.net (139.97.0.162)  22.454 ms  23.130 ms  23.885 ms
+ 6  213.192.184.109 (213.192.184.109)  25.150 ms  17.379 ms  18.065 ms
+ 7  as0-0.bbr1.ams1.nl.eunetip.net (213.192.191.226)  54.601 ms  50.913 ms  47.484 ms
+ 8  * * *
+ 9  * * *
+10  * * *
+....
+
+Discussion in community portal:
+http://fi.wikipedia.org/wiki/Wikipedia:Kahvihuone_%28tekniikka%29#Wikipedian_hidastelu",1367992987,PHID-USER-pmmyhpxkzmo6lbo5bcqo,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Bug 39322 came to my mind, so I'd still appreciate the output of the following commands
+
+traceroute bits.wikimedia.org
+
+curl -i http://bits.wikimedia.org/",1366803080,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Andre: we have already determined that it is a problem related to the source ip range.",1363057173,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Look at the screenshot. Just one out of multiple calls to the same script fails. So the routing is definitely ok.",1363057106,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Just realizing that this question still stands:
+
+> Is the routing to the bits servers ok from both ip address ranges?",1363000685,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","For me in Firebug that specific call is 51ms and 14.9kb (being logged in), for you 11440ms and 0.0kb.
+
+And in my case the URL is
+http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.wikimediaShopLink.core%7Cjquery.client%2Ccookie%2CmwExtension%7Cmediawiki.cldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cutil%7Cmediawiki.language.data%2Cinit%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cwikibase.client.init&skin=vector&version=20130311T110922Z&*",1363000652,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+screenshot of timeout in firebug
+
+**Attached**: {F10260}",1362773214,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Yes, it is still a problem. See the screenshot.",1362773152,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","As we've changed data centers in late January and the related setup, could you please test if this is still a problem?",1362732889,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+This appears to be a *script bug* in http://bits.wikimedia.org/en.wikipedia.org/load.php because the server itself shows no problems at all.",1356131835,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out",I'm wondering if this is a dup of bug 41130?,1356116359,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","(In reply to comment #2)
+> Works from 81.169.0.0/16, but *NOT* from 78.52.0.0/16 (Europe/Berlin/dynamic
+> IP
+> for DSL endpoint)
+
+Is the routing to the bits servers ok from both ip address ranges?",1355671621,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Works from 81.169.0.0/16, but *NOT* from 78.52.0.0/16 (Europe/Berlin/dynamic IP for DSL endpoint)",1355671137,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Works for me - is this still an issue, and on which continent are you based? There were some load issues but they are mostly fixed now.",1355665523,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+VisualEditor: Only replace url on veaction=edit if there is no other query,"Go to a VE wiki page directly in edit mode:
+
+http://mediawiki.org/wiki/VisualEditor:Test?uselang=he&veaction=edit
+
+The integration changes the URL to:
+
+https://www.mediawiki.org/wiki/VisualEditor:Test
+
+... instead of:
+
+https://www.mediawiki.org/wiki/VisualEditor:Test?uselang=he
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1354218360,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-er2j2jzi7wxs7w6xckns,task_description,resolved
+VisualEditor: Only replace url on veaction=edit if there is no other query,Code now live in master; will get deployed in the next cycle.,1354565570,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-er2j2jzi7wxs7w6xckns,task_subcomment,NA
+VisualEditor: Only replace url on veaction=edit if there is no other query,Change-Id: Ia63c937d3a0a68acaa178486ab439bc1ea9db8af,1354423024,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-er2j2jzi7wxs7w6xckns,task_subcomment,NA
+VisualEditor: Integration fails if an article has an '@' character in its title,"VE/MW integration fails (does not trigger but instead throws two errors, below) if an article has an '@' character in its title, though these are valid
+
+Uncaught Error: Bad constructor arguments    mediawiki.Uri.js:165
+Uri                     mediawiki.Uri.js:165
+mw.UriRelative          mediawiki.Uri.js:318
+(anonymous function)    mediawiki.Uri.js:325
+(anonymous function)    mediawiki.Uri.js:328
+
+Uncaught TypeError: undefined is not a function    ve.init.mw.ViewPageTarget.js:18
+VeInitMwViewPageTarget    ve.init.mw.ViewPageTarget.js:18
+(anonymous function)      ve.init.mw.ViewPageTarget.js:1121
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://www.mediawiki.org/wiki/VisualEditor:Test@4",1353449520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pjkjsbfhouqskvpvg6ev,task_description,resolved
+VisualEditor: Integration fails if an article has an '@' character in its title,"Fixed upstream, will be in 1.21wmf9.",1358878792,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pjkjsbfhouqskvpvg6ev,task_subcomment,NA
+VisualEditor: Integration fails if an article has an '@' character in its title,Upstream issue in the mediawiki.Uri module of mediawiki/core.,1354127118,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-pjkjsbfhouqskvpvg6ev,task_subcomment,NA
+VisualEditor: Putting cursor immediately before link should display inspector icon,"Currently, putting the cursor inside a link displays the inspector icon (except for bug 42276). Putting the cursor immediately after a link (i.e. between the last linked character and the first non-linked character) also displays the icon, but putting it immediately before the icon (between the last non-linked character and the first linked character) does not. I think it should.
+
+Of course, the interesting question here is what should happen when you have two directly adjacent links and you put the cursor between them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353379740,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nm5db6sizlej6gdhkkqp,task_description,declined
+VisualEditor: Putting cursor immediately before link should display inspector icon,"Per IRL discussion, this is wontfix.",1353539731,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-nm5db6sizlej6gdhkkqp,task_subcomment,NA
+VisualEditor: Pre-annotations code annotates characters with the empty set,"1. Open any document
+2. Blank it
+3. Type some text
+4. Dump the model into the console (ve.instances[0].documentModel.data)
+
+Expected output: [ 'F', 'o', 'o', 'b', 'a', 'r' ]
+Actual output: [ 'F', ['o', ve.AnnotationSet([])], ['b', ve.AnnotationSet([])] ...
+
+The pre-annotations code is applying the empty set as a pre-annotation to every character except the first. This shouldn't happen, it should just not annotate if it's got nothing to annotate with.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353378840,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vedbqhk6swjrkcfcznus,task_description,resolved
+VisualEditor: Pre-annotations code annotates characters with the empty set,Actually fixed in gerrit 34684,1353546438,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vedbqhk6swjrkcfcznus,task_subcomment,NA
+VisualEditor: Pre-annotations code annotates characters with the empty set,"...doesn't actually fix it, will investigate.",1353543663,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vedbqhk6swjrkcfcznus,task_subcomment,NA
+VisualEditor: Pre-annotations code annotates characters with the empty set,https://gerrit.wikimedia.org/r/#/c/34598/,1353541416,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vedbqhk6swjrkcfcznus,task_subcomment,NA
+VisualEditor: Pre-annotations code annotates characters with the empty set,Trevor has a commit queued up that fixes this.,1353530421,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-vedbqhk6swjrkcfcznus,task_subcomment,NA
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page","Currently to view the underlying wikitext of a page that's in a namespace where VisualEditor is active, one clicks an ""edit source"" tab. However, when editing, if you want to see the underlying wikitext but not lose your changes or really just not have to reload the page, that isn't possible. It'd be awfully nice if you could toggle between wikitext and the VisualEditor interface without needing to reload the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57462",1352958180,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-o2rqx7ng2feqhiottjsd,task_description,open
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page",It seems like this task is sort of obsoleted by {T102398} and its blockers+dependencies.,1437012494,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-o2rqx7ng2feqhiottjsd,task_subcomment,NA
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page","When a user presses ""Save page"" (for the second time, as you point out):
+* the HTML DOM gets converted to Parsoid-format HTML+RDFa,
+* this HTML+RDFa is squirted at Parsoid, 
+* Parsoid converts it to wikitext, and
+* Parsoid saves it to the DB (using the user permissions/etc. as provided by VE from the user session).",1353022256,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o2rqx7ng2feqhiottjsd,task_subcomment,NA
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page","(In reply to comment #1)
+> This would be nice, but goes far beyond current functionality of MW core, so
+> marking as low priority.
+
+It's unclear to me at which stage the visual document that a user is editing is converted to wikitext.",1353019498,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-o2rqx7ng2feqhiottjsd,task_subcomment,NA
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page","This would be nice, but goes far beyond current functionality of MW core, so marking as low priority.",1353018184,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-o2rqx7ng2feqhiottjsd,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Currently when using the VisualEditor extension, there's a big green button that reads ""Save page"" in the top-right corner of the browsing window.
+
+When a user clicks this button labeled ""Save page"", the page is not saved. Instead, a dialog box appears in which the user is prompted to enter an edit summary. If the user then clicks the ""Save page"" button again (a second time), the page will be saved (maybe).
+
+I believe this is behavior is a little wrong. Historically the behavior of the ""Save page"" button has been to actually attempt to save the page to the database. This new workflow changes that behavior.
+
+Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+
+There's also no warning within the ""Save page"" dialog box that says that the page has not yet been saved to the database. There's no ""this is only a preview!"" text. Perhaps that's a separate bug, though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1352957520,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-abb2jsunmv7mixlbbgye,task_description,resolved
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3957958, @Pinnerup wrote:
+> This issue has been open for 5+ years now. Please take action to differentiate the text on the two buttons so it's possible to distinguish whether pressing them will publish something immediately or not.
+
+If had a pound for every time someone said that, I'd be a rich man.
+
+Tasks come in faster than they can be worked on. The Editing team has only three full time engineers, and we have the responsibility of an entire ecosystem of editing tools across over 800 Wikimedia wikis, and thousands more third-party websites. The consequence is that many, many tasks sit around for years with no action, even though every task is very important to the person that filed it; this is an unfortunate reality of software development.",1524050312,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3957958, @Pinnerup wrote:
+> This issue has been open for 5+ years now. Please take action to differentiate the text on the two buttons so it's possible to distinguish whether pressing them will publish something immediately or not.
+
+I had a pound for every time someone said that, I'd be a rich man.
+
+Tasks come in faster than they can be worked on. The Editing team has only three full time engineers, and we have the responsibility of an entire ecosystem of editing tools across over 800 Wikimedia wikis, and thousands more third-party websites. The consequence is that many, many tasks sit around for years with no action, even though every task is very important to the person that filed it; this is an unfortunate reality of software development.",1524050081,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","With the completion of T189803, there is now more clarity about what clicking the first ""Publish changes"" button does, so this task is now resolved.",1524049612,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","I came here just for this after too often accidentally publishing an incomplete or undescribed edit. It's really frustrating to me as a user that it's not easily possible to see if pressing the ""Publish changes"" button will take me to an intermediate step allowing review and description or if it will publish the changes immediately. 
+
+This issue has been open for 5+ years now. Please take action to differentiate the text on the two buttons so it's possible to distinguish whether pressing them will publish something immediately or not.",1518175350,PHID-USER-vvb5cpvcki2rgdles7sq,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","> for example, we can provide an access to preview as an additional mode in the menu we provide access to ""Visual editing"" and ""Source editing"".
+
+I provided mockups demonstrating something like this in [[#3274084|a previous message]].",1504785682,PHID-USER-2fha2mym5lty6djs2qfl,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3579770, @Jan_Dittrich wrote:
+> From observing the users and further corroborated by the comments on Kurier 
+
+Some notes on the different observations:
+
+> 1. Users, particular experienced ones, seem to rely a lot on previewing before they save, so they want to preview //before// they save and create an entry in the history.
+
+This probably means that some users don't see preview as part of the publishing process, but as part of their edit process: edit-> preview -> continue editing...
+
+> 2. In the current UI, the only way to preview is clicking a button that indicates it does something they want to avoid: Saving directly.
+
+Having the option to preview as you publish is fine, but it does not have to be the only entry point we provide for it. Especially if we want to support users that don't see ""preview"" as part of the publishing process. for example, we can provide an access to preview as an additional mode in the menu we provide access to ""Visual editing"" and ""Source editing"". That seems to align better with the idea of supporting preview as another perspective to switch while editing. 
+
+> Thus there is a problem. Adding … does not solve all the problems. But it alleviates point 2: It indicates that clicking ""publish changes"" does //not// do immediately what they want to avoid. 
+
+I don't think that adding ellipsis is going to alleviate the issue of point 2 since the publishing button (with ellipses or other indications) has the main job of announcing the path to publishing, and being it in one or two steps, these users are not interested to go into it yet. Making the ""publish"" action (even slightly) to be less about publishing does not seem the most promising option.
+
+Let's assume that ellipses make more users access the summary panel. Is that solving the issue? I don't think the problem is that those users are not reaching the summary panel, these users probably have already done so (since they are experienced editors), the problem is they don't seem to find it natural to go through the publishing path while their editing process is not over.
+
+I'm ok with experimenting with this if people think it may have potential, but let's make sure it does not impact the regular use of publishing when people actually want to publish.
+",1504699168,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","I feel like unfortunately we already have enough tasks open about how long translations look ugly and make the interface potentially difficult to use. ""..."" is a good compromise that I really endorse.",1504695764,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","@dialmove's suggestion above to rename the button to ""Review and publish"" would also be a simple way to improve things.
+
+The downside is that the space for the button is limited, and the text can already be fairly long in some languages. E.g. in Hungarian ""Publish changes"" is ""Változtatások közzététele""; ""Review and publish"" would be something like ""Változtatások áttekintése és közzététele"".
+
+Maybe just change to ""Review"" and rely on the constructive colors to tell the user that's the next step?",1504627839,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","> I'd like to understand better the specific issues that the uncertainty about ""whether 
+> the save button saves immediately"" generates. 
+
+From observing the users and further corroborated by the comments on Kurier 
+
+1. Users, particular experienced ones, seem to rely a lot on previewing before they save, so they want to preview //before// they save and create an entry in the history.
+2. In the current UI, the only way to preview is clicking a button that indicates it does something they want to avoid: Saving directly.
+
+Thus there is a problem. Adding … does not solve all the problems. But it alleviates point 2: It indicates that clicking ""publish changes"" does //not// do immediately what they want to avoid. ",1504615255,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3578131, @Jan_Dittrich wrote:
+> Who is the one to decide about this?
+
+Me. I'm watching this task. :-)
+
+This is far from the most pressing item on the agenda, but I do agree with the statement of the problem. I like the ellipsis idea; it's not perfect, but it's easy to implement, is at least step in the right direction, and can easily be iterated on. I think more discussion about other solutions would be good.",1504606283,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3578131, @Jan_Dittrich wrote: 
+> @Pginer-WMF – what do you think? And: Who is the one to decide about this?
+
+I'm not convinced this would improve much. I'm ok with experimenting, but given the importance of the publishing workflow I'd like to have a clear hypothesis of what we expect and how to observe the impact of the change. More details below:
+
+**On the need to communicate additional steps**
+
+Ellipses may help to emphasise that the publishing process have multiple steps. The key question is whether we need to anticipate such information. There are many processes that require some kind of confirmation/follow-up step that users see as a logical progress to completion, and do not cause any kind of confusion or surprise despite those extra steps not being anticipated. For example, I don't think that adding ellipses to all actions that open any kind of panel such as ""add link"" or ""insert image"" would improve things much.
+
+I'd like to understand better the specific issues that the uncertainty about ""whether the save button saves immediately"" generates. What do we expect users to do differently if they know there are more step behind the button?
+
+The ellipses make also the call to action less strong. In addition, ellipses in buttons have been also used to communicate an action being performed (e.g., a ""Save"" button turning into ""Saving..."" after being pressed), so there is a risk of confusion for users thinking some publishing action may be going on that we may want to check.
+
+**Connection with ""preview"" issue**
+If the proposal is intended to improve the issue with preview (T155732), which some comments in this ticket still refer to, I don't think it will help much.
+
+My understanding of the preview issue is that some users don't see ""preview"" necessarily as an intermediary step in their way to publishing. That is, some users understand preview as away to check that their recent editing actions produce the expected result before continue their editing session. Since they are not completing their editing session, it is not obvious that preview will be behind the ""publish"" path. We are supporting well the scenario of ""preview in your way to publish"" but we may not be doing so well with the ""preview as you edit"". 
+
+Ellipsis help to emphasise that the publishing process has multiple steps. However, is surfacing that the publishing process has multiple steps going to solve the above issue? I don't think so. Since users in that context are not interested yet to go into the publishing path, they are unlikely to explore that way to check if they find functionality that they don't consider connected to it, being it ""preview"" or ""print"".
+",1504603185,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","You may consider my feedback withdrawn. I didn't make the connection with the operating system conventions. I have indeed used many applications that use ellipsis in context menus or top menus for items to indicate they won't be performed immediately but will require an additional interaction first (e.g. new dialog, or next panel if already in a dialog).
+
+Before I realised this connection, my main concern was that adding ellipsis would not solve the original problem, which is that users may be uncomfortable clicking this button because they may want to do a comparison first or enter an edit summary, and the current appearance of the button suggests it will be immediate. Adding ellipsis does make sense for this and might a good first step toward solving this problem.",1504553449,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","It seems that 
+* An ellipsis is standard in many UI guidelines, including Mac and Windows (as @Tgr wrote). It is an UI standard at least since the 90s and basically the icon for ""a window will open"".
+* The only feedback I remember that was contra ellipsis itself came from @Krinkle (""It doesn't clarify or improve the user experience, it only makes it more mysterious.""). 
+* The  character could be either included via CSS or in the translation messages.  
+* The ""does the save button save immediately?!"" is an actual problem (at least according to German Kurier and feedback on enwiki according to @TTO )
+
+With ellipsis, it would look like 
+
+{F7336409}
+
+@Pginer-WMF – what do you think? And: Who is the one to decide about this?",1504543438,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Yep, I’ve put the word ‘Done’ in my mockups.",1502922724,PHID-USER-2fha2mym5lty6djs2qfl,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","What about ""Complete..."", ""Final review"" or similar term to indicate the button will lead to the publication, but not being a ""Publish"" button?",1502921848,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Related to this, there is an [[ https://de.wikipedia.org/w/index.php?title=Wikipedia:Kurier&oldid=166132048 | article on the German signpost equivalent ""Kurier"" ]], in which as user talk about having trouble finding the save button and difficulties on clicking on ""save"", assuming it might save directly. 
+
+> »Zunächst einmal sucht man vergeblich einen Knopf für die Vorschau.  Wie heißt es doch: „Sei mutig!“ Wir drücken also einfach ohne Vorschau auf „Änderungen speichern“ «
+
+> Roughly translated: »We search unsuccessfully of the ""preview"" Button … They say ""Be brave"" and we press without preview on ""Save Changes""«",1496766716,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","@Frigory, @Jan_Dittrich: There is a task for this, where all this stuff should probably go, please see T155732",1495620185,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Hi @Frigory, Hi @Dvorapa,
+
+I like these ideas! I suppose they should have their own ticket. The current ticket was just meant to make the button actions clearer. Your suggestion extends the scope a lot. 
+Can you copy it in a separate tasks and mention this one (T44138)? Thus they would be kept connected and allows each one to focus on the button, two column view or both. 
+If you need help doing it, please write me or tell here. ",1495617839,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","So I could imagine something like this.
+
+- Possibility to have frames in the same dropdown, and an additional option for separate scrollbars: {F8119433}
+- A dropdown in the top right-hand corner of each frame to choose its content: {F8119439}
+- The splitted view: {F8119442} (the bar at the middle can be moved)
+- In the content selection, a ‘Switch panels’ option (I don’t know if the correct word should be ‘frame’ or ‘panel’), and the content of the other panel is grayed; also, a ‘Refresh’ button for the preview: {F8119451}
+
+Of course there should be other icons (‘Refresh’ should be an icon).
+
+This way the toolbar is even shorter than before, because ‘Done’ is shorter than ‘Publish changes’ — :).",1495137268,PHID-USER-2fha2mym5lty6djs2qfl,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","No, if I add just a button with ""Preview"" and dropdown arrow, the symbol button is moved to the second line. The problem of a space in a toolbar or why text labels should be avoided was discussed in detail in T116417 or T153306 or above I guess.",1494958136,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","No, if I add just a button with ""Preview"" and dropdown arrow, the symbol button is moved to the second line. The problem of why text labels should be avoided due was discussed in detail in T116417 or T153306 or above I guess.",1494958069,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","- Separate scrollbars could be a preference.
+- Indeed separate toolbars and dialogs are probably a bad idea.
+- I don’t understand why the Preview dropdown wouldn’t be convenient? You don’t have enough space for it?",1494957310,PHID-USER-2fha2mym5lty6djs2qfl,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","@Frigory I'm not a dev, but I like your proposals (I've already suggested some of them in a different task). Just be aware of those people with more narrow screens (like me - 1280x768), where those features like separate scrollbars, separate toolbars/dialogs and text ""Preview"" as a dropdown label are not very convenient.",1494956623,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Hello,
+
+I’m 21, and I have a bit of experience and interest in web ergonomics. I’ve contributed to the design of a few websites (notably [[http://www.france-ioi.org/|this one]], which was really worse before). I’d like to share my opinion on this task as a Wikimedia contributor. I hope I’m not too late.
+
+I’m not sure all my ideas are appropriate here but let’s spread. I’ve realized screenshots on a random article with the DOM manually modified.
+
+For the preview, I’m dreaming about something like this:
+{F8094031}
+
+I.e. two (possibly resizable) frames, one containing the code and the other one for preview or reviewing changes.
+On my desktop computer, I have two monitors with a resolution of 1920×1080. With this configuration, I could extend my browser window on the two monitors, and have the code on the first one, the preview on the second one.
+
+The initial setup would be:
+{F8094055}
+
+Then you would click on ‘Preview’ in the dropdown:
+{F8094059}
+
+It would make the preview appear on the right, half width, just like in the first screenshot but a bit larger, till the bottom:
+{F8094074}
+
+You could have full preview by sliding:
+{F8094102}
+
+You could reload the preview by clicking on the button ‘Preview’. To get the dropdown, you should click on the arrow. If you select ‘Review changes’, then the button’s label would change to ‘Review changes’.
+
+Then for writing the summary, the popup annoys me because it takes more than 1 second to appear. I contribute mainly for minor edits (orthotypo, article structure, etc.) and I sometimes do a bunch of them so I’d like efficient tools.
+I would imagine something similar to the Find & Replace panel when you click on ‘Done’:
+{F8094203}
+(I would also prefer it for template editing because the current dialog lags…)
+
+Other ideas:
+
+- Two different scrollbars: {F8094424}
+- With these separate scrollbars, a button to show the section containing the cursor in the preview, and another for the opposite (would be very useful when I’m reviewing long articles). This button could be on the vertical splitting bar.
+- For monitors having different sizes: vertically resizable frames (or two different windows?): {F8094520}
+- In the ‘Preview’/‘Review changes’ dropdown, a second subsection with 3 choices: Hidden/Splitted/Full to set the frames’ width automatically (or another button which would toggle between these 3 choices when clicked): {F8094595} I’m also suggesting new labels there. ‘Reviewing the changes’ is actually like viewing a preview of the changes.
+- Maybe having separate toolbars/dialogs in the two frames (e.g. Find & Replace with the wikitext, Publish with the preview)…
+
+Note that, currently, I’m often using two different windows for editing: the first with the wikitext editor and the second with the published article (to explore it and make the fixes at the same time; but it is quite a pity not to view the changes I’m realizing).
+
+I’m not sure I’m the ‘common’ editor but to me it would really be simpler to improve the quality of articles with such an interface, and newbies might appreciate it too.
+
+What do you think about all this? I can give more details if you feel there’s a gap somewhere.",1494907566,PHID-USER-2fha2mym5lty6djs2qfl,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",@Liuxinyu970226 That should be possible with CSS or HTML/CSS without big issues if requested and agreed upon.,1492070083,PHID-USER-caadsxn4xg5gmxrpn6kz,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3171667, @Tgr wrote:
+>>>! In T44138#3171527, @Elitre wrote:
+>> Do we know if there's an equivalent for the ellipsis for every language we support?
+> 
+> Looking at the translations for the [[https://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki%3AEllipsis|ellipsis]] and some messages containing it ([[https://translatewiki.net/w/i.php?title=Special%3ATranslations&message=Watching&namespace=8|1]], [[https://translatewiki.net/w/i.php?title=Special%3ATranslations&message=Moredotdotdot&namespace=8|2]]) it would seem so.
+
+Would it be possible to migrate all ellipsis of MediaWiki core and extensions in all languages to use ""…"" (by default, i.e. if we don't provide translations), which can help extract a lot?",1492008872,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",On desktop it's very widely used. See e.g. [[https://msdn.microsoft.com/en-us/library/windows/desktop/bb226792(v=vs.85).aspx|Microsoft]] and [[https://developer.apple.com/library/content/documentation/UserExperience/Conceptual/OSXHIGuidelines/TerminologyWording.html#//apple_ref/doc/uid/20000957-CH15-SW3|Apple]] button design guidelines.,1492006934,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">I'm not sure the standard is used in this way. It is used in dropdown menus, but I don't think it is common in push buttons. I certainly don't recall seeing it in web ""call to action-style"" buttons, ever.
+
+Yes, it is not very widely used on buttons. Checking some applications (Libreoffice and Ubuntu System  Settings), I found that: 
+* Few of the buttons I checked open new windows/popups anyway (makes sense, I assume, a button usually triggers an action)
+* For the buttons which open a new window, several had ""…""  (In Setting: ""Network""/""use as hotspot…"" ; ""Language Support""/""install / remove Languages…""; ""Security and Privacy""/ ""Files & Applications""/ ""Clear Usage Data…"")
+
+So, not //widely// used, but used, if it opens new windows. 
+
+ I think it would be an improvement.",1491926565,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","
+>>! In T44138#3162853, @Jan_Dittrich wrote:
+>> Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+> 
+> I think this would make sense – it is an established UI standard and can be found in many desktop applications. 
+> I would love to see an improved wording on the button itself, but util then, I’d go with …
+
+I'm not sure the standard is used in this way. It is used in dropdown menus, but I don't think it is common in push buttons. I certainly don't recall seeing it in web ""call to action-style"" buttons, ever.
+
+>>! In T44138#2087472, @Tgr wrote:
+> The whole save/preview/edit summary interface feels clunky and getting the way. I don't have a constructive suggestion, it's a rather straightforward way of handling saving in a WYSIWYG editor - but it does not feel right, and I hear others complaining about it as well.
+
+I think a large part of the weird feeling is having the button at the top of the screen. ""Submit"" buttons are typically at the bottom of the page, below the form they complete, to go with the reading flow (see this very interface as an example).",1491925559,PHID-USER-uqnvjf4m5wpzmkaddswb,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","
+>>! In T44138#3162853, @Jan_Dittrich wrote:
+>> Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+> 
+> I think this would make sense – it is an established UI standard and can be found in many desktop applications. 
+> I would love to see an improved wording on the button itself, but util then, I’d go with …
+
+I'm not sure the standard is used in this way. It is used in dropdown menus, but I don't think it is common in push buttons. I certainly don't recall seeing it in web ""call to action-style"" buttons, ever.",1491925344,PHID-USER-uqnvjf4m5wpzmkaddswb,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3171527, @Elitre wrote:
+> Do we know if there's an equivalent for the ellipsis for every language we support?
+
+Looking at the translations for the [[https://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki%3AEllipsis|ellipsis]] and some messages containing it ([[https://translatewiki.net/w/i.php?title=Special%3ATranslations&message=Watching&namespace=8|1]], [[https://translatewiki.net/w/i.php?title=Special%3ATranslations&message=Moredotdotdot&namespace=8|2]]) it would seem so.
+",1491923160,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","@Elitre: To better understand the concern – is this about the problem that users may see a rectangle because their fonts don't support ""…"" or about the users not understanding what ""…"" means in that context?",1491923012,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",Do we know if there's an equivalent for the ellipsis for every language we support?,1491921951,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","> Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+
+I think this would make sense – it is an established UI standard and can be found in many desktop applications. 
+I would love to see an improved wording on the button itself, but util then, I’d go with …
+
+Would look like: 
+{F7336409}",1491557467,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","> Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+
+I think this would make sense – it is an established UI standard and can be found in many desktop applications. 
+
+Would look like: 
+{F7336409}",1491557372,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",,1491557269,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",,1491557250,PHID-USER-3qggseejscb6dtiy4uyx,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","A very typical wording would be ""Review and save"" (or ""Review and publish""). It shouldn't be merely ""Save"" or ""Publish"", since the page is not immediately saved when pressing it.",1491301428,PHID-USER-uqnvjf4m5wpzmkaddswb,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","""Ready to save""?",1488280705,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Maybe there should be something like ""Proceed to save"" instead...",1487742745,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","I like the save process for the most part.  I agree this (initial label that opens the dialog) could potentially be changed, but in practice it's not really a problem as is.",1458845746,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","The whole save/preview/edit summary interface feels clunky and getting the way. I don't have a constructive suggestion, it's a rather straightforward way of handling saving in a WYSIWYG editor - but it does not feel right, and I hear others complaining about it as well.",1457067955,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","**swalling** wrote:
+
+This is being discussed on enwiki as well, at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VE_.22save.22_vs_.22finish_edit.22_button",1373412857,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","There have been a lot of complaints about this on the enwiki feedback page. One especially interesting point was raised by the ever-wise John Broughton:
+
+> [""Save page""] is the same label as on the button, in the old editing interface, that completed the edit session. Lots of effort has been made, over the years, to encourage editors to write an edit summary before they click ""Save page"", and now VE is designed exactly the opposite. The button ought to be labeled ""Finish edit"" or ""Continue"" or ""Final steps"" or just about anything other than ""Save page"".
+> The current problem is even worse than just one poorly labeled button. In VE, after clicking ""Save page"", a dialog box appears that also has a ""Save page"" button. So now an editor has to understand that the two ""Save page"" buttons do not do the same thing. And documentation (when it's written) is going to have to clarify which ""Save page"" button is being referred to - unless the label on the first occurrence of ""Save page"" is changed, as it should be.
+
+The button label on enwiki was modified to ""Finish edit"" per [[MediaWiki:Visualeditor-toolbar-savedialog]].",1433810308,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","There have been a lot of complaints about this on the enwiki feedback page. One especially interesting point was raised by the ever-wise John Broughton:
+
+> [""Save page""] is the same label as on the button, in the old editing interface, that completed the edit session. Lots of effort has been made, over the years, to encourage editors to write an edit summary before they click ""Save page"", and now VE is designed exactly the opposite. The button ought to be labeled ""Finish edit"" or ""Continue"" or ""Final steps"" or just about anything other than ""Save page"".
+
+> The current problem is even worse than just one poorly labeled button. In VE, after clicking ""Save page"", a dialog box appears that also has a ""Save page"" button. So now an editor has to understand that the two ""Save page"" buttons do not do the same thing. And documentation (when it's written) is going to have to clarify which ""Save page"" button is being referred to - unless the label on the first occurrence of ""Save page"" is changed, as it should be.
+
+The button label on enwiki was modified to ""Finish edit"" per [[MediaWiki:Visualeditor-toolbar-savedialog]].",1433810295,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","There have been a lot of complaints about this on the enwiki feedback page. One especially interesting point was raised by the ever-wise John Broughton:
+
+---
+[""Save page""] is the same label as on the button, in the old editing interface, that completed the edit session. Lots of effort has been made, over the years, to encourage editors to write an edit summary before they click ""Save page"", and now VE is designed exactly the opposite. The button ought to be labeled ""Finish edit"" or ""Continue"" or ""Final steps"" or just about anything other than ""Save page"".
+
+The current problem is even worse than just one poorly labeled button. In VE, after clicking ""Save page"", a dialog box appears that also has a ""Save page"" button. So now an editor has to understand that the two ""Save page"" buttons do not do the same thing. And documentation (when it's written) is going to have to clarify which ""Save page"" button is being referred to - unless the label on the first occurrence of ""Save page"" is changed, as it should be.
+---
+
+The button label on enwiki was modified to ""Finish edit"" per [[MediaWiki:Visualeditor-toolbar-savedialog]].",1373365011,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","I agree the toolbar button needs improvement, but imho changing the label from ""Save page"" to ""Save page..."" is not an improvement.
+
+It doesn't clarify or improve the user experience, it only makes it more mysterious.
+
+I'd prefer we look for another solution, but I think the current situation is better than having ""..."" tacked on to the label.",1370637776,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Setting milestone to 2013-06-27 since it is marked as blocker for ""Beta"" (2013-07). It may be moved to an earlier milestone as we see fit. But no later than 06-27. Setting it since I use milestone to sort ""My bugs"".",1370298498,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",Filing without prejudice as to whether we should implement.,1360206161,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: ""Watch this"" checkbox in Save dialog should use same logic as core EditPage","When using VisualEditor currently when creating a page, the ""Save page"" dialog box has two checkboxes below the edit summary input: ""This is a minor edit"" and ""Watch this page"".
+
+The ""Watch this page"" checkbox is not auto-checked, even though it is (for my account) via the non-VisualEditor editor. There's a user preference (""Add pages I create and files I upload to my watchlist"") that controls whether this checkbox is checked by default when creating a page. VisualEditor currently ignores the value of this user preference. It should respect it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1352957160,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-u4tbayn5u7dwwaa4yhrw,task_description,resolved
+"VisualEditor: ""Watch this"" checkbox in Save dialog should use same logic as core EditPage",Change-Id: Ic3daf32505a745b3cccd0663a03bbf7f3885be84,1354773511,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u4tbayn5u7dwwaa4yhrw,task_subcomment,NA
+"VisualEditor: ""Watch this"" checkbox in Save dialog should use same logic as core EditPage","If
+- option ""Watch pages I edit (watchdefault)
+- option ""Watch pages I create (watchcreations)"" (and this is a page creation)
+- the page is already watched by the user for whatever reason",1354773101,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u4tbayn5u7dwwaa4yhrw,task_subcomment,NA
+VisualEditor: Merging behaviour of lists should be looked at,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66452",1352935080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-53f6o63dslfan6juoyu2,task_description,open
+VisualEditor: Merging behaviour of lists should be looked at,I'm assuming that this is a high level tracking purpose ticket.,1362183560,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-53f6o63dslfan6juoyu2,task_subcomment,NA
+VisualEditor: Merging behaviour of lists should be looked at,"**orbit** wrote:
+
+Any details?",1362181189,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-53f6o63dslfan6juoyu2,task_subcomment,NA
+"VisualEditor: When editing a non-current revision of a page, alter the ""Save page"" button behaviour","Current behaviour on oldid pages is the same as for current ones - that is, the ""Save page"" button is greyed out and won't activate until the content changes.
+
+However, for oldid pages the content is already ""changed"" compared to the current revision, so it should be active right from the start. Also, ideally it should say ""Restore page"" at first, changing to ""Save page"" when/if the page's contents have been altered.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1352324940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y3mmi3dje57c7pi3w742,task_description,resolved
+"VisualEditor: When editing a non-current revision of a page, alter the ""Save page"" button behaviour",Merged into master.,1354737639,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-y3mmi3dje57c7pi3w742,task_subcomment,NA
+"VisualEditor: When editing a non-current revision of a page, alter the ""Save page"" button behaviour",I8b30c2a153911f44643e369b7c6a9b89c0fb2c5b should resolve the rest of this.,1354655326,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-y3mmi3dje57c7pi3w742,task_subcomment,NA
+"VisualEditor: When editing a non-current revision of a page, alter the ""Save page"" button behaviour","Partially resolved in I9e5ce76520e091612afe4fbc0300cff8ca645335
+
+No changes to labels yet.",1352325656,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-y3mmi3dje57c7pi3w742,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"**Author:** `orbit`
+
+**Description:**
+Internet Explorer 10, the most cutting-edge browser on the planet, is displaying the context menu far away from the end of the selection. It looks to be about 300 pixels to the right and 150 pixels down - similar to the size of the inspector. Maybe it's related?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1350690900,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gwjsvonglc5wqb5w3xah,task_description,resolved
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"Change 283443 merged by jenkins-bot:
+Update RangeFix to 0.2.0
+
+[[https://gerrit.wikimedia.org/r/283443]]",1460746418,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"Change 283443 had a related patch set uploaded (by Esanders):
+Update RangeFix to 0.2.0
+
+[[https://gerrit.wikimedia.org/r/283443]]
+",1460643139,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,Fixed in RangeFix: https://github.com/edg2s/rangefix/pull/4,1460642589,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"getClientRects (native function) is messed up in IE10 and below when the zoom level is not 100%, it looks like it's applying the zoom factor twice. It may be able to fix it using screen.deviceXDPI / screen.logicalXDPI to calculate the zoom level - maybe this can be done upstream in RangeFix...",1460638469,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"You would think our code would have changed a lot in the past two years, but this bug is still reproducible. It doesn't happen in IE11 though.",1409962684,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"Dhaval: There was a recent fix to the client test module here:
+https://gerrit.wikimedia.org/r/#/c/45183/ Which was deployed on Tuesday.
+
+This fixed a problem with VisualEditor being enabled in IE despite it being configured to be disabled for all versions of Internet Explorer during this deployment.
+
+However, there is a recent patch to enable VisualEditor in IE9 and above.
+https://gerrit.wikimedia.org/r/#/c/45233/
+Which should be rolled out in the next VisualEditor deployment.",1359072321,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,I couldn't see the visual editor option at all in IE10. I am using Windows 7 and IE10.0.9200,1359065509,PHID-USER-wi7txqp5ld5ze33dx7am,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"Yes, sorry; Rangy is a library on which VisualEditor depends heavily, and this appears to be a bug with Rangy that we'd want to get fixed upstream rather than hack around. We've got a reasonable relationship with Rangy's author, so this shouldn't be impossible. :-)",1351101004,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"(In reply to comment #2)
+> Rangy bug. To file/fix upstream?
+
+Means https://code.google.com/p/rangy/issues/list ?
+Curious how to isolate if it is an upstream issue?",1351039040,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,Rangy bug. To file/fix upstream?,1350929614,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"**orbit** wrote:
+
+This only happens when zoomed in.",1350691603,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"Wikitext:
+
+[[汉]]字
+
+Parsoid:
+
+<p data-parsoid=""{&quot;dsr&quot;:[0,6]}""><a rel=""mw:WikiLink"" href=""./汉"" data-parsoid=""{&quot;tsr&quot;:[0,6],&quot;bsp&quot;:[0,6],&quot;a&quot;:{&quot;href&quot;:&quot;./汉&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;汉&quot;},&quot;stx&quot;:&quot;simple&quot;,&quot;tail&quot;:&quot;字&quot;,&quot;dsr&quot;:[0,6]}"">汉字</a></p>
+
+PHP Parser <https://www.mediawiki.org/w/index.php?title=Project:Sandbox&oldid=594926>:
+
+<p><a href=""/w/index.php?title=%E6%B1%89&amp;action=edit&amp;redlink=1"" class=""new"" title=""汉 (page does not exist)"">汉</a>字</p>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350544680,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_description,resolved
+Linktrail&prefix is wrongly applied to CJK characters,"This seems fixed, but I found bug 54891 when testing it. Not sure whether this should be considered a bug on VisualEditor side or in Parsoid serializer.",1380741319,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"This should be fixed now.  The core patch has been merged for some time.  Liangent, can you retest?",1380739640,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"There's still a patch in that depends on a core patch. It's not testable on zhwiki until the core patch is deployed. I guess that will happen at wmf11, which is (at most) four weeks away from zhwiki. But it may have fixed this.
+
+If someone could test it locally, it's at https://gerrit.wikimedia.org/r/50814 and the core patch is in the latest mediawiki (from git).",1361989473,PHID-USER-nvavrb7ko66hv3xap6sb,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"(In reply to comment #7)
+> We could do so, but it is pretty low priority for us. Note that you can also
+> point the web service to a page in the user namespace like this:
+> 
+> http://parsoid.wmflabs.org/zh/User:Liangent/Test
+
+Now linkprefix is applied incorrectly. Still the same use case: [[中]]cjk[[文]]
+
+Expected: [[中]]cjk[[文]]
+
+Actual: [[中]][[文|cjk文]]",1361878825,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"We could do so, but it is pretty low priority for us. Note that you can also point the web service to a page in the user namespace like this:
+
+http://parsoid.wmflabs.org/zh/User:Liangent/Test",1361840613,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"(In reply to comment #5)
+> We have switched to use per-language link trail (and prefix) regexps now with
+> https://gerrit.wikimedia.org/r/#/c/48589/. Our HTML form defaults to English
+> settings, but testing on a test page from the Chinese Wikipedia has a good
+> chance of working. Can you verify that the test cases above are now fixed?
+
+Can you make that HTML form accept an extra ""language"" option?",1361708371,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"We have switched to use per-language link trail (and prefix) regexps now with https://gerrit.wikimedia.org/r/#/c/48589/. Our HTML form defaults to English settings, but testing on a test page from the Chinese Wikipedia has a good chance of working. Can you verify that the test cases above are now fixed?",1361300873,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"(In reply to comment #3)
+> Liangent, how well does the new regexp work for Chinese?
+
+[[中]]cjk[[文]]
+
+This gets linktrailed which are usually not wanted. I believe there're some real world use cases on zhwiki as we usually don't put a space between Chinese and embedded English words.",1359424006,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"This specific example is working now as we have extended our negative char class to include something very close to the union of the complements of per-language character classes. This is a bit of a departure from default MediaWiki behavior, but might not be noticeable in practice. 
+
+We'd get consistent link trail behavior across languages if this works ok. If it does not, we'd have to revert to traditional per-language regexps.
+
+Liangent, how well does the new regexp work for Chinese?",1359413776,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"[09:19] <liangent> $linkTrail = '/^([a-z]+)(.*)$/sD'; is in MessagesEn.php
+[09:20] <liangent> this shouldn't include CJK characters, right?
+[09:20] <gwicke> I would think so
+[09:20] <liangent> but parsoid includes CJK chars in linktrail..
+[09:21] <gwicke> interesting- I guess we approximate the regexp to something more liberal right now
+[09:22] <gwicke> there is no i18n support yet, so we don't use the localized regexps
+[09:23] <gwicke> we currently have tail:( ![A-Z \t(),.:\n\r-] tc:text_char { return tc } )* 
+[09:24] <gwicke> I think the idea was to be very liberal about tails in the tokenizer, and to convert/validate based on language in token stream transforms
+[09:24] <gwicke> invalid tails can then be converted back to a text token
+[09:25] <gwicke> the A-Z might be a bit fishy in that context though..",1350664104,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"We don't support the localized link trail regexp yet and default to the English one, so in this case the trail is not matched as such.
+
+Currently our focus is to make Parsoid safe for the English Wikipedia first, so that we can release it as a demo in December. After that release the plan is to shift the focus to C++, which will also enable us to call back into PHP. That should allow us to reuse the existing localizations and message systems, so we don't spend too much time reinventing the wheel in a JavaScript prototype.",1350661579,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"See gerrit 21142
+
+The latest Firefox (Iceweasel) version shipped with the latest ""working""[1] Debian is 10.x[2], so unless they install a newer Firefox manually, Debian desktop users can't use VisualEditor in Firefox.
+
+[1] http://en.wikipedia.org/wiki/Debian#Additional_repositories
+[2] http://packages.debian.org/search?keywords=iceweasel
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350539940,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-zdr6lujpo7t7bcteewl4,task_description,resolved
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"(In reply to comment #7)
+> Looks done in Gerrit change #46668?
+
+Whoops, sorry, yes, we didn't mark this bug as fixed then. Resolved since the 4 February roll-out.",1367002642,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,Looks done in gerrit 46668?,1366999513,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"I assume you have some kind of tests for the different functionalities. Exposing them would allow:
+a) Users to beta test the functionality on the UA of their choice.
+b) Vendors to actually test what fails and needs fixing (eg. Iceweasel maintainers)
+c) It's much more clear what is not working for each browser (or if it just hasn't been tested).",1352066955,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"Abstract layers can be done in another way. For example in your case, keypress is different, so we make our own keypress_ve, and for normal browsers, just use a wrapper function to map keypress_ve to keypress, but for Firefox, filter special keys out before mapping.
+
+So now for a new browser, use a simplest wrapper and ask people to press keys to test it. Once we find its behavior strange, make a special wrapper for that browser.",1350630563,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"I agree that it's difficult.
+
+For example, most of the point of the approach we've taken is to re-use browsers' native capability - this means that we can support IME, spell-checking and other things important to users of our wikis that would be (even more) hugely complex or impossible to implement in VE itself. However, this means that abstracting behaviour would go in completely the wrong direction - for more on this, see our (abandoned) EditableSurface attempt, before we switched over to ContentEditable for the core surface earlier this year.
+
+A simple example of the difficulties is that Firefox triggers a keypress event on special keys that other browsers don't, such as the cursor keys; this means we need to catch these but only on Firefox to avoid hugely unexpected behaviour (such as removing text when you make a selection with the keyboard). This, and dozens of issues like this example, is why we don't have the resources to support browsers further down the chain.",1350586012,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,Iceweasel seems to contain some backports from newer Firefox.,1350582384,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"but it's difficult for people to dig into code and find out the behavior that doesn't meet VE's requirement.
+
+maybe create some abstract layers over browsers?",1350582207,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"Though I understand the wish here, I'm afraid we in the core team have got our work cut out for us just supporting the latest, core versions of Firefox, Chrome, Safari and IE.
+
+We've already spent a good deal of time looking at compatibility with older versions of these four, with Opera, and other browsers or forks of these browsers (like Iceweasel, which from our testing is not just a re-badge of Firefox, but works differently in unexpected ways). It's not a case of just adding browses to the whitelist and assuming all will be fine.
+
+Our current browser support policy [0] is still in draft, but given the huge variance we're finding between browsers on their JavaScript models, how they react to key-press events, and similar issues that are key to making VisualEditor work. That's quite apart from the browsers that claim to support key technologies but don't (like Android native browser before 3.0) and those that don't even reach that far (like Opera Mini).
+
+It's very important to us that we don't give people false expectations of the VisualEditor working for them only to break somewhere down the line because their browser can't or won't follow what limited standards there are, or that appear to work only to break wiki content terribly when people save their changes.
+
+We would of course be delighted to accept git pushes that would fix the compatibility issues with Iceweasel and other more minor browsers, though that will be quite a lot of work in some cases. Sorry that we can't give the support you want here.
+
+[0] - https://www.mediawiki.org/wiki/VisualEditor/2012-13_Q1_forward-look#Browser_matrix",1350580222,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"With longer tables it can be very difficult to identify the columns. It might be nice if table headers stayed in view when scrolling trough a long table.
+
+This could be done with JS, but would need to be compatible with tablesorter of course.
+
+Thinking about 'fixed' position headers once the header moves out of the screen viewport. Can possibly do similar stuff with footers.
+
+--------------------------
+**Version**: 1.21.x
+**Severity**: enhancement
+**See Also**: {T12013}",1349347020,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_description,open
+Implement repeated/fixed/floating/sticky table headers,"Ah, yes it worked ----aaaaaah .. just not:
+
+as explained in
+https://en.wikipedia.org/wiki/Template:Sticky_header
+I copy/pasted: {{sticky header}}
+above the code generating this very long and wide table, but the data from the 150 lines scrolls and reappears above the sticky header : 
+
+ https://en.wikipedia.org/wiki/Template_talk:Sticky_header#sticky_header_template_works_just_about_-_just_makes_the_data_in_the_lines_scroll_under_it_and_reappear_above_the_sticky_header_:)
+",1711634392,PHID-USER-p5mohmucn4hzkcdmumnq,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Change 791014 **abandoned** by D3r1ck01:
+%%%[mediawiki/skins/Vector@master] [WIP] resources: Make sortable wikitable stick underneath sticky title%%%
+Reason:
+%%%%%%
+https://gerrit.wikimedia.org/r/791014",1706274672,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1711668368,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696548392,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696548279,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696506991,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696506917,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696506726,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#9102043, @matmarex wrote:
+> Timeless has a script that makes wide tables horizontally scrollable that might be conflicting.
+
+Correct. This is one of the problems that are hard to tackle. Sticky is relative to the first parent scrollcontext. But the skin offset (for the header) for sticky is relative to the top scroll context. This means that as we don’t really know all the situations where extra scrollers exist, it is hard to have universal CSS rules for timeless and vector 2022. The only reliable way around this, might be with JavaScript looking for scroll contexts, to set a specific class which opts out of the offset. I haven’t fully dived into that yet.",1692433044,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#9102043, @matmarex wrote:
+> Timeless has a script that makes wide tables horizontally scrollable that might be conflicting.
+
+Correct. This is one of the problems that are hard to tackle. Sticky is relative to the first parent scrollcontext. But the skin offset (for the header) for sticky is relative to the top scroll context. This means that as we don’t really know all the situations where extra scrollers exist, it is hard to have universal CSS rules for timeless and vector 2022. The only reliable way around this, might be with JavaScript looking for scroll contexts. I haven’t fully dived into that yet.",1692432972,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#9102043, @matmarex wrote:
+> Timeless has a script that makes wide tables horizontally scrollable that might be conflicting.
+
+Correct. This is one of the problems that are hard to tackle. Sticky is relative to the first parent scrollcontext. But the skin offset (for the header) for sticky is relative to the top scroll context. This means that as we don’t really know all the situations where extra scrollers exist, it is hard to have universal rules. The only reliable way around this, might be with JavaScript looking for scroll contexts. I haven’t fully dived into that yet.",1692432919,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,Timeless has a script that makes wide tables horizontally scrollable that might be conflicting.,1692375586,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#3139713, @TheDJ wrote:
+> I've created a gadget for this:
+> https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets
+> Currently inside the Testing and development section
+> 
+> It should work for all versions of Safari, most recent versions of Chrome (though less optimal), some versions of Firefox (support is a bit sketchy there).
+
+It seems to be.. buggy on #timeless when the table is wider than the article view area... Fine after editing (using VE) as it overflows, but on refresh it's broken again...",1692374274,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,It might be worthwhile to only make headers sticky for tables of a certain size and above.,1679089338,PHID-USER-wfmjbbgdraluvoigu3lo,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,It might be worthwhile to only make headers sticky for tables of a certain size.,1679089325,PHID-USER-wfmjbbgdraluvoigu3lo,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"With the sticky header in Vector2022 and sticky header in a sortable wikitable and a new patch applied, we now get.
+
+{F35130089}",1652270181,PHID-USER-7tsz7e5krfc7ng6ihkjr,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Change 791014 had a related patch set uploaded (by D3r1ck01; author: Derick Alangi):
+%%%[mediawiki/skins/Vector@master] resources: Make sortable wikitable stick underneath sticky title%%%
+https://gerrit.wikimedia.org/r/791014",1652269468,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"With @daniel's patch applied to Vector2010, here's a sample output
+
+{F35130045}
+
+{F35130044}
+
+But on Vector 2022, the sticky header hides the sticky table header.
+
+{F35130048}",1652268761,PHID-USER-7tsz7e5krfc7ng6ihkjr,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Change 791000 had a related patch set uploaded (by Daniel Kinzler; author: Daniel Kinzler):
+%%%[mediawiki/core@master] WIP: add sticky header support.%%%
+https://gerrit.wikimedia.org/r/791000",1652265418,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Change 790697 had a related patch set uploaded (by Daniel Kinzler; author: Daniel Kinzler):
+%%%[mediawiki/core@master] Extract table normalization out of tablesorter%%%
+https://gerrit.wikimedia.org/r/790697",1652192877,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Indeed, sorry: I incorrectly tested this.
+
+Still in Timeless, though.",1649709584,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#7844758, @Pols12 wrote:
+> Note `style=""position:sticky; top:0""` workaround meets an issue with new Vector sticky header (the site header displays over the table header).
+
+That has been addressed in T289817.
+",1649684393,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Note `style=""position:sticky; top:0""` workaround meets an issue with new Vector sticky header (the site header displays over the table header).",1649682592,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,@TheDJ Thanks for implementing a fix for iPhones.,1643589151,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I redid the styles for the large COVID-19 tables and added some additional features like a column of left-sticky row headers. Below are the styles and a few tables.
+* [[https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_data/styles2.css | Template:COVID-19 pandemic data/styles2.css]]
+* [[https://en.wikipedia.org/wiki/Template:2020_monthly_cumulative_COVID-19_death_totals_by_country | Template:2020 monthly cumulative COVID-19 death totals by country]]
+* [[https://en.wikipedia.org/wiki/Template:2021_monthly_cumulative_COVID-19_death_totals_by_country | Template:2021 monthly cumulative COVID-19 death totals by country]]
+* [[https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates_by_country | Template:COVID-19 pandemic death rates by country]]
+
+We found (**[[https://en.wikipedia.org/wiki/Template_talk:COVID-19_pandemic_data#New_styles_feedback|see talk]]**) that the new styles work on all tested browsers except iPhone (WebKit) browsers. The ""position: sticky;"" style works on iPhone if not on the Wikipedia site, but not on the Wikipedia site, so the mobile site's styles might be interfering. Unfortunately, I don't have any Apple products to test with. The same may be true with help from **[[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Sticky_table_headers_not_working_on_iPhone | Wikipedia:Village pump (technical)#Sticky table headers not working on iPhone]]**. Any iPhone help appreciated.
+
+With some adjustments and fine tuning, these styles could be moved to a ""Big table"" template so the styles can be included above the table's div wrapper, similar to how ""**{{Import-blanktable}}**"" and ""**{{Static row numbers}}**"" work. The ""big-table"" class would be added to the div that wraps the table.
+
+For tables with two rows of top-sticky column headers, I kept it simple with pure CSS and height/nowrap restrictions. Ideally, JavaScript would instead be used to set ""top"" for the second based on the first's ""height"", which would remove the need for height/nowrap restrictions. I didn't provide any links to tables with two top-sticky rows since the tables I updated didn't need them. Because of the JavaScript potential, it might be better to implement in Wikipedia's core instead of a template.",1643589318,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I redid the styles for the large COVID-19 tables and added some additional features like a column of left-sticky row headers. Below are the styles and a few tables.
+* [[https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_data/styles2.css | Template:COVID-19 pandemic data/styles2.css]]
+* [[https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country | Template:Monthly cumulative COVID-19 death totals by country]]
+* [[https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 | Template:Monthly cumulative COVID-19 death totals by country 2021]]
+* [[https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates_by_country | Template:COVID-19 pandemic death rates by country]]
+
+We found (**[[https://en.wikipedia.org/wiki/Template_talk:COVID-19_pandemic_data#New_styles_feedback|see talk]]**) that the new styles work on all tested browsers except iPhone (WebKit) browsers. The ""position: sticky;"" style works on iPhone if not on the Wikipedia site, but not on the Wikipedia site, so the mobile site's styles might be interfering. Unfortunately, I don't have any Apple products to test with. The same may be true with help from **[[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Sticky_table_headers_not_working_on_iPhone | Wikipedia:Village pump (technical)#Sticky table headers not working on iPhone]]**. Any iPhone help appreciated.
+
+With some adjustments and fine tuning, these styles could be moved to a ""Big table"" template so the styles can be included above the table's div wrapper, similar to how ""**{{Import-blanktable}}**"" and ""**{{Static row numbers}}**"" work. The ""big-table"" class would be added to the div that wraps the table.
+
+For tables with two rows of top-sticky column headers, I kept it simple with pure CSS and height/nowrap restrictions. Ideally, JavaScript would instead be used to set ""top"" for the second based on the first's ""height"", which would remove the need for height/nowrap restrictions. I didn't provide any links to tables with two top-sticky rows since the tables I updated didn't need them. Because of the JavaScript potential, it might be better to implement in Wikipedia's core instead of a template.",1643508964,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"@Jroberson108 
+There must be somewhere you can post this so that others can see it. I am afraid to point to other wikis such as Shoutwiki, etc.. They are often not using the latest version of Wikimedia. What about Toolforge:
+*https://wikitech.wikimedia.org/wiki/Help:Toolforge 
+
+
+",1638490929,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"@Timeshifter
+The page you linked to says ""This page is obsolete. It is being retained for archival purposes."" I'm not really sure where I can set it up.
+
+As for the code, although the majority of the use cases are covered, it's still a work-in-progress in regards to the more complex use cases like only making certain headers sticky versus all.",1638478027,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"@Jroberson108 
+Is there someplace you can set this up so we can see it in action as you make changes? Wikimedia Labs?: 
+*https://www.mediawiki.org/wiki/Wikimedia_Labs 
+
+",1638476190,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Just an update on the issues I mentioned above in regards to the work I did. I figured out a fix for the desktop browser issue, which has been implemented.
+
+The only issue left is on mobile browsers when there are multi-tiered column or row headers. The headers are sticky, but they become stacked when scrolling away. As far as I can tell, JavaScript isn't able to get the row height or column width on mobile browsers so I can assign it to the respective ""top"" and ""left"" values to prevent stacking. I've got a note on this in the JS file. The table may need to render first before they are set? Otherwise, the sticky column and/or row headers appear to work fine in mobile browsers.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox",1638424450,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Just an update on the issues I mentioned above in regards to the work I did. I figured out a fix for the desktop browser issue, which has been implemented.
+
+The only issue left is on mobile browsers when there are multi-tiered column or row headers. The headers are sticky, but they become stacked when scrolling away. As far as I can tell, JavaScript isn't able to get the row height or column width on mobile devices so I can assign it to the respective ""top"" and ""left"" values to prevent stacking. I've got a note on this in the JS file. The table may need to render first before they are set? Otherwise, the sticky column and/or row headers appear to work fine in mobile browsers.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox",1638424300,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#7539855, @Timeshifter wrote:
+> There are 4 scrolling tables that have long had sticky headers in this section:
+> *https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics 
+> 
+> Single header rows:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_vaccination_data 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 
+> 
+> Taller header row:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates 
+> 
+> Template with 2 header rows: 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country 
+
+I tested those tables. For desktop browsers (Windows 10: Chrome & Firefox), the sticky column headers work, but the row headers (country cells) weren't sticky. For mobile browsers (Android: Chrome & Firefox), there were no sticky headers. Mobile browsers are where it is needed the most because of the small screen size.",1638379200,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#7539855, @Timeshifter wrote:
+> There are 4 scrolling tables that have long had sticky headers in this section:
+> *https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics 
+> 
+> Single header rows:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_vaccination_data 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 
+> 
+> Taller header row:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates 
+> 
+> Template with 2 header rows: 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country 
+
+I tested those tables. For desktop browsers (Windows 10: Chrome & Firefox), the sticky column headers work, but the row headers (each country) weren't sticky. For mobile browsers (Android: Chrome & Firefox), there were no sticky headers. Mobile browsers are where it is needed the most because of the small screen size.",1638379157,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#7539855, @Timeshifter wrote:
+> There are 4 scrolling tables that have long had sticky headers in this section:
+> *https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics 
+> 
+> Single header rows:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_vaccination_data 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 
+> 
+> Taller header row:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates 
+> 
+> Template with 2 header rows: 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country 
+
+I tested those tables. For desktop browsers (Windows 10: Chrome & Firefox), the sticky column headers work, but the row headers weren't sticky. For mobile browsers (Android: Chrome & Firefox), there were no sticky headers. Mobile browsers are where it is needed the most because of the small screen size.",1638376988,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"There are 4 scrolling tables that have long had sticky headers in this section:
+*https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics 
+
+Single header rows:
+*https://en.wikipedia.org/wiki/Template:COVID-19_vaccination_data 
+*https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 
+
+Taller header row:
+*https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates 
+
+Template with 2 header rows: 
+*https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country ",1638344262,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"There are 3 scrolling tables that have long had sticky headers in this section:
+https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics ",1638343478,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I'm not sure if this helps any, but I've done some work on making table headers sticky while scrolling both on desktop and mobile browsers since Dec 4, 2020. This work is on my sandbox since I'm not familiar with the Wikipedia project/task workflow. Since this is my sandbox, the CSS/JS won't be included for you unless you are logged in as me. The only workaround I can think of is for you to reproduce the CSS and JS files in your sandbox.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox
+https://en.wikipedia.org/wiki/User:Jroberson108/common.css
+https://en.wikipedia.org/wiki/User:Jroberson108/common.js
+
+This code works fine for the majority of the tables, which have one row of column headers and/or one column of row headers, and works with ""sortable"".
+
+For multi-tiered headers, there are some issues where the second-tier header stacks above its first-tier header instead of sticking to its side. For desktop browsers, it works fine unless the first-tier row header is grouped and its second-tier isn't grouped (no column header issues). For mobile browsers, everything stacks. (e.g. https://en.wikipedia.org/wiki/User:Jroberson108/sandbox#Dual-tier_columns_and_rows)",1638329896,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I'm not sure if this helps any, but I've done some work on making table headers sticky while scrolling both on desktop and mobile browsers since Dec 4, 2020. This work is on my sandbox since I'm not familiar with the Wikipedia project/task workflow. Since this is my sandbox, the CSS/JS won't be included for you unless you are logged in as me. The only workaround I can think of is for you to reproduce the CSS and JS files in your sandbox.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox
+https://en.wikipedia.org/wiki/User:Jroberson108/common.css
+https://en.wikipedia.org/wiki/User:Jroberson108/common.js
+
+This code works fine for the majority of the tables, which have one row of column headers and/or one column of row headers, and works with ""sortable"". In the cases where there is a second row of column headers and/or a second column of row headers, the second header stacks against its first-tier counterpart.
+
+For multi-tiered headers, a stacking issue can occur in certain circumstances when the first-tier row header is grouped causing an overlap of the second row header, as indicated in the CSS file comments. (e.g. https://en.wikipedia.org/wiki/User:Jroberson108/sandbox#Dual-tier_columns_and_rows)",1638327549,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I'm not sure if this helps any, but I've done some work on making table headers sticky while scrolling both on desktop and mobile browsers since Dec 4, 2020. This work is on my sandbox since I'm not familiar with the Wikipedia project/task workflow. Since this is my sandbox, the CSS/JS won't be included for you unless you are logged in as me. The only workaround I can think of is for you to reproduce the CSS and JS files in your sandbox.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox
+https://en.wikipedia.org/wiki/User:Jroberson108/common.css
+https://en.wikipedia.org/wiki/User:Jroberson108/common.js
+
+This code works fine for the majority of the tables, which have one row of column headers and/or one column of row headers, and works with ""sortable"". In the cases where there is a second row of column headers and/or a second column of row headers, the second header stacks against its first-tier counterpart.
+
+For multi-tiered headers, a stacking issue can occur in certain circumstances when the first-tier row header is grouped causing an overlap of the second row header, as indicated in the CSS file comments. (e.g. https://en.wikipedia.org/wiki/User:Jroberson108/sandbox#Dual-tier_columns_and_rows)
+- Stacked multi-tier row headers wider than the first one are visible.",1638327223,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I'm not sure if this helps any, but I've done some work on making table headers sticky while scrolling both on desktop and mobile browsers since Dec 4, 2020. This work is on my sandbox since I'm not familiar with the Wikipedia project/task workflow. Since this is my sandbox, the CSS/JS won't be included for you unless you are logged in as me. The only workaround I can think of is for you to reproduce the CSS and JS files in your sandbox.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox
+https://en.wikipedia.org/wiki/User:Jroberson108/common.css
+https://en.wikipedia.org/wiki/User:Jroberson108/common.js
+
+This code works fine for the majority of the tables, which have one row of column headers and/or one column of row headers, and works with ""sortable"". In the cases where there is a second row of column headers and/or a second column of row headers, the second header stacks against its first-tier counterpart.
+
+For multi-tiered headers, a stacking issue can occur in certain circumstances when the first-tier header is grouped causing an overlap, as indicated in the CSS file comments. (e.g. https://en.wikipedia.org/wiki/User:Jroberson108/sandbox#Dual-tier_columns_and_rows)
+- Stacked multi-tier column headers taller than the top one are visible. Use the ""nowrap"" class for equal heights.
+- Stacked multi-tier row headers wider than the top one are visible.",1638324710,PHID-USER-srxdqhmx4zl3u4celq4u,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,I'm going to be deploying an update to my gadget on en.wp soon. This includes the fix for the collapsed borders + sticky. Unfortunately it seems that in Safari 14 there are now several problems with sticky table elements. The most noticeable is that the space that a table caption takes up is added above the sticky element. All these problems should be fixed in Safari 15 pretty soon however (according to the upstream tickets),1630505636,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#6654192, @XanonymusX wrote:
+> I just noticed that apparently the tables with sticky headers I created on dewiki don’t work anymore if I activate the new Vector skin! How can the skin interfere with this effect? Noticed this on Chrome.
+
+>>! In T42763#6654237, @XanonymusX wrote:
+> My question was whether there was a known interference of the new vector with position:fixed in table headers, not about a specific case.
+> 
+> Anyway, random example (taken from the Community Wishlist): [[ https://de.wikipedia.org/wiki/Red_Hot_Chili_Peppers/Diskografie | most tables here ]] have sticky headers. Works fine in old Vector and in all up-to-date browsers. With new vector position:fixed apparently is completely ignored (at least in Chrome).
+
+It was related to scrollable containers used for the skin's layout, similar to what @TheDJ mentioned above. This also caused problems with VisualEditor and other tools (e.g. T270146, T264679), and in the end the skin was changed to avoid breaking things. Looks like the fixed headers also work again now.",1622130356,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Update: [[ https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c60 | Chrome 91 will ship ]] with working position:fixed for <thead> and <tr> elements (I tested and it works), so this is much closer to reality now and all main browsers will support it soon.
+
+That means it is only details on 'when'/'how' to enable this functionality that remain to be determined.
+
+Note that position fixed for thead gets disabled inside scroll containers (like used by us on mobile), this is a technical limitation of the CSS specification: https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c59",1622129551,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Update: [[ https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c60 | Chrome 91 will ship ]] with working position:fixed for <thead> and <tr> elements, so this is much closer to reality now and all main browsers will support it soon.
+
+That means it is only details on 'when'/'how' to enable this functionality that remain to be determined.
+
+Note that position fixed for thead gets disabled inside scroll containers (like used by us on mobile), this is a technical limitation of the CSS specification: https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c59",1622129399,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Update: [[ https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c60 | Chrome 91 will ship ]] with working position:fixed for <thead> and <tr> elements, so this is much closer to reality now and all main browsers will support it soon.
+
+That means it is only details on 'when'/'how' to enable this functionality that remain to be determined.
+
+Note that position fixed for thead gets disabled inside scroll containers (like used by us on mobile), this is a technical limitation of the specification: https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c59",1622129340,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"My question was whether there was a known interference of the new vector with position:fixed in table headers, not about a specific case.
+
+Anyway, random example (taken from the Community Wishlist): [[ https://de.wikipedia.org/wiki/Red_Hot_Chili_Peppers/Diskografie | most tables here ]] have sticky headers. Works fine in old Vector and in all up-to-date browsers. With new vector position:fixed apparently is completely ignored (at least in Chrome).",1606661794,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,@XanonymusX: Please always provide links to test cases so other people could try to reproduce without having to somehow search for pages first. Thanks.,1606660747,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,I just noticed that apparently the tables with sticky headers I created on dewiki don’t work anymore if I activate the new Vector skin! How can the skin interfere with this effect? Noticed this on Chrome.,1606657775,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Reading/Enable_sticky_table_headers,1606654513,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Anyone interested feel free to work on a patch, please: https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker - thanks in advance!",1605562875,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"FYI, this task recently came up at [[ https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)/Archive_172#Always_Show_Column_Headers_in_Tables | the Village Pump ]], showing continuing interest.",1605562175,PHID-USER-tl3o6dlackm57f3qrt4b,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,This is possible in pure CSS these days with minimal dodginess; see for example the `.floatable-header` CSS at https://yugipedia.com/wiki/MediaWiki:Common.css and an example usage at https://yugipedia.com/wiki/Historic_Forbidden/Limited_Chart.,1596487144,PHID-USER-2wibf62nhsbcjs6773je,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Today I found the class //mw-sticky-header// being automatically applied to some tables on enwiki. As far as I can see, it only works in Safari and only on desktop. Does somebody know more about this?
+
+EDIT: Oh, I could have just read the thread again, my bad. So it's [[ https://en.wikipedia.org/wiki/MediaWiki:Gadget-StickyTableHeaders.js | TheDJ's gadget from 2017]]. But how come i only see this now? I have not changed my preferences recently.",1596403028,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Today I found the class //mw-sticky-header// being automatically applied to some tables on enwiki. As far as I can see, it only works in Safari and only on desktop. Does somebody know more about this?
+
+EDIT: Oh, I could have just read the thread again, my bad. So it's [[ https://en.wikipedia.org/wiki/MediaWiki:Gadget-StickyTableHeaders.js | TheDJ]]'s gadget from 2017. But how come i only see this now? I have not changed my preferences recently.",1596403009,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Today I found the class //mw-sticky-header// being automatically applied to some tables on enwiki. As far as I can see, it only works in Safari and only on desktop. Does somebody know more about this?",1596402546,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"@Sdkb: No updates, otherwise they would be in this task. :) Do you [plan to work on fixing this task](https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities), as you [increased the priority](https://www.mediawiki.org/wiki/Bug_management/Phabricator_etiquette) of this task? If so, please set yourself as assignee - thanks!",1587545384,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Any updates on this? It would be hugely useful for pages like https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources/Perennial_sources#Sources, and it's come up again at https://en.wikipedia.org/wiki/Help_talk:Table#Sticky_table_headers?.",1587515503,PHID-USER-tl3o6dlackm57f3qrt4b,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,Any updates on this? It would be hugely useful for pages like https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources/Perennial_sources#Sources.,1587515413,PHID-USER-tl3o6dlackm57f3qrt4b,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I've created a gadget for this:
+https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets
+Currently inside the Testing and development section
+
+It should work for all versions of Safari, most recent versions of Chrome (though less optimal), some versions of Firefox (support is a bit sketchy there).
+
+https://developer.microsoft.com/en-us/microsoft-edge/platform/status/positionsticky/
+https://bugzilla.mozilla.org/show_bug.cgi?id=886646
+https://bugzilla.mozilla.org/show_bug.cgi?id=975644
+https://bugs.chromium.org/p/chromium/issues/detail?id=231752
+https://developers.google.com/web/updates/2016/12/position-sticky
+https://bugs.chromium.org/p/chromium/issues/detail?id=702927",1490783329,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I've created a gadget for this:
+https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets
+Currently inside the Testing and development section
+
+It should work for all versions of Safari, most recent versions of Chrome (though less optimal), some versions of Firefox (support is a bit sketchy there).
+
+https://developer.microsoft.com/en-us/microsoft-edge/platform/status/positionsticky/
+https://bugzilla.mozilla.org/show_bug.cgi?id=886646
+https://bugs.chromium.org/p/chromium/issues/detail?id=231752
+https://developers.google.com/web/updates/2016/12/position-sticky
+https://bugs.chromium.org/p/chromium/issues/detail?id=702927",1490782070,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,*** Bug 53358 has been marked as a duplicate of this bug. ***,1377602419,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"http://datatables.net/extras/fixedheader/
+
+and 
+
+http://css-tricks.com/persistent-headers/
+
+are some of the nicest implementations i have seen so far. both require cloning the headers, which is currently not possible with sortable tables.
+
+I think that if we would want to do this, we should split of the thead and tableheader normalization of tablesorter into it's own module and reuse that for fixed headers.",1373152890,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,Moving to the right component. You need javascript to dynamically switch the styling of a table header like this.,1373123387,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Moving to the Parser component. I hope this is the right place.
+
+PS: part of https://www.mediawiki.org/wiki/Bug_management/Triage/20130307",1362674199,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,Adding 'floating' and 'fixed' to summary to clarify how we'd probably want to implement such things by dynamically switching them to position:fixed rather than actually repeating.,1349374141,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**Author:** `winne2i`
+
+**Description:**
+Column of fixed row numbers. 
+
+In tables where we enumerate something we usually add a first column with row numbers. Of course we set it as unsortable (class=unsortable) – BUT it doesn't prevent the column from being sorted while we sort another column. Then the row numbers get all messed up.
+
+There should be an additional parameter (class or something) for setting which column should not be sorted in any circumstance.
+(I cannot think of anything more in that column than row numbers…)
+
+Template:Static_row_numbers creates tables with fixed row numbers:
+https://en.wikipedia.org/wiki/Template:Static_row_numbers 
+https://en.wikipedia.org/wiki/Special:WhatLinksHere/Template:Static_row_numbers 
+
+A deprecated method is used for tables in this category: 
+*https://en.wikipedia.org/wiki/Category:Articles_with_tables_with_fixed_row_numbers
+Some of the tables in that category have row number columns that do not sort under any circumstance. Some only sort if that particular row number column header is clicked. For example; if ascending or descending ranking is desired. But none of the row number columns sort when other column heads are clicked.
+
+Wikitext of fixed row numbers in a table on Polish Wikipedia below, and in use here: 
+https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne_dyskusja/Archiwum/2012-grudzie%C5%84#Sortowanie_tabeli 
+The row number column does not sort under any circumstance.
+
+```
+{| class=""wikitable sortable"" style=""text-align:center;"" align=""left""
+!class=""unsortable""|№
+!color
+!name
+!city
+|-
+|1||white||John||New York
+|-
+|2||green||Alice||Warsaw
+|-
+|3||black||Mark||Rennes
+|}
+```
+
+Th attached chart images show what happens if the row number column is not fixed. For example; if the above table wikitext is used on English Wikipedia.
+**Attached**: {F9709}
+
+The best patch would add a column of fixed row numbers to any chart. Without having to manually enter the row numbers. Or reenter the numbers after every addition of more rows in the middle of the table. ",1348933560,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-forssl3t3nzyfxttmbjs,task_description,open
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","> Can you create a user sandbox page on that wiki with some simple example tables?
+
+Sure, see [[https://pl.wiktionary.org/wiki/Wikis%C5%82ownikarz:Peter_Bowman/autonumber|wikt:pl:Wikisłownikarz:Peter Bowman/autonumber]] ([[https://pl.wiktionary.org/w/index.php?title=Wikis%C5%82ownikarz:Peter_Bowman/autonumber&oldid=7809320|permalink]]). It looks like desktop Minerva has a different set of rules which I have not considered yet.",1635506371,PHID-USER-zzlez5ppzytn7ghyo6sc,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#7461512, @PeterBowman wrote:
+>  Example: [[https://pl.wiktionary.org/wiki/Wikis%C5%82ownik:Statystyka#J%C4%99zyki | wikt:pl:WS:STAT]].
+
+
+Thanks PeterBowman. I want to see the wikitext for a simple table. Not this:
+https://pl.wiktionary.org/w/index.php?title=Wikis%C5%82ownik:STAT/j%C4%99zyki&action=edit 
+
+Can you create a user sandbox page on that wiki with some simple example tables? 
+
+",1635361845,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Expanding on T42618#434018, [[ https://pl.wiktionary.org/w/index.php?title=MediaWiki:Gadget-autonumber.css&oldid=7808333 | wikt:pl:MediaWiki:Gadget-autonumber.css ]] works with both regular and sorted (`class=""sortable""`) tables, either HTML or wiki-syntax (`{| |}`), all basic skins (including mobile Minerva). No extra column needed, just add class `autonumber`. Example: [[https://pl.wiktionary.org/wiki/Wikis%C5%82ownik:Statystyka#J%C4%99zyki | wikt:pl:WS:STAT]].",1635344698,PHID-USER-zzlez5ppzytn7ghyo6sc,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","The new template **//{{Static row numbers}}//** is a lot better: 
+*https://en.wikipedia.org/wiki/Template:Static_row_numbers 
+
+**Works great** in both **desktop** and **mobile. **For multiple examples see: 
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox144 
+
+Unlike //{{rank}}// it **works with** the **Visual Editor. **
+
+For tables with a single header row all that is needed is to add **//{{static row numbers}}//** just above the top of the table wikitext.
+And **//class=static-row-numbers//** to the top line of the table wikitext. 
+
+For other options see the template documentation. 
+
+Is there any reason this could not be added to the Mediawiki software? That way people could just add the class to get the result. 
+
+And maybe something could be added so that multiple header rows don't need //class=static-row-header// in order for the row numbering to be correct. ",1621469845,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (whyyy)
+- edit previews (again, whyyy)
+- https://en.wikipedia.org/wiki/United_States_drug_overdose_death_rates_and_totals_over_time (what did they do right where the others failed?)
+- perhaps more pages
+
+Yeah... it's gonna suck to fix this bug if you can only see it in 'production'.
+
+(incomplete) list of pages using this template: https://en.wikipedia.org/w/index.php?title=Special%3AWhatLinksHere&target=Template%3ARank&namespace=
+
+Sorry for accidentally closing the task. I'm a noob.",1619598565,PHID-USER-5agpayhvmxww3lkrbrkw,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (whyyy)
+- edit previews (again, whyyy)
+- https://en.wikipedia.org/wiki/United_States_drug_overdose_death_rates_and_totals_over_time (what did they do right where the others failed?)
+- perhaps more pages
+
+Yeah... it's gonna suck to fix this bug if you can only see it in 'production'.
+
+(incomplete) list of pages using this template: https://en.wikipedia.org/w/index.php?title=Special%3AWhatLinksHere&target=Template%3ARank&namespace=",1619598541,PHID-USER-5agpayhvmxww3lkrbrkw,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (whyyy)
+- edit previews (again, whyyy)
+
+Yeah... it's gonna suck to fix this bug if you can only see it in 'production'.",1619597688,PHID-USER-5agpayhvmxww3lkrbrkw,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (which shouldn't use different CSS but alas they do)
+- edit previews
+
+Yeah... it's gonna suck to fix this bug if you can only see it in 'production'.",1619597661,PHID-USER-5agpayhvmxww3lkrbrkw,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (which shouldn't use different CSS but alas they do)",1619597529,PHID-USER-5agpayhvmxww3lkrbrkw,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","It has been pointed out to me that **row alignment is off when viewed in mobile browsers.** This is when using the previously mentioned **{{Rank} template.**
+
+See discussion here: 
+https://en.wikipedia.org/wiki/Talk:List_of_countries_by_population_(United_Nations)#Alignment_problem
+
+**This is another reason for an integrated, fixed row number column. **",1576042567,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A much easier and better method for creating a static row number column exists. Sandbox 89 linked below uses the new method, and is updated as needed. The table in Sandbox 89 is taken from a version of ""List of countries by incarceration rate"".
+*https://en.wikipedia.org/wiki/List_of_countries_by_incarceration_rate
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox89 
+
+It uses:
+*https://en.wikipedia.org/wiki/Template:Static_column_begin - see its documentation.
+*https://en.wikipedia.org/wiki/Template:End 
+
+{{Static column begin}} redirects to {{Rank}}
+
+Can any of that template code be used here for this phabricator task?
+
+I added class=""wikitable **nowrap** sortable"" to simplify things further.
+
+The nowrap class means the **table rows do not ladder** as the **screen is narrowed.** So the **rows always align.**
+
+**Header-lines=4** allows text alone to be zoomed to very high levels without causing row alignment problems. 
+
+Here is the wikitext at the top that adds the fixed row-number column: 
+
+```
+{{Rank | rows={{TRC|ignore=1|id=nations}} | header-lines=4 | caption=Incarceration populations and rates. From [[World Prison Brief]].}}
+{|class=""wikitable nowrap sortable mw-datatable"" border=1 style=""text-align:right;"" id=""nations""
+|-valign=bottom
+```
+
+And this goes at the end of the table:
+
+
+```
+{{End}}
+```
+",1575966318,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A much easier and better method for creating a static row number column exists. Sandbox 89 linked below uses the new method, and is updated as needed. The table in Sandbox 89 is taken from ""List of countries by incarceration rate"".
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox89 
+
+It uses:
+*https://en.wikipedia.org/wiki/Template:Static_column_begin 
+*https://en.wikipedia.org/wiki/Template:End 
+
+Can any of that template code be used here for this phabricator task?
+
+I added class=""wikitable **nowrap** sortable"" to simplify things further.
+
+The nowrap class means the **table rows do not ladder** as the **screen is narrowed.** So the **rows always align.**
+
+I set the header height to 140px so that people can increase the text size all the way to around 150% in their browsers without causing row alignment problems. 
+
+Basically, this is all that is needed at the top of the table to add the static row number column:
+
+```
+{{Static column begin
+| rows=223
+| header-text=Row
+| header-height=140px
+| text-align=right
+| caption='''Incarceration populations and rates.''' From '''[[World Prison Brief]].'''<ref name=WorldPrisonBrief/>
+}}
+{|class=""wikitable nowrap sortable"" border=1 style=text-align:right;
+|-
+! height=140px | [[Country]] (or [[dependent territory]],<br>[[Subnational administrative division|subnational]] area, etc.)
+```
+
+And this goes at the end of the table:
+
+
+```
+{{End}}
+```
+",1574313089,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A much easier and better method for creating a static row number column exists. See: List of countries by incarceration rate:
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox89 
+https://en.wikipedia.org/w/index.php?title=List_of_countries_by_incarceration_rate&oldid=927094380 
+https://en.wikipedia.org/wiki/Talk:List_of_countries_by_incarceration_rate#Much_easier_and_better_method_for_creating_static_row_number_column 
+
+It uses:
+*https://en.wikipedia.org/wiki/Template:Static_column_begin 
+*https://en.wikipedia.org/wiki/Template:End 
+
+Can any of that be used here for this phabricator task?
+
+I added class=""wikitable **nowrap **sortable"" to simplify things further.
+
+The nowrap class means the **table rows do not ladder ** as the **screen is narrowed.** So the **rows always align.**
+
+I set the header height to 140px so that people can increase the text size all the way to around 150% in their browsers without causing row alignment problems. ",1574243756,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A much easier and better method for creating a static row number column exists. See: List of countries by incarceration rate:
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox89 
+https://en.wikipedia.org/w/index.php?title=List_of_countries_by_incarceration_rate&oldid=927094380 
+https://en.wikipedia.org/wiki/Talk:List_of_countries_by_incarceration_rate#Much_easier_and_better_method_for_creating_static_row_number_column 
+
+It uses:
+*https://en.wikipedia.org/wiki/Template:Static_column_begin 
+*https://en.wikipedia.org/wiki/Template:End 
+
+Can any of that be used here for this phabricator task?
+
+I added class=""wikitable **nowrap **sortable"" to simplify things further.
+
+The nowrap class means the **table rows do not ladder ** as the **screen is narrowed.** So the** rows always align.
+**
+I set the header height to 140px so that people can increase the text size all the way to around 150% in their browsers without causing row alignment problems. ",1574243690,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","
+**[[ https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_and_correctional_supervision_rate | List of U.S. states by incarceration and correctional supervision rate ]] **is an example of a table that needs a fixed row number column. Because there are **3 separate columns that are important enough** that people want **to see them in rank order**. That can't be done with an integrated rank order column. It can only be done with a fixed row number column. 
+
+**[[ https://en.wikipedia.org/wiki/List_of_countries_by_incarceration_rate | List of countries by incarceration rate ]]** may or may not need a fixed row number column. It depends on whether one believes there is more than one column that people want to see in rank order. ",1555388540,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**List of countries by intentional homicide rate:**
+https://en.wikipedia.org/wiki/List_of_countries_by_intentional_homicide_rate
+
+The **[[https://en.wikipedia.org/w/index.php?title=List_of_countries_by_intentional_homicide_rate&oldid=876122887 | current version]]** is very usefully **sorted initially by region and subregion. ** See my comment on the talk page: 
+
+I noticed that the **current version of the table is wider than the last time I checked months ago:**
+https://en.wikipedia.org/w/index.php?title=List_of_countries_by_intentional_homicide_rate&oldid=858063940
+
+**A separate column of row numbers **(something I added to a few charts) **does not work correctly with wider tables and narrow screens. The rows do not align.**
+
+I suggest adding an integrated rank order column instead. There is new info in **[[ https://en.wikipedia.org/wiki/Help:Table | Help:Table ]]** in the Visual Editor section at the end.
+
+It makes editing of tables much easier and faster. It makes adding an integrated rank order column very easy too. Just copy and paste from another table.
+
+**Of course when the table is put in rank order, it is not sorted by region or subregion.**
+
+**That is why there is a Phabricator thread asking for an integrated row number column that remains static when the rest of the table is sorted. Then we could have wide tables that are initially sorted in any way we please.**
+
+See **[[ https://en.wikipedia.org/wiki/Help:Sorting | Help:Sorting ]]** and the section called something like: ""Auto-ranking or adding a row numbering column (1,2,3) next to a table"". See phab:T42618.
+",1546267416,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","@The_Equalizer: Welcome to Phabricator! I'm resetting the priority as you don't seem to [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | plan to work on fixing this ]] (correct me if I'm wrong!) and as the [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | Priority field summarizes and reflects reality and does not cause it ]]. If you're interested in contributing code to fix this, please refer to https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker . Or you could propose this task for the [[ https://meta.wikimedia.org/wiki/2018_Community_Wishlist_Survey | next Community Wishlist survey ]]. Thanks!",1536271320,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Team Phabricator, will there be any traction on this? This is such a core function of any table that I am surprised this has stalled for so long.
+As a builder of a few advanced tables this has been quite literally a bug-bear to me, even more so that we have a working solution on Polish Wiki.
+I appreciate the English Wiki will need some testing, but really this needs to be actively worked with a higher priority.
+Even if we implement this initially and then going forward, add functionality to make any column fixed.
+If need be I can supply coffee and biscuits to help get this going.",1536266299,PHID-USER-sdoyz3kq5f2hwi7epy2b,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Thanks for the links. I would like some links to long tables where the matmarex JS method of row numbering is being used. Of the links you provided this is the only one with such a table: 
+*https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne_dyskusja/Archiwum/2012-grudzie%C5%84#Sortowanie_tabeli 
+
+This is the class needed in the column header to fix the row numbers:
+
+!class=""unsortable ordinal""
+
+Here is the wikitext for that table below. I don't like the fact that one has to add the numbers. That is problematic. For example; with a long alphabetical list one would have to manually renumber the row numbers after each new row added in the middle of the table. Especially tedious the farther up the table one adds the row. Since all row numbers after the new row entry would have to be changed. 
+
+Can this JS solution be changed so that it also creates the row numbers? That way we can leave the row number column blank, and let the JS fill it in. Or maybe a combination of JS and CSS. Since table sorting depends on jquery.tablesorter.js, then I don't see why this JS can not be part of the solution. I like that the column header is default blank for the row number column. It is obvious it is a row of numbers, and that it is not sorting. Yet one could manually add a column header name, symbol, or icon. 
+
+```
+{| class=""wikitable sortable"" style=""text-align:center;"" align=""left""
+!class=""unsortable ordinal"" width=""25px""|
+!width=""60px""|kolor
+!width=""60px""|mebel
+!width=""60px""|miasto
+|-
+|1||biały||stół||Kraków
+|-
+|2||zielony||taboret||Iława
+|-
+|3||czarny||szafa||Puck
+|}
+```
+Is the previous CSS solution fixable? It does not require manually entering the row numbers. Could it be combined with the matmarex JS solution?",1523482294,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#4121570, @Timeshifter wrote:
+> matmarex. Could you edit that old comment of yours and add in full URLs so that we can check it out?
+
+Here you go:
+
+>>! In T42618#433972, @matmarex wrote:
+> The solution was discussed on pl.wikipedia's technical village pump[1][2] and is currently live in its common.js[3]. It's used on a few pages already, including the aforementioned [[pl:Miasta w Polsce (statystyki)]] and our help page with a list of interwiki codes, https://pl.wikipedia.org/wiki/Pomoc:Interwiki .
+> 
+> [1] https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne_dyskusja/Archiwum/2012-grudzie%C5%84#Poprawa_tabeli_w_Miasta_w_Polsce_%28statystyki%29
+> [2] https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne_dyskusja/Archiwum/2012-grudzie%C5%84#Sortowanie_tabeli
+> [3] https://pl.wikipedia.org/wiki/MediaWiki:Common.js , at the very bottom
+
+>>! In T42618#4121570, @Timeshifter wrote:
+> And could you start a new comment listing some more info and links since then. 
+Which ""more info and links"" are needed? What's missing in the current information provided? (It's hard to provide more info if you don't get told which info.)",1523443415,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","matmarex. Could you edit that old comment of yours and add in full URLs so that we can check it out? I have had to do that on old comments after we changed over to phabricator. Is the JS the same? You might update that also on that post. 
+
+And could you start a new comment listing some more info and links since then. Links to working tables, etc.. Also, any how-to pages concerning its use. I can use Google translation to figure it out somewhat. 
+
+Are people using this function of tables? Is it easy to use? Does it require a blank column to be set up? Or does it create the column too? 
+",1523392568,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","You could convince an English Wikipedia administrator to copy the solution from Polish Wikipedia that I implemented there five years ago, see comment above: T42618#433972. ",1523379257,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Could someone explain to me in simple English why there is no simple way to add a column of fixed row numbers to tables. What is blocking this? Many tables are out of date due to their use of rank order columns that are completely out of whack. Due to any change in data in the table. 
+
+There are thousands, if not tens of thousands, of tables that would benefit from this. Currently, the only method of adding a column of fixed row numbers is so tedious, timeconsuming, and problematic that only 5 tables has a column of fixed row numbers. See them here:
+*https://en.wikipedia.org/wiki/Category:Article_with_table_with_fixed_row_numbers 
+
+I bring this up now due to this template deletion discussion:
+*https://en.wikipedia.org/wiki/Wikipedia:Templates_for_discussion/Log/2018_April_10#Template:Rank_order 
+
+Removing the rank numbers might be too bold. People don't realize that there is an alternative that works better, and does the same thing (row numbers). They get pissed when the rank numbers are removed, and not replaced with the alternative (row numbers). And that takes some work. The template serves a purpose in remembering some tables to go back to someday, and hopefully someone will work on them. It also helps developers see the need for their patch that they sometimes work on, but haven't finished due to problems. There are thousands of tables that this template could be placed on.
+
+A patch would be so much simpler. ",1523374156,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Change 234473 abandoned by Krinkle:
+Add class rownumbers for tables
+
+Reason:
+Closing to reduce review noise. Feel free to re-open once task has settled on a solution.
+
+[[https://gerrit.wikimedia.org/r/234473]]",1511812174,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","This may be a starting point to pass on to others interested in this topic:
+Articles containing tables with fixed row numbers are in this hidden category: 
+*https://en.wikipedia.org/wiki/Category:Article_with_table_with_fixed_row_numbers 
+
+Please add the category to any article I have missed. 
+
+I noticed that the 800 row table with fixed row numbers is now sorting fast for me: 
+*http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 
+
+Later edit: I checked sorting using an 11-year old PC, and I see that sorting took 2 seconds for that very long table of 779 rows. 
+
+On that same 11-year-old PC sorting is fast on lists of around 200 rows. Such as this one that has fixed row numbers: 
+*http://cannabis.shoutwiki.com/wiki/Basic_2013_Global_Marijuana_March_city_list
+
+So since country lists on Wikipedia are a little over 200 rows, then this type of CSS will not be a problem, even on old PCs. Country lists are about the longest lists on Wikipedia. ",1500133061,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","This may be a starting point to pass on to others interested in this topic:
+Articles containing tables with fixed row numbers are in this hidden category: 
+*https://en.wikipedia.org/wiki/Category:Article_with_table_with_fixed_row_numbers 
+
+Please add the category to any article I have missed. 
+
+I noticed that the 800 row table with fixed row numbers is now sorting fast for me: 
+*http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 ",1500126292,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Any system of row numbering is fine by me. I saw another list today I would like to add row numbers to: 
+*https://en.wikipedia.org/wiki/List_of_minimum_wages_by_country 
+
+Click the header of the hourly PPP minimum wage column to get a list covering the highest to lowest minimum wages by country. USA is around 15th on the list. Not sure since there is no row numbering.
+
+That list though is too wide to use the method I have used in other lists. Such as in this one: 
+**https://en.wikipedia.org/wiki/List_of_countries_by_intentional_homicide_rate ",1498620295,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","It seems there are two feature requests being mixed here:
+
+1. Having a ""fixed"" column that won't change when the rows are sorted. Typically a column that numbers the rows, which we want to treat separately and not related to the other fields in each row.
+2. Not needing to manually maintain the numbers in these rows when editing pages so that you don't have to change all other rows when inserting or re-ordering entries.
+
+The current patch essentially implements a solution for issue 2 (automatically number the rows and render the row's number). It also kind of solves issue 1. It doesn't really preserve the authored cell contents, but rather it reproduces them dynamically in CSS. This still requires manual work and seems fairly limited.
+
+I'd recommend solving these problems separately. Two ideas:
+
+* Allow for automatic numbering of rows. Perhaps by providing syntax in wikitext that would allow a cell in each row to be set as the placeholder for an incrementing number within the current table. Or perhaps by generating the tables with a Lua module? Or by keeping them maintained manually, with perhaps a client-side feature in VisualEditor/WikiEditor to automatically encourage re-indexing the ""index number"" cell based on a particular marking on the class (e.g. a class on the table, similar to ""wikitable"" and ""sortable"").
+* Add a feature in tablesorter that allows one of the columns to be marked as ""static"" (similar to ""unsortable"") which will preserve that table column as-is regardless of the sorting of the rest of other columns for each row.",1495548608,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Here are some lists with row numbering: 
+*https://en.wikipedia.org/wiki/List_of_countries_by_incarceration_rate 
+*https://en.wikipedia.org/wiki/List_of_countries_by_intentional_homicide_rate 
+*https://en.wikipedia.org/wiki/List_of_countries_by_total_health_expenditure_per_capita 
+*https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_rate 
+
+Discovered another problem with the current method of row numbering. Italics used for some of the country names causes the rows to not align the farther down the list one goes. See this list revision: 
+https://en.wikipedia.org/w/index.php?title=List_of_countries_by_intentional_homicide_rate&oldid=727879356 
+Had to remove the italics to fix it. 
+
+These lists are popular and are maintained since they are in alphabetical order. The row numbering allows rank order to be seen easily with a click of the mouse on the sorting button. 
+
+The problem is that the initial setup of such lists is tedious, and subject to many rules such as no italics, no flag icons, and no references within the chart itself. All break the row alignment. Along with wide tables. So the number of columns has to be limited to allow the charts to be seen correctly on narrower screens. 
+",1467498935,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I put some tables in a sandbox of mine to see if the patch has been implemented in the test release of MediaWiki 1.27.0-wmf.7. 
+*https://test2.wikipedia.org/wiki/User:Timeshifter/Sandbox 
+
+The patch has not been implemented in the test release of MediaWiki 1.27.0-wmf.7. 
+*https://www.mediawiki.org/wiki/MediaWiki_1.27/wmf.7 ",1449321463,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I put some tables in a sandbox of mine to see if the patch has been implemented in the test release of MediaWiki 1.27.0-wmf.7. 
+*https://test2.wikipedia.org/wiki/User:Timeshifter/Sandbox 
+
+The patch has not been implemented in the test release of MediaWiki 1.27.0-wmf.7. ",1449321295,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I put some tables in a sandbox of mine to see if the patch has been implemented in the test release of MediaWiki 1.27.0-wmf.7 (dfe838b). 
+*https://test2.wikipedia.org/wiki/User:Timeshifter/Sandbox 
+
+The patch has not been implemented in the test release of MediaWiki 1.27.0-wmf.7 (dfe838b). ",1449320828,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I updated the tables in this Wikipedia article: 
+*[[https://en.wikipedia.org/wiki/List_of_countries_by_total_health_expenditure_per_capita|List of countries by total health expenditure per capita]]. 
+
+I noticed on the talk page that I had left a message over 3 years ago suggesting adding row numbering. No one had updated the list since then even though this is a topic frequently in the media. 
+
+The reason is that people had the list in rank order instead of in alphabetical order. I put it in alphabetical order which makes it much easier to update. See some of my method here: 
+*https://commons.wikimedia.org/wiki/Commons:Convert_tables_and_charts_to_wiki_code_or_image_files#Web_to_LibreOffice_Calc_to_tab2wiki
+
+Unfortunately, the current primitive method of row numbering I am using over the last few years breaks many functions of tables:
+*Flags can not be used because they break the alignment of the row-number column with the rest of the table. This adds up at the bottom of the table where the rows will be completely misaligned, especially at smaller text sizes. 
+
+*A note column can not be used due to narrow screens breaking alignment due to laddering. 
+*References can not be added within the table due to the superscript increasing the height of that one line, and thus breaking alignment. 
+*The tables can not be put side by side or laddering will occur, and alignment is broken. 
+
+This health expenditure table has to do without more than a few years of data or the table is too wide. This is a problem on many such lists of nations inside tables. For example; many more years of data could be added to these popular articles: 
+*[[https://en.wikipedia.org/wiki/List_of_countries_by_intentional_homicide_rate|List of countries by intentional homicide rate]]
+*[[https://en.wikipedia.org/wiki/List_of_countries_by_incarceration_rate|List of countries by incarceration rate]]
+
+There are many more years for homicide rates for example. See: 
+*[[https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox62|User:Timeshifter/Sandbox62]]
+
+
+
+",1448870831,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Is T113340 (Allow to request modules by CSS classes in content) holding this up? 
+
+I was looking at the proposed patch: 
+https://gerrit.wikimedia.org/r/#/c/234473 
+
+Trying to decipher the holdup from the notes there. There are so many tables not being updated because they are in rank order initially. ",1447348326,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I checked the Internet Explorer 7 page on Wikipedia: 
+https://en.wikipedia.org/wiki/Internet_Explorer_7 
+
+A reference from that article said that IE7's desktop browser share in August 2015 was 0.31%. 
+http://marketshare.hitslink.com/browser-market-share.aspx?qprid=2&qpcustomd=0",1442874731,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I was looking at: 
+https://gerrit.wikimedia.org/r/#/c/234473 
+
+and a note from Sept 3, 2015 3:31 AM says ""Added code to make the rank column always unsortable""
+
+I assume this is added to the column header?:
+```class=""unsortable"" |```
+
+That is necessary to remove the sorting icon from the header. So people will not be confused. ",1441943536,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1604298, @Timeshifter wrote:
+> How does this fail in Internet Explorer 7? Is it just a blank column? If so, that is not important in my opinion. 
+
+Yes, in IE7 and other unsupported browsers (if any), just a blank column will be shown. Or, if you add the numbers as fallback with the `rownumbers-fallback` class, these will be shown, but will be sorted along with the rest of the table, instead of being fixed.",1441352371,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1601171, @Schnark wrote:
+> Adding a blank column is easy. That's two clicks in Visual Editor, 
+
+It is not immediately intuitive, but it is easy after I figured it out! So it takes exactly 3 steps to add a row-number column to an existing table. See history: 
+https://test.wikipedia.org/w/index.php?title=User:Timeshifter/Sandbox4&action=history 
+https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox4 
+
+Now that I see how easy it is to add a blank column this is definitely easier than my previous suggestion. I could explain it all in fewer paragraphs than is currently used in [[https://en.wikipedia.org/wiki/Help:Sorting|Help:Sorting]]. See the section currently titled ""Auto-ranking or adding a row numbering column (1,2,3) next to a table"". 
+
+How does this fail in Internet Explorer 7? Is it just a blank column? If so, that is not important in my opinion. 
+
+",1441315081,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I'm of the opinion that functions like this should 'just work' and so far none of the proposals I have seen qualify as 'just work'. That means that people will use it incorrectly and there will be confusion. That's not a good experience. I'm also pondering: What would the dialog window look like for this in VE.
+
+As an 'overall picture' kind of guy, i'm just not enthusiastic and I think that we should be careful of 'feature creep' and long term maintenance burden. Sometimes it's better to NOT have a feature, then to add extra complexity.",1441275714,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","How about something like `header=Lp` in the top of the table wikitext? So to get Polish numbers and header:
+```
+{|  lang=""pl"" header=""Lp"" class=""wikitable sortable rownumbers""
+```
+
+>>! In T42618#1601171, @Schnark wrote:
+> Adding a blank column is easy. That's two clicks in Visual Editor, or replacing `/^\| /` with `| || ` with the search-and-replace-tool in the WikiEditor toolbar. Given that users are currently willing to add code like on https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_rate#Incarceration_rate_by_state adding a blank column won't scare them away.
+
+I am the one that added the fixed row numbering to that article. It had previously been in rank order, and so it was impossible to update it easily.  I added much more recent numbers that I copied from the data table of a Commons map of US incarceration rates that someone else did. It was in alphabetical order, and not rank order. The Wikipedia article had been using 2009 numbers until I updated it this summer. 
+
+This patch will not be used much if it depends on skilled editors. I don't use Wikieditor. I rarely use the Visual Editor. I barely understand some CSS, and I occasionally have figured out (and soon forgotten) some regex methods in Notepad++ to do complicated replacements within the Unicode wikitext of long lists or SVG images. Very frustrating. I am not a developer like you. I am skilled in other areas. 
+
+Currently, people are adding rank columns that are not fixed. Many of these table lists are way out of date because even a single change messes up the rank order, and the list is soon completely out of order. People stop updating it at all. A fixed row-number column fixes this because then the list can be put in alphabetical order. Alphabetical order is far easier to maintain. Sorting a column instantly produces a list in rank order. If this patch is dead simple to use then hundreds of tables will then be easy to set up and maintain. ",1441268597,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","How something like `header=Lp` in the top of the table wikitext? So to get Polish numbers and header:
+```
+{|  lang=""pl"" header=""Lp"" class=""wikitable sortable rownumbers""
+```
+
+>>! In T42618#1601171, @Schnark wrote:
+> Adding a blank column is easy. That's two clicks in Visual Editor, or replacing `/^\| /` with `| || ` with the search-and-replace-tool in the WikiEditor toolbar. Given that users are currently willing to add code like on https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_rate#Incarceration_rate_by_state adding a blank column won't scare them away.
+
+I am the one that added the fixed row numbering to that article. It had previously been in rank order, and so it was impossible to update it easily.  I added much more recent numbers that I copied from the data table of a Commons map of US incarceration rates that someone else did. It was in alphabetical order, and not rank order. The Wikipedia article had been using 2009 numbers until I updated it this summer. 
+
+This patch will not be used much if it depends on skilled editors. I don't use Wikieditor. I rarely use the Visual Editor. I barely understand some CSS, and I occasionally have figured out (and soon forgotten) some regex methods in Notepad++ to do complicated replacements within the Unicode wikitext of long lists or SVG images. Very frustrating. I am not a developer like you. I am skilled in other areas. 
+
+Currently, people are adding rank columns that are not fixed. Many of these table lists are way out of date because even a single change messes up the rank order, and the list is soon completely out of order. People stop updating it at all. A fixed row-number column fixes this because then the list can be put in alphabetical order. Alphabetical order is far easier to maintain. Sorting a column instantly produces a list in rank order. If this patch is dead simple to use then hundreds of tables will then be easy to set up and maintain. ",1441268474,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1598099, @Timeshifter wrote:
+
+> And a blank header is fine for the number column.
+
+I would consider a blank header just because the user was to lazy to add a row for it as bad practice. It's not clear whether that blank header is acceptable for everyone, see matmarex's comment:
+>>! In T42618#434067, @matmarex wrote:
+>    * In the heading neither ""№"" nor ""#"" would be acceptable in, say,
+>      Polish (we use ""Lp."" which is an abbreviation of ""ordinal
+>      number""), although this might be worked around by just leaving
+>      the space empty as tm112 suggests above; I'm not sure if that'd
+>      be acceptable for all languages we support in MediaWiki, though.
+
+
+> If editors are required to add a blank column first this will be used a lot less than it could be. Country lists have over 200 rows. 
+
+Adding a blank column is easy. That's two clicks in Visual Editor, or replacing `/^\| /` with `| || ` with the search-and-replace-tool in the WikiEditor toolbar. Given that users are currently willing to add code like on https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_rate#Incarceration_rate_by_state adding a blank column won't scare them away.
+",1441265148,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","OK, I see that currently it requires an existing blank column. See: 
+https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox3
+
+How about ""rownumbers"" class for adding numbers to an existing blank column? And ""autorownumbers"" class for adding both the numbers and the column. See:
+
+>>! In T42618#434018, @Yair_rand wrote:
+> To just get the fixed numbering column without manually adding cells to each row or using JS, one could use CSS generated-content cells with counters:
+
+But why require an existing column at all? And a blank header is fine for the number column. I used Yair_rand's method without problems on Shoutwiki. I removed the border coloring from his CSS. Maybe some other changes in the CSS too. I don't remember, since it was done a couple years ago. Here is what I did: 
+*http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+*http://cannabis.shoutwiki.com/wiki/2013list - see section called ""Alphabetical city list"".
+
+If editors are required to add a blank column first this will be used a lot less than it could be. Country lists have over 200 rows. 
+",1441229841,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","OK, I see that currently it requires an existing blank column. See: 
+https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox3
+
+How about ""rownumber"" class for adding numbers to an existing blank column? And ""autorownumber"" class for adding both the numbers and the column. See:
+
+>>! In T42618#434018, @Yair_rand wrote:
+> To just get the fixed numbering column without manually adding cells to each row or using JS, one could use CSS generated-content cells with counters:
+
+But why require an existing column at all? And a blank header is fine for the number column. I used Yair_rand's method without problems on Shoutwiki. I removed the border coloring from his CSS. Maybe some other changes in the CSS too. I don't remember, since it was done a couple years ago. Here is what I did: 
+*http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+*http://cannabis.shoutwiki.com/wiki/2013list - see section called ""Alphabetical city list"".
+
+If editors are required to add a blank column first this will be used a lot less than it could be. Country lists have over 200 rows. 
+
+",1441212943,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1594012, @Timeshifter wrote:
+> What about using ""rownumber""? Is that in use on Wikipedia, or other wikis?
+
+`rownumber` in singular or `rownumbers` in plural? But yes, that's probably the best idea.
+
+>>! In T42618#1594246, @TheDJ wrote:
+> Hmm, i still find the whole feature somewhat confusing:
+> 
+> Deployed here:
+> https://test.wikipedia.org/wiki/User:TheDJ/T42618
+
+I just added a second example, to both show how it works with an unsortable first column and how it looks like in a different language.
+
+> And it's still purely a stylistic effect, that will rely on people still fixing the fallback values, which of course they won't...
+
+Well, in most cases the fallback values won't be added at all, so users of IE6 and IE7 will see an empty row instead of the rank, which isn't perfect (that's why I think it should be possible to add a fallback), but doesn't hurt much.
+
+> And the whole initial premise of it being 'confusing' that the numbers follow the sort state, is rather an arbitrary valuation as well. I find it confusing if they don't follow the sorting actions personally. I don't know. I'm still not enthusiastic.
+
+In my example of course it doesn't make sense to have a column for the rank in the current order, but for example the table in https://de.wikipedia.org/wiki/Liste_der_Gro%C3%9Fst%C3%A4dte_in_Deutschland uses a hack to add such a fixed rank column, and it does make sense there.
+
+>>! In T42618#1594736, @Timeshifter wrote:
+> It seems that the patch does not create a column for the row numbers? Why not? 
+
+Because it doesn't know what to use as heading.",1441179713,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","It seems that the patch does not create a column for the row numbers? Why not? 
+*https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox2 ",1441142317,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","It seems that the patch does not create a column for the row numbers? Why not? 
+https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox2 ",1441141827,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","https://test.wikipedia.org/wiki/User:TheDJ/T42618
+
+> And the whole initial premise of it being 'confusing' that the numbers follow the sort state, is rather an arbitrary valuation as well. I find it confusing if they don't follow the sorting actions personally. I don't know. I'm still not enthusiastic.
+
+I suggest that the patch remove the sorting icon from the rank column. Then people are more likely to figure out that the rank column is not supposed to sort, nor change at all. The patch needs to add the ""unsortable"" class to the rank column header. See how here:
+*https://en.wikipedia.org/wiki/Help:Sorting#Making_a_column_unsortable 
+
+",1441139984,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Hmm, i still find the whole feature somewhat confusing:
+
+Deployed here:
+https://test.wikipedia.org/wiki/User:TheDJ/T42618
+
+And it's still purely a stylistic effect, that will rely on people still fixing the fallback values, which of course they won't...
+
+And the whole initial premise of it being 'confusing' that the numbers follow the sort state, is rather an arbitrary valuation as well. I find it confusing if they don't follow the sorting actions personally. I don't know. I'm still not enthusiastic.",1441135166,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","What about using ""rownumber""? Is that in use on Wikipedia, or other wikis?
+
+""mw-"" is used for mw-collapsible and mw-collapsed on Wikia:
+*http://community.wikia.com/wiki/Help:Collapsing 
+
+But not on Wikipedia: 
+*https://en.wikipedia.org/wiki/Help:Collapsing
+
+A side note. I noticed that the numbeo.com site uses fixed row numbering on most of their many sortable tables:
+*http://www.numbeo.com - for example: 
+*http://www.numbeo.com/crime/rankings_by_country.jsp - the rank column. ",1441139545,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","What about using ""rownumber""? Is that in use on Wikipedia, or other wikis?
+
+""mw-"" is used for mw-collapsible and mw-collapsed on Wikia:
+http://community.wikia.com/wiki/Help:Collapsing 
+
+But not on Wikipedia: 
+https://en.wikipedia.org/wiki/Help:Collapsing
+
+A side note. I noticed that the numbeo.com site uses fixed row numbering on most of their many sortable tables:
+*http://www.numbeo.com - for example: 
+*http://www.numbeo.com/crime/rankings_by_country.jsp - the rank column. ",1441132993,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","You almost convinced me to drop the ""mw-"" prefix, but then I noticed, that `autonumber` is already in use for autonumbered external links. This shouldn't be a problem if everything is done right, as in one case the class is on an `<a>`, in the other case on a `<table>` element, but you never know with what expectations users added rules for `.autonumber` to their personal CSS. Also note that there is a class `mw-datatable` which is used on tables in wiki content, too, so the ""mw-"" prefix isn't my invention.
+
+Of course I'm open to arguments against my concerns and other suggestions, the currently proposed patch won't be the last one.",1441092554,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I prefer simplicity. There is no great need for ""mw"" in front of the class name. I have no problem with ""autonumber"", ""rownumber"", or just ""rows"". Or anything else without ""mw"" in front of it. 
+
+I doubt too many people other than me used the old class=autonumber CSS provided by Yair_rand higher up in this thread.
+
+See: 
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+It has the Yair_rand CSS for easy autonumbering used on these pages: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_10 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 
+http://cannabis.shoutwiki.com/wiki/2013list 
+
+By changing to the latest Mediawiki class name those pages will still work when the mediawiki software used on Shoutwiki incorporates the new automatic row numbering class. I can then delete the old Yair_rand CSS for autonumbering from MediaWiki:Common.css on that Shoutwiki wiki. 
+
+",1441066023,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I prefer simplicity. There is no great need for ""mw"" in front of the class name. I have no problem with ""autonumber"", ""rownumber"", or just ""rows"". Or anything else without ""mw"" in front of it. 
+
+I doubt too many people other than me used the old class=autonumber CSS provided by Yair_rand higher up in this thread.
+
+See: 
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+It has the Yair_rand CSS for easy autonumbering used on these pages: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_10 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 
+http://cannabis.shoutwiki.com/wiki/2013list 
+
+By changing to the latest Mediawiki class name those pages will still work when the mediawiki software used on Wikia incorporates the new automatic row numbering class. I can then delete the old Yair_rand CSS for autonumbering from MediaWiki:Common.css on that Shoutwiki wiki. 
+
+",1441065859,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I prefer simplicity. There is no great need for ""mw"" in front of the class name. I have no problem with ""autonumber"", ""rownumber"", or just ""rows"". Or anything else without ""mw"" in front of it. 
+
+I doubt too many people other than me used the old class=autonumber CSS provided by Yair_rand higher up in this thread.
+
+See: 
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+It has the Yair_rand CSS for easy autonumbering used on these pages: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_10 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 
+http://cannabis.shoutwiki.com/wiki/2013list 
+
+By changing to the latest Mediawiki class name those pages will still work when the mediawiki software used on Wikia incorporates the new automatic row numbering class. I can then delete the old Yair_rand CSS for autonumbering from MediaWiki:Common.css on that Wikia wiki. 
+
+",1441065793,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Hmm, ""autonumber"" might be better in this case for consistency with existing classes from this script (like ""sortable"") and since the script aspires not to be MediaWiki-dependent.",1441044558,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1588087, @MatthiasDD wrote:
+> But why starts the classname with mw- ? I suggesst use of ""autonumber"" instesd ""mw-autonumber"".
+
+To avoid clashes with classes added to MediaWiki:Common.css, e.g. T42618#434098.
+",1441008907,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A good patch, it works good for ltr- and rtl-direction. But why starts the classname with mw- ? I suggesst use of ""autonumber"" instesd ""mw-autonumber"". Every user read this HTML-code in the wiki-editor. It should be simple and short. For the counter i suggest use of ""row"":
+  table.autonumber tr td:first-child:before {
+	counter-increment: row;
+	content: counter(row);
+}",1440971369,PHID-USER-tyoxb7kenw57z2mztwe2,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Change 234473 had a related patch set uploaded (by Gerrit Patch Uploader):
+Add class mw-autonumber for tables
+
+[[https://gerrit.wikimedia.org/r/234473]]
+",1440748008,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Is there any reason this can not be implemented right now? I will be adding row numbering to dozens of tables right away when this is implemented. Once I do so, I am sure it will be immediately added to hundreds more tables as others see how easy it is to add something like 
+class=""wikitable sortable rownumbers"" 
+
+See Help:Sorting to see how convoluted it is to add row numbers now without a class for it: 
+https://en.wikipedia.org/wiki/Help:Sorting 
+https://en.wikipedia.org/wiki/Help:Sorting#Auto-ranking_or_adding_a_row_numbering_column_.281.2C2.2C3.29_next_to_a_table 
+See also the talk page and this current thread (before it goes to the talk archive):
+https://en.wikipedia.org/wiki/Help_talk:Sorting#Accessibility_issues_when_implementing_.22rank.22_in_a_separate_table ",1439915370,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Is there any reason this can not be implemented right now? I will be adding row numbering to dozens of tables right away when this is implemented. Once I do so, I am sure it will be immediately added to hundreds more tables as others see how easy it is to add something like 
+class=""wikitable sortable rownumbers"" 
+
+See Help:Sorting to see how convoluted it is to add row numbers now without a class for it: 
+https://en.wikipedia.org/wiki/Help:Sorting 
+See also the talk page and this current thread (before it goes to the talk archive):
+https://en.wikipedia.org/wiki/Help:Sorting#Auto-ranking_or_adding_a_row_numbering_column_.281.2C2.2C3.29_next_to_a_table ",1439915268,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Bartosz Dziewoński from comment #20)
+> 1. Obviously, no support for old browsers. I understand that this is a
+>    trade-off that we're willing to make.
+
+According to http://caniuse.com/#feat=css-counters the CSS solution even works in IE8, and because IE7 and below are now grade C, a JS solution can't reach a greater level of support anyway.
+
+I doubt that there is great support for CSS Counter Styles Level 3 yet, but at least most of the stuff from Predefined Counter Styles should be supported, so localization up to the level it is done for ordered lists ([1]) should be possible.
+
+[1] https://git.wikimedia.org/blob/mediawiki%2Fcore.git/902f90a123bef85cfaf2b206c51a89ffdd416674/resources%2Fsrc%2Fmediawiki.legacy%2Fshared.css#L935",1411545124,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","In comment 18 I linked to a row-numbered sortable table in a page that no longer has that table. I copied the table from an old revision of the page to this sandbox: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_10 
+This table has 168 rows. Sorting is not slowed down by the auto numbering. 
+
+The auto numbering CSS used is found here: 
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+CSS is in the section titled ""Easy method of auto numbering of table rows"".
+
+As I said previously (comment 23) sorting a table with 779 rows is slowed down by the addition of auto numbering: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4",1400167451,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",*** Bug 10433 has been marked as a duplicate of this bug. ***,1398794576,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","On long lists autonumbering table rows means sorting any column takes longer. Around a couple seconds to sort a column 800 rows long. This is true whether using the easy CSS method or the hard CSS method (with every cell manually added in).
+
+I link to an example below of a table with around 800 rows. 
+
+With autonumbering:
+http://cannabis.shoutwiki.com/w/index.php?title=GMMcities&oldid=6398 
+Table from above-linked old revision has been copied to this sandbox after converting to the easy CSS method: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4
+
+Same table without autonumbering sorts faster:
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_5 
+
+The initial click takes a couple seconds in all cases. Click again. 
+
+I haven't been able to find a working JS method of autonumbering. Can someone link to a table with JS doing the autonumbering. I want to see how fast it is. 
+
+I have not seen any JS tables linked from previous comments that work for me. Please point me to working JS I can copy to Shoutwiki, or to my personal user JS on a wiki. So I can test it on some tables.",1396482842,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+They also say (on w3) that you can add suffix which solves the problem with number formatting that you mentioned. In such way those numbering issues are solved but every wiki would have to set its own @counter-style and heading cell content.
+(Or – can it be preset?)",1396467047,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Bartosz Dziewoński from comment #20)
+>    * No support for digit conversion (some languages use other numerals
+>      than 0 1 2 3 4 5 6 7 8 9, e.g. Arabic uses ٠‎ ١‎ ٢‎ ٣‎ ٤‎ ٥‎ ٦‎ ٧‎ ٨‎
+> ٩‎).
+>      I don't think this is possible with CSS (although I might be wrong).
+
+I underestimated the CSS designers, it does support this :) (in the spec at least). See <http://www.w3.org/TR/css-counter-styles-3/> and <http://www.w3.org/TR/predefined-counter-styles/>.",1396464926,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Yair Rand from comment #17)
+> To just get the fixed numbering column without manually adding cells to each
+> row or using JS, one could use CSS generated-content cells with counters:
+>   <snip>
+
+I was thinking about doing this with just CSS, and this solution is
+very neat, but is has two problems:
+
+1. Obviously, no support for old browsers. I understand that this is a
+   trade-off that we're willing to make.
+
+2. Less obviously, no support for internationalization!
+   * No support for digit conversion (some languages use other numerals
+     than 0 1 2 3 4 5 6 7 8 9, e.g. Arabic uses ٠‎ ١‎ ٢‎ ٣‎ ٤‎ ٥‎ ٦‎ ٧‎ ٨‎ ٩‎).
+     I don't think this is possible with CSS (although I might be wrong).
+   * No support for various typographic conventions on the number
+     formatting; again, proper Polish would require a dot to be placed
+     after the ordinal number (as in 1., 2., 3. etc. for first,
+     second, third), some might want 1st, 2nd, 3rd etc. in English as
+     well, and who knows what other languages might require.
+   * In the heading neither ""№"" nor ""#"" would be acceptable in, say,
+     Polish (we use ""Lp."" which is an abbreviation of ""ordinal
+     number""), although this might be worked around by just leaving
+     the space empty as tm112 suggests above; I'm not sure if that'd
+     be acceptable for all languages we support in MediaWiki, though.
+
+It's probably a good solution on a per-wiki basis (for at least some
+languages), but I'm afraid we won't be able to use it in core unless we
+manage to solve the above problems (might be doable with some deep LESS
+magic, at least for the latter two).",1396464716,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+This solution is great, I hope this one will be implemented soon.
+
+As for '#' or '№' – I think there could be also an empty cell or even a cell without borders and background (as if there was no cell). It could also be up to local admins choice.",1396437056,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Yair Rand from comment #17)
+> To just get the fixed numbering column without manually adding cells to each
+> row or using JS, one could use CSS generated-content cells with counters: ...
+
+It works great, and is a lot easier to use than the row-numbering method I was using before. 
+
+I am using Yair Rand's method on a ShoutWiki wiki. Currently using this easy method on the table on this page: 
+*http://cannabis.shoutwiki.com/wiki/2013list 
+
+Before I would have to manually create a cell at the beginning of each row in the table. Here is the table with the old method:
+* [Removed incorrect link]
+
+Now all I have to do is add this to the top line of any table: 
+
+class=""sortable autonumber""
+
+I adapted the CSS a little. Here it is:
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+I removed the border coloring, and I used # for the header. See: 
+https://en.wikipedia.org/wiki/Number_sign 
+- # is more common in American English. 
+
+I hope this easy method can be implemented soon on Wikipedia and the Commons. It is by far the easiest auto-row-numbering method I have seen. It would make things a lot easier than the hacks currently listed at Help:Sorting: 
+*https://en.wikipedia.org/wiki/Help:Sorting - see ""Static column"" and following sections.",1441210643,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Yair Rand from comment #17)
+> To just get the fixed numbering column without manually adding cells to each
+> row or using JS, one could use CSS generated-content cells with counters: ...
+
+It works great, and is a lot easier to use than the row-numbering method I was using before. 
+
+I am using Yair Rand's method on a ShoutWiki wiki. Currently using this easy method on the table on this page: 
+*http://cannabis.shoutwiki.com/wiki/2013list 
+
+Before I would have to manually create a cell at the beginning of each row in the table. Here is the table with the old method:
+* [Removed incorrect link]
+
+Now all I have to do is add this to the top line of any table: 
+
+class=""sortable autonumber""
+
+I adapted the CSS a little. Here it is:
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+I removed the border coloring, and I used # for the header. See: 
+https://en.wikipedia.org/wiki/Number_sign 
+# is more common in American English. 
+
+I hope this easy method can be implemented soon on Wikipedia and the Commons. It is by far the easiest auto-row-numbering method I have seen. It would make things a lot easier than the hacks currently listed at Help:Sorting: 
+*https://en.wikipedia.org/wiki/Help:Sorting - see ""Static column"" and following sections.",1439907173,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Yair Rand from comment #17)
+> To just get the fixed numbering column without manually adding cells to each
+> row or using JS, one could use CSS generated-content cells with counters: ...
+
+It works great, and is a lot easier to use than the row-numbering method I was using before. 
+
+I am using Yair Rand's method on a ShoutWiki wiki. Currently using this easy method on the tables on these pages: 
+*http://cannabis.shoutwiki.com/wiki/2014list 
+*http://cannabis.shoutwiki.com/wiki/2013list 
+
+Before I would have to manually create a cell at the beginning of each row in the table. Here is the table with the old method:
+*http://cannabis.shoutwiki.com/w/index.php?title=2014list&oldid=21668
+
+Now all I have to do is add this to the top line of any table: 
+
+class=""sortable autonumber""
+
+I adapted the CSS a little. Here it is:
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+I removed the border coloring, and I used # for the header. See: 
+https://en.wikipedia.org/wiki/Number_sign 
+# is more common in American English. 
+
+I hope this easy method can be implemented soon on Wikipedia and the Commons. It is by far the easiest auto-row-numbering method I have seen. It would make things a lot easier than the hacks currently listed at Help:Sorting: 
+*https://en.wikipedia.org/wiki/Help:Sorting - see ""Static column"" and following sections.",1396366807,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","To just get the fixed numbering column without manually adding cells to each row or using JS, one could use CSS generated-content cells with counters:
+  table.autonumber > tbody {
+    counter-reset: autonumbering;
+  }
+  table.autonumber > tbody > tr::before {
+    counter-increment: autonumbering;
+    content: counter(autonumbering);
+  }
+  table.autonumber > thead > tr::before {
+    content: ""№"";
+  }
+  table.autonumber > thead > tr::before, table.autonumber > tbody > tr::before {
+    display: table-cell;
+    padding: 0.2em;
+    border: 1px solid #AAA;
+    vertical-align: middle;
+    text-align: center;
+  }",1396243834,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I am not sure if T4315 and T12433 are resolved duplicates of this. I marked T4315 as a resolved duplicate of this, but now I am not sure. Maybe we can fix that problem too. 
+
+It would be nice if the fixed number column was automatically numbered (row numbering) without having to fill in anything in the column cells at all. 
+
+T12433 offers some automatic numbering JS that does this:
+https://en.wikipedia.org/wiki/User:Mike_Dillon/Scripts/autonumber.js 
+
+via class=""wikitable autonumber""
+
+The example given at T12433 is this: ""Example: say an author creates a chart that alphabetically lists all of the 535 members of the US Congress.  It would be laborious to list the numbers 1, 2, 3, … 533, 534, 535 near each of the 535 entries on the list.  And next time the list changes (at the next election, when names  are added to or subtracted from the list of Congress members), the author would have to repeat the laborious process of numbering the 535 entries on the  list all over again.""
+
+For T12433 the original poster's user page has moved to here:
+https://en.wikipedia.org/wiki/User:Joseph_A._Spadaro 
+
+The table wikitext he provided in T12433 produces this: 
+http://en.wikipedia.org/wiki/User:Timeshifter/Sandbox29 ",1439906511,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I am not sure if bug 2315 and bug 10433 are resolved duplicates of this. I marked bug 2315 as a resolved duplicate of this, but now I am not sure. Maybe we can fix that problem too. 
+
+It would be nice if the fixed number column was automatically numbered (row numbering) without having to fill in anything in the column cells at all. 
+
+Bug 10433 offers some automatic numbering JS that does this:
+[[User:Mike Dillon/Scripts/autonumber.js]]
+
+via class=""wikitable autonumber""
+
+The example given at bug 10433 is this: ""Example: say an author creates a chart that alphabetically lists all of the 535 members of the US Congress.  It would be laborious to list the numbers 1, 2, 3, … 533, 534, 535 near each of the 535 entries on the list.  And next time the list changes (at the next election, when names  are added to or subtracted from the list of Congress members), the author would have to repeat the laborious process of numbering the 535 entries on the  list all over again.""
+
+For bug 10433 the original poster's user page has moved to here:
+[[User:Joseph A. Spadaro]]
+
+The table wikitext he provided in bug 10433 produces this: 
+[[User:Timeshifter/Sandbox29]]",1357035993,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",%%%*** T4315 has been marked as a duplicate of this bug. ***%%%,1439906633,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",%%%*** Bug 2315 has been marked as a duplicate of this bug. ***%%%,1357034232,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",*** Bug 40634 has been marked as a duplicate of this bug. ***,1356967180,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+And I'd say it works very well…! Thanks, Bartosz!
+I really hope it will be implemented widely soon, as it's ready to work!",1356561239,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I've created a proof-of-concept implementation using the sortEnd.tablesorter event $.tablesorter fires upon finishing sorting.
+
+The code is essentially five lines:
+```
+$('table.sortable th.unsortable.ordinal').each(function(i, th) {
+	var $th = $(th), $table = $th.closest('table');
+	$table.on('sortEnd.tablesorter', function() {
+		$table.find('tr td:nth-child('+ (th.cellIndex+1) +')').each(function(j, td) {
+			$(td).text( (j+1) );
+		});
+	})
+});
+```
+This means that for every column with class=""unsortable ordinal"" on the header cell inside a table with class=""sortable"", the code will re-fill it with consecutive numbers, starting at 1, when the table is sorted. This allows for columns which contain ordinal numbers (the original use case).
+
+The solution was discussed on pl.wikipedia's technical village pump[1][2] and is currently live in its common.js[3]. It's used on a few pages already, including the aforementioned [[pl:Miasta w Polsce (statystyki)]] and our help page with a list of interwiki codes, [[pl:Pomoc:Interwiki]].
+
+[1] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Poprawa tabeli w Miasta w Polsce (statystyki)]]
+[2] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Sortowanie tabeli]]
+[3] [[pl:MediaWiki:Common.js]], at the very bottom",1523379117,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I've created a proof-of-concept implementation using the sortEnd.tablesorter event $.tablesorter fires upon finishing sorting.
+
+The code is essentially five lines:
+```
+$('table.sortable th.unsortable.ordinal').each(function(i, th) {
+  var $th = $(th), $table = $th.closest('table');
+  $table.on('sortEnd.tablesorter', function() {
+    $table.find('tr td:nth-child('+ (th.column+1) +')').each(function(j, td) {
+      $(td).text( (j+1) );
+    });
+  })
+});
+```
+This means that for every column with class=""unsortable ordinal"" on the header cell inside a table with class=""sortable"", the code will re-fill it with consecutive numbers, starting at 1, when the table is sorted. This allows for columns which contain ordinal numbers (the original use case).
+
+The solution was discussed on pl.wikipedia's technical village pump[1][2] and is currently live in its common.js[3]. It's used on a few pages already, including the aforementioned [[pl:Miasta w Polsce (statystyki)]] and our help page with a list of interwiki codes, [[pl:Pomoc:Interwiki]].
+
+[1] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Poprawa tabeli w Miasta w Polsce (statystyki)]]
+[2] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Sortowanie tabeli]]
+[3] [[pl:MediaWiki:Common.js]], at the very bottom",1439922832,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I've created a proof-of-concept implementation using the sortEnd.tablesorter event $.tablesorter fires upon finishing sorting.
+
+The code is essentially five lines:
+
+$('table.sortable th.unsortable.ordinal').each(function(i, th) {
+  var $th = $(th), $table = $th.closest('table');
+  $table.on('sortEnd.tablesorter', function() {
+    $table.find('tr td:nth-child('+ (th.column+1) +')').each(function(j, td) {
+      $(td).text( (j+1) );
+    });
+  })
+});
+
+This means that for every column with class=""unsortable ordinal"" on the header cell inside a table with class=""sortable"", the code will re-fill it with consecutive numbers, starting at 1, when the table is sorted. This allows for columns which contain ordinal numbers (the original use case).
+
+The solution was discussed on pl.wikipedia's technical village pump[1][2] and is currently live in its common.js[3]. It's used on a few pages already, including the aforementioned [[pl:Miasta w Polsce (statystyki)]] and our help page with a list of interwiki codes, [[pl:Pomoc:Interwiki]].
+
+[1] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Poprawa tabeli w Miasta w Polsce (statystyki)]]
+[2] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Sortowanie tabeli]]
+[3] [[pl:MediaWiki:Common.js]], at the very bottom",1356540538,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+(In reply to comment #10)
+> Sure. If we're going to add this, it'll be part of the jquery.tablesorter
+> module.
+
+Thanks.
+
+I just looked into the code with hope that I could help a bit but I understand too little to see what's going on there ;) But I thought I'd ask if it could be like:
+1) search for a colmun with class ""fixed"",
+2) store it's order,
+3) sort the table as usually,
+4) recover the ""fixed"" column.
+
+Or simplified version, only for ordering numbers:
+1) sort table as usually
+2) search for a column with class ""ordering-numbers""
+3) fill the cells of the column with ordering numbers.",1348967706,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to comment #9)
+> Yes, let's say it's a ""new feature"" but I feel it's inseparable part of
+> ""wikitable sortable"" feature.
+> 
+
+Sure. If we're going to add this, it'll be part of the jquery.tablesorter module.",1348965938,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+Yes, let's say it's a ""new feature"" but I feel it's inseparable part of ""wikitable sortable"" feature.
+
+And yes, you're totally right with ""fixed"", thanks for clarification.",1348965787,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Rephrasing ticket summary.
+
+If I understand correctly you're looking for a way to let a column be fixed, unaffected by row re-ordering.
+
+That is not a bug with ""unsorted"", ""unsorted"" works as it should, many people rely on the way it works. I believe you're looking for a new feature, I'll call it ""fixed"" for now.",1348964712,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+The ""every row"" issue can be avoided using:
+ table.autonumber td:first-child
+…which still doesn't change the fact that IE6/7 don't deal with it.",1348952714,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Also, this solution requires the class to be added in every row, instead of just to the header. I don't think this can be circumvented using CSS magic.",1348950369,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+Yes, that could be not only a workaround but a solution. Thanks, I didn't know about it!
+
+The counter property is supported in all major browsers (IE, FF, Opera, Chrome, Safari, maybe more). IE8 supports it only if a !DOCTYPE is specified.
+//source: http://www.w3schools.com/cssref/pr_gen_counter-increment.asp",1348950236,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to comment #3)
+> It works for me on Mozilla Firefox 15.0.1. Not sure if other browsers support
+> it.
+
+CSS counters are supported by all modern (and even slightly old) browsers except for IE <= 7. http://caniuse.com/#feat=css-counters
+
+Unfortunately I think MW still supports IE 7?",1348948811,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","See this example: http://www.mediawiki.org/w/index.php?title=User:Ciencia_Al_Poder/Test&oldid=588713
+
+Use the provided CSS code on that page to display the static numbers on the first column, that remain untouched when the table gets sorted. You can add that CSS to your personal css page.
+
+It works for me on Mozilla Firefox 15.0.1. Not sure if other browsers support it.",1348948350,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+Well, that was only just an immediate conclusion.
+
+Speaking precisely, rows of one (or more) specified column(s) should not be sorted. Most commonly it will be the 1st column as usually there are ordering numbers – e.g. list of cities in Poland* http://pl.wikipedia.org/wiki/Miasta_w_Polsce_(statystyki) – while sorting by inhabitants, area, voivodeship, (…) the cells in 1st column with ordering numbers also get sorted while they shouldn't. The 1st column with ordering numbers informs quickly e.g. ""Gdańsk is 6th in a row in terms of number of inhabitants"" or ""there are 125 cities with area <5 km²"".
+
+Ordering numbers just should be in order all the time regardless of sorting rows – otherwise they just become nonsense.
+
+*) It's big article, may load long. In this article I tried to make separate table with ordering numbers that would not be sorted but that looks like… nothing good. The feature is craved.",1348945144,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","When you sort, it's not a column what gets sorted, but the rows of the table, using the selected column as the sort key. The ""unsortable"" stands for ""do not sort using this column as a sort key"".
+
+Could you please provide a use case for this (one real example where it will be used)?
+
+[ changing from bug to enhancement]",1348934030,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","For consistency, when editing, the 'Cancel' link should really be a button along with the other buttons on the line, since it is an action like the rest of them even if it isn't directly tied to the form itself.
+
+The help link should also probably be removed entirely from at least the default installation, as no help pages actually come with said installation and thus the link doesn't go anywhere. Expecting wikis at this point to write their own editing help pages is also pretty silly, as there tend to already be much more thorough such pages on other wikis such as enwp, meta, and similar, and new projects can merely refer to those instead if needed. For any projects using the WikiEditor extension, though, having a link at all is redundant anyway as the toolbar the extension provides includes a navigable help menu directly in it.
+
+Ignore the other stuff, but the line of buttons would look something like on this: http://commons.wikimedia.org/wiki/File:Enwp_edit_20120917_with_even_less_stuff.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1348853520,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-msazj7jjbjrha34imxrt,task_description,declined
+"""Cancel"" link when editing a page should either be a button or not be there at all.","Okay, so I'm inclined to say this ain't worth doing. Closing.",1391019141,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","(In reply to comment #12)
+> If we need to be messing with the buttons, I'd say we need to be putting
+> additional emphasis on the ""Save page"" button rather than further emphasizing
+> ""Cancel"".
+
+There are some bold plans about doing just that, Steven and Jon (CC'd) know more about them than me. I think you can play with a reasonably current demo at http://ee-flow-extra.instance-proxy.wmflabs.org/wiki/Main_Page (use the ""Agora styling"" menu on the left).",1391014026,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","**skizzerz** wrote:
+
+Having Cancel be a link instead of a button is not unprecedented in designs, and in fact would be preferred for a couple of reasons:
+
+1. Making them both buttons would put extra emphasis on the Cancel action, making it more likely that users will accidentally click it and wipe their edit.
+2. If a user does not wish to actually edit, and the Cancel link is removed entirely, they may not know that they can also cancel the edit by clicking another link elsewhere (does anybody have info on how many times the cancel link is clicked vs how many edits are cancelled via other means?)
+
+If we need to be messing with the buttons, I'd say we need to be putting additional emphasis on the ""Save page"" button rather than further emphasizing ""Cancel"".
+
+Interesting further reading on the topic: http://www.lukew.com/ff/entry.asp?571=",1390929238,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","**andnlnbn18** wrote:
+
+Can I work on it?",1390925233,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.",Minor update!,1363750179,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","(In reply to comment #8)
+> The other consideration that should be made here is that MediaWiki core may end
+> up using different styling/button positions than VisualEditor (which currently
+> has one large, green ""Save page"" button _above_ the textarea).
+
+Having a button above the text area is not unprecedented - there was a labs feature that added a 'Publish' and a 'Cancel' button at the top right above the textarea. I've used it to cancel before, since it's in a convenient and expected place; dunno that I've ever used the link by the usual buttons.
+
+It really stands out with the VE sandbox, but that's the model both VE and the current editor should be following, regardless of positioning - a cancel button is intuitive. Having to click on the 'page' tab is not, and yet that is still more so than a text link that gets lost amidst the other text.",1349025940,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","The other consideration that should be made here is that MediaWiki core may end up using different styling/button positions than VisualEditor (which currently has one large, green ""Save page"" button _above_ the textarea).",1348933546,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","On the contrary, the save is the one that needs to be distinct, not the cancel, or that will really confuse people. Yes, different systems use different orientations, but it generally still works just fine - partly just because people are used to it at this point, but also because one button is consistently distinct: the one people care about. The save.
+
+The english wikipedia was right to bold that one. It should be bolded on all of them.
+
+And the cancel link should really be a button if it is going to be there at all.",1348908193,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","If there were only two actions (""save"" and ""cancel""), even then.  The positioning of the actions is important: (in LtR languages) left actions are ""backwards"" and right side actions are ""forwards"".  We are not talking about the ""word as written"" but rather the ""word as perceived"".  
+
+There have been about 4234523452345234532 studies done where human beings ignore the text ""cancel"" and simply click the button because they think it means something totally different.",1348903833,PHID-USER-ua75tm4u7cmt4mdof6vb,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","(In reply to comment #4)
+> I disagree that the ""cancel"" link *must* be a button.  If there were different
+> visual treatments to the various buttons, then it could work as a button with
+> an alternate treatment.
+> 
+> However, since all buttons have the same visual treatment, then the ""destroy""
+> action must have different treatment.  
+
+Why does it need to be different? The meaning of 'cancel' is pretty unambiguous.",1348903354,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","I disagree that the ""cancel"" link *must* be a button.  If there were different visual treatments to the various buttons, then it could work as a button with an alternate treatment.
+
+However, since all buttons have the same visual treatment, then the ""destroy"" action must have different treatment.  Ergo, it shouldn't be a button.
+
+This should be closed unless the buttons get different visual treatments.",1348888455,PHID-USER-ua75tm4u7cmt4mdof6vb,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","The following html should work for this:
+
+<a href=""/wiki/pagename"" title=""Pagename"" id=""mw-editform-cancel""><input type=""button"" name=""Cancel"" value=""Cancel""/></a>",1348886873,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.",Okay.,1348867653,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","You're conflating issues here. This bug should _only_ be about the ""Cancel"" link. Anything else (such as the ""Editing help"" link and its interaction with the WikiEditor toolbar) should be filed as separate bugs.
+
+I'm changing this bug's summary from ""'Cancel' link when editing should be a button, and 'Editing help' link is silly"" to """"Cancel"" link when editing a page should be a button"".",1348867597,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"VisualEditor: In link inspector, when you hover over a dropdown list item it should highlight (blue background), not only when using keyboard navigation","Suggested by a user.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1346774100,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t3ipmvj7oq3ez2aqp4mq,task_description,resolved
+"VisualEditor: In link inspector, when you hover over a dropdown list item it should highlight (blue background), not only when using keyboard navigation",Now in master.,1354322608,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-t3ipmvj7oq3ez2aqp4mq,task_subcomment,NA
+"VisualEditor: In link inspector, when you hover over a dropdown list item it should highlight (blue background), not only when using keyboard navigation",Hover state added in https://gerrit.wikimedia.org/r/36247,1354309419,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-t3ipmvj7oq3ez2aqp4mq,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,"The current wikitext escape algorithm adds excessive nowiki tags around quote marks.  While these are semantically correct and useful, for existing code, it introduces dirty diffs with the source wikitext.
+
+This is not a problem if unmodified DOM subtrees are serialized using original wikitext source.  But, we dont this right now.
+
+Till such time, the code needs fixing to use heuristics to eliminate nowikis where the parser can figure out the right parse without nowikis.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344977760,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-zgw6ir3d7s2sg2njimma,task_description,resolved
+Minimize unnecessary nowiki tags around quote marks,"We are using selective serialization by default, so this is no longer a major issue in practice.",1370993167,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,"(In reply to comment #3)
+> Note also that through continuous edits more cruft might be added around the
+> same source text, and at some point ugly visual changes do occur.
+
+This is VisualEditor bug 47434, which is fixed in VE master, but not yet deployed.",1366605485,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,"Note also that through continuous edits more cruft might be added around the same source text, and at some point ugly visual changes do occur.
+
+See the bold text at http://en.wikipedia.org/w/index.php?title=Yolanda_Ordaz_de_la_Cruz&oldid=551330208#Impact . It appeard through several edits, each one adding a bit.
+
+See the diff of the fix:
+
+http://en.wikipedia.org/w/index.php?title=Yolanda_Ordaz_de_la_Cruz&diff=551330391&oldid=551330208",1366483604,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,*** Bug 47442 has been marked as a duplicate of this bug. ***,1366470553,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,"Since quote heuristics are relatively complex, I guess the simplest and most reliable solution to figure out if escaping for quotes in a line is really needed would be to round-trip test the output for that line.",1344978834,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work","The VisualEditor extension currently requires a Parsoid instance to handle wikitext (cf. $wgVisualEditorParsoidURL in VisualEditor.php). This makes installing and using the extension very difficult (or impossible) for third-party users wishing to use the extension with their MediaWiki installations.
+
+Ideally, calling out to an external Parsoid instance should not be necessary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342672800,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-cxha3l6ahwyau5brwb5g,task_description,resolved
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work",Closing in favour of #parsoid-php.,1555119418,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work","Since modern web-applications are become ""stacks"" (i.e. microservices) I don't think this should be done....",1522382744,PHID-USER-g5rqg2k7irztdonlursm,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work",See https://www.mediawiki.org/wiki/Parsoid/Roadmap for our latest plans on this. Our plan is to support HTML-only wikis with VisualEditor without any dependency on Parsoid.,1359411901,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work",Mass-moving bugs into the new 'Parsoid' product.,1344281154,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work","Our plan is to port Parsoid to a C library and interface it to PHP as an extension and (for shared hosting) as a near-static binary following Tim's strategy for Lua. We have some issues to address in the JS implementation before we embark on that, so don't expect that to happen before October.
+
+We could later also port Parsoid to pure PHP, but PHP's less-than-stellar performance for memory-heavy workloads would make this only useful for very small wikis. See http://shootout.alioth.debian.org/u32/performance.php?test=binarytrees for a fun memory-heavy benchmark.",1342721922,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work",Re-wording to be specific. I know Gabriel (and Tim Starling) are already looking at solutions to this issue.,1342719453,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)","Currently just goes to latest revision, which is irritating.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1341265200,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jzhc7bilulnwxwe466rc,task_description,resolved
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)","It appears I didn't git-add the fix for this bug (I fixed several small issues at once).
+
+Since  I5bc24e0cbdf01b3704d4ccb0 is already merged, pushed for review separately:
+
+I7d702a3eb1f9ce23a5e3c9e846b00da5cead386e.",1344314009,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)",eh.. I5bc24e0cbdf01b3704d4ccb0.,1344312053,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)",Fixed in a better way in  I82e051b6f25f7e71bc7fbfcbd8e9b14ecc8870af (which fixed any and all edit-link related issues instead of hard-coding exceptions for oldid).,1344311999,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)","Fixed in I4b8e2e77ddeb3d38144a3c96790660e86d57a82d
+
+https://gerrit.wikimedia.org/r/#/c/17920/",1344295522,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)",*** Bug 38769 has been marked as a duplicate of this bug. ***,1343674164,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340654640,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_description,resolved
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"Not WORKSFORME; we actively did something that made this work (just, we didn't notice at the time). :-)",1362436146,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"(In reply to comment #4)
+> Behaviour
+> 
+> 1. Enter ""RFC 1234"" & save; it doesn't auto-nowiki, so you get a page with
+> ""RFC
+> 1234"" as wikitext which automatically links.
+> 2. Edit again in VE; you get a link which you could edit.
+This is no longer true. The behavior on master is that the link gets alienated.
+
+> 3. Saving this without changing causes the link to be unchanged (as
+> expected).
+> 4. Saving this with a different link doesn't convert 
+You can't do that, because it's an alien. You can remove it as a unit. Bolding it seems to work too, although there's a different bug that causes text to be cut off there, will investigate.
+
+> 5. Enter ""<nowiki>RFC 1234</nowiki>"" in wikitext editor, save.
+> 6. Edit in VE; you get some text link in an alien node.
+> 7. Saving this causes the link to be unchanged (as expected).
+> 
+Also alienated.
+
+Entering ""RFC 2822"" into an existing paragraph causes Parsoid to <nowiki> the entire paragraph.
+
+> Fixes for unexpected behaviours above:
+> 
+> 1. This feels a little odd; should magic links be allowed, or should Parsoid
+> (un?)magically wrap them in <nowiki>s?
+It does this now, although the entire paragraph is wrapped.
+
+> 2. This probably should be alienated in DM.
+It is now.
+
+> 4. If the link won't be alienated (i.e., option 2 is not followed), we'll
+> need
+> to special-case this kind of link and re-generate [[]]s around it (? in DM).
+Moot, because we have alienation working.
+
+Closing this bug as WORKSFORME. I saw a few weird issues while testing this, but they seem to be Parsoid serialization bugs not directly related to this bug, and I may have an out-of-date library again.",1362092338,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,Pulling from release; we won't get to this.,1355168491,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,Think there are still issues to resolve in DM (either options 1. or 2.) - Roan?,1354927639,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,https://gerrit.wikimedia.org/r/37496 has a fix for this -- but there is more to be tested and done.  Work-in-progress.  Feel free to report additional failure test cases here.,1354915694,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"Parsoid HTML+RDFa output for ""RFC 1234"" as wikitext input is:
+
+<a typeof=""mw:ExtLink/RFC"" href=""//tools.ietfs.org/html/rfc1234"" rel=""mw:ExtLink/RFC"" data-parsoid=""{&quot;tsr&quot;:[0,8],&quot;dsr&quot;:[0,8]}"">RFC 1234</a>",1354899393,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"Behaviour
+
+1. Enter ""RFC 1234"" & save; it doesn't auto-nowiki, so you get a page with ""RFC 1234"" as wikitext which automatically links.
+2. Edit again in VE; you get a link which you could edit.
+3. Saving this without changing causes the link to be unchanged (as expected).
+4. Saving this with a different link doesn't convert 
+5. Enter ""<nowiki>RFC 1234</nowiki>"" in wikitext editor, save.
+6. Edit in VE; you get some text link in an alien node.
+7. Saving this causes the link to be unchanged (as expected).
+
+Fixes for unexpected behaviours above:
+
+1. This feels a little odd; should magic links be allowed, or should Parsoid (un?)magically wrap them in <nowiki>s?
+2. This probably should be alienated in DM.
+4. If the link won't be alienated (i.e., option 2 is not followed), we'll need to special-case this kind of link and re-generate [[]]s around it (? in DM).",1354852310,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"<nowiki>RFC 12234</nowiki> round-trips just fine in Parsoid (try it at http://parsoid.wmflabs.org/_rtform/), so I think this is a VE bug. Guessing the module, please change as needed.",1343177484,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,Think this issue is going to be fixed by Parsoid as and when this is done. :-),1343175758,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,Magic links: RFC xxx stuff,1340654663,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+Support for creating and editing definition-lists in VisualEditor,"As discussed.
+
+See also:
+* {T62411}
+* {T54399}
+* {T57797}",1340654220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2yyksazxkjyor5p6mer4,task_description,open
+Support for creating and editing definition-lists in VisualEditor,"Note that VE supports ""bulletizing"" lines inside a definition list and they end up properly indented.
+
+For example, using VE to highlight 1, 2, and 3 on a page with the following wikitext
+  : 1
+  : 2
+  : 3
+and clicking ""Bullet list"" results in
+  :* 1
+  :* 2
+  :* 3
+
+Seems like this is a good start on some sort of broader support for arbitrary indention.",1415816927,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-2yyksazxkjyor5p6mer4,task_subcomment,NA
+Support for creating and editing definition-lists in VisualEditor,*** Bug 67751 has been marked as a duplicate of this bug. ***,1404964562,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2yyksazxkjyor5p6mer4,task_subcomment,NA
+Support for creating and editing definition-lists in VisualEditor,"I had a problem caused by the broken definition lists. If you have a maths equation aligned as a block using a dl ie
+
+:<math>e^{i \pi}</math>
+
+then you can't add a non indented paragraph after it. https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_2#Trying_to_add_a_line_after_an_equation
+
+This has some impact on Bug 61051 about how MathJax equations are aligned.",1396821462,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-2yyksazxkjyor5p6mer4,task_subcomment,NA
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,"From a VE test page:
+
+Perhaps a different colour font as you are editing...so you could keep track of what you're doing (TG)
+
+Not sure if we'd want to do this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60535",1340643120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ovut64wzzg2st7xdxqrv,task_description,open
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,*** Bug 65247 has been marked as a duplicate of this bug. ***,1402329075,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ovut64wzzg2st7xdxqrv,task_subcomment,NA
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,"(In reply to comment #2)
+> Perhaps the way to do this is to use the same visual clues that are used when
+> using revision tracking in OOo Writer, MS Word etc. Particularly if they use
+> the same markings as each other.
+
+Word does a thin line (1px wide, maybe) down the outer column of a page to indicate changed lines, in both the desktop and print versions, I believe, by default.",1376959499,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-ovut64wzzg2st7xdxqrv,task_subcomment,NA
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,"Perhaps the way to do this is to use the same visual clues that are used when using revision tracking in OOo Writer, MS Word etc. Particularly if they use the same markings as each other.",1375716176,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ovut64wzzg2st7xdxqrv,task_subcomment,NA
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,*** Bug 37903 has been marked as a duplicate of this bug. ***,1345669770,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-ovut64wzzg2st7xdxqrv,task_subcomment,NA
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,"Screenshot of iPad simulator
+
+iOS 5.1 simulator on Mac OS X. Screenshot attached.
+
+iOS's selection handles overlap the arrow button we add, so it can't be clicked on.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9311}",1340472240,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-byqi7qvbtypqe3qpqvys,task_description,invalid
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,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.,1399324094,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-byqi7qvbtypqe3qpqvys,task_subcomment,NA
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,"Regarding Android, I've raised a similar issue at Bug 51270.",1373682808,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-byqi7qvbtypqe3qpqvys,task_subcomment,NA
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,"Something very similar happens on my Android phone. However, if I blur the editor and refocus it, the first cursor I get upon focusing doesn't have a selection handle, but if I then move the cursor, a selection handle appears.",1363054703,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-byqi7qvbtypqe3qpqvys,task_subcomment,NA
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,"Moving to ""Mobile"" component.",1354811640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-byqi7qvbtypqe3qpqvys,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","Take a two-word link (e.g. [[Example link]]). Use the VE inspector to select ""Example"" and press the remove-formatting button. Repeat with ""link"". Now the text is ""Example <a href='...'> </a> link"", which is illegal wikitext, and renders as if there's no link there.",1340388420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_description,open
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",">>! In T39835#1170062, @NicoV wrote:
+> There's also the situation with nowiki surrounded by bold or italic formatting: [[2008|''<nowiki/>'']] in [[ https://fr.wikipedia.org/w/index.php?title=Saint-Florent-des-Bois&diff=prev&oldid=113366483 | this edit ]].
+
+{T95730}.",1429617085,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",There's also the situation with nowiki surrounded by bold or italic formatting: [[2008|''<nowiki/>'']] in [[ https://fr.wikipedia.org/w/index.php?title=Saint-Florent-des-Bois&diff=prev&oldid=113366483 | this edit ]].,1427888424,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",*** Bug 54266 has been marked as a duplicate of this bug. ***,1380072033,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","Just FYI, we have a user at en.wp stating <<I was going to give examples of what turns out to be bug 37835. As the bug is a year old, looks like this won't be fixed and therefore no use in giving the examples.>> :/",1377770349,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",*** Bug 51877 has been marked as a duplicate of this bug. ***,1374879481,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","I don't know if it is related to this bug, but it is no longer possible to select only part of a link. Previously you could unlink the second word separately for example. See also bug 51531 and bug 50945",1374066259,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","Change 74084 had a related patch set uploaded by Catrope:
+[WIP] Unwrap whitespace-only links
+
+https://gerrit.wikimedia.org/r/74084",1374014852,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",Pulling from this milestone as it's a lot of work for a small feature.,1366141216,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","(In reply to comment #4)
+> We probably shouldn't allow users to create whitespace-only links, because
+> they
+> don't render correctly in HTML let alone wikitext. I'm going to work on a
+> change that strips whitespace-only links in the converter.
+This part depends on bug 46464.",1364433622,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","<a> </a> doesn't actually render as a clickable link in Firefox. Even if you set text-decoration:underline; on it, it still doesn't render and can't be clicked. However, <a>&nbsp;</a> does behave ""correctly"".
+
+We probably shouldn't allow users to create whitespace-only links, because they don't render correctly in HTML let alone wikitext. I'm going to work on a change that strips whitespace-only links in the converter.",1363987143,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","(In reply to comment #2)
+> (In reply to comment #0)
+> >  ""Example <a href='...'> </a> link"", which is illegal wikitext.
+> 
+> ... because [[Foo| ]] will trigger the pipe-trick and turn it into [[Foo|Foo]].
+
+Actually, it doesn't (current master, not using Tidy).
+
+<pre>
+* [[Foo]]
+* [[Foo|]]
+* [[Foo| ]]
+* [[Foo|<nowiki></nowiki>]]
+* [[Foo|<nowiki> </nowiki>]]
+</pre>
+
+Expands to:
+
+* [[Foo]]
+* [[Foo|Foo]]
+* [[Foo| ]]
+* [[Foo|<nowiki></nowiki>]]
+* [[Foo|<nowiki> </nowiki>]]
+
+Renders as:
+
+<ul><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo"">Foo</a>
+</li><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo"">Foo</a>
+</li><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo""> </a>
+</li><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo""></a>
+</li><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo""> </a>
+</li></ul>
+
+Which means a loose space works, and with <nowiki> it even works when empty. Good news :)",1349132566,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","(In reply to comment #0)
+>  ""Example <a href='...'> </a> link"", which is illegal wikitext.
+
+... because [[Foo| ]] will trigger the pipe-trick and turn it into [[Foo|Foo]].",1349132335,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",Mass-moving items into VisualEditor product,1340402731,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+migrate MedaWiki from using BiDirectional characters by properly embedding any item using directionality syntax,"**Author:** `gangleri`
+
+**Description:**
+Hi! It is long time ago since Nikerabbit installed Goylem a RTL testwiki. At that time I suggested the usage of BiDirectional characters to stabilize the common look and feel of pages as recent changes, etc.
+
+It should be possible to obtain the same result by properly embed all objects and the delimiters (spaces or whatsoever) with directionality syntax.
+
+An example is available at bug 36803#0
+and http://en.wikipedia.org/?oldid=492307285#bugzilla ,
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1336886760,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eype2avbpoowyttmdlqv,task_description,resolved
+migrate MedaWiki from using BiDirectional characters by properly embedding any item using directionality syntax,"I'll allow myself to close it.
+
+In essence, VisualEditor now allows to edit template parameters comfortably separately from the rest of the text, and also includes a lang/dir setting (both made mostly by @mooeypoo; thanks!)
+
+Some articles might still be using bidirectional control characters (probably not much in the English Wikipedia, but quite a lot in the Hebrew Wikipedia), but that's a matter for editors and not developers.",1440920059,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-eype2avbpoowyttmdlqv,task_subcomment,NA
+migrate MedaWiki from using BiDirectional characters by properly embedding any item using directionality syntax,"I definitely have plans to introduce fine-grained control of directionality, maybe in the Visual Editor age and maybe even earlier (see https://www.mediawiki.org/wiki/Visual_editor/Bidirectional_text_requirements ). But I'm not sure that I understand what are you referring to.
+
+<span dir=""rtl/ltr""> doesn't solve everything in a heavily mixed-directionality environment. For example, a title in an RTL wiki can be LTR. <bdi> would be more comprehensive than span, but the support for it is not yet completely stable, neither in the browsers nor in MediaWiki (see bug 31817).",1336888426,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-eype2avbpoowyttmdlqv,task_subcomment,NA
+VisualEditor: Ctrl + K should trigger link inspector,"Pressing Ctrl + K doesn't work in chrome16/win7. It just produces a ? in the url bar instead with a dropdown option saying
+
+<Enter query> - Google search
+
+Repeated pressing does not solve the issue either.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1335243600,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_description,resolved
+VisualEditor: Ctrl + K should trigger link inspector,"**orbit** wrote:
+
+Fixed in:
+https://gerrit.wikimedia.org/r/12977
+Will release soon.",1340671640,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_subcomment,NA
+VisualEditor: Ctrl + K should trigger link inspector,Mass-moving items into VisualEditor product,1340402766,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_subcomment,NA
+VisualEditor: Ctrl + K should trigger link inspector,"I can confirm this issue on Ubuntu 12.04, Chrome 19.0.1084.56.",1340396406,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_subcomment,NA
+VisualEditor: Ctrl + K should trigger link inspector,"WORKSFORME on Ubuntu 12.04, Google Chrome 19.0.1084.56.
+
+Could you check if it is still happening on Windows 7?",1340332908,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_subcomment,NA
+VisualEditor: Sticky selection popup,"Playing around with text selection a bit I was able to find a ""sticky"" popup.
+
+Environment: Win7, Chrome 16
+
+What I did:
+1. Select some text
+2. Click on the small arrow that appears above the selected text
+3. Select the ""create link"" icon
+4. Neither input title for the link, nor close the popup
+5. Instead take the caret somewhere else and select some other word
+6. Repeat 4 and 5 a few times
+
+Soon, the following js error was generated:
+
+Uncaught Invalid annotation error. Can not find non-annotation data in character.
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:54
+ve.dm.DocumentNode.getIndexOfAnnotation
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:54
+ve.ce.Surface.removeInsertionAnnotation
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:103
+ve.ce.Surface.annotate
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:102
+ve.ui.LinkInspector.onClose
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:133
+ve.ui.Inspector.close
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:123
+ve.ui.Context.closeInspector
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:129
+(anonymous function)
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:122
+jQuery.event.dispatch
+load.php:49
+jQuery.event.add.elemData.handle.eventHandle
+load.php:42
+
+Plus, after a reload; I did the following:
+1. Select text
+2. Click on the arrow above it
+3. Not click any icon but instead take the caret elsewhere. This should (as I see it) have ideally closed the popup, but it didn't.
+4. I clicked on bold and italics but that does nothing (since because the caret has moved there is currently no text selected).
+5. Since the popup is still open, clicking on the link icon opens the link window, and closing it finally closes the popup.
+
+If the first 4 steps are reproduced and step 5 is replaced by clicking on the tickmark instead of the close, nothing happens since no text is selected. The click neither inserts a link into the page, nor closes the popup. After this, even clicking on the close doesn't close the popup. The caret can be moved and other text selected, but that just brings up the arrow and popup again. The previous popup still sticks. The popup finally went away on selecting an existing link in the text and clicking on the link icon in the toolbar. This made the link title appear in the popup and the close button finally worked.
+
+After another reload, I tried the following:
+1. Select text
+2. Click on the arrow
+3. Select some other word. Now, selecting some other word automatically moves the popup to be near the new selection, i.e the popup is already open for the new selection if the popup for the original selection isn't closed before making a new selection. Also, after step 2, since the popup is open, nothing below the popup can be selected without closing the popup first.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1335241260,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xiaw7dpykpv6pphvabfq,task_description,resolved
+VisualEditor: Sticky selection popup,"This was partly fixed a few commits ago. 
+Though, context icon was not being properly cleared when the editor loses focus.
+Steps to reproduce: 
+
+Make a selection (Icon appears)
+
+Click anywhere outside of the editor. ( lose selection, icon is stuck )
+
+Fixed in https://gerrit.wikimedia.org/r/16794",1343345020,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-xiaw7dpykpv6pphvabfq,task_subcomment,NA
+VisualEditor: Sticky selection popup,Mass-moving items into VisualEditor product,1340402736,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xiaw7dpykpv6pphvabfq,task_subcomment,NA
+VisualEditor: Sticky selection popup,"Btw, the second, third and fourth tests also produced some js-errors; but I forgot to note them down.",1335241495,PHID-USER-4bjsher5mqcoikeqnnec,PHID-TASK-xiaw7dpykpv6pphvabfq,task_subcomment,NA
+VisualEditor: All annotations are broken,"Editing annotations is broken in VisualEditor. Selecting some text and then clicking either Bold, Italics, Link, or Clear formatting has no effect. Tested in Chrome, Firefox 11, IE9, and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1334532660,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-klisuk3f7xmyrpypvmbw,task_description,resolved
+VisualEditor: All annotations are broken,Fixed in new version.,1340403982,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-klisuk3f7xmyrpypvmbw,task_subcomment,NA
+VisualEditor: All annotations are broken,Mass-moving items into VisualEditor product,1340402751,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-klisuk3f7xmyrpypvmbw,task_subcomment,NA
+VisualEditor: All annotations are broken,"(In reply to comment #0)
+> Editing annotations is broken in VisualEditor. Selecting some text and then
+> clicking either Bold, Italics, Link, or Clear formatting has no effect. Tested
+> in Chrome, Firefox 11, IE9, and Safari.
+
+What do you mean by annotations? I'm confused.",1340396215,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-klisuk3f7xmyrpypvmbw,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","Accessing http://www.mediawiki.org/ as a logged-in user with Konqueror 4.8.1, every page pops up a JavaScript alert: ""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1334440320,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-d5x4qtlwe24swelvcnf7,task_description,resolved
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""",777preethi: Please see https://www.mediawiki.org/wiki/How_to_report_a_bug and create a new ticket with sufficient information to reproduce your setup. Thank you in advance!,1391610944,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","**777preethi** wrote:
+
+This error is coming on some clicks.
+
+**Attached**: {F9202}",1391598197,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","This seems to have been fixed at least on mediawiki.org as messages appear no more.
+
+> [...]
+>   I understand that the purpose of the ResourceLoader effort was to minimize
+> JavaScript loading and execution; the running of the Visual Editor's code on a
+> normal page view would suggest that something's amiss here.
+
+I assume this has either been dealt with or is not important.",1353558325,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","(In reply to comment #13)
+> The problem is that KHTML's Range implementation is missing some constants
+> (required by DOM Level 2 Range spec) that Rangy expects. I've relaxed the
+> relevant tests in Rangy for the upcoming version 1.3 to work around this. [...]
+
+I've read and appreciate it; I just wanted to answer Roan's questions.
+
+  I understand that the purpose of the ResourceLoader effort was to minimize JavaScript loading and execution; the running of the Visual Editor's code on a normal page view would suggest that something's amiss here.",1347628110,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","**timdown** wrote:
+
+Tim,
+
+The problem is that KHTML's Range implementation is missing some constants (required by DOM Level 2 Range spec) that Rangy expects. I've relaxed the relevant tests in Rangy for the upcoming version 1.3 to work around this. See 
+
+https://code.google.com/p/rangy/issues/detail?id=113
+
+I created a bug on the KHTML bug tracker (https://bugs.kde.org/show_bug.cgi?id=301871) but since it has been so far ignored, the best solution is for MediaWiki to use a newer version of Rangy. I would be happy to do a new 1.2 release with this fix while 1.3 is still in alpha.",1347528439,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","(In reply to comment #10)
+> The only code I see adding Rangy to the page is in
+> SpecialVisualEditorSandbox.php, and that code is only run on, you guessed it,
+> Special:VisualEditorSandbox.
+
+> Given that this only happens when logged in, do you have a user script or
+> gadget enabled that uses rangy maybe?
+
+I don't have any user scripts on mediawiki.org; the gadgets section of the preferences list as enabled:
+
+- Edittools
+- WMF Project Status Helper
+- <gadget-enwp-boxes>
+
+Disabling all of them doesn't get rid of the Rangy message.",1347483158,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","**timdown** wrote:
+
+Roan: There are a couple of Chrome plugins I've heard of that use Rangy, so it's possible.
+
+Regardless of the specifics of this bug for MediaWiki, it's a general problem for Rangy. A minor oversight in KHTML's Range implementation is responsible for the error message, so I will be fixing Rangy to be less pedantic. The bug is here:
+
+https://code.google.com/p/rangy/issues/detail?id=113",1339631061,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","The only code I see adding Rangy to the page is in SpecialVisualEditorSandbox.php, and that code is only run on, you guessed it, Special:VisualEditorSandbox.
+
+Given that this only happens when logged in, do you have a user script or gadget enabled that uses rangy maybe?",1339609166,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","**timdown** wrote:
+
+Rangy's author here.
+
+This could be a Rangy bug, or at least something Rangy can address. Rangy checks for the existence of all of the standard DOM Level 2 Range methods to determine whether Range is properly supported by the browser so it's possible KHTML is missing one or more of those.
+
+I'll look into it.",1339607862,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""",Did you quit and start a new instance of Konqueror after changing the setting?,1334456407,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","It's set at ""WebKit"" by default for me.
+
+No visible error messages if I switch to ""KHTML"", either on http://www.mediawiki.org (logged in) or http://translatewiki.net (logged out).",1334452311,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","What's your engine set to?  With ""WebKit"" I see no problems as well, they occur with ""KHTML"" (the default setting).",1334451827,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","Konqueror 4.8.2 ""release 491"" on same VM .... also no problems visible at http://www.mediawiki.org/ when logged in.",1334449628,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","Tested Konqueror 4.7.2 ""release 5"" (openSUSE 12.1), no problems on home page (or even on Special:VisualEditorSandbox). Trying an update to KDE 4.8...",1334446321,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","(In reply to comment #1)
+> Does it also happen on test2 (Also 1.20wmf1) or any other projects?
+
+Not on test2.wikipedia.org, but on translatewiki.net (as an anonymous user).
+
+(In reply to comment #2)
+> Only extension I can find using the 'rangy' library is VisualEditor, which
+> shouldn't be loading anything on the home page...
+
+It occurs already on the Special:UserLogin ""Login successful"" page (""Anmeldung erfolgreich"").",1334445982,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","Only extension I can find using the 'rangy' library is VisualEditor, which shouldn't be loading anything on the home page...",1334442862,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""",Does it also happen on test2 (Also 1.20wmf1) or any other projects?,1334440806,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","In pages such as Special:LonelyPages I would love to have an easy to access form which allowed filtering by namespace (à la Special:Allpages). Since MW 1.18, all $wgContentNamespaces are included in the default listing, but I think it would be nice to have some extra filtering.
+
+I've played a bit, by adding a $namespace parameter extracted from $wgRequest->getInt( 'namespace' ), but I would need some guiding about reusing it in more Special pages (for instance, also in WantedPages) and prepare a patch if this enhancement is considered interesting enough.
+
+= Additional context
+Spun out of T170687:
+
+It would be useful on many of the pages listed above in T170687#3439746
+
+E.g. 
+Special:ShortPages and Special:DeadendPages could then be used with the Help: and Project: namespace to find things to cleanup or merge
+Special:LongPages could then be used with the usertalk namespace to find people to nag to archive their overwhelming talkpages.
+Special:AncientPages could then be used with the Help: and Mediawiki: namespace to find things to update or reconsider the defaults.
+
+Note: Special:Random already has this functionality, similar to solution (f) but using full namespace names, per mw:Help:Random_page e.g. full list at https://en.wikipedia.org/wiki/Wikipedia:Random
+
+= Unknowns
+[] Some design for how the filters should look. Tabs? A search form? A drop down? Is this covered in the UI standards spec?
+[] More input
+
+",1333731000,PHID-USER-af2fdb5prucep2ihmjqc,PHID-TASK-3yeacms7h4ndqwnaljiw,task_description,open
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","> Some design for how the filters should look. Tabs? A search form? A drop down? Is this covered in the UI standards spec?
+
+
+I've seen two different kinds of namespace filters on special pages:
+1. In `Special:Contributions` and some other pages there's a dropdown that allows you to choose just one:
+{F58011403}
+2. In `Special:Search` there's a dropdown that allows you to choose more namespaces:
+{F58011430}
+
+So the second have more options but I'm not sure are they needed here. And most other special pages have the first dropdown.",1734098960,PHID-USER-eqjbrvz42r7foicyocxh,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)",Is this supposed to be tagged Code-Stewardship-Review? Seems more like a feature request to me. If you disagree feel free to re-tag.,1685990607,PHID-USER-qydb7ytmqqctg7dn7fqa,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","For everyone's info, currently no #code-stewardship-reviews are taking place as there is no clear path forward and as this is not prioritized work.
+(Entirely personal opinion: I also assume lack of decision authority due to WMF not having a CTO currently. However, //discussing// this is off-topic for this task.)",1651563672,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","Removing task assignee due to inactivity, as this open task has been assigned for more than two years. See the email sent to the task assignee on February 06th 2022 (and `T295729`).
+
+Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome.
+
+If this task has been resolved in the meantime, or should not be worked on (""declined""), please update its task status via ""Add Action… 🡒 Change Status"".
+
+Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator.",1647201313,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","Another page where this will be very useful is MostTranscludedPages. The templates that are used on articles, user pages, talk pages, and category pages are quite different, and it would be useful to know what are the most used templates in each namespace.",1567917425,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","Change 522602 had a related patch set uploaded (by DannyS712; owner: DannyS712):
+[mediawiki/core@master] Add namespace filter to Special:WantedPages
+
+[[https://gerrit.wikimedia.org/r/522602]]",1563034515,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","There is similar code in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/SpecialNewpages.php | SpecialNewpages.php ]] that allows filtering that by namespace (see `parseParams`, `formDescriptor`, and the logic in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/pagers/NewPagesPager.php | the pager ]]. I think the use of a drop-down menu to select the namespace would be best, given that it is already in use elsewhere. I'll try to add a filter for Special:WantedPages, and if that works add it to the others.",1563034482,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","There is similar code in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/SpecialNewpages.php | SpecialNewpages.php ]] that allows filtering that by namespace (see `parseParams`, `formDescriptor`, and the logic in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/pagers/NewPagesPager.php | the pager ]]. I think the use of a drop-down menu to select the namespace would be best, given that it is already in use elsewhere.",1563025900,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","There is similar code in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/SpecialNewpages.php | SpecialNewpages.php ]] that allows filtering that by namespace (see `parseParams`, `formDescriptor`, and the logic in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/pagers/NewPagesPager.php | the pager ]]",1563025804,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)",There is similar code in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/SpecialNewpages.php | SpecialNewpages.php ]] that allows filtering that.,1563025495,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","Support for this feature request. It came up in the Dutch Wikipedia Village Pump as request a few days ago. A big help would already be to differentiate between Content namespaces (Main, List, etc) and All namespaces. ",1531157783,PHID-USER-bdyms27sdtgdvjm7zfz4,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)",This doesn't seem to be related to VisualEditor.,1503062038,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","(In reply to comment #0)
+> I've played a bit, by adding a $namespace parameter extracted from
+> $wgRequest->getInt( 'namespace' ), but I would need some guiding about
+> reusing
+> it in more Special pages (for instance, also in WantedPages) and prepare a
+> patch if this enhancement is considered interesting enough.
+
+I'd recommend to write a basic initial patch and iterate from there on.
+You are very welcome to use Developer access
+  https://www.mediawiki.org/wiki/Developer_access
+to submit a patch as a Git branch directly into Gerrit:
+  https://www.mediawiki.org/wiki/Git/Tutorial",1363962077,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+VisualEditor: behavior switches are saved in parser environment,"parser patch to stub signature wikitext
+
+Just learning about the parser--these patches will match the __NOTOC__ etc. layout behavior switch keywords, and signature and timestamp strings.
+
+I'm not so confident about my decisions where to put these grammars.
+
+The behavior switch keywords should probably turn into tokens which send control commands to set state in the sync23 stage.
+
+The signature doesn't have access to the current username.  The timestamp has no locale or user timezone functionality.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F8819}",1332357960,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_description,declined
+VisualEditor: behavior switches are saved in parser environment,Seems to be a NOTDONE given Adam's comment. :-),1340403756,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_subcomment,NA
+VisualEditor: behavior switches are saved in parser environment,Mass-moving items into VisualEditor product,1340402741,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_subcomment,NA
+VisualEditor: behavior switches are saved in parser environment,"Patches have been deprecated in favor of https://gerrit.wikimedia.org/r/4050
+
+I've abandoned the signature/timestamp patch, agreeing with Brion that,
+> These sorts of things really should be happening *in* the editor, rather
+> than in the parser. We only have to put ~~~~ in because the original editor
+> was too primitive to have a nice ""insert signature"" live function. So I
+> think it's worth really rethinking how these things get done for the new
+> paradigm. :)",1333247667,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_subcomment,NA
+VisualEditor: behavior switches are saved in parser environment,"Created attachment 10309
+parser grammar stub for behavior switch magic words
+
+**Attached**: {F8820}",1332358043,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_subcomment,NA
+VisualEditor: wrap parser output callback,"patch
+
+Totally trivial static function to abstract out __parseArgs[2] and explain.  It's possible that we want the flush() functionality to work differently in the future.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9217}",1332324900,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-nww4b27vuz6kurpzyhrl,task_description,resolved
+VisualEditor: wrap parser output callback,Mass-moving bugs into the new 'Parsoid' product.,1344281137,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,"Fixed in commit 1736e52bfb6c6b459b571cd8a8f26c7ee6d84da7. Thanks for your patch, Adam!",1341045649,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,"Just noticed that this was assigned to my old (now reactivated with wikimedia address) bugzilla account.
+
+It is still current, and still relates to VE since Parsoid is currently treated as a submodule of VE in Bugzilla. We should perhaps create a separate product for it so that we can set up our own set of default assignees etc.",1340476773,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,Gabriel - this still current?,1340403701,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,Mass-moving items into VisualEditor product,1340402719,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,What's the status of this bug? And does it actually relate to the VisualEditor extension?,1340395142,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,"**sumanah** wrote:
+
+By the way, Adam, you can get a Gerrit account if you want and suggest changes to be merged directly into our Git repository: https://www.mediawiki.org/wiki/Project:Labsconsole_account & https://www.mediawiki.org/wiki/Git/Workflow#Easier_submission_of_code have more information.",1332385352,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,"**sumanah** wrote:
+
+Thanks for the patch! Added keywords to ask for code review.",1332355998,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"WikiEditor toolbar icons are low-resolution raster images, and appear visibly pixelated on a high-resolution display such as iPad third-gen or when zoomed in.
+
+Recommend using SVG images with PNG fallbacks.
+
+Note that currently many of these images are sprited and may need to be re-separated and re-drawn.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1332199740,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_description,resolved
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 220344 abandoned by Jforrester:
+WikiEditor: Add svg images
+
+Reason:
+No reason to back-port.
+
+[[https://gerrit.wikimedia.org/r/220344]]",1435171591,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 220344 had a related patch set uploaded (by Paladox):
+WikiEditor: Add svg images
+
+[[https://gerrit.wikimedia.org/r/220344]]
+",1435099603,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"* https://gerrit.wikimedia.org/r/181786 (branch master): #mw1.26wmf12
+* https://gerrit.wikimedia.org/r/195529 (branch master): #mw1.26wmf12
+",1435093227,PHID-USER-n4kveqwjjlpsb6ydn73h,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 195529 merged by jenkins-bot:
+Add svg to LESS file
+
+[[https://gerrit.wikimedia.org/r/195529]]",1435092277,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181786 merged by jenkins-bot:
+WikiEditor: Add svg images
+
+[[https://gerrit.wikimedia.org/r/181786]]",1435092121,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,i have uploaded patch that moves the signature button down slightly please could you check it. and if you want the italic i changed a bit could i have some help to do that please.,1435067254,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I think the italic I was done like that on purpose.,1435066791,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Maybe I could do something with css for the signature since that is a new updated version of previous with details of who created in the patch at gerrit.
+
+But not sure about italic might need help on that one please.",1435012063,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi how can I fix it. I am using the original version but removed the shadow.,1435011419,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"I can be OK with this version.
+I have a slight concern about the outline of the italic I, and the signature button seems to be aligned a bit 'high'.
+
+{F182267}",1435009644,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Ok so I should disable enhanced dialogs to test to see if it still works.,1434913288,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"I just visited  http://en.random-wikisaur.tk/index.php?title=Main_Page&action=edit  with Win8.1/IE 11 and saw no ill-effects when zooming either. Some of the plain-text based icons still seem a little ""dull"" to me but so are the .png variants; not a reason to disqualify merging imho though.
+{F181822}
+'Enhanced dialogs' are enabled for guests it seems so it might be best to verify everything is OK without the dialogs enabled and just straight WikiEditor as well.
+
+Remember: A picture is worth a thousand words; especially if as many icons are displayed as possible (i.e. tick the 'Advanced' menu open like I did in my screen-grab)",1434911560,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Here is a screenshot showing it works now.
+
+Zoomed in at 110%.
+
+{F181806}",1434909052,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Yes it is fixed. I inserted the code to fix chrome issue I also tested it in ie to check if it affected the way it shows but doesent.,1434908363,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#399524, @TheDJ wrote:
+> Created attachment 16901
+> Alignment trouble
+> 
+> Well I should be able to see that it works in all situation, not just in yours, and as this screenshot of a zoomed Chrome shows, it simply still doesn't work... unfortunately.
+> 
+> **Attached**: {F9095}
+
+@TheDJ - assuming the modifications mentioned in...
+
+>>! In T37342#1228421, @Paladox wrote:
+> Hi I fonund a fix to chrome zooming out problem. we should use preserveAspectRatio=""none"" and xml:space=""preserve"" in button-sprite.svg file.
+
+>>! In T37342#1228470, @Paladox wrote:
+> Found the fix at http://yootheme.com/support/question/6801?order=modified
+
+... have been applied to the latest rebase, could you please see if the Chrome~Zoom issue has been resolved?
+Getting these .svg images up & working is the first step on the path to mirroring VE's scheme (FontAwesome-ish). Thanks
+",1434906902,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Found the fix at http://yootheme.com/support/question/6801?order=modified,1429726756,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Hi I fonund a fix to chrome zooming out problem. we should use preserveAspectRatio=""none"" and xml:space=""preserve"" in button-sprite.svg file.",1429726484,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,,1429301559,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,,1429301541,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,https://code.google.com/p/chromium/issues/detail?can=8&start=0&num=100&q=&colspec=ID%20Pri%20M%20Week%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=&id=458307,1427631594,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181788 abandoned by Paladox:
+Adds svg to css file
+
+Reason:
+Moved to https://gerrit.wikimedia.org/r/#/c/195529/8 since less has been merged.
+
+[[https://gerrit.wikimedia.org/r/181788]]",1425984241,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 195529 had a related patch set uploaded (by Paladox):
+Add svg to LESS file
+
+[[https://gerrit.wikimedia.org/r/195529]]
+",1425982208,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Thankyou. your really good at it.,1424895262,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1056482, @Paladox wrote:
+> Hi could you please do what you did with the image...
+Here is the icon without mask but same effect (+ some minor improvements).
+{F44927}",1424559619,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1056482, @Paladox wrote:
+> Hi could you please do what you did with the image...
+Here is the icon without mask but same effect.
+{F44922}
+",1424559306,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Thanks.,1424522731,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi could you please do what you did with the image your uploaded and do it to this one https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FWikiEditor/1eaf5e8463ae5a95c7a7939d8f3f894b1283742f/modules%2Fimages%2Ftoolbar%2Finsert-ilink.svg this is an old link and this is the current link https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FWikiEditor/c12f248eaa673b1419bd20c77a59ddc0c5bba07f/modules%2Fimages%2Ftoolbar%2Finsert-ilink.svg the old one uses mask the current link doesent please could you get the new link to look like old link without having to use mask.,1424522723,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Thank you for doing that. It is that another image had to have mask removed because it was not showing in internet explorer. but thanks for upload an updated image without mask.,1424484649,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+>> Hi internet explorer does not support mask. please could you do the image without having to do mask thanks.
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask, and bit other improvements). Thanks for promptly take.",1424481747,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask, and bit other improvements). Thanks for promptly take.",1424481721,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask). Thanks for promptly take.",1424481633,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask). Thanks for take.",1424481585,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask)",1424481557,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I have added the new image to the patch I have also updated the png version.,1424451742,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi internet explorer does not support mask. please could you do the image without having to do mask thanks.,1424442765,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Thanks will add it soon to the patch.,1424370183,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"On request I've created an new signature icon:
+* [[ http://commons.wikimedia.org/wiki/File:Insert-signature2.svg | File:Insert-signature2.svg ]]
+
+Because the current icon shows something like ""**f**alse"" or in German ""**f**alsch""/""fehlerhaft""",1424365201,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,The patch is ready to be merged with the svg and then we can merge the file that includes the svg line in css later.,1423781775,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have reported the bug at webkit for svg not being able to zoom out correctly on chrome. The bug is at https://bugs.webkit.org/show_bug.cgi?id=141535,1423779296,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181786 had a related patch set uploaded (by Paladox):
+Re add svg images
+
+[[https://gerrit.wikimedia.org/r/181786]]
+
+#patch-for-review",1422229973,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have uploaded the new image.,1422229917,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I am using my laptop screen on tv so I can upload the image now which I will be doing.,1422227559,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Ok should I use this one. Sorry I missed this reply. I will upload when I can. Laptop broke last week so have to wait for it be repaired before using git to upload.,1422205535,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Paladox
+
+I don't know what the big deal was. I commented out the `<mask>` section using a text editor and the basic icon reappeared when I opened it again. Now I don't know if that means it still needs a //mask// or not  -- can't say I didn't corrupt the file further either. 
+
+{F26805}
+
+The only thing I'm sure is that I can see it now in IE... and I bet that's better than knowing there is a button on your toolbar but the lack of even a crippled button-icon means you have no clue what it does until you tick on it. (NOT optimal).
+
+So use it if we can, fix it if we must... but at least swap out the one rendering ''blank'' for something that everybody can at least see. ",1420619890,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Paladox
+
+I don't know what the big deal was. I commented out the Mark section using a text editor and the basic icon reappeared when I opened it again. Now I don't know if that means it still needs a //mask// or not  -- can't say I didn't corrupt the file further either. 
+
+{F26805}
+
+The only thing I'm sure is that I can see it now in IE... and I bet that's better than knowing there is a button on your toolbar but the lack of even a crippled button-icon means you have no clue what it does until you tick on it. (NOT optimal).
+
+So use it if we can, fix it if we must... but at least swap out the one rendering ''blank'' for something that everybody can at least see. ",1420619856,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Paladox
+
+I don't know what the big deal was. I commented out the Mark section using a text editor and the basic icon reappeared when I opened it again. Now I don't know if that means it still needs a //mask// or not  -- can't say I didn't corrupt the file further either. 
+
+{F26805}
+
+The only thing I'm sure is that I can see it now in IE... and I bet that's better than knowing there is a button on your toolbar but the lack of even a crippled button-icon means you have no clue what it does until you tick on it. (NOT optimal).
+
+So use it if we can, fix it if we must... but at least swap out the one rendering ''blank'' for something that everybody at see. ",1420619808,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Jdforrester-WMF said:
+>At the request of Design I'm (very slowly) working on replacing all the assets with copies of the OOjs UI ones (in advance of actually switch WikiEditor over to using that, which is lower priority). Maybe we should merge these efforts?
+
+If it gets mobile, tablet and similar device user's the same intended results //A//nd within a reasonable amount of time, then I'm all for it. The current ''bundle'' of .png-matching .svg files are just not making the cut. I suspect the amount of turnover week in, week out has jaded many beyond the point of no return by now as well.
+
+Still, I'd hate to wait another 3 or 4 months for something that could be applied today in full & in the interim; where individual, problematic .svg based icons are disabled by pointing them either to the equivalent .svg stand alone image file or the alleged fallback, stand alone png  as the issues at hand should dictate.",1420567662,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi the image insert-ilink.svg and the same image but in button-sprite.svg seems to not show in certain browsers the problem is with using mask. It works in chrome but in Internet explorer it does not show this I doint know how to fix this problem.,1420554603,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#945952, @Paladox wrote:
+> I can confirm that problem is because of multiple images inside one image file. I tested it.
+
+Are you saying its because WikiEditor first looks to use ''Spirited'' button icons from //button-sprite.svg// using offset coordinates instead of individual icons?
+
+If so, I wonder why it does not happen using //button-sprite.png// (or does it but nobody bothered to try?)",1419888506,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I can confirm that problem is because of multiple images inside one image file. I tested it.,1419776339,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi here is the bug filed https://bugs.webkit.org/show_bug.cgi?id=125118 and https://code.google.com/p/chromium/issues/detail?id=260319 it seems the bug is when the image has multiple images in it.,1419774614,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi if you zoom out to 50% it lines up again. seems to either been a problem with the css or it is webkit or chrome.,1419774170,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"I think it is to do with this file jquery.wikiEditor.toolbar.config.js
+
+and how do you add something like 2px -142px center to background-position because it seems if I add 2px center the icon goes back to the position you want it to be but it is a different icon.",1419772581,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Oh ok.,1419767078,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#945594, @Paladox wrote:
+> probably the file button-sprite.png and .svg need to be separated into different images to fix the issue on google chrome (guessing)
+
+It could just be an overlooked css attribute and setting like the one that fixes T78354 for example. We won't know until folks have something to test against.",1419727208,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,probably the file button-sprite.png and .svg need to be sepereted into different images to fix the issue on google chrome (guessing),1419726053,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi but there is an error with chrome where if you zoom out pass 90% or lower it will make the icons go out of position. how will that get fixed but any ways chrome default zoom is 100% and not a lot of people use 90% zoom (guess) so this svg images that are being added could get merged and the problem fixed letter including the .css or .less file.,1419723973,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943845, @Paladox wrote:
+> There is also a bug with having svg images because if your on chrome and 90% zoomed in the icons go everywhere.
+
+Every example screenshot that I've seen is not the default WikiEditor toolbar but always with additional buttons, etc. added afterwards. I'd like to see an unmodified WikiEditor toolbar behave that way just to be sure.
+
+Scratch that I just saw https://phabricator.wikimedia.org/T37342#399524
+
+seems like problem with the spirited coordinates not re-sizing on such actions as a zoom. ",1419518358,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943845, @Paladox wrote:
+> There is also a bug with having svg images because if your on chrome and 90% zoomed in the icons go everywhere.
+
+Every example screenshot that I've seen is not the default WikiEditor toolbar but always with additional buttons, etc. added afterwards. I'd like to see an unmodified WikiEditor toolbar behave that way just to be sure.",1419517812,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi the problem started when someone created the images earlier this year. The problem was the reported.,1419517258,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943844, @Paladox wrote:
+> Do you have the link for svg version of format-olist.svg 
+
+It was part of one your patchsets - https://gerrit.wikimedia.org/r/151203",1419517097,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,There is also a bug with having svg images because if your on chrome and 90% zoomed in the icons go everywhere.,1419517000,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Do you have the link for svg version of format-olist.svg ,1419516963,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943824, @GOIII wrote:
+> ...but if the svg file variants for all the existing png files are missing some, I doubt anybody would want to merge that so there's the first roadblock
+> 
+Then again, the whole point of keeping/having the png files is for a fallback if svg somehow fails so I take it back -- no reason not to vote merge
+",1419515856,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"r151203 had at least `format-olist.svg` listed in it
+
+...but if the svg file variants for all the existing png files are missing some, I doubt anybody would want to merge that so there's the first roadblock
+
+I wish we could slow down some and address one thing at a time - we're already 9 patch-sets deep for example and the css could have taken some cleaning/amending first too.",1419514974,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi they doint currently have svg images but can be added later.,1419514374,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 abandoned by Paladox:
+WikiEditor: Convert .css to .less and also fixes SVG issues.
+
+Reason:
+Split this into two patches first patch is svg images https://gerrit.wikimedia.org/r/#/c/181786/ second patch is convert .css to .less https://gerrit.wikimedia.org/r/#/c/181790/
+
+[[https://gerrit.wikimedia.org/r/151203]]",1419514192,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have this patch now https://gerrit.wikimedia.org/r/#/c/181790/ that converts .css to .less,1419514115,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"See, this is partly why the previous patches were so hard to follow. With the revised 1st patch just being the addition of the svg variants, the following .png files have no corresponding .svg file in the new patch
+
+* format-bold-L.png
+* format-bold-hy.png
+* format-bold-ka.png
+* format-bold-os.png
+* format-bold-ru.png
+
+* format-italic-D.png
+* format-italic-E.png
+* format-italic-hy.png
+* format-italic-ka.png
+
+* format-olist-rtl.png
+* format-olist.png
+* format-ulist-rtl.png
+
+* insert-redirect-rtl.png
+
+* magnify-clip.png
+",1419514417,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"See, this is partly why the previous patches were so hard to follow. With the revised 1st patch just being the addition of the svg variants, the following .png files have no corresponding .svg file in the new patch
+
+* format-bold-L.png
+* format-bold-hy.png
+* format-bold-ka.png
+* format-bold-os.png
+* format-bold-ru.png
+
+* format-italic-D.png
+* format-italic-E.png
+* <s>format-italic-I.png (see previous comment above)</s>
+* format-italic-hy.png
+* format-italic-ka.png
+
+* format-olist-rtl.png
+* format-olist.png
+* format-ulist-rtl.png
+
+* insert-redirect-rtl.png
+
+* magnify-clip.png
+",1419514384,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"See, this is partly why the previous patches were so hard to follow. With the revised 1st patch just being the addition of the svg variants, the following .png files have no corresponding .svg file in the new patch
+
+* format-bold-L.png
+* format-bold-hy.png
+* format-bold-ka.png
+* format-bold-os.png
+* format-bold-ru.png
+
+* format-italic-D.png
+* format-italic-E.png
+* format-italic-I.png (see previous comment above)
+* format-italic-hy.png
+* format-italic-ka.png
+
+* format-olist-rtl.png
+* format-olist.png
+* format-ulist-rtl.png
+
+* insert-redirect-rtl.png
+
+* magnify-clip.png
+",1419513951,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have managed to do it.,1419513641,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Please could I have some help to rename it because I try it but it stays at lower case I instead of being uppercase i.,1419513287,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181788 had a related patch set uploaded (by Paladox):
+Adds svg to css file
+
+[[https://gerrit.wikimedia.org/r/181788]]
+
+#patch-for-review",1419512878,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181786 had a related patch set uploaded (by Paladox):
+Re add svg images
+
+[[https://gerrit.wikimedia.org/r/181786]]
+
+#patch-for-review",1419512868,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 abandoned by Paladox:
+WikiEditor: Re add SVG
+
+Reason:
+I have added split some of this in to two patches which are at https://gerrit.wikimedia.org/r/#/c/181786/ and https://gerrit.wikimedia.org/r/#/c/181788/
+
+[[https://gerrit.wikimedia.org/r/151611]]",1419512850,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"shouldn't `format-italic-i.svg` be `format-italic-I.svg` ? (capital i =I [eye] )
+
+the existing png I think its suppose to replace is `format-italic-I.png`",1419512845,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Css file containing svg.
+
+https://gerrit.wikimedia.org/r/#/c/181788/",1419511603,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Always abandon AFTER you have replacements up no?
+
+
+>>! In T37342#943714, @Paladox wrote:
+> So I should add svg images and if I have any png files I should add them and I should not edit the css files on first patch but add the svg image to css on the second patch and then last patch change css to less.
+
+
+Right, the first step should just be to add the final desired svg variants and/or any final desired png - be they replacements or previously missing",1419510935,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi this is the first patch https://gerrit.wikimedia.org/r/#/c/181786/ is this what you ment for first patch.,1419510842,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I will abandon them patches in a min. I will upload the new patches to make sure they are what your saying to do. thanks for helping.,1419510301,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,So I should add svg images and if I have any png files I should add them and I should not edit the css files on first patch but add the svg image to css on the second patch and then last patch change css to less.,1419509992,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Ok.,1419509863,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943701, @Paladox wrote:
+> So I should do the svg images first. and then css to less last.
+Patch No.
+# add all the final svg variants and any additional final png files to the ...images/toolbar directory
+     * nothing should change the current rendering by only adding image files here
+# edit the current css to use the svg variants and have the png variants as the fall backs
+     * we can stop here to see if anybody has svg rendering issues or not. If not...
+# convert the svg rich css files to use the less format
+     * we then see if anything has changed from the rendering seen in #2
+
+Well that's what I //think// is the best way for folks to pay attention to this again while addressing previously voiced concerns/issues. I could very well be 100% wrong mind you.",1419510822,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943701, @Paladox wrote:
+> So I should do the svg images first. and then css to less last.
+Patch No.
+# add the svg variants and any additional png files to the ...images/toolbar directory
+     * nothing should change the current rendering here
+# edit the current css to use the svg variants and have the png variants as the fall backs
+     * we can stop here to see if anybody has svg rendering issues or not. If not...
+# convert the svg rich css files to use the less format
+     * we then see if anything has changed from the rendering seen in #2
+
+Well that's what I //think// is the best way for folks to pay attention to this again while addressing previously voiced concerns/issues. I could very well be 100% wrong mind you.",1419509898,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943701, @Paladox wrote:
+> So I should do the svg images first. and then css to less last.
+Patch No.
+# add the svg variants and and any additional png files to the ...images/toolbar directory
+     * nothing should change the current rendering here
+# edit the current css to use the svg variants and have the png variants as the fall backs
+     * we can stop here to see if anybody has svg rendering issues or not. If not...
+# convert the svg rich css files to use the less format
+     * we then see if anything has changed from the rendering seen in #2
+
+Well that's what I //think// is the best way for folks to pay attention to this again while addressing previously voiced concerns/issues. I could very well be 100% wrong mind you.",1419509828,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Patch No.
+# add the svg variants and and any additional png files to the ...images/toolbar directory
+     * nothing should change the current rendering here
+# edit the current css to use the svg variants and have the png variants as the fall backs
+     * we can stop here to see if anybody has svg rendering issues or not. If not...
+# convert the svg rich css files to use the less format
+     * we then see if anything has changed from the rendering seen in #2
+
+Well that's what I //think// is the best way for folks to pay attention to this again while addressing previously voiced concerns/issues. I could very well be 100% wrong mind you.",1419509785,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I will create the first patch with the new svg images excluding the arrow image. and second will include css to less arrow svg images and the new svg images from first reason because if first patch gets merged then this patch could get rebased without needing to add anything else.,1419509681,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,So I should do the svg images first. and then css to less last.,1419509304,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi the reason I created three patches is because someone asked me to create separate patches and then someone asked me to put the patch into one. so I created three patches. should I create two one with the convert to .less and with the svg images of arrow and then the other svg images in different patch with the fix for the background.,1419509255,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,On second thought - maybe css to less conversion should be the last patch merged after all the other pieces are in place rather than the first patch.,1419509127,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"basically yes -- although I suspect you would do better by taking the existing three and separating the changes even further into even more specific patches. Again, this is just from an observational standpoint rather a technical one. Nevertheless, these enhancements seem to be pretty much ignored no matter how one looks at them.
+
+Maybe the first step should be a conversion of the existing .css into less format prior to the svg icons addition/modifications for example. Then add the svg variants in another patch - the changes needed to make them live in the now existing less files in still another patch. And so on....",1419508909,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi so should I abandon them and then re upload them.,1419504455,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"> [[https://gerrit.wikimedia.org/r/151611]]
+> 
+> [[https://gerrit.wikimedia.org/r/151616]]
+> 
+> [[https://gerrit.wikimedia.org/r/151203]]
+> 
+These 3 patches have been re-committed for weeks and weeks now to no avail. Nobody, including myself, seems to be comfortable with supporting a merge for revisions that have three-dozen or more Patch-sets in place to date -- not to mention each patch is trying to accomplish more than it should or overlaps into another's all at once.
+
+It seems to me the best way to get the underlying changes merged is to abandon these three and create new ones that accomplishes the same end results but with smaller steps to reach that aim instead.",1419474773,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded (by Paladox):
+WikiEditor: Re add SVG
+
+[[https://gerrit.wikimedia.org/r/151611]]
+
+#patch-for-review",1417643642,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded (by Paladox):
+WikiEditor: Convert .css to .less and also fixes SVG issues.
+
+[[https://gerrit.wikimedia.org/r/151203]]
+
+#patch-for-review",1417122920,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded (by Paladox):
+WikiEditor: Re add SVG
+
+[[https://gerrit.wikimedia.org/r/151611]]
+
+#patch-for-review",1417122843,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded by Paladox:
+WikiEditor: Re add SVG
+
+https://gerrit.wikimedia.org/r/151611",1416224701,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded by Paladox:
+WikiEditor: Fix issue with SVG
+
+https://gerrit.wikimedia.org/r/151611",1415219504,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Based on talking to James and Trevor, we can provide the icons that will improve consistency dramatically, we're targeting end of day tomorrow Nov 5 to have all the assets ready to integrate. Thanks for a moment of patience.",1415149663,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to Jared Zimmerman (WMF) from comment #66)
+> No, i just mean the same SVG assets. for bold, italic, image, link, etc. Not
+> the code behind an OOUI control
+
+That's fundamentally incompatible with how MediaWiki is built. Reaching in to the code base to pull out assets will immediately fail basic code review.",1415146038,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"No, i just mean the same SVG assets. for bold, italic, image, link, etc. Not the code behind an OOUI control",1415145973,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Using the OOUI icons means using OOUI. Porting the wikitext editor to OOUI is a big piece of work.,1415145859,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"part of me is still wondering why we aren't using the icons that are in use in VisualEditor currently, any rational?",1415145803,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 168821 merged by jenkins-bot:
+Revert ""Add SVG versions of toolbar icons""
+
+https://gerrit.wikimedia.org/r/168821",1415139693,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have one of the images that were fixed by a user here and fixed the other ones to. the patch is at https://gerrit.wikimedia.org/r/#/c/151611/,1415119144,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Okay, this is getting ridiculous. M4tx made a commit that added SVG files (a low priority enhancement). The commit accidentally mutilated the ""B"" icon (visible regression) and was merged by TheDJ.
+
+See
+https://gerrit.wikimedia.org/r/#/c/97454/
+http://i.imgur.com/mBZm28W.png
+
+
+I don't know what everyone is doing, but please just fix the icon. All this other stuff is unrelated to this bug. If there's no simple commit that fixes the icon soon I'll recommend reverting the SVGs for the time being and re-submitting that change as a draft blocked on restoring the B icon.",1415118989,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,This one only includes the fixes for svg http://simple-random-wikisaur.tk/index.php?title=Main_Page&action=edit,1414326828,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,That site also includes .less.,1414326445,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to Derk-Jan Hartman from comment #55)
+> ""is the way I thought this was all going to play out too."" There are no
+> dependencies on the tickets, there are no comments on the commit message
+> that indicate this.
+> 
+Granted - and you are absolutely correct to take that position imo as well. I merely had the small benefit of following this exercise 20+ revisions ago is all. Don't read into it any further than that.
+
+(In reply to Derk-Jan Hartman from comment #53)
+> 4: It turned out that there were problems with the SVGs in production. This
+> should have been cause for reverting the change.
+
+Bingo. Regression seems to be a dirty word around here however.",1414326005,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 16901
+Alignment trouble
+
+Well I should be able to see that it works in all situation, not just in yours, and as this screenshot of a zoomed Chrome shows, it simply still doesn't work... unfortunately.
+
+**Attached**: {F9095}",1414325710,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I have created 3 commits one has all of it in it and 2nd patch has .less in it and third patch has the fixes for svg.,1414325541,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"""is the way I thought this was all going to play out too."" There are no dependencies on the tickets, there are no comments on the commit message that indicate this.
+
+That first link already mixes three issues in a way that I'm not confident anymore that something unexpected is mixed into it as well.
+
+Separation of concerns (in bugzilla tickets, commit messages etc), be explicit about what depends on what, proof that stuff works (as intended) and you will convince a core reviewer to merge the code. That has not happened so far.",1414325442,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Ok I have tested all the patches on my site. here is link to show how it is working. http://en.random-wikisaur.tk,1414325196,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Paladox, I'm not sure how I need to explain this to you and it hope it doesn't come across as rude, because it's not intended to be that way, but this whole stuff is simply not reviewable right now.
+
+If I go trough a patchset, read the commit message and the diff, test it in my browsers and NOT have all my questions answered. It cannot be merged.
+
+Things I should not have to do are:
+1: Go trough 50 patchset rebases
+2: Go trough 15 comments interspersed with these rebases, for finding answers that should be in the commit message, if they affect the review.
+3: Pick and choose between 3 patchsets, for one change.
+
+
+This Bug ticket is about converting the Original PNGs to SVG.
+1: M4tx did some nice work
+2: This work was not pixel perfect with the original PNGs, but that was fine
+3: I approved the SVG change on that basis
+4: It turned out that there were problems with the SVGs in production. This should have been cause for reverting the change.
+5: Instead of reverting I gave people a chance to fix it, Pro, you etc.
+6: You currently are the one making those proposals for changes.
+7: You can't answer the questions in a way that gives enough people confidence to approve the changes. (either by lack of experience, by lack of your mastery of the language, of not actually being able to prove it all works as expected etc.)
+8: This means the patches cannot be merged, and that means that it's about time to bite the bullet, and I need to admit that I should have reversed the original commit back then when it became clear there were some problems with the original change to SVG.",1414325003,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to paladox2015 from comment #50)
+> Hi i have got it right i have added the images that were here to the patch
+> and also added a note on who created the image i also followed fomafix
+> instructions and so the patch should be correct now.
+
+https://gerrit.wikimedia.org/r/151203
+
+... followed by ...
+
+https://gerrit.wikimedia.org/r/151611
+
+... followed by ...
+
+https://gerrit.wikimedia.org/r/151616
+
+... is the way I thought this was all going to play out too.",1414324893,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 168821 had a related patch set uploaded by TheDJ:
+Revert ""Add SVG versions of toolbar icons""
+
+https://gerrit.wikimedia.org/r/168821",1414323690,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi i have got it right i have added the images that were here to the patch and also added a note on who created the image i also followed fomafix instructions and so the patch should be correct now.,1414323543,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"I can't seem to get a clear, concise and accurate description from the patch submitters on these problems. Problems also remain in the latest versions of the submitted patches with strange offset problems in the sprite when the user zooms in or out.
+
+Since there are clearly problems in the original patch that was converting the toolbar resources to SVG, and since it seems that the patch submitters cannot get them corrected, I think that there is only one solution left. Revert the original SVG patch and wait till someone with SVG skills AND gerrit experience pays attention to this problem.",1414323342,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have now fix it.,1412625240,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have fixed it.,1410782072,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to paladox2015 from comment #42)
+> Merge Failed.
+> This change was unable to be automatically merged with the current state of
+> the repository. Please rebase your change and upload a new patchset.
+
+So please fix that? :)",1410781002,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/151203",1410778589,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 160421 abandoned by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/160421",1410778225,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 160421 had a related patch set uploaded by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/160421",1410778182,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Hi I have now re opended the patch but it says 
+
+Merge Failed.
+
+This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset.",1410730049,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/151203",1410729808,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/151203",1410728915,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 restored by Paladox:
+Update WikiEditor
+
+https://gerrit.wikimedia.org/r/151203",1410728608,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have already done a patch that does that. https://gerrit.wikimedia.org/r/#/c/151203/ Someone commit and said to split them into two patches.,1410727035,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to Bartosz Dziewoński from comment #36)
+> 
+> Can anybody summarize what is going on and what's up with all the various
+> patches and attachments? . . .
+> 
+
+I'll second that!
+
+When it comes to such matters involving images/icons on a toolbar, it seems [to me] the best way to whittle down the issues is to actually have them render in semi-real world instances and have folks report back their findings.
+
+Can't we merge ....
+
+https://gerrit.wikimedia.org/r/151611
+
+and 
+
+https://gerrit.wikimedia.org/r/151616
+
+... so that they at least come up live & working on test2.wikipedia.org in the immediate near future (i.e. today)?
+
+That should get us a decent pool of user responses before next week's scheduled core update to see if those patches resolve anything (or not) bug-wise and still give us enough of a buffer to further refine or revert as needed before that scheduled update rolls-out as well.
+
+The way things stand now, with half a dozen patch sets awaiting attention or implementation for weeks if not months already, we sure don't seem to be resolving much.",1410666732,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"This bug seems to be tracking at least two or maybe three completely distinct issues, one of which has just been reported as bug 70679.
+
+Can anybody summarize what is going on and what's up with all the various patches and attachments? Derk, you're marked as assignee – are you still working on it?",1410455845,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have fixed the problem I also removed the shadow from the rest of the svg icons.,1409906966,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on attachment 15497
+button-sprite.svg fixed
+
+Hi there is a problem with this image I uploaded to gerrit and this is what user krinkle said.
+
+
+format-B is now missing a doctype. And the sprite completely changed. It should probably only have the bold part replaced.
+
+I mean xml header, not doctype.",1409311484,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded by Paladox:
+WikiEditor: Fix issue with SVG
+
+https://gerrit.wikimedia.org/r/151611",1407426536,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 abandoned by Paladox:
+Update WikiEditor
+
+Reason:
+Ok.
+
+Please see Ic0c261f66ee882efeb07ab77ee2a3a5533093c4f for the fix for svg images. and I2a223e202aa488f0e83e663e490ee009da686687 for converting .css to .less.
+
+https://gerrit.wikimedia.org/r/151203",1407168713,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded by Paladox:
+WikiEditor: Fix issue with SVG
+
+https://gerrit.wikimedia.org/r/151611",1407150680,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded by Paladox:
+Update WikiEditor
+
+https://gerrit.wikimedia.org/r/151203",1406927368,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"But for sure, I would upload tomorrow another fixed version, with all group transform attributes removed (W3C valid uncompressed and xml well formed).",1405204063,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Derk-Jan Hartman, yes me too, it is the browser zoom level, but only in Chrome and only sporadically. (If I reset the zoom level, the effect is gone immediately.)
+
+I can't say it is an SVG bug, instead of a Chrome bug with CSS sprite sheets (maybe only with SVG).",1405199463,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@PRO, i'm also seeing what you see in your: ""Screenshot - vector-bar completely disordered""
+
+I'm mostly seeing it if I zoom the page out a bit. Probably has to do with scaling and rounding... ?",1405112728,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Is anyone working on merging PRO's corrected button sprite into code?
+
+I'm also seeing what Krinkle reported before (positioning issues of the shadow of all letters) which is fixed with attachment 15497.
+
+This should be a high priority since it looks pretty broken right now!",1405070793,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@PRO, btw we don't need it to be SVGZ compressed, because that already happens on the fly.
+
+I concur that the gaussian blur is somewhat unusual, and I'm not a big fan of it myself.",1401360541,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Thank you PRO, i'll get on this in the next week.",1401277666,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on attachment 15497
+button-sprite.svg fixed
+
+All GaussianBlur filter are still present although this is very unusual for small icons. I would make a version without GaussianBlur. (File size before 152.841 Bytes after my optimation = 34.961, SVGZ compression = 10.918 Bytes)",1401259506,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"button-sprite.svg fixed
+
+I've optimized the button-sprite and also converted all text to path. Check it out.
+
+**Attached**: {F9094}",1401259124,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on attachment 15466
+Screenshot - vector-bar completely disordered
+
+Now everything is ok again, I've nothing changed.",1400877805,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on attachment 15465
+Letter B fixed
+
+font type to path",1400863912,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Screenshot - vector-bar completely disordered
+
+It appears also if I logged out. Win 7 Chrome 34. Firefox is normal.
+
+**Attached**: {F9093}",1400863853,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Letter B fixed
+
+Font to pfad converted , remove all transform attributes.
+
+**Attached**: {F9092}",1400863295,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 15431
+Zip of icon files
+
+**Attached**: {F9091}",1400417677,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@DJ, the proposed SVG icons were significantly different (bevels, embossing, gradients) which definitely diverge from what we had, I was just saying, if we're diverging from what we had, I'd like to diverge in the right direction, not in the direction of greater ornamentation.",1400172622,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Eh, this is just about the old style icons, we are not talking about replacing them...",1400159859,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I thought there is an Wikimedia icon initiative? I'm interesting to do this like simple in the Tango/GNOME style!? [[File:Gnome-format-text-bold.svg]],1400154692,PHID-USER-qrrijb4p5yfluwirt7lw,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Anything that is already part of wikifont doens't need to be redrawn https://github.com/munmay/WikiFont/blob/master/Screenshot-current.png,1400093115,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Good point, i'll upload them on commons.wm.org",1400075265,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"**anonmoos** wrote:
+
+Re: request for assistance in the Commons Graphics village pump:
+
+It might help if the SVG code in question were available somewhere as an ordinary SVG file, and not only as embedded in some kind of generalized source code patch management database system that not everybody may feel like trying to come to terms with...",1400074767,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I also left a request for assistence in the commons graphics lab. https://commons.wikimedia.org/wiki/Commons:Graphics_village_pump#SVG_improvements_for_MediaWiki_toolbar,1400056565,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on https://gerrit.wikimedia.org/r/97454:
+
+FIXME: The ""B"" button looks broken.
+
+> This change changed the B button to have 3D depth
+> whereas all the others remain flat (the book icon
+> also some depth to it, but not beyond a simple surface,
+> which looks fine). The depth is sufficiently odd that
+> I suspect this was not done on purpose. 
+>
+> Screenshot: http://i.imgur.com/mBZm28W.png
+> (bottom row shows the new SVG versions)
+>
+> It looks like the outline that is making it look
+> 3D is actually just the regular outline, and the
+> black filling for some reason only covers half
+> of the width.",1400005331,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 97454 merged by jenkins-bot:
+Add SVG versions of toolbar icons
+
+https://gerrit.wikimedia.org/r/97454",1399377216,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"DJ, looks ""good enough for now"" I'd like for us to clean this up, and switch to a smaller set of icons that use the new wikifont icons when we can https://www.mediawiki.org/wiki/Design/Wikicons",1398974317,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 15051
+screenshot safari 7
+
+I notice a few small problems the shadow of the chars seems a tad excessive, the red traffic sign around the W is a bit shifted for me (likely Mac Safari specific issues).
+
+**Attached**: {F9090}",1396961743,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Done and commented.,1386183122,PHID-USER-ua75tm4u7cmt4mdof6vb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Pau / Brandon: Could you review the patch (8 lines of CSS and a bunch of new SVG files), or do you have an idea who could?",1386182674,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 13895
+Screenshot of WikiEditor after the patch
+
+**Attached**: {F9089}",1385329916,PHID-USER-myqwv53kwudj34c4zwgl,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 97454 had a related patch set uploaded by M4tx:
+Add SVG versions of toolbar icons
+
+https://gerrit.wikimedia.org/r/97454",1385329638,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 10281
+screenshot of editing on en.wikipedia.org on iPad 3
+
+**Attached**: {F9088}",1332199815,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","* If debug=true, remember in session
+* the ""set debugmode"" code should check session in addition to GET query param
+* going to debug=false will also unset it in the session
+
+Allows to navigate the wiki, submit forms (T37061), and stuff.
+
+To prevent users from unknowingly staying in debug mode, JS should but up an informational notification on the page informing something short like: ""You've enabled debug mode of client resources delivery, click here to disable this""
+",1331206980,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlvuxsstbitv7gqtjze,task_description,open
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode",I propose to resolve this by documenting a one-line snippet that sets the cookie-based debug mode flag for a period of time (e.g. 1 hour).,1701992404,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode",I propose to resolve this by documenting a one-line snippet that sets the cookie-based debug mode flag for a period of time (e.g. 1 hour) and leave it at that.,1664909739,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","Deprioritising until after {T85805}.
+
+Right now debug mode changes execution behaviour in a significant way, and can be very slow for modules with 1000s of class files (such MediaViewer, Wikibase and VisualEditor). I expect T85805 will make debug mode more performant and less intrusive.
+
+After that, I think it would be worth considering to allow developers, WMF staff and other interested tech-savvy users to browse our sites with ""debug mode"" enabled by default. Whether through a beta feature, regular preference, via WikimediaDebug extension, or some other way.",1554174487,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","See also:
+https://github.com/he7d3r/mw-gadget-DebugModeToggle",1416917131,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","(In reply to comment #1)
+> Since setting a cookie ""resourceLoaderDebug"" enables debug mode, this probably
+> can be done easily on client side.
+
+Ah, this is already implemented. I didn't know that. (bug 25610 slipped by silently, and it never made it into documentation).
+
+Repurposing this bug for the GUI module.",1340243946,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","(In reply to comment #1)
+> Since setting a cookie ""resourceLoaderDebug"" enables debug mode, this probably
+> can be done easily on client side.
+
+The cookie can be set on the client side, however the initial server request needs to know this before any client code is processed because it influences how the page is rendered very early on. (one could implement a redirect/refresh, but that gives the same problem with form submissions).
+
+This needs (at least some) server development. But that's OK, it's not a hard thing to do :), just other priorities right now (although patches are welcome at any time :)",1331295470,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","Since setting a cookie ""resourceLoaderDebug"" enables debug mode, this probably can be done easily on client side.",1331283521,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+mergeMessageFileList.php spews undefined notices of some extensions,"mergeMessageFileList.php spews undefined notices of some extensions for usages of DefaultSettings variables in their inclusion script
+
+
+Updating ExtensionMessages-1.19.php...
+Loading data from /home/wikipedia/common/php-1.19/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CongressLookup/CongressLookup.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ContactPage/ContactPage.php
+PHP Notice:  Undefined variable: wgSitename in /home/wikipedia/common/php-1.19/extensions/ContactPage/ContactPage.php on line 44
+
+Notice: Undefined variable: wgSitename in /home/wikipedia/common/php-1.19/extensions/ContactPage/ContactPage.php on line 44
+Loading data from /home/wikipedia/common/php-1.19/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CustomUserSignup/CustomUserSignup.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+PHP Notice:  Undefined variable: wgUseFileCache in /home/wikipedia/common/php-1.19/extensions/FormPreloadPostCache/FormPreloadPostCache.php on line 11
+
+Notice: Undefined variable: wgUseFileCache in /home/wikipedia/common/php-1.19/extensions/FormPreloadPostCache/FormPreloadPostCache.php on line 11
+Loading data from /home/wikipedia/common/php-1.19/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PrefStats/PrefStats.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PrefSwitch/PrefSwitch.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Renameuser/SpecialRenameuser.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php
+PHP Notice:  Undefined variable: wgExtensionAssetsPath in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 27
+
+Notice: Undefined variable: wgExtensionAssetsPath in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 27
+PHP Notice:  Undefined variable: wgLocalDatabases in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 115
+
+Notice: Undefined variable: wgLocalDatabases in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 115
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+--------------------------
+**Version**: 1.19
+**Severity**: trivial",1329340740,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-lsoz6uynuyo3es6wev2y,task_description,declined
+mergeMessageFileList.php spews undefined notices of some extensions,Seems fine now,1343423081,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-lsoz6uynuyo3es6wev2y,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"**Author:** `van.de.bugger`
+
+**Description:**
+I have a form with nested templates:
+
+> {{{info}}}
+> {{{for template|Cache}}}
+> ...Cache fields...
+> {{{field|Locations|holds template}}}
+> {{{end template}}}
+> {{{for template|Cache/Location|multiple|embed in field=Cache[Locations]}}}
+> ...Location fields...
+> {{{end template}}}
+
+Everything works good. Page code looks as expected:
+
+> {{Cache
+> |...Cache fields...
+> |Locations={{Cache/Location|...}}{{Cache/Location|...}}...
+> }}
+
+I have an additional *partial* form:
+
+> {{{info|partial form}}}
+> {{{for template|Cache}}}
+> <!-- No Cache fields, just next one. -->
+> {{{field|Locations|holds template}}}
+> {{{end template}}}
+> {{{for template|Cache/Location}}}
+> ...Location fields...
+> {{{end template}}}
+
+After editing a page with this partial form, all the Location templates *moved* *out* of Cache, while Locations field receives strange value:
+
+> {{Cache
+> |...Cache fields...
+> |Locations=@replace_Cache___Locations@
+> }}
+> {{Cache/Location|...}}{{Cache/Location|...}}...
+
+That's obviously a big. Partial form should not move nested templates out of main template.
+
+However, there is a workaround: removing ""partial form"" specifier from partial form definition. Such a ""non-partial"" form produces correct result, but I am a bit afraid -- formally it is declared as partial form, so it does not have to save non-used fields of main template, does it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1328917020,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_description,declined
+SemanticForms: Partial forms and nested templates.,"Changing status to ""Declined"", since partial forms were removed entirely from Page Forms in version 5.3. Unfortunately, there's no ideal way to edit template calls that are not at the top of the page. Your best bet, if you want to preserve that layout of template calls halfway down the page, might be to use VisualEditor for those instead, with the TemplateData extension.",1682374235,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"I have the exact same problem, nested templates work perfectly well, until I add {{{info|partial form}}} to my form (tested on the latest version of page forms, 5.0.1)
+
+And I don't see any alternative solution to using partial form, when the form should apply to only part of the page content, that can be anywhere inside the page, as Sophivorus mentioned.
+
+Is there any alternative solution to provide the same result?",1609845290,PHID-USER-mot76bxt3c5mvqmzegwu,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"Problem with using pseudo-partial forms is that PageForms moves the template to the top of the page.
+
+I'm using partial forms to provide a user-friendly interface to add metadata to videos embedded through a {{Video}} template. This template has a ""comments"" parameter that should be filled with multiple {{Video comment}} subtemplates, each specifying a video time and corresponding comment. The natural solution would be a partial form with a multiple-instance subtemplate, but this bug prevents it. Pseudo-partial forms will not do because videos are often in the middle of the page and saving pseudo-partial forms moves them to the top of the page. :-(",1606317041,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,Problem with using pseudo-partial forms is that PageForms moves the template to the top of the page.,1606315365,PHID-USER-lucj4cqevg3ebah7vybd,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"Hi - partial forms have never really worked well, and they certainly don't work with embedded templates. My long-term plan is to get rid of them - as soon as there's support for editing sections in SF (as opposed to just templates), I think partial forms can be gotten rid of. Until then (and afterwards as well), you can definitely use ""pseudo-partial"" forms - regular forms that only have a small subset of the fields.",1329248569,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"**van.de.bugger** wrote:
+
+> formally it is declared as partial form, so it does not have to
+save non-used fields of main template, does it?
+
+Oops, of course it should be:
+
+formally it is NOT declared as partial form, so it does not have to
+save non-used fields of main template, does it?",1328917343,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+Hitting enter on an empty list item should end the list,"Or at least Aryeh thinks so; I guess this is disputable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1328023740,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ewjtzp76256uwhrcagor,task_description,resolved
+Hitting enter on an empty list item should end the list,Related: https://bugzilla.wikimedia.org/show_bug.cgi?id=48287,1368090037,PHID-USER-qmcrs2npimuywblubznv,PHID-TASK-ewjtzp76256uwhrcagor,task_subcomment,NA
+Hitting enter on an empty list item should end the list,Noting bugs closed in the 2012-10-15 release.,1351534185,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ewjtzp76256uwhrcagor,task_subcomment,NA
+Hitting enter on an empty list item should end the list,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341828,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ewjtzp76256uwhrcagor,task_subcomment,NA
+Hitting enter on an empty list item should end the list,Fixed with new version of VE.,1340401239,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ewjtzp76256uwhrcagor,task_subcomment,NA
+VisualEditor: Ctrl+Home / Ctrl+End don't navigate the cursor to the beginning/end of the document,"Pressing Ctrl+Home should send the cursor to the start of the document, but instead it sends it to the start of the line (same behavior as home). Similarly for Ctrl+End.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1328023500,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-ct4l6w4mrliejtnz6hwi,task_description,resolved
+VisualEditor: Ctrl+Home / Ctrl+End don't navigate the cursor to the beginning/end of the document,"**orbit** wrote:
+
+This works now.",1349999703,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ct4l6w4mrliejtnz6hwi,task_subcomment,NA
+VisualEditor: Ctrl+Home / Ctrl+End don't navigate the cursor to the beginning/end of the document,"Mass-move out of ""General"" to ""ContentEditable"".",1340415381,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ct4l6w4mrliejtnz6hwi,task_subcomment,NA
+VisualEditor: Ctrl+Home / Ctrl+End don't navigate the cursor to the beginning/end of the document,Mass-moving items into VisualEditor product,1340402777,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ct4l6w4mrliejtnz6hwi,task_subcomment,NA
+ApiQueryParseTree doesn't work when XML format is requested,"**Author:** `neilk`
+
+**Description:**
+Something like this query:
+
+    http://wiki.ivy.local/w/api.php?action=query&prop=parsetree&titles=Main%20Page&format=json
+
+Returns a sensible data structure. However, when formatted as XML, an error is returned:
+
+    Warning: htmlspecialchars() expects parameter 1 to be string, object given in /Users/neilk/Sites/trunk/includes/Sanitizer.php on line 978
+
+I've tried other variants and sometimes I do get reasonable XML back but with empty contents. Is it not possible for the API to return arbitrary PHP data structures? Is there something to be done with 'indexed tags'?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1327970460,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rgsze6qyeosq3v4u4bgt,task_description,invalid
+ApiQueryParseTree doesn't work when XML format is requested,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341879,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rgsze6qyeosq3v4u4bgt,task_subcomment,NA
+ApiQueryParseTree doesn't work when XML format is requested,Fixed with new version of VE (code replaced).,1340400724,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-rgsze6qyeosq3v4u4bgt,task_subcomment,NA
+ApiQueryParseTree doesn't work when XML format is requested,"**neilk** wrote:
+
+The code in question was added r110344.",1328025602,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-rgsze6qyeosq3v4u4bgt,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"**Author:** `utsavsabharwal`
+
+**Description:**
+It would be great if could add following shortcuts:
+
+ctrl + { <-- For decreasing font size upto Heading 6
+ctrl + } <-- For increasing font size upto Heading 1
+
+Lemme know if I can help you out :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1325686440,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-4vao55kg5dno6lnw3rh7,task_description,resolved
+VisualEditor: Add keyboard shortcut for heading level,"Some feedback on the choice of shortcuts:
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-September/071684.html
+(http://www.gossamer-threads.com/lists/wiki/wikitech/388134)",1378657723,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Change 81605 merged by jenkins-bot:
+Add keyboard shortcuts for formatting tools
+
+https://gerrit.wikimedia.org/r/81605",1378254410,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Change 81605 had a related patch set uploaded by Jforrester:
+[WIP] Add keyboard shortcuts for formatting tools
+
+https://gerrit.wikimedia.org/r/81605",1377736667,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Unfortunately the ⌘ + 1 -> ⌘ + 8 are taken by the browser in Chrome for ""switch to tab 1…8"", and ⌘ + 9 is for ""switch to final tab"".
+
+I'm going to go our own way (whee) with:
+
+* ⌘ + Alt + 0 -> Paragraph
+* ⌘ + Alt + 1 -> Heading 1 (Page title)
+* ⌘ + Alt + 2 -> Heading 2 (Heading)
+* ⌘ + Alt + 3 -> Heading 3 (Sub-heading 1)
+* ⌘ + Alt + 4 -> Heading 4 (Sub-heading 2)
+* ⌘ + Alt + 5 -> Heading 5 (Sub-heading 3)
+* ⌘ + Alt + 6 -> Heading 6 (Sub-heading 4)
+* ⌘ + Alt + 7 -> Preformatted
+
+And potentially:
+
+* ⌘ + Alt + 8 -> Blockquote (when that is working)
+
+This isn't great, but it's the least-bad option that I can see.",1377716311,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Confluence seems preferable, mainly because it has one less key.  I'm not sure how many people are familiar with either, and people who know the Word shortcuts will have to disregard Ctrl + Alt + 4 either way.",1374037058,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"(In reply to comment #5)
+> This is typically done with ctrl+alt+# in Microsoft Word on Windows, where #
+> is a number between 1 and 3. 
+> 
+> I'm not sure if this is the right way to go, but at least there's some
+> precedence.
+
+Microsoft Word:
+* Ctrl + Shift + N -> Paragraph (⌘ + Shift + N on Mac)
+* Ctrl + Alt + 1 -> H1 (⌘ + Alt + 1 on Mac)
+* Ctrl + Alt + 2 -> H2 (⌘ + Alt + 2 on Mac)
+* Ctrl + Alt + 3 -> H3 (⌘ + Alt + 3 on Mac)
+* Ctrl + Alt + 4 -> € (hello, Europe!)
+
+Confluence:
+* Ctrl + 0 -> Paragraph (⌘ + 0 on Mac)
+* Ctrl + 1 -> H1 (⌘ + 1 on Mac)
+* Ctrl + 2 -> H2 (⌘ + 2 on Mac)
+* Ctrl + 3 -> H3 (⌘ + 3 on Mac)
+* Ctrl + 4 -> H4 (⌘ + 4 on Mac)
+* Ctrl + 5 -> H5 (⌘ + 5 on Mac)
+* Ctrl + 6 -> H6 (⌘ + 6 on Mac)
+* Ctrl + 7 -> Preformatted (⌘ + 7 on Mac)
+
+Should we adopt the Word ones (which are more common but less relevant) or the Confluence ones (which are a perfect fit for our needs, but less commonly-known)?",1371056324,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"This is typically done with ctrl+alt+# in Microsoft Word on Windows, where # is a number between 1 and 3. 
+
+I'm not sure if this is the right way to go, but at least there's some precedence.",1345668861,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,Standardise title.,1341257162,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Mass-move out of ""General"" to ""ContentEditable"".",1340415517,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,Mass-moving items into VisualEditor product,1340402770,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Not sure if we want key bindings for toggling formatting type? Also, not sure if we want to use these particular ones. :-)",1340398744,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+"When translating a string at translatewiki.net, there should be a screenshot of the page where the string is used","- document the idea at [[ https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects | Mentorship programs/Possible projects ]]
+- this project would use a lot of code from existing VisualEditor screenshots project",1416494621,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-nx6rwv65d53u3tb74upy,task_description,declined
+"When translating a string at translatewiki.net, there should be a screenshot of the page where the string is used","Move to MediaWiki, because Translate and TWN already support this. It's ""just"" about producing the screenshots and adding them to qqq.
+
+I'm not sure how many components are using https://commons.wikimedia.org/wiki/Special:Contributions/LanguageScreenshotBot but perhaps that feature can be promoted more. There are some devs who love screenshots for documentation but are probably unaware of the feature.",1427879127,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nx6rwv65d53u3tb74upy,task_subcomment,NA
+"When translating a string at translatewiki.net, there should be a screenshot of the page where the string is used",I do not plan to work on this any time soon. Please reopen if you care about this.,1427800770,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-nx6rwv65d53u3tb74upy,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","All the items in https://bugzillapreview.wmflabs.org/tag/visualeditor-data_model/ should also be in the main VisualEditor project, which is currently called https://bugzillapreview.wmflabs.org/tag/visualeditor-general/ (and per {T856} won't be re-named until after the import).
+
+I support the ~8000 bugs //could// all just be mass-added(?) after the import, but this feels like a perfect opportunity to get it done right from the start.",1414167177,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_description,declined
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","Cf. T100, T72, T101 on subprojects and parent projects.",1416843686,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#15852, @Jdforrester-WMF wrote:
+> Because the saved searches for Phabricator work the way they do, this means that every month or so we'd need to ping out an e-mail to everyone who might care about VisualEditor telling them to forget the old search URL and use a new one.
+
+According to your previous post, this query was meant to be used basically by the development team leadership. Even if not, I personally think that a query URL posted and updated at the parent project description would be more useful than flooding the parent project with >1000 tasks. HOWEVER,  none of this really matters. You are the product owner and you decide how you want to organize your projects.   :)
+
+Back to the initial request, it looks clear at this point that //tagging tasks also against a super-project// is more a particular approach than a solution for everybody. Therefore, we will not touch the migration script, and we will leave this decision to project owners, who can do this manually pretty easily with batch edits.
+
+Resolving as Declined.",1414491978,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#15771, @Qgil wrote:
+> I still don't see why you cannot do what you explain with the search query I'm proposing. 
+
+[Snip]
+
+The number of sub-projects inside VisualEditor changes quite frequently. Right now they are tracked by a combination of Bugzilla tracking bugs (mostly for features) and Bugzilla components (for code areas and types of problem). On average I'd say a new project comes along every month or so.
+
+Because the saved searches for Phabricator work the way they do, this means that every month or so we'd need to ping out an e-mail to everyone who might care about VisualEditor telling them to forget the old search URL and use a new one. The only way to work around this, AFAIAA, is to cheat with a mega-project that is added to everything anyway.
+
+I'm sure you've considered this and decided that for Phabricator you don't need it, which is awesome, but some of us do. :-)
+
+> PS: ACL has nothing to do with this discussion, and I suspect it doesn't work as you think it works. See https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Policy
+
+Well, no. The **team** ""VisualEditor"" will have special status in the ACL of the ""VisualEditor"" **repos** but probably not needed in the ACL of the ""VisualEditor"" project's **tasks**. Probably.",1414436055,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","I still don't see why you cannot do what you explain with the search query I'm proposing. 
+
+Let me explain you the situation of the Wikimedia Phabricator team, which is very similar to your case. We don't have a mega-project. In most cases, tasks that can go to a specialized project are not listed under ""Phabricator"". If we want to triage tasks tasks regardless of the subproject they are in, we only need to query https://phabricator.wikimedia.org/maniphest/query/q47HlqJVpTSy/
+
+One list, all tasks, grouped by priority. And still someone can go to ""Phabricator"" and get a sane list of tasks, because we are not duplicating by default. We did that at the beginning, and it didn't take long before we moved away. If we want to aggregate, we can use saved queries, leaving the default/general projects genuinely for tasks that don't fit anywhere else (just like you have in Bugzilla, btw).
+
+PS: ACL has nothing to do with this discussion, and I suspect it doesn't work as you think it works. See https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Policy",1414429979,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14800, @Qgil wrote:
+>>>! In T859#14527, @Jdforrester-WMF wrote:
+>> the ""general"" bucket is just a ""triage me"" one, and a general-overview list of top-end priorities.
+> 
+> I'm not sure a list with ~8000 bugs is useful to ""triage me"" anything. Besides, you can just get that list with a saved search query whenever you need it.
+
+No.
+
+All new VE bugs go into the VE mega-project (with a status of ""Needs triage""). As part of the triage, it will be given a priority and added to one or more projects of which it's a part – //e.g.// ""VisualEditor MediaWiki integration"" or ""VisualEditor table editing"" or ""VisualEditor ContentEditable"" or ""VisualEditor performance"" or whatever.
+
+Most people will care about a particular feature or aspect of functionality, and so will only follow those particular projects. A few people, like the development team leadership, will want to see the overall priorities across the whole of the VisualEditor mega-project to decide whether to pull resources from one area and put it into another. The ACL for merge/etc. access will also belong to members of the VisualEditor mega-project (probably), as more fine-grained control is not needed and locking-down controls is against our general ethos at Wikimedia.
+
+Does this make sense?",1414426067,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14527, @Jdforrester-WMF wrote:
+> the ""general"" bucket is just a ""triage me"" one, and a general-overview list of top-end priorities.
+
+I'm not sure a list with ~8000 bugs is useful to ""triage me"" anything. Besides, you can just get that list with a saved search query whenever you need it.
+",1414191829,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14527, @Jdforrester-WMF wrote:
+> the ""general"" bucket is just a ""triage me"" one, and a general-overview list of top-end priorities.
+
+I'm not sure a list with ~8000 bugs is useful to ""triage me"" anything. Besides, you can just get that list with a search query.
+",1414191799,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14564, @Qgil wrote:
+> Also, wouldn't the right solution be to move the ""General"" tasks to the main project and then archive the ""General"" project?
+
+Yes, that's what T856 said. Except that there is no ""main project""; ""General"" is the principal project.",1414179922,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","Also, wouldn't the right solution be to move the ""General"" tasks to the main project and then archive the ""General"" project?",1414173470,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14534, @Aklapper wrote:
+> Umbrella projects: If you don't want to spend time manually adding super-projects to task in projects there needs to be some rule or even code to automatically do that... 
+
+Sure, that's what Herald is for. :-)
+
+> In general we prefer to keep the Bugzilla-to-Phab import code simple and not handle project rename requests in there.
+
+Yeah, fine for {T856} to be fixed manually by me after the migration. If necessary, I can fix this request manually too after the migration, but….",1414168616,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","Umbrella projects: If you don't want to spend time manually adding super-projects to task in projects there needs to be some rule or even code to automatically do that... 
+
+In general we prefer to keep the Bugzilla-to-Phab import code simple and not handle project rename requests in there.",1414168506,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14519, @Qgil wrote:
+> Different teams might want to deal with this situation in different ways. You are saying: all tasks in a subproject must be added to the parent project as well. Others might prefer the current situation, where tasks in a subproject are not ""duplicated"" in a parent project.
+> 
+> For instance, this is what we are doing in the Phabricator project. As soon as a task is defined as ""Code-Review"" or ""Project-Management"", we usually place them in these subprojects only, removing them from ""Phabricator"" unless for some reason we want to keep it as a reminder. This keeps the parent project backlog still usable, allowing us to put some attention to the tasks that are not placed in some other subproject.
+
+Sure, but for the projects I listed the ""general"" bucket is just a ""triage me"" one, and a general-overview list of top-end priorities.",1414167914,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","Different teams might want to deal with this situation in different ways. You are saying: all tasks in a subproject must be added to the parent project as well. Others might prefer the current situation, where tasks in a subproject are not ""duplicated"" in a parent project.
+
+For instance, this is what we are doing in the Phabricator project. As soon as a task is defined as ""Code-Review"" or ""Project-Management"", we usually place them in these subprojects only, removing them from ""Phabricator"" unless for some reason we want to keep it as a reminder. This keeps the parent project backlog still usable, allowing us to put some attention to the tasks that are not placed in some other subproject.
+",1414167756,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+High level overview of Phabricator projects,"Is this something that we want to have before the launch, right after the launch, or whenever it is ready?
+
+> [[ https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079117.html | On Wed, Oct 22, 2014 at 8:02 AM, David Cuenca  wrote ]]:
+> 
+> Tagging is just a poor man's
+> version of classing, since it doesn't let you define the relationship
+> between tags. True that you can put any task in several projects/tags, the
+> problem is that the project structure is nevertheless flat:
+> https://phabricator.wikimedia.org/project/query/all/
+> Which will become cumbersome to navigate for occasional visitors as the
+> number of projects goes up.
+
+Sure, but after years of Bugzilla we have also seen that the rigid tree structure of https://bugzilla.wikimedia.org/describecomponents.cgi causes many problems too, and occasional visitors probably find it cumbersome anyway.
+
+If we want a high level overview of the projects, we can always have a wiki page identifying the main teams/projects, the starting points to understand the hundreds of projects that we will have soon. Now there is a task to discuss this.  :)",1414075117,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_description,declined
+High level overview of Phabricator projects,"1. Regarding Bugzilla's product-component tree structure vs. Phab's flat namespace, soon the way to go in Phabricator will be using subprojects (see T123078) instead of some external wiki page listing connections or hierarchy between Phab projects.
+2. I consider http://www.mediawiki.org/wiki/Phabricator/Projects sufficient, and if $someone considers it not sufficient, $someone please write a wikipage for what is wanted here (and/or reopen this task and assign it to themselves), or enhance the code that creates http://www.mediawiki.org/wiki/Phabricator/Projects to fulfil their needs.
+1.+2. together: Hence I'm declining this task.",1453296382,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"We do have http://www.mediawiki.org/wiki/Phabricator/Projects nowadays (which is created automatically). That's probably where to continue here.
+
+That current script misses certain contextual knowledge, e.g. that a project named ""Flow"" is technically a ""MediaWiki extension"", or that ""FR"" is the same as ""Fundraising"". Not sure how that could be implemented.",1433945046,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,I'm going to remove ECT 01/2015 from this. It's a nice to have but I don't think I'll have time to work on this in January,1420635098,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"We have scheduled this task for #ECT-January-2015 but it has no owner. Based on lessons learned, we should either get an owner for it or remove it from the sprint.",1420616338,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Maybe you don't have the permissions. No problem, it's here now: https://www.mediawiki.org/wiki/Phabricator/Projects",1418381155,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"@Qgil I have added the draft template to the wiki. However, I cannot find the ""Move"" link. All I see is (From left to right): User Page, Discussion, Read, Edit, Edit Source, View History and Watchlist (The star). Some help is appreciated!",1418373981,PHID-USER-tezy4s5q5b72t2dhoo23,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"@Toolboxx8, you have done a tone of work! Thank you very much. I will close this task as completed now. Just one thing, can you please add a ""{{draft}}"" template at the top of the page (just paste that string using ""edit source"", and then move the page to Phabricator/Projects, please? To move the page just click the ""More"" link in the toolbar.
+
+We will probably massage that page a bit and then create another task to add the descriptions and polish it. As said, I believe you have put enough effort to consider your GCi task closed, even if we will keep this task here open until the page is ready. Thank you again.",1418369289,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"So, I have added links to the list and add a few more projects that were present in Phabricator but not in Bugzilla.
+
+It is still incomplete, mainly the MediaWiki extensions part (there are a lot under it) and the Wikimedia section at the bottom. I have included archived projects while adding a (Archived) note beside the projects, it can be removed if it is not wanted. I also have not include a lot of projects that are in Phabricator but was not in Bugzilla e.g. JavaScript, Jenkins, Human Resource etc.
+
+You can check out the list at : https://www.mediawiki.org/w/index.php?title=User:Toolboxx8/Sandbox
+
+Another problem is at the Common Apps part where all the projects are archived. Should it just be removed? I added a link to the Android project page on Phabricator by the side.
+
+Finally, just out of curiosity as I was going through the list of projects. Under 'Unofficial Apps' the projects listed there use ""or"" instead of ""on"", for example: Wikipedia or Windows 8. Shouldn't it be ""on"" instead of ""or""? Just a minor question.",1418357647,PHID-USER-tezy4s5q5b72t2dhoo23,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"@Aklapper Oh, I see.
+
+Yeah, that makes a lot of sense. As I was browsing through the active projects I couldn't find any that was closely related to those in Bugzilla. Yes, it only states if the projects is new, unconfirmed or patched.
+
+Okay, thanks a lot! I'll see what I can do to improve it further.
+
+@Qgil I will continue to work on it for a while and upload the URL to the GCi page. Is that ok?
+
+I feel that I could still improve the page a little more.",1418351217,PHID-USER-tezy4s5q5b72t2dhoo23,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"I think the current list would be good enough for a GCi task in terms of entries. We can polish these type of details that are quite time consuming for a newcomer but someone like Andre can decide in a whim. I would put my time on linking each entry to its Phabricator project and adding the soft description, if available.",1418326729,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"@Toolboxx8: Thanks for your work on this!
+Referring to your example, Bugzilla product ""Common Apps"" and component ""Android"" became Phabricator project ""Commons-App-Android"" - you can see that listed in the list of all projects under https://phabricator.wikimedia.org/project/query/all/?after=Commoa .
+Note that the project is closed as archived so no new tasks can be filed under it anymore (I guess you looked at the list of //active// projects in Phabricator, which makes sense - we're not interested in listing archived/inactive projects).
+Unfortunately, Bugzilla's describecomponents.cgi does not tell you whether a project is archived or not so that is indeed confusing. :-/
+
+If you have further specific cases where you aren't sure what has happened, don't hesitate to list them here and ask - but in general, don't worry too much if you cannot find some stuff, it does not have to be //totally// perfect. :)",1418320281,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"I have created a clone (quite literally) of the old Bugzilla page: https://old-bugzilla.wikimedia.org/describecomponents.cgi at https://www.mediawiki.org/w/index.php?title=User:Toolboxx8/Sandbox which is almost an exact copy of the old web page.
+
+I have not linked the items to any projects yet as I know the difference between Bugzilla and Phabricator. However, I am unsure of how to link the two together. Some projects that are in Bugzilla are not present in Phabricator. Whereas some projects in Phabricator are not listed in Bugzilla. Any advice on tackling this problem?
+
+Should I edit the project page? For example:
+
+  - Common Apps
+       - Android
+
+becomes
+
+  - Android
+(as in Phabricator) and then add subprojects under this title?
+
+
+
+
+
+
+",1418316119,PHID-USER-tezy4s5q5b72t2dhoo23,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"# Create an account in https://www.mediawiki.org/
+# Then you can go with your browser to a page like www.mediawiki.org/wiki/User:YOUR-USERNAME/Sandbox (changing ""YOUR-USERNAME"" for your actual username)
+# Click ""Create""
+# Type some text. Save. 
+
+There you have your page. Then you can share the URL here while you keep editing by clicking ""Edit"".
+",1418219396,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Hi @Qgil
+
+Thanks for the guidelines! I now understand what is my aim.
+
+However, I have a few questions. Where should the wiki page be? And how do I go about creating one?
+
+I'm sorry but I'm sort of new to creating wiki pages, but I'm willing to learn!
+
+I have search about and read a few articles and watch a few videos but I'm not sure which one to follow. Any suggestions?",1418218630,PHID-USER-tezy4s5q5b72t2dhoo23,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Hi @Toolboxx8, to keep this task simple, 
+
+# please create a wiki page cloning the list of projects shown in this page: https://old-bugzilla.wikimedia.org/describecomponents.cgi, but linking to their current Phabricator projects, which an be found under https://secure.phabricator.com/project/.
+# then, under each project list the subprojects that look more relevant to you, for instance checking the amount of tasks they have listed.
+
+I started a rough example of how this would look like at [[ https://phabricator.wikimedia.org/T833#19869 | at a previous comment ]] in this task.
+
+No need to aim for perfection. If you have a wiki page that looks complete enough for a v0.8, we can continue polishing it.",1418216129,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Hi!
+
+I'm excited in taking part in GCi and taking this task. However, I'm not very sure about my task at hand. I have a rough idea from the description given, but I would like to have a more detailed explanation? 
+
+It says that my proposal should help a newcomer to Phabricator to understand how we use Phabricator for managing projects. Does that mean I'm writing like a tutorial guide? 
+
+Some help is much appreciated! Thanks!",1418183434,PHID-USER-tezy4s5q5b72t2dhoo23,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Heads up! A student has taken this #Google-Code-in-2014 task.
+
+http://www.google-melange.com/gci/task/view/google/gci2014/5777066188341248
+
+Hi toolboxx8! If you have questions, you can ask them here. In addition to the GCi mentors there are other community members that may help you. Thank you for your interest in contributing to Wikimedia!",1417869252,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,Task added to GCI at https://www.mediawiki.org/wiki/Google_Code-in_2014#Category:_Documentation.2FTraining,1415646859,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"I don't think we need a 1:1 mapping of all the projects. After the Bugzilla migration we will have hundreds. The word ""overview"" in the subject of this task is important.
+
+Also, we don't need to perpetuate a Bugzilla tree structure that never made us happy.
+
+We just need a sane list of main areas, identifying the most popular / relevant projects underneath.",1415402096,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"If I understand correctly, we want to start with a 2-column table on mediawiki, that lists:
+1. The existing components in bugzilla, as the structured 2-level tree that they are currently in. (https://bugzilla.wikimedia.org/describecomponents.cgi)
+2. The current list of phabricator projects. (https://phabricator.wikimedia.org/project/query/all/)
+
+----
+Once that exists:
+* A) We'd add a section for anyone to Propose obvious/immediate additions, for column 2. 
+** These proposals would be related to things discussed in T802 and T705. 
+* B) We'd discuss/decide on a logical hierarchy for sorting the items in column 2, for an at-a-glance overview, to help people find the likely project name(s) they want to use in a Task.
+** B1) This might incorporate/adapt the listing/structure given in https://www.mediawiki.org/wiki/Wikimedia_Engineering#Features_engineering , plus other sections from https://wikimediafoundation.org/wiki/Template:Staff_and_contractors 
+** B2) Plus potentially some of the structure from https://meta.wikimedia.org/wiki/Wikimedia_movement
+* C) And we'd also take 1 or 2 key examples of each ""Type"" to add to the docs in https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Type_of_project (only ""Tag"" currently has an example: ""Accessibility"").
+
+----
+
+Q1. Is that fairly accurate?
+
+Q2. What other existing mappings, are missing?
+
+Q3. Are **all** the existing components in bugzilla going to be replicated in phabricator 1-to-1? (""No"" would mean we are also taking this opportunity to remove/merge some of the unused/un-useful components. Either now, or later.)
+
+Q4. Is there a static list of all bugzilla's current ""Product->Component"" options?  (Ideally, I want a copy&pastable 2-level bulletpoint list, of just the names. Otherwise I have to manually copy&paste a few hundred lines...)
+
+(I have zero spare time to guarantee mentoring. But I'd happily contribute thoughts/edits, occasionally. :-)",1415397006,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"...and I am very happy to (co-)mentor this task! 
+Anybody willing to add this to https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks ? (I might do so if nobody is faster)
+
+@Micru and/or @Quiddity: Are you in?",1415385417,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"(Sorry, apparently my brain cannot have all ideas at once)
+
+... and with https://bugzilla.wikimedia.org/describecomponents.cgi as starting point, a student cannot go too too wrong, with just a bit of guidance.",1415365199,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Also, this is a task that @Micru and/or @Quiddity could mentor. You just need to know about Wikimedia, editing wiki pages, and searching projects in Phabricator.",1415365104,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Also, this is a task that @Micru and/or @Quiddity could mentor. You just need to know about Wikimedia, editing wiki pages, and searching projects in Phabricator to mentor this one.",1415365070,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"We are talking about a wiki page that serves as a list of the main projects (the ones that are important on its own and the ones that act as umbrella of many others). Something like (if only our Bugzilla tree structure would be same). This page shouldn't aim to contain all the projects, probably 2 levels only i.e.
+
+* MediaWiki
+** API
+** Configuration
+** ((some more core components))
+* MediaWiki Extensions
+** VisualEditor
+** MobileFrontend
+** ((a few more selected))
+** See all extensions ((a query to all projects containing the word ""extension"" in the title)
+* (etc etc)
+
+While having a perfect two-level tree isn't trivial, having a first version up to a level that invites experienced contributors to fine tune it is not that difficult.",1415364901,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"I'm not entirely sure which problem we want to solve. Make people understand what types of ""projects"" we have is already reflected by https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Type_of_project I'd say? 
+Or what else is thought of?
+
+For the records, https://phabricator.wikimedia.org/project/query/all/ lists all archived and active projects.",1415364147,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,A GCi task?,1415354993,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"This would be useful to identify who is currently working on a card. Helps with visual scanning and clearly shows when certain people are ""hogging"" cards.",1419872102,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-j5yw5s756nhxpysj3ya6,task_description,resolved
+show avatar of assigned to field on cards displayed in workboard,"As Shaggy once said ""it wasn't me"", but do appreciate the heads up.",1425506265,PHID-USER-izqileijt5niumtehazh,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"CCing @JKatzWMF just to ma sure he is aware of he comment above. No worries, it happens the first time.  :)",1425465421,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,">>! In T85455#1083879, @Jdlrobson wrote:
+> Got it! FYI to newbies like myself there is a barely visible checkbox when you edit project details for Sprint - tick that and boom - magic :)
+
+@jdlrobson: Please do read https://www.mediawiki.org/wiki/Phabricator/Project_management#Sprints and spread the word that there is documentation. I just corrected the wrong icon, the wrong color, and the missing start and end dates of ""Gather Sprint C_"" (the name still violates the [[ https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects | project guidelines ]]).",1425464618,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Got it! FYI to newbies like myself there is a barely visible checkbox when you edit project details for Sprint - tick that and boom - magic :)
+",1425412962,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,That is not a Sprint project.... As in using the Sprint extension (no burndown chart).,1425412866,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,This is so far my biggest pain point about using Phabricator for sprint boards. I can see username but not avatar - how do I get the avatars on https://phabricator.wikimedia.org/tag/gather_sprint_c/board/,1425412673,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Proof: https://phabricator.wikimedia.org/tag/%C2%A7_visualeditor_q3_blockers/
+
+Thank you!",1424351788,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Good! It looks like the cards wuld benefit from some vertical-align: top.
+
+Anyway, @Jdlrobson is the one wanting this feature, and he is a web coder ninja himself... (hint, hint)",1421406939,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"In order to make the cards look better (like Trello), we would have to recreate several upstream UI classes.  
+
+For this image, I opted to use the basic icon class PHUIIconView() which has constants that control the css and celerity resource implementation.  The icon size is set by the constant HEAD_SMALL which makes it 35px square.  This was overridden in a recent update in the phabricator-side-menu-view.css (phabricator-icon-nav .phui-icon-view.phuihead-small) that sets it as 24px square.  This can be seen here: https://phab08.wmflabs.org/project/sprint/board/27/
+
+I do not think that this card style is very nice and it could be improved.  But, the small image is there for now.
+
+",1421910702,PHID-USER-lltif2drabccdkwhet7x,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"In order to make the cards look better (like Trello), we would have to recreate several upstream UI classes.  
+
+For this image, I opted to use the basic icon class PHUIIconView() which has constants that control the css and celerity resource implementation.  The icon size is set by the constant HEAD_SMALL which makes it 35px square.  This was overridden in a recent update in the phabricator-side-menu-view.css (phabricator-icon-nav .phui-icon-view.phuihead-small) that sets it as 24px square.  This can be seen here: https://phab08.wmflabs.org/project/sboard/27/
+
+I do not think that this card style is very nice and it could be improved.  But, the small image is there for now.
+
+",1421405535,PHID-USER-lltif2drabccdkwhet7x,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Thank you! Not bad at all for sprints, where there are less tasks and all of them are supposed to be assigned to someone. I can also see its usefulness in non-sprint projects, but that depends on https://secure.phabricator.com/T4863, which is a longer term game.
+
+I think it would be better to use the smallest version of the avatar, like the one used in the log of tasks (i.e. see above ""Aklapper triaged this task as ""Needs Volunteer"" priority."").
+
+Also, the boxes might need to be arranged differently. Currently the height of the avatar pulls ""Points:"" down, which looks bad and makes the size of the card bigger.",1421052913,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,Check https://phab08.wmflabs.org/project/sprint/board/27/ for demo and test of this feature.  ,1421910747,PHID-USER-lltif2drabccdkwhet7x,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,Check https://phab08.wmflabs.org/sprint/board/27/ for demo and test of this feature.  ,1420215031,PHID-USER-lltif2drabccdkwhet7x,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Change 182463 merged by Christopher Johnson (WMDE):
+adds User image icon to Sprint Board Task Cards
+
+[[https://gerrit.wikimedia.org/r/182463]]",1420214260,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Change 182463 had a related patch set uploaded (by Christopher Johnson (WMDE)):
+adds Owner Image Icon to Sprint Card
+
+[[https://gerrit.wikimedia.org/r/182463]]
+
+#patch-for-review",1420213938,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+Use URL from foreign file repositories to search for images within VisualEditor,"What I want:
+
+1)  Open page.
+2)  Insert > Image
+3)  Paste in URL (from Commons)
+4)  Insert image
+
+
+What I got:
+
+1)  Open page.
+2)  Insert > Image
+3)  Paste in URL (from Commons)
+4)  No image found.
+5)  Remove most of the URL
+6)  Insert image.
+
+",1418779487,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-v25fzfcgl7xz24bzsekb,task_description,open
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"As a user looking for a report about a MediaWiki core bug, I want to quickly look for it without bothering about non-core reports or specific components/projects, so that I find what I'm looking for before I give up out of desperation.
+
+----
+
+Currently, I must type N MediaWiki core projects manually in the ""Projects"" field. (Cf. https://secure.phabricator.com/T3670#65849, first bullet.)",1417872973,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_description,open
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#5405654, @Aklapper wrote:
+>>>! In T76942#2503522, @mmodell wrote:
+>> I think this discussion deserves to be resurrected now that we have real subproject support in phabricator.
+> 
+> Indeed. I think nowadays the way to go would be converting all current separate `#MediaWiki-*` parent projects which are about the MediaWiki Core codebase (note that not all are!) to [subprojects](https://www.mediawiki.org/wiki/Phabricator/Project_management#Parent_Projects,_Subprojects_and_Milestones) of a **new** `#MediaWiki` or `#MediaWiki-Core` parent project. 
+
+Premising I don't have a 100% big picture of the Wikidata stuff in Wikimedia Phabricator, implementing Sub-Projects makes really sense from me from a Phorge/Phabricator perspective. Everything in the Sub-Projects automatically ends up in the root Project, making any wide search definitively easier, without the need to list all Sub-projects manually.",1684857400,PHID-USER-hphk5jxfxfgl64tpfacw,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#2503522, @mmodell wrote:
+> I think this discussion deserves to be resurrected now that we have real subproject support in phabricator.
+
+Indeed. I think nowadays the way to go would be converting all current separate `#MediaWiki-*` parent projects which are about the MediaWiki Core codebase (note that not all are!) to [subprojects](https://www.mediawiki.org/wiki/Phabricator/Project_management#Parent_Projects,_Subprojects_and_Milestones) of a **new** `#MediaWiki` or `#MediaWiki-Core` parent project. 
+Why a new parent project?
+* A task cannot have both the parent project and a subproject of that parent project associated. So if the already existing project called `#MediaWiki-General` became the parent project and a task is both associated with the `#MediaWiki-General` project and another now-to-become subproject, we'd have data inconsistency in the database due to T224421.
+* Furthermore, when a first subproject is added to a parent project, all of the parent project members shift to the first subproject. Parent projects do not support adding members.
+That's why it would probably make more sense to keep the `#MediaWiki-General` project and **not** make it a parent project, but instead create a new parent project and make the existing `#MediaWiki-General` (or `#MediaWiki-Misc` or whatever to call it) a subproject of that new parent project.
+
+For completeness: A task can have more than one subproject of the same parent project associated (at least when I tested this locally). So there should not be issues having more than one `#MediaWiki-*` now-to-become subproject associated to a task. (Not the case for milestones but we don't talk about milestones here.)
+
+I hope I did not forget any relevant aspects when I wrote this comment.",1565372416,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#5214363, @Aklapper wrote:
+> Also note that nowadays, a lot of MediaWiki core tasks are under `#Core Platform Team` and `#Core Platform Team Backlog` tags. See for example https://phabricator.wikimedia.org/T219524#5070460
+
+That seems like an antipattern (if at all intentional).",1558960835,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Also note that nowadays, a lot of MediaWiki core tasks are under `#Core Platform Team` and `#Core Platform Team Backlog` tags. See for example https://phabricator.wikimedia.org/T219524#5070460",1558955029,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Also note that nowadays, a lot of MediaWiki core tasks are under `#Core Platform Team` and `#Core Platform Tean Backlog` tags. See for example https://phabricator.wikimedia.org/T219524#5070460",1558955015,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"This project is selected for the #developer-wishlist voting round and will be added to a MediaWiki page very soon. To the subscribers, or proposer of this task: please help modify the task description: add a brief summary (10-12 lines) of the problem that this proposal raises, topics discussed in the comments, and a proposed solution (if there is any yet). Remember to add a header with a title ""Description,"" to your content. Please do so before February 5th, 12:00 pm UTC. ",1486164929,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"A question @Nikerabbit asked reminded me of this bug, specifically of the use case: list the #i18n tasks filed against a MediaWiki core/MediaWiki extensions component, to have an overview similar to what was provided by SMW on https://translatewiki.net/wiki/Support/Open_requests#MediaWiki .",1478428446,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"The problem it was blocked on was disabling notifications, right? Having an umbrella project would make sense, with or without subproject support, but Andre has a point about spam.",1469742709,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),I think this discussion deserves to be resurrected now that we have real subproject support in phabricator.,1469742239,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#1287991, @Krinkle wrote:
+> We now have the generic ""Untriaged"" status
+
+There is no such task status but a ""Needs Triage"" priority but the task priority field is [[ https://www.mediawiki.org/w/index.php?title=Topic:Sh94hyx5vqslwf8n&topic_showPostId=shljfgkm296r8vk3#flow-post-shljfgkm296r8vk3 | not used by every team ]] so that does not entirely sound like the same.
+
+> However, considering not all components in MediaWiki core have an appropiate place in Phabricator yet (some are simply too niche or don't fit anywhere) a ""MediaWiki-Core-Misc"" or ""MediaWiki-Other"" component may be useful.
+
+""Misc"" to me is pretty much the same as ""General"" which already is part of the current name... but interpretation of words might be different.
+
+> I've tried to make a complete list of all MediaWiki core components, saved in the profile description of #MediaWiki-General-or-Unknown: https://phabricator.wikimedia.org/project/profile/135/
+
+Uh, thanks! I hope we will remember to update that when needed...",1432130685,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Indeed. ""Unknown"" should not be its own component anymore. We now have the generic ""Untriaged"" status and/or workboard column for that (depending on the project in question).
+
+However, considering not all components in MediaWiki core have an appropiate place in Phabricator yet (some are simply too niche or don't fit anywhere) a ""MediaWiki-Core-Misc"" or ""MediaWiki-Other"" component may be useful. Or perhaps having just ""MediaWiki"" for those suffices, though I do see a use case for being able to query those at ease (and even have a workboard for it). Doing an exclusion search is imho unacceptable. Also because the list of MediaWiki subcomponents will inevitably change over time, and will keep changing a lot in the short term as we identify more components in MediaWiki and move other things out into libraries.
+
+I've tried to make a complete list of all MediaWiki core components, saved in the profile description of #MediaWiki-General-or-Unknown: https://phabricator.wikimedia.org/project/profile/135/",1431701531,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#946690, @Nemo_bis wrote:
+>> rename MediaWiki-General-or-Unknown to #MediaWiki 
+> 
+> Absolutely not. We MUST be able to search stuff in the MediaWiki-General-or-Unknown component. If you rename it #MediaWiki, it will immediately get filled with stuff which is not General-or-Unknown, and phabricator doesn't practically offer search features to counter this. Deleting the project is about as useful.
+
+I disagree with Nemo; renaming sounds like a good idea to me. It won't get filed if the bugs are triaged, and bugs are being triaged.
+
+More important use-case are people filing bugs, who keep accidentally adding them in `#MediaWiki-Core-Team` (perhaps since that's what pops up when searching for ""mediawiki core"" project).",1423514102,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"So I'd propose creating a MediaWiki umbrella project (like VisualEditor or Multimedia) and creating a Herald rule to automatically add that umbrella project to any of the (newly created) tasks in one of MediaWiki Core's ""subprojects"". 
+
+(Big) **But:**
+* Adding that umbrella project to all existing tasks will create a huge number of notifications. We are talking about roughly already 4800 //open// tasks here, and for proper search results I'd prefer including also closed ones which means updating approx. 26000 tasks. I am not sure if we could (ab)use a maintenance window (like T86772) and //somehow// disable mail notifications for that time (@chasemp: Can we do that somehow?), but that's nothing I want to do in ""normal mode"".
+* Adding that umbrella project to all existing tasks via batch-editing will be cumbersome and time-consuming as long as T76152 is not fixed. I could survive that but it'll take some time (26000 / ~100 = 260 actions). Or I need to first play more with / learn Conduit and bots. Meh.
+
+So until these one and a half items are sorted out, we are unfortunately stuck here.",1421603212,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#946690, @Nemo_bis wrote:
+>> rename MediaWiki-General-or-Unknown to #MediaWiki 
+> 
+> Absolutely not. We MUST be able to search stuff in the MediaWiki-General-or-Unknown component. If you rename it #MediaWiki, it will immediately get filled with stuff which is not General-or-Unknown, and phabricator doesn't practically offer search features to counter this.
+
+It is unclear why ""we must"" and who we is. 
+You could search for ""In All Projects: MediaWiki"" && ""Not In Projects: ..."" and save that query. Setting that query up is pretty cumbersome though.",1419858507,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> rename MediaWiki-General-or-Unknown to #MediaWiki 
+
+Absolutely not. We MUST be able to search stuff in the MediaWiki-General-or-Unknown component. If you rename it #MediaWiki, it will immediately get filled with stuff which is not General-or-Unknown, and phabricator doesn't practically offer search features to counter this. Deleting the project is about as useful.",1419841708,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"==== Creating an MW Core umbrella project ====
+
+1) So the proposal is to rename #MediaWiki-General-or-Unknown to #MediaWiki ? If MW Core team is fine with that I am happy to go ahead.
+
+2) Note that for VisualEditor I set up a Herald rule (H10, but T630):
+
+ If ""Projects"" include any of: {VisualEditor-ContentEditable, VisualEditor-ContentLanguage, ...}, then: Add (umbrella) project ""VisualEditor"", every time this rule matches. (""every time"" means even if someone tries to manually remove the Umbrella project that it would be readded again to a task).
+  Is the same wanted here too?
+
+==== Renaming MW Core subprojects ====
+
+Renaming all those MediaWiki-* core subprojects is a separate topic (this task is about searching core tasks). See the list at https://phabricator.wikimedia.org/project/query/all/?after=MediaWiki-a (and ignore some stuff like extensions, ""MediaWiki-Developer-Summit-2015"" project etc.) for those projects.
+If we renamed ""MediaWiki-Database"" to ""Database"" this would collide with the Herald rule that I proposed above - any task with projects ""MediaWiki-extensions-Foo"" and ""Database"" (named ""MediaWiki-Database"" beforehand) would get an automatic ""MediaWiki"" project associated with that rule. I don't think this would be helpful, and if we didn't set up a Herald rule then manually adding the ""MediaWiki"" umbrella project is not a great use of triage time either.
+So with the current situation I'm slightly against using more generic names for those MW core subprojects.",1419806954,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#848212, @Chad wrote:
+>>>! In T76942#848206, @Nemo_bis wrote:
+>>> You'd search for [Database] and not [MediaWiki]
+>> 
+>> Is ""and not"" allowed in the search, filters and workboard definitions consistently? 
+> 
+> I see fields to exclude projects in all these places. Let me clarify:
+> # Go to [[ /maniphest/query/advanced/ | advanced search ]]
+> # Add ""MediaWiki"" to ""Not in Projects""
+
+That's one place, not ""all these places"". For instance the main search has no ""Not in projects"". https://phabricator.wikimedia.org/search/query/advanced/ 
+
+Did you check the search forms of all applications which have knowledge of projects? (I don't even know which those are.)",1419805268,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#848206, @Nemo_bis wrote:
+>> You'd search for [Database] and not [MediaWiki]
+> 
+> Is ""and not"" allowed in the search, filters and workboard definitions consistently? 
+
+I see fields to exclude projects in all these places. Let me clarify:
+# Go to [[ /maniphest/query/advanced/ | advanced search ]]
+# Add ""MediaWiki"" to ""Not in Projects""",1418661734,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> You'd search for [Database] and not [MediaWiki]
+
+Is ""and not"" allowed in the search, filters and workboard definitions consistently? ",1418661493,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#848047, @Nemo_bis wrote:
+>> So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database]
+> 
+> And how to distinguish that from, say, bugs in some extensions with the usage of the database?
+> 
+
+You'd search for [Database] and not [MediaWiki]
+
+> Plus, did we really surrender to the idea that to do a mere search here we'll need to edit tens of thousands bugs to update their tags?
+
+It's more than just search imho. I think the current tags are an awful way to organize bugs and my plan gives us a whole lot more flexibility in this area :)",1418655989,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database]
+
+And how to distinguish that from, say, bugs in some extensions with the usage of the database?
+
+Plus, did we really surrender to the idea that to do a mere search here we'll need to edit tens of thousands bugs to update their tags?",1418654659,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database]
+
+And how to distinguish that from, say, bugs in some extensions with the usage of the database?
+
+Plus, did we realy surrender to the idea that to do a mere search here we'll need to edit tens of thousands bugs to update their tags?",1418654644,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database]
+
+And how to distinguish that from, say, bugs in some extensions with the usage of the database?",1418654510,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"I think this is how it should be done, and I'm personally happy that no less than the MediaWiki team is willing to move in this direction. 
+
+In addition to solving the search fragmentation problem, this also will mean that there will be better piles of untriaged tasks: a very big one (but only one) for all MediaWiki related tasks, and then one for each ""discipline"" (tag), where contributors specialized in that area can help with a first triage regardless of whether they are directly involved in MediaWiki core or not.
+
+One problem to take into account are the mentions to `#mediawiki` the IRC channel. But well, chances that those mentions are written in #mediawiki related tasks are high, and if not, removing the project is easy.",1418376575,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#842969, @bd808 wrote:
+> Can we just rename #mediawiki-general-or-unknown to #MediaWiki?
+
+In my plan that's how I'd do it, then additionally add that tag to all MediaWiki-* tagged tasks and then rename their projects to drop the MW-* prefix.",1418337002,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),Once upon a time in Bugzilla we had a catch all component for Mediawiki:  MediaWiki -> General-or-Unknown.  #MediaWiki sounds good to me.,1418336918,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Here's what I've been saying to do (in a couple of places on IRC already). The current MediaWiki-* tags are awful. Instead, we should have a [MediaWiki] project in which bugs about MediaWiki go. We'd then have things like [Database], [Localization], [Editing], [Parsing] that would get applied alongside.
+
+So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database] (or even worse, adding a [MediaWiki-Core]).
+
+The added benefit is that all extensions and other projects will get to use core's general tags like database or javascript for tagging their bugs too.",1418336894,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),Can we just rename #mediawiki-general-or-unknown to #MediaWiki?,1418336760,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),[Project organization needs to primarily work for the project owners and Quim explained above the difference. Feel free to search for items under both the Phabricator and Phabricator.org if you are looking for Phab specific tasks.],1418302543,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> ""Phabricator.org"" project is for upstream requests, and this is clearly not one.
+
+Debatable, but that debate is happening on other reports. Feel free to create another Phabricator subproject for issues with the phabricator.wikimedia.org instance that don't fit your definition of ""specific features and configuration in our instance"".",1418288279,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> ""Phabricator.org"" project is for upstream requests, and this is clearly not one.
+
+Debatable, but that debate is happening on other reports. Feel free to create another Phabricator subprojects for issues with the phabricator.wikimedia.org instance that don't fit your definition of ""specific features and configuration in our instance"".",1418288265,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"For what is worth...
+
+""Phabricator.org"" project is for upstream requests, and this is clearly not one.
+
+""Phabricator"" project is for specific features and configuration in our instance. I personally think this is not one of these.
+
+""Project-Creators"" is a Phabricator related project to work on tasks related with the creation of projects, and I personally think that this is one of these.",1418287284,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),Please stop removing phabricator-related projects from phabricator-related reports. Searching tickets on this site is hard enough.,1418280960,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"I think a ""MediaWiki Core"" project distinct from the ""MediaWiki Core Team"" project is fine.  It might be a little confusing, but survivable.",1418260891,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"PS: ah, now I understand the confusion. I typed `#MediaWiki-Core` which is an additional hashtag of MediaWiki-General-or-Unknown. Sorry for the confusion. I'll edit my original comment.",1417946902,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#823768, @Nemo_bis wrote:
+> Why did you remove the Phabricator project?
+
+Because I don't think the legit problem you are reporting should be solved with a new Phabricator feature, but with the topols we have. 
+
+> This has nothing to do with MediaWiki code.
+
+This is a problem that the #MediaWiki-Core-Team should be aware of, and the solution agreed should work for them in the first place. 
+
+
+> Creating a new project for all MediaWiki core tasks is definitely overkill. 
+
+In my opinion, developing a local Phabricator application to solve this probles is an overkill.
+
+> Also, reusing the MediaWiki-General-or-Unknown name for such a new project is out of question, because we would then be unable to tell ""General/Unknown"" tasks from the others.
+
+Indeed. This is why in my proposal I didn't touch it.
+
+> Lower cost alternatives:
+> 1) a local phabricator application allowing us to do regex search against projects;
+> 2) a local phabricator application which, in the search form, expands a literal ""MediaWiki-*"" to a list of all MediaWiki core projects;
+
+I don't see the lower cost in these proposals. They are far more expensive to develop and maintain.
+
+> 3) a saved search across all MediaWiki core projects, maintained by the bugwrangler and prominently linked by all phabricator search forms.
+
+That would be low cost indeed. If this is a good solution, then this is all we need.",1417946769,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Why did you remove the Phabricator project? This has nothing to do with MediaWiki code.
+
+Creating a new project for all MediaWiki core tasks is definitely overkill. Also, reusing the MediaWiki-General-or-Unknown name for such a new project is out of question, because we would then be unable to tell ""General/Unknown"" tasks from the others. Lower cost alternatives:
+1) a local phabricator application allowing us to do regex search against projects;
+2) a local phabricator application which, in the search form, expands a literal ""MediaWiki-*"" to a list of all MediaWiki core projects;
+3) a saved search across all MediaWiki core projects, maintained by the bugwrangler and prominently linked by all phabricator search forms.",1417941666,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Why did you remove the Phabricator project? This has nothing to do with MediaWiki code.
+
+Creating another project for all MediaWiki core tasks is definitely overkill. Also, reusing MediaWiki-General-or-Unknown is out of question, because we would then be unable to tell ""General/Unknown"" tasks from the others. Lower cost alternatives:
+1) a local phabricator application allowing us to do regex search against projects;
+2) a local phabricator application which, in the search form, expands a literal ""MediaWiki-*"" to a list of all MediaWiki core projects;
+3) a saved search across all MediaWiki core projects, maintained by the bugwrangler and prominently linked by all phabricator search forms.",1417941627,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"A possible solution:
+
+* Create `#MediaWiki-Core` as a project umbrella (we could even consider the use of the 'umbrella' icon, still with violet background)
+* Batch edit all the tasks in all the MediaWiki Core subprojects and associate `#Media-Core` to them.
+* Create a Herald rule consisting in adding `#MediaWiki-Core` automatically to any task associated with any of the subprojects.
+
+I'm not sure whether this is an overkill or not, but it is very likely that @Nemo_bis is not the only person willing to perform queries across MediaWiki Core components.",1417946933,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"A possible solution:
+
+* Create #MediaWiki-Core as a project umbrella (we could even consider the use of the 'umbrella' icon, still with violet background)
+* Batch edit all the tasks in all the MediaWiki Core subprojects and associate #Media-Core to them.
+* Create a Herald rule consisting in adding #MediaWiki-Core automatically to any task associated with any of the subprojects.
+
+I'm not sure whether this is an overkill or not, but it is very likely that @Nemo_bis is not the only person willing to perform queries across MediaWiki Core components.",1417875650,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"Please split off a #Browser-Support-Opera-12 project from #Browser-Support-Opera. The Presto-based ""classic"" Opera 12.xx (and previous versions) is a completely different browser from the Chromium-based ""new"" Opera 15.xx (and later versions, currently at 26), having completely different and completely unrelated bugs. (There was no desktop Opera 13 or 14.)
+
+Most of the existing bugs under this project seem to be about Opera 12, but new reports are mostly about Opera 15+. I'll be happy to re-triage them (getting the bulk task change permission would probably help).",1417373028,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kozwn3k45tsayt7lttoe,task_description,declined
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,Meh.,1421877681,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"@matmarex: See my questions in T76302#796189 (first part before I unfortunately answered the braoder part).
+We talk about 15 open tickets in total for Opera, and currently I don't want specific projects for versions of one browser (like MSIE-10, MSIE-11 etc). I think 15 tickets is small enough (and in theory, priority could be decreased for ancient Opera codebases), and I don't think that adding more projects to differentiate makes more people use the browser-support tags that we already have. I'm afraid of tagging for the sake of tagging.",1421779333,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"@Aklapper, @Krinkle, After reading your comments, I have no strong argument myself to keep/archive these browser tags.",1417514135,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,">>! In T76302#795544, @Qgil wrote:
+> I guess at least the #Mobile-Web team will find these browser specific tags useful, and I have also seen many VisualEditor bugs being specific to i.e. Firefox.
+
+I'm not questioning the usefulness of a bug report detailing its relation to a specific browser. I'm questioning the use in maintaining tags for them. What would be the added value over simply stating it in the title or description (like we do for the other aspects of a bug, e.g. the page, class, country, user group etc.). Sure it matters, but every other aspect of a task name/description matters too. Is it useful to add tags? Have we used these for queries in the past?
+
+>>! In T76302#796188, @Aklapper wrote:
+> 
+>>>! In T76302#795501, @Krinkle wrote:
+>> We should've dropped this
+> 
+> (..) no information should ever be lost when migrating. (..)
+
+They could've been converted the same way we did ""Severity"", ""Version"" and ""See also"". Simply appended to the bug report (which probably mentions it already in the description and/or title).
+",1417503821,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"There are 15 open tasks with the Opera project tag set so should not be too hard to (re)triage. 
+Do you really also care about closed ones, or about Opera 12 bugs? (Basically: Is this information of any real value or are we just categorizing for the sake of categorizing.)
+
+>>! In T76302#795501, @Krinkle wrote:
+> We should've dropped this
+
+Your ""we"" is not the ""we"" of those folks who had and have a strong opinion that no information should ever be lost when migrating. In any case we could still always archive projects in Phab if we wanted.
+
+
+
+>>! In T76302#795544, @Qgil wrote:
+> I guess at least the #Mobile-Web team will find these browser specific tags useful
+
+At least when it came to the ""Mobile Platform"" field in Bugzilla, it was set zero times in the last 12 months by a mobile team. I can imagine that the absolute number isn't too different for the ""Web browser"" field though I haven't checked.
+
+> A rename might help using them for the purpose they were created. For instance, what about #Opera-Specific, #Firefox-Specific...
+
+That would have been a really good idea for Bugzilla where the ""Web browser"" field had a bug exposure. Now it's rather hidden as yet another project but I think I'd still go for #Opera-Browser-Specific etc.",1417435160,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"I guess at least the #Mobile-Web team will find these browser specific tags useful, and I have also seen many VisualEditor bugs being specific to i.e. Firefox.
+
+A rename might help using them for the purpose they were created. For instance, what about #Opera-Specific, #Firefox-Specific...
+",1417376275,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,I think tagging tasks with Browser-Support at all is a wasted effort. We should've dropped this like we dropped the other fields from BugZilla (and imported as plain text in the description).,1417373914,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"This is a huge problem for test automation.
+
+- open any page in VisualEditor
+- toolbar tools are located in `<div class=""oo-ui-toolbar-tools"">`
+- as far as I can see, there is no unique way to access a tool in the toolbar (example: click Insert tool)
+- all of them share the same classes, and none of them have unique attributes, like `id`
+- the only thing that is different is the string (Cite, Insert...), but since it changes when the UI language changes, it is not usable for us
+- our test automation breaks all the time because elements in the toolbar move around, and the workarounds that we have at the moment are all fragile
+- the best solution for us would be if every tool in the toolbar (undo, redo, paragraph...) had an unique id
+- unique classes (or any other attribute, as long as it is unique) would work for us
+- if there is an attribute used for translations, it would work for us, as long as each tool has and unique attribute
+- this is not just a problem in toolbar, but let's start somewhere",1417094720,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-2rcyzuif3kfiujpetxoz,task_description,resolved
+Tools in the toolbar do not have unique attributes,"Change 174666 merged by jenkins-bot:
+Add classes to toolbar UI elements
+
+[[https://gerrit.wikimedia.org/r/174666]]",1420574566,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#932189, @Esanders wrote:
+> Thanks Amir. On a separate issue - would you be able to work with a JS API in this case, so we know if it's worth implementing?
+
+This is probably a question for @zeljkofilipin. For the sake of language screenshots and testing in general it must be something that will work with Ruby and Selenium, and Zeljko is a far bigger expert in this than I am.",1418937647,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"Thanks Amir. On a separate issue - would you be able to work with a JS API in this case, so we know if it's worth implementing?",1418900427,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"I updated the patch. Now it adds classes only to elements that cannot be found in the DOM by Selenium in any other way. Incidentally, all of these are elements that are identified by a text label, rather than an icon. Where as icons have classes that are the same in all languages, the labels are different everywhere.
+
+I think that the current version of https://gerrit.wikimedia.org/r/#/c/174666/ (Patch set 15) addresses all the comments above.",1418898708,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"A 'better API' in this case would probably be giving groups unique symbolic names, then they could be accessed via 
+```
+ve.init.target.getToolbar().getGroup( 'structure' )
+```
+for example.",1418056141,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"The problem with letting people use these classes for gadgets is they then become an undocumented API. Trevor's point about greppability is that I should be able to see a class in the code and search for it to find out who uses it and what for, this is why we add comments when classes are built dynamically. API's for gadgets should be provided directly via JavaScript, not classnames/ID. ve-test-* obviously smells - but it is clear what it does and obvious what needs to be replaced when we come up with a better API for this particular task.",1418056038,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"I expected that the names that I gave may have to be changed. I'm generally fine with any naming scheme. If everybody is sure that these things are useful for nothing but testing then it can be ve-test-*. I can imagine that these classes can also be useful for community-developed gadgets that do Stuff with the toolbar; there were similar gadgets for WikiEditor. Also, it's kinda odd to have a class with ""test"" in it in usual production version, but that isn't a disaster either.",1417794562,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"I think there is no risk in adding a couple of strings causing any noticeable performance problem. However, if this is how we are going to target things, than I can see this becoming a very common thing, and it won't be a couple of strings, it will be a ton of them.
+
+My worry isn't even that it's ""bloat"" as much as cruft. If the classes are for testing only, then ideally we can namespace them as such. not only is ""ve-ui-TargetToolbar-insert"" not following the lowerCamelCase naming convention, but it's misleading that it's a class used for styling the ve.ui.TargetToolbar's insert object, rather than targeting it for testing.
+
+I recommend we better quarantine such added classes, such that they are easy to grep for later on, should we come up with a less ""duct tape"" approach. Perhaps you could namespace testing classes as ""ve-test"" and describe the actual thing being tested with the class name, such as ""ve-test-insertToolGroup""?",1417726988,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#794364, @Jdforrester-WMF wrote:
+> If you want robust tests, agree to my request to have the browser tests block merge. :-) Right now the tests are a basket case because they don't need to pass in master, which means they often don't. The responsibility for testing software should be with the team building it, and when they break a test they should also fix it. By having browser tests not block merge, they're just out-of-band chaff.
+
+Amen. It would mean some serious work on the tests, but I think this is the only way to go forward. I am not sure I have ever voted -1 when we were talking about making browser tests voting, but my memory could be failing me.
+
+> And I find it hard to believe that I still have to argue that we should have more rigorous testing, rather than a series of hacks. :-(
+
+I am not sure what you mean here.",1417293517,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#793969, @Jdforrester-WMF wrote:
+> Also, if this is a requirement, it should be made in OOUI which ships the toolbar code, not hacked in by one of its clients. Adding the request to the OOUI project.
+
+As far as I am concerned, this is a requirement. Amir and I did the best we could be we were pretty sure we did it wrong. Thanks for letting us know where this belongs to.",1417293154,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#794185, @zeljkofilipin wrote:
+>>>! In T76143#793969, @Jdforrester-WMF wrote:
+>> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+> 
+> This is not about testing //more easily//, this is about having robust test automation. At the moment, our test automation is made up of cardboard and duct tape.
+
+If you want robust tests, agree to my request to have the browser tests block merge. :-) Right now the tests are a basket case because they don't need to pass in master, which means they often don't. The responsibility for testing software should be with the team building it, and when they break a test they should also fix it. By having browser tests not block merge, they're just out-of-band chaff.
+
+>>! In T76143#794289, @zeljkofilipin wrote:
+>>>! In T76143#793969, @Jdforrester-WMF wrote:
+>> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+> 
+> I find it hard to believe that we still have to fight for testability in 2014. If VisualEditor team does not care about it, I give up on test automation of VisualEditor.
+
+And I find it hard to believe that I still have to argue that we should have more rigorous testing, rather than a series of hacks. :-(",1417282502,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#793969, @Jdforrester-WMF wrote:
+> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+
+Do you have any data on how much memory/etc. would be taken by adding a few strings to the page?
+",1417274523,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#793969, @Jdforrester-WMF wrote:
+> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+
+I find it hard to believe that we still have to fight for testability in 2014. If VisualEditor team does not care about it, I give up on test automation of VisualEditor.
+",1417274041,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#793969, @Jdforrester-WMF wrote:
+> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+
+This is not about testing //more easily//, this is about having robust test automation. At the moment, our test automation is made up of cardboard and duct tape.
+
+",1417254153,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily… Also, if this is a requirement, it should be made in OOUI which ships the toolbar code, not hacked in by one of its clients. Adding the request to the OOUI project.",1417228637,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"The above patch adds class `ve-ui-TargetToolbar-insert` to the Insert element. Something like this is all we need so far, if VisualEditor team thinks this is the way to go.
+
+Before:
+
+```
+<div class=""oo-ui-widget oo-ui-widget-enabled oo-ui-toolGroup oo-ui-indicatorElement oo-ui-labelElement oo-ui-popupToolGroup oo-ui-listToolGroup"">
+```
+
+After:
+
+```
+<div class=""ve-ui-TargetToolbar-insert oo-ui-widget oo-ui-widget-enabled oo-ui-toolGroup oo-ui-indicatorElement oo-ui-labelElement oo-ui-popupToolGroup oo-ui-listToolGroup"">
+```
+
+Tested in MediaWiki-Vagrant virtual machine with VisualEditor role enabled.",1417096989,PHID-USER-fz7hkyvt4jypl76ieyol,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"Change 174666 had a related patch set uploaded (by Zfilipin):
+WIP: Add a class to the toolbar button
+
+[[https://gerrit.wikimedia.org/r/174666]]
+
+#patch-for-review",1417094774,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+VisualEditor: Insert media dialog appears to immediately abort request,"In test2 and production(betalabs does not display the error).
+
+In VE, open any page for Edit and insert Media - ""Uncaught TypeError: undefined is not a function"" is immediately displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1415381700,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_description,resolved
+VisualEditor: Insert media dialog appears to immediately abort request,"The original issue was never reproduced, and the follow-up discussion about immediately aborted requests was apparently addressed in 2015, in {5d8108f229b8a284fc02b29e509bba39bd2142a0}.",1644536360,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_subcomment,NA
+VisualEditor: Insert media dialog appears to immediately abort request,"(In reply to Roan Kattouw from comment #2)
+> Elena showed me that if you open the media dialog on a new page after typing
+> some text and going to a new paragraph, the usual jQuery JSONP abort error
+> thing happens, and it consistently happens every time you open the dialog.
+> This probably means we are sending a request and then immediately aborting
+> it.
+
+We are immediately sending a request every time the search input is changed. In the case of opening the insert dialog, the search input should get the page title, so a request is immediately sent with that. If the request is sent and is immediately aborted even if no other detail was changed (so, if you didn't change the search input at all) then maybe there's an issue with the way the input is updated. But then, the search appears, so the request doesn't seem to be cancelled immediately.
+
+I'm not entirely sure what goes on there with the JSONP failures, but if this is about cancelling requests before they're done, I'm not entirely sure we can do anything about it -- requests are sent when the input is changed, which means that when the user types, we send each request on keystroke. If you're writing a whole word of 5 letters, then you'll get 4 cancelled requests and 1 completed one.
+
+Changing this behavior would mean adding some ""search"" button to do the search on click rather than instantaneously on keystroke, and that's not the behavior we want.",1415390018,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_subcomment,NA
+VisualEditor: Insert media dialog appears to immediately abort request,"Elena showed me that if you open the media dialog on a new page after typing some text and going to a new paragraph, the usual jQuery JSONP abort error thing happens, and it consistently happens every time you open the dialog. This probably means we are sending a request and then immediately aborting it.",1415389734,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_subcomment,NA
+VisualEditor: Insert media dialog appears to immediately abort request,"Works fine for me in production (enwiki), test2 and beta labs.",1415383213,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Change https://gerrit.wikimedia.org/r/#/c/171326/ shouldn't have to trigger bundle-rubocop.
+
+Affects at least mediawiki-extensions-VisualEditor and oojs-ui repos, probably more. ",1415276340,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-wcav44bst4bw55h5vacr,task_description,resolved
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,Confirmed that Rubocop still runs on //e.g.// https://gerrit.wikimedia.org/r/187166 which has a Ruby file.,1422672991,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Change 187805 merged by jenkins-bot:
+rubocop: Run *-bundle-rubocop only if relevant files were modified
+
+[[https://gerrit.wikimedia.org/r/187805]]",1422672389,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Change 187805 had a related patch set uploaded (by Krinkle):
+rubocop: Run *-bundle-rubocop only if relevant files were modified
+
+[[https://gerrit.wikimedia.org/r/187805]]
+
+#patch-for-review",1422652099,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Unassigning myself, I am not working on it.",1415803868,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Seems we should only trigger it when .rubocop.* or .rb files are changed.
+
+In Zuul something like:
+
+jobs:
+ - name: '^.*-rubocop$'
+   files: '(^\.rubocop\..*|.*\.rb$)'
+
+The same files: statement would have to be added to any other rubocop jobs defined as non voting in the jobs section. Ie:
+
+  - name: mediawiki-core-bundle-rubocop
+    voting: false
++   files: '(^\.rubocop\..*|.*\.rb$)'",1415614370,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+VisualEditor: Tool to set/unset background colour,"For completion.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1415217780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kv3qzdtcovilhit5wojg,task_description,open
+"VisualEditor: In the transclusion dialog, show the non-normalised parameter name if available?","Per bug 67657, there's now key.wt going to be available in the Parsoid output; if so, we should show that, not the key name, so that ""foo<!--OMG!-->bar"" is shown as ""foobar"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1414694340,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jx334o6lve2gveakyge4,task_description,open
+"VisualEditor: In the transclusion dialog, show the non-normalised parameter name if available?","Aha, yes.
+
+Still, the comment might be important in some rare cases…",1414694625,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-jx334o6lve2gveakyge4,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, show the non-normalised parameter name if available?","I think it's the other way around: Now the same code would show ""foobar"", and if you want to display ""foo<!--OMG!-->bar"" you'd need to use key.wt.",1414694500,PHID-USER-56wtmb23orq4pu5liyj5,PHID-TASK-jx334o6lve2gveakyge4,task_subcomment,NA
+VisualEditor: Provide a way to move pages through interacting with the displayed title,"An often encountered hurdle for new editors is that they can't find out how to move a page. Generally they ask how to ""change the title"". Apparently - and understandably - in their mental model, the title of a page is part of the page. It would be nice if VE could accommodate that model. For that I suggest
+* Make the page title editable
+* If the new page title is a valid title, move the page to that location
+** If the move fails, notify of the failure to automatically change the title, and link to the documentation of the move functionality, suggesting to do it manually.
+* If the new page title isn't a valid title, insert a {{DISPLAYTITLE}} element to the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414573980,PHID-USER-n27daagbl3wqf3ghr4nk,PHID-TASK-2wlcma4q7b3q3yusckvl,task_description,open
+VisualEditor: Provide a way to move pages through interacting with the displayed title,"This is a perennial request from inexperienced editors.  See, e.g., https://www.mediawiki.org/wiki/Topic:Uuooxecko4mfmnia ",1550858386,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-2wlcma4q7b3q3yusckvl,task_subcomment,NA
+VisualEditor: Provide a way to move pages through interacting with the displayed title,"Hmm. I like this idea. Could get a bit complicated where ""sometimes"" it is moving the page, and ""sometimes"" it's setting the {{DISPLAYTITLE}}, and it's not clear which is which.
+
+Also, moving mid-edit might be complicated on the back-end? MW relies on the title of a page /way/ too much. Something to watch for when we implement.",1414600396,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2wlcma4q7b3q3yusckvl,task_subcomment,NA
+VisualEditor: Inserted images overlap preformatted text box,"images overlap preformatted text box
+
+Betalabs - desktop and mobile
+
+Steps to reproduce: 
+
+1. In VE insert preformatted text 
+2. Insert an image  - observe that the image will be overlapping the preformatted text. 
+
+The two screenshots are attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14713}",1414024200,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3wq7rvzz7yhgz4hc5nya,task_description,declined
+VisualEditor: Inserted images overlap preformatted text box,"At the moment, <pre> blocks and images overlap in the read version of pages too, so we're correct to show the same thing in VisualEditor. I'm declining this; we can file a broader bug if we want to change how the read version looks.",1437696770,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-3wq7rvzz7yhgz4hc5nya,task_subcomment,NA
+VisualEditor: Inserted images overlap preformatted text box,"Created attachment 16892
+desktop - image overlap preformatted area
+
+Added attachment - VE_desktop_images overlapping preformatted text- that displays the issue clearer.
+
+**Attached**: {F14714}",1414186852,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-3wq7rvzz7yhgz4hc5nya,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,"For the very few GCNs that generate wiki-link links (class=new etc.).
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1412891220,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2eygkjsu6uashwjrsks,task_description,resolved
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,"Change 345607 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWSaveDialog: Run links through a render function for preview & visual diff
+
+[[https://gerrit.wikimedia.org/r/345607]]
+",1491060129,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,">>! In T73900#3146112, @Esanders wrote:
+> What did you mean by non-template GCN? Extension nodes?
+
+Yes.",1491059495,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,"Change 345607 had a related patch set uploaded (by Esanders; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] MWSaveDialog: Run links through a render function for preview & visual diff
+
+[[https://gerrit.wikimedia.org/r/345607]]
+",1490954038,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,What did you mean by non-template GCN? Extension nodes?,1490952931,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,(Uploaded Gerrit change 167249 for that),1413571914,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,Yeah. More with bug 65353 really,1413570393,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,"In the top template at https://it.wikipedia.org/wiki/Korova_Milk_Bar?veaction=edit ""migliorare questa voce"", which leads to https://it.wikipedia.org/w/index.php?title=Korova_Milk_Bar&action=edit , shows up as red. This is related to this bug, I guess?",1413566926,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Proposed external links should be validated before being created,"Open the link inspector and just type in double slash(forward), click done.It gets inserted in the CE as an external link.
+The external links should be validated for correct format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412776440,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3ojjmktdxwslnqst6zf3,task_description,open
+VisualEditor: Proposed external links should be validated before being created,"I raised this  ticket, because i thought there should be some sort of client-side validation for external link entries.What I mean is, when i type in a ""//"" or ""//foo"" then even the  external link icon should not get inserted to the page. Right now it is only after saving the page,you would see that ""//"" is saved as a text and not a link.",1412960452,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3ojjmktdxwslnqst6zf3,task_subcomment,NA
+VisualEditor: Proposed external links should be validated before being created,"(In reply to Ritu Swain from comment #2)
+> it could follow the HTTP URL syntax.
+
+What is that syntax? What about other protocols? How to define what's ""valid"" without excluding other valid URLs?",1412808976,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3ojjmktdxwslnqst6zf3,task_subcomment,NA
+VisualEditor: Proposed external links should be validated before being created,"(In reply to Andre Klapper from comment #1)
+> [Problem is unrelated to specific browsers hence removing 'Web browser'
+> field entry. ""should be"" -> new feature, hence setting 'Severity' to
+> 'enhancement'.]
+> 
+> (In reply to Ritu Swain from comment #0)
+> > The external links should be validated for correct format.
+> 
+> Do you have any definition (or even regular expression) in mind for ""correct
+> format""?
+> it could follow the HTTP URL syntax.But right now anything that has a double slash(""//"" or ""//foo"") is taken as an external link.",1412793003,PHID-USER-ndwodmhxnp2vypdesdns,PHID-TASK-3ojjmktdxwslnqst6zf3,task_subcomment,NA
+VisualEditor: Proposed external links should be validated before being created,"[Problem is unrelated to specific browsers hence removing 'Web browser' field entry. ""should be"" -> new feature, hence setting 'Severity' to 'enhancement'.]
+
+(In reply to Ritu Swain from comment #0)
+> The external links should be validated for correct format.
+
+Do you have any definition (or even regular expression) in mind for ""correct format""?
+*If* the scope of the link inspector is supposed to support URIs as per http://www.ietf.org/rfc/rfc3986.txt this could become complex...",1412785907,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-3ojjmktdxwslnqst6zf3,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"This suggestion comes from Gebruiker:Stratoprutser at nl.wp.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412346900,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_description,open
+VisualEditor: Make it easier to see that there is an option to paste as plain text,">>! In T73612#3588103, @Prtksxna wrote:
+> Has this come up as a problem again?
+
+There was some confusion about a similar problem (see T174898), but this specific problem hasn't come up. I'm changing priority to reflect the state of things here.",1505130706,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,">>! In T73612#775328, @Jdforrester-WMF wrote:
+> …so although we could add a ""paste unformatted"" button it would feel very odd…
+
+Where do you think this would make sense? Within the //Insert// menu? One option could be to add it in the right click context menu, but I am sure hijacking that will come with problems of its own.
+
+
+
+
+>>! In T73612#775330, @Jdforrester-WMF wrote:
+> If you couldn't find it then probably others couldn't either; we should keep this open until we come up with a good way to expose this.
+
+
+Has this come up as a problem again?
+",1504790189,PHID-USER-gc5hdyw5p4np7atqjynz,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"(In reply to Stratoprutser from comment #4)
+> ok my bad, thanks for the follow-up, closing
+
+If you couldn't find it then probably others couldn't either; we should keep this open until we come up with a good way to expose this.",1412365144,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"**m8r-0p6s0d** wrote:
+
+ok my bad, thanks for the follow-up, closing",1412363214,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"(In reply to Stratoprutser from comment #2)
+> Ah! In Firefox ctrl shift v opens Ad blocks' blockable items dialog, but
+> disabling adblocker indeed pastes unformated.
+> 
+> Not sure if it needs a button or an entry under ""Insert"", but its always
+> nice to have such a hidden feature somewhere exposed?
+
+If you click on the help icon, then ""keyboard shortcuts"" (""Tastaturkürzel"" in German), it is listed there along with the other standard shortcut commands. Unfortunately browsers will not let us provide cut/copy/paste buttons, so although we could add a ""paste unformatted"" button it would feel very odd…",1412362633,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"**m8r-0p6s0d** wrote:
+
+Ah! In Firefox ctrl shift v opens Ad blocks' blockable items dialog, but disabling adblocker indeed pastes unformated.
+
+Not sure if it needs a button or an entry under ""Insert"", but its always nice to have such a hidden feature somewhere exposed?",1412358966,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"This is already available via the standard shortcut (Ctrl/Cmd+Shift+V), and it's listed in the dialog of all keyboard shortcuts.
+
+Is this asking for a button to do this as well?",1412354396,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Be able to make block-level items centred (and other styles),"A fr.wp editor uses centered lists in his sandbox, https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Brouillon#Le_spectacle  (diff:  https://fr.wikipedia.org/w/index.php?diff=107080711&oldid=107080641 ).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409997000,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-bg7mho6ovlk6kuy4oasm,task_description,open
+VisualEditor: Be able to make block-level items centred (and other styles),"I don’t know what was the original issue, but currently, bullets points are kept left because of unexpected list item wrapping in paragraphs (T92441).",1643596968,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-bg7mho6ovlk6kuy4oasm,task_subcomment,NA
+VisualEditor:  Be able to search for an existing image by name,"Sometimes you know the name of an image, but need to be able to find it on a large page.  It would be convenient if searching (with Command-F or Control-F) could find the image this way.",1409542680,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-aanfzw3dbp4of5eqkf3w,task_description,open
+VisualEditor:  Be able to search for an existing image by name,"If we did this, we would need to highlight the matching text. We could do that by popping open the inspector which contains the matching file name and highlighting inside it. We'd still have to handle the common case of words which don't appear in an inspector because the title is too long, though.
+
+Somewhat similar to T103286.",1437699411,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-aanfzw3dbp4of5eqkf3w,task_subcomment,NA
+VisualEditor:  Be able to search for an existing image by name,"If we did this, we would need to highlight the matching text. We could do that by popping open the inspector which contains the matching file name and highlighting inside it.
+
+Somewhat similar to T103286.",1437699249,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-aanfzw3dbp4of5eqkf3w,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","Hello. As discussed in [[https://it.wikipedia.org/wiki/Discussioni_MediaWiki:Visualeditor-ca-editsource | :it:Discussioni_MediaWiki:Visualeditor-ca-editsource ]] we'd need a way to get the same editing labels of en.wiki (in italian, obviously), that are ""Edit"", ""Edit source"" and ""Edit beta"":
+
+* When VE is disabled by user, show these labels: ""EDIT"" (for wikitext)
+* When VE is enabled, show these labels: ""EDIT SOURCE"" (for wikitext), ""EDIT BETA"" (for VE)
+
+Now on it.wiki there are ""Modifica sorgente"" (edit source) for the classic edit when VE is off and ""Modifica"" (edit) both for the VE edit and for the classic edit when VE is enabled. There's a way to have three different labels to change according to the consensus that emerged?
+
+Thanks,
+Horcrux92
+
+P.S. Sorry for the probably erroneous categorization.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409484180,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_description,open
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034842, @Aklapper wrote:
+> It was difficult to understand because I assumed you want to potentially display three labels. Initial description wasn't entirely clear. Alright then, thanks for clarifying and your patience :)
+
+Thank to you.
+My probable guilt is I haven't got a very wide english lexicon, so the repetitions in the sentences may be confusing.",1423770458,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","It was difficult to understand because I assumed you want to potentially display three labels. Initial description wasn't entirely clear. Alright then, thanks for clarifying and your patience :)",1423768352,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034779, @Aklapper wrote:
+> Sorry but I'm getting lost here (plus I don't know implementation details as I'm not a developer). 
+> 
+> Could you please edit the task description here and finish these two sentences:
+> * When VE is off: Show these labels in this order: ...
+> * When VE is on, show these labels in this order: ...
+> plus for the case of just displaying ""Edit"", please also explain what ""Edit"" would do (either wikitext or VE).
+> That might things less confusing here. Sorry. :-/
+
+Maybe I should give up...
+
+* When VE is disabled by user, show these labels: EDIT
+* When VE is enabled, show these labels: EDIT SOURCE, EDIT BETA
+EDIT would open the classic edit mode, that is the wikitext editing (ovviously, since VE is disabled).
+
+The labels' names are indicative (they would be editable in the MediaWiki namespace) and I don't care about the order.
+
+Why it is so difficult to understand? It would be the <u>same</u> setting of en.wiki.",1423767505,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034779, @Aklapper wrote:
+> Sorry but I'm getting lost here (plus I don't know implementation details as I'm not a developer). 
+> 
+> Could you please edit the task description here and finish these two sentences:
+> * When VE is off: Show these labels in this order: ...
+> * When VE is on, show these labels in this order: ...
+> plus for the case of just displaying ""Edit"", please also explain what ""Edit"" would do (either wikitext or VE).
+> That might things less confusing here. Sorry. :-/
+
+Maybe I should give up...
+
+* When VE is disabled by user, show these labels: EDIT
+* When VE is enabled, show these labels: EDIT SOURCE, EDIT BETA
+EDIT would open the classic edit mode (wikitext editing).
+
+The labels' names are indicative (they would be editable in the MediaWiki namespace) and I don't care about the order (ovviously, since VE is disabled).
+
+Why it is so difficult to understand? It would be the <u>same</u> setting of en.wiki.",1423767455,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034779, @Aklapper wrote:
+> Sorry but I'm getting lost here (plus I don't know implementation details as I'm not a developer). 
+> 
+> Could you please edit the task description here and finish these two sentences:
+> * When VE is off: Show these labels in this order: ...
+> * When VE is on, show these labels in this order: ...
+> plus for the case of just displaying ""Edit"", please also explain what ""Edit"" would do (either wikitext or VE).
+> That might things less confusing here. Sorry. :-/
+
+Maybe I should give up...
+
+* When VE is disabled by user, show these labels: EDIT
+* When VE is enabled, show these labels: EDIT SOURCE, EDIT BETA
+EDIT would open the classic edit mode (wikitext editing).
+
+The labels' names are indicative (they would be editable in the MediaWiki namespace) and I don't care about the order.
+
+Why it is so difficult to understand? It would be the <u>same</u> setting of en.wiki.",1423767371,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","Sorry but I'm getting lost here (plus I don't know implementation details as I'm not a developer). 
+
+Could you please edit the task description here and finish these two sentences:
+* When VE is off: Show these labels in this order: ...
+* When VE is on, show these labels in this order: ...
+plus for the case of just displaying ""Edit"", please also explain what ""Edit"" would do (either wikitext or VE).
+That might things less confusing here. Sorry. :-/",1423766823,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034429, @Aklapper wrote:
+>>>! In T72230#1034061, @Horcrux92 wrote:
+>> Because ""edit"" is ambiguous.
+> 
+> If that's ambiguous then why request three labels, instead of two that are not ambiguous (classic wikitext editing, VE editing)?
+
+The third one would appear when VE is off and must be independent from the other two (like on en.wiki).
+
+Instead of quote only four words, I please you to try to answer to my two questions.",1423758786,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034429, @Aklapper wrote:
+>>>! In T72230#1034061, @Horcrux92 wrote:
+>> Because ""edit"" is ambiguous.
+> 
+> If that's ambiguous then why request three labels, instead of two that are not ambiguous (classic wikitext editing, VE editing)?
+
+The third one would appear when VE is off and must be independent from the other two (like on en.wiki).
+
+Instead of quote only four words, try to answer to my two questions.",1423758745,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034061, @Horcrux92 wrote:
+> Because ""edit"" is ambiguous.
+
+If that's ambiguous then why request three labels, instead of two that are not ambiguous (classic wikitext editing, VE editing)?",1423757892,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","Because ""edit"" is ambiguous. Why the basic ""edit"" should be the VE-mode?
+
+We discussed it a lot (as can you see in the page that I linked in the first post) and we'd like to be able to put into practice our decisions.
+
+The real question I'd like to make is: why on en.wiki it's possible to have three distinct labels (two for VE-mode on and one for VE-mode off) and on it.wiki it is not?",1423747546,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1033724, @Horcrux92 wrote:
+> The problem is that we cannot turn the label ""Edit"" in ""Vidual edit"" without changing the same label for who has got VE off.
+
+I understand that part, but why do you want to turn ""Edit"" into ""Visual edit""? The intention behind this would be welcome and why you think that it's not more confusing.",1423744234,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","The problem is that we cannot turn the label ""Edit"" in ""Vidual edit"" without changing the same label for who has got VE off.
+
+For us this is a problem, maybe not to big but I thought you would have been able to solve it.",1423735683,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","My question ""Which problem do you try to solve?"" is still unanswered though...",1423702519,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","(In reply to Andre Klapper from comment #1)
+> Hi,
+> what would ""Edit Beta"" do if you already have the two other buttons? 
+> Which problem do you try to solve? What's the URL to the discussion?
+
+https://it.wikipedia.org/wiki/Discussioni_MediaWiki:Visualeditor-ca-editsource
+
+We would like to:
+1) edit the label ""Modifica"" (edit) in ""Modifica visuale"" (visual edit) for the edit made with VE;
+2) edit the label ""Modifica sorgente"" (edit source) in ""Modifica"" (edit) for the classic edit (when VE is enabled);
+3) mantain the label ""Modifica"" for the classic edit (when VE is disabled);
+
+And, if I have correctly understood, the 1 and the 3 are impossible to do together, because both of them refer to MediaWiki:Visualeditor-ca-editsource.
+
+The same goes for the label [edit] near the section titles.
+
+If it can be useful, I forget to say that on en.wiki (as you may know) VE is disabled by default, while on it.wiki it's enabled by default.",1409493741,PHID-USER-vzowt52hw2qfnu2w3eim,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","Hi,
+what would ""Edit Beta"" do if you already have the two other buttons? 
+Which problem do you try to solve? What's the URL to the discussion?",1409490283,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+Allow setting all template parameters at once without having to pick which ones to enter,"A Wikipedia editor raised the following problem: When experienced Wikipedians want to add a template in the source editor, they can copy the template code without parameter values, which usually appears on template documentation pages, and then fill all the parameters one by one, and eventually delete the unneeded empty lines.
+
+In VE, parameters must be added one-by-one, and this feels less efficient. As the default behavior this may be OK, but there can be a button that shows all the available parameters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72083",1408434360,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-wia5kvwoexms6u3azcgb,task_description,open
+Allow setting all template parameters at once without having to pick which ones to enter,"How would this work? How does VisualEditor know that you wanted a field specified and left blank, vs. haven't set it?",1423675337,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wia5kvwoexms6u3azcgb,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","Lines starting with ; are not recognized as wikitext and just saved, only afterwards revealing their wikitext meaning:
+
+https://wikimania2014.wikimedia.org/w/index.php?title=User%3ADeryck_Chan%2FWMUK_report&diff=49488&oldid=49487
+
+Reported: https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/;caption
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1408359480,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_description,resolved
+"Entering "";"" does not trip the wikitext warning that it won't work","The current behavior in production: 
+;(semi-colon) triggers a warning ""Wikitext markup detected...""
+: (colon) adds <blockquote></blockquote>",1418257749,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","Indeed. This is intentional. Use of a "":"" to ""indent a paragraph"" (as multiple people who are wikitext experts have complained) is a sign that they're doing it wrong. :-) This is a much better outcome for editors – doing what they ""meant"" to do – and for readers.",1417542113,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","I don't think that's exactly correct:  the ; semi-colon and the : regular
+colon are supposed to create association lists (aka definition lists,
+because they're used for glossaries a lot).  I believe that a <blockquote>
+is a different thing.
+
+Whatamidoing (WMF)/Sherry Snyder
+Community Liaison
+Wikimedia Foundation, Inc.",1417539970,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work",Verified in beta and test2 - a semi-colon will trigger a wikitext warning; a colon(:)  - indicates a <blockquote> text.,1417467671,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","Change 175909 merged by jenkins-bot:
+Warn users who write ';' or ':' on a new line that it won't work
+
+[[https://gerrit.wikimedia.org/r/175909]]",1416966214,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","Change 175909 had a related patch set uploaded (by Jforrester):
+Warn users who write ';' or ':' on a new line that it won't work
+
+[[https://gerrit.wikimedia.org/r/175909]]
+
+#patch-for-review",1416964644,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"Goal:   
+
+* Add something to an existing citation that the template shouldn't include, like a {{verify credibility}} tag.
+* Assign a citation to a references group.
+
+
+Steps to reproduce:
+
+1.  Open a page containing a {{cite book}} template.
+2.  Click on the citation to edit it.
+3.  Think, ""Um, I don't actually want this ''in'' the template; I want this ''after'' the template.""
+4.  Give up.
+
+
+~~This can be done, if you happen to know that the thing to do is to select the ref, ignore the tag that pops up, go to the Cite menu, and choose Basic~~ (after Citoid replaced the old Cite menu, this is no longer possible).  But the ability to edit these refs would be more discoverable if the Cite Book dialog had a button at the bottom for ""Use reference editor"".
+",1407967980,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-j43eul4onpngbxmfr2sa,task_description,resolved
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"I'm going to call this resolved, per the previous comment:
+
+>>! In T71498#4868396, @matmarex wrote:
+> It is not exactly easy, but with that patch, it is at least possible again – you can open the ""basic"" reference dialog for citations using Edit → Replace reference → Manual → Basic form. See screenshots in T208981#4868393.
+
+Note that ""Replace reference"" has been renamed to ""Change reference type"" in the final version, but the behavior is otherwise the same.",1601427334,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"Change 483337 **merged** by jenkins-bot:
+[mediawiki/extensions/Citoid@master] Allow any reference to be replaced using Citoid
+
+https://gerrit.wikimedia.org/r/483337",1601391848,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"Change 483337 had a related patch set uploaded (by Esanders; owner: Bartosz Dziewoński):
+[mediawiki/extensions/Citoid@master] Allow any reference to be replaced using Citoid
+
+https://gerrit.wikimedia.org/r/483337",1600944169,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"It is not exactly easy, but with that patch, it is at least possible again – you can open the ""basic"" reference dialog for citations using Edit → Replace reference → Manual → Basic form. See screenshots in T208981#4868393.",1547095979,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"Change 483337 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/Citoid@master] Allow any reference to be replaced using Citoid
+
+[[https://gerrit.wikimedia.org/r/483337]]",1547095357,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,{T180104} looks related.,1510253140,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"MediaWiki: CSS/JS pages on any non-large wiki are usually a mess. Occasionally, we'll discover that wikis have been loading external resources for months and no one noticed. In addition, the local sysops maintaining those pages usually don't know JavaScript and are copy-pasting what someone else told them to do. Even when that's not the case, mistakes can result in code with [[https://szl.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.js&diff=prev&oldid=208782|obvious syntax errors]] being sent to readers for long periods of time.
+
+Various proposals have floated around over the years. The wikitech-l threads have some good discussion on some of the reasons why this is difficult for smaller wikis.
+* Wikitech-l:
+  * [[http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/74283|No longer allow gadgets to be turned on by default for all users on Wikimedia sites]] (specifically about Gadgets though)
+  * [[http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/79080/|Deployment targets and preferences (was: Superprotect user right, Comming to a wiki near you)]]
+* Wikimedia-l: 
+** [[http://thread.gmane.org/gmane.org.wikimedia.foundation/74166|Next steps regarding WMF<->community disputes about deployments]]
+** [[http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/79055/|Superprotect user right, Comming to a wiki near you]]
+
+**See Also**:
+* {T39230} (bug 37230)
+* {T53651} (bug 51651)
+* {T71550}
+* {T121470}
+* {T165981}
+* {T120886}
+* {T171563}",1407872640,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_description,open
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@DannyS712 @Xover
+It would seem that this proposed extension should just perform the functionality. This will likely require installation of Extension:FlaggedRevs or implementing a similar lightweight functionality for the new special page.
+As for handing merging, I propose using Special:MergeHistory to combine the specific revision approved for merge into the original page in MediaWiki namespace. Since this would lockout editing the mediawiki namespace pages, there would be less conflicts. This would retain the historical revision and edit summary in page history as attribution.  As for what happens to the forked page to user subpage, that's for the wiki community to handle as their policy.
+When forking, there should be some coordination to avoid edit conflicts or loss of code functionality. 
+ - Forking user is responsible for maintaining up to date with original page to avoid overwrite. if it does overwrite, previous revision should remain in page history.
+As for the rights based access issue 
+  - Handled by restricting access to the special page with a new user permission. 
+  - When a user who is allowed access to the special page, submits a fork or merge request, extension will check if the user has all these permissions: editinterface, editsitecss, editsitejs, editsitejson. Instead of relying on default usergroups [Interface Administrator], this would allow anyone to use the extension.
+
+ The big question for merging is do we want just the final version of the updated working code or all the subsequent trial & error historical revisions/edit summary?
+
+",1660423743,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#6496321, @DannyS712 wrote:
+> Quick idea version 2 for an extension + workflow
+
+Some quick ""diff"" proposals for your idea (below), with the caveat that I am not convinced this is the way to go.
+
+With the existence of a WMF Gitlab instance in this equation, I'm inclined to think the vast majority of this task's scope should be implemented there, and then it is how to connect the wiki side to the off-wiki (i.e. Gitlab) process that is the main problem. For example, being able to have decision artefacts //on wiki//, holding discussions //on wiki//, and seeing changes in the //on wiki// watchlist. We need some way to gain the other stuff without losing those bits (because they are critical to the long tail of contributors who will never visit Gitlab and have no clue what it is).
+
+>  # User wants to fork a script or gadget to propose a change
+>  #* !!User visits Special:ForkCode, says what the source page is and what the target page is!!
+
+""User selects the //Fork// option in the page actions menu, right next to the //Move// option. The page contents is copied to the same base page name as a subpage of that user's user page. If there is an existing page it is overwritten and there is no option to choose a different name (but the forking can always be done manually as before). A //page property/special MCR slot/ad hoc edit summary syntax// gives the source page for both attribution and subsequent merging reasons.""
+
+It could still be implemented as a special page (that can be used manually), but for the main use case it should be hidden behind some suitable UI and manual user inputs automated.
+
+>  # User submits edit request by requesting on the script/gadget talk page something like ""Please replace with the code currently at User:Me/code.js, which will implement the new feature ABC. This has been tested and consensus supports including the new feature.""
+
+""User requests merge using the //Merge// command in the page actions menu. The page to be merged to is extracted from //page property/special MCR slot/ad hoc edit summary syntax//. The code to be merged is saved as a flagged revision in the target page (NB: clashes with permissions-based access control, may be hard to solve) with a edit summary identifying the source of the merge request for both attribution and review purposes. Location of relevant discussion and consensus etc. is left as a social construct on the local wiki (the sandbox talk page, a central technical or general village pump, etc.).""
+
+>  # Interface administrator uses Special:ComparePages to see what the changes are, and, if they agree to make the edit, continues
+
+""Interface administrator sees //there are flagged revisions// notice on their watchlist, and uses ordinary diff tools to see what the changes are. Presumably a link in the edit summary will lead them to any relevant discussions.""
+
+>  # !!Interface administrator visits Special:MergeCode!!
+
+""Interface admin uses the flaggedrev tools to accept or reject the change, possibly including a manual review comment (possibly identifying the ""main author"" of the code being merged, but source page link and rev history attribution makes that unnecessary).
+
+> This would all be possible within the special pages.
+
+Yes, but with some lightweight UI / process sugar to make it a lot less tedious and prone to human mistakes.
+
+> * Not require database tables, special user rights, integration with external tools, etc.
+
+Modulo the clash between flaggedrevs and rights-based access control that I am uncertain would be reconcilable without major surgery.",1660389890,PHID-USER-3ay4ryrsytga5xa3rqak,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Quick idea version 2 for an extension + workflow (extension part highlighted)
+
+ # User wants to fork a script or gadget to propose a change
+ #* !!User visits Special:ForkCode, says what the source page is and what the target page is!!
+ #* !!Current content of source page is copied to target page, with a summary giving the needed attribution!!
+ # User makes desired modifications
+ # Others test, comment, etc. with normal talk pages
+ # User submits edit request by requesting on the script/gadget talk page something like ""Please replace with the code currently at User:Me/code.js, which will implement the new feature ABC. This has been tested and consensus supports including the new feature.""
+ # Interface administrator uses Special:ComparePages to see what the changes are, and, if they agree to make the edit, continues
+ # !!Interface administrator visits Special:MergeCode!!
+ #* !!provides the page title to be modified!!
+ #* !!provides and the permanent link to the revision of the fork that was approved (in case the page is modified in the middle)!!
+ #* !!provides a comment to be added to the automatic summary!!
+ #* !!provides the name of the user who wrote the new code being merged in!!
+ #* !!Clicks merge!!:
+ #* !!New revision is saved for the target page, implementing the edit request by copying the content from the approved revision. Edit is attributed to approving interface admin (in terms of whose contributions it shown up in, page history, etc.) but automatic summary notes the original author. Something like ""Updating with code written by User:FooBar. (rest of edit summary with explanation)!!
+
+This would all be possible within the special pages. It would:
+* Ensure that only users that can edit the actual gadget/mediawiki ns page/script can edit it using the special page
+* Provide attribution to the original author of the code (user who forked)
+* **Not** handle ""merging"" due to changes made in the script since the fork was created, but the user can just update their fork code; also doesn't deal with official branching, rebasing, etc.
+* Not require database tables, special user rights, integration with external tools, etc.",1601184019,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(completely forgot about this task)
+
+
+>>! In T71445#6265776, @Nux wrote:
+>> User forks a script or gadget in own user space
+> 
+> That would require a special page too. There should be some automatic information about forked version (at least as a oid link in the version history).
+> 
+> The fork information should then be available when merging/comparing.
+
+Sure, the automatic information at the start would be easy, though not sure about using that when merging/comparing since merging/rebasing may be an issue",1601183324,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"> User forks a script or gadget in own user space
+
+That would require a special page too. There should be some automatic information about forked version (at least as a oid link in the version history).
+
+The fork information should then be available when merging/comparing.",1593464204,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#6262201, @Dinoguy1000 wrote:
+> I'm not keen on the amount of work left in the hands of the merging interface admin in your proposal, @DannyS712. In particular, for an extension it should be possible to mark the forked pages as forks and indicate what page they're forked from, and have some mechanism to mark a particular revision as approved, at which point the special page could pull most of the required info automatically from the fork when an iadmin merges it back in. If it's a concern, the special page could allow certain fields to be modified pre-merge (e.g. tweaking the summary), but in general I feel much more comfortable not requiring the iadmin to manually copy so much (less chance for errors to creep in, etc).
+
+Interface admin only copies the approved revision id and the target page, plus its registered as a normal edit and so can easily be reverted.",1593327296,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I'm not keen on the amount of work left in the hands of the merging interface admin in your proposal, @DannyS712. In particular, for an extension it should be possible to mark the forked pages as forks and indicate what page they're forked from, and have some mechanism to mark a particular revision as approved, at which point the special page could pull most of the required info automatically from the fork when an iadmin merges it back in. If it's a concern, the special page could allow certain fields to be modified pre-merge (e.g. tweaking the summary), but in general I feel much more comfortable not requiring the iadmin to manually copy so much (less chance for errors to creep in, etc).",1593326552,PHID-USER-2wibf62nhsbcjs6773je,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"This is an N-of-one experience but I thought I should still share it:
+
+Recently, we decided that the version(s) of Twinkle that we had on fawiki were very old and not worth maintaining and patching; therefore, we decided to pull the latest version of Twinkle and localize it. We put the original code (which is in English, and has some enwiki-only features that we needed to modify or turn off) in the MediaWiki namespace, and made a gadget out of it. Then we also copied the code for each module in Draft namespace (and changed content model to JS) and a group of around 6-7 people started localizing the code. Those who know JS well helped with all aspects of localization, but those who don't only focused on translating Twinkle interface messages from English to Persian.
+
+In your scenario, this is akin to a single fork, in which multiple users are contributing. So regarding your point 5.F above, note that more than one user may need to be attributed.
+
+Each time the forked (Draft) version was merged into the MediaWiki version (by yours truly, and using manual code review + Preview feature of MediaWiki), we synced the Draft version too; that is, if I found an error in the Draft, I fixed it both in the Draft and in the MediaWiki version. If the Draft was further revised from then on, we had to merge again, and we would not want to attribute every contributor again (only those who contributed since the sync). You could argue the forked version in Draft should have been deleted and recreated to have clean history, but I think that is extra work.
+
+I can think of other ways your proposal may not be ideal, but for now, I will only focus on the issue of ""multiple contributors in the 'forked' version"". I like where you are going with this, but I think your model is too simple right now.",1593264047,PHID-USER-p2ebbrj45wupyi25othr,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Quick idea that just came to me for an extension + workflow (extension part highlighted)
+
+ # User forks a script or gadget in own user space
+ # User makes desired modifications
+ # Others test, comment, etc. with normal talk pages
+ # Interface administrator ""approves"" the edit (changes can be seen via Special:ComparePages)
+ # !!Interface administrator visits Special:MergeCode!!
+ #* !!provides the page title to be modified!!
+ #* !!provides and the permanent link to the revision of the fork that was approved (in case the page is modified in the middle)!!
+ #* !!provides a comment to be added to the automatic summary!!
+ #* !!provides the name of the user who wrote the new code being merged in!!
+ #* !!Clicks merge!!:
+ #* !!New revision is saved for the target page, implementing the edit request by copying the content from the approved revision. Edit is attributed to approving interface admin (in terms of whose contributions it shown up in, page history, etc.) but automatic summary notes the original author!!
+
+This would all be possible within a special page. It would:
+* Ensure that only users that can edit the actual gadget/mediawiki ns page/script can edit it using the special page
+* Provide attribution to the original author of the code (user who forked)
+* **Not** handle ""merging"" due to changes made in the script since the fork was created, but the user can just update their fork code; also doesn't deal with official branching, rebasing, etc.
+
+Thoughts? If this had support, I might apply for a rapid grant to write such an extension - shouldn't take too long for a working version to be created",1593251653,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Quick idea that just came to me for an extension + workflow (extension part highlighted)
+
+ # User forks a script or gadget in own user space
+ # User makes desired modifications
+ # Others test, comment, etc. with normal talk pages
+ # Interface administrator ""approves"" the edit (changes can be seen via Special:ComparePages)
+ # !!Interface administrator visits Special:MergeCode!!
+ #* !!provides the page title to be modified!!
+ #* !!provides and the permanent link to the revision of the fork that was approved (in case the page is modified in the middle)!!
+ #* !!provides a comment to be added to the automatic summary!!
+ #* !!provides the name of the user who wrote the new code being merged in!!
+ #* !!Clicks merge!!:
+ #* !!New revision is saved for the target page, implementing the edit request by copying the content from the approved revision. Edit is attributed to approving interface admin (in terms of whose contributions it shown up in, page history, etc.) but automatic summary notes the original author!!
+
+This would all be possible within a special page. It would:
+* Ensure that only users that can edit the actual gadget/mediawiki ns page/script can edit it using the special page
+* Provide attribution to the original author of the code (user who forked)
+* **Not** handle ""merging"" due to changes made in the script since the fork was created, but the user can just update their fork code; also doesn't deal with official branching, rebasing, etc.
+
+Thoughts?",1593251573,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,@Nux Wouldn't a simply way to utilize another namespace where the script or gadget is copied too and anyone that is authorized to make changes only touch that copied version? This way there wouldn't be any merge conflicts when merging back upon reviewer approval and the scripts/gadgets in MediaWiki namespace would be locked as production - live for viewers/users.,1574211681,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"> If we allow forking these to user css/json/js pages, when merging back there could be edit conflicts considering another edit could have been merged and the user didn't pull. How would you suggest keeping a fork to user namespace be kept up to date, might need to keep track of diff changes - this gets complicated?
+
+The problems are the same if users copy the page text. The difference you don't even know which version user copied. You also don't know if user copied text and saved and then did his/her changes or changed something while copying (and saved with the changes).
+
+So if you are merging you don't worry about that. You are reviewing changes as you see them. You either reject or accept them.
+
+Optionally the system can warn you (as a reviewer) that changes were forked before other changes were added. You can then reject and inform user about problems. The user then need to re-fork and re-apply changes. This is also similar to how you can resolve problems on Github.",1574200391,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"> If we allow forking these to user css/json/js pages, when merging back there could be edit conflicts considering another edit could have been merged and the user didn't pull. How would you suggest keeping a fork to user namespace be kept up to date, might need to keep track of diff changes - this gets complicated?
+
+The problems are the same if users copy the page text. The difference you don't even know which version user copied. You also don't know if user copied text and saved and then did his/her changes or did it change something while copying.
+
+So if you are merging you don't worry about that. You are reviewing changes as you see them. You either reject or accept them.
+
+Optionally the system can warn you (as a reviewer) that changes were forked before other changes were added. You can then reject and inform user about problems. The user then need to re-fork and re-apply changes. This is also similar to how you can resolve problems on Github.",1574196756,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"For general issues with forking/merging pages, see T113004. ",1574014937,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"If we allow forking these to user css/json/js pages, when merging back there could be edit conflicts considering another edit could have been merged and the user didn't pull. How would you suggest keeping a fork to user namespace be kept up to date, might need to keep track of diff changes - this gets complicated? Sending the fork to another namespace and keeping it in one location is much better. I am suggesting a simpler system due to these projects not being finished ie partial blocks was meant to become multi-blocks.",1573957857,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think what is needed is forking, not branching.
+
+  # Copy pages (make a fork).  This is not available AFAIK. Sure you can copy text but that doesn't preserve history.
+  # Merge pages (pull request). Kind of available but tricky. You can do some tricks with delete and restore IIRC, but that requires admin rights and is complicated anyway.
+
+Copying would have to be made available to standard users (e.g. user copies Mediawiki:common.css to User:Example/common.css). Then an admin could merge ""User:Example/common.css"" back to ""Mediawiki:common.css"" (visually e.g. by reviewing it as an edit).
+
+Note that both operations would actually be useful for articles as well. You sometimes need to merge articles and there is no nice way to do that.",1573952031,PHID-USER-awklupbdn3wr6glu7nyx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@JEumerus clarified my side note, yeah it was confusing. I was meaning to refer to how js, json, css pages under MediaWiki were split out, did not mean to suggest that EditInterface was a new permission.",1573889449,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Actually, editinterface has been around for a long time. It allows editing of all MediaWiki: namespace pages as they are not all super sensitive, the css and js extra permissions were created because js and css pages in the MediaWiki: namespace and elsewhere are more sensitive than the average MediaWiki namespace page.",1573812811,PHID-USER-cr5rnyhox7s3fl5at22e,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@DannyS712 isn't that the current system that Wikipedia already uses?
+
+Your branching/pull request concept is great! While using existing namespace could work, the need to delete and move seems messy. I think instead of having all of this within the MediaWiki namespace, a second namespace could be utilized. Keeps it much cleaner, though this would require new development resources...
+
+MediaWiki namespace scripts/gadgets would be the version that is activated for users/visitors. 
+Creation of a new namespace such as ""MediaWiki_Staging"" would be where changes are made to the scripts/gadgets as a sort of ""staging"" area, not served to users/visitors. 
+
+any scripts/gadgets from MediaWiki that need changes could then be cloned/pulled into MediaWiki_Staging by click of a button. When ready to submit changes, user clicks a ""submit"" button to send to reviewers (new user permission) and a status message is set to ""Pending Review"". Page would be locked from editing or if an edit is made, status is reset to nothing and review request is canceled.
+
+A special page to list all the pending changes to scripts/gadgets would provide reviewers option to approve or reject with reason.
+  - Approve would set status to ""Accepted"", latest revision is copied to script/gadget in MediaWiki namespace
+  - Reject would reset status back to ""Failed"", no changes occur
+
+side note: based on recent changes to edit access to js, json, css in MediaWiki namespace, It would make more logical sense and add additional protections to add in a configurable variable that acts as a whitelist regarding which of the system messages can be modified, on average only like 10% are ever modified.",1573889381,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@DannyS712 isn't that the current system that Wikipedia already uses?
+
+Your branching/pull request concept is great! While using existing namespace could work, the need to delete and move seems messy. I think instead of having all of this within the MediaWiki namespace, a second namespace could be utilized. Keeps it much cleaner, though this would require new development resources...
+
+MediaWiki namespace scripts/gadgets would be the version that is activated for users/visitors. 
+Creation of a new namespace such as ""MediaWiki_Staging"" would be where changes are made to the scripts/gadgets as a sort of ""staging"" area, not served to users/visitors. 
+
+any scripts/gadgets from MediaWiki that need changes could then be cloned/pulled into MediaWiki_Staging by click of a button. When ready to submit changes, user clicks a ""submit"" button to send to reviewers (new user permission) and a status message is set to ""Pending Review"". Page would be locked from editing or if an edit is made, status is reset to nothing and review request is canceled.
+
+A special page to list all the pending changes to scripts/gadgets would provide reviewers option to approve or reject with reason.
+  - Approve would set status to ""Accepted"", latest revision is copied to script/gadget in MediaWiki namespace
+  - Reject would reset status back to ""Failed"", no changes occur
+
+side note: I know that the editinterface permission plus the new restricted permissions for js, json, css were recently created. There should still be a configurable variable that acts as a whitelist regarding which of the system messages can be modified, on average only like 10% are ever modified.",1573792970,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Implementation with current technical options:
+
+# Have a script or gadgets at `Foo`
+# Copy the (then-current) version to `Bar` (Equivalent of branching)
+# Apply any suggested edits
+# Request that the edits be merged in (Equivalent of opening a pull request)
+# Move `Bar` to `Foo`, deleting `Foo` in the process (Equivalent of merging a pull request)
+# Restore old revisions of `Foo` (to provide continuity of history)
+
+This would
+* Provide attribution to users who suggest the edits (since they are still credited with the revision)
+* Not require new development (perhaps some user scripts to simplify things, but not strictly speaking needed)
+Thoughts?",1573703541,PHID-USER-ilk3nopl66nufkd26tee,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"thanks for letting me know about T205482. Given that Flagged Revs gave me an internal error (VM1844:1 Uncaught TypeError: Cannot read property 'addPortletLink' of undefined) for trying to add in MediaWiki namespace, I do not think that placing effort and time into solving T205482 is worth it.
+
+probably better off creating a new extension either from scratch or reusing elements from Extension Flagged Revs and Moderation. Simple Extension that has Approve/Reject buttons with a special page listing unreviewed .js, .css, Gadgets and preventing unreviewed from going live would be enough for basic usage. Also would allow any wiki to use it, not just WMF.
+
+Last I checked, this task stalled out on deciding a solution.",1538576793,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#4637342, @SpookyGhost8 wrote:
+> I know that a while ago it was mentioned that Extensions Flagged Revs + Code Review could be a potential solution.
+For the records, CodeReview is unmaintained so you'd have to solve T205482 first.",1538564697,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I know that a while ago it was mentioned that Extensions Flagged Revs + Code Review could be a potential solution. I tested yesterday on a small wikifarm and Flagged Revs does not work on the MediaWiki namespace at all, pretty sure I configured correctly. I did not grant myself the autoreview permission and did not use any of the default user groups. Any valid or invalid javascript added to MediaWiki:common.js went live immediately. Trying to hardcode ""NS_MEDIAWIKI"" into extension array resulted in an internal error at Special:UnreviewedPages. Extension:Approved Revs explicitly says that it doesn't work on MediaWiki namespace.
+
+Edit: ""addportlet"" error was my own script, not Flagged Revs",1538619107,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I know that a while ago it was mentioned that Extensions Flagged Revs + Code Review could be a potential solution. I tested yesterday on a small wikifarm and Flagged Revs does not work on the MediaWiki namespace at all, pretty sure I configured correctly. I did not grant myself the autoreview permission and did not use any of the default user groups. Any valid or invalid javascript added to MediaWiki:common.js went live immediately or gave a ""addportlet"" error in my browser console. Trying to hardcode ""NS_MEDIAWIKI"" into extension array resulted in an internal error at Special:UnreviewedPages. Extension:Approved Revs explicitly says that it doesn't work on MediaWiki namespace.",1538531515,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#3613657, @Tgr wrote:
+> the most promising approach is to make MediaWiki sync with the master branch of some remote repo, after which there is no point in rebuilding the code review interface in MediaWiki, since there are plenty decent ones out there.
+
+Now filed as {T187749}.",1519075015,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"another possibility outside of Gadget 2 is a test wiki where any JS, CSS or Lua is tested and then moved over to the main WMF wikis after having a +2 code reviewer approve merging it over. The MediaWiki namespace is mostly interface messages, restricting JS & CSS editing to new permissions might make this safer as well; editusercssJS was split into separate permissions though seems to be limited use cases (someone breaking personal js/css).",1505785630,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think relying on Git is a good idea, but I think you underestimate that by moving contributing to these files to a git, you remove it from direct access from the wiki. I think it will feel like we're taking away control form the community, even if this isn't the intention, as we in some way remove the direct editing possiblity from the wiki and make it more difficult to contribute there for normal user.
+
+We have to find a compromise to minimize this problem, because this wouldn't ever be accepted otherwise. (Many users still remember the js wheel-war between WMF and community at German Wikipedia to well, even if it's been a long time ago and many things have changed.)",1505771008,PHID-USER-4z6eerx3m7iocsrcpku5,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"CodeReview + FlaggedRevs is a possible way to handle this task, although not a good one. SVN-style ""linear"" history sucks for code review (which is why pretty much every single projetc abandoned it when DVCS-s became mainstream), and implementing non-linear history in MediaWiki does not sound like fun, so the most promising approach is to make MediaWiki sync with the master branch of some remote repo, after which there is no point in rebuilding the code review interface in MediaWiki, since there are plenty decent ones out there.",1505709294,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#3612257, @SpookyGhost8 wrote:
+> There also is [[ https://www.mediawiki.org/wiki/Extension:CodeReview | Extension:CodeReview  ]] but status is historical reference, perhaps reopening that for development would be a potential solution?
+
+CodeReview is perfectly stable and usable and (mostly) feature-complete. The `{{Historical}}` template was added to that page by someone who doesn't appear to be familiar with the extension. There is absolutely nothing preventing you from installing and using CodeReview -- or if there is, that's a bug and I'd love to hear about it so that we can get it fixed! Just because something isn't used on Wikimedia's wikis anymore doesn't mean it's flat-out obsolete and/or unusable.
+
+All that being said, CodeReview is mostly a web UI for a Subversion (SVN) repository. The workflow is essentially different when it comes to a SVN repository as opposed to editing on-wiki .css and .js pages: changes to the latter are live immediately, whereas code changes committed to a SVN repo need to be manually deployed by someone.
+It is my firm belief that creating a largely new system for ""code reviewing"" on-wiki .css and .js pages would be the easiest and cleanest solution instead of trying to repurpose CodeReview. In any case, please feel free to add me as a reviewer to CodeReview patches and I'll be happy to review 'em (unless someone else beats me to it, that is).",1505648536,PHID-USER-mlp7cjyksjzemkdr5ued,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"There also is [[ https://www.mediawiki.org/wiki/Extension:CodeReview | Extension:CodeReview  ]] but status is historical reference, perhaps reopening that for development would be a potential solution?",1505587846,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,,1505583022,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,,1505582353,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,From what I remember that was already done in #Gadgets-2.0.,1505580179,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Would it be more secure to possibly add in a few more custom user permissions such as splitting editinterface into editJS and editCSS with also adding in restrictions for template namespace and editLua for Lua? I know that edituserjs&css was split into edituserjs and editusercss. This way the mediawiki namespace would contain the interface messages; all javascript is restricted to .js and users with editJS, all css is restricted to .css and users with editCSS; all lua modules restricted by editLua; possibly restrict templates to editTemplate. Just a suggestion...",1505579931,PHID-USER-sypsy74suppfrytdu4vx,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"In relation to {T158149}, I dare to ask: what is the current status? :)",1505205187,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"See also {T171563}, which I just created for the rest of the problem (pages outside MediaWiki: namespace, still a very large set with some potential vulnerabilities).",1500954964,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Based on my work around T165981 during the 2017 Hackathon - which essentially involved creating a prototype implementation of Wikia's ContentReview extension compatible with core MediaWiki - I would like to note the following:
+
+Creating an extension that just requires site JS to pass certain requirements (manual review, automated tests) before it is served to other users is relatively easy to develop. As discussed above and elsewhere, such a system has been in operation at Wikia since 2015 - its main benefits are that it has a clear workflow, and is tightly integrated into MediaWiki.
+
+I'm on the opinion that if extra code review features are required from this product, such as branching or line comments, implementing them within MediaWiki would be a bad idea. It would have to reconcile MediaWiki's concept of singular multi-revision pages with the paradigm of a branching VCS - an extension implementing this could easily become a highly complex behemoth that is a nightmare to develop, maintain and sustain.
+
+If the decision is to extract the code review functionality from MediaWiki, it is possible to leverage the power of existing VCS and code review tools, such as Gerrit. In this scenario, the setup can be further simplified by completely eliminating JS pages handling from inside MediaWiki. The versatility of ResourceLoader makes it possible to define configurable custom modules that pull their source content from an external data source instead of MediaWiki pages.",1495415465,PHID-USER-c4xszutxtrvtj73h3rns,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Just an idea: what about committing to have an initial plan agreed by the end of Wikimania -- latest? Just an arbitrary date, but a firm one. A driver would be required to stir the discussion and draft plan, though.",1488387037,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Note that, for templates and modules, a branch-like system is already used manually on English Wikipedia (and probably other wikis) via template/module sandbox pages, though there's no hard requirement for their use to propose changes.",1487597449,PHID-USER-2wibf62nhsbcjs6773je,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#3039577, @Samwilson wrote:
+> […]
+> The tricky part of it I think is whether or not it's going to be possible to set up a development environment (or e.g. use an existing test wiki) in which to work on scripts etc. and then easily move them from there to code review and then to the live wiki.
+
+That's why I'd prefer a more universal approach: If you think of a wiki as a whole as a Git (or similar) repository, you could test in a particular ""branch"" (even if for example a change in a template system requires edits to multiple templates pages) and, after testing, merge it to ""master"".  Proposed changes to protected pages could be submitted as branches and, if approved, merged.  Changes to (subelements of) the main page or other portals could be mocked up without having to fiddle with all the dependent links.  Flagged revisions would be a special case where there is a social contract to merge changes to a particular branch regularly.  Users could save their incomplete rewrites of a page in a branch without having to copy & paste it to their computer.  Etc.
+
+That wouldn't make the solution to this task easier, but if the solution to this task already is complex, it would be nice if it solves other use cases as well.",1487591492,PHID-USER-vk6mlmacfhx77egryy5i,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@MZMcBride: the difference between on-wiki JS and CSS and pretty much any other wiki page (although templates and modules sometimes also fall into this category) is that edits to them can break the whole site for other users. So it's not about trying to limit editing of these to ""professionals"", but just to make it less likely to introduce errors.
+
+Which is why these pages are often protected and left to admins to edit. But even people who know what they're doing (which is all I would take ""engineers"" in the above sense to mean) can make mistakes and would benefit from a process of being able to propose changes and have those changes be easily reviewed by other people before they go live and suddenly make everyone's search autocomplete stop working. :-)
+
+I'd also say that no one seems to be suggesting Gerrit as a solution. I'm not super familiar with Differential, but I guess it's better (or does it just have more whitespace and better-looking buttons?) On the other side of the fence, there's Github and seemingly a lot of people find that relatively easy to use. So surely we can have figure out something that works.
+
+The tricky part of it I think is whether or not it's going to be possible to set up a development environment (or e.g. use an existing test wiki) in which to work on scripts etc. and then easily move them from there to code review and then to the live wiki.
+
+",1487549651,PHID-USER-hlhhe6qw6qfkl7wyfhxk,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1459477, @Krinkle wrote:
+> Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source.
+
+I agree with most of what you write in this comment. I'll note that there's a view that engineer should be treated similar to a term like doctor, and should require at least a degree in engineering. Developers, coders, or programmers might be more apt.
+
+I also don't really love the notion that engineers need to do the engineering (even when broadening the terms to be almost meaningless). Wikipedia is not exclusively written by professional encyclopedists, Wiktionary is not exclusively written by professional lexicographers, Wikinews is not exclusively written by professional reporters, etc.
+
+>>! In T71445#3028613, @Tgr wrote:
+> This was the second (slash third, in a tie) most popular item in the [[https://www.mediawiki.org/wiki/User:Community_Tech_bot/WishlistSurvey/Votes|Developer Wishlist results]]. Any thoughts about the next step?
+
+I would recommend re-reading this task. It's quite long, but contains a lot of good and useful thoughts.
+
+Speaking of engineers and engineering, it strikes me as odd and interesting that the Gerrit code review process isn't really well-liked (cf. {T114419}, etc.), and yet we're expecting the same people to build a ""sane code-review process"" that integrates perhaps Git, perhaps wiki pages, and definitely an even larger and more diverse group of Wikimedians?",1487445102,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"If this could be done as an extension that talks to //any// git repository (as configured by site admins), then it would work with whatever Git code review system people want (i.e. Wikimedia sites could use Gerrit or Differential), and third-party wikis could do it with Github.
+
+An extension could easily update a given set of gadget's pages based on the content of files in a public Git repository somewhere. It'd be really cool if changes made locally could also be pushed out to that repository as review-requests — although perhaps it's more likely that the set up would be that some wikis are configured to //only pull// from the repo (because that's the point of requiring code review after all), and it'd be possible to configure development wikis to send new code to the repo (and to receive updates when the user asks for them).
+
+Is there a possibility that such an extension could be a sort of global gadget system? The code is still duplicated, but it's controlled centrally. Would work for templates and modules too.",1487212377,PHID-USER-hlhhe6qw6qfkl7wyfhxk,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#3028613, @Tgr wrote:
+> I guess first we should determine if this needs to be done inside MediaWiki
+Yes please.
+
+> or the community would accept something based on gerrit/github/whatever (which would be much less work and would provide much better tooling integrartion).
+Gerrit is awful [no citations needed] and GitHub is proprietary, and plenty of people -- developers and users alike -- care about the solution being as FOSS as possible.
+
+Anyway, I don't think doing this as a MediaWiki extension is impossible; there are probably a few tricky questions to solve and whatnot, but considering that [[https://github.com/Wikia/app/tree/dev/extensions/wikia/ContentReview|Wikia managed to implement a similar system]], it should be doable. I'd be interested in helping out where possible to get this thing built.
+",1487165515,PHID-USER-mlp7cjyksjzemkdr5ued,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"This was the second (slash third, in a tie) most popular item in the [[https://www.mediawiki.org/wiki/User:Community_Tech_bot/WishlistSurvey/Votes|Developer Wishlist results]]. Any thoughts about the next step? I guess first we should determine if this needs to be done inside MediaWiki or the community would accept something based on gerrit/github/whatever (which would be much less work and would provide much better tooling integrartion).",1487151515,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"This proposal is selected for the developer wishlist voting round and will be added to a MediaWiki page very soon. To the subscribers, or proposer of this task: please help modify the task description: add a brief summary (10-12 lines) summarizing the problem that this proposal raises, topics discussed in the comments, and a proposed solution (if there is any yet). Remember to add a header with a title ""Description,"" to your content. Please do so before February 5th, 12:00 pm UTC. ",1486164465,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A couple possibilities:
+* write a bot that syncs page content to files on Github (or some other DVCS site to be bikeshedded later), push out the whole code review system there
+* write a proper extension that does that and can load alternative branches / pull requests on demand, a bit like TemplateSandbox
+* repurpose [[https://www.mediawiki.org/wiki/Extension:CodeReview|CodeReview]] to work with page revisions instead of an SVN repo, and pair it with something like FlagRev.
+
+The second option is probably the sane one.",1486114095,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I've been thinking about this task a bit more with {T151408} recently filed. I wonder whether we could implement some kind of social +2 process for on-wiki JavaScript and CSS as a medium-term solution. If we needed to, we could also investigate a technical +2 process, but that's probably overkill for now.
+
+What would a social +2 process look like? We'd try to convince the various wikis to adopt a process of proposing edits on the talk page and having more than one person review the code for sanity before editing the live JavaScript or CSS pages. This type of approach has both the same benefits and detriments as Gerrit's +2 process, of course. Gerrit implements this at a technical level and wikis could as well if needed, but a social process would be more organic and perhaps a better starting point.
+
+A lot of the discussion surrounding security issues related to on-wiki JavaScript editing boils down to this task, I think. A true increase in security would likely only come from some kind of sane and workable code review situation. The other issues (such as bot flags) are peripheral and marginal in comparison.",1480271160,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Would this task be a good topic for the #wikidev17 ? If so, the deadline to submit new proposals is next Monday, October 31: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation",1477575565,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,@Dinoguy1000 thanks for sharing that information !,1446066743,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"As a bit of a case study, Wikia recently experienced [[ http://community.wikia.com/wiki/Thread:890734 | two ]] [[ http://community.wikia.com/wiki/Thread:922459 | attacks ]] which resulted in revoking the ability for admins to edit pages in the MediaWiki namespace (except for a [[ http://community.wikia.com/wiki/Help:System_messages/whitelist | handful of whitelisted pages ]]), user JS being [[ http://community.wikia.com/wiki/Help:Personal_CSS_and_JS#JavaScript | made opt-in]] (and admins not being able to edit other users' CSS/JS any more either), and a [[ http://community.wikia.com/wiki/Help:JavaScript_review_process | review process ]] for sitewide JS instituted (though it's more of a [[ http://community.wikia.com/wiki/Help:JavaScript_review_process#What_are_the_criteria_for_approval.3F | lightweight sanity check ]] than a proper code review).",1446065037,PHID-USER-2wibf62nhsbcjs6773je,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1469730, @demon wrote:
+>>>! In T71445#1459477, @Krinkle wrote:
+>> Or we can enter the realm of Git. [..] I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.
+> 
+> I think it's very important to differentiate between ""using Git"" and ""using Git in the same way we develop MW.""
+
+Completely agree.
+>>! @demon wrote:
+> I can see the argument for Git, but under no circumstances should we subject any more people to Gerrit than we already do [..]
+
+Agreed. The repo shouldn't use Gerrit, and it shouldn't require WMF staff to add users to its access group. I'm pushing for a repo that is first and foremost maintained independently by the community and deployed often (at least weekly; with the option to ride WMF-SWAT deployment schedule for individual changes so they can even push changes twice a day when needed). Phabricator makes sense, but if the community has other suggestions we should consider those as well.",1438022631,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"The idea of Git but not Gerrit for gadget developers is sensible. It fits with T1238 and the idea of bringing gadget developers together and closer to our wider developer community.
+
+I agree that a code review extension for MediaWiki would put us in a costly spin-off. Differential is already enabled [[ https://phabricator.wikimedia.org/differential/query/all/ | here ]] (and in [[ https://phab-01.wmflabs.org/differential/query/all/ | phab-01 ]] if someone wants to play with it). Barriers are obstacles but also defenses. If there are barriers for gadget developers they will be barriers also for other developers. Better work on minimizing common barriers than creating different workflows to achieve the same goals.
+
+The process for deploying patches for gadgets from Differential to Wikimedia projects would need a plan. Would this be the same process as for MediaWiki core and extension patches (meaning that this plan is also blocked on {T18}) or can some shortcuts be taken?
+
+>>! In T71445#1459477, @Krinkle wrote:
+> this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+Nothing that Differential cannot handle, right?",1438006121,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1459477, @Krinkle wrote:
+> Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+> 
+
+Heh, ""tightly controlled."" Yes, you couldn't just sign up...but all you had to do was ask and not be an idiot. Versus now where anyone can sign up, but it's impossible to get trusted access to anything :p
+
+I disagree that there was lack of manpower to maintain ACLs for SVN...we already did...
+
+And...deployment cycles had nothing to do with whether we hosted Gadgets in SVN.
+
+I actually don't even remember a discussion about putting them in SVN, but I am gladly willing to be proven wrong.
+
+> Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.
+
+I think it's very important to differentiate between ""using Git"" and ""using Git in the same way we develop MW."" Right now I think the two are a little conflated (possibly because we've had discussions about doing the latter before).
+
+I can see the argument for Git, but under no circumstances should we subject any more people to Gerrit than we already do; the CR process it enforces is absurd, terrible, and actively scares people away. Also, I don't like the idea of building more infra in/around Gerrit when we're trying to kill the dang thing ;-)
+
+Now, if we want to build something on Phabricator. Or just plain old Git...that could be useful or cool. But let's not ruin all the Gadget maintainers' lives by making them use Gerrit :p",1437534518,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little staffing to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review problem and not all the other problems (being able to use an IDE, having testing, having localisation bot commits, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1605809299,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review problem and not all the other problems (being able to use an IDE, having testing, having localisation bot commits, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1605809262,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations. Of course I'd screw up if you let them drive a plane.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review problem and not all the other problems (being able to use an IDE, having testing, having localisation bot commits, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1437173532,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations. Of course I'd screw up if you let them drive a plane.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review problem and not all the other problems (being able to use an IDE, having testing, having localisation, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1437173381,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations. Of course I'd screw up if you let them drive a plane.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review aspects and not all the other aspects (being able to use an IDE, having testing, having localisation, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1437100088,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1018186, @DaBPunkt wrote:
+> This ticket exists to prevent users at Wikipedia of disabling stuff they don’t want.
+Not really.",1423162299,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,No it does not.,1423155874,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1017081, @Krenair wrote:
+> Yes, and it's bad. It's why this ticket exists.
+
+This ticket exists to prevent users at Wikipedia of disabling stuff they don’t want. That’s the hole purpose; not security, not helping, but control. Be at least so frank and say the truth.
+
+Yes, there is the possibility that an admin could do evil stuff with JS; but at Wikipedia we have something called »Assume good faith« and until now it worked great. The users implemented so much stuff in JS and CSS that Mediawiki lacks until today – if you are underused try to fix the software (there are a few thousand bugs in here) and not implement a new kind of force-control. 
+",1423154098,PHID-USER-4nukugv22wnc3p6k557t,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016949, @jayvdb wrote:
+>>>! In T71445#1016916, @Krenair wrote:
+>>>>! In T71445#1016860, @jayvdb wrote:
+>>> And whenever it happens, we can improve the static analysis tools (and desysop the fool who wrote it).
+>> 
+>> I don't think you understand. It's not okay for us to get to this stage.
+> 
+> You're already in this stage.  That is reality.
+
+Yes, and it's bad. It's why this ticket exists.",1423111689,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016916, @Krenair wrote:
+>>>! In T71445#1016860, @jayvdb wrote:
+>> And whenever it happens, we can improve the static analysis tools (and desysop the fool who wrote it).
+> 
+> I don't think you understand. It's not okay for us to get to this stage.
+
+You're already in this stage.  That is reality.",1423103019,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016860, @jayvdb wrote:
+> And whenever it happens, we can improve the static analysis tools (and desysop the fool who wrote it).
+
+I don't think you understand. It's not okay for us to get to this stage.",1423101886,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016685, @Krenair wrote:
+> 
+>>>! In T71445#1016653, @jayvdb wrote:
+>>>>! In T71445#1011829, @Krenair wrote:
+>>> I don't think we can just sandbox JS running on the wiki, @jayvdb
+>> 
+>> Firstly, that isnt what I recommended.  We can perform static analysis of the JS / CSS before it is saved.  Tools exist for this.  It doesnt need to be perfect; the JS is either written by an admin, or enabled by an admin, or a user is enabling a script in their own JS page only.  
+>> More broadly, the scary area is small wikis with few admins, potentially adding code that they dont understand written by someone else, possibly malicious.  Static analysis and ops monitoring suspicious JS page saves can gradually improve static analysis to make it increasingly difficult for malicious code to come via this vector through a sysop to the wiki's Common.js.
+> That's not good enough. It doesn't matter how big/small a wiki is or how many admins it has, that would only affect catching the fact that malicious JS ***has already been added*** by an admin user who is either malicious themselves (e.g. the account was taken over by someone unauthorised, or the actual authorised user was untrustworthy themselves even) or didn't know what they were doing. By then it's too late - we must catch this stuff *before* it can be run on random people's clients, e.g. with a full external code review system.
+
+Did you look at any of the static analysis tools before writing this?  My point is that wikis have a saner environment than many of the other projects who rely on static analysis, as we have less people able to edit the JS.  And whenever it happens, we can improve the static analysis tools (and desysop the fool who wrote it).  We can also run the static analysis tools in over-protective mode, and use {{edit protected}} to engage an JS expert (with a special right) whenever the tool incorrectly detects proposed code as unsafe, due to potential security implications.",1423100125,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016730, @Ricordisamoa wrote:
+>>>! In T71445#1016653, @jayvdb wrote:
+>> Another approach regarding JS is to migrate it to a language which is safer, and compile it into JS.  https://github.com/mherkender/lua.js
+> 
+> Is this a joke? Putting together two bad languages cannot result in a good one.
+> And by the way, MediaWiki embeds lots of 'custom' JS libraries we must be able to use.
+
+A bridge to 'approved' JS libraries would be needed.",1423099544,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016653, @jayvdb wrote:
+> Another approach regarding JS is to migrate it to a language which is safer, and compile it into JS.  https://github.com/mherkender/lua.js
+
+Is this a joke? Putting together two bad languages cannot result in a good one.
+And by the way, MediaWiki embeds lots of 'custom' JS libraries we must be able to use.",1423098198,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"
+>>! In T71445#1016653, @jayvdb wrote:
+>>>! In T71445#1011829, @Krenair wrote:
+>> I don't think we can just sandbox JS running on the wiki, @jayvdb
+> 
+> Firstly, that isnt what I recommended.  We can perform static analysis of the JS / CSS before it is saved.  Tools exist for this.  It doesnt need to be perfect; the JS is either written by an admin, or enabled by an admin, or a user is enabling a script in their own JS page only.  
+> More broadly, the scary area is small wikis with few admins, potentially adding code that they dont understand written by someone else, possibly malicious.  Static analysis and ops monitoring suspicious JS page saves can gradually improve static analysis to make it increasingly difficult for malicious code to come via this vector through a sysop to the wiki's Common.js.
+That's not good enough. It doesn't matter how big/small a wiki is or how many admins it has, that would only affect catching the fact that malicious JS ***has already been added*** by an admin user who is either malicious themselves (e.g. the account was taken over by someone unauthorised, or the actual authorised user was untrustworthy themselves even) or didn't know what they were doing. By then it's too late - we must catch this stuff *before* it can be run on random people's clients, e.g. with a full external code review system.",1423097598,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1011829, @Krenair wrote:
+> I don't think we can just sandbox JS running on the wiki, @jayvdb
+
+Firstly, that isnt what I recommended.  We can perform static analysis of the JS / CSS before it is saved.  Tools exist for this.  It doesnt need to be perfect; the JS is either written by an admin, or enabled by an admin, or a user is enabling a script in their own JS page only.  
+More broadly, the scary area is small wikis with few admins, potentially adding code that they dont understand written by someone else, possibly malicious.  Static analysis and ops monitoring suspicious JS page saves can gradually improve static analysis to make it increasingly difficult for malicious code to come via this vector through a sysop to the wiki's Common.js.
+
+However there are ways to sandbox JS. Again, tools exist and are in production. https://en.wikipedia.org/wiki/Caja_project 
+
+Another approach regarding JS is to migrate it to a language which is safer, and compile it into JS.  https://github.com/mherkender/lua.js  Then the only 'real' JS is libraries provided by extensions managed by code review processes.",1423097035,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I don't think we can just sandbox JS running on the wiki, @jayvdb",1422983276,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Maybe a tool like https://www.mediawiki.org/wiki/Gerrit_patch_uploader can be created to supplement Phab/etc.
+
+Not that I agree with this idea ; IMO we'd be far better off identifying the problematic uses of .css and .js and requiring a new right to save changes which appear to have security implications. That allows gradual improvement, and is not too dissimilar to security checks used on uploads.  And 'safe' functions added to properly managed JS modules whenever Common.js editors hit their head too regularly on the security inspector.",1422962357,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Ref web-based editor in Phabricator, as commented in T71445#742556, we checked upstream, but generally speaking they are not enthusiastic with the idea. See their reasoning at https://secure.phabricator.com/T6008#7
+",1422960004,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1005858, @Krinkle wrote:
+> Using Git does raise the barrier for contribution a little.
+
+This is a concern, though. While Phabricator uses SUL and so doesn't have the issues that earlier proposals of using Gerrit did, until WMF has moved from Gerrit to Phabricator for code review it's hard to really guess how this might work in practice for people who maintain gadgets on-wiki and aren't used to other workflows.
+
+Ideally one workflow would be loading the gadget files in a web-based editor of some sort, making the changes, and submitting that as a patch without having to use any locally-installed software other than a web browser and without any complicated key setup. But does Phabricator support that (and will it be enabled here)?",1422890696,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1005858, @Krinkle wrote:
+> We'd have a clear distinction between the ""wiki-content administrator"" role (sysop) and ""developer"" role. One person can still have both roles, but sysop would no longer imply ""developer"". We currently have a situation where users can become sysop (to block users, delete pages, etc.) – but at the same time able to change gadgets. (Through the MediaWiki-namespace that got unfortunately re-used for Gadgets). This isn't a matter of personal trust or malicious intent. These users have clearly gained the respect and trust of their respective communities. It's about technical competence and experience to make decisions about software modifications. This is a sensitive area. It's not fair to demand from most sysops that they have to make these decisions. They shouldn't have to deal with requests for edits on Common.js without knowing what the impact of such program would be.
+
+Conversely, more experienced JavaScripters should be able to merge improvements without having to request advanced user rights on each wiki.
+And what about Lua modules then? A Git repository would probably speed T52329 up.
+
+However, I'm afraid that many users could think of Git being another way to limit their independence.",1422706176,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1006055, @Steinsplitter wrote:
+>>>>! In T71445#968479, @Ricordisamoa wrote:
+>> I often find privacy violations in Common.js in the form of well-intended scripts  (...)
+> 
+> Then the software should log or prevent such actions (like a abusefilter). 
+
+There's no way to automate code review, especially not of obfuscated code. Same goes for security review, which is as important (and a lot of scripts are lacking here... only yesterday I had to kill a user script because of a CSRF vulnerability that would allow page deletions).",1422700941,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>>! In T71445#968479, @Ricordisamoa wrote:
+> I often find privacy violations in Common.js in the form of well-intended scripts  (...)
+
+Then the software should log or prevent such actions (like a abusefilter). 
+
+And please remember that a lot of script dev's don't like to work with git...",1422695806,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968479, @Ricordisamoa wrote:
+> I know this has probably been discussed before, but... what about hosting gadgets via Git/Phabricator?
+> At least the largest ones will benefit from more thorough review.
+
+Thanks for bringing this up @Ricordisamoa!
+
+I support the idea of using Git for gadgets in the future. There are other options, but Git is nice.
+
+Using Git/Phabricator for gadgets provides many benefits:
+
+* Code review
+ * Review by another person before merging (more stable code).
+ * Ability for anyone to submit a patch that others can easily merge (instead of copy-pasting from a talk page, or a user sub page).
+ * Inline discussion about the code and making small improvements.
+* Continuous integration
+ * Ability to write and run unit tests (less breakage for users).
+ * Option to enforce coding style and code quality via JSHint (opt-in of course).
+* Git
+ * ""git-blame"" to find authors of a particular pieces of code.
+ * The option to distinguish between stable and beta versions.
+ * Easily backport (apply) individual bugfixes to older versions.
+ * Streamlined process for deploying weekly to all wikis (for ""global"" gadgets).
+ * Ability for non-Wikimedia wikis to ""install"" gadgets on their wikis (and update it). Instead of copying all relevant pages and trying to keep them up-to-date. (Or hotlinking via extra HTTP requests and risking breakage with incompatible versions.)
+ * Ability for MediaWiki site-admins to install the right version of gadgets on their wikis. (Thanks to Git branches associated with a MediaWiki  release version.) – No more need to maintain compatibility with old MediaWiki versions or hotlinking code.
+* Issue tracker
+ * Central place to create and resolve tasks, bugs and feature requests.
+
+We could create an extension like ""WikimediaGadgets"". Or separate Git repositories with git-submodules or Composer-based. Everything is possible.
+
+Using Git does raise the barrier for contribution a little. But in full perspective of where we are coming from and what we all want, I think that's worth raising the barrier for. With gadgets, the community creates their own modules without involving Wikimedia Foundation. They can create and deploy anything they want. It's very enabling and flexible for the community.
+
+In the last few years, Wikimedia has changed a lot in how it manages code. We no longer have a single repository managed by a handful of people that only deploy updates once or twice a year. Quite the contrary. We now have a plethora of different repositories maintained by different people (including lots of volunteers!). This ""Wikimedia Gadgets"" repo can have its own access control in Git – separate from MediaWiki and Wikimedia user groups.
+
+Some gadgets have already done this by using GitHub (except for the deployment part, these still copy-paste to wiki pages):
+* https://github.com/azatoth/twinkle
+* https://github.com/Krinkle/mw-gadget-rtrc
+* https://github.com/Krinkle/mw-gadget-whatleaveshere
+* https://github.com/countervandalism/mw-gadget-cvnoverlay
+
+Aside from the benefits for authors and users of gadgets, there are a few extra gains.
+
+We'd have a clear distinction between the ""wiki-content administrator"" role (sysop) and ""developer"" role. One person can still have both roles, but sysop would no longer imply ""developer"". We currently have a situation where users can become sysop (to block users, delete pages, etc.) – but at the same time able to change gadgets. (Through the MediaWiki-namespace that got unfortunately re-used for Gadgets). This isn't a matter of personal trust or malicious intent. These users have clearly gained the respect and trust of their respective communities. It's about technical competence and experience to make decisions about software modifications. This is a sensitive area. It's not fair to demand from most sysops that they have to make these decisions. They shouldn't have to deal with requests for edits on Common.js without knowing what the impact of such program would be.
+
+I often find privacy violations in Common.js in the form of well-intended scripts that load files from third-parties. (E.g. fonts, images or scripts.) This is against the Foundations' privacy policy, and probably not what the sysop intended. There's a good chance the sysop and user who suggested such edit, actually believe in our privacy policy. But they simply lack knowledge of how web browsers work. They didn't realise that such edit would result in all readers of the wiki now loading a file from a Google server. (And send their IP address and other details about their computer and geolocation to that Google server – without consent.)
+
+The wikis can use their own policies for deciding what gadget to create, support and enable. The code would be reviewed by members of the community interested in development, instead of sysops. Sysops can still control which gadgets they enable by default etc.
+",1422672168,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968958, @Steinsplitter wrote:
+>>>! In T71445#968625, @Krenair wrote:
+>> All currently-on-wiki gadgets/scripts need to go through some form of pre-deployment code review. Not just popular ones.
+> 
+> Can we please establish community consensus before implanting such a code review. This sounds like a huge change.
+
+Huge yes, but if done it'd basically be a CONEXCEPT type of thing as this would be for technical code security and quality reasons.
+
+(Just in case it's not clear, this is with my technical volunteer hat on. My opinion only, etc.)",1421792603,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968479, @Ricordisamoa wrote:
+> I know this has probably been discussed before
+
+Yes, about a thousand times. Could you volunteer to read the past discussions (linked in task description) and summarise them in the task description, please?",1420973512,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968625, @Krenair wrote:
+> All currently-on-wiki gadgets/scripts need to go through some form of pre-deployment code review. Not just popular ones.
+
+Can we please establish community consensus before implanting such a code review. This sounds like a huge change.",1420964445,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968625, @Krenair wrote:
+> All currently-on-wiki gadgets/scripts need to go through some form of pre-deployment code review. Not just popular ones.
+
+Can we please establish community consensus before implanting such a code review. This is a HUGE change.",1420964424,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,All currently-on-wiki gadgets/scripts need to go through some form of pre-deployment code review. Not just popular ones.,1420921204,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,All currently-on-wiki gadgets/scripts need to go through some fprm of pre-deployment code review. Not just popular ones.,1420921187,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968494, @Steinsplitter wrote:
+>>>! In T71445#968479, @Ricordisamoa wrote:
+>> I know this has probably been discussed before, but... what about hosting gadgets via Git/Phabricator?
+>> At least the largest ones will benefit from more thorough review.
+> 
+> This is something else. Hosting highly popular gadgets like HotCat makes sense imho, :)
+
+But then we wouldn't need any on-wiki ""code-review process"".",1420913210,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968479, @Ricordisamoa wrote:
+> I know this has probably been discussed before, but... what about hosting gadgets via Git/Phabricator?
+> At least the largest ones will benefit from more thorough review.
+
+This is something else. Hosting highly popular gadgets like HotCat makes sense imho, :)",1420909334,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I know this has probably been discussed before, but... what about hosting gadgets via Git/Phabricator?
+At least the largest ones will benefit from more thorough review.",1420908816,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968415, @Nemo_bis wrote:
+>>>! In T71445#958792, @MZMcBride wrote:
+>> the list is in T71445#742344.
+> 
+> Anything that begins with «To take English wikipedia as an example» is IMHO irrelevant for a bug whose summary is ""on Wikimedia sites"".
+
+Exactly. For example, on commons are only a few coders who are keeping up scripts (fixing bugs, deprecated code etc.)  Implanting a code review in such a case makes coder unhappy.",1420907837,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#958792, @MZMcBride wrote:
+> the list is in T71445#742344.
+
+Anything that begins with «To take English wikipedia as an example» is IMHO irrelevant for a bug whose summary is ""on Wikimedia sites"".",1420905083,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#956103, @Nemo_bis wrote:
+> I feel this report is //un cane che si morde la coda//. Unless someone summarises the (relevant parts of the) discussion above and in the linked threads, I propose to close this invalid.
+
+Closing this issue as invalid would probably be the wrong choice as I think the issue is both real and unresolved.
+
+I can't quote Jon's list of action items above (the quote button is disabled for some godforsaken reason), but the list is in T71445#742344.",1420605953,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#957894, @Aklapper wrote:
+> [Please do not add otherwise contentless ""+1"" comments as they create notifications for everybody. Use tokens or flags instead. Thanks.]
+
+-1",1420577858,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"[Please do not add otherwise contentless ""+1"" comments as they create notifications for everybody. Use tokens or flags instead. Thanks.]",1420571578,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#956103, @Nemo_bis wrote:
+> I feel this report is //un cane che si morde la coda//. Unless someone summarises the (relevant parts of the) discussion above and in the linked threads, I propose to close this invalid.
+> 
+> We already have separate, actionable reports (and sometimes RfC) for things like JavaScript validation and granularity of sysop permissions.
+
++1",1420535434,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I feel this report is //un cane che si morde la coda//. Unless someone summarises the (relevant parts of the) discussion above and in the linked threads, I propose to close this invalid.
+
+We already have separate, actionable reports (and sometimes RfC) for things like JavaScript validation and granularity of sysop permissions.",1420491129,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#742556, @Qgil wrote:
+> @eloquence proposed to investigate the idea of Phabricator with a web based interface for editing files, as a possibility to bring easy-as-in-editing-text development closer to proper code review and continuous integration with automated QA.
+> 
+> We checked upstream, but generally speaking they are not enthusiastic with the idea. See their reasoning at https://secure.phabricator.com/T6008#7
+> 
+> For different reasons, @Legoktm proposed to go back to the idea of a MediaWiki-based code review...
+
+Now that this task is here, let me add #Code-Review just to make sure that people interested in code review in Phabricator know about this discussion.
+",1417697095,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think the effort of bringing all developers under the same roof is worth, and mediawiki.org is the right roof. 
+
+But going back to the definition of the sane code-review process, some ideas came up from a casual email chat. Summary in sequential order:
+
+Erik proposed to investigate the idea of Phabricator with a web based interface for editing files, as a possibility to bring easy-as-in-editing-text development closer to proper code review and continuous integration with automated QA.
+
+We checked upstream, but generally speaking they are not enthusiastic with the idea. See their reasoning at https://secure.phabricator.com/T6008#7
+
+For different reasons, Legoktm proposed to go back to the idea of a MediaWiki-based code review. Let me paste:
+
+""(...) we could just put a revision id in the gadget definition:
+
+""scripts"": {""foo.js"": 123, ""bar.js"": 456},
+""styles"": {""baz.css"": 789},
+
+Or something like that. So anyone can edit (maybe still restricted by
+a userright or maybe not) the JS/CSS pages, but their changes don't
+actually take effect until the gadget definition is updated by someone
+with those rights (+2). This allows us to take advantage of wiki
+process like be bold, revert, discuss, but still impose a review
+requirement by someone with ""+2"" rights. In some ways it's like SVN.""
+
+As Legoktm explain, there is a precedent of this type of process in the workflow for approving EventLogging schemas, where many can edit the schemas but only a few can point to a new version (the +2 equivalent).
+
+https://www.mediawiki.org/wiki/Extension:EventLogging/Guide#Peer_review",1409846486,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Quim Gil from comment #30)
+> mediawiki.org please. I'm happy to discuss the reasoning wherever
+> corresponds.
+Ideally both global user scripts and global gadgets should be in the same wiki (but Meta is already in use for the first, so going to another wiki will require migration - which is easy enough: 1. inform users; 2. import any /global.js/css from Meta, with history; 3. delete the old ones from Meta).
+
+Anyway, both Meta and mw.org have Translation extension installed, which will help creating multilingual documentation in a consistent way for popular gadgets.",1409246367,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Helder from comment #29)
+> using a single common wiki would be the best - whatever wiki is choosen -
+
+mediawiki.org please. I'm happy to discuss the reasoning wherever corresponds.",1409245878,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"What about creating the ""Gadget developer"" user group on WMF wikis, with the user rights which are currently given to sysops (edituserjs, editusercss and editinterface - which gerrit change 154452 splits into 'editsitejs' and 'editsitecss') and, later, also the user rights introduced by Gadgets 2.0 (see the links mentioned on comment 17).
+
+Then, send an announcement recommending communities to evaluate whose of their sysops should indeed have the permissions to edit JavaScript and CSS and add them to the new user group, and after a reasonable amount of time, remove the user rights from sysops on WMF wikis.
+
+Also, since it is recommended to keep gadgets central[1], and since now Meta-wiki is the central wiki used by extension GlobalCssJs, maybe apply any code-review process first to the editing of global gadgets hosted on Meta (some are currently hosted on mw.org or enwiki, or wikidata, but using a single common wiki would be the best - whatever wiki is choosen - and would help in the implementation of the Gadgets 2.0 when that is ready for deployment in the future).
+
+[1] https://www.mediawiki.org/wiki/ResourceLoader/Migration_guide_%28users%29#Keep_gadgets_central",1409245587,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Yann Forget from comment #27)
+> Why not do it as page correction and validation in Wikisource? It is a light
+> process, and there is no need to learn a new tool.
+> 
+> With the Proofreading page extension, 2 non-anonymous users are needed to
+> validate a page. Additionally, more right could be needed (either sysop or
+> autopatrolled).
+
+This sounds good to me. +1",1409239662,PHID-USER-nuf2sujf7qrx4v5ixbs3,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Why not do it as page correction and validation in Wikisource? It is a light process, and there is no need to learn a new tool.
+
+With the Proofreading page extension, 2 non-anonymous users are needed to validate a page. Additionally, more right could be needed (either sysop or autopatrolled).",1409235503,PHID-USER-dy7vqdheslnndi5s6r4g,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,Depends on bug 20153?,1408085526,PHID-USER-je4a7kqdfgacwkyhtg4c,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Stefan2 from comment #16)
+> I think that the problem is that the MediaWiki namespace can be edited by
+> any administrator. Many administrators do not understand what the code does,
+> as demonstrated for example by the ""~~~~"" in
+> [[szl:Special:PermanentLink/207947]], which Legoktm mentioned above. A
+> simple solution would be to remove the right to edit pages in the MediaWiki
+> namespace from administrators and instead assign it to a new group,
+> ""scripteditors"", consisting of editors who understand how the code works.
+> 
+
+> Broadly, administrators are trusted users and should be treated as such.
+
+Yes but whereas I might trust a fellow developer, I still wouldn't at all me comfortable if they +2ed their own code and this is why we have code review processes. Also I might trust an administrator in wiki things but if they are unable to use a code review tool then I wouldn't trust them to edit JavaScript. I worry that a lot of this is due to an outdated idea that JavaScript is not a real language. Ask yourself what if MediaWiki:Common.php existed and how allowing editing of code on a wiki that would make you feel...
+
+I can imagine Common.js being useful for a hobby wiki to make a few tweaks, but it really has no place on a Wikimedia wiki and we should certainly not be building code review systems to support it. Instead we should be focusing energy on making code review in mediawiki core quicker and more enticing and more regularly deploying our code.",1408039865,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to MZMcBride from comment #19)
+> In other words, if you all want to deprecate the use of MediaWiki:Common.js
+> and similar pages, you should work toward that goal. If/when the day comes
+> that they're no longer needed, then we can consider getting rid of them. But
+> this bug seems to be a bit ""cart before the horse.""
+
+Agreed, and if anyone wants to write patches that make our software more useful I will happily help merge them. Have raised bug 69550 so as not to derail this bug anymore. :)",1408032618,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to MZMcBride from comment #19)
+> Err, most of the MediaWiki namespace isn't JavaScript and CSS, it's
+> interface messages. The fact that JS and CSS pages are included in the
+> MediaWiki namespace has always been a design quirk that should probably be
+> corrected as their inclusion in the namespace is a(n) (ab|mis)use of the
+> namespace's purpose.
+
+Well yes, but there are some messages that are also a big issue. See also bug 43646",1407987309,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to C. Scott Ananian from comment #8)
+> I think that extensions and gadgets are probably the ""right"" way to make
+> sitewide changes.  Extensions already have a code review/deployment process,
+> although we can certainly work to make that smoother/easier.  Perhaps enwiki
+> could have an 'Extension:enwiki', for example, which could contain any code
+> which would otherwise live in common.js.
+
+I was thinking a bit more generic, but yeah, this might be a good idea to pursue. My thought was that you might have Extension:WikimediaScripts, which follows the pattern of E:WikimediaMaintenance and E:WikimediaMessages and E:WikimediaEvents. Inside the WikimediaScripts extension, you'd have modules that could then be loaded on a per-wiki basis.
+
+> common.js is just a weird special case that doesn't need to exist.
+
+I addressed this line of reasoning in comment 19, last paragraph. For now, there's a definite need for these pages to exist. That may not be true in the future, but it is true today.",1407985719,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Brad Jorsch from comment #9)
+> (In reply to MZMcBride from comment #6)
+>> Code is the enemy; less code is better. Rather than looking at ways to
+>> impose code review on wiki communities, we should first look for ways to
+>> centralize code (global gadgets) and we should look for ways to make the
+>> current site-wide JavaScript hacks no longer necessary.
+> 
+> While having more code in gadgets rather than in common.js is good, it's
+> orthogonal to the need for a good code review process that's actually usable
+> by wiki users. The global gadgets will still need a code review process.
+
+It would be helpful if you could explicitly specify what needs you see that you feel MediaWiki could handle well and/or that you think Phabricator could not handle well.
+
+> Wiki users might accept having to go to a Commons-like site instead of doing
+> it on their local wiki (and in the long run they'll probably have to), but
+> they're unlikely to accept something that requires they install software
+> locally, sign up for a non-SUL account, figure out ssh keys, publish an
+> email address publicly, and so on.
+
+GitHub and GitLab both allow in-browser editing now, I believe. I imagine Phabricator, which will allegedly be part of Wikimedia unified login, will also have equivalent functionality. The e-mail address is trivially solvable in Git by simply making up an e-mail address (User:Anomie@git-en.wikipedia.org), I think? And if you're using a Web browser and single unified login for authentication, you probably don't need to worry about SSH keys or installing software such as Git locally.
+
+You may be correct that there's a need here for global gadgets, but I think we need to do more to be much clearer about what that need is and how we propose to address it, assuming additional development—outside of the ongoing Phabricator work and I suppose the work to deprecate Common.js and similar pages—is needed.",1407985428,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Gilles Dubuc from comment #7)
+> The fact that people who aren't developers and/or who don't understand what
+> custom JS they're deploying to millions of users is the problem.
+
+You're basically hitting [[hard cases make bad law]] here. Most Wikimedia wikis (probably over 800 of them) do not have millions of users.
+
+> If you're not willing to learn git, you're not the right person to be
+> pushing custom JS to a top-5 website.
+
+Can we please collectively stop with the ""top-5"" bullshit? :-)  Obviously the English Wikipedia and other wikis are a consideration, but over 99% of MediaWiki wikis are not top-5 anything.",1407985318,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Stefan2 from comment #16)
+> I think that the problem is that the MediaWiki namespace can be edited by
+> any administrator. Many administrators do not understand what the code does,
+> as demonstrated for example by the ""~~~~"" in
+> [[szl:Special:PermanentLink/207947]], which Legoktm mentioned above. A
+> simple solution would be to remove the right to edit pages in the MediaWiki
+> namespace from administrators and instead assign it to a new group,
+> ""scripteditors"", consisting of editors who understand how the code works.
+
+Err, most of the MediaWiki namespace isn't JavaScript and CSS, it's interface messages. The fact that JS and CSS pages are included in the MediaWiki namespace has always been a design quirk that should probably be corrected as their inclusion in the namespace is a(n) (ab|mis)use of the namespace's purpose.
+
+Broadly, administrators are trusted users and should be treated as such.
+
+Whether the rest of the MediaWiki namespace is needed is also debatable nowadays, but probably also outside the scope of this ticket.
+
+> I think that some code should be removed from Common.js files and moved to
+> MediaWiki core instead. For example, [[sv:MediaWiki:Common.js]] contains
+> code fixing incorrect sorting of text in tables (search for
+> ""tableSorterCollation""). Every user of MediaWiki would want text to be
+> sorted correctly, so I don't see why this couldn't be in MediaWiki core
+> instead.
+
+Yes, for sure. I made a similar comment above (comment 6). We should figure out why these pages are still needed and work to address that by putting the functionality in MediaWiki core or in an extension. I think this is a better use of time than proposing trashing the functionality.
+
+In other words, if you all want to deprecate the use of MediaWiki:Common.js and similar pages, you should work toward that goal. If/when the day comes that they're no longer needed, then we can consider getting rid of them. But this bug seems to be a bit ""cart before the horse.""",1407984367,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Eran Roz from comment #13 and comment #14)
+> I just runned a simple phantomjs script on all wikipedia languages to catch
+> simple errors:
+> 
+> [...]
+
+Thanks for this. I split this out to bug 69519.",1407983890,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Gadgets 2.0 (T31272) introduces new user rights specific for edit/management of gadgets:
+https://www.mediawiki.org/wiki/ResourceLoader/Version_2_Design_Specification#User_rights
+See also this discussion about which users (user groups) should have each permission:
+https://www.mediawiki.org/wiki/Thread:Talk:ResourceLoader/V2_testing/Questions_about_permission_model_and_developer_workflow",1430821452,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Gadgets 2.0 introduces new user rights specific for edit/management of gadgets:
+https://www.mediawiki.org/wiki/ResourceLoader/Version_2_Design_Specification#User_rights
+See also this discussion about which users (user groups) should have each permission:
+https://www.mediawiki.org/wiki/Thread:Talk:ResourceLoader/V2_testing/Questions_about_permission_model_and_developer_workflow",1407966302,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think that the problem is that the MediaWiki namespace can be edited by any administrator. Many administrators do not understand what the code does, as demonstrated for example by the ""~~~~"" in [[szl:Special:PermanentLink/207947]], which Legoktm mentioned above. A simple solution would be to remove the right to edit pages in the MediaWiki namespace from administrators and instead assign it to a new group, ""scripteditors"", consisting of editors who understand how the code works.
+
+I think that some code should be removed from Common.js files and moved to MediaWiki core instead. For example, [[sv:MediaWiki:Common.js]] contains code fixing incorrect sorting of text in tables (search for ""tableSorterCollation""). Every user of MediaWiki would want text to be sorted correctly, so I don't see why this couldn't be in MediaWiki core instead.",1407964090,PHID-USER-zcvchmenkrawdr5233in,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,Eran Roz: please fill bug report for all such issues. This way they can be triaged / assigned to the proper persons and will be easier to track than this bug which is merely for discussion.,1407956393,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Created attachment 16185
+Example for errors across wikis
+
+Maybe it is a bit off-topic but here are some cases of errors across wikis in simple read/edit transaction using phantomJS
+
+**Attached**: {F14648}",1407955361,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think code review isn't the solution, as it is probable that no one will review the code for small wikis. 
+However it would be great to have automated tests running after changes in common.js and gadgets. Such general tests can at least validate no external resource is loaded, or no invalid syntax is added.
+The simplest option is to run it outside MW (such as a script in labs that runs X times a day), but an extension to do it while editing would be even better...
+
+BTW
+I just runned a simple phantomjs script on all wikipedia languages to catch simple errors:
+
+testing als
+ERROR: ReferenceError: Can't find variable: ta
+TRACE:
+ -> https://als.wikipedia.org/w/index.php?title=MediaWiki:If-pt-login.js&action=raw&ctype=text/javascript&dontcountme=s: 9
+
+testing kk
+ERROR: TypeError: 'null' is not an object (evaluating 'document.getElementById('mw-vector-current-variant').innerHTML=wgULS(""Кирил"",""Latın"",""توتە"")')
+TRACE:
+ -> https://bits.wikimedia.org/kk.wikipedia.org/load.php?debug=false&lang=kk&modules=site&only=scripts&skin=vector&*: 9
+
+
+anyone wants to fix them? :)",1407951117,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I don't think MediaWiki should invent its own code review software. I completely agree with every Gilles Dubuc and C. Scott said above.
+
+Code review software is /hard/ to build and for us to build it would 1) be a waste of resources and 2) be suboptimal.
+
+
+That aside, The existing MediaWiki:Common.js is a serious hack and huge security hole that I can't believe has not been exploited yet and we really should be thinking about better ways to replace it with something else.
+
+I too think Gadgets and extensions are the place for these things. Anything site wide should be in an extension, anything goes in a gadget as long as user has the choice to opt into it.
+
+MZMcBride is spot on and makes a good suggestion that we should be starting at the source.
+To take English wikipedia as an example [1]
+When I look through the code I see:
+
+* Main page layout fixes - why is this code running across the entire site?
+* A redirect script that sends User:Name/skin.js to User:Name/skin.js to vector.js or monobook.js - again why is this running across the entire site and not a feature of the software?
+* Some deprecation notices... shouldn't deprecation happen in the software?
+* Then a bunch of imported scripts:
+** if you are on an edit page 'MediaWiki:Common.js/edit.js'
+** on the watchlist MediaWiki:Common.js/watchlist.js
+** on the file page MediaWiki:Common.js/file.js
+
+At this point I gave up reading. All these indicate to me is that there are holes in the software that need fixing for all users and are being neglected to be fixed in the software because ""code review is too cumbersome"". This is completely irresponsible and upsets me. We should be striving to make MediaWiki as customisable and flexible as possible without having hacky compromises like this.
+
+""sysops are going to download and learn to use git."" if a person is not able to learn git then personally I worry about them tinkering with software that hits site wide. Tinkering with gadgets that are available for opt in is a great thing and I believe important for community innovation but site wide just scares me.
+
+My suggested way forward would be:
+* Audit all uses of Common.js
+* Open bugs for all the problems they are solving (I think we'll be surprised at how much overlap there is between projects)
+* Work with the community to fix the issues in the software they have identified in Common.js and remove the code from Common.js. In doing so build up a trust that through code review we can fix things just as quickly and better without resorting to needing a wikipage.
+* With a cleaner Common.js wikipage and better process see the wood through the trees and reevaluate what we need this page for.
+
+[1] https://en.wikipedia.org/wiki/MediaWiki:Common.js",1407944364,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Brad Jorsch from comment #9)
+> ...
+> they're unlikely to accept something that requires they install software
+> locally, sign up for a non-SUL account, figure out ssh keys, publish an
+> ...
+FYI: we might have SUL for Phabricator:
+http://fab.wmflabs.org/T314",1407942287,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Notice that many wikis have migrated code from Common.js to default gadgets (e.g. for modularization, to allow users to disable functionality, to make debugging easier, to allow importing specific parts from other wikis, etc), and others also load subpages like Common.js/edit.js, Common.js/watchlist.js, Common.js/IEFixes.js, etc..
+
+Wikimedia Commons for example has 17 gadgets enabled for everyone by default. See more stats on
+https://meta.wikimedia.org/wiki/Gadgets",1407942078,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Gilles Dubuc from comment #7)
+> The fact that people who aren't developers and/or who don't understand what
+> custom JS they're deploying to millions of users is the problem. It's not a
+> situation that needs to be perpetuated through dumbed-down on-wiki code
+> review.
+
+I've heard that same argument as to why wikitext is better than VisualEditor. I didn't agree then, and I don't agree now: making the process technically difficult to try to discourage ""unqualified"" contributors isn't a very well-targeted heuristic. Even if the people affected are smart enough to be able to figure out the process, they may well decide the effort isn't worth it.
+
+
+(In reply to MZMcBride from comment #6)
+> Code is the enemy; less code is better. Rather than looking at ways to
+> impose code review on wiki communities, we should first look for ways to
+> centralize code (global gadgets) and we should look for ways to make the
+> current site-wide JavaScript hacks no longer necessary.
+
+While having more code in gadgets rather than in common.js is good, it's orthogonal to the need for a good code review process that's actually usable by wiki users. The global gadgets will still need a code review process.
+
+Wiki users might accept having to go to a Commons-like site instead of doing it on their local wiki (and in the long run they'll probably have to), but they're unlikely to accept something that requires they install software locally, sign up for a non-SUL account, figure out ssh keys, publish an email address publicly, and so on.
+
+FlaggedRevs isn't a good model, because we need merging of proposed changes rather than a linear history. I don't know whether CodeReview will do pre-commit review, which is probably a necessity.",1407941889,PHID-USER-uqcn2l4ng4murmyfnvyp,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think that extensions and gadgets are probably the ""right"" way to make sitewide changes.  Extensions already have a code review/deployment process, although we can certainly work to make that smoother/easier.  Perhaps enwiki could have an 'Extension:enwiki', for example, which could contain any code which would otherwise live in common.js.  On github, at least, proposing a new change would be as easy as going to the 'common.js' file inside the Extension:enwiki respository and clicking 'edit', which takes care of forking, branching, commiting, and submitting a pull-request.
+
+Gadgets don't really have a good review mechanism at the moment.  I think this bug could concentrate on reviews for gadgets;  common.js is just a weird special case that doesn't need to exist.",1407941069,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"The fact that people who aren't developers and/or who don't understand what custom JS they're deploying to millions of users is the problem. It's not a situation that needs to be perpetuated through dumbed-down on-wiki code review. Like MZ just described, if there's a way to remove the bulk of the need for these users to deploy custom JS, it should be explored first.
+
+And for whatever JS is left that can't be standardized into a global gadget repository (I haven't looked at the code, but I imagine there will always be ""that specific thing that can't be done differently""), community members with appropriate skills should be doing it. If you're not willing to learn git, you're not the right person to be pushing custom JS to a top-5 website. Even if you don't want to learn or don't have time to, it just means that you need to enlist the help of someone who knows about this stuff. Right now that step doesn't exist and irresponsible actions are being taken by people who are just unaware of what they're doing.
+
+I think that a ""simple mode"" review tool is also likely to make the uneducated people sending JS they don't understand less likely to learn to master what they're doing. As such it wouldn't be code review, it would be ""please make this thing I don't understand work and deploy it"", which puts all the workload burden on the reviewer, instead of being the 2-way street code review should be.",1407939353,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I'm not sure this problem is being approached in the best way. I think it would be helpful to look at use-cases and work backward from there. Why are administrators adding custom site-wide JavaScript?
+
+Looking through [[MediaWiki:Common.js]], for example, it seems as though a lot of code is deprecated and could be removed once de-referenced. The non-deprecated code should probably exist in MediaWiki core or in a MediaWiki extension, if it's generally useful functionality.
+
+Code is the enemy; less code is better. Rather than looking at ways to impose code review on wiki communities, we should first look for ways to centralize code (global gadgets) and we should look for ways to make the current site-wide JavaScript hacks no longer necessary.
+
+(In reply to Zell Faze from comment #4)
+> I think the community would likely reject attempts to use git or gerrit. 
+> Whatever this system is, it will need to be implemented within Mediawiki. 
+> People have a hard enough time leaving their home wiki, I seriously doubt
+> that most sysops are going to download and learn to use git.
+
+A smart front-end could mask that the user is using Git. I'm thinking about an interface similar to in-browser editing in the GitHub front-end. But again, I'd like us to more closely look at the underlying use-cases first.",1407934687,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Indeed. This definitely must be implemented ""inside"" MediaWiki (whatever the backend we use, the UI must be displayed within regular MediaWiki pages) if it is supposed to be used by MediaWiki users and not MediaWiki developers.",1407931671,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think the community would likely reject attempts to use git or gerrit.  Whatever this system is, it will need to be implemented within Mediawiki.  People have a hard enough time leaving their home wiki, I seriously doubt that most sysops are going to download and learn to use git.
+
+Though Flaggedrevs is weird, I personally think that it, or something like it, is the way to go.  The learning curve of it is less than that of git and gerrit, and I'm sure some sort of bridge could be made that would allow running of tests on code submitted there.
+
+I feel like any system outside of Mediawiki would stifle each communities autonomy, something that in recent weeks we've seen they care an awful lot about.",1407930580,PHID-USER-2qzpsivaeuezrxqtzhwn,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Why can't we just do this the same way as our current status quo (gerrit) or the soon-to-be status quo (phabricator)? Less systems that do the same thing to maintain...
+
+Some volunteers have +2 on our projects, this is the same situation except that we need to find more volunteer reviewers than usual, because we don't have the bandwidth to review this at the moment.
+
+IMHO if the code review process we normally undergo feels heavy to impose on this audience, it just needs that we need to improve the process. If it becomes easier to outsiders, it benefits all projects.",1407927917,PHID-USER-papbtlagfolot4dzerne,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Would it make sense to use git / phabricator ?   We will have to convince the community that a pre commit review workflow is a good thing, but that would let us run validation tests and deploy on some staging area before rolling changes to production.
+
+I am very skeptical at our ability to code and maintain a review system in MediaWiki, we have past experiences:
+
+- CodeReview extension for svn could have been nice if we had the ability to devote time to it, it turned out to be simpler to delegate the software to third party (Gerrit, soon Phabricator). 
+
+- FlaggedRevs which would let one validate revisions before they were made public. I don't think anyone regret it. I found the workflow / UI etc terrible and never understood how it worked.
+
+
+Also, we could use such a review system for Gadgets and LUA modules.  When writing, versionning and collaborating on code, ones need a version control system. git comes to mind.",1407876357,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"This would need to be done differently from how FlaggedRevisions currently is implemented (as in FR you still submit a new version which is directly being used by eg. ResourceLoader).
+
+I would suggest to have a new extension in which edits can basically be suggested like github pull requests and then get merged/ commented on/ rejected by a reviewer.
+
+Mid to long term this process should be centralized and managing JS/CSS should move away from the Wikis into a central place (that can be a MediaWiki, but IMO doesn't necessarily have to be one).",1407873356,PHID-USER-2mey32xhshfnf7rz7jjn,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+VisualEditor: Reconsider whether you should be able to replace a selected node by typing / insertion tools,"Intention:
+Attempting to replace a formula with text by selecting the formula does not work.  Simply nothing happens.  Either typing or pasting has the same null effect.  Attempting to replace a formula by inserting a template results in the template being inserted after the formula, not instead of it.
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407805620,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-cjqylbv337cm23t2r2z6,task_description,open
+VisualEditor: Reconsider whether you should be able to replace a selected node by typing / insertion tools,"(In reply to Spinningspark from comment #0)
+> Intention:
+> Attempting to replace a formula with text by selecting the formula does not
+> work.  Simply nothing happens.  Either typing or pasting has the same null
+> effect.  Attempting to replace a formula by inserting a template results in
+> the template being inserted after the formula, not instead of it.
+
+Yes, this is intentional. We could reconsider it but I worry that the additional slowness to support certain broken browsers in this respect (I believe the main issue here is Firefox) is not worth the minor user experience improvement.
+
+Note that the ""delete"" and ""backspace"" keys still work to delete the selection.",1415882261,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cjqylbv337cm23t2r2z6,task_subcomment,NA
+"VisualEditor: in the image advanced settings dialog, ""Wrap text around this item"" looks like a label of the alignment buttons","The ""Wrap text around this item"" checkbox appears above the the alignment buttons and looks like a label for these buttons. The button group doesn't have a label of itself. It should be moved around somehow so the separation between them will be clear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407316440,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-bbylgmiwgkujcoiek33q,task_description,open
+"VisualEditor: in the image advanced settings dialog, ""Wrap text around this item"" looks like a label of the alignment buttons","Change 152054 abandoned by Amire80:
+Move the wrapping checkbox under the alignment buttons
+
+https://gerrit.wikimedia.org/r/152054",1415713370,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bbylgmiwgkujcoiek33q,task_subcomment,NA
+"VisualEditor: in the image advanced settings dialog, ""Wrap text around this item"" looks like a label of the alignment buttons","Change 152054 had a related patch set uploaded by Amire80:
+Move the wrapping checkbox under the alignment buttons
+
+https://gerrit.wikimedia.org/r/152054",1407329770,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bbylgmiwgkujcoiek33q,task_subcomment,NA
+"VisualEditor: in the image advanced settings dialog, ""Wrap text around this item"" looks like a label of the alignment buttons","... Also, it's on by default, so that's another reason not to put it on the top.",1407316562,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-bbylgmiwgkujcoiek33q,task_subcomment,NA
+VisualEditor: Main application namespace should be capitalised and not 2 characters short (ve -> VisualEditor),"Let's rename our global namespace to something longer than 2 characters and not identified by lowercase characters.
+
+Proposing VisualEditor instead of 've'.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1404778500,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jslvrd4uihevdc3j7qsn,task_description,declined
+VisualEditor: Main application namespace should be capitalised and not 2 characters short (ve -> VisualEditor),"Lowercase globals aren't ideal, but I think the ship has sailed on this for both `ve` and `mw`. Not worth messing with.",1530906840,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-jslvrd4uihevdc3j7qsn,task_subcomment,NA
+VisualEditor: Only display the wikitext warning once per session,"1. '[[' to a paragraph and dismiss the wikitext warning
+2. type in another paragraph then re-focus the [[ paragraph and type
+3. the wikitext warning returns
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403710500,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-xgn6yi4nvtbkl7ouzmwj,task_description,declined
+VisualEditor: Only display the wikitext warning once per session,"Displaying it once per session...? Per James, this is a wontfix I think.",1403811741,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-xgn6yi4nvtbkl7ouzmwj,task_subcomment,NA
+VisualEditor: Only display the wikitext warning once per session,Not sure that this is not a WONTFIX. We don't really want it to be lost on users that they're Doing It Wrong™. :-),1403741735,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xgn6yi4nvtbkl7ouzmwj,task_subcomment,NA
+VisualEditor: Provide a way to make images default sized without invoking a dialog,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403637300,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-ysksgctttx7kwjm25imt,task_description,open
+VisualEditor: Provide a way to make images default sized without invoking a dialog,"or it could be a spot in the resize steps which replaces the ""XXX x XXX"" with ""Default size"" There are any number of options.",1403748049,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-ysksgctttx7kwjm25imt,task_subcomment,NA
+VisualEditor: Provide a way to make images default sized without invoking a dialog,"(In reply to Jared Zimmerman (WMF) from comment #1)
+> updated the title to not jump to the conclusion of how this should be done,
+> not sure if a button is the right answer,
+
+An ""action button"" is the ""set … without invoking image settings dialog"" UX concept in VE…",1403746116,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ysksgctttx7kwjm25imt,task_subcomment,NA
+VisualEditor: Provide a way to make images default sized without invoking a dialog,"updated the title to not jump to the conclusion of how this should be done, not sure if a button is the right answer,",1403745680,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-ysksgctttx7kwjm25imt,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"When editing, ""default size"" in mw prefs is not honored.",1403637120,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-qbjbd5yessxi474lujxf,task_description,resolved
+VisualEditor: Image should not change size when going from read to edit,"Change 499330 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Respect user preference for default thumbnail size while editing
+
+[[https://gerrit.wikimedia.org/r/499330]]",1553645145,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"Change 499330 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] Respect user preference for default thumbnail size while editing
+
+[[https://gerrit.wikimedia.org/r/499330]]",1553635131,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,http://en.wikipedia.beta.wmflabs.org/wiki/Thumbnail_size2 / http://en.wikipedia.beta.wmflabs.org/api/rest_v1/page/html/Thumbnail_size2,1455138940,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"This really looks like it would be a simple fix. Parsoid sets `class=""mw-default-size""` on the `<figure>` elements if no explicit size was given, and VE already knows user's preferred thumbnail size.",1455138918,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"This issue has been pointed on fr.wp too.
+With the given example I see the image 1.66 bigger while reading than while editing.",1444936861,PHID-USER-unpoeiyj52rmcfqi5rbw,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"I'd like to revisit this, the current behavior is actively against the WYSIWYG model established in VE. I'm still not understanding the argument against this. If images are the same size both in read and edit mode, how will this contribute to editors wanted to resize them to ""look right for them"" if they already look correct? if anything this seems like it would lessen the desire to fiddle with image sizes.",1411066314,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"I think I might be being unclear with the request…
+
+
+As a user who sets my thumbnail preference to (120/180/220/250/300/etc)px while in visual editor I see ""default sized"" thumbnails display as (120/180/220/250/300/etc)px depending on my preference. 
+
+I'm not sure I understand your point ""we actively don't want people resizing images to look ""right"" for them, which this would encourage."" which is the exact opposite of what this would do, if the images LOOK right when i get to VE then I'm much less likely to go on a resizing spree.",1405968043,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"(In reply to Jared Zimmerman (WMF) from comment #2)
+> I think i might have been unclear on this one. 
+> 
+> The gist is ""Image should not change size when going from read to edit""
+> 
+> there are many possible fixes, but the one that seemed simplest was, for
+> images which are at ""default"" size, look at users preference for what size
+> ""default"" is and display them at that size when in edit mode.
+
+And as I said, we have intentionally chosen not to do this.
+
+> there might be other options, but the bug is that they change, size at all.
+
+The simplest ""fix"" to this issue is to remove the user preference. But you probably don't want that.",1403746069,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"I think i might have been unclear on this one. 
+
+The gist is ""Image should not change size when going from read to edit""
+
+there are many possible fixes, but the one that seemed simplest was, for images which are at ""default"" size, look at users preference for what size ""default"" is and display them at that size when in edit mode.
+
+there might be other options, but the bug is that they change, size at all.",1403745950,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"This is verging on a WONTFIX; we actively don't want people resizing images to look ""right"" for them, which this would encourage.",1403741652,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor:  Please strip trailing spaces and returns from media or image captions,"The solution for this may be related to Bug 61049:
+
+If you add a caption to an image, and you press return in the text area box at the end (perhaps several times), then the caption includes those pointless blank lines, which makes for ugly wikitext when the page is saved.
+
+See https://en.wikipedia.org/w/index.php?title=Sugar_candy&diff=613063549&oldid=611921250
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403032080,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-etg24hhx2qupzouy5rnw,task_description,open
+VisualEditor:  Please strip trailing spaces and returns from media or image captions,"I got bit by this bug again:  https://ca.wikipedia.org/w/index.php?title=Cloïssa_gegant&diff=prev&oldid=17846863 
+
+Ed, does this really need a general solution?  I'd be happy to limit it to just text that's entered into a dialog.",1481143532,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-etg24hhx2qupzouy5rnw,task_subcomment,NA
+VisualEditor:  Please strip trailing spaces and returns from media or image captions,"The same is true for the main document, but I'd rather issue warnings than do automatic document modification (cf. typing wikitext into VE)",1403033540,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-etg24hhx2qupzouy5rnw,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Go to this page:
+
+https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&oldid=87309
+
+Change the first image from Thumbnail to Basic and click on ""Apply Changes""
+The following error appears in the console and cannot save page or cancel editing the page with VE.
+ 
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 55
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402704660,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5cganofaldk4meetlmoe,task_description,resolved
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,Me neither.,1530051678,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,This seems to work correctly now. I can't reproduce any of the issues described here.,1530046412,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Now if I follow the minimal wikitext or the steps to reproduce in a page and try to change the first image from thumbnail to Basic, it moves the image inside the caption of the second image.
+
+Is that how we want it now?",1405546742,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Change 144136 merged by jenkins-bot:
+Fixes to getRelativeOffset and getRelativeRange
+
+https://gerrit.wikimedia.org/r/144136",1405445154,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Change 144136 had a related patch set uploaded by Esanders:
+Fixes to getRelativeOffset and getRelativeRange
+
+https://gerrit.wikimedia.org/r/144136",1405019099,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Change 144004 merged by jenkins-bot:
+Skip over nested handlesOwnChildren nodes in getRelativeOffset
+
+https://gerrit.wikimedia.org/r/144004",1404418515,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Change 144004 had a related patch set uploaded by Esanders:
+Skip over nested handlesOwnChildren nodes in getRelativeOffset
+
+https://gerrit.wikimedia.org/r/144004",1404415212,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"first case works perfectly in master
+second case still results in the image being deleted",1404408749,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"On test 2 wiki:
+the first case still throws an exception
+the second 'minimal' case results in the image being deleted",1404408560,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Marking as theoretically fixed, then. :-)",1404330575,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"I... can no longer reproduce this. I tried the steps in comment 3 as well as the wiki page in comment 2. Maybe this got fixed by Ed's selection-after-deletion fix? Because when we change an image from block to inline, we delete the old image and insert a new one.",1404329684,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Found the steps to reproduce it from VE :D
+
+1.Open a page with VE
+2.Insert an image, keep it thumbnail-right
+3.Go to next line of the added image by pressing enter
+4.Add another image on the next line, make it frameless right
+5.Now in the caption of the second image : Add another image and go to the next line of this image by pressing enter
+6.Add anything on the next line of the caption
+7.Apply changes
+8.Save Page
+7.Reopen the page
+8.Try to make the first image Thumbnail to Basic
+
+Observed Result:
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 55
+appears in the console and cannot cancel the edit or save the page in VE",1403120797,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"This is the minimum wikitext required to reproduce this issue:
+[[File:MO-supp-K.svg|thumb]]
+[[File:IMA-johnson1.jpg|right|frameless|
+
+[[File:S.M.R.JPG|thumb]]
+{{Cite web|url = http://yahoo.com|title = }}
+
+]]
+
+You can try on this page:
+https://test2.wikipedia.org/wiki/Test66604?veaction=edit",1403119407,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"The problem seems to be in ve.ce.Document.prototype.getNodeAndOffset() where the stack ends up empty but the element is not a slug.
+
+I am pretty certain this happens due to the image with the complex caption that includes {{Cite}} <math> <ref> and another image inside it. My attempts to sanitize the wikitext and try everything one-by-one failed when I added that piece: 
+
+
+[[File:MO-supp-K.svg|thumb]]
+[[File:MO-supp-K.svg|thumb]]
+[[File:IMA-johnson1.jpg|right|frameless|caption
+<ref>{{Cite web|url = http://yahoo.com|title = }}</ref>
+
+<ref>reference</ref>{{Citation needed}}
+
+<math>\pi</math>
+[[File:S.M.R.JPG|thumb]]
+
+{{Cite web|url = http://yahoo.com|title = }}
+
+]]",1402939454,PHID-USER-zq6nzfwxwkyliljd4lfy,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+[DO NOT USE] Additional keyboard shortcuts (tracking) [superseded by #VisualEditor-EditingTools],"(Now tracked as part of #VisualEditor-EditingTools.)
+
+More keyboard shortcuts help users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401473640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qhfyvgtoq7dd2wahxu7j,task_description,invalid
+[DO NOT USE] Additional keyboard shortcuts (tracking) [superseded by #VisualEditor-EditingTools],[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343615,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-qhfyvgtoq7dd2wahxu7j,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400886180,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-xiestiqvpxbtrw7ppizw,task_description,duplicate
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"A <br /> could be inserted when the user uses Shift + Enter (line break instead of change of paragraph).
+This would be consistent with word processor software.",1487757747,PHID-USER-mapumhlp3gw5qefhvafn,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Where do we draw the line about being paternalistic and disallowing users to do things they want to do but we don't think are ""good code"" or ""stylistically wrong"" it seems like in many cases we go to great lengths to make things possible or easy even if we think the outcome may be that users misuse or use in unexpected ways and other times we block on them by saying we don't want to be enablers of bad behavior. Curious in this case how that logic is applied to do, or not do this?",1403742826,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"(In reply to Jared Zimmerman (WMF) from comment #7)
+> Two possible proposals that we could use one, both, or some variations
+> 
+> When consecutive breaks are found we could use
+> 
+> <br>
+> <br>
+> 
+> which is what you'll commonly see on wikipages when people are trying to do
+> some advanced formatting
+
+… and is horrendous and explicitly deprecated.
+
+> if the <br> is followed by a [[template]] or == Section == we could strip
+> out any <br> and replace with {{Clear}}
+
+This is verging on a WONTFIX, but leaving as a possible thing for later consideration.",1403742521,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Two possible proposals that we could use one, both, or some variations
+
+When consecutive breaks are found we could use
+
+<br>
+<br>
+
+which is what you'll commonly see on wikipages when people are trying to do some advanced formatting
+
+if the <br> is followed by a [[template]] or == Section == we could strip out any <br> and replace with {{Clear}}",1402335045,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,Closing temporarily as there's no proposed action. Please feel free to re-open.,1402328468,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Unfortunately MediaWiki has no representation of a blank paragraph, so they get destroyed when you save.
+
+We could theoretically not let you insert a second new line (so ""enter"" in a blank paragraph does nothing), and though this is an extant UX in the wild – LyX does this because LaTeX has the same limitation – I think it's pretty crummy, and probably worse than the current behaviour.
+
+What would you expect to happen?",1402015126,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Created attachment 15503
+post-save
+
+**Attached**: {F13877}",1401302297,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Created attachment 15502
+pre-save
+
+**Attached**: {F13876}",1401302265,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"go to https://en.wikipedia.org/wiki/User:Jaredzimmerman_%28WMF%29/VEtest
+
+1. place cursor after ""line 1""
+2. press enter/return on keyboard twice
+3. save page
+
+expected : there will be two blank lines after ""line 1""
+actual: there are no blank lines after ""line 1""
+
+see attached images for pre and post save appearance.",1401302215,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Please provide steps to reproduce - no idea at which stage/keyboard focus I press some key on my keyboard, and which browsers this was tested with
+
+Please see https://www.mediawiki.org/wiki/How_to_report_a_bug",1401102456,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Allow editing of a category link (not just add/remove),"In the page options menu, you can add a category by typing its name in the ""add a category"" box and delete a category by clicking the the trash icon in the category inspector. However it's not currently possible to **edit** the name of the category.
+
+For example, if the page is currently in [[Category:Admirals of World War I]] and I want to put it in [[Category:Admirals of World War II]], I can do that easily in the wikitext editor by simply typing an extra ""I"".  In VisualEditor, I have to completely delete the first category and then add the second from scratch.",1400565600,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-miv67zvinnq5ma6mdz7k,task_description,open
+VisualEditor: Allow editing of a category link (not just add/remove),"This was just mentioned to me by an experienced editor as the #1 reason why he doesn't use the VE much. I was about to report it, and found that not only it's already reported, but that it's reported by myself :)",1548593910,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-miv67zvinnq5ma6mdz7k,task_subcomment,NA
+VisualEditor: Allow editing of a category link (not just add/remove),"{F4221948}
+
+Being able to edit this would make a big difference for UX. Right now it's border-line inaccessible to make the intended change.
+
+Additionally, the label is not selectable by cursor. The category object is shielded from text selection for some reason, requiring the user to retype it from scratch. This gets worse with T139189.",1467394682,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-miv67zvinnq5ma6mdz7k,task_subcomment,NA
+VisualEditor: Allow editing of a category link (not just add/remove),"(In reply to Amir E. Aharoni from comment #1)
+> Just noticed that the User guide[1] says: ""On the Page options menu there
+> are options [...] to add, edit, or delete categories.""
+> 
+> I'd say that actual ""editing"" must involve the resolution of this bug, and
+> otherwise it is just adding and deleting.
+> 
+> [1] https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide
+
+You can edit each category to add, change or remove the sort key for the page for that category.",1411847706,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-miv67zvinnq5ma6mdz7k,task_subcomment,NA
+VisualEditor: Allow editing of a category link (not just add/remove),"Just noticed that the User guide[1] says: ""On the Page options menu there are options [...] to add, edit, or delete categories.""
+
+I'd say that actual ""editing"" must involve the resolution of this bug, and otherwise it is just adding and deleting.
+
+[1] https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide",1411822235,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-miv67zvinnq5ma6mdz7k,task_subcomment,NA
+"If a reference is defined in a template, and re-used outside of it, and you delete the template, then the reference contents get lost; similarly, copying citations defined inside a template doesn't work","Steps to Reproduce:
+1. Start with a page that contains:
+
+(a) a template with a named ref inside it:  {{quote|Text.<ref name=Foo>Example citation</ref>}}
+
+(b) Some text outside the template that re-uses that citation:  Text.<ref name=Foo />
+
+2. Open the page in VisualEditor and remove the template.
+
+
+
+Actual Results:  
+The named ref becomes undefined.  VisualEditor doesn't ""see"" the citation inside the template, so it can't rescue the re-used template-based citation content when the template is deleted.
+
+Expected Results:  
+That the citation content would be preserved, just like it is preseved when the first instance of a re-used citation in regular page text (outside of templates) is removed.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400094060,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ja5zqpx3lc7f2cjcms4a,task_description,open
+"If a reference is defined in a template, and re-used outside of it, and you delete the template, then the reference contents get lost; similarly, copying citations defined inside a template doesn't work","Also, if the only refs are hidden in templates, then when you add a <references /> block, you get the error mesage that ""There are no references on this page to include in this list.""",1406314582,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ja5zqpx3lc7f2cjcms4a,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"**Author:** `admin`
+
+**Description:**
+Greetings,
+Please enable the Translate and any related extensions to the affcom wiki (chapcom.wikimedia.org) to help us with drafting English based text that will later be utilized on Meta-Wiki. I recognize that actually marking the pages for translation could be problematic - the goal is primarily to utilize tags without making the wikipages difficult to proofread and edit.
+
+Thank you!
+-greg aka varnent
+AffCom Member
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1397876460,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nz63pogjll27mlyr4bfz,task_description,declined
+Translate and related extensions on AffCom wiki,"> we can guess it was just a personal request
+
+If so I'd consider it invalid rather than declined. There's never a good reason to decline enabling Translate if people want to use it.",1467240667,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"I'm going to be bold here and close this task as declined. The requestor is no longer with AffCom, and we don't really know if the people there still wants this or not. No further tickets were filled asking for this feature, so we can guess it was just a personal request from Greg based on a need there back in the days. I've abandoned the gerrit change for this. Please reopen if you disagree. Thank you.",1467150621,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Change 275289 abandoned by MarcoAurelio:
+Enable Translate extension on AffCom (chapcomwiki)
+
+Reason:
+Per task. Requestor is no longer with AffCom and no apparent renewed interest in this feature.
+
+[[https://gerrit.wikimedia.org/r/275289]]",1467150307,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"You can help being present at one of our SWAT windows, for example this night at 23:00 UTC.",1460562206,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"You can help being present at one of our SWAT windows, for example this night at 00:00 UTC",1460562175,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"@Dereckson - I am no longer connected to AffCom having joined WMF as a contractor. However, I still have access to their wiki, and am still in touch with their members and staff liaison (Jaime Anstee). As such, I am happy to help with this ticket in whatever ways would be helpful and logical.",1460468301,PHID-USER-tbsqok4i4d2fpoef36s2,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"@Varnent I discussed again last week the issue with Marco Aurelio, whom isn't really comfortable to process this change.
+
+Would you be available during a SWAT window to help to test this change?",1460422980,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Well in such case, there is not a lot we can do for fishbowls.
+
+So, you can see it deployed during a SWAT window with two strategies.
+
+The first would be to ensure you have someone with access to test that at the moment the change is merged.
+
+The second is a minimal check, then an async broader check:
+
+# check the wiki homepage it's not broken with a fatal exception and all looks good as far as you can tell
+# state during deployment it's not further testable as fishbowl
+# leave the task open, move it in the Done column
+# report here the change is deployed, and ask original task author (here @Varnent) to ensure all is fine
+# You or @varnent can close it as resolved if it's actually fine. If not, you submit a fix or a revert change",1458398634,PHID-USER-4opnqejtv7adgswtxy67,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Please do not assign this to me as I don't have access to the chapcom wiki, thus I won't be able to test if the change works when deployed. Thank you.",1458393536,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"I missed the config rights mentioned above by @Nemo_bis, will try to do in PS2.",1457281006,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,@Varnent @Nikerabbit Will https://gerrit.wikimedia.org/r/275289 achieve what's desired here?,1457280970,PHID-USER-xvs3y6hf6yrfn6sxrk5d,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Change 275289 had a related patch set uploaded (by MarcoAurelio):
+Enabling Translation extension on AffCom (chapcomwiki)
+
+[[https://gerrit.wikimedia.org/r/275289]]
+",1457280835,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,Not stalled AFAICT.,1446737362,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Any progress, or has this stalled?",1443085199,PHID-USER-lumvg23bxmfbvekr2fbo,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Well in that case it's pretty straightforward, just need to explicitly disable all Translate features when enabling.",1433346685,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Responses:
+
+  - We just want to be able to setup <translate> tags while docs are being prepared to help make transitioning to Meta easier.
+  - Most translations would not be happening on the wiki, so we are not concerned about export/import. If translate is used, it will be for things like email messages that are template and housed on AffCom wiki permanently.
+  - Given that there are only a dozen active users, I am not too concerned about accidental markings.
+  - The members who code our pages are familiar with translate extension - I do not anticipate needing additional support.
+  - We do not use VisualEditor much, if at all, although a few members do - we do not anticipate that being a problem given the small percentage of draft pages we are talking about.
+
+If this is too much of a hassle, that's fine, we'll continue to work without. However, it was something we felt would make prep work for draft wikipages going to Meta easier.
+",1433100324,PHID-USER-tbsqok4i4d2fpoef36s2,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"In addition to above:
+* translation memory and other web services should be disabled
+* <translate> tags do not currently work well with visual editor (in case you use it)
+* related database tables must be created when Translate is enabled on a new wiki",1433097590,PHID-USER-732lqsmz4v6bss3kln2v,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"So you want Translate without actually marking pages for translation? If so, what checks are you interested in?
+* If you only want to check balanced translate tags and so on, the solution would be to enable Translate while revoking the pagetranslation right from all groups.
+* If you need Special:PageTranslation for your checks/preparations, how do you plan to avoid accidental marking?
+* If you want to actually mark the pages for translation and have them translated in private before publishing, do you already have a plan for export-import of translations?
+* In any case, do you have users on the wiki who are comfortable using the Translate extension and have enough time to train and assist all the other users, so that you are self-sufficient?",1433082996,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Niklas, can this be done? I know almost nothing about that extension.",1433072245,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+VisualEditor: Provide a way (other than selection) to extend link (and other) annotations to more of the content,"When you add text on the left side of a link (external, internal) in article core the content is not merge with the link. T55210 asks to change this.
+
+When you add text on the left side of a link (external, internal) in the reference assistant the content is merge with the link. Someone asks to change this on https://fr.wikipedia.org/w/index.php?title=Wikipédia:ÉditeurVisuel/Avis&oldid=102556548#Gestion_des_liens
+
+A solution might be : On clicking a link, show 2 sliders (left/right of the current link) to handle easily  what is In what is Out of the link
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1396823280,PHID-USER-hhw22zfd2xzrsyc22lp5,PHID-TASK-kfwclljbfb2twseyrniu,task_description,open
+VisualEditor: Provide a way (other than selection) to extend link (and other) annotations to more of the content,"These feels very confusing as a use paradigm; boxes suddenly flying out for links (just links? not bold/italics?) seems like it will get in the way of seeing what the existing content has. Marking as ""lowest"" priority and re-wording to be more general.",1398726027,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kfwclljbfb2twseyrniu,task_subcomment,NA
+VisualEditor: Warn/stop users from inserting wikitext/bad inputs in the Gallery inspector,"Right now if , a user inserts wikitext inside gallery inspector such as <gallery></gallery> or <ref> inside gallery inserter, it adds an empty gallery inside the page and if you switch to edit source you will see something like:
+<gallery><gallery><ref></ref></gallery></gallery>
+
+
+One possible solution to this issue could be let user know not to add any such wikitext/bad inputs inside gallery inspector
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395169020,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fwu3dpls26ckqdml4hft,task_description,resolved
+VisualEditor: Warn/stop users from inserting wikitext/bad inputs in the Gallery inspector,"Not exactly ""current"". :-)",1519255838,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fwu3dpls26ckqdml4hft,task_subcomment,NA
+VisualEditor: Warn/stop users from inserting wikitext/bad inputs in the Gallery inspector,"This has been resolved by the new gallery dialog, which doesn't allow users to input weird wikitext into the <gallery> tag (T45037).",1519255714,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-fwu3dpls26ckqdml4hft,task_subcomment,NA
+VisualEditor: Warn/stop users from inserting wikitext/bad inputs in the Gallery inspector,"Created attachment 14853
+Screenshot
+
+**Attached**: {F13152}",1395169083,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-fwu3dpls26ckqdml4hft,task_subcomment,NA
+VisualEditor: Be able to set a multimedia item's thumb position (thumbtime=) in the media dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394835120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-shlqtr6tjud3djafldgi,task_description,open
+VisualEditor: Be able to set a multimedia item's start position (start=) and end position (end=) in the media dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394835000,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-5lq7dixzl5nvcmty4r7v,task_description,open
+VisualEditor: Be able to set a multimedia item's start position (start=) and end position (end=) in the media dialog,"I'd like to try to find someone to help make this happen, how difficult would this be to do and what skills would the person need? ",1543864604,PHID-USER-bmbtggsblh3aipffyl4i,PHID-TASK-5lq7dixzl5nvcmty4r7v,task_subcomment,NA
+VisualEditor: Be able to set a multimedia item to not show an icon (noicon) in the media dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834880,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-fzczz22mbckxwxyidfg7,task_description,open
+VisualEditor: Be able to set an item's alignment (baseline/middle/…) in the media edit dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834640,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pfqaskw64eurbsarzh27,task_description,open
+VisualEditor: Be able to set a over-ride thumbnail (thumb=…) in the media edit dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834520,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-p75r2s6odgzvudzsebc2,task_description,open
+Jenkins: Set up perceptual diffs (visual regression testing),"This is something I've been experimenting with in spare time for a while.
+
+The idea is: Render a visual diff for one or more pages and states thereof (comparing the result of the current change to the result of the latest master, or whatever target branch the commit has).
+
+The screenshots would be created using PhantomJS' render() API. Or, while we don't need cross-browser per se, having a browser more representative than PhantomJS would be nice. Perhaps using Chromium under Xvfb with a large enough window (we don't need it to be very tall). And capture output from Xvfb using ImageMagic display `import`.
+
+Rough idea for the Jenkins job:
+
+* Run project setup (e.g. build script for projects like OOjs UI and VisualEditor; installing MediaWiki for core/extensions). Then expose workspace to the local web server (We've got re-usable macros for this already).
+
+* Run the scenarios or urls for the current project and capture the screen after each scenario.
+
+* Compare them against the ones from the last run (e.g. for a commit to master, compare them to the latest master build). TODO: Will need to be stored somewhere. Shared NFS maybe? `store/{project}/{branch}`.
+
+* In test pipeline:
+ * If different, make sure the latest.png/change-after.png/change-diff.png for that url is kept and stored as build artefacts in Jenkins. Otherwise delete the image.
+* In the post-merge pipeline:
+ * Replace the images in the store with those of this build.
+
+Scenarios:
+
+I imagine we'll need to support two kinds of scenarios:
+
+* Plain url.
+* Web driver steps (for large interfaces not accessible by url). This should *not* be used to trigger every possible dialog and component, that slows the test matrix and only tests for no reason. More useful would be to capture individual components via e.g. the OOjs UI demo page. Use these two assert the composition rather.
+
+A few urls we might want:
+* mediawiki-core:
+ - /index.php?title=Main_Page
+ - /index.php?title=Main_Page&useskin=monobook
+ - /index.php?title=Main_Page&action=edit
+ - /index.php?title=Main_Page&action=history
+ - /index.php?title=Special:UserLogin
+ - /index.php?title=Special:UserLogin/signup
+ - /index.php?title=Special:Search&search=wiki
+* VisualEditor:
+ - /demos/ve/#!/src/pages/empty.html
+ - /demos/ve/#!/src/pages/simple.html
+ - /demos/ve/#!/src/pages/complex.html
+* oojs-ui:
+ - /demos/icons.html
+ - /demos/widgets.html
+
+A few implementations that exist:
+* https://github.com/uber/image-diff/
+* https://github.com/bslatkin/dpxdt/
+* Talk (Velocity 2013): https://www.youtube.com/watch?v=1wHr-O6gEfc
+* Talk (Google Developers): https://www.youtube.com/watch?v=UMnZiTL0tUc
+
+Behind these is basically just a ImageMagick compare command between two PNGs.
+* https://github.com/bslatkin/dpxdt/blob/8e76f62e5/dpxdt/client/pdiff_worker.py#L115-L127
+* https://github.com/uber/image-diff/blob/1.0.1/lib/image-diff.js#L53-L65
+* http://www.imagemagick.org/Usage/compare/
+````
+compare
+      -verbose
+      -metric RMSE
+      -highlight-color RED
+      -compose Src
+      mytest-latest.png
+      mytest-build.png
+      mytest-diff.png
+```
+
+See also:
+* {T64511}",1394769900,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kvgadhnokjawoz2a3myt,task_description,stalled
+Jenkins: Set up perceptual diffs (visual regression testing),"Web team has built out a solution here without jenkins that is working well so far. I am curious Timo if this could solve what you had in mi d.
+
+Reports can be found at https://pixel.wmcloud.org
+
+More information at T302246: [GOAL] Leverage Automated Visual Regression Testing",1652228622,PHID-USER-5dwuaigmkz2vzg65lape,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),Until we have a data store to expose the generated files ( {T101545} ). There is not much we can do on this task.,1444134912,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),Lowering priority from high to normal since nobody is apparently actively pushing for this change.  Whenever the feature teams figure out a good utility / way to do such visual differences we can work on integrating it on Jenkins/Zuul.,1408458358,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),"See https://github.com/subbuss/parsoid_visual_diffs for a version that is being used to compare Parsoid and PHP parser HTML output. That works quite well and has already exposed a few css issues and other non-css rendering/html diffs.
+
+Something similar could perhaps be adapted for this purpose as well?",1404789309,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),Mentionned by Subbu on IRC: an example of what visual diffs can bring to us http://diplograph.net/posts/visual_diffs,1403558710,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),"**jgonera** wrote:
+
+See also: https://gerrit.wikimedia.org/r/#/c/126878/",1397862936,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),See also: https://github.com/facebook/huxley,1395961811,PHID-USER-z3l4i7dl52qicxtephy5,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),"I assume that it's easier to roll our own than to re-use wraith or something similar, due to trying to integrate it into jenkins? Multi-platform screenshot regression testing is probably a secondary-level target, but…",1394812559,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),"The job would be non-voting of course, and we'd change the jenkins-bot comment to Gerrit to CHANGED/UNCHANGED instead of SUCCESS/FAILURE.",1394770023,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"Some MediaWiki installations have images hosted on a different domain than the wiki, and in some cases do not have an 'Access-Control-Allow-Origin' header on the image server domain. This causes the XMLHttpRequest for MultimediaViewer to fail, and nothing but a black screen appears. So that the usability isn't completely broken in these (and similar) situations, if the XMLHttpRequest to get the image fails for any reason, MultimediaViewer should fall back to simply displaying the image using an <img> tag.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394426460,PHID-USER-qze3uk4zsetjvgf7liey,PHID-TASK-ma2djbmaav4mlnfs25tp,task_description,open
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,One of the problems is that the request is sending `withCredentials` marked true in the actual XHR. Is there a way to disable it?,1619556311,PHID-USER-bb2gcrpsvrrae4vbf4da,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,This issue still hasn't been resolved. The fallback to img tag is a very reasonable request.,1619554987,PHID-USER-bb2gcrpsvrrae4vbf4da,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"Mass-removing the Multimedia tag from MediaViewer tasks, as this is now being worked on by the Reading department, not Editing's Multimedia team.",1442850249,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"**bryanhunt** wrote:
+
+I can't comment on the rational other than to say that the behavior is common enough to indicate it would be condition worth considering. Due to the fact that the CORS header is requesting a browser to relax its security level it does sort of make sense that peripheral security would flag that as dangerous in that regard.
+
+The being said switching over to https does resolve the problem so offering that as an option to the user when the error screen shows up could be the easiest way to handle condition.",1405114675,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"We do fail more gracefully now (there is an error message, not just a black screen of deatch which is what the OP was complaining about). Could look nicer (we have some design notes in https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/299 ) but that's very low priority.
+
+I'll think about adding a fallover, but we have too many of them already (the image loading can fail in other ways) and the logic is getting way too complex for its own good. Also, while the image could be loaded without CORS, some of the metadata API requests could not (we could probably recover from those requests failing, though).
+
+All that said, stripping CORS headers is horribly broken behavior and makes zero sense from a security point of view. You should probably complain to the manufacturer / whitelist Wikipedia domains.",1405112327,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"**bryanhunt** wrote:
+
+Yes, while that is true (watchguard), it is far from an extraordinary configuration ( http://www.garysieling.com/blog/dont-use-access-control-allow-origin ) and the OP's comment was that the application should fail a bit more gracefully the headers don't exist. Web tech is far from my area of expertise but as a developer I would have to concur with the OP that it does make sense for Media Viewer to fail over to another mechanism to ensure a functional application in these situations.
+
+An interesting note is that while Firefox & Chrome both exhibit the same failure mode, IE (11.0.9) does not appear to - making me assume that it either lacks similar security checks or is already using a different mechanism.",1405096530,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"Wikipedia images are served with correct CORS headers:
+
+
+$ curl -vo/dev/null 'http://upload.wikimedia.org/wikipedia/commons/thumb/8/8a/Media_Viewer_-_View_Original_File_-_Mockup_1024px.jpg/1024px-Media_Viewer_-_View_Original_File_-_Mockup_1024px.jpg' 2>&1 | grep Access-Control
+
+< Access-Control-Allow-Origin: *
+< Access-Control-Expose-Headers: Age, Content-Length, Date, X-Cache, X-Varnish
+
+$ curl -vo/dev/null 'https://upload.wikimedia.org/wikipedia/commons/thumb/8/8a/Media_Viewer_-_View_Original_File_-_Mockup_1024px.jpg/1024px-Media_Viewer_-_View_Original_File_-_Mockup_1024px.jpg' 2>&1 | grep Access-Control
+
+< Access-Control-Allow-Origin: *
+< Access-Control-Expose-Headers: Age, Content-Length, Date, X-Cache, X-Varnish
+
+
+Maybe you are you behind some sort of proxy which messes with the headers?",1405040062,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"**bryanhunt** wrote:
+
+Media Viewer handling of lack of CORS headers in Chrome
+
+This seems to be the root cause of the chrome rendering problem of wikipedia images since media viewer is now enabled by default. I am quite surprised I couldn't find any other reference for media viewer simply not working for Chrome.
+
+I have confirmed this behavior in Chrome Version 35.0.1916.153 m on windows XP, 7, & 8
+
+**Attached**: {F12997}",1405033109,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"There could be a flag (off by default) to enable AJAX image loading; when off, we could show a static (positionless) loading bar.",1403822668,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"(In reply to Tisza Gergő from comment #5)
+> George: the MultimediaViewer version you use is outdated, the current
+> version loads images differently. Do you want to give a shot at updating to
+> the current version? (The tip of the 1.23wmf17 branch should be a safe
+> choice.)
+> 
+> I expect it will still fail, but for an entirely different reason, and that
+> will be easy to fix.
+
+Alright, I updated the extension. It works and does have the fallback, but the fallback also blurs the image a lot. I know why it's doing that, but maybe should it not upscale the img tag bigger than the image's thumbnail was?",1394489121,PHID-USER-qze3uk4zsetjvgf7liey,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"For now I am setting this back to unconfirmed, most of the image loading code has been replaced since then.",1394486794,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"George: the MultimediaViewer version you use is outdated, the current version loads images differently. Do you want to give a shot at updating to the current version? (The tip of the 1.23wmf17 branch should be a safe choice.)
+
+I expect it will still fail, but for an entirely different reason, and that will be easy to fix.",1394486512,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"Contents of the console:
+
+XMLHttpRequest cannot load http://images.brickimedia.org/7/7d/Goodship1.jpg. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://dev.brickimedia.org' is therefore not allowed access. 
+
+Uncaught TypeError: Cannot read property 'length' of null mmv.provider.Image.js:93
+Image.binaryToDataURI mmv.provider.Image.js:93
+(anonymous function) mmv.provider.Image.js:73
+(...)
+request.onreadystatechange mmv.performance.js:71",1394482240,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,Tracked in Mingle as https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/295,1394477799,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"(In reply to Tisza Gergő from comment #1)
+> We do have an <img> fallback, but it sets img.crossOrigin = true on certain
+> browsers where the fallback would otherwise result in downloading the image
+> twice. Just to be sure that is really the cause of the problem, is there a
+> public wiki where this bug can be reproduced?
+
+Yes, here is an example: http://dev.brickimedia.org/wiki/VisualEditor You'll have to make an account so you can enable it in Beta Features (I think) but that only takes a minute or so.",1394471169,PHID-USER-qze3uk4zsetjvgf7liey,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"We do have an <img> fallback, but it sets img.crossOrigin = true on certain browsers where the fallback would otherwise result in downloading the image twice. Just to be sure that is really the cause of the problem, is there a public wiki where this bug can be reproduced?",1394471074,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"We apply red link styles to nonexistent titles in the link suggestions, so for redirects and disambig pages the corresponding styles/classes should be applied as well.
+
+I don't actually know what these are, ask James :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1391818500,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-zddhewpobyqo3lkurdqv,task_description,resolved
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"Change 345883 merged by jenkins-bot:
+[mediawiki/core@master] mw.widgets.TitleOptionWidget: Apply styles for redirects/disambiguation links
+
+[[https://gerrit.wikimedia.org/r/345883]]
+",1491061072,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,">>! In T63072#3147540, @matmarex wrote:
+> I don't think so – that one did it for links in the editing surface, but not in the link inspector suggestions dropdown. Looks like this code lives in mw.widgets.TitleOptionWidget now.
+> 
+> …and we actually handle redirects and disambigs there with custom icons. So this should be trivial.
+
+Oh, hah, I thought we'd done it when the code was in VE but clearly I was wrong. :-)",1491060513,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"Change 345883 had a related patch set uploaded (by Bartosz Dziewoński):
+[mediawiki/core@master] mw.widgets.TitleOptionWidget: Apply styles for redirects/disambiguation links
+
+[[https://gerrit.wikimedia.org/r/345883]]
+",1490992438,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"I don't think so – that one did it for links in the editing surface, but not in the link inspector suggestions dropdown. Looks like this code lives in mw.widgets.TitleOptionWidget now.
+
+…and we actually handle redirects and disambigs there with custom icons. So this should be trivial.",1490992221,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,This was done by @matmarex way back in August 2014 (two weeks after my comment above) – 066283dde745fcc372ffab8d753962858813d032.,1490898090,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"(In reply to Bartosz Dziewoński from comment #2)
+> We actually don't apply any classes, ve.ui.MWLinkTargetInputWidget.css just
+> has some styles defining a close-enough reddish color. (This is kind of bad
+> since the color can differ per-skin.)
+> 
+> .ve-ui-mwLinkTargetInputWidget-menu .oo-ui-menuItemWidget[rel=newPage] {
+> 	color: #BA0000;
+> }
+> 
+> There are no styles by default for redirect and disambiguation links, some
+> users choose to style them in various ways (usually green for redirects and
+> maroon for disambigs). 
+
+Presumably the styles will be ported over to Parsoid content, at which point we can just apply them directly?
+
+
+> I'm not sure if we should do this for the link in the inspector; they are
+> already visually distinct by being placed in separate sections. We might
+> want to remove the reddish styles too...
+
+I'm not sure. Consistency of hinting is important.",1406821549,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"We actually don't apply any classes, ve.ui.MWLinkTargetInputWidget.css just has some styles defining a close-enough reddish color. (This is kind of bad since the color can differ per-skin.)
+
+.ve-ui-mwLinkTargetInputWidget-menu .oo-ui-menuItemWidget[rel=newPage] {
+	color: #BA0000;
+}
+
+There are no styles by default for redirect and disambiguation links, some users choose to style them in various ways (usually green for redirects and maroon for disambigs). 
+
+I'm not sure if we should do this for the link in the inspector; they are already visually distinct by being placed in separate sections. We might want to remove the reddish styles too...",1406813705,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,*** Bug 64584 has been marked as a duplicate of this bug. ***,1401417534,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+"VisualEditor:  Add a Preview feature to show actual version of page (minus slugs, etc.)","VisualEditor has some deliberate/non-buggy differences in its display, compared to what readers will see on a saved page, such as the addition of blank lines/slugs to make adding new items at the top of a page.  These differences sometimes confuse users.
+
+Add a preview button so that users can see the final version, rather than the slightly different VisualEditor version.
+
+**See Also**:
+*{T49790}
+*{T44139}
+*{T39931}",1390928460,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qi6wc6gcqjrnpifmlnvz,task_description,open
+"VisualEditor:  Add a Preview feature to show actual version of page (minus slugs, etc.)",Suggestion from SarahTehCat:  Use the 'Live Preview' system (if it's stable).,1425493251,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-qi6wc6gcqjrnpifmlnvz,task_subcomment,NA
+VisualEditor does not format hatnotes correctly,"comparison of screenshots
+
+Currently, VisualEditor inserts blockSlugs around rellinks and dablinks (collectively known as hatnotes). This adds a lot of extra whitespace around them compared to how they are formatted normally. See attachment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13459}",1390875300,PHID-USER-a5pveeqqwaddgfjiv2fq,PHID-TASK-3eutuphwveuy6tgpm2lo,task_description,open
+VisualEditor does not format hatnotes correctly,"Still exists (see testcase at https://en.wikipedia.org/wiki/User:Neil_P._Quinn-WMF/T62516). We now explain this inconsistency somewhat better by showing a ""insert paragraph"" message when you hover over one of the slugs (see screenshot), but this still falls short of our ideal of having the VisualEditor surface appear identical to the read surface.
+
+{F160551}",1430783645,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-3eutuphwveuy6tgpm2lo,task_subcomment,NA
+VisualEditor: Provide option in media insertion dialog to only show local media,"**Author:** `gabriel.birke`
+
+**Description:**
+There is no way to make the VisualEditor Media selection to look only for local media (send iilocalonly when querying imageinfo). While this is ok for Wikipedia, it's not suitable for other wikis.
+
+There should be a checkbox in the search dialog to switch to local only search.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389260880,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-eudgmmbmz7t3therwbwh,task_description,open
+"VisualEditor:  Unable to select empty section heading (e.g., to remove it) at the end of a page","Intention:
+Remove a blank section heading (==<nowiki/>==) at the end of a page.
+
+Steps to Reproduce:
+1. Place cursor on blank section heading at the end of the page.
+2. Try to select it.
+
+
+Actual Results:  
+Nothing.  Also, it's not possible to select the whole line (e.g., to cut and paste it, leaving nothing behind) even after you type something on the section heading.  If you type ""abc"", then you can select and cut ""abc"" (Note:  what it cuts is *not* ""==abc==""), but the ==<nowiki/>== will remain.
+
+
+Reproducible: Always
+
+You can test this at https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox2&oldid=589158823
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388854560,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-j2mehk62spszuq5kxa3y,task_description,resolved
+"VisualEditor:  Unable to select empty section heading (e.g., to remove it) at the end of a page","This seems to no longer to be a problem. I can remove the heading in the example page in two ways:
+* By putting the cursor inside it and pressing Backspace
+* By changing the format from ""Heading"" to ""Paragraph""",1542996092,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-j2mehk62spszuq5kxa3y,task_subcomment,NA
+"VisualEditor:  Unable to select empty section heading (e.g., to remove it) at the end of a page",The bug confirmed  - <nowiki/> cannot be deleted from VE.,1421789796,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-j2mehk62spszuq5kxa3y,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add any image
+3.Open the dialog box to add image again
+4.Type a different string in the textbox to search for matching images.
+
+Observed Result:
+An error appears TypeError: jQuery1830683983782510787_1388777743220 is not a function
+
+See the screenshot attached 
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/New_pageimage?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12791}",1388778000,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_description,declined
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",*** Bug 58364 has been marked as a duplicate of this bug. ***,1406740632,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",*** Bug 68059 has been marked as a duplicate of this bug. ***,1405543712,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Also:
+* Upstream jQuery: http://bugs.jquery.com/ticket/8744 (status: cantfix)
+* Closely related upstream Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=707154 (status: NEW)",1403055668,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","As such, please don't waste any more time on this. This is harmless errors that we can't do anything about and are side-effects of behaviour that is very much intended and wanted by us. Just another one the category of browsers being ugly and/or minor issues upstream.",1403055051,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","That patch, as far as I can see, did nothing. And if it did, it would actually have caused a regression.
+
+The TypeError thrown is caused by the JSONP <script> tag request finishing and trying to invoke a temporary global function that jQuery exposed, but has revoked since because the consumer of $.ajax, VisualEditor in this case, has aborted the request.
+
+All jqXHR objects have an abort method. Duck-typing it is useless because it is always there.
+
+And while JSON-P doesn't have a native abort mechanism, jQuery does a good job of emulating it (it will do a best effort approach to cancel the http request for efficiency reasons, and in case it still makes it, it will make sure it reaches a dead end and not cause our application code to process its data[1]).
+
+As I mentioned before, the dead end results in a Uncaught TypeError which sounds bad, but isn't, because it's in an asynchronous and independent call stack that has no influence on either our or jQuery's cod execution.
+
+[1] Even if there was a way to not half-abort these requests, we wouldn't want that. We actually want these requests to reach a dead end. Otherwise we'd get race conditions where you type ""a"", ""ab"", ""abc"" and after ""ab"" is intended to be aborted, it might still arrive *after* ""abc"" and mess up our search results.",1403054973,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Change 140044 merged by jenkins-bot:
+Media search dialog: Only try to abort request if possible
+
+https://gerrit.wikimedia.org/r/140044",1403026198,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Change 140044 had a related patch set uploaded by Alex Monk:
+Media search dialog: Only try to abort request if possible.
+
+https://gerrit.wikimedia.org/r/140044",1402960839,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","I already had InstantCommons enabled, but couldn't reproduce it before. Looks like I can now.",1402960294,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","This can be reproduced when using the input field for the Media insertion dialog.
+
+E.g. on https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet?veaction=edit
+
+It might not throw the error on your local wiki if your wiki is not configured to use a separate wiki, e.g. Wikimedia Commons, as extra file repository. Enable wgUseInstantCommons if you haven't already.
+
+https://www.mediawiki.org/wiki/Manual:$wgUseInstantCommons",1402830324,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",Looks like we fixed this – possibly by resetting the search on open?,1402694967,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",Although I can't actually reproduce this error.,1402690209,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","(In reply to Krinkle from comment #5)
+> This doesn't affect our callstack in any way, and from our perspective it
+> works as expected (after the request is aborted, our callback must not fire).
+> 
+> This last part is a jQuery internal implementation detail that might change
+> in the future, but either way, it is out of our hands, doesn't affect
+> anything, and nothing we can do anything about.
+
+I'm tempted to wontfix this, but apparently people are complaining that VE is broken because of it. I guess we'll just have to suppress the error.",1402689014,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Lowering priority as this is merely a console notice. It doesn't affect anything in any way, it is in fact ""expected"" behaviour by jQuery due to there not being another way to do what it does.
+
+What it does is cancel a cross-domain ajax request. Short of CORS/XHR, there isn't actually such thing as a cross-domain ajax request. What it really does (and we rely on this) is JSON-P, which is a <script> tag to the api.php entry point with a temporary function as callback (this is a sort-of standard method called ""JSON-P"" which MediaWiki actively supports, it's not a VE intention or a hack beyond what it is).
+
+As with many ajax-based content population requests (e.g. search suggestions, auto completion etc.) we abort pending requests when we fire off the next. When interacting with the local API, we use regular XHR which has an abort method.
+
+When interacting with a foreign API, jQuery gives us an XHR-like interface but really underneath it is JSON-P, which means there isn't a way to actually abort the request. Instead, jQuery deletes the callback and does a best-effort approach to cancel the request. When the request does come back, it will try to invoke a callback that has already been revoked, which results in a TypeError in the asynchronous callstack of the ajax request.
+
+This doesn't affect our callstack in any way, and from our perspective it works as expected (after the request is aborted, our callback must not fire).
+
+This last part is a jQuery internal implementation detail that might change in the future, but either way, it is out of our hands, doesn't affect anything, and nothing we can do anything about.",1389376025,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",This issue is happening on mw.org too,1389375010,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","This issue is still occurring while inserting image inside Media Settings and Reference Dialog.
+
+Steps to reproduce:
+
+1.Click on a image inside VE
+2.Go to Media Settings 
+3.Type something as caption and add another image inside it
+
+Second way to reproduce:
+
+1.Click on a reference inside VE
+2.Type something and add a image in this dialog box
+
+Screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Jan8th?veaction=edit",1389210897,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Created attachment 14258
+Reproduced on 8th January
+
+**Attached**: {F12793}",1389210883,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Not happening anymore.Possible fix for the bug might be: https://gerrit.wikimedia.org/r/#/c/102377/
+as discussed with Moriel.",1389055776,PHID-USER-24djtv3gj5gua2y6u2g5,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: If more than one section was changed, no section title should be shown in the edit summary","To reproduce:
+
+0. Go to a page with two sections.
+1. Click the ""Edit"" link on the second section.
+2. Make some changes in the first section.
+3. Press the save button.
+
+Observed: The second section's name is shown in the summary.
+Expected:
+1. If only one section was changed, then that section's title should be shown in the summary.
+2. If more than section was changed, no section title should be shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**: T53903",1387043280,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-gdczdi6me4o4ykhiyif2,task_description,open
+"VisualEditor: If more than one section was changed, no section title should be shown in the edit summary","The current behavior 
+- clicking on Edit in a section makes all page(sections) available for editing in VE. 
+- if there are two sections  - 'Review your changes' in save box will display both section titles - no matter which section was opened or edited
+- with three or four - only the section title to which changes were applied will be displayed
+",1419969643,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-gdczdi6me4o4ykhiyif2,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","**Author:** `Wikifram`
+
+**Description:**
+When I edit a page, and add a reference to the text and a different reference to an image caption, all in one edit, then the reference text for the image caption is not saved but gets changed to the reference text from the text (this already happens in the preview). You now get two references with the same text, even though you gave them a different text. 
+
+Example: [https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=840234&oldid=840227] (the image caption ref had a different text on typing)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386760560,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-nnnclbqpn5cgksi3kujo,task_description,invalid
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","Can **not** reproduce the issue (anymore). See the following test:
+
+- Edit/Create a page in VE
+- In one edit:
+  - Add a plain reference using the VE reference dialog with e.g. content `A`
+  - Add an image using the VE image dialog and in that process adding a plain reference to the caption with e.g. content `B`
+  - Save
+
+I then get two references with the two texts as exprected. Feel free to re-open the issue if there's something new to it.
+",1726499520,PHID-USER-k5wpqok2x66oei3wguaf,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","Can **not** reproduce the issue (anymore). See the following test:
+
+- Edit/Create a page in VE
+- In one edit:
+  - Add a plain reference using the VE reference dialog with e.g. content `A`
+  - Add an image using the VE image dialog and in that process adding a plain reference to the caption with e.g. content `B`
+  - Save
+
+I then get two references with the two texts as exprected. Feel free to re-open the issue is there's something new to it.
+",1726499498,PHID-USER-k5wpqok2x66oei3wguaf,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","{T87106} isn't quite a duplicate of the outcome, but it's the same issue.",1423675748,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","The key bug here is bug 47344, about using sub-documents instead of the current hack. This would affect media captions and references, and possibly other things.",1415054373,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text",See also bug 60919?,1414883373,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text",I can reproduce this issue.,1414812757,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","Change 102386 had a related patch set uploaded by Aquifacae:
+Changed wiktionary/en.ico favicon to proper image and resolutions
+
+https://gerrit.wikimedia.org/r/102386",1387344005,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","**Author:** `Wikifram`
+
+**Description:**
+This version of my sandbox at enwiki, [https://en.wikipedia.org/w/index.php?title=User:Fram/sandbox&oldid=585258547], is no longer editable in VE by me (FF25, W7). It opens, and I can make whatever changes I want, but the ""save"" button stays disabled, and when I open the reference interface, I can no longer close that one either. The category and media interface work allright though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57573",1386683160,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oycdhxzb7vj25wmx37yl,task_description,invalid
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","Sorry for randomly stumbling over that ticket. I can not reproduce the issue anymore. What I did:
+
+I open the sandbox with the revision linked and edit that revision in VE:
+- I can make changes in the editor and the `Save` button becomes enabled.
+- I can open, use & close the references interface without issues.
+
+Feel free to re-open the task if anything remains or I missed a point here.
+",1726500810,PHID-USER-k5wpqok2x66oei3wguaf,PHID-TASK-oycdhxzb7vj25wmx37yl,task_subcomment,NA
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","Yuck.
+
+So the problem is that you've got a reference in an image's caption, which is inside a reference; this is not allowed in wikitext (as you can see from the ""Cite error: A <ref> tag is missing the closing </ref> (see the help page)."" error), and is because the restriction on media items' captions doesn't inherit the restriction of the reference block.
+
+We'll need to build a way for restrictions to be explicit and inheritable.",1386697008,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-oycdhxzb7vj25wmx37yl,task_subcomment,NA
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","**Wikifram** wrote:
+
+[16:24:59.875] TypeError: itemNode is undefined @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20131210T024153Z:298",1386689836,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-oycdhxzb7vj25wmx37yl,task_subcomment,NA
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","Could you please open the Error Console (or whatever it is called in your browser) and reload the page that you see the problem on? If there is a problem or an error with JavaScript it should be printed in that console.
+For more information please see:
+* Firefox ≥24: https://developer.mozilla.org/en-US/docs/Tools/Web_Console
+* Internet Explorer: http://msdn.microsoft.com/en-us/library/ie/dn255006
+* Google Chrome: https://developers.google.com/chrome-developer-tools/
+* Apple Safari: https://developer.apple.com/library/safari/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/PrototypingYourWebsite/PrototypingYourWebsite.html
+* Opera: http://help.opera.com/Linux/12.10/en/errorconsole.html",1386687050,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-oycdhxzb7vj25wmx37yl,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu","Steps to reproduce:
+
+1. Go to https://en.wikipedia.org/wiki/Wax_foundation
+2. Click on ""Edit"".
+
+The first image is automatically selected, and its four corners are replaced with image resizing icons, but ""Media"" image editing icon is not shown. I expected that the image would not be selected, or if selected that image editing icon is shown.
+
+3. Click on the second image.
+4. Click again on the first image. Now the image editing icon should be shown.
+5. Click on the image editing icon.
+6. Click on the word ""frame"". Link editing icon should be shown.
+7. Click on the link editing icon.
+8. Enter ""Beehive frame"" (without quotes) in the text box.
+9. Click on ""Apply changes"".
+10. Click on ""Save page"". ""Save your changes"" dialogue appears.
+11. Click on ""Save page"" in the new dialogue.
+
+The VisualEditor displays ""Your changes to Wax foundation have been saved."", but nothing has actually been saved.
+
+Now, I see three bugs here:
+
+1) The first image should not be selected automatically.
+2) Possibly I have to do something after entering the link target in order for the target to be ""applied"" to the image caption? But I don't see what it is that I should do.
+3) The editor shouldn't display ""changes have been saved"" message when there are no changes to be saved; doing so prevents the people from knowing that what they did was not saved, regardless of whether there was an error on their part or on the VisualEditor part.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58248
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62542",1385195700,PHID-USER-asiusr6cw73okn35tobw,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_description,open
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu",(Confirmed still an issue.),1429559780,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu",*** Bug 62650 has been marked as a duplicate of this bug. ***,1394818952,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu","We now try to select the nearest content branch, so this bug is only reproduceable if the document consists of just an image.",1392388656,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu","1.1) I believe the image should not be selected, but I understand people might have different opinion about it.
+
+1.2) But if the image is selected, then the icon must be shown as well. I see this as an obvious bug.
+
+2)
+
+OK, it appears that in order for the link to be applied, I have to click on < icon in the top left corner of the link editing box; or, I have to press Enter twice; or, click in the text editing box and then in the space below it(?).
+
+To me, and I believe other editors, this is very unintuitive. Perhaps < icon could be changed to ✓ - I see < as signifying 'Undo' rather than 'Apply'. Perhaps ""Apply changes"" should be ghosted when there are no chages to apply. But even with these changes I don't see how I could intuitively know what I should do.
+
+The ""Review your changes"" button shows correctly whether I have any changes.",1385452878,PHID-USER-asiusr6cw73okn35tobw,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu","I'll leave the first question to others, for the other ones:
+2) You need to make sure that you select the word you want (then you click on it, press Enter, whatever). Try and review your changes before you save: is it there now? If it is, you should be able to save and your edit should stay in the page history. If it isn't, please let us know the browser (and its version) and Wikipedia skin you use.
+3) I experienced something similar back in July: https://bugzilla.wikimedia.org/show_bug.cgi?id=51243 .",1385398701,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","Intention:
+Re-use a reference.
+
+
+Actual Results:  
+The ref naming scheme needs improvements so that humans can remember which ref name they want to re-use, especially if they are using the wikitext editor, where they will not have any of the possible hints that VisualEditor may provide.
+
+Expected Results:  
+A system that is ""xxx:0"", where ""xxx"" is text simply copied out from the beginning of the named ref would be an improvement.  We can assume that anything inside the ref is in a language that the editor is capable of coping with.  We can exclude the names of templates and their parameters, as well as ""http"" (otherwise, bare URLs in refs will produce a lot of equally unfriendly <ref name=htt:n> names).
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385163660,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_description,duplicate
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","
+
+*** This bug has been marked as a duplicate of bug 50568 ***",1414104088,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","Speaking as an extensive editor, I just find the exist reference I want to re-use and manually copy the name; this is no extra work in VE. Clearly some people try to remember the name between uses, but given that random people write random names for references already…",1385399054,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","I realize that any automagic system will have serious limitations, compared to prompting users for a human-created name (which VisualEditor ought to be doing).  But a semi-random string of letters is actually easier for most people to remember than a purely incremental number.  <ref name=""sgd1""> and <ref name=""iuo2""> are easier to keep straight than <ref name="":1""> and <ref name="":2"">—and <ref name=""usc1""> and <ref name=""lee2"">, when the ref's contents actually meantion USC and Lee, are even easier.
+
+I don't understand how including some letters (taken from the ref's contents) in the ref name would fail to work anywhere, or at least would fail to work at any language that uses left-to-right typing (unless Arabic numbers are also typed right to left; I can imagine that combining RTL for letters with LTR for numbers would be irritating) and a non-IME/non-variant character set (which might also work just fine, but I don't know enough to have an opinion).",1385397795,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","Why humans need to be able to remember the ref names:
+
+Because actual humans actually have to be able to remember the ref name if they're going to re-use it.  They cannot re-use the ref any other way.
+
+This is true for everyone now, because VisualEditor is only showing (at most) the ref names when you try to re-use a ref, which means that anyone trying to re-use a ref currently needs to know whether the ref they want to re-use ref name :0, :1, :2, :3, :4, :5, etc.—sometimes through a dozen or more meaningless numbers.
+
+This is true permanently for anyone not using VisualEditor, because there is no other way to re-use a ref in the wikitext editor except to manually type (or copy) the name of the ref.",1385397298,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","(In reply to comment #0)
+> The ref naming scheme needs improvements so that humans can remember which
+> ref name they want to re-use
+
+Why?
+
+This is an insane amount of work to do, won't work on wikis that do things in a different way (e.g. this might work for enwiki and frwiki but not dewiki or others), and will likely not actually result in what you want.
+
+I'm hovering on WONTFIX, but will leave this as ""Lowest"" instead for now.",1385394470,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"In the linked diff I added an external link within single brackets.
+It didn't trigger the markup warning - I wouldn't know how to add such links in VE.
+The markup guide for en.wp says these links are ""Only used within article body for footnotes"", but of course they might be used also outside ns0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2Fsandbox&diff=582808389&oldid=582806629
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57419",1385123700,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hryitnavu3rbrhqscuk7,task_description,declined
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"On reflection, I'm WONTFIXing this as it'd be too disruptive for a temporary notice.",1398713139,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hryitnavu3rbrhqscuk7,task_subcomment,NA
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"I worry that this would interfere with languages which use []s rather than ()s in text – remember that the wikitext warning is for rare, occasional chiding comments for users who've temporarily forgotten that they're using a rich editor rather than wikitext.
+
+If you want to write ""using sites like Amazon [http://amazon.com and its local country variants] or eBay [http://ebay.com etc.]"" you're going to be rather annoyed by this…",1385488985,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hryitnavu3rbrhqscuk7,task_subcomment,NA
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"(As far as I tested, it can't edit them, that's why I filed bug 57419.)",1385488658,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-hryitnavu3rbrhqscuk7,task_subcomment,NA
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"Steps:
+1. Edit page
+2. Add [http://example.org]
+
+
+Yep, we should change our wikitext detection to account for external links. Widening scope of this bug for external links in general, not just unnamed ones.
+
+Steps:
+1. Edit page
+2. Add [http://example.org Foo] (unnamed external link)
+3. Add [http://example.org] (named external link)
+
+(In reply to comment #0)
+> [..] I wouldn't know how to add such links in VE.
+
+VisualEditor currently doesn't allow (external) links to be created without names. It can edit them (afaik), but not create new ones. This is a separate issue from the wikitext warning not being triggered though.",1385488417,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-hryitnavu3rbrhqscuk7,task_subcomment,NA
+Lots of CSS related noise in FF Web Console on enwiki,"Not urgent, but should probably be investigated and cleaned up were appropriate..
+
+[04:51:59.127] Unknown property '-moz-box-shadow'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.127] Expected 'none' or URL but found 'alpha('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.127] Unknown property 'zoom'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.127] Expected declaration but found '*'.  Skipped to next declaration. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.127] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.128] Error in parsing value for 'background'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.128] Error in parsing value for 'display'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.129] Error in parsing value for 'list-style-type'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.129] Unknown property 'user-select'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.130] Unknown property 'box-sizing'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.130] Error in parsing value for 'background-image'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.131] Unknown pseudo-class or pseudo-element '-webkit-input-placeholder'.  Ruleset ignored due to bad selector. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.131] Unknown pseudo-class or pseudo-element '-ms-input-placeholder'.  Ruleset ignored due to bad selector. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.168] Unknown property 'break-inside'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.169] Unknown property 'speak'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.169] Expected 'none' or URL but found 'chroma('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.170] Unknown property 'zoom'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.170] Expected media feature name but found '-webkit-min-device-pixel-ratio'. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.716] Unknown property 'box-sizing'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page
+[04:51:59.812] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:4
+[04:51:59.812] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:4
+[04:51:59.812] Error in parsing value for 'unicode-bidi'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:6
+[04:51:59.812] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Unknown property '-moz-box-shadow'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Unknown property '-moz-background-clip'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Expected 'none' or URL but found 'progid'.  Error in parsing value for 'filter'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Error in parsing value for 'background'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.812] Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.813] Unknown pseudo-class or pseudo-element '-o-prefocus'.  Ruleset ignored due to bad selector. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.813] Error in parsing value for 'background'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.813] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.813] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:16
+[04:52:00.137] Unknown property '-moz-box-shadow'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:2
+[04:52:00.138] Expected 'none' or URL but found 'alpha('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:2
+[04:52:00.138] Expected 'none' or URL but found 'alpha('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:52:00.138] Unknown property '-moz-background-clip'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Unknown property '-moz-background-origin'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Expected color but found 'bottom'.  Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Unknown property '-moz-border-radius-topleft'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Unknown property '-moz-border-radius-topright'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: minor",1385009520,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-wjmyqwnbfehyswxiilbk,task_description,declined
+Lots of CSS related noise in FF Web Console on enwiki,"Unless you have a good reason to kill any of these, this is expected and okay.
+
+The noise refers either to:
+* horrible hacks we need to support older browsers (""Expected
+  'important' but found 'ie'.  Expected ';' or '}' to terminate
+  declaration but found 'ie'."", ""Expected declaration but found '*'.
+  Skipped to next declaration."" – both of these are for IE 6 and 7)
+* browser-specific rules that other browsers do not understand (-ms-*,
+  -webkit-*, …)
+* or things your browser just does not support (""Unknown property
+  'user-select'."").",1385065447,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wjmyqwnbfehyswxiilbk,task_subcomment,NA
+Lots of CSS related noise in FF Web Console on enwiki,"Really depends on our browser version support.  
+For example, ""border-radius"" property is supported since Firefox 4; deprecated ""-moz-border-radius"" is required for Firefox 3.x and older, and unsupported since Firefox 13.",1385065111,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-wjmyqwnbfehyswxiilbk,task_subcomment,NA
+Lots of CSS related noise in FF Web Console on enwiki,"So... those are just the CSS parser saying it doesn't recognize various things that are there for other browsers or older browsers.
+
+Not sure how actionable this is?",1385051464,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-wjmyqwnbfehyswxiilbk,task_subcomment,NA
+Provide dialog to enter and edit templates,"It would be very nice if WikiEditor had a dialog to work with templates the way VisualEditor has. There is also a user script: [[User:קיפודנחש/TemplateParamWizard]], but IIRC this script doesn't use the informations provided by TemplateData, but uses its own format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384851900,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-d4viyvnin3zjuou7itc4,task_description,resolved
+Provide dialog to enter and edit templates,"With the beta of #mediawiki-extensions-templatewizard having been deployed {T202545}, I'm calling this resolved. Any related issues should be filed against that component.",1542127013,PHID-USER-wrimmmr5w2zt7nk2t753,PHID-TASK-d4viyvnin3zjuou7itc4,task_subcomment,NA
+Provide dialog to enter and edit templates,">>! In T59232#610546, @Aklapper wrote:
+> Michael: How is/was this request different from the (unmaintained) template editor which was just removed from WikiEditor recently? https://gerrit.wikimedia.org/r/#/c/123647/
+
+The difference is, that it actually should work ;-) This wasn't removed because nobody wants such a feature, but because that module didn't do anything sensible.",1425984217,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-d4viyvnin3zjuou7itc4,task_subcomment,NA
+Provide dialog to enter and edit templates,Michael: How is/was this request different from the (unmaintained) template editor which was just removed from WikiEditor recently? https://gerrit.wikimedia.org/r/#/c/123647/,1396879957,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-d4viyvnin3zjuou7itc4,task_subcomment,NA
+VisualEditor: do not remove line break before first category when a user deletes {{DEFAULTSORT}},"There should be a line break (ENTER) between ""{{Álgebra}}"" and ""[[Categoria:Estruturas algébricas]]"" on these edits:
+https://pt.wikipedia.org/wiki/Anel_%28matem%C3%A1tica%29?diff=37240720
+https://pt.wikipedia.org/wiki/Corpo_%28matem%C3%A1tica%29?diff=37240730
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383471540,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-6bdm7pcljc4dgt4wt7gc,task_description,open
+VisualEditor: do not remove line break before first category when a user deletes {{DEFAULTSORT}},"I just [[https://pt.wikipedia.org/w/index.php?title=Usu%C3%A1rio%28a%29%3ANeil_P._Quinn-WMF%2FTestcase%2FT58530&diff=41959157&oldid=41959144|tested it]], and this issue still exists.",1429548535,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-6bdm7pcljc4dgt4wt7gc,task_subcomment,NA
+VisualEditor: do not remove line break before first category when a user deletes {{DEFAULTSORT}},This issue [[https://pt.wikipedia.org/w/index.php?title=Usu%C3%A1rio%28a%29%3ANeil_P._Quinn-WMF%2FTestcase%2FT58530&diff=41959157&oldid=41959144|still exists]].,1429548497,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-6bdm7pcljc4dgt4wt7gc,task_subcomment,NA
+VisualEditor inspector for SyntaxHighlight is too tiny with no resize option,"screenshot
+
+While we can't yet just click into a <source> SyntaxHighlight extension chunk and edit it, I notice we can now click a ""<>"" button that opens a plaintext editor for the contents. Awesome!
+
+Unfortunately the popup box for this seems really small, and there doesn't appear to be any way to resize it (no resize handles or zoom button that I can find).
+
+Especially for editing source code blocks, being able to bump the size waaay up would be very helpful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Manual:CORS?veaction=edit
+
+**Attached**: {F12119}",1382271000,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-7kzo6bgqrlkpwpxqbvsn,task_description,resolved
+VisualEditor inspector for SyntaxHighlight is too tiny with no resize option,"Change 247567 merged by jenkins-bot:
+Use dialog for editing block level syntax highlights
+
+[[https://gerrit.wikimedia.org/r/247567]]",1445528831,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7kzo6bgqrlkpwpxqbvsn,task_subcomment,NA
+VisualEditor inspector for SyntaxHighlight is too tiny with no resize option,"Change 247567 had a related patch set uploaded (by Esanders):
+Use dialog for editing block level syntax highlights
+
+[[https://gerrit.wikimedia.org/r/247567]]
+",1445350935,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7kzo6bgqrlkpwpxqbvsn,task_subcomment,NA
+VisualEditor inspector for SyntaxHighlight is too tiny with no resize option,"That inspector shown in that screenshot is not one from the SyntaxHighlight extension. Rather, it's the default dialog VisualEditor provides to allow editing of unknown MediaWiki tags (e.g. ones not registered elsewhere with a dedicated interface for known attributes and validating of values).
+
+The SyntaxHighlight dialog or VisualEditor was merged only a few days ago:
+{T45126}
+
+It'll be deployed in wmf12 next week. Here's a screenshot from beta:
+
+{F183659}
+http://en.wikipedia.beta.wmflabs.org/wiki/Python?veaction=edit
+
+Which.. is also not very big.  Keeping this task unresolved for now.
+
+A few ideas:
+* Button to turn dialog into ""full page"" size.
+* By default, inner height unrestricted (however large the textarea is, autogrowing when changing it). With outer height providing scroll overflow based on browser window size.
+* Or; default to OOjs UI ""large"" or ""larger"" size at least.",1435307612,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7kzo6bgqrlkpwpxqbvsn,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"On the English Wikipedia, I'd like to be able to use the VisualEditor on any namespace, but especially the project namespace.
+
+Given that VisualEditor is opt-in and already regularly breaks pages anyway, I don't think lifting the arbitrary namespace restriction on wikis where VisualEditor is opt-in (such as the English Wikipedia) will be problematic.
+
+Submitted for consideration. CC'ing James and Roan.
+
+--------------------------
+
+See also: {T57968}",1381937700,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hmwjwgzjxsoee75bqkok,task_description,duplicate
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"(In reply to comment #3)
+> (In reply to comment #1)
+> > If VE is OK to edit a namespace (and, in general, it's probably fine for
+> > any that aren't signed, Template: or MediaWiki:) then we should just make
+> > that config change and not vary it per wiki. Make a distinct bug for that?
+> 
+> I vaguely understand what you're saying here, but I think it would be best if
+> you filed the bug.
+
+Sure - bug 55968 filed.",1382372495,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"This is not a site request but a VisualEditor enhancement.
+
+The check in [1] needs to be moved somewhere else (one of the hooks in VisualEditor.hooks.php?).
+
+[1] https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor.git/a531b396981042da09280df2ea5dceb6be3fa106/ApiVisualEditor.php#L218",1382168909,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"(In reply to comment #1)
+> If VE is OK to edit a namespace (and, in general, it's probably fine for
+> any that aren't signed, Template: or MediaWiki:) then we should just make
+> that config change and not vary it per wiki. Make a distinct bug for that?
+
+I vaguely understand what you're saying here, but I think it would be best if you filed the bug.",1381982024,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"Let's take a step back here. Here's my use-case: I don't edit articles very much, but I still want to be able to test VisualEditor when I do occasionally edit non-articles. Today I came across [[Wikipedia:Meetup/DC]] and wanted to use VisualEditor to edit it. I wasn't able to. :-(
+
+You bring up a good point about user signatures, but many project-space pages are informational in nature, not discussion-oriented.
+
+Perhaps there's some way to programmatically detect whether a page is a discussion page?
+
+Or perhaps we can remove the hard restriction on VisualEditor editing? For example, if I try to navigate to <https://en.wikipedia.org/w/index.php?title=Wikipedia:Meetup/DC&veaction=edit> directly, VisualEditor won't load. We could remove the hard restriction and leave in place the soft restriction (not exposing the user interface tab). This would allow people like me to just hack in an extra tab. Dirty, but probably fine for now.",1381981978,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"Three things:
+
+1 - If VE is OK to edit a namespace (and, in general, it's probably fine for any
+    that aren't signed, Template: or MediaWiki:) then we should just make that
+    config change and not vary it per wiki. Make a distinct bug for that?
+
+2 - Project: is frequently signed, especially on enwiki, so I think giving a VE
+    editor in this context would be confusing and actively wrong. There is no VE
+    tool for signing comments, nor for creating the definition lists which are
+    (ab)used so very widely for MediaWiki discussions right now. The intent has
+    always been that signed content would be covered by Flow, and I think trying
+    to build tools now for a few months' usage would be a diversion from the main
+    task of improving VisualEditor.
+
+3 - I think that this would end up being a rather broken user experience when a
+    wiki switched from opt-in to opt-out, and all the pages that you used to be
+    able to edit with VE suddenly vanish in a cloud of WT-only smoke, without any
+    explanation or obvious cause.
+
+Consequently, minded to WONTFIX, but am open to suggestions",1381939682,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+Flow: VE takes significant time to manifest,"We have been encountering a number of performance issues and race conditions with VE and Chrome in recent times, this is probably one more of those. 
+
+* In a fresh instance of Chrome 30 or Chrome 29, as a logged in user, visit https://en.wikipedia.beta.wmflabs.org/wiki/Special:Flow/Flow_QA
+
+* Enter a Message topic
+
+The VE controls and CE field take significant time to appear while the user sees a spinner.  For an example causing a failure in a browser test, see https://wmf.ci.cloudbees.com/job/Flow-en.wikipedia.beta.wmflabs.org-linux-chrome/12/testReport/(root)/Create%20new%20topic%20logged%20in/Add_new_Flow_topic/ .  Note the test times out with the spinner still visible after 5 seconds. 
+
+This is not seen in Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381877940,PHID-USER-kqibbfgfpgocyzwe32lv,PHID-TASK-mef22t3vme6fkzexu6mp,task_description,invalid
+Flow: VE takes significant time to manifest,"We removed the VE option in Flow long, long ago :) 
+
+People should feel free to reopen this when we actually have the VE in Flow option up and running again.",1390958494,PHID-USER-yu5wnmvkjecufsjgh2fa,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,"I've tested it on my own box. It's this call that takes the long time:
+
+'http://localhost/mw-dev/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cdata%2Cicons-vector%2Cstandalone%7Cext.visualEditor.viewPageTarget.icons-vector%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20131106T030133Z&*'
+
+This typically returns in ~6 seconds. However, I've found that sometimes it works in ~200ms. When that happens, VE loads quickly on my local box.
+
+So it does indeed seem to be caching, of a particular ResourceLoader resource.",1383707587,PHID-USER-cgfiqjzsqzd7ulp7eyr7,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,Aha; thanks for letting me know :).,1382990815,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,"(""RESOLVED LATER"" was replaced with the ""lowest"" priority. Might want to use that instead.)",1382990684,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,This is likely a problem with the Labs instance; no varnish == no caching of VE elements :/. Unfortunately that means it's something we're probably not going to be able to track or test properly until we go into deployment on production. Closing as WONTFIX since LATER is no longer available.,1382990575,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/324, but people from the community are welcome to contribute here and in Gerrit.",1382030051,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"**Author:** `swalling`
+
+**Description:**
+The introductory dialog for VE is supposed to be seen only once per person. However, it seems that the way it is hidden for users is dependent on session information, probably a cookie? 
+
+This means that every time I clear my cookies, open an incognito browser window, use a new browser, or use a new device, I get the intro again. Even if I'm using the same account. This stinks. 
+
+In GuidedTours we solve this problem (not showing users repeated intro tours across devices/sessions) by setting a hidden preference when someone completes a tour. I'd like to suggest we do that for the VE intro, unless someone can think of a more elegant way to avoid this annoying behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381393200,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-un4pzbob5j2l45f2pfnt,task_description,resolved
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"(In reply to Tom Hart from comment #5)
+> Where is this preference to turn of the Welcome overlay located? I am always
+> getting the ""Welcome..."" dialog when I click Edit, while logged in on the
+> same machine, same session... I'm using Chrome Version 35.0.1916.114 on
+> Mavericks 10.9.2.
+
+It's hidden, only the server interacts with it. This is bug 65821",1401217681,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"**tahart** wrote:
+
+Where is this preference to turn of the Welcome overlay located? I am always getting the ""Welcome..."" dialog when I click Edit, while logged in on the same machine, same session... I'm using Chrome Version 35.0.1916.114 on Mavericks 10.9.2.",1400877136,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"Change 125914 merged by jenkins-bot:
+mw.ViewPageTarget: Hide the welcome dialog via a preference if possible
+
+https://gerrit.wikimedia.org/r/125914",1399723586,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"Change 125914 had a related patch set uploaded by Jforrester:
+Hide the beta welcome via a preference, not a cookie, for logged in users
+
+https://gerrit.wikimedia.org/r/125914",1397518857,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"**swalling** wrote:
+
+(In reply to comment #1)
+> Yay more preferences bloat (and a slower page load). :-(
+> 
+> Given that the welcome dialog is temporary, I was tempted to WONTFIX this,
+> but
+> if someone wants to code it up we might consider accepting it.
+
+In this case, the preference is hidden so while it might be bloat, it's not the kind that clogs up Special:Preferences. I'm not sure what's worse: presenting an unnecessary modal repeatedly or slowing page load time. Have we actually quantified how much each preference slows page load?",1390848538,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"Yay more preferences bloat (and a slower page load). :-(
+
+Given that the welcome dialog is temporary, I was tempted to WONTFIX this, but if someone wants to code it up we might consider accepting it.",1390818198,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+"""Publish and submit"" button shouldn't be available because it shouldn't be used","Per discussion with Krinkle on IRC, the ""publish and submit"" button in Gerrit should not be used.
+
+If this is the case, it should not be present.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1380910920,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-gys4tf753s77f4zdjpsb,task_description,resolved
+"""Publish and submit"" button shouldn't be available because it shouldn't be used","Interesting, ""Publish and Submit"" is gone via upgrading. You can't submit from the review box anymore.",1469470370,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-gys4tf753s77f4zdjpsb,task_subcomment,NA
+"""Publish and submit"" button shouldn't be available because it shouldn't be used",Actually sometimes you are required to force merged.,1468340685,PHID-USER-bxp7xrbobtrp5o3q3swv,PHID-TASK-gys4tf753s77f4zdjpsb,task_subcomment,NA
+"""Publish and submit"" button shouldn't be available because it shouldn't be used","* Our Gerrit config requires V+2 to be present. We can change Jenkins to do V+1 on the patch test so that it doens't clash with the V+2 vote for the submit test, that resolves the ambiguity and will make the submit button not appear before it should.
+
+* Alternatively, like for various repositories already (including VisualEditor) we could remove the ""Submit"" right from regular users (e.g. only for JenkinsBot and l10nbot, and some ops maybe).",1380911098,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-gys4tf753s77f4zdjpsb,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","(Where the word is the actual working part of the element).
+Probably not a real bug, since it is triggered by a user mistake (who should remove the brackets), but since it's easily reproduceable, here are the steps:
+take any <nowiki>[[link]]</nowiki> created like this (by ignoring the markup warning).
+VEdit the page and use the linking tool on the word inside the brackets.
+Save, you now have [[[[link]]]], and of course the nowiki tags are gone.
+
+https://www.mediawiki.org/w/index.php?title=User:Elitre_(WMF)/SandboxVE&diff=prev&oldid=794483
+
+https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=794473&oldid=794472
+
+Just interested in understanding whether VE wants or can do something about it.
+
+(Note that it is absolutely possible to get the same result with the traditional editor as well, https://sl.wikipedia.org/w/index.php?title=Klerofa%C5%A1izem&diff=next&oldid=4101482 ).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380727020,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_description,resolved
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","Change 104695 merged by jenkins-bot:
+(Bug 54877) Tokenize [[[[Foo]]]] correctly
+
+https://gerrit.wikimedia.org/r/104695",1388700351,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","Change 104695 had a related patch set uploaded by Subramanya Sastry:
+WIP (Bug 54877) Tokenize [[[[Foo]]]] correctly
+
+https://gerrit.wikimedia.org/r/104695",1388448649,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","Re-re-phrasing the title (and yes, this appears to be a Parsoid bug, but a very low priority one).",1380845739,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","Rephrasing bug. A user would not have a goal to generate 4 brackets in wikitext, but the use case of typing (or editing existing pages that do have) [[ around a link, that is genuine content that VisualEditor should be able to create and edit.",1380728622,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","This is probably a bug in Parsoid, not VisualEditor.
+
+Given a page containing:
+
+[[[[Sandbox]]]]
+
+Which contains no <nowiki>, this is parsed as [[<a href=Sandbox>Sandbox</a>]] by the PHP parser and renders accordingly.
+
+When editing that page in VisualEditor, the initial rendering is wrong (it renders as a text node ""[[[[Sandbox]]]]"", no anchor link).
+
+If I add text to that line or change the word to something else, the serialisation from Parsoid is still the same (no <nowiki> is inserted, so Parsoid is unaware of it being a link both in parsing and serialising).
+
+
+Given a page containing:
+
+<nowiki>[[[[Sandbox]]]]</nowiki>
+
+When editing that in VisualEditor, the initial rendering is correct (1 text node containing ""[[[[Sandbox]]]]"").
+
+If I add text to that line or change the word to something else, the serialisation from Parsoid is no longer the same. It dropped the <nowiki>, thus effectively (according to the PHP parser) turning it into a link after saving.",1380728435,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+[DO NOT USE] VisualEditor: Tracking bugs for VisualEditor (tracking) [superseded by #VisualEditor],"[Unused; we don't do tracking bugs, post-Phabricator transition.]
+
+A central place for people to keep track of tracking bugs for VisualEditor. (Yay for bug meta-ness.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379656500,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ncpmmwig7janid6ikysj,task_description,invalid
+[DO NOT USE] VisualEditor: Tracking bugs for VisualEditor (tracking) [superseded by #VisualEditor],[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343622,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-ncpmmwig7janid6ikysj,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Missing scan and edit toolbar
+
+I am posting three separate bugs and mentioning this in this first report because they are somewhat related.
+
+The user defined edit toolbar, defined in my very simple
+https://en.wikisource.org/wiki/User:Ineuw/common.js stopped functioning in this latest version of the mw software. In versions previous, it worked reliably and always, permitting me greatly increased productivity. The toolbar does show up intermittently and occasionally. 
+
+Regardless of the toolbutton definition syntax used, the same intermittent functioning is the result. The syntax is either the current definition one, or an older one:
+
+mw.toolbar.addButton(
+        '',
+        ' Æ ',
+        'Æ',
+        '',
+        '',
+        ''
+);
+
+I also used the definitions without image buttons, thinking that this may be the cause, but it doesn't make a difference.
+
+The problem is also not browser related. I tried other browsers and OS's as well:
+
+Firefox in Windows, Xubuntu, and Apple OSX.
+Safari in Windows and Apple OSX.
+Google Chrome in Windows and Linux (Xubuntu).
+but the intermittent behaviour is the same. . . . . 
+
+Finally, this is also true on the Commons and Wikipedia, where it's less critical because I am not so active on those wikis.
+
+Please see attached image.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+
+**Attached**: {F11589}",1379578860,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-r3avdlac5as6usqbtpvz,task_description,declined
+Customized legacy edit toolbar does not always load correctly,"I ask that this bug be closed, since I accepted the demise of the old wiki toolbar.",1379736095,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"(In reply to comment #8)
+> I also got the same Firefox (23.0.1) error as Andre Klapper. If this seems to
+> be the cause, can't it be corrected?
+
+It might either be an issue in your code in common.js, or some changes in MediaWiki. Apart from Alex' cleanup which got merged at the beginning of September I cannot see any changes in
+https://git.wikimedia.org/history/mediawiki%2Fcore.git/HEAD/resources%2Fmediawiki.action%2Fmediawiki.action.edit.js
+
+> Finally, this is a very big disappointment because the replacement option is
+> very awkward. Among other things, it takes up (and unnecessarily) a lot of
+> screen real estate and I work on a 22"" screen.
+
+I don't see that big difference in size. Not sure if we refer to the same things?
+The legacy toolbar had enough issues (e.g. it was never meant to be expanded so inserting required exposing and dealing with implementation details) so it got replaced by the current toolbar.",1379680607,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"I am not the only one who is using the toolbar at Wikisource. While other users have occasional issues, theirs seem to work on most cases. 
+
+I also got the same Firefox (23.0.1) error as Andre Klapper. If this seems to be the cause, can't it be corrected?
+
+Finally, this is a very big disappointment because the replacement option is very awkward. Among other things, it takes up (and unnecessarily) a lot of screen real estate and I work on a 22"" screen. Krinkle's opinion is akin to taking away a mechanic's trusted tools because he doesn't personally favor them. He should try his hand at some proofreading for a day or two.",1379623232,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"To quote Krinkle: 
+""The classic edit toolbar has long been deprecated. The default was replaced
+with WikiEditor on Wikimedia in a 2010 deployment"", plus VisualEditor is also around the corner.
+Setting lowest priority, might be even a WONTFIX.",1379601766,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Created attachment 13327
+Character selection moved too low in new mw software version
+
+To the attention of Andre Klapper
+
+This is the missing image of the drop down character set selector
+
+**Attached**: {F11593}",1379590215,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Created attachment 13325
+old style toolbar coding
+
+This text contains the legacy toolbar layout, without captions by the elements, no images, and notice the function syntax difference. It doesn't matter which I use, the behaviour is identical.
+
+mw.toolbar.addButton(
+
+and NOT 
+
+mw.toolbar.addButtons(
+
+**Attached**: {F11592}",1379589793,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Created attachment 13324
+Legacy edit toolbar displayed.
+
+**Attached**: {F11591}",1379589573,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Hi. I am sorry to confuse you. The new edit toolbar was activated so that I could take a proper snapshot and I forgot to turn it off. Otherwise, it's not usable for me at the moment.
+
+Wikisource users, who use edit toolbar buttons, use the ""legacy"" old style because it's more versatile. For my main project work of Popular Science Monthly, I only need the 12-14 extended ANSI to accommodate French and German and occasionally Greek. 
+
+I am also working on Hebrew/Arabic texts, and not being able to access the dropdown box of character selections, this forced me to try using the ""advanced"" WikiEditor toolbar in which my language setting places things in reverse order.
+
+I am attaching what should be the correct display of the legacy toolbar when it works.",1379589495,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Hi ineuw,
+
+your screenshot looks like the old toolbar to me, instead of the WikiEditor toolbar. Is that intended or part of the problem?
+
+The WikiEditor toolbar should look like your screenshot in https://bugzilla.wikimedia.org/attachment.cgi?id=13323
+
+I went to 
+https://en.wikisource.org/w/index.php?title=Page:Popular_Science_Monthly_Volume_63.djvu/155&action=edit
+to reproduce the problem (Firefox 23.0.1) and switched to horizontal layout.
+
+I also copied your ""common.js"" file to my user account (the file basically just has a number of ""mw.toolbar.addButtons"" calls).
+
+The scanned image still loads for me, and I get the correct WikiEditor toolbar, but in Firefox' Error Console I get:
+
+Timestamp: 09/19/2013 11:52:12 AM
+Error: TypeError: mw.toolbar is undefined
+Source File: https://bits.wikimedia.org/en.wikisource.org/load.php?debug=false&lang=en&modules=user&only=scripts&skin=vector&user=AKlapper+%28WMF%29&version=20130919T095201Z&*
+Line: 1
+
+I have bug 47872 in mind.",1379585655,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Created attachment 13321
+edit toolbar is showing occasionally
+
+**Attached**: {F11590}",1379578978,PHID-USER-kdpydfvhr2l2qcrbvvz7,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"The link input widget should have separate fields for the link target and the displayed text.
+
+From various comments at T50789
+
+> There are essentially two ways to create a link:
+> 
+> […]
+> 
+> #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.
+> 
+> […]
+> 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 [T54462]
+> 
+> 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.
+
+---
+>>! In T50789#510194, @Thryduulf wrote:
+> An 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. 
+>
+> See also T53438
+
+---
+>>! In T50789#510207, @Thryduulf wrote:
+> 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]].
+
+--------------------------
+**See Also**: T52945",1378772640,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g66fda6j3q2ga6eul3do,task_description,resolved
+VisualEditor: Link input widget should have separate inputs for target and display text,"Change 303956 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] LinkAnnotationInspector: add a ""label"" field on mobile
+
+[[https://gerrit.wikimedia.org/r/303956]]",1566512170,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Change 303956 restored by Esanders:
+LinkAnnotationInspector: add a ""label"" field
+
+[[https://gerrit.wikimedia.org/r/303956]]",1561206667,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"The solution in T124305#4321883, which is implemented and will be live in two weeks, should effectively resolve this task.",1530193718,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Change 303956 abandoned by Jforrester:
+LinkAnnotationInspector: add a ""label"" field
+
+Reason:
+It was decided to go with Iad48fb55 instead.
+
+[[https://gerrit.wikimedia.org/r/303956]]",1530047719,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,Looks like we're going with the solution Pau proposed above – please see T124305 for details.,1529601576,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,FYI: Issues which are caused by the lack of a clear separate visualization of both link destination and link title on the German-language Wikipedia can be seen [[ https://tools.wmflabs.org/persondata/ve.php | with this tool]].,1522158502,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"@Pginer-WMF That looks like it would resolve at least most of the issues I have with the current set-up, and as long as it is obvious that truncation has happened when it has then there are no immediate problems with it I can see. ",1518921766,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"One possible approach to explore would be to expose a shortcut for editing the label that results in selecting the link label in place. In this way, there is no duplication of the places used to edit the label (avoiding the issues described above) while making the entry point for editing the label more explicit. We need to be cautious for the later not to cause issues, and test with users accordingly if we decide to explore this direction anytime.
+
+The idea is illustrated below:
+
+{F13736398, size=full}
+- A separate section of the inspector is added about the label. The current label can be cropped if too long, it is there just for reference.
+- Clicking on the section hides the inspector and selects the text label inside the link for the user to type the new one.  Temporary time-based tooltip can appear to indicate to ""type the new label"" if needed.",1518605752,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'm really not at all sure that the actual benefits of this task to the people who are at the sharp end are actually understood by the developers. There is a reason that this has been resurrected at least twice, has at least four duplicate tasks, and the requests for it continue more than 5 years after it was first requested. Indeed this is one of just two tasks (T51969 is the other, and this is far more important than that) that are standing between where we are now and VE being intuitively easy for both new and power editors to use simply and reliably for non-specialist editing in almost all reasonable circumstances without making unforced errors.
+
+Links are utterly fundamental to the way wikis work and VE is intended to be used by inexperienced users, so it is completely and utterly mind boggling to be told that something that forces unintuitive workarounds to achieve something that should be absolutely basic skill level 0.2 (at most) will not be fixed. ",1502273460,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"There is an insane amount of complexity with links in wikis due to the nature of how much they're used. Any change in this area would divert a lot of product and design time away from other projects, thus making changes here incredibly costly. Given the limited benefit of doing work here compared to other projects, this task is not going to be worked on any time soon. That is, after all, why James declined it twice. The debate here is interesting, but it is mostly academic at this point.",1502126282,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"There is an insane amount of complexity with links in wikis due to the nature of how much they're used. Any change in this area divert a lot of product and design time away from other projects, thus making changes here incredibly costly. Given the limited benefit of assigning work here compared to other projects, this task is not going to be worked on any time soon. That is, after all, why James declined it twice. The debate here is interesting, but it is mostly academic at this point.",1502126250,PHID-USER-kve2ug5yc3dp6ighnmqk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3505027, @Whatamidoing-WMF wrote:
+>> if a link targets a page that matches exactly the link label, and a user changes that label to the name of a different page, the software can suggest the target also to be updated.
+> 
+> That would be very annoying every time someone needs to change the ending of a link.  `[[Example]]s` is a good link.  `[[Example|Examples]]` is bearable.  Having Clippy ask you if you want to change the link from ``[[Example]]` to `[[Examples]]` every time you try to fix the grammar in a sentence is not bearable.
+
+I think that whether the approach is annoying or not would depend on its execution, and how prominently the suggestion is presented. Clippy represents the annoying extreme of suggestion mechanisms: causing distraction as an animated character, and providing unreasonable suggestions (""what made Clippy think this could be a letter?""). In this case, the approach should be much more subtle (no animated characters) and the connection on why a suggestion is provided is quite clear (so even if it is not what you want, there is not a big surprise that the suggestion was provided). More like [[ https://www.youtube.com/watch?v=qcm0rG8EKXI | Google instant ]] than Clippy.
+
+In that particular example, given that ""Examples"" is a redirect to ""Example"", we can probably show no suggestion at all.",1502096404,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> if a link targets a page that matches exactly the link label, and a user changes that label to the name of a different page, the software can suggest the target also to be updated.
+
+That would be very annoying every time someone needs to change the ending of a link.  `[[Example]]s` is a good link.  `[[Example|Examples]]` is bearable.  Having Clippy ask you if you want to change the link from `[[Example]]` to `[[Examples]]` every time you try to fix the grammar in a sentence is not bearable.",1502123192,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> if a link targets a page that matches exactly the link label, and a user changes that label to the name of a different page, the software can suggest the target also to be updated.
+
+That would be very annoying every time someone needs to change the ending of a link.  `[[Example]]s` is a good link.  `[[Example|Examples]]` is bearable.  Having Clippy ask you if you want to change the link from ``[[Example]]` to `[[Examples]]` every time you try to fix the grammar in a sentence is not bearable.",1502077881,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3500032, @Thryduulf wrote:
+>>>! In T55973#3491393, @ssastry wrote:
+>> When you want to change the label, can't you just change the label text without opening the link editor? 
+> There is no way for the software to know which you intend, and no way for the naive user to know which has actually happened without actively opening the link editor, but it is likely that the assumption will be that both were changed (per @Whatamidoing-WMF).
+
+There is no way for the software to know, but the software could pay attention to some clues. As I mentioned in T55973#2792012, if a link targets a page that matches exactly the link label, and a user changes that label to the name of a different page, the software can suggest the target also to be updated. That would give visibility to the user on the mismatch between label and target, and let the user to update the target in one click if needed as some word processors do with spellcheckers.",1501835793,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3491393, @ssastry wrote:
+> When you want to change the label, can't you just change the label text without opening the link editor? 
+The problem is that when you do that you could be intending to change the label without the link or you could be intending to change both label and link. There is no way for the software to know which you intend, and no way for the naive user to know which has actually happened without actively opening the link editor, but it is likely that the assumption will be that both were changed (per @Whatamidoing-WMF). Remember that VE is focused towards inexperienced and less-computer-literate users rather than power users, so there will be a very high proportion of users who do not know that you need to actively check what VE is doing. 
+
+Related to this, some way of identifying in the VE editing surface whether a link is piped or not would be useful in many different scenarios. I've only just thought of this but I've run out of time to investigate whether there is an existing task for this or not, so I'll pop it on VE/F and return to it this evening.
+",1501835075,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3491393, @ssastry wrote:
+> ... that hack is probably unpleasant, but at last for simple label text edit scenarios, it should work just fine?
+
+It works okay, assuming that you actually know that you have to follow all of those steps.  However, I think that we've proven that this is an invalid assumption in at least a substantial fraction of cases.  We have thousands of editors who are accustomed to changing a link such as `[[2016]]` to `[[2017]]` by only changing the visible number.  When you do that in VisualEditor, you end up with `[[2016|2017]]`.
+",1501630681,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3224611, @Thryduulf wrote:
+> Well that news is a big disaapointment as the inability to quickly, easily, reliably and unambiguously change the destination the destination and/or description of a link is the biggest single impediment to Visual Editor.
+> 
+> When changing a link you could want to do one of three things:
+> 1. Change the label
+> 2. Change the target
+> 3. Chang both.
+> 
+> The only way to be sure that the change you want to make is the one being made is to:
+> 1. delete the current link, making sure to note the exact title and capitalisation of any section links
+> 2. type the label
+> 3. select the label
+> 4. open the link dialog
+> 5. enter the link, appending section links if necessary
+> 6. close the link dialog.
+
+When you want to change the label, can't you just change the label text without opening the link editor? But yes, in certain label-edit scenarios, one hack you have to rely on is to make sure there is at least one character left behind with the link and delete that character last ... that hack is probably unpleasant, but at last for simple label text edit scenarios, it should work just fine?",1501628448,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Well that news is a big disaapointment as the inability to quickly, easily, reliably and unambiguously change the destination the destination and/or description of a link is the biggest single impediment to Visual Editor.
+
+When changing a link you could want to do one of three things:
+1. Change the label
+2. Change the target
+3. Chang both.
+
+The only way to be sure that the change you want to make is the one being made is to:
+1. delete the current link, making sure to note the exact title and capitalisation of any section links
+2. type the label
+3. select the label
+4. open the link dialog
+5. enter the link, appending section links if necessary
+6. close the link dialog.
+
+In Google Docs you need to.
+1. select the link
+2. open the link dialog
+3. change what needs to  be changed
+4. close the link dialog
+
+Google Docs users, to my knowledge, don't find this unnecessarily heavyweight but rather simple and reliable.",1493599292,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"For clarity, this task isn't likely to have work on it soon.
+
+In general, this goes strongly against the design philosophy of the tools, making the process of adding links much ""heavier"" and context-switching. Re-validating the research results would take a lot of time and effort. In practice users don't have as many problems with this area as with others that are higher importance.",1490394770,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Another problem to take into consideration are disambiguation pages. Example:
+1. I add a link to https://en.wikipedia.org/wiki/John_Quested_(producer)
+2. I then change the label (which has automatically been set to ""John Quested (producer)"") to just ""John Quested"".
+In this case I do not want any automatism to change the link, and actually not even a suggestion to do so.
+
+In this case this can easily be detected, as https://en.wikipedia.org/wiki/John_Quested is marked as disambiguation page. But doing the same steps with https://en.wikipedia.org/wiki/Albert_Einstein_(album) should work, too, without changing the link accidentally to https://en.wikipedia.org/wiki/Albert_Einstein, even though that page isn't a disambiguation.",1479205506,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2792226, @matmarex wrote:
+> Another idea (strawman): If a wikilink's target is identical to label, we could just synchronize the target with the label when the label is changed. In both the link context and the link inspector, there would be a ""lock/unlock"" button to toggle this behaviour for the currently focused link.
+
+Thanks for the proposal, @matmarex. As pointed out above, the difference is about how much automatic we need the process to be.
+
+Changing the target automatically solves the problem without requiring the users to notice what is going on, which works rally well when it does the right thing. However it creates a stronger inconsistency of expectations when editing a link and has a higher cost for false positives:
+- Inconsistency of expectations. Some links will change their target and others won't. Changing ""lemon"" to ""orange"" will change the target, but changing ""lemons"" to ""oranges"" won't. Conversely, with the proposed approach editing the document will change always the label for all kinds of links, but it will provide a suggestion to change the target too for some of them.
+- Cost for false positives. The Tokyo article indicates that it is the ""capital"" (linking to [[ https://en.wikipedia.org/wiki/Capital_of_Japan | ""Capital of Japan"" ]], not to [[ https://en.wikipedia.org/wiki/Capital | ""Capital"" ]]. The user can add a link to ""Capital of Japan"", change it to just say ""capital"" and either miss that it now points to a different article or get annoyed by having to recreate the link again on an autocorrect-like situation.
+
+
+>>! In T55973#2792689, @DLynch wrote:
+> * It's hard to change the link text completely. Selecting the entire thing by dragging is prone to accidentally selecting outside the link annotation and thus un-linking it when you start typing. Common case: people who paste in a URL letting it auto-link, and then want to add a descriptive label.
+
+This is an interesting case too, thanks for pointing to this, @DLynch. I wonder if we could facilitate things by selecting the whole label when the link is selected/added (similar to what ""add label"" does for quick links). This can be applied to either to (a) links with a URL as label, or (b) links that got their label automatically and have not been edited before.
+It is hard to anticipate how that may interfere with all the other editing processes, but it may be worth prototyping an example to check how it feels in practice.",1479145858,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> This issue seems to happen when editing a link that uses the page title as label. This may bring expectations of such information to remain in sync when changing the link (or even not being aware of the target potentially being different from the textual representation).
+
+I do think that's only half of the issue, mind you. There's:
+
+* It's easy to let the link text and URL get out of sync, if they were initially the same. This will show up with internal wikilinks, and URLs which are shown in full.
+* It's hard to change the link text completely. Selecting the entire thing by dragging is prone to accidentally selecting outside the link annotation and thus un-linking it when you start typing. Common case: people who paste in a URL letting it auto-link, and then want to add a descriptive label.
+
+Your suggestion helps with the former, but not the latter. I grant that this is entirely anecdotal, but I started working on this task because the latter issue was bugging me in-practice while I used VE (whereas the former hadn't actually come up for me) so it's the one I have more personal connection to. :D
+
+> Is that like T56947?
+Sort of. T56947 proposes basically exactly what @Pginer-WMF suggested -- a ""you might want to update this"" popup -- whereas @matmarex's suggestion is a more-aggressive version of that which forces the update unless you explicitly opt out.
+
+I think it's basically the system proposed there, yeah. We don't currently have a convenient ""suggest a change"" system in context popups like this, but it's certainly addable if we want it. Making it keyboard-accessible as suggested would break the current paradigm, but it's not like context popups are //currently// keyboard-accessible anyway, so...",1479141371,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2792226, @matmarex wrote:
+> Another idea (strawman): If a wikilink's target is identical to label, we could just synchronize the target with the label when the label is changed. In both the link context and the link inspector, there would be a ""lock/unlock"" button to toggle this behavior for the currently focused link.
+> 
+> I think this would eliminate the user errors of the kind we see now. On the other hand, it would make it somewhat annoying when you actually wanted to change the label (especially when writing in languages with rich inflexion).
+
+Is that like T56947?",1479126440,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Another idea (strawman): If a wikilink's target is identical to label, we could just synchronize the target with the label when the label is changed. In both the link context and the link inspector, there would be a ""lock/unlock"" button to toggle this behavior for the currently focused link.
+
+I think this would eliminate the user errors of the kind we see now. On the other hand, it would make it somewhat annoying when you actually wanted to change the label (especially when writing in languages with rich inflexion).",1479125778,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2789271, @matmarex wrote:
+>> As I understand it, the main problem occurs when adding a link without any previous text selection.
+> 
+> I think the biggest problem here is in editing links.
+
+Thanks for the illustrative examples, @matmarex.
+This issue seems to happen when editing a link that uses the page title as label. This may bring expectations of such information to remain in sync when changing the link (or even not being aware of the target potentially being different from the textual representation).
+
+I think those cases (where the label and page name matches) could be detected by VE and provide some support to quickly solve the out-of-sync status. For example, I illustrated below how we can surface that once the user changed the label, the link is pointing to the old page but that can be changed to point to a page that matches the new label. Clicking on the suggestion (or using keyboard down arrow to select it + enter) will update the link target without writing it twice.
+
+{F4723857, size=full}
+
+
+In the example above, having separate fields for editing label and target won't be very useful since we are not accessing the editing mode where those would be shown. It can be argued that making the edit label non-editable on the editing surface could force users to access the link editing panel, but that makes other scenarios more complex (e.g., quick label corrections, or using more complex content as link labels).",1479120130,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,What matma said.,1478931953,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> As I understand it, the main problem occurs when adding a link without any previous text selection.
+
+I think the biggest problem here is in editing links.
+
+For example, a user is editing a sentence like `[[Tim Berners-Lee]] was born in [[1965]].` and wishes to correct the typo (he was actually born in 1955). Editing the visible text in VisualEditor without correcting the link target will result in `[[1965|1955]]`; editing the link target without correcting the text will result in `[[1955|1965]]`; both of these mistakes are easy to make in the current interface and difficult to spot when reviewing, if you're not looking at the wikitext source code.",1478892137,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I think it is important to separate the problem from possible solutions. As I understand it, the main problem occurs when adding a link without any previous text selection. In that context, the way to add a label has not much visibility. This generates confusion about where is the label supposed to be edited and makes it difficult workflows based on a different order than the one supported by default.
+
+Provide a separate field for the link label as suggested above, makes label editing more explicit, but it is duplicating content that is already in the document which causes some different problems.
+
+I was trying to explore a way to make the label editing more inviting right where it is going to be, without any duplication:
+
+{F4716647}
+
+When adding a link with no selection, instead of showing no content in the text, a placeholder element can be added in-place (styled similar to the link that it will become later) for the user to indicate the label, while a selector can be also available to pick the link target.
+
+The content provided by the user in one field can inform the other (e.g., if I write ""rice"" as label, the Rice article should be among the suggestions when I click on the page search).
+
+This is just a rough idea, but I'm curious to hear whether a solution along these lines is considered to help with the issue identified, or use it to identify which parts of the problem that I may be missing.",1478889614,PHID-USER-c47vnc2yxmwfvvc4367q,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> How do you deal with something like `[[Parrot|{{lang|fr|perroquet}}]]`, where the label is built on a template?
+
+Most likely we will just not support cases where the link contains non-text through this particular interface, but they aren't that common.",1478705462,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2777160, @Quiddity wrote:
+>>>! In T55973#2775922, @Trizek-WMF wrote:
+>> How do you deal with something like `[[Parrot|{{lang|fr|perroquet}}]]`, where the label is built on a template?
+> 
+> Is that a regular pattern somewhere? I don't think I've seen it used before, and am interested to see examples.
+
+I've quick-searched on articles I've written and found that exemple [[https://fr.wikipedia.org/w/index.php?title=Mod%C3%A9lisme_ferroviaire&action=edit&section=33|here]]:  `''[[Gorre & Daphetid Railroad|{{lang|en|Gorre & Daphetid Railroad}}]]''` 
+
+I've also searched (ctrl+F) on [[https://fr.wikipedia.org/w/index.php?title=Histoire%20du%20communisme&action=edit|Histoire du communisme]], the biggest article on fr.wp, where I've found:
+* `[[groupe Barta|{{citation|groupe Barta}}]] ` or `[[De chacun selon ses moyens, à chacun selon ses besoins|{{citation|De chacun selon ses facultés, à chacun selon ses besoins}}]]`
+* `[[Kang Kek Ieu|{{citation|Douch}}]]`
+
+There is also cases like `[[1er octobre|{{1er}} octobre]]` or `[[18e congrès national du Parti communiste chinois|{{18e|congrès}} national]]`.
+
+Some cases can be rewritten for sure, but not always.",1478601347,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2775922, @Trizek-WMF wrote:
+> How do you deal with something like `[[Parrot|{{lang|fr|perroquet}}]]`, where the label is built on a template?
+
+Is that a regular pattern somewhere? I don't think I've seen it used before, and am interested to see examples.
+",1478541625,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"One reason to consider keeping the internal-labels is that they're easier to slip into the existing MW extension version of the link inspector, since that has to accommodate the wiki search results alongside the fields.",1478540932,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2769070, @Quiddity wrote:
+
+> Losing occasional text-formatting is an acceptable compromise.
+
+I've slept on that and now I agree.
+
+>>! In T55973#2773796, @Esanders wrote:
+> Inline labels:
+> 
+> {F4698802}
+> 
+> Google docs for comparison:
+> 
+> {F4698804}
+> 
+> I think focusing the link field first, and labelling it ""link"" instead of ""target"" (which is a bit technical) will help. We could also live-update the link as the text field is changed, which would avoid surprises when 'done' is clicked.
+
+I think that's the best for a link made on a raw text.
+How do you deal with something like `[[Parrot|{{lang|fr|perroquet}}]]`, where the label is built on a template?",1478518303,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Inline labels:
+
+{F4698802}
+
+Google docs for comparison:
+
+{F4698804}
+
+I think focusing the link field first, and labelling it ""link"" instead of ""target"" (which is a bit technical) will help. We could also live-update the link as the text field is changed, which would avoid surprises when 'done' is clicked.",1478360692,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> Use a 'placeholder' and insert an invisible label somewhere for accessibility.
+Worth considering that the common-case here is (probably) editing an already-existing internal-wiki link. With a placeholder as the only distinction, that's going to look like this:
+
+{F4693560}
+
+...which is perhaps initially confusing.
+
+Then the secondary case is editing an external link, where keeping the URL field as wide as possible is preferred, because URLs can get pretty long. The advantage of the internal label there is that it really is pretty space-efficient -- no added vertical size, and it's a compact horizontal representation.",1478203630,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2763929, @matmarex wrote:
+> * Just use a FieldLayout :)
+> * Use a 'placeholder' and insert an invisible label somewhere for accessibility.
+
+
+* This would make the inspector much taller, which may or may not be acceptable.
+* When editing the link both fields will be non-empty so the placeholder will never be seen.
+
+Google Docs uses an inline label, which may severely reduce the width if we need to make room for all languages, but this should be considered too.",1478203101,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2768853, @Trizek-WMF wrote:
+> And what if we only display a read-only text for the label?
+> 
+> Label: //2013//
+> Target: 2014
+> 
+> That way, people will notice there is something wrong and will be able to correct the text afterwards, using the full potential of VE.
+
+That would leave a primary use-case as very difficult - pasting or writing a complete replacement for the link label.
+
+I.e. As an experienced wikitext editor, I'm accustomed to writing/pasting the link first, and then writing/pasting the label after a space or pipe. -- With VE, it is hard to select the entire label, in order to paste my clipboard on top, or in order to write it from scratch.
+
+I really like the design given in T55973#2761021 above.
+Losing occasional text-formatting is an acceptable compromise.",1478194854,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2768853, @Trizek-WMF wrote:
+> And what if we only display a read-only text for the label?
+> 
+> Label: //2013//
+> Target: 2014
+> 
+> That way, people will notice there is something wrong and will be able to correct the text afterwards, using the full potential of VE.
+
+That would leave a primary use-case as very difficult - pasting or writing a complete replacement for the link label.
+
+I.e. As an experienced wikitext editor, I'm accustomed to pasting the link first, and then writing the label after a space or pipe. -- With VE, it is hard to select the entire label, in order to paste my clipboard on top, or in order to write it from scratch.
+
+I really like the design given in T55973#2761021 above.
+Losing occasional text-formatting is an acceptable compromise.",1478194804,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2768853, @Trizek-WMF wrote:
+> And what if we only display a read-only text for the label?
+> 
+> Label: //2013//
+> Target: 2014
+> 
+> That way, people will notice there is something wrong and will be able to correct the text afterwards, using the full potential of VE.
+
+This is another good option (I may have suggested it in the past).
+
+ps Note that we will be able to handle the example you gave just fine because the annotation (italic) spans the whole link. A better example would be:
+
+Label: Season //2014//
+Target: Season 2014",1478193377,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"And what if we only display a read-only text for the label?
+
+Label: //2013//
+Target: 2014
+
+That way, people will notice there is something wrong and will be able to correct the text afterwards, using the full potential of VE.",1478192130,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I do agree that showing wikitext is the wrong way to go. This is a prime user-facing tool, which a majority of users are going to be interacting with regularly, not something far more power-usery like templates.
+
+If we want to preserve the rare cases of internal formatting, we should go all out and have a VE surface inside the inspector... which I think makes it far too heavy for what's normally an incredibly quick action.
+
+Technically, I suppose there's alternatives like diffing/merging the change to the label so that we keep the annotations if the section they cover wasn't touched. But that's a bunch more work on our end, and moves towards being too magic for the user to understand why the formatting sometimes stays and sometimes goes.",1478191646,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Also, as a volunteer, I don't want to hear ""quotes on the text are making italics, that's a bug"" from a newbie. That's a request for my personal comfort, Sherry ;)
+
+>>! In T55973#2768788, @Esanders wrote:
+> Showing wikitext is not the right thing to do. Links with *partial* formatting are very rare, and editing their text rarer. Even in those cases the user can just edit the text directly. If the user edits the label in this very rare case they will get immediate visual feedback of the change. Let's not make perfect the enemy of the good.
+
+Wise words!
+
+",1478190964,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Showing wikitext is not the right thing to do. Links with *partial* formatting are very rare, and editing their text rarer. Even in those cases the user can just edit the text directly. If the user edits the label in this very rare case they will get immediate visual feedback of the change. Let's not make perfect the enemy of the good.",1478190826,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Rich display would be nicer (but take up a lot of space).  OTOH, given a link such as `[[Example|the ''blue'' picture]]`, I'd rather see 
+
+```
+the ''blue'' picture
+Example
+```
+
+rather than 
+
+```
+the blue picture
+Example
+``` 
+
+– especially when the second item will silently remove the italics if I touch it.
+",1478189876,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"No wikitext displayed, please! ",1478166975,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"@DLynch, would it be easy enough to make it show wikitext rather than ""plain text"" (i.e., like the template dialog does for parameters)?  Having the internal annotations silently disappear might be annoying (for the very small percentage of links that contain internal annotations).",1478136737,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"The patch currently behaves as:
+
+* If there's any block-level content in the link (e.g. an image), it disables the label field. (Cue taken from Google Docs, which completely hides the field in this case.)
+* If there's annotations on the content (bold, italic, etc), the field is enabled, and contains the plain text version. Making a change to its contents will remove all internal annotations from the link. (i.e. if it's in a block of bold text, it'll stay bold, but if part of the inside was bold, that'll be lost)",1478105014,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'm glad this is being worked on.
+
+>>! In T55973#2761021, @DLynch wrote:
+> {F4685690}
+> 
+> (Prior to any Design feedback.)
+
+Please don't use these weird right-side labels. TextInputWidget's 'label' option should never have been created. :/
+
+Unless design folks invent something new, there are two options that would be consistent with existing interfaces:
+* Just use a FieldLayout :)
+* Use a 'placeholder' and insert an invisible label somewhere for accessibility.",1478104836,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2763892, @DLynch wrote:
+> The other options I came up with are context item:
+> {F4688837}
+> (With attendant ""we need to think up an icon that intuitively symbolizes 'select all'"" dilemma, which nobody else seems to have really cracked. My favorite, after a bunch of searching, was [Blackberry's](https://help.blackberry.com/en/blackberry-leap/10.3.1/help/hjo1405445343190_hiresdevice_en-us.png))
+> 
+> Or inspector:
+> {F4688838}
+
+I'm pretty sure that people will not edit the label with that version. Edit label is not as obvious as it is on your first proposal with two separate fields.
+
+Speaking of which, how do you deal with a label which includes some wikitext formatting, like bold or, worse, an in-line template?",1478104532,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"The other options I came up with are context item:
+{F4688837}
+(With attendant ""we need to think up an icon that intuitively symbolizes 'select all'"" dilemma, which nobody else seems to have really cracked. My favorite, after a bunch of searching, was [Blackberry's](https://help.blackberry.com/en/blackberry-leap/10.3.1/help/hjo1405445343190_hiresdevice_en-us.png))
+
+Or inspector:
+{F4688838}",1478102871,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"{F4685690}
+
+(Prior to any Design feedback.)",1478028816,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Regular users have a really understand creating a mental model of how links work, especially when the label (nearly) matches the target. Having both side by side in the edit area makes it a lot clearer what is going on. More experienced users will be able to use the edit surface as designed.",1470870679,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"To elaborate slightly, 303956,2 adds some protection in to make sure it won't replace the current label text if it hasn't been changed from its initial value, so even internal annotations will be preserved if you're only editing the target.",1470870456,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Moving from gerrit:
+
+**James F:**
+This creates a TextInputWidget which is just wrong; the contents covered by the link annotation could be anything up to and including <span>s, <img>s and so on; this would need to be a complete SurfaceWidget, which would totally dominate this inspector and destroy the whole design of it being a lightweight, simple control. I'm pretty strongly against this change for exactly this reason.
+
+**David L:**
+James: This is totally cribbing from Google Docs' design for link labels. It shows the field... if the label is simple. If it's not simple, it hides it. That lets us give people a field that works in most cases, and won't break anything otherwise.
+Admittedly, I just have it *disabled* if it's not-simple, on the theory that might be less confusing, but I could go full-hidden.
+
+**Ed S:**
+That is technically true, however in almost all cases additional annotations to the link are covering, and can be preserved. This is the same behaviour as Google Docs. Links containing content (e.g. img) are many times rarer still. For these cases we can block/and or warn (or not).",1470870390,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"To clarify the issue about ""display text"", both Google Docs and the patch above will maintain all covering annotations, but will remove any partial annotations if the text is edited (e.g. <a><b><i>He</i>llo</b></a> -> <a><b>Bye</b></a>). Also if the label contains any non-text (e.g. an inline image) it will be uneditable, but this is a very rare edge case.
+
+This should also make the editing of external links and numbered external links a bit cleaner, getting rid of the 'add label' button for numbered external links.",1470850953,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Change 303956 had a related patch set uploaded (by DLynch):
+LinkAnnotationInspector: add a ""label"" field
+
+[[https://gerrit.wikimedia.org/r/303956]]
+",1470789051,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Off in T124305 there's a patch to make it easier to select the link-contents, which avoids many of the issues a ""display text"" field has (most notably: it's not just text). It's held up on general ""what design do we want?"" concerns.",1460559037,PHID-USER-hdkktg27rkwebepkv6yw,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"It's now approaching two months since this was declined without adequate explanation and reopened pending that explanation. Please can we now have the reasoning (or a pointer to it) that led to the decline - this remains the biggest single hindrance to simple, intuitive use in my experience.",1460556396,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Sorry Jdforrester, I re-opened this task. I don't doubt that a lot of thinking went into this idea - but could you please provide a concise summary of the reasons you don't want to see this implemented? Again, I don't doubt that there are good reasons, I just don't see any and haven't seen a discussion anywhere. Thank you!",1456522432,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Thinking more about it, that you have had to have discussions about it in ""dozens of places"" (none of which are linked so we can verify this) suggests that actually there is a very strong desire for a two-box solution. 
+
+WONTFIXing something that is so strongly desired by the editing community needs justification, particularly why two boxes would ""mak[e] the user experience too heavy"" - the only explanation actually given, and that was a musing two years ago. 
+
+The only current way to be sure that both link target and link title are correct when editing is to delete what is currently there, write the title, select it, and then create a link. I am unable to correlate this with the goal of creating an editing interface that makes editing easy. ",1456418517,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'd like to third this question. 
+In informal discussions of VE this is one of the most frequent issues brought up. Indeed I'm astounded that anyone could be ""happy"" at this decision. ",1456417495,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'd like to second this question. You could at the very least state the reason why you decline this, as from this feature request it's not clear at all why one would not add this little, extremely helpful textbox in the link widget.",1456257863,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'd like to second this question. You could at the very least state the reason why you decline this, as from this feature request it's not clear at all why one would not add this little, extremely helpful textbox in the link menu.",1456257811,PHID-USER-n5zbtah6t77lz2asxkmm,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2052851, @Jdforrester-WMF wrote:
+> With the benefit of four years' discussion in dozens of places, I'm now happy to conclude that this is indeed Declined.
+
+Because of...?",1456226144,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"With the benefit of four years' discussion in dozens of places, I'm now happy to conclude that this is indeed Declined.",1456174729,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,[[ https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis#Am.C3.A9lioration_de_l.27insertion_de_lien | New feedback concerning the separate input fields ]]. I also strongly support this idea.,1444311377,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Changing a wikilink to an external link is not so smart, because text in the External links tab is not automatically selected, and therefore needs to be selected before being replaced by typing or pasting.",1434625821,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"@Whatamidoing-WMF Works with Chromium, but not on Firefox (38.0 canonical 1.0 for Ubuntu).",1434616721,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"@Trizek-WMF:  It's supposed to automagically switch to the External links tab if you type ""http://"" at the start.  Is the automatic detection not working for you?",1434563472,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I've made some edits yesterday evening with VE in order to add an external link. Here is what I did: 
+
+  # select the text
+  # click on the link icon
+  # type my URL in the field
+  # click on ""Done"" button
+  # See a red link
+  # Realize there is a special tab for external links
+  # Start again...
+
+The same happens to me quite all the time. :/",1434530659,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Copy Google Docs solution?
+
+To elaborate, I don't think that labelling this solution as ""ugly"" is a strong rationale to why it shouldn't actually work for us. I'm fairly sure there must be a fair amount of research behind something that Google came up with for millions of people, and editors are constantly confused by our current interface instead.",1437581407,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,Copy Google Docs solution?,1409658400,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,*** Bug 51438 has been marked as a duplicate of this bug. ***,1395196870,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"This is not a WONTFIX, but it comes close in terms of making the user experience too heavy (for detailed reasoning, see endless bugs passim).",1395196770,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Let template's navboxes (VTE links) be used in VE edit move,"<< Currently when you click on a template with the ""VTE"" (view, talk page, edit) links, Visual Editor gives you the option of adding parameters to the transclusion of the template. Most of the templates with the ""VTE"" links are navigational boxes or other transcluded items without parameters, but as the VTE links suggest, we want people to easily view the template page itself. Maybe if someone clicks on a template with VTE links in Visual Editor, rather than being given the regular option to add parameters they should instead be given a dialogue box saying something along the lines of ""This is a template that appears on many pages. Would you like to open this template's page in a new tab?"". —[[User:Arctic.gnome|Arctic Gnome]] <small>([[User talk:Arctic.gnome|talk]] • [[Special:Contributions/Arctic.gnome|contribs]])</small> 13:45, 20 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377012600,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-jtv2xb4ipsbwnbem7fka,task_description,open
+VisualEditor: Let template's navboxes (VTE links) be used in VE edit move,"Bug 49772 - VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation) 
+looks relevant. 
+
+The V.T.E links are a specific of the way things are organised on en.wikipedia See for example the nav box template at the bottom of 
+http://en.wikipedia.org/wiki/When_an_Old_Cricketer_Leaves_the_Crease
+
+I suspect bug 49772 will be a more general solution.",1377021493,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-jtv2xb4ipsbwnbem7fka,task_subcomment,NA
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51527",1375013100,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-zsmkxbjmo6bthiyirco6,task_description,resolved
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"This was re-filed as bug 56205 and fixed in October.
+
+*** This bug has been marked as a duplicate of bug 56205 ***",1385396577,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zsmkxbjmo6bthiyirco6,task_subcomment,NA
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"With the VE being enabled in Help, File & Category pages, this message is now incorrect on en.wp (and others?) too.",1383118394,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-zsmkxbjmo6bthiyirco6,task_subcomment,NA
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"(In reply to comment #1)
+> Do you mean 
+> https://www.mediawiki.org/wiki/Manual:$wgContentNamespaces
+
+Presumably.
+
+> Is VE enabled in other content namespaces?
+
+Only on MediaWiki.org and the test wikis (where the alpha opt-in preference is not shown). Everywhere else, it's just NS0 (articles) and NS2 (user pages).",1375136842,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-zsmkxbjmo6bthiyirco6,task_subcomment,NA
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"Do you mean 
+https://www.mediawiki.org/wiki/Manual:$wgContentNamespaces
+Is VE enabled in other content namespaces?",1375135683,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-zsmkxbjmo6bthiyirco6,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"**Author:** `jonathan_haas`
+
+**Description:**
+It's currently impossible to change table cell background VE
+
+See for example http://de.wikipedia.org/wiki/Suriyakati-Kalender
+
+**See also**
+* Open subtasks of {T49780} ",1375007580,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ppmnn62nd4u24sclez4h,task_description,open
+Be able to set table cell background (and other formatting options),,1634434555,PHID-USER-6q5jenpm75klo2spmch3,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),,1624208185,PHID-USER-6q5jenpm75klo2spmch3,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),This was requested again at https://www.mediawiki.org/wiki/Topic:Vcflv3wnvk90yycr by @Guarapiranga.  I think that this or similar requests appear a couple of times each year.,1576212562,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#2169644, @Whatamidoing-WMF wrote:
+> If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+
+Please re-read my comment, where I accepted highlighting, as in a table, as a valid use case. But I'm also going to point out that the same information can and should be conveyed by a class, so that we can better enforce accessibility, if no other reason.
+
+See also {T37704} and {T89134}.",1459597392,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#2169644, @Whatamidoing-WMF wrote:
+> If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+
+Please re-read my comment, where I accepted highlighting, as in a table, as a valid use case. But I'm also going to point out that the same information can and should be conveyed by a class.
+
+See also {T37704} and {T89134}.",1459597259,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#2169644, @Whatamidoing-WMF wrote:
+> If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+
+Please re-read my comment, where I accepted highlighting, as in a table, as a valid use case. But I'm also going to point out that the same information can and should be conveyed by a class.
+
+See also T37704.",1459596974,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#2169644, @Whatamidoing-WMF wrote:
+> If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+
+Please re-read my comment, where I accepted highlighting, as in a table, as a valid use case. But I'm also going to point out that the same information can and should be conveyed by a class. See also T37704.",1459596951,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+",1459530568,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#969564, @Juandev wrote:
+>>>! In T54180#966351, @Jdforrester-WMF wrote:
+>> There's a strong use case to //not// let this be something people do. The colour in your example adds almost no value but massively distracts from the readability, accessibility and utility of the information being conveyed.
+> 
+> Probably strong case not to use it in Wikipedia, but what about Wikiversity. You may need to highlight cells just to be more atractive for the students or to be able to count someting better. I thing advanced MS Excell of Google Tabs already allow to search by table cell bg color.
+
+This looks like a (really) strong use case for a class to be applied to a row/cell, //not// random style, if in fact ""highlighting"" is being used in multiple places.
+
+I would tend to agree that random color should not be ""doable"" in VE, while permitting the addition of classes may be valuable (especially .wikitable if no others).",1458404950,PHID-USER-yawytiq5q7eduxmvnkid,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#966571, @Krinkle wrote:
+> Note that standardised styles (by the software or by local wikis) for tables can be developed and provided through program code (instead of through article content) by declaring them in CSS stylesheets (such as `MediaWiki:Common.css`).
+> 
+> I'd say it'd be an improvement if VisualEditor has an interface that can apply certain css classes to a table. Especially ones provided by MediaWiki core, such as `wikitable`, `sortable`, and `mw-collapsible`. (Though ideally through an intuitive interface, and not a free-form text field; which requires users to know internal software class names.)
+> 
+> ...
+
+Agreed. One of the most common ""deviations"" made to table element defaults is changing the `vertical-align` of all (or nearly all) of the table cells in a table to render //top// rather than default //middle//.
+
+Most folks assume this requires changing the default `vertical-align` value per every TR or per each TD within a table but the default is actually ''inherit'' for these elements - set by tbody, thead or tfoot which actually has the `vertical-align:middle` setting.
+
+Understanding the tbody element is not 'shown but always present' we can still simplify the table rendering of cell content throughout an entire table by making a simple .css addition to the default stylesheets such as...
+
+``` lang=""css""
+.valign-td-top > tbody {
+	vertical-align: top;
+}
+```
+... in turn, setting `table class=""valign-td-top""` is all the user needs to add (either manually or by design in a VE table option) to accomplish top rendering of content.
+
+Worst case scenario is the user needs to [re]adjust the TH header row's vertical-alignment back to middle - far less work than applying inline styling to each TR or every TD as is the case now.",1454639052,PHID-USER-fflcyhesfpbopooupqa3,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#971085, @Whatamidoing-WMF wrote:
+> I wonder if it could be a feature that is configurable per-wiki, or ideally per-namespace at each wiki.  Then you could get (for example) teaching materials at WIkiversity that use it, but keep it out of the article namespace at the English Wikipedia.  (It would still need to accept copied/pasted tables, and maybe have a 'remove this background color' button—which we need anyway, because of tables copied from other websites.)
+
+So should I understand your statment like we need community consensus for that?",1433206467,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),So the option per wiki is the best choise I guess. Namespaces are not standardized yet on some wv projcects.,1424002582,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"I wonder if it could be a feature that is configurable per-wiki, or ideally per-namespace at each wiki.  Then you could get (for example) teaching materials at WIkiversity that use it, but keep it out of the article namespace at the English Wikipedia.  (It would still need to accept copied/pasted tables, and maybe have a 'remove this background color' button—which we need anyway, because of tables copied from other websites.)",1421081161,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#966351, @Jdforrester-WMF wrote:
+> There's a strong use case to //not// let this be something people do. The colour in your example adds almost no value but massively distracts from the readability, accessibility and utility of the information being conveyed.
+
+Probably strong case not to use it in Wikipedia, but what about Wikiversity. You may need to highlight cells just to be more atractive for the students or to be able to count someting better. I thing advanced MS Excell of Google Tabs already allow to search by table cell bg color.",1421024302,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"> The colour...distracts from the readability, accessibility and utility of the information being conveyed.
+
+Making it possible and even moderately easy to render this image in a table instead of in an image would IMO be a significant improvement in the readability, accessibility and utility of the information.  For example, someone with a screen reader could actually read it, and anyone could edit the contents.
+
+I'm not looking for fruit salad in encyclopedia articles, but when someone wants to create a table like this, I want them to think ""Oooh, I can do that in VisualEditor"", not ""I'll draw this in Adobe Illustrator, export it as a jpeg, upload it to Commons, insert it on a page in mediawiki.org, and every time someone needs to have a simple typo fixed, I'll repeat that process.""
+
+",1420843846,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"> The colour...distracts from the readability, accessibility and utility of
+the information being conveyed.
+
+Making it possible and even moderately easy to render this image in a table
+instead of in an image would IMO be a significant improvement in the
+readability, accessibility and utility of the information.  For example,
+someone with a screen reader could actually read it, and anyone could edit
+the contents.
+
+I'm not looking for fruit salad in encyclopedia articles, but when someone
+wants to create a table like this, I want them to think ""Oooh, I can do
+that in VisualEditor"", not ""I'll draw this in Adobe Illustrator, export it
+as a jpeg, upload it to Commons, insert it on a page in mediawiki.org, and
+every time someone needs to have a simple typo fixed, I'll repeat that
+process.""
+
+
+
+
+
+Whatamidoing (WMF)/Sherry Snyder
+Community Liaison
+Wikimedia Foundation, Inc.",1420843792,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"Note that standardised styles (by the software or by local wikis) for tables can be developed and provided through program code (instead of through article content) by declaring them in CSS stylesheets (such as `MediaWiki:Common.css`).
+
+I'd say it'd be an improvement if VisualEditor has an interface that can apply certain css classes to a table. Especially ones provided by MediaWiki core, such as `wikitable`, `sortable`, and `mw-collapsible`. (Though ideally through an intuitive interface, and not a free-form text field; which requires users to know internal software class names.)
+
+And potentially a few other class-name / label combinations provided by the local wiki. There's definitely a use case for having more than one type of table for all of Wikipedia.",1420833804,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"Note that standardised styles (by the software or by local wikis) for tables can be developed and provided through program code (instead of through article content) by declaring them in CSS stylesheets (such as `MediaWiki:Common.css`).
+
+I'd say it'd be an improvement if VisualEditor has an interface that can apply certain css classes to a table. Especially ones provided by MediaWiki core, such as `wikitable`, `sortable` and `mw-collapsible` (though ideally through an intuitive interface, and not a free-form text field (which requires users to know internal software class names).
+
+And potentially a few other class-name / label combinations provided by the local wiki. There's definitely a use case for having more than one type of table for all of Wikipedia.",1420833751,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"There's a strong use case to //not// let this be something people do. The colour in your example adds almost no value but massively distracts from the readability, accessibility and utility of the information being conveyed.",1420829910,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"In terms of the scope for this item:  I'd like (Howie) to be able to create this table in VisualEditor:  https://www.mediawiki.org/wiki/File:Product_stages_and_players.jpg
+
+I'm not entirely sure how to do it in wikitext, but that's what I want to be able to do.
+",1420829373,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),This issue of table cell paragraph formatting is now Bug 65416.,1400273034,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"(In reply to WhatamIdoing from comment #1)
+> ""Other formatting"" should include support for font size and line height, so
+> that tables like the ones seen at
+> https://en.wikipedia.org/w/index.php?oldid=608813235#Early_years will
+> display with the correct row height.
+
+No, that's a bug caused by VE assuming that table cells' paragraphs should be styled like other paragraphs. That's a fix to styling rules, nothing to do with editing them to have custom styles. Could you file a new bug?",1400270237,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"""Other formatting"" should include support for font size and line height, so that tables like the ones seen at https://en.wikipedia.org/w/index.php?oldid=608813235#Early_years will display with the correct row height.",1400265859,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"Links are frequently placed in edit summaries but the user is currently perversely required to revert to wikicode to insert them.  The VisEd menu should be available for the edit summary and the text should be displayed as it will be seen.  Wysiwyg should apply to all elements of the edit summary (eg, the recently added section title is displayed as code rather than the grey italics as it will be seen).
+
+=== Potential use cases/impacts/hypotheses 
+- **[potential impact]**: if people publishing edits write more expressive edit summaries, these edit summaries will be compelling/interesting to people whose primarily relationship to Wikipedia is as as a reader
+-- //See more in {T379405}
+- **[potential use case]**: enable people to relate edits to the events/campaigns that inspired them to make them (T373232)
+-- //Inspired @AlexHollender-WMF and @ifried...//
+- **[hypothesis]** If people have an easier time doing things like mentioning other people, inserting links, and formatting text within the edit summary input, they will invest more effort into writing edit summaries.
+- **[potential impact]** If people write more descriptive edit summaries, then machine learning models will become more effecting at learning from the actions volunteers are taking because these models will have to make fewer inferences/assumptions about the semantic meaning of a change/changes someone is making. //This thought is inspired by the conversation we (the Editing Team) had with @diego on 27 July 2022.//
+- **[potential impact]** If people write more descriptive edit summaries, then people visiting an article's ""page history""  will have an easier time: A) understanding how the article they are interested in evolved over time and B) identifying changes they are curious to learn more about
+-- this could also open up the potential for edits/diffs being presented as small, standalone pieces of information people could ""consume"" 
+
+=== Related
+- T123529
+- T323875
+- https://hashtags.wmcloud.org/",1374996120,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-imjhsazltcwrba7knjzi,task_description,open
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,">>! In T54174#6178473, @MMiller_WMF wrote:
+> @ppelberg -- thanks for thinking about this.  We have the idea for ""notify your mentor"" as part of the longer term of suggested edits.  [[https://commons.wikimedia.org/wiki/File:Prototype_of_confirmation_desktop_guidance_for_suggested_edits_2020-01-16.png | Here's a mockup ]], and shown below.
+Assuming people are ""feeling good"" after having successfully completed an edit, it seems like a good idea to provide them with an opportunity to ""shop"" for more edits to make so they can keep that flow going.
+
+> But maybe it would make sense to combine that into one step, which would reduce how many ""posts"" happen after an edit is completed, and streamline the workflow for the user.
+This is what I had in mind. Additionally, I wonder if guiding the mentee to notify their mentor by way of edit summaries could have the following effects:
+- Other experienced editors will act more conscientiously towards newcomers, and their edits, if newcomers' intentions are more legible them.
+-- //Here, I'm assuming the interaction the ""Notify mentor"" workflow would facilitate would be less visible to experienced contributors than if the communication happened through edit summaries.//
+- Mentors will appreciate newcomers interacting with them via the tools/workflows they're used to
+- Newcomers will learn a skill that is likely to benefit outside the context of Newcomer tasks.
+
+I also wonder whether it's more consistent with how other, more experienced editors behave, to introduce this piece of communication (read: Edit summaries) as being //a part of the edit process// as opposed to something that happens after the fact. //This is a thought I'd like to develop more.// 
+
+>It sounds like you're saying that it would be better if they could use the `@` symbol and autocomplete with usernames.  Perhaps that would be useful beyond just newcomers.
+Exactly (to both points).
+
+> But all this said, I think that if we're going to encourage newcomers to ping their mentors in the edit summary (or elsewhere), we wouldn't have them type out their mentor's name, even with autocomplete.  The system would know their mentors name and take care of that part for them.  Although, the argument I see for having the newcomer type their mentor's name is that they would learn how to ping in edit summaries.  What do you think?
+I think it would be fine to automatically insert the mentor's handle into the newcomers' edit summary //so long as// newcomers can see the ping and have it appears as such: [@Marshall](https://meta.wikimedia.org/wiki/User:MMiller_(WMF)).
+
+Reason:
+- I think newcomers will intuitively understand/recognize the presence of  [@USERNAME](https://meta.wikimedia.org/wiki/User:MMiller_(WMF)) to mean: [i]
+-- A) @USERNAME is going to get a notification
+-- B) To notify someone next time, I bet I can just type {key @} and the rest will work like it does on other platforms. 
+
+
+---
+i. The above is informed, in part, by the latest round of user tests we ran where we found most test participants intuitively understood typing {key @} to tag/ping/mention someone else. //See ""@-mentioning a user not in the conversation"" in T246190#6186156 //",1591841391,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,">>! In T54174#6178473, @MMiller_WMF wrote:
+> @ppelberg -- thanks for thinking about this.  We have the idea for ""notify your mentor"" as part of the longer term of suggested edits.  [[https://commons.wikimedia.org/wiki/File:Prototype_of_confirmation_desktop_guidance_for_suggested_edits_2020-01-16.png | Here's a mockup ]], and shown below.
+Assuming people are ""feeling good"" after having successfully completed an edit, it seems like a good idea to provide them with an opportunity to ""shop"" for more edits to make so they can keep that flow going.
+
+> But maybe it would make sense to combine that into one step, which would reduce how many ""posts"" happen after an edit is completed, and streamline the workflow for the user.
+This is what I had in mind. Additionally, I wonder if guiding the mentee to notify their mentor by way of edit summaries could have the following effects:
+- Other experienced editors will act more conscientiously towards newcomers, and their edits, if newcomers' intentions are more legible them.
+-- //Here, I'm assuming the interaction the ""Notify mentor"" workflow would facilitate would be less visible to experienced contributors than if the communication happened through edit summaries.//
+- Mentors will appreciate newcomers interacting with them via the tools/workflows they're used to
+- Newcomers will learn a skill that is likely to benefit outside the context of Newcomer tasks.
+
+I also wonder whether it's more consistent with how other, more experienced editors behave, to introduce this piece of communication (read: Edit summaries) as being //a part of the edit process// as opposed to something that happens after the fact. //This is a thought I'd like to develop more.// 
+
+>It sounds like you're saying that it would be better if they could use the `@` symbol and autocomplete with usernames.  Perhaps that would be useful beyond just newcomers.
+Exactly (to both points).
+
+> But all this said, I think that if we're going to encourage newcomers to ping their mentors in the edit summary (or elsewhere), we wouldn't have them type out their mentor's name, even with autocomplete.  The system would know their mentors name and take care of that part for them.  Although, the argument I see for having the newcomer type their mentor's name is that they would learn how to ping in edit summaries.  What do you think?
+I think it would be fine to automatically insert the mentor's handle into the newcomers' edit summary //so long as// newcomers can see the ping and have it appears as such: [@Marshall](https://meta.wikimedia.org/wiki/User:MMiller_(WMF)).
+
+Reasons:
+- I think newcomers will intuitively understand/recognize the presence of  [@USERNAME](https://meta.wikimedia.org/wiki/User:MMiller_(WMF)) to mean: [i]
+-- A) @USERNAME is going to get a notification
+-- B) To notify someone next time, I bet I can just type {key @} and the rest will work like it does on other platforms. 
+
+
+---
+i. The above is informed, in part, by the latest round of user tests we ran where we found most test participants intuitively understood typing {key @} to tag/ping/mention someone else. //See ""@-mentioning a user not in the conversation"" in T246190#6186156 //",1591841123,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@ppelberg -- thanks for thinking about this.  We have the idea for ""notify your mentor"" as part of the longer term of suggested edits.  [[ https://commons.wikimedia.org/wiki/File:Prototype_of_confirmation_desktop_guidance_for_suggested_edits_2020-01-16.png | Here's a mockup ]], and shown below.
+
+{F31847417}
+
+Our thinking here was that the user would not be pinging the mentor in an actual edit summary, but rather writing them a separate notification via a dedicated workflow that would automatically ping the mentor, after having already posted a normal edit summary.
+
+But maybe it would make sense to combine that into one step, which would reduce how many ""posts"" happen after an edit is completed, and streamline the workflow for the user.
+
+It is currently possible to ping users in edit summaries, but only by using the traditional user page link syntax, e.g. `[[User:Cloud atlas]]`.  It sounds like you're saying that it would be better if they could use the `@` symbol and autocomplete with usernames.  Perhaps that would be useful beyond just newcomers.
+
+But all this said, I think that if we're going to ecourage newcomers to ping their mentors in the edit summary (or elsewhere), we wouldn't have them type out their mentor's name, even with autocomplete.  The system would know their mentors name and take care of that part for them.  Although, the argument I see for having the newcomer type their mentor's name is that they would learn how to ping in edit summaries.  What do you think?
+
+FYI @RHo ",1590799405,PHID-USER-krko4robkho2pjor6klf,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@ppelberg -- thanks for thinking about this.  We have the idea for ""notify your mentor"" as part of the longer term of suggested edits.  [[ https://commons.wikimedia.org/wiki/File:Prototype_of_confirmation_desktop_guidance_for_suggested_edits_2020-01-16.png | Here's a mockup ]].  Our thinking here was that the user would not be pinging the mentor in an actual edit summary, but rather writing them a separate notification via a dedicated workflow that would automatically ping the mentor, after having already posted a normal edit summary.
+
+But maybe it would make sense to combine that into one step, which would reduce how many ""posts"" happen after an edit is completed, and streamline the workflow for the user.
+
+It is currently possible to ping users in edit summaries, but only by using the traditional user page link syntax, e.g. `[[User:Cloud atlas]]`.  It sounds like you're saying that it would be better if they could use the `@` symbol and autocomplete with usernames.  Perhaps that would be useful beyond just newcomers.
+
+But all this said, I think that if we're going to ecourage newcomers to ping their mentors in the edit summary (or elsewhere), we wouldn't have them type out their mentor's name, even with autocomplete.  The system would know their mentors name and take care of that part for them.  Although, the argument I see for having the newcomer type their mentor's name is that they would learn how to ping in edit summaries.  What do you think?
+
+FYI @RHo ",1590799352,PHID-USER-krko4robkho2pjor6klf,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@Esanders would resolving this task enable us to extend T232601 to edit summaries? 
+
+I'm not suggesting we prioritize this, but the use case below occurred to me today and thought I'd ask.
+
+---
+=== Context
+**Use case: newcomer seeking review from mentor**
+1. Newcomer receives guidance from an experienced editor, be it via the Growth team's mentorship module or some other means [i]
+2. Newcomer makes an edit per mentor's instructions
+3. Newcomer wants to get the attention of their mentor, to ensure they made their edit correctly //before// someone comes along and reverts said edit
+4. Newcomer types their edit summary and @-mentions their mentor in said summary
+
+**😀 Benefits**
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Newcomer avoids their edit being reverted by someone else 
+- Mentor and newcomer now have a more contextual way of communicating about the process of editing through the edits themselves.
+
+**😬 Risks**
+- Easier to notify people = more noise
+- People writing edit summaries could begin to tailor their summaries to individuals rather than ""other editors as a whole"" leading them to become more difficult to understand.
+
+---
+
+i. https://nl.wikipedia.org/wiki/Overleg_gebruiker:Jessevermeulen18
+
+---
+@MMiller_WMF cc'ing you for your awareness.",1590711675,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@Esanders would resolving this task enable us to extend T232601 to edit summaries? 
+
+I'm not suggesting we prioritize this, but the use case below occurred to me today and thought I'd ask.
+
+---
+=== Context
+**Use case: newcomer seeking review from mentor**
+1. Newcomer receives guidance from an experienced editor, be it via the Growth team's mentorship module or some other means [i]
+2. Newcomer makes an edit per mentor's instructions
+3. Newcomer wants to get the attention of their mentor, to ensure they made their edit correctly //before// someone comes along and reverts said edit
+4. Newcomer types their edit summary and @-mentions their mentor in said summary
+
+**😀 Benefits**
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Newcomer avoids their edit being reverted by someone else 
+- Mentor and newcomer now have a more contextual way of communicating about the process of editing through the edits themselves.
+
+**😬 Risks**
+- Easier to notify people = more noise
+- People writing edit summaries could begin to tailor their summaries to individuals rather than ""edits as a whole"" leading them to become more difficult to understand.
+
+---
+
+i. https://nl.wikipedia.org/wiki/Overleg_gebruiker:Jessevermeulen18
+
+---
+@MMiller_WMF cc'ing you for your awareness.",1590708629,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@Esanders would resolving this task enable us to extend T232601 to edit summaries? 
+
+I'm not suggesting we prioritize this, but the use case below occurred to me today and thought I'd ask.
+
+---
+=== Context
+**Use case: newcomer seeking review from mentor**
+1. Newcomer receives guidance from an experienced editor, be it via the Growth team's mentorship module or some other means [i]
+2. Newcomer makes an edit per mentor's instructions
+3. Newcomer wants to get the attention of their mentor, to ensure they made their edit correctly //before// someone comes along and reverts said edit
+4. Newcomer types their edit summary and @-mentions their mentor in said summary
+
+**😀 Benefits**
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Newcomer avoids their edit being reverted by someone else 
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Mentor and newcomer now have a more contextual way of communicating about the process of editing through the edits themselves.
+
+**😬 Risks**
+- Easier to notify people = more noise
+- People writing edit summaries could begin to tailor their summaries to individuals rather than ""edits as a whole"" leading them to become more difficult to understand.
+
+---
+
+i. https://nl.wikipedia.org/wiki/Overleg_gebruiker:Jessevermeulen18
+
+---
+@MMiller_WMF cc'ing you for your awareness.",1590708577,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@Esanders would resolving this task enable us to extend T232601 to edit summaries? 
+
+I'm not suggesting we prioritize this, but the use case below occurred to me today and thought I'd ask.
+
+---
+=== Context
+**Use case: newcomer seeking review from mentor**
+1. Newcomer receives guidance from an experienced editor, be it via the Growth team's mentorship module or some other means [i]
+2. Newcomer makes an edit per mentor's instructions
+3. Newcomer wants to get the attention of their mentor, to ensure they made their edit correctly //before// someone comes along and reverts said edit
+4. Newcomer types their edit summary and @-mentions their mentor in said summary
+
+**😀 Benefits**
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Newcomer avoids their edit being reverted by someone else 
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Mentor and newcomer now have a more contextual way of communicating about the process of editing through the edits themselves.
+
+---
+
+i. https://nl.wikipedia.org/wiki/Overleg_gebruiker:Jessevermeulen18
+
+---
+@MMiller_WMF cc'ing you for your awareness.",1590708453,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,Re-purposing this to flesh out bug 42139 comment 1.,1390417719,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,Dupe of bug 42139 (specifically bug 42139 comment 1)?,1374996450,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"There are many pages for which VisualEditor is broken.  In some cases, the page syntax can be changed to avoid the problem.  In other cases (such as nlwp's largethumb, dewp dab pages, enwp episode lists), the design affects many pages, and the only feasible solution is to fix the parser.  While we wait for fixes, the VE should be disabled on those pages known to be affected.
+
+The set of pages to be VE-disabled could be a category, if you trust the villagers..:-)
+Or a page title blacklist in MediaWiki: namespace so it is admin only
+Or a page content regex blacklist in MediaWiki: namespace so it is easier to blacklist all pages which include a certain element.
+
+**See Also**: {T55767} (also declined)",1374931800,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_description,declined
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),">>! In T54141#1568572, @Neil_P._Quinn_WMF wrote:
+> @Kipod, whether it's easy or hard it not really the main issue. The main issue is whether the benefits outweigh the downsides—and unfortunately there //are// downsides. These magic words would increase complexity, sometimes stay on pages long after the need is gone, and risk confusing users when no visual editor tab appears on a page where they expect to see it.
+> 
+> Today, the visual editor corrupts pages //far// less often than it did when this bug was filed two years ago, which makes me think that the benefits of these magic words would be small. Are there other reasons for having them?
+
+Has Paroid been round-trip tested against Wikisource pages in the main & Page: namespace?
+I am guessing there will be a new batch of page corruptions on Wikisource when it is deployed for the Page: namespace, if there has not been specific testing for the Page: namespace. Wikisource has some very odd hacks. Many thanks if this testing has already been done and there are no serious problems when it is deployed.
+
+An alternative would be for wikisource to add an editnotice, which is only shown for VE editors, for pages which have problems with VE. Then it can be more advisory:
+
+""this page may have problems with VE; please check the diff after saving changes. Report bugs at <x> ; if there are no bugs, remove this editnotice by <do y>.""",1461565625,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),">>! In T54141#1568572, @Neil_P._Quinn_WMF wrote:
+> Today, the visual editor corrupts pages //far// less often than it did when this bug was filed two years ago, which makes me think that the benefits of these magic words would be small. Are there other reasons for having them?
+
+The primary benefit I see is that I'd like to enable VE on pages where it will not be enabled globally. ",1461516395,PHID-USER-fgzcdbj3je3ksnhufo47,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"@Kipod, whether it's easy or hard it not really the main issue. The main issue is whether the benefits outweigh the downsides—and unfortunately there //are// downsides. These magic words would increase complexity, sometimes stay on pages long after the need is gone, and risk confusing users when no visual editor tab appears on a page where they expect to see it.
+
+Today, the visual editor corrupts pages //far// less often than it did when this bug was filed two years ago, which makes me think that the benefits of these magic words would be small. Are there other reasons for having them?
+
+>this should override the namespace default, but _not_ the user personal choice (i.e., if the user elects to disable VE. 
+That only works for people who turn off the visual editor completely. If you disable the visual editor on a given page, I can no longer choose to use it. 
+
+Peace to you as well :)",1440440676,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"i see this is ""closed, declined"".
+since another ticket, opened by me, was ""closed, duplicate"" pointing here, i would like to request to reconsider.
+implementing my request should be very easy, controllable, requres no changes outside VE, and very simple change inside VE, and, oh, by the way, will also close/solve this one. so i paraphrase my previous request here:
+
+
+there are good reasons (i guess) not to enable VE on some namespaces, and specifically ""project"" namespace, but it would be desirable to be able to override it for specific pages.
+ 
+i was thinking something like adding two new magic words:
+
+
+```
+__ENABLE_VISUAL_EDITOR__
+__DISABLE_VISUAL_EDITOR__
+```
+this should override the namespace default, but _not_ the user personal choice (i.e., if the user elects to disable VE.
+
+implementing these two switches is 100% risk-free (currently there are no pages that use these magic words), and should be easy enough to implement, such that the switch that decides wheter or not to enable VE will test for these magic words, and make the correct decisiosn.
+
+so, implementing it would be risk-free, easy, and will soleve at least two legitimate requests that came from the community (with some 19 members subscribing to this ticket).
+
+maybe you should consider reopening. unfortunately i can't offer a patch to prove my claim that it's  ""easy""...
+
+
+peace.",1440372132,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"i see this is ""closed, declined"".
+since another ticket, opened by me, was ""closed, duplicate"" pointing here, i would like to request to reconsider.
+implementing my request should be very easy, controllable, requres no changes outside VE, and very simple change inside VE, and, oh, by the way, will also close/solve this one. so i paraphrase my previous request here:
+
+
+there are good reasons (i guess) not to enable VE on some namespaces, and specifically ""project"" namespace, but it would be desirable to be able to override it for specific pages.
+ 
+i was thinking something like
+
+
+```
+__ENABLE_VISUAL_EDITOR__
+__DISABLE_VISUAL_EDITOR__
+```
+this should override the namespace default, but _not_ the user personal choice (i.e., if the user elects to disable VE.
+
+implementing these two switches is 100% risk-free (currently there are no pages that use these magic words), and should be easy enough to implement, such that the switch that decides wheter or not to enable VE will test for these magic words, and make the correct decisiosn.
+
+so, implementing it would be risk-free, easy, and will soleve at least two legitimate requests that came from the community (with some 19 members subscribing to this ticket).
+
+maybe you should consider reopening. unfortunately i can't offer a patch to prove my claim that it's  ""easy""...
+
+
+peace.",1440372042,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"i see this is ""closed, declined"".
+since another ticket, opened by me, was ""closed, duplicate"" pointing here, i would like to request to reconsider.
+implementing my request should be very easy, controllable, requres no changes outside VE, and very simple change inside VE, and, oh, by the way, will also close/solve this one. so i paraphrase my previous request here:
+
+
+there are good reasons (i guess) not to enable VE on some namespaces, and specifically ""project"" namespace, but it would be desirable to be able to override it for specific pages.
+ 
+i was thinking something like
+
+__ENABLE_VISUAL_EDITOR__
+__DISABLE_VISUAL_EDITOR__
+this should override the namespace default, but _not_ the user personal choice (i.e., if the user elects to disable VE.
+
+implementing these two switches is 100% risk-free (currently there are no pages that use these magic words), and should be easy enough to implement, such that the switch that decides wheter or not to enable VE will test for these magic words, and make the correct decisiosn.
+
+so, implementing it would be risk-free, easy, and will soleve at least two legitimate requests that came from the community (with some 19 members subscribing to this ticket).
+
+maybe you should consider reopening. unfortunately i can't offer a patch to prove my claim that it's  ""easy""...
+
+
+peace.",1440351968,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"Hello, @Jdforrester-WMF. You merged T107426 here, but it is not the same problem. The main part over there was an ability to ENABLE the VisualEditor on a page in VE-disabled namespace. Thank you.
+",1438769968,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),Agreed.,1437697879,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),">>! In T54141#1312318, @ssastry wrote:
+> Yes, the largethumb template issue has been fixed since early 2014.
+> 
+> The only large-scale corruptions that have been reported have been due to transient bugs on deploys (which tend to be fixed quickly or deploys reverted). There are some pages on which Parsoid could potentially cause corruptions, but those one-off bugs tend to get fixed promptly. There are no large sets of pages that I am aware of that aren't handled properly on the Parsoid end. So, as far as I know, from the Parsoid perspective, this workaround shouldn't be needed.
+
+@Jdforrester-WMF, what do you think about declining this bug?
+
+",1437697817,PHID-USER-vixhpqcaqfpdj6impfwy,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"Yes, the largethumb template issue has been fixed since early 2014.
+
+The only large-scale corruptions that have been reported have been due to transient bugs on deploys (which tend to be fixed quickly or deploys reverted). There are some pages on which Parsoid could potentially cause corruptions, but those one-off bugs tend to get fixed promptly. There are no large sets of pages that I am aware of that aren't handled properly on the Parsoid end. So, as far as I know, from the Parsoid perspective, this workaround shouldn't be needed.",1432641854,PHID-USER-slccyo5rqasgpljxny7g,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"I'm pretty certain that the largethumb template issue has been fixed, and based on the lack of activity and concrete reports of ongoing large-scale corruptions it seems possible that the work-around described in this task might no longer be needed. @ssastry and @jdforrester-wmf: Could you chime in?",1432629212,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"This is an old task, so it would be good to get some specificity around whether this is still an issue and under which circumstances. Can someone please re-validate this issue?",1432563831,PHID-USER-v7pv6vw32wp56vc4wyt7,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"An interesting solution is to add a wikitext magic word `__NOVISUALEDITOR__` to disable it in contexts it might otherwise be enabled.
+
+https://www.mediawiki.org/wiki/Thread:Extension_talk:VisualEditor/Behavior_switch_NOVISUALEDITOR",1432543493,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"An interesting solution is to add a wikitext magic word __NOVISUALEDITOR__ to disable it in contexts it might otherwise be enabled.
+
+https://www.mediawiki.org/wiki/Thread:Extension_talk:VisualEditor/Behavior_switch_NOVISUALEDITOR",1392433326,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"(In reply to comment #6)
+> Obviously VE/Parsoid shouldn't cause breakage - the goal would be to keep
+> membership of that category close to zero at any given time. But if and when
+> things do break, it'd be good to have an official mechanism to deal with it,
+> rather than just template hacks.
+
+Bugzilla is the official mechanism for dealing with breakages.
+
+While it's easy to say that the goal would be to keep the category membership near zero, it sounds like (from reading comment 0) that this category would quickly include tens of thousands of pages.",1375488872,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"Obviously VE/Parsoid shouldn't cause breakage - the goal would be to keep membership of that category close to zero at any given time. But if and when things do break, it'd be good to have an official mechanism to deal with it, rather than just template hacks.",1375488524,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),I don't like the idea presented in bug 52489 (a blacklist category). VisualEditor simply shouldn't break pages ever. Users shouldn't be required to shield articles from it; that's a bit insane.,1375488293,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"It would indeed be helpful to be able to selectively disable VisualEditor (we should indicate to a user who'd otherwise see VisualEditor that it is disabled, to reduce confusion).
+
+A hidden blacklist category could be included in a page or template to achieve
+the desired effect, and could be used by developers to prioritize roundtripping
+issues.",1375488230,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),*** Bug 52489 has been marked as a duplicate of this bug. ***,1375488138,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"If WMF has spare compute power, Parsoid could flag which pages it _may_ break, and tell the VE extension to not enable itself on those pages.",1375047287,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"A temporary solution is being developed: {{Disable VE top}} and {{Disable VE bottom}}
+
+https://en.wikipedia.org/wiki/Template:Disable_VE_top",1374991704,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"The Visual Mode editor of Wikia is able to check all the available parameters automatically without the need for editors to edit the TemplateData for each template manually which is unrealistic to be done for over 505k templates on English Wikipedia.
+However, Wikia's template editor has a severe flaw that it cannot handle a template to be included inside another template. The visual editor will deem the coding to be too complex and forcibly switch back to source mode editor.
+
+--------------------------
+**See Also**:
+T54581 / {T191756}",1374901500,PHID-USER-xnvlg7y5phtzugavv6wj,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_description,open
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,">>! In T54135#2501906, @Whatamidoing-WMF wrote:
+> The GUI for TemplateData can detect (or attempt to detect) parameters now.  I wonder whether that could be 'borrowed' by the template tool?
+
+It's not perfect, and in the GUI there is manual review involved before publication. However, from a user perspective, the only side-effect of the detection is suggestion of parameter names. Not anything beyond that. That's fairly harmless.
+
+If we're ready to try and make this kind of detection available to users without review, then I propose to do this in the TemplateData API instead of in VisualEditor.
+
+That way it will benefit all users of the data, not just VE. And it will keep the logic in the same repository. When VisualEditor fetches it from the API will automatically respond with either the authored data, or fallback to auto-detection for parameter keys.",1469726549,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,">>! In T54135#2501906, @Whatamidoing-WMF wrote:
+> The GUI for TemplateData can detect (or attempt to detect) parameters now.  I wonder whether that could be 'borrowed' by the template tool?
+
+It's not perfect, and in the GUI there is manual review involved before publication. However, from a user perspective, the only side-effect of the detection is suggestion of parameter names. Not anything beyond that. That's fairly harmless.
+
+If we're ready to try and make this kind of detection available to users without review, then I propose to do this in the TemplateData API instead of in VisualEditor.
+
+That way it will benefit all users of the data, not just VE. And it will keep the logic in the same repository. When VisualEditor fetches it from the API which will automatically respond with either the authored data, or fallback to auto-detection for parameter keys.",1469726512,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,The GUI for TemplateData can detect (or attempt to detect) parameters now.  I wonder whether that could be 'borrowed' by the template tool?,1469716429,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,*** Bug 70228 has been marked as a duplicate of this bug. ***,1409694736,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"(In reply to comment #2)
+> This is something we're unlikely to get to do soon, as it would require a
+> vast
+> amount of work (and, indeed, Strong AI to do properly). However, it would be
+> a
+> great improvement, yes.
+
+Indeed. It would help the newbies - not to push them to look for template page and/or template documentation and fill it slow, piece by piece. It is than much faster to add it copy&paste in wiki code, than use VE.",1388572741,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"(In reply to comment #6)
+> (In reply to comment #5)
+> > Kipod do you have a direct link to templatewizard as I've like to link to it?
+> 
+> See bug 52581 comment 4
+
+Or even
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_103#Template_Parameter_Wizard
+mentioned on bug 39598 comment 1.",1383413531,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"(In reply to comment #5)
+> Kipod do you have a direct link to templatewizard as I've like to link to it?
+
+See bug 52581 comment 4
+
+The transclusion UI currently requires thousands of hours to implement on each and every wiki.  This is an enormous design problem that especially impacts small wikis without thousands of minions who have nothing better to do but create templatedata, so I've added this as a blocker for non-English Wikipedia (bug 51792).",1381022591,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"It is dead easy all you need to do is scan for {{{1}}}, {{{name}}}, {{{1| {{{name| etc. I've implemented this at
+http://en.wikipedia.org/wiki/User:Salix_alba/TDSkell
+and there are a few other implementations about. 
+
+Kipod do you have a direct link to templatewizard as I've like to link to it?
+
+There are 300,000 templates on the English wikipedia so many will never have their TemplateData written making this an important enhancement. 
+
+A slightly enhanced version of this request was asked at 
+
+http://en.wikipedia.org/w/index.php?title=Wikipedia_talk%3AVisualEditor&diff=574762591&oldid=573484823
+
+in addition to just getting the names it wanted to find the ""mandatory"" parameters, a much harder job.",1380869650,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,Kipod's Template Parameter Wizard is exactly the thing I'm looking for. At least it works in Wikitext mode nicely.,1375976785,PHID-USER-xnvlg7y5phtzugavv6wj,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"templatewizard on hewiki implements this logic using 9 lines on JS, (so PHP  should probably be able to accomplish that with no more than 50 lines). might not be perfect, but it works for a long time now, and i did not get any bug report yet.
+
+peace.",1375943106,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"This is something we're unlikely to get to do soon, as it would require a vast amount of work (and, indeed, Strong AI to do properly). However, it would be a great improvement, yes.",1375937039,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"i added a ""see also"" to bug 52581.
+
+the idea is not to change anything with VE itself, but rather to teach teh TemplateData extension to return a ""cookie cutter"" templatedata through the API if it does not find ""templatedata"" tag on the template page.
+
+this way, all existing functionality, with all the neat thing one can do with templatedata will still work, and still, VE will be usable for template editing even without it.
+
+also, i think that programmatically, the right place to handle the issue is in the templatedata extension and not in VE itself (in addition to being cleaner and shorter code, there might be other scripts and tools that want to use the templatedata API. even if these were not a consideration, the templatedata extension is the right place to deal with templatedata shortcomings).
+
+
+peace.",1375882556,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Allow preference to move toolbar to over navigation sidebar,"The editor an en.wp who signs as ""Josh, linguist"" has left the following suggestion about toolbar placement in the Visual Editor:
+
+""I've encountered a sort of inconvenience which is the following: while editing, the toolbar occupies a significant area in the upper third visually and otherwise blocking the text, when we, at the same time, usually have an unoccupied area to the left (where the navigation column is which is often empty much below the existing items); the question is why not to devise a possibility, an option to change its place — I mean the toolbar could be opted to place it either where it's offered to be now – or, otherwise, on the left side of the pane – where it should not be blocking an essential area of the text to edit, in this case the text available without scrolling will be by, approximately (depending on your zoom), a half more than it is now.""
+
+For RTL wikis read ""right"" instead of ""left"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374662220,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-ks4nmmzc4p4mogffuzxg,task_description,open
+VisualEditor: Allow preference to move toolbar to over navigation sidebar,"In that case, though, we'd only really have room for six toolbar options and then ""…"", which I'm not sure is much better. :-(",1425591680,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ks4nmmzc4p4mogffuzxg,task_subcomment,NA
+VisualEditor: Allow preference to move toolbar to over navigation sidebar,"Hmm, interesting idea. Lack of vertical space is especially a problem when using an on-screen keyboard, like on a tablet.
+
+{F56237}",1425591542,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ks4nmmzc4p4mogffuzxg,task_subcomment,NA
+VisualEditor: Allow preference to move toolbar to over navigation sidebar,"This is an interesting idea, and one worth exploring; right now, the team are focussed on squashing bugs, performance fixes, and core usability experience improvements, so I'm marking this as ""Lowest"" priority for now to avoid cookie-licking.",1379657567,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ks4nmmzc4p4mogffuzxg,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","one thing that makes life better with existing editor is the fact that when editing a specific section, the section name is automatically added to the edit summary. often, this ends up being the entire edit summary.
+
+REQUESTED ACTION
+1) when hitting ""save"", test to see if all the diffs are contained in a single section, and if so, add the section name to the edit summary automatically.
+2) just like with existing editor, allow the user to modify or remove this part. i.e., the request is to pre-populate the summary box, not to add section name outside of summary box such that the user can't touch it.
+
+peace.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**: T54859, T50274, T52872, T60488",1374605160,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_description,open
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary",">>! In T53903#959238, @matmarex wrote:
+>> The scope of the bug is bigger than that?
+>  
+> Yes:
+>  
+> - When the user edits text in other sections too, this hint shouldn't appear.
+> - When the user opens VE using the ""Edit"" tab at the top and only edits one section, the appropriate hint should appear.
+
+what he said.
+with VE, the ""edit"" links to the right (or left, in rtl wikis) of the section title are misleading: unlike wikieditor, where clicking one of those will limit the changes to this section, with VE there no such limitation. 
+
+IMO, the current VE behavior is wrong and misleading (T60488 agrees with this view). when looking at page history, i don't care which thingy the editor clicked to start the editor - i want to know which changes this edit contains.
+if you do not _know_ that the changes are limited to some section, please don't tell me they are. (and, on the other hand, if you _do_ know such a thing, it would be nice if you told me).
+
+peace.",1420824665,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","> The scope of the bug is bigger than that?
+ 
+Yes:
+ 
+- When the user edits text in other sections too, this hint shouldn't appear.
+- When the user opens VE using the ""Edit"" tab at the top and only edits one section, the appropriate hint should appear.",1420635773,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","Curret behavior in production:
+
+- click on Edit on a section on a page
+- make changes to that section - click Save
+- Save dialog box - 'Edit summary' box will pre-populated with the title of a section that was edited: 
+/* Section 3 */ 
+- 'Review your changes' will have an additional pointer to the section that was edited:
+Preview of edit summary:
+(→‎Section 3: )
+
+The scope of the bug is bigger than that?
+",1419970531,PHID-USER-4alekd35in5tg53zpsl4,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","(In reply to Elitre from comment #8)
+> Isn't this the current behavior (for various meanings of ""section editing"")?
+
+No. This is asking for VE-MW to insert the name of the section edited if only one section was edited, even if the editor was launched from a page-level link. Doing it when the user clicks a section edit link was bug 50872 and is indeed done. Not doing it when the user clicks a section edit link and then edits outside the link is bug 58488.",1412985721,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","Isn't this the current behavior (for various meanings of ""section editing"")?",1412929540,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary",*** Bug 56891 has been marked as a duplicate of this bug. ***,1384842568,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary",(Thanks Matthew!),1376512668,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","(In reply to comment #4)
+> A user at it.wp wonders: if VE could pre-populate the summary box, could it
+> also auto-add the text that was added, in case of very short additions? i.e.,
+> if someone added a parameter to a template, could it automatically detect
+> what was added and write it in the edit summary? Thanks.
+
+Yes, in theory, but in my opinion, that's a separate bug.  Filed as bug 52859.",1376506478,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","A user at it.wp wonders: if VE could pre-populate the summary box, could it also auto-add the text that was added, in case of very short additions? i.e., if someone added a parameter to a template, could it automatically detect what was added and write it in the edit summary? Thanks.",1376403025,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","You're right, this isn't a duplicate; I'm re-opening and titling it to be clearer.",1375199919,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","**ignatzmice.wiki** wrote:
+
+I agree with kipod's comments at bug 50872, this bug is not a duplicate if that one. This would be a very useful feature (if rather resource-intensive).",1375138221,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","
+
+*** This bug has been marked as a duplicate of bug 50872 ***",1374605494,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,"The basic idea is to have a clear and pleasant-to-use web-based interface for generating a MediaWiki instance manifest. The interface should allow you to tick off the extensions you want, for example, and it would automate the configuration of supporting software like Apache and memcached. There's an attractive example of such an interface at <https://puphpet.com/>.
+
+MediaWiki-Vagrant already implements the bulk of the work in that it provides a set of parametrized, MediaWiki-oriented Puppet modules and resource types. In plain English: MediaWiki-Vagrant can take a configuration file that says ""give me a MediaWiki instance with Scribunto and VisualEditor that is set up for development work"" and configure a machine to match these specifications.
+
+A number of cloud computing platforms provide hooks for uploading Puppet code to automate the creation and customization of servers. Some are event implemented as Vagrant 'providers', which means that you can run 'vagrant up' and Vagrant will create a cloud instance rather than a VirtualBox VM. Examples include vagrant-rackspace for Rackspace Cloud (<https://github.com/mitchellh/vagrant-rackspace>) and vagrant-aws (<https://github.com/mitchellh/vagrant-aws>) for Amazon AWS. A vagrant-openstack provider (<https://github.com/aodn/vagrant-openstack>) also exists; I don't know how much work it would take to make it work with Labs.
+
+The major work-item would be to build the web interface (or adapting the source code of <https://puphpet.com/> or some other project -- there are several), ideally as a MediaWiki extension so that we can offer the ability to provision a virtual server (either local or cloud-based) right on MediaWiki.org.
+
+I think that this could considerably broaden the appeal of MediaWiki to a new generation of internet users. The success of Wikia shows that there exists considerable demand for point-and-click wiki creation. It could also help drive third-party usage of VisualEditor / parsoid, if it is true that adoption is held back by anxiety over having to configure and maintain an additional software component.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374439020,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_description,open
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,Bulk unassigning bugs from Ori.,1416260155,PHID-USER-ll6tmaogat2b5q7tnqas,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_subcomment,NA
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.],1378939555,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_subcomment,NA
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,"See also https://www.heroku.com/
+
+Juan,  I'll like what you're doing.  Emailing you.",1375133344,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_subcomment,NA
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,"**jtreminio** wrote:
+
+Hi there, creator of PuPHPet here.
+
+We're actually actively working on providing ready-made quick-start configurations for some popular projects.
+
+Right now we have it done for Symfony2 (https://puphpet.com/quickstart/symfony) and for PuPHPet itself (https://puphpet.com/quickstart/puphpet).
+
+If I could be given your exact requirements I could easily whip something up for you :)",1374452121,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"The ""clear formatting"" button returns bold and italic text to its plain state, as expected. However it also removes any links in the selection, which is not expected, rather there should be a separate ""unlink"" button to do this job - conceptually I regard a link as an attribute not as formatting.
+
+For example selecting a bolded sentence with an italicised title and a linked word in it. I clicked the clear formatting intending to clear the bold and italic, which it did but it also removed the link. Similarly if using it to remove a link it also removes bold/italic which is unlikely to be the intention.",1374344100,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3geuv3zh7grvfypwtx6m,task_description,declined
+VisualEditor: Clear formatting button should not remove links,*** Bug 70739 has been marked as a duplicate of this bug. ***,1410482044,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,*** Bug 59191 has been marked as a duplicate of this bug. ***,1390025103,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"(In reply to comment #4)
+> (In reply to comment #3)
+> > Also, removing a link takes three clicks if you don't use 'clear
+> > formatting'.
+>
+> Which is why I said there should be a separate button to remove
+> links with a single click.
+
+We're meant to be in the business of removing user confusion, not
+adding to it. More buttons make things harder to understand, in
+general. In this specific case I'm not sure.
+
+> > 'Clear markup' would be more descriptive, but probably less user-
+> > friendly.
+>
+> ""Clear markup"" doesn't describe what it does either, because it
+> doesn't remove paragraph style, text size, templates, colour, etc.
+> It only removes text formatting and links.
+
+Actually, this is wrong. Specifically, ""clear formatting"" removes
+everything that's an annotation (things that take text and fiddle with
+it in some way), and not objects or structure - in VisualEditor
+language, ""styles"".
+
+I.e., things that are removed:
+
+* Bold, italics, underlines, strikethrough, superscript, subscript,
+  code style
+* Text size (big/small and font-size attributes)
+* Rich text annotations - links, language (lang=""fr""), direction
+  (dir=""rtl""), …
+* Colours (foreground and background highlight) on text
+* Arbitrary paragraph settings (<span>s with style tags, etc.)
+
+… and things that remain:
+
+* Formats (paragraph/heading/preformatted/blockquote/…)
+* Structure (numbered list/bulleted list/definition list/table/…)
+* Objects (media items/galleries/transclusions/equations/…)
+
+> My point is that bold and italic, etc. are a subset of formatting,
+> but links aren't.
+
+In your meaning of the term ""formatting"". I don't use it that way, and
+neither do similar functions in other rich editors like Word or Google
+Docs, I believe.
+
+> I want the ability to remove formatting without removing links, and
+> the ability to remove links without removing formatting.
+
+I understand the request. :-) I just don't think that it's a need that
+is sufficiently widely-held that we should burden all users with an
+extra button and a confusing ""everything except not that one sorry""
+cognitive step.",1383006366,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"(In reply to comment #3)
+Also, removing a link takes three clicks if you don't use 'clear
+> formatting'.
+Which is why I said there should be a separate button to remove links with a single click.
+ 
+> 'Clear markup' would be more descriptive, but probably less user-friendly.
+""Clear markup"" doesn't describe what it does either, because it doesn't remove paragraph style, text size, templates, colour, etc. It only removes text formatting and links.
+
+My point is that bold and italic, etc. are a subset of formatting, but links aren't. I want the ability to remove formatting without removing links, and the ability to remove links without removing formatting.",1375800747,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"I agree that links are fundamental to Wikipedia (and other wikis).  However, I think it is quite reasonable that 'clear formatting' removes links.  If you want to remove something in particular, you can use the individual buttons (click bold to unbold, etc.) in most cases.
+
+Part of this is that I've already become used to using 'clear formatting' for links in VE.  But I don't think this seemed unintutive even when I started using VE.  Also, removing a link takes three clicks if you don't use 'clear formatting'.
+
+'Clear markup' would be more descriptive, but probably less user-friendly.",1375599397,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"Well ""superscript/subscript/underline/strikethrough/big/small/code
+formatting and <span>s setting arbitrary formatting annotations (like ""color:
+red;"" or ""font-family: serif;"" are all just different sorts of text decoration formatting like bold and italic so the clear formatting button is appropriate for all of them.
+
+""language settings (lang=fr and dir=rtl)"" are not in my mind the same thing as bold, strikethrough, etc, but equally they're not the same thing as links. I haven't thought about them before now and I at this point I just don't know what my opinion is and I don't really know what the arguments for an against are, so more thinking needed before I can you a proper answer for those, sorry.
+
+I think possibly the difference in our opinions about links is that you are approaching this from a ""make it like a popular word processor that can edit Wikipedia"" whereas I'm thinking of it from ""make it an editor for Wikipedia that works like word processors"". There might not sound much different in those philosophies, and in most cases I don't think there is. However from a word processing POV links are useful-to-have additional metadata, whereas from a Wikipeida editor POV links are fundamental to the structure and essence they don't conceptually fit with decoration.",1374821514,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"This is exactly as designed. It also removes language settings (lang=fr and dir=rtl), superscript/subscript/underline/strikethrough/big/small/code formatting, and <span>s setting arbitrary formatting annotations (like ""color: red;"" or ""font-family: serif;"" or …). It's modelled against the same function in other editors, rendering the text down to completely plain text (except for objects like references or templates).
+
+Do you think each of these formatting options should have a ""remove"" function? Only some of them? Only those that trigger an inspector rather than just a boolean state (like links, language and arbitrary settings)? Only links? Why/why not? Happy to change direction but it would need to be a pretty strong reason to change (amongst other things, we'd need to give users ways to break out of the other kinds of pre-annotations as well as removing the selected annotation).",1374798885,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Support for SFN and similar references,"One of the major advances in wiki editing in the last few years has been support for the short template-based referencing systems like SFN. I've made it a basic rule to use SFN if a reference is used more than twice within the article, and an inline only in the rare case where it is used once or twice. I realize my editing patterns are not normal, but I think support for these templated refs would improve the editor greatly. 
+
+Perhaps a ""toolbar-like"" editor to one side of the main editor could list of global references created so far, and allow the user to drag a handle from them into the article to place the ref in the body.
+
+Even better, perhaps the use could drag URLs or text into the bar to create semi-filled out master refs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374057780,PHID-USER-5tluooawvjfhtqywnxag,PHID-TASK-ksoksajvjcd37y5wvvq2,task_description,declined
+VisualEditor: Support for SFN and similar references,"JD, can you point to the ""as discussed previously""? I am not familiar with the problem, so do I understand why this would be a ""horrible hack"".",1442227600,PHID-USER-5tluooawvjfhtqywnxag,PHID-TASK-ksoksajvjcd37y5wvvq2,task_subcomment,NA
+VisualEditor: Support for SFN and similar references,"I guess I agree that it may not be worthwhile to support creating new footnotes with the [[https://en.wikipedia.org/wiki/Template:Sfn| shortened footnotes (SFN) template]]. 
+
+However, for the time being this system is still around on enwiki. And since this bug was filed, the citation reuse features was introduced in VE, and there it's an awkward and confusing user experience that one is not able to reuse already existing sfn footnotes. 
+
+Compare the list of footnotes offered for reuse in
+https://en.wikipedia.org/w/index.php?title=AI_winter&oldid=680877170&veaction=edit  (via ""Cite"" -> ""Re-use"")  with the actual [[https://en.wikipedia.org/w/index.php?title=AI_winter&oldid=680877170#Notes |list of footnotes in that article revision]]. The numbering is inconsistent, e.g. #7 (John Hutchins) in the article becomes #3 in VE, with the original footnots #3, #4, #5 and #6 mission. I had to search and think for a while to realize that I wasn't simply overlooking things and that the reason for the discrepancy is this template.",1442195570,PHID-USER-wlku5ja6envbi4cz2etp,PHID-TASK-ksoksajvjcd37y5wvvq2,task_subcomment,NA
+VisualEditor: Support for SFN and similar references,"Cite.php is designed a certain (bad) way. It has issues, and we will replace it at some point, but the way to fix its issues is not to make horrible hacks in wikitext using loopholes over-looked when the code was written to try to re-design in.
+
+This is one of those cases, and is not sanely supportable in VisualEditor, so I'm going to mark this as WONTFIX. I know I previously said ""lowest"", but I don't think that that's a justifiable direction for the product to go in.",1393541245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ksoksajvjcd37y5wvvq2,task_subcomment,NA
+VisualEditor: Support for SFN and similar references,"As discussed previously, supporting this wikitext hack is exceptionally difficult to do, and it would be much more sensible to spend the effort on a proper cross-page, cross-wiki citations system instead which would solve the same problem (and lots more). However, it's not impossible, so keeping open as a lowest-priority enhancements.",1383281654,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ksoksajvjcd37y5wvvq2,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"Hi,
+
+a: Currently language list displayed below MediaWiki:Visualeditor-dialog-meta-languages-readonlynote/mr does not open the respective language wiki but when that is possible along with that respective language item ULS should offer option to open up the respective language wiki with related display and/or input .May be this shall need to mingle three extensions VE,wikidata,ULS and also
+
+b When in menubar languages displayed by wikidata if curser hover over any wiki language name options as requested in 4a should display and available. (Whether this needs to split as a separate 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_28864
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51431",1373886360,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-jfzrmnmoj3qahau2ohse,task_description,open
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"1(In reply to comment #6)
+> (In reply to comment #5)
+> However, is this a duplicate of bug 52383 maybe?
+
+::No not at all,if I have read bug 52383 correctly,it is asking to scrap certain feature made avaialable by VE by some frustrated user.Unless you are ready to scrap parts of VE design in that sense it is not an enhancement bug at all and most likely bug 52383 need to be wont fix
+
+
+* This bug 51355 assumes that any way you will be completeing the bug 52105. This bug is an enhancement over bug 52105 (So parsing job is happening at bug 52105)  and also expects bug 51431 enhancement also too take place.
+::In other words this bug 51355 wants to mount bug 51431 enhancement over bug 52105 enhancement.",1376726474,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"(In reply to comment #5)
+> *In VisualEditor - Toolbar -Page settings - language Section shows languages
+> heading with following message  
+> http://www.mediawiki.org/wiki/MediaWiki:Visualeditor-dialog-meta-languages-
+> section 
+> *Below this message  VisualEditor - Toolbar -Page settings - language Section
+> reproduces the same list of interwiki languages that I provided by Wiki data.
+> *Currently these language links are not parsed. 
+
+Not sure what you want to ""parse"" here, plus parsed by who?
+However, is this a duplicate of bug 52383 maybe?
+
+Please also update the bug summary to be descriptive. Thanks!",1376565627,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"I have split point b in a separate bug 51431.  
+
+
+*In VisualEditor - Toolbar -Page settings - language Section shows languages heading with following message  
+http://www.mediawiki.org/wiki/MediaWiki:Visualeditor-dialog-meta-languages-section 
+
+*Below this message  VisualEditor - Toolbar -Page settings - language Section reproduces the same list of interwiki languages that I provided by Wiki data.
+
+*Currently these language links are not parsed. 
+
+*This bug expects the same feature that is expected in bug 51431 but in context of Visual Editor toolbar -page settings languages",1374080554,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,...and please provide a bug summary that describes the actual feature request.,1374075864,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"Please provide exact and clear steps (click by click, as a numbered list) so anybody else could reproduce the problem, plus the expected and the actual outcome. I still don't know which page you are on, etc.
+See https://www.mediawiki.org/wiki/How_to_report_a_bug for general info.",1374075169,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"Created attachment 12860
+Request for Wikidata interwiki wikis to open with respective language ULS display and input
+
+**Attached**: {F11455}",1373971802,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"Please provide a screenshot of the current problem that you would like to
+solve, plus a link to a wikipage where the problem can be seen. 
+Furthermore, please only file one problem per report. 
+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.",1373893720,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"The ability to sign posts is useful outside of talk name spaces. For instance http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback is in project space. While that might one day be in flow there are many other project space items where  its useful to be able to sign. For instance lists of project members. Some uses have guest books in the User: space which can be signed. 
+
+You can't even enter them manually due to T51820.
+
+A button to insert this would be good, possibly done at the same time as bug 38029 which would insert symbols.
+ 
+This was discussed at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Let_me_sign.21
+
+----
+
+VisualEditor now allows you to insert signatures on pages that are in `$wgExtraSignatureNamespaces` (and any talk pages).
+
+This was previously implemented as a user script / gadget is available at https://meta.wikimedia.org/wiki/User:Matma_Rex/visualeditor-signature.js.",1373511180,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-kttslfnxq434mabydy2v,task_description,resolved
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"@Trizek-WMF Sure, I know, @Urbanecm told us the same on cswiki on community forum. I think we also have got on cswiki some bugs subpage under WP:Flow page, where all the bugs found are listed. I'll take a look into tasks I sent here, if there is another one I forgot to mention on that subpage.",1467125739,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"@Trizek-WMF Sure, I know, @Urbanecm told us the same on cswiki on community forum. I think we also have got on cswiki some bugs subpage under WP:Flow page, where all the bugs are listed. I'll take a look into tasks I sent here, if there is another one I forgot to mention on that subpage.",1467125678,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"@Dvorapa, please contact me if you have any suggestions about Flow bugs which need to be fixed.",1467110390,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,,1466612046,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,,1466604894,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,">>! In T53154#2399021, @Dvorapa wrote:
+> @Jdforrester-WMF I see, thank you. Still looking for a good talk solution - Flow is too buggy, VisualEditor is not really designed for discussions and wikitext is not easy to learn for novice users.
+
+I think getting the bugs in Flow fixed is the best option at this point, but I appreciate that there's a few things people would like to see added there.",1466602713,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"@Jdforrester-WMF I see, thank you. Still looking for a good talk solution - Flow is too buggy, VisualEditor is not really designed for discussions and wikitext is not easy to learn for novice users.",1466602589,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,">>! In T53154#2398111, @Dvorapa wrote:
+> Is there any option how to add a signature button to the main VE bar (e.g. instead of the special symbol button or next to?) (discussed on cswiki; just asking if possible)
+
+This is not possible. We intentionally do not allow the toolbar to vary in the position of buttons on the same wiki.",1466602060,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,Is there any option how to add a signature button to the main VE bar (e.g. instead of the special symbol button or next to?) (discussed on cswiki; just asking if possible),1466559576,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Is there any option how to add a signature button to the main VE bar (e.g. instead of the special symbol button or next to?) (cswiki; in discussion, just asking if possible)",1466559547,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,Is there any option how to add a signature button to the main VE bar (e.g. instead of the special symbol button or next to?),1466559506,PHID-USER-dcexrhjioxqqsq4pdrfe,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Change 251834 merged by jenkins-bot:
+Provide a tool to insert a signature in namespaces that need it
+
+[[https://gerrit.wikimedia.org/r/251834]]",1447719403,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Change 251834 had a related patch set uploaded (by Bartosz Dziewoński):
+Provide a tool to insert a signature in namespaces that need it
+
+[[https://gerrit.wikimedia.org/r/251834]]
+",1447004908,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Hmm, and so it seems that the $wgExtraSignatureNamespaces functionality provided by https://gerrit.wikimedia.org/r/87649 (T7645) was actually merged, even thought it looked hopeless a year ago. I think we can go ahead with migrating my gadget to VisualEditor proper, and enabling the signature inserting tool only in those namespaces.",1441556932,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,">>! In T53154#1138179, @Juandev wrote:
+> Thank you for the code. Could the user also add a special button to VE or is it a difficult cooding? 
+
+Per the task description and per my previous comment, there is a gadget that implements this that you can easily enable for yourself, or on your wiki.",1426958719,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,,1426958667,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,,1426958656,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,">>! In T53154#537004, @AdHuikeshoven wrote:
+> Adding a signature with VisualEditor can be simulated using a template:
+> 
+> ---template code:---
+> {{{Sign}}}
+> <noinclude>
+> This template allows to sign using Visual Editor by adding this template as you can't enter four tildes <nowiki>~~~~</nowiki> in VE. Enter the template in VE. Hit Add template. Enter <nowiki>~~~~</nowiki> in the field. Hit Insert template. Hit Save page. Enter edit summary. Hit Save. Doone.</br>
+> <templatedata>
+> {
+> 	""description"": ""A template to sign using Visual Editor. "",
+> 	""params"": {
+> 		""Sign"": {
+> 			""aliases"": [
+> 				""Signature""
+> 			],
+> 			""label"": ""Sign by entering ~~~~ in the field below"",
+> 			""description"": ""Field to enter signature, that is four tildes"",
+> 			""default"": ""Please enter four tildes here"",
+> 			""required"": true
+> 		}
+> 	}
+> }
+> </templatedata>
+> </noinclude>
+> ---end of template code---
+> 
+> Usage:
+> Enter the template in VE. Hit Add template. Enter ~~~~ in the field. Hit Insert template. Hit Save page. Enter edit summary. Hit Save.
+> 
+> Example:
+> See https://www.mediawiki.org/wiki/Template:VESign. Application of template tested on https://www.mediawiki.org/wiki/User:Ad_Huikeshoven/test. 
+> 
+> Evaluation:
+> There might be nicer methods to accomplish the same, maybe using JS (I have no experiene writing JS). When there is a switch over to Parsoid rendering the templates mid-edit rather than relying on PHP parser the above solution will probably break, as will probably do any solution to bug 51146.
+
+Thank you for the code. Could the user also add a special button to VE or is it a difficult cooding? ",1426954578,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,I updated the description with information about the gadget implementing this feature.,1425561628,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,@Pine: Yes I'd object. :) Please see T53154#536989,1425558453,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,Would anyone object to bumping up the priority of this to normal?,1425544467,PHID-USER-l7v72q5tq6vg6zclrld6,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Like @AdHuikeshoven, I just ran into the use case where I can't sign myself to a list of Wikimania talk attendees.",1425083820,PHID-USER-p6hvqn5njgnxuagekh4b,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Yes, I've moved it to talk space. Sorry I didn't catch that earlier.",1412362166,PHID-USER-l7v72q5tq6vg6zclrld6,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to Pine from comment #22)
+> Perhaps someone enabled VE on talk pages when they shouldn't have?
+> 
+> It's enabled on https://meta.wikimedia.org/wiki/Grants:APG/Comments
+
+Argh. That's not a talk page. You can tell because the talk page would be https://meta.wikimedia.org/wiki/Grants talk:APG – this is really unhelpful of people to use the wrong namespace. I'm sorry about that. :-(",1412362031,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Ah, I see. That's not really labeled as a talk page on Meta, but it probably should be. I'll try to take care of that.",1412362011,PHID-USER-l7v72q5tq6vg6zclrld6,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Perhaps someone enabled VE on talk pages when they shouldn't have?
+
+It's enabled on https://meta.wikimedia.org/wiki/Grants:APG/Comments",1412361949,PHID-USER-l7v72q5tq6vg6zclrld6,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to Pine from comment #20)
+> I am raising the priority of this bug. VisualEditor is now enabled for talk
+> pages on Meta, yet I can't insert my signature using VisualEditor, which is
+> a major shortcoming. Please fix!
+
+What talk pages is it enabled for? Can you give an example? It doesn't appear on the talk pages I just looked at. This feels like a distinct bug.
+
+Please read the history of this bug for why this is explicitly outside of the plans for VisualEditor; it's fundamentally the wrong approach. Resetting priority.",1412361791,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"I am raising the priority of this bug. VisualEditor is now enabled for talk pages on Meta, yet I can't insert my signature using VisualEditor, which is a major shortcoming. Please fix!",1412361008,PHID-USER-l7v72q5tq6vg6zclrld6,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"It seems that bug 5645 which I thought to be a dependency is not going to be fixed in a useful way. The only way to proceed would be reimplementing the namespace selection logic in VE, which I'm wary of. I don't know how to proceed with this, I guess we'll be stuck with the gadget for the time being.",1406412781,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Actually, a $wg config variable for this is not a very good idea. We should just be smart and display the signature button in the namespaces that need it (and no others).
+
+Core MediaWiki currently has no way to do this (other than the implied assumption that all talk namespaces need signatures), but there happens to be a patch pending that would introduce one (https://gerrit.wikimedia.org/r/87649). We should just wait for that to be implemented, and then use the same logic as wikitext editor when deciding whether to enable signatures or not.",1405887415,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to Bartosz Dziewoński from comment #16)
+> That sounds fine by me. So it would be enabled with a $wg config variable?
+
+That was my thought, yes.
+
+> I wonder if it would make sense to let users enable it for themselves (by
+> loading a RL module in common.js, for example).
+
+It doesn't; either VE namespaces are signable or they're not. A per-user setting doesn't make sense.
+
+""Assigning"" to Bartosz given he's done all the work here. :-)",1405787749,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"That sounds fine by me. So it would be enabled with a $wg config variable?
+
+I wonder if it would make sense to let users enable it for themselves (by loading a RL module in common.js, for example).",1405775648,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to Lokal_Profil from comment #14)
+> Being a basic building block of a wiki which is currently missing from VE I
+> would not mark this as Resolved until there is a solution integrated in VE.
+> Better then to leave it open and hope that some volunteer takes it on if it
+> is deemed to be outside of the scope for Wikimedia to implement.
+
+There is never going to be a ""sign post"" feature integrated into VisualEditor as deployed on WMF servers. That's the whole point of Flow. From a perspective of ""VisualEditor for WMF users"", this is WONTFIXed.
+
+This bug is not marked as ""WONTFIX"" though, because it's entirely plausible that someone might want to run VisualEditor on a wiki without Flow (or LQT or Message Wall or whatever).
+
+Maybe we should bundle up Bartosz's code into a VE plug-in that's available for users (but not on by default)?",1405474400,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Being a basic building block of a wiki which is currently missing from VE I would not mark this as Resolved until there is a solution integrated in VE. Better then to leave it open and hope that some volunteer takes it on if it is deemed to be outside of the scope for Wikimedia to implement.
+
+Adding a signature should be as easy or easier (for the user) as adding an image or template. Also since there is nothing preventing signatures from being added to any namespace in the wikitext editor there should be no hard-coded exceptions in the VE-solution (although there could of course be site-wide setting disallowing them.",1405344964,PHID-USER-uu7wg6g3b37dcktbje3a,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"I wonder what should we do with this bug? I think it should be marked either RESOLVED WONTFIX or RESOLVED FIXED, but I'm not sure which is more appropriate.",1405339051,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,I replied at [[meta:User talk:Matma Rex/visualeditor-signature.js]].,1405338928,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to SJ from comment #3)
+> I think it is important to enable signatures in VE.  I have found it useful
+> in a few circumstances; and regretted having to drop out of VE just for that
+> one addition.
+
+The use case I would like mention is adding your name to the list of interested attendees at the program pages of https://wikimania2014.wikimedia.org/. Bartosz tools works wonderfully outside content name space. However, it explicitly doesn't work on content name space in which the program pages at the Wikimania site reside.",1405327655,PHID-USER-mcyovqjor52nj3se4lq7,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Whoa, that's scary. Please don't do that.
+
+I wrote a script to implement signatures properly. This definitely isn't what the editor was designed to do, but, as it was noted in earlier comments, this has its use cases.
+
+https://meta.wikimedia.org/wiki/User:Matma_Rex/visualeditor-signature.js
+
+Please comment about it on the script's talk page, not here :) I'd be happy to include more translations (there are just two words to translate).
+
+I think the only thing missing is an icon that would match the look-and-feel of existing ones. I'd be happy to add it, too, if only someone drew one (SVG).",1405303431,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Adding a signature with VisualEditor can be simulated using a template:
+
+---template code:---
+{{{Sign}}}
+<noinclude>
+This template allows to sign using Visual Editor by adding this template as you can't enter four tildes <nowiki>~~~~</nowiki> in VE. Enter the template in VE. Hit Add template. Enter <nowiki>~~~~</nowiki> in the field. Hit Insert template. Hit Save page. Enter edit summary. Hit Save. Doone.</br>
+<templatedata>
+{
+	""description"": ""A template to sign using Visual Editor. "",
+	""params"": {
+		""Sign"": {
+			""aliases"": [
+				""Signature""
+			],
+			""label"": ""Sign by entering ~~~~ in the field below"",
+			""description"": ""Field to enter signature, that is four tildes"",
+			""default"": ""Please enter four tildes here"",
+			""required"": true
+		}
+	}
+}
+</templatedata>
+</noinclude>
+---end of template code---
+
+Usage:
+Enter the template in VE. Hit Add template. Enter ~~~~ in the field. Hit Insert template. Hit Save page. Enter edit summary. Hit Save.
+
+Example:
+See https://www.mediawiki.org/wiki/Template:VESign. Application of template tested on https://www.mediawiki.org/wiki/User:Ad_Huikeshoven/test. 
+
+Evaluation:
+There might be nicer methods to accomplish the same, maybe using JS (I have no experiene writing JS). When there is a switch over to Parsoid rendering the templates mid-edit rather than relying on PHP parser the above solution will probably break, as will probably do any solution to bug 51146.",1405282624,PHID-USER-mcyovqjor52nj3se4lq7,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"To clarify, this is a ""WONTFIX"" for VE as it is (and will be) enabled on WMF projects, but if someone wants to write a plugin for VE for other wiki hosts using it that want to try to make VE work in discussion namespaces (and don't want to use Flow).
+
+There are a number of meanings of ""Lowest"" priority, and this is one of the confusing ones. Sorry. :-(",1390430037,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to comment #6)
+> Will Flow be applicable to all namespaces? There are lots of article-style
+> pages that temporarily or permanently would benefit from inline comments in
+> the
+> middle of what is otherwise a full-text long-form page.  In those cases* I
+> don't see how the Flow design will help.
+
+Like what? Some examples, please?
+
+> 
+> Signatures are useful in most namespaces, whereas ""idiosyncratic protocols
+> and
+> templates and formats"", with unknown amounts of associated work, seem like
+> higher-hanging tasty fleshy vegetalia.
+> 
+Sure, and work on those namespaces is best done when we actually discuss _deploying_ in those namespaces - and when it is fully working for the primary target of the VE (i.e., the mainspace).
+
+> * Examples: wikis that don't separate talk from content; wikis that have two
+> layers of talk: limited inline v. permanent talk-threads; articles or main
+> pages that tabulate membership or participation or otherwise include tables
+> that include user signatures.
+
+Actual examples for each example...?",1390426187,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Will Flow be applicable to all namespaces? There are lots of article-style pages that temporarily or permanently would benefit from inline comments in the middle of what is otherwise a full-text long-form page.  In those cases* I don't see how the Flow design will help.  
+
+Signatures are useful in most namespaces, whereas ""idiosyncratic protocols and templates and formats"", with unknown amounts of associated work, seem like higher-hanging tasty fleshy vegetalia.
+
+* Examples: wikis that don't separate talk from content; wikis that have two layers of talk: limited inline v. permanent talk-threads; articles or main pages that tabulate membership or participation or otherwise include tables that include user signatures.",1390423793,PHID-USER-fgzcdbj3je3ksnhufo47,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"That's probably something to do with the fact that the VE isn't really being used in discussion namespaces.
+
+This is not, by far, the only feature blocking VE from being useful in many other contexts. A lot of the discussion namespaces have their own idiosyncratic protocols and templates and formats that parsoid and the VE will then have to directly support, which is likely to be some (unknown) additional amount of work, and that'll all be done just in time for us to start releasing Flow, which does auto-signing.
+
+I can understand the low prioritisation ;).",1390420131,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,I just noticed this is flagged as lowest-priority enhancement... again surprising considering the importance and prevalence of signing in wiki culture and other MW docs.,1390419820,PHID-USER-fgzcdbj3je3ksnhufo47,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"I think it is important to enable signatures in VE.  I have found it useful in a few circumstances; and regretted having to drop out of VE just for that one addition.
+
+This is the only feature blocking VE from being useful in a much wider variety of contexts, in my opinion.  (And it's odd for all sig options to be missing when reminders about how to sign and where to sign are some of the most prominent in the MediaWiki interface otherwise.)",1390419772,PHID-USER-fgzcdbj3je3ksnhufo47,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Let_me_sign.21
+
+^Updated link",1373787620,PHID-USER-kmbrbjm7jackp4nrang3,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"The VisualEditor isn't going to be in project space at any point in the near future, however.",1373571593,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","**Author:** `mcdevitd`
+
+**Description:**
+""Preformatted"" is HTML jargon which most of VisualEditor's target users will not understand, and it actually produces an effect (text with less formatting) which is unexpected if you don't know what it means beforehand. It should either be given a plain-language name so that people will expect the behavior, or removed.
+
+I actually don't understand why this style effect is in the header-level pull-down when it is not a header-level. My preference is to remove it, since it is uncommon and mostly adding noise, but it should be renamed if kept.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373247780,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_description,open
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","Also, a dictionary cite for usage of ""pre-formatted"": http://www.oed.com/view/Entry/149454?rskey=n6kMKv&result=2&isAdvanced=false#eid51449481 (not that it gives a definition or synonym we could use).",1394476377,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","(In reply to Dominic from comment #7)
+> (In reply to James Forrester from comment #6)
+> > (In reply to MZMcBride from comment #5)
+> > 
+> > I'm inclined to WONTFIX at this point…
+> 
+> I was under the impression that VisualEditor was about removing jargon
+
+Sort-of.
+
+Actually, it's about making it easy to edit content.
+
+
+> and unneeded advanced features that clutter the user experience.
+
+No.
+
+In meeting the ""making it easy to edit content"" objective, we can't rope off some content that is considered ""too difficult"" to explain nicely.
+
+
+> All three of the other commenters here agreed that ""Preformatted"" is jargon
+> that should at least be renamed using plain language.
+
+Sure, but no-one has actually suggested something they think is better yet (Chris suggested ""monospace"", but said he didn't like it, and I somewhat agree). Until such time as someone suggests a better term, this is unfixable.
+
+
+> And it's not really even clear why we expect ""preformatted"" to be a common
+> enough formatting choice among VisualEditor users that it even merits the
+> inclusion in that menu.
+
+That's a more interesting question, yes, as I said in comment 6. But that's not what other people's comments on this bug have been about.
+
+
+> Your comment on WONTFIXing the report doesn't address the actual problem
+> being raised.
+
+Pick one. Either this bug is about removing ""preformatted"" as an option, in which case WONTFIX stands, or it's about something else (""come up with a different name""? ""have a secondary system for less-common formats""? something else?) and make it about that?
+
+
+
+(In reply to MZMcBride from comment #8)
+> Eh, this is a bad wontfix. My dictionary doesn't contain ""preformatted""; we
+> can probably come up with a better term.
+
+See above.
+
+
+> Regarding the user interface, it's a bit confusing why there's a text
+> formatting menu (paragraph text and headings) next to another text
+> formatting menu (bold, underline, computer code, etc.). It might make sense
+> to move the artist currently known as preformatted to the bottom of the
+> latter menu as it's not very commonly needed (about as commonly needed as
+> needing to write ""computer code"" using VisualEditor, surely).
+
+It's formatting vs. styling; one operates on paragraphs, the other on selections (which can be smaller than a paragraph). I agree that it's confusing (yay HTML and MediaWiki), but I think it would be more confusing to have things in the same menu that do radically different things without distinction.",1394475244,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","Eh, this is a bad wontfix. My dictionary doesn't contain ""preformatted""; we can probably come up with a better term.
+
+Regarding the user interface, it's a bit confusing why there's a text formatting menu (paragraph text and headings) next to another text formatting menu (bold, underline, computer code, etc.). It might make sense to move the artist currently known as preformatted to the bottom of the latter menu as it's not very commonly needed (about as commonly needed as needing to write ""computer code"" using VisualEditor, surely).",1393989052,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","**mcdevitd** wrote:
+
+(In reply to James Forrester from comment #6)
+> (In reply to MZMcBride from comment #5)
+> 
+> I'm inclined to WONTFIX at this point…
+
+I was under the impression that VisualEditor was about removing jargon and unneeded advanced features that clutter the user experience. All three of the other commenters here agreed that ""Preformatted"" is jargon that should at least be renamed using plain language. And it's not really even clear why we expect ""preformatted"" to be a common enough formatting choice among VisualEditor users that it even merits the inclusion in that menu.
+
+Your comment on WONTFIXing the report doesn't address the actual problem being raised.",1393987799,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","(In reply to MZMcBride from comment #5)
+> Should this bug report continue to be assigned?
+> 
+> I think a mock would help here.
+
+A mock of what? Moving some (but not all) paragraph-level formats somewhere else seems like a really bad design. We'd be talking about pre-formatted, blockquote, and maybe other like poem and so-on being in one menu, and other tools that operate in the exact same way (e.g. don't apply to a selection). I'm inclined to WONTFIX at this point…",1393527782,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","Should this bug report continue to be assigned?
+
+I think a mock would help here.",1392360410,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","Now that we have the ""more"" menu I don't think the button issue exists (to the same degree at least) as it did.
+
+As the ""preformatted"" name I agree it doesn't make sense, as this isn't really what it does. I was going to suggest ""monospaced"" but it's more than that - it's monospaced and indented with a shaded background. However, <code> also produces monospace and a shaded background but that is different.",1379693519,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","**mcdevitd** wrote:
+
+My confusion came from the fact that the user guide refers to it as the ""Headings pull-down menu"" (http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/User_guide#Getting_started:_the_VisualEditor_toolbar), and every other option in the menu is a heading level (or no level), not a style.
+
+If there is somewhere else where styles like pre are going to go, or you intend to add other styles to this same menu, that's fine with me, but my original point about it being jargon still stands. (Though if you add more style options to the same menu, I think that is even more reason to remove pre as noise.)",1373524183,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","This isn't a ""header pull-down menu"", it's a text style menu. Also, having yet another control in the toolbar (for blockquote, pre and whatever else) doesn't feel great. :-(",1373504408,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","I agree.
+
+It's strange that it's currently in the header menu. A separate menu for <blockquote> and <pre> may make sense.",1373282762,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+VisualEditor: Remove Opera from blacklist,"I think we can (almost) remove Opera from the blacklist now, see blocking bug 36000. Opera < 12 should still probably be blacklisted, though, and < 10 should be blacklisted for sure (there's a bunch of people who insist that 9.64 was the ultimate version ever and stick to it).
+
+It'd be cool if it could be added to the whitelist as well, but I guess that would be a promise to support it and you guys probably don't want to promise that ;)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373044680,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g36wsrlii3gd62hxtn2u,task_description,resolved
+VisualEditor: Remove Opera from blacklist,It was unblacklisted in the now-merged Ia80a6f53.,1375135090,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g36wsrlii3gd62hxtn2u,task_subcomment,NA
+VisualEditor: Remove Opera from blacklist,"(In reply to comment #2)
+> Note that the Presto engine-based Opera 12.x is being end-of-lined; the new
+> Opera 15 is Chromium-based.
+
+There is no release date or anything apart from a very early alpha of Opera 15 (which basically does nothing apart from showing pages). I'd say Opera 12 still has a bit of time before it.
+
+
+> Is it worth worrying about Opera 12.x compatibility?
+
+Still, objectively, maybe it's not. But I care personally. :)",1373052515,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g36wsrlii3gd62hxtn2u,task_subcomment,NA
+VisualEditor: Remove Opera from blacklist,"Note that the Presto engine-based Opera 12.x is being end-of-lined; the new Opera 15 is Chromium-based.
+
+Is it worth worrying about Opera 12.x compatibility?",1373046513,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-g36wsrlii3gd62hxtn2u,task_subcomment,NA
+VisualEditor: Remove Opera from blacklist,"(In reply to comment #0)
+> I think we can (almost) remove Opera from the blacklist now, see blocking bug
+> 36000. Opera < 12 should still probably be blacklisted, though, and < 10
+> should
+> be blacklisted for sure (there's a bunch of people who insist that 9.64 was
+> the
+> ultimate version ever and stick to it).
+> 
+> It'd be cool if it could be added to the whitelist as well, but I guess that
+> would be a promise to support it and you guys probably don't want to promise
+> that ;)
+
+Very happy to add to the whitelist if you're sure that everything works perfectly. It's not a state a browser can only reach if supported by WMF, if you want to commit to doing that. The comprehensive testing is quite a high bar, however - does Opera now cope with everything at mediawiki.org/wiki/VisualEditor/Basic_example_worksheet ?",1373046107,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g36wsrlii3gd62hxtn2u,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,"Because.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373035320,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-eulhe75w7cy7if64iutj,task_description,declined
+VisualEditor: VisualEditor needs easter eggs,"Call me boring, but… :-)",1393642162,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,"(In reply to comment #4)
+> Articles mysteriously being littered with ♙ and ☃ doesn't count? :-)
+
+No :P",1383332239,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,Articles mysteriously being littered with ♙ and ☃ doesn't count? :-),1383324321,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,,1373035563,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,"Maybe it already has them, and we're just not cool enough to know...",1373035520,PHID-USER-2nnm76h4ykalvvref2ye,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,Maybe you're just not looking hard enough,1373035486,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"When you add a new citation in VE, templates which wrap the `<references />` tag do not update to display it until the page is saved. Examples include [[https://en.wikipedia.org/wiki/Template:Reflist|`{{reflist}}`]] on the English Wikipedia and [[https://es.wikipedia.org/wiki/Plantilla:Listaref|`{{listaref}}`]] on the Spanish Wikipedia. This bug doesn't block any of the core citation workflows (creating, editing, and reusing) since those are accessed from the toolbar and the in-text reference numbers, but it's still very annoying. 
+
+However, it remains unfixed because it's an //extraordinarily// hard technical challenge, verging on impossible given the current architecture of Mediawiki. No one has any idea what a workable solution would look like. Just to give one facet of the problem, you could implement this in VE right now //if// you completely re-parsed the entire page every time the user touched a template or a reference—which would be a //horrible// user experience and place //insane// loads on the servers. It's possible that in the future, someone will think up a brilliant solution that avoids all these huge issues, so this task remains open.
+
+In the meantime, the planned solution is to update the `<references />` tag, which does update properly during editing, to support multiple columns and alternative list styles so they have all the functionality of these templates (T53260). When that task has been completed, communities will be able to replace the templates with references tags at whatever pace and with whatever tools they prefer (if there's demand for it, it would probably be possible to do a more immediate, bot-driven changeover).
+",1372969200,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-kloqgpjwhtcokmj7eica,task_description,resolved
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Thank you.
+",1518731537,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Thanks, I've filed T187495.",1518726539,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,">>! In T52769#3975407, @Esanders wrote:
+> Can you link to an example?
+Sure:
+https://he.wikipedia.org/wiki/%D7%90%D7%93%D7%99_%D7%A7%D7%91%D7%98%D7%A0%D7%A8?veaction=edit&uselang=en",1518706913,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,Can you link to an example?,1518702862,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Hi. Our wiki does not show any references in reflists at all in VE now, the list is empty. All of them are created by reference template, rather than by tag. I was not sure it's new indeed, because I do not use VE, but people say it wasn't like this before.
+",1518653027,PHID-USER-t7ue4j3fnqznjjs4z5ef,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Change 408604 **merged** by jenkins-bot:
+[mediawiki/extensions/Cite@master] Treat template-generated reference lists as real ones
+
+[[https://gerrit.wikimedia.org/r/408604]]",1518112687,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Change 408604 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/Cite@master] Treat template-generated reference lists as real ones
+
+[[https://gerrit.wikimedia.org/r/408604]]",1517948195,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,">>! In T52769#541738, @Jdforrester-WMF wrote:
+> Note that we can't currently see a way to do this without round-tripping the entire page, which would be a sub-optimal solution, to put it mildly.
+
+So, if <references/> directly on the page are supposed to work (they're updated on edit) but when they're inside a template not, it should be possible to make parsoid tag the template with a special property so only that template region gets updated (or the references list) and not the entire page. Note that I'm speaking without knowledge about how the entire thing works.",1467209234,PHID-USER-jnta3z3spxto3vbxdngm,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"So to clarify, it is a known bug that adding references will display the updated reference list when the <references /> tag is used in the article, but not when the {{reflist}} template is used?",1405248457,PHID-USER-evd3wnvnlb66lrwulch4,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,*** Bug 51607 has been marked as a duplicate of this bug. ***,1374167787,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"(In reply to comment #0)
+> What it says on the tin; the addition of a reference is not reflected in an
+> update to {{reflist}} or <references/> or whathaveyou.
+
+I can't replicate the bug as described, but re-purposing to be about our desire to update fake reference lists inside templates on edit, rather than the current unhelpful not-updated-'til-page-save issue.
+
+Note that we can't currently see a way to do this without round-tripping the entire page, which would be a sub-optimal solution, to put it mildly.",1373163815,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+VisualEditor: Editing tool to changing case,"A user has requested a tool to alter the case of text that has been typed. Marking as lowest priority, since we've made clear it's not something anyone is likely to work on any time soon.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T55210}
+{T52678}
+{T55495}
+{T52452}",1372943460,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-w4y2nb4727kwbhfjqdup,task_description,open
+VisualEditor: Editing tool to changing case,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Editing/Case_conversion,1651251693,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-w4y2nb4727kwbhfjqdup,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Occasionally wiki links are being mangled adding ./ to the start and replacing spaces with underscores. For example replacing [[specific name (zoology)|specific epithet]] with [[./Specific_name_(zoology)|specific epithet]]. I've only noticed it with piped links.
+
+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)
+
+possibly related to bug 50428
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50539
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48769",1372919760,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-tyu752voayr4g6elcmgx,task_description,resolved
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Can no longer reproduce the test case given by Erik in FF13/14. Edited the link directly to avoid SelSer.
+
+https://en.wikipedia.org/wiki/HELLP_syndrome?veaction=edit&vewhitelist=1
+
+{F4089820}",1464692505,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them",">>! In T52720#2164275, @Schnark wrote:
+> Should this task just be closed? I don't think anyone is going to put work into supporting  these really old Firefox versions.
+
+I've been keeping this open as we //would// accept any patch doing this. Yes, there are relatively very few users, but it's not great to leave these users without an editor over something that's effectively trivial.",1459413492,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them",Should this task just be closed? I don't think anyone is going to put work into supporting  these really old Firefox versions.,1459413067,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Just wondering, has anybody tested VE on those old Firefoxes somewhat recently? The codebase is changing so fast this might as well be magically fixed now.",1379263769,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","(In reply to comment #11)
+> I think you viewed this bug solely as a blocker to bug 50848. I agree that it
+> no longer is, but I don't believe this bug is now resolved/fixed. The issue
+> hasn't been fixed, as I understand it, just worked around. I'm re-opening the
+> bug, but removing bug 50848 as a blocker, lowering the importance fields, and
+> clarifying the bug summary.
+
+Well, had you given me more than 30 seconds I was in the middle of creating a new bug, but never mind. :-) Repurposing this one.",1373502359,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","I think you viewed this bug solely as a blocker to bug 50848. I agree that it no longer is, but I don't believe this bug is now resolved/fixed. The issue hasn't been fixed, as I understand it, just worked around. I'm re-opening the bug, but removing bug 50848 as a blocker, lowering the importance fields, and clarifying the bug summary.",1373502220,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","We believe that this should not recur due to the (hopefully-temporary) blacklisting of Firefox 13 and 14, which is now live in production. Consequently, I'm marking this bug as fixed. Please re-open if you find it happening again.",1373501510,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Change 72675 merged by jenkins-bot:
+Blacklist Firefox 13 and 14 too
+
+https://gerrit.wikimedia.org/r/72675",1373334336,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Change 72675 had a related patch set uploaded by Jforrester:
+Blacklist Firefox 13 and 14 too
+
+https://gerrit.wikimedia.org/r/72675",1373332958,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them",Can reproduce in Firefox 13 and 14; cannot reproduce in 15 or 17 or 20. Interestingly in Firefox 13 I get a little bit more normalization in the diff as well. Looks like we get more progressively more broken the further down we go. :P,1373135486,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Confirmed in Firefox 14. Steps to reproduce:
+
+1) Open https://en.wikipedia.org/wiki/HELLP_syndrome?veaction=edit as a logged in user
+
+2) Make an unrelated edit
+
+3) Press ""Save"" and ""Review your changes"".
+
+The link [[Right upper quadrant (abdomen)|right upper quadrant]] is transformed to [[./Right_upper_quadrant_(abdomen)|right upper quadrant]].",1373134893,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","According to https://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07#VE_zerschie.C3.9Ft_Kats_und_Wikilinks this seems to be an issue in old Firefox: FF14 inserted the ./, while FF22 didn't.",1373097754,PHID-USER-tyjmn7xcw6s2b6rqagj7,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","I think it might be to do with having punctuation in the links in this edit
+https://en.wikipedia.org/w/index.php?title=Soccer_in_the_United_States&diff=prev&oldid=563041224
+this the links which have ' or ( in them which get mangled other links are ok so
+[[United States men's national soccer team|men's national team]] gets changed to 
+ [[./United_States_men's_national_soccer_team|men's national team]] but [[FIFA World Cup|World Cup]] is unchanged. And [[National Professional Soccer League (1967)|National Professional Soccer League]] is changed to [[./National_Professional_Soccer_League_(1967)|National Professional Soccer League]].",1373089586,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","(In reply to comment #1)
+> Escalating priority. Additional example:
+> 
+> https://en.wikipedia.org/w/index.
+> php?title=OMICS_Publishing_Group&curid=35277259&diff=562944992&oldid=56157968
+> 0
+I can't reproduce this, and can in fact edit the page just fine: https://en.wikipedia.org/w/index.php?title=OMICS_Publishing_Group&diff=563024944&oldid=562947045
+
+This bug must have some particularly nasty cache persistence properties; we've purged the Parsoid caches but that doesn't seem to have made it go away.",1373059132,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them",*** Bug 50539 has been marked as a duplicate of this bug. ***,1373020641,PHID-USER-7hrs7wwclcldf7mm6a7o,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Escalating priority. Additional example:
+
+https://en.wikipedia.org/w/index.php?title=OMICS_Publishing_Group&curid=35277259&diff=562944992&oldid=561579680",1373011178,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"Enhancement request for more informative error messages - as simple as ""Syntax error in JSON on line foo."" would be better than the current message, which is just ""Syntax error in JSON.""
+
+| {F34099979} | {F34099994}",1372704060,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_description,open
+TemplateData: Get better error messages for JSON syntax errors,"While I agree this is a valid feature request, I'm afraid there isn't much we can do at this point. I tried to annotate the generic error message with what `json_last_error_msg()` reports. All it says is ""Syntax error"". 😞 We would need to use another JSON parser to fulfill this feature request. That's unlikely to happen.",1638173623,PHID-USER-u6ycqhfpa3k4yvlpxjt2,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"This is not the same issue as T256574.
+
+
+T256574 is about the error message when clicking the ""Manage TemplateData"" button to open the ""Template documentation editor"" dialog:
+| {F34099977} | {F34099996}
+
+This is about the error message when clicking ""Publish changes"": (currently this error doesn't appear at all, that's yet another separate issue filed as T258790)
+| {F34099979} | {F34099994}",1612991707,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"(In reply to comment #2)
+> Presumably this could be done if bug 50169 was implemented, though. :-)
+
+Well, in case of bug 50169 (VisualEditor plugin for TemplateData) there would never be a syntax error in the JSON because the user wouldn't be editing it directly. They'd be using a form-like interface to interact with it (VE would generate the JSON which is always valid).
+
+However if the VE plugin would have a raw mode to edit the JSON (e.g. using an Ace surface like Extension:CodeEditor does), we could use its JSHint integration to get inline errors by line/char highlighting (e.g. like in Sublime).",1381079222,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"For the moment, you can use TemplateDataEditor to be able to create the <templatedata/> without editing any real JSON.
+
+http://en.wikipedia.org/wiki/User:NicoV/TemplateDataEditor",1374506154,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"**weskaggs** wrote:
+
+Displaying the contents of the line at which an error is detected, with a few lines around it for context, would be almost as useful as a line number.  Of course the actual error can be a long way off from the point at which a syntax error is detected, but the information would still be helpful.  Adding information about the type of error would make it even better.  Really any information at all about the nature of the error would be an improvement.",1372774985,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"Presumably this could be done if bug 50169 was implemented, though. :-)",1372734893,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"It is in my opinion not feasible to get line numbers because we use a native PHP extension to parse the JSON.
+
+If the JSON syntax itself is invalid, there is nothing we can do. Best case scenario the parser gives the type of error (""Unexpected comma"", ""Expected closing curly brace"" etc.) but a line number is unlikely.
+
+Once the JSON is parsed, the TemplateData validation itself (e.g. sets referring to existing parameters) we have full control over and gives pretty informative errors with the full path to the property.
+
+> Unexpected property ""params.user.blabla"".
+> Property ""params.timestamp.description"" is expected to be of type ""string|object"".
+
+etc.",1372711992,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"Until a recent MediaWiki change the default behavior of edit section links was to float to the far side of the heading (right on LTR Wikis, assume this case in the following).
+
+This was changed recently but almost all Wikis provide Gadgets to restore the old behavior (see http://en.wikipedia.org/wiki/MediaWiki:Gadget-righteditlinks.css or http://de.wikipedia.org/wiki/MediaWiki:Gadget-editsection-align-end.css for examples)
+
+The problem is, that the VisualEditor's fly-out-links reserve space to the right for the ""edit source"" link. Therefore when aligning the links right they actually appear with a large distance to the page-margin. The fly-outs should therefore be modified to not reserve any space so the ""edit"" link is correctly aligned right.
+
+To prevent the fly-outs to shift the whole ""edit"" link left as soon as they become visible they could be changed to fly-out to the left in this case or to the bottom.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372460880,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-wxztsvwizvyvhpvx2lty,task_description,resolved
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"This task refers to a short-lived VE feature, where instead of the dual ""edit"" and ""edit source"" section edit links we all know and love today, it only displayed one of the links, and the second one would appear (""fly-out"") when the links were hovered with the mouse. It was so short-lived that I can't even find any screenshots of it; it was implemented in [[https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/69984|change 69984]] (Jun 26, 2013) and then removed in [[https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/77165|change 77165]] (Aug 02, 2013). This task was filed on Jun 29.
+
+No solution is needed any more since we started showing both links, and this probably should have been closed in 2013!",1663958347,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-wxztsvwizvyvhpvx2lty,task_subcomment,NA
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"Trivial patch idea
+
+To add some content: Wouldn't a trivial patch along the lines of the attachment be sufficient to fix this problem?
+
+I'm sure something like this could be implemented with minimal effort for somebody with a little experience!
+
+**Attached**: {F11273}",1372621960,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-wxztsvwizvyvhpvx2lty,task_subcomment,NA
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"I see your point but you have to admit that without changing the style of the edisection-links these Gadgets wouldn't have been necessary in the first place. They are basically ""fixing"" what WMF ""broke"" so it would be nice if you at least tried to supply a solution.",1372620403,PHID-USER-v3yn5qf233ggnnnmvejc,PHID-TASK-wxztsvwizvyvhpvx2lty,task_subcomment,NA
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"(In reply to comment #0)
+> Until a recent MediaWiki change the default behavior of edit section links
+> was
+> to float to the far side of the heading (right on LTR Wikis, assume this case
+> in the following).
+> 
+> This was changed recently but almost all Wikis provide Gadgets to restore the
+> old behavior (see
+> http://en.wikipedia.org/wiki/MediaWiki:Gadget-righteditlinks.css or
+> http://de.wikipedia.org/wiki/MediaWiki:Gadget-editsection-align-end.css for
+> examples)
+> 
+> The problem is, that the VisualEditor's fly-out-links reserve space to the
+> right for the ""edit source"" link. Therefore when aligning the links right
+> they
+> actually appear with a large distance to the page-margin. The fly-outs should
+> therefore be modified to not reserve any space so the ""edit"" link is
+> correctly
+> aligned right.
+> 
+> To prevent the fly-outs to shift the whole ""edit"" link left as soon as they
+> become visible they could be changed to fly-out to the left in this case or
+> to the bottom.
+
+Note that in general WMF does not support gadgets and does not encourage their use; they are highly likely to break like this when the code they depend on changes, and this is a good example of that breakage. :-(
+
+I've re-written this a bit to be clearer. As ""lowest"" priority, reflecting that we don't support gadgets. of course anyone who is interested in patching is welcome to suggest ideas/code that could address this.",1372620013,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-wxztsvwizvyvhpvx2lty,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"It has been mentioned in some places[1][2] that the JSON syntax might be a problem for typical (non-technical) users, so I suggest creating a plugin for editing the content of the <templatedata> tags.
+
+[1] https://commons.wikimedia.org/wiki/Template_talk:Information#Adding_TemplateData_information
+[2] https://pt.wikipedia.org/wiki/WP:Café_dos_programadores#Mais_uma_novidade:_TemplateData
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51734",1372160580,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-blsibbjjroitozskiyjq,task_description,resolved
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"This was done as part of {T152230}.
+
+{F5229438}",1483554630,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"No, this is for editing TemplateData blocks nicely once we enable Template: namespace editing in VE (and the 2017 wikitext editor).",1476984711,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,We created a template data editor a few years ago.,1476640713,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"I've translated the script to enwiki : http://en.wikipedia.org/wiki/User:NicoV/TemplateDataEditor
+
+and made a screenshot in Commons : http://commons.wikimedia.org/wiki/File:TemplateDataEditor.png",1374308029,PHID-USER-o34e5i3eq4nstbvcf26w,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"Created attachment 12786
+Screenshot of the form provided by the user script from frwiki
+
+(In reply to comment #2)
+> A user on fr.wikipedia seems to have developed a user script to easily add
+> TemplateData to a template:
+> https://fr.wikipedia.org/wiki/Utilisateur:Ltrlg/scripts/TemplateDataEditor.js
+> 
+> This might be of interest while developing a similar VE module.
+
+For convenience, I've attached a screenshot of the form generated by that script.
+
+**Attached**: {F11686}",1373295643,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"A user on fr.wikipedia seems to have developed a user script to easily add TemplateData to a template:
+https://fr.wikipedia.org/wiki/Utilisateur:Ltrlg/scripts/TemplateDataEditor.js
+
+This might be of interest while developing a similar VE module.",1373293342,PHID-USER-z6nzrwuaij3spgyg23jt,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,See also bug 50370 comment 1.,1372535975,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],"A retread of bug 42847 for issues in the run-up to wider deployment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372053120,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nsv64fqtru36njpwa54p,task_description,invalid
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],Now replaced by https://phabricator.wikimedia.org/maniphest/query/V25BI8.HgRPz/#R instead.,1423674480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nsv64fqtru36njpwa54p,task_subcomment,NA
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],"Change 155841 merged by jenkins-bot:
+Greylist IE11
+
+https://gerrit.wikimedia.org/r/155841",1409263118,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nsv64fqtru36njpwa54p,task_subcomment,NA
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],"Change 155841 had a related patch set uploaded by Jforrester:
+[WIP] Greylist IE11
+
+https://gerrit.wikimedia.org/r/155841",1409099824,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-nsv64fqtru36njpwa54p,task_subcomment,NA
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],*** Bug 65688 has been marked as a duplicate of this bug. ***,1400868288,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-nsv64fqtru36njpwa54p,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikimedia wikis,"One of our long-term objectives is for VisualEditor to be enabled by default on all (public) Wikimedia wikis; this is a tracker for that ambition.
+
+As of August 2016, it isn't likely to be completed anytime soon, because some projects differ substantially from the Wikipedia use case for which VE has been primarily designed. For example, Wiktionary pages tend to be composed almost entirely of templates.",1371860160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-r5vx4pebxayyrkdqlagy,task_description,open
+Enable VisualEditor by default for all users of all Wikimedia wikis,"@Jdforrester-wmf, you are proposing to work on this task during the Wikimedia Hackathon in Lyon. Please consider associating this task or the specific related task(s) with #Wikimedia-Hackathon-2015.",1424384875,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-r5vx4pebxayyrkdqlagy,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikimedia wikis,"Change 71259 merged by jenkins-bot:
+Add ability to disable for anonymous users
+
+https://gerrit.wikimedia.org/r/71259",1372564644,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r5vx4pebxayyrkdqlagy,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikimedia wikis,"Change 71259 had a related patch set uploaded by Jforrester:
+Add ability to disable for anonymous users
+
+https://gerrit.wikimedia.org/r/71259",1372560612,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-r5vx4pebxayyrkdqlagy,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikimedia wikis,OMG. It's bug number 50000.,1371861883,PHID-USER-r7wrkcx7j2vutqs6hr3g,PHID-TASK-r5vx4pebxayyrkdqlagy,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,Current deployments listed at [[https://www.mediawiki.org/wiki/VisualEditor/Rollouts|mw:VisualEditor/Rollouts]].,1371860160,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-io6eogshz2s3ntb5ae7u,task_description,open
+Enable VisualEditor by default for all users of all Wikipedias,"Volunteers, across experience levels, benefiting from the positive impact [Reference Edit Check](https://www.mediawiki.org/wiki/Edit_check) has been [proven to cause ](https://phabricator.wikimedia.org/T342930#9753996) relates to how easily newcomers can access VE. Thus, why I'm relating this ticket to T331946.",1715626643,PHID-USER-7x5ai23ne5qampjf3g7r,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,">>! In T51999#2735651, @Liuxinyu970226 wrote:
+> What about Dutch, that's the only Phase 1 wiki that still haven't done?
+
+Will create a task.",1490411970,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"What about Dutch, that's the only Phase 1 wiki that still haven't done?",1477095772,PHID-USER-chrmcih5qjpx5buo7vx6,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"Change 102208 merged by jenkins-bot:
+Enable VisualEditor by default on ""phase 4"" Wikipedias
+
+https://gerrit.wikimedia.org/r/102208",1389635422,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"Change 102208 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on ""phase 4"" Wikipedias
+
+https://gerrit.wikimedia.org/r/102208",1387306106,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"Change 96473 merged by jenkins-bot:
+Enable VisualEditor as default to ""phase 3"" Wikipedias
+
+https://gerrit.wikimedia.org/r/96473",1386021517,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"Change 96473 had a related patch set uploaded by Catrope:
+Deploy VisualEditor as default to ""phase 3"" Wikipedias
+
+https://gerrit.wikimedia.org/r/96473",1384948485,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,*** Bug 54866 has been marked as a duplicate of this bug. ***,1380835091,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"###Problem
+There are various workflows where a user wants to both interact with (or at least see) a page's content, and also interact with a potentially complicated form/process, which may have many controls/inputs.
+
+Some VisualEditor examples:
+ - Adding/editing categories (T51969#548266)
+ - Adding/editing a template with many parameters
+Some non-VE examples:
+ - Rater dialog (T51969#2847958)
+ - [[https://en.wikipedia.org/wiki/Wikipedia:Twinkle|Twinkle]] dialogs ([[https://github.com/azatoth/twinkle/issues/414]])
+
+###Feature request
+Dialogs that have no need to be modal (intended to interrupt the primary workflow, and requiring some action before you can get back to the primary workflow) should be draggable.
+Gadget/script/other developers using OOUI should have a simple way to enable this feature, e.g. a config setting that can be set to `true` to allow dragging.
+
+Some specific workflows may have viable alternatives to dialogs, e.g. {T52239}, but that doesn't solve the general problem for more complicated dialog-based workflows.
+
+###Initial task description
+Quoth requester: If I can't read the article, because the ""page settings"" box is large and un-draggable and hides all the article, how can I see what defaultsort or categories I want to add (especially as for defaultsort I probably want to copy and paste all or part of the article title).
+",1371833520,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-g55t2yyhma4clcxdjjey,task_description,open
+OOUI: Dialogs should be repositionable/draggable,"The previous comments don't explain who or what (task?) exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status, as tasks should not be stalled (and then potentially forgotten) for six years for unclear reasons.
+
+//(Smallprint, as general orientation for task management:
+If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead.
+If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}.
+If this task is stalled on an upstream project, then the #upstream tag should be added.
+If this task requires info from the task reporter, then there should be instructions which info is needed.
+If this task needs retesting, then the #testme tag should be added.
+If this task is out of scope and nobody should ever work on this, or nobody else managed to reproduce the situation described here, then it should have the ""Declined"" status.
+If the task is valid but should not appear on some team's workboard, then the team project tag should be removed while the task has another active project tag.)//
+",1604263339,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#5669037, @John_Broughton wrote:
+> (b) let's find specific solutions to specific user problems that don't require that approach.
+
+Sure, but shouldn't they be discussed in more specific tasks? This task is for OOUI in general, which is used for more than just VisualEditor.",1573957456,PHID-USER-sesl3h225nhd3px7w7bu,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Regarding ""Your idea also doesn't seem to relate to dialogs where information is being input from multiple different places in the article"", I'm not proposing this for all situations. In fact, I'm primarily interested in getting some action on the problem of more easily adding categories to articles.
+
+And yes, it's true that some categories won't be have related text in the article. For that, one option is to leave the current menu-driven process as is (there isn't anything wrong with having two ways to do the same thing). Another option, of course, is for the user to select some (irrelevant) text, then when the dialog box occurs, change that text to whatever he/she wants as a category. (The selected text wouldn't be locked in any way, just as text selected to create a link can be changed by the user, in the dialog box.)
+
+Again, my larger points are (a) if a moveable dialog box is either difficult to implement or undesirable from a UI/UX viewpoint, then (b) let's find specific solutions to specific user problems that don't require that approach.",1573924342,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I'm now totally unfamiliar with VE because I abandoned it years ago because I found it unusable. I simply wanted to be able to move the category input box away from being on top of the info I needed to categorise, which might have been a county name for a locality, or a footballer's birth decade and field position, etc. It seems, to a naive editor, a simple request.
+Sent from Yahoo Mail on Android",1573919054,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"@John_Broughton that seems to be assuming that the category name will appear as text somewhere in the article, but that will not always be the case. For example [[ https://en.wikipedia.org/wiki/List_of_pear_cultivars | List of pear cultivars ]] is in Category:Lists of foods. The words ""Lists"" and ""foods"" appear nowhere on the page other than the category names, even ""food"" appears only in the link to a portal and in the title of one reference and neither are in close proximity to any instance of the word ""list"". I imagine this will be even worse in languages where plurals are formed differently than in English.
+
+Your idea also doesn't seem to relate to dialogs where information is being input from multiple different places in the article. 
+
+Back in May 2017 I commented:
+> I wouldn't object to dockable diaglogs appearing like that at the bottom of the screen as an option, but simply being able to move a reasonably sized box around the screen to a convenient point for the task at hand would be vastly superior imo.
+@Spinningspark replied
+>Yes, that exactly sums up the issues.  A moveable window is the best solution. The issue is being clouded with these alternative solutions and we have ended up with no solution at all.
+We don't seem to have moved on at all in the last 2½ years. ",1573913438,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I haven't thought this through, but, for example, to add a category to Wikipedia page, one could (1) select some text, and (2) tell VE that you want that text to be a category.  The process would be similar to linking, where one selects text and then clicks on the link icon. 
+
+The linking process works really well in VE because the link icon is one click away from the text being edited, while categories are a menu choice, so two clicks away. But I doubt that anyone would complain about the extra click if setting up a category was almost as easy a process as creating a link.
+
+Still, if one wants to dream about an even easier interface, it would be this:
+
+(a) select some text
+(b) a palette window automatically appears (relatively small, perhaps, since the editor might be selecting text to copy, move, or delete)
+(c) click on an icon in the palette window to select a relevant action from the palette window (which might be expanded with a click, maybe showing the selected text in an attached window). The relevant options could include create a link, create a category, format the text as a heading, format a paragraph (block quote), format some text within a paragraph (bold, italic, etc)
+
+In other words, in VE, when you select some text, VE would automatically say ""Okay, here are your options for that text."" [I have no idea how difficult this would be to program.]
+
+",1573840441,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"@John_Broughton, the StackExchange link makes me wonder whether we should be thinking of these as modal dialogs (something intended to interrupt the primary workflow [which is probably ""typing text into the body of an article""] and requiring some action before you can get back to the primary workflow).  Maybe editors would find it better to have a https://en.wikipedia.org/wiki/Palette_window instead.",1573838216,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Given that a user wants to both interact with (or at least see) a page's content, and also interact with a somewhat complicated form/process (i.e. many controls/inputs, e.g. Rater, or in VE adding/editing a template with many parameters), what alternatives are there?
+ - Unmovable dialog: Forces the user to swicth back-and-forth to another tab/window; or exit the dialog, find what they wanted to find, and go back in
+ - Docking: Only works if your screen is big enough
+ - Prepending to (or placing just above) the content area: Causes content to re-position, can't necessarily see both things at once (if scrolling is required), not really suitable if the form/process applies to only one section of the page
+ - Appending to (or placing just below) the content area: Similar to prepending, but instead content re-positioning existing content, the form/process won't initially be visible on longer pages, unless you force the page to scroll there
+I don't think those alternatives are actually better than letting the user move the dialog out of the way.",1573803105,PHID-USER-sesl3h225nhd3px7w7bu,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"https://ux.stackexchange.com/questions/81134/should-modal-dialogs-be-movable seems to show a (rough) consensus that when a proposed solution to a dialog is to make it moveable, the dialog itself is poorly designed. That implies looking for a different solution that addresses the underlying user problem. 
+
+For example, when in VE, and wanting to create a category, the dialog could include the text of the section where the pointer was located when the dialog was invoked (scrollable on the left side of the dialog). That way, the user could selected text from the left side of the dialog and paste it into the right side. [I'm not arguing that this is optimal, just that it's another way to solve the underlying user problem.]",1573599401,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"FYI, I found I could do the draggability easily enough without the library, just using mouse/pointer events directly - [[https://github.com/evad37/rater/commit/a510709e8eb61389e0d83faca7750215affb1f9c|diff]].",1573580066,PHID-USER-sesl3h225nhd3px7w7bu,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I've implemented draggability for an OOUI process dialog for the latest version of my [[ https://github.com/evad37/rater | Rater script]], by [[ https://github.com/evad37/rater/commit/0ef3d7eca0a2417550030ceac9219265dbcbdf5b | using a drag-and-drop library ]] and [[ https://github.com/evad37/rater/blob/f0ca4cdbbfca6529bbe235e2f8d8b3f626bcc18d/rater-src/css.js#L31 | some CSS overrides]]. It would be nicer if this functionality was directly supported, rather than relying on a library with a bunch of functionality that isn't actually used -- at least for reusers of OOUI, even if WMF devs choose not to use it.
+
+(Coincidentally, this is the exact use-case @Gryllida was describing above three years ago.)",1573488532,PHID-USER-sesl3h225nhd3px7w7bu,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#3224607, @Thryduulf wrote:
+> When editing in VE I sometimes have to load a duplicate copy of the page in a new tab so that I can see what I'm doing.
+> 
+> I dislike the split-screen approach as that uses more screen estate than required and divorces the dialog from its context. I wouldn't object to dockable diaglogs appearing like that at the bottom of the screen as an option, but simply being able to move a reasonably sized box around the screen to a convenient point for the task at hand would be vastly superior imo.
+
+Yes, that exactly sums up the issues.  A moveable window is the best solution.  The issue is being clouded with these alternative solutions and we have ended up with no solution at all.",1493641919,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"When editing in VE I sometimes have to load a duplicate copy of the page in a new tab so that I can see what I'm doing.
+
+I dislike the split-screen approach as that uses more screen estate than required and divorces the dialog from its context. I wouldn't object to dockable diaglogs appearing like that at the bottom of the screen as an option, but simply being able to move a reasonably sized box around the screen to a convenient point for the task at hand would be vastly superior imo.",1493598817,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Three and a half years on from my initial complaint, and as far as I know the Visual Editor is still useless to me, so I don't use it. Let me know when it becomes a useful editing system for people who need to see the original article while adding categories or doing other tasks.",1493224533,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,I still think something like a split-screen mode would be a better solution for these cases than movable dialogs (see mockup above in T51969#821409).,1493220892,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Yes - when someone tells me that VE is usable, I'll have another look at it. If the dialog box still obscures the content, then for my prolific WikiGnoming it's useless. Two years since I raised this, and no progress. Nice to feel appreciated. ",1481018430,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Astonishing this is still open.  I stopped using VE a year or two back because this and other problems made for an inefficient worklow.  Still not time to give it another try I see.,1481016428,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I appreciate this discussion happening. It is strange that we are thinking that draggable dialogs create problems, so I will attempt to illustrate it with a use-case. I am trying to write a user script in oojs-ui, and the script work should be similar to the old gadget whose dialog is draggable to expose different parts of the article text in order to perform its assessment.
+
+Here is the gadget documentation and source code: https://en.wikipedia.org/wiki/User:Kephir/gadgets/rater
+
+Here is a screenshot attached, which I also uploaded to Commons and which is found at the gadget documentation page:
+
+{F4983945}
+
+I would like to be able to perform article rating on the new pages queue continuously one after another, and having draggable dialog reduces the working memory (and increases efficiency) of the process about tenfold, as I don't have to hold the article contents in my memory.",1480961860,PHID-USER-aklqcs2xae5ghg6icqmd,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I agree that the dockable model is trying to modify something where we might better look for alternatives. For example, one way to create a new category might be to highlight some text, then select (say) Insert > Category. That could open a dialog (for example, to  allow a different sort key than the default, and to offer the opportunity to create a category if one being created didn't already exist.
+
+This isn't perfect, of course - if a particular category didn't exist (as text) on the page, the user would have to add it, create the category, then delete the unneeded text. Still, maybe it's better, and at least it's something to think about.",1418179696,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#821409, @matmarex wrote:
+> I'm increasingly convinced that draggable dialogs in general are a solution in search of a problem. (It could be interesting to do, but shouldn't be applied to all dialogs.)
+> 
+>> You're saying that I've got a problem with my workflow: how else do you suggest that I add a category, a stub template, or a DEFAULTSORT to an article, if I can't read the text of the article? I could copy and paste the entire article content into a notepad, so that I could refer to it ... hardly seems reasonable.
+> 
+> I was thinking, perhaps the dialogs should be ""dockable"" at the bottom of the screen? Clicking an icon on dialog's title bar would hide the white overlay and dock it, revealing article content. We should think what to do with dialogs that were modal in this case, but I think this approach could work, and could work a lot better than clunky dragging of dialogs (which are often way too large for dragging to make sense, as they would cover most of the content anyway even when dragged aside).
+> 
+> Here's a rough mockup – note the docking icon on the right. Thoughts?
+
+Eurgh. I really don't like the dockable model of modals. It feels like failure. I'd prefer instead that we provide secondary non-modal ways to do things people want to do that isn't modal. As @Whatamidoing-WMF says, this isn't going to work for anyone that doesn't have a huge desktop screen to use.",1418176632,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#835122, @TrevorParscal wrote:
+> In my view, editing categories should not be a modal experience.
+
+Not **necessarily** modal. The HotCat gadget that this partially replaces is already effectively-modal too, for instance.
+
+> The category editor should simply be embedded at the bottom of the page in place of the category listing.
+
+That's {T52239}.
+
+",1418176524,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#548465, @PamD wrote:
+> (In reply to Trevor Parscal from comment #22)
+>> I would like to avoid adding moving and resizing to dialogs, because I
+>> believe it solving the problem in the wrong way. At it's root, this is a
+>> workflow problem. Making the dialog resizable and movable does not
+>> adequately address it.
+>> 
+>>....
+> 
+> You're saying that I've got a problem with my workflow: how else do you suggest that I add a category, a stub template, or a DEFAULTSORT to an article, if I can't read the text of the article? I could copy and paste the entire article content into a notepad, so that I could refer to it ... hardly seems reasonable.
+
+I am not saying it's a problem with YOUR workflow, I'm saying it's a problem with the workflow we are providing you. I'm admitting we have failed you, and because we didn't understand how you actually use the software we modeled the workflow around our imagined way you might use the software.
+
+In my view, editing categories should not be a modal experience. The category editor should simply be embedded at the bottom of the page in place of the category listing. If we do anything to try and get the dialog out of the way temporarily, we will still not be able to let you select text behind the dialog without breaking the entire concept of a modal dialog. By placing the category editor at the bottom, you are free to scroll around and select whatever you like. This is the experience you have with the Wikitext editor, and there's no reason we can't continue to provide it.",1418163779,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Making the dialog one-third the width of the screen is only going to make sense on a desktop system.  One third the width of a smartphone screen is not going to be functional (the entire dialog box would be a couple of centimeters wide).,1418010994,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"The discussion is complicated by the unnecessary ""Options"" menu on the left side of the dialog box. (I believe this is the **only** place in VE where selecting a choice from a top menu results in a dialog box that shows all the other choices on that menu; that would make sense if an editor were likely to want to do two or three page-related things at once, but in fact he/she almost certainly does *not*.) While redoing the entire approach to how the three-line (should be ""Page"") menu choices work is probably outside the scope of this topic, I will note that what the requester needs (access to all the text on the page, *while* the dialog is open) is applicable only to **two choices** - categories and default sort. 
+
+For those two menu choices, categories and default sort, I suggest that the dialog attach itself to the **right side** of the window, taking up 1/3 of the width of the window, and that the left side - the text on the page - be scrollable. (If it's easier to program, then perhaps the dialog should be attached on the left, with the scrolling done on the right.) For the other menu choices, a normal modal dialog box is fine.",1417811550,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#821594, @PamD wrote:
+>I don't know the term ""dock""  but I think you mean what I'd call ""minimise""? 
+
+No, dock does not mean the same as minimise.  Docking is fixing the dialogue to one edge of the window, rather than plonking a popup in the middle of the window.  In the mockup example the dialogue is docked to the bottom of the window.  Applications often give the user a choice of which edge they want to dock to, but I don't know if that is what is propsoed here.
+
+For me, this would work if the window could still be scrolled while the dialogue was open, thus uncovering any content hidden by the dialogue (or even off the boundary of the window at the time the dialogue was invoked).
+",1417802087,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Looks as if it might work: I don't know the term ""dock""  but I think you mean what I'd call ""minimise""? So click on that icon, the dialog box shrinks to an icon, I read what's behind it: I hope I can copy text from it, eg to fix a DEFAULTSORT? Then click on the icon to restore the dialogue box and carry on. Yes, could be a great solution. Probably better than my original suggestion, many moons ago, of dragging or resizing.  Thanks.",1417799263,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Indeed, but in this use case you then have to drag it back on-screen to input the category name or whatever.",1417793086,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#821409, @matmarex wrote:
+> ...and could work a lot better than clunky dragging of dialogs (which are often way too large for dragging to make sense, as they would cover most of the content anyway even when dragged aside).
+
+Even if the dialog window is very large, it can still be pushed out of the way by dragging it until it is nearly completely off screen.
+",1417793032,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I'm increasingly convinced that draggable dialogs in general are a solution in search of a problem. (It could be interesting to do, but shouldn't be applied to all dialogs.)
+
+> You're saying that I've got a problem with my workflow: how else do you suggest that I add a category, a stub template, or a DEFAULTSORT to an article, if I can't read the text of the article? I could copy and paste the entire article content into a notepad, so that I could refer to it ... hardly seems reasonable.
+
+I was thinking, perhaps the dialogs should be ""dockable"" at the bottom of the screen? Clicking an icon on dialog's title bar would hide the white overlay and dock it, revealing article content. We should think what to do with dialogs that were modal in this case, but I think this approach could work, and could work a lot better than clunky dragging of dialogs (which are often way too large for dragging to make sense, as they would cover most of the content anyway even when dragged aside).
+
+Here's a rough mockup – note the docking icon on the right. Thoughts?
+
+{F19025,size=full}",1417792226,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to Trevor Parscal from comment #22)
+> I would like to avoid adding moving and resizing to dialogs, because I
+> believe it solving the problem in the wrong way. At it's root, this is a
+> workflow problem. Making the dialog resizable and movable does not
+> adequately address it.
+> 
+>....
+
+You're saying that I've got a problem with my workflow: how else do you suggest that I add a category, a stub template, or a DEFAULTSORT to an article, if I can't read the text of the article? I could copy and paste the entire article content into a notepad, so that I could refer to it ... hardly seems reasonable.
+
+If I want to add a stub template for a Russian footballer, and then discover that not only do I need {{Russia-footy-defender-stub}} but that it's subdivided by date of birth, I need to be able to look at the article and find his date of birth to use {{Russia-footy-defender-1960s-stub}}.  If I want to add a defaultsort, I need to be able to copy the surname, and then the forename, from the text of the article. How should I adjust my workflow?
+
+For the foreseeable future, I've adjusted my workflow by abandoning any attempt to use VE as it makes my editing too difficult.",1414347353,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to Trevor Parscal from comment #22)
+> I would like to avoid adding moving and resizing to dialogs, because I
+> believe it solving the problem in the wrong way. At it's root, this is a
+> workflow problem. Making the dialog resizable and movable does not
+> adequately address it.
+> 
+> More of these processes should be non-modal, especially authoring edit
+> summaries. This would allow users to contribute to edit summaries as they
+> work, rather than having to write them at the very end, when the changes
+> they've made are so temporally distant.
+> 
+> Even if the dialog is movable an resizable and movable, the contents below
+> are only visible through a semi-opaque mask and the contents cannot be
+> scrolled because the modal dialog is capturing events (on purpose, it's
+> modal).
+
+This is a good point, but I dont think, its related to this enhencment. You are right, that if I am doing a lot of different changes and/or editing the article several minutes, I forgot, what I was doing. But how this problem is related to the fact, I cannost drag the DW avay to see what is behind?",1414336477,PHID-USER-vm462i2ffbawnuo4mh3n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I would like to avoid adding moving and resizing to dialogs, because I believe it solving the problem in the wrong way. At it's root, this is a workflow problem. Making the dialog resizable and movable does not adequately address it.
+
+More of these processes should be non-modal, especially authoring edit summaries. This would allow users to contribute to edit summaries as they work, rather than having to write them at the very end, when the changes they've made are so temporally distant.
+
+Even if the dialog is movable an resizable and movable, the contents below are only visible through a semi-opaque mask and the contents cannot be scrolled because the modal dialog is capturing events (on purpose, it's modal).",1413922302,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"> You can't edit anything, tables, Chinese or galleries, 
+> if there is big immovable box in the way.
+
+This isn't really true:  you can close the box.  With the box open (and movable), you can *see* the content on the page, but you still can't edit it.  When you've got a dialog box open, but all your typing ends up on the page underneath the box, then we call that a bug.
+
+The problem here is that (depending on the size of the box and the exact location of your cursor when you open it), what you need to *see* on the page might be covered up by the box.  ""Open box, realize that you've forgotten how to spell something, realize that the box is covering up that word, close box, check spelling, open box again, finally type"" is not as efficient as ""Open box, drag it out of the way, start typing"".",1407787535,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to James Forrester from comment #18)
+> (In reply to Spinningspark from comment #17)
+> > Why is this languishing at low priority? Fixing something that is preventing
+> > the editor from reading the thing he is editing is HIGH priority.
+> 
+> ""High"" priority would mean that it's more important than editing tables,
+> editing in Chinese, or editing galleries. ""High"" priority is not appropriate
+> for this relatively minor and very complex enhancement request.
+
+You can't edit anything, tables, Chinese or galleries, if there is big immovable box in the way.",1407777158,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Just to be clear, this is a DESIGN TEAM problem, because it's a problem with the OOjs UI, which VE uses, but which is under the control of the Design team. The issue is that the OOjs UI WindowManager lacks a resizing event. That issue affects every use of windows in the OOjs UI, not just VE's use of windows.
+
+Why isn't this bug showing on the list of problems that the Design Team is considering (https://bugzilla.wikimedia.org/buglist.cgi?keywords=design&keywords_type=allwords&list_id=335932&order=changeddate%20DESC%2Cvotes%20DESC%2Cpriority%2Cbug_status%20DESC%2Cassigned_to%2Cbug_id&query_format=advanced&resolution=--- )? (I got that list via https://www.mediawiki.org/wiki/Design ) 
+
+Relatedly, why is the priority for fixing this bug being set by the VE team, rather than by the Design team?",1407776333,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to Spinningspark from comment #17)
+> Why is this languishing at low priority? Fixing something that is preventing
+> the editor from reading the thing he is editing is HIGH priority.
+
+""High"" priority would mean that it's more important than editing tables, editing in Chinese, or editing galleries. ""High"" priority is not appropriate for this relatively minor and very complex enhancement request.",1407771922,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Why is this languishing at low priority? Fixing something that is preventing the editor from reading the thing he is editing is HIGH priority.,1407759592,PHID-USER-imut7wxehhy35ukuzaks,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,*** Bug 67952 has been marked as a duplicate of this bug. ***,1405474879,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Moving to the OOjs UI product as that code is now shared.,1387222480,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Please see https://upload.wikimedia.org/wikipedia/commons/d/d9/Wide_edit_window_%28Proposal_for_Wikimedia_VisualEditor%29.png for an example of what a wide window might look like for reviewing changes.,1387216858,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"The change review window is also too small to be useful for some editors, especially if a lot of changes have been made.",1385605063,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Understandable. You will receive a bugmail notification once this bug report is fixed.,1382574004,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Let me know when this is fixed, because I'm not going to stress myself by using VE until then - it just makes my everyday editing too much like hard work. When it's fixed (and perhaps a few more of my long-standing complaints - hidden comments, red links appearing as red, etc), I might carry on with debugging your system. Till then, why should I bother?",1382566037,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to comment #9)
+> Two months since there's been any comment on this ... I admit I've pretty
+> much
+> given up using VE (too tedious because of this and other problems, plus some
+> stuff going on in Real Life which makes me want to reduce Wikistress). Any
+> chance of it getting fixed some time? I'm sure I'm not the only person
+> affected.
+
+Some time? Yes. Soon? No. In my view, it's not as important as fixing things like copy-and-paste or adding citation template quick-add support or editing tables.",1380756245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Two months since there's been any comment on this ... I admit I've pretty much given up using VE (too tedious because of this and other problems, plus some stuff going on in Real Life which makes me want to reduce Wikistress). Any chance of it getting fixed some time? I'm sure I'm not the only person affected.",1380755973,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Prioritisation of work is done on how much it interferes with people using the software, not how long ago it was first mentioned as an issue. For example, bug 4 (!) is from 2004.
+
+I'm sorry that this is getting in the way of your use of VisualEditor, but I think that adding copy and paste support (for example) should happen first. I could ""upgrade"" the importance of this to ""high"" but it wouldn't get the code written any faster. :-(",1375472653,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Six weeks on from first request it's depressing to see this is still ""low enhancement"". Example: stub-sorting a Russian icehockey player, I open the dialog box to remove the existing stub tag and then go to the dropdown menu to add ""Russia-icehockey-bio-stub"", only to discover that there are separate stubs for wingers, goalies, etc. I didn't notice what he was.  I have to quit the dialog box, find he's a winger, re-open it, re-delete the old stub, return to the dropdown menu to add the new stub template.  The inability to move or shrink the dialogue box makes ordinary routine wikignoming harder work. But I suppose the target market of newbies don't do things like that, and we established editors can be trusted to struggle on regardless (some of us, perhaps a diminishing number), however ignored our needs may be?  
+
+Yes, I could abandon VE and this wouldn't trouble me any more, but I'm trying to help by persevering in using it to help you debug it. In return, how about a little attention to one of the first issues I raised?",1375470897,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"How hard is it to make the dialog box moveable? Really? There is what, one parameter that needs to be changed? If this were a really hard problem, it would be understandable that the VE team was deferring this for more important things. But it's not that hard (I hope; if so, that bodes poorly for VE), and it impacts LOTS of editors. Yes, it affects the dialog box for page settings, when doing categories. But there is the identical problem when adding a caption for an image (Media settings dialog; might want to know how something in the article is spelled) and possibly for the other dialog boxes (for example, in the Media dialog, searching for an image where the search term has an unusual spelling).
+
+Even better would be the ability to copy/paste from the main editing window to a field in the dialog box. I realize that has potential ramifications for loss of focus - it would be undesirable for the dialog box to disappear *behind* the main editing window. Still, in Mac OS X, the ""Force Quit Applications"" dialog box is moveable, and the user is able to copy text from other windows, but the dialog box remains on top of every window until it is closed. (Excessive, actually: the ideal is to have the VE dialog box float on top of the main editing window, ONLY.)
+
+But we (as in, Wikipedia editors) would settle for a really minimal solution, initially - just make the dialog boxes moveable. Please?",1374967939,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Any movement on this? Low-priority according to the development team, I accept, but it's a pretty important chunk of the editing workflow for a lot of tasks.",1373882058,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"If I want to add ""Category:1917 births"" and ""Category 1987 deaths"" to an article, is it undesirable multitasking to expect to be able to see the lead sentence which says ""'''Joe Bloggs (1917-1987)..."", rather than having to remember the two dates? Or if I want to assign ""Category:Villages in ..."" for some area whose placenames are unfamiliar and have difficult spellings? Please let me see the article while adding categories: a simple way would be to let me drag, or shrink, the dialogue box which at present totally obscures the article text. (I was the original reporter of this bug on 21 June, and the response above seems to misunderstand its importance.)",1372628541,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to comment #1)
+> The idea of the dialog being modal is that you aren't multi-tasking with it
+> at all.
+
+This isn't asking for multi-tasking, it's asking for the ability to drag the dialog out of the way so that you can get context for the single-tasking, err, task. :-)",1371835847,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Makes sense.,1371835810,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"The idea of the dialog being modal is that you aren't multi-tasking with it at all.
+
+As far as adding a category or changing the default sort of a category directly from some other mode (such as reading, or editing paragraph text) we should look at those workflows rather than dissolve the intentional model-ness of the dialog.
+
+For example:
+
+- Perhaps categories could be edited at the bottom of the page, rather than inside a dialog.
+- Maybe the category editor could use some other kind of UI container that isn't modal.
+
+etc.",1371835724,PHID-USER-mpfqwllylfkzpcgkdkvc,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","When in the template editing dialog, a link going to the [template:name] page, would be really helpful for:
+* Reading detailed documentation
+* Easy access to (edit or examine) template source code
+
+**See Also**:
+* {T52354}
+* {T52656}
+* {T53311}",1371589200,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-axbu733atg4fftym2lek,task_description,resolved
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","Change 257443 merged by jenkins-bot:
+MWTemplatePage: Show a link to the template even when there's a description
+
+[[https://gerrit.wikimedia.org/r/257443]]",1482231864,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","Change 257443 had a related patch set uploaded (by Jforrester):
+MWTemplatePage: Show a link to the template even when there's a description
+
+[[https://gerrit.wikimedia.org/r/257443]]
+",1449525412,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","Exists templates with variable parameter names. If you create a tTD for a part of the parameters, then it just do not describe the other part of parameters and disappear link to the documentation. eg https://ru.wikipedia.org/wiki/Ш:Familytree",1441449224,PHID-USER-5joeladhczukimiv4rwl,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","MediaWiki doesn't enforce any particular page being a documentation page, it's a thing made up by users.",1414817959,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","If this wasn't clear enough, the user asks for a link to the template /documentation/ page.
+Here's another example of the need to access documentation page:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67986#c1
+If the user doesn't read the template's manual, he currently has no way to guess that there may be several required parameters and which ones he needs to fill for the template to work correctly.",1405348985,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","This is being asked at ru.wp even for templates which have TemplateData info;
+quoting the reasoning, the user wants to be able to access:
+-full template documentation 
+-see more examples of which are difficult to describe in words 
+-read about other similar templates 
+-edit template data.",1405346626,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","This was done two months ago for templates which lack documentation; I'm closing this as a ""WORKSFORME"" at this point, as if the user has to go read the template's page to understand what the documentation is telling them, the creator of the documentation has utterly failed.",1399324925,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","This bug seems to have strayed/widened far from the original simple request (which I remember also making on the feedback page at some point many days ago): when one is adding a template (""transclusion""), a button to link to the template page would be very useful - to be able to read all the detailed description there. Look at [[Template:Genukiwry]] as an example - it couldn't all be coded up into TemplateData, but it could be made accessible by providing a simple link which would open in a new tab / new window / popup (ie anything which wouldn't spoil the ongoing editing operation). This facility would be an area where VE could provide a better editing experience than Edit Source, and surely wouldn't need a huge programming effort.",1373999921,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","I googled ""mediawiki glossary"" and found this: 
+*[[mw:Manual:Glossary]] - now bookmarked. :)
+
+I am not using ""parameter"" correctly in the context of MediaWiki. I couldn't find ""parser"" listed in the glossary. :)
+
+My point with both bugs is to get links to the template pages so that people can edit them in wikitext source mode there on the template page. Nothing more. I am not interested in being able to edit templates within VE at all. 
+
+In fact, With the exception of reference templates I think editing of templates within VE should be disabled since it is not WYSIWYG, and only adds a new layer of abstraction. I think the only thing that should be provided by VE is a link to the template page. 
+
+If an editor of Wikipedia like me with 26,000 edits does not understand the terms (parameter) used in VE template editing, then imagine the difficulty new editors have when they see those terms listed in VE template editing. 
+
+I would like VE mainly to do text editing and references. Nothing more for now. I think people would be ecstatic with that. Since there are so many reference templates, I think that alone may require an increase in the number of paid full-time developers assigned to VE. 
+
+I actually understand a lot about table editing and template editing, but only at the wikitext editing level. I can do it, but not always explain it, since my knowledge mostly comes from hacking at it over the years. :) I help edit this page:
+*[[Help:Sorting]]",1371717599,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","(In reply to comment #1)
+> Here is a page that has a table and a couple transcluded navigation-box
+> templates at the bottom:
+> [[List of countries by incarceration rate]]
+> 
+> With VisualEditor (VE) the table is editable and WYSIWYG.
+
+(Yay. :-))
+
+> But with VE the existing text in the 2 navigation boxes can not be edited as
+> far as I can tell. At least not within VE from that page. I am talking about
+> after clicking the edit icons for the navigation boxes.
+
+Yes, VisualEditor is disabled for the Template namespace, and likely will be for a very long time (or forever). It's mostly used for very complicated transclusion wikicode which often can't be edited visually, because it doesn't form a complete document, only part of one.
+
+> New parameters can be added to one of the templates, but not to the other. I
+> don't see a way to edit the text for existing parameters in either navigation
+> box. 
+
+I'm a bit lost here - you mean parameters on [[List of countries by incarceration rate]]'s invocations of [[Template:Incarceration]] and [[Template:Law country lists]]? Those templates take no parameters, though it's possible to add new parameters to template invocations that don't currently have one - see my edit (actually two edits) with VisualEditor here: https://en.wikipedia.org/w/index.php?title=List_of_countries_by_incarceration_rate&diff=560637005&oldid=559696805
+
+> So to be able to edit one of those templates in source mode or otherwise it
+> would be helpful to have a direct link to the transcluded template page, and
+> not to the many templates that make up such a navigation box at the core
+> level. 
+
+You can definitely edit those templates in source mode still - do you mean, edit the invocation of those templates? You should be able to replicate anything you can do with a template invocation in source mode using VisualEditor at this point. On the other hand, trying to offer ""edit the source of this template invocation"" is extremely technically hard (as well as being a very complicated user interface issue for users).
+
+> See related bug 878.
+
+I'm afraid I don't see how that bug, about the wikitext editor's additional listing of templates used on section editing, is related. Could you explain the link?
+
+I also don't see how this relates to this bug, which is a minor enhancement request to add a link to the used template on the template's pane (which I think is fine, but we'll have to work out if we can do this in all situations - what do we do when the ""template"" you're using is in fact a parser function? - etc.).",1371665278,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","Here is a page that has a table and a couple transcluded navigation-box templates at the bottom:
+[[List of countries by incarceration rate]]
+
+With VisualEditor (VE) the table is editable and WYSIWYG.
+
+But with VE the existing text in the 2 navigation boxes can not be edited as far as I can tell. At least not within VE from that page. I am talking about after clicking the edit icons for the navigation boxes. 
+
+New parameters can be added to one of the templates, but not to the other. I don't see a way to edit the text for existing parameters in either navigation box. 
+
+So to be able to edit one of those templates in source mode or otherwise it would be helpful to have a direct link to the transcluded template page, and not to the many templates that make up such a navigation box at the core level. 
+
+See related bug 878.",1371619899,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"This is more of a tracking bug than anything else, but it should be something people are aware of and something that's formally logged; the VisualEditor is very slow on large articles, to the point where it causes confusing output.
+
+Using the example of https://en.wikipedia.org/wiki/OpenOffice - I edited this and it took a good 20 seconds just to render 'review changes', and another 20 to save. David Gerard did the same and the server popped up  ""Error saving data to server: timeout."" with both 'review' and 'save'. Despite this, it saved anyway.
+
+Obviously as a long-term thing: we shouldn't have an editor so slow that someone in an industrialised, Western nation (i.e. the UK) can't make things work.[1] As a short-term thing, we shouldn't be informing users ""something has gone terribly, terribly wrong, abort!"" when it has actually saved.
+
+[1] It's David Gerard, he's not going to be using dial-up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371467880,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_description,invalid
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],Let's use #VisualEditor-Performance instead.,1417556322,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Update on the test Oliver mentions at the top: on the same PC and the same Internet connection (though a current version of Firefox), it just now took:
+
+* 10 seconds to open [[OpenOffice.org]]
+* 176 seconds (nearly three minutes!) to render the ""Review your changes"" diff
+* two minutes attempting to save, then ""Error: Unknown error"". The edit did, however, save: https://en.wikipedia.org/w/index.php?title=OpenOffice.org&diff=597641893&oldid=593809275
+
+It's a ... test subject ... of a page.",1393664271,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"another stopped sript warning
+
+**Attached**: {F11497}",1372621880,PHID-USER-2mkpm2voxepwvz7abjug,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Firefox chokes
+
+This happens /before/ script-stop warnings.
+
+**Attached**: {F11496}",1372621308,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Stopped script warning
+
+**Attached**: {F11495}",1372621284,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"It was previously doing a very dirty diff; I just tried again on this article and it did a clean diff, but timed out when I hit ""save"", three times in a row, and didn't actually save any of them.",1371560422,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"(In reply to comment #3)
+> It may also be worth noting that this page takes ~30 seconds in my use to
+> save when using the ordinary source wikitext editor - it's a complex page!
+
+Yes, one of the problems is that VE being slow is rather more noticeable than MW being slow (because ""it's a website"" and so triggers different time response expectations in users). :-(",1371496866,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],It may also be worth noting that this page takes ~30 seconds in my use to save when using the ordinary source wikitext editor - it's a complex page!,1371495878,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Listing the issues so it's clear what we mean by ""performance issues"" and their different causes and artefacts:
+
+* [network] VE slow to load own JS - mostly provided by ResourceLoader and local cacheing so this would only be a slowness once per user's browser (assuming they don't clear their local cache); we could pre-load VE JS for all users on read, which would reduce load times when people press edit slightly, but that is evil
+
+* [network] VE slow to fetch HTML from Parsoid - mostly fixed due to highly-aggressive caching at our cluster (the payload is slightly smaller in byte size than the read page fetch, i.e. not significant)
+
+* [client] VE slow to render Parsoid HTML into an editable document - we're working on this (profiling etc.), but there's a tension between editability and simplicity of data structure. :-)
+
+* [client] VE slow to respond to user action - same as above; this is the core ""performance"" area for VE itself, of course
+
+* [server] VE slow to get a wikitext diff - this relies on two operations; a Parsoid serialise and an MW wikitext diff: we can work with Parsoid on that being faster, but there's a limit; theoretically we could pre-serialise as we go (but eww network traffic and load on the servers)
+
+* [server] VE slow to save edit - this is essentially the same performance issue as getting the wikitext diff, above; theoretically we could optimise by saving the output of the serialise from a wikitext diff, but this won't be triggered for most users, so it's of marginal utility",1371495451,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Specifically, 8Mbit ADSL through Zen. Most of the slowness appears to be thinking - I could hear my laptop's CPU fan speed up.",1371470989,PHID-USER-gfaq55vdypjmzz6nl2kn,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+VisualEditor: Provide a get-me-into-the-wikitext-editor link on every header inside the VisualEditor,"From [[https://phabricator.wikimedia.org/T50429#518092|a comment]] on T50429.
+
+>It would be wonderful if the ""edit source"" links or icons for sections also showed up inside the Visual Editor. The Visual Editor could treat ""edit source"" links or icons as uneditable links. But the link would still work. So people could click ""edit source"" links or icons to open source editing of a section. 
+>
+> People could go to source mode editing at anytime, even from inside the VisualEditor. That would be so convenient and so useful. Later on, this functionality could be extended to anything the VisualEditor can't edit. People could click on templates, tables, etc. inside the VisualEditor and go directly to source mode editing of that section. Or they could right-click templates, tables, etc. to go to a new tab in source mode for that section.
+
+**See also:**
+T50429
+T51664
+T49779",1371430140,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-cafdsbi6thmpaj3iik3u,task_description,open
+VisualEditor: Provide a get-me-into-the-wikitext-editor link on every header inside the VisualEditor,Is this still relevant now that {T49779} is resolved?,1446661434,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-cafdsbi6thmpaj3iik3u,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","[From bug 48429 comment 20.]
+
+Switching to ""edit source"" tab when VE was triggered via a section-edit link should enter the wikitext editor for that section, rather than the entire page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48429
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49665",1371429960,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qp7cge7h2tflfmzkmov,task_description,invalid
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","In the end we went with bug 49666, which is now done (code to be deployed this afternoon). As discussed above (and I agree), changing behaviour between wikitext section edit behaviour as currently is and the way it works post-VE roll-out - but only on VE-enable-able pages (i.e., not talk pages/etc.) would be complicated and not add value to users.
+
+Consequently, closing this as INVALID.",1372279963,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","Bug 49665 may be another solution: ""VisualEditor: Provide a get-me-into-the-wikitext-editor link on every header"". 
+
+It looks like there will be an ""edit"" link and ""edit source"" link (or icon) on every header.See bug 49666.
+
+If the header ""edit source"" links (or icons) remain clickable (and/or right-clickable) from within VE, then that would be a solution for getting into the source editor for sections.",1371649103,PHID-USER-ebwxbdwkoxprr4cvvjvy,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","(In reply to comment #3)
+> (In reply to comment #2)
+> > ""Edit Source"" never even existed before Visual Editor
+> 
+> Not even remotely true. The ""Edit Source"" tab is the relabelling of the
+> regular
+> ""Edit"" tab.
+> 
+> I'm minded to agree with This, that and the other, but willing to be
+> convinced.
+
+I see now what you mean, but my point still stands: ""edit source"" is not something that warrants use of the word ""always"", as it's completely new, introduced with visual editor... there was no ""edit source"" anywhere before VE.
+for all i care, we do not even need ""edit source"" on the page when reading it, ""Edit"" is enough, as long as there *is* ""edit source"" once VE fires up. as to what should be the action of this ""edit source"", i believe it should put you in the same spot you would have been if VE was not enabled. in the case you entered edit state through an editsection linkette, this means edit section.
+
+however, it is possible in this case to eat the cake and have it too, by rephrasing the original ticket, so let me try to do this:
+
+====== ORIGINAL TICKET REPHRASING ===========
+When the user press the editsection linkette and VE is enabled, a new top menu item should be generated: ""Edit section source"", next to ""Edit source"". pressing this menu item is equivalent to pressing the editsection link when VE is disabled.
+
+Not allowing this functionality basically means that there is no way to execute section edit of wikitext if VE is enabled, which, IMO, is a serious regression.
+(alternatively, pressing the ""edit source"" linkette should open a dialog asking if the user wants to edit the whole article or just the section).
+============== END REPHRASING ===============
+
+peace.",1371594513,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","(In reply to comment #2)
+> ""Edit Source"" never even existed before Visual Editor
+
+Not even remotely true. The ""Edit Source"" tab is the relabelling of the regular ""Edit"" tab.
+
+I'm minded to agree with This, that and the other, but willing to be convinced.",1371582534,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","(In reply to comment #1)
+> This behavior would be confusing and would break the consistency of the ""edit
+> source"" tab always going to the whole-page editor. 
+
+forgive my bluntness, but this is plain silly.
+what do you mean ""source tab always going to the whole page""? we are not discussing ""View Source"" tab, we are discussing ""Edit Source"" tab, which is something completely different.
+""Edit Source"" never even existed before Visual Editor and the reference to ""always"" does not make any sense: this project is slowly making its way from alpha to beta, and there is no ""backward compatibility"" or past behavior this thing should feel obliged to.
+
+peace.",1371581100,PHID-USER-akv4ingxkspiiam6r2n4,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","This behavior would be confusing and would break the consistency of the ""edit source"" tab always going to the whole-page editor. 
+
+Perhaps displaying the UI of bug 49666 while in VE edit mode would be a better solution to this. I'd be interested to see the resolution of bug 47779 first though.",1371521502,PHID-USER-sx63fwaih5kjt7bz4u6z,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+VisualEditor: Links to new pages inside templates are coloured red in the content but not a dialog iframe,"These links being red at all come about because content of templates is rendered by the PHP parser, which sets class=""new"" (Parsoid itself doesn't hint about target colour yet). However, because dialogs are implemented as <iframe>s, we can't inherit MW's CSS for the body element, so they appear differently.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369932240,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yevsvpn7ps2wcpzwmbie,task_description,resolved
+VisualEditor: Links to new pages inside templates are coloured red in the content but not a dialog iframe,Now fixed as of last month.,1399324316,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-yevsvpn7ps2wcpzwmbie,task_subcomment,NA
+Implement a find/search and replace tool,"There's a search-and-replace tool in the wikiEditor which some users might miss and would like in VisualEditor somehow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1368321420,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_description,resolved
+Implement a find/search and replace tool,"Change 174491 merged by jenkins-bot:
+Find and replace
+
+[[https://gerrit.wikimedia.org/r/174491]]",1417631052,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,Same. See the commit above.,1416824888,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,">>! In T50368#776888, @Esanders wrote:
+> For now I think the tool can go in the hamburger menu on the right.
+
+What about in non-MW integrations?",1416794975,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,For now I think the tool can go in the hamburger menu on the right.,1416791907,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,https://gerrit.wikimedia.org/r/#/c/174491/,1416791428,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"(In reply to Eran Roz from comment #12)
+> I can only think of ""Language"" and ""Replace"", so I guess we don't have
+> enougth tools right now for a new menu.
+> (or maybe the ""advanced"" options (page settings, categories etc...) is
+> actually ""tools"" menu?)
+
+We've been struggling with what to do with categories (which are pretty vital) compared to ""don't show TOC"" (which is pretty rare). Suggestions for improvements to the toolbar are always welcome. :-)",1400888389,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"I can only think of ""Language"" and ""Replace"", so I guess we don't have enougth tools right now for a new menu.
+(or maybe the ""advanced"" options (page settings, categories etc...) is actually ""tools"" menu?)",1400881097,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"(In reply to Eran Roz from comment #10)
+> Yes, I would like if it would be possible to create an extra different menu,
+> instead of adding all the tools to mislabelled ""Insert"". I think the new
+> ""Language"" option will also fit here.
+
+Hmm. Possibly. I was thinking of putting it in the ""text styling"" menu, but it could live here.
+
+Is there anything else that would live in the ""Tools"" menu? (Note that the obvious items to go in a ""tools"" menu – copy, cut, paste, paste formatting – can't be done in Javascript at all, sadly.)",1400880157,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"Yes, I would like if it would be possible to create an extra different menu, instead of adding all the tools to mislabelled ""Insert"". I think the new ""Language"" option will also fit here.",1400879623,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"(In reply to Eran Roz from comment #8)
+> We have a first working draft for replace tool for VE:
+> https://en.wikipedia.org/wiki/User:%D7%A2%D7%A8%D7%9F/veReplace.js
+
+This ends up in the (mis-labelled) ""Insert"" menu, right? Would it be helpful it we created a category of tool to manipulate the contents (a spelling or grammar tool might also fit here, though again it's something you'd generally expect your browser to provide)?",1398975277,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"We have a first working draft for replace tool for VE:
+https://en.wikipedia.org/wiki/User:%D7%A2%D7%A8%D7%9F/veReplace.js
+
+It works and replace the specified text, and undo&redo are properly supported (the last is just a claim that we didn't hack the VE too much :) ). 
+Currently it does only ""replace all"" but it can be easily extended with simple replace function, regexs and more... 
+We didn't ""publish"" it yet in village pumps since we want to do add at least some of this features before.",1398963768,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"(In reply to Eran Roz from comment #6)
+> As part of the work on
+> [[meta:Grants:IEG/Visual_editor-_gadgets_compatibility]], I plan to work on
+> [[meta:User:Pathoschild/Scripts/Regex menu framework]], that should give a
+> quick&dirty workaround to this issue.
+
+Consider using the new version of that script instead:
+[[m:User:Pathoschild/Scripts/TemplateScript]]",1396716497,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"I agree with Amir. This is regression as this option is already available in WikiEditor and it is very basic functionality (available even in simple notepad), so it isn't an enhancement but at least normal (or major?) bug.
+
+As part of the work on [[meta:Grants:IEG/Visual_editor-_gadgets_compatibility]], I plan to work on [[meta:User:Pathoschild/Scripts/Regex menu framework]], that should give a quick&dirty workaround to this issue.",1396687246,PHID-USER-cfsvvgbtlqnbt2yokfjf,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"Somebody told me that my comment was unclear: when I say that it's a regression and not an enhancement, I mean that the *lack* of search and replace functionality is a regression, and the request to have it should be treated as a bug report and not as an enhancement request.",1396685853,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,I'd say that it's a regression and not an enhancement.,1395925189,PHID-USER-xfe43w2lb5gpvglf4coa,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,This still seems to be a popular request from users at multiple Wikipedias.,1386468820,PHID-USER-uf3buojo4ceizjywvyn5,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,*** Bug 53326 has been marked as a duplicate of this bug. ***,1377460909,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"As long as it doesn't have the same performance issues which makes it unusable (bug 23510), I support this. :-)",1375968089,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"The difference between editing and reading mode isn't obvious enough for the user.
+
+(reported at http://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Alpha2013-04#Unterschied_Bearbeitungsfenster_und_gespeicherter_Artikel)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367512020,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-e53nvp2e24hk4kjigmbx,task_description,open
+VisualEditor: There is not enough UI difference between reading and editing mode,"This seems, well, almost trivial to implement. Here's what I have in my common.css to do this when I edit:
+
+.ve-ce-surface { background: #FFFDD0; }
+
+That's a personal color choice, of course. I'd be happy to defer to the consensus of a larger group of VE users about a better color. But other than choosing a color, this seems like an enhancement that can relatively easily be put in the ""done"" category.  ",1417807160,PHID-USER-hirrhium5ibrtof34lwa,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"I'm with Pam on this one. Editing and reading are not two halves of the same participation at all - they are distinct activities. There should be no (or at least minimal) barriers to people participating in both but there is a fundamental difference between them.
+
+Reading Wikipedia and other Wikimedia projects is an act of consuming content. With varying degrees of interactivity you can choose which content you want to consume, and in limited ways how you want to consume it. It is possible to read Wikipedia etc in many different environments, for example using a desktop computer, handheld tablet, e-ink reader, dead-tree books even projected onto the side of buildings iirc. The reader has no responsibility to or for the content and enters into no legal agreement with anyone (although they may do so with others in order to access Wikipedia in some modes).
+
+Editing Wikipedia is an inherently interactive process of collaborative production. It entails the responsibility to abide be the legal agreement they enter into, and the requirement to not insert copyright violations, to agree to community norms, and display at least basic competence, etc. Editors must agree to be responsible for the content they enter, and so must be old enough according to one or more legal jurisdictions to assume that responsibility. It is not possible to edit Wikipedia in all modes it is possible to read it in.
+
+Look at attachment 12954 (the second attachment on bug 52004 in case that link doesn't work) for perhaps the clearest evidence about how reading and editing are fundamentally different concepts.
+
+In addition to the above there a practical difference with the way one has to behave with a reading window and editing window. When reading, I can paste a new link anywhere on the page to view a different article, or an can follow a link from anywhere in the page with no need to think about anything else; I can page down using the space bar (often convenient on this laptop), and I can simply type a few characters or words to quickly jump to a different part of the page. When editing I cannot do any of those and I need to be able to tell at a glance whether pressing tab a couple of times followed by enter will take me to the third link or will alter the formatting of the page.",1374876541,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"What's the virtue of having no difference between reading and edit mode? I see none. If I'm in editing mode, I want to be reminded that I still need to close off the edit properly (give edit summary, save page), rather than accidentally just close down all tabs, or leave the computer and let it close itself messily after x hours). I may be juggling several open windows, in connection with the one edit or with other jobs (and because the page dialog obscures the article, I'm often opening a second copy of the page while I'm in VE so that I can actually see it while adding a category or stub template, as being quicker than closing the dialog box to see the information I need). Editing and reading are two different activities: someone editing has responsibilities - not to accidentally lean on keys and produce garbage, not to leave the page without a helpful edit summary. Someone reading... is just someone reading.",1373882835,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,*** Bug 50456 has been marked as a duplicate of this bug. ***,1373852659,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"Bug 48272 should help a little, changing the browser tab and title when editing. The reporter wanted a change within the content area, such as a red border while editing.",1369192036,PHID-USER-gbl4hfak3cfurt3c7skd,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"This is somewhat of a deliberate choice - indeed, a long term goal is to be able to have no distinction at all between 'read' and 'edit' modes (except that in one you'll have a cursor) - though we may not do this for Wikimedia's servers, and certainly not soon.
+
+I'm willing to consider suggestions about making it a little more obvious without breaking the fundamental concept that editing and reading are two halves of the same participation, but marking this as Lowest/Enhancement to reflect this.",1367547755,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: Link inspector doesn't open in Opera,"The link inspector doesn't open. Clicking the little button causes it to animate as if it was opening, then disappear completely.
+
+I'm investigating.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367169780,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_description,resolved
+VisualEditor: Link inspector doesn't open in Opera,"Sweet, link editing is now possible. Now we just need bug 47793 fixed and Opera will be basically on par with other browsers in temrs of VE support.",1372894482,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_subcomment,NA
+VisualEditor: Link inspector doesn't open in Opera,"Change 61365 merged by jenkins-bot:
+Revert ""Address error caused by changing focus from context menu to window.""
+
+https://gerrit.wikimedia.org/r/61365",1372889290,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_subcomment,NA
+VisualEditor: Link inspector doesn't open in Opera,"Ie4f1334e is just a proof-of-concept, not really a patch yet.",1367238767,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_subcomment,NA
+VisualEditor: Link inspector doesn't open in Opera,Related URL: https://gerrit.wikimedia.org/r/61365 (Gerrit Change Ie4f1334e0beb7ba7d4f4aa3b42464fa219c4778c),1367238634,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Something causes ve.ce.SurfaceObserver.prototype.stop() to be called without a subsequent call to ve.ce.SurfaceObserver.prototype.start().
+
+Apparently happens after clicking on a link. I'm investigating.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367169660,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_description,resolved
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),I'm hacking around mutation observers.. maybe we will get rid of SurfaceObserver soon (and get rid of those kind of problems).,1375851816,PHID-USER-s7sn3zjthnxvep34c5ho,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),Fixed a second time. Maybe. :-),1375845262,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 77639 merged by jenkins-bot:
+Actually fix bug 47793 for Opera for real this time
+
+https://gerrit.wikimedia.org/r/77639",1375845178,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 77639 had a related patch set uploaded by Matmarex:
+Actually fix bug 47793 for Opera for real this time
+
+https://gerrit.wikimedia.org/r/77639",1375650620,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),Hooray! This shouldn't be causing issues anymore now.,1375118463,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 71249 merged by jenkins-bot:
+ve.ce.Surface: Prevent focus loss on the document node in Opera
+
+https://gerrit.wikimedia.org/r/71249",1375118269,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 61358 abandoned by Matmarex:
+Don't bind 'blur' and 'focus' on the document node in Opera
+
+Reason:
+A different approach in I7962f59bd02e0.
+
+https://gerrit.wikimedia.org/r/61358",1372541828,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 71249 had a related patch set uploaded by Matmarex:
+ve.ce.Surface: Prevent focus loss on the document node in Opera
+
+https://gerrit.wikimedia.org/r/71249",1372541790,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),Gotcha. Why does Opera have to be weird...,1367235895,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),Related URL: https://gerrit.wikimedia.org/r/61358 (Gerrit Change Iaaa2a7993f3561dc663a064468c396ebfe951ce7),1367235847,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,"ve.ce.Surface.getSelectionRect() throws errors in Opera. I think this is the root cause of bug 37861 and likely various other issues.
+
+It seems that rangySel.get{Start,End}DocumentPos consistently fails in Opera, because nativeRange.getClientRects() inside of the private createClientBoundaryPosGetter() function returns an empty collection. This causes the ""Cannot get position for range ..."" error to be thrown.
+
+I'm still investigating the why, I'm just putting this here. Changing getSelectionRect() to just always return some static value seems to work (or at least not fail miserably anymore).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367065980,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_description,resolved
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,The fix is merged now. Marking as fixed.,1367595441,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,(Done is PS2.),1367168550,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,"Hmm, apparently this also happens for non-empty selections in some cases. We're gonna need a larger workaround...",1367165002,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,Related URL: https://gerrit.wikimedia.org/r/61190 (Gerrit Change I4bad882d1d6fb83bcdcfd0de3bfc9af52960c2ff),1367082013,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,"This seems to work:
+
+>>> range = document.getSelection().getRangeAt(0)
+Range 
+>>> span = document.createElement('span')
+<span/>
+>>> range.getClientRects()
+ClientRectList []
+>>> range.surroundContents(span)
+undefined
+>>> $(span).offset()
+{ left: 352, top: 1025 }
+
+Now we just have to substract window.scrollY from the 'top' value and remove the <span> from the DOM again. (And don't call .getClientRects() on that Range again, as it returns a completely bonkers huge list of values.)",1367069662,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,"So, what happens is that in Opera, for zero-length ranges (ie, just a caret, no selection):
+
+* .getSelection().getRangeAt(0) returns a Range
+* but then .getClientRects() returns an empty ClientRectList
+* and .getBoundingClientRect() returns a rectangle with all values being 0",1367067995,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**Author:** `suitongbowgn`
+
+**Description:**
+Feature request:
+
+A feature that supports insertion and simple editing of source code snippets in a general article. It may include a simple grammar checking mechanism which checks some fundamental grammatical errors such as having a { without closing it, having a () with a trailing period and nothing else, having solely a pair of brackets, etc.; an indentation correction tool which will perform indentation formatting on the codes; a beautify code tool which will reorganize code formatting, including indentation to make the code more reader-friendly in format.
+
+
+Features:
+* Insert or edit a code block.
+* Basic IDE features (perhaps re-use WikiEditor/CodeEditor)
+ * Syntax validation (matching quotes/parenthesis/braces etc.)
+ * Follow indentation level when breaking lines.
+ * Live grammar highlighting.",1366998060,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ss5sivrosviwhazfuu4q,task_description,resolved
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 247474 merged by jenkins-bot:
+Use Ace editor widget for code input
+
+[[https://gerrit.wikimedia.org/r/247474]]",1445528834,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 247851 merged by jenkins-bot:
+Introduce Ace editor widget
+
+[[https://gerrit.wikimedia.org/r/247851]]",1445528829,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 247851 had a related patch set uploaded (by Esanders):
+Introduce Ace editor widget
+
+[[https://gerrit.wikimedia.org/r/247851]]
+",1445443909,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 247474 had a related patch set uploaded (by Esanders):
+WIP Use Ace editor when available
+
+[[https://gerrit.wikimedia.org/r/247474]]
+",1445350934,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"A first step would be putting making an RL module for Ace in core. Each language is a separate JS file so we'd want submodules for each, like we used to do with GeSHi.",1442426303,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,">>! In T49742#1645908, @Esanders wrote:
+> I think the best approach would be to convert the editor to a dialog and drop in CodeEditor's existing code editor (Ace), or some equivalent (CodeMirror).
+
+That could work.",1442424825,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"I think the best approach would be to convert the editor to a dialog and drop in CodeEditor's existing code editor (Ace), or some equivalent (CodeMirror).",1442424794,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 114529 had a related patch set uploaded by Jforrester:
+[WIP] Add VisualEditor support
+
+https://gerrit.wikimedia.org/r/114529",1404758232,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,Re-opening as this is now unmerged.,1404758215,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,Marking this also as fixed by gerrit 68615 - congratulations again!,1380739898,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+Yes.
+
+(In reply to comment #19)
+> GSoC ""soft pencils down"" date was yesterday and all coding must stop on 23
+> September. Has this project been completed?",1379521061,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"GSoC ""soft pencils down"" date was yesterday and all coding must stop on 23 September. Has this project been completed?",1379435009,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+For now no codes from GeSHi are directly reused. I just used them as reference for regex patterns. I said 'port' due to this fact.
+
+(In reply to comment #17)
+> (In reply to comment #15)
+> > Have you considered using an existing highlighter
+> > library, or at least basing your implementation on a existing language spec
+> > format (e.g. implementing GeSHi language specs in JS?)
+> 
+> GeSHi is GPLv2+, whereas VisualEditor is MIT.  So if any GeSHi code is
+> reused,
+> the authorship and licensing should be made clear.",1378765646,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"(In reply to comment #15)
+> Have you considered using an existing highlighter
+> library, or at least basing your implementation on a existing language spec
+> format (e.g. implementing GeSHi language specs in JS?)
+
+GeSHi is GPLv2+, whereas VisualEditor is MIT.  So if any GeSHi code is reused, the authorship and licensing should be made clear.",1378765153,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+The highlighter spec is ported from GeSHi's php into js. I didn't find spec for validator so I came up with myself.
+
+(In reply to comment #15)
+> Tongbo: Re: your implmementation so far: Is the language spec something
+> you've
+> come up with yourself? Have you considered using an existing highlighter
+> library, or at least basing your implementation on a existing language spec
+> format (e.g. implementing GeSHi language specs in JS?)",1378509824,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Tongbo: Re: your implmementation so far: Is the language spec something you've come up with yourself? Have you considered using an existing highlighter library, or at least basing your implementation on a existing language spec format (e.g. implementing GeSHi language specs in JS?)",1378509073,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,CCing Andre who can give you editbugs.,1375196802,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"If you don't have permission to do it yourself, it's probably because you don't have the 'editbugs' right.  Hopefully, someone on this bug can give it you.  If not, ask on IRC.",1375163246,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 68615 had a related patch set uploaded by Jforrester:
+Source code editing
+
+https://gerrit.wikimedia.org/r/68615",1375162980,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+Somebody with the power could you change the bug status to assigned, and it was assigned to me.
+Also anyone who is interested please feel free to give code review at the following patch.
+
+> Related URL: https://gerrit.wikimedia.org/r/68615 (Gerrit Change
+> I4adede9e05fd2236cee50ce03f597e8ff6b1914d)",1375162735,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,Related URL: https://gerrit.wikimedia.org/r/68615 (Gerrit Change I4adede9e05fd2236cee50ce03f597e8ff6b1914d),1371190144,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Just a note to say that Tongbo Sui has submitted a GSoC proposal related to this report: https://www.mediawiki.org/wiki/User:Beanixster
+
+Good luck!",1367534348,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+In a nutshell it would be a major front-end JS work and will leave backend as-is as much as possible. I'm pretty sure that it will only utilize tags currently available and won't affect backend at all.(In reply to comment #6)",1367169151,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,Given that this is about desired enhancements to a VisualEditor plugin for the SyntaxHighlight extension - bug 43126 - moving this there and marking as a dependency.,1367002940,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+I understand that the rich text is just a presentation and I can see in article source that the formats are defined using a set of markups. What I'm proposing is a plugin/feature which will take care of write the markup(plaintext) for the user when editing code snippets, just like what VisualEditor is intended to do (in my opinion). In addition source code needs special formatting that is different from natural written human language, so that's why I think the feature should include automatic indentation and such.
+For editing just a part of the text, I'm thinking of an interface similar to a pop-up window, obscuring parts of the editing window. Just like when you insert an image the editor will have a new window pop up asking image url, alt text, target, etc. When you click insert the editor will convert your choice in that pop-up window to the plaintext with tags and other markups, which will be visually reflected in the main WYSIWYG editor.
+
+(In reply to comment #5)
+> Ah, it seems I misunderstood, sorry. I though you are talking about the
+> source
+> code *of the article itself*, and it appears like you meant source code in
+> different languages, such as what's included in a <syntaxhighlight> tag.
+> 
+> Sorry and please disregard my comments :)
+
+(In reply to comment #4)
+> Making sure that arbitrary wikitext does not interact with other parts of the
+> page is difficult. It is possible to enforce this for extension content, but
+> generally not for arbitrary parts of a page.",1367000971,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Ah, it seems I misunderstood, sorry. I though you are talking about the source code *of the article itself*, and it appears like you meant source code in different languages, such as what's included in a <syntaxhighlight> tag.
+
+Sorry and please disregard my comments :)",1367000177,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Making sure that arbitrary wikitext does not interact with other parts of the page is difficult. It is possible to enforce this for extension content, but generally not for arbitrary parts of a page.",1367000151,PHID-USER-hbtlbu4zftxnz4i6f7yf,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"If anything, it seems like this request would build on top of that one. It's currently just not possible to edit almost anything else than plaintext in VisualEditor (and it's not just an interface issue, but a backend one as well).
+
+I'm reopening and marking as dependent on that one, then. Feel free to adjust this :)",1367000062,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+I believe that request is too broad and this one is more specific. (In reply to comment #1)
+> 
+%%%> *** This bug has been marked as a duplicate of bug 43133 ***%%%",1366998862,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"
+
+*** This bug has been marked as a duplicate of bug 43133 ***",1366998592,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Automatically propose/suggest a category for images,"Let's crush the [categorisation backlog](https://commons.wikimedia.org/wiki/User:Multichill/Categorization_stats) once and for all!
+
+some categorization could be automated already.
+
+Searching for pictures based on meta-data is called ""Concept Based Image Retrieval"", searching based on the machine vision recognized content of the image is called ""Content Based Image Retrieval"".
+
+What I understood of Lars' request, is an automated way of finding the ""superfluous"" concepts or meta-data for pictures based on their content. Of course recognizing an images content is very hard (and subjective), but I think it would be possible for many of these ""superfluous"" categories, such as ""winter landscape"", ""summer beach"" and perhaps also ""red flowers"" and ""bicycle"".
+
+There exist today many open source ""Content Based Image Retrieval"" systems, that I understand basically works in the way that you give them a picture, and they find you the ""matching"" pictures accompanied with a score. Now suppose we show a picture with known content (pictures from Commons with good meta-data), then we could to a degree of trust find pictures with overlapping categories. I am not sure whether this kind of automated reverse meta-data labelling should be done for only one category per time, or if some kind of ""category bundles"" work better. Probably adjectives and items should be compounded (eg ""red flowers"").
+
+Relevant articles and links from Wikipedia:
+
+  # [w:Image_retrieval](https://en.wikipedia.org/wiki/Image_retrieval)
+  # [w:Content-based_image_retrieval](https://en.wikipedia.org/wiki/Content-based_image_retrieval)
+  # [w:List_of_CBIR_engines#CBIR_research_projects.2Fdemos.2Fopen_source_projects](https://en.wikipedia.org/wiki/List_of_CBIR_engines#CBIR_research_projects.2Fdemos.2Fopen_source_projects)
+
+ Some demo links bawolff found:
+
+
+  # [http://demo-itec.uni-klu.ac.at/liredemo/](http://demo-itec.uni-klu.ac.at/liredemo/ ) (Lire might even be integrated with CirrusSearch because it's based on Lucene)
+  # [http://image.mdx.ac.uk/time/demo.php](http://image.mdx.ac.uk/time/demo.php)
+  # [http://mi-file.isti.cnr.it:8765/CophirSearch/](http://mi-file.isti.cnr.it:8765/CophirSearch/)
+  # [http://orpheus.ee.duth.gr/anaktisi/](http://orpheus.ee.duth.gr/anaktisi/) (not free)
+  # [https://youtube.com/2eaGwk4Xhks](https://youtube.com/2eaGwk4Xhks)
+
+
+  - Skills: image recognition/analysis, possibly Natural language processing; language depending on implementation, e.g. python for a [PWB tool](https://www.mediawiki.org/wiki/Manual:Pywikibot), JavaScript and PHP for a MediaWiki extension, JavaScript for a [tool](https://www.mediawiki.org/wiki/Tool_Labs) similar to the [Wikidata Game](http://magnusmanske.de/wordpress/?p=203).
+  - Possible mentors: Kristian Kankainen (Keeleleek); WereSpielChequers?
+  - Additional info: ""I like the idea of automating categorisation, but I think we are a long way from being able to do much of it. So this would be a big longterm project. One of my concerns is that we are a global site, and we are trying to collect the most diverse set of images that anyone has ever assembled. Image recognition is a good way of saying that we now have another twenty images of this person, but it could be confused when we get our first images of one of the fox subspecies that we don't yet have a picture of. Or rather it would struggle to differentiate the rare and the unique from their more common cousins. There are also some spooky implications for privacy re image recognition and our pictures of people, aside from the obvious things like identifying demonstrators in a crowd or linking a series of shots of one person in such a way as to identify that this photograph of a face belongs to the same person as this photo of pubic hair because the hand is identical; We have had some dodgy things happening on Wikipedia with people wanting to categorise people ethnically and I worry that someone might use a tool such as this to try and semi accurately categorise people as say Jewish. Another major route for improved categorisation is geodata, and I think this could be a less contentious route. Not that everything has geodata, but if things have it could be a neat way to categorise a lot of images, especially if we can get boundary data so we can categorise images as being shot from within a set of boundaries rather than centroid data with all its problems that the parts of one place maybe closer to the centre of an adjacent place than the centre of the area they belong to. WereSpielChequers (talk) 09:58, 20 June 2014 (UTC)""
+
+----
+Proposed in #community-wishlist-survey-2016. Received 33 support votes, and ranked #45 out of 265 proposals. [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Commons#CW2016-R045 | View complete proposal with discussion and votes here. ]]",1366602900,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_description,open
+Automatically propose/suggest a category for images,"Hi there. I did work on a proof of concept for this during the hackathon. Backend code is at https://github.com/Niharika29/imagery as Framawiki pointed out. The user script is at https://commons.wikimedia.org/wiki/User:NKohli_(WMF)/imagery.js (It needs a lot of improvements but works okay as a proof of concept). To use it, add `importScript( 'User:NKohli_(WMF)/imagery.js' );` to your common.js page and then you will see a 'Detect labels' button underneath each image on the File page for the image. Clicking that button will activate it and after a few seconds it will be replaced by features it found in the image and suggested categories.
+
+This could use a lot of feature and design improvements. I haven't heard any actual feedback on the script yet so I was waiting on that a bit. I would be more than happy to work on improving this script and eventually proposing it be a gadget, if people think that's a good idea.
+
+As for integration into MediaWiki - that would be a challenge. This script works by querying Google's image recognition service. Anything that can do feature labelling for images needs to have a huge, good, trained dataset like Google does. We'd first have to build that in order to build the extension because we do not deploy extensions which rely on external services. That's a monumental task and it will probably be years before we can get that in place. 
+",1531771716,PHID-USER-qztkawkvfnwvkspdr46l,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,@Framawiki: Is there a reason why this should preferably be implemented via a MediaWiki extension (instead of any kind of implementation)?,1531749181,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,">>! In T49492#4427133, @Aklapper wrote:
+> Someone correct me if I'm wrong: I think that @Niharika worked on this in {T155538} as can be seen in https://commons.wikimedia.org/wiki/File:Wikimedia_Hackathon_2018_showcase_-_Image_labelling_and_category_suggester.jpg ? 
+> Wondering if there is a link to a codebase to share?
+
+True, but as I remember @Niharika says during the presentation that she worked on a proof-of-concept. Backend is at https://github.com/Niharika29/imagery.
+
+Why removing #MediaWiki-extension-requests ? It would be great to have this feature integrated in mediawiki, no ? For example directly integrated into the #UploadWizard.",1531745771,PHID-USER-aswxykknolbbycawydkz,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Someone correct me if I'm wrong: I think that @Niharika worked on this in {T155538} as can be seen in https://commons.wikimedia.org/wiki/File:Wikimedia_Hackathon_2018_showcase_-_Image_labelling_and_category_suggester.jpg ? 
+Wondering if there is a link to a codebase to share?",1531745242,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Removing the  #possible-tech-projects tag as we are planning to kill it soon! This project does not seem to fit in the #outreach-programs-projects category in its current state, so I am not adding that tag right now! ",1531374696,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,I'm interested in thinking along/working on image recognition (and classification) on Commons. See also T155538.,1492719064,PHID-USER-dl5hhyukw7ernefjsgrd,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"@WereSpielChequers That sounds great! Thanks for willing to mentor :) I'm going to link your Phabricator username in the hackathon task, and if someone wants to reach out to you for questions, they can comment here or msg you on Phabricator? ",1492713320,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"I'm happy to mentor, though my availability is limited at present. Email me if a Skype chat would be useful.",1492679788,PHID-USER-a4aiqpertfr5ceq6qg2d,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"I'm adding this task here T154988. Let me know if it is not a good idea to do so :) Also, if it's fine as it is in the linked task, would someone be willing to be a point of contact/ mentor/ available to answer questions for this task during the hackathon?  ",1492645954,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,I'm adding this task here T154988. Let me know if it is not a good idea to do so :) ,1492645575,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"I'm not sure I'd call it ""standard"".  Image processing is a notoriously difficult problem.  See https://xkcd.com/1425/ for relevant discussion.  ",1488416741,PHID-USER-u64h73gx226teqcym3r5,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"@Halfak this looks like an interesting and standard ML thing. Can this be structured as a research project to do a feasibility study of methods for image category suggestions for current round of GSoC, Outreachy, RGSoC internships?",1488342572,PHID-USER-ll7x5qhzru4lqz3xfdbm,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"(NOTE) This task was proposed in the #community-wishlist-survey-2016 and in its current state needs owner. Wikimedia is participating in [[ https://www.mediawiki.org/wiki/Google_Summer_of_Code_2017 | Google Summer of Code 2017 ]] and [[ https://www.mediawiki.org/wiki/Outreachy/Round_14 | Outreachy Round 14 ]].  To the subscribers -- would this task or a portion of it be a good fit for either of these programs? If so, would you be willing to help mentor this project? Remember, each outreach project requires a minimum of one primary mentor, and co-mentor.",1488248718,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"IMPORTANT: This is a message posted to all tasks under ""Need Discussion"" at Possible-Tech-Projects. Wikimedia has been accepted as a mentor organization for GSoC '16. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.",1456853860,PHID-USER-ll7x5qhzru4lqz3xfdbm,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Hi. I am new to image recognition, so I think this could be a great learning opportunity for me. I would really appreciate it if I could get some help understanding the scope of this project and also help me find mentors, or suggest how I could get in touch with possible mentors. I am interested in applying for this project in Outreachy 11, but if that doesn't work out, I think this would still be a really great learning opportunity for me and I would like to contribute to it nonetheless. Thanks. ",1443721833,PHID-USER-stsyzohkfwbw7rep2wxj,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"The description says ""Possible mentors: Kristian Kankainen (Keeleleek); WereSpielChequers?"" CCing @werespielchequers, couldn't find Kristian.
+
+I'm also adding #Community-Tech, since this feature looks like within their scope of tools helping experienced editors. Please remove it if this is not correct.
+
+It looks like this task needs a bit of discussion to confirm that it is a good fit for #Possible-Tech-Projects. Is it a feature that is needed and the community would welcome? Is the estimated project time for a senior contributor around 2-3 weeks?",1443519573,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,Hi. I think this project is very interesting. I want to work on this in the upcoming round of Outreachy and I want to know what is expected out of me in terms of the skills and background knowledge required. Please let me know how I can contribute. Thanks. ,1443514187,PHID-USER-stsyzohkfwbw7rep2wxj,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"This is a message sent to all #Possible-Tech-Projects. The new round of [[ https://meta.wikimedia.org/wiki/Grants:IEG | Wikimedia Individual Engagement Grants ]] is open until 29 Sep. For the first time, technical projects are within scope, thanks to the feedback received at Wikimania 2015, before, and after ([[ https://phabricator.wikimedia.org/T105414 | T105414 ]]). If someone is interested in obtaining funds to push this task, this might be a good way.",1443000963,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"This is a message posted to all tasks under ""Re-check in September 2015"" at #Possible-Tech-Projects. #Outreachy-Round-11 is around the corner. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.",1442999420,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Yeah, this idea is interesting but pretty much out of scope for Bugzilla as long as it's entirely unclear how to code it.",1405685443,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,So we discuss a number of options here and it is not clear at all how to proceed. Wondering if an https://www.mediawiki.org/wiki/Requests_for_comment would be better.,1373888179,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,Is this bug also apropriate for mw extension VisualEditor ?,1373629378,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Gather display and add few more options
+
+option 6)At advance search give an option to compare and suggest a category. If selected Compare the categories also when advance search is being carried out.
+
+Have a differentlly coloured column on right hand side of search results of uncatgorised pages 
+
+
+Option 7)In special pages there is one tool called  Special:ComparePages .The tool is currently under utilised if enhanced with feature button assking to show uncategorised pages one after another. and suggesting pages for comparison . Utilisation of this good tool will improve and also rest of the data also will get improved.",1367070822,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"I came across one edit filter Filter no1(http://ja.wikipedia.org/wiki/特別:不正利用フィルター/1)  on Japanese Wikipedia it has tagged more than 80000 new uncategorised pages , the data what is already available in special pages.But here purpose of using edit filter may be to be behind page creators to add a category.This is how an avarage wikipedian looks towards imporatance of categorisation it seems.",1367069812,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Where to display options and How to insert
+
+1)Vis a Vis above first option: If a page is new or uncategorised , A button can be shown before save pages to add category.
+
+:Horizontal category option display can be provided just above save button line ,and if clicked same as in edit tools it will get added to edit window
+
+2)For option two same as First's option
+
+
+3) For third option HotCat option display as some one clicks + button 
+
+4) For fourth option to display and  add category from exmine page please also see bug no. 47497 also.
+
+5)For fifth option either like first option or a pop-up after firt few sentences are typed on a new or uncategorised page.",1367069015,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Thanks for being prompt from your side and sorry for delay from my side.
+
+
+*>>how this woould be gathered<< 
+
+1)Some part of info is already being gathered for  ""Special:Categories"" ,'Special:UncategorizedPages' and other related pages.Analyse first copule of line of categorised pages and suggest categories to un categorised pages.
+
+2)Second option is to gather information from (interwiki) Wikidata . 
+Example: Say page 'abc' and its category page 'xyz' both are common for  language 'o' and language 'p'  wikipedia + may be more other languages; say page 'efg' also is connected on more than two wikis but category 'xyz' is mentioned on some wikis and not mentioned on some wiki's 
+
+3)Third option enhancement on HotCat gadget side, when, a category is being added collect first two or three sentences of the article for statisticle comparison,or give a key line option and request editors to provide keyline  
+
+4)fourth option, having few say 5 edit filters with upto 10 keywords each and allowing edit filter manager to add category from exmine page
+
+5) Fifth option As and when Wikipedia goes for realtime editing analyse first couple of lines statistically.",1367067890,PHID-USER-azy72hrp3tpetr52aob6,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,Mahitgar: Please elaborate how this woould be gathered and displayed.,1366734764,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Note people have done things like this before. See CommonSense on toolserver. I have no idea how that tool works or if it could be feasible to use the same method in mw.
+
+I agree with andre that how to display such information is very unclear.
+
+P.s. I don't think the original poster was referring to the CategoryTree extension when s/he said category tree.",1366617778,PHID-USER-dpu5hmqvprhycqlkdzrk,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"It's not clear to me how ""automatic suggestion"" would work - the only sentence you provide about your *expected* outcome is ""The way bugzilla suggests automated summary"".
+
+What would proposals be based on? Only checking for strings that were previously used, or do you also have other heuristics in mind?
+
+When would this be displayed, and where? Only when using CategoryTree?",1366613694,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","The job will vote -1. But only in gate-and-submit, when working on it the tests should pass (or have this one be non-voting).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1365022920,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-idlocbtqlilq2tqfojzu,task_description,declined
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","After all those years, it is not going to happen. Guess it is better handled directly in Gerrit eg via T135245.  Gerrit is replacing the draft system with private changes which would suit the WIP convention. ",1490610800,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits",T135245 propose to add a new label in Gerrit `Workflow` to let users vote -1 and prevent it from being merged.,1465209913,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","There is a patch proposed upstream:
+
+* https://review.openstack.org/#/c/251373/
+** Filter events by commit message,  Allow events to be filtered by commit messages
+
+That might  let us prevent a change from entering gate-and-submit.
+",1455277524,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","(In reply to Antoine ""hashar"" Musso (WMF) from comment #4)
+> Revisiting after a while: Zuul does not have support to prevent merge based
+> on a the content of the commit message.
+
+Really?  The Jenkins jobs have a full git checkout, so presumably you could write a jenkins job for gate-and-submit that runs:
+
+git log --oneline | head -1 | fgrep -q WIP
+
+The actual test would be a little more complicated, since you'd want to be sure you were looking at the right side of a merge commit, but either HEAD^1 or HEAD^2 would name the actual patch you're committing in that case.",1416436916,PHID-USER-m2ezqyeb4uz67zq6bats,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","Revisiting after a while: Zuul does not have support to prevent merge based on a the content of the commit message.
+
+A possibility is to use Code-Review: -2 which will effectively prevent Gerrit from submitting the patch.
+
+Another way would be to add a new label in Gerrit that would be used to flag a change has being in progress which would trigger the gate-and-submit when voted +1. Something like:
+
+ Approval:
+  +1 Approved
+   0 Pending review
+  -1 Work in progress
+
+Timo thoughts? Or should we just abandon this idea?",1400511546,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits",*** Bug 53405 has been marked as a duplicate of this bug. ***,1377672091,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","Looking at the dashboard of VisualEditor extension that makes a lot of sense :)
+
+https://gerrit.wikimedia.org/r/#/projects/mediawiki/extensions/VisualEditor,dashboards/default
+
+$ git-review -l|egrep '(WIP|MERGE)'
+70560  master  [WIP] Language Inspector Prototype                          
+71641  master  [DON'T MERGE] Remove 'mw-editsection-bracket' hack    
+71285  master  [WIP] Do not allow to resize thumb image to be bigger than original file
+70346  master  [DON'T MERGE] Rich Copy and Paste from External Source
+69796  master  [DON'T MERGE] Rich paste from external sources         
+71661  master  [WIP] ve.dm.Transaction: Implement newFromDocumentInsertion, take 2
+70981  master  [WIP] Math Node UI
+68615  master  [WIP] Source code editing
+70171  master  [WIP] Math Node Matcher
+69281  master  [WIP] Link surface fix for RTL
+$",1372883700,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","I would prefer we do not rely on the commit summary having WIP or DRAFT in it, though we might warn about it.
+
+OpenStack has a patch for Gerrit (might have been upstreamed), that let you flag a change has being a work in progress (see original feature request https://bugs.launchpad.net/openstack-ci/+bug/902953 ).
+
+
+From Gerrit 2.5 release-notes, the drafts do not send patchset-created events so they should not trigger any job.  When they are published we have a new `draft-published`  event which is essentially the same as patchset-created.
+
+
+I guess voting CodeReview +2 on a draft will thus send no event at all and the change will obviously never enter any pipeline.",1365577705,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+VisualEditor: Plugin editors to be created (tracking),"This is a tracking bug for the creation of VisualEditor plugin editors, for each of which the primary bug should live in that product/component instead (where they're about an existing Extension etc.).
+
+This task has been replaced by #VisualEditor-MediaWiki-Plugins
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1364926560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_description,resolved
+VisualEditor: Plugin editors to be created (tracking),Replaced by the #VisualEditor-MediaWiki-Plugins project.,1422424777,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_subcomment,NA
+VisualEditor: Plugin editors to be created (tracking),"(In reply to Elitre from comment #2)
+> For documentation, see https://www.mediawiki.org/wiki/VisualEditor_gadgets.
+
+No, that doesn't document how to create a proper VisualEditor plugin; the gadgets system uses a different way to work.",1415898284,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_subcomment,NA
+VisualEditor: Plugin editors to be created (tracking),"For documentation, see https://www.mediawiki.org/wiki/VisualEditor_gadgets.",1415894243,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_subcomment,NA
+VisualEditor: Plugin editors to be created (tracking),"Setting to ""Lowest"" priority as in general the WMF VisualEditor team won't itself be creating these, but instead helping others do so.",1364926707,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_subcomment,NA
+no language links shown in edit mode,"When you are editing an article the language links from Wikidata are not shown in the sidebar. Local links are shown.
+
+(Reported at https://en.wikipedia.org/wiki/Wikipedia_talk:Wikidata/Archive_1#No_interwiki_links_when_you_are_in_edit_mode%3F)
+
+**See Also**:
+{T48488}
+{T63768}",1362396060,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-xb522jegn4symvyf4f4u,task_description,resolved
+no language links shown in edit mode,Thanks for checking! It might have been fixed in the meantime then. Let's close it.,1644158450,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,"If I open https://en.wikipedia.org/wiki/Zdravets,_Varna_Province for editing and hit {nav Show preview} using the 2010 wikitext editor and legacy Vector, I see language links in the sidebar, even though none are specified in wikitext, only through Wikidata. @Lydia_Pintscher, could you please provide specific steps to reproduce, or close this ticket if you can’t reproduce it anymore either?",1644154172,PHID-USER-ocqnoktaualicuvge2tu,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,Should this still be fixed? see {T160931},1503080071,PHID-USER-3wfzrv2a2ggwauxc52is,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,Still an issue in wikitext editor.,1492960800,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,*** Bug 58518 has been marked as a duplicate of this bug. ***,1387190061,PHID-USER-7n5fvppwj4ueprv2iuys,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,"Tested on fiwiki: Language links are shown when you click ""Show preview"". In VisualEditor, they are shown immediately. Is this enough?",1383629823,PHID-USER-pxpu4muyuyvybjioj2la,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+"Create a ""zen mode""/""Distraction free mode"" MediaWiki extension","Perhaps might be nice in MediaWiki core, but would definitely be nice as at least a MediaWiki extension, we should implement a ""zen mode"" capability from ?action=edit.
+
+GitHub and it seems like the Cloud9 IDE both have this mode. It's demonstrated here: <https://docs.c9.io/zen_mode.html>.
+
+In short, in the case of GitHub, it appears to be a bit of JavaScript that adds a ""zen mode"" button to the UI. When the user clicks this button, the non-essential page elements are hidden from the page, allowing the user to focus on the textarea (or other central input area) alone. Basically it reduces the amount of noise on the page in order to increase the signal.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=14501",1361595420,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-edwajw6htxppl743yg5e,task_description,open
+"Create a ""zen mode""/""Distraction free mode"" MediaWiki extension",So... I like the way that Phabricator does full screen. It's probably more accurately called full browser window. I think we should steal the (idea of) their code and put it in MediaWiki core. It can't be that much JavaScript... and then the wikitext edit toolbar (WikiEditor?) and the VisualEditor toolbar can be modified to expose this full browser window functionality. Does that seem reasonable?,1427761367,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-edwajw6htxppl743yg5e,task_subcomment,NA
+"Create a ""zen mode""/""Distraction free mode"" MediaWiki extension","Could easily be done as a gadget, rather than a extension.",1361616078,PHID-USER-dw53c5cb2qfhyemej57o,PHID-TASK-edwajw6htxppl743yg5e,task_subcomment,NA
+"Create a ""zen mode""/""Distraction free mode"" MediaWiki extension","Also knows as ""Distraction free mode"", e.g. in Sublime Text 2:
+
+http://www.sublimetext.com/docs/2/distraction_free.html",1361613794,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-edwajw6htxppl743yg5e,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","**Author:** `Coiby.Xu`
+
+**Description:**
+I try a clean install of MW 1.20.2 and also install VE and Parsoid extension. When click ""VisualEditor"" button, the VE doesn't appear and there's a js error: ""Uncaught TypeError: Cannot read property 'error' of null"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1357988100,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-utiy7prmp4a62qvvpo6d,task_description,declined
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them",Now that 1.23.x is released I suppose this is unnecessary.,1404436245,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","(In reply to comment #8)
+> I would suggest creating a backport and then ask for a review of it.  If a
+> person can be found to implement and support the backport, I don't have a
+> problem with shipping a 1.19 with it.
+
+Thanks Mark; marking as lowest priority as (as said above) WMF won't be working on this, but if a third party would like to we'd be happy to help them out.",1366906626,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","(In reply to comment #6)
+> Copying Mark - Mark, what's policy for backporting functionality changes in
+> core so that people can use extensions?
+
+Andre is right -- depends on the complexity.  We did have some discussion of this on Wikitech-l, but I don't think a final decision was made.
+
+I would suggest creating a backport and then ask for a review of it.  If a person can be found to implement and support the backport, I don't have a problem with shipping a 1.19 with it.",1366902873,PHID-USER-ogbcrxm45oo3n3xe5q25,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","(In reply to comment #6)
+> Copying Mark - Mark, what's policy for backporting functionality changes in
+> core so that people can use extensions?
+
+James: Have specific commits been identified? 
+I guess it highly depends on the complexity of the task...",1366892475,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","Copying Mark - Mark, what's policy for backporting functionality changes in core so that people can use extensions?",1366665631,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","**Coiby.Xu** wrote:
+
+Suddenly VE gave such error:""Uncaught TypeError: Cannot call method 'enable' of null"" while it was normal a few days. I'm not sure if that error is related to this bug.",1359041505,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","**Coiby.Xu** wrote:
+
+Not really, I find it works on 1.20.0 :)
+> This is correct - minimum current version of MW for the VE code is 1.21/wmf5
+> (and this may go up as we add more functionality to MW core so that VE can
+> work; it is possible that these changes will get back-ported to 1.19 and 1.20
+> by some volunteers, but we at WMF won't be looking at this whilst the
+> extension
+> is still in an experimental stage.
+> 
+> Will change this to an enhancement for that to be done, with low priority
+> (reflecting that if a volunteer wants to do it, that'd be great).
+> 
+> See my comment on the wikitech-l mailing list thread:
+> http://lists.wikimedia.org/pipermail/wikitech-l/2013-January/065532.html
+> 
+> Have added this to the Extension page on MediaWiki.org - 
+> https://www.mediawiki.org/w/index.php?title=Extension:
+> VisualEditor&diff=628258&oldid=610234",1358149634,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","**Coiby.Xu** wrote:
+
+Hi Andre,
+The skin I use is Vector. This Mediawiki is in the local network thus can't be accessed from outside:(
+The version of VE is 72c121684c6edb6ab580258676759f62e3efd471 and Parsoid's is aa34a80a6e43fe4fe6c5a95b465bf10dee3ed922.
+> Hi Coiby,
+> which user interface skin do you use?
+> Is this MediaWiki installation publicly accessible somewhere?
+> Which versions of VE and Parsoid versions do you use?",1358149479,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","This is correct - minimum current version of MW for the VE code is 1.21/wmf5 (and this may go up as we add more functionality to MW core so that VE can work; it is possible that these changes will get back-ported to 1.19 and 1.20 by some volunteers, but we at WMF won't be looking at this whilst the extension is still in an experimental stage.
+
+Will change this to an enhancement for that to be done, with low priority (reflecting that if a volunteer wants to do it, that'd be great).
+
+See my comment on the wikitech-l mailing list thread: http://lists.wikimedia.org/pipermail/wikitech-l/2013-January/065532.html
+
+Have added this to the Extension page on MediaWiki.org - 
+https://www.mediawiki.org/w/index.php?title=Extension:VisualEditor&diff=628258&oldid=610234",1358117818,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","Hi Coiby,
+which user interface skin do you use?
+Is this MediaWiki installation publicly accessible somewhere?
+Which versions of VE and Parsoid versions do you use?",1358100484,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Hieroglyphics blocks,"<hiero>....</hiero> is unparsed but shown as plain wikitext:
+https://en.wikipedia.org/wiki/User:Raymond/hiero
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/hiero",1355479200,PHID-USER-3uecblbxq24ycewm2cog,PHID-TASK-flnjgejb5tcqxovz54rt,task_description,open
+Create a VisualEditor plugin tool to add/edit Hieroglyphics blocks,"Moving this back to WikiHiero for writing the VisualEditor rich editor, if someone ever wants to do this (the basic source one is now done).",1376115313,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-flnjgejb5tcqxovz54rt,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Hieroglyphics blocks,"The above tag lets you edit the hiero syntax and preview it.
+
+This could be further extended to provide a hiero IME, but that's not going to be on our priority list any time soon.",1375554659,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-flnjgejb5tcqxovz54rt,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Hieroglyphics blocks,"Hieroglyphics support.
+
+https://gerrit.wikimedia.org/r/77508",1375554460,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-flnjgejb5tcqxovz54rt,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,"Puppet config for wikibugs:
+
+https://gerrit.wikimedia.org/r/gitweb?p=operations/puppet.git;a=blob;f=manifests/misc/wikibugs.pp
+
+Puppet config for gerrit-wm:
+
+https://gerrit.wikimedia.org/r/gitweb?p=operations/puppet.git;a=blob;f=manifests/gerrit.pp
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1354738560,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ciosa56mnibqn4lx27ub,task_description,resolved
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,"Change 37570 abandoned by Jforrester:
+wikibugs: Set up #mediawiki-visualeditor
+
+Reason:
+We gave up and moved to using pywikibugs instead.
+
+https://gerrit.wikimedia.org/r/37570",1398113588,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,"Change 54984 abandoned by Jforrester:
+Filter VisualEditor product to new mediawiki-visualeditor.log
+
+Reason:
+We gave up and moved to using pywikibugs instead.
+
+https://gerrit.wikimedia.org/r/54984",1398113560,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,The bugs are now being reported in #mediawiki-visualeditor by pywikibugs.,1398113038,PHID-USER-muirnivxp5hzppn2a3z7,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,Related URL: https://gerrit.wikimedia.org/r/54984 (Gerrit Patch-Set: I04e82cb392f1ad680db6c469f76fb717d435c20d/1),1363816716,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,Related URL: https://gerrit.wikimedia.org/r/37570 (Gerrit Patch-Set: Id7405c8ee9a8658ed7afae844a870e0253a73806/4),1363816181,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,"gerrit-wm is done, but wikibugs is ""an almighty pile of crap"" and would need major work; moving to Lowest.",1360206228,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,Attempted fixes in Gerrit 37566 and Gerrit 37570.,1354926921,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+VisualEditor: Two replacements within the same transaction and the same paragraph cause change markers to be off,"Test case:
+
++                       'removing then inserting a character': {
++                               'calls': [
++                                       ['pushRetain', 41],
++                                       ['pushReplace', ['i'], []],
++                                       ['pushReplace', [], ['j']]
++                               ],
++                               'expected': function ( data ) {
++                                       data[41] = 'j';
++                                       ve.setProp( data[37], 'internal', 'changed', 'content', 2 );
++                               }
+                        }
+
+This sets the second change marker on data[36]. This happens because the start offsets handled in TransactionProcessor.replace are translated using this.adjustment , but that glosses over the fact that not all adjustments captured in this.adjustment actually apply if the offset is before the cursor. Instead, we need some sort of offset translation. I tried using ve.dm.Transaction.translateOffset() but that doesn't seem to work out of the box very well.
+
+I guess theoretically this might also be an issue with other uses of .start attributes in the replacement processor, but it hasn't led to issues so far.
+
+Low prio because we currently don't generate transactions that trigger this case.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1353134520,PHID-USER-fovtl67ew4l4cc3oeypc,PHID-TASK-guukovmsjsnlpphgujcv,task_description,invalid
+VisualEditor: Two replacements within the same transaction and the same paragraph cause change markers to be off,With bug 45061 all change marker code has been removed.,1360975473,PHID-USER-it53o2f2kyryqyj33uzt,PHID-TASK-guukovmsjsnlpphgujcv,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface","To quote Roan:
+
+| LQT hijacks section=new via the PerformAction hook, but it doesn't make
+| any attempt to hijack section=new in the API. Instead, LQT has its own
+| API for posting things
+
+This leads to tools that use the edit API (such as the Feedback tool) being incompatible with LQT.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+* {T54729}
+* {T35260}
+* {T59989}",1350927300,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uztlkap77g3rnibwjzla,task_description,open
+"LQT should intercept ""section=new"" edits through API as well as skin interface","LiquidThreads has been replaced by #Flow on all Wikimedia production wikis (except one, which will be done soon). It is no longer under active development or maintenance, so I'm re-classifying all open LQT tasks as ""Lowest"" priority.",1470353658,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface",">>! In T43276#838397, @He7d3r wrote:
+> Is this solved by Flow?
+
+No. Flow's version of this same problem is {T59989}.",1418237342,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface",Is this solved by Flow?,1418237275,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface",See also [[mw:Thread:VisualEditor/Feedback/Eror on Feedback?]],1378924102,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface","I guess LQT extension must be a good citizen and get along with other extensions? Under the exclusivity is there by design, this looks more like a bug (and a major one) rather than an enhancement request.
+
+Setting to ""Normal"" because I lack the background. Feel free changing to Major if you agree that blocking other extensions deserves that.",1363708216,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"More or less related to bug 41147 (T43147). Iceweasel team may consider Mozilla's ESR version in their forking work. However that bug was turned into talk about Firefox forks, so I start a new bug here.
+
+Firefox is said to have an ""Extended Support Release""[1] which is recommended to be used ""by enterprises, public institutions, universities and other organizations that centrally manage their Firefox deployments""[2] by Mozilla. We may want to support that version too (just an older Firefox with security bugs fixed AFAIS).
+
+[1] http://en.wikipedia.org/wiki/History_of_Firefox#Extended_Support_Release
+[2] http://blog.mozilla.org/blog/2012/01/10/delivering-a-mozilla-firefox-extended-support-release/
+",1350761460,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-2u5uxjiqhth3znfq26qw,task_description,declined
+VisualEditor: Support Firefox 10-14,"Per T266866, the support for Firefox 10-14 has been dropped. Declining this task is long overdue.",1644737571,PHID-USER-bf7nnwcm4i6wicvxtb77,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"Per {T266866}, the support for Firefox 10-14 has been dropped. Declining this task is long overdue.",1616112511,PHID-USER-bf7nnwcm4i6wicvxtb77,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"> Maybe that bug can be reconsidered as ""Support Firefox ESR version"". That is currently version 52 released in March 2017.
+
+No. That milestone was reached in mid-2013. This is specifically about very old Firefox versions. It's possible someone might want to do this in the future.",1513027210,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"Firefox 10-14 are from the past.
+
+From https://analytics.wikimedia.org/dashboards/browsers/#all-sites-by-browser/browser-family-and-major-hierarchical-view
+
+In percent of Firefox traffic:
+
+
+| v10 | 0.29%
+| v52 | 8.9%
+| v56 | 17%
+| v57 | 65%
+
+Maybe that bug can be reconsidered as ""Support Firefox ESR version"". That is currently version 52 released in March 2017.
+",1513022862,PHID-USER-orzyp3dswemhdgdznro5,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,">>! In T43245#1161468, @Krenair wrote:
+> Do we know how many people are still using our sites with 10-14?
+
+In Dec 2014, [[ https://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm | 305.8 M total requests ]].",1427706781,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"Are we still interested in supporting these versions? FF ESR 24.8.0 is EOL now, based on the chart at https://www.mozilla.org/en-US/firefox/organizations/faq/
+Do we know how many people are still using our sites with 10-14?",1427703276,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,Re-labelling this to be about supporting Firefox versions 10-14; 15+ (inc. ESR 17 and ESR 24) should work fine.,1386182693,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"(In reply to comment #5)
+> The new warning about VE being in beta stage is not fully readable with this
+> browser. This said, it might be interesting to know whether support is coming
+> at some point or this is going to be closed as ""won't fix"". Thanks.
+
+Note that the current ESR version of Firefox is 17 now instead of 10. What does your ""this browser"" refer to?",1375475479,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"The new warning about VE being in beta stage is not fully readable with this browser. This said, it might be interesting to know whether support is coming at some point or this is going to be closed as ""won't fix"". Thanks.",1375475270,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"(In reply to comment #3)
+> VE deployment is planned for up to the end of June 2013.
+> 
+> According to
+> https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal#Proposal
+> the end of life for Firefox 10.0.x is planned for February 12, 2013. That's 13
+> weeks from now.
+
+Considering this timeframe issue, it looks fine to me not to support 10.0.x ESR currently. But in
+
+http://www.mediawiki.org/wiki/VisualEditor/2012-13_Q1_forward-look#cite_note-FirefoxLater-3
+
+I see ""VE team roughly intend to support the current, soon-to-be-current, and immediately previous versions only."" and this bug is asking VE team not to treat ESR versions as ""outdated versions"" but ""current version"" in another ""branch"".",1352072123,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"The last comment is a general ""Do we allow unsupported browsers to use VE"" question. It's not specific to supporting Firefox ESR versions.
+
+To put this into context:
+
+https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals#Visual_Editor states: ""Q2 (October-December 2012):
+First English Wikipedia deployments and iteration (New Page creation is not an ideal candidate here because of required support for things like a VE citations to ensure page survivability)"".
+VE deployment is planned for up to the end of June 2013.
+
+http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm shows a 0.52% rate for Firefox 10.0 (which will likely decrease in the future).
+
+According to https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal#Proposal the end of life for Firefox 10.0.x is planned for February 12, 2013. That's 13 weeks from now.
+
+Though there are enough internet users who run unsupported vulnerable old software versions I'd say it's arguable if it makes sense to allow FF 10.0.x as it will be rather dead soon anyway.
+
+For the time being, feedback from testing VE on FF 10.0.x would be useless and not interesting for VE developers. If VE in 10.0.x turns out buggy, Wikimedia would get blamed for a non-functional VisualEditor and would receive feedback to ""fix it please!"", instead of the browser vendor for its old version.
+
+So at the current state I don't consider adding &vewhitelist helpful for anybody. Proposing WONTFIX again.
+
+Comments?",1352066239,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"(In reply to comment #1)
+> Mozilla's internal LTS-like arrangements do not mean that the rest of the Web
+> must dance to their tune. Quite the reverse; it means that they have committed
+> to keeping a particular primary version of their browser ""up-to-date"" by
+> back-porting security and other fixes.
+> 
+> If we target VE working for modern versions of Firefox, then Firefox ESR should
+> happen to work; if it does not, that is a flaw that the Firefox development
+> team are responsible for back-porting, and there would be nothing for us to do.
+
+Yes ESR versions may work but even if it always work with all required features, the whitelist keeps blocking it from working unless &vewhitelist is added.",1351973975,PHID-USER-zjzhrhmn36icnzbckqy4,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"As listed on bug 41147, our browser matrix is https://www.mediawiki.org/wiki/VisualEditor/2012-13_Q2_forward-look#Browser_matrix - right now, we are not likely to expand this list, though as previously stated, we'd look at including pushes from others. Browsers that are not ""supported"" are still likely to work, but we will not stand behind them as working before code is released.
+
+Mozilla's internal LTS-like arrangements do not mean that the rest of the Web must dance to their tune. Quite the reverse; it means that they have committed to keeping a particular primary version of their browser ""up-to-date"" by back-porting security and other fixes.
+
+If we target VE working for modern versions of Firefox, then Firefox ESR should happen to work; if it does not, that is a flaw that the Firefox development team are responsible for back-porting, and there would be nothing for us to do.
+
+Clearly there are levels of reasonableness about this, and we won't attempt to stop things working or make changes that cause it for no good reason.",1350939146,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","I am after removing a bit of clutter from show_bug.cgi.
+
+Mobile team prefers to keep Mobile Platform separate from Platform:
+""we don't want *any* desktop os in the platform, they're useless to us. it'll be pure noise to have the desktop os list.""
+
+Hence we should show the ""Mobile Platform"" custom field only for products ""Wikipedia App""/""Wiktionary App""/""WikiLoves Monuments Mobile"" and for component ""MobileFrontend"".
+This requires Bugzilla 4.2 as per https://bugzilla.mozilla.org/show_bug.cgi?id=479400 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350610560,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_description,declined
+"Display ""Mobile Platform"" custom field only for relevant products/components","Wikimedia has migrated from Bugzilla to Phabricator. Learn more about it here: https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla - This task does not make sense anymore in the concept of Phabricator, hence closing as declined.",1416786013,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","Based on data how rarely this field has been set in the last 12 months (except for by the reporter and the bugwrangler), I am very tempted to just hide 
+* field_label_cf_platform
+* field_container_cf_platform
+via ""display:none"" in CSS for the time being, wait if anybody will actually complain, and if nobody complains disable it entirely.",1398152893,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","...by the way, Bugzilla query to see which reports use the ""Mobile Platform"" field is https://bugzilla.wikimedia.org/query.cgi?format=advanced and setting ""Custom Search"" to ""Mobile Platform | is not equal to | ---"".",1357924202,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","Looking at this again, I wondered if there are cases apart from aforelisted components when the field is set. 
+There are, especially when ""Hardware"" is set to ""Tablet PC"":
+https://bugzilla.wikimedia.org/buglist.cgi?bug_id=43748,43414,43101,41984,38420,37875,38393,37160
+
+Hence this is maybe not a good idea, and I currently think I shouldn't pursue this idea.",1357924024,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","Now that we have upgraded Bugzilla to 4.2 we can define more than one product XOR product/component when a custom field (like ""Mobile platform"") should be shown.
+
+Proposing to show ""Mobile platform"" only for:
+
+* Commons App / General
+* MediaWiki extensions / MobileFrontend
+* MediaWiki extensions / MobileFrontend (Beta)
+* MediaWiki extensions / ZeroRatedMobileAccess
+* Tools / WikiSnaps
+* WikiLoves Monuments Mobile / Browse
+* WikiLoves Monuments Mobile / General
+* WikiLoves Monuments Mobile / Login
+* WikiLoves Monuments Mobile / Maps
+* WikiLoves Monuments Mobile / Upload
+* Wikimedia / WAP mobile gateway
+* Wikimedia Mobile / Content
+* Wikimedia Mobile / devices
+* Wikimedia Mobile / Generic
+* Wikimedia Mobile / Retired (Ruby) Gateway (DO NOT USE)
+* Wikipedia App / Automated Builds
+* Wikipedia App / Generic
+* Wikipedia App / History
+* Wikipedia App / Localization/Translation/Language
+* Wikipedia App / Media Uploads
+* Wikipedia App / Near by
+* Wikipedia App / Save Article
+* Wikipedia App / Search
+* Wikipedia App / Settings
+* Wikipedia App / Share
+* Wikisource App / General
+* Wiktionary App / Wiktionary",1354729486,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","Current situation and diffusion:
+
+* ""Wikimedia Mobile"" is closed for new bug entries. Good.
+* Several mobile apps exist, such as
+  WikiLoves Monuments Mobile
+  Wikipedia App
+  Wiktionary App
+  Commons Mobile App
+* Tools/WikiSnaps exists, which is a mobile app.
+* VisualEditor/Mobile should likely should also show this field.",1351280229,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+Add unsubscribe links to email notifications,"Please add ""unsubscribe"" links to these:
+
+
+>>>>> ""MM"" == MediaWiki Mail <wiki@wikimedia.org> writes:
+MM> Hi Jidanni,
+
+MM> this is a notification from MediaWiki that a new thread on Talk:Download from Git, 'Update error',
+MM> was created on 14 October 2012 at 03:30 by Lukas9950
+
+MM> You can see it at <http://www.mediawiki.org/w/index.php?title=Talk:Download_from_Git&offset=20121013193053&lqt_mustshow=19695#Update_error_19695>
+
+MM> The text is:
+MM> When I want to update all extensions, I get an error.
+
+MM> sh-4.1$ git submodule update --init
+MM> fatal: reference is not a tree: 655d019b84689e37b3fb1018600f629c657fb575
+MM> Unable to checkout '655d019b84689e37b3fb1018600f629c657fb575' in submodule path 'Persona'
+MM> sh-4.1$
+
+MM> Anyone can help me with this?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350158820,PHID-USER-awbqewknju4hbrnah6pm,PHID-TASK-hs2662uteqpf2jylzi43,task_description,declined
+Add unsubscribe links to email notifications,"This is already provided:
+
+Your friendly translatewiki.net notification system
+
+--
+To change your email notification settings, visit
+https://translatewiki.net/wiki/Special:Preferences
+
+To change your watchlist settings, visit
+https://translatewiki.net/wiki/Special:EditWatchlist
+
+To delete the page from your watchlist, visit
+https://translatewiki.net/w/i.php?title=Summary:Support/About_Wikia:Wikia-visualeditor-dialog-wikiamediainsert-upload-label/en_(3)&action=unwatch
+
+Feedback and further assistance:
+https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents",1402005852,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+Add unsubscribe links to email notifications,"Yes, but consider a user who has left a project for several years.
+He would be looking for 'to unsubscribe' links, and nothing more technical...
+However 'Configure bugmail' I suppose is better than nothing, agreed.",1350163279,PHID-USER-awbqewknju4hbrnah6pm,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+Add unsubscribe links to email notifications,"I was trying to be helpful. I disagree from your last statement. Copying the notification I got for your last comment:
+
+Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
+------- You are receiving this mail because: -------
+You are on the CC list for the bug.",1350162916,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+Add unsubscribe links to email notifications,"Yes, all that needs to be added *within* the email.
+More importantly, a ""standard"" explanation ""of how to unsubscribe"" needs
+to me added to such emails.
+
+Indeed, even this bugzilla needs it.",1350159872,PHID-USER-awbqewknju4hbrnah6pm,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+Add unsubscribe links to email notifications,You can unwatch that thread to stop receiving email notifications. Or disable on your preferences «E-mail me on replies to a thread I am watching»,1350159071,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+[DO NOT USE] Support tables (tracking) [superseded by #VisualEditor-Tables],This was a tracking bug when tasks were managed in Bugzilla. It has been replaced by the #VisualEditor-Tables project.,1345761660,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-ov5tmb6ogxr2kfhnpik4,task_description,invalid
+[DO NOT USE] Support tables (tracking) [superseded by #VisualEditor-Tables],"**tomte** wrote:
+
+By teaching groups for Wiki editing I found WYSIWYG support for tables most important. 
+
+Even elder people I can get accoustomed to markups like bold, links, headers / TOC, bullets, categories etc without WYSIWYG, but not for tables.
+
+Editing Wiki tables in Libre Office makes them huge and no longer editable manually.
+
+So table support is not just an option but a minimum feature  - the ""condition sine qua non"" -  for WYSIWYG support. 
+tomte , Member 542126 in WikiMedia Deutschland",1374741668,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-ov5tmb6ogxr2kfhnpik4,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","From user suggestion, along the lines of how Microsoft Word works.
+
+This would involve a number of language-specific substitutions (and probably some shared ones); for English, I believe it would at least involve:
+
+* If a user types the character string 'foo ""bar', on the pressing of the 'b' it would convert the '""' character to a an &ldquo;.
+* If a user types the '""' character whilst in a string that has an &ldquo; in it earlier, convert the character to an &rdquo;.
+* If a user types in ' - ', on the pressing of the space character after the hyphen, covert the hyphen to an &endash;.
+* If a user types in ' -- ', on the pressing of the space character after the second hyphen, covert the two hyphens into one &emdash;.
+
+Worth considering as a nice to have; this would probably want to be both site-configurable (is it available at all; if yes, is it default-on), and user-configurable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1343329080,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dnx6tmydfht55cpjp4ur,task_description,open
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","Hm, fair enough. Sounds a bit English-centered, but I get that the number of potentially supported/affected languages is a fact that should not be overlooked. I am indeed using Schnark’s tool and it works fine overall (except for single quotation marks, but even MS Word still can’t deal with those, so I guess there is no proper solution), also for other languages than German. As always with such tools, I just do believe that they would be most useful for new editors, and like this there is a only a small chance that they would find out about and start using it by themselves. That leaves us once again with lots of unnecessary corrections all over the articles. Furthermore, with every year that passes, the chance that some wikis might want to start “enforcing” proper typography is diminishing; I had a long discussion on itWP years ago about the issue and it was clear that without a generally available autocorrect function nobody would be willing to change the typography rules. I guess with autocorrect available from the beginning, even the (to say the least: debatable) MoS rule on enWP would not exist in this form.
+
+Anyway, I get why we are at this point, but it’s very unsatisfying.",1578572545,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","VisualEditor now has a framework for implementing autocorrection (and more generally, doing things in response to specific text being typed). In VE we mostly use it to add wikitext-inspired shortcuts for certain features, e.g. opening the link dialog when typing `[[`, inserting a bullet list when typing `* `.
+
+I know of one script that used it to implement autocorrection rules for German: https://de.wikipedia.org/wiki/Benutzer:Schnark/js/veAutocorrect.js
+
+However, doing it for the 100+ supported MediaWiki languages would be a lot more work, and personally I'd be afraid that it would be //really annoying// if it was done wrong. Or even if it was correct, but against the style accepted by a given wiki's community: for example, English Wikipedia prefers to use straight quotation marks: https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style#Quotation_marks
+
+I don't think we want to take responsibility for writing and maintaining that at this time.",1578534992,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)",We have several user scripts that do exactly what is requested here. Maybe take some ideas from them? The feature should be available for everyone and would prevent a lot of unnecessary typographical corrections.,1578223639,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)",Anything going on? It's high time that typography is corrected automatically; I don't get how you can classify this as lowest priority!,1476643032,PHID-USER-zrh22rct2jo5hs6nu67r,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","I actually can't promise that I'll implement this soon, so I'm unassigning myself; sorry. I'm still interested in this, and proper typography on the wikis in general :)",1430348486,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","For German, that would mean changing """" in „“, like it is being suggested at de.wp.",1404019929,PHID-USER-wil4b5lylrvf3krixlkl,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","en.wp user Ruud Koot requests ""--"" be converted to endash and ""---"" to emdash, which is slightly different to comment 0.",1375956377,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","**wmf.amgine3691** wrote:
+
+And use bom. It's the right thing to do.",1343358797,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","Also ellipses (... -> …) and other auto-conversions, if this is done.",1343348715,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"Inserting symbols, accented characters, and characters from other writing systems is a common task in encyclopedia-building.
+
+VisualEditor needs to provide this as much as WikiEditor does; preferably they should use the same configuration and avoid duplicating code or config if possible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340903580,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-svlkli7eygnwnscchzm6,task_description,declined
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"Re-visiting this, I'm not sure I agree with the premise any more.
+
+Lots of the per-language localisations (and the per-wiki customisations) of the ""edit tools"" message have added useful characters for editors without the ability to insert them using their keyboard, but they all mix the semantic concepts of wikitext syntax fragments (e.g. ""<nowiki>"" or even ""{{RLM}}"") and accented characters; asking communities to de-merge these just so VisualEditor can re-use some of them seems impractical.
+
+Consequently I'm going to mark this as a WONTFIX, but if you can think of a sane way to do this, please re-open. :-(",1387220701,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,*** Bug 58323 has been marked as a duplicate of this bug. ***,1387220238,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"Re-wording this and making it depend on bug 50296 - I have doubts about this, however. Many choices about availability of characters, or about their prominence, aren't appropriate in both contexts (""~~~~"" isn't something needed in VisualEditor, for example). Not sure whether this should instead be a WONTFIX in lieu of 50296, but leaving open for now.",1383282568,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,Another request for this today. It's regarded as one of the few key missing features by a significant content editor.,1375716584,PHID-USER-ysftv67jxeaxdwcakvwo,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"This seems coincidentally to have been the subject of two separate requests today in the VE feedback pages: many editors need access to accented characters, greek letters, em-dashes and other specialised symbols, etc. See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Quick_insert_panel and the section below it.",1374066955,PHID-USER-7zhn2ep5wvjhxetsbb6n,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"**weskaggs** wrote:
+
+I have a few comments; apologies if I misunderstand the issues or am commenting in the wrong place.
+
+First, the ability to enter special characters should have higher priority.  They are very frequently used -- long dashes the most frequently of all, but many others too.
+
+Second, the WikiEditor toolbar is probably overkill.  A better model may be the CharInsert gadget that can be enabled in the English Wikipedia preferences.  The JS code for the gadget can be found at
+
+http://en.wikipedia.org/wiki/MediaWiki:Gadget-charinsert.js
+
+The gadget depends on a very simple extension called CharInsert, whose php code can be viewed at
+
+https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FCharInsert/8fa1602e22324b73491004957f02d5309302505b/CharInsert.php
+
+Of course none of this can be used without modification, but it may provide a model for a character insert interface that has been optimized for usability.",1373638737,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"Forking existing code feels icky, but depending on an otherwise-unrelated extension isn't a good way to go.
+
+Possibly some of this could be core-ified?",1354835514,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,the character config can be found: WikiEditor/modules/jquery.wikiEditor.toolbar.config.js,1354832598,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"This may be obvious but to use the existing character code would make this feature dependent on WikiEditor.  Otherwise, reproduce the character configuration in a  VisualEditor module.  Another idea is to to pull the character configuration out of WikiEditor and place it in a more centralized place.  Thoughts?",1354832512,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,Agree with stealing existing code if possible. :-),1340922361,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"There is an eminently and patently useful extension called ""Drafts"" that was written a few years ago: <https://www.mediawiki.org/wiki/Extension:Drafts>.
+
+This project kind of stagnated and/or died, I believe. I'd like to see it revived. This bug is about doing whatever is necessary to have this extension deployed to Wikimedia wikis.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T57370}
+{T75241}",1340821500,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_description,open
+Review and deploy Drafts extension to Wikimedia wikis,Is this still relevant now that #edit_recovery is a thing?,1728102632,PHID-USER-escte3psz5yfd2nj3jzr,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I'd generally prefer client-side drafts, but as discussed offline with @Jdforrester-WMF there is no blanket prohibition from the legal team on server-side draft storage.",1419864569,PHID-USER-kqwh3rvfxxh3wfsft7mu,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"About ability to recover from crashes, I wonder how complex would it be enable this ""cache"" that Phabricator offers in this very Comments textarea I'm typing it. Type something, reboot your laptop, come back to this URL, and your text is still here, in the textarea, where you left it.",1416815782,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Legal issues put aside, using client-side storage for drafts does have a lot of advantages: better performance, support for anonymous edits, ability to recover from crashes that happen while there is no network connection. The main disadvantage that I can see is that it is not privacy-friendly - using good privacy practices like incognito mode of the browser would cripple a client-side draft feature as it could not recover the text after a browser crash.",1416814165,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,">>! In T39992#424332, @Jdforrester-WMF wrote:
+> If we create a server-side private drafts facility, we invite malefactors to (ab)use the facility to store and (using accounts with a shared password) distribute:
+> 
+> * Terrorism-related materials;
+> * Child pornography (even if the Drafts are 'just' text, e.g. base64 encoding of images);
+> * Foreign intelligence service / espionage channels (let's please not make the Wikileaks comparisons true);
+> * Other criminal information; and
+> * Civil illicit information (e.g. breaking NDAs, corporate espionage, …)
+>
+>All this kind of stuff is potentially uploaded to the public fora of Wikimedia's wikis (talk pages, etc.), but (because people are aware that it's public) it is much less frequently put there, and so is at a level where it can generally be dealt with by the existing community processes. A private cache of drafts that isn't visible to any other user means that the community couldn't police it, or flag for suppression/other admin action.
+> 
+> Because of this, *even if no terrorist/pædophile/spy/criminal/mole ever did this*, WMF would get many, many subpœnæ, warrants, clandestine requests (National Security Letters, etc.) and other legal instruments which would have the effect of hugely increasing the cost to comply with these matters. I appreciate that lots of the other top-10 websites have server-side drafts facilities, but they have lots more money to throw away like this, and (allegedly) direct NSA/FBI/… access to their servers anyway, reducing the legal compliance cost (but something to which we would never agree, of course). People running less-visible services run into this problem from time to time, and in some cases end up shutting down their services; we can't take the risk that we'd need to do this at Wikimedia.
+
+This is the classic argument from infocalypse [1] which is bad form in general, but makes even less sense in Wikimedia's case given that storing arbitrary private data is already possible via the options API [2]. In fact, any user with some Javascript skills could implement the Drafts extension right now as a user script. Even if arbitrary-key, arbitrary-length options got disabled, there would be ways to make Wikipedia store private information (e.g. split it into 255-byte chunks and store it as signatures over a set of autogenerated user accounts).
+
+Not that there is any need of that, given that Wikipedia can be edited by anyone and edits are practically never deleted, so a terrorist/pedophile/etc. who is particularly set on using Wikipedia to distribute illegal content could easily do that with some industry-grade cryptography tool and a bot that hides secret messages in vandalism. Or encode messages via steganography in penis selfies, etc.
+
+Not that there is any need of *that*, given that other WMF-operated services give you easier ways of sharing secret messages, such as etherpad which is essentially private if you choose a pad name that's hard enough to guess.
+
+Not that there is any need of that either, of course, since the net is full of services which, unlike Wikipedia, can be used easily and conveniently using pre-existing software to share information in secret. Dropbox, Google Drive etc, and we didn't even get to tools which were designed explicitly for that purpose like Freenet. So I find the notion that anyone would choose to use Wikipedia's draft feature as their underground distribution channel somewhat absurd.
+
+I appreciate the argument that such activities don't actually need to happen for law enforcement to decide that they need to police them, but as I said, they are already possible, so Drafts would not change the status quo at all.
+
+
+[1] https://en.wikipedia.org/wiki/Four_Horsemen_of_the_Infocalypse
+[2] https://www.mediawiki.org/wiki/API:Options",1416814019,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Thanks for the explanation of the legal issues relating to private drafts.  I've created bug  T57670 as a result.(In reply to comment #47)
+
+Regarding the client-side hit of a VE->Drafts interface vs VE->Local storage, I suppose I was expecting that VE would be putting HTML+RDFa into local storage, in which case the client side hit is the same for both.  But that should be discussed on bug T57370. (I've raised a few other points to consider there)",1469753942,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Thanks for the explanation of the legal issues relating to private drafts.  I've created bug 55670 as a result.(In reply to comment #47)
+
+Regarding the client-side hit of a VE->Drafts interface vs VE->Local storage, I suppose I was expecting that VE would be putting HTML+RDFa into local storage, in which case the client side hit is the same for both.  But that should be discussed on bug 55370. (I've raised a few other points to consider there)",1381649758,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"James' answer above is very authoritative and the concerns about server-side private drafts apply whether we're talking about wikitext or about VE.
+
+I like the general principle of using client-side storage for data recovery purposes (maximum privacy, avoids legal issues), and working towards better support for public drafts (inviting collaborators etc.) in future. That approach is more consistent with wiki-style collaboration in public while also safeguarding user actions.",1381348765,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"[Please note that I am not a lawyer and not currently working in a criminal prosecution or national security context; this is not legal advice, just based on my professional experience.]
+
+(In reply to comment #46)
+> (In reply to comment #44)
+> > Just a quick note, in case people are pushing hard on getting this done so it
+> > can be used for VisualEditor, it's not the direction we're looking at taking
+> > for VE.
+> > 
+> > * We would need something that is client-side, not server-side (this makes
+> > things faster and avoids the really icky legal issues).
+> 
+> Are these 'icky legal issues' explained somewhere? Are you referring to the
+> need for explicit copyright signoff before *distribution*?  Why cant that be
+> delayed until the real save button is pressed?
+
+Sorry - when I quickly wrote that yesterday, I assumed they were obvious, but that probably says more about me and my priors than anything else (I have a background in criminal prosecution and central government/security) - my apologies. :-)
+
+If we create a server-side private drafts facility, we invite malefactors to (ab)use the facility to store and (using accounts with a shared password) distribute:
+
+* Terrorism-related materials;
+* Child pornography (even if the Drafts are 'just' text, e.g. base64 encoding of images);
+* Foreign intelligence service / espionage channels (let's please not make the Wikileaks comparisons true);
+* Other criminal information; and
+* Civil illicit information (e.g. breaking NDAs, corporate espionage, …)
+
+All this kind of stuff is potentially uploaded to the public fora of Wikimedia's wikis (talk pages, etc.), but (because people are aware that it's public) it is much less frequently put there, and so is at a level where it can generally be dealt with by the existing community processes. A private cache of drafts that isn't visible to any other user means that the community couldn't police it, or flag for suppression/other admin action.
+
+Because of this, *even if no terrorist/pædophile/spy/criminal/mole ever did this*, WMF would get many, many subpœnæ, warrants, clandestine requests (National Security Letters, etc.) and other legal instruments which would have the effect of hugely increasing the cost to comply with these matters. I appreciate that lots of the other top-10 websites have server-side drafts facilities, but they have lots more money to throw away like this, and (allegedly) direct NSA/FBI/… access to their servers anyway, reducing the legal compliance cost (but something to which we would never agree, of course). People running less-visible services run into this problem from time to time, and in some cases end up shutting down their services; we can't take the risk that we'd need to do this at Wikimedia.
+
+> A client-side solution is not going to go down well.  People switch between
+> computers and browsers, use internet cafes, etc.  Wikipedia and VE are a
+> web-app; ordinary users will expect auto-save to persist across their
+> user-agents. A client side solution isnt auto-save; it is a data-recovery
+> mechanism only, which is still useful in its own right, but each client will
+> have its own quirks, etc.
+
+I appreciate that this is a pain, but the drafts would probably need to only last for a few hours anyway (it's intentionally a DR solution, as you say) - Wikimedia is in the business of providing wikis, and long-term drafting is completely anti-thetical to the concept of a wiki, where ""the page is the draft"". If you have a change which is an improvement, even if it's not all it could possibly be, save it so others can collaborate with you. I would be very troubled if we were to move in a direction of encouraging such anti-wiki behaviours.
+
+> > * We would need something that lets us persist VE linear-models, or at least
+> > Parsoid HTML+RDFa (otherwise each save will take dozens of seconds of
+> > computation, slowing clients down and adding to burdens on the cluster; until
+> > server-side storage of Parsoid HTML+RDFa is undertaken, there's nowhere
+> > really appropriate for this to be saved for the Drafts extension to implement,
+> > which is currently wikitext-based)
+> 
+> There is no client-side hit required to persist VE as wikitext. VE already
+> has an API call that accepts HTML+RDFa and produces wikitext; VE can add an API
+> call that accepts HTML+RDFa and persists it as wikitext into the Drafts
+> tables.
+
+I'm sorry, this is not correct. The API call in VE that you mention is a server-side request. The process to save (or get a wikitext diff) works roughly as follows:
+
+* VE client converts data model's linear model into Parsoid HTML+RDFa (this can take a noticeable amount of processing time for complex pages)
+* VE client establishes a connexion with the (very thin) server-side VisualEditor code, and transmits the HTML+RDFa to it (noticeable network time for long pages)
+* VE server establishes a connexion with the Parsoid service, and transmits the HTML+RDFa to it (server-side IO load)
+* Parsoid pulls from storage or the MW API the previous version of the page and other data so that it can as-cleanly-as-possible serialise (server-side IO load)
+* Parsoid serialises the HTML+RDFa from the client into wikitext based on this information (server-side CPU load)
+* Parsoid responds down the connexion with VE server and transmits the wikitext to it (server-side IO load)
+* VE server establishes a connexion with the MW cluster, and transmits the wikitext to it (server-side IO load)
+* MW saves the wikitext, or fails and returns an error code with why (server-side CPU load)
+
+This whole process can take multiple seconds (as you will see every time you press ""save"" in VE), and the first step is a significant CPU drain locally; I think this would be a really not-great thing to make happen every minute in the background, given the burden that VE already exhibits on some users' machines.
+
+> Not sure that there is going to be an overall additional burden to the
+> servers either.  Converting HTML+RDFa to wikitext will be a memory&processor
+> hit to the app servers, whereas persisting HTML+RDFa into the database is an
+> IO hit as compared to wikitext.
+
+Sure. But I'm not talking about persisting to the servers, as explained.
+
+> Besides, what percentage of overall server load is spent on processing page
+> saves to content pages (excluding rendering as autosave in VE doesnt need a
+> render hit)?  I'm guessing that isn't where the WMF resources are being
+> pinched.
+
+By definition, 100% of the Parsoid cluster's load is spent on processing page saves to re-render them now they have changed, either caused by a Parsoid client (like VE) or inside MW from another source (like the wikitext editor). The split is currently weighted towards MW changes, but that's an artefact of the current proportion of edits done with VisualEditor; we expect that figure to rise over time towards 100%.
+
+> > * We would want (but not strictly /need/) something very flexible, so we
+> > could persist undo stacks, etc. which could add a huge amount of
+> > complexity to the Drafts extension for just one use case/client.
+> 
+> I agree with Legoktm; it would be great if the source editor also had some
+> features added to it. undo stacks is a major part of the problems holding up
+> the deployment of Drafts; Drafts needs to handle multiple revisions of the
+> same page being saved as a draft.   I hear the majority of the editor base
+> tend to use the source editor most of the time ;-)
+
+Sure. But who's going to do that? Building expectations for features on the never-never isn't great for editors. :-(",1381332760,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #44)
+> Just a quick note, in case people are pushing hard on getting this done so it
+> can be used for VisualEditor, it's not the direction we're looking at taking
+> for VE.
+> 
+> * We would need something that is client-side, not server-side (this makes
+> things faster and avoids the really icky legal issues).
+
+Are these 'icky legal issues' explained somewhere? Are you referring to the need for explicit copyright signoff before *distribution*?  Why cant that be delayed until the real save button is pressed?
+
+A client-side solution is not going to go down well.  People switch between computers and browsers, use internet cafes, etc.  Wikipedia and VE are a web-app; ordinary users will expect auto-save to persist across their user-agents.  A client side solution isnt auto-save; it is a data-recovery mechanism only, which is still useful in its own right, but each client will have its own quirks, etc.
+
+> * We would need something that lets us persist VE linear-models, or at least
+> Parsoid HTML+RDFa (otherwise each save will take dozens of seconds of
+> computation, slowing clients down and adding to burdens on the cluster; until
+> server-side storage of Parsoid HTML+RDFa is undertaken, there's nowhere
+> really
+> appropriate for this to be saved for the Drafts extension to implement, which
+> is currently wikitext-based)
+
+There is no client-side hit required to persist VE as wikitext.  VE already has an API call that accepts HTML+RDFa and produces wikitext; VE can add an API call that accepts HTML+RDFa and persists it as wikitext into the Drafts tables.
+
+Not sure that there is going to be an overall additional burden to the servers either.  Converting HTML+RDFa to wikitext will be a memory&processor hit to the app servers, whereas persisting HTML+RDFa into the database is an IO hit as compared to wikitext.
+
+Besides, what percentage of overall server load is spent on processing page saves to content pages (excluding rendering as autosave in VE doesnt need a render hit)?  I'm guessing that isn't where the WMF resources are being pinched.
+
+> * We would want (but not strictly /need/) something very flexible, so we
+> could
+> persist undo stacks, etc. which could add a huge amount of complexity to the
+> Drafts extension for just one use case/client.
+
+I agree with Legoktm; it would be great if the source editor also had some features added to it.  undo stacks is a major part of the problems holding up the deployment of Drafts; Drafts needs to handle multiple revisions of the same page being saved as a draft.   I hear the majority of the editor base tend to use the source editor most of the time ;-)",1381282093,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I'm not sure this is should be discussed on this bug but...
+(In reply to comment #44)
+> Just a quick note, in case people are pushing hard on getting this done so it
+> can be used for VisualEditor, it's not the direction we're looking at taking
+> for VE.
+
+Thanks for the comment. Really I'm just trying to get this extension to not suck ;-)
+
+> * We would need something that lets us persist VE linear-models, or at least
+> Parsoid HTML+RDFa (otherwise each save will take dozens of seconds of
+> computation, slowing clients down and adding to burdens on the cluster; until
+> server-side storage of Parsoid HTML+RDFa is undertaken, there's nowhere
+> really
+> appropriate for this to be saved for the Drafts extension to implement, which
+> is currently wikitext-based)
+
+Technically Drafts is set up to store anything that is text based, and I think HTML+RDFa can be serialized into text (or is already text)? We might need to add a column for contentmodel in the drafts db schema though...
+
+> * We would want (but not strictly /need/) something very flexible, so we
+> could
+> persist undo stacks, etc. which could add a huge amount of complexity to the
+> Drafts extension for just one use case/client.
+
+Ideally the Drafts extension would also have some kind of history/undo, but this is kind of a slippery slope and at some point you end up with essentially private user sandboxes.
+
+> 
+> Though I think that the Drafts extension could be useful for wikitext users,
+> I
+> don't think it's right for VisualEditor; see bug 55370 for VisualEditor's
+> take.",1381270044,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Just a quick note, in case people are pushing hard on getting this done so it can be used for VisualEditor, it's not the direction we're looking at taking for VE.
+
+* We would need something that is client-side, not server-side (this makes things faster and avoids the really icky legal issues).
+* We would need something that lets us persist VE linear-models, or at least Parsoid HTML+RDFa (otherwise each save will take dozens of seconds of computation, slowing clients down and adding to burdens on the cluster; until server-side storage of Parsoid HTML+RDFa is undertaken, there's nowhere really appropriate for this to be saved for the Drafts extension to implement, which is currently wikitext-based)
+* We would want (but not strictly /need/) something very flexible, so we could persist undo stacks, etc. which could add a huge amount of complexity to the Drafts extension for just one use case/client.
+
+Though I think that the Drafts extension could be useful for wikitext users, I don't think it's right for VisualEditor; see bug 55370 for VisualEditor's take.",1381267322,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #42)
+> It would also be helpful if there are people willing to do code review, it
+> seems that's whats stalled the development of this extension in the past.
+
+It seems Yuvi is willing. You can also e-mail wikitech-l if you can't find anyone. :-)",1381196143,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #37)
+> 
+> Is it enabled on a WMF test wiki with VE?  Could it be enabled on
+> mediawiki.org
+> in order to encourage dev's playing with it?
+> 
+
+So I set up an instance at http://drafts.instance-proxy.wmflabs.org/wiki/Main_Page and attempted to install VE, except setting up parsoid failed with some cryptic error I didn't spent time debugging.
+
+Digging through the code, there's a lot of cleanup (deprecated stuff, (ab)use of globals, etc) that needs to be done and a start has been made at https://gerrit.wikimedia.org/r/#/c/29749/
+
+It would also be helpful if there are people willing to do code review, it seems that's whats stalled the development of this extension in the past.",1381161937,PHID-USER-v7vgzvvcw7v2umf737ri,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #39)
+> Shouldn't be deployed on cluster until code has had relevant code review
+> actioned against it, and any necessary remedial action completed.
+
+Hmm, right, I forgot that this bug has a bunch of outstanding dependencies.
+
+John V.: we'll need to find someone to work on the extension in order to eventually get it deployed on any Wikimedia wikis.",1381113030,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Well, and until Features and Product have confirmed it's something they're interested in supporting (unless Platform devs are comfortable explicitly saying 'yes, we will make sure it works forevermore')",1381112441,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Depends by what you mean as a wmf test wiki. Its not on the cluster, as its not branched. I don't think it is on beta either, but you van confirm it yourselves via NOC or mediawiki-config
+
+Shouldn't be deployed on cluster until code has had relevant code review actioned against it, and any necessary remedial action completed.",1381107508,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #37)
+> Is it enabled on a WMF test wiki with VE?  Could it be enabled on
+> mediawiki.org in order to encourage devs playing with it?
+
+Greg: do you know?",1381106680,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"The demo of this extension (http://kubo.wmflabs.org/wiki/Main_Page) now returns 404.  There are some non-WMF wikis using this extension: http://wikiapiary.com/wiki/Extension:Drafts
+
+Is it enabled on a WMF test wiki with VE?  Could it be enabled on mediawiki.org in order to encourage dev's playing with it?
+
+From a quick look at the code, a prototype of VE-support of Drafts can be done easily with only user: space custom JavaScript.
+
+Proper VE-support would need a new API call to minimise data being sent back and forth.",1381106334,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Visual editor brings new dataloss scenarios due to its beta status. If VE could autosave the article as a draft, and could open the draft in VE, this would allow switching editor.",1381102490,PHID-USER-oxd6f6xemkuyttw7z7wl,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,....by six people ;p.,1352200079,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**armbrust** wrote:
+
+There was a discussion on the Proposal Village Pump on the English Wikipedia (http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_94#Allowing_users_to_keep_private_drafts_of_their_work), where this feature was cleary supported.",1352199927,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I agree that browser auto-save isn't a sufficient alternative to this feature. We still need this, and help whipping the extension into shape is very much appreciated.",1351104490,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #31)
+> (In reply to comment #19)
+> > ... modern Web browsers have auto-save.
+> 
+> That's a good point. A couple of years ago this extension would have been
+> really appreciated by me, but nowadays it has become almost superfluous, thanks
+> to the improvement of the browsers' auto-save capabilities (Firefox, for one,
+> can recover what you have typed even in the case of a power failure).
+
+I'm not aware of other browsers having the same capabilities, which I anyway still see myself failing, not seldom. There are also many other chances to lose an edit with actions that the browser can consider intentional. In short, it's not a valid assumption that the wiki editor is using a human-like smart browser.
+
+> Another thing to consider is that, after such feature is deployed, users will
+> generally feel safer about starting an edit and postponing the save for hours
+> later, posing a higher risk of edit conflicts (especially in larger wikis as
+> Wikipedia).
+
+I doubt so, and anyway it's easily configurable as far as I can see.",1351094795,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**capmo700** wrote:
+
+(In reply to comment #19)
+> ... modern Web browsers have auto-save.
+
+That's a good point. A couple of years ago this extension would have been really appreciated by me, but nowadays it has become almost superfluous, thanks to the improvement of the browsers' auto-save capabilities (Firefox, for one, can recover what you have typed even in the case of a power failure).
+
+Another thing to consider is that, after such feature is deployed, users will generally feel safer about starting an edit and postponing the save for hours later, posing a higher risk of edit conflicts (especially in larger wikis as Wikipedia).",1351094482,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #29)
+> I agree that this is a useful extension, but this goes beyond code review. The
+> extension is not deployable in its current state and needs significant work.
+> I've added some dependencies.
+
+Yes, completely agreed. I hadn't realized this reality when I filed this bug.
+
+I actually considered marking this bug as ""resolved later"" over the weekend, but now that it has some dependencies and lacks the ""shell"" keyword, I think leaving this bug open as a tracking bug should work well. Thanks for looking into this, Erik!",1348521626,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I agree that this is a useful extension, but this goes beyond code review. The extension is not deployable in its current state and needs significant work. I've added some dependencies. 
+
+I don't think this is doable as a 20% time project for Trevor, so unless there are more folks who want to chip in improvements, I'd put this on hold for now from a WMF standpoint.",1348516213,PHID-USER-766idcqt4jkngnnuhnrj,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**stillwaterising** wrote:
+
+(In reply to comment #25)
+ 
+> For the record, I'd strongly urge that the first response to any Bugzilla that
+> will result in a change to the UI should be ""Please point me to the community
+> discussion that recommends this change.""   I'm not sure why the WMF would be
+> investing 20% of an engineer's time without any evidence that [multiple]
+> communities are interested in activating an extension.  There are plenty of
+> extensions around that, simply put, aren't used because they're unwanted or
+> have a negative impact on a project.  Unexpected and undiscussed UI changes
+> have repeatedly caused significant discord between communities and Engineering.
+
+The percentage of editors reading message boards like Village pump (idea lab) has to be a very small fraction. The ratio of developers to normal users reading and responding will be disproportionate. Village Pump does not represent what the average user wants.
+
+Successful companies looking to invest in new services or products will perform studies, focus groups, and surveys.  What I propose is a survey consisting of 250+ randomly-selected recently active auto-confirmed users.
+
+Users could be shown images or videos as well having written descriptions of proposed changes to the UI and ask for how interested, how useful, how effective, etc. they think it will be for them.
+
+Smaller focus groups can be organized where users are asked to go to a test wiki and perform certain tasks and answer questions about their experience.",1347853611,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #26)
+> I'm sorry; this problem is at least partially my fault. [...]
+
+And just to clarify, I take that portion of fault for myself because I'm the one who added the extension to the queue page, perhaps misleading someone. I did so because I well remember this coming from real usability issues found at the time, being tested and receiving unanimously positive comments which can in part still be found at https://usability.wikimedia.org (I agree that the lack of a live prototype is confusing those who can't remember the 2009 one). I think the documentation already explains everything that was requested, but maybe I'm reading too much into it. 
+Anyway, as Sumana notes, design is now being re-reviewed by the wider design team.",1347852451,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**sumanah** wrote:
+
+(In reply to comment #25 by Risker)
+
+> For the record, I'd strongly urge that the first response to any Bugzilla that
+> will result in a change to the UI should be ""Please point me to the community
+> discussion that recommends this change.""   I'm not sure why the WMF would be
+> investing 20% of an engineer's time without any evidence that [multiple]
+> communities are interested in activating an extension.  There are plenty of
+> extensions around that, simply put, aren't used because they're unwanted or
+> have a negative impact on a project.  Unexpected and undiscussed UI changes
+> have repeatedly caused significant discord between communities and Engineering.
+
+Thanks for the comment, Risker, and thanks to everyone in this thread for all your comments.
+
+I'm sorry; this problem is at least partially my fault.  Just before my vacation this summer, I asked for some help maintaining the review queue (for new extensions to potentially be deployed on WMF sites: https://www.mediawiki.org/wiki/Review_queue ).  The Drafts extension got added to this list, and in late August I accidentally went straight into requesting code review/improvements from Trevor, using his ""20%"" time ( https://www.mediawiki.org/wiki/Wikimedia_engineering_20%25_policy ) . Per our procedures at https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment#Design_review , I should have instead gotten Drafts a design review first, from our product management or design team.  As the ""design review"" procedure says, ""This will start a conversation about the design of your feature, which should include community consensus on the wiki where the extension would be deployed.""
+
+The design team is currently discussing Drafts on the design mailing list:
+
+http://lists.wikimedia.org/pipermail/design/2012-September/thread.html#130
+
+and I will update that list, Trevor, and the review queue to ask for that design review.
+
+Thanks, and my apologies again.",1347849681,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #24)
+> The drafts saved by a user are not publicly visible and as such do not show up
+> on 
+> recent changes. The author can delete them at any time by clicking on ""Discard""
+> either while editing a page for which he saved a draft or while accessing all
+> his personal drafts by Special:Drafts.
+
+
+Thanks, mybugs, for answering #2 and #3.  So the response to #1 should be no because the draft is not publicly visible, and #4 & #8 would be moot if it is seen only by the user.    
+
+So this leaves:
+
+5) How long between creation and ""automatic expiry""?  Is this configurable by
+user or only within the code?
+6) Will the edits made in a ""draft"" count as edits statistically?
+7) When drafts are ""saved"" into the page, is the edit history of the draft
+incorporated into the page history?  If so, is there a way to indicate that it
+was made on a ""different"" page and not directly into the article?  [Note that
+one of the biggest issues in merging page histories is that it is pretty much
+impossible to correctly identify what past versions of the page looked like.]
+
+9) Will drafts be included in dumps?
+10) What evidence is there that *users* want this feature?  
+
+I learned long ago not to assume too much here.  
+
+For the record, I'd strongly urge that the first response to any Bugzilla that will result in a change to the UI should be ""Please point me to the community discussion that recommends this change.""   I'm not sure why the WMF would be investing 20% of an engineer's time without any evidence that [multiple] communities are interested in activating an extension.  There are plenty of extensions around that, simply put, aren't used because they're unwanted or have a negative impact on a project.  Unexpected and undiscussed UI changes have repeatedly caused significant discord between communities and Engineering.",1347847001,PHID-USER-yif6nz5uhka5cnltixpc,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"The drafts saved by a user are not publicly visible and as such do not show up on 
+recent changes. The author can delete them at any time by clicking on ""Discard"" either while editing a page for which he saved a draft or while accessing all his personal drafts by Special:Drafts.",1347825120,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #8)
+> Trevor is looking at this extension for review & improvement.  See
+> https://gerrit.wikimedia.org/r/#/q/project:mediawiki/extensions/Drafts+-owner:L10n-bot,n,z
+> .
+
+Couple of questions:
+
+1) Will these be indexed? 
+2) Can they be deleted?
+3) Do they show up in Recent Changes?
+4) Is suppression enabled? 
+5) How long between creation and ""automatic expiry""?  Is this configurable by user or only within the code?
+6) Will the edits made in a ""draft"" count as edits statistically?
+7) When drafts are ""saved"" into the page, is the edit history of the draft incorporated into the page history?  If so, is there a way to indicate that it was made on a ""different"" page and not directly into the article?  [Note that one of the biggest issues in merging page histories is that it is pretty much impossible to correctly identify what past versions of the page looked like.]
+8) When drafts expire, is that information completely inaccessible, or accessible only under specific circumstances?  [It's important to be able to re-access any material that was *ever* publicly viewable because we never know which bits will wind up requiring some sort of response in the future.]
+9) Will drafts be included in dumps?
+10) What evidence is there that *users* want this feature?  
+
+
+I think there is a faulty assumption behind some of the discussion here, that users are saving frequently because of fear of losing their work.  This isn't true; users save frequently because (a) they want to see their work in the context of the page being edited, (b) there is a systemic problem with saving work because of time-outs or the system logging them out/otherwise not accepting edits, that will not be rectified by this and (c) they are beefing up their edit counts without using scripts.",1347822673,PHID-USER-yif6nz5uhka5cnltixpc,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"As a user, this seems useful.
+
+What to do about edit conflicts might be an issue, but even a short warning not to leave it too long (and why) upon saving a draft could be enough for that, and if a page is too highly edited, maybe just removing the draft option entirely on those would be in order? Could confuse people a little at first, but they'd probably catch on eventually since a draft on, say, enwp's WP:ANI would make NO BLOODY SENSE in the first place.
+
+Just suddenly turning on automatic drafts could also pose problems due to current habits of starting edits and then thinking better of them and leaving, as opposed to using the cancel button, but editors can be retrained. On the other hand, since editing and then previewing is not only the only way to test things without saving them, but also a really convenient one, that might actually be an issue... but if all else fails, a user option to turn the automatic drafts off should fix that pretty effectively. 
+
+And the only part of this that seems like it might go out of general enhancement territory and into OUTRAGE WHY YOU CHANGE THIS?! territory is the automatic drafts. But while a decision on the parts of the projects themselves whether or not enable that part at all might make them a little happier, why should be necessary, especially if users have the option to just turn it off themselves if they don't like it?",1347769391,PHID-USER-nv2bu7uh3huvidyjo4lk,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #20)
+> It'd be nice if this extension could be enabled on https://test.wikipedia.org
+> or similar. A lack of a working demonstration is hurting the conversation, I
+> fear.
+
+Okeyes said at
+[[WP:Village_pump_(proposals)#Allowing_users_to_save_drafts_of_their_work]]
+that (the version 0.1.1) of the extension is enabled on this wiki:
+http://kubo.wmflabs.org/wiki/Main_Page
+I don't know if this is the most up to date version.",1347751319,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #17)
+> I have to say, I'm with Oliver here.  I have concerns about deployment on a
+> wide scale without some further feature development and (more importantly)
+> community input and buy-in.  It seems to me that there are policy and
+> governance changes that also need to be introduced at the same time, and it
+> would be courteous to let the community work on those with some warning.
+
+Can you elaborate on the policy and governance changes you envision?
+
+> I also have UI challenges with this.  It's not immediately transparent how it
+> works to a new user (where is the integration to contribution history or recent
+> changes?), and (while I haven't seen the documentation) I suspect that the
+> documentation is also not user-ready.
+
+They're private (per-user) drafts. I'm not sure if this was apparent when you wrote this comment.
+
+It'd be nice if this extension could be enabled on https://test.wikipedia.org or similar. A lack of a working demonstration is hurting the conversation, I fear.",1347750972,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #12)
+> TL;DR, I really oppose turning this on with the way it's formatted now and
+> using the process that's being discussed.
+
+Most of your comment reads as ""I'm bored and looking for a fight"" with a hint of ""why wasn't I consulted?"" If you want to start petty disputes on Bugzilla with me, you really ought to do better research into the battles you pick. This isn't my brainchild or my code. It's a missing MediaWiki feature that would be particularly helpful to have on Wikimedia wikis.
+
+> *For more detail on each point; this is not, as MzMcBride claims, ""a general
+> MediaWiki enhancement"" unless you want to expand the definition to cover pretty
+> much anything.
+
+It seems like a fairly standard enhancement to me.
+
+> It introduces a completely new workflow, alters existing ones
+> and sticks a big button on the (already overfilled) page that we know all
+> editors are going to see. There is no way this can be turned on without a
+> community discussion unless you want a raging storm of anger hurled in the
+> direction of whoever hits the big red button.
+
+I'm not sure I understand what you're saying here. Microsoft Word has auto-save; WordPress has auto-save; modern Web browsers have auto-save. Who do you think will be shouting about this being enabled? Is there any evidence of this being a controversial feature?
+
+> *The UI elements clash with current thinking about the direction that we're
+> going in. The Micro Designs Improvement project is currently working on the
+> edit window as we speak, and plans to do a couple more iterations given the
+> opportunity. I'd rather not throw two competing philosophies of design into the
+> mix - that works if they're from the same team, but I worry we'd end up with
+> (at best) an inconsistent UI and (at worst) an active clash.
+
+I'm not sure how this is relevant. Other parts of the edit view need work, yes.
+
+> *This really doesn't seem an efficient way to do things. What's the use case
+> here, exactly? If it's ""people would like to save a draft in case they lose
+> their work"", save the draft automatically after [number] of minutes or seconds
+> rather than requiring them to actually make a decision, and then just void any
+> drafts after [other number] of minutes or seconds.
+
+This extension pretty much does exactly that, doesn't it? I don't think the current version of this extension is as heavy-handed about auto-discarding drafts as you suggest it could be, but that seems like a feature to me, not a bug.
+
+> If it's ""we want to sort how
+> confusing the existing setup is by offering functions found on other sites"",
+> integrate that into the existing workflows to avoid button bloat. At
+> https://www.mediawiki.org/wiki/Extension:Drafts I'm seeing edge cases discussed
+> and the workflow discussed...but not how this in any way can be integrated into
+> how Wikipedia currently works, or how we'd like it to work, or what exactly the
+> use case is for this software. If there is a use case, it needs to be
+> communicated. If there isn't, we shouldn't be turning it on.
+
+I didn't follow most of this section, so I'm not quite sure how to respond.
+
+> *Can someone point me to, if not a use case, the user demand for this feature?
+> One power user requesting it on bugzilla is not a case for change.
+
+You can't formulate a use-case for a drafts feature in your head? Interesting. You've been editing Wikipedia for how many years now? You've never wanted to create a draft of something? :-)
+
+As for the ""one power user"" comment, when you look at the history of the development of the extension (which you apparently didn't) and you look at related bugs (such as bug 19909), you can see that your comment doesn't make much sense. I'm not sure what you gain by trying to act as though there's only person pushing for auto-save functionality on Wikimedia wikis.
+
+> This is not to say that it isn't useful, or that this type of feature isn't the
+> sort of thing we should be looking at - as mentioned above, reforming the
+> editing workflows is something that is being discussed and worked on. I'm just
+> skeptical that this particular information, particularly deployed in this
+> fashion, is going to benefit more than it costs.
+
+""The extension needs a bit of work before deployment. Water is also wet. You can safely ignore the last few paragraphs I wrote.""",1347750601,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #15)
+> Really? Who makes these saves? And if this is a common use case, could we have
+> an on-wiki demonstration that people need or want it? :)
+Ok. I just created a topic on enwiki for this:
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)#Allowing_users_to_save_drafts_of_their_work
+
+(and there was the other one on ptwiki, mentioned on comment 13).",1347747627,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I have to say, I'm with Oliver here.  I have concerns about deployment on a wide scale without some further feature development and (more importantly) community input and buy-in.  It seems to me that there are policy and governance changes that also need to be introduced at the same time, and it would be courteous to let the community work on those with some warning.
+
+I also have UI challenges with this.  It's not immediately transparent how it works to a new user (where is the integration to contribution history or recent changes?), and (while I haven't seen the documentation) I suspect that the documentation is also not user-ready.  I would hope that the UI takes advantage of some of the knowledge gained through the past year's experimentation rigor, rather than charting a course that may or may not make sense.  
+
+With all that said, I agree with MZMcBride's intent in moving this forward - limbo is a terrible place, and when promising tools are stuck there, it's frustrating.  We SHOULD improve the pipeline; but let's do it intelligently.
+
+Philippe",1347746393,PHID-USER-gk4enxd23ebojohiq7rf,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #15)
+> Really? Who makes these saves? And if this is a common use case, could we have
+> an on-wiki demonstration that people need or want it? :)
+
+A DB query will give you plenty of examples. ;)
+
+> I'm not a developer either. However, I consider needlessly complicating the UI
+> interface or introducing new workflows without consulting people in advance or
+> having a firm use case that we actually know occurs to be a core problem with
+> what's being discussed - regardless of what's being discussed.
+
+As I already said, I don't think this introduces new workflows, except when the workflow is ""rewrite everything from scratch because you've lost all you wrote"" or ""save every 30 s to avoid losing everything"". And no, I can't imagine anyone who could dislike this feature intervening in such cases.",1347745859,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Really? Who makes these saves? And if this is a common use case, could we have an on-wiki demonstration that people need or want it? :)
+
+I'm not a developer either. However, I consider needlessly complicating the UI interface or introducing new workflows without consulting people in advance or having a firm use case that we actually know occurs to be a core problem with what's being discussed - regardless of what's being discussed.",1347745340,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #12)
+> *Can someone point me to, if not a use case, the user demand for this feature?
+
+The use case and user demand is the hundreds or thousands of users saving their edits every couple of minutes and so for fear of losing everything.
+I'm not a developer but the points you raise, although very important, don't seem to be blockers, rather marginal ones. 
+For instance, removing the button by default seems a reasonable solution, as long as the user understands what's going on (just a small notice every time the draft is saved?). A configuration variable could be used to enable the button for wikis which desire it.",1347744717,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I've asked on Portuguese Wikipedia a few days ago:
+http://pt.wikipedia.org/wiki/Project:Esplanada/propostas/Instalar_extens%C3%A3o_para_salvar_rascunhos_(1set2012)?uselang=en
+
+So far, no one opposed it, but one of the users asked if we could test it somewhere. According to
+http://www.gossamer-threads.com/lists/wiki/wikitech/278043
+the extension was installed by [[User:Petrb]] on
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:Drafts
+but the link is not working right now.",1347744546,PHID-USER-sryrz6tgcfnnsiddx32p,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"TL;DR, I really oppose turning this on with the way it's formatted now and using the process that's being discussed.
+
+*For more detail on each point; this is not, as MzMcBride claims, ""a general MediaWiki enhancement"" unless you want to expand the definition to cover pretty much anything. It introduces a completely new workflow, alters existing ones and sticks a big button on the (already overfilled) page that we know all editors are going to see. There is no way this can be turned on without a community discussion unless you want a raging storm of anger hurled in the direction of whoever hits the big red button.
+
+*The UI elements clash with current thinking about the direction that we're going in. The Micro Designs Improvement project is currently working on the edit window as we speak, and plans to do a couple more iterations given the opportunity. I'd rather not throw two competing philosophies of design into the mix - that works if they're from the same team, but I worry we'd end up with (at best) an inconsistent UI and (at worst) an active clash.
+
+*This really doesn't seem an efficient way to do things. What's the use case here, exactly? If it's ""people would like to save a draft in case they lose their work"", save the draft automatically after [number] of minutes or seconds rather than requiring them to actually make a decision, and then just void any drafts after [other number] of minutes or seconds. If it's ""we want to sort how confusing the existing setup is by offering functions found on other sites"", integrate that into the existing workflows to avoid button bloat. At https://www.mediawiki.org/wiki/Extension:Drafts I'm seeing edge cases discussed and the workflow discussed...but not how this in any way can be integrated into how Wikipedia currently works, or how we'd like it to work, or what exactly the use case is for this software. If there is a use case, it needs to be communicated. If there isn't, we shouldn't be turning it on.
+
+*Can someone point me to, if not a use case, the user demand for this feature? One power user requesting it on bugzilla is not a case for change.
+
+This is not to say that it isn't useful, or that this type of feature isn't the sort of thing we should be looking at - as mentioned above, reforming the editing workflows is something that is being discussed and worked on. I'm just skeptical that this particular information, particularly deployed in this fashion, is going to benefit more than it costs.",1347743734,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Could we see this put up on a labs instance somewhere? I have several concerns, but I'm not sure how valid they are because I can't actually see an example of the software in use - which is an issue.",1347742158,PHID-USER-j5ma2nageni56xp567v5,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**sumanah** wrote:
+
+Trevor is continuing to work on Drafts for about one day a week, fixing bugs, improving database handling, adding ResourceLoader and jQuery integration, and so on.",1347485723,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**swalling** wrote:
+
+(In reply to comment #4)
+> Consensus?
+
+This is also a feature that someday would have been tested anyway for new page creation. See also: https://www.mediawiki.org/wiki/Article_Creation_Workflow/Design",1346369067,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**sumanah** wrote:
+
+Trevor is looking at this extension for review & improvement.  See https://gerrit.wikimedia.org/r/#/q/project:mediawiki/extensions/Drafts+-owner:L10n-bot,n,z .",1346342384,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,-shell; nothing for ops to do yet. Extension needs review and improvements first.,1343434370,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #5)
+> (In reply to comment #4)
+> > Consensus?
+> 
+> I believe this extension falls under general MediaWiki enhancements and doesn't
+> require local community consensus to enable.
+> 
+> Do you feel otherwise? If so, how would you recommend moving forward?
+
+I'd agree with you. It should be an unobtrusive benefit for anyone with a browser that works with it.
+
+And even then, it's got a preference to turn it on/off",1343422972,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #4)
+> Consensus?
+
+I believe this extension falls under general MediaWiki enhancements and doesn't require local community consensus to enable.
+
+Do you feel otherwise? If so, how would you recommend moving forward?",1343419866,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,Consensus?,1343377587,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #2)
+> (In reply to comment #1)
+> > I guess step one is to get the code into Git/Gerrit. CC'ing Sam and Chad about
+> > that.
+> 
+> On it, will be done shortly.
+
+Done, https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Drafts",1340828567,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #1)
+> I guess step one is to get the code into Git/Gerrit. CC'ing Sam and Chad about
+> that.
+
+On it, will be done shortly.",1340826848,PHID-USER-oetk6bbl6omm354ejz3b,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,I guess step one is to get the code into Git/Gerrit. CC'ing Sam and Chad about that.,1340822766,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"[Suggestion from community.]
+
+Copy-pasting in an image to the editor should automatically upload it to the wiki and insert it into the article.
+
+After/on insertion (but before saving) the editor should be prompted to add meta-data (e.g. name, licence, source, ...).
+
+I'd imagine we'd be less likely to accept this for Wikimedia wikis, but others (Wikia?) might be interested.
+
+**See Also**: {T23557}",1340644620,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-usebfh653647q2fmkkwk,task_description,resolved
+VisualEditor: Upload-by-insertion of images via copy-paste,@matmarex Will do. Thank you for the response :),1541192975,PHID-USER-cb53pyjz3ccu7fvgd7m2,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"> See recording here: https://cloud.jackalope.tech/s/example
+
+(Here's the same, for future reference in case that URL becomes unavailable, and in smaller size to save folks a 200 MB download.)
+
+{F26990564}",1540950373,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,">>! In T39932#4708065, @Thedonquixotic wrote:
+> Hi @matmarex It does appear to work with copy pasting from paint but it doesn't work when copying pasting an image from another browser tab. 
+
+Interesting. Turns out that when you copy an image in the browser, it is stored in the clipboard in two formats: as the actual image, and as HTML like this:
+```
+<html>
+<body>
+<!--StartFragment--><img src=""https://apod.nasa.gov/apod/image/1705/Arp273Main_HubblePestana_3079.jpg"" alt=""Image result for galaxy""/><!--EndFragment-->
+</body>
+</html>
+```
+
+When this is pasted into VisualEditor, we use the HTML instead of the image (ve.ce.Surface.prototype.handleDataTransfer), because:
+```
+	// Only look for files if HTML is not available:
+	//  - If a file is pasted/dropped it is unlikely it will have HTML fallback (it will have plain text fallback though)
+	//  - HTML generated from some clients has an image fallback(!) that is a screenshot of the HTML snippet (e.g. LibreOffice Calc)
+```
+
+Then our paste sanitization strips that HTML down to nothing (since `<img>` tags using external resources are not possible in wikitext), and then nothing is pasted.
+
+@Thedonquixotic Can you file a separate task about this?
+
+(As a workaround, I guess you can paste into Paint, then copy from Paint.)",1540950367,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Hi @matmarex It does appear to work with copy pasting from paint but it doesn't work when copying pasting an image from another browser tab. 
+
+See recording here: https://cloud.jackalope.tech/s/example
+
+",1540942186,PHID-USER-cb53pyjz3ccu7fvgd7m2,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Hi @matmarex It does appear to work with copy pasting from paint but it doesn't work when copying pasting an image from another browser tab. 
+
+See recording here: https://cloud.jackalope.tech/s/example-copypaste  
+
+",1540942130,PHID-USER-cb53pyjz3ccu7fvgd7m2,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"(Also, we forgot to close this task in April 2017 when it was fixed, whoops.)",1540863713,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"File upload by copy-paste definitely still exists and works, I just tested it. However, it seems like there is a bug and the media dialog opens on the wrong tab when a file is pasted (or dragged and dropped). You can still complete the upload if you switch to the other tab. See demonstration:
+{F26972710}
+I filed T208286 about this issue.",1540863690,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,@Florian Sorry to bother on this old ticket but I don't see how to do this in my current (1.31) installation of Mediawiki with Visual Editor enabled. Is this feature still in mediawiki or has it been taken out?,1540769905,PHID-USER-cb53pyjz3ccu7fvgd7m2,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 339400 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWMediaTransferHandler: Allow uploading of dropped Blobs
+
+[[https://gerrit.wikimedia.org/r/339400]]
+",1493321563,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 288773 abandoned by Bartosz Dziewoński:
+WIP: Add possibility to paste a file to the document
+
+Reason:
+Apparently no longer needed? https://gerrit.wikimedia.org/r/339400 also works. It's not clear to me why we couldn't do that before.
+
+[[https://gerrit.wikimedia.org/r/288773]]",1493321068,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 339400 had a related patch set uploaded (by Jforrester; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Allow uploading of dropped Blobs
+
+[[https://gerrit.wikimedia.org/r/339400]]
+",1493245940,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Quick video of the change above:
+https://youtu.be/IuWaxS7mOBA",1463330808,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 288773 had a related patch set uploaded (by Florianschmidtwelzow):
+WIP: Add possibility to paste a file to the document
+
+[[https://gerrit.wikimedia.org/r/288773]]
+",1463330633,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 288773 had a related patch set uploaded (by Florianschmidtwelzow):
+WIP: Add possibility to paste a file to the document
+
+[[https://gerrit.wikimedia.org/r/288773]]
+",1463247437,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Interesting idea, I'll try to upload a first change for it :)",1463240041,PHID-USER-c5xwrfdyp3dckkh2nkoj,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,Bumping down priority.,1367089009,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"**orbit** wrote:
+
+I've been taking copy-paste related tickets.",1349897395,PHID-USER-ynivjflmc2dcl6w5ut5v,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Tweaking summary to clarify this is for HTML copy-paste -- if we get a full URL to the web then this should be doable. If we get a relative URL or something on the local filesystem, there's less we can do. :)
+
+Drag-and-drop of files or similar would be a separate concern.",1340651137,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+"VisualEditor on Opera 12: editing existing link doesn't work, breaks selection logic","Testing in Opera 12 on Mac
+
+Steps:
+* open https://www.mediawiki.org/wiki/VisualEditor:Welcome
+* hit 'edit'
+* select a link
+* hit link button
+
+Expected behavior:
+* link dialog pops up, lets you change the link
+
+Actual behavior:
+* nothing... usually
+* sometimes - nothing, followed by the next attempt opening a link dialog at your first selection
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340419620,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-mdlouwe6duqgfyx233gy,task_description,resolved
+"VisualEditor on Opera 12: editing existing link doesn't work, breaks selection logic",This shouldn't be happening anymore now that all dependencies are fixed. Rejoice!,1375118502,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-mdlouwe6duqgfyx233gy,task_subcomment,NA
+"VisualEditor on Opera 12: editing existing link doesn't work, breaks selection logic","Opera is not currently a target browser, so marking this as ""Lowest"" priority.",1354811733,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-mdlouwe6duqgfyx233gy,task_subcomment,NA
+"VisualEditor on Opera 12: clicking selection arrow shows, then hides popup bar","Testing in Opera 12 on Mac
+
+After making a selection, the little arrow shows up which you can click for a popup formatting bar. In Opera, the bar pops up then immediately hides itself, so can't be used.
+
+This also kills the selection.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340418600,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-qz33ogip6xbczaatjhcs,task_description,invalid
+"VisualEditor on Opera 12: clicking selection arrow shows, then hides popup bar",This refers to the inspector menu trigger icon that was removed in late-2012. Marking as INVALID as it doesn't matter any more.,1367028832,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qz33ogip6xbczaatjhcs,task_subcomment,NA
+"VisualEditor on Opera 12: clicking selection arrow shows, then hides popup bar",What arrow? I don't see one in neither Opera not Firefox.,1367017176,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-qz33ogip6xbczaatjhcs,task_subcomment,NA
+"VisualEditor on Opera 12: clicking selection arrow shows, then hides popup bar","Opera is not currently a target browser, so marking this as ""Lowest"" priority.",1354811747,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-qz33ogip6xbczaatjhcs,task_subcomment,NA
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"Selecting text from end to beginning with the mouse in Opera 12 doesn't work properly; the selection keeps resetting itself, so you end up with no selection.
+
+Selecting end to start via keyboard (shift+arrow keys) works as expected.
+
+Selecting from start to end works as expected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340418480,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_description,resolved
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"I poked around. This appears to have been fixed by I0873d906 together with bug 42925.
+
+Lesson for today: Opera bugs often highlight hidden non-Opera bugs ;)
+
+*** This bug has been marked as a duplicate of bug 42925 ***",1355350453,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_subcomment,NA
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"This currently appears fixed on en.wiki. What happened, and is it going to break itself again? :)",1355349532,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_subcomment,NA
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"I've determined the issue to happen within ve.ce.Surface.prototype.showSelection, which, every time a selection is made, removes it and adds it back (after the code path goes through two events called via the .emit() system). 
+
+I have also determined that the bug only happens when you're not debugging; setting apparently any breakpoint prevents it. Gotta be something timing-sensitive, but I don't know the codebase well enough to investigate (or, in fact, at all).",1354817818,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_subcomment,NA
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"Opera is not currently a target browser, so marking this as ""Lowest"" priority.",1354811757,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"The VisualEditor does not display when using Opera. The header ""Visual editor sandbox"" is the only thing displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1334532780,PHID-USER-um3fhlwaza6ecwf67t77,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_description,resolved
+VisualEditor: Does not work in Opera (tracking),No outstanding bugs against this tracker; closing.,1375126546,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"Change 72738 merged by jenkins-bot:
+Unblacklist Opera >= 12
+
+https://gerrit.wikimedia.org/r/72738",1375126428,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"Change 72738 had a related patch set uploaded by Matmarex:
+Unblacklist Opera >= 12
+
+https://gerrit.wikimedia.org/r/72738",1373385725,PHID-USER-idceizaw6elwiwm5xshb,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"[Reopening as a tracking bug and assigning to myself.]
+
+The current dependencies are the things that IMO are blockers to enabling VE for Opera users again.",1367169919,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"Yair Rand: Since the time of your posting, The Visual Editor surface has been completely rewritten and is based on Content Editable.
+
+Content Editable is supported in Opera 12 and above.
+
+Browsers that support contentEditable here:
+http://caniuse.com/#search=contentEditable
+
+Closing bug.",1343344311,PHID-USER-pun3sjvg3cemjzbgyo2t,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),Seems to work in Opera 12 on a quick spot-check.... but there's a few problems. I'll file bugs and stack them on this one.,1340417922,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),To check if this is still current.,1340404043,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),Mass-moving items into VisualEditor product,1340402746,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+Implement minification for SVG files in ResourceLoader,"This task is about implementing a high performance minifier for SVG content. It will also track the use of that minifier when embedding SVG files in file modules through CSSMin. 
+
+**See Also**:
+* {T175318}
+* {T61086}
+
+Task T61086 tracks the use of this minifier (once implemented) by ResourceLoaderImage for SVGs served from that endpoint.
+
+--------------------------
+
+>>! **Original report**:
+> 
+> 
+> This comes from bug 34810 (T36810)... Which could use this feature to dynamically do it (or the simpler older method of creating .min files)
+> 
+> SVG are used as non page content files, they contain a lot of whitespace. Minify and serve!
+> 
+
+",1330547040,PHID-USER-6vzzsmi22zem6yttr6vp,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_description,open
+Implement minification for SVG files in ResourceLoader,Raising priority per T59777. We're using more SVGs nowadays.,1430242878,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_subcomment,NA
+Implement minification for SVG files in ResourceLoader,*** Bug 63491 has been marked as a duplicate of this bug. ***,1410989371,PHID-USER-wkpnidxoctuhawexig5p,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_subcomment,NA
+Implement minification for SVG files in ResourceLoader,"I think we can apply the same as PNG files.
+
+I don't know of any SVG files we have in our repository that we manually edit to the level that can't aren't already be minified (they might have some indentation, but that's about it, and we could actually minify those in the repository, like we optimise PNG files).
+
+I know SVG is text where PNG is not, but unless we actually edit them, it should be fine.
+
+As for solving this bug, if we want to minify SVGs in separate requests (e.g. fonts), that would get quite tricky. They'd need a url to be served from.
+
+As for SVGs we embed in CSS (SVGs for icons like we do in VisualEditor), those could be easily minified before being base64 encoded (that is, once we have an xml minifier).",1362551377,PHID-USER-sai77mtxmpqnm6pycyvz,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_subcomment,NA
+Implement minification for SVG files in ResourceLoader,"There's several possible things to do here:
+
+* transparent HTTP gzip compression (can be enabled at webserver-level)
+* stripping comments and whitespace (traditional 'minification', could be done as a pre-processing step)
+* intelligent collapsing of redundant attributes and styles (harder!)
+* rounding coordinates to fewer digits
+* decimating points in overly-detailed polygons/curves
+
+Depending on just what you're trying to do, you could do some or all of those...
+
+For SVG fonts I'd recommend that they be relatively sane to begin with (if they're full of whitespace and comments as output assets, that's kinda lame -- they should be small/clean to begin with), and use transparent gzip compression on the web server configuration.",1330557265,PHID-USER-yek7ymogrv4qc67oilhf,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_subcomment,NA
+Polish : Editing tools (VisualEditor and WTE) should display to user when server connection has been lost,"This will reduce instances where user submits changes and receives an error, possibly resulting in data loss. 
+see — http://github.hubspot.com/offline/",1415513322,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-bzskyradcmgpuo2efgwc,task_description,open
+Polish : Editing tools (VisualEditor and WTE) should display to user when server connection has been lost,"Tagging with VE-ME and WikiEditor as this is the first time I've stumbled over this, and we might want to come back to it.
+
+Dropping ""easy"" because it isn't. Anyone tempted to try to work on this needs to have a serious long conversation with me and Operations about how we could do this in a way that doesn't over-load the servers and take down Wikipedia.",1465833995,PHID-USER-ydswvwhh5pm4lshahjje,PHID-TASK-bzskyradcmgpuo2efgwc,task_subcomment,NA
+Polish : Editing tools (VisualEditor and WTE) should display to user when server connection has been lost,"Then we might want to only alert at critical times, like when edit summary is open or when save is pressed prior to actually submitting, e.g. disable save if connection can't be restored. ",1415566359,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-bzskyradcmgpuo2efgwc,task_subcomment,NA
+Polish : Editing tools (VisualEditor and WTE) should display to user when server connection has been lost,The editors do not keep a constant connection open to the server.,1415552047,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-bzskyradcmgpuo2efgwc,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"We have three problems related to calendars that need to be resolved, which are related but perhaps may be fixed separately, even at different points in time:
+
+* **Introducing calendar data**. Now we are doing this in 1001 places. Ideally it would be just one place. The assumption of this task is that the one place would be Phabricator's calendar ([[ https://secure.phabricator.com/T7924 | today a prototype ]]), but other candidates should be considered.
+* **Pulling calendar data in other supports, mainly wiki pages**. While we could start linking from wiki pages to Phabricator calendar queries, the desired scenario would be a way for editors to embed calendars based on queries in wiki pages. This probably implies a Calendar API to query data ([[ https://secure.phabricator.com/T7944 | which is missing ]]) and a MediaWiki extension allowing to embed those queried calendars in wiki pages (which we don't have). Maybe this is just too much, and at least the tech-inclined Wikimedians would be fine clicking a Phabricator link.
+* **Integrating calendar data with other systems (mainly Google Calendar)**. ""[[ https://secure.phabricator.com/T7929 | Future work ]]"" upstream, no plans today.
+
+As we can see, deciding on Phabricator Calendar as the one place to introduce data would not provide a quick path to use that data out of Phabricator. However, what would be the alternatives? Other than defaulting to Google Calendar (which I think would be wrong as a matter of Wikimedia principles), I don't see a shortcut but others may have better ideas.
+
+== Phabricator Calendar in a nutshell ==
+
+After playing a bit with https://phabricator.wikimedia.org/calendar/, I think the most practical option is to focus on having that calendar up to date, and then link to it from the right places in mediawiki.org.
+
+* Entering events is simpler. The usual you can expect in a calendar application. There is no need to archive past events, since this is done automatically.
+* Users can RSVP, getting notifications about the event and letting others know that they are attending.
+* The calendars shown are the result of queries allowing for multiple parameters, including month view vs list, show only upcoming events, etc. These queries have static URLs.
+* Events can be assigned to projects, which means that
+** We could have projects for i.e. Tech Talks, Technical Office Hours, etc, people could subscribe to these projects and receive notifications when a new event is filed.
+** By adding an event to existing related projects (i.e. #Web-APIs-hub, #Google-Summer-of-Code-2015), users following that project would receive notifications as well.
+** Queries can be fine tuned to show a specific set of events.
+
+If we agree on this, the implementation would be relatively simple, since (at least in Wikimedia tech) a few people create most of the events. Redirecting from the current calendar pages to their equivalent Phabricator calendar queries should be enough to tell current users about these calendars about the new way to create new events.
+
+=== Basic review of existing MediaWiki extensions ===
+
+I went through https://www.mediawiki.org/wiki/Extension:Calendar (a linkhub for the ~12 different extensions or methods of integrating calendars with MediaWiki). There was no extension surviving a basic check against our needs. In fact, most of them are more than abandoned, and in general they focus on presentation, not on easy input, even less on semantic data (except the SemanticMediaWiki one, perhaps). [[ https://www.mediawiki.org/wiki/Extension:SimpleCalendar | SimpleCalendar ]] looks like the only candidate if we would ever want to start from this point.
+
+The reason for a lack of a proper MediaWiki Calendar extension may well be that MediaWiki was not designed to input calendar data, subscribe to events, etc.
+
+After this short investigation, I still think that it is better to start from something other than MediaWiki, and the main candidate keeps being Phabricator. Then work separately in a way to import Phabricator Calendar data and present it in MediaWiki pages.
+
+=== Background / previous description ===
+
+https://www.mediawiki.org/wiki/Project:Calendar has a lot of room for improvement. Creating tasks is not trivial, and although the calendar can be watched and the entries appear in the mediawiki.org homepage, it doesn't have any of the features expected nowadays in an online calendar, i.e. integration with the calendar apps people use to organize their lives.
+
+Also, for some low hanging fruit, a reporter explains in an email:
+> the whole project:calendar page hierarchy is confusing - I would avoid subpages at more than one level deep
+> It's not clear to me why this page is in the Project: namespace to begin with
+> https://www.mediawiki.org/wiki/Project:Namespaces seems to suggest the Project: namespace is for ""organization of mediawiki.org"", which does not describe this page
+> see https://meta.wikimedia.org/wiki/Tech for a better way to provide consistent navigation/page structure across a set of dispersed pages without use of subpages you asked :)",1415025314,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_description,declined
+Consolidate the many tech events calendars in Phabricator's calendar,"I would not reopen but keep this declined. Phabricator Calendar is a rudimentary ""Prototype"" application which currently lacks a few things.",1611614207,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Should this be reopened since Space has been abandoned?,1611613347,PHID-USER-bvi77f4zkvm3mrkrqvwp,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Yes, agreed.",1563807275,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Boldly declining this in favor of https://discuss-space.wmflabs.org/c/events/l/calendar,1563466400,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Also note that https://discourse.wmflabs.org/c/12-local-events exists now.,1531658546,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I'd propose to revert 2015's T1035#1579199 and go back to the original task scope.
+
+> We can use Developer-Wishlist (2017) to check how much interest there is for this idea.
+#66 out of 76, for the records.",1528549290,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Meanwhile, Meta seems to be moving to a wiki-based calendar: https://meta.wikimedia.org/wiki/Template:Events_calendar",1528195216,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"[See Also] Similar task for (non-technical) Education events, wondering where they should put such a potential calendar: {T111968}",1523261235,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,WMFR also worked on something on-wiki: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=831389270#Events_calendar,1521541032,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I keep not having time to even start thinking seriously on this task, and I believe it is better to reflect reality.",1519735180,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,This task is now a #goal. I need to update the description.,1507103115,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I realize this is well-underway but I recently came across [[ https://hackshackers.github.io/misinfocon-event-calendar/ | this public events calendar ]] and really liked the format and the code is [[ https://github.com/hackshackers/misinfocon-event-calendar | up on GitHub ]] so I thought I would share as a stickie in case there are future revisions planned down the road.
+
+(I also realize this could be a totally annoying update given the status of the project so if it's irrelevant, please ignore and forget this message ever existed. :))",1496150582,PHID-USER-w5dqcsw7esxdqy3say2e,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#3104260, @Aklapper wrote:
+> * DONE: [[ https://secure.phabricator.com/T10747 | Import and export ICS from Calendar ]]
+
+Pretty useless though in its current form as there is no stable export URL (the ""export"" link just takes you to a web page that initiates download of the actual file via JS) so you cannot plug an URL into your calendar client and get changes to the event automatically synced.
+
+> * DONE: [[ https://secure.phabricator.com/T7929 | Integrate Calendar with external systems ]]
+
+Declined, actually (upstream uses task statuses in weird ways), except for Google Calendar integration, which has not been done yet.",1496148909,PHID-USER-a6p24cvyblhfzc7we7nc,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Removed parent task T136213 as the technical side seems to be done.,1494331203,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Agreed.,1489757391,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Status update of related upstream tasks:
+* DONE: [[ https://secure.phabricator.com/T10747 | Import and export ICS from Calendar ]]
+* DONE: [[ https://secure.phabricator.com/T7944 | Add Conduit support to Calendar ]]
+* DONE: [[ https://secure.phabricator.com/T7929 | Integrate Calendar with external systems ]]
+* [[ https://secure.phabricator.com/T7924 | Unprototyping the calendar application ]] in upstream has not happened. It only depends on 
+** [[ https://secure.phabricator.com/T7930 | Let Calendar provide date services to other applications ]] 
+** and potentially [[ https://secure.phabricator.com/T8022 | Implement a meeting autoscheduler ]] (listed in task deps but not in task desc).
+The first item is likely still a blocker (Google Calendar being popular) for this very downstream task T1035, while I think the second might not be that crucial for us?",1489616971,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"This project is selected for the #developer-wishlist voting round and will be added to a MediaWiki page very soon. To the subscribers, or proposer of this task: please help modify the task description: add a brief summary (10-12 lines) of the problem that this proposal raises, topics discussed in the comments, and a proposed solution (if there is any yet). Remember to add a header with a title ""Description,"" to your content. Please do so before February 5th, 12:00 pm UTC. ",1486164935,PHID-USER-dho6cgabdzx4ehinmzcd,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,We can use #devwish17 to check how much interest there is for this idea.,1484641614,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Re DevSummit: Hmm, I'm not convinced. ""Dealing with calendar data in the Wikimedia movement""?",1477587409,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Would this task be a good topic for the #wikidev17 ? If so, the deadline to submit new proposals is next Monday, October 31: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation",1477576972,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2698874, @Qgil wrote:
+> I just 
+> 
+> # created {E329}
+> # clicked ""Export as .ics"", and an .ics file was downloaded to my laptop
+> # imported the .ics file to my Google Calendar
+> 
+> The event is now visible in my calendar. Progress!
+
+So as in mine. I don't know if it was the expected result. ;)",1475848243,PHID-USER-uciss2jl2e4ifxqqk7wk,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"There is more coming (just landing in Phabricator HEAD, not stable yet):
+
+https://secure.phabricator.com/book/phabricator/article/calendar_exports/",1475847624,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I just 
+
+# created {E329}
+# clicked ""Export as .ics"", and an .ics file was downloaded to my laptop
+# imported the .ics file to my Google Calendar
+
+The event is now visible in my calendar. Progress!",1475829026,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I just 
+
+# created {E329}
+# clicked ""Export as .ics"", and an .ics file was downloaded to my laptop
+# imported the .ics file to my Google Calendar
+
+It's there. Progress!",1475828997,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I just created {E329}, then clicked ""Export as .ics"", then import to my Google Calendar. It's there. Progress!",1475828903,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,(Aforementioned deployment postponed due to Ops offsite),1475177370,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,@qgil: That will land in our phabricator tomorrow night (midnight UTC) when I deploy #phab-2016-09-28 ,1475015490,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Initial support for ICS export is available in Phabricator HEAD, and the work is continuing as we speak -- see https://secure.phabricator.com/T10747
+
+I am counting on this ICS support for this proposal: {T146749}",1474981509,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Punting to Oct-Dec for Dev-Rel. 
+Not to happen this quarter as long as T136213 isn't resolved which is external.",1474644859,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@CKoerner_WMF - as I noted earlier, Semantic MediaWiki was declined for use on Wikipedia, in favor of Wikidata. (Which was the right choice.) I don't believe it has ever been reviewed for use on, say, mediawiki.org.
+
+And - though I'm repeating myself - Cargo is, in my opinion, the better option. But either one would work.",1466023933,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Just to chip in my $.02, I would encourage us to look for a solution that can be used on-wiki. There's something about investing time/money/energy in on-wiki solutions that sits better with me. Maybe it has to do with an on-wiki solution being more inviting. People without or only entry level development skills will find the information easier than here in phabricator, where super dev skills are the norm. :)
+
+I understand that SMW was declined many years ago. What were the reasons for the declination? It's not clear to me if those still stand today. Could those be addressed?
+
+@Yaron_Koren You're far more savvy with this than I, but does SMW meet these requirements? https://wikitech.wikimedia.org/wiki/Writing_an_extension_for_deployment
+
+My personal bias aside, SMW seems like a present solution that is free, on-wiki, adaptable, and within our own MediaWiki community. Much different than spending money on a one-time development of a feature from an outside vendor. Ok, that was totally biased. ",1466022679,PHID-USER-iwx53fdq7w3yv4h7wffx,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Just a reminder that if, say, Cargo and Semantic Forms were installed on mediawiki.org today, there would be functioning event-entry forms and event calendars on the site, probably by the end of the day. (And at no cost.)",1466010033,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wikimedia groups like WMES don't need to install their own Phabricator instance. They can use Wikimedia Phabricator instead.
+
+Only the users willing to introduce and manage calendar data would need to create an account here (which they can do with their Wikimedia accounts). Users only needing to access that data can visit the URLs of the calendars they are interested about, and according to this proposal they will be able to import Wikimedia Phabricator calendar data to their own calendars importing the iCalendar files (.ics)
+
+Users with a Phabricator account are able to RSVP, comment, and associate events to other projects (promoting activities to the users following those projects).
+
+@BrillLyle, we are not trying to compete with Google Calendar, but I think we can aim to provide the basic functionality that most people may need for Wikimedia activities. From your list:
+
+* Time zone support. Events are created with the timezone of the event creator, and that [[ https://phabricator.wikimedia.org/settings/panel/datetime/ | timezone can be defined ]] in the user profile. As of today, events cannot be created in a different timezone, but this is a problem with a simple workaround (find out the time in your own timezone). Not a blocker.
+
+* Color coding. Missing indeed. Icons can be defined for events, and if this is considered important then perhaps colors could be defined as well, just like it is possible to define icons and color for projects. This looks like an improvement simple to implement that would provide basic color cues in calendars.
+
+* Ability to select and maintain different calendars. This is possible, by associating events to projects (i.e. ArchCom meetings, Tech Talks, Wikimania Hackathon 2016...) and by [[ https://phabricator.wikimedia.org/calendar/query/advanced/ | querying events ]] in a pretty advanced way (i.e. IRC Office Hours about VisualEditor during 2015, displayed in month view). These queries provide static URLs that can be shared with users.
+
+* Ability to copy to events to personal calendar. Phabricator users can RSVP already now, and this will make events appear in their personal Phabricator calendar. According to this proposal, they will be able to import the .ics data as well, which will integrate such data in their calendar apps.",1463465173,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wikimedia groups like WMES don't need to install their own Phabricator instance. They can use Wikimedia Phabricator instead.
+
+Only the users willing to introduce and manage calendar data would need to create an account here (which they can do with their Wikimedia accounts). Users only needing to access that data can visit the URLs of the calendars they are interested about, and according to this proposal they will be able to import Wikimedia Phabricator calendar data to their own calendars importing the iCalendar files (.ics)
+
+Users with a Phabricator account will be able to RSVP, comment, and associate events to other projects (promoting activities to the users following those projects).
+
+@BrillLyle, we are not trying to compete with Google Calendar, but I think we can aim to provide the basic functionality that most people may need for Wikimedia activities. From your list:
+
+* Time zone support. Events are created with the timezone of the event creator, and that [[ https://phabricator.wikimedia.org/settings/panel/datetime/ | timezone can be defined ]] in the user profile. As of today, events cannot be created in a different timezone, but this is a problem with a simple workaround (find out the time in your own timezone). Not a blocker.
+
+* Color coding. Missing indeed. Icons can be defined for events, and if this is considered important then perhaps colors could be defined as well, just like it is possible to define icons and color for projects. This looks like an improvement simple to implement that would provide basic color cues in calendars.
+
+* Ability to select and maintain different calendars. This is possible, by associating events to projects (i.e. ArchCom meetings, Tech Talks, Wikimania Hackathon 2016...) and by [[ https://phabricator.wikimedia.org/calendar/query/advanced/ | querying events ]] in a pretty advanced way (i.e. IRC Office Hours about VisualEditor during 2015, displayed in month view). These queries provide static URLs that can be shared with users.
+
+* Ability to copy to events to personal calendar. Phabricator users can RSVP already now, and this will make events appear in their personal Phabricator calendar. According to this proposal, they will be able to import the .ics data as well, which will integrate such data in their calendar apps.",1463464977,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@Qgil  Wouldn't that require that each of our members created an account here? (Not that this was available until recently, so it's no wonder it hadn't been brought up as anoption). It may be worth trying, though.
+
+And installing a local phabricator instance… no, thanks.",1463447343,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@Qgil -- Hi Yes I have looked at the **[[ https://phabricator.wikimedia.org/calendar/query/month/ | Phabricator Calendar ]].** It seems fine but there are some significant things missing that would mean loss of functionality. (i.e., time zone support, color coding, ability to select and maintain different calendars, ability to copy to events to personal calendar, etc.). It also requires end users sign in using OAuth and have a Phabricator account, correct? We have problems getting participants onboarded to the en-Wiki so this is another thing that I'm just thinking of. Unless this solution was fully integrated with Wikipedia where it would not require logging in to another system to easily copy/export events, I am concerned this is a big issue.
+
+The fact of the matter is that the current reliance on Google and Facebook is a reality for most end users and organizers. So I think that while the focus of this solution is on Phabricator and MediaWiki options, it would be a bit ""head in the sand"" to ignore the reality of what is going on. These popular external calendars need to be able to be integrated -- either in export or import -- somehow with existing systems. They are sort of the only game in town calendar-wise, and it's not just because of market share, but because of functionality and the integratedness of the two options.
+
+Sorry, I don't mean to be demanding (but I am) or discouraging (yeah that too).
+
+– Erika
+User:BrillLyle
+
+
+>>! In T1035#2295877, @Qgil wrote:
+> 
+> @BrillLyle, have you tried Phabricator Calendar? I think it is quite low barrier as soon as users don't make the mental connection ""Phabricator == technical, not for me"", but I would be very interested in discussing the details.
+> 
+> I am not proposing to rely on Google, Facebook on anything at Wikimedia, so we can take this topic out of this discussion.
+> 
+> Anyone can request funding to develop a MediaWiki extension that allows  native input of calendar data. It's just that such funding request will need to come from [[ https://meta.wikimedia.org/wiki/Grants | grants ]], because (for the bureaucratic-sounding but very real reasons I have explained) the budget that our team has right now will not be available on July 1.",1463406303,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"By the way, I just rewrote this page, to be clearer and more up-to-date:
+
+https://www.mediawiki.org/wiki/Extension:Calendar",1463351662,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"A solution that would work for the Wikimedia Tech community is not a suboptimal solution, is a valid solution for a specific problem (which doesn't conflict with potential solutions for the non-tech Wikimedia communities).
+
+As for the general problem...
+
+@Platonides, can you show the use of calendar by Wikimedia Spain? Installing OwnCloud on your own server looks like a much more technical and involved task than just using Phabricator Calendar for your org/project. For what is worth, every time there are more chapters and non-tech groups that are using Phabricator as a project management tool.
+
+@BrillLyle, have you tried Phabricator Calendar? I think it is quite low barrier as soon as users don't make the mental connection ""Phabricator == technical, not for me"", but I would be very interested in discussing the details.
+
+I am not proposing to rely on Google, Facebook on anything at Wikimedia, so we can take this topic out of this discussion.
+
+Anyone can request funding to develop a MediaWiki extension that allows  native input of calendar data. It's just that such funding request will need to come from [[ https://meta.wikimedia.org/wiki/Grants | grants ]], because (for the bureaucratic-sounding but very real reasons I have explained) the budget that our team has right now will not be available on July 1.",1463330999,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"A solution that would work for the Wikimedia Tech community is not a suboptimal solution, is a valid solution for a specific problem (which doesn't conflict with potential solutions for the non-tech Wikimedia communities).
+
+As for the general problem...
+
+@Platonides, can you show the use of calendar by Wikimedia Spain? Installing OwnCloud on your own server looks like a much more technical and involved task than just using Phabricator Calendar for your org/project. For what is worth, every time there are more chapters and non-tech groups that are using Phabricator as a project management tool.
+
+@BrillLyle, have you tried Phabricator Calendar? I think it is quite low barrier as soon as users don't make the mental connection ""Phabricator == technical, not for me"", but I would be very interested in discussing the details.
+
+I am not proposing to rely on Google, Facebook on anything at Wikimedia, so we can take this topic out of this discussion.
+
+Anyone can request funding to develop a MediaWiki extension that allows  native input of calendar data. It's just that such funding request will need to come from [[ https://meta.wikimedia.org/wiki/Grants | grants ]], because (for the bureaucratic-sunding but very real reasons I have explained) the budget that our team has right now will not be available on July 1.",1463330943,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"A solution that would work for the Wikimedia Tech community is not a suboptimal solution, is a valid solution for a specific problem, that is not in direct competition with other potential solutions.
+
+As for the general problem...
+
+@Platonides, can you show the use of calendar by Wikimedia Spain? Installing OwnCloud on your own server looks like a much more technical and involved task than just using Phabricator Calendar for your org/project. For what is worth, every time there are more chapters and non-tech groups that are using Phabricator as a project management tool.
+
+@BrillLyle, have you tried Phabricator Calendar? I think it is quite low barrier as soon as users don't make the mental connection ""Phabricator == technical, not for me"", but I would be very interested in discussing the details.
+
+I am not proposing to rely on Google, Facebook on anything at Wikimedia, so we can take this topic out of this discussion.
+
+Anyone can request funding to develop a MediaWiki extension that allows  native input of calendar data. It's just that such funding request will need to come from [[ https://meta.wikimedia.org/wiki/Grants | grants ]], because (for the bureaucratic-sunding but very real reasons I have explained) the budget that our team has right now will not be available on July 1.",1463330861,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I agree that just because there is a budget and a time constraint doesn't mean that's the best approach -- especially because a bandaid and/or short-term solution may not provide what is needed in the long-term. 
+
+The google calendar and folks using Facebook event pages seems to be working right now. Is it ideal? No. 
+
+The lowest technical barrier on the end users and organizers is my biggest concern. Not sure any of these options is an improvement -- or needs to be a focus of this discussion. But wanted to mention it just in case. 
+
+Erika
+User:BrillLyle
+
+>>! In T1035#2295720, @Platonides wrote:
+> 
+> Should we spend budget in a suboptimal solution because of time constraints for expenditure in the TC team?
+> It may be worth it for the interim benefit. And while I prefer to spend money that way than developer hours, it's still a tough decision.
+
+
+",1463323693,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"One important reason for WM-ES to install Owncloud was precisely so we could use its calendar features.
+Storing calendars in external platforms like Google of Facebook is far from ideal. Even if people really had it in one of those unfree platforms{{citation needed}}, the problem is not just //showing// the ics calendar, but also //editing// it.
+If it's stored in the wiki, that would be relatively straightforward, compare that to finding out it is included from a Facebook calendar, which requires  you to create a Facebook account, then ask for permission to someone else (which may not even be too active now) for changing the calendar, just to enter your local event.
+And all of these duplicating the existing organization at a parallel site.
+
+Storing the calendars in phabricator may work for the Wikimedia technical community, but doesn't solve the problem for the second group.
+
+
+>>! In T1035#2295517, @Qgil wrote:
+> Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+
+Should we spend budget in a suboptimal solution because of time constraints for expenditure in the TC team?
+It may be worth it for the interim benefit. And while I prefer to spend money that way than developer hours, it's still a tough decision.",1463320979,PHID-USER-izojihzr4ja3jsgzn5wv,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Qgil wrote:
+
+> SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+
+If anyone's wondering, I assume he's referring to this ticket: T53642. To summarize that discussion: three of the DevOps people want to replace SMW on their system with dedicated DevOps tools. How relevant that is to this discussion is a matter of personal opinion.
+
+I hate to sound like a broken record here, but SMW is already in successful use on hundreds of wikis, including probably dozens where it's used specifically to manage calendar and event data. It provides all the functionality that people are talking about here, as far as I can tell: data entry, standard calendars, customized views/queries, data export. Cargo is a newer extension (first released in 2015), so it hasn't gotten as much use so far, but it does essentially all the same stuff as SMW.",1463316950,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thank you for the quick and diverse feedback provided so far. Some thoughts:
+
+Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+* The Technical Collaboration team has some budget available for FY2015-16, to be used by the end of June. What can be achieved within this timeline? Certainly not anything in the form of a new extension in the Wikimedia cluster. In comparison, the Phabricator Calendar improvements could be developed and deployed in Wikimedia within that timeframe.
+* Who is going to develop that extension? After agreeing on a plan for a MediaWiki extension, we need to define who will work on it as paid work, which also takes time. In comparison, funding Phacility Inc for Phabricator upstream improvements is a straightforward and quick decision.
+* Who is going to maintain that extension? The Technical Collaboration team doesn't have the skills to maintain it, and the Community Engagement department has a known problem of mid term sustainability plans of the software we commission and own. While other CE teams are trying to reduce and resolve this problem, TC cannot just start the development of a new extension without a maintenance plan. In comparison, the Phabricator improvements funded would be maintained by the Phabricator maintainers.
+
+When it comes to the technical plan, things are anything but clear:
+The first requirement is **Introducing calendar data**, something that plain MediaWiki was not designed for. 
+* SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+* Recent efforts on developing extensions focusing on input of structured data via forms (limiting wiki editing in its purest sense) are being met by a small but perseverant current of criticism. Would this project conflict with that view? (I don't agree with such view, and I wouldn't want to be a participant in such discussion)
+* In previous discussions about something new, Wikidata was mentioned as part of the solution, and then the Wikidata team disagreed for reasons that I found convincing. Is this another of these cases? In any case, that would not solve the input problem immediately either.
+* In comparison, Phabricator Calendar provides a way to input data designed for events, it is based on free software, and it is already deployed in Wikimedia servers.
+
+I think that starting this effort by requiring native calendar input data in MediaWiki is not the best tactic. Once the calendar data is introduced and available somewhere via .ics, a MediaWiki extension could focus on its presentation in MediaWiki pages. That would probably solve better the 3rd use case, since I can imagine many MediaWiki users needing calendar data in their wikis to have that data already in Google Calendar, Facebook Events, or elsewhere able to export data via .ics.
+
+I also want to note that output in MediaWiki pages is not the only destination of calendar data, and I would even contest the idea that it is the most important. I believe that most of our users would use this data integrated in their own calendars, importing Wikimedia events/calendars and following their updates from their calendar apps. That is also a reason why I am not obsessed with having MediaWiki output first, or as a requirement for any first step.
+
+For all these reasons, I still think that improving Phabricator Calendar is the best first step solving our problems with calendars. A step that would solve most of the Wikimedia tech problems, and a step that would be in a direction compatible with solving the problem for the rest of Wikimedia, and other MediaWiki users.
+
+The MediaWiki extension able to read .ics data and embed it in MediaWiki pages could be a good candidate for an Individual Engagement Grant. That program is well suited to evaluate movement priorities, feasibility of plans, and funding specific contributors, all done under a community review process. 
+
+If we solve the Phabricator Calendar piece in the next 2-3 months, and the MediaWiki extension piece in the next IEG round, we could have a good enough solution for everybody by the end of the year or so.",1463308865,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thank you for the quick and diverse feedback provided so far. Some thoughts:
+
+Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+* The Technical Collaboration team has some budget available for FY2015-16, to be used by the end of June. What can be achieved within this timeline? Certainly not anything in the form of a new extension in the Wikimedia cluster. In comparison, the Phabricator Calendar improvements could be developed and deployed in Wikimedia within that timeframe.
+* Who is going to develop that extension? After agreeing on a plan for a MediaWiki extension, we need to define who will work on it as paid work, which also takes time. In comparison, funding Phacility Inc for Phabricator upstream improvements is a straightforward and quick decision.
+* Who is going to maintain that extension? The Technical Collaboration team doesn't have the skills to maintain it, and the Community Engagement department has a known problem of mid term sustainability plans of the software we commission and own. While other CE teams are trying to reduce and resolve this problem, TC cannot just start the development of a new extension without a maintenance plan. In comparison, the Phabricator improvements funded would be maintained by the Phabricator maintainers.
+
+When it comes to the technical plan, things are anything but clear:
+The first requirement is **Introducing calendar data**, something that plain MediaWiki was not designed for. 
+* SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+* Recent efforts on developing extensions focusing on input of structured data via forms (limiting wiki editing in its purest sense) are being met by a small but perseverant current of criticism. Would this project conflict with that view? (I don't agree with such view, and I wouldn't want to be a participant in such discussion)
+* In previous discussions about something new, Wikidata was mentioned as part of the solution, and then the Wikidata team disagreed for reasons that I found convincing. Is this another of these cases? In any case, that would not solve the input problem immediately either.
+* In comparison, Phabricator Calendar provides a way to input data designed for events, it is based on free software, and it is already deployed in Wikimedia servers.
+
+I think that starting this effort by requiring native calendar input data in MediaWiki is not the best tactic. Once the calendar data is introduced and available somewhere via .ics, a MediaWiki extension could focus on its presentation in MediaWiki pages. That would probably solve better the 3rd use case, since I can imagine many orgs using MediaWiki that already have their calendars in Google, Facebook, or elsewhere able to export data via .ics.
+
+I also want to note that output in MediaWiki pages is not the only destination of calendar data, and I would even contest that idea that it is the most important. I believe that most of our users would use this data integrated in their own calendars, importing Wikimedia calendars and following their updates from their calendar apps. That is also a reason why I am not obsessed with having MediaWiki output first, or as a requirement for any first step.
+
+For all these reasons, I still think that improving Phabricator Calendar is the best first step solving our problems with calendars. A step that would solve most of the Wikimedia tech problems, and a step that would be in a direction compatible with solving the problem for the rest of Wikimedia, and other MediaWiki users.
+
+The MediaWiki extension able to read .ics data and embed it in MediaWiki pages could be a good candidate for an Individual Engagement Grant. That program is well suited to evaluate movement priorities, feasibility of plans, and funding specific contributors, all done under a community review process. 
+
+If we solve the Phabricator Calendar piece in the next 2-3 months, and the MediaWiki extension piece in the next IEG round, we could have a good enough solution for everybody by the end of the year or so.",1463308605,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thank you for the quick and diverse feedback provided so far. Some thoughts:
+
+Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+* The Technical Collaboration team has some budget available for FY2015-16, to be used by the end of June. What can be achieved within this timeline? Certainly not anything in the form of a new extension in the Wikimedia cluster. In comparison, the Phabricator Calendar improvements could be developed and deployed in Wikimedia within that timeframe.
+* Who is going to develop that extension? After agreeing on a plan for a MediaWiki extension, we need to define who will work on it as paid work, which also takes time. In comparison, funding Phacility Inc for Phabricator upstream improvements is a straightforward and quick decision.
+* Who is going to maintain that extension? The Technical Collaboration team doesn't have the skills to maintain it, and the Community Engagement department has a known problem of mid term sustainability plans of the software we commission and own. While other CE teams are trying to reduce and resolve this problem, TC cannot just start the development of a new extension without a maintenance plan. In comparison, the Phabricator improvements funded would be maintained by the Phabricator maintainers.
+
+When it comes to the technical plan, things are anything but clear:
+The first requirement is **Introducing calendar data**, something that plain MediaWiki was not designed for. 
+* SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+* Recent efforts on developing extensions focusing on input of structured data via forms (limiting wiki editing in its purest sense) are being met by a small but perseverant current of criticism. Would this project conflict with that view (I don't agree with such view, and I wouldn't want to be a participant in such discussion).
+* In previous discussions about something new, Wikidata was mentioned as part of the solution, and then the Wikidata team disagreed for reasons that I found convincing. Is this another of these cases? In any case, that would not solve the input problem immediately either.
+* In comparison, Phabricator Calendar provides a way to input data designed for events, it is based on free software, and it is already deployed in Wikimedia servers.
+
+I think that starting this effort by requiring native calendar input data in MediaWiki is not the best tactic. Once the calendar data is introduced and available somewhere via .ics, a MediaWiki extension could focus on its presentation in MediaWiki pages. That would probably solve better the 3rd use case, since I can imagine many orgs using MediaWiki that already have their calendars in Google, Facebook, or elsewhere able to export data via .ics.
+
+I also want to note that output in MediaWiki pages is not the only destination of calendar data, and I would even contest that idea that it is the most important. I believe that most of our users would use this data integrated in their own calendars, importing Wikimedia calendars and following their updates from their calendar apps. That is also a reason why I am not obsessed with having MediaWiki output first, or as a requirement for any first step.
+
+For all these reasons, I still think that improving Phabricator Calendar is the best first step solving our problems with calendars. A step that would solve most of the Wikimedia tech problems, and a step that would be in a direction compatible with solving the problem for the rest of Wikimedia, and other MediaWiki users.
+
+The MediaWiki extension able to read .ics data and embed it in MediaWiki pages could be a good candidate for an Individual Engagement Grant. That program is well suited to evaluate movement priorities, feasibility of plans, and funding specific contributors, all done under a community review process. 
+
+If we solve the Phabricator Calendar piece in the next 2-3 months, and the MediaWiki extension piece in the next IEG round, we could have a good enough solution for everybody by the end of the year or so.",1463308541,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thank you for the quick and diverse feedback provided so far. Some thoughts:
+
+Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+* The Technical Collaboration team has some budget available for FY2015-16, to be used by the end of June. What can be achieved within this timeline? Certainly not anything in the form of a new extension in the Wikimedia cluster. In comparison, the Phabricator Calendar improvements could be developed and deployed in Wikimedia within that timeframe.
+* Who is going to develop that extension? After agreeing on a plan for a MediaWiki extension, we need to define who will work on it as paid work, which also takes time. In comparison, funding Phacility Inc for Phabricator upstream improvements is a straightforward and quick decision.
+* Who is going to maintain that extension? The Technical Collaboration team doesn't have the skills to maintain it, and the Community Engagement department has a known problem of mid term sustainability plans of the software we commission and own. While other CE teams are trying to reduce and resolve this problem, TC cannot just start the development of a new extension without a maintenance plan.
+
+When it comes to the technical plan, things are anything but clear:
+The first requirement is **Introducing calendar data**, something that plain MediaWiki was not designed for. 
+* SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+* Recent efforts on developing extensions focusing on input of structured data via forms (limiting wiki editing in its purest sense) are being met by a small but perseverant current of criticism. Would this project conflict with that view (I don't agree with such view, and I wouldn't want to be a participant in such discussion).
+* In previous discussions about something new, Wikidata was mentioned as part of the solution, and then the Wikidata team disagreed for reasons that I found convincing. Is this another of these cases? In any case, that would not solve the input problem immediately either.
+* In comparison, Phabricator Calendar provides a way to input data designed for events, it is based on free software, and it is already deployed in Wikimedia servers.
+
+I think that starting this effort by requiring native calendar input data in MediaWiki is not the best tactic. Once the calendar data is introduced and available somewhere via .ics, a MediaWiki extension could focus on its presentation in MediaWiki pages. That would probably solve better the 3rd use case, since I can imagine many orgs using MediaWiki that already have their calendars in Google, Facebook, or elsewhere able to export data via .ics.
+
+I also want to note that output in MediaWiki pages is not the only destination of calendar data, and I would even contest that idea that it is the most important. I believe that most of our users would use this data integrated in their own calendars, importing Wikimedia calendars and following their updates from their calendar apps. That is also a reason why I am not obsessed with having MediaWiki output first, or as a requirement for any first step.
+
+For all these reasons, I still think that improving Phabricator Calendar is the best first step solving our problems with calendars. A step that would solve most of the Wikimedia tech problems, and a step that would be in a direction compatible with solving the problem for the rest of Wikimedia, and other MediaWiki users.
+
+The MediaWiki extension able to read .ics data and embed it in MediaWiki pages could be a good candidate for an Individual Engagement Grant. That program is well suited to evaluate movement priorities, feasibility of plans, and funding specific contributors, all done under a community review process. 
+
+If we solve the Phabricator Calendar piece in the next 2-3 months, and the MediaWiki extension piece in the next IEG round, we could have a good enough solution for everybody by the end of the year or so.",1463307550,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"After a first wave of feedback it is clear that we have two different discussions that need solving:
+
+# If we use WMF Technical Collaboration budget for Phabricator improvements, should we invest it the Calendar application? This is a well framed discussion with a clear deadline for decisions (very soon, or our FY2015-16 budget will be gone). I have created a task to discuss this specifically: {T135327}
+# If we want to improve the announcement and promotion of Wikimedia tech events, is the best first step to improve Phabricator Calendar? This is a complex discussion with many ramifications that we can keep discussing here.",1463304220,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@JanZerebecki - actually, both Semantic MediaWiki and Cargo can have their data displayed on other wikis. They both can export their data via the API, in formats including JSON and iCalendar (well, Cargo doesn't currently support iCalendar, but it would be easy to add it in). To be able to get and display the JSON data, any other wiki would just need to have the External Data extension installed:
+
+https://www.mediawiki.org/wiki/Extension:External_Data
+
+As for getting iCalendar data and actually being able to display a calendar with that information, the Widgets extension, and specifically the Google Calendar widget, could probably be used for that:
+
+http://www.mediawikiwidgets.org/Google_Calendar",1463275196,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wikibase (thus Wikidata) is able to store the required information. The time portion of dates might need some love first, though. It is able to provide that information to multiple clients (all Wikimedia wikis). And to external consumers in various formats. (Perhaps query.wikidata.org needs support to output ics! Sometime after exposing results to Lua.) Maybe conference occurrences can be entered in Wikidata (like was done for Wikimania 2016 https://www.wikidata.org/wiki/Q19291990 ) and maybe that could then link to their ics URL of the schedule...
+
+SMW is as the links above show able to store the required information. AFAIK as is, it is not able to provide that information to other wikis than the wiki where it is stored, though it can probably provide it to external consumers in various formats. Would be useful if SMW and Wikibase supported a common query result format. So that they could share many extensions. We didn't update the version of SMW that is running on one of the Wikimedia wikis. See e.g. https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/1479 (could need some love independent of this task).
+
+The Phabricator calendar doesn't automatically subscribe me to materialized instances of recurring events. (That reminds me that we have tasks that we manually repeat where I sometimes also need to subscribe to the next one manually depending on if the subscribers were copied.)
+> I oppose spending money on this unless we first spend money on the Phabricator upstream bugs which Wikimedia users suffer from.
+Yes #Phabricator-Upstream has some that are more important than those related to Calendar.
+
+Anything that doesn't export caldav/ical doesn't help me personally (all people I know use devices and software that can consume CaldDav or ics files from the Internet).
+Special Google Calendar support is probably not needed as google supports ics.
+Ext:Cargo sounds interesting. Other back ends (than SMW) could be supported in the same way.
+I personally use https://en.wikipedia.org/wiki/DAViCal as a back end.
+Still need to find something to sync ics files to a CalDav server. And something to filter and aggregate calendar events ( like query.wikidata.org ? ), e.g. to get an ics file with all events related to open educational resources (Q116781) that are at most 10km from the center of Berlin (Q64).
+
+Does FullCalendar support CalDav?
+http://agendav.org/ looks interesting as a front end.",1463241475,PHID-USER-mdihg2tyzmlvyhn3h32y,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I think we should be looking at the possibility of different solutions to serve the different purposes:
+
+* Firstly (as the basis of this task) we want a solution for the Tech crowd, where we can use tags, cross reference teams, tasks, subscribe/cc to follow, ACLs and the likes, and since Phabricator is already our central point it may be the best contender or it may not be once we start looking at extended features (example: displaying inside MediaWiki, exporting via standard formats etc, syncing to personal devices).
+
+* Secondary (probably best discussed in a separate task) appears to be where we want a calendaring solution for those that are primarily in the wiki-sphere and don't use Pharicator as a central discussion location and want to manage wholelly on a wiki based level (eg: WikiCons, meetups, EditThons).
+
+",1463223449,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,I oppose spending money on this unless we first spend money on the Phabricator upstream bugs which Wikimedia users suffer from.,1463218135,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,I would also like to see a calendar solution that is usable for 3rd party Mediawiki users.,1463198128,PHID-USER-fo56wm4wxiwpoofn2xdu,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@Qgil posted on wikitech-l asking for feedback about this. He writes:
+
+> The Technical Collaboration team has some budget that we could use to fund the Phabricator maintainers to prioritize some improvements in their Calendar. If you think this is a bad idea and/or you have a better one, please discuss in the task (preferred) or here.
+
+I'd personally prefer to see a calendar solution that integrates with MediaWiki. Many of the use-cases mentioned in this task relate to our wikis.
+
+There are times when investing in another organization's platform makes sense, but in this case, I think investing in our own platform is probably more prudent. As demonstrated by the dozen MediaWiki extensions in this space, there's demand among ""third-party"" (i.e., non-Wikimedia) MediaWiki installations—including wikis that I administer—to have a usable calendar system.",1463190845,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"The thing that us folks doing Wikipedia:Meetup editathons need is **something that can be maintained on the Wikipedia namespace **-- and probably for those still using Meta for use on that namespace as well.
+
+For the WM NYC chapter, we have been putting our event pages on Wikipedia via Wikipedia:Meetup as it is a semi-passive way to onboard people onto the main Wiki. Plus a lot of templates don't play well with Meta -- blargh. So that functionality / integration especially would be super helpful for the chapter.
+
+I think other chapters and probably more global meetups use Meta -- WM NYC doesn't really use our Meta that much, especially not for calendar-related activities. Again we are trying to point people to one main URI if possible. We have over 20 events (not including outliers) so far this year and it's only May, so this would be something used in a very robust way.
+
+If MediaWiki is not implementable onto the main Wiki, and assume Wikidata obviously (?) isn't an option for calendaring (?), then would Phabricator Calendar be able to be embedded onto Wikipedia:Meetup namespaces? We would really really like that. A lot.
+
+I'm probably using the term namespace incorrectly but it makes sense to my pea brain. Apologies for the lack of precision. I'm more of an end user experience person.
+
+Also, is the afore-mentioned Calagator just completely not an option? It doesn't have the bells and whistles of Google calendar but it seems sort of cool.
+
+– Erika 
+User:BrillLyle
+
+",1463184609,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I would appreciate an improvement to the calendar situation, not just for tech events but also for finance, fundraising, community, and everything else. I haven't looked into Cargo or SMW calendars in any detail, but I'd like to see *some* kind of progress on an open source calendar that can be used widely including outside of WMF by affiliates. Thanks!",1463178969,PHID-USER-l7v72q5tq6vg6zclrld6,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@Krenair - that was a discussion about including SMW on Wikipedia and the like; SMW was rejected in favor of Wikidata. It's unrelated to its use on ""internal"" sites like mediawiki.org and meta.wikimedia.org. Again, though, I personally think Cargo is the superior solution.",1463177991,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,SMW was already declined years ago: {T10390},1463175018,PHID-USER-x7ti5ksby4ubsabntlxa,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"There are already two MediaWiki extensions that handle the display of calendars very well: Semantic MediaWiki and Cargo. Both let you query events in any number of ways, displaying subsets of events and allowing for color-coding and so forth. When used in conjunction with the Semantic Forms extension for entering event data (which can be used with either SMW or Cargo), the whole system becomes fairly simple to use.
+
+https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki
+https://www.mediawiki.org/wiki/Extension:Cargo
+https://www.mediawiki.org/wiki/Extension:Semantic_Forms
+
+Personally, I think Cargo is a little nicer to use, but you can see here a nice demonstration of how SMW and SF were used together to enter the data for, and display, a conference schedule:
+
+https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2015/Calendar
+
+This is using the FullCalendar JS library:
+
+http://fullcalendar.io/",1463174574,PHID-USER-7jqnferdzzzwelhzchyo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I have updated the description adding the relevant information in the thread. If you are missing important bits, please add them.
+
+I have sent an informal call for feedback to wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085613.html
+
+The goal is to make a decision soon-ish, and if that decision is to fund the Phabricator maintainers, sign the agreement by the end of the month, and get the work done during June-July:
+
+# Unprototyping Calendar (mainly updating backend stuff?)
+# A Good API (tm)
+# .ics support
+# Basic Google Calendar support
+
+I wonder what would be the best way to proceed with the MediaWiki extension. If we get the Phabricator side done, it would be a decent candidate for the next Outreachy or Individual Engagement Grants rounds.",1463168681,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I have updated the description adding the relevant information in the thread. If you are missing important bits, please add them.
+
+I have sent an informal call for feedback to wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085613.html
+
+The goal is to make a decision soon-ish, and if that decision is to fund the Phabricator maintainers, sign the agreement by the end of the month, and get the work done during June-July:
+
+# Unprototyping Calendar (mainly updating backend stuff?)
+# A Good API (tm)
+# .ics support
+# Basic Google Calendar support
+
+I wonder what would be the best way to proceed with the MediaWiki extension. If we get the Phabricator side done, it would be decent candidate for the next Outreachy or Individual Engagement Grants rounds.",1463168661,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I have updated the description adding the relevant information in the thread. If you are missing important bits, please add them.
+
+I have sent an informal call for feedback to wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085613.html
+
+The goal is to make a decision soon-ish, and if that decision is to fund the Phabricator maintainers, sign the agreement by the end of the month, and get the work done during June-July:
+
+# Unprototyping Calendar (mainly updating backend stuff?)
+# A Good API (tm)
+# .ics support
+# Basic Google Calendar support
+",1463168574,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2191801, @Quiddity wrote:
+> 1. There's also https://www.mediawiki.org/wiki/Extension:Calendar (a linkhub for the ~12 different extensions or methods of integrating calendars with MediaWiki). If further work was done on one of those, to make it usable by us, many other MediaWiki users would also benefit. 
+
+I went through the list and there was none surviving a basic check against our needs. In fact most of them are more than abandoned, and in general they focus on presentation, not on easy input, even less on semantic data (except the SemanticMediaWiki one, perhaps). [[ https://www.mediawiki.org/wiki/Extension:SimpleCalendar | SimpleCalendar ]] looks like the only candidaste if we would ever want to start from this point.
+
+> There have been 12 attempts at this, for a reason!
+
+Sure, and the reason may well be that MediaWiki was not designed to input calendar data, subscribe to events, etc.
+
+After this short investigation, I still think that it is better to start from something other than MediaWiki, and the main candidate keeps being Phabricator. Then work separately in a way to import Phabricator Calendar data and present it in MediaWiki pages.",1463060811,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"High priority because I need to decide whether we are investing some FY2015-16 budget on a Phabricator Calendar improvement or not, and that decision needs to be made soon.",1462437116,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,,1462389147,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,,1462389023,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I posted this to the main mailing list, just sharing for 100% transparency. WM NYC had one massive calendar but the consensus was it needed to be carved down, so here they are.... :-)
+
+– –
+
+Hello --
+
+In an effort to de-clutter the Wikimedia NYC calendar -- and to support the various initiatives and enhance event calendaring within Wikimedia -- after some active discussion, Wikimedia NYC (well that would be me) has set up the following calendars. 
+
+Many events were pulled from these source:
+- https://meta.wikimedia.org/wiki/Events
+- https://www.mediawiki.org/wiki/Events
+
+Ideally a calendar solution would be open source and Wiki-friendly (see https://phabricator.wikimedia.org/T1035 Consolidate the many tech events calendars in Phabricator's calendar), but Google calendars seem to provide the most functionality right now so this is seen as an interim solution. For reference: https://phabricator.wikimedia.org/calendar/
+
+Please feel free to add events and share widely.
+
+G L O B A L
+
+Wikimedia Global Events
+Calendar ID: 7naa8gc5mjqhgjn1g2pbb4829s@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/7naa8gc5mjqhgjn1g2pbb4829s%40group.calendar.google.com/public/basic.ics
+
+Global Tech Events
+Calendar ID: 8bkj15efk0qgu4jut3oe5kd5eg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/8bkj15efk0qgu4jut3oe5kd5eg%40group.calendar.google.com/public/basic.ics
+
+.–.
+
+I N I T I A T I V E S
+
+AfroCROWD
+Calendar ID: djfkq9sql4h956b8vo6e35h484@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/djfkq9sql4h956b8vo6e35h484%40group.calendar.google.com/public/basic.ics
+
+Art+Feminism -- 3/4 complete, will go back and add missing & updated 2016 events
+Calendar ID: vpjc23to157rgtvgnkces05oq4@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/vpjc23to157rgtvgnkces05oq4%40group.calendar.google.com/public/basic.ics
+
+Black Lunch Table -- will double-check complete
+Calendar ID: speen8r33k1oh2e99u608g7moc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/speen8r33k1oh2e99u608g7moc%40group.calendar.google.com/public/basic.ics
+
+Black WikiHistory Month
+Calendar ID: 40pgnrv1hbagcd40ukv6c15o0c@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/40pgnrv1hbagcd40ukv6c15o0c%40group.calendar.google.com/public/basic.ics
+
+GLAM
+Calendar ID: ljmqctd112nju1fsngd1mvbelc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ljmqctd112nju1fsngd1mvbelc%40group.calendar.google.com/public/basic.ics
+
+Women in Red -- just started, in progress
+Calendar ID: qnadatlib4j65u1cn4ifo17o4k@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/qnadatlib4j65u1cn4ifo17o4k%40group.calendar.google.com/public/basic.ics
+
+
+WikimediaNYC
+Calendar ID: nnvhsl9su019vngvb58qb68u6o@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com/public/basic.ics
+
+WM NYC Planning -- Board and Event Planning so not public
+Calendar ID: ed471n0r5vkgg99dn3tau1i9vg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ed471n0r5vkgg99dn3tau1i9vg%40group.calendar.google.com/public/basic.ics
+
+
+Please forgive typos, errors and works in progress. :-)
+
+– Erika
+
+Erika Herzog
+Wikipedia User:BrillLyle
+Secretary, Wikimedia NYC",1461938043,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I posted this to the main mailing list, just sharing for 100% transparency. WM NYC had one massive calendar but the consensus was it needed to be carved down, so here they are.... :-)
+
+– –
+
+Hello --
+
+In an effort to de-clutter the Wikimedia NYC calendar -- and to support the various initiatives and enhance event calendaring within Wikimedia -- after some active discussion, Wikimedia NYC (well that would be me) has set up the following calendars. 
+
+Many events were pulled from these source:
+- https://meta.wikimedia.org/wiki/Events
+- https://www.mediawiki.org/wiki/Events
+
+Ideally a calendar solution would be open source and Wiki-friendly (see https://phabricator.wikimedia.org/T1035 Consolidate the many tech events calendars in Phabricator's calendar), but Google calendars seem to provide the most functionality right now so this is seen as an interim solution. For reference: https://phabricator.wikimedia.org/calendar/
+
+Please feel free to add events and share widely.
+
+G L O B A L
+
+Wikimedia Global Events
+Calendar ID: 7naa8gc5mjqhgjn1g2pbb4829s@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/7naa8gc5mjqhgjn1g2pbb4829s%40group.calendar.google.com/public/basic.ics
+
+Global Tech Events
+Calendar ID: 8bkj15efk0qgu4jut3oe5kd5eg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/8bkj15efk0qgu4jut3oe5kd5eg%40group.calendar.google.com/public/basic.ics
+
+--
+
+I N I T I A T I V E S
+
+AfroCROWD
+Calendar ID: djfkq9sql4h956b8vo6e35h484@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/djfkq9sql4h956b8vo6e35h484%40group.calendar.google.com/public/basic.ics
+
+Art+Feminism -- 3/4 complete, will go back and add missing & updated 2016 events
+Calendar ID: vpjc23to157rgtvgnkces05oq4@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/vpjc23to157rgtvgnkces05oq4%40group.calendar.google.com/public/basic.ics
+
+Black Lunch Table -- will double-check complete
+Calendar ID: speen8r33k1oh2e99u608g7moc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/speen8r33k1oh2e99u608g7moc%40group.calendar.google.com/public/basic.ics
+
+Black WikiHistory Month
+Calendar ID: 40pgnrv1hbagcd40ukv6c15o0c@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/40pgnrv1hbagcd40ukv6c15o0c%40group.calendar.google.com/public/basic.ics
+
+GLAM
+Calendar ID: ljmqctd112nju1fsngd1mvbelc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ljmqctd112nju1fsngd1mvbelc%40group.calendar.google.com/public/basic.ics
+
+Women in Red -- just started, in progress
+Calendar ID: qnadatlib4j65u1cn4ifo17o4k@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/qnadatlib4j65u1cn4ifo17o4k%40group.calendar.google.com/public/basic.ics
+
+
+WikimediaNYC
+Calendar ID: nnvhsl9su019vngvb58qb68u6o@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com/public/basic.ics
+
+WM NYC Planning -- Board and Event Planning so not public
+Calendar ID: ed471n0r5vkgg99dn3tau1i9vg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ed471n0r5vkgg99dn3tau1i9vg%40group.calendar.google.com/public/basic.ics
+
+
+Please forgive typos, errors and works in progress. :-)
+
+– Erika
+
+Erika Herzog
+Wikipedia User:BrillLyle
+Secretary, Wikimedia NYC",1461938024,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I posted this to the main mailing list, just sharing for 100% transparency. WM NYC had one massive calendar but the consensus was it needed to be carved down, so here they are.... :-)
+
+– –
+
+Hello --
+
+In an effort to de-clutter the Wikimedia NYC calendar -- and to support the various initiatives and enhance event calendaring within Wikimedia -- after some active discussion, Wikimedia NYC (well that would be me) has set up the following calendars. 
+
+Many events were pulled from these source:
+- https://meta.wikimedia.org/wiki/Events
+- https://www.mediawiki.org/wiki/Events
+
+Ideally a calendar solution would be open source and Wiki-friendly (see https://phabricator.wikimedia.org/T1035 Consolidate the many tech events calendars in Phabricator's calendar), but Google calendars seem to provide the most functionality right now so this is seen as an interim solution. For reference: https://phabricator.wikimedia.org/calendar/
+
+Please feel free to add events and share widely.
+
+G L O B A L
+
+Wikimedia Global Events
+Calendar ID: 7naa8gc5mjqhgjn1g2pbb4829s@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/7naa8gc5mjqhgjn1g2pbb4829s%40group.calendar.google.com/public/basic.ics
+
+Global Tech Events
+Calendar ID: 8bkj15efk0qgu4jut3oe5kd5eg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/8bkj15efk0qgu4jut3oe5kd5eg%40group.calendar.google.com/public/basic.ics
+
+--
+
+I N I T I A T I V E S
+
+AfroCROWD
+Calendar ID: djfkq9sql4h956b8vo6e35h484@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/djfkq9sql4h956b8vo6e35h484%40group.calendar.google.com/public/basic.ics
+
+Art+Feminism -- 3/4 complete, will go back and add missing & updated 2016 events
+Calendar ID: vpjc23to157rgtvgnkces05oq4@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/vpjc23to157rgtvgnkces05oq4%40group.calendar.google.com/public/basic.ics
+
+Black Lunch Table -- will double-check complete
+Calendar ID: speen8r33k1oh2e99u608g7moc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/speen8r33k1oh2e99u608g7moc%40group.calendar.google.com/public/basic.ics
+
+Black WikiHistory Month
+Calendar ID: 40pgnrv1hbagcd40ukv6c15o0c@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/40pgnrv1hbagcd40ukv6c15o0c%40group.calendar.google.com/public/basic.ics
+
+GLAM
+Calendar ID: ljmqctd112nju1fsngd1mvbelc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ljmqctd112nju1fsngd1mvbelc%40group.calendar.google.com/public/basic.ics
+
+Women in Red -- just started, in progress
+Calendar ID: qnadatlib4j65u1cn4ifo17o4k@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/qnadatlib4j65u1cn4ifo17o4k%40group.calendar.google.com/public/basic.ics
+
+
+WikimediaNYC
+Calendar ID: nnvhsl9su019vngvb58qb68u6o@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com/public/basic.ics
+
+WM NYC Planning -- Board and Event Planning so not public
+Calendar ID: ed471n0r5vkgg99dn3tau1i9vg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ed471n0r5vkgg99dn3tau1i9vg%40group.calendar.google.com/public/basic.ics
+
+
+Please forgive typos, errors and works in progress. :-)
+
+- Erika
+
+Erika Herzog
+Wikipedia User:BrillLyle
+Secretary, Wikimedia NYC",1461938003,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2214477, @BrillLyle wrote:
+> Wanted to mention that someone on one of the Wiki mailing lists recommended looking into the Calagator interface, Portland's Tech Calendar:
+
+Calagator is really interesting. Thanks for sharing.
+
+",1460999031,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wanted to mention that someone on one of the Wiki mailing lists recommended looking into the Calagator interface, Portland's Tech Calendar:
+
+https://github.com/calagator
+
+http://calagator.org/about
+
+As far as I can tell there's no typical calendar grid format, which is non-ideal, and I'm not a code person so I don't know how Wiki-friendly this is. They do seem to be open source FWIW....
+
+http://www.bizjournals.com/portland/blog/techflash/2016/01/after-8-years-of-connecting-portland-tech.html
+
+– Erika aka BrillLyle, Secretary Wikimedia NYC",1460997542,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"1. There's also https://www.mediawiki.org/wiki/Extension:Calendar (a linkhub for the ~12 different extensions or methods of integrating calendars with MediaWiki). If further work was done on one of those, to make it usable by us, many other MediaWiki users would also benefit. There have been 12 attempts at this, for a reason!
+
+2. I've made an incomplete linkhub, for easier listing of all relevant and tangential pages, at https://meta.wikimedia.org/wiki/Calendars_events_and_meetings (I grok that this task is just about tech events/meetings, but it's a perennial issue throughout the movement.)",1460151705,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Quim started a discussion on this task on the teampractices mailing list ([""Who doesn't love calendars?""](https://lists.wikimedia.org/pipermail/teampractices/2016-April/thread.html#1078)).  This comment is partly my response on that thread
+
+The Phab calendaring tool is really good for a lot of things, and seems to hold promise as the core of an information hub about events.  The things I like about it for recurring [ArchCom RFC meetings](https://www.mediawiki.org/wiki/Architecture_meetings):
+*  Automatically weekly event instances (e.g. [Phab query: list of all RFC meetings](https://phabricator.wikimedia.org/calendar/query/XJjy54s3PEFf/))
+*  Each instance has a comment section
+*  Comments are really well integrated with Phabricator.  We can refer to RFCs by Phab number, and get automatic linking ( #ArchCom-RFC process)
+
+The upsides of using Phab made it really easy to drop useful comments about scheduling E159 //while we were having// meeting E158.  I find these features fit the #ArchCom workflow way better than the current MediaWiki-based template process on meta.
+
+As @BrillLyle says in T1035#2191149, other non-MediaWiki tools are better for different forms of outreach.  Interoperability with a broad range of tools is going to be essential.  Phab upstream is very thoughtful about synchronization with other tools (see [Upstream:T7924](https://secure.phabricator.com/T7924)). Given that our instance of Phab is something Wikimedia has operational control over, it seems like a good repository as a ""source of truth"" about events that we can build on.
+
+That's my longwinded way of saying that I'm excited about following through on this work, and more deeply integrating Phab events into our general workflows.",1460139288,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2189693, @Peachey88 wrote:
+> My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+> 
+> But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. 
+> 
+> But its more a side thing compared to the main goal of this bug (example: thinking of the tech events list on the main page of mw wiki).
+
+I agree with @Peachey88's comments. I created a semi-complete calendar of the 2016 Art+Feminism events that happened globally and one of the noticeable realities was that it was often easier for folks to add a Facebook event page than an actual on-Wikipedia event page -- especially as a first organizational step. Also, most of the larger events had both Facebook event pages as well as Eventbrite registration. Additionally, WM NYC uses Meetup.com as a registration tool (see: http://www.meetup.com/WikimediaNYC/}
+
+I think there needs to be the ability to subscribe to calendars that reflects these different realities. Not a huge fan of the whole Facebook thing, but it did seem to be the most user-friendly approach that would be easiest for event organizers.
+
+see this link for the events, as well as the links to the Google calendar (which I should probably go back and update for posterity's sake, as well as to include some of the newer events).
+https://en.wikipedia.org/wiki/Wikipedia:Meetup/ArtAndFeminism#2016_Art.2BFeminism_Wikipedia_Edit-a-thon
+
+Long winded way of saying, yes, RSS. But also consider iCal, Facebook, etc.
+
+– Erika aka BrillLyle, Secretary Wikimedia NYC",1460136002,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2189693, @Peachey88 wrote:
+> My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+> 
+> But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. 
+> 
+> But its more a side thing compared to the main goal of this bug (example: thinking of the tech events list on the main page of mw wiki).
+
+I agree with @Peachey88's comments. I created a semi-complete calendar of the 2016 Art+Feminism events that happened globally and one of the noticeable realities was that it was often easier for folks to add a Facebook event page than an actual on-Wikipedia event page -- especially as a first organizational step. Also, most of the larger events had both Facebook event pages as well as Eventbrite registration. Additionally, WM NYC uses Meetup as a registration tool.
+
+I think there needs to be the ability to subscribe to calendars that reflects these different realities. Not a huge fan of the whole Facebook thing, but it did seem to be the most user-friendly approach that would be easiest for event organizers.
+
+see this link for the events, as well as the links to the Google calendar (which I should probably go back and update for posterity's sake, as well as to include some of the newer events).
+https://en.wikipedia.org/wiki/Wikipedia:Meetup/ArtAndFeminism#2016_Art.2BFeminism_Wikipedia_Edit-a-thon
+
+Long winded way of saying, yes, RSS. But also consider iCal, Facebook, etc.
+
+– Erika aka BrillLyle, Secretary Wikimedia NYC",1460135948,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2189693, @Peachey88 wrote:
+> My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+> 
+> But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. 
+> 
+> But its more a side thing compared to the main goal of this bug (example: thinking of the tech events list on the main page of mw wiki).
+
+I agree with @Peachey88's comments. I created a semi-complete calendar of the 2016 Art+Feminism events that happened globally and one of the noticeable realities was that it was often easier for folks to add a Facebook event page than an actual on-Wikipedia event page, and most of the larger events had both Facebook event pages as well as Eventbrite registration. Additionally, WM NYC uses Meetup as a registration tool.
+
+I think there needs to be the ability to subscribe to calendars that reflects these different realities. Not a huge fan of the whole Facebook thing, but it did seem to be the most user-friendly approach that would be easiest for event organizers.
+
+see this link for the events, as well as the links to the Google calendar (which I should probably go back and update for posterity's sake, as well as to include some of the newer events).
+https://en.wikipedia.org/wiki/Wikipedia:Meetup/ArtAndFeminism#2016_Art.2BFeminism_Wikipedia_Edit-a-thon
+
+Long winded way of saying, yes, RSS. But also consider iCal, Facebook, etc.
+
+– Erika aka BrillLyle, Secretary Wikimedia NYC",1460135903,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+
+But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. 
+
+But its more a side thing compared to the main goal of this bug (example: thinking of the tech events list on the main page of mw wiki).",1460116755,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+
+But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. ",1460116683,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"The fact is that RSS support is not in Phabricator plans, neither (I believe) RSS is a technology that comes to mind when handling calendar data. Yes, if that bridge would exist maybe we could use it but since it doesn't... should we invest on it?
+
+What is the difference of embedding a calendar in a wiki page and offering that calendar with a link? At the end the most important feature is not viewing a list of events but being able to subscribe, RSVP, and add it to your own calendar application.",1460110737,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2026019, @Peachey88 wrote:
+> RSS output would probably the most useful starter for us, For integration onto the wikis via E:RSS
+
+RSS support doesn't seem to be on the official upstream roadmap https://secure.phabricator.com/T1928 so would need to be built by us or someone else (https://secure.phabricator.com/w/community_resources/), or to be funded (https://secure.phabricator.com/w/prioritization/).",1460059598,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"We have three problems that need to be resolved, which are related but perhaps may be fixed separately, even at different points in time:
+
+* **Introducing calendar data**. Now we are doing this in 1001 places. Ideally it would be just one. The assumption of this task is that the one place would be Phabricator's calendar ([[ https://secure.phabricator.com/T7924 | today a prototype ]]), but other candidates should be considered.
+* **Pulling calendar data in other supports, mainly wiki pages**. While we could start linking from wiki pages to Phabricator calendar queries, the desired scenario would be a way for editors to embed calendars based on queries in wiki pages. This probably implies a Calendar API to query data ([[ https://secure.phabricator.com/T7944 | which is missing ]]) and a MediaWiki extension allowing to embed those queried calendars in wiki pages (which we don't have). Maybe this is just too much, and at least the tech-inclined Wikimedians would be fine clicking a Phabricator link.
+* **Integrating calendar data with other systems (mainly Google Calendar)**. ""[[ https://secure.phabricator.com/T7929 | Future work ]]"" upstream, no plans today.
+
+As we can see, deciding on Phabricator Calendar as the one place to introduce data would not provide a quick path to use that data out of Phabricator. However, what would be the alternatives? Other than defaulting to Google Calendar (which I think would be wrong as a matter of Wikimedia principles), I don't see a shortcut but others may have better ideas.",1460051551,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"We have three problems that need to be resolved, which are related but perhaps may be fixed separately, even at different points in time:
+
+* **Introducing calendar data**. Now we are doing this in 1001 places. Ideal it would be just one. The assumption of this task is that the one place would be Phabricator's calendar ([[ https://secure.phabricator.com/T7924 | today a prototype ]]), but other candidates should be considered.
+* **Pulling calendar data in other supports, mainly wiki pages**. While we could start linking from wiki pages to Phabricator calendar queries, the desired scenario would be a way for editors to embed calendars based on queries in wiki pages. This probably implies a Calendar API to query data ([[ https://secure.phabricator.com/T7944 | which is missing ]]) and a MediaWiki extension allowing to embed those queried calendars in wiki pages (which we don't have). Maybe this is just too much, and at least the tech-inclined Wikimedians would be fine clicking a Phabricator link.
+* **Integrating calendar data with other systems (mainly Google Calendar)**. ""[[ https://secure.phabricator.com/T7929 | Future work ]]"" upstream, no plans today.
+
+As we can see, deciding on Phabricator Calendar as the one place to introduce data would not provide a quick path to use that data out of Phabricator. However, what would be the alternatives? Other than defaulting to Google Calendar (which I think would be wrong as a matter of Wikimedia principles), I don't see a shortcut but others may have better ideas.",1459938293,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#19336, @Quiddity wrote:
+> * https://www.mediawiki.org/wiki/Meetings
+> * https://www.mediawiki.org/wiki/Architecture_meetings
+> * https://www.mediawiki.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Meetup
+
+* https://meta.wikimedia.org/wiki/IRC_office_hours and related tag #IRC-Meetings
+* https://meta.wikimedia.org/wiki/Community_Engagement/Calendar
+* https://www.mediawiki.org/wiki/Category:MediaWiki_developer_meetings",1459587043,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#19336, @Quiddity wrote:
+> * https://www.mediawiki.org/wiki/Meetings
+> * https://www.mediawiki.org/wiki/Architecture_meetings
+> * https://www.mediawiki.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Meetup
+
+* https://meta.wikimedia.org/wiki/IRC_office_hours and related tag #IRC-Meetings
+* https://meta.wikimedia.org/wiki/Community_Engagement/Calendar",1457464258,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2026016, @RobLa-WMF wrote:
+> Of course, [Upstream:T7929 (Integrate Calendar with external systems)](https://secure.phabricator.com/T7929) may be a blocker for us seriously moving over to this, but it adds enough value for repeating meetings and Phab integration that it's worth it for me (ymmv)
+
+RSS output would probably the most useful starter for us, For integration onto the wikis via E:RSS
+",1455406524,PHID-USER-hwuumsjqciw7ji5qhpc7,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"There's a new #IRC-Meetings tag, per T114322.  This tag is for all [Phabricator events](https://phabricator.wikimedia.org/calendar/query/upcoming/) that have an anticipated IRC component (e.g. office hours on #wikimedia-office).  A couple of queries:
+
+* **[All upcoming IRC meetings](https://phabricator.wikimedia.org/calendar/query/wiuSD6vCKuhA/)**
+* [All IRC meetings](https://phabricator.wikimedia.org/calendar/query/q0gEvg_5.lM_/)
+
+As of this writing, only #ArchCom-RFC meetings are in there, but hopefully that will expand as education grows.
+
+Of course, [Upstream:T7929 (Integrate Calendar with external systems)](https://secure.phabricator.com/T7929) may be a blocker for us seriously moving over to this, but it adds enough value for repeating meetings and Phab integration that it's worth it for me (ymmv)",1455406015,PHID-USER-edlps6xg553cjlnvd4ao,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Qgil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+-- Meetup calendar actually seems the most sharable and used within Wikipedia
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+**Wikimedia Phabricator calendar**
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it has more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+Erika, User:BrillLyle",1453746279,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Qgil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+**Wikimedia Phabricator calendar**
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it is more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+Erika, User:BrillLyle",1453746018,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+**Wikimedia Phabricator calendar**
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it is more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+Erika, User:BrillLyle",1453745970,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+**Wikimedia Phabricator calendar**
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it is more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+- Erika
+User:BrillLyle",1453745946,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+re: Wikimedia Phabricator existing calendar
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it is more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+- Erika
+User:BrillLyle",1453745922,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- Administrative burden on one or more people can be heavy
+- Duplication of effort 
+- Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- Google calendars can't be embedded on Wikipedia
+- Low sharability / visibility -- Google calendars are not super easy to add
+
+re: Wikimedia Phabricator existing calendar
+- Too many events: I think if there's too many events it will become unusable.
+- Color coding: Also the calendar needs to be color coded so it is more usability
+- Administrative burden: It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- Embeddability? Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+- Erika
+User:BrillLyle",1453745830,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- Administrative burden on one or more people can be heavy
+- Duplication of effort 
+- Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- Google calendars can't be embedded on Wikipedia
+- Low sharability / visibility -- Google calendars are not super easy to add
+
+re: Wikimedia Phabricator existing calendar
+- Too many events: I think if there's too many events it will become unusable.
+- Color coding: Also the calendar needs to be color coded so it is more usability
+- Administrative burden: It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+
+- Erika
+User:BrillLyle",1453745772,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I wonder whether #Community-Liaisons have any opinion about this proposal, considering that they Help organizing many of these activities (i.e. office hours).",1453726138,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#1960445, @Aklapper wrote:
+>>>! In T1035#1958506, @BrillLyle wrote:
+>> Is this still an active project?
+> 
+> @BrillLyle: Yes, people can [[ https://phabricator.wikimedia.org/calendar/event/create/ | create calendar events ]] in Wikimedia Phabricator. :)
+
+@Aklapper: Thanks for letting me know. Public calendars are a huge issue for Meetups -- not sure if it would be helpful to add such specific to locale events to this calendar but the interface looks great. Thanks!",1453666655,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#1958506, @BrillLyle wrote:
+> Is this still an active project?
+
+@BrillLyle: Yes, people can [[ https://phabricator.wikimedia.org/calendar/event/create/ | create calendar events ]] in Wikimedia Phabricator. :)",1453659554,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Is this still an active project? I stumbled upon this calendar when combing for national Wikimedia events. If this is active and is being used for local chapter meetup events, I would love to add the Wikimedia NYC events to this calendar so we can use this calendar in addition to the Google Calendar we are currently keeping. (Calendar ID: nnvhsl9su019vngvb58qb68u6o@group.calendar.google.com) -- Please let me know -- Erika aka BrillLyle",1453510534,PHID-USER-5orqjaw2whyidcs3hejo,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,fwiw #archcom is using Phabricator' calendar to organize their weekly meetings i.e. {E61} ,1441735624,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Email preferences have entries for calendar events that you could set to Ignore if you are not interested.
+
+Watching https://www.mediawiki.org/wiki/Project:Calendar and/or other calendar pages is not superior to subscribing only to the projects for the types of events you are interested about (i.e. Tech Talks yes but not Wikimedia Tech San Francisco Meetup) or defining whatever specific queries you are interested about.
+
+There is no iCal support in Phabricator (https://secure.phabricator.com/T7929). iCal for Wikimedia office hours is done via http://h2vx.com/, which doesn't seem to be able to digest our Phabricator URLs. Now idea when will upstream work on this, and how complex it is.
+
+But... an important factor is how simple it is to create events and announce them to those who probably care. Doing this on-wiki is a pain, and ultimately not very effective. I know well because I have done it multiple times. And another evidence is that there is only a few people creating events, and probably only a few people watching the relevant pages. An email to wikitech-l and a couple of mailing lists more keeps being our main way to reach our potential audience.
+
+When creating events is a pain, the rest of the process is broken. This is where Phabricator is clearly superior in the context of the Wikimedia tech community, because most potential users are already here, with the possibility to subscribe to the projects they care about.",1440672160,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Personally I don't see a benefit in this proposal. https://phabricator.wikimedia.org/settings/panel/emailpreferences/ doesn't have any useful notification setting for ""calendar"" things and I'm certainly not going to watch a project just for the sake of getting notifications of events which might be attached to it.
+
+MediaWiki transclusion, watchlist and enotifwatchlist are vastly superior features and integration with iCal applications is not particularly difficult: as far as I know, it's provided successfully for https://meta.wikimedia.org/wiki/IRC_office_hours (see there).",1440669277,PHID-USER-v7bwpq3rs3zdxegibdbh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thanks for this list of pages, @quiddity. I have announced this proposal at
+
+> * https://www.mediawiki.org/wiki/Meetings
+> * https://www.mediawiki.org/wiki/Architecture_meetings
+> * https://www.mediawiki.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Events
+> * https://www.mediawiki.org/wiki/Bug_management/Triage
+> * https://meta.wikimedia.org/wiki/Meetup
+
+Not at this one because it felt too off-topic:
+> * https://en.wikipedia.org/wiki/Wikipedia:Meetup",1440668646,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Proposal completely revamped. Feedback welcome.,1440668113,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Furthermore, [[ https://www.mediawiki.org/wiki/Hackathon | mw:Hackathon]] redirects to [[ https://www.mediawiki.org/wiki/Events | mw:Events]] but [[ https://www.mediawiki.org/wiki/Hackathons | mw:Hackathons]] does not and that plural page includes stuff that should be merged as part of T85598.",1422314971,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wasn't aware of this task and Quiddity's great list above (thanks!) when I wrote the following lines yesterday night in an email:
+
+ Trying to get an overview as an outsider: https://www.mediawiki.org/wiki/Events seems to be about physical events that last longer than two hours and https://www.mediawiki.org/wiki/Meetings seems to be even deader though some recent tech talks are listed there too. Hmm. There's also office hours on https://meta.wikimedia.org/wiki/IRC_office_hours
+
+ So currently there seems to be a division by either medium or format of activity, expressed via different pages. I can't easily get an overview of what's cooking or might be somehow ""joinable"" for me.
+
+If I had too much time I might try to merge all into one table on one page, and have 
+* 'medium' (IRC Office Hour? Physical Happening? Video hangout?) and 
+* 'content/format' (TechTalk presentation? WMFMetrics presentation? ECT TeamMeeting? Techy Hackathon? Non-techy Edithon? Booth/stand at some conference? Q&A on Phabricator? Other?) columns/pre-defined classifications that allow filtering (does MediaWiki support that?).",1418815978,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Note that there is an additional risk (positive or not, I still don't know) of having yet another calendar: {T466}",1415260538,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Agreed. I'm often confused as to why ""X"" isn't mentioned, and then I realize it's at the //other// page...  ([[https://meta.wikimedia.org/wiki/Mergism|Mergism]] is often good, when a few short pages are involved. :)
+
+Here are some more ""scheduled/re-occurring"" meetings, some or all of which should be considered for merging. (Or for upgrading, once there's a better system that we can recommend.)
+* https://www.mediawiki.org/wiki/Meetings
+* https://www.mediawiki.org/wiki/Architecture_meetings
+* https://www.mediawiki.org/wiki/Events
+* https://meta.wikimedia.org/wiki/Events
+* https://www.mediawiki.org/wiki/Bug_management/Triage
+* https://meta.wikimedia.org/wiki/Meetup
+* https://en.wikipedia.org/wiki/Wikipedia:Meetup
+",1415234931,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"actions such as adding projects or tags, adding cc's or assigning owner, changing security should be more easily added, removed or modified. ",1414186408,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_description,resolved
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"This is now implemented for status, priority, assignee, points, project tags subscribers and even workboard column.
+
+The only fields that can't be edited in-line with the comment form are title, description and advanced things like visibility policy.",1463618910,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"Tangentially, if you click ""2 others"" on this task, you get an in-browser pop-up window and even that window has no write capability. :-(
+
+>>! In T870#933937, @Jaredzimmerman-WMF wrote:
+> On your flickr photo pages, and on your facebook ""about"" section almost all fields are editable this way, If I remember correctly this is how Jira tasks were as well. I feel like some aspects of bugzilla were like this as well, but not that its locked I can't point to specific ones. 
+
+Yep, JIRA has this functionality (using a standard pencil icon on hover) and Bugzilla had similar functionality.
+
+Broadly the ""Add Comment"" box is probably mislabeled. But this task appropriately focuses on making the fields at the top of every task easier to modify. I think this is medium-ish priority, but definitely worth pursuing.",1420007762,PHID-USER-hyfm4swq76s4j642w46x,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"On your flickr photo pages, and on your facebook ""about"" section almost all fields are editable this way, If I remember correctly this is how Jira tasks were as well. I feel like some aspects of bugzilla were like this as well, but not that its locked I can't point to specific ones. ",1418937041,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"As I understand this request, users could click on the title of any field in a task page, and then such field would become editable, seamlessly.
+
+Not like VisualEditor ""all page is yours now"", field by field. I have seen this behavior before somewhere, I just don't remember where. Giving real examples might help this task moving forward upstream.",1418914734,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"@chasemp still 3, just a different 3",1418856171,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,you can do all 3 in the action drop down with 2-ish?,1418854492,PHID-USER-3neel27i7dyu62jbbx2l,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"@Aklapper I'm more referring to status, assigned, cc, currently these are all 3 actions, when they could just as easily be 1 or two ",1418854426,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"Might have been a fundamental design decision of upstream (though I cannot find any past discussions) to ""hide"" some not too common actions under a separate ""edit"" page. 
+It also makes the task view less cluttered (""Visible To"", ""Editable By"", ""Security"" checkbox not exposed, in my case at least).",1418840397,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"Nice feature, but I have no idea about the complexity.",1418825004,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Allow shortcut keys for text formatting and action in description fields like CMD+B, CMD+K, CMD+I, etc. ",1414018531,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-qku5ds4p6huc4ehidnf2,task_description,declined
+Shortcut keys for description fields text formatting are needed. ,Declining as per T816#5224212 and as several other ways to achieve similar functionality were provided.,1562205607,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,Another possibility would be something like https://addons.mozilla.org/en-US/firefox/addon/shortkeys/,1559769252,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"This looks like a couple of different requests:
+
+  - Add text formatting shortcuts like {key command B} (or whatever) to make selected text bold when editing text in a Remarkup text area.
+  - Add navigation shortcuts for a lot of other stuff.
+
+I don't currently plan to add either feature to the upstream.
+
+In both cases, we've seen relatively little interest in these features and they're somewhat complex to implement, test, and maintain. One issue in all cases here is conflicts with existing browser and OS shortcuts: for example, {key command B}, {key command K}, {key Control K}, {key Command U} and {key Command I} all do something in at least one of Safari, Firefox, or Chrome on macOS.
+
+For global navigation (like ""View Notifications""), you can probably bookmark the URL and use browser shortcut features, or use OS-level shortcut features with `open <url>`.
+
+For quicker access to on-page actions, you might be able to use accessibility features of your OS. For example, with VoiceOver you can {key Control Option I} to pull up a list of all links on a page, then type ""sub"" to select the ""subscribe"" link. This may or may not be a great fit, but is a general-purpose solution to providing keyboard access to the page if you need accessibility affordances because of poor vision, limited dexterity, RSI injury, etc.
+
+You can also use ""Bulk Edit"" to bulk-edit multiple tasks in a single action, or the API to automate a larger number of more complex edits.",1559233887,PHID-USER-ic77k5i4bubodmfnpbui,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,@aklapper: [[ https://en.wikipedia.org/wiki/Repetitive_strain_injury | Repetitive strain injury ]],1505493435,PHID-USER-fn7qnpccfbitivgtw2rt,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"What is ""RSI""?",1505490799,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Task specific shortcuts:
+
+* Edit task
+* Subscribe / unsubscribe
+* Assign to self
+* Remove assignment
+* Close task
+
+Navigation shortcuts:
+
+* Go to notifications
+* Go to RSI help page",1505473120,PHID-USER-mye6umixnhfo7lhpgzmj,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Task specific shortcuts:
+
+* Edit task
+* Subscribe / unsubscribe
+* Assign to self
+* Remove assignment
+* Close task
+
+Navigation shortcuts:
+
+* Go to notifications",1505473005,PHID-USER-mye6umixnhfo7lhpgzmj,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,">>! In T816#3296416, @Aklapper wrote:
+> See wontfix'ed https://secure.phabricator.com/T1931#144486 asking for use cases.
+
+You're probably the most active phab user here, so maybe you could add a list of use-cases? (If you're generally a user of keyboard shortcuts, of course!) - I do my triage via email, so cannot really help.",1496450839,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,See wontfix'ed https://secure.phabricator.com/T1931#144486 asking for use cases.,1495916660,PHID-USER-hgn5uw2jafgjgfvxibhh,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,I'd love some navigational shortcuts. Go to notifications is an obvious one (ctrl + n).,1461864852,PHID-USER-mye6umixnhfo7lhpgzmj,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"""Shortcut keys for description fields"" is too vague. I think we will have a better chance if specific shortcuts are requested, like in https://secure.phabricator.com/T704",1420809229,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"2 Closed Phab bugs:
+* Suggestion of going towards Github's standard of shortcuts, for Differential at least. (j/k for prev/next), done in https://secure.phabricator.com/T184
+* Feature request for ctrl-Enter to submit a comment, https://secure.phabricator.com/T704
+But nothing about bold/italic/link/code/etc.
+
+----
+Here are Mediawiki's shortcut standards: 
+* Mediawiki (navigational): https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts#Modifier_keys
+* VE (text formatting): https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts
+
+Here are Github's and Gerrit's:
+* https://help.github.com/articles/using-keyboard-shortcuts/
+* https://git.eclipse.org/r/Documentation/images/intro-quick-hot-key-help.jpg",1414564414,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"2 Closed Phab bugs:
+* Suggestion of going towards Github's standard of shortcuts, for Differential at least. (j/k for prev/next), done in https://secure.phabricator.com/T184
+* Feature request for ctrl-Enter to submit a comment, https://secure.phabricator.com/T704
+But nothing about bold/italic/link/code/etc.
+
+----
+Here are Mediawiki's shortcut standards: 
+* Mediawiki (navigational): https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+* VE (text formatting): https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts
+
+Here are Github's and Gerrit's:
+* https://help.github.com/articles/using-keyboard-shortcuts/
+* https://git.eclipse.org/r/Documentation/images/intro-quick-hot-key-help.jpg",1414564371,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"2 Closed Phab bugs:
+* Suggestion of going towards Github's standard of shortcuts, for Differential at least. (j/k for prev/next), done in https://secure.phabricator.com/T184
+* Feature request for ctrl-Enter to submit a comment, https://secure.phabricator.com/T704
+But nothing about bold/italic/link/code/etc.
+
+----
+Here are Mediawiki's shortcut standards: 
+* Mediawiki (navigational): https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+* VE (text formatting): https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts
+
+Here's Github's and Gerrit's:
+* https://help.github.com/articles/using-keyboard-shortcuts/
+* https://git.eclipse.org/r/Documentation/images/intro-quick-hot-key-help.jpg",1414564354,PHID-USER-hphmqcx66p6d6gvmjzp7,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Phabricator saves the text you are typing with some persistence (which is very useful if your connection drops, your browser crashes, etc). My bet is that you had typed ""test"" at some point while creating a task, and then you created this task here without any description (tsk tsk)  :) , and you didn't notice that your ""test"" was still there.",1414021678,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"I didn't type test… I see it there, but I didn't add it. Is there default description that is being added?",1414020873,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Sorry, for some reason reading ""test"" as sole description made me think this was a test.  :)",1414020799,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Wasn't an experiment, where do we log bugs against phabricator? bugzilla?",1414019041,PHID-USER-z3kqk2bjnqneldcznht6,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Hi, this is a production instance. Please file only legitimate tasks.
+
+We have https://phab-01.wmflabs.org/ for experimenting and learning.",1414018835,PHID-USER-lluzkul4z7us4sxkayss,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,The [[https://secure.phabricator.com/book/phabricator/article/remarkup/|ReMarkup]] system is not wikitext and not Markdown. Sad.,1397576333,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_description,declined
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,//importing issue status//,1410485105,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-09-04 11:06:07 (UTC)`
+
+I do not see a reason to switch off markup (and I don't think it's possible). I don't see much ""confusion"" because **there is a preview of your comment**. Plus functionality like @aklapper is nothing I want to switch off.",1410485105,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Svetlana** wrote on `2014-09-03 23:46:32 (UTC)`
+
+Can we force it to go plaintext? That could be nice, to avoid confusion of people who see an 'italic' button which adds //.",1410485105,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-09-03 14:23:49 (UTC)`
+
+>>! In T100#48, @Nemo_bis wrote:
+> Then just disable the phabricator-specific markup, no? Is there any reason we need a markup?
+
+Same reasons phab-specific markup exists as any other markup: It's convenient.",1410485104,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Nemo_bis** wrote on `2014-09-03 14:15:50 (UTC)`
+
+> In fact, it takes less work to copy a Wikimedia URL from your browser and paste it here than typing the mw:etc custom strings manually.
+
+Then just disable the phabricator-specific markup, no? Is there any reason we need a markup?",1410485104,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**qgil** wrote on `2014-09-01 07:26:21 (UTC)`
+
+In fact, it takes less work to copy a Wikimedia URL from your browser and paste it here than typing the mw:etc custom strings manually.
+
+After months of daily Phabricator use and after reading this discussion again, I think we can Decline this request.",1410485104,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**scfc** wrote on `2014-08-31 19:26:56 (UTC)`
+
+FWIW, as @aklapper said, the preview function (dearly missed in Bugzilla) makes this a not-so-big problem.
+
+Personally, I strongly favour full-fledged URLs over [[wikilinks]] because:
+
+  # They prevent users from messing with ""evidence"" relevant to a bug; if they just have to copy & paste something, the chances are much higher that what they report is what they actually experienced.
+  # They work //everywhere//, i. e. if you read a bug report in your mailbox, you don't have to set up a local filter and keep that in sync with the tracker, but you can just click on a link.",1410485103,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-08-26 09:59:47 (UTC)`
+
+For comparison, Bugzilla's [[https://bugzilla.wikimedia.org/buglist.cgi?bug_id=29506,41851,51720 | half-working]] ability to turn [[:mw:Extension:Flow]] into a link is a [[ https://git.wikimedia.org/blob/wikimedia%2Fbugzilla%2Fmodifications.git/HEAD/extensions%2FWikimedia%2FExtension.pm#L31 | custom patch on our side]]. Whether something similar is doable and feasible in Phabricator remains to be investigated by anybody willing to dive into the codebase (and upstream is very responsive in helping).
+
+If you are strongly interested in performance differences I recommend to contact upstream development for more information.",1410485103,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Svetlana** wrote on `2014-08-26 09:14:29 (UTC)`
+
+There is the routine work of having to click through or type through many times to link to common things like [[:mw:Extension:Flow]]. There is another task of having to ""learn a new markup"". The latter appears to be discussed extensively in this task and a visual editor could indeed help (or we could kick and scream a little and have Parsoid service break into this site).
+
+The former (routinely linking to mw and other sites) needs more attention. Implementing this would indeed be a repetition of the parser that Wiki uses which could probably be inefficient - some more insight is needed here; I wouldn't like to //assume// anything. If it is slower then //how// slower is it? Such feature would probably not be needed for other companies using Phabricator: they typically don't have a wiki farm, and may as-well do everything right in Phabricator itself. Phabricator is free software. Surely it's within its philosophy to be extensible and script-able to suit such specific needs?
+
+I'd suggest to split this task and move over some interwiki-related comments over to a new task.",1410485102,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-06-16 11:07:45 (UTC)`
+
+>>! In T100#40, @Nemo_bis wrote:
+> Ok, but at least not double brackets for external links, as Guillaume says in T100#14... And yes, I think such a decision must be before day 1.
+
+The comment preview would tell that markup parsing expectations from MediaWiki do not work out in Phabricator. 
+I expect a frustration level similar to Bugzilla and our custom regexes over there. Neither better nor worse. Which makes this not block day 1 for me currently.
+ --~~~~ (Y signature no work on tis Phabicreator wiki?!?!)",1410485102,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Nemo_bis** wrote on `2014-06-15 10:15:27 (UTC)`
+
+>>! In T100#39, @aklapper wrote:
+> I was missing a rationale for ""we'd really like to switch it to something else if possible"" in the task summary but I guess it translates to ""I'm used to wikitext markup and don't see good enough reasons to learn something else"".
+
+Given it was set by James, it probably rather means ""what's wrong with HTML after all"". :P
+
+Performance, really? Ok, but at least not double brackets for external links, as Guillaume says in T100#14... And yes, I think such a decision must be before day 1.",1410485102,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-05-23 03:40:42 (UTC)`
+
+I was missing a rationale for ""we'd really like to switch it to something else if possible"" in the task summary but I guess it translates to ""I'm used to wikitext markup and don't see good enough reasons to learn something else"".
+
+In any case I don't think that this should //block// Day 1 of Phabricator in production so I've changed the project of this task and added Maintenance (after day 1) instead.
+
+Reasons:
+You can actually see in the preview how your text will look like (compared to Bugzilla commenting) so you can realize beforehand that wikitext parsing might not work as expected. In the worst case people will realize that they need to paste full URLs - slightly more inconvenient, but not a dealbreaker IMHO. Furthermore, see RobLa's comment 33 above.
+
+> We definitely don't need to patch the parser to set links between bugs, with Gerrit, RT, or with Wikimedia wiki pages. The existing Bugzilla links can be converted during the migration.
+
+Good point; Added a comment to T39.",1410485101,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**qgil** wrote on `2014-05-15 18:13:55 (UTC)`
+
+We shouldn't maintain a local patch just because. If there is a very good reason to add some functionality, then it could be proposed upstream. 
+
+We definitely don't need to patch the parser to set links between bugs, with Gerrit, RT, or with Wikimedia wiki pages. The existing Bugzilla links can be converted during the migration.",1410485101,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**robla** wrote on `2014-05-14 19:10:18 (UTC)`
+
+The Phabricator folks explain their rationale for yet another markup language in https://secure.phabricator.com/T2849
+
+In a nutshell, they've packed a bunch of functionality into a syntax that is very efficient to parse.  One of the things that makes Phabricator a pleasure to use is the performance, so I would be hesitant to implement a (likely) less efficient, feature poor parser in the name of making something that we hope is vaguely headspace compatible with Mediawiki markup.  If we're concerned about usability, I would rather we push the Phabricator folks to implement visual editing like we ourselves are doing.",1410485101,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**jdforrester** wrote on `2014-05-10 20:35:20 (UTC)`
+
+◀ Merged tasks: T165.",1410485100,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Krenair** wrote on `2014-04-20 16:06:21 (UTC)`
+
+@Rillke If we implemented it again the default wiki obviously wouldn't be enwiki (probably mediawiki.org or maybe wikitech), so it wouldn't change much for them.",1410485100,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**qgil** wrote on `2014-04-20 15:24:50 (UTC)`
+
+In general, I would be reluctant to any local patches, except when they provide functionality that we would not get with the stock software.
+
+In any case, I don't think lack of wikitext parsing would stop us from migrating. Setting priority as Wishlist for now. My opinion is Wontfix.
+
+No guideline would be needed. Plain MediaWiki and VisualEditor also have a chain icon to define external links. When users click this icon, the rest is also obvious.",1410485099,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Rillke** wrote on `2014-04-20 11:57:05 (UTC)`
+
+> Can we please not implement wikitext again?
+
+@Krenair Yeah but then we should have some guide how to achieve the same, although phabricator has some nice toolbars and instant preview. I will not miss this feature very much because I mostly linked to `:commons:` and `:de:` (thus not a lot shorter or faster) but the `:en:`-guys may complain.",1410485099,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Krenair** wrote on `2014-04-20 11:40:29 (UTC)`
+
+Can we please not implement wikitext again?",1410485099,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**gpaumier** wrote on `2014-04-18 10:47:45 (UTC)`
+
+@aklapper The problem is that Remarkup uses the same syntax for external links as well, e.g.:
+  [[https://fr.wikipedia.org | Wikipédia]]
+
+There is an alternate Markdown-like syntax for external links:
+  [Wikipédia](https://fr.wikipedia.org)
+but the one with double brackets is the one inserted by default by the toolbar. 
+
+I don't know how customizable / fixable this is, but I just wanted to raise the issue for completeness :)",1410485098,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-04-18 10:31:46 (UTC)`
+
+...and that page says:
+
+[[wiki page]]             # Link to Phriction
+[[wiki page | name]]      # Named link to Phriction
+
+so with a small (?) code change we could hopefully link to mediawiki.org or whatever instead. Maybe.",1410485098,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-04-18 10:15:09 (UTC)`
+
+For the records, https://secure.phabricator.com/book/phabricator/article/remarkup/ covers the auto-linking stuff.",1410485098,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-04-17 12:45:09 (UTC)`
+
+Also see T88",1410485097,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-04-17 12:40:57 (UTC)`
+
+Haven't checked Phab's code, but as it autolinks numbers followed by a certain letter I'd assume somebody could patch the code and reuse the regexes we have in https://git.wikimedia.org/blob/wikimedia%2Fbugzilla%2Fmodifications.git/HEAD/extensions%2FWikimedia%2FExtension.pm",1410485097,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Rillke** wrote on `2014-04-15 15:39:46 (UTC)`
+
+[[ :de:Test | Testcase ]]",1410485097,PHID-USER-nyhmztvvw4luz5mlcuvg,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
diff --git a/src/helper_scripts/cleaning_scripts/0220_ve_rfcs_text.csv b/src/helper_scripts/cleaning_scripts/0220_ve_rfcs_text.csv
new file mode 100644
index 0000000..4a8430e
--- /dev/null
+++ b/src/helper_scripts/cleaning_scripts/0220_ve_rfcs_text.csv
@@ -0,0 +1,291 @@
+comment_text,date_created,Author
+"['==Watchlist notice?==\n', ""Any reason why there isn't one?  WP:CENT isn't enough.  [[User:Risker|Risker]] ([[User talk:Risker|talk]]) 18:56, 30 July 2013 (UTC)\n""]","18:56, 30 July 2013 (UTC)",Risker
+"[': This is now moot given the (much more prominent) [https://en.wikipedia.org/w/index.php?title=MediaWiki:Sitenotice&diff=566640843&oldid=534920727 site notice]. --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 03:03, 1 August 2013 (UTC)\n']","03:03, 1 August 2013 (UTC)",MZMcBride
+"['== How do I answer this ""until the current major bugs are fixed""? ==\n', '\n', 'I want to say that it should be opt-in for everyone, but only until the current set of major bugs are fixed. Then I want the developers to try again with opt-out. Should I add third options to the binary answers or what? [[User:EllenCT|EllenCT]] ([[User talk:EllenCT|talk]]) 19:03, 30 July 2013 (UTC)\n']","19:03, 30 July 2013 (UTC)",EllenCT
+"[':I\'d say that, if opt-in passes, we should follow this up with a poll as to what would be necessary before an opt-out. I, for one, would want support of basic wikitext and an end to the stupid on-hover-based selection of which tool to use for section editing, in addition to fixing major bugs, myself, largely because the VE team has made it clear they \'\'categorically refuse\'\' to fix those, despite them causing the &lt;nowiki&gt; bug and making section editing impossible on screen readers, respectively. <span style=""text-shadow:grey 0.118em 0.118em 0.118em; class=texhtml"">\'\'\'[[User:Adam Cuerden|Adam Cuerden]]\'\'\' <sup>([[User talk:Adam Cuerden|talk]])</sup></span> 10:14, 31 July 2013 (UTC)\n']","10:14, 31 July 2013 (UTC)",Adam Cuerden
+"['::Are they refusing to fix table editing and cross-browser support? [[User:EllenCT|EllenCT]] ([[User talk:EllenCT|talk]]) 17:37, 31 July 2013 (UTC)\n']","17:37, 31 July 2013 (UTC)",EllenCT
+"[':::No, table editing is on the list, and apparently always has been on the list for this quarter.  Some old browsers will never be supported.  I believe this is largely because those browsers are either quite rare or because they are simply incapable of handling the necessary actions (or both).  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 22:56, 31 July 2013 (UTC)\n']","22:56, 31 July 2013 (UTC)",Whatamidoing (WMF)
+"['==What is the VisualEditor?==\n', '\n', 'in my opinion, this Request for Comment illustrates why some users, myself included, find the Wikipedia a technically challenging place.\n', '\n', ""How can I comment on something when it isn't even explained what the  Visual Editor is, or what it does?  The wiki techies just assume that everyone has the same level of knowledge that they do.  This simply isn't the case.\n"", '\n', 'The very first bullet in this RFC should be an explanation of what the Visual Editor is.\n', '[[User:Mr Serjeant Buzfuz|Mr Serjeant Buzfuz]] ([[User talk:Mr Serjeant Buzfuz|talk]]) 14:51, 31 July 2013 (UTC)\n']","14:51, 31 July 2013 (UTC)",Mr Serjeant Buzfuz
+"[':[[Wikipedia:VisualEditor]].  It is the editing interface that you get right now when you click ""edit"" on an article.  [[User:Mr Serjeant Buzfuz|Mr Serjeant Buzfuz]], it is possible that you edit using one of the blacklisted browsers (Internet Explorer is blacklisted, for example) so have not encountered this editing interface.  [[User:Risker|Risker]] ([[User talk:Risker|talk]]) 15:55, 31 July 2013 (UTC)\n']","15:55, 31 July 2013 (UTC)",Risker
+"['\n', 'I sorta know what VE is from a previous notification, and actually tried it a little, but it didn\'t work on templates.  I am an Internet Explorer user, and thus blacklisted for who knows how long, which I also learned back when VE was supposedly (my pov) activated.  So why am I getting this notification?  Can\'t it be turned off for IE users?  I just wasted 15 minutes or so trying to figure out if it was actually working for IE users yet.  Please don\'t bother me till it\'s actually working for IE users, or at least include ""IE users need not apply"" or equivalent in a prominent place.  Thanks. [[User:Cpfan776|Cpfan776]] ([[User talk:Cpfan776|talk]]) 02:07, 1 August 2013 (UTC)\n']","02:07, 1 August 2013 (UTC)",Cpfan776
+"['== Focusing on improvements ==\n', '\n', ""While this [[WP:RFC|RFC]] somewhat heads in this direction, I think we should recognize that VisualEditor is the future and instead spend time and energy focusing on possible real, actionable  '''[[Wikipedia:VisualEditor/Improvements|improvements]]''' to VisualEditor. --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 17:14, 31 July 2013 (UTC)\n""]","17:14, 31 July 2013 (UTC)",MZMcBride
+"[':Why not support the [[Wikipedia_talk:VisualEditor#WikiProject_VisualEditor|wikiproject proposal]] instead of making more new buried pages?  There seems to be good support, so why not just start that page? [[User:Risker|Risker]] ([[User talk:Risker|talk]]) 17:22, 31 July 2013 (UTC)\n']","17:22, 31 July 2013 (UTC)",Risker
+"[':: A full response to these questions is available [https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:VisualEditor&oldid=566664245#Focusing_on_improvements here]. --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 03:12, 1 August 2013 (UTC)\n']","03:12, 1 August 2013 (UTC)",MZMcBride
+"[""''[Edit conflict]''\n"", ':VE is \'\'potentially\'\' the future, for \'\'some\'\' editors. However, it probably will never be suitable for low-bandwidth users on old computers, for example. Also,t he VE teasm\'s decisions have repeatedly crippled it, such their decision not to support Wikitext, instead causing buggy nowiki behaviour - the bug for that one has recently been marked ""WONTFIX"". Or the screenreader-breaking and generally poor functionality of the on-hover selection of which editor to use to edit sections. \n', ':VE is only the future should the VE team have some sense knocked into them. \n', "":If it's turned off, I'd say the next step is an RFC about VE itself. Something like:\n"", "":'''Feature/bugfix'''\n"", "":''Description''\n"", "":'''Option 1: VE should not be turned on until after this is in place'''\n"", "":'''Option 2: This must be included eventually, but is fine waiting until a while after relaunch'''\n"", "":'''Option 3: Not important to me'''\n"", ':\n', ':Run that with enough options, and VE might become the ffuture after all. <span style=""text-shadow:grey 0.118em 0.118em 0.118em; class=texhtml"">\'\'\'[[User:Adam Cuerden|Adam Cuerden]]\'\'\' <sup>([[User talk:Adam Cuerden|talk]])</sup></span> 17:30, 31 July 2013 (UTC)\n']","17:30, 31 July 2013 (UTC)",Adam Cuerden
+"['== Different responses between English and German wikipedias==\n', ""I've noted several people pointing to the results of a poll on the German Wikipedia.  Please note some very major differences between what we are doing on the page here, and what they did there.  None of this multiple questions, they were straightforward and just voted on whether or not it should be opt-in.  ONE question, publicised everywhere on their project. That is how they get over 400 people to voice an opinion.  [[User:Risker|Risker]] ([[User talk:Risker|talk]]) 17:22, 31 July 2013 (UTC)\n""]","17:22, 31 July 2013 (UTC)",Risker
+"["":I hope this doesn't fail because I'm not good at organizing this kind of thing. Most people seem to be only answering question 1, anyway. Would I cause trouble by just adding a site notice that publicizes the RFC? Where would I go to get consensus to do so?&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 17:35, 31 July 2013 (UTC)\n""]","17:35, 31 July 2013 (UTC)",Kww
+"['::[[WP:AN]], I think. Or, in theory, you could [[WP:BOLD]] edit [[MediaWiki:Sitenotice]] and [[MediaWiki:Sitenotice id]]; the only real rule seems to be it has to be something that affects all users. <span style=""text-shadow:grey 0.118em 0.118em 0.118em; class=texhtml"">\'\'\'[[User:Adam Cuerden|Adam Cuerden]]\'\'\' <sup>([[User talk:Adam Cuerden|talk]])</sup></span> 17:37, 31 July 2013 (UTC)\n']","17:37, 31 July 2013 (UTC)",Adam Cuerden
+"[""::KWW, I give you a lot of credit for starting this, especially after efforts by others were firmly rebuffed earlier in the process, and how much work and how much pressure from people even outside our usual editing community it took just to get the opt-out button on this project.  There is some hope for change, based on [http://lists.wikimedia.org/pipermail/wikimedia-l/2013-July/127354.html Erik's recent post to Wikimedia-L mailing list]. [[User:Risker|Risker]] ([[User talk:Risker|talk]]) 20:38, 31 July 2013 (UTC)<small> Updated with link now that Quiddity has passed it to me</small>\n""]","20:38, 31 July 2013 (UTC)",Risker
+"[""== Where's Question 5? ==\n"", '\n', ""I can't find question 5. Whether it is a typo or a dropped question can anyone please check in regards to its fate? --'''[[User:Marianian|Marianian]]'''<sup>([[User_talk:Marianian|talk]])</sup> 23:04, 31 July 2013 (UTC)\n""]","23:04, 31 July 2013 (UTC)",Marianian
+"[': http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Default_State_RFC&diff=566435922&oldid=566434802 shows that for some reason, the numbering went from 1,2,3,4 to 1,2,2.5,3,4 to 1,2,2.5,3,4,6. No idea why.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 23:17, 31 July 2013 (UTC)\n']","23:17, 31 July 2013 (UTC)",Kww
+"['::I went ahead and renumbered it. <span style=""text-shadow:grey 0.118em 0.118em 0.118em; class=texhtml"">\'\'\'[[User:Adam Cuerden|Adam Cuerden]]\'\'\' <sup>([[User talk:Adam Cuerden|talk]])</sup></span> 01:15, 1 August 2013 (UTC)\n']","01:15, 1 August 2013 (UTC)",Adam Cuerden
+"['== Special credit ==\n', '\n', 'While I specified in the top paragraph that this RFC was not a place to vent, I have to give special credit to [[User:Starblind|Starblind]]:\n', '\n', ""{{quote box\n|quote=This seems downright cruel given WP's supposed focus on editor retention/recruitment. Would anyone go to Disneyland if all they could ride was ''It's A Small World'', which was broken and on fire?\n|source=[http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Default_State_RFC&diff=566641247&oldid=566641204|Starblind]\n|align=center\n}}\n"", ""<br>That said, ''stop that''.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 23:11, 31 July 2013 (UTC)\n""]","23:11, 31 July 2013 (UTC)",Kww
+"['== Way too many edit conflicts ==\n', '\n', 'Yeah. —[[User:ITAC|<math>\\mathrm{ITAC}</math>]] [[User talk:ITAC|<math>\\mathrm{talk}</math>]] 23:16, 31 July 2013 (UTC)\n']","23:16, 31 July 2013 (UTC)",ITAC
+"['== A modest question ==\n', ""So are any of the WMF staff testing with Visual Editor? If no, why not? After all the bad feelings the average contributor has for VE, I'd think doing that would be an important sign of support for it. And considering this project will serve as Sue Gardner's legacy at Wikipedia, I would hope she is making edits with it & using her experience to help make this the best piece of software possible. (Unless she wants to be known for being responsible for a buggy WYSIWYG editor that veteran editors refuse to use, & newbie editors find as difficult to use as editing Wikicode directly.) -- [[User:Llywrch|llywrch]] ([[User talk:Llywrch|talk]]) 01:09, 1 August 2013 (UTC)\n""]","01:09, 1 August 2013 (UTC)",Llywrch
+"["":I would certainly oppose adding that to this RFC. It's not a direct actionable question that we need to get a sense of the community's feeling on.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 01:12, 1 August 2013 (UTC)\n""]","01:12, 1 August 2013 (UTC)",Kww
+"[""::Sue's contributions are [http://en.wikipedia.org/w/index.php?title=Special:Contributions&offset=20140101000000&limit=50&tagfilter=&contribs=user&target=Sue+Gardner&namespace=0 just as visible] as anyone else's, so you can check if you'd like to know.  \n"", ""::In general, staff isn't supposed to change content in their role as staff members, so you won't usually find many edits to articles in staff accounts.  (For example, my article-edit count on the English Wikipedia is currently zero.)  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 17:25, 1 August 2013 (UTC)\n""]","17:25, 1 August 2013 (UTC)",Whatamidoing (WMF)
+"['== Why just new users and anonymous editors? ==\n', '\n', ""NVM. They don't care. They spent time developing something and it's going to be pushed forward no matter what we say. --[[User:Onorem|Onorem]] ([[User talk:Onorem|talk]]) 01:15, 1 August 2013 (UTC)\n""]","01:15, 1 August 2013 (UTC)",Onorem
+"[':Thank you for responding. --[[User:Onorem|Onorem]] ([[User talk:Onorem|talk]]) 02:24, 4 August 2013 (UTC)\n']","02:24, 4 August 2013 (UTC)",Onorem
+"['::Not sure what you were asking here? Everyone got VisualEditor, not just the groups you mentioned. Thanks. --[[User:Elitre (WMF)|Elitre (WMF)]] ([[User talk:Elitre (WMF)|talk]]) 07:00, 4 August 2013 (UTC) PS: if you were talking about questions at the RfC, there is at least one which demands plain switch-off.\n']","07:00, 4 August 2013 (UTC)",Elitre (WMF)
+"["":::The site notice, or watchlist thing, or whatever it was inviting new users and anonymous editors to this page. NVM. I really don't remember where I saw it, and I really don't care now. --[[User:Onorem|Onorem]] ([[User talk:Onorem|talk]]) 22:01, 4 August 2013 (UTC)\n""]","22:01, 4 August 2013 (UTC)",Onorem
+"['I bought twitter for dummies(like me), but I haven\'t yet had time to read it. I am looking forward to being more wiki fluent.  <small><span class=""autosigned"">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Susiedarling|Susiedarling]] ([[User talk:Susiedarling|talk]] • [[Special:Contributions/Susiedarling|contribs]]) 01:40, 1 August 2013 (UTC)</span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->\n']","01:40, 1 August 2013 (UTC)",Susiedarling
+"["":Twitter for dummies. The name is perfect. Is there a facebook version? I think Wikipedia wants to review both because it sure seems like they're trying their hardest to make us more like both. --[[User:Onorem|Onorem]] ([[User talk:Onorem|talk]]) 13:34, 6 August 2013 (UTC)\n""]","13:34, 6 August 2013 (UTC)",Onorem
+"['== Suggested changes ==\n', '\n', ""Firstly, I want to say that I and the other members of the VisualEditor team greatly appreciate the interest and time dedicated by members of the community. It's a delight to work on software that people really care about. As a longtime Wikipedian, I am deeply committed to getting this right.\n"", '\n', ""With that in mind: we hear you. We're reading everything, and discussing daily. You are not being ignored. I read the comments here and throughout the wikis, as does Erik, as does Philippe and his team.\n"", '\n', ""As background, I strongly suggest that you read Erik's post on [http://lists.wikimedia.org/pipermail/wikimedia-l/2013-July/127331.html the Wikimedia-l mailing list yesterday], which lays out our thinking and in particular on the need to maintain a steady and representative stream of users, not just for reporting bugs, but also to help us validate changes as we make iterations every few days. We cannot develop VisualEditor in isolation from real users.\n"", '\n', 'That doesn\'t mean, though, that we need to continue running it in ""firehose mode"" as the primary editor. Therefore, I\'d like to propose the following changes:\n', '\n', '* We switch the tabs back around so that wikitext editor is more prominent as the ""primary"" way to edit.\n', '* We also re-label the edit tab and section edit links to further emphasise that VisualEditor is not longer the primary. For instance, we could label them ""Edit source"" (or ""Edit"") and ""VisualEditor"" (or ""VisualEditor <sup>beta</sup>"") - I\'m not sure what works best here.\n', '* We remove the animation from the section edit links, showing both links all the time (with the VisualEditor link second, like the edit tabs, using the same language).\n', '* We create a prominent notice that comes up when you load VisualEditor for the first time, explaining that the editor is a beta product, and that editors should be prepared for bugs.\n', '\n', 'Also note that it will, of course, continue to be possible to opt-out of VisualEditor using the existing preference, and users who have already done so will not see VisualEditor re-appear.\n', '\n', 'Do you think this would be an helpful way forward?\n', '\n', 'Yours,\n', '\n', '[[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 01:42, 1 August 2013 (UTC)\n']","01:42, 1 August 2013 (UTC)",Jdforrester (WMF)
+"["":Erik's message on the mailing list didn't address one important issue. You are months away from getting table editing implemented. You are months away from getting cut-and-paste to work. You are months away from acceptable performance. You have a list of several hundred bugs that have been found during this period of forced testing. Why do you need so much more feedback on this version? Why not focus on getting those elements corrected and then trying again when you have a product that there's a good chance that people will like?\n"", "":You've seriously strained our good will. Most of us are still quite willing to give you a second chance, though. I don't think many of us would give you a third, though, so it's important to make good use of your opportunities.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 01:53, 1 August 2013 (UTC)\n""]","01:53, 1 August 2013 (UTC)",Kww
+"['\n', ':: {{ping|Kww}}\n', ':: Hey Kww,\n', "":: That's a totally legitimate question. These are some of the main types of issues we're dealing with:\n"", '::* Category A: straightforward bugs, \'\'e.g.\'\' ""When I click this button in the dialog, it stops responding"".\n', '::* Category B: performance issues, \'\'e.g.\'\' ""It takes 25 seconds to save the page"".\n', '::* Category C: user experience issues, \'\'e.g.\'\' ""The reference dialog is not intuitive for me"".\n', '::* Category D: missing functionality, \'\'e.g.\'\' ""I can\'t insert or edit maths equations"".\n', "";: Our ability to address issues in ''each'' category is greatly enhanced by a significantly sized pool of users making real world edits using VisualEditor, and greatly decreased by seeing that set of users drop to a trickle, or a highly self-selective pool.\n"", "":: However, as I noted, you are correct that we don't require the firehose of usage that we're seeing today. That firehose has the benefit that it's truly unbiased -- IPs, new users, and long-time Wikipedians have all used VisualEditor in the last few weeks. But we understand that this is disruptive, and costing us goodwill. Sorry. :-( However, a compromise like the one we're suggesting above would help maintain a reasonable level of usage, while more fully informing users that they're participating in a beta test, and not changing the default experience for anyone.\n"", "";: Let me try to explain why each category of issue benefits from a large ''and'' diverse pool of users making real world edits.\n"", ""::;Category A issues: Bugs of this type often depend on VisualEditor being in a certain state (''e.g.'' a certain element on the page being selected), or only occur sporadically, or for users with certain configurations. We may be able to isolate and think we've fixed the bug under testing conditions, but it continues to occur in real-world conditions. Were we to go to 0 users and do all our testing internally, we'd do months of development and fix a lot of these issues, release again and have to re-open many of the bugs, because it turns out that users still encounter them under certain conditions. Users yell at us because the software still has bugs. That's fairly likely, and doesn't serve anyone well. \n"", ""::: In order to catch issues and regressions while we're developing code, we use unit tests, automated browser tests, and automated parser round-tripping tests. We have a continuous integration pipeline that lets us know when a commit breaks a given test. All aspects of the testing pipeline can be improved, of course, but even with a solid testing pipeline, you'll run up against the limitations of automated testing. In particular, maintaining more than a basic set of cross-browser tests requires very large development effort in its own right, because browser automation tends to be brittle as the user interface changes.\n"", ""::: Manual testing (literally paying people to follow test plans, perform exploratory testing, ''etc.'') also only gets us so far. If you've done Web development, you will know, for example, that the number of browser variants to support is ever-increasing, with browser makers shifting to very short release cycles, and each release exhibiting slightly different characteristics. As you go down in versions one-by-one from Firefox 22, you might literally see the same bug manifest in a dozen different ways.\n"", ""::: So, in order to really track an issue under real-world conditions and ensure that it's actually fixed, and in order to be complement our own testing efforts with the radically heterogeneous environments of our users, it is helpful to have a continued high level of real-world usage as development continues.\n"", ""::; Category B issues: Performance may seem like the most straightforward thing to optimise without having a significantly-sized user base, but it's actually not. The reason is that such issues often require highly-unusual optimisation strategies. The largest area for performance improvements isn't in the server-side code, but in the client-side code that manipulates the document object model. We're highly likely to encounter new issues ''as'' we optimise performance, and we do need new reports as we iterate, rather than by the time we reach a final state.\n"", '::; Category C and D issues: Essentially, any time we make a change to the user experience, we need to see whether it works. Not just ""works for us at WMF"", or even ""works for our projection of what real-world users would expect"", but actually works. The diffs of real users making edits using VisualEditor are essential for this. Does the number of references being added go up? Does the number of unintended <code><nowiki><nowiki></nowiki></code>s go down? Are users successfully using the table editor? Once again, doing this in a ""waterfall"" model where we come to you in 6 months with a shiny table editor is the best way to ensure that you \'\'won\'t\'\' be satisfied with the changes we make, and that we won\'t either. Aiming, always, for the [[minimum viable product]] helps us iterate under real world conditions.\n', "":: In sum, once again, while I completely understand the frustration with the opt-out beta period, we do need to build an unbiased, reasonably representative set of VE users in order to effectively support addressing any kind of issue you encounter, rather than quietly slaving away for a long time and then releasing a product that doesn't meet user needs and has lots of new and old bugs that only surface in real-world conditions.\n"", "":: Hope that's reasonable. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 03:17, 1 August 2013 (UTC)\n""]","03:17, 1 August 2013 (UTC)",Jdforrester (WMF)
+"[':::James, I think you that you are underestimating the  problem you are going to get into with regression against stable releases, and also against the problem of defining minimum feature sets. The biggest problem you face is that you are a \'\'long\'\' way from the minimum feature set, which includes full table editing capability, cutting-and-pasting both inside one VE window and between VE windows, good solid reference/citation wizards, and probably a retool of how Parsoid and VE deal with templates that don\'t meet your current definitions of being well-behaved. That combination of features is \'\'substantial\'\', and runs the risk of having functional regressions while you try to move forward. If you attempt to address that with the multiple release/week cycle you are going to have to go through, you are going to have a horrible time pinning down when and where fixing one bug caused you to regress on another. There\'s a time and a place for Agile-style methodologies and a time and a place for things closer to a waterfall methodology. Competing with a fully functional editor is one of those places where Agile methodologies have difficulties. The problem here is that you aren\'t really fixing a \'\'problem\'\': there\'s nothing about VE that makes the average Wikipedia user \'\'need\'\' to use it, and because we don\'t need it, we are pretty intolerant of bugs and poor performance. The whole ""develop part, see how it flies, develop some more, see how it flies"" stuff doesn\'t work so well when the user can just go next door and use a complete solution.\n', "":::Another key thing to note is that the changes you are discussing only apply to people that choose to turn this ''on''. Note that consensus so far in this RFC is ''strong'': not only are you expected to turn this off for new users, you are expected to go through and disable VE for ''everyone''. ''Everyone''. After doing that, only people that think you have something worth using and testing will turn it on. It's your obligation to have something worth using and testing, not our obligation to test and use software that doesn't give us benefits. That's where the decision you made to make something the default editor when it fell so short of the minimum expected feature set is going to hurt you, and I can't deny it will be painful. It's pain you brought on yourself, however, by ignoring everyone when we kept begging you to slow down.\n"", ':::You have developed a fan-base though: people that saw VE and think it\'s worthwhile. Hell, \'\'I\'\' think it\'s probably worthwhile. People are still willing to help test if you ask nicely. Maybe not as fast and furious as this, but I would happily run template, citation, and table editors through their paces and let you know how they went. Other people have fetishes about typography management, and you haven\'t even begun to address their needs (if you can call anything that involves counting the pixels in the width of a horizontal line a ""need""). There\'s a substantial group of people that pretty much fix typos and formatting that seem happy with VE as it stands and will give it a constant basic functionality check.\n', "":::What you need to understand and internalize is that Wikipedia itself is amazing: a distributed, collaborative work with an enormous pool of collaborators that actually maintains a fairly cohesive style and voice despite the fact that most of us have never met. The tools we have built up for using the existing software have helped us accomplish that, and we need to see how new tools are going to enter into our workflow before they will be embraced. Right now, the released Visual Editor basically supports a substandard junior class of editor that will never be able to compete with people using the older tools. That's not good for the junior editor, not good for the older editors, and doesn't reflect well on the tool the junior editor is using.\n"", "":::No one is asking you to go completely away. What we ''are'' asking is for you to not be quite so much in our face. Not to belittle the tools we use, disparage our opinions, and try to [https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=prev&oldid=563853529 pin the blame for UI deficiencies on editors]. To recognize that VE is not ''better'' than our existing tool-chain, it just appeals to a different class of user. You've got a lot of expertise to draw on here. You've got free access to the opinions of software designers ranging from self-taught script kiddies to old guys like me (over 30 years of software engineering, including software developments where we wrote 2 million lines of code by ourselves, compiled them on compilers that we wrote ourselves, ran them on hardware platforms that we developed ourselves and debugged them with in-circuit emulators that we designed and developed ourselves). It would be a lot better if we all felt like you listened to us.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 05:06, 1 August 2013 (UTC)\n""]","05:06, 1 August 2013 (UTC)",Kww
+"['*Why must we mince words here?  The thing sucks.  It doesn\'t work, it isn\'t likely to work anytime soon, and the satisfaction rate with it is near zero.  If it were a commercial product it would have been recalled by now and it\'s only developer pride and the fact that plenty of time has been wasted on it already that keeps it out of the wikidustbin completely.  So why not make it a purely optional opt-in feature for the masochists who like to beta test stuff and let everyone else move on?  It\'s painfully clear to everyone without a (WMF) behind their name that this \'feature\' is nowhere remotely ready for prime time on one of the world\'s largest websites. [[User:Starblind|Andrew Lenahan]] - <b><span style=""color:#FF0000;"">St</span><span style=""color:#FF5500;"">ar</span><span style=""color:#FF8000;"">bli</span><span style=""color:#FFC000;"">nd</span></b> 02:51, 1 August 2013 (UTC)\n']","02:51, 1 August 2013 (UTC)",Starblind
+"['** Of course it works. Several hundred (if not several thousand) of good edits are being made with it every day. :-)<p>Does it have bugs? Of course. It\'s beta software. (And, by the way, there are thousands of bugs in [[MediaWiki]] as well.)<p>Nobody is asking you to mince words, but I will ask you to assume a little good faith. I don\'t have a ""(WMF)"" in my username and likely never will, but I believe that VisualEditor is the future. I also advocated \'\'quite strongly\'\' for there to be an opt-out feature (that was successfully re-added) and I continue to advocate for making opt-out even easier (namely by removing the need to even visit [[Special:Preferences]] to opt out). I think we should focus on making [[Wikipedia:VisualEditor/Improvements|improvements]] to VisualEditor rather than simply re-stating how much it currently sucks. --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 03:01, 1 August 2013 (UTC)\n']","03:01, 1 August 2013 (UTC)",MZMcBride
+"['***Part of the problem with the \'let\'s just fix it\' option is that it\'s totally open-ended.  How long are we expected to tolerate during its supposed tweaking period it before it\'s considered a failed experiment?  6 more months?  A year?  Keeping in mind this is taking our donation money every second it exists.  I say the numbers speak for themselves.  If you worked at a soda company, you couldn\'t keep telling the boss, ""I swear Turd Cola will be ready to market any day now!  I just have to get the ratio of urea and bile just right!  The last taste test only 94% hated it!""  Sooner or later you just have to realise that you\'ve cooked up a turd. [[User:Starblind|Andrew Lenahan]] - <b><span style=""color:#FF0000;"">St</span><span style=""color:#FF5500;"">ar</span><span style=""color:#FF8000;"">bli</span><span style=""color:#FFC000;"">nd</span></b> 03:36, 1 August 2013 (UTC)\n']","03:36, 1 August 2013 (UTC)",Starblind
+"[""**** Hi [[User:Starblind|Starblind]]. As you may or may not be aware, each edit made with [[Wikipedia:VisualEditor|VisualEditor]] (VE) is tagged. For example, {{VE edits|MZMcBride|here}} is one of my edits made with VisualEditor. According to this same search, you currently have 0 {{VE edits|Starblind}}. So what, exactly, are you complaining about? Or more pointedly, who, exactly, are you complaining for? You may think VisualEditor is a complete piece of shit and you're certainly entitled to that opinion. But you seem to have no issue editing the wiki with the source editor and you seem to have no issue avoiding the use of VisualEditor. Can you please elaborate? --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 07:31, 1 August 2013 (UTC)\n""]","07:31, 1 August 2013 (UTC)",MZMcBride
+"[""***** Hi, you have to acknowledge that the reason that a lot of users who want to have VE going back to opt-in mode is not that they don't want to use VE (they can choose to disable it since we now have this option), but is because they are tired of seeing articles being damaged by edits made with VE (nowiki added, problems with tables, ...), damages that will have to be fixed mostly by other people than the one that are creating them with VE. About the number of bugs: you don't run easily on the thousands of MediaWiki bugs and they don't seem to damage articles, but with VE it's a different story. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 09:39, 1 August 2013 (UTC)\n""]","09:39, 1 August 2013 (UTC)",NicoV
+"["": It's difficult to disagree with the changes you're proposing, particularly as they echo [https://en.wikipedia.org/w/index.php?title=User_talk:MZMcBride&diff=prev&oldid=566623737&diffonly=1 similar thoughts] that I posted earlier today. ;-)  I have some minor quibbles (e.g., I think the beta notice should be dismissable, rather than only loaded for the first time based on a cookie), but otherwise these are all sound suggestions that I hope can be implemented as soon as possible.\n"", "": While I think everyone leading this [[WP:RFC|RFC]] (and participating in it) is acting in good faith, I think it's important to recognize (as both you, James, and Erik do) that a few vocal power-users on the English Wikipedia cannot speak for everyone. Some good ideas have been brought forward in this RFC and I'm hoping [[Wikipedia:VisualEditor/Improvements|further good ideas]] are on the way from the very bright and dedicated group of power-users who contribute so much to Wikimedia wikis. However, VisualEditor is a shared endeavor that I hope we all want to see done right.\n"", "": Again, I think your proposed changes should be of the highest priority, as I think they will be a sign of good faith and good will toward the community and will assuage a lot of the concerns we've been seeing with VisualEditor's deployment. --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 02:56, 1 August 2013 (UTC)\n""]","02:56, 1 August 2013 (UTC)",MZMcBride
+"["":I agree with [[User:Jdforrester (WMF)|Jdforrester]]'s suggestions, and think they are the best solution to this issue. I'd also like to note that the visual editor isn't as bad as people make it seem and that it is very useful. A part of the aversion to the visual editor is because it has many bugs and is slow, but a big part is just general change aversion. I like the visual editor: it makes many tasks, such as inserting references, easier (if we exclude the few bugs that prevent some actions). It's great how I can simply click on a reference button and then transclude a template and just fill the parameters without having to keep constantly switching from the editing tab to the tab with the template documentation of the citation template, and have all the parameters and their descriptions right in the editor. There are many things that are good about the visual editor. I don't think it'd be a good idea to remove the visual editor from anywhere, whatever the reason. Nobody is forced to use the visual editor, and if it was made less prominent, then there would be no problem anymore. It doesn't need to be removed, hidden or made opt-in only. -- [[User:Rastus Vernon|Rastus Vernon]] ([[User talk:Rastus Vernon|talk]]) 02:59, 1 August 2013 (UTC)\n""]","02:59, 1 August 2013 (UTC)",Rastus Vernon
+"['::While you\'re entitled to your opinions, consensus is very much against that view, with the current tally being 191 opt-in to 15 opt-out, much worse than 10 to 1.  And the response from the German wikipedia was even more decisive.  The community has spoken, will the developers choose to listen this time? [[User:Starblind|Andrew Lenahan]] - <b><span style=""color:#FF0000;"">St</span><span style=""color:#FF5500;"">ar</span><span style=""color:#FF8000;"">bli</span><span style=""color:#FFC000;"">nd</span></b> 03:16, 1 August 2013 (UTC)\n']","03:16, 1 August 2013 (UTC)",Starblind
+"[':As long as the visualeditor tab is labelled as ""Visual Editor - BETA"" I will be more than willing to accept these changes. [[User:PantherLeapord|PantherLeapord]]&#124;[[User talk:PantherLeapord|My talk page]]&#124;[[User:PantherLeapord/CSD log|My CSD log]] 04:30, 1 August 2013 (UTC)\n']","04:30, 1 August 2013 (UTC)",PantherLeapord
+"["":Should we move Jdforrester's suggestions to the main page to look for acceptance of the community? -- [[User:Sameboat|Sameboat - 同舟]] ([[User talk:Sameboat|talk]]) 04:43, 1 August 2013 (UTC)\n""]","04:43, 1 August 2013 (UTC)",Sameboat
+"['\n', "":''We cannot develop VisualEditor in isolation from real users'': well, for the moment, it seems quite the contrary.\n"", "":1) Every major features of VE seems to have been developed in isolation from real users: why didn't you start focused discussions with users for major features rather than deploying features that were totally useless at first (reference editing, ...) ? You could still start those focused discussions but you don't\n"", "":2) You don't take into account the more important issues for many users: hundreds of articles are currently being damaged every day when edited with VE. And your answer to the main problem is WONT FIX. Usually on every wiki, a tool that is causing damages is simply blocked until fixed, but you're WMF so you consider yourself are above this.\n"", "":Erik's mail is also based on the assumption that the opt-in alpha period wasn't sufficient, but he conveniently forget to say that you couldn't do anything useful with VE during the alpha (no template editing, no reference editing, ...) so users ended up either not being able to make their edit. There's never been a true opt-in alpha period.\n"", ':--[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 04:44, 1 August 2013 (UTC)\n']","04:44, 1 August 2013 (UTC)",NicoV
+"['::Otherwise, concerning your proposals: ok for 1, 2 (rather ""Edit"" to have the same on every namespace and something like ""Visual Editor (experimental)"" experimental being easier to understand than beta), 3. For proposal 4, I think its\' not enough: it should be dismissed by choice, not only displayed the first time; and the message should be explicit on how to disable it, that edits should be checked by the editor because bugs are expected and that the editor has many limitations. Otherwise, I still believe that VE should go back to opt-in to decrease the number of damages to articles until these problems are fixed. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 09:33, 1 August 2013 (UTC)\n']","09:33, 1 August 2013 (UTC)",NicoV
+"[""*{{ec}}I agree with James' suggestions. As someone who is spending a lot of time working with VE and the bugs it is causing, I see that VE has a great future. What it needs though is for people to realise that it isn't ready yet, but that the only way for it to ever be ready is by lots of real world testing. There are some bugs that require very specific combinations of elements in order to happen, for example {{phab|53893}} and {{phab|54341}}, that they just wont be found by testing in a controlled environment. That doesn't mean it has to be the default editor, and I've stated elsewhere that it shouldn't be, but it needs to be easily accessible for people who want to test it. If you just want to make a simple spelling correction, then VE is already up to the task so we shouldn't force someone uncomfortable with wikitext into the source editor. Equally, there should be a way for people who don't want anything to do with VE to be able to opt out completely - but the vocal minority of such users should not prevent those who want to use VE from doing so. Clearly marking VE as beta and making the source editor default should reduce the volume of the problems. Going forward there should always (even after the end of beta) be an equal choice between editors - neutrality is a founding principle and we should reflect that. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 09:44, 1 August 2013 (UTC)\n""]","09:44, 1 August 2013 (UTC)",Thryduulf
+"['\n', '* Yes, James\'s proposals seem a useful way forward. I\'ll probably continue to try to use VE for my editing, hoping to have a decreasing need for ""VE cleanup"" Edit Source edits as time progresses. But my motivation for editing is to enjoy myself, to contribute generally to the encyclopedia and improve it, to be useful: I can tolerate some misbehaviour from VE and quite enjoy making careful bug reports on [[WP:VEF|the feedback page]]. I can see it\'s all very different for someone with a mission to improve the coverage of Field XXX in Wikipedia, or to get a Featured Article on Topic YYY, especially if they\'re time-poor, or for someone coming new to editing who doesn\'t know what the hell is going on when ""edit"" leads them to totally different interfaces according to whether they\'re in article space or on a talk page etc. [[User:PamD|<span style=""color:green;"">\'\'\'\'\'Pam\'\'\'\'\'</span>]][[User talk:PamD|<span style=""color:brown;"">\'\'\'\'\'D\'\'\'\'\'</span>]] 11:12, 1 August 2013 (UTC)\n']","11:12, 1 August 2013 (UTC)",PamD
+"[""* Without specifically commenting on James's proposal, I would add to PamD's comments above: I am an example of someone working on a topic I'd like to get to featured article status; I'm using VE as much as I can, and am fine with the current level of functionality.  Of course I'd like to see it improve, and I'm sure it will.  I'd like to thank the development team for getting this far, and encourage them to keep the visibility and usage of VE high, along with the ability to opt out, of course. We need this tool for the future and we need high-volume usage now to help us get there.  If the budget for the dev team were as large as you might get with a Google or Apple team, then sure, I'd expect VE to be a bit cleaner and more comprehensive by now, but we don't have those resources and should not expect outcomes that require those resources.  I have no complaints about the rollout so far. [[User:Mike Christie|Mike Christie]] ([[User_talk:Mike Christie|talk]] - [[Special:Contributions/Mike_Christie|contribs]] -  [[User:Mike Christie/Reference library|library]]) 11:22, 1 August 2013 (UTC)\n""]","11:22, 1 August 2013 (UTC)",Mike Christie
+"['* Support all four changes suggested by jdforrester. In addition I hope referencing improvements (mainly citation templates & autofill) can be prioritized, as that is the main thing for me personally right now keeping me from doing basically all simple text edits with the VE.--[[User:Wouterstomp|WS]] ([[User talk:Wouterstomp|talk]]) 14:11, 1 August 2013 (UTC)\n']","14:11, 1 August 2013 (UTC)",Wouterstomp
+"[""* Support for this. It makes sense, and also provides an example to use for other changes in the interface. '''[[User:DGG| DGG]]''' ([[User talk:DGG| talk ]]) 18:40, 1 August 2013 (UTC)\n""]","18:40, 1 August 2013 (UTC)",DGG
+"['* Yes, really good suggestions. (I liked the animation. I think moving the [edit] links to the right and keeping the animations will be better than having non animated edit links along with the section headings. The animation draws the eyes, making them more prominent but with less disturbance/distraction. What do you think?<!---Thanks to OKeyes for the notification---><span style=""text-shadow:gray 0.2em 0.3em 0.2em"">···[[User:Vanischenu|\'\'\'V<span style=""color:green;"">ani</span>s<span style=""color:green;"">che</span>nu\'\'\']][[Special:Contributions/Vanischenu|<sup>「m</sup>]]/[[User_talk:Vanischenu|<sub>Talk」</sub>]]</span> 19:14, 1 August 2013 (UTC)\n']","19:14, 1 August 2013 (UTC)",Vanischenu
+"['*A little discussion on the talk page of an RFC cannot be used to subvert the RFC itself. These are all fine suggestions so long as the obvious result of the RFC (that VE is disabled for all accounts, old and new, until the editor specifically enables it) is done first.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 19:18, 1 August 2013 (UTC)\n']","19:18, 1 August 2013 (UTC)",Kww
+"['*First off, I expect the WMF to abide by the results of this RFC, just as they did the one on the German Wikipedia. Our reasons are just as good as theirs are, and we have already assumed a huge amount of good faith here. I think the proposal at the start of this section is appropriate for now, but we need to have some discussion separate to this RFC for the WMF and the English Wikipedia community to jointly determine appropriate methods for introducing software, and the discussion should include how to ramp up the visibility of VisualEditor. [[User:Risker|Risker]] ([[User talk:Risker|talk]]) 19:23, 1 August 2013 (UTC)\n']","19:23, 1 August 2013 (UTC)",Risker
+"['*I think that we should adopt the four proposals as laid out by jdforrester, and see what happens. If those don\'t suffice, then we should push for opt-in only. The advantage of doing it as he suggests is that this \'\'\'gives new editors a choice\'\'\'. Even if they decide that VE isn\'t for them, they\'ll see its possibilities, and the ""beta"" label on it will tell them that it \'\'\'will\'\'\' get better. If we go to opt-in only, virtually no new editors are going to be aware of the \'\'promise\'\' of VE, let alone try it out - because new editors don\'t go systematically though their preferences (lots of preferences) to decide what to turn on and off. -- <span style=""font-family:Monotype Corsiva; font-size:15px;"">[[User:John Broughton|John Broughton]] </span>  [[User talk:John Broughton |(♫♫)]] 23:27, 1 August 2013 (UTC)\n']","23:27, 1 August 2013 (UTC)",John Broughton
+"["":*How often do you think a small group of editors should try to override an RFC on the RFC's talk page, [[User:John Broughton|John]]? Is this some kind of new RFC procedure that I've never heard of before?&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 00:37, 2 August 2013 (UTC)\n""]","00:37, 2 August 2013 (UTC)",Kww
+"['::*{{Replyto|Kww}} I\'m unaware of any Wikipedia rule that says that when a topic is being discussed at an RfC, \'\'it cannot be discussed anywhere else but the main RfC page\'\'. If there is such a rule, I\'d appreciate your pointing it out, and then I\'ll certainly not violate it again.  -- <span style=""font-family:Monotype Corsiva; font-size:15px;"">[[User:John Broughton|John Broughton]] </span>  [[User talk:John Broughton |(♫♫)]] 01:28, 2 August 2013 (UTC)\n']","01:28, 2 August 2013 (UTC)",John Broughton
+"["":::*It's a matter of intent, [[User:John Broughton|John]]. I read your comment as indicating that if the RFC closes with a recommendation to opt-in, you believe we should ignore the result and continue with opt-out. That's not a matter of discussion in multiple places, that's a matter of advocating that we disregard community consensus. Did I misread you?&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 01:32, 2 August 2013 (UTC)\n""]","01:32, 2 August 2013 (UTC)",Kww
+"['*Strongly agree with all 4 suggestions. For labels, I\'d suggest ""Edit wikitext"" and ""VisualEditor <sup>beta</sup>"".  I agree that making it opt-in at this point would be problematic, as at least some (IP/New/Old) editors do prefer using it, and might not understand how to find it again. Also, per Wouterstomp, please prioritize improving the referencing tools - [[WP:Reftoolbar]] should be the guide. –[[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 00:33, 2 August 2013 (UTC)\n']","00:33, 2 August 2013 (UTC)",Quiddity
+"['\n', ""{{Done}} {{ping|Kww|MZMcBride|Starblind|NicoV|Rastus Vernon}}, {{ping|PantherLeapord|Sameboat|Thryduulf|PamD|Mike Christie}}, {{ping|Wouterstomp|Vanischenu|Risker|John Broughton|Quiddity}} As an update, this is now - I've posted an explanation for the decisions I've made and the reasons we've done it like this at [[Wikipedia:VisualEditor/August 2013 update]].  [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 05:27, 2 August 2013 (UTC)\n""]","05:27, 2 August 2013 (UTC)",Jdforrester (WMF)
+"[':\'tis appreciated. (Note, I\'ve changed your link from ""here"" to the actual pagename, per [[click here]] being [[considered harmful]] ;) –[[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 05:32, 2 August 2013 (UTC)\n']","05:32, 2 August 2013 (UTC)",Quiddity
+"[':I find that using ""Edit source"" and ""Edit beta"" is a bad idea: ""source"" or ""beta"" don\'t mean much for a basic user. At least as long as VE is alpha/beta, we should keep the default ""Edit"" for the classic wikitext editor. For VE, I think ""experimental"" (or other true english word) is more obvious than ""beta"" for non tech people. On Preferences, we already have ""(experimental)"" used for Live preview. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 06:49, 2 August 2013 (UTC)\n']","06:49, 2 August 2013 (UTC)",NicoV
+"['\n', ':: We need to keep in mind what the interface will look like at the end of the beta, so we don\'t heighten the confusion at that point. With the current setup, it\'s simply a matter of taking off the ""beta"" label (short of a drastic refactoring of the edit UI altogether), without additional confusion. It\'ll take some time to adjust to this change for sure (as it does to any change), but at least we can keep it in place and let folks develop muscle memory with the new system which they get to retain.\n', '\n', ':: As for ""edit source"", I think the devs chose ""Edit source"" in the first place because ""View source"" already appears on semi-protected pages.  So introducing the notion of source-editing into the vernacular does not seem unreasonable to me. It \'\'may\'\' be worth revisiting that at some point -- personally I prefer ""wikitext"" to ""source"" because it sounds more friendly and less programm-y.\n', '\n', ':: As for ""beta"" vs. ""experimental"", it\'s partially a matter of finding something \'\'short\'\' (string length) that has widely understood meaning - keep in mind these strings have to appear both on section edit links and tabs. The meaning of ""beta"" in this context is explained in the message that comes up when you first invoke VE.--[[User:Eloquence|Eloquence]][[User:Eloquence/CP|*]] 07:02, 2 August 2013 (UTC)\n']","07:02, 2 August 2013 (UTC)",Eloquence
+"['\n', ':::I think the changes suggested are a big step in the right direction. I also like ""wikitext"" better than ""source"" as it is likely to be more meaningful to the general public, takes very little extra space, and will not confuse the experienced editors. Experimental is clearer than beta. If space is an issue then beta is OK, \'\'\'\'\'Much\'\'\'\'\' better than nothing. Nothing is \'\'\'\'\'Really Bad™\'\'\'\'\'. Cheers, &bull; &bull; &bull; [[User:Pbsouthwood|Peter (Southwood)]] [[User talk:Pbsouthwood|<sup>(talk)</sup>]]: 09:23, 2 August 2013 (UTC)\n']","09:23, 2 August 2013 (UTC)",Pbsouthwood
+"["":::Opening up the whole article for editing in VE is also an unpleasant surprise ('''''Really Bad™''''') which should be eliminated urgently. When you click on a section edit link you expect to edit a section, not the whole article. Finding the place you wanted to edit is sometimes a non-trivial exercise. If this can't be done for technical reasons, take away the VE link at the section headers and have it only at the top tab. &bull; &bull; &bull; [[User:Pbsouthwood|Peter (Southwood)]] [[User talk:Pbsouthwood|<sup>(talk)</sup>]]: 09:23, 2 August 2013 (UTC)\n""]","09:23, 2 August 2013 (UTC)",Pbsouthwood
+"['==Restore site notice?==\n', '[http://en.wikipedia.org/w/index.php?title=MediaWiki:Sitenotice&diff=prev&oldid=566636834 For a few hours last night], a site notice pointing to this RfC was up. It resulted in about 100 editors expressing an opinion here, in the space of a few hours. The site notice was [http://en.wikipedia.org/w/index.php?title=MediaWiki%3ASitenotice&diff=566665925&oldid=566640843 removed] in the small hours. Could we restore it? No one notices watchlist notices: the site notice was very clearly more effective in bringing eyes to this page. [[User:Jayen466|Andreas]] <small>[[User_Talk:Jayen466|<span style=""color:#FFBF00;"">JN</span>]][[Special:Contributions/Jayen466|466]]</small> 14:30, 1 August 2013 (UTC)\n']","14:30, 1 August 2013 (UTC)",Jayen466
+"[':Discussion here: [[MediaWiki_talk:Sitenotice#Remove_VisualEditor_default_state_RFC_notice]] [[User:Jayen466|Andreas]] <small>[[User_Talk:Jayen466|<span style=""color:#FFBF00;"">JN</span>]][[Special:Contributions/Jayen466|466]]</small> 14:34, 1 August 2013 (UTC)\n']","14:34, 1 August 2013 (UTC)",Jayen466
+"['::I agree it should be put back. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 14:35, 1 August 2013 (UTC)\n']","14:35, 1 August 2013 (UTC)",KumiokoCleanStart
+"[':::Could you please say that over at [[MediaWiki_talk:Sitenotice#Remove_VisualEditor_default_state_RFC_notice]] as well? Thanks. [[User:Jayen466|Andreas]] <small>[[User_Talk:Jayen466|<span style=""color:#FFBF00;"">JN</span>]][[Special:Contributions/Jayen466|466]]</small> 14:39, 1 August 2013 (UTC)\n']","14:39, 1 August 2013 (UTC)",Jayen466
+"[': Well, err, yes: a site-wide notice results in more visitors (and thus editors) to a page. Film at 11. --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 15:03, 1 August 2013 (UTC)\n']","15:03, 1 August 2013 (UTC)",MZMcBride
+"['::MZM, [[WP:CIVIL]] please.  —[[User:Sladen|Sladen]] ([[User talk:Sladen|talk]]) 02:50, 2 August 2013 (UTC)\n']","02:50, 2 August 2013 (UTC)",Sladen
+"[""::: I'm trying my best. --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 03:29, 2 August 2013 (UTC)\n""]","03:29, 2 August 2013 (UTC)",MZMcBride
+"['== Thank you ==\n', '\n', 'Thank you for even more great info. as I have just heard of the Visual Editor.  <small><span class=""autosigned"">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Mikeg0513|Mikeg0513]] ([[User talk:Mikeg0513|talk]] • [[Special:Contributions/Mikeg0513|contribs]]) 17:55, 1 August 2013 (UTC)</span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->\n']","17:55, 1 August 2013 (UTC)",Mikeg0513
+"['== Anonymous editors? ==\n', '\n', 'If I create a username such as ""Mr. Mysteroso123"" or ""anonymousguy111"", or some such, and edit under that, I\'m an ""anonymous editor"" in the sense that no one knows who I am, but is this what is meant? \n', '\n', 'If I edit under my IP address, I\'m anonymous in the sence that I have ""no name"", ""a -nonym -ous"", but then everyone can easily find out where I am and therefore potentially even who I am, so it\'s not really as ""anonymous"" as editing under an assumed name, in the commonly understaood meaning of the word ""anonymous"".  \n', '\n', 'So the term ""anonymous editor"" is ambigous.\n', '\n', 'If you mean ""IP address editors"", why not just say that?  It would be more precise, less ambiguous, and not propagate the myth that editing under your IP address means that no one can know who you are. [[User:Chrisrus|Chrisrus]] ([[User talk:Chrisrus|talk]]) 19:44, 1 August 2013 (UTC)\n']","19:44, 1 August 2013 (UTC)",Chrisrus
+"[':I agree that ""anonymous"" is too ambiguous. But ""IP address editor"" is ambiguous to non-technical people too. It would be best to have a term that non-technical users would understand without further explanation. Even ""log in"" and ""log out"" can be problematic, because they overlap with the idea of ""logs"" and ""logging"". What we mean is ""not-signed-in"" editors. If you have not \'\'\'signed in\'\'\' your edits will be \'\'\'logged\'\'\' against your current IP address, which may allow people to identify your location, etc. When you haven\'t signed in, you should see something like the lower UI:\n', ':[[File:Sign-in status UI suggestion.png|Mock-up of top-right-hand corner of suggested enwiki screen when a user has not signed in]]<br>\n', ':We also need a vocabulary that distinguishes users who do not have accounts from those who \'\'do\'\' have accounts but are not currently signed in. ""Anon"" vs ""registered"" doesn\'t do this. But perhaps that\'s a discussion for another day.... - [[User:Pointillist|Pointillist]] ([[User talk:Pointillist|talk]]) 22:45, 1 August 2013 (UTC)\n']","22:45, 1 August 2013 (UTC)",Pointillist
+"['== This could be a bad idea ==\n', '\n', ""This could be a bad idea in which it will change MediaWiki to a visual editor only mode in the future like some other organizations/companies/whatever does. For example, many people new to MediaWiki could mass demand visual editor only in which all wikis could be forced to visual editor. Source mode is the best to use even for new, anonymous, etc users for they can actually learn something without it being handed to them like hey all I have to do is click this and that, an example of not learning could be Wikia(No offense wikia)--[[User:Micronationalist1999|Micronationalist1999]] ([[User talk:Micronationalist1999|talk]]) '''YOUR PROUD BANANA''' 22:24, 1 August 2013 (UTC)\n""]","22:24, 1 August 2013 (UTC)",Micronationalist1999
+"[':Thanks for your input! Please make sure you give your thoughts on the actual RFC page rather than this talk page where it could be overlooked. [[User:Killiondude|Killiondude]] ([[User talk:Killiondude|talk]]) 06:54, 2 August 2013 (UTC)\n']","06:54, 2 August 2013 (UTC)",Killiondude
+"['::The purpose of Wikipedia is not to learn wikitext markup. It is to create and use an encyclopaedia that anyone can edit. Wikitext is a barrier to a large number of people who could provide a lot of valuable content. &bull; &bull; &bull; [[User:Pbsouthwood|Peter (Southwood)]] [[User talk:Pbsouthwood|<sup>(talk)</sup>]]: 09:40, 2 August 2013 (UTC)\n']","09:40, 2 August 2013 (UTC)",Pbsouthwood
+"[':::[citation needed].  There\'s no evidence that wikitext specifically is a significant barrier to entry or that it has anything to do with the wiki\'s editor retention stats, nor that a visual editor will provide even the slightest help with that; without that evidence, all of this development time and serious disruption to the wiki is being made over what amounts to a glorified hunch.  (While it is too early to tell, of course, how things will be when all the bugs are worked out, what evidence we do have suggests that the visual editor has, so far, been actively harmful.)  The visual editor itself is going to require time to learn and use, and there\'s no reason to think that the time required to learn how to do ""simple"" edits via the editor is any less than with wikitext; there\'s also plenty of reasons to suspect that wikitext makes it much easier for new users to pick up day-to-day \'mid-level\' skills for whatever area they want to focus on (since they can see how something was done by viewing the text, whereas a visual editor doesn\'t tell you what of its numerous confusing buttons to push to replicate something you saw elsewhere.) Additionally, while it\'s certainly true that the purpose of Wikipedia is not to learn wikitext, it is unfortunately inescapable that the wiki is constructed entirely out of it; no editor is ever going to be able to provide full control over wikitext without becoming hopelessly complex in the process.  That means that creating an alternative ""learning path"" where people spend their time learning how to use a complicated visual editor is only setting them up for eventual frustration when they learn that the complicated visual editor they\'ve been wasting their time learning is still useless for many tasks -- even learning every single one of its dozens of unintuitive buttons still doesn\'t let you do everything you will need, and actively replaces the learning that would have helped them contribute more broadly. --[[User:Aquillion|Aquillion]] ([[User talk:Aquillion|talk]]) 22:30, 2 August 2013 (UTC)\n']","22:30, 2 August 2013 (UTC)",Aquillion
+"[""::::I believe that you will find links to the evidence that you seek at [[Wikipedia:VisualEditor/Why]].  If you'd prefer anecdotal evidence to systematically gathered quantitative data, I've personally had people tell me that they do not edit Wikipedia because the markup is too confusing.  Most recently, I spoke with someone in June who said that he had tried to fix an error in a page, and that he simply closed the window after seeing how complicated the code was. \n"", '::::The complexity varies a lot by page.  There are some that I think most people could figure out in a minute or so.  There are others, like the huge template-constructed tables of television episodes or election results, that [http://tools.wmflabs.org/xtools/pcount/index.php?name=WhatamIdoing&lang=en&wiki=wikipedia even I] find complicated.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 22:07, 3 August 2013 (UTC)\n']","22:07, 3 August 2013 (UTC)",Whatamidoing (WMF)
+"["":::::No, there's no evidence at [[Wikipedia:VisualEditor/Why]]; all it has is a graph showing that 1-year retention has been declining over time after an initial spike when Wikipedia first appeared (and even then, the graph is from ''2009'', over four years ago -- even if it showed what you claim, which it does not, it would be ridiculous to use it as a justification for anything.)  It links to the A/B test, which shows that the ''visual editor'' has driven people away, but nothing in there concretely connects the problem to wikitext.  Either way, that graph says nothing about ''why'' it was declining back in 2009; I think a very reasonable assumption is that Wikipedia (when it first exploded into the popular consciousness) spread rapidly to everyone who was interested in using an encyclopedia and who was currently using the internet, then increasingly gradually once those people were recruited.  Wikipedia's graph of usage also mirrors the problems with retaining users seen by many other major sites with unrelated purposes, like Amazon and Yahoo; the early internet was a fundamentally different place, and usage trends have changed in a way that makes it harder to recruit people.  All of this is at least partially speculative, of course, but it's no less speculative than the random and arbitrary speculation that Wikipedia's shift in usage was because of wikitext, or the entirely unproven and speculative assertion that a WYSIWYG editor is easier to use.  I don't find your speculation or your anecdotal evidence to be convincing at all -- surely many users are now going to be scared off by the clunky and excessively-complex appearance of the bloated visual editor, while previously, many ''parts'' of Wikipedia had very simple layout and did not require knowledge of wikitext at all.  (And, of course, the most complicated parts of the wiki -- the most intimidating ones -- are ''entirely impossible'' to edit with the visual editor by any means.) --[[User:Aquillion|Aquillion]] ([[User talk:Aquillion|talk]]) 01:20, 4 August 2013 (UTC)\n""]","01:20, 4 August 2013 (UTC)",Aquillion
+"['::::::Again:  I believe that you will find \'\'\'links to\'\'\' the evidence that you seek at [[Wikipedia:VisualEditor/Why]].  Not ""directly on the page"", but ""links to"".  Please read the subpage [[Wikipedia:VisualEditor/Why/User Test Data]].  You will also want to look for information on the 2010 Usability Initiative, which interviewed former editors about why they quit editing.  A substantial minority said that they quit because wikicode was getting too complicated.  Another substantial minority said unpleasant encounters with community members was the primary reason they quit.  Another large fraction gave changing life circumstances (like acquiring full-time work) as their reason for quitting.  But the fact remains that some actual, real former editors said that wikicode was too complicated for them.  \n', ""::::::It would be interesting, of course, to correlate those complaints about excessive complexity with the rise of infoboxes and citation templates (the two things people most frequently identify as being frighteningly complicated to look at in wikicode), but I don't believe that anyone has attempted that.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 21:24, 4 August 2013 (UTC)\n""]","21:24, 4 August 2013 (UTC)",Whatamidoing (WMF)
+"['== Super simple intro ==\n', '\n', 'I just now put in a few extremely simple sentences as a brief intro explaining what VE is for people who have no technical understanding and very little experience with editing the encyclopedia. [[User:Invertzoo|Invertzoo]] ([[User talk:Invertzoo|talk]]) 22:45, 1 August 2013 (UTC)\n']","22:45, 1 August 2013 (UTC)",Invertzoo
+"['\n', ""::In which they need to L.E.A.R.N the technical understaning and get experience with the help page and some tutorials by using their brains instead of having something handed to them.--[[User:Micronationalist1999|Micronationalist1999]] ([[User talk:Micronationalist1999|talk]]) '''YOUR PROUD BANANA''' 23:35, 1 August 2013 (UTC)\n""]","23:35, 1 August 2013 (UTC)",Micronationalist1999
+"['== Confusing Source Code ==\n', '\n', 'This should be enabled because to most new users, as I once was, the source coding can be very confusing.  Now, it is for this reason VE should be enabled for new/anonymous users because a user may want to fix what seems like a simple typo, and he or she goes to fix it, and unknowingly contributes to a larger problem.<br>[[User:Benhen1997|Ben]] ([[User talk:Benhen1997|talk]]) 23:58, 1 August 2013 (UTC)\n']","23:58, 1 August 2013 (UTC)",Benhen1997
+"["":Thanks for your opinion! If you haven't already, please make sure you add your thoughts to the actual RFC rather than this talk page. [[User:Killiondude|Killiondude]] ([[User talk:Killiondude|talk]]) 06:53, 2 August 2013 (UTC)\n""]","06:53, 2 August 2013 (UTC)",Killiondude
+"['== PLEASE CLARIFY WHERE DISCUSSION SHOULD BE TAKING PLACE ==\n', '\n', ""Many people are contributing to this discussion yet it is currently being 'discussed' on the Project page AND the Talk page. Which page should this discussion be taking place on & should all comments be moved across to the correct page? --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 06:10, 2 August 2013 (UTC)\n""]","06:10, 2 August 2013 (UTC)",Iryna Harpy
+"[':I think it depends what you want to discuss. This page has many subsections discussing different things. The project page ([[WT:VE]]) is more of a meta-page that is about a variety of things including text on the actual project page, a corresponding wikiproject, and some bugs that should probably have been reported on [[WP:VE/F]]. Things like this that have site-wide and long-lasting implications tend to have discussions that spill over everywhere. Just find where your 2 cents fit best. :-) [[User:Killiondude|Killiondude]] ([[User talk:Killiondude|talk]]) 06:52, 2 August 2013 (UTC)\n']","06:52, 2 August 2013 (UTC)",Killiondude
+"[""::Fair enough. I've already inserted nearly a buck's worth on the project page. No doubt, someone will start up an offshoot talk page on some point of order & I'll be able to continue my squawking there. Cheers for the response! --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 07:11, 2 August 2013 (UTC)\n""]","07:11, 2 August 2013 (UTC)",Iryna Harpy
+"['== Category D issues ==\n', '\n', 'Jdforrester gave an interesting categorisation of ""issues"" and the need for extensive user testing in the various categories.  The fourth and last was \'\'Category D: missing functionality, e.g. ""I can\'t insert or edit maths equations""\'\' and it seems implausible that any sort of testing can help with a functionality that isn\'t even there.  Where users could perhaps help is in the \'\'design\'\' stage.  In the area of mathematics, which is explicitly an example of a missing functionality, and which happens to be the area I edit in, there is a considerable amount of expertise and experience in the community about user interfaces for editing mathematics.  Perhaps WMF developers should be engaging specialised communities such as this at an early stage?  A notice at [[Wikipedia talk:WikiProject Mathematics]] asking for contributions to the design of the user interface would be much appreciated and probably quite helpful.  There\'s a [[Wikipedia talk:WikiProject Mathematics#Latex-to-HTML and HTML-to-Latex users|discussion]] there right now illustrating the degree of experience and range of opinions in that community on the subject of displaying mathematics.  I do hope developers have not underestimated the extreme difficulty of designing a viable point-and-click interface for mathematics — in fact I would go so far as to say that in my opinion \'\'nobody\'\' has ever succeeded in producing any kind of interface which can match the productivity of [[TeX]]-based markup.  [[User:Spectral sequence|Spectral sequence]] ([[User talk:Spectral sequence|talk]]) 18:19, 2 August 2013 (UTC)\n']","18:19, 2 August 2013 (UTC)",Spectral sequence
+"[':I believe that several people have already provided their opinions about TeX and related options, but more are always welcome.  \n', ':There are several obvious missing functionalities, but some are far from obvious, usually because they are only used on a tiny number of pages.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 20:41, 2 August 2013 (UTC)\n']","20:41, 2 August 2013 (UTC)",Whatamidoing (WMF)
+"[""::Thanks for that — glad to hear you have already started to engage.  Could I ask how and where you wish to engage with the existing community of mathematics editors?  Will you post on [[Wikipedia talk:WikiProject Mathematics\u200e]] with the contact details, please?  It would be interesting to know what the developers plans are for the VE mathematics interface, and I'm sure you'll find there's a lot of useful experience and expertise in the mathematics community available for you to tap into if you would share your thinking with us as early as possible.  [[User:Spectral sequence|Spectral sequence]] ([[User talk:Spectral sequence|talk]]) 21:17, 2 August 2013 (UTC)\n""]","21:17, 2 August 2013 (UTC)",Spectral sequence
+"[""==I've given up testing V/E==\n"", ""I was one of the testers early in the year and I thought it might be helpful to explain why it was such a frustrating exercise and why I wouldn't recommend it to others. Firstly there were too many testers for the size of the development team, we kept finding that we'd not discovered a new bug, rather we were the nth editor to report a particular known bug (Taking it out of Beta testing early has presumably only made that worse). Sometimes bug reports just went off into the archive without comment or action. Secondly it quickly became clear that v/e is not aimed to be a logical editor for people like myself who make large numbers of minor typo fixes. For me the lack of prefill in the edit summary field is a big deal, much bigger than for the editor who spends half an hour over each edit and for whom the edit summary is a small part of their editing. Once I heard that they weren't going to fix the prefill issue then I knew I'd personally be sticking with the classic editor.\n"", 'Then there\'s the whole problem with bugzilla. it isn\'t a wiki, it isn\'t even in SUL. Bugzilla looks almost like a tool the developers use to insulate themselves from the community. Lastly but most seriously I\'ve done software testing in previous careers, I\'ve been on the testing side and also the development side. In my experience it works best when you go back to the tester and tell them that you\'ve now fixed the bug they spotted. \'\'[[User:WereSpielChequers|<span style=""color:DarkGreen"">Ϣere</span>]][[User talk:WereSpielChequers|<span style=""color:DarkRed"">Spiel</span>]]<span style=""color:#CC5500"">Chequers</span>\'\' 18:23, 2 August 2013 (UTC)\n']","18:23, 2 August 2013 (UTC)",WereSpielChequers
+"["":I completely agree and had the same reaction. When I found out about VE it was May and as I was testing I found that the developers weren't particularly interested in fixing the bugs, they seemed to be more interested in documenting them so that when they released VE they could say the problem was identified. When we told them months ago that the program wasn't ready and they should delay it, they didn't listen and released it anyway wiping away any good will that the community had. Even given the huge push back they received from the community. They have even made comments in various places that the response from the community was better than they expected. Really? This is better than expected? I would hate to see what they did expect. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 18:59, 2 August 2013 (UTC)\n""]","18:59, 2 August 2013 (UTC)",KumiokoCleanStart
+"['\n', '::Thank. That just confirms my suspicions about this. It is nice to have some confirmation. However, I am a little dismayed some criticism of me making the same points on the main page for making the same points, along with positive suggestions of how things might be improved (which impact on improved project management to test properly before releasing beta software, and proper survey design to avoid loaded questions), which allege that I have only made denigratory comments and that I have been entirely negative. I hope it doesn\'t mean that not only do the team not want to do anytjing about bugs, but they do not want people to specifically criticize what has emerged and make positive suggestions of how they might work better. [[User:ddstretch|<span style=""border:1px solid DarkGreen; padding:1px;""><span style=""color:White; background:DarkGreen; font-size:x-small;"">&nbsp;DDStretch&nbsp;</span></span>]]&nbsp;[[User talk:ddstretch|<span style=""color:DarkGreen; font-size:x-small;"">(talk)</span>]] 20:31, 2 August 2013 (UTC)\n']","20:31, 2 August 2013 (UTC)",ddstretch
+"["":::I wouldn't take it personally. The same types of comments have been made to many of us. It seems unless you are there to pat the WMF on the back and tell the what great job they did and how wonderful VE is they don't want to hear it and just dismiss comments as meaningless. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 20:43, 2 August 2013 (UTC)\n""]","20:43, 2 August 2013 (UTC)",KumiokoCleanStart
+"['::::Kumioko, if you [https://bugzilla.wikimedia.org/reports.cgi?product=VisualEditor&datasets=RESOLVED look at the chart here], I think you will find that the devs resolved almost a hundred bug reports during May.  That doesn\'t sound to me like evidence that they ""weren\'t particularly interested in fixing the bugs"".  Since the software developers seem to prefer actually fixing the bugs to merely talking about the need to fix them, though, I can easily see how the situation might result in an inaccurate appearance that they didn\'t care.  I\'m sorry that their decision to fix more bugs instead of fixing fewer bugs but documenting their work on this particular wiki left you with such an inaccurate idea about whether the bug reports were read or being used.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 21:18, 2 August 2013 (UTC)\n']","21:18, 2 August 2013 (UTC)",Whatamidoing (WMF)
+"["":::::Whatamidoing, that was a good attempt at deflecting my comments but ineffectual I'm afraid. It has nothing to do with that at all. None of what you say is accurate of what occurred or what has been conveyed by the developers repeatedly in multiple conversations. My criticism at the developers and other members of the WMF isn't based on their lack of comments but what they actually did and said when they said it. Your also right they fixed a lot of bugs in May but fixing 100 problems of hundreds is hardly sufficient. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 22:41, 2 August 2013 (UTC)\n""]","22:41, 2 August 2013 (UTC)",KumiokoCleanStart
+"['\n', "":Agree totally.  This seems like a development team that had a good idea, and plunged ahead with it, but brought it out to a large pool of user-testers before they realized that they bit off more than they could chew.  Philosophically and practically, I can see a lot of value in making an easy-to-use interface available for the casual editor.  As a semi-active editor, I found it disconcerting to have the vast majority of edits I made become less-convenient.  There were 2 major impediments: the VE interface became the default in many contexts, requiring me to learn new habits to do the same old thing and the VE was, and continues to be, unreasonably slow.  The bugs and lack of clarity in scope compounded this by making me do everything twice: once in VE to discover it wouldn't work, then again in source to get it done.  It would have been better to hold off launch (both Beta and production) until the dev team had a more mature product.  It would also be good to slow the increase in scope of VE until there's enough hardware bandwidth available to support it.  I hope neither has gotten to the stage that it's too late to do anything. --[[User:Wcoole|Wcoole]] ([[User talk:Wcoole|talk]]) 21:13, 2 August 2013 (UTC)\n""]","21:13, 2 August 2013 (UTC)",Wcoole
+"[':[[User:WereSpielChequers|WereSpielChequers]], the edit summary ""prefill"" (or drop-down with previously used summaries) is currently involved in [[bugzilla:52133]] and it seems like there is a chance that this *could* be fixed. [[User:Killiondude|Killiondude]] ([[User talk:Killiondude|talk]]) 23:31, 2 August 2013 (UTC)\n']","23:31, 2 August 2013 (UTC)",Killiondude
+"['::But it was also raised as {{phab|50274}} and the devs don\'t seem interested in fixing it (""low enhancement"" and some pretty negative comments). [[User:PamD|<span style=""color:green;"">\'\'\'\'\'Pam\'\'\'\'\'</span>]][[User talk:PamD|<span style=""color:brown;"">\'\'\'\'\'D\'\'\'\'\'</span>]] 09:22, 3 August 2013 (UTC)\n']","09:22, 3 August 2013 (UTC)",PamD
+"['::Hi Killiondude, it is good to hear that they are now considering how to fix this, though I\'m not keen on the drop down box solution, we already have that as an option and it doesn\'t work well for me. But it is a sign of there being too many testers even at the Beta phase in May problem that I didn\'t hear that news from the developers or the community liaison. \'\'[[User:WereSpielChequers|<span style=""color:DarkGreen"">Ϣere</span>]][[User talk:WereSpielChequers|<span style=""color:DarkRed"">Spiel</span>]]<span style=""color:#CC5500"">Chequers</span>\'\' 17:47, 3 August 2013 (UTC)\n']","17:47, 3 August 2013 (UTC)",WereSpielChequers
+"["":::I would like to thank everybody here who has kept testing VE since May. I have actually read several comments of people, not just on en.wp, who noticed many improvements in these months (personally, I don't think you really need charts to ''see'' that), but I guess their stories are not so interesting ;) Anyway, I am not aware of people being personally notified about bugs, simply because Bugzilla has exactly this feature (you get an email each time someone updates that bug, so I really suggest that you give it a try!) I'd also notice that Bugzilla has been around like, forever, so that's at least one thing I would not blame VE for :) --[[User:Elitre (WMF)|Elitre (WMF)]] ([[User talk:Elitre (WMF)|talk]]) 19:06, 3 August 2013 (UTC)\n""]","19:06, 3 August 2013 (UTC)",Elitre (WMF)
+"['::::Thanks Elitre, I\'m aware that bugzilla precedes this saga, but this has highlighted its deficiencies, especially because of the way the number of testers was increased far beyond the ability of the developers to cope.  I believe that most of the bugs that I found in May were ones that had already been identified, and I doubt that has changed. It is now August, major problems like v/e\'s unacceptable slowness for older CPUs have been known for literally months. So the typical experience of someone reporting a v/e bug is going to be that after a while someone will mark it as a dupe of an existing bug, they will then discover how long the bug was known about before they suffered from it, and then they won\'t hear anything more. Bugzilla might have worked with a smaller group of testers or if the developers were so on top of things that most reported bugs were new bugs. But it isn\'t a suitable system for this situation. It is especially problematic for using IP editors as guinea pigs since Bugzilla does not allow reporting by unregistered IP editors. \'\'[[User:WereSpielChequers|<span style=""color:DarkGreen"">Ϣere</span>]][[User talk:WereSpielChequers|<span style=""color:DarkRed"">Spiel</span>]]<span style=""color:#CC5500"">Chequers</span>\'\' 23:39, 3 August 2013 (UTC)\n']","23:39, 3 August 2013 (UTC)",WereSpielChequers
+"['\n', '\n', "": I'm pleased to see that there is some sort of serious discussion regarding the state of VE being raised here. The fact is that there are more than a few bugs left to be ironed out, yet accusations as to wikimarkup elitism is being thrown around on the project page. Why has been accepted that VE must be rolled out right here, right now? Has some sort of belated Y2K bug been detected making the rolling out of a seriously flawed beta version not only inevitable but urgent? There seems to be a mentality surrounding VE that, now that it's gone live it's reached some invisible 'point of no return'. Please, take a serious look at some of the comments regarding where it's failing. The issues do not revolve around elitism or some imagined dinosaur mentality. --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 10:40, 3 August 2013 (UTC)\n""]","10:40, 3 August 2013 (UTC)",Iryna Harpy
+"['\n', '::The problem is that well-established and proven methods of managing this kind of project, including when and how to test it, and when and how to roll it out, have apparently not been followed completely. Thus we have a buggy editor released that cannot do many of the tasks people would want it to do (this highlights a lack of proper prior research about users\' needs), and a set of loaded questions that form this RFC produced that seem to pre-suppose that this editor will be kept and firmly introduced, almost in its present state, to beginners and anonymous editors when it is still announced to be ""beta software"". I quite agree with what various users have said, both on this talk page and on the main RFC page for these discussions, but I am dismayed at the dismissive reaction that mean many of our valid criticism of the faults of the software, and the apparent flaws in the process of managing this entire project are ignored. Iin one of my cases, a reply to some serious suggestions for improvement was used merely as an attack on my own personal integrity, so that I ended up being called unduly negative and denigrating. This seems to be a case of attention being given too much to the presentation of some new software and its praise, rather than a critical examination and frank appraisal of its content and actual process of development. At least, I would have hoped that the project team would have looked at the various wikipedia articles on software management and introduction, and then I hope they would at least have been able to give rational reasons why the well-accepted processes seem to not have been used here. Similarly, I would have expected some justification of the elementary mistakes made in asking such loaded questions in this RFC to be justified in a similar way (I have taught, advised and evaluated survey design and questionnaire design for over 30 years, so I do know about this issue in great detail.) Unfortunately, all we have are attempts to be dismissive of criticisms and attacks by others, which in other contexts would seem like defensiveness in the knowledge of problems that need to be covered up. I hope to be proved wrong here, but I would like to see some hard and definitive answers to these problems that have been raised by an official team-leader of this piece of software and project. It could have been done a lot better with some elementary knowledge unless special factors are present, and it would be good to know just what these factors could have been (if there are any), and how they were evaluated to be so important that this apparently flawed process was adopted and the well-established procedures not followed. [[User:ddstretch|<span style=""border:1px solid DarkGreen; padding:1px;""><span style=""color:White; background:DarkGreen; font-size:x-small;"">&nbsp;DDStretch&nbsp;</span></span>]]&nbsp;[[User talk:ddstretch|<span style=""color:DarkGreen; font-size:x-small;"">(talk)</span>]] 11:35, 3 August 2013 (UTC)\n']","11:35, 3 August 2013 (UTC)",ddstretch
+"["":::I've come to the point of believing that main reason for the schedule can be found in [https://wikimania2013.wikimedia.org/wiki/Submissions/VisualEditor:_The_present_and_future_of_editing_our_wikis here]. Every time the question was asked about why maintaining the insane schedule was asked, no answer. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 12:21, 3 August 2013 (UTC)\n""]","12:21, 3 August 2013 (UTC)",NicoV
+"['::::It\'s pretty much impossible to explain why they\'ve ""maintained the insane schedule"", because they haven\'t actually stuck to the original schedule.  I believe that the only event on the schedule published earlier this year that happened on the originally projected date was the 01 July rollout to registered editors at the English Wikipedia.  Everything since then has been delayed by weeks to months.  \n', '::::At this point, more than 90% of wikis will get VisualEditor after Wikimania.  Nobody at the WMF seems to be even slightly unhappy about that, and I\'ve never seen a single staffer suggest that it would even be desirable.  (In fact, the only thing they have said is that it would be extremely undesirable to deploy anything or make any changes at all during Wikimania.)  The ""must be done by Wikimania"" rumor seems to just be another unfounded rumor with no basis in fact.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 22:19, 3 August 2013 (UTC)\n']","22:19, 3 August 2013 (UTC)",Whatamidoing (WMF)
+"["":::::Granted, Wikimania may or may not be the reason. But if its not then why on earth would the WMF insist on keeping pushing VE after so many have said it isn't working, isn't wanted or isn't compatible. I have been on Wiki for years and I have seen the community push back on a lot of things. VE is the most reviled feature that the WMF has ever pushed out and largely because they refuse to except the fact that the app isn't ready for rollout. If they would just see reason and slow the F down and fix the problems then I think most folks would be ok with it or get behind it. But when we have an application that still causes massive errors and doesn't even work on most major browsers then its time to accept they F'ed up pull it back into an opt in state and keep working on it until its worthy of our time. But right now its a waste of our time to even use it given all the problems and its making people stop editing. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 22:45, 3 August 2013 (UTC)\n""]","22:45, 3 August 2013 (UTC)",KumiokoCleanStart
+"[':::::::I gave up trying to deal with developers after they kept insulting me for asking that the ridiculously-bad handling of large PNGs be fixed, or the several fixes made and abandoned actually be finished. Did you know complaining is grounds for block on bugzilla? It\'s off-topic, see. <span style=""text-shadow:grey 0.118em 0.118em 0.118em; class=texhtml"">\'\'\'[[User:Adam Cuerden|Adam Cuerden]]\'\'\' <sup>([[User talk:Adam Cuerden|talk]])</sup></span> 00:48, 4 August 2013 (UTC)\n']","00:48, 4 August 2013 (UTC)",Adam Cuerden
+"[""::::::::Like [[User:ddstretch|DDStretch]], I've been involved with my university's survey & questionnaire unit (attached to the Faculty of Economics, Business Studies) for the last 20 years, and have to agree that the methodology deployed here could be presented as a prime example of a flawed strategy from inception to delivery. I've also worked on web development since the mid 90's and am all too familiar with overexcited IT specialists getting caught up in the moment and forgetting all about the demographic they are purportedly serving. Similar concepts of 'updating' the [[Wikipedia:2013_main_page_redesign_proposal/RFC|Wikipedia entry page RfC]] recently brought up issues of primary concern which are constantly being overlooked:\n"", ""::::::::A) Many contributors do not live in a major US city with high broadband speeds, nor do they even have access to newer computers (much less be in a position of being able to install contemporary browsers). I have sincere doubts that, even if VE was even close to par for newer computers, it would not be backwards compatible for more than a couple of older OS's or older versions of predominant browsers. Well, that's wonderful incentive for attracting new contributors. If you don't already feel like a second-class citizen, we'll make certain you don't forget it.\n"", ""::::::::B) The fact that VE does not show hidden code, doesn't support mathematical & scientific algorithms & symbols, does not support non-Latin-based charactersets/scripts, etc. is a serious concern, not something to be addressed at a later date if someone gets around to it & can actually find a fix.\n"", ""::::::::Ultimately, Wikipedia is being treated as a test site for budding programmers to flex their grey-matter muscle. I seriously believe that [[WP:NOT|'What Wikipedia is Not']] should be expanded to state that it is not a commercial site trying to compete with the gimmickry of social networking sites luring in those with expendable incomes to the ends of attracting advertising bucks. Also, while Wikipedia is not a democracy, neither is it here to be usurped by minority interest groups over and above the needs/wants of of the majority. New ideas on methods of delivery do not necessarily equal progress. --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 04:31, 4 August 2013 (UTC)\n""]","04:31, 4 August 2013 (UTC)",Iryna Harpy
+"['::::::::: Incidentally, [[User:Whatamidoing (WMF)|Whatamidoing]], responses such as, ""At this point, more than 90% of wikis will get VisualEditor after Wikimania. Nobody at the WMF seems to be even slightly unhappy about that, and I\'ve never seen a single staffer suggest that it would even be desirable."" do not actually qualify as being valid responses to valid questions being posed by contributors who have serious & legitimate concerns about VE both in general & on specific matters. You\'re merely relaying a point that has been understood by those who are not part of the WMF. Could you please provide some information on the number of individuals who constitute WMF as opposed to the number of Wikipedians who are regular contributors (usually working on their own & in their own spare time)? WMF = what percentage of the overall content of Wikipedia? An approximation would suffice. --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 05:04, 4 August 2013 (UTC)\n']","05:04, 4 August 2013 (UTC)",Iryna Harpy
+"['::::::::::The question asked was whether the WMF staff cared about having VE rolled out before Wikimania.  The answer, as far as I can tell, is ""no"".  This seems to me to be a relevant answer to a valid question.  \n', ""::::::::::I don't think that I understand your question about the percentage of content.  The WMF staff [[DMCA|does not create encyclopedia content as part of their jobs]].  Staff members are permitted to volunteer just like anyone else.  For example, you have made [[Special:CentralAuth/Iryna_Harpy|456 edits to all WMF projects combined]] so far, and I think that [[User:WhatamIdoing|my volunteer account]] is approaching 75,000 these days.  But that's strictly volunteer work and has nothing at all to do with my current role as a staff member.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 21:42, 4 August 2013 (UTC)\n""]","21:42, 4 August 2013 (UTC)",Whatamidoing (WMF)
+"["":::::It's just not the truth to say that the only part of the schedule that was kept was July 1st, because many steps were kept or delayed for 1 week at the last moment (but still compatible with showing that VE ''is the default editor'' at wikimania)... A/B test was kept, rollout to registered users was kept (July 1st), rollout to anonymous users was kept (July 15th), rollout to registered users on major wikis was kept (July 24th), rollout to anonymous users on majour wikis was kept (July 29th). There has been no explanation about why keeping this [[Wikipedia:VisualEditor#Timetable|timetable]], even when asked so many times, when VE is clearly showing that it's not ready. The only step that has been really postponed is the rollout to all other projects. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 06:57, 4 August 2013 (UTC)\n""]","06:57, 4 August 2013 (UTC)",NicoV
+"[""::::::Not true. Please check the ''history'' of any page including the schedule to find out how many things (not just dates) changed. --[[User:Elitre (WMF)|Elitre (WMF)]] ([[User talk:Elitre (WMF)|talk]]) 07:02, 4 August 2013 (UTC)\n""]","07:02, 4 August 2013 (UTC)",Elitre (WMF)
+"[':::::::Yes, I have [http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor&oldid=562292970 checked]: July 15th (anonymous on enwiki) instead of July 8th, July 24th (registered on major wikis) and 29th (anonymous) instead of July 15th. For me, this is still a schedule that was kept without any explanation on why it was so urgent (still no answer to that question). --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 07:10, 4 August 2013 (UTC)\n']","07:10, 4 August 2013 (UTC)",NicoV
+"[""::::::::That's still a major point no one from WMF seems to want to answer... and we're still asking and waiting on an answer as to WHY this roll out has been treated as if it were an absolute priority over even being able to decide on what to name the tabs! The names have been changed but, for any new users, there's absolutely nothing intuitive about the nomenclature. You hadn't even thought that out properly. Is this some sort of rollercoaster ride with unstoppable momentum or are you simply not prepared to listen to contributors asking you to slow down due to valid concerns? WHY IS THE VISUAL EDITOR BEING ROLLED OUT WHILE HAS BEEN IDENTIFIED AS BEING FUNDAMENTALLY SERIOUSLY FLAWED? Is that really such a difficult question to answer? --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 10:20, 4 August 2013 (UTC)\n""]","10:20, 4 August 2013 (UTC)",Iryna Harpy
+"[':::::::::NicoV, the A/B test was also delayed.\n', ':::::::::Iryna, perhaps you could explain what\'s left to ""slow down"" here at the English Wikipedia.  Nothing else (except many bug fixes) was planned for the English Wikipedia after the IP rollout.  The only thing that could be ""slowed down"" (rather than ""reversed"" or ""hidden"" or ""removed"") is availability at other projects, which naturally would have no effect here.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 21:42, 4 August 2013 (UTC)\n']","21:42, 4 August 2013 (UTC)",Whatamidoing (WMF)
+"[""::::::::::Not only do we need to delay the rollout to other project until VE is fixed we need to de-roll it here. They can't even get it to work with some of the major browsers and can't get it to stop adding or removing stuff it shouldn't be doing. '''At this point the WMF is responsible for every error that VisualEditor makes.''' But in this case we can't block them as we would anyone who fails to follow the rules of use for AWB, twinkle or the other tools.[[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 21:52, 4 August 2013 (UTC)\n""]","21:52, 4 August 2013 (UTC)",KumiokoCleanStart
+"['::::::::::The A/B test was delayed only a few days, and instead of delaying the rest, it got reduced to 3 days, and the roll out kept going on immediately (registered, anonymous) without even waiting for the analysis... And you keep dodging the question about why it was urgent to roll out VE to every one, as it has been done each time the question was asked. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 21:57, 4 August 2013 (UTC)\n']","21:57, 4 August 2013 (UTC)",NicoV
+"["":::::::::::In my opinion the reason he and others are dodging the question is because there is no reason or justification for it. He doesn't answer because he doesn't know any more than the rest of us. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 22:03, 4 August 2013 (UTC)\n""]","22:03, 4 August 2013 (UTC)",KumiokoCleanStart
+"["":::::::::::: For a programmer, you're doing an excellent impression of a politician, [[User:Whatamidoing (WMF)|Whatamidoing]]. No matter how I parse your response to me it reads as game of semantics rather than anything remotely resembling an answer. If the implementation of V/E is a foregone conclusion, why is the RFC even bothering to ask questions such as whether unregistered users & anonymous IP's should be given the option of opting in, etc.? Surely, the whole kit & caboodle was planned to be in place ASAP regardless of whether it actually worked or not. I'll play at semantics with you: why isn't V/E being rolled back in order to discuss and analyse fundamental issues plaguing the system when there is such an overwhelming negative response to V/E in its current state? Personally, I'm not calling for it to be scrapped as it may well develop into a reasonable supplementary tool (if not as a viable alternative to source coding) at some point in the future. The future, however, is not here and now. V/E is beyond problematic in its current state and the attitude to the naughty naysayers smacks of blatant disregard for those who have to clean up the messes it leaves in its wake. You're dodging the real questions and you know it. Delays on rolling out flawed software and quickly rolling back while bugs are fully identified & addressed are counted by weeks and months, not by hours. --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 01:32, 5 August 2013 (UTC)\n""]","01:32, 5 August 2013 (UTC)",Iryna Harpy
+"['{{outdent}}\n', ""I am not a programmer.  (I'm also female.)\n"", '\n', 'The RFC was begun by editors at the English Wikipedia.  The WMF has no reason to interfere in their decision to discuss it.  In fact, the WMF is actually interested in their opinions on the matter.  The ""number of users"" isn\'t so interesting, but the reasons, concerns, and specific problems identified are very interesting, because it helps the devs understand what the most pressing problems are for the real users.\n', '\n', 'NicoV, I think that the devs\' understanding and the community\'s understand of the schedule are very different.  You ask ""why was it so urgent?""  As far as I can tell, it wasn\'t rolled out because it was ""urgent""; it was rolled out because it was normal to do so at that point in development.  We had discussions here about what features were important to have in place before it was made available to all of our editors here.  We all agreed that VisualEditor could be made available as soon as basic support for refs and templates was available.  These features were added, and therefore it was made available to everyone shortly afterwards.  There was no ""rush"" or ""urgency"" to get it out on the devs\' part.  I realize that a software developer\'s idea of ""ready"" and an end-user\'s idea of ""ready"" can be very different, but the devs actually thought it was ready (by their definition).  The WMF is not averse to slipping schedules; in fact, if you go read about previous projects, you\'ll see that they have something of a reputation for delivering products late, and this doesn\'t seem to bother them.  So:  why the rush?  There was no rush.  There were only different ideas about what constitutes readiness.\n', '\n', ""VisualEditor has not been completely removed for all users at this time for several reasons, which you will find repeated on this and other pages.  Just in case you haven't seen them or did not recognize that these were answers to your question, I offer these brief summaries of several major points:\n"", '# Removing VisualEditor means hiding it from new users who have made hundreds of successful edits in VisualEditor and do not know how to use the old markup editor.  ""I want to hide this from everyone who is using it"" requires a substantially stronger justification than ""I want to hide this for my account only"".\n', ""# The devs need to know what does and doesn't work for thousands of real-world users on thousands of articles, so that they can figure out what effect each small change has.  They need to know how it works, or doesn't, for people working on an enormous variety of articles.  It's useful to know whether it works on a very average article like [[Golden-crowned Sparrow]], but it's also important to find out whether it breaks the very few articles here that uses the {{tl|R}} template system or [[WP:List-defined references]].  It's important to find out [http://en.wikipedia.org/w/index.php?title=Leukemia&diff=567189014&oldid=566709522 how the table breaks] when someone (quite possibly me) misformats a table.  Real-world experience, with all of the odd combinations of browsers, computers, articles, previous actions, and user skills, is not something that can be achieved with structured testing or by having a few dozen experienced editors opt-in. \n"", '# The staff is mostly out of town for the first half of August.  There is essentially a code freeze until the middle of August.  You should not expect anything other than a total, site-completely-down disaster to result in changes before August 15th.\n', ""NB that this is not a complete list of reasons, and that in being a summary, some of the nuance and complexity is being lost.  But please notice also that, to the extent that any of these points sound familiar to you—I believe you have personally contested some of these points—then that familiarity is proof that this question has been answered within your 'hearing' already. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 19:17, 5 August 2013 (UTC)\n""]","19:17, 5 August 2013 (UTC)",Whatamidoing (WMF)
+"[':""\'\'...it was rolled out because it was normal to do so at that point in development\'\' isn\'t true, Whatiamidoing. Most developers wait until they have basic functionality. Additionally, if they do A/B testing, they wait until they have analysed the results before they proceed. It\'s extremely implausible that the release wasn\'t done in order to be able to claim that a date goal was met.\n', "":I've said it before and I will say it again: when one has made an extremely public mistake, the best route forward is usually a heartfelt apology and a pledge not to repeat the mistake again. It's unfortunate that the WMF still fails to acknowledge that it even ''made'' a mistake, much less showing any inclination to apologize for it and learn from it.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 20:21, 5 August 2013 (UTC)\n""]","20:21, 5 August 2013 (UTC)",Kww
+"[""::I do agree with Kww, because it wasn't 1 roll out, but 5 roll outs. I've been in the software development community for quite a while, and when you start to roll out a software and see many bugs piling up fast, as a developer you never want to roll out to even more users, but that's what you're telling happened on the last several rolls out ?\n"", ""::And, when I read that ''staff is mostly out of town for the first half of August'', I understand that the initial planning was to have a full roll out to every wiki just before every staff was unavailable ([http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor&oldid=562292970 29 July: Launch to all logged-in and anonymous users on all other projects]) and let every wiki then deal on their own with the problems ? What a great planning... --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 20:58, 5 August 2013 (UTC)\n""]","20:58, 5 August 2013 (UTC)",NicoV
+"[':::As I said, your idea of basic functionality and the devs\' idea apparently differ.  The devs seem to subscribe to the [[agile programming]] notion of many small ""incomplete"" deployments rather than one big ""finished"" one.  What you\'ve seen is consistent with that philosophy.  Notice that I\'m not claiming that this philosophy is popular with end users, only that what you are seeing is normal for developers that subscribe to this approach.  As a person who is not afflicted with early adopter syndrome myself, I personally have more sympathy for your definition than for the devs\', but this is entirely normal for this style. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 18:30, 6 August 2013 (UTC)\n']","18:30, 6 August 2013 (UTC)",Whatamidoing (WMF)
+"['::Otherwise, to answer your points:\n', '::# Advertisement has been made now that VE has been rolled out to everyone on enwiki, so even going back to opt-in, you would probably get many users opting in, but at least they would be warned that VE is alpha/beta and they need to check their edits. That\'s the main reason I\'m among the users asking for ""opt-in"": so that people using VE are aware of it being alpha/beta, and so that we can reduce the number of articles being damaged daily.\n', ""::# The problem is that the staff already has hundreds of bug reports/enhancements to work on, and they can't keep up with the flow. So, what many are asking is that the staff takes care of that backlog before letting it be used by everybody, because the only way to make users aware of the current problems is to make them act themselves to activate VE before using it.\n"", ""::# For 3, I've already answered above, and I'm baffled by this. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 21:06, 5 August 2013 (UTC)\n""]","21:06, 5 August 2013 (UTC)",NicoV
+"["":::# Every VisualEditor user has received (or will receive, if they've never opened it) a warning about this.  Until you acknowledge the warning, you are not permitted to do anything else in VisualEditor.  If your actual goal is to warn the users, then it has already been met.\n"", "":::# The devs have already resolved 70% of the bugs already reported, which suggests that they are keeping up with the flow.  Also, if you're familiar with the agile programming philosophy, continuing to receive reports is important.  Then you can discover unintended side effects.  For example, VE users originally were massively, wildly more likely to use edit summaries than users of the classic wikitext editor, and now they're only significantly more likely.  Something changed, but what?  If you dump two hundred bug fixes on the system at once, you'll have no hope of figuring out which ones had that effect.\n"", ':::# The original rollout would have given them a bit more than a week to deal with any truly major problems (e.g., VisualEditor simply does not work on the Chinese Wikipedia; by the way, there have been none in the projects that have enabled VisualEditor so far).  Since major problems are usually obvious within minutes, if not hours, of general use, then a week is probably enough.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 18:30, 6 August 2013 (UTC)\n']","18:30, 6 August 2013 (UTC)",Whatamidoing (WMF)
+"['{{unindent}}\n', ""Well, in [[agile programming]], there are several concepts: '''customer satisfaction''' (not achieved), '''welcome changing requirements''' (not achieved), '''working software''' (not achieved), '''close, daily cooperation between business people and developers''' (not achieved), '''minimal bugs''' (not achieved), ...\n"", '\n', ""There are currently more than [https://bugzilla.wikimedia.org/buglist.cgi?list_id=223852&resolution=---&resolution=LATER&query_format=advanced&product=VisualEditor 700 open bugs for VE] and [https://bugzilla.wikimedia.org/buglist.cgi?list_id=223852&resolution=---&resolution=LATER&query_format=advanced&product=Parsoid 140 for Parsoid]: how do you come to ''resolved 70% of the bugs'' and ''keeping up with the flow'' ?\n"", '\n', ""If users have been warned, then it's not enough, because damaged articles are piling up.\n"", 'The problem is that the goal of Wikipedia is producing an encyclopedia, not becoming a testing platform as you seem to believe... --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 19:39, 6 August 2013 (UTC)\n']","19:39, 6 August 2013 (UTC)",NicoV
+"['== Where is the most simplistic option for this discussion? ==\n', '\n', 'All I see is section after section of loaded questions. Where is the area to simply state that \'\'\'""Yes/No, Visual editor should be/not be enabled for new users and anonymous editors?""\'\'\' or simple Yes/No answers? The fact that the entire commenting thing is split into specific section only makes me wonder if the whole process is making it more difficult for honest answers and voting? --[[User:293.xx.xxx.xx|293.xx.xxx.xx]] ([[User talk:293.xx.xxx.xx|talk]]) 21:03, 2 August 2013 (UTC)\n']","21:03, 2 August 2013 (UTC)",293.xx.xxx.xx
+"[':Well, it \'\'\'\'\'is\'\'\'\'\' a [[WP:RFC|request for comment]] and not a ""request for vote"". That having been said, you can answer yes or no in the specific/corresponding section(s). I think this was a rather well organized RFC. Nothing is perfect, especially with the massive amount of people commenting and discussing. I don\'t really like that people have turned the main RFC page into a general discussion forum at the bottom, though. [[User:Killiondude|Killiondude]] ([[User talk:Killiondude|talk]]) 23:33, 2 August 2013 (UTC)\n']","23:33, 2 August 2013 (UTC)",Killiondude
+"['::Well, they do ask for comment, and my comment is a simple Yes/No format, so at least some arrangement should be added in.--[[User:293.xx.xxx.xx|293.xx.xxx.xx]] ([[User talk:293.xx.xxx.xx|talk]]) 00:07, 3 August 2013 (UTC)\n']","00:07, 3 August 2013 (UTC)",293.xx.xxx.xx
+"["":::I suspect you meant the 'simplest' option, not the most [http://en.wiktionary.org/wiki/simplistic 'simplistic'] - well, I certainly hope that's what you meant! Yes/No formats are, by nature, far more loaded as they assume right and wrong answers. The objective here is to initiate dialogue. As it stands, many are already of the opinion that the questions posed are not only loaded but the wrong questions. Without the opportunity to engage in a discussion, the broader Wikipedia community would be entirely disempowered... which is not what RFC's are about. As it stands, if you don't want to comment, you are free to simply add an 'agree', 'disagree', 'support', etc. without explaining yourself. Cheers! --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 04:53, 5 August 2013 (UTC)\n""]","04:53, 5 August 2013 (UTC)",Iryna Harpy
+"['== About 2.1 Question syntax ==\n', '\n', '\'\'2.1 Question 1: When a new account is created, should the preference be set to disable VE (""opt-in"") or to enable VE (""opt-out"")?\'\'\n', '\n', 'Should that read,\n', '\n', '\'\'2.1 Question 1: When a new account is created, should the preference be set to disable VE (""opt-out"") or to enable VE (""opt-in"")?\'\'\n', '\n', 'As in opting out of the VisualEditor?\n', '[[User:Davidf2|Df2]] ([[User talk:Davidf2|talk]]) 08:12, 3 August 2013 (UTC)\n']","08:12, 3 August 2013 (UTC)",Davidf2
+"[':No, ""opt-out"" means you must choose if you wish to turn it off, e.g default is on. <span style=""text-shadow:grey 0.118em 0.118em 0.118em; class=texhtml"">\'\'\'[[User:Adam Cuerden|Adam Cuerden]]\'\'\' <sup>([[User talk:Adam Cuerden|talk]])</sup></span> 10:44, 3 August 2013 (UTC)\n']","10:44, 3 August 2013 (UTC)",Adam Cuerden
+"['::I understand the confusion:  You can read it as {{xt|should the preference be set to disable VE (""the user must manually opt-in"")}} or as {{xt|should the preference be set to disable VE (""the user is already opted-in by default"")}}.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 22:22, 3 August 2013 (UTC)\n']","22:22, 3 August 2013 (UTC)",Whatamidoing (WMF)
+"['== Opt-in for experienced users ==\n', '\n', 'I propose adding the following question to the RFC: ""Should users with technical flags (e.g. Autopatrolled, Rollbacker, Administrator) be able to opt-in rather than have to opt-out)? --[[User:Синкретик|Синкретик]] ([[User talk:Синкретик|talk]]) 09:37, 3 August 2013 (UTC)\n']","09:37, 3 August 2013 (UTC)",Синкретик
+"['== This RFC is irrelevant ==\n', '\n', ""You are hopelessly naive if you don't think the Wikimedia Foundation won't ram the VisualEditor through against any editor objections.\n"", '\n', ""That said, personally, I think it's a good thing. Wikipedia as has long needed stronger leadership to cut through its dysfunctional editor bureaucracy and make life better for ordinary users.\n"", '\n', 'Yes, the VisualEditor is far far too slow, it has a few bugs and its UI has issues (e.g. its clunky UI for templates, especially references) but it\'s clearly a step forward. Well, as long as they don\'t reintroduce that ridiculous ""edit"" rollover. -[[User:Halo|Halo]] ([[User talk:Halo|talk]]) 06:44, 4 August 2013 (UTC)\n']","06:44, 4 August 2013 (UTC)",Halo
+"[':Past experience is that if the community outrage goes beyond a certain point then the WMF will backtrack. So no people are not naive if they think that it is worth objecting. In the case of the visual editor a few months ago almost everyone wanted this and the criticism of the WMF was almost entirely over them being too slow to deliver a working visual editor. Things have changed, and there is now quite a bit of distrust of any sort of visual editor, but I suspect that the majority are still with me in wanting this providing the bugs can be fixed. Most of the current disagreement is over how many editors are needed to test something which still has bugs that were spotted three months ago.  I\'m in the zero camp as I see no point in testing until some major bugs are fixed, others argue for some level of ongoing testing and a number are very strongly asserting that they don\'t want to be forced into using V/E in the future. So the area of disagreement may not be where you think, as for the project needing strong leadership; Well that isn\'t any way to run a volunteer community, people have tried that model and it just doesn\'t work. Even if the Foundation had the money to offer a thousand or so editors jobs writing an encyclopaedia it wouldn\'t want to be legally responsible for what they write, and some of the best editors are volunteers who have no interest in turning their hobby into a paid job. \'\'[[User:WereSpielChequers|<span style=""color:DarkGreen"">Ϣere</span>]][[User talk:WereSpielChequers|<span style=""color:DarkRed"">Spiel</span>]]<span style=""color:#CC5500"">Chequers</span>\'\' 13:28, 4 August 2013 (UTC)\n']","13:28, 4 August 2013 (UTC)",WereSpielChequers
+"[""*This RFC is not irrelevant. As with any and all RFCs, not everyone will be happy about the direction that emerges; and there may be questions of disregarded consensus, but the RFC itself is the vehicle to have your collaborative input published if for posterity alone; and to me the damn fool is the one who decides to forgo his own right to be heard to spite his forgone conclusion that his voice is of no consequence.&nbsp;'':)''&nbsp;[[User:John Cline|John Cline]] ([[User talk:John Cline|talk]]) 13:51, 4 August 2013 (UTC)\n""]","13:51, 4 August 2013 (UTC)",John Cline
+"[""*I also agree that the RFC is a good thing. Rarely do more than 500 editors show up to vote to do anything so to see more than 300 vote to oppose VE it shows that the community doesn't like it and the WMF needs to take that seriously. The WMF doesn't edit, so if they want to keep this a volunteer site then they need to listen to the community, not ignore us and expect us to clean up their mess. I agree with WereSpielChequers that the WMF couldn't make this project work without the volunteers and I agree that they need to stop ramming it down peoples throats with the argument its for testing purposes. I think the app has a lot of potential, but its far from being ready and all the WMF has done by forcing it out half finished and with major bugs is make it less likely the community will ever accept it. We are going to need to cut this RFC off at some point and submit a formal proposal to the WMF letting the know the result. What they choose to do will tell us a lot about what they think about the community.[[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 16:08, 4 August 2013 (UTC)\n""]","16:08, 4 August 2013 (UTC)",KumiokoCleanStart
+"['**It isn\'t clear whether this RFC is asking about the current ""beta"" situation or all future ""beta"" versions, or the eventual model once Visual Editor is Fit for Purpose™? Who decides what would make it fit for purpose anyway: can we have an RFC on that? - [[User:Pointillist|Pointillist]] ([[User talk:Pointillist|talk]]) 16:30, 4 August 2013 (UTC)\n']","16:30, 4 August 2013 (UTC)",Pointillist
+"[""***I didn't want to muddle the RFC with questions about the future. There's a lot of things that ''may'' happen and a lot of people will have different opinions about what we should do depending on what happens. I focused the questions on what we should do ''now''. If things change in the future, we can have another RFC about what to do at that time.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 16:44, 4 August 2013 (UTC)\n""]","16:44, 4 August 2013 (UTC)",Kww
+"['****Thanks - [[User:Pointillist|Pointillist]] ([[User talk:Pointillist|talk]]) 16:56, 4 August 2013 (UTC)\n']","16:56, 4 August 2013 (UTC)",Pointillist
+"['== IE users ==\n', '\n', ""Before you put this up for discussion, you should at least make it clear that IE users cannot participate. As we represent the majority of editors, I think it would have been in order to make it clear that the new editor was only available to those using certain browsers. I have been pressing for a WYSIWYG approach to Wiki editing for years but have always been bulldozed down by the hierarchy. Now it's here, I would have liked to have clearer instructions on how to access the beta version and explanations on why it is not available to IE users. Is this yet another Google venture?--[[User:Ipigott|Ipigott]] ([[User talk:Ipigott|talk]]) 21:50, 4 August 2013 (UTC)\n""]","21:50, 4 August 2013 (UTC)",Ipigott
+"[':No, it\'s nothing to do with Google - I use Firefox and up until I disabled the blighter, VE was functional for me. I do know that the structure of Internet Explorer is vastly different from the other common Web browsers (Chrome, Safari, Firefox) that\'re available, which may be why IE users can\'t use VE (i.e. it relies on something the other browsers have that IE does not). IANAP, however, so you\'d have to ask clarification from the devs. —[[User:Jéské Couriano|<span style=""color:#228B22;"">\'\'Jeremy\'\'</span>]] [[User talk:Jéské Couriano|<span style=""color:#228B22;"">v^_^v</span>]] <sup><small>[[Special:Contributions/Jéské Couriano|Bori!]]</small></sup> 22:20, 4 August 2013 (UTC)\n']","22:20, 4 August 2013 (UTC)",Jéské Couriano
+"[""::They still can't get it to work right with IE. So they turned it off and it likely nothing below 8 will ever be usable. So that gives a couple of notes. First, all the problems so far identified are with browsers not used by the majority and once IE is supported, we are likely to see another large spike in bugs. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 00:19, 5 August 2013 (UTC)\n""]","00:19, 5 August 2013 (UTC)",KumiokoCleanStart
+"['\n', ':According to Wikimedia, IE accounts for about 20% of non-mobile reader traffic [http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm].  That\'s still a significant amount, but your claim that IE accounts for anything like ""the majority of editors"" is likely wrong.  [[User:Dragons flight|Dragons flight]] ([[User talk:Dragons flight|talk]]) 00:15, 5 August 2013 (UTC)\n']","00:15, 5 August 2013 (UTC)",Dragons flight
+"[""::Maybe but I don't think the 20% number is accurate either. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 00:20, 5 August 2013 (UTC)\n""]","00:20, 5 August 2013 (UTC)",KumiokoCleanStart
+"["":::So, basically, we've returned to a serious fundamental problem being that, aside from being browser dependent, V/E is platform and OS dependent. I've already brought up the issue of backwards compliance after the [[Wikipedia:2013_main_page_redesign_proposal/RFC|2013 Main Page Redesign Proposal RFC]] made it abundantly clear that many contributors don't have access to broadband, much less new computers. What versions of Chrome, Firefox, Safari, Opera, etc. are the minimum for being able to use V/E? It's fine to say that they'll still be able to edit at source level but the more elitist Wikipedia becomes, the less new contributors will feel welcome to be proactive. --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 01:56, 5 August 2013 (UTC)\n""]","01:56, 5 August 2013 (UTC)",Iryna Harpy
+"['::::It\'s worse than just broadband. VE is pretty slow on anything but fairly high-end machines. Albeit getting \'\'somewhat\'\' better over time, as in, ""unusable"" changing to ""theoretically usable, but still not a good idea"" <span style=""text-shadow:grey 0.118em 0.118em 0.118em; class=texhtml"">\'\'\'[[User:Adam Cuerden|Adam Cuerden]]\'\'\' <sup>([[User talk:Adam Cuerden|talk]])</sup></span> 11:22, 5 August 2013 (UTC)\n']","11:22, 5 August 2013 (UTC)",Adam Cuerden
+"['\n', 'The blacklist includes:\n', '* all Internet Explorer; eventually, this will be only IE 8 and earlier.  IE is notorious for having ""creative"" interpretations of web standards, and supporting it is a problem for everyone, not just the WMF.  A bit less than 10% of editors use a semi-modern IE and will have access eventually.  A bit less than that use old versions and will not have access ever.\n', '* old Firefox, versions 14 and older\n', '* old versions of Safari and Chrome\n', '* old versions of Opera.  Recent Opera (12 and newer?) are semi-supported:  it is not blacklisted but not whitelisted, either, so users get a warning.\n', '\n', ""Old browsers are simply incapable of doing some of the things that need to be done.  A 20-year-old web browser or OS is simply not capable of doing this.  I don't know if there is an organized list of browsers, but if there are other browsers or specific versions of interest, I can ask.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 19:37, 5 August 2013 (UTC)\n""]","19:37, 5 August 2013 (UTC)",Whatamidoing (WMF)
+"[':Where exactly has anyone spoken about hugely old web browsers? XP and IE 7 still take up a significant enough chunk of the market for there to be a justification for running VE on slightly older stuff. VE shouldn\'t require super-powerful computers anyway, and yet it appears to at present. I\'ve not seen any reason for the lack of Opera support given anywhere. The fact IE has ""creative"" interpretations of web standards is irrelevant; as a major web browser, the VE should \'\'\'not\'\'\' have been released until it supported it. People running IE are generally the sort of people the VE is supposed to attract, anyway; they\'re non-power users. That, and IE is the only browser with a stable, official 64-bit build, so some may use it for that reason. [[User:Lukeno94|<span style=""color:navy;"">Luke</span><span style=""color:FireBrick;"">no</span><span style=""color:green;"">94</span>]] [[User talk:Lukeno94#top|<i>(tell Luke off here)</i>]] 20:34, 5 August 2013 (UTC)\n']","20:34, 5 August 2013 (UTC)",Lukeno94
+"['::\'\'IE is the only browser with a stable, official 64-bit build\'\'? You surprise me. I don\'t understand what is either unstable (in the everyday sense of the word) or ""unofficial"" about, say, [https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/22.0/linux-x86_64/ Firefox 22 for Linux 64]. (Actually I don\'t use this; I instead use the ""[[Mozilla Corporation software rebranded by the Debian project|Iceweasel]]"" flavor, which is arguably even more ""official"", coming as it does directly from a Debian repository.) &para; I presume that the lack of support for Opera is caused by this or that Opera-specific problem; have the developers of VE spurned offers of help to fix this? -- [[User:Hoary|Hoary]] ([[User talk:Hoary|talk]]) 00:51, 6 August 2013 (UTC)\n']","00:51, 6 August 2013 (UTC)",Hoary
+"['::::No.  Volunteer developers are welcome.  In fact, I understand that the reason that Opera is now off the blacklist is because of a volunteer.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 18:37, 6 August 2013 (UTC)\n']","18:37, 6 August 2013 (UTC)",Whatamidoing (WMF)
+"["":::[[User:Whatamidoing (WMF)|Whatamidoing (WMF)]], I'd suggest that none of us are asking about specific browsers for our own benefit but that of the entire Wikipedia demographic. I have no doubt that there are many, many valuable contributors who don't have the money for constant upgrades but do have invaluable knowledge. Knowledge is Wikipedia's greatest resource. The more Wikipedia does to exclude contributors based on their economic status, the more it will lose it's most valuable resource. Just looking at the comments by utter illiterates carrying on about how cool VE is is absolutely nauseating. There, I've said it: I'm an intellectual snob. Pandering to the dolts & further disempowering anyone who isn't privileged enough to be middle-American is not going to nurture this knowledge-base. I still feel that, in order to work on Wikipedia, it is essential to know some basic coding. If the name of the game is to attract quality over quantity contributors then developing methods of making people feel like second class citizens is a mistake. In an ideal world, a visual editor that really works for everyone would be a delight. This isn't an ideal world, nor is VE even close to being an ideal visual editor. I apologise if this sounds mean-spirited as I don't want to be mean about it. I know you and your colleagues have worked hard and are continuing to work hard on an ambitious project... but it's really not functioning well enough to have rolled out. If it's still Alpha, don't pretend it's Beta. --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 01:21, 6 August 2013 (UTC)\n""]","01:21, 6 August 2013 (UTC)",Iryna Harpy
+"['::::Hisorically, Wikipedia has had a remarkably low penetration of IE users, and that is WMF\'s main argument for not rolling it out on IE at first. I actually suspect that works against them: I suspect the overlap of the ""I use IE because I don\'t know how to install software on my PC"" population and the ""oooh, wikitext is too scary for me"" population is quite large.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 02:03, 6 August 2013 (UTC)\n']","02:03, 6 August 2013 (UTC)",Kww
+"[':::::This is all very puzzling. I ""have the money for constant upgrades"", but I choose to spend it elsewhere, not least because my infrequent upgrades cost no money whatever. I\'ve no idea what being American or not, let alone being middle-American or not, has to do with any of this. I thought that I should give VE a whirl, and read that \'\'To edit a page using VisualEditor, click on the ""Edit<sup>beta</sup> "" tab at the top of the page\'\' (of an article or user page); but there\'s no such tab at the top or anywhere else, and the string ""beta"" appears nowhere in the page of an article (unless of course the article itself includes it). (Maybe I\'ve failed some intelligence shibboleth.) I\'ve never encountered anyone who\'s said ""I use IE because I don\'t know how to install software on my PC""; I have encountered plenty of people who say variations on (a) ""Yes I have an internet. What do you mean, \'Internet Explorer\'?"" or (b) ""I have to use Internet Explorer because the batshit \'security\' obsession of the IT people in my company prevents me from installing any alternative."" -- [[User:Hoary|Hoary]] ([[User talk:Hoary|talk]]) 02:16, 6 August 2013 (UTC) PS the IQ test I failed was related to RTFM. My ""skin"" was Cologne Blue; when I changed it to Vector, I successfully used VE with both Iceweasel (not the latest version) and Chromium (thereby incidentally disproving the assertion in [[WP:VisualEditor]] that \'\'VisualEditor currently works only in the most modern versions of Firefox, Chrome and Safari\'\'). -- [[User:Hoary|Hoary]] ([[User talk:Hoary|talk]]) 09:48, 6 August 2013 (UTC)\n']","02:16, 6 August 2013 (UTC)",Hoary
+"[""::::::Your rant has been directed at... whom, precisely, [[User:Hoary|Hoary]]? You've taken snippets out of a couple of comments and made [[Kielbasa|kovbasa]] out of them. Perhaps you could start again & make a little effort at actually making coherent a point. Is your point that you edit on IE at work (you're a bad person) and that you can't use VE because IE is the only browser you have access to. Maybe you should start actually doing your 'work' at 'work', or do they pay you for 'attendance' & the pleasure of your using their equipment & broadband for your personal development? --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 06:27, 6 August 2013 (UTC)\n""]","06:27, 6 August 2013 (UTC)",Iryna Harpy
+"[':::::::(i) What ""rant""? (ii) I do not edit on IE at work or anywhere else. (iii) When I edit at work (which is rare), I normally do so on Iceweasel. (iv) Thank you for your concern for my employer\'s return on its investment in me. (v) \'\'My point\'\' is that a number of the assertions and assumptions above are bizarre. Among these: Wikipedia excludes contributors by economic status; a significant number of the browsers still in use are 20 years old; ""IE is the only browser with a stable, official 64-bit build""; the reason why people don\'t add an alternative to IE is that doing so seems/is too difficult; some of the comments on this matter have been by ""utter illiterates""; upgrading software costs money. -- [[User:Hoary|Hoary]] ([[User talk:Hoary|talk]]) 07:27, 6 August 2013 (UTC)\n']","07:27, 6 August 2013 (UTC)",Hoary
+"[':::::::*I was referring to Windows builds with my 64-bit comment, as Windows is the predominant OS. There are surely more people using IE on Windows XP than those using Firefox on Linux. I run Chrome on Windows 7, so this doesn\'t affect me; nevertheless, it potentially would have affected me at my old school, which still ran XP, and some of the machines were stuck on IE7. [[User:Lukeno94|<span style=""color:navy;"">Luke</span><span style=""color:FireBrick;"">no</span><span style=""color:green;"">94</span>]] [[User talk:Lukeno94#top|<i>(tell Luke off here)</i>]] 08:08, 6 August 2013 (UTC)\n']","08:08, 6 August 2013 (UTC)",Lukeno94
+"[""::::::::*Yes, what you say is true. Incidentally, I'm very willing to believe that I move in very atypical circles, but I do move in more than one of them, and in these circles OS X is about as widely used as Windows. So although Linux isn't ''a'' predominant OS, I start to wonder if OS X might be. -- [[User:Hoary|Hoary]] ([[User talk:Hoary|talk]]) 09:43, 6 August 2013 (UTC)\n""]","09:43, 6 August 2013 (UTC)",Hoary
+"[':::::::::*Mac OS X is definitely widespread enough, and stable enough, for it to be a factor. Linux is a bit more tricky; there are so many different versions of it, and it\'s not at the same level as Mac OS X or Windows. Also an interesting question; I wonder how VE would run on a Chromebook? [[User:Lukeno94|<span style=""color:navy;"">Luke</span><span style=""color:FireBrick;"">no</span><span style=""color:green;"">94</span>]] [[User talk:Lukeno94#top|<i>(tell Luke off here)</i>]] 18:42, 6 August 2013 (UTC)\n']","18:42, 6 August 2013 (UTC)",Lukeno94
+"[""* Relatively few of our users have IE8 or older.  Given the fact that support is going away for IE8 soon, this number will be falling even further.  Nobody ever promised that this JavaScript-based editor would work for every single user.  For example, if your web browser is 20 years old, then I guarantee that it won't work, because your web browser is older than JavaScript.\n"", ""* Given the uptake at the Spanish Wikipedia, which draws a lot of users from South and Central America, I don't believe that the evidence supports the belief that only wealthy users get VisualEditor. \n"", '* I\'m a little mystified by the solution favored by some people here.  VisualEditor is \'\'\'temporarily\'\'\' not available to IE9 and IE10 users.  IE has gone on and off the blacklist over the last year; it was most recently re-added to the blacklist when user testing in June proved that it wasn\'t working (e.g., {{phab|51187}}, in which IE users can\'t save a page because of one of IE\'s non-standard quirks).  So it\'s currently not available for about 10% of our users because the users have IE9 or IE10, and they are working on changing VisualEditor to work around IE\'s quirks.  But the proposed ""solution"" to this gap—this temporary unavailability to a small group of editors—seems to be to take the product away from the 80% of users who \'\'don\'t\'\' use any version of IE, until the IE fixes are in place again (in a few weeks).  This idea that taking it away from everybody will make it available for more people does not seem logical to me.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 19:12, 6 August 2013 (UTC)\n']","19:12, 6 August 2013 (UTC)",Whatamidoing (WMF)
+"[':*Stop making the absurd comments about 20-year-old web browsers. We\'re talking about IE 7/IE 8 and Windows XP here, which are still being used by enough people for them to be taken into consideration. Also, people on IE are rarely ""power users"", and isn\'t the whole point of VE to enable ""non-power users"" to edit? It\'s nothing to do with wealth whatsoever; anyone can pirate an OS. VE should not have been released without support for the latest version of IE, and blaming the quirks of IE doesn\'t change that fact. Besides, if you\'d waited until it worked with IE, then you\'d have had a much more stable, feature complete version of the editor, and it would\'ve been more of a success... [[User:Lukeno94|<span style=""color:navy;"">Luke</span><span style=""color:FireBrick;"">no</span><span style=""color:green;"">94</span>]] [[User talk:Lukeno94#top|<i>(tell Luke off here)</i>]] 19:24, 6 August 2013 (UTC)\n']","19:24, 6 August 2013 (UTC)",Lukeno94
+"[""::Why exactly should IE's problems hold back everyone else?  Is it truly important to you that every user have exactly the same access at the same time?  I believe that IE7 represents less than 2% of Wikipedia users, which is not IMO a really sizable group.  Would you block everyone else over one or two percent?  If so, then why aren't mobile users, which represent a dramatically larger group, on your list of groups to worry about?  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 19:39, 6 August 2013 (UTC)\n""]","19:39, 6 August 2013 (UTC)",Whatamidoing (WMF)
+"[':::For gawd\'s sake, this ""20 year old browser"" catchphrase really has the political spin-doctor in you running riot. No one has mentioned anything about a preference for Word Perfect as their preferred word processor... and seriously suspect the average older contributor/editor doesn\'t send off to the MP3 PRO club for for their cracked software. There are a lot of people who don\'t run 64-bit OS\'s simply because their favourite programs & 3rd party plugins are only 32-bit compatible. In itself, that\'s irrelevant as people are going to have to move along whether they prefer to or not. What IS relevant is that what you\'re doing is working on the assumption that the inevitable is here & now and that V/E is capable of accommodating enough platforms, OS\'s & browsers to be backwards compliant within reason & to be able to keep up with advents in the future. Seriously? You haven\'t even managed to debug it enough to get past Alpha phase & you\'ve rolled it out as a Beta system when it can\'t handle anything beyond the most simple tasks. And you\'re seriously expecting that there should be any vote of confidence when, in its present state, it\'s caused a furore. The Tearoom has asked for assistance in handling the queries about the system because they don\'t know their way around it themselves. The Village Pump is about to explode and I\'m still getting <nowiki><nowiki></nowiki> markups just editing pages that contain anything other than straightforward text (god forbid that there be an image floated left for aesthetic purposes because you can\'t get to the wrapped text underneath that div). Take a look at the RFC page. If that isn\'t a vote of no confidence in your brilliant system, I don\'t know what is. The articles look like abortions absolutely dripping with edit source/edit beta/edit me yellow and call me a banana tabs at every subsection when V/E doesn\'t edit subsections. I\'ve been having nightmares about it and, unlike you, I don\'t even get paid to have nightmares about it. <small><span class=""autosigned"">—&nbsp;Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]] • [[Special:Contributions/Iryna Harpy|contribs]]) </span></small><!-- Template:Unsigned -->\n', '* From {{phab|51187}} it isn\'t clear what ""IE\'s non-standard quirk"" (per [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]]) is. I\'m not a MS-apologist (mainly use Chrome myself) but IMO you need to be careful about making ""non-standard"" claims without taking a look at the other side of the coin. Is this in fact a situation where IE doesn\'t follow W3C technical recommendations, or is because there\'s some security thing&mdash;that no-one has standardized&mdash;where IE is giving the user more protection than the other browsers? Maybe that\'s why corporates stick with IE? The headline \'\'""Wikipedia wants editors to lower their security""\'\' probably isn\'t what we need right now. - [[User:Pointillist|Pointillist]] ([[User talk:Pointillist|talk]]) 22:29, 6 August 2013 (UTC)\n']","22:29, 6 August 2013 (UTC)",Pointillist
+"[""*:I believe that a brief inquiry at your favorite web search engine will remove any lingering concerns you might have about IE being more secure than other web browsers, especially if you specifically ask it about IE7, which Luke specifically called out as important in his opinion.  Major websites like Gmail and Google Docs [http://googledocs.blogspot.com/2011/06/our-plans-to-support-modern-browsers.html stopped supporting IE7 two years ago].  In fact, anyone who wants to use [[HTML5]] has stopped supporting IE7, because IE7 can't do HTML5.  A lack of support for IE7 is normal and increasingly expected.  The two typical policies are to drop support for any browser (assuming it requires special efforts) either when it is the third-oldest browser from the company (so support IE9 and 10, but not IE8, and support Firefox 22 and 21, but not 20) or when it reaches a tiny fraction of your traffic.  IE7, at latest count, is responsible for only ~1.5% of desktop/laptop traffic at ''all'' WMF websites (it is probably slightly less here), and dropping steadily.  In contrast, mobile editing (tablets and smartphones) is rising rapidly.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 18:06, 7 August 2013 (UTC)\n""]","18:06, 7 August 2013 (UTC)",Whatamidoing (WMF)
+"[""*::I'm perfectly comfortable with the principle that major new functionality requires an up-to-date browser (sorry, [[User:Lukeno94 |Lukeno94]]!). IE6+7+8 use on wikimedia is [http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm now] down to 6.66% so I can't see any problem excluding them from Visual Editor. I wouldn't even mind excluding IE9 (4.04% used) on the basis that IE11 will be out soon. So we agree almost completely. I'm just questioning whether there's really a W3C standard that applies to {{phab|51187}}. I suspect it's more like Chrome/FF do it one way, and IE does it another way, there's no right or wrong. I didn't mean to imply that ''in general'' IE gives users more security than other browsers, just that perhaps on this occasion IE is enforcing more/different security, because of their focus on corporate use. - [[User:Pointillist|Pointillist]] ([[User talk:Pointillist|talk]]) 11:29, 9 August 2013 (UTC)\n""]","11:29, 9 August 2013 (UTC)",Pointillist
+"[':::*6.66% is still a HUGE amount of people. Add in IE9, and that\'s 10%. Considering that VE is aimed at the non power-users, and those are more likely to be using older browsers (or any version of IE)... [[User:Lukeno94|<span style=""color:navy;"">Luke</span><span style=""color:FireBrick;"">no</span><span style=""color:green;"">94</span>]] [[User talk:Lukeno94#top|<i>(tell Luke off here)</i>]] 11:33, 9 August 2013 (UTC)\n']","11:33, 9 August 2013 (UTC)",Lukeno94
+"[""::::*I do understand your point. I can see the challenge, and I appreciate that non power-users are less likely to upgrade their machines, and some people won't feel comfortable switching browsers from IE to FF or Chrome. But it's also an opportunity to persuade people that the effort is worthwhile and pretty much inevitable if they want to get the most out of the web in future. - [[User:Pointillist|Pointillist]] ([[User talk:Pointillist|talk]]) 12:01, 9 August 2013 (UTC)\n""]","12:01, 9 August 2013 (UTC)",Pointillist
+"[':::::*That\'s an absurd suggestion! Wikipedia shouldn\'t be cherry-picking browsers or users, and it certainly shouldn\'t be promoting any. We\'re talking about 10% of the viewers of Wikipedia here - even 1% is a big enough amount of people for their browsers to need accommodating. At the moment, it must be nearer 20-30% of all users who can\'t use VE, when you take into account Opera, the other versions of IE, and some other, smaller browsers. [[User:Lukeno94|<span style=""color:navy;"">Luke</span><span style=""color:FireBrick;"">no</span><span style=""color:green;"">94</span>]] [[User talk:Lukeno94#top|<i>(tell Luke off here)</i>]] 12:23, 9 August 2013 (UTC)\n']","12:23, 9 August 2013 (UTC)",Lukeno94
+"['::::::*Well, I respect your position. All the best - [[User:Pointillist|Pointillist]] ([[User talk:Pointillist|talk]]) 13:50, 9 August 2013 (UTC)\n']","13:50, 9 August 2013 (UTC)",Pointillist
+"['== Moving misc. discussion ==\n', '\n', 'Hi. Can most of the stuff at [[WP:VE/RFC#Related discussions]] be moved to this talk page? The page is cumbersome to load and follow without every person thinking they need a whole new subsection dedicated to their comments. [[User:Killiondude|Killiondude]] ([[User talk:Killiondude|talk]]) 22:38, 5 August 2013 (UTC)\n']","22:38, 5 August 2013 (UTC)",Killiondude
+"["": I'd second that but am not familiar enough with the RFC process and the rules, if any, involved with maintenance tasks such as moving those discussions to this page. As there are quite a few would that all get appended to the bottom of this page? Should they be replaced with links to the discussion on this page? --[[User:Marc Kupper|Marc Kupper]]&#124;[[User talk:Marc Kupper|talk]] 20:06, 6 August 2013 (UTC)\n""]","20:06, 6 August 2013 (UTC)",Marc Kupper
+"['== problem with numbered votes in opt-out for question 1 ==\n', '\n', 'I added my vote to the opt-out section of the first question, [http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Default_State_RFC#Opt-out at the very end of this], but it restarted the numbering at 1.  I think it has something to do with the comment of the humble editor above me, but I don\'t know exactly what the problem is or how to fix it.  Any ideas?  Thanks!  [[User:Agnosticaphid|<span style=""color:DarkGreen;"">AgnosticAphid</span>]] [[User talk:agnosticaphid|talk]] 06:16, 6 August 2013 (UTC)\n']","06:16, 6 August 2013 (UTC)",agnosticaphid
+"[':Fixed. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 06:48, 6 August 2013 (UTC)\n']","06:48, 6 August 2013 (UTC)",NicoV
+"['::Hey, thanks. Those are some strange nowiki tags on that page you posted! But I think the problem is that whoever that was accidentally didn\'t select the whole name when they made the intra-wiki link, and then the VE added a nowiki tag because if you add a single letter to the end of a link, like <nowiki>""[[thi]]s""</nowiki> it would ordinarily show up as part of the link, like [[thi]]s.  So VE was just trying to preserve the mistaken edit!  I mean, they probably meant to link <nowiki>[[Dostoievski]] rather than [[Dostoievsk]]i.</nowiki>  So it seems like more of a typo than a bug to me, personally. I do know there are actual problems with tables, though! [[User:Agnosticaphid|<span style=""color:DarkGreen;"">AgnosticAphid</span>]] [[User talk:agnosticaphid|talk]] 07:02, 6 August 2013 (UTC)\n']","07:02, 6 August 2013 (UTC)",agnosticaphid
+"["":::Yes, it was accidental but VE behaviour is surely not what the editor intended to do. An other possibility for this is that the user tried a spelling, and when he added the link he saw that the spelling was wrong so he fixed the spelling just after adding the link. There are a lot of other situations where VE add nowiki tags (see abuse filter 550 which is still triggered several hundred times a day) which are not intended by the user, or that VE trashes an article (tables, ...). There's also the possibility to delete a template without intending to and being aware that you did it. It's all these problems that make me vote for opt-in because a novice won't know that garbage has been added to the article. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 09:24, 6 August 2013 (UTC)\n""]","09:24, 6 August 2013 (UTC)",NicoV
+"['== Changing the user preference label ==\n', '\n', ""Hi. I've begun a discussion at [[MediaWiki talk:Visualeditor-preference-betatempdisable#Changing this message]] to discuss whether we should change the user preference label that completely disables VisualEditor. Please participate there. --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 06:53, 6 August 2013 (UTC)\n""]","06:53, 6 August 2013 (UTC)",MZMcBride
+"['== Comment on the process ==\n', '\n', 'Generally when a topic is under discussion people are discouraged from making significant changes to the topic until the discussion is concluded. In this case, the RFC was started July 30 01:24<sup>[http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Default_State_RFC&dir=prev&action=history]</sup> and at 2 August 2013 05:22 the developers rolled out [[Wikipedia:VisualEditor/Updates/August 1, 2013]] to this site. It appears many of the changes in this rollout were in response to early feedback on the RFC. \n', '\n', ""While it's great that there was a near immediate response from the software developers it also means that some of the questions in the RFC are no longer valid as they are about VE's behavior in July. \n"", '\n', 'Should the RFC be kept open? \n', '\n', ""There's a secondary issue which is I found the July version of VE to be so disruptive that I had disabled it. I see from the RFC comments that many others had also disabled VE for the same reason I had. I learned about the August update when reading the RFC comments, re-enabled VE, and have left it enabled. Should a site-notice go out to editors that still have VE disabled about the August update? --[[User:Marc Kupper|Marc Kupper]]&#124;[[User talk:Marc Kupper|talk]] 20:04, 6 August 2013 (UTC)\n""]","20:04, 6 August 2013 (UTC)",Marc Kupper
+"["": I think the whole process is correct. By enabling the VE to a wider audience, there is A, more feedback and B, more motivation of others to provide input/help with development (it is, after all, open source, and its more interesting for many developers to work on a popular application than on some test program which might never even be used). So the wider deployment of the VE in fact accelerates its development, and I therefore guess that soon all 'major' issues will be solved. I'd say its a ''post modern'' kind of process :) -- [[User:Stratoprutser|Stratoprutser]] ([[User talk:Stratoprutser|talk]]) 21:59, 6 August 2013 (UTC)\n""]","21:59, 6 August 2013 (UTC)",Stratoprutser
+"['::Some of the more important problems are difficult to solve and will take a while, but I am looking forward to the next update, which might happen as early as 15 August.  Among other things, it is supposed to halve the ""nowiki"" problem (which has already declined substantially during the last month).  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 18:10, 7 August 2013 (UTC)\n']","18:10, 7 August 2013 (UTC)",Whatamidoing (WMF)
+"['== Further reading ==\n', '\n', 'There\'s a raucous but very informative (and very long) thread about the VE introduction and the problems with it [http://wikipediocracy.com/forum/viewtopic.php?f=8&t=2616 on Wikipediocracy] (a site dedicated to critiquing (or perhaps destroying) all things Wikipedian). A few of the folks posting to the thread are in the software development industry, and their views on this release might help put this in context a bit. It\'s a very long forum thread, but probably not quite as long as the RfC. --[[User talk:SB_Johnny|<span style=""color:green;"">\'\'\'SB_Johnny\'\'\'</span>]]&nbsp;&#124;&nbsp;<sup>[[User_talk:SB_Johnny|<span style=""color:green;"">talk</span>]]</sup>✌ 23:02, 6 August 2013 (UTC)\n']","23:02, 6 August 2013 (UTC)",SB_Johnny
+"[': Cheers for the link. Distinctly illuminating! --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 22:46, 7 August 2013 (UTC)\n']","22:46, 7 August 2013 (UTC)",Iryna Harpy
+"['== Page length ==\n', '\n', 'At time of writing, the RFC page stands at nearly 850,000 bytes (850kB) and growing. Would this make it the longest page ever on Wikipedia?\n', '\n', 'On a serious note though, the RFC should be closed soon, or the page size will grow towards an unacceptable level. [[User:Insulam Simia|Insulam Simia]] ([[User talk:Insulam Simia|talk]]) 12:23, 7 August 2013 (UTC)\n']","12:23, 7 August 2013 (UTC)",Insulam Simia
+"[':The page is already beyond critical mass (about 500K for some browsers). I do also agree its time for this RFC to close and the WMF to act on consensus. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 20:38, 7 August 2013 (UTC)\n']","20:38, 7 August 2013 (UTC)",KumiokoCleanStart
+"['\n', ': This RFC was opened 30 July. After 7 days, one would expect everyone with an opinion on this matter has spoken. I doubt any further light or insight will come into this discussion. -- [[User:Llywrch|llywrch]] ([[User talk:Llywrch|talk]]) 21:26, 7 August 2013 (UTC)\n']","21:26, 7 August 2013 (UTC)",Llywrch
+"['== Its time to present this to the WMF for action ==\n', '\n', 'Now that we have an RFC which shows the WMF clerly what the consenus for how to deal with Visual Editor its time someone presents it to them for action. Hundreds of people voted in this RFC which is, in and of itself, a sign that Visual Editor has caught people attention. The community clearly feels that VE needs to be disabled to opt in only and a variety of other changes until it is fixed and working. Excuse my rather blunt tone here, because it should have never came to this in the first place but its time for the WMF to step up and do as consensus reflects. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 20:36, 7 August 2013 (UTC)\n']","20:36, 7 August 2013 (UTC)",KumiokoCleanStart
+"[':I seriously doubt that anything can be done before the developers have returned from Wikimania.  There is a code freeze in effect until August 15th.  \n', "":I have no opinion on whether this should be closed, or left open for other people, or split into subpages, or anything else.  However, if you wanted to help speed the process along, then you might help find a team of experienced, uninvolved admins to formally close it.  If the decision makers have to find time to read through 850K of comments and figure out which ones pre-date James F's proposal and might be addressed by those changes, then the decision will necessarily be delayed by however many hours that takes them.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 22:43, 7 August 2013 (UTC)\n""]","22:43, 7 August 2013 (UTC)",Whatamidoing (WMF)
+"['::I agree we may as well keep it going until after Wikimania and that it might take a while to read through. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 23:29, 7 August 2013 (UTC)\n']","23:29, 7 August 2013 (UTC)",KumiokoCleanStart
+"['::Certainly you aren\'t suggesting that all votes from before the edit buttons were swapped out should be discarded, are you, [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]]? Everything James has done was relevant only to question 4, and they pretty unambiguously satisfied the demand to ""Explicitly warn that it is beta software"".  It was irrelevant to the other questions. Ratios like 465/110, 254/57, and 179/46 are pretty unambiguous. Only questions 2.5 and 5 have any judgment calls. &mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 03:04, 9 August 2013 (UTC)\n']","03:04, 9 August 2013 (UTC)",Kww
+"[':::I don\'t think that anything should be discarded wholesale.  However, a thoughtful close will consider the comments that a person made and not just the ""vote"", and it will consider which people\'s suggestions or comments have been addressed on individual questions.  [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 17:01, 9 August 2013 (UTC)\n']","17:01, 9 August 2013 (UTC)",Whatamidoing (WMF)
+"["":*'''Agreed''', present to the WMF for action.  [[User:N2e|N2e]] ([[User talk:N2e|talk]]) 13:40, 9 August 2013 (UTC)\n""]","13:40, 9 August 2013 (UTC)",N2e
+"['\n', '* RFCs typically last thirty days. This would mean that this discussion (or vote) would end on August 29 or August 30, I believe.<br>RFCs also typically have a formal closing. This requires an established user (admin or otherwise) reading through the discussion and writing a closing statement. As WhatamIdoing suggests, a group of users closing this RFC may make sense here. --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 21:07, 12 August 2013 (UTC)\n']","21:07, 12 August 2013 (UTC)",MZMcBride
+"[""::*You don't think [[WP:SNOW]] applies to this one, [[User:MZMcBride|MZMcBride]]? The problem with your approach is that if we wait another two weeks to start some formal multi-admin close, by the time we are done, Erik is going to claim that he's done so much since the RFC started that he no longer views the RFC results as valid, meaning we would need to do this over again, and every time we came to the close, the results would be rejected due to age. There's such an intensely lopsided result here that there's no benefit in waiting, and every day we wait is another day that the software is misconfigured to enable VE by default to new editor and IPs.&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 01:21, 16 August 2013 (UTC)\n""]","01:21, 16 August 2013 (UTC)",Kww
+"[""::** My only thought at this point is that I'm too involved to have an objective opinion on this RFC or any discussion or decision related to it. :-)  --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 03:13, 16 August 2013 (UTC)\n""]","03:13, 16 August 2013 (UTC)",MZMcBride
+"[""*I think this RfC has run its main course. I haven't noticed any new sections or what not popping up lately. [[User:Cncmaster|Command and Conquer Expert!]] <sup>[[User talk:Cncmaster|speak to me...]]</sup><sub>[[Special:Contributions/Cncmaster|review me...]]</sub> 22:40, 12 August 2013 (UTC)\n""]","22:40, 12 August 2013 (UTC)",Cncmaster
+"[':*I completely agree and I think we need someone to lose this out and submit it to the WMF. I believe its probable they will tell us that we cannot tell them what to do, which has been the basic argument from day one. But I think we at least need to show the that the community has come to a consensus about some issues pertaining to Visual editor. They can choose to follow the consensus of the community or continue to spit in the communities face. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 03:39, 16 August 2013 (UTC)\n']","03:39, 16 August 2013 (UTC)",KumiokoCleanStart
+"["":* Agree also. I don't know how to close a RFC on enwiki, so I will let other people do it. The result of the RFC is pretty clear, at least for questions 1, 2 and 3. To me it doesn't seem that anything that has happened since the beginning of this RFC should change much in the votes (a lot of votes are explained by the beta status). We'll see if WMF will keep disregarding the community or if they finally decide to work more closely with contributors. --[[User:NicoV|NicoV]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 17:02, 17 August 2013 (UTC)\n""]","17:02, 17 August 2013 (UTC)",NicoV
+"[':*I know how to close it but I think an argument could reasonably be made, based on my comments and activity, that I am too involved. I am going to request an uninvolved admin to stop by and see if anyone is willing. If no one is willing I will try and find time later in the week. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 01:02, 18 August 2013 (UTC)\n']","01:02, 18 August 2013 (UTC)",KumiokoCleanStart
+"["":*:A request was made at AN [[Wikipedia:Administrators%27_noticeboard/Archive252#Wikipedia:VisualEditor.2FDefault_State_RFC|here]] but does not seem to have attracted much attention.  My guess is that with so many people on vacation this time of year, there just weren't many people willing to do the entire thing by themselves.  One way to reduce the workload is to find a team, rather than dumping everything on one person.  Three is typical for an RFC of this size, although one per 'question' and someone else for the additional proposals is another option that might work here.  [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 01:08, 18 August 2013 (UTC)\n""]","01:08, 18 August 2013 (UTC)",WhatamIdoing
+"["":**Thank you I hadn't noticed that. I just left a note for Arbcom to consider drafting the results for submission to the WMF. The request can be seen [[Wikipedia talk:Arbitration Committee/Noticeboard#Closing statement for RFC on Visual Editor|here]]. I admit its a little outside the scope of the Arbcom but as the defacto legal body for Wikipedia and the intermediary between the WMF and the community, it seemed reasonable that they should do it since it pertains to a WMF decision. We'll see what they say. Otherwise I don't mind helping on it but as I said above I believe it would open the door for debate because I have been so vocally opposed to several aspects of VE. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 01:23, 18 August 2013 (UTC)\n""]","01:23, 18 August 2013 (UTC)",KumiokoCleanStart
+"["":***As expected the Arbcom has declined to get involved so I guess we need a couple folks to close this out and submit the results. Any takers? It doesn't require an admin but someone with some experience with RFC's would be good. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 15:23, 27 August 2013 (UTC)\n""]","15:23, 27 August 2013 (UTC)",KumiokoCleanStart
+"["":***I submited for the RFC to be closed [[Wikipedia:Administrators' noticeboard/Requests for closure#Wikipedia:VisualEditor/Default State RFC|here]]. If no one bites in the next few days I'll probably draft something up and then post something here for review. [[User:KumiokoCleanStart|Kumioko]] ([[User talk:KumiokoCleanStart|talk]]) 15:32, 27 August 2013 (UTC)\n""]","15:32, 27 August 2013 (UTC)",KumiokoCleanStart
+"['== Comparing the RfC results to the WMF reply ==\n', '\n', ""Let's discuss this step by step (WMF, please elaborate or correct what I present here as your replies), to get a better idea of where the perceived breakdown between the RfC (the community wishes) and the WMF (the fiat from above) is real and what can be done to minimize this gap. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 07:57, 13 September 2013 (UTC)\n""]","07:57, 13 September 2013 (UTC)",Fram
+"['== Motion to close ==\n', ""This is a done deal. I don't think anyone should bother with more input on this page. En:wp has far too much editing time needed in other places.--[[User:Canoe1967|Canoe1967]] ([[User talk:Canoe1967|talk]]) 18:42, 18 September 2013 (UTC)\n""]","18:42, 18 September 2013 (UTC)",Canoe1967
+"[':The RFC was closed on the 8th. &mdash;[[User_talk:Rybec|<span style=""color:black;""><span style=""background:#ccccff"">rybec</span></span>]] 18:32, 21 September 2013 (UTC)\n']","18:32, 21 September 2013 (UTC)",Rybec
+"[""::Precisely, Rybec: ''this'' RfC is closed. What it has revealed is that a much larger core issue has arisen revolving around the question of the RfC being presented for community input ''before'' even putting the question of the desirability of using agile programming as a reasonable method by which to develop VE. Additional comments on the RfC made it abundantly clear that the 'wrong questions' were being posed. The fact remains that VE is still buggy, yet the determination by the WMF to make executive decisions about what is desirable and what is undesirable ''despite'' community concerns should not be considered done and dusted. Getting on with editing has been compromised and complicated by the rolling out of a flawed system still in the process of being developed in an undesirable way, [[User:Canoe1967|Canoe1967]]. --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 01:33, 22 September 2013 (UTC)\n""]","01:33, 22 September 2013 (UTC)",Iryna Harpy
+"[""== James Forrester's remarks  ==\n"", '\n', ""The response to this RFC should be posted to every person's talk page who voted in this RFC.\n"", 'He should stand by his words. [[User:ChrisOBucket|ChrisOBucket]] ([[User talk:ChrisOBucket|talk]]) 03:07, 21 September 2013 (UTC)\n']","03:07, 21 September 2013 (UTC)",ChrisOBucket
+"['== Discussion of proposal to implement outcome of RFC via admin action ==\n', '\n', ""Participants of this RFC may be interested in the ongoing Admin Noticeboard thread [[Wikipedia:Administrators'_noticeboard/Archive253#Comments_requested_before_I_implement_consensus_at_WP:VisualEditor.2FDefault_State_RFC]]. The thread centers around a proposal to implement VE opt-in for new users via a local, administrative action (changing a global Javascript file.) [[User:OSborn|OSborn]] <sup>[[User_talk:OSborn|arf]]</sup><sub>[[Special:Contributions/OSborn|contribs.]]</sub> 04:52, 23 September 2013 (UTC)\n""]","04:52, 23 September 2013 (UTC)",OSborn
+"['\n', '[[Image:Stop hand nuvola.svg|30px|alt=Stop icon]] <big>Please stop and \'\'\'think\'\'\' before entering that discussion. If your contribution is going to be something on the line of ""Please do this because WMF Employee so-and-so is a jerk/dickwad/whatever"", then \'\'please don\'t contribute at all\'\'. If this goes forward, the responsibility is going to lie heavily upon my shoulders. I don\'t want people to be pointing and saying that the consensus was flawed because it included input from angry hateful people. If you contribute, contribute calmly.</big>&mdash;[[User:Kww|Kww]]([[User talk:Kww|talk]]) 05:39, 23 September 2013 (UTC)\n']","05:39, 23 September 2013 (UTC)",Kww
+"["":Point well made, {{U|Kww}}. In the first instance, it would be incorrect to present you as having encouraged ill-advised mutiny. Your point has been clear from the outset: to ask the WMF to account to users/editors/contributors who have expressed serious and valid reservations surrounding the method of and rolling out of VE. To use another forum in order to resort to bitching would be counterproductive (surely the ongoing debates are an attempt to open a reasonable dialogue with them). To put you in a precarious position which doesn't reflect your true concerns would be downright irresponsible of the 'disgruntled' elements of the community. --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 06:46, 23 September 2013 (UTC)\n""]","06:46, 23 September 2013 (UTC)",Iryna Harpy
+"['== RFC: VisualEditor launch issues ==\n', '{{Archive top|result= Before I close this, let me state a few things. First, I have an opinion on some aspects of VisualEditor (VE), which is probably known to most regulars in these debates. Second, I\'m one of the only regulars left to check VE and give feedback on it. This combination makes me either highly involved and unsuitable as a closer, or sufficiently neutral to be acceptable as a closer. I think I can be neutral enough to close this objectively (and I don\'t see others rushing to close it anyway), but feel free to overturn the close if it is too problematic anyway. Finally, much in this RfC is no longer applicable, things have evolved a lot in the past few months and after the other RfC, but it still has value to close this RfC and list the results. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 09:49, 24 October 2013 (UTC) \n*""1. VisualEditor is a good idea in theory"": there is \'\'\'clear support\'\'\' for this, most people agree that a Visual Editor is in itself a good idea.\n*""2. Buggy software should not become the default until it reaches a certain level of development."": \'\'\'clear support\'\'\' for this as well.\n*""3. VisualEditor should have a way to be turned off fully, easily, and without continuing to leech resources"": very \'\'\'clear support\'\'\' for this as well (not applicable at the moment, but something that should be taken into account if and when the opt-in is changed back to opt-out)\n*""4. The manner of the launch was unduly aggressive"": There is \'\'\'support\'\'\' for this, but with many people feeling that the launch was badly handled but that perhaps ""agressive"" is not the right word. \n*""5. This survey should have been begun by the VisualEditor team"": \'\'\'no consensus\'\'\'\n*""6. Wikimedia should disable this software by default"": this has \'\'\'clear support\'\'\' (like at the other RfC), and the WMF has in the meantime been forced to do this. \n*""7. VisualEditor, as currently deployed, is a useful feature"": \'\'\'clear opposition\'\'\' against this point\n*""8. Flow should support markup editing"": while perhaps badly placed in this RfC, it has \'\'\'clear support\'\'\'. \n}}\n']","09:49, 24 October 2013 (UTC)",Fram
+"[""<includeonly>\n:''This section is transcluded from [[Wikipedia:VisualEditor/RFC]]</includeonly>\n"", 'This is an RFC regarding the issues surrounding the deployment of VisualEditor. [[User:Gigs|Gigs]] ([[User talk:Gigs|talk]]) 17:03, 16 July 2013 (UTC)\n']","17:03, 16 July 2013 (UTC)",Gigs
+"['==Great work==\n', ""*Great work MediaWiki/Wikipedia team on the new editor.  This will allow Wikipedia to remain relevant in the current 'state of the web' where editing experiences like this are expected.  I was very impressed to see the implementation of the Reference editor and 'Transclusion' editor.  Features like those would have been easy to set aside for a Version 2.0, but a more comprehensive release really may start a positive trend.  No doubt technical issues like browser compatibility or differences of opinion on exact layout will arise and be resolved as part of the development as they have always been.  Please keep up the great work![[User:Cander0000|Cander0000]] ([[User talk:Cander0000|talk]]) 08:52, 11 July 2013 (UTC)\n""]","08:52, 11 July 2013 (UTC)",Cander0000
+"['*Given the scope of the problem (and just how horribly messed-up wikitext really is), it is actually very good, and easier for quick copyedits on complicated articles. And I know how damn hard everyone involved is working on it - [[User:David Gerard|David Gerard]] ([[User talk:David Gerard|talk]]) 16:32, 11 July 2013 (UTC)\n']","16:32, 11 July 2013 (UTC)",David Gerard
+"['\n', ""*Despite the fact that I'm not entirely happy with the way this has been deployed (frankly, it went far too early, before it was ready), I think we also need to acknowledge that putting together a Visual Editor is both the single most important technical thing that can be done to attract and retain new editors, and also one of the most difficult software engineering challenges possible.  Building something as functional as what we have on top of the years of adhoccery and legacy code that makes up Mediawiki and the English Wikipedia is an extremely impressive feat.  [[User:Lankiveil|Lankiveil]] <sup>([[User talk:Lankiveil|speak to me]])</sup> 11:44, 16 July 2013 (UTC).\n""]","11:44, 16 July 2013 (UTC)",Lankiveil
+"['**+1 --[[User:3family6|<span style=""color:navy;"">&iquest;3fam</span>]]\'\'\'\'\'[[User talk:3family6|<span style=""color:black;"">ily6</span>]]\'\'\'\'\' <sub>[[Special:Contributions/3family6|<span style=""color:purple;"">contribs</span>]]</sub> 13:44, 16 July 2013 (UTC)\n']","13:44, 16 July 2013 (UTC)",3family6
+"[""** I completely agree. I'm glad this new editor has been rolled out. [[User:Chogg|Chogg]] ([[User talk:Chogg|talk]]) 20:08, 16 July 2013 (UTC)\n""]","20:08, 16 July 2013 (UTC)",Chogg
+"['* I agree. It\'s a very good alpha, but it should never have been launched outside of a test deployment. <span style=""text-shadow:grey 0.118em 0.118em 0.118em; class=texhtml"">\'\'\'[[User:Adam Cuerden|Adam Cuerden]]\'\'\' <sup>([[User talk:Adam Cuerden|talk]])</sup></span> 12:04, 16 July 2013 (UTC)\n']","12:04, 16 July 2013 (UTC)",Adam Cuerden
+"[""*:I don't think it's up to alpha yet, as some of the critical enhancements have been marked WONTFIX. — [[User:Arthur Rubin|Arthur Rubin]]  [[User talk:Arthur Rubin|(talk)]] 19:25, 4 August 2013 (UTC)\n""]","19:25, 4 August 2013 (UTC)",Arthur Rubin
+"[""* This is something Wikipedia has needed for a long time, and I'm happy it's already available on every article.  I'm amazed at how complete it is. — [[User:Omegatron|Omegatron]]&nbsp;([[User talk:Omegatron|talk]]) 03:08, 3 August 2013 (UTC)\n""]","03:08, 3 August 2013 (UTC)",Omegatron
+"['==Comment about this RfC==\n', 'This RfC was designed with many weasel words, false choices, and questionable assumptions. This needs to be redone in a proper way to claim any sort of true consensus. -- [[User:Ypnypn|Ypnypn]] ([[User talk:Ypnypn|talk]]) 19:16, 11 July 2013 (UTC)\n']","19:16, 11 July 2013 (UTC)",Ypnypn
+"[""*'''Disagree''' I don't believe it comes across that way. I suppose it could be re-written to have a better effect, but there is no harm in it now.  But unlike the Visual Editor, this RFC can be improved as we go along just like any article or essay.  If you have better wording, mention them.  I believe this RFC was brought forward in good faith.--[[User:Paulmcdonald|Paul McDonald]] ([[User talk:Paulmcdonald|talk]]) 19:31, 11 July 2013 (UTC)\n""]","19:31, 11 July 2013 (UTC)",Paulmcdonald
+"['* So add a section more to your liking - [[User:David Gerard|David Gerard]] ([[User talk:David Gerard|talk]]) 19:51, 11 July 2013 (UTC)\n']","19:51, 11 July 2013 (UTC)",David Gerard
+"['::So I have. -- [[User:Ypnypn|Ypnypn]] ([[User talk:Ypnypn|talk]]) 20:56, 11 July 2013 (UTC)\n']","20:56, 11 July 2013 (UTC)",Ypnypn
+"['*I think Ypnypn has a point, it looks seriously biased to me, (not necessarily in bad faith though) but I think it is in any case a storm in a teacup, so to mix my metaphors, I will not fan the flames. &bull; &bull; &bull; [[User:Pbsouthwood|Peter (Southwood)]] [[User talk:Pbsouthwood|<sup>(talk)</sup>]]: 20:14, 11 July 2013 (UTC)\n']","20:14, 11 July 2013 (UTC)",Pbsouthwood
+"[""*Must say I didn't like the language used, which has detracted from its intended purpose.--[[User:Salix alba|Salix]] ([[User talk:Salix alba|talk]]): 21:57, 11 July 2013 (UTC)\n""]","21:57, 11 July 2013 (UTC)",Salix alba
+"[""*'''Agree''' but also support this RfC.  VE is not a bad idea, but it is not a sufficiently good implementation of that idea.  The RfC is another poor implementation of a good idea (re-evaluating the implementation of VE). --[[User:R.S. Peale|R.S. Peale]] ([[User talk:R.S. Peale|talk]]) 05:24, 12 July 2013 (UTC)\n""]","05:24, 12 July 2013 (UTC)",R.S. Peale
+"['*I have not commented in the RFC although I have already added several comments in the main discussion. As one of the MANY editors who are currently unable to use VE because our browsers (Opera in my case) are unsupported I do not feel I am in a position to do so. I can see the point in VE for new editors if it is done properly, but at the moment it clearly has not been. That all versions of IE are currently unsupported really means it is not fit for release in its current state, are they really serious about it..? [[User:Dsergeant|Dsergeant]] ([[User talk:Dsergeant|talk]]) 06:19, 12 July 2013 (UTC)\n']","06:19, 12 July 2013 (UTC)",Dsergeant
+"['*:Browser support is somewhat irrelevant in relation to breakage simply because ""unsupported"" means ""blacklisted"". An IE user is not given the VE, just as you\'re not given the VE; pushing a version out makes absolutely no impact on them, positive or negative. [[User:Okeyes (WMF)|Okeyes (WMF)]] ([[User talk:Okeyes (WMF)|talk]]) 14:36, 12 July 2013 (UTC)\n']","14:36, 12 July 2013 (UTC)",Okeyes (WMF)
+"['*::""Many"" is less than 20%, and that will be less than 10% soon, when IE 9, 10, and 11 are working properly.  [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 00:10, 13 July 2013 (UTC)\n']","00:10, 13 July 2013 (UTC)",WhatamIdoing
+"['*::: 80% of visitors to wikimedia sites use a browser other than IE, I think that editors are somewhere around 90% using something other than IE. [https://en.wikipedia.org/wiki/Usage_share_of_web_browsers] also, many other features online do not initially support IE, and some never do, possibly due to the difference in programming and function. -- [[user:aunva6|Aunva6]]<sup>[[user talk:aunva6|talk]] - [[Special:Contributions/Aunva6|contribs]]</sup>  21:11, 13 July 2013 (UTC)\n']","21:11, 13 July 2013 (UTC)",Aunva6
+"['*::::I use IE primarily because of [[WP:AWB|AWB]].  — [[User:Arthur Rubin|Arthur Rubin]]  [[User talk:Arthur Rubin|(talk)]] 22:46, 13 July 2013 (UTC)\n']","22:46, 13 July 2013 (UTC)",Arthur Rubin
+"['*::: When I do training, we often rely on the participants bringing their own equipment.  I\'m a big fan of Firefox, but ""you\'ll have to install Firefox in order to participate in this workshop"" is unprofessional, and ""you\'ll have to upgrade to a newer version of IE"" is even worse because it will likely cause all sorts of unexpected changes to their computer.  In many cases, their laptop is their work machine, and is locked down so they cant f&^k it up.  VE should work on most normal configurations, and IE users are slow upgraders.  20% is a very high risk factor.  And I can assure you that even when it is 10%, it will cause problems often, especially with outreach to GLAMs and government and even universities in first world countries, and will be very frequently a problem in developing countries that cant afford to regularly upgrade.  <span style=""font-variant:small-caps"">[[User:John Vandenberg|John Vandenberg]] <sup>\'\'\'([[User talk:John Vandenberg|chat]])\'\'\'</sup></span> 08:40, 18 July 2013 (UTC)\n']","08:40, 18 July 2013 (UTC)",John Vandenberg
+"['*The opening statement is terrible, and Philippe is absolutely right. The rest of the RFC is OK because we can at least oppose the statements we disagree with, but the opening statement really needs to be made more neutral and level-headed. — <span style=""border:dashed #666;border-width:1px 0 0 1px"">[[User:This, that and the other|This, that]]</span> and <span style=""border:dashed #666;border-width:0 1px 1px 0"">[[User talk:This, that and the other|the other<small> (talk)</small>]]</span> 07:10, 12 July 2013 (UTC)\n']","07:10, 12 July 2013 (UTC)","This, that and the other"
+"['*I don\'t think this RFC really needs to come to any kind of definitive consensus.  The feedback here is not conducive to coming to some sort of ""grand conclusion"", or closure.   It\'s clear that the general consensus of the community is that the rollout could have been handled a little better, but that\'s done and over with, so kind of moot. As I like to say, RFC is not a code word for polling, and the RFC still has value in the individual comments, even if there can be no ""result"". [[User:Gigs|Gigs]] ([[User talk:Gigs|talk]]) 14:27, 12 July 2013 (UTC)\n']","14:27, 12 July 2013 (UTC)",Gigs
+"['**I think that is only one of the points.  There are editors in favor of rolling back the project, making VE not be the ""default"" editor at this time, and pulling VE completely from Wikipedia.  It\'s more than just ""the rollout could have been handled a little better"" as you say, it\'s a whole lot more.  ""Sweep it under the rug"" is not an option.--[[User:Paulmcdonald|Paul McDonald]] ([[User talk:Paulmcdonald|talk]]) 18:07, 12 July 2013 (UTC)\n']","18:07, 12 July 2013 (UTC)",Paulmcdonald
+"[""*But it's still better planned/designed than the Visual Editor rollout was. [[User:Hullaballoo Wolfowitz|Hullaballoo Wolfowitz]] ([[User talk:Hullaballoo Wolfowitz|talk]]) 13:40, 14 July 2013 (UTC)\n""]","13:40, 14 July 2013 (UTC)",Hullaballoo Wolfowitz
+"['** +1 - [[User:David Gerard|David Gerard]] ([[User talk:David Gerard|talk]]) 14:15, 14 July 2013 (UTC)\n']","14:15, 14 July 2013 (UTC)",David Gerard
+"['** +2 - [[User:Double sharp|Double sharp]] ([[User talk:Double sharp|talk]]) 11:57, 15 July 2013 (UTC)\n']","11:57, 15 July 2013 (UTC)",Double sharp
+"['*\'\'\'Agree\'\'\': The RFC summary was not at all neutral, and Adam certainly seems to have tried to steer the discussion in a particular direction.--[[User:3family6|<span style=""color:navy;"">&iquest;3fam</span>]]\'\'\'\'\'[[User talk:3family6|<span style=""color:black;"">ily6</span>]]\'\'\'\'\' <sub>[[Special:Contributions/3family6|<span style=""color:purple;"">contribs</span>]]</sub> 13:43, 16 July 2013 (UTC)\n']","13:43, 16 July 2013 (UTC)",3family6
+"['**I changed it, not that it matters much at this point. [[User:Gigs|Gigs]] ([[User talk:Gigs|talk]]) 17:03, 16 July 2013 (UTC)\n']","17:03, 16 July 2013 (UTC)",Gigs
+"[""*Indeed it may come across as biased. But how many would have voted differently if it had been more neutral? How many seem to have been influenced by the tone of the initial statements (i.e. they had no reasons of their own)? I'm guessing very few. [[User:Double sharp|Double sharp]] ([[User talk:Double sharp|talk]]) 11:37, 19 July 2013 (UTC)\n""]","11:37, 19 July 2013 (UTC)",Double sharp
+"["":::Exactly. The questions just format and divide up the discussion. He hardly had to steer.  Everyone here knows what we are talking about by experience, without relying on them to tell us what's going on. I can think no way of asking the question that would give a significantly different response. The great majority except those connected with the WMF dislike it and think it unready, the only variation being the degree of dislike; everyone from  the WMF thinks it's useful, though some also think it wasn't ready.  For example, I'm more willing to tolerate editing systems I don't like than Adam is,  perhaps because I've managed to work with most of what's come out in the last 40 years or so (even earlier--I think I remember having to work with text in FortranIV). If I had to edit everything twice to make sure it worked, I would edit it twice, but that doesn't mean I want to.  '''[[User:DGG| DGG]]''' ([[User talk:DGG| talk ]]) 03:12, 20 July 2013 (UTC)\n""]","03:12, 20 July 2013 (UTC)",DGG
+"["":::RfCs have become the way the enWP decides things. What I think we need to think about is how long to give the developers until we  have one on the simple question of having it permanently removed until we say otherwise. My goodwill was exhausted at the previous interface change: I was assured the foundation had learned something, and I see that is not the case. And to supplement it, I see below they're intent on a similar change without approval. It's like a returning sockpuppet, who posts that after we throw him out he's going to come back again.'''[[User:DGG| DGG]]''' ([[User talk:DGG| talk ]]) 03:19, 20 July 2013 (UTC)\n""]","03:19, 20 July 2013 (UTC)",DGG
+"['* \'\'\'Agree\'\'\'. Adam Cuerden\'s original summary is not the only problem. With bullet points like ""it\'s a good idea \'\'in theory\'\'"" and ""Buggy software should not become the default until it reaches a certain level of development"", Adam is basically asking us all whether we\'ve stopped beating our wives. Points like ""VisualEditor should have a way to be turned off fully, easily, and without continuing to leech resources"" are based on presumptions (that VE imposes a burden even when turned off) that are simply not backed up by the facts. Where do those of us who think that the VE is at an acceptable level of quality, and should be deployed to all editors, put their opinions in this mess? [[User:Dcoetzee|Dcoetzee]] 02:27, 2 August 2013 (UTC)\n']","02:27, 2 August 2013 (UTC)",Dcoetzee
+"['** \'\'\'Agree\'\'\' I\'m only posting beneath Dcoetzee because they said it better than I ever could. The whole thing seems designed as a politicking power-play by a vocal minority of long term users. --[[User:Monk of the highest order|<span style=""color:green;"">Monk of the highest order</span>]]<sup>[[User talk:Monk of the highest order|(t)]]</sup> 04:28, 12 August 2013 (UTC)\n']","04:28, 12 August 2013 (UTC)",Monk of the highest order
+"['*Disagree. The RFC looks properly presented to me. [[User:Gryllida|Gryllida]] 09:17, 6 August 2013 (UTC)\n']","09:17, 6 August 2013 (UTC)",Gryllida
+"['== Visual Editor and Flow ==\n', '\n', ""It's official - [https://www.mediawiki.org/wiki/Talk:Flow_Portal/Interactive_Prototype#Markup-mode_.2Aneeded.2A_in_editor_30315] - you won't be able to use talk pages without it. This appears to put the lie to claims it will remain optional - [[User:David Gerard|David Gerard]] ([[User talk:David Gerard|talk]]) 22:26, 14 July 2013 (UTC)\n""]","22:26, 14 July 2013 (UTC)",David Gerard
+"[':Someone at the WMF needs to seriously take on board all the complaints they\'re getting and stop everything related with VE until they can fix the most egregious bugs it has. As it is, the way this is going on is a joke, and I won\'t be surprised if we see a few people getting fired over this fiasco. —[[User:Jéské Couriano|<span style=""color:#228B22;"">\'\'Jeremy\'\'</span>]] [[User talk:Jéské Couriano|<span style=""color:#228B22;"">v^_^v</span>]] <sup><small>[[Special:Contributions/Jéské Couriano|Bori!]]</small></sup> 23:59, 14 July 2013 (UTC)\n']","23:59, 14 July 2013 (UTC)",Jéské Couriano
+"[':Agreed.--[[User:Paulmcdonald|Paul McDonald]] ([[User talk:Paulmcdonald|talk]]) 00:14, 15 July 2013 (UTC)\n']","00:14, 15 July 2013 (UTC)",Paulmcdonald
+"[""::That thread does not say that VE will be the only way to use talk pages.  In fact, if you read [[:mw:Thread:Talk:Flow Portal/Interactive Prototype/Markup-mode *needed* in editor/reply (12)]], it specifically says that there will be a fallback, i.e., for users who ''cannot'' use VE due to not supporting Javascript.  [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 01:19, 15 July 2013 (UTC)\n""]","01:19, 15 July 2013 (UTC)",WhatamIdoing
+"[""::: Does not help. If equations are not rendered properly we'll be left with talking weather. --[[Special:Contributions/93.75.134.116|93.75.134.116]] ([[User talk:93.75.134.116|talk]]) 01:32, 15 July 2013 (UTC)\n""]","01:32, 15 July 2013 (UTC)",93.75.134.116
+"[""::::Why wouldn't you be able to render equations properly?  We '''are''' going to support math.  See [[:mw:Thread:Talk:Flow Portal/Maths/reply (2)]] for the latest word on math equations in VisualEditor.  [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 04:47, 15 July 2013 (UTC)\n""]","04:47, 15 July 2013 (UTC)",WhatamIdoing
+"[':::::Looks like there is some basic support for maths coming. [http://www.mediawiki.org/wiki/Talk:Flow_Portal#Maths_30340], demo at [http://www.mediawiki.org/wiki/VisualEditor:TestMath].--[[User:Salix alba|Salix]] ([[User talk:Salix alba|talk]]): 04:53, 15 July 2013 (UTC)\n']","04:53, 15 July 2013 (UTC)",Salix alba
+"['::::::Appears to me, that VE will be the least of our problems, when [[WP:Flow]] is ultimately implemented upon us all.--[[User:R.S. Peale|R.S. Peale]] ([[User talk:R.S. Peale|talk]]) 07:19, 15 July 2013 (UTC)\n']","07:19, 15 July 2013 (UTC)",R.S. Peale
+"["":::::::I ''was'' concerned about VE, but unaware of Flow. I'll be needing to recalibrate the paranoia filters, now.--[[User:R.S. Peale|R.S. Peale]] ([[User talk:R.S. Peale|talk]]) 07:19, 15 July 2013 (UTC)\n""]","07:19, 15 July 2013 (UTC)",R.S. Peale
+"[""::::::::Yech. I don't have the time right now to rebut every single point listed on its main page in its favour (which I could do though). If the WMF persists in not listening, I may just create [[User:Double sharp/talk]] to get away from this madness. (And learn how to hack the OBOD script for that – don't get me started on that.) Assuming I won't have to use VE on that, too. [[User:Double sharp|Double sharp]] ([[User talk:Double sharp|talk]]) 11:16, 15 July 2013 (UTC)\n""]","11:16, 15 July 2013 (UTC)",Double sharp
+"[':::::::::That\'s a genius idea, Double Sharp, assuming that is not made impossible as well. \'\'\'[[User:Toa Nidhiki05|<i style=""color:green;font-family:Mistral;"">Toa</i>]] [[User talk:Toa Nidhiki05|<i style=""color:green;font-family:Mistral;"">Nidhiki05</i>]]\'\'\' 18:59, 15 July 2013 (UTC)\n']","18:59, 15 July 2013 (UTC)",Toa Nidhiki05
+"[""::::::::::I have a feeling this sort of thing might have been used for a time in WP's early days... [[User:Double sharp|Double sharp]] ([[User talk:Double sharp|talk]]) 10:57, 28 July 2013 (UTC)\n""]","10:57, 28 July 2013 (UTC)",Double sharp
+"['[[Category:VisualEditor]]\n', '\n', "":[https://www.mediawiki.org/wiki/Flow_Portal/FAQ#Is_this_replacing_talk_pages.3F Flow is replacing talk pages], and [https://www.mediawiki.org/w/index.php?title=Thread:Talk:Flow_Portal/Interactive_Prototype/Markup-mode_*needed*_in_editor&lqt_oldid=39555 the only editor for talk pages will be Flow], so ''anyone saying that talk pages won't become VE-only is either [[WP:AGF|ignorant]] or [[WP:ACLUE|lying]].''  [http://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Flow&diff=prev&oldid=564299414 Jorm (WMF) can't be arsed to find out if VE will support wiki mark up], but [https://www.mediawiki.org/w/index.php?title=Thread:Talk:Flow_Portal/Interactive_Prototype/Markup-mode_*needed*_in_editor&lqt_oldid=39555 will force it on editors who will never have use for Visual editor].\n"", ':If the people behind Flow aren\'t going to be the least bit helpful to the people who are actually helping the encyclopedia (instead of just trying to make things easier for vandals and POV pushers), then the VE folks need to grow a pair (of ears), actually listen to the complaints instead of advertising other features as red herrings, and implement an ""edit source"" button in VE to let users who aren\'t senile or delinquent demi-literates actually get something done around here. [[User:Ian.thomson|Ian.thomson]] ([[User talk:Ian.thomson|talk]]) 19:52, 15 July 2013 (UTC)\n']","19:52, 15 July 2013 (UTC)",Ian.thomson
+"['\n', ""I pointed out at [[WP:VisualEditor]] that Flow will force all editors to use VE on talk pages, and [http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor&curid=37835429&diff=564415059&oldid=564409196 I was reverted and accused of making bad-faith false edits].  WMF has no idea what they're doing, and we need to make it known to them.  [[User:Ian.thomson|Ian.thomson]] ([[User talk:Ian.thomson|talk]]) 21:25, 15 July 2013 (UTC)\n""]","21:25, 15 July 2013 (UTC)",Ian.thomson
+"["":You've already made it clear you hold that opinion, Ian. I'm happy to engage with you more if you cease assuming bad faith of fellow contributors and staffers. [[User:Okeyes (WMF)|Okeyes (WMF)]] ([[User talk:Okeyes (WMF)|talk]]) 03:15, 16 July 2013 (UTC)\n""]","03:15, 16 July 2013 (UTC)",Okeyes (WMF)
+"[""::As a developer and admin (off-wiki) I've learned that assuming good faith in users and devs is nearly always warranted, and far more efficacious than assumption of bad.  However, I most emphatically decline to extend AGF toward code or parsers, until/unless it has proven itself non-faulty.  VE hasn't done this for me, yet, and I'm skeptical that it ever will.  WMF on the other hand, is not a script or a bot, but [[Soylent Green|made of people]].  And I'm '''sure''' you're trying harder than I to build an encyclopedia.  Even if I sometimes can't see it.--[[User:R.S. Peale|R.S. Peale]] ([[User talk:R.S. Peale|talk]]) 07:47, 17 July 2013 (UTC)\n""]","07:47, 17 July 2013 (UTC)",R.S. Peale
+"["":::I resent the assertion that we're made of people - we employ lawyers! I mean, they are made of people, but only in the same way that a hamburger is made of cows.\n"", ':::So, yeah, I appreciate the VE proper still needs a heck of a lot of work. It\'s not got the full featureset, and it\'s got a lot of bugs - but those are issues that can and will be fixed in time, hopefully (I can\'t say ""certainly"", because I don\'t make that decision, but ""almost certainly"") before any kind of Flow rollout. At the same time, as has been said by Erik and a few others (and he \'\'does\'\' make that decision) there will be an editor as part of flow that is an alternative to the VE. I don\'t personally know what that looks like yet, but I\'m in the office from Thursday and hope to chase it up in meatspace, where people can\'t run away ;). [[User:Okeyes (WMF)|Okeyes (WMF)]] ([[User talk:Okeyes (WMF)|talk]]) 08:42, 17 July 2013 (UTC)\n']","08:42, 17 July 2013 (UTC)",Okeyes (WMF)
+"['::::That is good news! Please make sure to also chase up that we actually need two things: A fall-back for VE for people without JavaScript for whatever reasons (Brandon stated that this will be available) but we also need a real Wikitext alternative to VE, or at least a Wikitext editor inside Flow (and Brandon didn\'t make any commitments regarding this one). Not that we end up with a very limited fall-back solution that stands far beyond the full featured Flow implementation of VE but ""supports Wikitext"". --[[User:Patrick87|Patrick87]] ([[User talk:Patrick87|talk]]) 09:17, 17 July 2013 (UTC)\n']","09:17, 17 July 2013 (UTC)",Patrick87
+"[""*Pointing to the new [[Wikipedia:VisualEditor/FAQ#VEFlow|FAQ question]] about this. There is, still, no plan to remove wiki text editing. Obviously, like all new tools, not all features will be available if you don't adopt it but we still plan to have it as a fall back (as certainly users will likely need it for years to come). [[User:Jalexander|Jalexander]]--[[Wikimedia Foundation|WMF]] 03:32, 16 July 2013 (UTC)\n""]","03:32, 16 July 2013 (UTC)",Jalexander
+"['\n', '""[https://www.mediawiki.org/wiki/Flow_Portal/FAQ#Is_this_replacing_talk_pages.3F Eventually, we\'ll probably get more aggressive about asking people to upgrade, and finally (at some nebulous time in the future), we\'ll auto-upgrade everyone.""] ...LOL. ""Unduly aggressive"", indeed! [[User:Double sharp|Double sharp]] ([[User talk:Double sharp|talk]]) 11:26, 16 July 2013 (UTC)\n']","11:26, 16 July 2013 (UTC)",Double sharp
+"[':Interesting that nobody has replied to this...interesting... [[User:Double sharp|Double sharp]] ([[User talk:Double sharp|talk]]) 10:40, 27 July 2013 (UTC)\n']","10:40, 27 July 2013 (UTC)",Double sharp
+"['::Check out [https://en.wikipedia.org/w/index.php?title=Wikipedia_talk%3AFlow&diff=565563209&oldid=565552556 these comments], which you might find reassuring. See also the FAQ link that Jalexander added, directly before your comment. HTH. –[[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 17:17, 28 July 2013 (UTC)\n']","17:17, 28 July 2013 (UTC)",Quiddity
+"['\n', '::: And [//en.wikipedia.org/w/index.php?title=Wikipedia_talk:Flow&diff=prev&oldid=565564684] (a couple of edits further) does show that Flow is meant to become incompatible with ""normal"" editing. So do [//en.wikipedia.org/w/index.php?title=Wikipedia_talk:Flow&diff=next&oldid=565570506], [//en.wikipedia.org/w/index.php?title=Wikipedia_talk:Flow&diff=next&oldid=565573181]... Sorry, but trying to deflect well-deserved criticism from WMF like [//en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/RFC&diff=566171408&oldid=566134704] does not look well. I would recommend you to self-revert. --[[User:Martynas Patasius|Martynas Patasius]] ([[User talk:Martynas Patasius|talk]]) 18:09, 28 July 2013 (UTC)\n']","18:09, 28 July 2013 (UTC)",Martynas Patasius
+"[""::::The visualeditor will not be mandatory for flow. It can't be, because some editors don't have javascript, and VE requires javascript. See [[WP:VisualEditor/FAQ#VEFlow]]. I completely agree that feedback (criticism/suggestions/bugreports/requests/etc) for VE and Flow is good/needed, but the wording in the header was factually incorrect and misleading, hence the change. –[[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 19:30, 28 July 2013 (UTC)\n""]","19:30, 28 July 2013 (UTC)",Quiddity
+"['\n', '::::: The point is that the ""wikitext editor"" will only be allowed to do what the ""VisualEditor"" does. And that will only be a subset of things that the ""wikitext editor"" can do now. In effect it means that we lose the ""old"" editor and get a ""VisualEditor"" with the graphical interface and a ""VisualEditor"" with the text interface. That is not a current ""wikitext editor"", although it might look like that from afar. It loses the main advantage of the normal ""wikitext editor"": flexibility.\n', '::::: Now it doesn\'t have to be this way, if WMF and the developers will act reasonably. It is relatively easy to show some box (or something) with words ""This part is not supported by this interface. You can edit its source directly."" (or something like that). Or at least ignore the unsupported part. Good editors do that. However, we are told that if something is supported by ""wikitext editor"" and unsupported by ""VisualEditor"", it will be simply rejected by the server... That\'s what we are furious about.\n', '::::: So, I still think that your change is wrong. --[[User:Martynas Patasius|Martynas Patasius]] ([[User talk:Martynas Patasius|talk]]) 20:01, 28 July 2013 (UTC)\n']","20:01, 28 July 2013 (UTC)",Martynas Patasius
+"[""::::::There are some technical details at the top of [[Wikipedia_talk:Flow#Supported_Wikitext]], and I've added an attemped summary of the issue from an editor's perspective (without the technical-aspects, and with examples of what we ''need'') at the bottom of that thread. There are also some helpful discussions around this topic in the thread directly above that. (Note: I'm a wikitext lover, too. I've handcoded webpages in notepad/homesite/notepad++/gedit since '97! I want what you want - power and flexibility without changing my typing habits too much. I'm just trying to help the conversation remain a conversation, rather than letting it turn into an argument over the as-yet-uncreated fallback editor and its hypothetical features, which will supposedly all be based around Parsoid (and will include whatever features Parsoid has available in ''x'' months time). HTH.) –[[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 21:09, 28 July 2013 (UTC)\n""]","21:09, 28 July 2013 (UTC)",Quiddity
+"['\n', '::::::: I guess it means we do not really disagree that much. You are saying that there are some things that must be achieved and we have to tell WMF what they are - I am saying that if we will do nothing, those things will not be achieved.\n', '::::::: In effect the difference is that by now I do not trust WMF that much: after all, it wasn\'t hard to make ""VisualEditor"" just slightly annoying without provoking ""everyone"" to hate it with great passion. And ""Flow"" (or ""Parsoid"") is a much harder project. So I suspect that ""Flow"" is not actually going to be implemented reasonably. However, it might be that the project won\'t get finished - and that might be the best we can hope for... Thus I would prefer to make WMF adopt the slogan ""There is no deadline!"" and just waste money without causing much harm... --[[User:Martynas Patasius|Martynas Patasius]] ([[User talk:Martynas Patasius|talk]]) 22:50, 28 July 2013 (UTC)\n']","22:50, 28 July 2013 (UTC)",Martynas Patasius
+"['== VE is annoying and disgusting ==\n', ""* I am feeling both annoyed and disgusted from the unwill and the unability of the foundation and their programmers to finally improve referencing content. With atm rank 17 on DE:WP's alltime editcount I am considering myself of one of the most active editors in that language's WP but never from the first day of my activity there (2006-07-12) was made any significant improvement on referencing articles. Actually referencing in MS Word 5.0 in 1989 was more easy than in WP 2013. You get it? It' just thouroghly failure. --[[User:Matthiasb|Matthiasb]] ([[User talk:Matthiasb|talk]]) 20:59, 19 July 2013 (UTC)\n""]","20:59, 19 July 2013 (UTC)",Matthiasb
+"['**I am nevertheless certain that a strictly time-based release of VE to German Wikipedia will be an unmitigated success - [[User:David Gerard|David Gerard]] ([[User talk:David Gerard|talk]]) 21:16, 19 July 2013 (UTC)\n']","21:16, 19 July 2013 (UTC)",David Gerard
+"[""*** Everyone can believe what he wants. Please be asured: there is no Easter bunny. I cannot help myself: for a couple of years or three the foundation does the maximum for making Wikipedia unattractive for new users and is doing nothing repeat nothing to motivate old users contributing also in future. Well, frankly spoken, the only improvement introduced to Mediawiki was the useless Wikilove feature a.k.a. give away a cat picture. Sorry but I really do not believe that Wikipedia will surve 2020 if WMF is ruled like at this moment for some more time. As a long time user and as a man who has [[dual education system|learned trading from the scratch]] I am sure, that the WMF is on a dangerous trip to nowhere. Unless they won't start to listen what editors are ''really'' needing WP is on a downwards loop. WMF lost way too much time with features not needed and even not helping at all. Throw away the VE as it is, nobody needs this. And finally listen to the communities. Well even if You never asked so far. --[[User:Matthiasb|Matthiasb]] ([[User talk:Matthiasb|talk]]) 21:49, 20 July 2013 (UTC)\n""]","21:49, 20 July 2013 (UTC)",Matthiasb
+"['****(Pretty sure David was being sarcastic, Matthias.) <span style=""text-shadow:grey 0.118em 0.118em 0.118em; class=texhtml"">\'\'\'[[User:Adam Cuerden|Adam Cuerden]]\'\'\' <sup>([[User talk:Adam Cuerden|talk]])</sup></span> 21:56, 20 July 2013 (UTC)\n']","21:56, 20 July 2013 (UTC)",Adam Cuerden
+"['\n', 'What really surprises me is the stubbornness the WMF is showing here in introducing the visual editor. Increasingly I find myself thinking that Wikipedia is being made harder and even impossible to edit step by step introducing an AFT nobody has ever needed or requested, an unusable Wikidata which has failed by design from the very start, now by doing away with the MediaWiki editor (after all, that\'s the tool that we use to bring in \'\'all\'\' content), and finally by replacing discussion pages with ""Flow"". The WMF, it appears, is not the least interested in the needs of its most faithful contributors, taking away the tools we need for our work, cf. the dying-away of the Toolserver, or the doing-away of the tick box to switch off visual editor for some hours on enwiki some weeks ago. I gather that it will not be possible to switch off ""Flow"". So, if we cannot even continue to discuss the way we used to what will be left for us to stay here? Even assuming lots of good faith, despite the WMF\'s best intentions, we will probably lose our core community pretty soon, and WMF does not seem to be interested in us any more. Been there, seen that. Paid editors are about to take over, I assume, while Wikimedia organisations are looking for a new community who likes these Facebook and Google kind of gadgets that are taking a lot of time and money to develop. Reminds me very much of Bertolt Brecht\'s poem \'\'[[Die Lösung]]\'\' (""The solution"") on the relationship between the East-German state and its people after the resurrection of 1953: \'\'Wäre es da/ Nicht doch einfacher, die Regierung/ Löste das Volk auf und/ Wählte ein anderes?\'\' (""Would it not be easier/ In that case for the government/ To dissolve the people/ And elect another?"").--[[User:Aschmidt|Aschmidt]] ([[User talk:Aschmidt|talk]]) 20:53, 23 July 2013 (UTC)\n']","20:53, 23 July 2013 (UTC)",Aschmidt
+"['*Even Microsoft have shown more interest in their clients than the WMF have... [[User:Lukeno94|<span style=""color:navy;"">Luke</span><span style=""color:FireBrick;"">no</span><span style=""color:green;"">94</span>]] [[User talk:Lukeno94#top|<i>(tell Luke off here)</i>]] 21:05, 23 July 2013 (UTC)\n']","21:05, 23 July 2013 (UTC)",Lukeno94
+"[""* '''Now ''WikiFahrenheit-451'' as they burn our old tools:''' I can expect how many users will want to quit, but the trampling of our community should strengthen our resolve, as in ''[[Fahrenheit 451]]'', we should form our own plans to improve tools, plus find [[sympathizer]]s within WMF Platform Engineering who will help us to preserve the contents of the books before everything is burned in the Firestorm. -[[User:Wikid77|Wikid77]] ([[User talk:Wikid77|talk]]) 16:03, 24 July 2013 (UTC)\n""]","16:03, 24 July 2013 (UTC)",Wikid77
+"['\n', '*I find these comments annoying and disgusting. This is a serious forum, not a lavatory for wild, emotive venting. [[User:Tony1|<span style=""color:darkgreen;"">\'\'\'Tony\'\'\'</span>]] [[User talk:Tony1|<span style=""color:darkgreen;"">(talk) </span>]] 02:28, 26 July 2013 (UTC)\n']","02:28, 26 July 2013 (UTC)",Tony1
+"['::Seconded.[[User:OrangesRyellow|OrangesRyellow]] ([[User talk:OrangesRyellow|talk]]) 10:33, 26 July 2013 (UTC)\n']","10:33, 26 July 2013 (UTC)",OrangesRyellow
+"[':::Yet the fact that such venting does take place and that people have felt the need to create a dedicated section of it shows pretty clearly the most common reaction... [[User:Double sharp|Double sharp]] ([[User talk:Double sharp|talk]]) 15:18, 31 July 2013 (UTC)\n']","15:18, 31 July 2013 (UTC)",Double sharp
+"['== ""Centralized discussion""? ==\n', '\n', 'Since at the moment this page seems to be the main for discussion of ""VisualEditor"", perhaps it should be mentioned in [[Template:Centralized discussion]]? A couple of ""less main"" discussions have been mentioned ([//en.wikipedia.org/w/index.php?title=Template:Centralized_discussion&oldid=565935250])... --[[User:Martynas Patasius|Martynas Patasius]] ([[User talk:Martynas Patasius|talk]]) 18:29, 28 July 2013 (UTC)\n']","18:29, 28 July 2013 (UTC)",Martynas Patasius
+"['== The Germans state their stand ==\n', '[[:de:Wikipedia:Umfragen/VisualEditor Opt-in|FWIW]]. [[User:Double sharp|Double sharp]] ([[User talk:Double sharp|talk]]) 00:53, 29 July 2013 (UTC)\n']","00:53, 29 July 2013 (UTC)",Double sharp
diff --git a/src/helper_scripts/cleaning_scripts/0224_https_talk_text.csv b/src/helper_scripts/cleaning_scripts/0224_https_talk_text.csv
new file mode 100644
index 0000000..d49d45c
--- /dev/null
+++ b/src/helper_scripts/cleaning_scripts/0224_https_talk_text.csv
@@ -0,0 +1,125 @@
+comment_text,date_created,Author
+"['== Organisation of the content page ==\n', 'Here are the thoughts which drived my writing/expansion of the content page.\n', '\n', 'I follow wikitech-l and wikitech-ambassadors since many years (less for the latter :) and I have difficulties to track the various topics. I’m interested in the HTTPS topic and  I find both the technical and community people should be involved in this question, hence a job for a wikitech ambassador.\n', '\n', 'I find this page should be a portal/hub -- still better it is presently -- explaining the general topic, the various questions involved (better than only the keywords presently), the past and coming deployments, and a collection of pointers about the state of the discussion (wikitech-l and bugzilla mainly for this topic).\n', '\n', 'Any thoughts about this organisation?<br />\n', '(Perhaps we can use this section -- with subsections -- to discuss specifically about the organisation, and let the other sections about true HTTPS questions.)<br />\n', '~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 09:34, 18 August 2013 (UTC)\n']","09:34, 18 August 2013 (UTC)",Seb35|<small>[^_^]<
+"[': [[w:en:WP:BOLD|Be bold]]. :-)  --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 16:40, 18 August 2013 (UTC)\n']","16:40, 18 August 2013 (UTC)",MZMcBride
+"[': Hi Seb35. Thanks for the dump. I am a little concerned, though, that people who are pointed to this page due to the planned Wednesday deploy of SecureLogin by default won\'t know where to begin; it\'s a little text heavy without much ""what is going on, what this means for you"" in simple and brief language. I hope you don\'t mind, but I\'m going to [[w:en:WP:BOLD|Be bold]] and drastically rearrange this page to address the most common questions and conerns from users who are having problems with HTTPS. I\'m going to keep much of what you wrote, just re-arrange, mostly. Thanks again! [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 22:49, 19 August 2013 (UTC)\n']","22:49, 19 August 2013 (UTC)",Greg (WMF)
+"['::Hi, thanks a lot for the rewritting, it’s better now with these simple explanations. I removed my paragraph about PRISM since you better summarised it in the introduction; I hesitated about adding a link, but it could distract the reader. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 12:14, 20 August 2013 (UTC)\n']","12:14, 20 August 2013 (UTC)",Seb35|<small>[^_^]<
+"['== Soft HSTS (HTTP Strict-Transport-Security) ==\n', '\n', 'I wrote [[:mw:Extension:HSTS|an extension]] for MediaWiki to enable [[:en:HTTP Strict-Transport-Security|HSTS]] on a per-user basis. The rationale behind is to let the privacy-conscious users to opt-in to HTTPS-everytime (for all compatible browsers) independently of their current connected or unconnected status, and at the same time not force the other users to use HTTPS (particularly if they use to live in a HTTPS-unfriendly environment as the China).\n', '\n', 'I find such an extension would be worth to be installed on the Wikimedia projects (in the first times on the test wikis and then the MediaWiki wiki) to balance between the advantages and drawbacks of HTTPS, as well as slowly increase the HTTPS load of the servers. HSTS coming with a high constraint (fatal error in case of bad TLS/HTTPS connection), I find it could be tested with increasing expiration times (1 hour; 1 day; 2 weeks; 1 month) with some volunteers during the next year to test if all works correctly (e.g. the users will obligatorily complain if their old browser’s cipher suite or SSL 3.0 is removed).\n', '\n', '~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 17:03, 18 August 2013 (UTC)\n']","17:03, 18 August 2013 (UTC)",Seb35|<small>[^_^]<
+"[':I misunderstood the deployment planned for August 21, 2013; I thought it was only the log-in page. This extension becomes almost useless if all HTTP traffic is 301-redirected to HTTPS, or it could be tweaked to remove the user preference and be activated for all logged-in users in order to remove the 301-redirect-over-HTTP step which can still be MITMed/spied. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 18:18, 18 August 2013 (UTC)\n']","18:18, 18 August 2013 (UTC)",Seb35|<small>[^_^]<
+"[':And the extension is now updated to give the server administrator the possibility to force anonymous and/or logged-in users to have a STS header, or to let the logged-in users choose if they want one. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 20:06, 18 August 2013 (UTC)\n']","20:06, 18 August 2013 (UTC)",Seb35|<small>[^_^]<
+"['== Load script from home wiki ==\n', '\n', ""En.wiki is my homewiki, and in all other projects I have this in my vector.js:<br /><code>mw.loader.load( '//en.wikipedia.org/w/index.php?title=User:Edokter/MenuTabsToggle.js&action=raw&ctype=text/javascript' );</code>\n"", '\n', 'This fails in modern browsers as a XSS-violation when in HTTPS. Are there any provisions where the several Wikimedia domains are trusted with regard to eachother? <span style=""font-family:\'Trebuchet MS\'""> — [[User:Edokter|<span style=""color:#008""><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style=""color:#080"">talk</span>]]) — </span> 09:56, 20 August 2013 (UTC)\n']","09:56, 20 August 2013 (UTC)",Edokter
+"['\n', ':I don’t know well XSS, but this syntax works for me (Opera 12.16, I have it in my en.wp common.js). Else I see on [[:mw:ResourceLoader/Migration guide (users)#Migrating user scripts]] it is recommanded to keep importScript instead of switching to mw.loader to avoid problems; perhaps you can try with importScript. Else what browser+version do you have? ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 12:41, 20 August 2013 (UTC)\n']","12:41, 20 August 2013 (UTC)",Seb35|<small>[^_^]<
+"["": I see [[:en:User:Edokter/MenuTabsToggle.js]] itself calls <code>mw.loader.load</code> with 'http' explicitly specified, and Firefox 23.0 here complains about the mixed content due to that. Try making that protocol-relative as well? [[User:Anomie|Anomie]] ([[User talk:Anomie|talk]]) 13:47, 20 August 2013 (UTC)\n""]","13:47, 20 August 2013 (UTC)",Anomie
+"['\n', '::A bug in Chrome (or was it IE?) prevents use of protocol-relative stylesheets in the .load method. XSS stands for \'Cross-site scripting\'. Most moders browsers block loading scripts form another domain when you are on a secure connection. The only way to allow secure cross-site scripts to load is by whitelisting those domains in the certificate. That is what my question partains to: does our certificate has such a whitelist? <span style=""font-family:\'Trebuchet MS\'""> — [[User:Edokter|<span style=""color:#008""><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style=""color:#080"">talk</span>]]) — </span> 20:47, 20 August 2013 (UTC)\n']","20:47, 20 August 2013 (UTC)",Edokter
+"[':::Independently of XSS, about the HTTP/HTTPS in the scripts and problems with protocol-relative, you can use some script like\n', ':::<syntaxhighlight lang=""javascript"">mw.loader.load( window.location.protocol+\'//en.wikipedia.org/w/...\' );</syntaxhighlight>\n', ':::([https://developer.mozilla.org/en-US/docs/Web/API/window.location ref]) ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 22:03, 20 August 2013 (UTC)\n']","22:03, 20 August 2013 (UTC)",Seb35|<small>[^_^]<
+"["":::: Seb35's solution is what I most commonly see for addressing this issue, so that's probably a good solution in this case. Edokter, the enwiki certificate has most of the other domains in the Subject Alternative Name. I personally haven't encountered the issue with the browsers I user, but I'll see if I can reproduce if you let me know what you're using. [[User:CSteipp|CSteipp]] ([[User talk:CSteipp|talk]]) 22:42, 26 August 2013 (UTC)\n""]","22:42, 26 August 2013 (UTC)",CSteipp
+"[':::::HTTPS has just kicked in and to my surprise, all my scripts seem to load from en.wiki just fine. <span style=""font-family:\'Trebuchet MS\'""> — [[User:Edokter|<span style=""color:#008""><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style=""color:#080"">talk</span>]]) — </span> 22:09, 28 August 2013 (UTC)\n']","22:09, 28 August 2013 (UTC)",Edokter
+"['== Excluded language ==\n', '\n', 'Please add ckb wikipedia to excluded language. All sysops of ckb.wiki are from Iran and we can not access to wikimedia projects via HTTPS.--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 19:01, 20 August 2013 (UTC)\n']","19:01, 20 August 2013 (UTC)",Calak
+"[':What is the exact list of the excluded languages: is it only <code>zh</code> and <code>fa</code>? Or are there also the other Chinese languages: <code>yue/zh-yue</code>, <code>wuu</code>, <code>gan</code>, <code>cdo</code>, <code>nan/zh-min-nan</code>? +those of Iran? Is there a gerrit patch about the config? ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 20:25, 20 August 2013 (UTC)\n']","20:25, 20 August 2013 (UTC)",Seb35|<small>[^_^]<
+"["":Please see [https://bugzilla.wikimedia.org/show_bug.cgi?id=52846 bug 52846], these wikis mostly used in Iran and have same problem: fa, ckb, mzn, glk, ku. I don't know any thing about Chinese languages.--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 20:34, 20 August 2013 (UTC)\n""]","20:34, 20 August 2013 (UTC)",Calak
+"[':The current plan is to exclude based on the IP/location of the user, not the language wiki. This means that users from eg China will be able to login to English Wikipedia over HTTP if needed. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:40, 21 August 2013 (UTC)\n']","23:40, 21 August 2013 (UTC)",Greg (WMF)
+"['== update of automated editing tools ==\n', '\n', 'Are pywikipediabot, autowikibrowser, etc, now https compliant? It would be extremely disruptive to implement this change without automated editing tools being able to accommodate it. [[User:DavidLeighEllis|DavidLeighEllis]] ([[User talk:DavidLeighEllis|talk]]) 19:24, 20 August 2013 (UTC)\n']","19:24, 20 August 2013 (UTC)",DavidLeighEllis
+"[':According to [[:mailarchive:wikitech-ambassadors/2013-August/000349.html|this message]] (just sent), pywikipediabot was updated for HTTPS and the pywikipediabot users must update their code with the last version. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 21:27, 20 August 2013 (UTC)\n']","21:27, 20 August 2013 (UTC)",Seb35|<small>[^_^]<
+"[':Please let me know (preferably via IRC or email, greg{{@}}wikimedia.org) if you see any tools that are not ready as soon as possible. Thanks! [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:42, 21 August 2013 (UTC)\n']","23:42, 21 August 2013 (UTC)",Greg (WMF)
+"['== Commons, Wikidata and SUL ==\n', '\n', ""Won't this create lots of trouble for people in China and Iran who need to upload an image to Commons or modify an interwiki link on Wikidata?\n"", '\n', ""* Commons: You must be logged in to upload an image. If HTTPS is unavailable and mandatory, then you can't log in.\n"", '* Wikidata: It is possible to edit links without logging in, so I suppose that you can edit as an IP using HTTP? This however reveals your IP for everyone to see. Editing over HTTP also reveals your IP address, but only to anyone who is wiretapping you at the same time as you are accessing the Internet.\n', ""* SUL: Logs you in automatically if you visit another project. Doesn't this mean that Chinese and Iranian users will have to log out in order to read an article in another language? This could be very inconvenient if you at the same time need to be logged in on Chinese or Iranian Wikipedia.\n"", '\n', ""You can presumably access HTTPS by using VPN or TOR and you can disable login on selected projects by changing your cookie settings. However, lots of users probably don't know how to do this and the result will instead be that logging in will be disabled. I am personally able to use HTTPS and have HTTPS Everywhere installed, but I understand that lack of unencrypted HTTP for logged in users may cause lots of problems to users in some countries. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 19:49, 20 August 2013 (UTC)\n""]","19:49, 20 August 2013 (UTC)",Stefan2
+"["":The current plan is to redirect based on the IP/location of the user, not based on language wiki. This should alleviate this issue as we'll whitelist users from China and Iran initially, along with potentially some locations that have a hard time using HTTPS. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:44, 21 August 2013 (UTC)\n""]","23:44, 21 August 2013 (UTC)",Greg (WMF)
+"['== HTTPS problem ==\n', '\n', ""Hello. Now we can't access to all WM projects (except Meta, Commons and Incubator)!--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 19:54, 20 August 2013 (UTC)\n""]","19:54, 20 August 2013 (UTC)",Calak
+"['*I guess Meta, Commons, and Incubator should all be excluded from the forced https until the ""GeoIP"" functions are available, in order not to cause any problems there for Iranian or Chinese users who e.g. want to complain here on Meta about https problems, are active with uploading files on Commons, or active in test-projects in their language on Incubator. --<small>[[User:MF-Warburg|MF-W]]</small> 20:01, 20 August 2013 (UTC)\n']","20:01, 20 August 2013 (UTC)",MF-Warburg
+"[""Now Bugzilla, MediaWiki and Wikidata have not any problem, but all WM projects are out of access. Now I am sysop on ckb wikipedia an I can't open even one page! What are we suppose to do?--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 20:07, 20 August 2013 (UTC)\n""]","20:07, 20 August 2013 (UTC)",Calak
+"[': Please see the ""[[{{SUBJECTPAGENAME}}#Help!|Help!]]"" section of the subject-space page. [[IRC]] is fastest. :-)  --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 21:23, 20 August 2013 (UTC)\n']","21:23, 20 August 2013 (UTC)",MZMcBride
+"[':I\'m confused, Calek, can you honestly not access ""even on page"" *right now*? We haven\'t made any changes yet. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:45, 21 August 2013 (UTC)\n']","23:45, 21 August 2013 (UTC)",Greg (WMF)
+"['== why Chinese languages are excluded？ ==\n', '\n', 'I think Chinese wikipedian community has made it clear that all Chinese language(Classical Chinees, Wuu chinese etc) should not be convert into https version, but here I see nothing. can somebody tell me why please? as A classical Chinese editor, I will no longer be able to do my work if it is true that Meta forget their promises. \n', '\n', '----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 23:04, 20 August 2013 (UTC)\n']","23:04, 20 August 2013 (UTC)",Benjamin Jiperus
+"[': See also [[bugzilla:52846#c12]] and try to get a complete list of the languages. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 23:12, 20 August 2013 (UTC)\n']","23:12, 20 August 2013 (UTC)",Stefan2
+"['\n', ""The Chinese community has given a list, on that list, it shows what kind of Chinese language should not be https, that also include Tibetan, another Sino-Tibetan language that will be influenced. because most of the native speakers are '''located in China''' where HTTPs isn't an easy option. we have already got restrictions from Communist party. https is no help to us. ----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 23:16, 20 August 2013 (UTC)\n""]","23:16, 20 August 2013 (UTC)",Benjamin Jiperus
+"['== Leave choice to users ==\n', 'Please let users choose which transport they want to use. --[[User:Purodha|Purodha Blissenbach]] ([[User talk:Purodha|talk]]) 23:06, 20 August 2013 (UTC)\n']","23:06, 20 August 2013 (UTC)",Purodha
+"[""* This. It will be complete crap if I will be forced to edit through HTTPS, it's slow on my instable connection. And FYI, forcing users should be only last resort, and I see no reason to change to HTTPS voluntarily. [[User:KPu3uC B Poccuu|KPu3uC B Poccuu]] ([[User talk:KPu3uC B Poccuu|talk]]) 02:32, 21 August 2013 (UTC)\n""]","02:32, 21 August 2013 (UTC)",KPu3uC B Poccuu
+"['\n', 'Please leave the choice to user, this is so wrong to force people to use HTTPS if they want to stay connected. --[[User:PierreSelim|PierreSelim]] ([[User talk:PierreSelim|talk]]) 05:19, 21 August 2013 (UTC)\n']","05:19, 21 August 2013 (UTC)",PierreSelim
+"[':You can [[HTTPS#Disabling|turn off HTTPS]] in the preferences. As of now I don’t see it, I guess it will be deployed in some hours at the same time HTTPS will become mandatory. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 06:33, 21 August 2013 (UTC)\n']","06:33, 21 August 2013 (UTC)",Seb35|<small>[^_^]<
+"['::Keep in mind that that will only disable the secure browsing and secure editing features; log-in remains only HTTPS even if that preference is selected. [[User:Risker|Risker]] ([[User talk:Risker|talk]]) 08:12, 21 August 2013 (UTC)\n']","08:12, 21 August 2013 (UTC)",Risker
+"["":::That should be enough for my JavaScript bot and for web-debugging. I'd prefer if I don't have to make my browser trust the Fiddler certificate. -- [[User:Rillke|Rillke]] ([[User talk:Rillke|talk]]) 08:11, 22 August 2013 (UTC)\n""]","08:11, 22 August 2013 (UTC)",Rillke
+"['\n', '\n', ""Is there anyway to make the opting out of HTTPS a global preference?  I tend to go to the foreign language wikis to get more extensive articles about subjects of greater import to that language community, and I'm having to manually go to the preferences page the first time I visit them after the change and to opt out of HTTPS for that wiki. That has been and remains my biggest gripe about the HTTPS switchover. [[User:Carolina wren|Carolina wren]] ([[User talk:Carolina wren|talk]]) 02:31, 12 September 2013 (UTC)\n""]","02:31, 12 September 2013 (UTC)",Carolina wren
+"['== Translation ==\n', '\n', ""Hi. Why neither this page nor global message delivery post isn't/wasn't translatable? Do you think everybody on the planet is at least en-2? Althought I try to AGF but I can't consider it another way than not respect to local not English communities who are not obliged to learn English. WMF should never do that way again. --[[User:Base|Base]] ([[User talk:Base|talk]]) 23:26, 20 August 2013 (UTC)\n""]","23:26, 20 August 2013 (UTC)",Base
+"[':Basically this is now possible in a manual way, although I’m personaly relunctant to use the Translated extension because the page is not stable and would ask frequent re-translations, but if someone wants to set up it, just do. I asked the Meta admins to [[Meta:Requests for help from a sysop or bureaucrat#Translate the link of Special:CentralNoticeBanners/edit/Genericmaintenancenotice|change the link in the banners]] (I would be very happy if someone could do that!). I sent a message to the [[:mailarchive:translators-l/2013-August/002362.html|translators-l mailing list]] about this translation. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 13:02, 21 August 2013 (UTC)\n']","13:02, 21 August 2013 (UTC)",Seb35|<small>[^_^]<
+"['== List of Chinese Wikipedia  ==\n', '\n', 'Please Notice these languages also need to remain http.\n', '\n', '*[//zh-classical.wikipedia.org/wiki/%E7%B6%AD%E5%9F%BA%E5%A4%A7%E5%85%B8:%E5%8D%B7%E9%A6%96 Classical Chinese(lzh)]\n', '*[//wuu.wikipedia.org/wiki/%E5%B0%81%E9%9D%A2 Wuu Chinese(wuu)]\n', '*[//gan.wikipedia.org/wiki/%E8%B4%9B%E8%AA%9E Gan Chinese(Gan)]\n', '*[//hak.wikipedia.org/wiki/Th%C3%A8u-Ya%CC%8Dp Hakka Chinese(Hak)]\n', '*[//zh-yue.wikipedia.org/wiki/%E9%A0%AD%E7%89%88 Cantonese(zh-yue) ]\n', '*[//bo.wikipedia.org/wiki/%E0%BD%82%E0%BD%99%E0%BD%BC%E0%BC%8B%E0%BD%84%E0%BD%BC%E0%BD%A6%E0%BC%8D Tibetan(bo)]\n', '*[//zh-min-nan.wikipedia.org/wiki/Th%C3%A2u-ia%CC%8Dh Minnan Chinese(zh-min-nan)]\n', '\n', '----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 23:28, 20 August 2013 (UTC)\n']","23:28, 20 August 2013 (UTC)",Benjamin Jiperus
+"['\n', 'Sorry there is two more languages:\n', '* [//cdo.wikipedia.org/wiki/T%C3%A0u_Hi%C4%95k Mindong Chinese(cdo)]\n', '*[//ug.wikipedia.org/wiki/%D8%A6%DB%87%D9%8A%D8%BA%DB%87%D8%B1%DA%86%DB%95_%DB%8B%D9%89%D9%83%D9%89%D9%BE%D9%89%D8%AF%D9%89%D9%8A%DB%95 Uyghur (ug)]\n', '\n', 'Uyghur are Turkish language, a majority of Uighur people lives in the west part of China.  \n', 'Thank you<br />{{unsigned|Benjamin Jiperus|23:49, 20 August 2013 (UTC)}}\n', ':I opened the [[:bugzilla:53144|bug 53144]] for tracking this problem and wrote the list you gave (+zh :) ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 07:39, 21 August 2013 (UTC)\n']","07:39, 21 August 2013 (UTC)",Seb35|<small>[^_^]<
+"['\n', '::[//ii.wikipedia.org Sichuan Yi (ii)] ([//ii.wikipedia.org/wiki/ 16 articles by now]) --<span style=""font-family:Palatino"">[[User:Geitost|Geitost]] [[User talk:Geitost|<sup>\'\'diskusjon\'\'</sup>]]</span> 07:31, 22 August 2013 (UTC)\n']","07:31, 22 August 2013 (UTC)",Geitost
+"['== Perfect forward secrecy ==\n', '\n', 'Will the new https-including setup have the [http://en.wikipedia.org/wiki/Perfect_forward_secrecy Perfect forward secrecy] property? If not, it would be nice to have. There should be an option to prioritize Diffie-Hellman for key-exchange to achieve this. Wishing you good results for the procedure, good to see that coming. --[[User:Methossant|Methossant]] ([[User talk:Methossant|talk]]) 23:35, 20 August 2013 (UTC)\n']","23:35, 20 August 2013 (UTC)",Methossant
+"[':According to ""[[:wmfblog:2013/08/01/future-https-wikimedia-projects/|The future of HTTPS on Wikimedia projects]]"" PFS will not be enabled soon, but it is in the future plans. From the some things I read about PFS [https://www.imperialviolet.org/2011/11/22/forwardsecret.html this blog post] is interesting (activation of PFS by Google) and [http://vincent.bernat.im/en/blog/2011-ssl-perfect-forward-secrecy.html this one] says PFS only cost 15% more in computer time (ECDHE version, because the classical DHE is much more expensive -- 300% more in compute time). But PFS is not completely supported by all modern browsers: IE support lacks, Opera only have DHE; Chromium and Firefox have full support. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 07:05, 21 August 2013 (UTC)\n']","07:05, 21 August 2013 (UTC)",Seb35|<small>[^_^]<
+"[':: If you have any news in this regard, you want to upgrade to something like quantum cryptography? [[User:João bonomo|João bonomo]] ([[User talk:João bonomo|talk]]) 20:06, 11 September 2013 (UTC)\n']","20:06, 11 September 2013 (UTC)",João bonomo
+"['== Unable to edit Wikidata ==\n', '\n', 'It says to report trouble here.<br />\n', 'I have not been able to edit Wikidata while logged in for the past couple of days.<br />\n', 'The [edit] buttons all appear initially, then they vanish.<br />\n', '[[User:Varlaam|Varlaam]] ([[User talk:Varlaam|talk]]) 00:36, 21 August 2013 (UTC)\n']","00:36, 21 August 2013 (UTC)",Varlaam
+"["":Hi Varlaam, I doubt this is due to the HTTPS (the topic of this Talk: page) as nothing has changed yet :-). I've reported it to the WikiData team in [https://bugzilla.wikimedia.org/show_bug.cgi?id=53200 this bug report]. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 05:07, 22 August 2013 (UTC)\n""]","05:07, 22 August 2013 (UTC)",Greg (WMF)
+"[':: Greg, thanks for pointing this our way. Varlaam, can you give a bit more info? Browser used? Operating system? Can you try switching off your gadgets and see if there is some interplay? --[[User:Denny|denny]] ([[User talk:Denny|talk]]) 09:30, 22 August 2013 (UTC)\n']","09:30, 22 August 2013 (UTC)",Denny
+"['::: I agree with Greg that it shouldn\'t be the HTTPS. You try disabling all your gadgets, then re-enable each individually to try to figure out if any is the problem. I remember some time ago a script caused a similar issue for me. If this doesn\'t help (if you still have the issue with all gadgets off, even after clearing your browser\'s cache, the extra information Denny asked for might be of some help. <b><span style=""border:2px solid;font-variant:small-caps"">[[User:Hazard-SJ|<span style=""background:#00008B;color:#FFF"">&nbsp;Hazard-SJ&nbsp;</span>]][[User talk:Hazard-SJ|<span style=""color:#00008B;background:red"">&nbsp;✈&nbsp;</span>]]</span></b> 23:25, 22 August 2013 (UTC)\n']","23:25, 22 August 2013 (UTC)",Hazard-SJ
+"['== Copy editing notes ==\n', '\n', '*Please add a link to some formal statement or roadmap or approved plan that says ""[t]he continued work to improve the security and privacy of Wikimedia project users is a stated goal of the Wikimedia Foundation"". (I\'m not doubting it\'s true, but a footnote/reference helps.) \n', '*It might also be useful to link to some internal or external site that confirms the use of Wikipedia as a site useful for tracking.  \n', ""*I recall some discussion on how images would be handled with HTTPS enabled, but wasn't technically competent enough to follow the conversation. Are there any issues with images that will change the effectiveness of the HTTPS login and browsing? If so, and since we have a huge number of non-Commons pages with images on them, it would be appropriate to mention this.\n"", '*Also appropriate to mention any other situations where HTTPS may not be as effective as expected.\n', '[[User:Risker|Risker]] ([[User talk:Risker|talk]]) 05:29, 21 August 2013 (UTC)\n']","05:29, 21 August 2013 (UTC)",Risker
+"['\n', ':1. no idea about that\n', ':2. added a Jimmy Wales’ tweet with an image (perhaps the journal article is better, don’t know)\n', ':3 and 4. I guess you are speaking about the traffic analysis, allowing an attacker to guess the page you are reading by collecting the sizes of the pages, images, and ressources from all pages and comparing it afterwards to some specific request you made; if so, I think it is too technical and specific for being worth to be mentioned here (but it’s because of this fact I wrote in the introduction ""you can have a reasonable expectation that nobody knows what pages you are visiting"").\n', ':~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 13:22, 21 August 2013 (UTC)\n']","13:22, 21 August 2013 (UTC)",Seb35|<small>[^_^]<
+"['== A request of resolution  ==\n', '\n', 'Here is all I know(forgive my English):\n', ""*Chinese Wikipedian have send a list of Chinese language(that are not suitable for https) while the meeting was still going 2 weeks ago.I wasn't at the meeting, people who was there told me Wikimedia Foundation would take into account Chinese languages(for example Wuu, Cantonese and Classical.etc)\n"", '*Now people are telling me except Chinese(standard), other dialects and Classical Chinese will still use https. \n', '*this is not what we expected. \n', '*I hope what is promised(if there is a promise made by Wikimedia Foundation) will be carried out. \n', '*If I am wrong about what I say, please tell me the actual situation of converting into https version. \n', '\n', 'thank you----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 09:34, 21 August 2013 (UTC)\n']","09:34, 21 August 2013 (UTC)",Benjamin Jiperus
+"["":Hi Benjamin. Sorry for the confusion. The current status, as described on [[HTTPS]], is that users from countries where HTTPS is not an option (specifically, China and Iran) will not be redirected to HTTPS but instead will stay on HTTP. Thus, if you are a Chinese user access English Wikipedia, you will still be able to login and view everything because you will be going over HTTP (as you're computer is based in China). Hope that clarifies, let me know if it doesn't. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 20:18, 27 August 2013 (UTC)\n""]","20:18, 27 August 2013 (UTC)",Greg (WMF)
+"['== Which documents? ==\n', 'The preamble of this article mentions: ""The Wikipedia project was referenced in several documents as a specific source for tracking users\' behavior online"". Which documents are referenced here? Was it discussed somewhere? -- [[User:Ace111|Ace111]] ([[User talk:Ace111|talk]]) 13:31, 21 August 2013 (UTC)\n']","13:31, 21 August 2013 (UTC)",Ace111
+"[':This was raised by [[User:Risker|Risker]] two sections above; I just added a link to one document I know, but I don’t know others. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 13:37, 21 August 2013 (UTC)\n']","13:37, 21 August 2013 (UTC)",Seb35|<small>[^_^]<
+"[':: Jimbo\'s twitter post refers to a NSA slide from [http://www.theguardian.com/world/2013/jul/31/nsa-top-secret-program-online-data Guardian] with a question: ""Why are we interested in HTTP?"" and an answer ""Because nearly everything a typical user does on the Internet uses HTTP"", followed by examples of web sites such as Facebook, Yahoo, Twitter, myspace, CNN, mail.ru, Wikipedia, Google and Gmail. I don\'t think this is a proper reference for Wikipedia as a specific source for tracking users\' behavior. -- [[User:Ace111|Ace111]] ([[User talk:Ace111|talk]]) 14:55, 21 August 2013 (UTC)\n']","14:55, 21 August 2013 (UTC)",Ace111
+"[':::I remembered some people in the discussions (on wikitech-l probably) with a similar opinion. I don’t have real opinion myself if this constitutes an evidence or not; but it’s the only thing I know that people refered for this claim, but obviously perhaps there are others I missed. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 22:19, 21 August 2013 (UTC)\n']","22:19, 21 August 2013 (UTC)",Seb35|<small>[^_^]<
+"['== privacy concerns with images embedded in pages, served by Commons ==\n', '\n', 'Is HTTPS fully supported as well for images hosted on Commons (if Commons does not have HTTPS support for now), when these images (most often thumbnailed) are embedded in Wikipedia pages ?\n', 'Can you warranty that noone will know which Wikipedia you are consulting (including in Talk pages) if they embed these images in an unique way ? It is easy to deduce which pages you are reading if you can track the images embedded in them.\n', ""Commons should then support HTTPS, including on the images server (but there's a huge scalability problem because Commons is extremely large and the thumbnail image servers have lots of work to do, probably much more than wikis themselves).\n"", '\n', 'Also a good thing to do would be to mutualize ALL WMF wikis on the same base domain, so that we could use the same logon domain and remain in it, even when navigating on foreign wikis (it would require only a new design for paths; e.g. allowing transparent remapping of\n', ': http(s)://(projectlangcode).(wikipedia).org/wiki/(pagename)\n', 'to\n', ': http(s)://www.wikimedia.org/(wikipedia)/(lang)/wiki/(pagename)\n', '\n', 'One bug advantage would be the unification of security, simplification of navigation. In fact we would just connect via HTTP or HTTPS to a single proxy with a single URL:\n', ': https://wikimedia.org/logon\n', 'and then all navigation would occur within the same domain within the same session, to request any number of pages or images, from any wiki of the foundation. only within this encrypted HTTPS session would the legacy URLs be requested. This proxy domain would connect directly to any one of the existing Squid proxies, forwarding internally the requests to the appropriate project wiki and image servers (or other services, including Worpress blogs, IRC channels, submission APIs, etc. that are compatible with HTTP proxies).\n', '\n', ""But the users won't see now any change in their address bar that will only show\n"", ': https://wikimedia.org/logon\n', 'during their navigation across pages, projects and services. Even when they will right click a link, they will be show anonymized URLs encrypted with their current secure session keys (e.g. https://go.wikimedia.org/(base-64 encoded encrypted string containing the service/project/language/page?get parameters).\n', 'Note that the proxy delivering an HTML wiki page could transform as well these links using short URLs specific to the session, to make the base-64 strings short (the proxy would cache the URLs from the original page to build short URLs specific to the session and not comparable across users, using a simple SHA1 digest of the full URL, encrypted with the private session key, so that the delivered HTML pages would only contain relative links like ""/(short base64 string)"")\n', '\n', 'The base-64 encoding is suggested, but a larger encoding alphabet could make the string even a bit shorter, similar to those strings used on services like TinyURL. As well the non-encrupted string could be cached internally with a mapping to make them even shorter (based on usage statistics) for frequently accessed URLs. The encryption of these short URLs would still remain private and specific to each user session.\n', '\n', 'Note that this encyption of URLs does not require to deliver any encryption key to the client, it is purely internal to the proxy that manages the encryption/devyption keys internally. Also this encryption will not increase the length of short URLs.\n', '\n', '[[User:Verdy p|verdy_p]] ([[User talk:Verdy p|talk]]) 19:51, 21 August 2013 (UTC)\n']","19:51, 21 August 2013 (UTC)",Verdy p
+"['\n', ':Commons and upload.wikimedia.org (where images are actually served from) support HTTPS. All of our projects have fully supported HTTPS for quite some time now.--[[User:Ryan Lane (WMF)|Ryan Lane (WMF)]] ([[User talk:Ryan Lane (WMF)|talk]]) 01:08, 29 August 2013 (UTC)\n']","01:08, 29 August 2013 (UTC)",Ryan Lane (WMF)
+"['== Loss of browser history ==\n', '\n', 'I just had cause to use Internet Explorer and it seems as though it was not saving history for https pages. I have not investigated fully but if I was forced to use Internet Explorer, I would prefer to be subject to snooping by the NSA than lose my browsing history. [[User:RHaworth|RHaworth]] ([[User talk:RHaworth|talk]]) 21:07, 21 August 2013 (UTC)\n']","21:07, 21 August 2013 (UTC)",RHaworth
+"['== Impossible Log out ==\n', ""Since tonight, I can not log out. It's some feature of https? --[[User:ŠJů|ŠJů]] ([[User talk:ŠJů|talk]]) 20:50, 22 August 2013 (UTC)\n""]","20:50, 22 August 2013 (UTC)",ŠJů
+"["": I usually use the secure login and have never had that problem, so I wouldn't say it's a feature. Did you try going to [[Special:UserLogout]], at least o the secure server? [[Special:Contributions/72.252.242.170|72.252.242.170]] 23:20, 22 August 2013 (UTC)\n""]","23:20, 22 August 2013 (UTC)",72.252.242.170
+"[':: The page [[Special:UserLogout]] appeared and the login from the top of the page dissappeared but in 1 or 2 second appeared again. However, the bug seems to be eliminated now. --[[User:ŠJů|ŠJů]] ([[User talk:ŠJů|talk]]) 00:53, 23 August 2013 (UTC)\n']","00:53, 23 August 2013 (UTC)",ŠJů
+"['== http/https link embedded in wiki text using the link tool … ==\n', '\n', '… does not work. If you select the link tool, and paste an url, it should be stripped off the protocol to get protocol relative urls automatically. At least for WP links like this (completely arbitrary): https://de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 the link tool shall strip the protocol. Adding //de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 to the link tool will create [http:////de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 //de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984] (url with prefix http:////de.wikipedia.org). Furthermore the wiki text (protocol relative url) //de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 should autolink like the non-protocol-relative-url does. --[[User:Herzi Pinki|Herzi Pinki]] ([[User talk:Herzi Pinki|talk]]) 23:02, 22 August 2013 (UTC)\n']","23:02, 22 August 2013 (UTC)",Herzi Pinki
+"['== API ==\n', '\n', 'Is this going to affect browser logins only, or will pure API sessions (those that occur outside a browser environment) be affected as well? [[User:This, that and the other|This, that and the other]] ([[User talk:This, that and the other|talk]]) 09:17, 25 August 2013 (UTC)\n']","09:17, 25 August 2013 (UTC)","This, that and the other"
+"[': This is only for browser logins, the api does not force a redirect [[User:CSteipp|CSteipp]] ([[User talk:CSteipp|talk]]) 22:47, 26 August 2013 (UTC)\n']","22:47, 26 August 2013 (UTC)",CSteipp
+"['== Causing problems ==\n', '\n', 'I have disabled this in my preferences, as the default left me totally unable to edit, or even view, Wikipedia. (Every time I clicked on a link, or even typed in a url, I was switched to an https url, with a popup window ""couldn\'t parse page name from url ..."". Previously, if directed to an https page, I have had to remove the s in order to open the page, but the new change made this impossible. Eventually I managed to open my preferences, find the relevant entry, and uncheck the tick; now everything works smoothly again.\n', '\n', 'I have no idea what is causing the problem; whether it is my Wikipedia gadgewts, my Firefox add-ons, or my security settings. Nor do I feel inclined to experiment and see what tweaks, if any, would resolve the problem. But it is clear to me that this change should not become a default, or be made mandatory, since this would certainly lock out readers and editors.\n', '\n', 'If anyone responds to this, please inform me at [http://en.wikipedia.org/wiki/User_talk:RolandR my talk page on English Wikipedia]; I have never before visited Wikimedia. [[User:RolandR|RolandR]] ([[User talk:RolandR|talk]]) 00:13, 29 August 2013 (UTC)\n']","00:13, 29 August 2013 (UTC)",RolandR
+"['\n', "": I'm pretty sure this is due to a script you have installed (as I indicated on the VPT thread). [https://en.wikipedia.org/w/index.php?title=User%3AQuarl%2Fwikipage.js&diff=570605025&oldid=38600544 I fixed it]. [[User:^demon|^demon]] ([[User talk:^demon|talk]])\n"", '::That doesn\'t seem to have resolved the problem. I re-enabled the secure login in my preferences, and again started to get the ""couldn\'t parse page name"" pop-up. Which of my scripts might be causing this? [[User:RolandR|RolandR]] ([[User talk:RolandR|talk]]) 10:56, 29 August 2013 (UTC)\n']","10:56, 29 August 2013 (UTC)",RolandR
+"[':::In fact, this seems to have made the problem worse; now, although I have unticked the checkbox in Preferences, every link defaults to https, and I am unable to open any page easily. Please help! [[Special:Contributions/86.186.105.211|86.186.105.211]] 11:10, 29 August 2013 (UTC)\n']","11:10, 29 August 2013 (UTC)",86.186.105.211
+"['::::If you wish to change the HTTPS setting back to HTTP, try going to [{{fullurl:en:Special:Preferences|useskin=modern}}] or [{{fullurl:en:Special:Preferences|useskin=cologneblue}}].\n', '::::If you wish to fix the problem, try going to [[w:User:RolandR/monobook.js]] and [[w:User:RolandR/vector.js]] and change ""http://"" to ""//"" everywhere on the pages. The JS files can only be edited by you or by an administrator at English Wikipedia.\n', ""::::If this doesn't help, then it probably means that something is wrong in one of the scripts that you are importing. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 12:31, 29 August 2013 (UTC)\n""]","12:31, 29 August 2013 (UTC)",Stefan2
+"['\n', 'Hello,\n', '\n', ""I also have some problems. First, I didn't get the images until I clicked to access a Commons page and validate the security certificate; now solved. But it seems the scripts don't work. I have no personnalised JS or CSS (the /monobook.js page or the like don't exist).\n"", '\n', 'Any clue?\n', '\n', '[[User:Cdang|Cdang]] ([[User talk:Cdang|talk]]) 13:46, 29 August 2013 (UTC)\n']","13:46, 29 August 2013 (UTC)",Cdang
+"['== Google Translate ==\n', '\n', 'When I paste ""https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Gadgets"" into either http://translate.google.com/ or https://translate.google.com/ I get the message:\n', ': Google Error\n', ': Sorry, this URL is invalid\n', ': http://fr.wikipedia.org:443/wiki/Sp%C3%A9cial:Gadgets\n', 'But when I paste the regular ""http://fr.wikipedia.org/wiki/Sp%C3%A9cial:Gadgets"", it translates it fine. Can someone attest that this is a Wikimedia problem and, if so, submit a bug about it? - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 08:37, 29 August 2013 (UTC)\n']","08:37, 29 August 2013 (UTC)",Dcljr
+"[':Looks like a bug in the google tool to me... Apparently it has existed [http://ubuntuincident.wordpress.com/2011/02/07/patch-to-google-translate-https-pages/ for years] already. Perhaps WMF operations can tickle their google contacts a bit. [[User:TheDJ|TheDJ]] ([[User talk:TheDJ|talk]]) 11:52, 29 August 2013 (UTC)\n']","11:52, 29 August 2013 (UTC)",TheDJ
+"[""::I've had this problem ever since I started using HTTPS (a while ago). It's a problem with Google Translate. {{ping|Snowolf}} didn't you write to a mailing list about this last year? [[User:PiRSquared17|PiRSquared17]] ([[User talk:PiRSquared17|talk]]) 18:55, 31 August 2013 (UTC)\n""]","18:55, 31 August 2013 (UTC)",PiRSquared17
+"[':::I did. I don\'t think they ever replied to me. <i><b>[[User:Snowolf|<font color = ""darkmagenta"">Snowolf</font>]] <sup><small>[[User talk:Snowolf|<font color = ""darkmagenta"">How can I help?</font>]]</small></sup></b></i> 22:09, 31 August 2013 (UTC)\n']","22:09, 31 August 2013 (UTC)",Snowolf
+"["":::: Hmm. Maybe now that Wikimedia is going HTTPS for all logged-in users on all projects, they'll get more pressure to do something about it. - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 01:26, 2 September 2013 (UTC)\n""]","01:26, 2 September 2013 (UTC)",Dcljr
+"['\n', 'I work for Google, and got the following answer from <b> Google Translate team: </b> <br>\n', '""Currently, the Google proxy-based web translation cannot translate HTTPS pages. It\'s a known limitation, and we\'d like to remove that limitation.""\n', "": OK, well, there's a very easy fix for that… - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 02:23, 17 September 2013 (UTC)\n""]","02:23, 17 September 2013 (UTC)",Dcljr
+"['== [[HTTPS#Various small problems]] ==\n', '\n', 'I added this section to help users particularly with script problems or certificate problems. Be bold at rewriting it or adding issues, I have only my own experience of HTTPS problems or those reported on the village pumps (although always difficult to precisely understand what is wrong and consider solutions).\n', '\n', 'For the scripts I guess this is quite important and many editors could wonder why their scripts suddently do no more work, see these few searches: [//fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Recherche&limit=20&offset=20&redirs=1&ns2=1&search=loadjs] (search the exact case loadJS), [//en.wikipedia.org/w/index.php?title=Special%3ASearch&limit=20&offset=20&redirs=1&ns2=1&search=loadjs], [https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=js+write&fulltext=Search&ns2=1&redirs=1&profile=advanced], [https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=js+http&fulltext=Search&ns2=1&redirs=1&profile=advanced]; even, some users call external scripts (sometimes the destination server don’t support https). For these scripts, I don’t know what exactly should be prefered, is it <code>importScriptURI</code>? not <code>mw.loader.load</code>?\n', '\n', 'About the Authority certificate (DigiCert High Assurance EV Root CA), is there known issues with the devices which don’t have it in their certificate repository? I use to see it on the Internet and with my browsers (Opera, Firefox), but perhaps there are exotic devices or browsers or operating systems or combinaisons of these ones which don’t recognize it. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 19:15, 29 August 2013 (UTC)\n']","19:15, 29 August 2013 (UTC)",Seb35|<small>[^_^]<
+"['== Help Needed: Problems due to Secure site change ==\n', '\n', ""I'm not even sure how I found my way here to this page, but I am in desperate need of help, as nothing I have tried has made any real difference. Rather than repeat what I've already written over at Wikipedia, I am going to re-post my own initial comment, followed by the entire contents of the discussion that ensued when I created a new section under the same heading I've used here -- which I think may be useful for other editors to read. [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 07:08, 2 September 2013 (UTC)\n""]","07:08, 2 September 2013 (UTC)",Cgingold
+"['== My experience with HTTP links ==\n', '\n', 'The instructions here say, ""\'\'If a user wants to login, the login will happen over HTTPS… and after they are logged in they stay on the HTTPS version of the Wikimedia site they are using.\'\'"" We-e-ell... I suppose this is \'\'technically\'\' true, but it doesn\'t quite work the way most people would expect.\n', '\n', 'After logging out and logging in again a couple of days ago (on the English Wikipedia) under the new HTTPS regime, I noticed that when following HTTP links to most other Wikimedia wikis from e-mails and bookmarks, I was not showing up as being logged in (was arriving under the HTTP protocol, of course). My bookmarks to the English Wikipedia and Meta seemed to be okay (I have visited those since the changeover, so presumably I already did something to fix the problem there), but if I tried my bookmark to, say, the Italian Wikibooks (to choose a random one I hadn\'t visited in a while), I showed up as being logged out. Reloading didn\'t help. Reloading bypassing the cache didn\'t help. Manually typing in the prefix ""https://"" in the address bar... that did it. Then I was logged in. (So... I have to actually use HTTPS to ""remind"" WM that I\'m already logged in as a registered user?)\n', '\n', 'Needless to say, I didn\'t want to manually type in a protocol every time I visited a new Wikimedia wiki (I help to maintain [[Wikimedia News]], so I have occasion to visit ""random"" WM wikis \'\'all the time\'\')! So I did something I \'\'really\'\' hate doing: I cleared all my cookies. And all my cookie settings (allow/deny/etc.). And my cache. And my browsing history. And then I closed and reopened Firefox (17.0.7).\n', '\n', 'After logging in to the English Wikipedia (my ""home wiki"") again, I found that when I first visited another WM site (in this case, Meta) — via a regular wikilink, no less... not even bookmarks or e-mail links yet — I showed up as \'\'not logged in\'\'! (And I had to accept a new cookie, which I expected, of course.) Then on to Commons: \'\'not logged in\'\'! Hey! Whatever happened to SUL?? Okay, so then I reloaded the page. Only then did it tell me ""You are centrally logged in… Reload the page to apply your user settings."" Okaaay. Reloaded a second time. Fine. But before reloading, I noticed that I was actually \'\'already\'\' logged in as me after the first reload. Something\'s screwy here... Finally, by going to another ""new"" wiki, I noticed that the first and second reloads can be replaced by two ""local"" page loads of any sort (i.e., following links to other pages on the same wiki). In other words, I\'m not logged in when I first bring up a wiki (a Main Page, in particular), but after either reloading or following an internal link, I am logged in. But only \'\'then\'\' do I get the message about ""[applying my] user settings"". But at that point that\'s already been done! Something tells me this is not how it\'s supposed to work.\n', '\n', ""So then I tried an old HTTP bookmark (this time to the Czech Wikipedia — remember, I first logged in to the English Wikipedia). Not logged in. Not in HTTPS. Reloading didn't work. Back to where I started. So then I navigate through HTTPS links (via [[List of Wikipedias]]) back to the Czech Wikipedia. I ''am'' logged in under HTTPS. Okay, back to the List and then to the, oh, Ilokano Wikipedia. I am logged in under HTTPS.\n"", '\n', ""Hmm. Okay, back to an HTTP ''bookmark'' to the Ilokano Wikipedia. Nope. HTTP and not logged in. (But I was just here! Don't you recognize me?) Finally, to an HTTP bookmark to the English Wikipedia. This time, mercifully, I show up as logged in under HTTPS.\n"", '\n', 'So, the moral of this story seems to be: If you explicitly log in to a Wikimedia wiki, HTTP links to that wiki will come up as HTTPS and have you logged in. Following links to any other Wikimedia wiki (assuming they\'re HTTPS) works, but only after reloading or following a link. But visiting any other wiki through an HTTP link, even though you have purportedly been ""CentralAuth"" logged in to ""all"" of them, you don\'t get recognized as being logged in and remain an anon under HTTP. Pretty annoying.\n', '\n', 'So now I have to go through 820 or so bookmarks changing ""http:"" to ""https:"" (not to mention actually visiting all 820 wikis again to set new cookies). Yay. - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 10:45, 2 September 2013 (UTC)\n']","10:45, 2 September 2013 (UTC)",Dcljr
+"[':When I got ""You are centrally logged in… Reload the page to apply your user settings."", I checked [[Special:Preferences]] and found that the setting for ""Always use a secure connection when logged in"" was opposite to what I thought it was. Flipping it and saving, then reloading the appropriate page, got things back in synch. It was necessary to do this separately for meta, commons, etc. --[[User:Redrose64|Redrose64]] ([[User talk:Redrose64|talk]]; [[:en:User:Redrose64|at English Wikipedia]]) 12:09, 2 September 2013 (UTC)\n']","12:09, 2 September 2013 (UTC)",Redrose64
+"['::Is this [[bugzilla:53538]]? --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 13:40, 2 September 2013 (UTC)\n']","13:40, 2 September 2013 (UTC)",Stefan2
+"[':::: My original report? Yeah, looks like it (although the thing about the late ""centrally logged in"" notice isn\'t mentioned there). I guess we\'ll see what happens when 1.22wmf16 is deployed ([[mw:MediaWiki 1.22/Roadmap|over the next few days]]). - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 12:47, 5 September 2013 (UTC)\n']","12:47, 5 September 2013 (UTC)",Dcljr
+"["":::I've been having some trouble staying logged in between projects (i.e. Commons) for a long time - well before https.  But it happens only when I have some scripts enabled (NoScript), and admittedly... I might not have had them all enabled at the start, and so gotten to some state unexpected by the developers.  Have you been using the same sort of script control? [[User:Wnt|Wnt]] ([[User talk:Wnt|talk]]) 18:00, 2 September 2013 (UTC)\n""]","18:00, 2 September 2013 (UTC)",Wnt
+"['::::What browser are you using? If the problem is that you are logged in when you use HTTPS but not when you use HTTP, then you might wish to install [https://www.eff.org/https-everywhere HTTPS Everywhere], provided that you use a browser compatible with that. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 18:20, 2 September 2013 (UTC)\n']","18:20, 2 September 2013 (UTC)",Stefan2
+"['== Updates on the Https situation ==\n', ""['''Note''': I've copied this from the Village Pump (technical) talk page over at Wikipedia.]\n"", ""*'''Update1''' - Hmmm. Has something been tweaked on ''your'' end? (i.e. some lines of code at Wikipedia/Wikimedia?) Just in the last hour I discovered that I was able to access Http pages while I'm logged in -- which I was NOT able to do before (except for a very short period over the weekend). They're also showing up in my browser history, as expected. And I can see that HotCat has returned, as well (though I haven't tried using it as of yet). However -- you knew that was coming, didn't you?? -- there's still some work to be done: When I accessed a couple of articles via redirects, they displayed as though I had suddenly logged out, even though I hadn't done so and was in fact ''demonstrably still logged in!'' (The links on those pages took me to normal pages that displayed properly.) I'll post another update later on today. Needless to say, I'm keeping my fingers crossed that things won't revert to dysfunctionality in the next couple of hours! [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 14:48, 2 September 2013 (UTC)\n""]","14:48, 2 September 2013 (UTC)",Cgingold
+"[""::'''Addendum''' to Update1: Complicating the picture I described in my update above, I just had a couple of pages accessed via redirects display ''properly'' -- but a couple of Category pages displayed improperly, as though I had logged out. So it seems there's no real pattern to whatever the hell is going on. <sigh> [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 15:33, 2 September 2013 (UTC)\n""]","15:33, 2 September 2013 (UTC)",Cgingold
+"['*\'\'\'Update2\'\'\' - Okay, it is now many hours later in the day. The positive developments I noted earlier have held up without reverting to the intractable problems I experienced over the weekend. For the most part, I am able to access Http pages and they display properly -- i.e. the Wiki software recognizes that I am logged in. I can also report that HotCat is functioning normally for me -- another major relief. However, there is still a recurring problem that crops up in a \'\'seemingly\'\' random fashion, causing certain pages to display as though I was not logged in -- even though I can go directly to other pages that display normally, without having had to log in again first. I suspect, however, that these problem pages may not be \'\'entirely\'\' random -- iow, they may possibly have some feature in common that results in problems with the new software -- mainly because certain pages continue to exhibit this problem every time I access them. Case in point: [[:Category:Biological evolution]], which displays as though I\'m just an Anon. IP editor every time.  Guess that\'ll do it for now. I hope I\'ve given you techies enough ""hints"" to make some headway in tracking down the source of the problem. :) [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 04:32, 3 September 2013 (UTC)\n']","04:32, 3 September 2013 (UTC)",Cgingold
+"['== Security information ==\n', '\n', 'When browsing wikipedia (via firefox, if it makes a difference), now in https, getting the security information by pressing the lock icon next to the URL, the browser reports ""you are connected to wikipedia.org which is run by (unknown)"". Similarly, meta.wikimedia.org is also reported ""unknown"". When clicking ""more information"" the browser reports under identity ""owner: This website does not supply ownership information"". Methinks this warrants correction. [[Special:Contributions/87.68.44.102|87.68.44.102]] 10:02, 4 September 2013 (UTC)\n']","10:02, 4 September 2013 (UTC)",87.68.44.102
+"['\n', "":I was curious, and checked, 12 days later. Using Google Chrome browser, both the identity and certificate seem proper, as <code>meta.wikimedia.org</code>, using SSL with DigiCert High Assurance CA-3 and 128-bit encryption connection SHA-1. I didn't check the entire CA chain, I confess. --[[User:FeralOink|FeralOink]] ([[User talk:FeralOink|talk]]) 13:26, 20 September 2013 (UTC)\n""]","13:26, 20 September 2013 (UTC)",FeralOink
+"['==Wikimedia sites and tracking, documentation==\n', '\n', ""First, I wanted to mention that HTTPS is working perfectly for me, every time, on every WMf site, with the possible exceptions of Wikidata. '''Thank you'''!\n"", '\n', 'Earlier, on 21 August 2013, inquiries were made by [[User:Risker|Risker]]\n', '<blockquote>""Please add a link to some formal statement or roadmap or approved plan that says ""[t]he continued work to improve the security and privacy of Wikimedia project users is a stated goal of the Wikimedia Foundation"". (I\'m not doubting it\'s true, but a footnote/reference helps.) It might also be useful to link to some internal or external site that confirms the use of Wikipedia as a site useful for tracking""</blockquote> and by [[User:Ace111|Ace111]]\n', '<blockquote>""The preamble of this article mentions: ""The Wikipedia project was referenced in several documents as a specific source for tracking users\' behavior online"". Which documents are referenced here? Was it discussed somewhere?""</blockquote>\n', 'These concerns were acknowledged and action was taken to address them by [[User:Seb35|Seb35]]\n', '<blockquote>""I just added a link to one document I know, but I don’t know others.""</blockquote>\n', ""However, I agree with [[User:Ace111|Ace111]]'s subsequent response:\n"", '<blockquote>""Jimbo\'s twitter post refers to [http://www.theguardian.com/world/2013/jul/31/nsa-top-secret-program-online-data an NSA slide via The Guardian] with a question: ""Why are we interested in HTTP?"" and an answer ""Because nearly everything a typical user does on the Internet uses HTTP"", followed by examples of web sites such as Facebook, Yahoo, Twitter, myspace, CNN, mail.ru, Wikipedia, Google and Gmail. I don\'t think this is a proper reference for Wikipedia as a specific source for tracking users\' behavior.""</blockquote>\n', ""[https://twitter.com/jimmy_wales/status/362626509648834560 Jimmy Wales' Twitter message] reads as follows:\n"", '<blockquote>NSA snooping on what YOU are reading at Wikipedia means I want us to go to SSL sooner.  Bastards fuck off. Owly <!-- hxxp owly/nv3I6 Owly is a blacklisted site, so I sorta-obfuscated --></blockquote> \n', 'The Owly-shortened URL directs to [http://static.guim.co.uk/sys-images/Guardian/Pix/audio/video/2013/7/31/1375269604628/KS8-001.jpg this image via The Guardian], which I haven\'t uploaded, though I guess I should. It is not a COPYVIO, as it is an alleged screen shot of antiquated social media icons in the characteristically MS Paint, circa Win 95 style, of PRISM slides. There is some lettering at the top, in light orange colored font, on a darker orange background, which might say ""COMINT"" (or maybe HUMINT or NOfORN or one of those other acronyms we\'ve had 4 months with which to become familiar). That isn\'t suficient as a proper reference for Wikipedia as a specific source for tracking users\' behavior, just as Ace111 said.  In fact, Jimmy Wales message was directly [https://twitter.com/StevenWalling/status/363397737254879232 replied to by Steven Walling]\n', '<blockquote>""the Foundation has not received any requests to date"" https://blog.wikimedia.org/2013/07/18/wikimedia-foundation-letter-transparency-nsa-prism/ …</blockquote> which leads me to wonder whether there were evidence of tracking by the NSA of Wikipedia users and/ or editors et al. Next, even though he sounds full of bravado, the content of Jimmy Wales\' Twitter message is rather hostile, specifically,\n', "":'''Bastards fuck off.'''\n"", ""Jimmy Wales as an individual is entitled to tell the NSA to fuck of. But using his personal Twitter account as the basis for Wikimedia's decision to transition to SSL, with that particular content, is representing Wikimedia foundation I would think. We don't tell any government entity to fuck of as official policy, I don't think. We didn't tell Khazakhastan to fuck of, nor Syria, nor Libya, nor North Korea, nor the Taliban. I don't need to list further ''bete-noire'' perceived countries, as you get the idea.  Remember, the NSA is acting as explicitly directed by the elected government of the USA, the executive branch and/ or the Department of Homeland Security. Bad men tell the NSA to do bad things.\n"", '\n', ""I don't want that Twitter message linked in the article, here, please? I fully agree with, and applaud Wikimedia's decision to transition to HTTPS and SSL. If further encryption measures are added in the future, I wouldn't argue against it. \n"", '\n', 'In fact, why is there any need to justify the switch to HTTPS at all? Someone needs to find some non-self-referential external source (or provide better detail from this one, The Guardian article, not Jimmy Wales), or just delete that section entirely, and thus resolve the pesky issue of explaining why SSL is needed. I will take it upon myself to do so, but wanted to explain myself first, and generate discussion, as the AfD folks say!  --[[User:FeralOink|FeralOink]] ([[User talk:FeralOink|talk]]) 01:22, 17 September 2013 (UTC)\n']","01:22, 17 September 2013 (UTC)",FeralOink
+"['== Still being forced into using HTTPS on occasion ==\n', '\n', ""Just now, I had to go thru the once every 30 days log in again.  And despite having that I do NOT want HTTPS, it forced me into HTTPS and I had go and manually delete the cookies yet again!  I understand why you are advocating HTTPS, but they don't apply to me or my use of Wikimedia, so I like to keep things as simple as possible. It's bad enough that each time I visit a Wikimedia site I haven't used since the change I have to go change the preferences for that site to undo the automatic HTTPS, but to have to keep deleting cookies is even worse. [[User:Carolina wren|Carolina wren]] ([[User talk:Carolina wren|talk]]) 02:15, 29 September 2013 (UTC)\n""]","02:15, 29 September 2013 (UTC)",Carolina wren
+"[': This sounds like [[bugzilla:54626|bug 54626]], the fix for which should be deployed starting on Thursday, October 3 and finishing up on October 10. Unless it gets pushed out sooner. [[User:BJorsch (WMF)|BJorsch (WMF)]] ([[User talk:BJorsch (WMF)|talk]]) 13:58, 30 September 2013 (UTC)\n']","13:58, 30 September 2013 (UTC)",BJorsch (WMF)
+"['== Preference ==\n', 'After this program is implemented, will individual contributors still be able to disable HTTPS if so they desire? [[User:Gryllida|Gryllida]] 22:21, 17 September 2014 (UTC)\n']","22:21, 17 September 2014 (UTC)",Gryllida
+"[': Why is the above question written in the future tense? This was implemented last year. Individual contributors can disable HTTPS at [[Special:Preferences#mw-prefsection-personal]] by unchecking the ""Always use a secure connection when logged in"" checkbox. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 22:52, 17 September 2014 (UTC)\n']","22:52, 17 September 2014 (UTC)",Stefan2
+"[""::I'm referring to the planned change.  In October 2014, some projects (not globally; currently this is on Russian Wikipedia) plan to roll out https by default to unregistered contributors. Some others are considering following their example and I'm trying to access the implications of such change. [[User:Gryllida|Gryllida]] 23:03, 17 September 2014 (UTC)\n""]","23:03, 17 September 2014 (UTC)",Gryllida
+"[""== API from contributor's username ==\n"", 'I understand that the program implies that where I visit a page, I will be automatically redirected to HTTPS.  Will the same happen for API queries I send from a bot/script? [[User:Gryllida|Gryllida]] 22:21, 17 September 2014 (UTC)\n']","22:21, 17 September 2014 (UTC)",Gryllida
+"[""::I'm referring to the planned change.  In October 2014, some projects (not globally; currently this is on Russian Wikipedia as a result of community consencus) plan to roll out https by default to unregistered contributors. Some others are considering following their example and I'm trying to access the implications of such change. [[User:Gryllida|Gryllida]] 23:04, 17 September 2014 (UTC)\n""]","23:04, 17 September 2014 (UTC)",Gryllida
+"['== Common HTTPS access issues ==\n', 'What is the common nature of the HTTPS access issues the https{{@}}wikimedia.org folks encounter, as suggested [[HTTPS#Help.21|here]]? I e-mailed them in but got no response. I would like to know who we would be locking out here and why. [[User:Gryllida|Gryllida]] 22:21, 17 September 2014 (UTC)\n']","22:21, 17 September 2014 (UTC)",Gryllida
+"[': HTTPS access is or has been blocked by the authorities in some countries (see [[{{SUBJECTPAGENAME}}#Excluded Countries]]). I assume that users in these countries may run into problems if they have to use an HTTPS connection. I do not know if users also may have other problems. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 22:55, 17 September 2014 (UTC)\n']","22:55, 17 September 2014 (UTC)",Stefan2
+"[':I was told that this was addressed by extensive EventLogging tests that didn\'t reveal trouble of ""random crappy ISP setup"" sort, but only revealed country-specific issues (and this program is being rolled out outside of these countries as I understand). Would be useful to have some documentation of tests, for reference. [[User:Gryllida|Gryllida]] 22:57, 17 September 2014 (UTC)\n']","22:57, 17 September 2014 (UTC)",Gryllida
+"['== Opting out for unregistered contributors ==\n', ""This is perhaps a slightly useless question, as the folks can use another internet access point to register, and opt out ''then'' (if the preference is still available). But is there currently no means to opt out ''without'' registering? See also [[bugzilla:20151]]. Can we think about it again? To me, a lot of preferences appear to be harmless to expose to IP contributors (HTTPS/HTTP toggle being one of them). [[User:Gryllida|Gryllida]] 22:57, 17 September 2014 (UTC)\n""]","22:57, 17 September 2014 (UTC)",Gryllida
+"["":To clarify: I'm referring to the planned change.  In October 2014, some projects (not globally; currently this is on Russian Wikipedia) plan to roll out https by default to unregistered contributors. Some others are considering following their example and I'm trying to access the implications of such change. [[User:Gryllida|Gryllida]] 23:04, 17 September 2014 (UTC)\n""]","23:04, 17 September 2014 (UTC)",Gryllida
+"[""::Where do I find information about the planned change? I hadn't heard of it until you mentioned it on this talk page.\n"", ""::Users who are not logged in can still change many settings by using a tool such as [[w:Greasemonkey]]. However, I realise that this method isn't very user-friendly. I don't know if this method provides a way to opt out from forced HTTPS.\n"", ""::Are you suggesting that some users won't be able to visit any Russian Wikipedia pages (including [[:ru:Special:UserLogin]]?) unless the users are logged in when the page is accessed? --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 23:28, 17 September 2014 (UTC)\n""]","23:28, 17 September 2014 (UTC)",Stefan2
+"[':::I have no idea what plans Gryllida is talking about, but official plans are at [[mw:Wikimedia Engineering/2014-15 Goals#Site Operations and Site Architecture]].\n', ':::So far zh.wiki and others had an opt-out from the forced HTTPS for registered users but I seriously doubt there will be any opt-in mechanism for further HTTPS changes. --[[User:Nemo_bis|Nemo]] 06:06, 18 September 2014 (UTC)\n']","06:06, 18 September 2014 (UTC)",Nemo_bis
+"[""::::No, they don't plan access changes. [[:ru:Википедия:Форум/Архив/Предложения/2013/09#.D0.92.D0.BA.D0.BB.D1.8E.D1.87.D0.B5.D0.BD.D0.B8.D0.B5_.D0.BF.D1.80.D0.BE.D1.82.D0.BE.D0.BA.D0.BE.D0.BB.D0.B0_https_.D0.B4.D0.BB.D1.8F_.D0.B2.D1.81.D0.B5.D1.85_.D0.BF.D0.BE.D0.BB.D1.8C.D0.B7.D0.BE.D0.B2.D0.B0.D1.82.D0.B5.D0.BB.D0.B5.D0.B9|Local consensus]] at Russian Wikipedia. Oh, and they opted in [[HTTPS/Beta_program|here]]. [[User:Gryllida|Gryllida]] 09:09, 18 September 2014 (UTC)\n""]","09:09, 18 September 2014 (UTC)",Gryllida
+"[':: [[User:Gryllida|Gryllida]], Where did you find this date ""October 2014"", сan you give a link to us? [[User:Sunpriat|Sunpriat]] ([[User talk:Sunpriat|talk]]) 20:08, 26 September 2014 (UTC)\n']","20:08, 26 September 2014 (UTC)",Sunpriat
+"['== Russian Wikinews ==\n', 'Please, let me know when you turn on HTTPS for [[n:ru:|Russian Wikinews]] ([https://meta.wikimedia.org/w/index.php?diff=9957749&oldid=5989231 diff]). --sasha ([[User:Krassotkin|krassotkin]]) 07:36, 22 September 2014 (UTC)\n']","07:36, 22 September 2014 (UTC)",Krassotkin
+"['* [https://ru.wikinews.org/w/index.php?diff=336990&oldid=336650 Done]. Thanks! --sasha ([[User:Krassotkin|krassotkin]]) 07:16, 5 December 2014 (UTC)\n']","07:16, 5 December 2014 (UTC)",Krassotkin
+"['== Performance impact ==\n', '\n', 'Do performance issues with HTTPS show up in any way on navigation timing EventLogging logs like those from which [https://gdash.wikimedia.org/dashboards/frontend/] is extracted? Consider the case ""the page takes so long to load over HTTPS that it times out in my browser"" for people with extremely slow connections. It would be nice to be at least \'\'able\'\' to assess the impact on specific countries or Wikimedia subdomains, for instance. IIRC even the simple but often-quoted [https://docs.google.com/presentation/d/1MtDBNTH1g7CZzhwlJ1raEJagA8qM3uoV7ta6i66bO2M/present] mention this need for breakdown. --[[User:Nemo_bis|Nemo]] 13:25, 12 June 2015 (UTC)\n']","13:25, 12 June 2015 (UTC)",Nemo_bis
+"['==Turning off HTTPS==\n', 'This article\'s content states: ""If so, you can turn off HTTPS in your user preferences (unless HSTS is set for the domain in question[2]). Go to the ""User profile"" tab, then uncheck the box labelled ""Always use a secure connection when logged in"". You will need to logout and login for the preference to take effect. But remember, you will still need to log in using HTTPS.""  Up until today, I did not use HTTPS and was editing just fine.  Today, I am being forced to use HTTPS and there is nothing in the preferences screen for me to control this.  I don\'t want HTTPS (loss of saved edit summary info).  What can I do to get back to HTTP? [[User:Hmains|Hmains]] ([[User talk:Hmains|talk]]) 17:14, 12 June 2015 (UTC)\n']","17:14, 12 June 2015 (UTC)",Hmains
+"["":Sorry, that's entirely my fault for not keeping this page as up to date as I'd had hoped to. This is the answer I got when I asked was that any form of opt-out would also leave potential security risks in our implementation which make it difficult to safeguard those who do not opt-out.  Because of this, we’ve made implementation decisions that preclude any option to disable HTTPS, whether logged in or not.  This renders the current opt-out option ineffective, and the option will be removed at a later date after we’ve completed the transition process.\n"", "":I'm trying to figure out if there's a good solution to the edit summary info problem. /[[User:Johan (WMF)|Johan (WMF)]] ([[User talk:Johan (WMF)|talk]]) 19:27, 12 June 2015 (UTC)\n""]","19:27, 12 June 2015 (UTC)",Johan (WMF)
+"['== Bots ==\n', '\n', '""API requests are now being forced redirected to HTTPS on some languages. On most bot frameworks, this should just work, but a few bot maintainers have reported problems. If your bot has problems, make sure that the library you are using supports HTTPS, and has access to appropriate root certificates.""\n', ""*How do you fix a library that doesn't support https to make it support that?\n"", '*What are root certificates, and what do I need to do regarding that?\n', ""*Why is this notice posted ''after'' implementation?\n"", ""*My library (see [[en:User:RMCD bot/botclasses.php]]) is something I got off of the now-defunct German tool server, and was written by guys who have all apparently retired from Wikipedia, so I guess I need to assume the job of maintaining it, though I'm not really sure that someone isn't still maintaining it somewhere.\n"", ""*I've been aware of this (potential) issue since last December: [[en:Wikipedia:Village pump (technical)/Archive 133#PHP API for #ifexist function?]] My [[en:special:diff/638797589|last question in that thread]] never got a response.\n"", '[[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 12:26, 14 June 2015 (UTC)\n']","12:26, 14 June 2015 (UTC)",Wbm1058
+"['== HTTPS timeout with curl and wget ==\n', '\n', 'Running these commands:\n', '\n', '*curl -s --trace o ""https://en.wikipedia.org/wiki/Charlies""\n', '*wget -q -O- ""https://en.wikipedia.org/wiki/Charlies""\n', '\n', 'Results in intermittent timeouts as reported by the debug feature of both programs. It might work 3 times in a row then hang on the 4th etc..\n', '\n', ""Traceroute shows I am located 10 hops from 208.80.154.224 in Virginia with a 6ms ping time with no dropped packets. I'm on Verizon FIOS. \n"", '\n', 'Problem started the same time HTTPS was implemented. \n', '\n', 'curl debug (curl -s --trace o ""https://en.wikipedia.org/wiki/Charlies""):\n', ' == Info: timeout on name lookup is not supported\n', ' == Info: About to connect() to en.wikipedia.org port 443 (#0)\n', ' == Info:   Trying 208.80.154.224...\n', ' == Info: Timed out\n', "" == Info: couldn't connect to host\n"", ' == Info: Closing connection #0\n', '\n', 'wget debug (wget -d -q -O- ""https://en.wikipedia.org/wiki/Charlies""):\n', ' Setting --quiet (quiet) to 1\n', ' Setting --output-document (outputdocument) to -\n', ' DEBUG output created by Wget 1.16.3 on cygwin.\n', ' URI encoding = ‘UTF-8’\n', ' Certificates loaded: 170\n', ' Caching en.wikipedia.org => 208.80.154.224 2620:0:861:ed1a::1  <-- note: hangs here\n', ' Closed fd 4\n', ' Closed fd 4\n', ' Releasing 0x800ce0c0 (new refcount 1).\n', '\n', '-- [[User:Green Cardamom|Green Cardamom]] ([[User talk:Green Cardamom|talk]]) 14:49, 17 June 2015 (UTC)\n']","14:49, 17 June 2015 (UTC)",Green Cardamom
+"['\n', ""::In case anyone has similar timeout problems, I've worked around it with this:\n"", '::: wget --retry-connrefused --waitretry=1 --read-timeout=2 --timeout=2 --no-dns-cache -q -O- ""https://en.wikipedia.org/wiki/Charlies""\n', '::This is working. Might need to adjust the 2 second delay depending on your connection speed. If there is no response within 2 seconds (--timeout) It will retry 20 times .. but usually succeeds after the first retry. -- [[User:Green Cardamom|Green Cardamom]] ([[User talk:Green Cardamom|talk]]) 15:12, 17 June 2015 (UTC)\n']","15:12, 17 June 2015 (UTC)",Green Cardamom
+"[':::Ping: [[User:BBlack (WMF)]]. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 03:25, 18 June 2015 (UTC)\n']","03:25, 18 June 2015 (UTC)",Bawolff
+"[""::::I don't think we're seeing this behavior in the general case (stats haven't shown it, and I can't reproduce it -- tried from a few places around the net over both v4 and v6).  If this wasn't a transient issue local to you that has since vanished, can you hop on our freenode #wikimedia-operations [https://meta.wikimedia.org/wiki/IRC/Channels IRC channel] to debug with us at some point? [[User:BBlack (WMF)|BBlack (WMF)]] ([[User talk:BBlack (WMF)|talk]]) 12:10, 18 June 2015 (UTC)\n""]","12:10, 18 June 2015 (UTC)",BBlack (WMF)
+"[':::: Ping: [[User:Green Cardamom]] ^\n', "":::: [[User:BBlack (WMF)|BBlack (WMF)]], it's working OK right now. I'll keep trying and if it starts happening again I'll get on IRC. Thanks. -- [[User:Green Cardamom|Green Cardamom]] ([[User talk:Green Cardamom|talk]]) 22:28, 18 June 2015 (UTC)\n""]","22:28, 18 June 2015 (UTC)",Green Cardamom
+"['== Yes indeed, My code is broken! ==\n', '\n', '\n', '<br>\n', 'I have written communication programs to fetch data from Wikipedia and the dictionarys.<br>\n', '(this was done in an environment that is called Caché or MUMPS: http://www.intersystems.com/our-products/cache/cache-overview)<br>\n', 'I made them in order to have the possibility to check the contents on errors and much more.\n', '<br><br>\n', 'Unfortunately they do not work anymore.\n', '\n', 'Somebody made the following statement:\n', 'For bot maintainers, you have a couple of choices. Either login as the bot and select the preference to not use HTTPS for that account, or update your code to use SSL instead.<br>\n', 'How do I realise the preference to not use HTTPS for an account?\n', '\n', 'Untill now I have tried a lot to fix it but I did not succeed...\n', '\n', 'Saludos,\n', '\n', '--[[User:Kvdrgeus|Kvdrgeus]] ([[User talk:Kvdrgeus|talk]]) 07:16, 21 June 2015 (UTC)\n']","07:16, 21 June 2015 (UTC)",Kvdrgeus
+"['\n', ':Disabling HTTPS is not possible anymore. Your only option is to fix it to work with HTTPS in some way. - [[User:JanZerebecki|Jan Zerebecki]] 10:23, 21 June 2015 (UTC)\n']","10:23, 21 June 2015 (UTC)",JanZerebecki
+"[""::Hi [[User:Kvdrgeus|Kvdrgeus]], the bot problems are noted, I hope to be able to put together some relevant information specifically for this. Due to security concerns, we haven't been able to leave the option of opting out open. See [[:en:special:diff/666682303|here]] for a technical explanation. /[[User:Johan (WMF)|Johan (WMF)]] ([[User talk:Johan (WMF)|talk]]) 13:44, 22 June 2015 (UTC)\n""]","13:44, 22 June 2015 (UTC)",Johan (WMF)
+"['\n', 'I finally did succeed in adapting the communication routines to the new TLS-protocols\n', 'so this problem has been solved...\n', '\n', '--[[User:Kvdrgeus|Kvdrgeus]] ([[User talk:Kvdrgeus|talk]]) 12:43, 26 June 2015 (UTC)\n']","12:43, 26 June 2015 (UTC)",Kvdrgeus
+"["":Excellent, I'm glad to hear that. /[[User:Johan (WMF)|Johan (WMF)]] ([[User talk:Johan (WMF)|talk]]) 08:45, 1 July 2015 (UTC)\n""]","08:45, 1 July 2015 (UTC)",Johan (WMF)
diff --git a/src/helper_scripts/cleaning_scripts/022825_wmf_master_phab_roster.json b/src/helper_scripts/cleaning_scripts/022825_wmf_master_phab_roster.json
new file mode 100644
index 0000000..58e7873
--- /dev/null
+++ b/src/helper_scripts/cleaning_scripts/022825_wmf_master_phab_roster.json
@@ -0,0 +1,7449 @@
+[
+    {
+        "id": 43935,
+        "type": "USER",
+        "phid": "PHID-USER-yx36n66rpytiaffvun4p",
+        "fields": {
+            "username": "LPetty-WMF",
+            "realName": "",
+            "mediawikiUsername": "LPetty-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1740515327,
+            "dateModified": 1740515341,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43923,
+        "type": "USER",
+        "phid": "PHID-USER-e5yxgprpn52cx4avauuh",
+        "fields": {
+            "username": "JDonatBolton-WMF",
+            "realName": "",
+            "mediawikiUsername": "JDonatBolton-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1740461573,
+            "dateModified": 1740461584,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43892,
+        "type": "USER",
+        "phid": "PHID-USER-lvnewfxcgvb4l3cjlurg",
+        "fields": {
+            "username": "AStein-WMF",
+            "realName": "Avishua",
+            "mediawikiUsername": "AStein-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1740167987,
+            "dateModified": 1740167999,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43882,
+        "type": "USER",
+        "phid": "PHID-USER-orewh77adzsxq6nmf4yl",
+        "fields": {
+            "username": "HSwan-WMF",
+            "realName": "",
+            "mediawikiUsername": "HSwan-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1740086650,
+            "dateModified": 1740086660,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43787,
+        "type": "USER",
+        "phid": "PHID-USER-36ognqz3dhry7evbhgoh",
+        "fields": {
+            "username": "TElder-WMF",
+            "realName": "Tom Elder",
+            "mediawikiUsername": "TElder-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1739203915,
+            "dateModified": 1739203924,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43735,
+        "type": "USER",
+        "phid": "PHID-USER-iqfdy5zl6ei4zegxanbd",
+        "fields": {
+            "username": "EMill-WMF",
+            "realName": "",
+            "mediawikiUsername": "EMill-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1738698487,
+            "dateModified": 1738698496,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43730,
+        "type": "USER",
+        "phid": "PHID-USER-jgc25ndhrunrpmdor5i6",
+        "fields": {
+            "username": "ABeckford-WMF",
+            "realName": "Aldrick Beckford",
+            "mediawikiUsername": "ABeckford-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1738679956,
+            "dateModified": 1738679969,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43659,
+        "type": "USER",
+        "phid": "PHID-USER-imms6bxq62tcoph2apjv",
+        "fields": {
+            "username": "MJahnavi-WMF",
+            "realName": "Jahnavi",
+            "mediawikiUsername": "MJahnavi-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1737795895,
+            "dateModified": 1737796103,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43646,
+        "type": "USER",
+        "phid": "PHID-USER-kbjf7n4wdrpwolvgrafk",
+        "fields": {
+            "username": "SSalgaonkar-WMF",
+            "realName": "",
+            "mediawikiUsername": "SSalgaonkar-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1737666238,
+            "dateModified": 1737666245,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43636,
+        "type": "USER",
+        "phid": "PHID-USER-ci5f44itz3kw33s4vdhk",
+        "fields": {
+            "username": "LLugo-WMF",
+            "realName": "Luz",
+            "mediawikiUsername": "LLugo-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1737572651,
+            "dateModified": 1737572669,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43517,
+        "type": "USER",
+        "phid": "PHID-USER-pils5xx2wat5rrakuvzq",
+        "fields": {
+            "username": "LPasqual_WMF",
+            "realName": "",
+            "mediawikiUsername": "LPasqual (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1736533848,
+            "dateModified": 1736533858,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43481,
+        "type": "USER",
+        "phid": "PHID-USER-j5tweaj2eicjspuri3gz",
+        "fields": {
+            "username": "FCeratto-WMF",
+            "realName": "Federico Ceratto",
+            "mediawikiUsername": "FCeratto-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1736275746,
+            "dateModified": 1738315285,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "federico3"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43270,
+        "type": "USER",
+        "phid": "PHID-USER-sotiaaje2evj4hkmcbro",
+        "fields": {
+            "username": "JRenteria",
+            "realName": "JRenteria (WMF)",
+            "mediawikiUsername": "JRenteria (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1734107887,
+            "dateModified": 1734107899,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43225,
+        "type": "USER",
+        "phid": "PHID-USER-eiwqbnw6fwoylbm44omc",
+        "fields": {
+            "username": "DLin-WMF",
+            "realName": "Damian",
+            "mediawikiUsername": "DLin-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1733766923,
+            "dateModified": 1733766933,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43168,
+        "type": "USER",
+        "phid": "PHID-USER-643w7s6rlxt74nvp4meq",
+        "fields": {
+            "username": "KMontalva-WMF",
+            "realName": "",
+            "mediawikiUsername": "KMontalva-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1733223011,
+            "dateModified": 1733833353,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43118,
+        "type": "USER",
+        "phid": "PHID-USER-cg3zcrrrpqsj4dwlwcik",
+        "fields": {
+            "username": "MRitch-WMF",
+            "realName": "",
+            "mediawikiUsername": "MRitch-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1732733564,
+            "dateModified": 1732733578,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43058,
+        "type": "USER",
+        "phid": "PHID-USER-dpanufkl24gimqbjdipg",
+        "fields": {
+            "username": "AJardine-WMF",
+            "realName": "Amanda Jardine",
+            "mediawikiUsername": "AJardine-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1732208617,
+            "dateModified": 1732208727,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 43030,
+        "type": "USER",
+        "phid": "PHID-USER-xhl5ztzfk2bms67tvua7",
+        "fields": {
+            "username": "Jdlrobson-WMF",
+            "realName": "",
+            "mediawikiUsername": "Jon (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1731952127,
+            "dateModified": 1731953074,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "Jdlrobson"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42985,
+        "type": "USER",
+        "phid": "PHID-USER-5xj3bykt2uty2p623psc",
+        "fields": {
+            "username": "SKivlehan-WMF",
+            "realName": "",
+            "mediawikiUsername": "SKivlehan-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1731519476,
+            "dateModified": 1731519569,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42918,
+        "type": "USER",
+        "phid": "PHID-USER-nwuhn7k33ebaniyjgzk5",
+        "fields": {
+            "username": "BJordan-WMF",
+            "realName": "Breianne (Bre)",
+            "mediawikiUsername": "BJordan-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1731000114,
+            "dateModified": 1731000157,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42792,
+        "type": "USER",
+        "phid": "PHID-USER-qijowityhtt7bu52sba2",
+        "fields": {
+            "username": "Sana_ELCHEHIB_WMFr",
+            "realName": "SanaWmfr",
+            "mediawikiUsername": "Sana EL CHEHIB WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1730212582,
+            "dateModified": 1730212598,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42691,
+        "type": "USER",
+        "phid": "PHID-USER-64n43u2blj3vzo4kgf47",
+        "fields": {
+            "username": "IAckerman-WMF",
+            "realName": "Ilse Ackerman",
+            "mediawikiUsername": "IAckerman-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1729516605,
+            "dateModified": 1729516745,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42690,
+        "type": "USER",
+        "phid": "PHID-USER-hhzyah5f7zk62kzntq55",
+        "fields": {
+            "username": "GSyalindri-WMF",
+            "realName": "Gisca",
+            "mediawikiUsername": "GSyalindri-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1729510130,
+            "dateModified": 1729510184,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42664,
+        "type": "USER",
+        "phid": "PHID-USER-fchfgj56gh6vt2ng4afw",
+        "fields": {
+            "username": "LMora-WMF",
+            "realName": "LorenMora",
+            "mediawikiUsername": "LMora-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1729278330,
+            "dateModified": 1729278343,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42562,
+        "type": "USER",
+        "phid": "PHID-USER-icd6vxjf2sfarbudknas",
+        "fields": {
+            "username": "JTweed-WMF",
+            "realName": "Jonathan Tweed",
+            "mediawikiUsername": "JTweed-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1728390507,
+            "dateModified": 1731338884,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42428,
+        "type": "USER",
+        "phid": "PHID-USER-f42oog566ciubypjkcr2",
+        "fields": {
+            "username": "WRai-WMF",
+            "realName": "William Rai",
+            "mediawikiUsername": "WRai-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1727809794,
+            "dateModified": 1727809811,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42419,
+        "type": "USER",
+        "phid": "PHID-USER-5ou7tkk2gsnba2qyitlh",
+        "fields": {
+            "username": "CaCogdill-WMF",
+            "realName": "Caitlin Cogdill",
+            "mediawikiUsername": "CaCogdill-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1727797151,
+            "dateModified": 1727797224,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42365,
+        "type": "USER",
+        "phid": "PHID-USER-bhdlfp3ywmt6xk6iudkm",
+        "fields": {
+            "username": "EBomani-WMF",
+            "realName": "",
+            "mediawikiUsername": null,
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1727282210,
+            "dateModified": 1727282235,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42109,
+        "type": "USER",
+        "phid": "PHID-USER-zin3mltwgpxh3ojuxger",
+        "fields": {
+            "username": "GOlson-WMF",
+            "realName": "Grey Olson",
+            "mediawikiUsername": "GOlson-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1724159712,
+            "dateModified": 1724159721,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42108,
+        "type": "USER",
+        "phid": "PHID-USER-phw5ejocuubrvssmmago",
+        "fields": {
+            "username": "SWangari-WMF",
+            "realName": "",
+            "mediawikiUsername": "SWangari-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1724148420,
+            "dateModified": 1724148456,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 42075,
+        "type": "USER",
+        "phid": "PHID-USER-ttmv6dfoc6wws5uxcsqe",
+        "fields": {
+            "username": "HCoplin-WMF",
+            "realName": "Halley",
+            "mediawikiUsername": "HCoplin-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1723820446,
+            "dateModified": 1738082239,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41995,
+        "type": "USER",
+        "phid": "PHID-USER-22spp4e5xggzb4bqx66z",
+        "fields": {
+            "username": "SChekfa-WMF",
+            "realName": "Sarah Chekfa",
+            "mediawikiUsername": "SChekfa-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1722975885,
+            "dateModified": 1725041713,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "sarah"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41986,
+        "type": "USER",
+        "phid": "PHID-USER-3a3frjuuhqh5pim4vuym",
+        "fields": {
+            "username": "JNakayama-WMF",
+            "realName": "",
+            "mediawikiUsername": "JNakayama-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1722862825,
+            "dateModified": 1722862844,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41984,
+        "type": "USER",
+        "phid": "PHID-USER-fx7j3kqzch4cjy773gk3",
+        "fields": {
+            "username": "Sarai-WMF",
+            "realName": "Sarai Sanchez",
+            "mediawikiUsername": "SSanchez-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1722848690,
+            "dateModified": 1722848839,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41861,
+        "type": "USER",
+        "phid": "PHID-USER-nlimkigzwyqzrfpddf7x",
+        "fields": {
+            "username": "APaul-WMF",
+            "realName": "Annu Paul",
+            "mediawikiUsername": "APaul-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1721854668,
+            "dateModified": 1721854679,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41852,
+        "type": "USER",
+        "phid": "PHID-USER-win3l7w2bcnh2beh2egs",
+        "fields": {
+            "username": "CPickens-WMF",
+            "realName": "",
+            "mediawikiUsername": "CPickens-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1721834066,
+            "dateModified": 1721834081,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41703,
+        "type": "USER",
+        "phid": "PHID-USER-ggux66p5n72blxcrvzlh",
+        "fields": {
+            "username": "Lferreira",
+            "realName": "Levi Ferreira (WMF)",
+            "mediawikiUsername": "LFerreira-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1720171680,
+            "dateModified": 1731507247,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41588,
+        "type": "USER",
+        "phid": "PHID-USER-y6ycokwluwuhl3scgff5",
+        "fields": {
+            "username": "MBywater-WMF",
+            "realName": "mbywater",
+            "mediawikiUsername": "MBywater-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1719328632,
+            "dateModified": 1719328643,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41549,
+        "type": "USER",
+        "phid": "PHID-USER-vpubvcebt3bxdaypny4c",
+        "fields": {
+            "username": "DSmit-WMF",
+            "realName": "Daphne Smit",
+            "mediawikiUsername": "DSmit-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1718797305,
+            "dateModified": 1718797518,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41538,
+        "type": "USER",
+        "phid": "PHID-USER-xs6v7vll6dw3v4o7nix6",
+        "fields": {
+            "username": "AlexHollender-WMF",
+            "realName": "Alex Hollender, design contractor",
+            "mediawikiUsername": "AlexHollender-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1718640248,
+            "dateModified": 1718648334,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 41022,
+        "type": "USER",
+        "phid": "PHID-USER-tcdavz53xh5w2aqcjexq",
+        "fields": {
+            "username": "KMorrow-WMF",
+            "realName": "Kelly M.",
+            "mediawikiUsername": "KMorrow-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1714592313,
+            "dateModified": 1714592325,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 40413,
+        "type": "USER",
+        "phid": "PHID-USER-kvhgxelgytq7l4uhislr",
+        "fields": {
+            "username": "LRGoncalves-WMF",
+            "realName": "Lukas Goncalves",
+            "mediawikiUsername": "LRGoncalves-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1709901896,
+            "dateModified": 1709901918,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 40195,
+        "type": "USER",
+        "phid": "PHID-USER-pyfhhw6g6olbfljb7yyk",
+        "fields": {
+            "username": "DJames-WMF",
+            "realName": "Destinie James",
+            "mediawikiUsername": "DJames-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1709525106,
+            "dateModified": 1720011861,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 40164,
+        "type": "USER",
+        "phid": "PHID-USER-deyho4y2oaqaxdfgeurd",
+        "fields": {
+            "username": "FBellamy-WMF",
+            "realName": "Febin Bellamy",
+            "mediawikiUsername": "FBellamy-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1709298367,
+            "dateModified": 1720011889,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "fbellamy"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 39781,
+        "type": "USER",
+        "phid": "PHID-USER-vtrv6pqd2fqwb34onfuf",
+        "fields": {
+            "username": "RLopez-WMF",
+            "realName": "Ramon",
+            "mediawikiUsername": "RLopez-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1706308806,
+            "dateModified": 1706309797,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 39772,
+        "type": "USER",
+        "phid": "PHID-USER-y2c6dm4nvxygkm47vio2",
+        "fields": {
+            "username": "RThomas-WMF",
+            "realName": "",
+            "mediawikiUsername": "RThomas-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1706192657,
+            "dateModified": 1706192667,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 39656,
+        "type": "USER",
+        "phid": "PHID-USER-wpqdg4x5tkn5vvrz6b2e",
+        "fields": {
+            "username": "SOzenogu-WMF",
+            "realName": "Susan",
+            "mediawikiUsername": "SOzenogu-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1705684593,
+            "dateModified": 1720011954,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 39627,
+        "type": "USER",
+        "phid": "PHID-USER-gijtkzcktagsduwnkeo6",
+        "fields": {
+            "username": "JWheeler-WMF",
+            "realName": "jack",
+            "mediawikiUsername": "JWheeler-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1705426020,
+            "dateModified": 1705426030,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 39175,
+        "type": "USER",
+        "phid": "PHID-USER-ygwm33p6bvmykssuhavh",
+        "fields": {
+            "username": "XiaoXiao-WMF",
+            "realName": "",
+            "mediawikiUsername": "XiaoXiao-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1701112393,
+            "dateModified": 1701112443,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 39138,
+        "type": "USER",
+        "phid": "PHID-USER-ajabnu5jgmjgu4e5cjfx",
+        "fields": {
+            "username": "SToyofuku-WMF",
+            "realName": "Steph Toyofuku",
+            "mediawikiUsername": "SToyofuku-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1700692234,
+            "dateModified": 1711644200,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 39019,
+        "type": "USER",
+        "phid": "PHID-USER-c3zcl5qeyj2qarjlocvn",
+        "fields": {
+            "username": "GBordoy_WMF",
+            "realName": "Giyu ",
+            "mediawikiUsername": "GBordoy (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1699469982,
+            "dateModified": 1735834223,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38975,
+        "type": "USER",
+        "phid": "PHID-USER-aoffukjveuvlnkgljdej",
+        "fields": {
+            "username": "GLima-WMF",
+            "realName": "Glauco Lima",
+            "mediawikiUsername": "GLima-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1698868384,
+            "dateModified": 1714374210,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38698,
+        "type": "USER",
+        "phid": "PHID-USER-x2bs2bsvpuzsskczvbgp",
+        "fields": {
+            "username": "DTorsani-WMF",
+            "realName": "Derek Torsani",
+            "mediawikiUsername": "DTorsani-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1696511717,
+            "dateModified": 1735828898,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38571,
+        "type": "USER",
+        "phid": "PHID-USER-vbmevvbag4ibbcd6vlcb",
+        "fields": {
+            "username": "SCampos-WMF",
+            "realName": "Sara Campos",
+            "mediawikiUsername": "SCampos-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1696278132,
+            "dateModified": 1696278177,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38521,
+        "type": "USER",
+        "phid": "PHID-USER-4qwugwiismkcpaslwicq",
+        "fields": {
+            "username": "AMarino-WMF",
+            "realName": "",
+            "mediawikiUsername": "AMarino-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1695938351,
+            "dateModified": 1695938366,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38386,
+        "type": "USER",
+        "phid": "PHID-USER-rij2tyfh5yliqa6wfwk7",
+        "fields": {
+            "username": "MMulaudzi-WMF",
+            "realName": "Masana Mulaudzi",
+            "mediawikiUsername": "MMulaudzi-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1694604992,
+            "dateModified": 1694605003,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38252,
+        "type": "USER",
+        "phid": "PHID-USER-oprgn52aabxc3rnzcmuu",
+        "fields": {
+            "username": "ABran-WMF",
+            "realName": "arnaudb",
+            "mediawikiUsername": "ABran-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1693297839,
+            "dateModified": 1732886477,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "arnaudb"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38231,
+        "type": "USER",
+        "phid": "PHID-USER-ycw7a7ioovylvbdhi4of",
+        "fields": {
+            "username": "EUwandu-WMF",
+            "realName": "",
+            "mediawikiUsername": "EUwandu-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1693000541,
+            "dateModified": 1693000578,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38203,
+        "type": "USER",
+        "phid": "PHID-USER-hwhk5xwveniiimmgq5bi",
+        "fields": {
+            "username": "VRiley-WMF",
+            "realName": "Valerie Riley",
+            "mediawikiUsername": "VRiley-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1692716803,
+            "dateModified": 1705631669,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38151,
+        "type": "USER",
+        "phid": "PHID-USER-i47wokgfjiksh6hnamjm",
+        "fields": {
+            "username": "ABreault-WMF",
+            "realName": "Arlo Breault",
+            "mediawikiUsername": "ABreault (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1692289589,
+            "dateModified": 1692290288,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38068,
+        "type": "USER",
+        "phid": "PHID-USER-ntivzl4ofomvpu4ldpms",
+        "fields": {
+            "username": "OSefu-WMF",
+            "realName": "Omari Sefu",
+            "mediawikiUsername": "OSefu-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1691414844,
+            "dateModified": 1691422639,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 38015,
+        "type": "USER",
+        "phid": "PHID-USER-ojvfchwtbgzwbabiytx2",
+        "fields": {
+            "username": "KColeman-WMF",
+            "realName": "",
+            "mediawikiUsername": "KColeman-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1690898514,
+            "dateModified": 1721840021,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 37860,
+        "type": "USER",
+        "phid": "PHID-USER-xjsxqce6njigefu4cahd",
+        "fields": {
+            "username": "JScherer-WMF",
+            "realName": "Justin Scherer",
+            "mediawikiUsername": "JScherer-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1689087031,
+            "dateModified": 1694450672,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 37571,
+        "type": "USER",
+        "phid": "PHID-USER-6tiugxoim676qaej427u",
+        "fields": {
+            "username": "KStineRowe_WMF",
+            "realName": "",
+            "mediawikiUsername": "KStineRowe (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1686344888,
+            "dateModified": 1686344904,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 37396,
+        "type": "USER",
+        "phid": "PHID-USER-g4r3nm2h5rnv5hwsqlur",
+        "fields": {
+            "username": "ATsay-WMF",
+            "realName": "",
+            "mediawikiUsername": "ATsay-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1685128912,
+            "dateModified": 1685128925,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 37202,
+        "type": "USER",
+        "phid": "PHID-USER-wmo34eigs2zs6xruxx6n",
+        "fields": {
+            "username": "SEgt-WMF",
+            "realName": "Silvia Guti\u00e9rrez",
+            "mediawikiUsername": "SEgt-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1683585665,
+            "dateModified": 1683585678,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 37153,
+        "type": "USER",
+        "phid": "PHID-USER-q2grbhlglab2hhuedil4",
+        "fields": {
+            "username": "ERoden-WMF",
+            "realName": "Erica",
+            "mediawikiUsername": "Emroden1",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1683144596,
+            "dateModified": 1683144606,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 37017,
+        "type": "USER",
+        "phid": "PHID-USER-53u6dgbjy2mfzfv7akav",
+        "fields": {
+            "username": "CCoxwell-WMF",
+            "realName": "Carrie",
+            "mediawikiUsername": "CCoxwell-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1682000879,
+            "dateModified": 1698938308,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 36948,
+        "type": "USER",
+        "phid": "PHID-USER-ndycq4b4d3caozo7ypfr",
+        "fields": {
+            "username": "AFowler-WMF",
+            "realName": "Amy Fowler",
+            "mediawikiUsername": "AFowler-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1681406907,
+            "dateModified": 1681406919,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 36514,
+        "type": "USER",
+        "phid": "PHID-USER-ctfiuzfgu2bdqoqkv3gf",
+        "fields": {
+            "username": "ROdonnell-WMF",
+            "realName": "Ruairi",
+            "mediawikiUsername": "ROdonnell-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1678796179,
+            "dateModified": 1679579145,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 36398,
+        "type": "USER",
+        "phid": "PHID-USER-kivver4jcakpom2p43sf",
+        "fields": {
+            "username": "FJoseph-WMF",
+            "realName": "Frantz Joseph",
+            "mediawikiUsername": "FJoseph-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1678288919,
+            "dateModified": 1721103197,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 36281,
+        "type": "USER",
+        "phid": "PHID-USER-jotz45n4jwinq6ryhfi6",
+        "fields": {
+            "username": "VYanez-WMF",
+            "realName": "Viviana Yanez",
+            "mediawikiUsername": "VYanez-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1677692096,
+            "dateModified": 1704909708,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 36273,
+        "type": "USER",
+        "phid": "PHID-USER-tciz5pejvizkp4fykyz5",
+        "fields": {
+            "username": "BAbiola-WMF",
+            "realName": "Barakat Ajadi",
+            "mediawikiUsername": "Barakat Ajadi",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1677668481,
+            "dateModified": 1704908663,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 36259,
+        "type": "USER",
+        "phid": "PHID-USER-e4t6xehpq3stypw62xhc",
+        "fields": {
+            "username": "SSpalding-WMF",
+            "realName": "SSpalding (WMF)",
+            "mediawikiUsername": "SSpalding (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1677608434,
+            "dateModified": 1677608445,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 36199,
+        "type": "USER",
+        "phid": "PHID-USER-d23g5tug3pl3wmbplgor",
+        "fields": {
+            "username": "tcappelletto_wmf",
+            "realName": "Tila",
+            "mediawikiUsername": "TCappelletto (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1677249232,
+            "dateModified": 1720012154,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 36148,
+        "type": "USER",
+        "phid": "PHID-USER-hfjjgxgmmicxiptxsqyj",
+        "fields": {
+            "username": "FDoria-WMF",
+            "realName": "Flavia Doria",
+            "mediawikiUsername": "FDoria-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1677090989,
+            "dateModified": 1677091033,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 36070,
+        "type": "USER",
+        "phid": "PHID-USER-fcgdwttbxa75cpmm2ldz",
+        "fields": {
+            "username": "LDlulisa-WMF",
+            "realName": "Luvo",
+            "mediawikiUsername": "LDlulisa-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1676464932,
+            "dateModified": 1676467425,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35798,
+        "type": "USER",
+        "phid": "PHID-USER-li4rooxlpprxj2hp5pa2",
+        "fields": {
+            "username": "JPBeland-WMF",
+            "realName": "JP B\u00e9land",
+            "mediawikiUsername": "JPBeland-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1674790610,
+            "dateModified": 1713438689,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35698,
+        "type": "USER",
+        "phid": "PHID-USER-bryykkyckrzako5gnizk",
+        "fields": {
+            "username": "KSarabia-WMF",
+            "realName": "Kim Sarabia",
+            "mediawikiUsername": "KSarabia-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1674056730,
+            "dateModified": 1711468543,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35686,
+        "type": "USER",
+        "phid": "PHID-USER-tvifd2z5e2aii4wba7ee",
+        "fields": {
+            "username": "CCiufo-WMF",
+            "realName": "Christopher Ciufo",
+            "mediawikiUsername": "CCiufo-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1673971276,
+            "dateModified": 1673971397,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35673,
+        "type": "USER",
+        "phid": "PHID-USER-wlcljmxinmtye5mbhkpj",
+        "fields": {
+            "username": "JEbe-WMF",
+            "realName": "Jennifer",
+            "mediawikiUsername": "JEbe-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1673896612,
+            "dateModified": 1689339875,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35636,
+        "type": "USER",
+        "phid": "PHID-USER-wawzcuwzhi4crnrpucok",
+        "fields": {
+            "username": "AKanji-WMF",
+            "realName": "Anil",
+            "mediawikiUsername": "AKanji-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1673546465,
+            "dateModified": 1673546780,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35570,
+        "type": "USER",
+        "phid": "PHID-USER-srxp5zs7f346ay5pkdww",
+        "fields": {
+            "username": "JSengupta-WMF",
+            "realName": "Joydeep Sengupta",
+            "mediawikiUsername": "JSengupta-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1673013739,
+            "dateModified": 1676383677,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35539,
+        "type": "USER",
+        "phid": "PHID-USER-yr2dgzzrxp3dpg3dxizd",
+        "fields": {
+            "username": "JLam-WMF",
+            "realName": "",
+            "mediawikiUsername": "JLam-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1672752259,
+            "dateModified": 1725996840,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35247,
+        "type": "USER",
+        "phid": "PHID-USER-txn7azbcvsw4qfmakcju",
+        "fields": {
+            "username": "HXi-WMF",
+            "realName": "Hua Xi",
+            "mediawikiUsername": "HXi-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1670001950,
+            "dateModified": 1685446976,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35233,
+        "type": "USER",
+        "phid": "PHID-USER-ts6dsgmubnixvmfsvt5f",
+        "fields": {
+            "username": "Maryann-Onyinye",
+            "realName": "Onyinyechi Onifade WMF",
+            "mediawikiUsername": "OOnifade-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1669886428,
+            "dateModified": 1694162658,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35168,
+        "type": "USER",
+        "phid": "PHID-USER-gpt3z55oom6v33uehuwi",
+        "fields": {
+            "username": "NMariano-WMF",
+            "realName": "Nick Mariano",
+            "mediawikiUsername": "NMariano-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1669227745,
+            "dateModified": 1733131812,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35160,
+        "type": "USER",
+        "phid": "PHID-USER-bftbg7w7hrly5ec22brb",
+        "fields": {
+            "username": "REsquito-WMF",
+            "realName": "Ricardo Esquito",
+            "mediawikiUsername": "REsquito-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1669202630,
+            "dateModified": 1669202640,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35147,
+        "type": "USER",
+        "phid": "PHID-USER-ms6aofas7kld4irq2qov",
+        "fields": {
+            "username": "SDeckelmann-WMF",
+            "realName": "Selena Deckelmann",
+            "mediawikiUsername": "SDeckelmann-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1669052027,
+            "dateModified": 1669052048,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35086,
+        "type": "USER",
+        "phid": "PHID-USER-otfljozyp7q6qq7fvaxi",
+        "fields": {
+            "username": "Jadnapa",
+            "realName": "AMtavangu(WMF)",
+            "mediawikiUsername": "Jadnapac",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1668526884,
+            "dateModified": 1668527643,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 35016,
+        "type": "USER",
+        "phid": "PHID-USER-7jsg6ykyhz53m36uoba2",
+        "fields": {
+            "username": "Udehb-WMF",
+            "realName": "Benedict Udeh",
+            "mediawikiUsername": "Udehb-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1668071049,
+            "dateModified": 1668071104,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34997,
+        "type": "USER",
+        "phid": "PHID-USER-nqxr4ozk266exjw4fpf6",
+        "fields": {
+            "username": "PPenloglou-WMF",
+            "realName": "Panos",
+            "mediawikiUsername": null,
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1667916994,
+            "dateModified": 1714669018,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34944,
+        "type": "USER",
+        "phid": "PHID-USER-ha4ssm77rhhlixgq55mu",
+        "fields": {
+            "username": "LLacroix-WMF",
+            "realName": "L\u00e9a Lacroix",
+            "mediawikiUsername": "LLacroix-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1667455109,
+            "dateModified": 1688483565,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34941,
+        "type": "USER",
+        "phid": "PHID-USER-u7s67b6a6mxmfxtsns7a",
+        "fields": {
+            "username": "NNgu-WMF",
+            "realName": "Natalie Ngu",
+            "mediawikiUsername": "NNgu-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1667422731,
+            "dateModified": 1667422741,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34923,
+        "type": "USER",
+        "phid": "PHID-USER-wslwcb2wulhik4rbirjq",
+        "fields": {
+            "username": "KMorgan-WMF",
+            "realName": "Kayla Morgan",
+            "mediawikiUsername": "KMorgan-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1667319942,
+            "dateModified": 1696239415,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34908,
+        "type": "USER",
+        "phid": "PHID-USER-7mrunqeaunc54qyqjabz",
+        "fields": {
+            "username": "RWambua-WMF",
+            "realName": "Rebecca",
+            "mediawikiUsername": "RWambua-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1667244860,
+            "dateModified": 1691266796,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34887,
+        "type": "USER",
+        "phid": "PHID-USER-wvf6nntbt2sjfbwfvgkl",
+        "fields": {
+            "username": "KLawal-WMF",
+            "realName": "Kolawole",
+            "mediawikiUsername": "KLawal-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1667074803,
+            "dateModified": 1720011997,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34872,
+        "type": "USER",
+        "phid": "PHID-USER-3fr24ue37syozz2qtuhl",
+        "fields": {
+            "username": "ILooremeta-WMF",
+            "realName": "Isaac",
+            "mediawikiUsername": "ILooremeta-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1666974193,
+            "dateModified": 1711460300,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34867,
+        "type": "USER",
+        "phid": "PHID-USER-jul2ocwliznwc7gu7ega",
+        "fields": {
+            "username": "HShaath-WMF",
+            "realName": "Hiba Sha'ath",
+            "mediawikiUsername": "HShaath-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1666963148,
+            "dateModified": 1711461511,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34834,
+        "type": "USER",
+        "phid": "PHID-USER-vws6thubnojfdjrcx3kr",
+        "fields": {
+            "username": "PMenon-WMF",
+            "realName": "Parthiv",
+            "mediawikiUsername": "PMenon-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1666679635,
+            "dateModified": 1704198707,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34825,
+        "type": "USER",
+        "phid": "PHID-USER-xknkkcdkeupo4ct3gtmy",
+        "fields": {
+            "username": "BSchowengerdt-WMF",
+            "realName": "Bethany Schowengerdt ",
+            "mediawikiUsername": "BSchowengerdt-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1666632418,
+            "dateModified": 1679122920,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34654,
+        "type": "USER",
+        "phid": "PHID-USER-kyaxkh3sbcadkbpicdmo",
+        "fields": {
+            "username": "DBarthel_WMF",
+            "realName": "",
+            "mediawikiUsername": "DBarthel (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1665408667,
+            "dateModified": 1682577313,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34584,
+        "type": "USER",
+        "phid": "PHID-USER-ug3fn5ckposquf2qzoml",
+        "fields": {
+            "username": "KHurd-WMF",
+            "realName": "Kelton Hurd",
+            "mediawikiUsername": "KHurd-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1664927867,
+            "dateModified": 1717144039,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34508,
+        "type": "USER",
+        "phid": "PHID-USER-l37732ailaqzfahgkz3j",
+        "fields": {
+            "username": "RGaines_WMF",
+            "realName": "Ricky Gaines",
+            "mediawikiUsername": "RGaines (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1664212360,
+            "dateModified": 1664212369,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34439,
+        "type": "USER",
+        "phid": "PHID-USER-nohaaivl3jao7tfii7iu",
+        "fields": {
+            "username": "EGranado-WMF",
+            "realName": "",
+            "mediawikiUsername": "EGranado-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1663448987,
+            "dateModified": 1663449552,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34426,
+        "type": "USER",
+        "phid": "PHID-USER-qwcfy3npcr6qom5m3s4i",
+        "fields": {
+            "username": "DSaroyan_WMF",
+            "realName": "Davit Saroyan",
+            "mediawikiUsername": "DSaroyan (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1663337166,
+            "dateModified": 1663337175,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34405,
+        "type": "USER",
+        "phid": "PHID-USER-yxspa45iegxgefngglgc",
+        "fields": {
+            "username": "ACorzati-WMF",
+            "realName": "Alicia Corzati",
+            "mediawikiUsername": "ACorzati-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1663176155,
+            "dateModified": 1683907810,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34340,
+        "type": "USER",
+        "phid": "PHID-USER-focpirwz2ncz4dgbc6wy",
+        "fields": {
+            "username": "SGupta-WMF",
+            "realName": "",
+            "mediawikiUsername": "SGupta-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1662617456,
+            "dateModified": 1662617474,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34251,
+        "type": "USER",
+        "phid": "PHID-USER-t6aceghk32x4hpoeul7e",
+        "fields": {
+            "username": "GMikesell-WMF",
+            "realName": "George",
+            "mediawikiUsername": "GMikesell-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1661879773,
+            "dateModified": 1661879863,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34246,
+        "type": "USER",
+        "phid": "PHID-USER-zneeqvgzmh6dd2crpbjp",
+        "fields": {
+            "username": "DBu-WMF",
+            "realName": "Danny Bu",
+            "mediawikiUsername": "DBu-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1661792811,
+            "dateModified": 1712822090,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 34060,
+        "type": "USER",
+        "phid": "PHID-USER-cvak3xjykwyfs2o6rqzr",
+        "fields": {
+            "username": "JMcRae-WMF",
+            "realName": "",
+            "mediawikiUsername": "JMcRae-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1660150311,
+            "dateModified": 1660150327,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33998,
+        "type": "USER",
+        "phid": "PHID-USER-lnr36kac5jkpc5zwji5j",
+        "fields": {
+            "username": "VirginiaPoundstone",
+            "realName": "vpoundstone, Virginia Poundstone (WMF)",
+            "mediawikiUsername": "VPoundstone-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1659476961,
+            "dateModified": 1668023424,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33931,
+        "type": "USER",
+        "phid": "PHID-USER-tjsn3to565aqibvomnno",
+        "fields": {
+            "username": "LMedley-WMF",
+            "realName": "Laurice",
+            "mediawikiUsername": "LMedley-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1658874998,
+            "dateModified": 1718664592,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33915,
+        "type": "USER",
+        "phid": "PHID-USER-cnkpoo5l2xv3flh2lqvq",
+        "fields": {
+            "username": "MHorsey-WMF",
+            "realName": "Michelle",
+            "mediawikiUsername": "MHorsey-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1658764706,
+            "dateModified": 1658764718,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33877,
+        "type": "USER",
+        "phid": "PHID-USER-onsbvrkv65ofeou6kn2p",
+        "fields": {
+            "username": "RASharma_WMF",
+            "realName": "Rachit",
+            "mediawikiUsername": "RASharma (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1658241425,
+            "dateModified": 1658241441,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33791,
+        "type": "USER",
+        "phid": "PHID-USER-td6c4h2jnotlu3hjrpj2",
+        "fields": {
+            "username": "SWoodruff-WMF",
+            "realName": "Sandy Woodruff",
+            "mediawikiUsername": "SWoodruff-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1657221195,
+            "dateModified": 1711544131,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33729,
+        "type": "USER",
+        "phid": "PHID-USER-3a5fseox7k4e5pe73naa",
+        "fields": {
+            "username": "DBautista-WMF",
+            "realName": "DBautista",
+            "mediawikiUsername": "DBautista-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1656527725,
+            "dateModified": 1656527741,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33726,
+        "type": "USER",
+        "phid": "PHID-USER-x4ajwuodnvdmw7rble7i",
+        "fields": {
+            "username": "PWaigi-WMF",
+            "realName": "Purity Waigi",
+            "mediawikiUsername": "PWaigi-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1656512342,
+            "dateModified": 1656512392,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33704,
+        "type": "USER",
+        "phid": "PHID-USER-vsywfwx2muzlpy37zapy",
+        "fields": {
+            "username": "RAdimer-WMF",
+            "realName": "Rae Adimer",
+            "mediawikiUsername": "RAdimer-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1656352286,
+            "dateModified": 1656352297,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33702,
+        "type": "USER",
+        "phid": "PHID-USER-q3aaklw3dpmwrpdywj3q",
+        "fields": {
+            "username": "PBradley-WMF",
+            "realName": "Phil Bradley-Schmieg",
+            "mediawikiUsername": "PBradley-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1656346465,
+            "dateModified": 1656346520,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33699,
+        "type": "USER",
+        "phid": "PHID-USER-ngr432tb4ly6zmblwck3",
+        "fields": {
+            "username": "ARamadan-WMF",
+            "realName": "",
+            "mediawikiUsername": "ARamadan-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1656337807,
+            "dateModified": 1656338013,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33693,
+        "type": "USER",
+        "phid": "PHID-USER-pjrz4rjjzv6cgo6f27eo",
+        "fields": {
+            "username": "BAPerdana-WMF",
+            "realName": "Bonaventura Aditya Perdana",
+            "mediawikiUsername": "BAPerdana-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1656262366,
+            "dateModified": 1732817574,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33622,
+        "type": "USER",
+        "phid": "PHID-USER-7t3opsulogrdgdxddjip",
+        "fields": {
+            "username": "JFernandez-WMF",
+            "realName": "Julieta",
+            "mediawikiUsername": "JFernandez-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1655694672,
+            "dateModified": 1715195667,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33528,
+        "type": "USER",
+        "phid": "PHID-USER-7fj4ixtzlqtd6tklb6v4",
+        "fields": {
+            "username": "CMyrick-WMF",
+            "realName": "Caroline Myrick",
+            "mediawikiUsername": "CMyrick-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1654787584,
+            "dateModified": 1654787595,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33468,
+        "type": "USER",
+        "phid": "PHID-USER-6rh36ng4svy5uwmpf4dx",
+        "fields": {
+            "username": "KBach",
+            "realName": "Kamil Bach (WMF)",
+            "mediawikiUsername": "KBach-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1654084385,
+            "dateModified": 1727948678,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "kbch"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33457,
+        "type": "USER",
+        "phid": "PHID-USER-mvxowaicn42xszoscrtn",
+        "fields": {
+            "username": "GEscalante-WMF",
+            "realName": "Gabriel Escalante Sobrino",
+            "mediawikiUsername": "GEscalante-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1654024714,
+            "dateModified": 1718236443,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33328,
+        "type": "USER",
+        "phid": "PHID-USER-hhhmpybdhuu7unbikbwp",
+        "fields": {
+            "username": "Shobha_WMF",
+            "realName": "Shobha",
+            "mediawikiUsername": "Shobha (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1653066754,
+            "dateModified": 1653066771,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33219,
+        "type": "USER",
+        "phid": "PHID-USER-fwepndfpweypybyfdscu",
+        "fields": {
+            "username": "RamzyM-WMF",
+            "realName": "RamzyM",
+            "mediawikiUsername": "RamzyM (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1652434593,
+            "dateModified": 1731601582,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33136,
+        "type": "USER",
+        "phid": "PHID-USER-w7jftu4lnwj255mnjxjl",
+        "fields": {
+            "username": "KStoller-WMF",
+            "realName": "Kirsten",
+            "mediawikiUsername": "KStoller-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1651675930,
+            "dateModified": 1654205155,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33119,
+        "type": "USER",
+        "phid": "PHID-USER-43j3d7v6jwmrb4xklqm7",
+        "fields": {
+            "username": "SLyngshede-WMF",
+            "realName": "Simon Lyngshede",
+            "mediawikiUsername": "SLyngshede-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1651492295,
+            "dateModified": 1676978910,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 33061,
+        "type": "USER",
+        "phid": "PHID-USER-q5lowi2qrjxtomknsfss",
+        "fields": {
+            "username": "NAramayo-WMF",
+            "realName": "Nicolas Aramayo",
+            "mediawikiUsername": "NAramayo-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1651000573,
+            "dateModified": 1651000585,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32994,
+        "type": "USER",
+        "phid": "PHID-USER-f3uz5xcs65ftnr7adih4",
+        "fields": {
+            "username": "SDelbecque-WMF",
+            "realName": "Stephanie Delbecque",
+            "mediawikiUsername": "SDelbecque-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1650455864,
+            "dateModified": 1650457899,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32980,
+        "type": "USER",
+        "phid": "PHID-USER-imgzj52ho7akm443sn65",
+        "fields": {
+            "username": "AOdit_WMF",
+            "realName": "Astuthis",
+            "mediawikiUsername": "AOdit (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1650364608,
+            "dateModified": 1650364631,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32915,
+        "type": "USER",
+        "phid": "PHID-USER-xglznjpmqwvyp2tqxka3",
+        "fields": {
+            "username": "OZhang-WMF",
+            "realName": "",
+            "mediawikiUsername": "OZhang-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1650041719,
+            "dateModified": 1711544456,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32845,
+        "type": "USER",
+        "phid": "PHID-USER-ug3myrtblv52hil6aowd",
+        "fields": {
+            "username": "NBaca-WMF",
+            "realName": "Nat Baca (Hillard)",
+            "mediawikiUsername": "NBaca-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1649700801,
+            "dateModified": 1733183546,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32750,
+        "type": "USER",
+        "phid": "PHID-USER-nbo76vl5wziw2yi2tiav",
+        "fields": {
+            "username": "AMuller-WMF",
+            "realName": "AmyMuller",
+            "mediawikiUsername": "AMuller-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1649076732,
+            "dateModified": 1649076752,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32536,
+        "type": "USER",
+        "phid": "PHID-USER-po6bbezgtakzixwqm4qo",
+        "fields": {
+            "username": "EChukwukere-WMF",
+            "realName": "emeka chukwukere",
+            "mediawikiUsername": "EChukwukere-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1647973402,
+            "dateModified": 1647973415,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32500,
+        "type": "USER",
+        "phid": "PHID-USER-td4g2pqq2ggdybn5vqjw",
+        "fields": {
+            "username": "EUdoh-WMF",
+            "realName": "Eazeeee",
+            "mediawikiUsername": "EUdoh-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1647630972,
+            "dateModified": 1673206949,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32454,
+        "type": "USER",
+        "phid": "PHID-USER-xuz2fmkxim6e5dphcjzb",
+        "fields": {
+            "username": "JArguello-WMF",
+            "realName": "Jackeline",
+            "mediawikiUsername": "JArguello-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1647362625,
+            "dateModified": 1669161540,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32453,
+        "type": "USER",
+        "phid": "PHID-USER-5x6sfc6dc3yy6sbk7jke",
+        "fields": {
+            "username": "KHernandez-WMF",
+            "realName": "Karen Hernandez",
+            "mediawikiUsername": "KHernandez-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1647362447,
+            "dateModified": 1647362485,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32452,
+        "type": "USER",
+        "phid": "PHID-USER-2nvr27vv42cfg25apdf4",
+        "fields": {
+            "username": "RZamora-WMF",
+            "realName": "Rosa Zamora",
+            "mediawikiUsername": "RZamora-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1647357695,
+            "dateModified": 1704198871,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32340,
+        "type": "USER",
+        "phid": "PHID-USER-43vqewokb6imw5y2aiqr",
+        "fields": {
+            "username": "NOkafor-WMF",
+            "realName": "Njay Okafor",
+            "mediawikiUsername": "NOkafor-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1646667076,
+            "dateModified": 1666693169,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32297,
+        "type": "USER",
+        "phid": "PHID-USER-hss3t2peg7ezmr7a2j4o",
+        "fields": {
+            "username": "BKots-WMF",
+            "realName": "Beta Kots",
+            "mediawikiUsername": "BKots-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1646284247,
+            "dateModified": 1671013677,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32287,
+        "type": "USER",
+        "phid": "PHID-USER-jsp6eohp2sltahpkqjyk",
+        "fields": {
+            "username": "Naphsica_papanicolaouWMFr",
+            "realName": "",
+            "mediawikiUsername": "Naphsica Papanicolaou WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1646228933,
+            "dateModified": 1646228947,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 32152,
+        "type": "USER",
+        "phid": "PHID-USER-rdod5yiocpcow3zy7imr",
+        "fields": {
+            "username": "Geugeor-WMF",
+            "realName": "Geugeor",
+            "mediawikiUsername": "Geugeor-WMF",
+            "roles": [
+                "approved"
+            ],
+            "dateCreated": 1644830434,
+            "dateModified": 1644830434,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31843,
+        "type": "USER",
+        "phid": "PHID-USER-fiytolp3giezaa5qmt3n",
+        "fields": {
+            "username": "AUgolnikova-WMF",
+            "realName": "",
+            "mediawikiUsername": "AUgolnikova-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1642503772,
+            "dateModified": 1642503785,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31830,
+        "type": "USER",
+        "phid": "PHID-USER-5xcfwhpd22gnwse5yt7u",
+        "fields": {
+            "username": "SLopes-WMF",
+            "realName": "S\u00e9rgio Lopes",
+            "mediawikiUsername": "SLopes-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1642409268,
+            "dateModified": 1642409290,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31711,
+        "type": "USER",
+        "phid": "PHID-USER-c4twio2buwmogl7ivtbq",
+        "fields": {
+            "username": "IZapico-WMF",
+            "realName": "",
+            "mediawikiUsername": "IZapico (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1641321823,
+            "dateModified": 1714821098,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31601,
+        "type": "USER",
+        "phid": "PHID-USER-wzo6wisafudddi3rtikp",
+        "fields": {
+            "username": "Aaharoni-WMF",
+            "realName": "Amir E. Aharoni (WMF)",
+            "mediawikiUsername": "Aaharoni-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1640337684,
+            "dateModified": 1640337756,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31585,
+        "type": "USER",
+        "phid": "PHID-USER-pg3vx6nyzhiq5wfafluh",
+        "fields": {
+            "username": "JMcLeod_WMF",
+            "realName": "JamesM",
+            "mediawikiUsername": "JMcLeod (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1640204597,
+            "dateModified": 1681207101,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31502,
+        "type": "USER",
+        "phid": "PHID-USER-g6ahwdfnf43fpurc45ey",
+        "fields": {
+            "username": "MRamirez_WMF",
+            "realName": "Maria Ramirez",
+            "mediawikiUsername": "MRamirez (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1639440304,
+            "dateModified": 1713439270,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31499,
+        "type": "USER",
+        "phid": "PHID-USER-u3zg6nshjg2auhzebw7u",
+        "fields": {
+            "username": "MShilova_WMF",
+            "realName": "Mariya Shilova",
+            "mediawikiUsername": "MShilova (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1639426652,
+            "dateModified": 1661437826,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31493,
+        "type": "USER",
+        "phid": "PHID-USER-xedc4uv6ijwhb67esc6p",
+        "fields": {
+            "username": "Adelaide_Calais_WMFr",
+            "realName": "",
+            "mediawikiUsername": "Ad\u00e9la\u00efde Calais WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1639404819,
+            "dateModified": 1639404837,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31455,
+        "type": "USER",
+        "phid": "PHID-USER-cmwatch6is2wzrnsq2of",
+        "fields": {
+            "username": "DSeyfert_WMF",
+            "realName": "Dustin Seyfert",
+            "mediawikiUsername": "DSeyfert (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1638979797,
+            "dateModified": 1722549058,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31261,
+        "type": "USER",
+        "phid": "PHID-USER-bmuhgzbr354jpr3pnbe6",
+        "fields": {
+            "username": "YLiou_WMF",
+            "realName": "Yu-Ming Liou",
+            "mediawikiUsername": "YLiou (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1637185065,
+            "dateModified": 1637185167,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31176,
+        "type": "USER",
+        "phid": "PHID-USER-sswuaazydsr25shr4plg",
+        "fields": {
+            "username": "ANakanishi_WMF",
+            "realName": "",
+            "mediawikiUsername": "ANakanishi (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1636500152,
+            "dateModified": 1702941676,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 31148,
+        "type": "USER",
+        "phid": "PHID-USER-v7df3kwnhakxh7cgcmxk",
+        "fields": {
+            "username": "DMartin-WMF",
+            "realName": "David Martin",
+            "mediawikiUsername": "DMartin (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1636161370,
+            "dateModified": 1636163191,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 30632,
+        "type": "USER",
+        "phid": "PHID-USER-3nf2j3qaabw3yhvvfpbk",
+        "fields": {
+            "username": "KCVelaga_WMF",
+            "realName": "KC",
+            "mediawikiUsername": "KCVelaga (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1631705794,
+            "dateModified": 1728583007,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 30566,
+        "type": "USER",
+        "phid": "PHID-USER-p6mxa2roof6gc7yhnje5",
+        "fields": {
+            "username": "TAdeleye_WMF",
+            "realName": "Temi",
+            "mediawikiUsername": "TAdeleye (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1631047423,
+            "dateModified": 1631047478,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 30509,
+        "type": "USER",
+        "phid": "PHID-USER-gish6k7n4hw23svhioxb",
+        "fields": {
+            "username": "AAlhazwani-WMF",
+            "realName": "Amin",
+            "mediawikiUsername": "AAlhazwani (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1630503919,
+            "dateModified": 1739284103,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 30460,
+        "type": "USER",
+        "phid": "PHID-USER-t5umzhhyjcwtlmnx4dt5",
+        "fields": {
+            "username": "Bethany",
+            "realName": "WMF",
+            "mediawikiUsername": "BGerdemann (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1630101272,
+            "dateModified": 1716835294,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 30091,
+        "type": "USER",
+        "phid": "PHID-USER-hyc7uqs3yphj4oxhrw7k",
+        "fields": {
+            "username": "CKibelka_WMF",
+            "realName": "Cornelius Kibelka",
+            "mediawikiUsername": "CKibelka (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1627388647,
+            "dateModified": 1688484041,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29793,
+        "type": "USER",
+        "phid": "PHID-USER-d7h6swnc3oqnivbzidrq",
+        "fields": {
+            "username": "MMoss_WMF",
+            "realName": "Madi Moss",
+            "mediawikiUsername": "MMoss (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1624637292,
+            "dateModified": 1624637305,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29727,
+        "type": "USER",
+        "phid": "PHID-USER-oihk4ihokuato6vxsixw",
+        "fields": {
+            "username": "DMburugu",
+            "realName": "Dennis Mburugu (WMF)",
+            "mediawikiUsername": "DMburugu (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1624030084,
+            "dateModified": 1681823738,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29697,
+        "type": "USER",
+        "phid": "PHID-USER-hsitvyc46ynsfkxa3ixe",
+        "fields": {
+            "username": "bchoo",
+            "realName": "BChoo (WMF)",
+            "mediawikiUsername": "BChoo (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1623803583,
+            "dateModified": 1623803596,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29641,
+        "type": "USER",
+        "phid": "PHID-USER-3aolm5sofjy7veqwk2zt",
+        "fields": {
+            "username": "RKumar_WMF",
+            "realName": "Rakhi",
+            "mediawikiUsername": "RKumar (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1623251723,
+            "dateModified": 1623251756,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29639,
+        "type": "USER",
+        "phid": "PHID-USER-uosfdkyt762u7wapiapw",
+        "fields": {
+            "username": "Patafisik_WMF",
+            "realName": "",
+            "mediawikiUsername": "Patafisik (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1623229495,
+            "dateModified": 1623229516,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29582,
+        "type": "USER",
+        "phid": "PHID-USER-kwvruu2vvtusu25sughu",
+        "fields": {
+            "username": "SNg_WMF",
+            "realName": "",
+            "mediawikiUsername": "SNg (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1622656687,
+            "dateModified": 1681319490,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29576,
+        "type": "USER",
+        "phid": "PHID-USER-rx6zmxgjxmn67flj34t5",
+        "fields": {
+            "username": "JBrungs_WMF",
+            "realName": "",
+            "mediawikiUsername": "JBrungs (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1622636282,
+            "dateModified": 1622636291,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29329,
+        "type": "USER",
+        "phid": "PHID-USER-qjqs3g4vsgvsu7xp3bx4",
+        "fields": {
+            "username": "Abbad_WMF",
+            "realName": "",
+            "mediawikiUsername": "Abbad (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1620526418,
+            "dateModified": 1711460806,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29165,
+        "type": "USER",
+        "phid": "PHID-USER-bozwpinzzjxxq5nzkkmn",
+        "fields": {
+            "username": "MPaul_WMF",
+            "realName": "MPaul_WMF",
+            "mediawikiUsername": "MPaul (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1618925736,
+            "dateModified": 1618925752,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 29161,
+        "type": "USER",
+        "phid": "PHID-USER-btdpuoxa3uei4xdvwbgk",
+        "fields": {
+            "username": "AKhatun_WMF",
+            "realName": "Aisha Khatun",
+            "mediawikiUsername": "AKhatun (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1618907967,
+            "dateModified": 1720011705,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "tanny411"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 28969,
+        "type": "USER",
+        "phid": "PHID-USER-exnwt7opk2kwfh3ra2ia",
+        "fields": {
+            "username": "AChang_WMF",
+            "realName": "",
+            "mediawikiUsername": "AChang (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1617811675,
+            "dateModified": 1656080320,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 28968,
+        "type": "USER",
+        "phid": "PHID-USER-hcvi3pslrgngzpbkzdmk",
+        "fields": {
+            "username": "Alejandra_Reyes_WMFr",
+            "realName": "Alejandra Reyes",
+            "mediawikiUsername": "Alejandra Reyes WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1617809574,
+            "dateModified": 1617809668,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 28683,
+        "type": "USER",
+        "phid": "PHID-USER-rqawir4jqupmkohkutxb",
+        "fields": {
+            "username": "LZaman",
+            "realName": "lzaman_WMF",
+            "mediawikiUsername": "LZaman (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1616510258,
+            "dateModified": 1639561147,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 28668,
+        "type": "USER",
+        "phid": "PHID-USER-orv5mcf5st35inouzwu3",
+        "fields": {
+            "username": "ldelench_wmf",
+            "realName": "Lauren de Lench",
+            "mediawikiUsername": "LDelench (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1616428222,
+            "dateModified": 1678458313,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 28271,
+        "type": "USER",
+        "phid": "PHID-USER-sid43bbu224hk6l6epak",
+        "fields": {
+            "username": "Xeno_WMF",
+            "realName": "Xeno",
+            "mediawikiUsername": "Xeno (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1614263030,
+            "dateModified": 1626785632,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 28198,
+        "type": "USER",
+        "phid": "PHID-USER-txushwvxfdgmez5gphl7",
+        "fields": {
+            "username": "MRaishWMF",
+            "realName": "Mike Raish",
+            "mediawikiUsername": "MRaish (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1613748212,
+            "dateModified": 1613748223,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 28105,
+        "type": "USER",
+        "phid": "PHID-USER-srjgz6nhffsjqxmigvmm",
+        "fields": {
+            "username": "MCasoValdes_WMF",
+            "realName": "Mercedes Caso",
+            "mediawikiUsername": "MCasoValdes (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1613061645,
+            "dateModified": 1739031109,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 27800,
+        "type": "USER",
+        "phid": "PHID-USER-ryxfiblmathwyazdz6x6",
+        "fields": {
+            "username": "STei-WMF",
+            "realName": "Sandister",
+            "mediawikiUsername": "STei (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1610973726,
+            "dateModified": 1663763661,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 27683,
+        "type": "USER",
+        "phid": "PHID-USER-ma752izlg6twocdnbnz6",
+        "fields": {
+            "username": "mickeybarber",
+            "realName": "Michael Barbereau WMFr",
+            "mediawikiUsername": "Michael Barbereau WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1610131033,
+            "dateModified": 1675850927,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 27578,
+        "type": "USER",
+        "phid": "PHID-USER-lbnjm26jgivkqd5qb3nq",
+        "fields": {
+            "username": "UOzurumba",
+            "realName": "Uzoma-WMF",
+            "mediawikiUsername": "UOzurumba (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1609268386,
+            "dateModified": 1609887198,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 27485,
+        "type": "USER",
+        "phid": "PHID-USER-nr6zcylxpt25qezydhea",
+        "fields": {
+            "username": "GFontenelle_WMF",
+            "realName": "Giovanna Fontenelle",
+            "mediawikiUsername": "GFontenelle (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1608392236,
+            "dateModified": 1618505435,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 27425,
+        "type": "USER",
+        "phid": "PHID-USER-4yee2alxfejgw4pdoyff",
+        "fields": {
+            "username": "Ankan_WMF",
+            "realName": "Ankan",
+            "mediawikiUsername": "Ankan (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1607957469,
+            "dateModified": 1718106550,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 27281,
+        "type": "USER",
+        "phid": "PHID-USER-rr2a3kt66kwm5gcebmpp",
+        "fields": {
+            "username": "MPhamWMF",
+            "realName": "",
+            "mediawikiUsername": "MPham (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1606843628,
+            "dateModified": 1718236426,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 26929,
+        "type": "USER",
+        "phid": "PHID-USER-q2inkkqhmsawczthflaq",
+        "fields": {
+            "username": "gmodena",
+            "realName": "GModena (WMF)",
+            "mediawikiUsername": "GModena (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1604322904,
+            "dateModified": 1695838224,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "gmodena"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 26573,
+        "type": "USER",
+        "phid": "PHID-USER-h56zvewfdl3gekg5z4pt",
+        "fields": {
+            "username": "MDemosWMF",
+            "realName": "Melanie Demos",
+            "mediawikiUsername": "MDemos (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1602096896,
+            "dateModified": 1602096909,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 26500,
+        "type": "USER",
+        "phid": "PHID-USER-qeuim6tntu4hujw2g4wa",
+        "fields": {
+            "username": "KMpumlwana_WMF",
+            "realName": "Khanyi",
+            "mediawikiUsername": "KMpumlwana (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1601649715,
+            "dateModified": 1704198678,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 26492,
+        "type": "USER",
+        "phid": "PHID-USER-k7ife5r2n7yppjfgmsss",
+        "fields": {
+            "username": "Yael-weissburg",
+            "realName": "Yael Weissburg, Strategic Partnerships WMF",
+            "mediawikiUsername": "Yael-weissburg",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1601596668,
+            "dateModified": 1601596693,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 26371,
+        "type": "USER",
+        "phid": "PHID-USER-6p73okbehsky7dy26eyc",
+        "fields": {
+            "username": "RSharma_WMF",
+            "realName": "RUPIKA_SHARMA",
+            "mediawikiUsername": "RSharma (WMF)",
+            "roles": [
+                "disabled",
+                "approved"
+            ],
+            "dateCreated": 1600857472,
+            "dateModified": 1688747986,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 26052,
+        "type": "USER",
+        "phid": "PHID-USER-r4l5epi2qcip4y7bneub",
+        "fields": {
+            "username": "HNordeenWMF",
+            "realName": "",
+            "mediawikiUsername": "HNordeen (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1598286277,
+            "dateModified": 1734650795,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 26023,
+        "type": "USER",
+        "phid": "PHID-USER-l3tl3jokizqdpfadpnup",
+        "fields": {
+            "username": "Urbanecm_WMF",
+            "realName": "Martin Urbanec / Urbanecm",
+            "mediawikiUsername": "Martin Urbanec (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1598007930,
+            "dateModified": 1688672739,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "urbanecm"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 25643,
+        "type": "USER",
+        "phid": "PHID-USER-hcfk3igh4aifxebwlu67",
+        "fields": {
+            "username": "KValenciaWMF",
+            "realName": "Kevin Valencia",
+            "mediawikiUsername": "KValencia (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1594934120,
+            "dateModified": 1594934148,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 25440,
+        "type": "USER",
+        "phid": "PHID-USER-jaseglfvgfgle74jxkka",
+        "fields": {
+            "username": "RStearns_WMF",
+            "realName": "Randy Stearns",
+            "mediawikiUsername": "RStearns (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1593446985,
+            "dateModified": 1593447004,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 25192,
+        "type": "USER",
+        "phid": "PHID-USER-d6utyjdvw5z3v5hciihh",
+        "fields": {
+            "username": "FRomeo_WMF",
+            "realName": "Fiona Romeo",
+            "mediawikiUsername": "FRomeo (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1591627224,
+            "dateModified": 1591627247,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 25072,
+        "type": "USER",
+        "phid": "PHID-USER-tkjfqp6fijlfmymyoeib",
+        "fields": {
+            "username": "RBrounley_WMF",
+            "realName": "Ryan",
+            "mediawikiUsername": "RBrounley (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1590796334,
+            "dateModified": 1688799724,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 23619,
+        "type": "USER",
+        "phid": "PHID-USER-3ldsqumzzxp67v5wizyz",
+        "fields": {
+            "username": "LDickinsonWMF",
+            "realName": "Lauren Dickinson",
+            "mediawikiUsername": "LDickinson (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1582137290,
+            "dateModified": 1582137300,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 23539,
+        "type": "USER",
+        "phid": "PHID-USER-k46kyorhhvitjwvcxoqa",
+        "fields": {
+            "username": "CBogen",
+            "realName": "Carly Bogen (WMF)",
+            "mediawikiUsername": "CBogen (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1581620148,
+            "dateModified": 1583253050,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 23452,
+        "type": "USER",
+        "phid": "PHID-USER-zaiwv2u4s57dijuytt4o",
+        "fields": {
+            "username": "Rileych",
+            "realName": "Chelsea Riley (WMF)",
+            "mediawikiUsername": "CRiley (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1581006982,
+            "dateModified": 1634557025,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 23445,
+        "type": "USER",
+        "phid": "PHID-USER-pemlflapk2pxbplbgsuf",
+        "fields": {
+            "username": "SGautam_WMF",
+            "realName": "Sudhanshu",
+            "mediawikiUsername": "SGautam (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1580993132,
+            "dateModified": 1580993149,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 23086,
+        "type": "USER",
+        "phid": "PHID-USER-wfitjkcijxsivlfpc3mb",
+        "fields": {
+            "username": "ARamirez_WMF",
+            "realName": "Aida Alejandra Ramirez",
+            "mediawikiUsername": "ARamirez (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1578442321,
+            "dateModified": 1712937136,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 23078,
+        "type": "USER",
+        "phid": "PHID-USER-7tsz7e5krfc7ng6ihkjr",
+        "fields": {
+            "username": "DAlangi_WMF",
+            "realName": "",
+            "mediawikiUsername": "DAlangi (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1578396614,
+            "dateModified": 1688557968,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "xSavitar"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 22815,
+        "type": "USER",
+        "phid": "PHID-USER-tdki3gemzpe42nmbibbs",
+        "fields": {
+            "username": "SNowick_WMF",
+            "realName": "Shay",
+            "mediawikiUsername": "SNowick (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1576524057,
+            "dateModified": 1601575363,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 22031,
+        "type": "USER",
+        "phid": "PHID-USER-t46t6kzswtfbfqoj4rae",
+        "fields": {
+            "username": "MKaurWMF",
+            "realName": "Manav",
+            "mediawikiUsername": "MKaur (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1572193195,
+            "dateModified": 1621811701,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 21982,
+        "type": "USER",
+        "phid": "PHID-USER-tjoqvhsvynujiid4kbb6",
+        "fields": {
+            "username": "Lgruwell-WMF",
+            "realName": "Lisa Seitz",
+            "mediawikiUsername": "Lgruwell-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1571848114,
+            "dateModified": 1571848165,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 21504,
+        "type": "USER",
+        "phid": "PHID-USER-ht4pprq7fnrih3rxytlh",
+        "fields": {
+            "username": "EZar-WMF",
+            "realName": "Essie",
+            "mediawikiUsername": "EZar (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1568647514,
+            "dateModified": 1632926134,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 21445,
+        "type": "USER",
+        "phid": "PHID-USER-samyzygdvef45id52vxf",
+        "fields": {
+            "username": "RSalazar_WMF",
+            "realName": "Rocio Salazar",
+            "mediawikiUsername": "RSalazar (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1568236492,
+            "dateModified": 1605946073,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 21385,
+        "type": "USER",
+        "phid": "PHID-USER-beishjcrhgd3gnrc6z5q",
+        "fields": {
+            "username": "CDenes_WMF",
+            "realName": "Camille de Nes",
+            "mediawikiUsername": "CDenes (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1567767160,
+            "dateModified": 1567767182,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 21270,
+        "type": "USER",
+        "phid": "PHID-USER-ef55eugqx6uq6ltqhtkz",
+        "fields": {
+            "username": "MPourzaki_WMF",
+            "realName": "Mehrdad",
+            "mediawikiUsername": "MPourzaki (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1567104861,
+            "dateModified": 1710697040,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 21126,
+        "type": "USER",
+        "phid": "PHID-USER-azzj6h7p7fnvk76vcyzt",
+        "fields": {
+            "username": "MSuijkerbuijk_WMF",
+            "realName": "",
+            "mediawikiUsername": "MSuijkerbuijk (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1565951504,
+            "dateModified": 1565951525,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 20813,
+        "type": "USER",
+        "phid": "PHID-USER-4aqt7pd2l3aejioztj4d",
+        "fields": {
+            "username": "DRanville_WMF",
+            "realName": "Diane / Opsylac",
+            "mediawikiUsername": "DRanville (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1563435818,
+            "dateModified": 1632926133,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 20633,
+        "type": "USER",
+        "phid": "PHID-USER-sv3nrekqj7b64f2xd3jo",
+        "fields": {
+            "username": "vhargyono-WMF",
+            "realName": "Vasanthi",
+            "mediawikiUsername": "VHargyono (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1562059264,
+            "dateModified": 1694961555,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 20576,
+        "type": "USER",
+        "phid": "PHID-USER-vnwn5zmxf7zvtd2lcggj",
+        "fields": {
+            "username": "Woubzena",
+            "realName": "WJifar (WMF)",
+            "mediawikiUsername": "WJifar (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1561590108,
+            "dateModified": 1602959387,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 20463,
+        "type": "USER",
+        "phid": "PHID-USER-a74xxlw4m4gosisvrxuv",
+        "fields": {
+            "username": "Dyolf77_WMF",
+            "realName": "Habib Mhenni",
+            "mediawikiUsername": "Dyolf77 (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1560781081,
+            "dateModified": 1716920127,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 19937,
+        "type": "USER",
+        "phid": "PHID-USER-m4eprzgku3qj6jomsjnm",
+        "fields": {
+            "username": "MGuadalupeWMF",
+            "realName": "Melissa Guadalupe Huertas",
+            "mediawikiUsername": "MGuadalupe (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1556808828,
+            "dateModified": 1558714593,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 19769,
+        "type": "USER",
+        "phid": "PHID-USER-w3clwynho4jqumonmmli",
+        "fields": {
+            "username": "JFishback_WMF",
+            "realName": "James",
+            "mediawikiUsername": "JFishback (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1555431405,
+            "dateModified": 1707923667,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "jfishback"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 19572,
+        "type": "USER",
+        "phid": "PHID-USER-hx7mn7y7biqi3oacdwpe",
+        "fields": {
+            "username": "WDoranWMF",
+            "realName": "Will Doran",
+            "mediawikiUsername": "WDoran (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1554150124,
+            "dateModified": 1728148323,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 19231,
+        "type": "USER",
+        "phid": "PHID-USER-woqgbng6hxhgthq6bhry",
+        "fields": {
+            "username": "JLetangWMF",
+            "realName": "Joel ",
+            "mediawikiUsername": "JLetang (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1551946191,
+            "dateModified": 1670273127,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 18940,
+        "type": "USER",
+        "phid": "PHID-USER-mwa7yl4t4imnbniyn6q2",
+        "fields": {
+            "username": "WMFOffice",
+            "realName": "",
+            "mediawikiUsername": "WMFOffice",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1550614258,
+            "dateModified": 1550614522,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 17965,
+        "type": "USER",
+        "phid": "PHID-USER-xtjmtxilromjmk75wdsq",
+        "fields": {
+            "username": "elappen-WMF",
+            "realName": "Elena Lappen",
+            "mediawikiUsername": "ELappen (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1543856646,
+            "dateModified": 1547770056,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 17259,
+        "type": "USER",
+        "phid": "PHID-USER-j662km5vkckh7t5rgr3a",
+        "fields": {
+            "username": "IJethroBT-WMF",
+            "realName": "Christopher Schilling",
+            "mediawikiUsername": "I JethroBT (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1540223304,
+            "dateModified": 1569348279,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 16567,
+        "type": "USER",
+        "phid": "PHID-USER-fx6welp5ofmuafu66zsz",
+        "fields": {
+            "username": "nettrom_WMF",
+            "realName": "Morten Warncke-Wang",
+            "mediawikiUsername": "MWang (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1534882982,
+            "dateModified": 1594317173,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "Nettrom"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 16464,
+        "type": "USER",
+        "phid": "PHID-USER-cpa73wmh5x7jqufnhzxc",
+        "fields": {
+            "username": "sguebo_WMF",
+            "realName": "Samuel Guebo",
+            "mediawikiUsername": "Samuel (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1533917854,
+            "dateModified": 1676030854,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 16401,
+        "type": "USER",
+        "phid": "PHID-USER-vswhijdjv5fnivxqf4ay",
+        "fields": {
+            "username": "Thargrovewmf",
+            "realName": "ty",
+            "mediawikiUsername": "THargrove (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1533320173,
+            "dateModified": 1589566993,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 15857,
+        "type": "USER",
+        "phid": "PHID-USER-jlrpflwfwzztoyl6a4pr",
+        "fields": {
+            "username": "JLaytonWMF",
+            "realName": "Janna Layton",
+            "mediawikiUsername": "JLayton (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1529000419,
+            "dateModified": 1529000430,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 15476,
+        "type": "USER",
+        "phid": "PHID-USER-hqyy4wr7smuc4rzaoio5",
+        "fields": {
+            "username": "JTannerWMF",
+            "realName": "Jazmin",
+            "mediawikiUsername": "JTanner (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1526319820,
+            "dateModified": 1610042472,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 15312,
+        "type": "USER",
+        "phid": "PHID-USER-alzdkqvyyarshbn7tgxo",
+        "fields": {
+            "username": "Dreamy_Jazz",
+            "realName": "WBrown (WMF)",
+            "mediawikiUsername": "Dreamy Jazz",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1525193758,
+            "dateModified": 1739360722,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "Dreamy_Jazz"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 14585,
+        "type": "USER",
+        "phid": "PHID-USER-krko4robkho2pjor6klf",
+        "fields": {
+            "username": "MMiller_WMF",
+            "realName": "Marshall Miller",
+            "mediawikiUsername": "MMiller (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1520274041,
+            "dateModified": 1540332310,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 14490,
+        "type": "USER",
+        "phid": "PHID-USER-spi4zwso5j56niexv6nm",
+        "fields": {
+            "username": "AmelieWFr",
+            "realName": "Amelie Cabon WMFr",
+            "mediawikiUsername": "Am\u00e9lie Cabon WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1519814057,
+            "dateModified": 1550490344,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 14460,
+        "type": "USER",
+        "phid": "PHID-USER-fjb4a4xug4p2wmtvfxiu",
+        "fields": {
+            "username": "RAyyakkannu_WMF",
+            "realName": "Ravi",
+            "mediawikiUsername": "RAyyakkannu (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1519659883,
+            "dateModified": 1583685789,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 14397,
+        "type": "USER",
+        "phid": "PHID-USER-cjbkqgaozso5gfp3xv2n",
+        "fields": {
+            "username": "alexhollender_WMF",
+            "realName": "Alex Hollender",
+            "mediawikiUsername": "AHollender (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1519260589,
+            "dateModified": 1704908594,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 14191,
+        "type": "USER",
+        "phid": "PHID-USER-6un32vdjaxh75edwte4n",
+        "fields": {
+            "username": "DNdubane_WMF",
+            "realName": "Dumisani",
+            "mediawikiUsername": "DNdubane (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1517998917,
+            "dateModified": 1722554946,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 14009,
+        "type": "USER",
+        "phid": "PHID-USER-7tjcqpnixwfvv4kqloqn",
+        "fields": {
+            "username": "MNovotny_WMF",
+            "realName": "Margeigh Novotny",
+            "mediawikiUsername": "MNovotny (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1516826247,
+            "dateModified": 1692429199,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 13722,
+        "type": "USER",
+        "phid": "PHID-USER-oo57v3mglfky7rwvhnwh",
+        "fields": {
+            "username": "Jonathan_WMFr",
+            "realName": "",
+            "mediawikiUsername": "Jonathan Balima WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1515063248,
+            "dateModified": 1515063264,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 12687,
+        "type": "USER",
+        "phid": "PHID-USER-nznhtgtfvtsbjzpsbomv",
+        "fields": {
+            "username": "PDrouin-WMF",
+            "realName": "Pam Drouin",
+            "mediawikiUsername": "PDrouin (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1507154142,
+            "dateModified": 1584553815,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 12171,
+        "type": "USER",
+        "phid": "PHID-USER-u7rndah2e3w4ri3cx5gd",
+        "fields": {
+            "username": "BVershbow_WMF",
+            "realName": "Ben",
+            "mediawikiUsername": "BVershbow (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1503601622,
+            "dateModified": 1622831176,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 12170,
+        "type": "USER",
+        "phid": "PHID-USER-s4ovs3cixbnc7fhnzjto",
+        "fields": {
+            "username": "Ramsey-WMF",
+            "realName": "Ramsey Isler",
+            "mediawikiUsername": "RIsler (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1503591603,
+            "dateModified": 1704909524,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 11773,
+        "type": "USER",
+        "phid": "PHID-USER-rizrvu26ar4azamanlp7",
+        "fields": {
+            "username": "CCicalese_WMF",
+            "realName": "Cindy Cicalese",
+            "mediawikiUsername": "CCicalese (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1501122703,
+            "dateModified": 1502378264,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 11437,
+        "type": "USER",
+        "phid": "PHID-USER-hnic7qh54vwfc5ps55ib",
+        "fields": {
+            "username": "SandraF_WMF",
+            "realName": "Sandra Fauconnier",
+            "mediawikiUsername": "SandraF (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1499075785,
+            "dateModified": 1671611208,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "spinster"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 10691,
+        "type": "USER",
+        "phid": "PHID-USER-gqulw6l6ua22uw6szp2r",
+        "fields": {
+            "username": "GereonKalkuhlWMF",
+            "realName": "Gereon Kalkuhl (WMF)",
+            "mediawikiUsername": "Gereon Kalkuhl (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1494692414,
+            "dateModified": 1736803821,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 10507,
+        "type": "USER",
+        "phid": "PHID-USER-cnm6fvpmlpz6pi5pl4rq",
+        "fields": {
+            "username": "MNoorWMF",
+            "realName": "",
+            "mediawikiUsername": "MShaver (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1493139067,
+            "dateModified": 1656080440,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 10415,
+        "type": "USER",
+        "phid": "PHID-USER-3rtspghxcd6lyd75e2yx",
+        "fields": {
+            "username": "AVasanth_WMF",
+            "realName": "Aaron Vasanth",
+            "mediawikiUsername": "AVasanth (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1492538237,
+            "dateModified": 1706832015,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 10327,
+        "type": "USER",
+        "phid": "PHID-USER-3ycwegbo7rfwvq6npqkp",
+        "fields": {
+            "username": "CSindersWMF",
+            "realName": "caroline sinders",
+            "mediawikiUsername": "CSinders (WMF)",
+            "roles": [
+                "disabled",
+                "approved"
+            ],
+            "dateCreated": 1491843333,
+            "dateModified": 1583685962,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 10270,
+        "type": "USER",
+        "phid": "PHID-USER-ylfheofbegcszvuwmqug",
+        "fields": {
+            "username": "DWilliamsWMF",
+            "realName": "Dianne",
+            "mediawikiUsername": "DWilliams (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1491406480,
+            "dateModified": 1583864034,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 9838,
+        "type": "USER",
+        "phid": "PHID-USER-ns7v2ss47eb37eugltrm",
+        "fields": {
+            "username": "OShehata_WMF",
+            "realName": "Omar Shehata",
+            "mediawikiUsername": "OShehata (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1488386845,
+            "dateModified": 1583686413,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 9596,
+        "type": "USER",
+        "phid": "PHID-USER-vgqpuaydwi66vdcttjqj",
+        "fields": {
+            "username": "Xenophon",
+            "realName": "Remy WMFr",
+            "mediawikiUsername": "Xenoph\u00f4n",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1486476606,
+            "dateModified": 1486476658,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 9262,
+        "type": "USER",
+        "phid": "PHID-USER-bbfrj4tw5tcpnyrvgh6c",
+        "fields": {
+            "username": "ABorbaWMF",
+            "realName": "",
+            "mediawikiUsername": "ABorba (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1483991456,
+            "dateModified": 1489701418,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 9052,
+        "type": "USER",
+        "phid": "PHID-USER-y7nwsjjzumufr7fhd44p",
+        "fields": {
+            "username": "Xavier-WMFr",
+            "realName": "Xavier Cailleau",
+            "mediawikiUsername": "Xavier Cailleau WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1481796087,
+            "dateModified": 1553781239,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 8196,
+        "type": "USER",
+        "phid": "PHID-USER-2rpn72fykefzsfh6e2m4",
+        "fields": {
+            "username": "SMalikWMF",
+            "realName": "",
+            "mediawikiUsername": "SMalik (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1474321561,
+            "dateModified": 1583686465,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 8193,
+        "type": "USER",
+        "phid": "PHID-USER-ev5njt6ynenwaa6whrjc",
+        "fields": {
+            "username": "NHarateh_WMF",
+            "realName": "Natalia Harateh",
+            "mediawikiUsername": "NHarateh (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1474312423,
+            "dateModified": 1574313947,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 8191,
+        "type": "USER",
+        "phid": "PHID-USER-goap3fegdomx6jbbahqv",
+        "fields": {
+            "username": "Ocaasi_WMF",
+            "realName": "Jake Orlowitz",
+            "mediawikiUsername": "Ocaasi (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1474306561,
+            "dateModified": 1568093541,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 8043,
+        "type": "USER",
+        "phid": "PHID-USER-7icaawxrer5mi3xlhhox",
+        "fields": {
+            "username": "Jules_WMFr",
+            "realName": "Jules X\u00e9nard",
+            "mediawikiUsername": "Jules WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1473167828,
+            "dateModified": 1476354388,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 7973,
+        "type": "USER",
+        "phid": "PHID-USER-wgnf63ha7u7kzh4v5ryh",
+        "fields": {
+            "username": "LGoto",
+            "realName": "Lani Goto (WMF)",
+            "mediawikiUsername": "LGoto (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1472495077,
+            "dateModified": 1617136085,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 7811,
+        "type": "USER",
+        "phid": "PHID-USER-y3plhie4f7ikf353vwxt",
+        "fields": {
+            "username": "RStallman-legalteam",
+            "realName": "RStallman (WMF)",
+            "mediawikiUsername": "RStallman (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1471382112,
+            "dateModified": 1490846623,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 7658,
+        "type": "USER",
+        "phid": "PHID-USER-qfn4mie23fh6wvbexjpy",
+        "fields": {
+            "username": "SarahWMFr",
+            "realName": "",
+            "mediawikiUsername": "Sarah Krichen WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1470131455,
+            "dateModified": 1470131471,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 7490,
+        "type": "USER",
+        "phid": "PHID-USER-ith747wgwmhplqvrcigu",
+        "fields": {
+            "username": "HJiang-WMF",
+            "realName": "HJiang-WMF",
+            "mediawikiUsername": "HJiang (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1468649602,
+            "dateModified": 1498059603,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 7474,
+        "type": "USER",
+        "phid": "PHID-USER-choai5trnusdoq35fy42",
+        "fields": {
+            "username": "JbuattiWMF",
+            "realName": "Jim",
+            "mediawikiUsername": "Jbuatti (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1468531347,
+            "dateModified": 1468531361,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 7221,
+        "type": "USER",
+        "phid": "PHID-USER-lee3lethmxfg4mqqb6ge",
+        "fields": {
+            "username": "Delphine_wmf",
+            "realName": "Delphine M\u00e9nard",
+            "mediawikiUsername": "Delphine (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1466431873,
+            "dateModified": 1645643285,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "delphine"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 6870,
+        "type": "USER",
+        "phid": "PHID-USER-uarm7omuyyilnstns6on",
+        "fields": {
+            "username": "VMasrour-WMF",
+            "realName": "Vahid Masrour",
+            "mediawikiUsername": "VMasrour (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1462980609,
+            "dateModified": 1563751834,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 6189,
+        "type": "USER",
+        "phid": "PHID-USER-i7q7xmht6j76kjuqtnc4",
+        "fields": {
+            "username": "mjue_wmf",
+            "realName": "Morgan Jue",
+            "mediawikiUsername": "MJue (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1456877238,
+            "dateModified": 1456877252,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 6161,
+        "type": "USER",
+        "phid": "PHID-USER-fjy7lhypg2x7jltr2dtl",
+        "fields": {
+            "username": "Remy_WMFr",
+            "realName": "R\u00e9my Gerbet",
+            "mediawikiUsername": "R\u00e9my Gerbet WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1456753845,
+            "dateModified": 1567170787,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 6037,
+        "type": "USER",
+        "phid": "PHID-USER-mvx4x7ywk2flsaku2dbk",
+        "fields": {
+            "username": "AlexMonk-WMF",
+            "realName": "Alex Monk",
+            "mediawikiUsername": "Alex Monk (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1455912914,
+            "dateModified": 1485643995,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "Krenair"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 5755,
+        "type": "USER",
+        "phid": "PHID-USER-iwx53fdq7w3yv4h7wffx",
+        "fields": {
+            "username": "CKoerner_WMF",
+            "realName": "Chris Koerner - WMF",
+            "mediawikiUsername": "CKoerner (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1453842401,
+            "dateModified": 1736297651,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "CKoerner_WMF"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 5532,
+        "type": "USER",
+        "phid": "PHID-USER-cgw4o6eavdk7iiz2ylah",
+        "fields": {
+            "username": "APalmer_WMF",
+            "realName": "Aeryn Palmer",
+            "mediawikiUsername": "APalmer (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1452130865,
+            "dateModified": 1469650525,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 5480,
+        "type": "USER",
+        "phid": "PHID-USER-wfdcjvceejrq2ktibp4j",
+        "fields": {
+            "username": "In2thats12",
+            "realName": "Pgehres (WMF)",
+            "mediawikiUsername": "In2thats12",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1451805196,
+            "dateModified": 1451805324,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 5017,
+        "type": "USER",
+        "phid": "PHID-USER-apzfaysehenx5w3n6pet",
+        "fields": {
+            "username": "Sophie_wmfr",
+            "realName": "",
+            "mediawikiUsername": "Sophie wmfr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1448382000,
+            "dateModified": 1448382023,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 5016,
+        "type": "USER",
+        "phid": "PHID-USER-oonyeotcauxgekr3jpdy",
+        "fields": {
+            "username": "Nathalie_Martin_WMFR",
+            "realName": "Nathalie Martin",
+            "mediawikiUsername": "Nathalie Martin (WMFR)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1448376387,
+            "dateModified": 1448376399,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 5004,
+        "type": "USER",
+        "phid": "PHID-USER-5ocgzb3ti5hztwstf6kz",
+        "fields": {
+            "username": "NadiaWMFr",
+            "realName": "Nadia AYACHI",
+            "mediawikiUsername": "NadiaWMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1448276162,
+            "dateModified": 1448276172,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 5003,
+        "type": "USER",
+        "phid": "PHID-USER-6k3mlg5vjm3byfb2ztbb",
+        "fields": {
+            "username": "Cyrille_WMFr",
+            "realName": "Cyrille BERTIN",
+            "mediawikiUsername": "Cyrille WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1448275712,
+            "dateModified": 1448275726,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 5002,
+        "type": "USER",
+        "phid": "PHID-USER-o3qdrebzrx6mz5j7zclf",
+        "fields": {
+            "username": "Pierre_Antoine_WMFr",
+            "realName": "Pierre Antoine LE PAGE",
+            "mediawikiUsername": "Pierre Antoine WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1448274827,
+            "dateModified": 1448274842,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 4966,
+        "type": "USER",
+        "phid": "PHID-USER-daiulkldkngw65r75c5v",
+        "fields": {
+            "username": "Anne-LaureWMFr",
+            "realName": "",
+            "mediawikiUsername": "Anne-Laure WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1448011262,
+            "dateModified": 1448011296,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 4287,
+        "type": "USER",
+        "phid": "PHID-USER-ttyyrgsrkyonct7hizgv",
+        "fields": {
+            "username": "PEarleyWMF",
+            "realName": "Patrick Earley",
+            "mediawikiUsername": "PEarley (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1443129899,
+            "dateModified": 1710696958,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 4256,
+        "type": "USER",
+        "phid": "PHID-USER-lckpozjo4xngwboo35az",
+        "fields": {
+            "username": "JUnikowski_WMF",
+            "realName": "Jonathan Unikowski (WMF)",
+            "mediawikiUsername": "JUnikowski (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1442870879,
+            "dateModified": 1563811176,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 4025,
+        "type": "USER",
+        "phid": "PHID-USER-zqsrtij4rv5bb5pvxhpe",
+        "fields": {
+            "username": "TGilbey-WMF",
+            "realName": "",
+            "mediawikiUsername": "TGilbey (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1441221104,
+            "dateModified": 1583686214,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 3871,
+        "type": "USER",
+        "phid": "PHID-USER-dvtfg64nrbfju7sgavlh",
+        "fields": {
+            "username": "ACella_WMF",
+            "realName": "Alex Cella",
+            "mediawikiUsername": "ACella (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1439935939,
+            "dateModified": 1498059464,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 3661,
+        "type": "USER",
+        "phid": "PHID-USER-almbmuy6a3hcls7c2zdl",
+        "fields": {
+            "username": "EWilfong_WMF",
+            "realName": "Eric Wilfong",
+            "mediawikiUsername": "EWilfong (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1438018937,
+            "dateModified": 1438019240,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 3460,
+        "type": "USER",
+        "phid": "PHID-USER-rg2dpcstyjbejkfw3gni",
+        "fields": {
+            "username": "Kalliope",
+            "realName": "Kalliope_WMF",
+            "mediawikiUsername": "Kalliope (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1436167712,
+            "dateModified": 1680352033,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "oxyacantha"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 3407,
+        "type": "USER",
+        "phid": "PHID-USER-tafu2uuupsf2oupzja23",
+        "fields": {
+            "username": "EdErhart-WMF",
+            "realName": "Ed Erhart",
+            "mediawikiUsername": "Ed Erhart (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1435701662,
+            "dateModified": 1498068099,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 3182,
+        "type": "USER",
+        "phid": "PHID-USER-tioxazw2fuz343rd7tvd",
+        "fields": {
+            "username": "SLien_WMF",
+            "realName": "Sam ",
+            "mediawikiUsername": "SLien (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1433973861,
+            "dateModified": 1683907898,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 3179,
+        "type": "USER",
+        "phid": "PHID-USER-kmnt2js6fskud6zu5daa",
+        "fields": {
+            "username": "Katherine-WMF",
+            "realName": "krmaher",
+            "mediawikiUsername": "Katherine (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1433958055,
+            "dateModified": 1618644344,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "krmaher"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 3123,
+        "type": "USER",
+        "phid": "PHID-USER-3vherldaz6ttjvvnimpj",
+        "fields": {
+            "username": "MBinder_WMF",
+            "realName": "Max Binder",
+            "mediawikiUsername": "MBinder (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1433454332,
+            "dateModified": 1696279960,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "maxbinder"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 3039,
+        "type": "USER",
+        "phid": "PHID-USER-uciss2jl2e4ifxqqk7wk",
+        "fields": {
+            "username": "Trizek-WMF",
+            "realName": "Beno\u00eet Evellin",
+            "mediawikiUsername": "Trizek (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1432564926,
+            "dateModified": 1713776020,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 2966,
+        "type": "USER",
+        "phid": "PHID-USER-3znuwdgdyqj2fp5qjepy",
+        "fields": {
+            "username": "Mjohnson_WMF",
+            "realName": "",
+            "mediawikiUsername": "Mjohnson (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1432063909,
+            "dateModified": 1673206833,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 2915,
+        "type": "USER",
+        "phid": "PHID-USER-k3fxewquh652htl7ssil",
+        "fields": {
+            "username": "Sadads",
+            "realName": "aka Astinson (WMF), Alex Stinson",
+            "mediawikiUsername": "Sadads",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1431448250,
+            "dateModified": 1726707776,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "Sadads"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 2860,
+        "type": "USER",
+        "phid": "PHID-USER-56jjdupteuqbc743z2wy",
+        "fields": {
+            "username": "ZhouZ",
+            "realName": "ZhouZ-WMF",
+            "mediawikiUsername": "Zhousquared",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1430870408,
+            "dateModified": 1507977482,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 2694,
+        "type": "USER",
+        "phid": "PHID-USER-vixhpqcaqfpdj6impfwy",
+        "fields": {
+            "username": "nshahquinn-wmf",
+            "realName": "Neil Shah-Quinn",
+            "mediawikiUsername": "Neil Shah-Quinn (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1429201022,
+            "dateModified": 1715035748,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 2300,
+        "type": "USER",
+        "phid": "PHID-USER-idvtqbd3jdldeanpdgjo",
+        "fields": {
+            "username": "Jrogers-WMF",
+            "realName": "Jacob",
+            "mediawikiUsername": "Jrogers (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1426280829,
+            "dateModified": 1466695703,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 2293,
+        "type": "USER",
+        "phid": "PHID-USER-ksxcfwf6vvnfvopbps4h",
+        "fields": {
+            "username": "Samwalton9-WMF",
+            "realName": "Sam Walton",
+            "mediawikiUsername": "Samwalton9 (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1426254468,
+            "dateModified": 1707331124,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "Samwalton9"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 2272,
+        "type": "USER",
+        "phid": "PHID-USER-jgn6ll7uul4yrddtgicr",
+        "fields": {
+            "username": "Selsharbaty-WMF",
+            "realName": "Samir Elsharbaty",
+            "mediawikiUsername": "Selsharbaty (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1426105928,
+            "dateModified": 1718900203,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 2142,
+        "type": "USER",
+        "phid": "PHID-USER-pjgh3jyt5fdffgds4okk",
+        "fields": {
+            "username": "mcruzWMF",
+            "realName": "Mar\u00eda Cruz",
+            "mediawikiUsername": "MCruz (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1425408702,
+            "dateModified": 1567604563,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1969,
+        "type": "USER",
+        "phid": "PHID-USER-42sn3gaubz4csl2xcblh",
+        "fields": {
+            "username": "Kacie",
+            "realName": "KHarold (WMF)",
+            "mediawikiUsername": "KHarold (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1424201850,
+            "dateModified": 1583685336,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1903,
+        "type": "USER",
+        "phid": "PHID-USER-wplzfp6ulg4tuzwl3or6",
+        "fields": {
+            "username": "Moushira",
+            "realName": "Moushira (WMF)",
+            "mediawikiUsername": "Melamrawy (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1423749002,
+            "dateModified": 1644318398,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "Moushira"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1881,
+        "type": "USER",
+        "phid": "PHID-USER-vlaaa7vapg5c2fisdymo",
+        "fields": {
+            "username": "JeanPhilippe_WMFr",
+            "realName": "Jean-Philippe WMFr",
+            "mediawikiUsername": "Jean-Philippe WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1423668549,
+            "dateModified": 1433253393,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1880,
+        "type": "USER",
+        "phid": "PHID-USER-5upf5j33bmxvmaoeb5ia",
+        "fields": {
+            "username": "MatsWMFr",
+            "realName": "Mathieu Denel",
+            "mediawikiUsername": "Mathieu Denel WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1423668518,
+            "dateModified": 1638356909,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1826,
+        "type": "USER",
+        "phid": "PHID-USER-joqqkabmjmvxeucx4ni2",
+        "fields": {
+            "username": "Mdennis-WMF",
+            "realName": "Maggie Dennis",
+            "mediawikiUsername": "Mdennis (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1423239059,
+            "dateModified": 1490843899,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1788,
+        "type": "USER",
+        "phid": "PHID-USER-e6scsvv2dsyhkfr4glnz",
+        "fields": {
+            "username": "Sylvain_WMFr",
+            "realName": "Sylvain Boissel",
+            "mediawikiUsername": "Sylvain Boissel WMFr",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1422983848,
+            "dateModified": 1446191630,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "Sylvain_WMFr"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1730,
+        "type": "USER",
+        "phid": "PHID-USER-brn4v5ta45bnw4f5as3h",
+        "fields": {
+            "username": "AKoval_WMF",
+            "realName": "Anna Koval",
+            "mediawikiUsername": "AKoval (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1422569469,
+            "dateModified": 1498857479,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "AnnaKoval"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1566,
+        "type": "USER",
+        "phid": "PHID-USER-6vqtwycrvuonr2xo7bqi",
+        "fields": {
+            "username": "BGerstle-WMF",
+            "realName": "Brian Gerstle",
+            "mediawikiUsername": "BGerstle (WMF)",
+            "roles": [
+                "disabled",
+                "approved"
+            ],
+            "dateCreated": 1421198308,
+            "dateModified": 1498861878,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "bgerstle"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1476,
+        "type": "USER",
+        "phid": "PHID-USER-ioc6klbtgwyd2nxdernp",
+        "fields": {
+            "username": "MeganHernandez_WMF",
+            "realName": "Megan Hernandez",
+            "mediawikiUsername": "MeganHernandez (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1420561196,
+            "dateModified": 1735834157,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1383,
+        "type": "USER",
+        "phid": "PHID-USER-lmjxm4d6hgq733p4q5kl",
+        "fields": {
+            "username": "BGibbs_WMF",
+            "realName": "Brett Gibbs",
+            "mediawikiUsername": "Bgibbs (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1419737512,
+            "dateModified": 1456766905,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1180,
+        "type": "USER",
+        "phid": "PHID-USER-w5ff3qutuzf3xbfhb5fv",
+        "fields": {
+            "username": "Shouston_WMF",
+            "realName": "Sati Houston",
+            "mediawikiUsername": "Shouston (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1418318815,
+            "dateModified": 1583686650,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1145,
+        "type": "USER",
+        "phid": "PHID-USER-oodbvkrh2ke6ueevnjxy",
+        "fields": {
+            "username": "JAnstee_WMF",
+            "realName": "Jaime Anstee",
+            "mediawikiUsername": "JAnstee (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1418152182,
+            "dateModified": 1647372583,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 1086,
+        "type": "USER",
+        "phid": "PHID-USER-kl7cb33zrbpidi6jwn7f",
+        "fields": {
+            "username": "Siko",
+            "realName": "Siko (WMF)",
+            "mediawikiUsername": "Siko (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1417817213,
+            "dateModified": 1520443219,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 850,
+        "type": "USER",
+        "phid": "PHID-USER-gk4enxd23ebojohiq7rf",
+        "fields": {
+            "username": "Philippe-WMF",
+            "realName": "Philippe Beaudette",
+            "mediawikiUsername": "Philippe (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1416528736,
+            "dateModified": 1455653596,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 819,
+        "type": "USER",
+        "phid": "PHID-USER-e4jqmosgbh4e43cicihh",
+        "fields": {
+            "username": "MSchottlender-WMF",
+            "realName": "Moriel Schottlender",
+            "mediawikiUsername": "MSchottlender-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1416355417,
+            "dateModified": 1532114240,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 725,
+        "type": "USER",
+        "phid": "PHID-USER-wswkm7jrcwes3tc7o34k",
+        "fields": {
+            "username": "JanWMF",
+            "realName": "Jan Eissfeldt",
+            "mediawikiUsername": "JEissfeldt (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1415370909,
+            "dateModified": 1490687431,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 678,
+        "type": "USER",
+        "phid": "PHID-USER-o2maduzdld3dcurrschj",
+        "fields": {
+            "username": "TFlanagan-WMF",
+            "realName": "Tighe Flanagan",
+            "mediawikiUsername": "TFlanagan-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1414842889,
+            "dateModified": 1525864040,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 656,
+        "type": "USER",
+        "phid": "PHID-USER-uxp3hc4banddtiwz6xrp",
+        "fields": {
+            "username": "CCogdill_WMF",
+            "realName": "Caitlin Cogdill",
+            "mediawikiUsername": "CCogdill (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1414621571,
+            "dateModified": 1605801012,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "ccogdill"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 609,
+        "type": "USER",
+        "phid": "PHID-USER-n2ftvsjm34tosq65gpve",
+        "fields": {
+            "username": "LuisVilla",
+            "realName": "Luis _personal_ - don't use for WMF-sensitive bugs",
+            "mediawikiUsername": "LuisVilla",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1414334637,
+            "dateModified": 1429158483,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 520,
+        "type": "USER",
+        "phid": "PHID-USER-izqileijt5niumtehazh",
+        "fields": {
+            "username": "JKatzWMF",
+            "realName": "Jon Katz",
+            "mediawikiUsername": "Jkatz (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1414099986,
+            "dateModified": 1627372248,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 495,
+        "type": "USER",
+        "phid": "PHID-USER-kqwh3rvfxxh3wfsft7mu",
+        "fields": {
+            "username": "LuisV_WMF",
+            "realName": "Luis Villa",
+            "mediawikiUsername": "LuisV (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1413995642,
+            "dateModified": 1467568710,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 494,
+        "type": "USER",
+        "phid": "PHID-USER-sv2dfl6iqi6362rwe44l",
+        "fields": {
+            "username": "MBrar.WMF",
+            "realName": "Manprit Brar",
+            "mediawikiUsername": "MBrar (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1413995637,
+            "dateModified": 1493228501,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 462,
+        "type": "USER",
+        "phid": "PHID-USER-pfx4qw7xzspc3rwl5kgp",
+        "fields": {
+            "username": "Stype_and_Co.-WMF",
+            "realName": "Chris Steipp",
+            "mediawikiUsername": "Stype & Co. (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1413842805,
+            "dateModified": 1490834228,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 458,
+        "type": "USER",
+        "phid": "PHID-USER-5gog4v3xjj6mq65koqgl",
+        "fields": {
+            "username": "KLans_WMF",
+            "realName": "Kristen Lans",
+            "mediawikiUsername": "KLans (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1413828989,
+            "dateModified": 1632926131,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 416,
+        "type": "USER",
+        "phid": "PHID-USER-j4ifauraw6sytqa3zrih",
+        "fields": {
+            "username": "atgo",
+            "realName": "Anne Gomez (WMF)",
+            "mediawikiUsername": "AGomez (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1413581418,
+            "dateModified": 1568574848,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "atgo, atgomez"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 375,
+        "type": "USER",
+        "phid": "PHID-USER-wodu5sr6tt37sthwshwb",
+        "fields": {
+            "username": "egalvezwmf",
+            "realName": "Edward Galvez",
+            "mediawikiUsername": "EGalvez (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1413421374,
+            "dateModified": 1550366191,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 189,
+        "type": "USER",
+        "phid": "PHID-USER-uf3buojo4ceizjywvyn5",
+        "fields": {
+            "username": "Whatamidoing-WMF",
+            "realName": "Sherry Snyder",
+            "mediawikiUsername": "Whatamidoing (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1412728495,
+            "dateModified": 1704909722,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 186,
+        "type": "USER",
+        "phid": "PHID-USER-edlps6xg553cjlnvd4ao",
+        "fields": {
+            "username": "RobLa-WMF",
+            "realName": "Rob Lanphier",
+            "mediawikiUsername": "RobLa-WMF",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1412720689,
+            "dateModified": 1477697754,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "robla"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 134,
+        "type": "USER",
+        "phid": "PHID-USER-c47vnc2yxmwfvvc4367q",
+        "fields": {
+            "username": "Pginer-WMF",
+            "realName": "Pau Giner",
+            "mediawikiUsername": "Pginer-WMF",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1412666808,
+            "dateModified": 1511863136,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "pginer"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 84,
+        "type": "USER",
+        "phid": "PHID-USER-ydswvwhh5pm4lshahjje",
+        "fields": {
+            "username": "Jdforrester-WMF",
+            "realName": "James D. Forrester",
+            "mediawikiUsername": "Jdforrester (WMF)",
+            "roles": [
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1412633316,
+            "dateModified": 1555109842,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "James_F"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 46,
+        "type": "USER",
+        "phid": "PHID-USER-z3kqk2bjnqneldcznht6",
+        "fields": {
+            "username": "Jaredzimmerman-WMF",
+            "realName": "Jared Zimmerman",
+            "mediawikiUsername": "Jaredzimmerman (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1412358173,
+            "dateModified": 1452283985,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 27,
+        "type": "USER",
+        "phid": "PHID-USER-dw53c5cb2qfhyemej57o",
+        "fields": {
+            "username": "Mattflaschen-WMF",
+            "realName": "Matthew Flaschen",
+            "mediawikiUsername": null,
+            "roles": [
+                "disabled",
+                "approved"
+            ],
+            "dateCreated": 1412310918,
+            "dateModified": 1524058756,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "matt_flaschen"
+        },
+        "attachments": {}
+    },
+    {
+        "id": 14,
+        "type": "USER",
+        "phid": "PHID-USER-wil4b5lylrvf3krixlkl",
+        "fields": {
+            "username": "Elitre",
+            "realName": "Elitre WMF",
+            "mediawikiUsername": "Elitre (WMF)",
+            "roles": [
+                "disabled",
+                "verified",
+                "approved"
+            ],
+            "dateCreated": 1411569691,
+            "dateModified": 1696508781,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": null
+        },
+        "attachments": {}
+    },
+    {
+        "id": 5,
+        "type": "USER",
+        "phid": "PHID-USER-hgn5uw2jafgjgfvxibhh",
+        "fields": {
+            "username": "Aklapper",
+            "realName": "Andre Klapper (WMF)",
+            "mediawikiUsername": "AKlapper (WMF)",
+            "roles": [
+                "admin",
+                "verified",
+                "approved",
+                "activated"
+            ],
+            "dateCreated": 1410977978,
+            "dateModified": 1720981198,
+            "policy": {
+                "view": "public",
+                "edit": "no-one"
+            },
+            "custom.irc_nick": "andre"
+        },
+        "attachments": {}
+    }
+]
\ No newline at end of file
diff --git a/src/helper_scripts/cleaning_scripts/0228_ve_phab_comments.csv b/src/helper_scripts/cleaning_scripts/0228_ve_phab_comments.csv
new file mode 100644
index 0000000..278fc30
--- /dev/null
+++ b/src/helper_scripts/cleaning_scripts/0228_ve_phab_comments.csv
@@ -0,0 +1,192743 @@
+task_title,comment_text,date_created,AuthorPHID,WMFaffil,TaskPHID,comment_type,status
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"When running Echo extensions tests under HHVM/Zend, Jenkins ends up with a failure:
+
+```
+1) EchoTitleLocalCacheTest::testGet
+Failed asserting that null is an instance of class ""Title"".
+
+extensions/Echo/tests/phpunit/includes/cache/TitleLocalCacheTest.php:37
+tests/phpunit/MediaWikiTestCase.php:141
+```
+
+In a workspace with the following extensions:
+
+mediawiki/extensions/Echo
+mediawiki/extensions/JsonConfig
+mediawiki/extensions/Mantle
+mediawiki/extensions/MobileApp
+mediawiki/extensions/MobileFrontend
+mediawiki/extensions/VisualEditor
+mediawiki/extensions/WikiGrok
+mediawiki/extensions/ZeroBanner
+mediawiki/extensions/ZeroPortal
+
+
+Running the Echo tests standalone pass ( php tests/phpunit/phpunit.php extensions/Echo )
+
+The whole testsuite fails though:
+```
+cd tests/phpunit
+php phpunit.php --testsuite extensions
+```
+
+Or slightly faster:
+```
+cd tests/phpunit
+php phpunit.php --testsuite extensions --filter 'Echo' --stop-on-failure
+```",1418676203,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_description,resolved
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,Filed separately as T88039 since that one is not related to HHVM.,1422579129,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,Filed separately as T88039.,1422579113,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Failed again just now:
+
+https://integration.wikimedia.org/ci/job/mwext-Flow-testextension-zend/344/consoleFull",1422575320,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184420 abandoned by Hashar:
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184420]]",1421532092,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184420 had a related patch set uploaded (by Hashar):
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184420]]
+
+#patch-for-review",1421094198,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"I have pushed the fix to 1.25wmf13 and 1.25wmf14 mediawiki/core branches (and ""deployed"").",1421075512,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184344 merged by jenkins-bot:
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184344]]",1421072935,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184343 merged by jenkins-bot:
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184343]]",1421072933,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184344 had a related patch set uploaded (by Hashar):
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184344]]
+
+#patch-for-review",1421072694,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 184343 had a related patch set uploaded (by Hashar):
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/184343]]
+
+#patch-for-review",1421072672,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,Merged in by Matthias \O/,1420817606,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 183840 merged by jenkins-bot:
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/183840]]",1420817440,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"The patch [[ https://gerrit.wikimedia.org/r/183840 | 183840 ]] for Echo does fix the job testing multiple extensions together:
+ 
+https://integration.wikimedia.org/ci/job/mediawiki-phpunit-integration-hhvm/15/console
+
+Pending review/merge.",1420810604,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Change 183840 had a related patch set uploaded (by Hashar):
+Fix EchoTitleLocalCacheTest::testGet corner case
+
+[[https://gerrit.wikimedia.org/r/183840]]
+
+#patch-for-review",1420808267,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Could someone from the #Collaboration-Team assist in tracking down this bug?  I have looked a bit at the cache code and attempted to debug it but eventually got lost in the code :-/
+
+The way to reproduce:
+
+Clone core / vendor and:
+
+mediawiki/extensions/Echo
+mediawiki/extensions/JsonConfig
+mediawiki/extensions/Mantle
+mediawiki/extensions/MobileApp
+mediawiki/extensions/MobileFrontend
+mediawiki/extensions/VisualEditor
+mediawiki/extensions/WikiGrok
+mediawiki/extensions/ZeroBanner
+mediawiki/extensions/ZeroPortal
+
+Setup a basic wiki via maintenance/install.php
+
+```
+cd tests/phpunit
+php phpunit.php --testsuite extensions --filter 'Echo' --stop-on-failure
+```
+
+Should fails.
+
+If one only run the Echo tests they pass ( php tests/phpunit.php extensions/Echo ).
+
+
+
+
+",1420729467,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"I forgot to reopen this task, see above for a way to reproduce.",1420711820,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"Example to reproduce:
+
+```
+cd tests/phpunit
+php phpunit.php --testsuite extensions --filter 'Echo' --stop-on-failure
+```
+
+There must be a race condition somewhere in the MRU Cache or Title local cache.",1420557287,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"The standalone job pass now https://integration.wikimedia.org/ci/job/mwext-Echo-testextension-hhvm/3/  but fails when being run with other extensions https://integration.wikimedia.org/ci/job/mediawiki-phpunit-integration-hhvm/11/console
+
+That last job uses:
+
+mediawiki/extensions/Echo
+mediawiki/extensions/JsonConfig
+mediawiki/extensions/Mantle
+mediawiki/extensions/MobileApp
+mediawiki/extensions/MobileFrontend
+mediawiki/extensions/VisualEditor
+mediawiki/extensions/WikiGrok
+mediawiki/extensions/ZeroBanner
+mediawiki/extensions/ZeroPortal
+
+I can reproduce the failure on my local install using Zend",1420551626,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,I couldn't get MediaWiki-Vagrant to work to reproduce this.,1420495047,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions,"You can trigger the hhvm job on an Echo proposed patch by commenting in Gerrit: ""check experimental"".  That will run a build of https://integration.wikimedia.org/ci/job/mwext-Echo-testextension-hhvm/",1418737731,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vrk66ztqr5wv6qiwliyc,task_subcomment,NA
+VisualEditor has been disabled unexpectedly on fr.wiktionary,"Hi,
+
+Visual Editor has been enabled on fr.wikt after https://phabricator.wikimedia.org/T65187 ; but now it has been disabled, it seems since last night (maybe since the installation of the version 1.25wmf9 of MediaWiki).
+
+Any idea?",1417040370,PHID-USER-76b52mrhaky23u2wzwmg,False,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_description,resolved
+VisualEditor has been disabled unexpectedly on fr.wiktionary,So sorry about this; now fixed.,1417046899,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_subcomment,NA
+VisualEditor has been disabled unexpectedly on fr.wiktionary,"Change 176182 merged by jenkins-bot:
+Followup 313c29f: correct spelling of wiktionary
+
+[[https://gerrit.wikimedia.org/r/176182]]",1417046763,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_subcomment,NA
+VisualEditor has been disabled unexpectedly on fr.wiktionary,"Change 176182 had a related patch set uploaded (by Catrope):
+Followup 313c29f: correct spelling of wiktionary
+
+[[https://gerrit.wikimedia.org/r/176182]]
+
+#patch-for-review",1417046167,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_subcomment,NA
+VisualEditor has been disabled unexpectedly on fr.wiktionary,"Hey, yes, sorry, it looks like we broke this. My apologies; will get it fixed.",1417040870,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ufoo62yyz25ibqfvz7ez,task_subcomment,NA
+VisualEditor does not open at en.wikipedia.beta.wmflabs.org,"- go to http://en.wikipedia.beta.wmflabs.org/
+- log in as Selenium user
+- make sure VisualEditor is enabled at http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences#mw-prefsection-betafeatures
+- go to http://en.wikipedia.beta.wmflabs.org/wiki/Language_Screenshot?veaction=edit
+- VisualEditor never opens
+- the loading bar in the top-right part of the screen just cycles (see screen shot) {F15998}",1416911298,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-j7cnykjnzlc5nu27zqtt,task_description,duplicate
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416275760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hlczvkjyex42kxtfvcdr,task_description,resolved
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified the fix in en.wiki,1417044518,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hlczvkjyex42kxtfvcdr,task_subcomment,NA
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified the fix in Betalabs and test2,1416275919,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hlczvkjyex42kxtfvcdr,task_subcomment,NA
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Fixed by 
+
+Followup ca6a16f: use parent selector both for hiding and showing windows
+
+https://gerrit.wikimedia.org/r/173977",1416275894,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hlczvkjyex42kxtfvcdr,task_subcomment,NA
+VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"From Ritu Swain:
+
+Reopen this issue.
+In test2 and beta only.
+
+steps-
+
+1> open the link/math/comment/special characters/ inspectors in Media Settings -> caption sub-editor or the References sub-editor. The inspectors are blank with no UI.
+
+Also see Bug 68130 https://bugzilla.wikimedia.org/show_bug.cgi?id=68130.",1416275852,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hlczvkjyex42kxtfvcdr,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"see e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Links_VisualEditor_Test?vehidebetadialog=true&veaction=edit
+
+see screen shot for error
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1415899860,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-6stmkadongdngovinrsy,task_description,resolved
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,I'm not sure why OCG broke or what that is but this would have been noticed if things ran tests for extensions that depended on them. In this case MobileFrontend should run qunit and phpunit tests for zero and Mantle should run qunit and phpunit on Flow and MobileFrontend,1415931146,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,*** Bug 73375 has been marked as a duplicate of this bug. ***,1415921818,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Please correct me if I am wrong:
+
+The change https://gerrit.wikimedia.org/r/#/c/168233/ to Mantle removed a bunch of javascript which turned out to be used by several other extensions (ZeroBanner and OCG at least).
+
+I guess running the qunit tests of ZeroBanner and OCG with that Mantle patch applied would have caught the issue. If someone has some spare time to verify that it would be rather nice.
+
+From there, I am willing to have a generic qunit job that will tests together all extensions having qunit jobs. This way if Mantle change something, the other extensions would complain.  Does that sounds like a good idea?",1415917656,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Beta labs is working again. Thanks Jon and Jeff.
+
+No need to add anything to anything because merged changes are deployed to beta labs automatically.",1415911888,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,(it's going to be easier to update Zero than Mantle and all its dependencies),1415911758,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,Greg does the patch solve the issue? Can we just add to the build?,1415911638,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"To be clear:
+This is breaking A LOT OF THINGS, pretty much all browser tests are failing all day due to bits not responding.
+
+Jon/Jeff: Can you just revert the change ASAP? The ""build is broken"" as it were, we can't leave it broken all day.",1415910756,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"This is breaking the OCG progress bar in beta as well.
+
+I'm assuming/hoping that Top Men are hard are work on this, and the bug won't survive into production?",1415910491,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Change 173069 merged by jenkins-bot:
+Use templates in core to avoid fatals
+
+https://gerrit.wikimedia.org/r/173069",1415909747,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Change 173069 had a related patch set uploaded by Jdlrobson:
+Use templates in core to avoid fatals
+
+https://gerrit.wikimedia.org/r/173069",1415906602,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,Jeff Hobson and I will work to get this fixed asap.,1415905615,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,This looks like it is coming from Zero. I didn't realise they were using this class. I had thought the deprecation warning had been running for long enough to remove it. Will chat to Adam.,1415905390,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/9dGlL33Y",1415903714,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,(Not a Beta Cluster bug),1415903685,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,This commit <https://gerrit.wikimedia.org/r/#/c/168233/> is breaking ZeroBanner <https://github.com/wikimedia/mediawiki-extensions-ZeroBanner/commit/c930255ed39ef11288d5e9e079fa5cd5837675b6>,1415903511,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Nov 13 18:22:44 deployment-mediawiki01 hhvm: #012Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506
+Nov 13 18:22:44 deployment-mediawiki01 hhvm: {#012    ""message"": ""Class undefined: ResourceLoaderTemplateModule"",#012    ""file"": ""/srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php"",#012    ""line"": 506,#012    ""context"": [],#012    ""backtrace"": [#012        {#012            ""file"": ""/srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php"",#012            ""line"": 506#012        },#012        {#012            ""file"": ""/srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php"",#012            ""line"": 111,#012            ""function"": ""getModule"",#012            ""class"": ""ResourceLoader"",#012            ""type"": ""->"",#012            ""args"": [#012                ""zerobanner""#012            ]#012        },#012        {#012            ""file"": ""/srv/mediawiki/php-master/includes/resourceloader/ResourceLoaderStartUpModule.php"",#012            ""line"": 438,#012            ""function"": ""preloadModuleInfo"",#012            ""class"": ""ResourceLoader"",#012            ""type"": ""->"",#012            ""args"": [#012                [#012                    ""site"",#012                    ""noscript"",#012                    ""startup"",#012                    ""filepage"",#012                    ""user.groups"",#012                    ""user"",#012                    ""user.cssprefs"",#012                    ""user.options"",#012                    ""user.tokens"",#012                    ""mediawiki.language.data"",#012                    ""mediawiki.skinning.elements"",#012                    ""mediawiki.skinning.content"",#012                    ""mediawiki.skinning.interface"",#012                    ""mediawiki.skinning.content.parsoid"",#012                    ""mediawiki.skinning.content.externallinks"",#012                    ""jquery"",#012                    ""jquery.accessKeyLabel"",#012                    ""jquery.appear"",#012                    ""jquery.arrowSteps"",#012                    ""jquery.async"",#012                    ""jquery.autoEllipsis"",#012                    ""jquery.badge"",#012                    ""jquery.byteLength"",#012                    ""jquery.byteLimit"",#012                    ""jquery.checkboxShiftClick"",#012                    ""jquery.chosen"",#012                    ""jquery.client"",#012                    ""jquery.color"",#012                    ""jquery.colorUtil"",#012                    ""jquery.confirmable"",#012                    ""jquery.cookie"",#012                    ""jquery.expandableField"",#012                    ""jquery.farbtastic"",#012                    ""jquery.footHovzer"",#012                    ""jquery.form"",#012                    ""jquery.fullscreen"",#012                    ""jquery.getAttrs"",#012                    ""jquery.hidpi"",#012                    ""jquery.highlightText"",#012                    ""jquery.hoverIntent"",#012                    ""jquery.localize"",#012                    ""jquery.makeCollapsible"",#012                    ""jquery.mockjax"",#012                    ""jquery.mw-jump"",#012                    ""jquery.mwExtension"",#012                    ""jquery.placeholder"",#012                    ""jquery.qunit"",#012                    ""jquery.qunit.completenessTest"",#012                    ""jquery.spinner"",#012                    ""jquery.jStorage"",#012                    ""jquery.suggestions"",#012                    ""jquery.tabIndex"",#012                    ""jquery.tablesorter"",#012                    ""jquery.textSelection"",#012                    ""jquery.throttle-debounce"",#012                    ""jquery.validate"",#012                    ""jquery.xmldom"",#012                    ""jquery.tipsy"",#012                    ""jquery.ui.core"",#012                    ""jquery.ui.accordion"",#012                    ""jquery.ui.autocomplete"",#012                    ""jquery.ui.button"",#012                    ""jquery.ui.datepicker"",#012                    ""jquery.ui.dialog"",#012                    ""jquery.ui.draggable"",#012                    ""jquery.ui.droppable"",#012                    ""jquery.ui.menu"",#012                    ""jquery.ui.mouse"",#012                    ""jquery.ui.position"",#012                    ""jquery.ui.progressbar"",#012                    ""jquery.ui.resizable"",#012                    ""jquery.ui.selectable"",#012                    ""jquery.ui.slider"",#012                    ""jquery.ui.sortable"",#012                    ""jquery.ui.spinner"",#012                    ""jquery.ui.tabs"",#012                    ""jquery.ui.tooltip"",#012                    ""jquery.ui.widget"",#012                    ""jquery.effects.core"",#012                    ""jquery.effects.blind"",#012                    ""jquery.effects.bounce"",#012                    ""jquery.effects.clip"",#012                    ""jquery.effects.drop"",#012                    ""jquery.effects.explode"",#012                    ""jquery.effects.fade"",#012                    ""jquery.effects.fold"",#012                    ""jquery.effects.highlight"",#012                    ""jquery.effects.pulsate"",#012                    ""jquery.effects.scale"",#012                    ""jquery.effects.shake"",#012                    ""jquery.effects.slide"",#012                    ""jquery.effects.transfer"",#012                    ""json"",#012                    ""moment"",#012                    ""mediawiki"",#012                    ""mediawiki.apihelp"",#012                    ""mediawiki.template"",#012                    ""mediawiki.apipretty"",#012                    ""mediawiki.api"",#012                    ""mediawiki.api.category"",#012                    ""mediawiki.api.edit"",#012                    ""mediawiki.api.login"",#012                    ""mediawiki.api.parse"",#012                    ""mediawiki.api.watch"",#012                    ""mediawiki.content.json"",#012                    ""mediawiki.confirmCloseWindow"",#012                    ""mediawiki.debug"",#012                    ""mediawiki.debug.init"",#012                    ""mediawiki.feedback"",#012                    ""mediawiki.hidpi"",#012                    ""mediawiki.hlist"",#012                    ""mediawiki.htmlform"",#012                    ""mediawiki.icon"",#012                    ""mediawiki.inspect"",#012                    ""mediawiki.notification"",#012                    ""mediawiki.notify"",#012                    ""mediawiki.pager.tablePager"",#012                    ""mediawiki.searchSuggest"",#012                    ""mediawiki.Title"",#012                    ""mediawiki.toc"",#012                    ""mediawiki.Uri"",#012                    ""mediawiki.user"",#012                    ""mediawiki.userSuggest"",#012                    ""mediawiki.util"",#012                    ""mediawiki.cookie"",#012                    ""mediawiki.toolbar"",#012                    ""mediawiki.action.edit"",#012                    ""mediawiki.action.edit.styles"",#012                    ""mediawiki.action.edit.collapsibleFooter"",#012                    ""mediawiki.action.edit.preview"",#012                    ""mediawiki.action.history"",#012                    ""mediawiki.action.history.diff"",#012                    ""mediawiki.action.view.dblClickEdit"",#012                    ""mediawiki.action.view.metadata"",#012                    ""mediawiki.action.view.postEdit"",#012                    ""mediawiki.action.view.redirect"",#012                    ""mediawiki.action.view.redirectPage"",#012                    ""mediawiki.action.view.rightClickEdit"",#012                    ""mediawiki.action.edit.editWarning"",#012                    ""mediawiki.language"",#012                    ""mediawiki.cldr"",#012                    ""mediawiki.libs.pluralruleparser"",#012                    ""mediawiki.language.init"",#012                    ""mediawiki.jqueryMsg"",#012                    ""mediawiki.language.months"",#012                    ""mediawiki.language.names"",#012                    ""mediawiki.libs.jpegmeta"",#012                    ""mediawiki.page.gallery"",#012                    ""mediawiki.page.ready"",#012                    ""mediawiki.page.startup"",#012                    ""mediawiki.page.patrol.ajax"",#012                    ""mediawiki.page.watch.ajax"",#012                    ""mediawiki.page.image.pagination"",#012                    ""mediawik",1415903021,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,Failed to load resource: the server responded with a status of 503 (Service Unavailable) http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*,1415900551,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"As visible in the first line of your screenshot, there's a load.php request that's 503ing. For me, it's an earlier load.php request that 503s (the startup request), and so I don't get the error, but no JavaScript works.
+
+Is beta labs broken again?",1415900104,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506,"Created attachment 17121
+Reference error
+
+**Attached**: {F15211}",1415899926,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-6stmkadongdngovinrsy,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","screenshot
+
+""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker
+
+**Attached**: {F15023}",1415213160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_description,resolved
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",Verified the fix in production,1416446814,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 172440 abandoned by Catrope:
+Followup d4c133b: also make TargetEvents depend on ve.track()
+
+Reason:
+Sorry, this was not a wmf7 regression, so this should not be cherry-picked
+
+https://gerrit.wikimedia.org/r/172440",1415663293,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 172440 had a related patch set uploaded by Catrope:
+Followup d4c133b: also make TargetEvents depend on ve.track()
+
+https://gerrit.wikimedia.org/r/172440",1415663118,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 172431 merged by jenkins-bot:
+Followup d4c133b: also make TargetEvents depend on ve.track()
+
+https://gerrit.wikimedia.org/r/172431",1415662611,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 172431 had a related patch set uploaded by Catrope:
+Followup d4c133b: also make TargetEvents depend on ve.track()
+
+https://gerrit.wikimedia.org/r/172431",1415660295,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",latest failures is https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/322/testReport/junit/(root)/VisualEditor%20Mobile/Switch_from_VisualEditor_to_source_editor/,1415660157,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","new js error from logged in user e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Sextet#/editor/0 is 
+
+Uncaught TypeError: undefined is not a function VM156:850ve.init.mw.TargetEvents.track VM156:850(anonymous function) VM156:840(anonymous function) load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:46fire load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:44self.fireWith load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:46done load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:135callback load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T…:141",1415659958,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",Verified the fix in test2,1415227876,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",Verified the fix in Betalabs,1415218406,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 171306 merged by jenkins-bot:
+Follow-up 07251d0: Add mobile target to RangeFix
+
+https://gerrit.wikimedia.org/r/171306",1415214648,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE","**gerritadmin** wrote:
+
+Change 171306 had a related patch set uploaded by Catrope:
+Followup 07251d0: add mobile target to rangefix
+
+https://gerrit.wikimedia.org/r/171306",1415214210,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf8] ""Uncaught Error: Unknown dependency: rangefix""  appears while trying to load mobile VE",*** Bug 73039 has been marked as a duplicate of this bug. ***,1415213710,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2oau4k2rwhb4lnhnwgl5,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"Can't work out why; supportedSelections is set for both.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1415152200,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nohpzqcpzjmuxbicpotc,task_description,resolved
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"Verified the fix in Betalabs,test2 and production.",1415657798,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),Fix now live in production.,1415233236,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"**gerritadmin** wrote:
+
+Change 171451 merged by jenkins-bot:
+Followup 31bafa1: forgot to rename 'data' to 'args' for citation commands
+
+https://gerrit.wikimedia.org/r/171451",1415232673,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"**gerritadmin** wrote:
+
+Change 171451 had a related patch set uploaded by Jforrester:
+Followup 31bafa1: forgot to rename 'data' to 'args' for citation commands
+
+https://gerrit.wikimedia.org/r/171451",1415224619,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"**gerritadmin** wrote:
+
+Change 171447 merged by jenkins-bot:
+Followup 31bafa1: forgot to rename 'data' to 'args' for citation commands
+
+https://gerrit.wikimedia.org/r/171447",1415224584,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does),"**gerritadmin** wrote:
+
+Change 171447 had a related patch set uploaded by Catrope:
+Followup 31bafa1: forgot to rename 'data' to 'args' for citation commands
+
+https://gerrit.wikimedia.org/r/171447",1415224131,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nohpzqcpzjmuxbicpotc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,"Steps to reproduce:
+
+1.Insert any template in the page
+
+Observed Result:
+VE gets completely unresponsive after this action,Cannot make any other change or save the page. No error in the console.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1415127300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k34jgliglfher6oyvsj3,task_description,resolved
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,Verified the fix in production,1415834025,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,Verified the fix in test2,1415228528,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,Verified the fix in Betalabs,1415128541,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,"**gerritadmin** wrote:
+
+Change 170991 merged by jenkins-bot:
+Followup 0165a53: don't store an mw.Title object instead of a string in TemplateModel
+
+https://gerrit.wikimedia.org/r/170991",1415127764,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template,"**gerritadmin** wrote:
+
+Change 170991 had a related patch set uploaded by Catrope:
+Followup 0165a53: don't store an mw.Title object instead of a string in TemplateModel
+
+https://gerrit.wikimedia.org/r/170991",1415127629,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k34jgliglfher6oyvsj3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","On any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click Cite/Website or any other Cite selection. 
+
+Nothing happens. No Cite inspector appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415111400,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-s4icej2snebqglex3pcn,task_description,resolved
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined """,The fix is re-verified in betalabs and test2.,1415234910,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined """,Opening a distinct bug for that one.,1415151534,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined """,This started happening again? Although not for basic reference but for citations and no error in console this time,1415147217,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","Verified in betalabs  - Safari, Chrome, and FF.",1415128323,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","**gerritadmin** wrote:
+
+Change 170985 merged by jenkins-bot:
+Followup 0165a53: fix typo causing undefined to be passed to mw.Title
+
+https://gerrit.wikimedia.org/r/170985",1415127378,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","**gerritadmin** wrote:
+
+Change 170985 had a related patch set uploaded by Catrope:
+Followup 0165a53: fix typo causing undefined to be passed to mw.Title
+
+https://gerrit.wikimedia.org/r/170985",1415127276,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror "" Cannot read property 'replace' of undefined ""","js error is ""TypeError: title is undefined""",1415112905,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-s4icej2snebqglex3pcn,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a template for example: Cite Web/Citation needed
+3.Save the page
+4.Reopen the page
+5.Reopen the Transclusion dialog for the template you just added
+
+Observed Result:
+Instead of the template dialog with all the parameters in it , it appears as an empty ""Add Template"" dialog 
+
+See the screenshot attached
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14841}",1414622880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,Verified the fix in production,1415834079,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,Verified the fix in test2,1415228454,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,Verified the fix in Betalabs,1414703204,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page,Fixed by: https://gerrit.wikimedia.org/r/169966,1414703188,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bfjwz5ljcpfpztnowj4p,task_subcomment,NA
+VisualEditor: Clicking in a table that contains templated rows causes JS error,"1. Go to http://en.wikipedia.beta.wmflabs.org/wiki/User:RoanKattouw/Evil_table?veaction=edit
+2. Click on a non-templated cell in the table (e.g. the cell that says ""simple"" in row 2)
+3. ""undefined is not a function"" error appears in console
+
+What happens is that TableMatrix#update runs, and when it hits cell (2,0) (3rd row, 1st column), it will find that cellNode is a ve.dm.MWTransclusionNode rather than a ve.dm.TableCellNode, and so calling .getRowSpan() on it will explode.
+
+We probably need some way to deal with templated rows/cells in the middle of an otherwise normal table, but I'm not entirely sure what that should look like. Maybe we can get away with skipping over these rows/cells everywhere in a consistent manner, and hopefully that will work out OK?
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1414622340,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dnykg7zlhhhsxuhitddq,task_description,resolved
+VisualEditor: Clicking in a table that contains templated rows causes JS error,Verified with the Evil_table given in the link - the js error is not displayed anymore.,1415234703,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-dnykg7zlhhhsxuhitddq,task_subcomment,NA
+VisualEditor: Clicking in a table that contains templated rows causes JS error,"**gerritadmin** wrote:
+
+Change 170245 merged by jenkins-bot:
+Add support for non-table nodes in tables (e.g. aliens)
+
+https://gerrit.wikimedia.org/r/170245",1415041463,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dnykg7zlhhhsxuhitddq,task_subcomment,NA
+VisualEditor: Clicking in a table that contains templated rows causes JS error,"**gerritadmin** wrote:
+
+Change 170245 had a related patch set uploaded by Esanders:
+Add support for non-table nodes in tables (e.g. aliens)
+
+https://gerrit.wikimedia.org/r/170245",1414710274,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dnykg7zlhhhsxuhitddq,task_subcomment,NA
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,"Steps to reproduce:
+
+* Open https://en.wikipedia.org/wiki/Snowman?veaction=edit
+
+* Mark the sentence ""It was 113 feet 7 inches (34.62 m) tall and weighed over 9,000,000 pounds (4,080,000 kg).[1]"" and cut it (Strg+X).
+
+* Paste it in again (Strg+V).
+
+* Click before ""It"" to place the cursor at the beginning of the sentence.
+
+
+Result: The editor starts adding copies of the sentence in an endless loop, with the templates (see below) replaced by snowmen:
+
+""It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ...""
+
+(Actually, if one scrolls or clicks somewhere in the page, the loop may stop, but I've observed it going on for more than a minute, generating 378 copies of the sentence.)
+
+
+Here is the wikitext source of the sentence:
+
+""It was {{convert|113|ft|7|in|m}} tall and weighed over {{convert|9000000|lb|kg|-4}}.<ref>{{cite web|url=http://www.sundayriveron-line.com/AngusSnowman_1.htm|title=Angus, King of the Mountain &mdash; World's Largest Snowman|date=February 19, 1999|publisher=Sunday River On-Line|archiveurl=http://web.archive.org/web/20071012082219/http://www.sundayriveron-line.com/AngusSnowman_1.htm|archivedate=2007-10-12}}</ref>""
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1414245600,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-kghawjstykvx6zxoqfju,task_description,resolved
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,Checked in betalabs and test2 - seems to be fixed.,1415059620,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-kghawjstykvx6zxoqfju,task_subcomment,NA
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,*** Bug 72491 has been marked as a duplicate of this bug. ***,1414692988,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kghawjstykvx6zxoqfju,task_subcomment,NA
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,"Yeah, sorry for this; fixed and back-ported on Monday. :-(",1414625279,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kghawjstykvx6zxoqfju,task_subcomment,NA
+VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop,"PS: Observed in Chromium 37 (no extensions) under Ubuntu both while logged in and while logged out. Under Firefox I can't even get the cutting (step 2) to work, which appears to be a separate bug.",1414246140,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-kghawjstykvx6zxoqfju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,"screenshot
+
+Environment- beta
+
+1> click on Cite and pick any citation(book/web/news/journal).E.g- select cite -> book. Cite book dialog opens.
+2> JS console error “Uncaught TypeError: undefined is not a function”.
+3> Click to Add more information and error in console is “Uncaught TypeError: Cannot read property 'on' of undefined”. See screenshot.
+4> Clicking on cancel or insert does not close the dialog.
+
+Screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14994}",1413212460,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-h5qveiikflwo46ebtb77,task_description,resolved
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,Verified the fix in production,1414101056,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,Verified the fix on test2,1413575893,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,Verified the fix in Betalabs,1413392288,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,"Change 166628 merged by jenkins-bot:
+Followup 1fc13cc: fix JS errors caused by incorrect context binding
+
+https://gerrit.wikimedia.org/r/166628",1413318986,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens,"Change 166628 had a related patch set uploaded by Catrope:
+Followup 1fc13cc: fix JS errors caused by incorrect context binding
+
+https://gerrit.wikimedia.org/r/166628",1413314878,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5qveiikflwo46ebtb77,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select any focusable node: citation note,math ,template or image
+
+Observed Result:
+
+The following error appears in the console:
+NS_ERROR_FAILURE: 
+
+The context menu for that focusable note is still active in CE ,if you select some other focusable note after this, no context menu appears for it or the one for previous node appears on top of it
+
+Environment:test2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15335}",1412290980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fjl7kogsfw35mh64piys,task_description,resolved
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes",Verified the fix in production,1413503136,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes",Verified the backport in test2,1412805362,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes",Verified the fix in Betalabs,1412708406,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Change 164593 merged by jenkins-bot:
+Revert ""ve.ce.Surface: Magic workaround for broken Firefox cursoring""
+
+https://gerrit.wikimedia.org/r/164593",1412358925,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Change 164548 merged by jenkins-bot:
+Revert ""ve.ce.Surface: Magic workaround for broken Firefox cursoring""
+
+https://gerrit.wikimedia.org/r/164548",1412358831,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Change 164593 had a related patch set uploaded by Jforrester:
+Revert ""ve.ce.Surface: Magic workaround for broken Firefox cursoring""
+
+https://gerrit.wikimedia.org/r/164593",1412358796,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Change 164548 had a related patch set uploaded by Bartosz Dziewoński:
+Revert ""ve.ce.Surface: Magic workaround for broken Firefox cursoring""
+
+https://gerrit.wikimedia.org/r/164548",1412342794,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes","Caused by 0d7eaf51767c4061b478610a035a3bc387c0973a (workaround for bug 70724 about broken Firefox cursoring). Calling .collapseToStart() sometimes fixes the selection, and sometimes causes this cryptic exception.
+
+This looks very ugly and very internal, so I'm just going to revert the patch and update the upstream bug report.",1412342724,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"VisualEditor: [Regression wmf2] Deleting any focusable node throws ""error:NS_ERROR_FAILURE:"" in Firefox and wrong context menu starts appearing for other nodes",Reproducible in standalone with comment nodes too.,1412342100,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-fjl7kogsfw35mh64piys,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Jobs running on Ubuntu Trusty for repositories with submodules are currently broken due to a bug in the Jenkins GIT Plugin.
+
+We use Jenkins GIT Plugin 1.5.0, which uses git-client-plugin 1.0.6:
+https://github.com/jenkinsci/git-client-plugin/blob/git-client-1.0.6/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L401-L412
+
+        args.add(""submodule"", ""foreach"");
+        if (recursive) {
+            args.add(""--recursive"");
+        }
+        args.add(""git reset"");
+        if (hard) {
+            args.add(""--hard"");
+        }
+
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/4684/console
+
+
+Cleaning workspace
+Resetting working tree
+FATAL: Command ""submodule foreach --recursive git reset --hard"" returned status code 1:
+stdout: Entering 'lib/ve'
+stderr: /usr/lib/git-core/git-submodule: 552: /usr/lib/git-core/git-submodule: git reset: not found
+Stopping at 'lib/ve'; script returned non-zero status.
+
+Trying to reproduce:
+
+jenkins-deploy@integration-slave1007:/mnt/jenkins-workspace/workspace/mwext-VisualEditor-npm$ git submodule foreach --recursive git reset --hard
+> works fine
+
+The version of git on Ubunty and Precise both support this command.
+The problem lies in the quoting and separation of the arguments.
+
+jenkins-deploy@integration-slave1007:/mnt/jenkins-workspace/workspace/mwext-VisualEditor-npm$ git submodule foreach --recursive 'git reset' --hard
+> /usr/lib/git-core/git-submodule: 552: /usr/lib/git-core/git-submodule: git reset: not found
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: critical",1412198400,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_description,resolved
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")",Plugin bumped to upstream 1.7.1,1432822495,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Apparently this is fixed upstream with: https://github.com/jenkinsci/git-client-plugin/commit/f75720d5de9d79ab4be2633a21de23b3ccbf8ce3  which was shipped with version 1.6.4
+
+```
+lang=diff
+-        args.add(""git reset"");
+-        if (hard) {
+-            args.add(""--hard"");
+-        }
++        args.add(""git reset"" + (hard ? "" --hard"" : """"));
+```
+
+Thus the whole command is passed as a single string.
+
+
+Will switch from our fork/patched version to upstream one as part of T100655
+",1432820455,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Apparently this is fixed upstream with: https://github.com/jenkinsci/git-client-plugin/commit/f75720d5de9d79ab4be2633a21de23b3ccbf8ce3  which was shipped with version 1.6.4
+
+```
+lang=diff
+-        args.add(""git reset"");
+-        if (hard) {
+-            args.add(""--hard"");
+-        }
++        args.add(""git reset"" + (hard ? "" --hard"" : """"));
+```
+
+Thus the whole command is passed as a single string.
+",1432820109,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Thank you Timo!
+
+I testing out with the job that shown the issue yesterday: https://integration.wikimedia.org/ci/job/pywikibot-core-tox-nose34-trusty/
+
+Test case:
+* Precise fresh workspace > OK
+* Precise, rebuild on existing workspace > OK
+* Trusty fresh workspace > OK
+* Trusty, rebuild on existing workspace > OK",1412237886,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","https://wikitech.wikimedia.org/wiki/Nova_Resource:Integration/Jenkins_Plugin
+
+Deployed the .jpi file to Jenkins.",1412204994,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","(In reply to Krinkle from comment #0)
+> Jobs running on Ubuntu Trusty for repositories with submodules are currently
+> broken due to a bug in the Jenkins GIT Plugin.
+> 
+> We use Jenkins GIT Plugin 1.5.0, which uses git-client-plugin 1.0.6:
+> 
+
+Actually, we while GIT Plugin requires git-client-plugin v1.0.5, we currently use git-client-plugin v1.4.6
+
+--
+
+https://github.com/wikimedia/git-client-plugin/commits/git-client-1.4.6%2Bwmf1
+https://github.com/wikimedia/git-client-plugin/commit/5d4c940519352a0a38038154f8c9690a7a5dba58#diff-4a13310f7c84a9d6e133def48c0aed5aR558",1412199962,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Created attachment 16643
+IRC log of a diagnostic on #pywikibot earlier (time is UTC+2)
+
+For what it is worth, attached is an IRC log from earlier today on #pywikibot.  That resulted in the previous attachment showing the 'git reset' not found issue.
+
+**Attached**: {F15207}",1412199778,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Created attachment 16642
+git submodule with GIT_TRACE=1
+
+I found that bug while testing a job for pywikibot/core.git which needs to be run on Trusty (it uses python3.4 which is not on Precise). It yielded:
+
+ /usr/lib/git-core/git-submodule: 552: /usr/lib/git-core/git-submodule: git reset: not found
+
+I have added to the job a parameter GIT_TRACE=1 and ran it again (see attached console output for https://integration.wikimedia.org/ci/job/pywikibot-core-tox-nose34-trusty/9/console ).  The git command shown:
+
+ stderr: trace: exec: 'git-submodule' 'foreach' '--recursive' 'git reset' '--hard'
+
+
+Note how git reset is enclosed in quote.  Since git version 1.9.0, that is passed as a single argument to git-submodule which can find such executable 'git reset'.
+
+I eventually had an audio call and had to be back home.   The Jenkins git-client-plugin needs to be patched to split 'git reset' to be two args, then compiled via maven and uploaded to Jenkins.
+
+You can take backup of the existing version by looking on gallium under /var/lib/jenkins/plugins/ for some .jpi files.
+
+
+Note: last time I have upgraded the Jenkins git plugin,  the whole CI setup went mad :-/  I gave up investigating the java code change and just stuck to the version we currently have.
+
+**Attached**: {F15206}",1412199342,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"Jenkins: The GIT Plugin is broken for submodules (""git-submodule: git reset: not found"")","Release notes of git 1.9 detailing this change in git-submodule semantics:
+ https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/1.9.0.txt
+
+Basically, it used to interpret the argument as a long string (similar to ssh), and letting bash separate the command and arguments. And it now does this at the git level.",1412199080,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-htn6d4t4wffqwtpyga74,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","screenshot
+
+Environment-test2
+
+1> In a blank page, insert a comment.
+2> open edit comment dialog. While the dialog is still open and cursor is blinking inside it, select any of the font styles except Language. For ex- select Bold or Italic.
+
+JS console error is -:
+
+“Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node”
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F14867}",1412007720,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_description,resolved
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment",Verified the fix in production,1412889048,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","(In reply to Ritu Swain from comment #6)
+> Issue resolved in test2, but can be reproduced in beta.
+
+Issue fixed in beta as well.",1412276069,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Issue resolved in test2, but can be reproduced in beta.",1412088735,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Change 163656 merged by Catrope:
+Followup a618491: fix JS errors when slugging near annotated inline nodes
+
+https://gerrit.wikimedia.org/r/163656",1412028314,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Change 163656 had a related patch set uploaded by Jforrester:
+Followup a618491: fix JS errors when slugging near annotated inline nodes
+
+https://gerrit.wikimedia.org/r/163656",1412020258,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Change 163636 merged by jenkins-bot:
+Followup a618491: fix JS errors when slugging near annotated inline nodes
+
+https://gerrit.wikimedia.org/r/163636",1412020222,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment","Change 163636 had a related patch set uploaded by Catrope:
+Followup a618491: fix JS errors when slugging near annotated inline nodes
+
+https://gerrit.wikimedia.org/r/163636",1412015281,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+"VisualEditor: [Regression wmf1] ""Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': .."" while inserting a comment",This bug also causes VE to throw errors when loading on pages like http://www.mediawiki.org/wiki/Parsoid/Deployments?debug=true&veaction=edit . This bug happens when an annotated inline node appears at the start of a paragraph.,1412014301,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pcjfp7itxwp6ka5s4r5q,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"Cannot open comment box in Betalabs. Throwing the following error in the console:
+Uncaught TypeError: Cannot read property '0' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411584480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,Verified the fix in production,1412283385,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,Verified the fix in test2,1411684683,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,Verified the fix in Betalabs,1411591138,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"**gerritadmin** wrote:
+
+Change 162647 merged by jenkins-bot:
+Update VE core submodule to master (6e68242)
+
+https://gerrit.wikimedia.org/r/162647",1411586687,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"**gerritadmin** wrote:
+
+Change 162647 had a related patch set uploaded by Catrope:
+Update VE core submodule to master (6e68242)
+
+https://gerrit.wikimedia.org/r/162647",1411586349,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"**gerritadmin** wrote:
+
+Change 162671 merged by jenkins-bot:
+Account for WhitespacePreservingTextInputWidget#getValue being called early
+
+https://gerrit.wikimedia.org/r/162671",1411585983,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs,"**gerritadmin** wrote:
+
+Change 162671 had a related patch set uploaded by Catrope:
+Account for WhitespacePreservingTextInputWidget#getValue being called early
+
+https://gerrit.wikimedia.org/r/162671",1411584596,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rh6lcdzaiwcz3kmrclju,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"Edit any page on beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click the Link button. Nothing happens.
+
+Error console shows ""TypeError: this.isValid(...).done is not a function""
+
+No other controls seem to be affected by this issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1411574820,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Link button does nothing,Verified the fix in production,1412283348,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,verified the fix in test2,1411684768,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,Verified the fix in Betalabs,1411591061,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"**gerritadmin** wrote:
+
+Change 162647 merged by jenkins-bot:
+Update VE core submodule to master (6e68242)
+
+https://gerrit.wikimedia.org/r/162647",1411586684,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"**gerritadmin** wrote:
+
+Change 162646 merged by jenkins-bot:
+Account for isValid() becoming async
+
+https://gerrit.wikimedia.org/r/162646",1411585729,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"**gerritadmin** wrote:
+
+Change 162647 had a related patch set uploaded by Catrope:
+Make MWLinkTargetInputWidget#isValid asynchronous
+
+https://gerrit.wikimedia.org/r/162647",1411584675,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Link button does nothing,"**gerritadmin** wrote:
+
+Change 162646 had a related patch set uploaded by Catrope:
+Account for isValid() becoming async
+
+https://gerrit.wikimedia.org/r/162646",1411584614,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-r4bsfhr5vzw7cgtwuw7z,task_subcomment,NA
+VisualEditor: Saving replaces categories with [[MediaWiki:Badtitletext]],"http://de.wikipedia.org/w/index.php?diff=134089498
+http://de.wikipedia.org/w/index.php?diff=134090414
+
+VisualEditor is replacing categories in articles with ""[[MediaWiki:Badtitletext]]"". Please fix it as soon as possible or deactivate VE. We do not have any time or desire to check and correct hundreds of revisions caused by broken software.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1410893460,PHID-USER-vvufz7opk2hhimdzyznx,False,PHID-TASK-3t7mpi32hxkzdcilczeh,task_description,resolved
+VisualEditor: Saving replaces categories with [[MediaWiki:Badtitletext]],This is caused by bug 70894; we have made an emergency modification to VE which should stop this recurring for now whilst we fix the problem. Sorry for the disruption.,1410895179,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3t7mpi32hxkzdcilczeh,task_subcomment,NA
+VisualEditor: Saving replaces categories with [[MediaWiki:Badtitletext]],"some other occurences:
+[1] http://de.wikipedia.org/w/index.php?diff=134086405
+[2] http://de.wikipedia.org/w/index.php?diff=134086148
+[3] http://de.wikipedia.org/w/index.php?diff=134085483
+[4] http://de.wikipedia.org/w/index.php?diff=134085429
+
+in [2], there is also some garbage added to an image invocation.",1410895070,PHID-USER-vvufz7opk2hhimdzyznx,False,PHID-TASK-3t7mpi32hxkzdcilczeh,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"When you edit a page with VE in IE, CSS styles are normalized, causing dirty diffs. This is because Internet Explorer very aggressively normalizes styles, to the point where we can't tell what the original value was without some nasty hackery.
+
+In practice, this means that any time you save a page in IE, things like style=""color: #ffffdd;"" get normalized to style=""color: rgb(255, 255, 221);"", bgcolor=""#FFFFDD"" gets normalized to bgcolor=""#ffffdd"" and invalid CSS is removed. The former two are annoying dirty diffs, the latter is actual information loss (someone else can come along later and fix invalid CSS, but not if we remove it).
+
+This normalization is a bug in Internet Explorer. I'm working on a workaround where I extract the original value using an XML parser and stash it so I can restore it later.
+
+hex to rgb normalization: https://fr.wikipedia.org/?diff=107359735
+bgcolor normalization: https://sv.wikipedia.org/?diff=27502354
+Invalid CSS removal: https://cs.wikipedia.org/?diff=11849661
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1410805080,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-b56uk34hrwocyqm77dht,task_description,resolved
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,Deploy scheduled for 08:00 SF time tomorrow.,1410837485,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160597 merged by Catrope:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160597",1410835912,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160596 merged by Catrope:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160596",1410835903,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160584 merged by jenkins-bot:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160584",1410835181,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160597 had a related patch set uploaded by Jforrester:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160597",1410835115,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160596 had a related patch set uploaded by Jforrester:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160596",1410835097,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160584 had a related patch set uploaded by Catrope:
+Use ve.parseXhtml() and ve.serializeXhtml()
+
+https://gerrit.wikimedia.org/r/160584",1410831715,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: Style and bgcolor attributes normalized by Internet Explorer,"Change 160583 had a related patch set uploaded by Catrope:
+Work around IE's normalization of style attributes by abusing XML parsers
+
+https://gerrit.wikimedia.org/r/160583",1410831704,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b56uk34hrwocyqm77dht,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Initial case:
+
+1. Go to https://www.mediawiki.org/wiki/VisualEditor/status?veaction=edit.
+2. Scroll to the final section, remove the ""…"", and insert template.
+3. Pick ""key press"" in the normal way.
+4. Set parameter 1 as ""Ctrl"", parameter 2 as ""Shift"", and parameter 3 as ""V"".
+5. Press ""Insert"".
+
+Result: dialog remains pending whilst endless snowmen get inserted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://www.mediawiki.org/w/index.php?title=VisualEditor/status&oldid=1152478",1410545940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ndseob64bszecd4p2h7o,task_description,resolved
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,Verified the fix in mediawiki.org with the case mentioned above.,1410825529,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Change 160105 merged by jenkins-bot:
+Account for the case where a FocusableNode has an empty outerRects array
+
+https://gerrit.wikimedia.org/r/160105",1410559650,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Change 160105 had a related patch set uploaded by Jforrester:
+Account for the case where a FocusableNode has an empty outerRects array
+
+https://gerrit.wikimedia.org/r/160105",1410559279,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Change 160102 merged by jenkins-bot:
+Account for the case where a FocusableNode has an empty outerRects array
+
+https://gerrit.wikimedia.org/r/160102",1410559231,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen,"Change 160102 had a related patch set uploaded by Catrope:
+Account for the case where a FocusableNode has an empty outerRects array
+
+https://gerrit.wikimedia.org/r/160102",1410559069,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ndseob64bszecd4p2h7o,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog","On any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Cite_VisualEditor_Test?veaction=edit
+
+click Cite, then choose any of Website, Book etc. 
+
+User should see an inspector dialog for that cite, but nothing appears
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1408638180,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_description,resolved
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",Verified the fix in production,1409866340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",Verified the fix in test2 for all dialogs in Chrome and Firefox,1408729928,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",Believe that this is now fixed in phase 0 (test2 etc.),1408726524,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",Verified the fix in Betalabs but this is happening in test2 right now,1408658332,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog",This was because we failed to do the MW-core pull-through of a breaking change in OOUI (whoops).,1408642084,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog","
+Also true of Insert, etc, anything with a selection list",1408638585,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-h2p2ez3bfy7n73tt2adc,task_subcomment,NA
+VisualEditor Mobile: Cannot load Mobile VE in Betalabs in iOS safari,"I cannot load any page with Mobile VE with iOS safari but it works fine in desktop Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406840040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sbk42chhxkin6ieg2dfm,task_description,resolved
+VisualEditor Mobile: Cannot load Mobile VE in Betalabs in iOS safari,Verified the fix in Betalabs.,1406929334,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sbk42chhxkin6ieg2dfm,task_subcomment,NA
+VisualEditor Mobile: Cannot load Mobile VE in Betalabs in iOS safari,"This should be fixed now.
+
+See https://gerrit.wikimedia.org/r/#/c/150995/",1406927676,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-sbk42chhxkin6ieg2dfm,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Scrolling and tapping into CE goes dead after using link inspector,"This just appeared as of a couple hours ago:
+
+1. Go into VE edit mode on beta labs
+2. Select a word and tap link inspector icon in toolbar
+3. Tap done to make the word a link
+4. When you return to the article in edit mode, you're no longer able to scroll the content or tap in to drop the cursor anywhere. All you can do is save, reopen the link inspector, or abandon changes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406757000,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-6bxeocfqy65faxfgqvze,task_description,resolved
+VisualEditor Mobile: [Regression pre-wmf16] Scrolling and tapping into CE goes dead after using link inspector,Verified the fix in betalabs and test2,1407190387,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6bxeocfqy65faxfgqvze,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Scrolling and tapping into CE goes dead after using link inspector,"Change 150719 merged by jenkins-bot:
+Revert ""Make scrolling in PanelLayout smoother on iOS""
+
+https://gerrit.wikimedia.org/r/150719",1406761528,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6bxeocfqy65faxfgqvze,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Scrolling and tapping into CE goes dead after using link inspector,"Change 150719 had a related patch set uploaded by JGonera:
+Revert ""Make scrolling in PanelLayout smoother on iOS""
+
+https://gerrit.wikimedia.org/r/150719",1406760425,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6bxeocfqy65faxfgqvze,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),"1. Make a change to a page on en.wiki and click review changes form the save dialog
+2. Close the save dialog and make another change, go back to the review changes page
+
+Observe that only your first change is visible. The same is true if you submit the change.
+
+This does not happen on my local wiki where I don't have pre-save caching enabled, so presumably it has something to do with that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1406389140,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-633guswlzr7odpcbch5o,task_description,resolved
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),*** Bug 68764 has been marked as a duplicate of this bug. ***,1406578618,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),*** Bug 68761 has been marked as a duplicate of this bug. ***,1406577779,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),"Nasty regression, but awesome response time - thanks, James & Ed!",1406565607,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),*** Bug 68693 has been marked as a duplicate of this bug. ***,1406564584,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),Now back-ported to wmf14 and wmf15 in production.,1406564578,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),*** Bug 68595 has been marked as a duplicate of this bug. ***,1406409644,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),Was fixed by https://gerrit.wikimedia.org/r/#/c/149392 . Quite serious though so should be deployed asap.,1406390642,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled),This is fixed by this - https://gerrit.wikimedia.org/r/#/c/149392/,1406389557,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-633guswlzr7odpcbch5o,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,"I cannot open any page with Mobile VE with iOS Safari, however in desktop Safari I am not seeing this issue
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1406315700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_description,resolved
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,Verified the fix,1407265254,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,This could be the HHVM issue…,1406656292,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,"It seems, it got resolved! Did anyone work on this one?",1406656252,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,"This occurs on desktop Safari too.
+
+It disappears when debug=true is used. Looking at the content response, it looks like Safari is getting the gzip'ed content and not decoding it for some reason.",1406582651,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,The error message that I get in the console is:SyntaxError: Invalid character '\u0031',1406582107,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs,What was the error message you were seeing? Something about an invalid character.,1406580277,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-qnqc42uqv5b4sr7b2rpz,task_subcomment,NA
+VisualEditor Mobile: MobileContext is not in the DOM,"**Author:** `jgonera`
+
+**Description:**
+When running VE on mobile, in the console:
+
+$('.ve-ui-context')
+[]
+$('.ve-ui-mobileContext')
+[]
+
+I thought that the context not appearing on mobile was a CSS regression but it seems it's no longer attached to the DOM. Too tired today to figure out why (or to figure out how DesktopContext is attached to DOM).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406248440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zy4ezl7vztln3ygf33xm,task_description,resolved
+VisualEditor Mobile: MobileContext is not in the DOM,Verified the fix in production,1408047681,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zy4ezl7vztln3ygf33xm,task_subcomment,NA
+VisualEditor Mobile: MobileContext is not in the DOM,Verified the fix in Betalabs and test2,1407190172,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zy4ezl7vztln3ygf33xm,task_subcomment,NA
+VisualEditor Mobile: MobileContext is not in the DOM,"Change 149356 merged by jenkins-bot:
+Attach mobile surface to the toolbar
+
+https://gerrit.wikimedia.org/r/149356",1406330663,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zy4ezl7vztln3ygf33xm,task_subcomment,NA
+VisualEditor Mobile: MobileContext is not in the DOM,"Change 149356 had a related patch set uploaded by Catrope:
+[WIP] Attach mobile surface to the toolbar
+
+https://gerrit.wikimedia.org/r/149356",1406311845,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zy4ezl7vztln3ygf33xm,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which contains a link 
+2.Press return after the link
+
+Observed Result:
+Uncaught TypeError: Cannot read property 'getOuterLength' of undefined VM112:521 
+appears in the console
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14637}",1406073900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fwehkkee2lr5fjpovjuq,task_description,resolved
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,Verified the fix in production,1407188817,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,Verified the fix in test2,1406324279,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,Verified the fix in Betalabs,1406160428,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,Verified the fix in Betalabs,1406160422,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,"Change 148559 merged by jenkins-bot:
+Followup b6cc76d4: call parent's onSetup/onTeardown
+
+https://gerrit.wikimedia.org/r/148559",1406074955,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521,"Change 148559 had a related patch set uploaded by Catrope:
+Followup b6cc76d4: call parent's onSetup/onTeardown
+
+https://gerrit.wikimedia.org/r/148559",1406074567,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fwehkkee2lr5fjpovjuq,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","In hebrew wikipedia, when I have created a new article, added a tamplate to it, wrote text and made it bold or italic - instead of the text appeared a pawn symbol, that was bold or italic according to the button I have clicked.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68147
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68691",1405590900,PHID-USER-em3l7mquu7qcck24eqq5,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_description,resolved
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660955,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659008,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658992,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658728,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656771,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646176,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646095,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645968,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645929,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645498,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645482,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630073,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594970,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","Change 149920 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406573306,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","The cause here is template with multiple unwrapped siblings,
+
+e.g. Template:Done -> [[File:tick.svg|20px]] Done",1406573226,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",*** Bug 68691 has been marked as a duplicate of this bug. ***,1406565502,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears","1. Add a new page in Wikipedia, with the visual editor.
+2. Add tamplate to it (I used ""מיון"" tamplate in the hebrew wikipedia).
+3. Write any text after the tamplate.
+4. Select the text.
+5. Click on the ""bold"" or ""italic"" buttons.
+6. A pawn symbol appears.",1406522131,PHID-USER-em3l7mquu7qcck24eqq5,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",Can you clarify the instructions?,1406466413,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",*** Bug 67797 has been marked as a duplicate of this bug. ***,1406341653,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+"VisualEditor: When making text bold or italic following a template, pawn symbol appears",Confirmed in Chrome and Firefox.,1406341635,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ln7jbu2x6wlzofbjcy4a,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,"Screenshot
+
+After saving a page,cursor still remains enabled on readmode in Betalabs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14361}",1405447980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_description,resolved
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,WFM – BetaLabs hiccup?,1406220733,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,This is happening again on Betalabs,1406146680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,Verified the fix in test2,1405719998,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,Verified the fix in Betalabs,1405556462,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,"Change 146984 merged by jenkins-bot:
+Close the save dialog on teardown only, not on save
+
+https://gerrit.wikimedia.org/r/146984",1405555253,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,"Change 146984 had a related patch set uploaded by Jforrester:
+Close the save dialog on teardown only, not on save
+
+https://gerrit.wikimedia.org/r/146984",1405554415,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,"<Krenair> So we're not destroying the surface, because the SaveDialog closing promise doesn't get resolved
+<Krenair> it's rejected with ""Cannot close window: window already closing with different data""
+<TrevorParscal> Krenair: that's not good
+<TrevorParscal> Krenair: have you identified why it doesn't get resolved?
+<Krenair> Not past that error, yet
+<Krenair> Even if I check !this.saveDialog.getManager().isClosing() before trying to this.saveDialog.close() it does that
+<Krenair> It's fine if I check !this.saveDialog.getManager().closing instead though
+<Krenair> well, then I get ""Uncaught TypeError: Cannot read property 'getComputedStyle' of undefined"", but the surface is torn down
+<Krenair> TrevorParscal, want to investigate further?
+<TrevorParscal> that's to do with removing the window from the dom before it's done with teardown
+<TrevorParscal> I added code in my rewrite which used promises in init to wait for the window to close before removing things, I saw that same error
+<TrevorParscal> maybe I missed something?",1405546313,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,*** Bug 68116 has been marked as a duplicate of this bug. ***,1405534284,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page,*** Bug 68110 has been marked as a duplicate of this bug. ***,1405528387,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b3df6m2mchn3utytvuaf,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"From bug 58221:
+
+Tilman Bayer 2014-07-14 04:16:20 UTC
+
+Another example:
+
+In https://en.wikipedia.org/w/index.php?oldid=616866203&veaction=edit , place the cursor left of ""F"" in the word ""Former"" in the first paragrah, and hit the delete key. The ""F"" is deleted correctly, but the cursor jumps two to the left (between ""s"" and ""."").
+
+Reproduced in Firefox and Chromium under Ubuntu 14.04.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405341540,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_description,resolved
+VisualEditor: Cursor positioning broken after about-grouped inline alien,*** Bug 68037 has been marked as a duplicate of this bug. ***,1405445319,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Now fixed. Thank you, all.",1405381338,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146166 merged by Mwalker:
+Update VE core submodule to cfdb3a54
+
+https://gerrit.wikimedia.org/r/146166",1405379310,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146165 merged by jenkins-bot:
+Update VE core submodule to e3fa7ec8
+
+https://gerrit.wikimedia.org/r/146165",1405379165,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146166 had a related patch set uploaded by Jforrester:
+Update VE core submodule to cfdb3a54
+
+https://gerrit.wikimedia.org/r/146166",1405364698,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146165 had a related patch set uploaded by Jforrester:
+Update VE core submodule to e3fa7ec8
+
+https://gerrit.wikimedia.org/r/146165",1405364457,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146161 abandoned by Jforrester:
+Update VE core submodule to cfdb3a54
+
+https://gerrit.wikimedia.org/r/146161",1405364324,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146159 abandoned by Jforrester:
+Update VE core submodule to e3fa7ec8
+
+https://gerrit.wikimedia.org/r/146159",1405364318,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146161 had a related patch set uploaded by Jforrester:
+Update VE core submodule to cfdb3a54
+
+https://gerrit.wikimedia.org/r/146161",1405363675,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146159 had a related patch set uploaded by Jforrester:
+Update VE core submodule to e3fa7ec8
+
+https://gerrit.wikimedia.org/r/146159",1405363602,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146138 merged by jenkins-bot:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146138",1405363540,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146137 merged by jenkins-bot:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146137",1405363528,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146138 had a related patch set uploaded by Jforrester:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146138",1405359116,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146137 had a related patch set uploaded by Jforrester:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146137",1405359096,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146079 merged by jenkins-bot:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146079",1405357551,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Change 146079 had a related patch set uploaded by Esanders:
+Prevent double counting of DM nodes in getNodeAndOffset
+
+https://gerrit.wikimedia.org/r/146079",1405352260,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"The problem here appears to be the IPA template which returns two <span>s which are about-grouped (about=""#mwtX""). I imagine the cursoring logic is expecting an alien to consist of only one node.",1405342403,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+VisualEditor: Cursor positioning broken after about-grouped inline alien,"Anywhere we do logical cursoring you get off by two errors, e.g. delete/backspace/arrow keys (after clicking)",1405341629,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6qxa43n2e2cuawkmsjkj,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Cannot open any cite options or template in betalabs or add it in an article throwing error:
+Uncaught TypeError: Cannot read property 'bind' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405015260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_description,resolved
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Verified the fix in production.,1405625558,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Verified the fix in test 2,1405106330,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Change 145431 merged by jenkins-bot:
+Fix cite/template dialogs
+
+https://gerrit.wikimedia.org/r/145431",1405033579,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Verified the fix in Betalabs,1405030191,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Fixed on master. Need to get a deployer to deal with production (test sites + mediawiki.org currently effected),1405027053,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Change 145427 merged by jenkins-bot:
+Fix cite/template dialogs
+
+https://gerrit.wikimedia.org/r/145427",1405026352,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Change 145431 had a related patch set uploaded by Jforrester:
+Fix cite/template dialogs
+
+https://gerrit.wikimedia.org/r/145431",1405026242,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined","Change 145427 had a related patch set uploaded by Alex Monk:
+Fix cite/template dialogs
+
+https://gerrit.wikimedia.org/r/145427",1405024797,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined",Whoops.,1405015648,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i5anxr3c7tfz3nnupv2g,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Formula
+3.Attempt to insert ""\pi"" inside the inspector
+
+Observed Result:
+As soon as you type \ in the inspector , it loses its focus and tries to parse that \ and shows error ""Failed to parse (lexing error)""
+
+
+Environment:Betalabs
+See the screenshot attached
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14534}",1404157860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eav5fcndl4mja6vawvjn,task_description,resolved
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,Verified the fix in production,1407189188,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,Verified the fix in test2,1406322027,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 147501 merged by jenkins-bot:
+Ignore staging events in CE surface
+
+https://gerrit.wikimedia.org/r/147501",1406162466,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 145442 abandoned by Esanders:
+Keep focus when live editing
+
+Reason:
+Fixed better by If03a200cead in core.
+
+https://gerrit.wikimedia.org/r/145442",1405698730,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 147501 had a related patch set uploaded by Esanders:
+Ignore staging events in CE surface
+
+https://gerrit.wikimedia.org/r/147501",1405698680,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 145444 had a related patch set uploaded by Alex Monk:
+Fix rerendering in VE
+
+https://gerrit.wikimedia.org/r/145444",1405029588,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value,"Change 145442 had a related patch set uploaded by Esanders:
+Keep focus when live editing
+
+https://gerrit.wikimedia.org/r/145442",1405028031,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eav5fcndl4mja6vawvjn,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","On https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-06-11?veaction=edit I am getting this stack trace from VE:
+
+Error: Models must be subclasses of ve.dm.Model
+    at VeDmModelRegistry.ve.dm.ModelRegistry.register (eval at <anonymous> (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:4:670), <anonymous>:276:655)
+    at mw.loader.implement.math-visualeditor-mwmathinspector-title (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.math.visualEditor&skin=vector&version=20140613T004358Z&*:1:363)
+    at runScript (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:171:201)
+    at checkCssHandles (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:171:602)
+    at execute (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:172:384)
+    at Object.mw.loader.implement (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:178:208)
+    at https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.math.visualEditor&skin=vector&version=20140613T004358Z&*:1:11
+
+Chromium 35.0.1916.153, Linux
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1402629360,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2idu63bmownfe3nmo7uw,task_description,resolved
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Fixed. Thank you, Ori!",1402683992,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Change 139445 merged by Ori.livneh:
+Fix the VisualEditor parts of Math-wmf9 with a working cherry pick of I7d5e1174
+
+https://gerrit.wikimedia.org/r/139445",1402683632,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Change 139445 had a related patch set uploaded by Jforrester:
+Fix the VisualEditor parts of Math-wmf9 with a cherry pick of I7d5e1174
+
+https://gerrit.wikimedia.org/r/139445",1402683390,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Change 139429 merged by Ori.livneh:
+Fix the VisualEditor parts of Math-wmf9 with a cherry pick of I7d5e1174
+
+https://gerrit.wikimedia.org/r/139429",1402682543,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","Change 139429 had a related patch set uploaded by Jforrester:
+Fix the VisualEditor parts of Math-wmf9 with a cherry pick of I7d5e1174
+
+https://gerrit.wikimedia.org/r/139429",1402680599,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+"Revert of Math extension in wmf9 causes VisualEditor to crash with ""Models must be subclasses of ve.dm.Model"" on every page","I can reproduce this issue in Chrome 35.0.1916.114 and Firefox 29.0.1 on openSUSE, for any page on mediawiki.org.",1402650583,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-2idu63bmownfe3nmo7uw,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Note: This happens in mediawiki.org (1.24wmf7 (941d0e1)), but not in en.wikipedia (1.24wmf6 (4331f6b)).
+
+To reproduce:
+1. Edit an article. Make a change.
+2. Press ""Save page"".
+3. Try writing an edit summary.
+
+Observed: The text is added to the article.
+
+Expected: The cursor must automatically focus in the edit summary field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1401957480,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-7htliylswhsoxwr2ubyy,task_description,resolved
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Change 137926 merged by jenkins-bot:
+Move save panel init to getReadyProcess
+
+https://gerrit.wikimedia.org/r/137926",1402080830,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,Thanks Ed!,1402080269,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Change 137971 had a related patch set uploaded by Jforrester:
+Move save panel init to getReadyProcess
+
+https://gerrit.wikimedia.org/r/137971",1402080246,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Change 137926 had a related patch set uploaded by Esanders:
+Move save panel init to onReady
+
+https://gerrit.wikimedia.org/r/137926",1402060727,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"Sorry, that comment was half-written about a different bug. Bah Bugzilla.
+
+I can indeed replicate in wmf7 and above (which is now everywhere).",1402000427,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"I can still reproduce it in Firefox and Chrome on mediawiki.org.
+
+In Firefox after opening the Save dialog, if I type, the text is added to the article.
+
+In Chrome the text doesn't seem to be added anywhere.
+
+And what's worse, I can now also reproduce it in the English Wikipedia.",1402000321,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox,"This is concerning; bug 65222 should have fixed this from happening. What browser were you using? I can't replicate in wmf7 in Chrome, Safari or Firefox.
+
+However, it does seem to have regressed in wmf8.",1401997686,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7htliylswhsoxwr2ubyy,task_subcomment,NA
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile","This is bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1400777100,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jgbkfgky2myuop7wzuxk,task_description,resolved
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile",Apparently…,1401324126,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jgbkfgky2myuop7wzuxk,task_subcomment,NA
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile",Is this now fixed?,1401321231,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jgbkfgky2myuop7wzuxk,task_subcomment,NA
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile","Change 135012 merged by jenkins-bot:
+Add createSurface to base target
+
+https://gerrit.wikimedia.org/r/135012",1401318950,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jgbkfgky2myuop7wzuxk,task_subcomment,NA
+"VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile","Change 135012 had a related patch set uploaded by Jforrester:
+Add createSurface to base target
+
+https://gerrit.wikimedia.org/r/135012",1400903688,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jgbkfgky2myuop7wzuxk,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"A few users are reporting (default) gadgets are missing on Portuguese Wikipedia:
+* https://pt.wikipedia.org/w/index.php?oldid=38937709#Scripts_n.C3.A3o_funcionando.21
+* https://pt.wikipedia.org/w/index.php?oldid=38937709#Sem_fast-buttons.2C_sem_hot-cat
+* https://pt.wikipedia.org/w/index.php?oldid=38937709#Problema_com_naveboxes
+* https://pt.wikipedia.org/w/index.php?oldid=38937709#Marcas_de_destaque_n.C3.A3o_aparecem
+
+Currently, ptwiki is running 1.24wmf4.
+
+Maybe related:
+* Bug 65340
+* Bug 65375
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Caf%C3%A9_dos_programadores&oldid=38938024#Problemas_com_os_gadgets",1400280420,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_description,resolved
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),Thanks! :-),1401904218,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),Posted at https://wikitech.wikimedia.org/wiki/Incident_documentation/20140517-bits,1401901021,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"Depooled. There is no indication that this was caused by a software fault, so I'm closing this bug as resolved. Once we have the full story on what happened to that server, a postmortem will be posted to <https://wikitech.wikimedia.org/wiki/Incident_documentation>.",1400289578,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"Of the 4 application servers for bits in eqiad (mw1149, mw1150, mw1151, mw1152), I've identified mw1151 as the problematic one.
+
+Using requests like the following https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.echo.badge%7Cext.gadget.BugStatusUpdate%2CDRN-wizard%2CReferenceTooltips%2CWatchlistChangesBold%2Ccharinsert%2Cedittop%2CmySandbox%2CrefToolbar%2Csearch-new-tab%2Cteahouse%7Cext.geshi.language.css%2Chtml4strict%2Cjavascript%2Ctext%7Cext.geshi.local%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cmw.PopUpMediaTransform%7Cskins.vector.styles%7Cwikibase.client.init&only=styles&skin=vector&*bust123
+
+(keep changing the bust query to make different cache misses).
+
+Ori noticed mw1151 has as CPU spike in ganglia and disk issues.
+
+I confirmed via mwscript on the local apache that its memcached is unable to retreive or store a value for cache key 'enwiki:gadgets-definition:7', from Gadget::loadStructuredList()
+
+We should depool that node and have ops look into it.",1400286015,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"Change 133871 merged by jenkins-bot:
+[wmf debug] resourceloader: Output servedBy when load.php has an error
+
+https://gerrit.wikimedia.org/r/133871",1400284542,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"The summary as of right now is that Gadgets' generated modules are sometimes missing in load.php (and thus gadgets are not loaded) and we don't know why, but top people are on it. :P
+
+It doesn't seem to affect any other modules nor any of Gadget's UI (like the special page or preferences).",1400284403,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"[01:32]	<MatmaRex> Krinkle: unless you have better ideas, i'd check if Gadget::loadStructuredList is sometimes returning null when it shouldn't be, and if yes, why is it doing that
+[01:33]	<Krinkle> MatmaRex: yeah, I'm mw-evalling now
+[01:35]	<Krinkle> Gadget::loadStructuredList() and the underlying memcached object is fine
+[01:35]	<Krinkle> at least not critical, let me inspect it",1400284258,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"[23:19]	<greg-g> now I just need to figure out what is causing: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Skin_and_gadget_issues_16_May_2014
+[23:24]	<MatmaRex> huh, i reproduced it
+[23:24]	<MatmaRex> and looking at this URL: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.echo.badge%7Cext.gadget.BugStatusUpdate%2CDRN-wizard%2CReferenceTooltips%2CWatchlistChangesBold%2Ccharinsert%2Cedittop%2CmySandbox%2CrefToolbar%2Csearch-new-tab%2Cteahouse%7Cext.geshi.language.css%2Chtml4strict%2Cjavascript%2Ctext%7Cext.geshi.local%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cmw.PopUpMediaTransform%7Cskins.vector.styles%7Cwikibase.client.init&only=styles&skin=vector&*
+[23:24]	<MatmaRex> i see a debug comment
+[23:24]	<MatmaRex> Problematic modules: {""ext.gadget.BugStatusUpdate"":""missing"",""ext.gadget.DRN-wizard"":""missing"",""ext.gadget.ReferenceTooltips"":""missing"",""ext.gadget.WatchlistChangesBold"":""missing"",""ext.gadget.charinsert"":""missing"",""ext.gadget.edittop"":""missing"",""ext.gadget.mySandbox"":""missing"",""ext.gadget.refToolbar"":""missing"",""ext.gadget.search-new-tab"":""missing"",""ext.gadget.teahouse"":""missing""}
+[23:24]	<MatmaRex> so, gadgets have magically disappeared
+…
+[23:26]	<ori> they're in the startup module
+[23:26]	<ori> mw.loader.getState('ext.gadget.teahouse')
+[23:26]	<ori> > ""ready""
+[23:27]	<ori> nothing missing for me
+[23:27]	<ori> in that url
+[23:28]	<MatmaRex> ori: took a few page refreshes for me
+[23:28]	<ori> oh yeah
+[23:28]	<MatmaRex> i refreshed that URL now and it loaded right
+[23:28]	<ori> i got it now
+…
+[00:49]	<greg-g> ori: MatmaRex odder can still repro
+[00:50]	greg-g just asked Krinkle to take a look now that he's back online
+[00:51]	<MatmaRex> yeah, i can reproduce still too
+[00:52]	<MatmaRex> seems to happen randomly, like 20% of time when i load an uncached URL
+[00:53]	<MatmaRex> all gadget modules are ""missing""",1400284154,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),//**content hidden as private in Bugzilla**//,1400284137,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),"Change 133871 had a related patch set uploaded by Krinkle:
+[wmf debug] resourceloader: Output servedBy when load.php has an error
+
+https://gerrit.wikimedia.org/r/133871",1400284017,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+ResourceLoader seems to sometimes not see Gadget modules (due to mw1151),//**content hidden as private in Bugzilla**//,1400283898,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q27xrsziqqu2gvfpstjp,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"Seen in Firefox 27 on Windows 8, FF 29 on OSX 10.6
+Reported also on Win7, OSX 10.9
+
+Edit any page on mw.o (or beta labs)
+
+Save button is clickable but does nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1400256360,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5iwkyaqeklkuqfwuota4,task_description,resolved
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"Hm.. not caused by the save button click, but due to the dialog being opened. So the same as bug 65373.
+
+*** This bug has been marked as a duplicate of bug 65373 ***",1400260271,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"Also, I was wrong above, FF on Ubuntu/Linux also shows the problem.",1400260227,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"(In reply to Krinkle from comment #3)
+> (In reply to Chris McMahon from comment #2)
+> > JS console log reports ""JQMIGRATE: jQuery.browser is deprecated""
+> 
+> Unrelated.
+
+Specifically, that's bug 65404.",1400259437,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"(In reply to Chris McMahon from comment #2)
+> JS console log reports ""JQMIGRATE: jQuery.browser is deprecated""
+
+Unrelated.",1400258968,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"JS console log reports ""JQMIGRATE: jQuery.browser is deprecated""",1400256819,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button,"
+Note: FF on Linux is fine.",1400256386,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5iwkyaqeklkuqfwuota4,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"NS_ERROR_NOT_AVAILABLE: appearing while trying to save a page in Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1400192580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_description,resolved
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,Verified the backported fix in test2,1400543255,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Marking this as ""FIXED"".",1400540821,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134159 merged by jenkins-bot:
+MWTransclusionDialog: Remove setMode() call from teardown()
+
+https://gerrit.wikimedia.org/r/134159",1400535862,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,All dialogs are now opening and closing without any error in Betalabs.,1400531406,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134159 had a related patch set uploaded by Jforrester:
+MWTransclusionDialog: Remove setMode() call from teardown()
+
+https://gerrit.wikimedia.org/r/134159",1400525656,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134156 merged by jenkins-bot:
+MWTransclusionDialog: Remove setMode() call from teardown()
+
+https://gerrit.wikimedia.org/r/134156",1400525573,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134156 had a related patch set uploaded by Krinkle:
+MWTransclusionDialog: Remove setMode() call from teardown()
+
+https://gerrit.wikimedia.org/r/134156",1400525082,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Confirmed. Closing the Template dialog triggers it as well. Looks like we found another hole that needs to be plugged.
+
+
+Trace:
+
+ curCSS() load.php:6129
+ .css() load.php:6718
+ .css/<() load.php:6867
+ jQuery.access() load.php:4153
+ .css() load.php:6868
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4170
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4139
+ OO.ui.BookletLayout.prototype.toggleOutline() oojs-ui.js:4382
+ ve.ui.MWTransclusionDialog.prototype.setMode() ve.ui.MWTransclusionDialog.js:229
+ ve.ui.MWTransclusionDialog.prototype.teardown() ve.ui.MWTransclusionDialog.js:335
+ OO.ui.Window.prototype.close() oojs-ui.js:1357
+ OO.ui.Dialog.prototype.close/<() oojs-ui.js:1753",1400524182,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Also, if you just close the Template insertion dialog without adding anything, it throws the error.",1400524088,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Yes, the dialogs are working opening for me now, but I still get this error when I click on Insert Template on Template dialog.",1400523573,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"It has not been backported to production yet (will happen soon).
+
+The automatic deploy to beta.wmflabs.org ran 2 minute after your comment was submitted.",1400523037,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Also, when I try to open Language inspector.",1400522710,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"I am still getting that error : when I try to open Media Settings Dialog, Template and Media Settings.",1400522568,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"(In reply to Greg Grossmeier from comment #26)
+> (In reply to Gerrit Notification Bot from comment #25)
+> > Change 134110 merged by jenkins-bot:
+> > Window: Apply display:none after initialize, not before
+> > 
+> > https://gerrit.wikimedia.org/r/134110
+> 
+> Is this now fixed?
+
+Yes, this should fix it.",1400521759,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"(In reply to Gerrit Notification Bot from comment #25)
+> Change 134110 merged by jenkins-bot:
+> Window: Apply display:none after initialize, not before
+> 
+> https://gerrit.wikimedia.org/r/134110
+
+Is this now fixed?",1400521718,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134110 merged by jenkins-bot:
+Window: Apply display:none after initialize, not before
+
+https://gerrit.wikimedia.org/r/134110",1400520536,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Instead of trying to fill all the wholes where we're doing style computation to early, I've revised https://gerrit.wikimedia.org/r/134110 to instead extend the time window where we can do style computation.
+
+I don't think it was intentionally made this short. The idea was to do it at the end of initialize(), and instead, due to our large code base and sub classes, it ended up at the beginning of initialize().
+
+This moves it back to where it belongs.",1400518868,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Hmm.. with https://gerrit.wikimedia.org/r/134110 applied locally, GridLayout dialogs still fail, this time a little further down the line:
+
+demos/dialogs.html#GridDialog
+ curCSS() jquery.js:6131
+ .css() jquery.js:6723
+ .css/<() jquery.js:6872
+ jQuery.access() jquery.js:4153
+ .css() jquery.js:6873
+ OO.ui.Element.getClosestScrollableContainer() oojs-ui.js:464
+ OO.ui.Element.scrollIntoView() oojs-ui.js:491
+ OO.ui.Element.prototype.scrollElementIntoView() oojs-ui.js:603
+ OO.ui.OptionWidget.prototype.setSelected() oojs-ui.js:6171
+ OO.ui.SelectWidget.prototype.selectItem() oojs-ui.js:6556
+ OO.ui.BookletLayout.prototype.updateOutlineWidget() oojs-ui.js:4616
+ OO.ui.BookletLayout.prototype.addPages() oojs-ui.js:4511
+ GridDialog.prototype.initialize()",1400517114,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 134110 had a related patch set uploaded by Krinkle:
+[WIP] GridLayout: Don't call getDir() during initialize
+
+https://gerrit.wikimedia.org/r/134110",1400517008,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"* Media Edit dialog
+ mw.log</log.warn() load.php:11380
+ curCSS() load.php:6131
+ .css() load.php:6723
+ .css/<() load.php:6872
+ jQuery.access() load.php:4153
+ .css() load.php:6873
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4168
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4137
+ OoUiGridLayout() oojs-ui.js:4069
+ OoUiBookletLayout() oojs-ui.js:4232
+ ve.ui.MWMediaEditDialog.prototype.initialize() ve.ui.MWMediaEditDialog.js:150
+
+* Template (transclusion)
+ mw.log</log.warn() load.php:11380
+ curCSS() load.php:6131
+ .css() load.php:6723
+ .css/<() load.php:6872
+ jQuery.access() load.php:4153
+ .css() load.php:6873
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4168
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4137
+ OoUiGridLayout() oojs-ui.js:4069
+ OoUiBookletLayout() oojs-ui.js:4232
+ ve.ui.MWTemplateDialog.prototype.initialize()
+ ve.ui.MWTransclusionDialog.prototype.initialize()
+
+* Page settings
+ mw.log</log.warn() load.php:11380
+ curCSS() load.php:6131
+ .css() load.php:6723
+ .css/<() load.php:6872
+ jQuery.access() load.php:4153
+ .css() load.php:6873
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4168
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4137
+ OoUiGridLayout() oojs-ui.js:4069
+ OoUiBookletLayout() oojs-ui.js:4232
+ ve.ui.MWMetaDialog.prototype.initialize() ve.ui.MWMetaDialog.js:47",1400515257,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"btw, since Firefox's NS_ERROR_NOT_AVAILABLE exceptions have no stack trace. This is how you catch it:
+
+Locally modify jquery.js like this:
+
+--- a/resources/lib/jquery/jquery.js
++++ b/resources/lib/jquery/jquery.js
+@@ -6122,10 +6122,15 @@ if ( window.getComputedStyle ) {
+                var width, minWidth, maxWidth, ret,
+                        style = elem.style;
+ 
++               try {
+                computed = computed || getStyles( elem );
+ 
+                // getPropertyValue is only needed for .css('filter') in IE9, see #12537
+                ret = computed ? computed.getPropertyValue( name ) || computed[ name ] : undefined;
++               } catch (e) {
++                       mw.log.warn(e);
++                       throw new Error('Firefox computed styles poop');
++               }
+ 
+                if ( computed ) {
+
+
+Then reproduce the error (preferably in debug mode), and fine a stack like the following (this one is for Media Edit dialog):
+
+console.trace:
+ mw.log</log.warn() load.php:11380
+ curCSS() load.php:6131
+ .css() load.php:6723
+ .css/<() load.php:6872
+ jQuery.access() load.php:4153
+ .css() load.php:6873
+ OO.ui.Element.getDir() oojs-ui.js:304
+ OO.ui.GridLayout.prototype.update() oojs-ui.js:4168
+ OO.ui.GridLayout.prototype.layout() oojs-ui.js:4137
+ OoUiGridLayout() oojs-ui.js:4069
+ OoUiBookletLayout() oojs-ui.js:4232
+ ve.ui.MWMediaEditDialog.prototype.initialize() ve.ui.MWMediaEditDialog.js:150
+
+
+Conclusion, like in OO.ui.PanelLayout (fixed in I31b495fc2d9725f), GridLayout, too is doing (what seems to be erroneous) style computation on a hidden frame. So the values of it are already useless, but are now throwing in Firefox.
+
+Should probably be dealt with similarly (in case we find more).",1400514330,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"As far as I can tell the above didn't fix the issue for opening the media edit dialog. The save dialog is now working for me (bug 65401) and mobile citation dialog (bug 65422).
+
+Dialogs that seem to work for me:
+
+* Citation
+* Reference
+* Reference list
+* Media insert
+* Save
+
+* Inspectors all seem to work – Link, language, hieroglyphics, gallery, special character
+
+
+Dialogs that do not:
+
+* Media edit
+* Template (transclusion)
+* Page settings
+
+
+What's the plan for fixing these?",1400312961,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 133738 merged by jenkins-bot:
+PanelLayout: Remove call to getDir()
+
+https://gerrit.wikimedia.org/r/133738",1400282374,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,*** Bug 65422 has been marked as a duplicate of this bug. ***,1400278074,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Upstream bug report:
+ http://bugs.jquery.com/ticket/15098",1400264994,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,*** Bug 65407 has been marked as a duplicate of this bug. ***,1400263581,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"More elaborate trace:
+
+
+Error: [Exception... ""Component is not available""  nsresult: ""0x80040111 (NS_ERROR_NOT_AVAILABLE)""  location: ""JS frame :: http://krinkle.dev/wikimedia/oojs/ui/demos/lib/jquery.js :: curCSS :: line 6128""  data: no]
+
+Not much, but new phrases that can help are ""Component is not available"" and ""JS frame"".
+
+Possibly related:
+https://bugzilla.mozilla.org/show_bug.cgi?id=358415
+> ""And yes, I'm cool with getComputedStyle throwing something like NS_ERROR_NOT_AVAILABLE if there's nothing in the window. """,1400262225,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Happens when opening any dialog that inherits directionality (OO.ui.ConfirmationDialog, ve.ui.MWSaveDialog, etc.)",1400260312,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,*** Bug 65401 has been marked as a duplicate of this bug. ***,1400260271,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Change 133738 had a related patch set uploaded by Krinkle:
+[WIP] Element: Work around Firefox exception in getDir()
+
+https://gerrit.wikimedia.org/r/133738",1400260087,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"To reproduce:
+
+ http://jsfiddle.net/v8Syf/4/",1400251670,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"So it's no longer using the global window and pass the (foreign) node, but uses the correct window now (ownerDocument.defaultView). If anything, that should fix issues, not cause Firefox to throw.",1400249891,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Inside .css():
+
+[1.8.3] jQuery.fn.css
+-> curCSS
+
+ computed = window.getComputedStyle( elem, null ),
+ style = elem.style
+ if ( computed ) {
+   // getPropertyValue is needed for .css('filter') in IE9, see #12537
+   ret = computed.getPropertyValue( name ) || computed[ name ];
+
+
+[1.11.1] jQuery.fn.css
+-> curCSS
+  computed = .. || getStyles( elem );
+  style = elem.style
+
+  // getPropertyValue is needed for .css('filter') in IE9, see #12537
+  ret = computed ? computed.getPropertyValue( name ) || computed[ name ] : undefined;
+
+-> getStyles
+  return elem.ownerDocument.defaultView.getComputedStyle( elem, null );",1400249861,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Caused by 
+
+OO.ui.ConfirmationDialog.prototype.initialize
+
+-> OO.ui.PanelLayout
+  (only when passing $: this.$, without it it works fine, so it is frame
+  related, this is OO.ui.ConfirmationDialog/OO.ui.Dialog/OO.ui.Frame.$)
+
+-> this.$element.addClass( 'oo-ui-' + OO.ui.Element.getDir( this.$.context ) );
+   Removing this line makes it go away.
+
+-> OO.ui.Element.getDir( HTMLDocument frame$context )
+   isDoc
+   obj = obj.body
+-> $( HTMLBodyElement obj ).css( 'direction' )
+
+
+When doing it step-by-step, the error doesn't happen.",1400243458,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Narrowed it down...
+
+A breakpoint doesn't seem to work as this is a lower level exception, this is most likely a bug inside Firefox as well. After this bug most of the page is unresponsive and even reloading the page in the same or a new tab doesn't work (like it has somehow frozen the network layer or no longer allows itself to make requests to this domain). So finding where in our code we go down that path is hard to find.
+
+Inside VisualEditor, it happens for dialogs that have iframes. Specifically the kind that copies link tags. I can see that it does make requests (which get HTTP 304, as it should) for several of the parent document's stylesheets before NS_ERROR_NOT_AVAILABLE is thrown.
+
+When using the oojs-ui dialogs demo, after having manually upgraded lib/jquery.js to jQuery 1.11.1 (without Migrate plugin), I can reproduce this exception in Firefox. But, only for the confirmation dialog. Small, medium, large, and medium footless dialogs are all fine.",1400236738,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Most likely, such as was with Ia7db42b7727b8ca16ae, this is one of three things:
+
+1) We're giving the DOM or jQuery garbage, and previous versions silently just assumed stupidity and used a default. Now it's throwing the garbage back at us. In case of Ia7db42b77, we passed a VeDmDocument object as second parameter to $() for creating a new <div>. That was a nonsensical function call. It defaulted to the global Document. In many cases this would never be merged as that would obviously conflict with iframes, but it happened to be right one here.
+
+* We're relying on an undocumented behaviour (e.g. an old bug, or feature was that really just tolerance or coincidence). E.g. weird code was written, it code worked, got shipped. A good example is eg. doing something like:
+ .css( 'font-size', '100potatoes' )
+or
+ .css( 'font-size', '100pxlz' )
+
+Maybe it previously used parseFloat to strip off 'px' and just assumed it was px, and changed to stripping only 'px' and passing on to the DOM without taking the blame for it and we'd now be getting weird exceptions.
+
+(example, afaik this was not an actual change).
+
+2) We're relying on something that was intentionally changed. Happy reading:
+
+ http://blog.jquery.com/2013/01/15/jquery-1-9-final
+ http://blog.jquery.com/2013/02/04/jquery-1-9-1-released/
+ http://blog.jquery.com/2013/05/24/jquery-1-10-0
+ http://blog.jquery.com/2013/05/30/jquery-1-10-1
+ http://blog.jquery.com/2013/07/03/jquery-1-10-2
+ http://blog.jquery.com/2014/01/24/jquery-1-11
+ http://blog.jquery.com/2014/05/01/jquery-1-11-1
+ http://jquery.com/upgrade-guide/1.9/
+
+3) Oh my, jQuery can have new bugs?",1400234472,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,Caused by the jQuery 1.11 upgrade.,1400198702,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"Correction, not ALL dialogs. The media insertion dialog isn't affected, all the others do seem to be.",1400198177,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"New in wmf5, happens when opening any dialog.",1400195029,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs,"This is not happening with Chrome though, but with Firefox",1400192809,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lcme72ntc4q7f7osmdcq,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Intention:
+Fix the URL in a citation
+
+Steps to Reproduce:
+1. Open an existing citation, using the citation tool.
+
+2. Change something.
+
+3. Apply changes.
+
+4. Look, now you have two:  first an old/wrong version, then a new/corrected version.
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_%28WMF%29/Sandbox&diff=91692&oldid=91691
+
+
+
+Reproducible: Always
+
+Same problem in Firefox and Safari.  No problems with this using the Insert>Reference editor, even though that opens the citation tool for editing citation templates.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398978480,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_description,resolved
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Change 131091 merged by jenkins-bot:
+Fix typo: this.transclusionNode -> this.selectedNode
+
+https://gerrit.wikimedia.org/r/131091",1399332438,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Change 131065 merged by jenkins-bot:
+Fix typo: this.transclusionNode -> this.selectedNode
+
+https://gerrit.wikimedia.org/r/131065",1399054384,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Change 131091 had a related patch set uploaded by Jforrester:
+Fix typo: this.transclusionNode -> this.selectedNode
+
+https://gerrit.wikimedia.org/r/131091",1399053679,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one","Change 131065 had a related patch set uploaded by Esanders:
+Fix typo: this.transclusionNode -> this.selectedNode
+
+https://gerrit.wikimedia.org/r/131065",1399045808,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uhyblvwcfbpgyw4wtwxt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs","Type anything or do any edit on any page in Betalabs 
+
+The undo button remains disabled even you made some changes to that page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398104580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_description,resolved
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs",Verified the fix on https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1398987929,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs",Verified the fix on test2,1398904982,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs","Verified the fix on Betalabs:
+http://en.wikipedia.beta.wmflabs.org/wiki/21staprilchrome?veaction=edit",1398117570,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs","Change 127693 merged by jenkins-bot:
+Revert ""Add aggregate method""
+
+https://gerrit.wikimedia.org/r/127693",1398109266,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Undo"" button remains disabled through out the edit session in Betalabs","Change 127693 had a related patch set uploaded by Catrope:
+Revert ""Add aggregate method""
+
+https://gerrit.wikimedia.org/r/127693",1398109162,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rnyntxlpgpkvucc3e4ik,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Screenshot
+
+Steps to reproduce:
+
+
+1.Try to open the Heiroglyphics inspector
+
+Observed Result:
+The following error shows up in the console:
+Uncaught TypeError: Cannot read property 'forcedLtr' of undefined 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13714}",1397767500,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_description,resolved
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,Verified the fix in production,1398990705,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,Verified the fix in test2,1398123512,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Change 127174 merged by Catrope:
+Extension inspector directionality
+
+https://gerrit.wikimedia.org/r/127174",1398120919,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Verified the fix in Betalabs:
+http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29?veaction=edit",1397780484,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Change 127156 merged by jenkins-bot:
+Extension inspector directionality
+
+https://gerrit.wikimedia.org/r/127156",1397775204,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Change 127174 had a related patch set uploaded by Jforrester:
+Extension inspector directionality
+
+https://gerrit.wikimedia.org/r/127174",1397775139,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Change 127156 had a related patch set uploaded by Jforrester:
+Extension inspector directionality
+
+https://gerrit.wikimedia.org/r/127156",1397772038,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,This is happening for Math and Gallery inspector too.,1397768776,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5",1397767633,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2vmwo4ulefvzsaoj7eql,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Save page button does not become enabled upon adding any text/changing format/adding reference in CE for Betalabs,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add a text/change the format of a text
+
+Observed Result:
+The""Save Page"" button remains disabled on the page
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397695080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tqwxzdskyfhflxbbieky,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Save page button does not become enabled upon adding any text/changing format/adding reference in CE for Betalabs,verified the fix in production with chrome and FF,1398378602,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tqwxzdskyfhflxbbieky,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Save page button does not become enabled upon adding any text/changing format/adding reference in CE for Betalabs,verified the fix on test2,1398196651,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tqwxzdskyfhflxbbieky,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Save page button does not become enabled upon adding any text/changing format/adding reference in CE for Betalabs,Verified the fix on betalabs,1397758979,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tqwxzdskyfhflxbbieky,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Close the VE for it
+3.Again reopen the page with VE
+4.Go to the last and hit return twice
+
+Observed Result:
+The following error appears in the console:
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds
+
+See the screenshot attached
+
+Test Environment:http://en.m.wikipedia.beta.wmflabs.org/
+Page: http://en.m.wikipedia.beta.wmflabs.org/wiki/New_page_for_testing_the_special_characters_by_creating_a_new_page#editor/0
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13638}",1397687700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-okkoyig77ax6awinvswk,task_description,resolved
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,verified the fix on production,1398990962,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,Verified the fix on test2,1398127109,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,"I can still reproduce this issue on 
+http://en.m.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29#editor/0",1397760473,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,"Change 126881 merged by jenkins-bot:
+Destroy the VE target after saving
+
+https://gerrit.wikimedia.org/r/126881",1397695962,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice,"Change 126881 had a related patch set uploaded by Catrope:
+Destroy the VE target after saving
+
+https://gerrit.wikimedia.org/r/126881",1397694778,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-okkoyig77ax6awinvswk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add some references
+3.Insert a reflist
+4.Click on the ""Save Page"" button
+5.Click on ""Review your changes""
+
+
+Observed Result:
+There is no wikitext for the reflist , in the review changes panel it says:
+Could not start the review because your revision matches the latest version of this page.
+
+After saving the page no reflist is appearing on the page
+An error is appearing on the read mode:
+
+
+
+Cite error: There are <ref> tags on this page, but the references will not show without a {{Reflist}} template or a <references /> tag; see the help page. ().
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397673360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mker322rzvciw5p7awgr,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,Verified the fix in production in Chrome and FF,1398384674,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,Verified the fix on test2,1397865515,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,Verified the fix on Betalabs,1397677674,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,"Change 126817 merged by jenkins-bot:
+Make inserting reference lists work again
+
+https://gerrit.wikimedia.org/r/126817",1397673915,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs,"Change 126817 had a related patch set uploaded by Catrope:
+Make inserting reference lists work again
+
+https://gerrit.wikimedia.org/r/126817",1397673752,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mker322rzvciw5p7awgr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,"While trying to edit a new page the following error appears in the console:
+Uncaught TypeError: Cannot call method 'isCollapsed' of null
+
+Also there is no toolbar appearing over the page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63945",1397585820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kzdbresrul4febvg7lyl,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,Verified the fix on test2,1397865921,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,Verified the fix on Betalabs,1397606723,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,"Change 126144 merged by jenkins-bot:
+Don't call select on a fragment if it's null
+
+https://gerrit.wikimedia.org/r/126144",1397601366,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,"Change 126144 had a related patch set uploaded by Trevor Parscal:
+Don't call select on a fragment if it's null
+
+https://gerrit.wikimedia.org/r/126144",1397599588,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs,"While trying to save the edit on an existing page the following error is appearing:
+
+Uncaught TypeError: Cannot call method 'select' of null",1397585966,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kzdbresrul4febvg7lyl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf1] Selection in Firefox can get to 0,0 which then breaks horribly","seen on beta labs as of 15 April in Firefox not in Chrome
+
+on a page that begins with text such as ""two words"" open VE and click link without clicking any other item in the page
+
+insert a link such as ""http://www.example.com""
+
+in Chrome this correctly creates a link like 
+
+	
+[http://www.example.com two] words
+
+
+but in Firefox we get incorrectly instead 
+
+	
+http://www.example.com 	
+  	
+two words
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1397573220,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-gudx655lxaye4zq5b6ff,task_description,resolved
+"VisualEditor: [Regression pre-wmf1] Selection in Firefox can get to 0,0 which then breaks horribly","Change 126835 merged by jenkins-bot:
+Fix initial selection when focusing in Firefox
+
+https://gerrit.wikimedia.org/r/126835",1397678986,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gudx655lxaye4zq5b6ff,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf1] Selection in Firefox can get to 0,0 which then breaks horribly","Change 126835 had a related patch set uploaded by Esanders:
+Fix initial selection when focusing in Firefox
+
+https://gerrit.wikimedia.org/r/126835",1397677823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gudx655lxaye4zq5b6ff,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf1] Selection in Firefox can get to 0,0 which then breaks horribly","With gerrit 126169 this is now slightly better (initial selection is 1,1 but collapses to 0,0 if you click in), but still needs work because 0,0 is achievable. Badness.",1397607544,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gudx655lxaye4zq5b6ff,task_subcomment,NA
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","After wmf21 deployment cannot load VE on en.wiki.GEtting the following error:
+
+Uncaught TypeError: Object #<Object> has no method 'lookup' VM734:1505
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397166240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_description,resolved
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","Looks like a caching issue.
+
+The offending line is 25 of ve.ui.Toolbar.js
+
+Fixed by Timo",1397169111,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_subcomment,NA
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","Looks like Rummana and Trevor can reproduce it on their machine, but Ed and myself cannot.
+
+And on their machine it also doesn't happen in Incognito mode, so looks like it is a caching bug.
+
+-- 
+[#wikimedia-operations]
+ !log krinkle touched php-1.23wmf21/resources/oojs-ui/oojs-ui.js'
+ !log krinkle touched php-1.23wmf21/resources/startup.js
+ !log krinkle touched php-1.23wmf21/extensions/VisualEditor/lib/ve/lib/oojs-ui/oojs-ui.js
+ !log krinkle touched php-1.23wmf21/extensions/VisualEditor/lib/ve/modules/ve/ui/ve.ui.Toolbar.js",1397168178,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_subcomment,NA
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","Uncaught TypeError: Object #<Object> has no method 'lookup' VM1319:1505
+OO.ui.Toolbar.setup VM1319:1505
+ve.init.mw.Target.setUpToolbar VM1319:19180
+ve.init.mw.ViewPageTarget.setUpToolbar VM1319:21943
+(anonymous function)",1397168039,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_subcomment,NA
+"VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load ""Uncaught TypeError: Object #<Object> has no method 'lookup'""","oojs-ui was pulled through to MW core with a breaking change ( https://gerrit.wikimedia.org/r/#/c/121537/ ) before the update to VE extension.
+
+It was correctly pulled through to ve core with changes: https://gerrit.wikimedia.org/r/#/c/120844/",1397167060,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-e4ksvaww5iuvjwbtsxcb,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Page options>Categories section
+3.Type in a category name which does not already exist
+
+Observed Result:
+The new category does not get added 
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63544
+
+**Attached**: {F13724}",1396643100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_description,resolved
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,"Verified the fix in production:
+https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox",1397775530,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,verified the fix on mw.org,1396998519,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,Verified the fix on test.wikipedia.org,1396917397,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs,"This issue got fixed with: https://gerrit.wikimedia.org/r/124381
+Verified the fix in Betalabs",1396911172,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s5rvm6dwfjaakdvzgibq,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Search for a template by typing in something on the search box for example: Cite
+4.When the matching transclusion names appear in the list try to select the first name
+
+Observed Result:
+
+The first match does not get selected .
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63547
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63554
+
+**Attached**: {F13706}",1396638000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r7qy3zpmgywloionffwx,task_description,resolved
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,Verified the fix on mw.org,1396998382,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,Verified the fix on test.wikipedia.org,1396917642,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,Verified the fix in Betalabs: http://en.wikipedia.beta.wmflabs.org/wiki/7thaprilchrome?veaction=edit,1396910740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,"Change 124381 merged by jenkins-bot:
+[BREAKING CHANGE] Death to initializeSelection
+
+https://gerrit.wikimedia.org/r/124381",1396907061,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box,"Change 124381 had a related patch set uploaded by Catrope:
+[BREAKING CHANGE] Death to initializeSelection
+
+https://gerrit.wikimedia.org/r/124381",1396898021,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r7qy3zpmgywloionffwx,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Screenshot
+
+Steps to reproduce:
+
+
+1.Add a link
+2.Apply format on it like Bold/Strikethrough
+3.Now add a space right after that and add a text
+
+
+Observed Result:
+An error appears in the console  Uncaught TypeError: Cannot read property 'constructor' of undefined and the text gets added in a weird way: One letter appears before the link and some letters gets typed inside the link text
+
+See the screenshot attached
+
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/31stMarChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13199}",1396304520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7tigxc4wvpbca2apofph,task_description,resolved
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,Verified the fix in production,1397178212,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,Verified the fix on mediawiki.org,1396989855,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Change 124488 merged by jenkins-bot:
+Adjust loop counters in word break detection when removing item
+
+https://gerrit.wikimedia.org/r/124488",1396912963,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Change 124488 had a related patch set uploaded by Catrope:
+Adjust loop counters in word break detection when removing item
+
+https://gerrit.wikimedia.org/r/124488",1396911225,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,Verified the fix on Betalabs,1396483273,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Change 123373 merged by jenkins-bot:
+Adjust loop counters in word break detection when removing item
+
+https://gerrit.wikimedia.org/r/123373",1396466070,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined,"Change 123373 had a related patch set uploaded by Esanders:
+Adjust loop counters in word break detection when removing item
+
+https://gerrit.wikimedia.org/r/123373",1396465703,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7tigxc4wvpbca2apofph,task_subcomment,NA
+"VisualEditor: ""Unbalanced set of replace operations found"" when deleting table cells","Screencast
+
+If I select a few cells in a table at
+https://pt.wikipedia.org/wiki/Quadrado_perfeito?oldid=38495158&veaction=edit
+and then press DELETE, I get the error ""Unbalanced set of replace operations found"".
+
+See the screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13276}",1395835140,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-bcgfqlvc5q7seezob47j,task_description,resolved
+"VisualEditor: ""Unbalanced set of replace operations found"" when deleting table cells",Verified the fix in test2 and production.,1415910570,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-bcgfqlvc5q7seezob47j,task_subcomment,NA
+"VisualEditor: ""Unbalanced set of replace operations found"" when deleting table cells",This should now be fixed with the new table editing code that replaces this broken issue.,1415883023,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bcgfqlvc5q7seezob47j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,"screenshot
+
+There are wide varieties of type errors I get for undoing typing references in different way.I will try to document each cases in this same bug report:
+
+
+Case 1:
+
+Steps to reproduce:
+
+1.Insert a reference with text for example : reference[1]
+2.Press ""Undo""
+
+Error 1:
+Uncaught TypeError: Cannot read property 'length' of undefined 
+
+3.Place the cursor at the end of the text
+
+Error 2:
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 12 is out of bounds 
+
+
+Case 2:
+
+1.Insert two references with text , for example:
+reference [1]
+reference [2]
+
+2.Now keep on pressing Undo untill the page gets empty
+
+Errors:
+Uncaught TypeError: Cannot read property 'length' of undefined VM484:296
+Uncaught Error: Offset could not be translated to a DOM element and offset: 12 VM484:447
+Uncaught Error: Invalid end offset: 21 VM484:252
+Uncaught Error: Unbalanced input passed to document 
+
+In both cases, after the Undo action , clicking on ""Save Page"" does not do anything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13217}",1395775560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-owiuxjd7oca7orel6ps4,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,Verified the fix in Betalabs: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Reference_numbering&veaction=edit,1395783576,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-owiuxjd7oca7orel6ps4,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,"Change 120874 merged by jenkins-bot:
+Rename stray this.refGroup usage to this.group in MWReferenceModel
+
+https://gerrit.wikimedia.org/r/120874",1395781742,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-owiuxjd7oca7orel6ps4,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,"Change 120874 had a related patch set uploaded by Catrope:
+Rename stray this.refGroup usage to this.group in MWReferenceModel
+
+https://gerrit.wikimedia.org/r/120874",1395780514,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-owiuxjd7oca7orel6ps4,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it,"Created attachment 14904
+screenshot 2
+
+**Attached**: {F13218}",1395775877,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-owiuxjd7oca7orel6ps4,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"On http://en.m.wikipedia.beta.wmflabs.org/
+
+Log in to edit
+Settings to alpha to get VisualEditor
+Attempt to edit any page
+
+A spinner appears and spins forever.  The VE UI never appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1395761400,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-rfstox6mxs6jh237skev,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"Change 120842 merged by jenkins-bot:
+Make generateCitationFeatures() not explode when citation code isn't loaded
+
+https://gerrit.wikimedia.org/r/120842",1395773184,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"Change 120842 had a related patch set uploaded by Catrope:
+Make generateCitationFeatures() not explode when citation code isn't loaded
+
+https://gerrit.wikimedia.org/r/120842",1395771997,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"Looks like the citation code broke this, sorry. I'll fix it.",1395771864,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"Looks like the problem might be in VisualEditor
+
+TypeError: Expecting a function in instanceof check, but got undefined TypeError {stack: (...), message: ""Expecting a function in instanceof check, but got undefined""} load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:9515
+log load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:9515
+handlePending load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:10492
+markModuleReady load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:10632
+nestedAddScript load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:10639
+(anonymous function) load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:10644
+script.onload.script.onreadystatechange load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Clo…:105",1395771506,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1798",1395761710,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rfstox6mxs6jh237skev,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Media Settings icon is not clickable since it got overlayed by image highlight box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image
+3.Select the image
+
+Observed Result:
+The media settings icon is getting hidden by the  Image highlight box and hence not clickable
+
+See the screenshot attached,
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Slug?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F12847}",1394829300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vlfpk6ajyvlxh6hgotnl,task_description,resolved
+VisualEditor: [Regression pre-wmf19] Media Settings icon is not clickable since it got overlayed by image highlight box,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Slug?veaction=edit,1394831749,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vlfpk6ajyvlxh6hgotnl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Media Settings icon is not clickable since it got overlayed by image highlight box,https://gerrit.wikimedia.org/r/#/c/118757/,1394831715,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vlfpk6ajyvlxh6hgotnl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,"I am getting this error while trying to save a page on betalabs:
+Uncaught TypeError: Cannot read property 'saveDialogSave' of undefined
+
+However, if you cancel the dialog box and reload again, it shows that the new content actually got saved
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394480520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-buwthuzxtqpnnddxy6dq,task_description,resolved
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1395350273,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,verified the fix on test2 :https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394846471,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,Verified the fix in betalabs.,1394490633,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,"Change 118021 merged by jenkins-bot:
+Followup 4bd80b62: fix JS error on page save
+
+https://gerrit.wikimedia.org/r/118021",1394489641,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page,"Change 118021 had a related patch set uploaded by Jforrester:
+Followup 4bd80b62: fix JS error on page save
+
+https://gerrit.wikimedia.org/r/118021",1394489530,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-buwthuzxtqpnnddxy6dq,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Unrelated edit removes ""upright"" parameter from images","Verified in the linked URL (I'm using Chrome, Win7, Vector), all I did was adding a few words at the top. I'll add that the edit did trigger the ""corrupted edit, please check"" warning, but I didn't verify what that caught, since the article is very large.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**URL**: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=598527246&oldid=598527036
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53853",1394185740,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lntjwslyqekt7yy463bc,task_description,resolved
+"VisualEditor: [Regression wmf16] Unrelated edit removes ""upright"" parameter from images",*** Bug 62499 has been marked as a duplicate of this bug. ***,1394476478,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lntjwslyqekt7yy463bc,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Unrelated edit removes ""upright"" parameter from images",Fixed with gerrit 117445 backport.,1394223314,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lntjwslyqekt7yy463bc,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Unrelated edit removes ""upright"" parameter from images","**letartean** wrote:
+
+This happens also on fr.wikipedia : https://fr.wikipedia.org/w/index.php?title=%C3%89glise_de_J%C3%A9sus-Christ_des_saints_des_derniers_jours&diff=prev&oldid=101872119
+This is clearly an unintentionnal removal of the upright parameter.",1394215385,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-lntjwslyqekt7yy463bc,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection appearing in en.wiki,"Screenshot
+
+Tried to load VE in en.wiki getting the following error in the console and the label of insert button is missing:
+
+Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13187}",1393007340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dwqhppzvqivqkml7bog4,task_description,resolved
+VisualEditor: Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection appearing in en.wiki,Kk.,1393015148,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dwqhppzvqivqkml7bog4,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection appearing in en.wiki,"(In reply to James Forrester from comment #1)
+> Is this the bug that Roan fixed with the no-op deployment touch this morning?
+Yes, I believe so.",1393015114,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dwqhppzvqivqkml7bog4,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection appearing in en.wiki,Is this the bug that Roan fixed with the no-op deployment touch this morning?,1393014992,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dwqhppzvqivqkml7bog4,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Seen on for example  http://en.m.wikipedia.beta.wmflabs.org/wiki/Selenium_Edit_Test 
+
+As logged-in user with 'alpha' mode set, attempt to edit a page on beta labs. 
+
+VE never appears, Mobile user sees only a spinner. 
+
+VE seems to work correctly for non-Mobile user.  
+
+(Possibly related may be a recent change to Parsoid on beta labs https://bugzilla.wikimedia.org/show_bug.cgi?id=60694)
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1391631060,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-hkzhgk7ageafae2dzf72,task_description,resolved
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Change 111919 merged by jenkins-bot:
+Move paste rules to Target
+
+https://gerrit.wikimedia.org/r/111919",1391732037,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Change 111912 merged by jenkins-bot:
+Move paste rules to Target
+
+https://gerrit.wikimedia.org/r/111912",1391727694,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Change 111919 had a related patch set uploaded by Jforrester:
+Move paste rules to Target
+
+https://gerrit.wikimedia.org/r/111919",1391727639,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","Change 111912 had a related patch set uploaded by Jdlrobson:
+Move paste rules to Target
+
+https://gerrit.wikimedia.org/r/111912",1391726513,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner",Seems to be a problem in the VE codebase. Managed to debug it with Trevor..,1391724891,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner",Actually it was a different parsoid bug. See bug 60755,1391635458,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner",Please provide more detail. It does sound like the parsoid bug...,1391632828,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1669",1391631323,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hkzhgk7ageafae2dzf72,task_subcomment,NA
+"VisualEditor: Cannot Save any page on Betalabs:""TypeError: this.toolbar is null"" appears","Screenshot
+
+I cannot save any page on Betalabs with FireFox and Chrome.It shows an error Unknown error on the dialog box and in the console it shows:
+TypeError: this.toolbar is null
+
+For Chrome, it shows:
+GET http://bits.beta.wmflabs.org/static-master/extensions/VectorBeta/less/images/unwatch-icon.svg 404 (Not Found) 
+
+Also ,Edit button is not loading VE sometimes.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13034}",1391108340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2nuk4asg3igwqhymztcn,task_description,declined
+"VisualEditor: Cannot Save any page on Betalabs:""TypeError: this.toolbar is null"" appears",Not happening anymore though.Page is loading properly now on Betalabs.Also I am able to save the content on any page,1391121473,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2nuk4asg3igwqhymztcn,task_subcomment,NA
+"VisualEditor: Cannot Save any page on Betalabs:""TypeError: this.toolbar is null"" appears","(In reply to comment #0)
+> http://bits.beta.wmflabs.org/static-master/extensions/VectorBeta/less/images/
+> unwatch-icon.svg
+> 404 (Not Found) 
+
+Not sure if related at all; but recent change is http://git.wikimedia.org/commit/mediawiki%2Fcore.git/58f72c5f227b9a16ca9f489cef5171a508a059ee",1391121115,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2nuk4asg3igwqhymztcn,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Steps to reproduce:
+
+1.Open a page with VE
+2.Select an image
+3.Go to Insert>Gallery
+
+Observed Result:
+An error appears in the console ""Uncaught TypeError: Cannot read property 'body' of undefined""
+
+After that the Media Settings option does not appear on any other image .Also the reference dialog option does not show up when you select a reference note.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390861980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_description,resolved
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Change 110652 merged by jenkins-bot:
+Don't throw JS errors when opening MWExtensionInspector on the wrong node type
+
+https://gerrit.wikimedia.org/r/110652",1391470642,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Change 110652 had a related patch set uploaded by Jforrester:
+Don't throw JS errors when opening MWExtensionInspector on the wrong node type
+
+https://gerrit.wikimedia.org/r/110652",1391209857,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,*** Bug 60699 has been marked as a duplicate of this bug. ***,1391204983,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,Verified the fix in test2 and mw.org,1391123779,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=29th_January&veaction=edit,1391021279,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Change 109832 merged by jenkins-bot:
+Don't throw JS errors when opening MWExtensionInspector on the wrong node type
+
+https://gerrit.wikimedia.org/r/109832",1390936358,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Change 109832 had a related patch set uploaded by Catrope:
+Don't throw JS errors when opening MWExtensionInspector on the wrong node type
+
+https://gerrit.wikimedia.org/r/109832",1390879415,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"There's no validation going on in MWExtensionInspector at all, so it's happy to try and inspect references or images or anything that's inspectable, even if it can't be inspected by the inspector you tried to open.",1390862654,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error,"Created attachment 14386
+Screenshot
+
+**Attached**: {F13418}",1390862238,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rgzdxwwd2r7aewnb3lwu,task_subcomment,NA
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Select a Text and press command+k
+
+Observed Result:
+Observe that no page suggestions are appearing on the link inspector regardless of whether it is a new page or an existing page.
+
+
+See the screenshot attached.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13086}",1390502760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-txpk2gqbin5ejaia7ygi,task_description,resolved
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,Verified the fix in test2 and mw.org,1391124077,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-txpk2gqbin5ejaia7ygi,task_subcomment,NA
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Jan_27th,1390863216,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-txpk2gqbin5ejaia7ygi,task_subcomment,NA
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,"Change 109738 merged by jenkins-bot:
+Followup 7994eae8c2: fix MWLinkInspector breakage
+
+https://gerrit.wikimedia.org/r/109738",1390857394,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-txpk2gqbin5ejaia7ygi,task_subcomment,NA
+VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs,"Change 109738 had a related patch set uploaded by Catrope:
+Followup 7994eae8c2: fix MWLinkInspector breakage
+
+https://gerrit.wikimedia.org/r/109738",1390857187,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-txpk2gqbin5ejaia7ygi,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a gallery from Insert>Gallery or just simply close the inspector without adding anything.
+3.Click on the ""Save Page"" button
+
+Observed Result:
+
+The page cannot be saved.
+
+An error appears in the console:
+Uncaught Error: InvalidCharacterError: DOM Exception 5
+
+See the screenshot attached.
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Thedomtest&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12917}",1390339800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gfuv2xwswyf4byfslddo,task_description,resolved
+VisualEditor: Cannot save a page after adding gallery to a page,"Change 110826 merged by jenkins-bot:
+Add tagName to ve.dm.MWGalleryNode
+
+https://gerrit.wikimedia.org/r/110826",1391470681,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"Change 110826 had a related patch set uploaded by Jforrester:
+Add tagName to ve.dm.MWGalleryNode
+
+https://gerrit.wikimedia.org/r/110826",1391299617,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,Verified the fix in mw.org and test2,1391124375,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,Verified the fix in betalabs.,1390869782,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"Change 109759 merged by jenkins-bot:
+Add tagName to ve.dm.MWGalleryNode
+
+https://gerrit.wikimedia.org/r/109759",1390862079,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"Change 109759 had a related patch set uploaded by Catrope:
+Add .tagName to MWGalleryNode
+
+https://gerrit.wikimedia.org/r/109759",1390859181,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Cannot save a page after adding gallery to a page,"**cmitasch** wrote:
+
+I can confirm the behaviour. It does not work in Chrome but it is working with Firefox 26.0.",1390392224,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gfuv2xwswyf4byfslddo,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Comment to follow from Roan.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1389836760,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_description,resolved
+VisualEditor: Copying references is completely broken,Checked the cases mentioned above.All of them are working now on Betalabs.No JS error is appearing now after copy -paste of reference.,1390937533,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,This patch may not have been merged into ve-mw yet. Please check commit history.,1390929298,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"The following JS error appears if I copy a reference note with some text following it.
+Uncaught Error: Unbalanced input passed to document",1390865438,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 109481 merged by jenkins-bot:
+Fix balancing of data in cloneSliceFromRange
+
+https://gerrit.wikimedia.org/r/109481",1390862444,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 109481 had a related patch set uploaded by Esanders:
+Fix balancing of data in cloneSliceFromRange
+
+https://gerrit.wikimedia.org/r/109481",1390675462,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 108720 merged by jenkins-bot:
+Fix up result of selectNodes
+
+https://gerrit.wikimedia.org/r/108720",1390415384,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 108720 had a related patch set uploaded by Esanders:
+Fix up result of selectNodes to remove empty items
+
+https://gerrit.wikimedia.org/r/108720",1390331335,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 108692 merged by jenkins-bot:
+Fix exception thrown by findEndOfNode
+
+https://gerrit.wikimedia.org/r/108692",1390330490,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Change 108692 had a related patch set uploaded by Esanders:
+Fix exception thrown by findEndOfNode
+
+https://gerrit.wikimedia.org/r/108692",1390323703,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Based on these findings, my expectation of what will and won't work is:
+
+Probably broken:
+* Copying a reference by itself, where that reference is immediately preceded by text in the same paragraph (foo|[1]|bar)
+* Copying a reference plus some text before it (f|oo[1]|bar)
+* Copying a reference plus some text after it, where there is no text immediately preceding that reference in the same paragraph (|[1]ba|r)
+
+Probably works:
+* Copying a reference plus some text after it, where that reference is immediately preceded by text in the same paragraph (foo|[1]ba|r)
+* Copying a reference plus text before and after it (f|oo[1]ba|r)
+* Copying a reference by itself, where there is no text immediately preceding that reference in the same paragraph (|[1]|bar)",1389839300,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"I forgot to include how these things lead to the actual failure:
+
+* cloneSliceFromRange returns a slice with an unclosed paragraph opening at the very beginning, as described above
+* The tree build algorithm in ve.dm.Document doesn't actually care about the unclosed opening and builds the tree as if the mwReference was the first node. This means we get a mostly valid tree except that all the offsets are off by one because the paragraph opening element was ignored
+* When we try to get the contents of the internalItem associated with the reference from this unbalanced slice, the range in the tree is one off from the range in the data array. And so instead of [ {type:'paragraph'}, 'F', 'o', 'o', {type:'/paragraph'} ] we get [ {type:'internalItem'}, {type:'paragraph'}, 'F', 'o', 'o' ] when calling .getFullData( itemNodeRange, true ) in ve.dm.MWReferenceNode.static.toDomElements on line 135 (it's actually written as .getFullData( new ve.Range( itemNodeRange.start, itemNodeRange.end ), true ) which is just WTF and should be simplified)
+* This data with two openings and zero closings then gets fed to getDomSubtreeFromData(), which calls removeInternalNodes(), which spots an internalItem as the very first element and tries to find its end with findEndOfNode()
+* findEndOfNode() can't find the internalItem closing because there are no closings, so it tries to throw an error, but that fails because dataElement is undefined and so accessing dataElement.type is itself an error",1389838450,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Copying references is completely broken,"Well, not *completely*, just mostly :)
+
+Go to https://www.mediawiki.org/w/index.php?title=VisualEditor:TestReferenceContents&veaction=edit and select reference [3] by clicking on it, then press Ctrl+C. You'll get a JS error.
+
+There are several things wrong here:
+
+In findEndOfNode() inside of ve.dm.Converter.prototype.getDomSubtreeFromData:
+* Line 1172 tries to throw an error using dataElement.type, but dataElement isn't set anywhere, so the generation of the error itself throws an error
+
+In ve.ce.Surface.prototype.onCopy:
+* On line 693, cloneSliceFromRange() returns a slice with unbalanced data: [ {type:'paragraph'}, {type:'mwReference'}, {type:'/mwReference'}, {type:'internalList'}, ..., {type:'/internalList'} ]
+
+In ve.dm.Document.prototype.cloneSliceFromRange:
+* On both lines 378 and 431, selectNodes() for a range exactly covering a reference returns the text node as well. In my test case, the return value is [ { node: TextNode, range: [69,69] }, { node: ReferenceNode } ]. This is clearly a bug in selectNodes()
+* Even if selection was correctly set to something of length 1, line 388 does not allow for selection[0].range to be undefined, but that's actually expected when a node is completely selected. This case should be handled, and selection[0].nodeRange should be checked against range instead in that case. So something like else if ( selection.length === 1 && range.equalsSelection( selection[0].range || selection[0].nodeRange ) ) . Otherwise, even if we fixed the selectNodes bug, the selection.length===1 code path still wouldn't be taken.
+* Because selection.length>1, the else path is taken, and we populate balanceOpenings and balanceClosings. These two are populated separately in a way that's broken: because the first node is a text node (not wrapped) we add an opening for that node's parent, but because the second node is a reference node (wrapped), we don't add a closing after it. The result is unbalanced output. This code seems to wrongly assume that leaf nodes are always unwrapped.",1389837554,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-vcsituk4chxvmxz2c4wl,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Attempt to invoke VE by clicking the Edit button on my near-empty user page http://en.wikipedia.beta.wmflabs.org/wiki/User:Cmcmahon, get error: 
+
+Error loading data from server: internal_api_error_ErrorPageError: Exception Caught: &lt;editpage-notsupportedcontentformat-text&gt;. Would you like to retry?
+
+Note: several hours ago a number of automated browser tests failed by timing out waiting for 10 seconds for the diff viewer to manifest in the browser.  There may have been a performance problem before this error appeared.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1389282300,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_description,resolved
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Synchronisation for betalabs has been broken for over a week due to bug 49846 – see http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version which says ""VisualEditor 0.1.0 (3e925e6) 20:50, 2 January 2014"". Re-closing as that's a distinct issue.",1389371498,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,*** Bug 59903 has been marked as a duplicate of this bug. ***,1389369253,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"This is fixed on test2/mw.o but still broken on beta labs.  Perhaps it was a hotfix in prod, but master not updated yet?",1389368904,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,Verified the fix in test 2 and mw.org.VE is now loading properly on wmf10.,1389307056,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106628 merged by Ori.livneh:
+Update VisualEditor for cherry pick I5cc44c5ef35 (bug 59867)
+
+https://gerrit.wikimedia.org/r/106628",1389306417,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106628 had a related patch set uploaded by Ori.livneh:
+Update VisualEditor for cherry pick I5cc44c5ef35 (bug 59867)
+
+https://gerrit.wikimedia.org/r/106628",1389306237,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,Fix now being deployed.,1389305985,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106627 merged by jenkins-bot:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106627",1389305883,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106621 merged by jenkins-bot:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106621",1389305529,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106627 had a related patch set uploaded by Jforrester:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106627",1389305464,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Asking here instead of in IRC:
+What's the offending commit? When was it merged into master?",1389303854,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"(grumble mid-air collision bz, really adding reedy now)",1389303036,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Adding reedy:
+
+Reedy, if this isn't fixed very quickly, we'll need to revert :/
+
+Rob: Can you get that reviewed and merged and tested on beta cluster ASAP?",1389303014,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106621 had a related patch set uploaded by Krinkle:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106621",1389302979,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"new patch
+https://gerrit.wikimedia.org/r/#/c/106621/",1389302413,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106619 abandoned by Robmoen:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106619",1389302281,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Change 106619 had a related patch set uploaded by Robmoen:
+Provide content format faux reqeust now that content format is validated
+
+https://gerrit.wikimedia.org/r/106619",1389300935,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,"Added Rob Moen and Greg Grossmeier and changed importance, this affects mediawiki.org also",1389300663,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,This is happening on test2 environment now after 1.23wmf10 deployment,1389300217,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10,Confirming.,1389283082,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-uuqogx3zmcprkfif7yn7,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=63377772&oldid=63377716
+
+I added the Citazione Necessaria template to my sandbox,
+and added some text to its only parameter.
+
+As a result I get an additional superscripted ""Citazione necessaria"" which is broken:
+<sup data-ve-ignore=""true"" class=""noprint""><span title=""Il testo selezionato deve essere comprovato da una fonte affidabile. Modifica la pagina per aggiungere fonti."" style=""color:red;"">[''<a href=""/wiki/Wikipedia:Uso_delle_fonti"" title=""Wikipedia:Uso delle fonti"">senza fonte</a>'']</span></sup>
+
+(Not sure if bug 59154/bug 55855 are related.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1388857800,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-euzbw3vi7isnaf55vkqs,task_description,resolved
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","What about these:
+https://en.wikipedia.org/w/index.php?title=Seattle%E2%80%93Tacoma_International_Airport&diff=592102043&oldid=592065880
+https://en.wikipedia.org/w/index.php?title=Lega_Nord&diff=594074863&oldid=593959708
+https://en.wikipedia.org/w/index.php?title=Swedish_Hockey_League&diff=591935813&oldid=589894884
+
+It looks like the fix here was not complete... Did that get fixed at some point?",1410029748,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)",This was fixed by https://gerrit.wikimedia.org/r/#/c/107559/,1390322597,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","(Copy/pasting isn't involved in the cases I reported at least, but thanks for assigning this.)",1389910134,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)",*** Bug 59902 has been marked as a duplicate of this bug. ***,1389904122,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","I've seen this in users of Windows 7, Windows 8, Mac OS 10.8, and Linux.  Editors have encountered this in at least Chrome, Firefox, and Safari.  Systematic testing of browsers can be seen at https://en.wikipedia.org/w/index.php?title=User:Ceyockey/sandbox_spantest&action=history
+
+Other examples include:
+ 
+https://en.wikipedia.org/w/index.php?title=List_of_information_graphics_software&curid=2891117&diff=590578180&oldid=590577937
+
+https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28Greece_season_4%29&curid=40567903&diff=590510331&oldid=590492954
+
+https://en.wikipedia.org/w/index.php?title=Tour_de_Ski&curid=8516243&diff=589296570&oldid=589296376
+
+https://en.wikipedia.org/w/index.php?title=Kamal_Haasan&curid=222346&diff=589232047&oldid=589174733
+
+https://en.wikipedia.org/w/index.php?title=PTC_Therapeutics&curid=13883765&diff=589307581&oldid=589306439
+
+https://office.wikimedia.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=105448&oldid=105447",1389897063,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","**mr.heat** wrote:
+
+This obviously is the same error:
+https://de.wikipedia.org/wiki/Nest_Labs?diff=126472789
+
+Reported/discussed here:
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/HTML_output_from_template_leaked_into_wikitext
+
+I tried to reproduce it but it did not happen.",1389888156,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","The French template ""etc"" gets a similar error:
+https://fr.wikipedia.org/w/index.php?title=Gremlin&diff=99848534&oldid=92711100
+
+{{etc}}<abbr data-ve-ignore=""true"" class=""abbr"" title=""et cetera"" xml:lang=""la"" lang=""la"">etc.</abbr>",1388961477,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)","The French version of that template also gets that bug, while the English one probably works differently: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=589354249&oldid=583268893 .",1388961303,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-euzbw3vi7isnaf55vkqs,task_subcomment,NA
+SVG icons embedded in stylesheets broken in Wikimedia production due to mime-type confusion,"Screenshot of problem in production.
+
+As of recently, we have SVG versions of the external link icons in MediaWiki. These are embedded as base64 encoded data uris by CSSMin in ResourceLoader.
+
+Locally, these are working fine for me. Comes out as:
+
+ background-image: linear-gradient(transparent,transparent),url(data:image/svg+xml;base64,PD...
+
+In production, however, they are broken.
+E.g.: https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet#Links
+
+ background-image: linear-gradient(transparent,transparent),url(data:application/xml;base64,PD...
+
+I can consistently reproduce this in Chrome (latest stable). I eliminated other causes by verifying that it breaks locally if I change the mime type in the CSS manually, and visa versa by changing it to image/svg+xml in the browser console when looking at production.
+
+
+Not sure if this supposed to work according to the spec, but fact is, Chrome (maybe other browsers as well) does not accept application/xml in data uris for background images.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major
+
+**Attached**: {F12090}",1388754600,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ej7jssp2ujl54r7e4pzw,task_description,resolved
+SVG icons embedded in stylesheets broken in Wikimedia production due to mime-type confusion,"
+
+*** This bug has been marked as a duplicate of bug 59234 ***",1388755125,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ej7jssp2ujl54r7e4pzw,task_subcomment,NA
+SVG icons embedded in stylesheets broken in Wikimedia production due to mime-type confusion,https://github.com/wikimedia/mediawiki-core/blob/master/includes/libs/CSSMin.php#L118-L142,1388754911,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ej7jssp2ujl54r7e4pzw,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"On MediaWiki.org (1.23wmf9), MW thinks that the appropriate MIME type for SVGs embedded in CSS as data: URIs is application/xml instead of image/svg+xml, causing them not to show up in any browser. It works for me locally.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: major
+**URL**: https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet#Links",1388703960,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_description,resolved
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #33)
+> I'll clone this ticket to cover the general issue.
+
+Filed as bug 59744. I only CC'd Kevin. The rest of you can CC yourselves if you'd like.",1389053266,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Both https://www.mediawiki.org/w/index.php?title=Requests_for_comment/Custom_inter-namespace_tabs&action=edit and [[mw:Special:RecentChanges]] look good to me now. Thanks!
+
+Marking this ticket as resolved/fixed. I'll clone this ticket to cover the general issue. Kevin: thanks as always for digging into this. :-)",1389052804,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #29)
+> (In reply to comment #23)
+> > I'm seeing missing arrows next to ""Templates used on this page:"" below the
+> > edit
+> > window on mediawiki.org as well. Example URL:
+> > <https://www.mediawiki.org/w/index.php?title=Requests_for_comment/
+> > Custom_inter-namespace_tabs&action=edit>.
+> > I'm not sure if this is already covered by the Gerrit changes linked above.
+> 
+> Ditto.
+> 
+> Also seeing it on the Beta Cluster, eg at
+> http://en.wikipedia.beta.wmflabs.org/w/index.
+> php?title=Dido_Sotiriou&action=edit
+> 
+> The Beta Cluster is already running with
+> https://gerrit.wikimedia.org/r/#/c/105469/ though, ie: even the cherrypick to
+> wmf9 (https://gerrit.wikimedia.org/r/#/c/105477/) won't fix it on mw.org most
+> likely.
+> 
+> So, this issue isn't fixed with any of the already merged (to master)
+> patches.
+
+I think I mispoke here/wasn't looking at the right thing. I think this one is indeed fixed by the patches.
+
+I think thanks to Reedy's lastest push, everything is back to normal/good. Anyone seeing any other inconsistencies/lack of images?",1389028137,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #30)
+> Change 105477 merged by jenkins-bot:
+> Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+> 
+> https://gerrit.wikimedia.org/r/105477
+
+Fixed mediawiki.org for me",1389027935,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Change 105477 merged by jenkins-bot:
+Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+
+https://gerrit.wikimedia.org/r/105477",1389027746,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #23)
+> I'm seeing missing arrows next to ""Templates used on this page:"" below the
+> edit
+> window on mediawiki.org as well. Example URL:
+> <https://www.mediawiki.org/w/index.php?title=Requests_for_comment/
+> Custom_inter-namespace_tabs&action=edit>.
+> I'm not sure if this is already covered by the Gerrit changes linked above.
+
+Ditto.
+
+Also seeing it on the Beta Cluster, eg at http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Dido_Sotiriou&action=edit
+
+The Beta Cluster is already running with https://gerrit.wikimedia.org/r/#/c/105469/ though, ie: even the cherrypick to wmf9 (https://gerrit.wikimedia.org/r/#/c/105477/) won't fix it on mw.org most likely.
+
+So, this issue isn't fixed with any of the already merged (to master) patches.
+
+(In reply to comment #16)
+> Created attachment 14228 [details]
+> Screenshot of missing arrows from [[mw:Special:RecentChanges]]
+> 
+> (In reply to comment #13)
+> > I don't know what you are looking at on mw.org, but it certainly isn't fixed
+> > for me or Mz ;)
+> 
+> I uploaded a screenshot of how [[mw:Special:RecentChanges]] looks to me at
+> the
+> moment. Perhaps cache?
+
+I don't see that issue on the BetaCluster, but I can confirm on mw.org.
+
+So, this one is indeed fixed with the patches merged to master.
+
+**Attached**: {F12054}",1389026304,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #16)
+> Created attachment 14228 [details]
+> Screenshot of missing arrows from [[mw:Special:RecentChanges]]
+
+I can still reproduce MZMcBride's screenshot after enabling ""Group changes by page in recent changes and watchlist"" on https://www.mediawiki.org/w/index.php?title=Special:Preferences#mw-prefsection-rc
+
+<span class=""mw-collapsible-toggle mw-collapsible-arrow mw-enhancedchange…-enhancedchanges-arrow-space mw-collapsible-toggle-collapsed"" tabindex=""0""></span> is empty but should probably show a collapsible arrow (if I interpret the classes correctly here).
+
+**Attached**: {F12054}",1389026166,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"This seems to have been fixed in file 5.04; however, PHP uses a bundled,
+patched copy of the library that was only updated from 5.03 to 5.11 in
+12cf930a403d.
+
+Running ""git tag --contains 12cf930a403d"" in php-src tells me that
+affected versions of PHP were 5.3.10 and older, as well as 5.4.0.
+Wikimedia runs 5.3.10 in production.
+
+Here's a snippet of the diff:
+
+--- file-5.03/magic/Magdir/sgml	2008-07-26 11:03:55.000000000 -0400
++++ file-5.04/magic/Magdir/sgml	2009-09-19 13:31:35.000000000 -0400
+@@ -1,36 +1,59 @@
+ #------------------------------------------------------------------------------
++# $File: sgml,v 1.24 2009/09/19 17:31:35 christos Exp $
+ # Type:	SVG Vectorial Graphics
+ # From:	Noel Torres <tecnico@ejerciciosresueltos.com>
+ 0	string		\<?xml\ version=""
+ >15	string		>\0
+->>23	search/400	\<svg			SVG Scalable Vector Graphics image
++>>19	search/4096	\<svg			SVG Scalable Vector Graphics image
+ !:mime	image/svg+xml
+
+Note that the start offset of the search for ""<svg"" was dropped from 23 to 19, and the newer, shorter XML declaration was the following 22-character string:
+
+<?xml version=""1.0"" ?>
+
+So this problem could have been avoided by either adding a DOCTYPE or leaving one more whitespace character in the right place.",1388924843,PHID-USER-3ampiwske4lc434cm6ot,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #24 and comment #25)
+
+Neither of these comments were helpful as a reply to comment 23. Thanks for adding Reedy to the relevant changeset, though.",1388895458,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,(I hoper we aren't using yet another set of arrows icons for that),1388890874,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"the arrow fixed hasn't been merged and deployed in wmf9, i've tagged reedy on that changeset.",1388890845,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"I'm seeing missing arrows next to ""Templates used on this page:"" below the edit window on mediawiki.org as well. Example URL: <https://www.mediawiki.org/w/index.php?title=Requests_for_comment/Custom_inter-namespace_tabs&action=edit>. I'm not sure if this is already covered by the Gerrit changes linked above.",1388890745,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #21)
+
+> https://gerrit.wikimedia.org/r/105477
+
+This one is the backport to 1.23wmf9, which someone else will need to merge+deploy.",1388888219,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Change 105477 had a related patch set uploaded by Legoktm:
+Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+
+https://gerrit.wikimedia.org/r/105477",1388888054,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Change 105469 merged by jenkins-bot:
+Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+
+https://gerrit.wikimedia.org/r/105469",1388887982,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Done, sorry about the mess. Backport and deploy to taste.",1388882251,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Change 105469 had a related patch set uploaded by Bartosz Dziewoński:
+Deoptimize SVG versions of enhanced recent changes collapse/show arrows
+
+https://gerrit.wikimedia.org/r/105469",1388882194,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"IIRC I was silly enough to optimize the recent changes arrows in a different commit, eh. Sorry about that, patch on the way.",1388881771,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Created attachment 14228
+Screenshot of missing arrows from [[mw:Special:RecentChanges]]
+
+(In reply to comment #13)
+> I don't know what you are looking at on mw.org, but it certainly isn't fixed
+> for me or Mz ;)
+
+I uploaded a screenshot of how [[mw:Special:RecentChanges]] looks to me at the moment. Perhaps cache?
+
+**Attached**: {F12054}",1388881150,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #14)
+> I'm looking at the main page on mw.o with FF26 on OSX10.9.1 and it looks fine
+> to me.
+
+Tried recent changes with enhanced recent changes on?",1388881144,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,I'm looking at the main page on mw.o with FF26 on OSX10.9.1 and it looks fine to me.,1388880979,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #12)
+> Ori just reverted it via https://gerrit.wikimedia.org/r/#/c/105413/ and
+> pushed
+> it out to wmf9. Looks fixed on the Beta Cluster and mw.org to me.
+
+I don't know what you are looking at on mw.org, but it certainly isn't fixed for me or Mz ;)",1388880710,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Ori just reverted it via https://gerrit.wikimedia.org/r/#/c/105413/ and pushed it out to wmf9. Looks fixed on the Beta Cluster and mw.org to me.
+
+His commit message:
+On my Mac, calling finfo_file on external-link-ltr-icon.svg gets the correct
+MIME-type (""image/svg+xml""), but in production I get  ""application/xml"".
+This is probably due to the version of fileinfo or libmagic that is deployed on
+the cluster. Reverting for now.
+
+
+Robla made the point that just upgrading libmagic isn't the right/full solution: we shouldn't break backwards compat here that quickly.",1388794113,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,*** Bug 59452 has been marked as a duplicate of this bug. ***,1388766487,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #8)
+> (In reply to comment #6)
+> > Bartosz: Can you get a patch for re-adding in the doctype on those svgs?
+> 
+> I didn't even remove doctypes from most of these files (they haven't had
+> any).
+> I'll leave shotgun debugging to someone who has access to production
+> environment; if you need this fixed immediately, try reverting If05ee0e0.
+
+That's what the Beta Cluster is for :).
+
+But you're right, just first random file change I looked at removed the doctype, but the external link svg, which is not shown in that test case on Beta Cluster, didn't have doctype before either.
+
+I'm confused now.
+
+On en.wiki (production), the lock icon next to an external url is a base64 encoded image/png.
+
+On en.betawiki, the lock icon is a base64 application/xml, that is in fact valid/renders if you load it directly. It just doesn't show on the page.
+
+Both viewed with Iceweasel 24.2.",1388766397,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #7)
+Not sure anymore if that's the same problem. Filed as bug 59452 instead.",1388765431,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(In reply to comment #6)
+> Bartosz: Can you get a patch for re-adding in the doctype on those svgs?
+
+I didn't even remove doctypes from most of these files (they haven't had any). I'll leave shotgun debugging to someone who has access to production environment; if you need this fixed immediately, try reverting If05ee0e0.
+
+
+(In reply to comment #7)
+> From #mediawiki a few minutes ago, pasting as it mentions IE difference:
+> <SVG^> Hey all. Is there already a bug report about the missing arrows in the
+> recent changes at MediaWiki.org with Chrome and FF (IE shows them properly)?
+
+Old IE uses the fallback PNG images, which show up correctly.",1388764905,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"From #mediawiki a few minutes ago, pasting as it mentions IE difference:
+<SVG^> Hey all. Is there already a bug report about the missing arrows in the recent changes at MediaWiki.org with Chrome and FF (IE shows them properly)?",1388764605,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Bartosz: Can you get a patch for re-adding in the doctype on those svgs? If you can get that merged today it'll be on Beta shortly after.
+
+The problem is exhibited on Beta Cluster, see eg:
+http://en.wikipedia.beta.wmflabs.org/wiki/User:Greg_%28WMF%29",1388764478,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"(Quote from bug 59249 comment #1)
+> https://github.com/wikimedia/mediawiki-core/blob/master/includes/libs/CSSMin.
+> php#L118-L142
+
+It probably works for us locally because it uses a different function than production, or maybe the underlying library has a different upstream version or configuration of an upstream C-library dependency.
+
+(In reply to comment #4)
+> Since this has worked before, a possible culprit is my commit optimizing the
+> SVGs: If05ee0e0 – lots of things that are supposedly non-essential were
+> removed
+> from the SVGs' source code.
+
+Yeah, let's find out if putting the doctype back makes it work for mimetype library Wikimedia uses in production.
+
+Otherwise we'll have to abstract mime type detection to make sure that valid XML documents of which the root tag is ""<svg>"" are detected as SVG (instead of plain XML).",1388756022,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"Since this has worked before, a possible culprit is my commit optimizing the SVGs: If05ee0e0 – lots of things that are supposedly non-essential were removed from the SVGs' source code.",1388755333,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,*** Bug 59249 has been marked as a duplicate of this bug. ***,1388755125,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,The empty gap is pretty confusing plus might create side effects (bug 59239); hence supporting blocking next deployment (bug 38865). CC'ing greg.,1388748128,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type,"For example, this affects the little icons shown next to links; a blank space appears instead.",1388704047,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3twnkxlpgxzvfbcyqhgy,task_subcomment,NA
+VisualEditor: Broken on mobile due to ULS dependency,"When loaded in alpha on beta labs I get 
+Error: Unknown dependency: jquery.uls Error {} 
+
+Given this is the second dependency related error I've now seen I'm a bit concerned about the speed at which dependencies are added to the mobile version of VisualEditor. Is there a way to better sandbox the mobile code? I find it hard to believe that ULS is actually needed for the stripped down mobile version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387229700,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-rurycjmbtcjhdokp3fmq,task_description,resolved
+VisualEditor: Broken on mobile due to ULS dependency,"Change 102368 merged by jenkins-bot:
+Move additional module loading from mw.Target to mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/102368",1387380981,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rurycjmbtcjhdokp3fmq,task_subcomment,NA
+VisualEditor: Broken on mobile due to ULS dependency,"Change 102368 had a related patch set uploaded by Jdlrobson:
+Move additional module loading to viewPage vs general target
+
+https://gerrit.wikimedia.org/r/102368",1387330337,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rurycjmbtcjhdokp3fmq,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Something&veaction=edit
+
+The error is :
+ailed to load resource: the server responded with a status of 500 (Internal Server Error) http://en.wikipedia.beta.wmflabs.org/w/api.php
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386196320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-expmgbsecy7tgvchmyll,task_description,resolved
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,Verified the fix on betalabs:http://en.wikipedia.beta.wmflabs.org/,1386223067,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Change 99317 merged by jenkins-bot:
+Followup ec3d1d67c: fix fatals because of removed run() methods
+
+https://gerrit.wikimedia.org/r/99317",1386220207,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Change 99317 had a related patch set uploaded by Catrope:
+Followup ec3d1d67c: fix fatals because of removed run() methods
+
+https://gerrit.wikimedia.org/r/99317",1386212974,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Chad – Not sure if this is solely caused by CirrusSearch, but it'd be great to get that factored out.",1386212972,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Exception associated with the HTTP 500 in the Apache logs on beta:
+
+Dec  5 03:02:04 10.4.0.187 apache2: PHP Fatal error:  Class CirrusSearchLinksUpdateJob contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Job::run) in /data/project/apache/common-local/php-master/extensions/CirrusSearch/includes/CirrusSearchLinksUpdateJob.php on line 22",1386212665,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"**jhall** wrote:
+
+Problem also successfully repros for me using Linux (Ubuntu) with Chrome v31 and Firefox v25.",1386203364,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"I am still getting it:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Something&veaction=edit
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5",1386201947,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Cannot reproduce. 
+Generic Labs bug 57968, maybe?",1386201645,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Steps to reproduce:
+
+1.Edit a page
+2.Click on ""Save Page""
+
+Observed Result:
+Unknown Error shows up in the dialog box.
+The error in the console is:
+Failed to load resource: the server responded with a status of 500 (Internal
+Server Error",1386196797,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs,"Created attachment 13987
+Screenshot of the error
+
+**Attached**: {F12113}",1386196499,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-expmgbsecy7tgvchmyll,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Steps to reproduce:
+
+1.Click on Switch to source editing from the down menu for an article on betalabs
+
+Observed Result:
+Nothing happens.It does not switch to source editing from VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1386101520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_description,resolved
+"VisualEditor: [Regression] ""Switch to source editing"" dies","(In reply to comment #9)
+> Seeing something slightly odd after this fix was deployed to Betalabs - not
+> sure this is Bad Thing, so not re-opening the bug at this point…
+> 
+> There are 2 pathways to switch from VE to wikitext, and they now navigate the
+> user to different URLs (this didn't happen prior to the bug fix).
+> 
+> If you start in VE editing mode, and use the ""Edit Source"" tab to switch to
+> wikitext, you end up at:
+> 
+> http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:
+> Oldjoe&action=edit
+> 
+> On other hand, if you start in VE editing mode and select ""Switch to source
+> editing"" from the Page Settings drop-down, you end up at:
+> 
+> http://en.wikipedia.beta.wmflabs.org/wiki/User:Oldjoe?action=submit
+> 
+> Is this the intended behavior?
+
+The change to the primary entry point isn't explicitly intended, but I don't think it's the end of the world to push people towards the canonical (and simpler) URLs.",1388917392,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies",verified in production,1386880493,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","**jhall** wrote:
+
+Seeing something slightly odd after this fix was deployed to Betalabs - not sure this is Bad Thing, so not re-opening the bug at this point…
+
+There are 2 pathways to switch from VE to wikitext, and they now navigate the user to different URLs (this didn't happen prior to the bug fix).
+
+If you start in VE editing mode, and use the ""Edit Source"" tab to switch to wikitext, you end up at:
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Oldjoe&action=edit
+
+On other hand, if you start in VE editing mode and select ""Switch to source editing"" from the Page Settings drop-down, you end up at:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/User:Oldjoe?action=submit
+
+Is this the intended behavior?",1386115369,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Verified the fix on beta labs 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386111795,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies",This should now be fixed.,1386110720,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Change 98989 merged by jenkins-bot:
+Fix naked request for save dialog's summary in save
+
+https://gerrit.wikimedia.org/r/98989",1386110546,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Change 98989 had a related patch set uploaded by Jforrester:
+Fix naked request for save dialog's summary in save
+
+https://gerrit.wikimedia.org/r/98989",1386110218,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Yes, it is still occurring.",1386109276,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies",Bug 57926 is now fixed - does this still occur?,1386109221,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies",Sorry Test Environment should be betalabs in my previous comment.,1386101679,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+"VisualEditor: [Regression] ""Switch to source editing"" dies","Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+Example Pagehttp://en.wikipedia.beta.wmflabs.org/wiki/Groel?veaction=edit",1386101651,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aunwbewxqem2omz7rmcs,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"- go to any article
+- edit it with visual editor
+- instead of text of the article in visual editor, text of another article appears
+
+- reproducible for every article I have tried at http://en.wikipedia.beta.wmflabs.org/
+- not reproducible at http://test2.wikipedia.org/
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57233",1386082320,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-owz56g6evszntatdaa2y,task_description,resolved
+beta: Parsoid is returning the wrong articles,"hopefully cleared parsoid cache using:
+
+
+ deployment-parsoidcache3$ sudo varnishadm ban.url .",1386108976,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"And it is fixed now!
+
+Gabriel kindly answered all my newbie questions related to Parsoid architecture. Ended up confirming that Parsoid running on deployment-parsoid2 did query the production infrastructure despite a localsettings.js  claiming otherwise.
+
+Roan showed up and noticed that /var/lib/parsoid/Parsoid points to the shared NFS directory (/data/project/apache/common-local/php-master/extensions/Parsoid/).  That one is autoupdated and did NOT contain the localsettings.js file
+
+Roan copied the settings file, I restarted the server and now it seems to be serving the proper pages.
+
+The root cause is https://gerrit.wikimedia.org/r/98014 from last Friday which I did not bother to verify :-(",1386108793,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"On deployment-parsoid2 , I have edited /usr/bin/parsoid to enable some log, namely the launch command is something like:
+
+ sudo -E -u parsoid nohup node \
+   /var/lib/parsoid/Parsoid/js/api/server.js \
+   >/data/project/logs/parsoid-stdout.log \
+   2>/data/project/logs/parsoid-error.log &
+
+/data/project being the shared project directory, that might gives some clue.",1386107800,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"[13:41] <gwicke> parsoid is not using action=visualeditor
+[13:42] <gwicke> I'd double-check that VE is actually using parsoidcache3
+[13:42] <gwicke> and that the request goes to the right parsoid backend",1386107024,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"The Parsoid does queries to the MediaWiki API to get some content to render. One of the request is logged in api.log as:
+
+ format=json action=visualeditor page=Marching_band paction=parse
+
+I used ApiSandbox to reproduce that query:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:ApiSandbox#action=visualeditor&format=json&page=Marching_band&paction=parse
+
+The response contains among other things:
+
+ http://en.wikipedia.org/wiki/Special:Redirect/revision/51845
+ <title>Marching_band</title>
+ Describe the new page here.
+
+ ""basetimestamp"": ""20120103034343"",
+ ""starttimestamp"": ""20131203212539"",
+ ""oldid"": 51845
+
+The redirection to old id 51845 yields page https://en.wikipedia.org/w/index.php?oldid=51845 which is the 'Pérez Prado' article.",1386106293,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,There is no more 404 errors but some articles still gives content that does not match the page being requested :/,1386101805,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"I upgraded the varnish on parsoidcache instance while I was investigating.
+
+Now it seems VE is querying the parsoid with some invalid URL and it popup a 404 error :-/   Nothing obvious in the logs though, maybe VE has a wgDebugLogGroup we should enable to get more logs.",1386090291,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"
+The articles returned do not seem to originate from beta enwiki or production enwiki",1386088489,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,"I have updated Parsoid code on deployment-parsoid2 in /srv/deployment/parsoid/Parsoid
+
+Forgot to run npm install to update the node modules, might be related :/",1386087321,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+beta: Parsoid is returning the wrong articles,This very much looks like an artefact of the changes for bug 57233 - marking as such.,1386086570,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-owz56g6evszntatdaa2y,task_subcomment,NA
+VisualEditor:Cannot Save a page after adding an image/template/link in the article in beta,"Screenshot attached
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Add any image/template/link in the article
+3.Click the ""Save Page"" button
+
+Observed Result:
+Cannot Save the Article.
+
+The following error is found in the developers tool:
+
+Uncaught TypeError: Object #<VeDmInternalItemNode> has no method 'isCollapsed'
+ve.dm.Transaction.newFromRemoval
+ve.ui.MWReferenceDialog.teardown
+OO.ui.Window.close
+(anonymous function)
+proxy load.php:10
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker
+
+**Attached**: {F12504}",1385855220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5smx3vzr2s6nuq4uvikr,task_description,resolved
+VisualEditor:Cannot Save a page after adding an image/template/link in the article in beta,"
+
+*** This bug has been marked as a duplicate of bug 57683 ***",1386012532,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5smx3vzr2s6nuq4uvikr,task_subcomment,NA
+VisualEditor:Cannot Save a page after adding an image/template/link in the article in beta,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 and FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/wiki/Groel?veaction=edit",1385855466,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5smx3vzr2s6nuq4uvikr,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Steps to reproduce:
+
+1.Click on the Edit page
+2.Select a text or place the cursor at the end of any text
+3.Click on More>Reference
+4.Click on Insert reference
+5.Click on Save Page
+
+Observed Result:
+No reference is getting added in the article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1385585280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytsxsndot74amowyp5vy,task_description,resolved
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,Moved my comments to bug 59599 and bug 59600.,1388769354,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"I think this just happened to me on the Danish Wikipedia?
+I used my userpage as a sandbox https://da.wikipedia.org/w/index.php?title=Bruger:Elitre_(WMF)&action=history, and the edits in which I tried to add references do not show up in the history, although I managed to save them and also got the message that confirms this.
+
+(For the record, I was trying to reproduce https://da.wikipedia.org/w/index.php?title=F-35_Lightning_II&diff=prev&oldid=7409486 and https://da.wikipedia.org/w/index.php?title=Enhedslisten&diff=prev&oldid=7414100 , where there might be a connection between adding a reference and getting a duplicated infobox).",1388180229,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,verified the fix in production,1386880605,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Verified in betalabs.
+http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386024384,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Change 98587 merged by jenkins-bot:
+Fix JS errors when inserting references
+
+https://gerrit.wikimedia.org/r/98587",1386018934,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Change 98587 had a related patch set uploaded by Catrope:
+Fix JS errors when inserting references
+
+https://gerrit.wikimedia.org/r/98587",1386012914,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,*** Bug 57785 has been marked as a duplicate of this bug. ***,1386012532,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"(In reply to comment #2)
+> Please note that, this is working fine in Live right now.
+By Live, I meant production in :https://en.wikipedia.org/",1385585912,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Please note that, this is working fine in Live right now.",1385585494,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta,"Test Environment: Betalabs
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+Example Page:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_(WMF)?veaction=edit",1385585446,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytsxsndot74amowyp5vy,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Seen in Firefox on beta labs as of Nov 25 (Chrome behaves correctly):
+
+Login and navigate to some page with text, e.g. as Selenium_user/User:Selenium_user
+
+Without touching anything on the page, click the ""Link"" icon in the menu bar. 
+
+Expected:  First word in the page is highlighted and link UI appears, referring to highlighted text. 
+
+Actual:  Link icon shows being pressed, but no link UI appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1385424900,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_description,resolved
+VisualEditor: Inspectors fail to appear at all in Firefox,Verified in production,1386881095,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Verified in Betalabs.
+http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386024454,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Change 98688 merged by jenkins-bot:
+Use visibility: hidden; for the ui.Context and its popup
+
+https://gerrit.wikimedia.org/r/98688",1386019137,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Change 98688 had a related patch set uploaded by Catrope:
+Use visibility: hidden; for the ui.Context and its popup
+
+https://gerrit.wikimedia.org/r/98688",1386018229,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,Also partially fixed in gerrit 98598.,1386014515,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Change 98569 merged by jenkins-bot:
+Use visibility: hidden; to hide inspectors
+
+https://gerrit.wikimedia.org/r/98569",1386012369,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Change 98569 had a related patch set uploaded by Catrope:
+Use visibility: hidden; to hide inspectors
+
+https://gerrit.wikimedia.org/r/98569",1386009867,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,Looks like transplantStyles isn't resolving in OO.ui.Frame.,1386006923,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,*** Bug 57779 has been marked as a duplicate of this bug. ***,1386005444,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Also, after clicking on the ""Link"" icon, the ""Save Page"" button does not work anymore even if I close the editor and reopen and re-edit it.Related issue?",1385499120,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"**jhall** wrote:
+
+Now it seems as though the Link interface is completely broken in Firefox.  Following repro steps above, when I click the ""Link"" icon, nothing happens at all (Chrome stills seems to work fine).",1385497011,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+VisualEditor: Inspectors fail to appear at all in Firefox,"Created attachment 13905
+link is pressed, 'Starting' should be highlighted, link UI should appear but does not
+
+**Attached**: {F12079}",1385425033,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-3bskmko72vtqvqb4i7uh,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"As discovered today with the Wikidata weekly summaries run, MassMessage ignores the namespace if it is a interwiki link.
+
+Example; {{#target:Wikidata:Status updates|www.wikidata.org}}
+
+The message gets delivered to https://wikidata.org/wiki/Status_updates which then errors due to it being in NS_MAIN and not NS_PROJECT which was specified.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58524",1385166000,PHID-USER-4n6zx4s5v23pjdztvtnr,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_description,resolved
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Seems to happen again? https://meta.wikimedia.org/w/index.php?title=VisualEditor/Newsletter/Wikis_with_VE&oldid=11801108
+",1430317571,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,This went out to the rest of the sites with today's deployment and looks to be working fine: <https://en.wikipedia.org/w/index.php?title=Wikipedia:Sandbox&diff=prev&oldid=589970369>,1389298817,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"(In reply to comment #22)
+> (In reply to comment #21)
+> > I've been using MassMessage the whole time. Just replace the namespaces with
+> > 'Project:' (if this is not deployed within time).
+> 
+> Is the canonical namespace name safe to use?
+
+Let's see: <https://meta.wikimedia.org/w/index.php?title=Special:Contributions/AnankeBot&dir=prev&offset=20121207114449&limit=39&target=AnankeBot>.",1388578857,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"(In reply to comment #21)
+> I've been using MassMessage the whole time. Just replace the namespaces with
+> 'Project:' (if this is not deployed within time).
+
+Is the canonical namespace name safe to use? If so, that's a handy workaround. :-)
+
+(In reply to comment #20)
+
+People continue to use EdwardsBot, both locally and globally. Bug 58962 is probably more pressing to get resolved, but this bug (bug 57464) is medium priority given the rather nasty side effect (failed deliveries). It can probably go out to Wikimedia wikis on Monday or Tuesday of this week. That'd be a question for Sam, Ori, or Aaron S., I imagine.
+
+There's also bug 54859 about adding an API module for MassMessage. This would help for the Signpost in particular given its use of LivingBot, in my estimation.",1388381982,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"(In reply to comment #20)
+> Dan or Greg, is there any chance we can get this deployed this week?
+> 
+> Because of this bug, we're still dependent on EdwardsBot for global message
+> delivery, and EdwardsBot is planned to be retired from global delivery in 2
+> days. The sooner we can fully transition to MassMessage, the better :)
+
+I've been using MassMessage the whole time. Just replace the namespaces with 'Project:' (if this is not deployed within time).",1388318666,PHID-USER-4n6zx4s5v23pjdztvtnr,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Dan or Greg, is there any chance we can get this deployed this week?
+
+Because of this bug, we're still dependent on EdwardsBot for global message delivery, and EdwardsBot is planned to be retired from global delivery in 2 days. The sooner we can fully transition to MassMessage, the better :)",1388310020,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101814 merged by jenkins-bot:
+Store title as a job parameter
+
+https://gerrit.wikimedia.org/r/101814",1387912109,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101814 had a related patch set uploaded by Legoktm:
+Store title as a job parameter
+
+https://gerrit.wikimedia.org/r/101814",1387174822,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101810 merged by jenkins-bot:
+Add debug logging for bug 57464
+
+https://gerrit.wikimedia.org/r/101810",1387170522,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101810 had a related patch set uploaded by Legoktm:
+Add debug logging for bug 57464
+
+https://gerrit.wikimedia.org/r/101810",1387170502,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101808 merged by jenkins-bot:
+Add debug logging for bug 57464
+
+https://gerrit.wikimedia.org/r/101808",1387169802,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 101808 had a related patch set uploaded by Legoktm:
+Add debug logging for bug 57464
+
+https://gerrit.wikimedia.org/r/101808",1387168721,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"At [[Special:Log/massmessage]] I currently see:
+
+---
+08:38, 9 December 2013 Delivery of ""[[m:Special:MyLanguage/Tech/News/2013/49|Tech News: 2013-49]]"" to Village pump (technical) was skipped because target was in a namespace that cannot be posted in
+---
+
+This is pretty gross. ""Village pump (technical)"" should be ""Wikipedia:Village pump (technical)"". Not sure what's going on with ""[[m:...]]""; that may be a separate bug.
+
+Ori: any chance you could take a look here?",1386882945,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"I'm not able to see where the namespace is being lost, so here are the steps the data goes through. Maybe someone else will spot it.
+
+1. Picked up by MassMessageHooks::storeDataParserFunction as a string
+2. MassMessageHooks::verifyPFData validates that it is a valid title (checks !is_null( Title::newFromText ) ), but returns the original string
+3. MassMessage::getParserFunctionTargets unserializes the string.
+4. MassMessage::normalizeTargets simply re-arranges the list of targets, not modifying the string.
+5. Back to SpecialMassMessage::submit, which feeds the result from normalizeTargets to MassMessageSubmitJob.
+6. the SubmitJob creates a Title object, and submits a group of MassMessageJobs.
+7. On meta, in MassMessageJob::__construct, there is ""$this->title = Title::newFromText( $this->title->getPrefixedText() );"", which was the original fix for this bug. It *should* do nothing when being run on meta.
+8. When the job is executed on the target wiki, that line is run again. Title::getPrefixedText should return the entire title (including interwiki) except for any fragments (url anchors). By re-creating the title, the namespace should be re-parsed as a real namespace instead of an interwiki prefix.
+
+The issue:
+If the namespace is not an interwiki prefix, it is re-parsed correctly as can be seen by the successful deliveries.
+
+If the namespace is an interwiki prefix, it is still thought to be an interwiki prefix (I think), and the delivery fails since it is not interpreted as a namespace.
+
+My hunch is that somewhere step 8 isn't working as I expect it would.",1386652693,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Not fixed apparently, see https://meta.wikimedia.org/w/index.php?title=User_talk:Guillom&oldid=6668167
+
+Glancing at the list of wikis, the first thing I notice is that for all the wikis in the ""did not work"" list (except for one), they all have namespaces that are also interwiki prefixes on meta.
+
+The lone exception is ttwiki, https://tt.wikipedia.org/wiki/%D0%9C%D0%B0%D1%85%D1%81%D1%83%D1%81:%D0%9A%D3%A9%D0%BD%D0%B4%D3%99%D0%BB%D0%B5%D0%BA/massmessage?uselang=en
+
+The weird thing about that is that link is to the correct page. The link on the failed commons delivery is missing the namespace, see https://commons.wikimedia.org/wiki/Special:Log/massmessage",1386649637,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,This was deployed at some point.,1386559175,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"(In reply to comment #6)
+> Kunal: Yeah, please prepare a backport to wmf5.
+
+I've created a branch called '1.23wmf5' and cherry-picked the patch onto it.",1386023039,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 98709 merged by jenkins-bot:
+Create a fresh Title object in the job
+
+https://gerrit.wikimedia.org/r/98709",1386022839,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 98709 had a related patch set uploaded by Legoktm:
+Create a fresh Title object in the job
+
+https://gerrit.wikimedia.org/r/98709",1386022765,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Kunal: Yeah, please prepare a backport to wmf5. And when would you be available to help with the deploy this week? We might be able to get this in tomorrow.
+
+(I assume the only bit that is needed to be backported is gerrit 97162.)",1386005323,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Thanks for the quick fix. This probably didn't get caught because we only deployed to test.wikipedia.org and test2.wikipedia.org, instead of a project such as Wikidata or Commons, which share an interwiki prefix and a namespace name. This probably points to an area where a unit test might make sense? (Or additional test inputs?) Maybe. In any case, this bug is no longer PATCH_TO_REVIEW. I'll leave it to someone else to figure out what to set it to.",1385352969,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Greg, Sam, would it be possible to get this backported and deployed next week? Global message delivery basically won't work because of this.",1385346361,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 97162 merged by jenkins-bot:
+Create a fresh Title object in the job
+
+https://gerrit.wikimedia.org/r/97162",1385343942,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"I guess this might also affect Commons (https://meta.wikimedia.org/wiki/Distribution_list/Global_message_delivery ).
+
+It looks like this issue prevents MM from being used for most of the usual global message deliveries to village pumps, so it's great that we already have a patch, and a timely review and deployment would be useful.",1385178044,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN,"Change 97162 had a related patch set uploaded by Legoktm:
+Create a fresh Title object in the job
+
+https://gerrit.wikimedia.org/r/97162",1385167775,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlk3wsew3wcl527ku3ln,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Try to reuse a reference in VE in an article featuring references.
+
+All you get is the list of number in brackets, which are the numbers of the references, and nothing else.
+
+(Actually, if you test it in https://en.wikipedia.org/wiki/Alex_Timbers?veaction=edit , you will notice that it does provide the ""ref name"" for the first reference; but that's it).
+
+It seems it does not matter which OS, browser or skin you are using.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://commons.wikimedia.org/wiki/File:VisualEditor_ref_dialog_box_showing_numbers_and_ref_names.png",1384810020,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_description,resolved
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Created attachment 14498
+Screenshot of testing the fix
+
+**Attached**: {F12146}",1391644263,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,Verified the fix in test2,1391643894,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,Fixed and back-ported.,1391625632,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111232 merged by jenkins-bot:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111232",1391558723,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111229 merged by jenkins-bot:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111229",1391558662,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"(In reply to comment #11)
+
+Thank you for your reply.",1391557114,PHID-USER-4cgt73x34j35pnbem65l,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111232 had a related patch set uploaded by Jforrester:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111232",1391538518,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111229 had a related patch set uploaded by Jforrester:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111229",1391538506,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111203 merged by jenkins-bot:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111203",1391538435,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Change 111203 had a related patch set uploaded by Esanders:
+Fix 'use existing reference' list rendering
+
+https://gerrit.wikimedia.org/r/111203",1391529322,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Sorry, this bug got entirely missed.
+
+For major regression bugs like this, if they've clearly missed out on immediate triage, please shout out-of-band (e.g. on IRC or the various Feedback pages) as otherwise it's likely to continue to get missed for weeks or even months, as in this case. :-(
+
+Assigning. Ed, please fix urgently.",1391485488,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Nemesis, what you're seeing for the fourth reference is the ref name (<ref name=""Couratier_Transvaal"">).  This is displayed, and might be helpful if the ref name were both sensibly chosen (e.g., not just a number or random letter) and if it already existed for every ref that you wanted to re-use.",1391442591,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"(In reply to comment #9)
+> This is ABSURD.
+
+Please discuss high-level team priorities or workflows e.g. on https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback - this specific bug report is only about this specific bug and its technical aspect. Thanks.",1391432944,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"This is ABSURD. It's been two and half months of having something that *used to work* no longer work. And that something was very USEFUL - if you wanted to use a existing citation/reference to support text in more than one place in an article, you could do so easily. 
+
+Why does it take the VE team MONTHS to fix something that gets broken? How difficult is this, really? Why don't regressions get TOP priority for fixing? 
+
+(Just so there's no misunderstanding about what's broken:
+
+a. In the ""Insert"" menu, select ""Reference""
+b. At the bottom left corner of the dialog box, click ""Use an existing reference"".
+
+While you can still select any existing reference, what you CAN'T do is actually see what the references consist of (author, title, date, publication, etc.). Yes, occasionally some text does appear, but REALLY?
+
+And yes, there is a workaround - first you should look at the References section in the article, and note the reference number you want, BEFORE you do a. and b. above. But REALLY - is this supposed to be user-friendly? Is this the sort of step-by-step procedure we want to put into a user manual?
+
+So to repeat - it's ABSURD that someone can't easily (and quickly) fix a problem that simply involves DISPLAYING SOME TEXT. And if there is an underlying problem with VE or Parsoid that prevents DISPLAYING SOME TEXT, then perhaps someone would post a brief explanation here so that this wouldn't seem so ABSURD.",1391381391,PHID-USER-hirrhium5ibrtof34lwa,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Actually, when test on my sandbox page, https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Ch%C3%A2teau_Rothschild_%28Boulogne-Billancourt%29?veaction=edit, there is some text displayed for the 4th ref. Still, if these two words are indeed in the reference, they are sperarated by many other words. And why for this reference, and not for the others ? The 2nd and the 7th references are very similar but no words are displayed in the tool...",1391380408,PHID-USER-4cgt73x34j35pnbem65l,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"The screenshot at https://en.wikipedia.org/wiki/File:Use_existing_reference_bug_for_VE.jpg shows how inadquate the interface is.  Even if you search for a word that you know is in the ref, you may still be left with many unidentified ref numbers.  ""Please blindly guess which one is the right one"" is not a desirable interface.",1390505223,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"**Wikifram** wrote:
+
+This is not a duplicate, these are completely different issues, and this one isn't fixed in MediaWiki. This bug is not about autonumbering, this is about ""use an existing reference"", where you only get to see the numbers, not the contents of the ref, which is totally useless. Please don't merge unrelated bugs.",1386670773,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Also reported as bug 57420, fix pending. Sorry for the disruption.
+
+*** This bug has been marked as a duplicate of bug 57420 ***",1385374223,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Hey Cainamarques, about this last comment, let's keep this conversation at https://en.wikipedia.org/wiki/User_talk:Cainamarques#Bug.3F . Thanks!",1385064692,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,FORGET my last comment. I did not know I could not edit simple external hiperlinks (with only the url). At least I am assuming I cant...,1385043855,PHID-USER-qlrpm27qlsmjh2pg65bg,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"Yeah, I was not paying attention Elitre. This bug happens to me as well. I did some testing and found something interesting. In the Alex Timbers article, I ""named"" more than one reference to see if the names would show up in the existing references list (as the first one did) and they do. But for whatever reason I can not edit those ""named"" references using VE. It only shows:
+
+[1]
+
+I can edit the first named reference and all the others perfectly. Is that a known bug?
+
+Test page:
+https://en.wikipedia.org/w/index.php?title=User:Cainamarques/sandbox&oldid=582669663",1385041839,PHID-USER-qlrpm27qlsmjh2pg65bg,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number,"This makes the """"Use an existing reference"" functionality almost *useless*. You can't see *any* information about the existing references - the author, title, url, etc., etc. I *could* modify the user guide to say ""Remember the footnote number you want to use again, because if you don't, the dialog box that appears will be worthless"", but that would be embarrassing. Also, hopefully, this regression will be fixed quickly. (I'd feel better if it were prioritized as at least ""High"" priority.)",1385000267,PHID-USER-hirrhium5ibrtof34lwa,True,PHID-TASK-fndgxh4r76y6bofc4pwd,task_subcomment,NA
+VisualEditor: Categories are showing up in wikitext format in the view mode of a page,"Categories
+
+Steps to reproduce:
+
+-Click on the Edit button of a page
+-Click on the Page Settings button
+-Add some category to this page
+-Click on ""Apply Changes""
+-Click on the ""Save Page""
+
+Observed Result:
+The categories appear in wiki text format in the view mode of the page.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12703}",1383611400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ejqmybntf4qgjjx56ees,task_description,resolved
+VisualEditor: Categories are showing up in wikitext format in the view mode of a page,Verified in betalabs,1383764711,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ejqmybntf4qgjjx56ees,task_subcomment,NA
+VisualEditor: Categories are showing up in wikitext format in the view mode of a page,Fixed in https://gerrit.wikimedia.org/r/93640,1383702017,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ejqmybntf4qgjjx56ees,task_subcomment,NA
+VisualEditor: Categories are showing up in wikitext format in the view mode of a page,Thanks for reporting this. It looks like newly added categories are getting mangled this way because Parsoid was rolled back to a version that does not recognize the new mw:PageProp/Category type we're sending it. Gabriel and I are looking into the possibility of redeploying Parsoid with the UTF8 bug fixed later today.,1383612777,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ejqmybntf4qgjjx56ees,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"VE is breaking text encoding on *all* edits on fr.wp. Looks like UTF-8 is being intepreted as ISO-8859-2 or something.
+
+Example edits:
+https://fr.wikipedia.org/w/index.php?title=Tulle&curid=51555&diff=98030422&oldid=98028576
+https://fr.wikipedia.org/w/index.php?title=Herv%C3%A9_Jolly&diff=prev&oldid=98030048
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1383596160,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xnks7a25xfso6juiiyae,task_description,resolved
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"**Wikifram** wrote:
+
+Thank, Bartosz",1383917531,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"Let's just add ""VisualEditor"" to the summary to make this easier to find.",1383833607,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,Bugzilla is primarily a tool for developers and its primary classification is based on codebases (products and components).,1383828783,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"**Wikifram** wrote:
+
+(In reply to comment #9)
+> Reverting. This was a bug with config, not with code, and so belongs in
+> ""Wikimedia"". Also, it was a bug with Parsoid, not with VisualEditor.
+
+This means that people looking for VE bugs won't find it though; this may make sense from a devs point of view, but not from an editor's point of view. They encountered severe problems when editing with VE (and not with wikitext editing), but can't find that bug when searching VisualEditor bugs. 
+
+Take a look at the ""search"" box for Bugzilla; first is status, second is product;  how many people trying to find info on this or similar bugs will look for ""Wikimedia""?",1383826508,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"Reverting. This was a bug with config, not with code, and so belongs in ""Wikimedia"". Also, it was a bug with Parsoid, not with VisualEditor.",1383754027,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"**Wikifram** wrote:
+
+Why ""Wikimedia""? It only happened to VE edits, so for the sake of being able to track bugs in VE editing (fixed and non-fixed, major and minor), I have moved this back to VisualEditor. Wikimedia is much too vague for this...",1383725953,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"Not that it matters, but there is no Apache involved here. Moved it to General.",1383671105,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,Relabelling and moving to the correct component.,1383668957,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,Post mortem has been posted at https://wikitech.wikimedia.org/wiki/Incident_documentation/20131104-Parsoid,1383606352,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,This is fixed now that the Parsoid update has been reverted.,1383599438,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,(gwicke restored working version of the code. Awaiting a post-mortem :) ),1383598310,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,*** Bug 56584 has been marked as a duplicate of this bug. ***,1383598243,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters,"Happens on other wikis too, including sv and pl.",1383596651,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xnks7a25xfso6juiiyae,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Tested on both the Italian and the English Wikipedia;
+Reach the bottom of any page: the style drop down menu does not open (it does when you're at the top of the page); the link inspector does not present the list of options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55465",1380976920,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_description,resolved
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox",Note that this is fixed and has been deployed to the cluster. Please re-open if it still occurs for you after a refresh.,1381281033,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88226 merged by Robmoen:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88226",1381274919,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88225 merged by Robmoen:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88225",1381274909,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox",*** Bug 55362 has been marked as a duplicate of this bug. ***,1381267451,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88226 had a related patch set uploaded by Jforrester:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88226",1381179193,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88225 had a related patch set uploaded by Jforrester:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88225",1381179178,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88195 merged by jenkins-bot:
+The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88195",1381178266,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Change 88195 had a related patch set uploaded by Trevor Parscal:
+Bug 55343 - The amazing mystery of scrollTop and onscroll
+
+https://gerrit.wikimedia.org/r/88195",1381174021,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","(In reply to comment #6)
+> Krinkle, do I need to file a different bug for the non-working wikilink menu
+> part? Thanks.
+
+Yes, let's keep that separate. Could be related, but different user end bugs.",1381168024,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Krinkle, do I need to file a different bug for the non-working wikilink menu part? Thanks.",1381142922,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Can't reproduce it in Chrome, but in Firefox.
+
+Note that (this is difficult to see in the screenshots), the height decreases only when you close and re-open the More menu.
+
+If you open the More menu on top of the page and scroll down, it stays that way and only when you resize the window does the menu grow/shrink (as it should).
+
+But when you close/re-open the menu when scrolled down, it seems to belief the page is shorter than it really is and draw the menu too small (by a factor that relates to how far one scrolls down) until very soon it is completely collapsed.
+
+For me the collapsed point is far from the bottom of the page (I scrolled down a few pixels each time, and after having scrolled a mere 100px it was already completely collapsed).",1381105970,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","From bug 55357:
+
+TeamGale reports:
+
+""while I was getting more down to the page, the drop down menus were getting
+""shorter"" and sometimes disappear at the very end. I tried it to many pages to
+see if it was happening everywhere and it does. I don't know exactly how to
+describe it that's why I took screencaps from the page. All three are from the
+same page, in different height. See how the drop down menu of ""more"" can be
+seen entirely at the top of the page and how it gradually disappear as I get
+closer to the bottom. It's really weird!! The same thing happens when I am
+trying to add a wiki link in the article's text and to be honest, that's how I
+notice the gradually disappearing.""
+
+The screenshot is at [[File:Drop Down Menus.jpg]]
+
+I can reproduce this in Firefox 24 on Linux when using the vector skin, but not
+when using Monobook. 
+
+Trying to add a link after the end of the first paragraph I get no suggestions
+when my window is not maximised. Even when it is maximised it has completely
+disappeared by the end of the page. 
+
+What seems to matter is where the view is, not where the cursor is.",1381080341,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox",*** Bug 55357 has been marked as a duplicate of this bug. ***,1381080286,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox","Created attachment 13447
+Screenshot of the 0px-height menus
+
+These 3 menus have a height of 0px.
+
+I’ve attached a screenshot of these menus without height.
+
+**Attached**: {F12608}",1381055815,PHID-USER-5pyvkdz65d5h5vxebodc,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+"VisualEditor: [Regression] ""More"" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox",Same bug with « more » menu,1380984143,PHID-USER-5pyvkdz65d5h5vxebodc,True,PHID-TASK-64s56xzrc22ustp2z7wx,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"load.php request for ve.base (when it crashes)
+
+At this time, on most Wikipedias that have just been switched to 1.22wmf19, VisualEditor is fatally broken.
+
+It cannot be consistently reproduced, but trying 3 or 4 times will hit the exception.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51766
+
+**Attached**: {F12689}",1380831300,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yznolfyf24iw64vdzaqk,task_description,resolved
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Fixed by touching the JS file in production.
+
+And yeah, this is another artefact of 43805, I think. :-(",1380839704,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),*or bug 43805,1380838980,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),Is this a dupe of bug 51766 or bug 51766?,1380838956,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Contrary to what one might think, both scenarios do not automatically resolve themselves the next 5-minute window of the startup module.
+
+The next time the startup module is generated, 5 minutes later, the max() timestamp of a module will still be the same.
+
+Touching startup.js won't help either.
+
+You'd have to artificially touch the individual module that got corrupted in cache and sync it and hope the same race condition won't happen again.",1380832743,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"The two ve.base request are (naturally) from different cache servers, but the Content-Length is identical, and the Age is close enough (sent out at different times, and my request is at a few seconds later as well).
+
+
+However the ve.core request is significantly different (eventhough we're giving the exact same url with the same timestamp from the startup module).
+
+I think this is a case where it once again shows how conceptually flawed our deployment system is (swapping out files and directory inside /a/common while apache is still fully serving and pooled) – or, how we did not take this into account in the design of ResourceLoader (take your pick).
+
+As a result I think one of the following 2 scenarios happened:
+
+Scenario A:
+- sync deployment starts
+- sync to srv100 complete
+- user visits Wikipedia
+- user requests load.php?module=startup
+  - load balancer picks srv100
+- user requests load.php?module=foo&version=123
+  - (timestamp the user got from srv100)
+  - load balancer picks srv200, which still runs the old code
+  - this url is now cached on some servers
+- user requests load.php?module=bar&version=212
+- sync to srv200 complete
+- sync deployment ends
+
+
+Imagine module bar depends on the (new version of) module foo. From this point on, users hitting srv100 for the module=foo request will keep getting an old version and results in broken scripts in unpredictable ways.
+
+
+
+Scenario B:
+- sync deployment starts
+- sync to srv100 complete
+- user visits Wikipedia
+- user requests load.php?module=startup
+  - load balancer picks srv100
+- sync to srv200 is busy (started, but not complete)
+- user requests load.php?module=foo&version=123
+  - (timestamp the user got from srv100)
+  - load balancer picks srv200, which has mixed code
+    so some of the files concatenated/minified are old some are new
+  - this url is now cached on some servers
+- sync to srv200 finishes
+- user requests load.php?module=bar&version=212
+- sync deployment ends
+
+In this scenario a dependency between different requests/modules doesn't even matter because in our deployment system a server can even be in mixed state within itself (as opposed to a mixed state across the datacenter, as scenario A).
+
+Again, it is cached under the new timestamp.",1380832336,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Created attachment 13436
+load.php request for ve.core (when it does not crash)
+
+**Attached**: {F12692}",1380831357,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Created attachment 13435
+load.php request for ve.core (when it crashes)
+
+**Attached**: {F12691}",1380831344,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined),"Created attachment 13434
+load.php request for ve.base (when it does not crash)
+
+**Attached**: {F12690}",1380831326,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yznolfyf24iw64vdzaqk,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Splitting from bug 54322.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1380823320,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3ez4hz7oidp3mnpniacp,task_description,resolved
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"(In reply to comment #3)
+> Change 87442 merged by jenkins-bot:
+> ve.Element: Fallback to body, window is not scrollable
+> 
+> https://gerrit.wikimedia.org/r/87442
+This was just deployed.",1380843163,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87466 merged by jenkins-bot:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87466",1380841953,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87467 merged by jenkins-bot:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87467",1380841897,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87467 had a related patch set uploaded by Jforrester:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87467",1380839286,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87466 had a related patch set uploaded by Jforrester:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87466",1380839274,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87442 merged by jenkins-bot:
+ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87442",1380839259,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"Change 87442 had a related patch set uploaded by Krinkle:
+(DRAFT) ve.Element: Fallback to body, window is not scrollable
+
+https://gerrit.wikimedia.org/r/87442",1380832685,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined),"I can reproduce this in Chrome on en.wikipedia.org. Though not every time.
+
+Stack trace:
+
+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
+
+In plain English:
+- User clicks Page settings button
+- Dialog doesn't exist yet, so we instantiate it and initialise it
+- MWMetaDialog.initialize adds the 'categories' section
+- SelectWidget sees we don't have a selected panel yet, and now that
+  we have > 0 panels, it selects this new one
+- OptionWidget is brave and tries to ensure the selected panel is
+  visibile attempting to scroll it into view
+- ve.Element traverses up from the panel element until it eventually is
+  unable to find any element that is scrollable and falls back to
+  ve.Element.getWindow( el )
+- We hand off this element (= detached iframe's window), to $.fn.animate
+  which will try to animate scrollTop to 60px.
+
+Both in our jQuery version (v1.8.3) and the current one in use on jquery.com (v1.9.1) animating scrollTop on either window, document or document.documentElement (<html>) is not supported and results in :
+
+
+$(window).animate({'scrollTop': 100})
+< TypeError: Cannot use 'in' operator to search for 'scrollTop' in undefined
+
+* $.css: There is no window.style, and thus no 'scrollTop' in window.style
+* Also, there is no window.scrollTop
+
+$(document).animate({'scrollTop': 100})
+< TypeError: Cannot read property 'ownerDocument' of null
+
+* There is no document.scrollTop.
+
+$(document.documentElement).animate({'scrollTop': 100})
+> [ <html> ]
+
+* No exception, but scroll unchanged.
+* There is a document.documentElement.scrollTop, but it doesn't appear to
+  do anything (defaults to 0, setting is a no-op)
+
+ 
+$(document.body).animate({'scrollTop': 100})
+> [ <body> ]
+
+* Works!
+
+
+
+.... so, we should fix getClosestScrollableContainer to not fallback to window, because that's not a viable fallback as that is in fact not a scrollable container.",1380830178,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-3ez4hz7oidp3mnpniacp,task_subcomment,NA
+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}",1380558180,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-mvlnrj6updlhvfhvduhk,task_description,resolved
+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",1380559572,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mvlnrj6updlhvfhvduhk,task_subcomment,NA
+VisualEditor: Editing at top of page shows pawn/slug character,*** Bug 54785 has been marked as a duplicate of this bug. ***,1380559441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mvlnrj6updlhvfhvduhk,task_subcomment,NA
+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",1380558906,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mvlnrj6updlhvfhvduhk,task_subcomment,NA
+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",1380383040,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_description,invalid
+Don't release any new VE updates for three months,"**Wikifram** wrote:
+
+Allright, thanks to both for the reply.",1380707473,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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.""",1380637726,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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?",1380583797,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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.",1380525615,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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.",1380525374,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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]].",1380395466,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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.",1380394985,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gwdd3z7hkhviwmwe5a2j,task_subcomment,NA
+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",1380298800,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_description,resolved
+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.",1406341511,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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 .",1406307637,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.",1406146981,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,"Um, folks, this may be happening again... please see bug:61272...",1392229880,PHID-USER-brn4v5ta45bnw4f5as3h,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,*** Bug 54976 has been marked as a duplicate of this bug. ***,1380936671,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.",1380843132,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380842062,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380842006,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380837106,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380837082,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380837069,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380836809,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,*** Bug 54917 has been marked as a duplicate of this bug. ***,1380835733,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.,1380832805,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.,1380832424,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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",1380831976,PHID-USER-gfaq55vdypjmzz6nl2kn,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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)",1380789059,PHID-USER-gfaq55vdypjmzz6nl2kn,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,"My edit above to [[OpenOffice.org]] was in Firefox 24.0, Ubuntu 12.04 distro version.",1380644594,PHID-USER-gfaq55vdypjmzz6nl2kn,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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 ""<ref name="":0"" />"", and it's added another spurious one of those higher up",1380643572,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,"Please replace the word ""pawns"" with ""snowmen"". Sorry for the confusion.",1380643247,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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.",1380300630,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+VisualEditor: Snowmen appear near newly added references,"**seudeau** wrote:
+
+%%%*** Bug 54708 has been marked as a duplicate of this bug. ***%%%",1380300556,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+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  :-)>>",1380299308,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-qzxqmy2qhwcdfwstvjhk,task_subcomment,NA
+"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",1379680980,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_description,resolved
+"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",1379977939,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379977741,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379977609,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379977566,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379702067,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379684992,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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"")",1379683942,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+"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",1379683839,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-m5xhygyqlxkvxhsdd6xe,task_subcomment,NA
+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",1379613840,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_description,resolved
+VisualEditor: [Regression] Unnamed references get their names corrupted,*** Bug 54445 has been marked as a duplicate of this bug. ***,1380836921,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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).",1380542637,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+VisualEditor: [Regression] Unnamed references get their names corrupted,*** Bug 54654 has been marked as a duplicate of this bug. ***,1380220185,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379977590,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379977489,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379977417,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379977381,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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",1379680077,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+VisualEditor: [Regression] Unnamed references get their names corrupted,"Change 85144 had a related patch set uploaded by Catrope:
+Failing test for <ref name="":3""> bug
+
+https://gerrit.wikimedia.org/r/85144",1379634802,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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 <ref> 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 <ref name="":3""> 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 <ref name="":n""> tags to the source), then removing or reordering references so the ref tags are aligned exactly right for this bug to occur.",1379625242,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-kfb3zo4zemxl5qzh25hm,task_subcomment,NA
+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: ""êtt<newline>t"" 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",1378943700,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-mb4drpsu5auacyiu42kp,task_description,resolved
+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 ***",1378959962,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mb4drpsu5auacyiu42kp,task_subcomment,NA
+VisualEditor: Corruption with circumflexes,"This is a dupe of bug 53747, bug 53680 or both.",1378945993,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mb4drpsu5auacyiu42kp,task_subcomment,NA
+VisualEditor: Corruption with circumflexes,"Also, circumflexes that are entered in VE are completely stripped on save. Instead, characters are jumping around to its location.",1378944232,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-mb4drpsu5auacyiu42kp,task_subcomment,NA
+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",1378296540,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_description,resolved
+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 :/",1379174957,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.",1378958511,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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!",1378943228,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.",1378745638,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.,1378745123,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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)",1378402971,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.,1378313646,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.",1378313289,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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.",1378297413,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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",1378296668,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pkce7psg2t4g6fb5wfiy,task_subcomment,NA
+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",1378127940,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_description,resolved
+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. ***,1378959962,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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.",1378958522,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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!",1378943119,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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.",1378309729,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns,Same as bug 53747?,1378308416,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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 <save> or even <backspace> 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.",1378307780,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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.",1378194601,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fbhx4wfxlfcwk7mwpqtl,task_subcomment,NA
+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",1377477420,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5bbhrorxovykfuz52i3u,task_description,resolved
+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).,1378223041,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-5bbhrorxovykfuz52i3u,task_subcomment,NA
+Parsoid: Annotated text after a template is deleted,"
+
+*** This bug has been marked as a duplicate of bug 53434 ***",1378222889,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-5bbhrorxovykfuz52i3u,task_subcomment,NA
+Parsoid: Annotated text after a template is deleted,"HTML
+
+<p><span typeof=""mw:Transclusion"" data-mw=""{&quot;target&quot;:{&quot;href&quot;:&quot;Template:Inline&quot;,&quot;wt&quot;:&quot;Inline&quot;},&quot;params&quot;:{&quot;1&quot;:{&quot;wt&quot;:&quot;Foo&quot;}}}""></span><b>bar</b>quux</p>
+
+Expected wikitext
+
+{{Inline|Foo}}'''bar'''quux
+
+Actual wikitext
+
+{{Inline|Foo}}quux
+
+:(",1377884301,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5bbhrorxovykfuz52i3u,task_subcomment,NA
+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.",1377538637,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-5bbhrorxovykfuz52i3u,task_subcomment,NA
+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}",1377188700,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_description,resolved
+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",1392229930,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1392218875,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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.",1392138773,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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.",1392137133,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+VisualEditor: [Regression] Link inspector prevents insertion of section links,… and now deployed.,1377213471,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377212160,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377212156,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377211215,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377211126,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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.,1377206624,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377206517,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1377196029,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+VisualEditor: [Regression] Link inspector prevents insertion of section links,"Ah, good that someone already reported. Confirmed in mediawiki.org.",1377190610,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2o36gh7lztukgi2lajdg,task_subcomment,NA
+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",1375867440,PHID-USER-mapumhlp3gw5qefhvafn,False,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_description,resolved
+VisualEditor: Template gets removed without editing it,Moving to date we likely fixed this with the changes to DM.,1379348384,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+VisualEditor: Template gets removed without editing it,"I can't reproduce it anymore either, so I'm closing it.",1378994061,PHID-USER-mapumhlp3gw5qefhvafn,False,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+VisualEditor: Template gets removed without editing it,"* ""I can't reproduce"" ... the issue. :)",1376929139,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+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
+}}",1376928153,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+VisualEditor: Template gets removed without editing it,"Roan, thoughts? Selser issue?",1375934940,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xtlw6alcryg5gfvrdeqj,task_subcomment,NA
+"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",1375462680,PHID-USER-ppvnwr24o32pux3le5ov,False,PHID-TASK-2czs2gshamoxbwaweocz,task_description,resolved
+"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.,1375469052,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2czs2gshamoxbwaweocz,task_subcomment,NA
+"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",1375468933,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2czs2gshamoxbwaweocz,task_subcomment,NA
+"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",1375468694,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2czs2gshamoxbwaweocz,task_subcomment,NA
+"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link","<<When I was trying to add a link to Classic XI, (didn't know it didn't exist) it repeatedly took the word ""Classic"" and continually tried to make the link go to Classical music. [...] --buffbills7701 19:42, 1 August 2013 (UTC)>>
+
+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",1375391400,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-q6smnzvqe6vc4eby67me,task_description,resolved
+"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link",Fixed and will be deployed tonight.,1375408346,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"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",1375408026,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"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",1375404594,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"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.",1375392847,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"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.",1375392350,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+"VisualEditor: autocomplete for wikilinks ""aggressively"" chooses what to link",*** Bug 52421 has been marked as a duplicate of this bug. ***,1375391536,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-q6smnzvqe6vc4eby67me,task_subcomment,NA
+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",1375331160,PHID-USER-7ey733eainlhx5xqp4d3,False,PHID-TASK-x7tgs2fyboki473gy3pu,task_description,resolved
+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.",1375332474,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-x7tgs2fyboki473gy3pu,task_subcomment,NA
+VisualEditor.php attempts to register a hook handler that was removed,Ia4e2a7854b3a2a5cbbe4da,1375331403,PHID-USER-7ey733eainlhx5xqp4d3,False,PHID-TASK-x7tgs2fyboki473gy3pu,task_subcomment,NA
+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}",1375261620,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-btjddhvc23db2mven5vt,task_description,resolved
+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. ***,1375312992,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar,This is fixed and being pushed live right now.,1375312939,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375308246,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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. ***,1375303552,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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]]",1375296594,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375291680,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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.",1375287482,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375287357,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375286909,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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.",1375280775,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-btjddhvc23db2mven5vt,task_subcomment,NA
+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",1375120080,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hdwzoxwzxwme4zwudykf,task_description,resolved
+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.",1375156109,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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"".",1375144061,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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.",1375135721,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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.",1375124710,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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.",1375124287,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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",1375123842,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+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",1375123752,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+Anonymous users getting VisualEditor on German Wikipedia and making edits,"This appears to be a caching issue, yes",1375122380,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hdwzoxwzxwme4zwudykf,task_subcomment,NA
+"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",1375049820,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_description,resolved
+"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",1375208914,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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. :-)",1375136346,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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?",1375129191,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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.,1375122779,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375119647,PHID-USER-dczyqgtdvr5hclqcljrr,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375116096,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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.",1375115973,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia",This is now done.,1375115930,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375115875,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375112857,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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?",1375086074,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375075738,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375073521,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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",1375072767,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"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: <https://gerrit.wikimedia.org/r/#/c/75543/4/wmf-config/InitialiseSettings.php,unified>.
+
+wmgVisualEditorDefault would be set to false for dewiki.
+
+wmgVisualEditorDisableForAnons would be left as true for dewiki.
+
+Is this correct?",1375070977,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","From bug 49998 comment 8:
+
+---
+In the quick poll (see #7) the results at the moment are as following:
+
+1) enabeling VE as default for all users: 21 votes
+2) VE as default for logged-in users: 6 votes
+3) VE to be opt-in only until all bugs are fixed: 430 votes (!)
+4) enabeling VE under another link name (suggestion was ""Visual Editor (beta)""
+instead of ""Bearbeiten"" (""edit"")): 31 votes
+
+According to this large majority of users who oppose defaulting VE by tomorrow,
+I hereby ask you to put VE back to opt-in for logged-in users until the most
+important bugs are fixed. Thank you.
+---",1375070446,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia","From bug 49998 comment 7:
+
+---
+the German wikipedia just started a quick poll over the weekend to at least
+postpone this activation for anonymous users on monday:
+
+https://de.wikipedia.org/wiki/Wikipedia:Umfragen/VisualEditor_Opt-in
+
+the poll has currently also a option for the previous state where VE was Opt-in
+for users instead of Opt-out if this is still possible.
+
+It would be appreciated to take the outcome on monday into account and postpone
+this activation for dewiki if desired.
+---",1375070430,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-sa6s63ajvv65ik2b7344,task_subcomment,NA
+"VisualEditor: A <nowiki> on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1374661020,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_description,resolved
+"VisualEditor: A <nowiki> on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare",Now fixed.,1375139113,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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",1375127248,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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",1374883810,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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.",1374796813,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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",1374730027,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","Change 75636 merged by jenkins-bot:
+Put <nowiki> edting in experimental for now
+
+https://gerrit.wikimedia.org/r/75636",1374683103,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> on page causes ""Uncaught RangeError: Maximum call stack size exceeded"" in oojs.compare","Change 75636 had a related patch set uploaded by Jforrester:
+Put <nowiki> edting in experimental for now
+
+https://gerrit.wikimedia.org/r/75636",1374682887,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+"VisualEditor: A <nowiki> 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 <nowiki> 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",1374661437,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-kql7loyrzdkr4rwpdcm6,task_subcomment,NA
+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",1374250680,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-shna2ollivhvhx6ukpk5,task_description,resolved
+VisualEditor: Newly-added references need a page save before being reusable,This is still the case for references added inside a table though?,1432297031,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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",1377889950,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+VisualEditor: Newly-added references need a page save before being reusable,Now fixed in master and will be deployed next week.,1377889823,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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",1377885677,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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.",1375427074,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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.",1375406536,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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.)",1375398952,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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.",1375346304,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-shna2ollivhvhx6ukpk5,task_subcomment,NA
+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",1373508480,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_description,resolved
+VisualEditor: Refactor references dialog to allow immediate insertion of reference content,This was done and deployed last week.,1374646985,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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",1374183566,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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",1374182076,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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",1374090269,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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.",1373510033,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-j5pmqk7nfjpk76iccyaa,task_subcomment,NA
+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",1373505480,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_description,resolved
+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]]",1418771598,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1418759614,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1374636985,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"**wicke** wrote:
+
+%%%*** Bug 51175 has been marked as a duplicate of this bug. ***%%%",1374270889,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373928857,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373927744,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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?",1373756996,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,*** Bug 51161 has been marked as a duplicate of this bug. ***,1373756843,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373590110,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373590022,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373561945,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373561592,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373561010,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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=""{&quot;target&quot;:{&quot;wt&quot;:&quot;echo&quot;,&quot;href&quot;:&quot;../Template:Echo&quot;},&quot;params&quot;:{&quot;1&quot;:{&quot;wt&quot;:&quot;foo&quot;}},&quot;i&quot;:0}""
+
+data-mw through VE after changing 'foo' to 'bar':
+data-mw=""{&quot;target&quot;:{&quot;wt&quot;:&quot;echo&quot;,&quot;href&quot;:&quot;../Template:Echo&quot;},&quot;params&quot;:{&quot;1&quot;:{&quot;wt&quot;:&quot;bar&quot;}}}""
+
+Note that the ""i"" member is gone.",1373555079,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,Aha. Gotcha.,1373554659,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373554601,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,"It is either data-mw.i or data-mw.parts[<n>].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 
+<body><p about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""a"":{""wt"":""foo""},""b"":{""wt"":""c""}},""i"":0}' data-parsoid='{""dsr"":[0,27,null,null],""src"":""{{echo|a   = foo\n|b   = c}}"",""pi"":[[{""k"":""a"",""spc"":["""",""   "","" "",""\n""]},{""k"":""b"",""spc"":["""",""   "","" "",""""]}]]}'>{{{1}}}</p>
+</body>",1373554563,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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.",1373554450,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace,*** Bug 51161 has been marked as a duplicate of this bug. ***,1373554368,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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?",1373507539,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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,1373505675,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ixmexwlx4wiq23ctxvjy,task_subcomment,NA
+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",1373067660,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ldrbm7zdbq6hmivijiqq,task_description,resolved
+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],1440343623,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ldrbm7zdbq6hmivijiqq,task_subcomment,NA
+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.",1373916884,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ldrbm7zdbq6hmivijiqq,task_subcomment,NA
+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",1372968840,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_description,resolved
+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",1395689849,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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",1395363046,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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.,1394036852,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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?",1394027803,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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.",1390411348,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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?",1390406910,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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. ***,1385382810,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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.",1384848197,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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. ***,1384845361,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+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. ***,1384845303,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jjb4vcjpt27hv7dg5p5g,task_subcomment,NA
+"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}",1372931040,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-b5zzf7lh657agk5cdqkw,task_description,resolved
+"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)",Merged and will hopefully go out soon.,1373053892,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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",1373049617,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1373016135,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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",1373004125,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1372969315,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1372952624,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1372952431,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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.",1372951540,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-b5zzf7lh657agk5cdqkw,task_subcomment,NA
+"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}",1372910460,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-r4klwzo7lxdsgw53zery,task_description,resolved
+"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.,1373497407,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-r4klwzo7lxdsgw53zery,task_subcomment,NA
+"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",1373497073,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r4klwzo7lxdsgw53zery,task_subcomment,NA
+"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",1373483215,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r4klwzo7lxdsgw53zery,task_subcomment,NA
+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",1372896120,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_description,resolved
+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.,1373359485,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.",1373333744,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.,1373303590,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.),1373303527,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.",1373303412,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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.",1373301240,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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",1372901309,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-i4cg3cr5ipw5q2y7rdrv,task_subcomment,NA
+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}",1372793160,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_description,duplicate
+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.",1377128046,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1374018125,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1374017295,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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?",1374016361,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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).",1373642100,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1373070573,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1373066776,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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). <B>Please be aware that wiki syntax (e.g.
+> ""[[link to another page]]"") will not work in this editing mode.</B> 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.",1373066249,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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). <B>Please be aware that wiki syntax (e.g. ""[[link to another page]]"") will not work in this editing mode.</B> 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.",1373065091,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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?",1372817358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1372801407,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1372801273,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.",1372796561,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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.,1372793189,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-6uhmvpxh7rikbtdr2wns,task_subcomment,NA
+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",1372554780,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_description,resolved
+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.",1373328432,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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",1373325377,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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. ***,1373155391,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.,1373061153,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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",1373010998,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1373010956,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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).",1373009694,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1373009612,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1372984760,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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?!",1372976195,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1372973949,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1372973401,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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. ***,1372747009,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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.",1372597774,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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}",1372597673,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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",1372596485,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+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?",1372558082,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mtdexeiuriq5cdelhc5o,task_subcomment,NA
+"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",1372520820,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_description,resolved
+"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.",1373917573,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373917479,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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.",1373780299,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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!,1373771135,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"VisualEditor: ""Invalid token"" message after period of inactivity leads to lost work",*** Bug 51302 has been marked as a duplicate of this bug. ***,1373759844,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373653678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373584937,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373584284,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373566281,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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",1373566278,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rutvvnh7fiqox2z3go4,task_subcomment,NA
+"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 <references\>, 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}",1372515720,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_description,resolved
+"VisualEditor: ref warning appears within template that contains references, post-modification",I'm forking this off into bug 51337.,1373852785,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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",1373812887,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"VisualEditor: ref warning appears within template that contains references, post-modification",Should probably leave this open to track improvements.,1373543056,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"VisualEditor: ref warning appears within template that contains references, post-modification",Also: https://gerrit.wikimedia.org/r/73096,1373543029,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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.",1373497983,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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",1373497512,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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",1373492178,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+"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.",1372690617,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pcg77ljjtbxyojrgt6ue,task_subcomment,NA
+VisualEditor: Reference toolbar icon missing in wmf9,"The references list one is still there; did Trevor's change break it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372404000,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vek6torvduvoml55paap,task_description,resolved
+VisualEditor: Reference toolbar icon missing in wmf9,Fixed with new pull.,1372442860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vek6torvduvoml55paap,task_subcomment,NA
+VisualEditor: &nbsp;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",1372385580,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-77axhndq3mqnxx2kqcjc,task_description,declined
+VisualEditor: &nbsp;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.",1373056593,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+VisualEditor: &nbsp;s converted to space characters (32s not 160s) on round-trip,Chrome Version 27.0.1453.116 on Windows 7 Home Premium.,1372412479,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+VisualEditor: &nbsp;s converted to space characters (32s not 160s) on round-trip,Will inquire.,1372386501,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+VisualEditor: &nbsp;s converted to space characters (32s not 160s) on round-trip,Do you know which browser was used for this edit?,1372386315,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+VisualEditor: &nbsp;s converted to space characters (32s not 160s) on round-trip,Odd. I can't reproduce this locally or on the article.,1372386209,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-77axhndq3mqnxx2kqcjc,task_subcomment,NA
+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",1372290900,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_description,resolved
+load.php error?  many symptoms...,Ah it seems the cached load.php got cleared finally.   I got AFT and VisualEdit working properly now :-],1372325082,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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 :(",1372324986,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+load.php error?  many symptoms...,Changes above reverts the two patches mentionned in bug 45918.,1372324616,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+load.php error?  many symptoms...,Related URL: https://gerrit.wikimedia.org/r/70806 (Gerrit Change Ie373d1f407788a8e2456c3d8a34cc79ac9ed8bb6),1372324322,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+load.php error?  many symptoms...,Related URL: https://gerrit.wikimedia.org/r/70805 (Gerrit Change I02ed22e324435e362cabdfc67e69c224ad9e2550),1372324295,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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""",1372323805,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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",1372294623,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+load.php error?  many symptoms...,"not a blocker, sorry, mw.o is a workaround",1372294116,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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.",1372293962,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-y6bkvqygqya2opqdmv3c,task_subcomment,NA
+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",1372281720,PHID-USER-kqwh3rvfxxh3wfsft7mu,True,PHID-TASK-d2rlcey47hxosbomhyfo,task_description,resolved
+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!",1372294327,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d2rlcey47hxosbomhyfo,task_subcomment,NA
+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",1372267200,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4qadhatjuo4mjlpfaic7,task_description,resolved
+VisualEditor: Be able to have enabled for all logged-in users but not anonymous users,We achieved this. Obviously. :-),1372726673,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4qadhatjuo4mjlpfaic7,task_subcomment,NA
+"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","Screenshot
+
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11809}",1372263180,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_description,resolved
+"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",1372794337,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"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",1372354311,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","Appears to be now fixed; marking as resolved. Thanks, Rob! :)",1372340043,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"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.,1372269443,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook","(Firefox 21.0, Windows 7)",1372263239,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yb6ulq67lztw2wvyk4lu,task_subcomment,NA
+"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}",1372146600,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-k6rdk2swblj7w4zhblsz,task_description,resolved
+"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.,1372379698,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+"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",1372379566,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+"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",1372361704,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+"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.,1372270138,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+"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.,1372187179,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-k6rdk2swblj7w4zhblsz,task_subcomment,NA
+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",1372115280,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-ih6vrsjge6cjapq5orey,task_description,resolved
+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.",1372266003,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+VisualEditor: Link inspector creates the text twice if not running on a selection,"Great! Thanks for the quick response, James and team!",1372265845,PHID-USER-kqwh3rvfxxh3wfsft7mu,True,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+VisualEditor: Link inspector creates the text twice if not running on a selection,Fixed and being deployed right now.,1372264523,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+VisualEditor: Link inspector creates the text twice if not running on a selection,Related URL: https://gerrit.wikimedia.org/r/70623 (Gerrit Change I8c68468a95cddbc7efb222cf3a1f9868b2949285),1372251641,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+VisualEditor: Link inspector creates the text twice if not running on a selection,*** Bug 50188 has been marked as a duplicate of this bug. ***,1372214415,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+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?,1372115781,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ih6vrsjge6cjapq5orey,task_subcomment,NA
+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",1372106580,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_description,resolved
+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.",1372704161,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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.",1372701493,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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",1372355719,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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?",1372314964,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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.",1372292154,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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.",1372291914,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+VisualEditor: Transclusions not properly round-tripped,"
+
+*** This bug has been marked as a duplicate of bug 50070 ***",1372127871,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+VisualEditor: Transclusions not properly round-tripped,The nowiki escaping in Schuylar_Oordt is Parsoid bug 50144. It would normally be hidden with selective serialization.,1372123167,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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",1372120806,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2hl7ewtzlnhd3pk5gn7t,task_subcomment,NA
+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",1372100100,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_description,resolved
+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.",1373500285,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373497930,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373494750,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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 <span>\n</span><table>...</table><link>
+* 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 <p>
+* The browser receives this HTML and is unhappy about the <table> inside the <p>, so it moves both the <table> and the <link> out of the <p>, leaving <p><span>\n</span></p><table>...</table><link>. 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 <p> 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;""",1373494553,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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,1373484409,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,*** Bug 50554 has been marked as a duplicate of this bug. ***,1373484208,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,"See also: bug 50554, bug 50385.",1373484037,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373483575,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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 <link> 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.",1373479449,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373476466,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,Possibly related: bug 50332.,1373476038,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373475508,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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 <link rel=""mw:WikiLink/Category"" href=""Category:foobar""> (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 <table> 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?",1373475152,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373440943,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.,1373439890,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373439837,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373439682,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373399973,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.,1373303777,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.",1373301012,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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",1373130413,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.,1373053343,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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.,1372360097,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,"Roan, thoughts?",1372109030,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+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,1372105662,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+Categories/default sort sometimes duplicated to random position in DOM after edit,"Perhaps related to:
+
+| PLACE OF BIRTH    =[Alexandria], [[Egypt]]",1372100226,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cl3n6ut5q64yapdxwsov,task_subcomment,NA
+VisualEditor: Link editor does not work in the reference editor in Firefox,"Self-explanatory; Firefox 21.0, Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372094820,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-fftdwlrkyjt5yc2hamtk,task_description,resolved
+VisualEditor: Link editor does not work in the reference editor in Firefox,Fixed and will be going out in a few minutes.,1372210400,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fftdwlrkyjt5yc2hamtk,task_subcomment,NA
+VisualEditor: Link editor does not work in the reference editor in Firefox,Patched in: https://gerrit.wikimedia.org/r/#/c/70559/,1372202020,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-fftdwlrkyjt5yc2hamtk,task_subcomment,NA
+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",1372089360,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-qsgca2wst2byl7ix2pwv,task_description,resolved
+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",1395689846,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+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",1395363039,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+VisualEditor: Provide way for local wikis to auto-prompt reference templates,*** Bug 51185 has been marked as a duplicate of this bug. ***,1377829415,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+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
+> <ref> tags and not about templates that add the <ref> tags themselves.
+
+Correct.",1374859109,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+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 <ref> tags and not about templates that add the <ref> tags themselves.,1374823336,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+VisualEditor: Provide way for local wikis to auto-prompt reference templates,*** Bug 51683 has been marked as a duplicate of this bug. ***,1374260100,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qsgca2wst2byl7ix2pwv,task_subcomment,NA
+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}",1372035120,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-awj25x4zsacz62adi3j5,task_description,resolved
+VisualEditor: Template-based references never editable from reference editor in Firefox,Related URL: https://gerrit.wikimedia.org/r/70119 (Gerrit Change I29e210aba9a6265d8364ff8ae49408cb4c2428b9),1372040060,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-awj25x4zsacz62adi3j5,task_subcomment,NA
+VisualEditor: Template-based references never editable from reference editor in Firefox,Confirmed by a second user.,1372035227,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-awj25x4zsacz62adi3j5,task_subcomment,NA
+"VisualEditor: If a sanity check doesn't work out, encourage the user to do a wikitext diff before saving","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372029300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-e3u3nzdde2xltny25tvr,task_description,resolved
+"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.,1372387323,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-e3u3nzdde2xltny25tvr,task_subcomment,NA
+"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",1372387308,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-e3u3nzdde2xltny25tvr,task_subcomment,NA
+"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),1372029924,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-e3u3nzdde2xltny25tvr,task_subcomment,NA
+VisualEditor: Metadata not preserved in references,"They get stripped out when rendered back to HTML.
+
+e.g.
+
+<ref>Foo<!--bar--></ref>
+
+->
+
+<ref>Foo</ref>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372007340,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ibds6gk456ofg6szjteu,task_description,resolved
+VisualEditor: Metadata not preserved in references,Related URL: https://gerrit.wikimedia.org/r/70060 (Gerrit Change I3bbea49132ef4a720a147ba9b170c39a0c00f711),1372008261,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ibds6gk456ofg6szjteu,task_subcomment,NA
+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 <b> 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",1371986880,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-yc4hfzr5ombibggchvok,task_description,resolved
+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",1372001636,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yc4hfzr5ombibggchvok,task_subcomment,NA
+"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",1371859260,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7sjurdxqyilrckxefznc,task_description,resolved
+"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.,1373053912,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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",1373049614,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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",1373039964,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1373039949,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1373035918,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1373033397,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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),1372289786,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.,1372280988,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1372264953,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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. ***,1372264868,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.",1372252282,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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.,1372173256,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-7sjurdxqyilrckxefznc,task_subcomment,NA
+"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",1371855300,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-uuaax5ooenq6lyv32r7j,task_description,resolved
+"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.",1372355114,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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",1372354202,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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),1372255145,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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 <a href=""Porcupine"">p</a><a href=""Porcupine"">orcupine</a> (adjacent <a>s with the same href) and possibly <a href=""porcupine"">p</a><a href=""Porcupine"">orcupine</a> as well (adjacent <a>s with different hrefs that normalize to the same title).",1372036243,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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.",1371982074,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+"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?",1371855415,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uuaax5ooenq6lyv32r7j,task_subcomment,NA
+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",1371684540,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_description,resolved
+mediawiki/extensions.git does not update some extensions,"Change 317923 merged by Dzahn:
+contint: remove python-requests
+
+[[https://gerrit.wikimedia.org/r/317923]]",1477523670,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]
+",1477429966,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]",1474048424,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]
+",1474047362,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]",1473409160,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]",1473361798,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1473329510,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]
+",1473329426,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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]]
+",1473329159,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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] <hashar> 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",1473329009,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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] <hashar> 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. ",1473328926,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1465398703,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Upstream bug is https://code.google.com/p/gerrit/issues/detail?id=2393,1454694024,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Same issue with `Cards` and `mediawiki/extensions/Cards` at T125182,1454594877,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1390501982,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1390341294,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1390341257,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1390334487,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1390334462,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1390332631,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389991554,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"Still failing :(
+
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-sync-gerrit/9/console",1389942210,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.,1389910865,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389909836,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389892786,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"Change 107862 merged by jenkins-bot:
+mwext-VisualEditor-sync-gerrit
+
+https://gerrit.wikimedia.org/r/107862",1389891995,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389891791,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389886128,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389885751,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389882277,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389882267,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389866906,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389866900,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389796145,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389796012,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1389795448,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389722159,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389720044,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.,1389653054,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Assigning to self and moving to CI,1389652979,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1389652459,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Re-opening rather than having a fork in bug 59758.,1389149782,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,*** Bug 59758 has been marked as a duplicate of this bug. ***,1389149751,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"happened again, see bug 59758",1389084905,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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/<foo>.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"".",1378225794,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1378204152,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,VisualEditor is finally working. I hope. I pray.,1376592201,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.,1374253962,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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'",1374232184,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1374228032,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,*** Bug 51635 has been marked as a duplicate of this bug. ***,1374228000,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,*** Bug 48893 has been marked as a duplicate of this bug. ***,1374227951,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"Change 73736 merged by Hashar:
+update VisualEditor to latest master
+
+https://gerrit.wikimedia.org/r/73736",1373881472,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1373881426,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,I hate life.,1373521899,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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 :(",1373491637,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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).",1372775601,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,"I fixed it before.
+
+Now I've fixed it once again.
+
+This is annoying.",1372695781,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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 :)",1372694917,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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
+$",1372669990,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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
+
+:-)",1371759767,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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!",1371759694,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1371759443,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+mediawiki/extensions.git does not update some extensions,Actually moving this bug under 'git/gerrit'.,1371754174,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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'.",1371722282,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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.",1371721861,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-7sbdbkrfcvaejzeycoty,task_subcomment,NA
+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",1371656400,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-j6slyvhfp3d6ozltvruk,task_description,resolved
+VisualEditor: Parsoid ate a reference,This is now fixed (Parsoid selser issue); sorry!,1371782480,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j6slyvhfp3d6ozltvruk,task_subcomment,NA
+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!",1371779509,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-j6slyvhfp3d6ozltvruk,task_subcomment,NA
+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",1371582180,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ivktalncu225io76zzys,task_description,resolved
+VisualEditor: Image insertion does not work,Fixed. Sorry about this.,1371782583,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ivktalncu225io76zzys,task_subcomment,NA
+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",1371542880,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-vm7v6vojqzplbnspgwqk,task_description,resolved
+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.",1372027620,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vm7v6vojqzplbnspgwqk,task_subcomment,NA
+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.",1371549819,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-vm7v6vojqzplbnspgwqk,task_subcomment,NA
+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",1371547249,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-vm7v6vojqzplbnspgwqk,task_subcomment,NA
+VisualEditor: Page with a <references /> block and no <ref>s throws fatal error on load,"Have a page with a <references /> block but no <ref>s and you get:
+
+| Uncaught TypeError: Cannot call method 'connect' of null 
+
+This is bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371431820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cheeem2iuszopjmd3axj,task_description,resolved
+VisualEditor: Page with a <references /> block and no <ref>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.",1371479770,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cheeem2iuszopjmd3axj,task_subcomment,NA
+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",1371265140,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_description,resolved
+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.",1417635932,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+VisualEditor: HTML comments are dropped from transclusion calls,"verified in betalabs - HTML comments are preserved both - generally and, specifically, in transclusions.",1417635694,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+VisualEditor: HTML comments are dropped from transclusion calls,"That's a separate bug, will raise as such.",1372002624,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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 :)",1371996558,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.",1371511467,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.,1371465156,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.",1371425926,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+VisualEditor: HTML comments are dropped from transclusion calls,"[[Wikipedia:VisualEditor/Feedback#Removal_of_comments_in_Infobox]]
+
+See also bug 42124.",1371424680,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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",1371424467,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.",1371420455,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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.",1371269621,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-b7q472kz3l2dnhbtziiw,task_subcomment,NA
+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",1371244680,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-2z2izcavd5te3dkswczw,task_description,resolved
+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. ***,1372002331,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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.",1371690785,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),What about commend 5 and comment 6?,1371684547,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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.",1371682009,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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:
+| <figure typeof=""mw:Image/Frame"" class="" mw-halign-right"">
+| <a rel=""mw:thumb"" href=""http://commons.wikimedia.org/wiki/File:Apples.jpg"">
+| <img src=""http://upload.wikimedia.org/wikipedia/commons/thumb/e/ee/Apples.jpg/
+|   100px-Apples.jpg"" width=""100"" height=""150"" resource=""undefined""></a></figure>
+| 
+| 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]].",1371659496,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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. ***,1371659407,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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"")",1371648653,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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:
+> <http://pt.wikipedia.org/w/index.
+> 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"".",1371640850,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+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. ***,1371627753,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),I get the same type of error: <http://pt.wikipedia.org/w/index.php?title=PLoS_ONE&diff=36119075&oldid=34872658>,1371391157,PHID-USER-vyidforzdhnrsoweujao,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"For additional examples, if that will be helpful, see:
+http://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29&diff=560023092&oldid=541758155
+
+http://en.wikipedia.org/w/index.php?title=Keshi_%28demon%29&diff=559979773&oldid=559978871",1371305701,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined'),"Roan, do we get the typeof:/etc. wrong at our end, or is this a Parsoid issue?",1371244860,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2z2izcavd5te3dkswczw,task_subcomment,NA
+VisualEditor: EventLogging gives the same pageViewSessionId for all edits,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371231960,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-myow2awxzmx4c4ssz6ta,task_description,resolved
+VisualEditor: EventLogging gives the same pageViewSessionId for all edits,Merged and we'll get this out on Monday so we can test it.,1371234407,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-myow2awxzmx4c4ssz6ta,task_subcomment,NA
+VisualEditor: EventLogging gives the same pageViewSessionId for all edits,Related URL: https://gerrit.wikimedia.org/r/68712 (Gerrit Change Iddb9eb9c64b55b25445ddf9e474d312b685978a6),1371233987,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-myow2awxzmx4c4ssz6ta,task_subcomment,NA
+VisualEditor: EventLogging gives the same pageViewSessionId for all edits,"(In reply to comment #1)
+> 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.",1371232257,PHID-USER-r7wrkcx7j2vutqs6hr3g,True,PHID-TASK-myow2awxzmx4c4ssz6ta,task_subcomment,NA
+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.",1371232111,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-myow2awxzmx4c4ssz6ta,task_subcomment,NA
+VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371231900,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-znkh7fhdepbxk6h3va36,task_description,resolved
+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.,1371234387,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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),1371233985,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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),1371233983,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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).",1371233068,PHID-USER-qb5aoo443n6fezsozhv4,True,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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. :-)",1371232172,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-znkh7fhdepbxk6h3va36,task_subcomment,NA
+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",1371213300,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_description,resolved
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,*** Bug 50049 has been marked as a duplicate of this bug. ***,1372004983,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Yes, <https://bugzilla.wikimedia.org/show_bug.cgi?id=49701>. It is apparently fixed.",1371657346,PHID-USER-vyidforzdhnrsoweujao,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,Did you open a new bug? If so could you please link it? I have someone with a similar issue.,1371652833,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Ah, sorry, I missed the tag. I think you should; this is certainly something different than what was happening here.",1371483619,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,It has the VisualEditor tag and was reported in the feedback page <http://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia%3AEditor_Visual%2FComent%C3%A1rios&diff=36129760&oldid=36054006>. Should I open a new bug?,1371482523,PHID-USER-vyidforzdhnrsoweujao,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"It's not, this bug had different symptoms, and that edit doesn't even seem to have been made using VE.",1371480754,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Not sure if this is related: <https://pt.wikipedia.org/w/index.php?title=CMM_-_Canal_Meninos_e_Meninas&diff=36129698&oldid=36129686>, but that edit was made today.",1371477080,PHID-USER-vyidforzdhnrsoweujao,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"To update, this bug was in an overly-keen Operations cacheing server configuration change which broke the caches' responses completely (and corrupted every response to not be what we want).
+
+Sorry everyone for the disruption; we've now found (and killed) this problem, and re-enabled VisualEditor as before.",1371235366,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"It looks like an update to the libraries Parsoid depends on might have caused this issue. It would have been visible in the diff, but since the user is not seeing that by default any more few noticed.
+
+Parsoid is rolled back, so this issue should be fixed.",1371223781,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"**ignatus31oct** wrote:
+
+(One more example from En-wiki) See this edit (if your traffic is easy, the diff is half-Mb):
+
+http://en.wikipedia.org/w/index.php?title=Russian_grammar&diff=559881732&oldid=558109653
+
+I only wanted to change one section, but after pressing a link everything was opened in VE. Well, I added text to different sections. There were no trouble with it, except that when I tried to type text into ''()'' italicised parentheses leaved by previous editor, when I pushed [BackSpace] at end (wrongly started to type in Cyrillic rather than Latin), first ( was doubled.
+
+When I entered enough and pushed ""Save"", I was introduced to type in the desc, and to view changes or to save page. I've just read the digest of how good is the VE now and pushed ""Save page"", but after a time I've seen.........",1371221239,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"Also note; as you can see from the gerrit change above, it looks like Ariel and James will be temporarily disabling the VE until this is solved for. I'm going to go round and notify people now :)",1371221206,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,Related URL: https://gerrit.wikimedia.org/r/68667 (Gerrit Change I267c8ba13a6ec1444010ce996fba05dfcba460fa),1371221157,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,Related URL: https://gerrit.wikimedia.org/r/68667 (Gerrit Change I267c8ba13a6ec1444010ce996fba05dfcba460fa),1371221153,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"A note; I've just spoken to James F; a fix to this is highest-priority. I'm deeply sorry about this (and think I speak for James and the VE team on that front, too).",1371220263,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,"(In reply to comment #3)
+> 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",1371219908,PHID-USER-jtxavgb3caz53o45csni,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+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",1371219726,PHID-USER-3qvsqam4jxugqg2l7qpw,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+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).,1371217642,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+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,1371215939,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+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",1371214660,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+New deployment of Parsoid leads to HTML insertion - needs deployed code reversion,*** Bug 49573 has been marked as a duplicate of this bug. ***,1371214602,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-m3novk5xasw5lqvg62ye,task_subcomment,NA
+VisualEditor: En hard-coded as TemplateData fetch language,"Should be user interface language.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1370893260,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g43ik5bj4ejp7p75b5p4,task_description,resolved
+VisualEditor: En hard-coded as TemplateData fetch language,"This is resolved in the latest version
+
+I3bcf924a3e179cb65f19e833277a39dfd3dad8bd",1370985573,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-g43ik5bj4ejp7p75b5p4,task_subcomment,NA
+"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",1370535240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-v44oexl4vlksqgaeptjm,task_description,resolved
+"VisualEditor: Move back to ""normal"" Save dialog with optional rather than mandatory Review",Fixed and will go out with wmf7 from next Thursday.,1370654365,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-v44oexl4vlksqgaeptjm,task_subcomment,NA
+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",1369387560,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r7nekr4d3omjjmecwwq6,task_description,resolved
+VisualEditor: Link corruption oddity in production on links (Parsoid issue?),I believe this is now fixed.,1372017998,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r7nekr4d3omjjmecwwq6,task_subcomment,NA
+VisualEditor: Link corruption oddity in production on links (Parsoid issue?),Can't reproduce in master.,1369389553,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-r7nekr4d3omjjmecwwq6,task_subcomment,NA
+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",1368667200,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5refjnnnoyqumq4ge53g,task_description,resolved
+VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox,This is not an issue anymore.,1371602123,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-5refjnnnoyqumq4ge53g,task_subcomment,NA
+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",1368622500,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-glwrzzfq4ph2os2n2f6r,task_description,resolved
+VisualEditor: [Regression] Link inspector button doesn't work,Merged into master; will go out with wmf5.,1368638702,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-glwrzzfq4ph2os2n2f6r,task_subcomment,NA
+VisualEditor: [Regression] Link inspector button doesn't work,Related URL: https://gerrit.wikimedia.org/r/63850 (Gerrit Change Icda3305e422bedaf0d490b8fbe51f55b8c8e79e8),1368626182,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-glwrzzfq4ph2os2n2f6r,task_subcomment,NA
+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?)",1368625612,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-glwrzzfq4ph2os2n2f6r,task_subcomment,NA
+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",1368561900,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-52eneev7kw444gspkrww,task_description,resolved
+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.",1371142270,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-52eneev7kw444gspkrww,task_subcomment,NA
+VisualEditor: Pawn appears when creating new list item in Firefox,@Quim: Are you still able to reproduce this problem? I can't.,1371073013,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-52eneev7kw444gspkrww,task_subcomment,NA
+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?",1370177174,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-52eneev7kw444gspkrww,task_subcomment,NA
+VisualEditor: Indenting & unindenting multiple list items fails,"Problems in IndentationAction that Ed it working on right now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1368392940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r45sjfea3cr6rhagxvom,task_description,resolved
+VisualEditor: Indenting & unindenting multiple list items fails,Code is merged into wmf4.,1368471026,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+VisualEditor: Indenting & unindenting multiple list items fails,Related URL: https://gerrit.wikimedia.org/r/63485 (Gerrit Change I5ce0c385214f30c5e5c66b5b5b755c9937267cd0),1368466116,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+VisualEditor: Indenting & unindenting multiple list items fails,*** Bug 48069 has been marked as a duplicate of this bug. ***,1368465449,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+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.",1368465399,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+VisualEditor: Indenting & unindenting multiple list items fails,Fixed by https://gerrit.wikimedia.org/r/#/c/63394/,1368393902,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-r45sjfea3cr6rhagxvom,task_subcomment,NA
+VisualEditor: [Regression] Lists badly broken again,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1368386340,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-iowbxqgcysomfeaijbgp,task_description,resolved
+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",1384458232,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+VisualEditor: [Regression] Lists badly broken again,Fixed in https://gerrit.wikimedia.org/r/63413. Will close after it gets merged.,1368428040,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+VisualEditor: [Regression] Lists badly broken again,Related URL: https://gerrit.wikimedia.org/r/63413 (Gerrit Change I8d7aeffc8166487806e3489b054f508c5e9418ff),1368427993,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+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.",1368388912,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+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",1368386572,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-iowbxqgcysomfeaijbgp,task_subcomment,NA
+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 <br> has appeared from nowhere:
+  <p><br><span slug></span></p>
+
+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",1368384600,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vv7dhxcel5yesltb4ctu,task_description,resolved
+VisualEditor: Delete contents of slugged paragraph results in double line break visible,This is fixed with my refactor to handleDelete method.,1372369906,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-vv7dhxcel5yesltb4ctu,task_subcomment,NA
+VisualEditor: Delete contents of slugged paragraph results in double line break visible,Deeming that this is now fixed.,1371781383,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vv7dhxcel5yesltb4ctu,task_subcomment,NA
+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.",1371520995,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vv7dhxcel5yesltb4ctu,task_subcomment,NA
+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.",1371072856,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-vv7dhxcel5yesltb4ctu,task_subcomment,NA
+"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",1368250320,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_description,resolved
+"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.",1384457027,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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.,1368498108,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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!",1368390197,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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.",1368390088,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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?",1368379669,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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?",1368303523,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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",1368255099,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption",Confirmed in Safari and Chrome as well.,1368252786,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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",1368251518,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+"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",1368251303,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-icuv2sbiyqbhbfbwtar6,task_subcomment,NA
+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",1368089940,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-bxvvumd26q44ufzm7ua5,task_description,resolved
+VisualEditor: Aborted empty list creates a pawn,Merged into master; will be deployed from Monday.,1368206349,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+VisualEditor: Aborted empty list creates a pawn,"(In reply to comment #3)
+> Related URL: https://gerrit.wikimedia.org/r/63102 (Gerrit Change
+> If22d9b904b8861e24d56944d791545635b2e4254)
+
+Merged.",1368206273,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+VisualEditor: Aborted empty list creates a pawn,Related URL: https://gerrit.wikimedia.org/r/63102 (Gerrit Change If22d9b904b8861e24d56944d791545635b2e4254),1368148455,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+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 <li> (return at the end of the list) it doesn't check that the <ul> is empty, so you get a node inside the <ul>.
+
+Note that in casual testing this 'worked', because backspace deletes the pawn and <ul> together. Bother.",1368126833,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+VisualEditor: Aborted empty list creates a pawn,Same when entering text instead of Delete,1368090135,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-bxvvumd26q44ufzm7ua5,task_subcomment,NA
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
+Put the cursor somewhere in the text.
+Type ""Enter"" 2 times.
+Type ""Up"".
+Type ""Delete"".
+Click Bullet List
+Type q
+Type Left
+Type Enter
+Type Up
+Type Delete
+
+Wild pawn appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368089760,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-beabkw6yw7remnijbvdm,task_description,resolved
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"(In reply to comment #3)
+> James, do you mean the pawn does not appear for you?
+> I tried just now on wikipedia.org, the pawn appears.
+> Please note that the correct instructions are those in Comment 1.
+> 
+> Ubuntu 2012.10, Firefox 20.0
+
+I didn't say it doesn't appear in production, I said it doesn't appear in master; had I been unable to reproduce, I would have said. :-)
+
+I think this is fixed through changes made in master but not deployed, but bug 47795 appears to have broken itself; I'll close this and mark that as re-opened.",1368211364,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-beabkw6yw7remnijbvdm,task_subcomment,NA
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"James, do you mean the pawn does not appear for you?
+I tried just now on wikipedia.org, the pawn appears.
+Please note that the correct instructions are those in Comment 1.
+
+Ubuntu 2012.10, Firefox 20.0",1368153322,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-beabkw6yw7remnijbvdm,task_subcomment,NA
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"I can reproduce bug 47795 in master in Firefox, but not the pawn issue; all works in Chrome, as normal.",1368126046,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-beabkw6yw7remnijbvdm,task_subcomment,NA
+VisualEditor: Delete on empty first item of list -> pawn in Firefox,"Sorry, ignore the first Delete step above.
+
+Steps should read:
+
+Type ""Enter"" 2 times.
+Type ""Up"".
+Click Bullet List
+Type q
+Type Left
+Type Enter
+Type Up
+Type Delete",1368089888,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-beabkw6yw7remnijbvdm,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"1. Open http://en.wikipedia.org/wiki/Enterprise_content_management
+2. Add a space and remove it
+3. Press ""Review and Save""
+4. Wait forever.
+
+The text stays greyed out and nothing changes. Changes can't be saved.
+Same for any article I tried.
+
+Ubuntu 2012.10, Firefox 20.0
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1367893860,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-32fs65piddaapoc5z4hg,task_description,resolved
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"
+
+*** This bug has been marked as a duplicate of bug 48181 ***",1368023940,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],Bug is gone indeed.,1368018208,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],Can't reproduce in Chrome or FF. I see other bugs (which I think have been filed elsewhere) but nothing that stops me from reviewing.,1368018032,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"Ed, marking this as immediate for when you wake.",1367895324,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],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,1367894800,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"Uncaught Error: toDomElements() failed to return an array when converting element of type alienBlock load.php:4092
+> ve.dm.Converter.getDomElementsFromDataElement load.php:4092
+> ve.dm.Converter.getDomSubtreeFromData load.php:4629
+> ve.dm.Converter.getDomFromData load.php:4444
+> ve.init.mw.ViewPageTarget.swapSaveDialog load.php:101
+> ve.init.mw.ViewPageTarget.showSaveDialog load.php:99
+> ve.init.mw.ViewPageTarget.onToolbarSaveButtonClick load.php:87
+> proxy load.php:10
+> ve.EventEmitter.emit load.php:11
+> ve.ui.ButtonWidget.onClick load.php:8696
+> proxy load.php:10
+> jQuery.event.dispatch load.php:45
+> elemData.handle.eventHandle",1367894666,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],"(In reply to comment #0)
+> 1. Open http://en.wikipedia.org/wiki/Enterprise_content_management
+> 2. Add a space and remove it
+> 3. Press ""Review and Save""
+> 4. Wait forever.
+> 
+> The text stays greyed out and nothing changes. Changes can't be saved.
+> Same for any article I tried.
+> 
+> Ubuntu 2012.10, Firefox 20.0
+
+Confirmed on Firefox 20, Mac OS X.",1367894611,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]],What does the console error log say?,1367893927,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-32fs65piddaapoc5z4hg,task_subcomment,NA
+VisualEditor: Indenting multiple list items now broken in Firefox,"Multiple list items don't indent properly.
+
+Steps to duplicate the bug:
+
+Write a couple of lines. Mark all the lines and click the ""list"" button - producing bullet-list. 
+
+If the indent button is clicked when the cursor is on a single list item, that item will be indented. However, if you mark a couple of list items and indent them at once, the indentation is jumbled: some of the items are indented and some double-indented (and the item above the selection seems to be indented as well)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367650560,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-cilebqon5xuldg2g3esr,task_description,resolved
+VisualEditor: Indenting multiple list items now broken in Firefox,"
+
+*** This bug has been marked as a duplicate of bug 48390 ***",1368465449,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cilebqon5xuldg2g3esr,task_subcomment,NA
+VisualEditor: Indenting multiple list items now broken in Firefox,"I am entirely not sure if I am in the right direction here, but I figured I'd share my intuition --
+
+I am thinking this is some bug with the definition of child-nodes vs same-level nodes, which results in indentation as if some of the nodes selected are parents.
+
+There was a change in ve.ce.BranchNode.js and ve.ce.ContentBranchNode.js regarding child nodes -- could this have caused it?
+
+
++ve.ce.BranchNode.prototype.onModelUpdate = function ( transaction ) {
++       this.emit( 'childUpdate', transaction );
+
+And there are a couple of other changes in the ve.ce.BranchNode.prototype.onSplice method. Perhaps something went wrong with the definition of what is a child and what is a same-level node, which then jumbles up the hierarchy of the list?
+
+(I do hope I am in the right direction here, I thought I'd share my thoughts)",1367694128,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-cilebqon5xuldg2g3esr,task_subcomment,NA
+VisualEditor: Indenting multiple list items now broken in Firefox,Broken in master for Firefox but not in wmf3 - presumably we changed something in the last week that did this?,1367692978,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cilebqon5xuldg2g3esr,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox","*that* was an amusing bug to find.
+
+Tested on mediawiki.org.
+
+Steps:
+
+1. Write text in an ordered list item
+2. Select some of the text
+3. Hit ""end""
+
+Expected:
+
+Cursor at end of line
+
+Actual:
+
+Cursor at end of line, text gone
+
+I would *suspect* this is an easy bug, unmark it if it's not.
+
+Found bug on Firefox 23 alpha 1
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367530560,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-kcoehi5bluofxq2bsd4i,task_description,resolved
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",*** Bug 48288 has been marked as a duplicate of this bug. ***,1369093388,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",https://gerrit.wikimedia.org/r/63223 (Gerrit Change I7a8d6c474ecca5af02b72b6453c900ed61acea58) | change APPROVED and MERGED [by jenkins-bot],1368221634,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",Related URL: https://gerrit.wikimedia.org/r/63223 (Gerrit Change I7a8d6c474ecca5af02b72b6453c900ed61acea58),1368219098,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",*** Bug 48039 has been marked as a duplicate of this bug. ***,1367600124,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+"VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox",Whoops. :-),1367545406,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kcoehi5bluofxq2bsd4i,task_subcomment,NA
+VisualEditor: VE sometimes posting to the wrong API when serializing wikitext?,"See Parsoid bug 47998.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1367509980,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-5wvor46u2dd3dffehhqn,task_description,invalid
+VisualEditor: VE sometimes posting to the wrong API when serializing wikitext?,"As far as we can tell, this isn't reproducible in live, so I'm marking as INVALID; happy to re-open if we see this happen in the wild.",1368216302,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5wvor46u2dd3dffehhqn,task_subcomment,NA
+VisualEditor: VE sometimes posting to the wrong API when serializing wikitext?,"Argh, a mess - Roan, could you investigate?",1367510099,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5wvor46u2dd3dffehhqn,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,"Steps to reproduce problem:
+1. Edit https://www.mediawiki.org/wiki/Git/Commit_message_guidelines in VisualEditor
+2. Add some text
+3. ""Review and save""
+4. ""Something is wrong""
+5. ""Report problem""
+
+Expected behaviour:
+Make an http request somewhere and report back in the UI.
+
+Actual behaviour:
+No http request is made and UI is unresponsive.
+
+console:
+> Uncaught TypeError: Converting circular structure to JSON
+> at:
+> > mw.Target.prototype.reportProblem = function(message) {
+> > var ...., report = { title: .., oldid: .., .. };
+> > $.post(mw.config.get('wgVisualEditorConfig').reportProblemURL, {'data': JSON.stringify(report)}, function() {
+
+debug:
+
+var objs = [];
+JSON.stringify(a, function (k, v) {
+  var i;
+  if (v === Object(v)) {
+    i = objs.indexOf(v);
+    if (i !== -1) {
+      console.log('dupe at #' + i, v);
+    }
+    objs.push(v);
+  }
+  return v;
+});
+dupe at #66 
+<p data-parsoid=​""{""dsr"":​[0,139,0,0]​}​"">​
+""The ""
+<b data-parsoid=​""{""tsr"":​[4,7]​,""dsr"":​[4,24,3,3]​}​"">​commit message​</b>​
+"" play an important role in revision control systems. They are the first thing other people will see of your commit.""
+</p>​
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1367434260,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dt7csod4a2evm53mkmur,task_description,resolved
+VisualEditor: JSON.stringify won't work if data contains DOM elements,Fixed in master.,1368038305,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,"Ah, because native DOM element objects have all kinds of ""convenience"" pointers like ""firstChild"", ""children"", ""nextSibling"", ""paretNode"", ""ownerDocument"", which all have the same as well, so its like a circular reference nightmare.",1368030444,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,Related URL: https://gerrit.wikimedia.org/r/62811 (Gerrit Change Id807ccc6ff31d063be815ed4988cb35684adb76a),1368020696,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,This is caused by the linear data now contain DOM elements in alien nodes (and other nodes that store original HTML). We will need to pre-process the data before serialising. We already do this in the unit tests so shouldn't be too difficult.,1368019429,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: JSON.stringify won't work if data contains DOM elements,"@Ed: I suspect the circular reference is coming from inside the data model. Can you look into this?
+
+See ve.init.mw.Target.js, method #reportProblem.",1367860376,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dt7csod4a2evm53mkmur,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,"Currently we don't alert users that they're outing their IP when they save. This is a Bad Thing(tm).
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1367266320,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bkkyo5d2dquufftw2sz,task_description,resolved
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,I see - wan't looking at main namespace.,1367604012,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,Merged and will go out with wmf4.,1367602898,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,"(In reply to comment #4)
+> mediawiki.org? I don't see it there.
+
+Compare https://www.mediawiki.org/w/index.php?title=MediaWiki_1.21&action=edit with https://www.mediawiki.org/wiki/MediaWiki_1.21?veaction=edit in an isolated browser (e.g. Chrome Incognito).",1367599367,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,mediawiki.org? I don't see it there.,1367598917,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,"(In reply to comment #2)
+> Currently the extension doesn't let anon editors use it at all (
+> $skin->getUser()->getOption( 'visualeditor-enable' ) is required ), but I've
+> put in a fix for when we do.
+
+Except for mediawikiwiki, where it's forced on for everyone, logged in or out, regardless of preference. :-)",1367594947,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,"Currently the extension doesn't let anon editors use it at all ( $skin->getUser()->getOption( 'visualeditor-enable' ) is required ), but I've put in a fix for when we do.",1367577948,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box,Related URL: https://gerrit.wikimedia.org/r/62143 (Gerrit Change Ib5c3284c646ebcc0a8cad0b02de559d7820e05a0),1367577674,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5bkkyo5d2dquufftw2sz,task_subcomment,NA
+VisualEditor: Editing lists results in PILE_OF_POO symbol ;),"1. Edit a page with an unordered list.
+
+2. Delete all the text on the last line.
+
+3. Press the <delete key>. The bullet should be erased.  Instead, it will
+remain and the cursor will move to the end of the previous line.
+
+4. down-arrow
+
+5. down-arrow off of the empty line.
+
+Turd appears in the empty line.
+
+Very many arrow-key actions will produce the turd.
+
+Firefox 20.0, linux.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367217060,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-dciqnjw7tyxyl2dkeuls,task_description,resolved
+VisualEditor: Editing lists results in PILE_OF_POO symbol ;),"Actually those are two separated issues. One is about turds appearing and the other one is about bullet not being erased. So in my previous comment I referred to the first issue, and second issue is something that I'm working on now (as a part of broader refactoring to handle deletion operations).",1367281537,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-dciqnjw7tyxyl2dkeuls,task_subcomment,NA
+VisualEditor: Editing lists results in PILE_OF_POO symbol ;),I believe that this is fixed in master: https://gerrit.wikimedia.org/r/#/c/61055/,1367281446,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-dciqnjw7tyxyl2dkeuls,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,"jQuery have WONTFIX'ed this bug (13821) so we'll have to work around.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+http://bugs.jquery.com/ticket/13821",1366992360,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_description,resolved
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,"(In reply to comment #5)
+> (In reply to comment #0)
+> > jQuery have WONTFIX'ed this bug (13821) so we'll have to work around.
+> 
+> Any link? http://bugs.jquery.com/report/13821 returns error.
+
+http://bugs.jquery.com/ticket/13821 (in the see also field).",1367595136,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,"Another place we had to work around:
+https://gerrit.wikimedia.org/r/#/c/62028/",1367577189,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,"(In reply to comment #0)
+> jQuery have WONTFIX'ed this bug (13821) so we'll have to work around.
+
+Any link? http://bugs.jquery.com/report/13821 returns error.",1367562927,PHID-USER-zjzhrhmn36icnzbckqy4,True,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,*** Bug 47860 has been marked as a duplicate of this bug. ***,1367545048,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,Ed's code is merged and will be going out with the regular deployment train on Monday.,1367097148,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,Related URL: https://gerrit.wikimedia.org/r/61180 (Gerrit Change I3df8f49b170c31da9610129d53cf8cb65dd5d5f8),1367066588,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest,*** Bug 47712 has been marked as a duplicate of this bug. ***,1366992520,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bwy7gci6gdsa3r3m24i,task_subcomment,NA
+VisualEditor: Saved annotated content cannot be unannotated,"This has reappeared (in live on hewiki and others) - if the page on load has bold annotation on some text, pressing the ""bold"" button doesn't remove bold but adds a second bold annotation (which can be removed, but not in a way that stops the text being bold).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366932000,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b7yvvcuza7umneartpgv,task_description,resolved
+VisualEditor: Saved annotated content cannot be unannotated,Merged and deployed.,1366937647,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b7yvvcuza7umneartpgv,task_subcomment,NA
+VisualEditor: Saved annotated content cannot be unannotated,Roan fixing now.,1366934154,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b7yvvcuza7umneartpgv,task_subcomment,NA
+VisualEditor: Saved annotated content cannot be unannotated,Related URL: https://gerrit.wikimedia.org/r/60948 (Gerrit Change I77f00e63c8732420063b0453fede7f453083c913),1366934093,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-b7yvvcuza7umneartpgv,task_subcomment,NA
+VisualEditor: Link inspector crashes when trying to annotate first character in the document,"Make a selection that includes the first character, and press the access key for creating a link (Ctrl+K?). You'll get a JS error.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366853220,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-67bjy5it2mluh5artfn6,task_description,resolved
+VisualEditor: Link inspector crashes when trying to annotate first character in the document,Mysteriously works upon updating to the current HEAD.,1367880698,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-67bjy5it2mluh5artfn6,task_subcomment,NA
+VisualEditor: Link inspector crashes when trying to annotate first character in the document,"I wanted to check this out, and I noticed that this fails (I reproduced the error) in Chrome and Firefox 20.x in Windows, but it works perfectly (no crash on first character) in my Firefox 20.x in Ubuntu.
+
+Also, if it helps, here's the error I'm getting on Firebug:
+
+Error: Error in Rangy Position module: Cannot get position for range [WrappedRange(<P>[4][<a href=""sdjfh"" titl]:0, <P>[4][<a href=""sdjfh"" titl]:0)]
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Crangy%7Cunicodejs.wordbreak&skin=vector&version=20130505T030747Z&*
+Line 224
+
+It seems it has something to do with the wordbreaks (??). Can there be a difference in wordbreaks that are used at the beginning of a document/paragraph between Linux and Windows? (Like ther'es a difference in endofline chars and whitespaces) ?
+
+Not sure if it helps, but here's for sharing.",1367812636,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-67bjy5it2mluh5artfn6,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,"As the title says. The bug seems to be in postHTML:
+
+array(
+        'postData' => array( 'content' => $html ),
+        'timeout' => $wgVisualEditorParsoidTimeout,
+        'oldid' => $parserParams['oldid']
+)
+
+
+should be:
+
+array(
+        'postData' => array( 'content' => $html, 
+                             'oldid' =>  $parserParams['oldid']),
+        'timeout' => $wgVisualEditorParsoidTimeout
+)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366408980,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-uw2enw4anj5qqfz3lyei,task_description,resolved
+VisualEditor: No oldid is sent on POST to Parsoid,*** Bug 47498 has been marked as a duplicate of this bug. ***,1366641916,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,Merged; to go out in next push as a critical priority.,1366641892,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,Related URL: https://gerrit.wikimedia.org/r/60082 (Gerrit Change Ib1b7079a7fd3357903e5a14795ed0d2f2bdc5d16),1366409690,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,Verified that this fixes the problem and lets Parsoid actually use selective serialization. Current production code does not use selective serialization for this reason.,1366409237,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+VisualEditor: No oldid is sent on POST to Parsoid,This would explain a great deal. :-),1366409214,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uw2enw4anj5qqfz3lyei,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use","The link tool showing ""undefined"" in step 5 of the bug report
+
+1. Hit an article on English Wikipedia and click ""Edit"" to invoke Visual Editor. I used http://en.wikipedia.org/wiki/Savage%2C_Montana.
+
+2. Double-click any word to highlight it. I used the first word of the ""History"" section, ""Savage"".
+
+3. Click the Link Tool icon, and the tool pops up.
+
+4. Choose any article title in the dropdown (I chose ""Savage Land"") and press Enter.
+
+5. The dropdown closes, and in the tool's text input, instead of saying ""Savage Land,"" it says ""undefined."" (See screenshot to be uploaded.)
+
+6. Now click outside the tool -- somewhere else on the article. The tool becomes completely blank (see second screenshot) and article text disappears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F10425}",1366381800,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_description,resolved
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",Now fixed by gerrit 60907 - thanks Trevor!,1366919875,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",Seemingly not fixed at all - still broken in master/production with same behaviour as before.,1366918173,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",Now merged and going out tomorrow.,1366854691,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",Related URL: https://gerrit.wikimedia.org/r/60781 (Gerrit Change I286a28002c1691e58bbd7de04ed08cceb8b3bb07),1366852733,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",*** Bug 47546 has been marked as a duplicate of this bug. ***,1366741802,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use","Same for me.
+
+In addition to Dan's step 6, i note that after step 6 I see: ""TypeError: 'undefined' is not an object (evaluating 'dataElement.attributes.title')""",1366464797,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use","Confirmed in Chrome/Mac, Firefox/Mac and Firefox/Linux. Looks like a general critical issue.",1366387816,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use",This is in Chrome 25.0.1364.172 on Ubuntu Linux.,1366381926,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+"[Regression] VisualEditor: Link tool produces ""undefined"" in normal use","Created attachment 12146
+The link tool going completely blank, and the article text behind it disappearing, as in step 6 of the bug report.
+
+**Attached**: {F10426}",1366381880,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-2kjxh5erw27qfzcnj2zn,task_subcomment,NA
+Master broken (jsduck),"Master is failing jenkins tests right now due to some JSDuck failures.
+
+Examples: https://gerrit.wikimedia.org/49364 , https://gerrit.wikimedia.org/r/57922
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: blocker",1365447240,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-exzifkfq2psfgq3kiwzv,task_description,resolved
+Master broken (jsduck),Original patch has been resubmitted by Roan with https://gerrit.wikimedia.org/r/#/c/58134/ . That new version passed the JSDuck job \O/,1365454559,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),"Changed merged by Jenkins, so that definitely fixed the issue :-]",1365449081,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),"(In reply to comment #3)
+> Maybe the V+2 and submit rights should be taken away from human users for
+> core?
+> We did this in VisualEditor a few months ago.
+
++10, best idea ever",1365448352,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),Maybe the V+2 and submit rights should be taken away from human users for core? We did this in VisualEditor a few months ago.,1365448120,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),"Most probably caused by https://gerrit.wikimedia.org/r/#/c/56637/ that has been force merged.
+
+Revert is https://gerrit.wikimedia.org/r/#/c/58131/",1365447919,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+Master broken (jsduck),Related URL: https://gerrit.wikimedia.org/r/58131 (Gerrit Change I2d945b7ffb7cfbcc5024a1c3bdcf0c9506b0cf76),1365447873,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-exzifkfq2psfgq3kiwzv,task_subcomment,NA
+"VisualEditor: Switch integration for deployed wikis from tabLayout ""add"" to ""replace"" mode","In preparation for making the VisualEditor the ""default"" editor, we should have the existing integration switched over for users so that they can see, test and feedback on the final UX for triggering edits in the run-up to switch-over.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1365032940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gngjvjs5g5d7kc4osh37,task_description,resolved
+"VisualEditor: Switch integration for deployed wikis from tabLayout ""add"" to ""replace"" mode",Now merged.,1366320602,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gngjvjs5g5d7kc4osh37,task_subcomment,NA
+"VisualEditor: Switch integration for deployed wikis from tabLayout ""add"" to ""replace"" mode","See https://gerrit.wikimedia.org/r/59557 , https://gerrit.wikimedia.org/r/59558",1366156038,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-gngjvjs5g5d7kc4osh37,task_subcomment,NA
+Jenkins merged a faulty change,"Aaron Schulz wrote:
+
+I noticed that https://gerrit.wikimedia.org/r/#/c/33971/ passed the tests but after it was merged, the new tests started failing for everything. The commit to revert it also failed so I override Jenkins and merged anyway, and the failures went away for new commits. This indicates that something broken is going, possibly Jenkins running tests just against master rather than master + the patch, which would explain this problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364653620,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_description,resolved
+Jenkins merged a faulty change,"Change 117045 merged by jenkins-bot:
+Parsoid: uses ZUUL_COMMIT as a git refspec to build
+
+https://gerrit.wikimedia.org/r/117045",1394446468,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Change 117045 had a related patch set uploaded by Hashar:
+Parsoid: uses ZUUL_COMMIT as a git refspec to build
+
+https://gerrit.wikimedia.org/r/117045",1394053460,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,I have verified the jobs triggered over the past few days. Seems to work fine now :-)  The root cause was using ZUUL_BRANCH as a branch specifier instead of ZUUL_COMMIT.,1366463506,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"hashar@gallium:~$ ./checkbug46723.py mediawiki-core-phpunit-api --filter 2013-04-16*
+Found 0 mismatches in 29 log files.
+hashar@gallium:~$ ./checkbug46723.py mediawiki-core-phpunit-misc --filter 2013-04-16*
+Found 0 mismatches in 29 log files.
+$
+
+Seems it got fixed :-]  Will verify again during the week, but so far that looks good.",1366117226,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,Will monitor over the next few days. Lowering priority for now.,1366023198,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"https://gerrit.wikimedia.org/r/#/c/58865/ has been deployed.
+
+I am now manually updating the jobs which are not under JJB:
+
+analytics-libanon
+analytics-udp-filters
+analytics-webstatscollector
+analytics-wikistats
+mwext-PoolCounter-pep8
+mwext-VisualEditor-docgen
+operations-debs-python-voluptuous-debbuild
+parsoid-parse-tool-check
+parsoid-roundtrip-test-check
+parsoid-runTests
+test-mediawiki-merge",1366022481,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,https://gerrit.wikimedia.org/r/58865 (Gerrit Change Iafebfffe480886fc8956e56517291b1b3b1fc0cc) | change APPROVED and MERGED [by Hashar],1366022447,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,*** Bug 47208 has been marked as a duplicate of this bug. ***,1365939442,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"(In reply to comment #13)
+> Related URL: https://gerrit.wikimedia.org/r/58865 (Gerrit Change
+> Iafebfffe480886fc8956e56517291b1b3b1fc0cc)
+
+Why is this comment duplicated?",1365759643,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"I have updated mediawiki-core-whitespaces job to use ZUUL_COMMIT as a refspec specifier. The job is non voting so that is not going to do any harm.
+
+The experimental change is https://gerrit.wikimedia.org/r/58865",1365759586,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,Related URL: https://gerrit.wikimedia.org/r/58865 (Gerrit Change Iafebfffe480886fc8956e56517291b1b3b1fc0cc),1365759515,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,Related URL: https://gerrit.wikimedia.org/r/58865 (Gerrit Change Iafebfffe480886fc8956e56517291b1b3b1fc0cc),1365759512,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"The branch specifier in the git plugin is set to ZUUL_BRANCH which is 'master'. 
+
+In the git plugin (at git-plugin/src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java ), the getCandidateRevisions() will recognize whether the branch looks like a sha1 (if it matches /[0-9a-f]{6,40}/) and in such a case will create a detached branch using that commit.
+
+Seems the Jenkins job macro should then use ZUUL_COMMIT as a branch specifier.",1365758998,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"ZUUL_COMMIT=76cb37f0c69dcd69884fc6e66681e77c8045a08e
+
+but it fetched origin/master instead :-(",1365717544,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Created attachment 12084
+Console output for https://integration.wikimedia.org/ci/job/mediawiki-core-phpunit-parser/5386/console
+
+**Attached**: {F10684}",1365717500,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,We are lacking the git plugin verbose mode in production due to a bug. It is corrected with https://gerrit.wikimedia.org/r/58489  . That will help find out what the plugin is doing internally.,1365595161,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"I have traced the issue as far as mediawiki-core-lint build #19 from made on November 22nd 2012).
+
+
+MISMATCH in /var/lib/jenkins/jobs/mediawiki-core-lint/builds/19/log
+Pipeline: gate
+Zuulcommit: 76606b66b006ac0e62087e6d00b1e4bdd56fff09
+Checkedout: 232e34733fc68739ba96cccc31d3ff88f9484a23",1365590692,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Extract for the two builds referenced somewhere above:
+
+Verifying /var/lib/jenkins/jobs/mediawiki-core-phpunit-misc/builds/5222/log
+Zuulcommit: 8cc0b601aa2db6db09ac0e4d70847293d75875aa
+Checkedout: 8cc0b601aa2db6db09ac0e4d70847293d75875aa
+Verifying /var/lib/jenkins/jobs/mediawiki-core-phpunit-misc/builds/5223/log
+Zuulcommit: 7dd3356a51951f8cdfe463552b5e5aae272e8e60
+Checkedout: 4c69569db71d149feff6c4b10ea7a493425d67fd (MISMATCH)
+
+
+We can see that build 5223 did not used the proper commit :-]
+
+
+I suspect git plugin does not fetch the proper references / can't find it. That result internally in an unknown sha1 and then git plugin fallback to master or something else.
+
+I will try to reproduce the issue in labs with git plugin set to verbose. That needs to start Jenkins with -Dhudson.plugins.git.GitSCM.verbose=true",1365542339,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Created attachment 12066
+output of checkbug46723.py
+
+The result script output highlight that some builds are not testing what they should be testing because they check out a parent commit.  By looking at the Jenkins Git plugin source code, it seems that whenever the reference is not parseable (aka: git rev-parse $ZUUL_REF), the plugin fallback to use master or some parent commit.
+
+I need to improve the script to find out if that happens in a specific pipeline or for some specific refs.
+
+**Attached**: {F10683}",1365541824,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"Created attachment 12065
+python script parsing build logs to find Zuul commit vs Git plugin checkout
+
+**Attached**: {F10682}",1365541532,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"build #5223 
+
+
+Workspace did get wiped:
+ 02:46:53 Wiping out workspace first.
+
+It check out the revision:
+ 02:46:56 Checking out Revision 4c69569db71d149feff6c4b10ea7a493425d67fd (origin/master)
+
+That is the master revision NOT the change. The commit should have been
+7dd3356a51951f8cdfe463552b5e5aae272e8e60
+
+----
+
+The related merge job
+https://integration.wikimedia.org/ci/job/mediawiki-core-merge/11333/console
+
+02:44:17 Commencing build of Revision 7dd3356a51951f8cdfe463552b5e5aae272e8e60 (origin/master)
+02:44:17 Checking out Revision 7dd3356a51951f8cdfe463552b5e5aae272e8e60 (origin/master)
+
+----
+
+The ZUUL_REF has probably not been resolved properly and the git plugin fallback to master.
+
+There is also the possibility that the mediawiki-core-phpunit-misc job was using ZUUL_COMMIT as a refspec instead of ZUUL_REF. That might prevent the plugin from fetching the revision.   The job history is no more accessible due to an unexpected upgrade (see bug 47040).",1365514200,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,"From bug 47031 : https://gerrit.wikimedia.org/r/#/c/57436/ has been merged although it is faulty.
+
+The unit tests ran on patchset upload did catch the issue:
+
+https://integration.wikimedia.org/ci/job/mediawiki-core-phpunit-misc/5222/console : FAILURE
+
+But the gating run after CR+2 did not catch it:
+
+https://integration.wikimedia.org/ci/job/mediawiki-core-phpunit-misc/5223/console : SUCCESS
+
+
+The root cause is that despite the ZUUL_REF points to the proper merge commit, the Jenkins Git plugin seems to use the current origin/master to build.",1365497215,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+Jenkins merged a faulty change,Related URL: https://gerrit.wikimedia.org/r/58283 (Gerrit Change I4b3fadccaae9c35964a0c47d63b22c4f35148a24),1365495617,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tud4ia4bietz5pnf4dyz,task_subcomment,NA
+VisualEditor: Leaving a link while the inspector is open can remove the link,"0. Open a document with links already in it.
+1. Click on a MediaWiki link, then click the icon to open the inspector.
+2. Click anywhere else in the document to lose focus.
+3. You're link has now been removed :(
+
+Note that this doesn't happen if you have just created a link, or if you have edited a link, so I assume this is functionality for letting people abandon the creation of a link.
+
+The only way to remove a link should be with the delete icon in the inspector, or clear formatting.
+
+This doesn't appear to affect external links.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363095900,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rl3v4wnjsqhxlyzhy4r4,task_description,resolved
+VisualEditor: Leaving a link while the inspector is open can remove the link,*** Bug 46505 has been marked as a duplicate of this bug. ***,1364164432,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rl3v4wnjsqhxlyzhy4r4,task_subcomment,NA
+VisualEditor: Leaving a link while the inspector is open can remove the link,Code now merged.,1363139966,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rl3v4wnjsqhxlyzhy4r4,task_subcomment,NA
+VisualEditor: Leaving a link while the inspector is open can remove the link,https://gerrit.wikimedia.org/r/53488,1363132183,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-rl3v4wnjsqhxlyzhy4r4,task_subcomment,NA
+VisualEditor: Node API re-write,"The re-write of the node API that dm provide up to the rest of VE is necessary for most of the added support that VE is aiming to provide this year.
+
+[Mostly done now.]
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1360975080,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oua6msncukecknrhwrdf,task_description,resolved
+VisualEditor: Node API re-write,… which is now merged. Hurrah.,1361576303,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oua6msncukecknrhwrdf,task_subcomment,NA
+VisualEditor: Node API re-write,Done in gerrit 50025 and related changes.,1361380955,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oua6msncukecknrhwrdf,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"**Author:** `phil`
+
+**Description:**
+visual editor after deleting lines 3 and 4 - note that 4 is still visible and the gap inbetween 2 and 4 is marked as 'cannot be edited'
+
+I had text
+1
+2
+3
+4
+
+selecting the last 2 lines ( 3 and 4 ) and deleting and saving, on looking at the page again '4' is visible and there is a gap that is marked as 'cannot be edited'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10499}",1360728000,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_description,resolved
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"Looks like this is similar to bug 44701. The linear model is correct, but is incorrectly serialized or parsed.",1419136405,PHID-USER-4yggyv53vecfrsed5djx,False,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),This is now fixed given the Parsoid update. Sorry for the delay.,1366396346,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"**orbit** wrote:
+
+Looks like this is similar to bug 44701. The linear model is correct, but is incorrectly serialized or parsed.",1361488266,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"**phil** wrote:
+
+Safari on Mac
+
+used the trackpad on my Mac to select the text
+
+Look at page
+http://en.wikipedia.org/wiki/User:PhilK10/sandbox/lines",1361484161,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?),"**orbit** wrote:
+
+What browser did this happen with? How did you make the selection (mouse vs. keyboard)? Can you link to the revision?",1361483818,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z34hczzuvb2kxj4wvl4l,task_subcomment,NA
+VisualEditor: Parsoid selective serialisation issue when single LI made from P (?),"**Author:** `phil`
+
+**Description:**
+error message on save after changing bullet format
+
+Blank page
+Add some text e.g. 'test' and make it a numbered bullet
+Save the page
+Edit the page
+Remove the text 'test'
+Click on the '1' and click the numbered bullet control to remove it
+Save page
+""Error loading data from server: Unsuccessful request: Error contacting the Parsoid server.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10836}",1360092960,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ukt7mx53j5m7gaxam7vy,task_description,resolved
+VisualEditor: Parsoid selective serialisation issue when single LI made from P (?),This is now fixed given the Parsoid update. Sorry for the delay.,1366396184,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ukt7mx53j5m7gaxam7vy,task_subcomment,NA
+VisualEditor: Parsoid selective serialisation issue when single LI made from P (?),"Can reproduce (not as a Parsoid error, which is just a ""this is not working"", but as a null diff.)
+
+This is a Parsoid bug; holding back for new Parsoid release to live to re-check before assigning.",1360209793,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ukt7mx53j5m7gaxam7vy,task_subcomment,NA
+VisualEditor: Backspace creating a slug then deletes again,"Pressing backspace creating a slug then deletes again:
+
+* Create a new page (or go to an existing one), and enter ""AB\nCD\nEF""
+* Place the cursor down-page of ""F"" and press backspace; ""F"" is deleted correctly.
+* Then press backspace again; ""E"" is deleted, as is the remaining slug, and the cursor moves us.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1354563540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jye77ivrdahrtvdtxmyb,task_description,resolved
+VisualEditor: Backspace creating a slug then deletes again,Fixed here: https://gerrit.wikimedia.org/r/#/c/37162/,1354754116,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-jye77ivrdahrtvdtxmyb,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog","
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1354562580,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-v466mnsvk3gmqhazwrti,task_description,resolved
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog",Merged into master.,1355176624,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog",Change-Id: I9d05ef6e3e2461bdcf363232f7b0fbad5e24f506,1354930076,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog",Now in gerrit as gerrit 37601.,1354929606,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog","Ic34fae7a8dbfc2a91ab36ba77613e17a91f29f6f is going to resolve this, when it's done.",1354921857,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+"VisualEditor: Implement ""Show changes"" (wikitext diff) in Save dialog","The VisualEditor should have a ""show changes"" button in the save dialog, taking the user to a wikitext diff in a hover over the editor surface; backend is now written but the front-end is still needed.",1354562716,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-v466mnsvk3gmqhazwrti,task_subcomment,NA
+VisualEditor: Paragraph changed to be a heading using the drop-down has its content deleted,"A paragraph when changed to be a heading using the toolbar drop-down has its content deleted (but the presence still stays).
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1354218900,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wh5lwbsbwcapw3b5fkjp,task_description,resolved
+VisualEditor: Paragraph changed to be a heading using the drop-down has its content deleted,"This was resolved in I994b8c43123c3cd02b9a550d5d7eac7d5052418e
+
+This bug was introduced in I4600e984b287c6ff9267f4281d2f09bab9e1ad95 because ve.ce.ContentBranchNode's onUpdate method was being overwritten by ve.ce.HeadingNode.",1354225226,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-wh5lwbsbwcapw3b5fkjp,task_subcomment,NA
+VisualEditor: Backwards selection fails over inline alien nodes,"Start with an article with an inline alien - e.g. ""ABC<tt>:-)</tt>DEF"". Place cursor ""up page"" (in LTR, left) of inline alien; selection with keyboard down-page works as expected. Now place the cursor ""down page"" (in LTR, right) of the inline alien; selection with keyboard up-page fails when reaching the alien, clearing the selection and placing the cursor immediately up-page of the alien.
+
+Note that in RTL this appears to work fine(!).
+
+Confirmed in both Chrome and Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353718440,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6tkrmk42gm6l4ttp56da,task_description,resolved
+VisualEditor: Backwards selection fails over inline alien nodes,"This was resolved in Iba55cfc3d531e7d1333b78c94912ff22179aace8
+
+The issue was that the cursor ""fix-up"" code was not preserving non-zero-length selections.",1354066309,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-6tkrmk42gm6l4ttp56da,task_subcomment,NA
+VisualEditor: Pass reference to data element to DM node constructor,"Post-December cleanup:
+
+Rather than passing the type, length, attributes and (soon) annotations into the dm.Node constructors separately, we should just pass a reference to the data element. This will make a lot of things cleaner, and make the constructors more consistent between node types.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353704640,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7hihps7ry67el6iq5omz,task_description,resolved
+VisualEditor: Pass reference to data element to DM node constructor,https://gerrit.wikimedia.org/r/#/c/34956/,1354054120,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7hihps7ry67el6iq5omz,task_subcomment,NA
+VisualEditor: Link inspector should edit existing annotation rather than creating new one,"When editing an existing link, the link inspector should grab the existing annotation and edit it, rather than starting over with a brand new annotation.
+
+Destroying the existing annotation loses metadata we need for preserving syntactical variation (hrefPrefix and origTitle), which means that currently, simply inspecting a link without actually changing its target can cause that link to be changed in the wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353380340,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vfbpfzavk4xiw4bzbauh,task_description,declined
+VisualEditor: Link inspector should edit existing annotation rather than creating new one,"Roan and I agree that as long as the annotation isn't re-applied (and meta data stripped) unless we actually changed the target, this behavior is OK.
+
+The concept is, if you touch something with the editor we have the right to normalize that bit.",1353971898,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-vfbpfzavk4xiw4bzbauh,task_subcomment,NA
+VisualEditor: Link inspector should edit existing annotation rather than creating new one,"What happens when the annotation type changes from internal to external? We have to create a new object at some point.
+
+What about when someone removes an annotation, then adds it back in? Do we then have a diff?
+
+I'm suspicious about this being the only way we cleanly round-trip.",1353957557,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-vfbpfzavk4xiw4bzbauh,task_subcomment,NA
+VisualEditor: First character in empty document behaves strangely in Firefox,"Steps to reproduce:
+1. Go to a nonexistent page
+2. Click the Create tab
+3. Type ""foobar""
+
+Result: ""f"" appears on a line by itself, ""oobar"" appears on the next line. The document model only contains ""oobar"". The ""f"" jumps around when rerendering (e.g. when you press enter).
+
+Can NOT be reproduced if:
+* you use Chrome
+* you click out of the editor and back into it before typing
+* you press Ctrl+A, Backspace before typing text
+
+The editor document looks like this:
+
+<div contentEditable=""true""><p><span class=""slug""></span></p></div>
+
+I think the cause of this bug is that Firefox initially puts the cursor before the <p>, rather than inside the <p> or inside the <span>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353377280,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-euqyxfrrhmfrgg76hheq,task_description,resolved
+VisualEditor: First character in empty document behaves strangely in Firefox,https://gerrit.wikimedia.org/r/#/c/34681/,1353545923,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-euqyxfrrhmfrgg76hheq,task_subcomment,NA
+VisualEditor: Add tab layout that adds a ve-tab instead of replacing the default,"Taken from bug 42117 which I'm de-prioritising
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1353122700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ffv55y77ier7bslrsyco,task_description,resolved
+VisualEditor: Add tab layout that adds a ve-tab instead of replacing the default,Change-Id: I3fe29c52b743837c2e1d66f25ccdca6115b8bd25,1354126331,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-ffv55y77ier7bslrsyco,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1353021960,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_description,resolved
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"Max,
+
+The reason for knowing which edits come from which source is so where the bugs are likely to be (and has the bonus of being possible to do statistical analysis).
+
+Longer-term, as we make editing through the API easier, we'd like to move every user of the API to be labelled as the source (this is the approach taken by Twitter, for example). And of course, for the edit box to go through the API too, though that's more for sanity and security model than for tracking down bugs given how stable that code is.
+
+It's entirely possible that Tags aren't the best venue for this data, but it's what we have for now, and we can move to a better one later.",1353704947,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"The use-case for adding this functionality/feature is still unclear to me. In theory, there should be no distinction between VisualEditor edits and edits made via the standard (the classic?) textarea editor.",1353704521,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,https://gerrit.wikimedia.org/r/34686,1353551242,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"(In reply to comment #1)
+> I guess for the testing phase it won't be too bad, but as Terry points out on
+> wikitech-l, the tagging system hasn't gotten much love since it was
+> implemented, so it may not scale well (fire hose and all...).
+>
+I think we'll be fine for a while. According to https://en.wikipedia.org/wiki/Special:Tags , the most-used tag (references removed) has been used over half a million times. There are five tags used >100k times, and they add up to about 1.8 million. Overall the number of tagged revisions on enwiki is probably about 2 million.
+
+Based on a quick toolserver query, the number of edits by logged-in users in the main namespace in the hour between 18:15 UTC and 19:15 UTC today (Nov 21) was about 4,500. Even if all those edits used VE, it would take 18 days for VE-tagged edits to reach 2 million at that pace. That's kind of fast, but it's slow enough that we'll have time to respond. I made change tagging configurable and turned it on by default. If it causes problems, we can turn it off.",1353551175,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified,"(In reply to comment 0)
+> Edits should add a VisualEditor tag (using MediaWiki's revision tagging
+> system) so they can be identified
+
+What's the use-case?
+
+I guess for the testing phase it won't be too bad, but as Terry points out on wikitech-l, the tagging system hasn't gotten much love since it was implemented, so it may not scale well (fire hose and all...).
+
+(Please don't file bugs with empty descriptions [comment 0]. Summaries often change and it makes replies with quoting more difficult.)",1353115901,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-bjs5pwsw6c4ji7r65fru,task_subcomment,NA
+VisualEditor: Meta-fy comments,"Comments should be stored in the meta-linmod, right now they're just ignored, which leads to all comments being removed when we save a page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352940240,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6whfmphns7qcm6tbt5j3,task_description,resolved
+VisualEditor: Meta-fy comments,"Ahm, I meant https://gerrit.wikimedia.org/r/34257 of course :S",1353384366,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6whfmphns7qcm6tbt5j3,task_subcomment,NA
+VisualEditor: Meta-fy comments,https://gerrit.wikimedia.org/r/3425,1353384355,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6whfmphns7qcm6tbt5j3,task_subcomment,NA
+VisualEditor: Add handling for mw:Entity,"Currently these are being alienated, which is bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352938560,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-d53w6sbodbcpx4rkzth3,task_description,resolved
+VisualEditor: Add handling for mw:Entity,Fixed with https://gerrit.wikimedia.org/r/#/c/34444/ and https://gerrit.wikimedia.org/r/#/c/34575/,1353528384,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-d53w6sbodbcpx4rkzth3,task_subcomment,NA
+VisualEditor: Remove feedback link for deployment,"Remove the MW feedback link for December deployment; it's not helpful given the different paradigm for users in this content.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1351911840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yvetu3dh7pwz6hn5x7ii,task_description,resolved
+VisualEditor: Remove feedback link for deployment,Fixed in https://gerrit.wikimedia.org/r/#/c/33500/,1352941206,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yvetu3dh7pwz6hn5x7ii,task_subcomment,NA
+VisualEditor: Support most common citation templates (special-case),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345761780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ldu3pqks4ww5ptxdm5nq,task_description,invalid
+VisualEditor: Support most common citation templates (special-case),We've decided to take a different tack which means this kind of special-casing won't be needed. Hopefully. :-) Consequently marking as invalid.,1364928248,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ldu3pqks4ww5ptxdm5nq,task_subcomment,NA
+VisualEditor: Support most common citation templates (special-case),Is this going to work also for languages other than English (e.g. Portuguese)?,1357400999,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-ldu3pqks4ww5ptxdm5nq,task_subcomment,NA
+VisualEditor: Support references,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345761720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zzor3of7nndkvfeeo4kt,task_description,declined
+VisualEditor: Support references,That issue is tracked as T52896.,1422564475,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,That's covered in specific tasks. Please don't open dead tasks from two years ago with drive-by comments; it's unhelpful and doesn't get anything done except wasting time diverting the conversation from the actual tasks.,1422562386,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,"I'm not clear as to why this is shown as ""Closed, Resolved"". VE still won't edit citations/footnotes where the body of the citation is in the References section (that is, within the reflist template), as demonstrated by the first two citations here: http://en.wikipedia.org/wiki/Pope_Francis#Name
+
+If this is a WONT FIX, it would be helpful to so state. And if so, I'll just note that decisions not to (ever) have VE be able to handle existing, widespread Wikipedia functionality, even where that is an ""ugly hack"", are one of the exact reasons that cause experienced editors to not want to use the VisualEditor.",1422426915,PHID-USER-hirrhium5ibrtof34lwa,True,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,Fixed in master and very soon in production.,1371968442,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,Related URL: https://gerrit.wikimedia.org/r/70031 (Gerrit Change I1551ddaa3d52c4827c7dcac2a02e31859769890a),1371958250,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,"(In reply to comment #1)
+> VisualEditor must be able to handle grouped footnotes ( as discussed here:
+> http://en.wikipedia.org/wiki/Help:Footnotes#Grouping_footnotes ) - at least,
+> not breaking these.
+
+I agree. In fact, you and I have discussed this several times, and each time I've told you that we're working on it, and that we won't go ""live"" for the beta without it. :-)
+
+> It also must be able to handle articles where the text
+> for
+> footnote is placed in the References section rather than in the body of the
+> article - see, for example,
+> http://en.wikipedia.org/wiki/Pope_Francis#References .
+
+Ugly hacks for wikitext like this are one of the exact reasons that cause us to want everyone to use the VisualEditor.",1367959088,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Support references,"VisualEditor must be able to handle grouped footnotes ( as discussed here: http://en.wikipedia.org/wiki/Help:Footnotes#Grouping_footnotes ) - at least, not breaking these. It also must be able to handle articles where the text for footnote is placed in the References section rather than in the body of the article - see, for example, http://en.wikipedia.org/wiki/Pope_Francis#References .",1367958327,PHID-USER-hirrhium5ibrtof34lwa,True,PHID-TASK-zzor3of7nndkvfeeo4kt,task_subcomment,NA
+VisualEditor: Link types need to be used by the UI so that the link inspector doesn't fail completely. :-),"As DM now has been adopted to the new RDFa link types, the UI needs to be adapted to them. Right now, all link inspectors fail utterly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1344375240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bnfj7ezq3zkwfxcrblkm,task_description,resolved
+VisualEditor: Link types need to be used by the UI so that the link inspector doesn't fail completely. :-),"Patched in https://gerrit.wikimedia.org/r/#/c/18048/ 
+Roan advised he will attempt a deploy of this today.",1344376085,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-bnfj7ezq3zkwfxcrblkm,task_subcomment,NA
+VisualEditor: New annotation API (tracking),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1343672040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4xi6ukfplmi5m5nx7n2s,task_description,resolved
+VisualEditor: License text should not be hard-coded,"The save dialog mentions but does not link to CC-BY-SA license, Project:Copyright page. These should be linked so you can get to them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1340905500,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-gmkobaxn2aw3klv7tvlc,task_description,resolved
+VisualEditor: License text should not be hard-coded,Change-Id: I84fee641162cdeed290092e56fb0e1d2562d833d,1354771701,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-gmkobaxn2aw3klv7tvlc,task_subcomment,NA
+VisualEditor: License text should not be hard-coded,In modules/ve/init/targets/ve.init.ViewPageTarget.js,1340926855,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gmkobaxn2aw3klv7tvlc,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature","IE11 on Windows 7 
+See the two screenshots to compare - VE in betalabs and in test2. 
+Production VE looks like test2 VE.{F24999}
+
+{F25001}",1419370204,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-lv7kzqodvetkfp53usel,task_description,invalid
+"VisualEditor incompatible with ""Fixed header"" beta feature",">>! In T85247#947266, @Se4598 wrote:
+> reopening: what's invalid here? (tasktitle had been changed to reflect incompatibility)
+
+(Now abandoned) Tools not designed to work with VE don't work with VE.",1441739949,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature",Thought that  since it's by design - not an issue/bug. ,1419873108,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature",reopening: what's invalid here? (tasktitle had been changed to reflect incompatibility),1419872711,PHID-USER-jcypqodpdpbcicgwgh7j,False,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature","Yes, unchecking 'Fixed header'  makes VE be back to normal. Should be there some warning to VE users?",1419870543,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature",another report: https://www.mediawiki.org/wiki/Topic:S4opda1x12kcc54w,1419553818,PHID-USER-jcypqodpdpbcicgwgh7j,False,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature","Looks okay to me. You have the ""Fixed header"" [[ http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences#mw-prefsection-betafeatures | beta feature ]] enabled, I guess VE isn't compatible with it. (You also have ""Compact personal bar"", but that isn't problematic AFAIK.)",1419523897,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+"VisualEditor incompatible with ""Fixed header"" beta feature","Actually, I see VE is broken in Chrome too - so the issue is not specific to IE. ",1419374069,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-lv7kzqodvetkfp53usel,task_subcomment,NA
+Create right-click menus for VisualEditor,"When I do Wikipedia editing workshops with VisualEditor, participants repeatedly suggest adding a right-click context menu.
+
+Something like that exists in Google Docs, and it's surprisingly useful. For MediaWiki It can include similar functions - formatting, styling, linking, commenting, suggesting edits, etc.",1419081869,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-zf3equ3kmfihdlt4bfvt,task_description,declined
+Create right-click menus for VisualEditor,"We have intentionally designed VisualEditor to not use right menus because they can't ever work on touch devices, because of user complexity, and because of their lack of find-ability. Even if these would start out purely as secondary UX controls, it would lead us down the road to Word's bloat.",1420842469,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zf3equ3kmfihdlt4bfvt,task_subcomment,NA
+ VisualEditor JavaScript and tests should only be added if VisualEditor is installed,"According to Antoine when he runs the tests using the following extensions together:
+
+- JsonConfig
+- Mantle
+- MobileApp
+- MobileFrontend
+- WikiGrok
+- ZeroBanner
+- ZeroPortal
+
+This yields two failures:
+
+ResourcesTest::testMissingDependencies
+The module 'ext.visualEditor.mobileViewTarget' required by
+'mobile.editor.ve' must exist
+Failed asserting that an array contains 'ext.visualEditor.mobileViewTarget'.
+
+ResourcesTest::testUnsatisfiableDependencies
+Undefined index: ext.visualEditor.mobileViewTarget
+
+
+",1419008593,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-v7rf6nwt2u72ghyq4kad,task_description,resolved
+ VisualEditor JavaScript and tests should only be added if VisualEditor is installed,"Change 181403 merged by jenkins-bot:
+Don't add VisualEditor related modules if VE isn't installed
+
+[[https://gerrit.wikimedia.org/r/181403]]",1419447395,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7rf6nwt2u72ghyq4kad,task_subcomment,NA
+ VisualEditor JavaScript and tests should only be added if VisualEditor is installed,"Change 181403 had a related patch set uploaded (by Florianschmidtwelzow):
+Don't add VisualEditor related modules if VE isn't installed
+
+[[https://gerrit.wikimedia.org/r/181403]]
+
+#patch-for-review",1419257192,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7rf6nwt2u72ghyq4kad,task_subcomment,NA
+Familiarize yourself with edit-reportcard.wmflabs.org,"https://edit-reportcard.wmflabs.org is a very rough beginning in the analysis of data related to the use of VisualEditor in the main wikipedias. The VisualEditor team needs help improving this space, so it provides metrics that help the team understand problematic areas, trends, impact of new features...
+
+At this point there is basically no documentation. T84926 and T84927 are very basic starts. Can you dig in these metrics and the raw data associated, and understand what is being shown there?
+
+Also, these graphs are created using [[ https://www.mediawiki.org/wiki/Analytics/Limn | Limn ]]. Have a look at the documentation in order to understand how it works. Bonus point if you install it locally and play with it a bit. 
+
+If you have any questions about Limn you can ask in the [[ https://lists.wikimedia.org/mailman/listinfo/analytics | analytics mailing list ]]. In any case, considering your background it is a good idea to subscribe to this list.",1418947018,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-sj4lh4ptvu2lzgg743rk,task_description,resolved
+Familiarize yourself with edit-reportcard.wmflabs.org,https://wikitech.wikimedia.org/wiki/Analytics/Dashboards is the documentation specifically about dasboards.,1418955612,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sj4lh4ptvu2lzgg743rk,task_subcomment,NA
+Familiarize yourself with edit-reportcard.wmflabs.org,"Great, I'm on it.",1418955520,PHID-USER-d3457iccsv4uq5ki2zkw,False,PHID-TASK-sj4lh4ptvu2lzgg743rk,task_subcomment,NA
+Special:MyLanguage should have a way to redirect to the fallback language if there is no translation,"If, for example, we want to give a link from VisualEditor in the Afrikaans Wikipedia to the VE user guide in mediawiki.org, we can only link to the source page in English. It would be more convenient to link directly to Afrikaans, but Special:MyLanguage only works if the user defined the language in the preferences of the same wiki, and [[VisualEditor/User guide//af]] will appear like a non-existent page if there is no translation.
+
+I can think of several options to fix this:
+* Make a non-existent sub-page redirect to the fallback language.
+* Make Special:MyLanguage work across wikis somehow.
+* Global cross-wiki language options (this would be Very Useful for a lot of other things).
+
+",1418930787,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-bifywkolpcqrbipm7zgp,task_description,duplicate
+Special:MyLanguage should have a way to redirect to the fallback language if there is no translation,@amire80 Do you have more information that can be used by Nemo and Niklas for this?,1433410170,PHID-USER-ttw4tpoosxc4pbmskrla,False,PHID-TASK-bifywkolpcqrbipm7zgp,task_subcomment,NA
+Special:MyLanguage should have a way to redirect to the fallback language if there is no translation,"> Make Special:MyLanguage work across wikis somehow.
+
+Do you mean, redirecting the user to another wiki?",1422318533,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-bifywkolpcqrbipm7zgp,task_subcomment,NA
+Special:MyLanguage should have a way to redirect to the fallback language if there is no translation,"This bug is vague. You can already link to [[mw:Special:MyLanguage/Page/af]] with the following caveats:
+* Set interface language in target wiki (if available) overrides the subpage request
+* It falls back directly to English.
+
+I think there is a task for the fallback thing already.",1422298572,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-bifywkolpcqrbipm7zgp,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"The undo link in the page history leads to the source editor and not VisualEditor. It should lead to the VisualEditor for people who prefer to use it.
+
+It's probably not a high priority at this point, but if the VisualEditor is supposed to replace the source editor, this issue should be handled at some point.",1418657683,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_description,open
+The undo link in the page history leads to the source editor and not VisualEditor,"I came across this issue while working on {T185548}, which in turn led me to {T185542}.
+
+I rebased the patch on `master` and overall it works (nice work!), but there are a few small issues:
+
+1. Undo notifications are still broken per T185548 because `undidRevId` isn't set when updating via the API (it's currently only set in `WikiPage.php`'s `doEditContent()`. This should be pretty easy to fix and I could push a commit to this patchset if you'd like.
+1. The edit summary is no longer working. As noted in {T185542} (item 5 in the task description), the edit summary used to correctly autopopulate with VE but it doesn't with this patch.
+1. When going to ""View history"" and then clicking on ""Undo"", I'd often be prompted by VE that ""This page was edited since you last loaded it."" VE then prompts to resume editing or start a new edit. If you click ""Resume editing"" the diff review won't show, but if you click ""start a new edit"", it will.
+1. Something is not quite right with auto-save functionality (line 518 of `ArticleTarget.js`). If you don't comment out `surfaceModel.restoreChanges();`, then VE informs you ""Changes recovered"" and you don't see the diff window.
+
+All of these seem pretty minor. I may have some time to work on them this week so I can move forward on resolving T185548, just let me know.",1529530774,PHID-USER-jzbjfcs2csloltie4voe,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"@Esanders: Yes, the priority should be higher. @Esanders, @AlexMonk-WMF (@Krenair): What is the status of this? How far is the patch to merge?",1520540365,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"Change 323357 restored by Esanders:
+[WIP] Undo support
+
+[[https://gerrit.wikimedia.org/r/323357]]",1483754459,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"Change 323357 abandoned by Alex Monk:
+[WIP] Undo support
+
+[[https://gerrit.wikimedia.org/r/323357]]",1483652990,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,This is higher priority with the new source mode.,1483226320,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"Change 323357 had a related patch set uploaded (by Alex Monk):
+[WIP] Undo support
+
+[[https://gerrit.wikimedia.org/r/323357]]
+",1479959213,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"I just hit this problem in my pet project, which has SET with VE enabled by default to everyone. Indeed, this problem is more annoying in this context because then editors who preferred VE or who didn't even use the wikitext editor are left with two problems after clicking Undo:
+
+# They are now facing a wikitext UI.
+# Their preference has now changed to wikitext, which means that all future edits will be presented on wikitext unless they find out how to bring VE back.",1474267745,PHID-USER-h6xz2shsbvhdtx5puurj,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"I just hit this problem in my pet project, which has SET with VE enabled by default to everyone. Indeed, this problem is more annoying in this context because then editors who preferred VE or who didn't even use the wikitext editor are left with two problems after clicking Undo:
+
+# They are now facing a wikitext UI.
+# Their preference has now chanded to wikitext, which means that all future edits will be presented on wikitext unless they find out how to bring VE back.",1474267609,PHID-USER-h6xz2shsbvhdtx5puurj,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"I just hit this problem in my pet project, which has SET with VE enabled by default to everyone. Indeed, this problem is more annoying in this context because then editors who preferred VE or who didn't even use the wikitext editor are left with two problems after clicking Undo:
+
+# They are now facing a wikitext UI.
+# Their preference has now chanced to wikitext, which means that all future edits will be presented on wikitext unless they find out how to bring VE back.",1474267416,PHID-USER-h6xz2shsbvhdtx5puurj,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,For some reasons I thought this was already fixed? It's particularly annoying/confusing on SET wikis.,1463397158,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"> the VisualEditor is supposed to replace the source editor
+
+Thunders and lightnings!",1451456248,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"When you press an undo button, not only do we set the revision text to the previous revision, but we also set up the standard revert summary as the default summary, and show the diff they're about to cause, and show a warning. I'm wondering what a similar experience in VE would look like.",1451449874,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+The undo link in the page history leads to the source editor and not VisualEditor,"Suggest that specifically the undo link should lead to the editing interface selected in the user preferences or, in the absence of preference, to the default editor.  ",1423015674,PHID-USER-yif6nz5uhka5cnltixpc,False,PHID-TASK-mt3dwshqj2hvmp73flaa,task_subcomment,NA
+"[gdash] ""VisualEditor: Latency"" graphs look dead",https://gdash.wikimedia.org/dashboards/ve/ seems to be missing data since the end of November.,1418651695,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-gfulce44jv65rvyd7kt2,task_description,duplicate
+<templatedata> cannot be used as Template Data,"I installed VisualEditor on MediaWiki 1.24.0. It works well now, I can edit and save pages.
+
+But when I tried to add Template Data to my old template page, it cannot be formate as a table. VisualEidtor cannot use template data when editing pages.
+
+My template data:
+
+```
+<templatedata>
+{
+    ""description"": ""插入注意文本框，突出显示注意内容"",
+    ""params"": {
+        ""1"": {
+            ""label"": ""注意内容"",
+            ""description"": ""注意文本框的内容"",
+            ""required"": true,
+            ""type"": ""string"",
+            ""aliases"": [ ""注意内容"" ]
+        }
+    }
+}
+</templatedata>
+```
+
+Template page: http://xuexiii.org/w/%E6%A8%A1%E6%9D%BF:%E6%B3%A8%E6%84%8F
+
+You can see template data is displayed as plain text. But in English Wikipedia, it should become a table.",1418381694,PHID-USER-g2bnzp2j6voh3sihftsl,False,PHID-TASK-hys6f6g7uxyhvocshtwi,task_description,resolved
+<templatedata> cannot be used as Template Data,,1439832857,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hys6f6g7uxyhvocshtwi,task_subcomment,NA
+<templatedata> cannot be used as Template Data,,1418406238,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hys6f6g7uxyhvocshtwi,task_subcomment,NA
+<templatedata> cannot be used as Template Data,@Jdforrester-WMF Thanks!,1418402337,PHID-USER-g2bnzp2j6voh3sihftsl,False,PHID-TASK-hys6f6g7uxyhvocshtwi,task_subcomment,NA
+<templatedata> cannot be used as Template Data,http://xuexiii.org/w/%E7%89%B9%E6%AE%8A:%E7%89%88%E6%9C%AC shows that you don't have the #TemplateData extension installed. If you install that (and then make an edit to any templates with TemplateData blocks on them so they can be re-parsed) it should work.,1418401710,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hys6f6g7uxyhvocshtwi,task_subcomment,NA
+Feedback link in VisualEditor needs to play nicely with LiquidThreads,"Steps to reproduce:
+
+1.  Open VisualEditor on MediaWiki.org.
+2.  Click on ""Leave feedback"" in the help menu.
+3.  Choose to leave feedback onwiki.  Type something and submit your feedback.
+
+Result:
+
+The feedback is posted as a ==Regular section heading== with normal, signed ~~~~ comments to a feedback page that is using LiquidThreads.  It either needs to post correctly within LiquidThreads or it needs to post to a different page.",1418189771,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-q4c2ad3gdnidfwio3wwp,task_description,duplicate
+Feedback link in VisualEditor needs to play nicely with LiquidThreads,">>! In T78120#836065, @TTO wrote:
+> I don't think it is fair to merge this. Realistically, that LQT task is never going to get resolved. VE needs to either work around this, or stop using a LQT-based feedback page (which is a WMF config issue).
+
+I disagree; the standard feedback form provided by Platform is what all feature teams are meant to use. The problem that it's particularly poor and needs fixing in various ways is something the Editing team have been (slowly) helping to improve. However, there are wider issues that are beyond our team and need specialists to fix. When all the LQT pages get converted to Flow, of course, the issue becomes the parallel {T59989}.",1418233399,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-q4c2ad3gdnidfwio3wwp,task_subcomment,NA
+Feedback link in VisualEditor needs to play nicely with LiquidThreads,"I don't think it is fair to merge this. Realistically, that LQT task is never going to get resolved. VE needs to either work around this, or stop using a LQT-based feedback page (which is a WMF config issue).",1418200649,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-q4c2ad3gdnidfwio3wwp,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,Can we create consistency between the naming convention of the (sub)projects related to Visual Editor and Wikitext editor to make them more easily findable and have better parity?,1418160470,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-hy7qluemr2knghxwplss,task_description,declined
+Rationalize the project names of VE and wikitext editor,We're not going to merge all the 20+ editing-related projects together.,1418165494,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,Umbrella projects having a distinct color seems sane.  Upstream seems to do this I think.,1418165382,PHID-USER-3neel27i7dyu62jbbx2l,True,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"> the wikitext editor in Flow, which is dealt with inside MediaWiki-extensions-Flow
+> the VisualEditor issues specific to the Flow integration, which are, well, not currently filed anywhere, but I guess would go in VisualEditor and MediaWiki-extensions-Flow together.
+
+The VE integration is not actively being worked on, though we still want to use it later, of course.
+
+We basically use the standard scheme (MediaWiki-extensions-ExtensionName).  We also have a team board ( #Collaboration-Team ), but if you file it in the extension component you don't need to worry about the team board (we may add that project later, though).
+
+Are there any action items for #Collaboration-Team ?  If not, we'll remove our projects from this task.",1418165300,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"There's also:
+* **Mobile Web**
+** the wikitext editor in Mobile Web, which is dealt with inside #MobileFrontend-General-or-Unknown (no specific project for editor issues)
+** VisualEditor issues specific to the Mobile Web integration, which are dealt with in #VisualEditor-MediaWiki-Mobile
+* **Apps**
+** the wikitext editor in the iOS mobile app, which is dealt with in #Wikipedia-App-iOS-App (but not really, because they haven't migrated to Phabricator yet)
+** the wikitext editor in the Android mobile app, which is dealt with in #Wikipedia-App-Android-App (but not really, again)
+* **Flow**
+** the wikitext editor in Flow, which is dealt with inside #MediaWiki-extensions-Flow
+** the VisualEditor issues specific to the Flow integration, which are, well, not currently filed anywhere, but I guess would go in #VisualEditor and #MediaWiki-extensions-Flow together.
+* the wikitext editor in **LiquidThreads**, which is dealt with inside #MediaWiki-extensions-LiquidThreads
+* the **code editor**, which is dealt with in #MediaWiki-extensions-CodeEditor
+
+… and probably some others I'm forgetting. 
+",1418162160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"No, not really. Core's wikitext editing must stay under MediaWiki- and VisualEditor (and WikiEditor) must be separate.",1418162003,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"thanks for clarifying @matamarex, you kind of hit on what I'm saying. Is there any way we can make the phab project names for these more clearly show those relationships you just outlined?",1418161813,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"We have three distinct editors and three corresponding projects.
+
+* The **VisualEditor** is #VisualEditor, this is an umbrella project that includes all tasks from all of the subprojects like #VisualEditor-EditingTools. You should never file tasks in subprojects only or they may get lost (until we have project inheritance or whatever in Phabricator).
+* The **WikiEditor extension**, which is #MediaWiki-Extensions-WikiEditor. This is what most people know as //the// wikitext editor and implements all of the fancy buttons around the wikitext editing area.
+* The **built-in** MediaWiki editor, which you never see unless you're the kind of person who still uses MonoBook and hates new things. It doesn't have a dedicated project, but any issues can be filed under #MediaWiki-Page-editing (this project also covers things like editing pages suddenly being broken or something).
+
+I'm not sure what this task is about.",1418161345,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"I've added what I know and can find to the task, but others may be present and hard to find, due to the issue in this task (Catch-22)",1418161019,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Rationalize the project names of VE and wikitext editor,"What are the ""subprojects related to Wikitext editor""?
+Or basically: Which existing projects are we discussing here?",1418160799,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-hy7qluemr2knghxwplss,task_subcomment,NA
+Compatibility in Beta Features,"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/35 //
+
+== Narrative ==
+
+As a user, I want to know if a beta feature doesn't work work for my browser or technical configuration.
+
+
+
+== Acceptance Criteria ==
+
+Browser and technology compatibility can vary from one feature to another (VisualEditor in particular isn't available for IE yet). Other features may require Javascript, CSS or other technical configurations as well, that could cause them to malfunction if not enabled.
+
+So each beta feature extension needs to have a blacklist of platforms that it cannot support, stored in Javascript, JSON or other machine-readable format that can be sent to Beta Features.
+
+The Beta Features (or the extension) then needs to check whether the user's configuration matches one of these restricted platforms, so it can let the user know if their platform is not compatible with that feature.
+
+Last but not least, we also need to inform the user about features that are not compatible with their particular browser or configuration. For example, we may want to display a message like: ""This feature is not compatible with your browser yet.""
+
+This is required so the user understands why they cannot enable that feature (even though it's still checked in their preferences -- so they can use it on other platforms).
+
+That message could be bolded and/or colored in red, to provide a visual cue that this feature will not work. Maybe the entire feature could be grayed out, to make it even more explicit?
+
+Here are the types of notes we may need to display, when a feature is not compatible for the user's configuration:
+* Notes about browser compatibility
+** Text displayed to user ""This feature is not compatible with your browser yet.""
+* Notes about JS compatibility
+** Text displayed to user ""You must  [[http://www.enable-javascript.com/ | enable JavaScript]] in your browser to use this feature.""
+* Notes about CSS compatibility
+** Text displayed to user ""Your site skin or custom CSS is not compatible with this feature, to enable it use the default site skin.""
+
+Only one error message should be displayed at any given time, the order of display should be as follows
+# CSS/Skin compatibility
+# JS compatibility
+# Browser compatibility
+e.g. if there is both a browser and JS compatibility issues the user would only see the JS issue.
+
+See the most current feature requirements here:
+
+ [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] 
+
+
+
+== Related Bugs ==
+
+== Related Stories ==
+
+ [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/2 | #2]]  Beta features
+
+See also:
+
+ [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] ",1418054212,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-vz22yajno24klsq4wdsy,task_description,resolved
+Compatibility in Beta Features,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/35 | mingle]] on 2013-10-30 at 23:57:09, @MarkTraceur wrote:
+
+https://gerrit.wikimedia.org/r/88987",1418054215,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-vz22yajno24klsq4wdsy,task_subcomment,NA
+Compatibility in Beta Features,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/35 | mingle]] on 2013-10-11 at 18:06:37, @MarkTraceur wrote:
+
+https://gerrit.wikimedia.org/r/88987",1418054214,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-vz22yajno24klsq4wdsy,task_subcomment,NA
+OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing,"OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing. 
+
+svgo emits SVG like `<path d=""M-1-2 …"">` or `<path d=""M.3.5 …"">` which rsvg is unable to parse (this is valid path data fragment that represents a points (-1; -2) and (0.3; 0.5), and the SVG 1.1 spec even explicitly discusses this syntax). The same issue affects ImageMagick when compiled with rsvg support.
+
+This means that some of OOUI's and VisualEditor's icons will not appear correctly e.g. when uploaded to Commons, and blocks {T76473} since we're unable to rasterize the SVGs to PNG.
+
+This can be worked around using some search-and-replace, but this leaves some questions:
+
+* Can this be fixed in rsvg? Gotta file a bug, even if it'll probably be ignored, and even if not no one is going to upgrade their copy.
+* //Where// do we apply the workaround? To the files in git? During build process? In MediaWiki's RL module from T76473?
+* Should we maintain the workaround ourselves somewhere, or maybe it could be upstreamed to svgo? (As a command-line option for people who want rsvg compatibility at the cost of a few bytes, like us?)",1417782237,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5qhy3k4ikqcg7djrpejr,task_description,resolved
+OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing,The patch is included in rsvg 2.40.6. https://git.gnome.org/browse/librsvg/log/,1417796826,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5qhy3k4ikqcg7djrpejr,task_subcomment,NA
+OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing,"Haha, I just learned that we have //just// deployed a rsvg patch to fix this on Wikimedia wikis last week: https://gerrit.wikimedia.org/r/#/c/173639/ (80dd6ad665610979af294aeff4db417599363250). rsvg upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=620923, patch is https://git.gnome.org/browse/librsvg/commit/?id=5ba4343bccc7e1765f38f87490b3d6a3a500fde1.
+
+So let's forget applying to fix to existing files or bothering svgo people, and just keep the one in ResourceLoaderImage patch for third-parties who don't have the most recent rsvg.",1417783585,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5qhy3k4ikqcg7djrpejr,task_subcomment,NA
+OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing,"The workaround goes like this: https://github.com/trevorparscal/colorize/pull/1/files – in the simplest form, we insert some spaces and zeroes to create path data that is readable to rsvg.
+
+This has already been implemented in [[ https://gerrit.wikimedia.org/r/#/c/165922/ | ResourceLoaderImageModule for icons ]] for T76473 (see `ResourceLoaderImage::massageSvgPathdata()`).
+
+I think we should keep the workaround there (for potential third-party users) **and** apply the fix to SVG files in our repos, for the benefit of people wishing to have copies of the files on Commons. It costs us little and isn't just theoretical, but has already been complained about: https://lists.wikimedia.org/pipermail/wikitech-l/2014-November/079532.html",1417782558,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5qhy3k4ikqcg7djrpejr,task_subcomment,NA
+wikibugs fails to link Phab task in some IRC notifications,"wikibugs fails to link Phab task in some IRC notifications, dunno why. From #-visualeditor (times in CEST or something):
+
+```
+[20:38]	<wikibugs> OOjs-UI: MediaWiki, Apex: Provide default margins for buttons and other widgets
+...
+[20:41]	<wikibugs> OOjs-UI: ComboBoxWidget: Provide a getMenu method
+```
+
+The tasks it should have linked are T76643 and T76646.",1417635858,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-35mqsk5kwrqhdyst3iki,task_description,resolved
+wikibugs fails to link Phab task in some IRC notifications,Fixed by https://gerrit.wikimedia.org/r/#/c/181523/,1419290531,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-35mqsk5kwrqhdyst3iki,task_subcomment,NA
+wm-bot facts have too much bugzilla in them,"Ctrl + F on http://bots.wmflabs.org/~wm-bot/db/%23mediawiki.htm gives 27 usages
+
+Some are probably ok (aliases and such), but some plainly need updating
+
+[22:10:20] <Reedy> !bug
+[22:10:20] <wm-bot> https://bugzilla.wikimedia.org/
+
+Another being vebug giving ""Submit a new ticket on Bugzilla for the VisualEditor: https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditor""",1417558557,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-d2wd3ojejdgstj6g3h2c,task_description,resolved
+wm-bot facts have too much bugzilla in them,Pretty sure I cleaned up most of those I could find.  Please ping me if more are found.,1422127750,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-d2wd3ojejdgstj6g3h2c,task_subcomment,NA
+wm-bot facts have too much bugzilla in them,"note, you can use !bug replace <new text>",1417959454,PHID-USER-ppytiem7rcsbnstfsrvq,False,PHID-TASK-d2wd3ojejdgstj6g3h2c,task_subcomment,NA
+"VisualEditor ""basic"" image type should be called ""inline""","The media type ""basic"", described using the message Visualeditor-dialog-media-type-none does not explain the real meaning of how the image will be inserted.
+
+It will be clearer to call it something like ""Inline"", and possibly to change the icon as well.",1417524575,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-cxmbeijkrc3gdlqivbjg,task_description,declined
+"VisualEditor ""basic"" image type should be called ""inline""","Change 176919 abandoned by Jforrester:
+Change Basic image type to ""Inline""
+
+Reason:
+See comments on the task.
+
+[[https://gerrit.wikimedia.org/r/176919]]",1417542089,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cxmbeijkrc3gdlqivbjg,task_subcomment,NA
+"VisualEditor ""basic"" image type should be called ""inline""","No. ""Inline"" is absolutely not what this sets. MediaWiki's Multimedia support is terrible, but lying to users to confuse them more is a terrible idea.",1417542081,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cxmbeijkrc3gdlqivbjg,task_subcomment,NA
+"VisualEditor ""basic"" image type should be called ""inline""","Change 176919 had a related patch set uploaded (by Amire80):
+Change Basic image type to ""Inline""
+
+[[https://gerrit.wikimedia.org/r/176919]]
+
+#patch-for-review",1417524806,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cxmbeijkrc3gdlqivbjg,task_subcomment,NA
+Module 'mobile.editor.ve' has incompatible target 'desktop',"```
+2) ResourcesTest::testUnsatisfiableDependencies
+The module 'mobile.editor.ve' must not have target 'desktop' because its dependency 'ext.visualEditor.mobileViewTarget' does not have it
+```",1417494246,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dtnazl6m376lv35fjrzu,task_description,resolved
+Module 'mobile.editor.ve' has incompatible target 'desktop',"Change 178731 merged by jenkins-bot:
+Don't load mobile.editor.ve module in desktop target
+
+[[https://gerrit.wikimedia.org/r/178731]]",1418181350,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dtnazl6m376lv35fjrzu,task_subcomment,NA
+Module 'mobile.editor.ve' has incompatible target 'desktop',"Change 178731 had a related patch set uploaded (by Jdlrobson):
+Don't load RL module for VE in supported mode
+
+[[https://gerrit.wikimedia.org/r/178731]]
+
+#patch-for-review",1418172098,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dtnazl6m376lv35fjrzu,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","This is so we can manage tasks as being definitely fixed, not just that it worked in test.
+
+Descriptions: ""Project for tasks verified by QA as being fixed in phase<N>.""
+
+Access as normal; icon as normal.",1417042379,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_description,resolved
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","I archived unused project tags #Verified-in-Phase0, #Verified-in-Phase1, #Verified-in-Phase2 last used 27 months ago.",1623921585,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","#Verified-in-Phase0 and #Verified-in-Phase2 were last used (set) in March 2019. 
+#Verified-in-Phase1 was never used.
+Is there still any use for them, or can they be [archived](https://www.mediawiki.org/wiki/Phabricator/Project_management#Archiving_a_project)?",1608415211,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#818733, @Aklapper wrote:
+> I've updated to yellow color and tag icon + added a link to the deployment train to project descriptions.
+
+Thank you!",1417809246,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","I've updated to yellow color and tag icon + added a link to the deployment train to project descriptions.
+
+>>! In T76104#801982, @Jdforrester-WMF wrote:
+> The old #verified tag is not fit for purpose and should be marked as inactive.
+
+If the Wikidata team has agreed on that and also plan to use the new Verified-in-PhaseX tags instead, I'm happy to archive it.",1417699280,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#789665, @Se4598 wrote:
+> Is it intentional that this are ""normal"" projects and not of (visual) type ""Tag"" as per https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Guidelines?
+
+Yes, but I'm sure QA don't particularly care. There is an on-going project to ensure that tasks marked as resolved are actually proven to be resolved in practice, which is what these are for…
+
+>>! In T76104#801766, @Aklapper wrote:
+> The project descriptions of those three projects should link to https://wikitech.wikimedia.org/wiki/Deployments ( https://www.mediawiki.org/wiki/MediaWiki_1.25/Roadmap unfortunately isn't a stable URL) . 
+
+The link can be changed as the current MediaWiki version requests; https://wikitech.wikimedia.org/wiki/Deployments is significantly less stable as an information resource.
+
+> These projects should be tag style. 
+
+Sure.
+
+> These projects might also create slight confusion towards the already existing, generic ""verified"" tag
+
+The old #verified tag is not fit for purpose and should be marked as inactive.
+
+> (at least I want the descriptions to refer to each other and explain the differences in usage).
+
+I see no value in using it.
+
+> For future reference, I appreciate waiting a little bit longer for further feedback on such ideas, if we're not in some urgent hurry. Thanks. :)
+
+There was an urgent hurry. The complete absence of a viable ""verified"" status in Phabricator made it impossible for QA to do their jobs of marking tasks as confirmed-fixed. Phabricator might have been in its first few days, but we are still shipping live code every week, and can't wait for a few days to restart our work.",1417541625,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#801791, @Qgil wrote:
+> I guess ""Visible To: All Users"" is simply a consequence of lack of awareness
+
+Yeah, chatted with James and that's fixed now",1417541010,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","I guess ""Visible To: All Users"" is simply a consequence of lack of awareness of  https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Default_policy. I have started to insist on View Public in proposals from new project creators.",1417538356,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","Also, why are these projects set as ""Visible To: All Users"" instead of ""Public""?
+Please always provide reasons, as explained on https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Policy
+
+Currently going to e.g. https://phabricator.wikimedia.org/T75378 and not being logged in I see two restricted projects (VisualEditor-Tables being the other one).",1417538204,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","...and I also appreciate pointers where the practice to use these new tags is documented on-wiki, as that should also **definitely** be part of the project descriptions.",1417538062,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","The project descriptions of those three projects should link to https://wikitech.wikimedia.org/wiki/Deployments ( https://www.mediawiki.org/wiki/MediaWiki_1.25/Roadmap unfortunately isn't a stable URL) . 
+These projects should be tag style. 
+These projects might also create slight confusion towards the already existing, generic ""verified"" tag (at least I want the descriptions to refer to each other and explain the differences in usage).
+
+If there's no opposition I am going to go ahead tomorrow or so.
+
+For future reference, I appreciate waiting a little bit longer for further feedback on such ideas, if we're not in some urgent hurry. Thanks. :)",1417538015,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#789703, @Qgil wrote:
+> They look indeed like better suited for tags.
+
+I agree (especially if QA don't care).
+>>! In T76104#789656, @Jdforrester-WMF wrote:
+>[...]
+>> And just curious, where can I learn about Phase0, 1, 2?
+> 
+> wikitech.wikimedia.org/wiki/Deployments and a few dozen other places.
+
+Based on that I assume this means the specific wiki sets/groups and so I updated the descriptions of the projects to reflect that. Please correct me if I'm wrong at this.
+
+I'm also confused of the usage of these different terms (group/set and phase), so it would for me initially clearer if they were named Verified-in-Group2 as group seems to be the normally used term for this.",1417044849,PHID-USER-jcypqodpdpbcicgwgh7j,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",They look indeed like better suited for tags.,1417043564,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#789665, @Se4598 wrote:
+> Is it intentional that this are ""normal"" projects and not of (visual) type ""Tag"" as per https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Guidelines?
+
+Yes, but I'm sure QA don't particularly care. There is an on-going project to ensure that tasks marked as resolved are actually proven to be resolved in practice, which is what these are for…",1417043208,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","Is it intentional that this are ""normal"" projects and not of (visual) type ""Tag"" as per https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Guidelines?",1417043124,PHID-USER-jcypqodpdpbcicgwgh7j,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA",">>! In T76104#789646, @Qgil wrote:
+> Just checking, are you in sync with QA?
+
+Yes; this was at @RYasmeen's request.
+
+> And just curious, where can I learn about Phase0, 1, 2?
+
+wikitech.wikimedia.org/wiki/Deployments and a few dozen other places.",1417042800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","You provided less than a minute for consensus.  :)
+
+Just checking, are you in sync with QA? And just curious, where can I learn about Phase0, 1, 2?",1417042591,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+"Create a project for ""verified in phase0"", ""verified in phase1"" and ""verified in phase2"" for QA","Done:
+
+#Verified-in-Phase0
+#Verified-in-Phase1
+#Verified-in-Phase2
+",1417042467,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k26xtxmrbja4nhavgk5s,task_subcomment,NA
+VisualEditor is not displayed after clicking on Edit,"MediaWiki version is 1.25wmf9
+
+VisualEditor 1.25wmf9 is installed and enabled:
+```
+require_once ""$IP/extensions/Parsoid/Parsoid.php"";
+require_once ""$IP/extensions/VisualEditor/VisualEditor.php"";
+
+$wgDefaultUserOptions['visualeditor-enable'] = 1;
+$wgHiddenPrefs[] = 'visualeditor-enable';
+//$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
+$wgVisualEditorParsoidHTTPProxy = false;
+$wgVisualEditorParsoidURL = 'http://[my.nodejs.host]:80';
+$wgVisualEditorParsoidPrefix = 'myWiki';
+//$wgSessionsInObjectCache = true;
+$wgVisualEditorParsoidForwardCookies = false;
+$wgVisualEditorNamespaces = array_merge( $wgContentNamespaces, array( NS_USER ) );
+```
+
+If I curl Parsoid for the Main Page (from the same host where MediaWiki is installed) I can see page parsed and a log on Parsoid
+```
+curl http://[my.nodejs.host]/myWiki/Main_Page?oldid=1
+```
+
+If I click on Edit {F16470} the page is refreshed (?title=Main_Page&veaction=edit), but I can't see the VisualEditor editing area. Moreover, nothing is logged on Parsoid (like if the request has never be done).
+If I click on Edit source the standard editor is displayed.",1417033425,PHID-USER-aost7ybqf3mbefvdfsdc,False,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_description,resolved
+VisualEditor is not displayed after clicking on Edit,"Yes, I found it and already did it, thanks.
+
+Now I'm investigating another issue.
+{F16587}
+After I click on Edit the loader bar rolls forever and the editing area never appears.
+I just found this error in the browser console
+
+```
+Exception thrown by ext.visualEditor.mwlink 
+
+
+TypeError: Expecting a function in instanceof check, but got undefined TypeError: Expecting a function in instanceof check, but got undefined {stack: (...), message: ""Expecting a function in instanceof check, but got undefined""}message: ""Expecting a function in instanceof check, but got undefined""stack: (...)get stack: function () { [native code] }arguments: nullcaller: nulllength: 0name: """"prototype: StackTraceGetterconstructor: function () { [native code] }arguments: nullcaller: nulllength: 0name: """"prototype: StackTraceGetterconstructor: function () { [native code] }arguments: nullcaller: nulllength: 0name: """"prototype: StackTraceGetterconstructor: function () { [native code] }arguments: nullcaller: nulllength: 0name: """"prototype: StackTraceGetter__proto__: function Empty() {}<function scope>__proto__: Object__defineGetter__: function __defineGetter__() { [native code] }__defineSetter__: function __defineSetter__() { [native code] }__lookupGetter__: function __lookupGetter__() { [native code] }__lookupSetter__: function __lookupSetter__() { [native code] }constructor: function Object() { [native code] }hasOwnProperty: function hasOwnProperty() { [native code] }isPrototypeOf: function isPrototypeOf() { [native code] }propertyIsEnumerable: function propertyIsEnumerable() { [native code] }toLocaleString: function toLocaleString() { [native code] }toString: function toString() { [native code] }valueOf: function valueOf() { [native code] }get __proto__: function __proto__() { [native code] }set __proto__: function __proto__() { [native code] }__proto__: function Empty() {}apply: function apply() { [native code] }arguments: nullbind: function bind() { [native code] }call: function call() { [native code] }caller: nullconstructor: function Function() { [native code] }length: 0name: ""Empty""toString: function toString() { [native code] }__proto__: Object<function scope><function scope>__proto__: Object__proto__: function Empty() {}apply: function apply() { [native code] }arguments: nullcaller: nulllength: 2name: ""apply""__proto__: function Empty() {}<function scope>arguments: nullbind: function bind() { [native code] }arguments: nullcaller: nulllength: 1name: ""bind""__proto__: function Empty() {}<function scope>call: function call() { [native code] }arguments: nullcaller: nulllength: 1name: ""call""__proto__: function Empty() {}<function scope>caller: nullconstructor: function Function() { [native code] }length: 0name: ""Empty""toString: function toString() { [native code] }__proto__: Object<function scope><function scope>__proto__: Object__proto__: function Empty() {}<function scope>set stack: function () { [native code] }arguments: nullcaller: nulllength: 1name: """"prototype: StackTraceSetter__proto__: function Empty() {}<function scope>__proto__: Error
+```",1417044265,PHID-USER-aost7ybqf3mbefvdfsdc,False,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_subcomment,NA
+VisualEditor is not displayed after clicking on Edit,"Aha. That means you didn't checkout the actual code for VisualEditor itself, just the MediaWiki extension that embeds it. You need to do `git submodule update --init `. See https://www.mediawiki.org/wiki/Extension:VisualEditor#Download.
+",1417041211,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_subcomment,NA
+VisualEditor is not displayed after clicking on Edit,"Maybe I found something:
+
+```
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: "".../extensions/VisualEditor/lib/ve/src/ve.track.js""' in .../includes/resourceloader/ResourceLoaderFileModule.php:843
+Stack trace:
+#0 .../includes/resourceloader/ResourceLoaderFileModule.php(362): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 .../includes/resourceloader/ResourceLoader.php(901): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 .../includes/resourceloader/ResourceLoader.php(647): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 .../load.php(45): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: "".../extensions/VisualEditor/lib/ve/src/ve.js""' in .../includes/resourceloader/ResourceLoaderFileModule.php:843
+Stack trace:
+#0 .../includes/resourceloader/ResourceLoaderFileModule.php(362): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 .../includes/resourceloader/ResourceLoader.php(901): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 .../includes/resourceloader/ResourceLoader.php(647): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 .../load.php(45): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+```
+The folder .../extensions/VisualEditor/lib/ve is empty, maybe something went wrong while downloading with git.",1417038630,PHID-USER-aost7ybqf3mbefvdfsdc,False,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_subcomment,NA
+VisualEditor is not displayed after clicking on Edit,What if any output is there on your browser's console log?,1417034461,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ff2rzzz5sv5pwbreaohw,task_subcomment,NA
+Mismatch between new page text seen by AbuseFilter and actual new page content,"On frwiki, we have false positives on a filter that tags edits that remove all categories.
+
+Filter: https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Filtre_antiabus/14
+Example of false positive: https://fr.wikipedia.org/w/index.php?title=Bertrand_Chameroy&diff=prev&oldid=109458887 (it should not have the tag ""suppression des catégories"")
+Details of the AbuseFilter log event: https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1204633
+
+I am sure that this is not an error in the filter itself, because in the details of the AbuseFilter log event, the diff shows that categories are indeed removed. But this diff does not match the real diff, where categories are unchanged.
+
+Expected behavior: the content of the 'new_text' variable of AbuseFilter should always match the new page text.
+
+I found 4 such false positives for this filter in the last two months. In all cases, modification also has the 'VisualEditor' tag, so this could be related.
+
+Other cases:
+https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1200961
+https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1190456
+https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1164028
+",1417029094,PHID-USER-5h57zgttfaaarfvo4g6s,False,PHID-TASK-g5mewjy3ybwuscrobyvx,task_description,duplicate
+"Cite inspector does not disappear upon clicking Insert, prevents page save","Edit any page in beta labs, e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Cite_VisualEditor_Test?vehidebetadialog=true&veaction=edit
+
+Click Cite and fill in the textareas
+
+Click Insert
+
+Cite inspector should disappear but does not. 
+
+Also note that the appearance of the Cite inspector is exceptionally small, in both Firefox and Chrome",1416844281,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-sx57fjn2ccu5x2lvqnvi,task_description,resolved
+"Cite inspector does not disappear upon clicking Insert, prevents page save",The issue is not reproducible anymore.,1423275793,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-sx57fjn2ccu5x2lvqnvi,task_subcomment,NA
+Newly made links are red until page is saved,"When I put in the template ""Infobox road"" onto a subpage of my user page, and added some parameters, the links they made were red.
+
+Screenshot link:
+
+[[https://en.wikipedia.org/wiki/File:Philroc-VEBug.png|The screenshot (red links circled)]]
+
+More info:
+
+[[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Newly_made_links_are_red_until_page_is_saved|The bug at Wikipedia]]
+
+I hope somebody gets to this soon.
+
+Thanks!",1416840250,PHID-USER-tx42osyrriffbzlseejv,False,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_description,invalid
+Newly made links are red until page is saved,"Right, it was T95247",1429147082,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,I can replicate the issue. I think it's separate - the reason those links get marked red is because their CE elements get a blank href element set somehow. Do you want to open a separate bug or shall I?,1429146825,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,"I don't know, but I'm seeing red links in Citoid.  It's in the initial
+display, not when you go back to look at it later.  I suspect that this is
+a separate bug, though.  (Steps to reproduce:  Add a ref to books.google.com;
+Insert; look at the red ISBN link.)",1427927039,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,Has this been fixed as T94315?,1427852197,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,This has re-appeared.  You can read the editor's report at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=651892335#Weird_bug_with_VE,1426661730,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,And feel free to reopen if you do still run into these issues,1421886602,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,Please try again. I think we fixed these issues already.,1421363927,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+Newly made links are red until page is saved,"Updating [[ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_4#Newly_made_links_are_red_until_page_is_saved | feedback page ]] link. This bug looks like a regression to me.
+Wittylama reported something similar today: <<See this edit https://en.wikipedia.org/w/index.php?title=National_Library_of_Australia&diff=636455550&oldid=636107184 - where I replace a raw link with the ""main"" template. Before saving, the Visual editor shows the link as a redlink and adds an extra line of whitespace above and below the new template. However, when I actually save the edit the link goes blue and the whitespace disappears. So, the saved result is exactly what I wanted to happen, but the visual editor 'preview' made it look like there were going to be two mistakes.>>",1417708202,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wh6hb2yzthpqgw4xqhff,task_subcomment,NA
+"""Maximum function nesting level"" fatal when visiting an imported page with nested conversations","I imported https://www.mediawiki.org/wiki/VisualEditor/Feedback into Flow with the LQT importer (plus some small changes for https://gerrit.wikimedia.org/r/#/c/172925/ that are probably not relevant to this bug).
+
+The import crashed (bug 73638), but a lot of stuff was already imported by then.  However, when I visit it, I get:
+
+""Fatal error: Maximum function nesting level of '200' reached, aborting""
+
+The stack is https://phabricator.wikimedia.org/P98 .
+
+It seems that the nesting level of a topic may influence the nesting level of the function stack, and cause it to go over the limit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416453300,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nscjwo6mgqab76opx5wt,task_description,declined
+"""Maximum function nesting level"" fatal when visiting an imported page with nested conversations","This error comes from xdebug.max_nesting_level.
+
+XDebug is not enabled in production, so we shouldn't have to worry about this.
+
+I confirmed it can be worked around locally by raising the limit or switching to HHVM.",1416454279,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nscjwo6mgqab76opx5wt,task_subcomment,NA
+"""Detected overflow for millisecond timestamp"" UID error when importing large LQT board into Flow","I hit this when testing https://gerrit.wikimedia.org/r/#/c/172925/ against https://www.mediawiki.org/wiki/VisualEditor/Feedback .
+
+So far I haven't retested against master, since the import is pretty slow.  I suspect it will be present there.
+
+Command was:
+
+mwscript extensions/Flow/maintenance/convertLqt.php --wiki=wiki User_talk:VE_Feedback_1 --allowunknownusernames 1 --remoteapi=https://www.mediawiki.org/w/api.php --srcpage=VisualEditor/Feedback --verbose 
+
+Log is https://phabricator.wikimedia.org/P97 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416452820,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-l54ayivuqbmpreuplbak,task_description,resolved
+"""Detected overflow for millisecond timestamp"" UID error when importing large LQT board into Flow","Change 174830 had a related patch set uploaded by EBernhardson:
+Bug: UID generator counter overflow
+
+https://gerrit.wikimedia.org/r/174830",1416522076,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l54ayivuqbmpreuplbak,task_subcomment,NA
+[Regression] VisualEditor: Switching to read mode after rendering diff leaves ve.ce.Surface behind,"Screenshot of Read mode after editing
+
+Steps to reproduce bug:
+
+1. Edit a page
+2. Insert some text or a table
+3. Click ""Save page"" in the toolbar
+4. Click ""Review your changes"" in the dialog
+5. Click ""Return to save form""
+6. Click ""Resume editing"" in the dialog
+7. Click ""Read"" tab from the MediaWiki navigation
+
+
+Expected:
+
+Original page re-appears.
+
+Actual:
+
+* The modified state from the editor persists.
+* Even the highlighting is still there (e.g. can highlight different cells in the table  we just inserted).
+* The ""Edit"" tab in the MW nav is now broken (clicking it does nothing, no exception thrown).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15110}",1416363840,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2zl7jj2byve5amcxz4nc,task_description,resolved
+[Regression] VisualEditor: Switching to read mode after rendering diff leaves ve.ce.Surface behind,"
+
+*** This bug has been marked as a duplicate of bug 73589 ***",1416364083,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2zl7jj2byve5amcxz4nc,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"switch edit mode fails in Chrome
+
+This manifests in several ways, see the browser test failures at
+Chrome: https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+Firefox: https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/
+
+The common case for Chrome and Firefox:
+
+As a logged-in user with access to VisualEditor, edit any page. 
+Attempt to switch from the wikitext editor to VE using the dropdown controls. 
+Nothing happens, VE does not show up.  See screen shot. 
+
+The Firefox-only issue: 
+
+Attempt to edit a new page by supplying a bogus URL, e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Foobarbaz
+
+Clicking the edit icon does nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15094}",1416354960,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-a27c6scsdqjxaingm45j,task_description,resolved
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,I can edit new pages on Firefox so I think this has been fixed. Please reopen if you can still duplicate it.,1416813191,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"**gerritadmin** wrote:
+
+Change 174384 abandoned by Florianschmidtwelzow:
+Don't try to set cursor on hidden elements
+
+Reason:
+Function reverted in: I672d04c16f9348f7e08c4f64b339b307276d2a5a
+
+https://gerrit.wikimedia.org/r/174384",1416517242,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,I captured the other issue in bug 73646,1416483048,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,If there are two problems here there should be 2 bugs..,1416479425,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"okay,just to keep note, this bug is now in test2 as well after today's deployment since it was regression from wmf9.I will test the fix in test2 once it is merged and backported.",1416451353,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"Unhappily no, this patch adresses the Firefox problem. For now, I haven't had the time to look into it, why VE doesn't work :/",1416434101,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"Ah got it, so this patch is going to fix for all pages in all browsers?",1416433265,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"Jon is talking about the Firefox only problem :) The VE problem is right, it doesn't work on all pages :(",1416432160,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"Nope, this is not a browser/page specific issue,was happening for me in all pages even in iOS safari.Once you switch to edit source mode the ""Edit"" button will no longer work from that point on.And then for a new page, it always opens the Edit Source mode first, so thats why its always reproducible for a new page too.",1416424643,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,This seems to be specific for new pages in Firefox.,1416421472,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"**gerritadmin** wrote:
+
+Change 174384 had a related patch set uploaded by Florianschmidtwelzow:
+Don't try to set cursor on hidden elements
+
+https://gerrit.wikimedia.org/r/174384",1416388806,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"For the second (FF only):
+[10:11:21.144] ""[Exception... ""Failure""  nsresult: ""0x80004005 (NS_ERROR_FAILURE)""  location: ""JS frame :: http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141030T090804Z :: EditorOverlay<._loadContent/< :: line 17""  data: no]"" [object XPCWrappedNative_NoHelper]
+
+Caused by: I2a3eab234338bae6258abcde99144bdd2464805f
+
+VE: confirmed :/",1416388781,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/LKgERdDV",1416355223,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-a27c6scsdqjxaingm45j,task_subcomment,NA
+VisualEditor:[Regression pre-wmf9] Inserted Media caption is not displayed correctly,"Caption without background
+
+Betalabs only in Chrome, FF, and Safari. test2 is fine.
+
+
+VE - Insert Media and enter Caption - save the page. The Media caption is displayed with white background. 
+See the attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15369}",1416006000,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-khh4rz3t6eqnbtz47oby,task_description,invalid
+VisualEditor:[Regression pre-wmf9] Inserted Media caption is not displayed correctly,"This is how Beta Labs is configured, irritatingly.",1416433677,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-khh4rz3t6eqnbtz47oby,task_subcomment,NA
+small race condition in Links inspector,"Edit a page on beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Links_VisualEditor_Test?vehidebetadialog=true&veaction=edit
+
+Click the Links inspector
+
+Note that the ""Done"" button is enabled
+
+Quickly paste (do not type by hand) an external link e.g. http://www.example.com in the link field
+
+Note that upon pasting ""http://www.example.com"", VE takes some time before displaying the ""External link/New page"" overlay. 
+
+If the user clicks ""Done"" after pasting text in the link field but before the ""External link/New page"" overlay appears, VE creates a local link [[foo]] instead of the desired external link [http://www.example.com foo]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415985120,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-sk5dddkhjvxvi76fjcya,task_description,resolved
+small race condition in Links inspector,"Re-checked in betalabs - there is no noticeable delay in displaying ""External link/New page"" overlay(some performance improvements were made). ",1423276267,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-sk5dddkhjvxvi76fjcya,task_subcomment,NA
+VisualEditor: Safari - white spaces are dropped for copied formatted text,"Safari cut and paste formatted text-white spaces issue
+
+Steps to reproduce: 
+
+Safari only - test2, Betalabs.
+
+1. In VE type some text - e.g. underlined text. Apply underlined format to 'underlined'.
+
+2. Highlight 'underlined text' and copy/paste it somewhere else on the page. 
+
+It will be displayed as: underlinedtext. Underlined formatting will be gone and a white space between words is lost. 
+
+This is affecting many options in formatted text - see the attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15096}",1415831700,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_description,resolved
+VisualEditor: Safari - white spaces are dropped for copied formatted text,This was verified in betalabs.  It is sort of a  test case for the bug fix for 71718.,1416265549,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_subcomment,NA
+VisualEditor: Safari - white spaces are dropped for copied formatted text,"
+
+*** This bug has been marked as a duplicate of bug 71718 ***",1415898350,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_subcomment,NA
+VisualEditor: Safari - white spaces are dropped for copied formatted text,Syntax fix: bug 71718,1415892093,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_subcomment,NA
+VisualEditor: Safari - white spaces are dropped for copied formatted text,"Duplicate of [[bug 71718]], I think.",1415890623,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2wk7ydj7z2mxwtrff6by,task_subcomment,NA
+VisualEditor: Using the VE toolbar in MSIE causes the cursor to jump to the start of the page,"Saw lots of bugs reported and fixed about the jumping of focus when using the toolbar.  Now seeing the problem in MSIE for many uses of the toolbar.  Would like a clue about fixing it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415771100,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-eohxemedb6jupuzhjihr,task_description,duplicate
+VisualEditor: Using the VE toolbar in MSIE causes the cursor to jump to the start of the page,Related bug/fix? T66041 ,1427391137,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-eohxemedb6jupuzhjihr,task_subcomment,NA
+VisualEditor: Using the VE toolbar in MSIE causes the cursor to jump to the start of the page,"Some examples when a page scrolls up in IE11 
+
+- Using Backspace button 
+
+- changing existing Page title, Heading, and sub-headings to other format",1415821431,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-eohxemedb6jupuzhjihr,task_subcomment,NA
+VisualEditor: Paste from Word to MSIE fails to insert anything,"Pasting anything besides plain text into MSIE fails.  Tried this with Word in FF and Chrome (see bug #73292) and had at least some success.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415766540,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-hiemxvbjccwrbpce5noi,task_description,resolved
+VisualEditor: Paste from Word to MSIE fails to insert anything,Closing this for now since it has been solved elsewhere.  At least *some* pasting works.,1429106123,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-hiemxvbjccwrbpce5noi,task_subcomment,NA
+VisualEditor: Paste from Word to MSIE fails to insert anything,Also bug 65714 comment 2.,1415767124,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-hiemxvbjccwrbpce5noi,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","When the categories suggested in the drop down are long enough, a scroll bar appears.  Clicking on this scroll bar causes the drop down to close.
+
+
+It would be nice if you could use the scrollbar like others -- to scroll up and down the list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415743920,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_description,resolved
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","
+
+*** This bug has been marked as a duplicate of bug 65774 ***",1415843475,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","Change 172933 had a related patch set uploaded by Catrope:
+Don't close PopupToolGroups when the scroll bar is clicked
+
+https://gerrit.wikimedia.org/r/172933",1415843388,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","Merging into bug 65774.
+
+*** This bug has been marked as a duplicate of bug 65774 ***",1415807884,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","Change 172723 had a related patch set uploaded by Alex Monk:
+MenuWidget: Don't close menu when you click the scroll bar
+
+https://gerrit.wikimedia.org/r/172723",1415802742,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","Okay, I was just lucky and the last category would fit always without a scroll bar, unless I changed the window height. This feels like a duplicate bug though...",1415753833,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown","I've reproduced this on https://www.mediawiki.org/wiki/Project:Sandbox?veaction=edit using Chrome and Firefox on Windows and Linux.
+
+What steps are you trying?  Maybe I need to provide more information?",1415752854,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown",Can't reproduce...,1415749132,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wwj7ivjxi3mj6jsc3tc6,task_subcomment,NA
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style","Enviornment-test2, beta
+
+1> Select language and click done, when the language inspector opens.
+2>type some text ,on the CE.
+//the text has language style
+3>now place the cursor to the start of the line and type in some more text.
+// also has the language  style
+4> after typing the additional text insert a space. Then delete that space.
+Notice the cursor moves to the start of the line and also the language annotation from the recently typed text has been removed. Whereas the previously typed text still retains the annotation style.
+
+See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1415627460,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ksiwshyonkquzpb6aoz4,task_description,resolved
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style",The issue was checked - does not exist anymore. ,1423524357,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ksiwshyonkquzpb6aoz4,task_subcomment,NA
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style","Confirmed. 
+
+The scenario for the issue is actually simpler. 
+
+1. Select language and click done, when the language inspector opens.
+2. type some text ,on the CE.
+3. then add text to the beginning of the line - just start typing something and after some text click delete as if you were to correct something - all entered text  from your cursor to the beginning of the line will be deleted.",1415646640,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ksiwshyonkquzpb6aoz4,task_subcomment,NA
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style",Also found in FF 33.1.,1415631019,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ksiwshyonkquzpb6aoz4,task_subcomment,NA
+"VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style",http://youtu.be/qzzJDdPJGQY,1415630681,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ksiwshyonkquzpb6aoz4,task_subcomment,NA
+VisualEditor: Can't delete text... which is actually not there,"User added the words ""La mui"" to https://fr.wikipedia.org/wiki/Audiomachine#Utilisations_de_leurs_musiques . Then proceeded to edit elsewhere in the page. When he went back to those words, he found out he couldn't remove them at all (see screencast at https://www.youtube.com/watch?v=IMlMZt1FMvY : all his actions seem to affect the header below). When he reviews his changes, that content is actually not there.
+
+Windows 7, Firefox Aurora 35.0a2 (2014-11-05), Vector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415610300,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-3jzj5p7wyiyt5e2ugrkb,task_description,resolved
+VisualEditor: Can't delete text... which is actually not there,"Could not reproduce. Sometime when a user session has been open for long and/or editing has taken long time(many edits) - UI becomes somewhat irresponsive. 
+However, no specific and reproducible details have been reported yet. ",1423692980,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-3jzj5p7wyiyt5e2ugrkb,task_subcomment,NA
+VisualEditor: Can't delete text... which is actually not there,"(In reply to Ed Sanders from comment #1)
+> Can't reproduce this.
+I am the user to which it happened. I actually don't know how it happened, I did nothing special as far as I can remember. Elitre has suggested it may be because of my PC (I have sometimes other bugs that happen only to me). However the same bug or an extremely similar one also happened to me last year (in November 2013) but with my old PC with Firefox and Windows 7.",1415661001,PHID-USER-4cgt73x34j35pnbem65l,True,PHID-TASK-3jzj5p7wyiyt5e2ugrkb,task_subcomment,NA
+VisualEditor: Can't delete text... which is actually not there,Can't reproduce this.,1415648109,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-3jzj5p7wyiyt5e2ugrkb,task_subcomment,NA
+VisualEditor: Tables wikitext can be inconsistent,"In wikitext editor, you can separate cells with a double bar ""||"" on the same line :
+
+|Cell 1 || Cell 2 || Cell 3
+
+(same thing for headers, except two exclamation marks ""!!"" are used).
+
+When adding a new cell with VE, the result will look like
+|Cell 1 || Cell 2 || Cell 3
+|Cell 4
+
+rather than |Cell 1 || Cell 2 || Cell 3 || Cell 4 .
+
+While this still works, it makes the table less understandable and usable for those who do not use VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415608980,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5bbju6mqrb4hytvcocfv,task_description,duplicate
+VisualEditor: Tables wikitext can be inconsistent,"Merging into bug 63356; ideally we'd want Parsoid to use inline or per-line syntax per precedent in the context, which sounds messy.
+
+*** This bug has been marked as a duplicate of bug 63356 ***",1415618411,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5bbju6mqrb4hytvcocfv,task_subcomment,NA
+VisualEditor: Annotation on top of a link produces inefficient wikitext ([[asd|''asd'']]),"Annotation on top of a link produces inefficient wikitext ([[asd|''asd'']]).
+
+1. Type text, for example ""asd"".
+2. Select it.
+3. Press Ctrl+K to create a link, accept ""asd"" as link target.
+4. Press Ctrl+I to italicize.
+
+Result: [[asd|''asd'']].
+
+Compare with:
+
+1. Type text, for example ""asd"".
+2. Select it.
+3. Press Ctrl+I to italicize.
+4. Press Ctrl+K to create a link, accept ""asd"" as link target.
+
+Result: ''[[asd]]''.
+
+I would expect both ways to produce the same wikitext, ''[[asd]]''.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415552880,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kkuldyxop75uyhtvgofe,task_description,resolved
+VisualEditor: Annotation on top of a link produces inefficient wikitext ([[asd|''asd'']]),"Yeah, merging with bug 50098.
+
+*** This bug has been marked as a duplicate of bug 50098 ***",1415618227,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kkuldyxop75uyhtvgofe,task_subcomment,NA
+VisualEditor: Annotation on top of a link produces inefficient wikitext ([[asd|''asd'']]),bug 50098 ?,1415605943,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-kkuldyxop75uyhtvgofe,task_subcomment,NA
+"VisualEditor: [regression] Inserting new internal link inserts text, but doesn't linkify it, if you complete the dialog before page title suggestions appear","Inserting new internal link inserts text, but doesn't linkify it.
+
+1. Place cursor on empty paragraph
+2. Open the link inspector (Ctrl+K)
+3. Type in title of a page and press Enter
+
+A new link to that page should appear. Instead, only the text typed is inserted, without the link annotation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415543760,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-zk2f2rtykxd7etnlrmtb,task_description,resolved
+"VisualEditor: [regression] Inserting new internal link inserts text, but doesn't linkify it, if you complete the dialog before page title suggestions appear","Seems that you need to complete the dialog before page title suggestions appear, so just press Enter really quickly after typing.",1415547012,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-zk2f2rtykxd7etnlrmtb,task_subcomment,NA
+"VisualEditor: Newly added template added with ""Template:"" prefix","https://www.mediawiki.org/w/index.php?title=Google_Code-in_2014&diff=1255073&oldid=1255066
+
+Newly added ""Bug"" template was added as {{Template:Bug|…}} rather than just {{Bug|…}}. As far as I know I did nothing special to cause that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415462520,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-7h5p3whd42ak5tbojlbc,task_description,resolved
+"VisualEditor: Newly added template added with ""Template:"" prefix",Verified on www.mediawiki.org - the Bug template added as {{Bug|73179}}.,1416260589,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-7h5p3whd42ak5tbojlbc,task_subcomment,NA
+"VisualEditor: Newly added template added with ""Template:"" prefix",Should've been fixed by Roan in Gerrit change 172319.,1416188116,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-7h5p3whd42ak5tbojlbc,task_subcomment,NA
+Get Parsoid (and thus VisualEditor) working again on Wikitech,"They broke and were disabled, but we should get them back.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415318040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vkpbe46usd5elh6546nv,task_description,resolved
+Get Parsoid (and thus VisualEditor) working again on Wikitech,Looks like this was fixed at some point.,1426689638,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-vkpbe46usd5elh6546nv,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"flow_tree_revision
+
+Parsoid is running happily. I can edit pages using VisualEditor without issue.
+
+I can visit a Flow page and add a new topic or comment. However, upon saving I don’t actually see the content of the comment. Topic titles do show up.
+
+I’m not a DB guru, but upon inspecting the flow-specific database tables I noticed some weird syntax in the fields. Maybe it’s my editor (Sequel Pro) or an encoding issue.
+
+I turned on MW debugging and I see this message:
+
+Warning: DOMDocument::saveHTML() expects exactly 0 parameters, 1 given in /var/www/html/w/extensions/Flow/includes/Parsoid/Utils.php on line 273
+
+1.25wmf5, PHP 5.3.3, most recent head/master build of Flow, most recent build of Parsoid.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+
+**Attached**: {F15052}",1415226120,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_description,declined
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"While this is incredibly specific to my situation, I would like to point out that PHP 5.3.3 is still the standard version provided with RHEL-6. Which isn't the latest version, but still supported by Redhat.
+
+Again, I realize this extension is a WMF-focused endeavor, but it's too cool to not be used elsewhere. :)
+
+I'm off to argue with my linux sysadmins on updating PHP. Wish me luck!",1415905967,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"https://www.mediawiki.org/wiki/Extension:Flow now documents Flow's php 5.3.6+ requirement. I'm proposing WONTFIX, although patches welcome.",1415386992,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),I just tested on a system with 5.6.1 - Flow works as intended.,1415299051,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Erik is right.  Core requires 5.3.3, so we have the option of keeping support for that or documenting requiring 5.3.6.  The former may be doable if it's not much work, but core will probably bump above that soon anyway.",1415234960,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Actually i didn't read close enough, you are on 5.3.3.  I'm almost certain the problem is that, and we will have to update Flow's minimum requirements to 5.3.6.",1415234734,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"The problem with DOMDocument::saveHTML is most likely our issue, it looks like that argument was added in php 5.3.6
+
+Which version of php are you on?  I think we advertise support of 5.3.3, but we might need to bump that.",1415234562,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Sorry, I should have checked your screenshots first.  I see it's MySQL.  The weird characters are the binary UUID values.  Basically, consider the ID an arbitrary blob of bits (it does appear in the UI, serialized, in some places, e.g. in Topic URLs).
+
+I'm not sure why it's not working, though.",1415234520,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"What database engine are you using (MySQL, PostegreSQL, etc.)?",1415234334,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Created attachment 17047
+mystery comments
+
+**Attached**: {F15054}",1415226207,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core),"Created attachment 17046
+flow_revision
+
+**Attached**: {F15053}",1415226159,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-yrjidyow5pz4cmjn4or3,task_subcomment,NA
+VisualEditor Mobile: Calling VisualEditor from MF spins forever,"As a logged in user with VE available, edit any page in beta labs e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Cyrion_and_Candidus#/editor/0
+
+Page is white and shows spinner, editor never appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415213400,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ju3dj4ysqtrezth635p2,task_description,resolved
+VisualEditor Mobile: Calling VisualEditor from MF spins forever,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/z22jBbGj",1415213714,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ju3dj4ysqtrezth635p2,task_subcomment,NA
+VisualEditor Mobile: Calling VisualEditor from MF spins forever,"
+
+*** This bug has been marked as a duplicate of bug 73038 ***",1415213710,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ju3dj4ysqtrezth635p2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,"Safari blurs text
+
+1. Open a page in Safari VE Read mode - the text is displayed normally.
+
+2. Switch to Edit  - the beginning of the page displays a blurred text.
+Clicking in the text does not make it clearer. 
+
+See the attached screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15010}",1415209920,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,Now seems fine?,1417578010,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,"Created attachment 17040
+Safari Read mode - text s clear
+
+**Attached**: {F15011}",1415212973,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,"Created attachment 17039
+Safari Read mode - text is clear
+
+//attachment Safari Read mode.png ignored as obsolete//",1415210338,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode,"Created attachment 17038
+Safari displays clear text in Read mode
+
+//attachment Safari Read mode.png ignored as obsolete//",1415210103,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3x3n5ljioxs67z2z7nhc,task_subcomment,NA
+Fix the language screenshot test for new VE architecture,"VE no longer has iframes.  I don't really understand how ""iframe_element"" is being used: 
+
+$ grep -r ""iframe_element"" *
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, -2)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, -2)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Page_Settings_Redirects-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.page_settings_heading_element, @current_page.prevent_redirect_element], @current_page.iframe_element, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Page_Settings_TOC-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.table_of_contents_element], @current_page.iframe_element, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Page_Settings_Edit_Links-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.page_settings_editlinks_element], @current_page.iframe_element, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Apply_Changes-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.settings_apply_button_element], @current_page.iframe_element, 3)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.link_list_element, @current_page.iframe_element, @current_page.new_link_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element])
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""VisualEditor_Media_alternative_text-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.media_alternative_block_element], @current_page.iframe_element)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element])
+features/step_definitions/language_screenshot_steps.rb:    page.iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element, @current_page.formula_image_element], nil, 0)
+features/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible
+features/step_definitions/language_screenshot_steps.rb:  capture_screenshot(""#{@scenario.name}-#{ENV['LANGUAGE_SCREENSHOT_CODE']}.png"", [@current_page.iframe_element], nil, 0)
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1415209320,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-6l5wjfkbykj3jdrufonn,task_description,resolved
+Fix the language screenshot test for new VE architecture,"**gerritadmin** wrote:
+
+Change 171531 merged by jenkins-bot:
+[BrowserTest] Fixed failing language screenshot browser tests
+
+https://gerrit.wikimedia.org/r/171531",1415624810,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6l5wjfkbykj3jdrufonn,task_subcomment,NA
+Fix the language screenshot test for new VE architecture,"**gerritadmin** wrote:
+
+Change 171531 had a related patch set uploaded by Vikassy:
+Fixed failing browser tests
+
+https://gerrit.wikimedia.org/r/171531",1415276609,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6l5wjfkbykj3jdrufonn,task_subcomment,NA
+Fix the language screenshot test for new VE architecture,"Vikas, can you take a look?
+
+Amir, if Vikas does not have the time to fix this, we could work on it during our regular pairing sessions.",1415265896,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-6l5wjfkbykj3jdrufonn,task_subcomment,NA
+VisualEditor: Safari only - typing text in a table cell - the page scrolls up,"1. Safari - open any page and make sure that a page has enough content to have a vertical scrollbar. 
+
+2. Insert a table at the bottom of the page.
+
+Start typing in a table cell - the page scrolls up with each typed character.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415149320,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-vgdeswcro65dp4sojtrt,task_description,resolved
+VisualEditor: Safari only - typing text in a table cell - the page scrolls up,This was resolved some time ago.,1417577587,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vgdeswcro65dp4sojtrt,task_subcomment,NA
+VisualEditor: line height in intro message is wrong causes collusions,"text collisions
+
+line height should be increased to not have text and controls run together.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14807}",1415128920,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-sz7lovyjgkskrmxay2d6,task_description,invalid
+VisualEditor: line height in intro message is wrong causes collusions,"on en.wiki:
+
+go to article bonshō, click edit beta.",1415145904,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-sz7lovyjgkskrmxay2d6,task_subcomment,NA
+VisualEditor: line height in intro message is wrong causes collusions,"...and in general, steps to reproduce (which site is this about?) are welcome.",1415139729,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-sz7lovyjgkskrmxay2d6,task_subcomment,NA
+VisualEditor: line height in intro message is wrong causes collusions,Local per-wiki templates need to be fixed locally…,1415130154,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sz7lovyjgkskrmxay2d6,task_subcomment,NA
+VisualEditor: featured article template is hidden and easy to accidently delete,"icon not showing in VE
+
+the featured article template added a significant amount of blank headspace to articles and doesn't draw the icon, so it is easy to accidently delete.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14803}",1415128800,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-t4mn4nb76mzz3ahxoggz,task_description,resolved
+VisualEditor: featured article template is hidden and easy to accidently delete,"
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1415129033,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-t4mn4nb76mzz3ahxoggz,task_subcomment,NA
+VisualEditor: unexpected results while copy/pasting reference contents,"See https://www.mediawiki.org/w/index.php?title=User:Elitre_(WMF)/sandbox&diff=prev&oldid=1249997 .
+
+References at the words ""this"" were created by copy/pasting the contents of the reference at the word ""complex"".
+
+Notice:
+1) The spaces between the elements get removed (Bug 71718?)
+2) The wikilink gets changed;
+3) If you selected until after the ""citation needed"" template only, this wouldn't appear when pasting (Bug 49396?).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415024640,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-altlbz4ow72qgwhpfdya,task_description,resolved
+VisualEditor: unexpected results while copy/pasting reference contents,"(In reply to Elitre from comment #0)
+> See
+> https://www.mediawiki.org/w/index.php?title=User:Elitre_(WMF)/
+> sandbox&diff=prev&oldid=1249997 .
+> 
+> References at the words ""this"" were created by copy/pasting the contents of
+> the reference at the word ""complex"".
+> 
+> Notice:
+> 1) The spaces between the elements get removed (Bug 71718?)
+
+Looks like.
+
+> 2) The wikilink gets changed;
+
+This is bug 70743.
+
+> 3) If you selected until after the ""citation needed"" template only, this
+> wouldn't appear when pasting (Bug 49396?).
+
+That bit works for me?
+
+Merging with bug 71718.
+
+*** This bug has been marked as a duplicate of bug 71718 ***",1415063629,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-altlbz4ow72qgwhpfdya,task_subcomment,NA
+"VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down","Steps to reproduce:
+
+1.Insert a table
+2.Add any focusable node inside content cell like template/image/math function
+3.Place the cursor at the end of the table
+
+Observed Result:
+The page scrolls down to the end of it
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414734360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h3ux7jbm3qrdgpuszex2,task_description,duplicate
+"VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down","Oh *that* outside of the table. Yeah - you're not supposed to put your cursor there...
+
+*** This bug has been marked as a duplicate of bug 71560 ***",1415203500,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-h3ux7jbm3qrdgpuszex2,task_subcomment,NA
+"VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down","Created attachment 17002
+video capture
+
+Still happening for me , See the video capture
+
+**Attached**: {F15093}",1415045420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h3ux7jbm3qrdgpuszex2,task_subcomment,NA
+"VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down",Works for me in Chrome & FF,1415025275,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-h3ux7jbm3qrdgpuszex2,task_subcomment,NA
+"VisualEditor does not display Files, and can not access the local files","**Author:** `lhug`
+
+**Description:**
+Intention:
+Trying to edit a page with linked files on a private wiki. Mainly to test if the Visual Editor functions are usable.
+
+Steps to Reproduce:
+1. Open page with a linked file
+2. click ""edit""
+3. wait and see
+
+Actual Results:  
+The linked file simply disappears and is not visible to the editor. after saving, it is accessible again. Trying to insert media showed no local media.
+
+Expected Results:  
+Picture is editable of course, and at least a list of media to add.
+
+Reproducible: Always
+
+Using vector as skin. Changing skin did not resolve the issue. Wiki is running on a CentOS with self certified SSL. 
+Accessing files that are on the commons is possible, and these are viewable by the editor. Copying the Link properties to other media links does not help, they are still invisible to the editor. Normal Text is editable and media are accessible there. Tried Workarounds found on several pages:
+
+Changing permissions to all-read-true and/or all-read-edit-true did not resolve the issue. (in fact, if I do that, many pictures are not viewable - they are still there and linked, but show broken image)
+Granting the ImageSearch read permissions did not help.
+granting localhost, 127.0.0.1, our url and our IP read permissions did not help.
+2 API-Queries returned expected results (https://dpaste.de/0Adz for ?action=query&prop=imageinfo&iiprop=url|size&iiurlwidth=220&titles=File:Logo.jpg&format=json and ?action=query&prop=imageinfo&iiprop=url|size&titles=File:Logo.jpg&format=json
+
+Locally (on a Ubuntu machine) the pictures are being shown, yet the local media repo is empty to the VE.
+
+We are running parsoid as a service run by root, the log file reports API request failed when trying to edit a page with pictures in it.
+
+The used versions are MediaWiki 1.23.5, VE Snapshot 1.23, nodejs 0.10.30, Parsoid snapshot 1.23
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414670820,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5jsfxjyzrxm3or6trnvk,task_description,invalid
+"VisualEditor does not display Files, and can not access the local files","This bug could not be reproduced and is now three years old, so I'm closing.",1513167417,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-5jsfxjyzrxm3or6trnvk,task_subcomment,NA
+"VisualEditor does not display Files, and can not access the local files","**lhug** wrote:
+
+Parsoid Log w. debug
+
+This is the Parsoid log with debugging info when opening a page with a picture in it. Since I have no idea what exactly is happening in that parsoid service, or when it happens, maybe someone else can tell me what to do with this.
+
+The fails API-request is easily notable
+
+**Attached**: {F14960}",1414674704,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5jsfxjyzrxm3or6trnvk,task_subcomment,NA
+"VisualEditor does not display Files, and can not access the local files","**lhug** wrote:
+
+A direct call of the api query the VE starts shows definite parsing errors.
+https://dpaste.de/8AhK is the result of the API-Query on the live system.
+
+https://dpaste.de/DKwm is the result of the same page on the local system.
+
+Notice the imagelinks in the first link are still in [[]].",1414673006,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5jsfxjyzrxm3or6trnvk,task_subcomment,NA
+Build jsduck through Gruntfile,"VisualEditor build documentation via Grunt [1] and publish via Jenkins.
+One of the benefits of this is you can use a jsduckcatconfig that pulls in documentation from core.
+
+We should do the same.
+
+[1] https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor/f35d577acb57319241ea992a95cb045298662cd8/Gruntfile.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414622580,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-kvh4xexeziejdfpxnqcl,task_description,resolved
+Build jsduck through Gruntfile,"Change 174851 merged by jenkins-bot:
+Run jsduck through grunt
+
+[[https://gerrit.wikimedia.org/r/174851]]",1417427917,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kvh4xexeziejdfpxnqcl,task_subcomment,NA
+Build jsduck through Gruntfile,"Change 174851 had a related patch set uploaded by Bmansurov:
+Run jsduck through grunt
+
+https://gerrit.wikimedia.org/r/174851",1416526479,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kvh4xexeziejdfpxnqcl,task_subcomment,NA
+Build jsduck through Gruntfile,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/w96Isqis",1414622716,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kvh4xexeziejdfpxnqcl,task_subcomment,NA
+VisualEditor Mobile: There is no Preview bar appearing at the top in iOS Safari for tablet and desktop browser while saving the edited content,"screenshot in desktop browser
+
+Steps to reproduce:
+
+1.Open the wikitext editor for any page in en.m.wikipedia.org 
+2.Make some edit
+3.Click on ""Next""
+
+Observed Result:
+
+There is no preview bar appearing at the top of the page indicating it's a preview as it does in iOS safari for iPhone.
+
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14824}",1414619880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rff3kdscndxezxto7luz,task_description,invalid
+VisualEditor Mobile: There is no Preview bar appearing at the top in iOS Safari for tablet and desktop browser while saving the edited content,Duplicate of T76624,1418171147,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-rff3kdscndxezxto7luz,task_subcomment,NA
+VisualEditor Mobile: There is no Preview bar appearing at the top in iOS Safari for tablet and desktop browser while saving the edited content,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/C7zx3kLC",1414620014,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rff3kdscndxezxto7luz,task_subcomment,NA
+VisualEditor Mobile: There is no Preview bar appearing at the top in iOS Safari for tablet and desktop browser while saving the edited content,"Created attachment 16947
+screenshot from iPhone
+
+**Attached**: {F14825}",1414620011,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rff3kdscndxezxto7luz,task_subcomment,NA
+Newly filed bugs with empty description are not accounced on IRC,"Newly filed bugs with empty description are not accounced on IRC. Bug 72705 wasn't pushed to #mediawiki-visualeditor when I filed it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414619700,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-alwvf22pdixzdjmak4za,task_description,resolved
+Newly filed bugs with empty description are not accounced on IRC,"Yeah, Bugzilla doesn't send messages to wikibugs-l, so pywikibugs cannot report anything. See #64836.
+
+*** This bug has been marked as a duplicate of bug 64836 ***",1414620496,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-alwvf22pdixzdjmak4za,task_subcomment,NA
+Issues with icons in alpha. Get fixed so we can move it to beta.,"* CtaDrawer down icon is not centered
+* Switcher in VisualEditor/Wikitext editor
+* Notification icon tiny mw-ui-icon-notification isn't sized correctly – font-size: 1.3em
+* Clicking the notification icon doesn't hide it while the notifications are loading
+* #page-actions .mw-ui-icon:before (the page actions) margin needs to be lowered
+Animation of the watchstar is broken
+* Toggleable (?) elements (Contents, section headings) don't have cursor: pointer
+* Watch star in page actions moves slightly to the left every time you click it
+* Provide SVG versions of all icons which currently only use SVGS
+The watchstar in the search results is tiny
+.mw-ui-icon-arrow-up isn't positioned hard-right when Contents is open
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414539120,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-dikhm6z5abefq6sfybiz,task_description,invalid
+Issues with icons in alpha. Get fixed so we can move it to beta.,I split this into various bugs to be more actionable,1415228819,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-dikhm6z5abefq6sfybiz,task_subcomment,NA
+Issues with icons in alpha. Get fixed so we can move it to beta.,"Also:
+* face icon (logged in vor not logged in) in Special:MobileDiff repeats itself",1414911471,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-dikhm6z5abefq6sfybiz,task_subcomment,NA
+Issues with icons in alpha. Get fixed so we can move it to beta.,"Also 
+* close icon in image overlay repeats itself",1414613484,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-dikhm6z5abefq6sfybiz,task_subcomment,NA
+Issues with icons in alpha. Get fixed so we can move it to beta.,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/Vh51EzgU",1414539310,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dikhm6z5abefq6sfybiz,task_subcomment,NA
+VisualEditor edit summary is not saved,"Example: https://www.mediawiki.org/w/index.php?title=Project%3ASandbox&diff=1242918&oldid=1242833
+
+Summary input: ""Test"". The summary was not saved.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414484940,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_description,resolved
+VisualEditor edit summary is not saved,"No, sry for delay.",1416062866,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"All patches mentioned in this report were merged or abandoned - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?",1416054282,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169953 merged by jenkins-bot:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169953",1414624795,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169952 merged by MaxSem:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169952",1414624577,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169953 had a related patch set uploaded by MaxSem:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169953",1414624551,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169952 had a related patch set uploaded by MaxSem:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169952",1414624527,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Maybe LD this patch in the next SWAT? The latest wmf branch was created today (without this patch), so Wikipedias will get thid patch in 14 days, which is a long time :/
+
+The edit summary is an important feature to summarize an edit, it's bad, that a users summary message will not be saved and a reviewer maybe think the user doesn't submitted a summary.",1414623408,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169778 merged by jenkins-bot:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169778",1414614516,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Change 169778 had a related patch set uploaded by Bmansurov:
+Save summary in VisualEditor
+
+https://gerrit.wikimedia.org/r/169778",1414610567,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"Hmm :/ I tested it again: https://m.mediawiki.org/wiki/Special:MobileDiff/1245793
+
+Used Chrome desktop and stable mode. Clicked the lead section edit, write down some test text and click save. In the ""Summary"" field i insert ""Test submit"" and clicked save. The edit is saved, but not the summary :(",1414605927,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"I'm not able to reproduce. My summary has been saved correctly:
+https://www.mediawiki.org/w/index.php?title=Project%3ASandbox&diff=1245788&oldid=1245681
+
+also this: https://www.mediawiki.org/w/index.php?title=Project%3ASandbox&diff=1245791&oldid=1245788
+
+Can you give me instructions how to reproduce this?",1414605618,PHID-USER-grftjc3ekkyjf6bwlsqi,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+VisualEditor edit summary is not saved,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/9UaadG2M",1414485010,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pquqanuuilo2pfgkwyps,task_subcomment,NA
+Jenkins: Create and enable MobileFrontend npm test job,"I notice VisualEditor has lots of Grunt magic. If I'm not mistaken the Gruntfile on each merge [1].
+
+Can a similar job be setup on mobile and could I grab one of either Krinkle and Antoine to see what else Mobile can do to get the most out of this Gruntfile?
+
+[1] https://integration.wikimedia.org/ci/job/oojs-ui-npm/1740/console
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1414453200,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_description,resolved
+Jenkins: Create and enable MobileFrontend npm test job,Fixed by @Jdlrobson who added the necessary npm  / package.json entries and crafted the Jenkins jobs.,1416824815,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_subcomment,NA
+Jenkins: Create and enable MobileFrontend npm test job,"Change 174696 had a related patch set uploaded by Krinkle:
+Add mwext-MobileFrontend-npm job
+
+https://gerrit.wikimedia.org/r/174696",1416506232,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_subcomment,NA
+Jenkins: Create and enable MobileFrontend npm test job,"The Gruntfile is created. Is there anything else we need to do? I'm not sure what you mean by ""once its working"" does this mean working locally or working in some other form?",1414532750,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_subcomment,NA
+Jenkins: Create and enable MobileFrontend npm test job,"Creation of Gruntfile is to be done by MF maintainers. Once it's working, let me know and I'll create/enable the job. Or alternatively, submit a patch to integration-config (should be a 2-3 line change) that I'll merge/deploy.",1414523483,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pt3ytqx2aq2gdplmppgg,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"Email I sent to Yuvi:
+
+tl;dr: grrrit-wm is broken right now, it's not relying messages, and
+when we try and attempt to kill it with qdel, it goes into some error
+state and keeps connecting/quitting.
+
+huh (PiRSquared) thinks he broke it when quieting it in another channel,
+it was down for a while before I came online. He asked if he could
+upgrade the irc node module it was using, so I said sure since he
+already had access...that didn't work, so he reverted it, but it's still
+not working.
+
+I logged into gerrit-to-redis, and based on the log messages it appears
+to be working fine (I also restarted it just in case, and it was working
+fine after the restart)
+
+So yeah...halp?
+
+<http://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-dev/20141026.txt> is
+our log trying to figure stuff out.
+
+---
+
+Second email:
+
+To stop spam, we moved the config.yaml to ""config_moved-cuz-bug"" so it
+would stop joining. It also finally died from qstat.
+
+At this point I'm not going to touch it until you or someone else has
+time to debug it...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414294380,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-z6jywipl5zqujo3htvlq,task_description,resolved
+grrrit-wm: runs into infinite loop if unable to join channels,I think this should be fixed now in https://github.com/martynsmith/node-irc/pull/187,1478251444,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,Leaving this open as the actual bot still needs fixing...,1414382570,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"**gerritadmin** wrote:
+
+Change 168927 merged by jenkins-bot:
+Bug 72523: Remove #wikimedia-growth
+
+https://gerrit.wikimedia.org/r/168927",1414381762,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"**gerritadmin** wrote:
+
+Change 168927 had a related patch set uploaded by Legoktm:
+Bug 72523: Remove #wikimedia-growth
+
+https://gerrit.wikimedia.org/r/168927",1414381729,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"Thanks, Merlijn!",1414376996,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"I can't get the patch in from tools and the patch uploader has memory issues, so here's the patch:
+
+commit 419e36d490f14d623633e79cf54dc46bb15dbd94
+Author: Merlijn van Deen <valhallasw@gmail.com>
+Date:   Sun Oct 26 20:23:16 2014 +0000
+
+    Bug 72523: Remove #wikimedia-growth
+
+diff --git a/config.yaml b/config.yaml
+index 01797e0..adb052d 100644
+--- a/config.yaml
++++ b/config.yaml
+@@ -126,10 +126,6 @@ channels:
+         ""mediawiki/extensions/ValueView"",
+         ""mediawiki/extensions/Capiunto""
+         }
+-    ""#wikimedia-growth"": {
+-        ""mediawiki/extensions/GuidedTour"",
+-        ""mediawiki/extensions/GettingStarted""
+-        }
+     ""#wikimedia-multimedia"": {
+         ""mediawiki/extensions/CommonsMetadata.*"",
+         ""mediawiki/extensions/MultimediaViewer.*"",",1414355628,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"So there were two issues currently:
+
+1) gerrit-to-redis was not running. From https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.gerrit-to-redis/SAL :
+19:46 valhallasw: grrrit-wm still not reporting anything; checking redis stream
+19:50 valhallasw: gerrit-to-redis reconnects to gerrit every two hours, but does not push to clients (last 'pushed to 1 clients' message was 26-10-2014 04:00:41,241)
+19:51 valhallasw: and gerrit-to-redis does not seem to be running ATM - qstat is empty
+19:53 valhallasw: job resubmitted; now running on continuous@tools-exec-10; SSH and redis connections are open
+19:57 valhallasw: ""2014-10-26 19:56:30,333 Pushed to 1 clients""
+
+2) grrrit-wm could not join #wikimedia-growth, and does not handle that correctly:
+https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lolrrit-wm/SAL
+
+20:02 valhallasw: 2014-10-26T20:01:00.911Z - error: prefix=hitchcock.freenode.net, server=hitchcock.freenode.net, command=err_channelisfull, rawCommand=471, commandType=error, args=[grrrit-wm1, #wikimedia-growth, Cannot join channel (+l) - channel is full, try again later]
+20:02 valhallasw: but I'm not sure if thta's the actual cause...
+20:11 valhallasw: kicked #wikimedia-growth from the config, let's see if that helps
+20:15 valhallasw: judging from the log, that seems to have been the issue indeed
+
+
+The following is in the log:
+
+2014-10-26T02:51:40.222Z - info: joining channels 0=#mediawiki-i18n, 1=#mediawiki-parsoid, 2=#mediawiki-visualeditor, 3=#pywikibot, 4=#semantic-mediawiki, 5=#wikimedia-analytics, 6=#wikimedia-dev, 7=#wikimedia-fundraising, 8=#wikimedia-corefeatures, 9=#wikimedia-labs, 10=#wikimedia-mobile, 11=#wikimedia-operations, 12=#wikimedia-qa, 13=#wikidata, 14=#wikimedia-growth, 15=#wikimedia-multimedia, 16=#wikipedia-en-ambassadors, 17=#wmt, 18=#brickimedia, 19=#mediawiki-feed
+2014-10-26T02:51:49.403Z - info: Joined channel #mediawiki-i18n
+(...)
+2014-10-26T02:51:58.412Z - error:  prefix=wilhelm.freenode.net, server=wilhelm.freenode.net, command=err_channelisfull, rawCommand=471, commandType=error, args=[grrrit-wm, #wikimedia-growth, Cannot join channel (+l) - channel is full, try again later]
+2014-10-26T02:51:59.411Z - info: Joined channel #wikimedia-multimedia
+(...)
+2014-10-26T02:52:03.426Z - info: Joined channel #mediawiki-feed
+2014-10-26T02:53:52.211Z - info: joining channels 0=#mediawiki-i18n, 1=#mediawiki-parsoid, 2=#mediawiki-visualeditor, 3=#pywikibot, 4=#semantic-mediawiki, 5=#wikimedia-analytics, 6=#wikimedia-dev, 7=#wikimedia-fundraising, 8=#wikimedia-corefeatures, 9=#wikimedia-labs, 10=#wikimedia-mobile, 11=#wikimedia-operations, 12=#wikimedia-qa, 13=#wikidata, 14=#wikimedia-growth, 15=#wikimedia-multimedia, 16=#wikipedia-en-ambassadors, 17=#wmt, 18=#brickimedia, 19=#mediawiki-feed
+(repeats)
+
+
+After kicking #wikimedia-growth out:
+
+2014-10-26T20:12:23.103Z - info: joining channels 0=#mediawiki-i18n, 1=#mediawiki-parsoid, 2=#mediawiki-visualeditor, 3=#pywikibot, 4=#semantic-mediawiki, 5=#wikimedia-analytics, 6=#wikimedia-dev, 7=#wikimedia-fundraising, 8=#wikimedia-corefeatures, 9=#wikimedia-labs, 10=#wikimedia-mobile, 11=#wikimedia-operations, 12=#wikimedia-qa, 13=#wikidata, 14=#wikimedia-multimedia, 15=#wikipedia-en-ambassadors, 16=#wmt, 17=#brickimedia, 18=#mediawiki-feed
+2014-10-26T20:12:32.315Z - info: Joined channel #mediawiki-i18n
+(..)
+2014-10-26T20:12:45.365Z - info: Joined channel #mediawiki-feed
+2014-10-26T20:12:45.366Z - info: Joined 19 channels. Starting relay
+2014-10-26T20:12:51.784Z - info: Sent message from apps/android/wikipedia to #wikimedia-mobile
+
+
+
+
+So, instead of retrying to join *all* channels when one fails, the bot should rather set up the relay for the joined channels, and try re-joining the failed channels.",1414354875,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+grrrit-wm: runs into infinite loop if unable to join channels,"I reverted the config.yaml move and the bot is now connected to freenode and seems stable. The stream seems broken, though.",1414297374,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-z6jywipl5zqujo3htvlq,task_subcomment,NA
+VisualEditor:Link inspector opens with an animation from top while trying to open it for the first time in an edit session,"video capture
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.click on link inspector icon 
+
+Observed Result:
+Link inspector opens with an animation from top
+
+See the video capture attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14920}",1414184760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u34r5p3uaxlfwzfdw4om,task_description,resolved
+VisualEditor:Link inspector opens with an animation from top while trying to open it for the first time in an edit session,This is no longer happening.,1421864811,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-u34r5p3uaxlfwzfdw4om,task_subcomment,NA
+VisualEditor:Link inspector opens with an animation from top while trying to open it for the first time in an edit session,There's an animation?,1421803269,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-u34r5p3uaxlfwzfdw4om,task_subcomment,NA
+VisualEditor:Link inspector opens with an animation from top while trying to open it for the first time in an edit session,Can't reproduce.,1419350022,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-u34r5p3uaxlfwzfdw4om,task_subcomment,NA
+Get Grunt setup in MobileFrontend,"VisualEditor team is using a grunt file. Flow have also moved to one of these.
+
+One of the benefits of the Gruntfile is Jenkins will run `grunt test` on every commit meaning we can get Jenkins automating quite a few things for us.
+
+MobileFrontend should also use it.
+
+One of the benefits of this will be jscs running on every Jenkins build (currently this only runs in a pre commit hook)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414090680,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-srlf3r7iawflrql5il7l,task_description,resolved
+Get Grunt setup in MobileFrontend,"Change: https://gerrit.wikimedia.org/r/#/c/168656/
+
+Merged.",1416103527,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-srlf3r7iawflrql5il7l,task_subcomment,NA
+Get Grunt setup in MobileFrontend,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/ecXDbChX",1414090828,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-srlf3r7iawflrql5il7l,task_subcomment,NA
+At nowiki the nowiki-tag shows up in some edits done with VisualEditor,"It seems like nowiki-tags show up at edits done at nowiki with VisualEditor.
+
+The first of the two examples (https://no.wikipedia.org/w/index.php?title=Cologne_Business_School&diff=13473599&oldid=13473538) could be a copy-paste. If so it is an user error and the same as in Bug 68928 VisualEditor: Copy/pasting causes <nowiki> and <em> tags to appear.
+
+The second edit seems to be different (https://no.wikipedia.org/w/index.php?title=Bergen&diff=prev&oldid=13467156) and I'm not sure what has happened here. Perhaps it is Bug 49820 - VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor. If this is the case the user has clicked through a warning (has it failed?) and still saved.
+
+There is a thread at nowiki about this, https://no.wikipedia.org/wiki/Wikipedia:Torget#Tomme_nowiki-tagger (""Empty nowiki-tags"")
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414090140,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-o6yfcomtzmhncilri75a,task_description,declined
+At nowiki the nowiki-tag shows up in some edits done with VisualEditor,"@Elitre is correct that the two bugs look like they are due to pasting wikitext into a place where wikitext doesn't work. Given the changes since then, this is unlikely to be as much of an issue, but we really can't stop users from doing the wrong thing in all occasions.",1421377390,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o6yfcomtzmhncilri75a,task_subcomment,NA
+At nowiki the nowiki-tag shows up in some edits done with VisualEditor,This should perhaps be a feature request as it seems to be about additional warning messages.,1414374118,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-o6yfcomtzmhncilri75a,task_subcomment,NA
+At nowiki the nowiki-tag shows up in some edits done with VisualEditor,"Allow me to underline the irony of a nowiki at no.wiki :D
+
+I don't think the first case is related to that bug - that simply looks like wikicode copy/pasted in a VE instance, that's why the nowiki tags are generated.
+
+The second case looks more like a confused attempt to edit a wikilink, similar to [[bug 70286]].
+
+As for wikitext warnings, those do exist, but I don't know if they're currently working (I filed a bug about that today) or if they're supposed to work when you copy/paste (not type) wikicode. I'd argue this should be possibile, since this is not the first time we see copy/pasting confusion.",1414156632,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-o6yfcomtzmhncilri75a,task_subcomment,NA
+"VisualEditor Mobile: Misaligned ""Cancel"" and ""Ok"" button in the confirmation dialogs for abandoning edit and switching to Edit Source mode","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE using desktop Safari
+2.Edit something on the page, click on the back button at the top left corner and observe the alignment of ""Ok"" and ""Cancel"" button in the confirmation dialog for abandoning edit
+3.Click cancel and now click on the button to switch to the edit source mode from the Settings menu
+
+4.Observe the alignment of ""Ok"" and ""Cancel"" button in the confirmation dialog for switching to edit source mode
+
+Observed Result:
+The buttons are misaligned as seen in the screenshot attached
+
+Environment:
+Betalabs, test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14709}",1414022820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2tym47dhhlsomwrn7ywj,task_description,invalid
+"VisualEditor Mobile: Misaligned ""Cancel"" and ""Ok"" button in the confirmation dialogs for abandoning edit and switching to Edit Source mode",Going with the latter for now.,1415070112,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2tym47dhhlsomwrn7ywj,task_subcomment,NA
+"VisualEditor Mobile: Misaligned ""Cancel"" and ""Ok"" button in the confirmation dialogs for abandoning edit and switching to Edit Source mode","These are native confirm dialogs, so this bug is upstream or invalid...",1415068013,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2tym47dhhlsomwrn7ywj,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","While some templates are easy to use in VE, this is not. At first VE doesnt load automatically its parameters, at second you need to enter hyperling to its values, but VE doesnt offer tools for that.
+
+Its often used template which gives information, about subjects with the same title.
+
+https://cs.wikipedia.org/wiki/%C5%A0ablona:Mo%C5%BEn%C3%A1_hled%C3%A1te
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413870600,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-ytvabqehjgq7vzt7rym4,task_description,invalid
+"""Možná hledáte"" template on cs.wp not easy to use with VE",That's tracked as bug 52581.,1414347550,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","(In reply to Alex Monk from comment #4)
+> How would VE grab a list of parameters without there being TemplateData...?
+
+Thats a question for you. I am not a specialist, I dont know.",1414343819,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE",How would VE grab a list of parameters without there being TemplateData...?,1414336556,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","Andre: I dont think so.
+
+Elitre: I thought VE grabs it even there is no TD.",1414336318,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","I don't think so. It seems to me this template lacks TemplateData information (https://www.mediawiki.org/wiki/Help:TemplateData ). That's easier to add now (see my announcement at https://cs.wikipedia.org/wiki/Diskuse_k_Wikipedii:VisualEditor/TemplateData ).
+At the moment, you need to use wikimarkup inside templates' fields, so you can use double square brackets to make links.
+If you need further help, please feel free to reach me at your wiki.",1413880860,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+"""Možná hledáte"" template on cs.wp not easy to use with VE","(In reply to Juan de Vojníkov from comment #0)
+> At first VE doesnt load automatically its parameters
+
+Is that bug 69734?",1413877541,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ytvabqehjgq7vzt7rym4,task_subcomment,NA
+VisualEditor:  Some links to URLs are being displayed as red,"This may only be happening to links inside templates or refs.  
+
+Steps to reproduce:
+
+1.  Click on https://en.wikipedia.org/wiki/HOSxP?veaction=edit
+
+2.  Watch the URL in the infobox turn red.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413849660,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gbdas2p32dgcym35jznx,task_description,resolved
+VisualEditor:  Some links to URLs are being displayed as red,"
+
+*** This bug has been marked as a duplicate of bug 72251 ***",1413849744,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gbdas2p32dgcym35jznx,task_subcomment,NA
+ext.eventLogging.subscriber.js broken,"File: https://github.com/wikimedia/mediawiki-extensions-EventLogging/blob/master/modules/ext.eventLogging.subscriber.js
+
+
+The ext.eventLogging.subscriber.js has not worked since past April. Visual Editor editor was using it to submit its events to EL. 
+
+While VE is removing usage of this class (as it really not needed on their case) we should either fix it or remove other usages of it. Sounds like its only usage on the codebase (besides Visual Editor's) is to report usage of deprecated javascript functions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413581220,PHID-USER-mwkkwzbzlkvdl4w2og44,False,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_description,resolved
+ext.eventLogging.subscriber.js broken,"Change 167326 merged by jenkins-bot:
+Fix off-by-one error in mw.track subscriber
+
+https://gerrit.wikimedia.org/r/167326",1414548076,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_subcomment,NA
+ext.eventLogging.subscriber.js broken,"(In reply to Roan Kattouw from comment #1)
+> Specifically, what's broken is the way that it tries to derive the schema
+> from the topic name. The things that are broken about it are:
+> 
+> * It ends up trying to load schema..foo (double dot)
+My patch fixes this.
+
+> * It documents that the topic must start with 'event.', and tries to strip
+> that (leaving the dot), but none of the callers actually pass 'event.'
+This seems to be deliberate, because it only listens for events that start with 'event'. My patch changes this to 'event.' so we don't capture random other stuff.
+
+> * If the schema is not found (which due to the bugs above is virtually
+> always the case), it fails silently with no warning logged anywhere
+> 
+This doesn't seem to be true: ResourceLoader does log an error about not being able to find a module called schema..foo
+
+> It's been suggested that subscriber.js (and mw.track(), which it
+> facilitates) just needs to be put out of its misery. VisualEditor is using
+> it, but there's no good reason for that and I'm porting it to call
+> EventLogging directly. However, a few things in MediaWiki are using
+> mw.track(), and some of them would benefit from deferred loading (they may
+> call mw.track() very early, before EventLogging has been loaded), so those
+> would have to be looked at.
+
+Right now Dan is suggesting we just keep it around.",1413583515,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_subcomment,NA
+ext.eventLogging.subscriber.js broken,"Change 167326 had a related patch set uploaded by Catrope:
+Fix off-by-one error in mw.track subscriber
+
+https://gerrit.wikimedia.org/r/167326",1413583341,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_subcomment,NA
+ext.eventLogging.subscriber.js broken,"Specifically, what's broken is the way that it tries to derive the schema from the topic name. The things that are broken about it are:
+
+* It ends up trying to load schema..foo (double dot)
+* It documents that the topic must start with 'event.', and tries to strip that (leaving the dot), but none of the callers actually pass 'event.'
+* If the schema is not found (which due to the bugs above is virtually always the case), it fails silently with no warning logged anywhere
+
+It's been suggested that subscriber.js (and mw.track(), which it facilitates) just needs to be put out of its misery. VisualEditor is using it, but there's no good reason for that and I'm porting it to call EventLogging directly. However, a few things in MediaWiki are using mw.track(), and some of them would benefit from deferred loading (they may call mw.track() very early, before EventLogging has been loaded), so those would have to be looked at.",1413581625,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cr523vgbmfq3b5zfi7gt,task_subcomment,NA
+VE instrumentation is not showing up in databases,"VE has a variety of schemas[1] that are not correctly feeding into the EL databases. They need assistance in figuring out what's happening.
+
+Dario suspects that the events are failing validation.
+
+[1] https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=VisualEditor&fulltext=Search&ns470=1&profile=advanced
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413517140,PHID-USER-ud7f5gp5h3uqup6viq4e,False,PHID-TASK-xzgjkfv633ag6fmt7rky,task_description,resolved
+VE instrumentation is not showing up in databases,"Edit team has a dashboard that is fed data from the DB, so everything seems ok from our point of view: http://edit-reportcard.wmflabs.org/",1421079666,PHID-USER-vbyvvtbztxaeuaxelxx4,False,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VE instrumentation is not showing up in databases,Roan.. can you clarify a bit your last comment? me no comprendo.,1413591244,PHID-USER-mwkkwzbzlkvdl4w2og44,False,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VE instrumentation is not showing up in databases,"(In reply to Roan Kattouw from comment #2)
+> Turns out EventLogging's mw.track subscriber is broken, and VisualEditor was
+> using it for no good reason. I'll port VE to use EL directly, but there are
+> other uses of mw.track and those are probably broken too:
+> 
+> resources/lib/jquery/jquery.migrate.js:65:mw.track( ""jquery.migrate"", key ||
+> ""unknown"" );
+> resources/src/mediawiki/mediawiki.js:567:mw.track( 'mw.deprecate', key );
+> resources/src/mediawiki/mediawiki.js:572:mw.track( 'mw.deprecate', key );
+
+ACTUALLY... the WikimediaEvents extension includes subscribers for both ve.* events and for these two. So they DO end up in EventLogging, just not via EventLogging's subscriber. It looks like nothing is just EventLogging's subscriber, which only subscribes to things starting with 'event.*'
+
+The schemas used by WikimediaEvents are:
+ve.* --> Schema:TimingData
+jquery.migrate --> Schema:JQMigrateUsage
+mw.deprecate --> Schema:DeprecatedUsage",1413589327,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VE instrumentation is not showing up in databases,"Turns out EventLogging's mw.track subscriber is broken, and VisualEditor was using it for no good reason. I'll port VE to use EL directly, but there are other uses of mw.track and those are probably broken too:
+
+resources/lib/jquery/jquery.migrate.js:65:mw.track( ""jquery.migrate"", key || ""unknown"" );
+resources/src/mediawiki/mediawiki.js:567:mw.track( 'mw.deprecate', key );
+resources/src/mediawiki/mediawiki.js:572:mw.track( 'mw.deprecate', key );",1413581032,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VE instrumentation is not showing up in databases,"No new events are coming in for schemas like VisualEditor%:
+
+zsub vanadium.eqiad.wmnet:8600 | grep '""schema"": ""VisualEditor'
+
+But at least two of the events used to validate at some point at the end of 2013, beginning of 2014:
+
+mysql:research@analytics-store.eqiad.wmnet [log]> select min(timestamp), max(timestamp) from VisualEditorDOMSaved_6063754;
++----------------+----------------+
+| min(timestamp) | max(timestamp) |
++----------------+----------------+
+| 20131016202600 | 20131121114538 |
++----------------+----------------+
+1 row in set (0.00 sec)
+
+mysql:research@analytics-store.eqiad.wmnet [log]> select min(timestamp), max(timestamp) from VisualEditorDOMRetrieved_5961496;
++----------------+----------------+
+| min(timestamp) | max(timestamp) |
++----------------+----------------+
+| 20131010222635 | 20140128212543 |
++----------------+----------------+
+1 row in set (0.00 sec)
+
+The most likely explanation is that the events are no longer emitted, as we don't see them in the raw stream.  So, in short, look around 20131121114538 and 20140128212543 to see what changed in your instrumentation.  We're setting up a meeting to discuss further, but feel free to comment here too.",1413565037,PHID-USER-vbyvvtbztxaeuaxelxx4,False,PHID-TASK-xzgjkfv633ag6fmt7rky,task_subcomment,NA
+VisualEditor: Moving the cursor with keyboard over a footnote number goes back and forth,"1. Go to https://www.mediawiki.org/w/index.php?title=Manual:Coding_conventions/Ruby&redirect=no&veaction=edit (revision: https://www.mediawiki.org/w/index.php?title=Manual:Coding_conventions/Ruby&oldid=1226556 )
+
+2. Put the caret at the end of the second paragraph after ""staff"".
+
+3. Move the caret forward with the keyboard using the ""right arrow"" key repeatedly
+
+Expected: The caret must move forward through the three footnote numbers.
+
+Observed: The caret moves to the first reference and then back before it.
+
+This is similar to bug T73550.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413473340,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-3elt5ys3qqz7nivrswhi,task_description,resolved
+VisualEditor: Moving the cursor with keyboard over a footnote number goes back and forth,Works for me now. Wish we could confirm when we'd fixed this. :-(,1423676182,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3elt5ys3qqz7nivrswhi,task_subcomment,NA
+VisualEditor[Regression wmf3]:Category context menu appears out of position.,"screenshot
+
+Environment- test2, beta
+
+1> Add a new category say- Japan.
+2> select the category to delete it. Notice the context menu appears out of position.
+
+see screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F15006}",1413215220,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-apuow26xcvt52fvqwwvs,task_description,resolved
+VisualEditor[Regression wmf3]:Category context menu appears out of position.,"
+
+*** This bug has been marked as a duplicate of bug 72052 ***",1413817416,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-apuow26xcvt52fvqwwvs,task_subcomment,NA
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.","Environment- test2
+
+1> In VE enter external link e.g- http://lowes.com . Save the page. Takes you to Read mode.
+2> Select Edit tab again and Edit the external link to google.com. Save the page.
+3> In the Read mode click on the external link to open the page. Navigates to google page. Now click on the back browser button. You would expect this to navigate you to the most recently saved page in VE , but click on the link and it opens lowes page . 
+4> Now click on Edit tab and it would show google.com as the link.
+
+
+Page in VE with lowes.com ->edit and saved the page with google.com -> google.com(current page)
+                                                                            
+                                                                                                                                                  
+                                                                                                                                                                                                                                                                                            
+Hit the back button.
+
+Page in VE with lowes.com(takes me here)  -> edit and saved the page with google.com (should have navigated here)-> google.com
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1412959980,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-6k2emu2psnugqtpitixd,task_description,resolved
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.",Re-checked it in test2 and betalabs - seems to be working fine.,1415387271,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-6k2emu2psnugqtpitixd,task_subcomment,NA
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.","(In reply to Ritu Swain from comment #2)
+> (In reply to James Forrester from comment #1)
+> > I can't reproduce this; can you confirm it's still an issue? (Test
+> > environment: Beta Labs, Chrome 38, Mac OS X 10.10)
+> 
+> I cannot reproduce it anymore in test2 or beta.
+
+OK, marking as FIXED though I know not how.",1414104706,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6k2emu2psnugqtpitixd,task_subcomment,NA
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.","(In reply to James Forrester from comment #1)
+> I can't reproduce this; can you confirm it's still an issue? (Test
+> environment: Beta Labs, Chrome 38, Mac OS X 10.10)
+
+I cannot reproduce it anymore in test2 or beta.",1414041545,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-6k2emu2psnugqtpitixd,task_subcomment,NA
+"VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.","I can't reproduce this; can you confirm it's still an issue? (Test environment: Beta Labs, Chrome 38, Mac OS X 10.10)",1414008818,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6k2emu2psnugqtpitixd,task_subcomment,NA
+VisualEditor: Annotations pull-down closes before scrolling it.,"Environment- test2, beta
+
+In the Reference dialog and Media Settings Caption dialog, before even  I could scroll down the Annotations menu list and select the Language tool or Clear styling,  the pull-down closes, making it difficult to  apply them to existing content.
+
+
+Environment-test2 only
+
+Similarly, in the Transclusion dialog -> Add a Template field, when you start typing and the suggestion list is shown, before you could scroll the list, it closes, making it unusable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP",1412775960,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ajcga6hkx4kdoeksqocl,task_description,resolved
+VisualEditor: Annotations pull-down closes before scrolling it.,"Merging into bug 65774.
+
+*** This bug has been marked as a duplicate of bug 65774 ***",1415807863,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ajcga6hkx4kdoeksqocl,task_subcomment,NA
+VisualEditor: Wikilinks with a final space,"This bug has been observed for a while on fr.wp and thus unofficially reported time ago, but now User:Drongou has kindly provided instructions to replicate it, so:
+
+1) Copy/paste something between square brackets, say [[2013]]
+2) Place the cursor before the 3 and type 4, so that it becomes [[20143]]
+3) Type a space, so it now looks like [[2014 3]]
+4) Remove the 3 and save.
+ 
+The result will be <nowiki>[[2014 ]]</nowiki>.
+Confirmed at least on Safari 7.1, Mac OS-X 10.9 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412365620,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-amkdzmp26p5hbs2ljuus,task_description,resolved
+VisualEditor: Wikilinks with a final space,"This is already covered in bug 52037 – it's really messy, yeah.
+
+*** This bug has been marked as a duplicate of bug 52037 ***",1412365997,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-amkdzmp26p5hbs2ljuus,task_subcomment,NA
+VisualEditor switcher isn't visible,"Switcher icon not visible
+
+In EditorOverlay the icon for the editor switcher (VE or Source) isn't visible (see attachment). You can still click/tap on the position and you can switch, but nobody know, that the switcher is there.
+
+Reported first on https://www.mediawiki.org/wiki/Thread:Extension_talk:MobileFrontend/visualeditor_abandoned
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15397}",1412337840,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-nnnzye23nj6ys3ykaygo,task_description,resolved
+VisualEditor switcher isn't visible,Working now :),1412361115,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164584 merged by jenkins-bot:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164584",1412359552,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164587 merged by jenkins-bot:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164587",1412359548,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164543 merged by jenkins-bot:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164543",1412358084,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164587 had a related patch set uploaded by Florianschmidtwelzow:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164587",1412357897,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164584 had a related patch set uploaded by Florianschmidtwelzow:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164584",1412357781,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**gerritadmin** wrote:
+
+Change 164543 had a related patch set uploaded by Florianschmidtwelzow:
+Use less function to embed editor images
+
+https://gerrit.wikimedia.org/r/164543",1412339180,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor switcher isn't visible,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/799d4SR5",1412337917,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnnzye23nj6ys3ykaygo,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"The author of this revision https://fr.wikipedia.org/w/index.php?title=La_Grange_au_Lac&diff=107837547&oldid=107804115 realizes that the wikicode he copy/pasted was not valid. The question is, does VE really need 5 nowiki tags to inform us? Can there be a good way of warning the user, maybe one which at the same time allows unexperienced editors to avoid saving and fix that mess?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412014620,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-gcgx64v3je25kov2xxdy,task_description,resolved
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"Yes, T73426.",1430414002,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,">>! In T73422#754038, @Elitre wrote:
+> I'll file a bug against Parsoid, thanks.
+
+Any ticket ID handy?",1423702692,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"It could also be a warning just like those for ""Comments"", with a different icon and/or color. This plus a warning on save, indicating the line, suggesting to ""switch to source editing"" and correct it directly in the code ?
+But this won't be efficient if the user doesn't know the wikicode.",1412288331,PHID-USER-4cgt73x34j35pnbem65l,True,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"I'll file a bug against Parsoid, thanks.
+Could we expose the specific issue, like, telling at which line it is and highlighting it? I realize pointing at code is not a great idea in a visual editor.",1412015341,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"Maybe we could have an additional warning on save, like we do for suspected page corruption?",1412014905,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Give the user a chance to understand if he made a mistake and to fix it,"There is already a warning that appears in the top right corner. Maybe that warning could be made better?
+
+The number of nowiki tags there is a bit excessive; that's a bug in Parsoid.",1412014882,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-gcgx64v3je25kov2xxdy,task_subcomment,NA
+VisualEditor: Letters getting added and duplicated on pages featuring chess templates,"See https://de.wikipedia.org/wiki/Benutzer:Elitre_(WMF)/sandbox?veaction=edit .
+Place your cursor after the last period of any section, and start typing. 
+The first letter of your word will get added to the beginning of the following line.
+Hit Backspace; now the whole word appears there.
+Verified also on en.wp on the Chess article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51932",1411981620,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-zuvvxfljo3m4uvk2s3ea,task_description,declined
+VisualEditor: Letters getting added and duplicated on pages featuring chess templates,Please reopen if you manage to reproduce this issue again.,1416182820,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-zuvvxfljo3m4uvk2s3ea,task_subcomment,NA
+VisualEditor: Letters getting added and duplicated on pages featuring chess templates,Is this still occuring? I can't reproduce the issue...,1414802369,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-zuvvxfljo3m4uvk2s3ea,task_subcomment,NA
+"VisualEditor: In Firefox ""TypeError: this.$documentNode is undefined"" appears while selecting a citation note for a second time but not consecutively","Screenshot
+
+Steps to reproduce:
+
+1.Insert 3 citation notes next to a text
+2.Now select the 3rd one
+3.Select the second one and edit it
+4.Select the first one and edit it
+5.Again select the 3rd one to edit it
+
+
+Observed Result:
+""TypeError: this.$documentNode is undefined"" appears in the console.
+
+See the screenshot attached.
+
+This happens in Firefox only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14758}",1411774380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ohb2gmeqf4uqlyoctr2o,task_description,resolved
+"VisualEditor: In Firefox ""TypeError: this.$documentNode is undefined"" appears while selecting a citation note for a second time but not consecutively",The error is not displayed anymore. ,1424134417,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ohb2gmeqf4uqlyoctr2o,task_subcomment,NA
+"VisualEditor:The ""Use this group"" drop down box is getting cut off in Basic Reference dialog","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Cite>Basic 
+3.Open the drop down box for ""Use this group""
+
+
+Observed Result:
+The drop down box appears very small 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14754}",1411772520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-g4ont2tuuoxetvha3ayd,task_description,resolved
+"VisualEditor:The ""Use this group"" drop down box is getting cut off in Basic Reference dialog","Sorry ,it is a duplicate, I could not find this bug in BZ, so reported it.",1411772893,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-g4ont2tuuoxetvha3ayd,task_subcomment,NA
+"VisualEditor:The ""Use this group"" drop down box is getting cut off in Basic Reference dialog","Sorry ,it is a duplicate, I could not find this bug in BZ, so reported it.
+
+*** This bug has been marked as a duplicate of bug 71178 ***",1411772879,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-g4ont2tuuoxetvha3ayd,task_subcomment,NA
+Visual editor screenshot job fails,"Most of the language jobs fail with the same errors. This is example for cs[1]. The parent job is [2].
+
+...
+00:18:18.444 Failing Scenarios:
+00:18:18.444 cucumber features/language_screenshot.feature:42 # Scenario: VisualEditor_Page_Settings
+00:18:18.444 cucumber features/language_screenshot.feature:142 # Scenario: VisualEditor_cancel_save
+...
+
+1: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox/LANGUAGE_SCREENSHOT_CODE=cs,label=contintLabsSlave%20&&%20UbuntuPrecise/5/console
+2: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1411650900,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_description,resolved
+Visual editor screenshot job fails,Looks like the problem is fixed by the above commit. Please reopen the bug if something is still failing.,1412082716,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+Visual editor screenshot job fails,"Change 163185 merged by jenkins-bot:
+[BrowserTest] Fixed failing language screenshot scenarios
+
+https://gerrit.wikimedia.org/r/163185",1411754440,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+Visual editor screenshot job fails,"Change 163185 had a related patch set uploaded by Jforrester:
+[BrowserTest] Fixed failing language screenshot scenarios
+
+https://gerrit.wikimedia.org/r/163185",1411753767,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+Visual editor screenshot job fails,"Change 162879 merged by jenkins-bot:
+[BrowserTest] Disable screenshots for broken scenarios
+
+https://gerrit.wikimedia.org/r/162879",1411651353,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+Visual editor screenshot job fails,"Change 162879 had a related patch set uploaded by Zfilipin:
+[BrowserTest] Disable screenshots for broken scenarios
+
+https://gerrit.wikimedia.org/r/162879",1411651132,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nw2zz6yzstf57zmtkbz5,task_subcomment,NA
+remove messages for features that aren't going to be developed,"Some features of WikiEditor probably aren't going to be developed much in the future. One such feature that I noticed is ""Side by side preview"". (I might actually be wrong, and this feature may be in development.)
+
+If these features will no be developed further, the messages for them should be removed, because currently translators' time is wasted on them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411637940,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_description,resolved
+remove messages for features that aren't going to be developed,"All messages of modules that aren't actually in use (either at WMF or externally) have been removed.
+
+Publish and side-by-side preview have remained.",1426443107,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,"The following patch removes previewDialog, since it probably isn't used anywhere anyways.
+https://gerrit.wikimedia.org/r/#/c/176512/",1417375699,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,">>! In T73287#795508, @TheDJ wrote:
+> side by side (aka preview), is a mode where you can switch between 3 tabs (source, preview, diff) that have live preview features
+Now //THAT// sounds like something Wikisource, Wikibooks, & the like could really use.. and even build upon -- //but I know better than to get my hopes up by now though//.
+
+If the consensus is better to trim it out, then I'd be OK with that too. 
+
+> previewDialog, even I don't know about ...(probably because it's disabled for everyone, incl fresh installs).
+If we follow the existing premise, its safe to say its going to do the same thing as 'preview' does using tabs hinged to the basic WikiEditor but with a MediaViewer-ish type of floating window/interface instead. //yawn// I see no point in pursuing something like that.",1417375664,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,"side by side (aka preview), is a mode where you can switch between 3 tabs (source, preview, diff) that have live preview features
+
+Publish gives you a dialog that basically replaces the summary and copyright disclaimer that is below the edit screen.
+
+Both have some users outside of Wikimedia, I know from bugreports that have been filed over the past few years.
+
+previewDialog, even I don't know about ...(probably because it's disabled for everyone, incl fresh installs).",1417374258,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,"Most of the ""original"" modules like 'toc', 'highlight' & 'templateEditor' are already gone. Not sure what ""Side-by-side preview"" is; I've never come across anything like that. But if you go by a current mock-up of features...
+```
+lang=php, name=mock $wgWikiEditorFeatures, lines=4, counterexample
+
+// Each module may be configured individually to be globally on/off or user preference based
+$GLOBALS['wgWikiEditorFeatures'] = array( 
+
+	/* Textarea / i-frame compatible (OK to deploy) */
+
+	// Enhanced toolbar
+	'toolbar' => array( 'global' => false, 'user' => true ),
+	// Provides interactive tools using dialogs
+	'dialogs' => array( 'global' => false, 'user' => true ),
+	// Hide signature button from main namespace
+	'hidesig' => array( 'global' => true, 'user' => false ), 
+
+	/* Textarea / i-frame compatible, but still experimental and unstable (do not deploy!) */
+
+	// Adds a tab for previewing in-line
+	'preview' => array( 'global' => false, 'user' => true ),
+	// Adds a button for previewing in a dialog
+	'previewDialog' => array( 'global' => false, 'user' => false ),
+	//  Adds a button and dialog for step-by-step publishing
+	'publish' => array( 'global' => false, 'user' => true ),
+
+); 
+```
+... the only thing I can guess that might be is the in-line (or live?) preview module. I've never seen 'publish' at work or heard anything about it either. And of course, hideSig is still in effect though it hasn't ""worked"" for months now.
+
+That said, I can go along with removing the ""abandoned"" feature bits - unless somebody knows better. The focus is on developing VisualEditor as far as I can tell anyway. I just hope they keep something like WikiEditor around for the non-Wikipedia types of projects.
+
+",1417373821,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+remove messages for features that aren't going to be developed,"Most of the ""original"" modules like 'toc', 'highlight' & 'templateEditor' are already gone. Not sure what ""Side-by-side preview"" is; I've never come across anything like that. But if you go by a current mock-up of features...
+```
+lang=php, name=mock $wgEditorFeatures, lines=4, counterexample
+
+// Each module may be configured individually to be globally on/off or user preference based
+$GLOBALS['wgWikiEditorFeatures'] = array( 
+
+	/* Textarea / i-frame compatible (OK to deploy) */
+
+	// Enhanced toolbar
+	'toolbar' => array( 'global' => false, 'user' => true ),
+	// Provides interactive tools using dialogs
+	'dialogs' => array( 'global' => false, 'user' => true ),
+	// Hide signature button from main namespace
+	'hidesig' => array( 'global' => true, 'user' => false ), 
+
+	/* Textarea / i-frame compatible, but still experimental and unstable (do not deploy!) */
+
+	// Adds a tab for previewing in-line
+	'preview' => array( 'global' => false, 'user' => true ),
+	// Adds a button for previewing in a dialog
+	'previewDialog' => array( 'global' => false, 'user' => false ),
+	//  Adds a button and dialog for step-by-step publishing
+	'publish' => array( 'global' => false, 'user' => true ),
+
+); 
+```
+... the only thing I can guess that might be is the in-line (or live?) preview module. I've never seen 'publish' at work or heard anything about it either. And of course, hideSig is still in effect though it hasn't ""worked"" for months now.
+
+That said, I can go along with removing the ""abandoned"" feature bits - unless somebody knows better. The focus is on developing VisualEditor as far as I can tell anyway. I just hope they keep something like WikiEditor around for the non-Wikipedia types of projects.
+
+",1417373777,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-upwgk7teb5ogr6ig3z4r,task_subcomment,NA
+Template editor does not load,"Intention:
+I tried to insert a template using VisualEditor when editing or creating pages on dewiki.
+
+Steps to Reproduce:
+1. Enable Visual Editor in the Beta preferences
+2. Open a random page on dewiki and edit it.
+3. Click ‘Einfügen’ → ‘Vorlage’ (= ‘Insert’ → ‘Template’).
+
+Actual Results:  
+A pop-up opens, but does not load (title: ‘Laden …’ = ‘Loading …’). The pop-up cannot be closed (hitting ‘Abbrechen’ = ‘Cancel’ does not work), so the previous changes are lost.
+
+Expected Results:  
+Instead the template editor should open normally.
+
+Reproducible: Always
+
+Using vector with Firefox 32.0 on Kubuntu 14.04.
+
+JS error (Firefox web console):
+TypeError: queue is undefined ve.dm.MWTransclusionModel.js:136
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411479300,PHID-USER-valtn43cik2zouepilqb,False,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_description,declined
+Template editor does not load,"You're welcome. On de.wp you can find me at https://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07 . Please let us know of any further issues, or just leave your thoughts about your experience with VE. Thank you.",1411482149,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_subcomment,NA
+Template editor does not load,"Hmm, strange.  The problem does not occur with a blanked common.js, though the user scripts did not report an error.  Anyway, thanks for the assistance; I’ll have another look at the user scripts.",1411481741,PHID-USER-valtn43cik2zouepilqb,False,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_subcomment,NA
+Template editor does not load,"I can't reproduce with the same browser but in Windows 8.
+Robin, can you please try to add a template in incognito mode to https://de.wikipedia.org/wiki/Benutzer:Elitre_(WMF)/sandbox?veaction=edit and tell us what happens? Thanks.",1411481150,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_subcomment,NA
+Template editor does not load,"Created attachment 16552
+Screenshot of the stuck template pop-up with Firefox 32.0 on Kubuntu 14.04
+
+**Attached**: {F14915}",1411479513,PHID-USER-valtn43cik2zouepilqb,False,PHID-TASK-5yf5dygkkj6zbjbu5pbs,task_subcomment,NA
+"VisualEditor: Citations appear broken for a few moments, before getting inserted in a Basic Reference dialog .","Citations broken display
+
+Environment- Test2, beta, production
+
+1> Cite Basic -> Select to insert any citation(book/journal/news/website)
+2> In the resulting modal, just click insert button.
+3> Notice the citation appears broken momentarily and then gets added to the Reference editor.
+
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14809}",1410879600,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gqixviakwxjhwko6a5nu,task_description,declined
+"VisualEditor: Citations appear broken for a few moments, before getting inserted in a Basic Reference dialog .",Done.,1415031297,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gqixviakwxjhwko6a5nu,task_subcomment,NA
+"VisualEditor: Citations appear broken for a few moments, before getting inserted in a Basic Reference dialog .","Please close this issue, i cannot reproduce it anymore.",1415027667,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gqixviakwxjhwko6a5nu,task_subcomment,NA
+VisualEditor: {{lowercasetitle}} is not reflected in Display title in Advanced page settings,"The article [[iOS]] in the English Wikipedia has {{lowercasetitle}}, which is a wrapper for {{displaytitle}}.
+
+It works correctly for display, but isn't shown in the Advanced settings dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410854280,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-4tcm2evcvzrqvo5xtchr,task_description,duplicate
+VisualEditor: {{lowercasetitle}} is not reflected in Display title in Advanced page settings,I'm guessing this is because the displaytitle is transcluded in?,1420942044,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-4tcm2evcvzrqvo5xtchr,task_subcomment,NA
+"VisualEditor: In Safari, Citation dialog opens with a weird animation and placing the cursor inside a parameter field enlarges it","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the citation dialog for an existing citation
+3.Place the cursor on any field that has an input in it.
+
+Observed Result:
+The citation dialog opens with a weird animation and the first textbox appears much larger
+
+
+See the screenshot attached.
+
+Environment:Betalabs, test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14782}",1410822360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d4545cy7z4y2r2mrze77,task_description,resolved
+"VisualEditor: In Safari, Citation dialog opens with a weird animation and placing the cursor inside a parameter field enlarges it",This seems to now be fixed?,1417577714,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d4545cy7z4y2r2mrze77,task_subcomment,NA
+"VisualEditor[Regression wmf21] :New Section/Add Topic tab when first enabled/disabled,  gets added to the toolbar only after clicking on the Edit Source tab.","New Section tab in Beta
+
+Environment-Production, Test2, beta
+
+1> Go to Advanced Settings and enable the “Show a tab on this page to add a new section” and apply changes.
+2> Save the page.Switch back and forth between the Edit beta and Read tab, notice the new section/Add topic tab is not added to the Toolbar. It gets added only after clicking on Edit Source tab and then Edit beta tab.
+3>Now  go back to Advanced Settings.Change the “Show a tab on this page to add a new section”  to No and apply changes.
+4>Save the page.
+5> Go back to the editor and notice the new section tab is still visible . And it is only when you click on the Edit source tab, that the New Section tab goes away from the Toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14727}",1410796380,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-v72oxbgvsl4t35xhcxhi,task_description,resolved
+"VisualEditor[Regression wmf21] :New Section/Add Topic tab when first enabled/disabled,  gets added to the toolbar only after clicking on the Edit Source tab.","
+
+*** This bug has been marked as a duplicate of bug 20177 ***",1410805042,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v72oxbgvsl4t35xhcxhi,task_subcomment,NA
+"VisualEditor[Regression wmf21] :New Section/Add Topic tab when first enabled/disabled,  gets added to the toolbar only after clicking on the Edit Source tab.","Created attachment 16470
+Add Topic in Test2
+
+**Attached**: {F14728}",1410796456,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-v72oxbgvsl4t35xhcxhi,task_subcomment,NA
+"VisualEditor: [Regression wmf21] :  Citations deleted, are still shown in “Use  this group” suggestion list.","References list
+
+Environment- Test2, beta
+
+1> Have at least 2 citations on the page.
+2> Select Basic  -> Use an Existing Reference. The selected citation to re-use gets inserted on the page.
+3> Now while the  re-used citation is still highlighted. Select “Basic” again and type in a name  in the “Use this group” input box.
+4> Apply changes.
+5> In the editor that citation gets replaced by the group name. Now delete all the citations from the page.
+6> Select Insert -> References list. And click on the arrow in the “Use this Group” drop-down. Notice the group name assigned in step#3 is still visible in the suggestion list drop-down.
+
+Same thing happens when you try to access the “Use this group” in the basic citation.
+See screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14722}",1410793920,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-fgqx6dqjpzobxffe3bcw,task_description,declined
+"VisualEditor: [Regression wmf21] :  Citations deleted, are still shown in “Use  this group” suggestion list.","(In reply to Rummana Yasmeen from comment #2)
+> Hey Ritu, this is intentional, because even if user deletes the citations
+> that belongs to a specific group, user might want to use that group later
+> and add other citations to that in that edit session.So, instead of making
+> user to do the same step again , we are keeping the group name for that
+> session, however if you save your edit after step 6 , you will no longer see
+> that group name.
+
+yes, i saw that too. But was assuming that the suggestions would get updated too when the page has no citations. got it now.",1410809854,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-fgqx6dqjpzobxffe3bcw,task_subcomment,NA
+"VisualEditor: [Regression wmf21] :  Citations deleted, are still shown in “Use  this group” suggestion list.","Hey Ritu, this is intentional, because even if user deletes the citations that belongs to a specific group, user might want to use that group later and add other citations to that in that edit session.So, instead of making user to do the same step again , we are keeping the group name for that session, however if you save your edit after step 6 , you will no longer see that group name.",1410804727,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fgqx6dqjpzobxffe3bcw,task_subcomment,NA
+"VisualEditor: [Regression wmf21] :  Citations deleted, are still shown in “Use  this group” suggestion list.","Created attachment 16468
+Basic Citation
+
+**Attached**: {F14723}",1410793999,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-fgqx6dqjpzobxffe3bcw,task_subcomment,NA
+Category description not displayed after save,"I added a description to my new category https://en.wikipedia.org/wiki/Category:Conspiracy_theories_in_popular_culture using VisualEditor.
+
+After I saved the category page, my new description was not visible. I had to reload the page, and then it was displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410675780,PHID-USER-bug3zrlooz3bdmi4fyl7,False,PHID-TASK-mlkcxdg52un5am2qjmf2,task_description,resolved
+Category description not displayed after save,"Merging this with bug 56289.
+
+*** This bug has been marked as a duplicate of bug 56289 ***",1415046616,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mlkcxdg52un5am2qjmf2,task_subcomment,NA
+VisualEditor: Moving an image in the document results in pixelated thumbnail,"## Steps
+
+1. Select an image node.
+   https://www.mediawiki.org/wiki/VisualEditor:Basic_example_worksheet#Media_files
+2. Resize a one of the small ones to be bigger. It'll fetch a large thumbnail momentarily.
+3. Drag and drop the image to a different position in the surrounding paragraph.
+
+## Unexpected behaviour
+
+The original image resource is re-used after a drag/drop, but now upscaled by the browser, thus pixelated. And no new thumb is fetched, either.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410639060,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yaxez2im35xxygh33vod,task_description,resolved
+VisualEditor: Moving an image in the document results in pixelated thumbnail,"It seems like it's been fixed - when resized(enlarged) images are dragged&dropped - they do not get reversed to the original resolution(and, therefore,  pixelated). 
+
+Or it could be that only specific images displayed the issue. ",1424211819,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-yaxez2im35xxygh33vod,task_subcomment,NA
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present","Span tag as seen in Firefox
+
+https://en.wikipedia.org/wiki/Everyone_Poops?veaction=edit produces an ugly span tag above the infobox.  
+
+The infobox is not displaying correctly at all in Safari, but in both Firefox and Safari it shows a long, large, bold-face span tag.  This appears to be caused by the <ref> tags.  See https://en.wikipedia.org/w/index.php?oldid=625300040 for a single-parameter infobox that causes the mess.
+
+These span tags are not saved, so they don't corrupt the wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15303}",1410561720,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-63hk7m7naae6ypxuy7z5,task_description,declined
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present","This is just a buggy template / template use.
+
+The wikitext on https://en.wikipedia.org/w/index.php?oldid=625300040 leads to the following template expansion for the infobox:
+
+...
+<span class=""Z3988""
+          title=""ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Everyone+Poops<ref name=""bnn"">{{cite web|url=http://search.barnesandnoble.com/Everyone-Poops/Taro-Gomi/e/9780916291457|title=Everyone Poops, My Body Science Series, Taro Gomi, Book|accessdate=2008-02-14|year=2009|publisher=[[Barnes & Noble]]}}</ref>""></span
+...
+
+See how the span has a title attribute that has a ref tag and transclusion. But even that brokenness is okay .. the real problem is the use of double quotes for the name attribute of the <ref> tag that is embedded in the title attribute.
+
+So, the wikitext is effectively something like this:
+
+<span title=""....name=""bnn""...""</span>
+
+That is broken because of the use of double quotes which terminates the title attribute early. This is one of those edge-case differences between PHP parser and Parsoid. If the name=""bnn"" is replaced with name='bnn', this will work.
+
+This is a wontfix on the Parsoid end since there is a wikitext edit that will handle this strange edge case.
+
+Please reopen if there is something to do on the Parsoid end.",1416237485,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-63hk7m7naae6ypxuy7z5,task_subcomment,NA
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present",Looks like a Parsoid issue?,1412366992,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-63hk7m7naae6ypxuy7z5,task_subcomment,NA
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present",Also reported here:  https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Infobox_on_en.wikipedia%27s_The_Little_Prince,1411949566,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-63hk7m7naae6ypxuy7z5,task_subcomment,NA
+"Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present","Created attachment 16456
+Infobox as seen in Safari.  Note that the content of the box does not display in Safari.  It's blank for half a screen, and then the article text begins.
+
+**Attached**: {F15304}",1410561833,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-63hk7m7naae6ypxuy7z5,task_subcomment,NA
+"VisualEditor:  ""Clear styling"" is confusing.  If it's going to clear links, too, then it should say, ""Clear styling and links""","If ""clear styling"" is going to clear links, too, then it should say, ""Clear styling and links"".  
+
+(I'd rather that it didn't clear links, because, when I copy a link from another page, I want a way to get rid of character formatting and colors without killing the links, too.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410464640,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-xcx7l75kyfn73sjmenqd,task_description,resolved
+"VisualEditor:  ""Clear styling"" is confusing.  If it's going to clear links, too, then it should say, ""Clear styling and links""","
+
+*** This bug has been marked as a duplicate of bug 51757 ***",1410482044,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xcx7l75kyfn73sjmenqd,task_subcomment,NA
+VisualEditor:  Links to disambiguation pages should be highlighted in a different color,"This is related to bug 61072 and bug 50240.
+
+Please consider marking all links to disambiguation pages in a different color, not just in the link inspector tool itself, but in the regular text that editors see when typing in VisualEditor.  This will help editors realize that there is something different (and probably wrong) with links that were previously added to the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410463440,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jtmdegkv2zterww5ielc,task_description,resolved
+VisualEditor:  Links to disambiguation pages should be highlighted in a different color,"This is (effectively) a duplicate of bug 7936 (which is only asking for Special:AllPages, but we'd also change it in the content display). It's nothing particularly specific to VisualEditor; VE just follows MW's lead here.
+
+*** This bug has been marked as a duplicate of bug 7936 ***",1410488331,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jtmdegkv2zterww5ielc,task_subcomment,NA
+VisualEditor:  Links to disambiguation pages should be highlighted in a different color,"BD2412 has specifically requested that this be available to everyone, not just for himself/people using a script.",1410468169,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jtmdegkv2zterww5ielc,task_subcomment,NA
+VisualEditor:  Links to disambiguation pages should be highlighted in a different color,"They already are! (Or rather can be.) I implemented a way to color them in 066283dde745fcc372ffab8d753962858813d032 (the links on the editing surface now have a .mw-disambig class that can be styled with user/site CSS). I also did the same functionality in the MW parser (8cc16d021410f49fa12a2f35c97cdac51adf4380, this is not rolled out yet).
+
+I'm not sure if we want to actually color them. Colors can be distracting/confusing, especially if it's not clear what they mean. MediaWiki has been providing a .mw-redirect CSS class in parser output for years and it was never styled in any way, as far as I know. (Some special pages mark redirects with italics, though.)
+
+For the record, such coloring functionality has sometimes been implemented by gadgets. pl.wp has a opt-in gadget to color redirects green and disambigs maroon and add a form to the page to selectively correct the links; ru.wp has some tool enabled for everyone that gives disambigs pink background with red outline (or had, last time I checked). I am not aware of any such thing on the English Wikipedia (but I'd be love to learn about it if it exists).",1410464649,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-jtmdegkv2zterww5ielc,task_subcomment,NA
+VisualEditor:  Language dialog box didn't draw correctly,"Language dialog box, as it's not meant to be
+
+While testing on Meta, the language inspector did not open correctly.  It had some odd box drawing and no buttons.  See the screenshot.
+
+(This is not the problem described in bug 70731.  This oddly drawn box was the correct size.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15132}",1410461400,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-kn7dujwu6ne4iw4jweqi,task_description,resolved
+VisualEditor:  Language dialog box didn't draw correctly,"This appears to now be fixed for me – testing in Firefox, Chrome and Safari.",1417480519,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kn7dujwu6ne4iw4jweqi,task_subcomment,NA
+"VisualEditor:  Saving produced a ""Something went wrong"" generic error message, but it silently and successfully saved the page","User:Mike Christie made ten small (often single-character) edits to [[w:en:2002 Pacific typhoon season]] recently.  Edits #1 and #3 produced a generic error of ""Something went wrong"", and it appeared the save had failed.  
+
+In both cases, the save worked.  The diffs are https://en.wikipedia.org/w/index.php?title=2002_Pacific_typhoon_season&diff=624878218&oldid=624550518 and https://en.wikipedia.org/w/index.php?title=2002_Pacific_typhoon_season&diff=next&oldid=624881675  None of the other, similar edits made to the article (including one in between these two) produced any errors. 
+
+Mike usually edits in Chrome on Windows 7.  I've seen the same behavior with a generic ""There was an error"" message in Firefox on Mac OS 10.8.5, so it's probably affecting everything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53093",1410457800,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-mgurrwf77bjbyrtqm46n,task_description,duplicate
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","I am following quick start instructions[1] on a Mac.
+
+1. https://www.mediawiki.org/wiki/MediaWiki-Vagrant#Quick_start
+
+```
+$ sw_vers -productVersion
+10.9.4
+
+$ git --version
+git version 2.1.0
+
+$ vboxmanage --version
+4.3.16r95972
+
+$ vagrant -v
+Vagrant 1.6.5
+
+$ git pull origin master
+From ssh://gerrit.wikimedia.org:29418/mediawiki/vagrant
+ * branch            master     -> FETCH_HEAD
+Already up-to-date.
+
+$ git submodule update --init --recursive
+
+$ ./setup.sh
+Plugin vagrant-vbguest is already installed
+Installing plugin mediawiki-vagrant-0.1.4.gem
+- Installing the 'mediawiki-vagrant-0.1.4.gem' plugin. This can take a few minutes...
+- Installed the plugin 'mediawiki-vagrant (0.1.4)'!
+You're all set! Simply run `vagrant up` to boot your new environment.
+
+$ vagrant destroy
+    default: Are you sure you want to destroy the 'default' VM? [y/N] y
+==> default: Removing puppet created files...
+==> default: Destroying VM and associated drives...
+==> default: Pruning invalid NFS exports. Administrator privileges will be required...
+Password:
+==> default: Running cleanup tasks for 'lsb_check' provisioner...
+==> default: Running cleanup tasks for 'puppet' provisioner...
+
+$ vagrant up
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'trusty-cloud'...
+==> default: Matching MAC address for NAT networking...
+==> default: Setting the name of the VM: vagrant_default_1410428807331_61896
+==> default: Clearing any previously set forwarded ports...
+==> default: Clearing any previously set network interfaces...
+==> default: Preparing network interfaces based on configuration...
+    default: Adapter 1: nat
+    default: Adapter 2: hostonly
+==> default: Forwarding ports...
+    default: 80 => 8080 (adapter 1)
+    default: 22 => 2222 (adapter 1)
+==> default: Running 'pre-boot' VM customizations...
+==> default: Booting VM...
+==> default: Waiting for machine to boot. This may take a few minutes...
+    default: SSH address: 127.0.0.1:2222
+    default: SSH username: vagrant
+    default: SSH auth method: private key
+    default: Warning: Connection timeout. Retrying...
+==> default: Machine booted and ready!
+GuestAdditions versions on your host (4.3.16) and guest (4.3.10) do not match.
+stdin: is not a tty
+ * Stopping VirtualBox Additions
+   ...done.
+stdin: is not a tty
+Reading package lists...
+Building dependency tree...
+Reading state information...
+The following packages were automatically installed and are no longer required:
+  dkms fakeroot gcc gcc-4.8 libasan0 libatomic1 libc-dev-bin libc6-dev
+  libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libfakeroot libfontenc1
+  libgcc-4.8-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgomp1
+  libice6 libitm1 libllvm3.4 libpciaccess0 libpixman-1-0 libquadmath0 libsm6
+  libtsan0 libtxc-dxtn-s2tc0 libx11-xcb1 libxaw7 libxcb-dri2-0 libxcb-dri3-0
+  libxcb-glx0 libxcb-present0 libxcb-sync1 libxcomposite1 libxdamage1
+  libxfixes3 libxfont1 libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1
+  libxshmfence1 libxt6 libxxf86vm1 linux-libc-dev manpages-dev x11-common
+  x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common
+  xserver-xorg-core
+Use 'apt-get autoremove' to remove them.
+The following packages will be REMOVED:
+  virtualbox-guest-dkms* virtualbox-guest-utils* virtualbox-guest-x11*
+0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
+After this operation, 12.1 MB disk space will be freed.
+(Reading database ... 60914 files and directories currently installed.)
+Removing virtualbox-guest-dkms (4.3.10-dfsg-1) ...
+
+-------- Uninstall Beginning --------
+Module:  virtualbox-guest
+Version: 4.3.10
+Kernel:  3.13.0-30-generic (x86_64)
+-------------------------------------
+
+Status: Before uninstall, this module version was ACTIVE on this kernel.
+
+vboxguest.ko:
+ - Uninstallation
+   - Deleting from: /lib/modules/3.13.0-30-generic/updates/dkms/
+ - Original module
+   - No original module was found for this module on this kernel.
+   - Use the dkms install command to reinstall any previous module version.
+
+
+vboxsf.ko:
+ - Uninstallation
+   - Deleting from: /lib/modules/3.13.0-30-generic/updates/dkms/
+ - Original module
+   - No original module was found for this module on this kernel.
+   - Use the dkms install command to reinstall any previous module version.
+
+
+vboxvideo.ko:
+ - Uninstallation
+   - Deleting from: /lib/modules/3.13.0-30-generic/updates/dkms/
+ - Original module
+   - No original module was found for this module on this kernel.
+   - Use the dkms install command to reinstall any previous module version.
+
+depmod....
+
+DKMS: uninstall completed.
+
+------------------------------
+Deleting module version: 4.3.10
+completely from the DKMS tree.
+------------------------------
+Done.
+Removing virtualbox-guest-x11 (4.3.10-dfsg-1) ...
+Purging configuration files for virtualbox-guest-x11 (4.3.10-dfsg-1) ...
+Removing virtualbox-guest-utils (4.3.10-dfsg-1) ...
+Purging configuration files for virtualbox-guest-utils (4.3.10-dfsg-1) ...
+Processing triggers for man-db (2.6.7.1-1) ...
+Processing triggers for libc-bin (2.19-0ubuntu6) ...
+stdin: is not a tty
+Reading package lists...
+Building dependency tree...
+Reading state information...
+dkms is already the newest version.
+dkms set to manually installed.
+linux-headers-3.13.0-30-generic is already the newest version.
+linux-headers-3.13.0-30-generic set to manually installed.
+The following packages were automatically installed and are no longer required:
+  libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libfontenc1 libgl1-mesa-dri
+  libgl1-mesa-glx libglapi-mesa libice6 libllvm3.4 libpciaccess0 libpixman-1-0
+  libsm6 libtxc-dxtn-s2tc0 libx11-xcb1 libxaw7 libxcb-dri2-0 libxcb-dri3-0
+  libxcb-glx0 libxcb-present0 libxcb-sync1 libxcomposite1 libxdamage1
+  libxfixes3 libxfont1 libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1
+  libxshmfence1 libxt6 libxxf86vm1 x11-common x11-xkb-utils xfonts-base
+  xfonts-encodings xfonts-utils xserver-common xserver-xorg-core
+Use 'apt-get autoremove' to remove them.
+0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+Copy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
+stdin: is not a tty
+mount: block device /tmp/VBoxGuestAdditions.iso is write-protected, mounting read-only
+Installing Virtualbox Guest Additions 4.3.16 - guest version is 4.3.10
+stdin: is not a tty
+Verifying archive integrity... All good.
+Uncompressing VirtualBox 4.3.16 Guest Additions for Linux............
+VirtualBox Guest Additions installer
+Copying additional installer modules ...
+Installing additional modules ...
+Removing existing VirtualBox DKMS kernel modules ...done.
+Removing existing VirtualBox non-DKMS kernel modules ...done.
+Building the VirtualBox Guest Additions kernel modules ...done.
+Doing non-kernel setup of the Guest Additions ...done.
+Starting the VirtualBox Guest Additions ...done.
+Installing the Window System drivers
+Could not find the X.Org or XFree86 Window System, skipping.
+An error occurred during installation of VirtualBox Guest Additions 4.3.16. Some functionality may not work as intended.
+In most cases it is OK that the ""Window System drivers"" installation failed.
+stdin: is not a tty
+==> default: Checking for guest additions in VM...
+==> default: Setting hostname...
+==> default: Configuring and enabling network interfaces...
+==> default: Exporting NFS shared folders...
+==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
+==> default: Mounting NFS shared folders...
+==> default: Mounting shared folders...
+    default: /tmp/vagrant-puppet-5/manifests => /Users/z/Documents/wmf/mediawiki/vagrant/puppet/manifests
+    default: /tmp/vagrant-puppet-5/modules-0 => /Users/z/Documents/wmf/mediawiki/vagrant/puppet/modules
+==> default: Running provisioner: lsb_check...
+==> default: Running provisioner: puppet...
+==> default: Running Puppet with site.pp...
+==> default: stdin: is not a tty
+==> default: Notice: Compiled catalog for mediawiki-vagrant.dev in environment production in 2.88 seconds
+==> default: Info: Applying configuration version '1410428953.no-git'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/multiversion-install]/ensure: created
+==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/51-cloudguest]/ensure: removed
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/mwscript]/ensure: created
+==> default: Notice: /Stage[main]/Main/File[/etc/apt/apt.conf.d/20shared-cache]/ensure: defined content as '{md5}711fa2f2a913db3990e7beb15cf57b5b'
+==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/00-header]/ensure: removed
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/alldbs]/ensure: created
+==> default: Notice: /Stage[main]/Misc/Exec[fix_root_profile]/returns: executed successfully
+==> default: Info: mount[files]: allowing mediawiki-vagrant access
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d]/group: group changed 'root' to 'vagrant'
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/bash_completion.sh]/ensure: removed
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/mediawiki-vagrant.sh]/ensure: defined content as '{md5}e9dcf6a1136af35370d9d8191cb11483'
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/Z99-cloud-locale-test.sh]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/var/www]/ensure: created
+==> default: Notice: /Stage[main]/Main/File[/srv]/owner: owner changed 'root' to 'vagrant'
+==> default: Notice: /Stage[main]/Main/File[/srv]/group: group changed 'root' to 'www-data'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/MWMultiVersion.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/defines.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/resources]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/missing.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/CREDITS]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/opensearch_desc.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/api.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/MWScript.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/thumb_handler.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/skins]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/thumb.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/10-help-text]/ensure: removed
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/index.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/dblist.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/foreachwiki]/ensure: created
+==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/Z97-byobu.sh]/ensure: removed
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/img_auth.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/COPYING]/ensure: created
+==> default: Notice: /Stage[main]/Mysql/File[/home/vagrant/.my.cnf]/ensure: defined content as '{md5}ef06fc0c2fb48af1df465c01df0f9634'
+==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/50-landscape-sysinfo]/ensure: removed
+==> default: Info: /etc/update-motd.d: Scheduling refresh of Exec[update_motd]
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/load.php]/ensure: defined content as '{md5}7c39985a7e1c410e006aeb5897548ee9'
+==> default: Notice: /Stage[main]/Misc/Motd::Script[mediawiki_vagrant]/File[/etc/update-motd.d/50-mediawiki-vagrant]/ensure: defined content as '{md5}3aba016b0d0dda7268fcb1b655ea78f9'
+==> default: Info: /Stage[main]/Misc/Motd::Script[mediawiki_vagrant]/File[/etc/update-motd.d/50-mediawiki-vagrant]: Scheduling refresh of Exec[update_motd]
+==> default: Notice: /Stage[main]/Motd/Exec[update_motd]: Triggered 'refresh' from 2 events
+==> default: Notice: /Stage[main]/Php::Composer/Exec[download_composer]/returns: executed successfully
+==> default: Notice: /Stage[main]/Php::Composer/File[/usr/local/bin/composer]/mode: mode changed '0644' to '0755'
+==> default: Notice: /Stage[main]/Apt/File[/etc/apt/sources.list.d/multiverse.list]/ensure: defined content as '{md5}a4108116df82d5428debf4b06fbd0f54'
+==> default: Notice: /Stage[main]/Apt/File[/usr/local/share/wikimedia-pubkey.asc]/ensure: defined content as '{md5}39e2c3119a82a59d706317fce97a6bfc'
+==> default: Info: /Stage[main]/Apt/File[/usr/local/share/wikimedia-pubkey.asc]: Scheduling refresh of Exec[add_wikimedia_apt_key]
+==> default: Notice: /Stage[main]/Apt/Exec[add_wikimedia_apt_key]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Apt/File[/etc/apt/sources.list.d/wikimedia.list]/ensure: defined content as '{md5}81cc6c07729914e993ebf1829da0e002'
+==> default: Notice: /Stage[main]/Apt/Exec[update_package_index]/returns: executed successfully
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/extensions]/ensure: created
+==> default: Notice: /Stage[main]/Php::Composer/Env::Var[COMPOSER_CACHE_DIR]/File[/etc/profile.d/set_COMPOSER_CACHE_DIR.sh]/ensure: created
+==> default: Notice: /Stage[main]/Main/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+==> default: Notice: /Stage[main]/Main/Package[build-essential]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Misc/Package[ack-grep]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[python-pip]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[ruby-dev]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Misc/Package[htop]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php::Remote_debug/Package[php5-xdebug]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Redis/Package[redis-server]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[python-dev]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[chef-zero]/ensure: removed
+==> default: Notice: /Stage[main]/Mysql::Packages/Package[mysql-server]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Main/Package[chef]/ensure: removed
+==> default: Notice: /Stage[main]/Redis/File[/srv/redis]/ensure: created
+==> default: Notice: /Stage[main]/Apache::Mod::Php5/Package[libapache2-mod-php5]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Misc/File[/etc/ackrc]/ensure: defined content as '{md5}744cd26afe93f6ae5e3f04cee2bbc188'
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/envvars]/content: content changed '{md5}331419cf134c3cdce519b0d0f151cbc9' to '{md5}adf14ad862398d9eaab25c196ffb4f40'
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/envvars]/group: group changed 'root' to 'vagrant'
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/envvars]: Scheduling refresh of Service[apache2]
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/envvars]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache::Mod::Proxy_fcgi/Apache::Mod_conf[proxy_fcgi]/Exec[ensure_present_mod_proxy_fcgi]/returns: executed successfully
+==> default: Info: /Stage[main]/Apache::Mod::Proxy_fcgi/Apache::Mod_conf[proxy_fcgi]/Exec[ensure_present_mod_proxy_fcgi]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mediawiki::Apache/File[/var/www/favicon.ico]/ensure: defined content as '{md5}b1d335c7c87c3d9b0693db6a5dc69d7b'
+==> default: Notice: /Stage[main]/Mediawiki::Apache/File[/var/www/info.php]/ensure: defined content as '{md5}fb92f9147037f47dcf29c96dbc68154d'
+==> default: Notice: /Stage[main]/Php/Package[php5-mysql]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php5-gd]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php-apc]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php5-mcrypt]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php5]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Apache::Mod::Headers/Apache::Mod_conf[headers]/Exec[ensure_present_mod_headers]/returns: executed successfully
+==> default: Info: /Stage[main]/Apache::Mod::Headers/Apache::Mod_conf[headers]/Exec[ensure_present_mod_headers]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Php/Package[php5-sqlite]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/sites-enabled/000-default.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Php/Package[php-pear]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Php/Package[php5-curl]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/env-enabled]/ensure: created
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/env-enabled]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Php/Php::Ini[debug_output]/File[/etc/php5/mods-available/_debug_output.ini]/ensure: defined content as '{md5}d063cce793713a4e99892c1076fcaa4c'
+==> default: Info: /Stage[main]/Php/Php::Ini[debug_output]/File[/etc/php5/mods-available/_debug_output.ini]: Scheduling refresh of Service[apache2]
+==> default: Info: /Stage[main]/Php/Php::Ini[debug_output]/File[/etc/php5/mods-available/_debug_output.ini]: Scheduling refresh of Exec[/usr/sbin/php5enmod -s ALL _debug_output]
+==> default: Notice: /Stage[main]/Php/Php::Ini[debug_output]/Exec[/usr/sbin/php5enmod -s ALL _debug_output]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Php/Php::Ini[session_defaults]/File[/etc/php5/mods-available/_session_defaults.ini]/ensure: defined content as '{md5}7236471110ece2bbd4ff508af9030132'
+==> default: Info: /Stage[main]/Php/Php::Ini[session_defaults]/File[/etc/php5/mods-available/_session_defaults.ini]: Scheduling refresh of Service[apache2]
+==> default: Info: /Stage[main]/Php/Php::Ini[session_defaults]/File[/etc/php5/mods-available/_session_defaults.ini]: Scheduling refresh of Exec[/usr/sbin/php5enmod -s ALL _session_defaults]
+==> default: Notice: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/File[/etc/php5/mods-available/_remote_debug.ini]/ensure: defined content as '{md5}f1115221d2629974b905dc37476797a1'
+==> default: Info: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/File[/etc/php5/mods-available/_remote_debug.ini]: Scheduling refresh of Service[apache2]
+==> default: Info: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/File[/etc/php5/mods-available/_remote_debug.ini]: Scheduling refresh of Exec[/usr/sbin/php5enmod -s ALL _remote_debug]
+==> default: Info: /etc/apache2/sites-enabled: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Php::Composer/Exec[update_composer]/returns: executed successfully
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/security.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Php/Php::Ini[session_defaults]/Exec[/usr/sbin/php5enmod -s ALL _session_defaults]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/other-vhosts-access-log.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/env-available]/ensure: created
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/env-available]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/Exec[/usr/sbin/php5enmod -s ALL _remote_debug]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/serve-cgi-bin.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/security.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/localized-error-pages.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/other-vhosts-access-log.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/charset.conf]/ensure: removed
+==> default: Info: /etc/apache2/conf-available: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/charset.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/localized-error-pages.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/sites-available/default-ssl.conf]/ensure: removed
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/ports.conf]/content: content changed '{md5}a961f23471d985c2b819b652b7f64321' to '{md5}832989c376f29c4740c3bc5eb9ed3f12'
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/ports.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/site-confs]/ensure: created
+==> default: Info: /Stage[main]/Apache/File[/etc/apache2/site-confs]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/serve-cgi-bin.conf]/ensure: removed
+==> default: Info: /etc/apache2/conf-enabled: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mysql/Exec[set_mysql_password]/returns: executed successfully
+==> default: Notice: /Stage[main]/Role::Mediawiki/Package[tidy]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Role::Mediawiki/Package[php5-tidy]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Redis/File[/etc/redis/redis.conf]/content: content changed '{md5}e79ac99a5236e6ab3faf86bdd99affaf' to '{md5}dedc5a2ff609b5cceadc08307646ad54'
+==> default: Info: /Stage[main]/Redis/File[/etc/redis/redis.conf]: Scheduling refresh of Service[redis-server]
+==> default: Notice: /Stage[main]/Redis/Service[redis-server]: Triggered 'refresh' from 1 events
+==> default: Notice: /Stage[main]/Redis::Php/Package[php5-redis]/ensure: ensure changed 'purged' to 'present'
+==> default: Info: /Stage[main]/Redis::Php/Package[php5-redis]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Hhvm/File[/usr/local/bin/hhvmsh]/ensure: defined content as '{md5}db1312e407c8fb05c1fb193692ce5c2f'
+==> default: Notice: /Stage[main]/Hhvm/File[/etc/hhvm]/ensure: created
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-dev]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/File[/etc/hhvm/php.ini]/content: content changed '{md5}38e0be69fb5da2bebc90f17f7fe3c705' to '{md5}ef2004ca4a64aea1d212962c34738666'
+==> default: Info: /Stage[main]/Hhvm/File[/etc/hhvm/php.ini]: Scheduling refresh of Service[hhvm]
+==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/File[/etc/apache2/site-confs/hhvm-admin]/ensure: created
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-luasandbox]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-wikidiff2]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/File[/etc/hhvm/config.hdf]/ensure: defined content as '{md5}2a46fb84966afc8fc3b51fd9abe57378'
+==> default: Info: /Stage[main]/Hhvm/File[/etc/hhvm/config.hdf]: Scheduling refresh of Service[hhvm]
+==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-fss]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Hhvm/File[/etc/init/hhvm.conf]/content: content changed '{md5}48267cf8f84fd68070699cf68ce7f663' to '{md5}329e085674306cc428a3440a0916b40f'
+==> default: Info: /Stage[main]/Hhvm/File[/etc/init/hhvm.conf]: Scheduling refresh of Service[hhvm]
+==> default: Notice: /Stage[main]/Hhvm/Service[hhvm]/ensure: ensure changed 'stopped' to 'running'
+==> default: Info: /Stage[main]/Hhvm/Service[hhvm]: Unscheduling refresh on Service[hhvm]
+==> default: Notice: /Stage[main]/Php/Package[php5-intl]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/File[/etc/apache2/site-confs/hhvm-admin/00-default.conf]/ensure: created
+==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/sites-available/000-default.conf]/ensure: removed
+==> default: Info: /etc/apache2/sites-available: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Git/Package[git]/ensure: ensure changed 'purged' to 'latest'
+==> default: Notice: /Stage[main]/Git/Package[git-review]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/tests]/ensure: created
+==> default: Notice: /Stage[main]/Php/Package[php5-readline]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Misc/File[/usr/local/sbin/isfresh]/ensure: defined content as '{md5}6fee8323b6bdd6afc7c37faa4491794a'
+==> default: Notice: /Stage[main]/Apache/Misc::Evergreen[apache2]/Exec[check_apache2_freshness]/returns: executed successfully
+==> default: Info: /Stage[main]/Apache/Misc::Evergreen[apache2]/Exec[check_apache2_freshness]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/MWVersion.php]/ensure: created
+==> default: Notice: /Stage[main]/Php/Package[php5-dev]/ensure: ensure changed 'purged' to 'present'
+==> default: Notice: /Stage[main]/Mediawiki/File[/usr/local/bin/run-mediawiki-tests]/ensure: defined content as '{md5}cb1918d4464e50c256399b91c411bb05'
+==> default: Notice: /Stage[main]/Mediawiki/File[/usr/local/bin/import-mediawiki-dump]/ensure: defined content as '{md5}81874e61ef7c14f0a5b1aa87a337cfbb'
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/vagrant/settings.d/wikis]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/File[/var/cache/mediawiki]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/vagrant/settings.d/wikis/LoadWgConf.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/File[/usr/local/bin/run-git-update]/ensure: defined content as '{md5}5ff218ed45bf3ea414f9c4776e9210d2'
+==> default: Notice: /Stage[main]/Mediawiki/Env::Profile_script[add mediawiki vendor bin to path]/File[/etc/profile.d/50-add-mediawiki-vendor-bin-to-path.sh]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Env::Var[MW_INSTALL_PATH]/File[/etc/profile.d/set_MW_INSTALL_PATH.sh]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/vagrant/settings.d/wikis/CommonSettings.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/jobrunner.json]/ensure: defined content as '{md5}670966939c990598a91362cb0ffb75ac'
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/File[/etc/jobrunner.json]: Scheduling refresh of Service[jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/default/jobrunner]/ensure: defined content as '{md5}baefee683608d285b2c4895c8f76c563'
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/File[/etc/default/jobrunner]: Scheduling refresh of Service[jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki/File[/srv/images]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: Composer could not find a composer.json file in /vagrant/mediawiki
+==> default: Notice: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: To initialize a project, please create a composer.json file as described in the http://getcomposer.org/ ""Getting Started"" section
+==> default: Error: composer install --optimize-autoloader returned 1 instead of one of [0]
+==> default: Error: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: change from notrun to 0 failed: composer install --optimize-autoloader returned 1 instead of one of [0]
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/wgConf.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/dbConf.php]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/File[mediawiki_upstart_bridge]/ensure: defined content as '{md5}b1cfb3aa1f75ada7780442b4a8a1ca76'
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/settings.d]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/settings.d/puppet-managed]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/settings.d/puppet-managed/README]/ensure: defined content as '{md5}64ae42537fb40c737e432f1e747355f7'
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_setup]/returns: executed successfully
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_include_extra_settings]/returns: executed successfully
+==> default: Notice: /Stage[main]/Mediawiki/Exec[copy_LocalSettings]/returns: executed successfully
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/logrotate.d/mediawiki_jobrunner]/ensure: defined content as '{md5}108922f7a7305cd4f69202fa6ba6d2ee'
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Git::Clone[mediawiki/services/jobrunner]/Exec[git_clone_mediawiki/services/jobrunner]/returns: executed successfully
+==> default: Info: Git::Clone[mediawiki/services/jobrunner]: Scheduling refresh of Exec[git_install_checkout_mediawiki/services/jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Exec[git_install_reset_mediawiki/services/jobrunner]/returns: executed successfully
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Exec[git_install_reset_mediawiki/services/jobrunner]: Scheduling refresh of Exec[git_install_checkout_mediawiki/services/jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Exec[git_install_checkout_mediawiki/services/jobrunner]: Triggered 'refresh' from 2 events
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: fatal: destination path '/vagrant/mediawiki/skins/Vector' already exists and is not an empty directory.
+==> default: Error: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]
+==> default: Error: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: change from notrun to 0 failed: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]
+==> default: Notice: /Stage[main]/Mediawiki/File[/var/www/mediawiki-vagrant.png]/ensure: defined content as '{md5}f9afb7d19e39247820bc1e81883a96f7'
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Dependency Exec[git_clone_mediawiki/skins/Vector] has failures: true
+==> default: Warning: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Skipping because of failed dependencies
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/init/jobrunner.conf]/ensure: defined content as '{md5}e2302b512e81c3d406f8f2159dd4dbcd'
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/File[/etc/init/jobrunner.conf]: Scheduling refresh of Service[jobrunner]
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Service[jobrunner]/ensure: ensure changed 'stopped' to 'running'
+==> default: Info: /Stage[main]/Mediawiki::Jobrunner/Service[jobrunner]: Unscheduling refresh on Service[jobrunner]
+==> default: Notice: /Stage[main]/Apache::Mod::Rewrite/Apache::Mod_conf[rewrite]/Exec[ensure_present_mod_rewrite]/returns: executed successfully
+==> default: Info: /Stage[main]/Apache::Mod::Rewrite/Apache::Mod_conf[rewrite]/Exec[ensure_present_mod_rewrite]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/Apache::Conf[disable sendfile]/File[/etc/apache2/conf-available/50-disable-sendfile.conf]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/Apache::Conf[devwiki]/File[/etc/apache2/sites-available/50-devwiki.conf]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/Apache::Conf[devwiki]/File[/etc/apache2/sites-enabled/50-devwiki.conf]/ensure: created
+==> default: Info: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/Apache::Conf[devwiki]/File[/etc/apache2/sites-enabled/50-devwiki.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/Apache::Conf[php5-devwiki]/File[/etc/apache2/sites-available/50-php5-devwiki.conf]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/Apache::Conf[php5-devwiki]/File[/etc/apache2/sites-enabled/50-php5-devwiki.conf]/ensure: created
+==> default: Info: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/Apache::Conf[php5-devwiki]/File[/etc/apache2/sites-enabled/50-php5-devwiki.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/File[/etc/apache2/site-confs/php5-devwiki]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/File[/etc/apache2/site-confs/php5-devwiki/00-default.conf]/ensure: created
+==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/Apache::Conf[hhvm-admin]/File[/etc/apache2/sites-available/50-hhvm-admin.conf]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/File[/etc/apache2/site-confs/devwiki]/ensure: created
+==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/File[/etc/apache2/site-confs/devwiki/00-default.conf]/ensure: created
+==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/Apache::Conf[hhvm-admin]/File[/etc/apache2/sites-enabled/50-hhvm-admin.conf]/ensure: created
+==> default: Info: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/Apache::Conf[hhvm-admin]/File[/etc/apache2/sites-enabled/50-hhvm-admin.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/Apache::Conf[disable sendfile]/File[/etc/apache2/conf-enabled/50-disable-sendfile.conf]/ensure: created
+==> default: Info: /Stage[main]/Apache/Apache::Conf[disable sendfile]/File[/etc/apache2/conf-enabled/50-disable-sendfile.conf]: Scheduling refresh of Service[apache2]
+==> default: Notice: /Stage[main]/Apache/Service[apache2]: Triggered 'refresh' from 22 events
+==> default: Info: Creating state file /var/lib/puppet/state/state.yaml
+==> default: Notice: Finished catalog run in 180.74 seconds
+The SSH command responded with a non-zero exit status. Vagrant
+assumes that this means the command failed. The output for this command
+should be in the log above. Please read the output to determine what
+went wrong.
+```",1410429960,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_description,resolved
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""",">>! In T72705#976450, @Kabhi2104 wrote:
+> {F28605} Uploaded provision.log here too for future reference and this is the link of new paste https://phabricator.wikimedia.org/P216 
+
+Further discussion moved to {T86787}",1421257654,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","{F28605} Uploaded provision.log here too for future reference and this is the link of new paste https://phabricator.wikimedia.org/P216 
+",1421256985,PHID-USER-cqpeh4jvvexbszsxogrw,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""",">>! In T72705#975760, @Kabhi2104 wrote:
+> I am facing the same problem in ubuntu 14.04.
+> When i run vagrant up i get  **"" VirtualBox VM is already running. ""**
+> While running 127.0.0.1:8080  says  **webpage not available**
+> http://imgur.com/R5ZDXCJ  regarding roles in **vagrant list-roles**
+> I get full bunch of red errors while running **vagrant provision** Here: http://imgur.com/yWohm04
+
+Adding a ""me too"" to a closed ticket probably isn't the best way to get good support. ;)
+
+The errors shown from your puppet provisioning run in the screen capture don't show enough to indicate where things went wrong, just that you had a cascading dependency failure. Based solely on past experience I would guess that there was an apt-get failure that ended up blocking Puppet from doing anything else.
+
+To get a real trace of the problem, you could run `PUPPET_DEBUG=1 vagrant reload --provision | tee provision.log` and then upload provision.log as a paste here and open a new ticket referencing it. The command given will restart the virtual machine and then force a Puppet run. The `PUPPET_DEBUG=1` environment var will tell Puppet to output more information on what it is doing at each stage of the run and `| tee provision.log` will make a copy of all the information sent to the screen in a log file that will be easier to cut-n-paste into [[https://phabricator.wikimedia.org/paste/create/|a new pastebin issue]].",1421253858,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","I am facing the same problem in ubuntu 14.04.
+When i run vagrant up i get  **"" VirtualBox VM is already running. ""**
+While running 127.0.0.1:8080  says  **webpage not available**
+http://imgur.com/R5ZDXCJ  regarding roles in **vagrant list-roles**
+I get full bunch of red errors while running **vagrant provision** Here: http://imgur.com/yWohm04",1421240910,PHID-USER-cqpeh4jvvexbszsxogrw,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""",Thanks for reporting this and writing it up.  I just ran into this. :(,1418456754,PHID-USER-qsj6mtmeexjxulfje7ie,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","(In reply to Bryan Davis from comment #4)
+> Was the vagrant/mediawiki clone new too or potentially very old?
+
+My vagrant/mediawiki clone was so old... (insert joke here).
+
+Documented:
+
+https://www.mediawiki.org/w/index.php?title=MediaWiki-Vagrant&diff=1151216&oldid=1139643",1410524423,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","(In reply to Bryan Davis from comment #4)
+> $ cd vagrant/mediawiki
+> $ git pull
+
+Wait, mediawiki (core?) does not get updated automatically!? Trying this now, will report in a few hours (when the machine is up).",1410521945,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","Was the vagrant/mediawiki clone new too or potentially very old? At least some of these errors look like your vagrant/mediawiki/skins/Vector directory is from before the changes were merged that made Vector a separate repository. The fix for that is given in <https://bugzilla.wikimedia.org/show_bug.cgi?id=70114#c1> :
+
+$ cd vagrant/mediawiki
+$ git pull
+$ cd skins
+$ rm -rf Vector  # might not be a dir here to delete now but worth trying
+$ vagrant provision",1410448617,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","Surprisingly, mediawiki is available at http://127.0.0.1:8080/wiki/Main_Page",1410430516,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","No roles are enabled, I have forgot to mention that.
+
+$ vagrant list-roles
+Available roles:
+
+  accountinfo                graph                      poem                    
+  analytics                  guidedtour                 popups                  
+  antispam                   gwtoolset                  proofreadpage           
+  antispoof                  hadoop                     renameuser              
+  apisandbox                 hive                       scholarships            
+  apparmor                   https                      scribunto               
+  babel                      hue                        simple_miser            
+  betafeatures               imagemetrics               simple_performant       
+  categorytree               interwiki                  sitematrix              
+  centralauth                jsduck                     svg                     
+  centralnotice              jsonconfig                 templatedata            
+  chromium                   labledsectiontransclusion   textextracts            
+  cirrussearch               mantle                     thumb_on_404            
+  cite                       massmessage                timedmediahandler       
+  cldr                       math                       translate               
+  codeeditor                 mathsearch                 uls                     
+  cologneblue                mleb                       uploadwizard            
+  commons                    mobileapp                  urlshortener            
+  commonsmetadata            mobilefrontend             usermerge               
+  confirmedit                modern                     vectorbeta              
+  doublewiki                 molhandler                 visualeditor            
+  echo                       monobook                   warnings_as_errors      
+  education                  multimedia                 wikidata                
+  eventlogging               multimediaviewer           wikidiff2               
+  featuredfeeds              navigationtiming           wikieditor              
+  flow                       newusermessage             wikihiero               
+  fss                        oauth                      wikilove                
+  fundraising                oozie                      wikimediaevents         
+  gadgets                    pagedtiffhandler           wikimediaincubator      
+  gadgets2                   pageimages                 wikimediamessages       
+  geodata                    pagetriage                 wikimetrics             
+  geshi                      parserfunctions            wikitech                
+  gettingstarted             parsoid                    xhprof                  
+  globalcssjs                pdfhandler                 zend                    
+  globaluserpage             phptags                    zero                    
+
+Roles marked with '*' are enabled.
+Note that roles enabled by dependency are not marked.
+Use ""vagrant enable-role"" & ""vagrant disable-role"" to customize.",1410430492,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+"""vagrant up"" fails with ""The SSH command responded with a non-zero exit status.""","Lines from ""vagrant up"" that are highlighted in my terminal (yellow or red) and one line before and after, for context:
+
+$ vagrant up
+...
+==> default: Machine booted and ready!
+GuestAdditions versions on your host (4.3.16) and guest (4.3.10) do not match.
+stdin: is not a tty
+...
+mount: block device /tmp/VBoxGuestAdditions.iso is write-protected, mounting read-only
+Installing Virtualbox Guest Additions 4.3.16 - guest version is 4.3.10
+stdin: is not a tty
+...
+Could not find the X.Org or XFree86 Window System, skipping.
+An error occurred during installation of VirtualBox Guest Additions 4.3.16. Some functionality may not work as intended.
+In most cases it is OK that the ""Window System drivers"" installation failed.
+stdin: is not a tty
+...
+==> default: Notice: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: To initialize a project, please create a composer.json file as described in the http://getcomposer.org/ ""Getting Started"" section
+==> default: Error: composer install --optimize-autoloader returned 1 instead of one of [0]
+==> default: Error: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: change from notrun to 0 failed: composer install --optimize-autoloader returned 1 instead of one of [0]
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki]/ensure: created
+...
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: fatal: destination path '/vagrant/mediawiki/skins/Vector' already exists and is not an empty directory.
+==> default: Error: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]
+==> default: Error: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: change from notrun to 0 failed: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]
+==> default: Notice: /Stage[main]/Mediawiki/File[/var/www/mediawiki-vagrant.png]/ensure: defined content as '{md5}f9afb7d19e39247820bc1e81883a96f7'
+...
+==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Dependency Exec[git_clone_mediawiki/skins/Vector] has failures: true
+==> default: Warning: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Skipping because of failed dependencies
+==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/init/jobrunner.conf]/ensure: defined content as '{md5}e2302b512e81c3d406f8f2159dd4dbcd'
+...
+==> default: Notice: Finished catalog run in 180.74 seconds
+The SSH command responded with a non-zero exit status. Vagrant
+assumes that this means the command failed. The output for this command
+should be in the log above. Please read the output to determine what
+went wrong.",1410430161,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-vqfyeha7beo3b4cn7bu7,task_subcomment,NA
+VisualEditor: Media search not working in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Enter something in the search box to search for images
+
+
+Observed Result:
+
+Nothing happens. ""No Results"" found message stays in the dialog instead
+
+Environment:Betalabs
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14832}",1410289080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-miymejtyr774ogj6oozg,task_description,resolved
+VisualEditor: Media search not working in Betalabs,Yeah may be..Working for me now as well,1410302702,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-miymejtyr774ogj6oozg,task_subcomment,NA
+VisualEditor: Media search not working in Betalabs,Works for me… Search blip?,1410299536,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-miymejtyr774ogj6oozg,task_subcomment,NA
+VisualEditor: The Field description popup looks weird on mediawiki.org,"Field description popup for template:Bugzilla on mediawiki.org
+
+See attachment. A lot of wasted empty space, and a scrollbar :) Possibly related to other reports, or a dupe.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70423
+
+**Attached**: {F14777}",1410258120,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-un6exrb6nu4tk4ohkbsk,task_description,resolved
+VisualEditor: The Field description popup looks weird on mediawiki.org,"My patch for bug 70423 seems to fix this.
+
+*** This bug has been marked as a duplicate of bug 70423 ***",1410356188,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-un6exrb6nu4tk4ohkbsk,task_subcomment,NA
+VisualEditor: The Field description popup looks weird on mediawiki.org,Same for the Special Characters dialog.,1410259729,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-un6exrb6nu4tk4ohkbsk,task_subcomment,NA
+"VisualEditor: The References List dialog looks too big, much unnecessary empty space","References list trying to impress us
+
+See screenshot (which was taken in IE), I tried with other browsers and it looked the same there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68226
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70423
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70016
+
+**Attached**: {F14773}",1410253440,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-kecyjmzzfanyavgzh5ry,task_description,resolved
+"VisualEditor: The References List dialog looks too big, much unnecessary empty space","
+
+*** This bug has been marked as a duplicate of bug 70016 ***",1414137121,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-kecyjmzzfanyavgzh5ry,task_subcomment,NA
+VisualEditor: The link inspector and comment box are appearing with no UI while opening them after an idle time,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Keep it open for a while (~10-15 mins)
+3.After coming back to this page, open a link inspector or a comment box 
+
+Observed Result:
+They open with no UI, see the screenshot attached.
+
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61078
+
+**Attached**: {F14719}",1410209040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5vpeo4fnxwtoxb7qsyxu,task_description,duplicate
+"VisualEditor: Link icon stays selected but is not inserted, with language style text.","screenshot
+
+Environment- test2, beta
+
+1> open a page in VE, insert some text. Open the language inspector and click on link icon.
+2> Now click anywhere on the Editor and type in some more text, the language inspector closes but the link icon stays selected.See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14676}",1410192240,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-oaaxxaeryjuj676qlgup,task_description,declined
+"VisualEditor: Link icon stays selected but is not inserted, with language style text.","(In reply to etonkovidova from comment #1)
+> Checked in test2 on Chrome - cannot confirm.
+
+Not reproducible. close the issue.",1415642571,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-oaaxxaeryjuj676qlgup,task_subcomment,NA
+"VisualEditor: Link icon stays selected but is not inserted, with language style text.",Checked in test2 on Chrome - cannot confirm.,1415406839,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-oaaxxaeryjuj676qlgup,task_subcomment,NA
+VisualEditor:  Bad things happen when you paste cruft-laden text from somewhere else,"An editor pasted text at the newly created https://en.wikipedia.org/w/index.php?title=Kalles_Fraktaler&oldid=624532595
+
+which resulted in this when the page was saved:
+
+<object type=""cosymantecnisbfw"" cotype=""cs"" id=""cosymantecnisbfw"" style=""width: 0px; height: 0px; display: block;""></object><object type=""cosymantecnisbfw"" cotype=""bgpage"" id=""cosymantecnisbfwbg"" style=""width: 0px; height: 0px; display: block;""></object><script type=""text/javascript"" defer=""defer"" id=""NortonInternetSecurityBF"" tab=""0"" browser=""0"">function NavigateTo(url, newWindow) { var myObject = new Object(); myObject.url = url; myObject.newWindow = newWindow; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcBFNavigateTo', false, false, myObject); document.dispatchEvent(theEvent); } function ChangeToolbarIcon(inText, inImage) { var myObject = new Object(); myObject.text = inText; myObject.image = inImage; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('changeToolbarIconEventHandler', false, false, myObject); document.dispatchEvent(theEvent); } function DimPage() { dimElement = document.createElement('div'); dimElement.id = 'coShastaDimDiv'; dimElement.style.cssText = 'z-index:10;width:100%;height:100%;background-color:black;opacity:0.60;position:absolute;top:0;left:0;'; var theBody = document.getElementsByTagName('body')[0]; theBody.appendChild(dimElement); } function NPNNew() { theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcBFActivate', false, false, 0); document.dispatchEvent(theEvent); } function UpdatePageStatus(inURL) { var myObject = new Object(); myObject.blockURL = inURL; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('updatePageStatusEventHandler', false, false, myObject); document.dispatchEvent(theEvent);}function UpdateToolbarMenu(inSafeSearch) { var myObject = new Object(); myObject.SafeSearch = inSafeSearch; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('updateToolbarMenuEventHandler', false, false, myObject); document.dispatchEvent(theEvent);}function SetBarVisibility(barstatus) { var myObject = new Object(); myObject.barstatus = barstatus; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('setBarVisibilityEventHandler', false, false, myObject); document.dispatchEvent(theEvent);}function SetCachedStrings(inText, inImage, inTextNA, inImageNA) { var myObject = new Object(); myObject.text = inText; myObject.image = inImage; myObject.textNA = inTextNA; myObject.imageNA = inImageNA; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('setCachedStringsEventHandler', false, false, myObject); document.dispatchEvent(theEvent); } function SetResourceFolder(inFolder) { var myObject = new Object(); myObject.resFolder = inFolder; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('setResourceFolderEventHandler', false, false, myObject); document.dispatchEvent(theEvent); } function SetSafeSearchValues(isSSEinPrefs, isSSEinSafeMgr,isBuzz, showMyAccount) { var myObject = new Object(); myObject.showMyAccount = showMyAccount; myObject.isSSEinPrefs = isSSEinPrefs; myObject.isBuzz=isBuzz; myObject.isSSEinSafeMgr=isSSEinSafeMgr; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('setSafeSearchValuesEventHandler', false, false, myObject); document.dispatchEvent(theEvent); } function ShowSafeSearchOffering() {theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcShowSafeSearchOffering', false, false, 0); document.dispatchEvent(theEvent); } function SafeSearchOfferResponded() {theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcSafeSearchOfferResponded', false, false, 0); document.dispatchEvent(theEvent); } function SetSearchString(inQuery) { var myObject = new Object(); myObject.query = inQuery; theEvent = document.createEvent('CustomEvent'); theEvent.initCustomEvent('symcSetSearchString', false, false, myObject); document.dispatchEvent(theEvent); } </script><object type=""cosymantecnisbfw"" cotype=""cs"" id=""SILOBFWOBJECTID"" style=""width: 0px; height: 0px; display: block;""></object> Kalles Fraktaler is a Windows-based fractal zoom computer program used for zooming into the Mandelbrot set or the Burning Ship fractal. <object type=""cosymantecnisbfw"" cotype=""cs"" id=""SILOBFWOBJECTID"" style=""width: 0px; height: 0px; display: block;""></object>
+
+cosymantecnisbfw appears to be related to NortonInternetSecurityBF
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410129540,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yb4podernpcrt5eyrrqt,task_description,resolved
+VisualEditor:  Bad things happen when you paste cruft-laden text from somewhere else,"
+
+*** This bug has been marked as a duplicate of bug 63229 ***",1410130325,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-yb4podernpcrt5eyrrqt,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21]TypeError: boundingRect is undefined and TypeError: surfaceRect is undefined appears when opening Media Settings dialog,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+
+Observed Result:
+The following errors are appearing in the console:
+
+
+TypeError: boundingRect is undefined
+
+TypeError: surfaceRect is undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15082}",1409946720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4irstsowbqex2mh6wzgk,task_description,invalid
+VisualEditor: [Regression pre-wmf21]TypeError: boundingRect is undefined and TypeError: surfaceRect is undefined appears when opening Media Settings dialog,"Yes, working fine now",1409959016,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4irstsowbqex2mh6wzgk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21]TypeError: boundingRect is undefined and TypeError: surfaceRect is undefined appears when opening Media Settings dialog,This was fixed by https://gerrit.wikimedia.org/r/#/c/158519/ but not pulled through. Sorry! It's pulled through now.,1409952229,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4irstsowbqex2mh6wzgk,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.","screenshot1
+
+1> open a blank page in VE, open the Language inspector. 
+2> Now click anywhere in the Editor, the inspector stays open but the language style text drop-down selection turns blank. After that any selection you make, it continues to stay blank. And if you type in any text, a pawn gets inserted beside the text. See screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F15074}",1409943780,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-mwpy2efniouotho4t26d,task_description,declined
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.",Per submitter.,1415143058,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.",Not reproducible.,1415108215,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.","Apologies.. here are the steps-
+
+1> open a blank page in VE, open the Language inspector and select a text style from the drop-down,for ex- select Heading.
+2> Now click anywhere in the Editor, the inspector  closes, but the text style drop-down selection turns blank. After that any selection you make, it continues to stay blank. And if you type in any text, a pawn gets inserted beside the text. See screenshots.
+
+Delete the text and the pawn character and reapeat steps #1 and 2, JS console error is ""Uncaught Error: Offset could not be translated to a DOM element and offset: 3"".",1410208205,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.","After deleting the text and pawn characters as mentioned in the steps above when i  repeat the steps #1 and #2, i get this console error 
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 3",1409944218,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.",Environment-test2,1409943850,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+"VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.","Created attachment 16388
+screenshot2
+
+**Attached**: {F15075}",1409943820,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-mwpy2efniouotho4t26d,task_subcomment,NA
+VisualEditor: comment feature should be removed by default,"<!-- comments are not recommended for users: it is hidden!  -->
+
+Comments aren't recommended for new editors (and for 99% of the times for advanced users too), as must comments should be written in talk page.
+
+It is not just a non useful feature, it is a harmful feature, as people get confused between reference and comments and it leads to ""too many icons"" problem. Please remove comment button from toolbar completely, or at least change it to opt-in/out feature.  (Only the toolbar icon, as the option to show and edit already written comments is important)
+
+Side benefit: less code to maintain and less bugs ;)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1409923860,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-c4uueulkx7xekhb35rdo,task_description,declined
+VisualEditor: comment feature should be removed by default,"James, comments are great to VIEW & EDIT, but there is no reason to ADD comments in VE. Please consider removing the button, as new editors don't understand what is ""comment"" (they use it instead of citation).",1410209524,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-c4uueulkx7xekhb35rdo,task_subcomment,NA
+VisualEditor: comment feature should be removed by default,"(In reply to Eran Roz from comment #0)
+> <!-- comments are not recommended for users: it is hidden!  -->
+> 
+> Comments aren't recommended for new editors (and for 99% of the times for
+> advanced users too), as must comments should be written in talk page.
+
+The principal use of HTML comments in articles is to warn new editors to not do something that seems ""obvious"" but there is talk-page consensus to not do. This was a very widely-requested pain point from experienced editors who felt now showing the comments was very damaging to new users' expereience. Hiding comments which are there for new users seems like the wrong way around…
+
+Long term, this will hopefully be replaced by a proper in-editor discussion system, but until that's done, this will have to do.",1410198549,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c4uueulkx7xekhb35rdo,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,"**Author:** `gryllida`
+
+**Description:**
+I'd like to enable a new beta feature on a wiki, but I wouldn't like the users to enable it thoughtlessly, as it currently breaks a lot of things. For this reason, I'd like to be able to append a 'do NOT use this! only for developers' note to such beta feature in the beta tab.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409922720,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ack5uaxekj6oz3tbot5c,task_description,declined
+BetaFeatures should have means to provide a custom note on-wiki,"(In reply to Gryllida from comment #4)
+> James Forrester, I expected you to be most familiar with the context here --
+> installation of visualeditor at non-Wikipedias as a sort-of-pre-beta
+> feature, while people script visualeditor to suit the project needs.
+
+This is the very first time you've suggested it, so no, I'm not remotely familiar with your idea. :-)",1410060066,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,"**gryllida** wrote:
+
+James Forrester, I expected you to be most familiar with the context here -- installation of visualeditor at non-Wikipedias as a sort-of-pre-beta feature, while people script visualeditor to suit the project needs.
+
+If it's put as a beta feature, a lot of people will enable it and make edits that break things or at least don't provide the relevant features (for wikipedias, this is the common use of <ref> tag, for instance; for its sisters, it's a need in other toolbar buttons and often lack of need in <ref> tag in the first place).",1409969828,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,"If there are severe issues that would ""break a lot of things"" it's not ready to be a Beta Feature and for WMF servers we wouldn't let it go live. Consequently I don't see a valid use case and am marking as WONTFIX.",1409950426,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,Editing the MediaWiki messages isn't good enough?,1409948431,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+BetaFeatures should have means to provide a custom note on-wiki,"Hmm. Does that sound like a common usecase, or rather like something that you could hack up yourself if really wanted? I don't know...",1409925140,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ack5uaxekj6oz3tbot5c,task_subcomment,NA
+"VisualEditor bugs: wikilinks, tables, nowiki and other","VisualEditor editor is full of bugs. Since his implementation i have disabled it for me, because, as experimented user i just like to edit clean code.
+So, i noticed folowing bugs
+when you edit a part of a wikilink (termination) visual editor leaves old wikilink as adrress and only add new edited variant as label. For example if you want to correct digit of an wikilinked year - your action will just add a correct label but wikilink will be the same, old.
+I first noticed this on rowiki when anonymous users edited wikipedia. One fresh example can be this https://ro.wikipedia.org/w/index.php?title=Gustar_%28festival%29&diff=8812463&oldid=8805982
+Now i tested myself this ""phenomenon"" on test2wiki and i obtained the same result
+https://test2.wikipedia.org/w/index.php?title=Edit_page_for_firefox&diff=104063&oldid=104062
+
+Other bug: when you try to remove title of a section from a page (for merging 2 sections), visual editor removes only caption but it keeps the real section heading (====) and adds between equal sign an ""<nowiki/>"". The result will be ==<nowiki/>== and section will exist further without title. Test edit: https://test2.wikipedia.org/w/index.php?title=New_page_for_bugzilla&diff=104066&oldid=104065
+
+Also there exists some problems when copying of tables in a page edited via VisualEditor. VisualEditor adds again some <nowiki> </nowiki> tags, and in some cases adds magic words like __INDEX__ and __NEWSECTIONLINK__
+Example (real edit on rowiki): https://ro.wikipedia.org/w/index.php?title=Kiesza&diff=next&oldid=8808818
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1409835300,PHID-USER-kzriyxckmvupw2nlyshe,False,PHID-TASK-i3da234yo25qxkfj7b4k,task_description,resolved
+"VisualEditor bugs: wikilinks, tables, nowiki and other","I noticed again a bug related to <nowiki/>
+
+Some user tried several times to add image and each time image (code) was put betweeen <nowiki/> tags
+Diffs:
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969441&oldid=8969436
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969445&oldid=8969444
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969449&oldid=8969448",1419347371,PHID-USER-kzriyxckmvupw2nlyshe,False,PHID-TASK-i3da234yo25qxkfj7b4k,task_subcomment,NA
+"VisualEditor bugs: wikilinks, tables, nowiki and other","Again noticed bug related to <nowiki/>
+
+Some user tried several times to add image and each time image (code) was put betweeen <nowiki/> tags
+Diffs:
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969441&oldid=8969436
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969445&oldid=8969444
+https://ro.wikipedia.org/w/index.php?title=The_Pirate_Bay&diff=8969449&oldid=8969448",1419347343,PHID-USER-kzriyxckmvupw2nlyshe,False,PHID-TASK-i3da234yo25qxkfj7b4k,task_subcomment,NA
+"VisualEditor bugs: wikilinks, tables, nowiki and other","Thanks for posting this.
+
+The first problem is ""working as designed"", but the design is seriously being discussed because of exactly this problem.  This item is best described as a duplicate of multiple other bug reports.  See bug 48789 for a list of most open link-related bugs.
+
+The second problem is bug 50100.  Also, this is what you'd expect from a word processor (like Microsoft Word):  if you type ""My Title"" and set bold formatting or a large font size on those words, and then you remove all the letters on that line, and start typing again, then you do expect the font size and bold formatting to be retained.  This report is a duplicate.
+
+On the third one (the table in ro.wp's [[Kiesza]]), it appears that the editor copied the wikitext code out of en.wp's article, and pasted it directly into VisualEditor.  VisualEditor then assumes that you wanted this pasted text to display (i.e., as if you were writing a help page telling someone what wikitext to type, so you really wanted the wikitext on the page).  Magic words can be set in VisualEditor by going to the Page options menu, choosing ""Advanced settings"", and clicking the buttons to turn on those magic words.  This report should be closed as ""working as designed"".
+
+I'm going to mark the whole thing as ""Resolved"", but without trying to specify it as a duplicate, because I don't know if Bugzilla can handle multiple duplicate numbers.  If you have other questions, then please feel free to follow up at those other open bugs.",1410804889,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-i3da234yo25qxkfj7b4k,task_subcomment,NA
+"VisualEditor bugs: wikilinks, tables, nowiki and other","Please file only one specific problem per report and stick to the topic (general complaints about perceived quality of software can go to wikis, mailing lists, blogs). https://www.mediawiki.org/wiki/How_to_report_a_bug might come handy. Thanks.",1409839210,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-i3da234yo25qxkfj7b4k,task_subcomment,NA
+VisualEditor:  Do not permit empty section headings (wikitext like == == or similar),"Sometimes users set the format of a line to be a == Section heading ==, but never put anything in it.  In that case, the section heading formatting should be removed.  There's no good reason to have == == or === === by itself on a line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409787120,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-n3nv2432ws3qayvnnhn2,task_description,resolved
+VisualEditor:  Do not permit empty section headings (wikitext like == == or similar),"
+
+*** This bug has been marked as a duplicate of bug 49452 ***",1415886608,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-n3nv2432ws3qayvnnhn2,task_subcomment,NA
+Page Options Dialog width is not wide enough,"**Author:** `josephsieh`
+
+**Description:**
+On http://en.wikipedia.beta.wmflabs.org/wiki/Cite_VisualEditor_Test?veaction=edit, when you click on the ""Page Options"" icon, the pop-up page options dialog appears to be too narrow.  Characters are missing.
+
+OS X 10.9.4.
+Safari 7.0.6
+Firefox 32.0
+
+visual editor version: https://git.wikimedia.org/tree/mediawiki%2Fextensions%2FVisualEditor.git/bfbe8cbbebe0a461d0ee68c0491b901507636fe2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1409704920,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pidkwinuimfpigrlcpjx,task_description,resolved
+Page Options Dialog width is not wide enough,"Yeah, this is a painful issue; merging with bug 57366.
+
+*** This bug has been marked as a duplicate of bug 57366 ***",1409767558,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pidkwinuimfpigrlcpjx,task_subcomment,NA
+Page Options Dialog width is not wide enough,"**josephsieh** wrote:
+
+Screen shot
+
+**Attached**: {F14703}",1409704989,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pidkwinuimfpigrlcpjx,task_subcomment,NA
+VisualEditor:  Adding a template to a redirect did not let me save the page,"Steps taken:
+
+1.  Open a redirect to edit.
+
+2.  Add a template:  {{R from other languages}}
+
+3.  Discover that I can't save.  The green 'save' button is still gray and non-functional.
+
+4.  Mash the keyboard to add some text to the page.  
+
+5.  Still can't save.  Give up and cancel the edit.
+
+
+This happened in Firefox on my Mac; when I closed the page and tried again, it worked correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409696880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-c5xlvoaq4xlahtprsd7f,task_description,resolved
+VisualEditor:  Adding a template to a redirect did not let me save the page,"Sounds like the editor had crashed by the time you added the template… Can't reproduce now, however. :-(",1423675003,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-c5xlvoaq4xlahtprsd7f,task_subcomment,NA
+VisualEditor:  Adding a template to a redirect did not let me save the page,"Created attachment 16345
+Screenshot showing the template that I just added (highlighted in blue) and the still-gray 'Save' button
+
+**Attached**: {F14679}",1409697055,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-c5xlvoaq4xlahtprsd7f,task_subcomment,NA
+"VisualEditor:  When image search results are returned very slowly, remove the ""No results found"" error message","""No results found"" overlaps with the results that were found
+
+Steps to reproduce:
+
+1.  Open VisualEditor and Insert > Media
+
+2.  Search for File:Alf Cooke's Packaging Factory - Hunslet Road - geograph.org.uk - 483165.jpg 
+
+3.  Nothing happens:  ""No results found"".
+
+4.  Spend a few moments grumbling about the stupidity of a search tool that cannot find a file even when you give it the complete and exact file name.
+
+5.  Spend a few moments groaning because there's no way to add this image unless the search tool can find it, even when you know the exact file name.
+
+6.  Hey!  Search finally found the image!  Why does VisualEditor still say ""No results found"" on top of the results?
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14693}",1409620980,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-buxz75urt74gcutli3bm,task_description,resolved
+"VisualEditor:  When image search results are returned very slowly, remove the ""No results found"" error message","
+
+*** This bug has been marked as a duplicate of bug 67438 ***",1409669754,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-buxz75urt74gcutli3bm,task_subcomment,NA
+VisualEditor: inserted special characters doesn't respect the surrounding text formatting,"To reproduce:
+
+1. Write text. Make it bold.
+2. Put the caret in the middle of the bold text.
+3. Insert a special character.
+
+Actual: The inserted character is not bold.
+
+Expected: The inserted character is bold like the surrounding text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409595060,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-a3kbjn7bnws47ljk6ywa,task_description,resolved
+VisualEditor: inserted special characters doesn't respect the surrounding text formatting,"
+
+*** This bug has been marked as a duplicate of bug 60476 ***",1409596086,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a3kbjn7bnws47ljk6ywa,task_subcomment,NA
+VisualEditor: inserted special characters doesn't respect the surrounding text formatting,"Change 157703 had a related patch set uploaded by Esanders:
+Annotate inserted special characters
+
+https://gerrit.wikimedia.org/r/157703",1409595941,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a3kbjn7bnws47ljk6ywa,task_subcomment,NA
+VisualEditor:  Be able to copy the name of an image,"Sometimes you want to re-use an image (or otherwise need to know its name).  Some file names are too long to display in the tab.  It would be nice if something in the media dialog box exposed the name of the file, so that it could be copied.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409542860,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-2clz3t46qatency62ael,task_description,duplicate
+Link target choice box scroll bar does not work,"If VisualEditor is used to introduce a link (Ctrl-K) and the list of suggested link targets is long enough to require a scroll bar, this scroll bar cannot be used: clicking on it immediately closes the target list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7",1409432400,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_description,resolved
+Link target choice box scroll bar does not work,"Merging into bug 65774.
+
+*** This bug has been marked as a duplicate of bug 65774 ***",1415807855,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_subcomment,NA
+Link target choice box scroll bar does not work,"Just noticed that the (non-functional) scroll bar is only shown if the target list is displayed too far down on the screen. Otherwise, the list just contains 10 items and no scroll bar. To test on mediawiki.org: start a new empty link with Ctrl-K and type R.",1409671182,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_subcomment,NA
+Link target choice box scroll bar does not work,"(Notice that using the mouse wheel works as intended, at least in the categories' case, so assuming it's the same bug we'll need to edit its title.)",1409662547,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_subcomment,NA
+Link target choice box scroll bar does not work,"I don't have examples for the link tool, but can confirm in the categories' one.",1409662111,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ve3s5gkwypzy4otg3e5f,task_subcomment,NA
+VisualEditor: Incorrect highlight while trying to add reference in a slug,"Screenshot
+
+The highlight that appears after inserting a reference in a slug is pretty weird.
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14232}",1409086200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ukh27frjetxrfd5snx42,task_description,resolved
+VisualEditor: Incorrect highlight while trying to add reference in a slug,"That bug is T89192, this particular issue was fixed with staging.",1423749557,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ukh27frjetxrfd5snx42,task_subcomment,NA
+VisualEditor: Incorrect highlight while trying to add reference in a slug,"Breaks even worse at the moment, appears to corrupt the document CE node.",1423749431,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ukh27frjetxrfd5snx42,task_subcomment,NA
+VisualEditor: Incorrect highlight while trying to add reference in a slug,Breaks even worse at the moment.,1423749379,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ukh27frjetxrfd5snx42,task_subcomment,NA
+VisualEditor: Incorrect highlight while trying to add reference in a slug,"It seems that if you insert a reference into a slug, the selection ends up as |<p>, <ref>, </ref>, </p>| rather than <p>, |<ref>, </ref>|, </p>
+
+We should see how this behaves in Ed's ""Stage slugs"" code, though, because that's the future.",1409164870,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ukh27frjetxrfd5snx42,task_subcomment,NA
+VisualEditor:  Hung while trying to save,"This edit was actually saved, but it seemed like it wouldn't be at the time:  https://en.wikipedia.org/w/index.php?title=Integrated_circuit&diff=622517186&oldid=622152913
+
+
+The report was this:
+
+Error saving to server: Empty server response
+
+Hangs when editing ""Integrated circuit"" page - section SSI, MSI and LSI - tried to remove redirect wikilinks to SSI, MSI and LSI (keywords). Chrome 36.0.1985.143 m, Win7 64bit Kozuch (talk) 21:08, 23 August 2014 (UTC)
+
+Hi, I see my edit was saved, but probably was later than what my patience allowed me to wait for :). I was looking at page history before cancelling the edit save, but it was not there, probably shower up later. VE interaction definitely ended up deadly though (hung on the ""saving"" dialog and when I canceled it the above error just was quickly show and then dialog closed by itself.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409007600,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-kgomrdkqhh5iwoae4w4d,task_description,invalid
+VisualEditor:  Hung while trying to save,"This bug could not be reproduced and is now three years old, and was probably a random transient issue, so I'm closing.",1513167493,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-kgomrdkqhh5iwoae4w4d,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"http://bits.beta.wmflabs.org is entirely down with 503.  E.g.:
+
+http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=true&lang=en&modules=ext.visualEditor.viewPageTarget.noscript&only=styles&skin=vector&*
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408737480,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nu7ca5igwfzpwjjvumze,task_description,resolved
+bits.beta.wmflabs.org down with 503,"Still working for me.  If you still get a 503, please re-open, and add the URL and error text you get.",1409777765,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"**physik** wrote:
+
+It worked fine this morning but now I'm getting 503 again.
+It's somehow hard to decide when a Temporarily bug has been fixed.",1408982845,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"The link works for me now, so it seems fixed.  If it is still broken when you test, please re-open.",1408937112,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"**physik** wrote:
+
+The link seems to be still broken (503).",1408792371,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"**gerritadmin** wrote:
+
+Change 155806 merged by BBlack:
+declare hhvm_appservers lvs service ip for labs, too
+
+https://gerrit.wikimedia.org/r/155806",1408739606,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+bits.beta.wmflabs.org down with 503,"**gerritadmin** wrote:
+
+Change 155806 had a related patch set uploaded by Ori.livneh:
+declare hhvm_appservers lvs service ip for labs, too
+
+https://gerrit.wikimedia.org/r/155806",1408739331,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nu7ca5igwfzpwjjvumze,task_subcomment,NA
+VisualEditor: Language selector should be able to use div,"Currently language selector adds <span lang="".."" dir=""...""> which is good for multiple words. However, sometimes longer text such as [few] paragraphs, lists etc should be makred as different language, and in this case it should wrap it with div.
+
+Example: https://he.wikipedia.org/wiki/%D7%A9%D7%9E%D7%A2%D7%95%D7%9F_%D7%90%D7%95%D7%9C%D7%9E%D7%9F?veaction=edit&uselang=en - the second title is ""Books"" and since all the books are in English, the whole list should be wrapped with <div lang=""en"" dir=""ltr"">.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408703280,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-auvoatapd5phg6h74xvs,task_description,resolved
+VisualEditor: Language selector should be able to use div,"Merging with bug 60187; this will require a major amount of work to provide a block-level editing concept more widely, of which this is the most obvious (but not sole) user.
+
+*** This bug has been marked as a duplicate of bug 60187 ***",1408734760,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-auvoatapd5phg6h74xvs,task_subcomment,NA
+"Media: bogus ""no results found"" message when searching media returns results","bogus ""no results"" found in Media interface
+
+Seen if Firefox, less so in Chrome
+
+On any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit 
+
+Click Insert/Media.  Message ""no results found"" appears.
+
+Search for media that returns results.  ""no results found"" message persists. See screen shot. 
+
+In Chrome, ""no results found"" flickers but ultimately disappears when media thumbs are displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14384}",1408656900,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-xez3lpoguhhnw27ay3na,task_description,resolved
+"Media: bogus ""no results found"" message when searching media returns results","(In reply to Chris McMahon from comment #1)
+> Also note that search results for Media in Firefox are different than in
+> Chrome, and Firefox seems to be less correct.
+
+Search results is a Cirrus problem. :-) But yeah.",1408657073,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xez3lpoguhhnw27ay3na,task_subcomment,NA
+"Media: bogus ""no results found"" message when searching media returns results","
+
+*** This bug has been marked as a duplicate of bug 67438 ***",1408657052,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xez3lpoguhhnw27ay3na,task_subcomment,NA
+"Media: bogus ""no results found"" message when searching media returns results","Also note that search results for Media in Firefox are different than in Chrome, and Firefox seems to be less correct.",1408657028,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-xez3lpoguhhnw27ay3na,task_subcomment,NA
+VisualEditor:  Adding text to a category resulted in an extra section heading with span tags,"I have not been able to reproduce this at en.wikipedia.beta, and I didn't want to edit live category pages for testing.
+
+In Firefox, I added a line of text.  VisualEditor added a level 1 section headign after it:
+
+= <span dir=""auto"">Category:Medical and health organizations</span> =
+
+You can see the diff here:  https://en.wikipedia.org/w/index.php?diff=621943590&oldid=615616525
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408562400,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5hcwojrrrykznqwemq5q,task_description,resolved
+VisualEditor:  Adding text to a category resulted in an extra section heading with span tags,"Inclined to mark it as resolved since it seems to be fixed.
+
+Instead of 
+```<h1><a href=""#Category:Medical_and_health_organizations"" class=""mw-headline-anchor"" aria-hidden=""true"" title=""Link to this section"">§</a>
+<span class=""mw-headline"" id=""Category:Medical_and_health_organizations"">
+<span dir=""auto"">Category:Medical and health organizations</span></span></h1>```
+
+when testing  span dir=""auto"" is not added anymore: 
+
+```<h1><a href=""#Category:Medical_and_health_organizations"" class=""mw-headline-anchor"" aria-hidden=""true"" title=""Link to this section"">§</a>
+<span class=""mw-headline"" id=""Category:Medical_and_health_organizations"">
+Category:Medical and health organizations</a></span></h1>```
+<h1>
+<a href=""#Some_page_titile"" class=""mw-headline-anchor"" aria-hidden=""true"" title=""Link to this section"">§</a>
+<span class=""mw-headline"" id=""Some_page_titile"">Some page titile</span></h1>",1425596458,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-5hcwojrrrykznqwemq5q,task_subcomment,NA
+VisualEditor:  Adding text to a category resulted in an extra section heading with span tags,"We fixed this a while ago, I think.",1425594010,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5hcwojrrrykznqwemq5q,task_subcomment,NA
+"VisualEditor: The custom tab does not get enabled after making an image of type ""Frame"" to full size","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Change the type of the image to ""Frame""
+4.Click on ""Apply Changes""
+5.Reopen the media settings dialog for that image
+
+Observe that the ""Make full size"" button is now active
+Click on that.
+The Custom tab does not get enabled, even though the size has just been customized by making it full size.
+
+Environment:Betalabs
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408557240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ppa4557zfmdweuq2ycvp,task_description,resolved
+"VisualEditor: The custom tab does not get enabled after making an image of type ""Frame"" to full size",Correct MediaWiki behaviour.,1423675100,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ppa4557zfmdweuq2ycvp,task_subcomment,NA
+VisualEditor: Suggest templates more proactively in the template adding dialog,"Currently, in the template adding dialog there is just one search box and a lot of empty space.
+
+A user needs to know the name of the template to insert.
+
+A template could be suggested in a more proactive way. One idea can be to simply show the currently available templates by category, starting from the top and let the user drill down (in enwiki the top is https://en.wikipedia.org/wiki/Category:Wikipedia_templates ; the top category should probably be defined in a wg variable). This will require each project to maintain their templates neatly categorized, but this should be done anyway ;)
+
+Another possibility is to let the projects define lists of commonly used templates, or to show a list of the most frequently transcluded ones.
+
+[And see also the trivial bug 69692.]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408550460,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-p5prxsfn6jdj43jb5hhk,task_description,resolved
+VisualEditor: Suggest templates more proactively in the template adding dialog,"I think this is bug 53590.
+
+*** This bug has been marked as a duplicate of bug 53590 ***",1408571387,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p5prxsfn6jdj43jb5hhk,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"The Hebrew Wikipedia, as well as a few others, have a gadget for canned edit summaries:
+https://he.wikipedia.org/wiki/MediaWiki:Gadget-Summarieslist.js
+
+If the forceeditsummary user preference is enabled and the user uses this gadget to insert a summary, the warning about an empty edit summary is issued, even though it shouldn't.
+
+I suspect that the problem is in the VE code.
+As far as I can see, this preference is checked in
+modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.js on line 867
+and the summary values are not what I expect them to be.
+
+(See also Bug 52085.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408466400,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-giznvs23bxpaswgircgp,task_description,declined
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Hmm. That is actually a very good point. Talked with @trevorparscal and you have us both convinced.
+
+Let's file a separate task for this (filed T86868), I'll adapt your patch ({F14710} from T71749#745592) for other InputWidgets.",1421283561,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Sync of the value to the DOM can be done in lazy way on the getValue() (so timer polling isn't really needed...)
+
+What is the correct policy to handle DOM value not equal to the OOUI widgets? Don't know but here are some possible options
+* Trigger change event - this is what I suggested above. This is WYSIWYG - you see X in DOM, X would be the value in the widget.
+* Raise exception - If you fear the above is too dangerous, and this moves the responsibility to the script writter but let him know
+* log.warning(...) - If OOUI lost DOM synchronization too often to raise exceptions. If this is the case then OOUI is probably broken.
+",1421181572,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Documented how/where? I'd be happy to if you come up with a sensible way to do it. :) (This isn't really a supported use-case for OOUI, but it's useful and people are going to do it anyway, so documenting something would make sense.)
+
+Just to be clear, when you modify `.value` from JavaScript (or use jQuery's `.val()`, etc.), there's literally no way for VisualEditor or any other script to pick up the changes in real-time (which we need for things like validation of the inputted values), unless you trigger a 'change' event or something like that (well, short of polling for changes every 100 ms or so, but let's not do that please). That's just how this works, whether we like it or not.",1421179322,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Documented how/where? I'd be happy to if you come up with a sensible way to do it. :) (This isn't really a supported use-case for OOUI, but it's useful and people are going to do it anyway, so documenting something would make sense.)
+
+Just to be clear, when you modify `.value` from JavaScript (or use jQuery's `.val()`, etc.), there's literally no way for VisualEditor or any other script to pick up the changes, unless you trigger a 'change' event or something like that (well, short of polling for changes every 100 ms or so, but let's not do that please). That's just how this works, whether we like it or not.",1421179274,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),Per Bartosz.,1421025800,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"At least it should be documented properly.
+Usually  the UI should be consistent with the DOM.",1421004471,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"I think this should be closed as invalid. Like Trevor said above, the script should call `.trigger( 'change' )` on the <input/> node.
+
+We could change #getValue to actually get the .value of the <input/> every time (like in the proposed patch), rather than relying on the cached one, but any scripts interacting with input fields //must trigger the 'change' event anyway//; there's more machinery that often depends on this – in this particular case, the script that limits the length of edit summary to 255 bytes.
+
+It is a bit weird that OOUI widgets rely on events only to update their internal state, but that's intentional per Trevor's design and I think the design is sensible. It can result in the state of the widget becoming inconsistent with the state of the DOM node when other scripts modify it without triggering events, but on the other hand it ensures that the state of the widget itself is //internally// consistent.",1420984193,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),Isn't this an OOjs UI thing?,1420938082,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"There are actually several reasons for the setTimeout, but the real problem here is that getValue compensating for not noticing the value changed previously causes other issues.
+
+The OO.ui.TextInputWidget has a ""change"" event, which is depended on by other systems. If we just make getValue compensate for not noticing the value changed previously, then systems depending the aggregated change event will behave incorrectly. The best way to handle this is to either trigger the event or come up with a way to access the input. We could, for instance, leave references to widgets in the elements using jQuery.data().",1408476850,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"This is onEdit function  (with setTimeout) that protect against browsers mishaps if I understand correctly.
+
+BTW - don't scar to change getValue, as it is used only in ~35 places in the code ;)",1408476130,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"The problem is that we really should be caching the value; it's done to protect the behavior against a lot of event triggering and browser mishaps that otherwise would make interaction with inputs pretty horrible.
+
+We can't have ooui deal with the jQuery element directly; if you notice, htere's also a SetTimeout() method inside 'setValue' -- that's on purpose to make sure that if the user types quickly we don't emit crazy amount of events. Changing ooui to deal with the jQuery element's value directly will remove a lot of its intended functionality.",1408475612,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"@Trevor Parscal, I already fixed it with triggering input event. However it should be fixed in oojs-ui itself for later cases.
+The browser should not emit event in this case (see RFC: http://www.w3.org/TR/html401/interact/scripts.html#adef-onchange), and even if the spec was the other way - oojs-ui can't blame browsers...",1408475334,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"The problem is actually to do with the fact that the browser isn't emitting events when it should. OOjs UI is listening for the change event.
+
+Just use:
+
+$input.val( newValue ).trigger( 'change' );",1408474763,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Created attachment 16237
+Fix for oojs-ui
+
+Attaching a proposed patch for oojs-ui.
+
+**Attached**: {F14710}",1408473504,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Fixed by triggering manually input event.
+
+However oojs-ui should use the widget value to get must up to date value (e.g protype.getValue( return this.widget.val(); ), and not to be based on some cached variable.
+If it does something smart with the value it can be check that if this.value !=this.widget.val()  then it should trigger the function for updating this.value, before actually return the widget value.",1408472348,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"Got it.
+
+The issue was a mixup between dealing directly with the textarea object through jQuery (which updates .val()) and dealing with VE's OOUI elements (which update through .setValue() )
+
+I've created a fix to the gadget, but I don't have the permissions to edit it. I've asked Eran to take a look and implement the fix.",1408470567,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value),"This gets a bit weirder for me. It seems that with the gadget that summaries aren't saved at all, even if I type something manually in the textbox, and this behavior is inconsistent:
+
+If I add automatic summaries from the buttons and save, the summary isn't saved.
+If I add automatic summaries from the buttons and then add a text, they are saved as a summary. 
+If I add a summary by hand, it isn't saved.
+
+I'm not sure what would cause this to happen; the gadget fills in automatic text by adding into the textbox.val() which should make this work.",1408467289,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-giznvs23bxpaswgircgp,task_subcomment,NA
+VisualEditor: Provide content-based descriptions when focusing references or templates,"In particular we've had a community request to display a citation summary when focusing citation nodes.
+
+We could list template values in order until we run out of room, but this may not lead to desirable results, for example the first parameter in {{Cite web}} is URL.
+
+A more complex solution would be to come up with a format for defining how to generate the summary of a template and store it in template data, either as a value on the column (summary order):
+
+Field     Desc  Summary order
+url       ...   null
+publisher ...   2
+title     ...   1
+date      ...   3
+month     ...   null
+
+A simplified version of this would just flag one field as being used in the summary.
+
+etc.
+
+Or as a string concatenation message somewhere:
+
+""{{{title}}}, {{{publisher}}} - {{{date}}}""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408463340,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-iboqexwepmrgmkfwmdpm,task_description,resolved
+VisualEditor: Provide content-based descriptions when focusing references or templates,Clearly I was protecting against typos in the bug number :),1408464073,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-iboqexwepmrgmkfwmdpm,task_subcomment,NA
+VisualEditor: Provide content-based descriptions when focusing references or templates,"I'm going crazy...
+
+*** This bug has been marked as a duplicate of bug 69474 ***",1408464025,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-iboqexwepmrgmkfwmdpm,task_subcomment,NA
+VisualEditor: Provide content-based descriptions when focusing references or templates,"Is this the same thing as bug 69474? (You filed that one too, and the bug numbers are confusingly similar. :D)",1408463781,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-iboqexwepmrgmkfwmdpm,task_subcomment,NA
+"VisualEditor:  After you create a link and close the link inspector, please de-select the newly linked text","Steps to reproduce:
+
+1.  Type some text:  ""Foo bar baz bat""
+
+2.  Select the last word, because you want to create a wikilink before you finish typing the sentence.
+
+3.  Type Command-K to create a link.  
+
+4.  Make a link.  Click ""Done"".
+
+5.  Finish typing the sentence.
+
+6.  Oops, where did [[bat]] go?
+
+
+Results:
+
+When you exit the link inspector, the linked text remains highlighted, and typing results in it being overwritten by your next character.  
+
+Expectation:  after I've made a link, de-select the link and put the cursor at the end of the word, so I can keep writing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408389720,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-kmwl4sqnbhfoukhb367a,task_description,declined
+"VisualEditor:  After you create a link and close the link inspector, please de-select the newly linked text",We've intentionally chosen this behaviour after a huge amount of user and product research.,1423675223,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kmwl4sqnbhfoukhb367a,task_subcomment,NA
+VisualEditor: Dropdown menu shows scrollbars,"screenshot of the problem
+
+Confirmed this on Safari 7, mac, Vector and Firefox 31, Windows 7, Monobook
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54705
+
+**Attached**: {F14614}",1408380300,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-5iagtk7ef7sicdms3ksc,task_description,resolved
+VisualEditor: Dropdown menu shows scrollbars,"Merging into bug 57366 (FIXED).
+
+*** This bug has been marked as a duplicate of bug 57366 ***",1409892989,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5iagtk7ef7sicdms3ksc,task_subcomment,NA
+VisualEditor: Dropdown menu shows scrollbars,I guess this became a problem when the cancel button was removed.,1409836500,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-5iagtk7ef7sicdms3ksc,task_subcomment,NA
+VisualEditor: Dropdown menu shows scrollbars,"The clipping is correct, but we aren't repositioning for the edge of the screen, like we do with link inspectors (context popups).",1408648098,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5iagtk7ef7sicdms3ksc,task_subcomment,NA
+VisualEditor: Dropdown menu shows scrollbars,Also Firefox 30 on a Mac.  I suspect that it's everywhere.  This problem has been present for at least a few weeks.,1408391451,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-5iagtk7ef7sicdms3ksc,task_subcomment,NA
+VisualEditor: allow parameter per line in inserted templates,"It is customary for big templates with a lot of parameters, such as infoboxes, to have each parameter written on a separate line in the wiki source code.
+
+If I am not mistaken, VE inserts all templates in one long line.
+
+As long as source code editing is common, VE should insert templates according to the above community practice.
+
+How to know whether to insert one line or multiple lines? Either do it with multiple lines if there are more than x parameters, say 4, or have a parameter in template data that suggests multiline insertion.
+
+**See Also**:
+* {T52584}",1408335060,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-jr2a2h6e2iclnvx4wa2e,task_description,duplicate
+VisualEditor: allow parameter per line in inserted templates,"It seems that VE users still get [[https://fi.wikipedia.org/wiki/Keskustelu_k%C3%A4ytt%C3%A4j%C3%A4st%C3%A4:Kuriuss#Infolaatikot | yelled at]] for this (or perhaps that was rather a manifestation of T52584, because in the offending edits - [[https://fi.wikipedia.org/w/index.php?title=Resedakasvit&diff=prev&oldid=14486819 |example]] - the parameters were already present).",1427240949,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-jr2a2h6e2iclnvx4wa2e,task_subcomment,NA
+VisualEditor:  Pasting a link label causes the link to split,"What I started with was a link to a disambiguation page:
+
+  Foo bar [[CML]] baz bat.
+
+
+What I wanted was a link to a real article, so I repointed the link:
+
+  Foo bar [[chronic myelogenous leukemia|CML]] baz bat.
+
+
+Hmm, that initialism doesn't appear to be expanded anywhere on the page.  Okay, what we need is:
+
+  Foo bar [[chronic myelogenous leukemia]] baz bat.
+
+
+So I copied the long name out of the link tool's field, and pasted it into the middle.  It produced:
+
+  Foo bar [[chronic myelogenous leukemia|CM]]chronic myelogenous leukemia[[chronic myelogenous leukemia|L]] baz bat.
+
+None of this would have been so difficult if we could edit labels in the link tool, in a separate box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408236960,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-2o5afywhjm53xfqkmeux,task_description,resolved
+VisualEditor:  Pasting a link label causes the link to split,"This is because of bug 48720. Grumble.
+
+*** This bug has been marked as a duplicate of bug 48720 ***",1408272633,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2o5afywhjm53xfqkmeux,task_subcomment,NA
+firsteditve no longer points to VisualEditor,"The step in firsteditve that appears when you start editing the document in VisualEditor no longer points to the ""Save page"" button due to an incompatible change to the VE HTML DOM.
+
+It still shows up, but it's no longer attached.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1408162620,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-o3mocvfmdnarvi5x2cyl,task_description,resolved
+firsteditve no longer points to VisualEditor,"Change 155234 abandoned by Phuedx:
+Point to the ""Save page"" button
+
+Reason:
+Abandoned in favour of I81fdc4f2fa41c86a6481cf478c154b5d6c99d41d.
+
+https://gerrit.wikimedia.org/r/155234",1408553781,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-o3mocvfmdnarvi5x2cyl,task_subcomment,NA
+firsteditve no longer points to VisualEditor,"**swalling** wrote:
+
+Fixed in https://gerrit.wikimedia.org/r/#/c/155280/",1408553774,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-o3mocvfmdnarvi5x2cyl,task_subcomment,NA
+firsteditve no longer points to VisualEditor,"Change 155234 had a related patch set uploaded by Phuedx:
+Point to the ""Save page"" button
+
+https://gerrit.wikimedia.org/r/155234",1408530620,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-o3mocvfmdnarvi5x2cyl,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,"When I open the VisualEditor on mobile in stable on enwiki using Chrome on desktop (OSX), I get the following JS error:
+Discontiguous selection is not supported. 
+
+I loaded it with ?debug=true here's what I see in the console:
+Discontiguous selection is not supported. rangy-core-1.3.js:2842
+(anonymous function) rangy-core-1.3.js:2842
+(anonymous function) rangy-core-1.3.js:2852
+(anonymous function) rangy-core-1.3.js:327
+init rangy-core-1.3.js:249
+loadHandler rangy-core-1.3.js:365
+
+Incidentally, I'm also seeing this in the console with ?debug=true (however I do not see this without ?debug=true):
+Uncaught Error: Module not found: loggingSchemas/MobileWebClickTracking load.php?debug=true&lang=en&modules=mobile.head&only=scripts&skin=minerva&version=20140815T031511Z&*:53
+mw.mobileFrontend.require load.php?debug=true&lang=en&modules=mobile.head&only=scripts&skin=minerva&version=20140815T031511Z&*:53
+(anonymous function) load.php?debug=true&lang=en&modules=mobile.languages&only=scripts&skin=minerva&version=20140815T101…:67
+(anonymous function)
+
+Not sure if the click tracking thing is related, a separate bug, or just a result of something going wonky with load order as a result of ?debug=true - if it seems like a separate issue, I'm happy to file another bug but figured it'd be worth mentioning here for now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408123380,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-a3yfrijahd6twdq67xo2,task_description,resolved
+JS error on loading mobile VE: Discontiguous selection is not supported.,"Duplicate of bug 68493 which is now fixed.
+
+*** This bug has been marked as a duplicate of bug 68493 ***",1412803537,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,Not sure if this is still a relevant bug. Guessing VE folks will know.,1412795473,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,"**jgonera** wrote:
+
+This (""Discontiguous selection is not supported"") is not a mobile bug. It happens on desktop too.",1408664773,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/nqeGVbpJ",1408123813,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+JS error on loading mobile VE: Discontiguous selection is not supported.,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/7MTSGUCb",1408123513,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-a3yfrijahd6twdq67xo2,task_subcomment,NA
+VisualEditor:  Offer to pre-fill the DEFAULTSORT field,"Usually, DEFAULTSORT contents need only a little re-arranging or capitalization changes.  If the name is long or unfamiliar, it may be difficult to type it to make these relatively minor changes.  It would be nice to pre-fill the box with the page title.
+
+But if VisualEditor simply fills in the box whenever you open the Page settings menu, then we'll get a lot of errors (because people won't notice that it needs to be updated).
+
+Possible solution:  Add a button next to the DEFAULTSORT item to insert the current page title as text that the editor can then change as needed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408048080,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-v3n4j4kb2ell4h52eujf,task_description,resolved
+VisualEditor:  Offer to pre-fill the DEFAULTSORT field,"This is the same as bug 50002 (and needs a huge amount of design thought).
+
+*** This bug has been marked as a duplicate of bug 50002 ***",1408096620,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-v3n4j4kb2ell4h52eujf,task_subcomment,NA
+VisualEditor Mobile: removing a link takes me to the top of the page,"Steps to repro:
+
+1. In production/stable, enter VE edit mode and scroll down to a section that's below the fold.
+2. Tap on a wikilink
+3. Use the ""remove"" button to remove the link & tap done.
+
+Expected: I am taken back to the section I was on.
+
+Actual: I'm taken back to the top of the page.
+
+Observed on iPad 2 & mobile site on desktop Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408047960,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-p5kjnipb4qiha2arheu4,task_description,resolved
+VisualEditor Mobile: removing a link takes me to the top of the page,"**jgonera** wrote:
+
+Can't reproduce anymore on latest master. Other bugfixes might have fixed this too. Reopen if it's still happening.",1409100209,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-p5kjnipb4qiha2arheu4,task_subcomment,NA
+VisualEditor Mobile: removing a link takes me to the top of the page,"**jgonera** wrote:
+
+I suspect this might be related to bug 66697.",1408058394,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-p5kjnipb4qiha2arheu4,task_subcomment,NA
+VisualEditor Mobile: removing a link takes me to the top of the page,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/JUXz2uL6",1408048213,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-p5kjnipb4qiha2arheu4,task_subcomment,NA
+Cannot copy text when dm.surface.enabled === false,"**Author:** `ryan.wold`
+
+**Description:**
+When disabling an Editor's .target.surface (by calling .disable()), the text is no longer editable, which is great.  However, the text in the disabled Editor cannot be copied and pasted.  It does not appear to make it to the clipboard. 
+
+Desired behavior is that the text can be be copied even when the editor is disabled.  Or perhaps there could be a setting/option around that.
+
+
+
+We traced this to ve.dm.Surface.prototype.changeInternal, where it returns immediately if the surface is disabled.
+
+if ( !this.enabled ) {
+  return;
+}
+
+I found this here: https://doc.wikimedia.org/VisualEditor/master/source/ve.dm.Surface.html#ve-dm-Surface-method-changeInternal
+
+
+I'm using OSX Mavericks and Google Chrome Version 36.0.1985.125.
+
+Thanks!
+
+- Ryan Wold
+  ryan.wold@neo.com
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1407976380,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-brolhdih457kpowhgvqe,task_description,resolved
+Cannot copy text when dm.surface.enabled === false,"**ryan.wold** wrote:
+
+
+
+%%%*** This bug has been marked as a duplicate of bug 69515 ***%%%",1407976455,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-brolhdih457kpowhgvqe,task_subcomment,NA
+VisualEditor:  Too much tabbing in the Template dialog,"From John Broughton:
+
+""This is what tabbing through Cite templates (in the mini-editors) looks like: type, tab, tab, tab, type, tab, tab, tab, type, ... You have to tab three times to get from one field to the next. That's because tabbing always includes both the “Field description” and “Remove field” icons. There isn't any reason to include these icons in tabbing; tabbing should bypass these icons.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407974220,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_description,resolved
+VisualEditor:  Too much tabbing in the Template dialog,"
+
+*** This bug has been marked as a duplicate of bug 68768 ***",1414084060,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_subcomment,NA
+VisualEditor:  Too much tabbing in the Template dialog,"(In reply to James Forrester from comment #2)
+> Using a <button> rather than a <div> in OOUI for buttoned elements takes us
+> into really horrible issues more widely, though…
+
+Can you elaborate, because I don't see why that would be ? We have gotten them pretty down even in mediawiki.ui",1408696342,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_subcomment,NA
+VisualEditor:  Too much tabbing in the Template dialog,"(In reply to WhatamIdoing from comment #0)
+> From John Broughton:
+
+[…]
+
+> There isn't any reason to include these icons in tabbing
+
+The reason is ""accessibility"". That's a pretty strong sine qua non for how we build things.
+
+(In reply to Derk-Jan Hartman from comment #1)
+> Using an actual button might fix 'excessive' tabbing here, since browsers
+> sometimes have different default tab behavior for buttons vs. fields, a
+> behavior overridden if you need to force button behaviors on a div/a.
+
+Using a <button> rather than a <div> in OOUI for buttoned elements takes us into really horrible issues more widely, though…",1408642685,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_subcomment,NA
+VisualEditor:  Too much tabbing in the Template dialog,"Also shift tab behaves differently (this is due to presence of icon only in focus state. WAI-ARIA has some further thoughts on how bot build fields like this, but I think it might be a bit too much effort right now.)
+
+Using an actual button might fix 'excessive' tabbing here, since browsers sometimes have different default tab behavior for buttons vs. fields, a behavior overridden if you need to force button behaviors on a div/a.",1408628873,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-nsm5ksrnyvwuqbyf6qjb,task_subcomment,NA
+VisualEditor:  Links added to captions for new images not quite working,"What happens when you try to make a link.  (Notice that the box is too small; that will be a separate bug in a moment.)
+
+I can only make this happen in Safari, not Firefox, but I believe that the user reporting this was using Firefox.
+
+Steps to reproduce:
+
+1.  Open VisualEditor and Insert > Media.
+
+2.  Pick and image and add a caption.
+
+3.  Select a word and press Command-K to make an internal link. 
+
+4.  Notice that you get no search results to help you find the correct page for your link.
+
+5.  Click inside the box.  Now you have search results.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14163}",1407973740,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wvmydl4bbkdtqm7osvyj,task_description,declined
+VisualEditor:  Links added to captions for new images not quite working,"I think it is the firefox which is different from Chrome and Safari, not sure which one is correct though!And not just for a link inside image, for a link in CE too,in Chrome and Safari, you will not get any list of link target suggestions unless you click inside the box.",1410220995,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-wvmydl4bbkdtqm7osvyj,task_subcomment,NA
+VisualEditor:  Links added to captions for new images not quite working,"Experience in Safari:
+
+1.  Open VisualEditor and Insert > Media.
+
+2.  Pick and image and add a caption.
+
+3.  Select a word and press Command-K to make an internal link. 
+
+4.  Notice that you get no search results to help you find the correct page for your link.
+
+5.  Click inside the box.  Now you have search results.
+
+
+Experience in Firefox:
+
+1.  Open VisualEditor and Insert > Media.
+
+2.  Pick and image and add a caption.
+
+3.  Select a word and press Command-K to make an internal link. 
+
+4.  Notice that you are immediately given a long list of search results, even if you don't want them.
+
+
+Since they don't behave the same, then one of these two browsers isn't working as designed.",1410217842,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wvmydl4bbkdtqm7osvyj,task_subcomment,NA
+VisualEditor:  Links added to captions for new images not quite working,I don't see a bug here? This seems to be working as expected. Have I missed something?,1410202699,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wvmydl4bbkdtqm7osvyj,task_subcomment,NA
+VisualEditor:  Information fields in template dialogs are sometimes very large,"See https://en.wikipedia.org/wiki/File:Cite_dialog_with_large_boxes_for_fields.png
+
+This is intermittent and may be relate to zooming in/large text size.  The fields go back to normal size when you click inside them.  Seen in both Firefox and Safari on Macs.
+
+Today, I'm getting pretty consistent results by opening https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&veaction=edit in Safari and selecting the infobox.  Opening it (double-clicking) the first time works as expected.  Cancelling it (escape key) and opening it again produces larger than necessary fields.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407972240,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uz4ebiomuh52dqhalxqd,task_description,resolved
+VisualEditor:  Information fields in template dialogs are sometimes very large,"Tried in Safari on Mac with the link provided - cannot reproduce. Also, checked if transclusion boxes will scale up/down with the selected zoom rate - all look fine. ",1419990286,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-uz4ebiomuh52dqhalxqd,task_subcomment,NA
+VisualEditor:  The Categories dialog should indicate which cats are red links,"Of a non-existent category has been added on a page, there is no indication in the Categories dialog that it is a red link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407971580,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rlvjrs3munfatsc5rqfz,task_description,resolved
+VisualEditor:  The Categories dialog should indicate which cats are red links,"
+
+*** This bug has been marked as a duplicate of bug 65517 ***",1414805875,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rlvjrs3munfatsc5rqfz,task_subcomment,NA
+VisualEditor:  Categories should be displayed at the end of the page,"VisualEditor should display categories in the page's footer, just like they will display when the page is saved.  Clicking on the footer could open the Categories editing tool.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407971340,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-mkaptpov6nx3eewv7jvc,task_description,duplicate
+VisualEditor:  Categories should be displayed at the end of the page,"
+
+*** This bug has been marked as a duplicate of bug 50239 ***",1414806319,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-mkaptpov6nx3eewv7jvc,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"Article URL: https://ru.wikipedia.org/wiki/%D0%A2%D0%B0%D0%B1%D0%BB%D0%B8%D1%86,_%D0%91%D0%BE%D0%B3%D1%83%D1%81%D0%BB%D0%B0%D0%B2
+
+The infobox is shown correctly while reading the article, but broken when editing in VisualEditor. HTML code is shown above the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407844800,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-btruvlfdq3qyqvht2rk7,task_description,resolved
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"> Looks like a bug in broken attribute heuristics.
+
+On second thought, I think what we're doing is fine. This is just broken wikitext.
+
+The php parser gets away with it by refusing all ""greater than"" chars in attributes. ie.
+
+  <div class=""class>ey"">stuff</div>
+
+is rendered as,
+
+  <div>ey""&gt;stuff</div>
+
+which seems worse.",1408488269,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"The template was returning something like,
+
+  <table><tr><th style=""text>great</th><td>""test</td></tr></table>
+
+which parsoid rendered as,
+
+  &lt;th style=""text>great
+  <table>
+  <tbody>
+  <tr>
+  <td>""test</td></tr></tbody></table>
+
+Looks like a bug in broken attribute heuristics.",1408482811,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"Fixed the template in,
+https://ru.wikipedia.org/w/index.php?title=%D0%9C%D0%BE%D0%B4%D1%83%D0%BB%D1%8C%3AUniversal_infocard&diff=64929809&oldid=64897667
+
+But we should be more robust against unclosed attributes.",1408478247,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,"(In reply to James Forrester from comment #1)
+> Looks like [[ru:Template:Универсальная карточка]] is getting a bunch of
+> content fostered out somewhere?
+
+I didn't go too deeply into the code, but it is build using this Lua module:
+https://ru.wikipedia.org/wiki/Module:Universal_infocard
+
+It pulls data from Wikidata, and seems to build tables using HTML rather than wiki table syntax. Maybe that is the cause.",1407846830,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic,Looks like [[ru:Template:Универсальная карточка]] is getting a bunch of content fostered out somewhere?,1407845929,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-btruvlfdq3qyqvht2rk7,task_subcomment,NA
+Chrome not populating text fields correctly,"Reported by S Page at QA mailing list[1]. Reported to Sauce Labs support[2].
+
+1: http://lists.wikimedia.org/pipermail/qa/2014-August/001843.html
+2: http://lists.wikimedia.org/pipermail/qa/2014-August/001846.html
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1407767220,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-yata753fflzx3ifjicto,task_description,resolved
+Chrome not populating text fields correctly,"**gerritadmin** wrote:
+
+Change 153408 merged by jenkins-bot:
+Chrome 28 is the last version that works properly on Sauce Labs
+
+https://gerrit.wikimedia.org/r/153408",1407917621,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yata753fflzx3ifjicto,task_subcomment,NA
+Chrome not populating text fields correctly,"I have started builds for all Chrome jobs. The jobs should be more green now.
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-test2.wikipedia.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Math-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-MultimediaViewer-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-PageTriage-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-UploadWizard-commons.wikimedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-test2.wikipedia.org-linux-chrome-sauce/",1407769872,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-yata753fflzx3ifjicto,task_subcomment,NA
+Chrome not populating text fields correctly,"**gerritadmin** wrote:
+
+Change 153408 had a related patch set uploaded by Zfilipin:
+Chrome 28 is the last version that works properly on Sauce Labs
+
+https://gerrit.wikimedia.org/r/153408",1407768857,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yata753fflzx3ifjicto,task_subcomment,NA
+Chrome not populating text fields correctly,"Sauce Labs support answer:
+
+Allison Wilbur (Sauce Labs Help Desk)
+Aug 09 02:03 AM
+
+Hi there,
+
+I'm sorry this issue suddenly popped up for you! Sauce Labs just recently updated the default versions of Chrome, ChromeDriver, and Selenium that we serve up when no version is explicitly requested in the Desired Capabilities we receive.
+
+Previously, the default values were:
+
+Selenium: 2.30.0
+Chrome: 27/28 (depending on environment - 28 for Linux)
+ChromeDriver: 26.0.1383.0
+
+The new default values are:
+Selenium: 2.40.0
+Chrome: 35
+ChromeDriver: 2.10
+
+If you set your Desired Capabilities to the previous values, I suspect your tests will behave as they used to. For example:
+
+desired_capabilities['selenium-version'] = '2.30.0'
+desired_capabilities['browserName'] = 'chrome'
+desired_capabilities['version'] = '28'
+desired_capabilities['chromedriver-version'] = '26.0.1383.0'
+
+The extremely odd behavior you saw with the recent versions update is something I'm currently investigating, and I've filed an internal ticket to get this problem fixed. It seems to be related to the later versions of Chrome/ChromeDriver for some reason, and specific to Linux. I found this issue with send_keys on the ChromeDriver forums: https://code.google.com/p/chromedriver/issues/detail?id=467 It's not quite the same issue, but it looks like there's some strange behavior with text input in Linux.
+
+I hope the previous values perform well for you as a workaround while we investigate the issues with the more recent versions of Chrome. I've linked this ticket to the issue, so I'll be sure to let you know when the fix is out so that you can test on more recent versions. If you want to try the later versions, I've had some success looping through my input and sending one key at a time, so perhaps something like that would help out.
+
+Sorry again for the trouble here. Let me know if you have any additional questions and I'll be happy to help. Hope you have a great weekend!
+
+Best,
+Allison",1407767724,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-yata753fflzx3ifjicto,task_subcomment,NA
+VisualEditor: <ref>s in a section-edit get re-numbered,"https://en.wikipedia.org/wiki/Sonic_Adventure#Development
+
+When I go here and click ""edit beta"", the <ref>s are re-numbered when ?veaction=edit loads.
+
+For example, at the implicit ?action=view:
+
+---
+The character of Sonic was redesigned for the game by Sonic Team artist Yuji Uekawa, with longer legs and spines that Iizuka subsequently noted were more suitable for 3D than Sonic's original and more compact design, which was meant to be seen from the side.[46][47] 
+---
+
+At ?veaction=edit:
+
+---
+The character of Sonic was redesigned for the game by Sonic Team artist Yuji Uekawa, with longer legs and spines that Iizuka subsequently noted were more suitable for 3D than Sonic's original and more compact design, which was meant to be seen from the side.[42][43]
+---
+
+This is super-confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407700140,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6myt7vl23u4acnyzoq5w,task_description,resolved
+VisualEditor: <ref>s in a section-edit get re-numbered,"This sounds like the same thing as what's described as bug 50474.
+
+*** This bug has been marked as a duplicate of bug 50474 ***",1407719768,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6myt7vl23u4acnyzoq5w,task_subcomment,NA
+VisualEditor:  Dialog for inserting new templates doesn't play well with search results,"Goal:  Insert a new template.
+
+Steps to reproduce:
+
+1.  Insert > Template
+
+2.  Start typing the template's name:  Citation nee…
+
+3.  Think, ""Ah, it's found it!  It's highlighted and has a checkmark next to it!  Great, I can stop typing that long name and just hit return to add the template that I want.
+
+4.  Press return.
+
+5.  Think, ""Um, [[Template:Citation nee]] is a redlink.  Why did it add that?  Why didn't it add the highlighted-and-checkmarked [[Template:Citation needed]]?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407651480,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gyjrpnwlzlseuj5ay2wq,task_description,resolved
+VisualEditor:  Dialog for inserting new templates doesn't play well with search results,"I am inclined to close as Resolved: the feedback to a user for inserting templates has improved
+
+- there is no check mark to a highlighted suggested selection anymore
+- clicking Return with 'Citation nee'  selects the first highlighted template from the suggestions list
+ - the next dialog box displays the template's  title and info/description to inform a user what kind of a template is about to be inserted
+-  That dialog box requires a user to click 'Insert' button explicitly - not just pressing Return keyboard buttonn.
+
+
+",1424904354,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-gyjrpnwlzlseuj5ay2wq,task_subcomment,NA
+Add parameterless GENDER as insertable,"When {{GENDER:|...}} is part of a source string, GENDER: is not available as insertable.
+
+Example string: https://translatewiki.net/wiki/MediaWiki:Visualeditor-editconflict/en
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1407519060,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-6zqiurw6oqkkhhopo7w5,task_description,resolved
+Add parameterless GENDER as insertable,"Change 153571 merged by Jsahleen:
+Add parameterless GENDER as insertable
+
+https://gerrit.wikimedia.org/r/153571",1410260970,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6zqiurw6oqkkhhopo7w5,task_subcomment,NA
+Add parameterless GENDER as insertable,"Change 153571 had a related patch set uploaded by Nikerabbit:
+Add parameterless GENDER as insertable
+
+https://gerrit.wikimedia.org/r/153571",1407837498,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6zqiurw6oqkkhhopo7w5,task_subcomment,NA
+VisualEditor: Distorted UI of Language Inspector/Special Character appears while trying to open them when the link inspector is already open in CE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text
+3.Click on Link inspector
+4.While the link inspector is open, open Language inspector or Special Character inserter
+
+Observed Result:
+The UI of both the inspector appears a bit distorted having a whitespace at the bottom
+
+See the screenshot attached
+
+Environment:Production,test2,Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14605}",1407356580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tjl4vryiojzktgcw53ge,task_description,resolved
+VisualEditor: Distorted UI of Language Inspector/Special Character appears while trying to open them when the link inspector is already open in CE,Checked betalabs  - all is displayed correctly.,1425329715,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-tjl4vryiojzktgcw53ge,task_subcomment,NA
+VisualEditor: Distorted UI of Language Inspector/Special Character appears while trying to open them when the link inspector is already open in CE,"Re-checked it in Ptoduction and test2 -  the Language, Link inspectors and Special character inserter looks normal. 
+
+I will check betalabs when the env will be back to normal. 
+",1425002064,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-tjl4vryiojzktgcw53ge,task_subcomment,NA
+"VisualEditor:Edit beta tab not shown, when not logged in.","Environment- beta, production
+
+1> Try to open your User page without logging in.
+2> Shows the ""Welcome to VE"" popup, click on ""continue"" to proceed.
+3> opens the page in VE mode , but the VE Edit tab is not seen on top.
+
+In test2 follow the above steps and the page would open in the Read mode and all the tabs(Read, Edit and Edit source can be seen).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1407343860,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-pamojafdtnhybmzjhew6,task_description,invalid
+"VisualEditor:Edit beta tab not shown, when not logged in.","Yes, this is intentionally how it's configured on some wikis.",1407364526,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pamojafdtnhybmzjhew6,task_subcomment,NA
+"VisualEditor: Enable toggling between tabs and dropdown menus in the Vector skin ,  does not make the Read, Edit tabs squeeze into one “View” tab for FF and Safari.","screenshot
+
+1> Preferences -> Gadgets
+2> Enable this under Appearance -> Enable toggling between tabs and dropdown menus in the Vector skin. 
+3> Save 
+4> go back to User page. Notice now the Tabs Read, Edit and Edit Source all have been moved into a single drop down labeled “View”. However, enabling the same appearance in FF and Safari does not show the “View” dropdown.
+Also, the “View” is out of position as compared to “More” and does not show the drop down arrow.See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14485}",1407271560,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-mkqig7y2abufhee3e6a4,task_description,declined
+"VisualEditor: Enable toggling between tabs and dropdown menus in the Vector skin ,  does not make the Read, Edit tabs squeeze into one “View” tab for FF and Safari.","We don't track issues with gadgets in Phabricator, sorry.",1417577754,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mkqig7y2abufhee3e6a4,task_subcomment,NA
+"VisualEditor: Enable toggling between tabs and dropdown menus in the Vector skin ,  does not make the Read, Edit tabs squeeze into one “View” tab for FF and Safari.",Environment-test2,1407272360,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-mkqig7y2abufhee3e6a4,task_subcomment,NA
+VisualEditor: Citation number 0,"* Add a basic citation
+* Add another non-basic(?) citation
+* Go back and set group of basic citation to something, apply changes
+* Undo changes twice
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407187800,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vqi7xz3ct5esenmosj2r,task_description,resolved
+VisualEditor: Citation number 0,"
+
+*** This bug has been marked as a duplicate of bug 69119 ***",1414806524,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vqi7xz3ct5esenmosj2r,task_subcomment,NA
+VisualEditor: Citation number 0,"Also if you undo again, you get this:
+Uncaught TypeError: Cannot read property 'length' of undefined
+Then this:
+Uncaught TypeError: Cannot read property 'canHaveChildren' of null
+Then this:
+Uncaught Error: Unbalanced input passed to document",1407188306,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vqi7xz3ct5esenmosj2r,task_subcomment,NA
+VisualEditor:  Placing some templates in bulleted lists causes complex transclusions,"Steps to Reproduce:
+1. Open https://ru.wikipedia.org/w/index.php?oldid=63644335&veaction=edit and look at the second section.
+
+The wikitext is:
+
+=== Б ===
+
+* [[Борисов, Бойко Методиев]] (род. 1959) — болгарский политик.
+* {{NL|Борисов, Борис}}
+
+{{NL}} is a template that transcludes the rest of this short list.
+
+2. The first bullet point is plain wikitext.  Click on the first item and try to change some of the text (e.g., to change the birth date from 1959 to 1960).
+
+
+Actual Results:  
+The first bullet point can only be edited as the ""content"" part of a complex transclusion.  
+
+Expected Results:  
+That plain-text list items can be edited as plain old list items.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407177240,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-x4x3miva4uelxlwoeyn2,task_description,declined
+VisualEditor:  Placing some templates in bulleted lists causes complex transclusions,"This is not a problem with lists per se. This is a result of how Parsoid represents templates in the DOM, and where some transclusions doesn't generate well-balanced DOM structures.
+
+Parsoid marks complete DOM subtrees as template-generated/affected. So, in scenarios where output of a template spans multiple dom subtrees, all those affected subtrees are wrapped as one piece.
+
+You can reproduce this behavior with a simple example like: ""a {{echo|b\n\nc}} d"". In this example, b and c belong to different paragraphs which also contain content from outside the transclusion. So, all of it is pulled into the template wrapping.
+
+This is the same behavior where multiple transclusions are used to generate football tables, succession tables, etc.",1408574718,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-x4x3miva4uelxlwoeyn2,task_subcomment,NA
+"VisualEditor: Media Settings dialog does not close, when inserting a media with a link or language  ""Uncaught TypeError: undefined is not a function""","screenshot
+
+Environment-test2
+
+Steps- 
+
+1> Insert-> Media.
+2> In media Settings dialog insert a link or type in some text in a language.
+3> Click on ""Insert media"". notice the file gets inserted in the background, and yet the media settings dialog never closes.
+
+See screenshot.
+
+Also See bug 65568.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows XP
+
+**Attached**: {F14256}",1406931420,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-otkdojq77s5a7dnwv5td,task_description,declined
+"VisualEditor: Media Settings dialog does not close, when inserting a media with a link or language  ""Uncaught TypeError: undefined is not a function""",I cannot reproduce it anymore in test2 or beta.Please close this issue.,1407162115,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-otkdojq77s5a7dnwv5td,task_subcomment,NA
+VisualEditor:  Can't re-use the same reference twice,"Intention:
+Re-use an existing reference
+
+Steps to Reproduce:
+1.  Open a page containing a citation.
+
+2.  Cite > Re-use.  Click on a reference.
+
+3.  Go to another sentence.
+
+4.  Cite > Re-use.  Click on the same reference (it's already highlighted).
+
+
+Actual Results:  
+The first time, it adds the ref.  The second time, it does nothing.  You have to insert a different (wrong) ref, delete that, and then add the one that you wanted (now that it's stuck on the ""wrong"" one).  Canceling and trying again doesn't help.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406928360,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rl2y2ishipdsqzcikuvr,task_description,resolved
+VisualEditor:  Can't re-use the same reference twice,"
+
+*** This bug has been marked as a duplicate of bug 68582 ***",1406929690,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-rl2y2ishipdsqzcikuvr,task_subcomment,NA
+VisualEditor:Insert -> Comment not working in Betalabs,"steps-
+1> open a page in VE.
+2> Insert -> Comment. Add/Edit Comment dialog does not pop.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP",1406912520,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-dko2nwcat2a5enwq6736,task_description,resolved
+VisualEditor:Insert -> Comment not working in Betalabs,"This is the same bug as https://bugzilla.wikimedia.org/show_bug.cgi?id=68960
+Just in Chrome the JS error is different , so initially I thought its a different one.",1406921165,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dko2nwcat2a5enwq6736,task_subcomment,NA
+VisualEditor:Insert -> Comment not working in Betalabs,"
+
+*** This bug has been marked as a duplicate of bug 68960 ***",1406921057,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dko2nwcat2a5enwq6736,task_subcomment,NA
+VisualEditor:Insert -> Comment not working in Betalabs,"yes, the error appearing in the console is:
+Uncaught TypeError: undefined is not a function",1406916416,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dko2nwcat2a5enwq6736,task_subcomment,NA
+VisualEditor:Insert -> Comment not working in Betalabs,Any errors in the JS console?,1406912940,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dko2nwcat2a5enwq6736,task_subcomment,NA
+"VisualEditor Mobile:Mobile VE does not load after saving the first time edit in production (en.wiki), shows Error,can't load section","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE in prouction
+
+2.Make any edit and save it
+
+3.Try to reopen the page with Mobile VE
+
+Observed Result:
+VE does not load the page and the error appears:
+Error,can't load section
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14658}",1406838660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ndrboycjw5r2mnma3qfj,task_description,declined
+"VisualEditor Mobile:Mobile VE does not load after saving the first time edit in production (en.wiki), shows Error,can't load section",Think this was solved long ago?,1409669905,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ndrboycjw5r2mnma3qfj,task_subcomment,NA
+Weird behavior of the Cite extension with VisualEditor,"References in MediaWiki view mode (rendering correctly)
+
+This is most likely due to Cite, but the extension works in ""view"" mode and fails in VE in my local wiki.
+
+The problem: 
+
+Citations/References work well in view mode but when VE loads, they appear as their ""raw"" tags <ref>Something</ref> and <references />. 
+
+More details: From within VE, even when the references appear broken like above, I can still add a reference, which renders correctly as [1]. When I save the page the wikitext is correct and the view mode recognizes all references (both those that were broken and those that were just inserted). Then if I re-edit the page, the references are broken again.
+
+Details -
+
+Cite extension is installed from the git repository, and this line is in LocalSettings.php:
+require_once ""$IP/extensions/Cite/Cite.php"";
+
+This happens in Chrome 36.0.1985.125 and Firefox 31.0 under Ubuntu 14.04
+
+
+Attachments: 
+
+View mode and edit mode of the same page (no change to wikitext)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14545}",1406787600,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-p274rceja3pbo4jwirun,task_description,invalid
+Weird behavior of the Cite extension with VisualEditor,"Apparently, the solution was to update and restart Parsoid.",1406832203,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-p274rceja3pbo4jwirun,task_subcomment,NA
+Weird behavior of the Cite extension with VisualEditor,"Created attachment 16107
+Same page in view mode
+
+**Attached**: {F14547}",1406787705,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-p274rceja3pbo4jwirun,task_subcomment,NA
+Weird behavior of the Cite extension with VisualEditor,"Created attachment 16106
+Same page in view mode
+
+**Attached**: {F14546}",1406787665,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-p274rceja3pbo4jwirun,task_subcomment,NA
+MediaWiki 1.24wmf6 required when trying to install VisualEditor_REL1.23,"**Author:** `sure4us`
+
+**Description:**
+A number of people trying to install 1.23.1 + VE + Parsoid are finding an error that crashes the site.
+
+https://www.mediawiki.org/wiki/Extension_talk:VisualEditor#MediaWiki_1.24wmf6_required_when_trying_to_install_VisualEditor_REL1.23_45012
+
+
+I'm also experiencing it, here's the error messaging:
+
+
+[d64ccb4d] /wiki/ Exception from line 3279 of /home/mywiki/public_html/wiki/includes/GlobalFunctions.php: MediaWiki 1.24wmf6 required--this is only 1.23.1
+
+Backtrace:
+
+#0 /home/mywiki/public_html/wiki/extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW(string)
+#1 [internal function]: VisualEditorHooks::onSetup()
+#2 /home/mywiki/public_html/wiki/includes/Setup.php(601): call_user_func(string)
+#3 /home/mywiki/public_html/wiki/includes/WebStart.php(156): require_once(string)
+#4 /home/mywiki/public_html/wiki/index.php(43): require(string)
+#5 {main}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406767620,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-vvn3l4s5izeg73ehqg63,task_description,declined
+MediaWiki 1.24wmf6 required when trying to install VisualEditor_REL1.23,"This sounds like the creation of the temporary tarball was very broken, but thanks to Kunal's work on ExtensionDistributor this should now be moot. Sorry for the troubles.",1408566124,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vvn3l4s5izeg73ehqg63,task_subcomment,NA
+MediaWiki 1.24wmf6 required when trying to install VisualEditor_REL1.23,"I just downloaded the latest tarball from <https://www.mediawiki.org/wiki/Special:ExtensionDistributor?extdist_extension=VisualEditor&extdist_version=REL1_23&extdist_submit=Continue>, and I see wmfUseMW( '1.22' ) in it.",1408563323,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-vvn3l4s5izeg73ehqg63,task_subcomment,NA
+MediaWiki 1.24wmf6 required when trying to install VisualEditor_REL1.23,"If they installed VisualEditor master, than that is bound to fail because it requires 1.24alpha (as all extensions do unless otherwise noted).
+
+There is a REL1_23 branch[1] which requires 1.22 or higher (not 1.24alpha).
+
+It seems however that the custom 1.23 download made available is packages from some arbitrary version not documented anywhere and that version contains ""wfUseMW( '1.24wmf6' );"" in its code.
+
+I suggest whatever hacks were applied to produce this tarball are applied to REL1_23 following regular code review. If it's based on master instead of REL1_23, we can fast-forward REL1_23 to master and apply the fixes then.
+
+Either way whatever we promote as 1.23-compat should be git and go through review. And when it does, it should be fixed to not require wfUseMW( '1.24wmf6' ); which is a bit silly for code explicitly made for 1.23.
+
+[1] https://github.com/wikimedia/mediawiki-extensions-VisualEditor/tree/REL1_23
+[2] https://www.mediawiki.org/wiki/Extension:VisualEditor",1406819171,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vvn3l4s5izeg73ehqg63,task_subcomment,NA
+VisualEditor:Categories when added are shown as return character in VE.,"screenshot1
+
+Environments-test2, betalabs, production.
+
+Steps-
+1> open a blank page in VE and type in some text.
+2> while the cursor is still at the end of the last character, add at least two categories.
+3> Save the page.
+4> Now open the page again in VE. Notice the categories are shown as return characters at the end of the text(one for each category added).See screenshots.
+
+Happens only in Chrome and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14346}",1406656560,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-dm6dyr2mel4tbhvuduxe,task_description,resolved
+VisualEditor:Categories when added are shown as return character in VE.,"Yeah, these are bug 48290 issues…
+
+*** This bug has been marked as a duplicate of bug 48290 ***",1406754254,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dm6dyr2mel4tbhvuduxe,task_subcomment,NA
+VisualEditor:Categories when added are shown as return character in VE.,"Created attachment 16096
+screenshot3
+
+**Attached**: {F14348}",1406656613,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-dm6dyr2mel4tbhvuduxe,task_subcomment,NA
+VisualEditor:Categories when added are shown as return character in VE.,"Created attachment 16095
+screenshot2
+
+**Attached**: {F14347}",1406656586,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-dm6dyr2mel4tbhvuduxe,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.","screenshot
+
+Environments-test2
+
+Steps-
+1> open a page in VE.
+2> Insert ->Media. 
+3>Select to add a media file. Opens the Media Settings dialog.
+4>Now click on “Caption” pane and Select to insert a Link .
+5> Click on the style text menu to select the Language and type some text. See screenshot.
+6> Now move the cursor to the link, notice the link icon is not appearing, but the icon in the toolbar does get selected. 
+7>Now  try to insert a new link by selecting the link icon on toolbar, does not open the link inspector and the text in the pane gets typed as normal text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14342}",1406652060,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_description,resolved
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",Issue fixed in test2.,1409667851,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",Assuming yes.,1409345322,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",Possibly fixed in 2014-07-31?,1407166916,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",Cannot reproduce it anymore in test2 or beta.,1407163211,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.","Yeah, this is not very good.",1406754539,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.",same issue found in betalabs,1406653055,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-xl7tc3cnzjbugrn4flu6,task_subcomment,NA
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.","screenshot1
+
+Environment-test2, production
+
+Steps-
+1> Open a page in VE.
+2> Insert ->Media. 
+3>Select to add a media file. Opens the Media Settings dialog.
+4>Now click on “Alternative Text”, with cursor in this input field. Select to insert a Comment or Special Character or a link.
+5> Notice that the inspectors open up in the Alternative text input field (see screenshots), but when entered they do show up in the Caption pane.
+Also see 62410 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14337}",1406650800,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_description,resolved
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.","
+
+*** This bug has been marked as a duplicate of bug 68806 ***",1406655142,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_subcomment,NA
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.",same issue found in betalabs.,1406652915,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_subcomment,NA
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.","Created attachment 16092
+screenshot3
+
+**Attached**: {F14340}",1406650898,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_subcomment,NA
+"VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.","Created attachment 16091
+screenshot2
+
+**Attached**: {F14339}",1406650875,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3m42xm4a2po4jrwv4dcy,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"cloudbees branch was a step in moving jobs from Cloudbees. Now that the move is finished, the branch should be merged with master.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1406640060,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-wkzeswtrlltjtokvlumh,task_description,resolved
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,Resolved in https://gerrit.wikimedia.org/r/#/c/156809/,1409589895,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"I might have attempted this merge, but I proved to myself yesterday that I still don't understand jjb well enough to do this with confidence.",1408550925,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"Change 152905 abandoned by Hashar:
+Merge cloudbees branch into master
+
+Reason:
+Was merely to highlight how to handle the merge with git.  Will revisit when Zeljkof is back from vacations.
+
+https://gerrit.wikimedia.org/r/152905",1408537513,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"Here what I did:
+
+ git remote update
+ git checkout master
+ git reset --hard gerrit/master
+ git merge --no-ff gerrit/cloudbees
+ # fix conflict
+ git push gerrit HEAD:refs/for/master
+
+
+I think the issue was when using git rebase. That create new commits that Gerrit does not know about.
+
+git merge --no-ff prevents the rebase and thus keep all the commits from cloudbees branch as is.",1407503476,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"Change 152905 had a related patch set uploaded by Hashar:
+Merge cloudbees branch into master
+
+https://gerrit.wikimedia.org/r/152905",1407503364,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"Antoine, is the the way to go? Or is there a better way?",1407428025,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+Merge master and cloudbees branch of integration/jenkins-job-builder-config repository,"$ git checkout cloudbees
+
+$ git checkout -b the_big_merge
+
+$ git rebase master
+First, rewinding head to replay your work on top of it...
+...(fixed all conflicts)...
+
+$ git review
+You are about to submit multiple commits. This is expected if you are
+submitting a commit that is dependent on one or more in-review
+commits. Otherwise you should consider squashing your changes into one
+commit before submitting.
+
+The outstanding commits are:
+
+64e8d18 (HEAD, the_big_merge) Add job for PageTriage tests
+017c8e2 Language screenshot job should run on test2.wikipedia.org
+657f627 Add Chrome build for Math extension on beta labs
+9ad0a82 Tie language screenshot to UbuntuPrecise
+4a70f3f Tie all jobs to UbuntuPrecise
+239bbdb The first job for Math extension
+fc7283c Language screenshot feature file runs only in language screenshot job
+64af5d1 Run language screenshot job manually
+5f3072b Language screenshot jobs run in serial now
+224139e VisualEditor renamed ""test"" folder to ""tests""[1]
+69cb80e mediawiki/core Jenkins job should not send e-mail notifications to ULS team
+3637bbd Remove mobile-tech from Jenkins notifications
+8e51dc8 language-screenshot jobs should use LanguageScreenshotBot user
+6637a2a Upload the language screenshots
+cbc0ff2 Normalize ZeroBanner job
+8a57c13 Support setting VERSION for phantomjs browser
+90eba50 Tests moved from ZeroRatedMobileAccess to ZeroBanner repository
+c85965f WikiLove job runs at Sauce Labs
+d322815 Moved mediawiki_user variable from jobs section to project section
+9254600 Running all CirrusSearch jobs at Sauce Labs
+95d9d29 Moved mediawiki_user variable from jobs section to project section
+e553524 Deleted CentralAuth job
+dcce7bf browsertests: matrix project to take screenshots
+313ca1d Deleted browsertests jobs, created Flow jobs
+2658ea7 Created the first job to run Selenium tests in mediawiki/core
+158770b Moved MultimediaViewer jobs from Cloudbees
+dce5026 Moved two browsertests-qa jobs to Sauce Labs
+522a666 Moved a couple of UploadWizard from Cloudbees
+e75d259 All language team jobs are now running at Sauce Labs
+56263c9 Deleted en.m.wikipedia.org MobileFrontend job
+9f6397d Moved the last two MobileFrontend jobs from Cloudbees
+88a2f1b Replace underscore by spaces in PLATFORM
+f3947d7 Moved the last VisualEditor job from Cloudbees
+53bf24c Created the first Windows XP job
+23be398 Created a couple of VisualEditor test2.wikipedia.org jobs
+ad0ccfa Refactored Flow, MobileFrontend and VisualEditor Sauce Labs jobs. Deleted local VisualEditor jobs.
+52561f5 Deleted local MobileFrontend jobs, refactored MobileFrontend Sauce Labs jobs
+8d65d8b Deleted two local Flow jobs, created two Flow jobs that run on Sauce Labs
+982f9df Disable MF/VE jobs moved to SauceLabs
+64cb2bf Sauce jobs for MobileFrontend
+de563e1 Chrome job for VisualEditor on en.beta
+b09d3ec Add support to pass VERSION for Chrome browsers
+62ca809 Create a -sauce template with headless set to false
+745ce86 Make headless a JJB variable
+427054b Let us manage disable manually
+8d3943c Disable all browsertests jobs
+f775cd1 Adjust node label
+7edd9c8 Notify qa-alerts@lists.wikimedia.org
+ee18913 Reset branch based on origin, not local copy
+67cd040 Fallback to master branch when test repo miss branch
+08a04ae Get mw branch from target URL and check it out
+249dfc4 Allow user to claim failed build
+5ef9dca Refactor UploadWizard API template to use mediawiki_url
+28c4f1f Refactor job template to include mediawiki_url
+54855f7 Add Screenshots for ZeroRatedMobileAccess
+2f66f2b browsertests: Change irc message-type from summary-scm to summary
+2bf9cd6 Export MEDIAWIKI_API_URL when running browser tests
+ea0d30d ZeroRatedMobileAccess had a cloudbees phantomjs install
+5e1b510 Normalize user/pass for language-stage instance
+2f153ee Normalize user/pass for language-browsertests instance
+4c70068 Prefix the two qa/browsertests jobs with 'qa-'
+b82a2b1 Make the job templates to vary by platform
+65031b2 Make platform all lower case
+2d0df48 Vary VisualEditor and ZeroRatedMobileAccess by browser
+671ecd7 Restore WikiLove job!
+76f83f6 Drop version parameter entirely
+906e611 Make the job template to vary by browser
+5b55a1b Rename build 'default' to 'browsertest-website'
+e5ae11d Rename default to 'browsertest'
+f397f8e Use YAML anchors and alias to maintain emails lists
+db84dab Write junit report under /log/junit/
+937cf75 Explode a long line in ZeroRatedMobileAccess
+50b487b Make sure we have a '/log' directory
+ff4f8c1 Split long line into several shorter ones
+d8c842d Tweak git scm to keep the workspace between build
+c14ab86 Avoid error when creating vendor directory
+4919d45 Take a screenshot when a test fails
+a694a43 Moved wikimedia.template to integration/jenkins repository
+2e92f77 Only notify #wikimedia-qa for browsertests results
+3232e6a Deleted job templates that are no longer used
+0b2a346 Added ""browsertests-"" to the beginning of every job
+842ad50 Deleting all Internet Explorer and Chrome jobs
+86e6897 Force cucumber to use colors
+f73b76f Run browser tests on the local machine headlessly
+5cf4441 Add timestamp and ansicolor to the console
+98b95c9 Make the ircbot publisher a macro
+2587d22 Use gem 1.9.3 and the installed bundler version
+59c668b Make bundle install verbose!
+3475b4d Install gems in a shared dir
+e94c1d1 Remove ruby 2.1.1 when running on wmflabs
+b3ba732 Tie browsertests jobs to wmflabs slaves
+1d617b8 .gitreview file for the cloudbees branch
+60e446b Created CentralAuth job
+85842ef Replaced browser_version JJB variable with BROWSER_TAG shell variable
+c643972 Added browser specific tags to ContentTranslation Cucumber feature
+72d9905 Fixed browser for several Jenkins jobs
+c707fa2 Added per-browser tags to MobileFrontend builds
+86a33c7 Renamed a couple of Flow jobs to follow the convention
+d78c52b Added browser specific tags to Cucumber features and scenarios
+4f17984 Update Chrome at Sauce Labs to the most stable version
+f65462a Change recipient for MultimediaViewer alerts
+1d66ec9 Fixed username and password for a Translate job
+3c0a9d5 Merged default and browsertests dcm section
+a72ae6d Refactored shell builders
+7c77449 Refactoring: grouped job templates and builders
+b8fa80d Moved UploadWizard job template to the template file, and jobs to jobs file
+ecbf4e0 Refactored VisualEditor job to use job template
+bbc1072 Refactored Zero job to use the job template
+1e14b88 Moved browsertests to the bottom of the file
+82a7254 Refactored an ULS job to use the template
+aef3275 Rename user for CX to TranslatorToDa
+113b5e5 Created the first ContentTranslation job
+5974b36 Documented Extended E-mail Notification plugin setup
+f58e24e Minor formatting improvements for Jenkins documentation
+217f6b0 Moved environment variables above IRC notification
+d921f3c Renamed e-mail template file so it has the same name as at Cloudbees
+e059c36 Moved Jenkins documentation from mediawiki/selenium[1] repository
+2cb2c9c Using new e-mail notifications
+c846509 Sending MobileFrontend e-mail notifications to mobile-tech
+dfb6b01 Removed myself from all Jenkins e-mail notifications
+ba130d0 Removed Jeff from all e-mail notifications
+a16b4fb Fixed Translate jobs
+a908cc9 Updated Ruby version from 2.1.0 to 2.1.1
+ec8ef0f Add the whole eng MM team to the recipient list of UW test failures
+bd6391a added browsertests-test2.wikipedia.org jobs
+3466d51 added browsertests-en.wikipedia.beta.wmflabs.org jobs
+abb996e refactoring: moved everything from default job template to defaults
+a72ac64 refactoring: moved disabled and triggers from job template to defaults
+46aa64d refactoring: extracted scm out of job template
+5467697 refactoring: extracted publishers out of job template
+7e78369 refactoring: extracted shell builder out of job template
+3baf71e Added the rest of UploadWizard jobs
+c6a2145 added ""api-"" to names of UploadWizard API jobs
+a6ff524 Added missing ""-windows"" to Flow IE job names
+ff68e9a added remaining UniversalLanguageSelector jobs
+d596706 Spread load evenly
+b5a13f6 Updated UniversalLanguageSelector and VisualEditor jobs
+c12b00b added Translate jobs
+4900cbd added comments, where the jobs run
+0ea737b Fixed mediawiki_url for test2 Flow jobs
+9478a96 PLATFORM environment variable should be quoted
+19a9888 added Flow jobs
+aabbe80 added MobileFrontend jobs
+3748443 Separated repositories with comments
+71c909f Add the whole eng MM team to the recipient list of e2e test failures
+3cdf7c5 Added TwnMainPage job
+2e76c52 ZeroRatedMobileAccess does not need to fetch a commit from Gerrit any more
+7bac79e added MultimediaViewer job
+e5824fe Sorted job variables alphabetically
+5e9d306 Spreading load evenly
+eacd407 added CirrusSearch jobs
+87c4b66 moved job template and jobs to separate files
+b920181 shorter file names
+a472a19 deleted unused job
+8106cde one job template to rule them all
+fdc8cfe VisualEditor and WikiLove are using the same job template
+3a992de yaml file for the first UniversalLanguageSelector job
+ac6ad09 Merged UploadWizard yaml files into one
+ab4f0fe Created one VisualEditor job template to rule them all
+6a27177 Combined two VisualEditor jobs into one file
+86a78ea Make sure the job does not fail if phantoms is not already installed
+bedc0f3 yaml file for ZeroRatedMobileAccess
+93fe2b6 yaml file for WikiLove-en.wikipedia.beta.wmflabs.org-linux-firefox
+376ca73 yaml file for VisualEditor-test2.wikipedia.org-linux-firefox
+0f3dcb5 forgot junit publisher
+bfaa8d3 yaml file for VisualEditor-test2.wikipedia.org-linux-chrome
+7705392 looks like James was not receiving some e-mail messages
+6154a38 yaml file for VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox
+8dad741 make it explicit that the job should care just about master branch
+7f82e70 yaml file for VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome
+9f05512 yaml file for VisualEditor-production.wikimedia.org
+a6fd55e yaml file for UploadWizard-commons.wikimedia.org
+777b7ca config file for UploadWizard-commons.wikimedia.beta.wmflabs.org job
+1f0359a Updated readme file with basic informatioin
+f9f9a0d Installing PhantomJS using the latest advice from Cloudbees support
+5a2b6af Ported free-style job to jenkins-job-builder
+d736f27 Initial commit
+
+Do you really want to submit the above commits?
+Type 'yes' to confirm, other to cancel: 
+Aborting.",1407427995,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-wkzeswtrlltjtokvlumh,task_subcomment,NA
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"screenshot1
+
+Environment- test2,betalabs.
+
+Steps-
+1>Open a page in VE.
+2>open Advanced Settings .Enable Display title and enter a title. Click “Apply Changes”.
+3>Click on “Save Page”
+4>Click on “Review your Changes”. Notice DISPLAYTITLE:titlename is shown under your text.
+5> Now click on Return to Save form. Click on “Cancel” on the Save your changes dialog.
+6>Go to Advanced Settings again in Page options. 
+7>Uncheck the “Enable Display title” checkbox and click to “Apply Changes”. 
+8> Repeat step#3 and #4. Notice even after disabling the display title it is still visible under your text in the “Review your changes” dialog. Open the advanced settings and you would notice that the enable display title is unchecked, but it shows up in Review your changes.
+
+Try the above steps with the other settings such as “Let this page be indexed by search engines”, “Show a tab on this page to add a new section”and with Categories too.Please see screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14247}",1406578140,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-zdzo44mp6rva2lnt47x2,task_description,resolved
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"Yes, this is bug 68619.
+
+*** This bug has been marked as a duplicate of bug 68619 ***",1406578618,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zdzo44mp6rva2lnt47x2,task_subcomment,NA
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"Created attachment 16071
+screenshot2
+
+**Attached**: {F14248}",1406578218,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-zdzo44mp6rva2lnt47x2,task_subcomment,NA
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"screenshot1
+
+Environment- test2,betalabs.
+
+Steps-
+1>Open a page in VE.
+2>open Advanced Settings .Enable Display title and enter a title. Click “Apply Changes”.
+3>Click on “Save Page”
+4>Click on “Review your Changes”. Notice DISPLAYTITLE:titlename is shown under your text.
+5> Now click on Return to Save form. Click on “Cancel” on the Save your changes dialog.
+6>Go to Advanced Settings again in Page options. 
+7>Uncheck the “Enable Display title” checkbox and click to “Apply Changes”. 
+8> Repeat step#3 and #4. Notice even after disabling the display title it is still visible under your text in the “Review your changes” dialog. Open the advanced settings and you would notice that the enable display title is unchecked, but it shows up in Review your changes.
+
+Try the above steps with the other settings such as “Let this page be indexed by search engines”, “Show a tab on this page to add a new section”and with Categories too.Please see screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14243}",1406577600,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ojclybdvdmwc7icip62q,task_description,resolved
+VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.,"
+
+*** This bug has been marked as a duplicate of bug 68619 ***",1406577779,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ojclybdvdmwc7icip62q,task_subcomment,NA
+"VisualEditor: Comment Edit dialog does not close, after inserting a list.","screenshot
+
+Environment- test2 and betalabs
+
+Steps-
+1> Open a blank page in VE and type in some text.
+2>At the end of the text insert a comment.
+3>Click on the Comment , to open the comment edit dialog.
+4> Now while the cursor is till in the comment edit dialog , click to insert a bullet point / numbered list.
+5>Now click on “Done” or “Remove” to close the dialog. The dialog stays open.Please see screenshot.
+
+Same behavior in Chrome, FF and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows XP
+
+**Attached**: {F14169}",1406559660,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-rci6ybeykugoc2ofg22w,task_description,resolved
+"VisualEditor: Comment Edit dialog does not close, after inserting a list.","Merging with bug 68679.
+
+*** This bug has been marked as a duplicate of bug 68679 ***",1406597593,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rci6ybeykugoc2ofg22w,task_subcomment,NA
+VisualEditor should display entire comment when the orange icon is clicked,"Screenshot of too-small comment popup
+
+Currently, when the orange comment icon is clicked, we see only the first few words of the comment.
+
+To read the whole comment, we have to click again, which takes us to the edit view. You shouldn't have to launch the editor just to read the whole text.
+
+The little popup that comes up when you first click the icon (I've lost track of VE jargon, sorry) should show the entire comment text, over multiple lines if necessary, and preferably in black or a darker gray.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14130}",1406542140,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-mxtw6d3rc6477dklsvnc,task_description,declined
+VisualEditor should display entire comment when the orange icon is clicked,"(In reply to This, that and the other (TTO) from comment #2)
+> You don't think 8 words is rather too short?
+
+The number of words shown is language dependent.
+
+On my system, if the comment is ""This is a ridiculously-long sesquipedalian comment."" you get everything except "" comment.""
+
+If the comment is ""Please don't change Obama's name."" it shows the entire thing, which is the point of showing the snippet version.",1406584613,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxtw6d3rc6477dklsvnc,task_subcomment,NA
+VisualEditor should display entire comment when the orange icon is clicked,You don't think 8 words is rather too short?,1406582833,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-mxtw6d3rc6477dklsvnc,task_subcomment,NA
+VisualEditor should display entire comment when the orange icon is clicked,"No. People writing long comments is a sign that they're doing it wrong, and encouraging such bad practice is contrary to helping editors.",1406564517,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxtw6d3rc6477dklsvnc,task_subcomment,NA
+"beta: ResourceLoader CSS URL gzipped twice, causing skins to be broken","One of the CSS resource loader URL yield content which is gzipped twice :-(
+
+The content is shown by piping to gzcat twice:
+
+curl 'http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles%7Cwikibase.client.init&only=styles&skin=vector&*'|gzcat|gzcat
+
+Headers:
+
+> User-Agent: curl/7.30.0
+> Host: bits.beta.wmflabs.org
+> Accept: */*
+> 
+< HTTP/1.1 200 OK
+* Server Apache is not blacklisted
+< Server: Apache
+< Access-Control-Allow-Origin: *
+< Expires: Mon, 28 Jul 2014 09:22:53 GMT
+< X-Content-Type-Options: nosniff
+< Content-Encoding: gzip, gzip
+< X-Powered-By: HHVM/3.3.0-dev
+< Cache-control: public, max-age=300, s-maxage=300
+< Vary: Accept-Encoding
+< Last-Modified: Thu, 24 Jul 2014 03:43:51 GMT
+< Content-Type: text/css; charset=utf-8
+< Content-Length: 24050
+< Accept-Ranges: bytes
+< Date: Mon, 28 Jul 2014 09:19:08 GMT
+
+
+
+Same goes on when passing Accept-Encoding: gzip
+
+I restarted varnish on the bits cache to clear up the bits cache, hasn't solved anything.
+
+
+The minified CSS cache key is enwiki:resourceloader:filter:minify-css:7:e07e6ad07840d291e66cf3fe9f0980c3
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406539320,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-j7533hletfeocs3ygieq,task_description,resolved
+"beta: ResourceLoader CSS URL gzipped twice, causing skins to be broken",Fixed in 4bdfea04cea2e54e6076a1c6b955ba1e1b51209f.,1411712675,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-j7533hletfeocs3ygieq,task_subcomment,NA
+"beta: ResourceLoader CSS URL gzipped twice, causing skins to be broken","Niklas reported it to be fixed in Vagrant:
+
+ hhvm: set GzipCompressionLevel = 0 to avoid double-gzip
+ https://gerrit.wikimedia.org/r/#/c/145771/
+
+Which was bug 67928",1406561078,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-j7533hletfeocs3ygieq,task_subcomment,NA
+"beta: ResourceLoader CSS URL gzipped twice, causing skins to be broken","Proper command:
+
+curl 'http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles%7Cwikibase.client.init&only=styles&skin=vector&*' | gzcat | gzcat
+
+** yields some CSS **",1406560868,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-j7533hletfeocs3ygieq,task_subcomment,NA
+VisualEditor: Edge case of unintentional image removal,"See https://it.wikipedia.org/w/index.php?title=Vallo_Atlantico&oldid=66317144&veaction=edit :
+Reach the paragraph ""Comandi del Vallo Atlantico"", see there's a list there.
+It looks weird because the syntax for the picture on the right is in the middle of the list.
+Average user doesn't actually know/realize this and just wants to fix the list.
+S/he will place the cursor right after the word ""Danimarca"" on the second line and hit Canc. The pic suddenly disappears.
+ 
+(Right now there's a further bug 68708 which did lead to the image being removed without the user really noticing it: he noticed that the ""Commando tedesco"" line was not aligned properly and tried to fix that by going on that line and hitting Backspace. He didn't notice the pic getting highlighted and hit Backspace again, so the page lost focus and all he could see when he read the list again was that he had fixed it.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406532480,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5usl4n5awcjbcbomw5bs,task_description,resolved
+VisualEditor: Edge case of unintentional image removal,"This is probably now fixed, as we change the selection when you type and move the object into view (so it's clear what's going to happen).",1444159075,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5usl4n5awcjbcbomw5bs,task_subcomment,NA
+VisualEditor:  Changes made after canceling a Save are lost,"Steps to Reproduce:
+1. Add some text to a page (""abc"").
+
+2. Click 'Save'.
+
+3. Think, ""Oops, I forgot to add…""
+
+4. Click the cancel button on the Save dialog.
+
+5. Go add the other text (""xyz"") (or add or change images, templates, refs, or remove the abc text that you typed earlier; it doesn't matter what changes you make).
+
+6. Save the page.
+
+7. Where's the ""xyz"" text I just added?!
+
+Actual Results:  
+This is a ""lose most of your work"" bug:  
+
+Everything you do after cancelling the first time is irretrievably lost, and unless you just happen to Review Changes before saving, you won't know that you're going to lose everything until it's too late to copy it to another page.
+
+
+Reproducible: Always
+
+Reported in Safari 7.1 on OS X 10.9.4; confirmed in Safari 6.1.4 and Firefox 30 on Mac OS 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1406498640,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-geqryn2sngosctjjau7u,task_description,resolved
+VisualEditor:  Changes made after canceling a Save are lost,"
+
+*** This bug has been marked as a duplicate of bug 68619 ***",1406564584,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-geqryn2sngosctjjau7u,task_subcomment,NA
+VisualEditor: Pawn ♙ appears if you type near a [[Link]] after the {{convert}} template,"Intention:
+Add a missing word (""and"") towards the end of a sentence.  
+
+Steps to Reproduce:
+1. Start with a pragraph that contains:
+
+* the en.wp {{convert}} template
+* several [[Links]] after the template
+
+2. Click before or after one of these links.
+
+3. Type a space and the word ""and"" (or any word, but don't press return to create a new paragraph).
+
+4. See the pawns?
+
+5. Now click somewhere else, and watch the pawns and text replicate.
+
+Actual Results:  
+See https://en.wikipedia.org/w/index.php?oldid=618713444#Composition for an example of the results.
+
+
+Reproducible: Always
+
+Found in Firefox 31 on Windows 7; confirm in Safari 6 on Mac OS 10.8.5
+
+May be related to Bug 68151
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/w/index.php?oldid=618713444#Composition
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68151",1406497380,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wbqcdudfren5nxeb76rg,task_description,resolved
+VisualEditor: Pawn ♙ appears if you type near a [[Link]] after the {{convert}} template,"Yeah, I think this is the same.
+
+*** This bug has been marked as a duplicate of bug 68151 ***",1406565501,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wbqcdudfren5nxeb76rg,task_subcomment,NA
+VisualEditor: copying a text and moving down using the arrow adds a space,"It often happens to me that I select a letter in a word, copy it using Ctrl-C, and move the caret to the next line using the arrow-down keyboard key, and a space is added before the letter that I selected.
+
+It's not completely consistent, but it happens in about 70% of my attempts to do the above.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406466780,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-7eeeai67evjmijctkql6,task_description,resolved
+VisualEditor: copying a text and moving down using the arrow adds a space,"Not reproducible anymore - marking it as Resolved. 
+
+For such issues any additional info would be helpful: which browser/OS the issue was happening. Also, the structure of a page may be important - say, the issue happens in bulleted list, or within a text with inline images etc",1425003675,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-7eeeai67evjmijctkql6,task_subcomment,NA
+PHP Notice:  Undefined index: REQUEST_TIME in extensions/EventLogging/includes/EventLogging.php on line 56,"php5 phpunit.php
+
+When doing http://paste.debian.net/111811/ , phpunit incurs in this:
+
+PHP Notice:  Undefined index: REQUEST_TIME in /srv/vagrant/mediawiki/extensions/EventLogging/includes/EventLogging.php on line 56
+PHP Stack trace:
+PHP   1. {main}() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:0
+PHP   2. MediaWikiPHPUnitCommand::main() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:160
+PHP   3. PHPUnit_TextUI_Command->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiPHPUnitCommand.php:42
+PHP   4. PHPUnit_TextUI_TestRunner->doRun() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/Command.php:176
+PHP   5. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/TestRunner.php:350
+PHP   6. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+PHP   7. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+PHP   8. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+PHP   9. PHPUnit_Framework_TestSuite->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:749
+PHP  10. MediaWikiTestCase->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:779
+PHP  11. PHPUnit_Framework_TestCase->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiTestCase.php:133
+PHP  12. PHPUnit_Framework_TestResult->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:783
+PHP  13. PHPUnit_Framework_TestCase->runBare() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestResult.php:648
+PHP  14. PHPUnit_Framework_TestCase->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:838
+PHP  15. ReflectionMethod->invokeArgs() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988
+PHP  16. SpecialNewPagesFeedTest->testAddArticles() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988
+PHP  17. ApiTestCase->doApiRequestWithToken() /srv/vagrant/mediawiki/extensions/PageTriage/tests/phpunit/SpecialNewPagesFeedTest.php:100
+PHP  18. ApiTestCase->doApiRequest() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:142
+PHP  19. ApiMain->execute() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:99
+PHP  20. ApiMain->executeAction() /srv/vagrant/mediawiki/includes/api/ApiMain.php:332
+PHP  21. ApiEditPage->execute() /srv/vagrant/mediawiki/includes/api/ApiMain.php:907
+PHP  22. EditPage->internalAttemptSave() /srv/vagrant/mediawiki/includes/api/ApiEditPage.php:401
+PHP  23. Article->doEditContent() /srv/vagrant/mediawiki/includes/EditPage.php:1973
+PHP  24. Article->__call() /srv/vagrant/mediawiki/includes/EditPage.php:1973
+PHP  25. call_user_func_array() /srv/vagrant/mediawiki/includes/page/Article.php:1992
+PHP  26. WikiPage->doEditContent() /srv/vagrant/mediawiki/includes/page/Article.php:1992
+PHP  27. wfRunHooks() /srv/vagrant/mediawiki/includes/page/WikiPage.php:2032
+PHP  28. Hooks::run() /srv/vagrant/mediawiki/includes/GlobalFunctions.php:4031
+PHP  29. call_user_func_array() /srv/vagrant/mediawiki/includes/Hooks.php:206
+PHP  30. WikimediaEventsHooks::onPageContentInsertComplete() /srv/vagrant/mediawiki/includes/Hooks.php:206
+PHP  31. WikimediaEventsHooks::logPageCreation() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:254
+PHP  32. EventLogging::logEvent() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:196
+
+Notice: Undefined index: REQUEST_TIME in /srv/vagrant/mediawiki/extensions/EventLogging/includes/EventLogging.php on line 56
+
+Call Stack:
+    0.0005     252912   1. {main}() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:0
+    3.1858   25034984   2. MediaWikiPHPUnitCommand::main() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:160
+    3.1859   25047464   3. PHPUnit_TextUI_Command->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiPHPUnitCommand.php:42
+   43.5670  196201632   4. PHPUnit_TextUI_TestRunner->doRun() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/Command.php:176
+   43.6076  196524896   5. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/TestRunner.php:350
+ 2979.9686 1021381672   6. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+ 2979.9689 1021383176   7. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+ 3006.5969 1036522696   8. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709
+ 3007.1232 1037095048   9. PHPUnit_Framework_TestSuite->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:749
+ 3007.1232 1037095048  10. MediaWikiTestCase->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:779
+ 3007.1233 1037095208  11. PHPUnit_Framework_TestCase->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiTestCase.php:133
+ 3007.2455 1037095568  12. PHPUnit_Framework_TestResult->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:783
+ 3007.2457 1037096512  13. PHPUnit_Framework_TestCase->runBare() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestResult.php:648
+ 3007.6986 1037467560  14. PHPUnit_Framework_TestCase->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:838
+ 3007.6987 1037468504  15. ReflectionMethod->invokeArgs() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988
+ 3007.6987 1037468776  16. SpecialNewPagesFeedTest->testAddArticles() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988
+ 3007.6987 1037469976  17. ApiTestCase->doApiRequestWithToken() /srv/vagrant/mediawiki/extensions/PageTriage/tests/phpunit/SpecialNewPagesFeedTest.php:100
+ 3007.6987 1037471616  18. ApiTestCase->doApiRequest() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:142
+ 3007.6992 1037528872  19. ApiMain->execute() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:99
+ 3007.6992 1037528920  20. ApiMain->executeAction() /srv/vagrant/mediawiki/includes/api/ApiMain.php:332
+ 3007.7069 1037555016  21. ApiEditPage->execute() /srv/vagrant/mediawiki/includes/api/ApiMain.php:907
+ 3008.1653 1037899936  22. EditPage->internalAttemptSave() /srv/vagrant/mediawiki/includes/api/ApiEditPage.php:401
+ 3008.2155 1037909472  23. Article->doEditContent() /srv/vagrant/mediawiki/includes/EditPage.php:1973
+ 3008.2155 1037910264  24. Article->__call() /srv/vagrant/mediawiki/includes/EditPage.php:1973
+ 3008.2155 1037910704  25. call_user_func_array() /srv/vagrant/mediawiki/includes/page/Article.php:1992
+ 3008.2155 1037911512  26. WikiPage->doEditContent() /srv/vagrant/mediawiki/includes/page/Article.php:1992
+ 3008.3812 1037999520  27. wfRunHooks() /srv/vagrant/mediawiki/includes/page/WikiPage.php:2032
+ 3008.3812 1037999568  28. Hooks::run() /srv/vagrant/mediawiki/includes/GlobalFunctions.php:4031
+ 3008.3813 1038001544  29. call_user_func_array() /srv/vagrant/mediawiki/includes/Hooks.php:206
+ 3008.3813 1038002848  30. WikimediaEventsHooks::onPageContentInsertComplete() /srv/vagrant/mediawiki/includes/Hooks.php:206
+ 3008.3813 1038002848  31. WikimediaEventsHooks::logPageCreation() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:254
+ 3008.3813 1038003736  32. EventLogging::logEvent() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:196
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14495}",1406409960,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-svm6hns77rkpqj4hta5x,task_description,invalid
+PHP Notice:  Undefined index: REQUEST_TIME in extensions/EventLogging/includes/EventLogging.php on line 56,"The `REQUEST_TIME` code that assumed HTTP context and was problematic when called from the command-line (e.g. in PHPUnit) was removed in {c12e93f9e1f5b05776bfb96ae467ffef15e7f13c}.
+
+```lang=diff
+@@ -53,22 +60,17 @@ static function logEvent( $schemaName, $revId, $event, $options = 0 ) {
+-			'timestamp'        => $_SERVER[ 'REQUEST_TIME' ],		
+```",1475706089,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-svm6hns77rkpqj4hta5x,task_subcomment,NA
+PHP Notice:  Undefined index: REQUEST_TIME in extensions/EventLogging/includes/EventLogging.php on line 56,"Your definition of ""a bunch"" differs of 1-2 orders of magnitude from mine. :) I still have open patches to fix the bugs I found in the last phpunit run; until those are merged in gerrit, I won't try again.",1421413832,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-svm6hns77rkpqj4hta5x,task_subcomment,NA
+PHP Notice:  Undefined index: REQUEST_TIME in extensions/EventLogging/includes/EventLogging.php on line 56,"Seems EventLogging works fine under HHVM with a bunch of other extensions. Proposed https://gerrit.wikimedia.org/r/#/c/185405/ passed and ran with:
+
+```
+mediawiki/extensions/AbuseFilter
+mediawiki/extensions/CheckUser
+mediawiki/extensions/ConfirmEdit
+mediawiki/extensions/Echo
+mediawiki/extensions/EventLogging
+mediawiki/extensions/JsonConfig
+mediawiki/extensions/Mantle
+mediawiki/extensions/MobileApp
+mediawiki/extensions/MobileFrontend
+mediawiki/extensions/SpamBlacklist
+mediawiki/extensions/Thanks
+mediawiki/extensions/VisualEditor
+mediawiki/extensions/WikiGrok
+mediawiki/extensions/ZeroBanner
+mediawiki/extensions/ZeroPortal
+```
+
+Can you still reproduce?",1421407816,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-svm6hns77rkpqj4hta5x,task_subcomment,NA
+VisualEditor Mobile: fresh accounts being taken to VE by default on beta labs,"Possible regression: Today I created a few fresh accounts on beta labs (desktop Chrome browser, mobile site) to test other stuff, and I noticed that when I tapped the edit pencil for the first time, I was taken to the VE editor instead of wikitext editor. Awhile back, we decided *not* to send new users to VE by default on any wiki and merged a patch to fix this -- looks like it's no longer working 
+:-/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406312100,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-nhp4v32xljmakc2dxomi,task_description,declined
+VisualEditor Mobile: fresh accounts being taken to VE by default on beta labs,"When I cleared cookies, the problem disappeared, so it must've been just lingering VE cookie crumbs on my machine from all those sockpuppets I've been using on beta labs :) Closing.",1406742992,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-nhp4v32xljmakc2dxomi,task_subcomment,NA
+VisualEditor Mobile: fresh accounts being taken to VE by default on beta labs,So far haven't been able to reproduce this. Tested in desktop Chrome on beta labs.,1406316292,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-nhp4v32xljmakc2dxomi,task_subcomment,NA
+VisualEditor Mobile: fresh accounts being taken to VE by default on beta labs,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/0AK0U7Nl",1406312415,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nhp4v32xljmakc2dxomi,task_subcomment,NA
+"VisualEditor: Sidebar button ""Add more information"" in template dialog is cut off / too long","Screenshot of bug
+
+In general items in the sidebar are wiki input (template names, parameter names) which are fine being cut off.
+
+When the item is a UI element for inserting a new parameter though, it shouldn't be cut off. We might as well put the ellipsis in the localisation message (joking) for it is never rendered fully... (also no tooltip with full version). This is even more problematic considered it's localised. In English the first two words are enough to make sense of it, but we can't assume that for all languages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14224}",1406169480,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-27c6qwr5exrk2ddgkl7k,task_description,declined
+"VisualEditor: Sidebar button ""Add more information"" in template dialog is cut off / too long","Width is fine in en/fr/de/nl, and appears in response to user action, selected at first.",1415062542,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-27c6qwr5exrk2ddgkl7k,task_subcomment,NA
+VisualEditor: Template dialog should provide a way to add parameters up front,"Right now there's imho two usability issues with the default (simplified) Template editor related to getting to the screen for adding parameters.
+
+I expect to see an input field and a pool of parameters to pick from right after clicking.
+
+Instead there is a widget labelled ""Add more information"". This is apparently the button to unhide the panel to add parameters. I'm not sure how this is useful, we can just ditch that button and have that always be visible? (maybe in the odd case of templates with no known parameters or explicitly documented as taking none we could hide it behind a button to avoid confusion, but we should optimise for the common case).
+
+This widget is confusing because:
+* It's labelled ""more"" information, but at this point it's the first parameter, not an additional one (unless you count the template name as information).
+* It's called ""information"" which is a bit vague (we use ""parameter"" and ""field"" elsewhere).
+* After inserting a parameter, the insertion panel goes away and I have to re-open it again. I recall it being there from the start and staying there in the past. Because it's implemented as a placeholder for an individual parameter now, this is presumably no longer possible. I think we should make this panel the ""add parameter"" interface, and not have ""add parameter"" insert this placeholder panel for a one-off use.
+
+I'd say, as a first step (enough to fix this bug), hide the button, have the panel be visible from the start. And then continue like it is now (after inserting the first, the ""add more information"" button is used to add additional parameters.",1406169000,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qxncvpizrrogrxizezsv,task_description,resolved
+VisualEditor: Template dialog should provide a way to add parameters up front,"It seems like the current version of the template dialog has fixed these usability problems, so I'm closing.",1434390920,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-qxncvpizrrogrxizezsv,task_subcomment,NA
+VisualEditor: Page Settings option is getting cut off in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open any page in betalabs with VE
+2.Open the page settings option
+
+Observed Result:
+The Page Settings menu is getting cut off
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14188}",1406154540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gns6o7tbrfc7vxzburbb,task_description,resolved
+VisualEditor: Page Settings option is getting cut off in Betalabs,"
+
+*** This bug has been marked as a duplicate of bug 57366 ***",1406156548,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gns6o7tbrfc7vxzburbb,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Screenshot tests have their own build, we do not want them running in the regular VE build: https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/115/testReport/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1406143740,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-kpls4bc5j2jlc3ln667n,task_description,resolved
+don't run screenshot tests in normal VE build,"Change 149045 merged by jenkins-bot:
+Language screenshot feature file runs only in language screenshot job
+
+https://gerrit.wikimedia.org/r/149045",1406547587,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Change 149047 merged by jenkins-bot:
+[BrowserTest] Language screenshot feature runs only for language screenshot job
+
+https://gerrit.wikimedia.org/r/149047",1406224326,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Change 149047 had a related patch set uploaded by Vikassy:
+[BrowserTest] Language screenshot feature runs only for language screenshot job
+
+https://gerrit.wikimedia.org/r/149047",1406222044,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Change 149045 had a related patch set uploaded by Vikassy:
+WIP: Language screenshot runs only for language screenshot job
+
+https://gerrit.wikimedia.org/r/149045",1406221503,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+don't run screenshot tests in normal VE build,"Vikas and I will pair on this, probably today.",1406186868,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-kpls4bc5j2jlc3ln667n,task_subcomment,NA
+VisualEditor: The highlight that appears after adding a template while selecting an image is not proper,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Select the image and insert a template like citation needed
+
+Observed Result:
+A highlight appears all around the image 
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14620}",1406068320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cz65rk35yeaxpnwx5nca,task_description,resolved
+VisualEditor: The link inspector appears over the toolbar while trying to add it inside an image for the first time,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE.
+2.Go to Insert>Media.
+3.Search for an image.
+4.Select an image.
+5.When the Media Settings>General settings for that image appears,click on the link inspector icon
+
+Observed Result:
+The link inspector icon appears over the toolbar,overlapping with the border of the Media dialog
+
+See the screenshot attached
+
+
+This issue was found in test2, I need to test it in master once Betalabs is alive again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14472}",1405986960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2bpmj5q3ahfokc4zz46h,task_description,resolved
+VisualEditor: The link inspector appears over the toolbar while trying to add it inside an image for the first time,Resolved months ago.,1423675914,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2bpmj5q3ahfokc4zz46h,task_subcomment,NA
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself","When I select (highlight) some text on the edit mode and start to type some text by replacing the old text, Visual Editor starts copying the text and typing by itself. I've seen it happening only on few articles, like https://fi.wikipedia.org/w/index.php?title=Arseni_Jatsenjuk&veaction=edit and https://fi.wikipedia.org/w/index.php?title=Mykola_Azarov&veaction=edit
+
+I tried this with Firefox and Chrome, logged-in / logged-out, and the same happens on both browsers.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405796700,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-e7pblfgszxhcuzstcumk,task_description,resolved
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself",Seems to be fixed - not reproducible.,1415061931,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-e7pblfgszxhcuzstcumk,task_subcomment,NA
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself","Yeah, I'm pretty sure we fixed this CE buggy stuff a few months ago.",1415055305,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e7pblfgszxhcuzstcumk,task_subcomment,NA
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself",I can't reproduce this issue...,1414806783,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-e7pblfgszxhcuzstcumk,task_subcomment,NA
+"VisualEditor: When highlighting and replacing a text, VE starts typing by itself","In case someone didn't understand my explanation, I have a video uploaded to http://tinypic.com/r/mbik2w/8
+On the video I only typed ""k"" (it doesn't matter what key you hit), and that's what happened.",1405963159,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-e7pblfgszxhcuzstcumk,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"https://test.wikipedia.org/w/index.php?title=Topic:Foo&action=edit&redlink=1
+
+[42ec2509] /w/index.php?title=Topic:Foo&action=edit&redlink=1 Exception from line 2340 of /usr/local/apache/common-local/php-1.24wmf14/includes/EditPage.php: This content model is not supported: flow-board
+
+Backtrace:
+
+#0 /usr/local/apache/common-local/php-1.24wmf14/includes/EditPage.php(960): EditPage->toEditText(Flow\Content\BoardContent)
+#1 /usr/local/apache/common-local/php-1.24wmf14/includes/EditPage.php(536): EditPage->initialiseForm()
+#2 /usr/local/apache/common-local/php-1.24wmf14/includes/actions/EditAction.php(49): EditPage->edit()
+#3 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(431): EditAction->show()
+#4 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(295): MediaWiki->performAction(Article, Title)
+#5 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(603): MediaWiki->performRequest()
+#6 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(452): MediaWiki->main()
+#7 /usr/local/apache/common-local/php-1.24wmf14/index.php(46): MediaWiki->run()
+#8 /usr/local/apache/common-local/w/index.php(3): require(string)
+#9 {main}
+
+--------------------------
+**Version**: master
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=73443",1405736340,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-dqhh6futiytkca6um27i,task_description,resolved
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"This bug is about the behavior of a wiki link `[[Topic:NoSuchUUID]]` MW detects the page doesn't exist so turns it into a URL with `?action=edit&redlink=1`.
+
+Flow's behavior with such a ""redlink"" URL is now:
+  # Redirect to plain Topic:NoSuchUUID
+  # With the fix in T75443 , that results in HTTP status 500 and a friendlier ""The requested page title was invalid. Pages in the Topic namespace are automatically created by Flow."" (`flow-error-invalid-topic-uuid` msg)
+
+I think this is reasonable behavior, so we can declare this resolved ",1418762041,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"Update: there is still an exception being thrown at 
+https://test.wikipedia.org/w/index.php?title=Topic:Foo&action=edit&redlink=1",1409838575,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,S Page is aware of this issue. He describes it here: https://www.mediawiki.org/wiki/User:S_Page_(WMF)#Flow_board_links,1408845798,PHID-USER-zcsdm7lwcehnusyhh6xp,False,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"(In reply to Justin Breeze from comment #3)
+> Just a note...
+> 
+> I am getting this same error on new pages only. I am using VisualEditor.
+> 
+> When I update the portion of the URL from ""&action=edit&redlink=1"" to
+> ""&veaction=edit&redlink=1"" it works fine.
+
+The only reason this works is because the &veaction=edit is completely ignored, thus not creating any problem.",1407458788,PHID-USER-zcsdm7lwcehnusyhh6xp,False,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"Update: VisualEditor isn't the problem. Its the &action=edit portion of the link. If I click on a link that doesn't include &action=edit (even if the page isn't created), such as http://website/w/index.php/User_talk:User, everything works like normal. But if I click a link, such as http://website/w/index.php?title=User_talk:User&action=edit&redlink=1, I get the error described.",1407458552,PHID-USER-zcsdm7lwcehnusyhh6xp,False,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,Confirmed on my wiki. Only happens with new pages and when VisualEditor is on. Everything is resolved when VisualEditor is turned off.,1407192765,PHID-USER-zcsdm7lwcehnusyhh6xp,False,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"**jbreeze** wrote:
+
+Just a note...
+
+I am getting this same error on new pages only. I am using VisualEditor.
+
+When I update the portion of the URL from ""&action=edit&redlink=1"" to ""&veaction=edit&redlink=1"" it works fine.",1406563136,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"Just for the record, a different error is seen at https://test.wikipedia.org/wiki/Topic:Foo
+
+== Error ==
+
+Invalid value was provided for loading flow content. 
+
+Return to Main Page.
+
+[6cf2bd00] /wiki/Topic:Foo Exception from line 162 of /usr/local/apache/common-local/php-1.24wmf14/extensions/Flow/includes/Model/UUID.php: Unknown input to UUID class
+
+Backtrace:
+
+#0 /usr/local/apache/common-local/php-1.24wmf14/extensions/Flow/includes/Actions/Action.php(118): Flow\Model\UUID::create(string)
+ #1 /usr/local/apache/common-local/php-1.24wmf14/extensions/Flow/includes/Actions/Action.php(70): Flow\Actions\FlowAction->detectWorkflowId(Title, WebRequest)
+ #2 /usr/local/apache/common-local/php-1.24wmf14/extensions/Flow/includes/Actions/Action.php(32): Flow\Actions\FlowAction->showForAction(string)
+ #3 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(431): Flow\Actions\FlowAction->show()
+ #4 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(295): MediaWiki->performAction(Article, Title)
+ #5 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(603): MediaWiki->performRequest()
+ #6 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(452): MediaWiki->main()
+ #7 /usr/local/apache/common-local/php-1.24wmf14/index.php(46): MediaWiki->run()
+ #8 /usr/local/apache/common-local/w/index.php(3): require(string)
+ #9 {main}",1405997915,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+Flow: Internal error when following redlink to a non-existent page in Topic namespace,"Put this in the backlog: https://trello.com/c/L7Kokob5
+
+Thanks for the report!",1405960431,PHID-USER-37czexl6ekrvcmp2tyqq,False,PHID-TASK-dqhh6futiytkca6um27i,task_subcomment,NA
+VisualEditor:  No Language selected in the Language Selector shows “$1”,"Screenshot
+
+Steps-
+1> Select Language form the Style text drop down.
+2>In the Language Selector dialog delete the two-letter code. Press done.
+3> Now type in some text in the editor, notice that beside the Language icon there is “$1” in the tootltip. See Screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14154}",1405639620,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-73pt5ehjfcwtumxwpuww,task_description,resolved
+VisualEditor:  No Language selected in the Language Selector shows “$1”,Fixed as a side effect of https://gerrit.wikimedia.org/r/#/c/160098/,1414136569,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-73pt5ehjfcwtumxwpuww,task_subcomment,NA
+VisualEditor:  No Language selected in the Language Selector shows “$1”,"Yes, happening in Betalabs as well.",1405642206,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-73pt5ehjfcwtumxwpuww,task_subcomment,NA
+VisualEditor:  No Language selected in the Language Selector shows “$1”,Tested on test2.,1405639745,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-73pt5ehjfcwtumxwpuww,task_subcomment,NA
+can't search image when inserting media in private wiki,"**Author:** `Coiby.Xu`
+
+**Description:**
+I'm testing VisualEditor on 1.23.1. Everything is OK except for inserting an image. When you insert media, you can't use search function. The error message is 'error"":{""code"":""readapidenied"",""info"":""You need read permission to use this module""}'. However if I set  $wgGroupPermissions['*']['read'] = true, the pictures will be shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405582980,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hnf7dr4pfcowjzfzszvb,task_description,resolved
+can't search image when inserting media in private wiki,"I think this is bug 64822.
+
+*** This bug has been marked as a duplicate of bug 64822 ***",1406584368,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hnf7dr4pfcowjzfzszvb,task_subcomment,NA
+can't search image when inserting media in private wiki,Confirmed on officewiki,1406314983,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hnf7dr4pfcowjzfzszvb,task_subcomment,NA
+can't search image when inserting media in private wiki,"I can confirm this issue. The problem is related to the use of the parameter 'callback=jQuery...' in the api call. 
+
+According to https://www.mediawiki.org/wiki/API:Data_formats#Callback_restrictions, when callback mode is used clients are treated as anonymous users, even after logging in. Is callback mode strictly necessary?",1405967872,PHID-USER-wz5bw3q6zykhqbbeohzq,False,PHID-TASK-hnf7dr4pfcowjzfzszvb,task_subcomment,NA
+VisualEditor: Blank link inspector UI appears when trying to open it inside the Media Settings while selecting another image in the caption,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page and insert an image
+2.Insert another image inside it
+3.Select the image inside and try to open link inspector
+
+Observed Result;
+The link inspector appears without any UI'
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14529}",1405550460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fsbewl22leh75q5wxi4m,task_description,resolved
+VisualEditor: Blank link inspector UI appears when trying to open it inside the Media Settings while selecting another image in the caption,"The inspector now ""works"", but due to bug 72431 immediately closes, AFAICT. Nominally FIXED.",1416342840,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fsbewl22leh75q5wxi4m,task_subcomment,NA
+"VisualEditor: Select text, type = garbled, repeated text + snowman on el.wp","See https://el.wikipedia.org/w/index.php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82%3AElitre_%28WMF%29%2Fsandbox&diff=4757904&oldid=4757901 .
+Replace one or more words with ""Foobar"" (that is, highlight the word(s), then type Foobar). Works once, works twice, then the third time corruption happens and le wild snowman appears.
+Must say that I only managed to reproduce that in my sandbox, which features content from https://el.wikipedia.org/wiki/%CE%95%CF%80%CE%B9%CF%84%CF%8C%CE%BA%CE%B9%CE%BF , and in this article page.
+It happens in Chrome and Firefox, tested under Windows 7, Ubuntu 13.10 and OS X 10.8.
+During an attempt to reproduce, VE also suppressed existing nowiki tags: https://el.wikipedia.org/w/index.php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82:P.a.a/%CF%80%CF%81%CF%8C%CF%87%CE%B5%CE%B9%CF%81%CE%BF&diff=next&oldid=4757859 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405545780,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-bnj7f5cnhoxzikonjjvj,task_description,resolved
+"VisualEditor: Select text, type = garbled, repeated text + snowman on el.wp","I think the Πηγή template is the issue here; down-page of the template everything breaks, up-page it works. That means it's almost certainly a duplicate of bug 67992.
+
+*** This bug has been marked as a duplicate of bug 67992 ***",1406598882,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bnj7f5cnhoxzikonjjvj,task_subcomment,NA
+"VisualEditor: Select text, type = garbled, repeated text + snowman on el.wp","I found another, smaller, text that manifests this bug https://el.wikipedia.org/w/index.php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82:P.a.a/%CF%80%CF%81%CF%8C%CF%87%CE%B5%CE%B9%CF%81%CE%BF&oldid=4767252",1406051395,PHID-USER-sbwcezpm5yhfcbntreum,True,PHID-TASK-bnj7f5cnhoxzikonjjvj,task_subcomment,NA
+"VisualEditor: Select text, type = garbled, repeated text + snowman on el.wp","(In reply to Elitre from comment #0)
+> See
+> https://el.wikipedia.org/w/index.
+> php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82%3AElitre_%28WMF%29%2Fsan
+> dbox&diff=4757904&oldid=4757901 .
+> Replace one or more words with ""Foobar"" (that is, highlight the word(s),
+> then type Foobar). Works once, works twice, then the third time corruption
+> happens and le wild snowman appears.
+> Must say that I only managed to reproduce that in my sandbox, which features
+> content from
+> https://el.wikipedia.org/wiki/
+> %CE%95%CF%80%CE%B9%CF%84%CF%8C%CE%BA%CE%B9%CE%BF , and in this article page.
+> It happens in Chrome and Firefox, tested under Windows 7, Ubuntu 13.10 and
+> OS X 10.8.
+> During an attempt to reproduce, VE also suppressed existing nowiki tags:
+> https://el.wikipedia.org/w/index.
+> php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82:P.a.a/
+> %CF%80%CF%81%CF%8C%CF%87%CE%B5%CE%B9%CF%81%CE%BF&diff=next&oldid=4757859 .
+
+The nowiki tags around the percentage signs were added by me, in an effort to eliminate a possible, if remote, cause of interference.",1405546425,PHID-USER-sbwcezpm5yhfcbntreum,True,PHID-TASK-bnj7f5cnhoxzikonjjvj,task_subcomment,NA
+VisualEditor: Easy way to reproduce a weird behavior with the link tool,"Take a page like https://en.wikipedia.org/wiki/Heliozela_rutilella?veaction=edit (that is, starting with a template, so there's some space above the first line of the article).
+Clicking on the link tool and pressing ESC will automatically make the first word (Heliozela) a link to the Heliozela article. 
+Click on the up arrow, then click on the link tool again, and press ESC. You get the word Heliozela again (with no links).
+
+**See Also**:
+T70101",1405518780,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-4gkkbuwk3jlg27h57c3x,task_description,resolved
+VisualEditor: Easy way to reproduce a weird behavior with the link tool,Serious comment: Seems to be fixed now. Closing.,1434390715,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-4gkkbuwk3jlg27h57c3x,task_subcomment,NA
+VisualEditor: Easy way to reproduce a weird behavior with the link tool,Test comment! Hi mom!,1430243737,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-4gkkbuwk3jlg27h57c3x,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"Load VE. Say ""Foobar"" is the first word on the page.
+If you click on the link tool, by mistake or not, without selecting anything before, Foobar will automatically become a link to the Foobar page (it doesn't help that pressing ESC doesn't abort the action, the link gets applied anyway, as we know).
+NicoV noticed this in several French articles, where you can quite tell links happened ""by mistake"" since the first word is an article, ""le"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68102",1405517940,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_description,declined
+VisualEditor: Don't allow a linking action if no text was highlighted before,"Ah. Bug 69407. Alright, thanks.",1407778944,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"I hereby distance myself from that guy who wrote ""enhancement"" in comment 8, as differing interpretations and judgements of that term might trigger ""lies"". Please feel free to argument why not supporting Esc is a ""serious bug"" in a separate, non-enhancement request if you wish so. Thank you.",1407778842,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"**ronnirubin** wrote:
+
+(In reply to Andre Klapper from comment #8)
+> (In reply to Arthur Rubin from comment #7)
+> > I don't know how to reopen this.
+> 
+> You were asked to not reopen this, but to file a new and separate
+> enhancement request for the Esc behavior if you wish so.
+
+So, you want me to lie and call it an ""enhancement request"" rather than a bug fix.  _That_, I won't do.  I'll still call it a bug fix, and apparently a serious one.",1407776541,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"(In reply to Arthur Rubin from comment #7)
+> I don't know how to reopen this.
+
+You were asked to not reopen this, but to file a new and separate enhancement request for the Esc behavior if you wish so.",1407775711,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"**ronnirubin** wrote:
+
+I don't know how to reopen this.  As an Admin on en.Wikipedia, I can say that having ""Escape"" _not_ close the box and take none of the actions indicated in the box is a deal-stopper for me.  I will argue against VE be made default if this isn't fixed.",1407772821,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,Please don't edit war on Bugzilla. Create a new bug about an actual issue if you wish.,1407699357,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"Well, give me one example of a software behaving like that: in any software I know, when you click on a button that open a dialog, if you cancel the dialog then no action is done.
+
+The current behavior is probably the reason of many links created in frwiki to pages ""Le"", ""La"", ""Les"", ... (all created by VE) which we have to fix on a regular basis. And we obviously miss all the other links created by mistake.
+
+Please, change the current behavior, so that Esc key behaves as in any normal software.",1407697489,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"(In reply to NicoV from comment #2)
+> But the main problem with this is that the ESC key is not working correctly
+> (it should cancel the action and not silently validate it). Do you plan to
+> do something to make the ESC key work as it works in every other application
+> ?
+
+You are mistaken. The Escape key is doing exactly what users expect; it closes the window. The user clicking the link button – not the closing the link editor window – is what makes the link.",1407697132,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,Please read my comment: the main problem is ESC key not working at all as could be expected by any user.,1407692120,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,"I was the one reporting the issue with words like ""le"" being made into internal links by mistake on frwiki. I think the behavior of automatically selecting the entire word when make an internal link should be kept (it's probably causing less issues than it's avoiding).
+
+But the main problem with this is that the ESC key is not working correctly (it should cancel the action and not silently validate it). Do you plan to do something to make the ESC key work as it works in every other application ?",1405575017,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+VisualEditor: Don't allow a linking action if no text was highlighted before,This is explicitly a feature that was requested (years ago now). People clicking buttons and not paying attention to what they're doing seems more like a social issue than a software bug.,1405533552,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-huk6uolixsrw4vl5idv3,task_subcomment,NA
+performance degradation with new UI,"Seen on beta labs as 15 July: 
+
+Upon loading a simple page such as http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+The contentEditable surface used to appear reliably in under ten seconds.  Now I am seeing 10+ second load times for about one page load of every three.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405466760,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-hfno6mirclxxp4wamoqs,task_description,invalid
+performance degradation with new UI,"
+I reported this poorly, needs more research.",1405467205,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-hfno6mirclxxp4wamoqs,task_subcomment,NA
+Opens wrong page in Edit source after making change in VE in old version of artcle,"*open old version of artcle
+*press tab Edit
+*make some changes
+*press tab Edit source
+*in warnng window press ""Discard changes""
+->will open this page https://en.wikipedia.org/w/index.php?action=edit&veswitched=1
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 8.1
+**Platform**: PC",1405437840,PHID-USER-5joeladhczukimiv4rwl,False,PHID-TASK-c57y4fdc3ukcmw6umira,task_description,declined
+Opens wrong page in Edit source after making change in VE in old version of artcle,"(In reply to James Forrester from comment #1)
+> This is consistent with how the wikitext editor works – on an old page, the
+> ""Read"" link goes to the latest (not old) version of the page. VisualEditor
+> deliberately does the same as that.
+
+
+May be possible change link for tab Editsource while user work in VE and do the same thing that do [Ξ]->""Switch to source code"". This enough intuitive behavior.",1405448944,PHID-USER-5joeladhczukimiv4rwl,False,PHID-TASK-c57y4fdc3ukcmw6umira,task_subcomment,NA
+Opens wrong page in Edit source after making change in VE in old version of artcle,"This is consistent with how the wikitext editor works – on an old page, the ""Read"" link goes to the latest (not old) version of the page. VisualEditor deliberately does the same as that.",1405448377,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c57y4fdc3ukcmw6umira,task_subcomment,NA
+"VisualEditor: switching to ""Default"" image size in image inspector does not make Apply Changes button active","in order to save this change a user must make another change in the dialog in addition to setting the image size to default
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405390800,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-vfapjnaswl6rsvgrurvh,task_description,resolved
+"VisualEditor: switching to ""Default"" image size in image inspector does not make Apply Changes button active","Yeah, dupe of bug 67684.
+
+*** This bug has been marked as a duplicate of bug 67684 ***",1406427644,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vfapjnaswl6rsvgrurvh,task_subcomment,NA
+"VisualEditor: switching to ""Default"" image size in image inspector does not make Apply Changes button active",Has this bug been fixed? It works fine for me.,1406312751,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-vfapjnaswl6rsvgrurvh,task_subcomment,NA
+VisualEditor: required parameter not showing,"**Author:** `manueltassi91`
+
+**Description:**
+In itwiki, we've noticed that when including [it.wikipedia.org/wiki/Template:A] in a page using VE doesn't show all required parameters, but just one. In fact, with VE there should be three required parameters (""Motivazione"", ""Data di inserimento"" ""Argomento""), but in the dialog only ""Motivazione"" is shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405346700,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_description,declined
+VisualEditor: required parameter not showing,I wonder if it was just waiting for someone to null edit the template page. I guess this bug is WFM.,1406314288,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_subcomment,NA
+VisualEditor: required parameter not showing,"**manueltassi91** wrote:
+
+No. At the moment the problem seems to be solved.",1406312725,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_subcomment,NA
+VisualEditor: required parameter not showing,Is this still valid? I just checked and the three required parameters are showing.,1406312461,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_subcomment,NA
+VisualEditor: required parameter not showing,"Possibly a dupe of bug 50747, but still: if a parameter is mandatory, I need to 1) know it is, 2) know I need to add it or the template will be broken. I don't understand why we 1) aren't making the user aware that such parameters exist, 2) are even hiding them, dooming templates to be incomplete and users to be confused.",1405348327,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-r6jtpcdwjxmbzke3wazy,task_subcomment,NA
+VisualEditor: In [[Pristina International Airport]] the backspace key makes the cursor jump further back,"I couldn't reproduce this in any other article, but it may happen elsewhere:
+
+1. Edit https://en.wikipedia.org/wiki/Pristina_International_Airport (I tested in this version: https://en.wikipedia.org/w/index.php?title=Pristina_International_Airport&oldid=615886404 ).
+
+2. Put the caret in the first paragraph, in the word ""handles"".
+
+3. Press Backspace.
+
+Expected: The caret moves one character and deletes it.
+Observed: The caret deletes one character before it, but moves back 26 characers to the beginning of the word ""international"".
+
+Happened to me in Firefox and Chrome on Fedora.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405201260,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-65is3y3rbqummqu5reci,task_description,resolved
+VisualEditor: In [[Pristina International Airport]] the backspace key makes the cursor jump further back,"Aha, this was a dupe of bug 67862. Sorry!
+
+*** This bug has been marked as a duplicate of bug 67862 ***",1406319801,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-65is3y3rbqummqu5reci,task_subcomment,NA
+VisualEditor: In [[Pristina International Airport]] the backspace key makes the cursor jump further back,I guess it was fixed at some point. Thanks for testing.,1406316186,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-65is3y3rbqummqu5reci,task_subcomment,NA
+VisualEditor: In [[Pristina International Airport]] the backspace key makes the cursor jump further back,Hmm... Can't reproduce on the latest version with Chrome.,1406315955,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-65is3y3rbqummqu5reci,task_subcomment,NA
+A menu item of VisusalEditor in Ukrainian Wikipedia has been changed by mistake.,"**Author:** `002soym`
+
+**Description:**
+Intention:
+To edit a wiki code
+
+Steps to Reproduce:
+A menu item of VisusalEditor in Ukrainian Wikipedia has been changed by mistake. Now we have instead of the correct menu item '''Редагувати код''' (Edit code) the absolutely incorrect '''Править викитекст'''. It's not even in Ukrainian.
+[https://uk.wikipedia.org/wiki/MediaWiki:Visualeditor-ca-editsource shows] the correct label here.
+
+Actual Results:  
+menu item '''Править викитекст''' 
+
+Expected Results:  
+menu item '''Редагувати код''' (Edit code)
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://uk.wikipedia.org/wiki/%D0%92%D1%96%D0%BA%D1%96%D0%BF%D0%B5%D0%B4%D1%96%D1%8F",1405130040,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-qcsqvh62dwh2bjvi4jg5,task_description,resolved
+A menu item of VisusalEditor in Ukrainian Wikipedia has been changed by mistake.,"As I replied on wiki to you, this is bug 67805
+
+*** This bug has been marked as a duplicate of bug 67805 ***",1405130110,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qcsqvh62dwh2bjvi4jg5,task_subcomment,NA
+Option to use VisualEditor not showing up on non-enwiki projects,"In production in beta. Steps to repro:
+
+1. Go to French, Polish, or Russian Wikipedia (where VE should be the default editing experience). 
+2. Opt into beta, log in, and attempt to edit a page.
+
+Expected: I am taken to VE editing mode, since VE is the default editing experience on those projects.
+
+Actual: I am taken to wikitext editing. Furthermore, I don't have the option to switch to VE editing in the edit window (the cog that shows me the drop-down menu is missing). 
+
+Also observed on Portuguese and Spanish Wikipedia. It seems to be everywhere except enwiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405115820,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-7qcly6qjxshoqdfuzt3e,task_description,invalid
+Option to use VisualEditor not showing up on non-enwiki projects,"Derp, helps to enable beta again after you clear your cookies for testing purposes :)",1405116083,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-7qcly6qjxshoqdfuzt3e,task_subcomment,NA
+Option to use VisualEditor not showing up on non-enwiki projects,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/EShXsKmu",1405116019,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7qcly6qjxshoqdfuzt3e,task_subcomment,NA
+VisualEditor: new autoadded reflist does not display when in VE edit mode,"new reflist behavior adds in the reflist to the saved/rendered display like TOC but when in VE edit mode the reflist is not displayed, which is confusing, especially when user is adding references
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405104840,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-pk3xxotbd2cygxbic2dv,task_description,duplicate
+VisualEditor: new autoadded reflist does not display when in VE edit mode,What is the problem here on the Parsoid end?,1408573896,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-pk3xxotbd2cygxbic2dv,task_subcomment,NA
+VisualEditor: new autoadded reflist does not display when in VE edit mode,I guess this refers to https://gerrit.wikimedia.org/r/#/c/141583/ / bug 66860.,1405105577,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-pk3xxotbd2cygxbic2dv,task_subcomment,NA
+"VisualEditor: Table cell templates are editable, but their re-rendering is broken","Screenshot
+
+Table cell templates are editable, but their re-rendering is broken.
+
+Example: try modifying any of the table cell templates at https://nl.wikipedia.org/wiki/Gebruiker:Ad_Huikeshoven/jh?uselang=en&veaction=edit#Prestatietabel
+
+They can be edited, such an edit can be saved and results in correct wikitext, but is rendered broken (the markup is rendered as text, instead of creating a table cell).
+
+(Found when playing with bug 67850.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://nl.wikipedia.org/wiki/Gebruiker:Ad_Huikeshoven/jh?uselang=en&veaction=edit#Prestatietabel
+
+**Attached**: {F14539}",1405090260,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-unakgbnnnqhghsth6f2x,task_description,duplicate
+"VisualEditor: Table cell templates are editable, but their re-rendering is broken","This is because we don't (can't) send context right now when asking for the template to be re-rendered – bug 51146 is the original report of this issue. Merging. (Boo.)
+
+*** This bug has been marked as a duplicate of bug 51146 ***",1405107160,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-unakgbnnnqhghsth6f2x,task_subcomment,NA
+VisualEditor: Pawns and reverse typing,"Reported on fr.wp. Verified so far in Win 7 (Chrome and FF). 
+
+You can use this page https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_%28WMF%29/Prove2&oldid=105329509 to reproduce.
+Steps:
+
+    1) Place the cursor immediatly after ""croisières"", before the non-breaking space.
+    2) Add a space. This space is added after the cursor.
+    3) Press Right Arrow then Left Arrow to make the cursor move, but it is finally at the same place.
+    4) Add a space : the pawn appears in the link.
+    5) Again right arrow, then add another space : a second pawn appears after the link.
+    6) If you try to type text after the last pawn, only a pawns appears. No text.
+
+    To have text written from right to left :
+    1) Place the cursor immediatly after ""croisières"", before the non-breaking space.
+    2) Add a space. This space is added after the cursor.
+    3) Press Right Arrow to make the cursor move.
+    4) Add a space : the pawn appears.
+    5) Again right arrow, then add another space (so efter the colon) : a second pawn appears.
+    6) Left arrow twice (cursor before the colon) and type text : it's written from right to left.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404992460,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-oxgjzrxg7p6u7stnpafd,task_description,resolved
+VisualEditor: Pawns and reverse typing,"
+
+*** This bug has been marked as a duplicate of bug 68151 ***",1406341653,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oxgjzrxg7p6u7stnpafd,task_subcomment,NA
+"VisualEditor:  Cite tool's dropdown menu is not displaying (it's ""underneath"" the toolbar)","Cite menu is inaccessible
+
+The dropdown menu for the Cite tool is not displaying correctly for me in Safari 6.1.4.  
+
+The screenshots show two different font sizes/resolutions.  This isn't consistent for me.  I zoomed in before it happened the first time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14279}",1404928980,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-y32jhfrfnhzhio3fteie,task_description,resolved
+"VisualEditor:  Cite tool's dropdown menu is not displaying (it's ""underneath"" the toolbar)","This sounds like bug 64388 which is very troubling. :-(
+
+*** This bug has been marked as a duplicate of bug 64388 ***",1404965618,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-y32jhfrfnhzhio3fteie,task_subcomment,NA
+"VisualEditor:  Cite tool's dropdown menu is not displaying (it's ""underneath"" the toolbar)","Created attachment 15883
+What happens is you have zoomed in
+
+**Attached**: {F14282}",1404929051,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-y32jhfrfnhzhio3fteie,task_subcomment,NA
+VisualEditor: Support non-image media (tracking),"We currently don't. We should.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1404850380,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-aanmrkvizmwbalha5bbk,task_description,duplicate
+VisualEditor: Support non-image media (tracking),"
+
+*** This bug has been marked as a duplicate of bug 67690 ***",1404851265,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-aanmrkvizmwbalha5bbk,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","Steps to reproduce:
+
+1.Open a page with Mobile VE with desktop safari or iOS safari
+2.Create a link to a new page and save the page
+3.Go to that new page that you just created link to
+4.Edit that page and save it
+
+Observed Result:
+
+It will redirect you to the page that you started with at step1
+
+Environment:Betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60848
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65041
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69559",1404775860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_description,resolved
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page",Bug is no longer reproducible due to https://gerrit.wikimedia.org/r/#/c/164131/,1412632719,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page",I think this bug is actually the same as bug 60848 and bug 65041. Bug 60848 was closed by Jon as WONTFIX. Should we reopen it? Bug 65041 is just another specific case of the underlying issue.,1405984487,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","The issue here is that we're adding a hash to the URL when we launch the editor, and then doing history.back() after it's saved to restore the original URL. The only problem is that redlinks link directly to the editor, so once you're done, going back takes you to the previous article. Linking directly to the editor is the correct behavior (it's the same as is done on desktop). The problem is the  history.back() hack (IMO).",1405979859,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page",Reproducing this bug is currently blocked by bug 68249.,1405978411,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","Just checked with Rumana and it's actually an issue in beta mode too.
+So not necessarily related to ajax page loading/link hijacking :)",1404840427,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","OT: I notice you are testing VisualEditor in alpha since the bug is assigned to alpha. Please don't.... Please use beta which is more stable and will help us filter out bugs in VE vs bugs in mobile.
+
+Can you confirm the above problem happens in the alpha mode or is it beta mode (it does indeed sound like alpha)?",1404838690,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page",Sounds like another lazy-loading bug.,1404778093,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+"Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/wdlVRRim",1404777020,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cwbxz7kcqiotdqiikk2n,task_subcomment,NA
+VisualEditor: A pawn appears while trying to type something to the the left/right of a reference note in Firefox,"Screenshot
+
+Steps to reproduce:
+
+1.Select a reference note in VE with firefox
+2.Press right/left
+3.Type something
+
+
+Observed Result:
+A pawn appears instead of the text
+
+
+See the screenshot attached
+
+Environment:Production (en.wiki)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14615}",1404763200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fz7qljplu3bbp45jxtbz,task_description,resolved
+VisualEditor: A pawn appears while trying to type something to the the left/right of a reference note in Firefox,"Boo.
+
+*** This bug has been marked as a duplicate of bug 58315 ***",1404763355,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fz7qljplu3bbp45jxtbz,task_subcomment,NA
+VisualEditor: Clear styling does not work when the cursor is the middle of a text but de-selects the option from style menu,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make a text Bold
+3.Now place your cursor somewhere in the middle of that text
+4.Select the option ""Clear Styling"" from style menu
+
+
+Observed Result:
+The text is still styled as Bold, however the highlight on Bold option in style menu is not anymore there.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14613}",1404762480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-42zqimydtpfzutihf66c,task_description,declined
+VisualEditor: Clear styling does not work when the cursor is the middle of a text but de-selects the option from style menu,"This is intentional; ""clear styling"" without a selection applies to the pre-annotation stack.",1404762894,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-42zqimydtpfzutihf66c,task_subcomment,NA
+Allow users to disable VE in their preferences on otrswiki,"RD asked me to file this bug for him.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404687060,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-jmmp4zdhs654ea55j6sa,task_description,invalid
+Allow users to disable VE in their preferences on otrswiki,"Hmm, I guess ""Temporarily disable VisualEditor while it is in beta"" works. Missed that.",1404688768,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-jmmp4zdhs654ea55j6sa,task_subcomment,NA
+Allow users to disable VE in their preferences on otrswiki,"I am the RD to which Lego refers to. ;-)
+
+Rather than creating a css hack to hide the effects of VE, it should be an option somewhere in user preferences to ""disable"" VE.  The default can be set to having VE enabled.
+
+I am an OTRS administrator.  Some were originally under the impression that this was going to be the case but as of now there is no way to opt-out other than personal scripts.",1404687301,PHID-USER-vwkldpcvthnpctszjph7,False,PHID-TASK-jmmp4zdhs654ea55j6sa,task_subcomment,NA
+VisualEditor: Link annotation gets cut off when label contains linktrail end characters,"Screen recording of bug
+
+1. Edit page with a link is applied to multiple words in sequence.
+   such as ""QUnit - Foo bar baz"".
+2. Select part of it (e.g. ""Foo bar baz"")
+3. Type something new (e.g. ""Quux"")
+
+Expected:
+
+Quux replaces ""Foo bar baz"" and is a link as well.
+
+Actual:
+
+The text is removed, the link now ends at ""-"" and the inserted text ""Quux"" is just plain unlinked text.
+
+This might have to do with linktrail processing and the operation happening as separate delete/insert.
+
+
+Video: http://cl.ly/2K1q1A471G2N
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14240}",1404349800,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tdor3tpvb3ykeaupjgx6,task_description,declined
+VisualEditor: Link annotation gets cut off when label contains linktrail end characters,"(In reply to This, that and the other from comment #2)
+> (In reply to James Forrester from comment #1)
+> > This is intentional behaviour.
+> 
+> Doesn't it strike you as something a user may very legitimately and
+> intuitively want to accomplish?
+
+Yes. We spent months discussing this, looking at dozens of different rich editors' behaviours. That's why I'm reasonably confident that the answer is ""tough"".",1404356644,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tdor3tpvb3ykeaupjgx6,task_subcomment,NA
+VisualEditor: Link annotation gets cut off when label contains linktrail end characters,"(In reply to James Forrester from comment #1)
+> This is intentional behaviour.
+
+Doesn't it strike you as something a user may very legitimately and intuitively want to accomplish?",1404354735,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-tdor3tpvb3ykeaupjgx6,task_subcomment,NA
+VisualEditor: Link annotation gets cut off when label contains linktrail end characters,"You've failed to spot the key part of this – you have to select *to or past the end of the link*.
+
+Selections from inside a whitespace-terminated annotation to outside it which replace into it with a whitespace character will terminate it. Selections from inside said annotation to another place inside it (in your example, ""Foo bar ba"" but not ""Foo bar baz"") don't.
+
+This is intentional behaviour.",1404353692,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tdor3tpvb3ykeaupjgx6,task_subcomment,NA
+VisualEditor: Link inspector should indicate link target when applied via keyboard shortcut,"Screen recording of bug
+
+1. Select text
+2. cmd+K (Mac) to apply a link annotation
+
+Expected:
+
+Either it shows page titles with a default selection (e.g. a link to the exact link text), or only shows suggestions and require I pick one.
+
+Actual:
+
+Becomes link to the exact link text but with no way of knowing that, nor with an intuitive way to select a different target (see attached video).
+
+http://cl.ly/3P2P2E1a1w1A
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14235}",1404349500,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zmkykyh2tvcwalgnx52u,task_description,resolved
+VisualEditor: Link inspector should indicate link target when applied via keyboard shortcut,"The current link inspector solved this bug. To clarify, as seen in the video, the problem was that the selection menu did not open by default (required an additional needless click/focus). Leaving the user in a confused state.
+
+This has nothing to do with what the most common use case is. We still link to the target by default. But we now show the other options so that the user knows that it was actually turned into a link. Not just a pre-filled text box waiting for a user action. This made the most common use case more intuitive.",1433344252,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zmkykyh2tvcwalgnx52u,task_subcomment,NA
+VisualEditor: Link inspector should indicate link target when applied via keyboard shortcut,"No. We chose to not show this as the most common case is making an internal link to the term you've selected, and we wanted this to be as painless as possible.",1404353268,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zmkykyh2tvcwalgnx52u,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**Author:** `jazeckel`
+
+**Description:**
+wiki debug log for navigating to and attempting to edit a page
+
+I am attempting to configure the VisualEditor REL1_23 to run with my MediaWiki instance.  I am using MediaWiki 1.23 and it is a private wiki.  It's served by IIS on Windows Server 2012 R2.  I am able to create a very simple page using it, although it runs slowly.  However, any attempt to edit the page -- even a page containing only one simple sentence -- times out with Parsoid.  I ran all of the Parsoid tests following installation and they all passed, and from Parsoid's test webpage (localhost:8000) I was able to run those tests and they succeed quickly.  However, I can't edit any pages of my wiki.  This is the output from the Parsoid service during an edit attempt:
+
+[warning/api][null/Test] Failed API request, 8 retries remaining.
+[info][localhost/Test] starting parsing
+[info][localhost/Test?oldid=834] completed parsing in 45006 ms
+
+The completed parsing line occurs after I click cancel on the prompt telling me the request timed out.  When I had the timeout set to 60s, I would see ""8 tries remaining"" and then ""7 tries remaining"" before it timed out (I have since changed the timeout to 45s).  The content of the page in this example is simply ""this is a visual editor test.""
+
+Relevant information:
+- Windows Server 2012 R2
+- IIS v8.5.9600.16384
+- 32-bit node.js
+- Parsoid on port 8000
+- Browser used is Chrome 35.0.1916.153 m
+- MediaWiki 1.23, set to require log in to view/edit
+- same problem in all skins that VisualEditor runs on
+
+A debug log from MediaWiki is attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: other
+**Platform**: PC
+
+**Attached**: {F14490}",1404148260,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_description,resolved
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","(In reply to C. Scott Ananian from comment #16)
+> gwicke: we should probably not be timing out if the api request returns an
+> error.  Maybe we should look into this?
+
+My understanding of the code is that we only retry when getting an error object, but not if we got an HTTP status code. There's either no proper HTTP status returned by this particular wiki setup, or the request library returns an error when it should not. 
+
+I just tested this locally, and there's no retrying on unauthorized requests. This means that this is probably an IIS-specific issue, where IIS does not return a proper HTTP status on authentication errors.",1404344823,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Okay, I finally have it working.  I think this boils down to configuration errors so the instructions for setup for Parsoid and the VisualEditor should probably be clarified, but also it would be nice to improve the error messaging so that a permissions error doesn't cause a timeout.
+
+Here's what I did to fix it:
+- made the key in parsoidConfig.setInterwiki equal to $wgVisualEditorParsoidPrefix, both of which I set to ""auc"" (rather than ""localhost/auc"")
+- set $wgSessionsInObjectCache = true (this is the line that didn't seem to have any effect before, but that was probably because the rest was not configured right)
+- set $wgVisualEditorParsoidForwardCookies = true (I already had that one set)
+
+Thanks for your help!",1404321623,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+FWIW if I go to http://localhost:8000/auc/Main_Page from a browser where my login credentials are cached, the content will load.  If I'm logged out of the wiki in that browser, I will get an error.",1404242245,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+(In reply to C. Scott Ananian from comment #16)
+> I'm guessing that one of these is prohibiting anonymous access to the API. 
+> I bet it's not actually the case that it works when you use the server name,
+> I bet that somehow you're actually accessing the wrong wiki in that case. 
+> I'm not a mediawiki permissions expert though, so take what I say with a
+> grain of salt.
+
+Yes, this is exactly what happens -- it loads the content from the wrong wiki.
+
+> If you are mucking with permissions, this link may be useful:
+> https://www.mediawiki.org/wiki/Extension:
+> VisualEditor#Linking_with_Parsoid_in_private_wikis
+
+I had already set $wgVisualEditorParsoidForwardCookies = true as instructed in that portion.  I didn't uncomment the line about session cacheing because it didn't seem to make a difference.
+
+> Yes, the 'localhost' part here has to match the string you set 
+> $wgVisualEditorParsoidPrefix to.
+
+Okay, thanks for letting me know that.  It wasn't clear from the installation/configuration instructions.
+
+(In reply to C. Scott Ananian from comment #18)
+> In particular, one running parsoid can service multiple different
+> mediawikis.  They are distinguished by the $wgVisualEditorParsoidPrefix and
+> corresponding localsettings.js.  For example, you should be able to visit
+> your running parsoid instance on http://localhost:8080 (or whatever port you
+> used) and then get different pages for:
+> 
+> http://localhost:8080/enwiki/Main_Page (links to wikipedia using 'enwiki'
+> prefix)
+> http://localhost:8080/localhost/Main_Page
+> http://localhost:8080/foo/Main_Page
+> 
+> given
+> 
+> parsoidConfig.setInterwiki( 'localhost', 'some api endpoint' );
+> parsoidConfig.setInterwiki( 'foo', 'some different api endpoint' );
+> 
+> Our docs could probably explain this better.  Suggestions welcome.
+
+Thanks, that explains some more.  I have set them both to ""auc"" and now it's not loading data from the wrong wiki anymore, but it's timing out again.  Perhaps there is some other detail of configuration for a private wiki that is causing a problem.  Can I go into Parsoid's code and hard code a username and password and make a private account just for Parsoid to resolve this?",1404242055,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","In particular, one running parsoid can service multiple different mediawikis.  They are distinguished by the $wgVisualEditorParsoidPrefix and corresponding localsettings.js.  For example, you should be able to visit your running parsoid instance on http://localhost:8080 (or whatever port you used) and then get different pages for:
+
+http://localhost:8080/enwiki/Main_Page (links to wikipedia using 'enwiki' prefix)
+http://localhost:8080/localhost/Main_Page
+http://localhost:8080/foo/Main_Page
+
+given
+
+parsoidConfig.setInterwiki( 'localhost', 'some api endpoint' );
+parsoidConfig.setInterwiki( 'foo', 'some different api endpoint' );
+
+Our docs could probably explain this better.  Suggestions welcome.",1404241663,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","(In reply to jazeckel from comment #15)
+> Also, if I comment out the entire parsoidConfig.setInterwiki line in my
+> localsettings.js, it loads the visual editor but with the wrong wiki's
+> content.  It appears that having ""localhost"" as the key on that line will
+> cause it to fail regardless, and if I change ""localhost"" to anything else it
+> loads the wrong content.  For example, I could make the line:
+> parsoidConfig.setInterwiki( 'foo', 'http://localhost/auc/wiki/api.php' );
+> 
+> and it will load the editor but with the wrong content.
+
+Yes, the 'localhost' part here has to match the string you set $wgVisualEditorParsoidPrefix to.",1404241409,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","(In reply to jazeckel from comment #11)
+> Hmm, so this is kind of interesting.  If I go to the URL but with the server
+> name instead of ""localhost,"" I get what I assume is the correct result -- a
+> big block of key value pairs about locales and such.  If I go to the URL
+> with ""localhost"", I get this: 
+> 
+> {""error"":{""code"":""readapidenied"",""info"":""You need read permission to use
+> this module""}}
+> 
+> I don't see any PHP error logs created though perhaps I am not looking in
+> the right place.
+
+This is generated if the anonymous user doesn't have appropriate permissions to access the API.  In include/DefaultSettings.php there is a group of permissions including:
+
+$wgGroupPermissions['*']['writeapi'] = true;
+
+I'm guessing that one of these is prohibiting anonymous access to the API.  I bet it's not actually the case that it works when you use the server name, I bet that somehow you're actually accessing the wrong wiki in that case.  I'm not a mediawiki permissions expert though, so take what I say with a grain of salt.
+
+If you are mucking with permissions, this link may be useful:
+https://www.mediawiki.org/wiki/Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis
+
+gwicke: we should probably not be timing out if the api request returns an error.  Maybe we should look into this?",1404241346,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Also, if I comment out the entire parsoidConfig.setInterwiki line in my localsettings.js, it loads the visual editor but with the wrong wiki's content.  It appears that having ""localhost"" as the key on that line will cause it to fail regardless, and if I change ""localhost"" to anything else it loads the wrong content.  For example, I could make the line:
+parsoidConfig.setInterwiki( 'foo', 'http://localhost/auc/wiki/api.php' );
+
+and it will load the editor but with the wrong content.",1404241027,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+To clarify, when it succeeds and loads the page from the wrong wiki, the URL I see in the debug output is ""http://localhost/wiki/api.php"" whereas the correct wiki is ""http://localhost/auc/wiki/api.php"", which is as specified in Parsoid's localsettings (although in localsettings it is specified now with servername instead of localhost).",1404240426,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+This is extremely confusing.  Here are the current issues:
+1) I don't understand why changing out localhost for servername should make a difference, considering they are the same machine.
+2) If I change out localhost for servername in parsoid/api/localsettings.js, then when I try to edit the visual editor loads, but it loads with the content of a page from a different wiki that runs on the same server.  Is there a missing database configuration in the Parsoid localsettings?
+3) If I change the wiki/localsettings.js to also use servername instead of localhost, it times out again.",1404240259,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time",It sounds like your configured API URL should actually include the real server name instead of 'localhost'. Could you change the config & verify that this fixes your issue?,1404237866,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Hmm, so this is kind of interesting.  If I go to the URL but with the server name instead of ""localhost,"" I get what I assume is the correct result -- a big block of key value pairs about locales and such.  If I go to the URL with ""localhost"", I get this: 
+
+{""error"":{""code"":""readapidenied"",""info"":""You need read permission to use this module""}}
+
+I don't see any PHP error logs created though perhaps I am not looking in the right place.",1404222602,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","@jazeckel: so, when you visit http://localhost/auc/wiki/api.php?format=json&action=query&meta=siteinfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensiontags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols manually, what happens?  Does anything show up in your PHP server logs?
+
+It sounds like there's something wrong with your wiki's API entrypoint.",1404221407,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Okay, I applied the patch, ran ""node api/server.js"" in the console, then loaded up my test page and clicked edit for the visual editor.  Some time passed with no output, then I got this:
+
+Request 1: http://localhost/auc/wiki/api.php?format=json&action=query&meta=sitei
+nfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensio
+ntags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols: 40016ms
+
+TypeError: Cannot read property 'statusCode' of undefined
+    at Request.cb [as _callback] (D:\public\jazeckel\parsoid\lib\mediawiki.ApiRe
+quest.js:99:49)
+    at self.callback (D:\public\jazeckel\parsoid\node_modules\request\request.js
+:121:22)
+    at Request.emit (events.js:95:17)
+    at null._onTimeout (D:\public\jazeckel\parsoid\node_modules\request\request.
+js:679:12)
+    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
+worker 3128 died (8), restarting.
+ - worker(3040) loading...
+ - worker(3040) ready on :8000
+
+After that I hit my 45 second timeout.",1404217137,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time",It might be easiest just to open lib/mediawiki.ApiRequest.js and apply the patch manually in your favorite editor.  It's only nine lines to copy-and-paste.  The lines with '+' at the front are additions.  The single line with '-' is a removal.,1404160847,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+Can you point me to instructions on how to apply the patch?  I won't be able to do it until tomorrow morning.  Thanks!",1404160479,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","Created attachment 15795
+Debugging patch to dump timing and status code of API requests
+
+Well, we don't have anything built in, but the attached patch is a hack which will dump the request timing and status codes.  If you apply this and then visit (say) http://localhost:8765/enwiki/Main_Page you should get a bunch of output on console about all the upstream API requests which Parsoid is making.  I suspect one or more of them is timing out.
+
+**Attached**: {F14491}",1404158191,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","Ok, I think we can rule out platform slowness.  So now I think my theory in comment 3 is probably on the right track.  Subbu, gwicke: do we have any tools to diagnose timeout issues in API requests made by Parsoid?",1404157376,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","**jazeckel** wrote:
+
+1) node --version reports v0.10.29
+2) running tests/parserTests.js --quiet took 30 seconds, and reported no unexpected results.
+3) it is not a virtual server.  It has 8GB RAM, and here's all the info about the CPU.  Not sure if CPU cache is the cache you wanted to know about or a different cache. 
+
+Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
+Intel64 Family 6 Model 45 Stepping 7, GenuineIntel
+HTT             *       Hyperthreading enabled
+HYPERVISOR      -       Hypervisor is present
+VMX             *       Supports Intel hardware-assisted virtualization
+SVM             -       Supports AMD hardware-assisted virtualization
+EM64T           *       Supports 64-bit mode
+
+SMX             *       Supports Intel trusted execution
+SKINIT          -       Supports AMD SKINIT
+
+NX              *       Supports no-execute page protection
+SMEP            -       Supports Supervisor Mode Execution Prevention
+SMAP            -       Supports Supervisor Mode Access Prevention
+PAGE1GB         *       Supports 1 GB large pages
+PAE             *       Supports > 32-bit physical addresses
+PAT             *       Supports Page Attribute Table
+PSE             *       Supports 4 MB pages
+PSE36           *       Supports > 32-bit address 4 MB pages
+PGE             *       Supports global bit in page tables
+SS              *       Supports bus snooping for cache operations
+VME             *       Supports Virtual-8086 mode
+RDWRFSGSBASE    -       Supports direct GS/FS base access
+
+FPU             *       Implements i387 floating point instructions
+MMX             *       Supports MMX instruction set
+MMXEXT          -       Implements AMD MMX extensions
+3DNOW           -       Supports 3DNow! instructions
+3DNOWEXT        -       Supports 3DNow! extension instructions
+SSE             *       Supports Streaming SIMD Extensions
+SSE2            *       Supports Streaming SIMD Extensions 2
+SSE3            *       Supports Streaming SIMD Extensions 3
+SSSE3           *       Supports Supplemental SIMD Extensions 3
+SSE4a           -       Supports Sreaming SIMDR Extensions 4a
+SSE4.1          *       Supports Streaming SIMD Extensions 4.1
+SSE4.2          *       Supports Streaming SIMD Extensions 4.2
+
+AES             *       Supports AES extensions
+AVX             *       Supports AVX intruction extensions
+FMA             -       Supports FMA extensions using YMM state
+MSR             *       Implements RDMSR/WRMSR instructions
+MTRR            *       Supports Memory Type Range Registers
+XSAVE           *       Supports XSAVE/XRSTOR instructions
+OSXSAVE         *       Supports XSETBV/XGETBV instructions
+RDRAND          -       Supports RDRAND instruction
+RDSEED          -       Supports RDSEED instruction
+
+CMOV            *       Supports CMOVcc instruction
+CLFSH           *       Supports CLFLUSH instruction
+CX8             *       Supports compare and exchange 8-byte instructions
+CX16            *       Supports CMPXCHG16B instruction
+BMI1            -       Supports bit manipulation extensions 1
+BMI2            -       Supports bit manipulation extensions 2
+ADX             -       Supports ADCX/ADOX instructions
+DCA             *       Supports prefetch from memory-mapped device
+F16C            -       Supports half-precision instruction
+FXSR            *       Supports FXSAVE/FXSTOR instructions
+FFXSR           -       Supports optimized FXSAVE/FSRSTOR instruction
+MONITOR         *       Supports MONITOR and MWAIT instructions
+MOVBE           -       Supports MOVBE instruction
+ERMSB           -       Supports Enhanced REP MOVSB/STOSB
+PCLULDQ         *       Supports PCLMULDQ instruction
+POPCNT          *       Supports POPCNT instruction
+LZCNT           -       Supports LZCNT instruction
+SEP             *       Supports fast system call instructions
+LAHF-SAHF       *       Supports LAHF/SAHF instructions in 64-bit mode
+HLE             -       Supports Hardware Lock Elision instructions
+RTM             -       Supports Restricted Transactional Memory instructions
+
+DE              *       Supports I/O breakpoints including CR4.DE
+DTES64          *       Can write history of 64-bit branch addresses
+DS              *       Implements memory-resident debug buffer
+DS-CPL          *       Supports Debug Store feature with CPL
+PCID            *       Supports PCIDs and settable CR4.PCIDE
+INVPCID         -       Supports INVPCID instruction
+PDCM            *       Supports Performance Capabilities MSR
+RDTSCP          *       Supports RDTSCP instruction
+TSC             *       Supports RDTSC instruction
+TSC-DEADLINE    *       Local APIC supports one-shot deadline timer
+TSC-INVARIANT   *       TSC runs at constant rate
+xTPR            *       Supports disabling task priority messages
+
+EIST            *       Supports Enhanced Intel Speedstep
+ACPI            *       Implements MSR for power management
+TM              *       Implements thermal monitor circuitry
+TM2             *       Implements Thermal Monitor 2 control
+APIC            *       Implements software-accessible local APIC
+x2APIC          *       Supports x2APIC
+
+CNXT-ID         -       L1 data cache mode adaptive or BIOS
+
+MCE             *       Supports Machine Check, INT18 and CR4.MCE
+MCA             *       Implements Machine Check Architecture
+PBE             *       Supports use of FERR#/PBE# pin
+
+PSN             -       Implements 96-bit processor serial number
+
+PREFETCHW       *       Supports PREFETCHW instruction
+
+Maximum implemented CPUID leaves: 0000000D (Basic), 80000008 (Extended).
+
+Logical to Physical Processor Map:
+*---  Physical Processor 0
+-*--  Physical Processor 1
+--*-  Physical Processor 2
+---*  Physical Processor 3
+
+Logical Processor to Socket Map:
+****  Socket 0
+
+Logical Processor to NUMA Node Map:
+****  NUMA Node 0
+
+Logical Processor to Cache Map:
+*---  Data Cache          0, Level 1,   32 KB, Assoc   8, LineSize  64
+*---  Instruction Cache   0, Level 1,   32 KB, Assoc   8, LineSize  64
+*---  Unified Cache       0, Level 2,  256 KB, Assoc   8, LineSize  64
+****  Unified Cache       1, Level 3,   10 MB, Assoc  20, LineSize  64
+-*--  Data Cache          1, Level 1,   32 KB, Assoc   8, LineSize  64
+-*--  Instruction Cache   1, Level 1,   32 KB, Assoc   8, LineSize  64
+-*--  Unified Cache       2, Level 2,  256 KB, Assoc   8, LineSize  64
+--*-  Data Cache          2, Level 1,   32 KB, Assoc   8, LineSize  64
+--*-  Instruction Cache   2, Level 1,   32 KB, Assoc   8, LineSize  64
+--*-  Unified Cache       3, Level 2,  256 KB, Assoc   8, LineSize  64
+---*  Data Cache          3, Level 1,   32 KB, Assoc   8, LineSize  64
+---*  Instruction Cache   3, Level 1,   32 KB, Assoc   8, LineSize  64
+---*  Unified Cache       4, Level 2,  256 KB, Assoc   8, LineSize  64
+
+Logical Processor to Group Map:
+****  Group 0",1404157149,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","(Oh, and as a first guess at a diagnosis: it seems suspiciously like one or more of the 30-second timeouts are expiring internal to Parsoid -- parsoid uses internal requests to the api.php of the containing wiki; if those are timing out it is likely that parsoid will take a long time to reply.  But let's double-check the speed of parserTests and underlying node to be sure.)",1404155565,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","As a first step, it would be useful to have some more information on your node.js setup, since we don't habitually test Parsoid on Windows.  Let's start with the output of 'node --version', some hardware information on the server in question (is it a virtual server?  If not, what is the CPU and clock speed and cache size), and how long 'tests/parserTests.js --quiet' takes to run.  With that we should at least narrow down the problem to node performance in general, or some quirk peculiar to how parsoid and mediawiki are interconnected.",1404155449,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time","This is pretty unhelpful, yes. 45 seconds is an insanely long time to parse the page - [[en:Barack Obama]] takes less than 12 seconds to parse, so it sounds like something is wrong there.
+
+Punting to the Parsoid team to ask for advice (and they'll probably need some more information to work out why Parsoid is so slow for you).
+
+If this server is going to be used by a number of people, I'd recommend putting a caching layer in front of Parsoid and using the Parsoid PHP extension to push changes to pages into the cache so they're available instantly.",1404154589,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lahzm5zackfjcqjtlntj,task_subcomment,NA
+Core message reuse,"VisualEditor correctly introduces visualeditor-ca-editsource, visualeditor-ca-editsource-section to change meaning of action=edit links, but it seems to reuse messages such as editsection, monobook-view-edit, vector-view-edit for its own veaction=edit links.
+https://www.mediawiki.org/wiki/Localisation#Avoid_message_reuse
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404045240,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-m24wzue25r3tbqzzunue,task_description,declined
+Core message reuse,"Change 147737 abandoned by Jforrester:
+Don't steal core's 'edit', 'create', 'editsection' by default
+
+Reason:
+Per discussion.
+
+https://gerrit.wikimedia.org/r/147737",1408990765,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"(In reply to Robin Pepermans (SPQRobin) from comment #4)
+> having yet another message and consequently having only
+> few translations.
+
+No such risk in my proposal.",1405779038,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"Change 147737 had a related patch set uploaded by Nemo bis:
+Don't steal core's 'edit', 'create', 'editsection' by default
+
+https://gerrit.wikimedia.org/r/147737",1405778351,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"(In reply to Nemo from comment #3)
+> How is linking veaction=edit not a different context than action=edit?
+
+They are on the same location and for the same function (i.e. editing). There is only a slight difference, i.e. in core it uses the normal editor while in VisualEditor obviously the visual editor. In my opinion, this does not weigh against having yet another message and consequently having only few translations. 
+
+Which makes me think, maybe we should have the ability to fall back to another message if a certain (identical but more specific) message is not translated.",1404152021,PHID-USER-th6xijvyee7wqsk7bc67,False,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"(In reply to Robin Pepermans (SPQRobin) from comment #2)
+> Message re-use
+> needs to be avoided when re-using them in a different context.
+
+How is linking veaction=edit not a different context than action=edit?",1404145793,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"I don't see why we would need separate messages for these. As far as I can see, they are used on the same location for the same function, so having separate messages would be unnecessary duplication imho. Message re-use needs to be avoided when re-using them in a different context.",1404145194,PHID-USER-th6xijvyee7wqsk7bc67,False,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+Core message reuse,"monobook-view-create and vector-view-create are also reused.
+
+As written in VisualEditor.php, we can avoid message reuse by adding the following code:
+ $wgVisualEditorTabMessages['edit'] = 'visualeditor-ca-ve-edit';
+ $wgVisualEditorTabMessages['create'] = 'visualeditor-ca-ve-create';
+ $wgVisualEditorTabMessages['editsection'] = 'visualeditor-ca-ve-edit-section';
+
+But visualeditor-ca-ve-edit, visualeditor-ca-ve-create, and visualeditor-ca-ve-edit-section are all ""VisualEditor"".",1404053114,PHID-USER-mchhpeuixutvfg7eceob,False,PHID-TASK-m24wzue25r3tbqzzunue,task_subcomment,NA
+CirrusSearch: suggesting categories which do not exist and never did,"On it.wp, trying to add a category in VisualEditor.
+If you start typing ""Terminologia dello"", you'll be prompted to add 3 categories.
+One of them though, ""Terminologia dello sport"", doesn't exist and never did.
+(Also, no articles or templates with that name).
+
+I'm told this link could be useful:
+https://it.wikipedia.org/w/api.php?format=json&uselang=en-gb&action=query&list=allcategories&acprefix=Terminologia+dello+sport&acprop=hidden&redirects=
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404023280,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ucqemxjwxsynri4inhdj,task_description,duplicate
+CirrusSearch: suggesting categories which do not exist and never did,This is likely the same issue as {T115756}.,1478127973,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-ucqemxjwxsynri4inhdj,task_subcomment,NA
+CirrusSearch: suggesting categories which do not exist and never did,"I think you'd have to validate the ""doesn't exist and never did"" claim.  Categories are ""created"" as soon as the name of one is saved in any page.  If a redlink to that category ever existed, then the category itself was created (but not the separate description page for the category, which is what you need to turn an existing category into a bluelink).",1431561842,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ucqemxjwxsynri4inhdj,task_subcomment,NA
+CirrusSearch: suggesting categories which do not exist and never did,"I think you'd have to validate the ""doesn't exist and never did"" claim.  Categories are ""created"" as soon as the name of one is saved in any page.  If a redlink to that category ever existed, then the category itself was created (but not the separate description page for the category, which is what you need to turn an existing category into a bulling).",1431561828,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ucqemxjwxsynri4inhdj,task_subcomment,NA
+Make new multi-part transclusions always put newlines between each transclusion (default whitespace of \n),"Some tables built from complex templates assume that there will be line breaks between the templates, so that this works:
+
+{{tabletop}}
+{{tablerow}}
+{{tablerow}}
+{{tablerow}}
+{{tableend}}
+
+but this does not:
+
+{{tabletop}}{{tablerow}}{{tablerow}}{{tablerow}}{{tableend}}
+
+
+There's another problem with transclusions containing content, which can be seen by opening the transclusion at https://en.wikipedia.org/wiki/Kilt#See_also in VisualEditor.  The template lines are fine, but the ""Content"" sections must always start with a blank line, to make up for the absence of line breaks at the end of the templates.  
+
+The solution for both of these is probably the same:  Complex transclusions should always have line breaks after the templates.  I haven't been able to find any (in my quick search) that would break if this were implemented.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1404015660,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-dpxhyjkbi3yny76mtezq,task_description,resolved
+Make new multi-part transclusions always put newlines between each transclusion (default whitespace of \n),"Pretty sure this is a dupe?
+
+*** This bug has been marked as a duplicate of bug 50166 ***",1405409435,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-dpxhyjkbi3yny76mtezq,task_subcomment,NA
+Make new multi-part transclusions always put newlines between each transclusion (default whitespace of \n),"I'm not entirely certain that there aren't multi-part templates that this is the wrong call for, but in general this is certainly a sensible tactic.",1404157701,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dpxhyjkbi3yny76mtezq,task_subcomment,NA
+VisualEditor crashes if the DefaultSummaries gadget is enabled,"VisualEditor crashes when you try to save if the Defaultsummaries gadget is enabled. (https://en.wikipedia.org/wiki/MediaWiki:Gadget-defaultsummaries.js )  This is new; it used to work.
+
+Workaround:  Disable the gadget.
+
+(Might be Firefox-specific.  I haven't tested it.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403930460,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-pqxet5vnqn3mirgkweo6,task_description,invalid
+VisualEditor crashes if the DefaultSummaries gadget is enabled,"Not really a VE bug, but here you go:
+
+The gadget is using ve.init.mw.targets[0] to access the target, which isn't supposed to be a public API yet, but hey. This was removed recently and is now accessible via ve.init.mw.target.",1403970054,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-pqxet5vnqn3mirgkweo6,task_subcomment,NA
+VisualEditor: deleting the text from the article and converting it to a redirect page still leaves in categories and Other Stuff,"Deleting the text from the article and converting it to a redirect page still leaves all the categories in it, as well as Other Stuff such as magic words and invisible templates.
+
+This is a regression in comparison to the source editor, where the editor could just delete everything and be sure that categories, magic words, invisible templates and everything else is gone.
+
+Just redirecting an article shouldn't necessarily remove everything, because it's actually possible that the editor wants to leave the article in a category. Some projects, including enwiki, have categories, templates etc. in redirect pages. But probably some kind of a warning should be shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403884980,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-mpoga25glxtbttk73ydj,task_description,resolved
+VisualEditor: deleting the text from the article and converting it to a redirect page still leaves in categories and Other Stuff,"
+
+*** This bug has been marked as a duplicate of bug 61858 ***",1403885598,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mpoga25glxtbttk73ydj,task_subcomment,NA
+Error saving settings: ... have cookies enabled,"Clicking Save looks OK
+
+After logging in, attempt to set beta settings. 
+
+After clicking Save, get message ""Error saving settings. Please make sure that you have cookies enabled""
+
+This causes test failures such as https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/36/testReport/(root)/VisualEditor/Going_back_from_save_screen_in_VisualEditor/
+
+This is probably a problem in core, and very likely related to the VE bug https://bugzilla.wikimedia.org/show_bug.cgi?id=65709
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65709
+
+**Attached**: {F14190}",1403825280,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-gekbe2bs7wupt3isplty,task_description,resolved
+Error saving settings: ... have cookies enabled,"Change 143799 merged by jenkins-bot:
+Revert ""Give anons tokens too""
+
+https://gerrit.wikimedia.org/r/143799",1404839875,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gekbe2bs7wupt3isplty,task_subcomment,NA
+Error saving settings: ... have cookies enabled,"Change 143799 had a related patch set uploaded by Jdlrobson:
+Revert ""Give anons tokens too""
+
+https://gerrit.wikimedia.org/r/143799",1404839773,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gekbe2bs7wupt3isplty,task_subcomment,NA
+Error saving settings: ... have cookies enabled,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/jtxt8rEw",1403825421,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gekbe2bs7wupt3isplty,task_subcomment,NA
+Error saving settings: ... have cookies enabled,"Created attachment 15756
+Error after clicking Save
+
+**Attached**: {F14191}",1403825307,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-gekbe2bs7wupt3isplty,task_subcomment,NA
+VisualEditor:  Tab order is bad in the Template dialog,"This is the same sort of problem as bug 67153 in the Save dialog.  
+
+
+Here is the incomplete tab order in Safari 6:
+
+1.  Insert > Template
+
+2.  The cursor starts in the template name field.  (It doesn't matter if you type something now.)  Tab:
+
+a) ""Add template"" button
+b)  Nothing—cursor disappears
+c) ""Apply changes"" button 
+d) ""Show options"" (visually backwards, but maybe that's okay)
+e)  Escape the template dialog into the mess described in the Safari-specific bug 67156.
+
+Not accessible:  The X-to-cancel button at the top of the dialog.
+
+
+
+Here is the even more incomplete tab order in Firefox 30:
+
+1.  Insert > Template
+
+2.  The cursor starts in the template name field.  (It doesn't matter if you type something now.)  Tab:
+
+a) the browser's URL bar
+b) the browser's search box (for search engines)
+c) who knows?  It disappears.
+d) the main Wikipedia search box 
+e) the top of the article
+f) the MediaWiki ""More"" menu (where ""Move"" hides)
+g) the icon/go button for the main Wikipedia search box
+h) the languages (gear icon) button
+i) the New template dialog (as a whole, not any useful piece of it)
+j) who knows?  It disappears again.
+k) the New template dialog (as a whole, not any useful piece of it)
+l) who knows?  It disappears again.
+m) back to the field for the template name, repeating endlessly.
+
+Where it doesn't go is:
+
+n) the Add template button
+o) the Show options button
+p) to the X at the top of the dialog box, so you can cancel adding a template and go back to editing. 
+
+
+IMO the order in all cases ought to be:
+
+a)  Start in the template name field
+b) ""Add template"" button
+c) ""Apply changes"" button 
+d) ""Show options""
+e)  X to cancel the dialog and go back to editing
+
+and nothing else (repeat endlessly, if the person keeps pressing tab).
+
+I'm willing to have C and D reversed, because it would be visually more obvious (for left-to-right languages).  However, most users won't be clicking that button, so it'd be more efficient to have it later in the tab order.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67153",1403809500,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-mpvfengewtqthcpazlj5,task_description,resolved
+VisualEditor:  Tab order is bad in the Template dialog,"@James Forrester, the tab index isn't good yet.
+
+Suppose I want to add a template with 4 parameters.
+1. Press on a textbox of the first parameter
+2. Press tab. This should move to the next parameter, but instead moves to button of info, and the next tab moves to button of delete. info and delete are less common than moving to next textbox.
+
+so instead of fill, TAB, fill, TAB... you should do fill, 3 x TAB etc",1408386229,PHID-USER-cfsvvgbtlqnbt2yokfjf,True,PHID-TASK-mpvfengewtqthcpazlj5,task_subcomment,NA
+VisualEditor:  Tab order is bad in the Template dialog,"I'm pretty sure this was done as part of bug 66824.
+
+*** This bug has been marked as a duplicate of bug 66824 ***",1404849994,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mpvfengewtqthcpazlj5,task_subcomment,NA
+VisualEditor:  Tab order or behavior is bad in the Save dialog,"Steps to reproduce:
+
+1.  Open a page and make a change.  
+
+2.  Click the Save button.
+
+3.  Tab.  The cursor starts in the edit summary box (good) and goes to (using en.wp/Vector):
+
+a) tick box for minor edit
+b) link to the minor edit help page**
+c) tick box for watching the page
+d) three links in the licensing statement**
+e) Review your changes button
+f) Save button (inside the dialog box)
+g) the browser's URL bar
+h) the main Wikipedia search box 
+g) the Cancel button (on VisualEditor's toolbar, and it works if you press return now)
+h) the Save button (on VisualEditor's toolbar)
+i) the top of the article
+j) the slug at the top of the article, where it gets stuck forever.
+
+Where it doesn't go is:
+
+k) to the X at the top of the dialog box, so you can cancel saving and go back to editing. 
+
+
+** I'd like these links to be skipped, but (a) maybe this is controlled by a browser setting and (b) maybe my opinion is in the minority.  I'd like these to be skipped so that I can save a page without having to press tab eight times between the edit summary and the final save button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67159",1403806620,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-2pzeuibn247qiu4bfkvi,task_description,resolved
+VisualEditor:  Tab order or behavior is bad in the Save dialog,"I think this is a dupe of bug 65554, which is now fixed.
+
+*** This bug has been marked as a duplicate of bug 65554 ***",1404848147,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2pzeuibn247qiu4bfkvi,task_subcomment,NA
+VisualEditor:  Tab order or behavior is bad in the Save dialog,"Here's the tab order in Firefox 30, starting from the edit summary box in the Save dialog:
+
+a) tick box for minor edit
+b) tick box for watching the page
+c) the browser's URL bar
+d) the browser's search box (for search engines)
+e) who knows?  It disappears.
+f) the main Wikipedia search box 
+g) the top of the article
+h) the MediaWiki ""More"" menu (where ""Move"" hides)
+i) the icon/go button for the main Wikipedia search box
+j) the languages (gear icon) button
+k) the Save dialog (as a whole, not any useful piece of it)
+l) who knows?  It disappears again.
+m) back to the edit summary box, repeating endlessly.
+
+Where it doesn't go is:
+
+n) the Save button in the Save dialog,
+o) the Review your changes button in the Save dialog, or
+p) to the X at the top of the dialog box, so you can cancel saving and go back to editing. 
+
+
+IMO the order ought to be, in its entirety, for all browsers:
+
+a) tick box for minor edit
+b) tick box for watching the page
+c) the Review your changes button
+d) the Save button
+e) the X at the top of the dialog box
+f) back to the edit summary—and repeat in a loop.",1403807315,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-2pzeuibn247qiu4bfkvi,task_subcomment,NA
+VisualEditor:  Tab order or behavior is bad in the Save dialog,The above is the tab order in Safari 6.1.4 on Mac OS 10.8.5.,1403806770,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-2pzeuibn247qiu4bfkvi,task_subcomment,NA
+VisualEditor:  In which it is apparently impossible to create a redirect to [[Foo]] because the list of possible links does not scroll,"Steps to reproduce:
+
+1.  Go to Page settings to create a redirect on the English Wikipedia.
+
+2.  Type ""foo"" (an actual article—well, a redirect to an actual article about metasyntactic variables) in the field.
+
+3.  Look at the search results, which are all about football (plus one for [[Foot (length)]] and one for the US FDA).  Think, ""I must need to scroll down past all of this sports stuff""... but it doesn't scroll.
+
+
+If you click on any of these items, then your correct link to ""Foo"" gets replaced by whatever was highlighted.  
+
+It turns out that you can actually get the link to ""Foo"", by clicking on any place outside the dialog box (to make the search results go away) and then clicking on ""Apply changes"", but this is really Not Good.  To make things worse, due to bug 61861, you can't see what actually happened without either going to Review your changes or saving the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403805780,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-nuccdntq5xq6sbg2nsxr,task_description,resolved
+VisualEditor:  In which it is apparently impossible to create a redirect to [[Foo]] because the list of possible links does not scroll,"Yeah, this is bug 54361.
+
+*** This bug has been marked as a duplicate of bug 54361 ***",1406753647,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nuccdntq5xq6sbg2nsxr,task_subcomment,NA
+VisualEditor:  In which it is apparently impossible to create a redirect to [[Foo]] because the list of possible links does not scroll,"Clarification: the list of links does scroll, it's just that there's only 10(?) of them and Foo isn't among them, even though it exists. This is because MWTitleInputWidget, unlike MWLinkTargetInputWidget, does not reserve a special space for the title you typed. Instead, we assume that searching for pages whose names start with ""Foo"" will always return ""Foo"" as the first result, but that doesn't happen in practice because of a bug in the search system (I've also noticed these results being out of alphabetical order).
+
+There's a bug... somewhere where we track things that go wrong because opensearch is unhelpful.",1406577020,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-nuccdntq5xq6sbg2nsxr,task_subcomment,NA
+VisualEditor: Section edit link is not appearing in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Load any page with sections in Betalabs
+
+Observed Result:
+There is no link for editing any section
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14604}",1403732280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ort3kaznvsgusca4dojy,task_description,invalid
+VisualEditor: Section edit link is not appearing in Betalabs,"Ignore this bug, this is for adding a tempalte Country Showdata in the page.",1403735184,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ort3kaznvsgusca4dojy,task_subcomment,NA
+VisualEditor: Section edit link is not appearing in Betalabs,I can't reproduce in any of four browsers tested. :-(,1403734880,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ort3kaznvsgusca4dojy,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"We have an imho fundamentally broken model for inserting links. I don't know why we show the Link tool in the toolbar when there is no selected text because it's pretty much impossible.
+
+The tool is optimised for adding a link to existing text (or typing the label out first, which is unnatural for anyone who hasn't acquired it as a habit due to this bug), and for changing the link target.
+
+A few use cases:
+* Add link in list
+  - Add item item (press return after the last item or create new list)
+  - User has a page or url he wants to link to
+  - Press ""Link"" tool
+  - Type target page name or url
+  - User wants to insert link with that label, or (more likely in case of an external link) have the label be something that is not the link target.
+
+* Add link while typing text
+* Update mistake in text (e.g. text mentioning ""born in the US"" or ""born in 1955"" and the link and label of US/1955 should be another country or year).
+
+I think the frequency at which one needs to only update the link label or link target are significantly lower, but the other cases are certainly not edge cases.
+
+Here's a recording of me painfully trying to insert a link:
+http://cl.ly/3s460Q442L3S
+
+To this day I have not once been able to insert a link without running into a bug that would've discouraged me as a user.
+
+I thought I filed these as separate bugs at some point but I can't find them. Issues encountered in the video:
+
+1) Inserting a plain external link and then typing its label causes an exception (a pawn appears; see video).
+
+2) The link inspector seems to lack an intuitive way to apply the change. During the video you can see me at various points being confused and eventually pressing ""Back"" (or pressing Enter) to apply the change. Especially when inserting a new link or changing an internal link to an external link (albeit by accident) it's counter-intuitive to not see anything in the page or to continue seeing a red link when I've already selected the value from the dropdown menu.
+
+I think when the user selects the value from the dropdown menu, that's when we can apply the change (but keep the inspector open). An interface component like this one that has no ""Save"" button and implies automatic saving should either make sure the object being changed has no visual impact or make sure it is applied live (And not suddenly when clicking away / blurring the inspector)
+
+3) Adding a label (or rather, due to the lack of an input for the label, being forced to change the implied label) is unusable due to lack of text selection within the boundaries of the link (see video).
+
+4) After the link is inserted, the link text is selected in the surface (the link target in the inspector, which is still open, is also selected). It's not clear whether typing will replace the label or the link target (see video).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403713920,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-aevdvuut3fcigynuksnq,task_description,invalid
+VisualEditor: Creating a new link is unusable,"Better followed-up in specific bugs and proposed UX changes, as discussed.",1403717655,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"The link inspector has long been our most concentrated area of bugs. UX changes are coming in response to user testing, and many bug fixes are on their way as well - more are needed obviously.
+
+1. There is no universal link creation process, as every application differs here, but I believe we are not totally off base in our initial design. As usually, we have to solve this problem with the most difficult constraints imaginable. Users are meant to be able to successfully navigate through a 3x3 matrix of options: link existing text, change linked text, create new link text; link to an internal page, a fragment on the existing page or an external page; produce an explicitly labeled link, an automatically labeled link or an unlabeled (external) link. We need to map out all the use cases and come up with a process that covers this matrix elegantly.
+
+2. User testing has confirmed that, even though pressing enter, escape and clicking away all serve to apply and close, users want a button, and the back button doesn't make sense to them. The new design will do away with the back button. It will move the remove button to the bottom left and drop the confusing icon in favor of a destructive button labeled ""Remove"". On the bottom right will be a primary button labeled ""Done"", which will behave the same as pressing enter, escape or clicking away.
+
+3. We need to use the transaction staging system to update the selected content dynamically as you type, making the link appear to be internal, external, red, auto-numbered, auto-labeled, etc.
+
+4. The bug you experienced needs to be addressed, and I will see if it is resolved (or can be resolved) by my context and window refactoring work. The whole system has suffered from having a narrow entry point with too many poorly mapped forks in the road producing unreliable results with any given path at any given time.",1403717586,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,I've filed the pawn bug as bug 67088.,1403715487,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"(In reply to James Forrester from comment #2)
+> Created attachment 15744 [details]
+> Example video showing that issues are caused by having a link immediately
+> preceding the new list item
+
+This video does not follow the same steps. The link existing in the previous list item is irrelevant. You're pressing enter and clicking stuff in between which is what makes it save and work. Those are reflexes as result of hitting these bugs in the past presumably.
+
+Here's the proof:
+
+http://cl.ly/2P2h473b2A20
+
+**Attached**: {F14577}",1403715283,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"Created attachment 15744
+Example video showing that issues are caused by having a link immediately preceding the new list item
+
+**Attached**: {F14577}",1403714761,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+VisualEditor: Creating a new link is unusable,"Regarding the pawn, that also ate the first character (see ""bc"" instead of ""abc"" appear in the recording).",1403714059,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-aevdvuut3fcigynuksnq,task_subcomment,NA
+Toolbar alignment out of whack,"screenshot of problem
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/MediaWiki?veaction=edit
+
+**Attached**: {F14540}",1403686200,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-okhxrptvop7zaitv5gj5,task_description,resolved
+Toolbar alignment out of whack,"
+
+*** This bug has been marked as a duplicate of bug 66988 ***",1403734997,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,I had this problem in Safari 6.1.4 on Mac OS 10.8.5,1403732159,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,Safari 7,1403728943,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,*** Bug 66988 has been marked as a duplicate of this bug. ***,1403700121,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,WFM in Chrome & Firefox. What browser/version/OS are you using?,1403696124,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+Toolbar alignment out of whack,"Created attachment 15733
+Another problem
+
+The second problem i sometimes see after initially loading. Interacting with the page makes the toolbar 'settle' and it's ok.
+
+Experienced it on https://www.mediawiki.org/wiki/VisualEditor?veaction=edit
+
+**Attached**: {F14541}",1403686286,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-okhxrptvop7zaitv5gj5,task_subcomment,NA
+"VisualEditor:  Section headings look like they've been removed, but they're still present when the page is saved","Why did it merge that subsection heading into the paragraph I was typing?
+
+Steps to reproduce:
+
+1.  Start editing a page with existing section headings.  Create a new paragraph above one of the section headings.
+
+2.  At some point, it looks like the ==Section heading== has accidentally been merged to the paragraph that you're typing.  It's no longer present below (just a blank line where it had been), and the text of the section heading is now (in paragraph formatting) in the paragraph you're typing.
+
+3.  Assume it's your fault (did you backspace?), and clean it up.  Replace the missing section heading.  Finish typing your paragraph, if necessary; you might have to do this a couple of times if the error recurs.
+
+4.  Save the page.
+
+5.  Check the diff, e.g., https://en.wikipedia.org/w/index.php?title=Candy_making&diff=prev&oldid=614021270
+
+6.  Ask yourself, why are there three section headings named ==Safety== in a row?
+
+
+If you don't replace the ""missing"" section heading, then everything works out:
+https://en.wikipedia.org/w/index.php?title=Candy&diff=614296008&oldid=614177828
+
+All of the attachments are from this diff.  I've only seen this in Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14503}",1403656140,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wno2xwrbywvfr44kwnto,task_description,resolved
+"VisualEditor:  Section headings look like they've been removed, but they're still present when the page is saved",Can't reproduce. Hopefully this is properly gone now. Wish we could confirm. :-(,1423675862,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wno2xwrbywvfr44kwnto,task_subcomment,NA
+"VisualEditor:  Section headings look like they've been removed, but they're still present when the page is saved","Created attachment 15723
+One of these things is not like the other
+
+**Attached**: {F14505}",1403656244,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wno2xwrbywvfr44kwnto,task_subcomment,NA
+"VisualEditor:  Section headings look like they've been removed, but they're still present when the page is saved","Created attachment 15722
+What it looked like just before I tried to save the page:  no ===Vegetarianism=== heading
+
+**Attached**: {F14504}",1403656217,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wno2xwrbywvfr44kwnto,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","I don't see the option to change the type of a parameter to ""string/line"" when I edit
+https://pt.wikipedia.org/wiki/Template:Marca_de_projeto/dados?action=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60693",1403369520,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-vjbacwfxxizwddsg34zm,task_description,resolved
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","Change 134928 merged by jenkins-bot:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1409438733,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","Change 134928 had a related patch set uploaded by Mooeypoo:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1405064955,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","Or are you referring to the change from ""string/line"" to just ""line""?
+https://gerrit.wikimedia.org/r/#/c/91623/9/spec.templatedata.json,unified
+(I can't select ""line"" either).",1403785930,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor","I wasn't aware of that. In this case, there are docs to update, e.g.:
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/TemplateData/Tutorial#Completing_the_TemplateData_information",1403785873,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+"TemplateData: Unable to select type ""string/line"" in the GUI editor",Didn't we remove those sub-types?,1403741972,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vjbacwfxxizwddsg34zm,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"The error is:
+
+err: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Browsertests::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Ruby::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Exec[bundle-install-/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]: Could not evaluate: Could not find command '/usr/local/rbenv/shims/bundle'
+
+---
+
+Full list of roles:
+
+  accountinfo                geshi                      parsoid                 
+  analytics                * gettingstarted             pdfhandler              
+  antispam                   globalusage                poem                    
+  antispoof                * guidedtour                 popups                  
+  apisandbox                 gwtoolset                  proofreadpage           
+  apparmor                   hadoop                     scribunto               
+  babel                      hhvm                       simple_miser            
+  betafeatures               hive                       simple_performant       
+  browsertests               https                      sitematrix              
+  centralauth                jsduck                     templatedata            
+  centralnotice              labs_initial_content       textextracts            
+  chromium                   mantle                     thumb_on_404            
+  cirrussearch               massmessage                timedmediahandler       
+  cite                     * math                       translate               
+  cldr                       mathsearch                 uls                     
+  codeeditor                 mleb                       uploadwizard            
+  commonsmetadata          * mobilefrontend             urlshortener            
+  confirmedit                multimedia                 vectorbeta              
+  doublewiki                 multimediaviewer         * visualeditor            
+  echo                       mysql                      wikidiff2               
+  education                  navigationtiming         * wikieditor              
+* eventlogging               newusermessage             wikihiero               
+  flow                       oauth                      wikilove                
+  fss                        pagedtiffhandler           wikimania_scholarships  
+  fundraising                pageimages               * wikimediaevents         
+  gadgets                    pagetriage                 wikimetrics             
+  geodata                  * parserfunctions            xhprof
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403054280,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-zom2liucvmkdzjzairgy,task_description,resolved
+VisualEditor fails to provision with rbenv error,"That solution makes perfect sense, and matches the symptoms, so I'm marking this fixed and not doing the retesting I mentioned in comment #8.",1404938920,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Change 145127 merged by jenkins-bot:
+Require git::clone before browsertests::bundle
+
+https://gerrit.wikimedia.org/r/145127",1404938483,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Change 145127 had a related patch set uploaded by BryanDavis:
+Require git::clone before browsertests::bundle
+
+https://gerrit.wikimedia.org/r/145127",1404938392,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"First try for me on a Trusty VM that had never had VE enabled before failed with:
+
+Error: Working directory '/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser' does not exist
+Error: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Browsertests::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Ruby::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Exec[bundle-install-/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/returns: change from notrun to 0 failed: Working directory '/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser' does not exist
+
+The problem for me was that browsertests::bundle doesn't require the git::clone.",1404937976,PHID-USER-ll6tmaogat2b5q7tnqas,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"VisualEditor is working now on that box (after a vagrant up --provision), except there are timeouts in the browser tests.
+
+Next (when I have a chance), I'm going to try to destroy that box, and create a fresh one (but using the same Debian packages), to see if the problem manifests on a fresh build.",1404856994,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Created attachment 15845
+Fresh install on 2014-07-03
+
+It eventually failed due to not getting all the Debian packages.  I didn't try (yet) to re-provision and see if that fixed it
+
+Dan, let's decide to how to proceed Tuesday.  I will make sure I don't lose the apt-cache, so I won't have to re-download the vast majority that did succeed (or the trusty base box).
+
+**Attached**: {F13943}",1404437336,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Sure.
+
+matthew@matthew-t520: ~/Code/Wikimedia/vagrant-ruby-visualeditor/mediawiki/extensions/VisualEditor (master|✔)% git status
+# On branch master
+nothing to commit (working directory clean)
+matthew@matthew-t520: ~/Code/Wikimedia/vagrant-ruby-visualeditor/mediawiki/extensions/VisualEditor (master|✔)% git show-ref HEAD
+4be59a00c12580e24e2de673c14e082bf714ee9c refs/remotes/origin/HEAD
+matthew@matthew-t520: ~/Code/Wikimedia/vagrant-ruby-visualeditor/mediawiki/extensions/VisualEditor (master|✔)% git submodule
+ a014302f441dda5c4805d378f4ccb67bc1d5e566 lib/ve (a014302)
+
+Note, this is from a fresh MediaWiki-Vagrant VM I created (same one as comment #4), not my regular MediaWiki-Vagrant VM.",1404171075,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Can you verify the working commit of VE and its submodules? i.e. Please provide the output of `git status`, `git show-ref HEAD`, and `git submodule` under the mediawiki/extensions/VisualEditor subdirectory.",1404161980,PHID-USER-7bifphmxtcqgvdofuzla,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Created attachment 15775
+Log from fresh install of MediaWiki-Vagrant
+
+I tried with a new box, with the latest Ruby change (use distro packages), against git 99633340308c46c2d7ebc488195b2d47be0f235c, and the following roles:
+-----
+Available roles:
+
+  accountinfo              * gettingstarted             poem                    
+  analytics                  globalusage                popups                  
+  antispam                 * guidedtour                 proofreadpage           
+  antispoof                  gwtoolset                  scribunto               
+  apisandbox                 hadoop                     simple_miser            
+  apparmor                   hhvm                       simple_performant       
+  babel                      hive                       sitematrix              
+  betafeatures               https                      templatedata            
+  browsertests               jsduck                     textextracts            
+  centralauth                labs_initial_content       thumb_on_404            
+  centralnotice              mantle                     timedmediahandler       
+  chromium                   massmessage                translate               
+  cirrussearch             * math                       uls                     
+  cite                       mathsearch                 uploadwizard            
+  cldr                       mleb                       urlshortener            
+  codeeditor               * mobilefrontend             vectorbeta              
+  commonsmetadata            multimedia               * visualeditor            
+  confirmedit                multimediaviewer           wikidiff2               
+  doublewiki                 mysql                    * wikieditor              
+* echo                       navigationtiming           wikihiero               
+  education                  newusermessage             wikilove                
+* eventlogging               oauth                      wikimania_scholarships  
+* flow                       pagedtiffhandler         * wikimediaevents         
+  fss                        pageimages                 wikimetrics             
+  fundraising                pagetriage                 wikitech                
+  gadgets                  * parserfunctions            xhprof                  
+  geodata                  * parsoid                                            
+  geshi                      pdfhandler                                         
+
+Roles marked with '*' are enabled.
+Use ""vagrant enable-role"" & ""vagrant disable-role"" to customize.
+-----
+I got the attached log.  You can see that VisualEditor failed, first with:
+
+Sat Jun 28 06:17:50 +0000 2014 /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Browsertests::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Ruby::Bundle[/vagra\
+nt/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Exec[bundle-install-/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/returns (err): change from notrun to 0 failed: Workin\
+g directory '/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser' does not exist
+
+It is not the first failure (Math also failed due to bug 66807), but I'm not sure the Math failure is related.
+
+**Attached**: {F13942}",1403988909,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Matthew, Would you mind trying this again in case the fix to bug #66763 was related? Thanks!",1403902785,PHID-USER-7bifphmxtcqgvdofuzla,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"Created attachment 15683
+Puppet error with VisualEditor provisioning failure
+
+Yes, it's reproducible on repeated provisioning runs.  I've attached the full log from a debug run.
+
+**Attached**: {F13941}",1403121299,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+VisualEditor fails to provision with rbenv error,"I'm unable to repro this from a fresh VM with the given roles enabled. Do you continue to get this error after provisioning a second time?
+
+Given the sometimes tricky nature of Puppet resource dependencies, it would help greatly to have a more detailed log of the run. Can you please specify `puppet_debug: true` in your `.settings.yaml` file and provide the output or `vagrant provision` as an attachment? Thanks!",1403116140,PHID-USER-7bifphmxtcqgvdofuzla,True,PHID-TASK-zom2liucvmkdzjzairgy,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Wikitext: '''foo[[File:Image.jpg|thumb]]bar'''
+
+Resulting DOM: <body><b><figure><a><img /></a></figure>bar</b>
+
+Block nodes like figure aren't supposed to occur inside of inline-ish (annotation) tags like b. When confronted with this, VisualEditor alienates the image to preserve its sanity (data model consistency), so bolded images can't be edited in VE.
+
+Reported by mattk_ on IRC.
+
+$ echo ""'''foo[[File:Image.jpg|thumb]]bar'''"" | node tests/parse.js
+
+<!DOCTYPE html>
+<html prefix=""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/""><head prefix=""mwr: http://en.wikipedia.org/wiki/Special:Redirect/""><meta property=""mw:parsoidVersion"" content=""0""/><link rel=""dc:isVersionOf"" href=""//en.wikipedia.org/wiki/Main_Page""/><title></title><base href=""//en.wikipedia.org/wiki/Main_Page""/><link rel=""stylesheet"" href=""//en.wikipedia.org/w/load.php?modules=mediawiki.skinning.elements|mediawiki.skinning.content|mediawiki.skinning.interface|skins.vector.styles|site|mediawiki.skinning.content.parsoid&amp;only=styles&amp;debug=true&amp;skin=vector""/></head><body data-parsoid='{""dsr"":[0,37,0,0]}' lang=""en"" class=""mw-content-ltr mw-body-content"" dir=""ltr""><b data-parsoid='{""dsr"":[0,36,3,3]}'>foo<figure class=""mw-default-size"" typeof=""mw:Image/Thumb"" data-parsoid='{""optList"":[{""ck"":""thumbnail"",""ak"":""thumb""}],""dsr"":[6,30,2,2]}'><a href=""./File:Image.jpg"" data-parsoid='{""a"":{""href"":""./File:Image.jpg""},""sa"":{},""dsr"":[8,28,null,null]}'><img resource=""./File:Image.jpg"" src=""//upload.wikimedia.org/wikipedia/en/thumb/7/78/Image.jpg/220px-Image.jpg"" height=""30"" width=""220"" data-parsoid='{""a"":{""resource"":""./File:Image.jpg"",""height"":""30"",""width"":""220""},""sa"":{""resource"":""File:Image.jpg""}}'/></a></figure>bar</b>
+</body></html>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403043660,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_description,resolved
+Parsoid outputs <figure> inside of <b>,">>! In T68749#4456438, @Arlolra wrote:
+>> Let us open a fresh task since this is specifically about figure in b that was addressed.
+> 
+> Ok, but the only thing that was addressed here was T68749#702519 (similarly T65642).
+> 
+> As quoted in T68749#4452211, the output of T68749#702575 was really case dependent.
+
+Got it .. but, did you reopen to only fix the figure in block tags case or something more general? But, I think either way ... a fresh task with clear description of what needs fixing is better since some of this history is too old and stale .. especially since you will have to edit the description and title.",1532709982,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"> Let us open a fresh task since this is specifically about figure in b that was addressed.
+
+Ok, but the only thing that was addressed here was T68749#702519 (similarly T65642).
+
+As quoted in T68749#4452211, the output of T68749#702575 was really case dependent.",1532705503,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,Let us open a fresh task since this is specifically about figure in b that was addressed. You are talking about a generic html content model violation.,1532671743,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"From the commit message of https://github.com/wikimedia/parsoid/commit/d473791ea982178af7a0fe15aff5cf8e21aaa5e8
+
+> However, in T68749, there's a request/argument to avoid nesting blocks
+> in formatting tags, since VE can't handle that data model violation and
+> marks the nodes as uneditable.  In the past, we've supported that
+> inconsistently.  For example, the case in ""1. List embedded in a
+> formatting tag"" is uneditable, despite it being a popular pattern.
+> In ""2. Treebuilder fixup of formatting elt"", only one of two images was
+> editable.
+>
+> We should consider reopening T68749 and adding a pass to solve the issue
+> generally.  Note that the Parsoid output now matches Remex so any
+> changes to the DOM is explicitly introducing a difference to support
+> editing clients, and should be noted as such.",1532574872,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"(In reply to ssastry from comment #8)
+> Roan: see below .. I don't see a <b> inside the <a> tag. Can you provide the
+> wikitext where you are seeing the problem html?
+> 
+> [subbu@earth lib] echo ""'''foo[[File:Foobar.jpg|thumb|caption]]bar'''"" |
+> node parse --normalize
+> 
+> <p><b>foo</b></p>
+> <figure><a href=""File:Foobar.jpg""><img
+> src=""//upload.wikimedia.org/wikipedia/commons/3/3a/Foobar.jpg"" height=""26""
+> width=""220""/></a><figcaption><b>caption</b></figcaption></figure>
+> <p><b>bar</b></p>
+
+Sorry, I'm blind. You're right, the output is correct now.",1413322888,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Roan: see below .. I don't see a <b> inside the <a> tag. Can you provide the wikitext where you are seeing the problem html?
+
+[subbu@earth lib] echo ""'''foo[[File:Foobar.jpg|thumb|caption]]bar'''"" | node parse --normalize
+
+<p><b>foo</b></p>
+<figure><a href=""File:Foobar.jpg""><img src=""//upload.wikimedia.org/wikipedia/commons/3/3a/Foobar.jpg"" height=""26"" width=""220""/></a><figcaption><b>caption</b></figcaption></figure>
+<p><b>bar</b></p>",1413322614,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"(In reply to Gerrit Notification Bot from comment #6)
+> Change 162819 merged by jenkins-bot:
+> (Bug 66749) Fix the test for DU.isGeneratedFigure
+> 
+> https://gerrit.wikimedia.org/r/162819
+
+This makes it better, but the resulting HTML still violates the Parsoid HTML spec.
+
+Old output: <body><b>foo<figure><a><img /></a></figure>bar</b></body>
+
+New output: <body><p><b>foo</b></p><figure><a><b><img /></b></a></figure><p><b>bar</b></p></body>
+
+At least the figure isn't bolded any more, but there's still a <b> tag between the <a> and the <img> whereas according to the spec, the structure should be <figure><a><img>",1413316823,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Change 162819 merged by jenkins-bot:
+(Bug 66749) Fix the test for DU.isGeneratedFigure
+
+https://gerrit.wikimedia.org/r/162819",1411688205,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Change 162819 had a related patch set uploaded by Subramanya Sastry:
+(Bug 66749) Fix the test for DU.isGeneratedFigure
+
+https://gerrit.wikimedia.org/r/162819",1411617418,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"What Gabriel points out in comment 2 is exactly the same as bug 63642. The DOM I get from <p>'''foo[[File:Image.jpg|thumb|caption]]bar''' looks like <p><b>foo</b></p><figure><b><a><img /></a><figcaption>caption</figcaption></b></figure><p><b>bar</b></p>
+
+(In reply to C. Scott Ananian from comment #1)
+> Not sure this is a bug:
+> 
+> > div = document.createElement('div')
+> <div>​</div>​
+> > div.innerHTML=""<b><figure></figure></b>""
+> ""<b><figure></figure></b>""
+> > div.outerHTML
+> ""<div><b><figure></figure></b></div>""
+> > div.innerHTML=""<b><div></div></b>""
+> ""<b><div></div></b>""
+> > div.outerHTML
+> ""<div><b><div></div></b></div>""
+> 
+> Note that HTML5 is perfectly happy to let the block element live inside the
+> <b> tag.
+Yeah, HTML lets you do it, but I don't think it's very sensible, and VE doesn't like it. I also see no reason why the behavior should be radically different depending on whether Parsoid has decided that the text is in a paragraph or free text. In the paragraph case, the bold tag is interrupted (and reapplied inside the figure, but that's bug 63642; really it should be reapplied in the caption instead, or not at all) and the figure isn't bolded, but in the free text case the figure is bolded. Given that the distinction between free text and paragraph text is pretty arbitrary, I don't think this makes much sense.
+
+Speaking of, this paragraph vs free text stuff is also pretty broken. The following wikitext:
+
+'''foo[[File:Image.jpg|thumb|caption]]bar'''
+
+'''foo[[File:Image.jpg|thumb|caption]]bar'''
+
+produces a DOM that looks like  <body><b>foo<figure><a><img /></a></figure>bar</b>\n\n<b>foo<figure><a><img /></a></figure>bar</b></body> which is wrong: bar and foo will be on the same line but shouldn't be.",1403045057,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"(Taking the bug, since if it ends up being a real bug with our image spec, I'll fix it in Parsoid.  It appears that, to the extent this is a real bug, it's a dup of bug 63642 though.)",1403044295,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"At a minimum, we should not create output that has the figcaption inside a figure wrapped into a formatting element.
+
+Yet that's what I seem to get with this input:
+
+<p>'''foo[[File:Image.jpg|thumb|caption]]bar'''",1403044135,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid outputs <figure> inside of <b>,"Not sure this is a bug:
+
+> div = document.createElement('div')
+<div>​</div>​
+> div.innerHTML=""<b><figure></figure></b>""
+""<b><figure></figure></b>""
+> div.outerHTML
+""<div><b><figure></figure></b></div>""
+> div.innerHTML=""<b><div></div></b>""
+""<b><div></div></b>""
+> div.outerHTML
+""<div><b><div></div></b></div>""
+
+Note that HTML5 is perfectly happy to let the block element live inside the <b> tag.",1403043980,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-5udu3lh4gaeui3owoea2,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Currently, Parsoid runs the following check to tell if an interwiki link points at the current wiki [1]:
+
+if ( interwikiInfo.prefix === env.conf.wiki.iwp.replace( /wiki/, '' ) ) {
+
+Obviously this is inadequate when the wiki name doesn't end in ""wiki"". (It's slightly unclear to me what ""iwp"" is; it claims to be an interwiki *prefix*, but some of the tests set it to ""enwiki"", so I'm assuming it's actually the DB name.)
+
+See http://parsoid.wmflabs.org/_rt/mediawikiwiki/VisualEditor:Local. Currently the first link is ""mw:WikiLink"" and the second is ""mw:ExtLink"", which is wrong. The PHP parser renders them identically as internal links.
+
+---
+[1] http://git.wikimedia.org/blob/mediawiki%2Fservices%2Fparsoid.git/18e31a06252db3813fe844b62f15248289cdf4cb/lib%2Fext.core.LinkHandler.js#L106
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403000460,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_description,resolved
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Change 155784 merged by jenkins-bot:
+Handle local interwiki links.
+
+https://gerrit.wikimedia.org/r/155784",1408986548,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Change 155784 had a related patch set uploaded by Cscott:
+WIP: handle local interwiki links.
+
+https://gerrit.wikimedia.org/r/155784",1408734995,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Ok, taking this.  It's related to bug 69909.  We should be using localinterwiki from the siteinfo.",1408733304,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Change 141276 merged by jenkins-bot:
+Expose $wgLocalInterwikis via the API
+
+https://gerrit.wikimedia.org/r/141276",1403531704,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,"Change 141276 had a related patch set uploaded by TTO:
+Expose $wgLocalInterwikis via the API
+
+https://gerrit.wikimedia.org/r/141276",1403414802,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+Parsoid's local interwiki link check fails on non-Wikipedia wikis,The MediaWiki API needs to expose the contents of $wgLocalInterwikis via the API's meta=siteinfo&prop=interwikimap. Then Parsoid will be able to consume that information.,1403000528,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-nt5xhkrvd2i4xkg5ro26,task_subcomment,NA
+VisualEditor:  Typing diacritics results in stray accent marks at the top of the page in Chrome,"María typed her name in VisualEditor on a Mac:  [SHIFT] m + a + r + [OPTION] e + i + a. 
+
+She runs Chrome on a MacBook Pro with a U.S. keyboard.  The result was this:
+
+
+[top of page]
+´
+
+Lots of text here
+
+María
+
+The rest of the page
+
+[end of page]
+
+
+Using a normal keyboard shortcut to add accents to characters should not result in  stray ""´"" characters at the top of the page.
+
+See https://office.wikimedia.org/w/index.php?diff=113478&oldid=113425 for an example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402958220,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ughpsi3kiwodix5i5iuq,task_description,declined
+VisualEditor:  Typing diacritics results in stray accent marks at the top of the page in Chrome,Testing after the latest update was unable to reproduce the problem.,1403301845,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ughpsi3kiwodix5i5iuq,task_subcomment,NA
+VisualEditor:  Typing diacritics results in stray accent marks at the top of the page in Chrome,"I can't reproduce in Chrome or Safari either, in master, testing or production – possibly something odd with a system IME or similar? Provisionally marking as WORKSFORME – can María test again and confirm?",1403127698,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ughpsi3kiwodix5i5iuq,task_subcomment,NA
+VisualEditor:  Typing diacritics results in stray accent marks at the top of the page in Chrome,I can't reproduce this in Safari 6.1.4 on my Mac and haven't tried to reproduce it in Chrome.,1402958281,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ughpsi3kiwodix5i5iuq,task_subcomment,NA
+VisualEditor: Getting Error loading data from server while reviewing changes from Save dialog,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Edit a page
+3.Click on ""Save Page""
+4.Click on ""Review your changes""
+
+Observed Result:
+
+Getting Error loading data from server while reviewing changes from Save dialog 
+
+See the screenshot attached
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13711}",1402942920,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fp5nv7xkzn6llpv5rdfl,task_description,resolved
+VisualEditor: Getting Error loading data from server while reviewing changes from Save dialog,"
+
+*** This bug has been marked as a duplicate of bug 66669 ***",1402943552,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fp5nv7xkzn6llpv5rdfl,task_subcomment,NA
+VisualEditor: Getting Error loading data from server while reviewing changes from Save dialog,"Change 139879 had a related patch set uploaded by Catrope:
+Followup e48ecbc5: fix fatal error due to undefined variable
+
+https://gerrit.wikimedia.org/r/139879",1402943491,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fp5nv7xkzn6llpv5rdfl,task_subcomment,NA
+Breaking VisualEditor breaks wikitext editor,"If VisualEditor ever throws an exception, which seems to be happening a lot, this means that the editor is inaccessible unless you resize the window and refresh.
+
+When an error occurs the wikitext editor should be loaded instead.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402941240,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-xtf36l2ciogrg6tcnf6x,task_description,resolved
+Breaking VisualEditor breaks wikitext editor,"Change 143797 merged by jenkins-bot:
+If error occurs while loading VE, load source editor instead
+
+https://gerrit.wikimedia.org/r/143797",1405112206,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtf36l2ciogrg6tcnf6x,task_subcomment,NA
+Breaking VisualEditor breaks wikitext editor,"Change 143797 had a related patch set uploaded by Kaldari:
+If error occurs while loading VE, load source editor instead
+
+https://gerrit.wikimedia.org/r/143797",1404347298,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtf36l2ciogrg6tcnf6x,task_subcomment,NA
+Breaking VisualEditor breaks wikitext editor,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/iIcumWus",1402941311,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xtf36l2ciogrg6tcnf6x,task_subcomment,NA
+VisualEditor:  Re-using references isn't working very well,"Incident #1:
+
+Add a reference.  Try to re-use it.  It's not in the list at all.
+
+
+Incident #2:
+
+Add a reference using the Cite tool.  Try to re-use it.  It's not in the list at all.  Add a plain <references /> block (rather than {{reflist}}).  Go back and try to re-use it.  Now it's there.
+
+
+Incident #3:
+
+Add a reference.  Try to re-use it.  Only the number (""[1]"") is present in the references list; the old refs are all listed correctly.  Cancel and go look at the new ref to make sure that it actually has contents.  Try to re-use it again.  Now the full description appears.  (Perhaps it was just being slow?  Perhaps it needed something else to trigger it?)
+
+
+(All of these happened in Firefox.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402789800,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yohnyaa6rhyxwjflhy7p,task_description,declined
+VisualEditor:  Re-using references isn't working very well,Let's leave this as worksforme unless someone can find another bug to mark it as a duplicate of.,1414810464,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-yohnyaa6rhyxwjflhy7p,task_subcomment,NA
+VisualEditor:  Re-using references isn't working very well,"I don't think that these are actually three bugs:  I think they are all the same problem, which is that (what is now) Cite > Re-use did not correctly produce a list of existing citations.
+
+I believe that this was resolved a couple of months ago, in some related work.  I haven't encountered this myself or heard any complaints about it for a long while.  The correct status is probably resolved/duplicate.",1414809250,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yohnyaa6rhyxwjflhy7p,task_subcomment,NA
+VisualEditor:  Re-using references isn't working very well,Why are there three bugs in one here? Is any of this still valid? Were you trying to use templates instead of the proper references tag in #1 and #3 as well?,1414808741,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-yohnyaa6rhyxwjflhy7p,task_subcomment,NA
+VisualEditor:  Make it possible to click on a link or URL that's inside a template (to open the link in another tab),"There are a lot of templates that create or display links to other pages.  It would be nice if it were possible to click on those links (to open the linked pages in another tab) while editing VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402600620,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-iueuapim3yguer55bovm,task_description,resolved
+VisualEditor:  Make it possible to click on a link or URL that's inside a template (to open the link in another tab),"
+
+*** This bug has been marked as a duplicate of bug 50966 ***",1402688065,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iueuapim3yguer55bovm,task_subcomment,NA
+"add ""Cite"", ""TemplateData"", ""ParserFunctions"" and Lua extensions for ""visualeditor"" role","References in VE do not work properly in the vagrant VM without also having the Cite extension in place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402527600,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-jozgz5cpm6v67hgjs2el,task_description,resolved
+"add ""Cite"", ""TemplateData"", ""ParserFunctions"" and Lua extensions for ""visualeditor"" role","Change 139053 merged by jenkins-bot:
+Added more depedency roles to visualeditor
+
+https://gerrit.wikimedia.org/r/139053",1402534918,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jozgz5cpm6v67hgjs2el,task_subcomment,NA
+"add ""Cite"", ""TemplateData"", ""ParserFunctions"" and Lua extensions for ""visualeditor"" role","Change 139053 had a related patch set uploaded by Dduvall:
+Added more depedency roles to visualeditor
+
+https://gerrit.wikimedia.org/r/139053",1402534455,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jozgz5cpm6v67hgjs2el,task_subcomment,NA
+"add ""Cite"", ""TemplateData"", ""ParserFunctions"" and Lua extensions for ""visualeditor"" role","
+16:12 chrismcmahon: RoanKattouw: beyond needing Cite for references in VE, is any other extension required for handling templates in VE properly?
+16:13 James_F: chrismcmahon: TemplateData.
+16:13 James_F: chrismcmahon: And Lua and ParserFunctions for most of the existing corpus of templates.
+16:13 chrismcmahon: James_F: awesome",1402528496,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-jozgz5cpm6v67hgjs2el,task_subcomment,NA
+bare wiki + VE does not handle References properly,"Use existing references disabled for page with references
+
+found in the course of enabling browser tests for the Vagrant role visualeditor: 
+
+In the mediawiki visualeditor role and also in a bare wiki having the VisualEditor extensions, references are not handled properly.  
+
+In the pure page view the existing references are not interpreted by the <references /> tag.  See screen shot. 
+
+In VE, the ""Use an existing reference"" button is disabled. See screen shot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13915}",1402527060,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_description,invalid
+bare wiki + VE does not handle References properly,I hate screen shots,1402527370,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+bare wiki + VE does not handle References properly,"gah,",1402527344,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+bare wiki + VE does not handle References properly,"(In reply to Chris McMahon from comment #1)
+> Created attachment 15632 [details]
+> ""Use existing reference"" button disabled on a page with a reference
+Nice vacation accrual stats ;)
+
+(In reply to Roan Kattouw from comment #2)
+> Did you install the Cite extension? Without it, the <ref> and <references>
+> tags don't work in read mode either.
+Additionally, you need to restart Parsoid after installing the Cite extension.
+
+**Attached**: {F13916}",1402527242,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+bare wiki + VE does not handle References properly,"Did you install the Cite extension? Without it, the <ref> and <references> tags don't work in read mode either.",1402527182,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+bare wiki + VE does not handle References properly,"Created attachment 15632
+mistake, disregard
+
+**Attached**: {F13916}",1402527107,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-2hkltmsnr5h4bebiuu3r,task_subcomment,NA
+VisualEditor: Footnote number is not localized while editing,"See the URL for an example.
+
+The reference numbers are not localized in languages that use non-European numbers, such as Arabic and Persian. They are localized correctly while viewing the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://fa.wikipedia.org/wiki/User:Amire80/ref-numbers",1402213680,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-cmxp5glim7b3bnu36xg4,task_description,resolved
+VisualEditor: Footnote number is not localized while editing,"
+
+*** This bug has been marked as a duplicate of bug 56240 ***",1402329599,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmxp5glim7b3bnu36xg4,task_subcomment,NA
+Javascript error when launching desktop VisualEditor (target.createSurface is not a function),"Whenever I try to launch the desktop VE, I get a JS error...
+
+In Firefox: 'target.createSurface is not a function'
+In Chrome: 'Uncaught TypeError: undefined is not a function'
+
+In both cases it comes from ve.init.mw.Target.js, line 1312:
+target.surface = target.createSurface( dmDoc );
+
+The error doesn't happen in mobile VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402081500,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-772o537nc7bdn7wry7rh,task_description,invalid
+Javascript error when launching desktop VisualEditor (target.createSurface is not a function),Nevermind. Had to update the VE submodules.,1402081615,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-772o537nc7bdn7wry7rh,task_subcomment,NA
+tracking: Flow loses session/token information,"Seen only one time:  https://wmf.ci.cloudbees.com/job/Flow-en.wikipedia.beta.wmflabs.org-linux-chrome/465/
+
+As a logged-in user, create a new topic in Flow.  Topic was saved as anonymous, even though user logged in successfully and test showed no sign of user logging out. 
+
+I want to note this because of the similarity to an intermittent issue when switching edit modes in VisualEditor, bug 65709
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+{T67709}",1401805680,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-og532unr32aprpg62cxq,task_description,invalid
+tracking: Flow loses session/token information,Closing - was seen only once & there hasn't been any new report since (and it's been open for > half a year),1418317389,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-og532unr32aprpg62cxq,task_subcomment,NA
+VisualEditor: Duplicate setting of named parameter in template removed when you edit the template in some unrelated way,"""visual editor did more than i told it to: https://en.wikipedia.org/w/index.php?title=Cameroon&diff=611127082&oldid=610427158 ""
+""hmm looks like ve actually removed a duplicate parameter when i made that edit""
+
+Seems this occurs when you edit a template in some way (e.g. adding a new parameter), if a named parameter has been set twice.
+
+Not sure if this is intended behaviour or not. Bug might be a dupe, might be in Parsoid instead of VE, or something else.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401654960,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-pbprcixeydceic4lndax,task_description,declined
+VisualEditor: Duplicate setting of named parameter in template removed when you edit the template in some unrelated way,"This is intended behaviour, yeah; we won't dirty-diff to fix broken wikitext when you edit something else, but VE will always fix up bad existing formatting when you change the item.",1401758985,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pbprcixeydceic4lndax,task_subcomment,NA
+Visual inconsistencies between OOJS and VisualEditorOverlay,"exit overlay
+
+See attachments
+
+* Different X icons used for VisualEditor close and OOUI close
+* There are vertical borders in the VE toolbar
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13867}",1401478260,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-vdyxqxqymleikvtbkkbj,task_description,invalid
+Visual inconsistencies between OOJS and VisualEditorOverlay,"**jgonera** wrote:
+
+Presently OOUI forms look completely different because of a few refactorings that happened in OOUI since that bug was reported. Visual consistency will be tackled in the new OOUI theme.",1406571087,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-vdyxqxqymleikvtbkkbj,task_subcomment,NA
+Visual inconsistencies between OOJS and VisualEditorOverlay,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/MaI2stPq",1401478519,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-vdyxqxqymleikvtbkkbj,task_subcomment,NA
+Visual inconsistencies between OOJS and VisualEditorOverlay,"Created attachment 15539
+Exit dialog in VE
+
+**Attached**: {F13868}",1401478299,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-vdyxqxqymleikvtbkkbj,task_subcomment,NA
+VisualEditor: Existing page shows up under New Page section inside Link Inspector in production,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page
+2.Attempt to insert a link with an existing target page such as ""Test""
+
+Observed Result :
+
+The page ""Test"" appears under the New Page section inside Link Inspector.
+See the screenshot attached
+
+Environment:
+https://en.wikipedia.org/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13800}",1401412020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pcp54qhvwgbbzskvrcsq,task_description,resolved
+VisualEditor: Existing page shows up under New Page section inside Link Inspector in production,"
+
+*** This bug has been marked as a duplicate of bug 51013 ***",1402016305,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pcp54qhvwgbbzskvrcsq,task_subcomment,NA
+"VisualEditor:  When editing a page in the Category: namespace, the contents of the category do not display upon saving","Intention:
+Change the contents of a category page (the description, not the files in it).  See https://commons.wikimedia.org/w/index.php?title=Category:Cuberdon&diff=prev&oldid=125000311
+
+Steps to Reproduce:
+1. Open the page in VisualEditor.
+2. Change the description.
+3. Save the page.
+
+Actual Results:  
+Upon savingm the description was displayed, but not the contents of the category.
+
+Expected Results:  
+You should be able to see all the images in that category, not just the text at the top of the cat page.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401407520,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-r7mvsfuq3amffbdzvceu,task_description,resolved
+"VisualEditor:  When editing a page in the Category: namespace, the contents of the category do not display upon saving","
+
+*** This bug has been marked as a duplicate of bug 64239 ***",1401408756,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r7mvsfuq3amffbdzvceu,task_subcomment,NA
+"toggle to VE makes UI spin forever, no VE, js error","on http://en.m.wikipedia.beta.wmflabs.org/ as logged-in user; set Settings mode for VE access; edit a page; toggle VisualEditor mode
+
+browser shows spinner forever
+
+javascript error is ""Error: Module not found: toggle 
+Error
+message: ""Module not found: toggle""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401203820,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-37lwji5jwrqcsuanpdky,task_description,invalid
+"toggle to VE makes UI spin forever, no VE, js error",This is bug 65823 but the JavaScript error is unrelated to that and actually bug 65838,1401233082,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-37lwji5jwrqcsuanpdky,task_subcomment,NA
+"toggle to VE makes UI spin forever, no VE, js error","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/lIGKYsRM",1401204014,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-37lwji5jwrqcsuanpdky,task_subcomment,NA
+VisualEditor introduces <nowiki> and then breaks template syntax,"https://pt.wikipedia.org/wiki/Jos%C3%A9_Antonio_Reyes?diff=38627387
+https://pt.wikipedia.org/wiki/Jos%C3%A9_Antonio_Reyes?diff=38645684
+https://pt.wikipedia.org/wiki/Jos%C3%A9_Antonio_Reyes?diff=39007919
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401103500,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ofzs6modf4yxz63ugmdy,task_description,resolved
+VisualEditor introduces <nowiki> and then breaks template syntax,This shouldn't now be happening. Long-since fixed.,1442345202,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ofzs6modf4yxz63ugmdy,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"Seasoned Catalan Wikipedia editors are finding strange diffs done by new editors using VisualEditor. See these examples:
+
+https://ca.wikipedia.org/w/index.php?title=Laocoont_o_sobre_els_l%C3%ADmits_en_la_pintura_i_poesia&diff=13401584&oldid=13401089
+
+https://ca.wikipedia.org/w/index.php?title=Joan_Francesc_Ferrer_Sicilia&curid=1102012&diff=13399985&oldid=13399856
+
+https://ca.wikipedia.org/w/index.php?title=Pere_Formiguera_i_Sala&oldid=13189613
+
+https://ca.wikipedia.org/w/index.php?title=Pere_Formiguera_i_Sala&diff=13276699&oldid=13276658
+
+We are still figuring out whether these strange edits are made on purpose or not, by humans or by some VisualEditor bug. Reporting here to check whether someone else has seen something similar elsewhere, or can shed some light.
+
+Related discussion (in Catalan)
+https://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Ajuda#Curiositat
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400848080,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_description,resolved
+Hypothetical generation of strange characters at the beginning of pages,"While ca.wiki got plenty of strange characters during several weeks, that happened month ago, and the strange characters haven't been seen ever since.
+
+We might not know the cause neither the solution, but the problem seems to be Resolved.
+
+https://ca.wikipedia.org/wiki/Topic:Sb2iif7fvhy6p365",1422959784,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"While ca.wiki got plenty of strange characters during several weeks, that happened month ago, and the strange characters haven't been seen ever since.
+
+We might not know the cause neither the solution, but the problem seems to be Resolved.",1422959740,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,See also Bug 63395,1403394234,PHID-USER-hhw22zfd2xzrsyc22lp5,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"(In reply to Quim Gil from comment #7)
+> it includes ☃ and ♙ !
+
+These specific two icons (snowman ☃ and chess pawn ♙) are a debugging feature of VE and unrelated to the original issue reported here.  ☃ and ♙ usually means that Parsoid has encountered something confusing in the wikitext markup.",1403364579,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"This problem keeps happening regularly, e.g. https://ca.wikipedia.org/w/index.php?title=Ferran_Clavell&diff=prev&oldid=13600764
+
+The most surreal edit we have seen so far: https://ca.wikipedia.org/w/index.php?title=Ana_Zelich&diffonly=1&diff=13511465 -- it includes ☃ and ♙ !
+
+One user reported MacBook Pro amb 10.8.5 with Chrome v34.0.1847.131. He also said that he could reproduce it sometimes by typing ""wrong"" accents, e.g. accent + space. 
+
+This might be due to newbie users typing ""L´aventura"" instead of ""L'aventura"" (note the different ´ '). How to test this: at least in my International English keyboard you can type ´ by typing twice '.",1403325888,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"Just in case those users all use Firefox, https://bugzilla.mozilla.org/show_bug.cgi?id=1015433 comes to my mind, though rather unlikely.
+We really need more info on the browser(s) used....",1401296913,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"The user hasn't answered yet. However, while bug 52327 is about ""garbage"" being injected in pages, that garbage consists at least in JavaScript chunks. In this case it is really meaningless garbage. Garbage so meaningless and relatively random that I still fail to deduce where does it come from.",1401176461,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,I asked because I'm wondering if this is another case of broken browser plugins (bug 52327)...,1401157753,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"More, from more users:
+
+https://ca.wikipedia.org/w/index.php?title=Partit_dels_i_les_Comunistes_de_Catalunya&diff=prev&oldid=13430606
+
+https://ca.wikipedia.org/w/index.php?title=Purita_Campos&diff=13441743&oldid=13383289
+
+I will ask the user that replied which browser he is using.",1401143640,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,Which browsers and browser versions are involved?,1401099980,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Hypothetical generation of strange characters at the beginning of pages,"One of the editors, a school teacher, replied saying that he hadn't added those characters manually. We still haven't found a way to reproduce this problem.",1401014103,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-otxks6mxubirbwsvqvfv,task_subcomment,NA
+Error thrown when try to create new pages in wikitext when VisualEditor is default,"Go to a page that doesn't exist.
+Click edit so that VisualEditor loads.
+Toggle to source mode.
+A JavaScript exception is thrown and the loader never clears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400686260,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-u7g6dtcwyoyjlymqpi37,task_description,resolved
+Error thrown when try to create new pages in wikitext when VisualEditor is default,"Change 135722 merged by jenkins-bot:
+Use same options for VisualEditor and Editor overlays
+
+https://gerrit.wikimedia.org/r/135722",1401302630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u7g6dtcwyoyjlymqpi37,task_subcomment,NA
+Error thrown when try to create new pages in wikitext when VisualEditor is default,"Change 135722 had a related patch set uploaded by Jdlrobson:
+Use same options for VisualEditor and Editor overlays
+
+https://gerrit.wikimedia.org/r/135722",1401234961,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u7g6dtcwyoyjlymqpi37,task_subcomment,NA
+Error thrown when try to create new pages in wikitext when VisualEditor is default,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/BGNz7shU",1400692793,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-u7g6dtcwyoyjlymqpi37,task_subcomment,NA
+503 from Parsoid in beta labs,"attempt to edit any page in http://en.wikipedia.beta.wmflabs.org/ with VisualEditor
+
+get error ""Error loading data from server: parsoidserver-http-bad-status: 503. Would you like to retry?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400619780,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-wurlwpdl3llexy7jqxw5,task_description,resolved
+503 from Parsoid in beta labs,"
+
+*** This bug has been marked as a duplicate of bug 65553 ***",1400619845,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wurlwpdl3llexy7jqxw5,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"I'm currently trying to edit Wikivoyage and nothing happens when I click edit. Very weird. hash does change...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400588160,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-hf7auwexf5hzfjlto5wz,task_description,resolved
+Edit button seems to have no effect in Wikivoyage,"Change 134410 merged by jenkins-bot:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134410",1400612157,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134411 merged by jenkins-bot:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134411",1400611800,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134411 had a related patch set uploaded by MaxSem:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134411",1400611736,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134410 had a related patch set uploaded by MaxSem:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134410",1400611707,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134405 merged by jenkins-bot:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134405",1400611536,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"Change 134405 had a related patch set uploaded by Jdlrobson:
+Fix edit link when VisualEditor is not available
+
+https://gerrit.wikimedia.org/r/134405",1400610990,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Edit button seems to have no effect in Wikivoyage,"
+
+*** This bug has been marked as a duplicate of bug 65509 ***",1400610714,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-hf7auwexf5hzfjlto5wz,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Could have sworn I raised this bug previously but here we go again..
+Load Article#editor/0 in alpha
+See VisualEditor.
+Switch to source editor.
+Now refresh the page using browser.
+Wikitext editor loads.
+Attempt to switch to VisualEditor.
+Fail.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400532480,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ltqykuq33aln74viml6d,task_description,resolved
+Cannot switch to VisualEditor after a reload,"Change 137731 merged by jenkins-bot:
+Show loader when switching between editors
+
+https://gerrit.wikimedia.org/r/137731",1402102067,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Change 137731 had a related patch set uploaded by Jdlrobson:
+Show loader when switching between editors
+
+https://gerrit.wikimedia.org/r/137731",1401993634,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Change 137251 abandoned by Jdlrobson:
+Show a spinner when switching between editors
+
+Reason:
+I'm going to do this another way.
+
+https://gerrit.wikimedia.org/r/137251",1401993313,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Change 137251 had a related patch set uploaded by Jdlrobson:
+Show a spinner when switching between editors
+
+https://gerrit.wikimedia.org/r/137251",1401845823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Change 136249 had a related patch set uploaded by Jdlrobson:
+WIP: have a standard way of invoking loader
+
+https://gerrit.wikimedia.org/r/136249",1401402678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Best way to simulate this... Open wikitext editor via clicking edit icon.
+Kill your web server.
+Click the toggle to VE icon.
+Nothing happens.",1401399166,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Created attachment 15464
+Double toolbar loading in VE
+
+**Attached**: {F14060}",1400856764,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"Created attachment 15463
+Delay between clicking button and seeing VE
+
+**Attached**: {F14059}",1400856697,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,It's not just the spinner - just sometimes it doesn't even start loading. I'm worried this indicates some bigger kind of problem. Let me attach some videos demonstrating the behaviour I am seeing...,1400856627,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"**jgonera** wrote:
+
+I'm marking as workforsome, please raise another bug if there are problems with the spinner.",1400854714,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,On my local instance it takes 2-3 seconds for VE to load cold but the spinner appears almost instantly.,1400704098,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"I don't see any indicator whatsoever for those 5 seconds so usually click it more than once :-(
+
+
+A few times I've also seen two toolbars get created.",1400692673,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"**jgonera** wrote:
+
+It takes about half a second on my vagrant instance, but the indication (loader) should probably appear earlier.",1400692597,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"So actually I've noticed it does actually load eventually but it takes 6 seconds to do so and doesn't show a loading overlay or anything so it's not clear the click did anything...
+
+I'm guessing you guys just have super fast instances...",1400535217,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,Works for me. Tested in Firefox on latest master.,1400534635,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"**jgonera** wrote:
+
+Can't reproduce on latest master.",1400534422,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+Cannot switch to VisualEditor after a reload,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/FcXnAItk",1400532614,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ltqykuq33aln74viml6d,task_subcomment,NA
+VisualEditor:  Special character inserter breaks up links to other pages,"Steps to Reproduce:
+1. Start with a link to another page, e.g., [[abc]].
+
+2. Use the special character inserter tool to add a special character, with the goal of producing something like this:  [[abc|aübc]].
+
+
+
+Actual Results:  
+Instead of [[abc|aübc]], you get [[abc|a]]ü[[abc|bc]].
+
+
+Reproducible: Always
+
+Reproduced in Firefox and Safari.  May be related to Bug 60476 about character formatting?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400521320,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jfbnqce7vgau7v3adje4,task_description,resolved
+VisualEditor:  Special character inserter breaks up links to other pages,"Yeah, merging this with bug 60476 and expanding the description there.
+
+*** This bug has been marked as a duplicate of bug 60476 ***",1400546427,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jfbnqce7vgau7v3adje4,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"I've been seeing this in the overnight runs of the browser tests in recent times. The build for VisualEditor will fail with a modal dialog that says ""Error loading data from server: readonly. The wiki is currently in read-only mode. Would you like to retry?""
+
+Here is an example from the overnight run Sunday 18 May: https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/512/testReport/(root)/VisualEditor/Edit_with_strings__outline_example_____Editing_with_%C3%84%C3%8B%C3%8F%C3%96%C3%9C___Editing_with_%C3%84%C3%8B%C3%8F%C3%96%C3%9C___/
+
+I can't think of any reason why beta labs would be in read-only mode late on a Sunday (PDT).  
+
+I suspect this may also be the cause of the occasional failure in other builds with less information, for example ""too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout)"" that we see in the MobileFrontend builds: too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/571/testReport/(root)/Check%20UI%20components/Check_existence_of_important_UI_components_on_other_pages_/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68349",1400509680,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_description,resolved
+beta labs mysteriously goes read-only overnight,"This seems to have been fixed by https://gerrit.wikimedia.org/r/#/c/149052/
+
+Thanks Sam!",1406300456,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,also see https://github.com/wikimedia/operations-mediawiki-config/commit/38990c671fd3b8d15f31a7c819e7bdd52ecef3ef,1406151403,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,Adding Sean Pringle.  This seems to be getting worse. I'd like to either update the db less often or else make it less disruptive.,1406151365,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,I saw this just now also.,1401826733,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"Antoine, would these messages be relevant?  They do not seem to happen at any particular interval but they might be correlated to the time at which Rummana saw the problem.  
+
+@deployment-bastion:/data/project/logs$ tail -f dberror.log 
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 17:17:09 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+Tue Jun 3 17:50:48 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 17:50:48 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+Tue Jun 3 19:20:48 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Tue Jun 3 19:20:48 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)",1401823647,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"Created attachment 15558
+Screenshot
+
+I have reproduced this issue today on Betalabs, attaching the screenshot
+
+**Attached**: {F14002}",1401820906,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"
+Right, and we know about the unexpected readonly status because it seems only VisualEditor displays that error in a javascript confirm modal dialog.  It might manifest in other ways that we would not see if not for the modal dialog that stops the test.",1401226061,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,FWIW VisualEditor doesn't know about <readonlytext> – it's just passing on what it gets from the API.,1401225595,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"On one SauceLab failure, it was POSTing to  ""http://en.wikipedia.beta.wmflabs.org/wiki/User:Selenium_user/firefox?vehidebetadialog=true&veaction=edit""
+
+The message:
+
+  The wiki is currently in read-only mode. Would you like to retry?
+
+Which comes from ApiBase::dieReadOnly(). That method seems to only be called when wfReadOnly() is true which is some legacy code that would let us create a file on the cluster that would disable edits entirely.
+
+There is like 0% change it is being triggered that way unless something mess with $wgReadOnly.  So most probably the i18n message is being reused by another path of code.",1401136491,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,Who could investigate this?,1401117229,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,"If I recall correctly, this is something that can happen when things go sideways with the database. Not sure if that's what's going on here, but may be worth looking into.",1400627006,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+beta labs mysteriously goes read-only overnight,I think this is the first time I've seen the wiki read-only during the day (PDT) https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/4/testReport/(root)/Switching%20between%20wikitext%20and%20Visual%20Editor%20modes/Switch_editing_modes_via_toolbar/,1400626399,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-azn3jqm7c4zgqmbqnk6m,task_subcomment,NA
+"VisualEditor: The ""Review changes"" button should be disabled when save dialog is locked during saving","It should be disabled/muted like we do in other cases.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400507340,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eibrrqabz54in23ld6jv,task_description,resolved
+"VisualEditor: The ""Review changes"" button should be disabled when save dialog is locked during saving","
+
+*** This bug has been marked as a duplicate of bug 65310 ***",1400507426,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eibrrqabz54in23ld6jv,task_subcomment,NA
+VisualEditor Mobile: Lock sign appearing over the Edit option on Mobile VE even if user has Beta and Experimental Mode on,"Screenshot
+
+I am getting this issue while trying to edit :https://en.m.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox
+
+I dont know how I stumbled upon it, but I can not edit my sandbox anymore with Mobile VE in any device/browser.
+
+However, if I add it to or remove it from my watchlist by tapping on star, only then the lock disappears from the edit icon and I can edit.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13821}",1400272200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6w4q2qazxtjqqz52eh5,task_description,declined
+VisualEditor Mobile: Lock sign appearing over the Edit option on Mobile VE even if user has Beta and Experimental Mode on,Probably a glitch in protection checking or something odd?,1401418027,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c6w4q2qazxtjqqz52eh5,task_subcomment,NA
+VisualEditor Mobile: Lock sign appearing over the Edit option on Mobile VE even if user has Beta and Experimental Mode on,"Works for me..
+https://en.m.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?mobileaction=alpha",1400522666,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-c6w4q2qazxtjqqz52eh5,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Load VE and switch to wikitext editor - triggers Validation error against schema MobileWebEditing: Missing property: funnel
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400195040,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-lryy7gpyx4cjl47ybghb,task_description,resolved
+EventLogging errors when switching from VisualEditor,Ignore above activity.,1401321316,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Change 135971 abandoned by Jdlrobson:
+Set funnel on VE
+
+https://gerrit.wikimedia.org/r/135971",1401321288,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Change 135971 had a related patch set uploaded by Jdlrobson:
+Set funnel on VE
+
+https://gerrit.wikimedia.org/r/135971",1401320995,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Change 134587 merged by jenkins-bot:
+Stop EventLogging errors when switching from VisualEditor to Editor
+
+https://gerrit.wikimedia.org/r/134587",1400858668,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"Change 134587 had a related patch set uploaded by Jdlrobson:
+Stop EventLogging errors when switching from VisualEditor to Editor
+
+https://gerrit.wikimedia.org/r/134587",1400667848,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+EventLogging errors when switching from VisualEditor,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/NxeR9xyO",1400195109,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lryy7gpyx4cjl47ybghb,task_subcomment,NA
+VisualEditor: Opening a popupToolGroup should disable other tools,"Per the design mock-up at https://trello.com/c/xCo6uLAZ/9-5-references-dropdown-from-toolbar-styling (and a conversation with Kaity to confirm), when a user opens a popupToolGroup, all other tools in the toolbar should be disabled. Clicking off the popupToolGroup should close the popup and reactivate the other tools.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400193060,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-krpdp7rpaekkdslv6m5f,task_description,invalid
+VisualEditor: Opening a popupToolGroup should disable other tools,"After talking with Trevor and Kaity, we're going to punt this one for now.",1400272697,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-krpdp7rpaekkdslv6m5f,task_subcomment,NA
+VisualEditor not opening consistently in Firefox,"Steps to reproduce:
+
+1.  Be me, or one of several other people, but not James F.  (This step may be difficult to reproduce.  ;-)
+
+2.  Login on Firefox. 
+
+3.  Try to open an article in VisualEditor.
+
+4.  Wait.  Wait.  Wait.  Wonder why a page that pops open in Safari in less than five seconds still hasn't opened in Firefox despite the animated blue bar showing for more than 30 seconds now.
+
+5.  Wait.  Wait.  Wait.  Wonder if this is ever going to open.   
+
+6.  Give up and reload.  Maybe it works this time; maybe it doesn't.  If it doesn't, consider restarting Firefox.  That usually helps... for one article.  Then it goes back to its old behavior of occasionally opening a page, but not usually.
+
+
+I don't feel like I have a lot of useful information to give you, but this has been a problem for a couple of weeks and does not seem to be getting better.  Logging out may help, according to https://en.wikipedia.org/w/index.php?oldid=608667917#VE_does_not_start
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400181900,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gcadzjjnt6fiqkhy623y,task_description,invalid
+VisualEditor not opening consistently in Firefox,"Whatever this problem was, there are no reports of it any more, and it could not be reproduced, so I'm closing.",1513167765,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-gcadzjjnt6fiqkhy623y,task_subcomment,NA
+VisualEditor not opening consistently in Firefox,"""Storage error"" load.php:161
+""[Exception... ""Persistent storage maximum size reached""  code: ""1014"" nsresult: ""0x805303f6 (NS_ERROR_DOM_QUOTA_REACHED)""  location: ""<unknown>""]"" DOMException [NS_ERROR_DOM_QUOTA_REACHED: ""Persistent storage maximum size reached""
+code: 1014
+nsresult: 0x805303f6
+location: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20140626T181618Z:183] load.php:161
+
+""Storage error"" load.php:161
+""[Exception... ""Persistent storage maximum size reached""  code: ""1014"" nsresult: ""0x805303f6 (NS_ERROR_DOM_QUOTA_REACHED)""  location: ""<unknown>""]"" DOMException [NS_ERROR_DOM_QUOTA_REACHED: ""Persistent storage maximum size reached""
+code: 1014
+nsresult: 0x805303f6
+location: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20140626T181618Z:183]",1404176574,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gcadzjjnt6fiqkhy623y,task_subcomment,NA
+VisualEditor not opening consistently in Firefox,Are/were there any errors in the JS console at all?,1404174460,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-gcadzjjnt6fiqkhy623y,task_subcomment,NA
+VisualEditor not opening consistently in Firefox,"I think this might have been solved for me, by removing one of Eran's scripts from common.js  However, another user who has reported the same problem isn't running that script.",1404173665,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gcadzjjnt6fiqkhy623y,task_subcomment,NA
+VisualEditor: The Advanced Settings opens up as a default tab for an image if that was the tab user opened for the last edited image,"Screenshot
+
+Steps to reproduced:
+
+1.Open a page with VE
+2.Insert an image and go to the advanced Settings to make some changes
+3.Apply the changes 
+4.Now insert another image and open the media settings for it
+
+Observed Result:
+Instead of starting from General Settings as default tab, it opens up the Advanced settings, moreover if you edited say the image size section of the last image, the scroll bar position for the newly added image is also at the same exact position.
+
+Test Environment:Betalabs, test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13579}",1400103600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vy4qb3tkuvo3pp2bvalh,task_description,declined
+VisualEditor: The Advanced Settings opens up as a default tab for an image if that was the tab user opened for the last edited image,Seems to have been fixed at some point.,1414094776,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vy4qb3tkuvo3pp2bvalh,task_subcomment,NA
+VisualEditor: The Advanced Settings opens up as a default tab for an image if that was the tab user opened for the last edited image,This sounds like a problem with BookletLayout. Trevor?,1400103732,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vy4qb3tkuvo3pp2bvalh,task_subcomment,NA
+Is it possible to set up VisualEditor on other skins instead of Vector skin?,"**Author:** `sean.chen`
+
+**Description:**
+hi,
+
+we are using MediaWiki for our intranet on Government of Ontario and we are amazed by the new and cool VisualEditor! And we want to set up VisualEditor while we upgrade our MediaWiki to version 1.23.x.
+
+However we need a customized skin instead of the default Vector skin. Is that possible to set up VisualEditor on a customized skin and how?
+
+thanks a lot,
+
+-Sean
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1400096640,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hebmh46ynxb5xtfcynmn,task_description,invalid
+Is it possible to set up VisualEditor on other skins instead of Vector skin?,"Also because this is for support, not an actual software issue, I have set it to resolved invalid.",1400097823,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hebmh46ynxb5xtfcynmn,task_subcomment,NA
+Is it possible to set up VisualEditor on other skins instead of Vector skin?,"Kind of relevant to this are my (WIP) notes on what VE expects of a skin, which you can find at bug 61500.",1400097722,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hebmh46ynxb5xtfcynmn,task_subcomment,NA
+Is it possible to set up VisualEditor on other skins instead of Vector skin?,"You can try setting $wgVisualEditorSupportedSkins[] = 'nameofyourskin'; in your configuration. If your skin is a derivative of one of the supported skins (vector, apex, monobook, minerva), this should come pretty close to making things work, with only a few CSS issues remaining. You can fix the CSS problems by copying and tweaking ve.init.mw.ViewPageTarget-vector.css and -vector-hd.css (or another one if your skin isn't based on Vector).
+
+Right now our skin integration is still a bit sucky. ve.init.mw.ViewPageTarget-shared.css needs to be loaded for all skins but isn't right now; I'll fix that. You also need to add your skin styles into VisualEditor.php itself (search for skinStyles), which is ugly. We'll need to work on improving that.
+
+In the meantime, feel free to pop into our IRC channel (#mediawiki-visualeditor on freenode) for interactive help.",1400097161,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hebmh46ynxb5xtfcynmn,task_subcomment,NA
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,"Steps to reproduce:
+
+1.Open a page with mobile VE
+
+Observed Result:
+
+The Cite option is appearing in the toolbar which is not supposed to be there just yet? The drop-down menu does not have any background layout.Clicking on any of the options make VE completely stuck
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400094420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_description,declined
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,This apparently was intentional. Now styled. :-),1401417868,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_subcomment,NA
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,"The dropdown appears to be unstyled in the mobile skin. Also, the mobile CSS that removes all text labels everywhere is probably undesirable in this case (and seems like overkill in general; it should be a conscious choice).",1400195537,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_subcomment,NA
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,This is now appearing in production as well after today's deployment,1400191472,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_subcomment,NA
+VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE,"Created attachment 15383
+Screenshot
+
+**Attached**: {F13527}",1400095261,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ndk7b6dff6ow5oi3ifru,task_subcomment,NA
+Raster icons missing from VE toolbar,"Toolbar with missing tool icons – undo, redo, all dropdown arrows, link, help, page notices, page options (several icons missing in the dropdowns too)
+
+If one forces VE to load with the raster icons, a bunch of them are missing.
+
+I'm not sure if this actually happens if any of the supported or greylisted browsers right now, but it blocks a fix for Opera 12 which doesn't handle elements with SVG background images and border-radius set.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14072}",1400005140,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_description,declined
+Raster icons missing from VE toolbar,"(In reply to Thiemo Mättig from comment #3)
+> (In reply to James Forrester from comment #2)
+> > We do not intend to load raster icons in VisualEditor.
+> 
+> You *do* load raster icons in VisualEditor.
+
+…
+
+> Are you planning to remove this feature?
+
+Yes, you're right, it was archaïc code we forgot to get rid of, and we should remove it. Done in gerrit 134758.",1400869128,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_subcomment,NA
+Raster icons missing from VE toolbar,"(In reply to James Forrester from comment #2)
+> We do not intend to load raster icons in VisualEditor.
+
+You *do* load raster icons in VisualEditor. Look:
+
+https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor/HEAD/modules%2Fve-mw%2Finit%2Fve.init.mw.Target.js
+https://git.wikimedia.org/tree/mediawiki%2Fextensions%2FVisualEditor/HEAD/modules%2Fve-mw%2Fui%2Fstyles
+https://git.wikimedia.org/tree/mediawiki%2Fextensions%2FVisualEditor/HEAD/modules%2Fve-mw%2Fui%2Fstyles%2Fimages%2Ficons
+
+Are you planning to remove this feature?",1400277284,PHID-USER-u6ycqhfpa3k4yvlpxjt2,False,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_subcomment,NA
+Raster icons missing from VE toolbar,We do not intend to load raster icons in VisualEditor.,1400009582,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_subcomment,NA
+Raster icons missing from VE toolbar,"Created attachment 15373
+Correctly rendered SVG toolbar
+
+(The Opera 12 fix I mentioned is Ieafeb9075f741fe6e2624c5c62cf2ea8138e63de.)
+
+**Attached**: {F14073}",1400005679,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-np4k3bluhrwdx3t7fl4r,task_subcomment,NA
+VisualEditor: Scroll bar appears to be a bit wider on hovering over it in Firefox,"scroll bar gets wider
+
+Steps to reproduce:
+
+1.Open a page with VE in Firefox
+2.Open any drop down box which has a scroll bar in it
+3.Hover over the scroll bar
+
+Observed Result:
+The scroll bar becomes a bit wider 
+
+See the video attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13998}",1399926660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-m6ahh3o7wiecdy5522i5,task_description,invalid
+VisualEditor: Scroll bar appears to be a bit wider on hovering over it in Firefox,That's OS behaviour when it thinks you want to manually interact with the scrollbar.,1401417923,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m6ahh3o7wiecdy5522i5,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","Seen in automated tests in beta labs 11 May and 12 May (and occasionally earlier). 
+
+Browser encounters a modal dialog saying ""Error loading data from server: readonly. The wiki is currently in read-only mode. Would you like to retry?""  The wiki is almost certainly not in read-only mode. 
+
+This may not actually be a VE error, I think it's coming from line 337 of ve.init.mw.ViewPageTarget.js, but I haven't tracked it to whatever is feeding the ""read-only"" status message to VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399915500,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cqabqcw62xkqwgp5vzag,task_description,resolved
+"false ""wiki is read-only mode"" message in beta labs","It seems the main issue was the database lag that would cause MediaWiki to switch readonly.  The threshold has been raised a few months ago and I have not heard of ""beta is read only"" issues since.
+
+Assuming this bug is fixed.",1414160812,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","
+Several failed builds with this error over the last few days, this is the most recent from last night 13 May: 
+
+https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/500/",1399994801,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","There is a few errors such as:
+
+Mon May 12 5:32:25 UTC 2014	deployment-apache01	testwiki	Error connecting to 10.68.17.94: :real_connect(): (42000/1049): Unknown database 'testwikidatawiki'
+Mon May 12 5:32:25 UTC 2014	deployment-apache01	testwiki	Connection error: No working slave server: Unknown error (10.68.17.94)
+
+
+Do you have an example of a failing build ? Will help find the exact time it happened and thus to investigate around that date/time.",1399986442,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","(11:08:16 AM) chrismcmahon: James_F:  I'm sure the read-only was not VE itself, but I do wonder if you've ever seen that msg. in VE or know what might cause it. 
+
+(11:09:16 AM) James_F: chrismcmahon: It happens locally when I lock the DB manually, and I've seen it when wikis are under high load in production due to the auto-lock.
+
+(11:09:31 AM) James_F: chrismcmahon: I believe it happens only in extremes, when master is lagging with load.
+
+(11:10:29 AM) chrismcmahon: James_F:  thanks, that's helpful, I've never seen that.  I can't imagine what would cause that kind of load in beta labs at that hour though.",1399918305,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","
+I've never seen this modal dialog or this error message under any circumstances other than when editing with VE. 
+
+I am curious as to the root cause though, I've never heard of a wiki automatically putting itself into read-only mode.",1399918007,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","Are you absolutely sure that Beta Labs wasn't catching up from too many edits? The site automatically puts itself into ""read only"" mode for a few seconds from time to time… Either way, this is a deployment-prep issue.",1399917099,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"false ""wiki is read-only mode"" message in beta labs","Created attachment 15357
+read-only status modal dialog in VE
+
+**Attached**: {F13976}",1399915600,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cqabqcw62xkqwgp5vzag,task_subcomment,NA
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again","Steps to Reproduce:
+1. Create a page that contains at least one image with no thumb or similar file specification, e.g., 
+
+[[File:Example.jpg|Here's an image.]]
+
+2. Open the page in VisualEditor.  
+
+3. Select the image and open the image inspector.
+
+4. Try to get out of the image inspector.
+
+Actual Results:  
+The ""Advanced settings"" pane in the image inspector has a spinning death spiral and the error message, ""Size values are invalid. Could not retrieve original file size."" 
+
+The X to close the image inspector does not respond.
+
+
+Reproducible: Always
+
+This was first reported by Magioladitis for the pdf's listed here:  https://el.wikipedia.org/w/index.php?oldid=4650532#.CE.94.CE.B9.CE.B1.CE.BB.CE.AD.CE.BE.CE.B5.CE.B9.CF.82
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399759500,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-7qyivx7mukqztl4bew6d,task_description,resolved
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again",Not exactly:  I selected it and pressed the Return key.  It has the same effect.,1399918730,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-7qyivx7mukqztl4bew6d,task_subcomment,NA
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again","Okay I just realized a huge bug: The image dialog popup/button doesn't appear (because it shouldn't yet) but double-clicking opens the media edit dialog.
+
+And since the image is inline, the dialog is not ready to handle it, the dialog then crashes.
+
+This seems to be a double-click bug; WhatamIdoing can you approve that this is how you opened the dialog?",1399914719,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-7qyivx7mukqztl4bew6d,task_subcomment,NA
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again","(In reply to Moriel Schottlender from comment #1)
+> This image is rendered as an inline image and the dialog, at the moment,
+> won't edit it at all. The editing capability for inline images is introduced
+> in the upcoming (big) change for the Image Model.
+> 
+> I've tried to reproduce the bug in both local master and in betalabs and the
+> image doesn't let me open the edit dialog (as expected)
+> 
+> See here:
+> http://en.wikipedia.beta.wmflabs.org/wiki/
+> 2014_May_11_TestImageBug?veaction=edit
+> 
+> Am I missing something?
+
+Double clicking the image opens the ""Media settings"" dialog for me.",1399914493,PHID-USER-zjzhrhmn36icnzbckqy4,True,PHID-TASK-7qyivx7mukqztl4bew6d,task_subcomment,NA
+"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again","This image is rendered as an inline image and the dialog, at the moment, won't edit it at all. The editing capability for inline images is introduced in the upcoming (big) change for the Image Model.
+
+I've tried to reproduce the bug in both local master and in betalabs and the image doesn't let me open the edit dialog (as expected)
+
+See here: http://en.wikipedia.beta.wmflabs.org/wiki/2014_May_11_TestImageBug?veaction=edit
+
+Am I missing something?",1399914138,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-7qyivx7mukqztl4bew6d,task_subcomment,NA
+"VisualEditor:  Firefox displays new lists incorrectly, if you've just pasted the text onto the page","Steps to Reproduce:
+1. Type a few paragraphs of plain text in another document (e.g., an e-mail message with rich text turned off).
+
+2. Open VisualEditor.  Copy and paste your paragraphs into VisualEditor.
+
+3. Place your cursor in the first paragraph.  Click the list button to turn the first line (only) into a list.
+
+Actual Results:  
+The entire pasted section is indented as if it were a list (a list separated by <br>, not with a bullet in front of each paragraph).
+
+However, when you save the page, only the first paragraph has actually been turned into a list.
+
+See you at http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=92716&oldid=92715
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399489680,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-bxloupudebssszvcsfyv,task_description,declined
+"VisualEditor:  Firefox displays new lists incorrectly, if you've just pasted the text onto the page","Created attachment 15315
+Photo collage showing before-and-after difference in formatting
+
+**Attached**: {F14093}",1399492243,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-bxloupudebssszvcsfyv,task_subcomment,NA
+VisualEditor: The suggestion dropdown box gets stuck inside the transclusion dialog box in Firefox when you click on Add template button as soon as the dropdown box appears,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Type something in the textbox
+4.As soos as the suggestion dropdown box for template appears click on ""Add template"" button
+
+Observed Result:
+The first suggestion of the dropdown box gets stuck in the transclusion dialog box
+
+See the screenshot attached
+
+Browser:Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14019}",1399419540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6xcbbe4kcyhfokfy2ccf,task_description,declined
+VisualEditor: The suggestion dropdown box gets stuck inside the transclusion dialog box in Firefox when you click on Add template button as soon as the dropdown box appears,Can't reproduce,1414095454,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6xcbbe4kcyhfokfy2ccf,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,"In LocalSettings.php I enabled scary transclusions:
+$wgEnableAPI = true;
+$wgEnableWriteAPI = true;
+$wgEnableScaryTranscluding = true;
+$wgTranscludeCacheExpiry = 0;
+
+Then in a template I have this:
+{{raw:lo::{{{1}}}}}
+
+I see this in the log:
+[info][localhost:Test] starting parsing
+[warning/api][localhost:Test][oldid:306] Failed API request, 8 retries remaining.
+... and so on.
+
+If just {{raw:lo::someItem}} is on the page parsoid evaluates this OK. But when this is in a template the requests fail for some reason.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399359720,PHID-USER-6fjfcuicwjgrpuv3znmv,False,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_description,resolved
+Templates using interwiki transclusions fails at API request,"This works now, I do not know what have happend but works, with both prefixes I inserted in the db :)",1399660124,PHID-USER-6fjfcuicwjgrpuv3znmv,False,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,Can you try with {{raw:lowiki::xxx}} for prefix lo. Just a hunch.,1399579704,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,"Oh, yikes, I missed the ""interwiki"" in the subject line. Thanks for the clarification.",1399579499,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,"Sorry, {{raw:lo::xxx}} should transclude template xxx from wiki with prefix 'lo'. This is what I did:
+
+1) Create a template containing just plain text on a wiki (A).
+2) From another wiki (B), make sure you have scary transclusion enabled and the other wiki in the transclusion database.
+3) Make a template that transcludes the template from wiki A.
+4) Create a page at wiki B the template you created in step 3.",1399579335,PHID-USER-6fjfcuicwjgrpuv3znmv,False,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+Templates using interwiki transclusions fails at API request,"I'm having trouble reproducing this bug. Here's what I did:
+
+1) Create a template Template:Lo::someItem with the content: Hi
+2) Create a template Template:Another with the content: {{raw:lo::{{{1}}}}}
+3) Create a page Testing with the content: {{another|someItem}}
+
+Result on Testing is: Hi
+
+I can edit all of the above in VisualEditor.",1399578663,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-qkmncwgadvm2zyw4ptz7,task_subcomment,NA
+"VisualEditor:  Adding citations inside hieroglyphics, gallery, or mathematics blocks results in the inspector never closing","Intention:
+Add a citation inside (not after) a hieroglyphics block.
+
+Steps to Reproduce:
+1. Open page containing hieroglyphics.  Open hierglyphics tool.
+
+2. Open Citation tool (or Insert > Reference).  Add citation.  
+
+3. Close citation tool (""Apply changes"").
+
+
+
+Actual Results:  
+The refernce is correctly added, but the hieroglyphics inspector stays open and empty until you save the page.
+
+
+Reproducible: Always
+
+Bonus bug:
+
+Before saving page, try editing a nearby link, gallery, or math formula.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399321380,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lfivv2gwageaek5qpppw,task_description,resolved
+"VisualEditor:  Adding citations inside hieroglyphics, gallery, or mathematics blocks results in the inspector never closing","
+
+*** This bug has been marked as a duplicate of bug 56644 ***",1399333995,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-lfivv2gwageaek5qpppw,task_subcomment,NA
+MathJax menus (in Math extension) are not localized into Vietnamese,"When MediaWiki's interface language is set to Vietnamese and MathJax rendering is turned on, the MathJax menus appear in English even though a Vietnamese localization is available. This issue does not occur when uselang=es etc.
+
+Steps to reproduce:
+
+1. Go to [[mw:Special:Preferences#mw-prefsection-rendering]] and turn on MathJax.
+2. Change the interface language to Vietnamese.
+3. Go to [[mw:User:Mxn/MathJax vi]] and right-click on the matrix.
+
+Expected results:
+
+The menus should all be translated, as they are at <https://github.com/mathjax/MathJax-i18n/tree/master/JSON/vi>.
+
+Actual results:
+
+All the menus are in English.
+
+Note that MathJax-i18n was missing entries in config.js for a number of languages, including Vietnamese, until very recently: <https://github.com/mathjax/MathJax-i18n/pull/1>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:Mxn/64809",1399157340,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_description,resolved
+MathJax menus (in Math extension) are not localized into Vietnamese,"**physik** wrote:
+
+OK. But it will be resolved by upgrading to MathJax 2.4. So it's the same problem
+
+%%%*** This bug has been marked as a duplicate of bug 70207 ***%%%",1413756495,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_subcomment,NA
+MathJax menus (in Math extension) are not localized into Vietnamese,"(In reply to physikerwelt from comment #2)
+> https://www.mediawiki.org/wiki/User:Mxn/64809?veaction=edit looks good for
+> me.
+
+This bug doesn't relate to VisualEditor. If I right-click on the matrix in [[mw:User:Mxn/64809]], the context menu is still in English, with items such as ""Show Math As"".",1413752347,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_subcomment,NA
+MathJax menus (in Math extension) are not localized into Vietnamese,"**physik** wrote:
+
+https://www.mediawiki.org/wiki/User:Mxn/64809?veaction=edit looks good for me.",1413748559,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_subcomment,NA
+MathJax menus (in Math extension) are not localized into Vietnamese,"As you mentioned, this is fixed upstream but not yet released -- the upcoming MathJax v2.4 will have the updated locale.",1399281849,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-b5mzjxluwzhdjnamwvwg,task_subcomment,NA
+VisualEditor: Math inspector is not working in Betalabs,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert  a math function with math inspector
+
+Observed Result:
+Nothing gets added
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399055580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6cgiws4wsgspk77z65mb,task_description,declined
+VisualEditor: Math inspector is not working in Betalabs,This works for me… Maybe a caching issue?,1399079949,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6cgiws4wsgspk77z65mb,task_subcomment,NA
+"""VisualEditor language tool"" beta feature links on test2 are broken","https://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures
+
+Under ""VisualEditor language tool"", if I click discussion or information I get sent to https://test2.wikipedia.org/wiki/&lt;visualeditor-preference-experimental-info-link&gt; or https://test2.wikipedia.org/wiki/&lt;visualeditor-preference-experimental-discussion-link&gt;
+
+Localisation cache issue?
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**URL**: https://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures",1398992040,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-qjbo7xdeq7skmyh72eli,task_description,declined
+"""VisualEditor language tool"" beta feature links on test2 are broken","Links to https://www.mediawiki.org/wiki/VisualEditor/Beta_Features/Language and https://www.mediawiki.org/wiki/Talk:VisualEditor/Beta_Features/Language for me now.
+Closing as WORSKFORME (please reopen if still a problem).",1401709351,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-qjbo7xdeq7skmyh72eli,task_subcomment,NA
+VisualEditor:  You shouldn't be able to set bold or other text attributes for ref tags,"Steps to Reproduce:
+1.  Select a ref tag.
+
+2.  Click on bold in the character formatting menu.
+
+
+
+Actual Results:  
+It dutifully adds the character formatting:  <ref>Foo</ref> becomes '''<ref>Foo</ref>'''
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=91700&oldid=91692
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1398979980,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jx5wa6pf2qanvuyvggpu,task_description,invalid
+VisualEditor:  You shouldn't be able to set bold or other text attributes for ref tags,"If it's ""valid"", then why doesn't it do anything?  
+
+'''<ref>Foo</ref>''' doesn't actually produce a bold-faced [1].
+
+I see your point about (b) but you can't see the existence of the misplaced bold in VisualEditor, so I doubt that anyone would actually use it to fix it.",1399237665,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jx5wa6pf2qanvuyvggpu,task_subcomment,NA
+VisualEditor:  You shouldn't be able to set bold or other text attributes for ref tags,"Why not? This is entirely valid, and relatively common, wikitext… VE has to let you make all kinds of stupid stylistic errors, because (a) it's our job to let you do anything you can validly do in wikitext, and (b) you might want to use VE to correct such things, which stripping in VE would prevent.",1399080407,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jx5wa6pf2qanvuyvggpu,task_subcomment,NA
+VisualEditor:  You shouldn't be able to set bold or other text attributes for ref tags,"It's not just refs:  templates, hieroglyphics, galleries, math equation... Not images, though.
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=91706&oldid=91700",1398980268,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jx5wa6pf2qanvuyvggpu,task_subcomment,NA
+VisualEditor Mobile: Mobile VE is redirecting to Google while trying to save a page,"For Chrome
+
+Steps to reproduce:
+
+1.Open this link:https://test2.m.wikipedia.org/wiki/0.8863089695452125?title=0.8863089695452125&campaign=random#editor/0
+
+2.Make some edit
+
+3.Save the page
+
+Observed Result:
+
+In Chrome: The page suddenly disappears and redirects me to Google Search Page 
+In FireFox: It keeps the VE edit mode open 
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13949}",1398901080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rwiwk6z77szqe2xi53tu,task_description,resolved
+VisualEditor Mobile: Mobile VE is redirecting to Google while trying to save a page,"
+
+*** This bug has been marked as a duplicate of bug 60848 ***",1398908742,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-rwiwk6z77szqe2xi53tu,task_subcomment,NA
+VisualEditor Mobile: Mobile VE is redirecting to Google while trying to save a page,"Created attachment 15260
+for Firefox
+
+**Attached**: {F13950}",1398901148,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rwiwk6z77szqe2xi53tu,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Right now, if you switch to alpha mode and click the edit button on a page like...
+https://en.m.wikipedia.org/wiki/User_talk:Kaldari
+...you get an error since VisualEditor is disabled for that namespace on en.wiki.
+
+To fix this, we need to surface the config settings in wmgVisualEditorNamespaces on the client-side and use it in the editor loading process in editor.js.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398892320,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-aaldjasjdqcsgs4dgei6,task_description,resolved
+Don't try to load VisualEditor in namespaces where it isn't supported,"Change 132124 merged by jenkins-bot:
+Only create editor switcher from wikitext editor if VE is usable
+
+https://gerrit.wikimedia.org/r/132124",1399507171,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Change 132124 had a related patch set uploaded by Kaldari:
+Only create editor switcher from wikitext editor if VE is usable
+
+https://gerrit.wikimedia.org/r/132124",1399504025,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Change 130794 merged by jenkins-bot:
+Make sure mobile VisualEditor is only loaded when appropriate
+
+https://gerrit.wikimedia.org/r/130794",1398985053,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Change 130794 had a related patch set uploaded by Kaldari:
+Make sure mobile VisualEditor is only loaded when appropriate
+
+https://gerrit.wikimedia.org/r/130794",1398903985,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"Looks like the information is already available on the client-side:
+mw.config.get( 'wgVisualEditorConfig' ).namespaces",1398893246,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+Don't try to load VisualEditor in namespaces where it isn't supported,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/cZTY61hQ",1398892516,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aaldjasjdqcsgs4dgei6,task_subcomment,NA
+VisualEditor: Inserting Media fails when caret is not positioned after initialization,"Original bug title:
+VisualEditor: Inserting Media fails when caret is not positioned after initialization
+
+And this is how to reproduce the issue:
+* Go to https://www.mediawiki.org/wiki/Sandbox?veaction=edit
+* Confirm the ""This is our new tool ....""
+* Reload the page
+* Press ""Insert""
+* Press ""Media"" (dialog opens)
+* Click one of the images.
+
+Result:
+Mozilla Firefox:
+* POST https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 281ms]
+** http://pastebin.de/124264
+* TypeError: splice is undefined load.php:153
+** http://pastebin.de/124263
+* Nothing happens except that the dialog is closed.
+* Pressing ""Insert"" -> ""Media"" now does not open any dialog
+
+Opera Next:
+* Uncaught TypeError: Cannot read property 'apply' of undefined VM140:146
+* Nothing happens except that the dialog is closed.
+* Pressing ""Insert"" -> ""Media"" now does not open any dialog
+* Stacktrace: http://pastebin.de/124262
+
+--------------
+Expected:
+* Image inserted
+* Being able to add further images to the page
+
+--------------
+Unrelated question:
+* Why are you using FormData for this specific request?
+
+
+
+--------------
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64759",1398776460,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-rtprhlspp44bc3deup2j,task_description,resolved
+VisualEditor: Inserting Media fails when caret is not positioned after initialization,"
+
+*** This bug has been marked as a duplicate of bug 64434 ***",1399065928,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rtprhlspp44bc3deup2j,task_subcomment,NA
+VisualEditor: Have redirected links in green at the edit mode,"In VisualEditor When we are at the edit mode it doesn't show redirected internal links in green.
+
+It can be as an option in top tool box or in setting part
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398748440,PHID-USER-dswbdv7ibhsefllcqarz,False,PHID-TASK-r5dtguf5lpskmwirqnjk,task_description,resolved
+VisualEditor: Have redirected links in green at the edit mode,"VisualEditor is designed to look like the read mode; having redirects as green for read mode is bug 166, and making VE copy them if they change is bug 61072, so merging with that.
+
+*** This bug has been marked as a duplicate of bug 61072 ***",1401417534,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-r5dtguf5lpskmwirqnjk,task_subcomment,NA
+VisualEditor:  Math formula does not display correctly if preferences are set to both TeX and MathJax,"Steps to Reproduce:
+1. Enable VisualEditor formulae editing at Special:Preferences#mw-prefsection-betafeatures.
+
+2. Change math-related preferences to:
+   * Leave it as TeX (for text browsers) (radio button; it's off by default)
+   * MathJax (experimental; best for most browsers) (tick box; it's off by default)
+
+3. Open a page like [[:w:Torque]] in VisualEditor.
+
+4. Select a math formula from the page.
+
+5. Open the math editing tool.
+
+6. Change some thing in the formula (e.g., replace ""alpha"" with ""beta"").
+
+7. Look at the mess in the new version of the math formula (the one on the page, not the TeX code in the editing tool).
+
+
+
+Reproducible: Always
+
+See screenshots here:
+
+https://en.wikipedia.org/wiki/File:Bug_with_using_VE_and_mathjax.png
+
+https://commons.wikimedia.org/wiki/File:MathJax_mess_2014-04-28_at_2.33.08_PM.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398721500,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-i2hkjs3uujagjhxf5ecx,task_description,resolved
+VisualEditor:  Math formula does not display correctly if preferences are set to both TeX and MathJax,"
+
+*** This bug has been marked as a duplicate of bug 60728 ***",1402295506,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-i2hkjs3uujagjhxf5ecx,task_subcomment,NA
+VisualEditor:  Math formula does not display correctly if preferences are set to both TeX and MathJax,"The CSS problem is caused by this rule
+
+.ve-ce-protectedNode, .ve-ce-protectedNode * {
+  position: relative !important;
+  top: 0 !important;
+  left: 0 !important;
+  bottom: 0 !important;
+  right: 0 !important;
+  ...
+}
+
+MathJax makes heavy use of absolute positioning with elements like 
+
+<span style=""font-family: MathJax_Size4; position: absolute; top: -1.624em; left: 0.003em;"">⎜<span style=""display: inline-block; width: 0px; height: 3.975em;""></span></span>
+
+so the .ve-ce-protectedNode CSS overrides all the positioning creating the mess.",1398752231,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-i2hkjs3uujagjhxf5ecx,task_subcomment,NA
+VisualEditor:  Math formula does not display correctly if preferences are set to both TeX and MathJax,"See https://en.wikipedia.org/w/index.php?oldid=606239634#Problem_with_MathJax_and_visual_editor. for an analysis of CSS-related issues.  MathJax uses absolute positioning, and VisualEditor uses relative positioning.",1398721663,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-i2hkjs3uujagjhxf5ecx,task_subcomment,NA
+VisualEditor: Pressing Return at the end of the document throws  Error: Offset could not be translated to a DOM element and offset: 675,"Screenshot
+
+Steps to reproduce:
+
+
+1.Go to the last line of this page:http://en.wikipedia.beta.wmflabs.org/wiki/28thAprilChrome?veaction=edit
+
+2.Press return
+
+Observed Result:
+
+An error appears in the console:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 675 
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13655}",1398716100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j2ivwzlbwna3s5gipwur,task_description,resolved
+VisualEditor: Pressing Return at the end of the document throws  Error: Offset could not be translated to a DOM element and offset: 675,Re-checked the page and the test scenario - no errors displayed in Console; Save button works as expected. Closing the issue as resolved.,1425602082,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-j2ivwzlbwna3s5gipwur,task_subcomment,NA
+VisualEditor: Pressing Return at the end of the document throws  Error: Offset could not be translated to a DOM element and offset: 675,"After the above steps if you click on ""Save Page"" dialog box and close it.
+Then again try to click on ""Save Page"" button it does not do anything.",1398717091,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j2ivwzlbwna3s5gipwur,task_subcomment,NA
+VisualEditor: PHP Notice on undefined index,"Patch for php notice
+
+PHP Notice:  Undefined index: visualeditor-enable-language in extensions/VisualEditor/VisualEditor.hooks.php on line 402
+
+Attaching patch since I can't submit to gerrit from here.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13607}",1398698640,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-nxkrip2qpu45o4qn32qd,task_description,resolved
+VisualEditor: PHP Notice on undefined index,Fixed in gerrit 130496.,1399082873,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nxkrip2qpu45o4qn32qd,task_subcomment,NA
+VisualEditor:  Cutting and pasting an {{essay}} template (containing shortcuts) resulted in a different template displaying,"Intention:
+Move a tag from the middle of a page to the top.
+
+Steps to Reproduce:
+See https://en.wikipedia.org/w/index.php?title=User:WhatamIdoing/Sandbox_3&diff=606088818&oldid=606088072 for the (entirely correct) diff.
+
+1. Select the essay tag in the middle of the page.
+
+2. Command-X to cut it.
+
+3. Scroll to the top.  Place cursor in the slug at the top.  Command-V to paste it.
+
+
+Actual Results:  
+The template that was displayed (upon pasting) does not look like the template that was cut.  It showed a ""clean up"" broom.
+
+The changes to the wikitext (upon saving) were correct, and the template displayed correctly upon refresh (after saving).
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1398633600,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qc5trqqgz5vloi4oqng6,task_description,resolved
+VisualEditor:  Cutting and pasting an {{essay}} template (containing shortcuts) resulted in a different template displaying,"Created attachment 15227
+The essay tag (the top one) as it should have appeared upon pasting, and as it did appear after saving the page.
+
+**Attached**: {F13515}",1398633763,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qc5trqqgz5vloi4oqng6,task_subcomment,NA
+VisualEditor:  Cutting and pasting an {{essay}} template (containing shortcuts) resulted in a different template displaying,"Created attachment 15226
+The essay tag, pasted at the top.  It does not look like what I cut from the middle.
+
+**Attached**: {F13514}",1398633728,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qc5trqqgz5vloi4oqng6,task_subcomment,NA
+VisualEditor:  Cutting and pasting an {{essay}} template (containing shortcuts) resulted in a different template displaying,"Created attachment 15225
+The essay tag, as seen originally in the middle of the page
+
+**Attached**: {F13513}",1398633681,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qc5trqqgz5vloi4oqng6,task_subcomment,NA
+VisualEditor won't start - With correct config,"**Author:** `petter.viippola`
+
+**Description:**
+I've done these steps and VisualEditor still dosen't work. There seems to be a problem with loading VisualEditor. I can only edit source, the command edit isn't possible to use. I've removed all the Parsoid options.
+
+cd extensions
+git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git  
+cd VisualEditor
+git submodule update --init
+
+require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");
+
+$wgDefaultUserOptions['visualeditor-enable'] = 1;
+ 
+
+$wgHiddenPrefs[] = 'visualeditor-enable';
+
+Everything else seems to be working the wiki, with got it ad-connected. Can there be any issues regarding to that?
+
+Best regards
+Petter
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Linux
+**Platform**: PC",1398424980,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_description,declined
+VisualEditor won't start - With correct config,Did this issue get resolved? I'm tempted to mark these sorts of entries as resolved worksforme.,1414808894,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor won't start - With correct config,"**petter.viippola** wrote:
+
+We are getting some other strange errors if we try with chrome on a testclient.
+server:parsoidserver-http-curl-error: couldn't connect to host.
+
+Does this mean we have the wrong configuration in the localsettings.js file?
+
+Best regards
+Petter",1398781795,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor won't start - With correct config,"**petter.viippola** wrote:
+
+[Mon Apr 28 14:39:36 2014] [error] [client 10.1.101.39] PHP Notice:  Undefined index: visualeditor-enable-language in /var/www/mediawiki-1.22.5/extensions/VisualEditor/VisualEditor.hooks.php on line 402, referer:http://wiki.ad.xxxxxx.se/index.php?title=SpaceClaim&action=edit
+
+This is the only error we get in the httpd, error.log.
+
+Best Regards
+
+Petter",1398696608,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor won't start - With correct config,"**petter.viippola** wrote:
+
+I can look tomorrow when i get back to work.
+
+The logs dosen't give any intresseting entries about problems with loading the VisualEditor.
+There is no errors when i open a page, log in et.c. That's the strange part.
+
+We have tried with chrome/""the wrong ie8"". I noticted it wasn't supported by IE, so we tried chrome but it was the same result.
+
+Best Regards
+
+Petter",1398627888,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor won't start - With correct config,"Does VisualEditor show up on Special:Version?
+
+If no, are there entries in your PHP error logs on the server?
+
+If yes, are there errors in your JS console on your client when you open a page?
+
+(What browser are you using? Note that Internet Explorer and a number of other elderly browser versions don't work with VisualEditor yet.)",1398471355,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v4yeqp4ktfp26rooyyb4,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot read property 'nodeType' of undefined appears while trying to add a newline after clicking on Edit Beta for Page Title heading,"screenshot
+
+Steps to Reproduce:
+
+1.Go to this page: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit
+
+2.Click on Edit beta for the Page Title
+
+3.Now press return after any line to add a new line in the page
+
+Observed Result:
+
+An error appears in the console:
+Uncaught TypeError: Cannot read property 'nodeType' of undefined 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&oldid=605655480
+
+**Attached**: {F13859}",1398372300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iro4l3sspq3bi2nblqmz,task_description,declined
+VisualEditor: Uncaught TypeError: Cannot read property 'nodeType' of undefined appears while trying to add a newline after clicking on Edit Beta for Page Title heading,This now works for me – deployment glitch?,1399083059,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iro4l3sspq3bi2nblqmz,task_subcomment,NA
+"VisualEditor:  ""Unknown error"" corrupts page upon saving, but saving again fixes the problems it created","Actual Results:  
+TeamGale added some citations and then saved the page.  She received an ""unknown error"" and assumed that the page did not get saved.  So she saved the page again.  Upon checking the history, she found that both attempts to save the page had resulted in a new version:
+
+https://en.wikipedia.org/w/index.php?title=Sakis_Rouvas&diff=605148987&oldid=605133988
+
+https://en.wikipedia.org/w/index.php?title=Sakis_Rouvas&diff=605149076&oldid=605148987
+
+However, the first diff removed the end of the page, including the reference secyion, external links, navboxes, succession boxes, categories, and more.  These were automagically restored when she saved the second time.
+
+
+Reproducible: Didn't try
+
+TeamGale usually edits with Firefox 28 on Windows 8.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398359400,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-227untois7bfweaz7mct,task_description,resolved
+"VisualEditor:  ""Unknown error"" corrupts page upon saving, but saving again fixes the problems it created",Provisionally marking this as 'Resolved' as no reported recurrences in two years.,1459666953,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-227untois7bfweaz7mct,task_subcomment,NA
+VisualEditor-doc-publish jobs are failing,"See for example https://integration.wikimedia.org/ci/job/mwext-VisualEditor-doc-publish/2336/console from https://gerrit.wikimedia.org/r/#/c/129372/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1398327960,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-vbe43kp33h3r5mdxnudc,task_description,resolved
+VisualEditor-doc-publish jobs are failing,Job is now passing: https://integration.wikimedia.org/ci/job/mwext-VisualEditor-doc-publish/2337/console,1398342116,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vbe43kp33h3r5mdxnudc,task_subcomment,NA
+VisualEditor-doc-publish jobs are failing,"Change 129401 merged by jenkins-bot:
+Revert ""mwext-VisualEditor-doc-publish: Simplify rsync calls""
+
+https://gerrit.wikimedia.org/r/129401",1398342097,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vbe43kp33h3r5mdxnudc,task_subcomment,NA
+VisualEditor-doc-publish jobs are failing,"Change 129401 had a related patch set uploaded by Hashar:
+Revert ""mwext-VisualEditor-doc-publish: Simplify rsync calls""
+
+https://gerrit.wikimedia.org/r/129401",1398341788,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vbe43kp33h3r5mdxnudc,task_subcomment,NA
+VisualEditor-doc-publish jobs are failing,"Caused by https://gerrit.wikimedia.org/r/#/c/125546/2/mediawiki-extensions.yaml,unified which uses a a dest dir:  $$WORKSPACE/docs/lib  :-D",1398341642,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vbe43kp33h3r5mdxnudc,task_subcomment,NA
+"VisualEditor: The default size is not getting applied on an image after clicking on ""Apply Changes""","Steps to reproduce:
+
+1.Go to this page:https://test2.wikipedia.org/w/index.php?title=22ndaprilFF&veaction=edit
+
+2.Select the image:""K"" which is now in 220x200 px size
+
+3.Now go to Advanced Settings and select the tab ""Default"" and click on ""Apply changes""
+
+Observed Result:
+It turns the image into full size 600x600 px
+
+Also,
+If you first make the image as full size, then click on default size and click on ""Apply Changes"" nothing happens
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398277140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u6jklhcw662pkjycjvtd,task_description,invalid
+"VisualEditor: The default size is not getting applied on an image after clicking on ""Apply Changes""",Agreed; basic images have a default size of full size.,1401213398,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u6jklhcw662pkjycjvtd,task_subcomment,NA
+"VisualEditor: The default size is not getting applied on an image after clicking on ""Apply Changes""","Yes, it turns the image to 600x600 because it's the image's original dimensions, which are considered ""default"" for image of the type ""basic"".
+
+This is intended behavior.",1398278613,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-u6jklhcw662pkjycjvtd,task_subcomment,NA
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Edit something
+3.Save the page
+4.Without scrolling the page, again reopen the VE for that page
+
+Observed Result:
+
+""Success! Your edit was saved"" message stays in the VE mode .
+
+See the screenshot too
+
+Test Environment: https://test2.m.wikipedia.org/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13581}",1398213660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2vhxquft7zgsd3wwscky,task_description,resolved
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","Change 130782 merged by jenkins-bot:
+Close drawers/toasts on a click event
+
+https://gerrit.wikimedia.org/r/130782",1399336225,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2vhxquft7zgsd3wwscky,task_subcomment,NA
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","Change 130782 had a related patch set uploaded by Jdlrobson:
+Close toasts on a click event
+
+https://gerrit.wikimedia.org/r/130782",1398902609,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2vhxquft7zgsd3wwscky,task_subcomment,NA
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1958",1398279610,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2vhxquft7zgsd3wwscky,task_subcomment,NA
+"VisualEditor Mobile: ""Success! Your edit was saved"" message stays in the VE mode unless user scrolls down the page","We should probably dismiss this message when the user opens VE again.
+
+Sounds like this code is in MobileFrontend.",1398279558,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2vhxquft7zgsd3wwscky,task_subcomment,NA
+Not getting any result for VisualEditor media search in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Type something on the search box to search for a media
+
+
+Observed Result:
+No search results for images appears in the dialog
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13537}",1398192600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ycn3ic72wlfp37rtzxzr,task_description,resolved
+Not getting any result for VisualEditor media search in Betalabs,"(In reply to Alex Monk from comment #2)
+> Hmm... Reminds me of bug 63989
+
+No, this was a deployment issue with the Beta Labs move.",1398280580,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ycn3ic72wlfp37rtzxzr,task_subcomment,NA
+Not getting any result for VisualEditor media search in Betalabs,Hmm... Reminds me of bug 63989,1398276745,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ycn3ic72wlfp37rtzxzr,task_subcomment,NA
+Not getting any result for VisualEditor media search in Betalabs,This is now fixed .I am getting search results for the media now,1398274843,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ycn3ic72wlfp37rtzxzr,task_subcomment,NA
+VisualEditor: Can't save after editing categories,"It just happened to me on both Chrome and FF, Win 7, Vector. 
+If I remove a category on it.wp, that's not considered as a change? The Save button stays grey. I need to type something and then delete it in order to be able to save my edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398173340,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-6nnrbmhm34zvreojlgpl,task_description,declined
+VisualEditor: Can't save after editing categories,At least provisionally…,1406320242,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6nnrbmhm34zvreojlgpl,task_subcomment,NA
+VisualEditor: Can't save after editing categories,Can you still not reproduce this issue? Maybe this should be marked worksforme.,1406315448,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-6nnrbmhm34zvreojlgpl,task_subcomment,NA
+VisualEditor: Can't save after editing categories,"Yes. Although as of now, I can't reproduce this issue, so I'm bringing it back to unconfirmed.",1398246189,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-6nnrbmhm34zvreojlgpl,task_subcomment,NA
+VisualEditor: Can't save after editing categories,"Once you do type something and delete it, does the category get removed in the edit?",1398199599,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-6nnrbmhm34zvreojlgpl,task_subcomment,NA
+VisualEditor: VE should have a toolbar icon for cut-copy-paste,"Right now, we have cut-copy-paste feature in VE but there is no icon for these Clipboard actions.
+It would be nice to have them on the toolbar as it is a pretty good feature with no visual indication that it exists.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398119700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wqkvsiwaq4pnd2lugivq,task_description,declined
+VisualEditor: VE should have a toolbar icon for cut-copy-paste,"WONTFIXing, but really this is CANTFIX, sadly.",1398124464,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wqkvsiwaq4pnd2lugivq,task_subcomment,NA
+VisualEditor: VE should have a toolbar icon for cut-copy-paste,Google Docs shows that message in non-Chrome browsers. In Chrome browsers it asks you to install a plugin. Basically this is impossible due to the (fairly sensible) browser security model.,1398120899,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqkvsiwaq4pnd2lugivq,task_subcomment,NA
+VisualEditor: VE should have a toolbar icon for cut-copy-paste,"Triggering a cut/copy/paste from JavaScript might be hard due to security restrictions :( . Google Docs, for instance, has cut/copy/paste actions in the edit menu, but if you try to use them you get a dialog that says ""these actions are unavailable via the Edit menu, but you can still use Ctrl+X / Ctrl+C / Ctrl+V"".
+
+We might be able to do this using execCommand though, but I don't know how well that works and how reliable it is. CC Ed because he's done a bunch of work on contentEditable copy/paste in the past so he might know more.",1398120066,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wqkvsiwaq4pnd2lugivq,task_subcomment,NA
+VisualEditor: Citation dialog does not focus correct field when adding parameter,"In the template dialog, when you add a parameter, that parameter's input field is then focused. This makes perfect sense. In the citation dialog, this doesn't happen, and instead the input field that was focused most recently is focused.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398112620,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ocb7ebf4v6bjoboovjt4,task_description,resolved
+VisualEditor: Citation dialog does not focus correct field when adding parameter,"
+
+*** This bug has been marked as a duplicate of bug 64098 ***",1398112734,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ocb7ebf4v6bjoboovjt4,task_subcomment,NA
+"VisualEditor: Cite Options dialog has ""Show Options"" button enabled when it is inside Reference Dialog box but not when they are added in Main CE or inside Media Settings dialog","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Cite> Website/Book/Newspaper/Journal 
+3.Observe that, Cite Options dialog does not have ""Show Options"" button
+4.Now open a reference dialog box and Go to Cite>Cite> Website/Book/Newspaper/Journal
+
+Observed Result:
+In this case, there is a ""Show Options"" button for Cite options
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/21staprilchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14020}",1398105780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qcrmoxueaa23emzyho3c,task_description,declined
+"VisualEditor: Cite Options dialog has ""Show Options"" button enabled when it is inside Reference Dialog box but not when they are added in Main CE or inside Media Settings dialog","This is pretty much intentional; citation templates that aren't the only thing in a reference (or aren't even in a reference) get the citation icon, but aren't ""real"" citations. For now I'm WONTFIXing this.",1398113113,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qcrmoxueaa23emzyho3c,task_subcomment,NA
+VisualEditor cut off last several characters of article text during two edits at pl.wp,"VisualEditor cut off last several characters of article text during two edits at pl.wp.
+
+https://pl.wikipedia.org/w/index.php?diff=39198236
+https://pl.wikipedia.org/w/index.php?diff=39246345
+
+These are two consecutive edits to the same article, [[pl:Lamborghini Aventador]].
+
+Content maiming → marking as 'major'.
+
+Originally reported at https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Lamborghini_Aventador_-_ko.C5.84cowe_znaki by WTM.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398083820,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6ronffn6fe4mqkisco3e,task_description,resolved
+VisualEditor cut off last several characters of article text during two edits at pl.wp,Can't reproduce. Reopen if you can.,1437686737,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-6ronffn6fe4mqkisco3e,task_subcomment,NA
+font-size in VisualEditor is smaller than view mode,"It seems typography refresh enlarged body font size but VE didn't follow this change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397885100,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ogvz5uh6cxjgnxeelh7e,task_description,resolved
+font-size in VisualEditor is smaller than view mode,"
+
+*** This bug has been marked as a duplicate of bug 63985 ***",1397903906,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-ogvz5uh6cxjgnxeelh7e,task_subcomment,NA
+VisualEditor:  Re-used references don't always match,"Intention:
+Remove a copyright violation
+
+Steps to Reproduce:
+I removed the first instance of a ref tag.  See https://en.wikipedia.org/w/index.php?title=Male_rape&diff=604793477&oldid=604792987
+
+
+Actual Results:  
+The re-used ref was ""moved"", but that had the effect of changing it, because the next instance of the same named ref had a different description.
+
+
+Reproducible: Didn't try
+
+I don't know how to solve this.  The wikitext shouldn't have been written that way in the first place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1397856060,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-d2r6gtoaqlgf6litoxhf,task_description,declined
+VisualEditor:  Re-used references don't always match,"(In reply to WhatamIdoing from comment #2)
+> There's no way for VisualEditor to know which is the ""right"" ref when two
+> refs have the same name but different content.  I've seen this occasionally,
+> and the ""mismatched"" refs sometimes have functionally the same content
+> (e.g., one with a typo or abbreviation not present in the other).
+> 
+> We could pop up an message about the error in the wikitext (which is
+> probably something that should be done by MediaWiki, not VisualEditor).  In
+> VisualEditor, we could rename the refs to force them to be separated.   Or
+> we could do nothing, and maintain bug-for-bug compatibility with Cite.php's
+> lack of internal checking.
+
+See bug 66233 for warning/stopping the user in Cite.php for this and other issues.",1402341486,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d2r6gtoaqlgf6litoxhf,task_subcomment,NA
+VisualEditor:  Re-used references don't always match,"There's no way for VisualEditor to know which is the ""right"" ref when two refs have the same name but different content.  I've seen this occasionally, and the ""mismatched"" refs sometimes have functionally the same content (e.g., one with a typo or abbreviation not present in the other).
+
+We could pop up an message about the error in the wikitext (which is probably something that should be done by MediaWiki, not VisualEditor).  In VisualEditor, we could rename the refs to force them to be separated.   Or we could do nothing, and maintain bug-for-bug compatibility with Cite.php's lack of internal checking.",1402341362,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-d2r6gtoaqlgf6litoxhf,task_subcomment,NA
+VisualEditor:  Re-used references don't always match,"I'm pretty sure this is a WONTFIX; if the wikitext is in such a broken state that it defines a reference twice, there's nothing sane that VisualEditor can really do.",1402332059,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d2r6gtoaqlgf6litoxhf,task_subcomment,NA
+VisualEditor:Wrapping is not working properly for Reference numbers in reflist as it gets overlapped by a left aligned image,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a image
+3.Add some content in the page
+4.Add some references
+5.Make the image left aligned
+6.Add a reflist in a way so that the references in that list is to the right of the image
+7.Save the page
+
+Observed result:
+
+Reference numbers in reflist are getting overlapped by the image
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13726}",1397770740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xctt6gf3mq7aojdrpzna,task_description,invalid
+VisualEditor:Wrapping is not working properly for Reference numbers in reflist as it gets overlapped by a left aligned image,"Not a VE issue, happens in read mode too.
+
+(That should be fixed though)",1401323215,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xctt6gf3mq7aojdrpzna,task_subcomment,NA
+VisualEditor: crashing when trying to save a reference?,"An IP user at sv.wp reports this (GoogleTranslated):
+In Ubuntu 10.13 crashes Firefox when I want to save a source.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux",1397642280,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lq26x5df5b2uayf5w4sb,task_description,declined
+VisualEditor: crashing when trying to save a reference?,Insufficient information to triage.,1414624719,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lq26x5df5b2uayf5w4sb,task_subcomment,NA
+"'Insert Media' in VE fails to search local repo, returns blank.","**Author:** `tech`
+
+**Description:**
+Running an up-to-date VisualEditor extension and parsoid server on mediawiki-1.22.2, when I use 'Insert Media' no matter the search term (exact filenames are no better) nothing is returned.
+
+Checking server logs and debugging client browser data shows that VE only goes as far as a call to the API 'api.php?format=json&action=query&meta=filerepoinfo' which returns:
+
+{
+  query: {
+    repos: [
+      {
+        name: ""local"",
+        displayname: null,
+        rootUrl: ""/images"",
+        local: true
+      }
+    ]
+  }
+}
+
+There are no further queries to the API after this call.
+
+I can add wikiCommons, with ""$wgUseInstantCommons = true"", which successfully searches the wikiCommons, but has no effect on local media.
+
+I can manually add media with the standard editor and the [[File:image.ext]] syntax, but if I double click a previously attached image in VE all of the fields in the media dialog box are vacant and I can't change any values or even close the dialog.
+
+A query of 'api.php?action=query&list=allimages&format=json' returns a complete set of media as expected.
+
+Further, looking at the API documentation on the server the example listed for filerepoinfo is 'api.php?action=query&meta=filerepoinfo&friprop=apiurl|name|displayname', but it returns in the warnings field: ""Unrecognized value for parameter 'friprop': apiurl"". Suggesting that perhaps a variable in LocalSettings.php is missing or inaccurate, I've looked over this several times, but don't see any glaring issues.
+
+The server in question is behind an intranet, but I'm happy to answer any questions.
+
+Thanks,
+Patrick
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux",1397627580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sizovmscvvm6rifym437,task_description,invalid
+"'Insert Media' in VE fails to search local repo, returns blank.","(In reply to Patrick King from comment #0)
+> Running an up-to-date VisualEditor extension and parsoid server on
+> mediawiki-1.22.2, when I use 'Insert Media' no matter the search term (exact
+> filenames are no better) nothing is returned.
+
+Sorry, I completely missed the bit of your question asking about MediaWiki 1.22 – for media search to work, VisualEditor requires APIs that were introduced in MediaWiki 1.23. Indeed, the code intentionally asserts that you are running the right version of MediaWiki to avoid these issues.
+
+For comparison, my local repo (running 1.24 alpha) comes out with:
+
+{
+    ""query"": {
+        ""repos"": [
+            {
+                ""name"": ""local"",
+                ""displayname"": ""devwiki"",
+                ""rootUrl"": ""/images"",
+                ""local"": true,
+                ""url"": ""/images"",
+                ""thumbUrl"": ""/images/thumb"",
+                ""initialCapital"": true,
+                ""scriptDirUrl"": ""/w"",
+                ""scriptExtension"": "".php"",
+                ""favicon"": ""http://localhost:8080/favicon.ico""
+            }
+        ]
+    }
+}
+
+Some of these extra return parts are required for VisualEditor's media search to work.
+
+
+(In reply to Patrick King from comment #2)
+> Yes, I did have it installed on the server's root (with a wiki. subdomain).
+
+Quite apart from the MediaWiki 1.22 issue, that's bug 62007 (MediaWiki installed on the server's root is an unsupported configuration by its API, apparently).",1406656996,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sizovmscvvm6rifym437,task_subcomment,NA
+"'Insert Media' in VE fails to search local repo, returns blank.","**tech** wrote:
+
+Upgraded mediawiki to 1.22.5.
+
+Installed parsoid and VisualEditor as new. 
+
+Merged basic LocalSettings.php.
+
+Uploaded a new file.
+
+File and description in Special:ListFiles.
+
+Still no change to this bug, nothing listed, no search results - only call to api is to query filerepoinfo, result as above.",1398218583,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sizovmscvvm6rifym437,task_subcomment,NA
+"'Insert Media' in VE fails to search local repo, returns blank.","**tech** wrote:
+
+Yes, I did have it installed on the server's root (with a wiki. subdomain). But I've just tested with the '/w' leading path ($wgScriptPath = ""/w"") and it's made no difference, no images are showing up even with exact filenames. 
+
+filerepoinfo query returns:
+{""query"":{""repos"":[{""name"":""local"",""displayname"":null,""rootUrl"":""/w/images"",""local"":true}]}}",1397709913,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sizovmscvvm6rifym437,task_subcomment,NA
+"'Insert Media' in VE fails to search local repo, returns blank.","Do you have your wiki installed in the server's root (i.e. corp.foo.com/index.php?title=Main_Page rather than corp.foo.com/w/index.php?title=Main_Page)?
+
+This appears to be a quite common configuration, but is explicitly advised against in MediaWiki's documentation because it doesn't work very well with MediaWiki's API and is the cause of similar issues to this for a number of people. :-(",1397670365,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sizovmscvvm6rifym437,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"After two weeks of vote we've just deliberated in favor of the Visual Editor activation for the logged users who want to tick it only: https://fr.wikinews.org/wiki/Wikinews:Prise_de_d%C3%A9cision/Installation_de_l%27%C3%A9diteur_visuel.
+
+Thank you for your work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1397257620,PHID-USER-dtdj4p6jtxbzs7trc3c6,False,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_description,resolved
+Enable VisualEditor on the French Wikinews users preferences,"(In reply to JackPotte from comment #5)
+> I've ticked the feature and got an error ""parsoidserver-http-bad-status:
+> 404"" on each attempt with Firefox 28.0, even after a cache reset.
+
+Sorry about that; there was a deployment issue. It should now be working for you.",1397520953,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"I've ticked the feature and got an error ""parsoidserver-http-bad-status: 404"" on each attempt with Firefox 28.0, even after a cache reset.",1397518648,PHID-USER-dtdj4p6jtxbzs7trc3c6,False,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,This is now done.,1397518536,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"Change 125538 merged by jenkins-bot:
+Enable VisualEditor on French Wikinews
+
+https://gerrit.wikimedia.org/r/125538",1397517103,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"(In reply to Gerrit Notification Bot from comment #1)
+> Change 125538 had a related patch set uploaded by Catrope:
+> Enable VisualEditor on French Wikinews
+> 
+> https://gerrit.wikimedia.org/r/125538
+Scheduled for deployment on Monday April 14 at 23:00 UTC (Tuesday 01:00 CEST).",1397261936,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+Enable VisualEditor on the French Wikinews users preferences,"Change 125538 had a related patch set uploaded by Catrope:
+Enable VisualEditor on French Wikinews
+
+https://gerrit.wikimedia.org/r/125538",1397260784,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7n4a7riwzybvgg2yg5oj,task_subcomment,NA
+VisualEditor: Editing a reference adds a separate extra reference in test2,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a reference 
+3.Open the reference dialog box again
+4.Add a cite web template inside it
+5.Save the reference
+
+Observed Result:
+A separate reference gets added just next to the existing reference
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397240520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-225bp5yp7locuogtr3qd,task_description,resolved
+VisualEditor: Editing a reference adds a separate extra reference in test2,"
+
+*** This bug has been marked as a duplicate of bug 63828 ***",1397244708,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-225bp5yp7locuogtr3qd,task_subcomment,NA
+VisualEditor: Editing a reference adds a separate extra reference in test2,This happens not only for adding template rather doing any change/edit on the existing reference,1397240888,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-225bp5yp7locuogtr3qd,task_subcomment,NA
+VisualEditor: Template parameters should resize on initialisation (when needed),"Intention:
+Add a new infobox using VE (from scratch)
+
+Steps to Reproduce:
+1. Go to https://sv.wikipedia.org/wiki/Anv%C3%A4ndare:Andr%C3%A9_Costa_%28WMSE%29/VEtest2?veaction=edit
+2. Enter edit-mode for the template
+3. Go to the ""medlemskap"" parameter. Click value.
+4. Go to the ""budget"" parameter. Click the value.
+
+Actual Results:  
+3. Nothing happens. You must use the down arrow to reveal hidden text.
+4. Value window re-sizes and introduces a scrollbar revealing previously hidden text.
+
+Expected Results:  
+Both cases: Window should have been re-seized on initialisation or indicated that there is more information than shown.
+First case: Window should have been re-seized or a scrollbar introduced.
+
+Reproducible: Always
+
+The main issue is that you might not ever expect that there is more information in the template value than is initially shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397215500,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-ioynhxkaq6fkwspf5nvl,task_description,duplicate
+VisualEditor: Newarticletext points to API not PAGENAME,"Intention:
+Create a new article using VE
+
+Steps to Reproduce:
+1. Go to https://en.wikipedia.org/wiki/THISISNOTANARTICLE?veaction=edit
+2. Wait for notices to load
+
+
+Actual Results:  
+All references to the pagename are changed to API (e.g. hover over search, or see the Special:Mypage/API link.
+
+Expected Results:  
+these links should point to the pagename (e.g. Special:Mypage/THISISNOTANARTICLE)
+
+Reproducible: Always
+
+This is occurs for any site using a pagename reference in MediaWiki:Newarticletext
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397210520,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-zdasmwk6nzlmwf5wx5ui,task_description,resolved
+VisualEditor: Newarticletext points to API not PAGENAME,"
+
+*** This bug has been marked as a duplicate of bug 63600 ***",1397866699,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zdasmwk6nzlmwf5wx5ui,task_subcomment,NA
+VisualEditor: Link inspector inserts plain text while trying to insert a link selecting a math formula,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a link
+3.Insert a math node right after the link
+4.Select the math formula
+5.Click on the link inspector
+6.When the link suggestions drop down appears close the inspector
+
+Observed Result:
+The link inspector inserts plain text right before the math node
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/9thapril2014?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13666}",1397154780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gkhfh2wlphtsgti7jxch,task_description,resolved
+VisualEditor: Link inspector inserts plain text while trying to insert a link selecting a math formula,"
+
+*** This bug has been marked as a duplicate of bug 56644 ***",1397757927,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gkhfh2wlphtsgti7jxch,task_subcomment,NA
+VisualEditor: Image repositioning is not working correctly when the image is inside a bock slug,"Centered wrt the slug
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image just after a block slug
+3.Now change the image position to Centre/Left and Image type to Frame
+
+Observed Result:
+
+The Image is not centered/ left aligned with respect to the page width rather with the width of the slug
+
+Try the first image on this page: https://test2.wikipedia.org/wiki/9thapril2014?veaction=edit
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13663}",1397153220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vz3x2eqhdts2i7ebivnh,task_description,invalid
+VisualEditor: Image repositioning is not working correctly when the image is inside a bock slug,"We don't slug after lists any more, and it looks like in this case you were inserting into the list, not a paragraph after it.",1423749104,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vz3x2eqhdts2i7ebivnh,task_subcomment,NA
+VisualEditor: Image repositioning is not working correctly when the image is inside a bock slug,Note: The block slug in the example page is after an indented list,1397153738,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vz3x2eqhdts2i7ebivnh,task_subcomment,NA
+"VisualEditor:  In the template dialog, the removal icon (trash can) should be visible on all items","When you open an existing template, it looks like only the first parameter can be removed.  To discover that it is possible to remove a template parameter, you must first click in that parameter's data box. 
+
+Instead, the trash icon should be visible on all items always.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1397143740,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gxyil7alpbre5j7mytzf,task_description,declined
+"VisualEditor:  In the template dialog, the removal icon (trash can) should be visible on all items","No. We considered this as part of the design, but it makes the interface far too heavy, cluttered and confusing for such an edge case task.",1397678465,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gxyil7alpbre5j7mytzf,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead","On any editable page on http://en.m.wikipedia.beta.wmflabs.org/ a logged-in user in alpha mode should invoke VisualEditor when clicking the edit icon. 
+
+Instead the user gets the normal non-VE editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397059440,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_description,resolved
+"VE does not appear when it should, get wikitext editor instead","
+
+*** This bug has been marked as a duplicate of bug 63658 ***",1397622427,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead","Change 124881 merged by jenkins-bot:
+Revert ""Only offer VisualEditor if installed and enabled""
+
+https://gerrit.wikimedia.org/r/124881",1397062618,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead",This was introduced by another patchset.,1397062586,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead","Change 124881 had a related patch set uploaded by Jdlrobson:
+Revert ""Only offer VisualEditor if installed and enabled""
+
+https://gerrit.wikimedia.org/r/124881",1397062553,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"VE does not appear when it should, get wikitext editor instead","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1916",1397059510,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-vgqjfn2lbwd73gkgod6a,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","To replicate:
+Disable VisualEditor and load the editor. Wikitext editor loads but according to toolbar VisualEditor is available.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396979040,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_description,resolved
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","Change 126672 merged by jenkins-bot:
+Make sure VisualEditor is installed before trying to use it
+
+https://gerrit.wikimedia.org/r/126672",1397669271,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","Change 126672 had a related patch set uploaded by Kaldari:
+Make sure VisualEditor is installed before trying to use it
+
+https://gerrit.wikimedia.org/r/126672",1397667002,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","sorry Theo! I missed that. I don't follow comments on merged commits. Can you bring up your questions on bug 63736 and I'll do my best to answer them in next 24hrs!
+
+Ryan see Bug: 63736 this bug was raised after a fix for it was merged that had to be reverted :(",1397622150,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","(In reply to Ryan Kaldari from comment #2)
+
+> I can't replicate this. If I disable the VisualEditor and try to load the
+> editor in Alpha mode, the editor won't even load. It gives me an unknown
+> dependency JS error. Looking at the code in editor.js, it doesn't look like
+> it takes into account the possibility of the VisualEditor being disabled
+> (which should probably be filed as a different bug).
+
+This. x1000.
+
+I brought this up as a comment on a patch in Gerrit[1], along with a possible solution, but there were never any replies.
+
+Right now MobileFrontend editing does not work on non-VE-enabled websites... which includes my dev site :P
+
+Probably worthy of a bug...
+
+[1] https://gerrit.wikimedia.org/r/#/c/124881/",1397621037,PHID-USER-wgpse4towjiaqbzotzgo,False,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","I can't replicate this. If I disable the VisualEditor and try to load the editor in Alpha mode, the editor won't even load. It gives me an unknown dependency JS error. Looking at the code in editor.js, it doesn't look like it takes into account the possibility of the VisualEditor being disabled (which should probably be filed as a different bug).
+
+If you can replicate this, please post more detailed replication steps.",1397620274,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+"When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1913",1396979110,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xrfq4g5uc44xmpqmjyis,task_subcomment,NA
+VisualEditor: Parse link in Newarticletext,"screenshot of VE, mozilla ff
+
+When going to
+https://en.wikipedia.org/wiki/File:Henri_Rousseau_009.jpg?veaction=edit
+VE has 1 notice telling me:
+
+""Du bist einem Link zu einer Seite gefolgt, die nicht vorhanden ist. Um diese Seite anzulegen, trage deinen Text in das untenstehende Bearbeitungsfeld ein (weitere Informationen auf der [/wiki/Help:Contents Hilfeseite]).""
+
+Note the ""[/wiki/Help:Contents Hilfeseite]"" part. I guess it should be a link.
+
+
+""Newarticletext"" seems to be the only message containing this text. And there was only one hit for ""Newarticletext"" in the VE repo:
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/797430e9efd4c773c149718ad086f51f8aa042f6/ApiVisualEditor.php#L339
+
+Indeed, the issue seems to be at the PHP side;
+POST /w/api.php
+action	visualeditor
+format	json
+paction	parse
+page	File:Henri_Rousseau_009.jpg
+
+returns the message as ""<p>Du bist einem Link zu einer [...] der [/wiki/Help:Contents Hilfeseite] [...] deines Browsers. </p>""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14035}",1396961580,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-5g5bsfyli427a7al2nvk,task_description,resolved
+VisualEditor: Parse link in Newarticletext,"
+
+*** This bug has been marked as a duplicate of bug 63600 ***",1402295035,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5g5bsfyli427a7al2nvk,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396913520,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_description,resolved
+Edit button throws errors when VisualEditor not installed,"Change 126672 merged by jenkins-bot:
+Make sure VisualEditor is installed before trying to use it
+
+https://gerrit.wikimedia.org/r/126672",1397669273,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"Change 126672 had a related patch set uploaded by Kaldari:
+Make sure VisualEditor is installed before trying to use it
+
+https://gerrit.wikimedia.org/r/126672",1397667007,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"Probably the easiest thing to do would be to just check mw.config.get( 'wgVisualEditorConfig' ). If VisualEditor isn't installed, that will return null.",1397666546,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,*** Bug 63736 has been marked as a duplicate of this bug. ***,1397622427,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,I had to revert this change... since the code is loaded asynchronously it will always return false.,1397062626,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"Change 124494 merged by jenkins-bot:
+Only offer VisualEditor if installed and enabled
+
+https://gerrit.wikimedia.org/r/124494",1396979145,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+Edit button throws errors when VisualEditor not installed,"Change 124494 had a related patch set uploaded by Jdlrobson:
+Only offer VisualEditor if installed and enabled
+
+https://gerrit.wikimedia.org/r/124494",1396913565,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zegr7o2fy2tmw2zqjzmu,task_subcomment,NA
+"VisualEditor: Cannot open VE in test 2 as it is throwing error: TypeError: undefined is not a function TypeError {stack: (...), message: ""undefined is not a function""}","Screenshot
+
+Steps to reproduce:
+Try to open any page with VE in test 2
+
+Observed Result:
+The following error appears and VE does not load
+TypeError: undefined is not a function TypeError {stack: (...), message: ""undefined is not a function""}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13971}",1396895520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k2eejhz2gxdoin7eo4qz,task_description,declined
+"VisualEditor: Cannot open VE in test 2 as it is throwing error: TypeError: undefined is not a function TypeError {stack: (...), message: ""undefined is not a function""}",Looks like this got fixed at some point.,1414088145,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-k2eejhz2gxdoin7eo4qz,task_subcomment,NA
+VisualEditor:  Images placed inside a <small> text block cannot be edited,"VisualEditor incorrect display of image inside <small> tags
+
+This may depend on Bug 51614 ""Tool to set/unset text as small"".
+
+Start with a page like https://en.wikipedia.org/w/index.php?oldid=603182124#Referenced_text that contains this wikitext:
+
+<small>
+[[File:Example.jpg|thumb|Caption]]
+</small>
+
+When you open the page in VisualEditor, the image ""thumb"" has a box the entire width of the screen, the image is the correct size, but centered, and you can't select (and therefore can't edit) the image.
+
+The caption's text is small, which is probably expected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13959}",1396893540,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zf5c7zmnxbn4etopqpde,task_description,resolved
+VisualEditor:  Images placed inside a <small> text block cannot be edited,"Yeah, we should fix this sooner rather than later. Sorry.
+
+*** This bug has been marked as a duplicate of bug 51614 ***",1396901647,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zf5c7zmnxbn4etopqpde,task_subcomment,NA
+VisualEditor: Edit notices widget confusingly mentions API (in plain text and/or links) when creating a new page,"See
+https://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove5?veaction=edit
+https://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE8?veaction=edit
+and https://en.wikipedia.org/wiki/User:Elitre_(WMF)/Sandbox3?veaction=edit .
+The widget behaves as if you are attempting to create the article ""API"".
+On en.wp it also provides a direct link to create Special:Mypage/API.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396884660,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-kxhi7vtkl2n4fcawl2u5,task_description,resolved
+VisualEditor: Edit notices widget confusingly mentions API (in plain text and/or links) when creating a new page,"
+
+*** This bug has been marked as a duplicate of bug 63600 ***",1396887928,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kxhi7vtkl2n4fcawl2u5,task_subcomment,NA
+"incorrect ""Wikitext markup detected"" message","**Author:** `richlv`
+
+**Description:**
+visual editor from git f8d56e6804a12248b485c2d3b49d4ff0ffa7220c
+
+testcase : https://www.zabbix.org/wiki/Bugsquash_Days
+(if creating a new account, real name is mandatory)
+
+edit the page with visual editor. using the cursor keys, modify on of the event link texts :
+
+""Wikitext markup detected
+You are using VisualEditor - wikitext does not work here. Click ""Edit source"" to edit the page in wikitext mode – unsaved changes will be lost.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396874580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4lsnvnfnca247mubrvhc,task_description,declined
+"incorrect ""Wikitext markup detected"" message","Yeah, the regex can't avoid false positives without making typing very slow; instead, we plan to remove the wikitext warning in a while.",1397592475,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4lsnvnfnca247mubrvhc,task_subcomment,NA
+"incorrect ""Wikitext markup detected"" message","**richlv** wrote:
+
+hmm, this might be caused by #-number sequence in the bullet points... if so, not sure whether that can be easily solved",1396879069,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4lsnvnfnca247mubrvhc,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Object #<Object> has no method 'lookup' appears upon loading any page on test2,"Screenshot
+
+For all pages on test2 I am getting the following error upon loading and Ve does not open for that page
+
+Uncaught TypeError: Object #<Object> has no method 'lookup' 
+
+Try this page:
+https://test2.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13741}",1396653660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nzp73hbths7mtxjcxvm4,task_description,declined
+VisualEditor: Uncaught TypeError: Object #<Object> has no method 'lookup' appears upon loading any page on test2,This now WFM; possibly a gadget issue?,1401475943,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nzp73hbths7mtxjcxvm4,task_subcomment,NA
+VisualEditor: [Regression wmf21] Media selector hangs without offering save,"As a logged in user on http://en.wikipedia.beta.wmflabs.org/ edit any page. 
+
+Choose ""Insert Media""
+
+Search for something e.g. ""San Francisco""
+
+Select a media image. 
+
+Insert Media interface does nothing, but should offer a Save and then Review your changes options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396537500,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-y5chdora657t2p3e7tbs,task_description,resolved
+VisualEditor: [Regression wmf21] Media selector hangs without offering save,Verified the fix on production,1397775352,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-y5chdora657t2p3e7tbs,task_subcomment,NA
+VisualEditor: [Regression wmf21] Media selector hangs without offering save,verified the fix on mw.org,1396999374,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-y5chdora657t2p3e7tbs,task_subcomment,NA
+VisualEditor: [Regression wmf21] Media selector hangs without offering save,"This issue got fixed by :https://gerrit.wikimedia.org/r/123803
+Verified in betalabs.",1396571513,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-y5chdora657t2p3e7tbs,task_subcomment,NA
+VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs,"seen on beta labs http://en.wikipedia.beta.wmflabs.org/
+
+After clicking Edit for VisualEditor, sometimes the user waits longer than expected for the editable div to appear.  
+
+There is a default timeout of 5 seconds in the automated browser tests, and these tests are failing more and more often because the edit surface in VE takes longer than 5 seconds to appear, for a page of reasonable size.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396474500,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5ulqzr566hicsrhuontf,task_description,resolved
+VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs,"(In reply to Chris McMahon from comment #2)
+> Well, the *tests* are fixed, but it is a bit sketchy that the editable div
+> is taking so long to manifest.
+
+Beta Labs being slow isn't really a bug so much as a statement of fact…",1396478785,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5ulqzr566hicsrhuontf,task_subcomment,NA
+VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs,"Well, the *tests* are fixed, but it is a bit sketchy that the editable div is taking so long to manifest.",1396478562,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5ulqzr566hicsrhuontf,task_subcomment,NA
+VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs,Fixed in gerrit 123450.,1396478369,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5ulqzr566hicsrhuontf,task_subcomment,NA
+VisualEditor:  Firefox displays icons in odd places in dialog boxes,"Firefox display bug
+
+This is related to Bug 63432, about the mis-display of an icon in the media settings dialog box, and Bug 63127, about the reference box.
+
+It also displays incorrectly in template boxes (see attachment), references (the icon at ""Options"" for ""Use this group""—see bug 63127), and pretty much everything in the ""Page options"" (three bars icon) menu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63127
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63432
+
+**Attached**: {F13423}",1396460880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gf4us2lajwz7mnxt2hru,task_description,resolved
+VisualEditor:  Firefox displays icons in odd places in dialog boxes,"
+
+*** This bug has been marked as a duplicate of bug 63127 ***",1397687806,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gf4us2lajwz7mnxt2hru,task_subcomment,NA
+VisualEditor:  Media dialog box has misplaced icon in Firefox,"Firefox-only display bug
+
+If you open the image dialog box and go to ""Advanced settings"" in Firefox, the ""window"" icon next to the headline ""Positions"" is misplaced, so that it covers up the checkbox for ""Wrap content with this item"".
+
+This cannot be reproduced in Safari or Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63127
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63433
+
+**Attached**: {F13420}",1396460400,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zwurzmbrgsoaldr6hnqg,task_description,resolved
+VisualEditor:  Media dialog box has misplaced icon in Firefox,"
+
+*** This bug has been marked as a duplicate of bug 63127 ***",1397687801,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zwurzmbrgsoaldr6hnqg,task_subcomment,NA
+Parsoid giving 503s for VE in mobilefrontend on beta labs,"To replicate:
+1) Browse to http://en.m.wikipedia.beta.wmflabs.org/ in a browser window with at least one dimension > 700px
+2) Opt-in to MobileFrontend's experimental feature (main menu -> settings -> beta -> 'on' -> save; main menu -> settings -> experimental -> 'on' -> save)
+3) Browse to random article
+4) Tap/click pencil icon to edit
+
+Current behavior:
+ Receive error ""Error, can't load section""
+Expected behavrio:
+ VisualEditor interface loaded to edit article
+
+
+When looking through the network requests, you should see an API request for the VE action (something like http://en.m.wikipedia.beta.wmflabs.org/w/api.php?format=json&action=visualeditor&paction=parse&page=0.019064959779951818) with a server response of:
+'{""servedby"":""deployment-apache02"",""error"":{""code"":""parsoidserver-http-bad-status"",""info"":""503""}}'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396397280,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-ki5b25is43aulcidvmv4,task_description,resolved
+Parsoid giving 503s for VE in mobilefrontend on beta labs,"This appears to be resolved now. Dunno what changed, but it is at least working again ;)",1396461709,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-ki5b25is43aulcidvmv4,task_subcomment,NA
+VisualEditor: The hand icon remains active after opening the Media Settings dialog and Reference dialog which selects some part inside the dialog upon double clicking,"video capture of the bug
+
+Steps to reproduce:
+
+1.Open a page with VE
+
+2.Insert an image or a reference somewhere at the centre of the page for better viewing the effect of it.
+
+3.Now click on the Reference Icon or the Media Settings icon
+
+Observed Result:
+
+You will see the hand icon inside the dialog box and upon double clicking it selects some part of the dialog box.
+
+See the Video Capture attached.
+
+
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13360}",1396394400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-phnj44ch6mszxq6qpohn,task_description,resolved
+VisualEditor: The hand icon remains active after opening the Media Settings dialog and Reference dialog which selects some part inside the dialog upon double clicking,"Re-checked - non-reproducible anymore, most likely due to re-design of citation dialog/edit boxes.",1425680477,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-phnj44ch6mszxq6qpohn,task_subcomment,NA
+Parsoid crashes on request (TypeError: undefined is not a function),"**Author:** `koem`
+
+**Description:**
+Setup:
+ - Ubuntu 12.04
+ - apache2
+ - mediawiki 1.22.4
+ - parsoid master 2014-04-01 12:58 UTC
+ - nodejs 0.10.26-1chl1~precise1
+ - VisualEditor snapshot REL1_22
+
+This is the error I get when I do curl http://localhost:8000/localhost/Wiki_Test_Page or when I try to edit the page http://wiki.testwiki.com/wiki/Wiki_Test_Page as a logged in user (Popup says ""Error loading data from server: parsoidserver-http-request-error: MWHttpRequest error. Would you like to retry?"").
+
+
+  /usr/local/parsoid/api/ParsoidService.js:355
+                                        callback();
+                                        ^
+  TypeError: undefined is not a function
+    at errCB (/usr/local/parsoid/api/ParsoidService.js:355:6)
+    at /usr/local/parsoid/api/ParsoidService.js:361:12
+    at /usr/local/parsoid/lib/mediawiki.parser.environment.js:241:3
+    at setupWikiConfig (/usr/local/parsoid/lib/mediawiki.parser.environment.js:295:3)
+    at Object.processSome [as _onImmediate] (/usr/local/parsoid/lib/mediawiki.ApiRequest.js:119:17)
+    at processImmediate [as _immediateCallback] (timers.js:330:15)
+  worker 2394 died (8), restarting.
+   - worker(2425) loading...
+   - worker(2425) ready
+
+The worker crashes and is restarted immediately. Always.
+
+The Wiki is private. It worked until I imported some templates and deleted them again. But I can't imagine that this is the reason.
+
+
+LocalPreferences.php:
+
+  require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");
+  $wgVisualEditorParsoidURL = 'http://localhost:8000';
+  $wgDefaultUserOptions['visualeditor-enable'] = 1;
+  $wgHiddenPrefs[] = 'visualeditor-enable';
+  $wgVisualEditorParsoidForwardCookies = true;
+
+
+api/localpreferences.js:
+
+  exports.setup = function( parsoidConfig ) {
+        parsoidConfig.setInterwiki( 'localhost', 'http://wiki.testwiki.com/mediawiki/api.php' );
+        parsoidConfig.useSelser = true;
+  };
+
+Best,
+Karsten
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**OS**: Linux
+**Platform**: PC",1396354080,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3x6kkofcned4qcjjk6dl,task_description,declined
+Parsoid crashes on request (TypeError: undefined is not a function),"The recommended way to deal with private wikis is documented at
+
+https://www.mediawiki.org/wiki/Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis",1400704166,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-3x6kkofcned4qcjjk6dl,task_subcomment,NA
+Parsoid crashes on request (TypeError: undefined is not a function),"**koem** wrote:
+
+ok, solved it by:
+
+          if ( $_SERVER['REMOTE_ADDR'] == '127.0.0.1' ) {
+           $wgGroupPermissions['*']['read'] = true;
+           $wgGroupPermissions['*']['edit'] = true;
+          } else {
+           $wgGroupPermissions['*']['edit'] = false;
+           $wgGroupPermissions['*']['read'] = false;
+          }
+
+and in localsettings.js
+
+          parsoidConfig.setInterwiki( 'localhost', 'http://localhost/mediawiki/api.php' );
+
+please add this to the documentation",1396517054,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3x6kkofcned4qcjjk6dl,task_subcomment,NA
+Parsoid crashes on request (TypeError: undefined is not a function),"**koem** wrote:
+
+When I comment out these lines in LocalSettings.php - then it works. But then my wiki isn't private anymore ...
+
+$wgGroupPermissions['*']['createaccount'] = false;
+$wgGroupPermissions['*']['edit'] = false;
+$wgGroupPermissions['*']['read'] = false;",1396465941,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3x6kkofcned4qcjjk6dl,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**Author:** `andr55`
+
+**Description:**
+I would like the extension:variables installed.
+
+It is available at https://www.mediawiki.org/wiki/Extension:Variables
+
+It is rated as stable.
+It allows creating local variables valid only in the current page.
+
+The current use case is to define a long string to be used in over 100 templates as part of links inside a larger template page.
+This extension will help alleviate constant ongoing problems in a frequently accessed and edited page.  (Over 400 edits in the last month.)
+
+1) By using a local variable, it removes the problem of typos, very common in the page where it will be used.  As well, it will minimize the problem of broken links, as many editors avoid typing the long string necessary to create valid links.
+
+2) It keeps this string local to the only page where it will be used, thus not polluting the template namespace, and avoiding potential name conflicts with other templates.
+
+3) The variable can be defined at the beginning, with a brief description to ensure that it's use is understood, so it becomes self-documenting where it is used.
+
+4) A shorter and more useful name can be chosen than for a template, as a template name would have to avoid ambiguity with other template pages.
+
+5) In the likely case that this string needs to be changed in the future, it can be done more easily, as it will be on the page where it is used.
+
+6) Although this is for use as part of a link, it could equally be used for other cases, as presented in examples on the extension page.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1396294740,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_description,duplicate
+Please add extension:variables to allow defining variables local to the current page,It was marked as a verified duplicate of T9865 while in Bugzilla: http://bugs.wmflabs.org/show_bug.cgi?id=63324,1450841495,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"The extension was never installed, so I'm not sure why this is marked Resolved.",1450839840,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Brad Jorsch from comment #9)
+> (In reply to andré from comment #8)
+> > So you are saying that problems with the implementation of these new
+> > features interfere with this extension ?
+> 
+> It's not a problem with those features, it's a design requirement.
+> 
+> We had to deal with that requirement when creating Scribunto, too.
+
+Evidently.  And it works very well, at least on pages I've seen using it.  Such modules can be a tremendous improvement over pure templates.
+
+> > I'm assuming that all this extension does is scan the page, taking the
+> > variable definitions and replacing all instances using the defined
+> > variables, before any other parsing of the page.  The result is a page that
+> > shows no evidence of the extension.
+> 
+> I haven't checked, but I'd imagine the model is more that when the parsing
+> process calls the hook for #vardefine it sets some internal state, and when
+> it calls the hook for #var then it returns that internal state. Much like
+> how with Cite a <ref> sets some internal state and <references> uses that to
+> construct a list of references.
+
+It would be setting a value for a token, and replacing tokens with that value.  Simple text replacement, as it passes through the page.  There are some more complicated options, but they could be ignored by WP if difficult to implement.  For instance, there could be a bar to using recursion.
+
+> > Maybe there needs to be a processing priority established ?
+> 
+> Let's not add even more passes to the parser. The Parsoid folks already want
+> to do that for Cite (and do do it in Parsoid).
+
+But additional passes can be a very effective way of simplifying the problem.  Often with little or no cost in performance.
+
+> > Maybe you can explain how any problems with the new VisualEditor and Parsoid
+> > are not orthogonal to this extension ?
+> 
+> Because wikitext needs to be parsed?
+
+Logically, the simplest solution for extension:Variables is to have a priority parsing pass to itself.  Once that is done, the resulting page shows no evidence of the extension.
+If there is a relatively straight-forward way to signal the use of the extension in the page (such as a definition near the beginning of the page), the performance hit for other pages should be minimal if any.
+Maybe the parser could do an initial scan of the page to enumerate all the extensions/modules used in the page (if it doesn't already), and then do parsing passes according to an appropriate priority.  Many but not all could be done in parallel.  Extension:Variables being an obvious exception.
+It's not rocket science.  (To experienced programmers, at least.)
+
+If there is a problem with how extension:Variables is implemented, I'd be interested in writing a similar very simple equivalent, that does nothing more than act as a preprocessor, replacing one or more variables with literal text in a single pass.  In my mind that is all that most uses of such an extension would be anyway.  And it does fill a void, between templates and modules created with Scribuntu/Lua",1396375482,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"(In reply to andré from comment #8)
+> So you are saying that problems with the implementation of these new
+> features interfere with this extension ?
+
+It's not a problem with those features, it's a design requirement.
+
+We had to deal with that requirement when creating Scribunto, too.
+
+> I'm assuming that all this extension does is scan the page, taking the
+> variable definitions and replacing all instances using the defined
+> variables, before any other parsing of the page.  The result is a page that
+> shows no evidence of the extension.
+
+I haven't checked, but I'd imagine the model is more that when the parsing process calls the hook for #vardefine it sets some internal state, and when it calls the hook for #var then it returns that internal state. Much like how with Cite a <ref> sets some internal state and <references> uses that to construct a list of references.
+
+> Maybe there needs to be a processing priority established ?
+
+Let's not add even more passes to the parser. The Parsoid folks already want to do that for Cite (and do do it in Parsoid).
+
+> Maybe you can explain how any problems with the new VisualEditor and Parsoid
+> are not orthogonal to this extension ?
+
+Because wikitext needs to be parsed?
+
+> I'm not trying to distract you from solving VisualEditor problems,
+
+Not my department anyway.",1396369923,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Brad Jorsch from comment #6)
+> (In reply to andré from comment #4)
+%%%> > > *** This bug has been marked as a duplicate of bug 7865 ***%%%
+> > 
+> > Not appropriate, for a very old bug rejected for circumstances which likely
+> > have changed.
+> 
+> Circumstances have in fact changed.
+> 
+> However, they've changed such that closing this as anything other than
+> WONTFIX is even more unlikely: VisualEditor and Parsoid require the ability
+> to reparse fragments of the page and then merge the new HTML into the
+> previously-rendered HTML, meaning that new wikitext that affects other parts
+> of the page will not be added (and it's even difficult to fix bugs in Cite
+> due to this issue).
+
+So you are saying that problems with the implementation of these new features interfere with this extension ?
+I don't understand.
+ 
+I'm assuming that all this extension does is scan the page, taking the variable definitions and replacing all instances using the defined variables, before any other parsing of the page.  The result is a page that shows no evidence of the extension.
+Is there something that prevents it from processing before any other parsing ?
+Maybe there needs to be a processing priority established ?
+
+Maybe you can explain how any problems with the new VisualEditor and Parsoid are not orthogonal to this extension ?
+I haven't used VisualEditor yet as I am very comfortable with the older editor, so I'm not aware of any problems there.
+
+BTW, to facilitate the use of this extension, WP could always make some supplementary requirement such as the use of the extension be signaled by a definition at/near the beginning of the page.  Or maybe restrict it to user: space initially, for testing purposes.
+
+I'm not trying to distract you from solving VisualEditor problems, but we have a pre-existing editor which works very well, and extension:Variables is an important enhancement.",1396369181,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Andre Klapper from comment #5)
+> (In reply to andré from comment #3)
+> I don't know what this refers to, but so far it looked like the bug report
+> was about deploying an extension instead.
+
+Exactly.  I was responding to your comment #1 
+
+> > Not appropriate, for a very old bug rejected for circumstances which
+> > likely have changed.
+> 
+> Please provide proof for the ""likely"".
+
+Evidently there have been considerable changes to WP since 2006.
+As well, looking at the changelog of extension:Variables, there was a major re-write for version 2.0.0.  (It is now at 2.0.1)",1396367370,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"(In reply to andré from comment #4)
+> > *** This bug has been marked as a duplicate of bug 7865 ***
+> 
+> Not appropriate, for a very old bug rejected for circumstances which likely
+> have changed.
+
+Circumstances have in fact changed.
+
+However, they've changed such that closing this as anything other than WONTFIX is even more unlikely: VisualEditor and Parsoid require the ability to reparse fragments of the page and then merge the new HTML into the previously-rendered HTML, meaning that new wikitext that affects other parts of the page will not be added (and it's even difficult to fix bugs in Cite due to this issue).",1396357479,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"(In reply to andré from comment #3)
+I don't know what this refers to, but so far it looked like the bug report was about deploying an extension instead.
+
+> Not appropriate, for a very old bug rejected for circumstances which
+> likely have changed.
+
+Please provide proof for the ""likely"".",1396351862,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Bawolff (Brian Wolff) from comment #2)
+> This was rejected way back in the day (bug 7865). I assume the rejection
+> still stands.
+
+It is a very bad assumption that a 7 year old rejection is still valid.
+In case you hadn't noticed, both Mediawiki and extension:variables have changed since then.
+ 
+> -----
+> 
+> 2) It keeps this string local to the only page where it will be used, thus
+> not polluting the template namespace, and avoiding potential name conflicts
+> with other templates.
+> 
+> Fun fact, there are
+> 74106937111882365071085430405560261026092790186009960985252853765064
+> 40296955904 possible template names, (This is an under-estimate, I didn't
+> count most non-english letters). You could easily use
+> Template:PageNameHere/Specific_string_name, or even just make it a subpage
+> of the actual page not in the template namespace, etc. Now namespacing
+> things might be nice just generally, but we're not running out of template
+> names.
+
+Assuming a 2-letter name, that gives only 676 possibilities.
+But that is not the point.
+It is not unreasonable to assume that many short names will conflict.  Disambiguation pages don't exist for nothing.
+One advantage of variables local to a particular page is that such variables can be short, thus easier to type, without any ambiguity.  As noted above.
+
+> 
+> >It is rated as stable.
+> 
+> Just for the record, those ratings are done by the extension author. There
+> are lots of extensions marked unstable which are actually more stable than
+> the stable extensions. So the rating is pretty much meaningless. (Which
+> isn't necessarily to say anything bad about this particular extension, I
+> have no idea how stable it may or may not be)
+> 
+OK.  But note that this extension existed in 2006, and was last modified in 2011.  So it has been around for a while.  And the last 2 (recent) versions are installed on 170 sites.
+
+%%%> *** This bug has been marked as a duplicate of bug 7865 ***%%%
+
+Not appropriate, for a very old bug rejected for circumstances which likely have changed.",1396311259,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"**andr55** wrote:
+
+(In reply to Andre Klapper from comment #1)
+> Hi André, thanks for taking the time to report this!
+> 
+> (In reply to andré from comment #0)
+> > I would like the extension:variables installed.
+> 
+> On which site? For any configuration change, a local consensus is required.
+> Could you discuss the matter on the Village pump page of your wiki to
+> confirm that this change is wanted by the community, and paste the link to
+> the discussion here?
+> 
+> Also, please see https://www.mediawiki.org/wiki/Review_queue for a checklist
+> of steps how to proceed before marking this as blocking bug 31235.
+
+Thanks for the feedback.
+The page in question is a template on the English WP.
+I've already had contact with someone on the Village pump page, who wasn't aware of this extension.
+I'll get back when I have the confirmation.",1396309935,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"This was rejected way back in the day (bug 7865). I assume the rejection still stands.
+
+-----
+
+2) It keeps this string local to the only page where it will be used, thus not polluting the template namespace, and avoiding potential name conflicts with other templates.
+
+Fun fact, there are 74106937111882365071085430405560261026092790186009960985252853765064
+40296955904 possible template names, (This is an under-estimate, I didn't count most non-english letters). You could easily use Template:PageNameHere/Specific_string_name, or even just make it a subpage of the actual page not in the template namespace, etc. Now namespacing things might be nice just generally, but we're not running out of template names.
+
+>It is rated as stable.
+
+Just for the record, those ratings are done by the extension author. There are lots of extensions marked unstable which are actually more stable than the stable extensions. So the rating is pretty much meaningless. (Which isn't necessarily to say anything bad about this particular extension, I have no idea how stable it may or may not be)
+
+*** This bug has been marked as a duplicate of bug 7865 ***",1396304859,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+Please add extension:variables to allow defining variables local to the current page,"Hi André, thanks for taking the time to report this!
+
+(In reply to andré from comment #0)
+> I would like the extension:variables installed.
+
+On which site? For any configuration change, a local consensus is required. Could you discuss the matter on the Village pump page of your wiki to confirm that this change is wanted by the community, and paste the link to the discussion here?
+
+Also, please see https://www.mediawiki.org/wiki/Review_queue for a checklist of steps how to proceed before marking this as blocking bug 31235.",1396304671,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ixgrpcodnk3skm7y2hlt,task_subcomment,NA
+VisualEditor:  Ever-growing list of edit summary menus if using the gadget,"Steps to Reproduce:
+1.  Enable the edit-summary gadget at the English Wikipedia as described in Bug 63314.
+
+2.  Make a small change to any page.  Click ""Save"".  Notice the two drop-down menus underneath the edit summary textarea.
+
+3.  Oops, you need to make another change before you save.  Close the save dialog (e.g., press the Escape key).
+
+4.  No, that change is not important (or make another change; it doesn't matter).  Go back to 'Save'.
+
+5.  Count the number of dropdown menus present.
+
+
+
+Reproducible: Always
+
+Repeating this process several times resulted in at least four pairs of dropdown menus in Firefox before I gave up.  
+
+In Safari, I got two pairs, and then (consistently) on the third time, VisualEditor seemed to crash (whole page grays out [or ""whites out"", really], nothing happens until I hit Escape).  But after pressing Escape, everything's fine, and the process can be repeated several more times, resulting in half a dozen pairs of drop downs.  (The white/apparent crash comes back after a few more rounds, but just press Escape again and keep going.)  
+
+Saving the page was ultimately successful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396290300,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-nx2jsmtulfpacm6ytqq2,task_description,invalid
+VisualEditor:  Ever-growing list of edit summary menus if using the gadget,"Bugs with gadgets aren't tracked in Bugzilla (per community request about forking the discussion from on-wiki venues), so marking this as INVALID, sorry.",1396290695,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nx2jsmtulfpacm6ytqq2,task_subcomment,NA
+"VisualEditor:  Edit summary gadget looks like it's working, but edits are saved without edit summaries","Intention:
+Add a pre-set edit summary to an edit using a gadget.
+
+Steps to Reproduce:
+1.  Turn on the gadget at en.wp:   Preferences > Gadgets > Editing > ""Add two new dropdown boxes below the edit summary box with some useful default summaries""
+
+2. Edit any article with VisualEditor.
+
+3.  Save page.  Don't click or type anything into the edit summary box.  Just click on an item something from one of the dropdown menus added by the gadget, and then click on 'Save'.
+
+4.  Look for the edit summary in the page history.
+
+Actual Results:  
+The edit summary displays in the textarea of the save dialog, but it is not saved with the edit.
+
+If you click in the textarea after (but not before) choosing an edit summary from the dropdown menu, then the edit is saved correctly.
+
+
+Reproducible: Always
+
+Confirmed in Chrome, Safari, and Firefox on Mac and Ubuntu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396289760,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-pau2osi4bgxm7omr62y5,task_description,invalid
+"VisualEditor:  Edit summary gadget looks like it's working, but edits are saved without edit summaries","Bugs with gadgets aren't tracked in Bugzilla (per community request about forking the discussion from on-wiki venues), so marking this as INVALID, sorry.",1396290681,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pau2osi4bgxm7omr62y5,task_subcomment,NA
+"When a template is in a section title, VE consider what is on the same line after as if it was into the template","Impossible to delete this addition: https//fr.wiktionary.org/w/index.php?title=pr%C3%A9dominer&diff=prev&oldid=18065635
+
+because VE consider it as a template part: https://commons.wikimedia.org/wiki/File:VisualEditor_bug_on_fr.wikt.PNG
+
+Tested on two PCs, including one with Firefox 28.0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://fr.wiktionary.org/w/index.php?title=pr%C3%A9dominer&diff=prev&oldid=18065635",1396225140,PHID-USER-dtdj4p6jtxbzs7trc3c6,False,PHID-TASK-d7f46ss2k5gqniu6endn,task_description,resolved
+"When a template is in a section title, VE consider what is on the same line after as if it was into the template","The problem here is that the template ""{{S|étymologie}}"" creates a broken block object, so everything after it has to be part of the same block. (This, BTW, is horrible wikitext.)
+
+When Parsoid encounters this, it has no choice but to assume that the (mistaken) rest of the block was intended to be there, so groups it in with the template. Had the user put a newline in correctly it would have worked fine, but this isn't great. :-(
+
+What do you suggest we should do in this case?",1396292877,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d7f46ss2k5gqniu6endn,task_subcomment,NA
+Template's CSS code shows on page when editing,"picture of the bug
+
+Template's html code shows on page when editing. I don't know should we change something with our templates on fi-wiki, or is it possible to fix in VisualEditor.
+
+How to reproduce:
+1) go to https://fi.wikipedia.org/wiki/Australian_Grand_Prix_2014?veaction=edit
+2) see the 2 templates on the bottom of the page
+
+If you need more information, feel free to ask.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13012}",1396097400,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-cqmy2yutnupgu7hrfwej,task_description,invalid
+Template's CSS code shows on page when editing,Closed. Thanks for your investigating.,1396191796,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-cqmy2yutnupgu7hrfwej,task_subcomment,NA
+Template's CSS code shows on page when editing,"Hi, i think that the idea of the ""lisätyylit"" is to add css inline rules to div and stuff after that is to end css-rules and add some table attributes. However it has never worked because there is div element and not table. It also broke resulting html-code even it seemed to work.
+
+Reason why visual editor broke is the mismatching doublequotes in expanded template result (in lisätyyli param: '... both"" cellpadding=""2"" cellspacing=""5""':
+
+-- Clip --
+<div class=""NavFrame "" style="" margin: auto; background-color: #ffffff; border: 1px #aaaaaa solid; margin: 0.5em auto auto auto; width: 600px; text-align: center; font-size: 95%; clear: both;; background-color: #FFFFFF; color: #000000; width: auto;""><div class=""NavHead"" style=""display:block;text-align:center;background-color: #F3D161;"">
+-- Clip --
+
+I fixed some templates with this change and my guess that all of F1-templates can be fixed with same way: 
+- https://fi.wikipedia.org/w/index.php?title=Malline%3ABrasilian_Grand_Prix&diff=13955778&oldid=13575504
+
+However there seems to be little delay before change can be seen in visual editor after template is fixed and i could not find any way to purge visual editors cache. 
+
+If it ok for stryn i think that this bug can be closed.",1396191578,PHID-USER-pmmyhpxkzmo6lbo5bcqo,False,PHID-TASK-cqmy2yutnupgu7hrfwej,task_subcomment,NA
+Template's CSS code shows on page when editing,"Well, https://fi.wikipedia.org/w/index.php?title=Malline:Australian_Grand_Prix&action=edit
+
+
+| lisätyylit = ...styleinfo..."" cellpadding=""2"" cellspacing=""5""
+
+What is that, and what gave anyone the idea that that would ever work ? :D",1396099045,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-cqmy2yutnupgu7hrfwej,task_subcomment,NA
+Clicking edit in VE tablet doesn't respond instantly,"When you click the edit button the address bar changes but the editor doesn't overlay. Many a time I find myself clicking it several times.
+
+The problem stems from VisualEditor code being loaded via mw.loader.using but no LoadingOverlay being shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395967680,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-hlddr6phtisadyt4ixuj,task_description,resolved
+Clicking edit in VE tablet doesn't respond instantly,"Change 124025 merged by jenkins-bot:
+Show LoadingOverlay when loading VE
+
+https://gerrit.wikimedia.org/r/124025",1396652665,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlddr6phtisadyt4ixuj,task_subcomment,NA
+Clicking edit in VE tablet doesn't respond instantly,"Change 124025 had a related patch set uploaded by JGonera:
+Show LoadingOverlay when loading VE
+
+https://gerrit.wikimedia.org/r/124025",1396650846,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlddr6phtisadyt4ixuj,task_subcomment,NA
+Clicking edit in VE tablet doesn't respond instantly,The loader should show and the overlay should be semi transparent.,1396477288,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-hlddr6phtisadyt4ixuj,task_subcomment,NA
+Clicking edit in VE tablet doesn't respond instantly,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1817",1395967809,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hlddr6phtisadyt4ixuj,task_subcomment,NA
+"VisualEditor: When using browser zoom, image overlays (resize, edit) become too small and inaccesible","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1395894960,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-csoldbfxlq5rsqqvnrq6,task_description,declined
+"VisualEditor: When using browser zoom, image overlays (resize, edit) become too small and inaccesible","Not convinced that this is something we should fix – the whole point of browser zoom is that VE shouldn't care what the zoom level is, and should be consistent. If you zoom out to the level that things are too small, then you won't be easily able to click them. If you zoom in, they will get bigger.
+
+Unless I'm missing something?",1400695607,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-csoldbfxlq5rsqqvnrq6,task_subcomment,NA
+"Scrolling a long template parameter, then clicking causes the cursor to jump to the top of the long parameter field","Navigate here: https://www.mediawiki.org/wiki/VisualEditor:Test12
+
+Open the VisualEditor
+
+Open the template editor for the page's content — should be Template:Longformcontent
+
+Scroll to the fourth parameter text entry field.
+
+Scroll within the fourth parameter's text entry field to ""Maecenas non condimentum risus.""
+
+Click ""Maecenas non condimentum risus.""
+
+Defect: the cursor is placed at the top of the text entry field, by ""Lorem ipsum dolor""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9",1395862260,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-2rc2hldv5lyl6kgrhcon,task_description,declined
+"Scrolling a long template parameter, then clicking causes the cursor to jump to the top of the long parameter field","I think this is now fixed on production, and this ticket should be closed.",1403637258,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-2rc2hldv5lyl6kgrhcon,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Screenshot
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13208}",1395772260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v5ulk7ng472f6cnu46nx,task_description,resolved
+VisualEditor: Math inspector label is showing up as null in Betalabs,Verified the fix in test2,1395790633,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Change 120854 merged by jenkins-bot:
+Make VE math inspector title not be null
+
+https://gerrit.wikimedia.org/r/120854",1395789798,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,Verified the fix on betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Reference_numbering&veaction=edit,1395775955,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Change 120846 merged by jenkins-bot:
+Make VE math inspector title not be null
+
+https://gerrit.wikimedia.org/r/120846",1395774688,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Change 120854 had a related patch set uploaded by Jforrester:
+Make VE math inspector title not be null
+
+https://gerrit.wikimedia.org/r/120854",1395774638,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+VisualEditor: Math inspector label is showing up as null in Betalabs,"Change 120846 had a related patch set uploaded by Catrope:
+Make VE math inspector title not be null
+
+https://gerrit.wikimedia.org/r/120846",1395772554,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v5ulk7ng472f6cnu46nx,task_subcomment,NA
+use new param in VE tests to get around beta warning,"see https://gerrit.wikimedia.org/r/#/c/119217/
+
+update VisualEditor appropriately
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395703860,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-vcoxn3g74svzqfbhj3kr,task_description,resolved
+VisualEditor: save button remains greyed out in IE9 even after modifying the document,"There is something that should be triggered to change the appearance of the save button in IE that isn't being triggered.  I need to find it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395702780,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-r3yfhoreb7uextmhj5cl,task_description,resolved
+VisualEditor: save button remains greyed out in IE9 even after modifying the document,"Think this is a dupe of Bug #63039
+
+*** This bug has been marked as a duplicate of bug 63039 ***",1395784399,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-r3yfhoreb7uextmhj5cl,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image/reference
+3.Inside the reference or media dialog box insert a link/special character inserter
+4.Now hover over any button on the link inspector like close or delete button
+
+Observed Result:
+The dialog box is getting misplaced like flickering
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395687420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_description,resolved
+VisualEditor: Various things wiggle on hover in Chrome,"For completion, usage of `.oo-ui-force-gpu-composite-layer()` in v0.24.3 resolved this misbehaviour in Chrome.",1513150356,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,Reference task: {T64591},1512598507,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"
+
+*** This bug has been marked as a duplicate of bug 62591 ***",1395876216,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"Update: this is only when *animating* opacity, not when changing opacity.",1395875546,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,Updated summary: there are also smaller wiggling bugs when you hover over close buttons of popups and various other places.,1395875140,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"This turns out to be because Chrome turns some sort of hardware acceleration or whatever on or off when the opacity is not 1. When you hover over certain icons, we change the opacity from 0.8 to 1, which triggers acceleration stuff, and so everything wiggles.
+
+I'll try to come up with a minimal test case and file this bug against Chrome, but for now I'll just change all opacity: 1; rules to opacity: 0.99;",1395874826,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+VisualEditor: Various things wiggle on hover in Chrome,"This may be a particularly bad incarnation of the wiggling issue (mouse over the closing X of the edit notices popup and you'll see the text wiggle), exacerbated by the fact that this is in an iframe.
+
+I think Trevor addressed wiggliness in the template dialog using -webkit-backface-visibility: hidden;, we should try that here.",1395858796,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ezhyct2qlpeljnoxkbyi,task_subcomment,NA
+"VisualEditor: When tabbing inside the template inspector, don't skip the ""Add Parameter"" option","When reaching the bottom of a list of parameters for a given template, cursor in the box of the last parameter, if you hit Tab you'll be taken directly to the ""Apply changes"" button, while some users would expect ""Add Parameter"" to be reachable then.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395675720,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-goupncgsrq626ilxi7gq,task_description,resolved
+"VisualEditor: When tabbing inside the template inspector, don't skip the ""Add Parameter"" option","I believe this was fixed with bug 65474 being completed. Sorry for getting this out of order.
+
+*** This bug has been marked as a duplicate of bug 65474 ***",1402553868,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-goupncgsrq626ilxi7gq,task_subcomment,NA
+VisualEditor: Link inspector icon remains enabled in the toolbar even after closing the link inspector,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Now open a link inspector
+3.Do not insert any link, just close the link inspector by pressing ""<"" or the trash icon
+
+Observed Result:
+
+The link inspector icon is still active on the toolbar
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12885}",1395440220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sffadm7jcu5zx5bxq7pj,task_description,invalid
+VisualEditor: Link inspector icon remains enabled in the toolbar even after closing the link inspector,"This isn't a bug; the ""active"" state is intentional.",1398726819,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sffadm7jcu5zx5bxq7pj,task_subcomment,NA
+"unexpected ""session no longer valid"" in automated test","unexpected session no longer valid message
+
+Seen in some automated tests, for example https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/410/testReport/(root)/VisualEditor/Edit_with_strings__outline_example_____Editing_with_%C3%A1%C3%A9%C3%AD%C3%B3%C3%BA___Editing_with_%C3%A1%C3%A9%C3%AD%C3%B3%C3%BA___/
+
+in the span of less than 90 seconds, this test does these steps: 
+
+* start a browser (Firefox)
+* login to beta labs and navigate to an editable page
+* dismisses the beta warning
+* edits the page with a smallish string
+* click Save page
+* click This is a minor edit
+* click Review your changes
+* click Return to save form
+* edit the description of the change
+* click Save page the second time
+
+At the last step, the result shows an error message ""Warning: we could not process your edit because the session was no longer valid..."" 
+
+See screen shot.  
+
+Note in the screen shot that the user is still logged in properly at the time they receive the error message.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12866}",1395418080,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-rmjs32q5moc3ksh5b4i6,task_description,resolved
+"unexpected ""session no longer valid"" in automated test",Wasn't this the bug that was caused by the mobile test for logging the user out running in parallel?,1417482592,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rmjs32q5moc3ksh5b4i6,task_subcomment,NA
+Load charset into special characters option,"I think its great that developers add special characters option. While I would see here an improvment to load on every different wikipedia its charset, which was after the years of its ussage developed. Its not an ""extra"" of folks, its the fact that every language has some specifics (Spanish ¿, Czech „“) which are not native to keyboards. But yet when we want to have a clear and quality ecyclopedia we use them.",1395392760,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-kvfwa2nd6meb57icljm7,task_description,resolved
+Load charset into special characters option,VisualEditor has used MediaWiki core's list of characters since around March.,1438804265,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kvfwa2nd6meb57icljm7,task_subcomment,NA
+VisualEditor:  Ctrl-clicking on redlinks (only) in a subpage takes you to the wrong page title,"Intention:
+Find out why [[Page]] was a redlink by opening the link in another window.
+
+Steps to Reproduce:
+1. Open a sandbox in a subpage, e.g. [[User:Example/Sandbox]]
+
+2. Add a redlink to a non-existent [[Page]].
+
+3. Ctrl-click on the redlink to open the non-existent page in another tab.
+
+4. See that the page actually opened in [[User:Example/Page]] instead of at [[Page]].
+
+
+
+Reproducible: Always
+
+This was fixed in Bug 59196 but has re-appeared for redlinks only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395336660,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-u3drbnyix6yjkcu5oyqk,task_description,resolved
+VisualEditor:  Ctrl-clicking on redlinks (only) in a subpage takes you to the wrong page title,"
+
+*** This bug has been marked as a duplicate of bug 58314 ***",1395344091,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-u3drbnyix6yjkcu5oyqk,task_subcomment,NA
+VisualEditor:  Redirects not found when you try to make a link (wmf18),"Intention:
+Add a link to a redirect page.
+
+Steps to Reproduce:
+1. Go to Mediawiki.org.  Open a page in VisualEditor and type some text.
+
+2. Select a word and try to link it to [[Help:Help]], an existing redirect page.
+
+
+
+Actual Results:  
+It claims that the existing page is a ""New Page""/redlink.
+
+
+Reproducible: Always
+
+This only happens at Mediawiki.org  The problem cannot be reproduced at either beta labs or at the Wikipedias, so it must be something in wmf18.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395184080,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ip33qxtt2biyhu6zcsou,task_description,resolved
+VisualEditor:  Redirects not found when you try to make a link (wmf18),"
+
+*** This bug has been marked as a duplicate of bug 54361 ***",1395185089,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-ip33qxtt2biyhu6zcsou,task_subcomment,NA
+VisualEditor:  Text-oriented templates don't wrap normally,"What the page ought to look like
+
+If you have an inline template (like {{highlight}} at en.wp) with a lot of text in it, the text needs to wrap instead of behaving like a block.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13155}",1395169320,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ly47mruxj7vi65vxkzoe,task_description,resolved
+VisualEditor:  Text-oriented templates don't wrap normally,"
+
+*** This bug has been marked as a duplicate of bug 51708 ***",1395169574,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ly47mruxj7vi65vxkzoe,task_subcomment,NA
+VisualEditor:  Text-oriented templates don't wrap normally,"Created attachment 14855
+What the page actually looks like inside VisualEditor
+
+**Attached**: {F13156}",1395169368,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ly47mruxj7vi65vxkzoe,task_subcomment,NA
+VisualEditor:  Selection problems involving sfn template in Safari,"Steps to Reproduce:
+1. Using Safari, open https://en.wikipedia.org/w/index.php?oldid=600087421 and scroll to the ==Referenced text== (first) section.
+
+2. Select a sentence in the first paragraph, including at least one <ref> tag.
+
+3. Control-click on your choice of ""refs"" in the next paragraph.  (These are all {{sfn}} templates.)
+
+4.  Pretty, isn't it?
+
+Actual Results:  
+Text all over the page was selected, but not box-type templates.
+
+
+Reproducible: Sometimes
+
+Unable to reproduce in Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395103080,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ynfnvjveqi44j7uneaz3,task_description,resolved
+VisualEditor:  Selection problems involving sfn template in Safari,Seems to be long-fixed?,1417578429,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ynfnvjveqi44j7uneaz3,task_subcomment,NA
+VisualEditor:  Selection problems involving sfn template in Safari,"Created attachment 14845
+Screenshot showing strange selection pattern
+
+**Attached**: {F13075}",1395103309,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ynfnvjveqi44j7uneaz3,task_subcomment,NA
+Display the version of VisualEditor in help popup,"Would be nice to see this there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395097560,PHID-USER-b27lopawgf2h6utuuqyi,False,PHID-TASK-7xrtsoeeizfsiz3k6g62,task_description,resolved
+Display the version of VisualEditor in help popup,"This was done in bug 53050. Unfortunately due to bug 53972 it doesn't display in production for Wikimedia sites yet, sorry.
+
+*** This bug has been marked as a duplicate of bug 53972 ***",1395351525,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7xrtsoeeizfsiz3k6g62,task_subcomment,NA
+VisualEditor:  What you see is not the Babel box that you get,"Intention:
+Add a Babel box
+
+Steps to Reproduce:
+1. Add {{#babel:en|de-1|es-1|vo-0}} using the workaround described in bug 62750.
+
+2. Look at the results.
+
+3. Save the page.  Look at the very different results.
+
+Actual Results:  
+See the screenshot.  The first shows the left-aligned box before save; the second shows the right-aligned, colorful box after the save.
+
+Expected Results:  
+What you saw in VisualEditor would have some signficant relationship to what you saw when the page was saved.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395083220,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-67pmnsh7dhho75ccfvye,task_description,resolved
+VisualEditor:  What you see is not the Babel box that you get,Re-checked it in production - no difference in displaying {{#babel:en|de-1|es-1|vo-0}} in VE and in Read mode.,1425682420,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-67pmnsh7dhho75ccfvye,task_subcomment,NA
+VisualEditor:  What you see is not the Babel box that you get,"Created attachment 14838
+Screenshots showing radically different displays of the same content pre- and post-saving.
+
+**Attached**: {F13023}",1395083273,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-67pmnsh7dhho75ccfvye,task_subcomment,NA
+"When cutting and pasting list items, it is hard to achieve the intended formatting","If I cut items from a bulleted list and try to past them into another bulleted list, the formatting gets confusing:
+
+*Extra empty bullets get left behind when I cut.
+*The relationship between an existing list and new items I paste to the end of it can be wonky. Extra line breaks appear, and sub-bullets lost their relationship to each other, so that pressing tab to increase the level of indentation sometimes creates two bullets in a row instead of just increasing the level of indentation.
+
+See this screen recording for more details of my experience: https://commons.wikimedia.org/wiki/File:Screen_recording_of_trying_to_move_bulleted_list_items_in_VisualEditor.ogv
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395080580,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-26ap2rg73qekvvcczshf,task_description,resolved
+"When cutting and pasting list items, it is hard to achieve the intended formatting","Appears to be fixed now. If you can still reproduce, please reopen.",1429223053,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-26ap2rg73qekvvcczshf,task_subcomment,NA
+VisualEditor: Edit links are not appearing for the headings in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add some headings
+3.Save the page
+
+Observed Result:
+
+Edit links are not appearing for the headings
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13017}",1395080160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d3gqxoje5kzf5dkzzc7n,task_description,invalid
+VisualEditor: Edit links are not appearing for the headings in Betalabs,Was caused by a transcluded page that set __NOSECTIONEDIT__,1395081382,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d3gqxoje5kzf5dkzzc7n,task_subcomment,NA
+VisualEditor: Edit links are not appearing for the headings in Betalabs,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/17thMarchrome",1395080266,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d3gqxoje5kzf5dkzzc7n,task_subcomment,NA
+"Description of tags ""VisualEditor: Check"" and ""VisualEditor: Switched"" are hard to translate","In its current form I'm always wondering ""check what?"" and ""switched what?""
+
+Can't them be replaced by sentences like ""Switched from VisualEditor"" and ""Check VisualEditor errors"" or something better?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394887140,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-7knsheja5rlwn5x4ough,task_description,declined
+"Description of tags ""VisualEditor: Check"" and ""VisualEditor: Switched"" are hard to translate",=/,1400032552,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-7knsheja5rlwn5x4ough,task_subcomment,NA
+"Description of tags ""VisualEditor: Check"" and ""VisualEditor: Switched"" are hard to translate","(In reply to Helder from comment #0)
+> In its current form I'm always wondering ""check what?"" and ""switched what?""
+> 
+> Can't them be replaced by sentences like ""Switched from VisualEditor"" and
+> ""Check VisualEditor errors"" or something better?
+
+Space is at a premium where tags are involved. They occur in page histories, recent changes, watchlists, diffs, IRC feeds, and other places. Brevity is important.
+
+Also, as Alex says, if this is just fixing the qqq messages to make these clearer, this can be done at TranslateWiki.net without the need for a bug.",1400014248,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7knsheja5rlwn5x4ough,task_subcomment,NA
+"Description of tags ""VisualEditor: Check"" and ""VisualEditor: Switched"" are hard to translate",Aren't the docs supposed to clear up issues like this? Are they insufficient?,1400013182,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-7knsheja5rlwn5x4ough,task_subcomment,NA
+"VisualEditor: On opening a page that contains only a template, template is selected but you can't edit the template","Intention:
+Edit https://www.mediawiki.org/wiki/User:Quiddity_(WMF)
+
+
+Steps to Reproduce:
+1. Click on https://www.mediawiki.org/wiki/User:Quiddity_%28WMF%29?veaction=edit
+
+2. Template is selected.
+
+3. But there's no puzzle piece, and you can't edit it.
+
+
+Actual Results:  
+You can't edit the template unless you click outside the template (e.g., in the title or on a blank spot in the sidebar) first.
+
+
+Reproducible: Always
+
+See bug 62542, for inability to use cursor keys to deselect the template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394818380,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-psa6ws3eur6fpdx4wxx6,task_description,resolved
+"VisualEditor: On opening a page that contains only a template, template is selected but you can't edit the template","Merging with the more general bug 57477.
+
+*** This bug has been marked as a duplicate of bug 57477 ***",1394818952,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-psa6ws3eur6fpdx4wxx6,task_subcomment,NA
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,"See icons overlapping other elements at
+https://commons.wikimedia.org/wiki/File:Bug_EV_insertion_mod%C3%A8les_ic%C3%B4ne_d%C3%A9plac%C3%A9e.png
+https://commons.wikimedia.org/wiki/File:Bug_EV_-_insertion_mod%C3%A8les_ic%C3%B4ne_d%C3%A9plac%C3%A9e_02.png
+https://commons.wikimedia.org/wiki/File:Bug_EV_-_insertion_mod%C3%A8les_ic%C3%B4ne_d%C3%A9plac%C3%A9e_03.png
+
+You can also see this very easily through the Options menu on other sites.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394811240,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_description,duplicate
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,duplicate of bug 63127,1398377862,PHID-USER-hhw22zfd2xzrsyc22lp5,True,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_subcomment,NA
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,"Some texts on the ""page options"" menu are unreadable because there is some buttons in wrong places. At least I can't check ""redirect this page to"" checkbox because the button is on the checkbox.
+
+Sorry about my ""ASAP"" comment. It looks bad, but there's no ""ASAP"" hurry (and for the record, I've never done any patches [maybe I need to learn]).",1396206923,PHID-USER-6majuboi566q3ozbh27r,True,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_subcomment,NA
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,"So does this ""only"" look bad, or is actually some functionality broken (icon is a button which is not clickable anymore but should be, etc)?
+ 
+I'm slightly allergic to ""should do ASAP"" comments -- if things should be fixed ASAP, providing a patch helps more than adding comments about ASAP. ;))",1396206262,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_subcomment,NA
+VisualEditor: Visualization issues with Firefox Aurora 29.0a2,The same problem exists also with Firefox 28.0. Should be fixed ASAP.,1396109201,PHID-USER-6majuboi566q3ozbh27r,True,PHID-TASK-y2qrrzk3vroo6d7obsoq,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","Clicking ""Edit"" (VisualEditor) on https://wikitech.wikimedia.org/wiki/Shell_Request/Rxy shows an error from the server about content model json being incompatible.
+
+However VisualEditor shouldn't initialise that far in the first place, we know the content model (conf.wgPageContentModel).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394654460,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_description,invalid
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","(In reply to Yaron Koren from comment #6)
+> I'm marking this as ""invalid"" - I would change the component to Semantic
+> MediaWiki, but that's not longer on Bugzilla. If you want to submit it as an
+> SMW bug, you need to go to the SMW GitHub page.
+
+Since the bug was filed it appears the page linked has been converted to actually be wikitext-based – Krinkle, can we leave this closed or do we need to raise a GitHub issue?
+
+(I note that it is actually wikitext, not JSON, content; perhaps us having a year-old version of SMW doesn't help.)",1405388498,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","I'm marking this as ""invalid"" - I would change the component to Semantic MediaWiki, but that's not longer on Bugzilla. If you want to submit it as an SMW bug, you need to go to the SMW GitHub page.",1405378673,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","Yes, Semantic Forms only provides the edit button/page - it doesn't affect the actual content page. If any SMW-related extension is causing this error, I would assume it's Semantic MediaWiki itself.",1395661352,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","(In reply to Yaron Koren from comment #3)
+> Well, ""lies"" is a strong word. :) What makes you think this problem comes
+> from Semantic Forms?
+
+
+The wiki uses Semantic MediaWiki, and this is FormEdit-able page (Special:Formedit). That's Semantic Forms, right?
+
+Or is the turning the page itself into semantic data done (json content model) done by another Semantic extension and Semantic Forms only provides the special page and edit button?",1395452387,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","Well, ""lies"" is a strong word. :) What makes you think this problem comes from Semantic Forms? Is it just the fact that the page uses a form?
+
+Also, you wrote, ""it admits its JSON"", meaning that the page really holds JSON but claims that it's holding wikitext. Isn't the problem the other way around?",1394713774,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","OutputPage.php exports:
+
+> 'wgPageContentModel' => $title->getContentModel(),",1394654727,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+"SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)","Hm... Looks like a bug with Semantic MediaWiki.
+
+It is exporting mw.config wgPageContentModel = 'wikitext', and yet when you really ask it it admits its JSON.
+
+> > mw.config.get( 'wgPageContentModel' );
+> < ""wikitext""
+
+> click ""Edit""
+> < AJAX Eror
+> {
+>   .. Exception Caught: The content format json is not supported by the content model wikitext.",1394654629,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nmx2oitfu5c5j3jvk2xb,task_subcomment,NA
+External link with embedded comment is not shown correctly,"The first external link in the ""Further reading"" section of https://en.wikipedia.org/w/index.php?title=State_Patty%27s_Day&oldid=597985640&veaction=edit is not shown the same in VisualEditor as the PHP parser.
+
+In VE, the text shows as ""'s+Day%22&hl=en&sa=X&ei=7XQyUaeaD4LqiQL9zIHIBw&ved=0CDAQ6AEwAA#v=onepage&q=%22State%20Patty's%20Day%22&f=false Early Adulthood in a Family Context - Alan Booth - Google Books"".
+
+In a normal view (https://en.wikipedia.org/w/index.php?title=State_Patty%27s_Day&oldid=597985640), it shows as ""Early Adulthood in a Family Context - Alan Booth - Google Books"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394349000,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-rowxfowcw2djnxscevba,task_description,declined
+External link with embedded comment is not shown correctly,This appears to now work.,1398901917,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rowxfowcw2djnxscevba,task_subcomment,NA
+VisualEditor:  Template converted to span tags at Javanese Wikipedia,"https://jv.wikipedia.org/wiki/Cithakan:Lahirmati (Template:Birth and death) is converted to span tags in this edit:  https://jv.wikipedia.org/w/index.php?title=Jojon&curid=74332&diff=881686&oldid=830430
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394236920,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-33whpxom3nwt6xusuiuy,task_description,invalid
+VisualEditor:  Template converted to span tags at Javanese Wikipedia,No steps to reproduce given in the past three years.,1533062237,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-33whpxom3nwt6xusuiuy,task_subcomment,NA
+VisualEditor:Trying to add an image as a bullet list item removes the bullet but the Bullet list option remains selected in the menu,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a bullet list
+3.Insert an image as an item to the bullet list.
+
+Observed Result:
+The bullet goes away but if you place the cursor in that position the bullet list icon remains active in the menu.
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13399}",1394156280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bw6f5yfozkwjmdh33dvf,task_description,resolved
+VisualEditor: Typing into empty paragraph with inspector open creates pawn,"1. Open empty.html in SA demo
+2. Open the language inspector or the special character inspector
+3. Type, a pawn appears
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393957200,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dwxkxakygop4b2h6bkwj,task_description,resolved
+VisualEditor: Typing into empty paragraph with inspector open creates pawn,Fixed these focus/range issues a while ago.,1402834213,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dwxkxakygop4b2h6bkwj,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","The fix for bug 48418 made the assumption that {CREDITS|AUTHORS}.* files were wikitext (with the implication that wikitext bullets should precede each file), contrary to expectations.
+
+Instead, we should treat their contents as the plain text they (mostly) were until this feature was added, and merely wrap them in <pre>s for Special:Version/Credits/… etc. purposes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1393866300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4fzagmogxghtgnyhorob,task_description,resolved
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116517 merged by jenkins-bot:
+Reformat AUTHORS as wikitext
+
+https://gerrit.wikimedia.org/r/116517",1394044641,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116515 merged by Mwalker:
+Special:Version: Treat AUTHORS.txt and CREDITS.txt as text, not wikitext
+
+https://gerrit.wikimedia.org/r/116515",1393873494,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116516 abandoned by Jforrester:
+Reformat AUTHORS as wikitext
+
+Reason:
+Already done in I213caa7692bdb0a.
+
+https://gerrit.wikimedia.org/r/116516",1393872025,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116517 had a related patch set uploaded by Anomie:
+Reformat AUTHORS as wikitext
+
+https://gerrit.wikimedia.org/r/116517",1393869492,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116516 had a related patch set uploaded by Anomie:
+Reformat AUTHORS as wikitext
+
+https://gerrit.wikimedia.org/r/116516",1393869483,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","Change 116515 had a related patch set uploaded by Anomie:
+Special:Version: Treat AUTHORS.txt and CREDITS.txt as text, not wikitext
+
+https://gerrit.wikimedia.org/r/116515",1393869471,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","(In reply to Brad Jorsch from comment #3)
+> (In reply to James Forrester from comment #0)
+> > Instead, we should treat their contents as the plain text they (mostly) were
+> > until this feature was added
+> 
+> I'm not sure about ""mostly"".
+> 
+> I haven't tried to account for changes since this feature was added, but
+> looking at the situation now for extensions in git, these appear to be
+> wikitext:
+> * CentralNotice/CREDITS
+> * CirrusSearch/CREDITS
+> * MultimediaViewer/AUTHORS
+> * RevisionCommentSupplement/CREDITS
+> * UniversalLanguageSelector/CREDITS
+> * UploadWizard/CREDITS
+> * Wikilog/CREDITS
+> * WikiLove/CREDITS
+> 
+> These don't:
+> * BetaFeatures/AUTHORS
+> * ContentTranslation/AUTHORS.txt
+> * EventLogging/AUTHORS
+> * Parsoid/AUTHORS.txt
+> * VisualEditor/AUTHORS.txt
+> 
+> Based on that, I'd lean towards renaming BetaFeatures/AUTHORS and
+> EventLogging/AUTHORS to have a "".txt"" extension (or just reformat them as
+> wikitext) and only apply <pre> if the file used ends in "".txt"".
+
+Works for me; have re-named the bug appropriately.",1393868488,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","(In reply to James Forrester from comment #0)
+> Instead, we should treat their contents as the plain text they (mostly) were
+> until this feature was added
+
+I'm not sure about ""mostly"".
+
+I haven't tried to account for changes since this feature was added, but looking at the situation now for extensions in git, these appear to be wikitext:
+* CentralNotice/CREDITS
+* CirrusSearch/CREDITS
+* MultimediaViewer/AUTHORS
+* RevisionCommentSupplement/CREDITS
+* UniversalLanguageSelector/CREDITS
+* UploadWizard/CREDITS
+* Wikilog/CREDITS
+* WikiLove/CREDITS
+
+These don't:
+* BetaFeatures/AUTHORS
+* ContentTranslation/AUTHORS.txt
+* EventLogging/AUTHORS
+* Parsoid/AUTHORS.txt
+* VisualEditor/AUTHORS.txt
+
+Based on that, I'd lean towards renaming BetaFeatures/AUTHORS and EventLogging/AUTHORS to have a "".txt"" extension (or just reformat them as wikitext) and only apply <pre> if the file used ends in "".txt"".",1393868233,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","(In reply to MZMcBride from comment #1)
+> This bug can probably be marked with the ""easy"" keyword, if there's
+> consensus to change the behavior.
+
+Agreed, but let's get rough consensus first.",1393866491,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+"Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext","This bug can probably be marked with the ""easy"" keyword, if there's consensus to change the behavior.",1393866437,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-4fzagmogxghtgnyhorob,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"List of repositories that need to be updated is here:
+
+https://github.com/wikimedia/mediawiki-selenium#links
+
+Do not forget mediawiki_selenium gem.
+
+To update Ruby to version 2.1.1, locate Gemfile file, either in the root of the repository (mediawiki_selenium) or in tests/browser folder, or in /modules/ve-mw/test/browser folder (VisualEditor).
+
+The first line in the Gemfile should be changed from:
+
+#ruby=ruby-2.1.0
+
+to
+
+#ruby=ruby-2.1.1
+
+Then, Jenkins jobs that run Selenium tests should be updated. The repository is located here:
+
+https://github.com/zeljkofilipin/jenkins-job-builder-config
+
+Find all files that contain this:
+
+RUBY_VERSION=2.1.0
+
+and replace it with:
+
+RUBY_VERSION=2.1.1
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1393865280,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_description,resolved
+Upgrade Ruby to version 2.1.1,(Should've been changed back to RESOLVED FIXED over a month ago.),1407267501,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 141134 abandoned by Alex Monk:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/141134",1403359394,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 141134 had a related patch set uploaded by Inchikutty:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/141134",1403352876,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"I have pushed the changes to Cloudbees, Ruby 2.1.1 installs just fine:
+
+https://wmf.ci.cloudbees.com/job/CirrusSearch-en.wikipedia.beta.wmflabs.org-linux-firefox/42/console",1394022585,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"(In reply to Vikas from comment #16)
+> I have sent you pull request from github to Jenkins jobs. Here is the link
+> 
+> https://github.com/zeljkofilipin/jenkins-job-builder-config/pull/1
+
+Merged into master branch.",1394021890,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116705 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116705",1394017908,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116704 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116704",1394017887,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116708 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116708",1394016931,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116707 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116707",1394016903,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116709 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116709",1394016829,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116710 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116710",1394016817,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116711 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116711",1394016751,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116715 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116715",1394016698,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116716 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116716",1394016653,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116522 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116522",1394016631,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116712 merged by jenkins-bot:
+[Browser tests] Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116712",1394016508,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116529 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116529",1394016387,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116706 merged by jenkins-bot:
+QA: Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116706",1393975011,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116700 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1 in tests/browser
+
+https://gerrit.wikimedia.org/r/116700",1393946469,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116713 merged by jenkins-bot:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116713",1393924515,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"I have sent you pull request from github to Jenkins jobs. Here is the link
+
+https://github.com/zeljkofilipin/jenkins-job-builder-config/pull/1",1393910405,PHID-USER-b5bosdf7b7zp3vqofbug,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116522 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116522",1393908508,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116529 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116529",1393908481,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116700 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1 in tests/browser
+
+https://gerrit.wikimedia.org/r/116700",1393908393,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116716 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116716",1393905780,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116715 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116715",1393905630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116713 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116713",1393905247,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116712 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116712",1393904603,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116711 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116711",1393904358,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116710 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116710",1393904157,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116709 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116709",1393903985,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116708 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116708",1393903761,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116707 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116707",1393903714,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116706 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116706",1393903051,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116705 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116705",1393902648,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+Upgrade Ruby to version 2.1.1,"Change 116704 had a related patch set uploaded by Vikassy:
+Updated Ruby version from 2.1.0 to 2.1.1
+
+https://gerrit.wikimedia.org/r/116704",1393902256,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lcdwdqoqbndlmqibkajx,task_subcomment,NA
+VisualEditor: Cannot go to a newline after undoing a heading format and Uncaught TypeError: Cannot call method 'getModel' of null appears in the console,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Create a heading
+3.Undo creating the heading and type something in that line instead
+4.Press enter
+
+Observed Result:
+
+Uncaught TypeError: Cannot call method 'getModel' of null appears in the console and user cannot go to the next line anymore and has to cancel that session.
+
+See the screenshot attached,
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:
+https://test2.wikipedia.org/w/index.php?title=27thfebchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13193}",1393529760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k2jmjawnw4bqcn7k66fw,task_description,resolved
+VisualEditor: Cannot go to a newline after undoing a heading format and Uncaught TypeError: Cannot call method 'getModel' of null appears in the console,"I'm going to take a wild guess and claim that this is a DUPE of bug 59911, but we should verify.
+
+*** This bug has been marked as a duplicate of bug 59911 ***",1393530490,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k2jmjawnw4bqcn7k66fw,task_subcomment,NA
+VisualEditor: Cannot go to a newline after undoing a heading format and Uncaught TypeError: Cannot call method 'getModel' of null appears in the console,"It happens in FireFox too, but the error message is different there:
+TypeError: outermostNode is null
+	
+
+...unt=outerParent.getChildren().length;if(outermostNode.type==='listItem'&&outerPa...",1393529979,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k2jmjawnw4bqcn7k66fw,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist","Steps to reproduce:
+
+1.Open a page with VE which has a reflist at the end of the page
+
+2.Place your cursor at the end of the page and press enter to add a newline
+
+Observed Result:
+No newline gets added and an error appears in the console:
+
+
+Uncaught TypeError: Cannot call method 'getModel' of null load.php:268
+ve.ce.Surface.handleEnter load.php:268
+ve.ce.Surface.onDocumentKeyDown load.php:247
+proxy load.php:10
+ve.EventSequencer.onEvent load.php:21
+(anonymous function) load.php:20
+jQuery.event.dispatch load.php:45
+elemData.handle.eventHandle load.php:38
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393368000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6si76vcvgzigcakihtz4,task_description,resolved
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist",This issue got resolved with  bug 59911,1393634687,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6si76vcvgzigcakihtz4,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist","This is almost certainly the same as bug 59911; merging with that.
+
+*** This bug has been marked as a duplicate of bug 59911 ***",1393474369,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6si76vcvgzigcakihtz4,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist","**cornel.punga** wrote:
+
+I confirm it. Reproduced both steps, same error, no newline added.",1393370044,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6si76vcvgzigcakihtz4,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getModel' of null "" appears while trying to add newline after a reflist","Created attachment 14682
+Screenshot
+
+**Attached**: {F12998}",1393368734,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6si76vcvgzigcakihtz4,task_subcomment,NA
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity","Hello,
+French Wikiversity need help to fixe the visual editor working on the ""recherche:"" space name.
+Thanks a lot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393274880,PHID-USER-mxwamhfxuzomk4umydpl,False,PHID-TASK-sdhut7ee3wusfacg3uhp,task_description,resolved
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity","Now done. If you want any further changes, happy to help!",1393289954,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sdhut7ee3wusfacg3uhp,task_subcomment,NA
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity","Change 115299 merged by jenkins-bot:
+Enable VE in the ""Recherche:"" (104) namespace for frwikiversity
+
+https://gerrit.wikimedia.org/r/115299",1393286747,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdhut7ee3wusfacg3uhp,task_subcomment,NA
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity","Change 115299 had a related patch set uploaded by Jforrester:
+Enable VE in the ""Recherche:"" (104) namespace for frwikiversity
+
+https://gerrit.wikimedia.org/r/115299",1393276836,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdhut7ee3wusfacg3uhp,task_subcomment,NA
+"Enable VisualEditor in the ""Recherche:"" (104) namespace for frwikiversity",No problem. Do you also want it on the Projet / Faculté / Département namespaces?,1393275125,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sdhut7ee3wusfacg3uhp,task_subcomment,NA
+VisualEditor:  Cursor behavior inconsistent when setting redirects,"Steps to reproduce:
+
+1.  Go to Page settings to set a redirect.  
+
+2.  Skip the tick box; just click in the field and type in your page name.
+
+3.  Apply changes.
+
+4.  Change your mind.  Go back to Page settings.  Untick the checkbox.
+
+5.  Apply changes.
+
+6.  Figure out the perfect target.  Go back to Page settings.  
+
+7.  Skip the tick box, just like you dud in Step 2; just click in the field.  Why won't it let me type there now?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1393271520,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-355w7hlobmllbrlusrps,task_description,resolved
+VisualEditor:  Cursor behavior inconsistent when setting redirects,"(In reply to WhatamIdoing from comment #0)
+> 7.  Skip the tick box, just like you dud in Step 2; just click in the field.
+> Why won't it let me type there now?
+
+Because it shouldn't have let you type there initially (bug 61864), but there was a line missing from the logic.
+
+*** This bug has been marked as a duplicate of bug 61864 ***",1393272393,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-355w7hlobmllbrlusrps,task_subcomment,NA
+VisualEditor: Parameter box is too small,"picture of the box
+
+Parameter box is too small
+
+How to reproduce:
+1) go to https://en.wikipedia.org/wiki/Saint_Titus?veaction=edit
+2) click the ""multiple issues"" template on the top of the page and click ""transclusion""
+
+there is in the ""issues"" box:
+
+{{refimprove|date=December 2010}}
+{{lead too short|date=July 2013}}
+
+and I only can see a blank row and little bit of the first line of text. Boxes should be resizable/moveable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12824}",1393268700,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-2gcwk5t4olp3qx43ljc7,task_description,resolved
+VisualEditor: Parameter box is too small,"This is the same as 61289 which is already fixed and will be release to MediaWiki.org this Thursday.
+
+*** This bug has been marked as a duplicate of bug 61289 ***",1393271161,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2gcwk5t4olp3qx43ljc7,task_subcomment,NA
+"VisualEditor:  Make references visible for re-use when they're 'hidden' inside templates, e.g., list-defined refs in the reflist template","This is related to Bug 57209.
+
+List-defined references (https://en.wikipedia.org/wiki/Wikipedia:LDR#WP:LDR) are listed in the {{reflist}} template rather than in the regular text of the page. References that are defined inside the {{reflist}} are not visible when you try to re-use an existing reference.
+
+Steps to reproduce:
+
+1. Open a page that uses list-defined references with the {{reflist}} template (rather than <references></ref>).
+
+2. Go to Insert > Reference to add a new reference.  Click ""Re-use existing reference"".
+
+3. Discover that the numbers (""[1]"") and ref names are visible, but the contents are not.
+
+This problem does not exist if the non-template method is used.  This problem also exists for refs inside blockquotes, infoboxes, and other templates.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393019340,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-mw46y7ei5hcau3e3zb6y,task_description,invalid
+"VisualEditor:  Make references visible for re-use when they're 'hidden' inside templates, e.g., list-defined refs in the reflist template","Not possible without re-writing the Cite extension from scratch, which is sort-of planned but won't be done before 2015 at the earliest. Marking as ""INVALID"", but it's mostly a ""can't fix"".",1393537301,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mw46y7ei5hcau3e3zb6y,task_subcomment,NA
+VisualEditor: Gallery Highlight is not getting redrawn in correct position while changing the Heading style applied on it,"Screenshot-1
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a gallery
+3.Select the gallery and apply the formated Preformatted and observe the blue highlight box
+4.Deselect and again select the gallery
+5.Change the format to Paragraph to Heading and observe the position of the blue highlighted box
+
+Observed Result:
+The highlight box does not get reposition according to the new position of the gallery.
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/21stfebff?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13200}",1393012860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3jt32w56utgsiwksttva,task_description,resolved
+VisualEditor: Gallery Highlight is not getting redrawn in correct position while changing the Heading style applied on it,"Galleries can no longer take a paragraph style, which is correct and fixes this bug.",1402921436,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3jt32w56utgsiwksttva,task_subcomment,NA
+VisualEditor: Gallery Highlight is not getting redrawn in correct position while changing the Heading style applied on it,"Created attachment 14655
+Screenshot
+
+**Attached**: {F13201}",1393012989,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3jt32w56utgsiwksttva,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"Intention:
+Open https://en.wikipedia.org/wiki/Afroyim_v._Rusk (TFA) in VisualEditor.
+
+Steps to Reproduce:
+1. Click to the Main Page.
+2. Click to the article (https://en.wikipedia.org/wiki/Afroyim_v._Rusk)
+3. Click on ""Edit beta"".
+4. Wait a long time.
+5. Discover two copies of the entire article.
+
+Actual Results:  
+Two copies of the article appear, one above the other.  This happens in Safari 6 but not in Firefox 27; it happens only when editing the actual mainspace page, not when editing a copy in a sandbox.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392924060,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yifu433xtyd2cz6f7zjy,task_description,declined
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"(In reply to WhatamIdoing from comment #4)
+> I can't reproduce this right now.  However, the timestamp on the screenshot
+> is 10:55 a.m. PST (and it had been onscreen for a few minutes before then),
+> and I thought that the deployment was set to start about five minutes after
+> that.
+
+The new version went a little early today, apparently (but only by a few minutes – see https://wikitech.wikimedia.org/wiki/Server_Admin_Log#February_20 where ""testwiki to 1.23wmf15 and build l10n cache"" at 16:58, though the changes start a couple of minutes before the log), but there were bigger issues involving deployment today that took down all the phase0 wikis (yay). Nothing to do with VisualEditor, but might well have caused random and otherwise inexplicable issues like this.
+
+However, for enwiki changes didn't happen until 21:26, so it /shouldn't/ have been affected, so it's a bit of a mystery. :-(
+
+Marking as WORKSFORME for now.",1392940376,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"I can't reproduce this right now.  However, the timestamp on the screenshot is 10:55 a.m. PST (and it had been onscreen for a few minutes before then), and I thought that the deployment was set to start about five minutes after that.",1392936289,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"I've just loaded it 5 times (with hard refreshes) each in Chrome, Safari and Firefox, without incident – perhaps it could be an odd cacheing issue with the switch-over to the new version?
+
+Can you reproduce still?",1392924580,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"I have just managed to get the article to open with a single copy, so this is intermittent.  
+
+Also, notice the absence of VisualEditor's toolbar.  The top of the attached image is the top of the browser window.",1392924214,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor,"Created attachment 14636
+Screenshot showing the bottom of first copy of the article and the top of the second copy.
+
+**Attached**: {F13022}",1392924108,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yifu433xtyd2cz6f7zjy,task_subcomment,NA
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),"* Latest master mediawiki-core and VisualEditor
+* Edit Worksheet page
+* Open ""Options"" dialog
+
+Nothing happens, console shows:
+
+
+
+ Uncaught TypeError: undefined is not a function
+ >         this.tableOfContents = new OO.ui.FieldLayout(new OO.ui.ButtonSelectWidget({'$': this.$}).addItems([new OO.ui.ButtonOptionWidget('mwTOCForce', {'label': ve.msg('visualeditor-dialog-meta-settings-toc-force')}), new OO.ui.ButtonOptionWidget(
+ VeUiMWSettingsPage
+ ve.ui.MWMetaDialog.initialize
+ oo.EventEmitter.emit
+ (anonymous function)
+ pollExternalStylesheets
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1392864900,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hfgaosahvwicr3n3m3lj,task_description,declined
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),"[19:12]	Krinkle	Yeah, I just updated mw-core again and it works now",1392865971,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hfgaosahvwicr3n3m3lj,task_subcomment,NA
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),This works fine for me with the current MW core. Ensure you have https://gerrit.wikimedia.org/r/#/c/113508/ .,1392865953,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hfgaosahvwicr3n3m3lj,task_subcomment,NA
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),> OO.ui.FieldLayout is undefined,1392865156,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hfgaosahvwicr3n3m3lj,task_subcomment,NA
+[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function),(Can still reproduce on VisualEditor @ 0b97870 after todays' merges),1392865011,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hfgaosahvwicr3n3m3lj,task_subcomment,NA
+VisualEditor: Redirects have ./ added to them in round-trip,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Page Settings
+3.Check the box Redirect this page to and specify the page/article to which it will redirect to.
+4.Apply changes
+5.Save the page
+6.Reopen VE for this page
+
+
+Observed Result:
+The page settings page pops up with ./ appended as prefix to the article name
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/19thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13414}",1392855420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-g6ao2orn4uf6igum3xuw,task_description,resolved
+VisualEditor: Redirects have ./ added to them in round-trip,Verified the fix in test2,1392944712,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-g6ao2orn4uf6igum3xuw,task_subcomment,NA
+VisualEditor: Redirects have ./ added to them in round-trip,"Change 114381 merged by jenkins-bot:
+Deal with ./ prefixes etc. in MWRedirectMetaItem
+
+https://gerrit.wikimedia.org/r/114381",1392860306,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g6ao2orn4uf6igum3xuw,task_subcomment,NA
+VisualEditor: Redirects have ./ added to them in round-trip,"Change 114381 had a related patch set uploaded by Catrope:
+Deal with ./ prefixes etc. in MWRedirectMetaItem
+
+https://gerrit.wikimedia.org/r/114381",1392860099,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g6ao2orn4uf6igum3xuw,task_subcomment,NA
+VisualEditor: Redirects have ./ added to them in round-trip,"(In reply to ryasmeen from comment #0)
+> Created attachment 14632 [details]
+> Screenshot
+> 
+> Steps to reproduce:
+> 
+> 
+> 1.Open a page with VE
+> 2.Go to Page Settings
+> 3.Check the box Redirect this page to and specify the page/article to which
+> it will redirect to.
+> 4.Apply changes
+> 5.Save the page
+> 6.Reopen VE for this page
+> 
+> 
+> Observed Result:
+> The page settings page pops up with
+That's a feature.
+
+> ./ appended as prefix to the article name
+>
+That's a bug :(
+
+**Attached**: {F13414}",1392856659,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-g6ao2orn4uf6igum3xuw,task_subcomment,NA
+VisualEditor: Adding content with newline in Edit source mode appears with return arrow in VE mode then placing the content in the preceding line,"Screenshot
+
+Steps to reproduce:
+
+1.Go to Edit Source mode
+2.Add a text or anything else in a newline
+3.Save the page
+4.Open the page with VE
+
+Observed Result:
+The newly added text gets merged with the previous line adding a return character between the lines.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/19thfebchrome?veaction=edit
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13402}",1392853920,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n5bah7oda2vyaqmkor4k,task_description,resolved
+VisualEditor: Adding content with newline in Edit source mode appears with return arrow in VE mode then placing the content in the preceding line,"
+
+*** This bug has been marked as a duplicate of bug 48290 ***",1393537023,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n5bah7oda2vyaqmkor4k,task_subcomment,NA
+Stop specifying the (default) size of media items in VisualEditor,"If you add ""File:Example.jpg"", without actively specifying a size, then you should get [[File:Example.jpg|thumb|Here is a caption]].  You should not get [[File:Example.jpg|thumb|220x220px|Here is a caption]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392851220,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ilhxonhqlmyxfkhaqn34,task_description,resolved
+Stop specifying the (default) size of media items in VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 61324 ***",1393447031,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ilhxonhqlmyxfkhaqn34,task_subcomment,NA
+VisualEditor: Word missing from wikilink,"During a test,
+I tried to create a wikilink to
+http://fr.wikipedia.org/wiki/Cabin_Fever:_Patient_Zero .
+What I did was writing Cabin Fever: Patient Zero,
+then selecting all the 4 words, copy/pasting that precise URL and selecting the ""red"" option in the dropdown menu as if to link to a new page.
+The result is https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve2&diff=101406090&oldid=101406077 ,
+that shows up as [Fever: Patient Zero] in view mode, while the wikicode shows the word Cabin as an existing part of the label.
+This happened on both Chrome and FF, Win7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392833640,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mbgornmacv5hvpihufw2,task_description,resolved
+VisualEditor: Word missing from wikilink,Seems to be fixed now.,1437687504,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-mbgornmacv5hvpihufw2,task_subcomment,NA
+VisualEditor: Pressing tab does not take the cursor to the next field/parameter in a template dialog box,"Steps to reproduce:
+
+
+1.Open a page in VE
+2.Go to Insert>Transclusion
+3.Search for a template like Cite Web
+4.Click on ""Add template""
+5.When all the parameters appear, insert a value in one of the parameters then press tab to go to the next parameter.
+
+Observed Result:
+Pressing tab does take user to the next tab
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/New_deep?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392774900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u54zpp3nlpyzgygilqys,task_description,resolved
+VisualEditor: Pressing tab does not take the cursor to the next field/parameter in a template dialog box,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394827111,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u54zpp3nlpyzgygilqys,task_subcomment,NA
+VisualEditor: Pressing tab does not take the cursor to the next field/parameter in a template dialog box,Verified the fix in test2 environment,1394153427,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u54zpp3nlpyzgygilqys,task_subcomment,NA
+VisualEditor: Return arrow is getting placed after every element inside Reference Dialog box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in VE
+2.Add a reference to the page
+3.Open the reference dialog box
+4.Add a text
+5.Go to the next line and then a Cite web template 
+6.Go to the next line and add a math funtion
+7.Save the page
+8.Reopen the page and open the reference dialog box
+
+Observed Result:
+After every element return arrow is getting placed.
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/18thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13281}",1392755580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iij5s3q5lqjww4xxudga,task_description,invalid
+VisualEditor: Return arrow is getting placed after every element inside Reference Dialog box,"I think this is just an artefact of ""↵"" characters being show for the <br />s put in by Parsoid…",1406754132,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iij5s3q5lqjww4xxudga,task_subcomment,NA
+VisualEditor Math plugin displayed equation becomes jumbled during and after editing if using MathJax,"Split off from bug 43058.
+
+Editing the last equation at 
+https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+
+if you actually make a change to the text of the equation the displayed equation becomes very jumbled. Any vertical positioning is lost, and text from different lines are overlaid on top of each other.
+
+This happens with Chrome on a Mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52499",1392739320,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-se5cgamgbkdgfzjnta6l,task_description,declined
+VisualEditor Math plugin displayed equation becomes jumbled during and after editing if using MathJax,MathJax will be removed T99369,1437345483,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-se5cgamgbkdgfzjnta6l,task_subcomment,NA
+VisualEditor Math plugin displayed equation becomes jumbled during and after editing if using MathJax,"The problem seems to be a clash of CSS styling. MathJax makes heavy use of position: absolute, position: relative and setting the top, and left properties eg
+
+<span style=""position: absolute; clip: rect(1.501em 1000.003em 2.347em -0.518em); top: -2.145em; left: 0.003em;"">...</span>
+
+yet this is all rendered to nothing by the CSS rule
+
+.ve-ce-protectedNode, .ve-ce-protectedNode * {
+  position: relative !important;
+  top: 0 !important;
+  left: 0 !important;
+  bottom: 0 !important;
+  right: 0 !important;
+  ...
+}
+
+If you comment out these css properties the MathJax displays OK.",1398718384,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-se5cgamgbkdgfzjnta6l,task_subcomment,NA
+VisualEditor Math plugin displayed equation becomes jumbled during and after editing if using MathJax,"Created attachment 15234
+Screenshot of garbled output
+
+This is a screenshot of the type of output obtained. You need MathJax on and image will become garbled as soon as the formula is edited with the VisualEditor formulae editing beta feature.
+
+**Attached**: {F13244}",1398717990,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-se5cgamgbkdgfzjnta6l,task_subcomment,NA
+"Messages ""symbols"", ""accents"", ""math"" in special character inserter tool not translatable","The special character inserter tool has hard-coded texts which are not translatable.
+
+There is texts ""symbols"", ""accents"" and ""math"" which are not translatable, because there is no existing MediaWiki messages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392561840,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-qe7ct72pnrg4lcr747kr,task_description,invalid
+"Messages ""symbols"", ""accents"", ""math"" in special character inserter tool not translatable","(In reply to Stryn from comment #1)
+> I guess
+> https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-
+> specialcharinspector-characterlist-insert/en is the one that needs to be
+> translated.
+
+Correct.",1392741532,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qe7ct72pnrg4lcr747kr,task_subcomment,NA
+"Messages ""symbols"", ""accents"", ""math"" in special character inserter tool not translatable","BTW I just saw https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Feedback_for_the_character_inserter/reply_%2836%29
+
+so I guess https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-specialcharinspector-characterlist-insert/en is the one that needs to be translated.",1392569902,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-qe7ct72pnrg4lcr747kr,task_subcomment,NA
+VE is unable to insert a internal reference with sub-section,"**Author:** `paulomsimoes`
+
+**Description:**
+VE is unable to insert a internal reference with sub-section. Example:
+
+[[""Wikipédia Article name""#""Section name""]], return only [[""Wikipédia Article name""]] (without redirect to section), as per [https://pt.wikipedia.org/w/index.php?title=Faculdade_Salesiana_de_Maca%C3%A9&diff=38176530&oldid=38176349|this edit].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1392505740,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xbwpkppvqworctg5ub5j,task_description,resolved
+VE is unable to insert a internal reference with sub-section,"I don't understand this bug report, sorry.
+
+It is certainly possible right now to write ""Foo#Bar"" as your target, though VisualEditor doesn't validate ""#Bar"" as being a valid section so it may be confusing…
+
+Do you mean that you would expect the link inspector to understand sections and give a better experience for that? If so, I think this is bug 50881. Provisionally merging with that one.
+
+*** This bug has been marked as a duplicate of bug 50881 ***",1401417280,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xbwpkppvqworctg5ub5j,task_subcomment,NA
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","**Author:** `jhall`
+
+**Description:**
+The VisualEditor headings.feature has begun to fail[1] when run via CloudBees (but not when run locally).  Relevant Selenium log message is (example is for the ""Subheading1"" scenario, but the pattern is the same for all scenarios in this test):
+
+00:25:21.230 INFO - Executing: [find element: By.xpath: .//a[@title='^3']] at URL: /session/83a0781b-247c-4f0a-88f8-a93cef166a15/element)
+00:25:21.247 WARN - Exception thrown
+org.openqa.selenium.NoSuchElementException: Unable to locate element: {""method"":""xpath"",""selector"":"".//a[@title='^3']""}
+Command duration or timeout: 13 milliseconds
+For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
+Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16 16:11:15'
+System info: host: 'chef', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'i386', os.version: '3.2.0-56-virtual', java.version: '1.6.0_31'
+Session ID: 185a49ff-3267-43a3-ad44-3e6881cd0d43
+Driver info: org.openqa.selenium.firefox.FirefoxDriver
+Capabilities [{platform=LINUX, acceptSslCerts=true, javascriptEnabled=true, browserName=firefox, rotatable=false, locationContextEnabled=true, version=26.0, cssSelectorsEnabled=true, databaseEnabled=true, handlesAlerts=true, browserConnectionEnabled=true, nativeEvents=false, webStorageEnabled=true, applicationCacheEnabled=true, takesScreenshot=true}]
+
+The problem does not repro when the test is run on a MacBook, and the insertion of the following command into the headings_steps.rb file at appropriate points succeeds as expected:
+
+@browser.a(:xpath, "".//a[@title='^3']"").should exist
+
+Need to figure out why these test scenarios fail when run via CloudBees, since they seem to be perfectly legitimate test cases.
+
+[1] https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/327/testReport/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1392418260,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_description,resolved
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","Chris, since we are moving away from Cloudbees, do you plan to investigate this or should be close it?",1398414326,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_subcomment,NA
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","All patches merged - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?",1398408179,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_subcomment,NA
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","Change 114114 merged by jenkins-bot:
+[Browser test] Repair broken ""header"" browser test
+
+https://gerrit.wikimedia.org/r/114114",1392771414,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_subcomment,NA
+"Investigate VisualEditor browser test failures for ""headings"" test run via CloudBees","Change 114114 had a related patch set uploaded by Jhall:
+[Browser test] Repair broken ""header"" browser test
+
+https://gerrit.wikimedia.org/r/114114",1392770355,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4pdqjq2wnzhgv26mfh6,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"screenshot
+
+Steps to reproduce
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Insert the search string ""April""
+
+Observed Result:
+
+An error appears in the console:
+Uncaught TypeError: Cannot read property '0' of undefined 
+
+and the search spinner continues indefinitely
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=14thfebchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12972}",1392407400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7ho2brlduxnhg2gejymz,task_description,resolved
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,Verified the fix on betalabs,1392939924,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"That, too, *should* be fixed with this commit.",1392431275,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"Change 113478 merged by jenkins-bot:
+Only display image info if that exists
+
+https://gerrit.wikimedia.org/r/113478",1392430497,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"There is another error appearing while I search for hoo:
+load.p...014333Z (line 583)
+TypeError: this.data.imageinfo is undefined
+
+Not Sure if it is related with this particular issue or not.",1392429573,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox,"Change 113478 had a related patch set uploaded by Mooeypoo:
+Only display image info if that exists
+
+https://gerrit.wikimedia.org/r/113478",1392419669,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7ho2brlduxnhg2gejymz,task_subcomment,NA
+VisualEditor: All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in test 2
+
+2.Select an image
+
+3.Go to the Media Settings >Advanced Settings for that image
+
+Observed Result:
+ All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2
+
+See the screenshot attached
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/13thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12856}",1392330060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-piljwz7ejgbgmrwmptju,task_description,resolved
+VisualEditor: All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2,Verified the fix on test 2,1392406219,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-piljwz7ejgbgmrwmptju,task_subcomment,NA
+VisualEditor: All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2,"Deployment issue, now fixed.",1392405621,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-piljwz7ejgbgmrwmptju,task_subcomment,NA
+VisualEditor: Blank edit notices for admins on each page at English Wikipedia,"As an admin on en.wp, I get a blank edit notice popup on every page I edit, with a red link to the page notice. I seem to recall that this is some interaction with local site JS/CSS, and that this was fixed at some point in the past.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43013",1392322980,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ciemclcqodgd6pk6mejb,task_description,resolved
+VisualEditor: Blank edit notices for admins on each page at English Wikipedia,"Merging into bug 43013. Gah. :-(
+
+*** This bug has been marked as a duplicate of bug 43013 ***",1394490038,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ciemclcqodgd6pk6mejb,task_subcomment,NA
+VisualEditor: Page Suggestions in link inspector are not appearing in FireFox on Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Create a link which has a target of existing page or a new page
+
+Observed Result:
+There is no drop down appearing with matched pages suggestion or a new page section.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:FF 25
+OS: MAC OS X 10. 8. 5
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_%28WMF%29&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13342}",1392240360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6hvjba3tuflbtzmptodb,task_description,declined
+VisualEditor: Page Suggestions in link inspector are not appearing in FireFox on Betalabs,I'm going to write this one us as a server issue.,1402550077,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6hvjba3tuflbtzmptodb,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"To reproduce:
+
+1. Go to https://en.m.wikipedia.org/wiki/ASCII in desktop Firefox.
+2. Press the pencil button to edit.
+
+Expected: The mobile editing is supposed to open.
+Observed:
+1. The editing interface doesn't open. The page stays the same.
+2. The following errors are displayed in the JS console:
+
+""Exception thrown by job.error"" (load.php:145)
+""Error: Container must be attached to the DOM"" [object Error] (load.php:145)
+
+This works in desktop Google Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392153780,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ljbacnsrtxmpcftewdk3,task_description,declined
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"(In reply to Juliusz Gonera from comment #6)
+> Also, Amir, if you're getting ""Error, can't load section."" on your local
+> instance that probably means you're trying to use VE without running Parsoid.
+
+Oh, useful to know. Thanks.",1392418256,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"**jgonera** wrote:
+
+Also, Amir, if you're getting ""Error, can't load section."" on your local instance that probably means you're trying to use VE without running Parsoid.",1392402195,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"The behavior described sounds like this was in experimental and likely an issue with VisualEditor. I am entirely unable to reproduce in FF or Chrome, in stable, beta, or alpha. I assume the issue was fixed since this was reported, so marking as WORKSFORME. Amir, please reopen if the issue is still present and let us know if you're in stable/beta/alpha.",1392401990,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"I can't reproduce in any mode, including experimental (on en.wiki or local master). Can someone verify whether or not it is still reproducable?",1392401949,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1697",1392400354,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,"If I try this on my local machine on master, I get something a bit different: I don't see JS errors, but I see a notification drawer at the bottom of the page:
+""Error, can't load section.""",1392194143,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+editing Wikipedia articles doesn't work in desktop Firefox with mobile interface,I can reproduce this in experimental mode (not in standard or beta).,1392159139,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-ljbacnsrtxmpcftewdk3,task_subcomment,NA
+VisualEditor:  Media Settings dialog always goes back to General settings if you switch windows while in Advanced settings,"Intention:
+Look up something in another window
+
+Steps to Reproduce:
+1. Open Media settings for an existing image, using Safari.
+
+2. Click on ""Advanced settings"".  Don't click inside any text field (e.g., width or height).
+
+3. Decide that you need to go to another window or browser tab for a moment, so click elsewhere.
+
+4. Go back to VisualEditor.
+
+5. Discover that the Media settings dialog has put you back in ""General settings"" again.
+
+Converse is also true:  if you put the text cursor in the ""Height"" box and then switch to ""General settings"" before leaving the page for a moment, you will be flipped back to ""Advanced settings"".
+
+
+
+Reproducible: Always
+
+Reproducible in Safari, not in Firefox.  Perhaps it's because Safari ""helpfully"" flips the box to wherever the text cursor is, and Firefox ignores it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392144240,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-olyocmpjb6k7cvxtzx7a,task_description,resolved
+VisualEditor:  Media Settings dialog always goes back to General settings if you switch windows while in Advanced settings,"
+
+*** This bug has been marked as a duplicate of bug 61062 ***",1392144760,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-olyocmpjb6k7cvxtzx7a,task_subcomment,NA
+VisualEditor:Double return arrow getting added after adding Galley just before a hiero,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a special character 
+3.Add a hiero on the next line
+4.Save the page 
+5.Reopen the page, add a gallery just after the special character but before hiero
+6.Save the page
+7.Reopen the page
+
+Observed Result:
+Double arrow appears just after gallery but before hiero
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Justhiero?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13041}",1392082080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nbxtzfyyzyj53uup2gmf,task_description,resolved
+VisualEditor:Double return arrow getting added after adding Galley just before a hiero,These don't show now; I think the upstream Parsoid fixes will have helped.,1406754182,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nbxtzfyyzyj53uup2gmf,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"Steps to reproduce:
+
+1.Open the page in VE
+2.Add an image
+3.Go to Media Settings>Advanced Settings
+4.Change the image type to Thumbnail ,Frame or Border
+5.Apply the changes
+
+Observed Result:
+There is no apparent different in either of these image types when selected
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=10thFeb&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392063240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dd4n7egyr75tqjapspdy,task_description,invalid
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,Per Moriel's statement in comment 4.,1395354454,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"Turns out: This is intended behavior.
+
+Images with |frameless but no position render as inline images in both Parsoid and the PHP Parser. That is, apparently, intended, as counterintuitive as it may be.
+
+Since we can't edit inline images just yet in VE, this turns out to be a bit of a hassle (and a bug) -- but hopefully very soon we'll be able to edit inline images in the media edit dialog, which would solve the issue of having the resulting image uneditable.",1392097815,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"Okay, for some reason, when an image has |frameless but no position set, VE intercepts it as an inline image.
+
+So, when a new image is inserted, the position is set to default (no representation in the wikitext) and when we set it to ""frameless"" it results in the following wikitext:
+
+[[File:Diplopedia main page.jpg|frameless|150x150px|]]
+
+It seems that since it's missing a position, VE reads it as an inline image.",1392066596,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"Sorry little change in the steps to reproduce:
+
+1.Open the page in VE
+2.Add an image
+3.Go to Media Settings>Advanced Settings
+4.Change the image type to Frameless
+5.Save the page
+6.Reopen the editor and go the media settings again
+7.Now change the image type to Thumbnail, then frame
+
+Observed Result:
+There is no thumbnail icon getting added in the VE mode unless user saves it, and then if he changes to frameless, it also looks pretty similar to the type thumbnail because both of them has no thumbnail icon beside the caption field.
+
+Selecting border also does not make any change compared to frameless which has a separate ticket:https://bugzilla.wikimedia.org/show_bug.cgi?id=61155",1392064737,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings,"I can't manage to reproduce in master in both Firefox 26.0 and Chrome 32.0 under Ubuntu.
+
+A new inserted image is inserted as ""thumb"" which is what I see selected in the media edit dialog when it's opened. Changing to ""frameless"" changes the type (and changes the view properly for me) as well as changing to ""Framed"" (though that one is a bit more subtle, because the difference between them isn't too noticeable)
+
+It seems to work for me as expected in master.",1392063878,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-dd4n7egyr75tqjapspdy,task_subcomment,NA
+Insert Media only searches commons,"**Author:** `robert.labrie`
+
+**Description:**
+The VisualEditor insert media only searches commons. I have a media item called ""WOM HighLevelDesign.png"" but when searching for HighLevelDesign there are no results. Looking at the request in Firebug:
+
+Request:
+GET http://commons.wikimedia.org/w/api.php?callback=jQuery18305320913342615314_1392057641882&format=json&action=query&generator=search&gsrsearch=HighLevelDesign&gsrnamespace=6&gsrlimit=15&gsroffset=0&prop=imageinfo&iiprop=dimensions%7Curl&iiurlheight=150 HTTP/1.1
+Host: commons.wikimedia.org
+User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0
+Accept: */*
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate
+Referer: http://opsdocs.carnival.com/index.php?title=Main_Page&veaction=edit
+Connection: keep-alive
+
+Response:
+HTTP/1.1 200 OK
+Via: 1.1 varnish, 1.1 varnish, 1.1 CCLPRDINFTMG3
+Connection: Keep-Alive
+Proxy-Connection: Keep-Alive
+Content-Length: 110
+Age: 0
+Date: Mon, 10 Feb 2014 19:33:02 GMT
+Content-Type: text/javascript; charset=utf-8
+Server: Apache
+Accept-Ranges: bytes
+X-Powered-By: PHP/5.3.10-1ubuntu3.9+wmf1
+x-content-type-options: nosniff
+Cache-Control: private
+x-frame-options: SAMEORIGIN
+Vary: Accept-Encoding,X-Forwarded-Proto
+X-Vary-Options: Accept-Encoding;list-contains=gzip,X-Forwarded-Proto,Cookie;string-contains=commonswikiToken;string-contains=commonswikiLoggedOut;string-contains=forceHTTPS;string-contains=commonswikiSession;string-contains=centralauth_Token;string-contains=centralauth_Session;string-contains=centralauth_LoggedOut;string-contains=mf_useformat;string-contains=stopMobileRedirect
+X-Varnish: 2999015801, 4264856558
+X-Cache: cp1055 miss (0), cp1052 frontend miss (0)
+
+
+jQuery18305320913342615314_1392057641882({""query"":{""searchinfo"":{""totalhits"":0,""suggestion"":""Hauserdesign""}}})
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392060960,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-irielkewu77v4z4a3hlm,task_description,invalid
+Insert Media only searches commons,This issue seems to be address with open task T188236,1717447423,PHID-USER-3baphe4xso6l4kkryqex,False,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,"Marking as INVALID; this isn't a bug in VisualEditor, but an artefact of the (not very good) search system in MediaWiki (and a continuing issue even with CirrusSearch).",1392774395,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,Can you also add a direct link to the image?,1392148110,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,"I've CC'd Nik Everitt, our CirrusSearch guru, to see if he can provide any insight.",1392147662,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,"After a bit of testing and fiddling around, there seems to be an issue with the API call itself and its response. 
+
+The API returns a list of matches by complete words, and it seems that it considers the suffix as a word as well.
+
+So, in my local wiki I have an image ""image of space.jpg"". 
+
+API calls:
+
+&gsrsearch=space.jpg --> 1 match
+&gsrsearch=space --> 0 matches
+&gsrsearch=image --> 1 matches
+&gsrsearch=from --> 0 matches
+&gsrsearch=image+from --> 1 match
+&gsrsearch=image+from+space --> 0 matches
+
+I am not sure if this is because of the specific query we use to search images or if this is an artefact of the API itself. 
+
+I'm conducting further research.
+
+Robert, if you have time to test this, try to see if you get the image you are looking for when typing ""HighLevelDesign.png"" or ""WOM"". Are you getting the local image on those searches?",1392146448,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+Insert Media only searches commons,"**robert.labrie** wrote:
+
+After cleaning my cache and setting $wgUseInstantCommons  = false; the result is now as follows:
+
+GET /api.php?format=json&action=query&meta=filerepoinfo HTTP/1.1
+Host: opsdocs.carnival.com
+User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0
+Accept: application/json, text/javascript, */*; q=0.01
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate
+X-Requested-With: XMLHttpRequest
+Referer: http://opsdocs.carnival.com/index.php?title=Main_Page&veaction=edit
+Cookie: wikidb796_session=86334fa21b8c09bd7c07958bdc0ac86e; wikidb796UserID=2; wikidb796UserName=CARNIVAL%5Crobertla; wikidb796Token=ceb473edd15eddf81147a6c9f583acf3; website#lang=en
+Connection: keep-alive
+
+
+HTTP/1.1 200 OK
+Cache-Control: private
+Content-Type: application/json; charset=utf-8
+Vary: Accept-Encoding
+Server: Microsoft-IIS/8.0
+X-Powered-By: PHP/5.3.24
+x-content-type-options: nosniff
+x-frame-options: DENY
+Persistent-Auth: true
+Date: Mon, 10 Feb 2014 19:55:15 GMT
+Content-Length: 198
+
+{""query"":{""repos"":[{""name"":""local"",""displayname"":null,""rootUrl"":""/images"",""local"":true,""url"":""/images"",""thumbUrl"":""/images/thumb"",""initialCapital"":true,""scriptDirUrl"":"""",""scriptExtension"":"".php""}]}}",1392062660,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-irielkewu77v4z4a3hlm,task_subcomment,NA
+VisualEditor: Text in Insert menu and in Option menu displays differently,"This happens with Monobook (I tried this with Chrome on fr. and it.wp).
+The text in the Option menu is in a larger and different font than the one under Insert.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392060360,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-6754fqjnk5hw4q6cz6zc,task_description,declined
+VisualEditor: Gallery remains highlighted even after clicking elsewhere in the page,"Screenshot
+
+Steps to reproduce:
+1.Open a page with Ve
+2.Select a gallery
+3.Open the gallery inspector 
+4.Click else where in the page to close the inspector
+
+Observed Result:
+The gallery remains highlighted in the page though it is not selected and link inspector is not appearing on the gallery
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12831}",1391816040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ximodnbmrouyqq5tnhwi,task_description,resolved
+VisualEditor: Gallery remains highlighted even after clicking elsewhere in the page,Appears to have been fixed a while ago.,1402921625,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ximodnbmrouyqq5tnhwi,task_subcomment,NA
+VisualEditor:  Odd removal of table inside an image caption,"Actual Results:  
+VisualEditor loses most of the table.
+
+
+Reproducible: Couldn't Reproduce
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Misl&diff=594020475&oldid=593707943
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49942",1391814720,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zmktchjngp5bwq3bloha,task_description,declined
+VisualEditor:  Odd removal of table inside an image caption,Probably a browser bug or flakiness.,1415883136,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zmktchjngp5bwq3bloha,task_subcomment,NA
+MathJax equations are centered,"MathJax has started centering displayed equations. For example
+https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:WikiProject_Mathematics&curid=148395&diff=594391082&oldid=594388357
+the display equation is centered. Previously they were aligned left.
+
+Looking at the generated the code we see 
+<div class=""MathJax_Display"" role=""textbox"" aria-readonly=""true"" style=""text-align: center;"">
+  <span class=""MathJax"" id=""MathJax-Element-2-Frame"" style=""""> ...
+  </span>
+</div>
+
+the centering is in the code rather than in a style sheet.
+
+Aligning equations to the left is the desirable format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391801640,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_description,resolved
+MathJax equations are centered,"**physik** wrote:
+
+I could not find any centered equations anymore. Please reopen in case I missed something.",1413758059,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+nageh: Form a client-side perspective this approach is perfectly fine. However, after discussions wiht Gabriel, I'm convinced that there are good (technical) reasons that tag extension should be functionally dependend from their input and not from their context.
+On the other hand this means that the math extension can not decide if the input was :<math or just <math because the : context is hidden.
+The only workable solution is to add an aditional parameter to the math tag.",1396866864,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"(In reply to nageh from comment #27)
+> See, this is what sets me up. ""It's a heuristic written specifically for
+> MediaWiki's math extension."" Bullshit! The heuristic was written
+> specifically for my mathJax user script to cleverly tell apart inline math
+> (where indices of large operators are ordered horizontally) from display
+> math (where indices are stacked). This was actually all explained in bug
+> 35188. And display math has always been left-aligned with my script.
+
+Nageh: I'm not sure what is your intention, but your complaints do not sound very constructive. The comment you state seems to be from Peter Krautzberger so you should ask him directly. But in my opinion, he is just saying that this heuristic is not part of the MathJax code and didn't mean to accuse you of anything. Honestly, I really don't understand why you are getting nervous for that.",1396865303,PHID-USER-5oxfu3gkolxxzkcx3e5n,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**mal.malego** wrote:
+
+See, this is what sets me up. ""It's a heuristic written specifically for MediaWiki's math extension."" Bullshit! The heuristic was written specifically for my mathJax user script to cleverly tell apart inline math (where indices of large operators are ordered horizontally) from display math (where indices are stacked). This was actually all explained in bug 35188. And display math has always been left-aligned with my script.",1396863634,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Change 119010 merged by TheDJ:
+Fix MathJax centers equations
+
+https://gerrit.wikimedia.org/r/119010",1396822113,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Just to add a further complication. 
+
+Bug 37938 is about support for definition lists in VE. As you all know Wikitext plays fast and loose with these transforming : into <dd>. VE being pretty strict with its html does not play nicely with these. I recently found a tricky bug where its difficult to add text after a maths equation 
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_2#Trying_to_add_a_line_after_an_equation
+
+Quite what VE's long term plan for using : as indentation I'm not quite so sure on. 
+
+As to ""heuristic is unwanted by the community"". I think this refers to poll at
+https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Mathematics#Should_display_equations_be_centered.3F
+which was closed at ""Consensus is overwhelmingly in favour of left alignment."". The heuristic was mentioned a little in the discussion. I don't think many really understood what heuristic was about so we can't really conclude what the community  thinks of the idea.",1396821057,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"So to be more accurate, I believe the real issue is that the heuristic forced MathJax's ""display mode"". But because this ""display mode"" does not exist (yet) in MediaWiki, Nageh added this displayAlign: ""left"" config to get MediaWiki's default mode.
+
+Moritz's plan was to generalize the math modes to have, inline/display (the classical modes line in MathJax, TeX, MathML etc) and ""inline displaystyle"" (MediaWiki's default). In his branch, the displayAlign: ""left"" was removed because the display and centering/displaystyle stuff is done elsewhere in MediaWiki. However, because it was hard to get review, he only merged changes step-by-step and unfortunately displayAlign: ""left"" was removed before the whole math modes are ready... So actually the only thing necessary for 119010 was to keep this heuristic and add this config option back.
+
+But as Moritz said on the entry, he is willing to make progress on the new modes and get his work merged, not only to fix bugs. Hopefully, we will recover the desired rendering soon.",1396813759,PHID-USER-5oxfu3gkolxxzkcx3e5n,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"(In reply to nageh from comment #22)
+> And I still don't understand why the ""heuristic is unwanted by the
+> community"" according to the comment in the source file. I thought this was
+> only about that display equations should be left-aligned (which they always
+> were in my code)?
+
+At some point some changes caused the heuristic to force the equation to be centered (probably because we removed displayAlign: ""left"" too early in the development) so that's probably what Moritz meant by ""unwanted by the community"". I think you should not pay too much attention to this comment (actually I believe it should be removed, it's not really useful to have it). The plan to add an explicit display attribute is exactly to avoid this kind of unexpected behaviors and inconsistencies between MathJax/mathoid/LaTeXML/texvc...",1396812806,PHID-USER-5oxfu3gkolxxzkcx3e5n,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**mal.malego** wrote:
+
+And I still don't understand why the ""heuristic is unwanted by the community"" according to the comment in the source file. I thought this was only about that display equations should be left-aligned (which they always were in my code)?",1396811845,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**mal.malego** wrote:
+
+Ha. I do get a bit sensible when I see things being discussed that have long been addressed in my code as if I hadn't done any work on it at all, and when I see comments in the git repository that seem to imply that problems were due to bugs in my code.
+As far as Moritz's efforts are concerned, I'm not exactly familiar with his works but I wish him well and encourage him.
+Peace out.",1396811301,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"(In reply to nageh from comment #19)
+> So far I have ignored all these bug reports, and it seems for good. It is
+> funny how much I am blamed here for all these bugs while clearly my code has
+> had it right from the very start. The heuristic is not about selecting
+> centered or left-aligned maths, it is about deciding the way big operators
+> are rendered. From the very first day my script had included as part of the
+> MathJax config environment
+> displayAlign: ""left""
+> It seems that all my work was in vain, as if it hadn't existed at all. Sigh,
+> I shall not read any of these comments.
+
+I'm not sure where you see that you are blamed. I think everybody recognize your efforts with client-side MathJax on MediaWiki. But if the MathJax option has never been enabled by default, there are good reasons (e.g. performance just to mention one of them). So Moritz has done an awesome work to implement server-side conversion, improves the texvc situation and more. Unfortunately, this is a big and complicate change and review has been slow. The goal is to have the traditional inline mode / display mode that we find in math documents and the default/current MediaWiki rendering ""inline displaystyle"". This handles whether the equation is centered or not and whether the displaystyle is used or not. Moritz has done several versions and branches to try to get the patch accepted and things may have been broken in the battle. Again, I don't think anyone blamed you. I'm sorry to see that you take that personally, instead of encouraging Moritz (and others)'s effort.",1396806384,PHID-USER-5oxfu3gkolxxzkcx3e5n,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**mal.malego** wrote:
+
+So far I have ignored all these bug reports, and it seems for good. It is funny how much I am blamed here for all these bugs while clearly my code has had it right from the very start. The heuristic is not about selecting centered or left-aligned maths, it is about deciding the way big operators are rendered. From the very first day my script had included as part of the MathJax config environment
+displayAlign: ""left""
+It seems that all my work was in vain, as if it hadn't existed at all. Sigh, I shall not read any of these comments.",1396805256,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+https://gerrit.wikimedia.org/r/119010 should fix the problem
+now someone has to do the code review.",1395043650,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Change 119010 had a related patch set uploaded by Physikerwelt:
+Fix MathJax centers equations
+
+https://gerrit.wikimedia.org/r/119010",1395040749,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+For me it looks as I could simply merge my patch that I have already implemented.
+However, I'd like to wait until https://bugzilla.wikimedia.org/show_bug.cgi?id=61006 is merged. Just to be sure, that noting breaks.",1393273493,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Hello,
+
+Thank you for all the work. I just want to say the consensus in the math editor community is to stop centering the equations. So, if possible, you can start fixing this bug.",1392986980,PHID-USER-kwqizcclqreml2x67det,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"Just seen there is a related thread on the MathJax mailing list
+  https://groups.google.com/forum/#!topic/mathjax-users/JwE_lr-HtpQ
+Looks like there is a 
+  displayAlign: ""center""
+parameter you can set in the hub see
+  http://docs.mathjax.org/en/latest/options/hub.html
+Things get a bit tricky if we want to allow both left aligned and center aligned equations.",1392363350,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"@physikerwelt why don't you just disable the heuristic? Or as a compromise, instead of making the equation display-style, make it inline but add \displaystyle to it to get display-style layout. 
+
+Whatever comes out of the RFC could inform Math 2.0 for how to implement real display math.",1392326777,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+Are there special system stylesheets that are loaded that do not belong to the default mediawiki schema?",1392228700,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+Hi Richard Morris,
+
+I'm trying to reproduce it the well defined Vagrant development environment as described here. That I set up as described here.
+http://www.formulasearchengine.com/sites/formulasearchengine.com/files/How%20to%20review%20the%20math%20extension_0.pdf
+
+Did anyone manage to reproduce the problem with vagrant?
+It would be very interesting how the production environment differs from vagrant with regard to MathJax. I was thinking that the problem might be related to my browser cache... but I can see the problem at enwiki
+Best
+Physikerwelt",1392146813,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"DOn't know if this helps but a simple example using the MathJax content delivery network creates centered equations.
+
+<html><head>
+<script type=""text/javascript""
+  src=""http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"">
+</script>
+
+<script type=""text/javascript"">
+	MathJax.Hub.Config({
+		jax : [ ""input/TeX"", ""output/HTML-CSS"" ],
+		extensions : [ ""tex2jax.js"" ],
+		""HTML-CSS"" : {
+			scale : 150
+		},
+		tex2jax : {
+			inlineMath : [ [ '$', '$' ], [ '\\(', '\\)' ] ]
+		}
+	});
+</script>
+</head>
+<body>
+<dl>
+<dt>
+$$1 + 2 + 3 + \dots = -{1 \over 12}.$$
+</dt>
+</dl>
+</body>
+</html>
+
+The bit which sets up the centering is in
+https://github.com/mathjax/MathJax/blob/master/jax/output/HTML-CSS/config.js",1392146433,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+mh... bad news. I can not reproduce the problem locally.
+If I copy the example 
+""I use MathJax, so my view may not be typical, but there could be a problem here.
+:<math>a R b \and b R c \rightarrow a R c</math>
+Yep, it's a problem here, also.""
+from the page I get
+""<dl>
+<dd><span class=""MathJax_Preview""></span><span style="""" aria-readonly=""true"" role=""textbox"" id=""MathJax-Element-1-Frame"" ...""
+even though I was using action=purge&debug=true",1392139735,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+oups... I don't like that workaround at all.
+I think I'll force mathjax to render everything on the left side for now.",1392138483,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"An alternative temporary workaround would be to add the CSS rule somewhere in the global site wide CSS or a users common.css
+
+.MathJax_Display { text-align : left !important; } 
+
+this would align all display equations to the left without having to change any wikitext. This would eliminate the problems in comment 6 but does require a friendly admin.",1392138289,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**anmichvon-wikipedia** wrote:
+
+One possible workarround is appending &nbsp; behind the equitation.
+
+:<math>...</math> &nbsp; <!-- hard blank works around bug 61051 -->
+
+But who removes the garbage, when 61051 is fixed? 
+
+So what about a template that just delivers the hard space and can be cleanly deployed and removed by bots?
+
+:<math>...</math> {{Bugfix-61051|Don't touch, will be removed automatically if and when...}}
+
+Possible Contras:
+* Deployment by bot would produce many instances that could affect the servers load. 
+* Bug will be fixed in short time, so don't mess around that much. It just isn't worth the effort.
+* Might collide with other bot jobs involved in the migration from version 1.1 to version 2.0.
+
+Pros:
+* Workable plan to resolve the situation. 
+* No garbage left over after jobs are done, if properly in concert with other operations of the migration.
+
+User:Pyrometer (Home-Wiki: de.wikipedia.org)",1392133652,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"I've just open an RFC on the question of should display equations to be centered? As this affects multiple wiki's is is open to users from all projects.
+
+https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Mathematics#Should_display_equations_be_centered.3F",1392129744,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+Of course I would really get some feedback about this problem from the community...
+Chaning the code is easy... but getting feedback or codereview is realy hard.",1392056849,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"**physik** wrote:
+
+No Math 2.0 will have a selector to switch the style. 
+
+Currently the situation is as follows:
+The PNG mode creates a new latex document for each equation and puts $$ followed by the secured user input followed by $$ into the document body. The resulting dvi image is cropped to that the equation that was rendered centered on a page generated by latex is no longer centered. So it's not centered displaystyle.
+
+The default for Math2.0 intends to keep this layout, but also offers to alternatives ""displaystyle"" which centers equations and ""inline"" which uses the inline mode (so the layout fit's into the text).
+
+To convert the old math elements one could write a bot that transforms 
+:<math> to math elements with the displaystyle property.
+Another bot could search for html math and convert it back to math tags.
+
+I would prefer to keep that two phase approach.
+If this option is merged mathjax will behave like all other rendering modes.
+(Frédéric an me tested that.)
+
+So the centered equation in MathJax are a bug in the middle of changing from version 1.1 to version 2.0",1392056796,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,"This is caused by a custom MathJax extension used in the MediaWiki Math Extension, wiki2jax, https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FMath/ff83048597fb256c2579f16ddcd982ef2ae75460/modules%2FMathJax%2Funpacked%2Fextensions%2Fwiki2jax.js. That custom extension contains a simple heuristic (part of the ConvertMath function) to identify display style equations.
+
+> Aligning equations to the left is the desirable format.
+
+IIUC that's simply due to the :<math>...</math> hack which the community adopted because the math extension lacks support for display style -- see  https://bugzilla.wikimedia.org/show_bug.cgi?id=12223. Traditionally, display-style math layout is centered.
+
+I think you opened a discussion about community preference on the WikiProject Math page, too. So perhaps it's best to wait until there's a more definitive response. 
+
+Physikerwelt will correct me, but once Math extension 2.0 is ready, the heuristic would also apply to the default image rendering.
+
+Peter.",1392055423,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+MathJax equations are centered,*** Bug 61139 has been marked as a duplicate of this bug. ***,1392043804,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-lutd3sk7dfkqcmljv7ob,task_subcomment,NA
+Ve preview header bar doesn't make sense,"What am I previewing?!
+
+In story 1625 we removed preview from VisualEditor but we left the header in place.
+https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1625
+
+This looks strange as demonstrated by attachment as nothing as being previewed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13434}",1391800260,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-3z36ic6aws767el6smak,task_description,resolved
+Ve preview header bar doesn't make sense,"Change 115550 merged by jenkins-bot:
+Change header message when saving in VE
+
+https://gerrit.wikimedia.org/r/115550",1393455887,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z36ic6aws767el6smak,task_subcomment,NA
+Ve preview header bar doesn't make sense,"Change 115550 had a related patch set uploaded by JGonera:
+Change header message when saving in VE
+
+https://gerrit.wikimedia.org/r/115550",1393374918,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z36ic6aws767el6smak,task_subcomment,NA
+Ve preview header bar doesn't make sense,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1677",1391800526,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3z36ic6aws767el6smak,task_subcomment,NA
+VisualEditor: Table of Contents is not appearing properly in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add Sub-heading 1 to sub-heading 4 
+3.Save the page
+4.Observe the table of contents
+
+Observed Result:
+The table of content is appearing without any style and  order
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan28thff
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13292}",1391722200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gokdl4kwqlwt6cmm66eh,task_description,invalid
+VisualEditor: Table of Contents is not appearing properly in Betalabs,This is due to the Typography refresh Beta Feature.,1394502330,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gokdl4kwqlwt6cmm66eh,task_subcomment,NA
+"VisualEditor: TypeError: OO.ui.IconButtonWidget is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE","Screenshot
+
+TypeError: OO.ui.IconButtonWidget  is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE
+
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13263}",1391716320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5qn7fz4uqtu624ogpnuh,task_description,declined
+"VisualEditor: TypeError: OO.ui.IconButtonWidget is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE",Think this was a deployment issue.,1396380412,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5qn7fz4uqtu624ogpnuh,task_subcomment,NA
+"VisualEditor: TypeError: OO.ui.IconButtonWidget is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE","Also, on load appearing TypeError: this.toolbarSaveButton is null",1391716534,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5qn7fz4uqtu624ogpnuh,task_subcomment,NA
+"VisualEditor: TypeError: OO.ui.IconButtonWidget is not a constructor appears in production and ""Save Page"" and ""Cancel"" button is not appearing inside VE","This is happening in FireFox.In Chrome, it is working fine.",1391716428,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5qn7fz4uqtu624ogpnuh,task_subcomment,NA
+VisualEditor: No vertical scrollbar on insert media (Firefox),"Intention:
+Insert media file in article using Firefox
+
+Steps to Reproduce:
+0. Open up Firefox
+1. Go to https://sv.wikipedia.org/wiki/Foo?veaction=edit&uselang=en
+2. Click Insert -> Media
+3. Write ""Foo"" in search window
+4. Select image
+5. Click Insert -> Media again
+
+Actual Results:  
+After 3: Image search returns 5*3 images
+After 5: Image search returns more images accessible using the vertical scrollbar
+
+Expected Results:  
+After 3: Image search returns more images accessible using the vertical scrollbar
+
+Reproducible: Didn't try
+
+This problem becomes more severe since beginners don't realise that there are ever more than 15 possible images, meaning they can usually not find an image they previously identified on Commons.
+
+Works fine in Chrome though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391702640,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-l56rigwmq6kptg33obmi,task_description,resolved
+VisualEditor: No vertical scrollbar on insert media (Firefox),"I can no longer reproduce it so seems fixed (in Firefox or on our side).
+
+I'll close it as fixed.",1404208489,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-l56rigwmq6kptg33obmi,task_subcomment,NA
+VisualEditor: No vertical scrollbar on insert media (Firefox),"This may have been fixed.  I can't reproduce this in Firefox 30.  The first search on a random article produced more images than fit on the screen, and I could get to them with the scrollbar.",1404169558,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-l56rigwmq6kptg33obmi,task_subcomment,NA
+VisualEditor: No vertical scrollbar on insert media (Firefox),"(In reply to comment #0)
+> 
+> Reproducible: Didn't try
+> 
+Missed this on filing bug. Definitely reproducible.
+
+On a side note I'm running Firefox 26.0",1391702895,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-l56rigwmq6kptg33obmi,task_subcomment,NA
+VisualEditor: No vertical scrollbar on insert media (Firefox),"Created attachment 14509
+Screencast
+
+**Attached**: {F13230}",1391702752,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-l56rigwmq6kptg33obmi,task_subcomment,NA
+"VisualEditor: The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs","In the VE mode
+
+Steps to reproduce:
+
+1.Open the page with VE
+2.Insert a reference for a text
+3.Add the same reference again somewhere in the page
+4.Add the reflist
+5.Save the page
+
+Observed Result:
+ The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Ehat
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13133}",1391649480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gxelvauhc4ymdd6gw2ss,task_description,resolved
+"VisualEditor: The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs","This is because the Parsoid (re)implementation of Cite doesn't support the customisation of the i18n message currently – merging with that issue.
+
+*** This bug has been marked as a duplicate of bug 43235 ***",1391659693,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gxelvauhc4ymdd6gw2ss,task_subcomment,NA
+"VisualEditor: The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs","Created attachment 14500
+In the read mode
+
+**Attached**: {F13134}",1391649617,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gxelvauhc4ymdd6gw2ss,task_subcomment,NA
+Page creation in alpha with VE wonky if you tap outside of the editable area,"In alpha, navigate to a non-existent page. You should see the text 'This page doesn't exist. Why not be bold and create it?'. Tap on the pencil edit icon. A cursor should show up in the editable area. Tapping outside of the editable area makes the cursor go away. Knowing where to tap in order to get the cursor back is a bit of a mystery. Perhaps we should make the tappable area for this visible to users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391640660,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-yt7hoiqatg2twcdmiujq,task_description,declined
+Page creation in alpha with VE wonky if you tap outside of the editable area,Eh I must've been using an outdated version; I just tested again to take some screenshots and the editable area now appears very obvious. Closing as WFM.,1391728851,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-yt7hoiqatg2twcdmiujq,task_subcomment,NA
+Page creation in alpha with VE wonky if you tap outside of the editable area,"Arthur not sure I follow. Can you provide some screenshots (sadly VE is broken everywhere for me to test)?
+Are you asking for placeholder text?
+Does this differ from VisualEditor desktop experience?",1391716653,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-yt7hoiqatg2twcdmiujq,task_subcomment,NA
+Page creation in alpha with VE wonky if you tap outside of the editable area,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1673",1391640921,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yt7hoiqatg2twcdmiujq,task_subcomment,NA
+VisualEditor: Don't insert a new gallery if the user doesn't enter any contents for it,"Steps to Reproduce:
+1. Open the gallery inserter tool.
+2. Don't add any content.
+3. Discover that no matter what you do from here, it's going to add a pair of gallery tags that is difficult to select (for removal) in VisualEditor and pointless on the page.
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1391634600,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zs5e5bzcmcr4rtwmlnui,task_description,resolved
+VisualEditor: Don't insert a new gallery if the user doesn't enter any contents for it,"This was fixed a few weeks ago (though if you insert "" "" it will insert, but… there's no defeating a user intentionally breaking things).",1394677396,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zs5e5bzcmcr4rtwmlnui,task_subcomment,NA
+VisualEditor:  You should be able to cancel a gallery without adding it,"Steps to Reproduce:
+1. Click on Insert > Gallery
+2. Think ""Oops, I meant to click on Transclusion"".
+3. Try to get out of there without having a gallery added to your page.
+
+Actual Results:  
+Click the < button:  it adds a nearly invisible empty gallery.  Press the ESCape key:  it adds a nearly inisible empty gallery.  Click elsewhere:  it adds a nearly invisible empty gallery.
+
+Expected Results:  
+I expected a trash can, but I'd prefer an X of the universal ""click here to cancel"" variety.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391634360,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-62gwo3nopvq6bsrwmth7,task_description,resolved
+VisualEditor:  You should be able to cancel a gallery without adding it,"(In reply to comment #1)
+> This should probably be merged with Bug 60779.
+
+Done (and fixed, yay).
+
+*** This bug has been marked as a duplicate of bug 60779 ***",1391668703,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-62gwo3nopvq6bsrwmth7,task_subcomment,NA
+VisualEditor:  You should be able to cancel a gallery without adding it,This should probably be merged with Bug 60779.,1391634760,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-62gwo3nopvq6bsrwmth7,task_subcomment,NA
+Enabling visualeditor does not result in usable visualeditor,"Steps to reproduce:
+
+#1 $ vagrant enable-role visualeditor
+Ok. Run 'vagrant provision' to apply your changes.
+
+
+
+#2 $ vagrant list-roles
+Available roles:
+
+  analytics
+  antispam
+  apisandbox
+  betafeatures
+  browsertests
+  chromium
+  cirrussearch
+  cldr
+  codeeditor
+  commonsmetadata
+  echo
+  education
+  eventlogging
+  fundraising
+  gadgets
+  geodata
+  geshi
+  gettingstarted
+  guidedtour
+  hadoop
+  hhvm
+  hive
+  massmessage
+  math
+  mathsearch
+  mleb
+  mobilefrontend
+  multimedia
+  multimediaviewer
+  navigationtiming
+  oauth
+  parserfunctions
+  pdfhandler
+  proofreadpage
+  remote_debug
+  scribunto
+  timedmediahandler
+  uploadwizard
+* visualeditor
+  wikieditor
+  wikimetrics
+  xhprof
+
+Roles marked with '*' are enabled.
+Use ""vagrant enable-role"" & ""vagrant disable-role"" to customize.
+
+
+
+#3 $ vagrant provision
+[default] Running provisioner: puppet...
+Running Puppet with site.pp...
+info: Applying configuration version '1391614793.16f99ad'
+info: mount[files]: allowing mediawiki-vagrant access
+notice: /Stage[main]/Mediawiki::Parsoid/Package[nodejs]/ensure: ensure changed 'purged' to '0.8.2-1chl1~precise1'
+notice: /Stage[main]/Mediawiki::Parsoid/File[/etc/init/parsoid.conf]/ensure: created
+notice: /Stage[main]/Mediawiki::Parsoid/Git::Clone[mediawiki/services/parsoid/deploy]/Exec[git clone mediawiki/services/parsoid/deploy]/returns: executed successfully
+notice: /Stage[main]/Mediawiki::Parsoid/File[localsettings.js]/ensure: defined content as '{md5}11ba3cfc1124f11f4a507a56cc70d34c'
+info: /Stage[main]/Mediawiki::Parsoid/File[localsettings.js]: Scheduling refresh of Service[parsoid]
+notice: /Stage[main]/Mediawiki::Parsoid/Service[parsoid]/ensure: ensure changed 'stopped' to 'running'
+notice: /Stage[main]/Mediawiki::Parsoid/Service[parsoid]: Triggered 'refresh' from 1 events
+notice: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Git::Clone[mediawiki/extensions/VisualEditor]/Exec[git clone mediawiki/extensions/VisualEditor]/returns: executed successfully
+notice: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Mediawiki::Settings[VisualEditor]/File[/vagrant/settings.d/puppet-managed/10-VisualEditor.php]/ensure: created
+notice: Finished catalog run in 587.81 seconds
+
+
+
+#4 Go to http://127.0.0.1:8080/wiki/Main_Page
+
+
+
+#5 Error page is displayed:
+
+MediaWiki 1.23wmf2 required--this is only 1.22alpha
+
+Backtrace:
+
+#0 /vagrant/mediawiki/extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW('1.23wmf2')
+#1 [internal function]: VisualEditorHooks::onSetup()
+#2 /vagrant/mediawiki/includes/Setup.php(569): call_user_func('VisualEditorHoo...')
+#3 /vagrant/mediawiki/includes/WebStart.php(161): require_once('/vagrant/mediaw...')
+#4 /vagrant/mediawiki/index.php(55): require('/vagrant/mediaw...')
+#5 {main}
+
+
+
+#6 Looks like mediawiki-vagrant uses an old version of mediawiki (1.22alpha) and visualeditor needs version 1.23wmf2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391618640,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-usrosfs2iqiakawkjchy,task_description,declined
+Enabling visualeditor does not result in usable visualeditor,I am not sure what I did wrong the last time. I have tried again with a clean VM and visual editor works just fine.,1391693357,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-usrosfs2iqiakawkjchy,task_subcomment,NA
+Enabling visualeditor does not result in usable visualeditor,There's also a 'vagrant git-update' command now that attempts to pull all latest changes to git repos.,1391638634,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-usrosfs2iqiakawkjchy,task_subcomment,NA
+Enabling visualeditor does not result in usable visualeditor,"Thanks, I got the same advice from James_F at #wikimedia-qa. The strange thing is that I have created the vagrant vm today. Shouldn't it have the lates core then?",1391619389,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-usrosfs2iqiakawkjchy,task_subcomment,NA
+Enabling visualeditor does not result in usable visualeditor,MediaWiki-Vagrant git-clones MediaWiki core the first time you provision it and leaves it for you to manage thereafter. You can go to the mediawiki/ subdirectory and run 'git pull' to get the latest.,1391618719,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-usrosfs2iqiakawkjchy,task_subcomment,NA
+VisualEditor: template and link inspectors not working for some users at it.wp,"Might need to split this later, and/or add more details, here's what we know now from it.wp users.
+
+Not logged in user, Firefox 26.0, Windows 7 reports the following.
+*When you try to edit a template, the template inspector will look empty.
+*When you try to add a new template, the inspector won't provide any suggestions for existing ones.
+*When you try to choose an option from the 3-bars menu on the right, none will work (nothing will happen clicking on those), except for the ""Switch to wikitext"" one.
+
+User:Nnvu, Chrome ver. 32.0.1700.102 m, Windows 8.1, Vector reports having the same issues, plus:
+*When you click on a wikilink anywhere in the page, instead than getting the box to edit it, you'll be directed to the linked page (the page will even ask you if you're sure you wanna leave).
+*When you save the page, it will stay in edit mode. If you click Save again, you'll get both the save dialog and the loading bar that keeps going. (The page results correctly saved from the history, nonetheless.) 
+
+Nnvu could check the console once, and said that this message
+*event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
+appeared once the editing page was loaded, while
+*Uncaught TypeError: Object #<Object> has no method 'apiRequest' VM189:567
+is what he got while trying to type inside the template inspector.
+
+VE will work fine for him:
+*if he logs out (but while when he's logged-in, disabling all BetaFeatures, all the gadgets and even blanking .js pages won't still help);
+*if he uses FF, as a logged-in user.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391612040,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-cp3g7luvxfst4ptkx7me,task_description,declined
+VisualEditor: template and link inspectors not working for some users at it.wp,This may have been due to some faulty cached code – we saw a similar issue during the aborted deployment of wmf12 to Wikipedias yesterday.,1391794669,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cp3g7luvxfst4ptkx7me,task_subcomment,NA
+VisualEditor: template and link inspectors not working for some users at it.wp,Apparently everything is back to normal now.,1391793651,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-cp3g7luvxfst4ptkx7me,task_subcomment,NA
+VisualEditor: template and link inspectors not working for some users at it.wp,"I can't reproduce any of this, and other users can't as well.",1391612515,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-cp3g7luvxfst4ptkx7me,task_subcomment,NA
+VisualEditor: Math Inspector icon and Link inspector icon appears together on a Math formula which has link applied on it,"Two inspector icon together over the math function
+
+Steps to produce:
+
+
+1.Open the page with VE
+2.Add a Math function such as \pi
+3.Now add a text before that such as life of pi
+4.Now select the text and the math function together
+5.Apply link on it
+6.Now select the Math function
+
+Observed Result:
+The Math inspector icon and the link inspector icon opens together over the math function.
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Test2chrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56644
+
+**Attached**: {F12944}",1391552880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-25boqjke4cijtwjgyjbt,task_description,invalid
+VisualEditor: Math Inspector icon and Link inspector icon appears together on a Math formula which has link applied on it,This is expected behaviour.,1399047303,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-25boqjke4cijtwjgyjbt,task_subcomment,NA
+VisualEditor: Blanking a page doesn't remove protection templates,"Similar to bug 52036.
+When you blank a page with VE, protection templates like
+https://en.wikipedia.org/wiki/Template:Pp-move-indef
+or
+https://en.wikipedia.org/wiki/Template:Pp-blp
+will stay.
+
+https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=593889831
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52036",1391525700,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-b2icu3jhk57jo4lbtgez,task_description,resolved
+VisualEditor: Blanking a page doesn't remove protection templates,"
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1393271673,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b2icu3jhk57jo4lbtgez,task_subcomment,NA
+VisualEditor: Blanking a page doesn't remove protection templates,"Also categories, interwikis, maybe other stuff that's not editable in the main editor. This sounds like the expected behavior to me.",1391525908,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-b2icu3jhk57jo4lbtgez,task_subcomment,NA
+VisualEditor: Math Formula appears (However does not get placed) inside gallery while opening Latex over gallery,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a gallery
+3.Select the gallery
+4.Open a Math Formula window.
+5.Type something on the editor
+
+Observed Result:
+The math function appears inside gallery .However, if you close the math inspector it will place the math function properly after the gallery not inside it.
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12825}",1391474580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6krx2nyb5rqgwoao3nrw,task_description,resolved
+VisualEditor: Math Formula appears (However does not get placed) inside gallery while opening Latex over gallery,"
+
+*** This bug has been marked as a duplicate of bug 56644 ***",1397757894,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6krx2nyb5rqgwoao3nrw,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**Author:** `jhall`
+
+**Description:**
+Per a request from James Forrester, we should create a new browser test(s) in the VisualEditor repo that will verify the availability of VisualEditor on production wikis in two categories:
+
+1) Test whether VE loads if invoked on each of the currently ~300 wikis that VisualEditor is deployed to.  This is just checking that ?veaction=edit causes a VE surface to load.
+
+2) Test whether VE's edit tab appears on the ~150 wikis to which is is deployed to as default for all users.  This is checking that the tab for VisualEditor loads for logged-out users.
+
+Some caveats regarding this new test:
+
+1)  The test should not perform any writing actions to the wiki (just loading, no saving).
+
+2) We're probably only looking for a quick verification every week or so, rather than 
+​every 12 hours (as with the existing schedule for other VE browser tests).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60842",1391469180,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_description,resolved
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+Yep, this one is resolved. Job is up-and-running via CloudBees:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-production.wikimedia.org/",1392395125,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Jeff, is this resolved?",1392377851,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Change 112809 merged by jenkins-bot:
+[Browser test] Update list of prod wikis to be verified.
+
+https://gerrit.wikimedia.org/r/112809",1392157240,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Change 112809 had a related patch set uploaded by Jhall:
+[Browser test] Update list of prod wikis to be verified.
+
+https://gerrit.wikimedia.org/r/112809",1392153700,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+CloudBees/Jenkins job for this task is[1]
+
+[1] https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-production.wikimedia.org/",1392089646,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Change 111142 merged by jenkins-bot:
+[Browser test] VisualEditor availability on prod wikis
+
+https://gerrit.wikimedia.org/r/111142",1392061254,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+Re-opening since this is still work-in-progress.",1391536657,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+Setting status back to RESOLVED since I'm not quite done with this just yet...",1391479193,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"Change 111142 had a related patch set uploaded by Jhall:
+[Browser test] WIP Test VisualEditor availability on production wikis
+
+https://gerrit.wikimedia.org/r/111142",1391479139,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Browser test for VisualEditor availability on production wikis,"**jhall** wrote:
+
+From James: ""The list of 300 wikis is[1] – though that contains at the bottom 4 private wikis that shouldn't be tested.""
+
+[1] http://noc.wikimedia.org/conf/highlight.php?file=visualeditor.dblist",1391473888,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-323aluzrs2vl2d7v27bc,task_subcomment,NA
+Flow: archive search in page header triggers error,"screenshot of error
+
+If I have {{archives}} or {{Talk header}} in the page header area, Flow gives this error (screenshot):
+
+The error message received was: Exception Caught: ID searchbox already defined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60816
+
+**Attached**: {F13408}",1391463960,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-m2mjxjfupqonuuet4g5a,task_description,resolved
+Flow: archive search in page header triggers error,"Change 111224 merged by jenkins-bot:
+Don't error out on duplicate id's
+
+https://gerrit.wikimedia.org/r/111224",1391640389,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,"I think the ""id=searchbox"" is coming from https://www.mediawiki.org/wiki/Extension:InputBox and there are frequently more than one searchbox per page so that does need to be solved.
+
+aha! bug 11777 (Multiple inputboxes make page invalid due to repetitive similar id) I don't know if that bug needs to be poked, with this fresh example? It's been silent since Sept 2012.",1391570033,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,"Change 111224 had a related patch set uploaded by EBernhardson:
+Don't error out on duplicate id's
+
+https://gerrit.wikimedia.org/r/111224",1391537515,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,*** Bug 60816 has been marked as a duplicate of this bug. ***,1391537507,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,"Parsoid is being strict about disallowing the duplicate element IDs in HTML (bug 60816).
+
+But these templates should not be causing invalid HTML output by specifying id=searchbox twice.  Somewhere besides {{archives |search=yes}} there must be another id=searchbox; I tried adding the template wikitext to [[wp:Wikipedia_talk:Flow/Developer_test_page]] but couldn't reproduce it. Assuming that's the problem these templates should use a unique ID, maybe we can alert their authors. Any special styling or behavior they're getting should be due to classes, not an ID.
+
+For grins, you could try to add the problematic templates in VisualEditor.",1391499416,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+Flow: archive search in page header triggers error,"Created attachment 14474
+screenshot 2
+
+After reading the error in the preview (screenshot 1), I removed the {{archives}} box, and hit save. That resulted in this: (screenshot 2)
+
+So I re-edited the header to remove {{Talk header}}. Once I hit save for that, it was still displaying the same error, until I did shift-F5 (hard-refresh).
+
+**Attached**: {F13410}",1391496922,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-m2mjxjfupqonuuet4g5a,task_subcomment,NA
+VisualEditor: The Strikethrough and Underline gets overlapped for a superscript text,"screenshot
+
+Steps to reproduce:
+
+1.Open a page with Ve
+2.Select a text
+3.Apply Superscript
+4.Apply Strikethrough
+5.Apply Underline
+6.Unselect superscript  
+7.Make it superscript again (Observe that strikethrough is now below the text, this is one issue)
+8.Unselect Underline
+9.Make it underline again
+
+Observed Result
+The Strikethrough and Underline gets overlapped for a superscript text
+
+**This is a FireFox only bug.Works perfectly on Chrome**
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13396}",1391459760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lac4g5g62zrekkfygvxx,task_description,invalid
+VisualEditor: The Strikethrough and Underline gets overlapped for a superscript text,I don't believe this is anything other than Firefox being difficult…,1402294906,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lac4g5g62zrekkfygvxx,task_subcomment,NA
+"VisualEditor:  The special character inserter tool should use the full width of the toolbar, rather than a narrow floating box","The floating palette for the special character tool is annoyingly out of reach if your cursor is at the bottom of your screen.  You have to scroll down (sometimes a lot) to reach the character that you want.  It's also narrow, which limits the number of characters that can be seen at once.
+
+It should be replaced with a fixed, full-width tool that is attached to the main toolbar.  This allows more characters to be displayed at once and is always visible, no matter where you are typing.
+
+This might also be convenient way to address the problems in bug 60657.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391448240,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yurtnajxpg7fxltytwpi,task_description,resolved
+"VisualEditor:  The special character inserter tool should use the full width of the toolbar, rather than a narrow floating box","Fixed by the ""Special Characters"" insertion redesign (can be tested already on http://en.wikipedia.beta.wmflabs.org )",1425547616,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-yurtnajxpg7fxltytwpi,task_subcomment,NA
+"VisualEditor:  The special character inserter tool should use the full width of the toolbar, rather than a narrow floating box","> The floating palette for the special character tool is annoyingly out of reach if your cursor is at the bottom of your screen. You have to scroll down (sometimes a lot) to reach the character that you want.
+
+@Whatamidoing-WMF: Is this still valid?
+Being at the very bottom in Firefox 36 with my cursor, trying to insert a special character the view scrolls automatically down. See screenshot:
+
+{F55250}",1425508610,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-yurtnajxpg7fxltytwpi,task_subcomment,NA
+"VisualEditor:  The special character inserter tool should use the full width of the toolbar, rather than a narrow floating box",Is this still valid? What about T78038?,1421888018,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-yurtnajxpg7fxltytwpi,task_subcomment,NA
+parsoidserver-http-bad-status,"http://en.m.wikipedia.beta.wmflabs.org/w/api.php?format=json&action=visualeditor&paction=parse&page=Selenium_Edit_Test
+
+Any idea why this request ends up with the response:
+{""servedby"":""deployment-apache32"",""error"":{""code"":""parsoidserver-http-bad-status"",""info"":""404""}}
+
+It prevents VisualEditor from loading on mobile...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391408100,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-btmvpbqnfpj57y5y72ua,task_description,declined
+parsoidserver-http-bad-status,"I'm closing this bug as worksforme, as the underlying API outage has since been fixed. Bug 58390 tracks the error code issue.",1391651487,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-btmvpbqnfpj57y5y72ua,task_subcomment,NA
+parsoidserver-http-bad-status,"The API issues were probably the internal LVS failure today, caused by a networking configuration error. See Mark's mail titled ""Outage report: LVS outage February 3, 2013"" on the ops list.",1391463920,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-btmvpbqnfpj57y5y72ua,task_subcomment,NA
+parsoidserver-http-bad-status,"This page loads for me: http://parsoid-lb.eqiad.wikimedia.org/itwiki/Utente%3ABaruneju%2Fsandbox2?oldid=63854985
+
+Sometimes issues in the MW API are misreported as 404s on our end, so maybe this was a transient API failure. The misleading error reporting is tracked in bug 58390.",1391455828,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-btmvpbqnfpj57y5y72ua,task_subcomment,NA
+parsoidserver-http-bad-status,"The problem is not limited to the mobile version, it also happens on the Web using both Firefox and Chrome, both Monobook and Vector.
+Example response: (on it.wiki user sandbox, but it also applies to en.wiki NS:0)
+
+{""servedby"":""mw1121"",""error"":{""code"":""parsoidserver-http-timed-out"",""info"":""http://10.2.2.29/itwiki/Utente%3ABaruneju%2Fsandbox2?oldid=63854985""}}",1391427708,PHID-USER-w7kicrzlpwfrteo6zs5p,False,PHID-TASK-btmvpbqnfpj57y5y72ua,task_subcomment,NA
+VisualEditor:The Image resize handler along with the blue highlighted box gets displaced while resizing the window,"Screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE which contains an image
+2.Now select the image
+3.Resize the window (Not the image)
+
+Observed Result:
+
+
+The image resize handle gets displaced
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13198}",1391208840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhochcqzfoj4bimpgiqx,task_description,resolved
+VisualEditor:The Image resize handler along with the blue highlighted box gets displaced while resizing the window,"
+
+*** This bug has been marked as a duplicate of bug 55789 ***",1394128066,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zhochcqzfoj4bimpgiqx,task_subcomment,NA
+VisualEditor - Inserting a gallery while having an image selected breaks the visual editor.,"(Tested on Firefox 26, Windows Vista)
+Steps to reproduce
+- Edit the [[Jefferson Davis County Courthouse (Mississippi)]] page using the visual editor.
+- Click the image present in the article.
+- Press ""Insert => Gallery"".
+
+The result of this is that the visual editor will break to a point where one cannot use it without entirely reloading the page. For example:
+- Pressing ""Insert => Gallery"" again yields no reaction.
+- Pressing ""Insert => Special Character"" results in a window that seems to be a hybrid of the gallery and character insertion tool.
+- Clicking any page link in the article will no longer result in the usual ""Edit Link"" popup. Using the link button on the interface will result in a hybrid version of the link window and the gallery window.
+
+Interestingly, there are no errors in Firefox's error console.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows Vista
+**Platform**: PC",1391204400,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-gtujhqzrxk5hd6l7lxu3,task_description,resolved
+VisualEditor - Inserting a gallery while having an image selected breaks the visual editor.,"(For future reference, please report only one issue per bug report. Thank you!)",1391436396,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gtujhqzrxk5hd6l7lxu3,task_subcomment,NA
+VisualEditor - Inserting a gallery while having an image selected breaks the visual editor.,"
+
+*** This bug has been marked as a duplicate of bug 60502 ***",1391204983,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gtujhqzrxk5hd6l7lxu3,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Screenshot
+
+Steps to reproduce:
+
+
+1.Create a page on Betalabs
+2.Add some content and save it
+3.Reopen the page with VE
+
+Observed Result:
+Content of some article is showing up instead of my own edited content
+
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/31st_january
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13186}",1391200560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_description,resolved
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,Verified the fix on Betalabs.,1391635700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"The puppet agent didn't seem to be running on the parsoid host in beta labs, and after starting that Parsoid was not restarted to reflect the the changes. Fixed that manually, and verified fixed at http://en.wikipedia.beta.wmflabs.org/wiki/0.6884344289426402?veaction=edit.",1391629537,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Change 111350 merged by Alexandros Kosiaris:
+Bug 60694: Make the config file path configurable
+
+https://gerrit.wikimedia.org/r/111350",1391625176,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Change 111350 had a related patch set uploaded by GWicke:
+Bug 60694: Make the config file path configurable
+
+https://gerrit.wikimedia.org/r/111350",1391553175,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,We need this on beta labs at the earliest opportunity.  I raised the importance.,1391546102,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,https://gerrit.wikimedia.org/r/#/c/110666/ creates a Debian package and makes the config file path configurable in /etc/defaults/mediawiki-parsoid. We might still want to fix this in puppet temporarily until we move to deb-based installs.,1391485605,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Another symptom of this is if you add or edit a post to a Flow board on betalabs (e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA ) and transclude a page with {{:Article name }}, it pulls in the page from enwiki.",1391478948,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"On deployment-parsoid2 in /var/log/parsoid/parsoid.log
+
+{ [Error: Cannot find module '/srv/deployment/parsoid/conf/wmf/localsettings.js'] code: 'MODULE_NOT_FOUND' }
+
+There is no conf directory but there is a file /srv/deployment/parsoid/localsettings.js which is described in puppet:
+
+ manifests/role/parsoid.pp:    file { '/srv/deployment/parsoid/localsettings.js':
+
+I introduced it on Jan 2 with https://gerrit.wikimedia.org/r/#/c/104938/
+
+
+The upstart configuration I wrote ( /etc/init/parsoid.conf ) was pointing to it but now points to ../conf/wmf/localsettings.js.
+
+So I guess the easiest path is to use an env variable such as PARSOID_CONF, set it in /etc/default/parsoid and make it vary in the puppet configuration.",1391467271,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"A bit more investigation shows that VE is sending the right oldid.
+
+I think this is caused by Parsoid not finding its config file in the deploy repo. In the production upstart config we are now passing the explicit path to a config file to parsoid, which is checked into conf/wmf/localsettings.js in the deploy repo. Beta labs might still rely on localsettings.js being in src/api, which will no longer work.
+
+I think we'll need to make the config path configurable in the upstart file, and set a different path (ideally conf/wmf-beta or the like) for betalabs.",1391464994,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Note that this could also be VE sending the wrong oldid, as that will always take precedence over the page name.",1391464443,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"This is unlikely to be related to bug 60372, as a) the oldid is sent, and b) it only happened sometimes under high request loads.
+
+This does not happen in production (running Parsoid master right now). I'm suspecting a configuration issue in betalabs.",1391456757,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,It seems to be quite easy to consistently reproduce. Just click 'random article' and then load the VisualEditor. I get the contents of a different article 100% of the time. The really weird thing is that the articles that are being loaded don't seem to even exist on Beta Labs.,1391455995,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,Does beta.wmflabs.org have latest parsoid master? Related is bug 60372 which was fixed in https://gerrit.wikimedia.org/r/#/c/110233/,1391455771,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"I noticed this today at
+http://en.m.wikipedia.beta.wmflabs.org/wiki/0.07511468210381089
+
+Whenever I load VisualEditor, it loads the allergy article instead.",1391455640,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"**jhall** wrote:
+
+I've also been seeing this behavior in beta labs today, although it's been difficult to consistently reproduce.  I've seen it much more frequently with the automated browser tests than I have with manual testing.",1391210840,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead,"Now, Uncaught TypeError: Cannot read property 'status' of null is appearing while trying to open VE in betalabs",1391203540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-timuxvvj3wafz5qt6zh2,task_subcomment,NA
+VisualEditor: Provide the character inserter everywhere that you can input text,"Intention:
+Add special characters
+
+Steps to Reproduce:
+If any of the following that happen to rely on special characters:
+
+* A template
+* A parameter name in said template
+* Data for parameter (e.g., the name of a person or place)
+* A link to another page
+* A category
+* A media item (e.g., image) that you can't find otherwise
+* An image or a caption in a image gallery
+* An edit summary
+
+then they cannot be successfully used in VisualEditor.  Probably there are uses for it in the Mathematics Formulae tool as well.  
+
+Basically, if you have a cursor for typing anything, anywhere in the entire VisualEditor interface, then you need access to the special character inserter.
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391125500,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-vod4bp3xvmjarqf6dtmz,task_description,declined
+VisualEditor: Provide the character inserter everywhere that you can input text,"Is that title better, @Jdforrester-WMF?",1425419652,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-vod4bp3xvmjarqf6dtmz,task_subcomment,NA
+VisualEditor: Provide the character inserter everywhere that you can input text,"I could write it up as a whole series of bugs, if you'd like:  Make it
+possible to access VisualEditor's special character tool when adding a
+template (ie., typing the name of the template).  Make it possible to
+access VisualEditor's special character tool when filling in parameter data
+for templates.  Make it possible to access VisualEditor's special character
+tool when editing citations.  Make it possible to access VisualEditor's
+special character tool when searching for media.  Make it possible to
+access VisualEditor's special character tool when typing a file name or
+caption in a gallery.  Make it possible to access VisualEditor's special
+character tool when writing an edit summary.  Make it possible to access
+VisualEditor's special character tool when adding a category (including a
+redlink category).",1425416797,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-vod4bp3xvmjarqf6dtmz,task_subcomment,NA
+VisualEditor: Provide the character inserter everywhere that you can input text,This isn't a bug. It isn't a task. It isn't asking for anything. It doesn't have an actionable element at all.,1425416329,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vod4bp3xvmjarqf6dtmz,task_subcomment,NA
+"VisualEditor: When followed by a template, the template edit icon is appearing over an image","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Now add an image to the page
+3.Now add a template infobox-country or any other infobox template like infobox-company
+4.Save the page
+5.Open the page again.
+6.Now Select the template 
+
+Observed Result:
+
+The template edit icon is appearing over the image now
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Image_after_template
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13094}",1391122080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bxocvjff7v4vgwjuctgr,task_description,resolved
+"VisualEditor: When followed by a template, the template edit icon is appearing over an image","Think I'm going to merge this with bug 51548.
+
+*** This bug has been marked as a duplicate of bug 51548 ***",1393455560,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bxocvjff7v4vgwjuctgr,task_subcomment,NA
+VisualEditor:General Settings and Advanced Settings button/text field labels are missing on Media Settings widget for test2 and mw.org,"Screenshot
+
+Steps to reproduce:
+
+1.Insert and image 
+2.Go to Media Settings
+
+Observed Result:
+
+General Settings and Advanced Settings button tags are missing on Media Settings widget
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13065}",1391112720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gwypfbeszglyxfdqtuls,task_description,declined
+VisualEditor:General Settings and Advanced Settings button/text field labels are missing on Media Settings widget for test2 and mw.org,All the labels and messages are appearing now in test2 and mediawiki,1391203627,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gwypfbeszglyxfdqtuls,task_subcomment,NA
+VisualEditor:General Settings and Advanced Settings button/text field labels are missing on Media Settings widget for test2 and mw.org,"Created attachment 14420
+Screenshot
+
+**Attached**: {F13066}",1391112912,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gwypfbeszglyxfdqtuls,task_subcomment,NA
+VisualEditor:General Settings and Advanced Settings button/text field labels are missing on Media Settings widget for test2 and mw.org,"Infact all the textbox name and heading of the advanced dialog Settings page is missing
+See the second screenshot",1391112893,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gwypfbeszglyxfdqtuls,task_subcomment,NA
+"VisualEditor: Clicking on Increase/Decrease Indentation button multiple times shows ""Confirm Navigation?"" dialog box on mediawiki.org","Screenshot attached
+
+Steps to reproduce;
+
+
+1.Open a page with VE
+2.Add a bullet list or a numbered list
+3.Keep on pressing the Add or decrease indentation  button for a bullet point 
+
+
+Observed Result:
+""Confirm Navigation?"" dialog box are showing up .
+
+See the screenshot attached.
+
+Test Environment: mw.org
+Browser: Chrome Version 26.0.1410.65 & FF25
+OS: MAC OS X 10. 8. 5 
+Page:https://www.mediawiki.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13048}",1391111220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r236onqi4kxnnfykppxk,task_description,resolved
+"VisualEditor: Clicking on Increase/Decrease Indentation button multiple times shows ""Confirm Navigation?"" dialog box on mediawiki.org",This now seems to be fixed!,1431640555,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-r236onqi4kxnnfykppxk,task_subcomment,NA
+"VisualEditor: ""Review your changes"" and ""Save Page"" button layout missing in test2","Screenshot
+
+Steps to reproduce:
+
+
+
+1.Open any page with VE in test 2
+2.Add some content and Save page
+
+Observed Result:
+""Review your changes"" and ""Save Page"" button layout missing in test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13039}",1391109780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lb4esyvemyxlbz7scvjj,task_description,declined
+"VisualEditor: ""Review your changes"" and ""Save Page"" button layout missing in test2",Not happening anymore,1391120065,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lb4esyvemyxlbz7scvjj,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"It would make sense, since all repositories (except VisualEditor) have Selenium tests already there:
+
+https://github.com/wikimedia/mediawiki-selenium#links
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391077980,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-xdef52u2xoutalmxvqxq,task_description,resolved
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Change 111998 merged by Cmcmahon:
+Moved Selenium tests from root folder of qa/browsertests repository to tests/browser folder
+
+https://gerrit.wikimedia.org/r/111998",1391789269,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Change 111997 merged by jenkins-bot:
+Moved tests from root folder to tests/browser folder
+
+https://gerrit.wikimedia.org/r/111997",1391770846,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Change 111998 had a related patch set uploaded by Zfilipin:
+Moved Selenium tests from root folder of qa/browsertests repository to tests/browser folder
+
+https://gerrit.wikimedia.org/r/111998",1391770769,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Change 111997 had a related patch set uploaded by Zfilipin:
+Moved tests from root folder to tests/browser folder
+
+https://gerrit.wikimedia.org/r/111997",1391770062,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder,"Chris, Jeff, what do you think?
+
+It would simplify our documentation and also Jenkins job template[1].
+
+We could replace
+
+if [ -d ""${FOLDER}"" ]; then cd ${FOLDER}; fi
+
+with just
+
+cd ${FOLDER}
+
+1: https://github.com/wikimedia/mediawiki-selenium/blob/master/docs/template.md#jelly-based-transformation",1391078169,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-xdef52u2xoutalmxvqxq,task_subcomment,NA
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,"Screenshot
+
+Cannot load any page on Betalabs.Getting the following error:
+
+6ca85571] /wiki/29th_January Exception from line 84 of /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php: Wikibase: Incomplete configuration: $wgWBRepoSettings[""entityNamespaces""] has to be set to an array mapping content model IDs to namespace IDs. See ExampleSettings.php for details and examples.
+
+Backtrace:
+
+#0 [internal function]: Wikibase\RepoHooks::onSetupAfterCache()
+#1 /data/project/apache/common-local/php-master/includes/Hooks.php(206): call_user_func_array(string, array)
+#2 /data/project/apache/common-local/php-master/includes/GlobalFunctions.php(3976): Hooks::run(string, array, NULL)
+#3 /data/project/apache/common-local/php-master/includes/Setup.php(520): wfRunHooks(string)
+#4 /data/project/apache/common-local/php-master/includes/WebStart.php(153): require_once(string)
+#5 /data/project/apache/common-local/php-master/index.php(46): require(string)
+#6 /data/project/apache/common-local/w/index.php(3): require(string)
+#7 {main}
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+
+**Attached**: {F12982}",1391045040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_description,resolved
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,*** Bug 60612 has been marked as a duplicate of this bug. ***,1391090756,PHID-USER-lzhljhpbm3qfphvqyill,False,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_subcomment,NA
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,Thanks.Verified the fix.,1391054896,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_subcomment,NA
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,"Fixed, will propagate to labs within the next 30 minutes, probably a bit earlier",1391045340,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_subcomment,NA
+VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php,Being worked on.,1391045213,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2hjerlp3jrpdifpv6ca6,task_subcomment,NA
+VisualEditor isn't able to handle header and row templates,"The VisualEditor template editor works on infobox templates like https://en.wikipedia.org/wiki/Template:Infobox_NRHP . On templates like https://en.wikipedia.org/wiki/Template:NRHP_header and https://en.wikipedia.org/wiki/Template:NRHP_row it doesn't work (yet) probably because these templates generate tables. We have a lot of these templates in a lot of different languages, see for example https://en.wikipedia.org/wiki/Category:Monument_list_templates . It would be nice if VE could be used to edit these templates.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391033760,PHID-USER-cw4amt4ewxdze5qcjdca,False,PHID-TASK-covwdyeu7km7zagn5wbs,task_description,resolved
+VisualEditor isn't able to handle header and row templates,"As @Etonkovidova said, it is possible (though not user-friendly) to do this. I'm tentatively closing; if anyone has specific ideas for how to make this more user friendly, feel free to open another task.",1437692916,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-covwdyeu7km7zagn5wbs,task_subcomment,NA
+VisualEditor isn't able to handle header and row templates,"The template content(and fields) can be edited via Transclusion or in Edit Source. 
+Checked in production  {{NRHP row}} , {NRHP header}}- in VE in Transclusion box the templates can be edited.
+
+",1421455993,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-covwdyeu7km7zagn5wbs,task_subcomment,NA
+"VisualEditor: After adding an empty gallery in a list, the list continues adding bullets/numbered points even after hitting return twice","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391024460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ey2t66avbr7lh2xruo6p,task_description,invalid
+"VisualEditor: After adding an empty gallery in a list, the list continues adding bullets/numbered points even after hitting return twice",I can't reproduce this now – presumably now fixed by not allowing empty galleries.,1394488268,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ey2t66avbr7lh2xruo6p,task_subcomment,NA
+"VisualEditor: After adding an empty gallery in a list, the list continues adding bullets/numbered points even after hitting return twice","Steps to reproduce:
+
+1.Open a page with VE
+2.Add a numbered list/bullet list
+3.Add an empty gallery as an item in the list.
+4.Now place the cursor in the last bullet/numbered point
+5.Press Enter twice
+
+Observed Result:
+
+It keeps on adding new bullets or numbered points in the list even after hitting return twice.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=29th_January&veaction=edit",1391029124,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ey2t66avbr7lh2xruo6p,task_subcomment,NA
+VisualEditor:  Special character inserter behaves oddly if you don't click somewhere in the page first,"Intention:
+Add a special character.
+
+Steps to Reproduce:
+1. Open a page in VisualEditor.  Don't click anywhere in it.
+
+2. Go to Insert > Special characters to open the Special charater inserter tool.
+
+3. Click on a character (or several).
+
+Actual Results:  
+Nothing is added, but the ""Save"" button lights up.  You can't use it, though.
+
+If you click elsewhere, the tool disappears, but nothing else happens.  ""Save"" is still green, but you still can't use it.
+
+If you go back into the special character tool and add a new special character, then all the original ones appear at the start of the page, but the tool's dialog box is still open.  
+
+If you then cancel (to get rid of the box), Bad Things happen, including snowmen and partial duplication of the page.  You still can't save.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390866360,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-riotbykdtow5sbh7ljef,task_description,declined
+VisualEditor:  Special character inserter behaves oddly if you don't click somewhere in the page first,"This has now been ""fixed"" by the simple effort of making this route impossible; tools are now disabled if there isn't an active surface insertion point.",1400546311,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-riotbykdtow5sbh7ljef,task_subcomment,NA
+VisualEditor: 'mozMatchesSelector' called on an object that does not implement interface when launching VE,"When launching VE in Firefox, it throws the following error:
+'mozMatchesSelector' called on an object that does not implement interface
+
+Happens on beta labs and local master.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1390864440,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-mcp3tejcciwpxx3d2tbm,task_description,declined
+VisualEditor: 'mozMatchesSelector' called on an object that does not implement interface when launching VE,Can't reproduce this now (Firefox 33.1 with Firebug)…,1415884389,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mcp3tejcciwpxx3d2tbm,task_subcomment,NA
+VisualEditor: 'mozMatchesSelector' called on an object that does not implement interface when launching VE,"Actually, it's not a JS error, but a breakpoint being triggered in Firebug.",1391542151,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-mcp3tejcciwpxx3d2tbm,task_subcomment,NA
+VisualEditor: 'mozMatchesSelector' called on an object that does not implement interface when launching VE,"Happens in Firefox 26 and latest nightly build.
+
+Although it's not that helpful for debugging, the error is thrown from line 5303 of jquery.js:
+var ret = matches.call( elem, expr );",1390945304,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-mcp3tejcciwpxx3d2tbm,task_subcomment,NA
+VisualEditor: [Regression] Save dialog no longer expands when viewing diff,"When you click ""Review your changes"" in the save dialog, it used to grow to accommodate the fact that diffs tend to be bigger than the regular save dialog contents. However, it stopped doing this a while ago.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390857780,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-f2ifd6fdj6pchv36q7fq,task_description,resolved
+VisualEditor: [Regression] Save dialog no longer expands when viewing diff,"Change 116897 merged by jenkins-bot:
+Update VE core submodule to master (ab70193)
+
+https://gerrit.wikimedia.org/r/116897",1394066191,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f2ifd6fdj6pchv36q7fq,task_subcomment,NA
+VisualEditor: [Regression] Save dialog no longer expands when viewing diff,"Change 116897 had a related patch set uploaded by Catrope:
+Update VE core submodule to 4513d9c21a9502b2fc2d9b6739c2dac0af21e03e
+
+https://gerrit.wikimedia.org/r/116897",1394059358,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f2ifd6fdj6pchv36q7fq,task_subcomment,NA
+Enable on redirects,"Redirects are normal wiki pages of main ns. So why not should allow to edit them with VisualEditor? For example in cases, I remove redirect and want edit a page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390664940,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-f3t5ledkhevthmf76bbm,task_description,resolved
+Enable on redirects,"(In reply to Juan de Vojníkov from comment #2)
+> Why you mareked it as duplicate. 
+
+Because it is the same request as bug 50878.
+
+> I can see the other bug takes care of en.w.
+
+No. https://gerrit.wikimedia.org/r/#/c/95213/ is generic. It's code in VisualEditor itself, not in server configuration.",1392637581,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-f3t5ledkhevthmf76bbm,task_subcomment,NA
+Enable on redirects,"(In reply to James Forrester from comment #1)
+> 
+%%%> *** This bug has been marked as a duplicate of bug 50878 ***%%%
+
+Why you mareked it as duplicate. I can see the other bug takes care of en.w. Here I am talking about cs.w and potetionally every other.",1392634313,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-f3t5ledkhevthmf76bbm,task_subcomment,NA
+Enable on redirects,"
+
+*** This bug has been marked as a duplicate of bug 50878 ***",1390695336,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f3t5ledkhevthmf76bbm,task_subcomment,NA
+Page rendered completely blank,"When I loaded [[mw:Mobile wikitext editing]] recently as a logged-in user, the page looked completely blank. This may be an issue in VisualEditor, I'm not sure. Purging the page fixed the issue.
+
+My suspicion is that Parsoid somehow returned blank content. Unfortunately I'm unable to reproduce this issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Mobile_wikitext_editing",1390590840,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-5qndpoaoah52uflwalmh,task_description,declined
+Page rendered completely blank,"Without a way to reproduce this or some kind of error log we can't really do anything here. There have also not been any other reports about blank pages, so closing this bug as worksforme.",1391717249,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-5qndpoaoah52uflwalmh,task_subcomment,NA
+Page rendered completely blank,"This is the Parsoid output: http://parsoid-lb.eqiad.wikimedia.org/mediawikiwiki/Mobile_wikitext_editing?oldid=889921
+
+Client-side VE issues typically result in JS errors in the browser JS console. Could you check whether that is the case?",1390785697,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-5qndpoaoah52uflwalmh,task_subcomment,NA
+Clicking the Media Settings Widget does not open the dialog,"I'm on 1.23wmf10 and the master build of both VisualEditor and Parsoid. I can insert and resize an image just fine, but clicking on the icon in the upper right performs no action. I discovered the following message:
+
+Uncaught TypeError: undefined is not a function 
+
+load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%2Cmwcore%2Cmwgalle…:344
+VeUiMediaSizeWidget load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%2Cmwcore%2Cmwgalle…:344
+ve.ui.MWMediaEditDialog.initialize load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%2Cmwcore%2Cmwgalle…:528
+oo.EventEmitter.emit load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.pl…:112
+(anonymous function) load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.pl…:125
+pollExternalStylesheets load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.pl…:124
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390582500,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-4yqfpq6tylsvui2kalk4,task_description,invalid
+Clicking the Media Settings Widget does not open the dialog,Updating to a more recent build of VisualEditor resolves this issue.,1401744326,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-4yqfpq6tylsvui2kalk4,task_subcomment,NA
+"VisualEditor:  Make {{reflist}} update with new refs as you add them, just like <references /> does","Intention:
+<References /> automatically updates as you edit a page.  The {{Reflist}} template does not.  Can the handling of the template be improved so that refs inside the {{ref list}} template also update automatically?
+
+
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1390437480,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-eee27mysfumux3ogerbm,task_description,duplicate
+"VisualEditor:  Make {{reflist}} update with new refs as you add them, just like <references /> does","This is a confusing response. {{reflist}} is used all over the place, often by preference.
+
+A blank ""wontfix"" doesn't address the reasons for this statement, and they do in fact need addressing. Are you planning to systematically remove {{reflist}}, for example? Clarification is needed on this point.",1390853772,PHID-USER-gfaq55vdypjmzz6nl2kn,True,PHID-TASK-eee27mysfumux3ogerbm,task_subcomment,NA
+"VisualEditor:  Make {{reflist}} update with new refs as you add them, just like <references /> does","(In reply to comment #0)
+> Intention:
+> <References /> automatically updates as you edit a page.  The {{Reflist}}
+> template does not.  Can the handling of the template be improved so that refs
+> inside the {{ref list}} template also update automatically?
+
+Unfortunately, no, we can't.
+
+This is one of the (many) reasons why we discourage people from using {{Reflist}}.",1390607802,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eee27mysfumux3ogerbm,task_subcomment,NA
+VisualEditor:The image resize handle is not appearing at the corner of the selection box around the image when it has a caption,"screenshot
+
+Steps to reproduce:
+
+1.Open a page which contains image with VE
+2.Add a large caption to the image by going to Media Settings
+3.Click on ""Apply Changes""
+4.Attempt to resize the image
+
+Observed Result:
+The image resize handle is not at the most bottom-left corner of the blue highlighted selection box around the image but at the corner of the image.
+It looks a bit odd to have it somewhere in the middle of the border when it has a large caption.
+Probably ,having it at the corner most corner will look better.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F13020}",1390423260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6yggapp3gflkqr5tutc5,task_description,declined
+VisualEditor:The image resize handle is not appearing at the corner of the selection box around the image when it has a caption,"This is correct as you are resizing the image, not the caption.",1390585818,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6yggapp3gflkqr5tutc5,task_subcomment,NA
+VisualEditor:The selected parameter gets switched upon mouse-up beyond the right panel,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a template like Cite web
+3.Select the parameter URL
+4.Add a value in this field like http://yahoo.com
+5.Now select this text from right to left
+6.Mouse up just a little beyond the borderline between left panel and right panel
+
+Observed Result:
+
+The parameter on the right panel gets switched to the next parameter which is ""Source Title""
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+Page:https://test2.wikipedia.org/w/index.php?title=22nd_january&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13019}",1390419240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mhhjk5pjhzhxuptufuod,task_description,declined
+VisualEditor:The selected parameter gets switched upon mouse-up beyond the right panel,I don't see any oddities now… marking as such.,1415054014,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mhhjk5pjhzhxuptufuod,task_subcomment,NA
+VisualEditor:The selected parameter gets switched upon mouse-up beyond the right panel,"I'm not quite sure what was happening here, but is this bug still valid?",1414884201,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-mhhjk5pjhzhxuptufuod,task_subcomment,NA
+VE does not appear at all on beta labs,"Seen as of Jan 22
+
+As a logged in user, edit any page on http://en.wikipedia.beta.wmflabs.org/ with VisualEditor. 
+
+User sees the ve-init-mw-viewPageTarget-loading bars moving, but VE never arrives. 
+
+Checked in Chrome and Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1390405560,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-iu3irtpbwblnycah2bvt,task_description,resolved
+VE does not appear at all on beta labs,"VisualEditor is working for me on beta.  I noticed some files belonged to root user, I have changed back to be owned by mwdeploy:mwdeploy.  That might have caused some update issue since the update job runs as mwdeploy.",1390506391,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+VE does not appear at all on beta labs,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Is the version of VE referenced by the mediawiki/extensions meta repo?
+> 
+> http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version says it's got VE
+> 37e90c1 from yesterday – https://gerrit.wikimedia.org/r/#/c/108713/ – which
+> isn't the latest version.
+
+That is bug 49846 (VE not being automatically updated on beta) which is now fixed.",1390502272,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+VE does not appear at all on beta labs,"Antoine, is this tracked already?",1390469804,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+VE does not appear at all on beta labs,"(In reply to comment #1)
+> Is the version of VE referenced by the mediawiki/extensions meta repo?
+
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version says it's got VE 37e90c1 from yesterday – https://gerrit.wikimedia.org/r/#/c/108713/ – which isn't the latest version.",1390416458,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+VE does not appear at all on beta labs,Is the version of VE referenced by the mediawiki/extensions meta repo?,1390416280,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-iu3irtpbwblnycah2bvt,task_subcomment,NA
+Visualeditor:A Return character gets placed between two galleries placed one after another,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which has a gallery in it
+2.Add another gallery code just after the already existing one
+3.Save the page
+4.Reopen the page with VE
+
+Observed Result
+A return arrow appears between the two galleries
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page: https://test2.wikipedia.org/wiki/Thedomtest?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12925}",1390348620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vtsg5xob5vkahyr6gi7o,task_description,resolved
+Visualeditor:A Return character gets placed between two galleries placed one after another,"This also looks to have been fixed, probably by Parsoid.",1406754223,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vtsg5xob5vkahyr6gi7o,task_subcomment,NA
+VisualEditor:The gallery inspector adds a newline while opening up a gallery,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which has for example the following gallery code:
+<gallery>
+File:Joo Chiat Place.jpg|Item 1
+File:Joo Chiat Place.jpg|a link to [[Help:Contents]]
+File:Joo Chiat Place.jpg
+File:Joo Chiat Place.jpg|alt=An example image. It has flowers
+File:Joo Chiat Place.jpg| ''italic caption''
+</gallery>
+
+2.Click on the gallery and open it with the new gallery inspector
+
+Observed Result:
+There is an extra newline inserted at the beginning of gallery code inside the inspector.
+
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Thedomtest?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12923}",1390346700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-l4vjyqc363bdzzivdhbk,task_description,resolved
+VisualEditor:The gallery inspector adds a newline while opening up a gallery,"No longer occurs, probably fixed a long time ago.
+
+{F128164}",1429599901,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-l4vjyqc363bdzzivdhbk,task_subcomment,NA
+VisualEditor: Reference numbers do not display properly on fr.wp,"NemesisIII reports that when VEditing a page, existing reference numbers do not appear as ""superscripted"" as they should.
+See section ""projet"" of https://commons.wikimedia.org/wiki/File:Bug_%C3%A9diteur_visuel_affichage_appels_de_r%C3%A9f%C3%A9rence.png (from https://fr.wikipedia.org/wiki/Avenue_Foch?veaction=edit ).
+Number 3 and 4 are existing references, and they are very low. Number 5 instead is a newly added reference, which displays ok (note that this reference does not really exist in the article, it was added just to take the screenshot).
+
+According to my tests, only fr.wp seems affected. I was able to reproduce this with
+*Firefox (both Vector and Monobook)
+*Chrome (Monobook)
+*Opera (while logged out).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390305780,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-xcqwgfkr43r7ohstvh74,task_description,resolved
+VisualEditor: Reference numbers do not display properly on fr.wp,"Fixed ages ago, I think.",1414624599,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xcqwgfkr43r7ohstvh74,task_subcomment,NA
+VisualEditor: Reference numbers do not display properly on fr.wp,"Updating the link, https://fr.wikipedia.org/wiki/Avenue_Foch_(Paris)?veaction=edit .",1392295643,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-xcqwgfkr43r7ohstvh74,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**Author:** `llamaal_wikis`
+
+**Description:**
+Intention:
+After the conclusion of https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual on the Spanish Wikipedia, some changes to the status of VE in that project have to be implemented:
+
+1. VE should now be opt-in
+2. The ""edit"" tab should return to wikitext
+3. VE should be presented as part of Beta Features
+4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+
+Regards,
+
+LlamaAl
+
+
+
+
+Reproducible: Didn't try
+
+After the conclusion of https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual on the Spanish Wikipedia, some changes to the status of VE in that project have to be implemented:
+
+1. VE should now be opt-in
+2. The ""edit"" tab should return to wikitext
+3. VE should be presented as part of Beta Features
+4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+
+Regards,
+
+LlamaAl
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1390009560,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oap3pcoqr67a3nxmzly7,task_description,resolved
+Changes to VisualEditor on eswiki as result of vote,"
+
+*** This bug has been marked as a duplicate of bug 60188 ***",1390011045,PHID-USER-3qsavo6roa5h32xcsgng,False,PHID-TASK-oap3pcoqr67a3nxmzly7,task_subcomment,NA
+VisualEditor:Only a single node is appearing to drag an image to resize,"Single node
+
+Steps to reproduce:
+
+
+1.Open a page with VE which has image inside it
+2.Select the image
+
+Observed Result:
+There is just one node appearing on the bottom-left corner of the image to resize it,previously there used to four nodes to drag.
+
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/, wmf11
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13171}",1389907260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kpwswnv3ba5na6dn3pbp,task_description,invalid
+VisualEditor:Only a single node is appearing to drag an image to resize,Not a bug; intentional behaviour change. :-),1389907705,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kpwswnv3ba5na6dn3pbp,task_subcomment,NA
+"VisualEditor:""Cite error: <ref> tags exist, but no <references/> tag was found ""  after adding a reference in the caption of an image although there was <references/> tag","In edit source mode
+
+Steps to reproduce:
+
+1.Open a page with VE which has some references and <references/> tag added 
+2.Add an image in the page
+3.Go to media settings and add a caption with reference inside it
+4.Save the page
+
+Observed Result:
+An error appears in the read mode :""Cite error: <ref> tags exist, but no <references/> tag was found ""
+
+Also in the resulting wikitext, the reference inside image did not get added in the <references/> section
+
+
+
+Although if you go to Edit mode the reference inside the image is correctly showing up in the <references/> tag.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://test2.wikipedia.org/wiki/Wmf11
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13149}",1389902400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v3oimjdnujt4xxuujgme,task_description,invalid
+"VisualEditor:""Cite error: <ref> tags exist, but no <references/> tag was found ""  after adding a reference in the caption of an image although there was <references/> tag","This is because the <references /> was before the <ref>.
+
+Yay MediaWiki. :-(
+
+Fixed: 
+
+https://test2.wikipedia.org/w/index.php?title=Wmf11&oldid=71790
+
+vs.
+
+https://test2.wikipedia.org/w/index.php?title=Wmf11&oldid=71598",1390022111,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v3oimjdnujt4xxuujgme,task_subcomment,NA
+"VisualEditor:""Cite error: <ref> tags exist, but no <references/> tag was found ""  after adding a reference in the caption of an image although there was <references/> tag","Created attachment 14327
+In Edit mode
+
+**Attached**: {F13150}",1389902484,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v3oimjdnujt4xxuujgme,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","The i18n messages for the Toolbar insert button and the subsequent special character tree does not seem to sync with translated messages at Translatewiki. 
+For some reason French and German gives correct messages but others give English default messages.
+
+The strings are:
+visualeditor-toolbar-insert
+visualeditor-specialcharacter-button-tooltip
+visualeditor-specialcharacterinspector-title
+visualeditor-specialcharinspector-characterlist-insert
+
+Possibly related to them being marked as non-translatable on translatewiki.
+
+See annotated screenshot at:
+https://commons.wikimedia.org/wiki/File:VisualEditorBugInsert.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389894780,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-3tsgq57muuprxfvxj5ar,task_description,resolved
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","(In reply to Lokal_Profil from comment #7)
+> Whatever was done seems to have worked. Thanks (closing)
+
+Yes, that was https://gerrit.wikimedia.org/r/#/c/109420/ (+ https://gerrit.wikimedia.org/r/#/c/112650/ ).",1392983896,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable",Whatever was done seems to have worked. Thanks (closing),1392138855,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","(In reply to comment #5)
+> These translations are still not being pushed through, is there anything else
+> which might have caused this?
+> 
+> Could translations which were done whilst the messages were ""untranslatable""
+> somehow have not triggered an updated translation?
+
+Opening again as this has not gotten fixed. See e.g. https://sv.wikipedia.org/wiki/Foo?veaction=edit&uselang=sv where ""Insert"" is still displayed as well as the other messages. To the list above can be added
+
+Visualeditor-mwgalleryinspector-title",1391698958,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","These translations are still not being pushed through, is there anything else which might have caused this?
+
+Could translations which were done whilst the messages were ""untranslatable"" somehow have not triggered an updated translation?",1391432413,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","Change 109420 had a related patch set uploaded by Jforrester:
+Re-enable support for two VisualEditor related groups
+
+https://gerrit.wikimedia.org/r/109420",1390605367,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","Change 107541 abandoned by Jforrester:
+Add support for moved VisualEditor core
+
+Reason:
+Done instead in Ia580491d9b329200d3def5425d887f0062e0a1a2.
+
+https://gerrit.wikimedia.org/r/107541",1390605331,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","Change 107541 had a related patch set uploaded by Jforrester:
+Add support for moved VisualEditor core
+
+https://gerrit.wikimedia.org/r/107541",1389934286,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable","Yeah, this is because TranslateWiki.Net removed tracking of VisualEditor's core messages (rather than the MW-specific ones) when the repo was split, and haven't yet added them back. Sorry about this!",1389934240,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tsgq57muuprxfvxj5ar,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"**Author:** `swalling`
+
+**Description:**
+Screenshot on enwiki
+
+Detection of the 'edit' tab and section edit links is broken currently, probably due to https://gerrit.wikimedia.org/r/#/c/97701/ change in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F13059}",1389826140,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kts426m6tijfml3ngiqw,task_description,resolved
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107735 merged by jenkins-bot:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107735",1389831185,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107734 merged by jenkins-bot:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107734",1389831178,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107735 had a related patch set uploaded by Mattflaschen:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107735",1389827628,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107734 had a related patch set uploaded by Mattflaschen:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107734",1389827613,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107631 merged by jenkins-bot:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107631",1389826467,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Change 107631 had a related patch set uploaded by Mattflaschen:
+Change how presence of VisualEditor is determined
+
+https://gerrit.wikimedia.org/r/107631",1389826330,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar',"Specifically, VE's isAvailable used to imply that the preference was also enabled, meaning the VE edit tab would be there.
+
+Now, isAvailable doesn't say anything about the preference. So if you have VE disabled, the tab will be missing, so it can't attach to it, and shows in the center like that.",1389826281,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-kts426m6tijfml3ngiqw,task_subcomment,NA
+Keep Going overlay overlaps with visualeditor overlay,"https://en.m.wikipedia.org/wiki/Lost_Coon_Lake?title=Lost_Coon_Lake&campaign=mobile-mainpage-keepgoing-links&mobileaction=alpha#editor/0
+
+Expected:
+The Keep Going overlay should appear below the VE overlay.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389820920,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-zjzk5xt7l23o75cnuaf2,task_description,declined
+Keep Going overlay overlaps with visualeditor overlay,Seems to have fixed itself.,1390607906,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-zjzk5xt7l23o75cnuaf2,task_subcomment,NA
+Keep Going overlay overlaps with visualeditor overlay,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1627",1389821133,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zjzk5xt7l23o75cnuaf2,task_subcomment,NA
+Incorrect wiki code when applying category,"Hi
+If I apply a category to a page using VE, it generates an incorrect code (for example %2520 instead of _ I think) and it has only one square character.
+
+Latest git of VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: http://wiki.mc128k.info/index.php/Test",1389650340,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_description,declined
+Incorrect wiki code when applying category,"Upgraded to latest git for MW, VE and Parsoid, now it works! Thanks!",1394972583,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_subcomment,NA
+Incorrect wiki code when applying category,"I'm sorry for the delay. Tried upgrading to latest and I get the same error. See the link.
+http://wiki.mc128k.info/index.php/Test",1390769648,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_subcomment,NA
+Incorrect wiki code when applying category,"Marking as ""WORKSFORME""; feel free to re-open if you have more details.",1390608352,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_subcomment,NA
+Incorrect wiki code when applying category,"Can you give some more details? It appears to be working locally, and on WMF production (see e.g. https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=885698&oldid=885622 for it working).
+
+A screenshot or copy-paste of your resultant wikitext (and ideally a dump of the HTML that got sent to Parsoid) would be hugely helpful.",1389989903,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dgtxn3qlqf7gdy53gvep,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"**Author:** `kwang`
+
+**Description:**
+If you are in the keep going campaign and you are in alpha, when you click edit you don't get VE you get the wikitext editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389403020,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rdqowzyta6j737yhntsg,task_description,resolved
+First edit in VE doesn't launch KeepGoing campaign,"Change 108990 merged by jenkins-bot:
+Make KeepGoing/toast confirmation run when editing using VE
+
+https://gerrit.wikimedia.org/r/108990",1391456992,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"Change 109436 merged by jenkins-bot:
+QA: Define expected behaviour for VisualEditor overlay for bug 59932
+
+https://gerrit.wikimedia.org/r/109436",1391200206,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"Change 109436 had a related patch set uploaded by Jdlrobson:
+QA: Define expected behaviour for VisualEditor overlay for bug 59932
+
+https://gerrit.wikimedia.org/r/109436",1391196909,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"**kwang** wrote:
+
+Unable to reproduce. I think this might actually have been the portrait landscape bug and I got confused.",1390456194,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"**kwang** wrote:
+
+This was originally if I launched keep going from the main page I was unable to get visual editor to launch. But this seems to be fixed now, or I am unable to reproduce anymore.",1390441148,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"Change 108990 had a related patch set uploaded by Jdlrobson:
+Make KeepGoing run when editing using VE
+
+https://gerrit.wikimedia.org/r/108990",1390429399,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"I don't understand this bug. You can't currently enter the KeepGoing campaign via VE. Kenan could you explain what the exact problem is here?
+
+Is the request that when I edit for the first time via VisualEditor it starts the Keep Going campaign to edit?",1390428453,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+First edit in VE doesn't launch KeepGoing campaign,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1614",1389403228,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rdqowzyta6j737yhntsg,task_subcomment,NA
+VisualEditor:Image size is appearing differently in the tooltip in  VE compared to the set value in Edit Source mode,"Screenshot in the Edit source mode
+
+Steps to reproduce:
+
+1.Open a page with VE 
+2.Insert any image
+3.Resize the image to specific size.For example:587x687px
+4.Save the page
+5.Open the page in Edit Source mode
+
+
+Observed Result:
+The Edit source mode shows the size of the image differently as 587x411
+
+Test Environment: mw.org
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12636}",1389383700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-42yujcjufaw4amwkd6cx,task_description,invalid
+VisualEditor:Image size is appearing differently in the tooltip in  VE compared to the set value in Edit Source mode,"After checking with the Parsoid team, this isn't a bug -- Parsoid serializes a square bounding box (max sizes) which is why the wikistring is different than the actual image size (that preserves aspect ratio).",1389827322,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-42yujcjufaw4amwkd6cx,task_subcomment,NA
+VisualEditor:Image size is appearing differently in the tooltip in  VE compared to the set value in Edit Source mode,"Created attachment 14285
+Size in the tooltip of VE
+
+**Attached**: {F12637}",1389383780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-42yujcjufaw4amwkd6cx,task_subcomment,NA
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"Intention:
+If I understand it correctly, the user defines a link target for text. This seems to highlight/mark the text for that user, so if the user then enters a space as the next letter as s/he wants to continue writing, this will overwrite the marked text. Says this happens with Safari 6.1.1 and Firefox 26.0 on OS X 10.7.5 and 10.8.5 (all four combinations). Haven't tried other browsers/operating systems. 
+
+Steps to Reproduce:
+1. Tried but could not duplicate this problem in Firefox 26 or Chrome 31
+2. 
+3. 
+
+
+
+Reproducible: Couldn't Reproduce
+
+Andre says: https://bugzilla.wikimedia.org/show_bug.cgi?id=57716 item 2# feels slightly related but not exactly the same.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://sv.wikipedia.org/wiki/Wikipedia:VisualEditor/%C3%85terkoppling#L.C3.A4nkad_text_blir_markerad_och_f.C3.B6rsvinner",1389313080,PHID-USER-brn4v5ta45bnw4f5as3h,True,PHID-TASK-l4uq3cbllrcxoqio4v45,task_description,declined
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"I don't know about this; this is intentional behaviour to give users the ability to do something further with their selection (often laboriously-made) if they want to, especially for those primarily using keyboard input.
+
+When you click away from the inspector, we move the cursor to where you clicked it. However, if you're using keyboard driving, you might want to adjust the item you just selected and did an action on, e.g. adding bold/etc. styling.
+
+In general, we've designed the editor so that removing the selection using the keyboard needs you to destroy the selection (type over it) or move the cursor with the cursor keys. I don't think we want to move away from this model, so I'm going to mark this as WONTFIX, but I'd be happy to discuss further if people think this is a mistake.",1390023404,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l4uq3cbllrcxoqio4v45,task_subcomment,NA
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"Thanks, NH. :) Actually, I was able to reproduce it this time! The text that was to be linked was selected or highlighted so that it could be linked. Pressing enter the first time makes the linking box/window/popup go away. Pressing enter a second time makes the newly-linked text go away. The work around is to click with cursor elsewhere on the page so as to deselect/unhighlight the text. But if this can be fixed code wise, would save everyone one additional click. HTH. :)",1389375082,PHID-USER-brn4v5ta45bnw4f5as3h,True,PHID-TASK-l4uq3cbllrcxoqio4v45,task_subcomment,NA
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"**nh.wikipedia** wrote:
+
+Anna Koval got it right, but I'll clarify anyway:
+
+1) Open some page for editing.
+2) Type a word that you wish to link to another page.
+3) Press Command-K or click at the link tool button.
+4) Select or type the name of the target page and press enter twice.
+5) When you continue to type the linked word disappears.
+
+If you, at step (4), click at the ""Close"" button in the link dialog instead of using the Enter key to complete, this does not happen.",1389349207,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-l4uq3cbllrcxoqio4v45,task_subcomment,NA
+VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it,"For the records: From https://sv.wikipedia.org/wiki/Wikipedia:VisualEditor/%C3%85terkoppling#L.C3.A4nkad_text_blir_markerad_och_f.C3.B6rsvinner
+
+I cannot reproduce in Firefox 26 on Fedora Linux 20 on cs.wikipedia.org - after clicking the ""Close"" button on the left in the ""Link target"" dialog the link text is not highlighted for me.",1389316714,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-l4uq3cbllrcxoqio4v45,task_subcomment,NA
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,"In read mode
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add few images to the page
+3.Save the Page
+4.Now click on any of the newly added images 
+5.Press back button from the browser to go back to the article
+
+Observed Result:
+The images in the page gets disappeared in the readmode though opening the VE shows up all the images.
+
+Test Environment:https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Wmf10
+
+
+See the screenshots attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12534}",1389309540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_description,declined
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,Cannot reproduce it now.,1389832746,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_subcomment,NA
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,This is occurring in mw.org too for adding any image.,1389387303,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_subcomment,NA
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,"Slight modification in the steps:
+
+1.Open a page with VE
+2.Add a heading/subheading to the page
+3.Place the cursor right after the heading text
+4.Insert an image
+5.Save the page
+6.Now click on any of the newly added images 
+7.Press back button from the browser to go back to the article
+
+Observed Result:
+The newly added image and the heading is not showing up in the readmode.",1389311591,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_subcomment,NA
+VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2,"Created attachment 14276
+In edit mode
+
+**Attached**: {F12535}",1389309582,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ni5qpiyvtnjgi6dt3iyo,task_subcomment,NA
+VisualEditor:Cutting the section heading along with the content under it and pasting them back moves the heading under the content,"Section heading got moved below the link of heading
+
+Steps to reproduce:
+
+1.Open a page with VE which has a section with section heading
+2.Cut the whole section with its heading
+3.Paste it back in the same position
+
+Observed Result:
+The heading of the section gets placed under the heading line with the contect
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/9th_jan?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12519}",1389296400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kbipswhiezygmb4rkkls,task_description,resolved
+Fatal error: Call to a member function matchStartAndRemove() on a non-object at Parser.php on line 3262,"[09-Jan-2014 19:32:59] Fatal error: Call to a member function matchStartAndRemove() on a non-object at /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php on line 3262
+Server: mw1149
+Method: GET
+URL: http://www.mediawiki.org/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*
+Backtrace:
+#0 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(3262): Parser::braceSubstitution()
+#1 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPFrame_DOM))
+#2 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(3147): PPFrame_DOM->expand(Object(PPNode_DOM), 0)
+#3 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(620): Parser->replaceVariables('{{ns:project}}:...')
+#4 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(4842): Parser->preprocess('{{ns:project}}:...', NULL, Object(ParserOptions))
+#5 /usr/local/apache/common-local/php-1.23wmf10/includes/cache/MessageCache.php(1002): Parser->transformMsg('{{ns:project}}:...', Object(ParserOptions), NULL)
+#6 /usr/local/apache/common-local/php-1.23wmf10/includes/Message.php(856): MessageCache->transform('{{ns:project}}:...', false, Object(Language), NULL)
+#7 /usr/local/apache/common-local/php-1.23wmf10/includes/Message.php(592): Message->transformText('{{ns:project}}:...')
+#8 /usr/local/apache/common-local/php-1.23wmf10/includes/Message.php(649): Message->toString()
+#9 /usr/local/apache/common-local/php-1.23wmf10/extensions/VisualEditor/VisualEditorDataModule.php(94): Message->text()
+#10 /usr/local/apache/common-local/php-1.23wmf10/extensions/VisualEditor/VisualEditorDataModule.php(129): VisualEditorDataModule->getMessageInfo()
+#11 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoader.php(102): VisualEditorDataModule->getMessages()
+#12 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoaderStartUpModule.php(265): ResourceLoader->preloadModuleInfo(Array, Object(ResourceLoaderContext))
+#13 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoaderStartUpModule.php(150): ResourceLoaderStartUpModule->getModifiedTime(Object(ResourceLoaderContext))
+#14 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoaderStartUpModule.php(224): ResourceLoaderStartUpModule::getModuleRegistrations(Object(ResourceLoaderContext))
+#15 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoader.php(761): ResourceLoaderStartUpModule->getScript(Object(ResourceLoaderContext))
+#16 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoader.php(516): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#17 /usr/local/apache/common-local/php-1.23wmf10/load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#18 /usr/local/apache/common-local/w/load.php(3): require('/usr/local/apac...')
+#19 {main}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389296160,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-utvzk3vp6pazzmc524i4,task_description,resolved
+Fatal error: Call to a member function matchStartAndRemove() on a non-object at Parser.php on line 3262,"Seems to be l10n cache related, but is fixed",1389298261,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-utvzk3vp6pazzmc524i4,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in duplicated section headings","Intention:
+Cut the appendices from an article (to see if they were the source of a problem), and then put them back (because they weren't)
+
+Steps to Reproduce:
+1. Select several sections from the end of an article, all the way to the end of the page.
+
+2. Command-x to cut.
+
+3. Command-v to paste.
+
+Actual Results:  
+The section headings were duplicated, but the content was not.  The result is two sets of section headings, the first of which is empty.  
+
+https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FS%26D&diff=588724359&oldid=588539903
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389227760,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-atmvlu42kr6udcjperus,task_description,resolved
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in duplicated section headings","[[https://en.wikipedia.org/w/index.php?title=User%3ANeil_P._Quinn-WMF%2FT61847&diff=657363248&oldid=657363001|Seems to work correctly now]] in Safari 8.0.3, although the copy-and-pasting does produce some significant normalization that may be a separate issue.",1429554871,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-atmvlu42kr6udcjperus,task_subcomment,NA
+VisualEditor:The <nowiki/> tag remains even after deleting spaces in between the link and re-applying a new link on it,"wikitext after step 8
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Type the following text:
+Tex ted
+3.Select this part of the text ""Tex t"" with a space in between.
+4.Now apply a link on it with command+k
+5.Save the page.
+6.Go to Edit source and observe the resulting wikitext for this is:
+[[tex t]]<nowiki/>ed
+
+7.Now reopen the page delete the space make it ""texted"" and delete the link applied.
+8.Reapply another link by selecting the whole text ""texted""
+
+Observed Result:
+The <nowiki/> tag still remains.The resulting wikitext after step 8 is:
+[[texted|text]]<nowiki/>[[texted|ed]]
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan8th&action=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12427}",1389209520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r2uo7jsfp6tf7hhh7pgx,task_description,resolved
+VisualEditor:The <nowiki/> tag remains even after deleting spaces in between the link and re-applying a new link on it,"This is because <nowiki /s> (unlike <nowiki>s) are ""meta"" items in the DOM rather than things VE can edit; merging with bug 56381.
+
+*** This bug has been marked as a duplicate of bug 56381 ***",1390023700,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-r2uo7jsfp6tf7hhh7pgx,task_subcomment,NA
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"When a page is loaded in portrait mode the VisualEditor is not loaded. We should get clever about when to load it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389206760,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gjdaipusi2pbcwygi4nx,task_description,resolved
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"Change 110625 merged by jenkins-bot:
+Load Tablet styles if portrait or landscape meets threshold
+
+https://gerrit.wikimedia.org/r/110625",1391454312,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gjdaipusi2pbcwygi4nx,task_subcomment,NA
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"Change 110625 had a related patch set uploaded by Jdlrobson:
+Load Tablet styles if portrait or landscape meets threshold
+
+https://gerrit.wikimedia.org/r/110625",1391201166,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gjdaipusi2pbcwygi4nx,task_subcomment,NA
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"http://googlewebmastercentral.blogspot.com/2011/03/mo-better-to-also-detect-mobile-user.html has a few ideas.
+
+Kenan suggests if the diagonal length of the screen is greater than 5.1 inches than we should assume tablet.",1390344876,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gjdaipusi2pbcwygi4nx,task_subcomment,NA
+VisualEditor only loads in alpha in landscape mode on an iPad mini,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1603",1389207028,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gjdaipusi2pbcwygi4nx,task_subcomment,NA
+Enable VisualEditor in all namespaces,"At some point VisualEditor should be enabled in the remaining namespace.
+
+I've seen a few requests for it, so this tracking bug will also provide an easy answer for why it isnt feasible now. e.g.
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(proposals)&oldid=589149415#VE_on_Wikipedia:_namespace
+",1389178800,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dahdfluva5saanqyyruw,task_description,invalid
+Enable VisualEditor in all namespaces,"(In reply to comment #0)
+> At some point VisualEditor should be enabled in the remaining namespace.
+
+{{cn}} :-)
+
+Right now I believe that VE is enabled on Wikipedias like enwiki in all namespaces except:
+
+1. the Talk namespaces;
+2. the Project namespace (Wikipedia:);
+3. the Lua namespace (Module:);
+4. the Template namespace; and
+5. the MediaWiki namespace.
+
+There are some (related) reasons for these:
+
+1. We don't ever intend for VisualEditor to be a good tool for editing signed content; the goals of a content editor with indenting and insertion do not mesh with those of a discussion editor. Instead, Flow will provide a VisualEditor surface for commenting in a proper system that makes sense. Enabling VE for talk namespaces on the WMF cluster is a WONTFIX from my point of view.
+
+2. The Project namespace contains a great deal of signed content, and so is not currently appropriate for VisualEditor per the reasoning above. Once Flow is fully up and running, switching VisualEditor on for the remaining (non-discussional) content is just a matter of flicking a switch. However, the point where Flow has replaced all Project namespace uses of signed content is probably a long way away.
+
+3. Lua code already has its own editor (quite why it has its own namespace instead of sitting as a ContentHandler object in the MediaWiki namespace like CSS and JS I don't know); VE doesn't add anything there.
+
+4. Templates are messy agglomerations of partial wikitext and lots of transclusion calls. I'm not sure VE would shine at its best here. We could enable it if you really think it would be useful (and can show community approval), though…
+
+5. Similarly, MediaWiki messages often contain messy partial wikitext (let alone partial HTML), and we are after all trying to discourage its use.
+
+
+
+On the particular ""blocking"" bugs:
+
+* bug 48429 – I don't see how this prevents VE from being deployed to further namespaces; it's mainly a problem in the content namespace (where it's already deployed), and would be in discussions (where we're not going to deploy it).
+* bug 50172 – Again, I don't see how this prevents VE from being deployed to further namespaces, given that it's mainly a problem between content, Draft and User (where it's deployed now).
+* bug 51154 – Though this would be necessary for deploying to Talk namespaces, see above.
+* bug 51899 – I don't understand how this blocks VE from being deployed to further namespaces.
+* bug 52141 – Same here.
+* bug 59229 – Yet another reason why we don't want to enable VE in discussions.
+* bug 59885 – This is currently only a super-class for bug 48429, and is not actually blocking deployment to the Draft: namespace because that happened.
+
+Consequently, I'm going to remove the dependencies and close this bug as INVALID. Happy to re-open if I'm wrong, though. :-)",1389987954,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dahdfluva5saanqyyruw,task_subcomment,NA
+"VisualEditor:""NetworkError: 404 Not Found"" appears while creating a new page with VE in FireFox 25","Screenshot
+
+Steps to reproduce:
+
+1.Attempt to create a new page with VE in FireFox 25 in any way.For example:Type this URL:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Textnew&veaction=edit
+
+Observed Result:
+
+An error appears in the console:
+
+""NetworkError: 404 Not Found - http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Textnew&veaction=edit""
+index....on=edit
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12343}",1389124080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ufqs3dhnocvsaimspsxt,task_description,declined
+"VisualEditor:""NetworkError: 404 Not Found"" appears while creating a new page with VE in FireFox 25",Not occurring anymore on test 2,1389910433,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ufqs3dhnocvsaimspsxt,task_subcomment,NA
+"VisualEditor:""NetworkError: 404 Not Found"" appears while creating a new page with VE in FireFox 25","However, the page can be created even though the error appears.",1389124265,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ufqs3dhnocvsaimspsxt,task_subcomment,NA
+"VisualEditor: "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears while opening up Categories dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the Categories Dialog box from Settings>Categories
+
+Observed Result:
+The error "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears in the console.
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan7th&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12329}",1389122820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jf4ozwjh3vlshz4bzqkm,task_description,declined
+"VisualEditor: "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears while opening up Categories dialog box",Not appearing any more .Got fixed in wmf11,1389909731,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jf4ozwjh3vlshz4bzqkm,task_subcomment,NA
+"VisualEditor: "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears while opening up Categories dialog box","Created attachment 14259
+Settings>Page Settings
+
+**Attached**: {F12330}",1389213979,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jf4ozwjh3vlshz4bzqkm,task_subcomment,NA
+"VisualEditor: "" Uncaught TypeError: Cannot read property 'langlinks' of undefined "" appears while opening up Categories dialog box","The error also appears when user goes to Setting>Page Settings.
+Screenshot attached",1389213930,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jf4ozwjh3vlshz4bzqkm,task_subcomment,NA
+Removing a blank == <nowiki /> == section heading leaves a <nowiki /> and produces a dirty diff,"Intention:
+Remove an empty section heading created in a previous edit (bug 59647) by VisualEditor
+
+Steps to Reproduce:
+1. Select the empty section heading
+2. Press the delete/backspace key
+
+
+Actual Results:  
+The line went away.  However, a nowiki tag remained, and the first item in the list of categories was added to the last paragraph on the page, instead of remaining on its own line.
+
+Expected Results:  
+The section heading would go away.  Zero nowiki tags would be present.  Content above and below would not get smashed into a single line.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Celebrity_branding&diff=589156903&oldid=589156664",1388854020,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-e3i52jzvuvgyt4mfbiae,task_description,resolved
+Removing a blank == <nowiki /> == section heading leaves a <nowiki /> and produces a dirty diff,"This is because <nowiki /s> (unlike <nowiki>s) are ""meta"" items in the DOM
+rather than things VE can edit; merging with bug 56381.
+
+*** This bug has been marked as a duplicate of bug 56381 ***",1390023730,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-e3i52jzvuvgyt4mfbiae,task_subcomment,NA
+VE automatically cuts off certain characters,"On the page on mediawiki.org https://www.mediawiki.org/wiki/Manual:ISBN (check action=history) VisualEditor keeps removing certain characters after I try to use it to make changes to the page. An example is given at https://www.mediawiki.org/wiki/VisualEditor:Test
+
+Reproduction steps:
+1. Set up a new page using the following code
+<space><space><space><url><apostrophe>
+<newline><space><space><space>
+example text1
+
+example text2
+Where <space> is one hit of the spacebar and <url> could be any URL
+2. Modify other places in the text, such as ""example text2"".
+3. See the first character in ""example text1"" get cut off.
+4. Modify ""example text2"" again and see ""example text1"" get cut off again.
+
+Example permalink: https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&oldid=873656
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388796000,PHID-USER-uhn27l5qsridnw4vbhko,False,PHID-TASK-sb5pc5upei6lbqlstsbe,task_description,resolved
+VE automatically cuts off certain characters,Non-reproducible - most likely fixed.,1421790530,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-sb5pc5upei6lbqlstsbe,task_subcomment,NA
+VisualEditor:  Can't save page after simple editing,"Intention:
+Copyedit an article
+
+Steps to Reproduce:
+1. I italicized two words.  I cut two sentences (including links and one ref) and pasted them in a different place.
+2. I tried to save the page.
+
+
+Actual Results:  
+The ""Save"" button looks normal, but clicking on it does nothing.
+
+Expected Results:  
+That I could save the page.  When I re-opened the page in VisualEditor and made the same changes, it worked (https://en.wikipedia.org/w/index.php?title=Neuralgia&diff=589057635&oldid=580866827).
+
+Reproducible: Couldn't Reproduce
+
+Firefox 26
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388793420,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5i5trthg3bfis3yeyeyg,task_description,invalid
+VisualEditor:  Can't save page after simple editing,"Also, in cases like this where pressing things (buttons etc.) appear to have no affect, you should try checking the JS console for errors.",1414811783,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-5i5trthg3bfis3yeyeyg,task_subcomment,NA
+VisualEditor:  Can't save page after simple editing,"(Quoting WhatamIdoing from comment #0)
+> Reproducible: Couldn't Reproduce
+
+Invalid/worksforme from creation then...",1414811622,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-5i5trthg3bfis3yeyeyg,task_subcomment,NA
+"VisualEditor: [Regression] Checkbox ""Watch this page"" in save dialog unchecked even that page is watched","Checkbox ""Watch this page"" in save dialog unchecked even that page is watched
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388779620,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-dqr5vyv74wju5geh4nth,task_description,resolved
+"VisualEditor: [Regression] Checkbox ""Watch this page"" in save dialog unchecked even that page is watched",This was fixed in the re-write in early January; sorry for the slow triage.,1394063679,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dqr5vyv74wju5geh4nth,task_subcomment,NA
+"VisualEditor:""TypeError: response.visualeditor is undefined"" appears while opening up the dialog box for adding catagories","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in FireFox
+2.Click on the Categories button to open up the dialog box to add categories
+
+Observed Result:
+TypeError: response.visualeditor is undefined appears in the console
+
+See the screenshot attached
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/3rd_janff?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12794}",1388778720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vvjswcot4n4j42ahvoek,task_description,declined
+"VisualEditor:""TypeError: response.visualeditor is undefined"" appears while opening up the dialog box for adding catagories",Not appearing anymore.got fixed in wmf11,1389910015,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vvjswcot4n4j42ahvoek,task_subcomment,NA
+VisualEditor: edits correctly saved are missing on da.wp,"Intention:
+I used my userpage as a sandbox
+https://da.wikipedia.org/w/index.php?title=Bruger:Elitre_(WMF)&action=history,
+and the edits in which I tried to add references do not show up in the history,
+although I did manage to save them and also got the message that confirms this.
+
+(For the record, I was trying to reproduce
+https://da.wikipedia.org/w/index.php?title=F-35_Lightning_II&diff=prev&oldid=7409486
+and
+https://da.wikipedia.org/w/index.php?title=Enhedslisten&diff=prev&oldid=7414100
+, where there might be a connection between adding a reference and getting a
+duplicated infobox).
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388769060,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-uh22mktin45cgziwuwry,task_description,resolved
+VisualEditor: edits correctly saved are missing on da.wp,Alright!,1432727427,PHID-USER-vignevg3qewvdhgbbwuh,True,PHID-TASK-uh22mktin45cgziwuwry,task_subcomment,NA
+VisualEditor: edits correctly saved are missing on da.wp,"If you can't reproduce any longer, given how old the task is, feel free to close - it can be reopened if and when the need arises.",1432646739,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-uh22mktin45cgziwuwry,task_subcomment,NA
+VisualEditor: edits correctly saved are missing on da.wp,I can't duplicate this - adding references works fine and the edits show up in my history.,1432480626,PHID-USER-vignevg3qewvdhgbbwuh,True,PHID-TASK-uh22mktin45cgziwuwry,task_subcomment,NA
+VisualEditor: edits correctly saved are missing on da.wp,Reproducible: Always?,1421888114,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-uh22mktin45cgziwuwry,task_subcomment,NA
+VisualEditor:  Cutting and pasting internal links converts them to external links in Firefox,"Intention:
+Move a sentence to a diffeent place on the page.
+
+Steps to Reproduce:
+1. In Firefox, open a page containing existing [[links]] to other pages on the wiki.
+2. Cut one of them.
+3. Paste it in a different spot.
+
+Actual Results:  
+The link gets converted from [[Link]] into [http://en.wikipedia.org/wiki/Link].
+
+See https://en.wikipedia.org/w/index.php?title=User:Edgepedia/VE/S%26D&diff=588724142&oldid=588539903 and https://en.wikipedia.org/w/index.php?title=Silaum_silaus&diff=588803158&oldid=587979575  
+
+Expected Results:  
+The [[Link]] would remain an internal link.
+
+Reproducible: Sometimes
+
+One of these pages involved the {{sfn}} (shortened footnotes) template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388682000,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zwykrgbpiln6fvzmfzeo,task_description,resolved
+VisualEditor:  Cutting and pasting internal links converts them to external links in Firefox,"Merging with bug 58136.
+
+*** This bug has been marked as a duplicate of bug 58136 ***",1390024188,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zwykrgbpiln6fvzmfzeo,task_subcomment,NA
+Page redirects are not recognized by VisualEditor's link inspector,"1. Edit an article with VisualEditor
+2. Select a word for which a redirect exists (not an actual page)
+3. Click the ""link"" icon.
+
+EXPECTED
+
+Since a redirect exists, the link inspector shows the option in blue (since the link is functional). All the better if it is shown in italics, just like redirects are shown by MediaWiki in lists of pages.
+
+ACTUAL
+
+Redirects are ignored by the link inspector. They appear just as red as a missing string. This creates a lot of extra work having to search the string manually in another window.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50593
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50240",1388672340,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dvyukuw5fsuzum36qlzx,task_description,resolved
+Page redirects are not recognized by VisualEditor's link inspector,"Merging with bug 49502.
+
+*** This bug has been marked as a duplicate of bug 49502 ***",1390024134,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dvyukuw5fsuzum36qlzx,task_subcomment,NA
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","Intention:
+Click on a link within VisualEditor
+
+Steps to Reproduce:
+1. Open an existing page in a subpage (e.g., User:Example/Sandbox)
+2. Control-click on any [[link]] and copy the link
+3. Paste the link somewhere to see what it says
+
+
+Actual Results:  
+Instead of the expected link to en.wikipedia.org/wiki/Link, the user saw links to en.wikipedia.org/wiki/User:Username/Link.  When this intermittent problem was happening, then all links on the page would do it.  However, it only happened during some editing sessions/some days.
+
+
+
+Reproducible: Sometimes
+
+Firefox 26 on Windows 7, Vector skin.  Is intermittent there; could not be immediately reproduced in either Firefox or Safari on a Mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48915
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58314",1388619840,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gvtbr3mwdnel75bfmsye,task_description,resolved
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","
+
+*** This bug has been marked as a duplicate of bug 58314 ***",1395363345,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gvtbr3mwdnel75bfmsye,task_subcomment,NA
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","Change 119914 had a related patch set uploaded by Catrope:
+Hack around Parsoid's href prefixing in rendering new links
+
+https://gerrit.wikimedia.org/r/119914",1395363135,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gvtbr3mwdnel75bfmsye,task_subcomment,NA
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","
+
+*** This bug has been marked as a duplicate of bug 58314 ***",1395344109,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gvtbr3mwdnel75bfmsye,task_subcomment,NA
+"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too","The brilliant ""Codename Lisa"" has figured out how to reproduce it consistently:
+
+1. Open a user subpage.
+2. Create a new link to an article on main space, e.g. [[Link]]
+3. Control-click on the link and copy it (or open the link in a new window)
+4. Discover that the link leads to [[User:YOURUSERNAME/Link]].
+
+More interestingly:
+
+1. Open a user subpage.
+2. Create a new link to an article on main space, e.g. [[Link]].
+3. Control-click on the link and copy it (or open the link in a new window)
+4. Save the page.
+5. Re-enter edit mode.
+6. Control-click on the same link again.
+7. Discover that the link now leads to [[Link]].
+
+Expected result:
+
+In both steps 3 and 6, the article must open at [[Link]], not at [[User:Username/Link]].
+
+Actual result:
+
+In step 3, a subpage with the same {{SUBPAGENAME}} as the link name opens. Step 6 is always successful. Pre-existing links open correctly.",1388634535,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gvtbr3mwdnel75bfmsye,task_subcomment,NA
+VisualEditor:Clear formatting removes the link from a text,"Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text  
+3.Apply some formatting from the formatting menu in the toolbar for example:
+Bold/Italic/Superscript
+4.Also apply a link on the text
+5.Now from the formatting menu select the ""Clear formatting"" option
+
+Observed Result:
+
+Along with all the text formatting, the link applied on the text also gets removed.
+It is better if Clear formatting only removes the text formatting not the link applied because that is not part of text formatting options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388609640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wsp5xk3lssgxslzaamko,task_description,resolved
+VisualEditor:Clear formatting removes the link from a text,"
+
+*** This bug has been marked as a duplicate of bug 51757 ***",1390025103,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wsp5xk3lssgxslzaamko,task_subcomment,NA
+"VisualEditor:Cannot go to the next line of an article after copy-paste of an hiero as the error ""TypeError: outermostNode is null"" appears","TypeError
+
+Steps to reproduce:
+
+1.Open a page with VE which contains a hiero
+2.Copy the hiero
+3.Open another page in FireFox with VE
+4.Paste the heiro
+5.Save the page
+6.Reopen the page and Press enter to go to the next line after the hiero
+
+Observed Result:
+Cannot go to the next line of an article after copy-paste of an hiero.The following error appears in the console:
+ 
+TypeError: outermostNode is null
+
+	
+
+...documentModel,selection.from,'\n');}else{node.traverseUpstream(function(node){if...
+
+load.p...4146Z&* (line 261)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12558}",1388272560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ok75mzddmda57d6nn6kk,task_description,resolved
+"VisualEditor:Cannot go to the next line of an article after copy-paste of an hiero as the error ""TypeError: outermostNode is null"" appears",This looks like we fixed it ages ago.,1442271794,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ok75mzddmda57d6nn6kk,task_subcomment,NA
+"VisualEditor:Cannot go to the next line of an article after copy-paste of an hiero as the error ""TypeError: outermostNode is null"" appears","Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=28th_decemberff&veaction=edit",1388272698,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ok75mzddmda57d6nn6kk,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","Screenshot of the error
+
+I have got this error several times in Betalabs recently,it happens if I keep VE open for a while for a page and then do some more edit and hit the ""Save Page"" button.
+I was still logged in to the previous session when this error appeared.
+
+""TypeError :this.timings is undefined ""
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12542}",1388267400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bexcdxbi3u4bthv7sscm,task_description,resolved
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","This was caused by a call to `.this.events.track()` in a detached way, which means `this` isn't bound and `ArticleTargetEvents` members like `timings` would not be found. This has since been fixed (based on the current code), though I can't find the exact commit.",1495794415,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while",Is this still occurring?,1439321337,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","Whoops, sorry, you're right!
+
+I use Firefox 26.0 on Ubuntu 12.04 LTS.",1389280808,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","(In reply to comment #1)
+> Happens frequently in Firefox under Ubuntu too
+
+Version information welcome, in general (don't know which version of Firefox is shipped on which version of Ubuntu).",1389263927,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor:""TypeError :this.timings is undefined ""appears while attempting to save a page which was open for a while","Happens frequently in Firefox under Ubuntu too, I have to click the ""Save"" twice to get it to actually save.",1389223764,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-bexcdxbi3u4bthv7sscm,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Selecting the whole line
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text to apply the paragraph format ""Preformatted"".Select the text in a way so that it selects the whole line.Check the screenshot of selection to better understand.
+
+3.Now select the option preformatted from paragraph styling options
+
+Observed Result:
+The Preformatted option gets applied to the other following text/element even though they are not selected.
+
+If the selection is done such way that it spans multiple empty lines then the preformatted options gets applied to those empty lines too.
+
+See the screenshots attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/28th_december
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12538}",1388266140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vgvl47jspv2pkkjrsfci,task_description,invalid
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","The selection of the following line is different than selecting the text on the line. If you choose to select just the text, you will get the behavior you are looking for. If you select the line and it's break (or empty lines after it) then you will get the behavior you are reporting as a bug.
+
+This is not a bug, it's doing exactly what it should. However, it may be valuable to revisit how we can better communicate what is selected and how to achieve the desired result to the user.
+
+Unfortunately, we have limited control over selection because we use ContentEditable, which is provided by the browser. The selection of a line and it's break may be something we can disable, but likely there will be negative effects on user experience and browser compatibility.
+
+Marking as invalid, since this is not a bug, but a known feature. I'm happy to discuss the UX impact of this feature and possible changes that could improve the situation on a different, enhancement, bug.",1391810383,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Sorry, I think I could not explain it properly in my steps.The issue was not about applying the format on the whole line rather on an immediate following line which was not selected.
+
+For example the content of a page is as follows:
+
+The text
+another text
+
+
+
+Not selected text
+
+
+Now if you select ""the text"" and ""another text"" but stop the selection just above the line ""Not Selected text"" and apply the format, it gets applied to ""Not Selected text""
+
+So, I am reopening the bug again as it is a different issue.",1390334416,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Yes, content formatting applies to the line(s) selected, not the text selection. This is by design (rather than splitting the text). Closing as WONTFIX, but happy to discuss if someone things we should split instead.",1390022822,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Created attachment 14184
+Observed Result
+
+**Attached**: {F12541}",1388266232,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection","Created attachment 14183
+Selecting multiple lines
+
+**Attached**: {F12539}",1388266192,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vgvl47jspv2pkkjrsfci,task_subcomment,NA
+VisualEditor:  List formatting not applied unless there is a blank line between items,"Intention:
+Turn a list of seven single-spaced items into a properly formatted list.
+
+Steps to Reproduce:
+1. Start with a page that contains a list of items that do not have blank lines between them.
+
+2. Open VisualEditor and select all the items.
+
+3. Click the 'list' button.
+
+Actual Results:  
+Only the first item is given list formatting.
+
+If some items are double-spaced and others are not, then double-spaced items are given list formatting, and any items without a blank line above them (except the first item, which always becomes list-formatted) is left as a plain paragraph rather than being formatted as a list item.
+
+Expected Results:  
+All the items would be given list formatting.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=587947827&oldid=587947700",1388168880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lowf6tecq6p7hjj3ouia,task_description,duplicate
+VisualEditor:  List formatting not applied unless there is a blank line between items,"At https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=587948540&oldid=587948443 you can see the 'workaround'.  This wikitext:
+
+* Monday is washing day.
+Tuesday is ironing day.
+Wednesday is mending day.
+Thursday is marketing day.
+Friday is cleaning day.
+Saturday is baking day. 
+
+displays like this in view mode:
+
+* Monday is washing day.
+Tuesday is ironing day. Wednesday is mending day. Thursday is marketing day. Friday is cleaning day. Saturday is baking day. 
+
+and displays like this within VisualEditor:
+
+* Monday is washing day.
+Tuesday is ironing day.↵Wednesday is mending day.↵Thursday is marketing day.↵Friday is cleaning day.↵Saturday is baking day. 
+
+If you select the subsequent items (Tuesday through Saturday), and click the button to apply list formatting, then only the ""Tuesday"" line acquires list formatting.  This looks in VisualEditor like this:  
+
+* Monday is washing day.
+* Tuesday is ironing day.↵Wednesday is mending day.↵Thursday is marketing day.↵Friday is cleaning day.↵Saturday is baking day. 
+
+If you save and re-open, you see this:
+
+* Monday is washing day.
+* Tuesday is ironing day.
+
+Wednesday is mending day.↵Thursday is marketing day.↵Friday is cleaning day.↵Saturday is baking day. 
+
+and the wikitext is this:
+
+* Monday is washing day.
+
+* Tuesday is ironing day.
+
+Wednesday is mending day.
+Thursday is marketing day.
+Friday is cleaning day.
+Saturday is baking day. 
+
+(Notice the HTML-list-formatting-breaking unwanted blank line between Monday and Tuesday.)
+
+Selecting the ""↵"" and hitting return produces the desired list.",1388169341,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lowf6tecq6p7hjj3ouia,task_subcomment,NA
+VisualEditor:500 (Internal Server Error) appearing while creating a link on betalabs,"Steps to reproduce:
+
+1.Open the editor for a page
+2.Create a link
+
+
+Observed Result:
+There is no suggestion appearing for the link creation and also in the console the error 500 (Internal Server Error) appearing
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388081580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-upb3ctljk2bwd7r3gsy3,task_description,declined
+VisualEditor:500 (Internal Server Error) appearing while creating a link on betalabs,This issue is not appearing anymore,1388167884,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-upb3ctljk2bwd7r3gsy3,task_subcomment,NA
+VisualEditor:500 (Internal Server Error) appearing while creating a link on betalabs,"There is a similar error appearing while adding media files to the page too.
+
+The error is as following:
+GET http://en.wikipedia.beta.wmflabs.org/w/api.php?callback=jQuery1830288604790…imit=15&gsroffset=0&prop=imageinfo&iiprop=dimensions%7Curl&iiurlheight=150 500 (Internal Server Error) load.php:128",1388082003,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-upb3ctljk2bwd7r3gsy3,task_subcomment,NA
+VisualEditor:500 (Internal Server Error) appearing while creating a link on betalabs,"Created attachment 14171
+Screenshot of the error
+
+**Attached**: {F12356}",1388081695,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-upb3ctljk2bwd7r3gsy3,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"I know this could be my fault, but I checked everything and it looks like it's a bug. Please correct me if I am wrong.
+
+Whenever I click the edit button the webpage does nothing. I see from the javascript debugger that the code stops at this line:
+
+return typeof jQuery !== ""undefined"" && (!e || jQuery.event.triggered !== e.type) ? jQuery.event.dispatch.apply(eventHandle.elem, arguments) : undefined;
+
+Any clues?
+
+I checked parsoid, tried creating a new settings file with minimal options, upgraded to latest trunk version both core and visualeditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1388002080,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_description,invalid
+Edit button not working -  empty /lib folder after downloading VE extension,"(In reply to comment #8)
+> When you download the VE extension, the lib folder is empty. (well, only an
+> empty subfolder). This is the cause.
+The empty folder is a submodule. Run 'git submodule update --init' to download it, and 'git submodule update' to update it after running git pull.",1389632091,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"When you download the VE extension, the lib folder is empty. (well, only an empty subfolder). This is the cause.",1389629778,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,Is there anything relevant in the Apache error log (could be folder/file access permissions)? Or in the debug log (see https://www.mediawiki.org/wiki/Manual:How_to_debug#Setting_up_a_debug_log_file )?,1389629712,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"Screen shot of console errors
+
+**Attached**: {F12331}",1389629299,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"**sumanah** wrote:
+
+Mc128k in #mediawiki just now confirmed that s/he has tried upgrading to the latest git master of VE and the bug still occurs.",1389629233,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"Adding more infos: debugging shows many 404 errors, and the lib/ve/ folder is empty. Something went very wrong with some git merge I think.",1388443150,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"I tried installing a clean mediawiki with only VE with a local sqlite database. Same issue, not even picked my config file, made one new.",1388273711,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,"It’s a private wiki, but VE should work even with readonly access (at least it worked before) by entering ?veaction=edit at the end of the URL. I tried firefox and Safari for Mac.
+
+This worked and now it doesn’t: http://wiki.mc128k.info/index.php?title=Test&veaction=edit
+
+I also noticed that if I click edit from the read tab it does nothing, if I click edit from the edit source tab it changes the URL, but nothing again.
+
+Thanks.",1388020068,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+Edit button not working -  empty /lib folder after downloading VE extension,Any link to reproduce the problem? Which browser(s) does this happen with?,1388002194,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rafw5v7fpv6llvfw3itz,task_subcomment,NA
+VisualEditor:The page alignment of the articles in betalabs is appearing more towards left,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page with editor.
+2.Add some content and image
+3.Save the page
+
+Observed Result:
+The content of the page is appearing more condensed and all the images are no more right aligned.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12290}",1387918680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-36ttyeifxhhwq5q4jnq3,task_description,resolved
+VisualEditor:The page alignment of the articles in betalabs is appearing more towards left,This was the ill-advised changes to the Typography Refresh update.,1439321255,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-36ttyeifxhhwq5q4jnq3,task_subcomment,NA
+VisualEditor:The page alignment of the articles in betalabs is appearing more towards left,This is happening on test2 too for both Chrome and FireFox,1390429043,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-36ttyeifxhhwq5q4jnq3,task_subcomment,NA
+VisualEditor:The page alignment of the articles in betalabs is appearing more towards left,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/Link_to_catapult",1387918821,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-36ttyeifxhhwq5q4jnq3,task_subcomment,NA
+VisualEditor:Betalabs is not loading properly in Chrome 26.0.1410.65,"screenshot
+
+I was trying to open some page on betalabs , it appears that none of the resources are loading properly.
+
+Getting some errors like following while attempting to login:
+Failed to load resource https://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=…m%7Cskins.common.interface%7Cskins.vector.styles&only=styles&skin=vector&*
+Failed to load resource https://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*
+Failed to load resource https://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*
+Failed to load resource https://upload.beta.wmflabs.org/wikipedia/en/b/bc/Wiki.png
+Failed to load resource https://bits.beta.wmflabs.org/static-master/skins/vector/images/search-ltr.png?303-4
+Failed to load resource https://bits.beta.wmflabs.org/images/wikimedia-button.png
+Failed to load resource https://bits.beta.wmflabs.org/static-master/skins/common/images/poweredby_mediawiki_88x31.png
+
+Please see the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12273}",1387905720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qcobbntfbebu2v6aryi,task_description,resolved
+VisualEditor:Betalabs is not loading properly in Chrome 26.0.1410.65,"Beta bits cluster issues, now fixed.",1390025257,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7qcobbntfbebu2v6aryi,task_subcomment,NA
+VisualEditor:Betalabs is not loading properly in Chrome 26.0.1410.65,"Before facing this issue , I was prompted with warning of server's certificate not trusted, after proceeding anyway its using https protocol to load the pages.",1387906203,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qcobbntfbebu2v6aryi,task_subcomment,NA
+VisualEditor:Betalabs is not loading properly in Chrome 26.0.1410.65,"The page I tried to open was: https://en.wikipedia.beta.wmflabs.org/wiki/Link_to_catapult
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5",1387905798,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qcobbntfbebu2v6aryi,task_subcomment,NA
+VisualEditor:  Clicking on parameters in the reference dialog box selects the wrong parameter,"Intention:
+Add a citation template
+
+Steps to Reproduce:
+1. Choose Insert > Reference
+
+2. Choose Insert > Transclusion
+
+3. Type ""Cite web"" into the box. Hit return twice.
+
+4. Click ""URL access date"" to add that parameter to the list. Cursor jumped back to ""Add parameter"" (not unreasonable; you might want to add lots of parameters before filling any of them in).
+
+5. Click ""URL access date"", which is now the first item in the left-hand column's list of parameters, so I can add today's date to my reference. Cursor jumped back to ""Add parameter"" (definitely unreasonable).
+
+6. Repeat that step as many times as you feel like.
+
+7. Give up and click on the second parameter, which is ""Source title"". Cursor jumped to the parameter box for ""URL access date"".
+
+8. Click on the third parameter in the list, which is ""URL"". Cursor jumped to the parameter box for ""Source title"". The only way to fill in any information for the last parameter in the list is to scroll down the list in the right-hand column.
+
+9. Read the article on [[:en:Fencepost error]].  
+
+
+
+Expected Results:  
+That clicking on the second parameter would actually take me to the second parameter, not to the first one.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1387846800,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rfypkehjlixpt65ao4mm,task_description,resolved
+VisualEditor:  Clicking on parameters in the reference dialog box selects the wrong parameter,This was fixed in gerrit 99749.,1390023047,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rfypkehjlixpt65ao4mm,task_subcomment,NA
+"VisualEditor:After deleting a reference list along with reference, the order of the first reference does not get deleted in FireFox 25","Selecting the reference with reference list
+
+Steps to reproduce:
+
+1.Open a page which has reference and reference list with VE on FireFox25
+2.Select the reference and the reference list and press delete
+3.Save the page
+
+Observed Result:
+
+In Edit mode the order (1.) remains in the page.However, in the read mode the order will not appear.In edit source mode , there is a # appearing.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/The_title
+
+The wikitext of the page before deleting:
+reference<ref>refererence</ref>
+<references />
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12253}",1387839660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-slqzyalxfqafkznbvky4,task_description,declined
+"VisualEditor:After deleting a reference list along with reference, the order of the first reference does not get deleted in FireFox 25","Unfortunately closing this Phabricator task as no further information has been provided. If anyone can still reproduce in a recent browser version, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks!",1589143295,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-slqzyalxfqafkznbvky4,task_subcomment,NA
+"VisualEditor:After deleting a reference list along with reference, the order of the first reference does not get deleted in FireFox 25",Is this still occurring?,1439321198,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-slqzyalxfqafkznbvky4,task_subcomment,NA
+VisualEditor: A lock icon is appearing in all references for a reference list in Firefox in test2,"screenshot of the lock icon appearing
+
+Steps to reproduce:
+
+1.Open the editor for a page which contains some references and a reference list
+
+2.Copy the references and the reference list and paste into anothe rVE
+
+3.Save the page
+
+Observed Result:
+
+A lock icon is appearing beside the reference for a reference list in FireFox in test2 
+Page:https://test2.wikipedia.org/wiki/23rdtemplatepaste
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12241}",1387833720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nhlyafdpxr6icar37fw4,task_description,invalid
+VisualEditor: A lock icon is appearing in all references for a reference list in Firefox in test2,This is because the links are to HTTPS sites.,1401472953,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nhlyafdpxr6icar37fw4,task_subcomment,NA
+VisualEditor:Cannot create a new page using VE on FireFox25 in test2,"the screenshot of the error
+
+Steps to reproduce:
+
+1.Open the editor for a existing VE
+2.Create a link to a new page
+3.Click on the link to open that new page in the same or a new tab
+4.Click on the Create button
+
+Observed Result:
+
+Ve does not load,An error is shown on the console:
+TypeError: list[firingIndex] is undefined
+	
+
+....split(core_rspace),function(_,flag){object[flag]=true;});return object;}jQuery....
+
+load.p...025514Z (line 12)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12227}",1387830960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2yxmskm3croyyjfnp4wh,task_description,declined
+VisualEditor:Cannot create a new page using VE on FireFox25 in test2,"Yes,it happens for every page including new page when I switch from wikitext editor to VE.
+But yes, it does not happen when I visit the page in read mode first by typing the address to go to the link directly",1387835318,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2yxmskm3croyyjfnp4wh,task_subcomment,NA
+VisualEditor:Cannot create a new page using VE on FireFox25 in test2,I cannot reproduce this in quick testing (FF 25.0.1/Mac 10.9.1) – is this on every new page when transitioning from the wikitext editor to VE? Does it happen if you visit the page first in read mode? What about if you go directly to the link by typing in the address by hand?,1387834060,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2yxmskm3croyyjfnp4wh,task_subcomment,NA
+VisualEditor:Image is appearing as link after copy paste from another VE in FireFox,"Screenshot
+
+Steps to reproduce:
+
+1.Open the Editor for a page which contains an image with FireFox
+
+2.Copy the image and paste it into another VE
+
+3.Save the page.
+
+Observed Result:
+After copy paste before saving it appears as an uneditable object in VE .After saving the image appears as a link in the page as follows:
+
+In read mode and Edit mode: 
+
+link=https://test2.wikipedia.org/wiki/File:158869_at_Truro.JPG|200x200px
+
+In Edit Source mode:[[undefined|link=https://test2.wikipedia.org/wiki/File:158869_at_Truro.JPG|200x200px]]
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also:**
+{T78026}
+
+**Attached**: {F12212}",1387825020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jsdvuoacpjes6iw6v4vx,task_description,resolved
+VisualEditor:Image is appearing as link after copy paste from another VE in FireFox,This has probably been fixed for a while.,1426872997,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jsdvuoacpjes6iw6v4vx,task_subcomment,NA
+VisualEditor:Image is appearing as link after copy paste from another VE in FireFox,This is occurring in mw.org now,1389381557,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jsdvuoacpjes6iw6v4vx,task_subcomment,NA
+VisualEditor:Image is appearing as link after copy paste from another VE in FireFox,"Created attachment 14161
+Before Saving
+
+**Attached**: {F12213}",1387825068,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jsdvuoacpjes6iw6v4vx,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"In http://en.wikipedia.beta.wmflabs.org/
+Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387819560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-patmtmusp6dirpvlwuru,task_description,resolved
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"
+
+*** This bug has been marked as a duplicate of bug 58897 ***",1387841449,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"This was an artifact of today's issue with database connections, resolved after restarting apaches on beta",1387838675,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,The issue is not happening now.,1387838546,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"okay will verify it, once bug 58897 gets resolved.",1387821592,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"On the few times when bug 58897 isn't having an effect so I can see the page, it seems to work for me right now…",1387820845,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>,"Created attachment 14158
+screenshot
+
+**Attached**: {F12188}",1387819632,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-patmtmusp6dirpvlwuru,task_subcomment,NA
+VisualEditor: Support <code> elements for text styling.,"Support adding and removing <code> elements.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387581000,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-744uhoqz2qaraesrqoyi,task_description,resolved
+VisualEditor: Support <code> elements for text styling.,This was done in July last year.,1394480631,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-744uhoqz2qaraesrqoyi,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,"I tried to give L10n-bot the correct access rights, but failed; I've removed my attempts again. Please give L10n-bot the rights at URL so that it can merge its own submits, like in MediaWiki repos.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**URL**: https://gerrit.wikimedia.org/r/#/admin/projects/wikimedia/wikimania-scholarships,access",1387579080,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-eumorghlixcu2bg3vnve,task_description,resolved
+Allow L10n-bot to merge in several Gerrit repos,"Nothing new or different. Give Code Review / Verified / Submit to the l10n-bot group.
+
+I did it in VisualEditor/* and oojs/* so those repo hierarchies will be fine from now on.",1391531703,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,"Thanks, Chad. Can you explain what you did? This may make a future occurrence ore easy to resolve.",1391530424,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,Done.,1391529275,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,"The same issue exists for the following repos:
+* VisualEditor/VisualEditor
+* oojs/ui",1391512362,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+Allow L10n-bot to merge in several Gerrit repos,What's keeping this from being addressed?,1391512133,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-eumorghlixcu2bg3vnve,task_subcomment,NA
+VisualEditor:Math functions are getting overlapped with previous line,"Screenshot
+
+Steps to reproduce:
+
+1.Open the editor for a page
+2.Add a text or a link or a numbered list
+3.Copy a math formula from another VE
+4.Paste it into the next line after step 2
+5.Save the page
+
+Observed Result:
+The math formula is  getting merged with the previous element
+
+Please check :http://en.wikipedia.beta.wmflabs.org/wiki/Mathpaste20th
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12767}",1387576980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p7dsmh4gtfhvebckg5yk,task_description,declined
+VisualEditor:Math functions are getting overlapped with previous line,Not occurring anymore.Changing the status to Resolved-WorksforMe,1389047494,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p7dsmh4gtfhvebckg5yk,task_subcomment,NA
+VisualEditor:Math functions are getting overlapped with previous line,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.6
+OS:MAC OS X 10.8.5",1387577171,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p7dsmh4gtfhvebckg5yk,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Steps to reproduce:
+
+1.Open the editor
+2.Create a numbered list with 4 items.For example:
+# item 1
+# item 2
+# item 3
+# item 4
+
+3.Now place the cursor at the end of item 2 and press enter
+4.Add a new item 3( it gets added properly)
+5.Now place the cursor just before item 1 and press enter to move it to the next line 
+6.Type a new item1 in first line
+7.Delete the new item
+
+Observed Result:
+
+The order  (1.) does not get deleted.In read mode the list appears like this:
+ 
+ 1.
+ 2. item 1
+ 3. item 2
+ 4. new item 3
+ 5. new item 4
+ 6. item 3
+ 7. item 4 
+
+After saving, in read mode the list appears as follows:
+
+1.item 1
+2.item 2
+3.new item 3
+4.new item 4
+5.item 3
+6.item 4
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387567980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_description,declined
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"I think that this is ""expected"" behaviour (blank <li>s don't show in read mode, but do in wikitext and VE), confusingly.",1394504624,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Created attachment 14151
+In read mode
+
+**Attached**: {F12756}",1387568343,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Created attachment 14150
+In VE edit mode
+
+**Attached**: {F12755}",1387568299,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Created attachment 14149
+In edit source mode
+
+**Attached**: {F12754}",1387568252,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode,"Test Environment:https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Another_page20th",1387568172,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cnlgzxw2fzybmpp3j5xx,task_subcomment,NA
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","**Author:** `jhall`
+
+**Description:**
+When it is feeling uncooperative, SauceLabs will report test results like this from a Chrome/Linux test of some or other aspect of Visual Editor:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/222/testReport/(root)/VisualEditor%20general%20text%20markup%20features/VisualEditor_general_markup__outline_example_____Underline____u_This_is_a_new_line__u____/
+
+The browser response at the time of the failure was this helpful message:
+
+https://saucelabs.com/jobs/58b6d51fe48b4eaf845939c1f3d6de20/0005screenshot.png
+
+The Selenium log captured by SauceLabs reports:
+
+[22.414][FINE]:     Command received (/session/7a6fd70f2bc2c63555f62ec29cc9d507/element) with params {
+   ""using"": ""xpath"",
+   ""value"": "".//span[contains(concat(' ', @class, ' '), ' oo-ui-iconedElement-icon oo-ui-icon-text-style ')]""
+}
+
+[22.414][FINER]:    Waiting for all views to stop loading...
+[22.414][FINER]:    Done waiting for all views to stop loading
+[22.447][FINER]:    Waiting for all views to stop loading...
+[22.447][FINER]:    Done waiting for all views to stop loading
+[22.447][WARNING]:  Command finished (/session/7a6fd70f2bc2c63555f62ec29cc9d507/element) with response {
+   ""sessionId"": ""7a6fd70f2bc2c63555f62ec29cc9d507"",
+   ""status"": 7,
+   ""value"": {
+      ""message"": ""The element could not be found""
+   }
+}
+
+…while the Sauce Log records several HTTP 500 conditions similar to this (I will attach the complete Sauce Log to this bug):
+
+    {
+        ""HTTPStatus"": 500, 
+        ""between_commands"": 0.0773019790649414, 
+        ""duration"": 0.036900997161865234, 
+        ""in_video_timeline"": 19.80928897857666, 
+        ""method"": ""POST"", 
+        ""path"": ""element"", 
+        ""request"": {
+            ""using"": ""xpath"", 
+            ""value"": "".//span[contains(concat(' ', @class, ' '), ' oo-ui-iconedElement-icon oo-ui-icon-text-style ')]""
+        }, 
+        ""result"": {
+            ""message"": ""The element could not be found""
+        }, 
+        ""screenshot"": null, 
+        ""statusCode"": 7
+    },
+
+Need to investigate and figure out what is going on here...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387566480,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oypbzk3jpzff5cgsiva7,task_description,invalid
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","**jhall** wrote:
+
+Changing bug status since task in still WIP.",1388083932,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oypbzk3jpzff5cgsiva7,task_subcomment,NA
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","Change 103058 abandoned by Jhall:
+[Browser test] WIP Add session teardown steps
+
+Reason:
+Abandoning this change after a pairing session with Chris McMahon, since we settled on change #103566 as a better solution for the root problem.
+
+https://gerrit.wikimedia.org/r/103058",1387907723,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oypbzk3jpzff5cgsiva7,task_subcomment,NA
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","Change 103058 had a related patch set uploaded by Jhall:
+[Browser test] Add session teardowns steps
+
+https://gerrit.wikimedia.org/r/103058",1387580211,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oypbzk3jpzff5cgsiva7,task_subcomment,NA
+"Investigate ""No data received"" errors from VE Chrome tests running via SauceLabs","**jhall** wrote:
+
+Complete Sauce Log
+
+**Attached**: {F12749}",1387566540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oypbzk3jpzff5cgsiva7,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"On fr.wp,
+NemesisIII usually copy/pastes titles of articles in the reference dialog.
+This led to this diff, https://fr.wikipedia.org/w/index.php?title=France_Roche&diff=prev&oldid=99244364, where the newly added link is among equal signs, as if its style was ""Page title"" rather than ""Paragraph"".
+
+When I tried to replicate this behavior,
+I got a slightly different result https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve&diff=99382715&oldid=99382337.
+Reference #2 is now... definitely different from the others (waaay bigger), and certainly not standard as it should be.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387465680,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_description,resolved
+VisualEditor: Reference dialog retains style of copy/pasted contents,"I've [[https://fr.wikipedia.org/w/index.php?title=Utilisateur%3ANeil_P._Quinn-WMF%2FTestcase%2FT60689&diff=114195603&oldid=114195075|tested this]] again using headlines from three different news sites, and the reference dialog now seems to correctly strip all rich formatting. Closing.",1429553616,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"I've [[https://fr.wikipedia.org/w/index.php?title=Utilisateur%3ANeil_P._Quinn-WMF%2FTestcase%2FT60689&diff=114195603&oldid=114195075|tested this]] again using headlines from three different news sites, and the reference dialog seems to correctly strip all rich formatting. Closing.",1429553604,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"NicoV, this bug is entirely about the reference dialog, so what you should do for refs is the only thing that we're talking about here.  So if ""manuals of style usually say that external links should not be in the text of the article, but as references"", then we SHOULD retain these links in the refs.",1392400957,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"Problem with this is and other design decisions in VE is that the exception is privileged over the most common situation.
+
+In most cases, you really don't want the formatting to be copied over like that when you're copying something from an external website:
+* italic, bold: probably ok
+* links: probably usually ok (and this is not really true, because manuals of style usually say that external links should not be in the text of the article, but as references or in an ""external links"" section)
+* everything else: usually not ok (I would say 99%), and even when it seems ok, it's not really a good idea. Why? Take the example of a different language: the notion should be kept in the end, but all wikis I know have defined a {{lang}} template to do that and discourage the use of <span lang=""xxx"">. And this is true for many things: even the links/italics/bold for a reference are usually handled by a template like {{cite web}} to have a consistent look&feel in wikipedia.
+
+Copying from an other page of wikipedia is an other subject: for this, copying the full wikimarkup would be usually good.",1392397248,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"There are good reasons to retain basic character formatting (e.g., italics) and linked URLs (e.g., the equivalent of [http://my.source.org Reliable Title]).  
+
+I suppose that font might be useful, if it has the effect of switching to a different language.  I'm just not sure that we'll encounter that.  <span lang=""jv-java""> of course should not get dropped, and LTR/RTL switches are critical.  Imagine a ref including both Arabic and a European language without this feature.",1392396305,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"(In reply to NicoV from comment #3)
+Precisely.",1392383608,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"I think keeping the formatting of a non-wiki contents is not really a good thing: every wiki has its own manual of style, to have a consistent look and feel in articles. There's almost no chance at all that a non-wiki contents will be formatted following the manual of style of the wiki.
+There's seldom use to keep font family, font size, color, ... from an external contents.",1392380611,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"I'm pretty sure it's working as intended, but I am not sure if it's helpful that it allows changing style to text (given it's a reference), and if there's a way to prevent that, because changing style to the single reference when you add it is not possible now.",1387482271,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor: Reference dialog retains style of copy/pasted contents,"This may be a case of 'working as designed':  Rich copying and pasting means that the style of the copied/pasted contents is retained.  This is a new feature, so users are surprised by this.  We don't want to break formatting for references:  titles should remain italicized, journal volumes should remain bolded, etc.  However, perhaps it would be possible to set the contents of all refs to ""Paragraph""?",1387481601,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-p2fgtkqsv3nbsvtion3a,task_subcomment,NA
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,"Steps to reproduce:
+
+1.Open the editor
+2.Add a Hieroglyphic
+3.When the cursor moves to the next line , add a heading and save the page
+
+Observed Result:
+The heading bar appears above the hiero where as the section edit options appear where the text of heading appears.The text styling for the heading changes to paragraph format.
+
+The wikitext resulting from these actions is:
+== <hiero>A
+</hiero>heading following hiero ==
+
+Found in:http://en.wikipedia.beta.wmflabs.org/wiki/Nonexist
+Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387400760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s6y4w7kahlei5ddylfmn,task_description,resolved
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,I can't reproduce this on Firefox 70.0b5 or Chrome 76.0.3809.132 on macOS 10.14.6.,1568144619,PHID-USER-cbjanejnwkkrbnj77d2d,False,PHID-TASK-s6y4w7kahlei5ddylfmn,task_subcomment,NA
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,Is this still occurring?,1439321145,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s6y4w7kahlei5ddylfmn,task_subcomment,NA
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,After adding the heading the cursor jumps to the beginning of the text in the first line of the document,1387486595,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s6y4w7kahlei5ddylfmn,task_subcomment,NA
+VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode,"Created attachment 14131
+screenshot
+
+**Attached**: {F12544}",1387400975,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s6y4w7kahlei5ddylfmn,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"Esperanto commonly uses some special characters.  The ""x-method"" of entering them (cx -> ĉ, gx -> ĝ, hx -> ĥ, jx -> ĵ, sx -> ŝ, ux -> ŭ (and the capital letters)) is already implemented in the Universal Language Selector and other MediaWiki software at https://doc.wikimedia.org/mediawiki-core/master/php/html/LanguageEo_8php_source.html launguages/classes/LanguageEO.php  
+
+VisualEditor should support the same method.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1387394340,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-y5w7khnzvllsehcslsmd,task_description,resolved
+VisualEditor:  Support x-method of entering special characters for Esperanto,"This is a duplicate of bug 49569.
+
+*** This bug has been marked as a duplicate of bug 49569 ***",1389025443,PHID-USER-w5a723w3wes6jd5wskgg,True,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"Ok I've confirmed that the ULS IME *doesn't* seem to work in current VE deployment.
+
+(This has replaced, or should replace, the old save-time transform...)
+
+James, is there a general issue with ULS IMEs working/not working in VE? Have we run into this issue for other languages? What can we do to help it work? Do we have to adapt the IME to work in VE particularly? Or is there currently no way for any of the ULS IMEs to work?",1389022794,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"Now on eo.wiki does not work such post-save transformation, see https://eo.wikipedia.org/w/index.php?title=Uzanto:KuBOT/provejo&diff=5371450&oldid=5333431 (should appear ""eĥoŝanĝo ĉiuĵaŭde"" both in page and in the edit summary).
+
+If ULS IME stuff just work it would be great - even another transform methods for Esperanto, already included in ULS, would work.",1387995512,PHID-USER-mld2htwndnaw3bpuiot3,True,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,Shouldn't the existing ULS IME stuff just work? Or does every one require custom support in VE?,1387479234,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"(In reply to comment #1)
+> What is this method? How does it work? It looks just like a basic post-save
+> transform - if so, that should already work with VisualEditor…
+
+It's an input method in jquery.ime. https://github.com/wikimedia/jquery.ime/blob/master/rules/eo/eo-x.js",1387407128,PHID-USER-w5a723w3wes6jd5wskgg,True,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+VisualEditor:  Support x-method of entering special characters for Esperanto,"What is this method? How does it work? It looks just like a basic post-save transform - if so, that should already work with VisualEditor…",1387400330,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-y5w7khnzvllsehcslsmd,task_subcomment,NA
+Italic text should not contain trailing spaces,"In VisualEditor, enter
+
+   one[space][Ctrl-I]two[space][Ctrl-I]three
+
+This will result in wiki text 
+
+   one ''two ''three
+
+but clearly
+
+   one ''two'' three
+
+was intended. I don't think a trailing (or leading?) space in italic/bold wikitext is ever appropriate.
+
+The fixed Bug 33108 is similar but deals with selected text.
+
+<editorial>
+I believe some of the hostility towards VE in the Wikipedia community results from issues like this: editors with long watchlists feel they have to clean up after many such VE edits.
+</editorial>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387321380,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-c3ineb5mdwoziw4jeqdo,task_description,resolved
+Italic text should not contain trailing spaces,"Merging with bug 52037.
+
+*** This bug has been marked as a duplicate of bug 52037 ***",1394501799,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c3ineb5mdwoziw4jeqdo,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","Right now we've a BetaFeatures component – https://bugzilla.wikimedia.org/buglist.cgi?component=BetaFeatures&product=MediaWiki%20extensions&list_id=259910 – but no single place to put bug reports about features that use BetaFeatures.
+
+Some of these have components of their own (e.g. MediaViewer) or even products (e.g. VisualEditor), but others don't (and probably won't).
+
+Right now, there's nowhere to raise a bug about e.g. Typography refresh that won't muddy up the bugs about BetaFeatures itself, as opposed to things that use it.
+
+Suggestions on better naming welcome. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387317120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_description,declined
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product",If features could provide preferred bug links that would be more useful.. Personally I just want to use talk pages for both of my features. I ignore the VectorBeta component. With respect to typography it's just not stable enough to warrant bugzilla bugs.,1387386327,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","The primary organization structure of Bugzilla is products and components which are mostly based on code repositories or code areas.
+
+(In reply to comment #6)
+> 1) People should not be expected to know from which extension beta features
+> come from so in the current scenario various bugs will be filed incorrectly.
+
+I'm happy to edit the BetaFeatures component description in Bugzilla to link to a wikipage that explains which beta feature is called how. https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures has links to ""Information"" and ""Discussion"" so you're free to add a link to corresponding Bugzilla components on the Information page. Or using the Bugzilla parameter of the {{Extension}} template.
+
+> Now I am seeing a flood of bugs filed under mobile from problems experienced
+> in the Beta Features environment field.
+
+Example bugs welcome so I can investigate plus if there are patterns I should improve documentation.",1387385235,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","Please reconsider or at least rethink the problem as there is a real problem here in my opinion.
+
+From my perspective:
+1) People should not be expected to know from which extension beta features come from so in the current scenario various bugs will be filed incorrectly.
+2) Beta features don't always plan to graduate to stable so are lower priority then the extensions that house them. For example - nearby pages is part of MobileFrontend.
+The purpose of the experiment was to explore whether such a feature was useful in desktop. If it is, it will need MediaWiki UI and a massive rewrite before being pushed to desktop.
+
+Now I am seeing a flood of bugs filed under mobile from problems experienced in the Beta Features environment field. These tend to not be helpful as I'm aware the code has issues when run in desktop.
+
+I would like some way of keeping these bugs separate from what I see as real bugs. I am very close to wanting to kill this beta feature because of this noise as I feel the bugs are intruding on the mobile teams core work which would be a huge shame. Please dont make me do this...",1387382627,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","(In reply to comment #1)
+> All BetaFeatures are currently parts of some extension, so the bugs should
+> probably be filed in the extensions, no?
+
+Yes. If extensions are missing I should create them (bug 58616, bug 58617, etc).",1387331868,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","So… we should just throw them in ""General"" and hope they get worked on? Lovely. :-(",1387318880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","Yeah, agreed with MatmaRex, this seems mighty silly. If anything, it wouldn't go under the Extensions product, because you're talking about something that *isn't* an extension, it's either only part of one or some sort of weird core betafeature.",1387317365,PHID-USER-nvavrb7ko66hv3xap6sb,True,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","(In reply to comment #0)
+> Right now, there's nowhere to raise a bug about e.g. Typography refresh that
+> won't muddy up the bugs about BetaFeatures itself, as opposed to things that
+> use it.
+
+Those should be filed against VectorBeta. Though, supposedly those styles are actually in core, so the bugs should be filed in core?
+
+(In reply to comment #1)
+> All BetaFeatures are currently parts of some extension, so the bugs should
+> probably be filed in the extensions, no?
+
+I agree.",1387317365,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"Add ""BetaFeatures feature"" component to ""MediaWiki extensions"" Bugzilla product","All BetaFeatures are currently parts of some extension, so the bugs should probably be filed in the extensions, no?",1387317239,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-tm5h6mdh2hlegrznd7pk,task_subcomment,NA
+"VisualEditor: can't submit/press ""save page"" button using return key","When I tab through the various input controls and highlight the ""save page"" button in VisualEditor, I can't seem to use the return key to submit the form/press the button. I'll upload a screenshot momentarily.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387246920,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-h5arfbwysxbybm7hujkv,task_description,resolved
+"VisualEditor: can't submit/press ""save page"" button using return key","Up-merging to the upstream issue.
+
+*** This bug has been marked as a duplicate of bug 62337 ***",1396380391,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h5arfbwysxbybm7hujkv,task_subcomment,NA
+"VisualEditor: can't submit/press ""save page"" button using return key","Created attachment 14117
+VisualEditor on mediawiki.org with ""save page"" button highlighted, 2013-12-16
+
+**Attached**: {F12370}",1387247043,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-h5arfbwysxbybm7hujkv,task_subcomment,NA
+VisualEditor: copying and pasting header results in non-breaking space being inserted,"Input text ([[mw:VisualEditor:What A]]):
+
+---
+=== test ===
+what is '''this''' i don't ''even''
+---
+
+I copy and paste this text from [[mw:VisualEditor:What A]] to [[mw:VisualEditor:What B]] and I end up with largely the same result, except an invisible non-breaking space is inserted before ""test"". If you view the HTML page source of [[mw:VisualEditor:What B]], it's trivial to spot:
+
+---
+<span class=""mw-headline"" id="".C2.A0test"">&#160;test</span>
+---
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387246800,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ki5ndhcsugxw2thwlhd4,task_description,resolved
+"VisualEditor: link inspector appears next to page title, pointing to what is an uneditable area of the page","1. Go to a non-existent page and edit it with VE
+2. Click to the right of the article title
+3. Click the link icon on the toolbar
+
+The link inspector appears next to the page title, pointing to what is an uneditable area of the page.
+
+Link creation works correctly, despite the incorrect location of the inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1387190940,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-crf7s6bmhldwret6sy4u,task_description,resolved
+"VisualEditor: link inspector appears next to page title, pointing to what is an uneditable area of the page",Seems to work correctly now.,1398733687,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-crf7s6bmhldwret6sy4u,task_subcomment,NA
+Adding diatrics to letters in defaultsort causes VisualEditor to belive the page was not changed.,"I ran into an issue with VisualEditor, when I tried to replace an letter with an diatric letter in defaultsort. VisualEditor would not activate the ""Save page"" button, making me unable to save the change. Also, I noticed, that if I would add some random letters to the page, after the defaultsort change, VisualEditor would still not activate the ""Save page"" button.
+
+Here is one of three nearly indentical tests where I found this issue. The other two where to test whether the bug was reproducable.
+# Change [[:is:Flokkur:Stjórnmál í Sádí-Arabíu]]
+# Open the More settings panel, and choose Page settings.
+# Sort the page as ""Sádí-Arabíu"" (without the hyphens).
+# Click apply changes
+# Notice that the ""Save page"" button does not activate.
+
+Expected behaviour: Should allow me to save the page, when changing an letter to an diatric letter. Adding text afterwards definatly should allow me to save the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387060200,PHID-USER-zrsacwdcrbgp2u32d5pr,False,PHID-TASK-lcm5zsufp2kobbnnphbv,task_description,declined
+Adding diatrics to letters in defaultsort causes VisualEditor to belive the page was not changed.,"I can no longer reproduce this bug.
+
+Closed as worksforme.",1388782680,PHID-USER-zrsacwdcrbgp2u32d5pr,False,PHID-TASK-lcm5zsufp2kobbnnphbv,task_subcomment,NA
+"VisualEditor:  Cursor misplaced while editing.  I click here, and it types over there.","Intention:
+Copyedit a sentence.  I clicked after the word ""elbow"" to add another phrase.
+
+
+Actual Results:  
+It typed my words in the middle of a sentence four lines lower.  The diff was correct, but did not include several of the last changes I made (e.g., adding paragraph breaks).  Also, in cutting and pasting another paragraph, the ref's contents were removed.
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387058460,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yht56d7rk34lqhlubcge,task_description,resolved
+"VisualEditor:  Cursor misplaced while editing.  I click here, and it types over there.",Seems to [[https://en.wikipedia.org/w/index.php?title=User%3ANeil_P._Quinn-WMF%2FTestcase%2FT60493&diff=657353327&oldid=657353041|work correctly now]]. Closing.,1429551450,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-yht56d7rk34lqhlubcge,task_subcomment,NA
+"VisualEditor:  Cursor misplaced while editing.  I click here, and it types over there.",The diff (what ended up being saved) is at https://en.wikipedia.org/w/index.php?title=Diffuse_large_B-cell_lymphoma&diff=586098843&oldid=582235478,1387058957,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yht56d7rk34lqhlubcge,task_subcomment,NA
+"VisualEditor:  Cursor misplaced while editing.  I click here, and it types over there.","Created attachment 14098
+Screenshot of the article after encountering the problem, but before saving
+
+Four places are marked in the image:
+
+(1) I split the paragraph as shown here, but this line break did not get saved.
+
+(2) I clicked above the '2' and started typing after ""elbow"".  The next few words should have been ""or a surgically implanted port"".  The words ""or a sur"" were visible on the screen at the time I saved, but did not appear in the diff.
+
+(3) The highlighted (blue) spot is where VisualEditor tried to put part of these words.  I have just 'undone' the addition of the text in the wrong paragraph.
+
+(4) The first thing I did in this article was to cut text out of the ==Treatment== section and use it to create a separate ==Research== section.  Ref #30 turned into <sup>[30]</sup> when I did this.  In addition to losing the refs, it may have added line breaks; they do not appear in the original wikitext, but I had to remove several before saving.
+
+The number of lines in between where I clicked to type at (2) and where it tried to put the words at (3) is approximately the same number of lines as what was moved to (4).
+
+**Attached**: {F12250}",1387058914,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yht56d7rk34lqhlubcge,task_subcomment,NA
+"""Edit"" tab not change to ""View source"" with protected template subpage","""Edit"" tab not change to ""Vew source"" with protected template subpage, see https://commons.wikimedia.org/wiki/Template:Delete/layout
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://commons.wikimedia.org/wiki/Template:Delete/layout",1386959040,PHID-USER-b27lopawgf2h6utuuqyi,False,PHID-TASK-eo43z5xddf6sg3om7sem,task_description,resolved
+"""Edit"" tab not change to ""View source"" with protected template subpage","So this is actually a duplicate report of a different, much older one :)
+
+*** This bug has been marked as a duplicate of bug 11700 ***",1386959666,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eo43z5xddf6sg3om7sem,task_subcomment,NA
+"""Edit"" tab not change to ""View source"" with protected template subpage","Actually, that was too quick. This also affects core with VisualEditor disabled. Sorry.",1386959536,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eo43z5xddf6sg3om7sem,task_subcomment,NA
+"""Edit"" tab not change to ""View source"" with protected template subpage","
+
+*** This bug has been marked as a duplicate of bug 53893 ***",1386959355,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eo43z5xddf6sg3om7sem,task_subcomment,NA
+"VisualEditor: Copying a template from one page to another: render is correct, but template is gone.","Let's copy the relatively simple {{irc}} template from 
+
+https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-12-04
+
+to
+
+https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-12-18
+
+1. Open both pages in Edit mode.
+
+2. Copy ""#wikimedia-meetbotconnect"" from one page and paste it in the other.
+
+EXPECTED
+
+The template is copied as i to the destination page.
+
+ACTUALLY
+
+If selecting only the text generated by the template, Ctrl-C seems to be not enough. Ctrl-V in the other page will still paste whatever you hadd in your clipboard before.
+
+If selecting the text of the template plus some extra text, then Ctrl-C does copy something, and Ctrl-V does paste a visually equivalent text.
+
+However, when checking the wikitext source of the page one can see that the original template has been rendered as HTML.
+
+See https://www.mediawiki.org/w/index.php?title=Architecture_meetings%2FRFC_review_2013-12-18&diff=841813&oldid=838192
+
+If this is part of a secret, long-term Parsoid plan to convert all template instances to HTML, fine. However, if this is not the intended behavior...  ;)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386889980,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-zdphbo6gq23bo6llwwdp,task_description,declined
+"VisualEditor: Copying a template from one page to another: render is correct, but template is gone.",I can no longer reproduce this in Firefox.  It's been months since the last time I remember seeing this.,1415246826,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-zdphbo6gq23bo6llwwdp,task_subcomment,NA
+"VisualEditor: Copying a template from one page to another: render is correct, but template is gone.",Can't reproduce this issue...,1414868700,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-zdphbo6gq23bo6llwwdp,task_subcomment,NA
+"VisualEditor: Copying a template from one page to another: render is correct, but template is gone.","https://en.wikipedia.org/w/index.php?title=User:Edgepedia/VE/S%26D&diff=588724142&oldid=588539903 (Command-F to search for ""Commons"") shows the same kind of problem, except that the result doesn't look right.  The image is missing, the box is missing, and the text is on the left rather than on the right.  The appendices are duplicated in that diff, so you can see both what's wrong (the first set of ==External links==) and what it ought to do (the very bottom of the page).",1389226703,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-zdphbo6gq23bo6llwwdp,task_subcomment,NA
+browsertests: triggers for Flow,"The browser tests for Flow should be triggered by Gerrit just like it
+is already the case for ULS (bug 52120) or going to be for VisualEditor (bug 53691).
+
+The tests need to be carefully filtered out since they are expecting content or
+behavior which are not to be found on a freshly installed wiki.
+
+CC QA
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1386869640,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_description,declined
+browsertests: triggers for Flow,We are not going to trigger browser tests on patch submission for now.  It is not that trivial to setup.,1408458857,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,Resetting ticket status as patch was merged,1398408670,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,Nice! I retriggered the job and it took screenshots for the failures: https://integration.wikimedia.org/ci/job/mwext-browsertests-Flow-phantomjs/6/,1394028087,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"As far as I can see[1], Flow is now using mediawiki_selenium 0.2.7, so screen shots should be taken.
+
+1: https://github.com/wikimedia/mediawiki-extensions-Flow/blob/master/tests/browser/Gemfile.lock#L25",1394023970,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"Antoine, do you still need help with this?",1394023662,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,( and one can trigger a run manually using the lame tutorial at https://www.mediawiki.org/wiki/Continuous_integration/Tutorials/Trigger_a_job_manually ),1393868310,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"I got Cirrus Search tests working with Nik and I am close to finish the integration of the VisualEditor tests.
+
+I triggered a run of the Flow browsertests this morning and they are failing: https://integration.wikimedia.org/ci/job/mwext-browsertests-Flow-phantomjs/5/ I havent investigated though.
+
+Cucumber HTML report is https://integration.wikimedia.org/ci/job/mwext-browsertests-Flow-phantomjs/5/artifact/log/report.html
+
+
+The screenshots are not taken because the repository uses mediawiki_selenium (0.2.2), should use 0.2.3 to let us specify the screenshot destination.",1393868264,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"Change 112874 merged by jenkins-bot:
+Tag browser tests with @clean
+
+https://gerrit.wikimedia.org/r/112874",1392402237,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,"Change 112874 had a related patch set uploaded by Hashar:
+Tag browser tests with @clean
+
+https://gerrit.wikimedia.org/r/112874",1392204282,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+browsertests: triggers for Flow,*** Bug 61219 has been marked as a duplicate of this bug. ***,1392204148,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-omucxcdp6ujh4xt2zaue,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"**Author:** `littlesandra88`
+
+**Description:**
+For private wiki's that requires login
+
+$wgGroupPermissions['*']['createaccount'] = false;
+$wgGroupPermissions['*']['edit'] = false;
+$wgGroupPermissions['*']['read'] = false;
+
+I get this from nodejs
+
+Stack trace: AccessDeniedError: Your wiki requires a logged-in account to access the API.
+
+when I do
+
+lynx  http://localhost:8000/localhost/x
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386867540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_description,declined
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"Yes, that should work unless things have changed in VE land in the meantime.",1397865528,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"**littlesandra88** wrote:
+
+Very interesting. I would like to try that.
+
+Based on https://www.mediawiki.org/wiki/Talk:Parsoid#More_private_wiki_trouble would it be correct that all I have to do is adding
+
+$wgVisualEditorParsoidPrefix = 'localhost'; 
+$wgVisualEditorParsoidForwardCookies = true;
+
+and then it should work?",1397859889,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"Parsoid forwards cookies to the API and disables caching if a cookie is set. The VisualEditor extension for example supports forwarding cookies to Parsoid for private wikis, see their settings.
+
+Parsoid should not have access to sensitive information like passwords. In the longer term we'll probably add support for time-limited signed token forwarding once MediaWiki in general gains support for that.",1397847902,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"**littlesandra88** wrote:
+
+If your wiki requires login, then the wiki api.php page, which parsoid needs, also requires login. There is no way to specify a username+password to parsoid so it can access this page. That is what you see in the error message.
+
+To fix this, I guess a dummy account have to be made in MediaWiki, and then the username+password needs to be entered somewhere in parsoid config files.",1392763486,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+AccessDeniedError: Your wiki requires a logged-in account to access the API.,"The behavior looks correct to me.
+
+Can you be more specific about where you see a problem here?",1392750973,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4otjzc7vuobs4xcw5kx2,task_subcomment,NA
+VisualEditor: Copying a section throws undefined error,"Safari 7:
+
+https://www.mediawiki.org/wiki/Communication?veaction=edit
+
+Copy from under H1, including template up to just before the Chat header. I get:
+[Error] TypeError: 'undefined' is not an object (evaluating 'delete children[i].values[attribute]')
+	removeAttributeRecursive (load.php, line 20)
+	removeAttributeRecursive (load.php, line 20)
+	removeAttributeRecursive (load.php, line 20)
+	removeAttributeRecursive (load.php, line 20)
+	removeHtmlAttribute (load.php, line 20)
+	getClonedElement (load.php, line 202)
+	cloneElements (load.php, line 170)
+	onCopy (load.php, line 292)
+	proxy (load.php, line 10)
+	dispatch (load.php, line 45)
+	eventHandle (load.php, line 38)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386842820,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-hqe3vfy7ixkkhkavdrmm,task_description,declined
+VisualEditor: Copying a section throws undefined error,This appears to now work for me; sorry for the epically slow triage.,1414452147,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hqe3vfy7ixkkhkavdrmm,task_subcomment,NA
+VisualEditor: Pasting a template throws undefined getModel error,"[Error] TypeError: 'undefined' is not an object (evaluating '$node.data('view').getModel')
+	getOffsetFromTextNode (load.php, line 244)
+	getOffset (load.php, line 244)
+	getRange (load.php, line 248)
+	pollOnceInternal (load.php, line 319)
+	pollOnce (load.php, line 319)
+	documentOnBlur (load.php, line 287)
+	proxy (load.php, line 10)
+	focus
+	afterPaste (load.php, line 299)
+	(anonymous function) (load.php, line 294)
+	proxy (load.php, line 10)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386842700,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-kfrktikcnijejv2ssua3,task_description,resolved
+VisualEditor: Pasting a template throws undefined getModel error,"Does this bug mean ""you can copy stuff, but nothing happens when you try to paste it""?",1426706269,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-kfrktikcnijejv2ssua3,task_subcomment,NA
+VisualEditor: Pasting a template throws undefined getModel error,"I haven't seen this problem for a long time, so we should probably close it.",1424377866,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-kfrktikcnijejv2ssua3,task_subcomment,NA
+VisualEditor: Pasting a template throws undefined getModel error,"I can't reproduce this now (Mac OS X 10.9 / Safari 7.0.2) – can you, or should we mark as WORKSFORME?",1394222678,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kfrktikcnijejv2ssua3,task_subcomment,NA
+VisualEditor: Pasting a template throws undefined getModel error,"I have trouble reproducing this one, but I think it sometimes happens if you delete something in a surface and then try to copy something else in that surface. Or if you select a block in the destination and then do a paste replace.
+
+Safari 7",1386842818,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-kfrktikcnijejv2ssua3,task_subcomment,NA
+VisualEditor: undefined error during copy,"I selected all VE content from: ""It is important to make"", up to ""Mediawiki-l mailinglist thread ""mysql5 binary schema"" 25.03.2009""
+
+I could pinpoint it to trying to copying the Header ""scripts"" and the warning template that follows it.
+
+[Error] TypeError: 'undefined' is not an object (evaluating 'delete children[i].values[attribute]')
+	removeAttributeRecursive (load.php, line 20)
+	removeAttributeRecursive (load.php, line 20)
+	removeHtmlAttribute (load.php, line 20)
+	getClonedElement (load.php, line 202)
+	cloneElements (load.php, line 170)
+	onCopy (load.php, line 292)
+	proxy (load.php, line 10)
+	dispatch (load.php, line 45)
+	eventHandle (load.php, line 38)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki?veaction=edit",1386840240,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-37pnzuvt2mm7zi2opamc,task_description,resolved
+VisualEditor: undefined error during copy,"Can't reproduce any more. We did a lot of changes to Select-All in the intervening period, which probably fixed it.",1428526886,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-37pnzuvt2mm7zi2opamc,task_subcomment,NA
+VisualEditor: undefined error during copy,"On Safari 7 btw:
+
+I have a slight suspicion thrown Undefined errors like these during copy might also be responsible for the broken internal links that are pasted: [[https://www.mediawiki.org/wiki/Manual:Restoring_a_wiki_from_backup|Manual:Restoring a wiki from backup]]",1386840770,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-37pnzuvt2mm7zi2opamc,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,"screenshot
+
+Steps to reproduce:
+
+1.Open the editor
+2.Insert an image
+
+Observed Result:
+An error appears:
+Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function api.php:1
+
+see the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11996}",1386807960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n7jievcoinoyg7mcltce,task_description,resolved
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,"This is actually still happening. It is a race condition that we can't do anything about and isn't actually affecting anything. It's just a weird warning that jQuery's callback system emits due to <script> limitations.
+
+See bug 59604 for more information.
+
+*** This bug has been marked as a duplicate of bug 59604 ***",1406740632,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,Not happening anymore on betalabs with Chrome and FF with MAC OS X 10.8.5,1388777702,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,This is again happening and the image inserted us appearing as a file link.See the screenshot attached.,1388689872,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,"Created attachment 14215
+Screenshot
+
+**Attached**: {F11997}",1388689847,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Pagelink11thdecember?veaction=edit",1386808174,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n7jievcoinoyg7mcltce,task_subcomment,NA
+"Investigate ""Selenium::WebDriver::Error::WebDriverError"" issues with Chrome via SauceLabs","**Author:** `jhall`
+
+**Description:**
+This seems to be happening somewhat regularly with Visual Editor jobs run in the ""Linux Firefox"" environment via CloudBees SauceLabs:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/203/testReport/(root)/VisualEditor%20Indent,%20Outdent/check_indent_and_outdent_enable_and_disable__outline_example_____Bullets___enabled___disabled___/
+
+Error message reported from SauceLabs is:
+
+unexpected response, code=404, content-type=""text/plain""
+ERROR Job 68d1926e89f24b24a35272766e190eb5 is not in progress. It may have recently finished, or experienced an error. You can learn more at https://saucelabs.com/jobs/68d1926e89f24b24a35272766e190eb5 (Selenium::WebDriver::Error::WebDriverError)
+./features/step_definitions/bullets_steps.rb:34:in `/^I click Bullets$/'
+features/indent_outdent.feature:11:in `When I click <control>'
+
+Looking at the Selenium log captured via SauceLabs, we may discover:
+
+[22.744][FINER]: Waiting for all views to stop loading...
+559[22.745][FINER]: Done waiting for all views to stop loading
+560[23.567][FINER]: Waiting for all views to stop loading...
+561[23.625][FINER]: Done waiting for all views to stop loading
+562[23.625][WARNING]: AfterExecuteCommand failed: Chrome did not respond to 'WaitForAllTabsToStopLoading'. Elapsed time was 57 ms.
+563[23.625][FINE]: Command finished (/session/78a6e87ee7f7d38f694da3813857645f/url) with response {
+564 ""sessionId"": ""78a6e87ee7f7d38f694da3813857645f"",
+565 ""status"": 0,
+566 ""value"": {
+567
+568 }
+569}
+
+The same test runs without errors on a local Linux machine with Firefox.  From the Selenium log on SauceLabs, we discover the following configuration info:
+
+43[3.622][FINE]: Command received (/session/78a6e87ee7f7d38f694da3813857645f)
+44[3.622][FINE]: Command finished (/session/78a6e87ee7f7d38f694da3813857645f) with response {
+45 ""sessionId"": ""78a6e87ee7f7d38f694da3813857645f"",
+46 ""status"": 0,
+47 ""value"": {
+48 ""acceptSslCerts"": false,
+49 ""applicationCacheEnabled"": false,
+50 ""browserConnectionEnabled"": false,
+51 ""browserName"": ""chrome"",
+52 ""chrome.chromedriverVersion"": ""26.0.1383.0"",
+53 ""cssSelectorsEnabled"": true,
+54 ""databaseEnabled"": false,
+55 ""handlesAlerts"": true,
+56 ""javascriptEnabled"": true,
+57 ""locationContextEnabled"": false,
+58 ""nativeEvents"": true,
+59 ""platform"": ""linux"",
+60 ""rotatable"": false,
+61 ""takesScreenshot"": true,
+62 ""version"": ""28.0.1500.95"",
+63 ""webStorageEnabled"": true
+64 }
+65}
+
+The 'WaitForAllTabsToStopLoading' issue seems to be a long-resolved issue with chromedriver (see http://code.google.com/p/selenium/issues/detail?id=2996), so why is this still happening when these test run via CloudBees/SauceLabs?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386807660,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dujs2kys4ubjpcmrausf,task_description,resolved
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"Bug 41193 VisualEditor: Support copy and paste from other VE instances (surfaces) is now closed as FIXED yet a fully working cut and paste is not.
+Some of the bits of copy and paste still not working are documented at http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=585650020&oldid=585645740
+
+#External links? {{Tick}} This seems usually to work (not completely the same, but near enough). Mind you, external links in templates go completely haywire though... 
+#Internal links? {{Cross}} I took one line from [https://www.mediawiki.org/wiki/Manual:FAQ?veaction=edit FAQ], ""where do I donwload MediaWiki?"". One single line, that's all. [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840546] Most other examples below contain further cases of internal links gone wrong
+#References? {{Cross}} I tried to copy [https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki?veaction=edit] (the whole page), to get a page with a reference (not common on Mediawiki). The result is baffling but amusing[https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840568]. If you go to the reference at the bottom of that page, and click the ""arrow"" at the left (taking you up to the place in the same page where that reference is used, no?) then suddenly you end at the original page, in VE edit mode! 
+#List bullets? {{Cross}} [https://www.mediawiki.org/wiki/Files_and_licenses_concept?veaction=edit], section Display, gives [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840576] Note how multiple lines from the original are squashed together in the copy
+#Images? {{Cross}} I found an image in [https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design?veaction=edit], section Code, Status: but the result [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840580] has no image, as part of the syntax is lacking...
+#Templates? {{Cross}} I tried copying the template from [https://www.mediawiki.org/wiki/Communication?veaction=edit here, on the right]: the result is [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840544]. Something simpler? <nowiki>{{Note}}</nowiki> changes into <nowiki><span class=""""><span class=""""></span></span><span class=""""> </span>'''Note'''<span class="""">:</span></nowiki> [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840555]
+#Tables? {{Cross}} Taken from [https://www.mediawiki.org/wiki/Manual:Code?veaction=edit], but the result is not quite the same [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840555], not the contents (yuk) nor the layout. 
+#Code? {{Cross}} I tried to copy the code from [https://www.mediawiki.org/wiki/Manual:FAQ?veaction=edit FAQ], section ""How do I add extra namespaces?"", but the result [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840549] is not quite the same as the original, and looking at the actual code underneath makes this even more obvious
+#Further bugs? {{Cross}}, e.g. the sudden appearance of (actually quite nice) clouds as section headers[https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840559]
+#Further bugs part 2? {{Cross}} But extremely funny! No idea what happened here, but I tried to copy a section from [https://www.mediawiki.org/wiki/Download?veaction=edit], section ""Development releases"", and nothing more. The amazing result, starting from an empty page, is [https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=840564&oldid=840563]. Don't ask me where that template at the bottom left comes from, I didn't ask for it!
+#Further bugs part 3? {{Cross}}, again funny, perhaps the same as the one above: From [https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design?veaction=edit] I copy the short sentence <nowiki>see the {{git file|project=mediawiki/core|file=resources/mediawiki.ui/sourcefiles|sourcefiles}} subdirectory.</nowiki> (shown here in wikitext format, but everything here is copied using VE only!), which looks originally like ""see the resources/mediawiki.ui/sourcefiles subdirectory"". The end result of this one sentence? [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840587] Don't you love it? 
+#Further bugs part 4? {{Cross}} If I want to copy [https://www.mediawiki.org/wiki/Flow_Portal/Design/FAQ?veaction=edit Flow Portal/Design/FAQ], I can't. I can't paste it into my sandbox, and if I paste it in multiple parts, I can't save it (the save button doesn't work).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386801180,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-z5fquxt3pmfidowhr5a7,task_description,invalid
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"Derk-Jan Hartman has responded on wiki http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=585724128&oldid=585724057
+so it looks like some of the work of splitting has been done.
+
+2. I suspect this might be caused by JS errors being thrown because of a copy action on the originating surface. All following copy actions from the source surface (even small ones) might then become corrupted I suspect. bug 58379
+3. Probably the same problem as 2
+4. I was not able to reproduce this: [28]
+5. I was not able to reproduce this: [29]
+6. I was not fully able to reproduce this, but there seems to be in issue in the paragraph following the template. bug 58384
+7. This seems to be because this table also doesn't render properly in the original surface to begin with. bug 58387
+8. I was not able to reproduce this [30], but again, if 2. occurred in the original source surface before your action, then this might cause that I guess. Also it seems that the syntax highlight classes are not dynamically loaded when you paste this content into the target. I reported this as bug 58388
+9. Clouds seem to be the result of pasting something over existing content. bug 58389
+10. not able to reproduce this yet.",1386850954,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-z5fquxt3pmfidowhr5a7,task_subcomment,NA
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"SO to recap: Filing issues is definitely welcome (though only one problem per report), and if I have enough time later today I might try to split this into separate reports. It's not that bug reports aren't welcome, it's that they need to be one issue per report (which is more work for reporters, I know :-/  ).",1386849413,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-z5fquxt3pmfidowhr5a7,task_subcomment,NA
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"Sorry, but this bug report is not handable so I am closing it as INVALID (which does not refer to the bugs you mention, but to this report itself). 
+Please see https://www.mediawiki.org/wiki/How_to_report_a_bug",1386839759,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-z5fquxt3pmfidowhr5a7,task_subcomment,NA
+VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces),"Please re-submit this as individual bugs, as you have been asked before. As it is, it's unactionable.",1386801304,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z5fquxt3pmfidowhr5a7,task_subcomment,NA
+VisualEditor:Newline cannot be entered after copy pasting a text from another VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open the editor
+2.Copy a text or a link 
+3.Paste it into another VE
+4.Press enter
+
+Observed Result:
+Newline cannot be entered in the other VE where the text was pasted into .
+
+It is giving an error :
+
+Resource interpreted as Font but transferred with MIME type application/font-woff: ""http://bits.beta.wmflabs.org/static-master/extensions/UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.woff?version=20131205"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12813}",1386797160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-l6tkqmvanqkkeexo642z,task_description,declined
+VisualEditor:Newline cannot be entered after copy pasting a text from another VE,"I cant reproduce this one either now .I think it got fixed somehow because now the cursor is moving to the next line automatically, after pasting a text into another VE.",1386962329,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-l6tkqmvanqkkeexo642z,task_subcomment,NA
+VisualEditor:Newline cannot be entered after copy pasting a text from another VE,The error you're showing looks like an unrelated warning. I can't reproduce the newline bug either.,1386931658,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-l6tkqmvanqkkeexo642z,task_subcomment,NA
+VisualEditor:Newline cannot be entered after copy pasting a text from another VE,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=11th_december&veaction=edit",1386797349,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-l6tkqmvanqkkeexo642z,task_subcomment,NA
+Fatal exception of type MWException,"**Author:** `littlesandra88`
+
+**Description:**
+After having upgraded from mw1.19 til mw1.22 I
+
+cd extensions
+git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git
+
+and added
+
+require_once ""$IP/extensions/VisualEditor/VisualEditor.php"";
+$wgDefaultUserOptions['visualeditor-enable'] = 1;
+$wgHiddenPrefs[] = 'visualeditor-enable';
+
+to LocalSettings.php as described at
+
+http://www.mediawiki.org/wiki/Extension:VisualEditor
+
+When I visit the wiki I get in the browser
+
+[da26e58f] 2013-12-11 13:28:05: Fatal exception of type MWException
+
+Using CentOS6 64bit
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal",1386769680,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_description,invalid
+Fatal exception of type MWException,"As that's support, could you please raise this in https://www.mediawiki.org/wiki/Project:Support_desk ? Thanks for your understanding!",1386777909,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"**littlesandra88** wrote:
+
+I would prefer to stay at mw1.22 and use an older visual editor, but finding the last git commit that broke mw1.22 is probably not easy.
+
+When I look at the git snapshots I don't see anything in the extensions/.
+
+Can you explain what I have to do to get all the files that makes up a full mw?",1386777827,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"So yeah, VisualEditor is rather experimental and needs non-released versions to work. You can download either 1.23alpha (aka git master) via git or at https://toolserver.org/~krinkle/mwSnapshots/snapshots/mediawiki-core/mediawiki-latest.tar.gz , or the wmf/1.23wmf2 branch (or some other wmf branch greater than 1.23wmf2) via git. These are of course experimental versions of MediaWiki, so it may not be as stable.
+
+You could also try downloading an earlier version of VisualEditor, if one is available.
+
+---
+
+Closing bug as INVALID since this isn't really a MW bug.",1386776520,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"**littlesandra88** wrote:
+
+Very useful variable =)
+
+Does the following make sense?
+
+[df264ef0] / Exception from line 3078 of /var/www/mediawiki-1.22.0/includes/GlobalFunctions.php: MediaWiki 1.23wmf2 required--this is only 1.22.0
+
+Backtrace:
+
+#0 /var/www/mediawiki-1.22.0/extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW(string)
+#1 [internal function]: VisualEditorHooks::onSetup()
+#2 /var/www/mediawiki-1.22.0/includes/Setup.php(592): call_user_func(string)
+#3 /var/www/mediawiki-1.22.0/includes/WebStart.php(153): require_once(string)
+#4 /var/www/mediawiki-1.22.0/index.php(46): require(string)
+#5 {main}",1386776241,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"(In reply to comment #2)
+> to LocalSettings.php. Should I do more?
+
+$wgShowExceptionDetails",1386775580,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"**littlesandra88** wrote:
+
+Hmmm. Do you know which commit that broke mw1.22 comparability? Because then I could just ""git checkout"" that version.
+
+I don't see any extra debug info in the browser of httpd log by adding
+
+error_reporting( -1 );
+ini_set( 'display_errors', 1 );
+
+to LocalSettings.php. Should I do more?",1386772600,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Fatal exception of type MWException,"(In reply to comment #0)
+> After having upgraded from mw1.19 til mw1.22 I
+> cd extensions
+> git clone
+> https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git
+
+So you cloned git master of VisualEditor?
+
+VisualEditor git master requires MW 1.23 - see https://www.mediawiki.org/wiki/Extension:VisualEditor
+
+> [da26e58f] 2013-12-11 13:28:05: Fatal exception of type MWException
+
+See https://www.mediawiki.org/wiki/Manual:How_to_debug",1386771546,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-eq2ksi6d2va2c2ejstl2,task_subcomment,NA
+Visual Editor UI should display MediaWiki:Edittools,"**Author:** `William915`
+
+**Description:**
+For Cantonese Wikipedia, MediaWiki:edittools is quite a useful tool to insert special characters used solely in Cantonese and not in Mandarin. It would be really helpful if it is shown in the interface of VisualEditor as well. I am not sure whether other wikis have similar requests for this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1386760620,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ecndqfmm5tbhzjqkbox5,task_description,resolved
+Visual Editor UI should display MediaWiki:Edittools,"I think that this should be merged into bug 38029, though there are issues there (which I'll comment on).
+
+*** This bug has been marked as a duplicate of bug 38029 ***",1387220238,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ecndqfmm5tbhzjqkbox5,task_subcomment,NA
+Visual Editor UI should display MediaWiki:Edittools,"This relates to bug 50296 (which implements an alternative to MediaWiki:edittools) which is fixed, but not yet deployed. And slightly to bug 38029, because the new implementation does not actually reuse those same characters.",1386767275,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ecndqfmm5tbhzjqkbox5,task_subcomment,NA
+Visual Editor UI should display MediaWiki:Edittools,"This is about https://zh-yue.wikipedia.org/wiki/MediaWiki:Edittools ?
+
+So I enabled 即見編輯 (Visual Editor) on https://zh-yue.wikipedia.org/wiki/Special:%E5%96%9C%E5%A5%BD%E8%A8%AD%E5%AE%9A#mw-prefsection-betafeatures .
+
+But comparing VE (編輯) and classical editing (改原碼) I'd love to know *where* you would display MediaWiki:edittools because there is no textfield anymore?",1386766352,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ecndqfmm5tbhzjqkbox5,task_subcomment,NA
+VisualEditor:Error contacting parsoid server error occurring while saving a page on betalabs,"Screenshot of the error
+
+Error contacting parsoid server error occurring while saving or editing a page on betalabs
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12611}",1386625380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-72io3l35lrubzg5lhtmy,task_description,declined
+VisualEditor:Error contacting parsoid server error occurring while saving a page on betalabs,This was probably a Beta Labs configuration/load issue; closing.,1395881797,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-72io3l35lrubzg5lhtmy,task_subcomment,NA
+VisualEditor:Error contacting parsoid server error occurring while saving a page on betalabs,"Getting error ""Error loading data from server: parsoidserver-http-bad-status: 503. Would you like to retry?""
+
+after clicking on Edit beta on this page:
+http://en.wikipedia.beta.wmflabs.org/wiki/Paste",1386625771,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-72io3l35lrubzg5lhtmy,task_subcomment,NA
+VisualEditor:Error contacting parsoid server error occurring while saving a page on betalabs,"Created attachment 14040
+Screenshot of the error
+
+**Attached**: {F12612}",1386625448,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-72io3l35lrubzg5lhtmy,task_subcomment,NA
+"VisualEditor:""Apply changes""  on the transclusion dialog box and ""Save Page"" button on the page remains active even though there is no change on the transclusion dialog box","Screenshot of the error
+
+Steps to reproduce:
+
+1.Open the Editor.
+2.Open the transclusion dialog.
+3.Click on the trash icon on the right
+4.Click on ""Apply Changes""
+5.Click on Save Pages
+6.Click on ""Review your changes""
+
+Observed Result:
+
+Although there is no change in the template dialog box, the ""Apply changes"" button in the transclusion dialog box remains active.
+After clicking on ""Review your changes"" it says: 
+""Could not start the review because your revision matches the latest version of this page""
+
+See the scrrenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12587}",1386618540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fsd7k5bgeeg76dzbdwqt,task_description,resolved
+"VisualEditor:""Apply changes""  on the transclusion dialog box and ""Save Page"" button on the page remains active even though there is no change on the transclusion dialog box","Merging into 55976.
+
+*** This bug has been marked as a duplicate of bug 55976 ***",1416357284,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fsd7k5bgeeg76dzbdwqt,task_subcomment,NA
+"VisualEditor:""Apply changes""  on the transclusion dialog box and ""Save Page"" button on the page remains active even though there is no change on the transclusion dialog box","Created attachment 14037
+Apply changes button remains active
+
+**Attached**: {F12588}",1386618623,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fsd7k5bgeeg76dzbdwqt,task_subcomment,NA
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,"Steps to Reproduce:
+From Deryck at mw:VisualEditor/Feedback:
+
+Suppose I have:
+
+A foobar B
+C foobar D
+E foobar F
+== foobarbaz ==
+foobar
+
+* When I hit delete at B, the paragraph break is removed correctly, but the cursor jumps to the beginning of the previous paragraph (A).
+* When I hit delete at D, the paragraph break is also removed correctly, but the cursor jumps to or the right-hand side margin of the paragraph before that (to the right of B).
+* Sometimes the paragraph break is removed, and the first letter of the next paragraph is moved to the beginning of the previous paragraph (can't figure out the conditions of this, only observed it once and can't replicate it).
+* When I hit delete at F (just before a section header), the section header disappears... this might be the correct behaviour, but sadly hitting Ctrl+Z does not restore the section header.
+
+
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386614340,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-4oyxxjh4jqregv7p7irk,task_description,resolved
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,The original issue(s) appear(s) to be fixed. The issue spotted by Tilman has been filed as bug 67985.,1405341696,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-4oyxxjh4jqregv7p7irk,task_subcomment,NA
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,"Another example:
+
+In https://en.wikipedia.org/w/index.php?oldid=616866203&veaction=edit , place the cursor left of ""F"" in the word ""Former"" in the first paragrah, and hit the delete key. The ""F"" is deleted correctly, but the cursor jumps two to the left (between ""s"" and ""."").
+
+Reproduced in Firefox and Chromium under Ubuntu 14.04.",1405311380,PHID-USER-wlku5ja6envbi4cz2etp,True,PHID-TASK-4oyxxjh4jqregv7p7irk,task_subcomment,NA
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,"Similar, scary things happen at fr.wp, as reported by VEditors there.
+
+Just a few examples:
+0. Try to VEdit https://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove .
+1. Hit Del right next to ""blabla"".
+2. Notice the cursor is now on the top left margin of the page.
+3. Hit any key, say ""w"". I now have two more lines in my section, the first with a ""b"" on it, the second with a ""w"".
+4. Wait for some seconds. Watch as a ""b"" gets magically added to the header title.
+
+0. VEdit the page again.
+1. Hit Del right next to ""Hawker Siddeley Andover"".
+2. Hit any key, say ""w"". Watch as a pawn appears on the previous line, and both the letter and the pawn multiply after a few seconds.",1388048560,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-4oyxxjh4jqregv7p7irk,task_subcomment,NA
+VisualEditor:  Using forward-delete key on a PC causes odd cursor placement,"The sequence above was performed on Firefox on Win7.
+
+---------------
+
+I've tried reproducing this on Firefox 25 on Ubuntu 12.04. Errors occur at all 3 locations for which errors have been described:
+
+The position of the cursor after hitting delete is unpredictable (read: Deryck has seen a few different outcomes and doesn't have enough time to exhaust all the possibilities); occasionally it even goes to the correct place.
+
+The ""eating up"" of the next (sometimes even previous) paragraph only occurs if you start inserting text immediately after hitting delete. If you click anywhere in the textbox or hit the arrow keys on the keyboard, no text is corrupted.
+
+Hitting Ctrl+Z after these errors yields unpredictable behaviour (same meaning of ""unpredictable"").",1386628058,PHID-USER-axuerq3wmxtfm6tav6bu,True,PHID-TASK-4oyxxjh4jqregv7p7irk,task_subcomment,NA
+Attempt to copy/paste some content blocks leads to JavaScript error,"If I copy from
+https://www.mediawiki.org/w/index.php?title=Wikimedia_Engineering/2013-14_Goals&veaction=edit
+
+to https://www.mediawiki.org/w/index.php?title=User:Eloquence/CP_tests&veaction=edit after clearing it
+
+and select the first section (from start to ""new opportunities."" including the navigation template), I get a JavaScript error 
+
+Uncaught TypeError: Cannot call method 'getType' of undefined  
+
+on the console, and VisualEditor becomes unresponsive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386573480,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-sb4u7diaqxhpd6losrrl,task_description,declined
+Attempt to copy/paste some content blocks leads to JavaScript error,"I think that this, too, was fixed by Ed as part of his suite of fixes for template copying; marking as WORKSFORME. Again, sorry for slow triage.",1394489980,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sb4u7diaqxhpd6losrrl,task_subcomment,NA
+"""Transclusion"" is not a good description for the button which inserts ""templates""","How is a new user supposed to know the meaning of ""Transclusion""?
+
+This should be replaced by something easier to understand such as ""Template"". It should also be easier to translate....
+
+The term is used on these messages:
+	'visualeditor-dialog-transclusion-title' => 'Transclusion',
+	'visualeditor-dialogbutton-transclusion-tooltip' => 'Transclusion',
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386436620,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-qd7qmbfus3ten7z3kj22,task_description,resolved
+"""Transclusion"" is not a good description for the button which inserts ""templates""","
+
+*** This bug has been marked as a duplicate of bug 55434 ***",1393525848,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qd7qmbfus3ten7z3kj22,task_subcomment,NA
+"""Transclusion"" is not a good description for the button which inserts ""templates""","BTW: I reported this after a comment on Portuguese Wikipedia:
+https://pt.wikipedia.org/wiki/WP:Esplanada/an%C3%BAncios?oldid=37579154#Predefini.C3.A7.C3.A3o_para_o_Dicion.C3.A1rio_Cravo_Albin",1386438135,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-qd7qmbfus3ten7z3kj22,task_subcomment,NA
+VisualEditor:Link inspector UI gets broken pressing Command+K to modify a link right after inserting it.,"Broken UI 1
+
+Steps to reproduce:
+
+1.Open the Editor
+2.Add a text and select it
+3.Press command+k to add link onto the text
+4.Again press command+k to modify it
+ 
+
+Observed Result:
+
+The link inspector UI gets broken 
+
+See the screenshots attached
+
+Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/The_link?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12374}",1386367440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6kcc6zwg5etjn2shtwsu,task_description,declined
+VisualEditor:Link inspector UI gets broken pressing Command+K to modify a link right after inserting it.,This issue got fixed.Not occurring anymore.,1389911909,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6kcc6zwg5etjn2shtwsu,task_subcomment,NA
+VisualEditor:Link inspector UI gets broken pressing Command+K to modify a link right after inserting it.,Clicking on the Link icon on the link also does that,1386367740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6kcc6zwg5etjn2shtwsu,task_subcomment,NA
+VisualEditor:Link inspector UI gets broken pressing Command+K to modify a link right after inserting it.,"Created attachment 14017
+Broken UI 2
+
+**Attached**: {F12375}",1386367495,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6kcc6zwg5etjn2shtwsu,task_subcomment,NA
+VisualEditor:Applying a special character insertion while selecting an image deletes the image,"Steps to  reproduce:
+
+1.Open the editor.
+2.Select an image
+3.Open the More>Special Character window
+
+
+Observed Result:
+The image gets deleted
+
+Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=6th_december&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386363900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wh2szim422wwxdw436uf,task_description,invalid
+VisualEditor:Applying a special character insertion while selecting an image deletes the image,This is intentional. Closing as INVALID.,1395355275,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wh2szim422wwxdw436uf,task_subcomment,NA
+VisualEditor:Applying a special character insertion while selecting an image deletes the image,"The behavior is different when the same action is done with Latex or Hieroglyphics which has been described in a separate issue:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58045",1387299843,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wh2szim422wwxdw436uf,task_subcomment,NA
+VisualEditor:Applying a special character insertion while selecting an image deletes the image,"sorry there are two more steps to the repro adding it here.
+
+4.Select any special character
+
+The special character does get added on the first line of the page
+but the image gets deleted.",1386364204,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wh2szim422wwxdw436uf,task_subcomment,NA
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,"Empty hiero tags
+
+Steps to reproduce:
+
+1.Open the editor
+2.Open the hiero insertion tool
+3.Now without closing it open another dialog box for example:Click on Latex/Special Characters/Reference etc.
+4.Close the second window
+5.Save the page
+
+Observed Result:
+The hiero insertion tool is also getting closed after step 4 but if you go to edit source you will see empty hiero tags 
+Now if you log out and press the back button on the browser and try editing the page as anonymous user , there are yellow bordered boxes saying ""Sorry this element can only be edited in source mode now"", on the positions where empty hiero tags are added
+
+See the screenshots attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12355}",1386361620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i2lmjhrkpsur4lev23mc,task_description,resolved
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,"Cannot reproduce.
+
+1. I go to https://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Aklapper&veaction=edit in Firefox 76.
+2. I click ""Insert > Hieroglyphs"" in the menubar. 
+3. Get a dialog.
+4. Click on ""Insert > Images and Media""
+5. Close second window.
+6. ""Publish changes"" is greyed out, hence cannot save page.
+
+Not happening anymore; neither after not closing the second window but entering something.",1590839983,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-i2lmjhrkpsur4lev23mc,task_subcomment,NA
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,Is this still occurring?,1439321171,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i2lmjhrkpsur4lev23mc,task_subcomment,NA
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,"(In reply to comment #1)
+> Created attachment 14012 [details]
+> yellow bordered boxes
+
+I see one tooltip (singular) saying ""Sorry, this element can only be edited in source mode for now."" I assume that's what you mean...
+
+**Attached**: {F12357}",1386373590,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-i2lmjhrkpsur4lev23mc,task_subcomment,NA
+VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open,"Created attachment 14012
+yellow bordered boxes
+
+**Attached**: {F12357}",1386361742,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i2lmjhrkpsur4lev23mc,task_subcomment,NA
+VisualEditor:The special character insertion tool does not open up if the cursor is placed after a link,"screenshot
+
+Steps to reproduce:
+
+1.Open the Editor
+2.Add a link
+3.Place the cursor just after that link position
+4.Go to More>Special Characters
+
+Observed Result:
+The special character insertion tool does not open up
+
+See the screenshot attached
+
+Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=6th_december&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12351}",1386359820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6hhndn43mfdn55mwrsk5,task_description,declined
+VisualEditor:The special character insertion tool does not open up if the cursor is placed after a link,Cannot reproduce it now on betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Page_create&veaction=edit,1387231972,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6hhndn43mfdn55mwrsk5,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**Author:** `jhall`
+
+**Description:**
+Per a request from James F, we should start to expand the selection of environments (OS and browser combinations) that Visual Editor automated tests run via CloudBees.  
+
+For example, add a ""Internet Explorer 10 on Windows 8"" test, and related variations that CloudBees/SauceLabs can accommodate.
+
+Per Chris M, a good way to get started is to copy the existing ""Selenium"" template in CloudBees and figure out what we need to do to add Windows into the mix.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386357000,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_description,resolved
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,Yes.,1403988707,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"Can this be closed? We have this job now, for example:
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-windows_xp-firefox-sauce/",1403988505,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"Jeff, where are the jobs configured? I do not see them anywhere. This is where I have looked:
+
+https://github.com/zeljkofilipin/jenkins-job-builder-config
+https://gerrit.wikimedia.org/r/#/admin/projects/integration/jenkins-job-builder-config
+
+Did you create the jobs manually?",1393856730,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+Tests have been setup in CloudBees at the following locations:
+
+1) Chrome on Windows XP: https://wmf.ci.cloudbees.com/view/ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-windows_xp-chrome/
+2) Firefox on Windows XP: https://wmf.ci.cloudbees.com/view/ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-windows_xp-firefox/",1393392418,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"Change 110980 abandoned by Jhall:
+Adding new priority Windows browser tests for VisualEditor.
+
+Reason:
+Abandoning this change per a discussion between Chris, Željko and myself.  We have decided to implement new (browser + OS) combinations for use with SauceLabs via environment variable values rather than via hard-coded amendments to the mediawiki-selenium gem itself.
+
+https://gerrit.wikimedia.org/r/110980",1391707791,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+Setting bug status back to resolved since the 110980 Gerrit patch is a first step only; if that change works out well, we can add additional (browser + OS) combinations to work towards eventually resolving this bug.",1391456839,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"Change 110980 had a related patch set uploaded by Jhall:
+Adding new priority Windows browser tests for VisualEditor.
+
+https://gerrit.wikimedia.org/r/110980",1391456698,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+Per a chat with Rummana, the priority test environments to add (via CloudBees and Sauce Labs) are:
+
+1) Chrome on Windows XP
+2) Firefox on Windows XP",1391455649,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"(In reply to comment #3)
+> #2 The entire config folder will soon(tm) be moved to mediawiki-selenium
+> gem[2]. We should probably rename config.yml to browsers.yml (since it no
+> longer has any other information, only browsers) and expand the number of
+> combinations, like Wikibase has already done[3]
+
+config.yml is now moved to mediawiki-selenium gem. Feel free to expand the number of browser/OS combinations in the gem.",1390996603,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+(In reply to comment #3)
+> #1 I would hesitate to add more Jenkins jobs until existing ones[1] are rock
+> solid (meaning there were no failures in a week or so).
+> 
+> #2 The entire config folder will soon(tm) be moved to mediawiki-selenium
+> gem[2]. We should probably rename config.yml to browsers.yml (since it no
+> longer has any other information, only browsers) and expand the number of
+> combinations, like Wikibase has already done[3]
+> 
+> 1: https://wmf.ci.cloudbees.com/view/r-ve/
+> 2: https://gerrit.wikimedia.org/r/#/c/90560
+> 3:
+> https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/tests/
+> browser/config/browsers.yml
+
+Thanks Željko - I agree with both of your points, especially #1, which is an ongoing problem area (which I am working on!)",1386721860,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"#1 I would hesitate to add more Jenkins jobs until existing ones[1] are rock solid (meaning there were no failures in a week or so).
+
+#2 The entire config folder will soon(tm) be moved to mediawiki-selenium gem[2]. We should probably rename config.yml to browsers.yml (since it no longer has any other information, only browsers) and expand the number of combinations, like Wikibase has already done[3]
+
+1: https://wmf.ci.cloudbees.com/view/r-ve/
+2: https://gerrit.wikimedia.org/r/#/c/90560
+3: https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/tests/browser/config/browsers.yml",1386703629,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+In addition to the new template in CloudBees, I think we'll need to expand the config.yml file in the VisualEditor repo:
+
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/master/modules/ve-mw/test/browser/config/config.yml
+
+For example, our existing ""firefox"" profile is hard-coded to Firefox version 23 on Linux, so we'll need to add more entries for Firefox on Windows 8, etc.",1386366626,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux,"**jhall** wrote:
+
+Created a new test template to mess around with:
+
+https://wmf.ci.cloudbees.com/template/81889c2c-ef15-4fad-b39b-8256eb9e841a/",1386362913,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ulu6mdlz3xg6p4np7egn,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"When ve-activated class is set on the body, it would be lovely to deactivate this feature as it's rather irritating. Think it's Shift+cursor or Ctrl+Shift+cursor or something similar?
+
+--------------------------
+**Version**: master
+**Severity**: normal",1386356220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qpfa44mctjexoxkqo5hy,task_description,resolved
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"We backported this fix to 1.23wmf6, so mediawiki.org and all sister sites should be fixed now.",1386720882,PHID-USER-nvavrb7ko66hv3xap6sb,True,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"Change 100611 merged by MarkTraceur:
+Move clearInterface things to mw.LightboxInterface
+
+https://gerrit.wikimedia.org/r/100611",1386720390,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"Change 100611 had a related patch set uploaded by MarkTraceur:
+Move clearInterface things to mw.LightboxInterface
+
+https://gerrit.wikimedia.org/r/100611",1386702965,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,Bam. Done. Thanks.,1386639709,PHID-USER-nvavrb7ko66hv3xap6sb,True,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"Change 99722 merged by jenkins-bot:
+Move clearInterface things to mw.LightboxInterface
+
+https://gerrit.wikimedia.org/r/99722",1386639680,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,"Change 99722 had a related patch set uploaded by MarkTraceur:
+Move clearInterface things to mw.LightboxInterface
+
+https://gerrit.wikimedia.org/r/99722",1386360971,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor,This may be because we don't clear keydown listener events on closing the viewer. Patch incomiiiiing,1386356424,PHID-USER-nvavrb7ko66hv3xap6sb,True,PHID-TASK-qpfa44mctjexoxkqo5hy,task_subcomment,NA
+"VisualEditor:Cite error for no {{reflist}} template shows up,when references are added after the reflist in the article","Screenshot of the error
+
+Steps to reproduce:
+
+1.Open the Editor
+2.Add a reference to a line
+3.Add a references list
+4.Now add someother lines after the reflist with references
+5.Save the page
+
+Observed Result:
+The following error appears where as there is already a reflist.
+
+Cite error: There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page).
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12198}",1386272940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c5hksu6p5uhmhvzh64ht,task_description,duplicate
+"VisualEditor:Cite error for no {{reflist}} template shows up,when references are added after the reflist in the article","
+
+*** This bug has been marked as a duplicate of bug 54906 ***",1393541417,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c5hksu6p5uhmhvzh64ht,task_subcomment,NA
+"VisualEditor:Cite error for no {{reflist}} template shows up,when references are added after the reflist in the article","
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:
+https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/testinfobox",1386273019,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c5hksu6p5uhmhvzh64ht,task_subcomment,NA
+VisualEditor:Pressing shift+Right arrow on a newly created page in VE opens up images/logos from media commons,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on Create beta
+2.Press Shift+Right arrow
+
+Observed Result:
+Some images/logos from media commons opens up with image viewer in VE.
+
+See the screenshot attached.
+
+Following errors are found:
+Uncaught TypeError: Cannot read property 'pages' of undefined
+XMLHttpRequest cannot load http://commons.wikimedia.org/w/api.php?action=query&format=json&list=users&ususers=Mike%2Elifeguard&usprop=gender. Origin http://en.wikipedia.beta.wmflabs.org is not allowed by Access-Control-Allow-Origin. /w/index.php?title=Rys&veaction=edit#mediaviewer/File:Wikibooks-logo.svg/1:1
+Uncaught TypeError: Cannot read property 'pages' of undefined
+XMLHttpRequest cannot load http://commons.wikimedia.org/w/api.php?action=query&format=json&list=users&ususers=-xfi-&usprop=gender. Origin http://en.wikipedia.beta.wmflabs.org is not allowed by Access-Control-Allow-Origin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12098}",1386191040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qxsrbiw7op5y6y6inavq,task_description,resolved
+VisualEditor:Pressing shift+Right arrow on a newly created page in VE opens up images/logos from media commons,I think this was fixed a while ago with fixes to MediaViewer.,1395355311,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qxsrbiw7op5y6y6inavq,task_subcomment,NA
+VisualEditor:Pressing shift+Right arrow on a newly created page in VE opens up images/logos from media commons,Pressing just right arrow is now bringing up those logos,1386197120,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qxsrbiw7op5y6y6inavq,task_subcomment,NA
+VisualEditor:Pressing shift+Right arrow on a newly created page in VE opens up images/logos from media commons,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5",1386191147,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qxsrbiw7op5y6y6inavq,task_subcomment,NA
+VisualEditor:Experiencing extreme slow response for all actions in VE in Betalabs,"Currently, while saving a page or when a link insertion too; searches for matching page it is taking longer than usual time in Betalabs.
+
+I am not facing it any other environment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386188280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mbub4crzlrqq6sng5lzq,task_description,declined
+VisualEditor:Experiencing extreme slow response for all actions in VE in Betalabs,I think this was due to the Labs cluster being DDoSed; marking as WORKSFORME as that's been cleared up.,1386356657,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mbub4crzlrqq6sng5lzq,task_subcomment,NA
+BetaFeatures: All icons must have RTL versions,"Beta features have icons to represent them at Special:Preferences.
+
+They usually show a schematic representation of a MediaWiki page with a logo in the top left corner, and this of course means that they should be flipped for RTL languages.
+
+Some of them are trivial - just a horizontal flip.
+
+Some of them are less trivial - for example, in the one for the VisualEditor formula editing I flipped the image and then flipped the Sigma icon inside it so it would still look like Σ and not flipped.
+
+Some of them are even less trivial, for example the icons for the font style experiments. It shows the Latin letter A, and it's weird to show a Latin letter in the beginning of a right-to-left text. Luckily, there are only two major right-to-left scripts, so I made one icon for Hebrew and one for Arabic.
+
+Some relevant sample commits by myself, already merged:
+* https://gerrit.wikimedia.org/r/#/c/94379/
+* https://gerrit.wikimedia.org/r/#/c/94269/
+* https://gerrit.wikimedia.org/r/#/c/94423/
+
+On this commit Jon and Juliusz complained that the image should be re-saved with a smaller size and less metadata:
+* https://gerrit.wikimedia.org/r/#/c/98159/
+
+The SVGs from the previous merged commits may have to be re-done as well.
+
+Any future beta features should have RTL-compatible icons from the start, preferably done by professional designers.
+
+See some more details here:
+https://www.mediawiki.org/wiki/Design_best_practices#Right-to-left_languages
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386162480,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-nng5pyk5o4ztbazvqymy,task_description,resolved
+BetaFeatures: All icons must have RTL versions,"Done by Amir. In future, it's the PM's job (i.e. my job for now) to make sure this is done before deployment.",1387320035,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nng5pyk5o4ztbazvqymy,task_subcomment,NA
+VisualEditor: the {{phpi}} template in mediawiki.org is not showing any content while editing in VE,"Try editing https://www.mediawiki.org/wiki/User:Amire80/phpi in VE.
+
+The template's content doesn't show when editing in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386151980,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-2mttdczw7itqtq7orbyc,task_description,declined
+VisualEditor: the {{phpi}} template in mediawiki.org is not showing any content while editing in VE,"(In reply to Alex Monk from comment #1)
+> Works for me.
+
+For me too. Probably got fixed at some point. Thanks for testing.",1400009090,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-2mttdczw7itqtq7orbyc,task_subcomment,NA
+VisualEditor: the {{phpi}} template in mediawiki.org is not showing any content while editing in VE,Works for me.,1400008936,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2mttdczw7itqtq7orbyc,task_subcomment,NA
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,"Screenshot
+
+I am getting pawn while typing fast on some pages on betalabs sometimes.
+It is not always reproducible.
+I will update the bug if i find any steps to reproduce.
+
+See the screenshots attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12011}",1386113580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_description,declined
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,These issues seem now to be fixed.,1406598559,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_subcomment,NA
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,"Got following error while this was happening:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 93
+Uncaught Error: Offset could not be translated to a DOM element and offset: 169",1386114426,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_subcomment,NA
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,"Created attachment 13973
+screenshot of pawns
+
+**Attached**: {F12012}",1386113733,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_subcomment,NA
+VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example 
+
+http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386113706,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2smfwsfpsgu5q6m6ladw,task_subcomment,NA
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","**Author:** `Wikifram`
+
+**Description:**
+Currently, bugs about Flow are shelved under Mediawiki extensions, unlike e.g. VisualEditor or less important things like QRpedia. Considering the probable serious influx of Flow bugs in the near future, I would propose that it gets its own ""level"", so that e.g. in the search box it is selectable (I mean that if you select ""search bugs"" on the left side, under ""Product"", you should be able to choose ""Flow"" directly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386068580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_description,declined
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","**Wikifram** wrote:
+
+Yeah, sorry about my earlier remark, I was pissed off at a WMF representative (for a oomment made at Mediawiki, not on Bugzilla) and your comment came for me at the wrong time. I shouldn't have replied so strongly. I still think it isn't user friendly to not have it separately, but I appreciate that you try to make it easier for everyone involved anyway.",1386105307,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_subcomment,NA
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","I wouldn't translate it to that, however Bugzilla is primarily a tool for developers and tech-savvy users (though I try to make it more user-friendly, e.g. by the guided bug entry form which is now linked from the very top of https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia since yesterday).
+
+If you don't feel comfortable on https://bugzilla.gnome.org/enter_bug.cgi and don't know that Flow is a ""MediaWiki extension"" (and can be found under that product), http://www.mediawiki.org/wiki/Extension:Flow and especially https://www.mediawiki.org/wiki/Flow_Portal#Contact_and_links provide links how to provide feedback and also where exactly to find and create new bug reports or feature requests. 
+
+Furthermore, once Flow has seen wider deployment, I expect the Flow team and involved Communication folks to set up similar Feedback channels like for VisualEditor at https://en.wikipedia.org/wiki/WP:VE/F which do not necessarily require to interact with Bugzilla.",1386090165,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_subcomment,NA
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","**Wikifram** wrote:
+
+So, translated, ""fuck everyone wanting to find something, Bugzilla is not for you""? Very user-friendly reply. What's the advantage of keeping Flow buried among the other extensions like ""AbsenteeLandlord"", ""Desysop"", and so on? I hope yu will reconsider once you get lots of Flow bugs here, which will probably be soon.",1386082709,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_subcomment,NA
+"Bugzilla should have Flow as a separate Product, not hidden under ""extensions""","Flow is technically speaking an extension, and Bugzilla's taxomony is not primarily based on visibility. 
+(However there have been exceptions from rules, e.g. when the codebase is rather complex and requires subcomponents, like in case of VisualEditor.)",1386069221,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6oalc7d7kvavaxvkwlfd,task_subcomment,NA
+VisualEditor:Reloading the page in read mode opens up the editor,"Steps to reproduce:
+
+1.Click on the Edit beta button
+2.Switch to Edit Source
+3.Switch back to VE
+4.Click on Cancel
+5.Reload the page
+
+
+Observed Result:
+Even after cancelling the edit, in the URL ""&veaction=edit"" still remains appended , therefore after reloading the page, VE opens up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386028260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gqb7b73hwnhh6qxsaoee,task_description,resolved
+VisualEditor:Reloading the page in read mode opens up the editor,"
+
+*** This bug has been marked as a duplicate of bug 57901 ***",1386035934,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gqb7b73hwnhh6qxsaoee,task_subcomment,NA
+VisualEditor:Reloading the page in read mode opens up the editor,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Groel&veaction=edit",1386028361,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gqb7b73hwnhh6qxsaoee,task_subcomment,NA
+Jenkins: Install node-csslint,"Also, set up initial jobs for projects that already use csslint in their local-dev Gruntfile (oojs-ui and visualeditor at the moment).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1386027300,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-poin5yyszgpyi25gk3je,task_description,resolved
+Jenkins: Install node-csslint,"(In reply to comment #5)
+> Does that also lint less or is there a extra tool?
+
+No, we don't yet use cssslint in mediawiki-core (current code doesn't pass) and neither does it validate LESS in any way.",1390847473,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"This has been installed, deployed and is now also actively used by various projects.
+
+In the main 'test' pipelines, however, this is no longer used as we have since migrated to using npm-test (from package.json) directly by installing it in a virtual machine in labs and executing it as specified by the source repository (instead of the install provided by Jenkins).",1390847427,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,Does that also lint less or is there a extra tool?,1386359787,PHID-USER-qaoxfiqu6bxhd5ehlwhc,False,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"Change 98868 merged by Krinkle:
+Create macro for csslint and use in oojs-ui and VisualEditor
+
+https://gerrit.wikimedia.org/r/98868",1386099008,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"Change 98868 had a related patch set uploaded by Krinkle:
+Create macro for csslint and use in oojs-ui and VisualEditor
+
+https://gerrit.wikimedia.org/r/98868",1386098003,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"Change 98722 merged by jenkins-bot:
+Install Grunt plugin for csslint
+
+https://gerrit.wikimedia.org/r/98722",1386028242,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+Jenkins: Install node-csslint,"Change 98722 had a related patch set uploaded by Krinkle:
+Install Grunt plugin for csslint
+
+https://gerrit.wikimedia.org/r/98722",1386027315,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-poin5yyszgpyi25gk3je,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Type something on the first line
+3.Place the cursor at the beginning of the line and insert a template ""Bronze Age""
+4.Save the page
+5.Reopen the editor
+6.Click on More>Reference and add a reference
+7.Type something on the CE
+8.Click on Save Page
+
+Observed Result:
+The Save page loader continues for indefinite amount of time.
+The following errors are found in the developers tool:
+
+Uncaught TypeError: Cannot call method 'apply' of undefined load.php:2
+Uncaught Error: Unbalanced input passed to document load.php:109
+Uncaught TypeError: Cannot read property 'keyedNodes' of undefined load.php:201
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12768}",1386026340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_description,resolved
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"I can't reproduce this, so I assume it is fixed. Please reopen if reproduction of the bug is achieved.",1498128539,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,This is so old I wonder if it still happens?,1498124461,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"I encountered a very similar bug two days ago at https://en.wikipedia.org/w/index.php?title=San_Francisco%E2%80%93Oakland_Bay_Bridge&oldid=650099835&veaction=edit, twice (once when clicking the Save button, and then after starting anew and clicking ""Switch to source editing"" in the Hamburger menu. In both cases, nothing happened after the click except console error messages, and consequently I wasn't able to save my edit).
+
+I wasn't able to reproduce it again, but I remember that the edit involved deleting the first reference and replacing it with a different one, using a citation template where I added an additional (non-default) parameter and then deleted it again in the template editor.
+
+This was in Chrome on a MacBook. Unfortunately I lost the JavaScipt console's output due to an unrelated crash, but I remember that it contained the word ""unbalanced"" just like in the original bug report here.",1426549953,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Could not reproduce on https://en.wikipedia.org/w/index.php?title=User%3AAKlapper_%28WMF%29%2FSandbox%2FT88306&diff=649905376&oldid=649903809 following exactly the steps in T59898#645389 in Firefox 36. 
+
+Is this still an issue, 15 months later? Setting task status to ""Stalled"".",1425509190,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Now The Save Page button does not work after the following steps:
+1.Click on the Edit button
+2.Type something on the first line
+3.Place the cursor at the beginning of the line and insert an image 
+4.Save the page
+5.Reopen the editor
+6.Press Delete twice
+7.Type something 
+8.Click the button ""save page""
+
+Following error appears:
+Uncaught Error: Unbalanced data: looking for closing /mwBlockImage load.php:150",1386111388,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,I can't reproduce now - perhaps due to fixing bug 57654?,1386110555,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Another way to reproduce it:
+After step 5 just click on ""Delete"" and click the button ""Save"".
+
+The following error appear this time:
+
+
+Uncaught Error: Unbalanced set of replace operations found load.php:65
+Uncaught Error: Unbalanced data: looking for closing /mwBlockImage load.php:146",1386029262,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,This issue can be reproduced with images too instead of template.,1386029179,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/infinite_save?veaction=edit",1386026454,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-34urcguvs6tsm3wpvxu2,task_subcomment,NA
+VisualEditor:The link icon appears on the template while attempting to apply a format on the article,"Screenshot
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button for a page
+2.Type something with a link on the main page
+3.Add a template for example:Bronze Age
+4.Save the page
+5.Reopen the editor
+
+Observed Result:
+
+1. Opening the editor selects/highlights the template,but if user attempts to press delete it deletes the first line gets deleted
+
+2.If user clicks on the numbered list or bullet list icon from the toolbar a link icon appears on the template
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12499}",1385850960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wodgydx2ln55w6eo4p32,task_description,resolved
+VisualEditor:The link icon appears on the template while attempting to apply a format on the article,"Possibly maybe this is now fixed? I couldn't reproduce, but I may have been doing it wrongly.",1402553504,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wodgydx2ln55w6eo4p32,task_subcomment,NA
+VisualEditor:The link icon appears on the template while attempting to apply a format on the article,"Slight modification on steps to reproduce:
+
+3.When you add a template place your cursor at the beginning of the first line which contains a link.",1385852486,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wodgydx2ln55w6eo4p32,task_subcomment,NA
+VisualEditor:The link icon appears on the template while attempting to apply a format on the article,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit",1385851038,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wodgydx2ln55w6eo4p32,task_subcomment,NA
+VisualEditor:The format of the text does not change if the cursor is at the end of the text though the options are highlighted in the menu,"screenshot
+
+Steps to reproduce:
+
+1.Place the cursor at the end of the text or in the beginning or in the middle of a text
+2.Now select any or all of the options from More>Computer Code/Strikethrough/Underline/Superscript/Subscript
+
+Observed Result:
+
+Observe that all the options are highlighted in the menu bar but the text format does not change accordingly.If the format of the text is not suppose to change, providing way to disable to the highlight will be better
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12445}",1385763600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ibwc5pqjlv3hmwafkxsy,task_description,resolved
+VisualEditor:The format of the text does not change if the cursor is at the end of the text though the options are highlighted in the menu,"It looks like a formatting button like ""subscript"" is highlighted if a character typed in the cursor's current location would have that formatting. This seems like a sensible behavior.",1437700804,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-ibwc5pqjlv3hmwafkxsy,task_subcomment,NA
+VisualEditor:The format of the text does not change if the cursor is at the end of the text though the options are highlighted in the menu,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/pawn?veaction=edit",1385763638,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ibwc5pqjlv3hmwafkxsy,task_subcomment,NA
+VisualEditor:Deleting an image inside a image settings and reverting it back makes the editor unresponsive,"Steps to reproduce:
+
+1.Click on the Edit button for a page
+2.Insert a image in the page
+3.Go to the media settings and add another image as caption
+4.Save the page
+5.Reopen the editor .
+6.Open the image settings and delete the image as caption.
+7.Undo the action
+8.Click on the media settings button for the image that is as caption
+
+Observed result:
+A media settings dialog box appears with no content but it cannot be crossed out .Also the ""apply changes"" button does not work therefore editor becomes unresponsive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385757300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mrrmkqrflbgdrpb2xbtx,task_description,declined
+VisualEditor:Deleting an image inside a image settings and reverting it back makes the editor unresponsive,Looks like this got fixed at some point.,1414869201,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-mrrmkqrflbgdrpb2xbtx,task_subcomment,NA
+VisualEditor:Deleting an image inside a image settings and reverting it back makes the editor unresponsive,"Test Environment: production
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/cancelled_edit_then_create_page&veaction=edit",1385757340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mrrmkqrflbgdrpb2xbtx,task_subcomment,NA
+VisualEditor:  Bare URLs of the [http://example.com] format cannot be edited,"Intention:
+Add a label to [http://example.com/]
+
+Steps to Reproduce:
+1. Open the page in VisualEditor
+2. Click on the link (which displays as ""[1]"")
+
+
+Actual Results:  
+Nothing.  It is not possible to edit the link.  If opened manually, the link inspector is empty.
+
+Expected Results:  
+1. That the link icon would display when the link was selected.
+2. That the link inspector would show the URL.
+3. That a label could be added (to create [http://example.com Example.com])
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385755140,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-awob47g62om2eeegot3r,task_description,resolved
+VisualEditor:  Bare URLs of the [http://example.com] format cannot be edited,"
+
+*** This bug has been marked as a duplicate of bug 53505 ***",1386000770,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-awob47g62om2eeegot3r,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears inside a media item's caption while user is typing in the page","Steps to reproduce:
+
+1.Click on the edit button for a page where you have some images on the right of the page
+
+2.Type something as the first line
+3.Delete the first line by pressing backspace
+4.When it deletes the first character of the line ,pressing backspace again still keeps the cursor in the main page
+5.Now type something
+
+
+Observed Result:
+Though the cursor is in the main page,a pawn appears inside the caption of the image at the right.
+
+A pawn will appear in the main document for the following steps:
+5. if after step 4 , user presses backspace again 
+6.While the image at the right is highlighted press the Right arrow > from the keyboard
+7.When the cursor comes to the main article type something
+
+A Pawn appears in the main document.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385688600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6t2ellqdwuvd5rouaqmf,task_description,resolved
+"VisualEditor: Pawn (""♙"") appears inside a media item's caption while user is typing in the page","Possibly got fixed by https://bugzilla.wikimedia.org/show_bug.cgi?id=57927
+Cannot reproduce it now.",1387229483,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6t2ellqdwuvd5rouaqmf,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears inside a media item's caption while user is typing in the page","Created attachment 13930
+Screenshot
+
+**Attached**: {F12417}",1385688823,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6t2ellqdwuvd5rouaqmf,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears inside a media item's caption while user is typing in the page","Test Environment: production
+Browser: Chrome Version FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/cancelled_edit_then_create_page&veaction=edit",1385688711,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6t2ellqdwuvd5rouaqmf,task_subcomment,NA
+VisualEditor:Clicking on reference does not bring up the reference add dialog for a specific case in production,"Steps to reproduce:
+
+1.Click on the edit button for a page where you have a image on the right of the page which has another image as caption
+
+2.Type something as the first line
+3.Delete the first line by pressing backspace
+4.When it deletes the first character of the line ,pressing backspace again still keeps the cursor in the main page
+5.Now add a reference to the empty space,which gets added to the caption of the image at the right.
+6.Now type something on the second line and add a reference
+
+Observed Result:
+
+The dialog box for adding reference does not appear anymore.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385676300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-euq7ddmd6rhlinex2kpe,task_description,resolved
+VisualEditor:Clicking on reference does not bring up the reference add dialog for a specific case in production,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/noref?veaction=edit",1385676383,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-euq7ddmd6rhlinex2kpe,task_subcomment,NA
+VisualEditor:Pawn (♙) appears in Media Settings when there is another media added in the caption,"Screenshot of the pawn
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Add an image in the caption of that media.
+3.Type a text in the caption
+4.Delete the text by pressing the backspace
+5.When the cursor reaches the image at the right,Press the right arrow to go back to the initial position of the deleted text.
+6.Type something again at that position.
+
+Observed Result:
+A Pawn (♙) appears in the Media Setting
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12405}",1385673960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3rb6x5qzoi77sgsqzncr,task_description,resolved
+VisualEditor:Pawn (♙) appears in Media Settings when there is another media added in the caption,This appears to be long-fixed.,1406598618,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3rb6x5qzoi77sgsqzncr,task_subcomment,NA
+VisualEditor:Pawn (♙) appears in Media Settings when there is another media added in the caption,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5
+Example Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/test_field&veaction=edit",1385674053,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3rb6x5qzoi77sgsqzncr,task_subcomment,NA
+VisualEditor: Improve link inspector to address usability issues,"There's currently two user experience issues that I think need to be addressed soon.
+
+1. Creating (or, more precisely, inserting) a new link.
+
+When creating a new link, there is no intuitive way to assign it a label until you decide to close the link inspector at which point the link target text appears as the link label.
+
+
+2. Editing the label of an existing link.
+
+When editing the label one has to manually ensure all of the link text is selected and replaced. In doing so it is almost impossible not to accidentally delete the link.
+
+Given ""foo <a>bar</a> baz"", selecting ""bar"" manually and typing will replace it with a text node. So essentially the only way to change is to do it in two arbitrary halves.
+
+Additionally, even if selecting and replacing would work, selecting an entire external link (e.g. right after insertion and the url becoming the label) can be quite difficult since URLs tend to contain one or more word-boundaries (that is word-boundaries from the perspective from double-click make-word-selected features that browsers provide).
+
+2b. Anti-pattern: Ambiguous focus, unable to overwrite text
+
+When clicking on the link the ""right"" way, it opens the inspector at which point the entire link label is nicely selected (even if the link spans multiple space-separated words or things like urls that contain word-boundary characters), but it seems hard to retain this selection as any action outside the inspector collapses the selection (maybe impossible, at least I couldn't).
+
+This also makes it hard to fully delete a link. The unlink feature (or clear-formatting) leaves the text. So one would have to carefully make a selection that spans the entire link label and remove that.
+
+---
+
+
+Note, there's currently a few open bugs for technical problems (not UX problems) that might require a (whether or not temporary) solution to the above UX issues as they currently happen due to certain actions not being expected by the code. In fixing those, we most likely have to come up with some way to handle this.
+
+For example: (bug  56976) Pawn appears when clicking into the label after creating a link
+
+When creating a new link and clicking (conceptually ""back"") in the document
+where the cursor was from the link inspector, a pawn appears. This happens because right now links have no label until you close the inspector. So when creating a new link, the cursor position remains empty the entire time. When eventually manually closing the inspector (or clicking anywhere other than the current paragraph) the empty (internal pawn) placeholder label is replaced with the text of the link target.
+
+The immediate fix would be to do the expansion earlier (or even live while the user is working on the link target), however that still leaves a smell of UX issue #2 afterwards.
+
+
+--
+
+Summary of issues:
+
+* It is impossible to select a link label (selecting it also selects the open/close tag, which means typing over it removes the link). To change a label, one has to enter the new label inside the old (e.g. in the middle of it), and strip away the outer halves of the old label.
+
+* It is hard to provide a label for a new link as one has to close the inspector first.
+
+* It is hard to delete a link (as an object that is, unlinking text is easy) as one can't focus it. And the auto-selection when opening the inspector always disappears when returning to the document from the inspector.
+
+Possible solutions:
+
+* Implement a new user interface concept in the content editable surface that would allow a cursor (and selection) to fully cover an annotation whilst not covering the open/close of the annotation. This would enable one to select (and replace) the label of a link.
+
+* Add the link label as an additional field to the link inspector.
+
+* (or; maybe) turn the link into a focusable node and have it no longer be an annotation. This naturally comes with complications, but may be for the best.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385657880,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xoirrjdhitvqz5v3riwf,task_description,resolved
+VisualEditor: Improve link inspector to address usability issues,"
+
+*** This bug has been marked as a duplicate of bug 48789 ***",1395197341,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xoirrjdhitvqz5v3riwf,task_subcomment,NA
+puppet config of Parsoid localsettings breaks in labs-vagrant,"Parsoid doesn't work when you add the visualeditor role in Labs-Vagrant setup,
+clients get 404 errors. After tweaking parsoid to log the actual error (bug 57694), /var/log/upstart/parsoid.log contains
+
+  Stack trace: DoesNotExistError: Page Fetch failure for null : Error: Invalid URI
+  ""undef/w/api.php?format=json&action=query&meta=siteinfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensiontags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols""
+
+Obviously undef/w/api.php is going to give 404.
+
+The bad URL path arises because puppet/manifests/roles.pp sets $server_url to 'undef' if forwarded_port isn't set, and it somehow isn't set in labs-vagrant. puppet/modules/mediawiki/templates/parsoid.localsettings.js.erb propagates this to /srv/parsoid/js/api/localsettings.js which contains 
+  parsoidConfig.setInterwiki( 'localhost', 'undef/w/api.php' )
+
+(Erik Bernhardson figured all this out!)
+
+One fix is to not set $server_url to undef. Patch coming.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385606640,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-pgc3jemya3dsi32iivp4,task_description,resolved
+puppet config of Parsoid localsettings breaks in labs-vagrant,Thanks for the detailed report and the patch.,1385609666,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-pgc3jemya3dsi32iivp4,task_subcomment,NA
+puppet config of Parsoid localsettings breaks in labs-vagrant,"Change 98060 merged by Ori.livneh:
+Set $server_url to something other than undef
+
+https://gerrit.wikimedia.org/r/98060",1385609634,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pgc3jemya3dsi32iivp4,task_subcomment,NA
+puppet config of Parsoid localsettings breaks in labs-vagrant,"Change 98060 had a related patch set uploaded by Spage:
+Set $server_url to something other than undef
+
+https://gerrit.wikimedia.org/r/98060",1385608993,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pgc3jemya3dsi32iivp4,task_subcomment,NA
+VisualEditor:Reflist is appearing as bullet list if while inserting reflist the cursor is at the end of an empty bulleted item,"Screenshot
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Type a text with reference in the page
+3.Make it a bulleted list by selecting the option from toolbar.
+4.Press Enter to entry the second item on the list but leave it blank 
+5.Now click on More>References list to add a reflist to the page
+6.Save the page
+
+Observed Result:
+
+The reflist is appearing as bulleted list
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12350}",1385596680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kwxuse4ccvh4vqlns2jq,task_description,resolved
+VisualEditor:Reflist is appearing as bullet list if while inserting reflist the cursor is at the end of an empty bulleted item,Seems to work correctly now.,1437700987,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-kwxuse4ccvh4vqlns2jq,task_subcomment,NA
+VisualEditor:Reflist is appearing as bullet list if while inserting reflist the cursor is at the end of an empty bulleted item,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/testlive",1385596774,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kwxuse4ccvh4vqlns2jq,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting the preceding text of a reference icon,"Screenshot of the pawn
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Add a reference to a text
+3.Select the reference icon
+4.Press left arrow key to move the cursor to the left of the icon
+5.Now delete all of the text on the left of the icon by pressing backspace button
+
+Observed Result:
+
+A pawn ♙ appears right next to the reference icon.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12224}",1385509080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dmyb42alfmzpnf6hhtbk,task_description,resolved
+VisualEditor: Pawn ♙ appears after deleting the preceding text of a reference icon,This looks fixed to me. Not sure exactly when.,1406598426,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dmyb42alfmzpnf6hhtbk,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting the preceding text of a reference icon,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page: https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox",1385509144,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dmyb42alfmzpnf6hhtbk,task_subcomment,NA
+VisualEditor: Link is not getting added when the clear formatting is used while the link inspector was open,"Steps to reproduce:
+
+1.Create the Edit button
+2.Select a text
+3.Open the link inspector
+4.Click on the clear formatting icon from the toolbar
+5.While the link inspector is still open select the first matching page
+6.Apply the link
+
+Observed Result:
+The link did not get applied.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385488740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uhuzwsa5ueu5efipt6sv,task_description,declined
+VisualEditor: Link is not getting added when the clear formatting is used while the link inspector was open,"We now close the inspector when you click into the toolbar, which essentially fixes the underlying issue.",1402550186,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uhuzwsa5ueu5efipt6sv,task_subcomment,NA
+VisualEditor: Link is not getting added when the clear formatting is used while the link inspector was open,I would suggest to close the inspector as user clicks on clear formatting,1385492198,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uhuzwsa5ueu5efipt6sv,task_subcomment,NA
+VisualEditor: Link is not getting added when the clear formatting is used while the link inspector was open,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page: Try applying the link to page ""link"" to the text link on this page:
+https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test_field?venotify=created",1385488871,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uhuzwsa5ueu5efipt6sv,task_subcomment,NA
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"The reference for the main page
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Add a reference to a text
+3.In the reference dialog add an image
+4.Also type some text into that reference box (for example ""The content"" in this case.)
+5.Now select the image
+6.Go to Media Settings
+7.Now add a reference to that image
+8.Type anything for this second reference box
+9.Apply changes in all three dialog boxes
+10.Save the changes 
+11.Reopen the editor
+12.Select the reference [1]
+13.Open the reference dialog box
+
+Observed Result:
+The text ""The content"" appears as a template with a highlighted blue box around it.Now click on the [1] reference on the image by going to the media settings of the image.
+It opens the same content for the first reference and it keeps on opening the same window as you repeatedly do it for all the reference windows appears.
+
+Expected Result:
+The reference on the main page and the reference on the image should be different content.But since the reference in image [1] is pointing to the same [1] for the article ,this issue arises.
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58270
+
+**Attached**: {F12091}",1385427060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sbvwivlalvusgjwp5ire,task_description,resolved
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"Re-checked - seems that the contents of all ""nested"" references are displayed correctly. No repeatedly open windows appear. 
+
+Marking as resolved.",1423527553,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-sbvwivlalvusgjwp5ire,task_subcomment,NA
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test_copy_and_paste?veaction=edit
+
+Click on the [1] reference of this page.",1385427311,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sbvwivlalvusgjwp5ire,task_subcomment,NA
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"Created attachment 13908
+Opening the same dialog box unlimited times
+
+**Attached**: {F12093}",1385427248,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sbvwivlalvusgjwp5ire,task_subcomment,NA
+VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference,"Created attachment 13907
+How it appears after step 13
+
+**Attached**: {F12092}",1385427205,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sbvwivlalvusgjwp5ire,task_subcomment,NA
+VisualEditor:When the cursor is in the middle of a text the formatting (Bold/Italic/No format) does not work properly,"Steps to reproduce:
+
+1.Click on the Edit button
+2. Place the cursor in the middle of a text, for example between u and r of ""cursor""
+3.Try different heading format and bullet or numbered list option:all of them work
+4.But try formatting to Bold/Italic/No format: it does not work but the buttons are selected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385409600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ggvevjnwwlcst5xdmmsn,task_description,invalid
+VisualEditor:When the cursor is in the middle of a text the formatting (Bold/Italic/No format) does not work properly,"That's supposed to do nothing initially, then when you start typing, the text you type will be bold/italic/whatever.",1414138312,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ggvevjnwwlcst5xdmmsn,task_subcomment,NA
+VisualEditor:When the cursor is in the middle of a text the formatting (Bold/Italic/No format) does not work properly,"Test Environment: test2
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://test2.wikipedia.org/w/index.php?title=Testing2511&veaction=edit",1385409685,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ggvevjnwwlcst5xdmmsn,task_subcomment,NA
+VisualEditor:Attempting to delete a template at the beginning of an article deletes the whole paragraph following it,"Steps to reproduce:
+
+1.Click on the ""Edit"" button for a page in production
+2.At the beginning of the article place a template
+3.Write a paragraph following that template.
+4.Save the page
+5.Reopen the page in Edit mode
+
+Observed Result:
+The template gets selected(blue highlight appears) automatically.However the template icon does not appear to edit the template rather a four sided drag icon appears on it.
+Now if you press the delete button while the template is selected ,the following paragraph gets deleted.Pressing undo does not get it back on the page.User have to cancel this edit session and restart again to by pass the issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385408580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-q2lm2rmvtrop4xotxxnt,task_description,resolved
+VisualEditor:Attempting to delete a template at the beginning of an article deletes the whole paragraph following it,This now [[https://en.wikipedia.org/w/index.php?title=User%3ARYasmeen_%28WMF%29%2Ftemplate_at_the_beginning&type=revision&diff=663104473&oldid=583275067|works correctly]]! ,1432052899,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-q2lm2rmvtrop4xotxxnt,task_subcomment,NA
+VisualEditor:Attempting to delete a template at the beginning of an article deletes the whole paragraph following it,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/template_at_the_beginning",1385408648,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-q2lm2rmvtrop4xotxxnt,task_subcomment,NA
+VisualEditor: [Regression?] Cursor appears misplaced after hitting Enter twice in a list,"This is where the cursor shows up in the text
+
+Might be related to https://bugzilla.wikimedia.org/show_bug.cgi?id=41064, or not.
+
+1. Reach https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=583262564 .
+2. Put the cursor after the last reference.
+3. Hit Enter once. A new bullet is correctly added.
+4. Hit Enter again.
+
+Possible outcomes:
+1) see screenshot: the cursor blinks between two lines, on the word ""cognitive"" (observed in Chrome, Vector/Monobook);
+2) the cursor is attached to the top right corner of the picture of Emily Deschanel (Firefox, Vector);
+3) the cursor is nowhere in sight (Firefox, Monobook).
+
+Notice that if you repeat the procedure at this point, it will work in Chrome, it will still fail in FF.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7
+**Platform**: PC
+
+**Attached**: {F12043}",1385404860,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-22g4ckg3k3byisqvwxiy,task_description,resolved
+VisualEditor: [Regression?] Cursor appears misplaced after hitting Enter twice in a list,"This was fixed a couple of weeks ago in the HandleEnter re-write work, I think.",1395360338,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-22g4ckg3k3byisqvwxiy,task_subcomment,NA
+VisualEditor: [Regression?] Cursor appears misplaced after hitting Enter twice in a list,"(Sorry, please read, ""it will work in Firefox, it will still fail in Chrome"".)",1385405084,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-22g4ckg3k3byisqvwxiy,task_subcomment,NA
+"VisualEditor: If a link that doesn't have a pipe is changed, the link target remains","Consider that you have an internal wiki link that doesn't use a pipe, for example ""[[Danzig]]"". If you edit the page in VE and change the text from ""Danzig"" to ""Gdańsk"" without using the link inspector the result will be ""[[Danzig|Gdańsk]]"". See the history of https://en.wikipedia.org/wiki/User:Amire80/links-nopipe .
+
+It is not obvious to the user what is happening - does the target or does it not? The users may want to achieve one result or the other in different cases. My own hunch is that users will more frequently want to change the target as well, although that is just a guess.
+
+If we have a reason to think that one behavior is far more common than the other, then it should be the default. If we are not sure, than some more indication about the target will be useful. The only ways to be sure before saving are to check the diff to open the link inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54947",1385296620,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-m7leu4xitl3lklt5rrdg,task_description,duplicate
+"VisualEditor: If a link that doesn't have a pipe is changed, the link target remains","
+
+*** This bug has been marked as a duplicate of bug 54947 ***",1400106756,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m7leu4xitl3lklt5rrdg,task_subcomment,NA
+"VisualEditor: If a link that doesn't have a pipe is changed, the link target remains","(In reply to Amir E. Aharoni from comment #0)
+> Consider that you have an internal wiki link that doesn't use a pipe, for
+> example ""[[Danzig]]"". If you edit the page in VE and change the text from
+> ""Danzig"" to ""Gdańsk"" without using the link inspector the result will be
+> ""[[Danzig|Gdańsk]]"".
+
+I get the opposite of this ([[Gdańsk|Danzig]]), but this bug still feels valid to me.",1400106672,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-m7leu4xitl3lklt5rrdg,task_subcomment,NA
+"VisualEditor: If a link that doesn't have a pipe is changed, the link target remains","... Just an explanation for my guess: In the source editor changing [[Nasik]] to [[Nashik]] requires the adding one 'h'. In the current version of VisualEditor it requires adding one 'h', opening the link editor and adding the 'h' there, too.",1385368772,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-m7leu4xitl3lklt5rrdg,task_subcomment,NA
+VisualEditor:A Return character appears when a text is followed by <math> code,"screenshot
+
+Steps to reproduce:
+
+1.Create a page
+2.Type something
+3.From the ""Edit Source"" option add the following after the text:
+<math>\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}
+
+
+</math>
+
+4.Save the page
+5.Click on Edit-beta again
+
+
+Observed Result:
+A Return character appears after the text in edit mode
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12681}",1385162100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hxm7dylzsr7cb36xgt4j,task_description,resolved
+VisualEditor:A Return character appears when a text is followed by <math> code,"
+
+*** This bug has been marked as a duplicate of bug 48290 ***",1415882814,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hxm7dylzsr7cb36xgt4j,task_subcomment,NA
+VisualEditor:A Return character appears when a text is followed by <math> code,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/text_then_math?veaction=edit",1385162188,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hxm7dylzsr7cb36xgt4j,task_subcomment,NA
+VisualEditor:After adding a reference the cursor jumps to the beginning of the first line of the page,"Steps to reproduce:
+
+1.Create a page with a long content first
+
+2.Towards the end add references
+
+Observed Result:
+
+Every time user adds a reference it takes him to the beginning of the article making him scroll down all the way down to get to where he was adding a reference
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385149560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b2the5znff3yi5iqewab,task_description,resolved
+VisualEditor:After adding a reference the cursor jumps to the beginning of the first line of the page,"
+
+*** This bug has been marked as a duplicate of bug 58090 ***",1386805579,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b2the5znff3yi5iqewab,task_subcomment,NA
+VisualEditor:After adding a reference the cursor jumps to the beginning of the first line of the page,Related to 57271?,1385406168,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-b2the5znff3yi5iqewab,task_subcomment,NA
+VisualEditor:After adding a reference the cursor jumps to the beginning of the first line of the page,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:
+https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/ref_not_editable",1385149578,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b2the5znff3yi5iqewab,task_subcomment,NA
+VisualEditor: unnamed links can not be edited,"The two links at the end of the third line are external unnamed links.
+VE does not allow editing them.
+The markup guide for en.wp says these links are ""Only used within article body
+for footnotes"", but of course they might be used also outside ns0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Elitre_%28WMF%29/sandbox&veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57418
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57420",1385123880,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-tjb4bkjfszkwoz7qktjo,task_description,resolved
+VisualEditor: unnamed links can not be edited,"Merging with bug 53505.
+
+*** This bug has been marked as a duplicate of bug 53505 ***",1385489060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tjb4bkjfszkwoz7qktjo,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,"Go to :https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/table_test
+
+See that in the VE mode and Edit source mode the reference list is showing up but in Read mode there is no reference list.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385077680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kgksabqabkax4kkg7izy,task_description,declined
+VisualEditor:References list does not appear when it follows a table in a page.,Seems to be because there are two reference list invocations on the page. The fact that the read mode only displays the first seems to be by design.,1437707657,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,Changing the summary to a more generalized one: References list does not appear when it follows a table in a page.,1385078540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,"Found the  the steps to reproduce:
+
+1.Create a page
+2.Add some references
+3.Add a table into it with the following from the edit source mode:
+{| border=""2""
+|+ [[my table]]
+
+|-
+|
+# first cell<ref>reference</ref>
+|
+# [[second cell]]
+|
+* third cell
+|-
+|1[[File:Tibouchina urvilleana flower ja.jpg|thumb|150x150px|{{Like resume}}]]
+|2{{Like}}
+|3<references />
+
+|}
+
+4.Add references list at the end of the page
+5.Save the page
+
+Observed Result:
+The references list does not appear in the view mode.",1385078395,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,"Created attachment 13870
+In the read mode
+
+**Attached**: {F12503}",1385077817,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+VisualEditor:References list does not appear when it follows a table in a page.,"Created attachment 13869
+In the VE mode
+
+**Attached**: {F12502}",1385077727,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kgksabqabkax4kkg7izy,task_subcomment,NA
+"VisualEditor:VE renders a table with border=""0"" as border=""1""","In read mode
+
+Steps to reproduce:
+
+1.Click on the Edit source.
+
+2. Type the following:
+
+table test title
+
+{| border=""0""
+|+ my table
+
+|-
+|first cell 
+|second cell 
+|third cell
+|-
+|1
+|2
+|3
+
+|}
+
+3.Save the page
+4.View the page in read mode
+5.Open the page in VE mode.
+
+Observed Result:
+There is not border for the table in read mode but when you open the page in VE mode it renders the table with a border=1.
+
+See he screenshots attached.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/table_test
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12479}",1385062260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-twgftigrpz6uckwjelnt,task_description,resolved
+"VisualEditor:VE renders a table with border=""0"" as border=""1""","
+
+*** This bug has been marked as a duplicate of bug 57295 ***",1385123360,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-twgftigrpz6uckwjelnt,task_subcomment,NA
+"VisualEditor:VE renders a table with border=""0"" as border=""1""","Created attachment 13864
+In VE mode
+
+**Attached**: {F12480}",1385062312,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-twgftigrpz6uckwjelnt,task_subcomment,NA
+VisualEditor:References resulting from repeated citation cannot be edited in the VE mode  after changing the ref name from :0,"Steps to reproduce:
+
+1.Click on the Edit mode
+2.Add a reference 
+3.Add the same reference 5 times in that page
+4.Save the page
+5.Go to Edit Source
+
+Observed Result:
+I think, due to repeated citation of the same reference with no defined name ,a name with value (:0) is added to the <ref> tags for all the references that is using the same reference
+
+But, if user intends to change the name of the original reference to a more meaningful name for future reference purpose he might do the following steps
+
+6. Change the name value from "":0"" to ""bbc"" for the first references
+7.Close the editor 
+8.Click on Edit now.
+9.Hover over other references which were using same references
+
+Observed Result:
+A message shows up this reference cannot be edited in the VE ,can only be edited in edit source mode.
+
+Can this message be more precise to point where the problem is?For example in the read mode it says ""Invalid <ref> tag; no text was provided for refs named :0""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385059320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lhb7q2iod46plkygoni4,task_description,resolved
+VisualEditor:References resulting from repeated citation cannot be edited in the VE mode  after changing the ref name from :0,"Not VE-specific, but a larger issue with how Cite.php ""works"" (hint: it doesn't).
+
+*** This bug has been marked as a duplicate of bug 18103 ***",1398114542,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lhb7q2iod46plkygoni4,task_subcomment,NA
+VisualEditor:References resulting from repeated citation cannot be edited in the VE mode  after changing the ref name from :0,"Created attachment 13861
+Screenshot of the error
+
+**Attached**: {F12468}",1385059523,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lhb7q2iod46plkygoni4,task_subcomment,NA
+Enhance hooks.rb in mediawiki-selenium gem to warn when BROWSER_LABEL is undefined,"**Author:** `jhall`
+
+**Description:**
+This is a follow-up to this recent change to the VisualEditor browser tests:
+
+https://gerrit.wikimedia.org/r/#/c/96793/
+
+Since a user may neglect to explicitly export a value for the BROWSER_LABEL environment variable, it might be a good idea to enhance hooks.rb for the mediawiki-selenium RubyGem to add a warning where that value is undefined.  
+
+The danger is that where the BROWSER_LABEL value is undefined, individual tests will not target the intended wiki pages, since those pages are expected to have the BROWSER_LABEL string included in the page URL.
+
+The hooks.rb file already issues similar warnings for the MEDIAWIKI_USER and MEDIAWIKI_PASSWORD variables in the ""Before('@login')"" method:
+
+https://github.com/wikimedia/mediawiki-selenium/blob/master/lib/mediawiki/selenium/hooks.rb
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385059020,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rutprbjwmdkgbr5b3uoo,task_description,invalid
+Enhance hooks.rb in mediawiki-selenium gem to warn when BROWSER_LABEL is undefined,"**jhall** wrote:
+
+This task is invalid now that warnings for undefined BROWSER, PLATFORM and VERSION environment variable values have been added to env.rb in the most recent versions of the mediawiki_selenium Rubygem, so closing this ticket as INVALID.",1393019466,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rutprbjwmdkgbr5b3uoo,task_subcomment,NA
+VisualEditor: Pawn appears near copy/pasted template,"This happens in FF (both skins).
+1. https://fr.wikipedia.org/wiki/Utilisateur:Elitre_%28WMF%29/Prove?veaction=edit
+2. reach the Sources section.
+3. copy the (en) template and paste it before ""Franca C"".
+4. hit space.
+
+A pawn appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385049060,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-nbvnewtd4mrfr4a4ytce,task_description,resolved
+VisualEditor: Pawn appears near copy/pasted template,This appears to be long-fixed.,1406598703,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nbvnewtd4mrfr4a4ytce,task_subcomment,NA
+VisualEditor: Pawn appears near copy/pasted template,https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_(WMF)/Prove&oldid=98530979,1390240856,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-nbvnewtd4mrfr4a4ytce,task_subcomment,NA
+[Regression?] VisualEditor: Still get a pawn when select-all->replace in Firefox,"Intention:
+I want to blank a page, and add new contents.
+
+Steps to Reproduce:
+Since this does not seem to happen on each page, I'll add the steps I followed to reproduce it.
+
+1. VEdit https://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE with Firefox and Monobook. 
+2. Right-click, select all, delete.
+3. Click to re-gain focus.
+4. Type something. A pawn will appear.
+5. Review your changes. Notice that not all of the contents were actually deleted after #2. Also notice that some or all of your newly added text might be missing. 
+6. Save the page. Your text (most or all of it) shouldn't be there. What you have are random chunks of old text. And your pawn :)
+
+
+
+Actual Results:  
+While reproducing, the following also occurred to me:
+1. After blanking, a weird cursor (like an arrow pointing up) appeared at the beginning of the line. After typing for a while, Back Space and the keyboard navigation arrows wouldn't work. 
+2. When VEditing the page created after #6, blanking it and then clicking on a line to make the cursor appear resulted in fragments of words appearing. If I tried to type, I'd also get rapidly multiplying pawns.
+(All these behaviors are not new to me.)   
+
+Expected Results:  
+I expected the page to be really blank, and pawn-less :)
+
+Reproducible: Sometimes
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42404",1385044860,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-32bj4xsfxzl66kfabfpq,task_description,resolved
+[Regression?] VisualEditor: Still get a pawn when select-all->replace in Firefox,"Up-merging to bug 64917 (whoops)
+
+*** This bug has been marked as a duplicate of bug 64917 ***",1399642730,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-32bj4xsfxzl66kfabfpq,task_subcomment,NA
+[Regression?] VisualEditor: Still get a pawn when select-all->replace in Firefox,"Original report at en.wp:
+<<If I go to Plato, enter VE, right click, select all, and then press some letter or number, a pawn will appear. Also, if I review changes, there is still material left is the ""your text"" section. Firefox 25.0.1; Windows 7 Professional SP1 64-bit; Monobook skin. --Atethnekos>>.",1385045081,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-32bj4xsfxzl66kfabfpq,task_subcomment,NA
+VisualEditor: Save page button does not work if user includes reflist template while there is already reference list,"Steps to reproduce:
+
+1.Click on the edit button
+2.Add some content in the page
+2.Add some references in the page
+3.Add references list from More>References list.
+4.Now Go to More>Transclusion
+5.Add the template reflist
+6.Click on the ""Save Page"" button
+
+Observed Result:
+The save page button does not work ,user had to cancel this edit session and re-work again on the editor
+
+There is no js error for this in the console.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/reference_list_and_reflist_both?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384989060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-prrrskdzk7yoo3hn4dt2,task_description,resolved
+VisualEditor: Save page button does not work if user includes reflist template while there is already reference list,"It is possible to save correctly now. It's still //not// possible to have a page display more than one `<references />` block for the same ref group, but that seems to be by design.",1437707348,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-prrrskdzk7yoo3hn4dt2,task_subcomment,NA
+VisualEditor: Save page button does not work if user includes reflist template while there is already reference list,I think its better if either we do not permit them to include both and explicitly notify them or both gets added properly.,1384989788,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-prrrskdzk7yoo3hn4dt2,task_subcomment,NA
+VisualEditor: Save page button does not work if user includes reflist template while there is already reference list,"However the issue is not same when user does the vice versa.That is, if he had reflist template before and adds again a references list it does get added in the page.But,the later one does not show up in the read mode but on VE edit mode and on edit source mode where both the {{Reflist}} and <references /> are present",1384989303,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-prrrskdzk7yoo3hn4dt2,task_subcomment,NA
+VisualEditor:Cannot save the content of a page after an idle time on the open editor,"Steps to reproduce:
+
+1.Open the VE editor for a page.
+2.Make some edit
+3.Leave the editor open for a long time (more than an hour)
+4.Come back after that idle time and click the button ""Save Page""
+
+
+Observed Result:
+The content does not get saved.Shows a js error in the console
+
+Uncaught TypeError: Cannot read property 'saveRetries' of undefined
+(anonymous function)
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+(anonymous function)
+fire load.php:12
+self.fireWith load.php:14
+done load.php:119
+callback
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384970580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ooqyq4axuutnv7pchwcb,task_description,resolved
+VisualEditor:Cannot save the content of a page after an idle time on the open editor,This [[https://en.wikipedia.org/w/index.php?title=User%3ANeil_P._Quinn-WMF%2Fsandbox&type=revision&diff=662373500&oldid=662187275|now seems to work]]!,1431646757,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-ooqyq4axuutnv7pchwcb,task_subcomment,NA
+VisualEditor:Cannot save the content of a page after an idle time on the open editor,"I am curious about how different this is from the common behavior with the wikitext editor, which will usually display a message like ""Sorry! We could not process your edit due to a loss of session data. Please try again. If it still doesn't work, try logging out and logging back in."" (not sure if this is the actual one though) and which ""fixes"" itself if you just retry to save.",1385402139,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ooqyq4axuutnv7pchwcb,task_subcomment,NA
+VisualEditor:Cannot save the content of a page after an idle time on the open editor,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test_reference",1384970640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ooqyq4axuutnv7pchwcb,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,"While testing on production , I found that when I select a specific template all the related parameters show up on the dialog box.
+However, in test 2 and beta I do not see any related parameter to select.
+Can those parameters be included on these environment, so that the testing can be done on it in these environment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384970040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ufkgro7khm6qaqk6mboe,task_description,invalid
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,Manual importing of the TemplateData is needed for this.,1394502019,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,"I might be missing something obvious here but,
+the last change to the Taxobox template on test 2 was made 7 years ago, I think, so even if it worked properly, and I didn't test this, I think it's missing TemplateData (https://www.mediawiki.org/wiki/VisualEditor/Portal/TemplateData ).
+If you want to use the same templates you use on en.wp, for example,
+you'd need to import them and their documentation, I guess.",1385399847,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,An example page for editing taxobox could be :https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/table_test?veaction=edit,1385071956,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,"What would be a link to edit e.g. taxobox with VE ""on production""?",1385067331,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor: The related parameters of templates are missing in test2 and beta environment,"I tried the following templates:
+reflist
+citeweb
+taxobox",1384970190,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ufkgro7khm6qaqk6mboe,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the edit button
+2.Add several references in the page
+3.Add a template reflist onto it.
+4.Insert an image
+5.Go to the Media Settings for that image and add a reference and also add the template reflist to the image
+6.Save the page
+
+Observed Result:
+
+The reflist that was created for the page disappears and the error appears ""Cite error: There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page)""
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12295}",1384913460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-32vbq6qkhx3wngjcnodn,task_description,duplicate
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"(Cool, I never used that template more than once on a page. Now I know it can be done :) https://en.wikipedia.org/wiki/Template:Reflist#Multiple_uses )",1385419366,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"
+
+https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/reflist_on_a_image
+(In reply to comment #2)
+> Some more issues with this action:
+> 
+> 1. After adding a reflist to the image the whole order of the references in
+> that page gets messed up.
+> 
+> The reference to the image becomes reference with footnote [1] and in the
+> page
+> the order of the reference got changed from [1],[2],[3]  to [2],[3],[4].
+> and the reference of the image gets modified to the [1] reference of the
+> document. 
+> 
+> 
+> 
+> 2. Now if you switch to edit source, you will see since the reference in the
+> image is taking the value of first reference of the document as a repetitive
+> reference, the [1] reference of the document gets assigned with ref name=
+> "":1"" 
+> 
+> But still there is another on the page:Cite error: The named reference :1 was
+> invoked but never defined (see the help page).",1384915850,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Created attachment 13844
+flower.com got changed to facebook.com
+
+**Attached**: {F12298}",1384915704,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Created attachment 13843
+the changed order
+
+**Attached**: {F12297}",1384915617,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Created attachment 13842
+The initial order
+
+**Attached**: {F12296}",1384915579,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,"Some more issues with this action:
+
+1. After adding a reflist to the image the whole order of the references in that page gets messed up.
+
+The reference to the image becomes reference with footnote [1] and in the page the order of the reference got changed from [1],[2],[3]  to [2],[3],[4].
+and the reference of the image gets modified to the [1] reference of the document. 
+
+
+
+2. Now if you switch to edit source, you will see since the reference in the image is taking the value of first reference of the document as a repetitive reference, the [1] reference of the document gets assigned with ref name= "":1"" 
+
+But still there is another on the page:Cite error: The named reference :1 was invoked but never defined (see the help page).",1384915131,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+VisualEditor:The reflist of the page disappears after adding a reflist to an image,Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/reference_on_a_image,1384913965,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-32vbq6qkhx3wngjcnodn,task_subcomment,NA
+export REUSE_BROWSER for 4 VisualEditor tests in Jenkins builds,"As of today we have four tests that use the @make_selectable_line and @edit_user_page hooks, and that pass with or without the REUSE_BROWSER env variable.  
+
+I suggest we set that env variable REUSE_BROWSER=true for 
+
+bullets.feature
+indent_outdent.feature
+headings.feature
+general_markup.feature
+
+This will save a significant amount of time for each of the four VE builds, since the four tests will log in only four times per build instead of a total of twenty-one times without REUSE_BROWSER=true. 
+
+Note that setting REUSE_BROWSER=true does not affect our ability to analyze test failures.  For example, see the failure messages below for a run of the bullets test: 
+
+----
+
+timed out after 10 seconds (Watir::Wait::TimeoutError)
+./features/step_definitions/bullets_steps.rb:26:in `block (2 levels) in <top (required)>'
+./features/step_definitions/bullets_steps.rb:25:in `/^a \# is added in front of input string in the diff view$/'
+features/bullets.feature:8:in `Then a <character> is added in front of input string in the diff view'
+
+timed out after 10 seconds (Watir::Wait::TimeoutError)
+./features/step_definitions/bullets_steps.rb:39:in `block (2 levels) in <top (required)>'
+./features/step_definitions/bullets_steps.rb:38:in `/^a \* is added in front of input string in the diff view$/'
+features/bullets.feature:8:in `Then a <character> is added in front of input string in the diff view'
+
+timed out after 10 seconds (Watir::Wait::TimeoutError)
+./features/step_definitions/bullets_steps.rb:52:in `block (2 levels) in <top (required)>'
+./features/step_definitions/bullets_steps.rb:51:in `/^a \#\# is added in front of input string in the diff view$/'
+features/bullets.feature:21:in `Then a <character> is added in front of input string in the diff view'
+
+timed out after 10 seconds (Watir::Wait::TimeoutError)
+./features/step_definitions/bullets_steps.rb:61:in `block (2 levels) in <top (required)>'
+./features/step_definitions/bullets_steps.rb:60:in `/^a \*\* is added in front of input string in the diff view$/'
+features/bullets.feature:21:in `Then a <character> is added in front of input string in the diff view'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384899720,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-6hbiyaynilweesovh3xs,task_description,declined
+export REUSE_BROWSER for 4 VisualEditor tests in Jenkins builds,As far as I remember we have agreed this will not be implemented. Please reopen if I misunderstood.,1386000360,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-6hbiyaynilweesovh3xs,task_subcomment,NA
+export REUSE_BROWSER for 4 VisualEditor tests in Jenkins builds,"I am **strongly against** reusing browsers between scenarios, for various reasons. If speed is our problem, we should run the tests in parallel.",1384950098,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-6hbiyaynilweesovh3xs,task_subcomment,NA
+"VisualEditor:""Cannot open another window while another one is active"" error appears while attempting to save the page after deleting the transclusion ""reflist""","Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the edit button
+2.Add few references to the page
+3.Go to more>Transclusion
+4.Add the template reflist
+5.Delete this template
+6.An icon still appears for that template click on it
+7.When the dialog for that template appears cross it out.
+8.Click the button ""Save Page""
+
+Observed Result:
+The Save page button does not work.User cannot save the edit made so far on the page. It requires to cancel the edit and reopen the editor.
+
+The js error that appears on the console is:
+Uncaught Error: Cannot open another window while another one is active
+
+See the screensshot attached
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/test_reference?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12289}",1384897440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-plwpcaqphz3xxe7n4naa,task_description,declined
+"VisualEditor:""Cannot open another window while another one is active"" error appears while attempting to save the page after deleting the transclusion ""reflist""",Think this was fixed in the re-work of how we attach to transclusions? WFM in my testing.,1393528386,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-plwpcaqphz3xxe7n4naa,task_subcomment,NA
+"VisualEditor:""Cannot open another window while another one is active"" error appears while attempting to save the page after deleting the transclusion ""reflist""",*** Bug 57204 has been marked as a duplicate of this bug. ***,1393528338,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-plwpcaqphz3xxe7n4naa,task_subcomment,NA
+"VisualEditor:""Cannot open another window while another one is active"" error appears while attempting to save the page after deleting the transclusion ""reflist""",Possibly a duplicate of bug 57204?,1385419740,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-plwpcaqphz3xxe7n4naa,task_subcomment,NA
+"VisualEditor:Template ""reflist"" does not get added immediately on the page","No indication if there is any reflist added or not
+
+Steps to reproduce:
+
+1.Click  on the edit button
+2.Add few references to the page
+3.Now click on the More>Transclusion
+4.Select the template ""reflist"" and add it to the page
+
+Observed Result:
+The reflist template does not get added rather an icon for the template shows up on the page.
+If you move your cursor that icon disappears too making user confused whether they have added any reflist or not.
+
+See the screenshots attached.
+
+Test Environment: Production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/test_reference?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12287}",1384895040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5wto4e4bokkzs7zmbjod,task_description,duplicate
+"VisualEditor:Template ""reflist"" does not get added immediately on the page","Well, so much for not using the dedicated References list button :p
+
+Now seriously:
+with my PC/Win 7 and Chrome (both skins), I can't even see the template icon.
+Under FF instead I see it, and at its left there's this character ^ in grey.
+In both cases, the blinking cursor is now at the top of the page:
+if I type something, the text will be added on that line (in Chrome) or where the Reflist is supposed to be (in FF: the icon is now gone).",1385405980,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-5wto4e4bokkzs7zmbjod,task_subcomment,NA
+"VisualEditor:Template ""reflist"" does not get added immediately on the page","Created attachment 13837
+template icon
+
+**Attached**: {F12288}",1384895082,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5wto4e4bokkzs7zmbjod,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the edit button
+2.Select a text or place your cursor in a blank space
+3.Go to More>Latex/hieroglyphics option
+
+Observed Result:
+None of the inspectors open up .More over ,in one attempt they opened overlapping with each other and after that I could not close any of them.I had to cancel my editing and reopen the editor to get rid of them
+
+It gives the following script error in the console:
+Uncaught TypeError: Cannot read property '$element' of null
+
+
+
+see the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12278}",1384891380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_description,resolved
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,This is fixed and verified too.,1386025050,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"(In reply to comment #5)
+> should this block the next deployment?
+
+James: ping?",1385980317,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"
+should this block the next deployment?",1385503659,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"In production the behavior is more annoying, as it opens the Latex inspector after a while and then it keeps opening everytime I select a text.And it does not go away by changing the focus/ crossing out the dialog.User have to cancel the edit and then re-open the editor.",1385490596,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,It is my understanding that this is related to James' second answer at https://www.mediawiki.org/wiki/Talk:VisualEditor/Beta_Features/Formulae#Bugs_&_compatibility_issues.,1385401860,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"Some more insight to the case where it opened.
+
+1.Keep the firbug or developers tool closed
+2.Click on Latex and/or hieroglyphics option
+3.Open the firebug/developer tool
+
+Observed Result:
+
+Both the inspectors open overlapping with each other.However if you type something inside it and try to close it , it does not let you do that",1385058457,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta,"Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Test Page:https://test2.wikipedia.org/w/index.php?title=Verify_56274&veaction=edit",1384891692,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d3idqafxjg2fp5yxwuqt,task_subcomment,NA
+VisualEditor:Quickly switching between Read and Edit tab gives a JS error,"Steps to reproduce:
+
+1.Click the button Edit
+2.Quickly switch to read tab and again switch back to edit button
+
+Observed Result:
+An error appears in the console
+Uncaught TypeError: Cannot call method 'getModel' of null load.php:37
+ve.init.mw.ViewPageTarget.updateToolbarSaveButtonState load.php:37
+(anonymous function) load.php:43
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+(anonymous function)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384887120,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xs35ywfjwn7iygqwhlqh,task_description,resolved
+VisualEditor:Quickly switching between Read and Edit tab gives a JS error,"
+
+*** This bug has been marked as a duplicate of bug 51546 ***",1395360091,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xs35ywfjwn7iygqwhlqh,task_subcomment,NA
+VisualEditor:Quickly switching between Read and Edit tab gives a JS error,"Also got these error once :
+
+Uncaught RangeError: ""Maximum call stack size exceeded""
+
+Uncaught TypeError:Object #<Object> has no method 'abort'",1384887846,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xs35ywfjwn7iygqwhlqh,task_subcomment,NA
+VisualEditor:Quickly switching between Read and Edit tab gives a JS error,"Test Environment:Production
+Test Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/test_reference?veaction=edit
+OS:MAC OS X 10.8.5
+Browser:Chrome 26.0.1410.65",1384887208,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xs35ywfjwn7iygqwhlqh,task_subcomment,NA
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","Intention:
+Edit a page containing a gallery.  The gallery contains <ref> citations.
+
+Steps to Reproduce:
+1. Open the page in VisualEditor.
+2. Notice the big red errors inside each gallery that contains a <ref> citation.
+
+
+Actual Results:  
+Big red errors are present at the bottom of each gallery that contains a <ref> citation.  Depending on whether the ref is part of a group, these are the two errors I saw:
+
+There are <ref group=$1> tags on this page, but the references will not show without a {{reflist|group=$1}} template (see the help page).
+
+There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page).
+
+
+Expected Results:  
+That VisualEditor would not produce an error.  (There were proper {{reflist}} templates at the bottom of the page.)
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384817640,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-htmipabmc3qfaiznrebo,task_description,resolved
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","This has been fixed, sort of:  Instead of a big red error, it now puts a references block at the end of the gallery (re-starting the numbering, and including only refs from the gallery).",1414857389,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-htmipabmc3qfaiznrebo,task_subcomment,NA
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","I don't think this is valid any more, is it?",1414811249,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-htmipabmc3qfaiznrebo,task_subcomment,NA
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","Also, as seen by editing https://en.wikipedia.org/w/index.php?oldid=596381198 you cannot re-use any references that are within a gallery block.",1392925622,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-htmipabmc3qfaiznrebo,task_subcomment,NA
+"VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery","If you change a caption in the gallery so that it contains a {{reflist}}, then VisualEditor displays the citations within the gallery (under the green can't-edit-this hash), and this error is not present.",1384817743,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-htmipabmc3qfaiznrebo,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"Trying to type a word in brackets might lead to the disappearing of the opening brackets, no wikitext warning appears and no nowikis are added.
+
+Happened to me twice in sandboxes,
+see https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/tests&oldid=185158 and https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=62542564&oldid=62363821 ;
+it didn't happen in https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=582254513&oldid=581339890 and I also don't seem able to get this bug while VEditing ns0.
+All tests under Chrome and Vector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53856",1384805580,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_description,declined
+VisualEditor: opening square brackets can sometimes disappear,"Also happening at https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=203117 when trying to add a new point under ""simpler"".",1414156189,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"Happening again.
+In https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_(WMF)/Prove2&oldid=108482122 I tried to start a new line precisely under the first one (the one ending in ""sdas"") with a word in brackets to see if it triggered the warning.
+After typing the opening square brackets, these disappear when I start typing a word.",1414155292,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,Closing provisionally as WORKSFORME.,1394677011,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,Is this still occurring?,1393642241,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,I still can. VE hates me :(,1385498718,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,I can't reproduce at https://en.wikipedia.org/wiki/User:Elitre_(WMF)/sandbox?veaction=edit&useskin=monobook with a hard-refresh. :-(,1385496350,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"It doesn't happen in FF, but it's still there if I switch to Monobook in Chrome.",1385122698,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"Sorry :/
+Chrome, Vector, Win7:
+
+https://en.wikipedia.org/wiki/User:Elitre_(WMF)/sandbox?veaction=edit
+Cursor right under the sandbox template and above the article text,
+I start typing brackets and they disappear.",1385122418,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"I guess we'll never know, since right now it seems to work again just fine. Good for us.",1384880909,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,I can't reproduce this after a few dozen tries. Can you give more details about how it happens? Is it on new pages only? Existing pages? Existing pages when you're editing an old revision? At the start of the document? Everywhere? Etc.,1384841983,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"Yeah, it's probably Chrome.",1384814747,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: opening square brackets can sometimes disappear,"I've been unable to replicate this in Mac OS 10.7.5/Safari 6/Vector or in Mac OS 10.7.5/Firefox 25.0.1/Vector, in either userspace or the mainspace.",1384813672,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-eja43n7xny5lbdanmj4p,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"Environment:test 2
+SamplePage:
+OS:MAC OS X 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384797420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_description,resolved
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),*** Bug 57194 has been marked as a duplicate of this bug. ***,1385420317,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"Verified this issue.
+Created a separate ticket for idle time issue:https://bugzilla.wikimedia.org/show_bug.cgi?id=57314",1384970683,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"(In reply to comment #11)
+> After the fix,I am not getting that error message.
+> However, after keeping the editor for a long time and then attempting to save
+> the content gives the following js error.
+> 
+> Uncaught TypeError: Cannot read property 'saveRetries' of undefined
+> (anonymous function)
+> fire load.php:12
+> self.fireWith load.php:14
+> self.fire load.php:14
+> (anonymous function)
+> fire load.php:12
+> self.fireWith load.php:14
+> done load.php:119
+> callback
+> 
+> Assuming it as a separate issue?
+
+Yes, that's distinct; marking this as FIXED, but please re-open if it re-occurs.",1384841530,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"After keeping the editor open for long time*(In reply to comment #11)
+> After the fix,I am not getting that error message.
+> However, after keeping the editor for a long time and then attempting to save
+> the content gives the following js error.
+> 
+> Uncaught TypeError: Cannot read property 'saveRetries' of undefined
+> (anonymous function)
+> fire load.php:12
+> self.fireWith load.php:14
+> self.fire load.php:14
+> (anonymous function)
+> fire load.php:12
+> self.fireWith load.php:14
+> done load.php:119
+> callback
+> 
+> Assuming it as a separate issue?",1384833671,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"After the fix,I am not getting that error message.
+However, after keeping the editor for a long time and then attempting to save the content gives the following js error.
+
+Uncaught TypeError: Cannot read property 'saveRetries' of undefined
+(anonymous function)
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+(anonymous function)
+fire load.php:12
+self.fireWith load.php:14
+done load.php:119
+callback
+
+Assuming it as a separate issue?",1384833601,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),I just got this error on production too.,1384817063,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"I got the Parsoid server message as well a few minutes ago on that page.
+Then I tried again (from Opera, unlogged, then from FF and Chrome while logged in) and it just saved. :/",1384816838,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"To the best of my knowledge, test2 and mediawiki.org are using the production Parsoid instance.  Please let us know if that is not the case.",1384816794,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"That might be a different issue, possibly with the parsoid service setup used by test2. AFAIK it is not using the Parsoid production cluster. The QA folks have been working on this recently and would know more.",1384816272,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),Happened again on test2 . No errors in the JS console.On the dialog box there was a message:Error: Error contacting the Parsoid server,1384814682,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),I am not getting this issue anymore.The new page creation and content saving both are working now.,1384812957,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),Any errors in the JS console?,1384812600,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),Sample Page: https://test2.wikipedia.org/w/index.php?title=Verify_56274&veaction=edit,1384798456,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"Created attachment 13825
+Screenshot of the error
+
+**Attached**: {F12136}",1384798087,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?),"Steps to reproduce:
+
+1.Attempt to modify any content on any page in test2 environment .
+2.Click the Save button 
+
+Observed Result:
+The spinner for saving continues for a long time but the content does not get saved .And ""An error occurred"" message appeared on the dialogue box
+See the screenshot attached
+
+Browser:Chrome Version 26.0.1410.65
+and FF 25",1384797670,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lpdahuwz6su3aljkvwaf,task_subcomment,NA
+VisualEditor:Add the tags to wikitext detection regex to show wikimarkup warning,"When a tag <ref> is inserted in visual editor it shows a wikitext warning to user but there are few more tags which I think will be good to be added to the wikitext detection regex such as 
+<s>
+<math>
+<poem>
+
+None of them triggers wikitext warning right now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384562700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qgpnwx66d3gjnes6vhh6,task_description,declined
+VisualEditor:Add the tags to wikitext detection regex to show wikimarkup warning,WONTFIX. The test is not intended to catch every possible mistaken attempted insertion of HTML or wikitext.,1384841786,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qgpnwx66d3gjnes6vhh6,task_subcomment,NA
+"VisualEditor:""ULS: Unknown language doi. ULS: Unknown language fonipa"" appears upon typing the on the ""Search Box""","Steps to reproduce:
+
+1.Load any page on test2
+2.Take your cursor to the ""Search Box"" and attempt to type something in it.
+3.Observe Console>Errors from Developer tool
+
+Observed Result :
+ULS: Unknown language doi.
+ULS: Unknown language fonipa
+
+Appears on this section.
+
+Note:The selected language is English in this case
+
+Not sure if it is expected or not.Close the bug if it is not an issue. 
+
+Test Environment:
+Browser:Chrome 26.0.1410.65
+OS:MAC OS 10.8.5
+Test Page:https://test2.wikipedia.org/wiki/Verify_56274
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384558620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iuv45mcdfmqdyf3lof4l,task_description,resolved
+"VisualEditor:""ULS: Unknown language doi. ULS: Unknown language fonipa"" appears upon typing the on the ""Search Box""","Not related to VisualEditor itself, ULS spams this to the console on every page everywhere.
+
+*** This bug has been marked as a duplicate of bug 45047 ***",1384558760,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-iuv45mcdfmqdyf3lof4l,task_subcomment,NA
+clean up obsolete VE API dependency,"AIUI, Flow no longer uses VE's API to convert from/to wikitext/html, it posts API requests to Parsoid's URL if its available.
+
+I think this means:
+* Hooks.php onSetupAfterCache() is obsolete, (and has been since we occupied namespaces?!),
+* Flow should have its own parameters $wgFlowParsoidURL, $wgFlowParsoidPrefix, $wgFlowParsoidTimeout which in comments can default to the $wgVisualEditor* values.
+* Clean up obsolete comments in ParsoidUtils.php
+
+This will make it clearer that Flow can work with Parsoid even if the VisualEditor extension isn't installed.
+
+(Is the Parsoid extension even required on MediaWiki servers in a cluster arrangement where only one machine runs the Parsoid nodejs service?)  I guess yes in order to ""trigger Parsoid cache updates"".)
+
+--------------------------
+**Version**: master
+**Severity**: minor",1384545240,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-uftjcaqg7wftryrkpsp5,task_description,resolved
+clean up obsolete VE API dependency,"Change 95605 merged by jenkins-bot:
+(bug 57111)  clean up obsolete VE API dependency
+
+https://gerrit.wikimedia.org/r/95605",1384888882,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uftjcaqg7wftryrkpsp5,task_subcomment,NA
+clean up obsolete VE API dependency,"Change 95605 had a related patch set uploaded by Matthias Mullie:
+(bug 57111)  clean up obsolete VE API dependency
+
+https://gerrit.wikimedia.org/r/95605",1384875148,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uftjcaqg7wftryrkpsp5,task_subcomment,NA
+clean up obsolete VE API dependency,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/470, but people from the community are welcome to contribute here and in Gerrit.",1384761811,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-uftjcaqg7wftryrkpsp5,task_subcomment,NA
+clean up obsolete VE API dependency,"Coincidentally, I had been working on that yesterday: https://gerrit.wikimedia.org/r/#/c/95605/
+
+onSetupAfterCache still needs to be removed in there, though.",1384593024,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-uftjcaqg7wftryrkpsp5,task_subcomment,NA
+VisualEditor:Edit|Edit Source links are appearing on a blank heading,"edit/edit source option on blank space
+
+Steps to reproduce:
+
+1.Click on the Edit button for a page
+2.Select the option sub-heading 1 in a blank space
+3.Click the button ""Save Page""
+
+Observed Result:
+The Edit/Edit Source link appears in the blank space
+
+Browser:Chrome
+Page:Any
+Environment:test 2
+
+see the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12697}",1384382100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6grklf7gpa6ipg5o6y3,task_description,resolved
+VisualEditor:Edit|Edit Source links are appearing on a blank heading,This now seems to be fixed (on test2 using Chrome).,1431471672,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-c6grklf7gpa6ipg5o6y3,task_subcomment,NA
+"When changing image type, the type is added to the wikitext instead of replacing the old one","This came up while working on the new Media dialog in VisualEditor. When changing a block image type, for instance from 'thumb' to 'frameless', the new type is added onto the wikitext instead of replacing the old type tag.
+
+Original wikitext:
+[[File:image.png|thumb|right|caption goes here|466x466px]]
+
+After changing the type of the image to frameless (including all style changes and type attribute) the resulting post-save wikitext is this:
+
+[[File:image.png|thumb|right|caption goes here|466x466px|frameless]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384290060,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-tzaqvebpmuva7a34ejvl,task_description,resolved
+"When changing image type, the type is added to the wikitext instead of replacing the old one","
+
+*** This bug has been marked as a duplicate of bug 48665 ***",1384299690,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-tzaqvebpmuva7a34ejvl,task_subcomment,NA
+Changing image alignment attribute adds the alignment instead of replacing it in wikitext,"This came up while working on the new media dialog in VisualEditor. When there's a change in an image align attribute, the resulting wikitext adds the new alignment keyword instead of replacing the original.
+
+Initial wikitext:
+[[File:image.png|thumb|right|caption goes here|466x466px]]
+
+After changing the image to right alignment (removing tright and replacing with tleft, and replacing the align attribute in the image object) -- the resulting wikitext post save is this:
+
+[[File:image.png|thumb|right|caption goes here|466x466px|left]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384289880,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-6jr33finz32lgguug7oy,task_description,resolved
+Changing image alignment attribute adds the alignment instead of replacing it in wikitext,"
+
+*** This bug has been marked as a duplicate of bug 48665 ***",1384299493,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-6jr33finz32lgguug7oy,task_subcomment,NA
+"VisualEditor: Template is not deselected when ""clicking out"" of it in certain circumstances","1. Edit [[mw:Manual:$wgEdititis]] in VE
+2. Click the ""Language"" template at the bottom, to select it
+3. Click in the blank space to the right of the word ""places""
+
+Notice that the template is (correctly) deselected.
+
+4. Do steps 2 and 3 again
+
+The template is not deselected this time. Even though the cursor is flashing in the right place (implying deselection), any typing will overwrite the template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1384236840,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-t4dsq6rpgyk5vhbxgywu,task_description,declined
+"VisualEditor: Template is not deselected when ""clicking out"" of it in certain circumstances","Doesn't matter, seems to work now.",1393633116,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-t4dsq6rpgyk5vhbxgywu,task_subcomment,NA
+"VisualEditor: Template is not deselected when ""clicking out"" of it in certain circumstances",Seems to work for me now. Setting unconfirmed so a VE team member can check and confirm.,1390548745,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-t4dsq6rpgyk5vhbxgywu,task_subcomment,NA
+Offer help or descripition for parameters,"It would be nice to offer informative description of each parameter when filling it, to know what to fill. Some paremetr names, are not clear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**Whiteboard**: aklapper-moreinfo",1384164660,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-uhsm2u4fy2r57ifl5now,task_description,invalid
+Offer help or descripition for parameters,"This is what the TemplateData system is for. If you fill in a <templatedata> block for the template in question, VisualEditor will show the descriptions you want.",1384842688,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uhsm2u4fy2r57ifl5now,task_subcomment,NA
+Offer help or descripition for parameters,"[""would be nice"" => please set the ""severity"" field to ""enhancement""]
+
+(In reply to comment #0)
+> It would be nice to offer informative description of each parameter when
+> filling it, to know what to fill. 
+
+What are exact steps that would allow me to reproduce this problem?
+
+> Some paremetr names, are not clear.
+
+Which exact parameter names do you refer to?",1384181509,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-uhsm2u4fy2r57ifl5now,task_subcomment,NA
+"on an existing course page ""Create source"" is used instead of ""Edit source"" in the tab at the top","On an existing course page ""Create source"" is used instead of ""Edit source"" in the tab at the top of the page. For an example, see https://en.wikipedia.org/wiki/Education_Program:University_of_Michigan/CHEM_540_%28Fall_2013%29
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384017120,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-drnulywmv5gyytjha22k,task_description,resolved
+"on an existing course page ""Create source"" is used instead of ""Edit source"" in the tab at the top","Just noting here now that this is still problematic. I'll comment on the VE bug, too. Appreciate any efforts to fix it. :)",1396986331,PHID-USER-brn4v5ta45bnw4f5as3h,False,PHID-TASK-drnulywmv5gyytjha22k,task_subcomment,NA
+"on an existing course page ""Create source"" is used instead of ""Edit source"" in the tab at the top","I filed this against the VisualEditor. I'm marking it as a duplicate, but adding Andrew Green to the cc in case he can see a good way of fixing it from within the EducationProgram extension.
+
+*** This bug has been marked as a duplicate of bug 53477 ***",1384096303,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-drnulywmv5gyytjha22k,task_subcomment,NA
+VisualEditor: JS parse error appears while enabling few gadgets for editors,"Steps to reproduce:
+
+1.Go to Preferences>Gadgets
+2.Enable few gadgets.I tried enabling all the gadgets under ""improved navigation"" , Interface : Editing and uploads and Interface:Files and Categories
+
+3.Now load the editor
+
+Observed Result:
+The following js error appears:
+
+Error: JavaScript parse error: Parse error: Illegal token in file 'MediaWiki:Gadget-popups.js' on line 1221 Error {} load.php:145
+log load.php:145
+runScript load.php:154
+checkCssHandles load.php:155
+(anonymous function) load.php:155
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+addEmbeddedCSS load.php:149
+(anonymous function)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383945720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6t3k4ac3wbqeudiatuwg,task_description,invalid
+VisualEditor: JS parse error appears while enabling few gadgets for editors,"https://test2.wikipedia.org/w/index.php?title=MediaWiki:Gadget-popups.js&action=history is from Feb 2012.
+
+Line 1221 is:
+	/*@if (@_jscript_version >= 5)
+
+https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-popups.js&action=history for example is from Nov 2013 (but also contains that line).
+
+Hence wondering if it's a ""real"" problem or just an ancient .js file on test2.",1384111250,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6t3k4ac3wbqeudiatuwg,task_subcomment,NA
+VisualEditor: JS parse error appears while enabling few gadgets for editors,It was found in test2 environment,1383946204,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6t3k4ac3wbqeudiatuwg,task_subcomment,NA
+VisualEditor: JS parse error appears while enabling few gadgets for editors,That sounds like a bug in the popups gadget. Which wiki was this on?,1383946148,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6t3k4ac3wbqeudiatuwg,task_subcomment,NA
+"VisualEditor: Subscript and Superscript applied on same text, making it placed somewhere in the middle of the preceding text","Superscript and Subscript
+
+Steps to reproduced:
+
+1.Click on the ""Edit"" button
+2.Type a text X
+3.Now type ""2"" and make it a superscript
+4.Select the text 2 and make it subscript
+
+Observed Result:
+The text ""2"" now appears somewhere in the middle of the preceding text X which neither superscript nor subscript.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12152}",1383939000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jruyips3fse6ym3bsadi,task_description,resolved
+"VisualEditor: Subscript and Superscript applied on same text, making it placed somewhere in the middle of the preceding text","Previously WONTFIXed. I'll reopen the original bug.
+
+*** This bug has been marked as a duplicate of bug 53330 ***",1384111137,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jruyips3fse6ym3bsadi,task_subcomment,NA
+VisualEditor: The table of content is not showing up until user adds sub-heading 3,"Steps to reproduce:
+
+1.Click on the Edit button
+2.Add a Heading to the page
+3.Now add a sub-heading 1
+4.Add a sub-heading 2 
+5.Click on ""Save Page""
+
+Observed Result:
+The table of contents does not appear.Now if the user adds sub-heading 3, the table of contents show up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383936780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5cydsdjiqddokog4ej2b,task_description,invalid
+VisualEditor: The table of content is not showing up until user adds sub-heading 3,This is MediaWiki native behaviour.,1383936861,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5cydsdjiqddokog4ej2b,task_subcomment,NA
+VisualEditor: Wiki markup and weird characters show up in the view mode while applying link to a text with reference,"Wiki markup and weird text
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Type a text and add a reference to it
+3.Select the text with the reference and apply link to it by clicking on link icon or pressing command+k
+4.Click on ""Save Page""
+
+Observed Result:
+Some weird text along with wiki markup shows up in the editor,
+
+See the screenshot attached.
+
+Page:Any
+Environment:Betalabs and test 2
+Browser:Chrome Version 26.0.1410.65 and firefox 20
+Reproducible :Yes
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12085}",1383869820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-z4ctrxtxswdyl3z2vpsi,task_description,resolved
+VisualEditor: Wiki markup and weird characters show up in the view mode while applying link to a text with reference,"Hi ryasmeen. 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 56250 ***",1383870381,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-z4ctrxtxswdyl3z2vpsi,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=580632339#Space_between_.22:.22_and_characters_count_increase
+
+Looks like this could potentially be the xhtml serializer converting &nbsp; to a nonbreaking space unicode char?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383851100,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_description,resolved
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 101292 merged by GWicke:
+(Bug 56733) Fixed bug serialization template args containing "" : ""
+
+https://gerrit.wikimedia.org/r/101292",1386964670,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 101259 merged by GWicke:
+Merge ""(Bug 56733) Fixed bug serialization template args containing "" : """"
+
+https://gerrit.wikimedia.org/r/101259",1386964668,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 101292 had a related patch set uploaded by GWicke:
+(Bug 56733) Fixed bug serialization template args containing "" : ""
+
+https://gerrit.wikimedia.org/r/101292",1386964478,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 101259 had a related patch set uploaded by GWicke:
+Merge ""(Bug 56733) Fixed bug serialization template args containing "" : """"
+
+https://gerrit.wikimedia.org/r/101259",1386964410,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?",Now deployed and tested fixed @ https://fr.wikipedia.org/w/index.php?title=Utilisateur%3ASsastry%2FSandbox&diff=98462286&oldid=98462267,1384808941,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 95301 merged by jenkins-bot:
+(Bug 56733) Fixed bug serialization template args containing "" : ""
+
+https://gerrit.wikimedia.org/r/95301",1384394433,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?","Change 95301 had a related patch set uploaded by Subramanya Sastry:
+(Bug 56733) Fixed bug serialization template args containing "" : ""
+
+https://gerrit.wikimedia.org/r/95301",1384385444,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+"White space before "":"" is converted to nonbreaking space unicode char?",This is caused by the template arg escaping code. Fix coming along with test case.,1384384772,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cgtmnxzfbtaknv2y77sf,task_subcomment,NA
+Drop-down menu in VisualEditor toolbar causes alternating horizontal scroll bars in dropdown and page,"As seen on mediawiki.org (running 1.23wmf2 (020fe63)) in Firefox 24.
+
+When editing in VisualEditor, the first time I click on the menu icon, the dropdown is slightly too small and a horizontal scroll bar appears inside the dropdown.
+
+The next time I click on the icon, the dropdown's width can accommodate the text and there is no scrollbar in the dropdown itself, but a horizontal scrollbar appears at the page level to accommodate the dropdown's extra width.
+
+Then, rinse and repeat: every other time, there's a scroll bar in the dropdown, and the next one there is one at the bottom of the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383820920,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-dbzugsxj63hxmjo7guoe,task_description,declined
+Drop-down menu in VisualEditor toolbar causes alternating horizontal scroll bars in dropdown and page,I can't reproduce; do you have a screenshot?,1402331915,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dbzugsxj63hxmjo7guoe,task_subcomment,NA
+Bugzilla: Set up product for OOJS and OOJS UI,"OOJS components:
+
+- General
+  The core utilities and unsorted issues.
+
+- EventEmitter
+
+- Registry
+  Registries and factories.
+
+
+Import from:
+https://github.com/trevorparscal/oojs/issues
+
+OOJS UI components:
+
+- General
+  The base classes (Dialog, Frame, Window etc.) and unsorted issues.
+
+- Elements
+  OO.ui.Element and subclasses.
+
+- Layouts
+  OO.ui.Layout and subclasses.
+
+- Tools
+  OO.ui.Tool, ToolGroup and subclasses.
+
+- Widgets
+  OO.ui.Widget and subclasses.
+
+No existing issue tracker (we'll gradually move over issues from VisualEditor and MediaWiki core as needed).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1383779220,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-djxrtouulbirtmeqhyvj,task_description,resolved
+Bugzilla: Set up product for OOJS and OOJS UI,"Per James, I've renamed the products from OOJS and OOJS UI to OOjs and OOjs UI.
+
+Sorry if this breaks anyone's permalinks. Better now than later now that the component is still fresh.",1386276878,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-djxrtouulbirtmeqhyvj,task_subcomment,NA
+Bugzilla: Set up product for OOJS and OOJS UI,"I've created a wiki page:
+ https://www.mediawiki.org/wiki/OOJS
+
+And added a link to it in the product description:
+
+ https://bugzilla.wikimedia.org/describecomponents.cgi?product=OOJS
+
+See wiki page for more information.
+
+Also, note this is all in early migration right now. Things will get clearer as things settle.",1384302859,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-djxrtouulbirtmeqhyvj,task_subcomment,NA
+Bugzilla: Set up product for OOJS and OOJS UI,"As a triager I have no idea what ""Library for working with objects"" might mean, where this is located in the stack, and how to identify tickets that should be moved to the new products. 
+Is there a wikipage covering OOJS? 
+Will https://github.com/trevorparscal/oojs/issues remain the canonical code base or will this / has this been moved to Wikimedia Git?",1383818300,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-djxrtouulbirtmeqhyvj,task_subcomment,NA
+Bugzilla: Set up product for OOJS and OOJS UI,Created the products and some of the components.,1383784953,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-djxrtouulbirtmeqhyvj,task_subcomment,NA
+VisualEditor: Categories are not being added instantly unless user refreshes the browser,"Steps to reproduce:
+
+1.Click on te Edit-beta button
+2.Click on the ""Settings"" button and go to ""Categories"" section
+3.Add a new category
+4.Click on the button ""Apply Changes""
+5.Now click on ""Save Page""
+
+Observed Result:
+The newly added category is not showing up at the end of the page unless user refreshes it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383765060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zkjur77n4a4fhw75q46a,task_description,resolved
+VisualEditor: Categories are not being added instantly unless user refreshes the browser,"Merge this with bug 48560.
+
+*** This bug has been marked as a duplicate of bug 48560 ***",1383767137,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zkjur77n4a4fhw75q46a,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter","The first letter goes to the newline
+
+Steps to Reproduce:
+
+1.Click on the Edit button in firefox
+2.Go to More>Reference
+3.Type something to add as a reference 
+
+Observed Result:
+In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56274
+
+**Attached**: {F12795}",1383694380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ztcqreqfln2w4zvztfod,task_description,resolved
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter","Unsetting ""VERIFIED""; we don't generally use that, and setting it will hide it from people's saved searches.",1384856051,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter","Verified for any page on https://test2.wikipedia.org/ with FireFox 25 using MAC OS X 10.8.5
+Example test page:  https://test2.wikipedia.org/wiki/Verify_56274",1384540116,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter",Verified in betalabs with firefox 25*,1384389969,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter",Looks like this issue got fixed .Verified in betalabs with FireFox,1384389854,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter",This is also happening now while creating a new page in firefox 20.,1383868284,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+"VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter","added a See Also, I think this is more of the cursor RETURN/BACKSPACE problem",1383694695,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ztcqreqfln2w4zvztfod,task_subcomment,NA
+VisualEditor: The text is going out of the border of the page for a lengthy content in math inspector,"Text going out of border
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Now from the toolbar click on More>LaTeX
+3.In the dialog box for LaTeX enter a long equation. For Example:
+
+
+\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}
+
+4.Save the page
+
+Observed Result:
+The text is going out of the border of the page for a lengthy content in math inspector
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12792}",1383692400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nw7eq5nisvhi4vmqmjnf,task_description,invalid
+VisualEditor: The text is going out of the border of the page for a lengthy content in math inspector,"This is ultimately up to the control of the user, and so not really a ""bug"".",1415882765,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nw7eq5nisvhi4vmqmjnf,task_subcomment,NA
+VisualEditor: The <ref> and <references/> tags are showing up in the view mode [https://gerrit.wikimedia.org/r/#/c/92595],"tags on view mode
+
+Steps to reproduce:
+1.Click on the Edit button
+2.Add a reference to the page
+3.Add a reference list at the end of the page.
+5.Click the button ""Save"" button
+
+
+
+Observed Result:
+The <ref> and <reference/> tags are showing up in the view mode
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12783}",1383683040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-66xp2mmqcy647pdvgm4x,task_description,invalid
+VisualEditor: The <ref> and <references/> tags are showing up in the view mode [https://gerrit.wikimedia.org/r/#/c/92595],Fault due to local lack of the Cite extension; fixed.,1383684301,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-66xp2mmqcy647pdvgm4x,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"Currently en.wikipedia.beta.wmflabs.org runs master of VisualEditor and a manually-synced version of Parsoid that is the same as production. This is great for testing VE as to whether it's good to deploy into production, and had served us reasonably well so far.
+
+We can't just run Parsoid as master, because (a) Parsoid master is occasionally not compatible with VisualEditor master for days or even weeks at a time as the APIs change, and (b) unless Parsoid is going to be pushed live at the same time as VisualEditor (and split into a het-deploy situation for the cluster's wmfX vs. wmfX+1 deployment) we wouldn't know if VE and Parsoid were truly OK to go out.
+
+However, bug 56583 showed that we also need to test master (and ideally also current production) of VisualEditor against *master* of Parsoid, in Labs, for automated browser testing and so on before any code goes live.
+
+Do we need en.wikipedia.beta.wmflabs.org to have en-Parsoid-master-VE-master.wikipedia.beta.wmflabs.org and en-Parsoid-master-VE-prod.wikipedia.beta.wmflabs.org duplicates? (Eww.)
+
+Also, are there other teams who need their multiple independent components and cross-dependencies? Wikidata, perhaps?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383672540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_description,invalid
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"I'm not sure I agree this bug is INVALID; we still can't reliably test master of VisualEditor against production of Parsoid or vice versa; instead, we test master of VisualEditor against master of Parsoid in Beta, and production VisualEditor against production Parsoid in production, and hope that we don't get into one of those situations again where one assumes things about the other…",1401746274,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"(In reply to comment #1)
+> In https://gerrit.wikimedia.org/r/#/c/93939/ I made the beta autoupdater to
+> run
+> `npm install` under common/php-master/extensions/Parsoid/js
+> 
+> Regardless, the parsoid instance is deployment-parsoid2     and runs its own
+> copy of the code under /srv/deployment/parsoid . So it is still being updated
+> manually by whoever has access on it.
+
+Copied that to:
+
+Bug 57233 - beta: Parsoid should continuously deploy master branch",1384852049,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"What we could potentially do in Jenkins:
+
+Whenever a change is send on VisualEditor, we could somehow boot up two Parsoid instances running master and production versions then run the VisualEditor tests against each of them.
+
+Similarly, whenever a change is send to Parasoid, we could create an instance of it and run VisualEditor tests from master and production versions.
+
+That should help both team figuring out potential issues and regressions.
+
+
+We never achieved such integration tests on any project yet. Ideally we would use labs to boot up instances that would contains all the required dependencies and run the tests there.  The infrastructure is not ready yet :-/",1383759070,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"Usually Parsoid master will work fine with VE. DOM spec changes have not been frequent in the past, and will get even less frequent over time. Empirically, the main source of issues has been a lack of integration testing rather than existing functionality breaking because of incompatibilities.
+
+So if we could only set up one version for now I'd prioritize testing against master over testing against an older version of Parsoid, in particular if that is not updated automatically. Much of the VE integration testing is also still manual at this point, which makes focusing on the most likely source of errors even more important.",1383758687,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,*** Bug 56670 has been marked as a duplicate of this bug. ***,1383756706,PHID-USER-kqibbfgfpgocyzwe32lv,True,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,For the sake of clarification: I am open to any solution :),1383755770,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing,"In https://gerrit.wikimedia.org/r/#/c/93939/ I made the beta autoupdater to run `npm install` under common/php-master/extensions/Parsoid/js
+
+Regardless, the parsoid instance is deployment-parsoid2	 and runs its own copy of the code under /srv/deployment/parsoid . So it is still being updated manually by whoever has access on it.
+
+
+The whole point of beta is to test the tips of master branches from all extensions.  That let us catch potential issue before all those tips are aggregated in a wmf branch.   To prevent new code from being executed, we use feature switching ($wgFeatureXXX = false) that still let us deploy the code and enable it selectively later on.
+
+That being said, I think it would make sense to run VisualEditor and Parsoid on the tip of master. That would probably help you detect possible breakage when deploying.",1383755721,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-7ogjkc6ddhzycfrd4aut,task_subcomment,NA
+Interface message visualeditor-mweditmodesource-title is missing in English for 1.23wmf2,"Noticed on mediawiki.org, in the VisualEditor toolbar, Menu icon, last item: <visualeditor-mweditmodesource-title>. 
+
+Special:Version says mw.o is currently running 1.23wmf2 (88c7b3f).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383655680,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-bawhmiorm2ucu6th36wp,task_description,declined
+Interface message visualeditor-mweditmodesource-title is missing in English for 1.23wmf2,Working now.,1383821933,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bawhmiorm2ucu6th36wp,task_subcomment,NA
+Interface message visualeditor-mweditmodesource-title is missing in English for 1.23wmf2,On further inspection looks like a deployment / server-side caching issue. Definitely nothing wrong with the code though.,1383670006,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-bawhmiorm2ucu6th36wp,task_subcomment,NA
+Interface message visualeditor-mweditmodesource-title is missing in English for 1.23wmf2,Sounds like a caching issue with ResourceLoader.,1383669434,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-bawhmiorm2ucu6th36wp,task_subcomment,NA
+"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE","Error message
+
+Steps to reproduce:
+Click on the edit button
+
+Observed Result:
+""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12683}",1383598080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-72rziu6fsgfsmc5bjdnx,task_description,resolved
+"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE","Fallout from fixing bug 56583. Should be okay now.
+
+*** This bug has been marked as a duplicate of bug 56583 ***",1383598243,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-72rziu6fsgfsmc5bjdnx,task_subcomment,NA
+Can drag and drop non-editable elements from outside the VE surface area,"Video made by en user Atethnekos
+
+As illustrated in the attached video, VE's drag and drop function has some odd quirks in Firefox.  One can select items from below the VE surface, such as the MediaWiki logo or the licensing disclaimer text, and drag them into the VE surface.  These items can only be added to the last line of an article.  Items seem to be added as bulleted items, increasing indent with each addition.
+
+Tested on FF 24 Win 7 with Monobook, duplicated with FF 24 and Mac OS 10.6
+
+Could not duplicate using Chrome on the above Mac OS - may be a Firefox issue.
+
+Described here:https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_12#Moving_links_on_the_page_from_outside_the_VE_surface_into_the_VE_surface
+
+And here:https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Drag_and_drop_redux
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12668}",1383594960,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-hec6fvmphtw5a6pgaa64,task_description,declined
+Can drag and drop non-editable elements from outside the VE surface area,"I confirm that it does not happen for me as well - I seem to be able to drag and drop items, but after I do that nothing changes, and as a matter of fact VE won't prompt me to save. In wikitext mode instead one can actually drag and drop stuff.",1403544337,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hec6fvmphtw5a6pgaa64,task_subcomment,NA
+Can drag and drop non-editable elements from outside the VE surface area,Can't reproduce in FF.,1403008759,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-hec6fvmphtw5a6pgaa64,task_subcomment,NA
+VisualEditor: Don't pre-annotate text for superscript and subscript,"All in superscript/subscript format
+
+Steps to reproduce:
+-Type a text x
+-Select it and make to to superscript
+-Now type 1 before x (1x) and both the letters are in superscript format
+-Now type ""/"" between these two letters (1/x) and all three letters are in superscript format
+-Now keep on typing anything before or after (1/x) all the letters are in superscript format.
+-Press ""Enter"" to go to new line
+ 
+Observed Result:
+Now the letter x and all other letters after that are in superscript format
+
+Expected Result:
+Unless selected as superscript/subscript all the texts typed before or after it should be in normal text format.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12661}",1383593280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2a2cr676hxaynicchkxu,task_description,declined
+VisualEditor: Don't pre-annotate text for superscript and subscript,"The pre-annotation described here is intentional behaviour, and used for all text styles (with some special logic for links); we could not do it for some, but I think that that would be too confusing.",1394483008,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2a2cr676hxaynicchkxu,task_subcomment,NA
+reasoning about javascript loading and test failures,"abnormal load.php requests
+
+this is essentially the same problem as shown with UploadWizard in https://bugzilla.wikimedia.org/show_bug.cgi?id=56483
+
+When run in the Sauce Labs environment, tests for VisualEditor for Chrome display many many calls to ResourceLoader that are not shown in normal operation, nor in a browser test in a local environment.  
+
+At least some of these calls to load.php fail with javascript errors, thus causing VE to fail and the test to fail.  
+
+One recent example is shown at https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/117/testReport/junit/(root)/VisualEditor%20Links/Enter_non_existing_link/
+
+Here we see two distinct calls for the same code at ext.echo.alert, the second of which fails, see screen shot.  In detail, the first call succeeds, the second fails:
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.echo.alert%2Cbase%2Cdesktop%2Coverlay&skin=vector&version=20131021T193233Z&*
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.echo.alert%2Cbase%2Cdesktop%2Coverlay&skin=vector&version=20131021T193233Z&*
+Uncaught SyntaxError: Unexpected token ILLEGAL 
+
+Also in this particular run of the test find VE loading up code for ArticleFeedback and for Gadget code for DelAutoDropdown.  VE loading gadget code in normal operation has been documented, see screen shot for invisible_iframe
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56483
+
+**Attached**: {F12626}",1383579480,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-xdv6gb57qioudhzewlqo,task_description,declined
+reasoning about javascript loading and test failures,This is no longer happening.,1384870912,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-xdv6gb57qioudhzewlqo,task_subcomment,NA
+reasoning about javascript loading and test failures,"Unless you can reproduce this outside of SauceLabs, I'm inclined to believe this is simply Chrome in SauceLabs being broken.",1383701818,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xdv6gb57qioudhzewlqo,task_subcomment,NA
+reasoning about javascript loading and test failures,"
+here is an example of a test for Flow on Chrome that repeats the same GET twice for VE code.  the first succeeds, the second gives an error: 
+
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cdata%2Cicons-vector%2Cstandalone%7Cext.visualEditor.viewPageTarget.icons-vector%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20131102T010844Z&*
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cdata%2Cicons-vector%2Cstandalone%7Cext.visualEditor.viewPageTarget.icons-vector%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20131102T010844Z&*
+Uncaught SyntaxError: Unexpected end of input
+
+Ref:  https://saucelabs.com/jobs/e0b3ed7901a14cfdb56b745c6938c12d",1383665196,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-xdv6gb57qioudhzewlqo,task_subcomment,NA
+reasoning about javascript loading and test failures,"Created attachment 13691
+gadget code in VE in normal operation
+
+**Attached**: {F12627}",1383579532,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-xdv6gb57qioudhzewlqo,task_subcomment,NA
+messages don't resolve in standalone VisualEditor,"Standalone VisualEditor shows all messages as the raw [visualeditor-message] strings in tooltips and in general button strings. 
+
+""Format"" dropdown, for example, has 
+[visualedit-rformatdropdown-format-paragraph]
+[visualedit-rformatdropdown-format-heading2]
+[visualedit-rformatdropdown-format-heading3]
+etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383414840,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-rzowuuc23degrhsrsjvb,task_description,resolved
+messages don't resolve in standalone VisualEditor,Yes,1383721313,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rzowuuc23degrhsrsjvb,task_subcomment,NA
+messages don't resolve in standalone VisualEditor,Does https://gerrit.wikimedia.org/r/#/c/93480/ fix this?,1383701956,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rzowuuc23degrhsrsjvb,task_subcomment,NA
+VE button is disable on testwiki,"On test.wikipedia.org I enabled VisualEditor through Beta Features.
+Visiting a page, display:none is applied to the VE edit button (li#ca-ve-edit). This css is at the header of the page.
+
+Since no button is shown, how anyone can use VE?
+Am I missing something?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383382320,PHID-USER-e7gwd3ou5ocdumo42srg,False,PHID-TASK-sgia5xvzrqql7odhc5nl,task_description,resolved
+VE button is disable on testwiki,"(In reply to comment #2)
+> https://test.wikipedia.org/w/index.php?title=MediaWiki:Common.
+> js&diff=184444&oldid=183093
+
+That was a test config for en.wiki that wanted it I believe, Mz should be fine with you commenting it out.",1383393079,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-sgia5xvzrqql7odhc5nl,task_subcomment,NA
+VE button is disable on testwiki,https://test.wikipedia.org/w/index.php?title=MediaWiki:Common.js&diff=184444&oldid=183093,1383392774,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-sgia5xvzrqql7odhc5nl,task_subcomment,NA
+VE button is disable on testwiki,"The button is disabled through js at MediaWiki:Common.js...
+
+It should be removed since people are asked to test it.",1383383030,PHID-USER-e7gwd3ou5ocdumo42srg,False,PHID-TASK-sgia5xvzrqql7odhc5nl,task_subcomment,NA
+Parsoid: [REGRESSION] content attribute missing from defaultsort tags,"Before https://gerrit.wikimedia.org/r/#/c/90449 :
+
+<meta property=""mw:PageProp/categorydefaultsort"" content=""Page, Main"" data-parsoid='{""src"":""{{DEFAULTSORT:Page, Main}}"",""dsr"":[1800,1826,null,null]}'/>
+
+After:
+
+<meta property=""mw:PageProp/categorydefaultsort"" data-parsoid='{""src"":""{{DEFAULTSORT:Page, Main}}"",""a"":{""content"":null},""sa"":{""content"":""Page, Main""},""dsr"":[1800,1826,null,null]}'/>
+
+This breaks editing of defaultsort in VisualEditor for obvious reasons, but it also triggers a failure mode in VisualEditor where missing content attributes aren't expected and are normalized to content=""null"", triggering corruption warnings and changing {{DEFAULTSORT:Foo}} to {{DEFAULTSORT:null}}. I'll fix that in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383337560,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5hxk5ete5tb4osa6g3ma,task_description,resolved
+Parsoid: [REGRESSION] content attribute missing from defaultsort tags,"Change 93108 merged by jenkins-bot:
+Bug 56489: Allow content attribute on parsoid-generated meta tokens
+
+https://gerrit.wikimedia.org/r/93108",1383342509,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5hxk5ete5tb4osa6g3ma,task_subcomment,NA
+Parsoid: [REGRESSION] content attribute missing from defaultsort tags,"Change 93108 had a related patch set uploaded by GWicke:
+Bug 56489: Allow content attribute on parsoid-generated meta tokens
+
+https://gerrit.wikimedia.org/r/93108",1383341411,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5hxk5ete5tb4osa6g3ma,task_subcomment,NA
+"VisualEditor: <ooui-toolbar-more> tag is showing up instead of ""More"" text in the toolbar in test2 environment","<ooui-toolbar-more> tag
+
+Steps to reproduce:
+
+-Click on the Edit button on a page in test 2 environment
+-Observe the toolbar
+
+Observed Result:
+
+<ooui-toolbar-more> tag is showing up instead of ""More"" text in the toolbar in test2 environment
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12443}",1383334620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qgb5fgt6vmjtfvknn43z,task_description,resolved
+"VisualEditor: <ooui-toolbar-more> tag is showing up instead of ""More"" text in the toolbar in test2 environment","Unsetting ""VERIFIED""; we don't generally use that, and setting it will hide it from people's saved searches.",1384856040,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qgb5fgt6vmjtfvknn43z,task_subcomment,NA
+"VisualEditor: <ooui-toolbar-more> tag is showing up instead of ""More"" text in the toolbar in test2 environment","Cant find this issue in test2 now. Therefore, changing the status to resolved.",1383345126,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qgb5fgt6vmjtfvknn43z,task_subcomment,NA
+"VisualEditor: ""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment","""Error:Database query error ""
+
+Steps to reproduce:
+-Click on the Edit-beta button
+-Type anything to made some changes in the CE
+-Click on the Save button 
+
+Observed Result:
+""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment.
+
+However,attempting to save the content for the second time is saving the content.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12442}",1383334260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kimy5ztgryvb4j5fhi5i,task_description,resolved
+"VisualEditor: ""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment","Unsetting ""VERIFIED""; we don't generally use that, and setting it will hide it from people's saved searches.",1384856027,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kimy5ztgryvb4j5fhi5i,task_subcomment,NA
+"VisualEditor: ""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment","Yes, now it looks fixed.Can not reproduce it anymore.",1383335670,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kimy5ztgryvb4j5fhi5i,task_subcomment,NA
+"VisualEditor: ""Error:Database query error "" is showing up while attempting to save the content for the first time in test2 environment",Try again? I've just fixed a database error that might actually be related,1383335394,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-kimy5ztgryvb4j5fhi5i,task_subcomment,NA
+reasoning about javascript loading and test failures,"WIP: 
+
+I am seeing a number of failures in the Selenium tests when running for Chrome. The failures seem to be caused by many calls to ResourceLoader, many repeated, many seemingly unnecessary, and some of these calls fail.  Other calls to other unexpected sources are also evident, this is just a single example.  
+
+Each failed test shows a different set of calls to load.php.  Here is one example:
+
+A normal load of UW on beta commons has 2 calls for two jquery things, one for the spinner and one for ULS. See screen shot. 
+
+But a failed automated test shows multiple repeated calls for jquery.ui.button. See screen shot. https://saucelabs.com/jobs/8fd3f6a483db46da9c4cfbbdcf7d2449
+
+A reference to jquery.ui.button is found only one place in all of the UploadWizard source code, line 473 of UploadWizardHooks.php.  It seem to be a dependency for ext.uploadWizard.campaign
+
+What causes UploadWizard to make multiple calls for a jquery feature jquery.ui.button that it would not normally need?
+
+Under what circumstances would this happen to a normal user?
+
+When UW makes these multiple calls, it seems that what is returned from some of those calls is corrupt, possibly truncated, since the errors tend to be 'Uncaught SyntaxError: Unexpected token ILLEGAL' and similar. 
+
+I think VisualEditor has a similar problem, possibly indicated in https://bugzilla.wikimedia.org/show_bug.cgi?id=55801 (see screen shot there)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56567",1383333720,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ccs2prus5tuvbhududhj,task_description,declined
+reasoning about javascript loading and test failures,no longer happening as of about Nov 15,1384870964,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ccs2prus5tuvbhududhj,task_subcomment,NA
+reasoning about javascript loading and test failures,"Created attachment 13659
+too many calls to load.php
+
+**Attached**: {F12435}",1383333823,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ccs2prus5tuvbhududhj,task_subcomment,NA
+reasoning about javascript loading and test failures,"Created attachment 13658
+normal operation
+
+**Attached**: {F12434}",1383333792,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ccs2prus5tuvbhududhj,task_subcomment,NA
+VisualEditor:Show the link to a missing page as a red link as it shows in the dialog,"Steps to reproduce:
+-Click on the button Edit-beta
+-Type a text to insert the link
+-Click on the link icon from the toolbar or press ctrl+k or command+k
+-Now select a new page which is not yet created
+-Save the content
+
+Expected Result:
+The link to a missing page should be shown as a red link as it shows in the dialog
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383264480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zvbelbjtso7n2rf7unpl,task_description,resolved
+VisualEditor:Show the link to a missing page as a red link as it shows in the dialog,"Merging this with bug 37901, which covers this and a little more.
+
+*** This bug has been marked as a duplicate of bug 37901 ***",1383277462,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvbelbjtso7n2rf7unpl,task_subcomment,NA
+VisualEditor: Show suggested links' status with an indicator during auto-suggest,"A link status indicator (red link, redirect, etc.)
+during autosuggest would be great, as long as it fires asynchronously
+and the user isn't blocked on actions while it's loading.
+[Suggested by Erik Moeller]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383256380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-445qwg6xrym7xzuyvyec,task_description,resolved
+VisualEditor: Show suggested links' status with an indicator during auto-suggest,"We did this using sections instead of icons, but marking as FIXED anyway.",1395359396,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-445qwg6xrym7xzuyvyec,task_subcomment,NA
+"central notice banner has js error, causes bogus test failures","URLs such as the following examples appear in several browser tests and cause intermittent test failures in browsers other than Firefox, for example for UploadWizard on beta commons and for AFTv5 on beta enwiki: 
+
+http://bits.beta.wmflabs.org/commons.wikimedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin.clearcookie%7Cext.uls.i18n%2Cime%2Cinit%2Cinterface%2Clanguagenames%2Cpreferences%2Cwebfonts%7Cext.uls.webfonts.repository%7Cjquery.client%2Ccookie%2CdelayedBind%2Ci18n%2CjStorage%2Cjson%2CmwExtension%2Ctipsy%2Culs%2Cwebfonts%7Cjquery.uls.data%2Cgrid%7Cmediawiki.Uri%2Capi%2Cnotify%2Cuser%2Cutil%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cskins.vector.js%7Cwikibase.client.init&skin=vector&version=20131026T061711Z&*
+view data
+
+[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin%7Cext.uls.i18n%2Cime%2Cinit%2Cinterface%2Clanguagenames%2Cpreferences%2Cwebfonts%7Cext.uls.webfonts.repository%7Cext.visualEditor.viewPageTarget.init%7Cext.wikimediaShopLink.core%7Cjquery.byteLength%2Cclient%2Ccookie%2CdelayedBind%2Ci18n%2CjStorage%2Cjson%2CmwExtension%2Ctipsy%2Culs%2Cwebfonts%7Cjquery.uls.data%2Cgrid%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.language.data%2Cinit%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cskins.vector.js%7Cwikibase.client.init%2Cnolanglinks&skin=vector&version=20131031T104306Z&*
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383230520,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-dgtigim34wqholkwxjpw,task_description,declined
+"central notice banner has js error, causes bogus test failures",I guess that issue has been fixed somehow. If it is still causing browser tests to choke please reopen.,1391375202,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dgtigim34wqholkwxjpw,task_subcomment,NA
+"central notice banner has js error, causes bogus test failures","the errors seen are: 
+
+javascript error: Uncaught SyntaxError: Unexpected token ILLEGAL
+
+javascript error: Uncaught SyntaxError: Unexpected end of input",1383230746,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-dgtigim34wqholkwxjpw,task_subcomment,NA
+"VisualEditor: Two adjacent paragraphs made lists in separate actions are made into two lists, not one list with two items","Wrongly ordered list
+
+Steps to reproduce:
+
+-Click on the ""Edit"" button of the Visual Editor.
+-Have multiple lines to be listed in a Numbered list.
+For Example:
+Item One
+Item Two
+-Now select the first line ""Item One"" and click on the icon of ""Numbered list"" to number this item
+-Now again select the both lines ""Item One"" and ""Item Two""
+-Click on the icon of ""Numbered List""
+
+Observed Result:
+Both the lines are now numbered with order 1 like following:
+
+1.Item One
+1.Item Two
+
+Expected Result:
+The numbered list should maintain the continuous order if selected a previously ordered line like following:
+
+1.Item One
+2.Item Two
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12117}",1383079200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-y4pcs6u7xh3tw5y7ea4f,task_description,declined
+"VisualEditor: Two adjacent paragraphs made lists in separate actions are made into two lists, not one list with two items",This is intentional behaviour; re-titling and marking WONTFIX.,1394504425,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y4pcs6u7xh3tw5y7ea4f,task_subcomment,NA
+VisualEditor: Do mass DM round trip testing with Wikipedia content,"Like, Parsoid's round-trip testing, we should do DM round-trip testing with content from Wikipedia. dirtydiffbot does this to some extent, but it tests the Parsoid output rather than the DM output and it uses the UI, which is hacky. We should have a proper service that just tests the DM HTML output is clean, which requires a test runner for that purpose in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383070560,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hl7fehn5dewfavdk36so,task_description,resolved
+VisualEditor: Do mass DM round trip testing with Wikipedia content,"
+
+*** This bug has been marked as a duplicate of bug 50513 ***",1393640838,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hl7fehn5dewfavdk36so,task_subcomment,NA
+VisualEditor: Controls stop working when browser window is small,"click Edit/beta, nothing happens at this size
+
+this seems to manifest in several ways: 
+
+* 'Edit/beta' link stops working, see screen shot
+* Indent/outdent buttons disappear, see screen shot
+* possibly more
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12066}",1383056100,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-gsqvj57elluda2nmu55f,task_description,resolved
+VisualEditor: Controls stop working when browser window is small,AFAICT this is now fixed.,1404168962,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gsqvj57elluda2nmu55f,task_subcomment,NA
+VisualEditor: Controls stop working when browser window is small,"I tried to reproduce this on my end using FireFox and Chrome browser and what I observed is re-sizing the window distorts the visual editor toolbar placement, which was making Indent/Outdent and other buttons hide behind the search box sometimes.
+
+But ""Edit/beta"" button was working fine in my browser.
+
+See the screenshot attached",1383090520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gsqvj57elluda2nmu55f,task_subcomment,NA
+VisualEditor: Controls stop working when browser window is small,"Created attachment 13626
+resize window
+
+**Attached**: {F12068}",1383090459,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gsqvj57elluda2nmu55f,task_subcomment,NA
+VisualEditor: Controls stop working when browser window is small,"Created attachment 13614
+indent/outdent controls not loaded in page at this size
+
+**Attached**: {F12067}",1383056197,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-gsqvj57elluda2nmu55f,task_subcomment,NA
+VisualEditor: Hitting Enter in a block slug does not create a new line,"Try to VEdit
+https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=578251398
+or
+https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&oldid=62136875 .
+
+Place your cursor at the bottom of the page.
+
+Hit Enter.
+
+Expected result: a new line is created.
+Actual outcome: nothing happens.
+
+Please note that this works fine if instead you type something, and hit Enter after doing so.
+
+It happens on both FF and Chrome with both Vector or Monobook.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382960700,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-43dibnfvzllm4nbj6ga3,task_description,invalid
+VisualEditor: Hitting Enter in a block slug does not create a new line,"This is because the cursor in these documents is in a block slug, and so VisualEditor stops you from creating pointless blank lines that won't be saved. Marking as INVALID, but this should (hopefully) be made much clearer with the proposed changes to block slugs to make them more obviously special.",1393983083,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-43dibnfvzllm4nbj6ga3,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"I do not know how to check if this is already happening or not. This is the list of repositories that currently contain Ruby code:
+
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/selenium
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/CirrusSearch
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Flow
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/MobileFrontend
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Translate
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/TwnMainPage
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/UniversalLanguageSelector
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/VisualEditor
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Wikibase
+https://gerrit.wikimedia.org/r/#/admin/projects/qa/browsertests
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382704500,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_description,resolved
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"  mwext-VisualEditor-ruby1.9.3lint: SUCCESS
+  mwext-Wikibase-ruby1.9.3lint: SUCCESS
+
+\O/
+
+Thank you :-]",1382708537,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91867 merged by jenkins-bot:
+trigger rubylint for VisualEditor and Wikibase
+
+https://gerrit.wikimedia.org/r/91867",1382708377,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91867 had a related patch set uploaded by Hashar:
+trigger rubylint for VisualEditor and Wikibase
+
+https://gerrit.wikimedia.org/r/91867",1382708347,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"  mwext-CirrusSearch-ruby1.9.3lint: SUCCESS
+  mwext-Flow-ruby1.9.3lint: SUCCESS
+  mwext-Translate-ruby1.9.3lint: SUCCESS
+  mwext-TwnMainPage-ruby1.9.3lint: SUCCESS
+
+I forgot the VisualEditor and Wikibase triggers :(",1382708255,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91862 merged by jenkins-bot:
+ruby1.9.3 lint jobs for some repositories
+
+https://gerrit.wikimedia.org/r/91862",1382707581,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91862 had a related patch set uploaded by Hashar:
+ruby1.9.3 lint jobs for some repositories
+
+https://gerrit.wikimedia.org/r/91862",1382707520,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91853 merged by jenkins-bot:
+ruby1.9.3 lint jobs for some repositories
+
+https://gerrit.wikimedia.org/r/91853",1382707232,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Change 91853 had a related patch set uploaded by Zfilipin:
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code
+
+https://gerrit.wikimedia.org/r/91853",1382705512,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"The rest:
+
+CirrusSearch
+Flow
+Translate
+TwnMainPage
+VisualEditor
+Wikibase",1382705372,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"[2:39p] hashar:
+the current jobs are:
+mediawiki-selenium-ruby1.9.3lint
+mwext-MobileFrontend-ruby1.9.3lint
+mwext-UniversalLanguageSelector-ruby1.9.3lint
+qa-browsertests-ruby1.9.3lint",1382704967,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Ruby lint should run after every patch set submission for all repositories that contain Ruby code,"Looks like this is the repo:
+
+https://gerrit.wikimedia.org/r/#/admin/projects/integration/jenkins-job-builder-config
+
+and this is example:
+
+https://gerrit.wikimedia.org/r/#/c/57730/2/mediawiki-extensions.yaml",1382704722,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-imfh6gg55vyil5deeyj5,task_subcomment,NA
+Set up Code Climate for all repositories that have Ruby code,"We have Code Climate set up for several repositories. Set it up for all repositories with Ruby code.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382690400,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-xjqjhle7et4eysgadisw,task_description,resolved
+Set up Code Climate for all repositories that have Ruby code,"Change 91830 merged by jenkins-bot:
+Set up Code Climate for all repositories that have Ruby code
+
+https://gerrit.wikimedia.org/r/91830",1382692753,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xjqjhle7et4eysgadisw,task_subcomment,NA
+Set up Code Climate for all repositories that have Ruby code,"Change 91830 had a related patch set uploaded by Zfilipin:
+Set up Code Climate for all repositories that have Ruby code
+
+https://gerrit.wikimedia.org/r/91830",1382692577,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xjqjhle7et4eysgadisw,task_subcomment,NA
+Set up Code Climate for all repositories that have Ruby code,"Existing:
+
+https://codeclimate.com/github/wikimedia/qa-browsertests
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-MobileFrontend
+
+New:
+
+https://codeclimate.com/github/wikimedia/mediawiki-selenium
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-CirrusSearch
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-Flow
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-Translate
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-TwnMainPage
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-VisualEditor
+https://codeclimate.com/github/wikimedia/mediawiki-extensions-Wikibase",1382691589,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-xjqjhle7et4eysgadisw,task_subcomment,NA
+qa/browsertests log in twice,"probably the new ruby gem.  see the video at 
+
+https://wmf.ci.cloudbees.com/job/browsertests-en.wikipedia.beta.wmflabs.org-windows-internet_explorer_10/248/testReport/junit/(root)/Page/Move_existing_page_dialog/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382641860,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-m5ly62fnpxkni7on4d5x,task_description,resolved
+qa/browsertests log in twice,"Change 91876 merged by jenkins-bot:
+[browser test] Workaround for the problem when Cucumber hook executes twice
+
+https://gerrit.wikimedia.org/r/91876",1382716505,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+qa/browsertests log in twice,"Change 91881 merged by Zfilipin:
+no need to log in twice
+
+https://gerrit.wikimedia.org/r/91881",1382716387,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+qa/browsertests log in twice,"Change 91881 had a related patch set uploaded by Zfilipin:
+no need to log in twice
+
+https://gerrit.wikimedia.org/r/91881",1382715683,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+qa/browsertests log in twice,"Change 91876 had a related patch set uploaded by Zfilipin:
+[browser test] Workaround for the problem when Cucumber hook executes twice
+
+https://gerrit.wikimedia.org/r/91876",1382714776,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+qa/browsertests log in twice,"There is a problem with running hooks twice.
+
+See:
+
+https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/107/testReport/(root)/VisualEditor%20Headings/Cycle_through_headings_values__outline_example_____Paragraph_____Editing____/",1382712122,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-m5ly62fnpxkni7on4d5x,task_subcomment,NA
+Fail on trying to target a person with a message,"2013-10-23 - 13:04:35  <marktraceur> !e VisualEditor | Svetlana
+2013-10-23 - 13:04:36  <wm-bot> Svetlana: https://www.mediawiki.org/wiki/Extension:VisualEditor_%7c_Svetlana
+
+It captured the "" | Svetlana"" part. That's very annoying.
+
+The message is currently https://www.mediawiki.org/wiki/Extension:$wiki_encoded_* - maybe that's wrong?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382559120,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-ya3ww47fwcb2aqeuzqly,task_description,resolved
+Fail on trying to target a person with a message,"
+
+*** This bug has been marked as a duplicate of bug 51259 ***",1382559178,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-ya3ww47fwcb2aqeuzqly,task_subcomment,NA
+Enable VisualEditor for the Portal and Book namespaces on enwiki,"Following on from bug 48430 and bug 56000.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382460120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-waufzrnebrjzcfjas3t4,task_description,resolved
+Enable VisualEditor for the Portal and Book namespaces on enwiki,Now done.,1382640853,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-waufzrnebrjzcfjas3t4,task_subcomment,NA
+Enable VisualEditor for the Portal and Book namespaces on enwiki,"Change 91198 merged by jenkins-bot:
+enwiki: Enable VisualEditor for Portal: and Book:
+
+https://gerrit.wikimedia.org/r/91198",1382640825,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-waufzrnebrjzcfjas3t4,task_subcomment,NA
+Enable VisualEditor for the Portal and Book namespaces on enwiki,"Change 91198 had a related patch set uploaded by Jforrester:
+enwiki: Enable VisualEditor for Portal: and Book:
+
+https://gerrit.wikimedia.org/r/91198",1382460198,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-waufzrnebrjzcfjas3t4,task_subcomment,NA
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,"As requested at https://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Ajuda#Editor_visual_a_Viquiprojecte
+
+Please enable VisualEditor in ca.wikipedia.org at the ""Viquiprojecte"" namespace.
+
+Having it enabled in ""Portal"" wold be useful as well.
+
+Currently VE is available also to anonymous users in the Main namespace at ca.wiki. The same behavior can be applied to these other namespaces. Thank you!
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1382459760,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_description,resolved
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,And deployed. It works. Thank you!,1382724903,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_subcomment,NA
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,Now done.,1382640836,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_subcomment,NA
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,"Change 91197 merged by jenkins-bot:
+cawiki: Enable VisualEditor for Portal: and Viquiprojecte:
+
+https://gerrit.wikimedia.org/r/91197",1382640724,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_subcomment,NA
+Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace,"Change 91197 had a related patch set uploaded by Jforrester:
+cawiki: Enable VisualEditor for Portal: and Viquiprojecte:
+
+https://gerrit.wikimedia.org/r/91197",1382460289,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m2ogvfsvhbevnrvvzb4q,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*","VE works well-enough for pages that aren't signed, except for ones where the pages rely on fiddly or partial wikitext munging, like the Template and MediaWiki namespaces. Consequently, we should be OK to enable VE in a larger number of namespaces, rather than just NS_MAIN and NS_USER:
+
+* NS_FILE	
+* NS_HELP	
+* NS_CATEGORY
+* wgContentNamespaces generally?
+
+Part of the fun are things like the portal namespace which is defined per-wiki.
+
+See also bug 55792 for comments about enabling VE in all namespaces, and why I think that's a bad idea.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382372460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_description,resolved
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*",Now done.,1382640790,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*","Change 90923 merged by jenkins-bot:
+Enable VisualEditor for NS_FILE, NS_HELP, NS_CATEGORY
+
+https://gerrit.wikimedia.org/r/90923",1382640276,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*","(In reply to comment #2)
+> How well does VisualEditor handle the non-editable portions of File and
+> Category pages? Do they just disappear when VE is invoked?
+
+Those aren't on the page, they're just composited on in read mode. See for example https://www.mediawiki.org/wiki/Category:Requests_for_comment or https://www.mediawiki.org/wiki/File:2013-08-21_Flow_prototype.png to take two pages at random from MWwiki.",1382455942,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*",How well does VisualEditor handle the non-editable portions of File and Category pages? Do they just disappear when VE is invoked?,1382433130,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*","Change 90923 had a related patch set uploaded by Jforrester:
+Enable VisualEditor for NS_FILE, NS_HELP, NS_CATEGORY
+
+https://gerrit.wikimedia.org/r/90923",1382373282,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2by3cfwyw4mn3t7yyzoq,task_subcomment,NA
+"VisualEditor: Page fragment parsing not interpreting raw citation template inserted into a ""content"" block correctly","Intention:  To copy a reference (copied from en.wp's article on [[Vanilla]]), using the ""+"" system within the transclusion editor into another article (Simple English's [[Vanilla]]).
+
+
+Expectation:  That the ref dialog box would display the citation correctly.
+
+
+Steps to reproduce:
+
+1)  Click the menu item to insert a reference.
+
+2)  Click the transclusion item to insert a template.
+
+3)  Click the ""+"" and the ""[ ]"" to insert 'content' rather than individual parameters.
+
+4)  Paste in the citation template, copied out of the English Wikipedia.  The citation template entered was:
+{{cite web | title = FAO's Statistical Database - FAOSTAT | year = 2011 | url = http://faostat3.fao.org}}
+
+5)  Click ""Apply changes"".
+
+
+Result:
+
+See https://commons.wikimedia.org/wiki/File:VisualEditor_Oct_2013_ref_dialog_box_with_oddly_formatted_citation_template.png
+
+It should have displayed within the reference dialog box as:
+
+""FAO's Statistical Database - FAOSTAT"". 2011.
+
+with the first part being the link.  Instead, it added a second copy of the URL at the end:
+
+""FAO's Statistical Database - FAOSTAT"". 2011.  http://faostat3.fao.org/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382051580,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-xbuo4fcnx4oupw7ol2me,task_description,resolved
+"VisualEditor: Page fragment parsing not interpreting raw citation template inserted into a ""content"" block correctly",Fixed a while ago; sorry for slow triage.,1398113380,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xbuo4fcnx4oupw7ol2me,task_subcomment,NA
+"VisualEditor: Page fragment parsing not interpreting raw citation template inserted into a ""content"" block correctly",Bug 59154 seems related.,1388857771,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-xbuo4fcnx4oupw7ol2me,task_subcomment,NA
+Customize Jenkins email notifications,"Could we use the same subject heading for these emails so they grouped
+into one thread? e.g. QA Report and move the current subject into the
+email body itself?
+
+Currently I am getting lots of mails in the form:
+Build failed in Jenkins: MobileFrontend-en.m.wikipedia.org-linux-firefox #97
+
+and it is very hard to group and filter them.
+
+As a result I tend to ignore them due to too much noise which is bad :).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**Whiteboard**: gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks
+**URL**: https://www.google-melange.com/gci/task/view/google/gci2013/5243150582939648",1381984200,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_description,resolved
+Customize Jenkins email notifications,"I have another way to resolve.
+
+I can generate an HTML file and send it as an email body.
+
+
+```
+Changing email body programmatically is possible now.
+
+You can go to Manage Jenkins > Configure System and set Default Content as
+           ${FILE,path=""email-body.html""}​​​​​​​
+
+           under Extended E-mail Notification area.
+
+
+Now, you just have to generate email-body.html file programmatically directly under your workspace root.
+
+Also, make sure that default content type is set to HTML.
+```
+
+src: https://softwaretestingboard.com/qna/2205/modify-email-subject-jenkins-using-automated-script-written",1499262343,PHID-USER-3clat6h5vxkg6w4ifzdn,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Change 106513 merged by Cmcmahon:
+Use new e-mail template
+
+https://gerrit.wikimedia.org/r/106513",1389290678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Change 106513 had a related patch set uploaded by Zfilipin:
+Use new e-mail template
+
+https://gerrit.wikimedia.org/r/106513",1389286652,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Change 103114 merged by Cmcmahon:
+Add jenkins email template for better email notifications
+
+https://gerrit.wikimedia.org/r/103114",1387812580,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Change 103114 had a related patch set uploaded by Sn1per:
+Add jenkins email template for better email notifications
+
+https://gerrit.wikimedia.org/r/103114",1387650250,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 14048
+after
+
+**Attached**: {F11948}",1386685401,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 14047
+before
+
+**Attached**: {F11947}",1386685379,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"As far as I am concerned, this bug is resolved. If you need more/less information in Jenkins e-mail notification, leave a comment. See attached e-mail for ""before"" and ""after"".",1386685353,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Asked cloudbees to upload the template:
+
+https://cloudbees.zendesk.com/requests/14940",1386681939,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"(In reply to comment #15)
+> Created attachment 13967 [details]
+> First version of jenkins template ready for testing
+> 
+> 1. To use this template, place it under $JENKINS_HOME/email-templates/
+> 2. make sure email-ext plugin is installed
+> 3. Under the job config for post-build actions, remove ""email notification""
+> and
+> add ""editable email notification""
+> 4. Change default content type to html
+> 5. Change body to ${SCRIPT, template=""wikimedia-jenkins.template-1""}
+> 6. Optional - change the subject using the token references; here is the one
+> i
+> used: ${PROJECT_NAME} ${BUILD_NUMBER} - ${BUILD_STATUS}
+> 7. Set the recipients, etc.
+> 8. Open Advanced Settings... and there you can change when an email
+> notification is triggered.
+
+If you want the subject to be constant for one build, make the subject just ${PROJECT_NAME}
+
+//attachment wikimedia-jenkins-1.template ignored as obsolete//",1386434031,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"(In reply to comment #26)
+> If you would like to continue working on the template (making it look more
+> like
+> Jenkins web page) I will create another task.
+
+Sure, I would definitely like to finish up this template.",1386371967,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Final email template (for now)
+
+**Attached**: {F11946}",1386371916,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey, the last e-mail that I got from your local Jenkins looked good to me! Please upload the template here so I can test it with our Jenkins and if it works I will close the task.
+
+If you would like to continue working on the template (making it look more like Jenkins web page) I will create another task.
+
+If you would like to work on something else, we have plenty of tasks.",1386330549,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"(In reply to comment #24)
+> Created attachment 13990 [details]
+> how e-mail notification after failed test should look like
+
+Do you want the entire table there in the email?  Right now I have the notifications working with everything and it looks pretty close to the jenkins build page.
+
+**Attached**: {F11945}",1386292055,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 13990
+how e-mail notification after failed test should look like
+
+**Attached**: {F11945}",1386256542,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey,
+
+see attached file on how an e-mail notification after failed test should look like. It is generated by this test:
+
+https://geofbot.ci.cloudbees.com/job/test2/lastCompletedBuild/testReport/",1386256508,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"I forgot to say, now you can test e-mail notifications using your jobs. If you have any questions, let me know.",1386195152,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 13979
+e-mail notification with failed tests
+
+**Attached**: {F11944}",1386166633,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey,
+
+I did not want to mess up existing job (test), so I have created another one (test2). Short documentation on how to set up a job to run tests is available[1]. I have cloned browsertests[2] repository and the job runs tests from login.feature[3] file. I will attach e-mail that was sent after the job failed.
+
+1: https://github.com/wikimedia/mediawiki-selenium/blob/master/docs/job.md
+2: https://github.com/wikimedia/qa-browsertests
+3: https://github.com/wikimedia/qa-browsertests/blob/master/features/login.feature",1386166601,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Example html 3
+
+The example html for template 1.1
+
+//attachment progress3.html ignored as obsolete//",1386125139,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Template v1.1
+
+Better version with some bugs ironed out
+
+Would be nice if someone tested out the ""tests"" part of it because I don't have tests set up for my local jenkins build.
+
+//attachment wikimedia-jenkins.template ignored as obsolete//",1386124914,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Example html 2
+
+I don't have tests set up on my jenkins, so unfortunately I couldn't test that aspect of the template
+
+I replaced all of the LAN image references with a cloudbees link so they would work, but the links to the build will be broken.
+
+//attachment progress2.html ignored as obsolete//",1386107476,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey, can you attach an example e-mail, so we can see if the template does what we need?",1386080408,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"First version of jenkins template ready for testing
+
+1. To use this template, place it under $JENKINS_HOME/email-templates/
+2. make sure email-ext plugin is installed
+3. Under the job config for post-build actions, remove ""email notification"" and add ""editable email notification""
+4. Change default content type to html
+5. Change body to ${SCRIPT, template=""wikimedia-jenkins.template-1""}
+6. Optional - change the subject using the token references; here is the one i used: ${PROJECT_NAME} ${BUILD_NUMBER} - ${BUILD_STATUS}
+7. Set the recipients, etc.
+8. Open Advanced Settings... and there you can change when an email notification is triggered.
+
+//attachment wikimedia-jenkins-1.template ignored as obsolete//",1386046436,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Progress on email-ext customization
+
+//attachment progress1.html ignored as obsolete//",1385856189,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey, feel free to attach the e-mail to this bug, or to send it to me, so I could take a look.",1385821722,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Progress!
+
+I managed to extract the first line of console output to find who started the job.  It took a lot of guesswork (I have never coded in Groovy before, especially not within a HTML :P)",1385782467,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Geoffrey, this might be the problematic part: ""Have your Jenkins administrator place the script inside JENKINS_HOME\email-templates."" (from plugin documentation[1]).
+
+You should contact cloudbees support and ask how to do it.
+
+1: https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin",1385740730,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,Cloudbees URL: https://geofbot.ci.cloudbees.com/job/test/,1385735855,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Hi Geoffrey and welcome!
+
+For future reference, if you get stuck you can ask questions here, at #wikimedia-qa freenode IRC channel or at QA mailing list[1].
+
+To answer your question, start with either installing Jenkins[2] on your local machine or create a free account at a hosted Jenkins service, like Cloudbees[3].
+
+When you have a test Jenkins instance, create a few jobs and start sending e-mail notifications to your e-mail.
+
+Then install the plugin[4] Jeff has suggested and try changing the e-mail notifications so they look more like this report[5].
+
+If you get stuck, or if you have any questions, let us know.
+
+1: https://lists.wikimedia.org/mailman/listinfo/qa
+2: http://jenkins-ci.org/
+3: http://www.cloudbees.com/
+4: https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
+5: https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/164/",1385580760,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Hey, I'm GEOFBOT from GCI!  I think I'll try out this task, but I have no clue how to start out.  Where should I start out?",1385572655,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"(In reply to comment #6)
+> From what I understand, the people would like the e-mail notification to look
+> similar to this page:
+> 
+> https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.
+> wmflabs.org-linux-chrome/164/
+
+Yeah, that would be *much* more useful. It would also be nice to still get the recent changes that were checked in like in the current mail, eg:
+
+Changes:
+
+[roan.kattouw] Share code between conflict resolution and the edit source
+switch
+
+[roan.kattouw] Don't build out save dialog when initializing editor
+
+[roan.kattouw] Use InputWidget facilities in byte limit counter
+
+[krinklemail] Remove the toolbar tracker
+
+And if they could provide links to changesets gerrit, that would be even better :)
+
+It would also be good if there was a direct link provided to the build in jenkins.",1385498734,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"From what I understand, the people would like the e-mail notification to look similar to this page:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/164/",1385490092,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"If you do not have an e-mail client, this is how an e-mail notification for a failed Jenkins job looks like:
+
+
+
+From: jenkins-no-reply@cloudbees.com 
+To:  
+Date: Tue, 26 Nov 2013 19:02:57 +0100 
+Subject: Build failed in Jenkins: VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox #172 
+ 
+See <https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/172/changes>
+
+Changes:
+
+[roan.kattouw] Share code between conflict resolution and the edit source switch
+
+[roan.kattouw] Don't build out save dialog when initializing editor
+
+[roan.kattouw] Use InputWidget facilities in byte limit counter
+
+[krinklemail] Remove the toolbar tracker
+
+------------------------------------------
+Started by user Chris Mcmahon
+Building remotely on s-e4476767 in workspace <https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/ws/>
+Cloning the remote Git repository
+Cloning repository https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor
+git --version
+git version 1.7.11.7
+Checking out Revision 07464e20a535fe1efdbd7f8e862ff8f7b3825722 (origin/master)
+[VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox] $ /bin/sh -xe /tmp/hudson495896231200628031.sh
++ export MEDIAWIKI_USER=Selenium_user
++ MEDIAWIKI_USER=Selenium_user
++ export MEDIAWIKI_PASSWORD_VARIABLE=MEDIAWIKI_PASSWORD_SELENIUM_USER_WMFLABS_ORG
++ MEDIAWIKI_PASSWORD_VARIABLE=MEDIAWIKI_PASSWORD_SELENIUM_USER_WMFLABS_ORG
++ export BROWSER_LABEL=firefox
++ BROWSER_LABEL=firefox
++ export MEDIAWIKI_URL=http://en.wikipedia.beta.wmflabs.org/wiki/
++ MEDIAWIKI_URL=http://en.wikipedia.beta.wmflabs.org/wiki/
++ curl -s -o use-ruby https://repository-cloudbees.forge.cloudbees.com/distributions/ci-addons/ruby/use-ruby
++ RUBY_VERSION=2.0.0-p247
++ source ./use-ruby
+++ [[ -z 2.0.0-p247 ]]
+++ ruby187='1.8.7-*'
+++ [[ 2.0.0-p247 == 1.8.7-* ]]
+++ BASE=/scratch/jenkins/addons
+++ mkdir -p /scratch/jenkins/addons
+++ '[' '!' -f /scratch/jenkins/addons/use.sh ']'
+++ wget -q -P /scratch/jenkins/addons https://repository-cloudbees.forge.cloudbees.com/distributions/ci-addons/lib/use.sh
+++ . /scratch/jenkins/addons/use.sh
+++ mkdir -p /scratch/jenkins/addons/ruby
++++ addon_architecture
++++ uname -m
+++ ruby_name=ruby-2.0.0-p247-x86_64
+++ '[' '!' -f /scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64.tar.bz2 ']'
++++ addon_platform
+++++ head -n 1
+++++ cat /etc/issue
++++ issue='Fedora release 17 (Beefy Miracle)'
++++ fedora_regex='Fedora release 17*'
++++ [[ Fedora release 17 (Beefy Miracle) == Fedora release 17* ]]
++++ echo fc17
++++ return
+++ wget -q -P /scratch/jenkins/addons/ruby https://repository-cloudbees.forge.cloudbees.com/distributions/ci-addons/ruby/fc17/ruby-2.0.0-p247-x86_64.tar.bz2
+++ '[' '!' -f /scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64/bin/ruby ']'
+++ tar xjf /scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64.tar.bz2 -C /scratch/jenkins/addons/ruby
+++ export RUBY_HOME=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64
+++ RUBY_HOME=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64
+++ export PATH=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64/bin:/opt/jdk/latest/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/opt/maven/latest/bin:/opt/ant/latest/bin:/opt/android/android-sdk-linux/tools:/opt/gradle/latest/bin:/home/jenkins/bin:/opt/jdk/jdk.latest/bin
+++ PATH=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64/bin:/opt/jdk/latest/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/opt/maven/latest/bin:/opt/ant/latest/bin:/opt/android/android-sdk-linux/tools:/opt/gradle/latest/bin:/home/jenkins/bin:/opt/jdk/jdk.latest/bin
+++ unset GEM_PATH
+++ unset GEM_HOME
+++ unset BUNDLE_PATH
++ gem install bundler --no-ri --no-rdoc
+Successfully installed bundler-1.3.5
+1 gem installed
++ '[' -d modules/ve-mw/test/browser/ ']'
++ cd modules/ve-mw/test/browser/
++ bundle install
+Fetching gem metadata from https://rubygems.org/..........
+Fetching gem metadata from https://rubygems.org/..
+Installing builder (3.2.2) 
+Installing ffi (1.9.3) 
+Installing childprocess (0.3.9) 
+Installing diff-lcs (1.2.4) 
+Installing multi_json (1.8.2) 
+Installing gherkin (2.12.2) 
+Installing multi_test (0.0.2) 
+Installing cucumber (1.3.8) 
+Installing i18n (0.6.5) 
+Installing faker (1.2.0) 
+Installing yml_reader (0.2) 
+Installing data_magic (0.16.1) 
+Installing json (1.8.1) 
+Installing net-http-persistent (2.9) 
+Installing page_navigation (0.9) 
+Installing rubyzip (1.0.0) 
+Installing websocket (1.0.7) 
+Installing selenium-webdriver (2.37.0) 
+Installing watir-webdriver (0.6.4) 
+Installing page-object (0.9.3) 
+Installing mime-types (2.0) 
+Installing rest-client (1.6.7) 
+Installing rspec-expectations (2.14.3) 
+Installing syntax (1.0.0) 
+Installing mediawiki-selenium (0.1.12) 
+Using bundler (1.3.5) 
+Your bundle is complete!
+Use `bundle show [gemname]` to see where a bundled gem is installed.
++ bundle exec cucumber --verbose --profile ci --tags @en.wikipedia.beta.wmflabs.org
+Code:
+  * features/support/env.rb
+  * features/support/hooks.rb
+  * features/support/modules/url_module.rb
+  * features/support/pages/cursor_test_page.rb
+  * features/support/pages/login_page.rb
+  * features/support/pages/visual_editor_page.rb
+  * features/step_definitions/bullets_steps.rb
+  * features/step_definitions/common_steps.rb
+  * features/step_definitions/cursor_steps.rb
+  * features/step_definitions/general_markup_steps.rb
+  * features/step_definitions/headings_steps.rb
+  * features/step_definitions/links_steps.rb
+  * features/step_definitions/references_steps.rb
+  * features/step_definitions/shared_steps.rb
+  * features/step_definitions/transclusion_steps.rb
+
+Features:
+  * features/bullets.feature
+  * features/edit_utf8_logged_in.feature
+  * features/general_markup.feature
+  * features/headings.feature
+  * features/indent_outdent.feature
+  * features/links.feature
+  * features/references.feature
+  * features/transclusion.feature
+Parsing feature files took 0m0.111s
+
+Build step 'Execute shell' marked build as failure
+Recording test results",1385489908,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"Created attachment 13911
+typical Jenkins report
+
+**Attached**: {F11943}",1385489783,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,This is how a typical Jenkins report looks like (see attached file).,1385489700,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,"**jhall** wrote:
+
+I used this plugin in a previous job and found it to be very flexible (among other things, it provides for customized e-mail subject strings):
+
+https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin",1385484207,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+Customize Jenkins email notifications,We should find a Jenkins plugin that should allow us to customize e-mail notification messages. The default messages are not really useful.,1382419361,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ytppcpdbs2adftajp5tt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"Seen in Chrome and not Firefox: 
+
+Sometimes initiating a VE session can take on the order of 3X the normal time (or possibly more).  This is a UX issue and also causes significant intermittent browser test failures in Chrome version 30.  Here are 10 runs of a script[*] that times how long it takes to bring up and dismiss the ""Welcome..."" iframe:
+
+2.194106
+2.187554
+2.222601
+2.226447
+2.369503
+2.182237
+7.639938 *
+2.335375
+2.397571
+2.271333
+
+This is on a fast connection.  The performance issue is exacerbated on a slow connection.
+
+Speculation as to the root cause: 
+
+* The ""Welcome..."" iframe is actually the second iframe in the page.  The first, much larger iframe in the page is invisible and is a complete copy of the base VisualEditor UI.  It could be that loading both iframes could cause intermittent performance problems. 
+
+* (Note that the invisible first iframe on the page not only contains an entire VE UI, but may also contain gadget code like HotCat or ProveIt sourced from other places like bits, see screen shot and Bug 55759.)
+
+[*] The meat of the little Ruby timer script is: 
+
+#CLICK EDIT
+b.a(:title => /Edit this page with VisualEditor/).when_present.click
+#SAVE START TIME
+welcome_start_time = Time.now
+#CLICK CLOSE ON THE WELCOME IFRAME WHEN IT BECOMES CLICKABLE
+b.frame(:index => 1).a(:title => 'Close').when_present.click
+#SAVE END TIME
+welcome_end_time = Time.now
+welcome_load_time = welcome_end_time - welcome_start_time
+puts welcome_load_time.to_s
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381945440,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5zskngbxk4z3y36fzvyt,task_description,invalid
+significant intermittent performance problem in Chrome,"probably not, closing.",1383846541,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"I don't know what significant intermittent performance problem you are observing in Chrome, but I am fairly confident that this is not related to ProveIt, or any other gadget.",1383842467,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"Gadgets are not and never were loaded in our iframes.
+
+The only thing related to gadgets being applied in iframes is their stylesheets. And this is not an explicit action, but a result of the stylesheet link established between the parent and child frame to ensure content looks the same.
+
+Afaik this should not have any significant impact in performance as 1) these styles are loaded in the same request as other styles, 2) the exact same request has been fired and cached already in the parent frame, and as such is pretty much guaranteed to be 304 cached if not already.
+
+Also, in non-debug mode, most stylesheets actually become <style> tags which are cloned to the iframe without any intermittent load.php request (be it a 304 or not).",1383842402,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"I also don't see a reason to load gadgets in the VE frames.  Since it's same-origin, gadgets can reach into the iframe if needed.  E.g.
+
+$( $( '.ve-ui-frame' )[0].contentDocument ).find( '.ve-ui-labeledElement-label' )",1382744657,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+significant intermittent performance problem in Chrome,"Created attachment 13511
+contents of the invisible iframe
+
+**Attached**: {F12750}",1381945594,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5zskngbxk4z3y36fzvyt,task_subcomment,NA
+Bogus phpcs failure in VisualEditor,"https://integration.wikimedia.org/ci/job/mwext-VisualEditor-phpcs-HEAD/1561/console is a bogus failure. The error messages are:
+
+14:41:05 FILE: ...orkspace/mwext-VisualEditor-phpcs-HEAD/maintenance/makeStaticLoader.php
+14:41:05 --------------------------------------------------------------------------------
+14:41:05 FOUND 2 ERROR(S) AFFECTING 2 LINE(S)
+14:41:05 --------------------------------------------------------------------------------
+14:41:05  78 | ERROR | Expected 1 space before ""?""; 3 found
+14:41:05     |       | (Squiz.WhiteSpace.OperatorSpacing.SpacingBefore)
+14:41:05  80 | ERROR | Expected 1 space before "":""; 3 found
+14:41:05     |       | (Squiz.WhiteSpace.OperatorSpacing.SpacingBefore)
+14:41:05 --------------------------------------------------------------------------------
+
+The source code doesn't have 3 spaces before the ?, only a bunch of tabs), but it does have a comment on the preceding line each time. Maybe that's what's confusing phpcs?
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1381502640,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-x2bemat6dbvj4qacn3ja,task_description,declined
+Bogus phpcs failure in VisualEditor,"Looking at the code, the phpcs failure seemed correct, the ternary operators should be at end of line.",1383048850,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-x2bemat6dbvj4qacn3ja,task_subcomment,NA
+Bogus phpcs failure in VisualEditor,Filing this because it will eventually block https://gerrit.wikimedia.org/r/#/c/88896/ once that commit has been cleaned up and reviewed.,1381502717,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-x2bemat6dbvj4qacn3ja,task_subcomment,NA
+Edit conflict: Review your changes performs different as Save page,"**Author:** `felix`
+
+**Description:**
+* Edit one section with VE
+*:Example diff:
+*:+ VEtext
+
+* Provoke edit conflict in another section
+*:Example diff:
+*:+ ConflictText
+
+* Click ""Review your changes"" in VE
+
+* Diff shows
+** the changes made in VE
+** the changes of the edit conflict as reverted (!)
+*:Example diff:
+*:+ VEtext
+*:- ConflictText
+
+* Click ""Save page""
+** Both edits are successfully merged
+*:Example diff:
+*:+ VEtext
+*:+ ConflictText
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55392",1381488000,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bytfsofa3wltd64urfvv,task_description,declined
+Edit conflict: Review your changes performs different as Save page,This is the same behaviour as the wikitext editor - what would you instead suggest VisualEditor (and the wikitext editor) do?,1384846589,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bytfsofa3wltd64urfvv,task_subcomment,NA
+VisualEditor: VE edit button shown on talk pages with titles starting with a full stop (period),"On talk pages that have titles starting with a full stop (period) such as [[talk:.mp]] and [[it:Discussione:.uk]] the button to launch VE is shown despite not being enabled in that namespace. Clicking on it gives the following error message:
+
+Error loading data from server: novenamespace: VisualEditor is not enabled in namespace 1. Would you like to retry?
+
+(incidentally this message is not translated for it.wp)
+
+Possibly this bug has the same cause as bug 55493
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55493",1381282140,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hibjkpd4gxjy4lfkuxhu,task_description,resolved
+VisualEditor: VE edit button shown on talk pages with titles starting with a full stop (period),"We fixed this just this week (this is also bug 38081 - if the page starts with a '.', mw:Title fails and so the code to suppress VE doesn't work), and will be deploying it to MediaWiki.org on Thursday (10 October); assuming that all goes well, it will hit the English Wikipedia next Thursday (17 October).
+
+*** This bug has been marked as a duplicate of bug 38081 ***",1381286891,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hibjkpd4gxjy4lfkuxhu,task_subcomment,NA
+VisualEditor: Does not load on pages with titles starting with a full stop (period),"At least in Firefox 24 on Linux (not tested in other systems) VisualEditor does not load on main namespace pages whose titles begin with a full stop (period). The URL changes and the page reloads but remains in view mode.
+
+Tested at [[.mp]], [[.uk]], [[.300]] and [[.300 Remington American Magnum]] at en.wp and at the .uk articles at it.wp, de.wp, fr.wp and es.wp
+
+The bug does not manifest in other namespaces, e.g. [[User:Thryduulf/.100]] and [[User:.anaconda]] load correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55494",1381281660,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k23jbc4tij5lhe6eeo73,task_description,resolved
+VisualEditor: Does not load on pages with titles starting with a full stop (period),"We fixed this just this week (this is bug 38081), and will be deploying it to MediaWiki.org on Thursday (10 October); assuming that all goes well, it will hit the English Wikipedia next Thursday (17 October).
+
+*** This bug has been marked as a duplicate of bug 38081 ***",1381286833,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k23jbc4tij5lhe6eeo73,task_subcomment,NA
+"VisualEditor: dropdown menus only completely visible at top of page, and disappear lower down page in Vector skin","TeamGale reports:
+
+""while I was getting more down to the page, the drop down menus were getting ""shorter"" and sometimes disappear at the very end. I tried it to many pages to see if it was happening everywhere and it does. I don't know exactly how to describe it that's why I took screencaps from the page. All three are from the same page, in different height. See how the drop down menu of ""more"" can be seen entirely at the top of the page and how it gradually disappear as I get closer to the bottom. It's really weird!! The same thing happens when I am trying to add a wiki link in the article's text and to be honest, that's how I notice the gradually disappearing.""
+
+The screenshot is at [[File:Drop Down Menus.jpg]]
+
+I can reproduce this in Firefox 24 on Linux when using the vector skin, but not when using Monobook. 
+
+Trying to add a link after the end of the first paragraph I get no suggestions when my window is not maximised. Even when it is maximised it has completely disappeared by the end of the page. 
+
+What seems to matter is where the view is, not where the cursor is.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1381012260,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4tqy4h2htavrdjo2k36n,task_description,resolved
+"VisualEditor: dropdown menus only completely visible at top of page, and disappear lower down page in Vector skin","
+
+*** This bug has been marked as a duplicate of bug 55343 ***",1381080286,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4tqy4h2htavrdjo2k36n,task_subcomment,NA
+"VisualEditor: dropdown menus only completely visible at top of page, and disappear lower down page in Vector skin",See also bug 55343,1381056057,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-4tqy4h2htavrdjo2k36n,task_subcomment,NA
+"VisualEditor: dropdown menus only completely visible at top of page, and disappear lower down page in Vector skin","TeamGale didn't give their system details with this report, but from another report of theirs they are most likely using the latest Firefox on Windows 8.",1381012355,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4tqy4h2htavrdjo2k36n,task_subcomment,NA
+[Regression] mediawiki.Title: jQuery.byteLength undefined,"Login at http://en.wikipedia.beta.wmflabs.org/ with VE enabled. 
+
+Click edit on any page to invoke VE.
+
+Page reloads, VE is not invoked. 
+
+Javascript errors: 
+
+Exception thrown by ext.visualEditor.viewPageTarget.init: Object function (selector,context){return new jQuery.fn.init(selector,context,rootjQuery);} has no method 'byteLength' load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151
+TypeError
+ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151
+Exception thrown by ext.gettingstarted.openTask: Object function (selector,context){return new jQuery.fn.init(selector,context,rootjQuery);} has no method 'byteLength' load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151
+TypeError
+ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: critical",1380899400,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-w7zawrtzky3vftelryka,task_description,resolved
+[Regression] mediawiki.Title: jQuery.byteLength undefined,"Change 87593 merged by jenkins-bot:
+mw.Title: Add missing dependency on jquery.byteLength
+
+https://gerrit.wikimedia.org/r/87593",1380906444,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w7zawrtzky3vftelryka,task_subcomment,NA
+[Regression] mediawiki.Title: jQuery.byteLength undefined,"Change 87593 had a related patch set uploaded by Krinkle:
+mw.Title: Add missing dependency on jquery.byteLength
+
+https://gerrit.wikimedia.org/r/87593",1380905932,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w7zawrtzky3vftelryka,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"User report:
+<<[...] The new one (for me at least, perhaps it already existed): when I edit a page in Beta (my sandbox, or a main space page), I get next to the page title two pale blue links, ""edit source / edit beta"", which bring me to the section editing for the lead. I don't get these pale links for other sections, only next to the title. I can't remember these being there, and I can't see the use for them (and if they have a use, they would probably be wanted for other sections as well). Fram (talk) 12:01, 4 October 2013 (UTC) >>
+
+He uses FF 24, I can't reproduce but we have a screenshot at 
+https://en.wikipedia.org/wiki/File:VE_error_Fram_1.jpg .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1380894960,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-u6bt2ddckctrby5sscwl,task_description,invalid
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"(In reply to comment #5)
+> I submitted a step towards potentially fixing this and other editsection and
+> VE-related bugs at https://gerrit.wikimedia.org/r/#/c/87627/ (after recent
+> discussion at [[WP:VPT]]).
+
+Thanks!",1381266111,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,I submitted a step towards potentially fixing this and other editsection and VE-related bugs at https://gerrit.wikimedia.org/r/#/c/87627/ (after recent discussion at [[WP:VPT]]).,1381266063,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"This is caused by the ""Add an [edit] link for the lead section of a page"" gadget on enwiki.
+
+As normal, because gadgets' bugs aren't tracked on Bugzilla, I'm marking this as INVALID, but please do contact the author of the gadget and ask them to fix it. :-(",1381264538,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"Fram, the original reporter, has confirmed that he uses Vector so it does seem to be skin-specific.",1381138526,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"I can confirm that I see this in Firefox 24/Linux/Monobook. I don't see it when using Vector skin. I don't have access to other browsers/systems to test on.
+
+Test page: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575760261",1380909771,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+VisualEditor: [edit source | edit beta] links near page title when already in VE mode,"<<Note that I only get this when the page has at least one section header. Pages without section headers don't have this behaviour. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 14:12, 4 October 2013 (UTC)>>",1380896005,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-u6bt2ddckctrby5sscwl,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"```
++----------------------+------+------+-------------+-----------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| dbname               | lang | name | family      | url                               | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |
++----------------------+------+------+-------------+-----------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| bat_smgwiki          | en   | NULL | wikipedia   | http://bat_smg.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| be_x_oldwiki         | en   | NULL | wikipedia   | http://be_x_old.wikipedia.org     |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| cbk_zamwiki          | en   | NULL | wikipedia   | http://cbk_zam.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| centralauth          | en   | NULL | centralauth | NULL                              |    1 | s7.labsdb |         0 |        0 |               0 |                0 |            0 |
+| fiu_vrowiki          | en   | NULL | wikipedia   | http://fiu_vro.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| map_bmswiki          | en   | NULL | wikipedia   | http://map_bms.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| nds_nlwiki           | en   | NULL | wikipedia   | http://nds_nl.wikipedia.org       |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| roa_rupwiki          | en   | NULL | wikipedia   | http://roa_rup.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| roa_rupwiktionary    | en   | NULL | wiktionary  | http://roa_rup.wiktionary.org     |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| roa_tarawiki         | en   | NULL | wikipedia   | http://roa_tara.wikipedia.org     |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| vewikimedia          | en   | NULL | wikimedia   | http://ve.wikimedia.org           |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_classicalwiki     | en   | NULL | wikipedia   | http://zh_classical.wikipedia.org |    1 | s3.labsdb |         0 |        0 |               1 |                1 |            1 |
+| zh_min_nanwiki       | en   | NULL | wikipedia   | http://zh_min_nan.wikipedia.org   |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
+| zh_min_nanwikibooks  | en   | NULL | wikibooks   | http://zh_min_nan.wikibooks.org   |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_min_nanwikiquote  | en   | NULL | wikiquote   | http://zh_min_nan.wikiquote.org   |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_min_nanwikisource | en   | NULL | wikisource  | http://zh_min_nan.wikisource.org  |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_min_nanwiktionary | en   | NULL | wiktionary  | http://zh_min_nan.wiktionary.org  |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |
+| zh_yuewiki           | en   | NULL | wikipedia   | http://zh_yue.wikipedia.org       |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |
++----------------------+------+------+-------------+-----------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+```
+
+For the wikis reported above lang is 'en', name in NULL and URL is wrong (maybe this is the reason for the other missing information). For example isn't http://roa_tara.wikipedia.org but http://roa-tara.wikipedia.org
+
+For all the wikis, 'size' column is always 1. This information can be get from:
+* site_stats.ss_good_articles table of replica db, or
+* API /w/api.php?action=query&meta=siteinfo&format=json&siprop=statistics under ""articles""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48626",1380879960,PHID-USER-6ji4nw2pi3dgjy7tgmhp,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_description,resolved
+Missing or wrong information in meta_p.wiki table,">>! In T56962#1051546, @jayvdb wrote:
+> Is T69476 part of the scope of this task?
+
+No, that should be handled there.
+
+Regarding the `size` column, looking at `maintain-replicas.pl` showed that it should not be `1` for all wikis, so I filed T90084 for that.
+
+I close this task as its original bug has been fixed.",1424404841,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,Is T69476 part of the scope of this task?,1424384247,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"At the moment, there are two wikis apart from `centralauth` that have `name` set to `NULL`:
+
+```
+MariaDB [enwiki_p]> SELECT * FROM meta_p.wiki WHERE name IS NULL;
++-------------+------+------+-------------+------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| dbname      | lang | name | family      | url                          | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |
++-------------+------+------+-------------+------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| qualitywiki | en   | NULL | special     | http://quality.wikimedia.org |    1 | s3.labsdb |         1 |        1 |               0 |                0 |            0 |
+| centralauth | en   | NULL | centralauth | NULL                         |    1 | s7.labsdb |         0 |        0 |               0 |                0 |            0 |
+| ukwikimedia | en   | NULL | wikimedia   | http://uk.wikimedia.org      |    1 | s3.labsdb |         1 |        1 |               0 |                0 |            0 |
++-------------+------+------+-------------+------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+3 rows in set (0.00 sec)
+
+MariaDB [enwiki_p]>
+```
+
+As these are closed wikis I assume that is correct?
+
+Also, there are no wikis with `size` not being `1`:
+
+```
+MariaDB [enwiki_p]> SELECT size, COUNT(*) FROM meta_p.wiki GROUP BY size;
++------+----------+
+| size | COUNT(*) |
++------+----------+
+|    1 |      858 |
++------+----------+
+1 row in set (0.00 sec)
+
+MariaDB [enwiki_p]>
+```
+
+Is this column important to you, @Pietrodn?  Otherwise I'd propose to resolve this task as the main issues seem to have been fixed.",1424287734,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"Change 160945 merged by coren:
+Labs: Fix generation of meta_p.meta
+
+https://gerrit.wikimedia.org/r/160945",1410954296,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"Change 160945 had a related patch set uploaded by coren:
+Labs: Fix generation of meta_p.meta
+
+https://gerrit.wikimedia.org/r/160945",1410954204,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,Now the problem seems to be fixed.,1410954159,PHID-USER-bxdsl6dwnf4xk47wrlkc,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"The meta_p.wiki tables now contains only one row: centralauth.
+
+MariaDB [meta_p]> select * from wiki;
++-------------+------+------+-------------+------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| dbname      | lang | name | family      | url  | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |
++-------------+------+------+-------------+------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+| centralauth | en   | NULL | centralauth | NULL |    1 | s7.labsdb |         0 |        0 |               0 |                0 |            0 |
++-------------+------+------+-------------+------+------+-----------+-----------+----------+-----------------+------------------+--------------+
+1 row in set (0.00 sec)",1410936827,PHID-USER-bxdsl6dwnf4xk47wrlkc,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,There was a typo that prevented the size column from being properly set.  Fixed since.,1399342402,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"(In reply to comment #3)
+> (In reply to comment #2)
+> > Also 'is_closed' column is always 0, for all the wikis.
+> 
+> That would be because we do not currently replicate any closed wikis.  :-)
+Ah, ok! Alright :)
+
+> For the other values, things should have been corrected now.  Please check?
+Now it seems ok, except for the 'size' column, is always 1 yet.",1381333801,PHID-USER-6ji4nw2pi3dgjy7tgmhp,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"(In reply to comment #2)
+> Also 'is_closed' column is always 0, for all the wikis.
+
+That would be because we do not currently replicate any closed wikis.  :-)
+
+For the other values, things should have been corrected now.  Please check?",1381326903,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"Also 'is_closed' column is always 0, for all the wikis.",1381326150,PHID-USER-6ji4nw2pi3dgjy7tgmhp,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+Missing or wrong information in meta_p.wiki table,"Yes, the URL being incorrect is likely the cause of the other errors.  Looking into it.",1380892195,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-eq6kmmhfj5sxk522ij2u,task_subcomment,NA
+"VisualEditor: Marathi/Devanagari: When using jquery.IME, type a word and press space bar = eliminates typed text immediately Typed content disappear while pressing Spacebar","I am using Malayalam Inscript2 IME of ULS for typing in Malayalam Wikipedia. Problem is described here:
+
+1. Open an article from ml.wikipedia (for eg. https://ml.wikipedia.org/wiki/%E0%B4%B8%E0%B5%82%E0%B4%AB%E0%B4%BF )
+2. Edit a section using VE
+3. Add a new line at the end of the section and type a word using ULS IME
+4. Press Spacebar, the typed word disappears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows 7
+**Platform**: PC
+**URL**: http://ml.wikipedia.org",1380877560,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-xkeqdnpvwm2mnuk2p4kq,task_description,duplicate
+"VisualEditor: Marathi/Devanagari: When using jquery.IME, type a word and press space bar = eliminates typed text immediately Typed content disappear while pressing Spacebar","Pretty sure that this is the same issue as bug 53700 - merging.
+
+*** This bug has been marked as a duplicate of bug 53700 ***",1381270703,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xkeqdnpvwm2mnuk2p4kq,task_subcomment,NA
+Editing refs in image descriptions,"As demonstrable in the last image inserted in:
+
+https://de.wikipedia.org/wiki/Tetrahedran
+
+refs inserted in the description of media, here 1), can't be edited. Report:
+
+https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=123123395#Einzelnachweise_in_Bildunterschriften
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380842100,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-bnfed45fsdr7ijiu7iy4,task_description,resolved
+Editing refs in image descriptions,"Happily this is already fixed in the code that just went to MediaWiki.org today, and will be available on dewiki (and elsewhere) in a week's time. Merging with bug 50459.
+
+*** This bug has been marked as a duplicate of bug 50459 ***",1380844957,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bnfed45fsdr7ijiu7iy4,task_subcomment,NA
+Newly inserted templates / transclusions are not floated,"example of the non-float
+
+Reproduced on Windows 7 and Mac OSX 10.8.5 — when a new template is added to an article it does not follow float:right. However, on page save and a re-entry of the VE it is properly floated.
+
+See the attached screenshot. This really breaks the WYSIWYG nature of the VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12578}",1380745680,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-jyvhhwmshuq26opbmerd,task_description,resolved
+Newly inserted templates / transclusions are not floated,"I'm merging this with bug 49784 - agreed that it's a real product fail.
+
+*** This bug has been marked as a duplicate of bug 49784 ***",1380746310,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jyvhhwmshuq26opbmerd,task_subcomment,NA
+"VisualEditor: Create a ""hamburger""-icon (☰) drop down menu for toolbar items which aren't editing tools","Such as:
+* Page settings
+* Help/about/version
+* Switch to source editing
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380708480,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-huguj37vwbp5tlmsngzb,task_description,invalid
+"VisualEditor: Create a ""hamburger""-icon (☰) drop down menu for toolbar items which aren't editing tools","(In reply to comment #0)
+> Such as:
+> * Page settings
+> * Help/about/version
+> * Switch to source editing
+
+Err… this was already done by Trevor many months ago. See https://commons.wikimedia.org/wiki/File:VisualEditor_-_Icon_-_Menu.svg for the version on Commons, let alone the version in the repo…
+
+(In reply to comment #1)
+> https://en.wikipedia.org/wiki/%E2%98%B0
+> 
+> Is using Qián (☰) going to cause problems with Chinese language UI's, or will
+> it require browsers to download additional fonts in order to render it?
+
+No, we're not using a character, we'll use an SVG icon like the rest of the interface.",1380731297,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-huguj37vwbp5tlmsngzb,task_subcomment,NA
+"VisualEditor: Create a ""hamburger""-icon (☰) drop down menu for toolbar items which aren't editing tools","https://en.wikipedia.org/wiki/%E2%98%B0
+
+Is using Qián (☰) going to cause problems with Chinese language UI's, or will it require browsers to download additional fonts in order to render it?",1380731074,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-huguj37vwbp5tlmsngzb,task_subcomment,NA
+Edit tab titles are not consistent,"Edit tab titles are not consistent (on hu.wikipedia):
+
+- If I am logged out, I see tab title ""visualeditor-ca-editsource"", and it opens the source edit page.
+- If I am logged in, and I have opt-outed from VisualEditor, then I see ""vector-view-edit"", and it opens the source edit page.
+- If I am logged in, and I have VisualEditor enabled (default), then I see ""vector-view-edit"", which opens the visual edit page, and also ""visualeditor-ca-editsource"", which opens the source edit page.
+
+Some user on hu.wikipedia complained, that the same ""vector-view-edit"" meant source edit 2 days ago, and it now means visual edit, which is confusing. So we would like to rename both tabs, to be clear for everyone: we want to create a ""Visual edit"" and a ""Source edit"" tab, with the same text for everyone. But this structure makes impossible to set translation according to this, because opt-outed users se the same text for source edit as non-opt-outed users for visual edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380704760,PHID-USER-hfilh4urx5vchfwani3k,False,PHID-TASK-4iunqtmz3u4jccn23ct7,task_description,resolved
+Edit tab titles are not consistent,"This is intentional - for a week, we deploy VisualEditor for logged-in users before we deploy it for logged-out users. This will be fixed for huwiki on Monday when VisualEditor is enabled by default for logged-out users too. Sorry for the disruption.
+
+*** This bug has been marked as a duplicate of bug 49999 ***",1380835091,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4iunqtmz3u4jccn23ct7,task_subcomment,NA
+Delete VisualEditor/core repo,"http://git.wikimedia.org/summary/?r=VisualEditor/core.git
+
+Seems unneeded.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: minor",1380590700,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-ar7o222adkj6yo6s5o5w,task_description,declined
+Delete VisualEditor/core repo,"We're about to fill it with content. So… no, please don't.",1380591667,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ar7o222adkj6yo6s5o5w,task_subcomment,NA
+When editing using VisualEditor I see the '♙' character at every newline,"Hi
+Just like the title, if I edit the body of the text, at every newline it enters an ♙ character, and I have to manually delete every time (by writig, going back and deleting).
+
+Also there are many other special characters displayed, like arrows for tab and return. Don't know if it's the same issue.
+
+The wiki is hosted on a CentOS 6.4 box, running latest versions of apache and PHP, under a virtualhost. The client is an OSX 10.9 computer.
+
+Please tell me if you need any additional information.
+
+Thank you.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: Macintosh",1380546240,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-qdobmgita3aclomioanb,task_description,resolved
+When editing using VisualEditor I see the '♙' character at every newline,"Hi there,
+
+This is a break we introduced on Friday, sorry - a fix is now in gerrit 86685 and will be merged in the next few minutes. Up-merging this with bug 54791 reported by our QA team. Thanks for the bug report!
+
+(In reply to comment #0)
+> Also there are many other special characters displayed, like arrows for tab
+> and return. Don't know if it's the same issue.
+
+That's not - this is intentional as a means to differentiate different kinds of whitespace (which show up differently to the user in wikitext, but would otherwise look the same in HTML).
+
+*** This bug has been marked as a duplicate of bug 54791 ***",1380559441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qdobmgita3aclomioanb,task_subcomment,NA
+Images are slow to update in the search index,"Inserting media with VE
+
+Sometimes I cant add image, because it doesnt display. This time at https://cs.wikipedia.org/wiki/Seznam_památných_stromů_v_okrese_Rokycany
+
+adding File:Kařízský dub, pohled.jpg with FF 23.0.1
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**Whiteboard**: cirrus-fixed
+
+**Attached**: {F12341}",1380515400,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_description,resolved
+Images are slow to update in the search index,"
+
+*** This bug has been marked as a duplicate of bug 52782 ***",1382572188,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_subcomment,NA
+Images are slow to update in the search index,"(In reply to comment #2)
+> Doesnt work still to me. Thats why I am opening it again. Once you will
+> update search, lets talk about clossing.
+
+This has nothing to do with VisualEditor; re-assigning.",1382370812,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_subcomment,NA
+Images are slow to update in the search index,"Doesnt work still to me. Thats why I am opening it again. Once you will update search, lets talk about clossing.",1382173897,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_subcomment,NA
+Images are slow to update in the search index,This is because the old search system is slow to update (it now works for me). Happily the new search system (which is coming hopefully soon). Sorry. :-(,1380834938,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z5y5vu36oczd2xqoi5r7,task_subcomment,NA
+Dragging elements to the end of the page should make a new empty line appear,"When you want to drag an element to the very bottom of the content editable area, the last position available for the cursor is the end of the last sentence. 
+
+Usually you want to place elements not at the end of a line, but right after, in a new line. The behavior expected would be to see a new empty line appearing when you drag an element until the end of a page, and the possibility to drop your element in that empty line.
+
+Tested with the {{Languages}} template at https://www.mediawiki.org/wiki/Groups 
+
+The last cursor position possible is at the end of the sentence: ""... to create your MediaWiki group."" Dropping the template after the last dot puts it at the end of the page, in a new line. The end result is correct, but the behavior is unituitive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51666",1380427800,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-hy35new7rxofajvvqivl,task_description,resolved
+Dragging elements to the end of the page should make a new empty line appear,"(In reply to comment #0)
+> When you want to drag an element to the very bottom of the content editable
+> area, the last position available for the cursor is the end of the last
+> sentence. 
+> 
+> Usually you want to place elements not at the end of a line, but right after,
+> in a new line. The behavior expected would be to see a new empty line
+> appearing when you drag an element until the end of a page, and the
+> possibility to drop your element in that empty line.
+
+Merging this with bug 51666 which I've re-titled.
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > Note also that for me, on
+> > [https://www.mediawiki.org/wiki/Communication?veaction=edit], the ""other
+> > languages"" template at the top is not even visible in VE mode... This is
+> > probably a separate bug though.
+> 
+> Possibly it is or is related to bug 50284
+
+No, this is because of the code inside the ""other languages"" template making assumptions which are true for read mode but not for VisualEditor - I think this is an artefact of bug 50172 and a few other issues.
+
+*** This bug has been marked as a duplicate of bug 51666 ***",1381246558,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hy35new7rxofajvvqivl,task_subcomment,NA
+Dragging elements to the end of the page should make a new empty line appear,"(In reply to comment #1)
+> Note also that for me, on
+> [https://www.mediawiki.org/wiki/Communication?veaction=edit], the ""other
+> languages"" template at the top is not even visible in VE mode... This is
+> probably a separate bug though.
+
+Possibly it is or is related to bug 50284",1381227927,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hy35new7rxofajvvqivl,task_subcomment,NA
+Dragging elements to the end of the page should make a new empty line appear,"**Wikifram** wrote:
+
+Only now noticed this. For me, dropping the template after the last dot was not even possible. I could drop it before the last dot, but not after, so for me it was not simply unintuitive, it was wrong. But now, this has been solved apparently, whether by a new VE version or by a Firefox update I don't know. 
+
+Note also that for me, on [https://www.mediawiki.org/wiki/Communication?veaction=edit], the ""other languages"" template at the top is not even visible in VE mode... This is probably a separate bug though.",1381225378,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hy35new7rxofajvvqivl,task_subcomment,NA
+VisualEditor opt-in preference disappears,"As user Selenium_user on beta labs enwiki, I have set my preference to opt-in to VisualEditor several times, but the preference then gets reset to default (opt-in not set) after a period of some hours.  
+
+This causes failures in the browser tests and I wonder if it is a risk in the production environment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1380234840,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_description,resolved
+VisualEditor opt-in preference disappears,"
+The fix is to not do a global reset of preferences for the shared test user. :-) 
+
+We will have the ULS tests create a user of their own.",1380642094,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"Great!    Now got to find a fix, ideally the VE feature should set the optin preference.  I am not sure whether you have support for that already.
+
+And sorry for the delay investigating this issue :/",1380588185,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"
+ULS tests are doing it: 
+
+
+tests/browser/features/support/pages/reset_preferences.rb 
+Last indexed a month ago
+1
+2
+3
+4
+class ResetPreferencesPage
+	include PageObject
+	include URL
+	page_url URL.url('Special:Preferences/reset')
+Ruby
+tests/browser/features/step_definitions/common_steps.rb 
+Last indexed 4 days ago
+59
+60
+61
+After('@reset-preferences-after') do |scenario|
+	visit(ResetPreferencesPage)
+	on(ResetPreferencesPage).submit_element.click",1380586091,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"
+this really should not be happening for any test: 
+
+0.2789   6.0M  Start request POST /wiki/Special:Preferences/reset
+
+thanks for pointing that out.",1380585639,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"What led me to suspect it is:
+
+0.2789   6.0M  Start request POST /wiki/Special:Preferences/reset
+HOST: commons.wikimedia.beta.wmflabs.org
+HTTP HEADERS:
+X-REAL-IP: ....  # Some IP address at saucelabs
+X-FORWARDED-PROTO: https
+...
+REFERER: https://commons.wikimedia.beta.wmflabs.org/wiki/Special:Preferences/reset
+COOKIE: ...centralauth_User=Selenium+user .... commonswikiUserName=Selenium+user...
+
+
+See also ""Update how VisualEditor's experimental config works""  https://gerrit.wikimedia.org/r/#/c/84433/  which got deployed on beta on Sep 18th.
+
+
+hashar@deployment-bastion:~$ mwscript eval.php --wiki=enwiki
+> return $wgDefaultUserOptions['visualeditor-enable'] ;
+0
+>
+$
+
+
+So you could add an exception in CommonSettings-labs.php or InitialiseSettings-labs.php to override that value for beta and make sure VE is always opted in.",1380585248,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"I am wondering, isn't it that the default is to disable the opt-in preference on enwiki now?   Thus if the Selenium test rest the user preference, it would end up opting out of VE :(
+
+Can you try in your test to explicitly set the user preference?",1380584760,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,VisualEditor opt-in preference unset again overnight PDT Sept 27.,1380557168,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"
+I have just enabled VE manually in beta labs for Selenium_user. I suspect it will become disabled soon. 
+
+Is it possible that the automatic run of update.php (or whatever updates the db) would un-set that preference?",1380292740,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor opt-in preference disappears,"The Selenium_user on enwiki has the following preferences right now:
+
+[""visualeditor-enable""]=> int(0)
+[""visualeditor-enable-experimental""]=>  int(1)
+[""visualeditor-betatempdisable""]=> int(0)
+
+So VE is actually disabled.
+
+Maybe some test is disabling the option while other set it?   Tests relying on VE should probably set the user preference through the API before the test run.",1380262166,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-owimzdmbcsatfp52eoa7,task_subcomment,NA
+VisualEditor: (silently) renumbering references,"Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 :
+<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>
+
+The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:
+<<About half of the 18 references I typed into the article on Homesickness disappeared between yesterday and today. I was certain to follow the Save Changes procedure, but many different references reverted to the same single reference. [...] Same bug today. In VE, I placed the cursor in the text, chose ""Reference"" from the ""More"" menu, added a reference, (It appeared as it should with the appropriate numerical superscript), Saved the work, returned to check the page...references disappeared from the list. - Window 8, Chrome >>.
+
+TeamGale adds:
+<<Hello...I have the same problem [...]. I didn't realized that it happened while I was editing. I only saw it when I saved the article and the number of the references had decreased. This https://en.wikipedia.org/w/index.php?title=Michael_Giannatos&diff=next&oldid=573583391 is the change I was doing when it happened. Could it be related to editing a table with beta? Probably not since I don't see any table on Christopher Thurber's article. After I re-added the references and the new table, every time I click ""edit beta"" the refs are gone! Before I even do any change! Basically I can't use beta at all on this article! I don't have any issues using the source but, if it's something simple that can be done with beta, I prefer to do it with it. But I can't. Just wanted to say that this is happening to other articles as well. And it's possible to happen and people don't see it. That would be a problem to a long article with lots of references... Mozilla 21, Windows 8.>>
+
+TeamGale again:
+<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] 
+Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>>
+
+I think I saw this renumbering issue at it.wp as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380214860,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-gjqblxpe4th4o7zcpret,task_description,resolved
+VisualEditor: (silently) renumbering references,"Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry!
+
+*** This bug has been marked as a duplicate of bug 54341 ***",1380220185,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gjqblxpe4th4o7zcpret,task_subcomment,NA
+VisualEditor: Section-editing lands user at wrong URL post-save,"After successfully section-editing <https://en.wikipedia.org/w/index.php?title=Black_Mail_%281973_film%29&section=2&veaction=edit> using VisualEditor, I land at <https://en.wikipedia.org/w/index.php?title=Black_Mail_%281973_film%29&section=2>.
+
+This shouldn't happen. &section=2 doesn't do anything with the implicit &action=view.
+
+Possibly related to bug 53089.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380209340,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-xrx5soggiup6jgpqpzkt,task_description,resolved
+VisualEditor: Section-editing lands user at wrong URL post-save,"
+
+*** This bug has been marked as a duplicate of bug 53089 ***",1392058252,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xrx5soggiup6jgpqpzkt,task_subcomment,NA
+"VisualEditor: Right half of toolbar disappears when image caption on first line contains ""page "" followed by any string","When an image caption on the first line of a page contains the string ""page "" (including the trailing space) followed by any text the right half of the VisualEditor toolbar disappears (everything right of ""more""). This includes the save button so edits cannot be saved (hence the ""major"" severity)
+
+This is likely related to either bug 54379 (same symptoms) or bug 53312 (same trigger).
+
+Comments on the VE/F report at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=574608525#Odd_one suggest this might be restricted to FireFox.
+
+Minimal test: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=574608905
+Real-world example: https://en.wikipedia.org/w/index.php?title=Clarke,_Irwin_%26_Company&oldid=574526057
+
+To reproduce:
+1. Create a page with any image on the first line of page
+2. Give the image a caption containing the string ""page "" (including the trailing space) followed by any text.
+3. Save the page
+4. Load the page in VE and observe the right half of the editing toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53312
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54379",1380206280,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-kvr63y5we4pdqpvagdka,task_description,resolved
+"VisualEditor: Right half of toolbar disappears when image caption on first line contains ""page "" followed by any string","As far as I can tell this was fixed when bug 53312 was fixed (and for the same reason).
+
+*** This bug has been marked as a duplicate of bug 53312 ***",1393531206,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kvr63y5we4pdqpvagdka,task_subcomment,NA
+"VisualEditor: Right half of toolbar disappears when image caption on first line contains ""page "" followed by any string","Can't reproduce on Chrome, looks like Ff issue.",1380222773,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-kvr63y5we4pdqpvagdka,task_subcomment,NA
+"VisualEditor: Right half of toolbar disappears when image caption on first line contains ""page "" followed by any string","There may be regression involved with this: The toolbar presented properly with the ""page "" string included in the first line for several VE edits over August and September, then the problem was observed Sept. 25.  No change in machine, OS, or browser at the time.",1380216001,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-kvr63y5we4pdqpvagdka,task_subcomment,NA
+wikitech.wikimedia.org needs to have VE enabled,"'coz I likes it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380197400,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-pv364hftdbapyxednn7m,task_description,invalid
+wikitech.wikimedia.org needs to have VE enabled,"(In reply to comment #2)
+> So there was ' Enable VisualEditor (only in the main and user namespaces)'
+> and
+> ' Temporarily disable VisualEditor while it is in beta' in preferences, and
+> they were both unchecked.
+Hah, I wasn't aware it was possible to have both preferences visible at once. That's probably a bug. Either way, you need to both have the ""enable"" box checked and have the ""disable"" box unchecked.",1380248015,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pv364hftdbapyxednn7m,task_subcomment,NA
+wikitech.wikimedia.org needs to have VE enabled,"So there was ' Enable VisualEditor (only in the main and user namespaces)' and ' Temporarily disable VisualEditor while it is in beta' in preferences, and they were both unchecked.",1380247009,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-pv364hftdbapyxednn7m,task_subcomment,NA
+wikitech.wikimedia.org needs to have VE enabled,It already does...,1380217469,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-pv364hftdbapyxednn7m,task_subcomment,NA
+"VisualEditor: Linux font stack sometimes lies about font width, leading to odd wrapping of text in format menu","subhead shows ""2"" in the wrong place
+
+seen in Firefox not in Chrome:  
+
+choose some text and pick a headings format.  Subheads with numbers show the number below the selectbox.  see screen shot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12017}",1380146220,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-tchh23qe4nddxeojdetp,task_description,resolved
+"VisualEditor: Linux font stack sometimes lies about font width, leading to odd wrapping of text in format menu",This was the Linux-wrong-width-of-fonts bug that was fixed a few months ago.,1399644958,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tchh23qe4nddxeojdetp,task_subcomment,NA
+"VisualEditor: Linux font stack sometimes lies about font width, leading to odd wrapping of text in format menu","Created attachment 13378
+shows '3' in the wrong place
+
+**Attached**: {F12018}",1380146299,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-tchh23qe4nddxeojdetp,task_subcomment,NA
+update other repos to qa/browsertests practices,"visualeditor browser tests don't use MEDIAWIKI_PASSWORD, they still use secret.yaml.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380120060,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-xaefdkhei34lxghlfb26,task_description,resolved
+update other repos to qa/browsertests practices,"
+
+*** This bug has been marked as a duplicate of bug 53579 ***",1381410415,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-xaefdkhei34lxghlfb26,task_subcomment,NA
+VisualEditor: Aborting the insertion of a formula should not insert any content,"If you click to use LaTeX, the ""math editor"" option, you cannot cancel or escape out of input.  VisualEditor adds the <math></math> tags regardless and this can only be removed by saving and going to source.
+
+Ideally, a cancel [X] or keyboard options should work to remove this.
+
+https://www.mediawiki.org/w/index.php?title=User:Keegan_(WMF)/sandbox&action=history
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380089700,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-bj5auvkiqa4ukpb3i76l,task_description,resolved
+VisualEditor: Aborting the insertion of a formula should not insert any content,This was fixed a long time ago; sorry for the slow triage.,1394480263,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bj5auvkiqa4ukpb3i76l,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Sikuli ( http://www.sikuli.org ) is a tool for testing desktop interactions, such as mouse clicks and keyboard typing.
+
+This tool is needed for testing typing in different languages, because the usual WebDriver tests are not able to generate proper keyboard events that completely emulate typing in advanced input methods for Japanese, Chinese and Indic scripts. We have many bugs in this area in the VisualEditor (e.g. Bug 52716), so we need proper regression testing.
+
+This week I worked with Željko in the WMF office and we built a prototype test that uses Sikuli to test typing in Japanese:
+https://gerrit.wikimedia.org/r/#/c/83966/
+
+This works on Željko's laptop. The next step is to get it working on the virtual clients that run our continuous integration tests.
+
+Thank you!
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1379701560,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_description,declined
+Add Sikuli to the machines that run browser tests,"You can also find other people discussing using Sikuli with xvfb, e.g. https://github.com/jatalahd/SikuliRobotLibrary/wiki/Hints-and-Tips",1425618435,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,">>! In T56393#1087507, @zeljkofilipin wrote:
+> @Mattflaschen the last time I have checked sikuli web page, it explicitly said running headless is not supported. Maybe something changed in the meantime.
+
+I think it depends on how you define ""headless"".  Sometimes it means ""without anything related to Xorg whatsoever"", but oftentimes it just means ""without a normal X server installation and associated drivers"" or ""without a physical monitor/physical video card"".
+
+https://answers.launchpad.net/sikuli/+question/248704#comment-1 is quite clear that he got it working on Amazon Web Services (presumably Elastic Compute Cloud) and Jenkins.  This is pretty similar to our setup, except we use OpenStack instead of AWS (of course there are other differences, but there doesn't seem to be any unsolvable issue).
+
+[xvfb](https://en.wikipedia.org/wiki/Xvfb) ([Jenkins plugin](https://wiki.jenkins-ci.org/display/JENKINS/Xvfb+Plugin)) is an established tool for this, so the Launchpad comment makes sense.",1425618258,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"@Mattflaschen the last time I have checked sikuli web page, it explicitly said running headless is not supported. Maybe something changed in the meantime.",1425459423,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Did anyone investigate using it headless with Xvfb?  People have gotten this working with Linux and Jenkins (see for example https://answers.launchpad.net/sikuli/+question/248704#comment-1 ).  Their setup differs, but it shows a fully automated headless installation can work.",1425442579,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 165204 merged by Dzahn:
+contint: Sikuli is no longer used anywhere
+
+https://gerrit.wikimedia.org/r/165204",1412969442,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 165204 had a related patch set uploaded by Zfilipin:
+contint: Sikuli is no longer used anywhere
+
+https://gerrit.wikimedia.org/r/165204",1412692379,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 83966 abandoned by Zfilipin:
+[WIP] [BrowserTest] Testing typing in VisualEditor
+
+Reason:
+Sikuli is not the way to go. We will investigate another tool.
+
+https://gerrit.wikimedia.org/r/83966",1406638159,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,Resolving. See comment #9 for details. Please reopen if you think Sikuli is the way to go.,1403988818,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"After further investigation with Amir today, looks like Sikuli does not work with headless machines: ""The system running Sikuli scripts or any apps using SikuliX features must have a real screen connected. So called headless systems are not supported (Java restriction).""
+
+1: http://www.sikulix.com/quickstart.html",1396537515,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"No, it is not really active yet.",1390743741,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Amir, this patch was merged, can this be closed?",1390743366,PHID-USER-u7udgblfyop6qd5wxot6,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 102141 merged by ArielGlenn:
+contint: install libsikuli-script-java for browser tests
+
+https://gerrit.wikimedia.org/r/102141",1387290472,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"I have deployed the package libsikuli-script-java on the integration-selenium-driver.pmtpa.wmflabs instance.  The script is available as /usr/bin/sikuli
+
+Could you craft a simple change that would attempt to run a single browser test using sikuli ?",1387290113,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 102141 had a related patch set uploaded by Hashar:
+contint: install libsikuli-script-java for browser tests
+
+https://gerrit.wikimedia.org/r/102141",1387289655,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Good news: sikuli has been packaged for Debian/Ubuntu. There is a package libsikuli-script-java which seems to provide the needed material:
+
+http://packages.ubuntu.com/precise/all/libsikuli-script-java/filelist
+
+I have no clue how to launch the tests though. Maybe we just have to use /usr/bin/sikuli ?",1387289374,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,"Change 83966 had a related patch set uploaded by Zfilipin:
+[WIP] [Browser test] Testing typing in VisualEditor
+
+https://gerrit.wikimedia.org/r/83966",1387288509,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+Add Sikuli to the machines that run browser tests,Moving from CI to QA,1379709008,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dxtpzjislp3ykzi64aen,task_subcomment,NA
+VisualEditor: Behaviour of <pre> tags,"VE allows editing text between <pre>...</pre> tags.
+That is, you seem to be able, for example, to add working wikilinks and references. Once you save though, everything is rendered as wikicode, as in [[France]] and <ref>France</ref>, and of course is not clickable.
+Thryduulf argues that ""VE shouldn't show it as working if it won't work after saving"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379694480,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-6las75m7yq6t6y42jony,task_description,invalid
+VisualEditor: Behaviour of <pre> tags,"Content that is pre-formatted is not wrapped in <pre> tags but with space-indented-preformatting, which does work with wikitext structures.",1415881409,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6las75m7yq6t6y42jony,task_subcomment,NA
+VisualEditor: Some templates with images show full size images on Swedish Wikipedia,"In some templates (e.g. Template:Infobox fornminne) on Swedish Wikipedia, the image in it is shown in full size when you enter VE. 
+
+Article: https://sv.wikipedia.org/wiki/S%C3%B6dermanlands_runinskrifter_305
+Screencast: https://dl.dropboxusercontent.com/u/8363895/out-8.ogv
+
+It does not behave like that for all templates though. In an article with Template:Kommunfakta is seems to work fine. E.g. https://sv.wikipedia.org/wiki/Botkyrka_kommun
+
+Behaviour is observed from two different users and in both Firefox and Chromium.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1379671920,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-um6o7aq2fxsloslxu5y5,task_description,resolved
+VisualEditor: Some templates with images show full size images on Swedish Wikipedia,"Given the above comment and lack of further reports, I'm marking this as a duplicate of bug 51628
+
+*** This bug has been marked as a duplicate of bug 51628 ***",1380930193,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-um6o7aq2fxsloslxu5y5,task_subcomment,NA
+VisualEditor: Some templates with images show full size images on Swedish Wikipedia,"Yes probably, I did did this change: 
+
+https://sv.wikipedia.org/w/index.php?title=Mall:Infobox_fornminne&diff=prev&oldid=23823659
+
+and now it seems to behave correctly in articles using that template. If I find the same error on other articles, I'll try to se if this is it first.",1380026528,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-um6o7aq2fxsloslxu5y5,task_subcomment,NA
+VisualEditor: Some templates with images show full size images on Swedish Wikipedia,"Could this be bug 51628? i.e. an image size being specified as e.g. ""250px"" in a field that is expecting e.g. ""250""
+
+It seems very likely but I can't read the Swedish source code to check.",1380024894,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-um6o7aq2fxsloslxu5y5,task_subcomment,NA
+VisualEditor: Consistency when restoring a page,"<<[...] When you edit an old version of a page, you get the ""save page"" at the top of the page, but a ""restore page"" button instead of the ""save page"" button at the edit summary page, even if you have made changes in the older version (and thus aren't simply restoring it). Why we have two different buttons (save and restore), when we have only one name otherwise, isn't clear. Beneath the ""restore page "" button, the small text says ""By clicking the ""save page"" button, you agree..."". It doesn't indicate what I agree to by clicking the ""restore page"" button though... Fram (talk) 14:08, 19 September 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379602800,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-yofovlast3zou4zon7j5,task_description,declined
+VisualEditor: Consistency when restoring a page,Reminding the user that they are editing from an old version and restoring it (with any changes they have made) over the top of the current version of the page is intentional. WONTFIXing.,1383767339,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yofovlast3zou4zon7j5,task_subcomment,NA
+VisualEditor: blue template overlay overlaps other page elements,"Try clicking the commons template in https://pl.wikipedia.org/wiki/Omega_Centauri?veaction=edit for an example. This bug appeared a while back, and seems to have regressed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50970",1379555760,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-n4ayvtd5iz5jguzeqtvl,task_description,resolved
+VisualEditor: blue template overlay overlaps other page elements,"
+
+*** This bug has been marked as a duplicate of bug 51933 ***",1402294829,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n4ayvtd5iz5jguzeqtvl,task_subcomment,NA
+VisualEditor: blue template overlay overlaps other page elements,This is because we wrap generated content in a div for ease of replacement. Arguably we shouldn't.,1379696782,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-n4ayvtd5iz5jguzeqtvl,task_subcomment,NA
+VisualEditor: Media items are inserted after selection and do not replace them,"**Author:** `renukaalurkar`
+
+**Description:**
+1)Log into http://en.wikipedia.beta.wmflabs.org
+2)Go to your user page
+3)Click on Edit beta tab
+4)Click on More
+5)Click Media
+6)Enter santa claus, select a image from the selection of images
+7)Select the image(the image is displayed in light blue)
+8)Again click on More, then Media and select another image.
+
+Expected:The original/old image should be replaced by the new image.
+Observed: The new image is added and the original image is also displayed.
+
+Another observation: Also, suppose there are 4 images Image1, Image2, Image3, Image4 one below the other. If Image2 is selected and I try to replace it with a new image, the new image appears in the place of Image3(instead of Image2).
+
+Observed on Firefox and Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51033",1379530500,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ql37zwei7lw6idcpnjvx,task_description,declined
+VisualEditor: Media items are inserted after selection and do not replace them,"Yes, confirming that this is intentional; closing as ""WONTFIX"". I agree that changing in line with bug 51033 would make more sense.",1380657485,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ql37zwei7lw6idcpnjvx,task_subcomment,NA
+VisualEditor: Media items are inserted after selection and do not replace them,"I can confirm this is the current behaviour, and that both points are due to the same reason: new images are inserted immediately after a selected image.
+
+However I'm not sure that this behaviour is incorrect though as it is consistent with what happens when a user inserts media or a template with text selected (the template/media is inserted after the selection rather than overwriting it) - see bug 52460.
+
+There is an open request for the media settings dialog to allow an image to be easily changed though (bug 51033), which I think is a better way to handle this.",1380657191,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ql37zwei7lw6idcpnjvx,task_subcomment,NA
+VisualEditor: Adding bold/italics to spaces before/after a word results in ugly wikitext,"Which is something like '' this '' as opposed to something like ''that''. Of course this is also true for the source editor, but since the wikilink tool already gets rid of spaces at the beginning or at the end of a word, I wanted to make sure this can/should also be done when just formatting it (and it's being requested).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379509800,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mlek6l25jsi4523n6c4x,task_description,resolved
+VisualEditor: Adding bold/italics to spaces before/after a word results in ugly wikitext,"This will be fixed by bug 52037.
+
+*** This bug has been marked as a duplicate of bug 52037 ***",1383767551,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mlek6l25jsi4523n6c4x,task_subcomment,NA
+VisualEditor: Adding bold/italics to spaces before/after a word results in ugly wikitext,"User Steven at fr.wp asks that VE somehow recognizes and avoids that formatting is applied to spaces, since this results in ugly wikitext.
+He suggests that spaces get highlighted so that people can easily recognize them; they might become black (when ""bold"" is applied) or grey (when ""italics"" is applied).",1382971506,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mlek6l25jsi4523n6c4x,task_subcomment,NA
+VisualEditor: prevent creating internal links with no displayed text or warn this is happening,"It is not easy, but you can create an empty wikilink with VE, https://en.wikipedia.org/w/index.php?title=Ascending_cholangitis&curid=5544827&diff=572776141&oldid=566427601 (I was able to reproduce that somehow, I think I just added the link to an empty space).
+I can't imagine a situation where this is desirable or useful, please correct me if I am wrong.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379502900,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-dfnjvi4ebxg4qf7ygljp,task_description,resolved
+VisualEditor: prevent creating internal links with no displayed text or warn this is happening,"Merging with bug 37835.
+
+*** This bug has been marked as a duplicate of bug 37835 ***",1380072033,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dfnjvi4ebxg4qf7ygljp,task_subcomment,NA
+visible parsoid HTML in existing Flow content on toro,"I updated Flow, Parsoid, and VisualEditor on toro. Adding a new post worked fine and brought up VE (after a long delay during which the text area should probably be locked) and I could WYSIWYG. \o/
+
+But existing summary and some posts on http://toro.wmflabs.org/wiki/Special:Flow/Sandbox_2 that have images and links in them show stuff like
+  <a rel=""mw:WikiLink"" href="".//Subpage"" data-parsoid=""{""stx"":""simple"",""a"":{""href"":"".//Subpage""},""sa"":{""href"":""/Subpage""},""dsr"":[89,101,2,2]}"">
+
+suggesting Flow is having problems figuring out Parsoid HTML content.
+
+I had set $wgFlowUseParsoid=true, now I think obsolete. I tried setting $wgFlowContentFormat='html', didn't seem to change behavior.
+
+Firebug reported some XHR errors, possibly from some VE API call, but now not.
+
+If the issue is existing content doesn't render right, this is fine to mark WONTFIX. We haven't promised data compatibility yet.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1379482140,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-qjg3q7wq3q3awr64hcmy,task_description,resolved
+visible parsoid HTML in existing Flow content on toro,"(In reply to comment #2)
+> This is due to us previously not tracking what kind of content was stored in
+> the field.
+Yup, flow_revision rev_flags had just 'utf-8'.
+
+> UPDATE flow_revision set rev_flags = CONCAT(rev_flags, ',html' ) WHERE
+> rev_flags NOT LIKE '%html%' and rev_flags NOT LIKE '%wikitext%';
+
+It worked! (now Toro has other errors...)",1379545289,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-qjg3q7wq3q3awr64hcmy,task_subcomment,NA
+visible parsoid HTML in existing Flow content on toro,"This is due to us previously not tracking what kind of content was stored in the field.  We now store a value of either 'html' or 'wikitext' in the content flags of the revision.  Not highly efficient, but the following query would fix the issue:
+
+
+UPDATE flow_revision set rev_flags = CONCAT(rev_flags, ',html' ) WHERE rev_flags NOT LIKE '%html%' and rev_flags NOT LIKE '%wikitext%';
+
+Untested, but should work.  Not sure if its worthwhile to build out the proper maintenance script to migrate.",1379515263,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-qjg3q7wq3q3awr64hcmy,task_subcomment,NA
+visible parsoid HTML in existing Flow content on toro,Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/185,1379483847,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-qjg3q7wq3q3awr64hcmy,task_subcomment,NA
+VisualEditor: Dimensions of small images are lost in rendering,"Images that have thumbnail sizes that are larger than the original should be rendered at the specified size, not the size of the original.
+
+MediaWiki core does this, but somewhere between MediaWiki/Parsoid/VisualEditor the specified dimensions are lost.
+
+
+For example, on https://www.mediawiki.org/wiki/VisualEditor/Team there are various uses of [[File:Wikimedia_Foundation_office_camera_shy.png]] (of which the full size is 140px). The thumbnail size on that page is 150px, and when viewing the page normally it is rendered at 150px (browser scales up from 140px non-thumb url), but when editing in VisualEditor the node has a width attribtue of 140 instead of 150.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379390340,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-bd72y7iiei67kbxti76b,task_description,resolved
+VisualEditor: Dimensions of small images are lost in rendering,Re-checked on https://www.mediawiki.org/wiki/VisualEditor/Team - seems to be fixed.,1415912062,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-bd72y7iiei67kbxti76b,task_subcomment,NA
+VisualEditor: Dimensions of small images are lost in rendering,Fixed in 2013.,1415881118,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bd72y7iiei67kbxti76b,task_subcomment,NA
+Cant edit as logged in,"Using FF 23.0.1 and Google Chrome 29.0.1547.66 m. Try edit w:en:Ondine's curse from a section #Treatment and prognosis. When logged the page shows to be in process, but never allowes editing. Why I log of editing via VE is possible within seconds.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1379362020,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-sj7ezonvgeb3be62737a,task_description,invalid
+Cant edit as logged in,"OK, thank you.",1379399232,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-sj7ezonvgeb3be62737a,task_subcomment,NA
+Cant edit as logged in,"This sounds like you have a gadget or user script that is breaking VisualEditor - I can make an edit successfully: https://en.wikipedia.org/w/index.php?title=Ondine%27s_curse&diff=573233549&oldid=565577837
+
+If you disable your scripts and gadgets one-by-one you should be able to discover which one causes the problem, which will allow you to notify the author that their code is broken and needs to be fixed.
+
+Marking as ""INVALID"" as gadgets are not tracked in Bugzilla but on-wiki. Sorry for the disruption - if you need a developer to explain to the offending gadget's author how to fix their code, please direct the author to us in IRC at #mediawiki-visualeditor, on e-mail or here on Bugzilla.",1379376765,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sj7ezonvgeb3be62737a,task_subcomment,NA
+Cant edit as logged in,"Sorry for mispeling. ""When I log off...""",1379362130,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-sj7ezonvgeb3be62737a,task_subcomment,NA
+VisualEditor: Edit summary field loses focus when pasting (Firefox),"When pasting some text into the edit summary box in Firefox 23 (via Ctrl+V or context menu), the paste occurs, but the edit summary box loses focus.
+
+Possibly related to bug 53632??
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378792920,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-pdpn7hvlculri4ccy42t,task_description,resolved
+VisualEditor: Edit summary field loses focus when pasting (Firefox),"Now that the edit summary is in its own window, this bug has gone away. I don't know whether the plan is to eventually return to the edit confirmation flyout - if so this bug may well reappear.",1393634141,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-pdpn7hvlculri4ccy42t,task_subcomment,NA
+Templates and tables {{infobox ship begin}},"This is going to give you a headache
+
+{{Infobox ship begin}}
+http://en.wikipedia.org/wiki/Template:Infobox_ship_begin
+is used in 26840 pages. I provides styling for tables used to make infoboxes relating to ships. It is used like
+
+{|{{Infobox ship begin}}
+{{Infobox ship image
+|Ship image=[[File:Whydah-model.jpg|300px]]
+|Ship caption=The ''Whydah Gally'' (1716–1717)
+}}
+{{Infobox Ship Career
+...
+}}
+|-
+|Commanded by:
+|Cap't. [[Lawrence Prince]]
+...
+|}
+
+The template transcludes {{WPMILHIST Infobox style}} which provides CSS styling
+class=""infobox {{#if:{{{2|}}}|{{{2}}}}}"" style=""float: right; clear: right; width: 315px; border-spacing: 2px; text-align: left; font-size: 90%;""
+So the table start tag and its styling are separate.
+
+Unsurprisingly VE fails to edit pages with this template correctly. The following was reported at 
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=572065469
+
+Open the article in the visual editor, e.g. by visiting https://en.wikipedia.org/wiki/Whydah_Gally?veaction=edit
+Observe the article now leads with the out-of-place text 
+ <nowiki>class=""infobox "" style=""float: right; clear: right; width: 315px; border-spacing: 2px; text-align: left; font-size: 90%;""</nowiki>
+try to click ""save page"" but note that it is not active
+make a trivial change so that ""save page"" is active.  Click it
+Click ""review your changes"", not that it says that
+<nowiki>{{Italic title}}{|{{Infobox ship begin}}</nowiki>
+was replaced with
+<nowiki>{{Italic title}}{{Infobox ship begin}}
+{|{{Infobox ship begin}}</nowiki>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378673760,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-lxnv4tg7oifuczocddhi,task_description,resolved
+Templates and tables {{infobox ship begin}},"
+
+*** This bug has been marked as a duplicate of bug 53139 ***",1386015391,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-lxnv4tg7oifuczocddhi,task_subcomment,NA
+Templates and tables {{infobox ship begin}},"Thanks for filing the report. We should have a fix for the edit corruption bug soon (it will be fixed as part of a patch that Arlo is working on). More later on the other parts of the bug, once we discuss how to handle this.",1378861053,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-lxnv4tg7oifuczocddhi,task_subcomment,NA
+VisualEditor: Disallow media items in other media items' captions,"This is a strange edit, where a new editor inserted an image in the image description of an existing image. A bug or something that should be able to be done? 
+
+https://sv.wikipedia.org/w/index.php?title=Dry_Martini&diff=prev&oldid=23709630
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378584900,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-zomjkczfpnrvxzpe4yzr,task_description,invalid
+VisualEditor: Disallow media items in other media items' captions,"Yeah, this is valid (if odd) wikitext, and so VisualEditor supports it.",1383759108,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zomjkczfpnrvxzpe4yzr,task_subcomment,NA
+VisualEditor: Disallow media items in other media items' captions,"I can't think where off the top of my head, but I have seen small inline images in image descriptions at en.wp before. I think it was being used as a key for the main image or something like that.
+
+It's not common, but its the sort of thing that could be useful on occasion.",1379685701,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-zomjkczfpnrvxzpe4yzr,task_subcomment,NA
+"When editing an infobox, the labels are sorted alphabetically and not in the original order","**Author:** `lionel.allorge`
+
+**Description:**
+In an infobox, items are in a certain logical order, for exemple, the image item and the caption are next to each other but the VisualEditor sort them alphabetically making it more difficult to find them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1378551060,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hesseird5ugq7qigg32p,task_description,resolved
+"When editing an infobox, the labels are sorted alphabetically and not in the original order","Indeed, this is not optimal. I'm marking this as a duplicate of bug 51930 which offers a way to sort this. Unfortunately that depends on bug 53608 which is presently not assigned to anyone to work on.
+
+*** This bug has been marked as a duplicate of bug 51930 ***",1380655447,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hesseird5ugq7qigg32p,task_subcomment,NA
+AssessmentBar gadget clashes with VisualEditor edit surface,"Bug pic
+
+Should this happen or shouldn't it?
+Btw, steps:
+1*  Install AssessmentBar from https://en.wikipedia.org/wiki/User:YuviPanda/AssessmentBar
+2* Go to an article.
+3* Go down to a picture or find the infobox.
+4* Click on the picture or infobox (when it's halfway through the AssessmentBar) and it will highlight the AssessmentBar (treating it like a picture or an infobox) AND/OR Click on the part of the AssessmentBar where the picture or infobox is getting highlighted and the infobox or picture will get selected instead of the AssessmentBar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11559}",1378540620,PHID-USER-wel3wo6tppcxgnrthxls,False,PHID-TASK-djpv4d2tw7he7bcaiwgo,task_description,invalid
+AssessmentBar gadget clashes with VisualEditor edit surface,"Thanks.
+As we don't track specific gadgets in Bugzilla this should likely be reported under https://en.wikipedia.org/wiki/User_talk:YuviPanda/AssessmentBar instead.
+
+Closing as INVALID because Bugzilla is not the right place to follow up on user scripts, not because there is no bug that should get fixed.",1378918457,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-djpv4d2tw7he7bcaiwgo,task_subcomment,NA
+AssessmentBar gadget clashes with VisualEditor edit surface,"Moving out of VisualEditor; in general, gadgets have to be made to work with VisualEditor and not the other way around.",1378914055,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-djpv4d2tw7he7bcaiwgo,task_subcomment,NA
+AssessmentBar gadget clashes with VisualEditor edit surface,CC'ing Yuvi as this covers AssessmentBar,1378909636,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-djpv4d2tw7he7bcaiwgo,task_subcomment,NA
+VisualEditor: weird behavior with double square brackets,"Try to start a line with a wikilinked word as you might do in the source editor.
+
+1) Typing the opening double square brackets will not trigger the no-markup warning.
+2) The opening brackets will immediately disappear, the closing ones will stay.
+3) When you reach the second closing bracket, VE will also add another one on the following line. (If instead of moving to step 4 you use the keyboard arrows around the word, you will not be able anymore to type something outside the brackets, and will need your mouse to place yourself outside of them).
+4) Keep typing something instead, then press Enter: whatever you added is automatically copied to the next line, while the ""third"" square bracket is furtherly moved onto the next line.
+5) Now add the brackets to an already existing word, correctly triggering the warning. Save anyway.
+6) Review the changes. The brackets that triggered the warning did not trigger the nowiki tags as well. An opening one and a closing one are gone, and what is left is weird anyway. (This can also be triggered before saving by hitting Back Space, but I can't say where).
+The brackets that we added in the first place are all gone, the duplicated text is gone as well, just a lonely closing bracket stands still.
+
+https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=61362482&oldid=61361463
+
+Reminds me of https://bugzilla.wikimedia.org/show_bug.cgi?id=53079, actually.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57207",1378482300,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ktfyzhjkb3urubsydtou,task_description,declined
+VisualEditor: weird behavior with double square brackets,"I think this may have been a cacheing error? I can't reproduce, but it feels a lot like bug 53079, yes.",1383759476,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ktfyzhjkb3urubsydtou,task_subcomment,NA
+"VisualEditor: Editor changed a parameter in a template, but the parameter was removed when they clicked ""Apply Changes""","A user at it.wp reports that he could not successfully replace a picture with this edit https://it.wikipedia.org/w/index.php?title=Castello_di_Serravalle_%28Bosa%29&diff=61339995&oldid=61339964, although he managed to do so on other occasions, so he knows how it works.
+He just replaced Bosa Castle.jpg with Veduta del Castello.JPG, and correctly previewed the latter.
+But upon saving, the pic was gone - the field is empty. He tried again later, and managed to reproduce this behavior.
+Other users, including me, are not able to reproduce this.
+He's using Chrome with Snow Leopard. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62366",1378478400,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-53pjjq3mogcsnoshnrpu,task_description,declined
+"VisualEditor: Editor changed a parameter in a template, but the parameter was removed when they clicked ""Apply Changes""","I can't quite understand this bug report - the user edited the template, changed the parameter for the image name, but when they applied the changes, the parameter was removed (and so no image)?
+
+I'm going to mark as WORKSFORME, but please re-open if anyone can reproduce.",1383758872,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-53pjjq3mogcsnoshnrpu,task_subcomment,NA
+"VisualEditor: Wikitext warning not triggered by <references />, <i>, etc.","en.wp user Fram reports:
+""When I add something that VE decides needs ""nowiki"", it usually gives the warning ""Wikitext markup detected"". However, when I add <references/> to the bottom of a page, he wraps it in ""nowiki""s, but no warning appears (while it does work with e.g. {{reflist}})""
+
+My testing at https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox2&diff=571756019&oldid=570197356 shows that <i> and <small> also get nowikied without triggering the warning.
+
+<!-- --> neither triggers the warning nor gets nowikied. I am about to start a discussion about whether that is desired or not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56213",1378458780,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5usozn6lenkcoenzeuyk,task_description,declined
+"VisualEditor: Wikitext warning not triggered by <references />, <i>, etc.","This is intentional; adding a complete set of wikitext detection would be very burdensome (i.e. slow VE down for users) without adding a lot of value.
+
+People who know complex things like HTML or advanced wikitext like <references /> will quickly learn that it doesn't work; this functionality is an aide-memoire for  newbies and rare users.
+
+Marking as WONTFIX, but happy to discuss.",1383758460,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5usozn6lenkcoenzeuyk,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),"The German template for quotes:
+
+https://de.wikipedia.org/wiki/Vorlage:Zitat
+
+eats refs, or rather their display at the end of the article, if the refs are inserted in it & the article is loaded in VE. Example articles:
+
+https://de.wikipedia.org/wiki/Arvo_P%C3%A4rt -> ref 5 & 8
+
+https://de.wikipedia.org/wiki/The_Rolling_Stones -> 26, 123-125
+
+https://de.wikipedia.org/wiki/Chick_Corea -> ref 12
+
+Report:
+
+https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=122231626#Einzelnachweise_am_Artikelende_werden_im_VE_nicht_angezeigt
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50474",1378330980,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_description,resolved
+De.WP's quote template eats refs (or gets eaten),"Merging this with bug 50474 which I have managed to determine that this is the same as that.
+
+*** This bug has been marked as a duplicate of bug 50474 ***",1383003781,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),"Updates:
+
+Rolling Stones: The section Discografie
+
+https://de.wikipedia.org/wiki/The_Rolling_Stones#Diskografie
+
+includes another article inserted as template:
+
+https://de.wikipedia.org/wiki/The_Rolling_Stones/Disko-_und_Videografie
+
+However, the article isn't displayed in full but only relevant parts, picked by  onlyinclude-tags.
+
+Shine a Light: The issue not included in a template is caused by something VE apparently can't handle in spelling out the ref name but Wikicode can: ""_"" vs "" "":
+
+https://de.wikipedia.org/w/index.php?title=Shine_a_Light&diff=prev&oldid=122747897
+
+The other two are eaten by the template, i.e. the same source is also referred to in refs outside the template and VE simply doesn't count the template-inserted refs.",1380840894,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),This looks like a side effect of the underlying problem in bug 50474.,1380552169,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),"Chances are this issue is systemic; three more examples:
+
+1) Info box for movie articles:
+
+https://de.wikipedia.org/wiki/Vorlage:Infobox_Film
+
+includes three refs in 
+
+https://de.wikipedia.org/wiki/Shine_a_Light
+
+and they all get eaten if the entry is loaded in VE.
+
+2) Info box for corporate entities:
+
+https://de.wikipedia.org/wiki/Vorlage:Infobox_Unternehmen
+
+see the first four refs in 
+
+https://de.wikipedia.org/wiki/Sony
+
+3) https://de.wikipedia.org/wiki/Vorlage:Infobox_Chemikalie
+
+eats the two included refs in:
+
+https://de.wikipedia.org/wiki/Magnesiumcarbonat",1378501325,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+De.WP's quote template eats refs (or gets eaten),"from the report:
+
+* a) {{<ref>source a</ref>}} -> eats ref completely
+
+in all other reported cases:
+
+* b) {<ref>source b</ref>} 
+* c) {{<ref>source c</ref>
+* d) {<ref>source d</ref> 
+* e) {{<ref>source a</ref>}.
+
+VE tells the user once ""This is Wikitext"" but then carries on; see test page:
+
+https://de.wikipedia.org/w/index.php?title=Benutzerin:Miss-Sophie/Spielwiese&oldid=122231700",1378331713,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-gcsogk6cy5vhnwnvhuql,task_subcomment,NA
+VisualEditor: Corruption: Leading whitespace removed from pre block,"See https://en.wikipedia.org/w/index.php?title=Epigram_%28programming_language%29&oldid=567048374&veaction=edit and click ""save"" (note that save box warns about corruption) and then ""view changes"" (ignoring the changes I have since made). The pre block has been corrupted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1378330500,PHID-USER-bug3zrlooz3bdmi4fyl7,False,PHID-TASK-wf4d3yulifq7pdamnvpv,task_description,resolved
+VisualEditor: Corruption: Leading whitespace removed from pre block,"
+
+*** This bug has been marked as a duplicate of bug 54083 ***",1379613849,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wf4d3yulifq7pdamnvpv,task_subcomment,NA
+Request for edit summary preview,"A De.WP user suggested to include a preview for the edit summary. Report:
+
+https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=122207411#Vorschau_f.C3.BCr_Zusammenfassung_und_Quellen
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378253700,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-uro44a5vqso2sy7u2arn,task_description,resolved
+Request for edit summary preview,"
+
+*** This bug has been marked as a duplicate of bug 42139 ***",1380545659,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-uro44a5vqso2sy7u2arn,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"See https://it.wikipedia.org/w/index.php?title=Bisanzio_Lupis&diff=61160806&oldid=51778070 .
+
+When creating a section for references and adding the relevant tag,
+it will suppress the Related Articles section - just the heading, not the content.
+
+I reproduced it easily in my sandbox by just adding the contents that you can see in the diff above.
+Note that it is not related to the reference being added in the same edit; here for instance https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=61285258&oldid=61285224 it was added previously.
+
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378206960,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_description,resolved
+VisualEditor: adding section for references will suppress the Related Articles one,Making resolved instead because it probably //was// a problem in 2013 :),1438627770,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,Making resolved instead because it probably //was// a problem in 2013.,1438627757,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"Yup, can't reproduce this one.",1425653133,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"Closing task as declined as per last two comments as nobody managed to reproduce.
+
+Please reopen if this problem still happens and provide an URL/link to an example. Thanks!",1425487289,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"> When creating a section for references and adding the relevant tag,
+
+What I tried:
+Write the text ""Notes"" right above ""Voci correlate"", mark that text, choose ""Heading"" from the formatting dropdown, then add a reference via ""Cite > Basic"" somewhere in the text, then click below the ""Notes"" heading and choose ""Insert > References list"" in VE.
+
+No issues either. Let's close this soon if noone can reproduce (already set to Stalled status).",1424366202,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: adding section for references will suppress the Related Articles one,"I've attempted to reproduce the two test cases in a sandbox on the Italian Wikipedia. In both cases ([[https://it.wikipedia.org/w/index.php?title=Utente:Neil_P._Quinn/test&diff=prev&oldid=70691767|full]] and [[https://it.wikipedia.org/w/index.php?title=Utente:Neil_P._Quinn/test&diff=next&oldid=70691826|reduced]]), adding the section heading and references list worked correctly.",1423081747,PHID-USER-cbjanejnwkkrbnj77d2d,True,PHID-TASK-ez3lf5ze2ra5vwgm2kwo,task_subcomment,NA
+VisualEditor: Wikitext warning triggered without adding wikitext,"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.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378050300,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dusvcxcsy7gqikdevzgn,task_description,resolved
+VisualEditor: Wikitext warning triggered without adding wikitext,"
+
+*** This bug has been marked as a duplicate of bug 51751 ***",1378458424,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dusvcxcsy7gqikdevzgn,task_subcomment,NA
+"VisualEditor: Show and make editable <nowiki>, </nowiki> and <nowiki /> tags","There is discussion at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=571087443#nowiki_tags about using the edit filter to block edits adding the <nowiki /> tag in mainspace. However it was pointed out that ""the user probably has no way to know what they need to fix in order to resubmit their edit.  They can't find the nowiki tag, as it is invisible.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49806
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49603",1378049580,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-brld2i7xjlh2vp4m2jxn,task_description,declined
+"VisualEditor: Show and make editable <nowiki>, </nowiki> and <nowiki /> tags","WONTFIXing this bug instead:
+
+<nowiki> is fundamentally an artefact of wikitext that users should be (blissfully) unaware of, and Parsoid should ""just make work"" as needed. Right now this is generally true, and it will get better, not worse, in the future, so this is not needed (which is good, because VisualEditor has no way of knowing whilst a user is editing whether Parsoid will decide to put a <nowiki> in).",1390023864,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-brld2i7xjlh2vp4m2jxn,task_subcomment,NA
+"VisualEditor: Show and make editable <nowiki>, </nowiki> and <nowiki /> tags","Gah, sorry, wrong bug.",1390023748,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-brld2i7xjlh2vp4m2jxn,task_subcomment,NA
+"VisualEditor: Show and make editable <nowiki>, </nowiki> and <nowiki /> tags","This is because <nowiki /s> (unlike <nowiki>s) are ""meta"" items in the DOM rather than things VE can edit; merging with bug 56381.
+
+*** This bug has been marked as a duplicate of bug 56381 ***",1390023708,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-brld2i7xjlh2vp4m2jxn,task_subcomment,NA
+text duplicated when following an image,"In some odd circumstances the text immediately following an image is duplicated. You can see the effect in
+http://en.wikipedia.org/w/index.php?title=Danny_Nalliah&oldid=570830443&veaction=edit
+where the text '''Daniel (Danny) Nalliah''' is duplicated. 
+
+To make things more confusing it does not occur for every revision 
+http://en.wikipedia.org/w/index.php?title=Danny_Nalliah&oldid=570591483&veaction=edit
+works fine.
+
+To make things thoughly weird in this revision in my sandbox
+http://en.wikipedia.org/w/index.php?title=User:Salix_alba/sandbox&oldid=570839025
+the text '''Daniel (Danny) Nalliah''' does not appear. Yet it magically appear in VE
+http://en.wikipedia.org/w/index.php?title=User:Salix_alba/sandbox&direction=prev&oldid=570839025&veaction=edit
+
+This issues is discussed at 
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Still_looks_like_VE_Feedback_to_me
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378023300,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-keti3xueyglzi4p4spht,task_description,declined
+text duplicated when following an image,"Cannot reproduce the problem either with the given links and Firefox 35...
+Assuming that this has magically fixed itself.
+Hence closing this ticket as DECLINED as no-one else could reproduce so far, unfortunately.
+
+@SalixAlba: If you can still reproduce this problem, please provide browser information. (Also, testing with the browser and having add-ons / extensions disabled or such might be welcome.)",1423705265,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-keti3xueyglzi4p4spht,task_subcomment,NA
+text duplicated when following an image,Cannot reproduce. Was this fixed at some point?,1421888484,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-keti3xueyglzi4p4spht,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"I cannot paste text into the edit summary with Ctrl+V or right click and paste when I use Chromium Version 28.0.1500.71 Ubuntu 13.04 (28.0.1500.71-0ubuntu1.13.04.1). Nothing happens. It works fine in FireFox though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377976740,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_description,resolved
+VisualEditor: Cannot paste into edit summary in Chromium,"Now that the edit summary is in its own window, this bug has gone away. I don't know whether the plan is to eventually return to the edit confirmation flyout - if so this bug may well reappear.",1393634250,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"en.wp user ToE further reports:
+Upon upgrading to Google Chrome: 29.0.1547.76 (Official Build 223446) m, JavaScript V8 3.19.18.23, paste into edit summary works properly.",1380030184,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"en.wp user ToE reports:
+[this bug] also applies to Google Chrome, version ""29.0.1547.66 (Official Build 220848) m"", JavaScript V8 3.19.18.19, running on Windows 7 Home Premium, Service Pack 1. Paste into edit summary works fine on the same machine in Firefox version 23.0.1.",1379878291,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"I'm observing the exact same problem in the same Chromium version on Ubuntu 13.04 (no error messages in the JavaScript console, works fine in Firefox).",1379211478,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"**eliashedberg** wrote:
+
+I had the same (or a similar) problem in Chrome 29.0.1547.62 under Mac OS X 10.6.8: when pasting the string ""Lavoslav Ružička"" into the edit summary the page behind the summary jumped down and back up (or the other way around) but there was no text inserted into the edit summary.
+
+I can recreate the failed paste action in the edit summary of my sandbox, but the text behind the edit summary doesn’t move (potentially because that article is too short).
+
+I can recreate the failed paste action with other strings too (in Chrome), i.e. no pasting works, no matter what string I try to paste.
+
+In Firefox, pasting into the edit summary works fine (Firefox 23.0.1, also under OS X 10.6.8).",1378189372,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,"Hm, how do I find the browser's error console? If it's F12 and Console, then no, no messages there. 
+
+I noticed that if the page I was editing is not scrolled to the top, when I try to paste, it behaves as if I press arrow up.",1378154905,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+VisualEditor: Cannot paste into edit summary in Chromium,Is there any kind of output in the browser's error console when you try?,1378119003,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dfdz2k3zlkzv6jpt4n44,task_subcomment,NA
+Delete tests from browsertests repository that are moved to other repositories,"We have moved ULS and VisualEditor tests to their repositories. Delete the code from browsertests repository.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377862680,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_description,resolved
+Delete tests from browsertests repository that are moved to other repositories,"Reopening until we decide if search.feature file should:
+
+- stay in browsertests repo
+- be moved to CirrusSearch repo
+- be deleted",1381823392,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_subcomment,NA
+Delete tests from browsertests repository that are moved to other repositories,"Change 88992 merged by Cmcmahon:
+Flow tests are moved to Flow repository
+
+https://gerrit.wikimedia.org/r/88992",1381420151,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_subcomment,NA
+Delete tests from browsertests repository that are moved to other repositories,"Chris, did we move all tests from browsertests repository to relevant repositories? Should this bug be resolved?
+
+The only remaining feature file that I see in browsertests repository that should be either deleted or moved to CirrusSearch repository is search.feature. Or, should we leave it in browsertests repository?",1381416666,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_subcomment,NA
+Delete tests from browsertests repository that are moved to other repositories,"Change 88992 had a related patch set uploaded by Zfilipin:
+Flow tests are moved to Flow repository
+
+https://gerrit.wikimedia.org/r/88992",1381416355,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pqtihvfc7f4d73rdtnjq,task_subcomment,NA
+Figure out how to reuse common test code between repositories,"At the moment we have similar setup code for browser tests in 6 repositories:
+
+https://github.com/wikimedia/qa-browsertests
+https://github.com/wikimedia/mediawiki-extensions-CirrusSearch
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend
+https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor
+https://github.com/wikimedia/mediawiki-extensions-Wikibase
+
+Figure out a way how to reduce code duplication. We should probably create a Ruby gem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377862440,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ma7ogjs2kvk66wshe44k,task_description,resolved
+Figure out how to reuse common test code between repositories,"
+
+*** This bug has been marked as a duplicate of bug 53579 ***",1381410774,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ma7ogjs2kvk66wshe44k,task_subcomment,NA
+Update readme file so it contains links to all repositories with Selenium tests,"README.md[1] file has information about Selenium tests in
+
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend
+
+Add links to:
+
+https://github.com/wikimedia/mediawiki-extensions-CirrusSearch
+https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor
+https://github.com/wikimedia/mediawiki-extensions-Wikibase
+
+1: https://github.com/wikimedia/qa-browsertests/blob/master/README.md
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377862320,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-dhqbmbptdf76io4mrpls,task_description,resolved
+Update readme file so it contains links to all repositories with Selenium tests,"Change 90562 merged by jenkins-bot:
+Relevant links
+
+https://gerrit.wikimedia.org/r/90562",1382362818,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dhqbmbptdf76io4mrpls,task_subcomment,NA
+Update readme file so it contains links to all repositories with Selenium tests,"Change 90562 had a related patch set uploaded by Zfilipin:
+Relevant links
+
+https://gerrit.wikimedia.org/r/90562",1382112246,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dhqbmbptdf76io4mrpls,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,".ruby-gemset and .ruby-version should be removed and RVM setup should be moved to Gemfile[1].
+
+Repositories that are doing it right:
+https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor
+
+Repositories that should be updated:
+
+https://github.com/wikimedia/mediawiki-extensions-CirrusSearch
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend
+https://github.com/wikimedia/mediawiki-extensions-Wikibase
+https://github.com/wikimedia/qa-browsertests
+
+1: https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector/blob/master/tests/browser/Gemfile#L1-L2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377861960,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-uvse6kpckod47zira6mk,task_description,resolved
+Make sure all repositories have the latest version of shared code,All repositories that have Selenium tests in Ruby now use mediawiki-selenium gem.,1382729080,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87552 merged by jenkins-bot:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87552",1382713394,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87581 merged by jenkins-bot:
+[browser test] Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87581",1382546758,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87563 merged by jenkins-bot:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87563",1382546616,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87125 merged by Cmcmahon:
+Moving code used in multiple repositores to a Ruby gem
+
+https://gerrit.wikimedia.org/r/87125",1382363305,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 90560 had a related patch set uploaded by Zfilipin:
+WIP Moved confing files from qa/browsertests repository
+
+https://gerrit.wikimedia.org/r/90560",1382111650,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 90559 had a related patch set uploaded by Zfilipin:
+WIP Moved config files to mediawiki/selenium repository
+
+https://gerrit.wikimedia.org/r/90559",1382111624,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 88010 merged by Tobias Gritschacher:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/88010",1381745570,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,*** Bug 53581 has been marked as a duplicate of this bug. ***,1381410774,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,*** Bug 54600 has been marked as a duplicate of this bug. ***,1381410415,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 88010 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/88010",1381134855,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87158 merged by jenkins-bot:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87158",1380988261,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87542 merged by jenkins-bot:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87542",1380987438,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87581 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87581",1380901487,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87563 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87563",1380896472,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87552 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87552",1380892900,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87542 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87542",1380888245,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,For more information see http://lists.wikimedia.org/pipermail/qa/2013-October/000509.html,1380805607,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87158 had a related patch set uploaded by Zfilipin:
+Moving shared code to mediawiki-selenium Ruby gem
+
+https://gerrit.wikimedia.org/r/87158",1380730588,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 87125 had a related patch set uploaded by Zfilipin:
+Moving code used in multiple repositores to a Ruby gem
+
+https://gerrit.wikimedia.org/r/87125",1380723813,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 86838 merged by jenkins-bot:
+Updated ULS repository to the latest version of shared test files
+
+https://gerrit.wikimedia.org/r/86838",1380645048,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 86845 merged by Cmcmahon:
+Updated the repository to the latest version of shared test files
+
+https://gerrit.wikimedia.org/r/86845",1380644856,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 86845 had a related patch set uploaded by Zfilipin:
+Updated the repository to the latest version of shared test files
+
+https://gerrit.wikimedia.org/r/86845",1380630502,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 86838 had a related patch set uploaded by Zfilipin:
+Updated ULS repository to the latest version of shared test files
+
+https://gerrit.wikimedia.org/r/86838",1380628011,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82039 merged by Tobias Gritschacher:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82039",1378124036,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82035 merged by jenkins-bot:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82035",1377987180,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82034 merged by jenkins-bot:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82034",1377987114,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82033 merged by Cmcmahon:
+Removed unused Rake Ruby gem
+
+https://gerrit.wikimedia.org/r/82033",1377987032,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82032 merged by Cmcmahon:
+Removed unused HTML Cucumber formatter
+
+https://gerrit.wikimedia.org/r/82032",1377986999,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82039 had a related patch set uploaded by Zfilipin:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82039",1377896220,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82035 had a related patch set uploaded by Zfilipin:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82035",1377894902,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82034 had a related patch set uploaded by Zfilipin:
+Updated test configuration to the latest version
+
+https://gerrit.wikimedia.org/r/82034",1377894425,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82033 had a related patch set uploaded by Zfilipin:
+Removed unused Rake Ruby gem
+
+https://gerrit.wikimedia.org/r/82033",1377893822,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 82032 had a related patch set uploaded by Zfilipin:
+Removed unused HTML Cucumber formatter
+
+https://gerrit.wikimedia.org/r/82032",1377893504,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 81929 merged by Cmcmahon:
+Updating shared code to the latest version
+
+https://gerrit.wikimedia.org/r/81929",1377883705,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"Change 81929 had a related patch set uploaded by Zfilipin:
+Updating shared code to the latest version
+
+https://gerrit.wikimedia.org/r/81929",1377871196,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Make sure all repositories have the latest version of shared code,"All repositories:
+
+https://github.com/wikimedia/qa-browsertests
+https://github.com/wikimedia/mediawiki-extensions-CirrusSearch
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend
+https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor
+https://github.com/wikimedia/mediawiki-extensions-Wikibase
+
+Files to update:
+
+config/config.yml
+config/cucumber.yml
+features/support/env.rb
+features/support/sauce.rb
+Gemfile
+Gemfile.lock
+README.md",1377870317,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-uvse6kpckod47zira6mk,task_subcomment,NA
+Send e-mail notification to relevant people after jenkins job is completed,"Who gets e-mail notification is documented in jobs.md[1]. At the moment Chris and I get notification for all jobs. Michelle is added for MobileFrontend, Rachel and James for VisualEditor.
+
+Nik Everett should be notified for CirrusSearch, Amir and Niklas for UniversalLanguageSelector.
+
+1: https://github.com/wikimedia/qa-browsertests/blob/master/docs/jobs.md
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377861600,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-skm7yk65ve7ofcodlrqs,task_description,resolved
+Send e-mail notification to relevant people after jenkins job is completed,"Change 88998 merged by Cmcmahon:
+Updated Jobs and documentation who gets e-mail notification when a Jenkins job fails
+
+https://gerrit.wikimedia.org/r/88998",1381846904,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-skm7yk65ve7ofcodlrqs,task_subcomment,NA
+Send e-mail notification to relevant people after jenkins job is completed,"Change 88998 had a related patch set uploaded by Zfilipin:
+Updated Jobs and documentation who gets e-mail notification when a Jenkins job fails
+
+https://gerrit.wikimedia.org/r/88998",1381417453,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-skm7yk65ve7ofcodlrqs,task_subcomment,NA
+VisualEditor: Images after template are shielded and uneditable in RTL,"I could not replicate this in LTR wikis (en.wiki or MediaWiki.org) but I suspect this is not so much ltr/rtl but floating behavior of the templates and images.
+
+See example here:
+https://he.wikipedia.org/wiki/%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%D7%AA:Mooeypoo/%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99/%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_%D7%95%D7%9E%D7%A9%D7%97%D7%A7%D7%99%D7%9D?veaction=edit
+
+The top two images are regular images (not templates) - they are perfectly editable if you remove the template at the top. They got their shielded status after I inserted that template.
+
+Steps to reproduce:
+1. Edit a page
+2. Insert some image (or more) to top
+3. Save page
+4. Edit again, insert template ""{{עליות}}"" just above the images. 
+5. Save.
+6. Edit again. Observe: The images jumped to the left (wrong float side) and are now uneditable. 
+7. Interesting fact: Remove the template and save, then go back into the editor and the images are still uneditable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377795900,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-jjwaxnsw7nonpkj5w5ug,task_description,resolved
+VisualEditor: Images after template are shielded and uneditable in RTL,This seems to be fixed now with the change of images and the way we render shields.,1406316798,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-jjwaxnsw7nonpkj5w5ug,task_subcomment,NA
+VisualEditor: Images after template are shielded and uneditable in RTL,Correction: images jump to the *right* (wrong floating side in RTL wikis) not left. Apparently my sense of directions needs its own bug report.,1377796057,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-jjwaxnsw7nonpkj5w5ug,task_subcomment,NA
+VisualEditor: broken reference tag swaps sections when VEditing,"If you open https://fr.wikipedia.org/w/index.php?title=Anna_Mouglalis&oldid=95468238&veaction=edit you'll notice a weird order of paragraphs. This is due to an extra space in the ref tag for the second reference. VE might probably autocorrect similar situations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377784560,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-m5whhh35h7fkdpaca77l,task_description,resolved
+VisualEditor: broken reference tag swaps sections when VEditing,"
+
+*** This bug has been marked as a duplicate of bug 52430 ***",1377786212,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-m5whhh35h7fkdpaca77l,task_subcomment,NA
+VisualEditor: Parameters in RTL can be duplicated in the transclusion dialog,"To reproduce:
+
+1. Go to this page: https://he.wikipedia.org/wiki/%D7%90%D7%9C%D7%9B%D7%A1%D7%A0%D7%93%D7%A8_%D7%94%D7%92%D7%93%D7%95%D7%9C
+2. Edit the infobox at the left side. 
+3. Behold! Some parameters appear both at the left panel (used) and also on the right panel (unused). Specific example, look for the parameters ""בן זוג"" and ""בת זוג"" 
+4. If you click the parameter ""בת זוג"" for example, on the left side (the used one) you will see data. If you click the one on the right side, it appears with empty textbox as if it's new.
+5. Click on the right side (as if to add param again) on ""בת זוג"" 
+6. Click again and again -- the parameter will keep being added to the list on the left in duplicates.
+
+And if the page is saved, the parameter is now completely removed.
+
+
+This has happened specifically in the hewiki but might be related to more than just RTL.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377741840,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-cbkpykct3waf2q7jincj,task_description,declined
+VisualEditor: Parameters in RTL can be duplicated in the transclusion dialog,"This works for me on hewiki and local on rtl settings. If anyone discovers this anew, please reopen.",1380749912,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-cbkpykct3waf2q7jincj,task_subcomment,NA
+VisualEditor: Parameters in RTL can be duplicated in the transclusion dialog,This seems to be fixed now.,1379704380,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-cbkpykct3waf2q7jincj,task_subcomment,NA
+VisualEditor: Link insertion dialog should preserve the case of the initial character,"Currently whenever a user enters a link when no text is selected the first character of the displayed link is always capitalised. This is often incorrect, e.g. in the middle of a sentence or for articles like [[iPhone]] or [[grep]].
+
+Especially until bug 50678 is fixed, correcting this is not at easy or intuitive.
+
+So, at least until bug 48789 and bug 50945 are fixed and the display text is settable in the dialog, and probably beyond that, it would be best if the displayed link used the same case as the search term entered. i.e.
+
+User entry ->  wikitext equivalent of desired output
+Green   ->  [[Green]]
+green   ->  [[green]]
+iPad    ->  [[iPad]]
+HAMmer  ->  [[Hammer]]
+london  ->  [[london]]
+
+Yes, this will result in some wrong captialisations, but no more than at present and will only be temporary (as noted above)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50678
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50745",1377720300,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hvan6ykhuzyhtye5e56x,task_description,resolved
+VisualEditor: Link insertion dialog should preserve the case of the initial character,"
+
+*** This bug has been marked as a duplicate of bug 50452 ***",1377802569,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hvan6ykhuzyhtye5e56x,task_subcomment,NA
+Right-click on newly linked page in VisualEditor opens invalid URL in new tab,"This is somewhat related to bug 50321.
+
+Steps to reproduce:
+
+1. Open your own sandbox/userpage (not a page in the mainspace) in VisualEditor.
+2. Add a link to a word (""xxx"").
+3. Control-click/right-click/command-click the new link to open the link in a new tab or new window.
+4. Discover that VisualEditor has sent you to an invalid URL:  http://en.wikipedia.org/w/Xxx or http://en.wikipedia.org/wiki/User:Whatamidoing_(WMF)/Xxx
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377715320,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lz4m6zadc7gusnegkxep,task_description,resolved
+Right-click on newly linked page in VisualEditor opens invalid URL in new tab,"This is bug 48915 although the bug title ""VisualEditor: Respect Parsoid's <base>"" describes the solution not the effect so I'm not surprised you didn't find it.
+
+*** This bug has been marked as a duplicate of bug 48915 ***",1377718799,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-lz4m6zadc7gusnegkxep,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,"Requested by James Forrester at QA mailing list:
+
+http://lists.wikimedia.org/pipermail/qa/2013-August/000339.html
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377688440,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_description,resolved
+Move VisualEditor Selenium test to VisualEditor repository,"Change 81486 merged by jenkins-bot:
+Moved VisualEditor Selenium tests from browsertests repository
+
+https://gerrit.wikimedia.org/r/81486",1377721181,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,"Change 81490 merged by Cmcmahon:
+Added support for running VisualEditor tests to Jenkins job template
+
+https://gerrit.wikimedia.org/r/81490",1377720850,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,"Change 81490 had a related patch set uploaded by Zfilipin:
+Added support for running VisualEditor to Jenkins job template
+
+https://gerrit.wikimedia.org/r/81490",1377696235,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,Resolved in https://gerrit.wikimedia.org/r/#/c/81486/,1377695195,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Move VisualEditor Selenium test to VisualEditor repository,"Change 81486 had a related patch set uploaded by Zfilipin:
+Moved VisualEditor Selenium tests from browsertests repository
+
+https://gerrit.wikimedia.org/r/81486",1377694989,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5xzxzrfm4dqssl7w5dix,task_subcomment,NA
+Show edit summary after clicking save,"**Author:** `molly.white5`
+
+**Description:**
+Only show the edit summary input box after the user clicks ""save"" (sort of like in the VisualEditor).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377659100,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-q6pz6kygm2rnc3zs7geb,task_description,declined
+Show edit summary after clicking save,"**molly.white5** wrote:
+
+See above comment.",1382039786,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-q6pz6kygm2rnc3zs7geb,task_subcomment,NA
+Show edit summary after clicking save,"**mr.heat** wrote:
+
+(In reply to comment #0)
+> Only show the edit summary input box after the user clicks ""save""
+
+But clicking ""save"" leaves the editor and reloads the page. If the edit summary is hidden and only shown after you clicked ""save"" you will see it only for a fraction of a second and not be able to enter anything.
+
+I guess you are suggesting to block the first click on the ""save"" button. First click shows the edit summary. Second click saves. I don't think this is useful for two main reasons:
+
+1. I want to be able to type something in the summary field while I'm still editing. Hiding the field removes this feature. I can't use it when I want. It forces me to remember everything I did and recap it in the end. This will lead to more empty and less descriptive summary lines.
+
+2. If I click a button labeled ""save"" I expect it to save and not to do something completely different. If you want to have this as an opt-in feature you can use the existing ""Prompt me when entering a blank edit summary"" setting or check my script [[de:User talk:TMg/forceEditSummary.js]]. Both do not hide the edit summary but block the ""save"" button one time if you forgot to enter a summary. The setting is server-side, my script is client-side and therefor a lot faster.
+
+I suggest to close this as ""works as expected"".",1382020847,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-q6pz6kygm2rnc3zs7geb,task_subcomment,NA
+VisualEditor: Media should be easily replaceable,"At the moment there doesn't appear to be a way to replace media - that is, to click on a media element, and select a different piece of media for that element. That's not a big deal at the moment, but we're going to move to a world where media settings are more complex - where alignment can be specified, referencing can be specified and permitted, so on and so forth.
+
+The result of this is that media elements will have a lot of data associated with them - media it's pretty hard to type out again if you find that the image (or video, or...whatever) needs to be replaced. It would be good to have a way of replacing images without losing the associated caption, size and alignment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377621000,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dhmvhapysnb7mmzkzrmc,task_description,resolved
+VisualEditor: Media should be easily replaceable,"I *knew* it's gotta be a dupe. ;)
+
+*** This bug has been marked as a duplicate of bug 51033 ***",1377621974,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dhmvhapysnb7mmzkzrmc,task_subcomment,NA
+Search and replace feature needed,"We need a search-and-replace feature in VisualEditor. This seacrh box should also support ULS
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377447840,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-5k5rt6qbkoyx3ta4vs6h,task_description,resolved
+Search and replace feature needed,"Hi Pavanaja. 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 48368 ***",1377460908,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5k5rt6qbkoyx3ta4vs6h,task_subcomment,NA
+Inserting and editing tables,"There should be a facility in VisualEditor for creating new table or edit an existing table
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377447540,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-lfg46f7cy7mmetnq3hpg,task_description,resolved
+Inserting and editing tables,"Indeed there should be such a feature, and one has been requested at bug 52181 so I'm marking this as a duplicate.
+
+*** This bug has been marked as a duplicate of bug 52181 ***",1377528014,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-lfg46f7cy7mmetnq3hpg,task_subcomment,NA
+Inserting and editing tables,"[New feature => setting the ""Severity"" field to ""enhancement"". 
+Feel free to do so yourself when filing a report.]",1377460978,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-lfg46f7cy7mmetnq3hpg,task_subcomment,NA
+VisualEditor: inconsistency when reviewing changes after a null edit,"User report:
+<<So I put a space and then a backspace.  Go to save, review changes to check and make sure it is a null edit, then it goes to this ""processing"" dialogue but then it shows ""Could not start the review because your revision matches the latest version of this page.""  So then I press the little back link on the dialogue, but it just goes back to the processing dialogue.  If the page is small, the processing is really quick, so before I can even press back again, it goes back to the ""Could not start"" warning message.  Even if I do manage to press the back a second time quickly, it will only stay at the save dialogue for a split second and then again bring me to the warning message, although ''then'' pressing back does take me to the save dialogue securely.  FF 23.0.1 Win7.>>
+
+I managed to reproduce this on Chrome as well, so which is the intended left button behaviour?
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377426720,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-inp4lb4bxjfhduddc4ri,task_description,resolved
+VisualEditor: inconsistency when reviewing changes after a null edit,"
+
+*** This bug has been marked as a duplicate of bug 53313 ***",1377426954,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-inp4lb4bxjfhduddc4ri,task_subcomment,NA
+VE does not finish initialization on KOWP,"**Author:** `ryuch`
+
+**Description:**
+VE not can be enabled by options in preferences for beta testing.
+When I click 'edit' on an article, the progress bar appear but does not finish initialization.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377353520,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z2y2nxnb7rd7vpntvfza,task_description,resolved
+VE does not finish initialization on KOWP,"This bug appears to be fixed as I can see VE edits happening in the recentchanges feed.
+
+https://ko.wikipedia.org/wiki/special:recentchanges?days=30&tagfilter=visualeditor",1380703487,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-z2y2nxnb7rd7vpntvfza,task_subcomment,NA
+VE does not finish initialization on KOWP,"**ryuch** wrote:
+
+Sorry, a critical typo I sent. 
+VE ""now"" can be enabled by options in preferences for beta testing.",1377353651,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z2y2nxnb7rd7vpntvfza,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"cucumber features/visual_editor_anon.feature:5 # Scenario: Basic edit fails 
+because VisualEditor these days shows an introductory disclaimer:
+
+  This is our new, easier way to edit. It's still in beta,
+  which means you might find parts of the page you can't edit...
+and so it fails with
+  expected ""You are not currently logged in. 
+which isn't visible until you dismiss the popup.
+
+I think the same explains a
+  timed out after 5 seconds, Element was not visible in 5 seconds
+that I'm getting in the similar
+cucumber features/visual_editor_logged_in.feature:5 # Scenario: Basic edit
+after applying gerrit 80709.
+
+The popup is in a div containing an iframe containing more divs until class=""ve-ui-mwBetaWelcomeDialog-content"", and then tests have to click outside it to dismiss it; and some day it will go away.
+
+Instead it seems better to set the ve-beta-welcome-dialog cookie to 1 upon visiting the site, which will turn off this disclaimer dialog.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1377334920,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_description,resolved
+VisualEditor tests fail due to introductory beta disclaimer popup,fixed,1382983457,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"Chris, this is fixed, right? Is there anything left here to do? Should we close the bug?",1381411550,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"Honestly, I would rather that VE behave the same on beta, test2wiki, and production. Preferably at more or less the same time.",1377806202,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"(In reply to comment #5)
+> Should this be closed since 80709 is merged into master?
+No, that's a different problem breaking VE tests.
+
+Please can you change the VE tests to have an
+    If there is an introductory welcome message
+      then dismiss it
+stanza?",1377805386,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,Should this be closed since 80709 is merged into master?,1377780987,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"(In reply to comment #3)
+> Why is VE using an iframe for this?  (and using iframes in general?)
+For the welcome message, we don't technically need to use an iframe. In that case we just use an iframe because all of our other dialogs use iframes.
+
+In general, we use iframes for dialogs and inspectors because we need to be able to have two selections at the same time. For instance, when you inspect a link, the link is selected, but you also have a cursor in the text field in the inspector. Because you can only have one selection in any given HTML document, we need the edit surface and the text field to be in different documents, and so we put the text field (along with most of the rest of the inspector) in an iframe.
+
+Dialogs use iframes for similar reasons: when the user interacts with UI elements in the dialog, that needs to not affect their selection in the edit surface. The welcome dialog doesn't have any elements that can steal the focus or selection so it's not an issue there, but since it uses the generic dialog code it's automatically in an iframe.",1377568185,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"When it shows up on test2 and/or beta I'll dismiss it in the test. 
+
+Why is VE using an iframe for this?  (and using iframes in general?)",1377554145,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,Also note that the beta welcome message will be rolled out to all wikis soon.,1377553601,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+VisualEditor tests fail due to introductory beta disclaimer popup,"
+I've been running these tests against test2wiki, which doesn't have that problem.  https://gerrit.wikimedia.org/r/#/c/80709/ should make it possible to run these against beta labs now that VE seems to be deployed there reliably",1377553370,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5gtyq6ebthpfjdmqjbyu,task_subcomment,NA
+"VisualEditor: add a wikilink to tags, the final inequality sign (>) is lost","User report following:
+<<If I start with a blank page, type in ""<br>"", select the entire text, press the link icon, select say ""France"" as the link, upon exiting the link dialog I am left with a link to [[France]] but the anchor is shortened to ""<b"".</nowiki>  I don't get any ""Wikitext markup detected"" warning. >>
+This is true for other tags as well (I tried with <b>).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377286560,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-6fqslp7awofcsqlxxg2u,task_description,declined
+"VisualEditor: add a wikilink to tags, the final inequality sign (>) is lost",This was fixed ages ago; sorry for not mentioning it here. (Please re-open if you can reproduce.),1397676516,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6fqslp7awofcsqlxxg2u,task_subcomment,NA
+"VisualEditor: add a wikilink to tags, the final inequality sign (>) is lost","(Sorry, that </nowiki> shouldn't be there, of course.)",1377286725,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-6fqslp7awofcsqlxxg2u,task_subcomment,NA
+VisualEditor is inserting greater than signs (>),"While I was fixing a simple grammatical error, VE threw in a > sign at the start of a template further down the page thus breaking the template.
+
+https://en.wikipedia.org/w/index.php?title=Tesla_Model_S&diff=next&oldid=569876875
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377279060,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-rnr44j25me5v5afzc5we,task_description,declined
+VisualEditor is inserting greater than signs (>),"I /believe/ that this was a Parsoid selser bug, long-since fixed; marking as WORKSFORME for now.",1394480185,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rnr44j25me5v5afzc5we,task_subcomment,NA
+VisualEditor: Unable to use save button using keyboard,"If I focus on the save button using [tab] from textarea, [enter] don’t save the page.
+
+Apparently the focus goes on the <div role=""button""> while the click event is listened on the span.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377270420,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_description,resolved
+VisualEditor: Unable to use save button using keyboard,"No, this bug as filed was indeed a duplicate of bug 51918. There's the subsequently-filed bug 62337 which tracks your comment.
+
+*** This bug has been marked as a duplicate of bug 51918 ***",1398102157,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_subcomment,NA
+VisualEditor: Unable to use save button using keyboard,"I'm reopening this rather than creating a new one, because it's not exactly a problem with the tab order.
+
+Here's how to reproduce this:  Open the Save dialog.  Type your edit summary.  Press the tab key seven times.  Everything tabs beautifully, in exactly the order I wish for.  Really:  Bug 51918 is resolved as far as I'm concerned.  The problem is not the tab ORDER.  
+
+The problem is that when I have successfully tabbed to the Save button, the Save button is BROKEN.  The Save button is selected.  There is a lovely blue box around it.  But it refuses to actually save the page when you press return.  It just sits there until, having pressed return twenty or thirty times, gone away in the hope that the server is just being slow, come back and hit the return key another dozen times or so, you finally conclude that it is not actually possible to save the page without taking your hands off the keyboard.  
+
+That's the problem:  ""Unable to use save button using keyboard"".  No amount of rearranging the deck chairs, I mean the tab order, is going to solve this problem.  The button itself is broken, not the tab order.
+
+The tick boxes for ""Minor edit"" and ""Watch this page"" can be tabbed to and toggled with the spacebar.  The links to the GFDL and other license stuff can be tabbed to and opened by pressing return.  But the ""Review your changes"" and ""Save"" buttons are broken.  There is no way to ""click"" those buttons without actually using a mouse/trackpad.",1398102028,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_subcomment,NA
+VisualEditor: Unable to use save button using keyboard,"Merging with bug 51918.
+
+*** This bug has been marked as a duplicate of bug 51918 ***",1378247189,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_subcomment,NA
+VisualEditor: Unable to use save button using keyboard,"**swalling** wrote:
+
+I also have this issue in Chrome 29 on OSX. Tabbing to Save page then hitting Enter does nada.",1378168841,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z4gyf5rhh3zawzwg3vor,task_subcomment,NA
+VisualEditor: Changing the first letter of wikilinked words is difficult,"Seems I had written about it in an unrelated bug, sorry. This happens on itwp: in order to do this
+http://it.wikipedia.org/w/index.php?title=DNasi_attivata_da_caspasi&diff=60101664&oldid=60089990
+I had to delete the word and link it back again. Our guidelines about style
+require pages in that section to appear with the capital letter, so we need to be able to fix that easily.
+
+It is also reported on en.wp, the user states <<When trying to correct a lower-case letter to a capital letter at the beginning of a link, I deleted the lower-case letter and found I couldn't type a capital letter and have it become part of the link, nor could I seem to extend the link over the capital. Eventually, I typed the capital after the lower-case letter and then deleted the lower-case letter. It might be good to have some way to extend a link over adjoining letters/words/text. Mount Flatten (talk) 05:31, 22 August 2013 (UTC) >>
+Thanks.
+
+ps. Might be related to https://bugzilla.wikimedia.org/show_bug.cgi?id=50745 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50745",1377174060,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-kecuajpgt5rzhwm6db3u,task_description,resolved
+VisualEditor: Changing the first letter of wikilinked words is difficult,"
+
+*** This bug has been marked as a duplicate of bug 50678 ***",1377445650,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-kecuajpgt5rzhwm6db3u,task_subcomment,NA
+VisualEditor: Changing the first letter of wikilinked words is difficult,*** Bug 53193 has been marked as a duplicate of this bug. ***,1377279290,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kecuajpgt5rzhwm6db3u,task_subcomment,NA
+VisualEditor: Changing the first letter of wikilinked words is difficult,pps. Also to https://bugzilla.wikimedia.org/show_bug.cgi?id=53193 .,1377186898,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-kecuajpgt5rzhwm6db3u,task_subcomment,NA
+VisualEditor: can't fix a broken template since this will result invisible,"See http://en.wikipedia.org/w/index.php?title=User:Christian75/sandbox2&oldid=569697466 .
+If you edit the page with VE you won't see the broken template at all.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377164100,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lpapd5tkeo4vhxavi7m5,task_description,declined
+VisualEditor: can't fix a broken template since this will result invisible,"Essentially the problem here is ""broken wikitext produces confusion""; there's not really anything that we can do except encourage people to use VisualEditor rather than wikitext where such errors are possible.",1397676723,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lpapd5tkeo4vhxavi7m5,task_subcomment,NA
+"VisualEditor: Need way to insert templates that set both key and value for a parameter into a template invocation, like {{subst:DATE}}","Currently there is no way to use {{subst:DATE}} in a template invocation in VisualEditor. If you try to paste it into the value of a date field, it won't work because you get
+
+|date = date=August 2013
+
+which won't parse.
+
+VisualEditor should actually set the date automatically, always, for such templates (e.g. refimprove).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52345",1377157620,PHID-USER-bug3zrlooz3bdmi4fyl7,False,PHID-TASK-in5fzrgdn5o7nk5vzdej,task_description,declined
+"VisualEditor: Need way to insert templates that set both key and value for a parameter into a template invocation, like {{subst:DATE}}","Yes(In reply to comment #0)
+> Currently there is no way to use {{subst:DATE}} in a template invocation in
+> VisualEditor. If you try to paste it into the value of a date field, it won't
+> work because you get
+> 
+> |date = date=August 2013
+> 
+> which won't parse.
+
+Yes. This is by design; templates that are designed around wikitext's structure won't work in general for editing. Note that ""{{subst:CURRENTDAY}} {{subst:CURRENTMONTHNAME}}"" works fine; auto-inserting this would solve the problem.
+
+> VisualEditor should actually set the date automatically, always, for such
+> templates (e.g. refimprove).
+
+I agree; that is bug 51428 (and its corresponding implementation in VisualEditor).",1377904404,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-in5fzrgdn5o7nk5vzdej,task_subcomment,NA
+VisualEditor: Links from a subpage are not rendered correctly in the editing surface,"If I add an unprefixed link to [[Main Page]] on
+
+https://www.mediawiki.org/wiki/Wikimedia_Engineering/WMF_Tech_Days_2013
+
+using VisualEditor, the link points to [[Wikimedia Engineering/Main Page]] when previewed in VisualEditor (by right-clicking and opening in a new tab). ""Review changes"" suggests that the correct link will be added when saving the page, so this issue may be limited to the editing surface.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377130800,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-wnlasenua7iwnzhgajgz,task_description,resolved
+VisualEditor: Links from a subpage are not rendered correctly in the editing surface,"
+
+*** This bug has been marked as a duplicate of bug 48915 ***",1377727533,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wnlasenua7iwnzhgajgz,task_subcomment,NA
+VisualEditor: nowiki when trying to edit an external link in references,"On de.WP, a user tried to replace an outdated link within an existing ref via VE and ran into a nowiki. 
+
+diff:
+
+http://de.wikipedia.org/w/index.php?title=Kin-dsa-dsa%21&diff=121506430&oldid=117367043
+
+report:
+
+http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121759646#nowiki_bei_unbeschriftetem_Link
+
+I could reproduce that; the previous is showing it prior to saving, too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377124920,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-6fktzxq6di35ahdf6gf4,task_description,resolved
+VisualEditor: nowiki when trying to edit an external link in references,"(In reply to Amir E. Aharoni from comment #2)
+> I cannot reproduce this with the current version of the article, which has
+> similar content.
+
+I can confirm that I could previously reproduce and this is now fixed; not quite sure where or when.
+
+> When trying to edit the old version of the article I get a strange result: I
+> don't see the external links in the reference editor at all.
+
+Yeah; that's very odd. Have filed bug 71652.",1412470303,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6fktzxq6di35ahdf6gf4,task_subcomment,NA
+VisualEditor: nowiki when trying to edit an external link in references,"I cannot reproduce this with the current version of the article, which has similar content.
+
+When trying to edit the old version of the article I get a strange result: I don't see the external links in the reference editor at all.",1412445538,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-6fktzxq6di35ahdf6gf4,task_subcomment,NA
+VisualEditor: nowiki when trying to edit an external link in references,"Confirmed
+
+Steps to reproduce:
+1. https://de.wikipedia.org/w/index.php?title=Kin-dsa-dsa!&oldid=117367043&veaction=edit
+2. open the ref dialog for the last ref in the first paragraph of section 'Video'
+3. open link dialog for the first external link
+4. replace http://kinocenter.rsuh.ru/Dan2.htm with http://wayback.archive.org/web/20080603185657/http://kinocenter.rsuh.ru/Dan2.htm
+
+Expected results:
+Only the URL changes
+
+Actual results:
+<nowiki>[1]</nowiki> is inserted
+
+Reproduced on a much smaller test case here:
+https://de.wikipedia.org/w/index.php?title=Benutzer:John_Vandenberg/test&diff=123052743&oldid=123052686",1380638685,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-6fktzxq6di35ahdf6gf4,task_subcomment,NA
+Cannot enter multiple authors in cite web template,"When I add a reference and add a template of type ""cite web"" in the reference, the template only allows me to enter a single author last name and a single author first name. To enter multiple authors I'm supposed to use the attributes ""last1, first1 through last9, first9 for up to nine authors"", but VisualEditor doesn't seem to offer the possibility of adding these attributes.
+
+There is an ""others"" field, but this is only supposed to be used for people who are neither authors nor editors, e.g. illustrators.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1377110520,PHID-USER-bug3zrlooz3bdmi4fyl7,False,PHID-TASK-oeqdjrsyoun6qoc3mib4,task_description,invalid
+Cannot enter multiple authors in cite web template,"This is a failing in the TemplateData that has been written for the template - it seems that the author of the template's hinting didn't bother to put in last1-9 or first1-9.
+
+However, despite the lack of hinting, you can enter these in VisualEditor (just manually type in 'first1' as a parameter, add it, set a value, repeat for 'last1', and so on for each additional author). It's very laborious, which is why this should be fixed in the template's TemplateData, but not an issue with VisualEditor.",1377114222,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oeqdjrsyoun6qoc3mib4,task_subcomment,NA
+VisualEditor: Removal of template when adding reference list,"Screencast
+
+When trying to add a new section and a reference list an existing template (defaultsort) gets removed, see screencast attachment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11699}",1377029340,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-dit32vs3thukzudalngg,task_description,resolved
+VisualEditor: Removal of template when adding reference list,Cannot reproduce. This must have been fixed at some point. I wonder if it was a Parsoid issue...,1416183797,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-dit32vs3thukzudalngg,task_subcomment,NA
+VisualEditor: Removal of template when adding reference list,Does this still happen?,1414811151,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-dit32vs3thukzudalngg,task_subcomment,NA
+"""edit lead section"" link incorrectly points to second section","**Author:** `sumanah`
+
+**Description:**
+On mediawiki.org, I have enabled the ""Add an [edit] link for the lead section of a page"" gadget and the ""Enable section editing via [edit] links"" Preference (in the Editing tab).
+
+If I go to a wiki page on mediawiki.org and click ""edit"" or ""edit source"" next to the title of an article (e.g., on https://www.mediawiki.org/wiki/Wikimedia_Labs ), then the VisualEditor link correctly thinks I want section 0, the lead section:
+
+https://www.mediawiki.org/w/index.php?title=Wikimedia_Labs&veaction=edit&section=0
+
+but the ""edit source"" link thinks I want section #1 and thus brings me to edit the ""Background"" section:
+
+https://www.mediawiki.org/w/index.php?title=Wikimedia_Labs&action=edit&section=1
+
+This may be a problem with the gadget rather than with VE, but it only started recently, so I think it might be a VE-related issue.  (I have looked at Bug 51030 - ""Edit link for lead section no longer works"" which sounds sort of separate.)  I shall also mention this bug in the talk page of the relevant gadget.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376623920,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bid73jyquzumwcuffblp,task_description,invalid
+"""edit lead section"" link incorrectly points to second section",Definitely a problem with the gadget.,1376668133,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-bid73jyquzumwcuffblp,task_subcomment,NA
+"VisualEditor: ""Error: Unknown error"" when creating page on test2wiki","**Author:** `sumanah`
+
+**Description:**
+close-up of error message and greyed button
+
+1. Try to use the VE to create a page at https://test2.wikipedia.org (while logged in, if that makes a difference).
+
+2. Click ""Save page"" button.
+
+The ""Save page"" button greys out and ""Error: Unknown error"" shows up to its left.  The user assumes that the page has not been saved.  But it has been created, e.g., https://test2.wikipedia.org/wiki/Kim_Stanley_Robinson .
+
+By the way, if the user reacts to the error by clicking Review changes and then getting back to Save, everything works fine.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11279}",1376614380,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aphzv5yajhoubslqbzir,task_description,resolved
+"VisualEditor: ""Error: Unknown error"" when creating page on test2wiki","I think this was due to a bug in the save dialog that we fixed last month; closing. If it re-occurs, please re-open this bug so we can fix this issue too.",1383015953,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aphzv5yajhoubslqbzir,task_subcomment,NA
+"VisualEditor: ""Error: Unknown error"" when creating page on test2wiki","**sumanah** wrote:
+
+Also, as you can see in https://test2.wikipedia.org/wiki/Special:Contributions/Sharihareswara_%28WMF%29 and (for instance) https://test2.wikipedia.org/w/index.php?title=Kim_Stanley_Robinson&oldid=57690 , those creation edits don't get the ""VisualEditor"" tag.",1376676868,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aphzv5yajhoubslqbzir,task_subcomment,NA
+"VisualEditor: Edit summary length counter ""hidden"" on it.wp","This does not affect Firefox, from what I saw - I used Chrome.
+I'd add a screenshot but it is really just as the summary says, 
+the number is there and it is working but you can not see it because the equivalent for ""Watch this page"", which is ""Aggiungi agli osservati speciali"", overlaps it (only the last word, of course).
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376489160,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-z73kr2qs67okpafmzjog,task_description,resolved
+"VisualEditor: Edit summary length counter ""hidden"" on it.wp",This was I think fixed some time ago. Sorry for the very slow triage.,1394501931,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-z73kr2qs67okpafmzjog,task_subcomment,NA
+End of transcluded page not/incorrectly detected,"Screenshot 1
+
+https://de.wikipedia.org/wiki/Knebel transcludes https://de.wikipedia.org/wiki/Konrad_Knebel
+
+Only 2 lines are transcluded but the VisualEditor does not detect the end of the transclusion, see screenshot 1.
+
+The other 3 lines are handled as content of this ""template"", see screeshot 2.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Knebel
+
+**Attached**: {F11960}",1376417640,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-es2flh3nsdngj3dxtuxi,task_description,resolved
+End of transcluded page not/incorrectly detected,"
+
+*** This bug has been marked as a duplicate of bug 51119 ***",1376639350,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-es2flh3nsdngj3dxtuxi,task_subcomment,NA
+End of transcluded page not/incorrectly detected,"Created attachment 13094
+Screenshot 2
+
+**Attached**: {F11961}",1376417681,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-es2flh3nsdngj3dxtuxi,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"Input in VisualEditor and Output after saving (+ Parsoid Server output)
+
+MediaWiki:
+1.22alpha (ffa9b0a) 19:02, 11. Aug. 2013
+
+VisualEditor (Version 0.1.0)(0e76b1b)20:01, 11. Aug. 2013
+
+ParsoidServer:
+commit 808cc39c81df83daaec458c81edbd126fd1dd19a
+Author: Subramanya Sastry <ssastry@wikimedia.org>
+Date:   Mon Aug 12 16:15:24 2013 -0500
+
+
+Adding more than one empty line isn't possible in the VisualEditor extension. Is this a desired behaviour?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11917}",1376401560,PHID-USER-26asvhtv4jalaeeuigbm,False,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_description,declined
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"Multiple sequential blank paragraphs are collapsed to one by design (we provide an HTML editor, not a desktop publishing system).",1397676105,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"Still happening with the following VE-commit
+
+commit c98a964d5f8495f0d16af9229abbeb0449042d1e
+Merge: 3d01a5b e7aed52
+Author: jenkins-bot <jenkins-bot@gerrit.wikimedia.org>
+Date:   Wed Sep 18 01:11:46 2013 +0000
+Merge ""Fix check for preformatted when stripping whitespace""
+
+Browser: Chrome 29.0.1547.66 m W764bit",1379658982,PHID-USER-26asvhtv4jalaeeuigbm,False,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,Confirmed this is still happening on en.wp (wmf 15) and mediawiki.org (wmf 16),1378425096,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"I've tested it with the VisualEditor on the official mediawiki-page. Here it works: Im able to enter more than one line break. Can you guys reproduce my problem with my version?
+
+I updated my VE to the latest master-branch-commit: 
+
+commit 2c4e9d832374f095d3fa9d43b845ac7c7083aeb4
+Merge: c84c47a 7673a39
+Author: jenkins-bot <jenkins-bot@gerrit.wikimedia.org>
+Date:   Wed Aug 14 22:00:12 2013 +0000
+Merge ""Support previews and concurrent updates in ce.GeneratedContentNode""
+
+Browser-Information: Chrome on Windows 7 64bit 28.0.1500.95 
+
+>>> Still the same problem.",1376631319,PHID-USER-26asvhtv4jalaeeuigbm,False,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,"Sounds like VE, as we'll produce empty lines fr p/br content just fine. Moving to VE.",1376612281,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.,Is this a question about the VE interface (in which case you should either file this against the VE component OR show up on IRC and ask on #mediawiki-visualeditor) or the wikitext that is generated?,1376407363,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ia2t3u7dnvzwa74mm3vr,task_subcomment,NA
+VisualEditor: support article layouts,"Pages started with a copy/paste of layouts (i.e. http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Football/Players ) are very, very common. VE does not seem to support this right now, making VE a very secondary choice to create articles. Probably related to https://bugzilla.wikimedia.org/show_bug.cgi?id=33105 , please feel free to mark this as a dupe if needed. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376387040,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-svug2yxishcvki3vxn4q,task_description,resolved
+VisualEditor: support article layouts,"I'm going to merge this with bug 52091, which would fix the issue (you could copy-and-paste from the read HTML without needing to do anything special).
+
+*** This bug has been marked as a duplicate of bug 52091 ***",1383280378,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-svug2yxishcvki3vxn4q,task_subcomment,NA
+VisualEditor: reusing existing reference generates duplicate references,"All the references adding in this edit: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=568232613&oldid=568231803 were added using the ""use existing reference"" option. 
+
+It seems that only when I added the same reference on the same line (trying to reproduce a different bug) did it reuse the existing ref rather than creating a duplicate one.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376326380,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xsaz6kvx37q5kaxfiw5l,task_description,invalid
+VisualEditor: reusing existing reference generates duplicate references,"I'm not sure I understand this bug report – surely it's obvious that if you re-use a reference, we need to modify the original reference to have a name (if it doesn't already have one) so we can re-use it? That's how MediaWiki's referencing system works. Please re-open if I've missed something.",1401473395,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xsaz6kvx37q5kaxfiw5l,task_subcomment,NA
+VisualEditor: reusing existing reference generates duplicate references,user Biosthmors at en.wp reports that this bug is frustrating his efforts to recruit a campus ambassador because they are getting so frustrated at trying to get VE to do what it claims it will do.,1378727138,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xsaz6kvx37q5kaxfiw5l,task_subcomment,NA
+"VisualEditor: ""existing references"" in the references dialog not identifying references","See https://pl.wikipedia.org/w/index.php?title=Wikipedysta:G%C5%BCdacz/brudnopis&oldid=37221362&veaction=edit for an example; only one citation appears as insertable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376287140,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-wwlsmm4fnvqjdssb7g4d,task_description,resolved
+"VisualEditor: ""existing references"" in the references dialog not identifying references","
+
+*** This bug has been marked as a duplicate of bug 50474 ***",1402332002,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wwlsmm4fnvqjdssb7g4d,task_subcomment,NA
+VisualEditor: Cannot backspace in Edit Summary window after reviewing changes,"**Author:** `hagurganus`
+
+**Description:**
+When typing an edit summary in the Edit Summary window, I was unable to backspace. It seemed to let me highlight and _replace_ text, but even then, I could not highlight and hit the backspace key to _remove_ the text, I had to highlight and hit spacebar to simply enter a space, etc.
+
+It could be that this is intentional, but I highly doubt this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1376249940,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-vis7xnmoa7ngc2i4ds2i,task_description,resolved
+VisualEditor: Cannot backspace in Edit Summary window after reviewing changes,"I believe that this is the same as bug 50722, yes.
+
+*** This bug has been marked as a duplicate of bug 50722 ***",1377833584,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vis7xnmoa7ngc2i4ds2i,task_subcomment,NA
+VisualEditor: Cannot backspace in Edit Summary window after reviewing changes,I think this is likely to be bug 50722?,1377449242,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-vis7xnmoa7ngc2i4ds2i,task_subcomment,NA
+VisualEditor: Cannot backspace in Edit Summary window after reviewing changes,"I've been encountering this for a while and just worked out how to reproduce this:
+
+1. Edit a page in VE
+2. Enter an edit summary (doesn't matter what) but don't save
+3. Review your changes.
+4. Return to editing the page without saving (e.g. using the ^ button). It doesn't matter if you make any more changes or not.
+5. Click save page again
+
+Expected behaviour
+* The edit summary input box works like a normal text entry field
+
+Actual behaviour
+* The delete, backspace and cursor keys do not work.
+* Text can only be selected using the mouse
+* Selected text can be removed by overwriting, by ""delete"" or ""cut"" from the RMB menu, or by using the ctrl+x shortcut to cut.
+
+This bug was originally reported on Safari/MacOS X, I encountered it using Firefox 23/Linux",1376475552,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-vis7xnmoa7ngc2i4ds2i,task_subcomment,NA
+"VisualEditor: After ""wikimarkup"" popup, save button temporarily does not work","An editor reports that he lost his work when an extensive edit unexpectedly triggered the ""wikimarkup"" popup and - after he dismissed it - the ""save"" button became unresponsive. The button appeared as normal but did not react to being selected.
+
+He was using Windows 7 and Firefox.
+
+I reproduced this using Windows 7 and Chrome (didn't matter if I removed the wikimarkup or not), and on further investigation found that the ""save"" button will respond as expected after a delay.
+
+The issue, of course, is that if this editor aborted his edit because he thought the system would not save, others are likely to think that as well.
+
+Not sure if anything can be done to make the save button immediately responsive or to figure out why it wouldn't be or to make it apparent to editors that the option to ""save"" will return.
+
+The conversation can be found here:
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=567809017#Wikitext_error_message
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376050200,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-avc3fsxulmn56uqgbsy6,task_description,resolved
+"VisualEditor: After ""wikimarkup"" popup, save button temporarily does not work","Is this still occurring? I think we've fixed it, so am marking as FIXED, but would prefer to get confirmation.",1383015225,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-avc3fsxulmn56uqgbsy6,task_subcomment,NA
+"VisualEditor: After ""wikimarkup"" popup, save button temporarily does not work","en.wp user GermanJoe reports a probably related problem:
+
+After dismissing the wikitext warning the ""upper third and right corner"" of the save and cancel buttons are not clickable."" and that ""Those partial locks are only released, after you clear your browser cache (stopping VE is not enough) ""
+
+GermanJoe was using Windows XP, FF 22, vector.js and a 1280 x 1024 resolution for test. He did not experience the problem in 800x600 resolution.
+
+Elitre was able to reproduce this and added that ""this behavior changes if you zoom in or out (that is, if the buttons get bigger or smaller)""
+
+I reproduce this using Monobook in Firefox 23 on Linux, but zooming the page did not result in changed behaviour for me.",1376141839,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-avc3fsxulmn56uqgbsy6,task_subcomment,NA
+VisualEditor: don't display all tools by default to new editors,"en.wp user Ruud Koot suggests that certain tools, such as underline and font colour (bug 52645) that are not normally wanted/needed in articles shouldn't be available to new editors.
+
+Personally I think everything should be available (this avoids the need for new classes of editor permissions) but just not shown by default. What is shown/not shown by default needs to be configurable on-wiki per wiki (and possibly per namespace).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49617",1375957260,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-vemzxauwwwilvulip65t,task_description,invalid
+VisualEditor: don't display all tools by default to new editors,This has been somewhat overtaken by changes to the toolbar; closing as INVALID.,1383015740,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vemzxauwwwilvulip65t,task_subcomment,NA
+Parsoid or VisualEditor:  __NOTOC__ sometimes replaced by copy of categories,"en.wp user Ruud Koot reports that occasionally he gets "" weird, random and unexplainable corruptions of wikitext on save"" when using the VisualEditor.
+
+The only example he gives is ""e.g., a __NOTOC__ being replaced with a copy of the categories""
+
+Bug 48231 might have something to do with this, but I confess to not understanding all the technical language there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375955220,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ssrgubmui6ycz46f7lkd,task_description,declined
+Parsoid or VisualEditor:  __NOTOC__ sometimes replaced by copy of categories,"Never mind.  I found it here.  https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=prev&oldid=567395325 .. No diffs there.  
+
+Looks like his experiments here are at least 3 weeks old.  https://en.wikipedia.org/w/index.php?title=User:Ruud_Koot/Computer_science/Lambda_calculus&action=history
+
+Lot of things have been fixed in the last couple weeks including instances of wikitext getting duplicated.  But 48231 is not related to this.  I am going to close this ticket for now.  We can open new bugs against specific bad diffs when we encounter them.
+
+Thanks for your diligent work in reporting bugs!",1376086189,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ssrgubmui6ycz46f7lkd,task_subcomment,NA
+Parsoid or VisualEditor:  __NOTOC__ sometimes replaced by copy of categories,Can you point me to his bug report (was this on the feedback page)?  It would be easier to debug with a diff if you have easy access to one.,1376085510,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ssrgubmui6ycz46f7lkd,task_subcomment,NA
+VisualEditor: saving fails silently for some large edits,"en.wp user Ruud Koot reports:
+
+""Occasionally, after a medium-sized editing session, the visual editor will silently refuse to save my edits. When clicking the save button the progress bar appears, disappears, and you stay in editing mode, with no new revision appended to the history. Trying again sometimes resolves the problem, sometimes it requires edit operations to be done in a different order or be broken up into smaller increments, saving in-between."" 
+
+He also asks, ""Do you keep any statistics on how often an editor presses the save button versus how many times this actually results in a new revision being saved?""
+
+Bug 51423 might be related.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51243",1375954440,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4hux64flsouxqgjibleh,task_description,declined
+VisualEditor: saving fails silently for some large edits,No subsequent reports or steps to fix; marking as WORKSFORME.,1406598295,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4hux64flsouxqgjibleh,task_subcomment,NA
+VisualEditor: saving fails silently for some large edits,Sorry that possibly related issue is bug 51243,1375954749,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4hux64flsouxqgjibleh,task_subcomment,NA
+VisualEditor: Bulleted bullets and bulleted headers produced; can't save,"en.wp user Ruud Koot reports:
+""When performing structural editing tasks (i.e. things which are slight more complex than changing typos or adding a sentence in the middle of an existing paragraph) it is very easy to get the editor into some weird state where it is impossible to get out of other than aborting the edit session and trying again more carefully. This includes things like introducing ""bulleted headers"" and ""bulleted bullets"", which cannot possibly be represented as wikitext.""
+
+He notes that ""Copying and pasting around text and editing pages with tables [is a] fairly reliable method"" to reproduce it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375953840,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xyg7preywhwlpczuaps6,task_description,declined
+VisualEditor: Bulleted bullets and bulleted headers produced; can't save,">>! In T54639#1091705, @Thryduulf wrote:
+> I don't see a need to keep this open any longer, if something similar is reported again a more specific bug can be opened. 
+
+Thank you for the quick reply! Sounds reasonible, closing as declined (as we cannot reproduce anymore).",1425633241,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xyg7preywhwlpczuaps6,task_subcomment,NA
+VisualEditor: Bulleted bullets and bulleted headers produced; can't save,"I don't recall this error, and I too can't reproduce anything now using Firefox 30.  Given that it's been ~18 months since the report, it's likely this has been fixed by some other update in the meanwhile.
+
+I don't see a need to keep this open any longer, if something similar is reported again a more specific bug can be opened. ",1425549798,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xyg7preywhwlpczuaps6,task_subcomment,NA
+VisualEditor: Bulleted bullets and bulleted headers produced; can't save,"Hi @Thryduulf! Sorry that nobody has taken a look at this report yet and given feedback.
+
+I tried copying bullets around on https://en.wikipedia.org/wiki/User:AKlapper_%28WMF%29/Sandbox?veaction=edit but could not reproduce anything weird in Firefox 36 on Fedora 21.
+
+Are there any specific steps to reproduce these problems, or edits / diffs that could be linked to? Any specific browser involved?
+
+Setting task status to STALLED for the time being; please reset task status once there are clearer steps to reproduce. Thanks!",1425487218,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xyg7preywhwlpczuaps6,task_subcomment,NA
+VisualEditor: Difficult to get a blank line when the page starts with a bulleted list,"If a page starts with a bulleted list, there's no way to put the cursor ""in front of"" the list styling.  If you want to add a non-list paragraph, you have to make a new, blank first bullet item and then remove the list formatting from the paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52032",1375918560,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gwksqe4mofbzkamj67mf,task_description,invalid
+VisualEditor: Difficult to get a blank line when the page starts with a bulleted list,"Seems to be resolved - checked on the page https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575308394. 
+The text is easily added on a new line before the first bullet.",1420846571,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-gwksqe4mofbzkamj67mf,task_subcomment,NA
+VisualEditor: Difficult to get a blank line when the page starts with a bulleted list,"Sorry, that last line should reference bug 52032.",1380645177,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-gwksqe4mofbzkamj67mf,task_subcomment,NA
+VisualEditor: Difficult to get a blank line when the page starts with a bulleted list,"To reproduce:
+1: Load a page in VE that starts with a bulleted list e.g. https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575308394
+2: Try to add text before the first bullet.
+
+It is possible that fix for bug 52302 might also resolve this issue.",1380645144,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-gwksqe4mofbzkamj67mf,task_subcomment,NA
+VisualEditor: Edit notices don't scroll,"Today's Featured Article edit notice displayed in Firefox 22/Linux/Monobook on a 481px high window
+
+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).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51755
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52667
+
+**Attached**: {F11480}",1375860960,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-i6f5p5xjfmxdo6ubzpmu,task_description,resolved
+VisualEditor: Edit notices don't scroll,"
+
+*** This bug has been marked as a duplicate of bug 50885 ***",1377446690,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-i6f5p5xjfmxdo6ubzpmu,task_subcomment,NA
+VisualEditor: Edit notices don't scroll,"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.",1375951466,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-i6f5p5xjfmxdo6ubzpmu,task_subcomment,NA
+"Wikimedia editors aren't automatically enrolled in Bugzilla, reducing VE bug reporting","**Author:** `gnu`
+
+**Description:**
+The unusually buggy deployment of the VisualEditor has caused large numbers of English Wikipedia editors to have bugs to report.  But the process of reporting bugs is a cumbersome many-step process -- starting with a requirement to ""log in"" using a credential that most editors do not have.
+
+The rest of the Wikipedia universe uses a universal login system in which you log in with the same username and password to everything, and it all works together.  Somehow Bugzilla didn't get integrated with that.
+
+So instead anyone with a bug report for Visual Editor -- assuming they can even find Bugzilla, perhaps from a comment in an RFC about disabling the Visual Editor, as I found it -- then has to get through the ""New User"" process, which includes providing an email address, checking mail at that address, and accessing a URL which then demands that a new password be created and remembered.
+This step should be avoided for logged-in Wikipedia users.
+
+I'm sure that many, many Visual Editor bugs are noticed by editors, but are never reported due to the pain of the reporting process.  This shortage of bug reports may serve the political purposes of the WMF in attempting to ram the new editor down the throats of the community, but it is not a good management practice, nor will it result in eliminating the bugs that make the Visual Editor too troublesome for naive use at this point.
+
+(The remaining process of bug reporting is also cumbersome and complex -- but 
+in this bug report I have no suggestions on how to fix that.)
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1375844100,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ud6rksuxulevqjsfqs6h,task_description,resolved
+"Wikimedia editors aren't automatically enrolled in Bugzilla, reducing VE bug reporting","(In reply to comment #0)
+> The rest of the Wikipedia universe uses a universal login system in which you
+> log in with the same username and password to everything, and it all works
+> together.  Somehow Bugzilla didn't get integrated with that.
+
+That's bug 14487. If you don't want to create a Bugzilla account you can report issues at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback .
+
+*** This bug has been marked as a duplicate of bug 14487 ***",1375847060,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ud6rksuxulevqjsfqs6h,task_subcomment,NA
+"VisualEditor: Label for beta notice/menu should use mixed case not all caps (""Beta"" not ""BETA"")","From en.wp user Cryptic C62:
+The beta button on the toolbar ""should not be labelled ""Beta"", not ""BETA"". The latter looks like it might be a mysterious acronym. ""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375820700,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-rvrst7lvd6twcpeipdkt,task_description,invalid
+"VisualEditor: Label for beta notice/menu should use mixed case not all caps (""Beta"" not ""BETA"")","This label no longer exists, but instead is just the help ""(?)"" icon.",1393528505,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rvrst7lvd6twcpeipdkt,task_subcomment,NA
+"VisualEditor: Label for beta notice/menu should use mixed case not all caps (""Beta"" not ""BETA"")","(In reply to comment #1)
+> Can I work on this bug? I know it has been assigned to someone but looks like
+> nothing has happened here for sometime.
+
+It looks like that's the default assignee for bugs in this component. In general it should be fine to do these.",1390957191,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-rvrst7lvd6twcpeipdkt,task_subcomment,NA
+"VisualEditor: Label for beta notice/menu should use mixed case not all caps (""Beta"" not ""BETA"")","**aravikn** wrote:
+
+Can I work on this bug? I know it has been assigned to someone but looks like nothing has happened here for sometime.",1390221344,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rvrst7lvd6twcpeipdkt,task_subcomment,NA
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"Where articles use the {{ref}} and  {{note}} pair of templates to generate footnotes, e.g. [[List of highest points of Canadian provinces and territories]], it is impossible to edit the contents of the notes in VisualEditor.
+
+The {{ref}} template is editable in the transclusion editor, and works as expected.
+
+The {{note}}-generated notes are apparently one block. No transclusion icon or indication of uneditablility (green stripes) appears on mouseover or when the block is clicked. 
+
+If a link in the notes is clicked it functions as a link would in read mode- ie. the link is followed and you leave the page. VE gives no warning about unsaved edits (although Firefox does).
+
+If the backlink to the location of the {{ref}} template is clicked it functions as above - i.e. it loads the page in read mode at the position of the note, exactly as if you had followed a link to that anchor from any other page on the internet.
+
+It is possible to select the block when selecting content before and after the block, although no indication is given that it has been selected. Once selected it is possible to apply bold/italic formatting to the block and other selected text using the B/I buttons, but it is not then possible to remove it using these buttons while the note block is selected. It is possible to remove bold/italic using the clear format button. The clear format button does not remove any links in the notes block, but does remove links from any other text selected at the same time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1375800120,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_description,declined
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"Cite.php is designed a certain (bad) way. It has issues, and we will replace it at some point, but the way to fix its issues is not to make horrible hacks in wikitext using loopholes over-looked when the code was written to try to re-design in.
+
+This is one of those cases, and is not sanely supportable in VisualEditor, so I'm going to mark this as WONTFIX.",1393541169,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_subcomment,NA
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"cklim: Not sure what your random HTML and image posted here has to do ""VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system"".
+Please file a separate ticket as this seems unrelated to this bug report.",1393068100,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_subcomment,NA
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"**cklim074** wrote:
+
+<head><meta content=""width=device-width; height=device-height;"" name=""viewport""><link href=""resource://gre/res/ImageDocument.css"" rel=""stylesheet""><link href=""resource://gre/res/TopLevelImageDocument.css"" rel=""stylesheet""><link href=""chrome://global/skin/media/TopLevelImageDocument.css"" rel=""stylesheet""><title>attachment.cgi (PNG Image, 1247&nbsp;×&nbsp;669 pixels)</title></head><body><img class=""decoded overflowing"" alt=""http://bug-attachment.wikimedia.org/attachment.cgi?id=14163"" src=""http://bug-attachment.wikimedia.org/attachment.cgi?id=14163""></body>",1393041491,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_subcomment,NA
+VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.,"**cklim074** wrote:
+
+<head><meta content=""width=device-width; height=device-height;"" name=""viewport""><link href=""resource://gre/res/ImageDocument.css"" rel=""stylesheet""><link href=""resource://gre/res/TopLevelImageDocument.
+
+<head><meta content=""width=device-width; height=device-height;"" name=""viewport""><link href=""resource://gre/res/ImageDocument.css"" rel=""stylesheet""><link href=""resource://gre/res/TopLevelImageDocument.css"" rel=""stylesheet""><link href=""chrome://global/skin/media/TopLevelImageDocument.css"" rel=""stylesheet""><title>attachment.cgi (PNG Image, 1247&nbsp;×&nbsp;669 pixels)</title></head><body><img class=""decoded overflowing"" alt=""http://bug-attachment.wikimedia.org/attachment.cgi?id=14163"" src=""http://bug-attachment.wikimedia.org/attachment.cgi?id=14163""></body>
+
+**Attached**: {F11426}",1393041446,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sjjvxqyu5lvsgdnholi7,task_subcomment,NA
+VisualEditor: Don't wait indefinitely for gadget servers that are not responding,"When a user has installed a gadget that relies on data from an external server, VisualEditor appears to wait indefinitely for that server to respond. Normally this is OK, but when that server is down VE will apparently wait forever (or at least longer than the 5 minutes I was prepared to wait) for a response.
+
+The source editor appears to give up after a wile (2 minutes?), and loads as if the gadget was not called. VE should exhibit this behaviour too.
+
+Tested with the HAPPI gadget ([[User:EpochFail/HAPPI]]). As of 21:52 UTC 05 August 2013 that gadget depends on a server at wikipedia.grouplens.org that is not responding
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375739580,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-brb5wektguex52kczga7,task_description,invalid
+VisualEditor: Don't wait indefinitely for gadget servers that are not responding,"Surely this is the responsibility of the gadget's author?
+
+Also, not sure if the wikitext editor executes poorly-responding gadgets, or it's just apparent happenstance. Either way, 120 seconds is about an order of magnitude too high.
+
+Sorry for very slow triage.",1390419026,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-brb5wektguex52kczga7,task_subcomment,NA
+VisualEditor or Parsoid: inserted HTML code instead of Wikilink,"At line 42 of https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&diff=567254040&oldid=566841354 attempting replace what appeared to be an empty image caption with ""The [[Sun]]"" (using ctrl+k for the link, no wikicode) resulted in the insertion instead of:
+The <a style=""white-space:nowrap"" data-mw=""{&quot;target&quot;:{&quot;wt&quot;:&quot;val&quot;,&quot;href&quot;:&quot;../Template:Val&quot;},&quot;params&quot;:{&quot;1&quot;:{&quot;wt&quot;:&quot;4.6&quot;},&quot;ul&quot;:{&quot;wt&quot;:&quot;byr&quot;}},&quot;i&quot;:0}"" rel=""mw:WikiLink"" href=""Sun"">Sun</a>
+
+The images were left over from testing for Bug 52341 and so that bug may be related.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375709160,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4xuz3vb5yze6xii6usyj,task_description,declined
+VisualEditor or Parsoid: inserted HTML code instead of Wikilink,I'm pretty sure this was a horrible artefact of a nasty bug we fixed back in September; provisionally marking as WORKSFORME. Sorry for the ludicrously-slow triage.,1401418799,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4xuz3vb5yze6xii6usyj,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"visual editor easily doubles mouse clicks and key presses. this can be seen, amongst others, on section editing, saving, adding a reference. to avoid bug reports in the line of ""please remove one mouse click while creating a reference"" create a (visual) design guideline mandatory to follow for all developers to minimize mouse clicks and key presses, and maximise screen estate available for editing/viewing the article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375607280,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-kvdgcfvnalphobirayqv,task_description,declined
+VisualEditor: Create a design guideline to minimize clicks and key presses,"Again: This won't be handled in Bugzilla, however pointing to a better place where to discuss would be very good.  Playing the ""I know it's the wrong place but still I want to discuss it here"" card isn't much better either though. :)
+
+Please don't reopen as a sign of disagreement. Thanks.",1376561195,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"james, let me reopen this one please. there is a big difference between ""it is our intention"" (whoever ""our"" is) and a crystal clear guideline having as primary target:
+* minimize clicks and key presses
+* response time <3 sec
+this would make it so much easier for new developers as well. and so much easier for testers to point out that something is against the goal. 
+
+as i tried to point out above with examples, people were and still are allowed to increase key presses and mouse-clicks considerable compared to the existing solution. i tried to look for design documents or mail references on some tech list to find a justification for this, but could not find one. 
+
+you as a software developer surely know that nothing is more expensive than fixing a design bug. and nothing is more expensive than finding a bug late. just to take an arbitrary url to support this: http://blog.bootstraptoday.com/2011/12/25/early-detection-of-bugs-can-save-up-to-22-billion-yearly/ 
+
+so, please do not play the ""a good thing but not the right place"" card. which then ends up nowhere. you can close the ticket if you either create this guideline, or successfully have a (public verifyable) decision in whatever place you consider right for a decision like this.",1376539525,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"Of course, this is already our intention. There is nothing to ""create"".
+
+Bugzilla is not really the right place to suggest user experience improvements like this - though walk-through data like you've given is hugely valuable, and if you have more I would love for you to share it.",1376521216,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"for bug48429, section editing, i tried VE at https://en.wikipedia.org/wiki/Jos%C3%A9_Mourinho. to repeat the clicks and key presses here:
+* 1 click and 15 secs to edit
+* 1 click to make go a away a note (see attachment)
+* 1 click to edit summary
+* 1 click and 20 secs to review changes
+* 1 click to return to save form
+* 1 click and 40 secs to save
+* 5* pg down to go to the section just edited
+
+while text editor sections can be edited with:
+* 1 click and 2 secs to open
+* 1 click and 2 secs to preview
+* 1 pg-down to find the save button (could be avoided by re-placing the button)
+* 1 click and 10 secs to save
+
+old is ideally 3 clicks, new is 6 clicks + 5 key presses.
+
+but, there are other cases as well. to add a category with hotcat is one click and a key press to confirm. It auto-corrects even the spelling to upper case. VE takes 8 clicks, a refresh, and scrolling down, if i counted correctly.",1375774987,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+VisualEditor: Create a design guideline to minimize clicks and key presses,"Which exact problem do you see with the current situation, that made you file this bug report?",1375620096,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kvdgcfvnalphobirayqv,task_subcomment,NA
+De.WP experiences wired edit labels on conversation pages,"Currently, De.WP talk, user talk, Wikipedia, Wikipedia talk..pages show for the last section not [Edit source] as En/Es/xy.WP do but [Add section / Edit source code / Add section] (Abschnitt hinzufügen Quelltext bearbeiten Abschnitt hinzfügen). It neither breaks anything technically as far as I can tell right now nor does it mix in VE interface but, where ever it might come from, it should be fixed asap
+
+http://de.wikipedia.org/w/index.php?title=Diskussion:Immanuel_Kant&oldid=120880638
+
+http://de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:JEissfeldt_(WMF)&oldid=120853192#VisualEditor_.2A_Projektseiten
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1375491060,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-33n5y7ewqlbefwxwacox,task_description,invalid
+De.WP experiences wired edit labels on conversation pages,"This is an issue with a script at [[de:MediaWiki:Common.js]].
+
+In the section ""erzeuge einen ""Neuen Abschnitt""-Link an der letzten Überschrift"", replace ""$( 'span.mw-editsection:last a' )"" with ""$( 'span.mw-editsection:last a:last' )"". That should be enough to fix it.",1375492148,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-33n5y7ewqlbefwxwacox,task_subcomment,NA
+Blacklist category for excluding pages from VisualEditor,"It would be helpful to be able to selectively disable VisualEditor (we should to indicate to a user who'd otherwise see VisualEditor that it is disabled, to reduce confusion). This would enable users to shield pages where VisualEditor/Parsoid cause roundtrip issues.
+
+A hidden blacklist category could be included in a page or template to achieve the desired effect, and could be used by developers to prioritize roundtripping issues.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375487760,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-qpvwyqg5nibzkozzdov5,task_description,resolved
+Blacklist category for excluding pages from VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 52141 ***",1375488138,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-qpvwyqg5nibzkozzdov5,task_subcomment,NA
+VisualEditor: Image thumbnails that don't specify size should render at the wiki-default size,"If one opens the VE editing interface, the user experience in relation to image formats varies significantly. The report: 
+
+http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121153156#Bilder_werden_im_VE_kleiner_angezeigt
+
+has several examples with different browsers like 
+
+FF 22 / Win 7: edgewise images smaller; rest bigger.
+Chrome 28 / Win 7: all significantly smaller.
+
+See also screenshots in perma link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375487460,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-7bui5nacoyzpq7m5e4vx,task_description,resolved
+VisualEditor: Image thumbnails that don't specify size should render at the wiki-default size,"Merging with bug 47804.
+
+*** This bug has been marked as a duplicate of bug 47804 ***",1380666480,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7bui5nacoyzpq7m5e4vx,task_subcomment,NA
+VisualEditor: Image thumbnails that don't specify size should render at the wiki-default size,"When viewing a page, images that are specified as [[File:Foo.jpg|thumb|Caption]] render as 220px wide (en.wp)/180px wide (de.wp), regardless of dimensions or aspect ratio.
+
+In visual editor, images specified the same way render so as not to exceed 190px wide by 212px high. 
+
+This means that images can appear at very different sizes in the VE editing surface to how they appear on the rendered page. This is especially true for very tall images.
+
+Example to better illustrate this, compare the two views of this page
+View mode: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575350620 
+VE edit mode: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=575350620&veaction=edit",1380666087,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-7bui5nacoyzpq7m5e4vx,task_subcomment,NA
+VisualEditor: uneditable table lines displayed wrong,"The displayed table (Firefox 22/Ubuntu)
+
+See [[fr:Special:redirect/revision/95505705#Pr.C3.A9sidents_de_l.27universit.C3.A9]]
+
+The 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 <tr> is wrapped in a <span>. Not really WYSIWYG…
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11257}",1375486440,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-ocna2wajo3o5voxuppid,task_description,resolved
+VisualEditor: uneditable table lines displayed wrong,"Yes, merging with bug 50607.
+
+*** This bug has been marked as a duplicate of bug 50607 ***",1385374740,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ocna2wajo3o5voxuppid,task_subcomment,NA
+VisualEditor: uneditable table lines displayed wrong,I think this might be a duplicate of bug 50607,1378374678,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ocna2wajo3o5voxuppid,task_subcomment,NA
+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 <ref></ref> 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",1375473900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tvsxq36upc6ipnvhxpyk,task_description,resolved
+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.",1377862353,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-tvsxq36upc6ipnvhxpyk,task_subcomment,NA
+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.",1377820107,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tvsxq36upc6ipnvhxpyk,task_subcomment,NA
+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 ***",1377819444,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tvsxq36upc6ipnvhxpyk,task_subcomment,NA
+"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",1375462920,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-wedvkdl2s27csm5sxz7t,task_description,resolved
+"VisualEditor: if the title page starts with a dot, VE won't load","
+
+*** This bug has been marked as a duplicate of bug 51308 ***",1375464734,PHID-USER-zjzhrhmn36icnzbckqy4,True,PHID-TASK-wedvkdl2s27csm5sxz7t,task_subcomment,NA
+"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).",1375463353,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-wedvkdl2s27csm5sxz7t,task_subcomment,NA
+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}",1375403700,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-klrivpj5pu4qmrhtcgbi,task_description,resolved
+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 ***",1375991502,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-klrivpj5pu4qmrhtcgbi,task_subcomment,NA
+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 <td>.
+
+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",1375401360,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-dpkxtqdack6wacscxvhg,task_description,resolved
+VisualEditor: {{clr}} prevents user from editing content,"
+
+*** This bug has been marked as a duplicate of bug 50551 ***",1395360523,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dpkxtqdack6wacscxvhg,task_subcomment,NA
+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.",1378423467,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dpkxtqdack6wacscxvhg,task_subcomment,NA
+"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",1375391460,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gbm6kyiyozz73ztd6xzq,task_description,resolved
+"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 ***",1375391536,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gbm6kyiyozz73ztd6xzq,task_subcomment,NA
+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:
+
+> <selected>
+> 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
+> </selected>
+> \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 <selected>NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar.
+> h2.References
+> references.
+> \n
+> \n
+> h2.External</selected> 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 <selected>NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar.</selected>
+> h2.References
+> references.
+> \n
+> \n
+> h2.External links
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375381560,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-idjdigelfjcuvhcx24zy,task_description,resolved
+VisualEditor: Undoing a larger cut restores selection incorrectly,This was fixed in the selection re-writes.,1385398843,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-idjdigelfjcuvhcx24zy,task_subcomment,NA
+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}",1375345320,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_description,duplicate
+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 ***",1386112687,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+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.",1379849577,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+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!",1375486433,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+Stray bullet points around template and strange editing around them,Reproduced in Chrome 28 and Opera 12.16.,1375394665,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+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]] <span style=""font-size:.95em;font-weight:bold;color:#555;"">(engelska)</span>
+*",1375345880,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+Stray bullet points around template and strange editing around them,This is probably a ContentEditable problem.,1375345435,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-xylt7ym6cdzsnco3r3ty,task_subcomment,NA
+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",1375319220,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-vs6adtg7gilhg5r2g74x,task_description,resolved
+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 ***",1375319436,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vs6adtg7gilhg5r2g74x,task_subcomment,NA
+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:
+
+ <div class=""do-not-make-smaller refsection references-column-count references-1column"">
+ <references />
+ </div>
+
+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",1375232040,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qwinndvqnthzbul47nb3,task_description,declined
+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).,1393528114,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qwinndvqnthzbul47nb3,task_subcomment,NA
+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?",1378424053,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-qwinndvqnthzbul47nb3,task_subcomment,NA
+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}",1375213740,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-ifh6gryuu6hee6pcadvb,task_description,invalid
+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.",1415880871,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ifh6gryuu6hee6pcadvb,task_subcomment,NA
+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}",1385522381,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-ifh6gryuu6hee6pcadvb,task_subcomment,NA
+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",1380645842,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-ifh6gryuu6hee6pcadvb,task_subcomment,NA
+VisualEditor: Following links in image captions that have a large <font size=> 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 <font size=12>, 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. <font size=12>text with a [[link]]</font>.
+
+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}",1375209840,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-aowfgq4eh3wcjsqyftty,task_description,resolved
+VisualEditor: Following links in image captions that have a large <font size=> 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 ***",1385396898,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aowfgq4eh3wcjsqyftty,task_subcomment,NA
+VisualEditor: Following links in image captions that have a large <font size=> 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.,1375227469,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-aowfgq4eh3wcjsqyftty,task_subcomment,NA
+VisualEditor: Following links in image captions that have a large <font size=> 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.",1375210111,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-aowfgq4eh3wcjsqyftty,task_subcomment,NA
+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",1375182720,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_description,declined
+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.",1384945365,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.
+
+:-)",1384871317,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.",1384864881,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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 :)",1383834351,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.",1383293007,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.",1383292738,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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.",1383282685,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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).",1382972546,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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 )",1377514974,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+VisualEditor should be themeable by the user with custom CSS,"Gryllida adds,
+<<To be quite honest, the first thing that I see wrong in the visual editor is the black-and-white style of icons, similar to what Google products uses. It is not 1980s when everything was black-and-white, nor it is 1990s when people used 256-color icons; it is 2013. [...] I believe it is important for accessibility to at least let users choose from a set of themes for the VisualEditor toolbar, if not alter the default theme.>>",1377427418,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wi6gwfwlbpwko4ows4b5,task_subcomment,NA
+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}",1375179540,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-juxrg4k7aci5xpwlvsaq,task_description,resolved
+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 ***",1376325366,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-juxrg4k7aci5xpwlvsaq,task_subcomment,NA
+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",1375176300,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-vbh2rbaxi3v4g2vosvk6,task_description,resolved
+Parsoid or VisualEditor: nowiki added around space following HTML comment,"
+
+*** This bug has been marked as a duplicate of bug 50758 ***",1375199871,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-vbh2rbaxi3v4g2vosvk6,task_subcomment,NA
+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",1375169040,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-poqv6admiczpvguuyu43,task_description,declined
+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.",1385396737,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-poqv6admiczpvguuyu43,task_subcomment,NA
+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.",1375263838,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-poqv6admiczpvguuyu43,task_subcomment,NA
+Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,"Labeled Section Transclusion (<section begin=""2012-07-monthly""/>Text here<section end=""2012-07-monthly""/>) 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",1375142220,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-2i2pvcby76cfowf624hh,task_description,resolved
+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 <section> 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 ***",1376428165,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+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.",1375203999,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,whoops. misfire.,1375203841,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid,"
+
+*** This bug has been marked as a duplicate of bug 51462 ***",1375203763,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+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. :-)",1375143543,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+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,1375142308,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-2i2pvcby76cfowf624hh,task_subcomment,NA
+"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}",1375142160,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xvbh6q43vypy6tjr3wjo,task_description,resolved
+"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 ***",1376073139,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xvbh6q43vypy6tjr3wjo,task_subcomment,NA
+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",1375138020,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-zg6asep6oadhz6pkrf4o,task_description,declined
+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.",1375141752,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zg6asep6oadhz6pkrf4o,task_subcomment,NA
+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",1375136040,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-yokifd7zmqwcieiz3iiy,task_description,resolved
+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 ***",1385384185,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yokifd7zmqwcieiz3iiy,task_subcomment,NA
+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",1375130640,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ahjlajk3zasbqo4br4bs,task_description,resolved
+VisualEditor: template substituted in,This was a recurring Parsoid bug which is now fixed; closing. Sorry for slow triage.,1385395969,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ahjlajk3zasbqo4br4bs,task_subcomment,NA
+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",1375105920,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-d4phvcwb6pak5wn2vbdh,task_description,resolved
+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 ***",1383282089,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d4phvcwb6pak5wn2vbdh,task_subcomment,NA
+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.",1375133339,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-d4phvcwb6pak5wn2vbdh,task_subcomment,NA
+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",1375088700,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-etdxsdkmhg4aoyrvdmmw,task_description,resolved
+reference clipboard errors,"
+
+*** This bug has been marked as a duplicate of bug 49396 ***",1375134084,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-etdxsdkmhg4aoyrvdmmw,task_subcomment,NA
+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}",1375057440,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wgr5qefyrk6vxixqgywz,task_description,resolved
+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 ***",1380221526,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wgr5qefyrk6vxixqgywz,task_subcomment,NA
+VisualEditor: Toolbar should fit on landscape iPad (and average non-maximised windows in general),Same as bug 51000?,1380219240,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-wgr5qefyrk6vxixqgywz,task_subcomment,NA
+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}",1380219110,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-wgr5qefyrk6vxixqgywz,task_subcomment,NA
+"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",1375037280,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_description,declined
+"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"":""<p>x</p>\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.",1384198086,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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.",1384198025,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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"":""<p>x</p>\n\n""}}",1384196822,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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.",1384196302,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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.",1375141400,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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) {
+    ...
+  }",1375047772,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+"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",1375045603,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3h7v3emjhhqinh5o5aqf,task_subcomment,NA
+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",1374988380,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-nuh252st2e54ff56mbpe,task_description,declined
+VisualEditor doesn't confirm closing window,Yeah I can confirm as well. Not sure when it started working again.,1390434737,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-nuh252st2e54ff56mbpe,task_subcomment,NA
+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?""",1390418026,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-nuh252st2e54ff56mbpe,task_subcomment,NA
+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.",1390417310,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nuh252st2e54ff56mbpe,task_subcomment,NA
+"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",1374947400,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-t6h3rucl4ojovdzxkq66,task_description,resolved
+"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 ***%%%",1375381691,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-t6h3rucl4ojovdzxkq66,task_subcomment,NA
+"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:
+
+<p data-parsoid=""{&quot;dsr&quot;:[0,45,0,0]}"" class=""ve-ce-branchNode"">
+<span class=""ve-ce-branchNode-slug ve-ce-branchNode-inlineSlug"">&#65279;</span></p>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374877260,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-3ew3gilga74djx2te24b,task_description,resolved
+"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 ***",1375199198,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ew3gilga74djx2te24b,task_subcomment,NA
+"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",1374905359,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-3ew3gilga74djx2te24b,task_subcomment,NA
+"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.",1374880550,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-3ew3gilga74djx2te24b,task_subcomment,NA
+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 <br clear=all> was duplicated minus the leading <
+
+Possibly related to bug 51304?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374877200,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-oqjy24dqtbqambra54dm,task_description,declined
+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.",1379848985,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oqjy24dqtbqambra54dm,task_subcomment,NA
+VisualEditor or Parsoid: Breaks and partially duplicates html tag,"Given the proximity of the image, im guessing this is bug 52107.",1375737774,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-oqjy24dqtbqambra54dm,task_subcomment,NA
+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",1374873360,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-jwf46mqjltex4ny7fpad,task_description,invalid
+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?)",1385398255,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jwf46mqjltex4ny7fpad,task_subcomment,NA
+VisualEditor - EditIntro is incorrectly linked in the monobook skin.,Confirming problem exists.  The fix probably needs to be made at [[MediaWiki:Common.js]],1374907792,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jwf46mqjltex4ny7fpad,task_subcomment,NA
+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",1374862080,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mx57agjpr44kackrkfz2,task_description,declined
+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.",1379847739,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mx57agjpr44kackrkfz2,task_subcomment,NA
+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",1375107801,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-mx57agjpr44kackrkfz2,task_subcomment,NA
+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.",1374903910,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-mx57agjpr44kackrkfz2,task_subcomment,NA
+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.",1374892576,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-mx57agjpr44kackrkfz2,task_subcomment,NA
+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/<i>foo<\/i>/g;"" | node parse --html2wt
+[[Foo|'''foo''']]
+
+[subbu@earth lib] echo ""[[Foo|'foo']]"" | node parse | sed ""s/foo/<b>foo<\/b>/g;"" | node parse --html2wt
+[[Foo|''''foo'''']]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374857700,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-pxbsw644f45j6giahmh5,task_description,resolved
+Missing nowiki escaping when single quotes wrap new i/b tags,Deployed and tested in production.,1375305913,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+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",1375108318,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+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",1375070667,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+Missing nowiki escaping when single quotes wrap new i/b tags,"Change 76162 merged by jenkins-bot:
+(Bug 52103) <nowiki/> escape when single quotes wrap new i/b tags
+
+https://gerrit.wikimedia.org/r/76162",1374946378,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+Missing nowiki escaping when single quotes wrap new i/b tags,"Change 76162 had a related patch set uploaded by Subramanya Sastry:
+(Bug 52103) <nowiki/> escape when single quotes wrap new i/b tags
+
+https://gerrit.wikimedia.org/r/76162",1374870985,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pxbsw644f45j6giahmh5,task_subcomment,NA
+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",1374837420,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-inyop7q4zxzxlulleamf,task_description,declined
+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.",1385996565,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-inyop7q4zxzxlulleamf,task_subcomment,NA
+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).",1385396429,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-inyop7q4zxzxlulleamf,task_subcomment,NA
+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.",1375183728,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-inyop7q4zxzxlulleamf,task_subcomment,NA
+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"".",1374838260,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-inyop7q4zxzxlulleamf,task_subcomment,NA
+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 <ref> tag, but about template that add the <ref> 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 <ref> 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",1374825720,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-olrhjl5ydsytkfv6yzoo,task_description,resolved
+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 ***",1374880234,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-olrhjl5ydsytkfv6yzoo,task_subcomment,NA
+"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 <nowiki><Tab></nowiki> 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",1374817380,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-3d44p7lu3ycz3cvuwxqd,task_description,resolved
+"Wrong tab-order on the ""Edit summary"" window","
+
+*** This bug has been marked as a duplicate of bug 51918 ***",1374880815,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3d44p7lu3ycz3cvuwxqd,task_subcomment,NA
+"Wrong tab-order on the ""Edit summary"" window","
+
+*** This bug has been marked as a duplicate of bug 50047 ***",1374818679,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-3d44p7lu3ycz3cvuwxqd,task_subcomment,NA
+VisualEditor: only a part of word is linked and <nowiki/> 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, <nowiki/> 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",1374778680,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-yvfkvibbvk27rfmuao7p,task_description,declined
+VisualEditor: only a part of word is linked and <nowiki/> 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.",1374797030,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yvfkvibbvk27rfmuao7p,task_subcomment,NA
+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",1374770400,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ijjtl5hsv4igmy4k6sej,task_description,resolved
+VisualEditor: blanking a page doesn't remove comments,"
+
+*** This bug has been marked as a duplicate of bug 49603 ***",1393271493,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ijjtl5hsv4igmy4k6sej,task_subcomment,NA
+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 .",1391511752,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ijjtl5hsv4igmy4k6sej,task_subcomment,NA
+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",1374765240,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-tghru467viza4owq4m3v,task_description,resolved
+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 ***",1395357259,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tghru467viza4owq4m3v,task_subcomment,NA
+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==<nowiki>{{template}}</nowiki>"" 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.",1378037641,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-tghru467viza4owq4m3v,task_subcomment,NA
+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",1374763800,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fcytooow3nd5c6cwcwl6,task_description,resolved
+TemplateData should allow specifying default values for parameters,"
+
+*** This bug has been marked as a duplicate of bug 51428 ***",1375183466,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fcytooow3nd5c6cwcwl6,task_subcomment,NA
+"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}",1374709260,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mcleu5c4oborex7k7xit,task_description,resolved
+"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.",1377190936,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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.",1377190457,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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&section=3",1374771991,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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.",1374744764,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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.",1374744542,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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?",1374740581,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-mcleu5c4oborex7k7xit,task_subcomment,NA
+"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",1374697260,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-s2gl74yfgu2t3qm3jv3q,task_description,resolved
+"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.,1385395164,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s2gl74yfgu2t3qm3jv3q,task_subcomment,NA
+"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",1374686580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fyok2cjpctqiorpfldvp,task_description,invalid
+"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)",1376065760,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fyok2cjpctqiorpfldvp,task_subcomment,NA
+"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?",1374704563,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-fyok2cjpctqiorpfldvp,task_subcomment,NA
+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",1374684900,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_description,resolved
+VisualEditor: can't remove missing image,"
+
+*** This bug has been marked as a duplicate of bug 50788 ***",1377623981,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+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.",1376309716,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+VisualEditor: can't remove missing image,I actually moved the above comment to https://bugzilla.wikimedia.org/show_bug.cgi?id=52575 . Thanks.,1375790933,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+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!),1375704777,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+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]]",1374705106,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-krz3dz5vyj2jo6pufnnb,task_subcomment,NA
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> 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 
+
+:<nowiki>...in common with the Classes <a href=tel:313 / 314 / 315"">313 / 314 / 315</a> / 507 / 508 units.</nowiki>
+
+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",1374669600,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hekxaxmddcora46opa6e,task_description,invalid
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> 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.,1374690787,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-hekxaxmddcora46opa6e,task_subcomment,NA
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> and refused to save,"Just for reference, the original reporter subsequently noted that they use Ipad IOS6 with Safari",1374683186,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hekxaxmddcora46opa6e,task_subcomment,NA
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> 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).",1374680186,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hekxaxmddcora46opa6e,task_subcomment,NA
+VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> and refused to save,This may be a VE issue if you are seeing a-href showing up in wikitext on serialization.,1374678107,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-hekxaxmddcora46opa6e,task_subcomment,NA
+VisualEditor: <nowiki> tags not deleted when surrounding element or text is deleted,"User Atethnekos at en.wp reports:
+""If in the source code there is <<nowwiki/>blockquote>, and in VE I select ""<blockquote>"" and delete it, when I save the <nowiki/> 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",1374661620,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-wg4if5a5jfs6ciuoa7x3,task_description,resolved
+VisualEditor: <nowiki> 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 ***",1374879593,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wg4if5a5jfs6ciuoa7x3,task_subcomment,NA
+VisualEditor: Deleting last use of reference should remove the entry from <references>..</references>,"This is related to Bug 51741, which is about adding support for <references>...</references>
+
+If the page already has <references>..</references>, and the last use of a named reference is removed, the entry inside <references>..</references> 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: <ref> tag with name ""rockspot_1"" defined in <references> is not used in prior text.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374657660,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dbgv7dfw47acis2f72rd,task_description,resolved
+VisualEditor: Deleting last use of reference should remove the entry from <references>..</references>,This was done some time ago; sorry for the slow triage.,1385395008,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dbgv7dfw47acis2f72rd,task_subcomment,NA
+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",1374642420,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-53dxg6rsj6uqcm45wss5,task_description,resolved
+VisualEditor: Retain newlines between parameters in transclusion invocations,This was fixed some time ago; sorry for the slow triage.,1385397595,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-53dxg6rsj6uqcm45wss5,task_subcomment,NA
+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",1374979926,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-53dxg6rsj6uqcm45wss5,task_subcomment,NA
+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",1374609540,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-horg3ds56xoznfv445i2,task_description,invalid
+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.",1385382898,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-horg3ds56xoznfv445i2,task_subcomment,NA
+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}",1374608640,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fl755yo3ekdckavdhb4b,task_description,invalid
+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.,1389677471,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+VisualEditor: Inserting media dialog has no confirmation button,Sorry for confirming; the UI design should be a separate bug.,1374706420,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+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.",1374703705,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+VisualEditor: Inserting media dialog has no confirmation button,Bug/enhancement reported as bug 51911.,1374614627,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+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.",1374613964,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+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.,1374608768,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fl755yo3ekdckavdhb4b,task_subcomment,NA
+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",1374588720,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-4r4lbhkxqhogotfzas57,task_description,resolved
+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.",1385394193,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4r4lbhkxqhogotfzas57,task_subcomment,NA
+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",1374583260,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-fz3rgh4ljjpvwe3terlp,task_description,declined
+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.",1390607728,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fz3rgh4ljjpvwe3terlp,task_subcomment,NA
+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?",1374592005,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fz3rgh4ljjpvwe3terlp,task_subcomment,NA
+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",1374573300,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-w26cnf2uzn6whhzpd4p5,task_description,declined
+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).",1408666032,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-w26cnf2uzn6whhzpd4p5,task_subcomment,NA
+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.,1408597771,PHID-USER-ll6tmaogat2b5q7tnqas,True,PHID-TASK-w26cnf2uzn6whhzpd4p5,task_subcomment,NA
+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.],1378939553,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-w26cnf2uzn6whhzpd4p5,task_subcomment,NA
+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",1374524640,PHID-USER-fgzcdbj3je3ksnhufo47,False,PHID-TASK-fgo5ntod4pt7hex3reuf,task_description,resolved
+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.,1385395314,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fgo5ntod4pt7hex3reuf,task_subcomment,NA
+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",1374518520,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ibvdz6zkyuw2mud34vwr,task_description,resolved
+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 ***",1374645680,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ibvdz6zkyuw2mud34vwr,task_subcomment,NA
+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.",1374522496,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ibvdz6zkyuw2mud34vwr,task_subcomment,NA
+Long lines in <pre> blocks don't cause page formatting to extend right. The html page is extended massively further than needed,"Long <pre> blocks rendered in Firefox 22 on Xubuntu Linux. Monobook skin.
+
+When <pre> blocks contain lines longer than the width of the page, the <pre> 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}",1374516900,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-o6hvv37kdmfpbrbf7mjf,task_description,resolved
+Long lines in <pre> 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 ***",1374526756,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-o6hvv37kdmfpbrbf7mjf,task_subcomment,NA
+Long lines in <pre> 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.",1374518559,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-o6hvv37kdmfpbrbf7mjf,task_subcomment,NA
+Long lines in <pre> 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.,1374517626,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-o6hvv37kdmfpbrbf7mjf,task_subcomment,NA
+"Removing a heading is hard, leaving ==<nowiki/>== 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.
+
+==<nowiki/>==
+
+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",1374514920,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-veppenlnczvh4hbbxwsw,task_description,resolved
+"Removing a heading is hard, leaving ==<nowiki/>== or turning the next paragraph into a heading","
+
+*** This bug has been marked as a duplicate of bug 50100 ***",1374609807,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-veppenlnczvh4hbbxwsw,task_subcomment,NA
+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",1374512940,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bsoljznx4zww5csa3zth,task_description,declined
+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).",1385392185,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bsoljznx4zww5csa3zth,task_subcomment,NA
+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}",1374512940,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-tvk7p5y33xg5evlkkbgh,task_description,resolved
+VisualEditor renderizes the image a lot bigger than it should,"
+
+*** This bug has been marked as a duplicate of bug 51628 ***",1374548109,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tvk7p5y33xg5evlkkbgh,task_subcomment,NA
+VisualEditor renderizes the image a lot bigger than it should,"Parsoid keeps the code as is:
+http://parsoid.wmflabs.org/_rt/pt/?oldid=36476193",1374513396,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-tvk7p5y33xg5evlkkbgh,task_subcomment,NA
+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]]",1374513316,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-tvk7p5y33xg5evlkkbgh,task_subcomment,NA
+"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",1374511320,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_description,resolved
+"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).",1394528224,PHID-USER-7zhn2ep5wvjhxetsbb6n,True,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+"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. ***,1394503905,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+"VisualEditor: When window is narrowed, article title can display over the top of the toolbar",This was fixed by Trevor in January.,1394477948,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+"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.",1374519760,PHID-USER-7zhn2ep5wvjhxetsbb6n,True,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+"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.",1374512088,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-4pnt5quh7n4hpe7ffu3t,task_subcomment,NA
+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",1374498600,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-2ub5t2oupkp4z4qo32ce,task_description,resolved
+Transclusion editor: remove template creates blank dialog,"
+
+*** This bug has been marked as a duplicate of bug 50281 ***",1374702151,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-2ub5t2oupkp4z4qo32ce,task_subcomment,NA
+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""",1374701365,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-2ub5t2oupkp4z4qo32ce,task_subcomment,NA
+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.",1374696871,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-2ub5t2oupkp4z4qo32ce,task_subcomment,NA
+"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}",1374495480,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-4itryfnmayohwwozkuws,task_description,resolved
+"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.",1375726508,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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",1375725903,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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",1375204451,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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.",1375202187,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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.",1375202101,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+"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),1375147278,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4itryfnmayohwwozkuws,task_subcomment,NA
+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",1374495000,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-calntit5bgsnncojx237,task_description,resolved
+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 ***",1374854170,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-calntit5bgsnncojx237,task_subcomment,NA
+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.",1374853627,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-calntit5bgsnncojx237,task_subcomment,NA
+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}",1374481140,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-kuzyc5hs4c2r4b2fex4f,task_description,resolved
+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",1374513446,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kuzyc5hs4c2r4b2fex4f,task_subcomment,NA
+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 ***",1374489509,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kuzyc5hs4c2r4b2fex4f,task_subcomment,NA
+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",1374487397,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kuzyc5hs4c2r4b2fex4f,task_subcomment,NA
+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",1374470760,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-ayjpiyllgpwjsso4fzvt,task_description,resolved
+TemplateData for redirected templates,"
+
+*** This bug has been marked as a duplicate of bug 50964 ***",1374641783,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ayjpiyllgpwjsso4fzvt,task_subcomment,NA
+TemplateData for redirected templates,Discussed at http://en.wikipedia.org/wiki/Wikipedia_talk:VisualEditor/TemplateData#What_about_redirected_templates,1374471289,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-ayjpiyllgpwjsso4fzvt,task_subcomment,NA
+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",1374415800,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-m2dyfyycv5j7jnwg3sup,task_description,resolved
+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.",1385392734,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-m2dyfyycv5j7jnwg3sup,task_subcomment,NA
+"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",1374349320,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-ydxhivupzag4qu4llhwx,task_description,declined
+"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.",1395355910,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ydxhivupzag4qu4llhwx,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'info' of undefined"" (when saving the page)",Which article did this occur on?,1374367709,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ydxhivupzag4qu4llhwx,task_subcomment,NA
+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",1374343560,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gkasmmcbpikhl6gq6kg5,task_description,resolved
+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.,1395356968,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gkasmmcbpikhl6gq6kg5,task_subcomment,NA
+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).",1386820754,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-gkasmmcbpikhl6gq6kg5,task_subcomment,NA
+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",1374334080,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-z7k6ld4qvfzn2ify7im6,task_description,resolved
+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.,1385391924,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z7k6ld4qvfzn2ify7im6,task_subcomment,NA
+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",1374306840,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-ltt3irfuuufns7tetoc3,task_description,resolved
+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 ***",1390416862,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ltt3irfuuufns7tetoc3,task_subcomment,NA
+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",1374285720,PHID-USER-3ampiwske4lc434cm6ot,False,PHID-TASK-ebhdb6qns6ottyytmzfa,task_description,resolved
+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",1374507519,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ebhdb6qns6ottyytmzfa,task_subcomment,NA
+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",1374506856,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ebhdb6qns6ottyytmzfa,task_subcomment,NA
+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",1374267420,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-s4chuo432xmbozeyirll,task_description,resolved
+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 ***",1377833797,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s4chuo432xmbozeyirll,task_subcomment,NA
+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",1374229860,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-ydbji5fefbbeiocpl24u,task_description,resolved
+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.,1385392298,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ydbji5fefbbeiocpl24u,task_subcomment,NA
+VisualEditor: Rearranging transclusions breaks the ability to select parameters.,Also happens on Linux.,1374477983,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ydbji5fefbbeiocpl24u,task_subcomment,NA
+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"".",1374231992,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-ydbji5fefbbeiocpl24u,task_subcomment,NA
+"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",1374203640,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z2agxnwfy52lvo6yjxrd,task_description,resolved
+"VisualEditor: Relabel buttons in ""cancel editing"" confirmation dialog","Merging with bug 50955.
+
+*** This bug has been marked as a duplicate of bug 50955 ***",1374267909,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z2agxnwfy52lvo6yjxrd,task_subcomment,NA
+"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.",1374212616,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-z2agxnwfy52lvo6yjxrd,task_subcomment,NA
+"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",1374199860,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-3qhhrxr2wofxfssyycod,task_description,declined
+"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.,1385392053,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3qhhrxr2wofxfssyycod,task_subcomment,NA
+"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",1374162180,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-2maqvichtgrs77o35tls,task_description,resolved
+"VisualEditor: ""Leave Feedback"" link greyed out; might confuse users",This design was fixed some time ago but I forgot to tag this bug; sorry!,1385386362,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2maqvichtgrs77o35tls,task_subcomment,NA
+"""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",1374162000,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-pbxss6r2sg7qfrxykect,task_description,resolved
+"""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 ***",1374162111,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pbxss6r2sg7qfrxykect,task_subcomment,NA
+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",1374088140,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-tgo7euxf3cnwhcvmwsfs,task_description,resolved
+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 ***",1395354371,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tgo7euxf3cnwhcvmwsfs,task_subcomment,NA
+"VisualEditor: <nowiki> 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 <nowiki> tags around it (correct according to apparent design, incorrect according to desired behaviour). 
+
+However, it also added <nowiki> 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",1374081420,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-rorj54kzrfz5yajplzy6,task_description,resolved
+"VisualEditor: <nowiki> 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.,1375199810,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rorj54kzrfz5yajplzy6,task_subcomment,NA
+"VisualEditor: <nowiki> 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.",1374081808,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-rorj54kzrfz5yajplzy6,task_subcomment,NA
+"VisualEditor: <nowiki> tags added to all markup in paragraph, including pre-existing","Sorry, typo in that last line. It should refer to Bug 50569 comment 5",1374081645,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-rorj54kzrfz5yajplzy6,task_subcomment,NA
+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",1374070440,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-lc76yoxati6qqmlqel6x,task_description,resolved
+Can't save,"
+
+%%%*** This bug has been marked as a duplicate of bug 50284 ***%%%",1374071458,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-lc76yoxati6qqmlqel6x,task_subcomment,NA
+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.",1374071358,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-lc76yoxati6qqmlqel6x,task_subcomment,NA
+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",1374065040,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-jo6lx3im2dnf4fgrh2cy,task_description,resolved
+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 ***",1374679397,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jo6lx3im2dnf4fgrh2cy,task_subcomment,NA
+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]]",1374678668,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jo6lx3im2dnf4fgrh2cy,task_subcomment,NA
+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",1374064500,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-nuhotkfh44rday75ra54,task_description,resolved
+VisualEditor: Tab key moves focus between citations; doesn't indent text as expected,"
+
+*** This bug has been marked as a duplicate of bug 48010 ***",1395359458,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nuhotkfh44rday75ra54,task_subcomment,NA
+"VisualEditor: Inserting whitespace in front of a paragraph shouldn't convert the paragraph to a preformatted block, but also shouldn't leave unneeded <nowiki>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",1374063600,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-tpc6ler6znj3xz2beohn,task_description,resolved
+"VisualEditor: Inserting whitespace in front of a paragraph shouldn't convert the paragraph to a preformatted block, but also shouldn't leave unneeded <nowiki>s",This was fixed in July; sorry for the slow triage.,1385386267,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tpc6ler6znj3xz2beohn,task_subcomment,NA
+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:
+<pre>
+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]#
+</pre>
+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",1374048060,PHID-USER-qrnoqj2szt6knvcqvaxt,False,PHID-TASK-eril5tvgiad53f3rcpft,task_description,declined
+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.",1374051736,PHID-USER-qrnoqj2szt6knvcqvaxt,False,PHID-TASK-eril5tvgiad53f3rcpft,task_subcomment,NA
+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.",1374048262,PHID-USER-qrnoqj2szt6knvcqvaxt,False,PHID-TASK-eril5tvgiad53f3rcpft,task_subcomment,NA
+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.",1374048167,PHID-USER-qrnoqj2szt6knvcqvaxt,False,PHID-TASK-eril5tvgiad53f3rcpft,task_subcomment,NA
+&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",1374012540,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-tlf237apfkoioeofs5ec,task_description,declined
+&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.",1382132925,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-tlf237apfkoioeofs5ec,task_subcomment,NA
+&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.",1382132880,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tlf237apfkoioeofs5ec,task_subcomment,NA
+&veaction= as a second parameter works on enwiki but not zhwiki,I cant reproduce this now.,1382132030,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-tlf237apfkoioeofs5ec,task_subcomment,NA
+"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",1373999220,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-djoqnd37pa6rtsa7b2iv,task_description,invalid
+"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.",1385374579,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-djoqnd37pa6rtsa7b2iv,task_subcomment,NA
+"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.",1380534380,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-djoqnd37pa6rtsa7b2iv,task_subcomment,NA
+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}",1373997420,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-w2eu52oilk4spsdpzeoa,task_description,resolved
+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 ***",1379788309,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-w2eu52oilk4spsdpzeoa,task_subcomment,NA
+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",1377775284,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-w2eu52oilk4spsdpzeoa,task_subcomment,NA
+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?),1377769124,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-w2eu52oilk4spsdpzeoa,task_subcomment,NA
+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",1373996400,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-d36xqpcmqmrkpqcgucpb,task_description,resolved
+VisualEditor: Category adding interface is hard to find,"
+
+*** This bug has been marked as a duplicate of bug 51153 ***",1374010099,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-d36xqpcmqmrkpqcgucpb,task_subcomment,NA
+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.",1374005371,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-d36xqpcmqmrkpqcgucpb,task_subcomment,NA
+"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",1373983800,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pskrxedevzwi6wzlhh27,task_description,declined
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'end' of null""",Provisionally closing as WORKSFORME.,1385386303,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pskrxedevzwi6wzlhh27,task_subcomment,NA
+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 <a>link</a>
+ Select link (has to be done manually (tedious and error prone) 
+ > Some [selection]<a>link</a>[/selection]""
+ Type ""hello"".
+ > Some <a>h</a>ello.
+
+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 ""<a>first char</a>other chars"" case.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48463",1373981640,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hqvxg56nlg2toykqmhmk,task_description,duplicate
+VisualEditor: Link inspector should make it easier to change the label,"
+
+*** This bug has been marked as a duplicate of bug 53973 ***",1395196870,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+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.",1391535731,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+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.",1378925410,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+VisualEditor: Link inspector should make it easier to change the label,I think this duplicates Bug 50945,1375181384,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+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.",1374009514,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-hqvxg56nlg2toykqmhmk,task_subcomment,NA
+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}",1373959140,PHID-USER-34ciubbmtvmsgh53t6hb,False,PHID-TASK-rl6e4brnawmfpf74jcdj,task_description,resolved
+Syndicated feeds of Watchlists include non-existent edits,This seems fixed now for me.,1395065589,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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.",1383507823,PHID-USER-a6jwrurphpx6yl4coupk,False,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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...",1374562249,PHID-USER-34ciubbmtvmsgh53t6hb,False,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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)",1374557457,PHID-USER-34ciubbmtvmsgh53t6hb,False,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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:",1373960032,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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.",1373959528,PHID-USER-34ciubbmtvmsgh53t6hb,False,PHID-TASK-rl6e4brnawmfpf74jcdj,task_subcomment,NA
+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",1373950620,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-nkmn6tlxg6fzvqjixjiw,task_description,resolved
+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 ***",1377278955,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nkmn6tlxg6fzvqjixjiw,task_subcomment,NA
+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.",1377248899,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-nkmn6tlxg6fzvqjixjiw,task_subcomment,NA
+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.",1377222218,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-nkmn6tlxg6fzvqjixjiw,task_subcomment,NA
+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",1373937720,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-euerogqwtdmzt7fjkkmb,task_description,resolved
+Blanking last section of page corrupts heading,"
+
+%%%*** This bug has been marked as a duplicate of bug 50100 ***%%%",1373938090,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-euerogqwtdmzt7fjkkmb,task_subcomment,NA
+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",1373929020,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-h3r2wuw2m4pdrb5ixf7h,task_description,resolved
+color picker,"
+
+*** This bug has been marked as a duplicate of bug 52645 ***",1376120681,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-h3r2wuw2m4pdrb5ixf7h,task_subcomment,NA
+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",1373917620,PHID-USER-dswbdv7ibhsefllcqarz,False,PHID-TASK-a465jbds23gplxffpkqu,task_description,resolved
+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 ***",1373926494,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-a465jbds23gplxffpkqu,task_subcomment,NA
+VisualEditor: spurious parentheses added,"See https://en.wikipedia.org/w/index.php?title=Wormshill&diff=564367057&oldid=557770558 for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373900400,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-nanbji3vohfklohczwir,task_description,declined
+VisualEditor: spurious parentheses added,"This is caused by an unbalanced <blockquote> 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.",1385386705,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nanbji3vohfklohczwir,task_subcomment,NA
+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",1373899320,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ipxn4a5xggbelogecqff,task_description,declined
+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.",1374456028,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ipxn4a5xggbelogecqff,task_subcomment,NA
+504 timeout with Parsoid service,See http://www.mediawiki.org/wiki/MediaWiki_on_IRC for information on IRC.,1373927829,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ipxn4a5xggbelogecqff,task_subcomment,NA
+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.,1373901602,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ipxn4a5xggbelogecqff,task_subcomment,NA
+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",1373895180,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-pi2tzunhpx5y7ayoea2g,task_description,resolved
+VisualEditor: Edit this Page button ignores &oldid=prev parameter.,This seems to now be fixed. Please re-open if you think I'm wrong!,1385387326,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pi2tzunhpx5y7ayoea2g,task_subcomment,NA
+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.",1374477548,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-pi2tzunhpx5y7ayoea2g,task_subcomment,NA
+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",1373886720,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-6syee5vbnlo6bygtishg,task_description,invalid
+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.",1378122078,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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 ?",1376729948,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+Add ULS language setting dialogue box in VisualEditor page settings,Mahitgar: Could you please answer comment 5?,1376399379,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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.",1374496050,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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?,1374494932,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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.,1374075062,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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}",1373969905,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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.",1373893663,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6syee5vbnlo6bygtishg,task_subcomment,NA
+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",1373885880,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-avk6xwxd7jsix4gwqxoe,task_description,resolved
+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 ***",1373968970,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-avk6xwxd7jsix4gwqxoe,task_subcomment,NA
+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}",1373956157,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-avk6xwxd7jsix4gwqxoe,task_subcomment,NA
+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.",1373893817,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-avk6xwxd7jsix4gwqxoe,task_subcomment,NA
+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",1373878680,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-6vh7i45cbz7znphxlsf6,task_description,resolved
+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 ***",1373932279,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6vh7i45cbz7znphxlsf6,task_subcomment,NA
+VisualEditor: Automatically add title of the section to edit summary,"**ignatzmice.wiki** wrote:
+
+I agree with Michael, this would be very useful.",1373891958,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6vh7i45cbz7znphxlsf6,task_subcomment,NA
+"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}",1373871600,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vlaiyo2akniolmqe5tq6,task_description,resolved
+"VisualEditor: double-clicking ""create reference"" generates a quasi-broken ref form.",This has been fixed since July; sorry for slow update.,1385383559,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vlaiyo2akniolmqe5tq6,task_subcomment,NA
+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",1373869620,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-aljzsqmks2kf5dymrk45,task_description,resolved
+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.,1385383181,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aljzsqmks2kf5dymrk45,task_subcomment,NA
+VisualEditor: Applying a transclusion that only contains content brackets breaks the edit toolbar.,*** Bug 51437 has been marked as a duplicate of this bug. ***,1374545947,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-aljzsqmks2kf5dymrk45,task_subcomment,NA
+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",1373847540,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-favvfitkxvyu4vmy3ump,task_description,resolved
+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.,1385384432,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-favvfitkxvyu4vmy3ump,task_subcomment,NA
+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",1373780340,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-fldsdjwnv5jvqc2iam55,task_description,duplicate
+Allow wikitext e.g. links to documentation in templatedata,"
+
+*** This bug has been marked as a duplicate of bug 50656 ***",1375191068,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fldsdjwnv5jvqc2iam55,task_subcomment,NA
+Allow wikitext e.g. links to documentation in templatedata,*** Bug 50656 has been marked as a duplicate of this bug. ***,1375187353,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-fldsdjwnv5jvqc2iam55,task_subcomment,NA
+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 <code> tag to all better distinguishing of '' (two apostrophes for italic markup) and "" (double quote) by rendering them in a monospace font.",1373787877,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fldsdjwnv5jvqc2iam55,task_subcomment,NA
+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",1373700600,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ykvbtj26wyleuw4bnbjh,task_description,resolved
+VisualEditor: External link missing in template due to linkname with ampersand in it,confirmed,1385420773,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ykvbtj26wyleuw4bnbjh,task_subcomment,NA
+VisualEditor: External link missing in template due to linkname with ampersand in it,I think this has been subsequently fixed - can you confirm?,1385386971,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ykvbtj26wyleuw4bnbjh,task_subcomment,NA
+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",1373649540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-de6dmorszoddddclnd4y,task_description,invalid
+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",1373652658,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-de6dmorszoddddclnd4y,task_subcomment,NA
+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",1373652398,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-de6dmorszoddddclnd4y,task_subcomment,NA
+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",1373645640,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-yz6cpenppcreusg72zvt,task_description,resolved
+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 <meta typeof=""mw:Placeholder"" data-parsoid=""…""> 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 ***",1373646127,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yz6cpenppcreusg72zvt,task_subcomment,NA
+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",1373645936,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-yz6cpenppcreusg72zvt,task_subcomment,NA
+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",1373610900,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-hrdmmz7wdsz3xmnhvpp2,task_description,resolved
+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 ***",1374459959,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-hrdmmz7wdsz3xmnhvpp2,task_subcomment,NA
+VisualEditor: Cut and Pasting a section that contains an image truncates all the sections formatting after pasting it.,Confirming your example.,1374459355,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-hrdmmz7wdsz3xmnhvpp2,task_subcomment,NA
+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,1373883205,PHID-USER-lumvg23bxmfbvekr2fbo,False,PHID-TASK-hrdmmz7wdsz3xmnhvpp2,task_subcomment,NA
+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",1373577600,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-jakyw4q5ktlmqgd4sv3v,task_description,declined
+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.",1373599184,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jakyw4q5ktlmqgd4sv3v,task_subcomment,NA
+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,1373577841,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jakyw4q5ktlmqgd4sv3v,task_subcomment,NA
+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.
+<br>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",1373569320,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-mruibaiz5kt46pzezn7l,task_description,resolved
+Template rearranging itself,This was the Parsoid complex templates / VisualEditor dirtying edits bug that got fixed months ago; sorry for the very slow triage.,1390416930,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mruibaiz5kt46pzezn7l,task_subcomment,NA
+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",1373566080,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-mgnru2nwxtufpuc6lqyx,task_description,resolved
+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 ***",1385382810,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mgnru2nwxtufpuc6lqyx,task_subcomment,NA
+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,1373568433,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-mgnru2nwxtufpuc6lqyx,task_subcomment,NA
+"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",1373562300,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-hn23baiwxuaicjnc3ue4,task_description,resolved
+"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.,1385380627,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hn23baiwxuaicjnc3ue4,task_subcomment,NA
+"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",1373555340,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-umxktvxo76lzoeghwqxz,task_description,resolved
+"Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read","**kwwilliams** wrote:
+
+It's 51150.",1374272928,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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",1374272740,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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.",1374272519,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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 ***",1374271260,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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.,1374270992,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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 ***%%%",1374270889,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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.",1374270607,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+"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).",1374252996,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-umxktvxo76lzoeghwqxz,task_subcomment,NA
+<nowiki/> 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",1373553780,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-htn2o6dmt6ze2hhaf537,task_description,invalid
+<nowiki/> added to wikilinks,"If the user selects ""diesel generator"" (i.e., misses the 's'), the resultant HTML would be
+
+  <a href=foo>diesel generator</a>s 
+
+The correct wikitext version of this is indeed
+
+  [[diesel generator]]<nowiki />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.",1373567309,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-htn2o6dmt6ze2hhaf537,task_subcomment,NA
+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",1373546700,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_description,resolved
+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 ***",1374079614,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_subcomment,NA
+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).",1373548204,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_subcomment,NA
+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.",1373547099,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_subcomment,NA
+VisualEditor: blanking an article and starting from scratch causes malformations,"Screenshot
+
+**Attached**: {F11062}",1373546784,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ikbuupkdg7jny4q2ih3u,task_subcomment,NA
+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",1373538900,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gonbe6svndpp6xg5nn7w,task_description,resolved
+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 ***",1377527402,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gonbe6svndpp6xg5nn7w,task_subcomment,NA
+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.,1374487773,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gonbe6svndpp6xg5nn7w,task_subcomment,NA
+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).",1373578518,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gonbe6svndpp6xg5nn7w,task_subcomment,NA
+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",1373509140,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-maorft5oyfrh3mtkgplv,task_description,duplicate
+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.",1385386774,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-maorft5oyfrh3mtkgplv,task_subcomment,NA
+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.",1374229995,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-maorft5oyfrh3mtkgplv,task_subcomment,NA
+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?",1374010319,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-maorft5oyfrh3mtkgplv,task_subcomment,NA
+VisualEditor: Category interface is hard to find,*** Bug 51452 has been marked as a duplicate of this bug. ***,1374010099,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-maorft5oyfrh3mtkgplv,task_subcomment,NA
+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",1373485620,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-zt2vp3ws2fthuoczhtcs,task_description,declined
+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.,1397677941,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zt2vp3ws2fthuoczhtcs,task_subcomment,NA
+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)",1377444558,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-zt2vp3ws2fthuoczhtcs,task_subcomment,NA
+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,<ref>[null http:///www.icmacabre.blogspot.com]</ref>
+
+----
+
+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",1373484720,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-zvpdqkuywxev3x3oy6sk,task_description,resolved
+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.",1385382685,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvpdqkuywxev3x3oy6sk,task_subcomment,NA
+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",1373481780,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-fc6sg7pcqin3kmtv4x57,task_description,resolved
+VisualEditor: Removing template & Adding content breaks editor,"Bug 51340 is essentially the same issue, and both are now fixed I believe.",1385387104,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fc6sg7pcqin3kmtv4x57,task_subcomment,NA
+"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",1373479140,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bypr3rbgyguddodinker,task_description,resolved
+"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 ***",1373480869,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bypr3rbgyguddodinker,task_subcomment,NA
+"VisualEditor: Review changes should show the edit summary, if one has been provided.",I think this duplicates bug 42139,1373479854,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bypr3rbgyguddodinker,task_subcomment,NA
+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",1373474880,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_description,duplicate
+Transcluded pages quasi-template eats into subsequent entry,Opened Parsoid bug 53368 for the issues described in comment #12 above.,1377549211,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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 <ul> 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.",1377219256,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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.",1377216081,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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.",1376663796,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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).",1376663213,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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.",1376662900,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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?",1376661657,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+Transcluded pages quasi-template eats into subsequent entry,*** Bug 52814 has been marked as a duplicate of this bug. ***,1376639350,PHID-USER-3uecblbxq24ycewm2cog,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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.,1376620889,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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 <ul> 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.",1376618254,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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')
+;
+```",1432542616,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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')
+;
+```",1432542425,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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')
+;",1374649444,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+Transcluded pages quasi-template eats into subsequent entry,"Relevant wikitext excerpt:
+
+| {{:Christian Delius}}
+| <!-- Änderungen bitte dort vornehmen, siehe unterhalb des Bearbeitungsfensters -->
+| * [[Christina Rau]], geb. Delius (* 1956), deutsche Politologin
+
+Yeah, this is because the HTML comment and <li> in the wikitext below the template insert themselves into the implicit <ul> 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).",1374645296,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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",1374539843,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-ax4pkg2fcq3uwnfjn5h5,task_subcomment,NA
+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",1373450100,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-rzacfnoggbzshwb2qnc6,task_description,resolved
+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 ***",1373480408,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rzacfnoggbzshwb2qnc6,task_subcomment,NA
+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",1373430900,PHID-USER-kc6qx3zohjybu3nzffu3,False,PHID-TASK-cj43kd2u4kzkuq6rlhnu,task_description,invalid
+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 <div>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.",1373724208,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cj43kd2u4kzkuq6rlhnu,task_subcomment,NA
+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.",1373693982,PHID-USER-kc6qx3zohjybu3nzffu3,False,PHID-TASK-cj43kd2u4kzkuq6rlhnu,task_subcomment,NA
+Editing adds JavaScript,"From a quick Google, this is a faulty browser plugin of some kind, FoxLingoJs.",1373521024,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cj43kd2u4kzkuq6rlhnu,task_subcomment,NA
+"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}",1373411220,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-j4lztgmjyrotthez4ft5,task_description,resolved
+"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 ***",1373411601,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-j4lztgmjyrotthez4ft5,task_subcomment,NA
+Adding a {{cn}} template causes VisualEditor to silently add <nowiki>..</nowiki> 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 <nowiki> issues on bugzilla
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373406240,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-eedu2jxaz76eztsst6ep,task_description,invalid
+Adding a {{cn}} template causes VisualEditor to silently add <nowiki>..</nowiki> 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.",1373409131,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eedu2jxaz76eztsst6ep,task_subcomment,NA
+Adding a {{cn}} template causes VisualEditor to silently add <nowiki>..</nowiki> 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.",1373406615,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eedu2jxaz76eztsst6ep,task_subcomment,NA
+VisualEditor: Link input field identifiers in DOM are bogus,"corrupt <class> identifier in DOM for Link
+
+see screenshot
+
+what is this ""class""?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11753}",1373398680,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-dhjt3sejejdufp3ya2co,task_description,invalid
+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.",1375221769,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-dhjt3sejejdufp3ya2co,task_subcomment,NA
+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",1373395500,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-weyb3zctidhjrppnilwj,task_description,resolved
+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 ***",1385381556,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-weyb3zctidhjrppnilwj,task_subcomment,NA
+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!",1373401725,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-weyb3zctidhjrppnilwj,task_subcomment,NA
+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",1373392500,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-2j6ctllml6qqxhzmqlmr,task_description,resolved
+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 ***",1394501875,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2j6ctllml6qqxhzmqlmr,task_subcomment,NA
+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]]",1379885198,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-2j6ctllml6qqxhzmqlmr,task_subcomment,NA
+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",1377447358,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-2j6ctllml6qqxhzmqlmr,task_subcomment,NA
+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}",1373385480,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-6uqz7k3i6hhy6r5mf4qh,task_description,resolved
+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 ***",1385381652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6uqz7k3i6hhy6r5mf4qh,task_subcomment,NA
+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",1373365380,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_description,resolved
+VisualEditor: adding spaces?,"This seems to be bug 48570
+
+*** This bug has been marked as a duplicate of bug 48570 ***",1379455266,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+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.",1379007082,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+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.",1374254808,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+VisualEditor: adding spaces?,Talking about spaces: https://en.wikipedia.org/w/index.php?title=Genie_%28feral_child%29&diff=564429158&oldid=564425048,1374227956,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+VisualEditor: adding spaces?,"Same thing here after ""équipes"": http://fr.wikipedia.org/w/index.php?title=Mafia_%28jeu%29&diff=94892395&oldid=91395852",1373626132,PHID-USER-mapumhlp3gw5qefhvafn,False,PHID-TASK-6d6mtcjbaxy3ev26rxls,task_subcomment,NA
+"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",1373361000,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-karzxpqg6fmjzovu77r7,task_description,resolved
+"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 ***",1373504485,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-karzxpqg6fmjzovu77r7,task_subcomment,NA
+"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.",1373364187,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-karzxpqg6fmjzovu77r7,task_subcomment,NA
+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",1373359380,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-3ngsdaq55c6cqyub75es,task_description,resolved
+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.",1383004078,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ngsdaq55c6cqyub75es,task_subcomment,NA
+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,1375808870,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-3ngsdaq55c6cqyub75es,task_subcomment,NA
+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.",1375121749,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-3ngsdaq55c6cqyub75es,task_subcomment,NA
+VisualEditor: Template dialog crushing parameters together and nowiking links,"Some broken browser extension sometimes adds lots of  <a class=""ktg6us78hf8vdu7"" href=""javascript:void(0)"">...</a> 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 <a class=""ktg6us78hf8vdu7"" href=""javascript:void(0)""><a class=""ktg6us78hf8vdu7"" href=""javascript:void(0)"">video</a></a> gaming|1990]]
+| products       = [[Crash Bandicoot|''Crash Bandicoot'' series]] (2002-2004) (2013- )<br>[[Skylanders|''Skylanders'' series]] (2011-2013)0)"">Guitar</a></a> Hero|''Guitar Hero'' series]] (2007–2010) 
+...
+}}
+
+Into
+{{Infobox company
+|<nowiki>1990]]</nowiki>
+|''Guitar Hero''<nowiki> series]] (2007–2010) </nowiki>
+...
+| foundation     = <nowiki>[[1990 in video gaming</nowiki>
+| products       = [[Crash Bandicoot|''Crash Bandicoot'' series]] (2002-2004) (2013- )<br>[[Skylanders|''Skylanders'' series]] (2011-2013) Guitar Hero
+...
+}}
+splitting the foundation and product parameters.",1373361466,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-3ngsdaq55c6cqyub75es,task_subcomment,NA
+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",1373330760,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-yvxmfw4svpxfoy2mq3xe,task_description,resolved
+VisualEditor: Template highlight is sometimes misplaced in the reference inspector,"
+
+*** This bug has been marked as a duplicate of bug 50913 ***",1373351191,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-yvxmfw4svpxfoy2mq3xe,task_subcomment,NA
+"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",1373324220,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-atyu2v5fwwehteymmmkf,task_description,duplicate
+"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 ***",1373472822,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-atyu2v5fwwehteymmmkf,task_subcomment,NA
+"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)",See also gerrit change 70564.,1373469016,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-atyu2v5fwwehteymmmkf,task_subcomment,NA
+"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/",1373325997,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-atyu2v5fwwehteymmmkf,task_subcomment,NA
+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",1373316060,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_description,resolved
+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 ***",1377831826,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+Selecting text does not work,Selecting text works at the page you provided but drag and drop does not work.,1373317925,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+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",1373317893,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+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 <translate> tags, it must be disabled on these pages. Thank you.",1373317502,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+Selecting text does not work,"It seems related to the <translate> tag, try it on another page like https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet",1373316358,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+Selecting text does not work,"As selecting text is a basic operation, bumping to a major issue.",1373316165,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+Selecting text does not work,FF 22,1373316086,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-xbi4z4qhqpsbwxzbb7j2,task_subcomment,NA
+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",1373315640,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-ovg5r2xmn4fehf7ofjhg,task_description,declined
+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.",1373363951,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-ovg5r2xmn4fehf7ofjhg,task_subcomment,NA
+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.",1373363212,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ovg5r2xmn4fehf7ofjhg,task_subcomment,NA
+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",1373314500,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-bhshtaaxwx36iiznlkm2,task_description,resolved
+Redlinks show up as bluelinks in VisualEditor mode,"
+
+*** This bug has been marked as a duplicate of bug 37901 ***",1373353929,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bhshtaaxwx36iiznlkm2,task_subcomment,NA
+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",1373297700,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-b3kpqkztod52q3bqpgcc,task_description,resolved
+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 ***",1373851066,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b3kpqkztod52q3bqpgcc,task_subcomment,NA
+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",1373241540,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-754mi2navz4pvonnspxh,task_description,declined
+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.",1385381445,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-754mi2navz4pvonnspxh,task_subcomment,NA
+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}",1373233920,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-njvhn6axgtv4xkldtkx2,task_description,resolved
+VisualEditor: Template editor turns links into [[link|name]] in CE,"
+
+*** This bug has been marked as a duplicate of bug 50801 ***",1373354186,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-njvhn6axgtv4xkldtkx2,task_subcomment,NA
+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",1373233620,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ovfsitu3qtht2esmfi2s,task_description,resolved
+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 ***",1375717235,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ovfsitu3qtht2esmfi2s,task_subcomment,NA
+VisualEditor: The anchor for the template editor can easily become invisible,Is this the same as bug 49922?,1374487466,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ovfsitu3qtht2esmfi2s,task_subcomment,NA
+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",1373232480,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-qrgadp2mt3qhvw2auoa4,task_description,resolved
+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 ***",1377814666,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qrgadp2mt3qhvw2auoa4,task_subcomment,NA
+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.",1373232552,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-qrgadp2mt3qhvw2auoa4,task_subcomment,NA
+Nested <nowiki>s considered harmful,"Sometimes Parsoid will wrap a <nowiki> around an existing <nowiki>; 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",1373055060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_description,resolved
+Nested <nowiki>s considered harmful,*** Bug 50724 has been marked as a duplicate of this bug. ***,1373637242,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+Nested <nowiki>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",1373473754,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+Nested <nowiki>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",1373470917,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+Nested <nowiki>s considered harmful,"Change 72230 merged by jenkins-bot:
+(Bug 50835) Dont nowiki escape already escaped template params
+
+https://gerrit.wikimedia.org/r/72230",1373307265,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+Nested <nowiki>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",1373065523,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lb7abq7fkyxs3qzwp4ty,task_subcomment,NA
+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",1373053920,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-wob6rhplaqtaaqqwjmgd,task_description,resolved
+VisualEditor: edits fail on hitting the abuse filter (with a cryptic error message),"
+
+*** This bug has been marked as a duplicate of bug 50472 ***",1373054299,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-wob6rhplaqtaaqqwjmgd,task_subcomment,NA
+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",1373048100,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-gqozvzrj5ka3lgyouwvn,task_description,resolved
+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 ***",1373077734,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gqozvzrj5ka3lgyouwvn,task_subcomment,NA
+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",1373026620,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_description,declined
+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 ""<p><br>"".
+
+Closing as worksforme. Please open a bug against VE if you have trouble with focusing or deleting the <br>.",1376618868,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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 <br> and so shown in VisualEditor as a ""↵"" and can be removed in-line.)",1373854399,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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",1373145121,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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.",1373102850,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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 ***",1373046915,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vjvfdsbkvnnffz3rb6r3,task_subcomment,NA
+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",1372966680,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-6yatmdhnokanuospfimc,task_description,resolved
+VisualEditor: VE's determination of image size should hook into user preferences,Related to bug 47804 too.,1372967030,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-6yatmdhnokanuospfimc,task_subcomment,NA
+VisualEditor: VE's determination of image size should hook into user preferences,"
+
+*** This bug has been marked as a duplicate of bug 50379 ***",1372966971,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-6yatmdhnokanuospfimc,task_subcomment,NA
+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",1372954140,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-rlgq63dcwusayyjqcpor,task_description,invalid
+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. :-)",1372956245,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rlgq63dcwusayyjqcpor,task_subcomment,NA
+"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",1372942020,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-5oldmu57nfk4gdllhb7z,task_description,declined
+"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.",1383280851,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5oldmu57nfk4gdllhb7z,task_subcomment,NA
+"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. :)",1372949758,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-5oldmu57nfk4gdllhb7z,task_subcomment,NA
+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",1372937460,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-qrcwbd4n7nqvsvfbykcb,task_description,resolved
+VisualEditor: Template inspector's parameter display causes smushing,"
+
+%%%*** This bug has been marked as a duplicate of bug 50728 ***%%%",1372937527,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-qrcwbd4n7nqvsvfbykcb,task_subcomment,NA
+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",1372937340,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ltzaf5hgb6yn3qi7gdwt,task_description,resolved
+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 ***",1373556875,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ltzaf5hgb6yn3qi7gdwt,task_subcomment,NA
+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.",1373556265,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-ltzaf5hgb6yn3qi7gdwt,task_subcomment,NA
+<nowiki> added to existing <nowiki> 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 <nowiki> tags around existing <nowiki> content (in this case the ""|"" symbol in the title of a cited website) inside a template inside a reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372923600,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-w3w62aq46ybywp76vzom,task_description,resolved
+<nowiki> added to existing <nowiki> content,"
+
+*** This bug has been marked as a duplicate of bug 50835 ***",1373637242,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-w3w62aq46ybywp76vzom,task_subcomment,NA
+<nowiki> added to existing <nowiki> content,"Other example:
+http://en.wikipedia.org/w/index.php?title=Beximco&diff=562685500&oldid=562676888",1372955926,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-w3w62aq46ybywp76vzom,task_subcomment,NA
+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",1372897260,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-xjgn5e55ct4mrwoaox2n,task_description,resolved
+VisualEditor: alt text?,"
+
+*** This bug has been marked as a duplicate of bug 38129 ***",1372900959,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xjgn5e55ct4mrwoaox2n,task_subcomment,NA
+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",1372875720,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-q6dmhbtud5dlan7xkm5f,task_description,resolved
+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.",1376511764,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-q6dmhbtud5dlan7xkm5f,task_subcomment,NA
+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.",1374460614,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-q6dmhbtud5dlan7xkm5f,task_subcomment,NA
+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",1372869900,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-ygke3aatutel76h64y5d,task_description,resolved
+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.,1385378094,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ygke3aatutel76h64y5d,task_subcomment,NA
+VisualEditor: Inherited category becomes explicitly invoked,Another example: https://fr.wikipedia.org/w/index.php?diff=94601807,1374255950,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-ygke3aatutel76h64y5d,task_subcomment,NA
+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",1372847760,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6tpy6ex557ljdilowdac,task_description,invalid
+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.)",1372853500,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+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.,1372853464,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+Section 0 (lede) editing does not offer VisualEditor,Can someone point me to the code that is building the VE edit section links ?,1372853398,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+Section 0 (lede) editing does not offer VisualEditor,"**wikipedia** wrote:
+
+Forwarded to:
+
+  http://en.wikipedia.org/wiki/User_talk:TheDJ#edittop.js:_VisualEditor",1372848588,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+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.",1372848358,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+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.",1372848234,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6tpy6ex557ljdilowdac,task_subcomment,NA
+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",1372842180,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gpv7ztvo3m727pmopcq7,task_description,resolved
+VisualEditor: image resizing causing implosion,"[17:29] <Excirial> 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] <Technical_13> Resolved fixed?
+[17:30] <Technical_13> !b 50651
+[17:30] <wm-bot> https://bugzilla.wikimedia.org/50651
+[17:30] <Excirial> Yes, confirmed that the problem no longer occurs.
+[17:30] <Technical_13> Kk",1373578420,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-gpv7ztvo3m727pmopcq7,task_subcomment,NA
+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 <https://test.wikipedia.org> momentarily.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1372833600,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-zr2hewhivqrgrbnvcapd,task_description,resolved
+Unify post-edit notifications on Wikimedia wikis,"**swalling** wrote:
+
+The current plan is to convert VE to use the same notification style as Extension:PostEdit previously did, now that it's been fully migrated to core (bug 48276)
+
+%%%*** This bug has been marked as a duplicate of bug 39632 ***%%%",1372834231,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zr2hewhivqrgrbnvcapd,task_subcomment,NA
+Unify post-edit notifications on Wikimedia wikis,"Created attachment 12739
+Post-edit notification using wikitext (source) editor on test.wikipedia.org
+
+**Attached**: {F11760}",1372833795,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-zr2hewhivqrgrbnvcapd,task_subcomment,NA
+Unify post-edit notifications on Wikimedia wikis,"Created attachment 12738
+Post-edit notification using VisualEditor on test.wikipedia.org, 2013-07-03
+
+**Attached**: {F11759}",1372833765,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-zr2hewhivqrgrbnvcapd,task_subcomment,NA
+VisualEditor: Still dirty refs?,"There seem to be several dirty ref sections in this diff:
+
+https://en.wikipedia.org/w/index.php?title=God_of_War_%28series%29&diff=prev&oldid=562631132
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372827600,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-odieilz34gnzoz67vumw,task_description,resolved
+VisualEditor: Still dirty refs?,"
+
+*** This bug has been marked as a duplicate of bug 48570 ***",1379613746,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-odieilz34gnzoz67vumw,task_subcomment,NA
+VisualEditor: Transclusion dialog does not handle missing parameter name,"To reproduce
+
+1. Click puzzle piece
+2. Type cn ([[Template:cn]] redirecting to [[Template:Citation needed]])
+3. Press enter twice.
+
+(I was experimenting see if there is a quick way to get out of the template dialog; this would be useful for templates like Template:cn that are commonly added without parameters).
+
+4. Type 'foo'
+5. Click 'Apply changes'
+6. It shows 'Template:Fooifsubst'
+7. Code is generated as '{{Cn| = foo}'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372810140,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-u7bebesywdz3nbtymuyr,task_description,resolved
+VisualEditor: Transclusion dialog does not handle missing parameter name,This was fixed quite some time ago; many apologies for being so slow to reply.,1385375541,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-u7bebesywdz3nbtymuyr,task_subcomment,NA
+VisualEditor: Transclusion dialog does not handle missing parameter name,"Upon re-opening it, though, it shows part_0/.",1372811272,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-u7bebesywdz3nbtymuyr,task_subcomment,NA
+VisualEditor: Transclusion dialog does not handle missing parameter name,I forgot to add: It shows part_1/ on the left where the parameter names go.,1372810279,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-u7bebesywdz3nbtymuyr,task_subcomment,NA
+"VisualEditor ""leave BETA"" dialogue jumps around, making leave hard/impossible","**Author:** `wikipedia`
+
+**Description:**
+To reproduce:
+
+1. http://en.wikipedia.org/wiki/High_Speed_2?veaction=edit&vesection=6
+2. Wait, hopefully the VisualEditor loads, and does not hang
+3. Click ""BETA""
+4. Click Leave.
+5. Try to type in this dialogue box
+
+What happens:
+
+6. The window scrolls around with each and every keypress.
+7. The Leave BETA dialogue is very hard to complete.
+
+What should happen:
+
+6. The window should not scroll
+7. The process of leaving should be easy and reliable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372794540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3nmcqmdcnvrslmvnpgyx,task_description,resolved
+"VisualEditor ""leave BETA"" dialogue jumps around, making leave hard/impossible","Sorry about this bug; we fixed it a few days ago and deployed it to the servers - merging with that report.
+
+*** This bug has been marked as a duplicate of bug 50538 ***",1373152861,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3nmcqmdcnvrslmvnpgyx,task_subcomment,NA
+"VisualEditor ""leave BETA"" dialogue jumps around, making leave hard/impossible","**wikipedia** wrote:
+
+Video of VisualEditor jumping around while typing in Leave dialogue.
+
+Third attempt at video attachment of issue (failed on creation).  Truncated with 'dd if=visual-editor-madness.ogv of=visual-editor-madness-10240kB.ogv bs=1k count=9999'
+
+**Attached**: {F11691}",1372795186,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3nmcqmdcnvrslmvnpgyx,task_subcomment,NA
+Editing sections one at a time results in editing old revisions,"When editing a section with VisualEditor the page loads and saves just fine.  However, if you next edit a different section *without refreshing the page*, VisualEditor does not recognize the version of the page you just saved as what you are editing and loads the last revision and warns you that you are editing an old revision.  This occurs in Chrome and Firefox using Windows 7 as I've tested it.
+
+From https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Editing_section_results_in_dirty_page_cache_--_have_to_reload_page_before_doing_additional_edits
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372788540,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-nptn4dym6znmjhge2meh,task_description,resolved
+Editing sections one at a time results in editing old revisions,"This is a really irritating bug, yes; sorry about this - merging with the wider report at bug 50441.
+
+*** This bug has been marked as a duplicate of bug 50441 ***",1373155391,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nptn4dym6znmjhge2meh,task_subcomment,NA
+Editing sections one at a time results in editing old revisions,"New editors are likely to edit a page, save it, have an afterthought, see this message, and panic. It just keeps on happening: experienced editors know the work-round (hit ""refresh"").
+
+Until the problem is fixed, could the error message in that pink box be amended to include ""Please click ""Cancel"" to close the editor, then reload/refresh the page, then try again. We apologise for this temporary problem and are working on a solution.""?",1372922278,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-nptn4dym6znmjhge2meh,task_subcomment,NA
+Editing sections one at a time results in editing old revisions,"It's not just after section editing: see many reports on feedback page. I edit a page in VE, save page, have an afterthought, reopen in VE, get told it's an old revision. Then cancel VE, refresh page, reopen VE, no problem. But shouldn't need to do that refresh.",1372840608,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-nptn4dym6znmjhge2meh,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?","Not sure if this is possible, but a user raises concerns about the behavior of VE opening the whole page for editing instead of editing specific sections, given that it increases the load time.
+
+See:
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562566677#edit_one_section_only
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372783680,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-3mzdvk7doccla2cgipwj,task_description,resolved
+"Can ""edit section"" be restricted to only open the single section?","Looks like it, yes!
+
+%%%*** This bug has been marked as a duplicate of bug 48429 ***%%%",1372793232,PHID-USER-gfaq55vdypjmzz6nl2kn,True,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?",Is this a dupe of bug 48429?,1372791768,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?","It also means that more bandwidth is consumed than the user asked for, which could be a problem in some cases (particularly on slow connections).
+
+On busy pages it is likely to lead to more edit conflicts, due to increased load times and encouragement to edit multiple sections.",1372791083,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?","Note that this constitutes the interface basically lying about what it's going to do, hence its disconcerting nature.",1372789295,PHID-USER-gfaq55vdypjmzz6nl2kn,True,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+"Can ""edit section"" be restricted to only open the single section?","**wikipedia** wrote:
+
+To reproduce:
+
+1. Visit a page, eg. http://en.wikipedia.org/wiki/High_Speed_2#Legal_challenges
+2. Hover over the section ""[ edit ]""
+3. Expands to ""[ edit | edit source ]"" (both with equivalent URLs)
+4. Observe that the link is: http://en.wikipedia.org/wiki/High_Speed_2?veaction=edit&vesection=6
+5. Click the link.
+
+What happens:
+
+6. The page jumps
+7. The page freezes
+8. The page is partially whited-out
+9. (If it happens to complete loading).  A massive toolbar obscures where the cursor was.
+
+What should happen:
+
+6. The page should remain exactly where it was, it should not move
+7. The page should remain interactive
+8. The page should remain readable
+9. The editor (visual or textedit) should correspond to only that section.",1372784238,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-3mzdvk7doccla2cgipwj,task_subcomment,NA
+VisualEditor: warn on markup.,"Similar to bugs 50093 and 50527; users need to be warned when they're using markup in the VE. This is a source of a pretty large amount of corruption on enwiki, and I'm not sure how sustainable the community's patience for that is.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372768500,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k3ijb4t7vtqm2fvl7dqa,task_description,resolved
+VisualEditor: warn on markup.,"
+
+%%%*** This bug has been marked as a duplicate of bug 49820 ***%%%",1372859187,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k3ijb4t7vtqm2fvl7dqa,task_subcomment,NA
+VisualEditor: warn on markup.,I strongly advise that this be made pretty high-priority (See above).,1372782236,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k3ijb4t7vtqm2fvl7dqa,task_subcomment,NA
+Infobox template shows HTML,"**Author:** `warnckew`
+
+**Description:**
+Screenshot showing infobox DIV HTML code
+
+Launching VisualEditor to edit http://en.wikipedia.org/w/index.php?title=United_Nations_Security_Council_Resolution_1693&oldid=541044487 makes the heading of the infobox show some unexpected HTML contents, as shown in the attached browser screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11621}",1372759800,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-u4b7k3vc55d23eoi7lfv,task_description,resolved
+Infobox template shows HTML,"This is the same as bug 50366 - merging with that one.
+
+*** This bug has been marked as a duplicate of bug 50366 ***",1372781074,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u4b7k3vc55d23eoi7lfv,task_subcomment,NA
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,"I have noticed an unexpected behavior while tesing Visual Editor with Malayalam Wikipedia. Describing the steps below:-
+
+1. Added the following text on a page
+
+ഡിസ്രയേലി
+
+2. When pressing a backspace immediately after the above text, it becomes
+
+ഡസരയ
+
+ie. many characters in between the original text disappeared. The expected result was ഡിസ്രയേ
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows 7
+**Platform**: PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50507",1372759140,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_description,declined
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,Now the problem has been solved. You may mark this bug as resolved.,1374044144,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,"(In reply to comment #1)
+> @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",1373267447,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+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.",1373135312,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,Browser was Firefox 22.,1373134659,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+VisualEditor: Bad typing/backspacing behaviour for Malayalam,@vssun: Any specific browser? Can't reproduce it in Chrome.,1373134158,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-ppoinlj2eyh5xj7jyhin,task_subcomment,NA
+"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",1372746900,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-zu3q7ugqbcdtlalzbdir,task_description,resolved
+"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 ***",1372747009,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zu3q7ugqbcdtlalzbdir,task_subcomment,NA
+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",1372741440,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-c67owxdoizewmtq2qqq2,task_description,resolved
+VisualEditor: Likely round-trip failure involving categories and transclusion content on [[Michala Petri]],"
+
+*** This bug has been marked as a duplicate of bug 50120 ***",1373484208,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-c67owxdoizewmtq2qqq2,task_subcomment,NA
+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",1372742420,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-c67owxdoizewmtq2qqq2,task_subcomment,NA
+"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",1372740840,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-xzt7v3b2ore2q4iogeui,task_description,resolved
+"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.,1374878989,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xzt7v3b2ore2q4iogeui,task_subcomment,NA
+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",1372737300,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-i5l4tj3jbqlfjjgj2xtx,task_description,resolved
+VisualEditor: Likely ref / transclusion round-trip failure,Fixed in Roan's DOM dirtying fixes drive in July.,1385375352,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i5l4tj3jbqlfjjgj2xtx,task_subcomment,NA
+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?",1373928755,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-i5l4tj3jbqlfjjgj2xtx,task_subcomment,NA
+VisualEditor: Likely ref / transclusion round-trip failure,Only difference is the removal of two spaces after equals signs.,1373894262,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-i5l4tj3jbqlfjjgj2xtx,task_subcomment,NA
+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",1372723860,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5jyjadx572ehzjtstm2i,task_description,resolved
+VisualEditor: Feedback form moves and jerks the screen around,*** Bug 50533 has been marked as a duplicate of this bug. ***,1385375230,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+VisualEditor: Feedback form moves and jerks the screen around,*** Bug 50602 has been marked as a duplicate of this bug. ***,1373152861,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+VisualEditor: Feedback form moves and jerks the screen around,Sorry about this bug; we've fixed this and just deployed it live.,1372894536,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+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",1372890609,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+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",1372874494,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+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.",1372834749,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+VisualEditor: Feedback form moves and jerks the screen around,This sounds really unhelpful; sorry about this.,1372726074,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5jyjadx572ehzjtstm2i,task_subcomment,NA
+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 <input> 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",1372716720,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-gm7mlj7ylnonhtpcmhmc,task_description,resolved
+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",1375115733,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gm7mlj7ylnonhtpcmhmc,task_subcomment,NA
+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",1373190428,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gm7mlj7ylnonhtpcmhmc,task_subcomment,NA
+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';",1373020498,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-gm7mlj7ylnonhtpcmhmc,task_subcomment,NA
+Tagging articles using old markup on VE,"I note that if an editor uses old markup in VE (like [[link]]), it gets enclosed in <nowiki> 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",1372715580,PHID-USER-65pjzcmoby2fsgzdrfjq,False,PHID-TASK-tndk34qrdqsecj3chsun,task_description,declined
+Tagging articles using old markup on VE,"**nykevin.norris** wrote:
+
+Removing self from CC.  Tired of spam.  Bug is dead, people.",1375295445,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375295294,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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!",1375293668,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375290243,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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?",1375287296,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375286688,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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).",1375259183,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375257056,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.""",1375214654,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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 <nowiki> 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.",1375209327,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375203199,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+Tagging articles using old markup on VE,"(In reply to comment #10)
+> (In reply to comment #7)
+> > Adding a <nowiki> 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? :-)",1375203157,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+Tagging articles using old markup on VE,"**kwwilliams** wrote:
+
+(In reply to comment #7)
+> Adding a <nowiki> 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.",1375202701,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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 <nowiki> 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...",1375202572,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375202406,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+Tagging articles using old markup on VE,"**nykevin.norris** wrote:
+
+Adding a <nowiki> 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.",1375201973,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1375201659,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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 <nowiki> 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.",1375200134,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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",1373826928,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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",1373475389,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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.",1372941268,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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",1372870715,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tndk34qrdqsecj3chsun,task_subcomment,NA
+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",1372714740,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-i6cv3vliogwuderqbjnw,task_description,invalid
+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.",1374878756,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-i6cv3vliogwuderqbjnw,task_subcomment,NA
+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.,1372714830,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-i6cv3vliogwuderqbjnw,task_subcomment,NA
+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",1372712700,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-y2smkmxkc74umzi22ziq,task_description,resolved
+Ghost references in VisualEditor?,"Yes, same issue as bug 50380.
+
+*** This bug has been marked as a duplicate of bug 50380 ***",1385375005,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-y2smkmxkc74umzi22ziq,task_subcomment,NA
+Ghost references in VisualEditor?,"I cant reproduce this using the example given.
+
+It looks like this may be a dup of bug 50380.",1373758575,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-y2smkmxkc74umzi22ziq,task_subcomment,NA
+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",1372711380,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-devcsvnwd5brcea5luka,task_description,resolved
+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 ***",1374079583,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-devcsvnwd5brcea5luka,task_subcomment,NA
+VisualEditor: Deleting all content removes input marker,Is this the same as Bug 50947 and/or Bug 51169?,1374077413,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-devcsvnwd5brcea5luka,task_subcomment,NA
+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",1372699740,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-p2n3tks426uods6v37cf,task_description,declined
+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.,1373996005,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-p2n3tks426uods6v37cf,task_subcomment,NA
+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}",1372613820,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-wf4a2uikjvfox37upsq3,task_description,declined
+VisualEditor: thick line appearing,"Created attachment 13766
+No thick line
+
+**Attached**: {F11386}",1384204317,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wf4a2uikjvfox37upsq3,task_subcomment,NA
+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.",1384204280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wf4a2uikjvfox37upsq3,task_subcomment,NA
+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}",1372613700,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yaappft5pc7quebc2sf7,task_description,resolved
+VisualEditor: Text wrongly being given pre-formatted format,Fixed for some time due to changes in Parsoid. Sorry for the slowness of updating.,1385374964,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yaappft5pc7quebc2sf7,task_subcomment,NA
+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",1372612740,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-4i77geu65qzvj7wexwob,task_description,resolved
+VisualEditor: Links created in the userspace are treated as links to subpages,"
+
+*** This bug has been marked as a duplicate of bug 48915 ***",1377445192,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4i77geu65qzvj7wexwob,task_subcomment,NA
+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",1372608360,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-my7qaki5z5rpjdhjrelx,task_description,resolved
+VisualEditor: Error saving data to server: Failed request: error.,"Performance issue, fixed some time ago; sorry for slowness in replying.",1385375109,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-my7qaki5z5rpjdhjrelx,task_subcomment,NA
+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",1372757474,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-my7qaki5z5rpjdhjrelx,task_subcomment,NA
+"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",1372595400,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-tb4dfoj5ivzds3d5vjbf,task_description,resolved
+"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 ***",1373852659,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tb4dfoj5ivzds3d5vjbf,task_subcomment,NA
+"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)",1373239841,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-tb4dfoj5ivzds3d5vjbf,task_subcomment,NA
+"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)",1372978408,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-tb4dfoj5ivzds3d5vjbf,task_subcomment,NA
+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}",1372595100,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-adbbasada34enlaaq6ns,task_description,resolved
+VisualEditor: Insert media dialog is borked,"
+
+*** This bug has been marked as a duplicate of bug 50471 ***",1372620610,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-adbbasada34enlaaq6ns,task_subcomment,NA
+"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 (&#124; -> <nowiki>|</nowiki>) in a section of the page I didn't edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372548840,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-qzi73sz5voocgvogf6kk,task_description,resolved
+"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…,1385380712,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qzi73sz5voocgvogf6kk,task_subcomment,NA
+Preserve wiki link href with ././ prefix,"The following HTML does not seem to properly round-trip through VE:
+
+<p><a rel=""mw:WikiLink"" href=""././Foo"">./Foo</a></p>
+
+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",1372526940,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-q22fxzgily436ad4iq5g,task_description,declined
+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",1372920044,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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.,1372887258,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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.",1372882310,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+Preserve wiki link href with ././ prefix,"It worked at http://en.wikipedia.org/wiki/User:Catrope/Shrek?veaction=edit though, so closing as working.",1372880388,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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",1372821570,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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",1372527319,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-q22fxzgily436ad4iq5g,task_subcomment,NA
+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",1372513920,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-mystbxhb36nxyv6pxcfr,task_description,resolved
+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 ***",1373407947,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mystbxhb36nxyv6pxcfr,task_subcomment,NA
+Feature request: permit copy-paste of templates from history,"I believe Maggie means copying the VisualEditor representation of a template, not copying wikitext.",1373407882,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-mystbxhb36nxyv6pxcfr,task_subcomment,NA
+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 <nowiki> 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.",1372805568,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-mystbxhb36nxyv6pxcfr,task_subcomment,NA
+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",1372507500,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-dwm6neygnm5atdz5p2ls,task_description,resolved
+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.",1384945237,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dwm6neygnm5atdz5p2ls,task_subcomment,NA
+VisualEditor: Backspace from header line into empty paragraph changes header format into paragraph,"Sorry: I should have said ""Backspace"", not ""Delete"".",1372508092,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-dwm6neygnm5atdz5p2ls,task_subcomment,NA
+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 <anonymous function: ve.copyDomElements>(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 <anonymous function: ve.copyDomElements>(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 <anonymous function: ve.ce.GeneratedContentNode.prototype.onUpdate>() 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 <anonymous function: ve.Factory.prototype.create>(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 <anonymous function: ve.ce.BranchNode.prototype.onSplice>(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 [<span...>, <dl...>] on Firefox. Since `index` is not undefined, this would indicate some sort of an internal inconsistency.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372507500,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_description,resolved
+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",1372556851,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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",1372510944,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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.,1372509962,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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.",1372509277,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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.",1372508815,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+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.",1372508473,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-am2tq4ttmt7ojewwkmyp,task_subcomment,NA
+"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",1372498200,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jp6ugl4t75zwxp4yb5dw,task_description,resolved
+"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 ***",1372500786,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-jp6ugl4t75zwxp4yb5dw,task_subcomment,NA
+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",1372436400,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-fxdptzpzjvmxdqfbxpig,task_description,resolved
+VisualEditor: massively duplicating references on render,*** Bug 50521 has been marked as a duplicate of this bug. ***,1385375005,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fxdptzpzjvmxdqfbxpig,task_subcomment,NA
+VisualEditor: massively duplicating references on render,Fixed a few months ago; sorry for late reply.,1383410182,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fxdptzpzjvmxdqfbxpig,task_subcomment,NA
+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)",1373758524,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-fxdptzpzjvmxdqfbxpig,task_subcomment,NA
+"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}",1372416960,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-rlct7v5aitn3wet7l6e6,task_description,resolved
+"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 ***",1372417299,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-rlct7v5aitn3wet7l6e6,task_subcomment,NA
+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}",1372414740,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-cbgrzxh5jpcsxgl5p5xy,task_description,resolved
+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 ***",1372690696,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cbgrzxh5jpcsxgl5p5xy,task_subcomment,NA
+"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",1372414500,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-smzjavkfcebgjqkdtqrx,task_description,resolved
+"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 ***",1373663953,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-smzjavkfcebgjqkdtqrx,task_subcomment,NA
+"VisualEditor: Can't drag and drop transclusions, text, references","While for text there's 49981 open, itwp users also request this for templates.",1373663530,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-smzjavkfcebgjqkdtqrx,task_subcomment,NA
+VisualEditor throws <nowiki> 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 <nowiki> tags like this:
+
+<nowiki>[Square brackets]</nowiki>
+
+<nowiki>[...]</nowiki>
+
+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 <nowiki> tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T54268}",1372374900,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-trv3cartgmv24xouxumz,task_description,resolved
+VisualEditor throws <nowiki> 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.",1372777003,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-trv3cartgmv24xouxumz,task_subcomment,NA
+VisualEditor throws <nowiki> 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.",1372756630,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-trv3cartgmv24xouxumz,task_subcomment,NA
+VisualEditor throws <nowiki> 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.",1372748767,PHID-USER-wswkm7jrcwes3tc7o34k,False,PHID-TASK-trv3cartgmv24xouxumz,task_subcomment,NA
+VisualEditor throws <nowiki> 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.,1372744432,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-trv3cartgmv24xouxumz,task_subcomment,NA
+VisualEditor: Cutting the text of a header leaves a blank header line behind,"Fairly self-explanatory.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372359060,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-lorkde4zqpoazowbiim6,task_description,resolved
+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 ***",1373154763,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lorkde4zqpoazowbiim6,task_subcomment,NA
+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?",1372853616,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-lorkde4zqpoazowbiim6,task_subcomment,NA
+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",1372358460,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ymkat6i32jrdnouhpmiw,task_description,invalid
+VisualEditor: edit link on the history page needs updating,"How very strange. Slightly slower loading time giving a false impression, probably; thanks :).",1372364368,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ymkat6i32jrdnouhpmiw,task_subcomment,NA
+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. :-)",1372364187,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ymkat6i32jrdnouhpmiw,task_subcomment,NA
+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}",1372348860,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-vthqyhkr4mcwanonthu2,task_description,resolved
+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}",1373854867,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vthqyhkr4mcwanonthu2,task_subcomment,NA
+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}",1372346160,PHID-USER-az3b22hiqzlaov5l2efk,False,PHID-TASK-mfexrt4v3gjwo4jczoeu,task_description,resolved
+ULS doesn't work while using VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 49569 ***",1372351064,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-mfexrt4v3gjwo4jczoeu,task_subcomment,NA
+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",1372344540,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bklb3mjjhzmtwofxaf4c,task_description,resolved
+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 ***",1373852602,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bklb3mjjhzmtwofxaf4c,task_subcomment,NA
+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 <ref>Jones (2003) p.23</ref> 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",1372337880,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-3b3ojih2e7wkq7l3upwi,task_description,resolved
+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 ***",1373851094,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3b3ojih2e7wkq7l3upwi,task_subcomment,NA
+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",1372331040,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-o7g3xrsatafdlookojvh,task_description,resolved
+VisualEditor: Page settings dialog adds categories with [[:Category:xyz]] syntax,"This was a Parsoid bug, since fixed.",1372435698,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-o7g3xrsatafdlookojvh,task_subcomment,NA
+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}",1372329960,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-6a4gkdcnicitblhp6cug,task_description,resolved
+VisualEditor: Toolbar obscures save dialog when scrolled down the page,"
+
+*** This bug has been marked as a duplicate of bug 50324 ***",1372387036,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-6a4gkdcnicitblhp6cug,task_subcomment,NA
+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",1372301820,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mgc6io5oxbkpzoctvybg,task_description,resolved
+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 ***",1373520752,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mgc6io5oxbkpzoctvybg,task_subcomment,NA
+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",1372280520,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-ytqjgzoe2nidan525q6p,task_description,resolved
+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 ***",1372284454,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ytqjgzoe2nidan525q6p,task_subcomment,NA
+Unwanted Removal of text formatting,Duplicated here: http://test.wikipedia.org/w/index.php?title=VisualEditor%3ATestingGrounds&diff=174932&oldid=174931,1372283768,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-ytqjgzoe2nidan525q6p,task_subcomment,NA
+'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",1372269540,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-44radwd6pkgnkplpyiul,task_description,invalid
+'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.",1372270000,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-44radwd6pkgnkplpyiul,task_subcomment,NA
+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",1372269480,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_description,declined
+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?",1404150917,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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.",1383053606,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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.",1378387791,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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)?",1378357656,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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.",1378356625,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+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.",1378356406,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+screen doesn't work from within 'become',"According to <https://wiki.toolserver.org/view/Multi-maintainer_projects#Using_screen>, 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?",1378355120,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+screen doesn't work from within 'become',"Then you almost certainly* remember incorrectly.  Screen can only operate on the terminal you are connected to (obviously), and that is necessarily owned by the user you have logged in with.
+
+Chances are this scenario (start a screen session /after/ having switched to another user) would have been less common on toolserver since most people ran only as their login user except for the infrequent multi-maintainer project -- which all projects are in Tool Labs.
+
+* (I say almost here because it /is/ possible to set screen suid to root; but that's on the same list as ""chmod 777 your home"", ""set your password to '1234'"", or ""allow telnet"" -- something a user might find convenient but a sysadmin should be fired for).",1378354665,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+screen doesn't work from within 'become',"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
+Cannot open your terminal '/dev/pts/50' - please check.
+
+I kept getting this. I checked <https://wikitech.wikimedia.org/wiki/Screen> 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.",1378349685,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+screen doesn't work from within 'become',"That's a limitation on how screen functions (i.e., it needs to have ownership of the terminal, which only the actual login process grants); sudo cannot circumvent this as it does not alter tty permissions.
+
+While it's a little annoying, the workaround you describe provides full functionality during interactive sessions (and it bears reminding here that tools should not be running interactive processes in detached screen sessions in any case).",1372269706,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-th6xciyktmum2yvdvsqy,task_subcomment,NA
+VisualEditor: Dialogs won't open after adding a template at the end of the page,"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.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372263600,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-alyz2tg2s4hlxhbv3yqa,task_description,resolved
+VisualEditor: Dialogs won't open after adding a template at the end of the page,"(In reply to comment #1)
+> (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 ***",1372271165,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-alyz2tg2s4hlxhbv3yqa,task_subcomment,NA
+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.",1372269533,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-alyz2tg2s4hlxhbv3yqa,task_subcomment,NA
+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",1372252500,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bcsg2progke55h2rhst6,task_description,resolved
+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.",1372864641,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bcsg2progke55h2rhst6,task_subcomment,NA
+VisualEditor not working due to unflushed ResourceLoader cache?,I assume this is obsolete now?,1372846999,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bcsg2progke55h2rhst6,task_subcomment,NA
+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.)",1372266477,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bcsg2progke55h2rhst6,task_subcomment,NA
+VisualEditor: Extra bullet point before template containing bulleted list,"VE rendering of [[WUEC#External_links]] does not match MW rendering.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372230840,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-7ma6pcpqiiyq3gvijprg,task_description,invalid
+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).",1372295480,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7ma6pcpqiiyq3gvijprg,task_subcomment,NA
+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}",1372228380,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-sgceljbbtlgbbpr3bdfh,task_description,resolved
+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 ***",1373164008,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sgceljbbtlgbbpr3bdfh,task_subcomment,NA
+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}",1372227660,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-z2wr7yxi5vylreuzml56,task_description,resolved
+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.",1373163131,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z2wr7yxi5vylreuzml56,task_subcomment,NA
+VisualEditor: Image size parameter with spaces is ignored,"See [[testwiki:VisualEditor:Little or big]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372216200,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-6xivramwe724jwphgukh,task_description,resolved
+VisualEditor: Image size parameter with spaces is ignored,"
+
+*** This bug has been marked as a duplicate of bug 49696 ***",1372216311,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6xivramwe724jwphgukh,task_subcomment,NA
+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",1372206060,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_description,resolved
+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 |
++---------------------+----------+",1374273514,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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.",1374090128,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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"";",1373589867,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+Logging broken for GettingStarted (page-save-success logged as page-impression),*** Bug 51208 has been marked as a duplicate of this bug. ***,1373589755,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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.",1372823275,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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",1372822882,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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",1372740115,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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].",1372739582,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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.",1372275305,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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. ;)",1372268511,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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.",1372208974,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-q3v5q4q6bifjgxghffaq,task_subcomment,NA
+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",1372172160,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-txtftm3ohgrpjqzazgnp,task_description,resolved
+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 ***",1373162765,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-txtftm3ohgrpjqzazgnp,task_subcomment,NA
+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",1372159200,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-yllnjqjrkuliux5dxtws,task_description,resolved
+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 ***",1373162663,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yllnjqjrkuliux5dxtws,task_subcomment,NA
+"<nowiki> tags added to (valid) list in a template parameter, corrupting them","In general,
+
+{{foo
+bar = 
+* 1
+* 2
+* 3
+}}
+
+… is RT'ing to 
+
+{{foo
+bar = <nowiki>* 1
+* 2
+* 3</nowiki>
+}}
+
+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",1372125540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bfsjo6ol2jmfu3gdf4ch,task_description,resolved
+"<nowiki> tags added to (valid) list in a template parameter, corrupting them","
+
+*** This bug has been marked as a duplicate of bug 50144 ***",1372127067,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-bfsjo6ol2jmfu3gdf4ch,task_subcomment,NA
+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",1372121400,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-tn6apoz6stp2eozgwscp,task_description,resolved
+Missing root git config file when cloning,[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.],1378939564,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-tn6apoz6stp2eozgwscp,task_subcomment,NA
+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.",1373095093,PHID-USER-r7wrkcx7j2vutqs6hr3g,True,PHID-TASK-tn6apoz6stp2eozgwscp,task_subcomment,NA
+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",1372480935,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tn6apoz6stp2eozgwscp,task_subcomment,NA
+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.",1372474317,PHID-USER-gbl4hfak3cfurt3c7skd,True,PHID-TASK-tn6apoz6stp2eozgwscp,task_subcomment,NA
+"Images: Frameless images should not emit the ""caption"" as a <figcaption> 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 <figcaption> 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 <figcaption>s for these as part of bug 50113, but Parsoid should fix these in due course.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372119780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dyhspvuz6dvlmjei7r7v,task_description,invalid
+"Images: Frameless images should not emit the ""caption"" as a <figcaption> 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],1372934057,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-dyhspvuz6dvlmjei7r7v,task_subcomment,NA
+"Images: Frameless images should not emit the ""caption"" as a <figcaption> even when it's set",This is by design. See http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images for documentation and rationales.,1372121678,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-dyhspvuz6dvlmjei7r7v,task_subcomment,NA
+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",1372095840,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dgi4ucdvhwjzbauoa7td,task_description,resolved
+VisualEditor adding spurious pipe separators to image syntax,"
+
+*** This bug has been marked as a duplicate of bug 50012 ***",1372096490,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dgi4ucdvhwjzbauoa7td,task_subcomment,NA
+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.",1372095892,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dgi4ucdvhwjzbauoa7td,task_subcomment,NA
+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<ref>{{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}}</ref>
+
+to...
+
+* Winner, Magenta Foundation award<ref>{{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}}</ref>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372088640,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_description,invalid
+VisualEditor template parameter normalization results in dirty diffs,"Closing ""bugs"" which consist of multiple issues.",1373163467,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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,1372107875,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Ivan_Tan&curid=39767321&diff=561408770&oldid=561406619,1372104798,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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.",1372104345,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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",1372104272,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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,1372102659,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Kamelot&curid=1161493&diff=561402036&oldid=560661945,1372102018,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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 ***",1372101714,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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,1372100288,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Dan_Penteado&curid=13006822&diff=561396894&oldid=561392351,1372099355,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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,1372099302,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=MTV&curid=18856&diff=561395466&oldid=561389102,1372098643,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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",1372098386,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,https://en.wikipedia.org/w/index.php?title=Wild_Pack&curid=29143457&diff=561394555&oldid=561394449,1372098360,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+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",1372096583,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor template parameter normalization results in dirty diffs,"
+
+*** This bug has been marked as a duplicate of bug 50066 ***",1372091701,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k43bzyrhgig4srkamrde,task_subcomment,NA
+VisualEditor ref weirdness,"https://en.wikipedia.org/w/index.php?title=Laura_Pannack&diff=561336738&oldid=557984097
+
+<ref name=""telegraph""/> --> <ref name=""telegraph""></ref>
+
+Weird.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372088340,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-jvpgelxqydhjqfkhkgas,task_description,resolved
+VisualEditor ref weirdness,https://en.wikipedia.org/w/index.php?title=Save_Rock_and_Roll&curid=38419944&diff=561416388&oldid=561387755,1372107851,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-jvpgelxqydhjqfkhkgas,task_subcomment,NA
+VisualEditor ref weirdness,https://en.wikipedia.org/w/index.php?title=Daniel_Kahneman&curid=165492&diff=561411461&oldid=560179630,1372106999,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-jvpgelxqydhjqfkhkgas,task_subcomment,NA
+VisualEditor ref weirdness,"
+
+*** This bug has been marked as a duplicate of bug 50066 ***",1372091672,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jvpgelxqydhjqfkhkgas,task_subcomment,NA
+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",1372086060,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dmz6g3cracqeyd3hxrar,task_description,invalid
+VisualEditor spurious attribute normalization (resulting in dirty diffs),"Closing ""bugs"" which consist of multiple issues.",1373163469,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dmz6g3cracqeyd3hxrar,task_subcomment,NA
+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",1372097247,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dmz6g3cracqeyd3hxrar,task_subcomment,NA
+VisualEditor spurious attribute normalization (resulting in dirty diffs),"
+
+*** This bug has been marked as a duplicate of bug 50066 ***",1372091521,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dmz6g3cracqeyd3hxrar,task_subcomment,NA
+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",1372085520,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-4c7jfgdvdgsa7tz3aom4,task_description,resolved
+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 ***",1372091385,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4c7jfgdvdgsa7tz3aom4,task_subcomment,NA
+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<len;
+        i++){
+
+I tried to get a better output using debug=true, but this seems to totally break VE (in IE10 at least).
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F11482}",1372059000,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-efd5wnljemqy75ubgwoi,task_description,resolved
+VisualEditor: Impossible to review or save changes in IE10,"This is bug 49187 (and yes, it's critical, hence we've re-blacklisted IE until we can get this fixed). :-(
+
+(IE has a hard limit on how many scripts it will take for a given page; debug=true suspends ResourceLoader, meaning all ~200 VE files come individually - along with the dozens of non-VE MW scripts - which IE ignores after the first ten or so, breaking everything. This is a known IE-is-terrible bug.)
+
+*** This bug has been marked as a duplicate of bug 49187 ***",1372084871,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-efd5wnljemqy75ubgwoi,task_subcomment,NA
+VisualEditor: Impossible to review or save changes in IE10,It's also impossible to save the page; same script error occurs. Upping to critical.,1372059463,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-efd5wnljemqy75ubgwoi,task_subcomment,NA
+VisualEditor: still making unrelated modifications,"See https://en.wikipedia.org/w/index.php?title=Royal_Lancaster_Infirmary&diff=561254127&oldid=560972172 for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372037520,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jazdgxdcnzvf2vvkoqay,task_description,resolved
+VisualEditor: still making unrelated modifications,This is still happening: https://en.wikipedia.org/w/index.php?title=Genie_%28feral_child%29&diff=564429158&oldid=564425048 Can you please check? Thanks.,1373984013,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-jazdgxdcnzvf2vvkoqay,task_subcomment,NA
+VisualEditor: still making unrelated modifications,"This particular one is (entirely cryptically) bug 50066, which is going to be fixed in the next few minutes and deployed tomorrow morning PDT.
+
+*** This bug has been marked as a duplicate of bug 50066 ***",1372039230,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jazdgxdcnzvf2vvkoqay,task_subcomment,NA
+"VisualEditor: ""read"" version after save page not picking up on category removals","If a user hits edit, removes a category and saves, the read-only article they're then presented with still includes the old category - or at least, does on https://en.wikipedia.org/wiki/Sumali
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372034880,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ndrderb5cpy5obe7r7so,task_description,resolved
+"VisualEditor: ""read"" version after save page not picking up on category removals","
+
+*** This bug has been marked as a duplicate of bug 48560 ***",1372036218,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ndrderb5cpy5obe7r7so,task_subcomment,NA
+VisualEditor saves HTML instead of wikitext,"In the following edit, VE saved the internal page representation instead of the wikitext:
+
+https://nl.wikipedia.org/w/index.php?title=Eurosong&diff=prev&oldid=38007082
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371986640,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-2nhg6abdnwgx5uutzfus,task_description,resolved
+VisualEditor saves HTML instead of wikitext,"This was due to the caches being mis-configured; really sorry about this issue.
+
+*** This bug has been marked as a duplicate of bug 49577 ***",1372004983,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2nhg6abdnwgx5uutzfus,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,"When viewing [[testwiki:Visualeditor_image_captions]] in VE, the images cannot be seen. They are still ""known"" though - they don't vanish on save.
+
+(My testing of this issue led to the filing of bug 50008, but the issue there seems to have gone away now. However, this one is still showing up for me, so I think this is a separate bug.
+
+Please close this bug if it turns out to have fixed itself.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371972060,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-k4lzd6fndz3snhg24las,task_description,resolved
+Images turned into mw:Placeholder in certain cases,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934068,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,"
+
+*** This bug has been marked as a duplicate of bug 48900 ***",1372104211,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,Related: Bug 48900,1372006246,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,*** Bug 50008 has been marked as a duplicate of this bug. ***,1372003922,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Images turned into mw:Placeholder in certain cases,"This is because Parsoid is converting the images to placeholders for some reason: http://parsoid.wmflabs.org/mw/User:Catrope/Bug_50035
+
+Moving to Parsoid",1371972510,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-k4lzd6fndz3snhg24las,task_subcomment,NA
+Jenkins: Provide build status images,"Assuming we do not yet have something like this, it'd be awesome if this Jenkins plugin could be installed:
+
+https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin
+
+I want to be able to embed such a build status image on some website.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1371912840,PHID-USER-mye6umixnhfo7lhpgzmj,False,PHID-TASK-fa3dg2ag3ccgjplogzop,task_description,resolved
+Jenkins: Provide build status images,"I have installed the plugin and restarted Jenkins. Please try it out, if it does not work simply reopen this bug :)",1372235730,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-fa3dg2ag3ccgjplogzop,task_subcomment,NA
+Jenkins: Provide build status images,"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:
+
+
+Configured Pipeline Manager postmerge
+Events:
+  <EventFilter types: change-merged>
+Projects:
+  mediawiki/extensions/VisualEditor
+    <Job mwext-VisualEditor-doc-publish> ^master$
+  operations/mediawiki-config
+    <Job beta-mediawiki-config-update> ^master$ 
+  test/mediawiki
+    <Job test-mediawiki-docgen>
+  analytics/wikistats
+    <Job analytics-wikistats>
+  analytics/udp-filters
+    <Job analytics-udp-filters>
+  operations/puppet
+    <Job operations-puppet-doc>
+  analytics/webstatscollector
+    <Job analytics-webstatscollector>
+  analytics/libanon
+    <Job analytics-libanon>
+  mediawiki/extensions/Parsoid
+    <Job parsoid-regressions>
+  mediawiki/core
+    <Job mediawiki-core-jslint> (?!REL1_19)^(\.jshint|.*\.(js|json)$)
+    <Job mediawiki-core-lint>
+    <Job mediawiki-core-jsduck-publish> ^(REL1_21|master)$^.*\.(js|json)$
+    <Job mediawiki-core-regression-master> ^master$
+    <Job mediawiki-core-regression-REL1_19> ^REL1_19$
+    <Job mediawiki-core-regression-REL1_20> ^REL1_20$
+    <Job mediawiki-core-regression-REL1_21> ^REL1_21
+    <Job mediawiki-core-regression-phpcs-HEAD>
+    <Job mediawiki-core-doxygen-publish>   
+  mediawiki/extensions/Math
+    <Job beta-recompile-math-texvc>
+  integration/docroot
+    <Job integration-docroot-deploy> ^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.",1372012020,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-fa3dg2ag3ccgjplogzop,task_subcomment,NA
+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.",1371986909,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fa3dg2ag3ccgjplogzop,task_subcomment,NA
+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.",1371986368,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fa3dg2ag3ccgjplogzop,task_subcomment,NA
+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",1371911220,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-ljxem5cmodalpwa72kg4,task_description,invalid
+Parametr adds =,"But anyway, thx for explanation and sorry for disturbing!",1373174465,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-ljxem5cmodalpwa72kg4,task_subcomment,NA
+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""?",1373174438,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-ljxem5cmodalpwa72kg4,task_subcomment,NA
+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 (<visualeditor-parameter-input-placeholder>) 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. :-(",1373161574,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ljxem5cmodalpwa72kg4,task_subcomment,NA
+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",1371898920,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-wvgg7vhdge7chox3fyjo,task_description,resolved
+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 ***",1371969869,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wvgg7vhdge7chox3fyjo,task_subcomment,NA
+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",1371855780,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-c3wbsdob4ioii2vvg62w,task_description,resolved
+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 ***",1371855868,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c3wbsdob4ioii2vvg62w,task_subcomment,NA
+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",1371854820,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-7ahnfikr3ud3nwuglytr,task_description,resolved
+VisualEditor: Insecure image links on https,"
+
+*** This bug has been marked as a duplicate of bug 43015 ***",1371855005,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7ahnfikr3ud3nwuglytr,task_subcomment,NA
+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}",1371825480,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-wzimuyoyzpmwzhvmicic,task_description,invalid
+VisualEditor: not functioning on it.wiki,"Cool; marking as resolved. I'd suggest speaking to the QE author quickfast, then :D.",1371828173,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-wzimuyoyzpmwzhvmicic,task_subcomment,NA
+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",1371827387,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wzimuyoyzpmwzhvmicic,task_subcomment,NA
+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.",1371825766,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wzimuyoyzpmwzhvmicic,task_subcomment,NA
+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",1371805320,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-btez3p46ypsfjdbg3yny,task_description,resolved
+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 ***",1371827708,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-btez3p46ypsfjdbg3yny,task_subcomment,NA
+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",1371798000,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-gd5v26ccraeduoxxlbju,task_description,resolved
+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],1372934049,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gd5v26ccraeduoxxlbju,task_subcomment,NA
+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 ***",1371829646,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gd5v26ccraeduoxxlbju,task_subcomment,NA
+VisualEditor translates templates into Uzbek language,Looks like a Parsoid caching issue: bug 49411 again?,1371812835,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-gd5v26ccraeduoxxlbju,task_subcomment,NA
+"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}",1371771480,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pfavb4dwppjl5cul5xfr,task_description,resolved
+"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 ***",1371771658,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-pfavb4dwppjl5cul5xfr,task_subcomment,NA
+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",1371748800,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_description,resolved
+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],1372933999,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_subcomment,NA
+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 ***",1371769152,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_subcomment,NA
+Parsoid: full sized images are displayed regardless of a |pictured parameter,"Aha,",1371751846,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_subcomment,NA
+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.",1371751628,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-dgmfpphgdhqlrv3bwalq,task_subcomment,NA
+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",1371738780,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-gt3d3w3roul5snkreii4,task_description,resolved
+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 ***",1371774369,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gt3d3w3roul5snkreii4,task_subcomment,NA
+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",1371654120,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-cttjkncimnkmzpg2rgta,task_description,resolved
+Existing image inclusions are duplicated and truncated by VisualEditor,"This is 49729.
+
+*** This bug has been marked as a duplicate of bug 49729 ***",1371721408,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cttjkncimnkmzpg2rgta,task_subcomment,NA
+Existing image inclusions are duplicated and truncated by VisualEditor,"(sorry, just saw the first edit.)",1371659331,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-cttjkncimnkmzpg2rgta,task_subcomment,NA
+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,1371659142,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-cttjkncimnkmzpg2rgta,task_subcomment,NA
+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",1371645900,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-u5v4rso2epl4jpiezw4u,task_description,resolved
+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],1372934053,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-u5v4rso2epl4jpiezw4u,task_subcomment,NA
+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 ***",1371660571,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u5v4rso2epl4jpiezw4u,task_subcomment,NA
+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",1371633600,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-b7f2axjx5q6kogc6seqp,task_description,declined
+VisualEditor: IE8 support,Great! Thanks.,1371658981,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+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)",1371658853,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+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"".",1371657906,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+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.",1371656351,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+VisualEditor: IE8 support,That's an en_INTERNET idiom. Do you want me to sic the internationalisation team on you? Cuz I will.,1371650531,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+VisualEditor: IE8 support,Kill it with fire!,1371650457,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-b7f2axjx5q6kogc6seqp,task_subcomment,NA
+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",1371612300,PHID-USER-ixwg3kf22idjy7x4ncxf,False,PHID-TASK-2mi7knu2wbwwklhttype,task_description,resolved
+VisualEditor: Insert media create link to undefined,"Same thing?
+
+*** This bug has been marked as a duplicate of bug 49596 ***",1371627753,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-2mi7knu2wbwwklhttype,task_subcomment,NA
+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}",1371584640,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-54g2ow3ld3vtvnaijiwz,task_description,resolved
+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 ***",1373155495,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-54g2ow3ld3vtvnaijiwz,task_subcomment,NA
+"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",1371574560,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-kybodyavmyonstmof6sr,task_description,resolved
+"VisualEditor: VE providing unasked-for removal of ""duplicate"" formatting","
+
+%%%*** This bug has been marked as a duplicate of bug 49755 ***%%%",1371574643,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-kybodyavmyonstmof6sr,task_subcomment,NA
+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|<nowiki>foo=bar</nowiki>|baz}}. However, ""foo=bar"" and ""<nowiki>foo=bar</nowiki>"" 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",1371545100,PHID-USER-rjtk3h6l2quifuajiime,False,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_description,resolved
+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",1373416635,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_subcomment,NA
+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",1373415473,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_subcomment,NA
+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<nowiki>=</nowiki>foo}}.",1373403587,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_subcomment,NA
+Parsoid uses nowiki tags for positional template parameters with '='s rather than just explicitly declaring them,See also bug 49743.,1371552288,PHID-USER-rjtk3h6l2quifuajiime,False,PHID-TASK-w6vvfriu2l3mqu3xrisn,task_subcomment,NA
+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}",1371532800,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-xfgiug37am4goz3ewbs4,task_description,resolved
+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 ***",1372015399,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xfgiug37am4goz3ewbs4,task_subcomment,NA
+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",1371524400,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-gpu6rhupzadk44q3zvmd,task_description,declined
+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.",1371527182,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gpu6rhupzadk44q3zvmd,task_subcomment,NA
+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...",1371525193,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-gpu6rhupzadk44q3zvmd,task_subcomment,NA
+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).",1371524702,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gpu6rhupzadk44q3zvmd,task_subcomment,NA
+VisualEditor: Possible to insert empty DEFAULTSORT,"Go to <https://test.wikipedia.org/wiki/IPod?veaction=edit>.
+
+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",1371514380,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-fz5qvkff7hb32uaxnpl7,task_description,resolved
+VisualEditor: Possible to insert empty DEFAULTSORT,Merged and will be deployed very soon.,1371845552,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fz5qvkff7hb32uaxnpl7,task_subcomment,NA
+VisualEditor: Possible to insert empty DEFAULTSORT,Related URL: https://gerrit.wikimedia.org/r/69850 (Gerrit Change Ie3caaf4811f87911444462f83d511c0cc46c0716),1371811734,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fz5qvkff7hb32uaxnpl7,task_subcomment,NA
+Special:Contributions lists spurious AFT entries and takes 20 more seconds to load,"The URL was served for me in 22.766 s and contain spurious entries (without visualeditor tag) like
+    21:47, 17 June 2013 . . (0)‎ . . Feedback: Wikipedia:File Upload Wizard . . DenakiPanos70 (talk) 
+
+This practically equivalent search was served in 1.645 s: <https://en.wikipedia.org/w/index.php?limit=500&tagfilter=visualeditor&title=Special%3AContributions&contribs=newbie&target=&namespace=8&nsInvert=1&tagfilter=visualeditor&year=2013&month=-1>
+
+--------------------------
+**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",1371500220,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-uubavjgv7r236ouenxi3,task_description,resolved
+Special:Contributions lists spurious AFT entries and takes 20 more seconds to load,Merged.,1371566599,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-uubavjgv7r236ouenxi3,task_subcomment,NA
+Special:Contributions lists spurious AFT entries and takes 20 more seconds to load,https://gerrit.wikimedia.org/r/#/c/69152/ & https://gerrit.wikimedia.org/r/#/c/69153/ should fix this.,1371549103,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-uubavjgv7r236ouenxi3,task_subcomment,NA
+Can not create references on some pages,"**Author:** `rachelqa99`
+
+**Description:**
+On this page, we cannot create a reference:   https://www.mediawiki.org/wiki/User:Cmcmahon%28WMF%29/references_bug
+
+We can create a reference on this page: https://www.mediawiki.org/wiki/User:Rachel99/VisualEditor_Feature_Test_Charter/refs_demo
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371490500,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_description,invalid
+Can not create references on some pages,"Chris, it's possible that we accidentally fixed the bug? We updated to master yesterday afternoon, though I don't think we were doing anything in this area.",1371572897,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_subcomment,NA
+Can not create references on some pages,"This seems to have been an anomaly. A strange anomaly because Rachel and I both were unable to create a reference on this page.  Upon clicking ""Apply changes"" in the Reference UI, nothing at all appeared on the page. Now it does.",1371570816,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_subcomment,NA
+Can not create references on some pages,Maybe you want bug 45132.,1371524288,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_subcomment,NA
+Can not create references on some pages,Works for me: https://www.mediawiki.org/w/index.php?title=User:Cmcmahon(WMF)/references_bug&diff=712793&oldid=712613 . Am I missing something?,1371524221,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-c2pwlmpgr24oxvj7ruka,task_subcomment,NA
+Edit with VisualEditor duplicates content with subst'd version of the content,"A user reported this edit
+<https://pt.wikipedia.org/w/index.php?title=CMM_-_Canal_Meninos_e_Meninas&diff=36129698&oldid=36129686>, 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",1371485940,PHID-USER-vyidforzdhnrsoweujao,False,PHID-TASK-amav3irppf34v275xo4q,task_description,resolved
+Edit with VisualEditor duplicates content with subst'd version of the content,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934032,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-amav3irppf34v275xo4q,task_subcomment,NA
+Edit with VisualEditor duplicates content with subst'd version of the content,"This is now fixed in production - really sorry about this bug. If it happens again, please re-open this.",1371515540,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-amav3irppf34v275xo4q,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> 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",1371470220,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-xbihpnurfxbt3vghqoxr,task_description,invalid
+"VisualEditor: Tables with a faulty <tr> 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 <tr> 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.",1371497885,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> at their end display it, confusing users","(In reply to comment #4)
+> This is a Parsoid bug. The PHP parser does not generate a <tr> for this
+> wikitext, and Parsoid does.
+
+Does the PHP parser create it but it then gets tidied away?",1371497466,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> at their end display it, confusing users","This is a Parsoid bug. The PHP parser does not generate a <tr> for this wikitext, and Parsoid does.",1371497353,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> 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. :-(",1371497109,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> 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 |}...,1371497019,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+"VisualEditor: Tables with a faulty <tr> 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 
+
+  |-
+  | <content>
+  |-
+  |}
+
+… 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.",1371496639,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xbihpnurfxbt3vghqoxr,task_subcomment,NA
+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",1371468780,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ss2itizzzz4vdy6z2bwv,task_description,resolved
+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 ***",1371510441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ss2itizzzz4vdy6z2bwv,task_subcomment,NA
+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",1371466320,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k4uqhsrhnkkuz3d2z6l6,task_description,resolved
+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],1372934078,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-k4uqhsrhnkkuz3d2z6l6,task_subcomment,NA
+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 <nowiki>s around wiki-able elements of tables is also, I believe, fixed in production.
+
+<nowiki>s around wikitext are, of course, intentional.",1371671665,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k4uqhsrhnkkuz3d2z6l6,task_subcomment,NA
+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,1371475258,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k4uqhsrhnkkuz3d2z6l6,task_subcomment,NA
+VisualEditor: Unexpected padding,"See the tabs on https://en.wikipedia.org/wiki/User:Panpog1 for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371466080,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jzepbqpzu7s7bfg4k2ua,task_description,resolved
+VisualEditor: Unexpected padding,Fixed.,1372015377,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jzepbqpzu7s7bfg4k2ua,task_subcomment,NA
+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",1371403200,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6tdi4t2hiwd4kw4wdp3k,task_description,resolved
+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 ***",1371409196,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-6tdi4t2hiwd4kw4wdp3k,task_subcomment,NA
+UniversalLanguageSelector Does not work with VisualEditor,"**bellayet** wrote:
+
+ULS Input tool is not supporting VisualEditor.",1371405203,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6tdi4t2hiwd4kw4wdp3k,task_subcomment,NA
+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",1371382800,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-5ezr4schgjcznl2chb3p,task_description,declined
+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?",1371422998,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.",1371420335,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.",1371416756,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.",1371415303,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.,1371415095,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+VisualEditor bugzilla component should be under MediaWiki extensions,...and Bugzilla bugs should be filed under Bugzilla. Moving.,1371408158,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+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.",1371408122,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5ezr4schgjcznl2chb3p,task_subcomment,NA
+"""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",1371315060,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-oz4sidkwsjedlisknc5h,task_description,invalid
+"""Use the wikitext editor for editing sections while VisualEditor is in beta"" should be default",Thanks. I like the chosen solution.,1372542001,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-oz4sidkwsjedlisknc5h,task_subcomment,NA
+"""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).",1372279685,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oz4sidkwsjedlisknc5h,task_subcomment,NA
+"""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.",1372129450,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oz4sidkwsjedlisknc5h,task_subcomment,NA
+Implement the same EventLogging of page edits in wikitext editor as in VisualEditor for comparison purposes,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371231960,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tmvxleqap5uqab7s5tju,task_description,resolved
+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.",1371507422,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tmvxleqap5uqab7s5tju,task_subcomment,NA
+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).",1371233136,PHID-USER-qb5aoo443n6fezsozhv4,True,PHID-TASK-tmvxleqap5uqab7s5tju,task_subcomment,NA
+Configure VisualEditor for section edit links to go to VisualEditor by default,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371155460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-c4vkf2igh4ozkrhmdcdd,task_description,invalid
+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.,1371161579,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-c4vkf2igh4ozkrhmdcdd,task_subcomment,NA
+VisualEditor: Switch over to handle mw:WikiLink/Interwiki,"Currently links with mw:WikiLink/Interwiki get alienated
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371150540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ruct6x62hxyefsmpylp6,task_description,resolved
+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 ***",1371150585,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ruct6x62hxyefsmpylp6,task_subcomment,NA
+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",1371145680,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-aujnfu5wgjys4i7m3tqa,task_description,resolved
+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 ***",1371153385,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aujnfu5wgjys4i7m3tqa,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) 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 <Gallery></Gallery>
+
+Anything following the opening <Gallery> 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",1371125760,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-7xdz6csv454jmjt43l3k,task_description,resolved
+Extension tags starting with a capital (<Gallery>) 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],1372934067,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) seem to confuse the parser,https://gerrit.wikimedia.org/r/68727 (Gerrit Change I288f6ec9e4117ce58e2f445e73868937be1654af) | change APPROVED and MERGED [by jenkins-bot],1371249813,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) seem to confuse the parser,Related URL: https://gerrit.wikimedia.org/r/68727 (Gerrit Change I288f6ec9e4117ce58e2f445e73868937be1654af),1371238814,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) seem to confuse the parser,*** Bug 49579 has been marked as a duplicate of this bug. ***,1371225610,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+Extension tags starting with a capital (<Gallery>) 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?)",1371135498,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7xdz6csv454jmjt43l3k,task_subcomment,NA
+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",1371117420,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ku4zjzbgxbemhv6sicxc,task_description,resolved
+VisualEditor: Mass of extraneous quot and amp marks,"I think that we've fixed this bug, but if it recurs please re-open.",1372014851,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ku4zjzbgxbemhv6sicxc,task_subcomment,NA
+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",1371058200,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-j57p7ueywyekpmhxkqes,task_description,resolved
+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 ***",1380609083,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-j57p7ueywyekpmhxkqes,task_subcomment,NA
+VisualEditor: Add the ability to drag highlighted text around with the mouse,Neat! Thanks :),1371058632,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-j57p7ueywyekpmhxkqes,task_subcomment,NA
+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 ***",1371058332,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j57p7ueywyekpmhxkqes,task_subcomment,NA
+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",1371027000,PHID-USER-vyidforzdhnrsoweujao,False,PHID-TASK-ajsfntti2ybnqjqeqxfs,task_description,resolved
+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 ***",1371049016,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ajsfntti2ybnqjqeqxfs,task_subcomment,NA
+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",1370906580,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-bumkxu7r6tdc2iyjok4e,task_description,resolved
+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.",1372762967,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-bumkxu7r6tdc2iyjok4e,task_subcomment,NA
+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.",1371227753,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-bumkxu7r6tdc2iyjok4e,task_subcomment,NA
+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}",1370856240,PHID-USER-ixwg3kf22idjy7x4ncxf,False,PHID-TASK-wdm6ddtjkbpjvqclln2i,task_description,resolved
+VisualEditor: Linking to an image results in the image being loaded,"
+
+*** This bug has been marked as a duplicate of bug 48387 ***",1370883912,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdm6ddtjkbpjvqclln2i,task_subcomment,NA
+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",1370689740,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-n7737xkjqezrnwwaava3,task_description,resolved
+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 ***",1370840639,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n7737xkjqezrnwwaava3,task_subcomment,NA
+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",1370270880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f22y5n2hutfcuixay276,task_description,resolved
+Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;,Done on 2013-06-06.,1370741026,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f22y5n2hutfcuixay276,task_subcomment,NA
+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.",1370288193,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f22y5n2hutfcuixay276,task_subcomment,NA
+Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;,And the test and MW.org wikis.,1370286285,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f22y5n2hutfcuixay276,task_subcomment,NA
+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",1369745520,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_description,resolved
+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 ***",1374227951,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+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""'.",1371841158,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+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.",1371066634,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+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.",1369937612,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+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.",1369755874,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-2xyzi2meu5y5iozdxh3z,task_subcomment,NA
+"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",1369114380,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6nrh4cee4ez6cwykweo5,task_description,resolved
+"VisualEditor misrepresents linked files as embedded inline, when editing","
+
+*** This bug has been marked as a duplicate of bug 48387 ***",1369114571,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6nrh4cee4ez6cwykweo5,task_subcomment,NA
+"VisualEditor misrepresents linked files as embedded inline, when editing","**swalling** wrote:
+
+Screenshot of markup
+
+**Attached**: {F10438}",1369114456,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6nrh4cee4ez6cwykweo5,task_subcomment,NA
+"VisualEditor misrepresents linked files as embedded inline, when editing","**swalling** wrote:
+
+Edit mode, with incorrect thumbnails
+
+**Attached**: {F10437}",1369114431,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6nrh4cee4ez6cwykweo5,task_subcomment,NA
+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",1369078800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4ottk5yqyncneqh7goju,task_description,resolved
+Enable section-editing on 'beta' profile of VisualEditor deployments,Done today.,1371169125,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4ottk5yqyncneqh7goju,task_subcomment,NA
+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",1369067700,PHID-USER-jcypqodpdpbcicgwgh7j,False,PHID-TASK-q6etjfxib3te52jrdbqh,task_description,resolved
+MediaWiki:Visualeditor-feedback-link doesn't use wiki language,"
+
+*** This bug has been marked as a duplicate of bug 47730 ***",1369068249,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q6etjfxib3te52jrdbqh,task_subcomment,NA
+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}",1368849600,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-f54j3i3yobgyvswaikfo,task_description,resolved
+VisualEditor expanding image links,"
+
+*** This bug has been marked as a duplicate of bug 48387 ***",1368979809,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f54j3i3yobgyvswaikfo,task_subcomment,NA
+"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",1368746160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-a6xscw7mjvhcbwgufh5y,task_description,invalid
+"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.,1368747382,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-a6xscw7mjvhcbwgufh5y,task_subcomment,NA
+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",1368684120,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-zfww4nd7axazvbfkd7qj,task_description,invalid
+List looks like it has extra empty lines,"Oh, I see, my bad, I should have checked the wikicode! :-)",1369104667,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-zfww4nd7axazvbfkd7qj,task_subcomment,NA
+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<ref name=""statinfo.biz""/> (2003)
+> *21 Sweden	 	639,000<ref name=""statinfo.biz""/> (2004)
+> 
+> *22 Ukraine	 	562,000<ref name=""statinfo.biz""/> (1995)
+> *23 France	 	544,000<ref name=""statinfo.biz""/> (2003)
+> *24 Australia	 	423,000<ref name=""statinfo.biz""/> (1995)
+> 
+> *25	Portugal	 	399,000<ref name=""statinfo.biz""/>	(2004)	
+> *26	Bulgaria	 	353,000<ref name=""statinfo.biz""/>	(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. :-))",1369080566,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zfww4nd7axazvbfkd7qj,task_subcomment,NA
+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",1368662520,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-a6lxhzu2xrx5tgje6umc,task_description,declined
+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.",1368662919,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a6lxhzu2xrx5tgje6umc,task_subcomment,NA
+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",1368583740,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-h57f3cph7qycjnbwjvnw,task_description,resolved
+VisualEditor: Can not paste new link anchor,"**jiabao.foss** wrote:
+
+That's very nice of you! I would love to investigate this bug.",1368805529,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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.",1368771998,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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. :)",1368767327,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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 ***",1368726943,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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.",1368725524,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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.",1368684779,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-h57f3cph7qycjnbwjvnw,task_subcomment,NA
+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}",1368565440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-apdnw6jklub4mtqzckmn,task_description,resolved
+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 ***",1368569378,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-apdnw6jklub4mtqzckmn,task_subcomment,NA
+VisualEditor link tool incorrectly shows a red link,"VisualEditor link dialog box incorrectly showing red text, 2013-05-13
+
+Go to <https://www.mediawiki.org/wiki/Sysadmin_hub>. 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}",1368500280,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-zpvndgxny4i6jsgnxaga,task_description,resolved
+VisualEditor link tool incorrectly shows a red link,"Also reported by Timo; given work us underway, DUPEing up rather than down.
+
+*** This bug has been marked as a duplicate of bug 48476 ***",1368720868,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zpvndgxny4i6jsgnxaga,task_subcomment,NA
+"""visualeditor-diff-nochanges"" exposed on mediawiki.org","VisualEditor message key exposed on mediawiki.org, 2013-05-13
+
+URL: <https://www.mediawiki.org/wiki/MobileFrontend/Photo_upload/Analysis>
+
+Error: see attached screenshot
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10756}",1368497760,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-uuriwo6q3mdhjyt6egwi,task_description,resolved
+"""visualeditor-diff-nochanges"" exposed on mediawiki.org",Now fixed.,1368545353,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uuriwo6q3mdhjyt6egwi,task_subcomment,NA
+"""visualeditor-diff-nochanges"" exposed on mediawiki.org",Looks like <visualeditor-diff-nochanges> is not in MW.org's message file; need to do a message purge?,1368500743,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uuriwo6q3mdhjyt6egwi,task_subcomment,NA
+"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",1368150660,PHID-USER-gibrlx54k2riiuit5paf,False,PHID-TASK-tstjv3noyoaah6bfdmns,task_description,resolved
+"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 ***",1368150918,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tstjv3noyoaah6bfdmns,task_subcomment,NA
+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",1367872680,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_description,resolved
+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],1372934001,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+Parsoid: HTML comment with immediately following table has newline split removed,Fixed in production.,1367944050,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+Parsoid: HTML comment with immediately following table has newline split removed,Related URL: https://gerrit.wikimedia.org/r/62546 (Gerrit Change If16dda01058715acee8df347b2b9c4da84609113),1367884917,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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?,1367877227,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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).",1367876908,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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?",1367876730,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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.",1367876593,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+Parsoid: HTML comment with immediately following table has newline split removed,Can you link to the original report?,1367876265,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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.",1367874446,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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",1367873178,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7u7csbjslb6fdxkpcs6y,task_subcomment,NA
+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.:
+
+<b>Bold on load text</b><b>added text</b>
+
+Which Parsoid converts to
+
+'''Bold on load text''''''added text'''
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367774100,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hc26warwwz5ylqujc3td,task_description,resolved
+VisualEditor: Adjacent annotations which are equal by name but not reference do not serialise correctly.,Merged into master.,1367871652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hc26warwwz5ylqujc3td,task_subcomment,NA
+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),1367782652,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hc26warwwz5ylqujc3td,task_subcomment,NA
+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 </span> and </table> got added automatically.
+
+Where's that ""partial serialization"" mentioned before?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367290980,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-slnchzhtiw4uoxg47vla,task_description,resolved
+VisualEditor: Extra tags got inserted causing infobox layout to be broken,"The main part of this bug (the extra </span> and </table>) 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 ***",1367545048,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-slnchzhtiw4uoxg47vla,task_subcomment,NA
+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",1367215380,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-r75ffyh3qiqooawo44eb,task_description,declined
+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.",1367544785,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-r75ffyh3qiqooawo44eb,task_subcomment,NA
+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",1367205180,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_description,resolved
+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 ***",1367268091,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_subcomment,NA
+RTL Support for VisualEditor,"I'll tentatively reopen it and mark it as blocking 33126 instead.
+Not sure though, maybe James knows. :)",1367231596,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_subcomment,NA
+RTL Support for VisualEditor,It's a bug for tracking a GSoC proposal. I think that it should be reopened.,1367228877,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_subcomment,NA
+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 ***",1367228662,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2gqmb4cvp2njgfweg4mi,task_subcomment,NA
+[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",1367047080,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ul25dgz4nyeridoqmsqg,task_description,resolved
+[VisualEditor] CSS and JS pages should only be editable using the source editor,"
+
+*** This bug has been marked as a duplicate of bug 47456 ***",1367097296,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ul25dgz4nyeridoqmsqg,task_subcomment,NA
+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",1367013780,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-a56uzvltsvz2gw6egtar,task_description,invalid
+Feedback is broken,"Not actually broken, see bug 42974.",1367222196,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-a56uzvltsvz2gw6egtar,task_subcomment,NA
+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",1367008080,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-exyn4bfiq2igip2xy6r4,task_description,declined
+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.",1367019704,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-exyn4bfiq2igip2xy6r4,task_subcomment,NA
+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).,1367009441,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-exyn4bfiq2igip2xy6r4,task_subcomment,NA
+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",1366719660,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ajr6uvwq3l2hdzyqjden,task_description,resolved
+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 ***",1366741802,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ajr6uvwq3l2hdzyqjden,task_subcomment,NA
+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}",1366719765,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ajr6uvwq3l2hdzyqjden,task_subcomment,NA
+"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",1366388640,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ob7cxxrhd6d3aeazrujm,task_description,resolved
+"VisualEditor: Dirty diffs with FF, but not in Chrome on pages with citations","
+
+*** This bug has been marked as a duplicate of bug 47417 ***",1366391720,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ob7cxxrhd6d3aeazrujm,task_subcomment,NA
+"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",1366388836,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ob7cxxrhd6d3aeazrujm,task_subcomment,NA
+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",1366058760,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-vav3ssxyt7puz6mth7ck,task_description,resolved
+VisualEditor: Problem with placing cursor inside slug (inline|block) with mouse,Fixed here: https://gerrit.wikimedia.org/r/#/c/59199/,1366059192,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-vav3ssxyt7puz6mth7ck,task_subcomment,NA
+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",1364916660,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ryyonehlcnqdc46zjg2w,task_description,resolved
+VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,Now fixed.,1366142624,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,Related URL: https://gerrit.wikimedia.org/r/58868 (Gerrit Change I6b2700d65476c4d34ba4a01a88382d7af8e736fb),1365765433,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality,Actually Ed is still working on it.,1365029413,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+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/,1365024583,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+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",1364916742,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ryyonehlcnqdc46zjg2w,task_subcomment,NA
+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",1364433480,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4q75ixwk7yvcayzud2qd,task_description,resolved
+VisualEditor: Allow nodes to handle their own children,Done in https://gerrit.wikimedia.org/r/#/c/58645/ and related commits.,1366130702,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4q75ixwk7yvcayzud2qd,task_subcomment,NA
+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",1364167560,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-sk3uspo3yfsnwm2o672b,task_description,resolved
+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 ***",1364167729,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sk3uspo3yfsnwm2o672b,task_subcomment,NA
+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",1364163180,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_description,declined
+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],1372934009,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364231575,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364231508,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364231440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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 :)",1364231169,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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?",1364229706,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364228786,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364227272,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+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.",1364165114,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-jhlniwxu2ykuroltxk3l,task_subcomment,NA
+"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",1364127180,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-6vicxrcuqmyqgizvbnop,task_description,resolved
+"Just added single character, but at review all content is replaced","
+
+*** This bug has been marked as a duplicate of bug 43103 ***",1364127463,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-6vicxrcuqmyqgizvbnop,task_subcomment,NA
+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",1364126940,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-l2eaq3bdozrt2dgpbncq,task_description,resolved
+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 ***",1364164432,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l2eaq3bdozrt2dgpbncq,task_subcomment,NA
+VisualEditor: store annotations in a document-wide index/value store and serialize as integer indexes,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363693320,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-e7xy2ghygeqe5vvk7vir,task_description,resolved
+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),1363819486,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-e7xy2ghygeqe5vvk7vir,task_subcomment,NA
+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",1363693508,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-e7xy2ghygeqe5vvk7vir,task_subcomment,NA
+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/",1363637880,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_description,declined
+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.",1375350900,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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.",1372186269,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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?",1372185965,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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.",1363805065,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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.",1363803636,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2gmwjvi3zn6cswyfyegi,task_subcomment,NA
+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}",1361749260,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mq355eomr24cmluqc7dh,task_description,resolved
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],A reasonable resolution of this issue. :),1361832255,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+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 <pre>. 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.",1361831946,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+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:
+
+<table>
+<tr>
+<td>
+  a</td>
+<td>
+ b
+</td>
+</tr>
+</table>
+
+""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.",1361826274,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],"This might be a bug in https://gerrit.wikimedia.org/r/#/c/32405/ or a regression.  The <pre> is coming from an #if parser function which should not have as per that commit message.
+
+Will investigate.",1361822814,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Created attachment 11841
+HTML of {{disambiguation}} from Parsoid
+
+The main problem is the presence of a <pre> that shouldn't be there.
+
+**Attached**: {F10465}",1361749531,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Created attachment 11840
+Screenshot of {{disambiguation}} from Parsoid
+
+**Attached**: {F10464}",1361749431,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+Parsoid: Incorrect rendering for [[Template:Disambiguation]],"Created attachment 11839
+HTML of {{disambiguation}} on [[Loco]] at en.wikipedia.org
+
+**Attached**: {F10463}",1361749373,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mq355eomr24cmluqc7dh,task_subcomment,NA
+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",1360879800,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2lufxleaemvynes2b2da,task_description,declined
+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.",1360889187,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2lufxleaemvynes2b2da,task_subcomment,NA
+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].<anonymous> (/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].<anonymous> (/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",1360784520,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xtyrp3i5752jen7uoe6m,task_description,invalid
+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],1372934041,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xtyrp3i5752jen7uoe6m,task_subcomment,NA
+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.",1360785028,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xtyrp3i5752jen7uoe6m,task_subcomment,NA
+VisualEditor: VE chokes on unexpected redirect response from Parsoid,"**Author:** `phil`
+
+**Description:**
+I created a page using the normal editor that was
+
+
+<gallery>
+File:Example.jpg|Caption1
+#REDIRECT [[Target page name]]
+</gallery>
+
+
+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",1360730040,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2aj3mfax5n7tlrsztfhy,task_description,resolved
+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.",1362769118,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2aj3mfax5n7tlrsztfhy,task_subcomment,NA
+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",1360785321,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2aj3mfax5n7tlrsztfhy,task_subcomment,NA
+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).",1360783589,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2aj3mfax5n7tlrsztfhy,task_subcomment,NA
+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",1360462980,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aqea5euyvi5ekuwq3kig,task_description,resolved
+VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,Now merged.,1360976726,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aqea5euyvi5ekuwq3kig,task_subcomment,NA
+VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,"Whoops, not yet merged.",1360613606,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aqea5euyvi5ekuwq3kig,task_subcomment,NA
+VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,Merged.,1360612923,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-aqea5euyvi5ekuwq3kig,task_subcomment,NA
+VisualEditor: Multiple toolbars created if tabs switched before initialization is complete,Patch in: https://gerrit.wikimedia.org/r/48491,1360612133,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-aqea5euyvi5ekuwq3kig,task_subcomment,NA
+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",1360297620,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hiumuha3tc6xqypqt2lz,task_description,resolved
+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 ***",1360376842,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hiumuha3tc6xqypqt2lz,task_subcomment,NA
+VisualEditor: What Heading levels are offered should flex based,"Created attachment 11760
+Screenshot showing H1 to H6 in VisualEditor mode
+
+**Attached**: {F11017}",1360376691,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hiumuha3tc6xqypqt2lz,task_subcomment,NA
+VisualEditor: What Heading levels are offered should flex based,"Created attachment 11759
+Screenshot showing H1 to H6 in read mode
+
+**Attached**: {F11015}",1360376669,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hiumuha3tc6xqypqt2lz,task_subcomment,NA
+Parsoid: Linktrails should get a <nowiki /> 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}",1360296540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nsc6gcp3vvg4tvl6tyfb,task_description,resolved
+Parsoid: Linktrails should get a <nowiki /> added on serialisation,"Ah, couldn't find the bug; thanks, Gabriel.
+
+*** This bug has been marked as a duplicate of bug 33091 ***",1360704683,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nsc6gcp3vvg4tvl6tyfb,task_subcomment,NA
+Parsoid: Linktrails should get a <nowiki /> added on serialisation,"To me it seems that the VE should produce a DOM including the space: 
+
+<a href=""foo"">bar</a> 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.",1360704397,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-nsc6gcp3vvg4tvl6tyfb,task_subcomment,NA
+Parsoid: Linktrails should get a <nowiki /> added on serialisation,"This appears to be a problem in Parsoid.
+
+In VisualEditor the user has (effectively) created <a href=""foo"">bar</a>baz; it is unexpectedly converted into [[foo|bar]]baz instead of [[foo|bar]]<nowiki />baz, hence the confusion.
+
+Gabriel, thoughts?",1360703129,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nsc6gcp3vvg4tvl6tyfb,task_subcomment,NA
+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",1360091400,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-xpyddbk7oe25b7f7bpp3,task_description,resolved
+VisualEditor: Opening link inspector without selection in stand alone instance throws error.,Now merged.,1360105358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xpyddbk7oe25b7f7bpp3,task_subcomment,NA
+VisualEditor: Opening link inspector without selection in stand alone instance throws error.,Patched in https://gerrit.wikimedia.org/r/#/c/47615/,1360094494,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-xpyddbk7oe25b7f7bpp3,task_subcomment,NA
+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 <nowiki> 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 <nowiki> tags up to the formatted character and leaves the rest of the line alone
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10444}",1359487500,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cke5acua2kmqpq2rtiv4,task_description,declined
+VisualEditor: Unexpected behavior when line starts with space,"... but when you save "" le'''''adi'''''ing space"" in the wikitext editor, you get <pre>le'''''adi'''''ing space</pre>, not <p> le'''''adi'''''ing space</p>. The <nowiki> tags are necessary to get the latter, which is what the VE user actually typed.
+
+Closing as WONTFIX.",1360208015,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+VisualEditor: Unexpected behavior when line starts with space,"Created attachment 11719
+normal editor vs. VE on save
+
+**Attached**: {F10447}",1359744124,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+VisualEditor: Unexpected behavior when line starts with space,"Created attachment 11718
+normal editor vs. VE preview
+
+**Attached**: {F10446}",1359744087,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+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 <nowiki> tags to this string.  VE adds <nowiki> tags. 
+
+The normal editor does not save the text with <nowiki> tags.  VE saves the text with <nowiki> tags. 
+
+It may be that VE adds <nowiki> tags by design, but they seem unnecessary.  Again, I could be wrong.",1359744005,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+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 <P> Foo</P> 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?",1359682189,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+VisualEditor: Unexpected behavior when line starts with space,look what happens in the regular editor.  I think VE is doing something really strange here.,1359671085,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+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 <nowiki> elements?,1359669739,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+VisualEditor: Unexpected behavior when line starts with space,"Created attachment 11706
+nowiki tags with formatted text
+
+**Attached**: {F10445}",1359487603,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cke5acua2kmqpq2rtiv4,task_subcomment,NA
+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",1359038700,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gf44zknlabktvyuiobnc,task_description,resolved
+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 ***",1360207511,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gf44zknlabktvyuiobnc,task_subcomment,NA
+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 :)",1359450666,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gf44zknlabktvyuiobnc,task_subcomment,NA
+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",1358094720,PHID-USER-37d2msujvpp2rippbzoq,False,PHID-TASK-fmsq2a44unt5qvw7fvjz,task_description,declined
+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.",1425405042,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fmsq2a44unt5qvw7fvjz,task_subcomment,NA
+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",1409587205,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fmsq2a44unt5qvw7fvjz,task_subcomment,NA
+"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",1357860900,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-cek4b33i7kzn3d5tir7d,task_description,resolved
+"VisualEditor: Make link inspector aware of annotations, rather than just target strings",Made it to master for the 2013-01-16 branch.,1358388388,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cek4b33i7kzn3d5tir7d,task_subcomment,NA
+"VisualEditor: Make link inspector aware of annotations, rather than just target strings",Addressed in gerrit 43028.,1357861248,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cek4b33i7kzn3d5tir7d,task_subcomment,NA
+"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",1357052100,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v5mejtdved3hadzpnblg,task_description,invalid
+"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://' );",1357704294,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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!",1357349661,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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",1357346134,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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?",1357308806,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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?",1357125626,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+"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?",1357116244,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-v5mejtdved3hadzpnblg,task_subcomment,NA
+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",1356608820,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-bbwwebnria5w3khcdb2z,task_description,resolved
+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 ***",1356713507,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-bbwwebnria5w3khcdb2z,task_subcomment,NA
+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",1356551700,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-d3f2ddd27saapnkqzblp,task_description,resolved
+Removing link trail doesn't affect the output,Finally squashed in https://gerrit.wikimedia.org/r/#/c/43985/.,1358213523,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-d3f2ddd27saapnkqzblp,task_subcomment,NA
+Removing link trail doesn't affect the output,Change I126116de should fix this.,1356634590,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-d3f2ddd27saapnkqzblp,task_subcomment,NA
+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.",1356553785,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-d3f2ddd27saapnkqzblp,task_subcomment,NA
+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",1356106320,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6tdn24gf46lji7yqfvl2,task_description,invalid
+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.,1356106907,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6tdn24gf46lji7yqfvl2,task_subcomment,NA
+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",1355898660,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-jtaql5mrtvhb43vajwv3,task_description,resolved
+VisualEditor: Tooltip broken on outdent button,Thanks for the report.  This was patched in. https://gerrit.wikimedia.org/r/#/c/38810/,1355942170,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-jtaql5mrtvhb43vajwv3,task_subcomment,NA
+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 <hiero> 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 <hiero> 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",1355479740,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-ttm23g3exfsgbjvupqdx,task_description,resolved
+Reporter missing in IRC announcement of new issue,"
+
+*** This bug has been marked as a duplicate of bug 42774 ***",1355479865,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ttm23g3exfsgbjvupqdx,task_subcomment,NA
+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",1355414040,PHID-USER-wel3wo6tppcxgnrthxls,False,PHID-TASK-i3kcektvabsqugyb5tzv,task_description,declined
+VisualEditor never loads,Wth?! Why does it take so much time to load. But then it atlast worked.,1355415643,PHID-USER-wel3wo6tppcxgnrthxls,False,PHID-TASK-i3kcektvabsqugyb5tzv,task_subcomment,NA
+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",1355398980,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-ux4izidb7xrrwhvej2xp,task_description,declined
+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.",1355445344,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-ux4izidb7xrrwhvej2xp,task_subcomment,NA
+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.",1355443086,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ux4izidb7xrrwhvej2xp,task_subcomment,NA
+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.)",1355436686,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-ux4izidb7xrrwhvej2xp,task_subcomment,NA
+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.",1355435276,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ux4izidb7xrrwhvej2xp,task_subcomment,NA
+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",1355386260,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-ly2xm7tz73tvksvhmtyz,task_description,resolved
+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.,1357678696,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ly2xm7tz73tvksvhmtyz,task_subcomment,NA
+VisualEditor: Things are sometimes alienated as block when they should be inline,https://gerrit.wikimedia.org/r/39846,1356175107,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ly2xm7tz73tvksvhmtyz,task_subcomment,NA
+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 <div> 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 <div class=""ve-ce-alienBlock""> or <span class=""ve-ce-alienInline""> 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.",1355389006,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ly2xm7tz73tvksvhmtyz,task_subcomment,NA
+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}",1355378640,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kvsbzknbe6m5oydwjk6y,task_description,resolved
+VisualEditor: Escape from LinkAnnotation editor closes annotation editor but leaves suggestion box floating,"
+
+%%%*** This bug has been marked as a duplicate of bug 43051 ***%%%",1355425528,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-kvsbzknbe6m5oydwjk6y,task_subcomment,NA
+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",1355358660,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-ton3dd6uf2z3sfe3n2k3,task_description,resolved
+VisualEditor: Suggestion tool fails to close when escaping out of context menu.,Add to deployment milestone.,1357594470,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ton3dd6uf2z3sfe3n2k3,task_subcomment,NA
+VisualEditor: Suggestion tool fails to close when escaping out of context menu.,%%%*** Bug 43055 has been marked as a duplicate of this bug. ***%%%,1355425528,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-ton3dd6uf2z3sfe3n2k3,task_subcomment,NA
+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",1355360183,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-ton3dd6uf2z3sfe3n2k3,task_subcomment,NA
+"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",1355344680,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gax37c3j4qvaskyhk55t,task_description,resolved
+"VisualEditor: For initial deployment, do not over-ride edit-section links",This appears to have missed the deploy-train; moving.,1357578100,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gax37c3j4qvaskyhk55t,task_subcomment,NA
+"VisualEditor: For initial deployment, do not over-ride edit-section links",Now merged into master.,1355829010,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gax37c3j4qvaskyhk55t,task_subcomment,NA
+"VisualEditor: For initial deployment, do not over-ride edit-section links",Fixed by https://gerrit.wikimedia.org/r/#/c/38451/,1355804868,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-gax37c3j4qvaskyhk55t,task_subcomment,NA
+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",1355342280,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-uqidpcw3y4xgb5ynjwev,task_description,resolved
+VisualEditor: Undo just after load of the editor causes JS error.,"Also happens for redo.
+Patched in: https://gerrit.wikimedia.org/r/#/c/38349/",1355342889,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-uqidpcw3y4xgb5ynjwev,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,"Seen on the VE-editing interface of https://www.mediawiki.org/wiki/VisualEditor:Test
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355292540,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-3ytipv46bzm44jpqmwoq,task_description,resolved
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,Add to deployment milestone.,1357594496,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,Working for me now after a hard refresh.,1355341256,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,"The messages are certainly in the i18n file, it probably just needs a l10n cache rebuild. Doing that now.",1355336196,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> 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",1355331834,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> 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.",1355327793,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+VisualEditor: <visualeditor-toolbar-savedialog> message is missing,"Also messages in that dialog, like <visualeditor-savedialog-title-review>, <visualeditor-savedialog-title-review-wrong>, <visualeditor-savedialog-title-review-good> etc",1355297902,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-3ytipv46bzm44jpqmwoq,task_subcomment,NA
+"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",1355189160,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-ivhyp5yplrphnwughsqu,task_description,resolved
+"VisualEditor: While using link inspector, transaction hangs and page eventually explodes.",Fixed in https://gerrit.wikimedia.org/r/#/c/38004/,1355191424,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-ivhyp5yplrphnwughsqu,task_subcomment,NA
+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",1355175300,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-hydd4sggtsrxlgqhafqc,task_description,resolved
+VisualEditor: Inspector doesn't open properly,*** Bug 37856 has been marked as a duplicate of this bug. ***,1355350453,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hydd4sggtsrxlgqhafqc,task_subcomment,NA
+VisualEditor: Inspector doesn't open properly,Fixed in gerrit 37945.,1355176593,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hydd4sggtsrxlgqhafqc,task_subcomment,NA
+VisualEditor: Re-enable the feedback tool for deployment,"Point to [[Project:VisualEditor/Feedback]] for now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355171460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6k6omehrnjj3d64g3xkp,task_description,resolved
+VisualEditor: Re-enable the feedback tool for deployment,See also https://gerrit.wikimedia.org/r/#/c/32700/ for usage.,1355175058,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6k6omehrnjj3d64g3xkp,task_subcomment,NA
+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",1355168340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qsgzi7766f5xj7zdn6hb,task_description,resolved
+VisualEditor: Toolbar tooltips should also suggest key-commands,"Now merged, will go out in 2013-02-04 release cycle.",1358469697,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qsgzi7766f5xj7zdn6hb,task_subcomment,NA
+VisualEditor: Toolbar tooltips should also suggest key-commands,Patched in https://gerrit.wikimedia.org/r/#/c/44347/,1358375049,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-qsgzi7766f5xj7zdn6hb,task_subcomment,NA
+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",1354930620,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qype6jzcuqvgj55crv3,task_description,resolved
+VisualEditor: Notifications should not use db-variant of page titles,"(In reply to comment #1)
+> Change-Id: Ie84168cd2509a17c180c6143a87a18ae8bbb3d0a
+Merged.",1354942098,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2qype6jzcuqvgj55crv3,task_subcomment,NA
+VisualEditor: Notifications should not use db-variant of page titles,Change-Id: Ie84168cd2509a17c180c6143a87a18ae8bbb3d0a,1354930713,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qype6jzcuqvgj55crv3,task_subcomment,NA
+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",1354926720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mu7m2pj54l427crmnupd,task_description,resolved
+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"".",1359516361,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mu7m2pj54l427crmnupd,task_subcomment,NA
+VisualEditor: Support Internet Explorer,Please see Bug 41233,1359065649,PHID-USER-wi7txqp5ld5ze33dx7am,True,PHID-TASK-mu7m2pj54l427crmnupd,task_subcomment,NA
+VisualEditor: Support Internet Explorer,"Argh, ignore that; an at-least partial fix in gerrit 37592.",1354926991,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mu7m2pj54l427crmnupd,task_subcomment,NA
+VisualEditor: Support Internet Explorer,Attempted fixes in gerrit 37566 and gerrit 37570.,1354926882,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mu7m2pj54l427crmnupd,task_subcomment,NA
+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",1354920600,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-jvbmuzupmyildaswp3ax,task_description,resolved
+VisualEditor: Create a link at the beginning of the document throws rangy error,Related URL: https://gerrit.wikimedia.org/r/69707 (Gerrit Change I8bcdea0f7a6951216bf8368865d23ef6246880ea),1371753492,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jvbmuzupmyildaswp3ax,task_subcomment,NA
+VisualEditor: Create a link at the beginning of the document throws rangy error,Fix in gerrit 37603,1354931366,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jvbmuzupmyildaswp3ax,task_subcomment,NA
+"VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354771560,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-75c273bypsftlyrbr3cc,task_description,resolved
+"VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language",Merged.,1354832652,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-75c273bypsftlyrbr3cc,task_subcomment,NA
+"VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language",Change-Id: I84fee641162cdeed290092e56fb0e1d2562d833d,1354771693,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-75c273bypsftlyrbr3cc,task_subcomment,NA
+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",1354596300,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vr2jeooanda24ls5knww,task_description,resolved
+VisualEditor: ext.visualEditor.specialMessages module cache invalidation broken,Now merged into master.,1354654432,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vr2jeooanda24ls5knww,task_subcomment,NA
+VisualEditor: ext.visualEditor.specialMessages module cache invalidation broken,Change-Id: I7f26b47e9467e850c08b9c217c4f1098590de109,1354607956,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vr2jeooanda24ls5knww,task_subcomment,NA
+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",1353963360,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-yjkqv35zcxvtirgx56ds,task_description,resolved
+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.",1354028484,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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",1354015514,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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.",1354001228,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),https://gerrit.wikimedia.org/r/#/c/35327/,1353972830,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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",1353970599,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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}",1353970120,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget(),Caused by https://gerrit.wikimedia.org/r/#/c/31330/,1353969954,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+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",1353969228,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yjkqv35zcxvtirgx56ds,task_subcomment,NA
+VisualEditor: Temporarily add IE to blacklist for December release as CE support is currently insufficient,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1353529620,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-drb6zxeswawnaqold54q,task_description,resolved
+VisualEditor: Temporarily add IE to blacklist for December release as CE support is currently insufficient,https://gerrit.wikimedia.org/r/#/c/34584/,1353530010,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-drb6zxeswawnaqold54q,task_subcomment,NA
+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",1352940180,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qyxlhx72vvvsjxiz5mxk,task_description,resolved
+VisualEditor: i18n for alien tooltip,Fixed in gerrit 33851,1353113705,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qyxlhx72vvvsjxiz5mxk,task_subcomment,NA
+VisualEditor: i18n for alien tooltip,"Also it's VisualEditor not ""Visual Editor"". :-)",1352940362,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qyxlhx72vvvsjxiz5mxk,task_subcomment,NA
+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",1352938800,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gcvicv5c5il3dfwvq4z6,task_description,resolved
+VisualEditor: Change markers don't propagate when generated paragraphs are unwrapped,"
+
+*** This bug has been marked as a duplicate of bug 41947 ***",1353108588,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gcvicv5c5il3dfwvq4z6,task_subcomment,NA
+[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",1352931660,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-btqaquo52pvsfg5ytjrc,task_description,resolved
+[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],1372934046,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-btqaquo52pvsfg5ytjrc,task_subcomment,NA
+[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 ***",1352932611,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-btqaquo52pvsfg5ytjrc,task_subcomment,NA
+[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.",1352931990,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-btqaquo52pvsfg5ytjrc,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"At the moment, prepending to lists is not obvious. I think most people would try to do it by pressing enter on the preceding line to create a new paragraph, then pressing the make (bulleted) list button.
+
+For some reason, this creates a list at the caret, but retains the blank paragraph afterwards (so you have list-para-list). Okay, so now you try to delete the para, but you can only deletes too much, for example merging the last list item on the first list with the first list item on the second list. In fact, pressing enter now works, but in any case the process is rather confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1352551740,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-54zoeovhyceutq4h2rxj,task_description,declined
+VisualEditor: Prepending to lists difficult,"Hmm, yes. I can certainly understand the case with (pre-existing) lists. But witness that neither of the two other editors mentioned put a slug (or indeed anything else) between the two adjoining lists created when one inserts a paragraph before a list and then presses the listify icon.
+
+(For Word, it would make no sense for them to because it's not two adjoining lists, just two adjoining list items; for GDoCs they just don't.)",1353757540,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"The ""weird blank paragraph"" is what a ""slug"" - a place in the editing interface where the user can insert some content. It needs to be there so that users can successfully place content between blocks, but it isn't an entire line (depending on your User Agent) - once you start entering content, it expands to be the same size as a ""real"" paragraph, however.
+
+An example of this is nested lists - in MediaWiki you can jump straight down to a second level of lists, but in HTML editing you still need to give the user some way to edit the list they're not in. This is why this wikitext:
+
+Hello
+** There
+
+... produces this in the VisualEditor:
+
+Hello
+* 
+** There
+
+... the middle ""line"" is a ""slug"" that will disappear once you save, but if you need to insert text that's where you can go.
+
+We're considering coming up with a little icon, perhaps a little like the cursor character, to make it clear that it's an insertion point rather than an actual blank line, but we're at early days yet.",1353723400,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,Any thoughts James on preventing the creation of that weird blank paragraph?,1353368318,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"Okay, right, figured it out. It's the randomly inserted blank paragraph that's annoying me. Even GDocs doesn't do that (it assumes you've got two lists next to each other); moreover, it's not the same behaviour as when you've got a paragraph next.",1352938178,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Firstly, I disagree with you about what users will expect. Behaviour in most
+> > visual editors, notably including Google Docs and Microsoft Word, is that you
+> > cannot prepend to a list other than by splitting the first item 
+> 
+> I believe going to a preceding paragraph and clicking the ""make list"" button
+> also prepends to a list in Word.
+
+Yeah; we may want to ape this, but it's a lot of work for relatively little benefit and I think we can punt it to a later date - see bug 42115.
+
+> Google Doc's list handling is different,
+> admittedly. I'm having trouble reminding myself of what annoyed me about the
+> VE's current response (""Error loading data from server: Invalid response from
+> server"") though -- so it could have been something relatively minor that just
+> bugged me for a while.
+
+Yes, sorry, we're midst-deploy right now, hence errors. Give us five minutes. :-)",1352935201,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,s/a preceding paragraph/the preceding paragraph (line)/,1352935050,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"(In reply to comment #1)
+> Firstly, I disagree with you about what users will expect. Behaviour in most
+> visual editors, notably including Google Docs and Microsoft Word, is that you
+> cannot prepend to a list other than by splitting the first item 
+
+I believe going to a preceding paragraph and clicking the ""make list"" button also prepends to a list in Word. Google Doc's list handling is different, admittedly. I'm having trouble reminding myself of what annoyed me about the VE's current response (""Error loading data from server: Invalid response from server"") though -- so it could have been something relatively minor that just bugged me for a while.",1352934930,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Prepending to lists difficult,"Firstly, I disagree with you about what users will expect. Behaviour in most visual editors, notably including Google Docs and Microsoft Word, is that you cannot prepend to a list other than by splitting the first item (i.e., by placing the cursor between the first bullet or enumerator and the start of the content on the first list item, and pressing 'Return').
+
+If you follow your instructions, you're creating a second, separate list before the original list, and then wanting the software to magically know that you want them merged, which is somewhat complex behaviour that we don't currently support well, so we should create a bug for that. However, I'm inclined to close this as a WONTFIX. Thoughts?",1352930949,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-54zoeovhyceutq4h2rxj,task_subcomment,NA
+VisualEditor: Restore lost Change Markers,"In the change-markers2 branch, we have some trouble.
+
+In a list item, there will be a <p> tag with change markers if I edit the content of the <li>. Roan decided to destroy those, and so did I. The change markers should instead be propagated to the <li>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352509140,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-bxfy5lj3p2kmooagyw4k,task_description,resolved
+VisualEditor: Restore lost Change Markers,*** Bug 42120 has been marked as a duplicate of this bug. ***,1353108588,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bxfy5lj3p2kmooagyw4k,task_subcomment,NA
+VisualEditor: Restore lost Change Markers,https://gerrit.wikimedia.org/r/33840,1353107651,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bxfy5lj3p2kmooagyw4k,task_subcomment,NA
+"VisualEditor: Post-uirewrite, list button does not behave as expected","
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1352499300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bzfy62f6eeawy7qsikz2,task_description,resolved
+"VisualEditor: Post-uirewrite, list button does not behave as expected",https://gerrit.wikimedia.org/r/32664,1352499455,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-bzfy62f6eeawy7qsikz2,task_subcomment,NA
+VisualEditor: Overflow and background messed up in save dialog workflow,"Screenshot
+
+See screenshot. Legal text is floating loose, and the heading in the toolbar is overlapping the buttons.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9759}",1352465220,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-r3cecfzae44mq2jgxqtv,task_description,resolved
+VisualEditor: Overflow and background messed up in save dialog workflow,//**content hidden as private in Bugzilla**//,1353103492,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-r3cecfzae44mq2jgxqtv,task_subcomment,NA
+VisualEditor: Overflow and background messed up in save dialog workflow,Confirmed on master.,1352466731,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-r3cecfzae44mq2jgxqtv,task_subcomment,NA
+VisualEditor: Overflow and background messed up in save dialog workflow,As well as the arrow in the save button.,1352466157,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-r3cecfzae44mq2jgxqtv,task_subcomment,NA
+VisualEditor: Overflow and background messed up in save dialog workflow,This was fixed in https://gerrit.wikimedia.org/r/#/c/31868/,1352465630,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-r3cecfzae44mq2jgxqtv,task_subcomment,NA
+VisualEditor: Parsoid is sent text outside of any node for the first line of a new article,"Steps to repro:
+
+1. Open new page in VE.
+
+2. Click on first line, enter text, enter newline, enter more text.
+
+3. Click save.
+
+Expected behavior: Two paragraphs.
+
+Actual behavior: One paragraph with a single line break where there should be two.
+
+Tested locally and found that Parsoid's web service gets the DOM as something like ""First line<p>Second line</p>"", which it can't handle correctly (the fix breaks many other parser tests).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352420400,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-j4syqnzwdunhoucwx6o6,task_description,resolved
+VisualEditor: Parsoid is sent text outside of any node for the first line of a new article,"
+
+*** This bug has been marked as a duplicate of bug 42121 ***",1353133977,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j4syqnzwdunhoucwx6o6,task_subcomment,NA
+VisualEditor: Parsoid is sent text outside of any node for the first line of a new article,"Fixed by Roan in between filing and now - Parsoid now receives ""<p data-parsoid=""{&quot;dsr&quot;:[0,23]}"">First line</p><p data-parsoid=""{&quot;dsr&quot;:[0,23]}"">Second line</p>"".",1353133921,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j4syqnzwdunhoucwx6o6,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"Parsoid currently wraps the first newline in a <pre> in <span typeof=""mw:Placeholder""> , see also bug 41725 where I reported a bug in this behavior. Because of the way this interacts with VisualEditor, I would like Parsoid to drop this wrapping altogether. The reason for mw:Placeholder wrapping is supposed to be to protect things from VE, but we don't need it here and it's actually causing problems.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351978800,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_description,resolved
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"The right kind of protection is removed in https://gerrit.wikimedia.org/r/#/c/32003/. We had to perform some tricks to preserve the newline after the opening pre tag in the treebuilder. The HTML spec makes that newline optional, so it seems that DOM implementations are free to discard it and still be compliant with the spec. This might or might not bite you.",1352225021,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"The pre protection, that is.",1352160813,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"Ooops, sorry- read that too fast on Friday and just acted based on that distant memory today ;) The protection is back now. Will see about removing the protection later.",1352160799,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,"(In reply to comment #1)
+> Great that you are handling <br> now ;) Removed the protection in
+> https://gerrit.wikimedia.org/r/#/c/31958/.
+I wasn't talking about <br>s at all, I was talking about the first newline in a <pre>.",1352160113,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>,Great that you are handling <br> now ;) Removed the protection in https://gerrit.wikimedia.org/r/#/c/31958/.,1352154328,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-vsa4dipmuhxhvfjv3ueq,task_subcomment,NA
+VisualEditor: Deal with mw:Placeholder span wrapping the first newline in a <pre>,"To distinguish between <pre>Foo</pre> and <pre>\nFoo</pre>, Parsoid gives us HTML like <pre><span typeof=""mw:Placeholder"">\n</span>Foo</pre> for the latter. We don't currently have any special handling for this placeholder in VE, so it shows up as an inline alien.
+
+I'm asking the Parsoid team to remove it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351915500,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rq2tsnu6ypd4j65ev7c2,task_description,resolved
+VisualEditor: Deal with mw:Placeholder span wrapping the first newline in a <pre>,"Parsoid removed this behavior as requested, and with https://gerrit.wikimedia.org/r/#/c/32260/ the editor now handles <pre>s correctly.",1352492571,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rq2tsnu6ypd4j65ev7c2,task_subcomment,NA
+VisualEditor: z-index problems in Monobook,"Screenshot of messed-up Monobook integration in Chrome
+
+The VE integration in Monobook is messed up, see screenshot. The toolbar is positioned too high, obscuring the content actions tab bar, except for the edit tab which protrudes through the toolbar. The toolbar is also off to the left a bit. The font size in the edit area is way too small, and the font size in the save dialog is way too big.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10131}",1351914420,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_description,resolved
+VisualEditor: z-index problems in Monobook,I'm going to remark this as closed - this breakage is bug 50652 which I believe we've just fixed.,1372893825,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_subcomment,NA
+VisualEditor: z-index problems in Monobook,"(In reply to comment #2)
+> Hope I'm not stepping on any toes by reopening, but this still seems to be an
+> issue. 
+> 
+> See http://i.imgur.com/h8SOdGB.png and more drastically
+> http://i.imgur.com/maUlOMv.png (the latter is when resizing the window to be
+> moderately smaller).
+Renamed bug to be applicable to these screenshots.",1372892844,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_subcomment,NA
+VisualEditor: z-index problems in Monobook,"**KilliondudeWP** wrote:
+
+Hope I'm not stepping on any toes by reopening, but this still seems to be an issue. 
+
+See http://i.imgur.com/h8SOdGB.png and more drastically http://i.imgur.com/maUlOMv.png (the latter is when resizing the window to be moderately smaller).",1372892746,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_subcomment,NA
+VisualEditor: z-index problems in Monobook,"Most of these issues were actually due to me messing up my Common.css, sorry :(
+
+Trevor fixed the remaining problems in https://gerrit.wikimedia.org/r/#/c/31943/",1352155670,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ot6puhxaw7ez7zuaeuyr,task_subcomment,NA
+VisualEditor: Newlines in <pre> render wrongly,"Given the following wikitext:
+
+
+<pre>
+Foo
+Bar
+Baz
+Quux
+</pre>
+
+the CE rendering I get is a pre with Foo↵Bar↵Baz↵Quux , rather than a pre with actual line breaks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351912620,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-e52bbyzcqb4xr73axz3g,task_description,resolved
+VisualEditor: Newlines in <pre> render wrongly,Fixed by Roan some time ago.,1354155736,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e52bbyzcqb4xr73axz3g,task_subcomment,NA
+VisualEditor: Converting format across 2 lists with paragraphs in between fails,"1. Create a list, 2 paragraphs and then another list
+2. Select from inside the first list to inside the second list
+3. Change the format to Heading 2 using the toolbar
+4. See errors in the console
+
+This is to do with a bug in the ve.FormatAction class's convert function.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351282140,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-jqy4wf5ol4o3dp66hs7r,task_description,resolved
+VisualEditor: Converting format across 2 lists with paragraphs in between fails,https://gerrit.wikimedia.org/r/#/c/30295/,1351290052,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jqy4wf5ol4o3dp66hs7r,task_subcomment,NA
+VisualEditor: Emptying paragraph in Firefox with backspace adds <br _moz_dirty>,"**Author:** `orbit`
+
+**Description:**
+Firefox naturally leaves a <br _moz_dirty> when the contents of a paragraph has been deleted. There are 2 cases, deleting text in a paragraph and deleting text in a paragraph in a list item.
+
+In the case of a paragraph NOT within a list item, the DOM is:
+<p><br _moz_dirty></p>. ve.ce.TextNode onUpdate cleans the parent, removing the <br>. 
+
+In the case of a paragraph WITHIN a list item, the DOM is:
+<li><p></p><br _moz_dirty></li>. Cleaning the parent doesn't remove the br, but parent.parent does. Maybe this needs to traverse up to the highest splittable node? 
+
+In both cases the focus does not return to the slug because the surface is locked, preventing showSelection (this is in the onChange method).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350672600,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cchu7wayqp2w3m4ikxkf,task_description,resolved
+VisualEditor: Emptying paragraph in Firefox with backspace adds <br _moz_dirty>,Fixed here: https://gerrit.wikimedia.org/r/#/c/37162/,1354755521,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-cchu7wayqp2w3m4ikxkf,task_subcomment,NA
+VisualEditor: Emptying paragraph in Firefox with backspace adds <br _moz_dirty>,I already found a few slightly different ways to solve this problem. After I will choose the best one I will update this ticket and send it for review to gerrit.,1351107837,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-cchu7wayqp2w3m4ikxkf,task_subcomment,NA
+VisualEditor: First 'space' in Firefox strands previous content in DIV outside of P element in new document,"Go to a non-existent document and press 'Create'
+
+1) Press a
+   Expect: ""a"" in a <P> element
+   Get: ""a"" in a <P> element
+2) Press <space>
+   Expect: ""a "" in a <P> element
+   Get: ""a"" in the document <DIV> followed by a newline, then "" "" in a <P> element
+3) Press b
+   Expect: ""a b"" in a <P> element
+   Get: ""a"" in the document <DIV> followed by a newline, then "" b"" in a <P> element
+4) Press <enter>
+   Expect: ""a b"" in a <P> element; a newline; then a <P> with a slug <SPAN>
+   Get: "" b"" in a <P> element; a newline; a <P> with a slug <SPAN>; another newline; then ""a"" in the document <DIV>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350582840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zkqsllah4f32kfkyu6pq,task_description,resolved
+VisualEditor: First 'space' in Firefox strands previous content in DIV outside of P element in new document,"**orbit** wrote:
+
+This has been fixed by Inez's ""Is there data"" change:
+https://gerrit.wikimedia.org/r/#/c/28463/",1350583392,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-zkqsllah4f32kfkyu6pq,task_subcomment,NA
+VisualEditor: Deleting selection does not delete selected list bullet,"1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press: a b Enter c d
+3) Make ""cd"" a list item
+4) Press Delete
+
+
+Expected:
+
+ad
+
+
+Actual:
+
+a
+
+・ d
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350553800,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-raetvmzuudiefybcm2if,task_description,declined
+VisualEditor: Deleting selection does not delete selected list bullet,"**orbit** wrote:
+
+Ah yeah, this is as expected. We're not currently handling adoption of list items into paragraphs. This type of selection + delete will work from a paragraph into another paragraph or a paragraph into heading, but just not for lists yet.",1350672888,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-raetvmzuudiefybcm2if,task_subcomment,NA
+VisualEditor: Deleting selection does not delete selected list bullet,"Sorry I forgot a step!
+
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press: a b Enter c d
+3) Make ""cd"" a list item
+3) With the mouse, select b and c
+4) Press Delete",1350614576,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-raetvmzuudiefybcm2if,task_subcomment,NA
+VisualEditor: Deleting selection does not delete selected list bullet,"**orbit** wrote:
+
+Where is your cursor when you press Delete? I can't think of any circumstance where a single press of Delete should remove 2 characters (ABCD -> AD) as you expected. Also, what browser are you using?",1350587124,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-raetvmzuudiefybcm2if,task_subcomment,NA
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,"The available actions in the link dialog are 3 icon-only buttons (see attachment):
+- ""no parking"" symbol
+- check symbol
+- cross symbol
+
+The difference between ""no parking"" and ""cross"" is not obvious.
+I had to try each to see which one means cancel and which one means ""remove link"".
+
+My point is: Tooltips would be useful here.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350546360,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_description,resolved
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,Merged,1354758675,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_subcomment,NA
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,"Added tooltips to inspector controls.
+Patched in https://gerrit.wikimedia.org/r/37171
+
+Awaiting review.",1354756810,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_subcomment,NA
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,Confirmed as missing.,1350580682,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_subcomment,NA
+VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog,"Created attachment 11204
+screenshot
+
+**Attached**: {F9914}",1350546392,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-fqt5fy3rkv2cyagloqrl,task_subcomment,NA
+VisualEditor: Firefox is not displaying cursor in slugs,"**Author:** `orbit`
+
+**Description:**
+Steps to reproduce:
+Place cursor at the end of a paragraph.
+Hit ""Enter"" to create a new paragraph.
+Cursor is not shown in the new paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350496140,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cvrmtrl6akf6grx2t2dt,task_description,resolved
+VisualEditor: Firefox is not displaying cursor in slugs,Fixed in https://gerrit.wikimedia.org/r/#/c/28401/,1350502148,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-cvrmtrl6akf6grx2t2dt,task_subcomment,NA
+CTRL-X does not remove selected text,"Steps:
+1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Select a word or character
+3) Press CTRL-X or select ""Cut"" in the context menu
+4) Text is copied, but not removed
+
+It guess many Wikimedia editors use cut-paste to reorder information, so it seems like a rather important feature to have.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Linux
+**Platform**: PC",1350437460,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-7oxigo4kmioch62jccio,task_description,resolved
+CTRL-X does not remove selected text,"**orbit** wrote:
+
+I found what's happening. This is now fixed but not yet released.",1350455700,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7oxigo4kmioch62jccio,task_subcomment,NA
+CTRL-X does not remove selected text,"**orbit** wrote:
+
+Yeah, it definitely is. I'll look into what happened with our cut support.",1350451005,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7oxigo4kmioch62jccio,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,"Steps:
+1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press: a Enter b Enter c Enter d Enter (that creates 4 paragraphs, each containing a single letter)
+3) With the mouse, select b and c
+4) Press Delete
+5) Wild pawn appears ♙
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=41067",1350379140,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-rw22m4geg4i4wedyx35p,task_description,resolved
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,"Verified.
+
+Test procedure: per comment 5, reporter retested the issue and can't reproduce the bug again.",1350454390,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,I (reporter) confirm it is fixed.,1350451754,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,"**orbit** wrote:
+
+This has been fixed and released to mediawiki.org.",1350450594,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,That's a Firefox issue only.,1350414414,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,"Same with ""Backspace"" instead of ""Delete"" at step 4.",1350379334,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when deleting two paragraphs,[ Confirming bug. See also bug 41067. ],1350379291,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-rw22m4geg4i4wedyx35p,task_subcomment,NA
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,"1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Put your cursor anywhere in the text
+3) Press CTRL+A to select everything
+4) Press Delete
+5) PROBLEM: Nothing happens. No content is removed.
+
+Pressing Backspace instead of Delete works, though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350378600,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-cv2eddejijgeuiyzx5iv,task_description,resolved
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,Fixed here: https://gerrit.wikimedia.org/r/#/c/28790/,1350692324,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-cv2eddejijgeuiyzx5iv,task_subcomment,NA
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,"Okay, thank you to have rechecked.
+
+I guess we should settle on ""Unconsistent behavior selecting all then deleting content"".
+
+[ Confirming bug. ]",1350392100,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-cv2eddejijgeuiyzx5iv,task_subcomment,NA
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,"@Dereckson:
+I just re-tried and you are right.
+I changed the bug's title but can't change the description unfortunately.
+Backspace has the exact same problem, contrarily to what my description was saying.",1350379777,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-cv2eddejijgeuiyzx5iv,task_subcomment,NA
+VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete,"Can't confirm the bug.
+
+I've a different behavior with Firefox 15.0.1: All the content is deleted except a sentence (currently ""Also, there strange chess symbols appear...."").",1350379388,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-cv2eddejijgeuiyzx5iv,task_subcomment,NA
+VisualEditor: Backspace does not work after removing all content,"1) Go to http://www.mediawiki.org/wiki/Special:VisualEditorSandbox with Firefox
+2) Put your cursor anywhere in the text
+3) Press CTRL-A (or select all text with the mouse)
+4) Press ""Backspace"". All content disappears.
+5) Type ""a"".
+6) Press ""Backspace"". Problem: ""a"" is not removed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350378480,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-4ygvi66vjgjggrrbm2gv,task_description,resolved
+VisualEditor: Backspace does not work after removing all content,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306609,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4ygvi66vjgjggrrbm2gv,task_subcomment,NA
+VisualEditor: Backspace does not work after removing all content,Now fixed in master.,1354217422,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4ygvi66vjgjggrrbm2gv,task_subcomment,NA
+VisualEditor: Backspace does not work after removing all content,"Confirmed on Mac/Firefox too (no issue on Chrome, Safari)",1350403427,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4ygvi66vjgjggrrbm2gv,task_subcomment,NA
+VisualEditor: Backspace in list: deleted character re-appears,"Steps:
+0) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+1) Between two simple text paragraph, insert a new paragraph by pressing ""Enter"".
+2) Click the ""bullet list"" button.
+3) Type ""a"".
+4) Press ""Backspace"". ""a"" is removed, and the next paragraph moves down a bit.
+5) Press ""Backspace"" again.
+6) The ""a"" reappears.
+
+Problems: The move at step 4 and the miracle at step 6.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1350376200,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-esphifhyt57uf6xcfxuh,task_description,resolved
+VisualEditor: Backspace in list: deleted character re-appears,Confirmed the fix in betalabs and test2.,1414444876,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-esphifhyt57uf6xcfxuh,task_subcomment,NA
+VisualEditor: Backspace in list: deleted character re-appears,"**orbit** wrote:
+
+Just leaving a note: This is a Firefox problem where the browser adds a <br _moz_dirty /> within the list item:
+<li>
+  <p></p>
+  <br _moz_dirty/>
+</li>",1350669002,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-esphifhyt57uf6xcfxuh,task_subcomment,NA
+VisualEditor: Backspace in list: deleted character re-appears,"**orbit** wrote:
+
+Yep, this is verified. We should have a fix soon.",1350591670,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-esphifhyt57uf6xcfxuh,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,"Steps:
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Click at the end of any list item
+3) Press Enter
+4) As expected, a new line is created in the list
+5) PROBLEM: This cursor blinks at the beginning of the previous line (the one in which the cursor was before pressing Enter
+6) When I begin typing, the text appears in the new line, so I guess the ""real cursor"" is actually at the right place, but its visualisation is misplaced.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350361740,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-bwuzjaia5wetefisy2ta,task_description,resolved
+VisualEditor: Cursor appears misplaced after adding item to list,I (original reporter) confirm the fix.,1351564499,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,Fixed by this changeset: https://gerrit.wikimedia.org/r/#/c/28401/,1350604430,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,"I think I know what's the issue, please keep assigned to me.",1350414315,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,Assigning to Christian given his heroic work on this last night.,1350402366,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,"**orbit** wrote:
+
+Appears to be a Firefox thing (this is a note to myself for later).",1350377911,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: Cursor appears misplaced after adding item to list,"About step 5:
+Also, it only blinks once.
+In some cases it does not blink at all (invisible), but that is a different problem.",1350361928,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-bwuzjaia5wetefisy2ta,task_subcomment,NA
+VisualEditor: SHIFT-LEFT deletes text in lists,"Steps to reproduce:
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press ""Edit""
+3) Click at the end of any item in a list
+4) Press SHIFT and LEFT, maintaining them pressed for a while
+
+Expected behavior: Text is selected
+Actual behavior: Text is deleted, leaving only some fragments near the bullets
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1350356940,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-2z4m5xpg5gzvx6kbldfe,task_description,resolved
+VisualEditor: SHIFT-LEFT deletes text in lists,"I (original reporter) I confirm the fix, great work :-)",1350437137,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-2z4m5xpg5gzvx6kbldfe,task_subcomment,NA
+VisualEditor: SHIFT-LEFT deletes text in lists,"**orbit** wrote:
+
+This is happening in Firefox and has been fixed. The patch should appear on mediawiki.org 10/16.",1350377650,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2z4m5xpg5gzvx6kbldfe,task_subcomment,NA
+VisualEditor: Pasting text doesn't work,"I'm testing on mediawiki.org but am creating a bug report since these haven't been mentioned before so I don't believe they've been fixed in git.
+
+If I try to paste some text in the editor, the paragraphs in it get stuck together, and it gets '↵' character inserted periodically, at places not corresponding to any line breaks in the text. Example:
+
+If you want your user to be able to configure your extension, you'll ↵need to provide one or more configuration variables. It is a good idea ↵to give those variables a unique name. They should also follow MediaWiki↵ naming conventions
+
+This happens both with pasting with Ctrl+v and with mouse. Firefox 16.0.1 on Windows XP SP 2.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350339660,PHID-USER-asiusr6cw73okn35tobw,False,PHID-TASK-47tdq27eh5j4qgr4lw5p,task_description,resolved
+VisualEditor: Pasting text doesn't work,"**orbit** wrote:
+
+Thanks for the additional detail. I found the problem and have committed a fix (https://gerrit.wikimedia.org/r/#/c/28628/). 
+
+Since we don't have a HTML -> Linear Model converter, copy and paste from external sources will paste as plain text only, so the 3 paragraphs will end up collapsed. This is as-expected. There is another enhancement request (https://bugzilla.wikimedia.org/show_bug.cgi?id=33105) to better support pasting from external sources.",1350601375,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-47tdq27eh5j4qgr4lw5p,task_subcomment,NA
+VisualEditor: Pasting text doesn't work,"I am copying the first three paragraphs from http://www.mediawiki.org/wiki/Manual:Developing_extensions#Making_your_extension_user_configurable (starting with ""If you want your user to be able to configure"" and ending with ""configuration variables in your installation notes."") I am pasting by clicking in VisualEditor at the end of ""answers to many of your questions."" paragraph and pressing Ctrl+V.
+
+If I paste the text in a text editor, and then copy that text and paste it in the VisualEditor, the paragraphs are merged together (with an empty string) but the '↵' character does not appear.
+
+This also happens with Firefox 11.0 on Ubuntu 10.10. It does not happen with Opera 11.50 on Ubuntu 10.10.",1350459248,PHID-USER-asiusr6cw73okn35tobw,False,PHID-TASK-47tdq27eh5j4qgr4lw5p,task_subcomment,NA
+VisualEditor: Pasting text doesn't work,"**orbit** wrote:
+
+I can't reproduce this on Firefox. Can you give me more details about the type of content you're pasting and where you're pasting it? For example, ""I'm copying a couple paragraphs from a normal HTML page and pasting it into a headline in the Visual Editor"".",1350450930,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-47tdq27eh5j4qgr4lw5p,task_subcomment,NA
+There's no way to specify the directionality of a paragraph,"In MediaWiki pages it is frequently required to write a paragraph in a different
+language, and possibly also with different directionality. For example, a
+quotation in English in an article in the Hebrew Wikipedia.
+
+With the plain wikitext editor this can be achieved using HTML, for example
+<div lang=""en"" dir=""ltr"">. In some Wikipedias there are templates that do
+this.
+
+There must be a way to do this using the VE GUI. For example, the user can
+select the text in a different language, open a dialog with ""Paragraph language
+properties"" and select ""Language: English"" and ""Directionality: Left-to-right"".
+
+For reference and further details:
+https://www.mediawiki.org/wiki/VisualEditor/Bidirectional_text_requirements
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350148320,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-lldcsju4qcxyd4jmidkt,task_description,resolved
+There's no way to specify the directionality of a paragraph,"
+
+*** This bug has been marked as a duplicate of bug 41009 ***",1350158076,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lldcsju4qcxyd4jmidkt,task_subcomment,NA
+VisualEditor: Disabled toolbar Buttons should not respond to clicks,"screenshot of the problem
+
+When you click a button that is disabled, it still gives you the visual feedback of being pressed.
+
+The screenshot shows me clicking the ""reduce indent level"" button while it is disabled. Note the shadow border that is added when you click it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9583}",1350045780,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-n7gptyps7udhncfic5rt,task_description,resolved
+VisualEditor: Disabled toolbar Buttons should not respond to clicks,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306613,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n7gptyps7udhncfic5rt,task_subcomment,NA
+wikibugs-l@ does not follow all products/components,"Not sure how the exact scope of wikibugs-l@ is defined (which products/components it is expected to cover) and what the expectations of people watching wikibugs-l@ in Bugzilla are, but wikibugs-l@ is NOT subscribed to ALL components/products.
+
+After spending 20min of investigating:
+
+Product level:
+To get bugmail for any changes in the products Cortado, Datasets, Huggle, mwEmbed, Parsoid, (Security,) VisualEditor, the only chance is to follow the default assignee listed on https://bugzilla.wikimedia.org/describecomponents.cgi . But that also means receiving all other bugmail created by her/him no matter which product the changes were made in.
+
+Components level:
+Several components in the ""MediaWiki extensions"" product that don't have the Default Assignee set to wikibugs-l@ do not always have wikibugs-l@ at least in the default CC list.
+Same for ""VIAF"" and ""WM-Bot"" components in the ""Tools"" product.
+Same for ""lucene-search-2"" and ""Prototype server"" components in the ""Wikimedia"" product.
+Same for ""bots"" in ""Wikimedia Labs"".
+
+
+(Fixing bug 37105 would be a different approach to solve part of the problem.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350032400,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-gxlesrzwrsipkfsxba4o,task_description,resolved
+wikibugs-l@ does not follow all products/components,"(In reply to comment #2)
+> You do realise that it was already setup as a Global Watcher in the email
+> config?
+
+Then something's broken. I do not get all bugmail always.
+
+I watch wikibugs-l@, I just commented on bug 22816, I didn't receive bugmail, because wikibugs-l@ is default assignee for that component, but that specific report had a non-default assignee. That means wikibugs-l@lists.wikimedia.org must still also be set as default CC to trigger bugmail.",1353163615,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-gxlesrzwrsipkfsxba4o,task_subcomment,NA
+wikibugs-l@ does not follow all products/components,"Darrn, of course I didn't (plus I had the vague feeling of missing out on some bugmail). That address was in the default CC of quite some components, but I shouldn't assume that people clean up duplications. :)",1350049808,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-gxlesrzwrsipkfsxba4o,task_subcomment,NA
+wikibugs-l@ does not follow all products/components,You do realise that it was already setup as a Global Watcher in the email config?,1350048728,PHID-USER-6vzzsmi22zem6yttr6vp,True,PHID-TASK-gxlesrzwrsipkfsxba4o,task_subcomment,NA
+wikibugs-l@ does not follow all products/components,Fixed. Now wikibugs-l@ should really report ALL changes to ANY bug reports (except for Security and deprecated products that are not open to new reports).,1350036846,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-gxlesrzwrsipkfsxba4o,task_subcomment,NA
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new","Right now the ""This is a [minor edit]"" text in the save dialog tries to take the user to a new page in the current context, prompting them to abandon their changes (or not leave). This is sub-optimal. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1349379660,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jykflci4lybdcwkdegx7,task_description,resolved
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new",Note which milestone this met.,1355171026,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jykflci4lybdcwkdegx7,task_subcomment,NA
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new",Merged.,1354758513,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-jykflci4lybdcwkdegx7,task_subcomment,NA
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new",Changed to target=_blank,1354752982,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-jykflci4lybdcwkdegx7,task_subcomment,NA
+"VisualEditor: Save dialog ""minor edit"" link should either give a pop-up explanation or target=_new","Funny enough, in the current edit mode the minor edit link takes you away from editing.   AFAIK, the taget attribute cannot be added to a link wikitext.  Solution is to open the minor edit page in a new tab by setting target: _new with jQuery.
+
+Patch in https://gerrit.wikimedia.org/r/37154",1354751276,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-jykflci4lybdcwkdegx7,task_subcomment,NA
+VisualEditor: Inline switching of styling mode does not correctly updating typed text when @EOL,"This is a bug in the functionality implemented for bug 33140
+
+Platform: Safari 6, Mac Mountain Lion
+
+Insert cursor after the . of the Note in the lede of the VisualEditor:Test page (end of line).
+
+Now press ctrl-b
+type: text is in bold
+Press ctrl-b again
+type: new text is STILL in bold, but should be non-bold
+Press ctrl-b again
+type: The previous block is rerendered to be non-bold and the new text is rendered as bold.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1349371140,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-zlrtgjuxyb4v4l2qepry,task_description,declined
+VisualEditor: Inline switching of styling mode does not correctly updating typed text when @EOL,"**orbit** wrote:
+
+I can't reproduce this. Additional work has been done on insertAnnotations, so this was likely only a bug for a day or so. Please re-open and provide more information if I'm incorrect.",1350000478,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zlrtgjuxyb4v4l2qepry,task_subcomment,NA
+VisualEditor: Selection is wrongly restored on undo,"Steps to re-create:
+* Go to a new page, insert the word ""Fascinating""
+* Select it (double-click, click-drag or select-all)
+* Press a list button, and then undo
+
+What happens: The word ""Fascinating"" de-lists; the selection is set to ""scinati"".
+ 
+What should happen: The word ""Fascinating"" de-lists; the selection is set to ""Fascinating"".
+ 
+* Again, press a list button, and then undo
+
+What happens: The word ""Fascinating"" de-lists; the selection is set to ""ina"".
+ 
+What should happen: The word ""Fascinating"" de-lists; the selection is set to ""scinati"".
+ 
+* Again, press a list button, and then undo
+
+What happens: The word ""Fascinating"" de-lists; the selection appears to have disappeared.
+ 
+What should happen: The word ""Fascinating"" de-lists; the selection is set to ""ina"".
+
+Etc. :-) 
+
+Rob suggested that it was likely an issue in Transaction Builder?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348700340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dzuii7n6goxb7ffjhlad,task_description,resolved
+VisualEditor: Selection is wrongly restored on undo,Noting bugs closed in the 2012-10-15 release.,1351534203,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dzuii7n6goxb7ffjhlad,task_subcomment,NA
+VisualEditor: Selection is wrongly restored on undo,Fixed in latest deployment.,1350326683,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dzuii7n6goxb7ffjhlad,task_subcomment,NA
+labs-nfs1 full again,"[ve-roundtrip2] ~ $ sudo du -sh /home/ori
+16M	/home/ori
+[ve-roundtrip2] ~ $ sudo df -h /home/ori
+Filesystem                               Size  Used Avail Use% Mounted on
+labs-nfs1:/export/home/visualeditor/ori   18G   17G     0 100% /home/ori
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348169460,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-rwdzpvdya3fyeweyik45,task_description,resolved
+labs-nfs1 full again,We cleaned up some space. I'm going to be moving this to gluster soon.,1348180945,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-rwdzpvdya3fyeweyik45,task_subcomment,NA
+VisualEditor: Creating a link over-writes any existing annotations on the text,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348000500,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qwmhk54ep4zitmtvbaik,task_description,resolved
+VisualEditor: Creating a link over-writes any existing annotations on the text,Regression fixed in https://gerrit.wikimedia.org/r/24643,1348271354,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-qwmhk54ep4zitmtvbaik,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"Assuming we implement bug 39558. That means the counter in the corner of the save dialog will be decreasing more than 1 per character on average.
+
+English users will likely not notice it as quickly, but € (EURO SYMBOL) for instance is 3 bytes. And in foreign languages it will be more common entirely.
+
+Right now the counter has no unit, which would be confusing (the natural expectation is to assume character count). We can add a unit word ""# bytes"" instead. But I'm not sure that is an improvement, do we want to face users with that?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=4715",1346892540,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7vr2tsadkbk7lzyzolas,task_description,resolved
+VisualEditor: Edit summary length counter confusing when in bytes,Merged and to be deployed in wmf12 train.,1347900984,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"(In reply to comment #2)
+> Appending "" bytes"" seems like a reasonable compromise here (though the i18n
+> will be fun).
+
+I've -1-ed the patch mentioned in comment 3 for not being understandable to users. We should provide them with a reasonable indication of how many more characters they can insert.
+
+Is it possible to do something with the average number of bytes per character for what's already been typed, and give an indication like ""~n characters remaining""?
+
+P.s. issue should be closed when patch is merged, not when it's submitted.",1347392907,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"Went with bytes for the time being.  Will change when core bug fixed.
+Patched in https://gerrit.wikimedia.org/r/23451",1347392179,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"Appending "" bytes"" seems like a reasonable compromise here (though the i18n will be fun).",1346949530,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Edit summary length counter confusing when in bytes,"Note that this is a consequence of bug 4715. Right now we just cut off the comment if it is too long; adding a confusing, but correct counter helps a lot.
+
+Now to the question: I think adding the word ""bytes"" would help, since (a) some people know what a byte is and (b) even those who don't and see that the counter differs from a character counter may realize that ""bytes"" can mean something else. They probably don't assume it is a character counter if there is an unknown term behind the number and so they have less expectation and get less confused if the counter differs from their expectation.",1346919604,PHID-USER-j27ofmod3h6tzafsujyq,False,PHID-TASK-7vr2tsadkbk7lzyzolas,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"Submitting the form on Enter in the current UI goes against all expectations.
+
+It is hardcoded in the javascript to override the default behavior (browsers are actually quite sane in this case and know not to auto-submit from a textarea because that's bad).
+
+Either make it not a text area or make it not submit on Enter.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52133",1346892300,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-khmajutgdejtygs4iuzr,task_description,resolved
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"(In reply to comment #5)
+> Maybe, maybe not. Either way, that's a separate request.
+> [...]
+> If you want, file a separate ticket to turn it into a single-line text input.
+
+bug 52133",1374903726,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"(In reply to comment #4)
+> Do we really need a textarea?
+> 
+> Newlines are not shown in page history.
+
+Maybe, maybe not. Either way, that's a separate request.
+
+Besides, when it is a text input Enter will submit the form automatically (browser behavior) which is good. So this change had to be made either way. If you want, file a separate ticket to turn it into a single-line text input.
+
+Note that textarea provides another thing besides multi-line: wrapping.
+
+It is much nicer to type a long line in a textarea then a flat input because there is no need to use the horrible scrubbing behavior that browsers have (select-dragging or keyboard arrows only). I've encountered numerous times during usability studies that a user thought the begin of the input was lost when it was no longer visible (there is no visual indication that it is still there, e.g. scroll or whatever). Or that the end was lost (when they focus another element, other elements scroll back to the begin).",1347383752,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"Do we really need a textarea?
+
+Newlines are not shown in page history.",1347381643,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"No, previously it was a text input.
+Patched in https://gerrit.wikimedia.org/r/23422",1347381271,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"(In reply to comment #1)
+> Actually, this is exactly the current behaviour of the edit summary box; see
+> bug 38042 and bug 38735 (the last one submitted by you :-)).
+
+Interesting. Was it a textarea back then?",1347374675,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary),"Actually, this is exactly the current behaviour of the edit summary box; see bug 38042 and bug 38735 (the last one submitted by you :-)).",1346948784,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-khmajutgdejtygs4iuzr,task_subcomment,NA
+VisualEditor: By-word selection fails when mouse moves,"Word-by-word text selection by mouse fails as soon as the user moves the mouse.
+
+Examples: If a user double clicks on ""Lorem"" in a ""Lorem ipsum"" string and then moves the mouse to, say, after the letter ""p"", the selected text becomes just ""Lorem ip"", rather than the entirety of both words. If a user double clicks on a word, it becomes entirely highlighted, but if the mouse is moved, the only parts highlighted are the letters between the beginning of the word and the cursor.
+
+The expected behavior is that after the user double clicks, the selection expands/shrinks only word-by-word, with the original selected word always highlighted.
+
+Tested on Chrome on Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1346752740,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-wkopxt22hpjopb4jwgk3,task_description,resolved
+VisualEditor: By-word selection fails when mouse moves,"**orbit** wrote:
+
+This is fixed due to the selection changes from Inez.",1350001255,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wkopxt22hpjopb4jwgk3,task_subcomment,NA
+VisualEditor: By-word selection fails when mouse moves,"**orbit** wrote:
+
+To clarify the steps to reproduce, a user must click-release-click-hold and move the mouse.",1348875034,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wkopxt22hpjopb4jwgk3,task_subcomment,NA
+VisualEditor: UI restores #toc as inline-block instead of table,"Bug in action
+
+When pressing Edit in VE mode, and then aborting (e.g. Parsoid is not running and the page is restored) the table of contents becomes an inline block which looks rather odd.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9671}",1346200560,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_description,resolved
+VisualEditor: UI restores #toc as inline-block instead of table,Fixed in I57532e556eafe783c8638b25fce502a158597c97.,1346830749,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_subcomment,NA
+VisualEditor: UI restores #toc as inline-block instead of table,"@TrevorParscal: .ve-init-mw-viewPageTarget-pageToc uses inline-block, why?",1346239596,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_subcomment,NA
+VisualEditor: UI restores #toc as inline-block instead of table,"(In reply to comment #1)
+> [ Adding design keyword. ]
+
+Why? This is just a javascript issue, there is no design question. It should look like it does on regular page views.",1346239381,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_subcomment,NA
+VisualEditor: UI restores #toc as inline-block instead of table,[ Adding design keyword. ],1346237488,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-g5vhskgl4jngc5bjv6k7,task_subcomment,NA
+"VisualEditor: Annotate the DOM to indicate on round-trip what's changed, so Parsoid can do partial serialisation","Per request of Parsoid team. Not sure if this is already a bug? Apologies if so. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345851360,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-z2cdsxjpkxttsbnu4d2x,task_description,resolved
+"VisualEditor: Annotate the DOM to indicate on round-trip what's changed, so Parsoid can do partial serialisation",https://gerrit.wikimedia.org/r/#/c/31990/,1352492599,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-z2cdsxjpkxttsbnu4d2x,task_subcomment,NA
+VisualEditor: DOM out of sync with data model when typing next to a link,"Reproduce by placing cursor just to the right of a link.  Start typing.  Force the node to re-render by changing the formatting to a heading. OR just save the page.  Notice that the new text is now part of the link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345766400,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-h6kkxvcriuqwp7klykw2,task_description,resolved
+VisualEditor: DOM out of sync with data model when typing next to a link,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306612,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h6kkxvcriuqwp7klykw2,task_subcomment,NA
+VisualEditor: DOM out of sync with data model when typing next to a link,This was fixed when I changed how pre-annotations work.,1354217099,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-h6kkxvcriuqwp7klykw2,task_subcomment,NA
+VisualEditor: Link inspector should abridge completion results so users can distinguish multiple very long similar titles,"Proposal is to automatically put the ellipsis in the middle rather than at the end of the string.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345748940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nepuoz3eghdbacybz47v,task_description,resolved
+VisualEditor: Link inspector should abridge completion results so users can distinguish multiple very long similar titles,Already fixed in master.,1347302279,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nepuoz3eghdbacybz47v,task_subcomment,NA
+VisualEditor: Link inspector should abridge completion results so users can distinguish multiple very long similar titles,"I agree, I've been seeing this in other places as well. I can't recall where I saw it but I was using my iPod touch and saw some autocompletion list use ellipsis in the middle and thought it was brilliant.
+
+When using long titles the beginning will be the same, especially knowing that our list will be in alphabetical order (as opposed to search rank or whatever, which is what a search engine's suggestions would/could be) it is very likely and worth optimizing for.
+
+Sounds like a good feature to implement in the jquery.autoEllipsis plugin we maintain in MediaWiki.",1345821017,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-nepuoz3eghdbacybz47v,task_subcomment,NA
+Comments break splitting of paragraphs,"See http://parsoid.wmflabs.org/_rt/mw/VisualEditor:Test , and note how ""many of your questions"" and ""Note: The Edit button"" are on the same line, while they're really supposed to be in separate paragraphs.
+
+Basically, what's going on here is that the wikitext:
+
+Foo
+<!-- Comment -->
+
+Bar
+
+is turned into this HTML:
+<p>Foo
+<!-- Comment -->
+
+Bar</p>
+
+while really the correct output is this:
+<p>Foo</p>
+<!-- Comment -->
+
+<p>Bar</p>
+
+This results in the page rendering as ""Foo Bar"" rather than ""Foo [paragraph break] Bar"", and of course that means the way the editor renders it and lets you edit it is wrong as well.
+
+What's maybe even scarier is that this round-trips ""correctly"", i.e. the wikitext->HTML conversion is wrong, but then the HTML->wikitext conversion is wrong in exactly the reverse way, and that causes it to round-trip. I suspect this is because of the presence of the newlines in the HTML, but that's also a bug: ideally the serializer shouldn't convert a single <p> to wikitext representing multiple paragraphs, regardless of newlines (this is very unlikely to be a practical problem for VE though).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345593360,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-g6mdoxrevyqbrazocz2q,task_description,resolved
+Comments break splitting of paragraphs,"Fixed in https://gerrit.wikimedia.org/r/#/c/24502/3
+Also, added a test to mediawiki/core parserTests.txt",1348260388,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-g6mdoxrevyqbrazocz2q,task_subcomment,NA
+VisualEditor: Select all then replace causes first character to be swallowed in Heading mode,"To reproduce:
+
+Go to a blank VisualEditor page, click edit, change entry mode to Heading 1 (or whichever Heading mode), select all (Ctrl-A or Cmd-A), type in 'Abc'.
+
+The 'A' will appear, then be replaced by the 'b'; the 'c' appears normally.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345502760,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kpx6sqi7fes7jlx6flt4,task_description,resolved
+VisualEditor: Select all then replace causes first character to be swallowed in Heading mode,"**orbit** wrote:
+
+
+
+%%%*** This bug has been marked as a duplicate of bug 39465 ***%%%",1345502985,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-kpx6sqi7fes7jlx6flt4,task_subcomment,NA
+VisualEditor: Annotated content stripped from an LI on save,"See: https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=574056&oldid=574055
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1345492260,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nhi52laxjrwxyxxoh46r,task_description,resolved
+VisualEditor: Annotated content stripped from an LI on save,Already fixed in master.,1347302507,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nhi52laxjrwxyxxoh46r,task_subcomment,NA
+VisualEditor: Annotated content stripped from an LI on save,Submitted a fix in https://gerrit.wikimedia.org/r/20818,1345493741,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-nhi52laxjrwxyxxoh46r,task_subcomment,NA
+VisualEditor: Link inspector should cache completion results,"If I type ""T"", then ""Te"", then press backspace, the link inspector will request suggestions for ""T"" for the second time. Instead, it should cache these results.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345484760,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-r2i2uzlqlwknth3ox5rg,task_description,resolved
+VisualEditor: Link inspector should cache completion results,Fixed in https://gerrit.wikimedia.org/r/#/c/20915/,1345571007,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-r2i2uzlqlwknth3ox5rg,task_subcomment,NA
+VisualEditor: Selecting all text and typing causes first typed character to be deleted,"To reproduce:
+
+1. Select all text in document (ctrl/cmd+a)
+2. Start typing a word
+3. Notice that the first character of the word disappears
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1345239480,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-nnvtoxoopp6h7zbzqq7s,task_description,resolved
+VisualEditor: Selecting all text and typing causes first typed character to be deleted,"**orbit** wrote:
+
+This is fixed due to the work that Inez has done with slug replacement.",1350001011,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnvtoxoopp6h7zbzqq7s,task_subcomment,NA
+VisualEditor: Selecting all text and typing causes first typed character to be deleted,"**orbit** wrote:
+
+%%%*** Bug 39517 has been marked as a duplicate of this bug. ***%%%",1345502985,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnvtoxoopp6h7zbzqq7s,task_subcomment,NA
+VisualEditor: Selection issues re-write,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344882780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rh7iz42inbmpgpuz2l7u,task_description,resolved
+VisualEditor: Selection issues re-write,[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343641,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-rh7iz42inbmpgpuz2l7u,task_subcomment,NA
+VisualEditor: Selection issues re-write,Selection re-write is now complete; closing this as now done.,1354812178,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rh7iz42inbmpgpuz2l7u,task_subcomment,NA
+VisualEditor: JS error after saving document,"Open a document in the editor, change something, then save it. The following JS error appears in my console after saving:
+
+TypeError: $editorDocument.children("".ve-ce-branchNode:last"").offset() is null
+[Break On This Error] 	
+
+$editorDocument.children( '.ve-ce-branchNode:last' ).offset().top
+
+ve.Surface.js (line 184)
+
+
+Observed in Firefox 14.0.1.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344637500,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bodj4j2hdcdjgi2sbtmy,task_description,resolved
+VisualEditor: JS error after saving document,"No longer occurs in either Firefox or Chrome. Given how much we've re-written this code, not surprising, really. :-) Marking as fixed.",1354812033,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bodj4j2hdcdjgi2sbtmy,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"Go to http://localhost:8000/_rtform/ and enter ""<br>""; it'll round-trip to ""<br />""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344466200,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_description,resolved
+Self-closing tags without trailing slash do not round-trip correctly,"Closing this bug for now, semantically insignificant whitespace is tracked by bug 39564.",1345656284,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"We need clean diffs, but there are different ways to get them, with different cost/benefit ratios. Tracking all semantically insignificant whitespace in rt information looks like a sure way to add a lot of bloat. Selective serialization of modified DOM parts on the other hand seems to offer a better cost/benefit ratio.
+
+The only downside of selective serialization I see is that it adds a burden on clients to mark modified parts of the DOM.",1345649522,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"This insignificant whitespace issue is broader than self-closing tags.  Worth closing this ticket and opening a new one to discuss that.
+
+For example, try this:
+
+""<div    style='color:red;'>foo</div>""
+
+The excess white space is lost.  While I am inclined to dismiss this issues as insignificant and as a case where dirty diffs are acceptable, I am also sensing the tension in the air around WMF projects.  So, maybe this is not such an insignificant issue after all.  Using selective serialization, we can for sure address all these newline, whitespace, etc. issues, and it is worth discussing how soon we should enable that.  As Gabriel noted, it will also eliminate a lot of the wikitext state we carry around in the DOM.
+
+But, the serializer also ought to be complete in and of itself, and so this question will rear its head in that context again.
+
+My personal inclination is to ignore this issue because supporting this consistently will mean essentially recognizing non-normalized-whitespace/newline scenarios and carrying diff-state in the DOM.  But, we will probably be doing this only to satisfy a requirement of perfect round-tripping which IMO is unreasonable/unrealistic.
+
+This might be one issue where it is worth bringing in the editor community into the discussion so we can make a more reasonable decision that everying can be happy with.",1345648752,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"We generally don't try to preserve insignificant whitespace inside HTML tags yet, and it is debatable if this would be worth it. The main reason for going to the length we currently do for full-serialization round-tripping is to simplify our own testing (so that we can use a simple text diff). In the longer term, selective serialization based on the editor's change annotations should provide the better bang for the buck. We might well remove some of the elaborate round-trip information we currently collect once that is enabled and a way to systematically ignore some rt differences is found.",1345599858,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"This is not quite fixed yet, because now ""<br />"" round-trips to ""<br/>"", see http://parsoid.wmflabs.org/_rt/mw/VisualEditor:Roadmap",1345593703,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"Boom, merged. Gettin' it done.",1344965167,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,Complete list of void elements submitted for review in https://gerrit.wikimedia.org/r/18697. Verified to preserve slash for hr as well.,1344636623,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"'img' tags are not normally allowed in wikitext, and are stripped out by the sanitizer. 'hr' tags should be allowed, just need to be added to the list of empty tags.",1344632214,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,"This fix was merged, but there were notes about '<hr>' and '<img>' as well. I tried to get those to work, but something happens to '<img>' tags before they get to the serializer, and I'm not entirely sure where.",1344628975,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+Self-closing tags without trailing slash do not round-trip correctly,Fix pushed for review in https://gerrit.wikimedia.org/r/#/c/18202/,1344471929,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4tmd7nww2cyfj5sek6yq,task_subcomment,NA
+VisualEditor: Round-tripping of double apostrophes causes them to be interpreted as wikitext,"Repro:
+
+1. Go to http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&action=edit&oldid=569294 , save, then edit it with VE
+2. Insert '' in the word ""link"", save. diff: http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&diff=569295&oldid=569294
+3. Edit it with VE again, select ""li''nk"", and make it italic, save. diff: http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&diff=next&oldid=569295
+4. So many unexpected quotes
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1344201240,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-3vh3dwgpiyxwl4qobayn,task_description,resolved
+VisualEditor: Round-tripping of double apostrophes causes them to be interpreted as wikitext,"This is fixed in production in that it doesn't introduce the excess quotes any more, see https://www.mediawiki.org/w/index.php?title=VisualEditor%3ABug39058&diff=571888&oldid=571887 . It still adds <span> tags though, but that's fixed on master.
+
+On my localhost, the diff I get is as follows, and I think that's perfectly reasonable:
+
+− '''This is a te<nowiki>''</nowiki>st page for bug 35058.'''
++ '''This is a ''te<nowiki>''</nowiki>st'' page for bug 35058.'''",1344908105,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3vh3dwgpiyxwl4qobayn,task_subcomment,NA
+Parsoid does not handle urlencoded interwiki prefixes correctly,"http://localhost:8000/localhost:VisualEditor:Foo works and parses VisualEditor:Foo on localhost
+
+http://localhost:8000/localhost:VisualEditor%3AFoo works too
+
+http://localhost:8000/localhost%3AVisualEditor%3A Foo does not work, it doesn't recognize the interwiki prefix, falls back to the default interwiki (mw:), and tries to parse [[mw:Localhost:VisualEditor:Foo]].
+
+Debugging shows that in the ""Regular article parsing"" callback on line 397, req.params is set to [ undefined, 'localhost:VisualEditor:Lists' ], whereas if the colons aren't urlencoded it's [ 'localhost', 'VisualEditor:Lists' ]. It looks like app.get()'s regex mode isn't processing urlencoded characters correctly even though it does unescape the matches before putting them in req.params.
+
+This is obviously a blocker for making VisualEditor always use an interwiki prefix.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343793720,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jzxawxvcg5luenehopjn,task_description,resolved
+Parsoid does not handle urlencoded interwiki prefixes correctly,Mass-moving bugs into the new 'Parsoid' product.,1344281149,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jzxawxvcg5luenehopjn,task_subcomment,NA
+Parsoid does not handle urlencoded interwiki prefixes correctly,I don't really see the need to urlencode the colon since it is plain ASCII (browsers don't do so evidently). I have added support for this nevertheless since it was easy to do: https://gerrit.wikimedia.org/r/#/c/17331/,1343853258,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jzxawxvcg5luenehopjn,task_subcomment,NA
+VisualEditor: UserAgent blacklisting (using jQuery.client?),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1343672940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hlm32lc3bwvjx3khjhox,task_description,resolved
+VisualEditor: UserAgent blacklisting (using jQuery.client?),"Resolved in I6ebb3f7a7d56d395e5fe5c7c9129b606f97aeaab
+
+Use ?vewhitelist to activate it on blacklisted browsers. This is superior to using debug mode because it can be used to diagnose problems that occur in and out of debug mode.",1345671208,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-hlm32lc3bwvjx3khjhox,task_subcomment,NA
+VisualEditor: UserAgent blacklisting (using jQuery.client?),Proposal that if debug=true then suspend this so that you can test in any browser.,1343673005,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hlm32lc3bwvjx3khjhox,task_subcomment,NA
+"VisualEditor: ""edit source"" link on oldid=foo should pass on the revision in the GET when going to action=edit, even though veaction=edit doesn't support it yet.","Right now we can't use VE on an old-id page due to Parsoid lacking the feature yet, but we could at least make the edit-source link work when users are looking at an old revision. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343424780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ybjzemdynryfg4brsgpi,task_description,resolved
+"VisualEditor: ""edit source"" link on oldid=foo should pass on the revision in the GET when going to action=edit, even though veaction=edit doesn't support it yet.","
+
+*** This bug has been marked as a duplicate of bug 38125 ***",1343674164,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ybjzemdynryfg4brsgpi,task_subcomment,NA
+VisualEditor: round-trip inline styles,"Input:
+
+This is an <span style=""background: red; color: white; font-weight: bold;"">Inline element</span>.
+
+This sentence contains '''wikitext bold''' and <b>html bold</b>, <strong>html strong</strong> and <span style=""font-weight: bold;"">inline style bold</span>.
+
+Output:
+
+This is an <span>Inline element</span>.
+
+This sentence contains '''wikitext bold''' and '''html bold''', <strong>html strong</strong> and <span>inline style bold</span>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343347860,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-od4vkgjhilutsh6eoi2o,task_description,resolved
+VisualEditor: round-trip inline styles,This was fixed last week in https://gerrit.wikimedia.org/r/#/c/18421,1345054334,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-od4vkgjhilutsh6eoi2o,task_subcomment,NA
+VisualEditor: round-trip inline styles,"This is a DM problem, attributes for text style annotations are not currently preserved. Will be fixed in my annotation API rewrite that I'm starting now.",1343348008,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-od4vkgjhilutsh6eoi2o,task_subcomment,NA
+VisualEditor: Round-trip <b> should not become '''syntax''',"Can not reproduce on parsoid.wmflabs.org but not sure which version runs where, so reporting as reminder to confirm that it is fixed once deployed on MediaWiki.org as well.
+
+Input:
+This sentence contains '''wikitext bold''' and <b>html bold</b>, <strong>html strong</strong>.
+
+Output:
+This sentence contains '''wikitext bold''' and '''html bold''', <strong>html strong</strong>.
+
+
+Example: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ADoom&diff=565804&oldid=565802
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=38738",1343347800,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-sofl3tiyrxpjkqmu6grn,task_description,resolved
+VisualEditor: Round-trip <b> should not become '''syntax''',"(In reply to comment #1)
+> This is a data model problem: Parsoid is giving us round-trip attributes but
+> the converter isn't preserving them. Same root cause as bug 38738
+Fixed, see bug 38738",1345054496,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-sofl3tiyrxpjkqmu6grn,task_subcomment,NA
+VisualEditor: Round-trip <b> should not become '''syntax''',This is a data model problem: Parsoid is giving us round-trip attributes but the converter isn't preserving them. Same root cause as bug 38738,1343347978,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-sofl3tiyrxpjkqmu6grn,task_subcomment,NA
+VisualEditor: Modify the Parsoid <-> DM converter to handle newlines properly,"* New lines after headlines are being stripped
+* New lines after lists are being stripped
+* New lines after tables are being stripped
+* New lines after <gallery> tags are being stripped
+
+
+Example: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ADoom&diff=565804&oldid=565802
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343347620,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lrcob3z2uqlumi23wzcg,task_description,resolved
+VisualEditor: Modify the Parsoid <-> DM converter to handle newlines properly,This was done a while ago. The main commits were https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=commit;h=63e6702c523614786f75f3ab2b4a1ddcc67b44c7 and https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=commit;h=452c759914aa29c6e7974f17c4bba63a9f010c9c,1347302350,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lrcob3z2uqlumi23wzcg,task_subcomment,NA
+VisualEditor: Modify the Parsoid <-> DM converter to handle newlines properly,"Gabriel, Trevor and I are gonna come up with a plan for newlines next week. Will need some Parsoid tweaks and DM changes.",1343347827,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lrcob3z2uqlumi23wzcg,task_subcomment,NA
+VisualEditor: Pressing Enter/Return in the edit summary input field should trigger submission,"As the title says. Tried on MediaWiki.org
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343347500,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-okkhp45bypa46o6v5bzh,task_description,resolved
+VisualEditor: Pressing Enter/Return in the edit summary input field should trigger submission,"
+
+*** This bug has been marked as a duplicate of bug 38042 ***",1343347540,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-okkhp45bypa46o6v5bzh,task_subcomment,NA
+VisualEditor: Table roundtripping is completely tripped up,"Several issues:
+
+* Ghost <nowiki></nowiki> tag pairs appearing
+
+* Syntax being normalized
+
+ 1)
+  ! foo !! bar !! baz
+  becomes
+  ! foo
+  ! bar
+  ! baz
+
+  Both are the same but should roundtrip if possible.
+
+ 2)
+  Row separators
+  {|
+  |-
+  ! foo
+  |-
+  | bar
+  |-
+  |}
+  becomes:
+
+  {|
+  ! foo
+  |-
+  | bar
+  |}
+
+  Although the first and last separator (|-) are optional, they should roundtrip
+  if possible.
+
+ 3) Syntax being broken due to new line insertion
+  ! foo !! bar !! baz
+  becomes:
+  ! foo
+  !! bar
+  !! baz
+
+  This is not just syntax appearance, this is actually broken. Because of the new lines, the output of 3) is actually difference, because it will display the second exclamation mark of each heading.
+
+
+
+Example: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ADoom&diff=565804&oldid=565802
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343347320,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hpovu36fcfgevlvacc57,task_description,resolved
+VisualEditor: Table roundtripping is completely tripped up,"Whatever caused this, it's fixed now. I just edited the VisualEditor:Doom page, which still has the same table on it, and the diff isn't dirty.",1352492777,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hpovu36fcfgevlvacc57,task_subcomment,NA
+VisualEditor: Table roundtripping is completely tripped up,This round-trips just fine when tested at http://parsoid.wmflabs.org/_rtform/. Looks like a known VE data model issue which causes round-trip attributes to be lost. Same root issue as bug 38738.,1343349837,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-hpovu36fcfgevlvacc57,task_subcomment,NA
+[Regression] VisualEditor: Down arrow in the inspector icon is mis-aligned.,"Due to the change[1] to arrow-down.png recently, the inspector icon was broken. The padding inside the image is very specific for the drop-down menu. The inspector-triggering icon however, does not need this padding and is mis-aligned as a result of that.
+
+
+[1] Change: Ib09a2a20b1 | https://gerrit.wikimedia.org/r/16218
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343176200,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4dujg5dey76ud6rkyyfy,task_description,resolved
+[Regression] VisualEditor: Down arrow in the inspector icon is mis-aligned.,Fixed in https://gerrit.wikimedia.org/r/16590,1343180029,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-4dujg5dey76ud6rkyyfy,task_subcomment,NA
+VisualEditor: User should be able to select text in the save dialog.,"The user-select: none; style from the ve-toolbar is cascading down into the save dialog, causing issues.
+
+Steps to reproduce:
+* View https://www.mediawiki.org/wiki/VisualEditor:Test
+* Change some text
+* Press ""Save page""
+
+Unexpected result:
+Users can't select/highlight any text inside the Save page dialog. In Chrome users can at least still select text inside the input field, though in Firefox it applies to form elements as well.
+
+If possible, the easiest fix would be to override user-select inside this save dialog and undo the ""none"" value. But its possible that that isn't possible (just like like display: block; doesn't do anything if an ancestor is display: none;).
+
+Otherwise it may have the be re-arranged to not be inside an element with class ve-toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343174820,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cxydx5rlo2r5gmbuelnf,task_description,resolved
+VisualEditor: User should be able to select text in the save dialog.,"There are issues in Firefox with overriding user-select properties.  Fix involves attaching the save dialog to the toolbar wrapper rather the toolbar itself.
+
+Patch in https://gerrit.wikimedia.org/r/16760",1343329073,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-cxydx5rlo2r5gmbuelnf,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"Screenshot of the white box overlapping regular text while using the editor
+
+From time time to time a white square appears in the editor, overlaying/masking part of the text.
+
+It can appear both when clicking/typing, as well as when selecting text. In the latter case it is even more visible due to the blue selection being interrupted by the box.
+
+Debugging tells me it is the idle iframe idling in the bushes, pretending to be hidden.
+
+Steps to reproduce:
+* Open https://www.mediawiki.org/wiki/VisualEditor:Test in Chrome 20 (Mac)
+* Switch to ""Edit"" mode
+* Select a word in the editor
+* Bolden it
+* Click ""Save Page""
+
+Unexpected result:
+* White box appears where the word was selected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9946}",1343172780,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4q4qvm4gto65caiusmb3,task_description,resolved
+VisualEditor: White box syndrome strikes back!,"Correction, when inspecting the iframe in the DOM, it is blue.   The issue has seemed to have vanished as Trevor and I were unable to reproduce it. 
+
+Set height and width to 0 for good measure.
+https://gerrit.wikimedia.org/r/21205",1345747417,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,It's blue this time!! I'll take a shot at it.,1345739767,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"I made an attempt to resolve it, but it caused the same old issue in FireFox as always.
+
+I7a69bac66c66ca1c0910f4adfda9a37cdac6f030",1345673987,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"The box ain't white this time, but it's stealing my clicks!",1345673925,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"I am still unable to reproduce this in Chrome 20 and 22.
+Though, hopefully is fixed by setting visibility hidden.
+Patched in https://gerrit.wikimedia.org/r/16663.",1343245501,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"Though the iframe has width: 0; height: 0;, Chrome does not allow
+zero-dimensioning an iframe.
+
+Firefox has issues with display: none; (doesn't load it until it is in the
+flow).
+
+Initial testing shows that visibility: hidden; may be an outcome. Because that
+makes it part of the flow, without being visible. Add that to the fact that it
+is absolutely positioned, and it is basically not in the flow at all.",1343173105,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: White box syndrome strikes back!,"Created attachment 10886
+Screenshot of the white box overlapping selected text in the editor
+
+**Attached**: {F9947}",1343172827,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4q4qvm4gto65caiusmb3,task_subcomment,NA
+VisualEditor: Bold and Italic UI buttons need to be internationalisable,"The Bold and Italic buttons say ""B"" and ""I"". Some languages can have different letters there; for example, Italian has ""G"" and ""C"" and German has ""F"" and ""K"".
+
+The corresponding buttons in the WikiEditor extension can be localized, but not in Visual Editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342883880,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-lj5fifjrup6bhxud572h,task_description,resolved
+VisualEditor: Bold and Italic UI buttons need to be internationalisable,Now merged into master.,1359765195,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lj5fifjrup6bhxud572h,task_subcomment,NA
+VisualEditor: Bold and Italic UI buttons need to be internationalisable,Fixed in gerrit 46863.,1359759302,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lj5fifjrup6bhxud572h,task_subcomment,NA
+VisualEditor: Bold and Italic UI buttons need to be internationalisable,"Assigning to current milestone, as it's been sitting around for five months untouched at this point.",1357601193,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lj5fifjrup6bhxud572h,task_subcomment,NA
+"VisualEditor: ""Undo"" and ""Redo"" buttons must be flipped for RTL environments","""Undo"" and ""Redo"" buttons must be flipped for RTL environments. Undo must point right and Redo must point left.
+
+The same images can be used, but they must be swapped.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342869480,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ss7w322z7ikgu5wkin5c,task_description,resolved
+"VisualEditor: ""Undo"" and ""Redo"" buttons must be flipped for RTL environments",Patch in https://gerrit.wikimedia.org/r/#/c/23478/,1347407456,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-ss7w322z7ikgu5wkin5c,task_subcomment,NA
+"VisualEditor: ""Bulleted list"" and ""Numbered list"" buttons in the editing toolbar must be reversed in RTL wikis","This bug is almost the same as Bug 28544 in WikiEditor :)
+
+The buttons ""Bulleted list"" and ""Numbered list"" must be mirrored in RTL wikis.
+
+The numbers in ""Numbered list"" in languages he, yi, arc and dv should look like
+regular Western numbers - not mirrored.
+
+In languages written in the Arabic alphabet (ar, fa, ur, ps, mzn etc.)
+[[Eastern Arabic numerals]] can be written there, but maybe Western numbers
+are OK, too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342869360,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dbjwk2354ghy4uqtyvgu,task_description,resolved
+"VisualEditor: ""Bulleted list"" and ""Numbered list"" buttons in the editing toolbar must be reversed in RTL wikis",Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306606,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dbjwk2354ghy4uqtyvgu,task_subcomment,NA
+"VisualEditor: ""Bulleted list"" and ""Numbered list"" buttons in the editing toolbar must be reversed in RTL wikis",This was resolved a while ago when the icons were redone.,1354216837,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-dbjwk2354ghy4uqtyvgu,task_subcomment,NA
+VisualEditor: down arrow in drop-down menu in RTL interface overlaps with the text,"Configure the user language to be Hebrew. Try to edit a page. The down arrow in format selection drop-down menu will overlap with the text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342866000,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-eftf2krwbij53usp7qbq,task_description,resolved
+VisualEditor: down arrow in drop-down menu in RTL interface overlaps with the text,Fixed in https://gerrit.wikimedia.org/r/#/c/16590/,1343346049,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-eftf2krwbij53usp7qbq,task_subcomment,NA
+VisualEditor: down arrow in drop-down menu in RTL interface overlaps with the text,Attempted to fix at https://gerrit.wikimedia.org/r/#/c/16218/ .,1342867057,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-eftf2krwbij53usp7qbq,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret","Ctrl+{Delete,Backspace} should delete a word right, left of the caret; Option+{Delete,Backspace} on Mac.
+
+Currently deletes a character right, left of the caret.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1342570860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ar46xe5css6dnxzqbtde,task_description,resolved
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret","The(In reply to comment #4)
+> It doesn't work in RTL.
+
+Bug 48912 is this bug for RTL; this has been closed for a year as done.",1369782887,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret",It doesn't work in RTL.,1369777371,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret","**orbit** wrote:
+
+This has been fixed. We're no longer programmatically handling delete and backspace keypresses. Now, we let the browser do its thing and we observe what's changed and compose an accurate transaction to the data model. The exception is at node boundaries (pressing backspace at the beginning of a paragraph, for example) which are still handled programmatically.",1345486426,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret","As with bug 38000, this feature must be left to the browser as much as possible. Some browsers delete the space after the word, some don't; some delete the punctuation after the word, some don't; in some languages the meaning of ""word"" is very surprising to people who speak English; in RTL languages ""right"" is the previous word and not the next; etc. We should just leave the behavior to which the users are accustomed in their favorite browsers.
+
+See https://www.mediawiki.org/wiki/VisualEditor/Internationalization_requirements .",1342868975,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+"VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret",Assigning to Christian as he's requested for all key-binding tickets.,1342570929,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ar46xe5css6dnxzqbtde,task_subcomment,NA
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,"I found that neither the global block nor the blacklisting of this title  prevented a globally-blocked proxy from creating http://www.mediawiki.org/w/index.php?title=VisualEditor:Modern_Apizza&action=edit&redlink=1.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1341867660,PHID-USER-wqc7ciyvfzunj3l2tvjt,False,PHID-TASK-jka67woodw5fn6qicshn,task_description,resolved
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306604,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jka67woodw5fn6qicshn,task_subcomment,NA
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,Fixed in gerrit 31889,1354218618,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jka67woodw5fn6qicshn,task_subcomment,NA
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,De-prioritising (as will be fixed when we properly deploy anyway).,1347302563,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jka67woodw5fn6qicshn,task_subcomment,NA
+VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation,"This will naturally resolve itself when we lift the namespace-specific restrictions on editing the Wikitext and can use the editing API instead of going through the back door, as we do now.
+
+This is related to bug 37844 - in that these will both be resolved in the same way.",1345672064,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-jka67woodw5fn6qicshn,task_subcomment,NA
+Selecting all text causes JS error in Firefox,"If I edit any page in Firefox 13 and select all text (using Ctrl+A), I get the following error:
+
+end is undefined
+http://localhost/w/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js
+Line 849
+rangyRange.setEnd( end.node, end.offset );
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux",1341519180,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3rsluniow7ulmwxctugw,task_description,resolved
+Selecting all text causes JS error in Firefox,"
+
+*** This bug has been marked as a duplicate of bug 38037 ***",1341519459,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3rsluniow7ulmwxctugw,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","From user submission. Uses same design argot as iOS. Perhaps confusing for non-iOS situations?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340916840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-etughy4urwl7bhwydk2t,task_description,resolved
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content",This is now how CE works; not sure when we altered behaviour to 'fix' it.,1360095133,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","Brion: Agreed.  IF anything we should surpress our context icon in IOS.  Perhaps invent our own tool there as well, though it seems it may get a bit cluttered.",1341617516,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","If we suppressed the default popup (assuming that's possible), then you'd be unable to copy/cut/paste text.
+
+That.... sounds bad. :)",1340920380,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","I imagine we'd want to suppress iOS's in-built behaviour if that happened (or suppress ours and magically work with it, somehow - using a generic mobile interface like PhoneGap, so we don't endlessly code for mobile? To discuss at a proper design meeting!",1340917997,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+"VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content","A potential problem here is overlapping with the system's own buttons. When you select on iOS, you get a little popup menu offering copy/cut/paste.
+
+We already overlap our arrow with the iOS selection handle (bug 37874), so make sure we don't go from one overlap to another. :)",1340917068,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-etughy4urwl7bhwydk2t,task_subcomment,NA
+VisualEditor: 'Enter' key does not submit edit from save dialog,"My muscle memory really, REALLY wants to hit enter after typing a summary, but it does nothing. Have to go to the mouse and find the button manually. Eww!
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340912820,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-3edkedybbeebfer2rcap,task_description,resolved
+VisualEditor: 'Enter' key does not submit edit from save dialog,Fixed in https://gerrit.wikimedia.org/r/16782,1343341015,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-3edkedybbeebfer2rcap,task_subcomment,NA
+VisualEditor: 'Enter' key does not submit edit from save dialog,":) same as bug 38042
+
+*** This bug has been marked as a duplicate of bug 38042 ***",1340916283,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-3edkedybbeebfer2rcap,task_subcomment,NA
+VisualEditor: doesn't trigger in IE 9 (Internet Explorer 9),"Tested on Windows 7 SP1 w/ IE 9...
+
+Edit tab just gives me the classic edit page...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340910600,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-etsrlkklzald7ybkqh3u,task_description,declined
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,"Possibly harmless but worrying.
+
+Steps to repro:
+* go to https://www.mediawiki.org/wiki/VisualEditor:Test?debug=true
+* hit edit
+* click in the article
+* ctrl+a (cmd+a on mac) to select all
+
+Expected:
+* all text of article should be selected
+
+Actual:
+* all text of article is selected
+* AND there's an error in the JS console: ""end is undefined""
+ve.ce.Surface.js (line 832)
+rangyRange.setEnd( end.node, end.offset );
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/VisualEditor:Test?debug=true",1340909880,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-h7ssc4ozwop6qczla4rr,task_description,declined
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,"**orbit** wrote:
+
+It doesn't look like this is happening any longer. Lots of changes that may have fixed this have rolled out since July.",1350377414,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,"(In reply to comment #0)
+> Possibly harmless
+
+It actually is harmful, and I suggest raising priority.
+
+Steps to reproduce:
+1) Go to http://www.mediawiki.org/wiki/Special:VisualEditorSandbox with Firefox
+2) Press CTRL-A (or select all text with the mouse)
+3) Press CTRL-X to cut all this text. The text disappears.
+4) Press CTRL-V to reinsert the text.
+
+PROBLEM: One can enter text, but not new lines. Pressing ""Enter"" does not have
+any effect.
+
+Tested on Ubuntu 2012.04, Firefox 13.0.1
+
+Tip to take with a grain of salt: I have seen some problems with UNDO when selecting everything or even everything but last character, but I can't reproduce, so don't mind. If I find something reproducible I will let you know.",1341541738,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,*** Bug 38207 has been marked as a duplicate of this bug. ***,1341519459,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,I can reproduce this in Firefox 13. Does not happen in Chrome.,1341519450,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: select all (ctrl+a) throws JS error in Firefox,Tested in Firefox 12.0 on Ubuntu 12.04 and 16 nightly on Mac OS X 10.7.4,1340910011,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-h7ssc4ozwop6qczla4rr,task_subcomment,NA
+VisualEditor: Tooltips for formatting menu are broken,"From user feedback. They seem to be unescaped, too - ""&lt;visualeditor-formatdropdown-tooltip&gt;"" etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1340834040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rataorpnc6452rqcpgfh,task_description,resolved
+VisualEditor: Tooltips for formatting menu are broken,"Thank you James.
+Fixed in https://gerrit.wikimedia.org/r/14599",1341617408,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-rataorpnc6452rqcpgfh,task_subcomment,NA
+VisualEditor: Tooltips for formatting menu are broken,"Occurs in Chrome/Mac and Safari/Mac, but not Firefox/Mac.
+
+Resultant HTML:
+
+<div class=""es-tool es-toolbarDropdownTool es-toolbarDropdownTool-format"" title=""&lt;visualeditor-formatdropdown-tooltip&gt;"">
+
+&lt;visualeditor-formatdropdown-tooltip&gt;
+
+(individual entries don't have tooltips assigned)
+
+Presumably this is meant to use [[MediaWiki:Visualeditor-formatdropdown-tooltip]] which is unititialised on MW.org - but setting it to something doesn't fix the problem:
+
+http://www.mediawiki.org/wiki/MediaWiki:Visualeditor-formatdropdown-tooltip
+
+From perusing the code I think it's in the messages array but missing from the i18n file, and not called by modules/ve/ui/tools/ve.ui.FormatDropdownTool.js, but it's got beyond my patience when rooting around with nano. :-)",1340926358,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rataorpnc6452rqcpgfh,task_subcomment,NA
+VisualEditor: Tooltips for formatting menu are broken,I don't see this in Firefox 13/Linux either in the deployment on mediawiki.org or locally. Any details on when/where this happens?,1340904447,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-rataorpnc6452rqcpgfh,task_subcomment,NA
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,"If in a link inspector or in the edit summary, pressing Page Up, Page Down, Home or End works in that box but also triggers the main edit space to move to the top or bottom. It needs to ignore if it's not got the caret. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340833800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d66zsm26kiowezoool57,task_description,declined
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,"**orbit** wrote:
+
+Okay, I looked more closely at this bug an understand it better. We're not doing any sort of processing of those keys, so the browser is doing what the browser naturally does. I use a Macbook Air and Chrome most of the time and for moving my cursor around a textarea (including the one that I'm typing in now), I use Command + [up, down, left, right] for jumping to the first char, last char, beginning of line, and end of line. I plugged in an external keyboard with proper page up, page down, home, and end keys and was able to reproduce the described behavior. Trevor and I just spoke about this and we don't think we should try to override the browser's handling of this. A ""fix"" may have other user experience consequences.
+
+Please reopen if you think I'm misunderstanding something.",1350690378,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-d66zsm26kiowezoool57,task_subcomment,NA
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,"**orbit** wrote:
+
+This is probably fixed now, but I'll have to test in the morning when I have a keyboard with these buttons properly.",1350377009,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-d66zsm26kiowezoool57,task_subcomment,NA
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,"Indeed - the problem as described seems only to happen in Safari and Chrome for me; in Firefox, instead the characters do nothing (pressing ""Home"" when in revision description box should move caret to before first character).",1340922316,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d66zsm26kiowezoool57,task_subcomment,NA
+VisualEditor: Using page movement keys when focus is not in edit area still triggers movement,Can't reproduce in Firefox 13.0/Linux.,1340902371,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-d66zsm26kiowezoool57,task_subcomment,NA
+VisualEditor: Design of save button should make it more prominent,"From user request. ""Big Red Button"" requested, but we might want to consider within a wider design discussion. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340833380,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l7c73muvr5qk2q5p42wr,task_description,resolved
+VisualEditor: Design of save button should make it more prominent,Various changes have been made in Ib1711f49af8929be12796aecdea49467b726856e which address this issue.,1347303896,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-l7c73muvr5qk2q5p42wr,task_subcomment,NA
+VisualEditor: Link inspector button in toolbar should let users create a link without any text selected,"From user request. Possibly insert the name of the target automatically? So a link to [[foo]] will be entered as <a href=foo>foo</a>?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340832780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-urg73yoypnuiks7zst4o,task_description,resolved
+VisualEditor: Link inspector button in toolbar should let users create a link without any text selected,"
+
+*** This bug has been marked as a duplicate of bug 33141 ***",1340833038,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-urg73yoypnuiks7zst4o,task_subcomment,NA
+"VisualEditor: Ctrl + {left,right} arrow should skip a word left or right (Apple + ... on Mac OS X)","From user request. There are other keybinding feature requests; possibly worth documenting all the ones we respect?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340830740,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-53mqogsdiodyzah24cx5,task_description,resolved
+"VisualEditor: Ctrl + {left,right} arrow should skip a word left or right (Apple + ... on Mac OS X)","**orbit** wrote:
+
+This is fixed now. The cursor moves natively unless some conditions are met (inside a slug or moving farther than 1 offset).",1349998405,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-53mqogsdiodyzah24cx5,task_subcomment,NA
+"VisualEditor: Ctrl + {left,right} arrow should skip a word left or right (Apple + ... on Mac OS X)","This is one of those things that should be left to the browser as much as possible.
+
+If it is implemented inside the VE, there will be no end to surprises. Different browsers have subtle differences in the behavior of this feature, and users who use it often and are accustomed to the behavior in their favorite browser won't like the VE implementation, whatever it will be. There are also numerous surprises in the i18n side - the different direction of movement in RTL environments, word-boundary algorithms in Thai, and many, many more.
+
+See https://www.mediawiki.org/wiki/VisualEditor/Internationalization_requirements .",1342868297,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-53mqogsdiodyzah24cx5,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","Steps to reproduce:
+1) Go to http://www.mediawiki.org/wiki/Special:VisualEditorSandbox
+2) Press CTRL-A (or select all text with the mouse)
+3) Press CTRL-X to cut all this text. The text disappears.
+4) Press CTRL-V to reinsert the text.
+
+PROBLEM1: Text is not reinserted, the page stays blank.
+PROBLEM2: One can enter text, but not new lines. Pressing ""Enter"" does not have any effect.
+
+Tested on Ubuntu 2012.04, Firefox 13.0.1
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1340770860,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-obhstlqgs73vks43hy74,task_description,resolved
+"VisualEditor: Cut all text, re-paste it: broken editor","(In reply to comment #6)
+> > Problem #2 is a Firefox-specific selection issue, so I'm filing a separate bug for that and closing this one as fixed.
+> 
+> Roan, could you please tell us the identifier of the new bug report you
+> created?
+
+Sorry, meant to do that but forgot. I filed bug 38207 for it and later found it was a duplicate of bug 38037.",1341540598,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","> Problem #2 is a Firefox-specific selection issue, so I'm filing a separate bug for that and closing this one as fixed.
+
+Roan, could you please tell us the identifier of the new bug report you created?",1341540453,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","(In reply to comment #4)
+> This looks like a bug in fixupInsertion. When the entire contents is cut, only
+> paragraph and /paragraph are in the documentModel. Pasting more than 2
+> paragraphs will error. 
+> 
+This fixupInsertion issue is fixed in https://gerrit.wikimedia.org/r/14398 . This fixes problem #1, which occurred in all browsers. Problem #2 is a Firefox-specific selection issue, so I'm filing a separate bug for that and closing this one as fixed.",1341518416,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","**orbit** wrote:
+
+This looks like a bug in fixupInsertion. When the entire contents is cut, only paragraph and /paragraph are in the documentModel. Pasting more than 2 paragraphs will error. 
+
+Steps to reproduce:
+1) Create a document with 3 simple paragraphs.
+2) Ctl-A
+3) Ctl-X
+4) Ctl-V",1341264805,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","The component below does not have this bug:
+http://html5demos.com/contenteditable/",1340926239,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor",Confirm problem 1 (but not 2) on Chrome 19/Mac and both problems on Firefox 13/Mac.,1340836052,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Cut all text, re-paste it: broken editor","On Ubuntu 2012.04, Chromium 18.0.1025.151: Only PROBLEM1 occurs, PROBLEM2 does not occur.",1340771015,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-obhstlqgs73vks43hy74,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: Macintosh",1340709300,PHID-USER-fgzcdbj3je3ksnhufo47,False,PHID-TASK-zlt7qdys5zthrlly644p,task_description,resolved
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari","This should be fixed now, as part of the fix for Ime.",1350414720,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari",I think I know what is the issue. Will be fixed together with adding support for IME.,1342551105,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari",Confirmed that I get the above odd behaviour using keyboard-shortcuts to create diacritics on Mac using Chrome and Safari (but not using Firefox).,1340730365,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari","Other behavior:
+* When entered as the first character on a newline, a duplicate line below it with that one character is created
+* Occasionally when a combo is made (e.g., ˆ+ a + r) when the second non-combo character is typed, the combination itself (here â) is deleted.",1340710556,PHID-USER-fgzcdbj3je3ksnhufo47,False,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+"VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari","Examples: typing ""ând"" at the end of a line often causes one of the following:
+* a floating linebreak at the cursor (one which can't be easily deleted, not sure what's happening underneath)
+* a character 4-5 characters to the left of the cursor to *change*.  
+** example changes: from one lowercase letter to another.  from one letter to an uppercase B.  
+
+The above is not 100% reproducible; some of the above happens at least 1 in 3 times I typed this just now; I'm trying to reproduce more specifically.  
+
+[Using Chrome on Mac OS X]",1340709453,PHID-USER-fgzcdbj3je3ksnhufo47,False,PHID-TASK-zlt7qdys5zthrlly644p,task_subcomment,NA
+VisualEditor: DM support for nested lists,"As discussed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340654160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-byaxrg34aq533rbmohda,task_description,resolved
+"VisualEditor: XYZ:Foo links round-trip surprisingly e.g. Categories, Images/Files, ….","As discussed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340653980,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-aypymh3waspkktjfjzyq,task_description,resolved
+"VisualEditor: XYZ:Foo links round-trip surprisingly e.g. Categories, Images/Files, ….",Fixed in https://gerrit.wikimedia.org/r/#/c/14605/,1341637505,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-aypymh3waspkktjfjzyq,task_subcomment,NA
+"VisualEditor: Trim whitespace on headings, list items, other node types","As discussed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340653920,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pz4hu5kupf3cy6rgi2hl,task_description,resolved
+"VisualEditor: Trim whitespace on headings, list items, other node types","Done in https://gerrit.wikimedia.org/r/#/c/18711/ , commit message explains what this feature is about.",1345485423,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-pz4hu5kupf3cy6rgi2hl,task_subcomment,NA
+"VisualEditor: Trim whitespace on headings, list items, other node types","Note -- ""as discussed"" isn't very clear; I presume some discussion was had somewhere by someone, and can only hope that the assignee of the bug understands what this means. In future please summarize the discussion in the bug, thanks. :)",1340904774,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-pz4hu5kupf3cy6rgi2hl,task_subcomment,NA
+"VisualEditor: Placing the cursor (by clicking or through the cursor keys) into sub-lists breaks - it ""flashes"" in, but then disappears (is no longer drawn anywhere) and cannot be used (e.g. shift-left or etc. doesn't work).","(From the casual list on the wiki.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340569500,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k2ubvggwznutod3v37na,task_description,resolved
+"VisualEditor: Placing the cursor (by clicking or through the cursor keys) into sub-lists breaks - it ""flashes"" in, but then disappears (is no longer drawn anywhere) and cannot be used (e.g. shift-left or etc. doesn't work).",This works now.,1343097980,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-k2ubvggwznutod3v37na,task_subcomment,NA
+"VisualEditor: Placing the cursor (by clicking or through the cursor keys) into sub-lists breaks - it ""flashes"" in, but then disappears (is no longer drawn anywhere) and cannot be used (e.g. shift-left or etc. doesn't work).","Add to ""VE-deploy-2012-07-09"" milestone per this morning's meeting.",1341266205,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k2ubvggwznutod3v37na,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,"(From the casual list on the wiki.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340569500,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_description,resolved
+VisualEditor: Indent and outdent buttons do not exist,I see them now :) . Fixed in today's deployment.,1343097650,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,"Add to ""VE-deploy-2012-07-09"" milestone per this morning's meeting.",1341266196,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,"Changing summary from ""do not work"" to ""do not exist"" then. :)",1340913272,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,... but you will. :-),1340653953,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Indent and outdent buttons do not exist,I don't see any indent/outdent buttons...,1340651426,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-mu5hvfs3z4bnfcwufhcz,task_subcomment,NA
+VisualEditor: Unlisting should unlist all list levels,"(From the casual list on the wiki.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340569440,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7hymyhokel2tmuz42xo3,task_description,resolved
+VisualEditor: Unlisting should unlist all list levels,"https://gerrit.wikimedia.org/r/#/c/32664/ fixes the previous functionality, which was to unlist the selected list and its child lists. Unlisting of parent lists was never implemented, but I see you've filed other bugs for that now (including bug 41935), so closing this one.",1352596148,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-7hymyhokel2tmuz42xo3,task_subcomment,NA
+VisualEditor: Unlisting should unlist all list levels,"Functionality appears to have been lost - now unlisting only unlists at the most-deeply-nested list, and has no effect on lists further up the tree.",1352482289,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7hymyhokel2tmuz42xo3,task_subcomment,NA
+VisualEditor: Unlisting should unlist all list levels,Implemented in https://gerrit.wikimedia.org/r/#/c/16680/,1343260936,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-7hymyhokel2tmuz42xo3,task_subcomment,NA
+VisualEditor: Unlisting should unlist all list levels,"Add to ""VE-deploy-2012-07-09"" milestone per this morning's meeting.",1341266188,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7hymyhokel2tmuz42xo3,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,"From MW.org report:
+
+Links should probably have a title="""". I naturally hover over links to see their target. I wanted to see if the target was correct and I had to fiddle with the link editor just to see something that should have been easily available.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340569140,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-utdxlw7pghyukf2ujhmo,task_description,resolved
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,Now merged; will be deployed as part of the 2013-01-16 release cycle.,1357678591,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,Patched in: https://gerrit.wikimedia.org/r/38636,1355436725,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,[REGRESSION] This was fixed but now is not (probably in UI-rewrite). Would be nice to fix.,1355435259,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,"Fixed in gerrit 21208 - left unclosed by accident, I think. (?)",1353134829,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,"Created attachment 11068
+Screenshot illustrating problem
+
+Illustration of problem attached.
+
+**Attached**: {F9394}",1346774776,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to see the target of a link without triggering the inspector,Resolved in I1a1cfd70c222dd1d686b46cd702edf2e9d0e5bae,1345749594,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-utdxlw7pghyukf2ujhmo,task_subcomment,NA
+VisualEditor: Provide a way to preview the diff of the changes made,"(Depends on us working out what diffing revisions should look like now.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340569020,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hcc3ucc2gxwo6jb557m7,task_description,resolved
+VisualEditor: Provide a way to preview the diff of the changes made,"
+
+*** This bug has been marked as a duplicate of bug 37931 ***",1345669770,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-hcc3ucc2gxwo6jb557m7,task_subcomment,NA
+VisualEditor: Edit window scrolls to top of page after paste,"iOS 5.1 simulator on Mac OS X
+
+After pasting text into the document, the view is scrolled up to the top of the page. This is a bit distracting if you're somewhere further down in the document. :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340473080,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_description,resolved
+VisualEditor: Edit window scrolls to top of page after paste,Note which milestone this met.,1355171016,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_subcomment,NA
+VisualEditor: Edit window scrolls to top of page after paste,Fixed in gerrit 37575.,1354928052,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_subcomment,NA
+VisualEditor: Edit window scrolls to top of page after paste,"This was also happening in Chrome and Firefox on desktop.
+
+http://cl.ly/image/0B443D3x1Y2T",1354920770,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_subcomment,NA
+VisualEditor: Edit window scrolls to top of page after paste,"Moving to ""Mobile"" component.",1354811631,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q6pn4p5ppytwmrilrwfc,task_subcomment,NA
+VisualEditor: toolbar mispositioned on iPad,"Screenshot of iPad simulator
+
+The toolbar is slightly mispositioned on iPad, tested in iPad simulator on Mac OS X as my iPad isn't handy.
+
+Seems to be slightly up and to the left of where it should be. Screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9308}",1340472060,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-dutiulezx3dwzyt4n3jd,task_description,resolved
+VisualEditor: toolbar mispositioned on iPad,"In the following commit, toolbar detaching mechanism has been disabled on mobile devices.  Floating logic has been improved with boundaries and a bottom position. 
+https://gerrit.wikimedia.org/r/#/c/14072/
+
+There is talk of creating a mobile friendly toolbar but that is a potential feature request that has yet to be designed.",1343668655,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-dutiulezx3dwzyt4n3jd,task_subcomment,NA
+VisualEditor: toolbar mispositioned on iPad,"Also doesn't seem to follow viewport properly....
+
+At some point in my testing the toolbar switched to fixed-position following the viewport, but it won't re-dock when scrolling to the top of the page.",1340473346,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-dutiulezx3dwzyt4n3jd,task_subcomment,NA
+"VisualEditor: Window-close prompt thinks I'm returning to view mode, and displays two warnings rather than one.","Tested in Safari 5.1.7.
+
+Steps to repro:
+* open https://www.mediawiki.org/wiki/VisualEditor:Welcome
+* hit 'edit'
+* close tab
+
+A prompt comes up:
+
+  https://www.mediawiki.org
+  Are you sure you want to leave this page?
+  Are you sure you want to go back to view mode without saving first?
+  [Stay on page] [Leave page]
+
+The ""Are you sure you want to go back to view mode without saving first?"" presumably comes from our code. This makes sense only if I were clicking on the 'read' tab link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340470920,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-k3ogdcpxt3y5m7tvnsj2,task_description,declined
+"VisualEditor: Window-close prompt thinks I'm returning to view mode, and displays two warnings rather than one.",I can't reproduce this - but that might be because this was a side-effect of something that has since been changed.,1345748822,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-k3ogdcpxt3y5m7tvnsj2,task_subcomment,NA
+"VisualEditor: Window-close prompt thinks I'm returning to view mode, and displays two warnings rather than one.",Moving from UI to Integration module.,1340564817,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k3ogdcpxt3y5m7tvnsj2,task_subcomment,NA
+"VisualEditor: Add inline editing after each link, accessed by hide/unhide icon","Suggestion: after each link add a little icon which, when clicked, adds a directly editable inline element containing the link destination. No need to go to the top, no no modal popup dialog which has to separately confirmed... The inline link destination should not require closing to accept, it should just be a part of the text and changes to it are naturally saved together with all other text when the page is being saved.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340418720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qc2hzb2zgpy4pqax7p6j,task_description,invalid
+"VisualEditor: Add inline editing after each link, accessed by hide/unhide icon",This is now not compatible with how the UX has developed; closing.,1360204987,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qc2hzb2zgpy4pqax7p6j,task_subcomment,NA
+"VisualEditor: Add inline editing after each link, accessed by hide/unhide icon","Changed title by jforrester from ""Add inspector accessor icon after each link for easier editing"" to ""Add inline editing after each link, accessed by hide/unhide icon"". The main part of my original proposal is not the accessor icon, but allow editors to optionally see and edit the link destination directly after the link text, without the need to open a modal dialogue box and memorize the link destination afterwards, potentially for multiple links.",1340539721,PHID-USER-grpjkpfolt5gz4ljlbfg,True,PHID-TASK-qc2hzb2zgpy4pqax7p6j,task_subcomment,NA
+"VisualEditor: Unexpected behaviour of list editing - what level should the buttons operate, and is it consistent?","From https://www.mediawiki.org/w/index.php?title=Thread:VisualEditor_talk:Welcome/Editing_numbered_Lists_is_broken&lqt_method=thread_history
+
+Click on one item in a three element numbered list and click on the numbered list button -> all three elements become unnumbered. Click again -> only the first element becomes numbered.
+Mark all three and click -> you sometimes get three elements in a numbered list, sometimes three numbered lists, each starting with number 1. Could not figure out when I get what...
+When I mark three fresh, non numbered, non-bulleted lines, it seems generally to work becoming a three part numbered list. Although clicking again (which changing selection focus) on the button to undo here never works. That is: all three 1 to 3 selected, click on numbered list button to unnumber does not work, going to the first element click same button, unnumbers all.
+Having three line of unnumbered text where the second element is a bulleted list item, select, click numbered list (expecting to have a nested bullet within a numbered list) does not work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340418540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vnz2yl4fdnpwhagmzdlo,task_description,declined
+"VisualEditor: Unexpected behaviour of list editing - what level should the buttons operate, and is it consistent?","This appears now to be fixed in current behaviour (part 1 of the issue is intended, the rest seems fixed).",1352481732,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vnz2yl4fdnpwhagmzdlo,task_subcomment,NA
+VisualEditor: Nested lists (tracking bug),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340413620,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jnj6pwbdr63nh5prebtr,task_description,resolved
+VisualEditor: Nested lists (tracking bug),"Add to ""VE-deploy-2012-07-09"" milestone per this morning's meeting.",1341266220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jnj6pwbdr63nh5prebtr,task_subcomment,NA
+VisualEditor: JS error on load in IE 10,"Seen in my JS console during loading in IE 10 on Windows 8 Release Preview:
+
+SCRIPT5007: Unable to get property 'to' of undefined or null reference
+ve.ui.Context.js, line 120 character 2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340405460,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-yl7i3kirybrkgyab56tk,task_description,resolved
+VisualEditor: JS error on load in IE 10,Confirmed fixed in newly-deployed version.,1350327505,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yl7i3kirybrkgyab56tk,task_subcomment,NA
+VisualEditor: JS error on load in IE 10,"I haven't been able to reproduce this in IE10.  Though, this same error happens randomly in all browsers.  I suspect it to be related to a recently closed context icon bug.  Though, I'm failing to find it since I marked it as resolved.",1341616538,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-yl7i3kirybrkgyab56tk,task_subcomment,NA
+VisualEditor: JS error on load in IE 10,"Line is:
+
+  if (selection.to > selection.from) {
+
+in Context.PositionIcon ...",1340405718,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-yl7i3kirybrkgyab56tk,task_subcomment,NA
+VisualEditor: Mouse selection very unreliable in Internet Explorer 10,"Testing on Windows 8 Release Preview running in VirtualBox.
+
+Click to set caret position and click-and-drag to select text don't seem to work reliably in IE 10. Tested both in desktop and Metro mode.
+
+Mouse activity can be seen in mouseover and mousedown text decoration/coloring on links, but ... most of the time the caret doesn't move / selection doesn't change.
+
+Occasionally one gets through, it's not clear how/why.
+
+Note that selection with arrow keys+shift works fine.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340404680,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-ilakhjhigyp4sxfadq5q,task_description,declined
+VisualEditor: Mouse selection very unreliable in Internet Explorer 10,"**orbit** wrote:
+
+This isn't reproducible, but a lot has changed since this bug was reported. The only problem I've noticed is the location of the context menu. I'll open a new bug for that.",1350690829,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ilakhjhigyp4sxfadq5q,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","For mobile, tablets and laptops with high-resolution displays we'll want double-resolution or SVG versions of the icons served. Attached screenshot taken in Firefox 16 nightly with acceleration disabled on MacBook Pro Retina. Looks about the same in Safari.
+
+The current icons appear to be PNG, with a PSD source file that's at low resolution. If the layers are vector shapes this should be easy to convert to high-resolution, but I don't have Photoshop on this machine to double-check.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340401080,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_description,resolved
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","The problem with always using SVG is that at lower DPI the rendering quality is inferior. In most browsers the pixel boundaries are off a bit here and there, making the icons look fuzzy. I think using raster graphics for icons will some day be antiquated, but we aren't there yet.",1347310446,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",Broke out follow-up issue to bug 40140.,1347307985,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","(In reply to comment #7)
+> This sounds like a UserAgent problem. Isn't the UA meant to handle this?
+
+Nope, no information available in the UA for this.
+
+(In reply to comment #8)
+> What about when you have the browser spanning between a low and high DPI
+> screen? We can only depend on devicePixelRatio.
+
+If you're spanning over low and high DPI screens on Mac OS X, the window gets assigned the density of whichever window it has the greatest area on. Eg, either you get 1.0 scale and it's pixelated on the high-res screen, or you get 2.0 scale and it's scaled down on the low-res screen.
+
+The trick is that window.devicePixelRatio may change over time -- it's a property, not a constant. I think you get a window.onresize event when switching ratios, but I'll have to double-check that.
+
+> I think this is closed until there's a better way to detect this.
+
+Yeah it's good enough for now, but I'll file a separate bug as a reminder for later if we find a cleaner way.
+
+The simplest full fix would be to always use SVG when SVG is supported in the browser -- this would also fix it for Internet Explorer 10, which doesn't support devicePixelRatio but has support for higher-resolution screens in Windows 8.",1347307314,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","What about when you have the browser spanning between a low and high DPI screen? We can only depend on devicePixelRatio.
+
+I think this is closed until there's a better way to detect this.",1347304194,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",This sounds like a UserAgent problem. Isn't the UA meant to handle this?,1347304100,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","Hmm.
+
+Actually there's a minor issue: if starting the editing on a low-resolution screen and then switching to high-resolution (by moving the window across screens or changing the screen resolution) we still are stuck with the low-resolution bitmap icons.",1347303656,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","Looks awesome in Safari and Chrome on MacBook Pro with Retina display, thanks guys! :D
+
+(Proper rendering on Firefox will come in future... upstream issues there still but it'll come.)",1347303562,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",Fixed in https://gerrit.wikimedia.org/r/#/c/22113/,1347302633,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",Moving to UI component,1340404205,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)",Mass-moving items into VisualEditor product,1340402721,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+"VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)","Created attachment 10782
+Screenshot on  Retina MacBook Pro
+
+**Attached**: {F9551}",1340401162,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-a2g47wnz3wqen23fp6b7,task_subcomment,NA
+Delete at end of document causes JS error,"As discussed. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340400480,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_description,resolved
+Delete at end of document causes JS error,"I borked that commit - this one is clean:
+
+https://gerrit.wikimedia.org/r/#/c/13177/",1340815105,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_subcomment,NA
+Delete at end of document causes JS error,"**orbit** wrote:
+
+This has been fixed in:
+https://gerrit.wikimedia.org/r/12974
+Will be released soon.",1340668774,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_subcomment,NA
+Delete at end of document causes JS error,"Mass-move out of ""General"" to ""ContentEditable"".",1340415378,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_subcomment,NA
+Delete at end of document causes JS error,Mass-moving items into VisualEditor product,1340402769,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oh5g652d7wxhvdg5yg3r,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,"The current VisualEditor interface has a prominent ""Save page"" button, but no ""Cancel"" button. It would be nice if there were a clear exit strategy in the interface.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340393700,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_description,resolved
+VisualEditor: Interface should have an obvious way to get back to reading mode,Now merged into master.,1354750533,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,"Added cancel button to VisualEditor MediaWiki Integration.
+Patched in https://gerrit.wikimedia.org/r/#/c/36934/
+
+Awaiting review.",1354667827,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,"(In reply to comment #3)
+> Perhaps the browser Back button could be harnessed for this purpose, by
+> changing the actual URL without reloading the page (like Facebook does when
+> browsing photos, for instance) or even just the anchor?
+
+You should file this as a separate bug (if one doesn't exist already). :-)",1340501803,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,"Perhaps the browser Back button could be harnessed for this purpose, by changing the actual URL without reloading the page (like Facebook does when browsing photos, for instance) or even just the anchor?
+
+But yes, I agree that a clearer way of ""cancelling"" needs to be given within the actual interface, in addition to the Back button.",1340500453,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,Trevor - thoughts on this as intended behaviour?,1340413229,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Interface should have an obvious way to get back to reading mode,Mass-moving items into VisualEditor product,1340402727,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4hfyvqkoxqfkrsf53qio,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"Based on some testing on MediaWiki.org, page protection and the abuse filter do not work - page protection does not change the ability of all non-blocked users to edit the page and abuse filter does not pick up any edits generated by the visual editor.
+
+I believe that the underlying problem is that using the visual editor is not a named action that can be restricted or filtered at the moment. If it was, then it would be possible to assign it to $wgRestrictionTypes and it would be possible for the abuse filter to log it (though the abuse filter does need the addition of some variables or other modification to accept visual editor edits).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340391180,PHID-USER-wqc7ciyvfzunj3l2tvjt,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_description,resolved
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306607,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,Fixed in gerrit 31889,1354218776,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,This was fixed when Roan changed to use the normal edit API rather than bypassing it internally.,1354216989,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"This will naturally resolve itself when we lift the namespace-specific restrictions on editing the Wikitext and can use the editing API instead of going through the back door, as we do now.
+
+This is related to bug 38268 - in that these will both be resolved in the same way.",1345672049,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"Two things:
+1.How would an abuse log entry look like? I can't think of anything other than 'Example (talk|contribs) triggered filter 16, performing the action ""usevisualeditor"" on VisualEditor:Welcome' (etc.).
+2.What about page protection?",1340422207,PHID-USER-wqc7ciyvfzunj3l2tvjt,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"AbuseFilter *should* see them, because to do otherwise is insane. That it doesn't is the bug. :)",1340420631,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"AbuseFilter does not see them, because I tested some VE edits against my experimental filter but edits made by the VE did not get caught.
+
+The 'usevisualeditor' permission would only be a temp solution to the current situation where page protection can't cover it. The other way is to require the 'edit' permission but then that wouldn't suffice in our current scheme of having only admins edit the wikitext directly.",1340417825,PHID-USER-wqc7ciyvfzunj3l2tvjt,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,"I would not recommend creating a 'usevisualeditor' permission. Rather, permission checks and the usual edit activity paths should be used. AbuseFilter *should* see VE edits exactly the same as edits made through the traditional editing UI or the API.",1340416947,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission,Mass-moving items into VisualEditor product,1340402735,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2kfniuyxuldpuiatpfod,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"I created a blank page at <https://www.mediawiki.org/wiki/VisualEditor:Hello_there>. When I try to edit the page using the VisualEditor extension, I receive the following error: ""Error loading data from server: No HTML content in response from server. Would you like to retry?""
+
+I imagine this is a safety check somewhere in the code that needs to be tweaked. If page_len == 0, it isn't always an error. Sometimes a blank page is just a blank page. ;-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340390820,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_description,resolved
+VisualEditor: Throws error when trying to edit blank (but existing) page,"Resolved in gerrit.
+
+Change-Id: I8857d39e1a20080c8419c6165be2b5ad0cdbacd2",1351287039,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"(In reply to comment #1)
+> That blank page shouldn't have been possible to create in the first place.
+You can easily create a blank page by first creating a page with content, then blanking it.
+
+(In reply to comment #4)
+> Parsoid does handle zero length content -- it returns a zero length HTML
+> response. Right now, VisualEditor extension expects a non-zero HTML response
+> and returns an error if not (line 18 of ApiVisualEditor.php).  This can be
+> verified at this url:
+> https://www.mediawiki.org/w/api.php?action=ve-parsoid&paction=parse&page=VisualEditor%3AHello_there&format=json
+> (for other pages, the result is success with a valid parsed string).
+Thanks Subbu, that's exactly what was going on. Fix submitted in https://gerrit.wikimedia.org/r/30281 .
+
+> So,
+> either ApiVisualEditor.php has to handle a zero-length response as a valid
+> response, and we need a different way to signal errors from Parsoid, or Parsoid
+> has to always return a non-zero response.   My hunch is that as long as Parsoid
+> returns a 200 OK, ApiVisualEditor accept a zero-length response as a valid
+> response (and if necessary, have sanity checks somewhere -- a non-zero length
+> body should not return a zero-length response, maybe).  Error conditions from
+> Parsoid could be signaled with a different HTTP response code maybe (offhand,
+> 503 is one option). At this time, I am not sure what the right solution is, but
+> hopefully this will help figure out what that might be.
+I verified that nonexistent pages give me a 404, so I think this is fine. I haven't checked other error conditions because they're nontrivial to reproduce, but as long as Parsoid only returns a 2xx status code when it's actually delivering parsed content and uses 4xx/5xx for errors, I'll be fine.",1351285526,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,Moving to DM if we're happy with current Parsoid behaviour - to discuss?,1340565870,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"Actually, I meant 500, not 503.",1340430020,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"Parsoid does handle zero length content -- it returns a zero length HTML response. Right now, VisualEditor extension expects a non-zero HTML response and returns an error if not (line 18 of ApiVisualEditor.php).  This can be verified at this url: https://www.mediawiki.org/w/api.php?action=ve-parsoid&paction=parse&page=VisualEditor%3AHello_there&format=json (for other pages, the result is success with a valid parsed string).  So, either ApiVisualEditor.php has to handle a zero-length response as a valid response, and we need a different way to signal errors from Parsoid, or Parsoid has to always return a non-zero response.   My hunch is that as long as Parsoid returns a 200 OK, ApiVisualEditor accept a zero-length response as a valid response (and if necessary, have sanity checks somewhere -- a non-zero length body should not return a zero-length response, maybe).  Error conditions from Parsoid could be signaled with a different HTTP response code maybe (offhand, 503 is one option). At this time, I am not sure what the right solution is, but hopefully this will help figure out what that might be.",1340428385,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,Mass-moving items into VisualEditor product,1340402745,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,"(In reply to comment #1)
+> That blank page shouldn't have been possible to create in the first place.
+
+Heh, well I originally created the page as the brand new account I was using to test VisualEditor didn't have the createpage right (for whatever reason).
+
+To be clear, this bug is not about VisualEditor creating a blank page. This bug is about VisualEditor throwing an error when the page length is 0 bytes and the user attempts to edit the page using the VisualEditor interface. <https://www.mediawiki.org/wiki/VisualEditor:Blank_page> is another test case.
+
+For discussion regarding whether MediaWiki should allow users to create blank pages, you want bug 12621. :-)",1340401108,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Throws error when trying to edit blank (but existing) page,That blank page shouldn't have been possible to create in the first place.,1340390983,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ksttu36zsaoc7fxnzt2x,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"If I input <nowiki>a</nowiki> in VE, save the page, then go back to the editor, text is broken in VE there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340390460,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_description,resolved
+VisualEditor: Improperly escapes <nowiki>,[Parsoid component reorg by merging CPP/* tickets into General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934305,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,Now merged.,1344447584,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,Fix submitted in https://gerrit.wikimedia.org/r/17921.,1344298000,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"So to be entirely clear:
+
+$ echo ""&lt;nowiki&gt;a&lt;/nowiki&gt;"" | node parse.js --html2wt
+
+actual
+<nowiki>&lt;nowiki&gt;</nowiki>a<nowiki>&lt;/nowiki&gt;</nowiki>
+
+expected
+## &lt;nowiki&gt;a&lt;/nowiki&gt;
+
+The problem is pretty clearly in mw.WikitextSerializer.js, near line 152, in the function wrapNonTextTokens. The serializer escapes any instances of <\/?nowiki> with its HTML-entitied counterpart, then wraps it in <nowiki>. I don't know why right now.
+
+`git blame` seems to think Gabriel would know :)",1344295746,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,Hmm- seems as if I made a mistake while testing this. There might be a Parsoid bug after all.,1344294838,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"<nowiki> is invalid HTML. The DOM representation of nowiki is <span typeof=""mw:Nowiki"">, which round-trips ok. Not sure if the VE handles this properly right now.
+
+<nowiki> in a DOM text node (&lt;nowiki&gt; when entered in the HTML -> wikitext test form) properly serializes to &lt;nowiki&gt;.
+
+Please test round-trip stuff on http://parsoid.wmflabs.org/ if possible ;)",1344294424,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"Oh, never mind.  I got it wrong.  So, the input is not what I tested against.  The text to test is ""&lt;nowiki&gt;a&lt;/nowiki&gt;",1344291499,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"Cannot replicate this either at http://parsoid.wmflabs.org/_html/ or on my CLI (excess newlines trimmed below) with the current HEAD.
+
+------------------
+[subbu@earth lib] echo ""<nowiki>a</nowiki>"" | node parse.js --html2wt 
+<nowiki>a</nowiki>
+
+[subbu@earth lib] echo ""<nowiki>a</nowiki>"" | node parse.js --html2wt | node parse.js
+<p><span typeof=""mw:Nowiki"" data-parsoid=""{&quot;tsr&quot;:[0,8],&quot;bsp&quot;:[0,18]}"">a</span></p>
+
+[subbu@earth lib] echo ""<nowiki>a</nowiki>"" | node parse.js --html2wt | node parse.js | node parse.js --html2wt
+<nowiki>a</nowiki>
+
+--------------------
+
+Either VE is using an older Parsoid version -- or something else is broken.",1344291251,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"Actually a Parsoid bug, moving.",1344290870,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,I would expect as wikitext: &lt;nowiki&gt;a&lt;/nowiki&gt;,1340417145,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,"Input HTML: <nowiki>a</nowiki>
+
+Actual output wikitext after RT: <nowiki>&lt;nowiki&gt;</nowiki>a<nowiki>&lt;/nowiki&gt;</nowiki>
+
+Expected wikitext: ???",1340412863,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+VisualEditor: Improperly escapes <nowiki>,Mass-moving items into VisualEditor product,1340402750,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-clc63qvmswgkzbw33tkq,task_subcomment,NA
+"VisualEditor: Shift-Page {Up,Down} selection only works upwards","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340388180,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mxb522dezlpdexpuwpqh,task_description,declined
+"VisualEditor: Shift-Page {Up,Down} selection only works upwards","**orbit** wrote:
+
+This was probably true at one point, but the work that I've done with native key handling looks to have fixed this.",1350000249,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-mxb522dezlpdexpuwpqh,task_subcomment,NA
+"VisualEditor: Shift-Page {Up,Down} selection only works upwards",Mass-moving items into VisualEditor product,1340402752,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mxb522dezlpdexpuwpqh,task_subcomment,NA
+"VisualEditor: Shift-Page {Up,Down} selection only works upwards","(In reply to comment #0)
+> 
+
+Please don't do this. Bug summaries often change over time. The bug description (comment 0) should be useful.",1340394886,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-mxb522dezlpdexpuwpqh,task_subcomment,NA
+VisualEditor: Shift-cursor selection downwards switches to upwards selection once you use Up or Right arrow,"Place the caret. Press Shift and then a downwards selection key (i.e. Down or Right arrow). As expected, you move the caret downwards correctly using either key. 
+
+However, after some text is selected, pressing Up or Left causes the caret to move to the start of the selection to expand (rather than allowing the leading edge of the selection to be reduced). All further shift-cursor key presses (Up/Down/Left/Right) only change the position of the earlier part of the selection, and you can no-longer select as desired.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340388060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-anbufyvs4yecgr5utuge,task_description,resolved
+VisualEditor: Shift-cursor selection downwards switches to upwards selection once you use Up or Right arrow,"**orbit** wrote:
+
+This is fixed now due to native cursor handling.",1350000874,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-anbufyvs4yecgr5utuge,task_subcomment,NA
+VisualEditor: Shift-cursor selection downwards switches to upwards selection once you use Up or Right arrow,Mass-moving items into VisualEditor product,1340402778,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-anbufyvs4yecgr5utuge,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"See https://www.mediawiki.org/w/index.php?title=VisualEditor:BugLinkSelection&action=history
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340341920,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uccw7yqukr3actwcyct3,task_description,resolved
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #13)
+> Yes, thank you, that was very helpful. I've no idea how the hell anyone is
+> supposed to know that (beyond reading your comment here on this bug).
+Yeah, I apologize for the poor discoverability of this information :(
+
+> It'd be
+> nice if http://wikitech.wikimedia.org/view/Software_deployments and
+> https://www.mediawiki.org/wiki/MediaWiki_1.20/Roadmap noted this. Is this only
+> for VisualEditor or are all Wikimedia extensions updated every two weeks now?
+All WMF extensions are updated from master every two weeks, same as core. Some WMF-maintained extensions have additional deployment windows scheduled to accelerate deployments, but everything is on the two-weekly deployment train. If people want their deployments to be slower, we tell them to keep their code out of master until it's ready.",1344536745,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #12)
+> (In reply to comment #7)
+> > Hmm, perhaps VisualEditor should have some kind of exposure of a version number
+> > or last deployment date? Given the frequent deployments and code changes, I
+> > think it'd be helpful for testing and bug-filing. I'm not sure if
+> > Special:Version covers this already. Perhaps a separate bug is needed?
+> > 
+> Special:Version lists the git hash of the deployed version, which isn't perfect
+> (and was out of date until just now). There is also a version number there
+> which is currently just set to 0.1, I suppose we could start using that field,
+> either by incrementing it each time or by using something like 0.1-20120806.
+
+It'd certainly be nice for debugging, yes. I was thinking about some kind of user preference or URL parameter or something that would add an HTML comment with useful debug info in it. I can imagine a few data points being helpful, but particularly VisualEditor version number, so people don't end up chasing down bugs that were fixed a week ago.
+
+> Anyway, as for deployment frequency: not counting the fixup deployments that
+> occurred yesterday because various things were broken, there is only one VE
+> deployment every two weeks, on the first Monday of every deployment cycle. The
+> most recent deployment was last Monday (Aug 6), the next one will be on Aug 20,
+> then two weeks after that, etc. This is because our code comes along for the
+> ride with the 1.20wmf* deployments (see
+> https://www.mediawiki.org/wiki/MediaWiki_1.20/Roadmap for the schedule) and the
+> only wiki where VE is currently deployed (mw.org) is part of phase 0, which
+> occurs on the first Monday.
+> 
+> Hope that clears things up a bit.
+
+Yes, thank you, that was very helpful. I've no idea how the hell anyone is supposed to know that (beyond reading your comment here on this bug). It'd be nice if http://wikitech.wikimedia.org/view/Software_deployments and https://www.mediawiki.org/wiki/MediaWiki_1.20/Roadmap noted this. Is this only for VisualEditor or are all Wikimedia extensions updated every two weeks now?",1344463399,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #7)
+> Hmm, perhaps VisualEditor should have some kind of exposure of a version number
+> or last deployment date? Given the frequent deployments and code changes, I
+> think it'd be helpful for testing and bug-filing. I'm not sure if
+> Special:Version covers this already. Perhaps a separate bug is needed?
+> 
+Special:Version lists the git hash of the deployed version, which isn't perfect (and was out of date until just now). There is also a version number there which is currently just set to 0.1, I suppose we could start using that field, either by incrementing it each time or by using something like 0.1-20120806.
+
+Anyway, as for deployment frequency: not counting the fixup deployments that occurred yesterday because various things were broken, there is only one VE deployment every two weeks, on the first Monday of every deployment cycle. The most recent deployment was last Monday (Aug 6), the next one will be on Aug 20, then two weeks after that, etc. This is because our code comes along for the ride with the 1.20wmf* deployments (see https://www.mediawiki.org/wiki/MediaWiki_1.20/Roadmap for the schedule) and the only wiki where VE is currently deployed (mw.org) is part of phase 0, which occurs on the first Monday.
+
+Hope that clears things up a bit.",1344439874,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #5)
+> No. :-) Per http://wikitech.wikimedia.org/view/Software_deployments#Ongoing it
+> is scheduled to happen from 19 minutes' time, for up to three hours. Remarking
+> as resolved.
+
+I looked at <http://wikitech.wikimedia.org/view/Software_deployments#Ongoing> and its associated page history and I have no idea what this comment is referring to. There's no mention of VisualEditor on that page. The only mention of VisualEditor I can find is at <http://wikitech.wikimedia.org/view/Software_deployments/2012_archive> in an entry dated June 21.",1344393140,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #9)
+> Max - This bug is already explicitly tagged against a release milestone (this
+> last Monday's), as you'd see if you looked. :-)
+
+James, I saw the bug filer not being able to verify that the bug was fixed. That's more than enough to mark it as reopened. Start meeting your deployment schedule and provide a way to measure which version of VisualEditor is deployed (in addition to, you know, fixing the actual reported bug) and then you can comment about what I did or did not notice.",1344392173,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"Max - This bug is already explicitly tagged against a release milestone (this last Monday's), as you'd see if you looked. :-)
+
+Liangent - This is fixed and 'in live' as of yesterday, but unfortunately you won't be able to tell as bug 39111 has broken the link inspector entirely (sorry, we should have tested this before deployment). Will live-patch in the next few hours, at which point I'll ping back on this bug.",1344376920,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #7)
+> Re-opening this bug for now. Until the bug filer can verify that the bug has
+> been fixed, it doesn't make much sense to mark it as such. We don't really use
+> ""verified"" in our current Bugzilla workflow, though perhaps we ought to in the
+> future.
+
+Some of us are using it, see bug 39040.",1344376044,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #6)
+> (In reply to comment #5)
+>> No. :-) Per http://wikitech.wikimedia.org/view/Software_deployments#Ongoing it
+>> is scheduled to happen from 19 minutes' time, for up to three hours. Remarking
+>> as resolved.
+> 
+> Is it deployed now so I can re-test these bugs?
+
+Hmm, perhaps VisualEditor should have some kind of exposure of a version number or last deployment date? Given the frequent deployments and code changes, I think it'd be helpful for testing and bug-filing. I'm not sure if Special:Version covers this already. Perhaps a separate bug is needed?
+
+Re-opening this bug for now. Until the bug filer can verify that the bug has been fixed, it doesn't make much sense to mark it as such. We don't really use ""verified"" in our current Bugzilla workflow, though perhaps we ought to in the future.",1344375713,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"(In reply to comment #5)
+> No. :-) Per http://wikitech.wikimedia.org/view/Software_deployments#Ongoing it
+> is scheduled to happen from 19 minutes' time, for up to three hours. Remarking
+> as resolved.
+
+Is it deployed now so I can re-test these bugs?",1344371737,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"No. :-) Per http://wikitech.wikimedia.org/view/Software_deployments#Ongoing it is scheduled to happen from 19 minutes' time, for up to three hours. Remarking as resolved.",1344274949,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,"Ouch, did the deployment take place?",1344273953,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,Not fixed: https://www.mediawiki.org/w/index.php?title=VisualEditor:BugLinkSelection&diff=569584&oldid=569582,1344273914,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,Fixed and included in August 6th deployment.,1343672405,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+VisualEditor: Creating link over an existing link is broken,Mass-moving items into VisualEditor product,1340402747,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uccw7yqukr3actwcyct3,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box","In ""Save page"" dialog, the content of message <minoredit> is not parsed and raw wikitext is displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340341320,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_description,resolved
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Confirmed that this is due to a local browser cache. Re-marking as fixed.,1344881831,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Where are you seeing this? This is working for me both on localhost and mw.org,1344541358,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box","Created attachment 10946
+Screenshot of raw wikitext for minor edit in save dialog
+
+**Attached**: {F9508}",1344485877,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",It's back.,1344485828,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Now deployed.,1343175512,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",minoredit fixed in https://gerrit.wikimedia.org/r/#/c/14603/,1341637400,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Also the watchthis message (Watch this page),1340431216,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Also other elements of the interface?,1340405611,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+"VisualEditor: Messages minoredit, watchthis not parsed in ""save page"" dialog box",Mass-moving items into VisualEditor product,1340402730,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yfp5mfkl2pgmbsvfh5vf,task_subcomment,NA
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,"== section ==
+
+# number      <cursor pops up here>
+# number
+<enter>
+<enter>
+
+== <when you type, the cursor pops down here and starts editing> section ==
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340318220,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-7piycxpmx56ohmyj2zuk,task_description,declined
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,"**orbit** wrote:
+
+I wasn't able to reproduce in Chrome on Mac or Windows. We had some earlier problems with exiting lists after double-enter, so maybe this bug was reported then.",1341267913,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7piycxpmx56ohmyj2zuk,task_subcomment,NA
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,Mass-moving items into VisualEditor product,1340402778,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7piycxpmx56ohmyj2zuk,task_subcomment,NA
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,"I take that back, it's in Chrome 19.",1340318316,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-7piycxpmx56ohmyj2zuk,task_subcomment,NA
+VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading,This is in Firefox 13.0.1,1340318274,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-7piycxpmx56ohmyj2zuk,task_subcomment,NA
+VisualEditor has broken delete behavior on end-of-file,"* Move cursor to last line of the page.
+* Delete till all subsequent empty lines are removed.
+* The next delete will remove the first character of the line and subsequent deletes delete larger chunks of text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340317440,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ryivokqumebwl4y5m3ua,task_description,resolved
+VisualEditor has broken delete behavior on end-of-file,"**orbit** wrote:
+
+Yep, this is a duplicate of 37813, which is now fixed.
+
+%%%*** This bug has been marked as a duplicate of bug 37813 ***%%%",1341267573,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ryivokqumebwl4y5m3ua,task_subcomment,NA
+VisualEditor has broken delete behavior on end-of-file,Mass-moving items into VisualEditor product,1340402773,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ryivokqumebwl4y5m3ua,task_subcomment,NA
+VisualEditor has broken delete behavior on end-of-file,Is this bug related to bug 37813?,1340396450,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ryivokqumebwl4y5m3ua,task_subcomment,NA
+VisualEditor has broken delete behavior on end-of-file,"Confirmed.
+
+When I press delete to remove the last character of the last line, I get:
+----
+Uncaught TypeError: Cannot read property 'node' of undefined ve.ce.Surface.js:847
+ve.ce.Surface.showSelection ve.ce.Surface.js:847
+ve.ce.Surface.onChange ve.ce.Surface.js:588
+jQuery.extend.proxy.proxy load.php:816
+ve.EventEmitter.emit ve.EventEmitter.js:33
+ve.dm.Surface.change ve.dm.Surface.js:88
+ve.ce.Surface.handleDelete ve.ce.Surface.js:753
+ve.ce.Surface.onKeyDown ve.ce.Surface.js:194
+jQuery.extend.proxy.proxy load.php:816
+jQuery.event.dispatch load.php:3332
+jQuery.event.add.elemData.handle.eventHandle
+----
+using Google Chrome 19.0.1084.56 on
+https://www.mediawiki.org/wiki/VisualEditor:Sandbox?debug=1
+
+Then, the cursor jumps to the beginning of the line. Subsequent delete will start removing the first characters.",1340334551,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ryivokqumebwl4y5m3ua,task_subcomment,NA
+VisualEditor: Text added to line below cursor,"Steps to reproduce:
+
+* Create a bunch of empty lines by hitting enter key
+* Move cursor up to the 1st/2nd empty line and start typing -- the first couple chars are inserted on the line below
+
+Can also reproduce this in other ways:
+* delete to end of line, enter a bunch of empty lines, move cursor to one of the middle empty lines and start typing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340316960,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-kpq3munittovusy35opj,task_description,declined
+VisualEditor: Text added to line below cursor,"**orbit** wrote:
+
+This probably was the case a while ago, but Inez has done a ton of work with typing in slugs. This isn't a problem any longer.",1350000047,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kpq3munittovusy35opj,task_subcomment,NA
+VisualEditor: Text added to line below cursor,Mass-moving items into VisualEditor product,1340402760,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kpq3munittovusy35opj,task_subcomment,NA
+VisualEditor: Lost text after deleting to/from EOF,"Steps to reproduce this on VE:
+
+* delete text to (or from) end of file using either backspace or delete key
+* type text and hit the return key,
+* the typed text is lost
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=37815",1340316720,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_description,resolved
+VisualEditor: Lost text after deleting to/from EOF,"**orbit** wrote:
+
+%%%*** Bug 37815 has been marked as a duplicate of this bug. ***%%%",1341267573,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_subcomment,NA
+VisualEditor: Lost text after deleting to/from EOF,"**orbit** wrote:
+
+This was fixed a little while ago, but was dropped due to a screwy merge. The fix has been recommitted:
+https://gerrit.wikimedia.org/r/13955",1341267341,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_subcomment,NA
+VisualEditor: Lost text after deleting to/from EOF,Re-assigning.,1341267286,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_subcomment,NA
+VisualEditor: Lost text after deleting to/from EOF,Mass-moving items into VisualEditor product,1340402734,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jvcrri6ivphdq3gs6cdy,task_subcomment,NA
+"VisualEditor: editing toolbar float trigger also triggers contextView icon, although there is no context to act on","When the editing toolbar trigger is triggered (either floating or defloating the editing toolbar), it also triggers the contextView icon to appear wherever the text cursor is, even if no text is selected. And of course you can't use any of the contextView tools while no text is selected. Once this occurs, subsequent interaction with the page is inconsistent. For example if you try to reposition the cursor it jumps back to the old location as soon as you start typing. Verified in Firefox and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1340315820,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ysuesdqax3nucpqxzzrl,task_description,resolved
+"VisualEditor: editing toolbar float trigger also triggers contextView icon, although there is no context to act on",Fixed in https://gerrit.wikimedia.org/r/13913,1341258696,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-ysuesdqax3nucpqxzzrl,task_subcomment,NA
+"VisualEditor: editing toolbar float trigger also triggers contextView icon, although there is no context to act on",Mass-moving items into VisualEditor product,1340402718,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ysuesdqax3nucpqxzzrl,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"**Author:** `dbaran`
+
+**Description:**
+Browser = Chrome 19.0.1084.56
+
+Clickstream:
+
+--used formatting toolbar to select bullet
+--entered single word
+--changed focus from browser to different window (skype I think)
+--changed focus back to browser by mousing back to bullet list
+--hit enter
+--nothing happened.  cursor didn't move.  
+
+
+I can reproduce consistently by typing in another window, then coming back to browser, and cursor will be stuck.  However if I perform some action in another tab of the browser, when I return to the tab in which I'm editing, the cursor works, although it requires hitting enter more than once.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7
+**Platform**: PC
+**URL**: https://internal.wikia-inc.com/wiki/New_Visual_Editor 	",1340314980,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gztnciutz4zkajephs5s,task_description,resolved
+VisualEditor: bullet list breaking after changing window focus,"**orbit** wrote:
+
+I committed some fixes for handling at the end of the document, which likely fixed this bug. I'm following the clickstream exactly and am unable to reproduce the problem. Daniel also showed me this bug on his computer, so I have a very good understanding of what the bug looked like.",1341002667,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,Reassigning per Christian's request.,1341002609,PHID-USER-p5svl2m3pqm6jjgznnhz,False,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,Mass-moving items into VisualEditor product,1340402715,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"**dbaran** wrote:
+
+No problemo.  Here's the errors with line numbers, and a detailed description of the actions I took:
+
+--loaded editor, placed cursor at end of bullet item (the word ""traffic"" at the very end of the article)
+--clicked away to skype, clicked back to browser with cursor still at end of list item, hit enter.  following error resulted:
+
+Uncaught TypeError: Cannot read property 'node' of undefined ve.ce.Surface.js:848
+
+hit enter again, and cursor moved down to beginning of next line, no bullet added.  hit backspace to return to previous line, following error resulted:
+
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.dm.Document.js:429
+
+Hit enter again, and cursor didn't move, following error resulted:
+
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.ce.Document.js:21
+
+hit enter a few more times, no cursor movement, and the following same errors:
+
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.ce.Document.js:21
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.ce.Document.js:21
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null ve.ce.Document.js:21",1340316338,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"Sorry, I should have told you this earlier: could you please set ?debug=true at the end of the URL and try again? That should assign the real line numbers to the errors.",1340315636,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"**dbaran** wrote:
+
+right, should have done the the first time.  Errors as follows:
+
+Uncaught TypeError: Cannot read property 'node' of undefined bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:202
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:141
+2Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:179
+Uncaught TypeError: Cannot read property 'node' of undefined bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:202
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:141
+11Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:179
+Uncaught TypeError: Cannot read property 'node' of undefined bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:202
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:141
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%7Crangy&skin=vector&version=20120621T210603Z&*:179",1340315455,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+VisualEditor: bullet list breaking after changing window focus,"Can you see any JS errors in the debugging console? To access this in Chrome, right-click anywhere on the page, selecting ""Inspect element"", then in the inspector that pops up at the bottom of the window go to the ""Console"" tab. If you see any error messages appear there, please post them here.",1340315147,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gztnciutz4zkajephs5s,task_subcomment,NA
+"Hit Enter at the end of a heading, blinking cursor disappears","**Author:** `sumanah`
+
+**Description:**
+Cursor should show up where the red circle indicates
+
+I went to https://www.mediawiki.org/wiki/VisualEditor:Test , hit Edit, clicked just at the end of a heading (got a blinking cursor), and hit Enter. A newline appeared, but there was no blinking cursor to indicate where I was; the cursor had disappeared.
+
+I can replicate this.  Firefox 11.0, Firebug is off, Ubuntu 11.10.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9494}",1340314620,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nfo3xiyndruo5aeqves4,task_description,resolved
+"Hit Enter at the end of a heading, blinking cursor disappears",Noting bugs closed in the 2012-10-15 release.,1351534183,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nfo3xiyndruo5aeqves4,task_subcomment,NA
+"Hit Enter at the end of a heading, blinking cursor disappears",Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341823,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nfo3xiyndruo5aeqves4,task_subcomment,NA
+"Hit Enter at the end of a heading, blinking cursor disappears",Fixed in https://gerrit.wikimedia.org/r/12541,1340315734,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nfo3xiyndruo5aeqves4,task_subcomment,NA
+VisualEditor freaks out on <span>,"After I vandalised the test page with[1], trying to edit this page resulted in ""renderers[annotation.type] is undefined""
+
+var openAnnotations = function( annotations ) {
+    var out = '',
+        annotation;
+    for ( var hash in annotations ) {
+        annotation = annotations[hash];
+        out += typeof renderers[annotation.type].open === 'function' ? <-- here
+            renderers[annotation.type].open( annotation.data ) :
+            renderers[annotation.type].open;
+        hashStack.push( hash );
+        annotationStack[hash] = annotation;
+    }
+
+
+----
+[1] https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=552553&oldid=552537
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340314080,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-rjxemhifa3x2566jx3he,task_description,resolved
+VisualEditor freaks out on <span>,Noting bugs closed in the 2012-10-15 release.,1351534191,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rjxemhifa3x2566jx3he,task_subcomment,NA
+VisualEditor freaks out on <span>,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341837,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rjxemhifa3x2566jx3he,task_subcomment,NA
+VisualEditor freaks out on <span>,"Fixed in https://gerrit.wikimedia.org/r/12539 , pending review in Gerrit.",1340315424,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rjxemhifa3x2566jx3he,task_subcomment,NA
+VisualEditor freaks out on <span>,"Yeah, this is because span is listed as an annotation but has no renderer defined. Fixing.",1340314167,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rjxemhifa3x2566jx3he,task_subcomment,NA
+Backspace deletes more than one character on newly-added text,"If you type in something new using VisualEditor, and then you press the backspace key, you end up deleting all of what you wrote plus the character immediately before. This seems to delete about 3-5 characters at a time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340310360,PHID-USER-wqc7ciyvfzunj3l2tvjt,False,PHID-TASK-tdi5kkh4rg6wvf7cam7m,task_description,resolved
+Backspace deletes more than one character on newly-added text,"**orbit** wrote:
+
+I don't think this is actually about newly-added text, but rather deleting text after you'd switched windows and then came back to the editor. There was a bug in which event handling was bound twice, causing the double backspace problem. Fixed and will release soon.
+https://gerrit.wikimedia.org/r/#/c/12701/",1340404706,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tdi5kkh4rg6wvf7cam7m,task_subcomment,NA
+Backspace deletes more than one character on newly-added text,Mass-moving items into VisualEditor product,1340402759,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tdi5kkh4rg6wvf7cam7m,task_subcomment,NA
+Backspace deletes more than one character on newly-added text,Confirmed in Chrome on Mac OS X too.,1340389821,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tdi5kkh4rg6wvf7cam7m,task_subcomment,NA
+VisualEditor: Link box should suggest page titles,"The input box used to select target pages for links should display suggestions for pages, like WikiEditor's ""Insert link"" dialog box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1339495020,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-6qteafzaet5hssww25zp,task_description,resolved
+VisualEditor: Link box should suggest page titles,Fixed in https://gerrit.wikimedia.org/r/#/c/19784/,1345486519,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6qteafzaet5hssww25zp,task_subcomment,NA
+VisualEditor: Link box should suggest page titles,Standardise title.,1341257320,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6qteafzaet5hssww25zp,task_subcomment,NA
+VisualEditor: Link box should suggest page titles,Mass-moving items into VisualEditor product,1340402775,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6qteafzaet5hssww25zp,task_subcomment,NA
+VisualEditor: Link box should suggest page titles,Bug 33053 is related.,1340333248,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-6qteafzaet5hssww25zp,task_subcomment,NA
+VisualEditor: npm dependencies,"New file to track npm dependencies
+
+This patch will make it simpler to install node module dependencies.  When the package.json file exists, running ""npm install"" with no arguments will create a directory ""node_modules"" and fetch dependencies.
+
+There are some related improvements to be made, such as editing the Makefile to point NODE_PATH to this directory.  Actually, I don't know what the recommended practice is here--seems like this should be in node's default require path.
+
+My focus was on running the tests, not sure about how to reuse this file for server configuration.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F9216}",1332324240,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-kil3chqyjneigkvf34lu,task_description,resolved
+VisualEditor: npm dependencies,Mass-moving bugs into the new 'Parsoid' product.,1344281146,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,"**wicke** wrote:
+
+Merged a while ago.",1340471199,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,Assuming this is for Gabriel,1340403596,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,Mass-moving items into VisualEditor product,1340402729,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,"What's the status of this bug?
+
+And can someone please clarify the bug summary? I have no idea what ""npm dependencies"" means.",1340396178,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+VisualEditor: npm dependencies,"**sumanah** wrote:
+
+Thanks for the patch, Adam! I've added keywords to indicate that this patch awaits code review.",1332356041,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kil3chqyjneigkvf34lu,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"**Author:** `rahuldeshmukh101`
+
+**Description:**
+Is it possible to make Extension:Semantic Forms available on mr.wikipedia .
+
+If so please enable it for mr wiki.
+
+Thanks
+
+Rahul Deshmukh
+
+User:rahuldeshmukh101
+Admin mr.wikipedia
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1331345460,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6goh2k74apor363cgxbh,task_description,declined
+Enable Semantic Forms on mrwiki,"(In reply to comment #9)
+> RESOLVED INVALID: Author does not seem think this extension should be reviewed
+> for deployment, and I am not aware of any community consensus for this change.
+
+I would call that a wontfix...",1343163065,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"RESOLVED INVALID: Author does not seem think this extension should be reviewed for deployment, and I am not aware of any community consensus for this change.",1343163005,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"**rahuldeshmukh101** wrote:
+
+So what is the direction for next action from my side ?",1339117448,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,As I just wrote on the similar request for the Czech Wikipedia: I think the combination of the upcoming VisualEditor and Wikidata projects make this request obsolete - I don't believe there's any chance that Wikipedia will ever use Semantic Forms. (Unfortunately.),1339084567,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,So apparently the extension is not reviewed and labsconsole isn't in the cluster which is why it can have the extension. Added extension author to the CC list.,1339082215,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,I see Semantic Forms is deployed on labsconsole. Does that mean it's deployable elsewhere now? And is there consensus for this to be deployed on mrwiki?,1339078434,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"**rahuldeshmukh101** wrote:
+
+That I will put for opinion immediately. - Rahul",1331451811,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,Also needs community consensus.,1331354493,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,"**rahuldeshmukh101** wrote:
+
+Please do the needful - Rahul",1331354390,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Enable Semantic Forms on mrwiki,Extension requires review before deployment can occur. It is currently not in a deployable state for wikimedia projects,1331347729,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-6goh2k74apor363cgxbh,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,"Since incorrect date entry causes unnecessary work for other users, or new users to receive bot or user corrections, generally providing a negative experience, especially for new users. Additionally until fixed, this leads to inconsistencies in data. 
+
+Correcting these automatically, either at input time or post edit see — http://momentjs.com/",1415519616,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-j3ofm67egbuxxvm3t7el,task_description,invalid
+Polish : Date entry in citations should be automatically reformatted to community norms ,">>! In T1186#1006024, @Krenair wrote:
+> Which community's norms? Is this a Citoid thing? A VisualEditor thing?
+
+(Or Cite?)
+
+This still needs an answer.",1475422832,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,">>! In T1186#1006024, @Krenair wrote:
+> Which community's norms? Is this a Citoid thing? A VisualEditor thing?",1422906231,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,Other aspects of VE are site/language specific. I don't see why this would be significantly different. ,1422690738,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,Which community's norms? Is this a Citoid thing? A VisualEditor thing?,1422688635,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,Which Polish community norms? Is this a Citoid thing? A VisualEditor thing?,1422688546,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,"I didn't say it was easy, but I'm pretty sure its possible…",1421438873,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+Polish : Date entry in citations should be automatically reformatted to community norms ,"If I get this bug right, it's anything but easy...
+
+Also adding something like momentjs and having it run over the wikitext entered by users (how?) and then correcting invalid dates could be controversial as we never did something like that before.",1421434183,PHID-USER-2mey32xhshfnf7rz7jjn,True,PHID-TASK-j3ofm67egbuxxvm3t7el,task_subcomment,NA
+"VisualEditor / General project should be imported as simply ""VisualEditor""","It's just a catch-all component, and isn't needed.",1414164555,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_description,declined
+"VisualEditor / General project should be imported as simply ""VisualEditor""",">>! In T856#14542, @Qgil wrote:
+> Well, if there is a better decision we have still time to change it. What agreement are you referring to? That task got just too long with too many topics mixed.
+
+I was going by T43#641 and related comments, and didn't see T43#653 and later comments. Happy to stand by T43#653 and then change it afterwards.",1414171154,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_subcomment,NA
+"VisualEditor / General project should be imported as simply ""VisualEditor""","Well, if there is a better decision we have still time to change it. What agreement are you referring to? That task got just too long with too many topics mixed.",1414169492,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_subcomment,NA
+"VisualEditor / General project should be imported as simply ""VisualEditor""",">>! In T856#14469, @Qgil wrote:
+> The script applies common rules for everybody, as it was defined in {T43}.
+> 
+> I agree that ""VisualEditor"" is better. However, project owners can just apply changes like this after the migration. You will be able to fine tune the names of your projects, following the [[ https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Name | naming guidelines ]], or proposing improvements to the guidelines.
+
+Oh. After I thought that we had all agreed on what would be done in that task, the decision got reversed. :-( No wonder I was confused.",1414166779,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_subcomment,NA
+"VisualEditor / General project should be imported as simply ""VisualEditor""","The script applies common rules for everybody, as it was defined in {T43}.
+
+I agree that ""VisualEditor"" is better. However, project owners can just apply changes like this after the migration. You will be able to fine tune the names of your projects, following the [[ https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Name | naming guidelines ]], or proposing improvements to the guidelines.",1414165658,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-sunqzkbtk2xufhfoaa2r,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","As a logged in user with beta access to VisualEditor using MobileFrontend, edit a new page on beta labs, e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Apsidufapodifuasdf or some such. 
+
+Click the pencil icon to edit the page.  I think this should bring up VE, but brings up wikitext editor instead. 
+
+From the gear menu, click Edit to invoke VE
+
+Again from the gear menu, click Edit source. 
+
+VE fails to disappear. Wikitext editor does not appear. No VE controls like Bold/Italic/Link etc. function at this point. 
+
+This is the failure at https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/455/testReport/(root)/VisualEditor%20Mobile/Switch_from_VisualEditor_to_source_editor/
+
+",1419890230,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_description,resolved
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing",Verified in en.wiki,1421362417,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Thanks. VE on mobile is apparently still broken, tracked as T85897.",1420510122,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Change 182943 merged by Aude:
+Fix naming issue to restore ability to switch between editors
+
+[[https://gerrit.wikimedia.org/r/182943]]",1420505903,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Change 182943 had a related patch set uploaded (by Kaldari):
+Fix naming issue to restore ability to switch between editors
+
+[[https://gerrit.wikimedia.org/r/182943]]
+
+#patch-for-review",1420497926,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing",This probably needs some swift backporting to wmf13?,1420475395,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing",Verified in betalabs.  test2 still have problems with switching between Edit and Edit source.,1419985114,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Change 182113 merged by jenkins-bot:
+Fix naming issue to restore ability to switch between editors
+
+[[https://gerrit.wikimedia.org/r/182113]]",1419978869,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","Change 182113 had a related patch set uploaded (by Jdlrobson):
+Fix naming issue to restore ability to switch between editors
+
+[[https://gerrit.wikimedia.org/r/182113]]
+
+#patch-for-review",1419895828,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+"in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing","The following error is displayed: 
+Uncaught TypeError: boolean is not a functionload.php?debug=false&lang=en&modules=mobile.abusefilter|mobile.editor.common%2Coverlay&skin=minerva…:8 Overlay.extend.hideload.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cmwcore|mobile.editor.ve|oojs-ui&skin=m…:624 EditorOverlayBase.extend.hideVM367:16 Class.extend._hideOverlayVM367:17 Class.extend.replaceCurrentload.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cmwcore|mobile.editor.ve|oojs-ui&skin=m…:625 (anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:45 fireload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:46 self.fireWithload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:47 deferred.(anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:168 mw.loader.usingload.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cmwcore|mobile.editor.ve|oojs-ui&skin=m…:625 EditorOverlayBase.extend.switchToSourceEditorload.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cmwcore|mobile.editor.ve|oojs-ui&skin=m…:624 (anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:65 jQuery.event.dispatchload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=minerva&version=20141220T…:60 elemData.handle",1419891872,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-m7dvl6wigpdkychmqdou,task_subcomment,NA
+Uncaught TypeError when strating mobile VisualEditor,"ve.ui.Toolbar.js:224 Uncaught TypeError: Cannot read property 'triggerListener' of undefined
+
+Example: https://m.mediawiki.org/wiki/MediaWiki_1.25/Roadmap?debug=true#/editor/0",1419625243,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-mi6bk4kxywbgiufipreu,task_description,duplicate
+VisualEditor not loading in el.wikipedia,VisualEditor is not loading in el.wikipedia since yesterday.,1419072099,PHID-USER-e7gwd3ou5ocdumo42srg,False,PHID-TASK-u6ckhkexjtiftpwrkmpc,task_description,invalid
+VisualEditor not loading in el.wikipedia,Checked VE for el.wikipedia in production.,1419294837,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-u6ckhkexjtiftpwrkmpc,task_subcomment,NA
+VisualEditor not loading in el.wikipedia,Resolved by  [[https://el.wikipedia.org/w/index.php?title=MediaWiki:Common.js&diff=4979660&oldid=4917315|removing some code from Mediawiki:Common.js]] (although it was there for ages without problems).,1419079272,PHID-USER-e7gwd3ou5ocdumo42srg,False,PHID-TASK-u6ckhkexjtiftpwrkmpc,task_subcomment,NA
+Editing breaks and edit button does nothing after switching from VE to wikitext editor,"
+As a logged-in user with access to VisualEditor visit any page e.g http://en.m.wikipedia.beta.wmflabs.org/w/index.php?title=Selenium_Test_Edit
+
+Click Edit to bring up VE
+
+From the gear menu select Edit source
+
+No wikitext editor appears, but there is an edit icon on the page.
+
+Click the edit icon. It does nothing. ",1418926603,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5asnk76tj5m575vlprx3,task_description,duplicate
+VisualEditor broken for MobileFrontend,"Broken since 11 December. 
+
+As a logged in user with access to VE, attempt to edit any page.  See a spinner. 
+
+Javascript error shown in Chromium is ""TypeError: Illegal invocation TypeError: Illegal invocation ""
+
+",1418766721,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_description,resolved
+VisualEditor broken for MobileFrontend,verified the fix in en.wiki,1421362793,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,VE works in Mobile betalabs/test2. ,1420763452,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 182993 merged by Catrope:
+Update setupToolbar signature in mobile target
+
+[[https://gerrit.wikimedia.org/r/182993]]",1420560800,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 182993 had a related patch set uploaded (by Alex Monk):
+Update setupToolbar signature in mobile target
+
+[[https://gerrit.wikimedia.org/r/182993]]
+
+#patch-for-review",1420515801,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 181005 merged by MaxSem:
+Update VE and MF for T78710
+
+[[https://gerrit.wikimedia.org/r/181005]]",1418950655,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 181005 had a related patch set uploaded (by Jforrester):
+Update VE and MF for T78710
+
+[[https://gerrit.wikimedia.org/r/181005]]
+
+#patch-for-review",1418947774,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 180700 merged by jenkins-bot:
+Fix Ia6bf604c: Update another caller to ve.init.mw.Target
+
+[[https://gerrit.wikimedia.org/r/180700]]",1418947643,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 180701 merged by jenkins-bot:
+Followup Ia6bf604c, I431a9025: Update way VE target is constructed
+
+[[https://gerrit.wikimedia.org/r/180701]]",1418947639,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Parsoid was stalled to a version from October 28th :-(  Thanks to Krenair, Roan and Kartik we get it back to the latest version :-]",1418923498,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"(All the many different problems with Parsoid now seem to be fixed, thanks to @hashar)",1418911812,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"(Or at least, as well as the desktop version, which just returns a Parsoid error.)",1418902314,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,it should now work.,1418902160,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 180759 merged by jenkins-bot:
+Update setupToolbar signature in mobile target
+
+[[https://gerrit.wikimedia.org/r/180759]]",1418902072,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,(https://gerrit.wikimedia.org/r/180690 happened while Gerrit was down.),1418902069,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Change 180759 had a related patch set uploaded (by Alex Monk):
+Update setupToolbar signature in mobile target
+
+[[https://gerrit.wikimedia.org/r/180759]]
+
+#patch-for-review",1418901934,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Beta labs, sorry.",1418828869,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+VisualEditor broken for MobileFrontend,"Production or beta labs?
+",1418779266,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-3bmha7jwdg75jxh75rnj,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Have triage sessions. Regarding topic, stakeholders and key developers, this will focus on VisualEditor and be on a weekly basis, and volunteers are very welcome:
+
+See Task 86867 for ""VisualEditor Q3 Release Criteria"".
+See https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=645421507#VisualEditor_News_2015.E2.80.94.231 for announcement.
+
+See https://www.mediawiki.org/wiki/Bug_management/Meeting_preparations for more information
+
+First bugday with Phabricator instead of Bugzilla.
+
+Potentially related Team-Practices tasks:
+* https://phabricator.wikimedia.org/T88325 - ""Whole team chat with Damon RE burndown chart expectations""
+* https://phabricator.wikimedia.org/T88328 - ""Feasibility study for using Phab for burndown charts""
+* https://phabricator.wikimedia.org/T88365 - ""Burndown chart training and support - VE release support with Editing Team""
+",1418751245,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-lerurhal64ijhdssrwjz,task_description,resolved
+Have public bug day / triage sessions in February 2015 about VE,">>! In T78684#1049659, @Qgil wrote:
+> Should we consider setting the beginning of the sprint on Feb 1?
+
+According to James' answer in T89715: No. :)",1424354515,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"https://phabricator.wikimedia.org/project/sprint/view/1015/ With this fix and the Sprint upgrade, this page looks great now!
+
+@Jdforrester-WMF, why there is not visible progress during the whole month of January? Should we consider setting the beginning of the sprint on Feb 1?
+
+I'm being picky with this page because (as @damons explained at the MW Dev Summit) a burndown chart is a key communication tool, and I think we can push this page in all our VE sprint communications (also to editors etc). I guess people will wonder ""what happened in January?"", and this is why I'm asking.",1424352781,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,">>! In T78684#1046995, @Christopher wrote:
+> Also, I suspect that if for the  § VisualEditor Q3 Blockers project, if the ""Complete"" column is renamed to ""Done"" then all previous moves to this column will show on the burndown chart.
+
+[[ https://phabricator.wikimedia.org/project/sprint/view/1015/ | Done ]], thanks.",1424280700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Also, I suspect that if for the  § VisualEditor Q3 Blockers project, if the ""Complete"" column is renamed to ""Done"" then all previous moves to this column will show on the burndown chart.",1424280231,PHID-USER-lltif2drabccdkwhet7x,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"This is expected since the switch from Maniphest Status to Column Position.  To show progress in a Sprint, the normal workflow is to move the task to the ""Done"" column on the board.  This then deducts the points from ""Points Remaining"".  
+
+As mentioned in T88328, there are currently 4 static column ""type"" constants, ""Backlog"", ""Doing"", ""Review"" and ""Done"" that are recommended for the Sprint extension.   Teams are encouraged, but not required, to use these column names.  Future implementation may allow the possibility of user-defined names that map to these types, and perhaps additional column types.",1424279112,PHID-USER-lltif2drabccdkwhet7x,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Just a side question: is it normal that the ""remaining points"" line is not burning down at https://phabricator.wikimedia.org/project/sprint/view/1015/ ?
+
+CCing @christopher just in case.",1424278223,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"I'm not sure whether {T88198} is a pure blocker of this task, but there is a relationship.",1423474310,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Ok, I'm now convinced that we don't need to use an additional task for this process. Just keep in mind that not everybody will be able to follow at the same path, and some users might want to voice their opinions constructively in channels other than the phone call meeting. Let's be understanding and let's bring their relevant opinions to the triage meetings, as opposed to i.e. limiting ourselves to remind people about the official process.
+
+I'm pretty sure you were already planning to do this, but since we are running this type of process for the first time, I prefer to write this down somewhere.  :)",1423473152,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"I don't know. 
+In theory folks that unfortunately skipped communicating with product/project maintainers could already add the ""real"" Q3 project anyway without making sure that their addition is helpful from a ""let's get the stuff out"" maintainer prospective. 
+
+Folks could try to convince maintainers on IRC why some task is important enough before adding the task. 
+Or in the task itself. I'm not sure if that tag in addition to the comment itself would really help us (well, it might if noone reads all the incoming comments on all the VE tasks, to be honest). It might be yet another list that's as diverse as the list of all open tasks when it comes to importance; it might also be a way to get helpful feedback from folks that have good judgement what's important now - really hard for me to judge VE's community.",1423177662,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"@Jdforrester-WMF, when chatting with @aklapper about the VE weekly calls, I suggested the possibility of offering a temporary #VE-Q3-candidate tag of sorts to users willing to propose a specific task for the mega-sprint. The reason being that defending a proposal in English and in front of an unseen/unknown crowd during a synchronous phone call might deter some users. Even if a user plans to do so, being able to mark a task as candidate, explaining in the comments why, sounds like a good way to have a more productive meeting.
+
+What do you think?",1423035891,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Have public bug day / triage sessions in February 2015 about VE,"Next triage should be targetting VisualEditor I guess.
+
+Notes to myself: https://phabricator.wikimedia.org/tag/%C2%A7_visualeditor_q3/ seems to be the current quarter (Using 'Q3' and no year and no description was not totally obvious though). [[ https://phabricator.wikimedia.org/sprint/board/1015/ | Workboard ]]; [[ https://phabricator.wikimedia.org/sprint/view/1015/ | Burndown chart ]] (not too readable).
+
+Generally speaking, there are currently 1152 open tickets in the umbrella VE project (which is automatically added for any subproject tasks). Also see the [[ https://phabricator.wikimedia.org/maniphest/report/project/ | Distribution of priorities of open tickets ]] (search for ""VisualEditor"").",1422300136,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-lerurhal64ijhdssrwjz,task_subcomment,NA
+Combine API requests required to load VE,"When I load VE on [[en:Gosford]], the following API requests are made:
+
+- 3x action=query&prop=imageinfo
+- 1x action=query&prop=info
+- 1x action=visualeditor&paction=parse (also see {T87553})
+
+For a total of five API requests. Couldn't the VisualEditor API module expose an endpoint that combines this metadata into a single response?",1418709771,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-umbcx7pdcw56w7fx2jhf,task_description,resolved
+Combine API requests required to load VE,"Change 193026 had a related patch set uploaded (by Jforrester):
+[WIP] Factor out loading code into TargetLoader
+
+[[https://gerrit.wikimedia.org/r/193026]]
+",1425330751,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-umbcx7pdcw56w7fx2jhf,task_subcomment,NA
+Combine API requests required to load VE,Also it's worth mentioning that only the action=visualeditor request blocks loading VE (which is reasonable because it delivers the Parsoid HTML). The prop=info and imageinfo requests do not block loading.,1418727693,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-umbcx7pdcw56w7fx2jhf,task_subcomment,NA
+Combine API requests required to load VE,"This is a duplicate of several tickets, and should probably become a tracking ticket. I'll find them and make them all subtasks of this one.",1418725652,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-umbcx7pdcw56w7fx2jhf,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Clicking on ""Advanced"" search and changing the default namespaces to search and clicking search returns:
+
+``` lines=10
+""Exception thrown by mediawiki.special.search"" load.php:150
+""TypeError: this.form is null"" TypeError: this.form is null
+Stack trace:
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:2:185
+jQuery.event.dispatch@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:65:771
+jQuery.event.add/elemData.handle@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:60:313
+jQuery.event.trigger@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:64:460
+.trigger/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:75:425
+.each@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:5:216
+jQuery.prototype.each@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:2:215
+.trigger@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:75:404
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:2:130
+jQuery.Callbacks/fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:44:928
+jQuery.Callbacks/self.add@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:45:488
+jQuery.fn.ready@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:48:879
+jQuery.fn.init@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:41:68
+jQuery@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:1:637
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:1:84
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:1:1
+runScript@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:160:473
+execute/</checkCssHandles@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:160:958
+execute/</cssHandle/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:161:96
+jQuery.Callbacks/fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:44:928
+jQuery.Callbacks/self.fireWith@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:46:258
+jQuery.Callbacks/self.fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:46:301
+addEmbeddedCSS@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:155:871
+execute@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:161:552
+mw.loader</<.implement@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:168:145
+@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:42:29
+.globalEval/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:4:655
+.globalEval@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:4:621
+mw.loader</<.work@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:164:68
+request@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:162:258
+mw.loader</<.load@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:169:720
+@https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=mw.util.addPortletLink&fulltext=Search:248:1
+```",1418658101,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-zooes6fkunmcss2rmnar,task_description,resolved
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Indeed, the click event was getting unbound, because local site JS was rewriting some `.innerHTML` properties (which has the side-effect of killing everything that's not in initial HTML, like event handlers and inputted form field values). I removed one line: https://zh.wiktionary.org/w/index.php?title=MediaWiki:Common.js&diff=prev&oldid=4074338 and it seems to be working. If any other sites have the same problem, doing this will probably help them too.",1421434986,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,I believe its 100% js but I dunno - I just know I'm like a bull in a china shop with browser debugging.,1421422486,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Hmm, wondering who could investigate the JS part then... any idea?",1421420621,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Unassigning to myself as I can't figure it out and Javascript isn't my forte.  It looks like the click event is getting unbound from the button after its creation.  This returns undefined:
+$._data($('#mw-search-toggleall')[0], 'events')
+on the wikis that don't work.",1421420555,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,The all/none buttons still work on zhwikipedia but do not on zhwikibooks or zhwiktionary.....,1421418940,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Also - its clicking the buttons that is broken.  Clicking on the check boxes still seems to work.,1421418747,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Reopened - it is indeed broken on zhwiktionary but not enwiktionary.  No idea why yet.,1421418691,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#981797, @Aklapper wrote:
+> @Liuxinyu970226: Can you provide a link / steps to reproduce please?
+
+Try ""全选 (all)"" & ""全不选 (none)"" at:
+* https://zh.wiktionary.org/w/index.php?title=Special:搜索&search=asdfg&fulltext=搜索&profile=advanced
+* https://zh.wikibooks.org/w/index.php?title=Special:搜索&search=asdfg&fulltext=搜索&profile=advanced",1421416049,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,@Liuxinyu970226: Can you provide a link / steps to reproduce please?,1421415812,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Can't work again on zhwiktionary and zhwikibooks, who can help them.",1421371291,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Can't work again on zhwiktionary and zhwikibooks,1421371261,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#931954, @Liuxinyu970226 wrote:
+> @Nikerabbit: Keeps on translatewiki, u know.
+
+OK now tsw fixed too.",1419687072,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"@Nikerabbit: Keeps on translatewiki, u know.",1418894001,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Verified on mw.org,1418832951,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Change 180319 merged by jenkins-bot:
+Move advanced search inputs back into the form
+
+[[https://gerrit.wikimedia.org/r/180319]]",1418832552,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"
+
+>>! In T78553#852344, @Krinkle wrote:
+> This isn't just causing a user scripts or extensions to throw an exception due to elements not existing in javascript land. The core feature itself is also plain broken.
+> 
+> 1. https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=formsGadgetConfig&fulltext=Search
+> 2. Tick/untick any namespace checkboxes.
+> 3. Press ""Search""
+> 
+> Expected: Search results now include different results and namespace selection is there as the user submitted it
+> 
+> Actual: The checkboxes not being part of the `<form>` means they're not submitted and completely ignored by the server. The advanced search is completely non-functional.
+
+Thanks for making that clear.  I didn't do a good job of documenting how broken it was.  I took a stab at it in https://phabricator.wikimedia.org/T78553#849773 but wasn't super clear.  The change to fix it is scheduled to by SWATed tonight.",1418782122,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"This isn't just causing a user scripts or extensions to throw an exception due to elements not existing in javascript land. The core feature itself is also plain broken.
+
+1. https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=formsGadgetConfig&fulltext=Search
+2. Tick/untick any namespace checkboxes.
+3. Press ""Search""
+
+Expected: Search results now include different results and namespace selection is there as the user submitted it
+
+Actual: The checkboxes not being part of the `<form>` means they're not submitted and completely ignored by the server. The advanced search is completely non-functional.",1418781672,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"This isn't just causing a user script exception due to elements not existing. The core feature is also plain broken.
+
+1. https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=formsGadgetConfig&fulltext=Search
+2. Tick/untick any namespace checkboxes.
+3. Press ""Search""
+
+Expected: Search results now include different results and namespace selection is there as the user submitted it
+
+Actual: The checkboxes not being part of the `<form>` means they're not submitted and completely ignored by the server. The advanced search is completely non-functional.",1418781623,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Evening swat deployment scheduled: https://wikitech.wikimedia.org/w/index.php?title=Deployments&oldid=138343,1418768313,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Change 180319 had a related patch set uploaded (by Robmoen):
+Move advanced search inputs back into the form
+
+[[https://gerrit.wikimedia.org/r/180319]]
+
+#patch-for-review",1418767649,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Change 180237 merged by jenkins-bot:
+Move advanced search inputs back into the form
+
+[[https://gerrit.wikimedia.org/r/180237]]",1418762135,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,,1418758615,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,,1418758578,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"Change 180237 had a related patch set uploaded (by Robmoen):
+Move advanced search inputs back into the form
+
+[[https://gerrit.wikimedia.org/r/180237]]
+
+#patch-for-review",1418758535,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Awesome!  Can you link it here?  We can certainly SWAT it tomorrow morning or this afternoon if we can get it reviewed ASAP.,1418758475,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#851447, @Manybubbles wrote:
+> Do they have to be logged in?  Not that it really matters.  Is it something you can fix in an hour or two?  If so we should just fix it I think
+
+Agreed.  I have identified a fix.",1418757869,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Do they have to be logged in?  Not that it really matters.  Is it something you can fix in an hour or two?  If so we should just fix it I think,1418757680,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#850699, @Manybubbles wrote:
+> Reassigning to rmoen as its very likely related to Ic6ec29817ab7deadc6bc7125f8b4cd16686baa04.  I don't want to just revert his work because it looks like it has some value.  If he isn't able to pick this up in a few hours I will just revert it so we can have advanced search back.
+
+The breaking change should be reverted as turns out it breaks the entire advanced search form for logged in users.  However, I have an easy fix for all of this.",1418757817,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,">>! In T78553#850699, @Manybubbles wrote:
+> Reassigning to rmoen as its very likely related to Ic6ec29817ab7deadc6bc7125f8b4cd16686baa04.  I don't want to just revert his work because it looks like it has some value.  If he isn't able to pick this up in a few hours I will just revert it so we can have advanced search back.
+
+The breaking change should be reverted as turns out it breaks the entire advanced search form for logged in users.  ",1418757629,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,Reassigning to rmoen as its very likely related to Ic6ec29817ab7deadc6bc7125f8b4cd16686baa04.  I don't want to just revert his work because it looks like it has some value.  If he isn't able to pick this up in a few hours I will just revert it so we can have advanced search back.,1418744783,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,I'm going to grab this.  I'm not particularly well qualified for it so if a Javascript expert wants it feel free to trump me.  I just think it needs looking at sooner rather than later.,1418743413,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"NOTE: In case it matters; excerpt from the recently merged duplicate T78636
+
+**Confirmed** ... reproduced behavior on both __www.MediaWiki.org__ and __test2.wikipedia.org__ `[1.25wmf12 (1d22bb3)]` at the moment.
+
+I could not reproduce this behavior (selecting //none// or //all// executes as expected) on __en.wikipedia.org__ or __en.wikisource.org__ `[1.25wmf11 (038c7a8)]` however.",1418740716,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"> The check all/none buttons do nothing. If I check or uncheck any of the namespace check boxes and then hit search to refine my search, the checkboxes revert to default and my results do not change.
+
+I see that too.",1418696238,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"There are no specific steps, just loading the page brings up that error.  Okay, I refresh the page with my console open and my Network, JS, and Security logs checked and I get:
+
+``` lines=15
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 580ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 470ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 528ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 522ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 561ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 634ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 675ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 683ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 761ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 752ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 889ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 787ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 1840ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 861ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 892ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 2545ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 134ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 281ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 255ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 293ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 377ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 258ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.lib.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralAuth/modules/ext.centralauth.centralautologin.clearcookie.js [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 102ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 124ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/lib/ve/src/ve.js [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/lib/ve/src/ve.track.js [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.byteLength.js [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.client.js [HTTP/1.1 200 OK 176ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery/jquery.cookie.js [HTTP/1.1 200 OK 149ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.css [HTTP/1.1 200 OK 148ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.js [HTTP/1.1 200 OK 212ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.mwExtension.js [HTTP/1.1 200 OK 147ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.accessKeyLabel.js [HTTP/1.1 200 OK 156ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.tabIndex.js [HTTP/1.1 200 OK 203ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery/jquery.ba-throttle-debounce.js [HTTP/1.1 200 OK 265ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 611ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery.tipsy/jquery.tipsy.js [HTTP/1.1 200 OK 283ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.notify.js [HTTP/1.1 200 OK 226ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.util.js [HTTP/1.1 200 OK 314ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.js [HTTP/1.1 200 OK 273ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.Title.js [HTTP/1.1 200 OK 348ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.Uri.js [HTTP/1.1 200 OK 388ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/EventLogging/modules/ext.eventLogging.core.js [HTTP/1.1 200 OK 354ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.css [HTTP/1.1 200 OK 349ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.init.js [HTTP/1.1 200 OK 383ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.init.js [HTTP/1.1 200 OK 439ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 457ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.legacy/wikibits.js [HTTP/1.1 200 OK 426ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.legacy/ajax.js [HTTP/1.1 200 OK 444ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 502ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 522ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.libs/CLDRPluralRuleParser.js [HTTP/1.1 200 OK 496ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.cldr.js [HTTP/1.1 200 OK 506ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.js [HTTP/1.1 200 OK 511ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.numbers.js [HTTP/1.1 200 OK 587ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.fallback.js [HTTP/1.1 200 OK 583ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.jqueryMsg.js [HTTP/1.1 200 OK 733ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.startup.js [HTTP/1.1 200 OK 586ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 615ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/collapsibleTabs.js [HTTP/1.1 200 OK 648ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/vector.js [HTTP/1.1 200 OK 657ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 712ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.user.js [HTTP/1.1 200 OK 657ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VectorBeta/resources/compactPersonalBar/trackClick.js [HTTP/1.1 200 OK 668ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VectorBeta/resources/compactPersonalBar/defaultTracking.js [HTTP/1.1 200 OK 741ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/modules/ve-mw/init/styles/ve.init.mw.ViewPageTarget.init.css [HTTP/1.1 200 OK 741ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js [HTTP/1.1 200 OK 873ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.preferences.js [HTTP/1.1 200 OK 744ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.webfonts.js [HTTP/1.1 200 OK 767ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.interface.js [HTTP/1.1 200 OK 795ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/120px-Foo.jpg [HTTP/1.1 200 OK 584ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Foo.svg/120px-Foo.svg.png [HTTP/1.1 200 OK 583ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/f/f5/Foo_2.png/120px-Foo_2.png [HTTP/1.1 200 OK 665ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/43/Foo_1.jpg/120px-Foo_1.jpg [HTTP/1.1 200 OK 751ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/8/8e/Mei_Foo_Sun_Chuen_Map.svg/120px-Mei_Foo_Sun_Chuen_Map.svg.png [HTTP/1.1 200 OK 662ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/48/Foo_Fighters_acoustic.jpg/120px-Foo_Fighters_acoustic.jpg [HTTP/1.1 200 OK 663ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/49/Foo_Fighters.jpg/120px-Foo_Fighters.jpg [HTTP/1.1 200 OK 932ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/Foo_1.png/120px-Foo_1.png [HTTP/1.1 200 OK 895ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/6/6b/Jane_McGonigal%2C_Foo_Camp.jpg/102px-Jane_McGonigal%2C_Foo_Camp.jpg [HTTP/1.1 200 OK 888ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/d/d8/Foo_Fighters_%28Logo%29.png/120px-Foo_Fighters_%28Logo%29.png [HTTP/1.1 200 OK 890ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/e/e3/Jane_McGonigal_Foo_Camp_2008.jpg/120px-Jane_McGonigal_Foo_Camp_2008.jpg [HTTP/1.1 200 OK 902ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/5/56/Mei_Foo_exit_A.jpeg/120px-Mei_Foo_exit_A.jpeg [HTTP/1.1 200 OK 884ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/e/e8/The_view_of_Mei_Foo_Skatepark_From_Entrance.jpeg/120px-The_view_of_Mei_Foo_Skatepark_From_Entrance.jpeg [HTTP/1.1 200 OK 442ms]
+GET https://bits.wikimedia.org/images/wikimedia-button.png [HTTP/1.1 200 OK 244ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/assets/poweredby_mediawiki_88x31.png [HTTP/1.1 200 OK 564ms]
+GET https://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png [HTTP/1.1 200 OK 544ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 242ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 98ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 1657ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 484ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 537ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 434ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.js [HTTP/1.1 200 OK 318ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/css/jquery.ime.css [HTTP/1.1 200 OK 316ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/jquery.ime.js [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.data.js [HTTP/1.1 200 OK 391ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.grid.css [HTTP/1.1 200 OK 372ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.messagestore.js [HTTP/1.1 200 OK 722ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.data.utils.js [HTTP/1.1 200 OK 727ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.core.css [HTTP/1.1 200 OK 645ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.theme.css [HTTP/1.1 200 OK 651ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.core.js [HTTP/1.1 200 OK 648ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.position.js [HTTP/1.1 200 OK 716ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.widget.js [HTTP/1.1 200 OK 721ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.parser.js [HTTP/1.1 200 OK 174ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.button.css [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.button.js [HTTP/1.1 200 OK 172ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.mouse.js [HTTP/1.1 200 OK 108ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/EventLogging/modules/ext.eventLogging.subscriber.js [HTTP/1.1 200 OK 59ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 113ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 102ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 117ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 104ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 232ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 168ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 120ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 173ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 219ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 213ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.sendBeacon.js [HTTP/1.1 200 OK 164ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.pt.css [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.deprecate.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.statsd.js [HTTP/1.1 200 OK 91ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.checkboxShiftClick.js [HTTP/1.1 200 OK 90ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.getAttrs.js [HTTP/1.1 200 OK 94ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.hidpi.js [HTTP/1.1 200 OK 117ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.highlightText.js [HTTP/1.1 200 OK 123ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.makeCollapsible.css [HTTP/1.1 200 OK 136ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.makeCollapsible.js [HTTP/1.1 200 OK 199ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.mw-jump.js [HTTP/1.1 200 OK 147ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.placeholder.js [HTTP/1.1 200 OK 149ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.action/mediawiki.action.view.rightClickEdit.js [HTTP/1.1 200 OK 167ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.watch.js [HTTP/1.1 200 OK 152ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.special/mediawiki.special.search.css [HTTP/1.1 200 OK 173ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.special/mediawiki.special.search.js [HTTP/1.1 200 OK 180ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 275ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 237ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 2994ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 250ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 307ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 651ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 414ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.emitter.js [HTTP/1.1 200 OK 269ms]
+GET https://commons.wikimedia.org/w/index.php [HTTP/1.1 200 OK 1076ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/images/icon-language.svg [HTTP/1.1 200 OK 655ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 931ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.draggable.js [HTTP/1.1 200 OK 873ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.resizable.css [HTTP/1.1 200 OK 338ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.resizable.js [HTTP/1.1 200 OK 867ms]
+TypeError: this.form is null mediawiki.special.search.js:53
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.hidpi.js [HTTP/1.1 200 OK 89ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.suggestions.css [HTTP/1.1 200 OK 96ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.suggestions.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.ready.js [HTTP/1.1 200 OK 86ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.watch.ajax.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.eventlogger.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.language.js [HTTP/1.1 200 OK 442ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/NavigationTiming/modules/ext.navigationTiming.js [HTTP/1.1 200 OK 432ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.searchSuggest.css [HTTP/1.1 200 OK 59ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.searchSuggest.js [HTTP/1.1 200 OK 60ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 145ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.dialog.css [HTTP/1.1 200 OK 69ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.dialog.js [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/NavigationTiming/modules/ext.navigationTiming.HHVM.js [HTTP/1.1 200 OK 63ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.i18n.js [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.css [HTTP/1.1 200 OK 63ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.lcd.css [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.core.js [HTTP/1.1 200 OK 213ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 138ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 112ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.lcd.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 96ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/base/ext.echo.base.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.languagefilter.js [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/overlay/ext.echo.overlay.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.regionfilter.js [HTTP/1.1 200 OK 61ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/overlay/ext.echo.overlay.init.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.mediawiki.js [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.ime.js [HTTP/1.1 200 OK 60ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 140ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/images/ime-active.svg [HTTP/1.1 200 OK 202ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/images/tick.svg [HTTP/1.1 200 OK 200ms]
+GET https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 210ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.buttons.css [HTTP/1.1 200 OK 60ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.languagesettings.css [HTTP/1.1 200 OK 61ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.languagesettings.js [HTTP/1.1 200 OK 64ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.parse.js [HTTP/1.1 200 OK 62ms]
+POST https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 2427ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.displaysettings.css [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.displaysettings.js [HTTP/1.1 200 OK 127ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.inputsettings.css [HTTP/1.1 200 OK 76ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.inputsettings.js [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/images/close.svg [HTTP/1.1 200 OK 298ms]
+```
+
+The check all/none buttons do nothing.  If I check or uncheck any of the namespace check boxes and then hit search to refine my search, the checkboxes revert to default and my results do not change.",1418671562,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"There are no specific steps, just loading the page brings up that error.  Okay, I refresh the page with my console open and my Network, JS, and Security logs checked and I get:
+
+```
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 580ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 470ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 528ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 522ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 561ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 634ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 675ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 683ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 761ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 752ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 889ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 787ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 1840ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 861ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 892ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 2545ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 134ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 281ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 255ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 293ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 377ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 258ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.lib.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralAuth/modules/ext.centralauth.centralautologin.clearcookie.js [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 102ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 124ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/lib/ve/src/ve.js [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/lib/ve/src/ve.track.js [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.byteLength.js [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.client.js [HTTP/1.1 200 OK 176ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery/jquery.cookie.js [HTTP/1.1 200 OK 149ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.css [HTTP/1.1 200 OK 148ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/CentralNotice/modules/ext.centralNotice.bannerController/bannerController.js [HTTP/1.1 200 OK 212ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.mwExtension.js [HTTP/1.1 200 OK 147ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.accessKeyLabel.js [HTTP/1.1 200 OK 156ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.tabIndex.js [HTTP/1.1 200 OK 203ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery/jquery.ba-throttle-debounce.js [HTTP/1.1 200 OK 265ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 611ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery.tipsy/jquery.tipsy.js [HTTP/1.1 200 OK 283ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.notify.js [HTTP/1.1 200 OK 226ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.util.js [HTTP/1.1 200 OK 314ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.js [HTTP/1.1 200 OK 273ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.Title.js [HTTP/1.1 200 OK 348ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.Uri.js [HTTP/1.1 200 OK 388ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/EventLogging/modules/ext.eventLogging.core.js [HTTP/1.1 200 OK 354ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.css [HTTP/1.1 200 OK 349ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.init.js [HTTP/1.1 200 OK 383ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.init.js [HTTP/1.1 200 OK 439ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 457ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.legacy/wikibits.js [HTTP/1.1 200 OK 426ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.legacy/ajax.js [HTTP/1.1 200 OK 444ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 502ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 522ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.libs/CLDRPluralRuleParser.js [HTTP/1.1 200 OK 496ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.cldr.js [HTTP/1.1 200 OK 506ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.js [HTTP/1.1 200 OK 511ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.numbers.js [HTTP/1.1 200 OK 587ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.language/mediawiki.language.fallback.js [HTTP/1.1 200 OK 583ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.jqueryMsg.js [HTTP/1.1 200 OK 733ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.startup.js [HTTP/1.1 200 OK 586ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 615ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/collapsibleTabs.js [HTTP/1.1 200 OK 648ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/vector.js [HTTP/1.1 200 OK 657ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 712ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.user.js [HTTP/1.1 200 OK 657ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VectorBeta/resources/compactPersonalBar/trackClick.js [HTTP/1.1 200 OK 668ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VectorBeta/resources/compactPersonalBar/defaultTracking.js [HTTP/1.1 200 OK 741ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/modules/ve-mw/init/styles/ve.init.mw.ViewPageTarget.init.css [HTTP/1.1 200 OK 741ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js [HTTP/1.1 200 OK 873ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.preferences.js [HTTP/1.1 200 OK 744ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.webfonts.js [HTTP/1.1 200 OK 767ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.interface.js [HTTP/1.1 200 OK 795ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/120px-Foo.jpg [HTTP/1.1 200 OK 584ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Foo.svg/120px-Foo.svg.png [HTTP/1.1 200 OK 583ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/f/f5/Foo_2.png/120px-Foo_2.png [HTTP/1.1 200 OK 665ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/43/Foo_1.jpg/120px-Foo_1.jpg [HTTP/1.1 200 OK 751ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/8/8e/Mei_Foo_Sun_Chuen_Map.svg/120px-Mei_Foo_Sun_Chuen_Map.svg.png [HTTP/1.1 200 OK 662ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/48/Foo_Fighters_acoustic.jpg/120px-Foo_Fighters_acoustic.jpg [HTTP/1.1 200 OK 663ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/4/49/Foo_Fighters.jpg/120px-Foo_Fighters.jpg [HTTP/1.1 200 OK 932ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/Foo_1.png/120px-Foo_1.png [HTTP/1.1 200 OK 895ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/6/6b/Jane_McGonigal%2C_Foo_Camp.jpg/102px-Jane_McGonigal%2C_Foo_Camp.jpg [HTTP/1.1 200 OK 888ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/d/d8/Foo_Fighters_%28Logo%29.png/120px-Foo_Fighters_%28Logo%29.png [HTTP/1.1 200 OK 890ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/e/e3/Jane_McGonigal_Foo_Camp_2008.jpg/120px-Jane_McGonigal_Foo_Camp_2008.jpg [HTTP/1.1 200 OK 902ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/5/56/Mei_Foo_exit_A.jpeg/120px-Mei_Foo_exit_A.jpeg [HTTP/1.1 200 OK 884ms]
+GET https://upload.wikimedia.org/wikipedia/commons/thumb/e/e8/The_view_of_Mei_Foo_Skatepark_From_Entrance.jpeg/120px-The_view_of_Mei_Foo_Skatepark_From_Entrance.jpeg [HTTP/1.1 200 OK 442ms]
+GET https://bits.wikimedia.org/images/wikimedia-button.png [HTTP/1.1 200 OK 244ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/assets/poweredby_mediawiki_88x31.png [HTTP/1.1 200 OK 564ms]
+GET https://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png [HTTP/1.1 200 OK 544ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 242ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 98ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 1657ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 484ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 537ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 434ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.js [HTTP/1.1 200 OK 318ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/css/jquery.ime.css [HTTP/1.1 200 OK 316ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/jquery.ime.js [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.data.js [HTTP/1.1 200 OK 391ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.grid.css [HTTP/1.1 200 OK 372ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.messagestore.js [HTTP/1.1 200 OK 722ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.data.utils.js [HTTP/1.1 200 OK 727ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.core.css [HTTP/1.1 200 OK 645ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.theme.css [HTTP/1.1 200 OK 651ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.core.js [HTTP/1.1 200 OK 648ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.position.js [HTTP/1.1 200 OK 716ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.widget.js [HTTP/1.1 200 OK 721ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 635ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.parser.js [HTTP/1.1 200 OK 174ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.button.css [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.button.js [HTTP/1.1 200 OK 172ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.mouse.js [HTTP/1.1 200 OK 108ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/EventLogging/modules/ext.eventLogging.subscriber.js [HTTP/1.1 200 OK 59ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 113ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 102ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 117ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 104ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 232ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 168ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 120ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 173ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 219ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 213ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.sendBeacon.js [HTTP/1.1 200 OK 164ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.pt.css [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.deprecate.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/WikimediaEvents/modules/ext.wikimediaEvents.statsd.js [HTTP/1.1 200 OK 91ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.checkboxShiftClick.js [HTTP/1.1 200 OK 90ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.getAttrs.js [HTTP/1.1 200 OK 94ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.hidpi.js [HTTP/1.1 200 OK 117ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.highlightText.js [HTTP/1.1 200 OK 123ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.makeCollapsible.css [HTTP/1.1 200 OK 136ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.makeCollapsible.js [HTTP/1.1 200 OK 199ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.mw-jump.js [HTTP/1.1 200 OK 147ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.placeholder.js [HTTP/1.1 200 OK 149ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.action/mediawiki.action.view.rightClickEdit.js [HTTP/1.1 200 OK 167ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.watch.js [HTTP/1.1 200 OK 152ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.special/mediawiki.special.search.css [HTTP/1.1 200 OK 173ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.special/mediawiki.special.search.js [HTTP/1.1 200 OK 180ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 275ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 237ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 2994ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 250ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 307ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 651ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 414ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.emitter.js [HTTP/1.1 200 OK 269ms]
+GET https://commons.wikimedia.org/w/index.php [HTTP/1.1 200 OK 1076ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/images/icon-language.svg [HTTP/1.1 200 OK 655ms]
+GET https://en.wikipedia.org/w/index.php [HTTP/1.1 200 OK 931ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.draggable.js [HTTP/1.1 200 OK 873ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.resizable.css [HTTP/1.1 200 OK 338ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.resizable.js [HTTP/1.1 200 OK 867ms]
+TypeError: this.form is null mediawiki.special.search.js:53
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.hidpi.js [HTTP/1.1 200 OK 89ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.suggestions.css [HTTP/1.1 200 OK 96ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/jquery/jquery.suggestions.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.ready.js [HTTP/1.1 200 OK 86ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.page/mediawiki.page.watch.ajax.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.eventlogger.js [HTTP/1.1 200 OK 569ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.i18n/jquery.i18n.language.js [HTTP/1.1 200 OK 442ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/NavigationTiming/modules/ext.navigationTiming.js [HTTP/1.1 200 OK 432ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.searchSuggest.css [HTTP/1.1 200 OK 59ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki/mediawiki.searchSuggest.js [HTTP/1.1 200 OK 60ms]
+GET https://www.mediawiki.org/w/index.php [HTTP/1.1 200 OK 145ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/skins/Vector/skinStyles/jquery.ui/jquery.ui.dialog.css [HTTP/1.1 200 OK 69ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/lib/jquery.ui/jquery.ui.dialog.js [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/NavigationTiming/modules/ext.navigationTiming.HHVM.js [HTTP/1.1 200 OK 63ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.i18n.js [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.css [HTTP/1.1 200 OK 63ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/css/jquery.uls.lcd.css [HTTP/1.1 200 OK 65ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.core.js [HTTP/1.1 200 OK 213ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 138ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 112ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 153ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.lcd.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 96ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/base/ext.echo.base.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.languagefilter.js [HTTP/1.1 200 OK 114ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/overlay/ext.echo.overlay.js [HTTP/1.1 200 OK 115ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/src/jquery.uls.regionfilter.js [HTTP/1.1 200 OK 61ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/Echo/modules/overlay/ext.echo.overlay.init.js [HTTP/1.1 200 OK 62ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.mediawiki.js [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.ime.js [HTTP/1.1 200 OK 60ms]
+GET https://bits.wikimedia.org/www.mediawiki.org/load.php [HTTP/1.1 200 OK 140ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/images/ime-active.svg [HTTP/1.1 200 OK 202ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.ime/images/tick.svg [HTTP/1.1 200 OK 200ms]
+GET https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 210ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.buttons.css [HTTP/1.1 200 OK 60ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.languagesettings.css [HTTP/1.1 200 OK 61ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.languagesettings.js [HTTP/1.1 200 OK 64ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/resources/src/mediawiki.api/mediawiki.api.parse.js [HTTP/1.1 200 OK 62ms]
+POST https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 2427ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.displaysettings.css [HTTP/1.1 200 OK 58ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.displaysettings.js [HTTP/1.1 200 OK 127ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/css/ext.uls.inputsettings.css [HTTP/1.1 200 OK 76ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/resources/js/ext.uls.inputsettings.js [HTTP/1.1 200 OK 132ms]
+GET https://bits.wikimedia.org/static-1.25wmf12/extensions/UniversalLanguageSelector/lib/jquery.uls/images/close.svg [HTTP/1.1 200 OK 298ms]
+```
+
+The check all/none buttons do nothing.  If I check or uncheck any of the namespace check boxes and then hit search to refine my search, the checkboxes revert to default and my results do not change.",1418670812,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"I simply cannot get see any stacktrace rendered in my browser - I get 1076 results for your link and nothing that makes it look like something really important is broken here. Could you elaborate?
+
+I can confirm that there's error output in the browser console, triggered by this line:
+  this.form.method = this.checked ? 'post' : 'get';
+from https://git.wikimedia.org/history/mediawiki%2Fcore.git/HEAD/resources%2Fsrc%2Fmediawiki.special%2Fmediawiki.special.search.js which hasn't seen recent changes.",1418669421,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+
+  lang= javascript, lines=10
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418671396,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+lang= javascript, lines=10
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418671347,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+lines=10
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+...
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418671289,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+lines=10
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418671261,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Foo&fulltext=Search&debug=true
+
+TypeError: this.form is null mediawiki.special.search.js:53
+
+		// Change the header search links to what user entered (line 34)
+		$headerLinks = $( '.search-types a' );
+		$( '#searchText, #powerSearchText' ).change( function () {
+			var searchterm = $( this ).val();
+			$headerLinks.each( function () {
+				var parts = $( this ).attr( 'href' ).split( 'search=' ),
+					lastpart = '',
+					prefix = 'search=';
+				if ( parts.length > 1 && parts[1].indexOf( '&' ) !== -1 ) {
+					lastpart = parts[1].slice( parts[1].indexOf( '&' ) );
+				} else {
+					prefix = '&search=';
+				}
+				this.href = parts[0] + prefix + encodeURIComponent( searchterm ) + lastpart;
+			} );
+		} ).trigger( 'change' );
+
+		// When saving settings, use the proper request method (POST instead of GET).
+		$( '#mw-search-powersearch-remember' ).change( function () {
+			this.form.method = this.checked ? 'post' : 'get';
+		} ).trigger( 'change' );
+
+When I view source of the page:
+    mw.user.options.set( {
+        ""ccmeonemails"": ""1"",
+        ""date"": ""mdy"",
+        ""editsectiononrightclick"": ""1"",
+        ""enotifwatchlistpages"": ""1"",
+        ""extendwatchlist"": ""1"",
+        ""gender"": ""male"",
+        ""imagesize"": ""3"",
+        ""math"": ""6"",
+        ""previewonfirst"": ""1"",
+        ""rcdays"": ""30"",
+        ""rclimit"": ""500"",
+        ""showhiddencats"": ""1"",
+        ""stubthreshold"": ""100"",
+        ""thumbsize"": ""6"",
+        ""uselivepreview"": ""1"",
+        ""usenewrc"": ""1"",
+        ""watchlistdays"": ""30"",
+        ""wllimit"": ""1000"",
+        ""lqtnotifytalk"": ""1"",
+        ""visualeditor-betatempdisable"": ""1"",
+        ""translate-editlangs"": ""en"",
+        ""echo-subscriptions-email-edit-user-talk"": 1,
+        ""echo-subscriptions-web-article-linked"": ""1"",
+        ""echo-subscriptions-email-mention"": ""1"",
+        ""uls-preferences"": ""{\""ime\"":{\""language\"":\""en\"",\""previousLanguages\"":[\""en\""],\""previousInputMethods\"":[],\""imes\"":{\""en\"":\""system\""}}}"",
+        ""searchNs1"": ""1"",
+        ""searchNs2"": ""1"",
+        ""searchNs3"": ""1"",
+        ""searchNs4"": ""1"",
+        ""searchNs5"": ""1"",
+        ""searchNs6"": ""1"",
+        ""searchNs7"": ""1"",
+        ""searchNs8"": ""1"",
+        ""searchNs9"": ""1"",
+        ""searchNs10"": ""1"",
+        ""searchNs11"": ""1"",
+        ""searchNs13"": ""1"",
+        ""searchNs90"": ""1"",
+        ""searchNs91"": ""1"",
+        ""searchNs101"": ""1"",
+        ""searchNs103"": ""1"",
+        ""betafeatures-vector-compact-personal-bar"": ""0"",
+        ""gadget-DotsSyntaxHighlighter"": ""1"",
+        ""gadget-HotCat"": ""1"",
+        ""gadget-Navigation_popups"": ""1"",
+        ""gadget-TabOverride"": ""1"",
+        ""gadget-UTCLiveClock"": ""1"",
+        ""gadget-ajaxrecentchanges"": ""1"",
+        ""gadget-contribsrange"": ""1"",
+        ""gadget-externalsearch"": ""1"",
+        ""gadget-oldeditor"": ""1"",
+        ""gadget-templatedata"": ""1"",
+        ""popups"": ""0"",
+        ""timecorrection"": ""ZoneInfo|-300|America/New_York"",
+        ""uls-compact-links"": ""0"",
+        ""watchlisttoken"": ""/* (redacted) */""
+    } );
+
+and
+    mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax"",""ext.gadget.site"",""ext.centralauth.centralautologin.clearcookie"",""skins.vector.compactPersonalBar.defaultTracking"",""ext.visualEditor.viewPageTarget.init"",""ext.uls.init"",""ext.uls.interface"",""ext.centralNotice.bannerController"",""skins.vector.js""]);",1418665273,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+Special:Search on mw.org throwing an error - Advanced search checkboxes broken,"> Clicking on ""Advanced"" search and changing the default namespaces to search and clicking search returns:
+
+Please provide //exact// steps to reproduce. I cannot reproduce the problem using https://www.mediawiki.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced but the steps are simply too vague. Using &debug=true is also very welcome.",1418663601,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zooes6fkunmcss2rmnar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors","Recently, there has been a rapid increase in errors like:
+
+```
+Sorry! This site is experiencing technical difficulties.
+
+Try waiting a few minutes and reloading.
+
+(Cannot contact the database server: Too many connections (208.80.154.18))
+```
+
+This happens not only when I open dozens of wikitech pages, but also when I reload single pages afterwards.",1418544923,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-6welbf6ni6cfb2mlnvar,task_description,resolved
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors","This has stopped happening now that wikitech is on silver, safely away from puppet's vandalism.",1424571360,PHID-USER-22bsa5u75jz3ci3wnplu,False,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors","… and they come from the Puppet extension, so that's fine.  I think the problem lies in the interface MediaWiki/MySQL.  7 hits/11 s shouldn't bring a wiki down; perhaps some connection pool not set up or something like that?
+
+(@yuvipanda: BTW, totally forgot: Congrats! :-))",1418642169,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors",All the Hiera hits are from the puppetmaster,1418631203,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors",Most likely the issue here is that the main cluster robots.txt is more tolerant of crawlers than wikitech can afford to be.  I'll investigate how to make a site-local robots.txt (or bug bryan to do so).,1418608223,PHID-USER-22bsa5u75jz3ci3wnplu,False,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+"Many ""(Cannot contact the database server: Too many connections (208.80.154.18))"" errors","Looks like we're getting crawled.
+
+208.80.154.18 - - [15/Dec/2014:01:40:57 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=ids&titles=Hiera:Video HTTP/1.1"" 200 5064 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+208.80.154.18 - - [15/Dec/2014:01:40:57 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=content&titles=Hiera:Video HTTP/1.1"" 200 666 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+208.80.154.18 - - [15/Dec/2014:01:41:00 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=ids&titles=Hiera:Oxygenguide HTTP/1.1"" 200 5064 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+208.80.154.18 - - [15/Dec/2014:01:41:00 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=content&titles=Hiera:Oxygenguide HTTP/1.1"" 200 666 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+68.180.228.125 - - [15/Dec/2014:01:41:01 +0000] ""GET /wiki/Special:PrefixIndex/User:OccultZone/ HTTP/1.1"" 500 5485 ""-"" ""Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)""
+208.80.154.14 - - [15/Dec/2014:01:41:10 +0000] ""GET / HTTP/1.1"" 302 457 ""-"" ""check_http/v1.4.15 (nagios-plugins 1.4.15)""
+208.80.154.18 - - [15/Dec/2014:01:41:10 +0000] ""GET /w/api.php?action=query&prop=revisions&format=json&rvprop=ids&titles=Hiera:Visualeditor HTTP/1.1"" 200 5064 ""-"" ""HieraMwCache/0.1 (/, ruby 1.8.7 (2011-06-30) [x86_64-linux])""
+2",1418607697,PHID-USER-22bsa5u75jz3ci3wnplu,False,PHID-TASK-6welbf6ni6cfb2mlnvar,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Turns out Flow is a great tool for newbies compared to free-form wikitext. Well, at least until the point where they need to create a link or they want to add some basic formatting. Especially if the newbies are defaulting to VisualEditor, they might have difficulties posting anything other than plaintext and full URLs.
+
+{F21334 size=full}
+
+Trimming the selection was discussed, and discovered to be both subjectively-desirable and technically-complicated. Newcomers will eventually have an alternative VE interface, to satisfy the requests for a less complicated set of buttons. So, please implement the full/default WikiEditor toolbar.
+
+Further notes at {T90052}
+
+See also: {T93243}",1418336289,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-monj46bisauzpolgauzi,task_description,resolved
+Wikitext editing toolbar for Flow,"Solved by {T155861}. 
+Concerning advanced toolbar, that's now covered by {T93243} while both editors are based on the same toolbar.",1523032235,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,,1505324640,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,,1505305235,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I'm retitling this task, due to the recent work on the VE toolbar in {T93243}",1464882800,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,Some thoughts raised during Collaboration team's offsite concerning VE toolbar for Flow have been added to {T93243}.,1464134744,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,[[https://fr.wikipedia.org/wiki/Sujet:T32v2yjule0ssfq7 | New feedback concerning the lack of toolbars]]. I hope we will be able to address that problem soon.,1462181068,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1747890, @Pginer-WMF wrote:
+>> Create a minima a way to personalize VE and wikitext toolbars with a gadget would be a good idea.
+> 
+> Adding media is a reasonable usecase for conversations. We consider providing support for it from the beginning but the decision was postponed until VE would be able to support an uploading process (and not just reusing existing images from commons).
+
+That will be done very soon, next week iirc. ({T40030})
+ 
+> As the image upload workflow gets supported inside VE,  Flow would adopt those powers too (at least for the rich text view where VE is used). If I recall correctly, exposing the ""insert media"" icon is just a simple configuration change.
+
+There is two different requests from communities : 
+- add images on a conversation
+- add smileys/kittens/whatever on a conversation ([[https://www.mediawiki.org/w/index.php?title=Topic:Smsn1ofyp04kqxle&topic_showPostId=snovfwyo3tasvyou#flow-post-snovfwyo3tasvyou | usual tools  ]] on a chat)
+
+And there is still the following needs:
+- add a toolbar to wikitext
+- personalize the toolbars (I would love to have my personal pre-written messages when I answer on the fr help desk)",1462180984,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1747890, @Pginer-WMF wrote:
+>> Create a minima a way to personalize VE and wikitext toolbars with a gadget would be a good idea.
+> 
+> Adding media is a reasonable usecase for conversations. We consider providing support for it from the beginning but the decision was postponed until VE would be able to support an uploading process (and not just reusing existing images from commons).
+
+That will be done very soon, next week iirc. ({T40030})
+ 
+> As the image upload workflow gets supported inside VE,  Flow would adopt those powers too (at least for the rich text view where VE is used). If I recall correctly, exposing the ""insert media"" icon is just a simple configuration change.
+
+There is two different requests from communities : 
+- add images on a conversation
+- add smileys/kittens/whatever on a conversation ([[ https://www.mediawiki.org/w/index.php?title=Topic:Smsn1ofyp04kqxle&topic_showPostId=snovfwyo3tasvyou#flow-post-snovfwyo3tasvyou | usual tools  ]]on a chat)
+
+And there is still the following needs:
+- add a toolbar to wikitext
+- personalize the toolbars (I would love to have my personal pre-written messages when I answer on the fr help desk)",1445606259,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"> Create a minima a way to personalize VE and wikitext toolbars with a gadget would be a good idea.
+
+Adding media is a reasonable usecase for conversations. We consider providing support for it from the beginning but the decision was postponed until VE would be able to support an uploading process (and not just reusing existing images from commons).
+
+As the image upload workflow gets supported inside VE,  Flow would adopt those powers too (at least for the rich text view where VE is used). If I recall correctly, exposing the ""insert media"" icon is just a simple configuration change.
+",1445605062,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"A user [[ https://fr.wikipedia.org/w/index.php?title=Sujet:Sqsccaf41ercbdaq&topic_showPostId=sqtsyrdrdzk309os#flow-post-sqtsyrdrdzk309os | complains ]] about she can't post pictures of kittens on a conversation. We definitely need to do something. For kittens.
+
+Create //a minima// a way to personalize VE and wikitext toolbars with a gadget would be a good idea. I know, there is always risks of abuses (thousand of buttons) but this did not happen with wikitext editing toolbar afak.",1445604231,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"On [[ https://fr.wikipedia.org/w/index.php?title=Sujet:Sox3xbkro37l4fta&topic_showPostId=sox3xblgm25yjf9q#flow-post-sox3xblgm25yjf9q | this feedback ]], a user asks to have personalized buttons on the toolbar (#3), and a way to add templates (#8).",1442303722,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,See also https://www.mediawiki.org/wiki/Topic:Smsn1ofyp04kqxle.,1440514581,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,Shouldn't this be resolved?,1440464281,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"In ru.wiki we definitely ourselves will add some buttons for wikitext. (https://ru.wikipedia.org/wiki/Википедия:Викификатор , https://ru.wikipedia.org/wiki/Википедия:Гаджеты/Упрощение_ссылок ) Something for these buttons ""it was necessary already yesterday"".",1428190160,PHID-USER-5joeladhczukimiv4rwl,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1115277, @DannyH wrote:
+> I added new screenshots from the prototype to T90764.
+> 
+> I have a question about the Mentions modal: If there are a lot of users who have posted on the thread, does it get a scroll bar? 
+
+Yes.  Try typing Assoc into the link inspector to get an idea.  Ours probably won't be a truncated list, though.
+
+I've created {T92588} to track this specifically.",1426206978,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I added new screenshots from the prototype to T90764.
+
+I have a question about the Mentions modal: If there are a lot of users who have posted on the thread, does it get a scroll bar? ",1426202773,PHID-USER-37czexl6ekrvcmp2tyqq,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"> - Inspector (the one you see when you click the link icon)
+We can start using this. I can create a mockup to illustrate the dialog in that format.",1426178885,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1099845, @Pginer-WMF wrote:
+> For the mention dialog (check mockups below), I would recommend the following:
+> - Show the dialog in-line with the text. When the user clicks on the mention icon, the dialog is shown where the text cursor is. This makes the user feel that she is manipulating the content directly since the information is in a single place.
+
+We decided it will use an inspector, at least initially.
+
+> - Initially, provide as the auto-suggestion values the users that participate in the current conversation or sub-conversation, or the frequently mentioned by the user (or any other criteria that can anticipate the user action and it is easy to implement).
+
+Auto-complete will use all authors in the current topic.",1426178846,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"VE basically has two types of dialogs:
+
+* Inspector (the one you see when you click the link icon)
+* Dialog (e.g. Insert->Template)
+
+For now, I think we should stick to one of these two, for both maintainability and visual consistency.  The closer one (but not that close) is inspector.",1425948264,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I also put together some of the mockups we mentioned for the first version [[ http://pauginer.github.io/prototypes/flow/editor/index.html | in this prototype ]]. Only basic transition between modes are supported, don't expect to actually turn text into bold.",1425903324,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"For the mention dialog (check mockups below), I would recommend the following:
+- Show the dialog in-line with the text. When the user clicks on the mention icon, the dialog is shown where the text cursor is. This makes the user feel that she is manipulating the content directly since the information is in a single place.
+- Initially, provide as the auto-suggestion values the users that participate in the current conversation or sub-conversation, or the frequently mentioned by the user (or any other criteria that can anticipate the user action and it is easy to implement).
+- As the user types, auto-suggestions will show users with the given username (if possible, it would be great to be flexible in the search to typos and preferred names if those are available). The first selection will be highlighted (following the standard style for list selection).
+- If the user is not found, some text will indicate so.
+- An option to close the dialog is provided.
+- The dialog can be controlled with the keyboard. The user can type @ and the dialog will open for the user to just type the user name and hit enter to insert the first selection from the list. We may want to not interfere with the use of ""@"" as a valid character. For that we may want to (a) make sure that the ""@"" happens in a valid context (after a space, text beginning, or non-word character) to avoid it appearing when users type an email for example; and (b) close the panel if the user types a space after having pressed ""@"", which would just result in adding the ""@"" character. the ""esc""key will close the dialog.
+- Most of the time the mention action will be triggered without a selected text,but if there is a text selection, we may want to use that text for the user search when the panel is opened. In this scenario, if the operation is cancelled, the user text should not be destroyed.
+
+
+
+{F65305}
+
+{F65534}
+
+{F65307}",1425901972,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Pau, I think the only mockup that we still need is the mentions modal... Am I forgetting anything?
+
+",1425603473,PHID-USER-37czexl6ekrvcmp2tyqq,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"We talked about this in the design meeting this morning, and decided on a plan for v1. 
+
+We need to get a simple v1 of the VE toolbar out soon, in order to roll out on a couple of languages that are excited about trying out Flow. 
+
+So v1 will have:
+
+* Bold/Italics (with a menu offering the two choices)
+* Link (with the same VE modal)
+* Mention (with a new modal)
+* Toggle to wikitext / VE
+
+There are several pieces that we definitely want to include, but not in the v1: Lists, something that helps with Code/Pre/Nowiki/Blockquote (tbd), and Insert media. (Insert media would be especially helpful if it includes an upload picture function, so that people could upload screenshots when they're asking for help.) ",1425603391,PHID-USER-37czexl6ekrvcmp2tyqq,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"The idea is for the different controls to behave like they do on the VE toolbar (preferably using the same components, just adjusting how prominent they are shown according to our context). For the case of the text format action, a drop-down like the one used by VE will be shown:
+
+{F53362}
+
+
+Regarding which controls to use, some thoughts:
+- Regarding the ""code"" and ""nowiki"", I wonder if we can have a unified ""quote"" action to cover most of the usecases (refer to portions of wikicode, source code, or specific parts of a comment someone previously said).
+- We may consider lists and inserting media to be under the ""more"" section. For example, in the current conversation in Phabricator they are used frequently and, although it cannot be generalised, I wonder if they may be used more in the wiki context if they were easily accessible.
+- I think it is ok to start with fewer controls and iterate on adding new ones.
+
+With the controls mentioned above, the expanded ""more"" menu can either expand in-place the advanced controls or be a regular dropdown menu (the later may be easier to support initially, but if menu items grow, or we want to better support repetitive use the former is preferred):
+
+{F53387}
+
+{F53373}",1425375273,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"if anyone is going to write 'yet another toolbar', can someone please make sure to really think stuff through ? I'm counting:
+
+1: Old toolbar (that community doesn't want to get rid off, yet we do)
+2: WikiEditor toolbar (that we prefer over old, but is also a bit over designed and old style JS)
+3: VE toolbar (OOjs UI, but not yet finished)
+4: Mobile Editing versions of VE toolbar.
+5: and now Flow
+
+Will the Math extension soon require 4 modules to provide a math insertion button to all editors types ?
+We have things like textSelection, confirmCloseWindow, live preview and stash. All that stuff comes into play, and any new wikitext editor work we do should recognize that and along the way should try to improve and consolidate.
+
+Similarly:
+```
+Enhancing WikiEditor for normal pages is completely outside the scope of this bug.
+```
+But please do account for the many ways in which it is FAILING users.",1425377996,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"if anyone is going to write 'yet another toolbar', can someone please make sure to really think stuff true ? I'm counting:
+
+1: Old toolbar (that community doesn't want to get rid off, yet we do)
+2: WikiEditor toolbar (that we prefer over old, but is also a bit over designed and old style JS)
+3: VE toolbar (OOjs UI, but not yet finished)
+4: Mobile Editing versions of VE toolbar.
+5: and now Flow
+
+Will the Math extension soon require 4 modules to provide a math insertion button to all editors types ?
+We have things like textSelection, confirmCloseWindow, live preview and stash. All that stuff comes into play, and any new wikitext editor work we do should recognize that and along the way should try to improve and consolidate.
+
+Similarly:
+```
+Enhancing WikiEditor for normal pages is completely outside the scope of this bug.
+```
+But please do account for the many ways in which it is FAILING users.",1425372893,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"+1 to the idea of starting with a subset of the current VE toolbar for articles.
+
++1 to the idea of enabling in the Flow VE buttons the same UX as the full ED version.",1425364714,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Based on these example threads, and our goal to rollout further at mediawikiwiki, and He7d3r's comment above, and my own experience, I still strongly advocate for having `<code>` and `<nowiki>` tags available and planned from the start (in a dropdown menu).
+
+* https://ca.wikipedia.org/wiki/Topic:Sbk26yv6cpcxxm87
+* https://ca.wikipedia.org/wiki/Topic:Sbi6jrldf94ea8nt
+* https://ca.wikipedia.org/wiki/Topic:Sa23rwtl0w12e4sk
+* https://ca.wikipedia.org/wiki/Topic:S8h1yv4n7yfm4fmi
+* https://ca.wikipedia.org/wiki/Topic:S8adbxrruu971vyd
+* https://fr.wikipedia.org/wiki/Sujet:Sb3nxhhm4wdodaez
+* https://fr.wikipedia.org/wiki/Sujet:Sabk082dkr6rat37
+* https://fr.wikipedia.org/wiki/Sujet:Sb3m5set5zkob0rj
+* https://fr.wikipedia.org/wiki/Sujet:Sbceer9529lnk66g
+Being able to //discuss// wikimarkup, is crucial to so many of the places we want to deploy to.",1425349109,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Link should be exactly the same as VE once you click it, both for a consistent user experience and so we don't have to implement a new link widget (with autocomplete, etc.)",1425346213,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I talked to James about toolbar use in VE -- they don't currently have tracking on which buttons get used the most. But he gave me his gut instinct on it, which I think is good enough for a first pass. 
+
+He said that for discussions, the most used tools are: Links, Mentions, and Bold/Italics. 
+
+(For article content, he'd also include Citations, Templates & Media, but these aren't as important for discussions.)
+
+I think we can go with Pau's mockups for a first version of a VE/Flow toolbar. We can even take out the ellipsis/more menu, and just have these controls:
+
+* Bold/Italics
+* Link
+* Mention
+* switch to wikitext
+
+This will be better than not having one, and we can find out what else people need from there. 
+
+Pau, we'll need mockups that show what happens when you click on those buttons. I'm assuming Bold/Italics has a dropdown menu. Would Link and Mention have little modal boxes? 
+
+{F34174}
+{F34176}
+{F52902}",1425343610,PHID-USER-37czexl6ekrvcmp2tyqq,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1061982, @Pginer-WMF wrote:
+> 
+> @GOIII, so for the specific case of discussions in Wikisource, is there any specific kind of content that would be useful to get help from a rich text editor to deal with in converstions?
+> 
+> I tried to look for some complex scenarios based on current use but [[ https://en.wikisource.org/wiki/Talk:The_Metamorphosis | in the example I found ]] formatting needs seemed basic (user mentions, lists, and links). Do you know of some examples of current (or potential) uses of more advanced formatting?
+
+@Pginer-WMF - Boy, finding something in NS-1 (the talkspace for the main namespace) that would benefit from //Flow// is not likely to exist. Again, Wikisource's mainspace output follows the premise of ''reproducing an original publication as faithfully as possible"" so there is little left to question where long or ongoing talk page discussions are likely needed to take place.
+
+Still, we do have continuous ""action"" in the Village Pump equivalent, [[https://en.wikisource.org/wiki/Wikisource:Scriptorium| Scriptorium]], that might benefit from using //Flow//. Debate traffic also exists for certain Help: and Template: namespace pages every so often, but nowhere near approaching the typical Wikipedia article's talkpage traffic or timeframe.
+
+I'll keep looking for other possible examples in mind but I wouldn't bet on anything more substantial coming to light beyond those already mentioned.",1425073820,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"> Flow is pretty and (I guess) helpful for ongoing or complex discussions; we just don't have as many instances of this as Wikipedia seems to have. Sure, making it standard provides easier maintenance across all wikis but it won't add much ""value"" to our project if any at all.
+
+ @GOIII, so for the specific case of discussions in Wikisource, is there any specific kind of content that would be useful to get help from a rich text editor to deal with in converstions?
+
+I tried to look for some complex scenarios based on current use but [[ https://en.wikisource.org/wiki/Talk:The_Metamorphosis | in the example I found ]] formatting needs seemed basic (user mentions, lists, and links). Do you know of some examples of current (or potential) uses of more advanced formatting?",1424776115,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1060761, @Quiddity wrote:
+>>>! In T78346#1038829, @GOIII wrote:
+>> So until we either actively poll for as much or implement & advertise those ""enhancements"" to accurately gauge User: preference, etc., we're just making decisions based in conjecture & assumptions more so than in reality and facts.
+> 
+> The Design Research team did some investigation into editing tools. I believe they're still compiling the results, but here are the links for watchlisting: https://www.mediawiki.org/wiki/Design/Research#Editing
+
+My point exactly - ""they"" limited their concerns, polling and decision to a single project (Wikipedia) -- which has a certain scope and a specific mission -- both of which translate to almost the complete opposites as far as Wikisource is concerned (a //different// project with a //different// scope and a //different// mission). 
+
+Wikipedia is an ongoing collaborative endeavor that expects both mainspace presentations and non-mainspace discussions to always be in a state of perpetual flux to some degree thanks to it's inherent nature where new developments = addition of new sources to support new content = new points of contentions to work through.
+
+Wikisource, on the other hand, shares little with Wikipedia beyond also being an ongoing collaborative endeavor. Our mainspace end products are suppose to be static by design and as a result our non-mainspace discussions are mostly style guide/formatting/bug/enhancement related in nature.
+
+What does this mean? In a nutshell (a few examples-wise), this means...
+# Nobody here gives a crap about citation tools et. al anywhere near the degree to which Wikipedians do - we primarily deal with static footnotes found in the original fixed content of a specific edition of a copyright free publication. So -- while the two //feel// similar at first glance -- they are not in practice nor purpose.
+# Thanks to the nature of the works being reproduced and hosted on WS, our needs for image manipulation and presentation make things like Media Viewer completely useless.
+# Flow is pretty and (I guess) helpful for ongoing or complex discussions; we just don't have as many instances of this as Wikipedia seems to have. Sure, making it standard provides easier maintenance across all wikis but it won't add much ""value"" to our project if any at all.
+# We don't attract the temp newbie contributor types in any comparable numbers nor are they likely to need toolbar dialog crutches to facilitate contributions. What prevents folks by us to break out of their specific favorites into ""new"" works is an easier way to customize tools to specific works & not so much the repetitive WP-like tasks. 
+# ... and I could go on ad nausea
+
+The point -- as it relates to the issue of editing/toolbars in general and development overall -- is ""we"" basically continue to have no say in these matters; if an editing feature or a contribution aspect is not Wikipedia- or Commons- centric, the editing needs of other projects will, at best, be an add-in, a work around or some other afterthought -- //if ""we"" are lucky, that is//. The [[https://www.mediawiki.org/wiki/Editing_Tasks_Survey|Editing Tasks Survey]] mentioned is but another example of this....
+
+> ... Based on the above criterion, we queried our internal data-bases for **English Wikipedia users** and found 9316 users to contact.
+
+Doesn't seem like anything ""good-for-Wikisource"" can from decision making based on polling like that does it?
+",1424735529,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1060761, @Quiddity wrote:
+>>>! In T78346#1038829, @GOIII wrote:
+>> So until we either actively poll for as much or implement & advertise those ""enhancements"" to accurately gauge User: preference, etc., we're just making decisions based in conjecture & assumptions more so than in reality and facts.
+> 
+> The Design Research team did some investigation into editing tools. I believe they're still compiling the results, but here are the links for watchlisting: https://www.mediawiki.org/wiki/Design/Research#Editing
+
+My point exactly - ""they"" limited their concerns, polling and decision to a single project (Wikipedia) -- which has a certain scope and a specific mission -- both of which translate to almost the complete opposites as far as Wikisource is concerned (a //different// project with a //different// scope and a //different// mission). 
+
+Wikipedia is an ongoing collaborative endeavor that expects both mainspace presentations and non-mainspace discussions to always be in a state of perpetual flux to some degree thanks to it's inherent nature where new developments = addition of new sources to support new content = new points of contentions to work through.
+
+Wikisource, on the other hand, shares little with Wikipedia beyond also being an ongoing collaborative endeavor. Our mainspace end products are suppose to be static by design and as a result our non-mainspace discussions are mostly style guide/formatting/bug/enhancement related in nature.
+
+What does this mean? In a nutshell (a few examples-wise), this means...
+# Nobody here gives a crap about citation tools et. al anywhere near the degree to which Wikipedians do - we primarily deal with static footnotes found in the original fixed content of a specific edition of a copyright free publication. So -- while the two //feel// similar at first glance -- they are not in practice nor purpose.
+# Thanks to the nature of the works being reproduced and hosted on WS, our needs for image manipulation and presentation make things like Media Viewer completely useless.
+# Flow is pretty and (I guess) helpful for ongoing or complex discussions; we just don't have as many instances of this as Wikipedia seems to have. Sure, making it standard provides easier maintenance across all wikis but it won't add much ""value"" to our project if any at all.
+# We don't attract the temp newbie contributor types in any comparable numbers nor are they likely to need toolbar dialog crutches to facilitate contributions. What prevents folks by us to break out of their specific favorites into ""new"" works is an easier way to customize tools to specific works & not so much the repetitive WP-like tasks. 
+# ... and I could go on ad nausea
+
+The point -- as it relates to the issue of editing/toolbars in general and development overall -- is ""we"" basically continue to have no say in these matters; if an feature aspect is not Wikipedia- or Commons- centric, it will at best be an add-in, a work around or some other afterthought if ""we"" are lucky. The [[https://www.mediawiki.org/wiki/Editing_Tasks_Survey|Editing Tasks Survey]] mentioned is but another example of this....
+
+> ... Based on the above criterion, we queried our internal data-bases for **English Wikipedia users** and found 9316 users to contact.
+
+Doesn't seem like anything ""good-for-Wikisource"" can from decision making based on polling like that does it?
+",1424735342,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1038829, @GOIII wrote:
+> So until we either actively poll for as much or implement & advertise those ""enhancements"" to accurately gauge User: preference, etc., we're just making decisions based in conjecture & assumptions more so than in reality and facts.
+
+The Design Research team did some investigation into editing tools. I believe they're still compiling the results, but here are the links for watchlisting: https://www.mediawiki.org/wiki/Design/Research#Editing",1424731958,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1038747, @Mattflaschen wrote:
+> Note: Enhancing WikiEditor for normal pages is completely outside the scope of this bug.
+
+Then don't select the next course of action based solely on that mwgrep's results.
+
+Folks aren't using WikiEditor in some meaningful number just because of the lack in the ease of customization compared to the //Classic// toolbar followed by some other meaningful number for the inability to prevent the generation of WikiEditor's current defaults.
+
+So until we either actively poll for as much or implement & advertise those ""enhancements"" to accurately gauge User: preference, etc., we're just making decisions based in conjecture & assumptions more so than in reality and facts.",1423892360,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1026966, @Quiddity wrote:
+> Separately, I know there is some amount of local customization of the WikiEditor Toolbar buttons (both individually, and at the wiki-level), but I'm not sure how widespread the individual customizations are, nor how to find out, beyond searching for ""addToToolbar"" at each wiki in user-space and mediawiki-space. Any suggestions?
+
+mwgrep can answer this question for WMF production.  It allows searching for CSS and JS in the User, MediaWiki, or Module namespaces (one at a time).
+
+>>! In T78346#1033515, @GOIII wrote:
+> Make the current //WikiEditor// defaults an option or User pref with a far more simply way to customize it for individuals and I guarantee you the ""opting-in"" of the //Classic// toolbar would drop off drastically.
+
+Note: Enhancing WikiEditor for normal pages is completely outside the scope of this bug.",1423886182,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1026966, @Quiddity wrote:
+> ...
+> Separately, I know there is some amount of local customization of the WikiEditor Toolbar buttons (both individually, and at the wiki-level), but I'm not sure how widespread the individual customizations are, nor how to find out, beyond searching for ""addToToolbar"" at each wiki in user-space and mediawiki-space. Any suggestions?
+
+IMHO, you'd be doing yourself an injustice if you try to make decisions or draw up plans based on a tally of the ""current"" numbers or try to apply a ""strict"" accounting rationale in order to reliably ascertain something like that.
+
+Speaking entirely from the perspective of an Admin primarily focused on the needs and wants of en.wikisource contributors, a vast majority were not entirely thrilled with the //Classic// toolbar to begin with.... but the ease of customizing it to specific needs still makes it near & dear to just about anyone with any decent amount contributing time under their belts even today. And its not entirely true when folks were never ""sold"" on what the //WikiEditor// initiative(s) promised either.
+
+Most folks by me tried //WikiEditor// when it came off the beta status and immediately hated what they a.) were being forced to load as the ""defaults"" closely followed by b.) the convoluted process needed just to add customizations to make a.) somewhat bearable. Take those two points and add-in the fact the ProofreadPage extension made life with //WikiEditor// more problematic as time went by and the exodus back to using the //Classic// toolbar is not hard to understand.
+
+So its not that [my] people //won't// or //don't// utilize //WikiEditor// because it ""sucks"" or something but because -- at its core -- its specifically designed for the never-to-appear-again-in-the-numbers-they-once-did newbie or occasional Wikipedia-geared contributor with Wikipedia-like needs (not the deal-breaker however). What everybody agrees on as the major roadblock is the forcing of 'crap' as defaults nobody will ever use in addition to the inability to remove said defaults nor the customization of buttons & such without jumping through a billion hoops most non-techie types just won't deal with.
+
+Make the current //WikiEditor// defaults an option or User pref with a far more simply way to customize it for individuals and I guarantee you the ""opting-in"" of the //Classic// toolbar would drop off drastically.
+",1423713968,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"On talk pages, I believe these are the custom buttons I use the most:
+> <code>test</code>
+> <nowiki>test</nowiki>
+> <syntaxhighlight lang=""javascript"" enclose=""none"">test</syntaxhighlight>
+> <span style=""color: #000; background: #E99;""></span>
+> <pre>test</pre>
+(mainly because I usually help with technical problems in the wikis I use) and for content pages,
+> <math>test</math>
+which was removed in 2009 by the usability initiative
+https://usability.wikimedia.org/wiki/Talk:Releases/Acai#Math",1423566520,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1017880, @He7d3r wrote:
+> I miss my custom buttons in the edit toolbar.
+> See also:
+> * {T23692}
+
+I installed 3 of your scripts to test: https://meta.wikimedia.org/w/index.php?title=User:Quiddity_%28WMF%29/global.js&diff=11213986&oldid=10917385
+And took these screenshots: http://imgur.com/a/na16D#0
+
+Are there any use-cases here that might be widely applicable to an entire wiki, or even to all wikis as a default Flow feature? Or perhaps a global-template (if/when those arrive) ?
+
+Separately, I know there is some amount of local customization of the WikiEditor Toolbar buttons (both individually, and at the wiki-level), but I'm not sure how widespread the individual customizations are, nor how to find out, beyond searching for ""addToToolbar"" at each wiki in user-space and mediawiki-space. Any suggestions?",1423536220,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"I miss my custom buttons in the edit toolbar.
+See also:
+* {T23692}",1423143413,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"We're going to work on this as part of turning on VE for Flow. 
+
+The current spike card is T88182 : Define and estimate work for Minimum Viable Product of VisualEditor in Flow (spike)",1423090263,PHID-USER-37czexl6ekrvcmp2tyqq,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"We're going to work on this as part of turning on VE for Flow. 
+
+The current spike card is T88182",1423090207,PHID-USER-37czexl6ekrvcmp2tyqq,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Since people are already talking about VE, I expanded the scope of the task somewhat (""WikiEditor"" is the wikitext toolbar shown in production).  This is in the idea/design stage, so it's okay to cover both technologies in the same task for now.",1422944651,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Since people are already talking about VE, I expanded the scope of the task somewhat (""WikiEditor"" is the wikitext toolbar shown in production).  This is in the idea/design stage, so it's okay to cover both technologies in the same card for now.",1422944638,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#1010433, @Pginer-WMF wrote:
+> Regarding the second comment, I think you are right and we could avoid the whole mode switching if VE supported wikitext input.
+
+Currently, VE mostly just warns you about this (""Wikitext markup detected"")
+
+Even if VE supported certain obvious wikitext examples (actually, it does for certain very limited cases like the * list keyboard shortcut), it's never going to support the full power of wikitext.  That would require a *third* full-featured wikitext parser, in addition to the PHP MW parser and Parsoid, with the added complication that the source text is part rich text, part wikitext.
+
+I think mode switching is a better choice.  We can make the mode switch control normally subtle, then become obvious if you start typing wikitext (VE already has logic to detect this, as noted above).",1422942621,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"@Jaredzimmerman-WMF regarding the first comment, I think we need a general framework to deal with actions attached to input fields. I was thinking on distributing actions on the left and configuration on the right where the input method menu could fit.
+
+Regarding the second comment, I think you are right and we could avoid the whole mode switching if VE supported wikitext input.",1422929636,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Two things…
+
+I think its smart to have WYSIWYG as the default, but we'd talked in the past about having the bottom right corner reserved for IME tools, we should decide on the merit of having that be the WTE/VE switch vs access to IME, especially if we want IME to be a standard component on input fields. 
+
+One thing that I've been asking for forever was the ability for VE to detect wikitext input and parse it on the fly to convert to rich text, not to increase scope but this might be an ideal use case for this, rather than manually switching between modes. ",1422908982,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Discussing this with Pau -- we'll have to define the set of controls that we'll expose. We'll look at current use on talk pages, and also talk with some of the people who are currently using Flow (or will be using it soon). 
+
+Today's hypothesis for what we think are important:
+* Links 
+* Mentions
+* Lists?
+* Add image?
+
+Not sure about Bold/Italics/Underline. 
+
+Whatever we decide on, we'll have to use event logging to see if people are using the ""More"" section to access other controls. 
+
+All of this WIP.",1422907976,PHID-USER-37czexl6ekrvcmp2tyqq,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"For the contest of Flow, I think styling controls should be less prominent than the user message, and consider the specific needs in the context of Flow. That may imply to hide some controls and show new ones (e.g., user mentioning).
+
+I created a mockup showing these ideas, but more research is needed to determine the specific actions to show:
+{F34174}
+
+The above was done assuming rich text editing as the default mode and making it possible to switch to wikitext for advanced users. I didn't include a specific toolbar for wikitext in the mockups but it would be possible to keep the same tools if we really think that they are needed in that mode. This is illustrated below:
+{F34176}",1422903281,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#844010, @Qgil wrote:
+> But, but, but... 
+
+On a second thought, I'm happy with the solution that can land faster. At the end, this is an interim situation while VisualEditor integration in Flow comes. On that day, we will have most likely two main types of Flow users: those defaulting consistently to VE and those defaulting consistently to wikitext. If both have the tools they want, both will be happy.",1418466425,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843120, @Quiddity wrote:
+> Personally, I'd like to have the entire existing WikiEditor toolbar in Flow, with 1 exception.[1]
+> I often need special characters, or `<nowiki>` tags, or to insert an image, or create a table, or add a citation for discussion.{F20913}
+> 
+> [1] The //only// element I think we'd want to remove, is the signature button. And that should be removed when the toolbar is shown on articles anyway, so double benefit if we solve it!
+> 
+> Can we add that to WikiEditor, somehow?
+
+//My repeated solution -->// ... all we need to do is add...
+
+		'filters': [ 'body.ns-talk' ],
+
+... to the 'signature' button's entry in...
+
+		jquery.wikiEditor.toolbar.config.js
+
+... and you're done. The same approach is used for the 'reference' button btw (see [[https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FWikiEditor/HEAD/modules%2Fjquery.wikiEditor.toolbar.config.js#L170 | that same .js file]] if you don't believe me).
+
+This way, all talk pages will automatically generate the 'signature' button while solving the immediate issue of how to stop its generation in the ns-0 and other Subject-space namespaces.
+If it was up to me, I'd at least thrown in the Project: namespace (like for Village Pump) along with all the talkspaces...
+
+		'filters': [ 'body.ns-talk, body.ns-4' ],
+
+... The above should be the common sense ""default"" setting. And I suspect all the  other ""hide WikiEditor type of fixes"" floating about would not be affected no matter what this 'filters' setting might be set to - no?",1418432048,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843064, @Mattflaschen wrote:
+> If OOJS-UI (the UI library used by VE) rolled out everywhere (to e.g. WikiEditor) this consideration would no longer apply
+
+We're on it. Not in the next few weeks, though.",1418423358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"But, but, but... Flow is about simplicity for everybody, and for increasing the participation of newcomers in discussions. <ref> in comments? Tables? Really? I'd rather bet on a very simple setup that solves 90% of the formatting used 90% of the times by 90% of the users. Then the ""Help"" link explains how to type all the rest. ",1418380297,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843120, @Quiddity wrote:
+> [1] The //only// element I think we'd want to remove, is the signature button. And that should be removed when the toolbar is shown on articles anyway, so double benefit if we solve it!
+
+See T42972. Seems like it ought an easy bug to resolve, but not so.",1418360651,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"Personally, I'd like to have the entire existing WikiEditor toolbar in Flow, with 1 exception.[1]
+I often need special characters, or `<nowiki>` tags, or to insert an image, or create a table, or add a citation for discussion.{F20913}
+
+[1] The //only// element I think we'd want to remove, is the signature button. And that should be removed when the toolbar is shown on articles anyway, so double benefit if we solve it!
+
+(Note, the CharInsert (special character section //under// the editing window) uses this code, to remove the signature button, when we're editing mainspace. 
+`{{#ifeq:{{NAMESPACE}}|{{ns:0}}||'''Sign your posts on talk pages:''' <nowiki>~~~~</nowiki> &nbsp;}}` at https://en.wikipedia.org/w/index.php?title=MediaWiki:Edittools&diff=559635127&oldid=558019716
+Can we add that to WikiEditor, somehow?",1418342597,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843064, @Mattflaschen wrote:
+> It would make more sense to use the WikiEditor icons.
+
+I disagree, because Flow design and VE design fit, while the old toolbar icons will look really old there, and what matters is the impression we cause to new users, but.... this is not a battle I will pick.  :)
+
+In any case the icons are available. It is a matter of deciding which options would survive the pruning (I just added a proposal to the description) and reuse them. There is basically no need for asset creation.",1418340570,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,">>! In T78346#843053, @Qgil wrote:
+> There is no lack of existing design assets. Why not just removing the VE toolbar icons that are superfluous in the context of discussions? See M26
+
+As of now, using the VE toolbar (or a subset of it) for wikitext would be very confusing.  Looking at your mockup, it strongly makes me think I'm using VisualEditor (the only odd man out is the Preview button).
+
+It would make more sense to use the WikiEditor icons.  If OOJS-UI (the UI library used by VE) rolled out everywhere (to e.g. WikiEditor) this consideration would no longer apply (but at that point we'd want another way to visually hint to people whether they're using wikitext or VE).",1418339741,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,There is no lack of existing design assets. Why not just removing the VE toolbar icons that are superfluous in the context of discussions? See M26,1418339394,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,There is no lack of existing design assets. Why not just removing the VE options that are superfluous in the context of discussions? See M26,1418339336,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wikitext editing toolbar for Flow,"adding design, as we had previously talked about adding the default toolbar and it was considered too cluttered and confusing.  Something less confusing would need to be designed.",1418336842,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-monj46bisauzpolgauzi,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"Steps to reproduce:
+
+1.Open a page with VE
+2.Place a cursor after a text like ""sub-heading 1""
+3.Open the link inspector
+
+Observe that the character 1 is not getting selected and the link inspector is opening at the end of the line
+
+{F20734}
+",1418251189,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_description,resolved
+Wordbreak detection is faulty for selection starting just down-page of a single character,Verified the fix in Betalabs and test2,1427330396,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"Change 197661 merged by jenkins-bot:
+[BREAKING CHANGE] Use Unicode character class to calculate word expansions
+
+[[https://gerrit.wikimedia.org/r/197661]]",1426727791,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"Change 197661 had a related patch set uploaded (by Divec):
+WIP: BREAKING CHANGE: Use unicode character class to calculate word expansions
+
+[[https://gerrit.wikimedia.org/r/197661]]
+",1426698338,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"UnicodeJS change was released in v0.1.3, which is now in VisualEditor core master following https://gerrit.wikimedia.org/r/188729 – what's next?",1423103268,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"The word break calculation is correct:
+
+|Sub| |heading| |1|
+
+But our word expansion logic avoids wrapping single length ranges due to the following cases:
+
+|Double| | |Space|
+
+|中|國|人|",1421340158,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Wordbreak detection is faulty for selection starting just down-page of a single character,"I spoke to David about this issue, there is definitely something off about how we account for word boundary and wordbreaks.",1420845176,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-5mt4qblkmzcmmaz4z7cw,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,Message 'visualeditor-find-and-replace-regular-expression' missing.,1418237110,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-baxx2wdr226fyxswg265,task_description,resolved
+Message 'visualeditor-find-and-replace-regular-expression' missing,We should really be consuming modules.json from core to avoid problems like this,1422061033,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Change 178883 merged by jenkins-bot:
+Follow-up I4e38607d8: Register <visualeditor-find-and-replace-regular-expression>
+
+[[https://gerrit.wikimedia.org/r/178883]]",1418238206,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Change 178881 merged by jenkins-bot:
+Follow-up I4e38607d8: Register <visualeditor-find-and-replace-regular-expression>
+
+[[https://gerrit.wikimedia.org/r/178881]]",1418238111,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Change 178883 had a related patch set uploaded (by Jforrester):
+Follow-up I4e38607d8: Register <visualeditor-find-and-replace-regular-expression>
+
+[[https://gerrit.wikimedia.org/r/178883]]
+
+#patch-for-review",1418238017,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Change 178881 had a related patch set uploaded (by Jforrester):
+Follow-up I4e38607d8: Register <visualeditor-find-and-replace-regular-expression>
+
+[[https://gerrit.wikimedia.org/r/178881]]
+
+#patch-for-review",1418237509,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+Message 'visualeditor-find-and-replace-regular-expression' missing,"Bah, probably my screw-up.",1418237371,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-baxx2wdr226fyxswg265,task_subcomment,NA
+"Chinese table contents are lost when saving in VisualEditor, unless the first letter is in the Latin alphabet","[[ https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&offset=20141127161632#Input_Chinese_to_table_will_disappear_when_saving_unless_start_with_an_English_alphabet.__51109 | Original report ]] by Cwlin0416 on 27 November 2014:
+
+Input Chinese to table will disappear when saving unless start with an English alphabet.
+
+If i just type Chinese into table, it can't be saved, if i start with an English alphabet, the problem is solved.
+
+",1418190225,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ktvckajg62tqaio3n4gv,task_description,resolved
+"Chinese table contents are lost when saving in VisualEditor, unless the first letter is in the Latin alphabet","The problem was originally spotted in Google Chrome while using Traditional Chinese.
+
+The user says (at 16:48 UTC on 11 December) that it was fixed with the recent update.  From Elena's testing, it sounds like we should re-confirm this.",1418412422,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ktvckajg62tqaio3n4gv,task_subcomment,NA
+"Chinese table contents are lost when saving in VisualEditor, unless the first letter is in the Latin alphabet","Confirmed on https://zh.wikipedia.org/ - typed Cangjie(on Mac) in tables is not saved.
+
+Tried  in betalabs and test2(wmf12)  the typed text in tables is saved as well as  everywhere else.",1418252142,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-ktvckajg62tqaio3n4gv,task_subcomment,NA
+"Vertical alignment of the ""add template"" button and the search box is incorrect in template dialog in VisualEditor when using the OOjs UI MediaWiki theme","See screenshot:
+
+{F20272}",1418156342,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-675e74bf6yv4vzpihvax,task_description,resolved
+"Vertical alignment of the ""add template"" button and the search box is incorrect in template dialog in VisualEditor when using the OOjs UI MediaWiki theme","Change 179339 merged by jenkins-bot:
+TextInputWidget: Set vertical-align: middle, like buttons
+
+[[https://gerrit.wikimedia.org/r/179339]]",1418413007,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-675e74bf6yv4vzpihvax,task_subcomment,NA
+"Vertical alignment of the ""add template"" button and the search box is incorrect in template dialog in VisualEditor when using the OOjs UI MediaWiki theme","Above patch fixes this:
+
+{F20933}",1418347242,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-675e74bf6yv4vzpihvax,task_subcomment,NA
+"Vertical alignment of the ""add template"" button and the search box is incorrect in template dialog in VisualEditor when using the OOjs UI MediaWiki theme","Change 179339 had a related patch set uploaded (by Bartosz Dziewoński):
+TextInputWidget: Set vertical-align: middle, like buttons
+
+[[https://gerrit.wikimedia.org/r/179339]]
+
+#patch-for-review",1418339505,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-675e74bf6yv4vzpihvax,task_subcomment,NA
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,"See screenshot:
+
+{F20262}",1418156052,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cm26etfhdyviprbpebfm,task_description,resolved
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,"Change 179193 merged by jenkins-bot:
+MediaWiki theme: Use gray instead of blue for select and highlight
+
+[[https://gerrit.wikimedia.org/r/179193]]",1418332756,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-cm26etfhdyviprbpebfm,task_subcomment,NA
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,"Change 179193 had a related patch set uploaded (by Trevor Parscal):
+Use gray instead of blue for select and highlight
+
+[[https://gerrit.wikimedia.org/r/179193]]
+
+#patch-for-review",1418331144,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-cm26etfhdyviprbpebfm,task_subcomment,NA
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,Eww. Oh well.,1418254890,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cm26etfhdyviprbpebfm,task_subcomment,NA
+We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme,"See T78032, I think the MediaWiki theme calls for light gray for highlighted and a medium gray for selected.",1418166945,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-cm26etfhdyviprbpebfm,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"See screenshot:
+
+{F20257}",1418155912,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ywadwhslnfchsbahscag,task_description,resolved
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"Change 179518 merged by jenkins-bot:
+MediaWiki theme: Make button sizes match Apex
+
+[[https://gerrit.wikimedia.org/r/179518]]",1418411301,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"Change 179518 had a related patch set uploaded (by Jforrester):
+MediaWiki theme: Make button sizes match Apex
+
+[[https://gerrit.wikimedia.org/r/179518]]
+
+#patch-for-review",1418411091,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"The clipping depends on zoom level, so probably Chromium rendering bug.",1418405798,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,I'm pretty sure that's by design. The task for figuring out what to do with the massive buttons is T78169.,1418251037,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme,"No clipping for me in Chrome of FF, but the thing that really stands out is the massive difference in height between buttons and textboxes. That needs to get fixed.",1418236631,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ywadwhslnfchsbahscag,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"See screenshot:
+
+{F20257}",1418155886,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_description,resolved
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"Change 179545 merged by jenkins-bot:
+ButtonGroupWidget: Remove weird margin-bottom: -1px; from theme styles
+
+[[https://gerrit.wikimedia.org/r/179545]]",1418762865,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,https://gerrit.wikimedia.org/r/#/c/179545/,1418416810,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,This also affects the Apex theme.,1418416546,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"Change 179339 merged by jenkins-bot:
+TextInputWidget: Set vertical-align: middle, like buttons
+
+[[https://gerrit.wikimedia.org/r/179339]]",1418413007,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,Not fixed. I'm going to declare this not a blocker to switching.,1418412612,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"Above patch doesn't seem to fix the issue at hand:
+
+{F20931}",1418347245,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"I am not sure if the patch fixes the issue here, because I've somehow broken all the styles for the search-and-replace ""pulldown"" locally. Let's retest this after pulling all recent fixes through.",1418339584,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"Change 179339 had a related patch set uploaded (by Bartosz Dziewoński):
+TextInputWidget: Set vertical-align: middle, like buttons
+
+[[https://gerrit.wikimedia.org/r/179339]]
+
+#patch-for-review",1418339506,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+Vertical alignment of text in the search-and-replace field is off in VisualEditor,"We'd need to upstream this functionality into OOUI, as the input widget padding varies from skin to skin.",1418236814,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-63zjaemkihhdn67rqs2l,task_subcomment,NA
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","See screenshot:
+
+{F20244}",1418155549,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-426ekcmockyid64cqfva,task_description,resolved
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179343 abandoned by Trevor Parscal:
+[WIP] Apex theme: Fix box-sizing for inputs
+
+Reason:
+Didn't live up to my expectations. In that... It didn't work at all.
+
+[[https://gerrit.wikimedia.org/r/179343]]",1418412481,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-426ekcmockyid64cqfva,task_subcomment,NA
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179355 merged by jenkins-bot:
+MediaWiki theme: Improve search widget styling
+
+[[https://gerrit.wikimedia.org/r/179355]]",1418411795,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-426ekcmockyid64cqfva,task_subcomment,NA
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179355 had a related patch set uploaded (by Jforrester):
+Improve search widget styling in MediaWiki theme
+
+[[https://gerrit.wikimedia.org/r/179355]]
+
+#patch-for-review",1418345062,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-426ekcmockyid64cqfva,task_subcomment,NA
+"Parameter ""add more information"" label ""No unused fields"" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179343 had a related patch set uploaded (by Trevor Parscal):
+[WIP] Fix box-sizing for inputs
+
+[[https://gerrit.wikimedia.org/r/179343]]
+
+#patch-for-review",1418341325,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-426ekcmockyid64cqfva,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","See screenshot:
+
+{F20244}",1418155514,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_description,resolved
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179343 abandoned by Trevor Parscal:
+[WIP] Apex theme: Fix box-sizing for inputs
+
+Reason:
+Didn't live up to my expectations. In that... It didn't work at all.
+
+[[https://gerrit.wikimedia.org/r/179343]]",1418412482,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179355 merged by jenkins-bot:
+MediaWiki theme: Improve search widget styling
+
+[[https://gerrit.wikimedia.org/r/179355]]",1418411796,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","With the ""Improve search widget styling"" patch, this looks better but not ideal: {F20921}
+
+Adding the ""Fix box-sizing for inputs"" patch doesn't change the display: {F20923}
+
+For context, the current Apex display in master/OOUI 0.4.0: {F20925}",1418346030,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179355 had a related patch set uploaded (by Jforrester):
+Improve search widget styling in MediaWiki theme
+
+[[https://gerrit.wikimedia.org/r/179355]]
+
+#patch-for-review",1418345063,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"Parameter ""add more information"" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 179343 had a related patch set uploaded (by Trevor Parscal):
+[WIP] Fix box-sizing for inputs
+
+[[https://gerrit.wikimedia.org/r/179343]]
+
+#patch-for-review",1418341324,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qsx26ngxjl4avpi2ln2b,task_subcomment,NA
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","See screenshot:
+
+{F20244}",1418155481,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cidep33c4c5o3tej2ipd,task_description,resolved
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 178717 merged by jenkins-bot:
+ve.ui.MWParameter*: Use the destructive flag for all four remove buttons
+
+[[https://gerrit.wikimedia.org/r/178717]]",1418177075,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-cidep33c4c5o3tej2ipd,task_subcomment,NA
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme",">>! In T78033#835291, @TrevorParscal wrote:
+> Gosh that looks terrible. I don't know that the style guide actually demands this, because these are secondary actions and should thus be quieter.
+
+Yeah, but consistency…",1418169765,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cidep33c4c5o3tej2ipd,task_subcomment,NA
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Change 178717 had a related patch set uploaded (by Jforrester):
+ve.ui.MWParameter*: Use the destructive flag for all four remove buttons
+
+[[https://gerrit.wikimedia.org/r/178717]]
+
+#patch-for-review",1418169760,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-cidep33c4c5o3tej2ipd,task_subcomment,NA
+"We should set ""destructive"" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme","Gosh that looks terrible. I don't know that the style guide actually demands this, because these are secondary actions and should thus be quieter.",1418166758,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-cidep33c4c5o3tej2ipd,task_subcomment,NA
+Per-site configuration for enabling Media Viewer,"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 //
+
+== Narrative ==
+
+As a development team, we can enable Media Viewer by default on a few pilot sites, so that we can try it out in a limited release before deploying it everywhere.
+
+== Acceptance Criteria ==
+
+Add a site configuration option with which Media Viewer can be enabled for every user (including non-logged-in) on a few pilot wikis(e.g. Commons, French, Hungarian, Korean)
+ * Configure Beta Features so that when Media Viewer is enabled, it does not show up as a beta option anymore
+ * We can adapt the code used by VisualEditor for the same purpose
+ * After we've tested the feature on a few wikis, we may want to gradually increase the number of sites -- or enable it everywhere, based on community feedback.
+
+
+== Related Bugs ==
+
+== Related Stories ==
+
+== Related Changesets ==
+
+
+
+ [[https://gerrit.wikimedia.org/r/117374 | https://gerrit.wikimedia.org/r/117374]] ",1418056781,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-6hephrfe43g3sajiaspv,task_description,resolved
+Per-site configuration for enabling Media Viewer,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 | mingle]] on 2014-03-27 at 21:15:30, @Tgr wrote:
+
+https://gerrit.wikimedia.org/r/#/c/121526/",1418056789,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-6hephrfe43g3sajiaspv,task_subcomment,NA
+Per-site configuration for enabling Media Viewer,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 | mingle]] on 2014-03-07 at 02:08:31, @MarkTraceur wrote:
+
+https://gerrit.wikimedia.org/r/117374",1418056787,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-6hephrfe43g3sajiaspv,task_subcomment,NA
+Per-site configuration for enabling Media Viewer,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 | mingle]] on 2014-02-27 at 19:42:03, @Tgr wrote:
+
+I'll make this one into the server-side ticket and the other one into the client-side one.",1418056786,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-6hephrfe43g3sajiaspv,task_subcomment,NA
+Per-site configuration for enabling Media Viewer,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 | mingle]] on 2014-02-27 at 18:09:16, @MarkTraceur wrote:
+
+Should be merged with  [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/263 | #263]] ",1418056784,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-6hephrfe43g3sajiaspv,task_subcomment,NA
+VisualEditor Opt-In for BetaFeatures,"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/43 //
+
+== Narrative ==
+
+As a user, I want the option to enable Visual Editor, if it is not available by default on this site.
+
+== Acceptance Criteria ==
+
+Some sites require user opt-in for the VisualEditor (the English and German Wikipedias in particular aren't ready yet to make this feature available by default). So we would like to make the basic version of VisualEditor available as a prominent BetaFeature -- but for those sites only. For example, we could handle this issue by having a site whitelist/blacklist for each beta feature -- or there may also be other technical solutions that work just as effectively to achieve the same results.
+
+See more feature requirements here:
+
+ [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] 
+
+
+
+
+
+== Related Bugs ==
+
+== Related Stories ==",1418054265,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-v2ol64y3mialrzwjykor,task_description,resolved
+VisualEditor Opt-In for BetaFeatures,">>! In [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/43 | mingle]] on 2013-10-11 at 18:00:20, @MarkTraceur wrote:
+
+https://gerrit.wikimedia.org/r/78795",1418054267,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-v2ol64y3mialrzwjykor,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,AFAICT this hasn't been done yet?,1417898198,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_description,resolved
+Expose the production citoid service publicly so we can start switching scripts over to use it,My guess it the problem was T133830 or similar.,1461837156,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Er, I added the above commit 1,5 years ago.. not sure what just happened here...",1461825954,PHID-USER-xwxce3kpvsv54t735g7q,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,Thank you everyone. :-),1422075147,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Change 184904 merged by Alexandros Kosiaris:
+Re-use Parsoid Varnishes for citoid too
+
+[[https://gerrit.wikimedia.org/r/184904]]",1422056327,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Change 184904 had a related patch set uploaded (by Jforrester):
+Re-use Parsoid Varnishes for citoid too
+
+[[https://gerrit.wikimedia.org/r/184904]]
+
+#patch-for-review",1421252997,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Change 178419 abandoned by Catrope:
+Expose citoid through misc-web
+
+Reason:
+Forgot to abandon this. Gabriel said he'd work on caching infra for the entire services cluster, which they need for RESTbase, but which Citoid would then also use once it's done.
+
+[[https://gerrit.wikimedia.org/r/178419]]",1418914800,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Citoid !== Cite, they're totally different.
+
+However, Gabriel said he would work on setting up a services Varnish thing as part of setting up RESTbase, and Citoid could hitch a ride on that. So this ticket should have been marked as blocked on services, instead it was marked as blocked on ops by mistake.
+
+Under normal circumstances I would have attended SoS yesterday and would have known to file this correctly, but I wasn't able to make it.",1418914576,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Hello,
+
+So I am a bit unclear on this and the two tasks listed as blocked (T62768 and T67540) did not make it any more clear for me. So here's the question:
+
+We want citoid to be publicly available as an endpoint so that Cite and VisualEditor to directly query it, right ?
+
+I assume, Cite is this: http://www.mediawiki.org/wiki/Extension:Cite in which case I am wondering why a Mediawiki Extension can not query an internal endpoint (namely citoid.svc.eqiad.wmnet). I am not at all familiar with Cite so it might be javascript, served by Cite, that runs on the user's browser that does the querying at which point what this ticket asks make sense.
+
+Same thing goes for VisualEditor, I just want to clarify what/who will be doing the endpoint query. Is the situation different than Cite ? And if yes, how ? 
+
+As as side note and since I mentioned javascript, what about same origin policy ? Will that end up being a problem ?",1418914466,PHID-USER-xwxce3kpvsv54t735g7q,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+Expose the production citoid service publicly so we can start switching scripts over to use it,"Change 178419 had a related patch set uploaded (by Catrope):
+Expose citoid through misc-web
+
+[[https://gerrit.wikimedia.org/r/178419]]
+
+#patch-for-review",1418095569,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ie5f4kyk73zuc2topaj7,task_subcomment,NA
+"Show the VisualEditor toolbar/editor chrome as soon as VE scripts are loaded, rather than blocking on waiting for the content to load",,1417558133,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-snvwps4elfr6ehb3bg2z,task_description,resolved
+"Show the VisualEditor toolbar/editor chrome as soon as VE scripts are loaded, rather than blocking on waiting for the content to load","Change 192072 merged by jenkins-bot:
+Show the toolbar as soon as the target has been activated
+
+[[https://gerrit.wikimedia.org/r/192072]]",1425295969,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-snvwps4elfr6ehb3bg2z,task_subcomment,NA
+"Show the VisualEditor toolbar/editor chrome as soon as VE scripts are loaded, rather than blocking on waiting for the content to load","Change 192072 had a related patch set uploaded (by Esanders):
+Show the toolbar as soon as the target has been activated
+
+[[https://gerrit.wikimedia.org/r/192072]]
+
+#patch-for-review",1424515634,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-snvwps4elfr6ehb3bg2z,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"The Page options menu, which appears when the ""hamburger"" button is clicked, goes off-screen in RTL wikis.
+
+Screenshot with wrong display in Hebrew:
+https://commons.wikimedia.org/wiki/File:VisualEditorBug2a.png
+{F168546}
+
+Screenshot with correct display in English:
+https://commons.wikimedia.org/wiki/File:VisualEditorBug2b.png
+{F168548}
+
+(I have a vague recollection that I reported it once, but I cannot find it now. If somebody does find it, please mark this one as a dupe.)",1417531699,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_description,resolved
+VisualEditor page options menu goes off-screen in RTL wikis,My fix for this caused part of T98506.,1432467767,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Change 179581 merged by jenkins-bot:
+ClippableElement: Handle clipping with left edge
+
+[[https://gerrit.wikimedia.org/r/179581]]",1418762928,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Change 179565 abandoned by Amire80:
+Add noflip to oo-ui-popupToolGroup-left and -right
+
+Reason:
+Done better in I0c2d9800a1c0bdbe523c978307546ec205202681 .
+
+[[https://gerrit.wikimedia.org/r/179565]]",1418431819,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Change 179581 had a related patch set uploaded (by Bartosz Dziewoński):
+[WIP] ClippableElement: Handle clipping with left edge
+
+[[https://gerrit.wikimedia.org/r/179581]]
+
+#patch-for-review",1418431572,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"The real issue is that ClippableElement doesn't handle clipping with the left edge of browser window, only with the right edge.",1418430091,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Setting appropriate left and right values for oo-ui-popupToolGroup-left and oo-ui-popupToolGroup-right by adding noflip seems to fix the issue, but because I'm not an experienced oojs-ui dev, this needs review.
+
+For now I fixed this locally in he.wikipedia by adding:
+
+```
+.oo-ui-popupToolGroup-left > .oo-ui-toolGroup-tools {
+	left: 0;
+	right: auto;
+}
+```",1418426437,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+VisualEditor page options menu goes off-screen in RTL wikis,"Change 179565 had a related patch set uploaded (by Amire80):
+Add noflip to oo-ui-popupToolGroup-left and -right
+
+[[https://gerrit.wikimedia.org/r/179565]]
+
+#patch-for-review",1418424391,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tnxcsv7yi4nvi2fk6b6r,task_subcomment,NA
+Support legal requirements about publishing,"**Context**
+
+Adjust the publishing UI to meet the legal requirements for attribution.
+
+**Narrative**
+
+As a user, I can be informed about the terms under which my content gets published, so that I can just ignore them but no potential legal concerns are raised.  
+
+**Acceptance Criteria**
+
+  # When the user starts a translation, legal text is provided in the new panel dialog as shown in the design notes:
+  ## The legal text is similar to the one appearing in the wikitext editor (those links should point to the same place).
+  ## The only difference is that the ""By pressing the 'X' button"" part should match the name of the button in the UI for all languages
+  # We need to solve the case of users building a URL to access the translation view and thus bypassing the legal agreement, here is how we'll do that:
+  ## For users that started a translation (and have been exposed to the legal terms already) we should let them get into he translation at any time without any additional interruption.
+  ## For users that try to access the translation view directly for an article they have not explicitly started before, instead of directing them to the Translation view, they will be directed to the Translation Dashboard. There, the new translation dialog will be open and they will be able to start the translation with a single click (after reading the legal terms, as we all usually do).
+  # Read the acceptance criteria 1 again, and realise that this affects not only the ""new translation dialog"" but any entry point. Go and fix it for the red link entry point, and remember for future entry points to either (a) link to the Dashboard with the new translation fields pre-filled or (b) show the legal terms, or you may go to jail.
+
+**Design notes**
+
+The new translation dialog should incorporate the legal text, and we need to make sure that users are exposed at leas once (and prefereably only once) to it:
+
+{F17019}
+
+
+When a user tries to access another user's draft:
+- The draft content becomes non-interactive and translucent (opacity: 0.5) to indicate it is ""disabled"".
+- Publish button and saving indicator are hidden.
+- A dialog is shown in the warning area (view mockup below). It provides (a) a link to the translation author page, (b) a link to start a new translation (will go to the dashboard with the ""new translation"" dialog open and the fields pre-filled), (c) the legal text (note that the name of the button mentioned should match the current UI) and (d) a button to continue.
+- If the user continues, the above described elements would disappear and the user would be allowed to edit the draft.
+
+{F17098}",1417153277,PHID-USER-ttw4tpoosxc4pbmskrla,False,PHID-TASK-4res6cs3y6litn77e77o,task_description,resolved
+Support legal requirements about publishing,"Change 181863 merged by jenkins-bot:
+Change the cookie name for valid translation workflow
+
+[[https://gerrit.wikimedia.org/r/181863]]",1419593378,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 181863 had a related patch set uploaded (by Santhosh):
+Change the cookie name for valid translation workflow
+
+[[https://gerrit.wikimedia.org/r/181863]]
+
+#patch-for-review",1419588453,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 179105 merged by jenkins-bot:
+Make sure translator see license text even if use manually created URL
+
+[[https://gerrit.wikimedia.org/r/179105]]",1419252073,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"I adjusted the styling for the red interlanguage links dialog ([[ https://gerrit.wikimedia.org/r/#/c/179489/ | patchset]]) and the new translation dialog on the dashboard ([[https://gerrit.wikimedia.org/r/#/c/179498/ | patchset]]). 
+
+Screenshots:
+{F21011}
+{F21017}",1418407355,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"I adjusted the styling for the red interlanguage links dialog [[ https://gerrit.wikimedia.org/r/#/c/179489/ | patchset]]) and the new translation dialog on the dashboard ([[https://gerrit.wikimedia.org/r/#/c/179498/ | patchset]]). 
+
+Screenshots:
+{F21011}
+{F21017}",1418407345,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"I adjusted the styling for the red interlanguage links dialog ([[ URL | at ]] [[ https://gerrit.wikimedia.org/r/#/c/179489/ | patchset]]) and the new translation dialog on the dashboard ([[https://gerrit.wikimedia.org/r/#/c/179498/ | patchset]]). 
+
+Screenshots:
+{F21011}
+{F21017}",1418407332,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"I adjusted the styling for the red interlanguage links dialog at https://gerrit.wikimedia.org/r/#/c/179489/
+
+Screenshot:
+{F21011}",1418404447,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,Screenshot of CX dashboard with source selector automatically opened and prefilled with URL parameters {F20775},1418292534,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 179105 had a related patch set uploaded (by Santhosh):
+Make sure translator see license text even if use manually created URL
+
+[[https://gerrit.wikimedia.org/r/179105]]
+
+#patch-for-review",1418292390,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"> publishing only happens in the regular editor (the Translation View in this case).
+
+""Translation view"" doesn't sound like the regular editor.
+
+P.s.: Confirmed, it's not. Commented on that at https://www.mediawiki.org/wiki/Talk:Content_translation/Translation_view",1417616976,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"> publishing only happens in the regular editor (the Translation View in this case).
+
+""Translation view"" doesn't sound like the regular editor.",1417614467,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 176327 merged by jenkins-bot:
+Add the license agreement text to new translation entry points
+
+[[https://gerrit.wikimedia.org/r/176327]]",1417528352,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,@Nemo_bis: publishing only happens in the regular editor (the Translation View in this case). The purpose of this is to show the legal terms at the beginning of the process so that users can focus on translating on the Translation View without additional legal text or confirmation steps when publishing.,1417175486,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"This would be easier if ""publishing"" only happened in the regular editor: see for instance how VisualEditor sends you to action=edit (actually action=submit) when commuting an edit.",1417165968,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,New translation dialog with legal agreement: {F17064},1417165583,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+Support legal requirements about publishing,"Change 176327 had a related patch set uploaded (by Santhosh):
+Add the license agreement text to new translation dialog
+
+[[https://gerrit.wikimedia.org/r/176327]]
+
+#patch-for-review",1417164197,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4res6cs3y6litn77e77o,task_subcomment,NA
+VisualEditor not updating in beta labs,"As of this writing, http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version says beta labs is running a 20-hour old version of VE, and that seems to be accurate given that there are a few bugs that are fixed in master but not in beta.",1417039011,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-kok6e7cmusz47p2lyu46,task_description,resolved
+VisualEditor not updating in beta labs,"Seems there was some transient error that prevented Gerrit to merge the bot change automatically. Apparently due to some merge conflict.  I am not sure what went wrong but that is definitely fixed.
+
+The last bot change is https://gerrit.wikimedia.org/r/#/c/176867/ which updates the VisualEditor submodule in mediawiki/extensions.git to 6c4c340
+
+I have pulled the repo and did `git submodule update --init VisualEditor`, that points to the same commit 6c4c340.",1417552368,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+VisualEditor not updating in beta labs,"Seems the script python I wrote to update the VisualEditor repo is no more working / choking on something.  I haven't noticed this task until it has be pointed to me during the Releng weekly checkin.
+
+The related Jenkins job is `mwext-VisualEditor-sync-gerrit`  one might want to look at it to see what is happening and hopefully fix it.
+
+
+If it is quite tonight at home, I *might* be able to look at this issue.",1417542650,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+VisualEditor not updating in beta labs,"The commit on Beta Labs has now moved to d20cc324…; however, for ~ 24 hours 9dad03819… has been the latest merged commit. The Jenkins views on code updates to Beta Labs looks fine (notwithstanding https://integration.wikimedia.org/ci/view/Beta/job/beta-scap-eqiad/31718/console which happened much later). Odd.",1417229051,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+VisualEditor not updating in beta labs,"info-extensions-VisualEditor.json says:
+
+```
+{
+  ""head"": ""a14f88d80eec331a94cfdfc50da800c8fbc68ef3"",
+  ""remoteURL"": ""https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git"", 
+  ""branch"": ""a14f88d80eec331a94cfdfc50da800c8fbc68ef3"", 
+  ""headCommitDate"": ""1417037864"", 
+  ""headSHA1"": ""a14f88d80eec331a94cfdfc50da800c8fbc68ef3"", 
+  ""@directory"": ""/srv/mediawiki-staging/php-master/extensions/VisualEditor""
+}
+```",1417040928,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+VisualEditor not updating in beta labs,deployment-bastion:/srv/mediawiki-staging/php-master/extensions/VisualEditor is at git hash a14f88d which seems to match https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FVisualEditor and https://github.com/wikimedia/mediawiki-extensions-VisualEditor/commits/master,1417040089,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-kok6e7cmusz47p2lyu46,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"We are getting ready to integrate Parsoid with RESTBase. This task tracks our progress and what's left to do.
+
+Generally, we need a way to communicate multiple mime entities both in POST requests to Parsoid, and in responses from Parsoid back to RESTBase. We could use [RFC 2387](https://tools.ietf.org/html/rfc2387) or [RFC 2388](https://www.ietf.org/rfc/rfc2388.txt), but this seems to be a bit cumbersome especially for the response part. Instead, we can just use a simple JSON encoding with a structure that's otherwise basically identical to MIME.
+
+The downside of using JSON is possibly efficiency (quite a bit more escaping going on, especially for HTML-in-JSON). However, we could address that later by optionally using a binary encoding like [msgpack](http://msgpack.org/) without changing the message structure itself.
+
+Another option to consider would be to flatten the structure by using names like `original.html`. This would make it easy to encode the same message as `multipart/related`.
+
+== Implementation notes ==
+
+- Parsoid: Slightly simpler format done & deployed. Needs to be updated to indicate the mime types as documented above.
+- RESTBase: Prototype implementation.
+  - should pass to Parsoid:
+    - previous revision's HTML + data-parsoid OnEdit
+    - current revision's HTML + data-parsoid OnDependencyChange
+- Parsoid WIP implementation: https://gerrit.wikimedia.org/r/#/c/165685/
+- RESTBase to be done
+",1416964657,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_description,resolved
+RESTBase / Parsoid integration - waiting for parsoid deploy,Resolved by Parsoid deploy yesterday.,1424194514,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Latest iteration of the RESTBase transform API: https://github.com/wikimedia/restbase/pull/173
+
+Testing revealed an issue with selser, possibly on the Parsoid side: T89411",1423784954,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,See https://github.com/wikimedia/restbase/blob/master/specs/mediawiki/v1/content.yaml for the content API v1 spec in development.,1423596265,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,This task is getting rather unwieldy.  I'm going to split it up into better-digestible subtasks.,1422989107,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Notes from conversation with @gwicke:
+
+* We don't want the client to pass in `original` -- RESTBase will always find that on its own (e.g. from storage)
+* We don't need to allow the client to specify the content type //yet//
+* Assume client is always using the latest spec for whichever Content-Type they're using
+* Client //might// know the specific Content-Type, but we shouldn't break if we can fallback to a functioning default",1422922493,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, your example is from the Parsoid v2 API, while the RESTBase transform API can just use flat posts. We make the assumption that the transform API does not need to deal with mis-matches in the posted content, as the use cases this is intended for (VE, edit widgets etc) aren't long-running & don't involve storage.
+
+`multipart/form-data` does support per-field content-type headers, but by default those are not set afaik.",1422920885,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"It's from the discussion above:
+
+{F34542}",1422919943,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, is there a use case for this? The discussion about multipart/form-data is about the RESTBase API, not the Parsoid v2 API.",1422919683,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"What is the multipart/form-data counterpart to the following application/json?
+
+```
+{
+    ""html"": {
+        ""headers"": {
+            ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+        },
+        ""body"": ""<html>The modified HTML</html>""
+    },
+    ""original"": {
+        ""revid"": 12345,
+        ""wikitext"": {
+            ""headers"": {
+                ""content-type"": ""text/plain;profile=mediawiki.org/specs/wikitext/1.0.0""
+            },
+            ""body"": ""the original wikitext""
+        },
+        ""html"": {
+            ""headers"": {
+                ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+            },
+            ""body"": ""the original HTML""
+        },
+        ""data-parsoid"": {
+            ""headers"": {
+                ""content-type"": ""application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1""
+            },
+            ""body"": {
+                ""ids"": {}
+            }
+        }
+    }
+}
+```
+
+
+Should each multipart field contain JSON?  For example:
+
+```--------------------------d0f6b49b1b041887
+Content-Disposition: form-data; name=""html""; filename=""html""
+Content-Type: application/json
+
+{
+    ""headers"": {
+        ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+    },
+    ""body"": ""<html>The modified HTML</html>""
+}
+
+--------------------------d0f6b49b1b041887
+Content-Disposition: form-data; name=""original""; filename=""original""
+Content-Type: application/json
+
+{
+    ""revid"": 12345,
+    ""wikitext"": {
+        ""headers"": {
+            ""content-type"": ""text/plain;profile=mediawiki.org/specs/wikitext/1.0.0""
+        },
+        ""body"": ""the original wikitext""
+    },
+    ""html"": {
+        ""headers"": {
+            ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+        },
+        ""body"": ""the original HTML""
+    },
+    ""data-parsoid"": {
+        ""headers"": {
+            ""content-type"": ""application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1""
+        },
+        ""body"": {
+            ""ids"": {}
+        }
+    }
+}
+
+--------------------------d0f6b49b1b041887--
+```
+",1422919149,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,This is what Parsoid uses: https://github.com/wikimedia/parsoid/blob/master/lib/mediawiki.ApiRequest.js#L224,1422657845,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Great, thanks!",1422657813,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#1005304, @Jdouglas wrote:
+> Can you point me to the docs on how to get Wikitext from the MW API?
+
+[action=raw](https://www.mediawiki.org/wiki/Manual:Parameters_to_index.php#Raw) ought to help",1422657749,PHID-USER-hxwwywcyzpooynxuo7a2,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> The other missing bit is that we currently don't actually fetch wikitext from the MW API. We need to do so (and perhaps store it) for proper html2wt support.
+
+Can you point me to the docs on how to get Wikitext from the MW API?",1422657577,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#980780, @Jdouglas wrote:
+> * accept a `multipart/form-data` body rather than JSON
+
+We could also accept both.
+
+The other missing bit is that we currently don't actually fetch wikitext from the MW API. We need to do so (and perhaps store it) for proper html2wt support.",1422137549,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Ok, so it sounds like we need only augment the `POST /{domain}/v1/transform/<html|wt>/to/html` endpoint to:
+
+* allow an optional `bodyOnly` field
+* accept a `multipart/form-data` body rather than JSON
+
+Sound right?",1421362618,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, I think we need to always request the full HTML from Parsoid, so that our storage has the full version. If bodyOnly was requested in the POST, then we should probably pluck out the body with a regexp in restbase.
+
+Regarding `multipart/form-data` vs. `application/json`: Should we promote the former for the transform API?",1421362232,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, I think we need to always request the full HTML from Parsoid, so that our storage has the full version. If bodyOnly was requested in the POST, then we should probably pluck out the body with a regexp in restbase.
+
+Regarding `multipart/form-data` vs. `application/json`: Should we promote the former for now?",1421362215,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#976719, @Jdouglas wrote:
+>> test whether the original content was indeed passed to parsoid
+> 
+> @gwicke For specification purposes, can you define ""original"" in this context?
+> 
+> Does it always mean ""penultimate"" with respect to the state of the wiki behind `{domain}`?
+
+On second thought, does it mean ""the revision for which new changes are being submitted""?",1421361979,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Does the following look correct?
+
+**User -> RESTBase:**
+
+```
+{
+  method: 'post',
+  uri: '/{domain}/v1/transform/<html|wt>/to/html',
+  headers: {
+    'content-type': 'application/json',
+  },
+  body: {
+    content: 'Hello, world!',
+    bodyOnly: true,
+  },
+}
+```
+
+**RESTBase -> Parsoid:**
+
+```
+{
+  method: 'post',
+  uri: 'http://parsoid-lb.eqiad.wikimedia.org/{domain}/FAKE_PAGE_NAME',
+  headers: {
+    'content-type': 'application/x-www-form-urlencoded',
+  },
+  body: '$BODY',
+}
+```
+
+
+Where `$BODY` is the form-urlencoded representation of:
+
+```
+{
+  oldid: 123, // optional
+  html: 'Hello, world!',
+  body: true, // optional
+}
+```",1421360972,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Does the following look correct?
+
+**User -> RESTBase:**
+
+```
+{
+  method: 'post',
+  uri: '/{domain}/v1/transform/<html|wt>/to/html',
+  headers: {
+    'content-type': 'application/json',
+  },
+  body: {
+    content: 'Hello, world!',
+    bodyOnly: true,
+  },
+}
+```
+
+**RESTBase -> Parsoid:**
+
+```
+{
+  method: 'post',
+  uri: 'http://parsoid-lb.eqiad.wikimedia.org/{domain}/{page}',
+  headers: {
+    'content-type': 'application/x-www-form-urlencoded',
+  },
+  body: '$BODY',
+}
+```
+
+
+Where `$BODY` is the form-urlencoded representation of:
+
+```
+{
+  oldid: 123, // optional
+  html: 'Hello, world!',
+  body: true, // optional
+}
+```",1421360786,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#977393, @Jdouglas wrote:
+>> Anyone want to do a final check of the tests to verify they cover the scope of this task?
+> 
+> We're not quite there yet.  The [[ https://www.mediawiki.org/wiki/Parsoid/API | Parsoid API ]] accepts a `body` flag that reduces the scope of the response.
+> 
+> @GWicke do you know who is using this feature?  
+
+AFAIK this is currently used by Flow, likely also VE.
+
+> Is it something RESTBase should provide via its own API?
+
+Yes. We talked about supporting a plain POST body with the html/wt in 'content' and optional other fields like a 'bodyOnly' boolean. I would vote for using this option in the transform API, as it is easy enough and more efficient for binary content when using `multipart/form-data` encoding. We can always add JSON as an option later.",1421275798,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> Anyone want to do a final check of the tests to verify they cover the scope of this task?
+
+We're not quite there yet.  The [[ https://www.mediawiki.org/wiki/Parsoid/API | Parsoid API ]] accepts a `body` flag that reduces the scope of the response.
+
+@GWicke do you know who is using this feature?  Is it something RESTBase should provide via its own API?  If so, how will it effect storage?  We might not want to store the `body.innerHTML`, but instead store the entire content.  The drawback to this is that we'll have to replicate some of the same DOM parsing that Parsoid currently handles to be able to subset the content on demand.",1421272316,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> test whether the original content was indeed passed to parsoid
+
+@gwicke For specification purposes, can you define ""original"" in this context?
+
+Does it always mean ""penultimate"" with respect to the state of the wiki behind `{domain}`?",1421260909,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,Strictly speaking https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/ondemand.js#L87 does not really test whether the original content was indeed passed to parsoid. Maybe we could let parsoid emit a header if it received the original properly. We could then assert that header in the response.,1421170310,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I think we're pretty close to marking this one as done.  Anyone want to do a final check of the tests to verify they cover the scope of this task?
+
+//On-demand generation of HTML and data-parsoid://
+
+https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/ondemand.js
+
+//html2wt conversion support://
+
+https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/transform.js",1421107926,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I think we're pretty close to ready to close this task.  Anyone want to do a final check of the tests to verify they cover the scope of this task?
+
+//On-demand generation of HTML and data-parsoid://
+
+https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/ondemand.js
+
+//html2wt conversion support://
+
+https://github.com/wikimedia/restbase/blob/3412329b102e69bb25482d9f21a74151bd00abdd/test/features/parsoid/transform.js",1421107412,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"The transform endpoint is now functioning: https://github.com/wikimedia/restbase/pull/98
+
+After #98, is there anything else needed for T75955?
+
+Answer: yes: https://coveralls.io/files/412841510#L93",1420502909,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"The transform endpoint is now functioning: https://github.com/wikimedia/restbase/pull/98
+
+After #98, is there anything else needed for T75955?",1420499740,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,The transform endpoint is now functioning: https://github.com/wikimedia/restbase/pull/98,1420499685,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Oh, my mistake.  The new patch already supports `POST parsoid/v2/{domain}/wt`.",1419981101,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, basically title and oldid are optional, so both `POST parsoid/v2/{domain}/wt/{title}` and `POST parsoid/v2/{domain}/wt` should work. If the request without title doesn't work in parsoid right now, then we could work around it by inventing one like 'Main_Page' for now. IIRC that's what Parsoid used to do as well if the title is missing.
+
+Edit: Parsoid [uses the configured mainpage for the wiki](https://github.com/wikimedia/parsoid/blob/1f43a268b70cf4a91b4e982e328e9dbfd0889f96/lib/mediawiki.parser.environment.js#L248), which happens to be 'Main Page' for enwiki, but differs for other languages.",1419981080,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas, basically title and oldid are optional, so both `POST parsoid/v2/{domain}/wt/{title}` and `POST parsoid/v2/{domain}/wt` should work. If the request without title doesn't work in parsoid right now, then we could work around it by inventing one like 'Main_Page' for now. IIRC that's what Parsoid used to do as well if the title is missing.",1419980835,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"When there's no title or revision, i.e. `POST /{domain}/v1/transform/html/to/wt`, what should be the Parsoid request URL?
+
+`POST parsoid/v2/{domain}/wt/{title}/{oldid}`
+
+Parsoid appears to allow gibberish:
+
+`POST parsoid/v2/{domain}/wt/___NOT_A_REAL_TITLE_1231___/`
+
+Should we designate a special placeholder title?  Or should we update Parsoid to respond to `POST parsoid/v2/{domain}/wt`?",1419980679,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"When there's no title or revision, i.e. `POST /{domain}/v1/transform/html/to/wt`, what should be the Parsoid request URL?
+
+`POST parsoid/v2/{domain}/wt/{title}/{oldid}`",1419980564,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,{icon thumbs-up},1419966615,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: I think we can always wrap things into a full request on the restbase end, and just add the latest configured parsoid mime type if we didn't receive any from the client. So we can perhaps just strike this as a parsoid requirement.",1419967245,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: I think we can always wrap things into the a full request on the restbase end, and just add the latest configured parsoid mime type if we didn't receive any from the client. So we can perhaps just strike this as a parsoid requirement.",1419966212,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: I think we can always wrap things into the a full request on the restbase end, and just add the latest configured parsoid mime type if we didn't receive any from the client.",1419966184,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@gwicke:
+
+> If the modified html is just a string, then Parsoid is expected to assume that it's in the latest html version.
+
+Does this refer to a POST to //parsoid/v2/{domain}/wt/{title}/{oldid}// with a request body containing raw HTML?",1419965826,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@gwicke:
+
+> If the modified html is just a string, then Parsoid is expected to assume that it's in the latest html version.If the modified html is just a string, then Parsoid is expected to assume that it's in the latest html version.
+
+Does this refer to a POST to //parsoid/v2/{domain}/wt/{title}/{oldid}// with a request body containing raw HTML?",1419965809,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,See proposed tests here: https://github.com/wikimedia/restbase/pull/98,1419900797,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Change 165685 merged by Jdouglas:
+API v2 parsing and serialization routes
+
+[[https://gerrit.wikimedia.org/r/165685]]",1419898786,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: To be fair, JSON schema validation is not usually happening for free just by having stronger typing.",1419896272,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Understandable, considering we're operating without a type system. :]",1419896146,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,@jdouglas I think validation is fairly embryonic at this point. Definitely agreed on 400 being better than 500.,1419895777,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,Gotcha. Does Parsoid have any infrastructure for validation? A 400 with a reason might be more informative to an erroneous client than a 500 with an obscure es6-shim stack trace.,1419895327,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: Passing in data-parsoid without ids in the body could be considered a bug in the client worth highlighting. If that passed unnoticed, the result would likely be wikitext corruption in edits, which would make many people unhappy. If we send the 'original' object, then it should contain both html *and* a valid data-parsoid attribute, both from storage. 
+
+Parsoid also needs to support html2wt conversion without the 'original' object (for new page creation for example). That might be a simpler mode to test for the first iteration.",1419894921,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Here's the source of the problem: https://github.com/wikimedia/parsoid/blob/04721c235f9cc6d4ffdca8418e73d602aecfebba/lib/mediawiki.DOMUtils.js#L1963
+
+Would it be better to allow for an id-less body?
+
+e.g.
+
+```
+Object.keys( dp.ids || {} ).forEach(function ( key ) {
+```",1419890893,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"This works for `wt` when I replace `""body"": {}"" with the following:
+
+```
+        ""body"": {
+            ""counter"": 1,
+            ""ids"": {
+                ""mwAA"": {
+                    ""dsr"": [
+                        0,
+                        949,
+                        0,
+                        0
+                    ]
+                },
+                ""mwAQ"": {
+                    ""dsr"": [
+                        928,
+                        949,
+                        0,
+                        0
+                    ]
+                }
+            }
+        }
+```
+
+EDIT: The key is having `body.ids` -- at least `""body"": { ""ids"": {} }`",1419890072,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"This works for `wt` when I replace `""body"": {}"" with the following:
+
+```
+        ""body"": {
+            ""counter"": 1,
+            ""ids"": {
+                ""mwAA"": {
+                    ""dsr"": [
+                        0,
+                        949,
+                        0,
+                        0
+                    ]
+                },
+                ""mwAQ"": {
+                    ""dsr"": [
+                        928,
+                        949,
+                        0,
+                        0
+                    ]
+                }
+            }
+        }
+```
+
+The key is having `body.ids` -- at least `""body"": { ""ids"": {} }`",1419890060,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"This works for `wt` when I replace `""body"": {}"" with the following:
+
+```
+        ""body"": {
+            ""counter"": 1,
+            ""ids"": {
+                ""mwAA"": {
+                    ""dsr"": [
+                        0,
+                        949,
+                        0,
+                        0
+                    ]
+                },
+                ""mwAQ"": {
+                    ""dsr"": [
+                        928,
+                        949,
+                        0,
+                        0
+                    ]
+                }
+            }
+        }
+```",1419889456,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"This appears to work for `pagebundle` in place of `wt`.
+
+```
+curl -s -H ""Content-Type: application/json"" -X POST -d @T75955.json localhost:8000/v2/en.wikipedia.org/pagebundle/Main_Page/1
+```
+
+```
+{
+    ""data-parsoid"": {
+        ""body"": {
+            ""counter"": 1,
+            ""ids"": {
+                ""mwAA"": {
+                    ""dsr"": [
+                        0,
+                        949,
+                        0,
+                        0
+                    ]
+                },
+                ""mwAQ"": {
+                    ""dsr"": [
+                        928,
+                        949,
+                        0,
+                        0
+                    ]
+                }
+            }
+        },
+        ""headers"": {
+            ""content-type"": ""application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1""
+        }
+    },
+    ""html"": {
+        ""body"": ""<!DOCTYPE html>\n<html prefix=\""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/\"" about=\""http://en.wikipedia.org/wiki/Special:Redirect/revision/12345\""><head prefix=\""mwr: http://en.wikipedia.org/wiki/Special:Redirect/\""><meta property=\""mw:articleNamespace\"" content=\""0\""/><link rel=\""dc:replaces\"" resource=\""mwr:revision/12342\""/><meta property=\""dc:modified\"" content=\""2002-02-16T19:00:49.000Z\""/><meta about=\""mwr:user/0\"" property=\""dc:title\"" content=\""210.55.230.17\""/><link rel=\""dc:contributor\"" resource=\""mwr:user/0\""/><meta property=\""mw:revisionSHA1\"" content=\""1ec7fece702a00b9d99c0e848eea8c524d12fe3f\""/><meta property=\""dc:description\"" content=\""*\""/><meta property=\""mw:parsoidVersion\"" content=\""0\""/><link rel=\""dc:isVersionOf\"" href=\""//en.wikipedia.org/wiki/Main_Page\""/><title>Main_Page</title><base href=\""//en.wikipedia.org/wiki/\""/><link rel=\""stylesheet\"" href=\""//en.wikipedia.org/w/load.php?modules=mediawiki.legacy.commonPrint,shared|mediawiki.skinning.elements|mediawiki.skinning.content|mediawiki.skinning.interface|skins.vector.styles|site|mediawiki.skinning.content.parsoid&amp;only=styles&amp;debug=true&amp;skin=vector\""/></head><body id=\""mwAA\"" lang=\""en\"" class=\""mw-content-ltr sitedir-ltr ltr mw-body mw-body-content mediawiki\"" dir=\""ltr\""><p id=\""mwAQ\"">the original wikitext</p></body></html>"",
+        ""headers"": {
+            ""content-type"": ""text/html;profile=mediawiki.org/specs/html/1.0.0""
+        }
+    }
+}
+```",1419887881,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I converted the `POST parsoid/v2/{domain}/wt/{title}/{oldid}` example above to a JSON file, and attempted to run it locally, but something went wrong:
+
+
+```
+$ curl -H ""Content-Type: application/json"" -X POST -d @T75955.json localhost:8000/v2/en.wikipedia.org/wt/Main_Page/1
+Cannot call method on undefined
+TypeError: Cannot call method on undefined
+    at Object.ES.CheckObjectCoercible (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:152:17)
+    at Object.ES.ToObject (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:164:26)
+    at Function.Object.keys (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:905:38)
+    at Object.DU.applyDataParsoid (/home/jdouglas/code/parsoid/lib/mediawiki.DOMUtils.js:1958:10)
+    at Promise.then.timeout.then.apiUtils.jsonResponse.wikitext.headers.content-type (/home/jdouglas/code/parsoid/api/routes.js:275:7)
+    at /home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1220:20
+    at Object._onImmediate (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1177:28)
+    at processImmediate [as _immediateCallback] (timers.js:345:15)
+```
+
+Any debugging pointers?
+
+{F25608}
+
+EDIT: It works if I s/wt/html/g in the URL.",1419887417,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I converted the `POST parsoid/v2/{domain}/wt/{title}/{oldid}` example above to a JSON file, and attempted to run it locally, but something went wrong:
+
+
+```
+$ curl -H ""Content-Type: application/json"" -X POST -d @T75955.json localhost:8000/v2/en.wikipedia.org/wt/Main_Page/1
+Cannot call method on undefined
+TypeError: Cannot call method on undefined
+    at Object.ES.CheckObjectCoercible (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:152:17)
+    at Object.ES.ToObject (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:164:26)
+    at Function.Object.keys (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:905:38)
+    at Object.DU.applyDataParsoid (/home/jdouglas/code/parsoid/lib/mediawiki.DOMUtils.js:1958:10)
+    at Promise.then.timeout.then.apiUtils.jsonResponse.wikitext.headers.content-type (/home/jdouglas/code/parsoid/api/routes.js:275:7)
+    at /home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1220:20
+    at Object._onImmediate (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1177:28)
+    at processImmediate [as _immediateCallback] (timers.js:345:15)
+```
+
+Any debugging pointers?
+
+{F25608}",1419887280,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"I converted the `POST parsoid/v2/{domain}/wt/{title}/{oldid}` example above to a JSON file, and attempted to run it locally, but something went wrong:
+
+
+```
+$ curl -H ""Content-Type: application/json"" -X POST -d @T75955.json localhost:8000/v2/en.wikipedia.org/wt/Main_Page/1
+Cannot call method on undefined
+TypeError: Cannot call method on undefined
+    at Object.ES.CheckObjectCoercible (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:152:17)
+    at Object.ES.ToObject (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:164:26)
+    at Function.Object.keys (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:905:38)
+    at Object.DU.applyDataParsoid (/home/jdouglas/code/parsoid/lib/mediawiki.DOMUtils.js:1958:10)
+    at Promise.then.timeout.then.apiUtils.jsonResponse.wikitext.headers.content-type (/home/jdouglas/code/parsoid/api/routes.js:275:7)
+    at /home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1220:20
+    at Object._onImmediate (/home/jdouglas/code/parsoid/node_modules/es6-shim/es6-shim.js:1177:28)
+    at processImmediate [as _immediateCallback] (timers.js:345:15)
+```
+
+Any debugging pointers?",1419887206,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: Yes, that should work. See https://www.mediawiki.org/wiki/Parsoid/Setup#Manual_installation_on_Linux_or_Mac_OS_X
+
+Basic summary:
+
+```
+# clone parsoid
+git clone ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid
+
+cd parsoid
+
+# check out the patch with the git commandline shown in gerrit:
+git fetch ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid refs/changes/85/165685/13 && git checkout FETCH_HEAD
+npm install
+
+node api/server
+```
+
+This should bring up parsoid locally. The wikipedia domains are all configured by default.",1419886351,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: Yes, that should work. See https://www.mediawiki.org/wiki/Parsoid/Setup#Manual_installation_on_Linux_or_Mac_OS_X
+
+Basic summary:
+
+```
+# clone parsoid
+git clone ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid
+
+cd parsoid
+
+# check out with the git commandline shown in gerrit:
+git fetch ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid refs/changes/85/165685/13 && git checkout FETCH_HEAD
+npm install
+
+node api/server
+```
+
+This should bring up parsoid locally. The wikipedia domains are all configured by default.",1419886292,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@jdouglas: Yes, that should work. See https://www.mediawiki.org/wiki/Parsoid/Setup#Manual_installation_on_Linux_or_Mac_OS_X
+
+Basic summary:
+
+```bash
+# clone parsoid
+git clone ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid
+
+cd parsoid
+
+# check out with the git commandline shown in gerrit:
+git fetch ssh://<user>@gerrit.wikimedia.org:29418/mediawiki/services/parsoid refs/changes/85/165685/13 && git checkout FETCH_HEAD
+npm install
+
+node api/server
+```
+
+This should bring up parsoid locally. The wikipedia domains are all configured by default.",1419886278,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Is it feasible to run this Parsoid patch in my local dev environment so that I can develop against it?
+
+EDIT: I found instructions [[ https://github.com/wikimedia/cassandra-codec/pull/9#issuecomment-68279450 | here ]].",1419886395,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Is it feasible to run this Parsoid patch in my local dev environment so that I can develop against it?
+
+EDIT: I found instructions [[ https://github.com/wikimedia/cassandra-codec/pull/9#issuecomment-68279450 | here ]].
+```",1419886375,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,Is it feasible to run this Parsoid patch in my local dev environment so that I can develop against it?,1419885989,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,Is it feasible to run this patch in my local dev environment so that I can develop against it?,1419885973,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,I updated the patch with that.,1419295340,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@arlolra: See my review there.
+
+As you noted in your response, we also need a way to request more targeted updates. This includes the current wt2html updates (re-render templates or re-render images), but we should use a mechanism that can also cover more refined requests in the future: 
+
+- re-sanitization of HTML / upgrade of HTML spec
+- update of transclusions affected by certain templates only
+- update of specific images only
+
+A key in the request seems to make most sense. Perhaps something like this?
+
+```
+{
+   update: {
+      templates: true,
+      images: false,
+      spec: true
+   },
+   original: { ... }
+}
+```
+
+Not all of these need to be set all the time, only the actually requested updates could be set to a truish value. In the future, we could add an object value with finer-grained options instead to support targeted template / image updates.",1419281047,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> Do you mean html2wt or wt2html in the issue summary?
+
+wt2html
+
+> It reuses template expansions or images, depending which of the two triggered the update. The reason for the update is relayed in an x-parsoid header currently.
+
+I was thinking it only did that with the `previous` revision data but I guess it's both then
+https://gerrit.wikimedia.org/r/#/c/165685/12/api/routes.js
+
+can you review https://gerrit.wikimedia.org/r/#/c/165685/ when you get a chance?",1419274370,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#937200, @Arlolra wrote:
+> @Gwicke: In the example responses from Parsoid, you'll showing the pagebundle but the route examples say `/html/`.
+
+Do you mean html2wt or wt2html in the issue summary?
+
+>> For a no-cache request, RESTBase instead first checks whether the *current* revision is found in storage. If it is, it sends the data for that in the original key:
+> 
+> what, if anything, does Parsoid do with the `original` data.
+
+It reuses template expansions or images, depending which of the two triggered the update. The reason for the update is relayed in an x-parsoid header currently.",1419273092,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#937200, @Arlolra wrote:
+> @Gwicke: In the example responses from Parsoid, you'll showing the pagebundle but the route examples say `/html/`.
+
+Do you mean html2wt or wt2html in the issue summary?
+
+>> For a no-cache request, RESTBase instead first checks whether the *current* revision is found in storage. If it is, it sends the data for that in the original key:
+> 
+> what, if anything, does Parsoid do with the `original` data.
+
+It reuses template expansions or images, depending which of the two triggered the update. The reasion for the update is relayed in an x-parsoid header currently.",1419273071,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> what, if anything, does Parsoid do with the original data.
+
+if the original data contains the wikitext source, then parsoid won't have to fetch it. I'll assume you meant that",1419046452,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@Gwicke: In the example responses from Parsoid, you'll showing the pagebundle but the route examples say `/html/`.
+
+Also, in the cache scenario (wt2html), we try to reuse the expansions from the previous revision, as in,
+https://gerrit.wikimedia.org/r/#/c/165685/10/api/routes.js
+
+but, for no-cache,
+
+> For a no-cache request, RESTBase instead first checks whether the *current* revision is found in storage. If it is, it sends the data for that in the original key:
+
+what, if anything, does Parsoid do with the `original` data.",1419027930,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Makes sense, thanks!",1418949597,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#934492, @Jdouglas wrote: 
+> 1. What does `original` mean -- is it the penultimate revision of the content in question?  Is it the first revision of the content?  What's the context of originality?
+
+'original' means the data for the edit revision the edit was based on (if title and oldid is specified, and if we had that in restbase).
+
+> 1. Why is so much data being sent to Parsoid?  Does Parsoid need two HTML representations, plus a wikitext representation, plus a data-parsoid representation?  Or does this example show the different options for the types of source data?
+
+Parsoid does a lot of clever tricks to keep the conversion clean and make it fast. One is to diff the modified HTML against the original & using the original wikitext for portions of the DOM that weren't modified (based on offset information similar to a source map from data-parsoid). The predecessor revision is used to speed up parsing of new versions by plucking out some bits of content (template expansions, image thumbs) & reusing them without going off and generating them from scratch using the PHP API.
+
+> 1. What is the minimum request that could be sent to Parsoid through this endpoint?
+> 
+> My goal is to be able to document this API , part of which means defining the schemas for the requests and responses, so it will help me to understand exactly what's going on.
+
+We could only send the modified content, but then diffs will be dirty and the performance will suffer.",1418949428,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@gwicke Can you break down the request described above?
+
+```
+POST parsoid/v2/{domain}/{title}/wt
+
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: '<html>The modified HTML</html>'
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+
+I have several questions, most of which are probably due to my lack of knowledge about how Parsoid works.
+
+1. What does `original` mean -- is it the penultimate revision of the content in question?  Is it the first revision of the content?  What's the context of originality?
+1. Why is so much data being sent to Parsoid?  Does Parsoid need two HTML representations, plus a wikitext representation, plus a data-parsoid representation?  Or does this example show the different options for the types of source data?
+1. What is the minimum request that could be sent to Parsoid through this endpoint?
+
+My goal is to be able to document this API , part of which means defining the schemas for the requests and responses, so it will help me to understand exactly what's going on.",1418949159,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Right now these POST requests are completely ephemeral.
+
+We *could* eventually consider caching some responses based a request hash for a limited time (and return that hash in some header), so that the result could be dereferenced shortly later using just the hash. That could be handy for features like VisualEditor's speculative html2wt conversion, which is currently implemented using custom memcached logic. But that's really not needed in the first iteration IMHO.",1418947862,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@Jdouglas I think it would have to be ephemeral. You could hash the content to create an identifier but if it contained a template or whatnot, it wouldn't be clear when that needs expunging.",1418946004,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"If the optional title is omitted, does that mean the converted data is ephemeral, or would we want to generate some kind of identifier so that the content can be stored for future access?",1418945157,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Re POST requests, I think we could perhaps use the following:
+
+- html2wt without selser: `POST /v2/{domain}/wt/{title}` (title optional)
+- html2wt with selser: `POST /v2/{domain}/wt/{title}/{oldid}`
+- html2html or wt2html: `POST /v2/{domain}/html/{title}/{oldid}` (title and oldid optional)",1418944107,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#853672, @Jdouglas wrote:
+>> html2wt conversion support
+>> 
+>> Request to RESTBase: POST /v1/{domain}/transform/html/to/wt
+>>
+>> RESTBase retrieves the original html, wikitext & data-parsoid from storage & POSTs it to Parsoid:
+>>
+>> POST parsoid/v2/{domain}/{title}/wt
+> 
+> How does RESTBase determine the title of the content?
+
+@jdouglas, @arlolra: good question. Maybe flipping the order would actually make more sense for Parsoid? It would still provide a list of formats, and it does not require knowledge of the oldid.
+
+Example: `POST parsoid/v2/{domain}/wt/{title}`
+
+Alternatively, we could figure everything but the domain out by POSTing to `/v2/{domain}/`.",1418855954,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#853672, @Jdouglas wrote:
+>> html2wt conversion support
+>> 
+>> Request to RESTBase: POST /v1/{domain}/transform/html/to/wt
+>>
+>> RESTBase retrieves the original html, wikitext & data-parsoid from storage & POSTs it to Parsoid:
+>>
+>> POST parsoid/v2/{domain}/{title}/wt
+> 
+> How does RESTBase determine the title of the content?
+
+@jdouglas, @arlolra: good question. Maybe flipping the order would actually make more sense for Parsoid? It would still provide a list of formats, and it does not require knowledge of the oldid.",1418855783,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"> html2wt conversion support
+> 
+> Request to RESTBase: POST /v1/{domain}/transform/html/to/wt
+>
+> RESTBase retrieves the original html, wikitext & data-parsoid from storage & POSTs it to Parsoid:
+>
+> POST parsoid/v2/{domain}/{title}/wt
+
+How does RESTBase determine the title of the content?",1418837594,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"If the title isn't provided, what do we supply in the POST to Parsoid?
+
+> POST parsoid/v2/{domain}/{title}/wt
+
+Or would there be a different URL for arbitrary html conversion in Parsoid?",1418320854,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#842132, @Jdouglas wrote:
+> In the //html2wt conversion support// section, how do we identify the article that the user wants to convert?  Should we add a //{title}// to the url?
+
+Since it's a POST anyway, we could also just ask for an optional `title` and `revision` in the post data. That way the same URL will work for random HTML (which is not associated with any particular page / revision), and for edits to existing content.",1418320408,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"In the //html2wt conversion support// section, how do we identify the article that the user wants to convert?  Should we add a //{title}// to the url?
+
+> Request to RESTBase: POST /v1/{domain}/transform/html/to/wt",1418319272,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: We could add a 'version' property which has the link to the spec version, which we can then prefix with text/html and application/json to get a complete mime type for each respective bit. On the way back we'll then need to undo that. When we re-sanitize HTML, we'll also need to update the version numbers on data-mw and data-parsoid, even if those weren't actually changed in any way. Or, alternatively, we could use the maximum version for a combined version as you propose when sending the different bits of content back to Parsoid.
+
+This is all more complexity than I'd like to have. It would really be simpler if you could just give us a complete mime type for each bit of content, the same way you would set it when asked for one of those formats only (for non-pagebundle formats). We can then set that mime type in responses to clients asking for HTML, and send it back to you later, without having to track special details about the parsoid version scheme.",1418283852,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: We could add a 'version' property which has the link to the spec version, which we can then prefix with text/html and application/json to get a complete mime type for each respective bit. On the way back we'll then need to undo that. When we re-sanitize HTML, we'll also need to update the version numbers on data-mw and data-parsoid, even if those weren't actually changed in any way. Or, alternatively, we could use the maximum version for a combined version as you propose when sending the different bits of content back to Parsoid.
+
+This is all more complexity than I'd like to have. It would really be simpler if you could just give me a complete mime type for each bit of content. I can then set that mime type in responses to clients asking for HTML, and send it back to you later, without having to track special details about the parsoid version scheme.",1418283716,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: We could add a 'version' property which has the link to the spec version, which we can then prefix with text/html and application/json for the respective bits. We'll also need to indicate the mime type in mixed content we send to parsoid, for each part. To me as a user it's actually simpler if you just give me a complete mime type for each bit of content. I can then just send that back to you later, without knowing much about custom mime type massaging etc.",1418283201,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: We could add a 'version' property which has the link to the spec version, which we can then prefix with text/html and application/json for the respective bits. We'll also need to send that in stuff we send to parsoid, for each part. To me as a user it's actually simpler if you just give me a complete mime type for each bit of content. I can then just send that back to you later, without knowing much about custom mime type massaging etc.",1418283152,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Right, we need to know the version number, but, I was just wondering if it needs to be part of every resource in the v2 page bundle, i.e. you can add a html-version property to the v2 page bundle, for example.",1418280934,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"@ssastry: When we load some old HTML from storage, we need to know
+
+1) whether this HTML needs to be re-sanitized after discovering that sanitization issue in the Parsoid version that emitted DOM spec 1.0.0, and
+2) whether we need to update the HTML to actually work in current clients like VE. This is both purely in RESTBase.
+
+If Parsoid is going to use (and likely update / re-sanitize) old HTML, it also needs to know which assumptions it can make based on the version. It might well elect to throw away any old HTML before version X, but without knowing the version you can't make that decision easily.
+
+So far we ducked these issues by not storing any HTML, and clearing the entire cache when we made major changes. We won't be able to do this with storage in the longer term.",1418280783,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Sorry I couldn't look at this earlier. 
+
+But, one obvious comment right away is that wikitext doesn't have a ""spec"" really and there is no real versioning as far as I know. Secondly, I don't see a real use case where Parsoid would be able to take different HTML versions (for old and modified) and then use that for serialization. Parsoid may regenerate the old HTML for the new HTML spec and/or fall back to full serialization in that scenario.
+
+I also don't see a scenario where a client (like VE, Flow, etc) is going to take an old version of HTML, edit it and generate a new version of the HTML. So, I think from the scenario of editing clients, the HTML version is going to be preserved. All version bumps in HTML are likely going to happen entirely in Parsoid land on the wt2html pipeline.
+
+So, is this more richer representation really useful? I personally prefer a simpler representation. But, I haven't thought through this fully. Perhaps something worth a discussion on IRC so I understand this better.
+
+
+
+
+",1418279281,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#833765, @Jdouglas wrote:
+> Makes sense to me.  I like the idea of including spec versions in the content types.  Is there a central repository of specs I can peruse?
+
+Not yet, but we should start building it up, even if it isn't exposed in the advertised location yet.
+
+> Would this framing structure extend to other types of content, such as binary data?
+
+Yes. We can use `'transfer-encoding': 'base64'` in the headers.",1418143691,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,">>! In T75955#833765, @Jdouglas wrote:
+> Makes sense to me.  I like the idea of including spec versions in the content types.  Is there a central repository of specs I can peruse?
+
+Not yet, but we should start building it up, even if it isn't exposed in the advertised location yet.
+
+> Would this framing structure extend to other types of content, such as binary data?
+
+Yes. We can use 'transfer-encoding': 'base64' in the headers.",1418143674,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Makes sense to me.  I like the idea of including spec versions in the content types.  Is there a central repository of specs I can peruse?
+
+Would this framing structure extend to other types of content, such as binary data?",1418143556,PHID-USER-2aknafvxpqtbnnzpvtno,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. On the way back, we should indicate to Parsoid which version of HTML, wikitext or data-parsoid we are passing it, so that Parsoid can interpret it correctly. This is especially important when editing old revisions.
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multipart/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+Similarly, the v2 wt2html API would indicate the content type of each component in its response, which restbase will then store & return to the client.
+
+@arlolra, @parsoid, @jdouglas: Does this makes sense to you?",1418078655,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. On the way back, we should indicate to Parsoid which version of HTML, wikitext or data-parsoid we are passing it, so that Parsoid can interpret it correctly. This is especially important when editing old revisions.
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multipart/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+Similarly, the v2 wt2html API would indicate the content type of each component in its response, which restbase will then store & return to the client.
+
+Does this makes sense to you?",1418078438,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. On the way back, we should indicate to Parsoid which version of HTML, wikitext or data-parsoid we are passing it, so that Parsoid can interpret it correctly. This is especially important when editing old revisions.
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multipart/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+
+Does this makes sense to you?",1418078370,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. On the way back, we should indicate to Parsoid which version of HTML, wikitext or data-parsoid we are passing it, so that Parsoid can interpret it correctly. This is especially important when editing old revisions.
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multi-part/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+
+Does this makes sense to you?",1418078321,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"One issue with the format above (especially for GETs) is that we don't have a content type for the HTML & data-parsoid. This is important, as the content-type also indicates the spec version that parsoid currently emits, which we really need to track in the database. 
+
+To fix this, I have been thinking about a more generic framing structure for multi-part responses more along the lines of `multi-part/form-data`:
+
+```
+{
+    headers: {
+        'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+    },
+    body: '<html>....</html>'
+}
+```
+
+In the v2 serialization API, we could basically replace each individual key with a full mime object:
+
+```
+{
+    html: {
+        headers: {
+            'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+        },
+        body: ""the modified html""
+    },
+    original: {
+        revid: 12345, // The original revision ID
+        wikitext: {
+            headers: {
+                'content-type': 'text/plain;profile=mediawiki.org/specs/wikitext/1.0.0'
+            },
+            body: ""the original wikitext""
+        },
+        html: {
+            headers: {
+                'content-type': 'text/html;profile=mediawiki.org/specs/html/1.0.0'
+            },
+            body: ""the original HTML""
+        }
+        'data-parsoid': {
+            headers: {
+                'content-type': 'application/json;profile=mediawiki.org/specs/data-parsoid/0.0.1'
+            },
+            body: {}
+        }
+    }
+}
+```
+
+Does this makes sense to you?",1418077997,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+RESTBase / Parsoid integration - waiting for parsoid deploy,"Change 165685 had a related patch set uploaded (by Arlolra):
+Add v2 serialization route
+
+[[https://gerrit.wikimedia.org/r/165685]]
+
+#patch-for-review",1417051016,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ijwoo3bfloiiovk2zi4r,task_subcomment,NA
+Rename MediaWiki release tags,"In BugZilla, the MediaWiki product had milestones like ""1.1 release"", ""1.20.x release"" and ""1.25.0 release"" etc.
+
+Individual MediaWiki extensions didn't have such a milestone, but we did have shared ones for extensions like ""MW 1.18 version"", ""MW 1.14 version"".
+
+To avoid clashing with other project's release tags (see also T75899), we should rename the MediaWiki core ones to include ""MediaWiki"" or ""MW"".
+
+While at it I'd like to propose merging the ones formerly for extensions to be the same (e.g. merge ""1.24.0 release"" and ""MW 1.24 version"" into ""MediaWiki-1.24"" or something like that.",1416944367,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_description,resolved
+Rename MediaWiki release tags,"Thanks for raising these very valid and convincing points and for your patience.
+
+I have added ""MW-""prefixes. They are slightly less discoverable as I didn't want more stuff cluttering the projects dropdown when you enter ""MediaWiki"" plus as the dropdown does not support colors yet (there is some upstream ticket about this), people might think that they describe the version they are running instead of the version the bug should get fixed for.
+
+See https://phabricator.wikimedia.org/project/query/all/?after=MW for a list.
+
+Ironically that prefix we had also used for extension target milestones in Bugzilla too, so there were also disabled ""MW-1.18-version"" style projects. I have renamed those to ""MW-extension-1.18-version"" style to have less confusion in project dropdowns.
+
+All in all, it's a bit more confusing than I had naively anticipated. I am sorry for that.
+
+Closing as resolved.",1421156230,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,This issue doesn't seem resolved.,1420694018,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#960085, @Legoktm wrote:
+> I agree with Krinkle and fbstj that the projects should be MediaWiki specific. Basically, there should be one project for a MediaWiki 2.0 Release and another for a Pywikibot 2.0 Release.
+
++1",1420661455,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I agree with Krinkle and fbstj that the projects should be MediaWiki specific. Basically, there should be one project for a MediaWiki 2.0 Release and another for a Pywikibot 2.0 Release.",1420653182,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"So if I understand correctly you're recommending we consider version milestones as ""accidentally"" indexed and browsable through Phabricator as projects.
+
+Thus we'd have to disregard all features related to it (members, watchers, workboards, archiving, edit permissions, change feeds, ..).
+
+Because if you'd archive v2.0 when Project A's v2.0 is finished, that says nothing about a Project B still at v1.9 that will have a v2.0 next year. (e.g. like Firefox 30 and Chrome 30, you'd have to abandon all features related to individual projects and treat them as individual-meaningless correlation keywords instead).
+
+That seems like a big waste and compromise in overall usability of Phabricator (the link on task pages to e.g. [1.24 release](https://phabricator.wikimedia.org/tag/1.24-release/) would only be confusing for users as it'd provide a meaningless feed of unrelated projects). All only to try and gain what? Smaller number of projects overall?
+
+I'm not saying we should have separate version milestones for MediaWiki Core and MediaWiki extensions that follow the same release versioning. It makes perfect sense to share one ""MW 1.25 release"" between those (as I originally recommended which is what prompted this whole thread). Those would use additional filters in searches for e.g. ""MediaWiki"" when interested in that one project. (E.g. the Cite extension doesn't have its own release process, it just follows MediaWiki). But I'm talking about projects not directly following MediaWiki's release process. E.g. OOjs, VisualEditor, CDB, and all other projects we have.",1420647097,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"So if I understand correctly you're recommending we consider version milestones as ""accidentally"" indexed and browsable through Phabricator as projects.
+
+Thus we'd have to disregard all features related to it (members, watchers, workboards, archiving, edit permissions, change feeds, ..).
+
+Because if you'd archive v2.0 when Project A's v2.0 is finished, that says nothing about a Project B still at v1.9 that will have a v2.0 next year. (e.g. like Firefox 30 and Chrome 30, you'd have to abandon all features related to individual projects and treat them as individual-meaningless correlation keywords instead).
+
+That seems like a big waste and compromise in overall usability of Phabricator (the link on task pages to e.g. [1.24 release](https://phabricator.wikimedia.org/tag/1.24-release/) would only be confusing for users as it'd provide a meaningless feed of unrelated projects). All only to try and gain what? Smaller number of projects overall?
+
+I'm not saying we should have separate version milestones for MediaWiki Core and MediaWiki extensions that follow the same release versioning. It makes perfect same to share one ""MW 1.25 release"" between those and use ""MediaWiki"" as additional filter in searches when only interested in one project. (E.g. the Cite extension doesn't have its own release process, it just follows MediaWiki). But I'm talking about projects not directly following MediaWiki's release process. E.g. OOjs, VisualEditor, CDB, and all other projects we have.",1420646702,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I disagree as I do not see the problem of ""clashing"" once you can explicitly search for //MediaWiki core tasks only// with that generic milestone. So with the given arguments I currently don't (yet?) see a need to identify that the generic 1.25 milestone tag should specifically refer to MediaWiki releases only.
+If there are other projects forced to adopt some pattern, I'm happy to get aware of these projects and discuss why `v1.2.3-release` is better for them instead of `1.2.3-release`.",1420645688,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#959250, @Aklapper wrote:
+> I'm afraid that I don't understand the last two comments and I need a more concrete example of an existing problem. (In short: if you don't want non-MediaWiki results in your search results, don't put non-MediaWiki projects into your search criteria. [..]
+
+I'm sorry but this is rather frustrating. What don't you understand? This has got nothing to do with search results. I'll try and repeat myself one more time in verbose bullet points.
+
+* All Phabricator projects share a common global namespace. They're not like nested directories. Associating umbrellla or parent projects does not change this (it'll always be `project/1.25-release`, it doesn't nest like `project/mediawiki/1.25-release`, the umbrella is just meta-data, not part of the identifier).
+* A `1.2.3-release` pattern is too generic as it doesn't specify what project it is about and can't be adopted as Phabricator convention in general as it would clash with other projects. It assumes MediaWiki core it the only project we have. We have in fact about 100 others.
+* Other projects are already forced to adopt a different pattern. Maybe they'll use a different generic pattern (arms racing for every variation you can think of). E.g. Project A might use `v1.2.3-release` (prefix ""v""), Project B might use `Release 1.2.3` (the word ""Release""), project C might use `ProjectC-v1.2.3`. All variations that either try to fight MediaWiki's version numbers or come up with their own non-generic pattern.
+* Therefore, let's agree on a non-generic pattern to use for all projects (e.g. `ProductName-v1.2.3` seems sensible).
+* Now use that for MediaWiki as well (keeping the old names as additional-hashtag aliases for back-compat).",1420645438,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#959250, @Aklapper wrote:
+> I'm afraid that I don't understand the last two comments and I need a more concrete example of an existing problem. (In short: if you don't want non-MediaWiki results in your search results, don't put non-MediaWiki projects into your search criteria. [..]
+
+I'm sorry but this is rather frustrating. What don't you understand? This has got nothing to do with search results.I'll try and repeat myself one more time in verbose bullet points.
+
+* All Phabricator projects share a common global namespace. They're not like nested directories. Associating umbrellla or parent projects does not change this (it'll always be `project/1.25-release`, it doesn't nest like `project/mediawiki/1.25-release`, the umbrella is just meta-data, not part of the identifier).
+* A `1.2.3-release` pattern is too generic as it doesn't specify what project it is about and can't be adopted as Phabricator convention in general as it would clash with other projects. It assumes MediaWiki core it the only project we have. We have in fact about 100 others.
+* Other projects are already forced to adopt a different pattern. Maybe they'll use a different generic pattern (arms racing for every variation you can think of). E.g. Project A might use `v1.2.3-release` (prefix ""v""), Project B might use `Release 1.2.3` (the word ""Release""), project C might use `ProjectC-v1.2.3`. All variations that either try to fight MediaWiki's version numbers or come up with their own non-generic pattern.
+* Therefore, let's agree on a non-generic pattern to use for all projects (e.g. `ProductName-v1.2.3` seems sensible).
+* Now use that for MediaWiki as well (keeping the old names as additional-hashtag aliases for back-compat).",1420645417,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#959250, @Aklapper wrote:
+> I'm afraid that I don't understand the last two comments and I need a more concrete example of an existing problem. (In short: if you don't want non-MediaWiki results in your search results, don't put non-MediaWiki projects into your search criteria. There's no forcing to needless variation as any project can request creating new projects, and there's no forcing to adopt prefixes as there are no prefixes currently.)
+> 
+> I'm closing this ticket as resolved. Which still allows adding followup comments.
+
+I'm sorry but this is rather frustrating. What don't you understand? I'll try and repeat myself one more time in verbose bullet points.
+
+* All Phabricator projects share a common global namespace. They're not like nested directories. Associating umbrellla or parent projects does not change this (it'll always be `project/1.25-release`, it doesn't nest like `project/mediawiki/1.25-release`, the umbrella is just meta-data, not part of the identifier).
+* A `1.2.3-release` pattern is too generic as it doesn't specify what project it is about and can't be adopted as Phabricator convention in general as it would clash with other projects. It assumes MediaWiki core it the only project we have. We have in fact about 100 others.
+* Other projects are already forced to adopt a different pattern. Maybe they'll use a different generic pattern (arms racing for every variation you can think of). E.g. Project A might use `v1.2.3-release` (prefix ""v""), Project B might use `Release 1.2.3` (the word ""Release""), project C might use `ProjectC-v1.2.3`. All variations that either try to fight MediaWiki's version numbers or come up with their own non-generic pattern.
+* Therefore, let's agree on a non-generic pattern to use for all projects (e.g. `ProductName-v1.2.3` seems sensible).
+* Now use that for MediaWiki as well (keeping the old names as additional-hashtag aliases for back-compat).",1420645376,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"Ahh yeah, my problem can be solved by either doing `MediaWiki + version number` tags or doing `version number + not MediaWiki` tags (querying 'not in 'MediaWiki tag')
+
+EDIT: after further comments, I would still support prefixing rather than multi-tagging",1421060103,PHID-USER-tqvzwasywo4a7bnuwuz4,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"Ahh yeah, my problem can be solved by either doing `MediaWiki + version number` tags or doing `version number + not MediaWiki` tags (querying 'not in 'MediaWiki tag')",1420641663,PHID-USER-tqvzwasywo4a7bnuwuz4,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I'm afraid that I don't understand the last two comments and I need a more concrete example of an existing problem. (In short: if you don't want non-MediaWiki results in your search results, don't put non-MediaWiki projects into your search criteria. There's no forcing to needless variation as any project can request creating new projects, and there's no forcing to adopt prefixes as there are no prefixes currently.)
+
+I'm closing this ticket as resolved. Which still allows adding followup comments.",1420636340,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,But what about when there is a task/bug which involves one of these tags (targeting it for a particular release) and another piece of software/library/etc which is targeted too?,1420474319,PHID-USER-tqvzwasywo4a7bnuwuz4,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#955248, @Aklapper wrote:
+> It is not too generic once we've fixed T76942.
+
+Association or hierarchy does not equal containment. Even when Phabricator supports parent project associations (umbrellas), they're still in a shared global namespace and are bound to clash with other software projects. Forcing projects other than MediaWiki them to either adopt needless variation (e.g. v123 instead of 123-release), or adopt the same kind of prefixes I'm proposing for MediaWiki release tags.",1420474318,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,It is not too generic once we've fixed T76942.,1420473965,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#952762, @Aklapper wrote:
+> Urgh. So I wasn't aware that Phabricator doesn't support mentioning hash tags starting with a number. :(
+
+Phabricator support aside, ""1.24 release"" is too generic. Let's rename them to include ""MW"" (or ""MediaWiki"")?",1420461867,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"Urgh. So I wasn't aware that Phabricator doesn't support mentioning hash tags starting with a number. :(
+However, when is that important? I'd expect people to edit the Projects when setting a milestone, not mention those exact milestone names in a comment instead.
+
+Regarding an umbrella MediaWiki project, that's covered in T76942.
+
+I've dropped the .x and .0 suffixes from those milestone projects still active. Active projects left are:
+* 1.19-release
+* 1.23-release
+* 1.24-release
+* 1.25-release
+* In the list view: https://phabricator.wikimedia.org/project/query/all/?after=1
+
+So from my point of view we are done here.",1420223124,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,+1 to dropping the point release suffixes.,1419026463,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,I also support dropping and also prefixing with MW as there's more than just mediawiki that might require versions at some point,1419022372,PHID-USER-tqvzwasywo4a7bnuwuz4,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I'd drop the suffixes indeed. And also rename to mention ""MW"" or ""MediaWiki"" (with old name as additional hash-tag for back-compat and redirect). This to be less generic, and also because Phabricator doesn't support mentioning hash tags starting with a number.",1419021398,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,Left here: Drop the .x or .0 prefixes?,1419020839,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"<tl;dr>: We now have [[ https://phabricator.wikimedia.org/project/query/active/?after=1 | four active ""Target Milestone"" release projects ]] in Phabricator left, regarding the MW core (and to some extend MW extensions) world:
+* 1.19.x release
+* 1.23.x release
+* 1.24.0 release
+* 1.25.0 release
+
+------
+
+Way too long version for transparency (had to write this down anyway as this stuff can get confusing if I don't concentrate):
+
+I've archived the past projects #1.23.0_release , #1.22.x_release, #1.22.0_release, #1.21.x_release, #1.21.0_release, #1.20.x_release, #1.20.0_release, #1.19.0_release, #1.18.x_release, #1.18.0_release (which somehow don't get autolinked here, sigh).
+
+In the meantime, @Legoktm had archived the  #MW_1.24_version and #MW_1.23_version projects (use for extensions before) and changed their (open and closed) tasks' TM projects to the generic TM projects #1.24.0_release ( we don't have a 1.24.x_release project) and #1.23.0_release (.0, which is archived now, but there were no open tasks anyway).
+
+I archived #MW_1.22_version which was empty. In general the use of these target milestones in Bugzilla seems to have declined over the versions
+
+I batch-edited those tasks having MW_1.99_version tags set to have 1.99.x_release tags now.
+
+Then I archived #MW_1.19_version to #MW_1.21_version.",1419020731,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,Happy for us to go ahead with this.,1418402033,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"If we have a decision, I volunteer with the renaming itself. For some reason blocked tasks T75994 and T78140 bother me more than they should whenever I see them in backlogs.  :)",1418377495,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I also think that one MediaWiki 1.47 target milestone is better than two. While a minority knows which one should be used where, the majority get puzzled whenever find the double 1.47.
+
+I'm for applying the single tag for a single version, and then deal with the problems retrieving the right information, i.e. by sharing a saved search somewhere public for ""All MediaWiki core tasks tagged for 1.47"".",1418217664,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#808898, @Aklapper wrote:
+>So ""MediaWiki-1.47.0-release"" and ""MediaWiki-1.47.x-release"" (literally, replace ""47"" by your favorite number though)?
+
+Whether we should have only ""MediaWiki-1.47"", or ""MediaWiki-1.47.0"" and ""MediaWiki-1.47.x"", is a separate from this task. But, personally, I think we should only have ""MediaWiki-1.47"". These tags are milestones, release targets. Not the version a bug report relates to, or whether a fix should be backported. I always found the `.x` ones strange in the milestones for MediaWiki core when we used BugZilla.",1417908876,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#793597, @Jdforrester-WMF wrote:
+>>>! In T75916#792822, @Qgil wrote:
+>>>>! In T75916#789084, @Jdforrester-WMF wrote: 
+>>> Well, the union search of ""MediaWiki"" project &&
+>> 
+>> A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+> 
+> Oh, I assumed that the MW team were going to fix this the way we have for VisualEditor, Parsoid, Multimedia… are they not?
+> 
+
+I'd really like us to tag every single MediaWiki core bug with a [MediaWiki] project. The various subprojects (-Database, -UnitTests, etc) would be generalized to not be MW-core specific.
+
+So for a MediaWiki database bug you'd tag it with [MediaWiki] and [Database].
+
+This would also allow us to do things like [CirrusSearch] [UnitTests].
+
+But really this should be its own task.",1417743542,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I'm happy with this, for one. Let's do it.",1417660839,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"> A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+
+Thanks for the better wording; that is the one single reason why I wrote ""cross-pollution"" here, as long as subprojects in https://secure.phabricator.com/T3670 aren't available...
+
+If adding (currently) 30 projects (all those previous components of MediaWiki core in Bugzilla) to a search query to get only get MediaWiki core tasks with that milestone isn't considered a huge hassle (do it once for that target milestone, save the custom query for yourself or share the search query URL on some wikipage) I'm definitely in for making the naming scheme between extensions and core for target milestones consistent.
+
+I assume we still want to distinguish ""1.47.0"" (which would cover potentially everything that was fixed in all those 1.46wmfXY versions and hence included in the 1.47.0 tarball) from ""1.47.x"" (to mark stuff that should be fixed or has been fixed in 1.27.x tarball releases //after// the initial 1.47.0 release and has required backporting from 1.48wmfXY branches or git master)?
+
+So ""MediaWiki-1.47.0-release"" and ""MediaWiki-1.47.x-release"" (literally, replace ""47"" by your favorite number though)?",1417651989,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"A venturous summary of this discussion could be:
+
+* Valid Tags for past, present, and future MediaWiki releases: #MW-1.24.x, #MW-1.24.0, #MW-1.24.1...
+* Valid Tags for past, present, and future MediaWiki weekly snapshots: WMF-deploy-2014-11-26-(1.25wmf10)...
+
+These tags are equally applicable to core, extensions, and anything else.",1417509059,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#787907, @Aklapper wrote:
+> I'm not convinced to give those MediaWiki extensions Target Milestones the same name though as that would cross-pollute when searching in all those MediaWiki-* projects we have now so I' rather go with some ""MW-1.24.x-series"" or such. 
+
+I think this is biased towards MediaWiki core. You'd need to create milestones for every extension, skin and other MediaWiki-related project that doesn't have its own release/versioning scheme. That seems like a waste. Using #MW_1.24_version (as we're already doing for extensions, one has to intersect with the relevant project) seems simple enough.
+
+For projects with lots of sub projects (e.g. things formerly having their own BugZilla product, like MediaWiki core and VisualEditor) would use an umbrella project.
+
+At the moment that involves manual double-tagging (though a triager would have queries to find untagged issues to clean up). But there's to be intent in upstream Phabricator to embrace umbrella projects as a native concept (e.g. projects being in a hierarchy where they're visible and queryable via their parents). – https://secure.phabricator.com/T3670",1417201138,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#792822, @Qgil wrote:
+>>>! In T75916#789084, @Jdforrester-WMF wrote: 
+>> Well, the union search of ""MediaWiki"" project &&
+> 
+> A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+
+Oh, I assumed that the MW team were going to fix this the way we have for VisualEditor, Parsoid, Multimedia… are they not?
+
+> What is clear is that the current cohabitation of #1.24.0-release and #mw_1.24_version is confusing. As a bug reporter or even as a casual extension developer, how am I supposed to know which one to use?
+
+I agree we should fix this by only having one.
+
+> PS: also, I wonder why #1.24.0_release or #1.24.0-release won't render a proper label.
+
+Maybe projects' hashtags can't start with a number to get auto-linked?",1417199157,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#789084, @Jdforrester-WMF wrote: 
+> Well, the union search of ""MediaWiki"" project &&
+
+A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+
+What is clear is that the current cohabitation of #1.24.0-release and #mw_1.24_version is confusing. As a bug reporter or even as a casual extension developer, how am I supposed to know which one to use?
+
+PS: also, I wonder why #1.24.0_release or #1.24.0-release won't render a proper label.
+",1417163048,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#789084, @Jdforrester-WMF wrote: 
+> Well, the union search of ""MediaWiki"" project &&
+
+A problem being that ""MediaWiki"" (core) is not one project but a bunch of them. Not a problem for a saved search but not ideal for casual queries... Is this relevant?
+
+What is clear is that the current cohabitation of #1.24.0-release and #mw_1.24_version is confusing. As a bug reporter or even as a casual extension developer, how am I supposed to know which one to use?
+
+PS: also, I wonder why #1.24.0_release or #1.24.0_release won't render a proper label.
+",1417163033,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,">>! In T75916#787907, @Aklapper wrote:
+> I strongly support renaming the generic MediaWiki Target Milestones.
+> I'm not convinced to give those MediaWiki extensions Target Milestones the same name though as that would cross-pollute when searching in all those MediaWiki-* projects we have now so I' rather go with some ""MW-1.24.x-series"" or such. 
+> There is also a small (maybe neglectable?) differentiation between ""must fix in MW core for the 1.25.0 tarball release"" vs. ""should fix in this MW extension at some point in the branch corresponding to MW core 1.25.x releases"".
+
+Well, the union search of ""MediaWiki"" project && ""MediaWiki-release-1.18"" release tag won't contain any extension items (and v.v.) – is that not suitable? This is what we're doing with ""WMF-deploy-2014-11-26_(MW1.25wmf10)"".",1417031970,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"> Individual MediaWiki extensions didn't have such a milestone, but we did have shared ones for extensions like ""MW 1.18 version"", ""MW 1.14 version"".
+What was the purpose of those milestones? Where they for things that should be backported or for planning (""hope to get this done by then"")?
+
+@Aklapper: can you update the description of {T100} with the summary of what we did/planned (or point to a wiki page that describes it). That should probably be the place we work from to solve this issue.",1417026417,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"I strongly support renaming the generic MediaWiki Target Milestones.
+I'm not convinced to give those MediaWiki extensions Target Milestones the same name though as that would cross-pollute when searching in all those MediaWiki-* projects we have now so I' rather go with some ""MW-1.24.x-series"" or such. 
+There is also a small (maybe neglectable?) differentiation between ""must fix in MW core for the 1.25.0 tarball release"" vs. ""should fix in this MW extension at some point in the branch corresponding to MW core 1.25.x releases"".",1417006148,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"You say ""release tags"", I CC @greg and @Jdforrester-WMF.",1416992053,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+Rename MediaWiki release tags,"(Starting today, I'm moving all the tasks related to new/renamed projects to #Project-Creators because the Phabricator backlog is getting really big)",1416948852,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-g4umm5xifvnyjhvuzvzx,task_subcomment,NA
+"Create remaining VisualEditor projects and migrate ""tracking"" tasks into the relevant projects","We're scrapping tracking bugs
+
+* All VE projects' descriptions should have ""Reminder: All VisualEditor-related tasks should be tagged with #VisualEditor as well, for tracking, triage and management purposes."" appended.
+* All projects are regular (briefcase) type.
+
+| Project | Description | Task it replaces
+| #VisualEditor-Performance | Performance issues with #VisualEditor. | T51685 |
+| #VisualEditor-CopyPaste | Copy paste issues with #VisualEditor. | T35105 |
+| #VisualEditor-InterfaceLanguage | Multi-lingual interface (i18n, l10n, RTL) issues with #VisualEditor. | N/A |
+| #VisualEditor-Links | Link editing in #VisualEditor (not #VisualEditor-MediaWiki specific). | N/A |
+| #VisualEditor-Media | Media editing in #VisualEditor (not #VisualEditor-MediaWiki specific). | N/A |
+| #VisualEditor-MediaWiki-Plugins | Performance issues with #VisualEditor. | T48803 |
+
+
+Merge into existing projects:
+
+| Tracker | Projects |
+| T68083 | #VisualEditor, #VisualEditor-ContentEditable |
+| T69690 | #VisualEditor, #VisualEditor-MediaWiki-Media |
+| T67955 | #VisualEditor, #VisualEditor-EditingTools |
+| T72372 | #VisualEditor, #VisualEditor-MediaWiki-Mobile, #Browser_Support_Google_Android |
+| T49780 | #VisualEditor, #VisualEditor-EditingTools |
+| T52781 | #VisualEditor, #VisualEditor-Initialisation |
+| T54327 | #VisualEditor, #VisualEditor-Initialisation |
+| T50789 | #VisualEditor, #VisualEditor-MediaWiki-Links |
+| T55604 | #VisualEditor, #VisualEditor-MediaWiki-Templates |
+| T53792 | #VisualEditor, #VisualEditor-ContentLanguage |
+| T35126 | #VisualEditor, #VisualEditor-ContentLanguage |
+| T35077 | #VisualEditor, #VisualEditor-ContentLanguage |
+| T41596 | #VisualEditor, #VisualEditor-Tables |
+| T39870 | #VisualEditor, #VisualEditor-MediaWiki-Media |",1416938037,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5ufggm4c7s4fufhtimjv,task_description,resolved
+"Create remaining VisualEditor projects and migrate ""tracking"" tasks into the relevant projects",Now complete.,1422425192,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5ufggm4c7s4fufhtimjv,task_subcomment,NA
+[Regression pre-wmf10] VisualEditor does not load on beta labs,"Errors: 
+
+""Exception thrown by papaparse"" load.php:161
+""TypeError: document.getElementById(...) is null""
+
+""Exception thrown by user callback"" load.php:161
+""TypeError: mw.log.warning is not a function""",1416929762,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-mgagqv36esykujdeqdd6,task_description,resolved
+[Regression pre-wmf10] VisualEditor does not load on beta labs,Verified in Betalabs,1416956566,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mgagqv36esykujdeqdd6,task_subcomment,NA
+[Regression pre-wmf10] VisualEditor does not load on beta labs,"Change 175862 merged by jenkins-bot:
+Disable papaparse because it breaks everything
+
+[[https://gerrit.wikimedia.org/r/175862]]",1416952927,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mgagqv36esykujdeqdd6,task_subcomment,NA
+[Regression pre-wmf10] VisualEditor does not load on beta labs,"Change 175862 had a related patch set uploaded (by Catrope):
+Disable papaparse because it breaks everything
+
+[[https://gerrit.wikimedia.org/r/175862]]
+
+#patch-for-review",1416952218,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mgagqv36esykujdeqdd6,task_subcomment,NA
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,"my bot found maiwiki at meta_p and tried to start running queries, but this fails.
+
+name value must be 'Wikipedia' but name is currently a char sequenze repeating hex E0A4B5
+```
+MariaDB [(none)]> select *, hex(name) from meta_p.wiki where dbname like 'mai%';
++---------+------+------------+-----------+--------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+--------------------------------------------------------------+
+| dbname  | lang | name       | family    | url                      | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |                                                    hex(name) | 
++---------+------+------------+-----------+--------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+--------------------------------------------------------------+
+| maiwiki | mai  | ?????????? | wikipedia | http://mai.wikipedia.org |    1 | s3.labsdb |         0 |        1 |               0 |                1 |            1 | E0A4B5E0A4BFE0A495E0A4BFE0A4AAE0A4BFE0A4A1E0A4BFE0A4AFE0A4BE |
++---------+------+------------+-----------+--------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+--------------------------------------------------------------+
+1 row in set (0.00 sec)
+```
+maiwiki.labsdb missing in /etc/hosts
+```
+$ mysql -hmaiwiki.labsdb
+ERROR 2005 (HY000): Unknown MySQL server host 'maiwiki.labsdb' (0)
+```
+",1416916519,PHID-USER-rbcxdzszrm6s4izt67kj,False,PHID-TASK-hc57wasluvhgws762zjc,task_description,resolved
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,The hosts files have been updated accross tools.,1416937163,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-hc57wasluvhgws762zjc,task_subcomment,NA
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,"Ok, but the dns problem still exists:
+
+```
+tools.merlbot@tools-dev:~/lists/qs$ mysql -hmaiwiki.labsdb
+ERROR 2005 (HY000): Unknown MySQL server host 'maiwiki.labsdb' (0)
+
+```",1416933249,PHID-USER-rbcxdzszrm6s4izt67kj,False,PHID-TASK-hc57wasluvhgws762zjc,task_subcomment,NA
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,"The data of the meta table is mostly filled by the maintain-replicas script from API queries to the actual wiki proper; what I see when I query the table manually is 'विकिपिडिया' which is, as far as I can tell, the correct name for the project in that language.  The value in hexadecimal is also correct; it /appears/ to repeat itself because those are Unicode codepoints are on a high codepoint plane and the utf8 encoding has a long prefix for every character.  Notice:
+
+E0A4**B5**E0A4**BF**E0A4**95**...
+
+In other words, this works as designed.  You may want to use 'family' if you want to test for Wikipedia-ness rather than 'name' which is meant for display to endusers.  This is true even in European languages since, for example, frwiki would have 'Wikipédia' (note the accent) in the name column.
+",1416930210,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-hc57wasluvhgws762zjc,task_subcomment,NA
+maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts,"The data of the meta table is mostly filled by the maintain-replicas script from API queries to the actual wiki proper; what I see when I query the table manually is 'विकिपिडिया' which is, as far as I can tell, the correct name for the project in that language.  The value in hexadecimal is also correct; it /appears/ to repeat itself because those are Unicode codepoints are on a high codepoint plane and the utf8 encoding has a long prefix for every character.  Notice:
+
+E0A4**B5**E0A4**BF**E0A4**95**...
+
+In other words, this works as designed.  You may want to use 'family' if you want to test for Wikipedia-ness rather than 'name' which is meant for display to endusers.  This is true even in European languages since, for example, frwiki would have 'Wikipédia' (not the accent) in the name column.
+",1416930114,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-hc57wasluvhgws762zjc,task_subcomment,NA
+Combine imageinfo requests on load,"1. Go to http://en.wikipedia.org/wiki/Barack_Obama as a logged-in user in Chrome
+2. Open the inspector, go to the network panel, click the filter icon and select ""XHR""
+3. Click Edit beta
+4. Observe lots of POST /w/api.php requests, one for each image
+
+We should combine these requests rather than doing a separate one for each image.",1416886111,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-kcbyh6alaid3ganxbdh7,task_description,resolved
+Combine imageinfo requests on load,"Change 716268 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Remove redundant initialization from LinkCache%%%
+https://gerrit.wikimedia.org/r/716268",1630656376,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"Change 716268 had a related patch set uploaded (by Thiemo Kreuz (WMDE); author: Thiemo Kreuz (WMDE)):
+%%%[mediawiki/extensions/VisualEditor@master] Remove redundant initialization from LinkCache%%%
+https://gerrit.wikimedia.org/r/716268",1630583660,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"Change 180228 merged by jenkins-bot:
+Combine imageinfo requests
+
+[[https://gerrit.wikimedia.org/r/180228]]",1422905521,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"There are two Parsoid bug/feature requests that prevent us from eliminating the API calls:
+
+1. We need the original dimensions and image type of the image. If Parsoid can give it to us in the data that will solve the issue.
+2. Right now, Parsoid hard-codes the image default size to 220, which is the enwiki size default. That, however, is not the default of all wikis (and definitely not standalone) so we have to resize the image. This requires us to get the original dimensions and file type (since many resize rules depend on whether the image is bitmap or drawing) which leads to API requests.
+
+If #1 is solved, we shouldn't need an API request on load for existing images.",1422904203,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"I don't think that batching imageinfo requests goes quite far enough. I'd like to eliminate this API request from the critical path.
+
+Let's assume that every image whose file name matches /\.svg/ is type=DRAWING type and that all other images are bitmaps. Although not guaranteed to be reliable, in practice this heuristic will almost always be correct. We should only attempt to validate our guess with an API request when the user attempts to resize the image. (This may mean that we have to scale the image back down after allowing the user to scale it up. Such cases should be exceedingly rare, however.)
+
+The original dimensions of bitmap images should ideally be part of the paction=parse response from the API. We could also include them in the MediaWiki read HTML as data-* attributes. (This approach would take 30 days to propagate fully, but I think that's OK.)",1422854751,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+Combine imageinfo requests on load,"Change 180228 had a related patch set uploaded (by Alex Monk):
+[WIP] Combine imageinfo requests by setting up a new class like LinkCache to request them all centrally
+
+[[https://gerrit.wikimedia.org/r/180228]]
+
+#patch-for-review",1418761684,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kcbyh6alaid3ganxbdh7,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Open up the wikitext editor and attempt to switch to VE. It no longer works. Clicking has no effect and you remain on the wikitext editor.
+
+On Chrome and Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1416483000,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_description,resolved
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Change 176052 merged by Catrope:
+Followup 142a44e: fix path names to MobileContextItemWidget.{js,css}
+
+[[https://gerrit.wikimedia.org/r/176052]]",1417045961,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),Verified the fix in Betalabs and test2,1417042711,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Change 176052 had a related patch set uploaded (by Catrope):
+Followup 142a44e: fix path names to MobileContextItemWidget.{js,css}
+
+[[https://gerrit.wikimedia.org/r/176052]]
+
+#patch-for-review",1417034259,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Still failing in wmf9, now because our fix used MobileContextOptionWidget instead of MobileContextItemWidget",1417034244,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),Checked the fix in betalabs - switching between Editor and Edit source works.,1416521838,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),Fixed in master; backport scheduled for this evening's SWAT.,1416515441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"**gerritadmin** wrote:
+
+Change 174779 merged by jenkins-bot:
+Follow-up I7eb0d0e: ve.ui.MobileContext.css doesn't exist any more, Toto
+
+https://gerrit.wikimedia.org/r/174779",1416512973,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"**gerritadmin** wrote:
+
+Change 174779 had a related patch set uploaded by Jforrester:
+Follow-up I7eb0d0e: ve.ui.MobileContext.css doesn't exist any more, Toto
+
+https://gerrit.wikimedia.org/r/174779",1416512799,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"Issue seems to be in VisualEditor
+exception 'MWException' with message 'ResourceLoaderFileModule::readStyleFile: style file not found: ""/srv/mediawiki/php-master/extensions/VisualEditor/lib/ve/src/ui/styles/ve.ui.MobileContext.css""' in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoaderFileModule.php:902
+Stack trace:
+
+See http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core.mobile%7Cext.visualEditor.mediawiki.mobile%7Cext.visualEditor.mobileViewTarget%7Cmobile.editor.ve&skin=minerva&version=20141120T011929Z&*",1416490761,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),I'm investigating this. I know what's happening but not why.,1416490395,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?),"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/AbulO05q",1416483313,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ztbhkhlbjf2yhr7pllu2,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN","See e.g. https://fr.wikipedia.org/?diff=109114947
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415995140,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mi4dx3mxevunni7ssqg3,task_description,resolved
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN",Verified the fix in test2.,1416443478,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN",Verified the fix in beta.,1416009547,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN",To go out in Monday's SWAT.,1416006013,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN","Change 173363 merged by jenkins-bot:
+Restore original rowspan/colspan rather than normalizing or overwriting with NaN
+
+https://gerrit.wikimedia.org/r/173363",1416004630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN","It turned out there were two corruption problems: colspan=""02"" was normalized to colspan=""2"", and colspan=""2 garbage"" was normalized to colspan=""NaN"". The patch fixes both.",1415999232,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+"VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN","Change 173363 had a related patch set uploaded by Catrope:
+Restore original rowspan/colspan rather than normalizing or overwriting with NaN
+
+https://gerrit.wikimedia.org/r/173363",1415999100,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mi4dx3mxevunni7ssqg3,task_subcomment,NA
+VisualEditor: shortcut(Ctrl+1) for Page Title does not work on Mac,"Betalabs and test2
+
+In VE on Mac click Ctrl+1 which should insert Page Title - nothing happens. 
+
+All other shortcuts - Ctrl+0,2-7 - work.
+
+
+Ctrl+1 works in IE 11.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: Macintosh",1415837760,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-mvlq3qqfqqmazl5ytcnb,task_description,invalid
+VisualEditor: shortcut(Ctrl+1) for Page Title does not work on Mac,"So, it was actually set as one of your shortcuts as we have seen yesterday.Changing Status back to Resolved Invalid.",1416431095,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mvlq3qqfqqmazl5ytcnb,task_subcomment,NA
+VisualEditor: shortcut(Ctrl+1) for Page Title does not work on Mac," Ctrl+1 does not work in any of browsers on my Mac - Safari7, Chrome, and FF 38. 
+
+And I did not see any shortcuts assigned to Ctrl+1 in my System preferences.",1415923607,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-mvlq3qqfqqmazl5ytcnb,task_subcomment,NA
+VisualEditor: shortcut(Ctrl+1) for Page Title does not work on Mac,"Works for me in Safari 8, Chrome 38 and Firefox 33. What browser were you using?",1415879355,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mvlq3qqfqqmazl5ytcnb,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","screenshot
+
+Environment- beta
+
+1> Select Insert -> Template 
+2> In the resulting add a template dialog the button is labeled ""Hide Options"".See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14839}",1415647980,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-xliej5372d5wtuol7oum,task_description,resolved
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""",Checked in production.,1416436863,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""",Verified the fix in test2,1415822579,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","Was a regression in wmf7, fix has been cherry-picked and deployed.",1415665803,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","**gerritadmin** wrote:
+
+Change 172329 merged by jenkins-bot:
+Followup a86d824: fix reference to this in foreach callback
+
+https://gerrit.wikimedia.org/r/172329",1415663196,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""",Verified the fix in betalabs.,1415657268,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","**gerritadmin** wrote:
+
+Change 172329 had a related patch set uploaded by Catrope:
+Followup a86d824: fix reference to this in foreach callback
+
+https://gerrit.wikimedia.org/r/172329",1415651859,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","**gerritadmin** wrote:
+
+Change 172320 merged by jenkins-bot:
+Followup a86d824: fix reference to this in foreach callback
+
+https://gerrit.wikimedia.org/r/172320",1415651367,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","**gerritadmin** wrote:
+
+Change 172320 had a related patch set uploaded by Catrope:
+Followup a86d824: fix stupid stupid logic inversion
+
+https://gerrit.wikimedia.org/r/172320",1415650039,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+"VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as ""Hide Options"", instead of ""Show Options""","Good finding! 
+
+It's in betalabs only. test2 and production display 'Show options' button.",1415648733,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-xliej5372d5wtuol7oum,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,"If I open https://en.wikipedia.org/wiki/James_Braid_(surgeon)?veaction=edit in Chrome 38, the viewport initially jumps to the bottom of the page (the references list). If I press a cursor key, I'm back at the top. If I reload the page, the problem is not reproducible. Cannot reproduce in Firefox either.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415562720,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-vdncadf63tpumxtunpkp,task_description,resolved
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,Verified in Chrome 38.,1417047518,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,Scheduled for SWAT later today.,1415902195,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,"**gerritadmin** wrote:
+
+Change 172983 merged by jenkins-bot:
+Initialize context's $element as hidden
+
+https://gerrit.wikimedia.org/r/172983",1415901665,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,"**gerritadmin** wrote:
+
+Change 172983 had a related patch set uploaded by Esanders:
+Initialize context's $element as hidden
+
+https://gerrit.wikimedia.org/r/172983",1415885146,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,Note that I am able to reproduce the incorrect scroll position in Chrome in a private browser window.,1415656961,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome,"Chrome remembers a scroll position on the page - if a a content at the bottom of the page was viewed/edited, and Back/Forward buttons then were used, loading the same page again will display the last scroll position. 
+
+So far, I could not see that anything was stored in cookies.",1415651930,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-vdncadf63tpumxtunpkp,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"This is due to the fix applied in https://gerrit.wikimedia.org/r/#/c/170280/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415376420,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-l2puvf36mj2rean2tzju,task_description,resolved
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,Verified in test2 and production.,1416434299,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,Also fixed in test2 now.,1415665724,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,Verified the fix in betalabs.,1415657861,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"Change 172298 merged by jenkins-bot:
+Fix craziness in template dialog focusing
+
+https://gerrit.wikimedia.org/r/172298",1415651790,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"Change 172298 had a related patch set uploaded by Jforrester:
+Fix craziness in template dialog focusing
+
+https://gerrit.wikimedia.org/r/172298",1415644160,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"Change 171997 merged by jenkins-bot:
+Fix craziness in template dialog focusing
+
+https://gerrit.wikimedia.org/r/171997",1415408098,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load,"Change 171997 had a related patch set uploaded by Catrope:
+Fix craziness in template dialog focusing
+
+https://gerrit.wikimedia.org/r/171997",1415407374,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l2puvf36mj2rean2tzju,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"When I click on the ""Bin"" icon to delete an empty parameter from a template, the system doesn't delete it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415368440,PHID-USER-j3xqvy6nbc2vdqsijned,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_description,resolved
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,Verified in production.,1415915601,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"Confirmed, it works on itwiki (Chrome; VEctor; Win 8.1)",1415867009,PHID-USER-j3xqvy6nbc2vdqsijned,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,Verified in Betalabs and test2.,1415824909,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,Fix was backported to wmf7 and deployed.,1415666118,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"**gerritadmin** wrote:
+
+Change 172446 merged by jenkins-bot:
+Followup a054a75: don't reintroduce removed template parameters
+
+https://gerrit.wikimedia.org/r/172446",1415664001,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"**gerritadmin** wrote:
+
+Change 172446 had a related patch set uploaded by Catrope:
+Followup a054a75: don't reintroduce removed template parameters
+
+https://gerrit.wikimedia.org/r/172446",1415663907,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"**gerritadmin** wrote:
+
+Change 172317 merged by jenkins-bot:
+Followup a054a75: don't reintroduce removed template parameters
+
+https://gerrit.wikimedia.org/r/172317",1415652271,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"**gerritadmin** wrote:
+
+Change 172317 had a related patch set uploaded by Catrope:
+Followup a054a75: don't reintroduce removed template parameters
+
+https://gerrit.wikimedia.org/r/172317",1415649897,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,Did we break something when we re-wrote the template parameter fixing code last week?,1415620424,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"Can confirm in Chrome and FF. What happens is that clicking on the bin makes the field disappear in the dialog, but when you save it's still in the template, as if you hadn't changed anything.",1415386564,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"Could not confirm - tried both mentioned links - [https://it.wikipedia.org/wiki/Atletica_leggera_ai_Giochi_della_XXV_Olimpiade_-_100_metri_ostacoli] and[https://it.wikipedia.org/w/index.php?title=Utente%3ANnvu%2FSandbox1&diff=69043230&oldid=69043213] 
+ any field(empty or not) can be deleted.",1415386192,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,I got no error.,1415370569,PHID-USER-j3xqvy6nbc2vdqsijned,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"Ok, on both of those templates I was able to delete the missing fields while using Chrome on Ubuntu. 
+
+You could try opening up the javascript console in Chrome (Ctrl+Shift+J) and seeing if any errors appear when you try to use the bin button.",1415370322,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"I tried to delete the field on [https://it.wikipedia.org/wiki/Atletica_leggera_ai_Giochi_della_XXV_Olimpiade_-_100_metri_ostacoli this page] with Chrome and Firefox, but I couldn't delete any field. 
+
+In [https://it.wikipedia.org/w/index.php?title=Utente%3ANnvu%2FSandbox1&diff=69043230&oldid=69043213 this edit] I tried to delete the field ""successivo"" (which is not a required field) and I couldn't delete it.",1415369636,PHID-USER-j3xqvy6nbc2vdqsijned,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted,"I'm unable to duplicate this on master. I tried emptying the field and then deleting it, which worked. I also tried adding an empty field in wikitext, saving, and then opening it up in VE. I was able to delete the parameter then too. 
+
+Do you have any more details that might help us duplicate? Do you have a particular diff where this was happening?",1415369032,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-3skoc3yrmrphd6vlwwdo,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"Steps to reproduce:
+
+1.Open any of the following dialog:
+Basic Reference/Citation/Reference list/Page Settings
+
+2.Start typing
+
+Observe that , the text that you are typing is appearing on CE, as the cursor is active there instead of inside the dialog
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1415309880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_description,resolved
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Verified the fix in production,1416446266,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Verified the fix in test2,1415822390,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Verified the fix in test2,1415822383,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Fix was cherry-picked to wmf7 and deployed.,1415665846,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Verified the fix in Betalabs,1415657473,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171882 merged by jenkins-bot:
+Remove and restore selection for non-isolated dialogs
+
+https://gerrit.wikimedia.org/r/171882",1415618199,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171882 had a related patch set uploaded by Catrope:
+Remove and restore selection for non-isolated dialogs
+
+https://gerrit.wikimedia.org/r/171882",1415388759,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171852 merged by jenkins-bot:
+Remove and restore selection for non-isolated dialogs
+
+https://gerrit.wikimedia.org/r/171852",1415383198,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171852 had a related patch set uploaded by Esanders:
+Remove and restore selection for non-isolated dialogs
+
+https://gerrit.wikimedia.org/r/171852",1415381304,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"This is still happening for all other dialogs(Page Settings,References List,Citation) except Basic Reference dialog in test2",1415321190,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,Going out in 16:00 SWAT.,1415315016,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171757 merged by jenkins-bot:
+Fix non-linear selection handling in ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/171757",1415314342,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171757 had a related patch set uploaded by Catrope:
+Fix non-linear selection handling in ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/171757",1415314184,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171734 merged by jenkins-bot:
+Fix non-linear selection handling in ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/171734",1415314121,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings,"**gerritadmin** wrote:
+
+Change 171734 had a related patch set uploaded by Catrope:
+Fix non-linear selection handling in ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/171734",1415311719,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jc73aooy3axdug4ckbsa,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"Dragging images to table
+
+1. In VE insert a table(do not enter anything in the table).
+2. Inser->Media-> select and insert any image outside the table.
+3. Select the inserted image and drag it to the table - make sure that the insertion indication(an underscore) is displayed outside of the table,  on the right side. 
+
+Drop the table  - the table becomes separated in two parts. The attached screenshot shows the result of several attempts of the described scenario
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14885}",1415146800,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-5oa3p2m62q7vlwtaworj,task_description,resolved
+VisualEditor: Drag-and-drop an inserted image slices a table,Verified the fix in production.,1416434473,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,Confirmed in Betalabs and test2.,1415823224,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,Bug 73318 was created about drag-and-drop block images issue.,1415813377,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"(In reply to etonkovidova from comment #3)
+> Created attachment 17066 [details]
+> Dragging images to table
+> 
+> I added a screen recording  - kind of tricky to reproduce, however,
+> something can be(or should be) done about the issue?
+
+Ah, that's of block images; inline images now work fine.
+
+I'm minded to say that we won't try to fix block images here; at least, let's put that into a different bug?
+
+**Attached**: {F14887}",1415809490,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"Created attachment 17066
+Dragging images to table
+
+I added a screen recording  - kind of tricky to reproduce, however, something can be(or should be) done about the issue?
+
+**Attached**: {F14887}",1415320024,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"Change 171271 merged by jenkins-bot:
+Replace block drop logic with isAllowedChildNodeType check
+
+https://gerrit.wikimedia.org/r/171271",1415218723,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: Drag-and-drop an inserted image slices a table,"Change 171271 had a related patch set uploaded by Esanders:
+Replace block drop logic with isAllowedChildNodeType check
+
+https://gerrit.wikimedia.org/r/171271",1415200246,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5oa3p2m62q7vlwtaworj,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,"Steps to reproduce:
+
+1.Select a text
+2.Press command+k
+3.When the link inspector opens , place the cursor inside the textbox which already has the selected text as link target name
+
+Observed Result:
+Link suggestions are not appearing after placing the cursor inside it.
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415126640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,Verified the fix in production,1415834510,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,Verified the fix in test2,1415228177,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,Verified the fix in Betalabs,1415146695,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,"Change 171006 merged by jenkins-bot:
+Populate LookupInputWidget on mousedown too
+
+https://gerrit.wikimedia.org/r/171006",1415140368,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it,"Change 171006 had a related patch set uploaded by Catrope:
+Populate LookupInputWidget on mousedown too
+
+https://gerrit.wikimedia.org/r/171006",1415129507,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-c6rxgzyci66c7ffcr5dz,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox,"Steps:
+1. In Firefox, enable ""Preferences > Advanced > General > Browsing > Check my spelling as I type""
+2. On an empty line (slug), write ""occurence""
+3. Observe wiggly red line; right click and change it to ""occurrence""
+4. Observe explosion
+
+Possibly a unicorning issue?
+
+
+Working steps:
+
+1. On an empty line (slug), write ""Foo occurence"" or ""occurence bar""
+2. Observe wiggly red line; right click and change it to ""occurrence""
+3. Observe non-explosion
+
+(i.e., it works fine if there's any other content in the content node)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415058420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kyyxvxidfguxqxef3flo,task_description,resolved
+VisualEditor: Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox,"Re-checcked (Mac FF 34.0.5)
+
+- production
+- test2
+- betalbs
+
+The issue is not presented anymore.  Closing the bug as Resolved.
+
+",1423854619,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-kyyxvxidfguxqxef3flo,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox,"Cannot reproduce on https://cs.wikipedia.org/wiki/Wikipedista:AKlapper_%28WMF%29/Sandbox?veaction=edit with Firefox 35 on Fedora 21, given the steps above. 
+Only one insertion/string replacement (as expected); no output in browser console.
+
+Is this still an issue? If so, which FF version on which platform?",1423690686,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-kyyxvxidfguxqxef3flo,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox,"This sounds similar to T65462 in Chrome, which has insertions, deletions, and corruptions.",1418191658,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-kyyxvxidfguxqxef3flo,task_subcomment,NA
+Fix nowiki heuristics for quotes,"See https://fr.wikipedia.org/w/index.php?title=Univers_cin%C3%A9matographique_Marvel&curid=5796605&diff=108676945&oldid=108668984 for a particularly bad sequence of nowikis.
+
+We should examine this and NicoV's suggestions below and see what is realistic / feasible. But, at least a couple of back-to-back nowikis should be avoidable.
+
+NicoV says (on https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=631914857#Unnecessary_succession_of_nowiki)
+
+-----
+    There are 4 sets of nowiki tags:
+
+        The first one is a combination of an opening tag and a closing tag <nowiki>...</nowiki>.
+        The second one is a self-closing nowiki tag <nowiki/> (just after the previous set) : it's totally useless, and brings nothing except more complexity to the wikitext
+        The third one is a self-closing nowiki tag <nowiki/> (just before the next set) : same remark as above
+        The fourth one is a combination of an opening tag and a closing tag <nowiki>...</nowiki>.
+
+    My report is that 2 sets are completely useless (first and second are redundant; third and fourth are redundant).
+    Of course, there's also the problem reported many times, a long time ago, that if nowiki are added they should be added only around the part that needs them not around a whole part of a sentence, but it was not the main issue I was reporting. For this, as it already been said so many times, my preferred methods (in order):
+
+        Use {{'}} (it should be possible to configure VE on each wiki to know if there's such a template, that's what I'm doing for example in WPCleaner's configuration)
+        Use '<nowiki/>'' (nowiki between the single quote and the italic formatting)
+        Use <nowiki>'</nowiki>'' (nowiki around the single quote)
+-----
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414811340,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4tywejgljpprmmm7tbbh,task_description,resolved
+Fix nowiki heuristics for quotes,A whole bunch of fixes landed in production yesterday which should improve this situation.,1420556920,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4tywejgljpprmmm7tbbh,task_subcomment,NA
+Fix nowiki heuristics for quotes,"I may not be able to get this done quickly enough -- I have an updated version up now, which eliminates the excess nowikis in this example by consolidating all heuristics in once place, but it might require more smarts. In this new version, it will insert a <nowiki/> whenever it sees a quote-char as the preceding/next sibling or first/last child of a I/B element in the DOM. That said, because of selective serializer, this might only kick in when new quotes are needed in those positions.
+
+Still have to figure out some improvements to the heuristics .. but given the context-sensitive nature of quote-parsing where stuff at the end of line can change parse behavior earlier in the line, these might be elusive. 
+
+I am going to be travelling and so cannot get to this again before next week.",1415391133,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4tywejgljpprmmm7tbbh,task_subcomment,NA
+Fix nowiki heuristics for quotes,"**gerritadmin** wrote:
+
+Change 171154 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 72844): Fixes to quote nowiki protection in selser mode.
+
+https://gerrit.wikimedia.org/r/171154",1415145234,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4tywejgljpprmmm7tbbh,task_subcomment,NA
+Fix nowiki heuristics for quotes,"This seems to be selser-specific.
+
+This below is what selser generates:
+[subbu@earth lib] node parse --selser --html2wt --oldtextfile /tmp/quote.wt --oldhtmlfile /tmp/old.html < /tmp/new.html
+*<nowiki> MARVEL Studios et ABC prépare cinq séries '</nowiki><nowiki/>''Netflix Original''<nowiki/><nowiki>'de </nowiki>[[Film de super-héros|super-héros]] pour [[Netflix]]. La diffusion de ces séries s'étalera sur plusieurs années : ''[[Daredevil (série télévisée)|Daredevil]]'' sera la première, puis ''Jessica Jones'', ''Iron Fist'' et enfin ''Luke Cage''.
+
+This below is what the full serializer generates:
+[subbu@earth lib] node parse --html2wt < /tmp/new.html
+* MARVEL Studios et ABC prépare cinq séries '<nowiki/>''Netflix Original''<nowiki/>'de [[Film de super-héros|super-héros]] pour [[Netflix]]. La diffusion de ces séries s'étalera sur plusieurs années : ''[[Daredevil (série télévisée)|Daredevil]]'' sera la première, puis ''Jessica Jones'', ''Iron Fist'' et enfin ''Luke Cage''.",1415143333,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4tywejgljpprmmm7tbbh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,"Page settings box opacity issue
+
+found in test2 and betalabs
+
+Steps to reproduce: 
+
+1. In VE - click on Page options icon. 
+2. Select Page settings->click in the check box 'Redirect this page to'
+3. Start typing 'Something' (no quotes)
+4. At some point of typing(or after you type 'Something' and then start to delete it a letter by letter) - a drop-down list of suggestions appears partially displaying underlying options for 'Show the Table of Contents' options. Look at the attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15193}",1414790040,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,Verified in production.,1415834937,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,Verified the fix in betalabs and test2.,1415222688,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,"**gerritadmin** wrote:
+
+Change 170508 merged by jenkins-bot:
+Pass $overlay to redirectTargetInput in MWSettingsPage
+
+https://gerrit.wikimedia.org/r/170508",1415039888,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue,"**gerritadmin** wrote:
+
+Change 170508 had a related patch set uploaded by Alex Monk:
+Pass $overlay to redirectTargetInput in MWSettingsPage
+
+https://gerrit.wikimedia.org/r/170508",1414817472,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-iyyzwzlyhrbyhzbudijv,task_subcomment,NA
+Put table cell editing controls in the context of the cell/selection so they aren't so hard to find,"screenshot
+
+(On beta.wmflabs) I had a very hard time finding the table editing menus for Merge cell. I knew they were available, but assumed they would be part of the normal attached-to-the-table menu system.
+
+I also didn't notice the ""Content cell"" menu appear until it was pointed out to me.
+
+I think it would be more intuitive, to put those controls next to the elements I'm changing, as shown in the mockups at https://www.mediawiki.org/wiki/VisualEditor/Design/Table_editor#Version_2
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14988}",1414694280,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-iezltl5j2pc2evrnk2x6,task_description,duplicate
+Put table cell editing controls in the context of the cell/selection so they aren't so hard to find,"{F17789}
+
+{F17790}
+
+Designs for including a menu in context.",1417470106,PHID-USER-flenunkasbjk4topxvaj,False,PHID-TASK-iezltl5j2pc2evrnk2x6,task_subcomment,NA
+Put table cell editing controls in the context of the cell/selection so they aren't so hard to find,"Yeah, I agree. Over-riding the formatting menu is clever but entirely non-obvious, and completely breaks the VE design rule about only disabling, not changing, controls between contexts.",1414694536,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iezltl5j2pc2evrnk2x6,task_subcomment,NA
+VisualEditor: Please let me drop the cursor into the table caption if it exists. Please?,"See e.g. the table in section 0 of the link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/User:Jdforrester_(WMF)/Sandbox?veaction=edit",1414624080,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hsyburiakp2zdvz34qoh,task_description,resolved
+VisualEditor: Please let me drop the cursor into the table caption if it exists. Please?,Verified in production.,1416422920,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-hsyburiakp2zdvz34qoh,task_subcomment,NA
+VisualEditor: Please let me drop the cursor into the table caption if it exists. Please?,"Verified the fix in betalabs and test2(FF, Safari, Chrome).",1415227772,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-hsyburiakp2zdvz34qoh,task_subcomment,NA
+VisualEditor: Please let me drop the cursor into the table caption if it exists. Please?,Thanks!,1415040528,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hsyburiakp2zdvz34qoh,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"1. Open VE on a page that contains a focusable node
+2. Click out of the surface so it's blurred and the toolbar tools are greyed out (selection is a ve.dm.NullSelection)
+3. Try to select a focusable node by clicking on it
+4. Nothing happens
+5. Click to drop the cursor in some normal text
+6. Repeat #3, observe that it works now
+
+This also causes bug 72719: double-clicking focusable nodes fires their double-click handler and opens the associated dialog, but the selection is still null, so the dialogs don't open with the right context.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1414623540,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2iqe4d6ln6247lyafirs,task_description,resolved
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,Verified the fix in test2 and production (en.wiki),1415062309,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 170370 merged by jenkins-bot:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/170370",1414792644,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 170371 merged by jenkins-bot:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/170371",1414792639,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 170371 had a related patch set uploaded by Catrope:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/170371",1414780008,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 170370 had a related patch set uploaded by Catrope:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/170370",1414779989,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,Verified the fix in Betalabs,1414703162,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 169966 merged by jenkins-bot:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/169966",1414660282,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred,"Change 169966 had a related patch set uploaded by Catrope:
+Fix selection transitions between FocusableNodes and non-linear selections
+
+https://gerrit.wikimedia.org/r/169966",1414627126,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2iqe4d6ln6247lyafirs,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"Screenshot
+
+There is an extra space appearing at the top of the toolbar inside VE
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14781}",1414608180,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_description,resolved
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,Verified the fix in production,1415835121,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,Verified the fix in Betalabs and test2,1414702821,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"**gerritadmin** wrote:
+
+Change 169861 merged by jenkins-bot:
+Hide page status indicators even if they aren't :visible
+
+https://gerrit.wikimedia.org/r/169861",1414623733,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"**gerritadmin** wrote:
+
+Change 169860 merged by jenkins-bot:
+Hide page status indicators even if they aren't :visible
+
+https://gerrit.wikimedia.org/r/169860",1414616343,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"**gerritadmin** wrote:
+
+Change 169861 had a related patch set uploaded by Jforrester:
+Hide page status indicators even if they aren't :visible
+
+https://gerrit.wikimedia.org/r/169861",1414616050,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"**gerritadmin** wrote:
+
+Change 169860 had a related patch set uploaded by Bartosz Dziewoński:
+Hide page status indicators even if they aren't :visible
+
+https://gerrit.wikimedia.org/r/169860",1414615976,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"(In reply to Bartosz Dziewoński from comment #2)
+> Butbutbut wasn't that supposed to be fixed with c81ed82f?
+
+Apparently it didn't work.",1414609009,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,Butbutbut wasn't that supposed to be fixed with c81ed82f?,1414608754,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE,"This is because of the mw-indicators div. It's empty if there are no indicators, but the fact that it floats right and the VE toolbar then has clear: both; seems to make it take up space somehow.
+
+Even if an empty indicators div doesn't take up space: if there are indicators, where do we put them in VE mode?",1414608616,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5sccvnyuy43bzxbyv7n4,task_subcomment,NA
+"VisualEditor: Deleting from a paragraph-terminating node to a paragraph-terminating node (?) is throwing ""Unbalanced set of replace operations found""","Reproduce:
+
+1. go to https://fi.wikipedia.org/wiki/User:Stryn/VE?veaction=edit
+2. highlight all texts from the end of ""This is just a test.[1]"" to end of ""Visuaalinen muokkain.[2]"" and press backspace button or delete or whatever and nothing happens - VE just gets stuck.
+3. you can't save the page nor switch to wikitext editor even if you have made changes to the page.
+
+If you highlight text from ""This is just a test.[1]"" to ""This is not."" it's working as it should. So probably the problem is with the references.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72640",1414442040,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-pgkoq2ygryfod5gjbheg,task_description,resolved
+"VisualEditor: Deleting from a paragraph-terminating node to a paragraph-terminating node (?) is throwing ""Unbalanced set of replace operations found""","Confirmed in test2 and on https://fi.wikipedia.org/wiki/User:Stryn/VE?veaction=edit.
+
+On the page https://fi.wikipedia.org...  - there are many Uncaught Error: ve.dm.Document.getBranchNodeFromOffset(): offset 39 is out of bounds etc.
+
+
+In test2: type four lines of text on four separate lines.
+
+- Add reference to the end of the first line
+- add another reference to the end of the second line
+- leave the third line as it is
+- re-use the first reference and add it to the end of the fourth line
+
+
+Start highlighting the text and try to delete it with 'Delete' button. 
+FF displays: 
+Error: Unbalanced set of replace operations found load.php:316
+TypeError: currentNode.children[(nao.offset - 1)] is undefined load.php:479
+Error: Unbalanced input passed to document.
+
+After several attempts of highlighting and deleting - the page becomes unresponsive - I can place cursor but cannot move it with arrow or Enter buttons; cannot Save, cannot switch to Read mode(TypeError: data[i] is undefined).",1415056388,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-pgkoq2ygryfod5gjbheg,task_subcomment,NA
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,"screenshot of the console error
+
+Environment- test2,production,beta
+
+1>In a blank page, open the link inspector,type in some text in the link input box and keep the inspector open.
+2> While the inspector is open ,click on to add a bullet/numbered list.
+3> JS  console error “Uncaught Error: offset -1 out of bounds” and the inspector remains open.See screenshot.
+
+Clicking on Done or Remove does not close the inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72494
+
+**Attached**: {F15103}",1414419600,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_description,resolved
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,Verified in production.,1416423181,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_subcomment,NA
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,Verified the fix in betalbs and test2.,1415232212,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_subcomment,NA
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,"Change 170855 merged by jenkins-bot:
+Protect against offset=-1 in insertContent()
+
+https://gerrit.wikimedia.org/r/170855",1415129377,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_subcomment,NA
+VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open,"Change 170855 had a related patch set uploaded by Catrope:
+Protect against offset=-1 in insertContent()
+
+https://gerrit.wikimedia.org/r/170855",1415055527,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7c7nuth53wqtbnm6qaa2,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"I don't seem to be able to trigger the warning with anything on any production wiki today.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414156020,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_description,resolved
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Verified in production, betalabs, and test2.",1415381886,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168620 merged by jenkins-bot:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168620",1414449072,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168619 merged by jenkins-bot:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168619",1414449036,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168620 had a related patch set uploaded by Catrope:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168620",1414171681,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168608 merged by jenkins-bot:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168608",1414171667,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168619 had a related patch set uploaded by Catrope:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168619",1414171662,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?,"Change 168608 had a related patch set uploaded by Alex Monk:
+Fix wikitext warning: Get range from selection before trying to find start
+
+https://gerrit.wikimedia.org/r/168608",1414167506,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upmb4s4arsl5sfm2zcbh,task_subcomment,NA
+VisualEditor:  Opening a very large complex transclusion sometimes hangs in Firefox,"Firefox with the wrong box
+
+Steps to reproduce:
+
+1.  Open [[William Shakespeare]] in VisualEditor. 
+
+2.  Scroll to the ==References== section and select the contents (a complex transclusion).
+
+3.  Try to open it so you can edit it.
+
+
+This hangs in Firefox 32 with this error message:
+
+Warning:  Unresponsive script
+
+A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.
+
+Script: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141016T200718Z:89
+
+
+It opens correctly (but slowly) in Chrome and Safari, and sometimes in Firefox, too.  When it fails to open correctly, then it displays the contents in the wrong dialog box (see attachment).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15370}",1414016880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zsenbwls7ebypri26j7n,task_description,duplicate
+VisualEditor:  Opening a very large complex transclusion sometimes hangs in Firefox,Is this the same problem as {T71799}?,1426445245,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-zsenbwls7ebypri26j7n,task_subcomment,NA
+Actually run MediaWiki-VisualEditor's tests for MWHeadingNode / MWPreformattedNode,"Right now we have a hack in ve.test.utils.js that reregisters the core versions of HeadingNode and PreformattedNode to ensure MWHeadingNode and MWPreformattedNode aren't used, because using them would break the VE core tests when run in VE-MW.
+
+This is horrible, because it makes us unable to test specific behavior in the MW nodes. For instance, https://gerrit.wikimedia.org/r/#/c/162310/3 fails its own tests because those tests use HeadingNode rather than MWHeadingNode, even though the tests in question were clearly designed to use MWHeadingNode.
+
+We should come up with a way that MW nodes can be not registered for code tests, but be registered for MW tests.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414016460,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qmfoshrg3djlltdfiuev,task_description,resolved
+Actually run MediaWiki-VisualEditor's tests for MWHeadingNode / MWPreformattedNode,"Change 191036 merged by jenkins-bot:
+Add tests for MW node variants (heading/table/pre)
+
+[[https://gerrit.wikimedia.org/r/191036]]",1424199001,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qmfoshrg3djlltdfiuev,task_subcomment,NA
+Actually run MediaWiki-VisualEditor's tests for MWHeadingNode / MWPreformattedNode,"Change 191036 had a related patch set uploaded (by Esanders):
+Add tests for MW node variants (heading/table/pre)
+
+[[https://gerrit.wikimedia.org/r/191036]]
+
+#patch-for-review",1424178367,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qmfoshrg3djlltdfiuev,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"IE11 test2 and betalabs
+
+Steps to reproduce: 
+
+1. Open VE-> try to insert a link(via a shortcut or by clicking on the option) - the box(class=""oo-ui-window-isolated oo-ui-ltr"" ) shows up and disappears momentarily.
+
+2. Editing links - presents the same problem 
+
+Debugger complains about load.php ""Unable to get property 'from' of undefined or null reference' rangeSelection is undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1414014960,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-frawcbm336hvwpzabjlz,task_description,resolved
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"The previous comment was filed as a separate bug: 73154
+
+Besides bug 73154 - the fix re-verified in betalbs/test2/en wiki.",1415390965,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"IE11: Using a shortcut Ctrl+K to insert a link consistently gives the following message twice :
+
+DOM7009: Unable to decode image at URL: 'data:image/gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA'.  File: gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA",1415310607,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"Verified in test2 and production(en.wikipedia.org)
+
+- inserting a link with a menu option - OK
+- editing an existing link wiht a menu option - OK
+- insert a link with the shortcut - Ctrl+K - the link inspector opens and closes momentarily",1414514256,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169228 merged by jenkins-bot:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169228",1414446820,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169228 had a related patch set uploaded by Catrope:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169228",1414446705,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169224 merged by jenkins-bot:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169224",1414446221,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169221 merged by jenkins-bot:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169221",1414446134,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169224 had a related patch set uploaded by Jforrester:
+Make link inspector not close itself in IE... again
+
+https://gerrit.wikimedia.org/r/169224",1414446057,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"**gerritadmin** wrote:
+
+Change 169221 had a related patch set uploaded by Catrope:
+Make link inspector not close itself in IE. Again.
+
+https://gerrit.wikimedia.org/r/169221",1414444852,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer,"Affecting IE10 as well, as per fi.wp report.",1414409027,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-frawcbm336hvwpzabjlz,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Select any template
+4.Click on ""Show Options""
+
+
+Observed Result:
+There is no advanced option showing up on the left panel.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15057}",1413838440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_description,resolved
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content",Verified the fix in production,1414614075,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content",Verified the fix in test2,1414102963,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content",Verified the fix in Betalabs,1414000340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content","**gerritadmin** wrote:
+
+Change 167973 merged by jenkins-bot:
+GridLayout: Set dimensions.visibility = '' again if we have a height and a width
+
+https://gerrit.wikimedia.org/r/167973",1413933451,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content","**gerritadmin** wrote:
+
+Change 167973 had a related patch set uploaded by Alex Monk:
+GridLayout: Set dimensions.visibility = '' again if we have a height and a width
+
+https://gerrit.wikimedia.org/r/167973",1413931019,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] The ""Show Options"" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content",Caused by Gerrit change 166191,1413930885,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-dokvmwmoyy5xh2fmdf7t,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Steps to reproduce:
+
+1.  Open a page and go to Page options > Categories.
+
+2.  (Add a category if none exist.)  Edit a category to add a sort key.
+
+3.  Save page.
+
+4.  Check diff:  no sort key was added.  :-(  
+
+
+Confirmed in Firefox 32 and Safari 6.2 on Macs and Windows, so it's probably happening everywhere.
+
+This doesn't seem to be bug 48555.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413506580,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_description,resolved
+VisualEditor: [Regression] Adding category sort keys no longer working,Verified the fix in production,1414627937,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Verified in betalabs, test2, and wikimedia - e.g. a Category gets added as [[Category:Cat2|Sort_added]]",1414432683,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Change 167876 merged by jenkins-bot:
+CategoryPopupWidget: Track popup hiding again so sortkey changes are applied
+
+https://gerrit.wikimedia.org/r/167876",1413936802,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Change 167877 merged by jenkins-bot:
+PopupWidget: Remove references to 'show' and 'hide' events
+
+https://gerrit.wikimedia.org/r/167877",1413933624,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Change 167877 had a related patch set uploaded by Alex Monk:
+PopupWidget: Remove references to 'show' and 'hide' events
+
+https://gerrit.wikimedia.org/r/167877",1413919349,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Adding category sort keys no longer working,"Change 167876 had a related patch set uploaded by Alex Monk:
+CategoryPopupWidget: Track popup hiding again so sortkey changes are applied
+
+https://gerrit.wikimedia.org/r/167876",1413919252,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qvglmtpnlcnxuc34bwtp,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Steps to reproduce:
+
+1.  Open a page in Firefox (my version is 32).
+
+2.  Select some text.
+
+3.  Press Ctrl-X or Command-X.
+
+4.  Notice that nothing happened.
+
+
+Paste (Ctrl-V) might be working intermittently, but you have to copy rather than cut the text to do that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1413504300,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_description,resolved
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Re-verified in Chrome, FF, IE11, and Safari - cut/copy/paste look fine.",1415321607,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"(In reply to etonkovidova from comment #8)
+> Safari(1.25wmf6 (295d963) - when text is pasted, the page scrolls up
+> momentarily. Otherwise, cut/paste seems to be working correctly in
+> Safari(wmf6).
+> 
+> FF and Chrome do not display this ""scroll-up"" behavior
+
+This is bug 71728.",1415052959,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Safari(1.25wmf6 (295d963) - when text is pasted, the page scrolls up momentarily. Otherwise, cut/paste seems to be working correctly in Safari(wmf6).
+
+FF and Chrome do not display this ""scroll-up"" behavior",1415048669,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"In case this needs to be re-opened in the futre:  
+
+I can't cut text in Safari today.  I'm going to assume that this is fixed in the next release, because it happens at en.wp but not at Beta Labs or MediaWiki.org  Consequently, this Firefox-specific bug might not actually be Firefox-specific.",1414176075,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Safari does not handle Paste smoothly - when some text is pasted, the page swiftly(but noticeably) scrolls to the top and back to the place when the text is pasted.",1414104409,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,Confirmed - the issue is fixed in test2 (wmf5).,1414103937,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,Confirmed the fix(es) on Betalabs.,1413925382,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"(In reply to Ed Sanders from comment #2)
+> Fixed after various copy/paste related patches
+> https://gerrit.wikimedia.org/r/#/q/status:merged+project:VisualEditor/
+> VisualEditor+branch:master+topic:copy-fix,n,z
+> 
+> Works on beta labs, but apparently hasn't been deployed yet. Wasn't this
+> supposed to be backported?
+
+Backports due on Monday morning.",1413654656,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"Fixed after various copy/paste related patches https://gerrit.wikimedia.org/r/#/q/status:merged+project:VisualEditor/VisualEditor+branch:master+topic:copy-fix,n,z
+
+Works on beta labs, but apparently hasn't been deployed yet. Wasn't this supposed to be backported?",1413654562,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers,"This is a serious issue. I actually managed to get the program to start deleting whole sections of text with this bug.
+
+Steps to reproduce: 
+1. Select some text
+2. Ctrl-x
+3. Ctrl-v at a different location. The cursor should (shouldn't, but it does) go to the top of the page, above everything else.
+4. Right-click at a different location and click ""paste"". Should (n't) have pasted the text at the top of the page.
+6. Select this stray text, right click, and press delete (use the mouse, not keyboard).
+7. Watch the article get randomly deleted in completely unpredictable ways.
+
+I tried this on multiple articles and got wacky behaviour both times. Browser: Firefox 33.0.",1413639663,PHID-USER-uku6gl4xeqbtbrcbr5ig,True,PHID-TASK-dqkqlyz5zbhrlqk3ihv6,task_subcomment,NA
+VisualEditor: Selection starting on a tooled item (e.g. link) always shows the context menu,"Start a selection inside a link and drag to outside it. The context menu never disappears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413494100,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xkj5bkkwqzmcktj6whgq,task_description,resolved
+VisualEditor: Selection starting on a tooled item (e.g. link) always shows the context menu,"**gerritadmin** wrote:
+
+Change 167217 merged by jenkins-bot:
+Fix contextChange events from annotations
+
+https://gerrit.wikimedia.org/r/167217",1413573845,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xkj5bkkwqzmcktj6whgq,task_subcomment,NA
+VisualEditor: Selection starting on a tooled item (e.g. link) always shows the context menu,"**gerritadmin** wrote:
+
+Change 167217 had a related patch set uploaded by Jforrester:
+Fix contextChange events from annotations
+
+https://gerrit.wikimedia.org/r/167217",1413562026,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xkj5bkkwqzmcktj6whgq,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open Cite>Book or Cite>Journal
+3.Place the cursor inside the Title field
+
+Observed Result:
+
+A weird red border is surrounding the textfield instead of light blue highlight
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15258}",1413408120,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ue6vedmhhpltifawbjjw,task_description,resolved
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,Verified the fix in production,1414613579,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,Verified the fix in test2,1414103222,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,Verified the fix in Betalabs,1413833974,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"**gerritadmin** wrote:
+
+Change 167334 merged by jenkins-bot:
+Only validate required template params after blur
+
+https://gerrit.wikimedia.org/r/167334",1413587953,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"**gerritadmin** wrote:
+
+Change 167334 had a related patch set uploaded by Jforrester:
+Only validate required template params after blur
+
+https://gerrit.wikimedia.org/r/167334",1413585703,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"**gerritadmin** wrote:
+
+Change 167226 merged by jenkins-bot:
+Only validate required template params after blur
+
+https://gerrit.wikimedia.org/r/167226",1413581302,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"**gerritadmin** wrote:
+
+Change 167226 had a related patch set uploaded by Alex Monk:
+Only validate required template params after blur
+
+https://gerrit.wikimedia.org/r/167226",1413564956,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away,"Looks like a regression from the ""highlight invalid text inputs"" change.",1413408288,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ue6vedmhhpltifawbjjw,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a bullet or numbered list
+3.Keep on adding indentation to the list to create slugs
+4.Place your cursor inside the slug to add an item to the list
+Observed Result:
+It throws error in the console:TypeError: Cannot read property 'getSelection' of null
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15252}",1413406020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6suiiraatmj5yc6h6pe5,task_description,resolved
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""",Verified the fix in production,1414101312,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""",Verified the fix in test2,1413504112,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""",Verified the fix in Betalabs,1413423273,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""","**gerritadmin** wrote:
+
+Change 166884 merged by jenkins-bot:
+Followup 2432cbf: add recursion guard to updateSlug
+
+https://gerrit.wikimedia.org/r/166884",1413410379,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""","**gerritadmin** wrote:
+
+Change 166884 had a related patch set uploaded by Catrope:
+Followup 2432cbf: add recursion guard to updateSlug
+
+https://gerrit.wikimedia.org/r/166884",1413408204,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws ""TypeError: Cannot read property 'getSelection' of null""","Rephrasing the bug its not only for slugs created from the list but rather a generic issue for all kind of slugs.It happens if you place your cursor in a slug and then place your cursor anywhere in the page which follows the slug.
+If you place your cursor somehwere above the slug , you wont get the error.",1413406392,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6suiiraatmj5yc6h6pe5,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Current pipeline uses the global wmfgrunt slave-script:
+* [/bin/wmfgrunt](https://github.com/wikimedia/integration-jenkins/blob/0b85d48e60/bin/wmfgrunt)
+* [/tools/Gruntfile.js](https://github.com/wikimedia/integration-jenkins/blob/0b85d48e60/tools/Gruntfile.js)
+
+Fetch integration-jenkins.git to test it. As dependencies are pre-compiled and committed to git for Ubuntu Precise, on other platforms, first `cd ./tools; rm -rf node_modules` and `npm install` to provide for your system's architecture.
+
+It's invoked from this macro: https://github.com/wikimedia/integration-config/blob/0b85d48e60/jjb/macro.yaml#L344
+
+
+For many reasons, we should migrate from grunt-contrib-qunit to Karma, and use Chromium and/or Firefox as browser instead of PhantomJS:
+* Performance. Chromium is faster.
+* Accuracy.  PhantomJS is not a browser we support. Its layout and JavaScript engine and version thereof are irrelevant. It's based on a port from an old Safari build. Aside from being old it's also customised and under various abstraction layers. Ideally we'd run in multiple browsers, but even one would be a great start. PhantomJS does support nice features most browsers can't or wont implement, but those are not features we need to run unit tests. We want a real browser.
+* Ability. While testing fallback behaviour is important, many new browser features are unavailable in PhantomJS. This is actively making it impossible to run tests against modern code such as from OOjs UI and VisualEditor that don't support Safari 4 or 5.
+
+https://github.com/karma-runner/karma
+https://github.com/karma-runner/karma-chrome-launcher
+https://github.com/karma-runner/karma-qunit
+https://github.com/karma-runner/grunt-karma
+
+This is already being used by OOjs, OOjs UI and VisualEditor standalone. This task is about migrating the pipeline for projects that rely on running in a MediaWiki context. This brings many complexities due to registering and loading of scripts. As well as migrating the bootstrapping code to support Ubuntu Trusty and labs instances (as opposed to prod slavs running Precise).",1413326580,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_description,resolved
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Sorry for the noise, but after all the nagging I also wanted to thank for this great improvement. I can now easily run the QUnit tests headlessly without having to clone `integration/jenkins`, it supports two browsers we actually support, and it's so fast: Down from 33 seconds to 18 seconds in Chromium and 23 seconds in Firefox. Awesome!",1427112789,PHID-USER-m2zne2efu3rgmre73nl7,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"More issues I had when running `grunt karma:main` locally:
+
+* I had to pass `MW_SERVER` and `MW_SCRIPT_PATH` (which makes sense), but it's a) not documented anywhere and b) the error message is not helpful at all.
+* In `karma-qunit` (`lib/adapter.js`), `QUnit.load` and `QUnit.start` are executed (which is fine), and they try to set `QUnit.config.autostart` to `false`, but that doesn't work somehow in my setup. Instead, `QUnit.config.autostart` is `undefined` right before `QUnit.load` is called, and thus QUnit fails on trying to `start()` twice. I had to patch it locally to set `autostart` to `false` directly before calling `load`.",1427112177,PHID-USER-m2zne2efu3rgmre73nl7,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"The reported number of tests ran differs widely between running QUnit manually in the browser and running it via Karma. For example, [some recent mediawiki-core-qunit run](https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/38693/console) reports `Executed 259 of 259`, while [this run from last Thursday](https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/38575/console) said `1576 assertions passed`. I suppose `karma-qunit` counts tests, while `Special:JavaScriptTest/qunit` counts assertions? Even if that is the explanation, it should be mentioned somewhere.",1427111764,PHID-USER-m2zne2efu3rgmre73nl7,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198293 merged by jenkins-bot:
+mwext-{name}-qunit: To hhvm/karma/chromium from zend/php53/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198293]]",1426893093,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198293 had a related patch set uploaded (by Krinkle):
+mwext-{name}-qunit: To hhvm/karma/chromium from zend/php53/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198293]]
+",1426892796,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198257 merged by jenkins-bot:
+mwext-VisualEditor-qunit: To trusty/karma/chromium from precise/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198257]]",1426876782,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198257 had a related patch set uploaded (by Krinkle):
+mwext-VisualEditor-qunit: To trusty/karma/chromium from precise/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198257]]
+",1426873737,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198210 merged by jenkins-bot:
+mediawiki-core-qunit: To trusty/hhvm/mysql/chrome from precise/zend/sqlite/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198210]]",1426871791,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 198210 had a related patch set uploaded (by Krinkle):
+Update mwcore-qunit to trusty/hhvm/mysql/chrome from precise/zend/sqlite/phantomjs
+
+[[https://gerrit.wikimedia.org/r/198210]]
+",1426849570,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 186934 merged by jenkins-bot:
+Add qunit-karma macro and various *-qunit-karma jobs
+
+[[https://gerrit.wikimedia.org/r/186934]]",1422598807,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 187638 merged by jenkins-bot:
+mediawiki-core-qunit: Migrate to simplified mw-set-env-qunit.sh
+
+[[https://gerrit.wikimedia.org/r/187638]]",1422591931,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"First passing build using local Karma and Chromium!
+https://integration.wikimedia.org/ci/job/mediawiki-core-qunit-karma/5/console",1422583906,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 186934 had a related patch set uploaded (by Krinkle):
+[WIP] Add qunit-karma macro and mediawiki-core-qunit-karma job
+
+[[https://gerrit.wikimedia.org/r/186934]]
+
+#patch-for-review",1422583844,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 187638 had a related patch set uploaded (by Krinkle):
+mediawiki-core-qunit: Migrate to simplified mw-set-env-qunit.sh
+
+[[https://gerrit.wikimedia.org/r/187638]]
+
+#patch-for-review",1422583792,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 173512 merged by coren:
+contint: Add tmpfs mount in jenkins-deploy homedir for labs slaves
+
+[[https://gerrit.wikimedia.org/r/173512]]",1420558950,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 178551 merged by jenkins-bot:
+SpecialJavaScriptTest: Add export feature
+
+[[https://gerrit.wikimedia.org/r/178551]]",1420481309,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 178551 had a related patch set uploaded (by Krinkle):
+SpecialJavaScriptTest: Add export feature
+
+[[https://gerrit.wikimedia.org/r/178551]]
+
+#patch-for-review",1420480792,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),,1418757151,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),,1418757143,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 173529 merged by jenkins-bot:
+Migrate mediawiki/qunit jobs from production slaves to labs
+
+[[https://gerrit.wikimedia.org/r/173529]]",1417375509,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),">>! In T74063#787333, @Krinkle wrote:
+> Blocked on https://gerrit.wikimedia.org/r/#/c/175949/ which removes the test that was leaking jQuery animations.
+
+This has been merged.
+
+>>! In T74063#765974, gerritadmin wrote:
+> 
+> Change [173529](https://gerrit.wikimedia.org/r/173529) in `integration/config` by Krinkle:
+>> Migrate mediawiki/qunit jobs from production slaves to labs
+>>
+>> Change-Id: I69c4d6db114e2960c76ac01c4b255b7fb7bf8962
+
+This change has been deployed to Jenkins. The QUnit jobs now install MediaWiki on a labs slave and also run PhantomJS there.",1417375446,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),Blocked on https://gerrit.wikimedia.org/r/#/c/175949/ which removes the test that was leaking jQuery animations.,1416982781,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 173529 had a related patch set uploaded by Krinkle:
+Migrate mediawiki/qunit jobs from production slaves to labs
+
+https://gerrit.wikimedia.org/r/173529",1416072839,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Tested a few in labs, and are now running fine. The compared runs in labs are an N+1 run since the first one involve zuul-cloner cloning mediawiki-core.
+
+--
+
+on gallium in 1m18s:
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/12309/
+
+on integration-slave1003 in 1m34s:
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/12365/
+
+--
+
+on gallium in 1m23s:
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/12362/
+
+on integration-slave1003 in 1m31s:
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/12366/
+
+--
+
+on gallium in 29s:
+https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/32092/
+
+on integration-slave1003 in 32s:
+https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/32094/",1416072792,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"The sqlite installer auto-detects presence of a tmpfs mount in $HOME via mw-set-env:
+
+ https://github.com/wikimedia/integration-jenkins/blob/8abc7b6/bin/mw-set-env.sh#L19
+
+I've mounted tmpfs drive in the $HOME of jenkins-deploy on the integration slaves
+
+ https://gerrit.wikimedia.org/r/173511
+ https://gerrit.wikimedia.org/r/173512",1416068611,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 173512 had a related patch set uploaded by Krinkle:
+[WIP] contint: Add tmpfs mount in jenkins-deploy homedir for labs slaves
+
+https://gerrit.wikimedia.org/r/173512",1416060464,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"I've copied one of the qunit2 jobs to a static directory on integration-slave1008 and proxied it through ssh to my local Chrome to use Dev Tools to investigate the QUnit failures.
+
+They are indeed timing out, on load.php requests. Some of which are taking over 12 seconds (the QUnit timeout for an individual test is 10 seconds, defined in our testrunner.js in mediawiki-core:/tests/qunit/data).
+
+The main slowdown is the database layer. Increasing the timeout to 30 seconds made it work, but we don't want our tests to be that slow. I'll first try to match production speed more, and we could resort to increasing the timeout otherwise.
+
+Will add a tmpfs to the integration slaves and make Jenkins use that when appropriate.",1416057491,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Step 1: Move qunit from prod/precise to labs/trusty.
+Step 1a: Refactor puppet for localhost/qunit and apply to labs.
+Step 1b: Refactor puppet for mediawiki testing and apply to labs (sqlite, php5-cli, imagemagic, etc.)
+Step 2: Change integration/jenkins:bin/wmfgrunt to use Karma instead of Grunt-contrib-qunit/grunt-lib-phantomjs
+
+localhost/qunit:
+* https://gerrit.wikimedia.org/r/#/c/170792/
+* https://gerrit.wikimedia.org/r/#/c/168630/
+* https://gerrit.wikimedia.org/r/#/c/168631/
+
+Looks like the qunit test doesn't pass in labs. Some seeminly-random API calls are failing.
+
+https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit2/6/console",1415204108,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium),"Change 168631 had a related patch set uploaded by Krinkle:
+[WIP] contint: Apply contint::qunit_localhost to labs slaves
+
+https://gerrit.wikimedia.org/r/168631",1415203966,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h5r6intumxzasr64ard3,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add some categories
+3.Try to open the context menu for it
+
+Observed Result:
+Observe that the context menu is appearing far towards left side of the dialog box and it is not closing when you navigate to other options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15142}",1413318120,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cq5xz34jat667ipldw3m,task_description,resolved
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,*** Bug 71999 has been marked as a duplicate of this bug. ***,1413817416,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,Verified the fix in production,1413504648,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,Verified the fix in Betalabs and test2,1413392117,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166709 merged by jenkins-bot:
+Put category popups in the inner overlay for now
+
+https://gerrit.wikimedia.org/r/166709",1413334092,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,SWATting in the morning.,1413333864,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166709 had a related patch set uploaded by Jforrester:
+Put category popups in the inner overlay for now
+
+https://gerrit.wikimedia.org/r/166709",1413333760,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166701 merged by jenkins-bot:
+Put category popups in the inner overlay for now
+
+https://gerrit.wikimedia.org/r/166701",1413332269,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166701 had a related patch set uploaded by Catrope:
+Put category popups in the inner overlay for now
+
+https://gerrit.wikimedia.org/r/166701",1413331489,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing,"**gerritadmin** wrote:
+
+Change 166279 had a related patch set uploaded by Catrope:
+Correctly place CategoryPopupWidget in LTR and RTL
+
+https://gerrit.wikimedia.org/r/166279",1413318325,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cq5xz34jat667ipldw3m,task_subcomment,NA
+"VisualEditor:  New and changed citations display with blank lines before and after the citation in <references />, if using citation templates","Steps to reproduce:
+
+1.  Open a page containing the <references /> block (so you can see what happens as you change citations).
+
+2.  Create a new citation or edit an existing one, using a citation template (e.g., Cite web) in the Cite menu.
+
+3.  See a blank line displayed before and after the citation.  
+
+This can be reproduced in Safari 6.2 and Firefox 32 on Mac OS 10.8.5.  It happens with Marielle's script for Citoid and with manually completed citation templates. cannot be reproduced by adding text to the Basic citation dialog (although it can be reproduced by using the Cite menu within the Basic citation dialog).
+
+This is a display-only problem.  When the page is saved, everything is normal (e.g., https://en.wikipedia.org/w/index.php?diff=629488479&oldid=629487984).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1413234900,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-hhyxloh7waxmrcuezybh,task_description,resolved
+"VisualEditor:  New and changed citations display with blank lines before and after the citation in <references />, if using citation templates",I can't reproduce this (any more?).,1414013635,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-hhyxloh7waxmrcuezybh,task_subcomment,NA
+"VisualEditor:  New and changed citations display with blank lines before and after the citation in <references />, if using citation templates",Is this caused by our recent changes to how references are evaluated?,1413915263,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hhyxloh7waxmrcuezybh,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"Reported at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Irrelevant_tags , quoting below:
+
+> Why would [this edit](http://en.wikipedia.org/w/index.php?title=M.R._Organisation_Limited&curid=44080416&diff=629153289&oldid=629153016) get tagged with copyright violation template removed and speedy deletion template removed if the edit did not remove the templates? Is this a bug in the tags system? The user used HHVM and VisualEditor, is this relevant? 109.79.177.119 09:43, 11 October 2014 (UTC)
+
+(The page in question has unfortunately been deleted since, but the data is still there, just hidden.)
+
+I did some quick investigating:
+
+* If you review the page history a bit (which I managed to do before
+  it was deleted), the two templates were indeed removed at a point
+  (and that was correctly tagged) and then restored, with the next
+  edit being tagged incorrectly.
+* You can examine the logic that led to that edit being tagged at
+  [[Special:AbuseFilter/examine/log/10945503]] – if you look at the
+  row described as ""Unified diff of changes made by edit"", you can see
+  that AbuseFilter really thinks these tags were removed in that edit
+  (although they were not).
+
+--------------------------
+**URL**: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29/Archive_131#Irrelevant_tags
+**See Also**:
+* {T74329}",1413023760,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_description,resolved
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"This bug has been fixed and the fix will be deployed to Wikimedia wikis this week, with MediaWiki version 1.27.0-wmf.21, per https://www.mediawiki.org/wiki/MediaWiki_1.27/Roadmap.",1460198078,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"Change 282100 merged by jenkins-bot:
+Avoid crippled APIEditBeforeSave hook, use new features of EditFilterMergedContent instead
+
+[[https://gerrit.wikimedia.org/r/282100]]",1460165183,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,This proved easier to fix than I expected thanks to @tstarling's wonderful work in 09a5febb7b024c0b6585141bb05cba13a642f3eb.,1460010075,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"Change 282100 had a related patch set uploaded (by Bartosz Dziewoński):
+Avoid crippled APIEditBeforeSave hook, use new features of EditFilterMergedContent instead
+
+[[https://gerrit.wikimedia.org/r/282100]]
+",1460009891,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,I suppose no one else is going to work on this.,1459974657,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"> Any chance of a fix?
+
+Any contributed patches are welcome to speed up progress here. 
+See https://www.mediawiki.org/wiki/Developer_access and https://www.mediawiki.org/wiki/Gerrit/Tutorial for more information.",1454939914,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,https://en.wikipedia.org/wiki/WP:Village_pump_%28technical%29?oldid=694005525#Edit_filter_problem,1449409097,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,This came up on the English Wikipedia again this week. Any chance of a fix? It seems like a pretty big issue that we are sometimes tagging and disallowing entirely the wrong edits.,1449066003,PHID-USER-ksxcfwf6vvnfvopbps4h,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"@He7d3r Hunm, well. At least the cause of this bug was identified, but the solutin does not seem to be simple...",1440343817,PHID-USER-fhga6fel7wefoxau7gvo,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"As far as I can see, they are the same thing;",1440341623,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"@He7d3r This bug is the cause of the problem related in  T100530, right?",1440340212,PHID-USER-fhga6fel7wefoxau7gvo,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"From the duplicated bug:
+
+>On
+>https://pt.wikipedia.org/wiki/Special:AbuseLog?wpSearchUser=189.5.174.202&wpSearchFilter=1&wpSearchTitle=Lygia+Moura+Rassi&uselang=en
+>we have two logs:
+>>* 13:39, 27 May 2015: 189.5.174.202 (Talk | block) triggered filter 1, performing the action ""edit"" on Lygia Moura Rassi. >Actions taken: Tag; Filter description: Remoção de proposta de eliminação (details | examine | diff)
+>>* 13:39, 27 May 2015: 189.5.174.202 (Talk | block) triggered filter 1, performing the action ""edit"" on Lygia Moura Rassi. Actions taken: Warn; Filter description: Remoção de proposta de eliminação (details | examine)
+>
+>For some reason AbuseFilter is using the same wikitext for both attempts to save the page. This is wrong! In fact, after the user received the warning, he fixed the issue and submitted the edit again, but the filter was triggered a second time, as if the user used the same wikitext twice. 
+>
+>Originally reported on
+>https://pt.wikipedia.org/wiki/WP:Filtro_de_edi%C3%A7%C3%B5es/1#Falsos_positivos",1440339986,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"I have found the cause: The problem is that edits through API (that is the difference, @Catrope [re your comment](https://phabricator.wikimedia.org/T99000#1283126)) pass through the AbuseFilter //twice//: The first time, via the `onAPIEditBeforeSave` hook, the second time via the `onEditFilterMergedContent` hook. Only the second hooks gets the post-merged content.
+
+And, because AbuseFilter makes sure it processes every edit only once, it sets `editAlreadyFiltered` in `filterEdit` and on every subsequent hook call for the same edit it just returns without further processing. It means AbuseFilter sees and processes the pre-merged content in `onAPIEditBeforeSave`, and ignores the post-merged content in `onEditFilterMergedContent`.
+
+You could check this by adding `unset($context->getTitle()->editAlreadyFiltered);` at the end of `onAPIEditBeforeSave` – the filter will run correctly the second time and see the postmerged content, however, the edit will be noted twice in the abuse log, so this is (obviously) not a correct solution.
+
+I’d think the correct solution would be to make a variant of `APIEditBeforeSave` hook which would include the post-merged text and AbuseFilter would then switch to that new hook. Maybe. (Or, some voodoo with making sure `APIEditBeforeSave` is read-only, immutable test-this-edit, saving nothing into the abuse log, and //not// setting the `editAlreadyFiltered` flag. But that could be a bit brittle, I guess.)",1431699235,PHID-USER-7clmfrlb7fwuko4jdjbs,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"@Oriodrim: Yep, I guessed the same in the linked dupe, AbuseFilter seems to see the pre-automerged version of edits from VisualEditor.",1431548624,PHID-USER-7clmfrlb7fwuko4jdjbs,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,readding VisualEditor: was removed without explanation and the correlation seems obvious.,1431548574,PHID-USER-jcypqodpdpbcicgwgh7j,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"I found how to reproduce this bug, at least in some cases. If you edit a page with VisualEditor and an automatic merge happens when you submit (i.e. someone submits a change between the moment you click ""edit"" and the moment you press ""submit""), then AbuseFilter sees the revision before the merge.
+",1417074693,PHID-USER-5h57zgttfaaarfvo4g6s,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,added VE Project as it's mentioned here and for all edits in merged T76063,1417033481,PHID-USER-jcypqodpdpbcicgwgh7j,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,"Here is another example on Portuguese Wikipedia:
+https://pt.wikipedia.org/wiki/Special:AbuseFilter/examine/log/1898713?uselang=en
+https://pt.wikipedia.org/w/index.php?diff=40613438&uselang=en
+The string ""{{ESR2|"" is in ""removed_lines"" but not in ""added_lines"". However, it should not be in the ""removed_lines"", because it is still in the new revision:
+https://pt.wikipedia.org/w/index.php?title=Zats_Boy&action=edit&oldid=40613438
+
+This was reported on
+https://pt.wikipedia.org/wiki/WP:CP?oldid=40613984#Falso_positivo_na_etiqueta",1416009035,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,(Adding 'hhvm' keyword just in case it's related to that.),1413030041,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit,Also: https://en.wikipedia.org/wiki/Special:AbuseLog?wpSearchUser=&wpSearchFilter=224&wpSearchTitle=M.R.+Organisation+Limited,1413023915,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mzsciyic2wqa2bvm4hc7,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link icon is missing in from the toolbar,"Screenshot
+
+Link inspector icon in the toolbar seems to be missing in 
+https://en.m.wikipedia.org/
+
+However, it is appearing in test2 and Betalabs.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14753}",1412900640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iykzkw3bnfenwugca5ap,task_description,resolved
+VisualEditor Mobile: [Regression] Link icon is missing in from the toolbar,"Argh, yes, this was fixed in wmf3 I believe.",1413917906,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iykzkw3bnfenwugca5ap,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link icon is missing in from the toolbar,Which browser? Link icon appears to be showing for me...,1413916039,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-iykzkw3bnfenwugca5ap,task_subcomment,NA
+VisualEditor: Bring back the edit summary byte counter in the save dialog,"It's ve-ui-mwSaveDialog-editSummary-count in MWSaveDialog, but there are several issues with it:
+
+* It should be stored in a variable, not searched for using jQuery .find() every time
+* It should be modified with methods on OO.ui.LabelWidget, not jQuery .text()
+* It should actually be visible
+
+I don't know why it's being hidden, but display: none; is set on it, so maybe .hide() is called somewhere?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412800080,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5xquomxdtu6ifmyxtnyo,task_description,resolved
+VisualEditor: Bring back the edit summary byte counter in the save dialog,"**gerritadmin** wrote:
+
+Change 165871 merged by jenkins-bot:
+Bringing back the edit summary byte counter in the save dialog
+
+https://gerrit.wikimedia.org/r/165871",1412890189,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5xquomxdtu6ifmyxtnyo,task_subcomment,NA
+VisualEditor: Bring back the edit summary byte counter in the save dialog,"**gerritadmin** wrote:
+
+Change 165871 had a related patch set uploaded by SuchetaG:
+Bringing back the edit summary byte counter in the save dialog
+
+https://gerrit.wikimedia.org/r/165871",1412888072,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5xquomxdtu6ifmyxtnyo,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a new image
+3.Open the media settings dialog again
+4.Click on ""Choose a different image"" button
+5.Select a different image
+6.Click on ""Apply Changes"" button
+
+Observed Result:
+
+User gets stuck inside Media Settings dialog.Cannot close the dialog anymore
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15264}",1412798520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ywep5k7o4fxifohcgdas,task_description,resolved
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,Verified the fix in production,1413502689,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ywep5k7o4fxifohcgdas,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,Verified the fix in test2,1412895852,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ywep5k7o4fxifohcgdas,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,Verified the fix in Betalabs,1412805547,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ywep5k7o4fxifohcgdas,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image,Fall-out from selection rewrite; fixed by Roan.,1412799699,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ywep5k7o4fxifohcgdas,task_subcomment,NA
+"VisualEditor: [Regression wmf3] For every Math expression, it is not appearing on CE when its gets evaluated for the first time","Screenshot
+
+Steps to reproduce:
+
+1.Open a new page with VE
+2.Go to Insert>Formula
+3.Insert ""\pi""
+
+Observe that, nothing appears on CE. But if you save the page or review your changes , you will see it actually got added in the page .
+
+If you reopen the page after saving, and try again adding the same math expression it will appear immediately.
+
+But if you try adding a different math expression or modify the existing math function , say for example: make ""\pi"" to ""\sqrt\pi"", it wont render on CE again. 
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71852
+
+**Attached**: {F15254}",1412797500,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-upmf46g433ncdqqvf7jl,task_description,resolved
+"VisualEditor: [Regression wmf3] For every Math expression, it is not appearing on CE when its gets evaluated for the first time","Verified the fix in Betalabs, test2 and en.wiki",1413836720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-upmf46g433ncdqqvf7jl,task_subcomment,NA
+"VisualEditor: [Regression wmf3] For every Math expression, it is not appearing on CE when its gets evaluated for the first time",Now appears to work in production. Success.,1413836449,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-upmf46g433ncdqqvf7jl,task_subcomment,NA
+"VisualEditor: [Regression wmf3] For every Math expression, it is not appearing on CE when its gets evaluated for the first time",Probably the same cause as bug 71852.,1413820239,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-upmf46g433ncdqqvf7jl,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,"demonstration from office-wiki
+
+When typing at the end of a line of an item in a bulleted list some character are duplicated or appear on the wrong line, delete/backspace behaves erratically.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+//attachment VE character insertion.m4v ignored as private//",1412796180,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_description,resolved
+VisualEditor: Extra characters being inserted when typing in bulleted lists,"This is the exact bug that https://gerrit.wikimedia.org/r/#/c/164514/ was designed to fix; Rachel F showed me the exact same thing the day before I wrote it. I don't think it ever got cherry-picked, but it should be on mediawiki.org some time later today as part of wmf3. We may need to cherry-pick it to wmf2.",1412844289,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,"yes just reproduced on mediawiki.org too on this page:https://www.mediawiki.org/wiki/User:RYasmeen_(WMF)?veaction=edit
+
+However, it does not happen in any other test wikis",1412814383,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,I didn't test on multiple platforms but I'm on Chrome 38.0.2125.101 beta / OS X 10.9,1412811711,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,I certainly didn't get a warm feeling while it was happening.,1412811665,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: Extra characters being inserted when typing in bulleted lists,This sounds bad.,1412811094,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-a2ijxws7hzmbqlcz7s2f,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert Cite>Website/News/Journal etc
+
+Observed Result:
+All citation notes are getting added as basic reference, opening them opens the basic reference dialog instead of the citation dialog.
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412795940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_description,resolved
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,Verified the fix in production,1413502870,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,Verified the fix in test2,1412895717,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,Verified the fix in Betalabs,1412805709,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,(Core pull-through not yet merged but otherwise fixed.),1412799291,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Change 165593 merged by jenkins-bot:
+Followup b8d8a5b: pass selections, not ranges, to SurfaceFragment#clone
+
+https://gerrit.wikimedia.org/r/165593",1412798773,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Change 165592 merged by jenkins-bot:
+Followup b8d8a5b: pass selections, not ranges, to SurfaceFragment#clone
+
+https://gerrit.wikimedia.org/r/165592",1412798655,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Change 165593 had a related patch set uploaded by Catrope:
+Followup b8d8a5b: pass selections, not ranges, to SurfaceFragment#clone
+
+https://gerrit.wikimedia.org/r/165593",1412798229,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Change 165592 had a related patch set uploaded by Catrope:
+Followup b8d8a5b: pass selections, not ranges, to SurfaceFragment#clone
+
+https://gerrit.wikimedia.org/r/165592",1412798180,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"This is happening because the references inserted by the citation dialog are empty, they don't have a template in them like they should.",1412796753,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference,"Created attachment 16719
+Screenshot
+
+**Attached**: {F15243}",1412796632,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nrc66pgj7y6cxhboa2o2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,"But not only when typing fast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412793540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4o73zjiapudkgirgztfc,task_description,resolved
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,Verified the fix in production,1413503004,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,Verified the fix for double-typing issue in test2,1412895685,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,The issue of double-typing of characters is resolved but the cursor is still appearing on readmode after saving the page.,1412805823,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,"Change 165537 merged by jenkins-bot:
+Followup b8d8a5b: fix stray check for !selection
+
+https://gerrit.wikimedia.org/r/165537",1412795872,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,"Change 165537 had a related patch set uploaded by Catrope:
+Followup b8d8a5b: fix stray check for !selection
+
+https://gerrit.wikimedia.org/r/165537",1412795302,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox,"Also, after saving a page or discarding an edit, the cursor appears on the Read Mode which could be a related issue, if not will file a separate bug later.",1412793830,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-4o73zjiapudkgirgztfc,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","While trying to login to betalabs i get ""404 file Not Found Error"" after clicking the Log In button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412783520,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-vi6faapr4iunjpanknxn,task_description,resolved
+"""404 file Not Found Error"" when logging into betalabs","Another example of why beta shouldn't have a diverged apache config from production.
+
+Docroot paths fixed in https://gerrit.wikimedia.org/r/165649
+
+Puppet force run on deployment-mediawiki0[1-3], apache and hhvm restarted.
+
+WFM now :)",1412807704,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs",http://login.wikimedia.beta.wmflabs.org/ is entirely down.  Normally there is a whole wiki there (albeit one normally used only for login).,1412804669,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","Raising priority (and changed summary) since most Flow browser tests are failing.
+
+Login through the API may be working.",1412804545,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","I can confirm comment 3, same outcome here, simply because http://login.wikimedia.beta.wmflabs.org/wiki/Special:CentralLogin/start does not exist.
+
+This feels unrelated to VE, hence correcting product/component.",1412800930,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","(In reply to Ritu Swain from comment #2)
+> > Also, URLs to reproduce the problem are welcome.
+
+I followed this link http://en.wikipedia.beta.wmflabs.org/wiki/User:Swainr?veaction=edit
+
+and clicked on Log in.After entering id and password in the page when I click on log in button it takes me to this page
+http://login.wikimedia.beta.wmflabs.org/wiki/Special:CentralLogin/
+> start?token=bbdd420df13bbf427dba8b3a38d6f947 .",1412797839,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","> Also, URLs to reproduce the problem are welcome.
+http://login.wikimedia.beta.wmflabs.org/wiki/Special:CentralLogin/start?token=bbdd420df13bbf427dba8b3a38d6f947",1412795851,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+"""404 file Not Found Error"" when logging into betalabs","How is that problem related to VisualEditor (which you set as a product here)? 
+I don't see VisualEditor mentioned in your steps to reproduce?
+Also, URLs to reproduce the problem are welcome.",1412793242,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vi6faapr4iunjpanknxn,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,"1. Open https://www.mediawiki.org/wiki/QA/Selenium_Workshop in latest stable Chrome.
+2. Click ""Edit""
+3. Put cursor in the first paragraph, insert a single character.
+
+Expected:
+
+Save button enables, allowing the user to save the page.
+
+Actual:
+
+Save button stays disable, user is unable to save the edit.
+
+No exceptions or warnings on the dev console.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412655300,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-c62cwehj54km2p5gebox,task_description,resolved
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,This appears to now be fixed in wmf3.,1413819814,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,Only happens on first click.,1412697829,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,Works for me in latest Chrome,1412697476,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,"This works fine if the first cursor position is in the Header, or before the first character of the paragraph. Very complex behaviour…",1412697301,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,Could this be fixed by https://gerrit.wikimedia.org/r/164514 ?,1412667718,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases,"It seems the model is consistently one character behind. When I worked-round the bug in comment #0 by backspacing over my new character and typing it again, and then changing another word on the page, clicking Save page and reviewing my change showed only the first word change in the wikitext diff.",1412655396,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-c62cwehj54km2p5gebox,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,"See https://office.wikimedia.org/w/index.php?diff=118847&oldid=118846
+
+Steps to reproduce:
+
+1.  Start with a paragraph that says ""Foo '''bar''' baz blah blah"".
+
+2.  Cut paragraph.
+
+3.  Paste paragraph elsewhere.
+
+4.  Notice that it now says """"Foo '''bar'''baz blah blah"" (i.e., minus one space immediately after the word in bold-face formatting).
+
+This also happened with <mark> formatting.
+
+This edit was made in Safari 6 on Mac OS 10.8.5.  I was not immediately able to reproduce this in Firefox 32.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412625180,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-fielr75hawu6al7yvwgb,task_description,resolved
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,Verified the fix in betalabs and test2.,1416264850,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,"Change 173256 merged by jenkins-bot:
+Safari copy-paste fix
+
+https://gerrit.wikimedia.org/r/173256",1416256303,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,"Change 173256 had a related patch set uploaded by Esanders:
+Safari copy-paste fix
+
+https://gerrit.wikimedia.org/r/173256",1416231976,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,*** Bug 73333 has been marked as a duplicate of this bug. ***,1415898350,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: Pasting annotated text causes space to be removed at annotation separators,*** Bug 72901 has been marked as a duplicate of this bug. ***,1415063629,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fielr75hawu6al7yvwgb,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"* Insert a reference (Cite > Basic)
+* Insert an MWLink node (Ctrl + K > http://www.amazon.com)
+
+Observe magic zero-width node. Converting to an annotation makes it work fine.
+
+Same happens in media caption dialogs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412470080,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_description,resolved
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"Change 167335 merged by jenkins-bot:
+Apply mw-body-content styles to SurfaceWidget
+
+https://gerrit.wikimedia.org/r/167335",1413587949,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"Change 167335 had a related patch set uploaded by Jforrester:
+Apply mw-body-content styles to SurfaceWidget
+
+https://gerrit.wikimedia.org/r/167335",1413586492,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,Verified the fix on test2.,1413577145,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"Change 166918 merged by jenkins-bot:
+Apply mw-body-content styles to SurfaceWidget
+
+https://gerrit.wikimedia.org/r/166918",1413420147,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"Change 166918 had a related patch set uploaded by Trevor Parscal:
+Apply mw-body-content styles to SurfaceWidget
+
+https://gerrit.wikimedia.org/r/166918",1413417420,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width,"This is because the CSS for these link nodes (and pretty much everything else from Parsoid CSS) is scoped to .mw-body-content, a class that we set on the main ce.Surface but not on surfaces inside of dialogs.
+
+I tried applying mw-body-content to the surface in the dialog, and that does cause the link node to appear, but it also messes up the font size. Someone with a better understanding of our various layers of font size manipulation (coughtrevorcough) should look at this.",1412495721,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-hnw54lb3tce7w3w2y7dx,task_subcomment,NA
+VisualEditor: The comment icon is repeatedly selected and deselected with the keyboard,"When selecting text with the keyboard (Shift-arrow), starting the selection range in adjacency to a comment icon repeatedly selects and deselects the icon. Starting the selection not in adjacency to the icon works as expected.
+
+If this is hard to understand, see this page:
+https://en.wikipedia.org/wiki/User:Amire80/comment
+
+It has detailed instructions to reproduce.
+
+This is broken in both LTR and RTL. RTL test page:
+https://he.wikipedia.org/wiki/%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%D7%AA:Amire80/ve-comment-selection
+
+Thanks to David Chan for helping with minimizing the test case :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/User:Amire80/comment",1412249460,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-bonyuszkfft3v3iimug2,task_description,resolved
+VisualEditor: The comment icon is repeatedly selected and deselected with the keyboard,This should have been resolved with the switch to native cursoring that goes out in wmf17. Please say if not.,1423676254,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bonyuszkfft3v3iimug2,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page","Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden appears while trying to save a page in Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1412186460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fv2akybq3ywgtzliagz5,task_description,resolved
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page",Verified the fix in production,1412888804,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page",Verified the fix in test2,1412292717,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page",Verified the fix in Betalabs,1412202398,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page","**gerritadmin** wrote:
+
+Change 164122 merged by jenkins-bot:
+Fix syntax error in mittoHidden selector
+
+https://gerrit.wikimedia.org/r/164122",1412197138,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf2] ""Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden"" appears while trying to save a page","**gerritadmin** wrote:
+
+Change 164122 had a related patch set uploaded by Catrope:
+Fix syntax error in mittoHidden selector
+
+https://gerrit.wikimedia.org/r/164122",1412186692,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fv2akybq3ywgtzliagz5,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","Environment- test2
+
+1> In VE, open Basic citation dialog and enter any citation(book,news,Web or Journal). For ex- enter a book citation.
+2> Now while the citation is still highlighted select Insert  -> Template.Notice the Add a Template window does not open , instead it opens the Cite Book dialog.
+
+But if you enter a book citation in the CE and while it is still highlighted try to open the Template dialog(Insert  -> Template) . Notice the Add a Template dialog opens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1412006940,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_description,resolved
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","Thank you once again :), will keep that in mind.",1412100712,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to Ritu Swain from comment #7)
+> (In reply to James Forrester from comment #6)
+> > (In reply to Ritu Swain from comment #5)
+> > > I checked with a clear history.It still does not open the ""Add a Template""
+> > > dialog ,when a  book citation is highlighted in Basic reference dialog.
+> > > 
+> > > Instead it opens the Cite Book dialog.
+> > 
+> > Oh, right, you weren't talking about the other bug in this report. Yes,
+> > opening any of the dialogs when you've selected that item (selecting a
+> > template and clicking the template button; an image and the media button; a
+> > reference and the reference button) will always open the item for editing
+> > rather than insert a new one, by design. Sorry for the confusion.
+> 
+> Thank you, i got it now. 
+> 
+> But when i try the above steps in the Content Editor or the Editor in the
+> Media Settings Caption.
+> 
+> For ex- 
+> 1> click on cite -> book and insert a book citation.
+> 2> Now while the citation is still highlighted select Insert  ->
+> Template.Notice the Add a Template modal opens , and not the Cite Book
+> dialog.
+> 
+> If this is how it is supposed to behave in different editors, then please
+> ignore this issue.
+
+It is. When you insert ""Cite > Book"" in the editor, it inserts a citation – a reference with a template inside it. When you try this inside a reference, it cleverly inserts the template, not a reference inside a reference (which isn't allowed). It's a little confusing, clearly. :-(",1412099011,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to James Forrester from comment #6)
+> (In reply to Ritu Swain from comment #5)
+> > I checked with a clear history.It still does not open the ""Add a Template""
+> > dialog ,when a  book citation is highlighted in Basic reference dialog.
+> > 
+> > Instead it opens the Cite Book dialog.
+> 
+> Oh, right, you weren't talking about the other bug in this report. Yes,
+> opening any of the dialogs when you've selected that item (selecting a
+> template and clicking the template button; an image and the media button; a
+> reference and the reference button) will always open the item for editing
+> rather than insert a new one, by design. Sorry for the confusion.
+
+Thank you, i got it now. 
+
+But when i try the above steps in the Content Editor or the Editor in the Media Settings Caption.
+
+For ex- 
+1> click on cite -> book and insert a book citation.
+2> Now while the citation is still highlighted select Insert  -> Template.Notice the Add a Template modal opens , and not the Cite Book dialog.
+
+If this is how it is supposed to behave in different editors, then please ignore this issue.",1412097130,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to Ritu Swain from comment #5)
+> I checked with a clear history.It still does not open the ""Add a Template""
+> dialog ,when a  book citation is highlighted in Basic reference dialog.
+> 
+> Instead it opens the Cite Book dialog.
+
+Oh, right, you weren't talking about the other bug in this report. Yes, opening any of the dialogs when you've selected that item (selecting a template and clicking the template button; an image and the media button; a reference and the reference button) will always open the item for editing rather than insert a new one, by design. Sorry for the confusion.",1412096168,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to James Forrester from comment #4)
+>
+> 
+> 
+
+I checked with a clear history.It still does not open the ""Add a Template"" dialog ,when a  book citation is highlighted in Basic reference dialog.
+
+Instead it opens the Cite Book dialog.",1412096017,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","I can't; have you refreshed?
+
+The citation template now opens as expected.",1412095049,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference","(In reply to James Forrester from comment #2)
+> I believe this has now been fixed and backported as part of the fix for bug
+> 71418.
+
+I can still reproduce it, in both test2 and beta.",1412089237,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference",I believe this has now been fixed and backported as part of the fix for bug 71418.,1412040334,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference",http://youtu.be/sy91ReXk_f4,1412007273,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ttqllxkghaqgjfflgrdp,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"1. Open VisualEditor
+2. Find or create a paragraph with a link followed by some non-linked text
+3. Inspect the link
+4. While the link inspector is open, click to drop the cursor in the non-linked text
+
+The link inspector does not close, and instead moves to follow your selection.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71151",1411770300,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_description,resolved
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,Verified the fix in test2 and production,1412367524,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,Merged into master and deployed to wmf1.,1412090473,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"Change 163852 merged by jenkins-bot:
+Followup b149390: fix dm.Surface's concept of ""selectedNode"" to match SurfaceFragment's
+
+https://gerrit.wikimedia.org/r/163852",1412086657,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"Change 163852 had a related patch set uploaded by Jforrester:
+Followup b149390: fix dm.Surface's concept of ""selectedNode"" to match SurfaceFragment's
+
+https://gerrit.wikimedia.org/r/163852",1412086525,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"Change 163783 merged by jenkins-bot:
+Followup b149390: fix dm.Surface's concept of ""selectedNode"" to match SurfaceFragment's
+
+https://gerrit.wikimedia.org/r/163783",1412084885,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"Change 163783 had a related patch set uploaded by Catrope:
+Followup b149390: fix dm.Surface's concept of ""selectedNode"" to match SurfaceFragment's
+
+https://gerrit.wikimedia.org/r/163783",1412037373,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"(In reply to Bartosz Dziewoński from comment #2)
+> Related? Bug 71151.
+
+Yes, absolutely. While investigating this, I wished I had ""git bisect concerning"" in addition to ""good"" and ""bad"". At first, nothing was wrong, then the flicker started happening, and now it doesn't close at all.
+
+I think this happened because Ed changed the context to reposition itself directly from events emitted by the surface. The surface also emits a contextChange event that causes the context to realize that it should close (or did; this bug is about that event not being emitted any more), but that event listener is debounced, so we close the context after moving it.",1411779222,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,Related? Bug 71151.,1411779053,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text,"This broke in https://gerrit.wikimedia.org/r/#/c/162495/ , which made it so contextChange is no longer emitted when the selection moves from inside a link to outside a link.",1411771797,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fvdvxsgxt5hfh5g5e7b6,task_subcomment,NA
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order","See https://office.wikimedia.org/w/index.php?diff=118520&oldid=118519
+
+This was all supposed to be on one line, essentially changing ===One=== to ===One and two===  It displays almost correctly, the equivalent of:
+
+===One and two===
+a
+
+but saves completely wrong:
+
+===One===
+ndtwoa
+
+
+James F has a screenshot in e-mail.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411756740,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qwganlrulofurpdkcbyf,task_description,resolved
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order",This is almost certainly a duplicate of the bug that was fixed by https://gerrit.wikimedia.org/r/#/c/164514/,1415656063,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-qwganlrulofurpdkcbyf,task_subcomment,NA
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order",Checked Safari/Chrome - cannot reproduce.,1415655941,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-qwganlrulofurpdkcbyf,task_subcomment,NA
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order",Looks like the issue we had in Safari selections that Ed fixed a couple of weeks ago?,1415046514,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qwganlrulofurpdkcbyf,task_subcomment,NA
+"VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order",Can't reproduce this issue...,1414802772,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-qwganlrulofurpdkcbyf,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"We have isValid() functions for similar inputs, but not this one, so it's possible to try to create a redirect to ""|"" (which Parsoid turns into MediaWiki:Badtitle).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411586340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_description,resolved
+VisualEditor: TitleInputWidget should validate inputs,"(In reply to etonkovidova from comment #8)
+> test2 has the same validation that is in betalabs: 
+> 
+> - cannot add Talk: as a template - 'Add template' is disabled
+> - cannot add a template or a  category with |(a pipe), < and > chars
+> - if 'Page settings' redirection has aforementioned  symbols -
+> MediaWiki:Badtitletext is displayed.  Does it need some improvement?
+
+That sounds like it covers all our needs.",1415229764,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"test2 has the same validation that is in betalabs: 
+
+- cannot add Talk: as a template - 'Add template' is disabled
+- cannot add a template or a  category with |(a pipe), < and > chars
+- if 'Page settings' redirection has aforementioned  symbols - MediaWiki:Badtitletext is displayed.  Does it need some improvement?",1415229722,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"Change 169623 merged by jenkins-bot:
+Introducing isValid() in MWTitileInputWidget
+
+https://gerrit.wikimedia.org/r/169623",1414606526,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"Change 169623 had a related patch set uploaded by SuchetaG:
+Introducing isValid() in MWTitileInputWidget
+
+https://gerrit.wikimedia.org/r/169623",1414539689,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,This is scarily close to what I filed bug 72468 about. While filing it I was thinking that an isValid() implementation should also be provided. I'll add that to that bug.,1414115463,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"(In reply to James Forrester from comment #3)
+> (In reply to Alex Monk from comment #1)
+> > Currently the redirect section of the page settings dialog and the template
+> > placeholder page use MWTitleInputWidget.
+> > 
+> > The template placeholder page can be fixed with a simple change from value
+> > === '' to !mw.Title.newFromText( value ) in
+> > MWTemplatePlaceholderPage#onTemplateInputChange. It will no longer allow you
+> > to add a template with an invalid name. No need for isValid here.
+> 
+> What happens when you use a parser function or a magic word?
+
+I imagine it would break. So let's not do that.
+
+> > As for the redirect settings, that seems more difficult. I don't think we
+> > should just silently ignore the value if it was set to an invalid title...
+> > And I don't think we should disable the apply button either.
+> 
+> We show ""invalid title"" for link searches; presumably that's evaluated
+> server-side?
+
+That is shown when the page does not seem to exist (based on the search results) and we get a false-y value from mw.Title.newFromText on the given title.",1413317234,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"(In reply to Alex Monk from comment #1)
+> Currently the redirect section of the page settings dialog and the template
+> placeholder page use MWTitleInputWidget.
+> 
+> The template placeholder page can be fixed with a simple change from value
+> === '' to !mw.Title.newFromText( value ) in
+> MWTemplatePlaceholderPage#onTemplateInputChange. It will no longer allow you
+> to add a template with an invalid name. No need for isValid here.
+
+What happens when you use a parser function or a magic word?
+
+> As for the redirect settings, that seems more difficult. I don't think we
+> should just silently ignore the value if it was set to an invalid title...
+> And I don't think we should disable the apply button either.
+
+We show ""invalid title"" for link searches; presumably that's evaluated server-side?",1412803664,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,Bump.,1412718616,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+VisualEditor: TitleInputWidget should validate inputs,"Currently the redirect section of the page settings dialog and the template placeholder page use MWTitleInputWidget.
+
+The template placeholder page can be fixed with a simple change from value === '' to !mw.Title.newFromText( value ) in MWTemplatePlaceholderPage#onTemplateInputChange. It will no longer allow you to add a template with an invalid name. No need for isValid here.
+
+As for the redirect settings, that seems more difficult. I don't think we should just silently ignore the value if it was set to an invalid title... And I don't think we should disable the apply button either.",1411602589,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-62x4lmlf5c4o37ouorno,task_subcomment,NA
+API XHR requests from mediawiki do not transmit cookies when editing,"Looking at the network traffic from visiting a page on enwiki, I saw that when editing a page (both with VE enabled and without it) a few GET requests get performed to API, like in example:
+
+https://en.wikipedia.org/w/api.php?format=json&uselang=en&action=visualeditor&paction=parse&page=Moravian-Silesian_Region
+
+these requests go out as XHR requests and my browser does not attach any cookie to the request. Of course, this means that any cookie-based test we might want to perform (like using HHVM) will not work as expected.
+
+This would effectively block us from testing hhvm on the API cluster.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1411540440,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-zxwfb74rzwpzfsgbjyzv,task_description,invalid
+API XHR requests from mediawiki do not transmit cookies when editing,"Upon further analysis; this happened because of a bug in a chromium adblocking extension I was using, which blocked cookies in GET requests to api based on a regex I must have added years ago. Disabling the adblocking extension effectively sent the cookies correctly.",1411571347,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-zxwfb74rzwpzfsgbjyzv,task_subcomment,NA
+API XHR requests from mediawiki do not transmit cookies when editing,"I cannot reproduce this. According to Firebug the cookies are being included in XHR requests to the API when I visit enwiki pages, including the request to https://en.wikipedia.org/w/api.php?format=json&uselang=en&action=visualeditor&paction=parse&page=Moravian-Silesian_Region if I enable the VE beta feature and then attempt to edit that page using VE.
+
+Further, I'd expect we'd have had many more bug reports if this were a widespread problem, since lacking cookies in the API requests would cause the VE edits to be performed as an IP.
+
+My browser is Iceweasel 32.0 (which is Debian's rebranded version of Firefox 32.0). While it shouldn't matter for this particular case, I have ""Accept third-party cookies"" set to ""Always"".
+
+
+At any rate, this certainly isn't an API bug since the API has no control over whether the client sends any cookies. I'm going to tentatively reassign it to ""JavaScript"".",1411569490,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-zxwfb74rzwpzfsgbjyzv,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,"No UI
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the link inspector/math inspector for an existing link
+3.Close the inspector by clicking on ""Done"" button or you can keep the inspector open
+4.Now scroll down the page so that the inspector goes outside the current surface
+5.Now click somewhere else in the document
+6.Now go back and reopen the previous inspector
+
+Observed Result:
+There is no UI for the inspector,if you try inspecting some other inspector on the current viewport that will also appear without any UI.
+
+for link inspector if you switch tab and come back to VE, the link inspector will have only the link target suggestions inside it .
+
+Environment: Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14854}",1411428360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mypudm3323akv2drcpva,task_description,resolved
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,Verified the fix in Production,1412283585,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,Verified the backport in test2,1411667828,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,Verified the fix in Betalabs,1411592274,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,"**gerritadmin** wrote:
+
+Change 162474 merged by jenkins-bot:
+Re-clip popups after resizing them
+
+https://gerrit.wikimedia.org/r/162474",1411509800,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,"**gerritadmin** wrote:
+
+Change 162474 had a related patch set uploaded by Catrope:
+Re-clip popups after resizing them
+
+https://gerrit.wikimedia.org/r/162474",1411508273,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document,"Created attachment 16543
+Link inspector
+
+**Attached**: {F14856}",1411428435,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mypudm3323akv2drcpva,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","video capture of the bug
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open any inspector-Link/Math/Special Character for any existing node
+3.Now while the inspector is open, place the cursor any where else in the document
+
+
+Observed Result:
+The inspector closes and flickers in the new position.
+
+See the video capture attached
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71373
+
+**Attached**: {F14852}",1411426740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_description,declined
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",I'm now not getting any flickering in Beta Labs or production. Fixed?,1421176141,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","I am still getting this issue in Betalabs.
+
+{F20118}",1418081747,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",Not seeing any flicker in master.,1418050687,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","Nope, still happening in en.wiki,test2 and Betalabs",1413832164,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","Nope, still happening in en.wiki,test2 and Betalabs",1413832159,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",This appears to now be fixed (testing on enwiki); can we confirm and close?,1413820149,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there","It's now worse, see bug 71373. I speculated about why this bug happens in bug 71373 comment 3.",1411779985,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",Nope this is still happening.I guess it has something to do with the code change in https://gerrit.wikimedia.org/r/#/c/160034/,1411591661,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+"VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there",Possibly now fixed?,1411588926,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wfdurzh7jsda4trl4dsh,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert a citation/a comment/math node
+3.Now place your cursor at the beginning of the node that you just added
+4.Drag the selection vertically, you will be able to do the selection over the next lines
+5.Now again place the cursor at the beginning of the node added in step 2
+6.Select the line of the node horizontally and then try to drag the selection vertically
+
+Observed Result:
+The selection stops at the focusable node and does not get extended towards the next lines.
+
+Environment:Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411418760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7cay56sblrqfurqj5hno,task_description,resolved
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,Verified the fix in production,1412888686,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7cay56sblrqfurqj5hno,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,Verified the fix in test2,1412361272,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7cay56sblrqfurqj5hno,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,"**gerritadmin** wrote:
+
+Change 162904 merged by jenkins-bot:
+Don't perform focus node native selection trick while dragging
+
+https://gerrit.wikimedia.org/r/162904",1411682242,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7cay56sblrqfurqj5hno,task_subcomment,NA
+VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node,"**gerritadmin** wrote:
+
+Change 162904 had a related patch set uploaded by Esanders:
+Don't perform focus node native selection trick while dragging
+
+https://gerrit.wikimedia.org/r/162904",1411660287,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7cay56sblrqfurqj5hno,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Formula
+3.Attempt to insert ""\pi"" inside the inspector
+
+Observed Result:
+As soon as you type \ in the inspector , it closes and tries to parse that \ and shows error ""Failed to parse (lexing error)""
+
+
+Environment:Betalabs
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1411413300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szea6r75prmyfpghqu7p,task_description,resolved
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Verified the fix in test2 and Betalabs,1413830221,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Moving back to ""FIXED"" and re-using bug 72136.",1413481348,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,*** Bug 72136 has been marked as a duplicate of this bug. ***,1413481134,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"But the difference is, this time it does not try to parse each time a character is inserted , just closes the inspector",1413422439,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,This started happening within last couple of hours,1413422340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Verified the fix in production,1412283461,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Verified the fix in test2,1411684245,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Verified the fix in Betalabs,1411591230,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Change 162495 merged by jenkins-bot:
+Calculate selected node on change and emit contextChange
+
+https://gerrit.wikimedia.org/r/162495",1411521450,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Change 162473 abandoned by Bartosz Dziewoński:
+ve.ui.Context: Prevent context changes during opening/closing inspectors better
+
+Reason:
+Ed probably knows better.
+
+https://gerrit.wikimedia.org/r/162473",1411513209,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Change 162495 had a related patch set uploaded by Esanders:
+Calculate selected node on change and emit contextChange
+
+https://gerrit.wikimedia.org/r/162495",1411512763,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"Change 162473 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ui.Context: Prevent context changes during opening/closing inspectors better
+
+https://gerrit.wikimedia.org/r/162473",1411507822,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,(The cause is probably 49a239b4b68719dc59bacf79e5186aceca881c58.),1411427135,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,"After dm.Surface emits 'contextChange', ve.ui.Context#afterContextChange thinks that the inspector should be closed, because `selectedNode !== this.lastSelectedNode` (this.lastSelectedNode is null). I spent way too much time debugging this and I still don't know why that happens. It worries me somewhat that `selectedNode` is a paragraph node rather than mwMath node.",1411424695,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,Focus issue?,1411420860,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it,It only closes when you're inserting a new formula. Editing existing ones doesn't have this problem.,1411420549,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-szea6r75prmyfpghqu7p,task_subcomment,NA
+[Regression] Jenkins: SQLite database is often locked causing queries to fail,"https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/11566/
+
+Artifact: mw-debug-www.log
+
+DatabaseBase::query: Writes done: REPLACE INTO objectcache (keyname,value,exptime) VALUES ('X')
+SQL ERROR (ignored): database is locked
+..
+
+
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR: database is locked
+..
+
+
+MessageBlobStore::insertMessageBlob failed to update DB: exception 'DBQueryError' with message 'A database error has occurred. Did you forget to run maintenance/update.php after upgrading?  See: https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script
+Query: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('en','jquery.ui.button','{}','20140919182152')
+Function: MessageBlobStore::insertMessageBlob/single-row
+Error: 5 database is locked
+
+
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: REPLACE INTO objectcache (keyname,value,exptime) VALUES ('X')
+SQL ERROR (ignored): database is locked
+..
+
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+SQL ERROR (ignored): database is locked
+DatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')
+...
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major",1411151220,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4sadouseu6almebfar54,task_description,duplicate
+[Regression] Jenkins: SQLite database is often locked causing queries to fail,"I don't think MediaWiki manages SQLite lock and concurrency at all.
+
+In this case, it seems two different Apache PHP threads are attempting to update the message cache.   For CI purposes, maybe we want to repopulate the message cache in the DB or skip it entirely to use the good old messages PHP files.",1411380617,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-4sadouseu6almebfar54,task_subcomment,NA
+Dates replaced by [[MediaWiki:Badtitletext]],"https://ast.wikipedia.org/w/index.php?title=Peligru_Mariellu&diff=747158&oldid=747157
+
+shows 1922 being replaced by [[MediaWiki:Badtitletext]].
+
+https://ast.wikipedia.org/w/index.php?title=Peligru_Mariellu&diff=747160&oldid=747159
+
+shows ""sieglu XX"" being replaced by [[MediaWiki:Badtitletext]].
+
+Nothing is known about the user's browser, skin, or OS.  It appears that the editor wrote this article at the Spanish Wikipedia, pasted the wikitext code into VisualEditor, and was trying to translate it into Asturian and correct the resulting nowiki mess when this happened.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411065120,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wicmfrektsx4wuuuhcwq,task_description,resolved
+Dates replaced by [[MediaWiki:Badtitletext]],"Without knowing anything more about what HTML parsoid got, this is hard to reproduce, so for now, I am going to presume this is an instance of the yet to be fixed T72960 (or the now fixed T72894) and close this. Please reopen if you have any additional information that can help.",1422986051,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-wicmfrektsx4wuuuhcwq,task_subcomment,NA
+Dates replaced by [[MediaWiki:Badtitletext]],"This may be a duplicate of bug 70960 if the user did insert a ""./"" in the link content part. Otherwise, it may be another instance of bug 70894. But leaving this open for now in case we can figure out more about what the user typed there in the links.",1411066072,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-wicmfrektsx4wuuuhcwq,task_subcomment,NA
+"VisualEditor: Overlay doesn't close, elements aren't clickable when copying dir=""auto"" values","1. Open any article
+2. Select the article title (firstHeading), copy, open the page settings, and set the default sort, and apply.
+3. try to click any element - it fails.
+
+Inspect element tells you there is ""ve-ui-overlay-global ve-ui-overlay"" over all...
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1410725100,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-qhmfjyurm2j53vu5lrbp,task_description,resolved
+"VisualEditor: Overlay doesn't close, elements aren't clickable when copying dir=""auto"" values",Fixed as part of the fixes for 70731.,1412359187,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qhmfjyurm2j53vu5lrbp,task_subcomment,NA
+"VisualEditor: [Regression wmf21] Cannot open any inspector, throwing error ""Uncaught TypeError: Cannot read property 'top' of undefined""","Steps to reproduce:
+
+1.Open a page with VE
+2.Try to open Link/Math/Language/Special Character inspector
+
+Observed Result:
+None of them opens and in the console it shows the following error:
+
+Uncaught TypeError: Cannot read property 'top' of undefined 
+
+Environment:test2.betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70770
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70768",1410551280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d4t2kxc6dwgul6wss43q,task_description,resolved
+"VisualEditor: [Regression wmf21] Cannot open any inspector, throwing error ""Uncaught TypeError: Cannot read property 'top' of undefined""",Verified the fix in production,1411683755,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d4t2kxc6dwgul6wss43q,task_subcomment,NA
+"VisualEditor: [Regression wmf21] Cannot open any inspector, throwing error ""Uncaught TypeError: Cannot read property 'top' of undefined""",Verified the fix in test2,1410823806,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d4t2kxc6dwgul6wss43q,task_subcomment,NA
+"VisualEditor: [Regression wmf21] Cannot open any inspector, throwing error ""Uncaught TypeError: Cannot read property 'top' of undefined""",Verified the fix in Betalabs.,1410559740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d4t2kxc6dwgul6wss43q,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"Environment- test2, beta
+
+1> open VE, I get JS console error as “Uncaught TypeError: Cannot read property 'top' of undefined” in Chrome.
+
+
+In FF the error is TypeError: rect is undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70782
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70768",1410526980,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ppbj4smgqgqx5ararami,task_description,resolved
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,Verified the fix in production,1411683636,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,Verified the fix in test2,1410823823,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,Verified the fix in Betalabs,1410559714,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"**gerritadmin** wrote:
+
+Change 160082 merged by jenkins-bot:
+ve.getStartAndEndRects returns null for empty rect lists
+
+https://gerrit.wikimedia.org/r/160082",1410559654,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"**gerritadmin** wrote:
+
+Change 160082 had a related patch set uploaded by Jforrester:
+ve.getStartAndEndRects returns null for empty rect lists
+
+https://gerrit.wikimedia.org/r/160082",1410553231,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"**gerritadmin** wrote:
+
+Change 160076 merged by jenkins-bot:
+ve.getStartAndEndRects returns null for empty rect lists
+
+https://gerrit.wikimedia.org/r/160076",1410552540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"**gerritadmin** wrote:
+
+Change 160076 had a related patch set uploaded by Catrope:
+ve.getStartAndEndRects returns null for empty rect lists
+
+https://gerrit.wikimedia.org/r/160076",1410552315,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"(In reply to Rummana Yasmeen from comment #4)
+> RoanKattouw, Try opening a new page with VE, you will get this error.
+
+Yup, that does the trick. Thanks.",1410550162,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"RoanKattouw, Try opening a new page with VE, you will get this error.",1410550034,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"I can't reproduce this, neither logged in nor logged out, neither on test2 nor on beta labs, using Chrome.",1410549264,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,"(In reply to Roan Kattouw from comment #1)
+> I can't reproduce this on test2. Does it happen when logged out as well?
+
+yes, it happens irrespective of my login status.",1410549010,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched,I can't reproduce this on test2. Does it happen when logged out as well?,1410543569,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ppbj4smgqgqx5ararami,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"I haven't tried to reproduce this.  
+
+I copied a page title from Meta and pasted it into VisualEditor on another wiki.  The text was set to =Page title= and highlighted in very pale blue, with a dashed line underneath, so I set it to Paragraph (that worked) and went to the character formatting menu to clear the formatting.  The 'Language' item was highlighted, so I chose that.
+
+The first time, the dialog box that popped up was tiny.  It was barely big enough to display the ""done"" button, which was overlapping with an odd ""$1 AUTO"" string in gray text.
+
+The second time, the dialog box looked normal, but 'Remove' didn't actually remove anything.  'Clear formatting' also doesn't remove anything.  
+
+Then the box got stuck open.  It would go away if I highlighted text, but 'Done' didn't close it and clicking outside it didn't close it.
+
+I was able to keep editing and to save the page when I was finished, but it produced <span dir=""auto""> tags, which I didn't want.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410461100,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-hqizdzws5eagirsav5rw,task_description,resolved
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"**gerritadmin** wrote:
+
+Change 160096 merged by jenkins-bot:
+(Kind of) fix treatment of strange dir values
+
+https://gerrit.wikimedia.org/r/160096",1410558535,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"**gerritadmin** wrote:
+
+Change 160098 merged by jenkins-bot:
+Don't return undefined in ve.init.mw.Platform#getLanguageName
+
+https://gerrit.wikimedia.org/r/160098",1410558397,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"**gerritadmin** wrote:
+
+Change 160098 had a related patch set uploaded by Catrope:
+Don't return undefined in ve.init.mw.Platform#getLanguageName
+
+https://gerrit.wikimedia.org/r/160098",1410558252,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"**gerritadmin** wrote:
+
+Change 160096 had a related patch set uploaded by Catrope:
+(Kind of) fix treatment of strange dir values
+
+https://gerrit.wikimedia.org/r/160096",1410557636,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language,"It looks like page titles (at least on meta, possibly elsewhere) are wrapped in <span dir=""auto"">, which is recognized as a language annotation (because it has a dir attribute) but doesn't work very well once it's considered a language annotation (because it has no lang attribute). I'll poke at this. Earlier, Amir reported a problem with pages containing <span dir=""rtl""> tags (also no lang attribute) so maybe this is semi-related.",1410464181,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-hqizdzws5eagirsav5rw,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,"link inspector
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Open a link inspector for any link
+3.Tap on the text box to bring up the link target suggestions
+
+Observed Result:
+Link target suggestion drop down are appearing cut off to a small size.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14991}",1410379500,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-poy4sfkajyxaov7ad2nl,task_description,resolved
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,Verified the fix in production for desktop and mobile iOS,1411681425,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-poy4sfkajyxaov7ad2nl,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,"Yes, this one got fixed in wmf 22.Marking it as fixed.",1411596190,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-poy4sfkajyxaov7ad2nl,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,"Created attachment 16476
+desktop
+
+**Attached**: {F14993}",1410817251,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-poy4sfkajyxaov7ad2nl,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector,"Created attachment 16475
+In desktop
+
+**Attached**: {F14992}",1410817198,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-poy4sfkajyxaov7ad2nl,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),"screenshot1
+
+Environment-test2,beta, production.
+
+1> open a page in VE, add a Basic citation.
+2>Click to add Basic citation again ,in the modal click on “Use an Existing Reference “.Select the citation that you just added.
+3>In the editor pane, delete all the citations.
+4> Select  to add Basic citation again. In the modal notice the “Use an Existing Reference “ button is  still active, although there are no citations to add to. Click on it and it opens a blank Reference modal.
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14787}",1410278760,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_description,resolved
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),Verified the fix in production,1411071391,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),Verified the fix in test2,1410553948,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),(Opened bug 70640 for that),1410308555,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),"This bug is about a very specific way to break the existing disabling of a different button. What you propose makes sense but it's not in scope here. I'll take a look into doing it anyway, but I'm going to re-close this bug.",1410307712,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),The Re-Use option in the Cite menu from the toolbar still remains enabled when there is no reference in the article.,1410306971,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),"**gerritadmin** wrote:
+
+Change 159423 merged by jenkins-bot:
+Properly mark reference search index as empty when setting internal list
+
+https://gerrit.wikimedia.org/r/159423",1410305209,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),Nice.,1410305119,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty),"**gerritadmin** wrote:
+
+Change 159423 had a related patch set uploaded by Alex Monk:
+Properly mark reference search index as empty when setting internal list
+
+https://gerrit.wikimedia.org/r/159423",1410304462,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gvnhzkjgz3cv6frzglkt,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","In Safari, Go to Insert>Media, try to enter something in the search box.
+you will get the following error in the console and wont be able to place your cursor in to the search box:
+
+
+api.php:1TypeError: 'undefined' is not a function (evaluating 'jQuery111102360369882080704_1410208128038({""warnings"":{""main"":{""*"":""Unrecognized parameter: 'uselang'""}},""query"":{""searchinfo"":{""totalhits"":0}}})')
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1410208200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhkhxz7oi6kric5dekys,task_description,resolved
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that",Verified the fix in production,1411683480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that",Verified the fix in test2,1410824448,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that",Verified the fix in Betalabs,1410821352,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","**gerritadmin** wrote:
+
+Change 160503 merged by jenkins-bot:
+Work around position: fixed; bug in Safari
+
+https://gerrit.wikimedia.org/r/160503",1410809008,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","**gerritadmin** wrote:
+
+Change 160503 had a related patch set uploaded by Catrope:
+Work around position: fixed; bug in Safari
+
+https://gerrit.wikimedia.org/r/160503",1410808890,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","This issue happens when you scroll down the page a bit and try adding reference/citation/media.
+
+This happens everywhere: Betalabs, test2, production.",1410806053,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that","This is happening for all citation dialogs, basic reference dialog, transclusion dialog, reference list dialog, Page Settings dialog.
+
+Environment:Betalabs",1410212007,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhkhxz7oi6kric5dekys,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,"Screenshot
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=Help:Extension:GlobalCssJs&veaction=edit
+
+**Attached**: {F14684}",1410197220,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-hsklb2fted77hcl6jkir,task_description,resolved
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,Verified the fix in production,1411071242,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,Verified the fix in test2,1410553903,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,"Yes.
+
+*** This bug has been marked as a duplicate of bug 70423 ***",1410198175,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,Isn't this bug 70423?,1410198066,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+VisualEditor: [Regression wmf20] Edit notice displays at half-width,Probably related to similar link inspector behaviour?,1410197987,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hsklb2fted77hcl6jkir,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"**Author:** `yaukasin`
+
+**Description:**
+zh-yue wikipedia does not load the stylesheets properly. When I view the source HTML code, I discover that there are many garbage stylesheets which would return error 404.
+
+Below is the code after the line <link rel=""canonical"" href=""......""> in zh-yue wikipedia 
+
+=============================================================
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.gadget.internalLinkHelper-altcolor&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.uls.nojs&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.visualEditor.viewPageTarget.noscript&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.wikihiero&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.legacy.commonPrint&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.legacy.shared&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.skinning.interface&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.ui.button&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=skins.vector.styles&amp;only=styles&amp;skin=vector&amp;*"" />
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=wikibase.client.init&amp;only=styles&amp;skin=vector&amp;*"" />
+=============================================================
+
+
+Below is the code after the line <link rel=""canonical"" href=""......""> in en wikipedia for comparison 
+
+=============================================================
+<link rel=""stylesheet"" href=""//bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&amp;lang=en&amp;modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cfeatured-articles-links%2CrefToolbar%2Cteahouse%7Cext.rtlcite%2Cwikihiero%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles%7Cwikibase.client.init&amp;only=styles&amp;skin=vector&amp;*"" />
+=============================================================
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major",1410180900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kinrik6hswrtg2xxwohw,task_description,resolved
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"Thanks for the quick investigation and fixing, Giuseppe!",1410204055,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"the patch has solved the problem, and now the page loads correctly.",1410199718,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"A patch for the problem has been created:
+
+https://gerrit.wikimedia.org/r/#/c/159080/",1410194886,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"While on varnish the url
+
+https://bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector&*
+
+returns 404, the same url without the final parameter returns correctly 200:
+
+https://bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector
+
+
+I confirmed that both urls, when properly translated, are answered with a 200 OK (and the same content) by the backend:
+
+https://zh-yue.wikipedia.org/w/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector
+ * 200 OK 26761
+https://zh-yue.wikipedia.org/w/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector&*
+ * 200 OK 26761
+
+So this seems to be an issue at the varnish layer.
+
+I'll update the ticket as I find out more.",1410188539,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+404 errors for CSS and HTML from Bits in zh-yue wikipedia,"Thanks for taking the time to report this!
+
+I went to https://zh-yue.wikipedia.org/wiki/%E9%A0%AD%E7%89%88?debug=true and using the ""Network"" tab of Firefox' developer tools there are a few 404s for HTML/CSS stuff from bits, like
+
+https://bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&lang=yue&modules=site&only=scripts&skin=vector&* which is a 404.
+
+Replacing lang=yue by lang=zh-yue works.
+
+According to Operations mailing list there were issues with Bits which started on Friday around 16:33 UTC due to a serialisation of requests for one specific uncacheable URL which was extremely slow to render and piled up requests, but that should have been sorted out / worked around. I'll ask on the list.",1410186906,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kinrik6hswrtg2xxwohw,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Image
+3.Try to type in a caption
+
+Observed Result:
+
+
+The text gets copied again in the text line and a pawn follows it.Also if you try to edit the caption of an existing image in a page , it is almost impossible to type in.
+
+Enviornment:Betalabs
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15068}",1409943240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ovmfajyzbve3uus6gktf,task_description,resolved
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,Verified the fix in production,1411080858,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,Verified the fix in test2,1410554134,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,Verified the fix in Betalabs,1409961065,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,"**gerritadmin** wrote:
+
+Change 158797 merged by jenkins-bot:
+Followup cb86c4f: fix call to renamed setChanged() function
+
+https://gerrit.wikimedia.org/r/158797",1409955776,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn,"**gerritadmin** wrote:
+
+Change 158797 had a related patch set uploaded by Catrope:
+Followup cb86c4f: fix call to renamed setChanged() function
+
+https://gerrit.wikimedia.org/r/158797",1409953884,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ovmfajyzbve3uus6gktf,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,"Screenshot
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15012}",1409878200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_description,resolved
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,Verified the fix in production,1411071931,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,Verified the fix in test2,1410554069,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,Verified the fix in Betalabs,1410377689,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari,Fixed in https://gerrit.wikimedia.org/r/#/c/159243/,1410374292,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ii2vmdvj7u6fxg2vyxax,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"See https://en.wikipedia.org/wiki/File:VisualEditorTableCopyBugScreenshot.jpg for what the editor selected.  See https://en.wikipedia.org/wiki/File:VisualEditorTableCopyBugScreenshot2.jpg (top) for what he got when he pasted it into the new place.
+
+This was found on Chrome and Windows 7.
+
+Also, if he used Ctrl-X to cut the table, he was unable to save his changes.  Clicking on the Save button did nothing after that point.  Ctrl-C to copy the table did not disable the Save button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409791740,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5nl2agli3yogyhbgab57,task_description,resolved
+Deleting from an empty paragraph to the end of an inline node throws an exception,Re-checked with 1.25wmf24 (32a0b3f). The fix works reasonably well - just make sure that the table is selected along with some text.  ,1428009677,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,In test2: selecting the above table and paste it will insert  the following symbol.☢,1427474126,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Verified in beta - for general cases it's fixed: tables can be copy/cut, the table format is preserved - and Save button is properly activated and functioning. 
+
+However, in the issue refers to  **the particular table example**( https://en.wikipedia.org/w/index.php?oldid=624091874 ) due to <ref name=""Tuck_U""></ref> will throw a lot of hiccups:
+``` {| class=""wikitable"" style=""font-size: 10pt; line-height: 11pt; margin-left: 2em; text-align: center; float: right""
+! 
+!
+Winter
+!
+<nowiki> </nowiki>Spring 
+!
+Summer 
+!
+Autumn 
+!
+Winter
+|-
+!
+1937
+| 
+| 
+| 
+| 
+| bgcolor=""#ccffff"" |1
+|-
+!
+1938
+| 
+| bgcolor=""#ccffff"" |2 
+| bgcolor=""#ccffff"" |3 
+| bgcolor=""#ccffff"" |4 
+| bgcolor=""#ccffff"" |5
+|-
+!
+1939
+| 
+| bgcolor=""#ccffff"" |6 
+| bgcolor=""#ccffff"" |7 
+| bgcolor=""#ccffff"" |8 
+| bgcolor=""#ccffff"" |9
+|-
+!
+1940
+| 
+| bgcolor=""#ccffff"" |10 
+| bgcolor=""#ccffff"" |11 
+| bgcolor=""#ccffff"" |12 
+|
+|-
+!
+1941
+| bgcolor=""#ccffff"" |13 
+| bgcolor=""#ccffff"" |14 
+| 
+| bgcolor=""#ccffff"" |15 
+|
+|-
+!
+1942
+| 
+| bgcolor=""#ccffff"" |16 
+| 
+| 
+|
+|-
+| colspan=""6"" style=""font-size: 8pt; text-align:left"" |Issues of ''Tales of Wonder'', showing issue number.
+Walter Gillings was editor throughout.<ref name=""Tuck_U""></ref>
+|}
+<br>
+
+``` 
+
+Try to select, copy, and cut the above table: 
+Uncaught Error: Offset could not be translated to a DOM element...
+Uncaught TypeError: Cannot read property 'isWrapped' of null...
+Uncaught Error: offset was inside a handlesOwnChildren...
+Uncaught Error: Invalid retain length, cannot retain backwards:...
+",1426703976,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Change 158662 merged by jenkins-bot:
+Fix unbalanced transaction when removing to/from the edge of an inline node
+
+[[https://gerrit.wikimedia.org/r/158662]]",1426180649,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Change 158662 had a related patch set uploaded (by Catrope):
+WIP Failing test case
+
+[[https://gerrit.wikimedia.org/r/158662]]
+",1426164999,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"**gerritadmin** wrote:
+
+Change 158662 had a related patch set uploaded by Esanders:
+WIP Failing test case
+
+https://gerrit.wikimedia.org/r/158662",1409943300,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Minimal failure case in core to trigger the unbalanced delete which is causing this to happen:
+
+<p></p>
+<p>a<span rel=""ve:Alien"">b</span></p>
+
+Select from the empty paragraph to after the b (range 1,6) and delete.",1409942098,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"The problem appears after the cutting, not after the pasting.  Also, it's usually possible to switch to source editing.  Consequently, this is only a lost-work bug for most people (anyone who doesn't know about or doesn't try switching to source.)",1409936955,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+Deleting from an empty paragraph to the end of an inline node throws an exception,"Update:
+
+To make this work, you have to select the table (just its own cells), without any text before and after.
+
+If you select more than the table (text + table + more text), then the table formatting appears to be correct when pasted in VisualEditor, but isn't actually correct when it's saved.  See https://en.wikipedia.org/w/index.php?oldid=624091874 for the saved version, and compare it to the same table in previous versions.  
+
+In addition to not being able to save after cutting and pasting, it's not possible to switch to source code editing.",1409875504,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5nl2agli3yogyhbgab57,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,"Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text
+3.Press commann+K
+
+
+Observed Result:
+Link inspector flickers and applies the link text as link target without showing any link target names.
+
+Environment:Betalabs
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1409766540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a6d7zyzurpoea557wxot,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,Verified the fix in Production,1410545647,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,Verified the fix in test2,1409871338,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,Verified the fix in Betalabs,1409856880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,"Change 158269 merged by jenkins-bot:
+Only focus the paste target if focusedNode has changed
+
+https://gerrit.wikimedia.org/r/158269",1409789018,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,"Change 158269 had a related patch set uploaded by Esanders:
+Only focus the paste target if focusedNode has changed
+
+https://gerrit.wikimedia.org/r/158269",1409785018,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off,Regression from https://gerrit.wikimedia.org/r/#/c/157199/,1409771041,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-a6d7zyzurpoea557wxot,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"The message https://translatewiki.net/wiki/MediaWiki:Visualeditor-dialog-action-insert/he was translated on August 21, but still doesn't appear in the Hebrew Wikipedia: https://he.wikipedia.org/wiki/MediaWiki:Visualeditor-dialog-action-insert .
+
+IRC:
+James_F	aharoni: Yeah, I've been looking at this.
+James_F	aharoni: It looks like the i18n job for VE-core hasn't run for a while.
+James_F	aharoni: I fixed it in If68193e7c3c78beeeb47975dc63ebaaec21448f3 and it worked… maybe that didn't stick?
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1409598060,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-7fusp4t2k553x5ynkjxt,task_description,resolved
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"(In reply to Amir E. Aharoni from comment #3)
+> The message that triggered this bug was imported successfully, so I guess
+> that it's fixed now
+
+And it still is.
+
+(In reply to Niklas Laxström from comment #4)
+> extensions//Parsoid/php/i18n/en.
+> json in
+
+That's not VisualEditor and it's caused by 9b986c9cb0169918d41e146096d4d73c3aca58f0
+Sent https://gerrit.wikimedia.org/r/162548 / I0bf1db4b8 (19edff5a)",1411540312,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,So REOPENED?,1411538585,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"This has been going since August 14th so there is something broken still:
+PHP Warning:  filemtime(): stat failed for /resources/projects/mediawiki-extensions/extensions//Parsoid/php/i18n/en.json in /www/translatewiki.net/w/extensions/Translate/utils/MessageGroupCache.php on line 196",1411538516,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"The message that triggered this bug was imported successfully, so I guess that it's fixed now, but I don't know what caused or what fixed it.",1411537716,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"Is this still a problem? If so, can someone (Niklas/Amir/?) on this bug help point out where the problem might be?",1411514972,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+[l10n] LocalisationUpdate doesn't seem to run for VisualEditor,"A better link to see that the translation is not updated:
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%99%D7%95%D7%97%D7%93%3A%D7%94%D7%95%D7%93%D7%A2%D7%95%D7%AA+%D7%94%D7%9E%D7%A2%D7%A8%D7%9B%D7%AA&prefix=Visualeditor-dialog-action-insert&filter=all&lang=he&limit=50",1409598873,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-7fusp4t2k553x5ynkjxt,task_subcomment,NA
+VisualEditor: Attempting to set an invalid range on undo,"1. Open a page with some content (a few paragraphs)
+2. Select all and delete
+3. Insert a math node
+4. Press undo
+
+You'll get an exception as selectionBefore in the undo stack is still the range of the whole original document, but your document should be empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409318940,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-gc45eius7aytam2rlpth,task_description,resolved
+VisualEditor: Attempting to set an invalid range on undo,"**gerritadmin** wrote:
+
+Change 157149 merged by jenkins-bot:
+Track selectionBefore in staging transactions
+
+https://gerrit.wikimedia.org/r/157149",1409336800,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gc45eius7aytam2rlpth,task_subcomment,NA
+VisualEditor: Attempting to set an invalid range on undo,"**gerritadmin** wrote:
+
+Change 157149 had a related patch set uploaded by Esanders:
+Track selectionBefore in staging transactions
+
+https://gerrit.wikimedia.org/r/157149",1409330992,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gc45eius7aytam2rlpth,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,"Screenshot
+
+the following error is appearing in the console while trying to open Math inspector:
+
+Uncaught TypeError: Cannot read property 'length' of null
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14629}",1408999440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x72zymsnartka42zou7j,task_description,resolved
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,Verified the fix in production,1409865451,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,Verified the fix in test2,1409261109,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,Verified the fix in Betalabs,1409075778,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,"This was fixed by https://gerrit.wikimedia.org/r/#/c/155831/ , don't know why it hasn't deployed to beta labs yet.",1409071611,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,This is still occurring in Betalabs while trying to open math inspector in an empty line.,1409013117,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console,Now appears to work for me – deployment issue?,1409011001,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-x72zymsnartka42zou7j,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media and insert an image
+3.Reopen the media settings dialog and change the image position to left/centre
+
+Observed Result:
+The following error appears in the con sole:
+Uncaught TypeError: Cannot read property 'length' of null 
+
+User gets stuck inside Media Settings dialog as it none of the button is working to escape from it.
+
+
+Environment:Betalabs
+Browser:Chrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408997580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_description,resolved
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,Verified the fix in production,1409865244,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,Verified the fix in test2,1409261969,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,Verified the fix in Betalabs,1409075454,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,"Change 156192 merged by jenkins-bot:
+Followup bbff57b, 8c71904: use getter for availableTools, again
+
+https://gerrit.wikimedia.org/r/156192",1409002854,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null,"Change 156192 had a related patch set uploaded by Mooeypoo:
+Validate availableTools before loop in Context's 'hasInspector'
+
+https://gerrit.wikimedia.org/r/156192",1409002079,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lwdlllmgxfie4lfk6ywk,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"In MWLinkTargetInputWidget and other places, we perform API requests that give us exactly the kind of information (existence, redirect status, etc.) that goes into ve.init.mw.LinkCache, but we don't write it to the link cache. We should do that, so we can save ourselves some API requests.
+
+Right now, when you make a link, we do another API request to check if the link should be blue or red, even if the link target came from a suggestion list and we already know it should be blue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408688640,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-goezj3fhvn2phuamifjy,task_description,resolved
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 159623 merged by jenkins-bot:
+Refactor a bunch of CategoryInputWidget code, tear out dead/broken redirect handling that should be rewritten
+
+https://gerrit.wikimedia.org/r/159623",1410920005,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 159623 had a related patch set uploaded by Alex Monk:
+Refactor a bunch of CategoryInputWidget code, tear out dead/broken redirect handling that should be rewritten
+
+https://gerrit.wikimedia.org/r/159623",1410387449,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Now just waiting for category existence checking, I believe?",1410376367,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 159418 merged by jenkins-bot:
+Update LinkCache in MWTitleInputWidget
+
+https://gerrit.wikimedia.org/r/159418",1410376147,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 159418 had a related patch set uploaded by Alex Monk:
+Update LinkCache in MWTitleInputWidget
+
+https://gerrit.wikimedia.org/r/159418",1410302500,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"(In reply to James Forrester from comment #3)
+> Do we want to do this from MWTitleInputWidget and MWCategoryInputWidget?
+
+Re-opening after discussing with Roan.",1410055508,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,Do we want to do this from MWTitleInputWidget and MWCategoryInputWidget?,1409266825,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 156955 merged by jenkins-bot:
+In LinkTargetInputWidget, put existence status into LinkCache
+
+https://gerrit.wikimedia.org/r/156955",1409264225,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc,"Change 156955 had a related patch set uploaded by Alex Monk:
+In LinkTargetInputWidget, put existence status into LinkCache
+
+https://gerrit.wikimedia.org/r/156955",1409260214,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-goezj3fhvn2phuamifjy,task_subcomment,NA
+VisualEditor: Return of the whitespace bunny-hopping bug,"This mess:
+
+[[Help:Installing Japanese character sets|<span class=""t_nihongo_icon"" style=""color: #00e; font: bold 80% sans-serif; text-decoration: none; padding: 0 .1em;"">?</span>]]) [[Category:Articles containing Japanese-language text]]
+
+was added in https://en.wikipedia.org/w/index.php?curid=31216768&diff=621842944&oldid=600210359
+
+to produce this:
+
+;Track & road events<ref name=""JAAF20120611"">[http://www.jaaf.or.jp/fan/news/2012/20120611.html {{Nihongo||ロンドンオリンピック トラック・フィールド種目・競歩種目の日本代表選手|The Japanese national team of Track & Field and Race Walk at the 2012 Olympic Games}}][[Help:Installing Japanese character sets|<span class=""t_nihongo_icon"" style=""color: #00e; font: bold 80% sans-serif; text-decoration: none; padding: 0 .1em;"">?</span>]]) [[Category:Articles containing Japanese-language text]]{{ja icon}}. Japan Association of Athletics Federations (2012-06-11). Retrieved 19 June 2012.</ref>
+
+The editor says s/he didn't edit this line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69876",1408640880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-htx2um5fnyusay6ynwua,task_description,resolved
+VisualEditor: Return of the whitespace bunny-hopping bug,"**gerritadmin** wrote:
+
+Change 155634 merged by jenkins-bot:
+Fix the newline bunny-hop bug harder
+
+https://gerrit.wikimedia.org/r/155634",1409133591,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-htx2um5fnyusay6ynwua,task_subcomment,NA
+VisualEditor: Return of the whitespace bunny-hopping bug,"(In reply to Gerrit Notification Bot from comment #2)
+> Change 155634 had a related patch set uploaded by Catrope:
+> Fix the newline bunny-hop bug harder
+> 
+> https://gerrit.wikimedia.org/r/155634
+
+This addresses the VE part of the bug. With this patch, VE will no longer corrupt whitespace around categories and the like (I've been seeing this a bunch in needcheck diffs, so that should fix those too). This will prevent Parsoid from corrupting the reference on this page, *unless* you edit it, in which case it'll still get messed up. I'll file a Parsoid bug for that.",1408655661,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-htx2um5fnyusay6ynwua,task_subcomment,NA
+VisualEditor: Return of the whitespace bunny-hopping bug,"**gerritadmin** wrote:
+
+Change 155634 had a related patch set uploaded by Catrope:
+Fix the newline bunny-hop bug harder
+
+https://gerrit.wikimedia.org/r/155634",1408654740,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-htx2um5fnyusay6ynwua,task_subcomment,NA
+VisualEditor: Return of the whitespace bunny-hopping bug,"Ugh, I found the cause, it's another whitespace bunny-hop bug.
+
+This whole mess is made because we have something like )[category] <span> and it gets turned into ) [category]<span> . The space jumps to the other side of the category.
+
+Additionally, there's a template leakage bug in Parsoid here. That parenthesis, category, space and span tag should have been marked as template-generated content but aren't. This means that if you try to edit this reference, Parsoid will make a big mess of it. As long as you don't edit it, it'll be fine, but the space jump bug in VE causes it to be edited.",1408650606,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-htx2um5fnyusay6ynwua,task_subcomment,NA
+Regression: Nested citations broken,"From https://bugzilla.wikimedia.org/show_bug.cgi?id=50749#c2
+
+Look at [[Otto I]].  It has 63 references, including ref #18 (""Thompson"") from explanatory footnote [d].  This ref doesn't appear in VisualEditor.
+
+http://en.wikipedia.org/wiki/Otto_I%2C_Holy_Roman_Emperor?oldid=621934593
+http://parsoid.wmflabs.org/enwiki/Otto_I%2C_Holy_Roman_Emperor?oldid=621934593
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408586580,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-t2avilcwnjfjpdywdken,task_description,resolved
+Regression: Nested citations broken,Now deployed. Please reopen if necessary.,1408997647,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-t2avilcwnjfjpdywdken,task_subcomment,NA
+Regression: Nested citations broken,"Change 155661 merged by jenkins-bot:
+(Bug 69827): Supported nested <ref> tags once more
+
+https://gerrit.wikimedia.org/r/155661",1408731167,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t2avilcwnjfjpdywdken,task_subcomment,NA
+Regression: Nested citations broken,"Change 155661 had a related patch set uploaded by Subramanya Sastry:
+(Bug 69827): Supported nested <ref> tags once more
+
+https://gerrit.wikimedia.org/r/155661",1408663367,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t2avilcwnjfjpdywdken,task_subcomment,NA
+Regression: Nested citations broken,This broke in https://gerrit.wikimedia.org/r/#/c/143362/,1408637619,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-t2avilcwnjfjpdywdken,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","I'm not sure why, but wgBetaFeaturesFeatures is incomplete on my local MediaWiki-Vagrant install.
+
+In the actual preferences UI, I see the following BetaFeatures:
+
+* Hovercards
+* Compact personal bar
+* Fixed header
+* VisualEditor
+* VisualEditor language tool
+
+But wgBetaFeaturesFeatures is only:
+
+{ popups: null, visualeditor-enable-language: null }
+
+That in turn means that these are the only ones looped over in betafeatures.js, which means other features don't have the JavaScript/browser blacklist processing.
+
+This bug affects production as well.
+
+Side note, you can use:
+
+.client-js .mw-ui-feature-requirements-javascript {
+  display: none;
+}
+
+for a simpler way to do the JS-hiding, but that doesn't address the underlying problem.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70371",1408581780,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-7336trfcokkmlnznz5wa,task_description,resolved
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","(In reply to Matthew Flaschen from comment #0)
+> Side note, you can use:
+> 
+> .client-js .mw-ui-feature-requirements-javascript {
+>   display: none;
+> }
+> 
+> for a simpler way to do the JS-hiding, but that doesn't address the
+> underlying problem.
+
+Done in https://gerrit.wikimedia.org/r/161690",1411238274,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","Underlying issue is only fixed by James's patch, but Seb35's patch has already fixed the display for the beta features I tested.",1411237957,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","**gerritadmin** wrote:
+
+Change 159538 merged by jenkins-bot:
+Populate $features even if there aren't any requirements
+
+https://gerrit.wikimedia.org/r/159538",1411237819,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","Ah, sorry. I meant https://gerrit.wikimedia.org/r/160213.",1411170587,PHID-USER-2nopae2cxuamwcbndaih,True,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences",https://gerrit.wikimedia.org/r/161629 should have resolved this bug. Is it confirmed?,1411170445,PHID-USER-2nopae2cxuamwcbndaih,True,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","This bug is a consequence of bug 70814, see https://bugzilla.wikimedia.org/show_bug.cgi?id=70814#c5 : the fix there correctly populates the wgBetaFeaturesFeatures array. (I make this bug depend of bug 70814, but it is similar to a duplicate.)",1411082291,PHID-USER-2nopae2cxuamwcbndaih,True,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences","**gerritadmin** wrote:
+
+Change 159538 had a related patch set uploaded by Jforrester:
+Populate $features even if there aren't any requirements
+
+https://gerrit.wikimedia.org/r/159538",1410379499,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-7336trfcokkmlnznz5wa,task_subcomment,NA
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox","Alt+Shift+F is shortcut for search box (very useful to validate a name of article...)
+
+Pressing Alt+Shift+F when the cursor is in the begining of article or in the dummy paragraph (slug) will cause a white pawn ♙ to appear. 
+
+(appears in https://he.wikipedia.org/wiki/%D7%90%D7%99%D7%9C%D7%9F_%D7%9E%D7%9C%D7%9B%D7%90?veaction=edit)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408566780,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-awpfthjrjritxkhujr46,task_description,resolved
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox",Fixed.,1421282422,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-awpfthjrjritxkhujr46,task_subcomment,NA
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox",(But can in Firefox.),1415813716,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-awpfthjrjritxkhujr46,task_subcomment,NA
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox",Cannot reproduce on Chrome...,1415813626,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-awpfthjrjritxkhujr46,task_subcomment,NA
+"VisualEditor: White pawn ""♙"" appears on Alt+Shift+F in Firefox",With which browser(s) was this tested?,1408571861,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-awpfthjrjritxkhujr46,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"Observed on iPad. Steps to repro:
+
+1. Go into VE edit mode on an article and enter the link inspector
+2. Use browser back to exit the link inspector
+
+Expected: you get a message asking if you want to abandon changes and get taken back to the content if you say yes
+
+Actual: no message about abandoning changes, and you're taken to the top of the page but can't scroll below the fold
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408143420,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_description,resolved
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,Verified the fix in production,1409866242,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,Verified the fix in Betalabs and test2,1409346227,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**jgonera** wrote:
+
+All patches merged, marking as fixed.",1409163492,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**gerritadmin** wrote:
+
+Change 155668 merged by jenkins-bot:
+Destroy WindowManagers in Context and Surface destructors
+
+https://gerrit.wikimedia.org/r/155668",1408665316,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**gerritadmin** wrote:
+
+Change 155668 had a related patch set uploaded by Catrope:
+Destroy WindowManagers in Context and Surface destructors
+
+https://gerrit.wikimedia.org/r/155668",1408665201,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**gerritadmin** wrote:
+
+Change 155657 merged by jenkins-bot:
+Remove global overlay classes when destroying MobileSurface
+
+https://gerrit.wikimedia.org/r/155657",1408664697,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**gerritadmin** wrote:
+
+Change 155657 had a related patch set uploaded by JGonera:
+Remove global overlay classes when destroying MobileSurface
+
+https://gerrit.wikimedia.org/r/155657",1408662224,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"(In reply to Juliusz Gonera from comment #3)
+> I thought it could be easily fixed by adding this.inspectors.clearWindows()
+I haven't reported this in Bugzilla yet, but I discovered yesterday that clearWindows() is completely broken. It will only clean up the current window (i.e. the one that's currently open), and it won't touch any others.
+
+> in ve.ui.Context.prototype.destroy, but unfortunately that results in:
+> 
+> ""Uncaught TypeError: Cannot read property 'getComputedStyle' of undefined ""
+> 
+> This happens when WindowManager invokes OO.ui.Window.prototype.hold. I
+> suspect it's because everything in WindowManager is async/delayed (to
+> accommodate for animations), so DOM nodes no longer exist when WindowManager
+> tries to tear windows down.
+Yeah that sounds likely. Maybe WindowManager needs a destroy function that destroys everything immediately? I also don't really understand why WindowManager not cleaning up is causing problems if the WindowManager's DOM element is removed.",1408575498,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**jgonera** wrote:
+
+This actually seems to be a VE/OOUI bug. The problem lies in WindowManager not cleaning up after itself.
+
+I thought it could be easily fixed by adding this.inspectors.clearWindows() in ve.ui.Context.prototype.destroy, but unfortunately that results in:
+
+""Uncaught TypeError: Cannot read property 'getComputedStyle' of undefined ""
+
+This happens when WindowManager invokes OO.ui.Window.prototype.hold. I suspect it's because everything in WindowManager is async/delayed (to accommodate for animations), so DOM nodes no longer exist when WindowManager tries to tear windows down.",1408575332,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/kzlyuZku",1408143915,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/ttlYWwkt",1408143613,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-omkq3ws5wkkdmzuc3v34,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"I copied part of a header from one page on se.wikimedia and pasted in an already started header on another page. After my paste the symbol ☀ was added:
+
+https://se.wikimedia.org/w/index.php?title=Projekt%3AWikidata_2014%2FAns%C3%B6kan_till_Vinnova&diff=34844&oldid=34843
+
+(Page I copied from: https://se.wikimedia.org/wiki/Projekt:Offentligkonst.se_2014/Ans%C3%B6kan_till_Vinnova )
+
+I used Google Chrome Version 35.0.1916.153 on Ubuntu 14.04.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408095180,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-k7nxqqgjeodo2osblgev,task_description,resolved
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"**gerritadmin** wrote:
+
+Change 154407 merged by jenkins-bot:
+Ignore whitespace when generating paste context
+
+https://gerrit.wikimedia.org/r/154407",1408299616,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"**gerritadmin** wrote:
+
+Change 154407 had a related patch set uploaded by Esanders:
+Ignore whitespace when generating paste context
+
+https://gerrit.wikimedia.org/r/154407",1408198388,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,This happens when pasting into any node with inner whitespace in it's Parsoid HTML (e.g. <h2> Foo </h2>),1408198195,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"Nevermind, managed to reproduce.",1408196413,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+VisualEditor: Pasting into nodes with whitespace inserts ☀,"Can you give more detailed steps to reproduce. Did you copy from read mode, or from VE? Where exactly did you select, and where exactly did you paste?",1408196281,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-k7nxqqgjeodo2osblgev,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","screenshot
+
+environment- test2, production, beta
+
+1> open page in VE, insert a comment.
+2> Open to edit the comment.
+3>Now click on the Text Style Menu and select  any style, for ex-Page Title or the Heading style.
+4> Notice the edit comment dialog turns blank.Please see screenshot.
+
+same behavior found in FF.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14201}",1407444600,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gynefzcsmqruipthvy7i,task_description,resolved
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".",Odd.,1418323355,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","This seems fixed now. Cannot Reproduce it anymore.
+Also see [[ https://phabricator.wikimedia.org/T78308 | T78308 ]]",1418315428,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","In addition to my previous comment: the edit comment pop-up box changes its display(the comment that being edited is still displayed, not blanked out).",1413918002,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","Confirmed test2, Betalabs, production (FF, Chrome). The error is displayed as the following: 
+
+Uncaught Error: Cannot set attributes on closing element VM86:325
+ve.dm.Transaction.newFromAttributeChangesVM86:325

+(anonymous function)VM86:699

+(anonymous function)VM86:45

+OO.ui.Process.executeVM86:45

+OO.ui.Window.teardownVM86:31

+(anonymous function)",1413847966,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","Issue is reproducible and is related to Bug 70888.Please ses ""Screenshot 1.25wmf2"".",1412608380,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".","Created attachment 16678
+Screenshot 1.25wmf2
+
+**Attached**: {F14202}",1412608303,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+"VisualEditor: Clicking on a block format control when edit comment dialog is open throws ""Uncaught TypeError:Cannot Read Property 'getSurface of null'"".",JS Console error- Uncaught TypeError:Cannot Read Property 'getSurface of null'.,1407446633,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gynefzcsmqruipthvy7i,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,".
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1407261180,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-mkys274ty5zb7zz3ixqh,task_description,resolved
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156494 merged by Catrope:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156494",1409102193,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156493 merged by jenkins-bot:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156493",1409102065,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156494 had a related patch set uploaded by Catrope:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156494",1409101958,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156493 had a related patch set uploaded by Catrope:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156493",1409101860,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156491 merged by jenkins-bot:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156491",1409101726,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+VisualEditor: Edit conflict message provides no button to actually resolve the conflict,"Change 156491 had a related patch set uploaded by Jforrester:
+Make the Resolve conflict button actually appear
+
+https://gerrit.wikimedia.org/r/156491",1409101616,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mkys274ty5zb7zz3ixqh,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**See also**
+* {T52512}
+* {T56140}",1407256980,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-i7jndqttvnweqczobiov,task_description,resolved
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","(In reply to JAn Dudík from comment #10)
+> really fixed?
+> https://cs.wikipedia.org/w/index.php?title=%C5%A0ablona:Infobox_-
+> _s%C3%ADdlo&diff=11940098&oldid=11761581
+
+It will be deployed to cswiki in a few hours…",1414081207,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","really fixed?
+https://cs.wikipedia.org/w/index.php?title=%C5%A0ablona:Infobox_-_s%C3%ADdlo&diff=11940098&oldid=11761581",1414068773,PHID-USER-wwnv7nzuscfuc2xfjwbq,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","Change 165908 merged by jenkins-bot:
+Add <noinclude> tags to new <templatedata> strings
+
+https://gerrit.wikimedia.org/r/165908",1412899303,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","Change 165908 had a related patch set uploaded by Mooeypoo:
+Add <noinclude> tags to new <templatedata> strings
+
+https://gerrit.wikimedia.org/r/165908",1412893139,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","(In reply to Alex Monk from comment #2)
+> Well how would we distinguish a documentation subpage from a ""proper""
+> template page?
+
+
+If the title has a ""/"" in it assume that it's OK to put in without <noinclude>s?",1412872641,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","This has caused a few problems on the en wiki. As I discuss at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=prev&oldid=628346583 it affected over 100 article space pages as anons and newer users have used the button and created template data blocks outside of <noinclude> tags. This then gets transcluded into main space articles. 
+
+Examples include
+ http://en.wikipedia.org/w/index.phptitle=Template:Roman_Catholic_Cathedrals_in_Great_Britain_and_Ireland&diff=prev&oldid=626352880 
+
+ http://en.wikipedia.org/w/index.php?title=Template:Punknews&diff=prev&oldid=628254485
+
+ http://en.wikipedia.org/w/index.phptitle=Template:List_of_Philippine_seas&diff=prev&oldid=625635816 
+
+ http://en.wikipedia.org/w/index.phptitle=Template:ABC_Mindanao&diff=prev&oldid=622140533 
+
+A list of page affect is at
+http://en.wikipedia.org/w/index.php?title=Wikipedia:TemplateData/List&oldid=628258871
+I've fixed all the current boken templates.",1412679935,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","I assume that the system would be essentially like this:
+
+* If the TemplateData is being added to Template:Foo, then add noinclude tags around it.
+* If the TemplateData is being added to Template:Foo/subpage, then check the name of the subpage.
+** If $local-variable is set, amd the subpage matches the local variable, then skip the noinclude tags.
+** If $local-variable is not set, and the subpage is $mw-default-subpage (which should be set to ""/doc""), then skip the noinclude tags.
+** Otherwise, assume the subpage is a real template and add noinclude tags.
+
+This means that the way it would work on some future Swahili Wikia is ""the local sysops would set the local variable"".  At the Swahili Wikipedia, local admins would set it to /hati (their preferred page name).
+
+If local sysops did not define the variable, and also didn't use the default subpage name, and someone added TemplateData to a documentation page that the extension treated as a real template, then it would get an ""extra"" set of noinclude tags (one that it adds and one that the doc page's transclusion adds).  I'm not sure that this would harm anything at all, but it's preseumably something to test.",1407276842,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","(In reply to WhatamIdoing from comment #3)
+> Otherwise, I think we'd have to make assumptions based on the page name. 
+> Different wikis use different names, but most use /doc (and/or one other
+> variant), and I've not yet seen an actual template subpage using those names.
+
+Okay, how do you plan for this to work on the ... Swahili Wikia? (if such a thing exists)",1407267571,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","It's possible that TemplateData could be noinclude'd no matter what. (Would nested noinclude tags cause problems?) 
+
+Otherwise, I think we'd have to make assumptions based on the page name.  Different wikis use different names, but most use /doc (and/or one other variant), and I've not yet seen an actual template subpage using those names.",1407262741,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags","Well how would we distinguish a documentation subpage from a ""proper"" template page?",1407258044,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags",Maybe. I'd rather we just fix bug 54140 instead.,1407257674,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-i7jndqttvnweqczobiov,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Go to the end of a line
+3.Press return to go the next line and click on link inspector or comment icon from the toolbar
+
+Observed Result:
+The link inspector and the comment box opens at the end of the previous line
+After adding a link or a comment it appears on the next line though.
+
+
+See the screenshot attached
+
+Environment:Betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14434}",1407184260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_description,resolved
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Got fixed with Ed's selection re-write I believe? I have not seen it happening recently too.Marking as fixed,1413931552,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Can't reproduce...,1413926325,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","(In reply to Rummana Yasmeen from comment #14)
+> This is again happening for both link inspector and comment box in Betalabs",1410816528,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",This is again happening for comment box in Betalabs,1410809568,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",*Verified the fix in production*,1410545461,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Verified the fix in Betalabs,1410545428,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Verified the fix in test2,1409872169,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Verified the fix in betalabs,1409856383,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Change 157868 merged by jenkins-bot:
+Don't use three different coordinate systems in getSelectionRect()
+
+https://gerrit.wikimedia.org/r/157868",1409789022,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Change 157868 had a related patch set uploaded by Catrope:
+Don't use three different coordinate systems in getSelectionRect()
+
+https://gerrit.wikimedia.org/r/157868",1409687356,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Created attachment 16282
+Screenshot
+
+This is still happening,the inspectors are now opening not at the end of previous line, but somewhere along the preceding 4/5 lines 
+
+See the screenshot attached, where I tried to add a link inside the bullet list and it appears at some position in page title.
+
+**Attached**: {F14435}",1409077912,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Change 155619 merged by jenkins-bot:
+Fallback to node position when getting selection rectangle
+
+https://gerrit.wikimedia.org/r/155619",1408652773,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Change 155619 had a related patch set uploaded by Esanders:
+Fallback to node position when getting selection rectangle
+
+https://gerrit.wikimedia.org/r/155619",1408651574,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","Yeah, selection is going very wonky here.",1407953415,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Language inspector also behaves in the same way,1407355267,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line",Right Alex :) This bug is not for mobile VE but for desktop. Sorry about that!,1407262535,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line","(In reply to Rummana Yasmeen from comment #0)
+> Created attachment 16137 [details]
+> Screenshot
+> 
+> Steps to reproduce:
+> 
+> 1.Open a page with mobile VE
+
+That screenshot does not appear to be from a mobile device...
+
+**Attached**: {F14434}",1407253023,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2didnifgbvsq7sszd23i,task_subcomment,NA
+"VisualEditor: In Betalabs,Media search is extremely slow, some images are not appearing and the progress bar keeps on moving infinitely","Screenshot
+
+Steps to reproduce:
+
+1.Open any page with VE
+2.Go to Insert>Media
+
+Observe that ,the progress bar is active on the text field and never stops
+If you retype the search string, the search results comes up but very slowly, some of the images are not even loading completely inside the dialog box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14212}",1406919000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wawq2es6xnwknziib6yf,task_description,resolved
+"VisualEditor: In Betalabs,Media search is extremely slow, some images are not appearing and the progress bar keeps on moving infinitely",Seems fine now.,1420843166,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wawq2es6xnwknziib6yf,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Happening on Betalabs and test2
+
+Cannot open the new comment box
+
+Getting following error in the console:
+TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406849160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k7yzoaid7tne2jeioxrh,task_description,resolved
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor",Verified the fix in production,1408654128,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor",Verified the fix in test2,1407275534,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor",*** Bug 69012 has been marked as a duplicate of this bug. ***,1406921057,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor",This was backported and deployed just now.,1406854389,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Change 150990 merged by jenkins-bot:
+Followup 23a949844: fix typo in class name for WhitespacePreservingInputWidget
+
+https://gerrit.wikimedia.org/r/150990",1406850776,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Change 150990 had a related patch set uploaded by Catrope:
+Followup 23a949844: fix typo in class name for WhitespacePreservingInputWidget
+
+https://gerrit.wikimedia.org/r/150990",1406850648,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Change 150989 merged by jenkins-bot:
+Followup 23a949844: fix typo in class name for WhitespacePreservingInputWidget
+
+https://gerrit.wikimedia.org/r/150989",1406850506,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor","Change 150989 had a related patch set uploaded by Catrope:
+Followup 23a949844: fix typo in class name for WhitespacePreservingInputWidget
+
+https://gerrit.wikimedia.org/r/150989",1406850179,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7yzoaid7tne2jeioxrh,task_subcomment,NA
+VisualEditor: Link inspector sets wrong title when clicking suggestion,"On enwiki:
+
+* Inspect an existing link
+* Type ""N"" in the text box
+* Click ""North America"" in the suggestions list
+* Click Done
+* Observe that the link now points to ""North American B-25 Mitchell""
+
+What seems to happen is:
+* you click North America
+* the textbox is changed to North America
+* a new suggestions list opens, with ""North America"" as the second item and ""North American B-25 Mitchell"" as the first
+* this closes again, setting the annotation to NAB25M while keeping the text as NA
+* when you click Done, the annotation is what's saved, not the text
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406829240,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ggojb6ctli2epykmy6k6,task_description,duplicate
+VisualEditor: Link inspector sets wrong title when clicking suggestion,"Still a dupe of bug 65343 :-)
+
+*** This bug has been marked as a duplicate of bug 65343 ***",1408668143,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ggojb6ctli2epykmy6k6,task_subcomment,NA
+VisualEditor: Link inspector sets wrong title when clicking suggestion,"Change 155673 had a related patch set uploaded by Trevor Parscal:
+Select the correct annotation in MWLinkTargetInputWidget
+
+https://gerrit.wikimedia.org/r/155673",1408666157,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ggojb6ctli2epykmy6k6,task_subcomment,NA
+VisualEditor: Link inspector sets wrong title when clicking suggestion,"
+
+*** This bug has been marked as a duplicate of bug 65343 ***",1408666007,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ggojb6ctli2epykmy6k6,task_subcomment,NA
+"VisualEditor: Triggering context on link after defocus throws ""TypeError: Cannot read property 'isCollapsed' of null""","1. Click on a link to show the context menu.
+2. Right click on the description of the link in the context menu (eg. name of page the link points to).
+3. Choose ""Inspect element"" which will defocus the page.
+4. Click on the link again, thus putting the cursor back in the page; somewhere in the linked word.
+
+After the context menu re-appears, a callback from AnnotagionInspector run via a OO.ui.Process throws:
+
+Uncaught TypeError: Cannot read property 'isCollapsed' of null 
+> ve.ui.AnnotationInspector.prototype.getSetupProcess = function () {
+>   ..
+>   .. fragment.getRange().isCollapsed()
+ (anonymous function) ve.ui.AnnotationInspector.js:159
+ (anonymous function) oojs-ui.js:3030
+ (anonymous function)
+ jQuery.extend.Deferred
+ promise.then
+ OO.ui.Process.execute oojs-ui.js:3067
+ OO.ui.Window.setup oojs-ui.js:1902
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406807880,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-j4fwj3nkikf5qqbm775b,task_description,declined
+"VisualEditor: Triggering context on link after defocus throws ""TypeError: Cannot read property 'isCollapsed' of null""",Can't reproduce.,1411594541,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-j4fwj3nkikf5qqbm775b,task_subcomment,NA
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","Shows that redirect page Save page (=Uložit stránku) is gray
+
+In this case, I am adding a template to the redirect page (delete template), but I cannot safe it. The safe button stay gray (attachment).
+
+Steps to reproduce this bug (Windows Vista, FF 31.0):
+1) open https://cs.wikipedia.org/w/index.php?title=Cristina_Fern%C3%A1ndez_de_Kirchner&redirect=no
+2) click on Edit
+3) Cencel options
+4) Insert > Template > Smazat (Add more information: 1; randoom text) > Insert template
+5) Save page = but you cannot!
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14552}",1406789640,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-5frqhlvurysfjreie4jc,task_description,resolved
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","Change 150772 merged by jenkins-bot:
+ve.ui.MWMetaDialog: Really *ALWAYS* return to normal tracking behavior
+
+https://gerrit.wikimedia.org/r/150772",1406793089,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5frqhlvurysfjreie4jc,task_subcomment,NA
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","Change 150772 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ui.MWMetaDialog: Really *ALWAYS* return to normal tracking behavior
+
+https://gerrit.wikimedia.org/r/150772",1406791818,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5frqhlvurysfjreie4jc,task_subcomment,NA
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","It gets better: the state of the 'Save' button stops being updated always when you open the ""Options"" dialog and cancel it instead of applying.",1406791707,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5frqhlvurysfjreie4jc,task_subcomment,NA
+"VisualEditor: State of 'Save' button stops being updated after opening and cancelling the ""Options"" dialog","Indeed.
+
+In step 4), it also suffices to just input any text – the ""Save"" button doesn't become enabled.
+
+However, if in step 3) you click ""Apply changes"" rather than ""Cancel"", everything works correctly.",1406790437,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5frqhlvurysfjreie4jc,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,"If an exception occurs while processing a transaction, we should roll it back safely, so the converter will still work and the user can still save or bail to source mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406768880,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_description,resolved
+Make VisualEditor transaction processing exception-safe,"Change 195361 merged by jenkins-bot:
+Make transaction processing exception-safe
+
+[[https://gerrit.wikimedia.org/r/195361]]",1426005844,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,"Change 195361 had a related patch set uploaded (by Catrope):
+Make transaction processing exception-safe
+
+[[https://gerrit.wikimedia.org/r/195361]]
+",1425933123,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,Operations are now queued but exceptions aren't caught yet.,1408586978,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,"Change 152776 merged by jenkins-bot:
+Queue up annotation changes to make operations safer
+
+https://gerrit.wikimedia.org/r/152776",1408586301,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+Make VisualEditor transaction processing exception-safe,"Change 152776 had a related patch set uploaded by Jforrester:
+Queue up annotation changes to make operations safer
+
+https://gerrit.wikimedia.org/r/152776",1407796877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-btr4z4bv5sp7jrbg3tc7,task_subcomment,NA
+VisualEditor: MWReferenceSearchWidget should only build the index if there isn't one or if it was built against a different version of the internal list,"Right now we build it blindly every time, which is inefficient. Can we listen to the internal list or get its hash or something so that we don't have to re-build except if a reference is added, removed or altered?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406766720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ihbbvcuqsgulvmjyinx7,task_description,resolved
+VisualEditor: MWReferenceSearchWidget should only build the index if there isn't one or if it was built against a different version of the internal list,"Change 151234 merged by jenkins-bot:
+Only build reference search index when it's been changed
+
+https://gerrit.wikimedia.org/r/151234",1408586168,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ihbbvcuqsgulvmjyinx7,task_subcomment,NA
+VisualEditor: MWReferenceSearchWidget should only build the index if there isn't one or if it was built against a different version of the internal list,"Change 151234 had a related patch set uploaded by Alex Monk:
+Only build reference search index when it's been changed
+
+https://gerrit.wikimedia.org/r/151234",1406932894,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ihbbvcuqsgulvmjyinx7,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add a reference (Basic/Citation)
+3.Check Re-use existing reference dialog (The reference appears in the dialog though the reference name is missing which is a different bug:https://bugzilla.wikimedia.org/show_bug.cgi?id=67342)
+4.Now add some citation/basic references 
+5.Check re-use existing reference dialog again
+
+Observed Result:
+Except the first one , none of the newly added references are appearing in the use existing dialog
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67342
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68582",1406743800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lhmoss6srr2f2jmg2mip,task_description,resolved
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,Verified the fix in production,1408048491,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,Verified the fix in test2,1407192079,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,"Change 150711 merged by jenkins-bot:
+Follow-up I569098: Rebuild reference list when reopening as it can change
+
+https://gerrit.wikimedia.org/r/150711",1406767181,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,"Change 150711 had a related patch set uploaded by Alex Monk:
+Don't refuse to rebuild reference list when reopening re-using existing citation widget
+
+https://gerrit.wikimedia.org/r/150711",1406758069,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening,"Could it be that the list of references in the ""Use existing"" panel is just never cleared?",1406747192,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lhmoss6srr2f2jmg2mip,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Place the cursor somewhere at the top of the page
+3.When the cursor is active on Ce and the keyboard is open, try scrolling down the page
+
+Observe dResult:
+Scrolling does not work
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406678220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aimwlbodlnjas75xvos2,task_description,resolved
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,Verified the fix for original issue in production.,1409866102,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"This seems to still be broken-ish due to bug 68832, which means you can't scroll all the way up to reveal the toolbar, but scrolling down works.
+
+Closing this one, we'll track the remaining problems over at bug 68832.",1409163669,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,This issue did not get resolved with the revert,1406765731,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"**jgonera** wrote:
+
+Should be fixed by https://gerrit.wikimedia.org/r/#/c/150719/",1406761757,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"This is happening now but following a different steps to reproduce:
+1.Open a page with Mobile VE
+2.Open link inspector
+3.Click on the ""Done"" button
+4.Once you are back to CE, tap on it to activate the cursor
+5.Now try scrolling up/down
+
+The scrolling wont work",1406753749,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,"Reopening it again,since I just reproduced it.",1406752883,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,Beta Labs gremlins.,1406748295,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE,This is also happening while scrolling down the link suggestions inside link inspector.,1406679123,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aimwlbodlnjas75xvos2,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"This is an apparent separate bug discovered in the course of bug 67805.
+
+Niklas suggested, ""LC issue is possibly caused by incorrect fallback merging, because L10nupdate contains update for ru, but not for uk (because the translation is already up to date for uk):""
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67805
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70686",1406604120,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-x6dj767aouujxepwm3oj,task_description,resolved
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"I think it's safe to mark this fixed now, although we still have to force-update all the l10n caches to make sure brokenness doesn't stay cached somewhere. Reedy says on IRC that he'll do that once he finishes the train deploy that's going on right now.",1409854129,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158423 merged by jenkins-bot:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158423",1409853304,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158421 merged by jenkins-bot:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158421",1409853199,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158422 merged by jenkins-bot:
+Use new LocalisationCacheRecacheFallback hook
+
+https://gerrit.wikimedia.org/r/158422",1409852370,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158423 had a related patch set uploaded by Reedy:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158423",1409852101,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158422 had a related patch set uploaded by Reedy:
+Use new LocalisationCacheRecacheFallback hook
+
+https://gerrit.wikimedia.org/r/158422",1409852064,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158421 had a related patch set uploaded by Reedy:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158421",1409852045,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),Now theoretically FIXED (once the code is deployed)?,1409851766,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158146 merged by jenkins-bot:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158146",1409850946,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158147 merged by jenkins-bot:
+Use new LocalisationCacheRecacheFallback hook
+
+https://gerrit.wikimedia.org/r/158147",1409842361,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"The problem is over-optimization: in LocalisationUpdate you're storing only the changed messages for each language, but that's causing problems when the current language doesn't have a change but a fallback language does. We've had this bug before, and it was worked around in r104041.
+
+Rather than doing the same thing as r104041 again and having this recur again the next time someone tries to optimize things, let's really fix it: LocalisationUpdate needs a hook to call for each fallback before it's merged into the final array, rather than one hook after we've already lost the information as to which language each message came from. But to do that, we have to rearrange the processing in LocalisationCache so it accumulates the data for each fallback language",1409768324,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158147 had a related patch set uploaded by Anomie:
+Use new LocalisationCacheRecacheFallback hook
+
+https://gerrit.wikimedia.org/r/158147",1409768303,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Change 158146 had a related patch set uploaded by Anomie:
+LocalisationCache: Process one fallback at a time
+
+https://gerrit.wikimedia.org/r/158146",1409768287,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"(In reply to Nemo from comment #5)
+> https://git.wikimedia.org/blob/mediawiki%2Ftools%2Fscap.git/HEAD/
+> bin%2FrefreshCdbJsonFiles (authors Bryan and Antoine, AFAICS).
+
+Yeah, I asked them. They said they didn't know anything about the actual generation of the json stuff.
+
+(In reply to Niklas Laxström from comment #6)
+> To clarify, are we talking about the json created by LocalisationUpdate
+> (which are then included in the CDB files by LocalisationCache), or the json
+> files created from the CDB files by the deployment scripts for efficient
+> syncing?
+
+There's two different json files? I'm glad I asked for help: I didn't know that it generated json files for the updated messages, then built cdbs, then generated more json files from the cdbs, and then generated cdbs again from the json files.
+
+I was referring to the json files that are created from the cdbs and then used to recreate the cdbs. Now that I know better how things work, I'm digging further into it.",1409755181,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"To clarify, are we talking about the json created by LocalisationUpdate (which are then included in the CDB files by LocalisationCache), or the json files created from the CDB files by the deployment scripts for efficient syncing?",1409722719,PHID-USER-732lqsmz4v6bss3kln2v,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"(In reply to Brad Jorsch from comment #4)
+> point to
+> who knows anything about the json-generating code.
+
+https://git.wikimedia.org/blob/mediawiki%2Ftools%2Fscap.git/HEAD/bin%2FrefreshCdbJsonFiles (authors Bryan and Antoine, AFAICS).",1409721483,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"(In reply to Greg Grossmeier from comment #3)
+> Niklas: Can you give any pointers to Brad to help him get up to speed on
+> this?
+
+More specifically, I tracked the problem down as far as ""the .json files are wrong"". When I asked around, you were the only person anyone could point to who knows anything about the json-generating code. Where do I find this code? If it's not going to be obvious, how generally does that code work? Is there a known way to run just the json-generator and output files to some temporary directory?",1409696180,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),Niklas: Can you give any pointers to Brad to help him get up to speed on this?,1409693137,PHID-USER-z3l4i7dl52qicxtephy5,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"(In reply to Brad Jorsch from comment #1)
+> So the problem seems to be in the (new JSON-based) l10nupdate process.
+
+Moving to ""Deployment systems""; feel free to move back.",1406714586,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?),"Further detail from bug 67805: ""I tracked that one as far as observing that the json file for uk that the cdb file gets built from has ""Править вики-текст"" as the value for messages:visualeditor-ca-editsource rather than ""Редагувати код"".""
+
+So the problem seems to be in the (new JSON-based) l10nupdate process.",1406633212,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-x6dj767aouujxepwm3oj,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","screenshot
+
+Environment- test2
+
+Steps-
+1>1> Open a blank page in VE and type in some text.
+2>At the end of the text insert a comment.
+3>Click on the Comment , to open the comment edit dialog.
+4> Now while the cursor is still in the comment edit dialog , click to insert a Template.
+5> As you start typing, add any template from the list that shows likely matches. For Example -select the “Bar” template.
+6>Type in Field name and insert the template.
+7>Notice the template does get added and then a snowman like character gets triggered after it.
+
+Behavior found in Chrome,FF and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14172}",1406561340,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_description,resolved
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","In FF, the highlight seems to mask the comment icon.See screenshot_FF.",1406919511,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Created attachment 16120
+screenshot_FF
+
+**Attached**: {F14173}",1406919391,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.",Issue fixed in beta and test2,1406751259,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.",Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660968,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659011,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658995,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658725,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656776,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646170,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646101,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645965,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645939,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645501,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645467,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630082,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594988,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","Change 149920 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406573312,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+"VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.","confirmed in betalabs. Try the template ""Bar chart""",1406562568,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-aezkk3hojhat5t2zwuar,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"If a paragraph contains a template, and VisualEditor is used to insert two characters somewhere after the template, and the second character is deleted with backspace, then the first character will be replaced by another character that is duplicated from several positions before that character.
+
+To reproduce, go to 
+
+https://en.wikipedia.org/w/index.php?title=User:AxelBoldt/Sandbox&oldid=618813650&veaction=edit
+
+and change the word ""Italian"" in the first sentence to ""Itaxxlian"", then delete the second x. Result: ""Itatlian"", where the second ""t"" results from duplication of the first ""t"". 
+
+This is a consequence of the IPA template earlier in the paragraph. The test file also contains a paragraph without template, where the bug does not occur, and a paragraph with a convert template, where the bug does occur.
+
+Wikipedia is at MW 1.24wmf15 and I'm on Windows 7 running Chrome 36.0.1985.125 m.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406552880,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_description,resolved
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660962,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),*** Bug 68789 has been marked as a duplicate of this bug. ***,1406659236,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659000,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658990,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658737,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656754,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646179,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646103,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645963,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645919,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645495,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645487,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630079,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594979,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Change 149920 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406573584,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"The effect seems to occur whenever you insert two or more characters in a paragraph after a template and then delete any one of them. The inserted characters do not have to be contiguous. The distance between first inserted character and duplicated character depends on the template.
+
+I believe VE internally uses the length of the unexpanded template where it should use the length of the expanded template.",1406567960,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),"Yeah, this looks a bit like bug 67862 but less severe.",1406566263,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?),Maybe related: bug 67862?,1406553462,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-bnbg6xhq6kx3wi7mwirb,task_subcomment,NA
+"VisualEditor: Remove media or templates, page loses focus","Take any article long enough to notice the effect (i.e. Cake on en.wp).
+Delete any of the pics at the bottom of the article.
+Notice the focus jumps back at the top.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58038
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68589",1406531520,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-sz5lbvh7j7kau3kukcw2,task_description,resolved
+"VisualEditor: Remove media or templates, page loses focus","Change 151400 merged by jenkins-bot:
+Set selection before focusing document
+
+https://gerrit.wikimedia.org/r/151400",1407065073,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sz5lbvh7j7kau3kukcw2,task_subcomment,NA
+"VisualEditor: Remove media or templates, page loses focus","Change 151400 had a related patch set uploaded by Jforrester:
+Set selection before focusing document
+
+https://gerrit.wikimedia.org/r/151400",1407064970,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sz5lbvh7j7kau3kukcw2,task_subcomment,NA
+"VisualEditor: Remove media or templates, page loses focus","It also happens with templates, so I'm guessing this is probably worrying but maybe a duplicate.",1406542869,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-sz5lbvh7j7kau3kukcw2,task_subcomment,NA
+VisualEditor: Weird behavior around a wikilink,"1) VEdit https://fr.wikipedia.org/wiki/Marie_Coutant?veaction=edit .
+
+2) Reach the end of the second paragraph, find the word Métivier.
+
+3) Start typing right before the ""M"" or after the ""r"". Pawns appear and random letters can appear in the word. Click on the word again, and watch letters and pawns multiply.
+
+4) Abandon the edit, go back to step 1 and 2.
+
+5) Add an ""h"" after the ""t"": Méthivier.
+
+6) Enter the link tool and click Supprimer to suppress the link.
+
+7) Notice the ""h"" has become an ""é"": Météivier. This is just an example, you can get different results adding other letters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406451840,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-y5us6kajeyeryt5odbuu,task_description,resolved
+VisualEditor: Weird behavior around a wikilink,I think this was caused by the pawning/snowmen issue that we fixed and pushed to production yesterday.,1406754678,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-y5us6kajeyeryt5odbuu,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"1. Create a document with two paragraphs, and make both of them entirely bold
+2. Put the cursor at the beginning of the first paragraph, and type a character. This character will be bold
+3. Put the cursor at the beginning of the second paragraph, and type a character. This character will not be bold
+
+#2 and #3 should be consistent. In fact, #2 *only* happens at the very start of the document, #3 happens everywhere else.
+
+The reason this is broken is that the code computing the new insertionAnnotations in ve.dm.Surface#setSelection by pulling from the left does not take paragraph boundaries into account at all. In case #3, it tries to pull from the left across the paragraph boundary, but because getAnnotationsFromOffset() doesn't work the way it thinks it does (the offset at the end of the first paragraph is a content offset, but getting its annotations returns an empty set) that doesn't work, and so text inserted at the beginning of this paragraph is not annotated. However, at the very start, the getRelativeContentOffset() call that computes the offset to the left bounces back and returns the offset to the right instead (1), so left === right, and we end up pulling from the right and bolding the inserted text.
+
+So really, the code is trying to achieve the wrong behavior (#2), but in most cases that breaks and we end up with the right behavior (#3). So the correct behavior is achieved completely by accident, except in one edge case where the code successfully achieves the wrong behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406337660,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ijstbrdms7lza5yyddte,task_description,resolved
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 155260 merged by jenkins-bot:
+Fix check for left/right annotations
+
+https://gerrit.wikimedia.org/r/155260",1408557331,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 150378 abandoned by Catrope:
+Fix pulling of annotations when typing at the beginning of the document
+
+Reason:
+https://gerrit.wikimedia.org/r/155260 fixes this bug
+
+https://gerrit.wikimedia.org/r/150378",1408557179,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 155260 had a related patch set uploaded by Catrope:
+Fix check for left/right annotations
+
+https://gerrit.wikimedia.org/r/155260",1408557160,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 150378 had a related patch set uploaded by Alex Monk:
+[WIP] Fix pulling of annotations when typing at the beginning of the document
+
+https://gerrit.wikimedia.org/r/150378",1406665375,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 150120 abandoned by Alex Monk:
+Fix pulling of annotations when inserting new character at start of document
+
+Reason:
+Breaks other things.
+
+https://gerrit.wikimedia.org/r/150120",1406665080,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null,"Change 150120 had a related patch set uploaded by Alex Monk:
+Fix pulling of annotations when inserting new character at start of document
+
+https://gerrit.wikimedia.org/r/150120",1406598969,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ijstbrdms7lza5yyddte,task_subcomment,NA
+"VisualEditor: Putting cursor after reference list throws ""offset was inside a handlesOwnChildren node"" error","Steps:
+
+1. Open http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+2. Scroll to bottom
+3. Place cursor in slug between gallery and references list
+4. Cursor right twice
+
+Expected outcome: Cursor ends up in slug at end of the page after the references list
+
+Actual outcome: Error thrown: ""offset was inside a handlesOwnChildren node""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit",1406321880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zwrntrbhezfc6nqksazy,task_description,resolved
+"VisualEditor: Putting cursor after reference list throws ""offset was inside a handlesOwnChildren node"" error","Change 155260 merged by jenkins-bot:
+Fix check for left/right annotations
+
+https://gerrit.wikimedia.org/r/155260",1408557334,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zwrntrbhezfc6nqksazy,task_subcomment,NA
+"VisualEditor: Putting cursor after reference list throws ""offset was inside a handlesOwnChildren node"" error","Change 155260 had a related patch set uploaded by Esanders:
+Fix check for left/right annotations
+
+https://gerrit.wikimedia.org/r/155260",1408542960,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zwrntrbhezfc6nqksazy,task_subcomment,NA
+"VisualEditor: Putting cursor after reference list throws ""offset was inside a handlesOwnChildren node"" error","This doesn't seem to be related to focusable nodes or the end of the document. All you need to do is put the cursor in a block slug after a references list.
+
+Suppose the references list is at (23,25). What happens is this:
+* setSelection (25,25) is called
+* It tries to compute insertion annotations by pulling from the left
+* It does so by calling getNearestContentOffset( 24, -1 )
+* Two stack levels deeper, getRelativeOffset() notices that 24 is inside of a handlesOwnChildren node and throws an exception
+
+Questions:
+* Why is reference list a handlesOwnChildren node? Is it because <ref> can be nested inside of <references>?
+* Why do we do offset-1 here? There is a Math.max() to guard against ending up at -1, but this bug uncovers another reason why subtracting one from an offset is dangerous and should ideally never be done",1406575296,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-zwrntrbhezfc6nqksazy,task_subcomment,NA
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,"VE get stucks when saving settings
+
+How to reproduce:
+1) click ""Options"" and then ""cancel""
+2) click ""Advanced settings"" and then ""apply changes""
+
+After this it gets stuck. It's ""applying changes"" even if you didn't do any changes. You must reload the page to make your changes again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406298300,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-xlnqf77fujlvuvwewshn,task_description,resolved
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,"Yes, this is fixed in wmf15 (as on MediaWiki.org right now) but not in wmf14 (on enwiki etc.).",1406307422,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xlnqf77fujlvuvwewshn,task_subcomment,NA
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,I think Ed fixed this in Gerrit change 148671,1406302133,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-xlnqf77fujlvuvwewshn,task_subcomment,NA
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,"(In reply to Alex Monk from comment #1)
+> Can't reproduce this issue.
+> 
+> Stryn, do you get an error in the JS console when this happens?
+
+Yup, with Firefox and Chrome
+
+Firefox gives:
+TypeError: bindings[i] is undefined load.php:608
+
+and Chrome:
+Uncaught TypeError: Cannot read property 'context' of undefined VM51:8oo.EventEmitter.disconnect VM51:8ve.ui.MWCategoriesPage.teardown VM53:224(anonymous function) VM53:229(anonymous function) VM51:42OO.ui.Process.execute VM51:43OO.ui.Dialog.executeAction VM51:33OO.ui.ProcessDialog.executeAction VM51:74OO.ui.Dialog.onActionClick VM51:31oo.EventEmitter.emit VM51:7oo.EventEmitter.emit VM51:7OO.ui.ButtonWidget.onClick VM51:102proxy load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20140724T1…:6jQuery.event.dispatch load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20140724T1…:65elemData.handle",1406302013,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-xlnqf77fujlvuvwewshn,task_subcomment,NA
+VisualEditor: VE gets stuck when applying changes to settings window the second time it's open,"Can't reproduce this issue.
+
+Stryn, do you get an error in the JS console when this happens?",1406298858,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-xlnqf77fujlvuvwewshn,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","screenshot
+
+Test Environment-test2 and betalabs
+Steps-
+1> open a blank page in VE.
+2>type some text and at the end of the last character (could be a space after the text or the last character in the text itself) insert a comment.
+3>Now click to move the cursor after the comment, this closes the comment dialog too.
+4> Insert a whitespace.I cannot see the cursor at this point.
+5> click on the page again and the cursor appears before the start of the line. 
+6>Hit the spacebar and then press backspace key. A pawn appears next to the comment. Please see screenshot_chrome.
+
+In Safari-
+Try the same steps and at step#6 I get the WebKit2WebProcess.exe  dialog saying “WebKit2WebProcess.exe has encountered a problem and needs to close.”. After I click to send the error report and I get logged out of my account. 
+
+In FF 31- no issues were found when whitespace was inserted after a comment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14311}",1406242920,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_description,resolved
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","(In reply to James Forrester from comment #9)
+> (In reply to Ritu Swain from comment #8)
+> > thank you. just for future.. this is not the right forum ..
+> 
+> No problem. :-)
+> 
+> > but how can i find the  release version of beta?
+> 
+> Unhelpfully, it's not present of beta (because it doesn't exist yet), but
+> the specific version of VisualEditor can be found inside VE itself:
+> 
+> If you go to a page and enter VisualEditor, click on the help menu – ""(?)""
+> in the toolbar on the right (left if RTL). The version hash will be at the
+> bottom of the menu.
+> 
+> mediawiki.org is currently running ""Version ce427f4 18:49, 29 July 2014"".
+> 
+> en.wikipedia.beta.wmflabs.org is currently running ""Version 3dd63f7 20:00,
+> 30 July 2014"".
+> 
+> > if a bug is not reproducible in beta , but it is in test2 , then can it be
+> > called fixed?
+> 
+> Normally, as long as we think it's actually fixed. Sometimes other changes
+> can have ripple effects, but sometimes it's caused by the local wiki's
+> configuration (or something else), so it's not a perfect call each time,
+> sadly.
+
+thank you :)",1406755410,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","(In reply to Ritu Swain from comment #8)
+> thank you. just for future.. this is not the right forum ..
+
+No problem. :-)
+
+> but how can i find the  release version of beta?
+
+Unhelpfully, it's not present of beta (because it doesn't exist yet), but the specific version of VisualEditor can be found inside VE itself:
+
+If you go to a page and enter VisualEditor, click on the help menu – ""(?)"" in the toolbar on the right (left if RTL). The version hash will be at the bottom of the menu.
+
+mediawiki.org is currently running ""Version ce427f4 18:49, 29 July 2014"".
+
+en.wikipedia.beta.wmflabs.org is currently running ""Version 3dd63f7 20:00, 30 July 2014"".
+
+> if a bug is not reproducible in beta , but it is in test2 , then can it be
+> called fixed?
+
+Normally, as long as we think it's actually fixed. Sometimes other changes can have ripple effects, but sometimes it's caused by the local wiki's configuration (or something else), so it's not a perfect call each time, sadly.",1406752805,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","thank you. just for future.. this is not the right forum .. but how can i find the  release version of beta?
+
+if a bug is not reproducible in beta , but it is in test2 , then can it be called fixed?",1406750788,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","Sorry, yes, I meant wmf16. My apologies!",1406749936,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","(In reply to James Forrester from comment #5)
+> Sounds like it was fixed in wmf15 then.
+
+a bit confused, i can reproduce it in test2 with the release version  1.24wmf15 (148011a).",1406749890,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.",Sounds like it was fixed in wmf15 then.,1406653811,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","(In reply to Alex Monk from comment #3)
+> I can't reproduce this now, Roan couldn't either. Ritu, does this still
+> happen for you?
+
+I can reproduce it in test2 , but not in beta.",1406652638,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","I can't reproduce this now, Roan couldn't either. Ritu, does this still happen for you?",1406579105,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.",Confirmed,1406314736,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.","did a fresh install of Safari, still getting WebKit2WebProcess.exe message.",1406260958,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-yz4c2eic4amw552h2kwd,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Page Settings option>Categories
+3.Try to add categories 
+
+Observed Result:
+After typing into a category name, it getting added twice and trying again throws error:
+
+TypeError: categoryItem is undefined 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14192}",1406155680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hixyotclnt74wvydoglc,task_description,resolved
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Verified the fix in production,1408653602,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Verified the fix in test2,1408051414,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Hmm, I can't either. Marking it as fixed.",1407349730,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",And I can't reproduce it on deployment-prep any more. Rummana?,1407323599,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Also, I am getting a different error this time while closing the dialog second time:
+Uncaught TypeError: Cannot read property 'disconnect' of undefined",1407276641,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Can now successfully reproduce on deployment-prep, but not my local wiki...",1407273736,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",This is still happening on Betalabs,1407267273,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Silly Gerrit.,1407262706,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Change 151088 merged by jenkins-bot:
+Tear down meta dialog pages when cancelling
+
+https://gerrit.wikimedia.org/r/151088",1407262656,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","The patch is not even merged yet, assuming the bug was closed by mistake.",1407261384,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Change 151088 had a related patch set uploaded by Alex Monk:
+Tear down meta dialog pages when cancelling
+
+https://gerrit.wikimedia.org/r/151088",1406904459,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined","Reproduced it today following these steps
+
+1.Open a page with VE
+2.Go to Page Settings option>Categories
+3.Type a category name in the text field
+4.When the drop down box appears, close the dialog
+5.Again, reopen the Page Settings option>Categories
+6.Now select a category from the drop down box
+
+Observed Result:
+
+It gets added twice,if you cancel the dialog box again it will throw the error:
+TypeError: categoryItem is undefined 
+
+If you reopen the Page Settings option>Categories, you will get stuck inside it.",1406850704,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Seems to be working again. Probably a deployment gremlin. Again. :-(,1406320458,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined",Can't reproduce...,1406314616,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hixyotclnt74wvydoglc,task_subcomment,NA
+Upgrade gerrit to 2.12,"Please upgrade gerrit to 2.12.
+
+Following plugins needs to be tested and fixed in the new version (and blocks an upgrade):
+
+```
+its-phabricator	2.8.1	Enabled
+its-phabricator-from-bugzilla	2.8.1	Enabled
+github-create-1.0-rc0	1.0-rc0	Enabled
+deleteproject	2.8.1	Enabled
+```
+
+Release notes for 2.12 are at https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.12.html
+
+--------------------------
+See Also: T65847",1405777980,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_description,resolved
+Upgrade gerrit to 2.12,"Change 300815 abandoned by Chad:
+TESTING STUFF
+
+Reason:
+Yay stuff works now.
+
+[[https://gerrit.wikimedia.org/r/300815]]",1469459058,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300815 had a related patch set uploaded (by Chad):
+TESTING STUFF
+
+[[https://gerrit.wikimedia.org/r/300815]]
+",1469458877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"```
+2016-07-25
+
+    03:26 hashar: scandium: migrating zuul-merger repos from lead to gerrit.wikimedia.org: find /srv/ssd/zuul/git -path '*/.git/config' -print -execdir sed -i -e 's/lead.wikimedia.org/gerrit.wikimedia.org/' config \;
+    02:03 ostriches: gerrit: reindexing lucene now that we have new data. searches/dashboards may look a tad weird for a bit
+    01:53 hashar: starting Zuul
+    01:51 mutante: restarted grrrit-wm
+    01:39 ostriches: lead: turning puppet back on, here we go
+    01:38 jynus: m2 replication on db2011 stopped, master binlog pos: db1020-bin.000968:1013334195
+    01:37 hashar: scandium: restarted zuul-merger
+    01:36 ostriches: ytterbium: Stopped puppet, stopped gerrit process.
+    01:34 mutante: switched gerrit-new to gerrit in DNS
+    01:30 ostriches: lead: stopped puppet for a few minutes
+    01:17 hashar: scandium: migrating zuul-merger repos to lead find /srv/ssd/zuul/git -path '*/.git/config' -print -execdir sed -i -e 's/ytterbium.wikimedia.org/lead.wikimedia.org/' config \;
+    01:10 hashar: stopping CI
+    01:09 jynus: reviewdb backup finished, available on db1020:/srv/tmp/2016-07-25_00-54-31/
+    01:02 ostriches: rsyncing latest git data from ytterbium to lead
+    00:57 mutante: manually deleted reviewer-counts cron from gerrit2 user, runs as root and puppet does not remove crons unless ensure=>absent
+    00:55 jynus: starting hot backup of db1020's reviewdb
+```",1469428542,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"2016-07-25
+
+    03:26 hashar: scandium: migrating zuul-merger repos from lead to gerrit.wikimedia.org: find /srv/ssd/zuul/git -path '*/.git/config' -print -execdir sed -i -e 's/lead.wikimedia.org/gerrit.wikimedia.org/' config \;
+
+    02:03 ostriches: gerrit: reindexing lucene now that we have new data. searches/dashboards may look a tad weird for a bit
+    01:53 hashar: starting Zuul
+    01:51 mutante: restarted grrrit-wm
+    01:39 ostriches: lead: turning puppet back on, here we go
+    01:38 jynus: m2 replication on db2011 stopped, master binlog pos: db1020-bin.000968:1013334195
+    01:37 hashar: scandium: restarted zuul-merger
+    01:36 ostriches: ytterbium: Stopped puppet, stopped gerrit process.
+    01:34 mutante: switched gerrit-new to gerrit in DNS
+    01:30 ostriches: lead: stopped puppet for a few minutes
+    01:17 hashar: scandium: migrating zuul-merger repos to lead find /srv/ssd/zuul/git -path '*/.git/config' -print -execdir sed -i -e 's/ytterbium.wikimedia.org/lead.wikimedia.org/' config \;
+    01:10 hashar: stopping CI
+    01:09 jynus: reviewdb backup finished, available on db1020:/srv/tmp/2016-07-25_00-54-31/
+    01:02 ostriches: rsyncing latest git data from ytterbium to lead
+    00:57 mutante: manually deleted reviewer-counts cron from gerrit2 user, runs as root and puppet does not remove crons unless ensure=>absent
+    00:55 jynus: starting hot backup of db1020's reviewdb",1469428480,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300660 abandoned by Dzahn:
+switch gerrit-new to gerrit
+
+Reason:
+duplicate of https://gerrit.wikimedia.org/r/#/c/299007/
+
+[[https://gerrit.wikimedia.org/r/300660]]",1469222038,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300660 had a related patch set uploaded (by Dzahn):
+switch gerrit-new to gerrit
+
+[[https://gerrit.wikimedia.org/r/300660]]
+",1469221691,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300657 merged by Dzahn:
+gerrit: lower TTLs to 600
+
+[[https://gerrit.wikimedia.org/r/300657]]",1469221452,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 300657 had a related patch set uploaded (by Dzahn):
+gerrit: lower TTLs to 600
+
+[[https://gerrit.wikimedia.org/r/300657]]
+",1469220934,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"> Yeah I know these hours weren't ideal for you, but I'm pretty sure from our testing that things will be ok. And ""broken CI"" is a condition for rolling things back.
+
+There is never a good time.  I should be to make a personal arrangement to show up without waking up the whole house!",1469118627,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2483146, @hashar wrote:
+> We would want to keep the ssh host fingerprint for the Gerrit embedded SSH daemon.  If it changes bunch of bots will stop until manually accepted.
+> 
+
+This has been done. I'll get it done in puppet too so we don't miss it next time.
+
+> 1am-4am UTC turns to 3am-7am CET, I can't reasonably work from home at those hours. not much opportunity until 6:30am UTC at best.
+> 
+> Then it is very low traffic at those hours, so I guess we can afford to have CI potentially broken somehow for a few hours.
+
+Yeah I know these hours weren't ideal for you, but I'm pretty sure from our testing that things will be ok. And ""broken CI"" is a condition for rolling things back.",1469109627,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"We would want to keep the ssh host fingerprint for the Gerrit embedded SSH daemon.  If it changes bunch of bots will stop until manually accepted.
+
+1am-4am UTC turns to 3am-7am CET, I can't reasonably work from home at those hours. not much opportunity until 6:30am UTC at best.
+
+Then it is very low traffic at those hours, so I guess we can afford to have CI potentially broken somehow for a few hours.",1469097294,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,@demon Sounds sane! :) Thanks for your work and the work of any other one involved so far :),1469083795,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Sounds good to me. I can be there Sunday night Pacific time. ,1469058840,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+# Decide/announce a window (ASAP, no time is good though)
+# Stop puppet on `lead`
+# Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+4) Run puppet one last time on `ytterbium`, stop puppet, stop Gerrit processes
+# Do a last snapshot of the Gerrit database, in case we have to roll back
+# Enable & run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing), Gerrit will restart) 
+# Run puppet for zuul nodes (restart zuul w/ new config)
+# Verify installation
+# Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+# Stop puppet on lead, turn off gerrit
+# Restore database to snapshat that we did prior to downtime
+# Revert puppet/DNS change from above ^^
+# Restart puppet and gerrit on `ytterbium` and `lead`
+# Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056818,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+# Decide/announce a window (ASAP, no time is good though)
+# Stop puppet on `lead`
+# Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+4) Run puppet one last time on `ytterbium`, stop puppet, stop Gerrit processes
+# Do a last snapshot of the Gerrit database, in case we have to roll back
+# Enable & run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing), Gerrit will restart) 
+# Run puppet for zuul nodes (restart zuul w/ new config)
+# Verify installation
+# Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056661,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+3) Run puppet one last time on `ytterbium`, stop puppet, stop Gerrit processes
+4) Do a last snapshot of the Gerrit database, in case we have to roll back
+6) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing), gerrit will restart
+7) Run puppet for zuul nodes (restart zuul w/ new config)
+9) Verify installation
+9) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056574,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+3) Run puppet one last time on `ytterbium`, stop puppet on, stop Gerrit processes
+4) Do a last snapshot of the Gerrit database, in case we have to roll back
+6) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing), gerrit will restart
+7) Run puppet for zuul nodes (restart zuul w/ new config)
+9) Verify installation
+9) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056558,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Run puppet for zuul nodes (restart zuul w/ new config)
+7) Verify installation
+8) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056243,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Run puppet for zuul nodes, restart
+7) Verify installation
+8) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469056222,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Adjusting my upgrade list from above, minor tweaks only:
+
+1) Decide/announce a window (ASAP, no time is good though)
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet / dns changes for lead and CI ([[https://gerrit.wikimedia.org/r/#/c/298673/|298673]], [[https://gerrit.wikimedia.org/r/#/c/299007/|299007]])
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Upgrade zuul, restart
+7) Verify installation
+8) Point DNS from ytterbium to `lead`
+
+The big points is we can leave puppet on `lead` the whole time and don't need downtime for reindexing. We did most of the prep work so Gerrit 2.12.2 is already running on that host. The index will be slightly out of date, but it can be rebuilt in-place. Searches will be a little wonky for the 45m or so, but it's better than staying down. We'll need a zuul upgrade, but this should be mostly prepared and in place prior to doing it. @hashar: How close are we to having the new zuul ready? It should be mostly done right?
+
+The whole process, ideally, should only take about 45 minutes tops, thanks to the extensive testing we did prior. Looking at the ganglia data, it looks like our lowest traffic times on weekdays are from about 01:00 to 10:00 UTC. Saturday and Sundays are mostly quiet other than the l10n bot updates at around 00:00UTC. So quietest time from my gathering is basically 01:00 to about 10:00 on Mondays, late Sunday night in the US. Basically let l10n bot do its thing and then start the window. The nice thing, in case things go totally wrong the European ops will be awake soon on a workday to help and take over.
+
+But it shouldn't go totally wrong. Roll back plan if things go wrong (and I plan to be very aggressive in rolling back if we don't have full functionality back) is as follows:
+* Stop puppet on lead, turn off gerrit
+* Restore database to snapshat that we did prior to downtime
+* Re-start puppet and gerrit on ytterbium
+* Reassess and plan a new window after issues fixed
+
+If this sounds good, I'd like to shoot for this coming Monday, July the 25th for our downtime (Sunday evening my time). I'm thinking 01:00-04:00UTC, that's 6-9pm locally.",1469054311,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"@MoritzMuehlenhoff Gerrit should show a little orange bubble near the ""Parent(s)"" section of the commit information, which indicates, that the parent isn't the latest one (which normally allows you to rebase). See this example:
+{F4271015}
+
+Merge conflicts (the current ""Can merge: No"" section), btw., is now a string with a red font in the change information box:
+{F4271027}",1468445225,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2456703, @demon wrote:
+>>>! In T70271#2456522, @AlexMonk-WMF wrote:
+>> I don't think the VE backport submodule update issue has been fixed :/
+>> I made https://gerrit-new.wikimedia.org/r/#/c/298010/ but it doesn't look like the submodule update showed up against mediawiki/core.git's wmf/1.28.0-wmf.1 branch
+> 
+> It probably will require a manual fix in the database where the old registration took place. Check with `gsql`?
+
+```gerrit> select * from submodule_subscriptions where submodule_path like '%VisualEditor%' and submodule_branch_name = 'refs/heads/wmf/1.28.0-wmf.1';
+ submodule_project_name | submodule_branch_name       | super_project_project_name | super_project_branch_name   | submodule_path
+ -----------------------+-----------------------------+----------------------------+-----------------------------+------------------------
+ VisualEditor           | refs/heads/wmf/1.28.0-wmf.1 | mediawiki/core             | refs/heads/wmf/1.28.0-wmf.1 | extensions/VisualEditor
+(1 row; 18 ms)```",1468423995,PHID-USER-mvx4x7ywk2flsaku2dbk,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"The old gerrit version only showed the ""Rebase"" button if the patch was in need of the rebase, while on gerrit-new the option is always displayed. If that's configurable it would be nice to revert to the old behaviour (since it makes it more obvious whether a patch needs to be rebased before merging)",1468418080,PHID-USER-abszjqutasfjxgagymds,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"@demon hi, I noticed that it dosent show the links to phabricator from the changes or from project pages.
+
+And it seems zuul is not testing in gerrit-new.
+
+And it the performance has really increased, loads instantly for me on a 80mbps connection from BT.",1468400541,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2456476, @AlexMonk-WMF wrote:
+> I've been messing around with gerrit-new. On the projects list, a lot appear to be duplicated under the 'git/' prefix?
+
+Looks like a mistake on-disk from my part from when we were doing replication of repositories via rsync. Deleted the git/* ones.",1468387574,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2456522, @AlexMonk-WMF wrote:
+> I don't think the VE backport submodule update issue has been fixed :/
+> I made https://gerrit-new.wikimedia.org/r/#/c/298010/ but it doesn't look like the submodule update showed up against mediawiki/core.git's wmf/1.28.0-wmf.1 branch
+
+It probably will require a manual fix in the database where the old registration took place. Check with `gsql`?",1468387417,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"I don't think the VE backport submodule update issue has been fixed :/
+I made https://gerrit-new.wikimedia.org/r/#/c/298010/ but it doesn't look like the submodule update showed up against mediawiki/core.git's wmf/1.28.0-wmf.1 branch",1468376670,PHID-USER-mvx4x7ywk2flsaku2dbk,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"I've been messing around with gerrit-new. On the projects list, a lot appear to be duplicated under the 'git/' prefix?",1468374689,PHID-USER-mvx4x7ywk2flsaku2dbk,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 298041 merged by Dzahn:
+gerrit: make Apache config compatible with 2.4
+
+[[https://gerrit.wikimedia.org/r/298041]]",1468274630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Change 298041 had a related patch set uploaded (by Dzahn):
+gerrit: make Apache config compatible with 2.4
+
+[[https://gerrit.wikimedia.org/r/298041]]
+",1468271973,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Paladox spoke to hashar after the comment above and the user does not have to be created (?),1468270190,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"The user jenkins-bot will need to be created in lead 
+
+https://github.com/wikimedia/operations-puppet/blob/30ffadcb6d8e6925affd55958981dce8c2c448d9/modules/role/manifests/zuul/configuration.pp#L8",1468267164,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"We need to update 
+
+https://github.com/wikimedia/operations-puppet/blob/30ffadcb6d8e6925affd55958981dce8c2c448d9/modules/role/manifests/zuul/configuration.pp#L8
+
+and 
+
+https://github.com/wikimedia/operations-puppet/blob/30ffadcb6d8e6925affd55958981dce8c2c448d9/modules/contint/manifests/firewall.pp#L60",1468262620,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,We need to update https://github.com/wikimedia/operations-puppet/blob/30ffadcb6d8e6925affd55958981dce8c2c448d9/modules/role/manifests/zuul/configuration.pp#L8,1468262418,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Also the zuul seems to work perfectly with gerrit 2.12 (no lost in connection or ssh connection) It seems to me that may have been a bug in gerrit 2.8.,1468253923,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"@hashar Ive been testing zuul, jenkins and gerrit 2.12 and it works. See 
+
+* https://gerrit-zuul.wmflabs.org/
+
+* https://gerrit-jenkins.wmflabs.org/
+
+* https://gerrit-test.wmflabs.org/
+",1468253816,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Ive been testing zuul, jenkins and gerrit 2.12 and it works. See 
+
+* https://gerrit-zuul.wmflabs.org/
+
+* https://gerrit-jenkins.wmflabs.org/
+
+* https://gerrit-test.wmflabs.org/
+",1468253807,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"The upgrade of Gerrit definitely has an impact on Zuul.
+
+The version we run is based on upstream 66c8e52 which is:
+* from early December 2015 (7 months ago)
+* when they were still running Gerrit 2.8.4
+* before a massive refactoring of how Zuul connects to Gerrit
+
+I tried to upgrade Zuul further but a mysteriously issue happened related to the Zuul / Gerrit ssh connection: T137525 . I haven't managed to reproduce it locally or on labs though :-(
+
+OpenStack has (since December) switched to Gerrit 2.11.x + patches and I haven't looked at Zuul code whether there are changes that are needed. They will most probably be based on massive refactoring that we still do not have in our version.
+
+
+The, maybe the Zuul version will just work with Gerrit 2.12.  If `stream-events` hasn't changed and the `review` command is still compatible, we might be just fine.
+
+
+----------
+
+As part of the migration we also have to:
+* update various Zuul related bits that points to ytterbium
+* most probably manually change the remote URL of zuul-merger repos on scandium in /srv/ssd/zuul/git
+
+
+----
+
+Also I think the old change screen is gone and that is going to cause major havoc  and complains for sure. So wanna communicate about that user facing change ahead of time.
+
+
+",1468250598,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Re timing:
+I guess email Ops list with the plan, ask for a volunteer for Sunday (offer $drinks), if someone replies before tomorrow (Saturday) when Chad wake up then he should send out the announcement that we'll do the Sunday maintenance window.",1468017013,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Tested the upgrade path today using copies of production data (Sql and Git) and the 2.12.2 package we built for Jessie. It went well. Couple of more tests this afternoon and then it looks like we can run the upgrade ASAP. Workflow will be:
+
+1) Decide/announce a window
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet manifest to new server `lead`
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Stop puppet on `lead` until (7) is done to keep Gerrit from being brought up just yet
+7) Run the reindexing process on new `lead`, will take about 45-60m from testing.
+8) Re-enable puppet so systemd can take over running gerrit
+9) Verify installation
+10) Point DNS from ytterbium to `lead`
+
+The whole process, ideally, should only take about an hour to an hour and a half based on my testing. I want to give myself 3 hours in case. This is highly disruptive so needs to be announced widely, but soon (as in days, not weeks). I'm almost thinking this weekend since less disruption than on a workday...
+
+I will need a root user on hand to take the snapshot and merge puppet changes (which can all be staged beforehand). @Dzahn has been super helpful so far, but I know @jcrespo is the DBA.",1468368567,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Tested the upgrade path today using copies of production data (Sql and Git) and the 2.12.2 package we built for Jessie. It went well. Couple of more tests this afternoon and then it looks like we can run the upgrade ASAP. Workflow will be:
+
+1) Decide/announce a window
+2) Stop puppet on `ytterbium`, stop Gerrit processes
+3) Do a last snapshot of the Gerrit database, in case we have to roll back
+4) Apply puppet manifest to new server `lead`
+5) Run puppet on `lead`, which will issue the schema upgrades to m2-master (will take about 4-5 minutes from testing)
+6) Stop puppet on `lead` until (7) is done to keep Gerrit from being brought up just yet
+7) Run the reindexing process on new `lead`, will take about 30-45m from testing.
+8) Re-enable puppet so systemd can take over running gerrit
+9) Verify installation
+10) Point DNS from ytterbium to `lead`
+
+The whole process, ideally, should only take about an hour to an hour and a half based on my testing. I want to give myself 3 hours in case. This is highly disruptive so needs to be announced widely, but soon (as in days, not weeks). I'm almost thinking this weekend since less disruption than on a workday...
+
+I will need a root user on hand to take the snapshot and merge puppet changes (which can all be staged beforehand). @Dzahn has been super helpful so far, but I know @jcrespo is the DBA.",1468014014,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Another feature/bug in 2.11 (and with it in 2.12, too) would be a fix for:
+https://bugs.chromium.org/p/gerrit/issues/detail?id=1207
+
+Yes... on a german keyboard you can't use the shortkeys for next/previous file in the diff view, which isn't really great  :(",1465317098,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"@demon Hi, any news here? :) Is it possible to have a look at a test instance running the newer Gerrit version?",1462873310,PHID-USER-m2zne2efu3rgmre73nl7,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"I don't think, that such a hidden feature, especially because it isn't mentioned in the changelog and only available by adding a query to the url, is something which could be named as a ""near"" feature we've after upgrading :)",1459536003,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"There's polygerrit, gerrit said next version but built into gerrit to test at moment. Once updated to gerrit 2.12 add this to your url ?polygerrit=1 the new design is really nice.",1459474099,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,I guess ops may like https://code.google.com/p/gerrit/issues/detail?id=3293,1457627783,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#2107030, @siebrand wrote:
+> Is there any way to find out if this will or won't be scheduled?
+
+When I have a firm date/time for switching to the new machine & version I'll let everyone know. Right now I'm getting the box prepped and testing the new version.",1457624570,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,I believe that they have a setup a new server and that will use gerrit 2.12  they will be switching soon I think. I may be wrong.,1457622881,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Is there any way to find out if this will or won't be scheduled?,1457622008,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Gerrit 2.12 includes support for signed pushes now which some users on Wikipedia use.
+
+Release notes at https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.12.html",1451238766,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Maybe create a test site with gerrit and test weather upgrading gerrit will cause zuul and jenkins too break.,1449169909,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"OpenStack is upgrading to 2.11 on Dec 16th (from 2.8.4+).  They already wanted to upgrade a couple weeks ago but cancelled it, maybe because it was not working properly.
+
+No idea whether 2.12 will work.
+
+Upgrade of Gerrit usually have side effect with Zuul.",1449169117,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Yes and plus makes it really easy to edit in browser. Some users like using the gerrit tool provided by Wikimedia to upload there patches with this update they can do it from gerrit supper easy.,1449165846,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Although Phabricator is the glorious future, we should upgrade Gerrit at least for stability + security improvements if nothing else. 2.12 is basically ready to go, testing it now.",1449163362,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Gerrit 2.11.1 has been released doesent show it on its front page but in the release notes it does. Please visit https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.1.html which I think fixed the problem that blocked us from upgrading.,1434123615,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,And delete project can be downloaded at https://ci.gerritforge.com/view/Plugins-stable-2.11/job/Plugin_delete-project_stable-2.11/ and already compiled to works with gerrit 2.11.,1433349752,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,And includes more features and no longer uses google to generate charts.,1433349700,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,If you doint want to compile gitblit use this https://ci.gerritforge.com/job/Plugin_gitblit_stable-2.11/ which is already complied and works for me. ,1433349554,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Me too.,1433271785,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"It's been a while since I looked at upstream…
+
+* Keyboards shortcuts in diff view all work correctly again, so do long lines; unified diff is back, as well as prefs. There's an inline button to leave a comment when you select text; no one is going to miss double-clicking (you can effectively triple-click now). There is literally no reason not to prefer the new diff view now. https://gerrit-review.googlesource.com/#/c/68292/1/gerrit-server/src/main/java/com/google/gerrit/server/config/GerritGlobalModule.java
+* Automated comments (bots, new patchsets) in change view are collapsed by default.
+* ""Size"" column in changes lists! *drools* https://gerrit-review.googlesource.com/#/q/status:open
+* ""Conflicts with"" pane! ""Merge conflict"" status in changes lists!
+
+so much awesome
+
+seriously
+
+can we update already plz?",1433271106,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,And improvements to list of projects because it doesent show all of projects In one list it now puts them on different pages. ,1433270051,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Yes get them to look at that is better.,1433269947,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Or they can just [[ https://gerrit-review.googlesource.com/#/c/68304/ | look at upstream ]].,1433269286,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,I doint mean the current new screen in gerrit on Wikimedia. Wikimedia could set up a test gerrit server with the new screen and get feedback since they wont upgrade unless the majority like it. And when they moved bug software from bugzilla to phabricator that was a big user ajust ment. so the same can be applied here.,1433267433,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Note that the new screen in 2.11 is said to have received much improvement, so asking users based on the current new screen makes no sense.",1433266117,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Yep. Since that would be a breaking change I suggest to create a feedback online and ask users to say would they like the new change screen or not. And say the improvements it would have if we upgrade.,1433263209,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"That release seems to include the patch QChrist identified as missing and according to my reading of the source it will ship with jgit 4.0.0.201505050340-m2. If that works for openstack...
+
+Then the only thing remaining we identified is living with the old ChangeScreen being gone.",1433252884,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Hi 2.11.1 release notes at https://gerrit.googlesource.com/gerrit/+/refs/heads/stable-2.11/ReleaseNotes/ReleaseNotes-2.11.1.txt looks like they may have fixed performance bug.,1433244298,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1296359, @Paladox wrote:
+> we could upgrade to latest 2.8.x release
+
+...which isn't handled in this task (now i feel like a parrot o.O) - See {T65847}.",1432048476,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Hi yes we could upgrade to latest 2.8.x release which would includes fixes.,1432048325,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1285022, @Paladox wrote:
+> Hi what about upgrading to 2.8.6.1
+
+Not handled in this task. - See T65847.",1432029435,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,And then once 2.11 is fixed. then disccuss about upgrading since it removes the old screen which everyone is used too.,1431619328,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,2.10 should be the version we upgrade to since it still has the old change screen but not default you would have to set it default and you can now customise the my page,1431619274,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,or 2.9 or 2.10. Note 2.9 onwards the bugzilla plugin uses the new its-bugzilla instead of old plugin and plugins list are now shown.,1431618933,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Hi what about upgrading to 2.8.6.1 since it is a minor upgrade from 2.8.1 to 2.8.6.1 and in preparation for if people are in favour of upgrading to 2.11 when the bug is fixed.,1431618480,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,That definitively sounds like a blocker (i assume we have a comparable traffic in our gerrit-instance).,1431508397,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1281258, @QChris wrote:
+> I guess @hashar was instead refering to the post about gerrit complaining about corrupt pack files. See also https://groups.google.com/forum/#!topic/repo-discuss/CYYoHfDxCfA
+
+Yup that is the one I wanted to refer to sorry. OpenStack definitely want to upgrade so I am sure they will push to get it fixed (or fix it themselves).
+",1431507203,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1280109, @Paladox wrote:
+> I believe they fixed problem but haven't released a new version of gerrit for 2.11 with the fix they only released it with 2.10. Please see https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.10.4.html
+
+The fix you mentioned is for [[https://code.google.com/p/gerrit/issues/detail?id=3300|Gerrit Issue 3300]]. That was the bug for the performance degradation in 2.10.
+
+I guess @hashar was instead refering to the post about gerrit complaining about corrupt pack files. See also https://groups.google.com/forum/#!topic/repo-discuss/CYYoHfDxCfA",1431473496,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,I believe they fixed problem but haven't released a new version of gerrit for 2.11 with the fix they only released it with 2.10. Please see https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.10.4.html,1431447902,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"For what is worth, OpenStack has upgraded from Gerrit 2.8 to 2.11 and had to revert due to JGit issue.
+
+Revert announce with some details is: http://lists.openstack.org/pipermail/openstack-infra/2015-May/002750.html
+
+Jeremy Stanley (fungi) and James E. Blair (jeblair) can be reached on IRC in #openstack-infra (or one can mail them).",1431447230,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,This extension its-phabricator has been fixed and is now compatible with 2.11 whereas I am not sure about its-phabricator-from-bugzilla since I carnt find source code.,1431355030,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1271255, @QChris wrote:
+> Not sure about `github-create` ... is the code for that anywhere in the open?
+
+No, that's my secret sauce. I have to make sure I still have the code even.",1431098694,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1271255, @QChris wrote:
+> * 'Generate HTTP Password' is gone. I know that at least a few people used this at WMF.
+
+https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.html#remove-generate-http-password-capability reads:
+> Remove the Generate HTTP Password capability.
+>
+> The Generate HTTP Password capability has been removed to close a security vulnerability. Now only administrators are allowed to generate and delete other users' http passwords via the REST or SSH interface.
+>
+> It is encouraged to clean up your project.config settings after upgrading.
+
+This reads as if the ability for users except admins to do that for other users is gone, but users are still able to do that for themselves. ( https://android-review.googlesource.com/ is on 2.11 but integrated with Google Account so that one can still use the feature there possibly doesn't mean anything for our setup. )",1431090189,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1269328, @demon wrote:
+> `its-phabricator-*` ones are mission-critical and must be upgraded and functioning. `github-create` primarily affects me and @qchris but would be nice to still have working. `deleteproject` we don't maintain but will have to rebuild. The remaining 4 are all bundled and should Just Work.
+
+I can handle the `its-*` ones. Sure.
+
+`delete-project` we can grab for example from http://builds.quelltextlich.at/gerrit/nightly/stable-2.11/2015-05-07/index.html#delete-project.jar to spare us manual building. (It currently builds, and can be loaded, but I have not tested whether or not it's working).
+
+Not sure about `github-create` ... is the code for that anywhere in the open?
+
+(I am sure people will also ask for Luca's github plugin to get nice and easy Pull-Reuest handling. There have been some authentication issues in that plugin lately ... not sure if that is currently in a working state or not).
+
+But I think there are other deal-breakers (this list need not be exhaustive):
+* In 2.11, our current default ChangeScreen is gone. Forcing people to use the new ChangeScreen and only to tell them to again cange to Differential in a few months(?). I'd consider that a no-go.
+* In 2.11, the same Mina SSHD is used that is somewhat suspected by users to cause issues for 2.10.3.1. Debugging Mina SSHD is no fun. I had to do that twice. I don't want to do it again, just because we cannot downgrade and (maybe) 2.11's Mina SSHD causes issues.
+*  The released 2.11 war lacks https://gerrit-review.googlesource.com/#/c/67490/1 which fixes mouse grab issues, and I'd consider it important.
+* One person reported running out of heap after upgrading to 2.11. The reporter got it under controll by running garbage collection on their repos. But since downgrading again is somewhat not an option and some of our repos are big, one need to double-check and make sure that this does not bite us ... or if it bites wmf's gerrit, one needs to at least check that gc can reliably mitigate it for wmf.
+* 'Generate HTTP Password' is gone. I know that at least a few people used this at WMF.
+
+All in all ... I am not sure if now is the right time to upgrade to a 2.11 version. A few weeks down the road (and maybe after a new release in the 2.11 series), the middle three items go away. But the dropping of the our current default ChangeScreen will stay. People would get forced to use the New ChangeScreen.",1431048060,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Hi here is link for updates for its-phabrictor https://gerrit.googlesource.com/plugins/its-phabricator/+/master,1431040464,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T70271#1269328, @demon wrote:
+> We currently have the following plugins:
+
+I added them (the ones need an update/test) to the task description :)",1431015224,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"We currently have the following plugins:
+```
+commit-message-length-validator	v2.8.1	Enabled
+deleteproject	2.8.1	Enabled
+download-commands	v2.8.1	Enabled
+github-create-1.0-rc0	1.0-rc0	Enabled
+its-phabricator	2.8.1	Enabled
+its-phabricator-from-bugzilla	2.8.1	Enabled
+replication	v2.8.1	Enabled
+reviewnotes	v2.8.1	Enabled
+```
+`its-phabricator-*` ones are mission-critical and must be upgraded and functioning. `github-create` primarily affects me and @qchris but would be nice to still have working. `deleteproject` we don't maintain but will have to rebuild. The remaining 4 are all bundled and should Just Work.",1431014698,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"[08:59:05] <^d> Somebody convince qchris to redo the plugins and I'll do it :p
+
+@qchris, are you up for that? :)",1431014428,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,+1. I still have hope that there is someone who can do this and who doesn't hate Gerrit so much as to not touch it with a stick.,1431005789,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,">>! In T65847#1268664, @Nemo_bis wrote:
+> The request for 2.11 should be moved to T70271. This report is for requesting a minor version upgrade within 2.8.x.
+
+Then this task should be reopened.",1431005769,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Moving some offtopic discussion from the other report:
+
+>>! In T65847#1268528, @Florian wrote:
+> Gerrit [[ https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.html | release 2.11 ]] adds another really really useful feature, [[ https://gerrit-documentation.storage.googleapis.com/Documentation/2.11/user-inline-edit.html | inline editing ]], which allows you to create changes within the browser without cloning the repo or checkout the change itself. I know, that we're planing to migrate gerrit to phabricators Differential, but it would be a very nice and (like i said) useful feature in gerrit, which (as far as i know) doesn't exist in Differential at the moment (see {T409}, and it seems, see the discussion on the upstream task, that this feature will not arrive in Differential in the next time). In my point of view it would be a step backwards if Gerrit now (after a long long time of user wishes, i think) get's a web based editor and we move to Differential, which doesn't support this feature and doesn't has the plan to implement it.
+> 
+> Another point is, that i don't see a real roadmap for the migration (i read some tasks and haven't found one to implement a testing environment to show the code-review process, which wasn't resolved so far and was planned for last xyear september iirc, but i doesn't find it again :/). So, should we re-consider to upgrade gerrit? That would make it possible to resolve {T71445}.
+> 
+> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default, see for information https://gerrit-review.googlesource.com/Documentation/user-review-ui.html.
+
+
+
+>>! In T65847#1268589, @matmarex wrote:
+>> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default
+> 
+> Good, it's already way better than the old one in the ancient beta version we're running, and I heard that the issues it has got ironed out. I'd also love if the upgrade (any upgrade) happened.
+
+
+
+>>! In T65847#1268589, @matmarex wrote:
+>> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default
+> 
+> Good, it's already way better than the old one in the ancient beta version we're running, and I heard that the issues it has got ironed out. I'd also love if the upgrade (any upgrade) happened.
+
+
+
+>>! In T65847#1268606, @Florian wrote:
+>>>! In T65847#1268584, @JanZerebecki wrote:
+>> I'd like the upgrade to 2.11 to be reconsidered. But it is also a question of finding someone who does the work. So lets first find someone to do the work of upgrading to 2.8.6.1.
+> 
+> Not really needed, we're already using gerrit release 2.8.x (2.8.1), which would allow us to directly upgrade to 2.11, see https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.11.html
+> 
+> (let's adjust the title of this task to ""Upgrade gerrit"", because it seems, that we are currently not really sure, _if_ we can/should/want upgrade gerrit at all :))
+> 
+> 
+> 
+>>>! In T65847#1268589, @matmarex wrote:
+>>> But there is a (maybe) bad thing with Gerrit 2.11: The old (actual default) change screen was removed iirc, so the new change screen is the default
+>> 
+>> Good, it's already way better than the old one in the ancient beta version we're running, and I heard that the issues it has got ironed out. I'd also love if the upgrade (any upgrade) happened.
+> 
+> +1, i tested it locally and it's a big improvement, still a ""new"" thing, but you find all needed things very fast :)
+
+",1431005224,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"(In reply to christian from comment #6)
+> Since people asked for more reasons, why to not upgrade:
+
+Thanks, that's useful. None of these points applies to 2.8.x upgrades (bug 63847), correct?",1415268588,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Since people asked for more reasons, why to not upgrade:
+
+* Search backend gets switched. And the first test I made with it some time back
+  were not super solid. That might have changed in the meantime, and the old
+  (=current) search system has it's warts too, but we know them, and can live
+  with them. No hidden dangers there.
+
+* At first glance, it seems there are database schema changes. Those typically
+  make it hard to downgrade if something goes wrong. So the upgrade would need
+  good preparation. We cannot “just try it out”.
+
+* We'd need new plugins, since part of the functionality that was in core before
+  got put into separate plugins.
+
+* We'd need to rebuild our bugzilla integration.",1405891941,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"So if it's just some new random features with questionable gain in our usecase, I will close this as WILL NOT FIX.",1405797393,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,It also has a new plugin for bugzilla.,1405791360,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,Well the new design that is an option in the current version of gerrit on wikimedia is a part of the new design but they also redesigned it complete in 2.9. It also includes a new side by side diff and also Fix truncated long lines in new side-by-side diff screen.,1405791299,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"Gerrit 2.9 includes the new change screen which is worse. That's a reason not to upgrade.
+
+Plus we're planning a Phabricator migration soon-ish. What's to gain?",1405788661,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+Upgrade gerrit to 2.12,"I don't consider ""please upgrade some software to some latest version"" very useful if there are not 1) very good reasons to do this 2) urgently.
+Your list above does not provide any good reasons.",1405782365,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kf2l66kfrhge5pukl6ms,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","We get ""Unknown error"" (not internationalised) when saving on officewiki.
+
+This is because the response object given to ve.init.mw.Target.onSave is actually a jqXhr(?) object here for some reason, which has an error function. The data we actually want is in the responseJSON property of this, and we can also get it via .done( ... ).
+
+This stuff comes through tryWithPreparedCacheKey and the way it fits together with everything else wasn't very clear here (lots of chaining deferreds etc.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405716000,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_description,resolved
+"VisualEditor: ""Unknown error"" on saving on officewiki","I fixed it up in the remaining places:
+```commonswiki         MediaWiki:LAPI.js
+dewikiversity       MediaWiki:LAPI.js
+enwiki              MediaWiki:LAPI.js
+fawiki              MediaWiki:LAPI.js
+huwiki              MediaWiki:LAPI.js
+huwikiquote         MediaWiki:LAPI.js
+kawiki              MediaWiki:LAPI.js
+mlwiki              MediaWiki:LAPI.js
+nnwiki              MediaWiki:LAPI.js
+rowiki              MediaWiki:LAPI.js
+ruwikibooks         MediaWiki:LAPI.js
+srwikibooks         MediaWiki:Common.js/Core.js
+svwiki              MediaWiki:LAPI.js
+zhwiki              MediaWiki:LAPI.js```",1425670493,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki",">>! In T70235#719892, @Krenair wrote:
+> So that last srwikibooks entry appears to be in an unused file... Roan, can you release and upstream the LAPI.js changes to the other wikis? I don't think I can do it (I'd have to do it as staff, but my global editinterface is personal, so...).
+
+Sorry for the extreme delay: https://eo.wikipedia.org/w/index.php?title=MediaWiki:LAPI.js&diff=prev&oldid=5628789",1425668478,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","So that last srwikibooks entry appears to be in an unused file... Roan, can you release and upstream the LAPI.js changes to the other wikis? I don't think I can do it (I'd have to do it as staff, but my global editinterface is personal, so...).",1407160072,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki",https://dpaste.de/JS7k/raw courtesy of legoktm is an mwgrep of all of the redefinitions of bind on the cluster. Yay.,1407059571,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","This was caused by local JS overwriting Function.prototype.bind with a broken polyfill that ignores additional parameters rather than passing them to the bound function.
+
+We were using something like onSave.bind( this, doc, saveData ) which should have resulted in a call like onSave( doc, saveData, responseData, statusText, jqXHR ) but the broken polyfill dropped doc and saveData, causing the remaining arguments to be shifted two places to the left. Then when we check if responseData.error is defined, we're really looking at jqXHR.error, which is in fact a method on the jqXHR object, so it's always defined and we always believe there is an error, even if there isn't one. But of course we can't find an error code or error text because we're looking in the wrong place, so we say ""Unknown error"". In fact, we would say that even if there was an error, because the error data got shifted over into the doc parameter, which we don't look at.
+
+https://office.wikimedia.org/w/index.php?title=MediaWiki:LAPI.js&diff=115901&oldid=24064 fixes the unconditional overwrite so Function.prototype.bind isn't overwritten if it's already present. This check was already being done for everything else that the script polyfills.
+
+https://office.wikimedia.org/w/index.php?title=MediaWiki%3ALAPI.js&diff=115904&oldid=115902 fixes the polyfill to correctly pass additional parameters along.",1407034283,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki",Mis-fire.,1406147366,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","Change 148757 had a related patch set uploaded by Catrope:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148757",1406146930,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","officewiki is important, actually",1406139217,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: ""Unknown error"" on saving on officewiki","Does not affect other private wikis (checked otrswiki, collabwiki), not major/high priority.",1405717579,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jt6qre2zwuzp7bltugkt,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Screenshot
+
+1.Open a page with VE in FF
+2.Click on Link inspector icon 
+3.The inspector does not open up
+4.Now again click on the link tool on the toolbar
+
+Observed Result:
+The link inspector opens up with distorted UI and the following error appears in the console
+
+TypeError: manager.opening is null
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14196}",1405707060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_description,resolved
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI",Verified the fix in production,1407189770,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI",Verified the fix in Betalabs and the backport on test2,1406161145,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Change 148770 merged by jenkins-bot:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148770",1406153427,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Change 148770 had a related patch set uploaded by Jforrester:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148770",1406148486,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Change 148757 merged by jenkins-bot:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148757",1406148399,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","Change 148757 had a related patch set uploaded by Catrope:
+Followup b141a7d23: don't display:none; the popup in the DesktopContext
+
+https://gerrit.wikimedia.org/r/148757",1406147238,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error ""TypeError: manager.opening is null"" and appears with broken UI","This is also happening for Language inspector,math inspector,special character.
+Its not that they are not opening on the first attempt, it takes too long to open it , so when I tried to open them second time , it throws that error and appears in broken way.",1405708610,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xg7pbllkf35fo5qpa5uo,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned","Screenshot
+
+Open language inspector in betalabs and observe the brokenness
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14642}",1405620240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6qda63lpaymzom6tbttz,task_description,resolved
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned",Verified the fix in production en.wiki,1406318938,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned",Verified the fix in test2,1405719538,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned",Verified the fix in test2,1405719533,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned",Fixed in gerrit 147179; will pull through and back-port.,1405624867,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned","Also , Special Character inspector has its UI distorted.Are they related?",1405620557,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6qda63lpaymzom6tbttz,task_subcomment,NA
+VisualEditor: PopupToolGroup item not 'ticked' after changing,"1. Place the cursor in a paragraph and change it to a heading the the popup tool
+2. Open the popup tool again and observe that nothing is selected (with a tick)
+3. Change the context (click in another paragraph/heading, then back)
+4. Open the popup tool, the correct item is now selected
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405615500,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yjzj5bv5ffrnllxzssak,task_description,resolved
+VisualEditor: PopupToolGroup item not 'ticked' after changing,Fixed in gerrit 4b874d42206e988844367eccacb9503fe6c3ddb5.,1406060277,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yjzj5bv5ffrnllxzssak,task_subcomment,NA
+VisualEditor: PopupToolGroup item not 'ticked' after changing,"This may well be a oojsui bug, tbd.",1405615571,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yjzj5bv5ffrnllxzssak,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"When I have created an article in the hebrew version of wikipedia, ☃ symbol replicated.
+
+The operations I did:
+1. I copied an tamplate from another article.
+2. I edited it's fields by the visual editor.
+3. I started to write text in bold.
+4. I changed the text state to normal.
+5. The symbol ☃ started to replicate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68151",1405587840,PHID-USER-em3l7mquu7qcck24eqq5,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_description,resolved
+VisualEditor: ☃ symbol replicates when creating an article with a template,Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660949,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659002,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658987,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658731,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656758,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646181,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646098,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645954,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645924,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645480,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645472,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630070,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,*** Bug 68148 has been marked as a duplicate of this bug. ***,1406601182,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+VisualEditor: ☃ symbol replicates when creating an article with a template,"Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594983,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ygqki32oghxhcc37oyhf,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make an edit 
+3.Click on the ""Save Page""
+4.While the saving is in progress,keep on clicking on the ""Save Page"" button on the Save dialog
+
+Observed Result:
+The following error appears in the console:
+
+Uncaught TypeError: Cannot read property '$saveOptions' of null
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14424}",1405459560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_description,resolved
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""",Verified the fix in production,1407187444,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""",Verified the fix in test2,1406327297,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""",Verified the fix in Betalabs,1406159736,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""",Going to mark as FIXED but please re-open if there's an issue.,1406083201,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Does this still happen? I was able to replicate it on deployment-prep at the time (not on my local machine, as I said), but now I can't...
+
+I get ""Uncaught TypeError: Cannot read property 'getModel' of null"" when trying to load VE after it's been saved (again, only on deployment-prep, not my local machine), but that seems unrelated.",1405632802,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","I can reproduce both the UI as well as the logic problem.
+
+Both the ""Review your changes"" and the ""Save page"" buttons in the save dialog remain clickable.
+
+Their apparent state looks clickable, their response to clicking is appeared pressed, and the result is the event handler firing internally.
+
+The exception usually doesn't happen until after the first save attempt has finished and the view goes back to ""read"" mode, but it does throw:
+
+ve.init.mw.ViewPageTarget.prototype.onSave = function ( ..  ) {
+	if ( !this.pageExists || this.restoring ) {
+		..
+	} else {
+		if ( mw.page.watch && mw.page.watch.updateWatchLink ) {
+			watchChecked = this.saveDialog.$saveOptions
+.. ^",1405561718,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","I don't think that fixed it, unfortunately. But I can't reproduce this error locally.",1405545623,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Change 146810 merged by jenkins-bot:
+Don't allow document save if we're already tearing down the surface
+
+https://gerrit.wikimedia.org/r/146810",1405543526,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Change 146810 had a related patch set uploaded by Alex Monk:
+Don't allow document save if we're already tearing down the surface
+
+https://gerrit.wikimedia.org/r/146810",1405529649,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws ""Uncaught TypeError: Cannot read property '$saveOptions' of null""","Seems that I can only get ""Uncaught TypeError: Cannot read property 'messages' of null "" on my local machine",1405527697,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-yx3vtjrhpk7db6rdy7sr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,"Steps to reproduce:
+
+1.Open a page with VE
+2.Make an edit to the page
+3.Click on the ""Cancel"" button next to ""Save Page""
+
+Observed Result:
+Nothing happens, the confirmation dialog box does not appear neither it lets user close VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405457520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xbka5x6ezizjtfccyclk,task_description,resolved
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,Verified the fix in production en.wiki,1406318542,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,Verified the fix in test2,1405720234,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,Verified the fix in Betalabs,1405556318,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,"Change 146639 merged by jenkins-bot:
+Make a message dialog for cancelling VE
+
+https://gerrit.wikimedia.org/r/146639",1405543530,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs,"Change 146639 had a related patch set uploaded by Alex Monk:
+Make a message dialog for cancelling VE
+
+https://gerrit.wikimedia.org/r/146639",1405465411,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xbka5x6ezizjtfccyclk,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,"Screenshot
+
+Steps to reproduce:
+
+1.Select a math node/ a reference/image /open any inspector
+2.Scroll down the page
+
+Observed Result:
+The highlights, context menus and inspectors everything is appearing over the toolbar
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14413}",1405455840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-izo3tiafzfdz4gvztvz5,task_description,resolved
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,Verified the fix in production en.wiki,1406318442,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,Verified the fix in production en.wiki,1406318428,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,Verified the fix in test2,1405721309,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,"Change 146981 merged by jenkins-bot:
+Update VE core submodule to master (8bb3848)
+
+https://gerrit.wikimedia.org/r/146981",1405554705,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome,"Change 146981 had a related patch set uploaded by Jforrester:
+Update VE core submodule to master (8bb3848)
+
+https://gerrit.wikimedia.org/r/146981",1405553286,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-izo3tiafzfdz4gvztvz5,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,"Screenshot
+
+The Link inspector in mobile became completely broken and unusable after new windows refactor change
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14399}",1405453020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j2fbmrbwc2pv3om246qs,task_description,resolved
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,Verified the fix in production en.wiki,1406317240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j2fbmrbwc2pv3om246qs,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,Verified the fix in test2,1405723887,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j2fbmrbwc2pv3om246qs,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,"Change 146296 merged by jenkins-bot:
+Get OOUI working with mobile again
+
+https://gerrit.wikimedia.org/r/146296",1405548473,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j2fbmrbwc2pv3om246qs,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken,"Change 146296 had a related patch set uploaded by Jforrester:
+[WIP] Get OOUI working with mobile again
+
+https://gerrit.wikimedia.org/r/146296",1405456924,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j2fbmrbwc2pv3om246qs,task_subcomment,NA
+VisualEditor Mobile: Context menu for Math is still appearing in Mobile VE,"Tapping on a math node is still bringing up the context menu on top of the page,letting user to open math inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405378440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dexoxhnm6p7r5tl42o5j,task_description,declined
+"OOjs UI: When the text in buttons in confirmation dialogs is too long, some of the buttons may overflow, breaking the dialog","Example with cyrillic text where one button overflows.
+
+When the dialog to switch from VisualEditor to wikicode edition is shown, its dimensions are sufficient to show all the buttons when the interface text is in English. However, in fr, crh-Cyrl and possibly in other languages, the text on the buttons is longer, and the buttons can fall and flow over the edge of the dialog (overflow). This makes it impossible to read the text on them.
+
+This issue is best described by the screenshot attached to this message, and by the subsequent screenshots.
+
+To reproduce:
+
+- Browse to this URL: https://en.wikipedia.org/w/index.php?title=User:Rastus_Vernon/VisualEditor_Sandbox&veaction=edit&uselang=fr.
+- Open the VisualEditor menu.
+- Click “Passer à l'édition de code”.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14277}",1405374540,PHID-USER-2rwkb3az6uklfhh5aqw5,False,PHID-TASK-htrpa3kqlb6jcmk4geh7,task_description,resolved
+"OOjs UI: When the text in buttons in confirmation dialogs is too long, some of the buttons may overflow, breaking the dialog",Happily we just fixed this in gerrit 139550 which means the buttons on ConfirmationDialogs will automatically re-order and re-size based on the length of the label.,1405375780,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-htrpa3kqlb6jcmk4geh7,task_subcomment,NA
+"OOjs UI: When the text in buttons in confirmation dialogs is too long, some of the buttons may overflow, breaking the dialog","Created attachment 15937
+Example of the expected behavior, in English, for comparison.
+
+**Attached**: {F14281}",1405374648,PHID-USER-2rwkb3az6uklfhh5aqw5,False,PHID-TASK-htrpa3kqlb6jcmk4geh7,task_subcomment,NA
+"OOjs UI: When the text in buttons in confirmation dialogs is too long, some of the buttons may overflow, breaking the dialog","Created attachment 15936
+Example with French text where two buttons overflow.
+
+**Attached**: {F14278}",1405374619,PHID-USER-2rwkb3az6uklfhh5aqw5,False,PHID-TASK-htrpa3kqlb6jcmk4geh7,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Based on feedback and test by French Wikipedians, which we always thank.
+
+An editor reported getting a snowman here https://fr.wikipedia.org/w/index.php?title=Lucien_Dayle&diff=next&oldid=105411841 when all he did was removing a comma (Chrome, Mac OS X).
+I wasn't able to reproduce https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve2&diff=105432197&oldid=105432184 .
+
+Then another user created a sandbox with similar templates in it and I tested there as well; https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AZebulon84%2FBrouillon&diff=105432505&oldid=105431985 the snowman showed up in the exact place where I had added a comma.
+
+In another case instead https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AZebulon84%2FBrouillon&diff=105432576&oldid=105432561 the letter ""e"" shows up where I had put the comma. The user had previously replaced the template {{e}} with <sup> tags (https://fr.wikipedia.org/w/index.php?title=Utilisateur:Zebulon84/Brouillon&diff=prev&oldid=105422272 ).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405353120,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_description,resolved
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,Should be now fully fixed in master; deployment to production scheduled for 4 hours' time.,1406660943,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406659005,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150274 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406658984,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 restored by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406658734,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150274 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150274",1406656765,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+Reason:
+I give up.
+
+https://gerrit.wikimedia.org/r/150224",1406646173,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 restored by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406646092,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645959,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150224 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150224",1406645934,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150222 abandoned by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645493,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 150222 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/150222",1406645477,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 149920 merged by jenkins-bot:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406630076,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,*** Bug 68124 has been marked as a duplicate of this bug. ***,1406598882,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 149920 had a related patch set uploaded by Jforrester:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406594974,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Change 149920 had a related patch set uploaded by Catrope:
+Generate only one pair of snowmen for multi-sibling nodes
+
+https://gerrit.wikimedia.org/r/149920",1406573578,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Note from Jay8g:
+
+In this edit [https://en.wikipedia.org/w/index.php?title=Hong_Kong_International_Airport&diff=618742880&oldid=618629367], I got a snowman after rearranging (copy and paste) a sentence with {{convert}}. This did not show up in VE itself, and appeared in place of the comma that I had actually added (and that had displayed in VE).
+
+This seems to be the same problem.",1406568378,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp,"Comments from Erica on another bug:
+
+> 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.
+> 
+> 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 .",1406341582,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5vqpyeuqy5abgcxggp5x,task_subcomment,NA
+VisualEditor: Down-page of {{IPA-es}} backspace behaviour is very broken,"**Author:** `and1eternal1`
+
+**Description:**
+When typing, inserting templates, hitting ""backspace"", and possibly more actions, the cursor moves two characters left after every action. Obviously, this makes editing nearly impossible.
+
+Confirmed and repeatable on: https://en.wikipedia.org/wiki/Corcovado_Volcano?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405097400,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-grrxbpfjnax5tx6mcpya,task_description,resolved
+VisualEditor: Down-page of {{IPA-es}} backspace behaviour is very broken,*** Bug 67933 has been marked as a duplicate of this bug. ***,1406319801,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-grrxbpfjnax5tx6mcpya,task_subcomment,NA
+VisualEditor: Down-page of {{IPA-es}} backspace behaviour is very broken,Fixed by the fix for bug 67432.,1405967290,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-grrxbpfjnax5tx6mcpya,task_subcomment,NA
+VisualEditor: Down-page of {{IPA-es}} backspace behaviour is very broken,"Interesting. It looks like the template IPA-es is causing this. If you delete the template, everything works fine.",1405097625,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-grrxbpfjnax5tx6mcpya,task_subcomment,NA
+Local versions of system messages are ignored,"Yesterday a user reported on the Italian Wikipedia that several Mediawiki messages which have a local version there are being ignored (I guess the system is showing the original message available at Translatewiki, but can't check since that site is currently down). This doesn't seem to be targeting one product only.
+
+Examples:
+The button to launch the new TemplateData editor says ""Gestisci documentazione template"" (you can check at the top left of https://it.wikipedia.org/w/index.php?title=Template:Cassetto/man&action=edit ). It should read ""Gestisci TemplateData"" instead, as per https://it.wikipedia.org/wiki/MediaWiki:Templatedata-editbutton .
+
+Or see Table 1 at https://it.wikipedia.org/wiki/Discussioni_utente:Rotpunkt#Messaggi_che_non_funzionano . The link says ""Comprimi""/""Espandi"", but the correct messages, linked a few lines above the table, should actually be ""Nascondi""/""Mostra"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68781",1405001760,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_description,resolved
+Local versions of system messages are ignored,"(In reply to Matthew Flaschen from comment #37)
+> > And is ""II) Localisation cache returns ru when uk exists"" still a problem?
+> 
+> No one has identified a fix, so I would assume yes (even if the symptoms are
+> not exposed right now).
+> 
+> Filed as bug 68781.
+
+Thanks. CLosing this ticket about I) as FIXED as II) is handled there now.",1406713731,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Andre Klapper from comment #36)
+> (In reply to Andre Klapper from comment #35)
+> > NickK: Is this still a problem on Ukrainian Wikimedia sites?
+> 
+> And is ""II) Localisation cache returns ru when uk exists"" still a problem?
+
+No one has identified a fix, so I would assume yes (even if the symptoms are not exposed right now).
+
+Filed as bug 68781.",1406604188,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Andre Klapper from comment #35)
+> NickK: Is this still a problem on Ukrainian Wikimedia sites?
+
+And is ""II) Localisation cache returns ru when uk exists"" still a problem?",1406228586,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,NickK: Is this still a problem on Ukrainian Wikimedia sites?,1405614622,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,Lorenzo: Please create a separate ticket. This is offtopic.,1405597405,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Niklas Laxström from comment #32)
+> (In reply to Lorenzo Marconi from comment #31)
+> > Hello. On it.wiki we had changed the shortcut for the button ""Show preview""
+> 
+> This is separate issue and the cause is that ""-"" means that the message is
+> disabled and thus ""-"" cannot be used as an accesskey.
+
+Excuse me for the OT, but why it doesn't work only since a few days?",1405528698,PHID-USER-vzowt52hw2qfnu2w3eim,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Lorenzo Marconi from comment #31)
+> Hello. On it.wiki we had changed the shortcut for the button ""Show preview""
+
+This is separate issue and the cause is that ""-"" means that the message is disabled and thus ""-"" cannot be used as an accesskey.",1405523552,PHID-USER-732lqsmz4v6bss3kln2v,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Hello. On it.wiki we had changed the shortcut for the button ""Show preview"" from alt+shift+v to alt+shift+- (see it:MediaWiki:Accesskey-diff). That shortcut doesn't work for a few days (or weeks, dunno). Since I thought that problem had been solved (comment #27), it may be related to this bug or not?",1405522811,PHID-USER-vzowt52hw2qfnu2w3eim,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Nemo from comment #29)
+> Does the nutcracker issue completely explain findings I-II in comment 9? If
+> there are further underlying causes or possible improvements, separate bug
+> reports would be very useful once this one about the specific incident is
+> closed.
+
+Finding I, yes. Probably not finding II.
+
+I tracked that one as far as observing that the json file for uk that the cdb file gets built from has ""Править вики-текст"" as the value for messages:visualeditor-ca-editsource rather than ""Редагувати код"". That seems to be a separate issue from this one, and so should have its own bug report if it doesn't already.",1405436644,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Does the nutcracker issue completely explain findings I-II in comment 9? If there are further underlying causes or possible improvements, separate bug reports would be very useful once this one about the specific incident is closed.",1405434677,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Do the ResourceLoader caches need to be flushed to take care of any lingering issues? The entries in msg_resource with mr_timestamp less than 20140715002850 (based on comment 24) and mr_blob != '{}' are potentially problematic.
+
+At a quick look, this might apply to the following languages on wikis still on 1.24wmf12: ak af aln am ang anp arc ary as ast avk bbc bcl bg bi bo br brh ch ceb chr chy cr cps crh crh-latn cu dv dz ee en en-ca en-gb eu ext fj fo fy ga gom-latn got grc gu gv ha haw hi hif hif-latn hil hy ie ig ik ike-cans ike-latn ilo io iu jam jbo ka kab kbd kbd-cyrl kg khw ki km kri krj ks ks-arab ks-deva ku ku-latn kw ky la lfn lg li lo loz lrc lt lus lzh mai mdf mi mn mr my na ne new niu nl nl-informal nov nrm nso nv ny oc om or pag pam pap pi pih pnb pnt prg ps rif rm roa-tara rup rw sa sat sc sco sd sdc se sei sgs sh shi si sm sma sn so sq srn ss st sw te tet tg tg-cyrl tg-latn ti tk tl tly tn to tokipona tpi tru ts tt-latn tw ug ug-arab ug-latn ur uz ve vls vo war xh xmf yo yue zea zu. Other languages (except maybe uselang hacks) should have been updated already by the l10nupdate run at 02:00 UTC this morning.
+
+It looks like all languages on 1.24wmf13 wikis should have been updated by the l10nupdate run at 02:00 UTC this morning. This afternoon's update of non-Wikipedias to wmf13 should fix them too, BTW.",1405433305,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,It. and de.wp look fine though.,1405418946,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,Not sure if I should've actually closed it...,1405418010,PHID-USER-6vzzsmi22zem6yttr6vp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"reedy@tin:~$ mwscript eval.php itwiki
+> var_dump( MessageCache::singleton()->load( 'it' ) );
+bool(true)
+
+>",1405417968,PHID-USER-6vzzsmi22zem6yttr6vp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,<jgage> andre__: nutcracker is now updated on tin,1405384130,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"[01:09:35] <Reedy> I suspect it just hasn't had nutcracker updated on it
+[01:09:40] <Reedy> tin
+[01:09:41] <Reedy> nobody   23483  0.0  0.0  18732  1704 ?        Sl   Apr25   8:59 /usr/local/bin/nutcracker -m 65536 -a 127.0.0.1 -c /usr/local/apache/common-local/wmf-config/twemproxy-eqiad.yaml
+[01:09:46] <Reedy> mw1017
+[01:09:47] <Reedy> 112      14857  0.1  0.0  21652  2144 ?        Ssl  Jul07  13:11 /usr/sbin/nutcracker --mbuf-size=65536 --stats-port=22223
+[01:10:04] -*- jgage takes a look
+[01:10:10] <Reedy> Yeah
+[01:10:15] <Reedy> tin still is on ""twemproxy""
+[01:10:20] <Reedy> apaches are on ""nutcracker""",1405383049,PHID-USER-6vzzsmi22zem6yttr6vp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Ok, I think this is it. Turning on logging gives this from tin:
+
+ > var_dump( MessageCache::singleton()->load( 'it' ) );
+ [memcached] get(itwiki:messages:it:hash)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:hash"" on server ""127.0.0.1:11212"": CONNECTION FAILURE
+ [memcached] get(itwiki:messages:it)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] add(itwiki:messages:it:status)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:status"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] get(itwiki:messages:it:status)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:status"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] add(itwiki:messages:it:lock)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:lock"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] set(itwiki:test)
+ [memcached-serious] Memcached error for key ""itwiki:test"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] delete(itwiki:messages:it:lock)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:lock"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] get(itwiki:messages:it)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ [memcached] add(itwiki:messages:it:status)
+ [memcached-serious] Memcached error for key ""itwiki:messages:it:status"" on server ""127.0.0.1:11212"": SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
+ MessageCache::load: Loading it... global cache is empty, waited for other thread to complete, global cache is empty, could not acquire status key., loading FAILED - cache is disabled
+ bool(false)
+
+I think at this point we need to get an ops person involved.",1405373573,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"More information: Something is screwy on tin, which is where the cache flush is run.
+
+This command:
+
+ wfMessage( 'collapsible-collapse' )->inLanguage( 'it' )->plain()
+
+returns ""nascondi"" on terbium (and presumably other servers) but ""Comprimi"" on tin.",1405373034,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Certainly RL cache clearing: after the fix above, I reset the timestamp on the new row and re-ran the RL cache clearer (refreshMessageBlobs.php in WikimediaMaintenance) on itwiki. And it's re-broken.",1405371839,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Yeah, when we ran into this with a VE message a few days ago, I checked this. wfMessage( $msg )->plain() returned the correct version, but mw.msg( msg ) did not.",1405371051,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"As a test, I removed the database row for ResourceLoader's message cache for jquery.makeCollapsible for Italian on itwiki. And upon reload, it started serving the correct messages for that expand/collapse example.
+
+Which makes me suspect even more that the RL cache clearing is broken.",1405370820,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Are there any examples where the incorrect message is being displayed in the served HTML, rather than being served via ResourceLoader for use in JavaScript? I'm suspecting not, since I can open https://it.wikipedia.org/wiki/Discussioni_utente:Rotpunkt#Messaggi_che_non_funzionano and add ""{{int:Collapsible-expand}} {{int:Collapsible-collapse}}"" and see the correct messages despite the JS-added link in the table being wrong.
+
+That makes me suspect either RL's message cache isn't being cleared properly, or else something in it is broken such that it's not picking up the customized messages.",1405370300,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Re-adjusting importance fields. I'd say this constitutes a ""major loss of functionality"", and definitely should not take ""one to six months"" to fix.",1405367857,PHID-USER-ea6gwat27oulytc5tvsy,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Please not that this bug is critically important for Ukrainian: the message affected (VE Edit tab) is a prominent one, and the fallback displayed (Russian despite both local and global translations being correct) is very badly received by the community (to the point that some people suggest disabling VE).",1405367707,PHID-USER-2nmvdoea7rwpw6ql3ydo,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"In case this wasn't clear enough, this is affecting several wikis, including large ones like the French or the German WP.",1405330739,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"In reply to Niklas Laxström from comment #12)
+Understood. Thanks.",1405194762,PHID-USER-auec42hjrvg4pumgrmut,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Володимир Ф from comment #11)
+> Maybe first space in this message in database causes error?
+
+That is just how MessageCache::loadFromDB presents them internally. There is no space in front of that message in the database.",1405194451,PHID-USER-732lqsmz4v6bss3kln2v,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,">   string(28) "" Редагувати код""
+or ""Редагувати код""?
+Maybe first space in this message in database causes error?",1405193134,PHID-USER-auec42hjrvg4pumgrmut,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"(In reply to Niklas Laxström from comment #9)
+> III) (bonus) Unicode does not work on eval.php at WMF
+> For III) It would be nice for someone to file a separate bug.
+
+Done, see bug 67924",1405176012,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"I have made multiple observations:
+1) Typing unicode to mwscript eval.php does not work in WMF
+2) This particular message has existed in uk.json since April
+3) Other messages in the same file seem to work on random testing
+4) MessageCache thinks the message does not exist:
+mwscript maintenance/eval.php --wiki=ukwiki
+> var_dump( MessageCache::singleton()->getMsgFromNamespace( 'Visualeditor-ca-editsource', 'uk' ) );
+bool(false)
+
+Because of 1) I was not able to test whether calling MessageCache::replace would have fixed that.
+
+5) MessageCache can find the message if instructed manually to load messages directly from the database:
+mwscript maintenance/eval.php --wiki=ukwiki
+var_dump( MessageCache::singleton()->loadFromDB( 'uk' ) );
+  ..
+  [""Visualeditor-ca-editsource""]=>
+  string(28) "" Редагувати код""
+  ..
+
+6) Localisation cache returns the ru version:
+> var_dump( $wgLang->getLocalisationCache()->getSubItem( 'uk', 'messages', 'visualeditor-ca-editsource' ) );
+string(33) ""Править викитекст""
+
+7) I cannot reproduce this issue locally
+
+8) LC issue is possibly caused by incorrect fallback merging, because L10nupdate contains update for ru, but not for uk (because the translation is already up to date for uk):
+nikerabbit@tin:/var/lib/l10nupdate/cache-1.24wmf12$ grep visualeditor-ca-editsource *-ru.* *-uk.*
+Binary file l10n_cache-ru.cdb matches
+l10nupdate-ru.json:    ""visualeditor-ca-editsource"": ""\u041f\u0440\u0430\u0432\u0438\u0442\u044c \u0432\u0438\u043a\u0438\u0442\u0435\u043a\u0441\u0442"",
+l10nupdate-ru.json:    ""visualeditor-ca-editsource-section"": ""\u043f\u0440\u0430\u0432\u0438\u0442\u044c \u0432\u0438\u043a\u0438\u0442\u0435\u043a\u0441\u0442"",
+Binary file l10n_cache-uk.cdb matches
+
+9) Something fishy with message cache:
+mwscript maintenance/eval.php --wiki=ukwiki
+> var_dump( MessageCache::singleton() );
+object(MessageCache)#108 (8) {
+  ...
+  [""mDisable"":protected]=>
+  bool(false)
+  ..
+}
+
+mwscript maintenance/eval.php --wiki=ukwiki
+> var_dump( MessageCache::singleton()->getAllMessageKeys( 'uk' ) );
+NULL
+> var_dump( MessageCache::singleton()->load( 'uk' ) );
+bool(true)
+
+> var_dump( MessageCache::singleton() );
+object(MessageCache)#108 (8) {
+  [""mCache"":protected]=>
+  bool(false)
+  [""mDisable"":protected]=>
+  bool(true)
+  ..
+  [""mLoadedLanguages"":protected]=>
+  array(0) {
+  }
+  ..
+}
+
+
+My conclusions so far are that there seems to be at least two separate issues here:
+I) MessageCache is failing to load its cache
+II) Localisation cache returns ru when uk exists
+III) (bonus) Unicode does not work on eval.php at WMF
+
+For I) I would like other people to inspect why that is happening.
+For II) My observation in 8 is a good starting point for my investigations for someone else while I continue my vacation. This might be specific to the way WMF runs l10n update.
+For III) It would be nice for someone to file a separate bug.",1405159197,PHID-USER-732lqsmz4v6bss3kln2v,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,Updated importance fields per https://mediawiki.org/wiki/Bugzilla/Fields#Priority,1405148176,PHID-USER-w5a723w3wes6jd5wskgg,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Doesn't fit the definition of ""critical"", AFAICS.
+
+Did someone try rebuilding the l10n cache? Were there changed to the LocalisationUpdate or deploy scripts in the last few days? Did someone inspect their logs?",1405147928,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,*** Bug 67911 has been marked as a duplicate of this bug. ***,1405130110,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Yes, this is pretty bad.
+
+Amir/Niklas: Can you take a look into this ASAP?",1405126522,PHID-USER-z3l4i7dl52qicxtephy5,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"Escalating as this is now active on Ukranian Wikipedia too – https://uk.wikipedia.org/wiki/MediaWiki:Visualeditor-ca-editsource is correct but instead the Russian version, ""Править викитекст"" is showing in production.",1405125930,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"When I open this link in a private browsing window:
+
+https://it.wikipedia.org/w/index.php?title=Template:Cassetto/man&action=edit&uselang=it
+
+I see the default, non-customized button label for TemplateData, but I see the local, custom message for https://it.wikipedia.org/wiki/MediaWiki:Anoneditwarning",1405004992,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,It is indeed the original CDB translation (see https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FTemplateData.git/7136f55975d1f275e1c42fb0ad722c00e3ec5d82/i18n%2Fit.json).,1405002604,PHID-USER-ea6gwat27oulytc5tvsy,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+Local versions of system messages are ignored,"The original can be checked in the i18n directory of the source repo, e.g. https://git.wikimedia.org/tree/mediawiki%2Fcore.git/HEAD/languages%2Fi18n
+(Or in Special:AllMessages *if* it works.)
+
+Important note, Rotpunkt said this started happening between the 8th and the 9th, dates when no new MediaWiki version was deployed on it.wiki AFAICS.",1405002310,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-7y5kuddivdzl45gvwj6r,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,"I don't see the option to add Cite/References in Mobile Ve anymore in any mode .Is it switched off intentionally?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404862020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gyvrffyluoyvwurby4pu,task_description,resolved
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,Verified the fix in production en.wiki,1406317420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gyvrffyluoyvwurby4pu,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,Verified the fix in test2,1405723303,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gyvrffyluoyvwurby4pu,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,"Change 146962 merged by jenkins-bot:
+Enable mwreference, mwtransclusion modules on all targets including mobile
+
+https://gerrit.wikimedia.org/r/146962",1405550583,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gyvrffyluoyvwurby4pu,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes,"Change 146962 had a related patch set uploaded by Jforrester:
+Enable mwreference, mwtransclusion modules on all targets including mobile
+
+https://gerrit.wikimedia.org/r/146962",1405550402,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gyvrffyluoyvwurby4pu,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Inspired by comments at various wikis and at bug 63389:
+pretty much what the summary says.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63389",1404763440,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_description,resolved
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 163029 merged by jenkins-bot:
+Let help link target be locally over-ridden; default to the MW help page
+
+https://gerrit.wikimedia.org/r/163029",1413914032,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 163029 had a related patch set uploaded by Jforrester:
+Let help link target be locally over-ridden; default to the MW help page
+
+https://gerrit.wikimedia.org/r/163029",1411680434,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,Looks like it is. Thanks!,1411670233,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,Have pointed it to https://www.mediawiki.org/wiki/Help:TemplateData instead – hope that's OK.,1411668181,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"James, if the link can't point to the local help page for each wiki, please redirect it to https://www.mediawiki.org/wiki/VisualEditor/Portal/TemplateData .",1411156930,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 134928 merged by jenkins-bot:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1409438730,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 134928 had a related patch set uploaded by Jforrester:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1409437169,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+TemplateData: add tooltip/quick link to TD help page near new TD editor button,"Change 134928 had a related patch set uploaded by Mooeypoo:
+Refactor TemplateData Editor
+
+https://gerrit.wikimedia.org/r/134928",1406664777,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5u7yrk6gecrewqxqwwkc,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector","Steps to reproduce:
+
+1.Open a page with VE
+2.Open the language inspector
+3.Now Open the language selector dialog
+4.Select any language or just close the dialog
+
+Observed Result:
+The following error appears in the console:
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds
+
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404756540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cjhmjbqvl2impaei6gum,task_description,resolved
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector",Verified the fix in production en.wiki,1406316738,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector",Verified the fix in test2,1405724138,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector",Verified the fix in Betalabs,1405545794,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector","Yeah, fixed probably by Trevor's re-write of windows.",1405439083,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+"VisualEditor: [Regression wmf13] ""Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds"" appears upon selecting language or closing the language selector",Appears to be fixed in master.,1405426136,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cjhmjbqvl2impaei6gum,task_subcomment,NA
+VisualEditor: Snowmen appearing for some reason,"https://pt.wikipedia.org/w/index.php?diff=39208742
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404736800,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-fj2r7bnjbarkjkyc42pf,task_description,resolved
+VisualEditor: Snowmen appearing for some reason,"Merging with bug 57884 then.
+
+*** This bug has been marked as a duplicate of bug 57884 ***",1404767562,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fj2r7bnjbarkjkyc42pf,task_subcomment,NA
+VisualEditor: Snowmen appearing for some reason,Not really. I found that page by chance (while playing the Wikidata Game).,1404764786,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-fj2r7bnjbarkjkyc42pf,task_subcomment,NA
+VisualEditor: Snowmen appearing for some reason,Any reproduction steps? :-(,1404762943,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fj2r7bnjbarkjkyc42pf,task_subcomment,NA
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,"See at http://en.wikipedia.beta.wmflabs.org/wiki/0.37197036937123?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404562920,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vebbfxury34xj3qnszdg,task_description,resolved
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,"Change 816703 had a related patch set uploaded (by Xqt; author: Xqt):
+%%%[pywikibot/core@master] [BUGFIX] Add localized ""archive"" variables to archivebot.py%%%
+https://gerrit.wikimedia.org/r/816703",1658737382,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vebbfxury34xj3qnszdg,task_subcomment,NA
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,"Change 144136 merged by jenkins-bot:
+Fixes to getRelativeOffset and getRelativeRange
+
+https://gerrit.wikimedia.org/r/144136",1405445152,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vebbfxury34xj3qnszdg,task_subcomment,NA
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,"Change 144136 had a related patch set uploaded by Esanders:
+Fixes to getRelativeOffset and getRelativeRange
+
+https://gerrit.wikimedia.org/r/144136",1405019105,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vebbfxury34xj3qnszdg,task_subcomment,NA
+VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node,Also pressing left in the first slug takes you forward.,1404563023,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vebbfxury34xj3qnszdg,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,"Currently Hovercards just takes the title attribute and uses that value as the article that it wants to preview.
+
+This does not handle many types of links, nor is not very reliable in combination with image links.
+
+Hovering an image like: [[File:S can.gif|18px|link=Cancer (astrology)|Cancer]] Will show you the article 'Cancer' instead of 'Cancer (astrology)' for instance, because inline images set their link title attribute to the caption.
+
+
+A link interpreter is also much more flexible and would be able to identify, different types of links.
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1404379320,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_description,resolved
+Hovercards: Use a link interpreter instead of title attribute,"As @ricordisamoa points out, we did switch to using a link interpreter when @wctaiwan fixed {T93605}. ",1444923799,PHID-USER-gc5hdyw5p4np7atqjynz,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,">>! In T69466#1691123, @Ricordisamoa wrote:
+> I'm not aware of any steps that could be made to improve the status quo without needing Parsoid
+
+BTW, according to [[ //www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Wiki_links | spec ]], Parsoid does nothing to make parsing the title easier, in fact here's what VisualEditor does:
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/867c63e9b235968f2a9f92c75b483b719b222609/modules/ve-mw/dm/annotations/ve.dm.MWInternalLinkAnnotation.js#L92",1443649219,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,">>! In T69466#1690148, @Jdlrobson wrote:
+> Thanks for the clarification @Ricordisamoa but still `href` is not ideal. Can you update the title/description accordingly?
+
+I'm not aware of any steps that could be made to improve the status quo without needing Parsoid (which would be very bad for small wikis) or T40598.
+And after all, the current mechanism is kind of a link interpreter already.",1443648123,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,Thanks for the clarification @Ricordisamoa but still `href` is not ideal. Can you update the title/description accordingly?,1443634812,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,">>! In T69466#1681893, @Jdlrobson wrote:
+> To obtain the title of the page associated with the wiki link it relies on the title attribute, which is sometimes accurate.
+
+Wrong. It has been relying on href since https://gerrit.wikimedia.org/r/199694.",1443580273,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,"So my interpretation of this is:
+Hovercards hijacks wiki links and gives a preview of the pages they refer to to save clicks to them.
+To obtain the title of the page associated with the wiki link it relies on the title attribute, which is sometimes accurate.
+My question is, does Parsoid mark up links so that it is clear which page title they relate to?
+",1443461847,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,">>! In T69466#1681157, @Jdlrobson wrote:
+> @ssastry I assume this is something Parsoid solves? If we used Parsoid as the main parser would this be given for free? 
+
+I don't fully understand how hovercards work, but from the description, it looks like it relies on the title attribute? Right now, Parsoid doesn't set the title attribute for images.
+
+But, the description / title also says ""link intepreter"" and I don't know what that means either.
+
+So, need more specifics about what hovercards needs to function properly and we can talk more if Parsoid can support that out of the box.
+",1443461723,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,@ssastry I assume this is something Parsoid solves? If we used Parsoid as the main parser would this be given for free? ,1443454894,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+Hovercards: Use a link interpreter instead of title attribute,@ssastry I assume this is something Parsoid solves? If we switched Hovercards to use a Parsoid based service would this solve this problem?,1443454824,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-dbp5fnytgn27ydme3c6e,task_subcomment,NA
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged","Screenshot
+
+1.Open a page with VE
+2.Select an image
+3.Click on the ""Change Image"" button
+4.It will take you back to the Media Search dialog box
+
+
+Observed Result:
+Observe that,the ""Apply Changes"" button is enabled on the search dialog box
+Clicking on that will not have any effect.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14223}",1404346260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iu3lzoun25ro22ahnfsl,task_description,resolved
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged",Verified the fix in production,1405028848,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iu3lzoun25ro22ahnfsl,task_subcomment,NA
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged",Verified the fix in test2,1404422235,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iu3lzoun25ro22ahnfsl,task_subcomment,NA
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged","Change 143749 merged by jenkins-bot:
+UX Improvements to the Media Dialog
+
+https://gerrit.wikimedia.org/r/143749",1404350085,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iu3lzoun25ro22ahnfsl,task_subcomment,NA
+"VisualEditor:Disable ""Apply changes"" button on Media Search dialog now that the Edit and search dialog both are merged","Change 143749 had a related patch set uploaded by Jforrester:
+UX Improvements to the Media Dialog
+
+https://gerrit.wikimedia.org/r/143749",1404348184,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iu3lzoun25ro22ahnfsl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Type a text
+3.Select the text
+4.Open the link inspector to apply link on it
+5.Type something inside the link inspector
+
+Observed Result:
+No link suggestions are appearing in the link inspector.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14198}",1404334680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7mhhjati7jq7vehinugh,task_description,resolved
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,Verified the fix in Betalabs,1411066338,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Change 161150 merged by jenkins-bot:
+Followup 6c862e8: position before AND after showing in TextInputMenuWidget
+
+https://gerrit.wikimedia.org/r/161150",1411002301,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Change 161150 had a related patch set uploaded by Catrope:
+Followup 6c862e8: position before AND after showing in TextInputMenuWidget
+
+https://gerrit.wikimedia.org/r/161150",1411001944,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,This got broken again apparently in last few hours.,1410999140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,Verified the fix in production,1405028895,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,Verified the fix in test2,1404421697,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,Verified the fix in Betalabs,1404409597,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Change 143782 merged by jenkins-bot:
+Followup 96ff968: use this.$element after it's initialized, not before
+
+https://gerrit.wikimedia.org/r/143782",1404341858,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE,"Change 143782 had a related patch set uploaded by Catrope:
+Followup 96ff968: use this.$element after it's initialized, not before
+
+https://gerrit.wikimedia.org/r/143782",1404341374,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7mhhjati7jq7vehinugh,task_subcomment,NA
+VisualEditor Mobile: references context selection is wonky,"It's pretty much impossible to open the references context toolbar to edit an existing reference.
+
+Steps to reproduce:
+
+1. Open an article in VE editing mode on an iPad
+2. Tap on any reference footnote in the body of the article – sometimes the reference context toolbar appears, sometimes it doesn't, and sometimes it appears for a second and scrolls away.
+3. If you've managed to get the reference context toolbar to appear, tap it – sometimes it takes you to the link inspector, and sometimes it takes you to a new blank citation form
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67390
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67637",1404329700,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-ffazj5r46gg74oi7gacd,task_description,resolved
+VisualEditor Mobile: references context selection is wonky,Looks like this is now fixed thanks to Juliusz's new context menu changes.,1406747326,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ffazj5r46gg74oi7gacd,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"Copied from my Russian Wikipedia talk page:
+
+After reference VE added symbol ""♙"".
+
+sample for https://ru.wikipedia.org/w/index.php?title=Гёрлфренд&oldid=58928673&veaction=edit
+
+find ref№3 -> ""к подруге.[3]""
+click after the dot -> ""к подруге.|[3]""
+delete the dot with backspace  back  ->""к подруге|[3]""
+press en:Arrow keys  →  two times ->""к подруге[3]|""
+press key dot  .  ->
+expected that will be shown the symbol ""."" -> ""к подруге[3].|""
+but it shows the symbol ""♙"" ->""к подруге[3]♙|""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404328260,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-vggdj3oaoiimjl76co4b,task_description,resolved
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"Change 145346 merged by jenkins-bot:
+Make sure the document is focused when setting a selection
+
+https://gerrit.wikimedia.org/r/145346",1405383662,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,Upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1037004,1405008743,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"Change 145346 had a related patch set uploaded by Esanders:
+Make sure the document is focused when setting a selection
+
+https://gerrit.wikimedia.org/r/145346",1405007554,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,Monitoring document.activeElement (the currently focussed element) it's apparent that simply setting a selection on the document (back from the paste target) doesn't changed the focussed element. This means you can move your cursor in one textbox and type in another. What the hell Firefox...,1405006352,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"This happens just by typing anything after an inline focusable node after cursoring off it (nothing to do with deletion). If the node is at the end of a paragraph you get a pawn, but if it isn't you get equally broken behaviour with the cursor not moving properly.",1404942081,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"(In reply to Elitre from comment #2)
+> If this happens in FF, can it be related to bug 54917?
+
+Doesn't look like it; this was caused by insertion, not cursoring.",1404760957,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,"If this happens in FF, can it be related to bug 54917?",1404738178,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox,Sounds like a VE issue. Moving there.,1404328383,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-vggdj3oaoiimjl76co4b,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media and select any image after searching
+
+Observed Result:
+When the Media settings dialog pop-up, observe that all the icons for the tabs General Settings, Advanced Settings and the headings Caption,Alternative text, Position,Image Type, Image Size etc are missing
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14179}",1404325620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-erh6pdj44sgbbysd6pck,task_description,resolved
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,Verified the fix in production,1405028578,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-erh6pdj44sgbbysd6pck,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,Verified the fix in betalabs and test2,1404769312,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-erh6pdj44sgbbysd6pck,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,Almost certainly a Beta Labs problem of the moment.,1404331449,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-erh6pdj44sgbbysd6pck,task_subcomment,NA
+VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs,"This is also happening for Basic reference, cite news , cite journal and reference list dialog as well.",1404326088,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-erh6pdj44sgbbysd6pck,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the semi-highlight is still happening on selection of a node when there is no text cursor activation upon opening a page on Mobile VE","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Do not place your cursor anywhere on CE but try to select a node 
+Observed Result:
+The semi-highlight of lighter shade appears over the node and tapping on it for the second time selects it with darker highlight.
+
+It might get resolved with :https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+
+Still I am filing it as a separate issue.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+
+**Attached**: {F14690}",1404249300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cwv4uf7sks54skkmccyq,task_description,resolved
+"VisualEditor Mobile: In iOS Safari, the semi-highlight is still happening on selection of a node when there is no text cursor activation upon opening a page on Mobile VE",Verified the fix in production,1405626233,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cwv4uf7sks54skkmccyq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the semi-highlight is still happening on selection of a node when there is no text cursor activation upon opening a page on Mobile VE","This is not happening anymore,Checked in Betalabs and test2 .
+Marking it as fixed",1404780385,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cwv4uf7sks54skkmccyq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, after adding a link, the cursor still blinks on CE in the position where it was appearing inside the search box for link inspector","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE in iOS Safari
+2.Select a text
+3.Click on the link icon from the toolbar
+4.Type a link target page inside link inspector and apply it
+
+Observed Result:
+The cursor that was appearing inside the search box of a link inspector remains on the screen appearing over the title of the page
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14689}",1404245460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hzeisownarrcldmlrur4,task_description,resolved
+"VisualEditor Mobile: In iOS Safari, after adding a link, the cursor still blinks on CE in the position where it was appearing inside the search box for link inspector",Verified the fix in production en.wiki,1406318823,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hzeisownarrcldmlrur4,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, after adding a link, the cursor still blinks on CE in the position where it was appearing inside the search box for link inspector",Verified the fix in test2,1405719892,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hzeisownarrcldmlrur4,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, after adding a link, the cursor still blinks on CE in the position where it was appearing inside the search box for link inspector",Fixed by Trevor's mobile styling work.,1405558544,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hzeisownarrcldmlrur4,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Type a template name such as ""Cite Web""
+
+Observed Result:
+In the template suggestion drop dwon box all template names are appearing with a prefix ""Template:""
+
+See the screenshot attached
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14680}",1404242520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_description,resolved
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box",Verified the fix in production,1405028961,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box",Verified the fix in test2,1404421631,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box",Verified the fix in Betalabs,1404409700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box","Change 143685 merged by jenkins-bot:
+Try some more to handle template namespace properly
+
+https://gerrit.wikimedia.org/r/143685",1404350629,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+"VisualEditor: For all templates , ""Template:"" is getting added as a prefix while searching from Template dialog box","Change 143685 had a related patch set uploaded by Alex Monk:
+Try some more to handle template namespace properly
+
+https://gerrit.wikimedia.org/r/143685",1404330111,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dxzb43i42p6jkhs4k3pq,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Writing https://gerrit.wikimedia.org/r/143322 , I realized that the `ve.ce.isShortcutKey( e )` check in ve.ce.Surface (which rejects every keypress event where Ctrl or Cmd is pressed) sometimes prevent legit keypresses from being handled.
+
+To reproduce (in any browser):
+
+* Place cursor on an empty line.
+* Input 'ą' ([[ą]]). This is accomplished by pressing AltGr+a (right Alt+a, Alt+Ctrl+a) when using the ""Polish (Programmers)"" keyboard layout on Windows 7 (this is the default layout for Polish).
+* Type in something else. The 'ą' disappears, because it was never handled by ve.ce, only by native contenteditable element.
+
+I only tested this on Windows 7, but I believe other operating systems all use the same method. Other letters with diacritics from the [[Polish alphabet]] are input in the same way (AltGr + base key), we have nine of them.
+
+On Windows 7 you can enable this keyboard layout by typing ""keyboard layout"" into the Start menu, choosing ""Change keyboards…"" and adding the input method.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404226500,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_description,resolved
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),Proper fixed!,1419338125,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Change 181174 merged by jenkins-bot:
+ve.ce: Remove hacks from Surface#onDocumentKeyPress; add related IME test
+
+[[https://gerrit.wikimedia.org/r/181174]]",1419335362,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Change 181173 merged by jenkins-bot:
+imetests: Add a regression test for Polish keyboard input
+
+[[https://gerrit.wikimedia.org/r/181173]]",1419335358,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Change 181174 had a related patch set uploaded (by Bartosz Dziewoński):
+ve.ce: Remove hacks from Surface#onDocumentKeyPress, add related IME test
+
+[[https://gerrit.wikimedia.org/r/181174]]
+
+#patch-for-review",1419026959,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Change 181173 had a related patch set uploaded (by Bartosz Dziewoński):
+imetests: Add a regression test for Polish keyboard input
+
+[[https://gerrit.wikimedia.org/r/181173]]
+
+#patch-for-review",1419026957,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),Let's do that.,1419026098,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),Yes! See fakeIMETests. Please use the script to generate a previously-failing test case so we lock this in. :-),1419021276,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"This no longer happens. Just for the kicks I bisected and found that the commit that fixed the bug is 40101e42a4544768ac624ef2b4da0e7d44b69b65 (https://gerrit.wikimedia.org/r/#/c/151046/).
+
+I wonder if we could have a browser test to prevent this from regressing? (It was fixed accidentally, could be broken accidentally again.)
+
+I also wonder if we need the checks in `ve.ce.Surface.prototype.onDocumentKeyPress` at all anymore? Removing them doesn't seem to cause the issue they're supposed to prevent (""Unexpected content deletion when selection is not collapsed and the user presses, for example, the Home key (Firefox fires 'keypress' for it)"").",1419020102,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Hmph, we can't kill this code yet. It's not just to prevent pawning, it's also to prevent the selection from being deleted when you press a shortcut key. We'll need David's next project (prepare-observe-fixup) to be done before we can get rid of this, I think.",1413940427,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),I can still reproduce on betalabs.,1413746460,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"(In reply to Roan Kattouw from comment #2)
+> (In reply to James Forrester from comment #1)
+> > Is this now fixed, given that we've killed pawns?
+> 
+> We haven't quite killed them yet, the chimera commit does that.
+
+But we should make sure that that commit also kills this logic; which right now I'm not sure that it does.",1413329653,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"(In reply to James Forrester from comment #1)
+> Is this now fixed, given that we've killed pawns?
+
+We haven't quite killed them yet, the chimera commit does that.",1413329628,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line),"Is this now fixed, given that we've killed pawns?",1413329572,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2fo2vepgfvoop6cua3yb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a reference
+3.Go to the option Use an existing reference
+
+Observed Result:
+In the dialog for using an existing reference, the reference name for the reference just added is missing just the reference number appears inside the bracket.
+Opening it for the second time brings up the reference name
+
+See the screenshot attached
+
+Environment:http://en.m.wikipedia.beta.wmflabs.org/
+Both on Desktop browser and iOS Device
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68869
+
+**Attached**: {F14576}",1404175680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-povdwehsnsp3g7l76hmb,task_description,resolved
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time",Verified the fix in production for both desktop and mobile,1408046784,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time",Verified the fix in test2,1407192494,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time",Should be solved.,1406765032,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time","Change 150736 merged by jenkins-bot:
+Don't clone internal item node element used for references in re-use citation dialog
+
+https://gerrit.wikimedia.org/r/150736",1406764794,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time","Change 150736 had a related patch set uploaded by Alex Monk:
+Don't clone internal item node element used for references in re-use citation dialog
+
+https://gerrit.wikimedia.org/r/150736",1406764576,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+"VisualEditor: The reference name for a newly added reference is not appearing in the dialog for ""Use existing reference"" while opening it for the first time","This is happening in desktop as well , not when you add Basic reference but cite references.",1406677463,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-povdwehsnsp3g7l76hmb,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"**Author:** `oliver.buchtala`
+
+**Description:**
+Probably a matter of taste, but we find the embedded control not too appealing.
+In our case (a block equation) the button to open the inspector is typically below. However, when the element is growing (2+ lines), it is suddenly on the right-hand side.
+
+It would be great if there was a way to control that and override the present behavior if desired.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404139740,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hiqmkuftu6tynmzgz27e,task_description,resolved
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"
+
+*** This bug has been marked as a duplicate of bug 66542 ***",1408710950,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"The original request was about optional disabling embedding, but this I suppose ""fixes"" the issue (though really that was bug 66542).",1404248899,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"Change 143393 merged by jenkins-bot:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/143393",1404247814,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"Change 143393 had a related patch set uploaded by Esanders:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/143393",1404245015,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node,"It would be nice to keep it consistent, although for a live-updating node it would certainly make sense to keep the context menu out of the way (at least when it is open).",1404232676,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hiqmkuftu6tynmzgz27e,task_subcomment,NA
+VisualEditor Mobile: Focusable nodes can't be deleted,"(Chrome mobile)
+Clicking on a focusable node doesn't bring up the keyboard so there is no access to the backspace key. Even if you click on text then the focusable node, the backspace key doesn't work.
+
+Regardless a mobile user would expect to have a separate control for deleting focusable nodes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403981520,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ulr4ihyno7bftkrdq7gf,task_description,resolved
+VisualEditor Mobile: Focusable nodes can't be deleted,"Same problem as on iOS. Merging.
+
+*** This bug has been marked as a duplicate of bug 60110 ***",1407064915,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ulr4ihyno7bftkrdq7gf,task_subcomment,NA
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it","The same node sometimes is deleted and sometimes isn't. Appears to apply to block and inline nodes alike. Can't work out exact reproduction steps. Race condition?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403829360,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ewm6busofenduqisc4ug,task_description,resolved
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it","Change 142527 merged by jenkins-bot:
+Always refocus the paste target when a node is selected
+
+https://gerrit.wikimedia.org/r/142527",1403889430,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ewm6busofenduqisc4ug,task_subcomment,NA
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it","Change 142527 had a related patch set uploaded by Esanders:
+Always refocus the paste target when a node is selected
+
+https://gerrit.wikimedia.org/r/142527",1403878950,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ewm6busofenduqisc4ug,task_subcomment,NA
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it",I can reproduce by clicking directly from one node to another. Looks like a focus issue.,1403862835,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ewm6busofenduqisc4ug,task_subcomment,NA
+"VisualEditor: Pressing ""delete"" / ""backspace"" when selecting a node sometimes does not delete it","Definitely no clean repro - comes and goes as you click on templates. But once it stops working in a session, it seems to stop for good.",1403830621,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-ewm6busofenduqisc4ug,task_subcomment,NA
+VisualEditor: Typing when a focusable node is selected should do nothing,"Correct outcome:
+
+* Select an inline image (or a reference or alien or…).
+* Press ""a"".
+
+Observe that the reference has been deleted, and an 'a' is in its place.
+
+
+Bad outcome;
+
+* Select a block image (or block template or…).
+* Press ""a"".
+
+Observe that the block image has not been deleted, and the 'a' is not in its place (and no transaction has occurred).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403829240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zjrtgmgipdtxr4pdqjch,task_description,resolved
+VisualEditor: Typing when a focusable node is selected should do nothing,"Change 146808 merged by jenkins-bot:
+Prevent deletion of focusable nodes by typing
+
+https://gerrit.wikimedia.org/r/146808",1405551075,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zjrtgmgipdtxr4pdqjch,task_subcomment,NA
+VisualEditor: Typing when a focusable node is selected should do nothing,"Change 146808 had a related patch set uploaded by Esanders:
+Prevent deletion of focusable nodes by typing
+
+https://gerrit.wikimedia.org/r/146808",1405529411,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zjrtgmgipdtxr4pdqjch,task_subcomment,NA
+VisualEditor: Typing when a focusable node is selected should do nothing,"Real world comparison:
+* Open/Libre office: typing while selecting an image does nothing
+* Google docs: typing replaces the image
+
+I think it's a rare workflow where you select a block image and want to replace it with a paragraph, and if you really do you can just press backspace/delete. We have taken other measures to prevent the accidental deletion of focusable nodes elsewhere (e.g. adjacent backspace only selects) so this seems like a logical extension.",1405529394,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-zjrtgmgipdtxr4pdqjch,task_subcomment,NA
+VisualEditor: Double-click should not open items that shouldn't be opened,"References defined inside a {{reflist}} aren't editable – but double-click now opens the reference dialog (to empty content).
+
+I imagine this happens for a few things.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403829060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-utovzemiq3m7agsxe4zz,task_description,resolved
+VisualEditor: Double-click should not open items that shouldn't be opened,"Change 143352 merged by jenkins-bot:
+Hide context tools when the model they match isn't ""inspectable""
+
+https://gerrit.wikimedia.org/r/143352",1404249479,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-utovzemiq3m7agsxe4zz,task_subcomment,NA
+VisualEditor: Double-click should not open items that shouldn't be opened,"Change 143352 had a related patch set uploaded by Esanders:
+Hide context tools when the model they match isn't ""inspectable""
+
+https://gerrit.wikimedia.org/r/143352",1404234623,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-utovzemiq3m7agsxe4zz,task_subcomment,NA
+VisualEditor: Double-click should not open items that shouldn't be opened,"(In reply to Ed Sanders from comment #1)
+> Link to an example?
+
+First reference on https://en.wikipedia.org/wiki/Anne_Dallas_Dudley?veaction=edit – appears to be an issue with references more generally, and affects the context too. Bother.",1403987115,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-utovzemiq3m7agsxe4zz,task_subcomment,NA
+VisualEditor: Double-click should not open items that shouldn't be opened,Link to an example?,1403968584,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-utovzemiq3m7agsxe4zz,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"I have tried running the unit tests with both Echo and Math installed and ends up with a database error:
+
+```
+$ ls -1 extensions
+Echo
+Math
+README
+```
+
+```
+$ cd tests/phpunit
+$ php phpunit.php --tap --testsuite extensions
+not ok 588 - Error: MathDatabaseTest::testCreateTable
+A database query error has occurred.
+Query: DELETE FROM unittest_math
+Function: MediaWikiTestCase::resetDB
+Error: 1 no such table: unittest_math
+
+
+---
+
+#0 /core/includes/db/Database.php(1134): DatabaseBase->reportQueryError('no such table: ...', 1, 'DELETE FROM uni...', 'MediaWikiTestCa...', false)
+#1 /core/includes/db/Database.php(2919): DatabaseBase->query('DELETE FROM uni...', 'MediaWikiTestCa...')
+#2 /core/tests/phpunit/MediaWikiTestCase.php(572): DatabaseBase->delete('math', '*', 'MediaWikiTestCa...')
+#3 /core/tests/phpunit/MediaWikiTestCase.php(138): MediaWikiTestCase->resetDB()
+#4 /pear/PHPUnit/Framework/TestSuite.php(775): MediaWikiTestCase->run(Object(PHPUnit_Framework_TestResult))
+#5 /pear/PHPUnit/Framework/TestSuite.php(745): PHPUnit_Framework_TestSuite->runTest(Object(MathDatabaseTest), Object(PHPUnit_Framework_TestResult))
+#6 /pear/PHPUnit/Framework/TestSuite.php(705): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)
+#7 /pear/PHPUnit/Framework/TestSuite.php(705): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)
+#8 /pear/PHPUnit/Framework/TestSuite.php(705): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)
+#9 /pear/PHPUnit/TextUI/TestRunner.php(349): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)
+#10 /pear/PHPUnit/TextUI/Command.php(176): PHPUnit_TextUI_TestRunner->doRun(Object(PHPUnit_Framework_TestSuite), Array)
+#11 /core/tests/phpunit/MediaWikiPHPUnitCommand.php(42): PHPUnit_TextUI_Command->run(Array, true)
+#12 /core/tests/phpunit/phpunit.php(160): MediaWikiPHPUnitCommand::main()
+#13 {main}
+```
+
+
+Also the Math extension seems to be running the updater in the test.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403805420,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_description,resolved
+Math tests dies when run with the Echo extensions,"This original problem reported seems to be fixed now.
+Hoever, there is another unrelated error
+```
+ok 948 - ResourcesTest::testStyleMedia with data set #13 ('skins.vector.styles', 'screen and (min-width: 982px)', 'screen-hd.less', stdClass Object (...))
+ok 949 - ResourcesTest::testIllegalDependencies
+not ok 950 - Failure: ResourcesTest::testMissingDependencies
+  ---
+  message: 'The module ''ext.visualEditor.mwcore'' required by ''ext.math.visualEditor'' must exist'
+  severity: fail
+  ...
+not ok 951 - Error: ResourcesTest::testUnsatisfiableDependencies
+ok 952 - ResourcesTest::testMediaWikiTestCaseParentSetupCalled
+```",1420904055,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"This original problem reported seems to be fixed now.
+However changing the order or inclusion in the way that math is included before echo leads to the following error
+```
+ok 948 - ResourcesTest::testStyleMedia with data set #13 ('skins.vector.styles', 'screen and (min-width: 982px)', 'screen-hd.less', stdClass Object (...))
+ok 949 - ResourcesTest::testIllegalDependencies
+not ok 950 - Failure: ResourcesTest::testMissingDependencies
+  ---
+  message: 'The module ''ext.visualEditor.mwcore'' required by ''ext.math.visualEditor'' must exist'
+  severity: fail
+  ...
+not ok 951 - Error: ResourcesTest::testUnsatisfiableDependencies
+ok 952 - ResourcesTest::testMediaWikiTestCaseParentSetupCalled
+```
+And the number of tests that were executed reduces from 1818 to 1547",1420902798,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Would need to be tried again, it might have been fixed.",1420837178,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"**physik** wrote:
+
+This Bug is not related to the math extension.
+My experience is the following
+At first I could reproduce a similar error as reported in the bug report. But the error indicated that database access related to the echo extension caused the error.
+To investigate further I changed the order in the Localsettings.php an loaded Math before echo.
+I wanted to reproduce exactly the problem that you had reported before. But no error occurred. After switching the order back the error did not come back.
+AS a result I think the error is not related to the Math extension, rather to the sqllite db backend. Especially given the fact that the error does not occur with mysql",1406420211,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,*** Bug 68628 has been marked as a duplicate of this bug. ***,1406408729,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Still the same error with latest master of Math Echo and core:
+
+not ok 588 - Error: MathDatabaseTest::testCreateTable
+A database query error has occurred.
+Query: DELETE FROM unittest_math
+Function: MediaWikiTestCase::resetDB
+Error: 1 no such table: unittest_math",1406274723,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Antoine, is it fine for you now?",1406247567,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Change 142739 merged by jenkins-bot:
+Fix MathDatabaseTest
+
+https://gerrit.wikimedia.org/r/142739",1405042641,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,Sure! See comment 1. Install a stock MediaWiki core with extensions Echo and Math.  That should trigger the issue.,1404145580,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"**physik** wrote:
+
+does the problem disappear if you disable the Echo module?
+Are those tests using sqlite?",1404140080,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,We really need tests to pass when all wmf extensions are installed together. That is preventing us from progression toward the HHVM migrating. Raising priority to High.,1404137324,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"Change 142739 had a related patch set uploaded by Physikerwelt:
+Fix MathDatabaseTest
+
+https://gerrit.wikimedia.org/r/142739",1403907884,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"I did ran update.php
+
+A slightly more complicated test I ran in Jenkins is:
+
+https://integration.wikimedia.org/ci/job/mediawiki-core-extensions-integration/38/consoleFull
+
+
+It clones a bunch of extensions, load their entry points then run install.php and then update.php
+
+ 00:01:04.861 Creating math table ...done.
+
+
+The dberror:
+
+ Thu Jun 26 16:15:01 UTC 2014	gallium	build38-unittest_	MediaWikiTestCase::resetDB		1	no such table: unittest_math	DELETE FROM unittest_math",1403898654,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"**physik** wrote:
+
+did you run update.php before?
+As far as I understand the database tests copy the schema with and prefix the tables with untitest. If there is no math table in the base schema no table will be created in the copied unittest schema.
+The database test tries to delete the test schema and creates a new one.
+We should either improve the error message or ignore the missing math table in the  main database. I don't know which option is better?",1403887803,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+Math tests dies when run with the Echo extensions,"tests/MathDatabaseTest.php has:
+
+ public function testCreateTable() {
+  ...
+  $dbu->doUpdates( array( ""extensions"" ) );
+  ...
+
+among other. Commenting out the function let us continue the test suite.",1403805649,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kaupnnwmc22zgqdjwdqc,task_subcomment,NA
+VisualEditor: Cursor is appearing in the read mode in Firefox after canceling the edit in VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in FireFox
+2.Without editing just click on ""Cancel"" button 
+
+Observed Result:
+The cursor is still appearing at the end of the page in read mode.
+
+See the screenshot attached
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14619}",1403739000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zvw4nqatdijriyfaposh,task_description,resolved
+VisualEditor: Cursor is appearing in the read mode in Firefox after canceling the edit in VE,I think we fixed this a long time ago (and then it recurred and we fixed that one too).,1416794925,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvw4nqatdijriyfaposh,task_subcomment,NA
+VisualEditor: Cursor is appearing in the read mode in Firefox after canceling the edit in VE,"This is happening in production now, so environment is not just Betalabs now.",1403892554,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zvw4nqatdijriyfaposh,task_subcomment,NA
+VisualEditor: [Regression] Pawn appears when inserting a link (no preselected text) and implicitly exiting from the inspector,"(from bug 67086)
+
+1. Press ""Link"" tool.
+2. Enter a link target (url or page name).
+3. Select the url or page name from the suggestions.
+- Notice that the surface still shows your blinking cursor with no link or text
+4. Click back into the surface and type text.
+
+Expected behaviour:
+
+The link becomes a pre-annotation and the entered text the label.
+Or, alternatively, the link autosaves and inserts itself and my text appears after the link.
+
+Actual behaviour:
+
+* First character is eaten.
+* Link is inserted.
+* First character of link is unlinked.
+* Pawn appears.
+* Second and further characters inserted will remove the link and insert plain text
+
+See http://cl.ly/3s460Q442L3S
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68590",1403714880,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fxbpehdnotnzwpki3qwo,task_description,resolved
+VisualEditor: [Regression] Pawn appears when inserting a link (no preselected text) and implicitly exiting from the inspector,"No longer an issue (Trevor-rewrite probably), but bug 68590 is a related problem.",1406324569,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fxbpehdnotnzwpki3qwo,task_subcomment,NA
+VisualEditor: [Regression] Pawn appears when inserting a link (no preselected text) and implicitly exiting from the inspector,"(In reply to Krinkle from comment #1)
+> Reduced test case video of only the steps for this bug (without existing
+> links before the list item):
+> 
+> http://cl.ly/2P2h473b2A20
+
+Dead link.
+
+Also, on step 3, my cursor is in the target box... Not the surface. Is this still valid with the window rewrite and everything?",1406322886,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-fxbpehdnotnzwpki3qwo,task_subcomment,NA
+VisualEditor: [Regression] Pawn appears when inserting a link (no preselected text) and implicitly exiting from the inspector,"Reduced test case video of only the steps for this bug (without existing links before the list item):
+
+http://cl.ly/2P2h473b2A20",1403715527,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fxbpehdnotnzwpki3qwo,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"Screenshot-1
+
+Steps to reproduce:
+
+1.Open a page with safari in any iOS device which contains image in it
+2.Now tap on the image to select it
+
+Observed Result:
+The highlight for the image is appearing much below the image 
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65326
+
+**Attached**: {F14511}",1403656560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dzlegd43ozkumznabj4b,task_description,resolved
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,Verified the fix in production,1405023725,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,Verified the fix in test2,1404777720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,Verified the fix in Betalabs.,1404160997,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"The highlight for images appearing in wrong position is now fixed ! :)
+However the tapping on link or image redirecting to the link target or image file page and second tap on reference closing the VE is still there.Therefore, I suppose the following bugs are not related:
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65326
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67002",1403894488,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"Change 142260 merged by jenkins-bot:
+FocusableNode: Use getClientRects()[0] instead of getBoundingClientRect()
+
+https://gerrit.wikimedia.org/r/142260",1403801793,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"Change 142260 had a related patch set uploaded by Esanders:
+Use getClientRects()[0] instead of getBoundingClientRect()
+
+https://gerrit.wikimedia.org/r/142260",1403798307,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,Want to write up a bug report for Apple?,1403791790,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,In every browser except iOS7 getClientRects is relative to the viewport. In iOS7 it is relative to document. Thanks Apple.,1403791536,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS,"Created attachment 15726
+Screenshot-2
+
+**Attached**: {F14512}",1403656610,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dzlegd43ozkumznabj4b,task_subcomment,NA
+VisualEditor: Highlight for multi-line inline template only applies to the first line of it,"It's easiest to understand this from the screenshot.  This is a display bug.
+
+Steps to reproduce:
+
+1.  Open a page containing a (long-ish) citation dialog.
+
+2.  Select the ref and go to Insert > References.
+
+3.  Select the citation template (e.g., to copy it).
+
+4.  Ask yourself, ""Why is only the first line of this template being selected?  Why is the cite tag in the middle instead of underneath the template?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14508}",1403656440,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-o6vqpx64l4l5tkaovklh,task_description,resolved
+VisualEditor: Highlight for multi-line inline template only applies to the first line of it,Works on beta labs.,1403696576,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-o6vqpx64l4l5tkaovklh,task_subcomment,NA
+VisualEditor: Highlight for multi-line inline template only applies to the first line of it,"
+
+*** This bug has been marked as a duplicate of bug 52339 ***",1403696547,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-o6vqpx64l4l5tkaovklh,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","https://www.mediawiki.org/wiki/VisualEditor:Test1234?veaction=edit
+
+Dragging the image on this page on Chrome Version 35.0.1916.153 on Mac OSX 10.9.3 does not relocate the image. The ""shadow"" and magic line appear as expected, but when the click is released the image does not move.
+
+The entire interaction works properly for me on latest Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1403632800,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_description,resolved
+"VisualEditor: On Chrome, new relocatable node does not work",Verified the fix in test2,1403909760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","Change 141949 merged by jenkins-bot:
+Cache block drop position data before setTimeout
+
+https://gerrit.wikimedia.org/r/141949",1403720170,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","Change 141949 had a related patch set uploaded by Esanders:
+Cache block drop position data before setTimeout
+
+https://gerrit.wikimedia.org/r/141949",1403700044,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","Update to my earlier comment. It's working for me on Firefox 30, Mac OSX 10.9.3",1403640324,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work",Works for me in Chrome 34 but broken for me in Firefox 30 (both on Ubuntu 14.04),1403639914,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+"VisualEditor: On Chrome, new relocatable node does not work","**kirkburn** wrote:
+
+https://www.mediawiki.org/wiki/VisualEditor:Test1234?veaction=edit
+
+Similarly, the interaction is not working for me on Chrome 35.0.1916.153 m on Windows 8.1 - I see the shadow and magic line, but nothing happens on mouseup.
+
+However, unlike Trevor, it is also not working for me in pre-release Firefox - on Firefox Aurora 32.0a2 (19-06-14), on Windows 8.1. No effect on mouseup.",1403633991,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6ftf7qwnyyvl5eqcv524,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"**Author:** `jgonera`
+
+**Description:**
+As mentioned in bug 66999 references require two taps on iOS Safari. Often, the first tap results in a lighter ""semi-selection"" appearing a bit below the actual reference. When that happens, second tap on the reference suddenly closes the editor (first video).
+
+The editor doesn't crash though, somehow cancel action is triggered. If you have unsaved changes, you'll see a dialog asking you if you want to abandon the edit (second video).
+
+Tested and recorder in iOS Safari 7.1.1. Does not happen on Chrome for Android.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66999
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65326",1403559480,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_description,resolved
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Verified the fix in production,1405023646,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Verified the fix in test2,1404778996,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Verified the fix in Betalabs,1404160135,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"This seems to got fixed by:
+
+Select highlights on touchend event
+
+https://gerrit.wikimedia.org/r/142839",1404160121,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"Ok, the behavior got slightly changed here, it wont close the VE now if your second tap on the same reference follows right after your first tap
+
+To reproduce it now you need to first tap on a reference say [1], then tap on another reference [2], then go back and tap [1].Now it will close the VE .",1403914344,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"For images, second tap on it opens up the image which might also be the effect of this same bug.",1403895522,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"This bug did not get fixed by :
+
+Use getClientRects()[0] instead of getBoundingClientRect()
+
+https://gerrit.wikimedia.org/r/142260",1403894552,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Probably (?) fixed by the fix to bug 67063.,1403806273,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,Pushing to Ed because it appears to be a shield/highlight issue.,1403573089,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"**jgonera** wrote:
+
+Editor shows confirmation dialog
+
+**Attached**: {F14382}",1403559531,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari,"**jgonera** wrote:
+
+Editor closes
+
+**Attached**: {F14376}",1403559512,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2o3jcx26svgc5z7twzye,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"**Author:** `jgonera`
+
+**Description:**
+Double tap required
+
+If you open VE on mobile and want to edit an existing reference, you need to tap it twice. This is really hard, especially given that the tap target is quite small (which is a separate issue).
+
+Tested and recorder in iOS Safari 7.1.1. Does not happen on Chrome for Android (just a single tap needed there).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65326
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67002
+
+**Attached**: {F14364}",1403558880,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_description,resolved
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Verified the fix in production,1405023590,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Verified the fix in test2,1404779121,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Verified the fix in Betalabs.,1404160006,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"Change 142839 merged by jenkins-bot:
+Select highlights on touchend event
+
+https://gerrit.wikimedia.org/r/142839",1404152414,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"Change 142839 had a related patch set uploaded by Esanders:
+Select highlights on touchend event
+
+https://gerrit.wikimedia.org/r/142839",1403992540,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"This bug did not get resolved by Ed's fix.
+
+The issue here is, the first tap is showing a lighter highlight which is equivalent to the hover effect in the desktop and for the second tap it is actually selecting that node.
+
+This is why, even if you have selected a reference (with two tap) , you can still semi-select another node (with lighter highlight)at the same time  
+
+For mobile, it should require one single tap to select any reference/image etc.",1403895969,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Looks like it's fixed by bug 67063's fix.,1403806238,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"(In reply to Ed Sanders from comment #3)
+> Isn't this fixed then (comment 1)?
+
+… no?
+
+Comment 1 says that the context being useless (""the tap target is quite small"") is  fixed by some other patches and you should ignore.
+
+Comment 0 is mostly about ""If you open VE on mobile and want to edit an existing reference, you need to tap it twice."" which remains a bug.",1403656022,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Isn't this fixed then (comment 1)?,1403624172,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,Pushing to Ed because it appears to be a shield/highlight issue.,1403573091,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor Mobile: References/images require double tap to be selected on iOS Safari,"**jgonera** wrote:
+
+Ignore wrong positioning of mobile context (second toolbar), it's fixed now. To actually see the context though you need those patches:
+https://gerrit.wikimedia.org/r/#/c/141085/
+https://gerrit.wikimedia.org/r/#/c/141087/",1403560673,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rsuk24lv6ttcz4hpew66,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Type a template name with matching suggestion in the text box
+
+Observed Result:
+There are no suggestions for template appearing in the dialog
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14341}",1403548200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rpfc6ad3ojppedslirip,task_description,resolved
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,Verified in production (en.wiki),1404767078,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rpfc6ad3ojppedslirip,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,Verified in test2,1403907204,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rpfc6ad3ojppedslirip,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,This is fixed now.,1403639996,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rpfc6ad3ojppedslirip,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template,*** Bug 66981 has been marked as a duplicate of this bug. ***,1403550337,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rpfc6ad3ojppedslirip,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","1. Edit [[mw:API:Meta]] in VisualEditor
+2. Select the ""MediaWiki version 1.8"" template
+
+A popup appears showing the template's correct name (""MW 1.8"").
+
+3. Open the transclusion editor for the template
+
+VE thinks it is editing a template called ""MW 1"".
+
+Also note that when you try to insert a template with a period in its name, like ""MW 1.8"", you get a whole lot of suggestions for ""MW 1"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403416680,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-tth52wedfhhza5omlooc,task_description,resolved
+"VisualEditor: When editing a template, the title is truncated at first dot (period)",Should be fixed now.,1403827141,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","Change 142372 merged by jenkins-bot:
+Don't remove 'extension' from template names
+
+https://gerrit.wikimedia.org/r/142372",1403826426,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","Change 142372 had a related patch set uploaded by Alex Monk:
+Don't remove 'extension' from template names
+
+https://gerrit.wikimedia.org/r/142372",1403811538,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","Yeah, I worked that out soon after moving the bug.
+
+Still, I wonder if the documentation should be improved for those methods.",1403804486,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","btw, This is a compatibility/legacy left-over from when mw.Title was part of UploadWizard and they got dibs on the more intuitive name ""getNameText"". Unfortunately this mistake was not uncovered until after it was merged in mediawiki-core and released in an LTS.",1403804456,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","getNameText() explicitly leaves out any faux extension. That's by design. To get the page title, use getMainText.
+
+
+https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.Title-method-getNameText",1403804231,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)","Yep.
+
+mw.Title.newFromText( 'Template:Asd.com' ).getNameText()
+""Asd""",1403804143,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+"VisualEditor: When editing a template, the title is truncated at first dot (period)",I blame mwTitle. Because it's always at fault.,1403741920,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tth52wedfhhza5omlooc,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"Until Parsoid removes metadata, large articles are going to consist of several megabytes of data (en:Barack_Obama = 3.4MiB). As browsers doesn't provide any mechanism for compressing post data, this is takes about 20s to upload on a typical 1Mbps up ADSL line.
+
+Using a JS implementation of deflate, we could achieve 80-90% compression in a few hundred ms on a decent machine: http://jsperf.com/js-deflate
+
+A couple of considerations with performing such a complex calculation in pure JS:
+
+* Really bad JS engines or slow devices (old browsers, IE, mobile) may offer to little to overall speed benefit. We may want to detect these cases by user agent or performance profiling.
+* The compression function will be synchronous and lock browser interaction. On slower machines this may give the appearance of crashing, or with memory leaks may actually crash. If this proves to be a significant problem we could look into encoding in chunks of 100k at a time so we could at least provide progress, and maybe improve memory usage (at the cost of overall compression).
+
+--------------------------
+
+**See Also**:
+* {T61659}
+* {T61660}
+* {T66171}",1403358000,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_description,resolved
+VisualEditor: Compress POST data in the client,"Change 141678 merged by jenkins-bot:
+Compress HTML data with deflate before POSTing
+
+https://gerrit.wikimedia.org/r/141678",1404171798,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"(In reply to Ed Sanders from comment #0)
+> * The compression function will be synchronous and lock browser interaction.
+
+You could look at doing it asynchronously in the background, with a Web Worker (i.e. thread) (https://developer.mozilla.org/en-US/docs/Web/API/Worker), in supported browsers (IE 10+, and Firefox/Chrome/Safari/Opera going back pretty far).",1403908962,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,*** Bug 59659 has been marked as a duplicate of this bug. ***,1403735953,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"There are a number of things we can do to avoid this heavy payload:
+* Section editing
+* Separating Parsoid metadata
+* Sending differential linmod data using a server-side converter
+
+None of these are ready or close to being ready yet, and 20s to save a page is fairly significant problem in the present that compression can mitigate.",1403623965,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"Change 141678 had a related patch set uploaded by Esanders:
+Compress HTML data with deflate before POSTing
+
+https://gerrit.wikimedia.org/r/141678",1403614511,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: Compress POST data in the client,"Supporting section editing (bug 48429), and submitting only modified section to the server, might be a better way to increase performance.",1403358178,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-o6lz6v2kc4f7zqt46qrr,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,"Screenshot
+
+Formula icon is missing in the Insert menu
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14131}",1403295660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cn7ribouyrqugmfcsow6,task_description,resolved
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,Verified in production (en.wiki),1404766986,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,Verified in test2,1403907529,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,Works in Betalabs too now.,1403569456,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,"Definitely works in master, must be a deployment issue.",1403352413,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu,Did the registration in the Math extension not work?,1403296660,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cn7ribouyrqugmfcsow6,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image
+3.Open the Media Settings dialog for the image
+4.Go to Advanced Settings tab
+5.Click on ""Make full size""
+
+Observed Result:
+It switches to the Custom tab and keeps the size value as default instead of making it full size.
+
+Environment:Betalabs,test2, en.wiki
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403221860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_description,resolved
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix in production,1405625779,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix in test2,1405036608,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix in Betalabs,1404865261,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 144637 merged by jenkins-bot:
+Apply 'original size' to images
+
+https://gerrit.wikimedia.org/r/144637",1404842132,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 144638 merged by jenkins-bot:
+Apply 'original size' to images and enable apply button in ve-MW
+
+https://gerrit.wikimedia.org/r/144638",1404842120,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 144638 had a related patch set uploaded by Mooeypoo:
+Apply 'original size' to images and enable apply button in ve-MW
+
+https://gerrit.wikimedia.org/r/144638",1404798315,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 144637 had a related patch set uploaded by Mooeypoo:
+Apply 'original size' to images
+
+https://gerrit.wikimedia.org/r/144637",1404798130,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Its changing the size value in the dialog but after clicking on ""Apply Changes"" button it is not making it full size.So, reopening it .",1404764938,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix on test2,1404152879,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Backported to wmf11 and working great.,1404144107,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 142855 merged by jenkins-bot:
+Update VisualEditor to Iba4e6b32
+
+https://gerrit.wikimedia.org/r/142855",1404142302,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 142855 had a related patch set uploaded by Jforrester:
+Update VisualEditor to Iba4e6b32
+
+https://gerrit.wikimedia.org/r/142855",1404001396,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","We need to backport the fix for this one,it did not make it to test2.",1403903163,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images",Verified the fix in betalabs,1403902903,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 142171 merged by jenkins-bot:
+Correctly update full size in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/142171",1403745466,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+"VisualEditor: Clicking on ""Make full size"" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images","Change 142171 had a related patch set uploaded by Mooeypoo:
+Correctly update full size in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/142171",1403743468,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftsn3l6t3sodv3lfszbw,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a cite option/references/formula/image
+
+Observed Result:
+Observe that the,context menus are appearing for these items for a second and then suddenly disappears right after adding
+
+Environment: Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403201760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ssdjpviwo7nog652sz63,task_description,resolved
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified the fix in production (en.wiki),1404767443,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified the fix in test2,1403903577,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified the fix in Betalabs.,1403743096,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified the fix in Betalabs.,1403743096,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,"Change 141940 merged by jenkins-bot:
+Revert ""Accessibility: Restore element focus when a window closes""
+
+https://gerrit.wikimedia.org/r/141940",1403719157,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,"Change 141940 had a related patch set uploaded by Esanders:
+Revert ""Accessibility: Restore element focus when a window closes""
+
+https://gerrit.wikimedia.org/r/141940",1403698053,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,"Updated MW core and it broke, must be an OOJS regression.",1403697005,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image,Verified working in master.,1403696873,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ssdjpviwo7nog652sz63,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"On English Wikipedia, tabbing in the citation dialog is broken.  To reproduce:
+
+1. Edit an article with VE.
+2. Choose 'News' from the Cite menu.
+3. Click the first field.
+4. Tab to try to get to the next field.
+
+Focus goes to a help icon, and even tabbing repeatedly will not get it to leave that icon.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65554",1403155500,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-l57zuo7fpi4s3unocju2,task_description,resolved
+VisualEditor: Fix tabindexes in the citation dialog,*** Bug 67159 has been marked as a duplicate of this bug. ***,1404849994,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,Well that's at least a workaround. I wonder if this might be an upstream bug...,1404152426,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Change 142718 merged by jenkins-bot:
+Set tabindex for template dialog info/remove buttons on parent <div> rather than <a>
+
+https://gerrit.wikimedia.org/r/142718",1404152289,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Change 142718 had a related patch set uploaded by Alex Monk:
+Set tabindex for template dialog info/remove buttons on parent <div> rather than <a>
+
+https://gerrit.wikimedia.org/r/142718",1403902432,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Weird... I can replicate this in Firefox, but not Chrome.
+
+I tried copying the inner HTML out of the dialog iframe and into a separate file - it worked there.
+I also tried moving the tabindex attribute from the <a>s to their parent <div>s... That seems to work. Not sure why.
+
+(I've been testing with any template which has TemplateData, btw - not specifically Cite stuff)",1403902374,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Created attachment 15765
+Tabbing issue in Firefox
+
+I can still reproduce it.  I should have said, I tested in Iceweasel/Firefox 30.0 on Debian Wheezy.
+
+I'm attaching a video.  It shows how I got there, and that it tabs to the help icon.  I tab multiple times and it sticks, though you can't see that in the video.
+
+**Attached**: {F14064}",1403896446,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"Actually:
+
+* in Firefox, the tabbing doesn't take you to the help icon (or delete icon), only in Chrome (instead it takes you to the next field);
+* in neither can you tab to the ""add field"" button;
+* when the add field panel opens your cursor doesn't open in the search field;
+* when in the add field search box tabbing doesn't take you to the field options.
+
+However, yeah, I can't replicate the original report – Matt, can you clarify?",1403218376,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: Fix tabindexes in the citation dialog,"It's supposed to go to the help icon (that was Gerrit change 137152 - bug 65474), but 'tabbing repeatedly will not get it to leave that icon' is WFM",1403199839,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-l57zuo7fpi4s3unocju2,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Attempt to insert a formula or a hiero with the inspectors
+
+Observed Result:
+The math inspector jumps to the beginning of the article then comes back to the right position where it was intended to open
+
+For hiero, it gets stuck at that position.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14045}",1403128380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_description,resolved
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,Verified the fix in production (en.wiki),1404767262,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,Verified in test2,1403906704,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,"Fixed for Math inspector.Will check for Heiro later, when it is available",1403906645,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,Verified the fix in Betalabs,1403742731,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,"Change 141985 merged by jenkins-bot:
+Render a placeholder when extension contents are empty
+
+https://gerrit.wikimedia.org/r/141985",1403732447,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session,"Change 141985 had a related patch set uploaded by Esanders:
+Render a placeholder when extension contents are empty
+
+https://gerrit.wikimedia.org/r/141985",1403712087,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3cn64gzbt6oqm2bmb34,task_subcomment,NA
+VisualEditor: [Regression pre-wmf10] Save fails with fatal error,"as a logged in user on any page in http://en.wikipedia.beta.wmflabs.org/
+
+edit a page and attempt to save.
+
+Save your changes interface shows ""Error: unknown error""
+
+fatal.log shows 
+
+[2014-06-18 16:18:37] Fatal error: Call to a member function getDisplayTitle() on a non-object at /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditorEdit.php on line 120
+Server: deployment-apache01
+Method: POST
+URL: http://en.wikipedia.beta.wmflabs.org/w/api.php
+Cookie: enwiki-gettingStartedUserId=kJSYCjZCvJa3o9xl48ODXiGk1DaduG2m; centralauth_LoggedOut=1402329725; ve-beta-welcome-dialog=1; optin=beta; centralnotice_bucket=0-4.2; edittoolscharsubset=0; GeoIP=US:Tucson:32.2217:-110.9265:v4; uls-previous-languages=%5B%22en%22%5D; mediaWiki.user.sessionId=2vKzOP6dVykMZfazhyIC7OKY5jkC0O3t; enwikiUserID=54; enwikiUserName=Cmcmahon; enwikiSession=29dd771993d2f54b0eb86b9ccc4e85df; centralauth_User=Cmcmahon; centralauth_Session=caf75694c6a3d741ef094fac43c50f47
+Backtrace:
+#0 /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditorEdit.php(120): ApiVisualEditorEdit::execute()
+#1 /srv/common-local/php-master/includes/api/ApiMain.php(908): ApiVisualEditorEdit->execute()
+#2 /srv/common-local/php-master/includes/api/ApiMain.php(363): ApiMain->executeAction()
+#3 /srv/common-local/php-master/includes/api/ApiMain.php(334): ApiMain->executeActionWithErrorHandling()
+#4 /srv/common-local/php-master/api.php(85): ApiMain->execute()
+#5 /srv/common-local/w/api.php(3): require('/srv/common-loc...')
+#6 {main}
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66717",1403108460,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5uojpr32nnknnwpwsv2v,task_description,resolved
+VisualEditor: [Regression pre-wmf10] Save fails with fatal error,"Change 140558 merged by jenkins-bot:
+Revert ""Update displaytitle on save""
+
+https://gerrit.wikimedia.org/r/140558",1403123018,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5uojpr32nnknnwpwsv2v,task_subcomment,NA
+VisualEditor: [Regression pre-wmf10] Save fails with fatal error,"Change 140558 had a related patch set uploaded by Catrope:
+Revert ""Update displaytitle on save""
+
+https://gerrit.wikimedia.org/r/140558",1403122809,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5uojpr32nnknnwpwsv2v,task_subcomment,NA
+VisualEditor Mobile: There's no way to apply heading/etc. paragraph formatting,"There's no way to apply heading styles.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403098140,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-54wl37knbm4fkiq6mgrc,task_description,duplicate
+VisualEditor Mobile: There's no way to apply heading/etc. paragraph formatting,"Yeah, this was intentionally left out of the MVP.",1406600551,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-54wl37knbm4fkiq6mgrc,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE 
+2.Type a text in CE
+3.Select that text
+4.Click on Link inspector icon from the toolbar
+
+Observed Result:
+The link inspector dialog opens but there is no suggestion for link target, also the text selected should appear in the text field inside link inspector, which is not happening as well
+
+Device: Nexus 7(Android 4.4.2)
+Environment:Betalabs
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13913}",1403045460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-citqfhmyoebglw4grn67,task_description,resolved
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Verified the fix in production en.wiki for iOS only, for Android there is a different issue, where the link text is not appearing inside the link inspector,   so cannot follow the exact steps to reproduce to check it there.",1406316076,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Verified the fix in test2 with iOS and Android.,1405725535,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Verified the fix in Betalabs with Android as well,1404335511,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Verified the fix in Betalabs with iOS,1404333288,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Yay deployment.,1404331548,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Possibly a deploy issue.,1404329806,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,Still happening on Betalabs,1404323802,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Change 143524 merged by jenkins-bot:
+Use globalOverlay as the contextOverlay in MobileContext
+
+https://gerrit.wikimedia.org/r/143524",1404260533,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Change 143524 had a related patch set uploaded by Catrope:
+Use globalOverlay as the contextOverlay in MobileContext
+
+https://gerrit.wikimedia.org/r/143524",1404260391,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"Found the steps.
+This happens every second attempt on adding a link where the keyboard gets hidden after adding the first link in CE
+
+So the steps are:
+
+1.Open a page with mobile VE 
+2.Type a text in CE
+3.Select that text
+4.Click on Link inspector icon from the toolbar
+5.Select a suggestion that appears in the dropdown box
+6.After this link gets added successfully, hide the keyboard
+7.Again type a new text and try to add a link to it from the link inspector
+
+Observed Result:
+No link suggestions appear, cannot close the link inspector.",1404170568,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"I am getting this issue intermittently now. Surely the behavior got changed/improved which is why it is not reproducible anymore in a straight forward way.
+
+I will see if I can find any consistent step that ensures this issue to happen.",1404169704,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS,"This is not android specific issue, its happening for iOS as well.
+Also, it has gone to production now.So, the environment is not just Betalabs now :(",1403736136,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-citqfhmyoebglw4grn67,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in Firefox
+2.Go to Insert>Language
+3.Close the language inspector without making any change
+
+Observed Result:
+An error appears in the console:
+TypeError: sel.nativeSelection is null
+
+See the screenshot attached
+
+Environment:test2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13853}",1403030700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_description,resolved
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null",Verified the fix in production,1403901923,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null",Verified the fix in test2,1403303156,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","After re-deployment , it is now fixed :)",1403223776,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Note: doesn't appear in Beta Labs for some reason, but does in production.",1403216138,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Indeed, not working. Sigh.",1403216004,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null",It's still not working on test2.,1403204522,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Actually yes, just a deployment issue.",1403202333,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null",Apparently not. :-(,1403199532,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Change 140426 merged by jenkins-bot:
+Catch rangy exception thrown in FF
+
+https://gerrit.wikimedia.org/r/140426",1403114816,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Change 140426 had a related patch set uploaded by Catrope:
+Catch rangy exception thrown in FF
+
+https://gerrit.wikimedia.org/r/140426",1403114678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Change 140326 merged by jenkins-bot:
+Catch rangy exception thrown in FF
+
+https://gerrit.wikimedia.org/r/140326",1403114345,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+"VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null","Change 140326 had a related patch set uploaded by Esanders:
+Catch rangy exception thrown in FF
+
+https://gerrit.wikimedia.org/r/140326",1403085768,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4odvxcpwxrfuqnmkdos7,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"on https://www.mediawiki.org/wiki/Extension:Gadgets and edit throws following error:
+TypeError: title is null
+https://bits.wikimedia.org/static-1.24wmf9/resources/src/mediawiki/mediawiki.Title.js
+Line 123
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403017560,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_description,resolved
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Change 145055 merged by jenkins-bot:
+MWTemplatePage: Account for template.title being null
+
+https://gerrit.wikimedia.org/r/145055",1405000743,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Change 145055 had a related patch set uploaded by Krinkle:
+MWTemplatePage: Account for template.title being null
+
+https://gerrit.wikimedia.org/r/145055",1404936548,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Yep. It used to throw 
+> Uncaught TypeError: title is null
+
+It now fails earlier because the code changed. Namely on 
+
+> Uncaught TypeError: Cannot read property 'replace' of null",1404935289,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"I wanted to open a new bug, but here is still one :) Actually i become the message:
+Uncaught TypeError: Cannot read property 'replace' of null
+
+fyi :)",1404566086,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"(In reply to Gabriel Wicke from comment #3)
+> Simple test case: {{{{echo|echo}}|foo}}
+> 
+> The Parsoid output looks correct to me.
+
+Thanks!
+
+
+Ed – I guess in these cases we should just detect that it's an invalid title somehow and mark the template as uneditable?",1403140768,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Hmm, actually there is an issue in the Parsoid output for this test case, but it's not likely to be related to this bug.
+
+{{{{echo|echo}}|foo}}
+
+data-mw looks good, but the string 'foo' is missing in the span for some reason.
+
+<span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""{{echo|echo}}""},""params"":{""1"":{""wt"":""foo""}},""i"":0}}]}'></span>
+
+Reported in bug 66820.",1403139914,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Simple test case: {{{{echo|echo}}|foo}}
+
+The Parsoid output looks correct to me.",1403139652,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"(In reply to Ed Sanders from comment #1)
+> Looks like we don't support evaluated template names:
+> {{ {{TNTN:Extension}}
+>   |...
+> }}
+> 
+> Not sure if this a VE or Parsoid problem.
+
+Feels like this template should have been ExpandedAttrs'ed by Parsoid?",1403139279,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+VisualEditor: Template dialog throws error when target is a wikitext expression,"Looks like we don't support evaluated template names:
+{{ {{TNTN:Extension}}
+  |...
+}}
+
+Not sure if this a VE or Parsoid problem.",1403091885,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-d72tlf3bm27wp2zhe5ko,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","VE editable div remains after Save
+
+As a logged in user on beta labs http://en.wikipedia.beta.wmflabs.org/
+
+Edit any page and Save
+
+User can continue to type in the saved page in a VE documentNode div
+
+See screen shot
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66792
+
+**Attached**: {F13826}",1403013420,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_description,declined
+"VisualEditor: Page remains ""editable"" after saving","(In reply to Alex Monk from comment #5)
+> How did you guys reproduce this before the revert (outside of
+> deployment-prep)?
+
+We didn't.",1403132251,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving",How did you guys reproduce this before the revert (outside of deployment-prep)?,1403125095,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","I fixed the server errors, and now I can't reproduce this.",1403124705,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","(In reply to Gerrit Notification Bot from comment #2)
+> Change 140558 had a related patch set uploaded by Catrope:
+> Revert ""Update displaytitle on save""
+> 
+> https://gerrit.wikimedia.org/r/140558
+
+This was unrelated we think.",1403123495,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","Change 140558 had a related patch set uploaded by Catrope:
+Revert ""Update displaytitle on save""
+
+https://gerrit.wikimedia.org/r/140558",1403122804,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: Page remains ""editable"" after saving","Getting server errors on beta, but can't reproduce in master.",1403092625,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jv3ln2ejw5h3wcq3tixs,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in Firefox
+2.Go to Insert>Language
+3.Close the language inspector without making any change
+4.Click on ""Save Page""
+
+Observed Result:
+After step 3 you get the error: TypeError: sel.nativeSelection is null
+After saving there is another error in the console:
+TypeError: this.debugBar is null
+
+If you had categories add on this page, they move to the top of the page
+The context menu for Language Inspector is still open in read mode
+Try to reopen VE , clicking on Edit button, VE does not open.
+
+Environment: test2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13751}",1402957200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_description,resolved
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that",Verified the fix in production(en.wiki),1403299599,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Ignore my last comment, added the comment on wrong bug",1403199681,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that",The backport did not work in test2,1403199544,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that",Verified the fix in Betalabs,1403030047,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","(In reply to ryasmeen from comment #5)
+> Sorry, the language inspector throwing ""TypeError:sel.nativeSelection is
+> null""-
+> this is in both test2 and betalabs,but not the issue with tearing down the
+> debug bar.
+> Initially I thought both of them are related.I am opening a different bug
+> for that one.
+
+OK, thanks.",1403029978,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Sorry, the language inspector throwing ""TypeError:sel.nativeSelection is null""-
+this is in both test2 and betalabs,but not the issue with tearing down the debug bar.
+Initially I thought both of them are related.I am opening a different bug for that one.",1403029902,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that",Are you sure this is a fault for test2? The code this follows up wasn't present for wmf9 unless I'm missing something.,1403028723,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Change 140039 merged by jenkins-bot:
+Followup 00af434: only tear down debug bar if it exists
+
+https://gerrit.wikimedia.org/r/140039",1403025580,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","Change 140039 had a related patch set uploaded by Catrope:
+Followup 00af434: only tear down debug bar if it exists
+
+https://gerrit.wikimedia.org/r/140039",1402959281,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that","The second error: TypeError: this.debugBar is null
+appears after selecting any language from the language selector",1402958330,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ryz7t2wtrhqbokqt3o6s,task_subcomment,NA
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox","Steps to reproduce:
+
+1.Open a pag with VE
+2.Insert a Heiro
+3.While the cursor is at the end of hiero, hit return to go the next line
+
+
+Observed Result:
+Error: Inserted data is trying to close the root node (at index 0) appears and cannot go to the next line
+
+Environment:
+
+Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402956420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5z56coxja6r5rbey633o,task_description,resolved
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox",Looks like it is now.,1412360025,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5z56coxja6r5rbey633o,task_subcomment,NA
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox",This is not yet fixed in Betalabs.,1403202317,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5z56coxja6r5rbey633o,task_subcomment,NA
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox","Change 140345 merged by jenkins-bot:
+Prevent getOffset from return an offset inside a content node
+
+https://gerrit.wikimedia.org/r/140345",1403114249,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5z56coxja6r5rbey633o,task_subcomment,NA
+"VisualEditor: Getting ""Error: Inserted data is trying to close the root node (at index 0)"" while trying to go the next line after inserting a Hiero in Firefox","Change 140345 had a related patch set uploaded by Esanders:
+Prevent getOffset from return an offset inside a content node
+
+https://gerrit.wikimedia.org/r/140345",1403096730,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5z56coxja6r5rbey633o,task_subcomment,NA
+"VisualEditor: Scrolling for &vesection=N works correctly except for N=0, where it scrolls to the bottom of the document","When a page is opened in the wikitext editor with section=0, the top of the page is presented for editing The is the desired and expected behavior:
+
+https://en.wikipedia.org/w/index.php?title=Armadillo&action=edit&section=0
+
+However, VisualEditor does not do this when vesection=0 is opened up for editing. The cursor is placed at the top of the page, but the screen scrolls down to the bottom of the page. The expected behavior is that the scree stay at the top of the window:
+
+https://en.wikipedia.org/w/index.php?title=Armadillo&veaction=edit&vesection=0
+
+This does not occur when using section=0:
+
+https://en.wikipedia.org/w/index.php?title=Armadillo&veaction=edit&section=0
+
+This is particularly important to the Russian Wikipedia, where they regularly use edit&section=0 links and it's easy to wind up with vesection=0.
+
+Here's the report on my ru.wp talk page, with ru.wp links:
+https://ru.wikipedia.org/w/index.php?title=%D0%9E%D0%B1%D1%81%D1%83%D0%B6%D0%B4%D0%B5%D0%BD%D0%B8%D0%B5_%D1%83%D1%87%D0%B0%D1%81%D1%82%D0%BD%D0%B8%D0%BA%D0%B0:Keegan_(WMF)&oldid=prev&diff=63662618
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402939800,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-fyybkik3jnrz25mdbjea,task_description,resolved
+"VisualEditor: Scrolling for &vesection=N works correctly except for N=0, where it scrolls to the bottom of the document","Change 141977 merged by jenkins-bot:
+Don't try to change offset for vesection=0
+
+https://gerrit.wikimedia.org/r/141977",1403715366,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fyybkik3jnrz25mdbjea,task_subcomment,NA
+"VisualEditor: Scrolling for &vesection=N works correctly except for N=0, where it scrolls to the bottom of the document","Change 141977 had a related patch set uploaded by Esanders:
+Don't try to change offset for vesection=0
+
+https://gerrit.wikimedia.org/r/141977",1403710849,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fyybkik3jnrz25mdbjea,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,"On any page at http://en.wikipedia.beta.wmflabs.org/ 
+
+Make an edit
+
+Click Review your changes
+
+User sees a modal dialog saying ""Error loading data from server: error.""
+
+
+fatal log shows
+
+[2014-06-16 14:57:25] Fatal error: Call to a member function get() on a non-object at /srv/common-local/php-master/includes/api/ApiQueryRevisions.php on line 629
+Server: deployment-apache02
+Method: POST
+URL: http://en.wikipedia.beta.wmflabs.org/w/api.php
+Cookie: enwiki-gettingStartedUserId=kJSYCjZCvJa3o9xl48ODXiGk1DaduG2m; centralnotice_bucket=1-4.2; centralauth_LoggedOut=1402329725; ve-beta-welcome-dialog=1; edittoolscharsubset=0; optin=beta; GeoIP=US:Tucson:32.2217:-110.9265:v4; uls-previous-languages=%5B%22en%22%5D; mediaWiki.user.sessionId=y0AhKxKUggdcyUd7KMOLw6Bx8JuBJTqT; enwikiUserID=54; enwikiUserName=Cmcmahon; enwikiSession=090850308740c4e1214d05399aa6d221; centralauth_User=Cmcmahon; centralauth_Session=d47cf247a4d3ea1081576f3520609ffe
+Backtrace:
+#0 /srv/common-local/php-master/includes/api/ApiQueryRevisions.php(629): ApiQueryRevisions::extractRowInfo()
+#1 /srv/common-local/php-master/includes/api/ApiQueryRevisions.php(402): ApiQueryRevisions->extractRowInfo(Object(stdClass))
+#2 /srv/common-local/php-master/includes/api/ApiQuery.php(282): ApiQueryRevisions->execute()
+#3 /srv/common-local/php-master/includes/api/ApiMain.php(908): ApiQuery->execute()
+#4 /srv/common-local/php-master/includes/api/ApiMain.php(332): ApiMain->executeAction()
+#5 /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditor.php(230): ApiMain->execute()
+#6 /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditor.php(501): ApiVisualEditor->diffWikitext(Object(Title), 'Starting a new ...')
+#7 /srv/common-local/php-master/includes/api/ApiMain.php(908): ApiVisualEditor->execute()
+#8 /srv/common-local/php-master/includes/api/ApiMain.php(363): ApiMain->executeAction()
+#9 /srv/common-local/php-master/includes/api/ApiMain.php(334): ApiMain->executeActionWithErrorHandling()
+#10 /srv/common-local/php-master/api.php(85): ApiMain->execute()
+#11 /srv/common-local/w/api.php(3): require('/srv/common-loc...')
+#12 {main}
+[2014-06-16 14:57:25]
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402930860,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-upajxn6r42b5mvgdvg4u,task_description,resolved
+[Regression pre-wmf10] Review your changes throws fatal error,Verified the fix in Betalabs,1402955700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,"Change 139879 merged by jenkins-bot:
+Followup e48ecbc5: fix fatal error due to undefined variable
+
+https://gerrit.wikimedia.org/r/139879",1402944298,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,"Change 139879 had a related patch set uploaded by Catrope:
+Followup e48ecbc5: fix fatal error due to undefined variable
+
+https://gerrit.wikimedia.org/r/139879",1402943560,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,*** Bug 66681 has been marked as a duplicate of this bug. ***,1402943552,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,I am seeing this error modal dialog also intermittently on test2wiki (and presumably mediawiki.org) when switching modes from VE to wikitext editor.,1402941380,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+[Regression pre-wmf10] Review your changes throws fatal error,"
+Note: saving changes works correctly",1402930897,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-upajxn6r42b5mvgdvg4u,task_subcomment,NA
+VisualEditor: Keyboard events not detected after selecting a focusable node with the mouse,"1. Click on an image
+2. Press delete
+
+Nothing happens
+
+Contrast with focussing an image by keyboard navigation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402836420,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3xmwgu22clys4qnwhvfj,task_description,resolved
+VisualEditor: Keyboard events not detected after selecting a focusable node with the mouse,"Change 139679 merged by jenkins-bot:
+Defer focusableNode selection fix until after native selection change
+
+https://gerrit.wikimedia.org/r/139679",1403054361,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3xmwgu22clys4qnwhvfj,task_subcomment,NA
+VisualEditor: Keyboard events not detected after selecting a focusable node with the mouse,"Change 139679 had a related patch set uploaded by Esanders:
+Defer focusableNode selection fix until after native selection change
+
+https://gerrit.wikimedia.org/r/139679",1402836725,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3xmwgu22clys4qnwhvfj,task_subcomment,NA
+VisualEditor: Image CE HTML should match Parsoid,"When converting between block and inline images we hide the <figcaption> with CSS instead of removing it from the DOM tree. We need to preserve the caption in case the user converts from inline back to block, but this can be done in the model.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402736640,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g6ern4m4ctxikpozgnha,task_description,resolved
+VisualEditor: Image CE HTML should match Parsoid,"Current Parsoid HTML:
+
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb"" data-parsoid=""…"">
+	<a href=""./File:Smokeycover.jpg"" data-parsoid=""…"">
+		<img resource=""./File:Smokeycover.jpg"" src=""//upload.wikimedia.org/wikipedia/en/thumb/7/73/Smokeycover.jpg/170px-Smokeycover.jpg"" height=""237"" width=""170"" data-parsoid=""…"">
+	</a>
+	<figcaption data-parsoid=""…"">
+		<a rel=""mw:WikiLink"" href=""./Smokey_Stover"" title=""Smokey Stover"" data-parsoid=""…"">Smokey Stover</a><!-- no italics, character’s name --> driving a ""foomobile"", with <i data-parsoid=""…"">phoo</i> visible on the front
+	</figcaption>
+</figure>
+
+
+Current VE HTML:
+
+<figure class=""ve-ce-mwBlockImageNode ve-ce-mwBlockImageNode-type-thumb mw-default-size ve-ce-branchNode ve-ce-mwBlockImageNode-borderwrap mw-halign-right ve-ce-focusableNode"" typeof=""mw:Image/Thumb"" contenteditable=""false"" style=""width: 172px; height: auto;"">
+	<a class=""image"" href=""https://en.wikipedia.org/wiki/File:Smokeycover.jpg"">
+		<img src=""//upload.wikimedia.org/wikipedia/en/thumb/7/73/Smokeycover.jpg/170px-Smokeycover.jpg"" class=""ve-ce-mwBlockImageNode-thumbimage"" style=""width: 170px; height: 237px;"">
+	</a>
+	<figcaption class=""ve-ce-branchNode"">
+		<div class=""magnify""><a class=""internal""></a></div>
+		<p class=""ve-ce-paragraphNode ve-ce-generated-wrapper ve-ce-branchNode"">
+			<a class=""ve-ce-linkAnnotation ve-ce-mwInternalLinkAnnotation new"" href=""http://en.wikipedia.beta.wmflabs.org/wiki/Smokey%20Stover"" title=""Smokey Stover"">Smokey Stover</a><span class=""ve-ce-leafNode ve-ce-commentNode oo-ui-indicatedElement-indicator oo-ui-indicator-alert oo-ui-indicatedElement ve-ce-focusableNode"" contenteditable=""false""> </span>&nbsp;driving a ""foomobile"", with <i class=""ve-ce-textStyleAnnotation ve-ce-italicAnnotation"">phoo</i> visible on the front
+		</p>
+	</figcaption>
+</figure>
+
+The only structural difference is the ""<div class=""magnify""><a class=""internal""></a></div>"" which Parsoid is missing (and will go away soon enough anyway). Deeming this to be fixed.",1409254775,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g6ern4m4ctxikpozgnha,task_subcomment,NA
+VisualEditor: Image CE HTML should match Parsoid,What's left to do here?,1408662539,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g6ern4m4ctxikpozgnha,task_subcomment,NA
+VisualEditor: Image CE HTML should match Parsoid,"Discussion from Gerrit:
+
+Mooeypoo		Jun 13 8:25 PM
+
+<figcaption> isn't destroyed and/or is recreated each time an image type changes, so it has to be hidden for the block image types that don't support it, like frameless and basic.
+But yes, it could be added to the CSS instead, hiding the figcaption for the block image types that don't support it. 
+I'm not sure it should be generalized for Parsoid's use, though, since the Parsoid output for the figcaption is always correct (so, no caption for images that don't support it). We keep the caption in VE to let the user be able to change the images back and forth and retain the information in the caption even if the type changed.
+
+Esanders		Jun 13 8:29 PM
+
+If it's not supposed to be in the tree when it's not in use, why don't we destroy it completely and recreate it when it's needed again?
+
+Mooeypoo		Jun 13 8:40 PM
+
+Because the caption information is taken from <figcaption> and we want to retain it for (A) if the user regrets their type choice and edits again to another type that supports the caption (make sure that the caption isn't lost) and (B) so it won't be removed from the wikitext.
+There's a tech debt to fix the way caption works in general, especially in light of VE allowing the switch from block to inline and the existence of alternate text (which gets the value of the caption if it exists) but right now it's on hold for a little bit waiting for the new Media Edit dialog redesign.
+
+Esanders		Jun 13 8:43 PM
+
+If we need to preserve the caption that should be done in the model, not the view.
+
+Mooeypoo		Jun 13 8:48 PM
+
+Yes, and it also must be preserved in wikitext, so the <figcaption> must be sent to parsoid in certain cases. And the caption surface in the editor should be selectively disabled and enabled, and exchange its information with the alt-text in a way that the user understands where and why things are replaced.
+Hence the tech debt.
+
+GWicke		Jun 13 9:36 PM
+
+Also see https://gerrit.wikimedia.org/r/#/c/139473/. There should be no need to manually hide the caption with inline CSS. Inline images have no caption in the DOM, as that can for example break a surrounding paragraph in case the caption contains a paragraph.",1402736738,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g6ern4m4ctxikpozgnha,task_subcomment,NA
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,"* Move your cursor anywhere in the document, don't select anything.
+* Open the link inspector
+* Set target anywhere
+* Click back to document in the same position
+* Press any key
+* New character is shown, but is highlighted. If you undo and then redo, a pawn character appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68590",1402600500,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-e754krtqrkmtvi55a5wr,task_description,resolved
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,"Yeah, I'm going to declare this one also fixed in the re-write. The block slug issue is… interesting, and may deserve its own bug, but I'll comment on bug 68590.",1406324798,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e754krtqrkmtvi55a5wr,task_subcomment,NA
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,"Doesn't seem to happen anymore. Although we do now have bug 68590, which is pretty much these same steps but with another undo instead of redo at the end. Not sure about Roan's comment.",1406323339,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-e754krtqrkmtvi55a5wr,task_subcomment,NA
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,Sometimes I've managed to get this to create a pawn character at the same time as making the highlighted text. Appears to be to do with the target text.,1402600750,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-e754krtqrkmtvi55a5wr,task_subcomment,NA
+VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link,"Additionally, if you put your cursor in a block slug, open the link inspector in creation mode, and click back into the surface in the same place, the link inspector doesn't close. Then when you start typing, the same behavior as in comment 0 appears.",1402600664,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-e754krtqrkmtvi55a5wr,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"After a fresh installation of MW 1.23 (from the tarball), adding VisualEditor and configuring parsoid, the ""Edit"" (or ""Create"") link of any page is not working.
+
+I am not the only one having this problem: https://www.mediawiki.org/wiki/Extension_talk:VisualEditor#Can_not_get_VisualEditor_extension_for_MediaWiki_REL1_23_working_on_freshly_installed_system_44018
+
+What I saw when I checked with FireBug:
+* In an old (1.22) installation clicking ""Edit"" results in a POST-request with action=visualeditor&paction=parse&page=Main_Page&format=json as its content.
+* In the new installation no request is visible in FireBug when clicking on ""Edit"".
+
+One more finding: It seems to work in 1.23alpha. I used wikiapiary to search for sites using VisualEditor and found e.g. this one: http://techwiki.umbel.org/index.php/Special:Version where it works...
+
+Some more investigation:
+using the Poster-extension of Firefox to manually POST 
+""action=visualeditor&paction=parse&page=Main_Page&format=json"" (application/x-www-form-urlencoded) to .../api.php
+returns good looking content of type ""application/json; charset=utf-8"" (see attachment ""visualeditor_postresponse.json"").
+
+But the JS-compoments of VisualEditor are not displaying anything!
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402562460,PHID-USER-3x5zfm7iedaghxnnelco,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_description,resolved
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"(In reply to Tony Mach from comment #10)
+> Ok, VisualEditor is now running on my system!
+> 
+> And I found the problem:
+> 
+> If you download the VisualEditor via the web-interface at
+> http://git.wikimedia.org/branches/mediawiki%2Fextensions%2FVisualEditor.git
+> then you will *NOT* get any submodules, like e.g. lib/ve/. 
+> 
+> The problem is, that web-interface for git at git.wikimedia.org can not
+> handle git submodules. If you download an archive of VisualEditor (e.g.
+> REL1_23) then lib/ve will be missing. If you try to access a submodule like
+> lib/ve, then the web-interface will give you an error message.
+> 
+> If you download VisualEditor via
+> https://www.mediawiki.org/wiki/Special:ExtensionDistributor/VisualEditor
+> then everything is fine.
+> 
+> If you manually download VisualEditor via git commandline, and do a ""git
+> submodule update --init"" afterwards, then everything is fine.
+
+Yeah, the instructions say this pretty clearly, though I see you've now gone rather over-board in saying this several times in big boxes. :-)
+
+> What is really annoying was the lack or error-messages.
+
+Yeah; we should raise an issue with MediaWiki core about the lack of user-visible errors, though gerrit 155177 will at least make it more obvious for VisualEditor users in future.",1408636513,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"**bugzilla.wikimedia.org** wrote:
+
+Ok, VisualEditor is now running on my system!
+
+And I found the problem:
+
+If you download the VisualEditor via the web-interface at http://git.wikimedia.org/branches/mediawiki%2Fextensions%2FVisualEditor.git then you will *NOT* get any submodules, like e.g. lib/ve/. 
+
+The problem is, that web-interface for git at git.wikimedia.org can not handle git submodules. If you download an archive of VisualEditor (e.g. REL1_23) then lib/ve will be missing. If you try to access a submodule like lib/ve, then the web-interface will give you an error message.
+
+If you download VisualEditor via https://www.mediawiki.org/wiki/Special:ExtensionDistributor/VisualEditor then everything is fine.
+
+If you manually download VisualEditor via git commandline, and do a ""git submodule update --init"" afterwards, then everything is fine.
+
+What is really annoying was the lack or error-messages.",1408621745,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,Please explain how you installed VE and its dependencies and which exact guide you followed; might be better to ask/discuss on IRC in #mediawiki-visualeditor or https://www.mediawiki.org/wiki/Talk:VisualEditor or https://www.mediawiki.org/wiki/Extension_talk:VisualEditor,1408620475,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"**bugzilla.wikimedia.org** wrote:
+
+D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/ is missing on my system!!! There is only jquery.uls ...
+
+Where do I get the ve lib? Why don't I have the ve lib?",1408616873,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"**bugzilla.wikimedia.org** wrote:
+
+Oh, one more thing I just found, when I manually do the GET /mediawiki/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cmediawiki%2CviewPageTarget%7Cext.visualEditor.core.desktop%7Cjquery.visibleText%7Cmediawiki.api.edit%7Cmediawiki.feedback%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20140820T142325Z&* then I get the following (snipped at the end):
+
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/modules/ve/ve.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/modules/ve/ve.Range.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/modules/ve/ui/ve.ui.DesktopSurface.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/lib/jquery/jquery.visibleText.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/lib/rangy/rangy-core-1.3.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+/*
+exception 'MWException' with message 'ResourceLoaderFileModule::readScriptFiles: script file not found: ""D:\xampp\apps\mediawiki\htdocs\extensions\VisualEditor/lib/ve/modules/unicodejs/unicodejs.js""' in D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php:658
+Stack trace:
+#0 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoaderFileModule.php(277): ResourceLoaderFileModule->readScriptFiles(Array)
+#1 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(797): ResourceLoaderFileModule->getScript(Object(ResourceLoaderContext))
+#2 D:\xampp\apps\mediawiki\htdocs\includes\resourceloader\ResourceLoader.php(546): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)
+#3 D:\xampp\apps\mediawiki\htdocs\load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))
+#4 {main}
+*/
+mw.loader.implement(""ext.visualEditor.mediawiki"",function($,jQuery){ve.init.mw={'targets':[]};(function() ...",1408616570,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"**bugzilla.wikimedia.org** wrote:
+
+I have a similar (same?) problem: VisualEditor does not load when clicking on the ""edit"" tab.
+
+This is the setup I use:
+
+- Windows 7
+- XAMPP win32-1.8.3-4-VC11
+- MediaWiki (tried both REL1_23 and 1.24wmf17)
+- VisualEditor (tried 1.23wmf22, 1.23wmf21, 1.24wmf17)
+
+I tried it both with Firefox 31 and Google Chrome 36 - in both, the VisualEditor does not load from my server. (VisualEditor loads fine for example from wikimedia.org in both browsers)
+
+I think my Parsoid is running fine. When I access port 8000, I get access to my parsoid installation, and it seems to parse html and wikicode just fine.
+
+I tried using VisualEditor-refs_heads_wmf_1.23wmf22 and VisualEditor-refs_heads_wmf_1.23wmf21 - no change, VisualEditor does not load.
+
+I tried using Mediawiki core-refs_heads_wmf_1.24wmf17 with VisualEditor refs_heads_wmf_1.24wmf17 - no change, VisualEditor does not load.
+
+I do not get any error message. The access log does not show much. 
+
+Loading the main page:
+127.0.0.1 - - [21/Aug/2014:12:11:24 +0200] ""GET /mediawiki/index.php/Main_Page HTTP/1.1"" 304 - ""-"" ""Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0""
+
+127.0.0.1 - - [21/Aug/2014:12:11:25 +0200] ""GET /mediawiki/load.php?debug=false&lang=en&modules=ext.visualEditor.viewPageTarget.noscript%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles&only=styles&skin=vector&* HTTP/1.1"" 304 - ""http://127.0.0.1/mediawiki/index.php/Main_Page"" ""Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0""
+
+127.0.0.1 - - [21/Aug/2014:12:11:25 +0200] ""GET /mediawiki/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&* HTTP/1.1"" 304 - ""http://127.0.0.1/mediawiki/index.php/Main_Page"" ""Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0""
+
+Then pressing on the edit tab:
+
+127.0.0.1 - - [21/Aug/2014:12:12:19 +0200] ""GET /mediawiki/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cmediawiki%2CviewPageTarget%7Cext.visualEditor.core.desktop%7Cjquery.visibleText%7Cmediawiki.api.edit%7Cmediawiki.feedback%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20140820T142325Z&* HTTP/1.1"" 304 - ""http://127.0.0.1/mediawiki/index.php/Main_Page"" ""Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0""
+
+Are there any debug-output, logfiles, or something like that I can access or activate? I have no idea why VisualEditor does not load, and I do not know where to look. Can this be a firewall problem? Has anybody any idea?",1408616164,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"I've updated REL1_23 to just simply use 1.23wmf22 instead, which should fix the incompatibility. Sorry about this.",1403633787,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"Relevant commits that were in wmf/1.23wmf22 but not in REL1_23 yet:
+
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/compare/REL1_23...wmf/1.23wmf22
+
+https://github.com/wikimedia/VisualEditor/compare/55a5cdc047...b3e5759654
+
+I reckon one or more of those should be backported.",1403603952,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"Hello Kevin,
+
+thank you for the confirmation and the additional information!
+
+Switching to the git-Version of VisualEditor and using branch wmf/1.23wmf22 did indeed make it work for me as well!
+
+But I do not want to use this work-around in a production environment without anyone in the know confirming it's the way to go...",1403602007,PHID-USER-3x5zfm7iedaghxnnelco,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"I can confirm this bug.  It is throwing the following JS exception:
+
+Exception thrown by ext.visualEditor.core
+Error: constructor must be a function, cannot be a undefined
+
+The exception gets throwing trying to call:
+
+ve.ui.windowFactory.register( OO.ui.ConfirmationDialog );
+
+From line 22 of lib/modules/ve/ui/ve.ui.js
+
+The problem goes away if I switch from branch REL1_23 to wmf/1.23wmf22 (and run git submodule update).",1403568663,PHID-USER-5yr7uedvkbhzdccm6hy2,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23,"Created attachment 15635
+Response of POST to api.php
+
+**Attached**: {F13953}",1402562535,PHID-USER-3x5zfm7iedaghxnnelco,False,PHID-TASK-bmc4xfzmfvvqjrrocbcd,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"Right now they're not, which is irritating when I'm writing about how VE supports the functionality. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402552140,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_description,resolved
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"Change 140194 merged by jenkins-bot:
+(Bug 66514) Fix bug in nowiki-escaping of magic words
+
+https://gerrit.wikimedia.org/r/140194",1403212063,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"Change 140194 had a related patch set uploaded by Subramanya Sastry:
+(Bug 66514) Fix bug in nowiki-escaping of magic words
+
+https://gerrit.wikimedia.org/r/140194",1403035222,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"[subbu@earth lib] echo ""Fails when not in <b>sol context</b> __TOC__"" | node parse --html2wt --trace wt-escape
+[wt-esc]       | EWT: ""Fails when not in ""
+[wt-esc]       | ---No-checks needed---
+[wt-esc]       | EWT: ""sol context""
+[wt-esc]       | ---No-checks needed---
+[wt-esc]       | EWT: "" __TOC__""
+[wt-esc]       | SOL: false "" __TOC__""
+[wt-esc]       | ---Not-SOL and safe---
+Fails when not in '''sol context''' __TOC__
+[subbu@earth lib] echo ""Works when node is in sol context __TOC__"" | node parse --html2wt --trace wt-escape
+[wt-esc]       | EWT: ""Works when node is in sol context __TOC__""
+[wt-esc]       | SOL: true ""Works when node is in sol context __TOC__""
+[wt-esc]       | nl: true :text= ""Works when node is in sol context __TOC__""
+[wt-esc]       | T: ""Works when node is in sol context ""
+[wt-esc]       | T: {""type"":""SelfclosingTagTk"",""name"":""behavior-switch"",""attribs"":[{""k"":""word"",""v"":""__TOC__""}],""dataAttribs"":{""tsr"":[34,41],""src"":""__TOC__""}}
+[wt-esc]       | ---Found WT tokens---
+Works when node is in sol context <nowiki>__TOC__</nowiki>",1403029746,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"[subbu@earth lib] echo ""<b>__TOC__</b>"" | node parse --html2wt
+'''__TOC__'''
+[subbu@earth lib] echo ""<foobar>__DISAMBIG__</foobar>"" | node parse --html2wt
+<foobar>__DISAMBIG__</foobar>",1403029498,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"See e.g. https://www.mediawiki.org/w/index.php?title=VisualEditor/status&diff=prev&oldid=1034135 for an insertion without <nowiki>s, or https://www.mediawiki.org/w/index.php?title=VisualEditor:Bug_66514&oldid=1039124 for a more minimal test.
+
+The problem appears to be that <code>__Foo__</code> stops __Foo__ being recognised.",1403029182,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context,"See https://en.wikipedia.org/w/index.php?title=User%3ASsastry%2FVE_Test&diff=613314757&oldid=584723202
+
+and also this:
+
+[subbu@earth lib] echo ""This is a test of __DISAMBIG__ getting nowikied"" | node parse --html2wt
+This is a test of <nowiki>__DISAMBIG__</nowiki> getting nowikied",1403028853,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rwxrle7xnhmz63ujcqjc,task_subcomment,NA
+VisualEditor: Work out whether removing repositionOnly parameter in DesktopContext.update() was a good idea,"It's unused now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402532640,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fk7j2az3j3ks52n4wvg5,task_description,resolved
+VisualEditor: Work out whether removing repositionOnly parameter in DesktopContext.update() was a good idea,Done in gerrit 141089.,1405375988,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fk7j2az3j3ks52n4wvg5,task_subcomment,NA
+VisualEditor: Work out whether removing repositionOnly parameter in DesktopContext.update() was a good idea,Fair point. Whoops. :-) Relabelling.,1402533549,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fk7j2az3j3ks52n4wvg5,task_subcomment,NA
+VisualEditor: Work out whether removing repositionOnly parameter in DesktopContext.update() was a good idea,"We still need to 1) get Trevor to look at whether it actually needs to die and 2) update callers, including ones which pass the parameter through",1402533498,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fk7j2az3j3ks52n4wvg5,task_subcomment,NA
+VisualEditor: Swapping an existing reference scrolls viewport to top,"* Create two references, one above the fold and one below
+* Scroll down to the one below the fold, inspect it, and use the ""Use existing reference"" feature to swap it out for the first one
+* The page is now scrolled to the top
+
+I think this might be because we delete and reinsert the reference?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65882",1402442100,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qwu6tsfyuvic4ungwofd,task_description,resolved
+VisualEditor: Swapping an existing reference scrolls viewport to top,Verified the fix in test2 and Betalabs.,1403557211,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qwu6tsfyuvic4ungwofd,task_subcomment,NA
+VisualEditor: Swapping an existing reference scrolls viewport to top,It is indeed fixed. Thanks Ed!,1403060858,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qwu6tsfyuvic4ungwofd,task_subcomment,NA
+VisualEditor: Swapping an existing reference scrolls viewport to top,May have been fixed by https://gerrit.wikimedia.org/r/#/c/138833/ ?,1402829459,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qwu6tsfyuvic4ungwofd,task_subcomment,NA
+VisualEditor: GeneratedContentNode rerenders with double-escaped HTML entities,"* Create a page with <syntaxhighlight lang=""javascript"">foo && bar</syntaxhighlight>
+* Open the page in VE
+* Inspect the syntaxhighlight block and change bar to baz
+* Observe &amp;&amp; instead of && in the preview
+
+Saving the change doesn't double-encode the ampersands though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402436820,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-riqtlu6jga2olfkc3ozl,task_description,resolved
+VisualEditor: GeneratedContentNode rerenders with double-escaped HTML entities,"
+
+*** This bug has been marked as a duplicate of bug 60332 ***",1404435630,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-riqtlu6jga2olfkc3ozl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in VE with Firefox
+2.Add a link or reference
+3.Select the node
+4.When the context menu appears, hover over it
+
+Observed Result:
+Its not highlighting the entire context menu, but some part of it
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13767}",1402426980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7nid5fuef63kkolvi3n,task_description,resolved
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,Verified the fix in production (en.wiki),1403300850,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7nid5fuef63kkolvi3n,task_subcomment,NA
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,Verified the fix in test2 running wmf9,1402696734,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7nid5fuef63kkolvi3n,task_subcomment,NA
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,Verified the fix in Betalabs,1402595959,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7nid5fuef63kkolvi3n,task_subcomment,NA
+VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu,Fixed by gerrit 138906.,1402527451,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-w7nid5fuef63kkolvi3n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"QUnit is complaining whenever I try and +2 code and it is preventing merges from happened e.g. https://gerrit.wikimedia.org/r/#/c/138375/ https://integration.wikimedia.org/ci/job/mwext-MobileFrontend-qunit/6228/console
+
+After talking to Antoine we think it might be a side effect of the warnings produced by: https://gerrit.wikimedia.org/r/#/c/135429/
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402417680,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_description,resolved
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138682 merged by jenkins-bot:
+Revert ""Revert ""Officially deprecate skin autodiscovery""""
+
+https://gerrit.wikimedia.org/r/138682",1402880758,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138648 merged by Krinkle:
+defaults: Make values for 'wipe-workspace' and 'clean' explicit
+
+https://gerrit.wikimedia.org/r/138648",1402493269,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138682 had a related patch set uploaded by Bartosz Dziewoński:
+Revert ""Revert ""Officially deprecate skin autodiscovery""""
+
+https://gerrit.wikimedia.org/r/138682",1402432729,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),Thank you!,1402432689,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Confirmed fix by seeing that old files in skins/* are gone in workspaces on gallium, and confirmed again by touching a file `krinkle.txt` and confirming it was gone the next build.",1402427639,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138657 merged by jenkins-bot:
+mw-core-get: Clean workspace first
+
+https://gerrit.wikimedia.org/r/138657",1402426240,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138657 had a related patch set uploaded by Krinkle:
+mw-core-get: Clean workspace first
+
+https://gerrit.wikimedia.org/r/138657",1402425832,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138648 had a related patch set uploaded by Krinkle:
+defaults: Make values for 'wipe-workspace' and 'clean' explicit
+
+https://gerrit.wikimedia.org/r/138648",1402423802,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"(In reply to Krinkle from comment #7)
+> Taking mwext-VisualEditor-qunit as a usecase there's a couple facts:
+> 
+> 1) As being a repo not having the target git repo (VE) at its root, it has
+> git:clean:false and git:wipe:true (defaults), see 'use-zuul-for-mw-ext' in
+> jenkins-job-builder-config and confirmed on
+> https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/configure
+> (expand the Advanced sections)
+> 
+> * [ ] Clean after checkout [_]
+>       (runs `git clean`)
+> * [x] Wipe out workspace before build
+> 
+> 
+> 2) Looking at an example build:
+>   
+> https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/10021/
+> consoleFull
+>    - Wiping out workspace first.
+>    - Cloning repository
+> git://zuul.eqiad.wmnet/mediawiki/extensions/VisualEditor
+>    - /srv/deployment/integration/slave-scripts/bin/mw-core-get.sh master
+> 
+>    In that order.
+> 
+> 3) Even if this wouldn't happen, I think it's fine to use full wipe instead
+> of git-clean since all these run on the local system and should be able to
+> use hardlinks during the cloning (for the extension repo), and for mwcore we
+> use archive from a central repo /srv/ssd/gerrit/mediawiki/core.git so its'
+> fine to wipe the workspace of the extension repo)
+> 
+> 4) Confirmed by running mkdir ~/test; export WORKSPACE=~/test;
+> /srv/ssd/gerrit/mediawiki/core.git master; that the central git repo is not
+> dirty, the old files and skin directories are not in there.
+> 
+> 
+> So then why do we have RELEASE-NOTES-1.22 and skins/Modern.php in
+> mwext-VisualEditor-qunit workspace still?
+
+
+Looks like the real underlying bug is that the 'non-git' wipe option we have (the one that fully removes the work tree and will require a new git-clone on each build, the option we actually *are* using for extensions jobs) that wipe option (not git-clean) still restricts itself to where the git-clone will be. It doesn't wipe the workspace, it wipes workspace/{basedir}.",1402423463,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),Let's get this issue fixed now so we can work towards merging Bartosz's patch again.,1402422859,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138626 merged by jenkins-bot:
+Revert ""Officially deprecate skin autodiscovery""
+
+https://gerrit.wikimedia.org/r/138626",1402421790,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),I went ahead and merged Jon's revert so that mobile and VE development are not blocked.,1402421764,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Rephrasing bug summary. For the record, this only affects files that have actually landed in master. We do clean out files from proposed patches properly, this bug is specifically due to and related to fetching of latest master within extensions.",1402421541,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Taking mwext-VisualEditor-qunit as a usecase there's a couple facts:
+
+1) As being a repo not having the target git repo (VE) at its root, it has git:clean:false and git:wipe:true (defaults), see 'use-zuul-for-mw-ext' in jenkins-job-builder-config and confirmed on https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/configure (expand the Advanced sections)
+
+* [ ] Clean after checkout [_]
+      (runs `git clean`)
+* [x] Wipe out workspace before build
+
+
+2) Looking at an example build:
+   https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/10021/consoleFull
+   - Wiping out workspace first.
+   - Cloning repository git://zuul.eqiad.wmnet/mediawiki/extensions/VisualEditor
+   - /srv/deployment/integration/slave-scripts/bin/mw-core-get.sh master
+
+   In that order.
+
+3) Even if this wouldn't happen, I think it's fine to use full wipe instead of git-clean since all these run on the local system and should be able to use hardlinks during the cloning (for the extension repo), and for mwcore we use archive from a central repo /srv/ssd/gerrit/mediawiki/core.git so its' fine to wipe the workspace of the extension repo)
+
+4) Confirmed by running mkdir ~/test; export WORKSPACE=~/test; /srv/ssd/gerrit/mediawiki/core.git master; that the central git repo is not dirty, the old files and skin directories are not in there.
+
+
+So then why do we have RELEASE-NOTES-1.22 and skins/Modern.php in mwext-VisualEditor-qunit workspace still?",1402421458,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),Sorry Kunal :-(  And you have no idea how much it piss me off to have to revert such a patch from core :-(,1402419275,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"(In reply to Antoine ""hashar"" Musso from comment #2)
+> The reason is that since mediawiki/core.git is so huge to clone, we are
+> using git archive to grab a snapshot of MediaWiki in the Jenkins job
+> workspace.  A side effect is that files removed from the repository are not
+> removed from the workspace.
+
+Uck :/
+
+(In reply to Antoine ""hashar"" Musso from comment #4)
+> We could clean up the /skins/ directory in all workspaces potentially, but I
+> can't remember whether the same job could use a REL1_*** codebase which
+> would bring back the skins.
+
+Lets do that for now. People shouldn't be backporting stuff to REL branches in the near future, which gives us a little more time to fix jenkins to delete files properly.",1402419039,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"We could clean up the /skins/ directory in all workspaces potentially, but I can't remember whether the same job could use a REL1_*** codebase which would bring back the skins.",1402418671,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"Change 138626 had a related patch set uploaded by Hashar:
+Revert ""Officially deprecate skin autodiscovery""
+
+https://gerrit.wikimedia.org/r/138626",1402418534,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"https://gerrit.wikimedia.org/r/#/c/135429/ added a warning message whenever an old skin is found under Mediawiki /skins/ . The skins have been removed from core but are still present in Jenkins workspace.
+
+The reason is that since mediawiki/core.git is so huge to clone, we are using git archive to grab a snapshot of MediaWiki in the Jenkins job workspace.  A side effect is that files removed from the repository are not removed from the workspace.
+
+
+A potential way to solve it would be to have mediawiki core in a dedicated directory which we would be able to delete recursively before taking a snapshot with git archive.  From there we could symlink extensions from their dedicated directories under mediawiki /extensions/ .
+
+I also have an ongoing project to clone multiple repositories which might let us solve the issue.
+
+Meanwhile my recommendation is to revert the deprecation patch ( https://gerrit.wikimedia.org/r/#/c/135429/ ) until CI has catched up and ensure MediaWiki code base is clean in the Jenkins workspaces.",1402418470,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist),"(In reply to Jon from comment #0)
+
+> https://integration.wikimedia.org/ci/job/mwext-MobileFrontend-qunit/6228/
+
+Since Modern is no longer in core, why is it in the skins directory?",1402418375,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-fzzyk5pyf5z3b4bz7k2n,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page","I have been getting this issue since this morning, I think this has something to do with changing image size when the size of an image gets adjusted or changed.
+I do not have the exact steps to reproduce for now.But it happened this one time when I changed the thumbnail left aligned image to centre float.
+
+This is the page where you will see the image on which I made the change and getting the edit conflict error :
+http://en.wikipedia.beta.wmflabs.org/wiki/9thjunechrome?veaction=edit
+
+We had encountered similar kind of issue quiet a while ago, which was fixed:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62172
+
+I am not sure, if the same cause is behind the bug or not
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402357800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2kxlh36d7ae4apn7vxff,task_description,resolved
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page",Verified the fix in production (en.wiki),1403300322,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page",Verified the fix in test2 running wmf 9,1402703931,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page",Verified the fix in Betalabs,1402424943,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page","Change 138521 merged by jenkins-bot:
+Followup bd49f97: prevent MWExtensionNodes from having children
+
+https://gerrit.wikimedia.org/r/138521",1402362445,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page","Change 138521 had a related patch set uploaded by Catrope:
+Followup bd49f97: prevent MWExtensionNodes from having children
+
+https://gerrit.wikimedia.org/r/138521",1402362192,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+"VisualEditor:Getting  ""Your edit may have been corrupted – please review before saving"" message while making changes to an image in the page","There is a very weird issue, probably introduced by Ed's extension nodes rewrite. Any extension node's children get duplicated on the way back to Parsoid: a hieroglyphs <table> gets two <tbody>s, a gallery <ul> contains all of its <li>s twice, etc.",1402361189,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2kxlh36d7ae4apn7vxff,task_subcomment,NA
+ResourceLoader: Modules should be able to specify dependencies evaluated at run-time,"Sometimes modules have dependencies that can't be determined until runtime; most obviously, code that requires shims for browser functionality that may be missing on a few clients.
+
+It would be great if instead of static dependencies, modules could specify dependencies that are evaluated at run-time and only loaded if needed.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56341",1402342020,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bkunv6kbite7pb74lhap,task_description,resolved
+ResourceLoader: Modules should be able to specify dependencies evaluated at run-time,"Change 135085 merged by jenkins-bot:
+resourceloader: Implement ""skip function"" feature
+
+https://gerrit.wikimedia.org/r/135085",1402546093,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bkunv6kbite7pb74lhap,task_subcomment,NA
+ResourceLoader: Modules should be able to specify dependencies evaluated at run-time,"Per discussion between Roan and me we're taking this use case as a story rather than a specific call to implementation.
+
+We won't be adding a feature to conditionally declare something as a dependency. So the following will not be the how it is used:
+
+visualeditor.dependencies = [es5]
+->
+visualeditor.dependencies = function (deps) {
+  if ( browser doesn't support es5 ) {
+    deps.push( es5);
+  }
+};
+
+
+Instead we're going to take it the other way around and have the condition be on the target module (e.g. es5.js instead of visualeditor).
+
+visualeditor.dependencies = [es5]
+es5.skip = function () {
+  return browser supports es5;
+};
+
+This way will result in much less duplication, and feels more semantically correct because it doesn't make sense for an application to have a dependency that can change. Modules are supposed to be a canonical representation of an interface, not a specific implementation, skin, language or file. Either the module to provide it or it doesn't. Instead visualeditor (or indeed, oojs) would declare it needs the thing that es5-shim.js provides. And es5-shim can decide to forego fetching of any actual files if it detects the environment has it already (either by native or another polyfill).
+
+This will make the experience for developers much easier (no need to duplicate if -conditions for es5 all over the place) and practically removes any possibility of abusing this feature for implementing any bad ideas.",1402343478,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-bkunv6kbite7pb74lhap,task_subcomment,NA
+ResourceLoader: Modules should be able to specify dependencies evaluated at run-time,"Change 135085 had a related patch set uploaded by Jforrester:
+[WIP] resourceloader: Implement ""skip function"" feature
+
+https://gerrit.wikimedia.org/r/135085",1402342072,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bkunv6kbite7pb74lhap,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","**Author:** `vojtech.dostal`
+
+**Description:**
+A student of Education program at Czech Wikipedia noticed that she cannot resize an image which is inserted as a frame. It is well possible to adjust the size in the preview mode, but saving it does not produce appropriately resized image frame. 
+
+
+see image under heading ""Půdorys"" at:
+https://cs.wikipedia.org/wiki/Kostel_Nanebevzet%C3%AD_Panny_Marie_%28Charvatce%29
+
+Thank you
+Vojtěch Dostál
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402266840,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jwcd6eadytsw2au77emm,task_description,resolved
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Change 138388 merged by jenkins-bot:
+Disable the size widget for 'frame' images
+
+https://gerrit.wikimedia.org/r/138388",1402426284,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Scratch my last remark. There is still a technical debt (that is being taken care of) about default vs. custom size but the issue in this case is that we don't follow the wikitext rules properly. 
+
+Frame images ignore size specification. 
+See wikitext documentation here: https://www.mediawiki.org/wiki/Help:Images#Size_and_frame",1402339903,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Change 138388 had a related patch set uploaded by Mooeypoo:
+Disable the size widget for 'frame' images
+
+https://gerrit.wikimedia.org/r/138388",1402339760,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Yes, after a bit of analysis, I believe there's a problem with the way the scalable object analyzes default vs custom values. I'm working on refactoring the way that works; we have a tech debt about this, too, I believe.",1402331038,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)","Thanks for this bug; it seems like a regression(?!) in MediaWiki. Moriel, can you confirm?",1402294292,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jwcd6eadytsw2au77emm,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Change the Image type from Thumbnail to Frameless/Basic
+
+Observed Result:
+
+The checkbox for wrap option gets unchecked but the alignment tabs are still active
+
+See the screenshot attached
+
+This is happening in Betalabs but not on test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13997}",1402095420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qs2qv3kzzffml4p5gons,task_description,resolved
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",Verified the fix in production (en.wiki),1403300650,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",Verified the fix in test2 running wmf 9,1402700452,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",Verified the fix,1402520085,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",I REALLY mean gerrit 138663,1402518821,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",I mean gerrit 80d1240,1402518795,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs",Fixed in 80d1240,1402518784,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qs2qv3kzzffml4p5gons,task_subcomment,NA
+"VisualEditor: [Regression] ""manual subst"" hack doesn't work any more","It's not really possible to subst MediaWiki templates in VE yet (bug 49904). According to James F., it should be possible to write ""subst:Foo"" when inserting the template with some caveats.
+
+This doesn't seem to work at the time. For example, writing ""subst:Clarify"" in the English Wikipedia, shows the string ""{{subst:Clarify}}"", but as a template with a highlight. When the page is saved, the template {{Clarify|date=June 2014}} is inserted - not substed.
+
+From IRC:
+
+aharoni: Is there a way to do a subst to a template in VE?
+James_F: aharoni: Ish.
+James_F: aharoni: To add a template called ""Foo"", instead tell it to insert subst:Foo"".
+James_F: aharoni: But it doesn't get the TemplateData (so it's pretty icky).
+James_F: aharoni: There's a bug asking for an actual checkbox.
+[...]
+aharoni: James_F: about that subst thing: It doesn't seem to work. It inserts a literal {{subst:Foo}}.
+James_F: aharoni: Huh. That's a regression, then. :-(
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49904",1402089360,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-g4sg72aye2nbqzjdh3gd,task_description,invalid
+"VisualEditor: [Regression] ""manual subst"" hack doesn't work any more",Aha. Anti-subst tech? Whatever next?,1402171502,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g4sg72aye2nbqzjdh3gd,task_subcomment,NA
+"VisualEditor: [Regression] ""manual subst"" hack doesn't work any more","I can't replicate this bug. But I think this is actually invalid.
+
+This 'Clarify' template on enwiki uses some clever 'Unsubst' lua module hack to deliberately break subst - take a look at the source. Also notice how that 'date' parameter appeared from nowhere?
+
+I tested this out using the normal editor (just added '{{subst:Clarify}}'): https://en.wikipedia.org/w/index.php?title=User:Krenair/sandbox&diff=611955311&oldid=492366611
+
+If I try any other non-Unsubst template, it's fine. For example, I added 'subst:Cite web' from VE: https://en.wikipedia.org/w/index.php?title=User:Krenair/sandbox&diff=611955603&oldid=611955311",1402153458,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-g4sg72aye2nbqzjdh3gd,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page","Screenshot
+
+Steps to reproduce:
+
+1.Open any page with VE in Firefox or Chrome
+
+2.Make an Edit
+
+3.Click on ""Switch to source editing""
+
+Observed Result:
+It does not open the wikitext editor for the page, rather a message appears at the op of the page: 
+Some parts of the edit form did not reach the server; double-check that your edits are intact and try again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13873}",1402013460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytqk243gnjxzenhu2jo7,task_description,resolved
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",Verified the fix in production(en.wiki),1403299864,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",Verified the fix in test2 running wmf9,1402705356,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",Verified the fix in Betalabs,1402084693,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",Fixed by the fix for bug 66168.,1402084650,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+"VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message ""Some parts of the edit form did not reach the server; double-check that your edits are intact and try again."" on top of the page",This is happening even for a new page where no edit has been done yet :(,1402014082,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ytqk243gnjxzenhu2jo7,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,"Obviously it'd also be nice if fatals didn't happen, but I have less faith that that is possible in shorter time…
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402012080,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-chatnkffcac2ryz34vhn,task_description,resolved
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,"Change 200649 merged by jenkins-bot:
+Don't break the editor if paste handling fails
+
+[[https://gerrit.wikimedia.org/r/200649]]",1427756404,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,"Change 200649 had a related patch set uploaded (by Catrope):
+Don't break the editor if paste handling fails
+
+[[https://gerrit.wikimedia.org/r/200649]]
+",1427743719,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,"Mostly seems to be caused by elements it doesn't recognise (? like <section>), especially when copying bits of tables and other structures from non-MediaWiki sources (e.g. Google Docs, Bugzilla or other places). Lots of different mystical errors as well about e.g. refusing to insert a closing tag that hasn't been opened.",1402512088,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,Need an example so I know where to put the try/catch.,1402507964,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+VisualEditor: Would be nice if copying/pasting kept working after a fatal,*** Bug 64009 has been marked as a duplicate of this bug. ***,1402505914,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-chatnkffcac2ryz34vhn,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Screenshot
+
+Steps to reproduce:
+
+1.Open any page in Betalabs or test2 with VE in Firefox
+
+2.Make an edit
+
+3.Save the page
+
+4.Reopen the page
+
+Observed Result:
+
+In the console the following error appears:
+
+
+TypeError: this.documentView is null
+
+Also, another issue that is happening is, after editing if you try to switch to edit source mode, it is not opening the wikitext editor.Rather showing a message:
+Some parts of the edit form did not reach the server; double-check that your edits are intact and try again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13849}",1402006920,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lekklfuupduztoemlst2,task_description,resolved
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox",Verified the fix in production en.wiki,1403118845,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox",Not yet fixed in en.wiki,1402619049,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Change 139207 merged by Catrope:
+*Actual* death and/or *actual* destruction
+
+https://gerrit.wikimedia.org/r/139207",1402608657,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Change 139207 had a related patch set uploaded by Catrope:
+*Actual* death and/or *actual* destruction
+
+https://gerrit.wikimedia.org/r/139207",1402608199,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox",This is happening in production.Didn't we backport it?,1402607600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox",Verified the fix in Betalabs,1402354186,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","(In reply to Ed Sanders from comment #8)
+> MW hasn't had a core update since this was merged.
+> 
+> FYI: If there isn't a commit called 'Update VE core submodule to master'
+> above a core commit you are testing on this page:
+> 
+> https://gerrit.wikimedia.org/r/#/q/is:watched+status:merged,n,z
+> 
+For that link to work, you need to be logged in and be watching the right projects :)
+
+More portable link: https://gerrit.wikimedia.org/r/#/q/status:merged+AND+%28+project:mediawiki/extensions/VisualEditor+OR+project:VisualEditor/VisualEditor+%29,n,z",1402346604,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","MW hasn't had a core update since this was merged.
+
+FYI: If there isn't a commit called 'Update VE core submodule to master' above a core commit you are testing on this page:
+
+https://gerrit.wikimedia.org/r/#/q/is:watched+status:merged,n,z
+
+it won't be in MW yet.",1402346453,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","This is still happening in Firefox for Betalabs, So reopening it",1402345997,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Change 138014 merged by jenkins-bot:
+*Actual* death and/or *actual* destruction
+
+https://gerrit.wikimedia.org/r/138014",1402146215,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Change 138014 had a related patch set uploaded by Catrope:
+*Actual* death and/or *actual* destruction
+
+https://gerrit.wikimedia.org/r/138014",1402085007,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","The error from comment 2 happens because the old destroyed surface is getting blurred, and DesktopContext is responding to that.
+
+The fundamental issue is this.fragment.select(); in the teardown process of ve.ui.Dialog, which runs 200ms after the save dialog closes, at which point the surface is already hidden and lots of stuff goes wrong.
+
+Beside that, though, we should be much more aggressive about destroying things properly. And also audit things we do after a delay like this (so potentially anything in a setup/teardown process) because the user might have deactivated the editor in the meantime.",1402016517,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","The ""Switching to edit source mode not opening the wikitext editor"" issue is happening in Chrome as well, however the error found for Firefox in not appearing for Chrome, so I am taking this issue to a different bug, assuming it is not related.",1402013045,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","Also getting this error now:
+
+Error: Range error: Range is no longer valid after DOM mutation ([WrappedRange(""link"":0, ""link"":4)])
+after applying link to the text ""link""",1402010177,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+"VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox","This seems to be happening because, somehow, the old torn-down ce.Surface gets a focus event, calls this.surfaceObserver.startTimerLoop(), but this explodes because the SurfaceObserver has been detached already and its .documentView is null.
+
+We should make sure we properly destroy the old surface.",1402007173,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lekklfuupduztoemlst2,task_subcomment,NA
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"<nowiki> tags appear when editing on the Hebrew Wikipedia:
+
+Examples:
+https://he.wikipedia.org/w/index.php?title=%D7%99%D7%A8%D7%95%D7%9F_%D7%9E%D7%A8%D7%92%D7%95%D7%9C%D7%99%D7%9F&curid=1154717&diff=15542199&oldid=15542181
+
+https://he.wikipedia.org/w/index.php?title=%D7%99%D7%A8%D7%95%D7%9F_%D7%9E%D7%A8%D7%92%D7%95%D7%9C%D7%99%D7%9F&curid=1154717&diff=15542199&oldid=15542181
+
+https://he.wikipedia.org/w/index.php?title=HOT&diff=15542428&oldid=15528284
+
+From the given examples, it seems to be related to editing internal links?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1401996780,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_description,declined
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"Corruption bugs are handled independently on a case-by-case basis; nothing in this list indicates that the <nowiki> issue is specifically related to Hebrew or RTL.
+
+Space in the beginning of paragraphs is followed up in this bug: https://bugzilla.wikimedia.org/show_bug.cgi?id=66628
+
+Transforming a star into bullet point (in the beginning of a line) is followed in this bug report: https://bugzilla.wikimedia.org/show_bug.cgi?id=51408
+
+The rest seem to be errors in typing wikitext.",1412539179,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_subcomment,NA
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"After further analysis, here are the results:
+
+Most of the nowiki problems seem to happen due to typing wikitext in the editor. For instance, typing ''word'' or '''word''' instead of marking the word as italics or bold, or typing literal == which VE then marks as =<nowiki/>= to prevent wikitext'ifying the result.
+
+There are, however, some typing issues we could work on to make the experience easier on users:
+
+1. Users typing a space at the beginning of a paragraph; this seems to be a mistake most of the time. Since a space at the beginning of a paragraph in wikitext transforms the paragraph to a <pre>, VE adds a <nowiki /> tag after it. It might be better if we strip those spaces when we save the page.
+
+2. Users sometimes add list items by typing the literal * at the beginning of a line. While this is wikitext function (so VE wraps it with <nowiki>) it actually might make sense to try and transform any * at the beginning of lines to new bullet points; this is a the behavior that LibreOffice and Word are following, so it might be reasonable to have VE follow suit.
+
+There are very few <nowiki> tags that I saw that are actual corruption. A new one that was reported recently on hewiki might show a problem with reading the wikitext headings wrong, so upon deleting the heading all that's left are == which VE marks with =<nowiki>= (see here: https://he.wikipedia.org/w/index.php?title=%D7%A9%D7%95%D7%9C%D7%97%D7%9F&diff=15566083&oldid=154101 ) 
+
+Some, like this one, seem to show a problem with existing <nowiki> tags that then get ""worse"" after edit: https://en.wikipedia.org/w/index.php?title=Rathmore,_County_Kildare&curid=43246971&diff=618885701&oldid=618885287
+
+We might want to consider marking any existing <nowiki>, perhaps?
+
+In any case, these seem to be fairly uncommon and we should treat them on a case to case basis.",1408373441,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_subcomment,NA
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"This seems to also happen in the English wikipedia with quotes and asterix characters.
+
+Examples:
+
+https://en.wikipedia.org/w/index.php?title=Scar_(The_Lion_King)&curid=30258014&diff=619292425&oldid=619246147
+
+https://en.wikipedia.org/w/index.php?title=Scar_(The_Lion_King)&curid=30258014&diff=619165895&oldid=619158383
+
+https://en.wikipedia.org/w/index.php?title=Ravi_Babu&curid=24981592&diff=618944152&oldid=611211776
+
+https://en.wikipedia.org/w/index.php?title=Adoni&curid=2329629&diff=618931054&oldid=618930241
+
+https://en.wikipedia.org/w/index.php?title=Mia_Freedman&curid=10942134&diff=618755773&oldid=618669491
+
+(Several <nowiki> tags right after quotes)
+https://en.wikipedia.org/w/index.php?title=Rathmore,_County_Kildare&curid=43246971&diff=618885701&oldid=618885287
+
+(Around an asterix)
+https://en.wikipedia.org/w/index.php?title=Tulluru&curid=6910687&diff=618802171&oldid=618802085",1406838421,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_subcomment,NA
+VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki,"I've gone through articles that had 'nowiki' and VisualEditor tags in hewiki to try and find the common error, and as far as I can see, 90% of the errors involve quotes ("") and the others are * and |
+
+Examples:
+
+https://he.wikipedia.org/w/index.php?title=%D7%A2%D7%95%D7%A4%D7%A8_%D7%A2%D7%99%D7%A0%D7%99&curid=309950&diff=15774877&oldid=15774872
+
+https://he.wikipedia.org/w/index.php?title=%D7%94%D7%90%D7%A8%D7%99_%D7%A4%D7%95%D7%98%D7%A8_%D7%95%D7%90%D7%95%D7%A6%D7%A8%D7%95%D7%AA_%D7%94%D7%9E%D7%95%D7%95%D7%AA_(%D7%A1%D7%A8%D7%98)&curid=794595&diff=15773383&oldid=15733742
+
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%95%D7%A2%D7%A6%D7%AA_%D7%94%D7%AA%D7%9C%D7%9E%D7%99%D7%93%D7%99%D7%9D_%D7%95%D7%94%D7%A0%D7%95%D7%A2%D7%A8_%D7%94%D7%90%D7%A8%D7%A6%D7%99%D7%AA&curid=73014&diff=15770323&oldid=15756104
+
+https://he.wikipedia.org/w/index.php?title=%D7%90%D7%9C%D7%99_%D7%A4%D7%99%D7%A0%D7%99%D7%A9&curid=144088&diff=15769264&oldid=15724086
+
+https://he.wikipedia.org/w/index.php?title=%D7%93%D7%95%D7%A7%D7%98%D7%95%D7%A8_%D7%94%D7%95_-_%D7%9E%D7%A4%D7%9C%D7%A6%D7%95%D7%AA&curid=1085331&diff=15768361&oldid=15766030
+
+https://he.wikipedia.org/w/index.php?title=%D7%A1%D7%A8%D7%98_%D7%90%D7%A8%D7%91%D7%A2-%D7%9E%D7%9E%D7%93&curid=1156586&diff=15764947&oldid=15051822
+
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A0%D7%97%D7%9D_%D7%A4%D7%A8%D7%95%D7%A9&curid=33000&diff=15764545&oldid=15571348
+
+https://he.wikipedia.org/w/index.php?title=%D7%A2%D7%95%D7%9E%D7%A8_%D7%93%D7%9E%D7%90%D7%A8%D7%99&curid=908862&diff=15763688&oldid=15763681
+
+https://he.wikipedia.org/w/index.php?title=%D7%A2%D7%93_%D7%A2%D7%A6%D7%9D_%D7%94%D7%99%D7%95%D7%9D_%D7%94%D7%96%D7%94_(%D7%A1%D7%93%D7%A8%D7%AA_%D7%98%D7%9C%D7%95%D7%95%D7%99%D7%96%D7%99%D7%94)&curid=1016962&diff=15762484&oldid=15762481
+
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%91%D7%A6%D7%A2_%D7%A6%D7%95%D7%A7_%D7%90%D7%99%D7%AA%D7%9F&curid=1201545&diff=15761499&oldid=15761352
+
+
+This might be an issue of bad character escaping or encoding.",1406835764,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ldqdnoxy2auvexjbdlp2,task_subcomment,NA
+"VisualEditor: Fields are case sensitive in citation dialog, allowing duplicates of the same field","Two URL fields visible.
+
+The citation dialog field selector is case sensitive. This allows the same field to be added multiple times as long as it's a different case. This results in a ""multiple <field>"" error when the citation is inserted because the fields are treated as case insensitive. 
+
+This issue could organically come up if a citation was added using wikitext and then another user inspected the citation in VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F13823}",1401993720,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-67wxtc4ozjdd24rgjf7t,task_description,invalid
+"VisualEditor: Fields are case sensitive in citation dialog, allowing duplicates of the same field","Not a VE bug :). Turns out this was actually because ""URL,"" which is an accepted alias of ""url"" by module:citation/cs1, wasn't in the templatedata as an alias. This is probably true of a LOT of the other identifiers as well. I fixed this for url on en wiki for the ""big 4"" but this might also be an issue with other identifiers that are commonly capitalised as well, and probably on any template that is based on this module.",1408273027,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-67wxtc4ozjdd24rgjf7t,task_subcomment,NA
+"VisualEditor: Fields are case sensitive in citation dialog, allowing duplicates of the same field","Created attachment 15574
+Two fields error
+
+**Attached**: {F13824}",1401994034,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-67wxtc4ozjdd24rgjf7t,task_subcomment,NA
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"See comments on https://gerrit.wikimedia.org/r/#/c/136981
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401925620,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wiosc4sy22tsxnhzhxot,task_description,resolved
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"Change 138500 merged by jenkins-bot:
+Initialize 'default' size properly in media edit dialog
+
+https://gerrit.wikimedia.org/r/138500",1402425709,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wiosc4sy22tsxnhzhxot,task_subcomment,NA
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"Change 138497 merged by jenkins-bot:
+Reorganize initialization of default size in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/138497",1402423004,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wiosc4sy22tsxnhzhxot,task_subcomment,NA
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"Change 138500 had a related patch set uploaded by Mooeypoo:
+Initialize 'default' size properly in media edit dialog
+
+https://gerrit.wikimedia.org/r/138500",1402357224,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wiosc4sy22tsxnhzhxot,task_subcomment,NA
+VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable,"Change 138497 had a related patch set uploaded by Mooeypoo:
+Reorganize initialization of default size in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/138497",1402356867,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wiosc4sy22tsxnhzhxot,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"VE does not seem to accept the following link:
+
+https://graphite.wikimedia.org/render/?width=588&height=310&_salt=1401910888.742&from=00%3A00_20140513&until=23%3A59_20140604&target=frontend.navtiming.totalPageLoadTime.desktop.authenticated.median&target=frontend.navtiming.totalPageLoadTime.desktop.anonymous.median
+
+Instead, it reverts to the highlighted text as the link target.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66139",1401911520,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_description,resolved
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"Change 138016 merged by jenkins-bot:
+Don't send invalid titles from the link inspector to the API
+
+https://gerrit.wikimedia.org/r/138016",1402102911,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"Change 138016 had a related patch set uploaded by Alex Monk:
+Don't sent invalid titles from the link inspector to the API
+
+https://gerrit.wikimedia.org/r/138016",1402085103,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"External URLs can be valid titles, we just want to ignore invalid titles (i.e. things over 255 characters).",1402081951,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"The HTTP 400 error we get comes with an error: {""code"":""request_too_long"",""info"":""Prefix search request was longer longer than the maximum allowed length. (267 > 255)""}
+
+This is sent by CirrusSearch. Which explains why some wikis don't have this issue.",1402080736,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),I can replicate this on mediawiki.org but not en.wikipedia.org or my local dev wiki.,1402011942,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"This is two separate bugs – we shouldn't be sending these to the API anyway, but we also should cope with the 400 error, which I've made into bug 66139.",1401914590,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),"This shows up in the JS console:
+
+Failed to load resource: the server responded with a status of 400 (Bad Request) https://www.mediawiki.org/w/api.php?format=json&action=query&generator=pref…edian&gpsnamespace=0&prop=info%7Cpageprops&ppprop=disambiguation&redirect=",1401912829,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable),Browser: Chromium 35.0.1916.114 Debian Linux,1401911579,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ae5pdnywbce3fdaiy6ww,task_subcomment,NA
+VisualEditor: isMsie doesn't catch MSIE 11+,"So odd behaviour untested in MSIE11 for CE isn't done differently…
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401835080,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-adgbuexuqgrstkyhiwax,task_description,resolved
+VisualEditor: isMsie doesn't catch MSIE 11+,Fixed by Roan by the simple expediency of deleting this function.,1409099544,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-adgbuexuqgrstkyhiwax,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null","Screenshot
+
+Steps to reproduce:
+
+1.Open a page
+2.Open a link inspector
+3.Click on the Add label link
+
+Observed Result:
+TypeError: this.linkNode is null shows up in the console and cannot close the link inspector afterwards.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14090}",1401738360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_description,resolved
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null",Verified the fix in test2,1402343639,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null",Verified the fix in Betalabs,1401747819,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null","Change 136899 merged by jenkins-bot:
+Remove link node inspector from insert menu
+
+https://gerrit.wikimedia.org/r/136899",1401743256,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf8] Clicking on ""Add Label""/Close button in simple link inspector throws TypeError: this.linkNode is null","Change 136899 had a related patch set uploaded by Catrope:
+Remove link node inspector from insert menu
+
+https://gerrit.wikimedia.org/r/136899",1401743022,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7qzoqhzy6hdwgnxmlkfw,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","To reproduce:
+1. Edit an article in the Hebrew Wikipedia.
+2. Click Insert (הוספה) -> Reference (הערת שוליים).
+Observed: The ""Cite"" item in the toolbar is in English.
+There seems to be a message for it - visualeditor-toolbar-cite-label, and it was translated to Hebrew on May 12 and exported to the code, but it doesn't appear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1401723360,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_description,resolved
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs",Cherry-picks going out tomorrow.,1401927706,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136782 merged by jenkins-bot:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136782",1401924179,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136783 merged by jenkins-bot:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136783",1401924146,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136783 had a related patch set uploaded by Jforrester:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136783",1401730842,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136782 had a related patch set uploaded by Jforrester:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136782",1401730828,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136767 merged by jenkins-bot:
+Use <visualeditor-toolbar-cite-label> correctly in the Media and Reference toolbars
+
+https://gerrit.wikimedia.org/r/136767",1401730718,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+"VisualEditor: The ""Cite"" toolbar item is not internationalised in the Media and Reference dialogs","Change 136767 had a related patch set uploaded by Amire80:
+Use the message visualeditor-toolbar-cite-label correctly
+
+https://gerrit.wikimedia.org/r/136767",1401727586,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sbabim6xkbzbfmpzbhw2,task_subcomment,NA
+VisualEditor: Add reference (footnote) dialog is LTR in RTL wikis,"To reproduce:
+1. Edit an article in the Hebrew Wikipedia.
+2. Click Insert (הוספה) -> Reference (הערת שוליים).
+Observe: The contenteditable div for writing the footnote text is forced to dir=""ltr"".
+Expected: It must be in the direction of the wiki - dir=""rtl"", or simply without the dir, and inherit the direction.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401722160,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-g37btpr3pykwbk3ho5jh,task_description,resolved
+VisualEditor: Add reference (footnote) dialog is LTR in RTL wikis,This seems to be fixed now with the new reference/cite system.,1406316915,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-g37btpr3pykwbk3ho5jh,task_subcomment,NA
+VisualEditor: adding a new link shows the target of the previously-added link for a few moments in the link inspector,"To reproduce:
+
+1. Edit an article with the words Dog and Cat.
+2. Select the word ""Dog"". Press Ctrl-K and add an internal link to Dog.
+3. Select the word ""Cat"".
+4. Press Ctrl-K.
+
+Observe: In the auto-suggestions, ""Dog"" appears for a few moments before it is replaced by ""Cat"".
+Expected: Linking to ""Dog"" is irrelevant here. The previous target and auto-suggestions shouldn't be reused here.
+
+I find this rather disruptive because I want to use the link inspector for its primary purpose of adding links quickly, and this actually delays me by a few seconds. What's worse is that if I'm not careful, I can add a link with the wrong target.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401699120,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-m3mxko4zbo6nl2kgz2by,task_description,resolved
+VisualEditor: adding a new link shows the target of the previously-added link for a few moments in the link inspector,"Change 138113 merged by jenkins-bot:
+[BREAKING CHANGE] Update OOjs UI to v0.1.0-pre (9f4f250f88) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138113",1402533081,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m3mxko4zbo6nl2kgz2by,task_subcomment,NA
+VisualEditor: adding a new link shows the target of the previously-added link for a few moments in the link inspector,"Change 138113 had a related patch set uploaded by Jforrester:
+[BREAKING CHANGE] Window process cleanup
+
+https://gerrit.wikimedia.org/r/138113",1402353749,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m3mxko4zbo6nl2kgz2by,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,"Steps to reproduce;
+
+1.Open a page 
+2.Open the reference dialog 
+3.Click on use existing reference or just simply close it
+
+Observed Result:
+TypeError: sel.nativeSelection is null aappears in the console
+
+Environment:test 2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1401431160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dtf7e3athicgtegt5jra,task_description,resolved
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,Verified the fix in en.wiki running wmf8,1402685315,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,Verified the fix in test2,1402344115,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,Verified the fix in Betalabs,1401491594,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,"Change 136451 merged by jenkins-bot:
+Cleanup createSurface methods
+
+https://gerrit.wikimedia.org/r/136451",1401484639,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,"Change 136451 had a related patch set uploaded by Jforrester:
+Cleanup createSurface methods
+
+https://gerrit.wikimedia.org/r/136451",1401482937,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,Almost certainly the same cause as bug 65934,1401480027,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox,This is also happening while closing Media Settings dialog in Firefox,1401433112,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dtf7e3athicgtegt5jra,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,"Screenshot
+
+Steps to reproduce
+
+1.Open a page
+2.Go to Insert>Reference
+3.Type in a text as reference
+
+Observed Result:
+Each letters are getting added in each line , ends with a pawn then the text appears.The following error appears in the console:
+
+Error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds
+
+After clicking on ""Insert Reference"":
+
+TypeError: sel.nativeSelection is null
+
+After saving the page:
+TypeError: elem.ownerDocument.defaultView is null
+
+This issue is happening on Firefox only.
+
+Environmen:test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13820}",1401430500,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7xd4p7fhhty3seeornpc,task_description,resolved
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,Verified the fix in en.wiki running wmf8,1402685106,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,Verified the fix in test2,1402344699,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,Verified the fix in Betalabs,1401491568,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,"Change 136451 merged by jenkins-bot:
+Cleanup createSurface methods
+
+https://gerrit.wikimedia.org/r/136451",1401484642,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,"Change 136451 had a related patch set uploaded by Jforrester:
+Cleanup createSurface methods
+
+https://gerrit.wikimedia.org/r/136451",1401482932,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox,Caused by https://gerrit.wikimedia.org/r/#/c/135012/ being a breaking change but not marked as such. Will be fixed once https://gerrit.wikimedia.org/r/#/c/135014 is merged.,1401479343,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7xd4p7fhhty3seeornpc,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"James's suggestion: never split a paragraph with a block image. It's not at all obvious what happened, especially if the image is floated right. Instead, we should put the image at the beginning of the paragraph. This would apply when inserting an image, converting an inline image to a block image, and when drag-and-dropping an image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51666",1401320100,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_description,resolved
+VisualEditor: Only insert block images at the start of a paragraph,"Please discuss Tech News issues by going to Tech News (e.g. Talk page) and not to a VE bug report in Bugzilla. General questions like at the end of comment 5, even if you might consider image maps somehow related to block images in general, should better go to IRC or mailing lists. Thanks.",1403364381,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"(In reply to James Forrester from comment #4)
+
+See Bug 66896 (general RFE plus a real bug)
+
+For allowing max-height and general improvement to client-side (and text-friendly) image rescaling which should also be frienfly with the current (broken) Mobile view.",1403315507,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"- It is a bug of the Tech News that incorrectly says it applies to all images.
+- This is in our control (Tech News can be fixed to say it applies only to ""block images"", i.e. images with left/right/center/thumb parameters, and not to other inline images; notably the many emoticon images used in may places in the middle of paragraphs: these images must not be constrained to be only at the start of paragraphs, when inserted or modified with the VisualEditor! Asian users will immediately think that the change is undesirable if they think they can't use their emojis without a supporting font !)",1403315174,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"(In reply to Philippe Verdy from comment #5)
+> So the current Tech News needs correction.
+
+Our submissions to Tech News are generally re-written to be ""simpler"" and wrong. This is not (a) a bug and (b) within our control.
+
+The rest of this is not germane for this bug; please take discussion to a venue for proper discussion, like MediaWiki.org or a mailing list.",1403313393,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"So the current Tech News needs correction.
+The expressions ""block image"" is ambiguous, at first reading I wondered who was right.
+
+Yes having client-side image resizing with just the addition of support of custom CSS for images would be a bonus.
+
+I know this works because this is already visible and used on the Mobile view even if it works with ""max-width:100%"" (used with the ""box-model"" quirk that should have never been used in its specific stylesheet, and which is absolutely not needed)
+
+It also works best with the support of ""image sets"" (now enabled by default in MediaWiki that can lists several thumbnail sizes, at resolutions 1x, 1.5x and 2x; but it could also add 0.5x and 0.75x for best results, letting browsers select the best interpolations depending on screen resolution and/or zoom mode; and ideally, the image sets for SVG images could also list the native SVG format for the best quality needed for images replacing complex text)
+
+----
+
+For now the current Tech News for this week (referencing this bug) needs fixing as it is interpreted as meaning all images.
+
+And what you call a ""block image"" is in MediaWiki an [[image:]] or [[file:]] with ""left"" or ""right"" floating-mode attribute, or ""center"", or ""thumb(nail)"" (your terminology is strange, because in HTML images are always inline by default, and even MediaWiki keeps them inline by placing the generated <img> element, possibly surrounded by an <a> element, within a block element).
+
+----
+
+Also, what is happening to image maps in the VisualEditor ? (they are also inline by default, and probably should be resizable by the client)",1403311665,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"(In reply to Philippe Verdy from comment #3)
+> What is happening to **inline** images (sometimes used to replace some text
+> which is hard to render, such as letters with stacked diacritics rarely
+> supported in fonts, where the word is instead rendered using an SVG image,
+> or small icons, when they are not inserted by using a custom template?
+
+Nothing. This bug is only about block images, as it says.
+
+> OK there's a problem with inline images because they cannot be easily
+> dimensionned according to the current font size and positioned according to
+> the line-height and specific baseline of some scripts, and they cannot match
+> other font styles. But they are still needed in some cases because it is not
+> possible to build custom fonts in pages without support of page-level CSS,
+> or scoped CSS (it is impossible with inline CSS in element style attributes
+> that don't have selectors).
+> 
+> ----
+> 
+> Note that it should be possible to rescale an inline SVG image to fit in the
+> 1.6em line-height using CSS ""max-height:1.6em"" in the <img> HTML element,
+> but MediaWiki still does not support setting any ""style="" attribute in
+> [[File:name]] or [[Image:name]].
+> 
+> You can see the effect of client-side image rescaling in the Mobile view of
+> our wikis: it uses ""max-width:100% !important"" (in addition to other really
+> dirty quirks such as changing the ""box-model:"" of almost all elements to
+> ""border-box"" inherited from old ""IE quirks mode"", rather than the standard
+> ""content-box"", breaking lots of layouts, even though the mobile view has
+> never been meant to be used with old version of IE; but meant to be used
+> with standard HTML! Someone shoud rework the Mobile view to remove this
+> dirty quirk that breaks lots of layouts as it applies to ALL spans and
+> blocks, forcing many templates to manually set the ""content-box:content-box""
+> everywhere and dewikifying lists with ol/ul + li or dl + dt/dd...).
+> 
+> With the support client-side image rescaling (support of ""max-height:"" style
+> in wiki-images), inline images are safe in the middle of a paragraph (for
+> now they are supported provided that template specify small heights, below
+> 20px).
+
+
+This feels like a MediaWiki bug (""Please let me size text-inline images to automatically be line-height"") – do you want to create one?",1403308771,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"What is happening to **inline** images (sometimes used to replace some text which is hard to render, such as letters with stacked diacritics rarely supported in fonts, where the word is instead rendered using an SVG image, or small icons, when they are not inserted by using a custom template?
+
+OK there's a problem with inline images because they cannot be easily dimensionned according to the current font size and positioned according to the line-height and specific baseline of some scripts, and they cannot match other font styles. But they are still needed in some cases because it is not possible to build custom fonts in pages without support of page-level CSS, or scoped CSS (it is impossible with inline CSS in element style attributes that don't have selectors).
+
+----
+
+Note that it should be possible to rescale an inline SVG image to fit in the 1.6em line-height using CSS ""max-height:1.6em"" in the <img> HTML element, but MediaWiki still does not support setting any ""style="" attribute in [[File:name]] or [[Image:name]].
+
+You can see the effect of client-side image rescaling in the Mobile view of our wikis: it uses ""max-width:100% !important"" (in addition to other really dirty quirks such as changing the ""box-model:"" of almost all elements to ""border-box"" inherited from old ""IE quirks mode"", rather than the standard ""content-box"", breaking lots of layouts, even though the mobile view has never been meant to be used with old version of IE; but meant to be used with standard HTML! Someone shoud rework the Mobile view to remove this dirty quirk that breaks lots of layouts as it applies to ALL spans and blocks, forcing many templates to manually set the ""content-box:content-box"" everywhere and dewikifying lists with ol/ul + li or dl + dt/dd...).
+
+With the support client-side image rescaling (support of ""max-height:"" style in wiki-images), inline images are safe in the middle of a paragraph (for now they are supported provided that template specify small heights, below 20px).",1403307572,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"Change 140037 merged by jenkins-bot:
+Insert images at the start of paragraphs
+
+https://gerrit.wikimedia.org/r/140037",1403134828,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Only insert block images at the start of a paragraph,"Change 140037 had a related patch set uploaded by Mooeypoo:
+Insert images at the start of paragraphs
+
+https://gerrit.wikimedia.org/r/140037",1402958320,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f45ircs47t3ihtnmxal3,task_subcomment,NA
+VisualEditor: Viewport scrolls to top after drag-and-dropping image,"Go to a page with an image that's below the fold (i.e. you have to scroll down to see it). Drag it and drop it in a position that's also below the fold.
+
+The viewport scrolls up to the top, scrolling the image out of view :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62420
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66462",1401319920,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-34u5syhh5mqyo7rcvvfm,task_description,resolved
+VisualEditor: Viewport scrolls to top after drag-and-dropping image,"Change 138833 merged by jenkins-bot:
+Don't refocus the document in onModelSelect
+
+https://gerrit.wikimedia.org/r/138833",1402534639,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-34u5syhh5mqyo7rcvvfm,task_subcomment,NA
+VisualEditor: Viewport scrolls to top after drag-and-dropping image,"Change 138833 had a related patch set uploaded by Esanders:
+Don't refocus the document in onModelSelect
+
+https://gerrit.wikimedia.org/r/138833",1402502781,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-34u5syhh5mqyo7rcvvfm,task_subcomment,NA
+"VisualEditor: Cannot go to the next line of an article after inserting a special character in a block slug and ""TypeError: Inserted data is trying to close the root node (at index 0)"" appears","Screenshot
+
+Steps to reproduce:
+
+1.Open this page with VE:http://en.wikipedia.beta.wmflabs.org/wiki/28thmayff?veaction=edit
+
+2.Insert a special character in the block slug just on top of the last image in the page
+
+3.Press enter to go to the next line
+
+Observed Result:
+Cannot go to the next line, the following error appears:
+
+Error: Inserted data is trying to close the root node (at index 0)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13657}",1401309240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hzfx6auxygw63xeggrj6,task_description,resolved
+"VisualEditor: Cannot go to the next line of an article after inserting a special character in a block slug and ""TypeError: Inserted data is trying to close the root node (at index 0)"" appears",Appears to work now.,1423749786,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hzfx6auxygw63xeggrj6,task_subcomment,NA
+"VisualEditor: Cannot go to the next line of an article after inserting a special character in a block slug and ""TypeError: Inserted data is trying to close the root node (at index 0)"" appears",Yay for things in block slugs. :-(,1402525358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hzfx6auxygw63xeggrj6,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Since a few days, there are reports of the version dropdown being empty even though the branches exist. This makes it impossible to download extensions from ExtensionDistributor.
+
+https://www.mediawiki.org/wiki/Thread:Extension_talk:CirrusSearch/CirrusSearch_download
+https://www.mediawiki.org/wiki/Thread:Project:Current_issues/Can%27t_download_extensions
+
+--------------------------
+**Version**: master
+**Severity**: major",1401283020,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_description,resolved
+ExtensionDistributor: Some extensions have no versions available for download,"We're no longer using github at all, so this should no longer be an issue.",1406830858,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"I203d635b2a5e42197913d7d8b7cd8da083dd8981 was also merged, which will provide negative cache entries when a branch doesn't exist, which should make this a lot better in the short term.
+
+After discussing with ^d and James_F, we're going to stop using github and instead use a labs setup I created (ex: http://extdist.wmflabs.org/?version=REL1_23&ext=VisualEditor) which will make it so we don't need to worry about ratelimiting at all.",1405544184,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Change 146386 merged by jenkins-bot:
+Allow making API requests as an authenticated user
+
+https://gerrit.wikimedia.org/r/146386",1405544032,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Change 146394 merged by jenkins-bot:
+Display an error if no branches are found
+
+https://gerrit.wikimedia.org/r/146394",1405543516,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Change 146394 had a related patch set uploaded by Florianschmidtwelzow:
+Display an error if no branches are found
+
+https://gerrit.wikimedia.org/r/146394",1405411159,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Change 146386 had a related patch set uploaded by Legoktm:
+Allow making API requests as an authenticated user
+
+https://gerrit.wikimedia.org/r/146386",1405402706,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"legoktm@terbium:~$ curl --proxy url-downloader.wikimedia.org:8080 -i https://api.github.com/repos/wikimedia/mediawiki-extensions-MassMessage/tarball/REL1_23
+
+X-RateLimit-Limit: 60
+X-RateLimit-Remaining: 0
+
+and the content body:
+
+{
+  ""message"": ""API rate limit exceeded for <ip>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)"",
+  ""documentation_url"": ""https://developer.github.com/v3/#rate-limiting""
+}",1405400739,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Are we being hit by github's ratelimiting? (I don't know if we have a special exemption or anything...)
+
+Via eval.php:
+
+> $httpOptions = array( 'followRedirects' => false );
+
+> $httpOptions['proxy'] = $wgExtDistProxy;
+
+> $req = MWHttpRequest::factory(""https://api.github.com/rate_limit"", $httpOptions);
+
+> var_dump($req->getContent());
+string(177) ""{""resources"":{""core"":{""limit"":60,""remaining"":0,""reset"":1405398906},""search"":{""limit"":10,""remaining"":10,""reset"":1405396979}},""rate"":{""limit"":60,""remaining"":0,""reset"":1405398906}}""",1405397710,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,Seems to be somewhat random. Versions appearing and disappearing regardless of their branches existing.,1405372877,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"These extensions shows an empty dropdown here and seem to have RELX_XX branches:
+* https://www.mediawiki.org/wiki/Special:ExtensionDistributor/LoopFunctions
+* https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FLoopFunctions
+
+* https://www.mediawiki.org/wiki/Special:ExtensionDistributor/MediaFunctions
+* https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FMediaFunctions
+
+* https://www.mediawiki.org/wiki/Special:ExtensionDistributor/AbuseFilter
+* https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FInterwiki
+
+And I guess some more...",1405342596,PHID-USER-e7a5lnjpgncgdxknmdxb,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"I confirm this, while the extensions has RELX_XX branches: https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FNonlinear",1405342016,PHID-USER-e7a5lnjpgncgdxknmdxb,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Created attachment 15932
+Example extension Nonlinear
+
+https://www.mediawiki.org/wiki/Special:ExtensionDistributor/Nonlinear
+
+This extension actually doesn't work for me.
+
+**Attached**: {F13612}",1405341875,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Works here also, couldn't find any extension where ExtensionDistributor fails. Btw, is that URL in this bugs' settings really needed?",1405340765,PHID-USER-e7a5lnjpgncgdxknmdxb,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Hmm, now it works for me, too :/",1405340412,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"(In reply to Florian from comment #11)
+> One more example:
+> https://www.mediawiki.org/wiki/Special:ExtensionDistributor/
+> ExtensionDistributor
+> 
+> (It's ExtensionDistributor itself)
+
+Works for me at this moment",1405339399,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"One more example:
+https://www.mediawiki.org/wiki/Special:ExtensionDistributor/ExtensionDistributor
+
+(It's ExtensionDistributor itself)
+
+And there are some RELX_XX branches:
+https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/ExtensionDistributor,branches",1405322657,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Oh, yeah, i thought there was one, will create it, thanks :) i will look into some extensions i remember tomorrow, when i'm at pc again.",1405026386,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"(In reply to Florian from comment #8)
+> One example that doesn't work:
+> 
+> https://www.mediawiki.org/wiki/Special:ExtensionDistributor/GoogleLogin
+
+That one has an explanation. It doesn't have any REL1_XX branch [1]
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FGoogleLogin.git
+
+ED shouldn't be listed in the extension's page",1405025635,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"One example that doesn't work:
+
+https://www.mediawiki.org/wiki/Special:ExtensionDistributor/GoogleLogin",1405025304,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"I've checked all extensions linked in comments from this bug and all of them list 1.23 and older in their dropdown. It's still an issue?
+
+Note that some extensions weren't properly branched for 1.23, downloading an old (and probably incompatible) version, but that's bug 64157",1405024985,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Hmm, now i have now list of versions, too, on some Extensions :/",1404384584,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Created attachment 15498
+branches exist
+
+Hmm, anything i do false :?
+
+Now i have tested with FF, Chrome and Android/HTC Stock Browser
+
+**Attached**: {F13611}",1401288938,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"Problem does also exist for downloading Oversight (is that extension even downloadable?), see https://www.mediawiki.org/wiki/Special:ExtensionDistributor/Oversight. Status can be changed to CONFIRMED.",1401286059,PHID-USER-e7a5lnjpgncgdxknmdxb,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"https://www.mediawiki.org/wiki/Special:ExtensionDistributor/MaintenanceShell (original report) does have empty dropdown for me, how common is this? How are they picked?",1401283956,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"I see 1.22 and master for CirrusSearch. Giving me https://codeload.github.com/wikimedia/mediawiki-extensions-CirrusSearch/legacy.tar.gz/REL1_22 to download
+
+There is no 1.23, but that isn't setup in CommonSettings.php",1401283327,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+ExtensionDistributor: Some extensions have no versions available for download,"-> https://www.mediawiki.org/wiki/Special:ExtensionDistributor/CirrusSearch
+I see a master and 1.22 branch :/
+
+-> https://www.mediawiki.org/wiki/Special:ExtensionDistributor?extdist_extension=AbuseFilter
+Abuse Filter all branches up from 1.19 :) Tested with Firefox 17.0.1 ESR and Google Chrome 34.0.1847.116m",1401283273,PHID-USER-c5xwrfdyp3dckkh2nkoj,False,PHID-TASK-ypgoy4zxc5bctzwefulz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,"Error: Unknown dependency: mediawiki.skinning.content.parsoid Error {stack: (...), message: ""Unknown dependency: mediawiki.skinning.content.parsoid""} load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:160
+
+logload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:160
+handlePendingload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:169
+runScriptload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:170
+checkCssHandlesload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:171
+(anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:171
+fireload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:44
+self.fireWithload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:46
+self.fireload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:46
+addEmbeddedCSSload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:166
+(anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:165
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1401211500,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-zvmwksybywvrfm2uti2u,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,Should now be fixed.,1401219438,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,"Change 135606 merged by jenkins-bot:
+Enable mediawiki.skinning.content.parsoid on Mobile target too
+
+https://gerrit.wikimedia.org/r/135606",1401217520,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,"Change 135606 had a related patch set uploaded by Jforrester:
+Enable mediawiki.skinning.content.parsoid on Mobile target too
+
+https://gerrit.wikimedia.org/r/135606",1401216207,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,Aha. I'm a complete fool; my apologies. Fix inbound.,1401216189,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,See also bug 64607,1401212465,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,It's not invalid. This is on beta labs which mirrors production. It sounds like Parsoid is declaring a module that has not been set to the mobile target. We had this exact issue before with another RL module.,1401212427,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,mediawiki.skinning.content.parsoid is provided by MW-core as of Wednesday – see gerrit 130770.,1401212212,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target,Sounds like you just didn't install the Parsoid *extension* when it became required (used to be optional).,1401211947,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-zvmwksybywvrfm2uti2u,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","No manual repro or network trace so far, this is for tracking
+
+VE loses user token: 
+https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/9/testReport/(root)/VisualEditor%20multi-edit%20workflow/Make_multiple_edits_to_the_same_article/
+
+VE logs user out:
+https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/12/testReport/junit/(root)/Switching%20between%20wikitext%20and%20Visual%20Editor%20modes/Switch_editing_modes_via_toolbar/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65710
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66076
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67171",1400887020,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_description,resolved
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures",Handled this by better managing test users. There was a rogue test logging out. ,1423259488,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Given this is a duplicate of non-VE bugs, it's clearly a MediaWiki issue that the Editing team haven't been able to track down. :-( Moving.",1404153510,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures",*** Bug 62583 has been marked as a duplicate of this bug. ***,1404138675,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Created attachment 15686
+Something went wrong... session no longer valid
+
+Slightly different manifestation of error message for this issue.
+
+**Attached**: {F13886}",1403208502,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures",also still getting this in automated tests launched from WMF Jenkins (not Cloudbees) for example https://saucelabs.com/tests/5c4697a6618543708b7a59382e9813f6,1402341824,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Created attachment 15608
+Screenshot
+
+**Attached**: {F13885}",1402338060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Created attachment 15607
+Screenshot
+
+I reproduced this issue, after clicking on Switch to edit source and then again coming back to VE,I tried to save the page from VE.
+It showed an error: there might be an edit conflict in the save dialog and then I got logged out
+
+See the screenshots attached
+
+**Attached**: {F13882}",1402338036,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures",Now seen in Chrome also https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/535/,1401466027,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","I should have said: 
+
+Note: a close look at the screencast of the logout instance shows the logout happens instantly upon clicking Edit source for logged-in user while the user is in VisualEditor.",1400888911,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+"In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures","Note: a close look at the screencast of the logout instance shows the logout happens instantly upon clicking Edit source for logged-in user.  
+
+In attempting to recreate the problem I encountered Bug 65710.  
+
+Since the beta warning is controlled by a cookie, these issues may be related.",1400887564,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-u3bc5ilahqhu67jkbxxw,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>References list
+3.Observe the animation that happens when you open it.
+
+Observed Result:
+In both Chrome and Firefox , there is a bit of irregular animation when you try to open the reference list for the first time
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400885220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-emgwmnazcg2mnjqwuy34,task_description,resolved
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,Verified the fix in production (en.wiki),1403300744,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,Verified the fix in test2 running wmf9,1402697182,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,"Change 138114 merged by jenkins-bot:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533856,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,"Change 138114 had a related patch set uploaded by Jforrester:
+[BREAKING CHANGE] Window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402353853,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session,"It's simultaneously opening (animating from 0.5 scaling factor to 1.0) and animating from normal size to small size, that's why it looks weird.",1401303106,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-emgwmnazcg2mnjqwuy34,task_subcomment,NA
+VisualEditor: PageTriage UI appears after save,"PageTriage shown after saving edit.
+
+I've seen this a few times, but this is the first time I've been in a position to take a screen shot.  
+
+After saving an edit in VE, the PageTriage pager UI exists on the saved page.  See screen shot.
+
+Note: the page is still viable at http://en.wikipedia.beta.wmflabs.org/wiki/Special:NewPagesFeed
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13852}",1400884440,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-cgd7gfh5limbmfzyuqbj,task_description,resolved
+VisualEditor: PageTriage UI appears after save,"Change 135587 merged by jenkins-bot:
+Follow-up I7b49a6dd0: Fix page curation bar reappearing after VE closes
+
+https://gerrit.wikimedia.org/r/135587",1401319645,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cgd7gfh5limbmfzyuqbj,task_subcomment,NA
+VisualEditor: PageTriage UI appears after save,"Change 135587 had a related patch set uploaded by Alex Monk:
+Fix page curation bar appearing after VE closes for some users
+
+https://gerrit.wikimedia.org/r/135587",1401209848,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cgd7gfh5limbmfzyuqbj,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Insert>Reference
+3.Type something in the text box
+4.Click on ""Insert Reference""
+5.Again re-open that reference
+6.Delete the content inside the text field
+
+Observed Result:
+issue 1: The ""Use an existing reference"" button remains enabled when user has entered something in the textbox (step 3), it should be disabled as soon as user enters types something in the field.
+
+issue 2:After clicking on ""insert reference"" , when user reopens that reference, there is no ""Use an existing reference"" button in the reference dialog box (step5), the button should appear there but as ""Disabled""
+
+Once user deletes the content inside the text field (step 6), the button should again re-anabled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400868360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_description,resolved
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it",Verified the fix in production(en.wiki),1403299959,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it",Verified the fix in test2 running wmf 9,1402705124,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it",Verified the fix in Betalabs,1402348021,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Change 136599 merged by jenkins-bot:
+MWReferenceDialog: Allow swapping of existing references for others
+
+https://gerrit.wikimedia.org/r/136599",1402102521,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Change 136599 had a related patch set uploaded by Alex Monk:
+Allow swapping of existing references for others.
+
+https://gerrit.wikimedia.org/r/136599",1401564246,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","(In reply to ryasmeen from comment #4)
+> When I will delete the content of that already added reference, it should
+> re-enable that button.
+
+This bit is being dealt with already in Gerrit change 136505",1401562796,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","The issue 2 stated above in the bug report is still there:
+
+When I reopen an already added reference , there should be ""Use an existing reference"" button in that dialog but disabled , right now the button is not there at all.
+
+When I will delete the content of that already added reference, it should re-enable that button.",1401499329,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Change 136443 merged by jenkins-bot:
+""Use an existing reference"" in the reference dialog should be disabled when there is content
+
+https://gerrit.wikimedia.org/r/136443",1401488795,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","Change 136443 had a related patch set uploaded by Alex Monk:
+""Use an existing reference"" in the reference dialog should be disabled when there is content
+
+https://gerrit.wikimedia.org/r/136443",1401480442,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: ""Use an existing reference"" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it","James says it should disable when the surface is not empty and re-enable when empty, and also appear for existing references.",1401303220,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wnt7rzmhqp7spos2ra3v,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a left aligned thumbnail and Frame image, unchecking the wrapping option moves it to the right side of the page","Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image
+3.Make it Thumbnail or Frame
+4.Make it left aligned
+5.Now uncheck the wrap option 
+6.Click on ""Apply Changes""
+
+Observed Result:
+
+The image gets moved to the right side of the page
+
+
+Environment : Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400715360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gcxpqprlky5p3csmakeu,task_description,resolved
+"VisualEditor: [Regression wmf6] For a left aligned thumbnail and Frame image, unchecking the wrapping option moves it to the right side of the page",Verified the fix in production,1402086527,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gcxpqprlky5p3csmakeu,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a left aligned thumbnail and Frame image, unchecking the wrapping option moves it to the right side of the page",Verified the fix in test2,1401496888,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gcxpqprlky5p3csmakeu,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a left aligned thumbnail and Frame image, unchecking the wrapping option moves it to the right side of the page",Verified the fix on Betalabs,1401212247,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gcxpqprlky5p3csmakeu,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Steps to reproduce:
+
+1.Open a oage with VE
+2.Insert an image
+3.Make it right aligned and framless
+4.Hover over it
+
+Observed Result:
+It throws the following error:
+Uncaught TypeError: Cannot read property 'getSurface' of null
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400714160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-goldr7i773st4wqcjxev,task_description,resolved
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Change 134363 merged by jenkins-bot:
+[BREAKING CHANGE] Merge ProtectedNode into FocusableNode
+
+https://gerrit.wikimedia.org/r/134363",1402442351,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,Verified the fix in production.,1402091164,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,Verified the fix in Betalabs and test 2,1400808287,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,Still fixed.,1400800772,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Change 134363 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Merge protected node into focusable node
+
+https://gerrit.wikimedia.org/r/134363",1400797623,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,Fixed and backport going out in SWAT.,1400795905,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Change 134363 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Merge protected node into focusable node
+
+https://gerrit.wikimedia.org/r/134363",1400770552,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"Created attachment 15455
+Screenshot
+
+**Attached**: {F13647}",1400738209,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null,"It also happens for the following case:
+
+1. Change alignment of any image
+2. Delete the image
+3. Observe that, the phantom of the image is still there after deleting the image
+4.Now hover over the phantom
+
+Observed Result:
+As soon as you delete the image the error: Cannot read property 'getSurface' of null appears, also everytime you hover over the phantom , you will get this same error.
+
+See the screenshot attached",1400738183,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-goldr7i773st4wqcjxev,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image of any type
+3.Now uncheck the wrapping option
+4.Click on ""Apply Changes""
+5.Open the media settings dialog box again
+
+Observed Result:
+The wrap option is getting checked again
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400713740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_description,resolved
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,Verified the fix in production,1402088566,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,Verified the fix in test2,1401397894,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,Verified the fix in Betalabs,1401318840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,"Provisionally, fixed in gerrit 135699.",1401318622,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,This should be resolved now following the change of default alignment pt II,1401317043,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,This is still happening on Betalabs,1401224236,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types,This should be resolved now following the change of default alignment.,1401213663,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-cuzlz53jl73xd5rwzfwe,task_subcomment,NA
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size","screenshot
+
+Steps to reproduce:
+
+1.Go to this page: http://en.wikipedia.beta.wmflabs.org/wiki/21stmaychrome?veaction=edit
+
+2.Open the Media settings>Advanced Settings dialog for the first image
+
+3.Click on Custom tab for the image
+
+4.Once you get the size values are invalid, click on default tab
+
+Observed Result:
+
+The fields for default size gets empty , switching back to custom also shows empty fields and the ""MAke full size"" button gets disabled
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13636}",1400713080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zjnwbcq6vujt355a3rpo,task_description,resolved
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size",Verified the fix in Betalabs,1401314050,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zjnwbcq6vujt355a3rpo,task_subcomment,NA
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size","Change 135832 merged by jenkins-bot:
+Decode URL encoding in resource attriute for images
+
+https://gerrit.wikimedia.org/r/135832",1401311084,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zjnwbcq6vujt355a3rpo,task_subcomment,NA
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size","Change 135832 had a related patch set uploaded by Catrope:
+Decode URL encoding in resource attriute for images
+
+https://gerrit.wikimedia.org/r/135832",1401305034,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zjnwbcq6vujt355a3rpo,task_subcomment,NA
+"VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size",This is because the image in question is the feared Image With A Question Mark of Doom. Moriel is looking at it.,1401303580,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zjnwbcq6vujt355a3rpo,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it frameless/basic
+4.Change the alignment to Left
+5.Now try to change the alignment to Right
+6.Click on ""Apply changes""
+
+Observed Result:
+The alignment is still set as left , not moving it to Right
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400698800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_description,resolved
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Verified the fix in production,1402087318,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Verified the fix in test2,1401495524,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Verified the fix in Betalabs,1401315459,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,"Change 135167 merged by jenkins-bot:
+Followup dd1c7f7fd7: fix LESSification errors in Parsoid styles
+
+https://gerrit.wikimedia.org/r/135167",1400901128,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,"Change 135167 had a related patch set uploaded by Catrope:
+Followup dd1c7f7fd7: fix LESSification errors in Parsoid styles
+
+https://gerrit.wikimedia.org/r/135167",1400900653,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,This is happening for all image types now.Not just Frameless and Basic,1400891735,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Reopening since I can still reproduce this issue for both the image types in Betalabs.,1400706744,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,Marking as such.,1400705022,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right,The latest fix (https://gerrit.wikimedia.org/r/#/c/134660/) should fix this too (tested on master),1400703639,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-d77ihdd6l74pyicsh6os,task_subcomment,NA
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Clean up the mess I made in https://gerrit.wikimedia.org/r/134546
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400638440,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-scuorfdmgzjdphugjbmh,task_description,resolved
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Change 134621 merged by jenkins-bot:
+Clean up interaction with confirmation dialog
+
+https://gerrit.wikimedia.org/r/134621",1401494095,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-scuorfdmgzjdphugjbmh,task_subcomment,NA
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Change 134620 merged by jenkins-bot:
+[BREAKING CHANGE] Emit a single event from confirmation dialog
+
+https://gerrit.wikimedia.org/r/134620",1401492000,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-scuorfdmgzjdphugjbmh,task_subcomment,NA
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Change 134621 had a related patch set uploaded by Alex Monk:
+Clean up interaction with confirmation dialog
+
+https://gerrit.wikimedia.org/r/134621",1400686854,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-scuorfdmgzjdphugjbmh,task_subcomment,NA
+VisualEditor: Clean up unbinding of ConfirmDialog events,"Change 134620 had a related patch set uploaded by Alex Monk:
+Emit a single 'done' event from confirmation dialog instead of 'ok' and 'cancel'
+
+https://gerrit.wikimedia.org/r/134620",1400686764,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-scuorfdmgzjdphugjbmh,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Screenshot
+
+Steps to reproduce:
+
+1. Insert a frameless-left aligned image 
+2.Save the page
+3.Reopen the page
+4.Open the Media Settings dialog for the image
+
+
+Observed Result:
+There is no text field for the caption,Cannot close the Media Settings dialog box.
+The following error appears in the console:
+TypeError: node.getCaptionNode is not a function
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13542}",1400632140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_description,resolved
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears",Verified the fix in production,1401392205,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears",Verified the fix in test2,1400809157,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears",Verified the fix in Betalabs,1400700825,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","(In reply to Roan Kattouw from comment #4)
+> Well, you can most certainly trust node.getType() to tell you if calling
+> node.getCaptionNode() will cause it to explode or not, and you apparently
+> can't trust imgModel.getImageNodeType() in this case ;)
+Yes, fallbacks should be included. I think the current (merged) commit dealt with that, I hope no more bugs will come with it, but I'll go over the code to verify.
+
+> Yup, that sounds reasonable. However, we'd also have to define what happens
+> when we inspect a node whose type appears to be ""wrong""; we probably
+> shouldn't change its type if the user didn't change any of the flags. OTOH,
+> this just shouldn't happen.
+
+That would be a problem, though -- how would we know that the type is wrong? It's not like the user consciously chooses inline vs block. The inline/block type is defined by seemingly arbitrary flags. They're not completely arbitrary, which is good, but they're also not entirely intuitive either. The only way to know for sure is through the tests in the getImageNodeType. It just has to be verified to follow the right conditions.
+
+In this case, I had a typo in there, and from my tests so far this *should* be true for all the cases I tested, but I am slightly concerned we may be missing things with wikitext, or that if new types are added we will have to adjust as well.",1400649158,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Change 134554 merged by jenkins-bot:
+Fix MWImageModel's getImageNodeType()
+
+https://gerrit.wikimedia.org/r/134554",1400645312,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Change 134554 had a related patch set uploaded by Mooeypoo:
+Fix MWImageModel's getImageNodeType()
+
+https://gerrit.wikimedia.org/r/134554",1400644951,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","(In reply to Moriel Schottlender from comment #3)
+> Most times, we can't trust the node.getType() because changes in the model
+> changes the node's type -- that's what the model's test was for.
+> 
+Well, you can most certainly trust node.getType() to tell you if calling node.getCaptionNode() will cause it to explode or not, and you apparently can't trust imgModel.getImageNodeType() in this case ;)
+
+> It should, however, not lie or make mistakes. This is going to be somewhat
+> complex, since wikitext's way of transforming between inline/block can be
+> extremely arbitrary-looking.
+> 
+Yeah, it should be improved, but if it makes mistakes the consequences shouldn't be /this/ bad.
+
+> One more thing that we could do, however, is use node.getType() whenever
+> that *can* be trusted. This means that on loading the node (like in this
+> bug) the node's type can be used, and same with after inserting a new node.
+> 
+Yes, exactly.
+
+> In the other cases, though (like checking whether we're going to change a
+> node type or just change the attributes) the node.getType() won't help us,
+> we'll have to use a custom test inside the model to check.
+Yup, that sounds reasonable. However, we'd also have to define what happens when we inspect a node whose type appears to be ""wrong""; we probably shouldn't change its type if the user didn't change any of the flags. OTOH, this just shouldn't happen.",1400643505,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Most times, we can't trust the node.getType() because changes in the model changes the node's type -- that's what the model's test was for.
+
+It should, however, not lie or make mistakes. This is going to be somewhat complex, since wikitext's way of transforming between inline/block can be extremely arbitrary-looking.
+
+One more thing that we could do, however, is use node.getType() whenever that *can* be trusted. This means that on loading the node (like in this bug) the node's type can be used, and same with after inserting a new node.
+
+In the other cases, though (like checking whether we're going to change a node type or just change the attributes) the node.getType() won't help us, we'll have to use a custom test inside the model to check.",1400643101,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","This happens because imgModel.getImageNodeType() returns 'mwBlockImage', but the actual node is an inline image.
+
+So 1) we shouldn't base decisions on what to do with the node object on the image model's opinion of what class the node should be, 2) that opinion should be used in very very few places, everywhere else we should be using node.getType() and 3) the image model's opinion should not be wrong :)",1400639573,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears","Example page 1: The first image on:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_%28WMF%29&veaction=edit
+
+Example Page 2: The first image on:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=20thmaychrome&veaction=edit",1400632439,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c6jr2jdyjmcydtgy4pr7,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Steps to reproduce:
+
+1.Open a page with VE 
+2.Insert an image 
+3.Change the Image type to ""Frame""
+4.Click on ""Apply changes""
+5.Reopen the media settings dialog
+
+Observed Result:
+Though the image is on the right , the alignment is set to Left on the Media Settings dialog, and if you click on ""Apply Changes"" button now, it will move the image to left
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400626920,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_description,resolved
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",Verified the fix in en.wiki running wmf 8,1402687364,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",Verified the fix in test2,1402342746,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",Verified the fix in Betalabs,1401928680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 136971 merged by jenkins-bot:
+Adjust default alignment when switching from inline to block
+
+https://gerrit.wikimedia.org/r/136971",1401921428,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 136971 had a related patch set uploaded by Mooeypoo:
+Adjust default alignment when switching from inline to block
+
+https://gerrit.wikimedia.org/r/136971",1401769554,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","This issue still happening but the behavior got slightly changed.Previouslt after changing the alignment of any image types to ""Left"" and then reopening the Media Settings dialog was setting the alignment as ""Right"" , even though it was still on the left.Now the same issue happens but you need to save the page first after changing the alignment to left and then reopen the media settings dialog to see it.
+
+So the new steps to reproduce is:
+
+1.Insert any type of image
+2.Change the alignment to left
+3.Click on ""Apply Changes""
+4.Click on ""Save Page""
+5.Reopen the page
+6.Reopen the Media Settings dialog>Advanced Settings
+
+Observed Result:
+The alignment tab is set to ""Right""",1401398771,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 135699 merged by jenkins-bot:
+Another default alignment fix to MWImageModel
+
+https://gerrit.wikimedia.org/r/135699",1401315123,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 135699 had a related patch set uploaded by Mooeypoo:
+Another default alignment fix to MWImageModel
+
+https://gerrit.wikimedia.org/r/135699",1401311231,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",This is happening for all image types now in Betalabs.,1401225328,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Yes, that's intended. This happens to images that have default alignment; default in a block image is opposite the text direction (""right"" in ltr) and default for inline images, which is what the basic change does, is with text direction (""left"" in ltr).
+
+This is intended.",1400705854,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Right now, when you add an image and make it basic and select Right alignment, it moves it to the left and sets alignment as ""Left"".",1400705274,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 134660 merged by jenkins-bot:
+Don't update image model twice
+
+https://gerrit.wikimedia.org/r/134660",1400700237,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","Change 134660 had a related patch set uploaded by Mooeypoo:
+Don't update image model twice
+
+https://gerrit.wikimedia.org/r/134660",1400697863,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",This issue is still occurring for image type Basic.,1400696553,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save","The issue of default alignment between inline and block is more complex than I initially thought. I made an additional fix to this behavior in this commit https://gerrit.wikimedia.org/r/#/c/134554/ (which is merged now)
+
+This should fix the current bug as well (it did on my tests locally, but please verify)
+
+I hope no more default-alignment problems pop up.",1400652437,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save",The same issue appears when you change the Image type to Basic too,1400628181,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x74esizqbmiiw7nhiogh,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make an edit
+3.Click on ""Switch to source editing ""
+4.Click on ""No, cancel""
+5.Now click on the ""Cancel"" button of the editor 
+6.Click on ""Continue Editing""
+7.Now again go to """"Switch to source editing ""
+8.This time click on ""Yes, switch""
+
+Observed Result:
+It does not switch to edit source mode and throws the following errors in the console:
+
+
+Uncaught TypeError: Cannot read property 'css' of null and 
+Uncaught TypeError: Cannot read property 'each' of null 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13495}",1400622660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-42zzbjl2eh4mv5xecel6,task_description,resolved
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,Verified the fix in production.,1401392334,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,Verified the fix on test 2,1400808693,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,Verified the fix in Betalabs,1400701590,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"Change 134546 merged by jenkins-bot:
+Unbind confirm dialog handlers after either of the events fires once
+
+https://gerrit.wikimedia.org/r/134546",1400680518,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"Change 134546 had a related patch set uploaded by Catrope:
+Unbind confirm dialog handlers after either of the events fires once
+
+https://gerrit.wikimedia.org/r/134546",1400638427,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"(In reply to Roan Kattouw from comment #1)
+> Holy crap this is an obscure bug. Steps 3 and 4 (switching to source mode
+> the first time) can be skipped, but other than that every step is necessary.
+> 
+As Rummana points out, the second error (with 'each') does not occur if you skip those steps, so there's something else going on too. There's some code in ViewPageTarget that gets run after this.$checkboxes has been cleared.
+
+On second inspection, there's a lot more going on. For instance, the 'ok' handler executes twice, and so we attempt to serialize twice.",1400638052,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case,"Holy crap this is an obscure bug. Steps 3 and 4 (switching to source mode the first time) can be skipped, but other than that every step is necessary.
+
+This happens because the switch to source mode button and the cancel button share the same instance of the confirmation dialog. When you click OK in the source mode one, the cancel button code is still listening to the 'ok' event; we need to disconnect that on cancel.
+
+Perhaps it would be nicer if these two were combined into one event so we could use .once() and not have to unbind explicitly.",1400625140,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-42zzbjl2eh4mv5xecel6,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,"Bug 50047 and bug 51918 have regressed for Firefox – possibly as a result of Ed's changes to how the buttons work? Yay for Firefox and its attitude to tab indexes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66824",1400619540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lgy5g6voka2ep73yf275,task_description,resolved
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,*** Bug 67153 has been marked as a duplicate of this bug. ***,1404848147,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,Well that's at least a workaround. I wonder if this might be an upstream bug...,1404152488,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,"Change 143055 merged by jenkins-bot:
+Set tabindex on button <div> instead of <a>
+
+https://gerrit.wikimedia.org/r/143055",1404152364,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,"Change 143055 had a related patch set uploaded by Alex Monk:
+Set tabindex on button <div> instead of <a>
+
+https://gerrit.wikimedia.org/r/143055",1404148906,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,"So adding this.reviewButton.$element.attr( 'tabindex', '0' ).find( 'a' ).removeAttr( 'tabindex' ); fixed this... Wtf firefox?",1404147725,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox,Looks like the same issue as bug 66824,1404147095,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-lgy5g6voka2ep73yf275,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the link inspector : insert [http://yahoo.com]
+3.Apply the link
+4.Save the page
+
+Observed Result:
+The link appears inside VE with single brackets around it: [http://yahoo.com]
+And when you save the page, the unicode for the ending single bracket appears at the end of the link as a part of that link:[http://yahoo.com&#x5D;
+
+Expected Result:
+The link inspector should say to user that it is an invalid external link format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13473}",1400614080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vdj2elhgawonhfvz6sns,task_description,resolved
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"Change 139128 merged by jenkins-bot:
+Wrap external URL protocols regex in brackets.
+
+https://gerrit.wikimedia.org/r/139128",1402592717,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,I don't think so. I think things including the wgUrlProtocols regex should be dealing with this issue themselves.,1402590530,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,Do we need to upstream a fix for wgUrlProtocols?,1402590080,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"Change 139128 had a related patch set uploaded by Alex Monk:
+Wrap external URL protocols regex in brackets.
+
+https://gerrit.wikimedia.org/r/139128",1402589216,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"Currently, the regex looks something like this (based on wgUrlProtocols):
+
+/^bitcoin\:|ftp\:\/\/|ftps\:\/\/|geo\:|git\:\/\/|gopher\:\/\/|http\:\/\/|https\:\/\/|irc\:\/\/|ircs\:\/\/|magnet\:|mailto\:|mms\:\/\/|news\:|nntp\:\/\/|redis\:\/\/|sftp\:\/\/|sip\:|sips\:|sms\:|ssh\:\/\/|svn\:\/\/|tel\:|telnet\:\/\/|urn\:|worldwind\:\/\/|xmpp\:|\/\//
+
+Notice the '^' is only against 'bitcoin' and not any other protocol? Yeah I think we need to wrap everything after the '^' in brackets.",1402589191,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,Is our regex not anchored to the start of the string somehow?,1402549443,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector,"
+note that the wikitext for the saved string reads: 
+
+&#x5Dhttp://yahoo.com&#x5D;",1400615575,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-vdj2elhgawonhfvz6sns,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Language
+3.Now click on ""Find Language"" button
+
+Observed Result:
+
+The language selector dialog box takes a long time to load, approx. 15 secs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66124",1400540520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_description,resolved
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,Verified the fix in production (en.wiki),1403300505,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,Verified the fix in test2 running wmf 9,1402704938,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,Verified the fix in Betalabs,1402354271,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Change 137741 merged by jenkins-bot:
+GroupElement: Improve performance by avoiding .add() overhead
+
+https://gerrit.wikimedia.org/r/137741",1402349469,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Change 137736 merged by jenkins-bot:
+Use this.$() in LanguageResultWidget#highlightQuery
+
+https://gerrit.wikimedia.org/r/137736",1402041593,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"These two patches get it down to 780ms on my computer. This breaks down in about 520ms for opening the dialog (including constructing all of the language entries), and 260ms for displaying the ""search result"" for an empty search bar. The latter is repeated every time you empty the search bar (press backspace when one character is left), which is noticeably laggy. That mostly has to do with the search query highlighting code (that's about 200ms of it), which needs to be optimized further. The dialog opening is also a bit slower than I'd like, but at least isn't as critical as responding quickly when the user presses backspace.
+
+To be fair, without these patches, it's 520ms for opening the dialog (unchanged), and 14 seconds to display an empty search result (12 seconds for adding results, 2 seconds for highlighting), so this is already a pretty good improvement :)",1402008214,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Change 137741 had a related patch set uploaded by Catrope:
+Fix GroupElement performance
+
+https://gerrit.wikimedia.org/r/137741",1401997608,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"Change 137736 had a related patch set uploaded by Catrope:
+Use this.$() in LanguageResultWidget#highlightQuery
+
+https://gerrit.wikimedia.org/r/137736",1401995364,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"(Additional information from the duplicate bug)
+
+The slowness also means the user can click somewhere on the screen to close the language inspector while the language list loads; it seems to allow the user to choose a language, but since the inspector is already closed, the chosen language isn't updated properly.",1401898887,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,*** Bug 66124 has been marked as a duplicate of this bug. ***,1401898213,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load,"In Firefox, it is comparatively faster than Chrome",1400540731,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2riepmcawlf54gdgu2o,task_subcomment,NA
+VisualEditor: Category autocompletion is broken in RTL wikis,"a screenshot with the problem
+
+To reproduce:
+
+1. Edit an article in the Hebrew Wikipedia using VE.
+2. Go to the categories dialog.
+3. Start typing a category name.
+
+Expected: autocompletion list appears under the input box.
+Actual: autocompletion list appears to the side of the input box.
+
+See screenshot.
+
+This is similar to Bug 51490.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13994}",1400505240,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dnopciwdieirbov75q2y,task_description,resolved
+VisualEditor: Category autocompletion is broken in RTL wikis,"Change 138041 merged by jenkins-bot:
+Correct TextInputMenuWidget position for RTL
+
+https://gerrit.wikimedia.org/r/138041",1402098125,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dnopciwdieirbov75q2y,task_subcomment,NA
+VisualEditor: Category autocompletion is broken in RTL wikis,"Change 138041 had a related patch set uploaded by Mooeypoo:
+[wip] Correct TextInputMenuWidget position for RTL
+
+https://gerrit.wikimedia.org/r/138041",1402089868,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dnopciwdieirbov75q2y,task_subcomment,NA
+VisualEditor: Save dialog's request for checkboxes should respect the uselang param,"There is content in pt-BR after setting ""uselang=en""
+
+See the screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13936}",1400420160,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ftg6xmbgjlpqhszufc2t,task_description,resolved
+VisualEditor: Save dialog's request for checkboxes should respect the uselang param,"Change 138407 merged by jenkins-bot:
+Send language when making API requests
+
+https://gerrit.wikimedia.org/r/138407",1402347137,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftg6xmbgjlpqhszufc2t,task_subcomment,NA
+VisualEditor: Save dialog's request for checkboxes should respect the uselang param,"Change 138407 had a related patch set uploaded by Alex Monk:
+Send language when making API requests
+
+https://gerrit.wikimedia.org/r/138407",1402343419,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftg6xmbgjlpqhszufc2t,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,"ve.ce.Surface uses $.browser to do paste special casing; replace or remove this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400259180,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pemezhinhwcmsjmxrgcv,task_description,resolved
+VisualEditor: Remove use of jQuery.browser,"Change 136036 merged by jenkins-bot:
+Remove last jQuery.browser uses with temporary ve.isMsie hack
+
+https://gerrit.wikimedia.org/r/136036",1401390951,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,Thanks Ed!,1401390896,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,"Change 136036 had a related patch set uploaded by Krinkle:
+Remove last jQuery.browser uses with temporary ve.isMsie hack
+
+https://gerrit.wikimedia.org/r/136036",1401380354,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,Still one use in ve.ce.Surface.,1401380304,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,"Change 132431 merged by jenkins-bot:
+Remove IE check (and possible compatibility) from beforepaste/paste event switch
+
+https://gerrit.wikimedia.org/r/132431",1400895485,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+VisualEditor: Remove use of jQuery.browser,"Change 132431 had a related patch set uploaded by Jforrester:
+[WIP] Remove IE check from beforepaste/paste event switch
+
+https://gerrit.wikimedia.org/r/132431",1400259251,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pemezhinhwcmsjmxrgcv,task_subcomment,NA
+OOjs UI: Need a way to add a non-functional label to the top of a popupToolGroup (within the popup),"See design mock-up at https://trello.com/c/xCo6uLAZ/9-5-references-dropdown-from-toolbar-styling.
+
+Right now, I can give a popupToolGroup a label by using the 'label' param in a toolbarGroup definition:
+{
+    'label': 'Cite',
+    'type': 'list',
+    'icon': 'reference',
+    'title': OO.ui.deferMsg( 'visualeditor-toolbar-cite-label' ),
+    'include': [ { 'group': 'cite' } ]
+}
+
+However, this puts the label above the popup (in the popupToolGroup-handle) rather than within the popup itself (as needed by the design linked to above).
+
+I can imagine two different ways of providing this functionality:
+
+1. Add a new type of param for toolbarGroups called something like 'inner-label'
+
+2. Allow creating non-functional labels from the on-wiki group definition, for example:
+[
+    { ""label"": ""cite"" },
+    { ""name"": ""web"", ""icon"": ""ref-cite-web"", ""template"": ""Cite web"" },
+    { ""name"": ""book"", ""icon"": ""ref-cite-book"", ""template"": ""Cite book"" },
+    { ""name"": ""news"", ""icon"": ""ref-cite-news"", ""template"": ""Cite news"" },
+    { ""name"": ""journal"", ""icon"": ""ref-cite-journal"", ""template"": ""Cite journal"" }
+]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400194680,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-lpehn2gbooedlcmnbnt4,task_description,resolved
+OOjs UI: Need a way to add a non-functional label to the top of a popupToolGroup (within the popup),Fixed by https://gerrit.wikimedia.org/r/#/c/134237/,1402081686,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-lpehn2gbooedlcmnbnt4,task_subcomment,NA
+OOjs UI: Need a way to add a non-functional label to the top of a popupToolGroup (within the popup),I would recommend option 1.,1400274032,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-lpehn2gbooedlcmnbnt4,task_subcomment,NA
+OOjs UI: Need a way to add a non-functional label to the top of a popupToolGroup (within the popup),After discussing with Trevor we decided the best way to implement this would be to have a parameter like 'label-position' which controls where the label appears.,1400273880,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-lpehn2gbooedlcmnbnt4,task_subcomment,NA
+VisualEditor: Transclusion content blocks don't auto-expand in Firefox,"Probably the same issue as we had for parameter fields?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400178360,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cxvk42p4teyvew3duhd3,task_description,duplicate
+VisualEditor: Blue link / red link logic should descend into links inside generated content nodes,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400178120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zfbsov36z6srqhbwgabt,task_description,resolved
+VisualEditor: Blue link / red link logic should descend into links inside generated content nodes,"Bah.
+
+*** This bug has been marked as a duplicate of bug 65353 ***",1400178184,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zfbsov36z6srqhbwgabt,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"Redlinks are displayed as blue links in templates inside the VisualEditor
+
+
+https://en.wikipedia.org/wiki/Javier_Payo?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400177400,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-4sbnoqmt6akkxouhu25v,task_description,resolved
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"(In reply to Alex Monk from comment #7)
+> Well, it was you who changed this bug from being about just templates to
+> being about ""generated content nodes (e.g. templates)""... We can just make
+> it about templates only again if you want.
+
+Created that as bug 71900.",1412891280,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"Well, it was you who changed this bug from being about just templates to being about ""generated content nodes (e.g. templates)""... We can just make it about templates only again if you want.",1412791547,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"(In reply to Alex Monk from comment #5)
+> Transclusion nodes are not the only generated content nodes
+
+They are, however, almost exclusively the GCNs with wikitext links in them. Do we actually care about <easytimeline> blocks?",1412791246,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,Transclusion nodes are not the only generated content nodes,1412787503,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"Change 165240 merged by jenkins-bot:
+Apply link styling logic to transclusion nodes
+
+https://gerrit.wikimedia.org/r/165240",1412778604,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"Change 165240 had a related patch set uploaded by Alex Monk:
+Apply link styling logic to transclusion nodes
+
+https://gerrit.wikimedia.org/r/165240",1412712151,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,"We used to parse template content with action=parse from the PHP parser which naturally contained <a class=""new"">.
+
+Nowadays we use Parsoid for the generated fragments as well, but this meant we lost the natural classes MediaWiki provided.
+
+The mw.LinkCache logic should extend to the nodes inside generated content.
+
+I think right now this isn't done because we use the same DOM for both the DM and the CE of generated content nodes, but, just as we do for practically everything else, it shouldn't be an issue to have our copy in CE be different from the copy in DM (thus not having to worry about needing to strip any classes when saving back to Parsoid).",1411593819,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside transclusions,*** Bug 65355 has been marked as a duplicate of this bug. ***,1400178184,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4sbnoqmt6akkxouhu25v,task_subcomment,NA
+VisualEditor: On saving a page in the File: namespace the file preview is not reshown (until reload),"After saving an edit in the file namespace the big thumbnail of the file is not shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400164080,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-fclmxs3oedf5jio2gq6g,task_description,resolved
+VisualEditor: On saving a page in the File: namespace the file preview is not reshown (until reload),"Change 133897 merged by jenkins-bot:
+On file pages, only replace the (local) image description when saving
+
+https://gerrit.wikimedia.org/r/133897",1400521871,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fclmxs3oedf5jio2gq6g,task_subcomment,NA
+VisualEditor: On saving a page in the File: namespace the file preview is not reshown (until reload),"Change 133897 had a related patch set uploaded by Alex Monk:
+On file pages, only replace the (local) image description when saving
+
+https://gerrit.wikimedia.org/r/133897",1400346229,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fclmxs3oedf5jio2gq6g,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"1. Edit some text (e.g the -> foo)
+1. Edit existing link (e.g. on [[mw:VisualEditor]], link to ""Parsoid"")
+2. Enter text that makes up part of a title (e.g. ""ResourceLoade"", note, the missing ""r"" at the end)
+3. Select ""ResourceLoader"" from the suggestions
+   (due to a bug in our search engine, this is the second suggestion, not the first:
+   [ > ResourceLoade                                 ]
+     - ResourceLoader/JavaScript Deprecations
+     - ResourceLoader
+     - ResourceLoader/Version 1 Design Specification
+
+4. Observe that the suggestions close after selecting an item, and the text field now contains ""ResourceLoader"". Do not press enter or click anywhere.
+
+5. Press Save Page
+
+Video: http://cl.ly/11431q402d3A
+
+Expected:
+
+* Diff shows ""the -> foo"", and ""Parsoid -> ResourceLoader"".
+
+
+Actual:
+
+* Diff shows ""the -> foo"".
+
+Because:
+
+We both selected a value from the suggestions and then blurred the inspector by clicking ""Save page"". Either of those actions ought to save the value into the model, but doing both certainly should.
+
+There are two weird things about this:
+
+* Changing step 4 and pressing Enter there instead of Save page, makes it save correctly.
+
+So it seems that we just don't save properly on selection or blurring and require one of Escape-key, Enter-key, Back-button or focussing surface (instead of blurring inspector / focussing anything in the main window, e.g. toolbar / save button as well, not just surface).
+
+* Changing step 2/3 to type ""ResourceLoader"" straight up, and not pressing Enter or clicking anywhere before clicking Save page also works. 
+
+So it seems that merely changing focus from input field to save page can be enough to have it saved. Maybe we have an exception for onkeyup/onchange and select is bypassing that?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1400155260,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-j7kkjkivstfcbdtgopcv,task_description,resolved
+VisualEditor: Link inspector ignores selected value,*** Bug 68934 has been marked as a duplicate of this bug. ***,1408668143,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Change 155673 merged by jenkins-bot:
+Select the correct annotation in MWLinkTargetInputWidget
+
+https://gerrit.wikimedia.org/r/155673",1408666534,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Change 155673 had a related patch set uploaded by Catrope:
+Select the correct annotation in MWLinkTargetInputWidget
+
+https://gerrit.wikimedia.org/r/155673",1408666195,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,*** Bug 68934 has been marked as a duplicate of this bug. ***,1408666007,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Following the steps exactly as per comment #0 still exhibits this bug exactly.
+
+I can reproduce it locally on latest master by making a link to User:Root when typing ""User:Ro"" where the suggestions are [ ""User:Root/common.js"", ""User:Root"" ].",1403713144,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Change 138114 merged by jenkins-bot:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533850,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor: Link inspector ignores selected value,"Change 138114 had a related patch set uploaded by Catrope:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533460,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j7kkjkivstfcbdtgopcv,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"Steps to reproduce:
+
+1.Open a page with VE that has link inside it.
+2.Tap on any link 
+
+Observed Result:
+The browser page gets redirected to the link target page
+
+Test Environment: https://en.m.wikipedia.org/
+Device: iPad Mini
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66999
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67002
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67063",1400114400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_description,resolved
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Verified the fix in production,1405026344,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Verified the fix in test2,1404774327,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Verified the fix in Betalabs,1404261101,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"Change 143152 merged by jenkins-bot:
+Prevent iOS Safari from following links
+
+https://gerrit.wikimedia.org/r/143152",1404243362,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"Change 143152 had a related patch set uploaded by Esanders:
+Prevent iOS Safari from following links
+
+https://gerrit.wikimedia.org/r/143152",1404162008,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"(In reply to Ed Sanders from comment #8)
+> We don't even have event listeners on links at the moment but we might have to
+> add some as a work around
+
+Eww. If we do, let's keep it as local as possible (mobile-only, for instance).",1404160763,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Links don't have any custom highlights (and shields no longer exist) so this must just be a CE bug in iOS (should be filed upstream if possible). We don't even have event listeners on links at the moment but we might have to add some as a work around,1404160696,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,did not get*,1403895079,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"This bug did not resolved by :
+
+FocusableNode: Use getClientRects()[0] instead of getBoundingClientRect()
+
+https://gerrit.wikimedia.org/r/142260",1403895048,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"**jgonera** wrote:
+
+%%%*** Bug 66559 has been marked as a duplicate of this bug. ***%%%",1403652268,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,Pushing to Ed because it appears to be a shield/highlight issue.,1403573090,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"**jgonera** wrote:
+
+Jon has never worked on this bug.",1403560880,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"**jgonera** wrote:
+
+Link is followed (kind of)
+
+**Attached**: {F13597}",1403559841,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden,"**jgonera** wrote:
+
+This bug happens on any iOS Safari probably. The link doesn't seem to go to the destination in some cases (in my dev instance it goes to 127.0.0.1 even though I loaded the page from an external IP).
+
+More importantly, this seems to be happening only when the keyboard is hidden (contenteditable is not focused). See attached video.
+
+I tested it on iOS 7.1.1. It doesn't happen on Chrome for Android.",1403559813,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dpdpa5liabymg7w2g4yy,task_subcomment,NA
+VisualEditor: Use $.when() rather than sourceCount in MediaSearchWidget,"See inline comment on https://gerrit.wikimedia.org/r/#/c/133050/1/modules/ve-mw/ui/widgets/ve.ui.MWMediaSearchWidget.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400108760,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-b73qbgwpj2jg4avkkdnb,task_description,resolved
+VisualEditor: Use $.when() rather than sourceCount in MediaSearchWidget,"Change 150001 merged by jenkins-bot:
+Use $.when() in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/150001",1406787242,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b73qbgwpj2jg4avkkdnb,task_subcomment,NA
+VisualEditor: Use $.when() rather than sourceCount in MediaSearchWidget,"Change 150001 had a related patch set uploaded by Mooeypoo:
+Use to $.when() in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/150001",1406575990,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b73qbgwpj2jg4avkkdnb,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Go to this page:http://en.wikipedia.beta.wmflabs.org/wiki/14thmaychrome?veaction=edit
+2.Select the image on the page
+3.Go to Media Settings>Advanced Settings>Image Size
+4.Change the tab from Default to custom or Custom to Default
+
+Observed Result:
+
+The ""Make full size"" button remains disabled for the image
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13562}",1400101140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_description,resolved
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,Verified the fix in production,1400794773,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,Verified the fix in test2,1400268218,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,Verified the fix in Betalabs,1400202274,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,"Change 133384 merged by jenkins-bot:
+Revert ""Cache image scalable promises by filename""
+
+https://gerrit.wikimedia.org/r/133384",1400108201,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,"Change 133384 had a related patch set uploaded by Catrope:
+Revert ""Cache image scalable promises by filename""
+
+https://gerrit.wikimedia.org/r/133384",1400108090,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,It seems likely that this is due to cache pollution of the promise cache introduced in https://gerrit.wikimedia.org/r/#/c/132207/4/modules/ve-mw/dm/nodes/ve.dm.MWImageNode.js . The bug only happens when saving then reopening the editor in the same session without navigating away.,1400107759,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs,"Found the steps to reproduce:
+
+1.Insert any image
+2.Go to Media Settings>Advanced Settings
+3.Select Custom tab and change the values
+4.Apply changes
+5.Save the page
+6.Reopen the page
+7.Go to the Media Settings>Advanced Settings of that image again
+
+Observed Result:
+The ""Make full size"" button became disabled ,switching tabs/changing values again does not make it enabled anymore.",1400106941,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x4lxm7vnk37zcqajzk5r,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,"Screenshot
+
+Steps to reproduce:
+
+1.Go to this page:http://en.wikipedia.beta.wmflabs.org/wiki/12thmayff?veaction=edit
+
+2.Select the first image on the page: Dau_ho_thoi_Ho.png
+
+3.Make any edit on the image's caption field
+
+4.Click on ""Apply Changes""
+
+Observed Result:
+
+The Media Settings dialog does not get closed , the edit does not get saved
+
+The following error appears in the console:
+
+
+TypeError: originalDimensions is undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13995}",1399925160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_description,resolved
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,Verified the fix in production,1400794643,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,Verified the fix in test2,1400269461,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,Verified the fix in Betalabs,1400014154,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,"Change 133123 merged by jenkins-bot:
+Make sure originalDimensions are available before use
+
+https://gerrit.wikimedia.org/r/133123",1400011867,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,"Change 133123 had a related patch set uploaded by Mooeypoo:
+Make sure originalDimensions are available before use
+
+https://gerrit.wikimedia.org/r/133123",1400010908,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,For Chrome the error appearing is a bit different:Uncaught TypeError: Cannot read property 'width' of undefined,1399932675,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image,"The following steps ensure reproducing the issue for all images:
+
+1.Insert a new image in a page and save the page
+2.Reopen the page and go to the Advanced Settings of the image
+3.Click on custom tab and click on Apply Changes
+4.Save the page
+5.Reopen the page and again go the Advanced Settings of the image
+6.Click on Default tab and click on Apply changes
+
+You will see the error and get stuck inside the media settings dialog box",1399928696,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zz6pjwdovfpej7nnkvlg,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"Earlier today, the toolbar in VisualEditor stopped displaying ""Cite"" on the new citation tool, and instead started displaying ""<visualeditor-toolbar-cite-label>"".  
+
+For me, it displayed correctly until I changed languages to qqx to check something else; when I went back, it was broken.  For James F, it was displaying correctly until he logged out.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66543",1399917120,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-xph2545wogpg3ilxwqvv,task_description,duplicate
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"(In reply to Antoine ""hashar"" Musso from comment #4)
+> I tried to reproduce the issue with:
+> 
+>  eaction=edit&uselang=en
+>  eaction=edit&uselang=qqx
+>  eaction=edit
+> 
+> The Cite label in the toolbar was back to normal.
+
+Indeed; a null edit to the message page brought it back into the l10n cache.
+
+> Could it be that whenever that new Cite function got added the l10n cache
+> did not get regenerated?   Without a way to reproduce it there is not much
+> we can do unfortunately.
+
+No. It was added in 1.23wmf20. It is very unlikely that the l10n cache having suddenly broken on Monday night was caused by a deploy two months ago. :-)",1399997338,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"I tried to reproduce the issue with:
+
+ eaction=edit&uselang=en
+ eaction=edit&uselang=qqx
+ eaction=edit
+
+The Cite label in the toolbar was back to normal.
+
+
+Could it be that whenever that new Cite function got added the l10n cache did not get regenerated?   Without a way to reproduce it there is not much we can do unfortunately.",1399986128,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"(In reply to Andre Klapper from comment #2)
+> Only in VisualEditor strings, or also other places been seen?
+
+So far I've only seen it for this particular VE-related message, but the fun thing with deployment bugs is you never know…",1399927904,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"Only in VisualEditor strings, or also other places been seen?",1399923681,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels,"As a note, it was fixed by me making a null edit to [[MediaWiki:visualeditor-toolbar-cite-label]]. Apparently the same breakage (in pl rather than en) was experienced on plwiki earlier as well.",1399917463,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xph2545wogpg3ilxwqvv,task_subcomment,NA
+VisualEditor: Automatically place cursor in edit summary field,"TeamGale doesn't recall that in order to fill the edit summary field you need to click on that first - if she doesn't, the text she's typing, although the dialog is visible, ends up in the article instead (FF29, Win8).
+
+If I hit Save changes in any of my browsers (Chrome, FF and Opera) and don't click on the dialog, nothing happens if I keep typing.
+However I believe that if it is technically possible, the extra click shouldn't happen, there are no other places where the cursor should end up, and editors seeing it flashing might be encouraged to use the field a little more.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64521",1399906920,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-kvdc2sbtbd6agc4wdbbt,task_description,resolved
+VisualEditor: Automatically place cursor in edit summary field,*** Bug 64521 has been marked as a duplicate of this bug. ***,1401996489,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kvdc2sbtbd6agc4wdbbt,task_subcomment,NA
+VisualEditor: Automatically place cursor in edit summary field,"Change 134108 merged by jenkins-bot:
+Initialise save panel on 'ready' so focus works
+
+https://gerrit.wikimedia.org/r/134108",1400521769,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-kvdc2sbtbd6agc4wdbbt,task_subcomment,NA
+VisualEditor: Automatically place cursor in edit summary field,"Change 134108 had a related patch set uploaded by Esanders:
+Initialise save panel on 'ready' so focus works
+
+https://gerrit.wikimedia.org/r/134108",1400516649,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-kvdc2sbtbd6agc4wdbbt,task_subcomment,NA
+VisualEditor Mobile: Cannot save any page on production after an edit with mobile VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open any page with Mobile VE 
+2.Make some Edit
+3.Attempt to save the page
+
+Observed Result:
+The Page cannot be saved, the spinner does not go away from the page.
+The following error appears in the console:
+TypeError: s is undefined
+	
+
+...unction(s){return s.replace(/['""<>&]/g,escapeCallback);},element:function(name,a...
+
+load.p...203716Z (line 168)
+
+See the screenshot attached
+
+Found on this page: https://en.m.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13680}",1399673700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oz5jjuc4evheyckkxa75,task_description,resolved
+VisualEditor Mobile: Cannot save any page on production after an edit with mobile VE,This issue got fixed after the wmf 4 deployment to production.Marking as fixed and verified .,1400191988,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oz5jjuc4evheyckkxa75,task_subcomment,NA
+VisualEditor Mobile: Cannot save any page on production after an edit with mobile VE,It works on beta labs so I would suspect that this is an issue that got caught and will be fixed in next deployment... unless beta labs and enwiki differ in any way?,1400090712,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-oz5jjuc4evheyckkxa75,task_subcomment,NA
+VisualEditor Mobile: Cannot save any page on production after an edit with mobile VE,"In chrome,the error that appears in the console while saving a page is:
+
+
+Uncaught TypeError: Cannot read property 'replace' of undefined 
+
+However,if you refresh the page , you will see the edit does get saved on the page",1399938958,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oz5jjuc4evheyckkxa75,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,"in ve.ce.Surface we the following line:
+
+ if ( $.browser.msie === true && e.which === 229 ) {
+
+Give we haven't tested IE in so longer I suspect this might not work anymore, but if it does, we need another way to detect that this hack is needed as $.browser is deprecated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399649400,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cxvaopbhevdikka45q3y,task_description,resolved
+VisualEditor: IME detection should not use useragent sniffing,Was fixed by https://gerrit.wikimedia.org/r/#/c/141457 .,1414059000,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,"Rephrasing to be the bug David wants to work on in general.
+
+For the literal usage of $.browser, see bug 65404.",1401380341,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,Bumping priority as this needs to be done very soon…,1401380159,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,It needs to not use $.browser within 2 weeks tops.,1400512997,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+VisualEditor: IME detection should not use useragent sniffing,"I'm in the process of stripping these checks out anyway, because the inIme checks cannot be made realiable. Does this need removing immediately? If so I can submit a smaller patch that does this.",1400512916,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-cxvaopbhevdikka45q3y,task_subcomment,NA
+"VisualEditor: Link icon in menu shown as ""selected"" (but only if link was created this session?)","Screenshot showing link vs. formula icon to highlight difference
+
+It's possible to get a link inspector icon shown as ""selected"" in the inspector menu, which is… confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14013}",1399416300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dobpoqvld4np3b5yv3hj,task_description,resolved
+"VisualEditor: Link icon in menu shown as ""selected"" (but only if link was created this session?)",This was fixed a while ago with the new context.,1406756218,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dobpoqvld4np3b5yv3hj,task_subcomment,NA
+VisualEditor: CTRL+A in Firefox creates a selection starting at 0 and ending after the document node,"Selections at non-content offsets are bad, e.g. pressing delete will throw an exception.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399324080,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rj2zoft2yh74cpk6h2y7,task_description,resolved
+VisualEditor: CTRL+A in Firefox creates a selection starting at 0 and ending after the document node,*** Bug 57355 has been marked as a duplicate of this bug. ***,1399642730,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rj2zoft2yh74cpk6h2y7,task_subcomment,NA
+VisualEditor: CTRL+A in Firefox creates a selection starting at 0 and ending after the document node,"Change 131688 merged by jenkins-bot:
+Special case for deleting the entire document
+
+https://gerrit.wikimedia.org/r/131688",1399626382,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rj2zoft2yh74cpk6h2y7,task_subcomment,NA
+VisualEditor: CTRL+A in Firefox creates a selection starting at 0 and ending after the document node,"Change 131688 had a related patch set uploaded by Esanders:
+Special case for deleting the entire document
+
+https://gerrit.wikimedia.org/r/131688",1399379110,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rj2zoft2yh74cpk6h2y7,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Type something to search a media file
+
+Observed Result:
+When the search results appear observe that there is an extra empty column appearing at the right end in the search result dialog box.
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64808
+
+**Attached**: {F13839}",1399314000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zwqtfztcfyrexovbyarr,task_description,resolved
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row",Verified the fix in en.wiki running wmf8,1402685612,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row",Verified the fix in Betalabs and test2,1402343157,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Change 136314 merged by jenkins-bot:
+Change padding on media search results so we can display 4 results on a row with a scrollbar
+
+https://gerrit.wikimedia.org/r/136314",1401925013,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Change 136314 had a related patch set uploaded by Alex Monk:
+Change padding on media search results so we can display 4 results on a row with a scrollbar
+
+https://gerrit.wikimedia.org/r/136314",1401456799,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row",Re-phrasing title based on feedback from Roan.,1401401408,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","This is still happening for me, when I always have scroll bar showing on MAC OS",1399331340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Change 131516 merged by jenkins-bot:
+Remove unnecessary space in footless dialog
+
+https://gerrit.wikimedia.org/r/131516",1399315979,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+"VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row","Change 131516 had a related patch set uploaded by JGonera:
+Remove unnecessary space in footless dialog
+
+https://gerrit.wikimedia.org/r/131516",1399315766,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zwqtfztcfyrexovbyarr,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"**Author:** `b.coughlan2`
+
+**Description:**
+Tested on MW 1.22.6 with stable snapshot of VisualEditor, but looking at the master branches I'm quite sure that this still applies.
+
+Steps to reproduce
+==================
+
+1. Set wiki to have read access only for users:
+
+   $wgGroupPermissions['*']['read'] = false;
+   $wgGroupPermissions['user']['read'] = true;
+
+   Note that if testing on local environment, you will have to first open VE with the 'Edit' button, so that Parsoid is not locked out by this configuration.
+
+2. Open the 'Media' button in the VE toolbar and search for something.
+3. The AJAX request will return 'readapidenied', because it won't recognise the user credentials.
+
+
+Cause
+=====
+
+ve.ui.MWMediaSearchWidget.js makes a JSONP request to the localhost. However, MediaWiki's ApiMain.php:180 (https://git.wikimedia.org/blob/mediawiki%2Fcore.git/9db61c9ab58b11b639a1f95916b37b57530ec674/includes%2Fapi%2FApiMain.php#L180) will remove user credentials from JSONP requests for security reasons. Therefore, the user is treated as not being logged in and the 'readapidenied' message is returned.
+
+
+
+Solution
+========
+
+There is already a TODO here from Trevor Parschal bf268e82:
+
+    // TODO: Only use JSON-P for cross-domain.
+    // jQuery has this logic built-in (if url is not same-origin ..)
+    // but isn't working for some reason.
+
+However, I can't see anything in the jQuery $.ajax docs that says it will switch from JSONP to JSON for same-origin requests.
+
+So if it's not automatic, the obvious fix is to add a function that checks for same-origin in the Javascript. But since this issue is hard to debug and may occur again for other extension developers, I think it would be better to patch the MW core so that it only strips user credentials for cross-origin JSONP requests ApiMain.php:180. 
+
+I didn't want to make a patch for this without checking about the security implications, and also to ask if there is an existing utility function in MediaWiki which checks if a request is same-origin?  
+
+
+Workaround
+==========
+
+If you are only searching the private wiki and no external sources, a temporary workaround is to change ""'datatype': 'jsonp'"" to ""'datatype': 'json'""  in ve.ui.MWMediaSearchWidget.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399207560,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-reknxycmtl2gxva75ktp,task_description,resolved
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 223853 merged by jenkins-bot:
+MWMediaResourceProvider: Use exist instead of bool check on API values
+
+[[https://gerrit.wikimedia.org/r/223853]]",1436466919,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 223853 had a related patch set uploaded (by Jforrester):
+MWMediaResourceProvider: Use exist instead of bool check on API values
+
+[[https://gerrit.wikimedia.org/r/223853]]
+",1436466679,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),Thanks!,1434050858,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"* https://gerrit.wikimedia.org/r/217444 (branch master): #mw1.26wmf10
+",1434042133,PHID-USER-n4kveqwjjlpsb6ydn73h,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 217444 merged by jenkins-bot:
+MWMediaResourceProvider: Use exist instead of bool check on API values
+
+[[https://gerrit.wikimedia.org/r/217444]]",1434040562,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),This bug has popped up again because the check of config.local is wrong.,1433983523,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 217444 had a related patch set uploaded (by MarkAHershberger):
+Fix check of JSON return value
+
+[[https://gerrit.wikimedia.org/r/217444]]
+",1433983507,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 150054 merged by jenkins-bot:
+MWMediaSearchWidget: Use json/jsonp for local/foreign api respectively
+
+https://gerrit.wikimedia.org/r/150054",1406740424,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"Change 150054 had a related patch set uploaded by Mooeypoo:
+Switch between json/jsonp for local/remote api search
+
+https://gerrit.wikimedia.org/r/150054",1406585034,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),*** Bug 68141 has been marked as a duplicate of this bug. ***,1406584368,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"(In reply to Krinkle from comment #7)
+> (In reply to Barry Coughlan from comment #2)
+> > The crossDomain logic will switch between the 'script' and 'xhr' transports,
+> > but both requests will still have be JSONP and have the callback parameter.
+> > 
+> > See here: http://jsfiddle.net/yvzSL/228/
+> > 
+> > In your developer tools console you can see that the local request uses XHR,
+> > but it is still a JSONP request over XHR. I have read through the $.ajax
+> > docs a number of times now and I see no indication that it should behave
+> > otherwise.
+> 
+> That example is broken. The first request is is malformed. ""json jsonp"" is
+> not a valid dataType. This value is invalid and unsupported. It seems to
+> default to a script tag instead, but as you can see the callback in that
+> code never fires. Here's a forked version of that example where I added
+> number ""1"" and ""2"". You'll find that ""DONE 1"" never appears.
+> 
+> http://jsfiddle.net/L5PtK/
+
+To clarify, I know dataType supports multiple values, but that's for converting the response (e.g. xml over jsonp). But you can't convert the actual data from json to jsonp or from json to jsonp (unless an API would embed javascript inside json or something like that).
+
+As for VisualEditor, it should use json when contacting the local API. and jsonp when contacting any foreign API (whether on the same domain or not).
+
+There is logic for this in jQuery that automatically switches from ""json"" to ""jsonp"" for cross domain urls.
+
+However that doesn't trigger the way I expected. It makes the assumption that 1) you should only make 'json' requests to APIs on the same domain or with CORS authentication set up. Then if a browser doesn't support CORS it will use script  with JSONP instead of XHR. So it functions like a fallback for browsers not supporting CORS, *not* as a convenience to switch to JSONP automatically for any cross domain url.
+
+jquery.js
+> if ( !options.crossDomain || support.cors ) {",1406583039,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"(In reply to Barry Coughlan from comment #2)
+> The crossDomain logic will switch between the 'script' and 'xhr' transports,
+> but both requests will still have be JSONP and have the callback parameter.
+> 
+> See here: http://jsfiddle.net/yvzSL/228/
+> 
+> In your developer tools console you can see that the local request uses XHR,
+> but it is still a JSONP request over XHR. I have read through the $.ajax
+> docs a number of times now and I see no indication that it should behave
+> otherwise.
+
+That example is broken. The first request is is malformed. ""json jsonp"" is not a valid dataType. This value is invalid and unsupported. It seems to default to a script tag instead, but as you can see the callback in that code never fires. Here's a forked version of that example where I added number ""1"" and ""2"". You'll find that ""DONE 1"" never appears.
+
+http://jsfiddle.net/L5PtK/",1406582208,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"(In reply to Krinkle from comment #5)
+> [callback] is only applied when the ""jsonp"" transport is activated (builds
+> on top of the ""script"" transport).
+> 
+> And the ""json"" dataType only activates ""json"" in case of crossDomain.
+> 
+
+I mean, the ""json"" dataType only activates ""jsonp"" in case of crossDomain.",1406582085,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"(In reply to Barry Coughlan from comment #2)
+> The crossDomain logic will switch between the 'script' and 'xhr' transports,
+> but both requests will still have be JSONP and have the callback parameter.
+> 
+> See here: http://jsfiddle.net/yvzSL/228/
+> 
+> In your developer tools console you can see that the local request uses XHR,
+> but it is still a JSONP request over XHR. I have read through the $.ajax
+> docs a number of times now and I see no indication that it should behave
+> otherwise.
+
+You read wrong. &callback= (or rather s.jsonpCallback) is only applied when the ""jsonp"" transport is activated (builds on top of the ""script"" transport).
+
+And the ""json"" dataType only activates ""json"" in case of crossDomain.
+
+Making a plain api request to a non-crossdomain url does NOT result in a callback parameter. Instead it results in a plain JSON response that is parsed by JSON.parse, no callback or javascript execution comes into play.
+
+MediaWiki core uses $.ajax in this in many places. For example mediawiki.user.js[1] uses it to fetch user rights and groups information from the API. This behaviour has been this way for quite a while.
+
+Like I said, if VisualEditor and/or your wiki is doing it differently, there is most likely a bug in the code invoking $.ajax.
+
+
+[1] https://github.com/wikimedia/mediawiki-core/blob/08c17086e1/resources/src/mediawiki/mediawiki.user.js#L27-L41",1406582007,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"I ran into the same problem myself my private wiki (1.23 and the REL1_23 branch of VE)
+
+What are the security implications if I make the workaround change mentioned above? I have a foreign API configured, but it's one I control.
+
+Thanks!
+--Ryan",1403031941,PHID-USER-evwol34rsld7viokxokd,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"**b.coughlan2** wrote:
+
+I did some more re-thinking about this.
+
+I examined the jQuery code and the 'crossDomain' attribute is just for selecting the transport (XMLHttpRequest or <script> tag). It does not select data types (json/jsonp), i.e. if the datatype is 'jsonp' and the request is local, you will get a 'jsonp' request with a 'callback' parameter over XMLHttpRequest. The MW core will assume that any request with a 'callback' parameter is from another domain, and will treat the request as unauthenticated.
+
+MW core needs a better way to detect if a request is really cross-origin. The solution is CORS, but this is not supported in a standard way on IE9 (http://caniuse.com/cors). The most ""correct"" fix would be to change the MW core to use CORS to detect cross-origin requests, but this might break plugins relying on the API in IE<=9, so it would be a risky fix until IE9 is no longer a concern for anyone.
+
+I'm now convinced that the simplest fix for now is to add some logic in the VisualEditor JS to detect if the request will be local, based on the target URL of the request. Then use the 'json' datatype if it is local, and the 'jsonp' datatype if not. Here is jQuery's logic for checking that: https://github.com/jquery/jquery/blob/master/src/ajax.js#L518
+
+Note that I tried this out by implementing custom prefilters/transports for jQuery (to leverage the crossDomain code already present), but this approach is hacky and a dead end.",1401770496,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"**b.coughlan2** wrote:
+
+The crossDomain logic will switch between the 'script' and 'xhr' transports, but both requests will still have be JSONP and have the callback parameter.
+
+See here: http://jsfiddle.net/yvzSL/228/
+
+In your developer tools console you can see that the local request uses XHR, but it is still a JSONP request over XHR. I have read through the $.ajax docs a number of times now and I see no indication that it should behave otherwise.",1399374421,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API),"There is most certainly logic in $.ajax to switch between xhr/json and script/jsonp. This has been in jQuery for many years.
+
+The reason it isn't working might be related to the usage of protocol-relative urls, or the presence of CORS support.
+
+To cite the relevant parts:
+
+	// A cross-domain request is in order when url parts mismatch
+	if ( s.crossDomain == null ) {
+		parts = rurl.exec( s.url.toLowerCase() );
+		s.crossDomain = !!( parts[ 1 ] !== ajaxLocParts[ 1 ] || .. );
+	}
+	..
+	jQuery.ajaxTransport( ""script"", function(s) {
+		// This transport only deals with cross domain requests
+		if ( s.crossDomain ) {
+			..
+		}
+	});
+	..
+	if ( xhrSupported ) { jQuery.ajaxTransport(function( s ) {
+		if ( !s.crossDomain .. ) {
+			return { send: function() {
+				var xhr = s.xhr();
+				..
+	..
+
+Anyway, no work around is needed. It is a well-known feature of $.ajax, we just need to start using it. And if it isn't working, find out what we're doing wrong on our end.",1399244614,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-reknxycmtl2gxva75ktp,task_subcomment,NA
+VisualEditor: Get rid of div wrapping in template rendering,"Div wrapping of rendered templates causes problems, especially when the template generates something like a <tr>. We should try to get rid of this wrapping and instead put shields and what not directly in the tag itself.
+
+Potential issues:
+* may not work for all tags
+* may not work for inline tags
+* won't work for non-tag things (text nodes, comments)
+* tricky for multi-sibling templates
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399091520,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2caghp6wplr54d3wekly,task_description,resolved
+VisualEditor: Get rid of div wrapping in template rendering,Fixed by Ed in https://gerrit.wikimedia.org/r/#/c/140439/,1404350131,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2caghp6wplr54d3wekly,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier","Right now there's a noticeable delay; we can speed up user experience at the expense of resources.
+",1399072260,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_description,declined
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",I think this is something we could do after the page has finished loading...,1427320035,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",Slowing down load isn't something we're interested.,1426880111,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier","Unassigning for now. Already working with Roan on TargetLoader, {T91715}, and the blockers under {T74063}.",1426622432,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",I started looking into this and found that MWTransclusionModel#fetchRequestDone actually wants to handle all sorts of data about normalisation and redirects and things which a current ApiResponseCache system (as part of the above link) would not provide (as it's not part of the data.query.pages part of the response). Waiting for @Catrope's input.,1422654417,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",I started looking into this and found that MWTransclusionModel#fetchRequestDone actually wants to handle all sorts of data about normalisation and redirects and things which a current ApiResponseCache system (as part of the above link) would not provide (as it's not part of the data.query.pages part of the response).,1422572392,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",I started looking into this and found that MWTransclusionModel#fetchRequestDone actually wants to handle all sorts of data about normalisation and redirects and things which a proper ApiResponseCache system would not provide (as it's not part of the data.query.pages part of the response).,1422572367,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",Might be something that could take advantage of code in https://gerrit.wikimedia.org/r/#/c/180228/,1422049468,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",(Needs performance investigation.),1400138507,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+"On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier",Also pre-load the templates configured for the cite tools.,1399317199,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-parbfhdkrfhhceyjfyzf,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open a reference dialog box or Media Settings for an image
+3.Try open any of the inspectors:Math/Hiero/Special Character
+
+Observed Result:
+All inspector appearing with broken UI
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13474}",1399055460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_description,resolved
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"(In reply to Rummana Yasmeen from comment #11)
+> Ah I see, Sorry we didnt know that before the fix, opening a different one
+> and tagging that against this week's target milestone.
+
+No worries. :-)",1416276547,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Ah I see, Sorry we didnt know that before the fix, opening a different one and tagging that against this week's target milestone.",1416275702,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"This bug didn't recur, it was a new bug with a totally different cause. Let's not confuse things by claiming we fixed the same bug. :-)",1416271003,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Change 173977 merged by jenkins-bot:
+Followup ca6a16f: use parent selector both for hiding and showing windows
+
+https://gerrit.wikimedia.org/r/173977",1416262354,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Change 173977 had a related patch set uploaded by Catrope:
+Followup ca6a16f: use parent selector both for hiding and showing windows
+
+https://gerrit.wikimedia.org/r/173977",1416261348,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Created attachment 17116
+screenshot,  showing blank link inspector
+
+**Attached**: {F13475}",1415891464,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Reopen this issue.
+In test2 and beta only.
+
+steps-
+
+1> open the link/math/comment/special characters/ inspectors in Media Settings -> caption sub-editor or the References sub-editor. The inspectors are blank with no UI.
+
+Also see Bug 68130 https://bugzilla.wikimedia.org/show_bug.cgi?id=68130.",1415891307,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified in production,1400188644,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified the fix in test2,1400023054,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,Verified the fix on Betalabs,1399074288,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Change 131112 merged by jenkins-bot:
+Fix regression in frame style scoping
+
+https://gerrit.wikimedia.org/r/131112",1399057262,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box,"Change 131112 had a related patch set uploaded by Catrope:
+Fix regression in frame style scoping
+
+https://gerrit.wikimedia.org/r/131112",1399057200,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-twukwcdq55v7wby6qwvx,task_subcomment,NA
+OOjs UI: Auto-disabled tool group still responds to clicks,"* Go to the tools demo
+* Click ""auto-disabling list""
+* Click ""click to disable this tool""
+* ""auto-disabling list"" now appears greyed out
+* Click ""auto-disabling list""
+* An active effect appears, even though the dropdown is disabled and you can't interact with it at all
+
+Other disabled toolgroups don't have this problem, it's only the one that gets disabled dynamically.
+
+This causes a bug in VisualEditor as well: click out of the editor (this disables most tools and auto-disables the Insert toolgroup), then click Insert. An active effect appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64601",1399055100,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2glncnsws774p5ae225r,task_description,resolved
+OOjs UI: Auto-disabled tool group still responds to clicks,"(In reply to Rainer Rillke @commons.wikimedia from comment #2)
+> Is this a duplicate of Bug 64601 ?
+
+No; bug 64434.",1399065942,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2glncnsws774p5ae225r,task_subcomment,NA
+OOjs UI: Auto-disabled tool group still responds to clicks,"Change 131120 merged by jenkins-bot:
+Use .isDisabled() instead of .disabled to support inheriting
+
+https://gerrit.wikimedia.org/r/131120",1399059823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2glncnsws774p5ae225r,task_subcomment,NA
+OOjs UI: Auto-disabled tool group still responds to clicks,Is this a duplicate of Bug 64601 ?,1399059282,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-2glncnsws774p5ae225r,task_subcomment,NA
+OOjs UI: Auto-disabled tool group still responds to clicks,"Change 131120 had a related patch set uploaded by Trevor Parscal:
+Use .isDisabled() instead of .disabled to support inheriting
+
+https://gerrit.wikimedia.org/r/131120",1399058825,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2glncnsws774p5ae225r,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"In some cases, MediaWikiModuleStore can be quite large (over 1 MB). This can lead to local storage becoming full and causing random problems like T66716. According to https://support.mozilla.org/en-US/questions/963825 Firefox shares local storage space across all hosts on a single domain name, so this may be especially problematic for Firefox.
+
+In theory, this shouldn't be an issue since people should always have some sort of fall-back behavior if there are problems with local storage, but in the interests of defensive programming, perhaps we should put a cap on the maximum size of MediaWikiModuleStore.
+
+--------------------------
+**See Also**:
+* {T66716} (bug 64716)
+* {T67566} (bug 65566)
+
+**Upstream**;
+* <https://bugzilla.mozilla.org/show_bug.cgi?id=1064466>",1398981300,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_description,resolved
+mw.loader.store should not occupy all of localStorage,">>! In T66721#7865568, @AlexisJazz wrote:
+> I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/.
+>
+> At the same time, enwiki doesn't seem to be affected.
+
+This means that the changes from this ticket, made some 5-7 years ago, are fortunately still working as expected. We do not use the defragmented module cache in environments where we know localStorage quotas would be shared.
+
+While not a ""cause"", the reason you are seeing this console warning today and not before, is because something is storing large values in localStorage. That is most likely `mw.loader.store` indeed, which was recently re-enabled in Firefox as per T235852, after we learned and confirmed emperically that the shared quotas indeed are no longer a thing in Firefox. Thus allowing the same savings from the defragmented module cache, that people using Safari- and Chromium-based browsers have been enjoying all these years ([documentation](https://www.mediawiki.org/wiki/ResourceLoader/Architecture#Store)).
+
+> JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+This is measuring the uncompressed size of the (minified) CSS and JS code downloaded during your browsing session so far (including from previous pageviews; limited to 1 copy of any given module bundle by name; old versions or variants for other lang/skin contexts are automatically discarded).
+
+1.4MB is not a particularly large number in that regard. Note that nothing about this feature is incurring additional cost in terms of what you download. Quite the opposite.
+
+Features like MediaViewer are not new. They were there before and are there now. Previously, this was stored in the HTTP cache by URL key. They are now stored in a defragmented fashion in the module cache.
+
+By doing this, your browser is able to make optimal use of this cache, allowing it to re-use part of something you downloaded on a previous pageview, and re-use it on this one. This has the impact that as a Firefox user, you are now downloading a drastically lower amount of bytes from the network on a typical pageview, and storing essentially only 1 copy. Saving bandwidth cost, saving disk space, and saving time.
+
+> 
+> JSON.stringify( window.localStorage ).length is 3281.
+> 
+> Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+No. As part of ensuring the cache plays nice with other features and gadgets that make use of cookies and localStorage, mw.loader automatically removes its portion from localStorage if it is full. You probably just missed the window during which this was briefly stored and then no longer.
+
+I suspect you might have additional features enabled that I don't, or have built up caches over a longer period of time. For me in Firefox (my main browser) on test.wikipedia. That's okay, automatically clearing unused code is part of the cycle. It'll start paying off again starting on the next pageview.
+
+```
+JSON.stringify( mw.loader.store ).length
+//> 811398 (0.8MB)
+JSON.stringify( window.localStorage ).length
+//> 847312 (0.8MB)
+```
+
+> I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Extraordinary claims require extraordinary evidence.
+
+Note, I don't think it's extraordinary //in general// that a volunteer would write good code. On the contrary, I'm sure your code is fine, and in fact many extensions we deploy or host as gadgets are maintained by volunteers and often quite to a standard that is as good or above average, including in following performance guidenance.
+
+However your particular claim is obviously meant to suggest that our software somehow is inefficient, which is factually inaccurate by almost every imaginable metric. Wikipedia.org is and remains one of the best performing sites in the world, in any category. That's no small feat.
+
+> Is this task why I'm seeing this error? Is this really resolved?
+
+I believe it remains resolved. The warning you saw (not an uncaught error) in the developer console, is a rare but entirely expected and harmless side-effect of the system working as intended, as has it has been for other browsers over the past 7 years.
+
+This warning may appear on 1 single pageview once a month or so, possibly more regularly if you engage with many different and large frontend features in a short period of time. If you see it on every page view, or if it has any observable negative effect on functionality by a gadget or user script, or on network/bandwidth use; please create a task as that would be an important issue to address.",1650400355,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#7865568, @AlexisJazz wrote:
+> I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/.
+>
+> At the same time, enwiki doesn't seem to be affected.
+
+This means that the changes from this ticket, made some 5-7 years ago, are fortunately still working as expected. We do not use the defragmented module cache in environments where we know localStorage quotas would be shared.
+
+While not a ""cause"", the reason you are seeing this console warning today and not before, is because something is storing large values in localStorage. That is most likely `mw.loader.store` indeed, which was recently re-enabled in Firefox as per T235852, after we learned and confirmed emperically that the shared quotas indeed are no longer a thing in Firefox. Thus allowing the same savings from the defragmented module cache, that people using Safari- and Chromium-based browsers have been enjoying all these years ([documentation](https://www.mediawiki.org/wiki/ResourceLoader/Architecture#Store)).
+
+> JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+This is measuring the uncompressed size of the (minified) CSS and JS code downloaded during your browsing session so far (including from previous pageviews; limited to 1 copy of any given module bundle by name; old versions or variants for other lang/skin contexts are automatically discarded).
+
+1.4MB is not a particularly large number in that regard. Note that nothing about this feature is incurring additional cost in terms of what you download. Quite the opposite.
+
+Features like MediaViewer are not new. They were there before and are there now. Previously, this was stored in the HTTP cache by URL key. They are now stored in a defragmented fashion in the module cache.
+
+By doing this, your browser is able to make optimal use of this cache, allowing it to re-use part of something you downloaded on a previous pageview, and re-use it on this one. This has the impact that as a Firefox user, you are now downloading a drastically lower amount of bytes from the network on a typical pageview, and storing essentially only 1 copy. Saving bandwidth cost, saving disk space, and saving time.
+
+> 
+> JSON.stringify( window.localStorage ).length is 3281.
+> 
+> Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+No. As part of ensuring the cache plays nice with other features and gadgets that make use of cookies and localStorage, mw.loader automatically removes its portion from localStorage if it is full. You probably just missed the window during which this was briefly stored and then no longer.
+
+I suspect you might have additional features enabled that I don't, or have built up caches over a longer period of time. For me in Firefox (my main browser) on test.wikipedia. That's okay, automatically clearing unused code is part of the cycle. It'll start paying off again starting on the next pageview.
+
+```
+JSON.stringify( mw.loader.store ).length
+//> 811398 (0.8MB)
+JSON.stringify( window.localStorage ).length
+//> 847312 (0.8MB)
+```
+
+> I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Extraordinary claims require extraordinary evidence.
+
+Note, I don't think it's extraordinary //in general// that a volunteer would write good code. On the contrary, I'm sure your code is fine, and in fact many extensions we deploy or host as gadgets are maintained by volunteers and often quite to a standard that is as good or above average, including in following performance guidenance.
+
+However your particular claim is obviously meant to suggest that our software somehow is inefficient, which is factually inaccurate by almost every imaginable metric. Wikipedia.org is and remains one of the best performing sites in the world, in any category. That's no small feat.
+
+> Is this task why I'm seeing this error? Is this really resolved?
+
+I believe it remains resolved. The warning you saw (not an uncaught error) in the developer console, is a rare but entirely expected and harmless side-effect of the system working as intended, has it has been for other browsers over the past 7 years. This may pop up once a month or so, possibly more regularly if you engage with many large frontend features in a short period of time. If you see it on every page view, or if it has any observable negative effect on functionality by a gadget or user script, or on network/bandwidth use; please create a task as that would be an important issue to address.",1650400091,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#7865568, @AlexisJazz wrote:
+> I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/.
+>
+> At the same time, enwiki doesn't seem to be affected.
+
+This means that the changes from this ticket, made some 5-7 years ago, are fortunately still working as expected. We do not use the defragmented module cache in environments where we know localStorage quotas would be shared.
+
+While not a ""cause"", the reason you are seeing this console warning today and not before, is because something is storing large values in localStorage. That is most likely `mw.loader.store` indeed, which was recently re-enabled in Firefox as per T235852, after we learned and confirmed emperically that the shared quotas indeed are no longer a thing in Firefox. Thus allowing the same savings from the defragmented module cache, that people using Safari- and Chromium-based browsers have been enjoying all these years.
+
+> JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+This is measuring the uncompressed size of the (minified) CSS and JS code downloaded during your browsing session so far (including from previous pageviews; limited to 1 copy of any given module bundle by name; old versions or variants for other lang/skin contexts are automatically discarded).
+
+1.4MB is not a particularly large number in that regard. Note that nothing about this feature is incurring additional cost in terms of what you download. Quite the opposite.
+
+Features like MediaViewer are not new. They were there before and are there now. Previously, this was stored in the HTTP cache by URL key. They are now stored in a defragmented fashion in the module cache.
+
+By doing this, your browser is able to make optimal use of this cache, allowing it to re-use part of something you downloaded on a previous pageview, and re-use it on this one. This has the impact that as a Firefox user, you are now downloading a drastically lower amount of bytes from the network on a typical pageview, and storing essentially only 1 copy. Saving bandwidth cost, saving disk space, and saving time.
+
+> 
+> JSON.stringify( window.localStorage ).length is 3281.
+> 
+> Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+No. As part of ensuring the cache plays nice with other features and gadgets that make use of cookies and localStorage, mw.loader automatically removes its portion from localStorage if it is full. You probably just missed the window during which this was briefly stored and then no longer.
+
+I suspect you might have additional features enabled that I don't, or have built up caches over a longer period of time. For me in Firefox (my main browser) on test.wikipedia. That's okay, automatically clearing unused code is part of the cycle. It'll start paying off again starting on the next pageview.
+
+```
+JSON.stringify( mw.loader.store ).length
+//> 811398 (0.8MB)
+JSON.stringify( window.localStorage ).length
+//> 847312 (0.8MB)
+```
+
+> I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Extraordinary claims require extraordinary evidence.
+
+Note, I don't think it's extraordinary //in general// that a volunteer would write good code. On the contrary, I'm sure your code is fine, and in fact many extensions we deploy or host as gadgets are maintained by volunteers and often quite to a standard that is as good or above average, including in following performance guidenance.
+
+However your particular claim is obviously meant to suggest that our software somehow is inefficient, which is factually inaccurate by almost every imaginable metric. Wikipedia.org is and remains one of the best performing sites in the world, in any category. That's no small feat.
+
+> Is this task why I'm seeing this error? Is this really resolved?
+
+I believe it remains resolved. The warning you saw (not an uncaught error) in the developer console, is a rare but entirely expected and harmless side-effect of the system working as intended, has it has been for other browsers over the past 7 years. This may pop up once a month or so, possibly more regularly if you engage with many large frontend features in a short period of time. If you see it on every page view, or if it has any observable negative effect on functionality by a gadget or user script, or on network/bandwidth use; please create a task as that would be an important issue to address.",1650400059,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#7865568, @AlexisJazz wrote:
+> I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/.
+>
+> At the same time, enwiki doesn't seem to be affected.
+
+This means that the changes from this ticket, made some 5-7 years ago, are fortunately still working as expected. We do not use the defragmented module cache in environments where we know localStorage quotas would be shared.
+
+While not a ""cause"", the reason you are seeing this console warning today and not before, is because something is storing large values in localStorage. That is most likely `mw.loader.store` indeed, which was recently re-enabled in Firefox as per T235852, after we learned and confirmed emperically that the shared quotas indeed are no longer an issue in Firefox. Thus allowing the same savings from the defragmented module cache, that people using Safari- and Chromium-based browsers have been enjoying all these years.
+
+> JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+This is measuring the uncompressed size of the (minified) CSS and JS code downloaded during your browsing session so far (including from previous pageviews; limited to 1 copy of any given module bundle by name; old versions or variants for other lang/skin contexts are automatically discarded).
+
+1.4MB is not a particularly large number in that regard. Note that nothing about this feature is incurring additional cost in terms of what you download. Quite the opposite.
+
+Features like MediaViewer are not new. They were there before and are there now. Previously, this was stored in the HTTP cache by URL key. They are now stored in a defragmented fashion in the module cache.
+
+By doing this, your browser is able to make optimal use of this cache, allowing it to re-use part of something you downloaded on a previous pageview, and re-use it on this one. This has the impact that as a Firefox user, you are now downloading a drastically lower amount of bytes from the network on a typical pageview, and storing essentially only 1 copy. Saving bandwidth cost, saving disk space, and saving time.
+
+> 
+> JSON.stringify( window.localStorage ).length is 3281.
+> 
+> Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+No. As part of ensuring the cache plays nice with other features and gadgets that make use of cookies and localStorage, mw.loader automatically removes its portion from localStorage if it is full. You probably just missed the window during which this was briefly stored and then no longer.
+
+I suspect you might have additional features enabled that I don't, or have built up caches over a longer period of time. For me in Firefox (my main browser) on test.wikipedia. That's okay, automatically clearing unused code is part of the cycle. It'll start paying off again starting on the next pageview.
+
+```
+JSON.stringify( mw.loader.store ).length
+//> 811398 (0.8MB)
+JSON.stringify( window.localStorage ).length
+//> 847312 (0.8MB)
+```
+
+> I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Extraordinary claims require extraordinary evidence.
+
+Note, I don't think it's extraordinary //in general// that a volunteer would write good code. On the contrary, I'm sure your code is fine, and in fact many extensions we deploy or host as gadgets are maintained by volunteers and often quite to a standard that is as good or above average, including in following performance guidenance.
+
+However your particular claim is obviously meant to suggest that our software somehow is inefficient, which is factually inaccurate by almost every imaginable metric. Wikipedia.org is and remains one of the best performing sites in the world, in any category. That's no small feat.
+
+> Is this task why I'm seeing this error? Is this really resolved?
+
+I believe it remains resolved. The warning you saw (not an uncaught error) in the developer console, is a rare but entirely expected and harmless side-effect of the system working as intended, has it has been for other browsers over the past 7 years. This may pop up once a month or so, possibly more regularly if you engage with many large frontend features in a short period of time. If you see it on every page view, or if it has any observable negative effect on functionality by a gadget or user script, or on network/bandwidth use; please create a task as that would be an important issue to address.",1650399979,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/. At the same time, enwiki doesn't seem to be affected.
+
+JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+JSON.stringify( window.localStorage ).length is 3281.
+
+Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+Sometimes I worry if my userscript is efficient enough. Then I see numbers like 1.4MB and I'm confident again that no matter how bad, I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Is this task why I'm seeing this error? Is this really resolved?",1650395373,PHID-USER-fstzz5dgooacghhxvdbs,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I get ""Exception in store-localstorage-update"" and ""The quota has been exceeded."" on https://test.wikipedia.org/wiki/. At the same time, enwiki doesn't seem to be affected.
+
+JSON.stringify( mw.loader.store ).length is 938292. After clicking an image (opening it in MediaViewer) it's 1096751. After that I pressed ""Your alerts"" (the bell) it's 1375615. That's like, 1.4MB? For what exactly?
+
+JSON.stringify( window.localStorage ).length is 3281.
+
+Those values combined, while high, are nowhere near 5MB so the error doesn't quite make sense to me still. I must be missing a storage mechanism?
+
+Sometimes I worry if my userscript is efficient enough. Then I see numbers like these and I'm confident again that no matter how bad, I'm somehow vastly outperforming the paid WMF team when it comes to efficiency. Which is fairly insane.
+
+Is this task why I'm seeing this error? Is this really resolved?",1650395347,PHID-USER-fstzz5dgooacghhxvdbs,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 776261 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] resourceloader: Enable mw.loader.store in Firefox%%%
+https://gerrit.wikimedia.org/r/776261",1648851599,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 776261 had a related patch set uploaded (by Krinkle; author: Krinkle):
+%%%[mediawiki/core@master] resourceloader: Enable mw.loader.store in Firefox%%%
+https://gerrit.wikimedia.org/r/776261",1648849582,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Thank you, would you mind creating a new task for that?",1571338055,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"This issue seems to be resolved in Firefox 69 and apparently the quota is now per origin. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1064466#c18
+
+So maybe we can start thinking about enabling local storage for Firefox again? At least dependent on the Firefox version number in the user agent?",1571317115,PHID-USER-6wbaay22g6ffupyt3pxo,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Are you seeing that error in Firefox? That shouldn't be possible because MediaWiki self-disables the `mw.loader.store` functionality on all Firefox versions. And upon viewing a page, any previous use of it is also proactively cleared. The `flushWrites` code should not be reachable. If you find that it is being reached in Firefox, please file a separate task and we'll investigate to make sure it remains off.
+
+As for Chrome, there shouldn't be a course of action needed. The system is meant to be self-correcting. The errors you're seeing are ""caught"", that means the MediaWiki code did not crash or stop unexpectedly. The code prints the caught error to the developer console as a ""warning"" so that when developers investigate other issues, they also know this particular condition was reached. Are you finding any loss of functionality in Chrome?
+
+The main problem found in this task was due to multiple wikis storing their modules under the same quota in Firefox. That is not something we can control. More-over, the browser also does not provide a way to let module storage expire from wikis not recently visited. For this reason, we have decided to disable this performance feature in Firefox. In Chrome this should not be a problem given that Chrome sets the quota at the full domain level (not the parent domain).
+
+I noticed in your example that you might be experiencing problems from serving multiple MediaWiki installations from the same domain under different directories. If that is the case and you intend to also offer multiple installations this way in production, I recommend `$wgResourceLoaderStorageEnabled = false;`.
+
+Alternatively, if this is only for local development, run `localStorage.clear();` from the console to clear the storage used by previous/other wiki installations.",1537632521,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"> As for the issue reported in this task, it's been resolved. In theory, it will always be 
+
+So, what is the appropriate course of action? Given that I'm seeing an elevated level (for FF and Chrome) of:
+
+```
+Exception in store-localstorage-update:
+:8080/mw-31-00-elastic/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=0xnodom:177 QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value of 'MediaWikiModuleStore:mw-31-00-elastic' exceeded the quota. DOMException: Failed to execute 'setItem' on 'Storage': Setting the value of 'MediaWikiModuleStore:mw-31-00-elastic' exceeded the quota.
+    at flushWrites (http://127.0.0.1:8080/mw-31-00-elastic/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=0xnodom:175:212)
+logError @ :8080/mw-31-00-elastic/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=0xnodom:177
+```",1537625422,PHID-USER-ldehclaehsvglrqxywsj,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Replied at T85923#2471543 as it seems about a key disappearing, not a key being unable to be set.
+
+As for the issue reported in this task, it's been resolved. In theory, it will always be possible for the storage quota to be reached, at which points random keys will fail to be set. (This is true for cookies as well.)
+
+Task T101732 tracks moving the module cache to a different interface for that reason.",1468861106,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Replied at T85923#2471543 as it seems about a key disappearing, not a key being unable to be set.
+
+As for the issue reported in this task, it's been resolved. In theory, it will always be possible for the storage quota to be reached, at which points random keys will fail to be set. (This is true for cookies as well.)
+
+Task T101732 tracks moving the module cache into a different interface for that reason.",1468861098,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"From {T85923}: `wgMediaViewerOnClick` apparently cannot be reliably saved to local storage; used space (as per `encodeURIComponent(JSON.stringify(localStorage)).length`) is 2600025, quota is (per [[https://arty.name/localstorage.html|this test]]) somewhere between 2600000 and 2700000. The browser is Safari. May be related, although 2600025 is 0b1001111010110001011001 which does not seem like something that would be very close to a quota limit.",1468857408,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,No reports for over a month; closing.,1458258992,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 269625 merged by jenkins-bot:
+resourceloader: Disable localStorage cache on FF, Opera
+
+[[https://gerrit.wikimedia.org/r/269625]]",1455119961,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 269625 had a related patch set uploaded (by Ori.livneh):
+ResourceLoader: disable localStorage cache on FF, Opera
+
+[[https://gerrit.wikimedia.org/r/269625]]
+",1455093316,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Ok. I have been in denial about this long enough, I suppose. Let's start by disabling it completely in Firefox and Opera. I am still interested in more reports, because it will help determine where we go from there.",1455092112,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,I still get this on every page view using Firefox 44.,1454965195,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I continue to get this error on every page view using Opera 12 (obviously, since you only blacklisted Firefox).",1454962821,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Has anyone encountered any bugs since {7787a85d5c6f} went out, just under a month ago?",1454961269,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Nothing has changed here since 2014 -- it was a mistake to enable this feature on Firefox at the time, and it is a mistake to enable it now with a 30KB per-module limit. On my browser at the moment, MediaWikiModuleStore:enwiki is using 655KB, which is hardly an improvement from when the bug was first reported. You only need to visit 7 or 8 wikis to exhaust the quota.
+
+I don't think a <250ms performance improvement justifies randomly breaking the many extensions which use localStorage. 
+
+mediawiki.js will keep writing module caches until it hits the quota and fails. The functionality of the site after such a failure depends on how much of the quota is left -- effectively the remainder of the division, 5MB modulo the per-wiki module store size. An unlucky combination could leave a user unable to dismiss dialog boxes or to choose a preferred language.
+
+Some extensions try localStorage first, and fall back to a cookie if it fails. But the MW core does not provide a convenient interface for this, leaving each extension to implement it separately.",1454308136,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 263417 merged by jenkins-bot:
+Module storage: set stricter storage quotas on Firefox
+
+[[https://gerrit.wikimedia.org/r/263417]]",1452570602,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 263417 had a related patch set uploaded (by Ori.livneh):
+Module storage: set stricter storage quotas on Firefox
+
+[[https://gerrit.wikimedia.org/r/263417]]
+",1452545806,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"FYI, i had an issue fixed in WikEd, which was throwing exceptions all over the place, because it wasn't expecting a full localStorage.
+
+That's the problem with this issue. it's infectious....",1442262617,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Generally yes, regardless of this bug, even. localStorage likes to throw
+exceptions. (For example, apparently it will be defined but throw exception
+on access on Firefox if you disable it in browser settings.)",1441733763,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I assume anyone who wants to use `localStorage` is supposed to use `try`/`catch` on every attempt to save a value so that unrelated scripts are still executed? E.g.:
+https://pt.wikipedia.org/wiki/MediaWiki:Gadget-fastbuttons.js?diff=43318591
+https://meta.wikimedia.org/w/index.php?diff=13512749&oldid=13462279&diffonly=1
+https://github.com/brion/MediaWiki-MobileSidebar/pull/5/files?w=1",1441720355,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I assume anyone who wants to use `localStorage` is supposed to use `try`/`catch` on every attempt to save a value? E.g.:
+https://pt.wikipedia.org/wiki/MediaWiki:Gadget-fastbuttons.js?diff=43318591
+https://meta.wikimedia.org/w/index.php?diff=13512749&oldid=13462279&diffonly=1
+https://github.com/brion/MediaWiki-MobileSidebar/pull/5/files?w=1",1441720309,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I assume anyone who wants to use `localStorage` is supposed to use try/catch on every attempt to save a value? E.g.:
+https://pt.wikipedia.org/wiki/MediaWiki:Gadget-fastbuttons.js?diff=43318591
+https://meta.wikimedia.org/w/index.php?diff=13512749&oldid=13462279&diffonly=1
+https://github.com/brion/MediaWiki-MobileSidebar/pull/5/files?w=1",1441720294,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Interesting and thanks for the counter-example.
+I've taked to @ori about T96155 and the plan is for me to make this code use the new frontend api. When that's in place we could potentially be a bit more clever about what we are allowed to store e.g. limit number of bytes we allow saving for.
+
+Given that MobileFrontend/Gather are only using this storage mechanism to decide whether to show onboarding tutorials for new features, mostly targeting readers who are not editing or newbies, if localStorage is exhausted not showing these things is not the end of the world.
+",1439570818,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T96155#1539605, @matmarex wrote:
+>>>! In T96155#1528593, @Jdlrobson wrote:
+>> Yup. I recognise this is an issue but I am saying that this issue mostly impacts power users (especially on Firefox). I'm yet to see this on the mobile site, where gadgets and user scripts are currently not available nor used.
+> 
+>Eh, I don't think that it mostly impact power users, it can impact even occasional editors too.
+> 
+>As an example:
+>* Visit https://pl.wikipedia.org/wiki/Ostatnia_droga_Temeraire%27a, which is a pretty generic article on the Polish Wikipedia, as anonymous user. Run `JSON.stringify( mw.loader.store ).length` to see how much data ResourceLoader puts in localStorage (this is 707573 for me on first page load).
+>* Open the MediaViewer, which is not a power-user feature. The length increases to 923750.
+>* Open the VisualEditor, which is not a power-user feature either. The length increases to 2008078.
+> 
+>This is already 2 MB, and this is just one wiki and an anonymous user (I'm not sure how the browsers calculate the limit, but if anything, this is less than the number of bytes actually stored). Visit another wiki (say, the same article in English, if you're not satisfied with the content in Polish and speak two languages) and this doubles. Log in (which gets you features like Echo and lets you enable some gadgets or beta features), or visit a third wiki, and you're quickly over the 5 MB limit.
+
+",1439560126,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1418743, @Jdlrobson wrote:
+> Could we use ServiceWorker for this now (see T101731) ?
+
+Yes. We created T101732 last month.",1435784972,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Could we use ServiceWorker for this now (see T101731) ?
+",1435784898,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1411737, @ori wrote:
+>>>! In T66721#1411731, @SamB wrote:
+>> So, um, any tips on how to manually clean up the MediaWikiModuleStore keys from all of the wikipedias on Firefox/Iceweasel, including 31.7.0esr as included in Debian Jessie?
+> 
+> It should not be possible to fill it up now that the patch above has been pushed. You must have gotten into some weird state. Clear localStorage (either by nuking your browser history or by using https://addons.mozilla.org/en-US/firefox/addon/volatile-storage/?src=cb-dl-updated) and see if the problem recurs.
+
+Hmm, I'm still a bit nervous about nuking localStorage entirely, though that certainly would be less tedious than visiting every Wikipedia I've ever loaded in this bowser (including mobile versions) one-by-one and clearing the relevant key from the JS console... (though, that might not be so bad if I used a greasemonkey script to do the actual cleanup for each wiki).
+
+Anyway, this:
+
+>>! In T66721#1340094, @gerritbot wrote:
+> Change 216014 merged by jenkins-bot:
+> mw.loader.store: decline to store items > 100 kB
+> 
+> [[https://gerrit.wikimedia.org/r/216014]]
+
+... doesn't sound very promising to me.  Just because it only stores items < 100 kB does *not* prevent it from storing many such items, which could add up to a lot of usage on a single Wiki; factor in the fact that subdomains share quota on Firefox, and you could still easily hit 5 MiB, no?",1435671555,PHID-USER-3bnjvlq3zbpzzxdh4g4g,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"That extension does not seems to be enough, since I still get this on every page on Portuguese Wikipedia using Firefox 38.0:
+> ""Exception in store-localstorage-update:"" load.php:177:752
+> ""NS_ERROR_DOM_QUOTA_REACHED: Persistent storage maximum size reached"" DOMException [NS_ERROR_DOM_QUOTA_REACHED: ""Persistent storage maximum size reached""
+> code: 1014
+> nsresult: 0x805303f6
+> location: https://pt.wikipedia.org/w/load.php?debug=false&lang=pt&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=CZ6SC%2Fzc:175] load.php:177:790
+> log() load.php:177
+> handler() load.php:155
+> jQuery.Callbacks/fire() load.php:45
+> jQuery.Callbacks/self.fireWith() load.php:46
+> jQuery.Callbacks/self.fire() load.php:46
+> mw.track() load.php:155
+> flush() load.php:175
+and running
+> localStorage.clear();
+in the console doesn't help either.",1435661170,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1411731, @SamB wrote:
+> So, um, any tips on how to manually clean up the MediaWikiModuleStore keys from all of the wikipedias on Firefox/Iceweasel, including 31.7.0esr as included in Debian Jessie?
+
+It should not be possible to fill it up now that the patch above has been pushed. You must have gotten into some weird state. Clear localStorage (either by nuking your browser history or by using https://addons.mozilla.org/en-US/firefox/addon/volatile-storage/?src=cb-dl-updated) and see if the problem recurs.",1435614205,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"So, um, any tips on how to manually clean up the MediaWikiModuleStore keys from all of the wikipedias on Firefox/Iceweasel, including 31.7.0esr as included in Debian Jessie?",1435614036,PHID-USER-3bnjvlq3zbpzzxdh4g4g,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1340106, @matmarex wrote:
+> While the last patch may be helpful, it still does not prevent the cache from taking up all available localStorage space.
+
+Especially on Firefox, where e.g. all of the Wikipedias are sharing quota.  (There are a lot of Wikipedias, and there are reasons someone might look at quite a lot of them.)
+
+Also, to clean up after this, you'll need to do something like what's described at <https://bugzilla.mozilla.org/show_bug.cgi?id=1064466#c11>: have a path on each wiki that will clean up the storage, and also a way to open an iframe to that path on *every* wiki for a given domain ...",1435599957,PHID-USER-3bnjvlq3zbpzzxdh4g4g,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"On the topic of using IndexedDB for module store, beware that there is an important difference with localStorage.
+
+localStorage, while having a lower quota by default (~ 5MB), doesn't have a way to expand that quota. Which means when it's full, the API returns a failure code but nothing is shown the user.
+
+IndexedDB, while having a higher quota by default (~ 10-50MB), has a way of extending the quota. It's not clear to me what happens when you reach the quota. It appears that browsers default to asking the user to expand the quota.
+
+For the purpose of caching modules, and for Wikipedia in general, I don't think we should ever allow that to happen. So we may have to somehow manually poll the aggregate size of database to prevent the browser from asking the user any such question.
+
+See http://www.html5rocks.com/en/tutorials/offline/quota-research/
+{F177107}",1433880982,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"On the topic of using IndexedDB for module store, beware that there is an important difference with localStorage.
+
+localStorage, while having a lower quota by default (~ 5MB), doesn't have a way to expand that quota. Which means when it's full, the API returns a failure code but nothing is shown the user.
+
+IndexedDB, while having a higher quota by default (~ 10-50MB), has a way of extending the quota. It's not clear to me what happens when you reach the quota. It appears that browsers default to asking the user to expand the quota.
+
+For the purpose of caching modules, and for Wikipedia in general, I don't think we should ever allow that to happen. So we may have to somehow manually poll the aggregate size of database to prevent the browser from asking the user any such question.",1433880942,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"* https://gerrit.wikimedia.org/r/216014 (branch master): #mw1.26, #mw1.26wmf9
+",1433469636,PHID-USER-n4kveqwjjlpsb6ydn73h,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"While the last patch may be helpful, it still does not prevent the cache from taking up all available localStorage space.",1433468829,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 216014 merged by jenkins-bot:
+mw.loader.store: decline to store items > 100 kB
+
+[[https://gerrit.wikimedia.org/r/216014]]",1433468548,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 216014 had a related patch set uploaded (by Ori.livneh):
+mw.loader.store: decline to store items > 100 kB
+
+[[https://gerrit.wikimedia.org/r/216014]]
+",1433463569,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#1339632, @kaldari wrote:
+> @Mattflaschen The last two solutions sound sensible. Do you have any idea how much that might reduce the average size of the cache by?
+
+On a primed cache on enwiki, the top modules by size for me are:
+
+| Module | Size |
+|--------|------|
+| ext.visualEditor.core | 624 kB |
+| oojs-ui | 179 kB |
+| oojs-ui.styles.icons | 132 kB |
+| oojs-ui.styles | 90 kB |
+| mmv.ui.canvasButtons | 71 kB |
+| ext.visualEditor.mwmeta | 67 kB |
+| jquery.ui.core | 66 kB |
+| ext.visualEditor.mwtransclusion | 65 kB |
+| ext.visualEditor.mwimage | 65 kB |
+| oojs-ui.styles.icons-editing-advanced | 58 kB |
+| ext.visualEditor.mwcore | 52 kB |
+| jquery.ime | 50 kB |
+| moment | 48 kB |
+| mmv.ui.metadataPanel | 47 kB |
+| unicodejs | 46 kB |
+| ext.visualEditor.icons | 45 kB |
+| jquery.chosen | 42 kB |
+| jquery.uls | 37 kB |
+| ext.visualEditor.mediawiki | 35 kB |
+| jquery.uls.data | 33 kB |",1433461898,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"""Assigned To: None"" and ""Priority: High"" are at odds with each other. @ori, are you planning to work on this?",1433461535,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"@Mattflaschen The last two solutions sound sensible. Do you have any idea how much that might reduce the average size of the cache by? Blacklisting Firefox might be good as a last resort, but I would favor trying other solutions first.",1433461107,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Yesterday, we talked on IRC about a few possibilities:
+
+* Blacklisting Firefox (only seems to be an issue due to how it calculates quotas)
+* Blacklisting certain large modules
+* Only storing modules that are needed at page load",1433442846,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"BTW at some point I played with a promise wrapper lib for indexedDB: https://gerrit.wikimedia.org/r/#/c/157818/
+Might be useful if one wants to implement this ticket.",1430294125,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#974945, @Mattflaschen wrote:
+> @Ori plans to look into IndexedDB (which has very different quota rules) as a solution.
+
+Is there a status update about this?",1426484011,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Happened to me too.  A thought occurs: could this be related to the repeated reports during the massive fundraiser in December of dismissed banners coming back? (i.e. because the hide was not remembered, as Kaldari suggested above?)",1423603851,PHID-USER-qsj6mtmeexjxulfje7ie,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,@Ori plans to look into IndexedDB (which has very different quota rules) as a solution.,1421195890,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,">>! In T66721#946527, @Technical13 wrote:
+> Apparently I had 1,772,879 characters in localStorage on test.wikipedia.org.  Since this is so large, I've been unable to find a pastebin to paste it all to.
+
+There's no need to paste it.  We're aware of (most of, at least) the contents, and the underlying causes.",1421194351,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Apparently I had 1,772,879 characters in localStorage on test.wikipedia.org.  Since this is so large, I've been unable to find a pastebin to paste it all to.",1419818317,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"```
+""NS_ERROR_DOM_QUOTA_REACHED: Persistent storage maximum size reached"" DOMException
+[
+   NS_ERROR_DOM_QUOTA_REACHED: ""Persistent storage maximum size reached""
+   code: 1014
+   nsresult: 0x805303f6
+   location: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141217T214024Z:173
+]
+```
+on my `Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0` system indicates this is still a problem?",1419815416,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 176628 merged by jenkins-bot:
+resourceloader: Clear module storage if disabled by configuration
+
+[[https://gerrit.wikimedia.org/r/176628]]",1417491543,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"I think we should turn $wgResourceLoaderStorageEnabled off for the WMF cluster (it's already off by default in DefaultSettings.php) for now.
+
+>>! In T66721#795821, @tstarling wrote:
+> I don't think localStorage can be used as a cache for large objects if there is no way for us to implement an LRU policy.
+
+There is a way, but not if we use localStorage directly.  To solve this issue, I think we should ban direct use of localStorage, and require using a wrapper library that implements some kind of expiration (and also require expirations actually be used when setting).  jStorage (already in core) implements time to live/max-age (as does Storer.js, used by Flow).  Least recently used might be good for some kinds of data as an alternative to TTL, but I don't know if any of the libraries we currently use have it.",1417490159,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Actually the VE thing was disabled 18 months ago, but it will live on in my browser forever. The reason I saw an exception when I activated VisualEditor is because activating VE increased the module storage size to about 1.8MB.",1417416863,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Change 176628 had a related patch set uploaded (by Tim Starling):
+Clear module storage if it is disabled by configuration
+
+[[https://gerrit.wikimedia.org/r/176628]]
+
+#patch-for-review",1417414290,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Actually, disabling the code is not enough -- localStorage has no expiry, so everyone's browser will stay broken until we explicitly clean up these old entries.",1417413196,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"This is the first thing I saw on opening my web console on Wikipedia today -- localStorage exceptions from VisualEditor due to quota exhaustion, apparently due to module storage. I guess it should be reverted, or at least disabled on Firefox, if it can't be managed without breaking localStorage for everyone.
+
+I don't think localStorage can be used as a cache for large objects if there is no way for us to implement an LRU policy.
+
+%%%
+sqlite> select sum(length(value))+sum(length(key)) from webappsstore2 where scope like 'gro.aidepikiw.%' and key like 'MediaWikiModuleStore%';
+3731546
+sqlite> select sum(length(value))+sum(length(key)) from webappsstore2 where scope like 'gro.aidepikiw.%' and key like 've-%';
+535604
+%%%
+
+The VE thing will probably need to be removed or reduced as well.",1417412948,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,Filed an upstream bug against Firefox at https://bugzilla.mozilla.org/show_bug.cgi?id=1064466,1410203795,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Michael M.: That sounds like a good idea, but doesn't solve the underlying issue of this bug (that mw.loader.store takes up too much of localStorage).",1410202490,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"What about this approach?
+1. Before saving a module to localStorage try to save a string of 20 KB* there.
+2. If this fails, don't save the module in localStorage.
+3. If it succeeds, try to save the module.
+4. Whether or not putting the module in localStorage succeeds, remove the string from step 1.
+
+This will make sure that the modules never will occupy the last 20 KB* of localStorage.
+
+*) 20 KB is just the first number that came to my mind. Feel free to replace it with any other reasonable number. I have several user scripts that make use of localStorage, they take up 3 KB, but I know users who use them more heavily than me, they probably end up at about 10 KB or more.",1409558108,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,Ori: Could you reply to comment 6 please if you have some ideas?,1409519861,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Ori: Any thoughts on this? It's still a significant problem, especially for Firefox users.",1408647522,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"(In reply to Krinkle from comment #4)
+> mw.loader.store falls back to fetching from the server. However other
+> features that actually use localStorage in a more visible way will lose data
+> in a much worse way (e.g. users unable to store drafts, or a ""hide"" button
+> not being remembered etc.)
+
+Yep, as you can see from bug 65566 (thanks for marking that as a see also), we've already had to switch to cookies for a feature due to this issue.",1406254533,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"Raising priority as this will likely become increasingly more problematic as wikis and extensions register more modules and users enable more features.
+
+mw.loader.store falls back to fetching from the server. However other features that actually use localStorage in a more visible way will lose data in a much worse way (e.g. users unable to store drafts, or a ""hide"" button not being remembered etc.)",1405456170,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,*** Bug 65364 has been marked as a duplicate of this bug. ***,1405455430,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,"(In reply to Ryan Kaldari from comment #1)
+> Any thoughts on this? This bug makes using Wikipedia very annoying for me.
+> Surely I can't be the only person that cares about this.
+
+This document explains how to clear localStorage:
+
+https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Storage#Storage_location_and_clearing_the_data
+
+You can also up the quota via about:config. Search for ""dom.storage.default_quota"" option. Its value is in kilobytes.
+
+I'm not suggesting that these are adequate resolutions for this bug -- they're just workarounds. I want to try something like what DJ is proposing in <https://bugzilla.wikimedia.org/show_bug.cgi?id=65364#c3>.",1400638400,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+mw.loader.store should not occupy all of localStorage,Any thoughts on this? This bug makes using Wikipedia very annoying for me. Surely I can't be the only person that cares about this.,1400176516,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ena4hp3pzrqznsrbns76,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"Running JavaScript profiling on both desktop and mobile the majority of time is spent in jQuery.extend.css - the majority of which seems to be caused by ve.ce.ProtectedNode.prototype.onProtectedSetup
+
+On mobile this seems to be even more severe.
+
+In desktop 7.9% of execution time to load VisualEditor was spent in jQuery.extend.css - this was the most heavy function. In mobile it was also the most heavy - however in mobile a whopping 23.76% of time was spent in jQuery.extend.css
+
+Stubbing out the contents of the foreach loop 
+this.$element.add( this.$element.find( '*' ) ).each( function () {
+
+seems to remedy this problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51202",1398970740,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_description,resolved
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"Based on the work that Ed did, I'm going to mark this as closed.",1404866154,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"Additional fixes made for the 2014-05-15 release – but not sure what counts as ""fixing"" this bug. Jon, could you re-test?",1400145400,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"https://gerrit.wikimedia.org/r/130823 (for bug 52499) should make this perform a bit better as well, by 1) reducing the number of elements protectedNode CSS is applied to and 2) targeting them with a class rather than a star selector: .ve-ce-protectedNode * is an expensive selector just like .header > *:nth-child(3)",1399071192,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"I went deeper down the rabbit hole... 
+
+Removing all button styling drops this by 23.76% to 16.4%
+It drops to 8.6% with removal of 'skins.minerva.chrome.styles', 8.6% when I drop the use of ui.less
+
+Both the stylings for buttons and ui.less use last-child, nth-child, first-child, not selectors. These seem to be the major pain point.
+
+See bug 64719.",1398980755,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"Specifically it is a style or styles in one of these modules:
+http://localhost.alpha/w/load.php?debug=false&lang=en&modules=mediawiki.ui.button%7Cmobile.pagelist.styles%7Cmobile.styles.beta%7Cskins.minerva.chrome.styles%7Cskins.minerva.content.styles%7Cskins.minerva.drawers.styles&only=styles&skin=minerva&target=mobile&*
+
+
+It drops to 8% with their removal.",1398977725,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"So I tried removing #content element - no visible difference.
+Killing our stylesheets - visible difference (drops 1.59%).
+
+This must be linked to causing reflows, that are more expensive in the Minerva skin.",1398977336,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,We have a lot more DOM nodes in mobile - 2 times the number of DOM nodes in an article. In desktop they replace the page rather than create an overlay..,1398976699,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"**jgonera** wrote:
+
+The question is, why is this more of a problem with mobile skin than with Vector?",1398976459,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,"There may be ways to improve this in the short term, but what we really need to do is experiment with using an SVG overlay.",1398975000,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog,The majority of time is spent in looking up the float property but importNode is also a relatively big performance hog here,1398971621,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-em74gqq6yx5on4mj77dz,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs","Steps to reproduce:
+
+1.Open a page 
+2.Add few references
+3.Now Go to Insert>Reference>Use an Existing Reference 
+4.Select one of the existing references
+
+
+Observed Result:
+
+The selected reference does not get added in the page and the ""Save Page"" remains disabled
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/30thAprilChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398884040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-psuzyfjtumeoqqoapj7r,task_description,resolved
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs",Verified the fix on production,1400011514,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs",Verified the fix on test2,1399078263,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs",Verified the fix in Betalabs,1398895110,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs","Change 130734 merged by jenkins-bot:
+Make inserting existing references work again
+
+https://gerrit.wikimedia.org/r/130734",1398893606,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs","Change 130734 had a related patch set uploaded by Jforrester:
+Make inserting existing references work again
+
+https://gerrit.wikimedia.org/r/130734",1398892280,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Use existing reference"" is not functioning at all in Betalabs","Also, if you have added a reference list on that session before attempting to add an existing reference,the ""Save Page"" button becomes enabled but if you go to the Review your changes section there is no entry for adding <references> there.
+
+After clicking on ""Save Page"" , you will see the reference list did not get added in the page , but you open VE , you will the reference list",1398884383,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-psuzyfjtumeoqqoapj7r,task_subcomment,NA
+VisualEditor: Clean up Monobook-specific mess in ViewPageTarget init code,"In particular, see comments on https://gerrit.wikimedia.org/r/#/c/130085/
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398881280,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-izisrqmjp3trkjaifdin,task_description,resolved
+VisualEditor: Clean up Monobook-specific mess in ViewPageTarget init code,Fixed in gerrit 130717.,1398891382,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-izisrqmjp3trkjaifdin,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Go to Insert>Template
+
+Observed Result:
+
+Observe that, in the header of the dialog box , instead of text ""Transclusion"" ,""Null"" is appearing
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13912}",1398881220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftzt37epboyseb3ggnxl,task_description,resolved
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box",Verified the fix in production,1400011801,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftzt37epboyseb3ggnxl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box",Verified the fix in Betalabs and Test2,1399070765,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftzt37epboyseb3ggnxl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box","Change 130749 merged by jenkins-bot:
+Bring the transclusion title back to life
+
+https://gerrit.wikimedia.org/r/130749",1398896883,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftzt37epboyseb3ggnxl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] ""Null"" appearing instead of ""Transclusion"" in the template insert dialog box","Change 130749 had a related patch set uploaded by Jforrester:
+Bring the transclusion title back to life
+
+https://gerrit.wikimedia.org/r/130749",1398894082,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ftzt37epboyseb3ggnxl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""","Larger reference dialog
+
+Reference list dialog box is appearing much larger in size like the previous design that we had.
+
+See the two screenshots attached and compare
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13908}",1398880260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tp3if73tgdh5us2okcnt,task_description,resolved
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""",Verified the fix in production,1400012042,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""",Verified the fix in test2,1399067283,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""",Verified the fix in Betalabs,1398967868,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""","Change 130796 merged by jenkins-bot:
+Make reference list dialog small again
+
+https://gerrit.wikimedia.org/r/130796",1398908760,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""","Change 130796 had a related patch set uploaded by Catrope:
+Make reference list dialog small again
+
+https://gerrit.wikimedia.org/r/130796",1398906371,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer ""small"" size, but default ""large""","Created attachment 15253
+Reference list dialog box in production and test2
+
+**Attached**: {F13909}",1398880317,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-tp3if73tgdh5us2okcnt,task_subcomment,NA
+"VisualEditor: For formulae (and some other nodes?), inspection trigger region is a single line, not the whole block","The region you need to move the mouse over to get the inspector to popup.
+
+Using the math editor beta feature. The region you need to position the mouse over the get the inspector icon to come up is quite small. Ideally it should be the whole size of the image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50791
+
+**Attached**: {F13812}",1398807600,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-pwym3hscyxiqlzuo6ffh,task_description,resolved
+"VisualEditor: For formulae (and some other nodes?), inspection trigger region is a single line, not the whole block",*** Bug 50776 has been marked as a duplicate of this bug. ***,1412589972,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pwym3hscyxiqlzuo6ffh,task_subcomment,NA
+"VisualEditor: For formulae (and some other nodes?), inspection trigger region is a single line, not the whole block",The bug as reported (formula click areas)  is fixed now. It was probably fixed by https://gerrit.wikimedia.org/r/#/c/139805/,1412588736,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pwym3hscyxiqlzuo6ffh,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Screenshot of view and edit mode side-by-side
+
+Ever since the typography update, the content looks malformed in the editor.
+
+This is because the way the typography change in Vector was implemented, used rather specific selectors that cannot apply to VisualEditor's surface and thus it cascades in ways it wasn't supposed to.
+
+The content line-height is squished, and the font size is too small.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13719}",1398772380,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jx5rpwyz5z3myik43die,task_description,resolved
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,Verified the fix on production,1399072889,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,Verified the fix on Betalabs and test2,1399070699,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130745 merged by Catrope:
+mw.ViewPageTarget: Move .mw-body-content down to .ve-ce-surface
+
+https://gerrit.wikimedia.org/r/130745",1398899098,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130745 had a related patch set uploaded by Catrope:
+mw.ViewPageTarget: Move .mw-body-content down to .ve-ce-surface
+
+https://gerrit.wikimedia.org/r/130745",1398893379,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130541 merged by jenkins-bot:
+mw.ViewPageTarget: Move .mw-body-content down to .ve-ce-surface
+
+https://gerrit.wikimedia.org/r/130541",1398892611,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"(In reply to Krinkle from comment #7)
+> Yeah, we fixed the page content font-size and line-height, but now those
+> changes incorrectly apply to our overlays as well. This causes all our
+> inspectors to have messed up line-heights and recursively smaller font-sizes
+> inside e.g. link inspector suggestions and the context menu cursor.
+
+https://gerrit.wikimedia.org/r/130541 addresses this.",1398889325,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Yeah, we fixed the page content font-size and line-height, but now those changes incorrectly apply to our overlays as well. This causes all our inspectors to have messed up line-heights and recursively smaller font-sizes inside e.g. link inspector suggestions and the context menu cursor.",1398889312,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130541 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Move .mw-body-content down to .ve-ce-surface
+
+https://gerrit.wikimedia.org/r/130541",1398818521,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,Still some mess here.,1398815688,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130507 merged by jenkins-bot:
+mw.ViewPageTarget: Use .mw-body-content for content styling
+
+https://gerrit.wikimedia.org/r/130507",1398813965,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 129567 merged by jenkins-bot:
+mw.ViewPageTarget: Use .mw-body-content for content styling
+
+https://gerrit.wikimedia.org/r/129567",1398810355,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 130507 had a related patch set uploaded by Jforrester:
+mw.ViewPageTarget: Use .mw-body-content for content styling
+
+https://gerrit.wikimedia.org/r/130507",1398810240,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector,"Change 129567 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Use .mw-content for content styling
+
+https://gerrit.wikimedia.org/r/129567",1398772850,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx5rpwyz5z3myik43die,task_subcomment,NA
+VisualEditor:  Edit summary typed into the article instead of the Save dialog in Firefox,"Intention:
+Save a page.
+
+Steps to Reproduce:
+1. Rearrange a lot of text.
+
+2. Click the save button.
+
+3. Start typing the edit summary.
+
+Actual Results:  
+The edit summary appeared where I'd last been typing in the article, rather than in the Save dialog.
+
+I tried to reproduce it once, with no success.
+
+
+Reproducible: Couldn't Reproduce
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65222",1398648360,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-vugz2ayag65wyaecr7ve,task_description,resolved
+VisualEditor:  Edit summary typed into the article instead of the Save dialog in Firefox,"On reflection, I'm going to assume that this was caused by bug 65222 which is now resolved and so up-merging with that.
+
+*** This bug has been marked as a duplicate of bug 65222 ***",1401996489,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vugz2ayag65wyaecr7ve,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Formula
+3.Without closing the Math Inspector keep on pressing tab
+
+Observed Result:
+An error appears in the console:
+
+Uncaught  TypeError: Cannot read property 'start' of null
+
+See the screenshot attached
+
+Test Environment: https://en.wikipedia.org
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14000}",1398461400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_description,resolved
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,Verified the fix in production,1400011581,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,Verified the fix on test2,1399078153,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,Verified the fix on Betalabs,1398895353,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,"Change 129851 merged by jenkins-bot:
+Clear the focusedNode when the document is blurred
+
+https://gerrit.wikimedia.org/r/129851",1398469849,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null,"Pressing tab actually blurs the surface, but blurring the surface doesn't clear the focusedNode highlighting, so I'm fixing that first.",1398468542,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jvicijhnnvmkmtkj4r5b,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error","Steps to Reproduce:
+1. Open any page in VisualEditor.
+
+2. Go to Insert > Reference to add a reference.  Do NOT click inside the reference box.
+
+3. Go to Insert > Template to add a template.
+
+
+
+Actual Results:  
+You can't add a template, you can't exit the dialog, you can't do anything except close the browser tab and lose all of your work.
+
+
+Reproducible: Always
+
+This cannot be reproduced in Safari.  This cannot be reproduced if you first click inside the reference box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398443040,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_description,resolved
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Verified the fix in production,1400012136,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Verified the fix on test2,1399405833,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error","(In reply to Rainer Rillke @commons.wikimedia from comment #4)
+> Where is the gerrit change?
+
+https://gerrit.wikimedia.org/r/#/c/129806/ makes sure the tools correctly initialize as disabled if the initial selection is null
+
+https://gerrit.wikimedia.org/r/#/c/130262/ makes sure the selection isn't 0,0 the second time you open the reference dialog",1399067016,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Where is the gerrit change?,1399066128,PHID-USER-fgjrqsoj4hk6ezzjdea4,True,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",*** Bug 64601 has been marked as a duplicate of this bug. ***,1399065928,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Verified the fix in Betalabs,1398896444,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+"VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error",Fixed in the Firefox-selection change Ed wrote.,1398889785,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-n2qnl3eqyqev6tdkohxz,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398377400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j4en6ingifxpa67vre45,task_description,resolved
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,Moved to a different bug.,1412802831,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,This is again happening on Betalabs,1412738904,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,Verified the fix in production,1399067933,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,Verified the fix in test2,1399067406,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Change 130804 merged by Catrope:
+Always fix up selection after ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/130804",1398907814,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Change 130804 had a related patch set uploaded by Catrope:
+Always fix up selection after ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/130804",1398907631,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,Verified the fix in Betalabs with Firefox 27.0.1,1398889730,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Change 130262 merged by jenkins-bot:
+Always fix up selection after ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/130262",1398731458,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Change 130262 had a related patch set uploaded by Esanders:
+Always fix up selection on after ce.Surface#focus
+
+https://gerrit.wikimedia.org/r/130262",1398730973,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Reference
+3.Type something fast inside the reference dialog box
+
+Observed Result:
+The first character of the text moves to the next line in reference dialog box
+
+Test Environment: production
+Browser: FF 25
+OS: MAC OS X 10. 8. 5",1398377638,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox,"Created attachment 15208
+Screenshot
+
+**Attached**: {F13881}",1398377616,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-j4en6ingifxpa67vre45,task_subcomment,NA
+VisualEditor: [Regression wmf2] Loading spinner appears in the Media Settings dialog while loading it for the first time,"screenshot of the loading spinner
+
+There is a loading spinner appears on the Media Settings dialog box when I try to load it for the first time in a page.
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13831}",1398364020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vfdslw5rczsnlnpgu752,task_description,invalid
+VisualEditor: [Regression wmf2] Loading spinner appears in the Media Settings dialog while loading it for the first time,Expected behaviour.,1398365417,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vfdslw5rczsnlnpgu752,task_subcomment,NA
+VisualEditor: Snowmen inserted (or other bad breakage) with certain easy combinations of actions/keys that move the cursor out of the document,"<Krenair> Move the cursor to the end of a line before the start of a new section header, delete, enter, enter, up, delete, type a random character.
+<James_F> Backwards delete or forwards delete?
+<Krenair> Um. The delete next to 'Home' and 'End'
+<Krenair> not backspace
+<James_F> Forwards, then. :-)
+<James_F> Whee, snowmen.
+<James_F> I blame edsanders.
+<Krenair> observed on http://en.wikipedia.org/wiki/Hippeastrum_calyptratum, depending on what random character you try (I hit 'f'), stuff breaks in a difficult to explain but quite obvious
+<Krenair> especially if you do it twice to the same document
+<James_F> So the first thing that happens is that the cursor ends up outside of the document.
+<James_F> Which is Bad™.
+<James_F> Everything breaking after this is non-deterministic, but definitely also Bad™.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398297840,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qamxjhmoqqas27inzryu,task_description,resolved
+VisualEditor: Snowmen inserted (or other bad breakage) with certain easy combinations of actions/keys that move the cursor out of the document,"Change 129371 merged by jenkins-bot:
+Re-render selection after deleting
+
+https://gerrit.wikimedia.org/r/129371",1398310207,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qamxjhmoqqas27inzryu,task_subcomment,NA
+VisualEditor: Snowmen inserted (or other bad breakage) with certain easy combinations of actions/keys that move the cursor out of the document,"Change 129371 had a related patch set uploaded by Catrope:
+Rerender selection after deleting.
+
+https://gerrit.wikimedia.org/r/129371",1398310077,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qamxjhmoqqas27inzryu,task_subcomment,NA
+VisualEditor: Snowmen inserted (or other bad breakage) with certain easy combinations of actions/keys that move the cursor out of the document,"If you put the cursor at the end of a paragraph and press Delete, the cursor will go to the top left corner of the surface (range (0,0)). However, if the next thing after the cursor is not a paragraph (but e.g. a heading) this doesn't happen.
+
+Once the cursor is at (0,0) and you start typing, things break completely.",1398309644,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qamxjhmoqqas27inzryu,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in FireFox
+2.Go to Insert>Template
+3.Type something in the textbox to search for templates
+4.Now without selecting anything from the dropdown box, click on ""Add template""
+
+Observed Result:
+The dropbox for the search results gets sticked to the template dialog box 
+If you click on Show options button or just close the template dialog box and reopen again, it still stays
+
+
+This problem also exists for the search result dropbox for Redirect Target Page and Categories 
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13701}",1398295380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ousahplumt5sf7vusapd,task_description,resolved
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open",Verified in production,1400188852,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open",Verified the fix in test2,1400017549,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Change 131608 merged by jenkins-bot:
+Make autoFocus default to true
+
+https://gerrit.wikimedia.org/r/131608",1399324046,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Change 131608 had a related patch set uploaded by Catrope:
+Make autoFocus default to true.
+
+https://gerrit.wikimedia.org/r/131608",1399323887,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","For template, if you click on add template button quickly as soon as the dropbox appears you will be able to reproduce it.
+For Redirect Page and Categories, it can be reproduced in pretty straightforward way",1399076093,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open",This is still occurring in Betalabs and test2,1399068171,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Change 130767 merged by jenkins-bot:
+Auto-choose selected item when adding a template
+
+https://gerrit.wikimedia.org/r/130767",1398903238,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Change 130767 had a related patch set uploaded by Catrope:
+Auto-choose selected item when adding a template
+
+https://gerrit.wikimedia.org/r/130767",1398903085,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Created attachment 15189
+Redirect page
+
+**Attached**: {F13704}",1398295534,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+"VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open","Created attachment 15188
+category
+
+**Attached**: {F13702}",1398295457,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ousahplumt5sf7vusapd,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"<Krenair> The issue I get after adding ConfirmEdit to my wiki is ""Error: Unknown error"" when saving >_>
+<Krenair> {""visualeditoredit"":{""result"":""error"",""edit"":{""captcha"":{""type"":""simple"",""mime"":""text/plain"",""id"":""586723432"",""question"":""24+8""},""result"":""Failure""}}}
+<James_F> Hmm.
+<James_F> That kind of CAPTCHA isn't supported yet.
+<Krenair> meh. thought it would be something like that
+<James_F> You'd need to add it to the save dialog's logic.
+[...]
+<James_F> Krenair: It's worth adding support, feel free to make a bug (I don't have a list of CAPTCHA methods to support).
+
+I think at least Simple, Math, and Questy. Currently it looks like Fancy is supported though I haven't tested it
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398290340,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-upntlx7j3bdz3r52gesp,task_description,resolved
+VisualEditor: Add support for more types of ConfirmEdit captcha,From Alex: Yes.,1398978897,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"QuestyCaptcha and MathCaptcha both done too.
+
+Is Fancy sufficiently supported that we can close this?",1398893679,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"Change 129570 merged by jenkins-bot:
+Support QuestyCaptcha and (kind of) MathCaptcha
+
+https://gerrit.wikimedia.org/r/129570",1398893646,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"Change 129570 had a related patch set uploaded by Jforrester:
+Support QuestyCaptcha and (kind of) MathCaptcha
+
+https://gerrit.wikimedia.org/r/129570",1398372212,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"Change 129315 merged by jenkins-bot:
+Add support for SimpleCaptcha
+
+https://gerrit.wikimedia.org/r/129315",1398301771,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,Simple done. :-),1398301709,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+VisualEditor: Add support for more types of ConfirmEdit captcha,"Change 129315 had a related patch set uploaded by Alex Monk:
+Add support for SimpleCaptcha
+
+https://gerrit.wikimedia.org/r/129315",1398292000,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-upntlx7j3bdz3r52gesp,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Screenshot
+
+I tried to save which was open for a long time (probably ~3-4 hrs)and got the following error in the console which stopped me from saving the edited content:
+
+Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13580}",1398210960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_description,resolved
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while",Verified the fix in production,1399052386,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while",Verified the fix in test2,1398990077,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Change 129326 merged by Catrope:
+Unbreak badtoken recovery on mobile
+
+https://gerrit.wikimedia.org/r/129326",1398295542,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Change 129326 had a related patch set uploaded by Catrope:
+Unbreak badtoken recovery on mobile
+
+https://gerrit.wikimedia.org/r/129326",1398295516,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Change 129243 merged by jenkins-bot:
+Unbreak badtoken recovery on mobile
+
+https://gerrit.wikimedia.org/r/129243",1398283165,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while","Change 129243 had a related patch set uploaded by Catrope:
+Unbreak badtoken recovery on mobile
+
+https://gerrit.wikimedia.org/r/129243",1398281605,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+"VisualEditor Mobile: ""Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' "" appears while trying to save a page which was idle for a while",This looks like a bug in ve.init.mw.Target :(,1398279478,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pgl7oiy2l6bvk7hzunv7,task_subcomment,NA
+VisualEditor: [Regression] Can't remove annotation,"I challenge you!
+VEdit https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&oldid=65498176.
+Make the first line bold. Then un-bold it. I don't manage to.
+Win7, Vector, Chrome/FF.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398174780,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7xyquvj6hhetuc547oo3,task_description,resolved
+VisualEditor: [Regression] Can't remove annotation,"Change 129074 merged by jenkins-bot:
+Look for comparable annotations when toggling
+
+https://gerrit.wikimedia.org/r/129074",1398298640,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7xyquvj6hhetuc547oo3,task_subcomment,NA
+VisualEditor: [Regression] Can't remove annotation,"Change 129074 had a related patch set uploaded by Esanders:
+Look for comparable annotations when toggling
+
+https://gerrit.wikimedia.org/r/129074",1398210011,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7xyquvj6hhetuc547oo3,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"Before applying the changes
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Cite>Website/Book/Newspaper/Journal
+3.Add some optional parameters from the parameter list 
+4.Also add the parameter URL as an optional parameter
+5.Apply changes
+
+Observed Result:
+Observe that, before applying changes the parameter URL does not have a trash icon beside but the other optional parameter does.But, after applying the changes , the trash icon does appear for the parameter URL but not for the other one.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/21staprilchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14025}",1398108060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ntqqbxxddzdo7yltukgf,task_description,resolved
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"Change 129344 merged by jenkins-bot:
+Make citation dialog display like transclusion dialog in single mode
+
+https://gerrit.wikimedia.org/r/129344",1398301797,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"Change 129344 had a related patch set uploaded by Trevor Parscal:
+Make citation dialog display like transclusion dialog in single mode
+
+https://gerrit.wikimedia.org/r/129344",1398299815,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"This is only broken in the citation inspector, it works fine in the template inspector.",1398112544,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"It seems that the logic here is that:
+* When creating a new citation, none of the default parameters can be removed
+* When inspecting an existing citation, only the first (topmost) parameter can be removed
+* After adding a new parameter, only that parameter can be removed",1398112378,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog,"Created attachment 15151
+After applying changes
+
+**Attached**: {F14026}",1398108328,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ntqqbxxddzdo7yltukgf,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Current extension repositories have REL1_23 branch, but it was created when REL1_22 was created too, so basically it's outdated.
+
+Examples:
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FCite.git
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FImageMap.git
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FCheckUser.git
+
+They have REL1_23 updated as of 22-10-2013
+
+I've only found one exception, though:
+
+https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FWidgets.git
+
+
+One particular change introduced on 1.23 release was the migration from PHP to JSON files for i18n. I think all the extensions were migrated to JSON files in master, but REL1_23 still doesn't have that change.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67270",1398010200,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-crppoo23swkvxppmtyyo,task_description,resolved
+Update branches in mediawiki/extensions/* for REL1_23,"Thanks @hashar!
+
+`defaultbranch` has since been removed from `.gitreview` (so now it submits to the upstream branch by default), so this is not an ongoing problem.",1485543614,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,thanks!,1485532627,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"For Bundled extensions:
+
+for ext in Cite ConfirmEdit Gadgets ImageMap InputBox Interwiki LocalisationUpdate Nuke ParserFunctions PdfHandler Poem Renameuser SpamBlacklist SyntaxHighlight_GeSHi TitleBlacklist WikiEditor; do echo -n ""$ext ""; git -C $ext show REL1_23:.gitreview|grep defaultbranch; done;
+
+|Cite | defaultbranch=master
+|ConfirmEdit | defaultbranch=REL1_23
+|Gadgets | defaultbranch=master
+|ImageMap | defaultbranch=master
+|InputBox | defaultbranch=master
+|Interwiki | defaultbranch=master
+|LocalisationUpdate | defaultbranch=master
+|Nuke | defaultbranch=master
+|ParserFunctions | defaultbranch=master
+|PdfHandler | defaultbranch=master
+|Poem | defaultbranch=master
+|Renameuser | defaultbranch=master
+|SpamBlacklist | defaultbranch=master
+|SyntaxHighlight_GeSHi | defaultbranch=master
+|TitleBlacklist | defaultbranch=master
+|WikiEditor | defaultbranch=master
+
+Fixed them all.
+
+I also fixed extensions that had recent changes.
+
+So it is mostly done. Given the traffic on `REL1_23` I don't think it is worth fixing all the rest.
+",1485514996,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334546 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334546]]",1485514960,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334546 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334546]]
+",1485514957,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334545 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334545]]",1485514911,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334545 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334545]]
+",1485514908,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334544 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334544]]",1485514859,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334544 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334544]]
+",1485514856,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334543 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334543]]",1485514822,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334543 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334543]]
+",1485514819,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334542 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334542]]",1485514791,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334542 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334542]]
+",1485514780,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334540 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334540]]",1485514699,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334539 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334539]]",1485514697,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334538 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334538]]",1485514694,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334537 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334537]]",1485514692,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334536 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334536]]",1485514690,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334535 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334535]]",1485514688,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334534 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334534]]",1485514686,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334533 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334533]]",1485514684,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334532 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334532]]",1485514682,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334531 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334531]]",1485514680,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334530 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334530]]",1485514678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334529 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334529]]",1485514676,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334528 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334528]]",1485514674,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334527 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334527]]",1485514671,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334526 merged by Hashar:
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334526]]",1485514669,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334540 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334540]]
+",1485514248,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334539 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334539]]
+",1485514245,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334538 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334538]]
+",1485514242,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334537 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334537]]
+",1485514239,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334536 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334536]]
+",1485514235,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334535 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334535]]
+",1485514232,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334534 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334534]]
+",1485514230,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334533 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334533]]
+",1485514227,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334532 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334532]]
+",1485514224,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334531 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334531]]
+",1485514221,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334530 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334530]]
+",1485514218,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334529 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334529]]
+",1485514215,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334528 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334528]]
+",1485514211,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334527 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334527]]
+",1485514209,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Change 334526 had a related patch set uploaded (by Hashar):
+.gitreview: update defaultbranch to REL1_23
+
+[[https://gerrit.wikimedia.org/r/334526]]
+",1485514206,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"The initial requests was to bump MediaWiki extensions REL1_23 branches and I guess all the bump that were required have been done quite quickly. So that is essentially done.
+
+
+The task apparently was left open to update `.gitreview` files. From July 2014 comment:
+
+>>! In T66157#704385, @Tgr wrote:
+> Not sure, if this is a bug in the one-off update process, or something that is generally not handled when creating new versions of extensions, but the .gitreview file in the root extension folder should have defaultbranch=REL1_23 but it has defaultbranch=master instead. (I have run into this in MultimediaViewer and UploadWizard; I assume it's the same for all others.)
+
+I checked extensions from mediawiki/extensions.git with:
+
+   git submodule foreach 'git show origin/REL1_23:.gitreview|grep defaultbranch||:'
+
+A wide range of them still have a .gitreview file with `defaultbranch=master`
+
+
+Looking in Gerrit for [[ https://gerrit.wikimedia.org/r/#/q/branch:REL1_23+project:%255Emediawiki/extensions/.*+NOT+project:%255Emediawiki/extensions/BlueSpice.* | branch:REL1_23 project:^mediawiki/extensions/.* NOT project:^mediawiki/extensions/BlueSpice.* ]] there are a few repo still active. And the .gitreview files are wrong :(
+
+
+",1485513144,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"On my radar, but unsure of exact situation anymore. @MarkAHershberger can you give an update on this task?",1465936763,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Moving this into RelEng's orbit more clearly; however, I imagine this isn't going to get done given it's been two years, and can just be closed as Declined or somesuch?",1465833665,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,I'll use this one.,1412864239,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"hexmode:
+> Are you going to use this bug to track that or open a new one?",1412767995,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Mark A. Hershberger from comment #28)
+> (In reply to Tisza Gergő from comment #27)
+> > Not sure, if this is a bug in the one-off update process, or something that
+> > is generally not handled when creating new versions of extensions, but the
+> > .gitreview file in the root extension folder should have
+> > defaultbranch=REL1_23 but it has defaultbranch=master instead. (I have run
+> > into this in MultimediaViewer and UploadWizard; I assume it's the same for
+> > all others.)
+> 
+> This is something we should update our branching script to take care of.
+
+Are you going to use this bug to track that or open a new one? Just don't want this to be lost in the aether...",1411592480,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Tisza Gergő from comment #27)
+> Not sure, if this is a bug in the one-off update process, or something that
+> is generally not handled when creating new versions of extensions, but the
+> .gitreview file in the root extension folder should have
+> defaultbranch=REL1_23 but it has defaultbranch=master instead. (I have run
+> into this in MultimediaViewer and UploadWizard; I assume it's the same for
+> all others.)
+
+This is something we should update our branching script to take care of.",1411409718,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Not sure, if this is a bug in the one-off update process, or something that is generally not handled when creating new versions of extensions, but the .gitreview file in the root extension folder should have defaultbranch=REL1_23 but it has defaultbranch=master instead. (I have run into this in MultimediaViewer and UploadWizard; I assume it's the same for all others.)",1406140429,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Fixed the ones in Comment 19.  Emailed a couple of q's to developers about the right revision to use, but it should be fixed now.",1404535834,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,*** Bug 67270 has been marked as a duplicate of this bug. ***,1404240941,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,The upload wizard case is fixed by https://gerrit.wikimedia.org/r/141586,1403562681,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Mark A. Hershberger from comment #16)
+> After looking through the bugs with fixes for UW, I found the following
+> three that seem like good candidates for backports:
+> 
+> Bug #54750 - UploadWizard allows two different files with same name at same
+> time
+> Bug #64067 - Pg Support
+> Bug #65406 - Flikr support
+
+Agreed, these are good candidates for backport. None of them are critical though.
+
+> Without more information, it is impossible to tell if fixing these will
+> address comment #12:
+> > UploadWizard is also affected by this, and as a result it is completely
+> > broken on 1.23.
+
+That would be addressed by moving all the missing commits (between 2013-10-24 and 2014-04-10) into REL1_23. Specifically, UW is broken because this commit from 2013 December is missing:
+http://git.wikimedia.org/commit/mediawiki%2Fextensions%2FUploadWizard/8bd13ac4317f48336f90a39723d142628eb906e9",1403417575,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Mark A. Hershberger from comment #21)
+> Others, like WikimediaMessages, suffer from the problem of
+> d373fd87b17bfb67f6616011ec1faa2531e58878 -- where the committer ""This, that
+> and the other"" made a commit indicating ""Update for release of MW 1.23""
+> without merging it with REL1_23 or requesting a backport.
+
+I don't think that patch needs to be backported, as the change is only relevant to mediawikiwiki, which is on 1.24wmfX by now.
+
+Since WikimediaMessages is a WMF-only extension I don't understand why it needs release branches in the first place.",1403406168,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Looks like UW -- and others branched before April 22 -- would benefit from a bit of work.
+
+Others, like WikimediaMessages, suffer from the problem of d373fd87b17bfb67f6616011ec1faa2531e58878 -- where the committer ""This, that and the other"" made a commit indicating ""Update for release of MW 1.23"" without merging it with REL1_23 or requesting a backport.",1403401254,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Number of extensions with last commit on REL1_23 that was in April and the message was ""Localisation updates from http://translatewiki.net."" or ""Update i18n shim"": 470
+
+The extensions on comment #19 all had the last message ""Localisation updates..."" except for SyntaxHighight_GeSHi and TwnMainPage.
+
+
+Remaining extensions:
+
+BlueSpiceExtensions REL1_23 57ae783 Tue Apr 8 11:20:14 2014 +0200 Fix spelling: occurred
+CategoryTree REL1_23 c7333ea Fri Jun 6 11:44:02 2014 +0200 Register CategoryTreeMagic from global scope instead of setup
+Collection REL1_23 bf7c4b9 Thu Apr 24 20:52:39 2014 +0100 Fatal error: Unsupported operand types in Collection.body.php
+ConfirmAccount REL1_23 e4f00be Tue Apr 22 15:09:02 2014 +0000 Add support for request account link
+ConfirmEdit REL1_23 0c63352 Mon Apr 7 19:25:45 2014 +0200 SimpleCaptcha: Move the equals sign inside the <label/>
+DPLforum REL1_23 01211c5 Fri Jun 6 17:32:19 2014 +0300 Fix DPLforum b0rkage.
+DataTransfer REL1_23 24f7782 Tue Jun 17 14:00:56 2014 +0200 Fix incorrect path in $wgMessagesDirs
+Disambiguator REL1_23 cf11744 Fri May 9 19:04:52 2014 +0100 Fix table prefixing in SpecialDisambiguationPages
+Math REL1_23 d0e998f Wed Apr 16 19:39:10 2014 -0700 Simplify VE inspector code by extending new MWLiveExtensionInspector
+MobileFrontend REL1_23 984e276 Mon May 12 14:29:25 2014 -0700 Fix XSS in section handling
+Nuke REL1_23 ba618ff Thu Jun 5 14:17:17 2014 +0100 chmod -x Nuke.alias.php Nuke_body.php Nuke.hooks.php Nuke.i18n.php Nuke.php SpecialNuke.php
+NumberFormat REL1_23 70be63c Mon Jun 16 21:13:13 2014 +0600 fix bug with negative numbers (version 0.8.0)
+PagedTiffHandler REL1_23 1e2be08 Tue Apr 22 09:34:03 2014 +0200 mark method visibleMetadataFields as public
+ProofreadPage REL1_23 86fa295 Tue Apr 15 21:01:56 2014 +0200 Fills $params to recursive calls of preloadTransform
+VisualEditor REL1_23 82dc0cb Wed May 21 09:33:19 2014 -0700 [browser test] Dismiss new confirm dialog
+Wikibase REL1_23 d2ed0cc Mon Apr 14 21:13:23 2014 +0000 Merge ""Add documentation for badgeItems setting on repo""",1403400384,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Extensions that look like they were branched on Oct 24:
+
+SolrStore REL1_23 5dabd1e Thu Oct 24 20:50:10 2013 +0000
+SpamBlacklist REL1_23 d6bd4c1 Thu Oct 24 20:50:16 2013 +0000
+SphinxSearch REL1_23 4a24249 Thu Oct 24 20:50:22 2013 +0000
+SubPageList REL1_23 a68966d Thu Oct 24 20:50:26 2013 +0000
+Sudo REL1_23 98bd893 Thu Oct 24 20:50:33 2013 +0000
+SyntaxHighlight_GeSHi REL1_23 2f064f4 Thu Oct 24 05:51:03 2013 +0000
+TemplateData REL1_23 26dacfc Thu Oct 24 20:50:37 2013 +0000
+TemplateSandbox REL1_23 1e880cc Thu Oct 24 20:50:40 2013 +0000
+Thanks REL1_23 22333e0 Thu Oct 24 20:50:46 2013 +0000
+ThrottleOverride REL1_23 e122ac6 Thu Oct 24 20:50:50 2013 +0000
+TimedMediaHandler REL1_23 7bd2b47 Thu Oct 24 20:50:54 2013 +0000
+Translate REL1_23 dfee4f4 Thu Oct 24 20:51:04 2013 +0000
+TranslateSvg REL1_23 5d30452 Thu Oct 24 20:51:11 2013 +0000
+TranslationNotifications REL1_23 5537a12 Thu Oct 24 20:51:18 2013 +0000
+TwnMainPage REL1_23 016ea86 Thu Oct 24 21:19:02 2013 +0000
+TwoFactorAuthentication REL1_23 e2fb0cc Thu Oct 24 20:51:31 2013 +0000
+UploadWizard REL1_23 9b39bd9 Thu Oct 24 20:51:37 2013 +0000
+Validator REL1_23 3c3997a Thu Oct 24 20:51:44 2013 +0000",1403399010,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Created attachment 15695
+differences between bundled version of spamblacklist in 1.22 and 1.23
+
+I only see l10n diffs for the bundled versions of SpamBlacklist, but they aren't the same.
+
+$ git log -1 --pretty=format:""%h%x09%an%x09%ad"" origin/REL1_23
+d6bd4c1 Translation updater bot Thu Oct 24 20:50:16 2013 +0000
+$ git log -1 --pretty=format:""%h%x09%an%x09%ad"" origin/REL1_22
+f91ad56 Translation updater bot Tue Oct 22 19:21:30 2013 +0000
+
+So, year, not the right place for a branch, but not the same thing. No clue yet why this happened.
+
+**Attached**: {F13932}",1403385148,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"non-l10n changes in UploadWizard since it was branched: https://gerrit.wikimedia.org/r/#/q/status:merged+project:mediawiki/extensions/UploadWizard+branch:master+-owner:L10n-bot,n,z",1403383468,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(Missed a couple of lines for the above script bit:
+  rel123=`git log -1 --oneline origin/REL1_23 2>&1`
+  rel122=`git log -1 --oneline origin/REL1_22 2>&1`
+)
+
+UploadWizard was branched on 2014-Apr-14.  Some bugs (bug #47161, bug #53245, bug #40147, bug #64908, bug #63921, bug #64067, bug #64883 and others below) were addressed with patches but no indication was made that a backport should be considered.
+
+After looking through the bugs with fixes for UW, I found the following three that seem like good candidates for backports:
+
+Bug #54750 - UploadWizard allows two different files with same name at same time
+Bug #64067 - Pg Support
+Bug #65406 - Flikr support
+
+Without more information, it is impossible to tell if fixing these will address comment #12:
+> UploadWizard is also affected by this, and as a result it is completely
+> broken on 1.23.",1403383066,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Comment on attachment 15693
+Submodules under extensions w/o commits for 1.23
+
+The following script was used to create this file:
+
+ lines=`git log --oneline --before 2014-04-10 --after 2013-10-10 | wc -l`
+ branch123=`git branch -a | grep origin/REL1_23 | wc -l`
+ branch122=`git branch -a | grep origin/REL1_22 | wc -l`
+ echo REL1_23: $branch123 REL1_22 $branch122 lines $lines
+ if [ ""$lines"" -eq ""0"" -a ""$rel123"" == ""$rel122"" ]; then
+    echo REL1_23 == REL1_22 for $ext
+    echo $ext >> /tmp/122=123
+ fi",1403381195,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Created attachment 15693
+Submodules under extensions w/o commits for 1.23
+
+This file was generated by using an up-to-date extensions checkout (with updates submodules) and listing those submodules without any commit between 2014-04-10 (when REL1_23 was created) and 2013-10-10 (~when REL1_22 was created).  This will help determine when REL1_22 should be the same as REL1_23.
+
+**Attached**: {F13931}",1403381064,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Greg / hexmode / Markus:  Will anybody fix this? It's been open for two months and creates followup issues, confusion, brokenness (bug 66866).",1403264281,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"UploadWizard is also affected by this, and as a result it is completely broken on 1.23.",1403123732,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"It looks like some extensions including SyntaxHighlight_GeSHi and SpamBlacklist were not fixed, and as a result the 1.22 versions of these two extensions are in the 1.23.0 tarball.",1402006976,PHID-USER-7ggbl2sm3bxckkmp6uw3,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,Wrote a script to remove the faulty REL1_23 branches (since I couldn't just push a new one).  Should all be fixed now.,1398103255,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,Fixed BlueSpiceFoundation,1398093136,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Fixed those in comment #0, looking for more problems.",1398092244,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"It looks like some of the problem is confusion between gerrit and gitblit.  For example, https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FSemanticMediaWiki.git shows REL1_23 on 2013-10-24.
+
+A fresh checkout from gerrit, though, shows the last commit on REL1_23 to be 26923ba5d306b24afe3e8d71f3f065139fd593c6 on 2014-04-14.
+
+Hmmm, and part of what I'm running into here is caching.  Opening the branch listing in a new browser shows what I expect.
+
+Another part of the problem is that I did initially make a mistake of branching the wrong code.  When I discovered that I got a pointer from Chad on how to fix the problem.  Evidently, though, this happened in more places than I realized.",1398091152,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"Like I say, ProofreadPage was massively out of date too. Now fixed though",1398090274,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #0)
+> One particular change introduced on 1.23 release was the migration from PHP
+> to JSON files for i18n. I think all the extensions were migrated to JSON
+> files in master, but REL1_23 still doesn't have that change.
+
+Any extensions that have i18n files will need to be updated, but some, like Auth_remoteuser, are fine as is.
+
+Thank you for pointing out this problem before the release!",1398089169,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"(In reply to Mark A. Hershberger from comment #3)
+> That is, the dates you see on the branch page are the dates of the last
+> commit on that branch, not when the branch was made.
+> 
+> I created most of these REL1_23 branches last week.
+
+That doesn't seem right. As I said in comment #0, a lot of extensions were changed to have i18n messages in JSON files instead of PHP, and that was done weeks before REL1_23 was branched on master (it's in REL1_23 in core). But REL1_23 on the extensions I've linked as example doesn't include this change, among others that were merged on master after October 2013.
+
+I've manually checked some of those extensions, downloading from git for that branch name and they aren't migrated, while if I switch to master they have the new JSON files.",1398088401,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"If you look at Auth_remoteuser (https://git.wikimedia.org/branches/mediawiki%2Fextensions%2FAuth_remoteuser.git), you'll see that REL1_21, REL1_22, and REL1_23 were all apparently branched when REL1_20 was created.
+
+From this I conclude that there were no changes on master between the time that REL1_20 was created and when REL1_23 was created.  And the history seems to confirm this: https://git.wikimedia.org/log/mediawiki%2Fextensions%2FAuth_remoteuser.git/refs%2Fheads%2Fmaster
+
+That is, the dates you see on the branch page are the dates of the last commit on that branch, not when the branch was made.
+
+I created most of these REL1_23 branches last week.",1398087801,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"I fixed ProofreadPage by having Chad enable force push, and pushing to update the remote REL1_23 branch.
+
+
+Why were the REL1_23 branches created at the branching point of REL1_22? :/",1398084051,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+Update branches in mediawiki/extensions/* for REL1_23,"While we're on it, could please whoever is in charge of releasing new MediaWiki versions, add also a note to check extension branches to the steps to create a new release? Every major release since we're on git have the same problem!! (usually REL1_XX branch is not created when the new release is done in core)
+
+See also bug 48837",1398010764,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-crppoo23swkvxppmtyyo,task_subcomment,NA
+VisualEditor: Deleting a paragraph separator and subsequently typing any character messes up the page,"Steps to reproduce:
+
+1. Go to (say) https://en.wikipedia.org/w/index.php?title=Visual_editor&veaction=edit
+
+2. Place the cursor after the end of a paragraph (e.g. after the full stop in ""editors are."")
+
+3. Hit the delete key to merge the paragraph with the subsequent one.
+
+4. Type any character (a letter, blank, etc.)
+
+Result: Chaos ;) - large swaths of text are deleted, and (apparently) random characters appear near the beginning of the page.
+
+Reproduced in Chromium (Version 33.0.1750.152) and Firefox (28.0).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62333",1397889240,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-wbcmbobk54vghobxtvq5,task_description,resolved
+VisualEditor: Deleting a paragraph separator and subsequently typing any character messes up the page,"Yes, works for me too now in Chromium and Firefox.",1402354099,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-wbcmbobk54vghobxtvq5,task_subcomment,NA
+VisualEditor: Deleting a paragraph separator and subsequently typing any character messes up the page,"Works for me, probably resolved at some point in the last couple of months.",1402312928,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wbcmbobk54vghobxtvq5,task_subcomment,NA
+VisualEditor: [Regression] Citation dialog does not focus correct field when adding a new parameter,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a Cite option like Cite Website/Cite Journal
+3.Add some value for a parameter
+4.Click on ""Add Parameter""
+5.Select a parameter
+
+Observed Result:
+
+The cursor instead of moving to the new parameter, stays at the last edited parameter box
+
+
+Test Environment:  http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397846160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5yohjyriweszqbp34vz6,task_description,resolved
+VisualEditor: [Regression] Citation dialog does not focus correct field when adding a new parameter,Verified the fix on production,1400011923,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5yohjyriweszqbp34vz6,task_subcomment,NA
+VisualEditor: [Regression] Citation dialog does not focus correct field when adding a new parameter,Verified the fix on Betalabs,1399069800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5yohjyriweszqbp34vz6,task_subcomment,NA
+VisualEditor: [Regression] Citation dialog does not focus correct field when adding a new parameter,*** Bug 64201 has been marked as a duplicate of this bug. ***,1398112734,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5yohjyriweszqbp34vz6,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a citation or a reference
+
+Observed Result:
+The cursor jumps to the beginning of the document 
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397693880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_description,resolved
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,Verified the fix in production (en.wiki),1404767619,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"So, this issue did get re-introduced in wmf 10, and then got somehow resolved in wmf 11, Because I am getting it in production running wmf 10 but not on test2 running wmf 11.
+Therefore , I am changing the target milestone accordingly.",1403897953,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"(In reply to Ed Sanders from comment #9)
+> Works in master.
+
+Doesn't work in Beta Labs, which is running master AFAICT.",1403291952,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,Works in master. Deployment issue?,1403291406,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,This bug has been reborn in wmf 10,1403289668,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,Verified on betalabs for Cite options too,1398189179,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,Verified by adding template in test2,1398124127,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Change 127698 merged by Catrope:
+Add focusing state flag to ce.Surface when programatically focusing
+
+https://gerrit.wikimedia.org/r/127698",1398119444,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Change 127698 had a related patch set uploaded by Catrope:
+Add focusing state flag to ce.Surface when programatically focusing
+
+https://gerrit.wikimedia.org/r/127698",1398109444,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Change 127136 merged by jenkins-bot:
+Add focusing state flag to ce.Surface when programatically focusing
+
+https://gerrit.wikimedia.org/r/127136",1398107342,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,"Change 127136 had a related patch set uploaded by Esanders:
+Add focusing state flag to ce.Surface when programatically focusing
+
+https://gerrit.wikimedia.org/r/127136",1397764749,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references,This happens after adding a template too.,1397759470,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yarhuzhed4wqvpw62gpb,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open any page with mobile VE
+2.Add a text
+3.Save the page 
+4.Reopen the page
+5.Go to the next line of the text you added in step 2
+6.Start typing something
+
+Observed Result:
+The following error appears in the console
+
+Uncaught TypeError: Cannot read property 'nextSibling' of undefined
+
+See the screenshot attached
+
+Test Environment:http://en.m.wikipedia.beta.wmflabs.org/
+Page:http://en.m.wikipedia.beta.wmflabs.org/wiki/0.4040571254571662?title=0.4040571254571662&campaign=random#editor/0
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13635}",1397686200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atiq5mebijzmzfpmqye2,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,Verified the fix in: https://en.m.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/Sandbox,1398379043,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,Verified the fix on test2,1398127291,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 127380 merged by jenkins-bot:
+Also destroy target when exiting without saving changes
+
+https://gerrit.wikimedia.org/r/127380",1398120865,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 127380 had a related patch set uploaded by Jforrester:
+Also destroy target when exiting without saving changes
+
+https://gerrit.wikimedia.org/r/127380",1397859900,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 127364 merged by jenkins-bot:
+Also destroy target when exiting without saving changes
+
+https://gerrit.wikimedia.org/r/127364",1397856078,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 127364 had a related patch set uploaded by Catrope:
+Also destroy target when exiting without saving changes
+
+https://gerrit.wikimedia.org/r/127364",1397853717,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 126881 merged by jenkins-bot:
+Destroy the VE target after saving
+
+https://gerrit.wikimedia.org/r/126881",1397695959,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE,"Change 126881 had a related patch set uploaded by Catrope:
+Destroy the VE target after saving
+
+https://gerrit.wikimedia.org/r/126881",1397694773,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atiq5mebijzmzfpmqye2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,"Screenshot
+
+Steps to reproduce:'
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Click on ""Show options""
+
+Observed Result
+The template icon and the trash icon is overlapping with ""Add template"" button
+The NEw template heading is appearing below the textbox
+
+Try to add a content/parameter its broken for them too
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13598}",1397677140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_description,resolved
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,Verified the fix on production,1398385885,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,verified the fix on test 2,1397862572,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,Verified the fix on Betalabs,1397759374,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,"Change 126869 merged by jenkins-bot:
+Followup 099f26ec: fix $content in FieldsetLayout
+
+https://gerrit.wikimedia.org/r/126869",1397698884,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,"Change 126869 had a related patch set uploaded by Catrope:
+Followup 099f26ec: fix $content in FieldsetLayout
+
+https://gerrit.wikimedia.org/r/126869",1397690635,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs,"Created attachment 15121
+parameter textbox
+
+**Attached**: {F13599}",1397677210,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h2scyo6a2vi7fzgxwmg2,task_subcomment,NA
+VisualEditor: Copy-Paste of a block of HTML disables all further copy-paste of anything: FF28 on Linux,"* Open https://www.mediawiki.org/w/index.php?title=Parsoid/Deployments&oldid=959448&veaction=edit
+* Copy the section starting @ ""Monday, April 14, 2014 around 1pm PST : Deployed fba548cb"" including the list upto the next section
+* Try pasting it -- nothing gets pasted.
+* Now try copy-pasting othe things (even simple strings) .. everything fails.
+
+Can consistently reproduce this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397671800,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-u7s5e2g4bwlbc7qkpfjc,task_description,resolved
+VisualEditor: Copy-Paste of a block of HTML disables all further copy-paste of anything: FF28 on Linux,"It's almost certainly because the copy-paste code fatals on come content currently, and doesn't bring itself back; up-merging into bug 66229 which asks for this to be fixed.
+
+*** This bug has been marked as a duplicate of bug 66229 ***",1402505914,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u7s5e2g4bwlbc7qkpfjc,task_subcomment,NA
+VisualEditor: Copy-Paste of a block of HTML disables all further copy-paste of anything: FF28 on Linux,Works for me.,1402501178,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-u7s5e2g4bwlbc7qkpfjc,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","**Author:** `swalling`
+
+**Description:**
+VE's edit surface has a body font size of 0.8em (equals 13px) which mismatches with the new default body font size (0.875em, which translates to 14px on Chrome and Firefox on most systems). The same is true for line-height, which is now 1.6em for body content. 
+
+We should make sure the two are consistent. The body font stack and heading settings do get translated to VE edit mode correctly, so we're close. :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63540",1397610060,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_description,resolved
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 130481 merged by jenkins-bot:
+vector: Apply content text style via .mw-body-content instead of #bodyContent
+
+https://gerrit.wikimedia.org/r/130481",1398813972,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)",Will back-port to wmf2 at least.,1398804515,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 130481 had a related patch set uploaded by Jforrester:
+vector: Apply content text style via .mw-body-content instead of #bodyContent
+
+https://gerrit.wikimedia.org/r/130481",1398804386,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 129563 merged by jenkins-bot:
+vector: Apply content text style via .mw-body-content instead of #bodyContent
+
+https://gerrit.wikimedia.org/r/129563",1398804366,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 129563 had a related patch set uploaded by Krinkle:
+Make new styles target .mw-content instead of #bodyContent
+
+https://gerrit.wikimedia.org/r/129563",1398772993,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","I'm not quite sure about the pre-typograpy-refresh situation, but it shouldn't be to different from the curent.
+
+Here's the situation now . We have #mw-head-base (tabs and personal links) and #content (#firstHeading, #bodyContent, #catlinks and everything in between). Both have a base fontsize of 1em and left-margin of 10/11em. They need to match, no matter what, to align the tabs with the content part of the page.
+
+Fontsize isn't actually set until deep inside the various parts:
+#p-personal li {font-size: 0.75em;},
+div.portal div.body ul li {font-size: 0.75em;},
+div.vectorTabs li a {font-size: 0.8em;},
+and in #bodyContent {font-size: 0.875em;}
+
+The rest of the Vector layout relies on the base fontsize of 1em. If you must have 0.875em for #content, then the entire structure needs to be revised. So I don't know is VE can match the current situation, that would be the easiest way.",1398373392,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Change 129567 had a related patch set uploaded by Trevor Parscal:
+Use .mw-content for content styling
+
+https://gerrit.wikimedia.org/r/129567",1398371500,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","(In reply to Erwin Dokter from comment #5)
+> Just discovered that setting the 0.875em fontsize to #content instead of
+> #bodyContent messes with the layout of the entire page; the navigation bar
+> relies on the fontsize of #content to be 1em, otherwise it collapses.
+> 
+> To compensate, the left margin of #content would have to be modified from
+> 10/11em to 11.43/12.57em. That seems quite an unsightly hack with a
+> potential for alignment issues due to rounding errors.
+> 
+> Just so you know.
+
+Suggests that we should probably revisit the margins a little, but yes. :-(
+
+Can we get this fixed urgently? It's a quite disruptive regression for VisualEditor users.",1398363133,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Just discovered that setting the 0.875em fontsize to #content instead of #bodyContent messes with the layout of the entire page; the navigation bar relies on the fontsize of #content to be 1em, otherwise it collapses.
+
+To compensate, the left margin of #content would have to be modified from 10/11em to 11.43/12.57em. That seems quite an unsightly hack with a potential for alignment issues due to rounding errors.
+
+Just so you know.",1398275444,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","(In reply to Erwin Dokter from comment #2)
+> Both @body-line-height and @body-font-size are already applied to
+> #bodyContent (see bug 63731). Don't you mean they should be moved to
+> div#content instead, where everything else is defined?
+
+Sorry, yes. Corrected title.",1398114948,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)",*** Bug 64124 has been marked as a duplicate of this bug. ***,1397903906,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","Both @body-line-height and @body-font-size are already applied to #bodyContent (see bug 63731). Don't you mean they should be moved to div#content instead, where everything else is defined?",1397903077,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+"[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)","As discussed, we should apply the styling to bodyContent to affect other parts of the page like siteSub, contentSub, printfooter, catlinks, and also VE edit surface etc.",1397845166,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dkzwbg45silmhmsouxdk,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to page options
+3.Select Page Settings
+4.Go to Page options again
+5.Select Advanced Settings from the menu
+
+Observed Result:
+It navigates to the tab that was last opened but not to Advanced Settings
+
+Test Environment: https://test2.wikipedia.org/ and v
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1397608920,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oucacwo66k2ybwrotr5f,task_description,resolved
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,Verified the fix on production,1398386242,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,Verified the fix on test2,1397865593,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,Verified the fix on Betalabs,1397675730,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,"Change 126187 merged by jenkins-bot:
+Fix name of advanced settings page in open command
+
+https://gerrit.wikimedia.org/r/126187",1397617052,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab,"Change 126187 had a related patch set uploaded by Alex Monk:
+Fix name of advanced settings page in open command
+
+https://gerrit.wikimedia.org/r/126187",1397610673,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oucacwo66k2ybwrotr5f,task_subcomment,NA
+VisualEditor: Pull in Parsoid's new styling module so we don't need to duplicate locally,"Per bug 51245 Parsoid now has the start of a CSS module – gerrit 124785 – which we should pull into VE. Once we've done that we can start upstreaming a lot of our local CSS hacks into Parsoid and save the effort. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60017
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51245",1397606880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-msf2quw2wlciqweodnnt,task_description,resolved
+VisualEditor: Pull in Parsoid's new styling module so we don't need to duplicate locally,"Change 129810 merged by jenkins-bot:
+Pull in Parsoid's new styling module
+
+https://gerrit.wikimedia.org/r/129810",1398714784,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-msf2quw2wlciqweodnnt,task_subcomment,NA
+VisualEditor: Pull in Parsoid's new styling module so we don't need to duplicate locally,"Change 129810 had a related patch set uploaded by Jforrester:
+Pull in Parsoid's new styling module
+
+https://gerrit.wikimedia.org/r/129810",1398456948,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-msf2quw2wlciqweodnnt,task_subcomment,NA
+VisualEditor: Pull in Parsoid's new styling module so we don't need to duplicate locally,"So I think we need to:
+* Start depending on the Parsoid extension. (At the moment it's optional and improves performance.) James says this will break Vagrant installations.
+* Mark the VE RL module as depending on Parsoid's.",1397781167,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-msf2quw2wlciqweodnnt,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,"Intention:
+See if I could reproduce Alex's bug.  I could.
+
+Steps to Reproduce:
+1. Click http://en.wikipedia.beta.wmflabs.org/wiki/User:Whatamidoing_(WMF)/Sandbox?veaction=edit or open another page in VisualEditor.
+
+2. Click outside the main editing area.  For example, highlight part of the page title, or put the cursor in the search box.
+
+3. While your cursor is still outside the editing area, click the page options menu (three bars icon) and choose any item.  For example, choose ""Categories"".  (Perhaps you just used the search box to figure out how to spell the name of the category you're interested in adding, and that's why your cursor is in the search box.)
+
+Actual Results:  
+Nothing happens.  ""Switch to source editing"" is the only menu item that produces a response.
+
+Expected Results:  
+Normal editing behavior.  It doesn't matter where my cursor is placed for these items, so they shouldn't care.
+
+Reproducible: Always
+
+Confirmed in Safari 6 and Firefox 28 on Mac OS 10.8.5, and assumed to affect everything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63954",1397582280,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qvq2zj4itka6fwjddhwh,task_description,resolved
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1398380561,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,Verified the fix in test2,1397866304,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,Presuming that this is now FIXED.,1397600481,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,"Change 126058 merged by jenkins-bot:
+Use document direction when a fragment has a null range
+
+https://gerrit.wikimedia.org/r/126058",1397592134,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,"Change 126058 had a related patch set uploaded by Trevor Parscal:
+Use document direction when a fragment has a null range
+
+https://gerrit.wikimedia.org/r/126058",1397589656,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,CCing Roan - James mentioned earlier that he was working on something like this yesterday.,1397587203,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area,"I found this on Chrome 33 on Ubuntu 13.10.
+
+Error if you try to open something like Page settings (or most other items on that list):
+Uncaught TypeError: Cannot read property 'start' of null
+ve.Document.selectNodes
+ve.ce.Document.getDirectionFromRange
+ve.ui.DialogAction.open
+ve.ui.Surface.execute
+ve.ui.Command.execute
+ve.ui.Tool.onSelect
+OO.ui.ToolGroup.onMouseUp
+OO.ui.PopupToolGroup.onMouseUp
+proxy
+jQuery.event.dispatch
+elemData.handle.eventHandle
+
+Error if you try to type in the main text editing area:
+Uncaught TypeError: Cannot call method 'isCollapsed' of null
+ve.ce.Surface.handleInsertion
+ve.ce.Surface.onDocumentKeyPress
+proxy
+ve.EventSequencer.onEvent
+(anonymous function)
+jQuery.event.dispatch
+elemData.handle.eventHandle",1397587114,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-qvq2zj4itka6fwjddhwh,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Reference
+3.Type something inside the reference dialog box
+
+Observed Result:
+As soon as you type the first word the first letter diappears.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397501340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_description,resolved
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Now , it does not look broken .Hence, marking it as Fixed.",1398889897,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,I am again getting this issue in Chrome in Betalabs.,1398884750,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,verified the fix in production for Chrome,1398378180,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 129323 merged by Catrope:
+Prevent SurfaceWidgets from focussing themselves
+
+https://gerrit.wikimedia.org/r/129323",1398295506,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 129323 had a related patch set uploaded by Catrope:
+Prevent SurfaceWidgets from focussing themselves
+
+https://gerrit.wikimedia.org/r/129323",1398294927,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 129081 merged by jenkins-bot:
+Prevent SurfaceWidgets from focussing themselves
+
+https://gerrit.wikimedia.org/r/129081",1398283780,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 129081 had a related patch set uploaded by Esanders:
+Prevent SurfaceWidgets from focussing themselves
+
+https://gerrit.wikimedia.org/r/129081",1398212352,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Also the following errors appear on the console while trying to delete the texts inside the reference dialog box:
+TypeError: startNode is null
+Error: Unbalanced set of replace operations found
+Error: ve.dm.Document.getNodeFromOffset(): offset 3 is out of bounds",1398207479,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"For FireFox, I am getting this problem in a slightly different manner:
+Instead of getting missing the first letter of the first word you type inside reference dialog box , goes to the next line.",1398207135,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,Verified the fix in test2,1397865275,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,Verified the fix for the caption field in the Media Settings dialog in Betalabs,1397689160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 126855 merged by jenkins-bot:
+Also focus surface in media edit dialog
+
+https://gerrit.wikimedia.org/r/126855",1397686636,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 126855 had a related patch set uploaded by Catrope:
+Also focus surface in media edit dialog
+
+https://gerrit.wikimedia.org/r/126855",1397686418,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,This is now happening for the caption field inside Media Settings,1397681517,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,Verified the fix on Betalabs,1397678723,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 125911 merged by jenkins-bot:
+Focus the surface in the reference dialog after it opens
+
+https://gerrit.wikimedia.org/r/125911",1397674853,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Change 125911 had a related patch set uploaded by Catrope:
+Focus the surface in the reference dialog after it opens
+
+https://gerrit.wikimedia.org/r/125911",1397518093,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,With the reversion this should now be working again?,1397507631,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box,"Correction:
+Observed Result:
+
+As soon as user types the first word, the first letter of it disappears.",1397501449,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6vymomlg7udbwzf75icd,task_subcomment,NA
+VisualEditor: [Regression] Clicking out of inspector jumps selection back to inspected text,"If you click out of an inspector into some other text, it used to be that the cursor went to that text and stayed there, but now it jumps back to the text that was being inspected. I suspect this may have something to do with changes to ve.ui.DesktopContext. There seems to be a delay so maybe something's happening from a setTimeout( ..., 200 ) after the closing animation?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397496840,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bd4dgg3belnvzk5644rb,task_description,resolved
+VisualEditor: [Regression] Clicking out of inspector jumps selection back to inspected text,"Change 127805 merged by jenkins-bot:
+Prevent annotation inspector from updating selection if using DesktopContext#hide
+
+https://gerrit.wikimedia.org/r/127805",1398123996,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bd4dgg3belnvzk5644rb,task_subcomment,NA
+VisualEditor: [Regression] Clicking out of inspector jumps selection back to inspected text,"Change 127805 had a related patch set uploaded by Esanders:
+Prevent annotation inspector for updating selection if using DesktopContext#hide
+
+https://gerrit.wikimedia.org/r/127805",1398117872,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bd4dgg3belnvzk5644rb,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert a reference
+3.Type in something in the reference dialog box
+4.Save the page
+5.Reopen the page
+6.Open the reference
+
+
+Observed Result:
+There is no content in the reference dialog box
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1397239320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sfzqgeaol3scscbd2imq,task_description,resolved
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,Verified the fix on productionhttps://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1398386363,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,Verified the fix on test2,1397519598,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,"Change 125431 merged by jenkins-bot:
+Update VE core submodule to latest master (74353d9)
+
+https://gerrit.wikimedia.org/r/125431",1397517601,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,Verified the fix in Betalabs,1397505551,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,"Change 125431 had a related patch set uploaded by Jforrester:
+Update VE core submodule to latest master (74353d9)
+
+https://gerrit.wikimedia.org/r/125431",1397244788,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one,*** Bug 63829 has been marked as a duplicate of this bug. ***,1397244708,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sfzqgeaol3scscbd2imq,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Try to open math inspector on betalabs:
+The following error appears on the console and the math function does not open up
+
+Uncaught TypeError: Cannot call method 'getModel' of undefined VM2690:273
+ve.ui.MWMathInspector.setup VM2690:273
+(anonymous function) VM2688:23
+proxy load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:10
+listenerWrapper VM2688:6
+oo.EventEmitter.emit VM2688:7
+(anonymous function) VM2688:20
+pollExternalStylesheets
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397156220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_description,resolved
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 129623 merged by jenkins-bot:
+Update VE implementation to use model-only inspectors
+
+https://gerrit.wikimedia.org/r/129623",1398384517,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 129623 had a related patch set uploaded by Jforrester:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/129623",1398384394,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,Verified the fix on production with Chrome and FF,1398378457,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,Verified the fix on test2,1398196713,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 126909 merged by jenkins-bot:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/126909",1397703693,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 126909 had a related patch set uploaded by Catrope:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/126909",1397703494,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,Verified the fix in Betalabs,1397693209,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 125933 merged by jenkins-bot:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/125933",1397604310,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined,"Change 125933 had a related patch set uploaded by Esanders:
+Update VE implementation to use model-only inpsectors
+
+https://gerrit.wikimedia.org/r/125933",1397526851,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hl2jx7woen5yuyiqirv4,task_subcomment,NA
+VisualEditor: Icons render weirdly in IE10,"how the ...
+
+In my Windows 7 VMWare machine the icons render strangely in the toolbar.  Image attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7
+
+**Attached**: {F13606}",1397082960,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-2falvdljg7ldqp2rj3l5,task_description,declined
+VisualEditor: Icons render weirdly in IE10,"I have, however, seen a number of interesting rendering problems in IE11. It seems like their hardware acceleration sometimes chokes on gradients or transitions or whatever it is that we do that it doesn't like, and you'll get things like black boxes or iframes being transparent while they should be opaque, or buttons appearing to be flat when they shouldn't be.",1409961040,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2falvdljg7ldqp2rj3l5,task_subcomment,NA
+VisualEditor: Icons render weirdly in IE10,Works fine for me in IE10.,1409960965,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2falvdljg7ldqp2rj3l5,task_subcomment,NA
+VisualEditor: [Regression] Back button in ?veaction=edit changes address bar but doesn't alter page state,"Forking from bug 43844. Not good.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1397067840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cpq7rrq57bxr73nzx4zb,task_description,resolved
+VisualEditor: [Regression] Back button in ?veaction=edit changes address bar but doesn't alter page state,"Change 125745 merged by jenkins-bot:
+Always replace state with VE tag when loading
+
+https://gerrit.wikimedia.org/r/125745",1397674211,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-cpq7rrq57bxr73nzx4zb,task_subcomment,NA
+VisualEditor: [Regression] Back button in ?veaction=edit changes address bar but doesn't alter page state,"Change 125745 had a related patch set uploaded by Alex Monk:
+Always replace state with VE tag when loading
+
+https://gerrit.wikimedia.org/r/125745",1397492637,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-cpq7rrq57bxr73nzx4zb,task_subcomment,NA
+VisualEditor: [Regression] Back button in ?veaction=edit changes address bar but doesn't alter page state,I think this is caused by Gerrit change 118357,1397083170,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-cpq7rrq57bxr73nzx4zb,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"On http://parsoid.wmflabs.org/enwiki/User:Tamravidhir?oldid=603142295 , I see two images that look like:
+
+<figure><small><a href=""...""><img src=""..."" /></a><figcaption>Caption text</figcaption></small></figure>
+
+You can find them by opening that link in a browser and typing document.querySelectorAll('figure>small') in a console, then clicking on the result (Firebug) or right-clicking the result and choosing ""Reveal in elements panel"" (Chrome).
+
+Putting a <small> inside a <figure> tag but wrapped around a <figcaption> tag is a violation of the image spec (in addition to just being insane), which causes VisualEditor to get very confused and corrupt the image, which causes Parsoid to output [[undefined|NaNxNaNpx|right|link=]], see https://en.wikipedia.org/w/index.php?title=User:Tamravidhir&diff=603142575&oldid=603142295 . This is reminiscent of bug 62805 (NaNxNaNpx).
+
+The wikitext that triggers this is fairly complicated, and I haven't been able to isolate a test case locally. It seems to be something like:
+
+* '''Text'''
+<small>
+[[File:Foo|right|200px|Caption]]
+
+Text
+
+[[File:Foo|right|200px|Caption]]
+</small>
+* '''Text'''
+<small>
+etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1396894380,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_description,resolved
+Parsoid outputs <small> as child of <figure>,This is now fixed and will be deployed on Monday. Please reopen if you see this not fixed in production.,1438291859,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Change 215058 had a related patch set uploaded (by Subramanya Sastry):
+T65642: Additional scenarios dealing with treebuilder fixup
+
+[[https://gerrit.wikimedia.org/r/215058]]
+",1433177043,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"That patch also fixes your example from Comment 14:
+
+[subbu@earth lib] echo ""<small>[[File:Foo.jpg|right|300px]]</small>"" | node parse.js --wt2wt
+<small>[[File:Foo.jpg|right|300px]]</small>
+
+Okay, will revive it and try to get a resolution on it soon enough. I need to study behavior on more convoluted test cases and see what Tidy does and what we do now and see if I can fold that into this patch.",1413323636,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"(In reply to ssastry from comment #15)
+> Any thoughts about https://gerrit.wikimedia.org/r/#/c/162816/?
+
+I don't understand the patch very well, but the changes to the test cases look promising.",1413317924,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,Any thoughts about https://gerrit.wikimedia.org/r/#/c/162816/?,1413317657,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"This is still causing problems. See https://ru.wikipedia.org/?diff=66125825 for instance.
+
+$ echo ""<small>[[File:Foo.jpg|right|300px]]</small>"" | node tests/parse.js --wt2wt
+
+<small>[[File:Foo.jpg|right|300px|link=]]
+
+This seems to happen because of something similar to what I described in bug 66749 comment 7: there is a <small> inside a <figure>, which violates Parsoid's HTML spec, and causes a round-trip failure. Additionally, there's a frivolous <p><small></small></p> before and <p></p> after the image.",1413317084,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"See bug 66749 which appears to be a dup?
+
+Also, the WTS side of this ( https://gerrit.wikimedia.org/r/129818 ) never got finished/merged.",1403044473,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,Will close this .. Please reopen if this is not fixed post deploy tomorrow.,1399417225,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,This will be deployed on Wednesday.,1399298483,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Change 130109 merged by jenkins-bot:
+(Bug 63642): Cleanup treebuilder fixup of formatting elts.
+
+https://gerrit.wikimedia.org/r/130109",1399281146,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Change 130109 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 63642): Cleanup treebuilder fixup of formatting elts.
+
+https://gerrit.wikimedia.org/r/130109",1398706638,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Change 129818 had a related patch set uploaded by Cscott:
+WIP: WTS: Handle tag fixup that floats inside <figure>.
+
+https://gerrit.wikimedia.org/r/129818",1398458344,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"For the WTS case, it's probably sufficient to tweak the code that looks for the various bits of <figure> and ensure it skips over any extraneous <small>/<b>/<i>/<s>/<u> as direct children of <figure>.  That part wouldn't require a separate fixup pass.",1398455284,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Firefox fixes this up as follows:
+
+> div=document.createElement('div')
+> div.innerHTML = ""<p><small></p><figure><figcaption>foo</figcaption></figure</small>""
+> div.outerHTML
+""<div><p><small></small></p><figure><figcaption><small>foo</small></figcaption></figure></div>""
+
+But:
+> div.innerHTML = ""<p><small></p><figure><a href='xxx'><img></a><figcaption>foo</figcaption></figure></small>""
+> div.outerHTML
+""<div><p><small></small></p><figure><small><a href=""xxx""><img></a><figcaption>foo</figcaption></small></figure></div>""
+
+So it seems to be the <a> tag in particular which causes the treebuilder to resurface the <small> tag.  The same thing happens if <small> is <b> or <i> or <s> or <u>, but not <a>:
+
+> div.innerHTML = ""<p><a href=yyy></p><figure><a href='xxx'><img></a><figcaption>foo</figcaption></figure></a>""
+> div.outerHTML
+""<div><p><a href=""yyy""></a></p><figure><a href=""xxx""><img></a><figcaption>foo</figcaption></figure></div>""
+
+We might be able to handle this with a focused post-processing step which looks for <small>/<b>/<i>/<s>/<u> as the direct child of a <figure> and hoists the formatting safely inside the <figcaption>.  In theory we should have a similar check in WTS in case we get invalid HTML as input.",1397490798,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Reports from Roan on IRC:
+
+* Not very common, but seen on a few user pages.
+* This corrupts wikitext on save in pages where it is seen.
+* Community liasion wants this fixed in some fashion.
+* More important to protect content than provide editability.
+
+If possible, we should probably wrap such images with uneditable protection (mw:Placeholder) and deal with the larger issue later.",1397240855,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"node parse --trace html --dump dom:post-builder reveals that Parsoid generates a <p><small></p><figure>..</figure></small> (imagine them to be html tokens input to the HTML5 treebuilder) which the treebuilder helpfully fixes up to <p><small></small></p><figure><small>..</small></figure>
+
+But, the odd thing is that the tree builder does this only when this is nested inside the table. Not sure if that is a feature or a bug. To be tested in Firefox and Chrome.
+
+Replace <small> with <b>/<i>/.. and you see the same behavior. But, I think this is the same class of bugs around formatting tags wrapping certain kind of block tags and getting fixed up by HTML5 parsing semantics. In the case of unclosed tags, we have bug reports where a <s> or a <ul> formatting tag continues to the rest of the document (bug 50536, bug 57196). I am recording this info here for now. Unclear what the exact solution is for this here, but clearly, we need a generic solution for misnested formatting tags.",1396976815,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Reduced test case: Every newline in there is important to reproduce this.
+```
+{|
+|
+<small>
+[[File:Foo.jpg|right|Test]]
+</small>
+|}
+```",1433172542,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"Reduced test case: Every newline in there is important to reproduce this.
+
+{|
+|
+<small>
+[[File:Foo.jpg|right|Test]]
+</small>
+|}",1396898674,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"(02:34:55 PM) RoanKattouw: This structure is in a table cell BTW
+(02:35:00 PM) RoanKattouw: It's like the 104th child of a <td>
+(02:35:08 PM) RoanKattouw: Mismatched tags seems plausible
+(02:35:15 PM) RoanKattouw: There's a +</div> elsewhere in the dirty diff",1396895764,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+Parsoid outputs <small> as child of <figure>,"I'm fairly certain that LinkHandler never outputs <small>, so my guess is that this is a foster-parenting bug.",1396895657,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-axqdhgfcw2rceb3xxkdn,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,"**Author:** `richlv`
+
+**Description:**
+visual editor from git f8d56e6804a12248b485c2d3b49d4ff0ffa7220c
+
+opera 12.16 on linux.
+
+in the save form, minor edit & watching checkboxes can not be marked
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1396874100,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ovk5omihhahdt4qfvph7,task_description,declined
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,Not reproducible and no response from bug reporter :(,1410805662,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,"Can not reproduce using Opera 12.17 on Windows 7, on the page from comment 3. Clicking on both the checkboxes and their labels works as expected, checking the box.",1399407547,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,Not good.,1399404848,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,"**richlv** wrote:
+
+for the record, this still does not work for me at https://www.mediawiki.org/w/index.php?title=VisualEditor&veaction=edit - but i'll wait for 1.23 to be out before complaining more about it :)",1399403916,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,"**richlv** wrote:
+
+sorry, with ve currently not working with 1.22, i'll have to wait for the release of 1.23 to test this again",1399403311,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+VisualEditor: [Regression] Can't use save form checkboxes in Opera,It seems to work OK for me now – can you confirm?,1399307251,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ovk5omihhahdt4qfvph7,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"QUnit tests for jquery.makeCollapsible are often failing on Jenkins. I've seen this at least three times in the last week or so, most recently on https://gerrit.wikimedia.org/r/#/c/124051/ . Every time the failure was within the jquery.makeCollapsible tests (but I'm not entirely sure if on the same exact test).
+
+This might be related to the fake timers being used in them.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: major",1396723500,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-f627kqg22t3exoned4d4,task_description,resolved
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 145479 abandoned by Mattflaschen:
+Fix spurious QUnit failures related to fake timers
+
+Reason:
+I'm okay with throwing an error (which is already merged), rather than having the test runner work to clean it up.  The important thing is the test author/maintainer has a clear indication of the problem, which allows them to easily fix it.
+
+https://gerrit.wikimedia.org/r/145479",1405115464,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"I disabled the GuidedTour GUI that was triggering this during tests (1e37db808e1f9cc8daffb61e4303ce53d701e25a).  Krinkle's b90c69cdf70ae55a7ae608b074893d140d0a96b6 (""QUnit: Detect unfinished jQuery effects or ajax requests in teardown"") has been merged to core, which should detect similar issues in the future.
+
+I will abandon the other patch, since if isolation deficiencies (e.g. running effects queue) are fully detected and error'ed, the runner doesn't need to enforce that isolation.",1405115134,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 143481 abandoned by Krinkle:
+Use QUnit.asyncTest even for fake timers, to fix spurious failures
+
+Reason:
+See Ibada489a58295
+
+https://gerrit.wikimedia.org/r/143481",1405091263,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 145487 merged by jenkins-bot:
+Don't actually show guiders in unit tests
+
+https://gerrit.wikimedia.org/r/145487",1405086064,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"(In reply to Krinkle from comment #25)
+> Also, this really should've been a separate bug. The bug as reported was
+> fixed and affected core.
+
+The original symptoms appeared very close (not just ""it's something with timers and animations"", but specifically jquery.makeCollapsible).
+
+I didn't dive deeper to figure out the underlying interactions until later.",1405055330,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 145487 had a related patch set uploaded by Mattflaschen:
+Don't actually show guiders in unit tests
+
+https://gerrit.wikimedia.org/r/145487",1405045006,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Also, this really should've been a separate bug. The bug as reported was fixed and affected core. This looks similar (it's something with timers and animations), but a different exception is thrown, different unit tests are failing, and it's only affecting extensions (doesn't mean the bug isn;t in core, but it's a separate bug).
+
+This isn't a ""something is wrong with qunit and timers"" tracking bug.",1405043223,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"You were right, I didn't need to make it async.
+
+Side note, the SinonJS docs imply that useFakeTimers() uses the current date by default.  Unfortunately (this would have fixed half of my patch), this is not true, so I submitted a patch for those docs at https://github.com/sinonjs/sinon-docs/pull/2 .",1405040133,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 145479 had a related patch set uploaded by Mattflaschen:
+Fix spurious QUnit failures related to fake timers
+
+https://gerrit.wikimedia.org/r/145479",1405039965,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Turning the tests from sync to async in core is the functional equivalent of removing the assertion ""test framework works as expected"". It's like boldly removing unit tests or parser tests because when executed with a certain extension, they no longer match expected behaviour.
+
+I can reproduce this consistently but only with those extensions installed. With plenty of other extensions installed it works fine. I don't see anything obvious this extension that might cause it, but that wasn't the case earlier this year either and eventually we did find the problem there too.
+
+After static analysis yielded nothing, I turned to removing code locally until you find out what's causing it. Maybe it'll turn out to be a trigger that calls back into mediawiki-core, maybe not. But the surface layer triggering it isn't in core.",1404392948,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Doesn't look like we have a GettingStarted example yet, so:
+
+https://integration.wikimedia.org/ci/job/mwext-GettingStarted-qunit/58/consoleFull
+
+(Jul 3, 2014 12:13:51 AM per https://integration.wikimedia.org/ci/job/mwext-GettingStarted-qunit/58/)
+
+Seems to be the same set.  Again, jquery.color is the first error.
+
+If it affects any other extensions, please add.",1404350428,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"(In reply to Krinkle from comment #19)
+> Considering it is only affecting tests related to asynchronous Date
+> manipulation, I suspect one or more of the extensions the Growth team
+> maintains is interfering with that interface.
+
+I'm not sure what you mean by ""asynchronous Date manipulation"".  Sinon's fake timer methods are synchronous, AFAICT, just a simulation where you advance the clock manually.
+
+As far as the actual code (jquery.color.js and jquery.makeCollapsible.js), they are both using .promise (https://api.jquery.com/promise/) to monitor completed actions in the fx queue.
+
+GuidedTour (one of the extensions this bug affects) does not have any asynchronous tests, nor does GettingStarted.  Although we use setTimeout, we certainly don't do anything weird like redefining it.
+
+EventLogging (one of our dependencies) does use asynchronous tests, but we're hardly the only extension to use EventLogging.  (Note, EventLogging is not a Growth extension).  I don't know if any extensions with QUnit tests use EventLogging, but I suspect they do.
+
+If you see a bug (or unexpected interaction) which we can fix in a Growth extension, let us know.
+
+However, practically speaking, we should focus on getting this bug fixed.  My next step (as mentioned on Gerrit) will be to try use PhantomJS's remote debugging to step through and find exactly what's happening.",1404258173,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Considering it is only affecting tests related to asynchronous Date manipulation, I suspect one or more of the extensions the Growth team maintains is interfering with that interface.
+
+That was the case a few months back as well (that time it was an infrastructure library inside Grunt/Jenkins causing it).
+
+I can't reproduce this in MediaWiki core or any of the other extensions I can find. The test for MediaWiki core alone or those run for extensions such as VisualEditor and other projects are all consistently passing.",1404250281,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Change 143481 had a related patch set uploaded by Mattflaschen:
+Use QUnit.asyncTest even for fake timers, to fix spurious failures
+
+https://gerrit.wikimedia.org/r/143481",1404249272,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Actually, the first failure (at least sometimes, such as 220 mentioned above) is jquery.color.
+
+From the full log (https://integration.wikimedia.org/ci/job/mwext-GuidedTour-qunit/220/consoleFull) (without full it shows the tail):
+
+19:08:06 jquery.color - animate...ERROR
+19:08:06 >> Message: Expected 1 assertions, but 0 were run",1404246668,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,This is really problematic… https://gerrit.wikimedia.org/r/#/c/137837/,1403791471,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"I'm going to work on this as well, since it's a recurring problem affecting the Growth team.",1402791966,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Hm.. will give it another look. Although I doubt it's a bug in core.,1400784106,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,This is an old report. Been fixed a while ago.,1400784066,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Krinkle/Antoine: can you take a look please.,1400783594,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Someone really needs to take a look at this.  It is causing major friction in the continuous integration pipeline due to spurious failures.,1400783083,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"It's recurred.  See https://integration.wikimedia.org/ci/job/mwext-GuidedTour-qunit/220/console .  It's from about 6 hours ago.
+
+It's causing spurious failures in GuidedTour (likely other extensions too).  E.g.:
+
+19:08:11 >> Message: after expanding: contentItem is visible
+19:08:11 >> Actual: false
+19:08:11 >> Expected: true",1399426741,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"This was resolved after the following upgrades were made:
+
+
+* [jenkins] Update wmfgrunt dependencies to newer upstream versions 
+  - grunt-contrib-qunit from v0.2.0 to v0.4.0
+  - phantomjs from v1.8.1 to v1.9.7
+  https://gerrit.wikimedia.org/r/#/c/125052/
+
+* [mediawiki-core] Update QUnit from v1.11.0 to v1.14.0 
+  https://gerrit.wikimedia.org/r/#/c/125533/
+
+The latter is what made the false failures go away, so presumably the changes in those QUnit releases fixed it (possibly the changes in v1.12.0 and v1.14.0 that cache setTimeout and clearTimeout to protect against mocks).",1397754931,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"The internal time out is 30 seconds.
+
+It hanging for more than 30 seconds is new, that didn't happen until today.
+
+Both that 30s timeout and the 360min timeout should not be triggered because the tests aren't actually taking more than < 10-20 seconds to run. Something is causing it to get stuck or in some kind of loop...",1397243450,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"mediawiki-core-qunit is now sometime stuck. I killed a few jobs earlier today that ran for multiple hours.
+
+Just killed  https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/19068/console which was running for 10 minutes.
+
+Might want to add adjust the timeout of jobs to something more reasonable than the current 360 minutes.",1397222682,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Somewhat interestingly, the job sometimes hangs for real.
+
+From <https://gerrit.wikimedia.org/r/#/c/125370/>: ""https://integration.wikimedia.org/ci/job/mediawiki-core-qunit/19052/console : ABORTED in 5h 51m 36s""",1397221920,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"This has nothing to do with a time limit of any kind. The qunit tests run quicker than ever and have recently been sped  up a lot further by getting rid of slow animations and http calls to the server etc.
+
+This is failing because for some reason QUnit unexpectedly dies at which point PhantomJS never gets the 'end' event callback and thus times out. It does not time out because the tests are too long or anything.",1396898145,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,*** Bug 63647 has been marked as a duplicate of this bug. ***,1396898036,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,"Warning: PhantomJS timed out, possibly due to a missing QUnit start() call.\x07 Use --force to continue
+
+On https://gerrit.wikimedia.org/r/#/c/124366/ and some more of my changes from last days
+
+Possible regression from gerrit 117153
+
+Please have a look into this tests. Thanks.",1396894390,PHID-USER-qaoxfiqu6bxhd5ehlwhc,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Again: https://gerrit.wikimedia.org/r/#/c/124302/,1396866763,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins,Another example from today: https://gerrit.wikimedia.org/r/#/c/123804/,1396723834,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-f627kqg22t3exoned4d4,task_subcomment,NA
+VisualEditor: [Regression wmf21] Caption field is not appearing for any image in Betalabs and throwing error TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection',"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert a media
+3.Open the media Settings for the image
+
+Observed Result:
+The caption field is missing in the media settings dialog box .Also in the console the following error appears:
+
+Uncaught TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection'
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63544
+
+**Attached**: {F13747}",1396658520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-44p2piogq6pows7eriqb,task_description,resolved
+VisualEditor: [Regression wmf21] Caption field is not appearing for any image in Betalabs and throwing error TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection',Verified the fix in production,1397776336,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-44p2piogq6pows7eriqb,task_subcomment,NA
+VisualEditor: [Regression wmf21] Caption field is not appearing for any image in Betalabs and throwing error TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection',Verified the fix on mw.org,1396998463,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-44p2piogq6pows7eriqb,task_subcomment,NA
+VisualEditor: [Regression wmf21] Caption field is not appearing for any image in Betalabs and throwing error TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection',"This issue got fixed with this commit:
+https://gerrit.wikimedia.org/r/124381
+
+Verified the fix in Betalabs",1396911073,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-44p2piogq6pows7eriqb,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Reported by users and repro'd in beta labs
+
+Log in and edit any page with VE at http://en.wikipedia.beta.wmflabs.org/
+
+From the hamburger list select ""Switch to source editing""
+
+Nothing happens.  In the javascript console find the error 
+
+
+Uncaught Error: OO.ui.Tool.onSelect not implemented in this subclass:function VeUiMWEditModeSourceTool(toolGroup,config){ve.ui.MWEditModeTool.call(this,toolGroup,config);}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396562520,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_description,resolved
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Verified the fix in production:
+https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox",1397775464,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error",Verified the fix in mw.org,1396999325,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123825 merged by jenkins-bot:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123825",1396913445,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error",Verified the fix on Betalabs: http://en.wikipedia.beta.wmflabs.org/wiki/Regression3rdaprilchrome,1396634053,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123825 had a related patch set uploaded by Jforrester:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123825",1396577458,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123806 merged by jenkins-bot:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123806",1396570050,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123806 had a related patch set uploaded by Alex Monk:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123806",1396569871,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error","Change 123806 had a related patch set uploaded by Alex Monk:
+Revert edit mode tool's onSelect method
+
+https://gerrit.wikimedia.org/r/123806",1396569524,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error",also repro'd on test2wiki,1396563407,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-hrckm6oxmmkaoroohbia,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome,"Video showing issue
+
+Chrome Version 33.0.1750.152
+
+1. Access spelling suggestion from right click menu
+2. characters begin to be deleted (video attached)
+or
+3. Page content becomes corrupted, strange character insertions, loss of formatting. (image attached)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50822
+
+**Attached**: {F13521}",1396505280,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-m5xgrnjz6bps3ib55cr7,task_description,resolved
+VisualEditor: Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome,"Agreed, we've fixed this.",1423876215,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-m5xgrnjz6bps3ib55cr7,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome,"Could not reproduce the problem on https://cs.wikipedia.org/wiki/Wikipedista:Malyacko/Sandbox?veaction=edit with Chrome 40 on Fedora 21.
+Could not reproduce either by randomly trying on https://en.wikipedia.org/w/index.php?title=Kintsugi&veaction=edit
+Only one insertion/string replacement (as expected).
+
+Is this still an issue nowadays?",1423691064,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-m5xgrnjz6bps3ib55cr7,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome,"Created attachment 15013
+random character insertion and lack of formatting.
+
+**Attached**: {F13522}",1396505336,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-m5xgrnjz6bps3ib55cr7,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Screenshot
+
+Steps to reproduce:
+
+1.Select an image
+2.Click on Cite> Website/Book/Newspaper/Journal 
+
+Observed Result:
+It throws an error: Uncaught TypeError: Object #<VeDmMWBlockImageNode> has no method 'getInternalItem' 
+
+and VE gets stuck at this point, as you cannot close that dialog anymore
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Pageoffseterror?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13484}",1396479120,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_description,resolved
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,Verified the fix on Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Test63452?veaction=edit,1396644715,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Works for me now, both locally and on beta labs.",1396637383,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"After the fix, now the Cite dialogs does not open at all after selecting any image or any other mentioned nodes.
+Therefore reopening the bug and changing the title of the bug .",1396483936,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Change 123124 merged by jenkins-bot:
+Correctly insert or update citations based on template option
+
+https://gerrit.wikimedia.org/r/123124",1396482307,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Change 123124 had a related patch set uploaded by Catrope:
+Correctly insert or update citations based on template option
+
+https://gerrit.wikimedia.org/r/123124",1396481925,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,"Should be resolved by I34a5a2da576247f4046da45f742bccc3cec22c5a
+
+Specifically, the error is caused by calling getInternalItem on the node without checking if it's a ve.dm.MWReferenceNode. This patchset introduces an instanceof check.",1396481233,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog,It happens if you select a gallery/Math formula/template/reflist and then try to open any of the cite options,1396479463,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xl64eqcb6ygsvtl5jnqv,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","Intention:
+Correct the spelling of a word
+
+Steps to Reproduce:
+1. Open a page in Chrome.
+
+2. Pick a word that Chrome believes is misspelled.
+
+3. Right-click to correct the spelling.
+
+4. Save the page and check the diff.
+
+Actual Results:  
+Trying to change ""Minories"" to ""Minorities"" resulted in the missing ""ti"" being added at the very top of the page, rather than in the proper place.  (See http://en.wikipedia.org/w/index.php?title=User:Edgepedia/sandbox1&diff=next&oldid=602158018)
+
+
+
+Reproducible: Didn't try
+
+This may be related to Bug 50822 or Bug 59748.  
+
+Reported in Chrome Version 33.0.1750.154 m on Windows 7 using Vector.  Cannot be reproduced in Safari 6 (although there are other spelling problems in Safari.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50822",1396392120,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_description,resolved
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","In that case, marking as FIXED in that release. Unsatisfying, but…",1409011116,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","According to a post on frwiki VE feedback page:
+
+If you look at abuse filter 216, problem stopped to happen on June 19th, just after 1.24wmf9 being deployed, so probably a bug fixed in this release (in UTC+2 for Paris):
+14h38 - 128.179.139.136
+15h08 - 91.183.82.40
+16h26 - 92.94.142.126 (not save)
+19h00 - 195.101.137.28
+19h22 - 195.101.137.28
+20h35 - 87.90.125.24
+20h35 - 90.32.27.10
+21h12 - 41.189.42.250
+23h07 - 1.24wmf9 on WP:fr [2]
+
+[1] https://fr.wikipedia.org/w/index.php?title=Spécial:Journal_du_filtre_antiabus&wpSearchFilter=216
+[2] https://wikitech.wikimedia.org/wiki/Server_admin_log",1408998580,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","This was happening in new versions of chrome as recently as a month ago, I can no longer reproduce.",1408989710,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","Might this be caused by ancient versions of Firefox/Chrome caused in part by some config of frwiki, or a bug in their dictionary app, or something?",1408987394,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome",Can't reproduce in FF or Chrome...,1408986548,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","It's still happening, several times a day on frwiki. If you need examples, there's an abuse filter set in place in frwiki that catches some of the problems
+
+https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Journal_du_filtre_antiabus&wpSearchFilter=216",1400838863,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome",Just a note that this is still happening: https://www.mediawiki.org/w/index.php?diff=prev&oldid=997038,1399533054,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome","This is also an active bug for Firefox users, tested on FF 28.  Same steps to reproduce as above, same result (the corrected characters are added to both the word highlighted by the spellchecker, and the top of the document)
+
+Note: the unwanted text can be removed with the ""Undo"" button. However, you can't ""Undo"" your spelling correction, undo goes grey after the first action)",1398191119,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+"VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome",*** Bug 63652 has been marked as a duplicate of this bug. ***,1398186720,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6ylcfxjs56sonur5wvhg,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+
+2.Insert a link
+
+3.Now add a space and then a text next to it
+
+4.Now delete the space and concatenate the text with the exiting link
+
+5.Select the previous link and the text together
+
+6.Re-apply the link 
+
+
+Observed Result:
+The new link does not get applied and ""Save Page"" button remains disabled 
+
+
+
+See the screenshot attached
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/1staprilChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13327}",1396377540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_description,resolved
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Change 125019 merged by jenkins-bot:
+Fix covering annotations logic
+
+https://gerrit.wikimedia.org/r/125019",1397084815,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Change 125019 had a related patch set uploaded by Esanders:
+Fix covering annotations logic
+
+https://gerrit.wikimedia.org/r/125019",1397084657,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"The fix is not working for the following cases:
+
+Case 1:
+
+Steps to reproduce:
+
+1.Open a page with VE
+
+2.Insert a link where the target is an existing page
+
+3.Now add a space and then a text next to it
+
+4.Save the page
+
+5.Reopen the page
+
+6.Now delete the space
+
+7.Select the previous link and the text together
+
+8.Re-apply the link where the link target is a new page
+
+
+Case 2:
+
+Steps to reproduce:
+
+1.Open a page with VE
+
+2.Insert a link where the link target is a new page
+
+3.Now add a space and then a text next to it
+
+4.Save the page
+
+5.Reopen the page
+
+6.Now delete the space
+
+7.Select the previous link and the text together
+
+8.Re-apply the link where the link target is a different new page
+
+Case 3:
+
+1.Open a page with VE
+
+2.Insert a link where the target is a new page
+
+3.Now add a space and then a text next to it
+
+4.Save the page
+
+5.Reopen the page
+
+6.Now delete the space
+
+7.Select the previous link and the text together
+
+8.Re-apply the link where the link target is an exiting page
+
+In all the above three cases , the link does not get applied to the concatenated text",1397074188,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"I can still reproduce it on Betalabs.So, reopening it.",1397000509,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Change 124006 merged by jenkins-bot:
+Apply annotations to partially annotated selections
+
+https://gerrit.wikimedia.org/r/124006",1396656835,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"Change 124006 had a related patch set uploaded by Esanders:
+Apply annotations to partially annotated selections
+
+https://gerrit.wikimedia.org/r/124006",1396644843,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,This happens even if you dont delete the space and just select both the link and the text and then re-apply a new link.,1396557465,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link,"So the problem is:
+
+If you select text that is partially linked and partially not linked (in this specific case, the first part is linked and the second part isn't), then open the link inspector, we inspect the existing link but don't extend the link. If you then close the inspector without changing the target, nothing happens, but if you close the inspector with a changed target, the link is extended.
+
+So I guess that on opening the link inspector, we should aggressively extend the link?",1396482878,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5fgokfjvvl5idcf7wq5q,task_subcomment,NA
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a Cite Web or Cite Book
+3.Click on Show options to get the advanced widget
+
+
+Observed Result:
+Parameter icons inside transclusion dialog are overlapping with the parameter name
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13392}",1395880020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mdr37i6dfciuquwfrsiu,task_description,resolved
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,Verified the fix in betalabs and test2,1395964846,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mdr37i6dfciuquwfrsiu,task_subcomment,NA
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,Should now be fixed in production too.,1395962516,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mdr37i6dfciuquwfrsiu,task_subcomment,NA
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,"Change 121417 merged by jenkins-bot:
+Move padding rules for OutlineItemWidget from core to skins.
+
+https://gerrit.wikimedia.org/r/121417",1395945674,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mdr37i6dfciuquwfrsiu,task_subcomment,NA
+VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name,"Change 121417 had a related patch set uploaded by Catrope:
+Move padding rules for OutlineItemWidget from core to skins.
+
+https://gerrit.wikimedia.org/r/121417",1395943196,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mdr37i6dfciuquwfrsiu,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Screenshot
+
+Steps to reproduce:
+
+1.Create a page with VE
+2.Add a bullet list
+3.Add few items
+4.Now change the list to numbered list
+5.The cursor gets shifted to the start of the document
+6.Now type something
+
+Observed Result:
+Everything starts to behave weirdly .It starts to add text everywhere at the beginning of the page.The list disappears.
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Checkcursorbullet&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13373}",1395876240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pquph4y6rgkckbyn7rza,task_description,resolved
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,Verified the fix in production,1397177893,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,Verified the fix on mediawiki.org,1396990720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,Verified the fix on Betalabs,1396547285,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Change 123488 merged by jenkins-bot:
+Restore selection after ListAction too
+
+https://gerrit.wikimedia.org/r/123488",1396483527,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Change 123488 had a related patch set uploaded by Catrope:
+Restore selection after ListAction too
+
+https://gerrit.wikimedia.org/r/123488",1396483402,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Created attachment 14999
+snowman!!
+
+**Attached**: {F13374}",1396391384,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"Also, got the following error one time and the snowman while typing after changing the bullet list to numbered list:
+Uncaught Error: Invalid retain length, cannot retain backwards:-1",1396391363,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list,"The errors that appears in the console are:
+Uncaught Error: Unbalanced set of replace operations found
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 26 is out of bounds",1395876416,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pquph4y6rgkckbyn7rza,task_subcomment,NA
+VisualEditor: Update newarticletext usage for added parameter,"https://gerrit.wikimedia.org/r/#/c/83221/ added a parameter to newarticletext, but VE doesn't pass it, so now when you try to use VE on a nonexistent page with vanilla messages (enwiki's newarticletext message doesn't use $1) you see a raw $1 in the edit notice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395868740,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ih4n4564yrxr2ygatq7s,task_description,resolved
+VisualEditor: Update newarticletext usage for added parameter,"Change 121251 merged by jenkins-bot:
+Update use of newarticletext for added parameter
+
+https://gerrit.wikimedia.org/r/121251",1395871245,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ih4n4564yrxr2ygatq7s,task_subcomment,NA
+VisualEditor: Update newarticletext usage for added parameter,"Change 121251 had a related patch set uploaded by Alex Monk:
+Update use of newarticletext for added parameter
+
+https://gerrit.wikimedia.org/r/121251",1395869962,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ih4n4564yrxr2ygatq7s,task_subcomment,NA
+VisualEditor: Cannot close the Media Settings dialog as the error Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode' appears in the console,"screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Open the math inspector
+3.Keep it open
+4.Insert an image
+5.Select the image
+6.Click on undo 
+7.Click on the media settings icon that is still appearing at the right corner of the page
+
+Observed Result:
+
+The Media Settings dialog box appears with empty caption field .An error appears in the console: 
+Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode'
+
+Also, you will not be able to close the Media Settings dialog box and will get stuck at this step.
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13323}",1395860460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xskmm57u4y7kf62syw5f,task_description,resolved
+VisualEditor: Cannot close the Media Settings dialog as the error Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode' appears in the console,"Yes, Checked in production,appears to be fixed.",1401474803,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xskmm57u4y7kf62syw5f,task_subcomment,NA
+VisualEditor: Cannot close the Media Settings dialog as the error Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode' appears in the console,I believe that this is now fixed – please confirm.,1401472140,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xskmm57u4y7kf62syw5f,task_subcomment,NA
+VisualEditor: Cannot close the Media Settings dialog as the error Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode' appears in the console,"This seems to be because MediaEditDialog is launched for an MWMathNode, which shouldn't be possible. Assigned to Trevor as the fact that we even got here is a bug in the tools system.
+
+MediaEditDialog also shouldn't crash in this case, but Moriel is already going to merge the insertion and edit dialogs, so that should take care of that issue.",1395872280,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xskmm57u4y7kf62syw5f,task_subcomment,NA
+VisualEditor: Citation tool matching should also match templates with whitespace before the first parameter,"The citation tool recongizes a citation template that starts like this:
+
+<ref>{{cite web|url= 
+
+It does not recognize one that starts like this:
+
+<ref>{{cite web |url=
+
+The only difference is the (very common) addition of a space before the parameter.  It should understand both of these.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395859680,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-4yo52lx6x7wj5lym5xlc,task_description,resolved
+VisualEditor: Citation tool matching should also match templates with whitespace before the first parameter,I fixed this in https://gerrit.wikimedia.org/r/#/c/132725/ without realizing it.,1400095463,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-4yo52lx6x7wj5lym5xlc,task_subcomment,NA
+"VisualEditor: [Regression] Firefox displaying icons in odd places in dialog boxes (reference, media, template, …)","Intention:
+Edit an existing reference
+
+Steps to Reproduce:
+1. Open any article containing an existing citation in Firefox.  (I can't reproduce this in Safari.)
+
+2. Open an existing reference.
+
+3. Look at the ""Options"" area.
+
+Actual Results:  
+The icon overlaps with the text.  See screenshot.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63433
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63432",1395858900,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-7gxc6q7whoodm3jmk5bv,task_description,resolved
+"VisualEditor: [Regression] Firefox displaying icons in odd places in dialog boxes (reference, media, template, …)",*** Bug 63433 has been marked as a duplicate of this bug. ***,1397687806,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7gxc6q7whoodm3jmk5bv,task_subcomment,NA
+"VisualEditor: [Regression] Firefox displaying icons in odd places in dialog boxes (reference, media, template, …)",*** Bug 63432 has been marked as a duplicate of this bug. ***,1397687801,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7gxc6q7whoodm3jmk5bv,task_subcomment,NA
+"VisualEditor: [Regression] Firefox displaying icons in odd places in dialog boxes (reference, media, template, …)","Created attachment 14915
+Screenshot showing misaligned icon and labels
+
+**Attached**: {F13315}",1395858984,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-7gxc6q7whoodm3jmk5bv,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Click on  Insert> Formula
+3.Insert a formula inside then delete it 
+
+Observed Result:
+An empty selection box appears
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13248}",1395793260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7uw3xey4tqnzlnmyclap,task_description,resolved
+VisualEditor: An empty selection box is appearing while inserting a math formula,Verified the fix in production,1397177151,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"As per Ed, the initial empty selection box appearing on opening Math inspector is not related with this issue.So creating a separate bug for it and closing this one.",1397172262,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"This bug is partially fixed, the empty selection box is still appearing when you first open the Math Inspector.",1397089704,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,Verified the fix on Betalabs and test2,1397088241,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"Change 122602 merged by Physikerwelt:
+Emit rerender on math node if Tex image is not present
+
+https://gerrit.wikimedia.org/r/122602",1396349720,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+VisualEditor: An empty selection box is appearing while inserting a math formula,"Change 122602 had a related patch set uploaded by Esanders:
+Emit rerender on math node if Tex image is not present
+
+https://gerrit.wikimedia.org/r/122602",1396307311,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uw3xey4tqnzlnmyclap,task_subcomment,NA
+"VisualEditor: Close inspectors when the user clicks on the toolbar (e.g. on ""Save Page"") so it's clear that it has applied to the document","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a gallery or a Link inspector
+3.Edit something and close the inspector, this will make the save page button disabled
+
+4.Now again reopen that inspector and make further changes but do not close the inspectors .
+
+5.Click on the already active ""Save Page"" button
+
+Observed Result:
+The modified content of step 4 also gets saved even though user did not close the inspector to save it.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/24thmarchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395706620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-un4nilv22yoifhx5muc5,task_description,resolved
+"VisualEditor: Close inspectors when the user clicks on the toolbar (e.g. on ""Save Page"") so it's clear that it has applied to the document","
+
+*** This bug has been marked as a duplicate of bug 51439 ***",1401996119,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-un4nilv22yoifhx5muc5,task_subcomment,NA
+"VisualEditor: Close inspectors when the user clicks on the toolbar (e.g. on ""Save Page"") so it's clear that it has applied to the document",This is intended behavior but should be made clearer to the user. Perhaps clicking the save button should close the inspector? Or clicking anywhere in the surface+toolbar should close the inspector?,1395858638,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-un4nilv22yoifhx5muc5,task_subcomment,NA
+VisualEditor: Cite options are appearing as empty dialog on a new empty page for some time,"Screenshot
+
+Steps to reproduce:
+
+1.Open a new page with VE
+2.On this empty page select any option under Cite 
+
+Observed Result:
+
+The dialog box for cite options are appearing as empty dialog box 
+After a long time , the required parameters for Cite options appear
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Another24Marchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F13128}",1395702600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pe2hcgpuqebuelkuegcp,task_description,resolved
+VisualEditor: Cite options are appearing as empty dialog on a new empty page for some time,"It shouldn't be very long (but that's a different issue), but we've now fixed this by adding a loading animation to dialogs",1401418651,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pe2hcgpuqebuelkuegcp,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).","Without any required parameters
+
+Steps to reproduce:
+
+
+1,Open a page with VE
+2.Insert a reference
+3.Open the reference dialog box select any option under Cite (Website/Book/Newspaper/Journal)
+
+Observe Result:
+None of the required parameters are showing up , in all cases the dialog to add a transclusion comes up.
+
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Another24Marchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13118}",1395701400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_description,resolved
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).","Change 121266 merged by jenkins-bot:
+Make cite transclusion tools actually work
+
+https://gerrit.wikimedia.org/r/121266",1395874136,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).","Change 121266 had a related patch set uploaded by Catrope:
+Make cite transclusion tools actually work
+
+https://gerrit.wikimedia.org/r/121266",1395873726,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).",It is not related with Beta Labs being slow yesterday.I can still reproduce it.,1395771627,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).",This was caused by Beta Labs melting; now working again. Ish.,1395702237,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+"VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).","Created attachment 14898
+how it appears on CE with the required parameters
+
+**Attached**: {F13119}",1395701531,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xdi4r7ceks7mdjg5jvbl,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Uncaught TypeError: Cannot read property 'keyedNodes' of undefined  appears while adding a reference in the page and makes VE unresponsive,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a reference
+
+Observed Result:
+
+Uncaught TypeError: Cannot read property 'keyedNodes' of undefined appears in the console and VE gets unresponsive
+
+See the screenshot attached.
+ 
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13105}",1395697140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-z6u74sout6eqjchhlbja,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Uncaught TypeError: Cannot read property 'keyedNodes' of undefined  appears while adding a reference in the page and makes VE unresponsive,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Another24Marchrome?venotify=created,1395703011,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-z6u74sout6eqjchhlbja,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Uncaught TypeError: Cannot read property 'keyedNodes' of undefined  appears while adding a reference in the page and makes VE unresponsive,"Change 120613 merged by jenkins-bot:
+Update reference's internal item after inserting reference
+
+https://gerrit.wikimedia.org/r/120613",1395699599,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-z6u74sout6eqjchhlbja,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Uncaught TypeError: Cannot read property 'keyedNodes' of undefined  appears while adding a reference in the page and makes VE unresponsive,"Change 120613 had a related patch set uploaded by Catrope:
+Update reference's internal item after inserting reference
+
+https://gerrit.wikimedia.org/r/120613",1395698783,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-z6u74sout6eqjchhlbja,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Screenshot
+
+Steps to reproduce:
+
+Just open the Keyboard shortcut page
+
+Observed Result: See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13057}",1395683880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_description,resolved
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Change 357808 had a related patch set uploaded (by Pmiazga; owner: Pmiazga):
+[mediawiki/extensions/Popups@master] Handle Restbase HTML response
+
+[[https://gerrit.wikimedia.org/r/357808]]
+",1496928668,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/26thmarChrome?veaction=edit,1395940894,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Change 121264 merged by jenkins-bot:
+Bring CommandHelpDialog CSS back
+
+https://gerrit.wikimedia.org/r/121264",1395873586,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Change 121264 had a related patch set uploaded by Catrope:
+Bring CommandHelpDialog CSS back
+
+https://gerrit.wikimedia.org/r/121264",1395873164,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted,"Some CSS paths changed, maybe that's what broke this.",1395858843,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7vghnyvf4zsfnamrgi5g,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a text
+3.Try to Save the page
+
+
+Observed Result:
+An error appears : Uncaught TypeError: Cannot call method 'teardown' of undefined
+The page seems to be in readmode but the cursor still appears on the page
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Toc_issue
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12876}",1395424800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dwllxtwbn3l46wpsweqk,task_description,resolved
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs",Verified the fix in betalabs,1395439734,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","Change 120070 merged by jenkins-bot:
+Fix a typo that causes crashes when using the wrong symbol for mwTocWidget
+
+https://gerrit.wikimedia.org/r/120070",1395434096,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","Change 120070 had a related patch set uploaded by Jforrester:
+Fix a typo that causes crashes when using the wrong symbol for mwTocWidget
+
+https://gerrit.wikimedia.org/r/120070",1395433999,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","Oops... I meant:
+
+if ( this.surface.mwTocWidget ) {
+    this.surface.mwTocWidget.teardown();
+}",1395425086,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs","This error has to do with code that looks like this:
+
+if ( this.surface.mwTocWidget ) {
+    this.mwTocWidget.teardown();
+}
+
+which needs to be rewritten to look like:
+
+
+if ( this.surface.mwTocWidget ) {
+    this.mwTocWidget.surface.teardown();
+}",1395425048,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-dwllxtwbn3l46wpsweqk,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"This will alert us to things going wrong quickly. Hopefully. (Yes, there's a risk of noise, but there should be 0 of these, anyway.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395281460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sg62navkedep4loydypt,task_description,resolved
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"(In reply to Elitre from comment #7)
+> The tag vepawns, i.e. :
+> https://en.wikipedia.org/w/index.php?title=Special:
+> RecentChanges&tagfilter=vepawns .
+
+That's not done by VisualEditor; these must be a local AbuseFilter written by the community…",1406750919,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"The tag vepawns, i.e. : https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=vepawns .",1406750846,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,What filter?,1406740869,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"@Alex, that filter doesn't seem to be catching anything, I have no idea if it's still functional or not, that's why I asked.",1406736985,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"Went with approach #3, it's a python script run under the 'wm-ve-needcheck-reporter' service user in tool labs. Cron set up to run every day at 16:30 (UTC).
+
+(In reply to Elitre from comment #3)
+> Should vepawns edits be tracked as well?
+Perhaps we should have a separate bug for this - it sounds like a good idea to mark edits which add new pawn characters to the page as needcheck",1406140592,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,Should vepawns edits be tracked as well?,1395393174,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"As I said in IRC, option 3 seems sanest to me, but that's not really my call as I'm not the one that'll write it. :-)",1395350006,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis,"The CVNBot software used for #cvn-sw, #cvn-commons, #cvn-meta etc. can't provide this because of limitations in the source feed, irc.wikimedia.org, which doesn't expose revision change tags.
+
+Looks like realistically the fast way to make this happen is probably a little nodejs project ran from tool labs that polls wikis using one of these approaches:
+
+1) Socket to irc.wikimedia.org, join all channels, filter for lines that look like edits/page creations (any line that includes a url with rcid), extract rcid from url, make API request and retrieve change tags.
+
+Pros:
+ - Only one socket for events.
+ - No API polling.
+
+Cons: 
+ - It's friggin IRC
+ - Still requires an API request, looots of them (one for every edit/newpage across all of Wikimedia). Could be done in batches when implementing it with a short local delay/buffer before outputting it, but still a ton of requests.
+
+1b) Alternative: Like #1a, but do the changetag retrieval via SQL query to labsdb instead of API request.
+
+Pros:
+ - Only one socket for events.
+ - No API polling.
+ - No API requests at all.
+Cons:
+ - dbreplag might cause problems.
+
+
+2) Have the app generate a list of API entry points for all Wikimedia wikis (using either operations/mediawiki-config data or using centralauth/sitematrix API), and poll all these periodically for action=recentchanges, taking care to ensure we don't miss edits (lower query is faster/cheaper, but means if there is more than limit N number of edits since the last query, you miss out).
+
+Pros:
+ - Edit information included in main event stream (ApiRecentChanges).
+
+Cons:
+ - API polling.
+ - One API request for each wiki, at an interval.
+ - Not missing events is going to be hard.
+
+3) Have the app fetch a list of wikis from labsdb.meta.wiki, open 1 connection for each db shard, and start polling recentchanges for each wiki (using WHERE query to find everything since the last poll, potentially LIMIT still to keep things rate limited)
+
+Pros:
+ - Edit information included in main event stream (recentchanges table).
+ - Only a few sockets needed (7 or 8) to be able to query all 100s of wikis.
+ - No API polling.
+ - No API requests at all.
+
+Cons:
+ - Slight delay due to dbreplag to labs, but we don't use anything else so it's consistent should the app should be blind to it.",1395283265,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-sg62navkedep4loydypt,task_subcomment,NA
+VisualEditor:  Template tabbing is odd in Firefox (loses focus between parameters?),"Intention:
+Tab through the fields in a pre-existing infobox
+
+Steps to Reproduce:
+1. In Firefox 27, open a page that contains an infobox.
+
+2. The cursor is (should be) in the first parameter, which should light up with a blue border.  Press the tab key. 
+
+3. Where is the cursor now?
+
+4. Repeat.
+
+
+Bonus:  When you get nearly to the end of the template, use the mouse or arrow keys to click back in the first parameter.  Press tab.  The cursor should be in parameter #2, but sometimes it goes to the parameter after your pre-click location.
+
+Actual Results:  
+You sometimes have to tab twice to get from parameter #1 to parameter #2.  If you do, then select-all from the keyboard will select the TemplateData descriptions.
+
+
+Reproducible: Sometimes
+
+I was unable to reproduce this in Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395248040,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-p6ts7vep3e6p2gds2ktg,task_description,resolved
+VisualEditor:  Template tabbing is odd in Firefox (loses focus between parameters?),"Change 125894 merged by jenkins-bot:
+Only blur inputs within booklet pages when moving away
+
+https://gerrit.wikimedia.org/r/125894",1397670710,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6ts7vep3e6p2gds2ktg,task_subcomment,NA
+VisualEditor:  Template tabbing is odd in Firefox (loses focus between parameters?),"Change 125894 had a related patch set uploaded by Trevor Parscal:
+Only blur inputs within booklet pages when moving away
+
+https://gerrit.wikimedia.org/r/125894",1397515572,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6ts7vep3e6p2gds2ktg,task_subcomment,NA
+VisualEditor:  Template tabbing is odd in Firefox (loses focus between parameters?),This is probably Firefox not respecting tab-index: -1; or something. Eurgh.,1395281211,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6ts7vep3e6p2gds2ktg,task_subcomment,NA
+"VisualEditor: <a rel=""mw:WikiLink"" href=""Foo"" ></a> shouldn't ever be sent to Parsoid.","From bug 50945#c3
+
+| However my testing showed that this was not reliable and sometimes resulted
+| in odd wikicode, e.g. [[Ecuador|<nowiki/>]][[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
+
+<p><a rel=""mw:WikiLink"" href=""./Ecuador"" ></a><a rel=""mw:WikiLink"" href=""./Egypt"">E</a><a rel=""mw:WikiLink"" href=""./Egypt"">gypt</a></p>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395196560,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nazqhnyfc7ftcgefkuwk,task_description,resolved
+"VisualEditor: <a rel=""mw:WikiLink"" href=""Foo"" ></a> shouldn't ever be sent to Parsoid.",We /believe/ that this may have been fixed this week; provisionally closing as such.,1395196643,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nazqhnyfc7ftcgefkuwk,task_subcomment,NA
+VisualEditor: Link inspector doesn't save changes when closing while XHR is pending,"Introduce artificial delays in your API modules (sleep(2); at the top of ApiOpenSearch::execute() and ApiQueryInfo::execute(); alternatively, you can try this in production if you're quick enough), then perform the following steps quickly:
+
+1. Inspect an existing link
+2. Change its target
+3. Before the API request completes, close the link inspector by clicking out or clicking the back arrow
+4. Inspect the link again
+
+Expected: new target shows in inspector
+Actual: old target shows
+
+With the keyboard it's even weirder:
+
+1. Inspect an existing link
+2. Type ""foo"". Wait for the API request to come back and display suggestions
+3. Type ""bar"" at the end (so you now have ""foobar""), then quickly (before the API call comes back) press Enter.
+4. Expected: inspector closes. Actual: input value is reset to ""foo""
+(At least if you press Enter again, ""foo"" is actually saved.)
+
+You can work around this and still reproduce the first bug:
+
+1. Inspect an existing link
+2. Type ""foo""
+3. If a suggestion box is displayed (perhaps because ""f"" was in cache, or because the previous value was in cache), press Esc to dismiss it
+4. Press Enter, the inspector closes
+5. Inspect the link again
+
+Expected: ""foo""
+Actual: previous value
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395195780,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ccf5hssmynovsc2eeyi7,task_description,resolved
+VisualEditor: Link inspector doesn't save changes when closing while XHR is pending,This looks like it's now been fixed. I think.,1402548960,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ccf5hssmynovsc2eeyi7,task_subcomment,NA
+VisualEditor: setResizableHandlesSizeAndPosition() shouldn't measure things on every keypress,"In afterDocumentKeyPress, setResizableHandlesSizeAndPosition() is called and measures and repositions all ResizableNode resize handles, even though they're not even visible. This is wasteful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395188760,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mjjjlepmev2tbtsh3jxb,task_description,resolved
+VisualEditor: setResizableHandlesSizeAndPosition() shouldn't measure things on every keypress,Fixed in gerrit Ia6cf8de0da0.,1412610753,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mjjjlepmev2tbtsh3jxb,task_subcomment,NA
+VisualEditor: setResizableHandlesSizeAndPosition() shouldn't measure things on every keypress,This was fixed at some point. setResizableHandlesSizeAndPosition() is now attached to the 'position' event on focus and detached on blur.,1412588928,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mjjjlepmev2tbtsh3jxb,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'update' of null"" and inserts empty formula","The error
+
+Steps to reproduce:
+
+
+1.Open a page with VE which has slug in it
+2.Place your cursor in the slug and open the math inspector
+3.Now type something inside the math inspector
+
+
+Observed Issue 1: 
+It throws an error:
+Cannot call method 'update' of null
+
+And if you insert the math function and save the page and then go to edit source , you will see an empty math rag has also been added to the page
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_(WMF)&action=edit
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58286
+
+**Attached**: {F13147}",1395166680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b4n4vtsivb5tsumyakxy,task_description,resolved
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'update' of null"" and inserts empty formula","
+
+*** This bug has been marked as a duplicate of bug 58286 ***",1397704103,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b4n4vtsivb5tsumyakxy,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'update' of null"" and inserts empty formula",Confirming still occurring.,1397692741,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b4n4vtsivb5tsumyakxy,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'update' of null"" and inserts empty formula","Created attachment 14851
+The empty math tag
+
+**Attached**: {F13148}",1395166732,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b4n4vtsivb5tsumyakxy,task_subcomment,NA
+VisualEditor: [Regression] Long target names no longer get shortened in the link inspector,"Steps to reproduce:
+
+- go to http://en.wikipedia.beta.wmflabs.org/wiki/Snail
+- edit the page with visual editor
+- highlight text ""animal""
+- click Hyperlink tool
+- paste http://en.wikipedia.beta.wmflabs.org/wiki/Animal into Hyperlink tool
+- the link goes out of Hyperlink tool box (see attached screen shot)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395164040,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-54nochcknohar22gmhks,task_description,resolved
+VisualEditor: [Regression] Long target names no longer get shortened in the link inspector,"Oh, yeah, we fixed this in the inspector styling tweaks in April, I think.",1401468546,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-54nochcknohar22gmhks,task_subcomment,NA
+VisualEditor: [Regression] Long target names no longer get shortened in the link inspector,Works for me. Did this get fixed at some point since this bug was filed?,1401449578,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-54nochcknohar22gmhks,task_subcomment,NA
+VisualEditor: [Regression] Long target names no longer get shortened in the link inspector,"Created attachment 14849
+hyperlink tool
+
+**Attached**: {F13143}",1395164089,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-54nochcknohar22gmhks,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the link inspector 
+3.Now enter something invalid for link inspector , for example: File:Joo Chiat Place.jpg|Item 1
+
+Observed Result:
+
+An error message appears for invalid page title , the style of the error message should be much more apparent like red 
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13049}",1395097740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-um7czp26rhb3rg5y7ylt,task_description,resolved
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,Nice!,1416266975,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"All patches mentioned in this report were merged or abandoned - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?",1416053635,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Change 150297 merged by jenkins-bot:
+MWLinkTargetInputWidget: Add styles for invalid link titles
+
+https://gerrit.wikimedia.org/r/150297",1406832737,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Change 150297 had a related patch set uploaded by Palerdot:
+Fixed Bug 62761, added invalid link title style.
+
+https://gerrit.wikimedia.org/r/150297",1406831831,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Comment on attachment 16097
+Screenshot of Fix for Bug 62761
+
+The color in the screenshot is red. I have changed the color to #d45353 to match the other warning elements in the mediawiki page.",1406661753,PHID-USER-or5bjqrmvxl6rczurt2w,False,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Screenshot of Fix for Bug 62761
+
+This is the screenshot of the fix I have made for the bug 62761. The gerrit patch link is https://gerrit.wikimedia.org/r/#/c/150297/
+
+**Attached**: {F13050}",1406661578,PHID-USER-or5bjqrmvxl6rczurt2w,False,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"I have made a fix to this bug. The gerrit patchset link is https://gerrit.wikimedia.org/r/#/c/150297/
+
+Things done:
+A new CSS File 
+'ve.ui.MWLinkTargetInputWidget.css' is added to the path 'VisualEditor/modules/ve-mw/ui/styles/widgets'. Warning text style is added to the class '.ve-ui-mwLinkTargetInputWidget-warning' in this file. The CSS File is included in the style resources in the file 'VisualEditor.php'. Tested in latest stable firefox, chrome in Ubuntu 14.04.
+
+Please review the changes. I'm new to open source contribution, So let me know if I have done the fix to the bug in the right way. Thanks.",1406661456,PHID-USER-or5bjqrmvxl6rczurt2w,False,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: The style of error message for invalid page title for link should be more apparent in style,"Change 150297 had a related patch set uploaded by Palerdot:
+Fixed Bug 62761, added invalid link title style.
+
+https://gerrit.wikimedia.org/r/150297",1406661128,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-um7czp26rhb3rg5y7ylt,task_subcomment,NA
+VisualEditor: Drag and drop inserted the relocatable node image marker as a data:image/gif;base64 string,"I don't know how the user did that, but take a look at this edit:
+https://pt.wikipedia.org/wiki/Esporte_Clube_Pelotas?diff=38422037
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395063660,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-27yzqmhzbjs5rne5s34q,task_description,declined
+VisualEditor: Drag and drop inserted the relocatable node image marker as a data:image/gif;base64 string,I can't replicate; I've not seen any other reports like this; and we re-wrote this system last week. Provisionally I'm going to mark as WFM.,1404421306,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-27yzqmhzbjs5rne5s34q,task_subcomment,NA
+VisualEditor: Drag and drop inserted the relocatable node image marker as a data:image/gif;base64 string,"That's the relocatable node image marker, so it's a  drag & drop bug.",1395065812,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-27yzqmhzbjs5rne5s34q,task_subcomment,NA
+VisualEditor: The message that appears while adding a template with no description should use the readable form of template name,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Transclusion
+3.Insert a template that does not have any description.
+4.For example: Country showdata for betalabs
+
+Observed Result:
+A message comes up :You are adding the ""Country_showdata"" template to this page. It doesn't yet have a description, but there might be some information on the template's page.
+
+In this message , the template name used should be in more readable form that is with underscores: Country showdata
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_(WMF)?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F12888}",1394836500,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vi756jr6zyy2qwagomlc,task_description,resolved
+VisualEditor: The message that appears while adding a template with no description should use the readable form of template name,This appears to have been fixed in Gerrit change 132723 by Bartosz,1401475141,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vi756jr6zyy2qwagomlc,task_subcomment,NA
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Place the cursor in a slug
+3.Press tab
+
+Observed Result:
+An error appears in the console:
+Uncaught TypeError: Cannot call method 'getParent' of null
+ve.Document.getCoveredSiblingGroups
+ve.ui.IndentationAction.increase
+ve.ui.Surface.execute
+ve.ui.Command.execute
+ve.ui.Surface.execute
+ve.ce.Surface.onDocumentKeyDown
+proxy load.php:10
+ve.EventSequencer.onEvent
+(anonymous function)
+jQuery.event.dispatch load.php:45
+elemData.handle.eventHandle
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12844}",1394827800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_description,resolved
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item",Verified the fix on test2:https://test2.wikipedia.org/wiki/Wmf19?veaction=edit,1395356950,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_subcomment,NA
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item",Verified the fix on Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_(WMF)?veaction=edit,1395083360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_subcomment,NA
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item","Change 119045 merged by jenkins-bot:
+Don't try to return the document in getCoveredNodes
+
+https://gerrit.wikimedia.org/r/119045",1395076238,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_subcomment,NA
+"VisualEditor: Pressing tab on a slug throws error ""Cannot call method 'getParent' of null"" and does not go to the next line or next item","Change 119045 had a related patch set uploaded by Esanders:
+Don't try to return the document in getCoveredNodes
+
+https://gerrit.wikimedia.org/r/119045",1395064673,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rtrlbvsemfk66nq4yjrk,task_subcomment,NA
+VisualEditor: Inspector flickers and flashes continuously when resizing window,"When resizing the window with an inspector open, it continuously flickers and flashes blank, sometimes making a slow, fast or partial fade in/out, others when you let go of the resize handle it does a bunch of flashes in burst (as if they were queued up).
+
+Screen capture: http://cl.ly/0g2F0q2D3p1D
+
+Seems to relate to code that adds/removes the ""oo-ui-popupWidget-transitioning"" class.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394758800,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xudydyain6z66hfd3b4j,task_description,resolved
+VisualEditor: Inspector flickers and flashes continuously when resizing window,Fixed a couple of weeks ago by Trevor.,1397763968,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xudydyain6z66hfd3b4j,task_subcomment,NA
+VisualEditor: Inspector flickers and flashes continuously when resizing window,"(In reply to Krinkle from comment #0)
+> Screen capture: http://cl.ly/0g2F0q2D3p1D
+
+This also exposes bug 55789, though these flashes are not caused or related to (absence of) the logic to reposition the overlay elements themselves.",1394758898,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xudydyain6z66hfd3b4j,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Seen often in browser tests run locally and on Cloudbees, this happens: 
+
+
+* default status of Beta toggle is OFF
+* click Beta toggle to ON
+* click Save
+
+* get error: ""Error saving settings. Please make sure that you have cookies enabled""
+
+* Beta toggle goes back to OFF
+* test fails
+
+
+I have not yet triggered this manually. (but I haven't tried that hard either)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394741760,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_description,resolved
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Change 126873 merged by jenkins-bot:
+Use core token handling
+
+https://gerrit.wikimedia.org/r/126873",1397692239,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Change 126873 had a related patch set uploaded by Jdlrobson:
+Use core token handling
+
+https://gerrit.wikimedia.org/r/126873",1397691972,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Jon from comment #64)
+> We deep dived this issue again and concluded we should remove getMobileToken
+> in favour of user->getToken
+> 
+> Chris says that soon anonymous editors will get a unique token when that is
+> called.
+
+Out of curiosity, is there a timeline for this?
+
+> In mean time there is a CSRF risk to anons using Special:MobileOptions but
+> we decided since risk was low we can live with this.
+
+This makes sense to me since this would only be an issue for anons. I'm ok with it so long as Chris S is OK with it.",1397689915,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"We deep dived this issue again and concluded we should remove getMobileToken in favour of user->getToken
+
+Chris says that soon anonymous editors will get a unique token when that is called.
+
+In mean time there is a CSRF risk to anons using Special:MobileOptions but we decided since risk was low we can live with this.",1397683593,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"The test for ""Keep Going"" registers a new account but also triggers the token-mismatch problem: https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/493/testReport/(root)/Encourage%20new%20users%20to%20Keep%20Going/I_see_a_KeepGoing_message_after_completing_my_VisualEditor_edit/",1397490104,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"For reference, history:  http://git.wikimedia.org/history/mediawiki%2Fextensions%2FMobileFrontend/f7180dc297b958a27920a88348db27104eaf10e5/includes%2FMobileContext.php;jsessionid=7rk483w9yc4w15fi1z5t8bd05
+
+and change to MobileContext: 
+
+http://git.wikimedia.org/blobdiff/mediawiki%2Fextensions%2FMobileFrontend/27e463c35c202607fe3023fc020c76ef41c13cd8/includes%2FMobileContext.php",1397252836,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,There have been 8708 hits to this error in the last 30 days on our production wikis.,1397252475,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,The problematic function seems to be MobileContext::getMobileToken,1397148129,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"So this problem seems to only happen when the user is anonymous...
+It seems that $this->getRequest()->getSessionData( 'wsMobileToken' ) is returning null which results in a new session getting setup on submitting the form which results in invalidation of the form.
+
+Don't understand this code well enough to know if this is misbehaving and if it is why.",1397148092,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+Jon updated the editor_ve.feature test today, but I cannot get a clean run of the test on beta labs.  
+
+In every case one token seems to persist longer than it should, on the order of 15+ seconds.  I was tailing mobile.log for three successive unsuccessful runs of that test and got these results: 
+
+2014-04-09 22:04:34 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 0784e6702ac5df67d042c4a7969165bd - expected 0a84ee38edc0905b86d3620bd12765e9
+2014-04-09 22:05:36 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 738fbdc0987c5b31cef77ae5e08aa9fb - expected a041b5f2632ef617d1b92681456d8866
+2014-04-09 22:05:53 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 738fbdc0987c5b31cef77ae5e08aa9fb - expected a041b5f2632ef617d1b92681456d8866
+
+
+2014-04-09 22:08:13 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received b9547af8f118ad0bca2834777d62ba1c - expected 29d3774af72c2a0e6f0768092480c982
+2014-04-09 22:08:31 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received b9547af8f118ad0bca2834777d62ba1c - expected 29d3774af72c2a0e6f0768092480c982
+2014-04-09 22:09:42 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received c6c71ff97b5a448c78f3e85aa27e343d - expected 3a78d9b84bb3873f503baf7d0e41b4cc
+
+2014-04-09 22:11:14 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 1ec21965b2c0eb6dcfd6a01ef1c4eacc - expected 520e7ebbfa9f0449d3ebc0c79e350911
+2014-04-09 22:11:31 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 1ec21965b2c0eb6dcfd6a01ef1c4eacc - expected 520e7ebbfa9f0449d3ebc0c79e350911
+2014-04-09 22:12:38 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 9ce4d541e91887bed12a76e988f90965 - expected 467de8a293b2a6de7a6fef0905660b46",1397081944,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+I set the editor_ve.feature test to log in with a different user anyway and generated the following errors in the second run of the test on my local host: 
+
+2014-04-02 17:52:34 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 60fa1ffd7c4273c5c1e5ceeb7d44cfd2 - expected 361fda81efd0e50f37234db4384ee64e
+2014-04-02 17:53:35 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 60cd4c3b308cac220e7a8629b0427056 - expected 34a28952e608764e4452a5b73b80175e
+2014-04-02 17:53:50 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received 60cd4c3b308cac220e7a8629b0427056 - expected 34a28952e608764e4452a5b73b80175e
+
+
+Is it of interest that the last two errors have exactly the same mismatched tokens 15 seconds apart?",1396461473,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+These tests manipulate the ON/OFF toggle settings before logging in, and each browser starts with a fresh profile on every run of every scenario.  Username should be immaterial.",1396460912,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Thanks Chris, that narrows down the problem significantly.
+
+Can you rerun the tests with a different (or new) username, so we can rule out that this is a race condition with multiple tests using the same user account, or something is corrupted in the session cache?
+
+I ran the tests from the office from my linux box, and the test (whenever they finally ran) passed without any errors. So it seems like there is either something about the user that you're using, or the network lag affecting a race condition.",1396458859,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+From the log in beta labs on eqiad just now: 
+
+-04-02 07:46:39 deployment-apache02 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received cb9248cad0ffc2d5886f2322ac58c2f9 - expected ff97fcfc9650819e3788b20c26680d6b
+2014-04-02 14:36:50 deployment-apache01 enwiki: SpecialMobileOptions::submitSettingsForm(): token mismatch, received b6752dcbd18953383d871c531d620f4c - expected a3e842905af2f624cb4511345978fdc4",1396452907,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,https://gerrit.wikimedia.org/r/121879 added logging of token details to mobile.log,1396294028,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Thanks Chris. That confirms that this is different from what Jeremy posted, since his had a Location header come back from the POST request, whereas yours showed the form with the <div class=""error"">Error saving settings. Please make sure that you have cookies enabled.</div>.
+
+The only codepath that sets wsMobileToken seems pretty safe, and since the Set-Cookie with enwikiSession is returned with the form, that seems pretty safe.
+
+Could someone add a logging statement just after the token check to see what value MediaWiki thinks the mobile token is supposed to be?",1396032229,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Created attachment 14959
+WireShark capture of error conversation
+
+
+This should be the entire conversation containing the POST to MobileOptions that causes the token error. 
+
+(I happen to have another Ubuntu laptop.  After 90 OS upgrades, installing RVM and installing Wireshark, I was able to capture the traffic on a repro of the error.)
+
+**Attached**: {F13407}",1396026559,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"chris steipp, it's however worth noting that we've been unable to replicate this with the above steps on OS X",1396021309,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+Chris Steipp: 
+
+Pretty reliable repo for me has been to run the editor_ve.feature test, and the second Scenario fails with the error almost every time.  Watch the browser as the test runs to see the red error message appear before the ON/OFF toggle switches back to OFF:
+
+$ export MEDIAWIKI_URL=http://en.m.wikipedia.beta.wmflabs.org/wiki/
+$ export MEDIAWIKI_USER=USER
+$ export MEDIAWIKI_PASSWORD=PASSWORD
+
+:~/MobileFrontend/tests/browser$ bundle exec cucumber features/editor_ve.feature 
+@chrome @en.m.wikipedia.beta.wmflabs.org @firefox @login @test2.m.wikipedia.org
+Feature: VisualEditor
+
+  Background:                               # features/editor_ve.feature:4
+    Given I am in alpha mode                # features/step_definitions/common_steps.rb:77
+    And I am logged into the mobile website # features/step_definitions/common_steps.rb:10
+
+  Scenario: Switch from VisualEditor to source editor               # features/editor_ve.feature:8
+    Given I am on the ""Selenium Edit Test"" page                     # features/step_definitions/common_steps.rb:88
+    And I click the edit button                                     # features/step_definitions/editor_steps.rb:7
+    And I see the VisualEditor overlay                              # features/step_definitions/editor_ve_steps.rb:9
+    And The VisualEditor overlay has an editor mode switcher button # features/step_definitions/editor_ve_steps.rb:29
+    And I click the editor mode switcher button                     # features/step_definitions/editor_steps.rb:32
+    When I click the source editor button                           # features/step_definitions/editor_steps.rb:36
+    Then I see the wikitext editor overlay                          # features/step_definitions/editor_steps.rb:11
+
+  Scenario: Ensure we load the correct section # features/editor_ve.feature:17
+    Given I am in alpha mode                # features/step_definitions/common_steps.rb:77
+      timed out after 5 seconds, waiting for {:class=>""mw-mf-settings-off"", :tag_name=>""span""} to become present (Watir::Wait::TimeoutError)
+      ./features/step_definitions/common_steps.rb:82:in `block (3 levels) in <top (required)>'
+      ./features/step_definitions/common_steps.rb:81:in `block (2 levels) in <top (required)>'
+      ./features/step_definitions/common_steps.rb:78:in `/^I am in alpha mode$/'
+      features/editor_ve.feature:5:in `Given I am in alpha mode'",1396019125,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Jon from comment #46)
+> This is now the main source of our failing test builds (the last 3 builds
+> failed solely because of this issue)
+> 
+> Thanks for all the attention being given here.
+> 
+> I wonder if in the mean time we should alter Special:MobileOptions to use a
+> preference for logged in users rather than a cookie - this would be a way of
+> getting around the failures and would be a useful user facing feature - opt
+> in once, get beta/alpha everywhere...
+
+We would still have the same problem - at least in terms of setting the preference. In order to use that form, we need to set the CSRF token which requires the session/cookie. So when the form was submitted to set the preference, you would get stuck with the same behavior. I suppose though once the preference were set, the issue would be moot. It could be a stopgap measure... just as I think running the tests against FF/Chrome in OSX rather than linux/windows would be.",1395981689,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Is anyone able to reproduce this in the office yet? If so, I'm happy to work on this in person tomorrow. Or if someone can walk me through the steps to reproduce, I can attempt from a couple of installs I have.",1395980907,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"This is now the main source of our failing test builds (the last 3 builds failed solely because of this issue)
+
+Thanks for all the attention being given here.
+
+I wonder if in the mean time we should alter Special:MobileOptions to use a preference for logged in users rather than a cookie - this would be a way of getting around the failures and would be a useful user facing feature - opt in once, get beta/alpha everywhere...",1395968165,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Chris, in the meantime, can we point the saucelabs test to not use Linux, perhaps to use FF/Chrome in OS X since we haven't been able to replicate the issue there?",1395966051,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"CSteipp, Wireshark is killing my poor underspec'd laptop.  I spent a couple hours on this, but I cannot even get the test to complete or my wlan interface to stay functional with WireShark running.",1395950220,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Chris, can you do ""follow TCP Stream"" and screenshot the result? I'd like to confirm that you're NOT seeing a Location header returned in the result of that call.",1395941837,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"The screen shot above I think shows the token-mismatch problem on the POST.  
+
+However, the test itself behaves strangely on my local machine with WireShark running so I may have done this incorrectly",1395941530,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Created attachment 14943
+token mismatch on POST shown in WireShark on Linux
+
+**Attached**: {F13406}",1395941378,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Jeremy L Grajales from comment #39)
+> Created attachment 14914 [details]
+> (Partial) Wireshark capture of editor_ve test
+> 
+> [attachments]
+> I captured the test with Wireshark.
+> The POST is obviously the first packet in the log.
+> I find the same behavior as Chris does in Windows Firefox.
+
+So in both Chris'es headers and Jeremy's pcap, there is a session cookie being sent. So that's good.
+
+What I'm confused on is that Jeremy's pcap shows the POST to /wiki/Special:MobileOptions, and you see coming back a Location: http://en.m.wikipedia.beta.wmflabs.org/wiki/Main_Page header, which means that the inequality check in SpecialMobileOptions.php (line 208) was NOT true (i.e., the token parameter matched getMobileToken()), otherwise a form would have been returned.
+
+Is the pcap not showing the issue? Or is this not a token issue?
+
+**Attached**: {F13405}",1395939417,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(Partial) Wireshark capture of editor_ve test
+
+[attachments]
+I captured the test with Wireshark.
+The POST is obviously the first packet in the log.
+I find the same behavior as Chris does in Windows Firefox.
+
+**Attached**: {F13405}",1395848237,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+Requested by Chris Steipp, Request headers and stuff pulled from the Network tab in Firefox after incurring the token error (I also have the entire response that contains the error message if you need it): 
+
+request header: 
+
+Host: en.m.wikipedia.beta.wmflabs.org
+User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0
+Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate
+Referer: http://en.m.wikipedia.beta.wmflabs.org/wiki/Special:MobileOptions?useformat=mobile
+Cookie: centralnotice_bucket=1-4.2; mf_useformat=true; enwikiSession=ed4a7df6517c9aa79ce5231905291c84
+Connection: keep-alive
+
+request body: 
+
+Content-Type: application/x-www-form-urlencoded
+Content-Length: 87
+enableImages=on&enableBeta=on&token=b9a06d2beb98ed9b35acded20a41e9fb&returnto=Main+Page
+
+timings: 
+Waiting 892 ms
+Receiving 3 ms",1395846103,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Arthur Richards from comment #36)
+> Chris, any luck dumping those headers? I'm increasingly curious to see
+> what's going on there.
+
+What headers are you looking for at what point?
+I'd like to see it on my end to see if the Windows reproduction diverges any further from the original bug.",1395838452,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Chris McMahon from comment #27)
+> I chatted with Chris Steipp about this a bit: 
+> 
+> (03:53:51 PM) csteipp: So yeah, either the user doesn't have a session,
+> wsMobileToken in the session is getting overwritten, or the form isn't
+> correctly sending the token
+> 
+> <Antoine restarts all the caches on beta labs>
+> 
+> (04:06:19 PM) csteipp: chrismcmahon: Yeah, times out for me. So the thing is
+> to narrow down which of those 3 is happening. A header capture of a failure
+> would help determine that.
+> 
+> I'll look into getting those headers with WireShark or something.
+
+Chris, any luck dumping those headers? I'm increasingly curious to see what's going on there.",1395798413,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Change 120959 abandoned by Jdlrobson:
+See if sleeping helps avoid token issues on Special:MobileOptions
+
+Reason:
+Thanks to Jeremy L Grajales we can confirm this doesn't have any effect. Back to drawing board.
+
+https://gerrit.wikimedia.org/r/120959",1395790500,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Gerrit Notification Bot from comment #32)
+> Change 120959 had a related patch set uploaded by Jdlrobson:
+> See if sleeping helps avoid token issues on Special:MobileOptions
+> 
+> https://gerrit.wikimedia.org/r/120959
+I get the same behavior as before with the patch using Firefox on Windows.",1395790308,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Gerrit Notification Bot from comment #32)
+> Change 120959 had a related patch set uploaded by Jdlrobson:
+> See if sleeping helps avoid token issues on Special:MobileOptions
+> 
+> https://gerrit.wikimedia.org/r/120959
+I get the same behavior as before with the patch using Firefox on Windows.",1395790286,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Change 120959 had a related patch set uploaded by Jdlrobson:
+See if sleeping helps avoid token issues on Special:MobileOptions
+
+https://gerrit.wikimedia.org/r/120959",1395788208,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Jon from comment #30)
+> If the opt into alpha happens after login does this resolve the issue? I
+> wonder if it's something particularly strange with opting in whilst
+> anonymous...
+
+Don't you mean the opt into beta?
+And this is something I thought of before.
+I tried this manually, and anon or logged-in works fine.
+
+Not sure about running an automated test. But I do not have enough experience editing tests to attempt this fix you suggest. If someone could show me how to do it, I'd love to try it out. But someone else would probably have the chance to do it before I got the chance to learn how to.",1395777013,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,If the opt into alpha happens after login does this resolve the issue? I wonder if it's something particularly strange with opting in whilst anonymous...,1395769112,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+(In reply to Jon from comment #9)
+> If someone can help me get Chrome driver setup maybe I can find a way around
+> this... does delaying the opt in event with a wait help at all Chris?
+
+I also added a ""sleep 5"" below line 79 in common_steps.rb to see if that would resolve anything. Not sure if that is what you were suggesting to do. 
+
+But
+(In reply to Jeremy L Grajales from comment #28)
+adding that delay didn't change any of the previous results on Firefox (Windows).
+
+(In reply to Chris McMahon from comment #27)
+> (03:53:51 PM) csteipp: So yeah, either the user doesn't have a session,
+> wsMobileToken in the session is getting overwritten, or the form isn't
+> correctly sending the token
+
+I think this is heading in the right direction. My only objection to this is that when I attempt to reproduce this manually, everything works fine. This seems like a test handling error and not a session issue. Wouldn't a session issue affect all tests manual/automated?",1395767717,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+I tested this on Firefox (Windows).
+http://pastebin.com/yi9FGPVU
+
+Seems to reproduce the  same issue.
+Although, I'm not sure.
+
+Visually:
+The browser gets to the settings page. 
+Toggles beta switch ON.
+Saves settings.
+And when the page refreshes, the beta button is toggled to OFF.
+
+
+No obvious HTML errors are displayed as reported previously (ie. red text in the browser warning of disabled cookies).",1395764647,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+I chatted with Chris Steipp about this a bit: 
+
+(03:53:51 PM) csteipp: So yeah, either the user doesn't have a session, wsMobileToken in the session is getting overwritten, or the form isn't correctly sending the token
+
+<Antoine restarts all the caches on beta labs>
+
+(04:06:19 PM) csteipp: chrismcmahon: Yeah, times out for me. So the thing is to narrow down which of those 3 is happening. A header capture of a failure would help determine that.
+
+I'll look into getting those headers with WireShark or something.",1395702840,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Arthur Richards from comment #23)
+> I agree with Max, in this case a race condition doesn't make sense due to
+> the nature of PHP. However, it is conceivable that there are occasional
+> hiccups/something going wrong with session storage on the cluster. If that
+> were the case though, I would expect we would hear about more things like
+> this happening - that said, it is probably worth checking into since this
+> has been persistent and we have not been able to adequately explain it
+> otherwise.
+
+
+After chatting a bit with Chris today, I wonder if the problem is related to the platform and/or platform/browser combo. The jobs on sauce labs run in FF/Chrome on Linux - and when Chris tests locally he does so with a Linux box. AFAIK everyone else who has not been able to replicate this problem has been testing from a Mac.",1395696574,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Jeremy if you (In reply to Jeremy L Grajales from comment #24)
+> Is there anything I could do to attempt to replicate this on my end?
+
+Thanks Jeremy - if you don't have it set up already, the first thing to do would be to get MediaWiki and MobileFrontend setup and working. You would also need to install a few other extensions - ConfirmEdit (enable FancyCaptcha), GeoData, Echo, PageImages, VisualEditor (and get parsoid installed/running as well).
+
+Then, you'd need to get your browser testing environment set up (https://www.mediawiki.org/wiki/Quality_Assurance/Browser_testing/Running_tests), and be sure to follow MobileFrontend-specific instructions in MobileFrontend/tests/browser/README.mediawiki
+
+If you run into any problems, let us know and we can probably help you out. If you join #wikimedia-mobile on IRC (Freenode), you can usually get support faster than via Bugzilla.",1395696459,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**jeremygrajales** wrote:
+
+Is there anything I could do to attempt to replicate this on my end?",1395691908,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I agree with Max, in this case a race condition doesn't make sense due to the nature of PHP. However, it is conceivable that there are occasional hiccups/something going wrong with session storage on the cluster. If that were the case though, I would expect we would hear about more things like this happening - that said, it is probably worth checking into since this has been persistent and we have not been able to adequately explain it otherwise.",1395423730,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+I think the fact that this is passing anywhere is an environment issue.  
+
+Same error happened twice in Firefox in the build just hours ago: https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/438/",1395423484,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"As stated before, I really thing this is an environment issue. Chris what else might be different in your setup to us?",1395423372,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Chris, these are synchronous operations, it's really hard to do stufff in parallel in PHP:) So no race condition.",1395423052,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+Seems like a race condition in lines 204-208 of SpecialMobileOptions.php in submitSettingsForm. 
+
+As I read this: 
+
+* submitSettingsForm calls out to do ""$context = MobileContext::singleton();"" and also ""$request = $this->getRequest();""
+
+** both of these must take time
+
+* then the code immediately compares tokens with ""if ( $request->getVal( 'token' ) != $context->getMobileToken() )""  
+
+It seems to me like submitSettingForm should wait for both $request and $context to complete before comparing values obtained from those operations.",1395420073,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,Yep but still unable to replicate this bug in any way either locally or on beta labs...,1395327687,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"(In reply to Jon from comment #9)
+> If someone can help me get Chrome driver setup maybe I can find a way around
+> this... does delaying the opt in event with a wait help at all Chris?
+
+Jon, did you manage to get chromedriver working on your machine?",1395322601,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"and here is the same problem in Firefox, so it is not only Chrome:  https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/430/testReport/(root)/VisualEditor/Toolbar_VisualEditor/",1395174074,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"ChromeDriver (v2.9.248304)
+
+but that has nothing to do with the problem.",1395172006,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I understand - I can see this in the browser test screencast but I'm not seeing this so your environment must be setup slightly different to mine?
+
+What version of Chrome Driver are you using?",1395169983,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Created attachment 14852
+error saving settings
+
+**Attached**: {F13404}",1395168954,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I understand but I ran exactly the same test 6 times and can't replicate this. This always passes for me.
+
+What version of Chrome Driver are you using?",1395168564,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I got the problem the first time I ran, on the second scenario: 
+
+$ bundle exec cucumber features/editor_ve.feature 
+@en.m.wikipedia.beta.wmflabs.org @login @test2.m.wikipedia.org
+Feature: VisualEditor
+
+  Scenario: Toolbar VisualEditor                      # features/editor_ve.feature:4
+    Given I am in alpha mode                          # features/step_definitions/common_steps.rb:77
+    And I am logged into the mobile website           # features/step_definitions/common_steps.rb:10
+    And I am on the ""Selenium Edit Test"" page         # features/step_definitions/common_steps.rb:88
+    When I click the edit button                      # features/step_definitions/editor_steps.rb:7
+    Then I see the VisualEditor overlay               # features/step_definitions/editor_ve_steps.rb:9
+    And I see a toolbar in the overlay header         # features/step_definitions/editor_ve_steps.rb:17
+    And The VisualEditor toolbar has a bold button    # features/step_definitions/editor_ve_steps.rb:21
+    And The VisualEditor toolbar has an italic button # features/step_definitions/editor_ve_steps.rb:25
+
+  Scenario: I can edit a page using VisualEditor # features/editor_ve.feature:14
+    Given I am in alpha mode                     # features/step_definitions/common_steps.rb:77
+      timed out after 5 seconds, waiting for {:class=>""mw-mf-settings-off"", :tag_name=>""span""} to become present (Watir::Wait::TimeoutError)
+      ./features/step_definitions/common_steps.rb:82:in `block (3 levels) in <top (required)>'
+      ./features/step_definitions/common_steps.rb:81:in `block (2 levels) in <top (required)>'
+      ./features/step_definitions/common_steps.rb:78:in `/^I am in alpha mode$/'
+      features/editor_ve.feature:15:in `Given I am in alpha mode'
+
+<snip>
+
+$ date
+Tue Mar 18 11:35:44 MST 2014
+
+
+And in the browser I can clearly see the red error message ""Error saving settings. Please make sure that you have cookies enabled""",1395167909,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I have run this 6 times locally against beta labs with the latest ChromeDriver (v2.9.248307) and all passed.
+
+I'm still not sure what's going on here.",1395167488,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,If someone can help me get Chrome driver setup maybe I can find a way around this... does delaying the opt in event with a wait help at all Chris?,1395164025,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"
+To the extent that it is an issue with Selenium, the speed of the test between clicking the ""ON"" toggle and the ""Save"" button is probably triggering a race condition that is difficult to trigger manually.
+
+But if I run ""editor_ve.feature"" with the ""Given I am in alpha mode"" step 3 times on my local environment pointed to beta labs, I'll get the error 1 or 2 times.",1394841922,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,I wonder if it's possibly an issue with Selenium? This is not something I've been able to repro either and certainly not something I've experienced locally or in production.,1394833538,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Max, for me when I run the browser test ""editor_ve.feature"" (or any test with the step ""Given I am in alpha mode"") against beta labs,  I see the ""Error saving settings. Please make sure that you have cookies enabled"" pretty often, but not always.",1394821396,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"Chris, how do I repro this problem locally?",1394820350,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"I've not been able to replicate this issue myself. However if there is a bug it's going to be in getMobileToken - the only time when this error should happen is if the token in the settings form differs from the result of getMobileToken
+
+Max any ideas to why this might happen?",1394756027,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"As I said originally, this is pretty easy to repro locally, it is not just Cloudbees builds.",1394751630,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,This looks like an issue on Cloudbees. The error shows only when cookies are disabled. Are we able to say with 100% certainty Cloudbees is not doing something funky?,1394751417,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+Problem with getMobileToken in MobileContext causing browser tests to fail,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1770",1394742012,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnept6fzie6soxprbn5c,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"After moving the image
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a thumbnail image
+3.Move the image from Right to left
+4.Again move the image from right to left
+
+Observed Result:
+Moving the image from Left to Right or Right to Left changes the size of the image in the VE mode
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Test_62581?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13293}",1394663460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ptgqr6zojc4enjvswwud,task_description,resolved
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754456,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Change 118601 merged by jenkins-bot:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118601",1394752330,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Change 118427 merged by jenkins-bot:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118427",1394744965,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Change 118601 had a related patch set uploaded by Catrope:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118601",1394744857,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Change 118427 had a related patch set uploaded by Mooeypoo:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118427",1394683653,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized,"Created attachment 14797
+Before moving the image
+
+**Attached**: {F13294}",1394663634,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ptgqr6zojc4enjvswwud,task_subcomment,NA
+VisualEditor: Selection after deleting block focusablenode (e.g. image) is weird,"1. Edit a document containing a block image
+2. Click on the block image
+3. Press delete
+4. The selection looks odd
+
+Inspection of the DM selection shows that it now covers [/paragraph, paragraph].
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394658780,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-evpea5eipr52hejululr,task_description,resolved
+VisualEditor: Selection after deleting block focusablenode (e.g. image) is weird,This looks OK now… assuming that Ed fixed it. Go Ed.,1407064881,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-evpea5eipr52hejululr,task_subcomment,NA
+VisualEditor: Up and down cursor keys don't let you cursor from a focusable node into a slug,"Intention:
+Edit https://www.mediawiki.org/wiki/Sandbox
+
+Steps to Reproduce:
+1. Click on https://www.mediawiki.org/wiki/Sandbox?veaction=edit
+
+2. Press down arrow key.  Nothing happens.
+
+3. Press up arrow key.  Nothing happens.
+
+4.  Huh, how do I get off this template?
+
+Actual Results:  
+Left and right arrow keys take me to the slugs on either side, so why don't up and down arrow keys do the same?
+
+In my brief testing, this doesn't happen if there is an infobox and text on the page.  https://www.mediawiki.org/wiki/Sandbox is the only page that I'm sure it always happens on.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://www.mediawiki.org/wiki/Sandbox?veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57477",1394560560,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-vytwuphk2slvp4di2jdx,task_description,duplicate
+VisualEditor: Up and down cursor keys don't let you cursor from a focusable node into a slug,"**oliver.buchtala** wrote:
+
+It happened that I ran over that issue while debugging. Here some details that may help:
+
+The problem is, that after focussing 've.ce.Surface.onModelSelect()' runs into a case which seems to be dedicated to pasting situations:
+
+  ...
+  if ( next ) {
+    rangySel = rangy.getSelection( this.getElementDocument() );
+    if ( !ve.contains( this.$pasteTarget[0], rangySel.anchorNode, true ) ) {
+      ...
+    }
+  ...
+
+After that the window selection is on the paste element which will make the next up/down do nothing, but leaving the navigation to the CE.
+
+HTH,
+
+Oliver",1402581005,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-vytwuphk2slvp4di2jdx,task_subcomment,NA
+VisualEditor: Link input widget sometimes picks wrong link target,"Use the VisualEditor to edit an article on mediawiki.org, enter the word ""bugzilla"" and turn it into a link (highlight, Ctrl-K). The link input widget proposes a list of link targets, starting with ""bugzilla"" (checked), ""Bugzilla/Notes/4198"" and ""Bugzilla"". Click on the third one (""Bugzilla""). With quick eyes, you will notice that ""Bugzilla/Notes/4198"" is checked instead, but the list disappears immediately and the target box contains the string ""Bugzilla"". It appears as if the desired ""Bugzilla"" had been accepted as link target. Close the link input widget and preview your changes: ""Bugzilla/Notes/4198"" is used as link target.
+
+Another instance:
+
+Go to https://en.wikipedia.org/wiki/War?veaction=edit and turn the word ""integral"" in the second paragraph into a link. The link input widget proposes a list of link targets, starting with ""integral"" (checked), ""Integral domain"" and ""Integral"". Click on the third one (""Integral""). With quick eyes, you will notice that ""Integral domain"" is checked instead, but the list disappears immediately. It then appears as if the desired ""Integral"" had been accepted as link target. Close the link input widget and preview your changes: ""Integral domain"" is used as link target.
+
+It's likely that these cases won't be reproducible for long since the suggested target list is highly dependent on the respective wiki's current set of articles.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394469360,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-qbcdetoo7qm4jdonkcjz,task_description,resolved
+VisualEditor: Link input widget sometimes picks wrong link target,Fixed as part of the general link inspector work this week.,1402551024,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qbcdetoo7qm4jdonkcjz,task_subcomment,NA
+VisualEditor: Edit notices widget should clip correctly and have a max height,"https://he.wikipedia.org/wiki/%D7%9E%D7%93%D7%99%D7%94_%D7%95%D7%99%D7%A7Sandbox?veaction=edit as an anon yields to edit notices which together are way taller than the screen, which produces really weird behavior where you can't scroll to reach the bottom part of the edit notices.
+
+Either the edit notices widget should be a ClippableElement, or it should have a max height and scroll beyond that (or both).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394231940,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-inzxqv53pmck5ixn7m3p,task_description,resolved
+VisualEditor: Edit notices widget should clip correctly and have a max height,"
+
+*** This bug has been marked as a duplicate of bug 50885 ***",1397067550,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-inzxqv53pmck5ixn7m3p,task_subcomment,NA
+VisualEditor: Edit notices widget should clip correctly and have a max height,See also https://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove5?veaction=edit or https://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE8?veaction=edit for more examples. (And bug 63631 for a related bug.),1396885303,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-inzxqv53pmck5ixn7m3p,task_subcomment,NA
+VisualEditor: Edit notices widget should clip correctly and have a max height,"This bug doesn't really address the root issues here, which are that:
+* In some instances the edit notice box just needs to be wider if there's that much content to display.
+* We don't provide a way of proving VE-specific edit notices. Most notices are wrapped in coloured-margined-padded boxes which is unnecessary with our UI.",1394287105,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-inzxqv53pmck5ixn7m3p,task_subcomment,NA
+VisualEditor: Edit notices widget should clip correctly and have a max height,I prefer both.,1394233160,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-inzxqv53pmck5ixn7m3p,task_subcomment,NA
+"VisualEditor: The ""Insert reference"" button remains enabled in the reference dialog even if it is empty","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Reference
+3.Click on ""Apply Changes"" without inserting any content for the reference
+
+Observed Result:
+The empty reference gets added in the page and after saving it shows the error message:Cite error: Invalid <ref> tag; refs with no content must have a name; see the help page ().
+
+Expected Result:
+
+The ""Apply Changes"" button should remain disabled unless user enters any content for the reference 
+
+See the screenshot attached.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+http://en.wikipedia.beta.wmflabs.org/wiki/7thmarchrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12857}",1394219880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kxnh5pjmlmwxifaxh7ms,task_description,resolved
+"VisualEditor: The ""Insert reference"" button remains enabled in the reference dialog even if it is empty","
+
+*** This bug has been marked as a duplicate of bug 52182 ***",1401479536,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-kxnh5pjmlmwxifaxh7ms,task_subcomment,NA
+"VisualEditor: Backwards cursoring of an image inside an image's caption selects the sub-image, not the main image (and then breaks nastily)","Intention:
+Delete an image.
+
+Steps to Reproduce:
+1. Click on http://en.wikipedia.beta.wmflabs.org/w/index.php?oldid=82527&veaction=edit
+
+2. Place cursor inside the ==Referenced text== section heading.
+
+3. Press the forward arrow key a few times.  At the end of the line, you'll select the entire image-and-image-containing-caption block.  Forward-arrow once more, and you'll end up in the first paragraph.  (This is all expected behavior.) 
+
+4. If necessary, place your cursor in the first sentence after the ==Referenced text== section heading.
+
+5.  Press the back arrow key a few times.  This selects only the image that is inside the caption, not the entire two-image block.  You can remove the second image or change the caption for the first image (only) while your cursor is there.  If you keep back-arrowing, you'll eventually select the whole block, and then end up in the ==Referenced text== section heading. 
+
+
+Expected Results:  
+I expected forward- and backward- arrows to produce the same results.
+
+I like the ""backward"" result better.  Why not make it possible to edit captions simply by placing the cursor in the caption (either by clicking the caption [instead of the image] or with the keyboard)?
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394217540,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ykbhhmjodoocwvhdre4y,task_description,resolved
+"VisualEditor: Backwards cursoring of an image inside an image's caption selects the sub-image, not the main image (and then breaks nastily)",This was fixed a while ago by Ed's selection/node work.,1413329674,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ykbhhmjodoocwvhdre4y,task_subcomment,NA
+"If VisualEditor is open, it should be considered 'alreadyediting'","We deliberately don't show a CTA if they're already editing.  However, this is broken if they're editing with VE.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1394158500,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-uxy2xvq5jbknz67fn7wg,task_description,resolved
+"If VisualEditor is open, it should be considered 'alreadyediting'","Change 131315 merged by jenkins-bot:
+Don't show CTA on signup if user is editing with VE
+
+https://gerrit.wikimedia.org/r/131315",1399314680,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uxy2xvq5jbknz67fn7wg,task_subcomment,NA
+"If VisualEditor is open, it should be considered 'alreadyediting'","Change 131315 had a related patch set uploaded by Mattflaschen:
+Don't show CTA on signup if user is editing with VE
+
+https://gerrit.wikimedia.org/r/131315",1399170048,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uxy2xvq5jbknz67fn7wg,task_subcomment,NA
+"If VisualEditor is open, it should be considered 'alreadyediting'","This blocks the signup CTA experiment (https://trello.com/c/MaqpJE5f/405-create-pre-edit-anonymous-editor-signup-invitation-guided-tour), since it creates a very bad experience for people who click 'signup and edit' (the GettingStarted CTA stays open even when VE is fully loaded).",1399168603,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-uxy2xvq5jbknz67fn7wg,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image which has an full size less than the default size for example: http://en.wikipedia.beta.wmflabs.org/wiki/File:FS_barnstar.png
+It has a full size of 111x107 px which is less than the default size 220x212 px
+
+3.Now if you switch to set to custom size , it will show Size values are invalid as it is larger than the full size.
+
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Betachrome5th?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13258}",1394065020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_description,resolved
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",Verified the fix in production,1401392799,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",verified the fix in test2,1400808583,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Yes, I checked it with those images on Betalabs and looks like it got fixed with https://gerrit.wikimedia.org/r/#/c/120808/",1400702196,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Provisionally marking as FIXED, then. :-)",1400701822,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Just tested this again with the new MWImageModel, and it seems this bug is fixed.
+
+I tested on both Ló_heraldika.png and FS_barnstar.png with quick changes to the size (as before). Works properly for me in labs.",1400653179,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","This is still happening:
+
+Getting the error message ""Size values are invalid"" when I switch to custom from default tab.Also, also the default size is appearing as 220x245 px where as the full size of the image is 71x79 px (smaller than the default size)",1399573147,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","I can't replicate on master with the same image [[File:Ló_heraldika.png|thumb]]
+
+It appears in the proper size, which is much smaller than the default.",1397679865,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",This bug is happening again now in Betalabs and test2 for the image File:Ló_heraldika.png,1397517934,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",Verified the fix in production: https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1395350378,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",Verified the fix on test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394846409,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size",Verified the fix on :http://en.wikipedia.beta.wmflabs.org/w/index.php?title=12thmarchchrome&veaction=edit,1394649138,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Change 118231 merged by jenkins-bot:
+Deal with images whose size is smalled than default
+
+https://gerrit.wikimedia.org/r/118231",1394647852,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Change 118231 had a related patch set uploaded by Mooeypoo:
+Deal with images whose size is smalled than default
+
+https://gerrit.wikimedia.org/r/118231",1394593813,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","I can still reproduce this bug for the same image on that page when I switch from ""Set to default size"" to ""Set Custom Size""",1394582178,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Change 117161 merged by jenkins-bot:
+Enforce width-only default size only on larger images
+
+https://gerrit.wikimedia.org/r/117161",1394487125,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size","Change 117161 had a related patch set uploaded by Mooeypoo:
+Enforce width-only default size only on larger images
+
+https://gerrit.wikimedia.org/r/117161",1394082122,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w7pprk65bliocrygvf6x,task_subcomment,NA
+"VisualEditor:  Too many draggable image resizing handlers for frameless, frame, and basic images (thumbnails working as intended)","VisualEditor screenshot, showing number of image resizing handles in frameless vs thumb
+
+May be related to bug 62139.
+
+1.  Open a right-aligned image in VisualEditor.  Set to ""thumb"".  Count image resizing handlers (answer:  1).
+
+2.  Change image to ""frameless"".  Count image resizing handlers (answer:  4).
+
+I believe this also happens in ""frame"" and ""basic"", but it's a little hard to tell because of another bug (that sets them to full size).
+
+It would make more sense to only have one handle for this situation.  Two (on the two lower corners) might make sense for centered images.  Probably nothing should have a handle on the top corners.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13223}",1394057940,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-27nmtsor6eimhr5y7et3,task_description,resolved
+"VisualEditor:  Too many draggable image resizing handlers for frameless, frame, and basic images (thumbnails working as intended)","
+
+*** This bug has been marked as a duplicate of bug 61968 ***",1404850803,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-27nmtsor6eimhr5y7et3,task_subcomment,NA
+"VisualEditor:  Too many draggable image resizing handlers for frameless, frame, and basic images (thumbnails working as intended)","So, this seems to still happen in beta labs, but it's seems to be fixed in master.",1395082050,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-27nmtsor6eimhr5y7et3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Wikitext code:  [[File:Hedrick (1921) - Bartlett.jpg|thumb|Caption]]
+
+Original image dimensions:  920 × 1,216 pixels.
+
+VisualEditor says:  166.32302405498282 × 220 pixels.
+
+
+Please round to whole numbers of pixels.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394056320,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-surzsdxcrbzuyzqvftoa,task_description,resolved
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Change 117161 merged by jenkins-bot:
+Enforce width-only default size only on larger images
+
+https://gerrit.wikimedia.org/r/117161",1394487128,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Change 117161 had a related patch set uploaded by Mooeypoo:
+Enforce width-only default size only on larger images
+
+https://gerrit.wikimedia.org/r/117161",1394083233,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Apologies, I mean this fix: https://gerrit.wikimedia.org/r/#/c/117161/
+
+(Added Math.round() in the default size conversion in the dm)",1394083079,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"I still can't manage to replicate the bug on master or on betalabs, but in any case, height calculations are rounded in this patch: https://gerrit.wikimedia.org/r/#/c/117144/
+
+This should fix instances of this bug.",1394082965,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"I can't manage to replicate this, not even in betalabs.
+
+http://en.wikipedia.beta.wmflabs.org/wiki/User:Mooeypoo/Test?veaction=edit
+
+I get 166x220 in the media size widget...",1394060254,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers,"Created attachment 14746
+Screen shot of VisualEditor's image dialog, under advanced settings
+
+**Attached**: {F13209}",1394056431,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-surzsdxcrbzuyzqvftoa,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Now select the image and delete it
+4.Go to the next line by pressing enter
+
+Observed Result:
+
+
+The following error appears in the console:
+
+
+Uncaught TypeError: Cannot call method 'getChildren' of null 
+Uncaught TypeError: Cannot call method 'getChildren' of null load.php:269
+ve.ce.Surface.handleEnter load.php:269
+ve.ce.Surface.onDocumentKeyDown load.php:247
+proxy load.php:10
+ve.EventSequencer.onEvent load.php:21
+(anonymous function) load.php:20
+jQuery.event.dispatch load.php:45
+elemData.handle.eventHandle
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13081}",1393974060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhrtjoratrgaaikgkpse,task_description,resolved
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1395350472,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,Verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394846255,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=12thmarchchrome&veaction=edit,1394661636,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,"Change 118340 merged by jenkins-bot:
+Fix JS error when pressing Enter with selection across multiple paragraphs
+
+https://gerrit.wikimedia.org/r/118340",1394656820,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image,"Change 118340 had a related patch set uploaded by Catrope:
+Fix JS error when pressing Enter with selection across multiple paragrahps
+
+https://gerrit.wikimedia.org/r/118340",1394653745,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zhrtjoratrgaaikgkpse,task_subcomment,NA
+"VisualEditor: Link inspector dirties links, causes dirty diffs for links with underscores","Edit a page with wikitext [[User:Trevor_Parscal|Trevor Parscal]] ([[User talk:Trevor_Parscal|talk]]). Inspect the second link (""talk""), wait for the suggestions to load, then click out of the inspector. The save button activates. Click the save button and review the diff, and you'll see that the underscore in the link target went away.
+
+Looking at the DM transaction history, the link was replaced with a newly generated annotation that doesn't have htmlAttributes and doesn't have origTitle or any of the orig* attributes.
+
+For whatever reason, this bug doesn't happen for the first link. Maybe it's because only the second link has a namespace prefix that contains a space?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:Catrope/Bug_62229",1393966320,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jluksfszdh7gv4yindcl,task_description,resolved
+"VisualEditor: Link inspector dirties links, causes dirty diffs for links with underscores","AFAICT this is now fixed, thanks be to Parsoid.",1400719999,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jluksfszdh7gv4yindcl,task_subcomment,NA
+"VisualEditor: Link inspector dirties links, causes dirty diffs for links with underscores",Is there anything for VE to do here or will it Just Work™ once Parsoid updates the production service?,1400541259,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jluksfszdh7gv4yindcl,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Now type something and open a link inspector over it
+
+Observed Result:
+
+The ""New Page"" and ""Matching Pages"" messages are not greyed out inside Link Inspector rather appearing in a more apparent style
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13045}",1393963860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eadbguwqy532rvgz6odb,task_description,resolved
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing",Verified the fix on :https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394833642,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing",verified the fix on test2,1394149517,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing",Verified the fix in Betalabs,1394139348,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing","Change 117132 merged by jenkins-bot:
+Rename OO.ui.MenuSectonItemWidget.less to the right name
+
+https://gerrit.wikimedia.org/r/117132",1394068429,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+"VisualEditor: [Regression-pre-wmf17] Styling on ""New Page"" and ""Matching Pages"" messages inside Link Inspector missing","Change 117132 had a related patch set uploaded by Catrope:
+Rename OO.ui.MenuSectonItemWidget.less to the right name
+
+https://gerrit.wikimedia.org/r/117132",1394068172,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eadbguwqy532rvgz6odb,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"For the serialization of new transclusions we'd like to have information about the preferred formatting from TemplateData:
+
+* all parameters on a single line vs. one parameter per line
+* (possibly) preferred order of parameters by key
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393951920,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4gefxwl7us64nltukoon,task_description,duplicate
+TemplateData: Provide information about preferred formatting of transclusions,Is this a dupe of T64147 ?,1445254014,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"BTW  -Question about the ""real-world"" use: I think that block  (non-inline) templates are infobox and (almost) only infobox?  if so, we can use this as heuristic for creating a bot to fill the format field in all existing templates quite easily.",1444763318,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"Change 243138 had a related patch set uploaded (by Eranroz):
+Introducing template format
+
+[[https://gerrit.wikimedia.org/r/243138]]
+",1443782340,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"Though admittedly this is really minor issue, it has a huge impact on whether VisualEditor is accepted by power users or not. Because of this issue it is actually frowned upon to create biographies with VE in de.wikipedia, users have been told already to use the normal source code editor instead.",1442564519,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,">>! In T64217#1188824, @Schnark wrote:
+> Proper formatting actually requires more information than just single line vs. one parameter per line
+
+Yes, and we are not going to implement that. We aren't going to give the community tools to enact their epic, pointless wikitext style edit wars with each other through config settings.",1442514746,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"Proper formatting actually requires more information than just single line vs. one parameter per line:
+
+* Whitespace before pipe: For templates that should have one parameter per line this will be `""\n""`, for single line templates it can be the empty string or just a space.
+* Whitespace after pipe: In most cases either an empty string or just a space.
+* Whitespace before equal sign: This may vary widely: Empty string, one space, many spaces (depending on the length of the parameter name, to align the equal signs).
+* Whitespace after equal sign: In most cases either an empty string or just a space. But this may depend on whether the parameter has a value or not, i.e. it should be possible to have a space after the equal sign iff the value isn't empty.
+
+One important example is [[https://de.wikipedia.org/wiki/Vorlage:Personendaten|Vorlage:Personendaten (de.wikipedia)]], which provides meta-data about persons (it predates Wikidata but still fits our needs much better and thus is still actively used): To make parsing these data as easy as possible the whitespace used in the template transclusion should follow exactly the documentation. This means: When somebody uses VE to insert this template, another user //will// make [[https://de.wikipedia.org/w/index.php?title=Nazira_Abdula&curid=8786932&diff=140583554&oldid=140583398|an edit]] just to remove the spaces. So it should be possible to tell VE just not to insert them in the beginning.",1428481519,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,*** Bug 63813 has been marked as a duplicate of this bug. ***,1404840904,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+TemplateData: Provide information about preferred formatting of transclusions,"(In reply to Gabriel Wicke from comment #0)
+> For the serialization of new transclusions we'd like to have information
+> about the preferred formatting from TemplateData:
+> 
+> * all parameters on a single line vs. one parameter per line
+
+Sounds sensible.
+
+> * (possibly) preferred order of parameters by key
+
+This is already done for display purposes; I imagine we should just re-use the same order?",1393952155,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4gefxwl7us64nltukoon,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Screenshot
+
+Steps to reproduce:
+
+Yet Unknown.I am getting it by following no specific steps.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12939}",1393890420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_description,resolved
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula",Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox,1394757925,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Change 117445 merged by jenkins-bot:
+Work around DOM corruption for default-sized images
+
+https://gerrit.wikimedia.org/r/117445",1394222986,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Change 117445 had a related patch set uploaded by Catrope:
+Work around DOM corruption for default-sized images
+
+https://gerrit.wikimedia.org/r/117445",1394217795,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula",verified the fix on test2,1394152716,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula",Verified the fix on betalabs  on this page: http://en.wikipedia.beta.wmflabs.org/wiki/Editcorrupted,1394150170,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Change 117144 merged by jenkins-bot:
+Work around DOM corruption for default-sized images
+
+https://gerrit.wikimedia.org/r/117144",1394071813,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Change 117144 had a related patch set uploaded by Catrope:
+Work around DOM corruption for default-sized images
+
+https://gerrit.wikimedia.org/r/117144",1394070337,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","This is not because of galleries of formulas, but because of Moriel's fixes for default images sizes in the DM. So it manifests only for images with default size.
+
+The corruption occurs because the default image size fixes overwrite Parsoid's width/height (which is reasonable) but then also send the overwritten values back to Parsoid (which is not reasonable). We should store the original values and send those back in the HTML unless the user changed something.
+
+Additionally, the default size fixes are causing us to incorrectly size images whose original size is less than 220px. An 16x16px icon, for instance, is 16x16 even though the default bounding box is 220, because default sizing never grows an image above its original size. In this case Parsoid's width/height are actually correct, but we overwrite that with the default size, and so 16x16px icons end up rendering as 220x220px in VE and look horribly pixelated.",1394062687,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Confirmed on http://en.wikipedia.beta.wmflabs.org/wiki/Editcorrupted?veaction=edit with not actual corruption, but can't reproduce locally.",1393944051,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Getting  ""Your edit may have been corrupted – please review before saving"" message when page contains gallery/formula","Steps to reproduce:  (found later )
+
+1.Open a page with VE
+2.Add a formula or a gallery
+3.Save the page
+
+Observed Result:
+ ""Your edit may have been corrupted – please review before saving"" appears on the save dialog box",1393896082,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cqwbgfkvpqda37mpw4ej,task_subcomment,NA
+[Regression]: VisualEditor broken on private wikis,"#1 Go to https://office.wikimedia.org/wiki/HR_Corner/Massage_Signups#Standby_list
+#2 Click edit
+
+Notice how you get a 'Error loading data from server: parsoidserver-http-curl-error: Couldn't resolve host 'HR_Corner%2FMassage_Signups'
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1393887000,PHID-USER-qmantxp3p7omhisp3qgq,False,PHID-TASK-ax47g3ki5ssd7peuji3p,task_description,resolved
+[Regression]: VisualEditor broken on private wikis,"Change 116792 merged by jenkins-bot:
+Really actually fix VE on private wikis
+
+https://gerrit.wikimedia.org/r/116792",1393965485,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ax47g3ki5ssd7peuji3p,task_subcomment,NA
+[Regression]: VisualEditor broken on private wikis,"Change 116792 had a related patch set uploaded by Catrope:
+Really actually fix VE on private wikis
+
+https://gerrit.wikimedia.org/r/116792",1393965285,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ax47g3ki5ssd7peuji3p,task_subcomment,NA
+[Regression]: VisualEditor broken on private wikis,"Change 116662 merged by jenkins-bot:
+Fix VisualEditor/Parsoid on private wikis
+
+https://gerrit.wikimedia.org/r/116662",1393892507,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ax47g3ki5ssd7peuji3p,task_subcomment,NA
+[Regression]: VisualEditor broken on private wikis,"Change 116662 had a related patch set uploaded by Catrope:
+Fix VisualEditor/Parsoid on private wikis
+
+https://gerrit.wikimedia.org/r/116662",1393887842,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ax47g3ki5ssd7peuji3p,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Options>Categories
+3.Try to add a category to the page
+
+Observed Result:
+Cannot place the cursor in the Add a category text box and cannot add a category
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/Newpage3rdfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+
+**Attached**: {F12924}",1393880460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_description,resolved
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,Verified the fix in test2,1394229704,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,Verified the fix in Betalabs,1393960326,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,Fixed in OOjs UI; will be pulled into master for MW-core later today.,1393889696,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"Change 116664 merged by jenkins-bot:
+Allow focusing of inputs in booklet layouts without continuous pages
+
+https://gerrit.wikimedia.org/r/116664",1393889517,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"Change 116664 had a related patch set uploaded by Trevor Parscal:
+Allow focusing of inputs in booklet layouts without continuous pages
+
+https://gerrit.wikimedia.org/r/116664",1393889272,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"(In reply to James Forrester from comment #2)
+> Roan suggests that it may be caused by Ed's blur of surface on dialog open.
+I was wrong, it was the autofocusing of pages feature in oojs-ui, which didn't properly respect the config setting that disables it (plus had other issues). Fix inbound from Trevor.",1393889208,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,Roan suggests that it may be caused by Ed's blur of surface on dialog open.,1393881213,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs,"This seems to repeat for all input boxes inside Dialogs. It happens also for alternate text in Media Edit dialog and in the MediaSizeWidget in the same dialog.
+
+The values change properly through the automatic changes (by selecting different options) but the textboxes do not get focused and seem to be non responsive.",1393881062,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-jwmmvp23t2xd4yvcgzu4,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon","1. ""frame"" thinks you can set a size other than original size, you can't
+2. changing from ""thumbnail"" to ""frame"" doesn't hide the zoom icon
+3. changing from ""thumbnail"" or ""frame"" to border doesn't collapse the border
+4. ""border"" images come up as inline so can't be edited, even though you can convert to border from a block image
+
+I'm concerned we're merging features before they're ready. We should consider rolling back features that don't fully work yet at is looks like there's a lot still to do.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393851360,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-p4neoppdlgxnyyv67555,task_description,resolved
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon","Change 117928 merged by jenkins-bot:
+Show/hide the magnify button on type change
+
+https://gerrit.wikimedia.org/r/117928",1394485746,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon","Change 117928 had a related patch set uploaded by Mooeypoo:
+Show/hide the magnify button on type change
+
+https://gerrit.wikimedia.org/r/117928",1394484702,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon","(In reply to Ed Sanders from comment #0)
+> 1. ""frame"" thinks you can set a size other than original size, you can't
+
+Fixed.
+
+
+> 2. changing from ""thumbnail"" to ""frame"" doesn't hide the zoom icon
+
+Not fixed.
+
+> 3. changing from ""thumbnail"" or ""frame"" to border doesn't collapse the border
+
+Fixed.
+
+> 4. ""border"" images come up as inline so can't be edited, even though you can
+> convert to border from a block image
+
+Fixed.
+
+(In reply to Ed Sanders from comment #1)
+> 5. Opening the media dialog editor on a frameless centred image
+> ([[File:Example.jpg|200px|center]]) throws an exception (Cannot call method
+> 'getData' of null ve.ui.MWMediaEditDialog.js:329)
+
+Fixed.
+
+=> Re-titling.",1394082321,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon",I believe at least some of these are done in gerrit 115939.,1393867663,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+"VisualEditor: Changing a media item type from ""thumbnail"" to ""frame"" doesn't hide the zoom icon",5. Opening the media dialog editor on a frameless centred image ([[File:Example.jpg|200px|center]]) throws an exception (Cannot call method 'getData' of null ve.ui.MWMediaEditDialog.js:329),1393853079,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-p4neoppdlgxnyyv67555,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Create a heading
+3.Undo creating the heading and type something in that line instead
+4.Press enter
+
+Observed Result:
+Uncaught Error: Inserted data is trying to close the root node (at index 0) is appearing in the console.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Test62015&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13363}",1393636920,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h653ah4yfpixu3lyftgq,task_description,resolved
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,Verified the fix in production: https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394827288,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,Verified the fix in test2 environment,1394153181,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,Verified the fix in Betalabs,1394068269,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,"Change 116754 merged by jenkins-bot:
+Store previous range in breakpoint for undo
+
+https://gerrit.wikimedia.org/r/116754",1394049282,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,"Change 116754 had a related patch set uploaded by Esanders:
+Use previous breakpoint's range when undoing
+
+https://gerrit.wikimedia.org/r/116754",1393950356,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+VisualEditor: Undoing creation of empty heading places cursor at invalid offset,"In standalone demo empty.html
+
+1. Turn on 'get range on change', observe [1,1]
+2. Create heading, observe [1,1]
+3. Undo, observe [2,2]
+
+Expected: Range is still [1,1] after undo",1393946176,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-h653ah4yfpixu3lyftgq,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Steps to Reproduce:
+1. Open the page:  http://en.wikipedia.beta.wmflabs.org/w/index.php?oldid=81526&veaction=edit
+
+2. Scroll down to the image of an apple.
+
+3. Why is it barely visible?
+
+
+
+Reproducible: Always
+
+This happens in both Safari and Firefox, but only at beta.wmflabs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: http://en.wikipedia.beta.wmflabs.org/w/index.php?oldid=81526&veaction=edit",1393527000,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_description,resolved
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size",Verified the fix on : https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394833981,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size",Verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394066716,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 117123 merged by jenkins-bot:
+Force thumb and frameless images to default size in DM
+
+https://gerrit.wikimedia.org/r/117123",1394065049,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 117123 had a related patch set uploaded by Catrope:
+Force thumb and frameless images to default size in DM
+
+https://gerrit.wikimedia.org/r/117123",1394064922,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 117106 merged by jenkins-bot:
+Force thumb and frameless images to default size in DM
+
+https://gerrit.wikimedia.org/r/117106",1394064404,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 117106 had a related patch set uploaded by Catrope:
+Force thumb and frameless images to default size in DM
+
+https://gerrit.wikimedia.org/r/117106",1394061403,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size",Verified the fix in betalabs,1394050967,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046687,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Change 115939 had a related patch set uploaded by Jforrester:
+Add type 'none' to the media edit dialog
+
+https://gerrit.wikimedia.org/r/115939",1393536027,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+"VisualEditor: [Regression wmf16] Floated images of type ""none"" display as only a couple of pixels wide, not full-size","Created attachment 14705
+Image display bug
+
+**Attached**: {F13189}",1393527050,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-dr3mdcdnc5tips2mh57g,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**Author:** `robert.labrie`
+
+**Description:**
+Intention:
+Add media with visual editor
+
+Steps to Reproduce:
+LocalSettings.php and wiresharks are attached. The MW search does work. I can do a partial name search for an image in the File namespace and it works. The gallery in mediawiki does not.
+
+Actual Results:  
+No images
+
+Expected Results:  
+Images
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1393522440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-feyxsootc5yehsnjglpn,task_description,invalid
+VisualEditor: Add media does not search local repo when MW is in root,This appears to be a core MW issue with unsupported hosting paths. Closing as INVALID.,1394727592,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"If you access the MediaWiki core api.php entry point directly in your browser, what do you get back?
+
+It should look like this: https://www.mediawiki.org/w/api.php
+
+If it doesn't then there is nothing VisualEditor can do as it means your server is not configured correctly to expose MediaWiki's entry points (perhaps you only whitelisted index.php?).
+
+This likely means other features are broken as well (the autocompleting of page names in the search box, the ""Watch this page"" button etc.).
+
+Serving the MediaWiki application directory from your document root is highly discouraged.  If you don't like exposing a /wiki/ path in URLs you can keep the application in /w/ but let Apache rewrite your urls from /Page_name to /w/index.php. That way you have both nice urls in the root, but still keep your application's internal files tucked away safely in /w. See https://www.mediawiki.org/wiki/Manual:Short_URL and related pages.",1394561612,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"(In reply to James Forrester from comment #6)
+> Moriel – was this what Gerrit change #112491 fixed?
+
+That change fixed another related bug, but apparently there are other remaining issues after that fix that I'm trying to understand. 
+
+I think it has to do with the fact the wiki is installed in the root directory. The media search seems to skip looking for files in the local repository.",1394492099,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,Moriel – was this what gerrit 112491 fixed?,1393640336,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**robert.labrie** wrote:
+
+Hi James,
+
+I'm not sure. What I do know is that VE never sends a search to the API. It does a filerepoinfo and that's the end of it. Whatever I type in the searchbox, nothing gets sent to the API.
+
+If you give me a sample querystring I'll change the srsearch param to match something that should be found and test it.",1393594146,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,Is this related to the issue we found (fixed?) in MediaWiki core recently about certain configurations of document root and the file search API?,1393540075,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**robert.labrie** wrote:
+
+My local settings file
+
+**Attached**: {F13178}",1393522748,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**robert.labrie** wrote:
+
+search pcap
+
+This is just proving that the search does work. Something is broken in the way VisualEditor calls the API, or in the results the API returns.
+
+**Attached**: {F13177}",1393522605,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+VisualEditor: Add media does not search local repo when MW is in root,"**robert.labrie** wrote:
+
+visual editor pcap
+
+This shows the whole experience from clicking edit to clicking add media. You can see the call to API.php where it asks for repos, it gets nothing back.
+
+**Attached**: {F13176}",1393522556,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-feyxsootc5yehsnjglpn,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates","Right now you can re-position an inline transclusion in the same way as images, with a click-drag feature. Unfortunately this isn't set for block transclusions.
+
+This is particularly irritating for suers because when you initially insert a transclusion we assume it's inline, so let them move it, but then when they re-open the page it's now magically un-moveable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1393521720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_description,resolved
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates",I'm declaring that it was.,1408650245,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates",Was this fixed by the changes to GCNs?,1404934961,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates","The problem here is not block templates, but that the CE HTML is <div wrapper><table float:right/></div>, and the relocatable marker takes it's dimensions from the <div> (which has no height).
+
+In ProtectedNode we solve this by drawing boxes around _every_ descendent. Ideally we'll come up with a better solution before we start add drag handlers to them.",1393611288,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates","Abandoned that, the test case I was using appears to be an edge case, it actually works ok.",1393607320,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates",Disable on block images for now: https://gerrit.wikimedia.org/r/#/c/116118/,1393605930,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+"VisualEditor: Create relocatable markers for complex shapes, e.g. block templates","Relocatable doesn't work on block elements atm. We have it enabled for block images, but it breaks.",1393605805,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-d7no6zkv7cafcmlb4pgb,task_subcomment,NA
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image 
+3.Make it frameless
+4.Keep on resizing down the image going beyond 1x1 px.
+5.Click anywhere on the page
+
+Observed Result:
+
+The image becomes a dot size . and user can no more select or find Media Settings icon for it.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13101}",1393459860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nfrfujiczibmostmogl4,task_description,resolved
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,Sorry on:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394833482,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nfrfujiczibmostmogl4,task_subcomment,NA
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,Verified the fix in production:http://en.wikipedia.beta.wmflabs.org/wiki/Slug?veaction=edit,1394833422,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nfrfujiczibmostmogl4,task_subcomment,NA
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,Verified the fix in test2 environment.,1394153006,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nfrfujiczibmostmogl4,task_subcomment,NA
+VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it,Verified the fix in Betalabs,1394068793,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nfrfujiczibmostmogl4,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references","Invalid input
+
+Steps to reproduce:
+
+1.Open a page with VE which has multiple references
+2.Go to Insert>Reference>Use an existing reference
+3.Now input something in the search box which will have no search result
+4.Now cross out the dialog box
+5.Again go to Insert>Reference
+
+Observed Result:
+The ""Use an existing reference"" button is disabled and it does not become enabled for the rest of the session unless user cancels the edit and reopen the page again with VE
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13055}",1393448280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_description,resolved
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references",Verified the fix in test2 :https://test2.wikipedia.org/wiki/Wmf19?veaction=edit,1395356010,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references","Change 119702 merged by jenkins-bot:
+Don't use search widget emptiness as a proxy for ""no reusable references""
+
+https://gerrit.wikimedia.org/r/119702",1395294643,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references","Change 119702 had a related patch set uploaded by Catrope:
+Don't use search widget emptiness as a proxy for ""no reusable references""
+
+https://gerrit.wikimedia.org/r/119702",1395294485,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" button becomes disabled for the current session once user inputs an invalid search term for searching existing references","Created attachment 14692
+Disabled ""Use an existing reference"" button
+
+**Attached**: {F13056}",1393448346,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fxa5h2jzelmnjbfjhslc,task_subcomment,NA
+VisualEditor: Breaking words on diacritics,"VisualEditor breaking words on diacritics
+
+A user was trying to remove the duplicated header which is on section ""Propriedades Algébricas"" of
+https://pt.wikipedia.org/wiki/Logaritmo?oldid=38172637&veaction=edit
+
+After deleting the duplicated cells, Visual Editor also removes part of a word from the previous paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://pt.wikipedia.org/w/index.php?title=Logaritmo&diff=38264880&oldid=38264877
+
+**Attached**: {F13042}",1393436040,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-pgrl2ozbdinedqyu3zhp,task_description,resolved
+VisualEditor: Breaking words on diacritics,"I suspect this had nothing to do with diacritics, but was because there was unbalanced wikitext. It looks like Parsoid outputs that particular wikitext differently now anyway. Suggest WONTFIX.",1408119118,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pgrl2ozbdinedqyu3zhp,task_subcomment,NA
+Move EventLogging component from MediaWiki extensions product to Analytics product,"Move EventLogging component from MediaWiki extensions product to Analytics product, as requested via email.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1393417560,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-jwug2jk4wwdhybwdo5mt,task_description,resolved
+Move EventLogging component from MediaWiki extensions product to Analytics product,"I'm still trying to adjust to VisualEditor being a product instead of a component under ""MediaWiki extensions."" Now I'll have to add a mental exception for EventLogging as well. Blergh.",1393562759,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-jwug2jk4wwdhybwdo5mt,task_subcomment,NA
+Move EventLogging component from MediaWiki extensions product to Analytics product,Done.,1393419433,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-jwug2jk4wwdhybwdo5mt,task_subcomment,NA
+ApiQueryLogEvents STRAIGHT_JOIN queries slow,"enwiki has been seeing a bunch of slow ApiQueryLogEvents queries:
+
+SELECT /* ApiQueryLogEvents::execute */ /*! STRAIGHT_JOIN */ log_type, log_action, log_timestamp, log_deleted, log_id, page_id, log_user, log_user_text, user_name, log_namespace, log_title, log_comment, log_params FROM `logging` LEFT JOIN `user` ON ((user_id=log_user)) LEFT JOIN `page` ON ((log_namespace=page_namespace) AND (log_title=page_title)) INNER JOIN `change_tag` ON ((log_id=ct_log_id)) WHERE (log_type != 'suppress') AND ct_tag = 'Possible self promotion in userspace' ORDER BY log_timestamp DESC LIMIT 11
+
+SELECT /* ApiQueryLogEvents::execute */ /*! STRAIGHT_JOIN */ log_type, log_action, log_timestamp, log_deleted, log_namespace, log_title, ts_tags FROM `logging` LEFT JOIN `user` ON ((user_id=log_user)) LEFT JOIN `page` ON ((log_namespace=page_namespace) AND (log_title=page_title)) LEFT JOIN `tag_summary` ON ((log_id=ts_log_id)) INNER JOIN `change_tag` ON ((log_id=ct_log_id)) WHERE (log_type != 'suppress') AND ct_tag = 'VisualEditor' ORDER BY log_timestamp DESC LIMIT 11
+
+... and several other similar forms.
+
+In all cases the STRAIGHT_JOIN forces an index scan on logging.times index, or more rarely a range access on logging.type_time index. Both query plans hit tens of millions of rows and take many minutes.
+
+Removing the STRAIGHT_JOIN allows the MariaDB query optimizer to choose a plan that takes seconds. Often it includes a filesort step, but more importantly it allows ""index condition pushdown"" which makes the filesort cheap.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: major",1393296960,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-7oof4yk2z7twkxa4m44m,task_description,resolved
+ApiQueryLogEvents STRAIGHT_JOIN queries slow,"Change 115381 merged by Springle:
+Remove STRAIGHT_JOIN from ApiQueryLogEvents
+
+https://gerrit.wikimedia.org/r/115381",1393375751,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7oof4yk2z7twkxa4m44m,task_subcomment,NA
+ApiQueryLogEvents STRAIGHT_JOIN queries slow,"Change 115381 had a related patch set uploaded by Anomie:
+Remove STRAIGHT_JOIN from ApiQueryLogEvents
+
+https://gerrit.wikimedia.org/r/115381",1393340810,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7oof4yk2z7twkxa4m44m,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which contains an image
+2.Select the image
+3.Go to Insert>References List
+
+Observed Result:
+The Save page button becomes active though there is no new reflist got added.If you click on ""Review Your Changes"" on the Save Dialog box, it will say 
+""Could not start the review because your revision matches the latest version of this page""
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12904}",1393288440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_description,resolved
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active",Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1398379382,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active",Verified the fix in test2,1397867310,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active",Verified the fix on Betalabs,1397512208,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active","Change 125799 merged by jenkins-bot:
+Fix inserting references list while selecting another kind of node
+
+https://gerrit.wikimedia.org/r/125799",1397504972,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+"VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the ""Save Page"" button becomes active","Change 125799 had a related patch set uploaded by Trevor Parscal:
+(Bug 61885) Inserting ref list while selecting another kind of node
+
+https://gerrit.wikimedia.org/r/125799",1397504587,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-na3kvjeuvjvrfmdfp33y,task_subcomment,NA
+VisualEditor:  Don't set STATICREDIRECT if there's no redirect on the page,"Steps to reproduce:
+1.  Start with a blank page.
+
+2.  Go to Page settings.
+
+3.  Tick both redirect-related boxes, but don't provide a page name.
+
+4.  Apply changes.
+
+
+Results:
+It sets __STATICREDIRECT__, which is not pointful on an otherwise blank page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61864",1393271280,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-hixhmoom5yqrm66bfq43,task_description,resolved
+VisualEditor:  Don't set STATICREDIRECT if there's no redirect on the page,"Change 115239 merged by jenkins-bot:
+Don't let the user set a static redirect flag on a non-redirect
+
+https://gerrit.wikimedia.org/r/115239",1393279753,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hixhmoom5yqrm66bfq43,task_subcomment,NA
+VisualEditor:  Don't set STATICREDIRECT if there's no redirect on the page,"Change 115239 had a related patch set uploaded by Jforrester:
+Don't let the user set a static redirect flag on a non-redirect
+
+https://gerrit.wikimedia.org/r/115239",1393272739,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hixhmoom5yqrm66bfq43,task_subcomment,NA
+VisualEditor:  Don't set STATICREDIRECT if there's no redirect on the page,Hmm. This shouldn't be possible – I think this is the same issue as bug 61864.,1393271388,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hixhmoom5yqrm66bfq43,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,"In the ""Page settings"" dialog, it says ""Redirect this page to"" and a blank field for the target name.  If you put a name in there, then it sets a redirect, even if you don't tick the checkbox.  
+
+VisualEditor should automatically tick the checkbox there if it's going to set a redirect (e.g., as soon as you start typing).  Otherwise, it looks like it's not going to redirect the page when you exit the dialog box.
+
+(Reproducing this has only been consistent if there is no redirect on the page at the start of the editing session.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61865",1393270920,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_description,resolved
+VisualEditor: Disable the redirect input field unless the checkbox is checked,verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Imageghau,1393546614,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,"Change 115237 merged by jenkins-bot:
+Disable redirect field unless the checkbox is set in setup
+
+https://gerrit.wikimedia.org/r/115237",1393279661,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,"Change 115237 had a related patch set uploaded by Jforrester:
+Disable redirect field unless the checkbox is set in setup
+
+https://gerrit.wikimedia.org/r/115237",1393272601,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,*** Bug 61866 has been marked as a duplicate of this bug. ***,1393272393,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: Disable the redirect input field unless the checkbox is checked,"The logic for this box is meant to work the other way around - that is, you can't set a redirect unless you check the box first - but a simple forgotten line made this not work in one (very frequent) case: when the page isn't a redirect and you're making it one. Whoops. :-(",1393272380,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gw4kqg7hxd3uiuwopwmw,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"Intention:
+Add one ref
+
+Steps to Reproduce:
+1. Opened an existing ref, copied the contents, and cancelled out of the dialog.
+
+2. Opened a new ref, pasted what I'd just copied, changed the contents slightly, and applied changes.
+
+
+Actual Results:  
+All the <ref name = whatever> tags on the page were ""corrected"".
+
+Expected Results:  
+Nothing would change in paragraphs that I didn't touch.
+
+Reproducible: Didn't try
+
+This is presumably a regression, but search couldn't find any bugs containing the word ""name"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=912199&oldid=840682",1393017180,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_description,declined
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"I, too, can't reproduce – possibly a Parsoid deployment cache artefact? Closing as WFM.",1393355731,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"I can't reproduce this today in Safari (which is what I was using at the time), either.  Perhaps it has been fixed already?  Perhaps there's something unfortunately subtle about it (e.g., must click eleven times first, only on the night before the last quarter of the Moon)?",1393355173,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"Can't reproduce using that specific revision of the page, and the same edit, either in FF or Chrome.",1393345365,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"(In reply to WhatamIdoing from comment #2)
+> https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/
+> Sandbox&diff=912199&oldid=840682
+
+Very odd. Seems to be something on that page triggering the behaviour?",1393021033,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=912199&oldid=840682,1393020870,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?),"I tried this on MediaWiki.org, following your steps with this edit: https://www.mediawiki.org/w/index.php?title=VisualEditor:TestReferenceContents&diff=912228&oldid=768024
+
+As you can see, I couldn't reproduce. Can you give a link to a page where this happens?",1393017648,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gjdoj3a3jrnvxz3zslyj,task_subcomment,NA
+"VisualEditor: If the edit summary is empty, don't show a preview of it (""()"") in the Review Changes panel","Screenshot
+
+Do no Show empty summary preview: () when there is no summary in Review Changes dialog box
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13076}",1392940980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6m7f64h6b4dqidv7aoqk,task_description,resolved
+"VisualEditor: If the edit summary is empty, don't show a preview of it (""()"") in the Review Changes panel",Verified the fix in betalabs,1393277147,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6m7f64h6b4dqidv7aoqk,task_subcomment,NA
+"VisualEditor: If the edit summary is empty, don't show a preview of it (""()"") in the Review Changes panel","Change 114737 merged by jenkins-bot:
+Don't show edit summary preview if it's blank
+
+https://gerrit.wikimedia.org/r/114737",1393083591,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6m7f64h6b4dqidv7aoqk,task_subcomment,NA
+"VisualEditor: If the edit summary is empty, don't show a preview of it (""()"") in the Review Changes panel","Change 114737 had a related patch set uploaded by Alex Monk:
+Don't show edit summary preview if it's blank
+
+https://gerrit.wikimedia.org/r/114737",1392987765,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6m7f64h6b4dqidv7aoqk,task_subcomment,NA
+"VisualEditor: Copy/pasting blanks page, prevents saving","Reported on fr.wp:
+<<Here is how I did : on the page https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Ch%C3%A2teau_Rothschild_(Boulogne-Billancourt) opened with VE, ""Historique"" section, copy from ""Joseph Fleuriau d'Armenonville"" to ""évoqua brièvement le lieu."" Then paste it somewhere on the page https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Brouillon [it's a sandbox, it's ok to test there], and everything will be deleted. 
+I also noticed that a few times nothing was deleted but nothing was pasted too. [...]
+I have the same bug with FF 29 with both W7 and W8.1, and also Chrome 32 with W7. Nemesis III (me contacter), le 19 février 2014 à 19:16 (CET). >>
+
+I reproduced this as well.
+In addition, the first time it didn't blank the destination page, and the same happened on one of my sandboxes. Then one time it blanked the page, allowed me to save, I got the confirmation message but nothing was recorded (the history doesn't have signs of this).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392835080,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-nn2dv56qvs3mjvm533mq,task_description,declined
+"VisualEditor: Copy/pasting blanks page, prevents saving",Can't reproduce.,1409070187,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-nn2dv56qvs3mjvm533mq,task_subcomment,NA
+"VisualEditor: Copy/pasting blanks page, prevents saving","This is happening elsewhere as well.
+I was testing if you can copy/paste a reference from a VE instance on one wiki to another (from sv.wp to it.wp).
+Sometimes it takes a lot for the save dialog to appear; in other cases the action just leads to page blanking.",1395751667,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-nn2dv56qvs3mjvm533mq,task_subcomment,NA
+VisualEditor: Shift-selection of a template and then typing-replacement can cause pawns in Firefox,"VEdit https://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove2?veaction=edit in Firefox.
+
+Place your cursor right below the initial template, press Shift and the Up arrow to select it, type something = pawn.
+
+NicoV, who found this, says you can also start from the line above the template, Shift + Down arrow in that case.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58675
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54917",1392821340,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-q4ectqywx354prbxw6g6,task_description,resolved
+VisualEditor: Shift-selection of a template and then typing-replacement can cause pawns in Firefox,This is fixed now.,1406598517,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-q4ectqywx354prbxw6g6,task_subcomment,NA
+VisualEditor: Shift-selection of a template and then typing-replacement can cause pawns in Firefox,"Simple test case:
+{{Simple table include}}
+Foo
+
+Place the cursor before 'Foo', press up (shift not requred) and type.
+
+Interestingly if the block template is float right it works fine.",1392828352,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-q4ectqywx354prbxw6g6,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add a text with reference
+3.Add a reflist
+4.Go to the next line of the text with reference and add an image
+5.Go to the Media settings of the image and set the alignment to left(This should move the image between reference and reflist , instead it distorts the reflist position and it appears just beside the image instead of appearing below it)
+6.Save the page
+7.Reopen the page
+8.Try to the position of reflist it by pressing enter 
+
+Observed Result:
+No newline gets entered , an error appears in the console:
+Uncaught TypeError: Cannot call method 'getModel' of null 
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Anotherdeep?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13298}",1392770580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kc7quhrwey6274zbvvpw,task_description,resolved
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return",This issue got resolved with  bug 59911,1393635082,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return","The pressing-enter-in-the-slug bug is I think bug 59911, so merging with that.
+
+*** This bug has been marked as a duplicate of bug 59911 ***",1393474403,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return","I don't see anything wrong with the rendering, it looks pretty similar to the PHP parser output. The pressing-enter-in-the-slug bug is a problem though.",1392915710,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return","(In reply to ryasmeen from comment #1)
+> This is also happening when the first element of a page is image and you try
+> to press enter to go to the next line
+
+Correction: When the first element of a page is a left aligned image",1392857061,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and ""Cannot call method 'getModel' of null "" appears while trying to fix it by pressing return",This is also happening when the first element of a page is image and you try to press enter to go to the next line,1392856767,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kc7quhrwey6274zbvvpw,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","pawn before the link
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Create a link
+3.Type something just before the link
+4.Type something just after the link
+4.Click on ""Undo"" several times
+
+Observed Result:
+
+A pawn appears right before and after the link 
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=18thfebchrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13288}",1392762420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_description,resolved
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action",No pawns now.,1421282614,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","I'm not taking this bug either, but I can reproduce it -if I make the link in the block slug-. Which I wasn't doing when I tested this before.",1416333719,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","Created attachment 17150
+video capture of the bug
+
+See the video capture attached
+
+**Attached**: {F13290}",1416266032,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action",I just reproduced this on Chrome in Betalabs,1416265954,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","Tried again, seems fixed.",1416184177,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action",Cannot reproduce.,1415813522,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","I might be reopening the wrong bug, but this doesn't seem to be fixed.
+
+1) VEdit any article on the French Wikipedia.
+2) Type some words exactly before a wikilinked single word. (Based on my tests, it doesn't really matter if we add one word or several ones.)
+3) Undo your edit with the related keyboard shortcut or the Undo button: a pawn will appear. Undo again, the pawn might disappear, undo one more time, it appears again, etc.
+I was able to reproduce with Vector and Safari.",1410170185,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action",I think this is now fixed.,1406599124,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+"VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by ""undo"" action","Created attachment 14622
+Pawn after the link
+
+**Attached**: {F13289}",1392762479,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2mwqn6vwc6bznvjfn3vg,task_subcomment,NA
+VisualEditor: Moving templates down is broken,"1. Go to template dialog
+2. Insert two templates (or a template and a content item, or whatever)
+3. Click the bottom one and click the up arrow to move it up; this works
+4. Click the top one and click the down arrow; nothing happens
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392420840,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vsxmfaftb5u77hxjzrlr,task_description,resolved
+VisualEditor:  Box for alt text in the media dialog is too small,"This is related to bug 38129.
+
+The alt text box in the media dialog is only about two-thirds the width of the screen, with no possibility of wrapping/scrolling down.  Maybe eight words fit in it (two-thirds of the example given in the lead of https://en.wikipedia.org/wiki/WP:ALT).  
+
+It should be at least the normal width of the dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392317880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-2lbvzwvr2rcpaahfrzu7,task_description,resolved
+VisualEditor:  Box for alt text in the media dialog is too small,Verified the fix in test2,1392940065,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-2lbvzwvr2rcpaahfrzu7,task_subcomment,NA
+VisualEditor:  Box for alt text in the media dialog is too small,"Change 114022 merged by jenkins-bot:
+Make alternate text input stretch to full width
+
+https://gerrit.wikimedia.org/r/114022",1392758254,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2lbvzwvr2rcpaahfrzu7,task_subcomment,NA
+VisualEditor:  Box for alt text in the media dialog is too small,"Change 114022 had a related patch set uploaded by Mooeypoo:
+Make alternate text input stretch to full width
+
+https://gerrit.wikimedia.org/r/114022",1392752877,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2lbvzwvr2rcpaahfrzu7,task_subcomment,NA
+VisualEditor:  Don't specify the default alignment for images (in the resulting wikitext),"This is related to bug 51293, bug 61323, and the general bug 38129:
+
+The alignment options in the media dialog's advanced settings are:
+
+Left
+Center
+Right
+None
+
+It is the convention to not specify the alignment when choosing the default, mostly to avoid needless clutter in the wikitext.  If the default is right (or left), and the user chooses that default, then VisualEditor should not add ""right"" but instead should leave the alignment setting empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392315180,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6xlmfh5z7qar45y5xdva,task_description,resolved
+VisualEditor:  Don't specify the default alignment for images (in the resulting wikitext),*** Bug 61565 has been marked as a duplicate of this bug. ***,1393447031,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6xlmfh5z7qar45y5xdva,task_subcomment,NA
+VisualEditor:  Don't specify the default alignment for images (in the resulting wikitext),Done last week (I think).,1393446964,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6xlmfh5z7qar45y5xdva,task_subcomment,NA
+"VisualEditor:  Provide a button in the image dialog box's advanced settings to set ""default"" alignment for images","This is related to bug 51293 and the general bug 38129:
+
+The alignment options in the media dialog's advanced settings are:
+
+Left
+Center
+Right
+None
+
+These are the four explicit settings provided in MediaWiki.
+
+Most users, even if they click on a few buttons to consider other options, are going to want the image at the default (i.e., on the right for left-to-right languages).  It is the convention to not specify the default, mostly to avoid needless clutter in the wikitext.
+
+Most users have no idea what ""None"" does because they've never encountered it before.  They're going to think that it means ""unspecified default"", rather than left-and-clear.  
+
+It would be good to offer a ""default"" button, even though this duplicates the function of one of the existing buttons.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392315060,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-p4knbm6poo246efefsph,task_description,resolved
+"VisualEditor:  Provide a button in the image dialog box's advanced settings to set ""default"" alignment for images",Verified the fix in betalabs.,1393546976,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-p4knbm6poo246efefsph,task_subcomment,NA
+"VisualEditor:  Provide a button in the image dialog box's advanced settings to set ""default"" alignment for images",*** Bug 56609 has been marked as a duplicate of this bug. ***,1393528443,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p4knbm6poo246efefsph,task_subcomment,NA
+"VisualEditor:  Provide a button in the image dialog box's advanced settings to set ""default"" alignment for images",Done in gerrit 114420.,1393446852,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p4knbm6poo246efefsph,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","Actual Results:  
+You can only see about 1.5 lines of text.  It should be tall enough to display two lines of text, even if people are using slightly larger fonts.
+
+
+Reproducible: Always
+
+Multiple complaints with screenshots:
+
+https://en.wikipedia.org/wiki/File:Euromaidan_VisualEditor_infobox.PNG
+
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_13#Multiple_issues_-_minimal_space
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60541",1392253440,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rfnk22psp766igbje5es,task_description,resolved
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","Cool, please keep no limit for the size, some template have a lot of content :
+https://fr.wikipedia.org/w/index.php?title=Espèces_du_genre_Carex&oldid=96878307&veaction=edit",1393544143,PHID-USER-hhw22zfd2xzrsyc22lp5,True,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured",*** Bug 61859 has been marked as a duplicate of this bug. ***,1393271161,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","As of gerrit 114527 parameter value boxes will now auto-size (without maximum), and when empty (or have a short value) will show as just a single line (actually ""normal size"" which is ~1.5x in height).
+
+(In reply to WhatamIdoing from comment #2)
+> Other suggestions from en.wp:
+>  
+> * At least three lines tall.
+
+I think that's too large for default; most parameter values are simple entries (e.g. a file name or an author's surname). We want filling in the fields to seem like a quick, easy thing to do, not an overwhelming prompt to write an essay. However, we could possibly bump the minimum size to larger than 1.5x, though I'd still be worried about making them too large. Note the size of the boxes in the sketch of the citation dialog by way of example: https://www.mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog#mediaviewer/File:VE-reference-dailog-design-04b.png – this change was done as part of that work. I suggest we re-visit this if it doesn't feel like it's working out very well.
+
+
+> * Scrollbars as needed.
+
+Right now they'll just grow without limit, which means if it's such an insanely large parameter value that it's larger than the dialog it will get scrollbars, but otherwise it will just grow. Maybe we could set a maximum size (10 lines? 5?) and then scroll when larger than that? Perhaps something for another bug?
+
+
+> * Ability to resize the window vertically.
+
+Which ""window""? The dialog itself, or the text box? If the latter, that's now done; if the former, I don't think that that's a reasonable outcome (because it breaks the design for mobile, limited vision users, and others with small screen sizes, and because it's Yet Another Control for users to have to understand what it does, why they'd use it, and how it works).
+
+
+> * Replace the grey area between parameters by a line (less space wasted, as
+> readable as before), don't use large padding inside the fields, reduce white
+> space between parameter name and value.
+
+The first and third of these points is also being done as part of the citation dialog work; if anything, we're probably going to increase the padding on the input boxes in line with that work, though.
+
+
+Am thus closing this bug as FIXED for now, with an adjustment to the title to reflect the design decision, and we can open further bugs for other ideas.",1393009160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","Other suggestions from en.wp:
+ 
+* At least three lines tall.
+
+* Scrollbars as needed.
+
+* Ability to resize the window vertically.
+
+* Replace the grey area between parameters by a line (less space wasted, as readable as before), don't use large padding inside the fields, reduce white space between parameter name and value.",1392750930,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured","We may want to re-visit this when these boxes are rich content, but whilst as wikitext they're likely to be expansive more often than not.",1392352160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rfnk22psp766igbje5es,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Screenshot
+
+Steps to reproduce:
+
+1.Open this page with VE:http://en.wikipedia.beta.wmflabs.org/wiki/12thfebchrome?veaction=edit
+
+2.Go to the Media Settings for the image:[[File:Dau ho thoi Ho.png]]
+
+3.Set the Width size of the image to 8000 and Apply changes (Works fine)
+
+4.Set the Width of the image to 8000000 and apply changes (Still work fine)
+
+
+5.Set the Width of the image to 80000000 and Apply changes 
+
+Observed Result:
+The image shrinks to a dot size in the VE mode
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13328}",1392233220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gczwgyrlggneqddarcum,task_description,resolved
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"This looks like it's now fixed, I think.",1404850639,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Created attachment 14785
+Reproduced on windows8-chrome
+
+**Attached**: {F13330}",1394478635,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"I can't replicate here; I set the image even up to ""800000000000000000000"" width and still it resized as ""expected"".",1394413820,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Created attachment 14761
+This is how it appears in the review changes in the save dialog
+
+**Attached**: {F13329}",1394133756,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"I see this image as a huge one. There is a bug here that the context menu is hidden outside the page (should be reported separately) but I don't see this as a dot-size.
+
+Checked under Windows on Chrome version 33.0.1750.146 m and Firefox 27.0.1
+
+In both cases, I see this image as humongous, which is exactly as it appears in the ""view"" mode. 
+
+I can't manage to replicate the ""dot-image"" effect.",1394070360,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,Another page and image where I encountered this issue: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Hateres&veaction=edit,1394069805,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,I can still reproduce this issue for the image :[[File:Dau ho thoi Ho.png]] with Frame and Basic Image type,1394064287,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046682,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Change 115939 had a related patch set uploaded by Mooeypoo:
+[wip] Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1393991570,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,I can still reproduce this issue.,1393459000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Change 115307 merged by jenkins-bot:
+Limit thumbnail dimensions in media edit dialog
+
+https://gerrit.wikimedia.org/r/115307",1393447584,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"Change 115307 had a related patch set uploaded by Mooeypoo:
+[wip] Limit thumbnail dimensions in media edit dialog
+
+https://gerrit.wikimedia.org/r/115307",1393279148,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size,"I can't replicate the exact phenomenon, but it does seem to show an issue with maximum dimensions.
+
+When I increase the size (even to the 80000000 width) I just get a humongous version of the stretched image. 
+
+I'm looking into the conditions of limiting image scale size.",1393275231,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-gczwgyrlggneqddarcum,task_subcomment,NA
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen","Intention:
+edit Polish Wikipedia using VisualEditor
+
+Steps to Reproduce:
+1. difflink 1: https://pl.wikipedia.org/w/index.php?title=Amalowie&diff=38322555&oldid=38322515
+2. difflink 2: https://pl.wikipedia.org/w/index.php?title=Amalowie&diff=prev&oldid=38322515
+3. discussion link: https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Edytor_wizualny_psuje_przypisy
+
+Actual Results:  
+snowmen appear (see difflink 1) and text disappears or ""gets eaten""
+
+Expected Results:  
+no snowmen and text is inserted where it is wanted
+
+Reproducible: Didn't try
+
+please see bug:54712 and bug:54976 re: snowmen
+
+please see bug:51624 and bug:50286 re: backspace
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Edytor_wizualny_psuje_przypisy",1392226980,PHID-USER-brn4v5ta45bnw4f5as3h,True,PHID-TASK-7l43lybihonkgrfu2q5d,task_description,declined
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen","I played around a bit with Chrome, Firefox and Opera and couldn't reproduce. Closing as WORKSFORME, but that feels bad…",1395252569,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7l43lybihonkgrfu2q5d,task_subcomment,NA
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen","I /think/ the editor replied that that problem didn't occur again since, and that he doesn't want to test further. If you want you can play with my sandbox at https://pl.wikipedia.org/wiki/Wikipedysta:Elitre_(WMF)/sandbox or just close this provisionally. Thanks.",1395239221,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7l43lybihonkgrfu2q5d,task_subcomment,NA
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen",I asked for details at pl.wp.,1395232579,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7l43lybihonkgrfu2q5d,task_subcomment,NA
+"VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen",Difficult to do anything without steps to reproduce...,1395230444,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-7l43lybihonkgrfu2q5d,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Misaligned Undo/Re-do buttons at Beta Labs
+
+The Undo/re-do buttons aren't lined up properly in the toolbar at Beta Labs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13192}",1392142980,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-thvvordl2hv7kcsai3bw,task_description,resolved
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112946 abandoned by Jforrester:
+Fix margins after they were broken in 9d988924
+
+Reason:
+Whoops, this is wmf13 only.
+
+https://gerrit.wikimedia.org/r/112946",1392239534,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112814 merged by jenkins-bot:
+Fix margins after they were broken in 9d988924
+
+https://gerrit.wikimedia.org/r/112814",1392239524,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112947 had a related patch set uploaded by Jforrester:
+Fix margins after they were broken in 9d988924
+
+https://gerrit.wikimedia.org/r/112947",1392239463,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112946 had a related patch set uploaded by Jforrester:
+Fix margins after they were broken in 9d988924
+
+https://gerrit.wikimedia.org/r/112946",1392239439,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Change 112814 had a related patch set uploaded by Jforrester:
+Fix margins after they were broken in 9d988924
+
+https://gerrit.wikimedia.org/r/112814",1392160140,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs),"Resolved in Ie6b47f5d1929533669118ba51202c1fccda4a0d6
+
+Basically, Liangent made a change to the padding of the content div Vector and didn't make a corresponding change to the toolbar in the VisualEditor extension.",1392156068,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-thvvordl2hv7kcsai3bw,task_subcomment,NA
+VisualEditor: [Regression] Link inspector prevents addition of section links to existing links,"Take text. Make link to page (""Foo""). Observe wikitext. Good.
+
+Take text. Make link to page with section (""Foo#Bar""). Observe wikitext. Bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1392138660,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-evpxmbfxyief5l7gsbk6,task_description,resolved
+VisualEditor: [Regression] Link inspector prevents addition of section links to existing links,Fixed in gerrit 112898.,1392231577,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-evpxmbfxyief5l7gsbk6,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings>Advanced Settings for that image
+4.Select the option Border under Image Type
+
+Observed Result:
+There is no value/Change appears for this image type
+The resulting wikitext is:
+[[File:Wheat (flo).JPG|200x200px||left]]
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=10thFeb&action=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392064020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_description,resolved
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755538,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,Verified the fix in test2,1394228977,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,Verified the fix in Betalabs,1394051975,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046685,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Change 115939 had a related patch set uploaded by Mooeypoo:
+[wip] Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1393628853,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Created attachment 14708
+Screenshot
+
+**Attached**: {F13029}",1393539331,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Still not working for me.I could still reproduce it in page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27thfebff&action=edit
+
+See the screenshot attached",1393539304,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Change 112041 merged by jenkins-bot:
+Revamp media edit dialog's position widget
+
+https://gerrit.wikimedia.org/r/112041",1392940263,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Change 112041 had a related patch set uploaded by Jforrester:
+Revamp media edit dialog's position widget
+
+https://gerrit.wikimedia.org/r/112041",1392162364,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,"Found the bug, the wikitext doesn't have |border even though the CE is updated.
+
+This commit seems to fix it: https://gerrit.wikimedia.org/r/#/c/112041/",1392160784,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field,Cannot replicate in master in both Chrome 32 and Firefox 27 under Ubuntu.,1392155939,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-kuwpox6ibgr56bpzslcr,task_subcomment,NA
+VisualEditor: Resize text in Option menu or put it on two lines if too long,"In French, the option to switch to wikitext is called ""Basculer vers la modification du code"". In Italian, it's ""Passa alla modifica sorgente"".
+In both languages the text is so long you need to slide to the right to see all of it. Is there a better way to display it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392060000,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_description,resolved
+VisualEditor: Resize text in Option menu or put it on two lines if too long,"Merging into bug 57366.
+
+*** This bug has been marked as a duplicate of bug 57366 ***",1401743910,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_subcomment,NA
+VisualEditor: Resize text in Option menu or put it on two lines if too long,"I spent a while looking into this. I gave up but here is what I found anyway
+
+First of all I tried to make it expand outwards instead of squashing against the side, and couldn't get that to work.
+
+Then I tried making the text wrap instead, found I could set the white-space CSS property on the tool title which kind of did the job, but it was not working well enough (last word of a wrapped line would overflow). I found word-break: break-word; but that only made things look worse.",1398977073,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_subcomment,NA
+VisualEditor: Resize text in Option menu or put it on two lines if too long,"I asked on fr.wp. On the Italian one, this is still the case with Monobook, but Vector displays the message just fine...",1394615953,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_subcomment,NA
+VisualEditor: Resize text in Option menu or put it on two lines if too long,Could we improve the translations to be briefer?,1394502042,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5mgdsk4ykjr4lc4rfm3a,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","In mobile various JavaScript and CSS modules are loaded that are not needed including OO JS UI.css (see https://gerrit.wikimedia.org/r/#/c/109940/)
+
+After talking to Trevor and Timo we agreed that it would be a good idea to refactor and break out many of VisualEditor's modules to support a much slimmer mobile version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391820360,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_description,resolved
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS",Done.,1393464256,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","Change 113488 merged by jenkins-bot:
+Split up ext.visualEditor.mwcore into smaller parts
+
+https://gerrit.wikimedia.org/r/113488",1393464108,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","Change 113487 merged by jenkins-bot:
+Split VE-MW's ve.ce.Node.css file into per-node files
+
+https://gerrit.wikimedia.org/r/113487",1392932889,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","Change 113488 had a related patch set uploaded by Jforrester:
+Split up ext.visualEditor.mwcore into smaller parts
+
+https://gerrit.wikimedia.org/r/113488",1392423592,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS","Change 113487 had a related patch set uploaded by Jforrester:
+Split VE-MW's ve.ce.Node.css file into per-node files
+
+https://gerrit.wikimedia.org/r/113487",1392423585,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mppl4c4v4ljpt2byhnxf,task_subcomment,NA
+"VisualEditor: Link inspector ""Matching/redirect/disambiguation page"" messages should be pluralized","""visualeditor-linkinspector-suggest-matching-page"": ""Matching page"",
+""visualeditor-linkinspector-suggest-disambig-page"": ""Disambiguation page"",
+""visualeditor-linkinspector-suggest-redirect-page"": ""Redirect page""
+
+These messages should be something like {{PLURAL:$1|Matching page|Matching pages}} instead, and be passed the number of pages in the section.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391818380,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-32vq2w6nrmkqhr2ecptb,task_description,resolved
+"VisualEditor: Link inspector ""Matching/redirect/disambiguation page"" messages should be pluralized","Change 112164 merged by jenkins-bot:
+Pluralise visualeditor-linkinspector-suggest-(matching|redirect|disambig)-page
+
+https://gerrit.wikimedia.org/r/112164",1391822396,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-32vq2w6nrmkqhr2ecptb,task_subcomment,NA
+"VisualEditor: Link inspector ""Matching/redirect/disambiguation page"" messages should be pluralized","Change 112164 had a related patch set uploaded by Alex Monk:
+Pluralise visualeditor-linkinspector-suggest-(matching|redirect|disambig)-page
+
+https://gerrit.wikimedia.org/r/112164",1391819746,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-32vq2w6nrmkqhr2ecptb,task_subcomment,NA
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image
+3.Open the media settings for that image
+4.Go to Advanced Settings tab
+5.Change the image size to something different than what it is right now
+6.Click on ""Apply Changes""
+7.Reopen the Media Settings again and go to Advanced Settings panel
+
+Observed Results:
+The Size values are still reflecting the previous value unless user saves the whole page and open the panel again it stays like this.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit#cite_ref-2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391803020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-boiihq6lvygsgus2qbrt,task_description,resolved
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,Verified the fix on test2,1392253579,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-boiihq6lvygsgus2qbrt,task_subcomment,NA
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,"Change 112950 merged by jenkins-bot:
+Quick fix: image size property update
+
+https://gerrit.wikimedia.org/r/112950",1392242431,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-boiihq6lvygsgus2qbrt,task_subcomment,NA
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,"Change 113014 had a related patch set uploaded by Catrope:
+Quick fix: image size property update
+
+https://gerrit.wikimedia.org/r/113014",1392242394,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-boiihq6lvygsgus2qbrt,task_subcomment,NA
+VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page,"Change 112950 had a related patch set uploaded by Mooeypoo:
+Fix image size property update
+
+https://gerrit.wikimedia.org/r/112950",1392239704,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-boiihq6lvygsgus2qbrt,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE which contains a image at the right
+
+2.Select the image 
+
+3.Go to the Media Settings> Advanced Settings
+
+4.Move the position of the image to center
+
+5.Select some other element or just click outside the image anywhere on the page
+
+
+Observed result:
+Cannot select any other object in the page 
+An error appears in the console:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 227
+
+See the screenshot attached.
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Ehat?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13303}",1391732220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yk5ghixsbt7pcjv7wois,task_description,resolved
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,verified the fix in test2,1392943781,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,"Change 113258 merged by jenkins-bot:
+Prevent clicks on top-most shield for centered image nodes
+
+https://gerrit.wikimedia.org/r/113258",1392854973,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,I believe that gerrit 113256 fixed part of this issue.,1392748429,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,"Change 113258 had a related patch set uploaded by Jforrester:
+Prevent clicks on top-most shield for centered image nodes
+
+https://gerrit.wikimedia.org/r/113258",1392748207,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page,It happens while moving an image from Left to Right too,1391732797,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yk5ghixsbt7pcjv7wois,task_subcomment,NA
+VisualEditor: Format action applies to nodes inside handlesOwnChildren node,"1. Select a block image with caption
+2. Press the list button
+
+Expected:
+Either nothing, or a list is created above/below the image
+
+Observed:
+The caption is wrapped in a list
+
+Clearly we need to ignore nodes which are inside handlesOwnChildren nodes when applying such actions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60804",1391704140,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-p6nh7m7ljbshvwyj2lmd,task_description,resolved
+VisualEditor: Format action applies to nodes inside handlesOwnChildren node,"Change 111822 merged by jenkins-bot:
+Don't descend into handlesOwnChildren nodes in selectNodes
+
+https://gerrit.wikimedia.org/r/111822",1391803183,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p6nh7m7ljbshvwyj2lmd,task_subcomment,NA
+VisualEditor: Format action applies to nodes inside handlesOwnChildren node,I'm assuming that bug 60804 the same issue.,1391708410,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p6nh7m7ljbshvwyj2lmd,task_subcomment,NA
+VisualEditor: Format action applies to nodes inside handlesOwnChildren node,"Change 111822 had a related patch set uploaded by Esanders:
+Don't descend into handlesOwnChildren nodes in selectNodes
+
+https://gerrit.wikimedia.org/r/111822",1391707727,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p6nh7m7ljbshvwyj2lmd,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"See 
+https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE3&diff=63988076&oldid=63988055 ,
+or https://it.wikipedia.org/w/index.php?title=Oreste_Tommasini&diff=63836558&oldid=61161898, or https://it.wikipedia.org/w/index.php?title=Frederic_William_Maitland&diff=63692381&oldid=59785358 .
+
+Reproduced with Chrome, FF, Opera (unlogged), tested with both skins.
+
+You only need to add the Template:Interprogetto to an existing page or a new one.
+Useless code like <span data-ve-ignore=""true"" about=""g0.8632714317645878""></span> is added.
+James, bug 59653, IMHO, had a similar problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60375",1391610120,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_description,resolved
+VisualEditor: HTML content model constraints are sometimes violated,"Change 111518 merged by jenkins-bot:
+Only generate transclusion contents for clipboard
+
+https://gerrit.wikimedia.org/r/111518",1391641350,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"Change 111518 had a related patch set uploaded by Esanders:
+Only generate transclusion contents for clipboard
+
+https://gerrit.wikimedia.org/r/111518",1391632112,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"(In reply to comment #5)
+> Is Bug 60375 related?
+
+Looks like it.",1391630206,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,Moving it back to VE.,1391626970,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,Is Bug 60375 related?,1391626108,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,This is scenario #3 from https://www.mediawiki.org/wiki/Parsoid/DOM_notes#Efficient_re-rendering_on_edits,1391621996,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"So this is caused by new templates always being inline templates, as we don't know if they are block templates until they render. As a result the above HTML is invalid (<ul> inside a <p>) which after Parsoid fixes, means the about-grouped items are no longer siblings.",1391621604,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"This extra HTML is correctly added here for the sake of putting something meaningful into the external clipboard. data-ve-ignore tells the converter to ignore it if it's pasted into another VE instances, and about=""g[random]"" tells Parsoid to ignore it. However the about grouping appears not to be working at Parsoids end:
+
+HTML:
+<p><span about=""g1"" typeof=""mw:Transclusion"" data-mw=""{&quot;parts&quot;:[{&quot;template&quot;:{&quot;target&quot;:{&quot;href&quot;:&quot;Template:Interprogetto&quot;,&quot;wt&quot;:&quot;Interprogetto&quot;},&quot;params&quot;:{&quot;commons&quot;:{&quot;wt&quot;:&quot;cats&quot;}}}}]}"" data-ve-no-generated-contents=""true""></span><span data-ve-ignore=""true"" about=""g1""></span><ul data-ve-ignore=""true"" about=""g1"">
+<li>Foo</li>
+</ul>
+<span data-ve-ignore=""true"" about=""g1"">
+
+</span></p>
+
+Wikitext:
+{{Interprogetto|commons = cats}}
+* Foo
+
+<span data-ve-ignore=""true"" about=""g1""></span>
+
+The first about-grouped sibling is discarded, but the subsequent ul and span are not.",1391619704,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: HTML content model constraints are sometimes violated,"There was a related issue beforehand – but this isn't getting copied, so I can't work out out data-ve-ignore is getting added to the HTML?",1391618697,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ypnibbwkhkctaw6xxskl,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"link text appearing for the second time
+
+Steps to reproduce:
+
+1.Select a math function/image/gallery/hiero
+2.Now open the link inspector
+3.Insert a link (this link gets placed just before the selected element)
+4.Again select the element
+5.Open the link inserter
+6.Observe that the link title of the previous link is appearing now in the link inspector
+7.Close the link inspector.
+
+Observed Result:
+The link text title of the previous link is getting inserted just before the selected element.
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Image_then_gallery?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12936}",1391544360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_description,resolved
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Verified the fix in production,1411682155,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Verified the fix in test2,1411082475,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Verified the fix in Betalabs,1410981634,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,I can't reproduce. Probably fixed by Ed's recent cleanup of the link inspector.,1410955005,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"Never mind, I'm an idiot. It's still broken if you try to inspect the same reference with the link inspector twice in a row.",1408732836,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Confirmed fixed in master but not in wmf18.,1408732672,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,I think this is fixed now? I can't reproduce it any more...,1408690676,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Roan says the fix is to fix the pre-population of the link inspector in create mode. I think.,1406144930,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,Selection's not being re-set to the actual link (of the pre-annotation stack or something odd)?,1405969347,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,This is not yet fixed.The link text is still getting added next to the previously added link,1402700275,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"Change 138114 merged by jenkins-bot:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533853,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"Change 138114 had a related patch set uploaded by Catrope:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533735,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element,"Created attachment 14487
+link text getting added before math function
+
+**Attached**: {F12937}",1391544477,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-f6765ahcloqg4k3lhy2n,task_subcomment,NA
+VisualEditor: Images trigger creation of huge protectedNode-shields that cover the page,"Any time I try to use the mobile VisualEditor on a page that includes an image, it is not editable due to having a protectedNode-shield covering most of the page. You can see an example at:
+https://en.m.wikipedia.org/wiki/Rice_flour#editor/0
+
+The protectedNode-shield has a width of 100% and a height of 100% and it appears that each image creates a new one.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1391542860,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ark2omnqbkzm4rckjjjm,task_description,resolved
+VisualEditor: Images trigger creation of huge protectedNode-shields that cover the page,"**jgonera** wrote:
+
+Fix in https://gerrit.wikimedia.org/r/#/c/113475/",1392420075,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ark2omnqbkzm4rckjjjm,task_subcomment,NA
+VisualEditor: Images trigger creation of huge protectedNode-shields that cover the page,*** Bug 60103 has been marked as a duplicate of this bug. ***,1391647241,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ark2omnqbkzm4rckjjjm,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Intention:
+Add a gallery
+
+Steps to Reproduce:
+1. Open a page in Safari.
+
+2. Go to Insert > Gallery
+
+3. Type in the name of an image and a caption.  *Don't click or type anywhere else after this.*
+
+4. Click on the save button.
+
+5. Realize that the gallery dialog is still open, so cancel the save box.  The dialog will close and the gallery will display.
+
+6. Click on the save button again.
+
+Actual Results:  
+The gallery displays on screen, but is not present in Review Changes or when the page is saved.
+
+If you click outside the gallery dialog after typing the name, or if you click the mysterious < button, then it works as expected.
+
+Expected Results:  
+A button at the bottom of the gallery inserter that says ""Insert this gallery now"".
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67049",1391540760,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-d6fvkqxdzbk3emadetgp,task_description,resolved
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Change 112893 merged by jenkins-bot:
+Give the document focus on save dialog open to resolve inspectors
+
+https://gerrit.wikimedia.org/r/112893",1392229720,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","(In reply to comment #6)
+> 2. OOUI defers the close event of the dialog by 250ms for animation purposes,
+> after which we set up a one-time listener to surface-transact to clear the
+> serialization cache, but the transaction has already happened.
+> 
+Is there an event / method in OOUI (closing as opposed to close, maybe?) that fires before the animation? Then we could listen to that and immediately attach the event listener.",1392229631,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","1. The document is given focus, triggering events which result in the inspectors being closed, and a transaction being created which inserts the extension node.
+2. OOUI defers the close event of the dialog by 250ms for animation purposes, after which we set up a one-time listener to surface-transact to clear the serialization cache, but the transaction has already happened.
+
+Fix:
+Give the document focus before opening the save dialog to make sure it's in a more stable state.",1392214713,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Change 112893 had a related patch set uploaded by Esanders:
+Give the document focus on save dialog open to resolve inspectors
+
+https://gerrit.wikimedia.org/r/112893",1392214526,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Actually the CE and DM aren't out of sync, but the new document isn't being passed to Parsoid.",1392137057,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Yuck.
+
+Clicking out of an inspector *into the surface* causes the inspector to close, applying changes.
+
+Clicking out of an inspector *outside the surface* (such as the save dialog launcher) causes the inspector to not close; when the save dialog is closed, this also closes the inspector and ""insert"" the content into CE but NOT DM, causing them to get out of sync. Not good.",1391661572,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","More Observation: This issue happens for all other inspector for example: Math,Hiero, Link inspector.",1391547427,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+"VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion","Created attachment 14483
+Screenshot displaying a visible gallery, and displaying the absence of the gallery in the wikitext code
+
+**Attached**: {F12922}",1391540887,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-d6fvkqxdzbk3emadetgp,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a image
+3.Open the media settings for the image
+4.Insert a link as a caption
+5.Save the page
+6.Reopen the page and select the image
+7.Open the link inspector and type in a different a link inside it
+8.Save the page
+9.Reopen the page and the Media Settings for the image
+
+Observed Result:
+The link inside the caption got changed by the link inserter in step 7
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60969
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58045",1391480580,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dstdh5ubda4mfhlddsus,task_description,resolved
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,Verified the fix in production,1397177603,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,Verified the fix in mediawiki.org,1396992640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,"Change 123429 merged by jenkins-bot:
+Skip over handlesOwnChildren nodes in newFromAnnotation
+
+https://gerrit.wikimedia.org/r/123429",1396469415,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,"Change 123429 had a related patch set uploaded by Esanders:
+Skip over handlesOwnChildren nodes in newFromAnnotation
+
+https://gerrit.wikimedia.org/r/123429",1396469204,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,If there are multiple links inside the media caption then the link applied outside the image gets applied to all other links .,1396385672,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor: Creating a link while selecting an image modified the link inside the caption,"Created attachment 14472
+Screenshot of the error
+
+**Attached**: {F12832}",1391480774,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dstdh5ubda4mfhlddsus,task_subcomment,NA
+VisualEditor:  It should not be possible to paste images from external websites into the references dialog,"Intention:
+Replicate a mess seen at https://pt.wikipedia.org/w/index.php?title=Esporte_Clube_Pelotas&curid=68824&diff=38075497&oldid=38075466
+
+Steps to Reproduce:
+1. Start creating a new reference.
+2. Open nytimes.com and select both some text and one small image. 
+3. Copy the selection and paste it into the ref dialog box.
+
+Actual Results:  
+In Safari, nothing pastes.  In Firefox, both text and image rich-paste into the ref dialog box, but I can't save the page.
+
+Expected Results:  
+That the image would be discarded, since it's not uploaded to the wiki.
+
+Reproducible: Sometimes
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391457300,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wkw5zbjzhfqvkpwqq4dz,task_description,resolved
+VisualEditor:  It should not be possible to paste images from external websites into the references dialog,Verified in betalabs.,1414093606,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-wkw5zbjzhfqvkpwqq4dz,task_subcomment,NA
+VisualEditor:  It should not be possible to paste images from external websites into the references dialog,"AFAICT this is now completely fixed; however, in testing this I uncovered bug 72385 which is sigh-inducing.",1414011221,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wkw5zbjzhfqvkpwqq4dz,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"**As an editor I can get paste a link or DOI into a simple form to get an auto-filled citation.**
+
+A user has their cursor in a place they would like to add a citation. 
+They click the Cite button on the toolbar. 
+An inspector opens in context, showing the title ""Cite"" a URL field, and a ""Lookup"" button.
+
+Click-through prototype http://invis.io/HR2DK2FXM
+
+**Workflow**
+{F55330}
+
+**Detail of citation inspector**
+Include line below field with link that opens the manual citation dialogue.
+{F45790}
+
+**Manual Citation Dialogue**
+First step now includes all items in the former Cite menu
+{F43867}
+
+**Errors**
+DOI error - if incorrect amount of characters entered
+{F43776}
+
+URL error - if page not found
+{F45749}
+
+Generic error
+{F45752}
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391446500,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_description,resolved
+Cite: Auto-filled references based on destination URL / DOI etc.,">>! In T62768#1138925, @Mvolz wrote:
+> FYI citoid does not support ISBNs yet so I edited that bit out- very surprised to find out we supported ISBNs when I read the tech bulletin on my RSS reader this morning, and it was probably because it was in the description here. 
+
+Thank you for the heads-up. I wasn't sure we'd be announcing this in Tech News, because I was confused about the status of this feature, due to last week's rushed deployment. This is why this task was marked as ""Not ready to announce"" (which does apply to Tech News). On Friday, James added the item to the newsletter, and I edited it to use simpler language; I also added the ISBN bit, based on this task's title.
+
+> @gpaumier Also, I noticed this is tagged ""not ready to announce"" yet - does that not apply to tech bulletin? If so there's still technically time to remove it because even though it ended up in my RSS reader, because publication is not technically until tomorrow. 
+
+Yes, however we can't make last-minute edits to the newsletter because that only changes the English version; translators need more time to echo the changes.
+
+Considering that:
+* the current text is inaccurate and could cause confusion if sent,
+* the current text only concerns two wikis that have already been notified of the feature,
+* and there is no urgency in sending this information,
+I've removed the Citoid item from this week's issue entirely, and added it to the list of items to announce in next week's newsletter.
+",1427122926,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Elitre, I agree. It hasn't been re-triggered for translation yet so there
+is still time to remove that link.",1427026425,PHID-USER-evd3wnvnlb66lrwulch4,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"(I find the link to the [[ https://www.mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog | design page ]] confusing. Some parts of the interface are different in production - and the last 2 screenshots on the page would show the regular Cite flow - which is not so ""connected"" to Citoid.)",1427026149,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"FYI citoid does not support ISBNs yet so I edited that bit out- very surprised to find out we supported ISBNs when I read the tech bulletin on my RSS reader this morning, and it was probably because it was in the description here. 
+
+@gpaumier Also, I noticed this is tagged ""not ready to announce"" yet - does that not apply to tech bulletin? If so there's still technically time to remove it because even though it ended up in my RSS reader, because publication is not technically until tomorrow. ",1427013644,PHID-USER-evd3wnvnlb66lrwulch4,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"FYI citoid does not support ISBNs yet so I edited that bit out- very surprised to find out we supported ISBNs when I read the tech bulletin on my RSS reader this morning, and it was probably because it was in the description here. Also, I noticed this is tagged ""not ready to announce"" yet - does that not apply to tech bulletin? If so there's still technically time to remove it because even though it ended up in my RSS reader, because publication is not technically until tomorrow. ",1427013067,PHID-USER-evd3wnvnlb66lrwulch4,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 198261 abandoned by Mooeypoo:
+Add general citations dialog
+
+Reason:
+Not needed.
+
+[[https://gerrit.wikimedia.org/r/198261]]",1426898858,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 198261 had a related patch set uploaded (by Mooeypoo):
+Add general citations dialog
+
+[[https://gerrit.wikimedia.org/r/198261]]
+",1426873551,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 197925 merged by jenkins-bot:
+Enable Citoid extension on all VisualEditor wikis
+
+[[https://gerrit.wikimedia.org/r/197925]]",1426780531,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 197925 had a related patch set uploaded (by Alex Monk):
+Enable Citoid extension on all VisualEditor wikis
+
+[[https://gerrit.wikimedia.org/r/197925]]
+",1426780007,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 197074 merged by jenkins-bot:
+Enable Citoid extension on all VisualEditor wikis
+
+[[https://gerrit.wikimedia.org/r/197074]]",1426778958,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 195802 merged by jenkins-bot:
+Redesign the citation widget in the citoid inspector
+
+[[https://gerrit.wikimedia.org/r/195802]]",1426552347,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 196645 merged by jenkins-bot:
+Add general citations dialog
+
+[[https://gerrit.wikimedia.org/r/196645]]",1426551858,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 197074 had a related patch set uploaded (by Jforrester):
+Enable Citoid extension on all VisualEditor wikis
+
+[[https://gerrit.wikimedia.org/r/197074]]
+",1426523008,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 196645 had a related patch set uploaded (by Mooeypoo):
+[wip] Add general citations dialog
+
+[[https://gerrit.wikimedia.org/r/196645]]
+",1426278790,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Change 195802 had a related patch set uploaded (by Mooeypoo):
+Redesign the citation widget in the citoid inspector
+
+[[https://gerrit.wikimedia.org/r/195802]]
+",1426030328,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,">>! In T62768#1094741, @Eloquence wrote:
+> Can we project a ""week of"" deployment ETA?
+
+No. Everything is backed up on {T89656} which has an unknown schedule.",1425684052,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Can we project a ""week of"" deployment ETA?",1425610555,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Hi Marielle,
+I think we should leave the user on the same screen, in case they messed up the number and want to try again. 
+We should show an error message that says something like ""We couldn't find that book"" and maybe give a hint like ""An ISBN is usually 10 or 13 digits.""
+And the user still has the option at the bottom to go to the screen to enter the citation manually.
+{F20069}",1418077680,PHID-USER-flenunkasbjk4topxvaj,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"Hi Kaity,
+
+What should the user see if there are no results?
+
+For most urls I think it should just be the linked url, and then they can edit that, but for some identifiers (like issn, isbn) it's definitely possible there won't be anything to display at all. And we may or may not know what kind of ID it is (although we could guess?) I'm assuming it should go to this page https://www.mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog#mediaviewer/File:Magic_cite4-02.png automatically but should there be some sort of error message or something....
+
+Also it's possible that if the scraping is bad- i.e. it's just the text of the url as the title- these automatically are set as web citations, but it's possible the user will want to change the citation type from web to journal, for instance. Any thoughts on that?",1417693157,PHID-USER-evd3wnvnlb66lrwulch4,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,,1417555606,PHID-USER-flenunkasbjk4topxvaj,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,,1417554442,PHID-USER-flenunkasbjk4topxvaj,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,"(In reply to WhatamIdoing from comment #0)
+> It would be convenient if the reference tool would autofill {{cite book}}
+> from a URL to books.google.com  This is done in several existing gadgets on
+> the English Wikipedia and is especially helpful for books that do not have
+> ISBNs.
+
+Czech Wikipedia could be filled from national book database. I think their API might be available to us as we were already negotiating with them. Basically every time I fill reference template and also ISBN variable I wonder, why this cant be done automaticaly as in many countries such data are available and readable for scripts.
+
+But what Ive been talking about in https://bugzilla.wikimedia.org/show_bug.cgi?id=60863
+
+was just to load some basic options and than the user should file them by values. But this proposal is even better.",1392633415,PHID-USER-vm462i2ffbawnuo4mh3n,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,*** Bug 60863 has been marked as a duplicate of this bug. ***,1391708860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+Cite: Auto-filled references based on destination URL / DOI etc.,This is part of bug 50768's re-written merged form; am re-splitting and using this one for the second half.,1391448623,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yko76gbkbhubxt5cplo5,task_subcomment,NA
+VisualEditor: VE doesn't load on mobile anymore,"http://en.m.wikipedia.beta.wmflabs.org/wiki/Forty-seven_Ronin?mobileaction=alpha#editor/0
+
+Error: Container must be attached to the DOM Error {stack: (...), message: ""Container must be attached to the DOM""}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391133180,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_description,resolved
+VisualEditor: VE doesn't load on mobile anymore,"Change 110498 merged by jenkins-bot:
+Fix VE error with latest VE master
+
+https://gerrit.wikimedia.org/r/110498",1391191162,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_subcomment,NA
+VisualEditor: VE doesn't load on mobile anymore,"Change 110498 had a related patch set uploaded by JGonera:
+Fix VE error with latest VE master
+
+https://gerrit.wikimedia.org/r/110498",1391135465,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_subcomment,NA
+VisualEditor: VE doesn't load on mobile anymore,"@Juliusz: Looks like the .surface element selector here is either not finding anything at all or it is referring to something that is still detached at that point:
+
+https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/blob/c4264d76bc817df71c6b3631afb19be737246c52/javascripts/modules/editor/VisualEditorOverlay.js#L16
+
+It doesn't have to be fully initialised, but the target container element should however be somewhere in the document.",1391134025,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_subcomment,NA
+VisualEditor: VE doesn't load on mobile anymore,"This is exposing a pre-existing bug in mobile VE or MobileFrontend's VE integration or something in this ecosystem: you cannot initialize targets into a container that isn't already attached to the DOM. Previously, you could do this and various things regarding measurements would just break and render wrong, but now we throw an exception.",1391133988,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nxdykwxwefwrkkwa2sxc,task_subcomment,NA
+VisualEditor: Closing a Math inspector deletes the selected node/element,"Steps to reproduce:
+
+
+1.Open a page with VE
+2.Now select an image or a reference note in the Page
+3.Now Open the Gallery from Insert>Gallery
+
+Observed Result:
+
+It deletes the image and the reference note.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391023680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ddwzsz5d7gwehcqqwr6x,task_description,resolved
+VisualEditor: Closing a Math inspector deletes the selected node/element,This was fixed a while ago by Ed.,1402296411,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ddwzsz5d7gwehcqqwr6x,task_subcomment,NA
+VisualEditor: Closing a Math inspector deletes the selected node/element,And then close the Math inspector.,1391023868,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ddwzsz5d7gwehcqqwr6x,task_subcomment,NA
+VisualEditor: Closing a Math inspector deletes the selected node/element,"Sorry the third step should be ""Insert>Formula""",1391023807,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ddwzsz5d7gwehcqqwr6x,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"The CSS file modules/ve-mw/ce/styles/ve.ce.Node.css implements styling of page content. This styling should be handled by the skin, not by VisualEditor. It looks like someone already figured this out, as most of the styles include TODO notes about merging them into core styles.
+
+As the mobile team is now implementing VE with a mobile-specific skin, now would be the best time to make these fixes. Otherwise, lots of !important overrides will be necessary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390944600,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-lmv6en7m2i2nthp4bbad,task_description,resolved
+VisualEditor: Let skin variance for styling of <figures> in page content,"Change 112618 merged by jenkins-bot:
+Move some skin styling from ve.ce.Node.css to a shared skin css file
+
+https://gerrit.wikimedia.org/r/112618",1392845587,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"Change 112618 had a related patch set uploaded by Kaldari:
+Move some skin styling from ve.ce.Node.css to the skin styles
+
+https://gerrit.wikimedia.org/r/112618",1392081287,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"Talked to Roan. He definitely favors solution 2 and gave me some advice on implementing it. Apparently VE already has some skin styling in it (modules/ve-mw/init/styles/), so most of these styles should just be moved there.",1392062806,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"There are two possible solutions:
+
+1. Make VE's page DOM more similar to the normal rendered page DOM. That way VE won't have to worry about styling them as they'll be styled by existing skin styles. (This seemed to be a solution favored by Trevor.)
+
+2. Add support for some VE-specific elements to the skins, for example, figure elements. (This seemed to be a solution favored by Roan.)
+
+Probably the best solution is a combination of both. I would be happy to help with solution 2, although it would be nice to get some guidance from the VE team on what approach (or approaches) they would prefer to see (and possibly help implement).",1392061761,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Let skin variance for styling of <figures> in page content,"What's the solution to this issue, though? Re-write MW's skins to work with nodes? 'Cos right now they don't…
+
+""Fix MW's skin system"" is a bit of a large tangential bug.",1392060050,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lmv6en7m2i2nthp4bbad,task_subcomment,NA
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text for example: ""link with wikitext""
+3.Press command+k to apply link on it
+4.Without adding anything just close the inspector.
+5.Save the page.
+6.Reopen the page in VE
+
+Observed Result:
+The wikitext for the link is appearing in Read mode and in VE
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13098}",1390511280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3dkpw6uttju4ehjxawfk,task_description,resolved
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,Verified the fix on test2 and mw.org,1391123930,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3dkpw6uttju4ehjxawfk,task_subcomment,NA
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,Verified the fix on Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Jan_27th?veaction=edit,1390862978,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3dkpw6uttju4ehjxawfk,task_subcomment,NA
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,"Change 109738 merged by jenkins-bot:
+Followup 7994eae8c2: fix MWLinkInspector breakage
+
+https://gerrit.wikimedia.org/r/109738",1390857396,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3dkpw6uttju4ehjxawfk,task_subcomment,NA
+VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs,"Change 109738 had a related patch set uploaded by Catrope:
+Followup 7994eae8c2: fix MWLinkInspector breakage
+
+https://gerrit.wikimedia.org/r/109738",1390857192,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3dkpw6uttju4ehjxawfk,task_subcomment,NA
+VisualEditor:  Adding a template and removing a non-breaking space (nbsp) causes span tags with data-ve-ignore,"Intention:
+Add a template and remove a non-breaking space (&nbsp;) in the same line/paragraph
+
+Steps to Reproduce:
+(Order matters!)
+
+1.  Begin with a page that contains the HTML code for a non-breaking space.  Open in VisualEditor.
+
+2.  On the line that contains the nbsp, add a template (e.g., {{fact}}).  The template should be added to the same 'word' that contains the nbsp.
+
+3.  Then remove the nbsp (replace with a plain space, or just delete the whole 'word').
+
+Actual Results:  
+VisualEditor added span text like <span about=""g0.42287685585435686"" data-ve-ignore=""true""></span> when the nbsp was removed.
+
+Adding a fact template to the end of:
+
+1&nbsp;mg 2&nbsp;mg 3&nbsp;mg 4&nbsp;mg
+
+turns into:
+
+1&nbsp;mg 2&nbsp;mg 3&nbsp;mg 4 mg{{Fact}}<span data-ve-ignore=""true"" about=""g0.5170239245053381""></span>
+
+However, adding the template to ""3 mg"" and deleting the nbsp from ""2 mg"" works correctly:
+
+1&nbsp;mg 2 mg 3&nbsp;mg{{Fact}} 4&nbsp;mg
+
+
+
+
+Reproducible: Always
+
+See https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=591972176&oldid=591955710 and testing at https://en.wikipedia.org/w/index.php?title=User:Jay8g/sandbox&action=history on 23 January 2014 for many more details.
+
+Found in Firefox 26 on Windows 7 with Monobook, confirmed in Safari 6 on Mac OS 10.8.5 with Vector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60897",1390506600,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-h52lnxgvppaohab4kg6x,task_description,resolved
+VisualEditor:  Adding a template and removing a non-breaking space (nbsp) causes span tags with data-ve-ignore,"From following WhatAmIDoing's instructions, I can replicate in enwiki and it's fixed in Beta Labs; marking as FIXED.",1391668943,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-h52lnxgvppaohab4kg6x,task_subcomment,NA
+VisualEditor:  Adding a template and removing a non-breaking space (nbsp) causes span tags with data-ve-ignore,"Probably a duplicate of bug 60897
+
+See if the fix there resolves this.",1391633551,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-h52lnxgvppaohab4kg6x,task_subcomment,NA
+VisualEditor:  Adding a template and removing a non-breaking space (nbsp) causes span tags with data-ve-ignore,"This also appears if you add any template after a {{convert}} template, and then remove the {{convert}} template.
+
+If there are multiple nbsp's on the same line, them it is only the removal of the nbsp that is immediately before the template that appears to trigger it.",1390581096,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-h52lnxgvppaohab4kg6x,task_subcomment,NA
+"VisualEditor:  ""Edit"" tab not appearing sometimes","Reproducible: Didn't try
+
+Two editors report that VisualEditor's ""Edit beta"" tab occcasionally does not appear on their screens.  Both were using Firefox on Windows 7.  The button reappeared upon refreshing the screen, or spontaneously reappeared the next day.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1390436160,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-xe24oejtt6ji24d5t62v,task_description,resolved
+"VisualEditor:  ""Edit"" tab not appearing sometimes","I'm presuming that this is a duplicate of bug 54706.
+
+*** This bug has been marked as a duplicate of bug 54706 ***",1397067449,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xe24oejtt6ji24d5t62v,task_subcomment,NA
+"VisualEditor:  ""Edit"" tab not appearing sometimes",It happened to one of them again.,1391037771,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-xe24oejtt6ji24d5t62v,task_subcomment,NA
+"VisualEditor:  ""Edit"" tab not appearing sometimes","Possibly a JS transmission error; without detailed information we'll never have any idea what caused it, but let's keep this open in case there are further reports.",1390442979,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xe24oejtt6ji24d5t62v,task_subcomment,NA
+importImages.php broken on cluster,"reedy@tin:/tmp/uploads$ sudo -u apache mwscript importImages.php --wiki=commonswiki --user=""Jdforrester_(WMF)"" /tmp/uploads
+Import Images
+
+Importing linux.conf.au 2014 - VisualEditor presentation.ogv...PHP Warning:  fopen(/tmp/uploads/linux.conf.au 2014 - VisualEditor presentation.ogv): failed to open stream: Permission denied in /a/common/php-1.23wmf10/includes/filebackend/SwiftFileBackend.php on line 278
+
+Warning: fopen(/tmp/uploads/linux.conf.au 2014 - VisualEditor presentation.ogv): failed to open stream: Permission denied in /a/common/php-1.23wmf10/includes/filebackend/SwiftFileBackend.php on line 278
+done.
+
+Found: 1
+Added: 1
+reedy@tin:/tmp/uploads$
+
+
+The added is a lie. The upload didn't complete, it's a 404
+
+https://upload.wikimedia.org/wikipedia/commons/e/ea/Linux.conf.au_2014_-_VisualEditor_presentation.ogv
+
+404 Not Found
+
+The resource could not be found.
+
+File not found: /v1/AUTH_mw/wikipedia-commons-local-public.ea/e/ea/Linux.conf.au_2014_-_VisualEditor_presentation.ogv
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60777",1390354860,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_description,resolved
+importImages.php broken on cluster,"Change 111116 merged by Aaron Schulz:
+Fixes and cleanups to FileOpBatch
+
+https://gerrit.wikimedia.org/r/111116",1391470291,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111115 merged by jenkins-bot:
+Use ""rb"" instead of ""rb+"" for Swift store operation handles
+
+https://gerrit.wikimedia.org/r/111115",1391469961,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 110993 merged by jenkins-bot:
+Use ""rb"" instead of ""rb+"" for Swift store operation handles
+
+https://gerrit.wikimedia.org/r/110993",1391469906,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111116 had a related patch set uploaded by Aaron Schulz:
+Fixes and cleanups to FileOpBatch
+
+https://gerrit.wikimedia.org/r/111116",1391469439,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111115 had a related patch set uploaded by Aaron Schulz:
+Use ""rb"" instead of ""rb+"" for Swift store operation handles
+
+https://gerrit.wikimedia.org/r/111115",1391469425,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111111 merged by jenkins-bot:
+Fixes and cleanups to FileOpBatch
+
+https://gerrit.wikimedia.org/r/111111",1391469371,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 111111 had a related patch set uploaded by Aaron Schulz:
+Fixes and cleanups to FileOpBatch
+
+https://gerrit.wikimedia.org/r/111111",1391468881,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"Change 110993 had a related patch set uploaded by Aaron Schulz:
+Use ""rb"" instead of ""rb+"" for Swift store operation handles
+
+https://gerrit.wikimedia.org/r/110993",1391459513,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"(In reply to comment #2)
+> I don't see any way around getting errors when trying to upload files as a
+> user
+> that can't see them. What exactly is this about?
+
+The behaviour changed at some point (I didn't have to change file permissions before). But even with read for everyone on /tmp/uploads, it doesn't work with errors.
+
+There is a related error that the uploads apparently succeed, even though they weren't imported.
+
+
+reedy@tin:/tmp/uploads$ sudo -u apache mwscript importImages.php --wiki=commonswiki --user=""Odder"" /tmp/uploads
+Import Images
+
+Importing 2014 State Of The Union Address Enhanced.webm...PHP Warning:  fopen(/tmp/uploads/2014 State Of The Union Address Enhanced.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+
+Warning: fopen(/tmp/uploads/2014 State Of The Union Address Enhanced.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+done.
+Importing 2013-10-05 President Obama's Weekly Address.webm...PHP Warning:  fopen(/tmp/uploads/2013-10-05 President Obama's Weekly Address.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+
+Warning: fopen(/tmp/uploads/2013-10-05 President Obama's Weekly Address.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+done.
+Importing 2013-10-12 President Obama's Weekly Address.webm...PHP Warning:  fopen(/tmp/uploads/2013-10-12 President Obama's Weekly Address.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+
+Warning: fopen(/tmp/uploads/2013-10-12 President Obama's Weekly Address.webm): failed to open stream: Permission denied in /a/common/php-1.23wmf11/includes/filebackend/SwiftFileBackend.php on line 278
+done.
+
+Found: 3
+Added: 3
+reedy@tin:/tmp/uploads$ ls -al
+total 2404792
+drwxrwxrwx  2 reedy wikidev      4096 Feb  3 18:47 .
+drwxrwxrwt 46 root  root        12288 Feb  3 18:46 ..
+-rw-rw-r--  1 reedy wikidev      1255 Feb  1 14:50 2013-10-05 President Obama's Weekly Address.txt
+-rw-rw-r--  1 reedy wikidev 163504321 Jan 27 22:13 2013-10-05 President Obama's Weekly Address.webm
+-rw-rw-r--  1 reedy wikidev      1197 Feb  1 14:52 2013-10-12 President Obama's Weekly Address.txt
+-rw-rw-r--  1 reedy wikidev 158637780 Feb  1 14:34 2013-10-12 President Obama's Weekly Address.webm
+-rw-rw-r--  1 reedy wikidev       884 Jan 31 16:26 2014 State Of The Union Address Enhanced.txt
+-rw-rw-r--  1 reedy wikidev 909068945 Jan 30 19:37 2014 State Of The Union Address Enhanced.webm
+-rw-r--r--  1 reedy wikidev 909060459 Feb  3 18:45 SOTU.tar.gz
+-rw-r--r--  1 reedy wikidev 322185685 Feb  3 18:46 WeeklyAddresses.tar.gz
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$
+reedy@tin:/tmp/uploads$ chmod 777 *
+reedy@tin:/tmp/uploads$ rm *.gz
+reedy@tin:/tmp/uploads$ ls -al
+total 1202392
+drwxrwxrwx  2 reedy wikidev      4096 Feb  3 18:52 .
+drwxrwxrwt 46 root  root        12288 Feb  3 18:50 ..
+-rwxrwxrwx  1 reedy wikidev      1255 Feb  1 14:50 2013-10-05 President Obama's Weekly Address.txt
+-rwxrwxrwx  1 reedy wikidev 163504321 Jan 27 22:13 2013-10-05 President Obama's Weekly Address.webm
+-rwxrwxrwx  1 reedy wikidev      1197 Feb  1 14:52 2013-10-12 President Obama's Weekly Address.txt
+-rwxrwxrwx  1 reedy wikidev 158637780 Feb  1 14:34 2013-10-12 President Obama's Weekly Address.webm
+-rwxrwxrwx  1 reedy wikidev       884 Jan 31 16:26 2014 State Of The Union Address Enhanced.txt
+-rwxrwxrwx  1 reedy wikidev 909068945 Jan 30 19:37 2014 State Of The Union Address Enhanced.webm
+reedy@tin:/tmp/uploads$ sudo -u apache mwscript importImages.php --wiki=commonswiki --user=""Odder"" /tmp/uploads
+Import Images
+
+Importing 2014 State Of The Union Address Enhanced.webm...done.
+Importing 2013-10-05 President Obama's Weekly Address.webm...done.
+Importing 2013-10-12 President Obama's Weekly Address.webm...done.
+
+Found: 3
+Added: 3
+reedy@tin:/tmp/uploads$",1391453683,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,I don't see any way around getting errors when trying to upload files as a user that can't see them. What exactly is this about?,1391211450,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+importImages.php broken on cluster,"If I chmod 777 it, I can upload it :/",1390364266,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-i7csvcnyrxx5gr5lwuwd,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**Author:** `llamaal_wikis`
+
+**Description:**
+Intention:
+After the conclusion of https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual on the Spanish Wikipedia, some changes to the status of VE in that project have to be implemented:
+
+1. VE should now be opt-in
+2. The ""edit"" tab should return to wikitext
+3. VE should be presented as part of Beta Features
+4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+
+Regards,
+
+LlamaAl
+
+
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1390009440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_description,resolved
+Changes to VisualEditor on eswiki as result of vote,This is now done.,1392253962,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**albertojuansebastian** wrote:
+
+Thank you very much, James. If you have any doubt, ask us here or there: https://es.wikipedia.org/wiki/Wikipedia:Caf%C3%A9/Archivo/Noticias/Actual#Acuse_de_recibo. 
+
+Regards.
+_________________________________________________________________________
+And thanks, Nemo. Maybe I could convince some of my 'tech collegues' on esWikipedia to take part in the discussion there.
+
+Greetings.
+_________________________________________________________________________
+Thank you all. Albertojuanse.",1392078540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"(In reply to comment #11)
+> Finally, even if they had nothing to do with the VisualEditor, several users
+> have meant to note that more economics and human resources should be focuses
+> on
+> fixing existing problems such us the FastButtons —it was disabled weeks ago
+> because a security breach—, the cellular phone and portable devices editing
+> softwares, etc.
+
+Indeed beyond the scope of a bug: I've copied this to https://www.mediawiki.org/?diff=902629&oldid=892609 . It would be useful if those users (or other users who understand Spanish and read their comments) could elaborate/continue the discussion there, I think.",1392070089,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Understood. Thank you for the responses. I have adjusted the configuration change to correct for these issues as much as we can.
+
+I will now ask my colleagues to find a time that we can make these changes.",1392069338,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**albertojuansebastian** wrote:
+
+(In reply to comment #8)
+
+Finally, I am able to aswer the questions. Thank you for the waiting. 
+
+The talk about the answers is here (in Spanish): https://es.wikipedia.org/w/index.php?title=Wikipedia:Caf%C3%A9/Archivo/Noticias/Actual&oldid=72405348#Preguntas 
+
+The aswers can be also be read here (in English): https://es.wikipedia.org/w/index.php?title=Wikipedia:Caf%C3%A9/Archivo/Noticias/Actual&oldid=72405348#Respuestas
+
+Greetings.
+_____________________________________________________________________________
+> 1. When you say ""VE should now be opt-in"", what should happen to the accounts
+> that have been using VE? Should they be opted-in, or just left stranded
+> without
+> VisualEditor? Should the default for new accounts be to have to find
+> VisualEditor to switch it on?
+
+As a consequence of the votation, the ""opt-in"" must be disabled; and thus it will be enabled by those who want to use it. The proper announcements will be made in order that noone overlook this change.
+
+And, that is correct, the new users will have to get informed —or they will be informed if they ask for help— about the different tools available in esWikipedia, which are not less useful and important that this one: our spelling checker, the PopUps or FastButtons, etc.
+_________________________________________________________________________
+> 2. You want the labels to be ""Edit"" for wikitext and ""Editor Visual"" for
+> VisualEditor? Which way around should they go? (Right now eswiki has VE as
+> the
+> primary/first tab, but we could change it to secondary/second tab if you
+> think
+> it would be a good change. However, that would be a bit odd to do as well as
+
+Fully right, if the user enables the VE, the label ""Edit"" —""Editar""— should be the wikitext's one and the ""Editor Visual"" should be the VisualEditor one. Regarding to the labeling way once the VE is activated, the community was not asked about that in the votation; although most of the users have pronounced in favour of using the second label for ""Editor Visual"" —""Visual Editor""—. However, proceed as you see best.
+_________________________________________________________________________
+> 3. Also on the labels of the tabs, in general, we're not happy with the
+> ""beta""
+> superscript note and we were planning to get rid of it in the next few
+> weeks. I
+> don't think it makes sense for an opt-in system with two warnings about the
+> software being beta to have a third, and it doesn't work very well in Firefox
+> and some other platforms due to browser bugs.
+
+In esWikipedia, the ""beta"" superscript has never been implemented, so we ignored its flaws. Besides, when the votation was proposed there were any warning about the software being beta, so it is logical that the community would desired to implement the ""beta"" warning. Be that as it may, our desires are limited by the technical viability of those, although this ""beta"" labeling it is still desired.
+_________________________________________________________________________
+> 4. What is the plan to inform users who have been using VisualEditor as to
+> the
+> disruption? Particularly, what is the plan for anonymous editors (who can't
+> opt-in)? About 20% of edits by anonymous users have been through VisualEditor
+> to date, and this is likely to confuse them.
+
+Will be developed the same action plan that was developed when the VisualEditor was implemented, id est, it will be announce in our ""Café de noticias"" —Village pump (news)— and the guide ""Wikipedia:VisualEditor"". Besides, we all will beware in order to solve the doubts from users and help them in this issue.
+_________________________________________________________________________
+> 5. What is the plan for returning to use VisualEditor as the primary editor?
+> What changes or fixes would you like to see?
+
+When the tool have been fully finished, and the developers let us know this situation, the entire community will be asked again about this issue. At the time, if there is consensus about its implementation, it will be enabled; if not, there will be another votation about the VisualEditor. Please also note that in a votation, the ""enable"" option must reach 2/3 of the votes to be enabled.
+
+Regarding to the second question, several users are already working with the VisualEditor and they are reporting their feedback to the developers; so when it will be reported that the software has not structural flaws and that the use experience is acceptable, we will let you know. Also, there has been an interest in solving all the incompatibilities with other ""mod"" and ""opt-in"" softwares, although it is known that some of them are already fixed.
+
+Finally, even if they had nothing to do with the VisualEditor, several users have meant to note that more economics and human resources should be focuses on fixing existing problems such us the FastButtons —it was disabled weeks ago because a security breach—, the cellular phone and portable devices editing softwares, etc.
+_________________________________________________________________________",1391824184,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**albertojuansebastian** wrote:
+
+(In reply to comment #9)
+
+Indeed. We are already discussing the answers in our Café (Village pump). In fact, in a few days (2 or 3)  we will be able to give you the answers, since it seems that we are reaching consensus. Greetings.",1391521353,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Shouldn't these ""big questions"" be brought up with the entire eswiki community, rather than on Bugzilla where only the single community member who filed the bug will see?",1391514324,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Some questions and points (sorry for being slow; I've been on leave, returning next week):
+
+1. When you say ""VE should now be opt-in"", what should happen to the accounts that have been using VE? Should they be opted-in, or just left stranded without VisualEditor? Should the default for new accounts be to have to find VisualEditor to switch it on?
+
+2. You want the labels to be ""Edit"" for wikitext and ""Editor Visual"" for VisualEditor? Which way around should they go? (Right now eswiki has VE as the primary/first tab, but we could change it to secondary/second tab if you think it would be a good change. However, that would be a bit odd to do as well as the opt-in, and is more an alternative.
+
+3. Also on the labels of the tabs, in general, we're not happy with the ""beta"" superscript note and we were planning to get rid of it in the next few weeks. I don't think it makes sense for an opt-in system with two warnings about the software being beta to have a third, and it doesn't work very well in Firefox and some other platforms due to browser bugs.
+
+4. What is the plan to inform users who have been using VisualEditor as to the disruption? Particularly, what is the plan for anonymous editors (who can't opt-in)? About 20% of edits by anonymous users have been through VisualEditor to date, and this is likely to confuse them.
+
+5. What is the plan for returning to use VisualEditor as the primary editor? What changes or fixes would you like to see?",1391213693,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Change 109639 had a related patch set uploaded by TTO:
+Move VisualEditor to secondary status on eswiki
+
+https://gerrit.wikimedia.org/r/109639",1390817856,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"Just to explain:
+
+This request is easy, except for the desire to have the VisualEditor tab labelled ""Editor Visual <sup>BETA</sup>"". It is not currently possible to label the VisualEditor tab differently from the regular ""Edit"" tab (other than the appending of a BETA suffix), this would appear to require an alteration to the VisualEditor software itself.
+
+The remaining three points of the request can be fulfilled easily, I think.",1390706953,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**llamaal_wikis** wrote:
+
+I want to clarify something: the ""BETA"" part in the name of the Visual Editor tab should appear in small and superscript text, as shown in this diff [1].
+
+[1] https://es.wikipedia.org/w/index.php?title=Wikipedia%3AZona_de_pruebas%2F5&diff=72006555&oldid=71969129",1390172986,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**llamaal_wikis** wrote:
+
+(In reply to comment #3)
+> (In reply to comment #1)
+> > 4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+> Note that this is different from the enwiki config (the rest of the request
+> is
+> the same). On enwiki:
+> * users who have VE disabled only see one tab, labeled ""Edit"", that points to
+> the source editor
+> * for users who have VE enabled, this tab is labeled ""Edit source"" instead
+> * additionally, they have a VE tab labeled ""EditBETA""
+> * the VE tab appears after (to the right of) the source editor tab
+> 
+> For eswiki, #4 in the request asks us to implement the third bullet point
+> differently, by labeling the VE tab ""Editor VisualBETA"" rather than
+> ""EditarBETA"".
+> 
+> So what should happen to the source editor tab for users who have VE enabled?
+> Should it be labeled ""Editar código"" (as it is now, and would be with an
+> enwiki-like configuration), or as ""Editar"", or ... ? Should it appear before
+> or
+> after the source editor tab (right now it's before, with an enwiki-like
+> configuration it would be after).
+
+In the case a user enables VE, the source editor tab should remain as ""Editar"", and a new tab labeled ""Editor VisualBETA"" should appear after it.",1390011606,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"(In reply to comment #1)
+> 4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+Note that this is different from the enwiki config (the rest of the request is the same). On enwiki:
+* users who have VE disabled only see one tab, labeled ""Edit"", that points to the source editor
+* for users who have VE enabled, this tab is labeled ""Edit source"" instead
+* additionally, they have a VE tab labeled ""EditBETA""
+* the VE tab appears after (to the right of) the source editor tab
+
+For eswiki, #4 in the request asks us to implement the third bullet point differently, by labeling the VE tab ""Editor VisualBETA"" rather than ""EditarBETA"".
+
+So what should happen to the source editor tab for users who have VE enabled? Should it be labeled ""Editar código"" (as it is now, and would be with an enwiki-like configuration), or as ""Editar"", or ... ? Should it appear before or after the source editor tab (right now it's before, with an enwiki-like configuration it would be after).",1390011071,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,*** Bug 60189 has been marked as a duplicate of this bug. ***,1390011045,PHID-USER-3qsavo6roa5h32xcsgng,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+Changes to VisualEditor on eswiki as result of vote,"**llamaal_wikis** wrote:
+
+After the conclusion of
+https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual
+on the Spanish Wikipedia, some changes to the status of VE in that project have
+to be implemented:
+
+1. VE should now be opt-in
+2. The ""edit"" tab should return to wikitext
+3. VE should be presented as part of Beta Features
+4. The tab for VE, if users activate it, should be ""Editor VisualBETA""
+
+Regards,",1390009593,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xwtmpv2x7s3ve2444eyi,task_subcomment,NA
+VisualEditor: Standalone demo toolbar breaks sometimes in Chrome,"Screenshot of the bug
+
+See attached screenshot.
+
+This is because the standalone demo initializes the target into a detached DOM element, then attaches it once it's done. But you can't do that, because it causes ve.ui.Toolbar.prototype.initialize to be run before the toolbar is attached to the DOM (and generally causes initialize to be run on unattached things, which is not allowed), which means its measurements will be wrong, and so the toolbar gets right: 1840px; (width of screen) rather than width: 63px; or whatever.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13274}",1389997140,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qs4hjzccsgzpxttdtdrd,task_description,resolved
+VisualEditor: Standalone demo toolbar breaks sometimes in Chrome,"
+
+*** This bug has been marked as a duplicate of bug 59720 ***",1390864797,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qs4hjzccsgzpxttdtdrd,task_subcomment,NA
+VisualEditor messages not updated for 1.23wmf11,"Broken inspector
+
+Steps to reproduce:
+
+1.Open the VisualEditor
+2.Go to Insert menu and Settings menu
+
+Observed Result:
+<visualeditor-mwgalleryinspector-title> and <visualeditor-dialog-commands>  is appearing in the Insert menu and Settings menu respectively.
+Also selecting <visualeditor-mwgalleryinspector-title> opens up a broken gallery inspector.
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/,wmf11
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13165}",1389904560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gfsol6rwzvgp2bqtxhxa,task_description,resolved
+VisualEditor messages not updated for 1.23wmf11,Verified the fix in test2 using Chrome and FF,1389985847,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gfsol6rwzvgp2bqtxhxa,task_subcomment,NA
+VisualEditor messages not updated for 1.23wmf11,Now fixed.,1389985486,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gfsol6rwzvgp2bqtxhxa,task_subcomment,NA
+"VisualEditor: Switching insertion types for inspectable notes (e.g. hiero, formula, gallery) mid-creation breaks entertainingly","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a math function from Insert>Formula for example \pi
+3.While the added math formula is still selected go to Insert>Hiero
+4.Observe that the math function previously added is now appearing in hiero inspector.
+5.Close the inspector for hiero
+6.Save the page
+
+Observed Result:
+A hiero tag got added  in the wikitext as  <hiero>\pi</hiero>
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=Wmf11&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13157}",1389903480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-43nrc2oe3kjbjeoi5weu,task_description,resolved
+"VisualEditor: Switching insertion types for inspectable notes (e.g. hiero, formula, gallery) mid-creation breaks entertainingly",Can not reproduce from my end as well.Closing the bug.,1391728232,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-43nrc2oe3kjbjeoi5weu,task_subcomment,NA
+"VisualEditor: Switching insertion types for inspectable notes (e.g. hiero, formula, gallery) mid-creation breaks entertainingly","Can't reproduce, might have been fixed by https://gerrit.wikimedia.org/r/#/c/111178/ ? Please test again.",1391717104,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-43nrc2oe3kjbjeoi5weu,task_subcomment,NA
+"VisualEditor: Switching insertion types for inspectable notes (e.g. hiero, formula, gallery) mid-creation breaks entertainingly","When you ""switch"" inspectors the content of the first inspector is inserted, but a new inspector isn't created (so the content of the first is also available for the new one).",1390021684,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-43nrc2oe3kjbjeoi5weu,task_subcomment,NA
+"VisualEditor: Selection highlighting breaks on changing selection format (cursor moves to wrong place, selection is unhighlighted but still selected)","Selecting a line of text and turning it into a header (ctrl+1) removes the selection highlighting but keeps the text selected. Additionally turning text into a header also moves the position marker to the wrong place (visually).
+
+As a result e.g. the action of creating a header then pressing enter replaces the header by an empty line.
+
+Se screencast below for procedure and illustration.
+https://www.youtube.com/watch?v=7OtpP5iS2uw
+
+Reproducible in Chrome and Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1389892740,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-j7arlw5peomdv3rolltm,task_description,resolved
+"VisualEditor: Selection highlighting breaks on changing selection format (cursor moves to wrong place, selection is unhighlighted but still selected)","
+
+*** This bug has been marked as a duplicate of bug 57552 ***",1394659271,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-j7arlw5peomdv3rolltm,task_subcomment,NA
+"VisualEditor: Loading the San Francisco article on mobile causes massive breakage, unusable editor","Oh nos!
+
+When trying to edit San Francisco with VE in mobile alpha mode all hell breaks lose.
+
+See for yourself at this URL:
+https://en.m.wikipedia.org/wiki/San_Francisco?mobileaction=alpha#editor/0
+
+and see screen for the sort of things that happen.
+
+I can't focus the textarea or make any changes. This makes me sad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13080}",1389833400,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-hjchikg52kgk75rl7yaa,task_description,resolved
+"VisualEditor: Loading the San Francisco article on mobile causes massive breakage, unusable editor",This appears to have been fixed by the changes that Juliusz and Jon made last month.,1394494444,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hjchikg52kgk75rl7yaa,task_subcomment,NA
+VisualEditor:  [Regression] External rich pasting in Firefox inserting newlines again,"https://jv.wikipedia.org/w/index.php?title=Kraton_Ngayogyakarta_Hadiningrat&curid=87083&diff=879162&oldid=845799
+
+This begins with a =Level 1 heading= (perhaps the article title was copied?).  Some paragraphs are broken onto separate lines. The [[links]] are improperly converted to [[http://jv.wikipedia.org/wiki/Links]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389725880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rafcafjslpgvnetrixxn,task_description,resolved
+VisualEditor:  [Regression] External rich pasting in Firefox inserting newlines again,"Whenever we fixed this, it's certainly not a problem now.",1421282899,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rafcafjslpgvnetrixxn,task_subcomment,NA
+VisualEditor:  [Regression] External rich pasting in Firefox inserting newlines again,"The H1 is just external copy of the read HTML (and isn't a bug, just bad user behaviour).
+
+The links getting badly converted are bug 58136.
+
+However, the paragraphs getting split is a new regression in Firefox pasting behaviour. :-(",1390022523,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rafcafjslpgvnetrixxn,task_subcomment,NA
+VisualEditor:TypeError: currentDom[i].setAttribute is not a function appears while adding content from Template dialogbox,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Transclusion 
+3.Add some content and click on ""Apply changes""
+4.Click on ""Save Page""
+
+Observed Result:
+
+The ""Save Page"" button does not worl.In the console the following error appears:
+TypeError: currentDom[i].setAttribute is not a function
+
+See the screenshot attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Jan_13th?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12850}",1389651180,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4hrlw6tweytjl62h36,task_description,resolved
+VisualEditor:TypeError: currentDom[i].setAttribute is not a function appears while adding content from Template dialogbox,Verified the fix  in test2,1390336093,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4hrlw6tweytjl62h36,task_subcomment,NA
+VisualEditor:TypeError: currentDom[i].setAttribute is not a function appears while adding content from Template dialogbox,This should have been fixed by https://gerrit.wikimedia.org/r/#/c/107511/,1390317183,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yw4hrlw6tweytjl62h36,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which has some content
+2.Add any image from Insert>Media after going to a newline.
+3.Save the page
+4.Reopen the page
+5.Place the cursor in a new line and hit return
+
+Observed Result:
+Newline cannot be added , in the console an error appears:
+TypeError: outermostNode is null
+	
+
+...documentModel,selection.from,'\n');}else{node.traverseUpstream(function(node){if...
+
+load.p...1826Z&* (line 261)
+
+Test Environment: mw.org
+Browser: FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox_345&oldid=885285?veaction=edit
+
+**Attached**: {F12613}",1389374820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_description,resolved
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754958,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,Verified the fix in test2.,1394232814,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,Verified the fix in betalabs,1393634363,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,"Change 109693 merged by jenkins-bot:
+Fix handleEnter in nodes that don't split
+
+https://gerrit.wikimedia.org/r/109693",1393612229,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,*** Bug 62015 has been marked as a duplicate of this bug. ***,1393530490,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,*** Bug 61525 has been marked as a duplicate of this bug. ***,1393474403,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,*** Bug 61932 has been marked as a duplicate of this bug. ***,1393474369,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,"Change 109693 had a related patch set uploaded by Divec:
+WIP:Fix handleEnter when not in a splittable node
+
+https://gerrit.wikimedia.org/r/109693",1390845592,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item,"Seems to be failing to handle enter when in a block slug for some reason… but only on the page re-load.
+
+Line 1675 of ve.ce.Surface.js (in handleEnter) is throwing ""TypeError: Cannot call method 'getModel' of null"" because  ""outermostNode"" is null.
+
+ncaught TypeError: Cannot call method 'getModel' of null ve.ce.Surface.js:1675",1389906213,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6ghlb6bfzg6jhbosmoq2,task_subcomment,NA
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken","Steps to reproduce:
+
+- go to page (for example [1]) that has only this as contents: {{done}}
+- edit the page with visual editor
+- copy/paste the template
+- I was expecting the page now to contain only this text: {{done}}{{done}}
+- instead, the page text is: {{done}}{{done}}<span data-ve-ignore=""true""> </span>'''Done.'''
+- that causes ""Done."" to be displayed three times (instead of two), see screenshot[2]
+- two minute video recording reproducing the bug is available at [3]
+- Sauce Labs is pretty slow to respond, so the actions looks really really slow, the best way to view the video is to download it from [4] and play it with VLC on maximum speed (4x)
+
+1: https://test2.wikipedia.org/wiki/Done
+2: https://saucelabs.com/jobs/9dd0291def28413bb7f9ca3a9fd7e891/0001screenshot.png
+3: https://saucelabs.com/tests/9dd0291def28413bb7f9ca3a9fd7e891
+4: https://saucelabs.com/jobs/9dd0291def28413bb7f9ca3a9fd7e891/video_9dd0291def28413bb7f9ca3a9fd7e891.flv
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1389356460,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-mipnpagv42ujw7okwcjf,task_description,resolved
+"VisualEditor: Pasting copied template cause it to be inserted twice, once broken","
+
+*** This bug has been marked as a duplicate of bug 59653 ***",1389904122,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mipnpagv42ujw7okwcjf,task_subcomment,NA
+VisualEditor: Document selection should be nullable,"Despite the fact that you can have the appearance of the document being blurred and having no active selections, we will always keep the last valid range as the current selection. This is a case of the model not matching the view.
+
+The other solution (as used by Google Docs) is to always render a selection even when the document is unfocused, but as we are using native selections this may not be possible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62410",1389282420,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-23mm54valrpkfsjce3lj,task_description,resolved
+VisualEditor: Document selection should be nullable,"Change 124359 merged by jenkins-bot:
+Detect document focus properly and allow null selection in model
+
+https://gerrit.wikimedia.org/r/124359",1397261984,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,"Change 124359 had a related patch set uploaded by Esanders:
+Detect document focus properly and allow null selection in model
+
+https://gerrit.wikimedia.org/r/124359",1396892619,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,Was reverted in https://gerrit.wikimedia.org/r/123464,1396477637,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,"Change 121534 merged by jenkins-bot:
+Detect document focus properly and allow null selection in model
+
+https://gerrit.wikimedia.org/r/121534",1396394668,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,"Change 121534 had a related patch set uploaded by Esanders:
+Detect document focus properly and allow null selection in model
+
+https://gerrit.wikimedia.org/r/121534",1395956704,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+VisualEditor: Document selection should be nullable,What's the status of this? Did your work on cursor selections last week relate?,1394494239,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-23mm54valrpkfsjce3lj,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","Intention:
+Test a bug.
+
+Steps to Reproduce:
+1. Selecting the appendices on the page https://en.wikipedia.org/w/index.php?oldid=588539903&veaction=edit
+
+2. Cut them out (Control-x), and 
+
+3. Paste them right back where they were.  
+
+
+Actual Results:  
+The indentation level for all the bulleted lists was increased.
+
+
+Reproducible: Didn't try
+
+**URL**: https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FS%26D&diff=588777573&oldid=588539903",1389228060,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uctbq2qfw5ogzgknys3a,task_description,resolved
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome",I've tested this out and it seems to work correctly now. Feel free to reopen if I've missed something.,1437603288,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","I'm convinced that most editors don't know this.  I only learned this a couple of years ago, when talking to someone with WikiProject Accessibility.
+
+https://en.wikipedia.org/wiki/Template:Glossary is only used 101 times, which is almost nothing for the English Wikipedia.  I don't believe that I've ever seen a list using it.  The normal way to make a definition list is:
+
+;Term
+:Definition
+
+or, alternatively:
+
+;Term: Definition
+
+See [[Disease]] for one of several examples I could name off the top of my head.  Both formats produce the same end result.
+
+VisualEditor does not support definition lists at all at this time.  Support is planned (see bug 37938), but it may be a while.  Whenever that happens, this problem should (hopefully) be resolved.",1412488651,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","> TLDR:  The colon does *not* actually mean ""indent"".
+
+Ok, the colon does not mean indent.  However, I have had an account on English Wikipedia for seven years, have made 50,000 edits in that time (which must include tens of thousands of colons) but this is the first I have heard of it.  We have a page (WP:INDENT) explaining how to use colons for indenting, MOS:MATH requires it for display formulae, and WP:TALK suggests that it may be disruptive to deliberately not use colons.  On none of those pages is it explained that, actually, colon does not really mean indent.
+
+I am almost certain that the vast majority of editors do not know this.  There are probably hundreds of thousands of articles that use colons.  It is simply not going to be acceptable for VE to chew up articles because it does not ""like"" the markup used by editors and established for many years.  A less disruptive way forward would be to make the colon actually mean indent.  Definition lists are usually achieved with templates.  The few that are not are going to be a much smaller number of pages that need fixing and can easily be found by extracting a list of pages from the database with semicolons in lines beginning with colons.  A semi-automated bot could then go through them.",1412442963,PHID-USER-imut7wxehhy35ukuzaks,True,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","I don't understand why editors aren't allowed free use of indenting, either.  But ""free use of indenting"" is bug 4521 from eight years ago.  ""Free use of indenting"" is not ""using the second half of the markup from a definition list to sort of fake indenting, so that it looks okay on my desktop system but also so that reading the page is irritating to people using screen readers"".
+
+The colon is part of semantic markup.  Screen readers don't skip over semantic markup.  They don't just read the contents of a list.  They stop reading content and announce that there is a list, and how long the list is.  If you use a colon, then some screen readers (correctly) interpret this as being marked as a long list of definitions, so that your markup:
+
+:where,
+: ''D'' = 1/''C'' is elastance
+: ''C'' is capacitance
+: ''S'' is stiffness
+
+is read as something like ""Term with four definitions:  where, d = 1/C is elastance, c is capacitance, s is stiffness"".  Unless you really want the words ""Term with four definitions"" to be stuck in the middle of that sentence, then you should not define those four lines as being in a definition list (aka association list).
+
+If you just want visual-only indentation, then you have to set span or div tags to provide visual-only changes to the text arrangement.  As I said above, I don't know why MediaWiki doesn't have a much simpler method for letting editors provide visual intendations properly, and instead gives them a choice between screwing up accessibility or having to hand-type complicated HTML codes.  Using indentation freely been requested for at least eight years.  We have a legitimate need for this, but I don't know if we'll ever get it.
+
+
+TLDR:  The colon does *not* actually mean ""indent"".",1412359030,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","(In reply to WhatamIdoing from comment #2)
+
+> However, what's being used there as ""indentation"" isn't indentation,
+> strictly speaking; that text has been marked as the second half of a
+> term-definition pair in a definition list, which is not semantically
+> meaningful.  
+
+It wasn't so marked by me and I don't see any markup in the edit window so you would appear to mean that VE has generated markup.  Generating semantically incorrect markup and then blaming the user for the error is plainly ridiculous.  Or perhaps you mean that the colon in wiki markup does not really mean indentation?  Well, yes it does, it is used extensively all over Wikipedia (ahem, talk pages) with just that intention so by practice and precedent that is what it means.  VE needs to live with that, not garble it because it doesn't like the semantics, otherwise VE will never be ready for prime time.
+
+> where,
+> * ''D'' = 1/''C'' is elastance
+> * ''C'' is capacitance
+> * ''S'' is stiffness
+
+No, that is not a good solution.  Display maths lines are pretty universally indented for aesthetic reasons.  The definitions list following a maths display line are commonly indented as well.  Thus not indenting the ""where"" and using bullets are both not acceptable.  Bear in mind that a formula, even a display formula, can be inserted in the middle of a sentence so bullets would break the grammatical punctuation.  I can't understand this desire not to allow editors free use of indenting.  It is an editorial decision and there is no reason for VE to interfere or impose something different.  It is for the style guidelines to thrash out, not for VE to impose.",1412208518,PHID-USER-imut7wxehhy35ukuzaks,True,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","The mess created here is definitely a problem.
+
+However, what's being used there as ""indentation"" isn't indentation, strictly speaking; that text has been marked as the second half of a term-definition pair in a definition list, which is not semantically meaningful.  
+
+I don't know whether VisualEditor is expected to support the presence of only half of a paired list:  maybe, because it's (mis)used a lot, but maybe not, because it shouldn't be used that way?  (That decision is someone else's problem.)  
+
+However, what's represented there like this:
+
+:where,
+: ''D'' = 1/''C'' is elastance
+: ''C'' is capacitance
+: ''S'' is stiffness
+
+
+probably ought to be (for proper semantic meaning) a standard (non-definition/non-association) list like this:
+
+where,
+* ''D'' = 1/''C'' is elastance
+* ''C'' is capacitance
+* ''S'' is stiffness
+
+(or in a similar format, but without bullet points, which is possible but not as trivial to create in wikitext).
+
+It would be nice if MediaWiki actually supported plain old indentation, similar to pressing the tab key on a typewriter, perhaps along the lines of the request in bug 4521 (from 2006), but so far that request has not been granted.",1412185441,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+"VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome","I don't know if this is related, or whether it should be a new bug.  In this edit:
+
+https://en.wikipedia.org/w/index.php?title=User:Spinningspark/Work_in_progress/Mobility_analogy&diff=626824709&oldid=626823704
+
+VE adds a number of spurious indents.  The intended edit was to swap over the order of two blocks of text containing math markup.  Very frustrating that the problem could not even be fixed from within VE since indenting does not function in general.",1412132187,PHID-USER-imut7wxehhy35ukuzaks,True,PHID-TASK-uctbq2qfw5ogzgknys3a,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"1. Open up the standalone demo /empty.html and type some text
+2. Select text from right to left, mouse up outside the surface (or even outside the window)
+3. Although the text is selected in CE pressing dump range gives a collapsed range. Formatting actions will fail too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389195120,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eri6nma5at4veawakgy2,task_description,resolved
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Verified the fix in production,1411681950,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Verified the fix in test2,1411083301,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Verified the fix in Betalabs,1410810842,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"Change 159919 merged by jenkins-bot:
+Trigger selection update on selectionchange or mousemove events
+
+https://gerrit.wikimedia.org/r/159919",1410484474,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"Change 159919 had a related patch set uploaded by Esanders:
+Trigger selection update on selectionchange or mousemove events
+
+https://gerrit.wikimedia.org/r/159919",1410475411,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"Change 159807 merged by jenkins-bot:
+Bind ve.ce.Surface#onDocumentMouseUp to the entire document on mousedown
+
+https://gerrit.wikimedia.org/r/159807",1410471475,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,"Change 159807 had a related patch set uploaded by Esanders:
+Bound onDocumentMouseUp to the entire document on mousedown
+
+https://gerrit.wikimedia.org/r/159807",1410461605,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Or just stop the surface observer from being disabled. We currently have a bug whereby if you create a selection on a blurred document the SO isn't disabled so you can see the range being periodically updated as you change the selection.,1405016742,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Mouse up outside the surface doesn't register a selection change.,Perhaps we should be using document.onselectionchange to update the model selection (polyfill: https://github.com/2is10/selectionchange-polyfill),1405015999,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eri6nma5at4veawakgy2,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389118200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4hd4cmhduncacfpdevsv,task_description,resolved
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,Verified the fix in test2 and mw.org,1391129224,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,Verified the fix in Betalabs,1390609554,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"I believe that this is now fixed in master (but not in Beta Labs yet). Can reproduce in wmf11 but not in master, so closing as fixed by Roan's change in gerrit 108082.",1390021348,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"Observed Result:
+1.The page *focus* automatically scrolls up
+2.If you scroll up or down a bit you will see the link inspector is broken as shown in the screenshot",1389118877,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"Created attachment 14246
+Link inspector UI is broken
+
+**Attached**: {F12306}",1389118496,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article,"Steps to reproduce:
+
+1.Open a page with VE which contains two or more paragraphs
+2.At the end of the page select a text
+3.Press command+K and apply a link
+
+Observed Result:
+The page fous automatically scrolls up and if you scroll down a bit you will see the link inspector is broken as shown in the screenshot.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Jan7th?veaction=edit",1389118459,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4hd4cmhduncacfpdevsv,task_subcomment,NA
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari","Intention:
+Correct the spelling of a word.
+
+Steps to Reproduce:
+1. Add some text, including a spelling error, to an article.
+2. Use Safari's built-in spellcheck to correct the spelling. 
+
+
+Actual Results:  
+The correct spelling displays on the screen.  However, if you ""review changes"", only the old, incorrect spelling is present.  Also, the correct spelling stops being displayed on the screen if you hit return to start a new paragraph or list item.
+
+Screenshot shows the display and the review changes.  Confirmed in both lists and plain paragraphs.
+
+
+Reproducible: Always
+
+Confirmed in Safari 6 on Mac OS 10.8.5 using Vector.  It's not present in Firefox 26.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50822",1389056280,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-sfrluwneg7unava7ogpl,task_description,resolved
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari",">>! In T61748#836003, @Whatamidoing-WMF wrote:
+> I think we're making some progress on this.  Today, the automatic spelling correction is visible in ""Review changes"".  If the spelling change has the net effect of removing one character, then it even appears to be handled correctly.  However, if it adds a character, then the change is not made, but an equivalent number of extra letters are repeated at the end.
+> 
+> Examples:
+> 
+> * Typing ""teh"" and auto-correcting it to ""the"" displays correctly and saves correctly.
+> * Typing ""cantalop"" and auto-correcting it to ""cantaloup"" (adding one character) is saved as ""cantalopp"" (last letter repeated; added 'u' missing).
+> * Typing ""proftabilty"" and auto-correcting it to ""profitability""(adding two characters) is saved as ""proftabiltyty"" (last two letters repeated; added two letters missing).
+
+This also appears to now be fixed. Adding and removing characters works perfectly, in all three use cases here and others I tested.",1424273920,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sfrluwneg7unava7ogpl,task_subcomment,NA
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari","I think we're making some progress on this.  Today, the automatic spelling correction is visible in ""Review changes"".  If the spelling change has the net effect of removing one character, then it even appears to be handled correctly.  However, if it adds a character, then the change is not made, but an equivalent number of extra letters are repeated at the end.
+
+Examples:
+
+* Typing ""teh"" and auto-correcting it to ""the"" displays correctly and saves correctly.
+* Typing ""cantalop"" and auto-correcting it to ""cantaloup"" (adding one character) is saved as ""cantalopp"" (last letter repeated; added 'u' missing).
+* Typing ""proftabilty"" and auto-correcting it to ""profitability""(adding two characters) is saved as ""proftabiltyty"" (last two letters repeated; added two letters missing).
+",1418192661,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-sfrluwneg7unava7ogpl,task_subcomment,NA
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari",Confirmed with Safari 7 on 10.9,1389057186,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-sfrluwneg7unava7ogpl,task_subcomment,NA
+"Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari","Created attachment 14242
+VisualEditor screenshot, showing ""Review changes"" not matching the displayed text
+
+**Attached**: {F12267}",1389056395,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-sfrluwneg7unava7ogpl,task_subcomment,NA
+VisualEditor: Use gzip compression when POSTing HTML,"Per Gabriel's report via email, when VE POSTs HTML to api.php , it should ensure that gzip compression is used for the POST body.
+
+TODO: Figure out how to actually tell the browser to do this
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388891040,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vlthdxz6gr6ej4yayl53,task_description,resolved
+VisualEditor: Use gzip compression when POSTing HTML,"
+
+*** This bug has been marked as a duplicate of bug 66914 ***",1403735953,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vlthdxz6gr6ej4yayl53,task_subcomment,NA
+VisualEditor: Use gzip compression when POSTing HTML,"This doesn't seem to be supported natively in browsers. Even the XHR2 standard doesn't include support for this. Presumably this is because POST bodies large enough that compression is desired are rare, and because clients don't know in advance whether the server will support compression.
+
+We may be able to do this using a client-side gzip implementation; I'll have to see whether that makes sense. Alternatively, it might be that the savings from fixing bug 59660 and dropping data-parsoid will suffice.",1388987872,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vlthdxz6gr6ej4yayl53,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Intention:
+Add a caption to an image without having to type out the name by hand.
+
+Steps to Reproduce:
+1. Add an image in VisualEditor (e.g., an image of a person).  Open the caption dialog.
+2. Go to another window (e.g., an article about the person) and copy a =Name= from the article title.
+3. Paste the rich text into the caption.
+
+Actual Results:  
+The pasted text retained rich formatting.  It is not possible to remove the =Heading= formatting.  Only '''text''' <s>formatting</s> can be added or removed in that dialog.  So if you copy the article title from [[George Washington]] and paste it into the caption box, then it produces this wikitext:
+
+= <span dir=""auto"">George Washington</span> =
+
+and there is no way to remove the formatting.
+
+Expected Results:  
+That either you could remove the formatting, or ideally, that the caption box would strip the unwanted formatting automagically.  There's no obvious reason why someone would need or want a ==Heading== of any level in a caption.
+
+Reproducible: Didn't try
+
+Confirmed in Safari 6 and Firefox 26
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388776980,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_description,resolved
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Closing for now, though we may make further changes about removing or allowing certain kinds of formatting in future.",1391651684,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"We mean discouraged. At the moment there's a Parsoid bug that breaks list rendering, but we can revisit that decision if users really want it. And yes, the patch will convert lists to paragraphs.",1391642942,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"What does ""disallowed"" mean?  People do put lists into refs.  See https://en.wikipedia.org/wiki/Wikipedia:Verifiability#cite_note-9 for an example.
+
+It is important that people be able to paste something that was in a list format, even if it was converted into a paragraph upon pasting.",1391634077,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Disallowed inside references: references, reference lists, lists, definition lists, tables. Headings can be pasted but are converted to paragraphs.
+
+Disallowed inside image captions: lists, definition lists, tables. Headings can be pasted but are converted to paragraphs.",1391632187,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Change 110960 merged by jenkins-bot:
+Implement surface paste rules for media/ref dialogs
+
+https://gerrit.wikimedia.org/r/110960",1391628234,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,"Change 110960 had a related patch set uploaded by Esanders:
+Implement surface paste rules for media/ref dialogs
+
+https://gerrit.wikimedia.org/r/110960",1391600356,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target,SurfaceWidgets currently aren't even implementing the main surface's paste rules.,1391191118,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-vyopkwx7tzzhwu3uxyi3,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","I see now, that there is a dialog box for reference group, while in most cases, where refs are being used as citation, we dont need to fill that group. I propose than to give a tip below that dialox box saing: ""For reference list leave empty"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388573640,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_description,resolved
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","Change 114382 merged by jenkins-bot:
+Add placeholder to 'group' field in reference dialog too
+
+https://gerrit.wikimedia.org/r/114382",1392860375,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","(In reply to Alex Monk from comment #3)
+> Is there anything else to do here?
+
+Beyond also adding it to references' dialogs too (now done :-)), there's the TODO from that file:
+
+// TODO: Use a drop-down or something, and populate with existing groups instead of free-text
+
+But will split that off into a new bug (and it will require a new kind of OOjs UI widget anyway).",1392860331,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","Change 114382 had a related patch set uploaded by Jforrester:
+Add placeholder to 'group' field in reference dialog too
+
+https://gerrit.wikimedia.org/r/114382",1392860102,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty",Is there anything else to do here?,1392858295,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","Change 113684 merged by jenkins-bot:
+Show placeholder text in group input box on reference list dialog
+
+https://gerrit.wikimedia.org/r/113684",1392857039,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+"VisualEditor: Make the insertion of a reference list suck less; e.g. show ""General references"" as placeholder text in the group box when it is empty","Change 113684 had a related patch set uploaded by Alex Monk:
+Show ""General references"" as placeholder text in group input box on reference list insert dialog
+
+https://gerrit.wikimedia.org/r/113684",1392568946,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j4o6hezr3wnjxd57w5a5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in FireFox which contains a reference and reference list
+For example:
+reference<ref>reference</ref>
+<references />
+2.Copy the reference and the reference list
+3.Open another page with VE in FireFox
+4.Paste the reference and the reference list
+5.Save the page
+
+Observed Result:
+The wikitext resulting from after copy-paste is:
+
+reference<span class=""reference"" id=""cite_ref-1-0"" rel=""dc:references""><sup href=""http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit#cite_note-1"">[1]</sup></span>
+#<span class="""" rel=""mw:referencedBy"">[http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit#cite_ref-1-0 ↑]</span> reference
+
+And it redirects to the source page (in this case: http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit#cite_ref-1-0) 
+
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Newrefff
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12746}",1388531940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d6mwrlxedpo24myhvpw5,task_description,resolved
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,Verified the fix in test2,1391130109,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan24th_ff&action=edit,1390593630,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,betalabs doesn't have this code deployed yet,1390559944,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,"Still getting this issue on Betalabs:
+
+The resulting wikitext after copying a reference and reference list from FireFox to FireFox is:
+
+reference<span class=""reference"" id=""cite_ref-1-0"" rel=""dc:references""><sup href=""http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january?veaction=edit#cite_note-1"">[1]</sup></span>
+#<span class="""" rel=""mw:referencedBy""><a href=""http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january#cite_ref-1-0"">↑</a></span> reference",1390531161,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,"Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430349,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference is redirecting to the page from where it is copied in Firefox,"Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317337,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d6mwrlxedpo24myhvpw5,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page with VE in Chrome Browser which has references list in it 
+2.Copy the references list with the reference.For example copy the following:
+reference<ref>reference</ref>
+<references />
+3.Open another page in FireFox with VE
+4.Paste the copied reference and reference list
+5.Save the page
+
+Observed Result:
+The reference list got copied as bullet list rather than as <references/>
+
+The resulting wikitext is as follows:
+reference<sup>[1]</sup>
+# reference
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Chrome Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=31st_december&veaction=edit
+FF Page:http://en.wikipedia.beta.wmflabs.org/wiki/Newrefff
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12743}",1388527440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wuqpc2pu5uodgmseauhd,task_description,resolved
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,Verified the fix in test2,1391130429,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,Verified the fix in Betalabs.,1390593485,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,betalabs doesn't have this code deployed yet,1390559956,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,"Still getting this issue on betalabs.
+
+Copied Reference list from this page:http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january?veaction=edit
+
+
+
+Pasted on the page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Paste_reference&action=edit
+
+The resulting wikitext is:
+reference<sup>[1]</sup>
+# reference",1390530842,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,"Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430346,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF,"Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317332,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wuqpc2pu5uodgmseauhd,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in Chrome Browser with VE which has a template in it
+2.Copy the template
+3.Open another page in FirFox browser with VE
+4.Paste the copied template
+
+Observed result:
+The template does not get copied and in the console an error appears:
+TypeError: item is undefined
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/31st_decemberff?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12738}",1388526240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oupzvbwduxmp5jze2owb,task_description,resolved
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,Verified the fix in test2,1391130924,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,betalabs doesn't have this code deployed yet,1390559897,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,I can still reproduce this issue on Betalabs.,1390531607,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,"Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430355,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined,"Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317327,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oupzvbwduxmp5jze2owb,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,"Steps to reproduce:
+
+1.Open a page with VE which has reference added to a text
+2.Copy the text with the reference 
+3.Open another page with VE in FireFox
+4.Paste the copied reference
+
+Observed Result:
+Instead of getting copied as text <ref> reference </ref>, it is getting copied as text<sup> [1] </sup>
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=30th_december_ff&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388450160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_description,resolved
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,Verified the fix in test2,1391131365,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan24th_ff&action=edit,1390593605,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,betalabs doesn't have this code deployed yet,1390559950,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,"Still getting this issue on betalabs.
+
+Copied Reference list from this
+page:http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january?veaction=edit
+
+
+
+Pasted on the
+page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Paste_reference&action=edit
+
+The resulting wikitext is:
+reference<sup>[1]</sup>
+# reference",1390530965,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,"Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430358,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox,"Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317342,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ye5mwgkyf24rzjhatyv4,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF","Screenshot
+
+Steps to reproduce:
+
+1.Open the VE in Chrome browser for a page which contains image
+2.Copy the image
+3.Open another VE in FireFox browser
+4.Paste the copied image
+
+Observed Result:
+Image does not get copied.An error appears in the console:
+TypeError: item is undefined
+	
+
+...nction(){return this.getData(this.balancedRange);};ve.dm.LinearData=function VeD...
+
+load.p...2128Z&* (line 122)
+
+See the screenshot attached.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+http://en.wikipedia.beta.wmflabs.org/wiki/30th_december_ff?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12694}",1388441100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-udmrgnust5cyxf2ghvzk,task_description,resolved
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF",Verified the fix in test2,1391131595,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF",Verified the fix in Betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/Jan_24th?veaction=edit,1390593751,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF",betalabs doesn't have this code deployed yet,1390559938,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF",I can still reproduce it on Betalabs,1390531301,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF","Change 108680 merged by jenkins-bot:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390430352,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF","Change 108680 had a related patch set uploaded by Esanders:
+Protect RDFa attributes from obliteration
+
+https://gerrit.wikimedia.org/r/108680",1390317322,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-udmrgnust5cyxf2ghvzk,task_subcomment,NA
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template","Warning in the save dialog box
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add the template Cite Web from Insert>Transclusion
+3.Save the page
+4.Reopen the page with VE
+5.Do some more edit in that page
+5.Click on ""Save Page""
+
+Observed Result:
+A warning appears in the save dialog box ""You edit may have been corrupted-Please review your changes""
+
+This error appears everytime I add this Cite Web template even though there is no apparent reason for being my edit corrupted.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12545}",1388269860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-24fbkjihpzafrhlh33na,task_description,resolved
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template","Change 115510 abandoned by Jforrester:
+[Browser test] WIP Additional Scenario for bug 59091 regression.
+
+Reason:
+Not currently being worked on AFAICT.
+
+https://gerrit.wikimedia.org/r/115510",1396279329,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-24fbkjihpzafrhlh33na,task_subcomment,NA
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template","Change 115510 had a related patch set uploaded by Jhall:
+[Browser test] WIP Addtional Scenario for bug 59091 regression.
+
+https://gerrit.wikimedia.org/r/115510",1393360356,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-24fbkjihpzafrhlh33na,task_subcomment,NA
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template",Got fixed with the fix of https://bugzilla.wikimedia.org/show_bug.cgi?id=59002,1389909929,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-24fbkjihpzafrhlh33na,task_subcomment,NA
+"VisualEditor: ""You edit may have been corrupted"" Warning appears everytime after adding Cite Web template","**spektre1** wrote:
+
+Tested on my private install. Any transclusion at all seems to throw it this error in the save dialog.",1389305990,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-24fbkjihpzafrhlh33na,task_subcomment,NA
+VisualEditor:Cannot Edit any page in betalabs,"Attempting to edit any page in betalabs is giving following error:
+Error loading data from server: internal_api_error_MWException: Exception Caught: Tag hook for namespace is not callable.
+
+In the console,I see the following error
+Uncaught TypeError: Cannot read property '$actions' of null
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27th_december
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1388182380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-edd62atl2rczsx2d656j,task_description,declined
+VisualEditor:Cannot Edit any page in betalabs,This issue is not happening anymore in betalabs now.I can now open any page to edit.,1388204152,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-edd62atl2rczsx2d656j,task_subcomment,NA
+VisualEditor:Cannot Edit any page in betalabs,"Error message from exception.log is: 
+
+2013-12-27 22:53:15 deployment-apache33 enwiki: [f9bc37e3] /w/api.php   Exception from line 3585 of /data/project/apache/common-local/php-master/includes/parser/Parser.php: Tag hook for namespace is not callable
+
+#0 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3333): Parser->callParserFunction(Object(PPTemplateFrame_DOM), 'NAMESPACE', Array)
+#1 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#2 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3247): PPFrame_DOM->expand(Object(PPNode_DOM))
+#3 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#4 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3483): PPFrame_DOM->expand(Object(PPNode_DOM))
+#5 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#6 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1532): PPFrame_DOM->expand(Object(DOMElement), 4)
+#7 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1540): PPTemplateFrame_DOM->getNamedArgument('group allowed')
+#8 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3947): PPTemplateFrame_DOM->getArgument('group allowed')
+#9 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1132): Parser->argSubstitution(Array, Object(PPTemplateFrame_DOM))
+#10 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3247): PPFrame_DOM->expand(Object(PPNode_DOM))
+#11 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#12 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3247): PPFrame_DOM->expand(Object(PPNode_DOM))
+#13 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#14 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3488): PPFrame_DOM->expand(Object(PPNode_DOM))
+#15 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPTemplateFrame_DOM))
+#16 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3483): PPFrame_DOM->expand(Object(PPNode_DOM))
+#17 /data/project/apache/common-local/php-master/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPFrame_DOM))
+#18 /data/project/apache/common-local/php-master/includes/parser/Parser.php(3150): PPFrame_DOM->expand(Object(PPNode_DOM), 0)
+#19 /data/project/apache/common-local/php-master/includes/parser/Parser.php(1212): Parser->replaceVariables('{{editnotice lo...')
+#20 /data/project/apache/common-local/php-master/includes/parser/Parser.php(395): Parser->internalParse('{{editnotice lo...')
+#21 /data/project/apache/common-local/php-master/includes/cache/MessageCache.php(1064): Parser->parse('{{editnotice lo...', Object(Title), Object(ParserOptions), true)
+#22 /data/project/apache/common-local/php-master/includes/Message.php(845): MessageCache->parse('{{editnotice lo...', NULL, true, true, Object(StubUserLang))
+#23 /data/project/apache/common-local/php-master/includes/Message.php(590): Message->parseText('{{editnotice lo...')
+#24 /data/project/apache/common-local/php-master/includes/Message.php(669): Message->toString()
+#25 /data/project/apache/common-local/php-master/includes/Title.php(4892): Message->parseAsBlock()
+#26 /data/project/apache/common-local/php-master/extensions/VisualEditor/ApiVisualEditor.php(298): Title->getEditNotices()
+#27 /data/project/apache/common-local/php-master/includes/api/ApiMain.php(862): ApiVisualEditor->execute()
+#28 /data/project/apache/common-local/php-master/includes/api/ApiMain.php(387): ApiMain->executeAction()
+#29 /data/project/apache/common-local/php-master/includes/api/ApiMain.php(358): ApiMain->executeActionWithErrorHandling()
+#30 /data/project/apache/common-local/php-master/api.php(76): ApiMain->execute()
+#31 /data/project/apache/common-local/w/api.php(3): require('/data/project/a...')
+#32 {main}",1388184890,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-edd62atl2rczsx2d656j,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open the editor for page
+2.Go to Insert>Template
+3.Search for template Cite Web
+4.Add a a value for source title field but keep the URL field empty
+5.Add the template
+6.Click the button ""Save Page""
+
+Observed Result: 
+The ""Save Page"" button does not work .In the console it is showing an error:
+Uncaught TypeError: Object [object Text] has no method 'setAttribute'
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55985
+
+**Attached**: {F12409}",1388169840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_description,resolved
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,Works for mw.org in Chrome now.Might be a caching issue.,1389900032,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"(In reply to comment #21)
+> This issue is verified for test2.But in mw.org I still cannot save after
+> adding
+> a template in Chrome 26.0.1410.65, however it does not show any error in the
+> console as such Uncaught TypeError: Object [object Text] has no method
+> 'setAttribute'
+> 
+> In FireFox, it works for both test 2 and mw.org.
+> 
+> Hence reopening it.If it is a separate issue please Close this one , I will
+> file a separate issue for mw.org
+
+Maybe if you refresh it will go away? Sounds most likely like a cacheing issue…",1389891174,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,Can't reproduce on mw.org. Which template did you use?,1389891018,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"This issue is verified for test2.But in mw.org I still cannot save after adding a template in Chrome 26.0.1410.65, however it does not show any error in the console as such Uncaught TypeError: Object [object Text] has no method 'setAttribute'
+
+In FireFox, it works for both test 2 and mw.org.
+
+Hence reopening it.If it is a separate issue please Close this one , I will file a separate issue for mw.org",1389845563,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,Now fixed and back-ported to production.,1389837750,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107638 merged by Catrope:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107638",1389831589,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107530 merged by Catrope:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107530",1389831578,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107640 merged by Catrope:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107640",1389831553,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107531 merged by Catrope:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107531",1389831544,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107640 had a related patch set uploaded by Catrope:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107640",1389819206,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107638 had a related patch set uploaded by Catrope:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107638",1389818593,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107559 merged by jenkins-bot:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107559",1389817561,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107559 had a related patch set uploaded by Esanders:
+About-group extra DOM data in toDomElements
+
+https://gerrit.wikimedia.org/r/107559",1389784095,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,data-ve-ignore showing up in converter in some cases still. Working on a fix.,1389782794,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Fix has been merged, backported and will be deployed during tomorrow's lightning deploy window (Thu Jan 16 00:00 - 00:30 UTC; Wed Jan 15 16:00 - 16:30 PST)",1389754131,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107511 merged by jenkins-bot:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107511",1389749660,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107531 had a related patch set uploaded by Catrope:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107531",1389749651,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107530 had a related patch set uploaded by Catrope:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107530",1389749596,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Change 107511 had a related patch set uploaded by Esanders:
+Wrap text nodes in spans if trying to mark as data-ve-ignore
+
+https://gerrit.wikimedia.org/r/107511",1389743226,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,*This is happening for adding all templates on test2*,1389730479,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,This s\is happening for adding all templates on test2.,1389730436,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Adding to my previous comment: when i try to switch to wiki markup mode i get the same error. No way to save my stuff :(
+
+Here's a stack trace:
+
+Uncaught TypeError: Object [object Text] has no method 'setAttribute' 
+ve.dm.MWTransclusionNode.static.toDomElements 
+ve.dm.Converter.getDomElementsFromDataElement 
+ve.dm.Converter.getDomSubtreeFromData 
+ve.dm.MWReferenceNode.static.toDomElements 
+ve.dm.Converter.getDomElementsFromDataElement 
+ve.dm.Converter.getDomSubtreeFromData 
+ve.dm.Converter.getDomSubtreeFromModel 
+ve.dm.Converter.getDomFromModel 
+ve.init.mw.ViewPageTarget.editSource 
+ve.ui.MWEditModeSourceTool.onSelect 
+OO.ui.ToolGroup.onMouseUp 
+OO.ui.PopupToolGroup.onMouseUp 
+proxy 
+jQuery.event.dispatch 
+elemData.handle.eventHandle",1389616325,PHID-USER-no27b6dclreknhhzodyn,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"I can reproduce this problem as well. A pity, because not being able to save makes the Visual Editor, well, pretty much useless. I've changed priority to 'High' for that reason.",1389616198,PHID-USER-no27b6dclreknhhzodyn,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27th_december&veaction=edit",1388169940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jqbci4yiint3kpdehjhn,task_subcomment,NA
+VisualEditor: Alt + any key in a slug introduces a pawn in Firefox on Windows,"With FireFox (compulsory) on Windows
+insert a new line then enter : Alt A (or Alt + any key)
+=> a pawn is inserted
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61538",1387409040,PHID-USER-hhw22zfd2xzrsyc22lp5,False,PHID-TASK-nbwk4dgm4c4qnjzg6thr,task_description,resolved
+VisualEditor: Alt + any key in a slug introduces a pawn in Firefox on Windows,Have re-tested; no issue any more.,1421282349,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nbwk4dgm4c4qnjzg6thr,task_subcomment,NA
+VisualEditor: Alt + any key in a slug introduces a pawn in Firefox on Windows,"Looks like alt+a doesn't fire a KeyPress event in Chrome whereas it does in FF. As slugs are always pawned, and there is no inserted content from alt+a we have a problem.",1387465822,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nbwk4dgm4c4qnjzg6thr,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,"VisualEditor supports the 'apex' skin, however that isn't installed on WMF projects, so users using a non-supported skin will see ""&lt;skinname-apex&gt;"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387340940,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-tudylk7ksc5zbhsewjyu,task_description,resolved
+BetaFeatures: Validate skin requirement is installed before showing it,"Sorry, page error. This comment is for bug 70814.",1410617419,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,"The current state on the Wikimedia project is without the names of the required skins. In the case it is wanted to keep the current state (for Wikimedia and/or for the master branch of BetaFeatures), this feature can be hidden with CSS, similarly to the browser requirements, by editing BetaFeatures/resources/betafeatures.less.",1410617306,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,"Change 102383 merged by jenkins-bot:
+Don't show skin names if the user can't enable them
+
+https://gerrit.wikimedia.org/r/102383",1404238799,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,*** Bug 63151 has been marked as a duplicate of this bug. ***,1395898645,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+BetaFeatures: Validate skin requirement is installed before showing it,"Change 102383 had a related patch set uploaded by Legoktm:
+Don't show skin names if the user can't enable them
+
+https://gerrit.wikimedia.org/r/102383",1387341704,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tudylk7ksc5zbhsewjyu,task_subcomment,NA
+VisualEditor:Reference is getting copied as an empty <ref/> tag,"screenshot of the error
+
+Steps to reproduce:
+
+1.Go to this page:
+
+https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/12th_december&veaction=edit
+
+2.Copy the reference and the reference list at the end of this page
+3.Paste in into another VE
+4.Save it
+
+Observed Result:
+
+The wiki text for the text copied is: 
+
+reference<ref>http://cnn.com</ref>
+<references />
+
+The wiki text on the page where it is copied to:
+reference<ref />
+<references />
+
+In Edit mode it says:
+The reference is defined in a template or other generated block and for now can
+only be edited in source mode.
+
+and the reference cannot be edited using VE
+
+
+In read mode it shows:
+
+Cite error: The opening <ref> tag is malformed
+or has a bad name (see the help page).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12112}",1386894600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sxmma4s54vfesb7w6uwo,task_description,resolved
+VisualEditor:Reference is getting copied as an empty <ref/> tag,"verified the fix in test2 with  MediaWiki 1.23wmf8 on page:
+https://test2.wikipedia.org/wiki/Another_page20th",1387559522,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sxmma4s54vfesb7w6uwo,task_subcomment,NA
+VisualEditor:Reference is getting copied as an empty <ref/> tag,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/December_16th,1387211609,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sxmma4s54vfesb7w6uwo,task_subcomment,NA
+VisualEditor:Reference is getting copied as an empty <ref/> tag,This appears to be fixed in master. Please re-open if you can reproduce on beta labs.,1387210816,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sxmma4s54vfesb7w6uwo,task_subcomment,NA
+VisualEditor: Transclusion template suggestions are no longer available,"**Author:** `jhall`
+
+**Description:**
+Seen in beta labs with these repro steps:
+
+1)  Open Visual Editor.
+2)  Select ""Transclusion"" from the ""Insert"" menu.
+3)  Type some characters in the ""New Template"" text box.
+
+In previous releases of VE, the user would get a list of template suggestions.  That list of suggestions doesn't seem to be displaying anymore :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53231",1386875760,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_description,declined
+VisualEditor: Transclusion template suggestions are no longer available,Now the template suggestions are appearing.,1388168683,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_subcomment,NA
+VisualEditor: Transclusion template suggestions are no longer available,"This is again happening on betalabs.I dont see any template suggestion appearing. 
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/26th_december?veaction=edit",1388082270,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_subcomment,NA
+VisualEditor: Transclusion template suggestions are no longer available,"**jhall** wrote:
+
+(In reply to comment #1)
+> This seems to work for me? Which browser is this in? (Tested in Mac/Chrome 31
+> and Mac/Firefox 25.)
+
+Hmmm… this does now seem to be working in beta labs with Chrome, Firefox, and Safari on Mac OS.  I successfully get transclusion template suggestions for the letters C, N, T, and W.  My favorite suggestion so far is ""Noble Pipe"".  Not sure what that is, but it's a great name for a transclusion template.
+
+I'll update the automated browser test to search by one of the letters indicated above (rather than by ""S"", which doesn't currently return any suggestions).",1387296859,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_subcomment,NA
+VisualEditor: Transclusion template suggestions are no longer available,This seems to work for me? Which browser is this in? (Tested in Mac/Chrome 31 and Mac/Firefox 25.),1387245213,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c3pmu5hmgxjgedm5kw7e,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Screenshot inside reference
+
+We have changed the toolbar design to have all the formatting under one button A (underlined) and all other options to add elements under Insert option.
+
+But if you open up the Media Settings or a Reference the toolbar that appears there does not conform with the new design.
+It will better to have a consistent design everywhere the toolbar is used.
+
+See the screemshots attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12060}",1386874140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i73bqleta3mxkalcjer2,task_description,resolved
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit,1386965991,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,Now being deployed on wmf7.,1386890427,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Change 101047 merged by Catrope:
+Use the same new toolbar for media and reference dialogs
+
+https://gerrit.wikimedia.org/r/101047",1386890178,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Change 101039 merged by jenkins-bot:
+Use the same new toolbar for media and reference dialogs
+
+https://gerrit.wikimedia.org/r/101039",1386876744,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Change 101047 had a related patch set uploaded by Jforrester:
+Use the same new toolbar for media and reference dialogs
+
+https://gerrit.wikimedia.org/r/101047",1386876707,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Change 101039 had a related patch set uploaded by Jforrester:
+Use the same new toolbar for media and reference dialogs
+
+https://gerrit.wikimedia.org/r/101039",1386876171,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE,"Created attachment 14073
+toolbar inside media settings
+
+**Attached**: {F12061}",1386874279,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i73bqleta3mxkalcjer2,task_subcomment,NA
+VisualEditor: Clouds are added at the end of a paste,"A could sometimes suddenly appears. As well as 'left over sections' it seems.
+
+https://www.mediawiki.org/w/index.php?title=User:TheDJ/sandbox&oldid=841359
+
+I think this was due to ""select all"" cmd-A, then cmd-v paste over the old content.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386844260,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-npjjopn76exjm4ew3cxf,task_description,resolved
+VisualEditor: Clouds are added at the end of a paste,I believe we fixed this bug with the CE select-all change that Ed worked on two months ago.,1402508824,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-npjjopn76exjm4ew3cxf,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Steps to reproduce:
+
+
+1.Open the editor for a page which contains link
+
+2.Copy it.
+
+3.Paste it into a new line 
+
+4.Save it
+
+Observed Result:
+The link is getting merged on to the end of the previous line
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386790440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_description,resolved
+VisualEditor: CE adds linebreaks when pasting into empty lines,*The fix for the original issue has been verified in test 2 with mediawiki 1.23wmf8*,1387484260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"The original issue of this bug has been verified in test 2 with MediaWiki 1.23wmf8 
+on page:https://test2.wikipedia.org/wiki/19th_december",1387484077,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,This is a new bug and something to do with Parsoid and Selser. Filed as bug 58695.,1387471583,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"After these steps if you try copying a math function or a link on the third line of Page B , it will also get merged with the two merged links",1387470527,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Sorry, here are the detailed steps: 
+
+1.Create a page ""A"" with three links in three consecutive lines.
+2.Create another page ""B"" where you will copy these links to.
+3.Copy the first and second link to ""B""
+4.Save it.
+5.Reopen the editor.
+6.Now copy the third link and paste it to the third line of ""B""
+7.Save it.
+
+Observed Result:
+The second and the third link in page B is getting merged.
+
+Example Pages:
+
+A:http://en.wikipedia.beta.wmflabs.org/wiki/19th_december_source?veaction=edit
+B:http://en.wikipedia.beta.wmflabs.org/wiki/19th_destination",1387468526,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,Works for me in Chrome and Firefox. Please provide detailed instructions if you can reproduce.,1387466105,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"I am still getting the issue of two links getting merged in one line after pressing enter after pasting the first link:
+http://en.wikipedia.beta.wmflabs.org/wiki/December_17th",1387310733,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Change 101905 merged by jenkins-bot:
+Strip trailing linebreaks on paste due to Chrome bug
+
+https://gerrit.wikimedia.org/r/101905",1387306391,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Change 101905 had a related patch set uploaded by Esanders:
+Strip trailing linebreaks on paste due to Chrome bug
+
+https://gerrit.wikimedia.org/r/101905",1387218312,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,This latest version of the bug is known issue with CE in Chrome when pasting into a newline.,1387214118,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Modification in steps to reproduce:
+
+1.Open the editor 
+2.Copy a link or a text
+3.Paste it into another VE
+4.Observed that the cursor is automatically to the next line though you have not pressed Enter/return
+5.Now paste the link or the text again in that position without pressing enter
+6.Save the page
+
+Observed Result:
+The texts or the links are getting merged in the same line",1387210853,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,The issue of link getting merged is still reproducible in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/December_16th,1387209664,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Another issue which I think might be related with this, if not I will file separate bug:
+
+Steps to reproduce:
+
+
+1.Open the editor for a page 
+
+2.Copy a text
+
+3.Paste it into another page
+
+4.Copy an image and paste it onto the next line
+
+Observed Result:
+The image does not gets pasted in the other VE.",1386794603,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Modification in steps to reproduce:
+
+step 3 :paste it into a newline on another page or VE",1386793274,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Created attachment 14062
+Screenshot
+
+**Attached**: {F12812}",1386791724,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: CE adds linebreaks when pasting into empty lines,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=11th_december",1386790517,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yw4lbpse7jkf77ng3ueg,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Steps to reproduce:
+
+1.Open the Editor.
+2.Place the cursor inside a word or text but do not select anything
+3.Press command+c
+4.Now go to another page and do command+v (Nothing is getting copied, which is okay as per the fix given in https://bugzilla.wikimedia.org/show_bug.cgi?id=58138)
+5.But now select anything from the source page by selecting it
+6.Press command+c
+7.Press command+V onto the other page where you were pasting.
+
+Observed Result:
+Nothing gets copied
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386788820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kq6jtegqhbf7n3nonedr,task_description,resolved
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,Pushed to wmf6.,1386808461,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Change 100915 merged by jenkins-bot:
+Move resetting of paste state variables to after afterPaste
+
+https://gerrit.wikimedia.org/r/100915",1386803574,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Change 100915 had a related patch set uploaded by Jforrester:
+Move resetting of paste state variables to after afterPaste
+
+https://gerrit.wikimedia.org/r/100915",1386799598,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,Verified on betalabs,1386796268,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Change 100827 merged by jenkins-bot:
+Move resetting of paste state variables to after afterPaste
+
+https://gerrit.wikimedia.org/r/100827",1386790134,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Change 100827 had a related patch set uploaded by Esanders:
+Move resetting of paste state variables to after afterPaste
+
+https://gerrit.wikimedia.org/r/100827",1386789819,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word,"Test Environment:betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5",1386788905,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kq6jtegqhbf7n3nonedr,task_subcomment,NA
+Special:ExtensionDistributor/VisualEditor not picking up REL1_22,"Maybe some new config has to be added for it to consider REL1_22 as a valid branch to download?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386779400,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-6rfydyjylk7nntzf43tk,task_description,resolved
+Special:ExtensionDistributor/VisualEditor not picking up REL1_22,"Change 100799 merged by jenkins-bot:
+Add REL1_22 to ExtensionDistributor branches
+
+https://gerrit.wikimedia.org/r/100799",1386780385,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6rfydyjylk7nntzf43tk,task_subcomment,NA
+Special:ExtensionDistributor/VisualEditor not picking up REL1_22,"Change 100799 had a related patch set uploaded by Reedy:
+Add REL1_22 to ExtensionDistributor branches
+
+https://gerrit.wikimedia.org/r/100799",1386780267,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6rfydyjylk7nntzf43tk,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Safari 7
+
+Copy on https://www.mediawiki.org/wiki/VisualEditor?veaction=edit
+
+From and including the header Timeline, up to the paragraph before ""Notes"" headline (including the table).
+
+Past in an empty surface:
+
+[Error] TypeError: 'undefined' is not an object (evaluating 'source.clone')
+	copy (undefined, line 3)
+	getClonedElement
+	fixupInsertion
+	fixupInsertion
+	newFromDocumentInsertion
+	afterPaste
+	proxy (load.php, line 10)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386752340,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-3vfkchuyvemtkqdiybsv,task_description,resolved
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,Pushed to wmf6.,1386808472,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Change 100916 merged by jenkins-bot:
+Allow tables to contain captions!
+
+https://gerrit.wikimedia.org/r/100916",1386803625,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Change 100916 had a related patch set uploaded by Jforrester:
+Allow tables to contain captions!
+
+https://gerrit.wikimedia.org/r/100916",1386799611,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Change 100792 merged by jenkins-bot:
+Allow tables to contain captions!
+
+https://gerrit.wikimedia.org/r/100792",1386786079,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"Change 100792 had a related patch set uploaded by Esanders:
+Allow tables to contain captions!
+
+https://gerrit.wikimedia.org/r/100792",1386776728,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,Part of this appears to be caused by table captions. Investigating.,1386775890,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,"More detail: the problem is caused by ContentEditable (surprise). When you paste a table into an empty paragraph, the paragraph is *completely* deleted, which the paste context comparer can't currently deal with.",1386774900,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Pasting a table with a caption breaks fixUpInsertion,The problem here is that fixUpInsertion is deciding you can't put a table in a paragraph but not resolving properly.,1386774787,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3vfkchuyvemtkqdiybsv,task_subcomment,NA
+VisualEditor: Typing between text and a reference produces a pawn in Firefox,"This came from the Hebrew Wikipedia feedback page, I could not replicate it in the English Wikipedia
+
+It seems to happen only in Firefox.
+
+
+To reproduce -
+
+1. Go to this sample page: https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Nurick/%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_-_%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99&oldid=14834614&veaction=edit
+
+2. Put the cursor a couple of character to the left of the word ""יפן"" (third paragraph, the word with the reference attached)
+
+3. Move the cursor so it is between the word and the reference.
+
+4. Add a period.
+
+Watch a pawn appear.
+
+* Firefox 25.0.1 on Windows and on Ubuntu
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386748620,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-fbvcimq5q66ajybncb7c,task_description,resolved
+VisualEditor: Typing between text and a reference produces a pawn in Firefox,This appears to be now fixed. I think.,1406596147,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fbvcimq5q66ajybncb7c,task_subcomment,NA
+VisualEditor: Typing between text and a reference produces a pawn in Firefox,*** Bug 67620 has been marked as a duplicate of this bug. ***,1404763355,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fbvcimq5q66ajybncb7c,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki","This is an interesting feedback comment that came from the Hebrew Wikipedia and I managed to also replicate in the English Wikipedia. 
+
+Steps to replicate:
+
+1. Go to a Sandbox page under a username. For example, this page https://en.wikipedia.org/w/index.php?title=User:Mooeypoo/Sandbox&veaction=edit
+
+2. Mark one of the words and add an existing page to link to it. For instance, I marked 'some' and chose the link to ""Somerset"".
+
+3. Inspect the link while still in VisualEditor - the link is under the user namespace, so in my example, the link is now ""https://en.wikipedia.org/wiki/User:Mooeypoo/Somerset""
+
+4. Save the page.
+
+5. After save, the link seems fine (points to https://en.wikipedia.org/wiki/Somerset as it should).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59196",1386745260,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-yavg34kffrrjkowzgnkc,task_description,resolved
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki","Change 119914 merged by jenkins-bot:
+Hack around Parsoid's href prefixing in rendering new links
+
+https://gerrit.wikimedia.org/r/119914",1395874565,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki",*** Bug 59196 has been marked as a duplicate of this bug. ***,1395363345,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki","Change 119914 had a related patch set uploaded by Jforrester:
+Hack around Parsoid's href prefixing in rendering new links
+
+https://gerrit.wikimedia.org/r/119914",1395363291,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki",*** Bug 59196 has been marked as a duplicate of this bug. ***,1395344109,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+"VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki",*** Bug 62877 has been marked as a duplicate of this bug. ***,1395344091,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yavg34kffrrjkowzgnkc,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"Broken UI
+
+Steps to reproduce:
+
+
+1.Open the editor 
+2.create a link
+3.Save the page
+4.Re-open the editor.
+5.Select the link to modify it
+
+Observed Result:
+
+Link inspector is not opening.Coming back from some other window opens it but the UI is totally broken
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12763}",1386721860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eoqysm7gglrd73chhak6,task_description,resolved
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,verified on test2:https://test2.wikipedia.org/w/index.php?title=13th_december&veaction=edit,1386982947,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,verified in betalabs.,1386805068,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"Change 100828 merged by jenkins-bot:
+Followup 5d7673eb: still adjust width/height when positioning fails
+
+https://gerrit.wikimedia.org/r/100828",1386792229,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"Change 100828 had a related patch set uploaded by Catrope:
+Followup 5d7673eb: still adjust width/height when positioning fails
+
+https://gerrit.wikimedia.org/r/100828",1386790070,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"yes, i can still reproduce it .",1386787011,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,Can you still reproduce this? It works for me.,1386786919,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"
+Test Environment:betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example:http://en.wikipedia.beta.wmflabs.org/wiki/Latex?veaction=edit",1386722053,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation,"Created attachment 14053
+No link inspector opening up
+
+**Attached**: {F12764}",1386721962,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eoqysm7gglrd73chhak6,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","screenshot of the error and empty Latex window
+
+Steps to reproduce:
+
+1.Add a bullet list
+2.Add a template as a bulleted item
+3.Save the page and reopen the editor
+4.Go to the next line of the bulleted list (get rid of bullets by pressing return twice)
+
+5.Click on More>Latex
+
+Observed Result:
+
+The latex window is opening up at the right end, where the template is placed.
+
+6.Then if you change the focus by clicking somewhere on the page outside the latex window
+
+Observed Result:
+
+A blank Latex windows is opening up and a uncaught type error appears Uncaught TypeError: Cannot call method 'getOuterRange' of null 
+
+If you save the page and go to edit source , you will see empty <math> tag is getting placed
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62797
+
+**Attached**: {F12725}",1386706860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_description,resolved
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",Verified the fix in production,1398988255,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",Verified the fix in test2,1398898767,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Change 129622 merged by jenkins-bot:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/129622",1398384371,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Change 129622 had a related patch set uploaded by Jforrester:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/129622",1398384255,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",Verified the fix on Betalabs,1397855570,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Change 126900 merged by jenkins-bot:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/126900",1397845433,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Change 126900 had a related patch set uploaded by Esanders:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/126900",1397780751,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",This code as of gerrit 126900 is moving back into VE's repo where it needs to be fixed.,1397705234,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""",*** Bug 62797 has been marked as a duplicate of this bug. ***,1397704103,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","This happens because ve.ui.MWMathInspector.prototype.setup assumes that after calling insertContent() to insert a math node, the selection will cover the math node exactly. But in a block slug, that's not true, because fixupInsertion will have amended the insertion to wrap the math node in a paragraph. Then when the selection does not precisely cover a FocusableNode, focusedNode will be null.",1387229637,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Modification in steps to reproduce:
+
+4.There is an empty bullet place cursor there and then go to More>Latex
+
+It can also be reproduced by adding image in step 2.",1386719531,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+"VisualEditor: Inserting a formula into a block slug throws ""Uncaught TypeError: Cannot call method 'getOuterRange' of null""","Created attachment 14050
+emtpy <math> tags
+
+**Attached**: {F12726}",1386707070,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yd7ochttyhijjxl6b2jj,task_subcomment,NA
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"E.g. copying the disclaimer from my staff page https://www.mediawiki.org/wiki/User:Jdforrester_%28WMF%29 takes:
+
+<p><b>Disclaimer:</b> Although I work for the Wikimedia Foundation, contributions under this account do not necessarily represent the actions or views of the Foundation unless expressly stated otherwise. For example, edits to articles or uploads of other media are done in my individual, personal capacity unless otherwise stated.</p>
+
+… and turns it into the wikitext:
+
+'''Disclaimer:'''
+<nowiki> </nowiki>Although I work for the Wikimedia Foundation, contributions under this
+account do not necessarily represent the actions or views of the
+Foundation unless expressly stated otherwise. For example, edits to
+articles or uploads of other media are done in my individual, personal
+capacity unless otherwise stated.
+
+… (with the newlines showing before saving; not a Parsoid bug).
+
+No new lines added when doing a plain paste.",1386702300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f4tvdtjt3vze2yti62aa,task_description,resolved
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"Change 100614 merged by Catrope:
+Fix paste sequence in Firefox
+
+https://gerrit.wikimedia.org/r/100614",1386720865,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-f4tvdtjt3vze2yti62aa,task_subcomment,NA
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"Change 100613 merged by jenkins-bot:
+Fix paste sequence in Firefox
+
+https://gerrit.wikimedia.org/r/100613",1386703730,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-f4tvdtjt3vze2yti62aa,task_subcomment,NA
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"Change 100614 had a related patch set uploaded by Jforrester:
+Fix paste sequence in Firefox
+
+https://gerrit.wikimedia.org/r/100614",1386703720,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-f4tvdtjt3vze2yti62aa,task_subcomment,NA
+VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox,"Change 100613 had a related patch set uploaded by Esanders:
+Fix paste sequence in Firefox
+
+https://gerrit.wikimedia.org/r/100613",1386703041,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-f4tvdtjt3vze2yti62aa,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"Failed to read file: exception 'Exception' with message 'Expected open tag, whitespace, or variable., got T_STRING ('array_map')' in /a/common/php-1.23wmf6/extensions/LocalisationUpdate/QuickArrayReader.php:135
+Stack trace:
+#0 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/QuickArrayReader.php(119): QuickArrayReader->except(Array, 'open tag, white...')
+#1 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(528): QuickArrayReader->__construct('<?php $messages...')
+#2 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(313): LocalisationUpdate::parsePHP('$messages = arr...', 'messages')
+#3 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(435): LocalisationUpdate::loadFilesToCompare('VisualEditor', '/var/lib/l10nup...', '/a/common/php-1...', false, false)
+#4 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(153): LocalisationUpdate::compareExtensionFiles('VisualEditor', '/var/lib/l10nup...', '/a/common/php-1...', false)
+#5 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(113): LocalisationUpdate::updateExtensionMessages('/a/common/php-1...', 'VisualEditor', false, '/var/lib/l10nup...')
+#6 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/update.php(34): LocalisationUpdate::updateMessages(Array)
+#7 /a/common/multiversion/MWScript.php(97): require_once('/a/common/php-1...')
+#8 {main}
+Failed to parse /var/lib/l10nupdate/mediawiki/extensions/VisualEditor/VisualEditor.i18n.php
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386642780,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-y4bnpd7zbos4ftiaptko,task_description,resolved
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"(In reply to Amir E. Aharoni from comment #6)
+> Is this fixed now?
+
+I believe it will be fixed by gerrit 119944 when that is merged and deployed.",1395520301,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,Is this fixed now?,1395519881,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"Please see https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/LocalisationUpdate+branch:json-rewrite,n,z",1394795013,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,This issue is tracked in mingle at https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/3897,1387482123,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"(In reply to comment #2)
+> Change 100527 merged by jenkins-bot:
+> Revert ""Shim for VisualEditor.i18n.php that reads JSON blobs""
+> 
+> https://gerrit.wikimedia.org/r/100527
+This has been reintroduced, because despite the scary-looking exception, it didn't actually break LU for anything other than VE.",1386721977,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"Change 100527 merged by jenkins-bot:
+Revert ""Shim for VisualEditor.i18n.php that reads JSON blobs""
+
+https://gerrit.wikimedia.org/r/100527",1386643458,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages,"Change 100527 had a related patch set uploaded by Jforrester:
+Revert ""Shim for VisualEditor.i18n.php that reads JSON blobs""
+
+https://gerrit.wikimedia.org/r/100527",1386643286,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y4bnpd7zbos4ftiaptko,task_subcomment,NA
+"VisualEditor: On load, don't select a node if it's the first thing in the document","Ed,
+
+Think you were working on this before? Would be lovely to finally get this fixed…
+
+J.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57477",1386641760,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nesgwricmarnjfu5yju5,task_description,resolved
+"VisualEditor: On load, don't select a node if it's the first thing in the document",Verified the fix on test2,1389906629,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-nesgwricmarnjfu5yju5,task_subcomment,NA
+"VisualEditor: On load, don't select a node if it's the first thing in the document","Change 106707 merged by jenkins-bot:
+Move initial selection to first content offset
+
+https://gerrit.wikimedia.org/r/106707",1389641452,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nesgwricmarnjfu5yju5,task_subcomment,NA
+"VisualEditor: On load, don't select a node if it's the first thing in the document","Change 106707 had a related patch set uploaded by Esanders:
+Move initial selection to first content offset
+
+https://gerrit.wikimedia.org/r/106707",1389367335,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nesgwricmarnjfu5yju5,task_subcomment,NA
+"VisualEditor: On load, don't select a node if it's the first thing in the document",Any update on this? It's a significant UX issue.,1387305115,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-nesgwricmarnjfu5yju5,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"The Errors
+
+Steps to reproduce:
+
+1.Open an editor which has a text with reference and the reflist
+For example:
+
+text with reference[1]
+↑ ref
+
+2.Try to paste it into a different page
+
+Observed Result:
+Uncaught TypeError: Cannot read property 'length' of undefined appears and nothing gets pasted.
+
+However the ""Save Page"" button is active and clicking on that gives the error:
+Uncaught TypeError: Cannot call method 'getRange' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12622}",1386630120,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_description,resolved
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,Yes please. Give steps with wikitext to reproduce.,1386894085,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Checked the fix in production.The issue specified in this bug is fixed.Reference is getting pasted with reference list and the subsequent elements are getting copy-pasted properly.But still there is a problem with pasting reference :(
+
+The reference is getting copied as an empty <ref/> tags and on edit mode it says 
+The reference is defined in a template or other generated block and for now can only be edited in source mode.
+
+In read mode: There is an error:Cite error: The opening <ref> tag is malformed or has a bad name (see the help page).
+
+Should I create a different issue ticket for that?",1386893689,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,Now being deployed on wmf6 and wmf7.,1386890311,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101133 merged by Catrope:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101133",1386890076,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101134 merged by Catrope:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101134",1386890063,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101134 had a related patch set uploaded by Catrope:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101134",1386890036,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101131 merged by jenkins-bot:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101131",1386890024,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101133 had a related patch set uploaded by Catrope:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101133",1386890020,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Change 101131 had a related patch set uploaded by Esanders:
+Check InternalList node exists when rendering MWReferenceList
+
+https://gerrit.wikimedia.org/r/101131",1386889396,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"In production, go to this page :https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/12th_december&veaction=edit
+
+Copy the last reference along with reference list and try to paste it into another page.
+And after that nothing can be copied into the other VE",1386888679,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"I am escalating this issue, because it is now reproducible in production:https://en.wikipedia.org/wiki/ and after this action copy-paste does not work from one VE to another.",1386887125,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page with reference and reflist: :http://en.wikipedia.beta.wmflabs.org/wiki/Bold?veaction=edit",1386630288,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-unomzqtpqw6kv6noyrev,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Table format in destination page
+
+Steps to reproduce:
+
+1.Open the editor.
+2.Copy a template with a parameter which has a value and paste it into a different page
+3.Copy a template which does not have any parameter  and paste it into a different page
+4.Copy a template with a parameter which does not have any value.
+
+
+Observed Result:
+
+
+1.All the template copied are getting pasted as a table
+2.If you switch to the edit source you will see :
+
+the template copied in step 2 has a table format
+the template copied in step 3 is getting pasted in an empty template wikitext format:{|
+!
+|}
+
+the template copied in step 4 is getting pasted in a template wikitext format with the page name inside it:{|
+!Copy
+|}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12618}",1386629040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_description,resolved
+VisualEditor: Template is getting pasted as a table while doing copy-paste,verified in production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/13th_december,1386983673,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,(And back-ported to wmf6.),1386810383,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Change 100943 merged by Catrope:
+Fix issues with copy-pasting MWTransclusionNodes
+
+https://gerrit.wikimedia.org/r/100943",1386809823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Change 100943 had a related patch set uploaded by Catrope:
+Fix issues with copy-pasting MWTransclusionNodes
+
+https://gerrit.wikimedia.org/r/100943",1386809812,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Change 100775 merged by jenkins-bot:
+Fix issues with copy-pasting MWTransclusionNodes
+
+https://gerrit.wikimedia.org/r/100775",1386809136,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Change 100775 had a related patch set uploaded by Esanders:
+Fix issues with copy-pasting MWTransclusionNodes
+
+https://gerrit.wikimedia.org/r/100775",1386759929,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"For an example
+if you go to this page :http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Paste
+
+I have copied three templates from http://en.wikipedia.beta.wmflabs.org/wiki/Copy
+and they are having these issues.",1386709164,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,Can you give a more specific example. The templates I'm testing on copy and paste okay.,1386707443,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Created attachment 14043
+tooltip and yellow bordered box
+
+**Attached**: {F12620}",1386629528,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"After pasting a template, which has parameter with no value, it does not let user to edit that template on the edit mode.
+and shows a tooltip ""Sorry this element can be edited in source mode now"" with yellow bordered box.
+
+See the screenshot attached",1386629488,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Template is getting pasted as a table while doing copy-paste,"Created attachment 14042
+The edit source section for the destination page
+
+**Attached**: {F12619}",1386629195,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nm5utpa7p43ribr4hikq,task_subcomment,NA
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,"screenshot
+
+Steps to reproduce:
+
+1.Open the editor for a page
+2.Place a link to a page
+3.Rename the link text to something different than the destination page name
+4.Save the page
+5.Now copy this link and paste it to another page
+6.Save the second page
+
+Observed Result:
+In the read mode of the second page the wikitext for the link is showing up
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12566}",1386614460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-in4rh3odis5atqwtca5u,task_description,resolved
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,"OK, will mark as FIXED.",1386973700,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-in4rh3odis5atqwtca5u,task_subcomment,NA
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,"I cannot reproduce it either now.But, this was a different issue than bug 58136",1386973640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-in4rh3odis5atqwtca5u,task_subcomment,NA
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,I can't reproduce now - is this the same as bug 58136?,1386973295,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-in4rh3odis5atqwtca5u,task_subcomment,NA
+VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target,"Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/wiki/Linker",1386614564,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-in4rh3odis5atqwtca5u,task_subcomment,NA
+VisualEditor: Copied/pasted wiki links are prefixed with ./,"See: https://www.mediawiki.org/w/index.php?title=User:Eloquence/CP_tests&oldid=838815
+
+Copied from:
+https://www.mediawiki.org/w/index.php?title=VisualEditor:Welcome&oldid=799120
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386573000,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-4qiopkau6hjwndo32zi6,task_description,resolved
+VisualEditor: Copied/pasted wiki links are prefixed with ./,This was fixed in Ed's series of fixes to rich copy and paste in (I think) the same week this was filed; sorry for the very slow triage.,1394489459,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4qiopkau6hjwndo32zi6,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","screenshot of the icon
+
+Steps to reproduce:
+
+1.Open the editor for an article
+2.Place your cursor any position of a link and press command+c.
+3.Open another page and press command+v
+
+Observed:
+ An icon ☁ appears on the second page.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58136
+
+**Attached**: {F12394}",1386377460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hratsjfcabvp22ykev47,task_description,resolved
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too",verified the fix on test2:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/13th_december?veaction=edit,1386983801,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too",Verified in Betalabs,1386787483,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Change 100605 merged by Catrope:
+Check the selection has collapsed after pasting
+
+https://gerrit.wikimedia.org/r/100605",1386720891,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Change 100605 had a related patch set uploaded by Jforrester:
+Check the selection has collapsed after pasting
+
+https://gerrit.wikimedia.org/r/100605",1386700920,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Change 100578 merged by jenkins-bot:
+Check the selection has collapsed after pasting
+
+https://gerrit.wikimedia.org/r/100578",1386694996,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Change 100578 had a related patch set uploaded by Esanders:
+Check the selection has collapsed after pasting
+
+https://gerrit.wikimedia.org/r/100578",1386690762,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Ignore that, only works if the cursor is placed on a blank line.",1386675839,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too",Can't reproduce in Chrome 30 on OSX.,1386675792,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too","Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Linker?veaction=edit",1386377561,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hratsjfcabvp22ykev47,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"**Author:** `Wikifram`
+
+**Description:**
+Version 2013-12-05 (MW 1.23wmf6), implemented at MediaWiki, now for the first time tested apparently (by me)... When you add a reference, the cursor is again positioned at the top of the article, no matter where you insert the reference. The focus (the part you actually see) of the page is where you added the reference, but when you start typing, you are actually adding text to the top of the page. This is confusing as hell. 
+
+The same applies when adding a template, but not with media.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1386320580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_description,resolved
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,*** Bug 57034 has been marked as a duplicate of this bug. ***,1394659143,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,Verified on betalabs,1386805619,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,*** Bug 57438 has been marked as a duplicate of this bug. ***,1386805579,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"A fix for this for wmf6 is going out in about 4 minutes' time; fixing it for wmf5 would involve back-porting half of wmf6, and is too risky. Sorry for the disruption.",1386633441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"Change 100496 merged by jenkins-bot:
+Don't move the cursor to the top of the page after closing a dialog
+
+https://gerrit.wikimedia.org/r/100496",1386632906,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"Change 100490 merged by jenkins-bot:
+Don't move the cursor to the top of the page after closing a dialog
+
+https://gerrit.wikimedia.org/r/100490",1386631280,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"Change 100496 had a related patch set uploaded by Jforrester:
+Don't move the cursor to the top of the page after closing a dialog
+
+https://gerrit.wikimedia.org/r/100496",1386631235,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,"Change 100490 had a related patch set uploaded by Catrope:
+Don't move the cursor to the top of the page when closing a dialog
+
+https://gerrit.wikimedia.org/r/100490",1386628831,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,This is actually present in 1.23wmf5 as well.,1386582487,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page,*** Bug 58194 has been marked as a duplicate of this bug. ***,1386572578,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-aqkrg4zofhwpyfihiwdi,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","**Author:** `Wikifram`
+
+**Description:**
+Have you ''really'' implemented a new version at MediaWiki that scrolls to the ''bottom'' of the page when opened in VE? Was this intentional or (if I'm allowed to say this) just something that should have been obvious with the most basic test, but somehow wasn't noticed? FF25, W7, nothing fancy or unusual. And no, this didn't happen in earlier versions, and doesn't happen when I use VE on enwiki...
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386319980,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uzu755zs7nfkcf7hr26i,task_description,resolved
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox",A fix for this is going out in about 4 minutes' time. Sorry for the disruption.,1386633345,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","Change 99785 merged by jenkins-bot:
+mw.Target: Fix document focus scroll bug
+
+https://gerrit.wikimedia.org/r/99785",1386633010,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","Change 99785 had a related patch set uploaded by Jforrester:
+mw.Target: Fix document focus scroll bug
+
+https://gerrit.wikimedia.org/r/99785",1386375914,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","Change 99718 merged by jenkins-bot:
+mw.Target: Fix document focus scroll bug
+
+https://gerrit.wikimedia.org/r/99718",1386366052,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","Change 99718 had a related patch set uploaded by Krinkle:
+mw.Target: Fix document focus scroll bug
+
+https://gerrit.wikimedia.org/r/99718",1386361397,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox",Confirming with Firefox 25 on Fedora 20 on mediawiki.org.,1386334403,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+"VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox","**Wikifram** wrote:
+
+Note that the ''cursor'' is at the top, but the part of the page you view (if the page is longer than the screen) is the bottom, so your cursor isn't even visible when you start typing... If it had been intentional, I suppose that the cursor would have been at the bottom as well (still useless, but at least consistent).",1386320191,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uzu755zs7nfkcf7hr26i,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Steps to reproduce:
+
+1.Open any article on VE
+2.Add a bullet list
+3.Try to add an image as a bulleted item of that list ( the image goes to the right side but keep it like that)
+4.Save the page
+5.Reopen the editor
+6.Now go to position where empty bullet list is.
+7.Now try to remove it by clicking ob bullet list icon from the toolbar
+
+Observed Result:
+The Editor become completely unresponsive
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386284160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_description,resolved
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,Verified the fix in Betalabs,1393888539,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,Cannot verify this issue for:https://bugzilla.wikimedia.org/show_bug.cgi?id=62022,1393538488,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Change 115402 merged by jenkins-bot:
+Add special case to de-indentation for slugs in listItems
+
+https://gerrit.wikimedia.org/r/115402",1393445614,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Change 115385 merged by jenkins-bot:
+Check indentation was successful before trying again
+
+https://gerrit.wikimedia.org/r/115385",1393445540,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Change 115402 had a related patch set uploaded by Esanders:
+Add special case to de-indentation for slugs in listItems
+
+https://gerrit.wikimedia.org/r/115402",1393349283,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,Above patch prevents infinite loop. Need to investigate why indentation is failing.,1393343694,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Change 115385 had a related patch set uploaded by Esanders:
+Check indentation was successful before trying again
+
+https://gerrit.wikimedia.org/r/115385",1393343480,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Also occurs (same STR) with the wikitext
+
+* {{infobox}}
+
+on testwiki.",1387191429,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Created attachment 13998
+Screenshot
+
+**Attached**: {F12233}",1386284405,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Infact it makes the browser page unresponsive.I could not close the browser window even until it showed an error to kill page in Chrome and stop script in FF.
+
+See the screenshot attached.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/unresponsive?veaction=edit
+
+In this page, Go to the last bullet and click on Bullet icon from toolbar to reproduce.",1386284358,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive,"Infact it makes the browser page unresponsive.I could not close the browser window even until it showed an error to kill page in Chrome and stop script in FF.
+
+See the screenshot attached.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/unresponsive?veaction=edit
+
+In this page, Go to the last bullet and click on Bullet icon from toolbar to reproduce.",1386284348,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhbaybf77c2fnawhs7mp,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"Screenshot
+
+Button UI is missing in production for Link/Undo/Redo/Cancel formatting 
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12207}",1386277320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_description,resolved
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,Verified in Production,1386282991,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"Deployment issue fixed by touching the OOjs UI file in wmf5:
+
+https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&diff=91382&oldid=91381",1386282831,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"I am not seeing any UI of the following buttons in production:
+Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings",1386277676,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"Created attachment 13997
+Screenshot of the UI missing in More option
+
+**Attached**: {F12208}",1386277555,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/windows8?veaction=edit",1386277408,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nqplnxbxs7jfzg4fzdna,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Steps to reproduce:
+
+There are several issues in this bug.I tried to document all of them chronologically in one issue for convenience.
+
+
+1.click on the Edit button
+2.click on the bullet list icon.
+3.Click on tab to add indentation to the list for several times.
+4.Now press Enter/Return
+5.It deletes the bullets, where as pressing delete does not do that.
+6.After deleting all the bullets by pressing return it goes to the next line 
+7.Again add bulleted list with indentation on the first line
+8.Now this time if you press Enter it goes to the next line but does not add next bullet.
+9.Now go to the end of the first line and press enter, this time the next bullet gets added.
+10.Now try adding indentation to the second item , it does not work
+11.Delete the bullet and repeat the action again,this time it will add indentation.
+12.Now if you save the page , you will see there is no bullets in the read mode
+13.If you try to delete all the content by selecting with mouse pad, it gives the error:
+""Uncaught Error:Invalid start offset:-1""
+
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page where in the read mode there is no bullets but in the edit mode they appear:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/New_bullet
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386192540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_description,resolved
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Looks like this was done as part of the ""handle enter"" re-write.",1395442089,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Giving steps to reproduce again:
+
+1.Open a completely new page with VE
+2.Add a text
+3.Click on Bullet list icon from the toolbar
+4.Add indentation to that line
+5.Go to the next line (Adds a second bullet)
+6.Add indentation to this second bullet line too
+7.Go back to the first bullet point and delete the text
+8.Go back to end of the second empty bullet point
+9.Press Delete(this will bring all the bullet points in one line)
+
+After this step you will get the error:Uncaught TypeError: Cannot call method 'getOffset' of null 
+
+If you press Delete again it will show error Uncaught Error: Invalid start offset: -1",1391727442,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","I can't reproduce this problem as written (Chrome here too), but there is some funkiness related to being able to split some mutli-depth bullet list items oddly.",1391662904,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Created attachment 14234
+Reproduced on 6th Jan
+
+**Attached**: {F12102}",1389030036,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Yes , I can still reproduce it.Attaching the screenshot.
+Are you getting the error:Uncaught TypeError: Cannot call method 'getOffset' of null ?",1389029763,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list",I've reproduced the steps in the video but I don't get an exception. Can you try again with the latest code.,1389028954,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Created attachment 14088
+video capture of the bug
+
+**Attached**: {F12101}",1386957303,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Steps 1-7 are as expected. I don't understand step 8, as after 7 there is only one double-indented bullet item.",1386932229,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+"VisualEditor: ""Uncaught Error:Invalid start offset:-1"" shows up while deleting the bullets of a bulleted list","Another way to reproduce the error ""Uncaught Error:Invalid start offset:-1""
+
+1.Open the editor
+2.Add a text 
+3.Go the next line add a bullet list with a text
+4.Add indentation to that item
+5.Press enter go to the next line then add indentation to the second empty bullet item
+6.Press enter to go to the next line
+7.It actually takes the cursor to the end of first bulleted item
+8.Press delete until all the bullets comes in the same line.
+9.The cursor then moves to the end of the first line of step 2
+10.Delete that text
+11.Now place your cursor at the end of series bullets press delete to delete it
+
+A. you will get the error:Uncaught TypeError: Cannot call method 'getOffset' of null
+
+B. If you again press delete , you will get ""Uncaught Error:Invalid start offset:-1""
+
+C. if you press undo then redo, you will get ""Uncaught Error: Unbalanced input passed to document""
+
+D. if you attempt to save the page, you will get ""Uncaught TypeError: Cannot set property 'lastOuterPost' of null""",1386373019,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-h43bnjrvp2e4ey2244ee,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"Screenshot of the error
+
+Steps to reproduce:
+
+Still Unknown.Will update once I get it.
+
+Mostly it occurred to me when I reload an open editor after an idle time or switch from Edit Source to VE it does not the editor and shows the following error:
+
+
+TypeError:Cannot read property 'Element' of undefined >TypeError
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12080}",1386178920,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_description,resolved
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,verified the fix in production.,1386880418,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,Verified the fix on betalabs:http://en.wikipedia.beta.wmflabs.org/,1386266416,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,One way it is always reproducible is: while creating a new page switch to Create-Beta.,1386185048,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,Somehow OO.ui becomes undefined. I have no idea why.,1386184360,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"Created attachment 13984
+Screenshot of the error
+
+**Attached**: {F12082}",1386183665,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"From VE, switched to Edit source then again switching back to VE gave this error this time and VE did not load
+
+Uncaught TypeError: Cannot read property 'Element' of undefined
+VeUiSurface
+(anonymous function)",1386183642,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"Created attachment 13983
+Screenshot of the error
+
+**Attached**: {F12081}",1386179425,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"The environment in my previous comment will be betalabs.
+
+The error occured again while creating a new page on Betalabs.
+
+ypeError: Cannot read property 'Element' of undefined TypeError {} load.php:145
+log load.php:145
+runScript load.php:154
+checkCssHandles load.php:155
+(anonymous function) load.php:155
+fire load.php:12
+self.fireWith load.php:14
+self.fire load.php:14
+addEmbeddedCSS load.php:149
+(anonymous function) load.php:149",1386179386,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit",1386179015,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-atznnv7miiw6xcbyzewl,task_subcomment,NA
+Pre-fetch VisualEditor modules to improve load speed,"First impressions count! You can make the initial experience of loading VE substantially faster by prefetching the modules on a standard article page if the DOM isn't busy.
+
+What I have in mind is something like this:
+
+    $( window ).load( function () {
+        if ( !mw.loader.store.enabled ) {
+            return;
+        }
+
+        setTimeout( function () {
+            var modules = [
+                'ext.visualEditor.base',
+                'ext.visualEditor.core'
+                'ext.visualEditor.data',
+                'ext.visualEditor.icons-vector',
+                'ext.visualEditor.mediawiki',
+                'ext.visualEditor.viewPageTarget',
+                'ext.visualEditor.viewPageTarget.icons-vector',
+            ]
+
+            mw.loader.using( modules.filter( function ( module ) {
+                var key = mw.loader.store.getModuleKey( module );
+                return key in mw.loader.store.items;
+            } ) );
+
+        }, 0 );
+    } );
+
+
+You'd need to ensure that the modules don't execute automatically somehow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1386109920,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-7xlzuxk3ore4kep2xn5u,task_description,declined
+Pre-fetch VisualEditor modules to improve load speed,"I'll challenge my own contention from 2013:
+> You can make the initial experience of loading VE substantially faster 
+
+Probably not. For all but the slowest of connections, VE load time is dominated by the cost of fetching the Parsoid DOM, building the linear model, and then building the ContentEditable DOM from the linear model. The cost of retrieving the JavaScript and CSS is negligible in comparison.
+
+This may or may not be worth doing, but in the absence of good data, there is no strong case for doing this work, so I'm closing this for now.",1442609143,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-7xlzuxk3ore4kep2xn5u,task_subcomment,NA
+Pre-fetch VisualEditor modules to improve load speed,Roan says there should be some infrastructure in RL to do this.,1422664786,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-7xlzuxk3ore4kep2xn5u,task_subcomment,NA
+Pre-fetch VisualEditor modules to improve load speed,"It's fine for them to execute automatically, nothing happens until .activate() is invoked.",1386110539,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7xlzuxk3ore4kep2xn5u,task_subcomment,NA
+VisualEditor: Paragraphs merged into image captions by backspace,"Wiktext:
+[[File:Image.jpg|thumb|Foo]]
+Bar
+
+Place the cursor the the left of 'B' and press backspace
+
+Expected: Image is focused
+Result: 'Bar' is moved into the image caption
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386086400,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-izzgctdjakrtomfnsa2n,task_description,resolved
+VisualEditor: Paragraphs merged into image captions by backspace,verified in betalabs,1386808249,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-izzgctdjakrtomfnsa2n,task_subcomment,NA
+VisualEditor: Paragraphs merged into image captions by backspace,"Change 99419 merged by jenkins-bot:
+Prevent content selections ending up inside handlesOwnChildren nodes
+
+https://gerrit.wikimedia.org/r/99419",1386266565,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-izzgctdjakrtomfnsa2n,task_subcomment,NA
+VisualEditor: Paragraphs merged into image captions by backspace,"Change 99419 had a related patch set uploaded by Esanders:
+Prevent content selections ending up inside handlesOwnChildren nodes
+
+https://gerrit.wikimedia.org/r/99419",1386261968,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-izzgctdjakrtomfnsa2n,task_subcomment,NA
+VisualEditor: Cache key is not cleared when surface is torn down,"1. Open VE on a page
+2. Make a change
+3. Go into save dialog, review diff
+4. Close save dialog without saving
+5. Click Read tab, click through warning that you'll lose your changes
+6. Click Edit tab to open VE again
+7. Make a change that's very different from #2
+8. Go into save dialog, review diff
+9. Observe that the diff displayed is for #2, not #7
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386033660,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-o2njh75t3ulqqtpvzcjc,task_description,resolved
+VisualEditor: Cache key is not cleared when surface is torn down,"Change 98752 merged by jenkins-bot:
+Clear cache key when deactivating target
+
+https://gerrit.wikimedia.org/r/98752",1386095070,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o2njh75t3ulqqtpvzcjc,task_subcomment,NA
+VisualEditor: Cache key is not cleared when surface is torn down,"Change 98752 had a related patch set uploaded by Catrope:
+Clear cache key when deactivating target
+
+https://gerrit.wikimedia.org/r/98752",1386039187,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o2njh75t3ulqqtpvzcjc,task_subcomment,NA
+VisualEditor: Snowmen being created (no reproduction steps),"On fr.wp at least a couple of edits were noticed that generated snowmen:
+
+https://fr.wikipedia.org/w/index.php?title=D%C3%A9sir_mim%C3%A9tique&diff=98365348&oldid=96841726
+and https://fr.wikipedia.org/w/index.php?title=Andromaque&diff=98765089&oldid=97860409 (a vandalism).
+
+The snowman appears in the word ""français(e)"" (so it's possibly related to the ç character?).
+
+No other details available - the first editor didn't provide them, and the other was a vandal.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1386018180,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-s6jclbzflvjqvzupxbrv,task_description,resolved
+VisualEditor: Snowmen being created (no reproduction steps),I believe that we fixed the last of the snowmen issues (ha!) with the re-write last week; I've not been able to reproduce these edits at all now. Provisionally marking as FIXED.,1407061838,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-s6jclbzflvjqvzupxbrv,task_subcomment,NA
+VisualEditor: Snowmen being created (no reproduction steps),*** Bug 67591 has been marked as a duplicate of this bug. ***,1404767562,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-s6jclbzflvjqvzupxbrv,task_subcomment,NA
+VisualEditor: Snowmen being created (no reproduction steps),"Here's another odd set of snowmen, this time at the Javanese Wikipedia.  
+
+https://jv.wikipedia.org/w/index.php?title=Igor_Stravinsky&curid=73209&diff=881366&oldid=830233
+
+The edit was inappropriate (poor English replacing Javanese) and was reverted.",1393356467,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-s6jclbzflvjqvzupxbrv,task_subcomment,NA
+VisualEditor: Snowmen being created (no reproduction steps),"About the first case, where an external link was added and a <br> tag can also be observed, User:Drongou notes that it is ""utterly incomprehensible. It's impossible to add a <br> vith VE, and VE itself does not seem to generate it. It must have come from copy/paste (snowmen are typical of failed copy/paste). Really strange, (one would rather expect a <br />): all the inclusions of <br> should be checked.""
+
+I roughly translated his words. I didn't notice that before - he's right that adding <br> by hand in VE would produce nowiki tags, which are not there.",1386020602,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-s6jclbzflvjqvzupxbrv,task_subcomment,NA
+Flow: API module issues,"For action=flow:
+* The ""flowaction"" parameter lacks a description.
+* The ""page"" parameter lacks a description.
+* The ""flowaction"" parameter does not list available actions.
+* The ""params"" parameter is poorly documented. Passing a json blob of ""params"" is rather awful. I might rather see a setup where ""flowaction"" selects a submodule, along the lines of how action=query works, so these parameters could actually be documented in api.php.
+* getExamples() should be properly implemented.
+* getHelpUrls() should be implemented.
+* I'm assuming at least some of the possible flowactions are write actions. isWriteMode() should therefore return true.
+* I note that ApiBase is already a ContextSource, so there is no need for $this->getContext()->getUser() instead of just $this->getUser().
+* I see you're setting ""_element"" directly. Use ApiResult's method to handle that instead, please. The same goes if you're setting ""*"" directly anywhere.
+* I see that sometimes the ""result"" element in the result will be an associative array and sometimes it will be the string ""error"". I'd rather see a ""status"" element of some sort that is always a string and have ""result"" always be an associative array when it is present.
+* I see you have a ""doRenderer"" protected method that is never actually called.
+
+For list=flow:
+* The link returned by getHelpUrls() does not actually document this API module.
+* The ""flowaction"" parameter does not list available actions.
+* Same criticisms of the ""params"" blob as above.
+* You are setting ""_element"" directly instead of using ApiResult's methods.
+* You should be checking the return from ApiResult's addValue method and properly handling failure.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1385566620,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_description,resolved
+Flow: API module issues,"Marking as fixed, the issues in comment 0 were fixed, and it supports autogenerated documentation.
+
+What's still missing is the on-wiki documentation, that's bug 58361.",1405325549,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to Brad Jorsch from comment #0)
+
+> For list=flow:
+> * The link returned by getHelpUrls() does not actually document this API
+> module.
+
+I had removed this earlier, but I'll make sure to add it in once the parameters are finalized.
+
+> * The ""flowaction"" parameter does not list available actions.
+
+Removed in I73347cb3b0a8cf35881691f50e70be10d10571b8 because it's pointless.
+
+> * Same criticisms of the ""params"" blob as above.
+
+After looking through all the JS that call this, they're either options to control the result format, like ""contentFormat"": ""wikitext"", or they're a post-id. I'll turn this into 2-3 more parameters to the API module directly.
+
+> * You are setting ""_element"" directly instead of using ApiResult's methods.
+
+Note to self that this needs to be fixed in all implementations of Block::renderAPI as well.
+
+> * You should be checking the return from ApiResult's addValue method and
+> properly handling failure.
+
+From the documentation, addValue will return false if the data is too big. We'll need some kind of continuation parameter...I'm not exactly sure how Flow handles that internally.
+
+https://gerrit.wikimedia.org/r/#/q/project:mediawiki/extensions/Flow+topic:flow-api,n,z",1396424928,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"action=flow looks much better!
+
+list=flow still needs work though, so reopening.",1396015870,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"Change 107411 merged by jenkins-bot:
+API: Revamp action=flow
+
+https://gerrit.wikimedia.org/r/107411",1396001572,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"This bug is marked as ""PATCH_TO_REVIEW"", but the patch in question is marked as work in progress (""[WIP]"").  For clarity, I'm moving this back out to ""assigned"", since I understand that Kunal is working on it.",1393010611,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"> (In reply to comment #21)
+Alex Z., what do you and others want from a Flow API?  How can we best collaborate on it?  A Flow board makes API requests for all in-page updates, so Flow heavily exercises its API while we implement Brad Jorsch's feedback, but I'm concerned about what we overlook. I filed bug 60808 and bug 60809, but I'm just guessing.
+
+Erik Bernhardson posted https://en.wikipedia.org/wiki/Wikipedia:Bot_owners%27_noticeboard#New_extension:_Flow , so that's another venue. I mentioned these bugs there.
+
+I've created https://www.mediawiki.org/wiki/Flow/Architecture/API with links to these, and empty sections awaiting use cases. I'll try to keep it updated.
+
+Thanks everyone.",1391493384,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #21)
+> So, to expand: I fully believe that the community should be factored into the
+> decision-making process, directly and indirectly - but factored in is very
+> different from being a trump card. If the argument is ""there will be people
+> who
+> look at the API and think it's Us Doing The VisualEditor All Over Again"",
+
+I'm looking at this and thinking, ""Oh, no, it's them doing WikiEditor all over again,"" where a product is deployed to wikis before the API is properly documented or becomes stable, and bot/script developers practically have to reverse engineer it in order to update all of their code in time.
+
+I mean, you're at the point of field testing it in production, but there apparently isn't even a specification for how the real API will work, let alone a place where the people who will be using it might actually be able to make some input.",1391486589,PHID-USER-xab2aohgotczcynszcm2,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #24)
+> (In reply to comment #23)
+> > Easily. Just include the necessary text in the string returned from the
+> > module's getDescription() method.
+> 
+> Sorry, more meant ""Can the team please do this soon, or say why not?"" :)
+
+https://gerrit.wikimedia.org/r/#/c/110967/ should address that.",1391449078,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #23)
+> Easily. Just include the necessary text in the string returned from the
+> module's getDescription() method.
+
+Sorry, more meant ""Can the team please do this soon, or say why not?"" :)",1391211062,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #22)
+> So, back on topic...
+> 
+> From Brian on bug 60178 comment 28:
+> ""I would think the appropriate thing to do (If we must do this) is to
+> include a
+> note in the auto-generated api documentation.""
+> 
+> Can this be done
+
+Easily. Just include the necessary text in the string returned from the module's getDescription() method.",1391207891,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"So, back on topic...
+
+From Brian on bug 60178 comment 28:
+""I would think the appropriate thing to do (If we must do this) is to include a note in the auto-generated api documentation.""
+
+Can this be done, or explain why not? I still think a note to BAG or similar is good in addition, personally.",1391203609,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #19)
+> (In reply to comment #9)
+> 
+> > Possibly. There are some community members who would find a way to take
+> > offence to ""how is your day going?"". I don't particularly think we should base
+> > our decisions around pandering to them.
+> 
+> This is unacceptable attitude, Oliver. You in particular should know better
+> than that.
+
+Sorry, I should be clearer; the 'them' is 'the sort of people who would find a way to take offence...'
+
+So, to expand: I fully believe that the community should be factored into the decision-making process, directly and indirectly - but factored in is very different from being a trump card. If the argument is ""there will be people who look at the API and think it's Us Doing The VisualEditor All Over Again"", that's a bad argument, and the sort of people who would jump from 'the minimum viable product is not perfect' to 'everything is going to be terrible forever' are not people I am particularly interested in basing our decisions on, because anyone who _makes_ that cognitive leap is clearly not approaching things rationally, and so it becomes very hard to actually compromise with them - if compromising with them is actually worthwhile in the first place.",1391199755,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #13)
+> Personally I find impersonal communication methods like bugzilla a passive
+> aggressive way to air issues without actually talking to anyone directly.
+
+I'm severely confused. After reading comment 0 out of the blue, I expected comment 1 to start like this: ""Great Brad, thanks for your thorough review of our API module! It's very useful when someone helps us learn more about/do better with some specialised areas of the code rather than let us alone hitting against a wall"". And then a conversation to clarify the various actionable items and to log them properly in atomic bugs or cards.",1391199542,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #9)
+
+> Possibly. There are some community members who would find a way to take
+> offence to ""how is your day going?"". I don't particularly think we should base
+> our decisions around pandering to them.
+
+This is unacceptable attitude, Oliver. You in particular should know better than that.",1391197935,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(Off-topic, like the rest of the last 6 or so comments, but, I wanted to publicly say: Sorry for my tone. We'll work together on addressing this bug.)",1391192912,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #15)
+> (In reply to comment #14)
+> > Bugzilla is how one files bugs against a product--sorry you don't like it.
+> > The
+> > nice thing is it's asynchronous so if someone is in a different timezone they
+> > can easily report issues without waiting for you to be around :)
+> 
+> Bugzilla is an excellent way to track bugs, but for solving problems nothing
+> beats communicating with a human being in real time.  The foundation uses
+> real
+> time communication within teams extensively to organize and ensure the work
+> they want to get done happens.  Embrace the most effective forms of
+> communication you can.
+> 
+> Lucky for those in other timezones, we have team members in 2 american
+> timezones, europe and australia.
+
+The point is simply: there was a bug report by a respected member of the platform team (whether or not you knew he was the point person for the API); please respond to bug reports. People are busy and reviewing a lot of people's code and can't be on point to track everyone down all the time (seriously, if Platform had to do that, we'd never get anything else done).
+
+Please take some initiative and review your bugzilla tickets and ask for clarification where needed.",1390931011,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #15)
+> (In reply to comment #14)
+> > Bugzilla is how one files bugs against a product--sorry you don't like it.
+> > The
+> > nice thing is it's asynchronous so if someone is in a different timezone they
+> > can easily report issues without waiting for you to be around :)
+> 
+> Bugzilla is an excellent way to track bugs, but for solving problems nothing
+> beats communicating with a human being in real time.
+
+Indeed. But it's also good to file bugs because people are imperfect and can forget conversations they have :)
+
+> The foundation uses
+> real
+> time communication within teams extensively to organize and ensure the work
+> they want to get done happens.  Embrace the most effective forms of
+> communication you can.
+> 
+
+I know how the Foundation works...I work here too ;-)
+
+Is real time communication awesome? Sure. Is finding someone on IRC to chat about your problem sometimes faster than a bug? Absolutely.
+
+But you said:
+
+(In reply to comment #13)
+> Personally I find impersonal communication methods like bugzilla a passive
+> aggressive way to air issues without actually talking to anyone directly.  If
+> you had come into our irc room months ago and xommunicated in real time I
+> guarantee this bug would be in a different state.
+
+Regardless of your personal opinions about Bugzilla, it's where we file bugs about
+our software--all of it. It's completely reasonable to expect people to file bugs here, and they should be treated with just as much interest and care as things tracked in Mingle, Trello, or reported to the IRC ether.",1390930989,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #14)
+> Bugzilla is how one files bugs against a product--sorry you don't like it.
+> The
+> nice thing is it's asynchronous so if someone is in a different timezone they
+> can easily report issues without waiting for you to be around :)
+
+Bugzilla is an excellent way to track bugs, but for solving problems nothing beats communicating with a human being in real time.  The foundation uses real time communication within teams extensively to organize and ensure the work they want to get done happens.  Embrace the most effective forms of communication you can.
+
+Lucky for those in other timezones, we have team members in 2 american timezones, europe and australia.",1390930483,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #13)
+> (In reply to comment #12)
+> > (In reply to comment #10)
+> > > (In reply to comment #7)
+> > > > In the future, let's not rely on passive Bugzilla communication
+> > > > around things you feel are serious blockers; let's just talk to each other
+> > > > directly
+> > > 
+> > > In that case please document outcome as a comment in Bugzilla, so community
+> > > members can also be aware and provide input if they were not physically
+> > > around
+> > > in your office.
+> > 
+> > Personally, I find bugzilla works as well as email and IRC doesn't seem like
+> > it
+> > would have been that much of an improvement here.
+> > 
+> > No one besides me is around my office. ;)
+> 
+> Personally I find impersonal communication methods like bugzilla a passive
+> aggressive way to air issues without actually talking to anyone directly.  If
+> you had come into our irc room months ago and xommunicated in real time I
+> guarantee this bug would be in a different state.
+
+Bugzilla is how one files bugs against a product--sorry you don't like it. The nice thing is it's asynchronous so if someone is in a different timezone they can easily report issues without waiting for you to be around :)",1390929404,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #12)
+> (In reply to comment #10)
+> > (In reply to comment #7)
+> > > In the future, let's not rely on passive Bugzilla communication
+> > > around things you feel are serious blockers; let's just talk to each other
+> > > directly
+> > 
+> > In that case please document outcome as a comment in Bugzilla, so community
+> > members can also be aware and provide input if they were not physically
+> > around
+> > in your office.
+> 
+> Personally, I find bugzilla works as well as email and IRC doesn't seem like
+> it
+> would have been that much of an improvement here.
+> 
+> No one besides me is around my office. ;)
+
+Personally I find impersonal communication methods like bugzilla a passive aggressive way to air issues without actually talking to anyone directly.  If you had come into our irc room months ago and xommunicated in real time I guarantee this bug would be in a different state.",1390927052,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #10)
+> (In reply to comment #7)
+> > In the future, let's not rely on passive Bugzilla communication
+> > around things you feel are serious blockers; let's just talk to each other
+> > directly
+> 
+> In that case please document outcome as a comment in Bugzilla, so community
+> members can also be aware and provide input if they were not physically
+> around
+> in your office.
+
+Personally, I find bugzilla works as well as email and IRC doesn't seem like it would have been that much of an improvement here.
+
+No one besides me is around my office. ;)",1390862653,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #10)
+> (In reply to comment #7)
+> > In the future, let's not rely on passive Bugzilla communication
+> > around things you feel are serious blockers; let's just talk to each other
+> > directly
+> 
+> In that case please document outcome as a comment in Bugzilla, so community
+> members can also be aware and provide input if they were not physically
+> around
+> in your office.
+
+I think that's what Maryana just said she'd do. Indeed, it's what she just did :).",1390859479,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #7)
+> In the future, let's not rely on passive Bugzilla communication
+> around things you feel are serious blockers; let's just talk to each other
+> directly
+
+In that case please document outcome as a comment in Bugzilla, so community members can also be aware and provide input if they were not physically around in your office.",1390858246,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #8)
+> (In reply to comment #7)
+> > Putting Flow out there on a couple of real discussion spaces
+> > is
+> > the only way we're going to be able to get actionable feedback on the design
+> > and UI side. The sooner we start receiving this kind of feedback, the sooner
+> > we
+> > can prioritize our work on all the outstanding bugs, enhancements and feature
+> > requests, so we get the right features to the right users at the right time.
+> 
+> That sounds like the same reasoning they used when deploying VE to enwiki
+> with
+> known bugs unfixed. I think we all know how well *that* went.
+> 
+> I realize the proposed deployment of Flow to enwiki is somewhat different
+> since
+> it's a deployment to two rather out-of-the-way talk pages rather than being
+> enabled by default for everyone. But on the other hand, it's also that much
+> less likely to give you the sort of feedback you're hoping for. And certain
+> vocal community members will be on the defensive given the recent VE
+> situation,
+> ready to blast ""the WMF"" for doing the ""same"" thing again.
+> 
+Possibly. There are some community members who would find a way to take offence to ""how is your day going?"". I don't particularly think we should base our decisions around pandering to them.
+> 
+> (In reply to comment #7)
+> > I understand that your priorities as a platform engineer fall toward making
+> > sure our API is robust and well-documented.
+> 
+> I also want to avoid causing our volunteer community members to develop
+> towards
+> an API with known major flaws by pushing it on a production site before it's
+> ready. The test wikis and mediawiki.org, while in production, are still test
+> sites.",1390857650,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #7)
+> Putting Flow out there on a couple of real discussion spaces
+> is
+> the only way we're going to be able to get actionable feedback on the design
+> and UI side. The sooner we start receiving this kind of feedback, the sooner
+> we
+> can prioritize our work on all the outstanding bugs, enhancements and feature
+> requests, so we get the right features to the right users at the right time.
+
+That sounds like the same reasoning they used when deploying VE to enwiki with known bugs unfixed. I think we all know how well *that* went.
+
+I realize the proposed deployment of Flow to enwiki is somewhat different since it's a deployment to two rather out-of-the-way talk pages rather than being enabled by default for everyone. But on the other hand, it's also that much less likely to give you the sort of feedback you're hoping for. And certain vocal community members will be on the defensive given the recent VE situation, ready to blast ""the WMF"" for doing the ""same"" thing again.
+
+
+(In reply to comment #7)
+> I understand that your priorities as a platform engineer fall toward making
+> sure our API is robust and well-documented.
+
+I also want to avoid causing our volunteer community members to develop towards an API with known major flaws by pushing it on a production site before it's ready. The test wikis and mediawiki.org, while in production, are still test sites.",1390855001,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"Brad,
+
+We've chosen our first deployment to English Wikipedia with care. The reason Flow is only going live on the 2 discussion pages in question (Wikipedia_talk:Wikiproject_Breakfast and Wikipedia_talk:Wikiproject_Hampshire) is that those pages have zero bot activity, and relatively light human traffic, for that matter, skewing largely power user (e.g. no clueless n00bs who need to get smacked around by Cluebot). In my capacity as product owner, I felt completely comfortable deploying a beta trial of experimental software with an incomplete API to two pages where an API wouldn't be critically necessary for vital workflows, with the understanding that the next step after this deployment would be to reach out to bot operators, invite them to test aggressively on a developer test page, and work with them to make the API fulfill their needs. I apologize for not communicating all of this to you explicitly sooner; frankly, it was hard for me to ascertain whether this particular bug was more or less high-priority than your critiques of our use of whitespace. In the future, let's not rely on passive Bugzilla communication around things you feel are serious blockers; let's just talk to each other directly -- I don't bite :)
+
+I understand that your priorities as a platform engineer fall toward making sure our API is robust and well-documented. But please keep in mind that this project also involves significant design and UI components that are just as critical to the success of the overall mission (to replace talk pages entirely and create more universally-usable, stable software tools for all the processes they support). Putting Flow out there on a couple of real discussion spaces is the only way we're going to be able to get actionable feedback on the design and UI side. The sooner we start receiving this kind of feedback, the sooner we can prioritize our work on all the outstanding bugs, enhancements and feature requests, so we get the right features to the right users at the right time.",1390852535,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"Change 107411 had a related patch set uploaded by Legoktm:
+[WIP] Revamp API
+
+https://gerrit.wikimedia.org/r/107411",1390799392,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,Flow team: This was reported in November with pretty clear concerns. Brad is the current point of reason/arbitration for the API. Can you give a response to this as well? (On BZ not Mingle ;) ).,1390799329,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #3)
+> (In reply to comment #0)
+> > * The link returned by getHelpUrls() does not actually document this API
+> > module.
+> 
+> Removed in https://gerrit.wikimedia.org/r/#/c/102030/
+
+Good to get rid of the bad link. But list=flow does need a valid implementation of getHelpUrls(). I expect you already are aware of this, but the obvious bears stating.",1387292443,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"(In reply to comment #0)
+> * I note that ApiBase is already a ContextSource, so there is no need for
+> $this->getContext()->getUser() instead of just $this->getUser().
+
+https://gerrit.wikimedia.org/r/#/c/102046/
+
+> * The link returned by getHelpUrls() does not actually document this API
+> module.
+
+Removed in https://gerrit.wikimedia.org/r/#/c/102030/",1387240689,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"Marking as high priority, it gets much harder to change the API once something is deployed...",1386807456,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+Flow: API module issues,"**bingle-admin** wrote:
+
+The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/532, but people from the community are welcome to contribute here and in Gerrit.",1385566935,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yoiz5bs5xl4hztc6azyb,task_subcomment,NA
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,"Steps to reproduce:
+* Click on an image before a text node. The image will be marked as selected.
+* Press rightarrow to cursor next to the text.
+* Start typing. The text will be inserted backwards.
+
+Cause:
+After cursoring off the image, the selection is in the text node (and the cursor is flashing), but the focus is not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54917",1385483520,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-vxauebeaoyvfqdythyzt,task_description,resolved
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,"Change 97750 merged by jenkins-bot:
+Fix moving over an image with the arrow keys in Firefox
+
+https://gerrit.wikimedia.org/r/97750",1385495488,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vxauebeaoyvfqdythyzt,task_subcomment,NA
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,"Change 97750 had a related patch set uploaded by Catrope:
+Fix moving over an image with the arrow keys in Firefox
+
+https://gerrit.wikimedia.org/r/97750",1385485733,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vxauebeaoyvfqdythyzt,task_subcomment,NA
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,*** Bug 57347 has been marked as a duplicate of this bug. ***,1385484604,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vxauebeaoyvfqdythyzt,task_subcomment,NA
+VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox,"Change 97750 had a related patch set uploaded by Divec:
+Fix post-image selection bug
+
+https://gerrit.wikimedia.org/r/97750",1385483662,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vxauebeaoyvfqdythyzt,task_subcomment,NA
+VisualEditor: Annotate body tag or #content tag when in edit mode with class,"Other modules (and gadgets) should be able to hide their interfaces when VisualEditor is opened - for example the Nearby pages BetaFeature (https://www.mediawiki.org/wiki/Beta_Features/Nearby_Pages) creates a blue button in the top right.
+
+Ideally this feature should be able to know when it is in edit mode and hide itself.
+
+Maybe abusing the action-edit / action-view classes would be useful here?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385409780,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ralatlcjdkp2pb5sjaiy,task_description,resolved
+VisualEditor: Annotate body tag or #content tag when in edit mode with class,"Change 97702 merged by jenkins-bot:
+mw.ViewPageTarget: Use ve-activated class on the html element
+
+https://gerrit.wikimedia.org/r/97702",1385506336,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ralatlcjdkp2pb5sjaiy,task_subcomment,NA
+VisualEditor: Annotate body tag or #content tag when in edit mode with class,"Change 97702 had a related patch set uploaded by Robmoen:
+Toggle veaction-edit class on the body of the view page
+
+https://gerrit.wikimedia.org/r/97702",1385460063,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ralatlcjdkp2pb5sjaiy,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"Screenshot
+
+Steps to reproduce:
+
+1.Click on the Edit button in a page
+2.Select a text by dragging with mouse control.
+3.Change the heading format of the text to any format for example:heading/paragraph etc.
+
+Observed Result:
+The cursor moves to a position which is the middle of the first and second line of the page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58998
+
+**Attached**: {F12046}",1385407560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_description,resolved
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,*** Bug 60139 has been marked as a duplicate of this bug. ***,1394659271,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27thfebchrome&veaction=edit,1393533723,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"Change 115759 merged by jenkins-bot:
+Restore focus after node-destroying actions
+
+https://gerrit.wikimedia.org/r/115759",1393452937,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"Change 115759 had a related patch set uploaded by Esanders:
+Restore focus after node-destroying actions
+
+https://gerrit.wikimedia.org/r/115759",1393452124,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"This issue is still happening however I am changing the steps and observed result as follows:
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select any text with keyboard/mouse control/double click
+3.Change the heading format of the section to any format, for example:Preformatted/Sub-heading 1 etc.
+
+Observed Result:
+The cursor jumps to the beginning of the page.Now Type something on the first line or apply a format on the first line say ""Page title"", it actually adds the text in the text position of step 2 replacing replacing its previous content and style.",1393364053,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/ref_not_editable?veaction=edit",1385407634,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-22dxmk6w5i2gv5vgbjoj,task_subcomment,NA
+VisualEditor: MWExtensionInspector does not take directionality from context when creating,"https://gerrit.wikimedia.org/r/#/c/96984/ adds a workaround for the fact that getting the directionality from the FocusedNode doesn't work if there is no node focused (i.e. in creation mode), but it doesn't add any alternative logic for getting the directionality. We should look at the context in the CE tree somehow and figure out what directionality to use. Right now it just defaults to the UI directionality.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385125260,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-aljnlx2ibmppm5ov7vo7,task_description,resolved
+VisualEditor: MWExtensionInspector does not take directionality from context when creating,"Change 101125 merged by jenkins-bot:
+Add a getDirectionFromRange Method to ve.ce.Document
+
+https://gerrit.wikimedia.org/r/101125",1386966265,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aljnlx2ibmppm5ov7vo7,task_subcomment,NA
+VisualEditor: MWExtensionInspector does not take directionality from context when creating,"Change 101125 had a related patch set uploaded by Mooeypoo:
+Add a getDirectionFromRange Method to ve.ce.Document
+
+https://gerrit.wikimedia.org/r/101125",1386886808,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aljnlx2ibmppm5ov7vo7,task_subcomment,NA
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,"At the end of the first paragraph there is reference #1.
+If you scroll to the reference list, it will look empty.
+
+Actually, the reference, which can be edited, contains an unnamed link. 
+The markup guide for en.wp says these links are ""Only used within article body
+for footnotes"", so it makes sense that VE should display them correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Elitre_%28WMF%29/sandbox&veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57419",1385124180,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-j3t4kswoyrigddha43ep,task_description,resolved
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,"Change 97037 merged by jenkins-bot:
+Also apply autonumbering CSS to links in generated content
+
+https://gerrit.wikimedia.org/r/97037",1385496806,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-j3t4kswoyrigddha43ep,task_subcomment,NA
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,*** Bug 57209 has been marked as a duplicate of this bug. ***,1385374223,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j3t4kswoyrigddha43ep,task_subcomment,NA
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,"This happened because the numbered link was generated by a template (indirectly in this case: it was in the references list which was in turn generated by {{reflist}}), and the CSS we use to do the numbering didn't account for numbered links in templates.",1385140816,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-j3t4kswoyrigddha43ep,task_subcomment,NA
+VisualEditor: Auto-numbering CSS for external links should also apply to generated content,"Change 97037 had a related patch set uploaded by Catrope:
+Also apply autonumbering CSS to links in generated content
+
+https://gerrit.wikimedia.org/r/97037",1385140090,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-j3t4kswoyrigddha43ep,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,"**Author:** `swalling`
+
+**Description:**
+Screenshot from mediawiki.org
+
+The box that appears on hover around dropdown menu items overlaps with the text for the ""Switch to source editor"" option. (See attachment)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12471}",1385060520,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-t37b6rskig2gygqauzqe,task_description,resolved
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,Verified the fix in Production,1410545528,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 69707 has been marked as a duplicate of this bug. ***,1409892989,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,Verified the fix in Betalabs and test2,1409876520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,This bug got fixed with this change commit:https://gerrit.wikimedia.org/r/#/c/157295/,1409876443,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 70316 has been marked as a duplicate of this bug. ***,1409767558,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,"Created attachment 16280
+Screenshot of problem on master.
+
+It's worse now that the ""Cancel"" button is gone. The menu is even narrower now and more items are cut off. And the ""Switch to source text"" item is now actually cropped instead of just partially hanging outside the container.
+
+**Attached**: {F12472}",1409072441,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 69808 has been marked as a duplicate of this bug. ***,1408570728,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,"I believe this blocks bug 67340 (or at least, this being fixed would be useful there).",1406763651,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,@Krinkle: Ping. Any progress on this?,1406671445,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,Bumping priority now that the loss of the Cancel button makes this more acute.,1406320862,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 68483 has been marked as a duplicate of this bug. ***,1406156548,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,*** Bug 61149 has been marked as a duplicate of this bug. ***,1401743910,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Toolbar utilities menu items should not be cut off against browser edge,Merging in bug 61149 to this.,1401743896,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t37b6rskig2gygqauzqe,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,"**Author:** `Wikifram`
+
+**Description:**
+There are a number of bugs about pawns and/or reverse typing, many of them ""resolved fixed"". But it is clear that in many circumstances, on different wikiversions, pawn characters and reverse typing still occur. 
+
+See [[en:Wikipedia:VisualEditor/Feedback#Line with template, pawn]] (and the linked sections on fr-wiki as well) for an explanation of some scenarios when this occurs. This has, in various guises, been reported since the first deployment of VE, and none of the fixes seem to have been permanent or fundamental. Can this please be tackled?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1385030100,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-q5yeocuc7uzle4efdhw5,task_description,resolved
+VisualEditor: Pawning and reversed typing in Firefox,"Re-merged with bug 57600, as slightly distinct from bug 54917.
+
+*** This bug has been marked as a duplicate of bug 57600 ***",1385484604,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,"Merging into bug 54917 which is the same, yes.
+
+*** This bug has been marked as a duplicate of bug 54917 ***",1385472098,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,Possibly a dupe of https://bugzilla.wikimedia.org/show_bug.cgi?id=54917?,1385194254,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,"The above was related to templates (that is, a weird behavior when templates are selected and then deselected via keyboard arrows). The opposite happens when dealing with references.
+
+1. https://en.wikipedia.org/wiki/Selan_%28Dungeons_%26_Dragons%29?veaction=edit
+2. Put your cursor right after the first reference number ([1]).
+3. Arrow left.
+4. Arrow left.
+5. Start typing.
+
+You are typing backwards.
+
+Also:
+
+1. and 2. as above.
+3. Arrow left.
+4. Arrow right.
+5. Start typing.
+
+A pawn appears.",1385046939,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Pawning and reversed typing in Firefox,"In short (and partially reusing Fram's words).
+This happens in FF, in both MB and Vector.
+
+1. VEdit https://en.wikipedia.org/wiki/Selan_(Dungeons_%26_Dragons) .
+2. Put your cursor at the start of the text (i.e. before ""In the..."").
+3. Arrow left.
+4. Arrow left.
+5. Start typing.
+
+A pawn appears. 
+
+Also:
+
+1. and 2. as above.
+3. Arrow left.
+4. Arrow right (nothing happens; a bug in its own right?)
+5. Arrow right.
+6. Start typing.
+
+You are typing backwards.",1385046376,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-q5yeocuc7uzle4efdhw5,task_subcomment,NA
+VisualEditor: Change event reaction order,"The current event reaction order means that many IMEs including jQuery.IME and a number of Windows built-in input methods don't work in VE; we should change it to something that does – needs investigation as to what order is right.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1384939680,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pdqwezif4yyehpz3pomy,task_description,resolved
+VisualEditor: Change event reaction order,"IME support has improved markedly due to incrementally revamped event logic. Significant milestones included:
+
+https://gerrit.wikimedia.org/r/86688 - Selection change debounce
+https://gerrit.wikimedia.org/r/91786 - Fixup selection after rerender
+https://gerrit.wikimedia.org/r/105231 - Reduce refreshes
+https://gerrit.wikimedia.org/r/125937 - Unicorns
+https://gerrit.wikimedia.org/r/166188 - Poll refactor
+https://gerrit.wikimedia.org/r/179530 - Stable selections
+https://gerrit.wikimedia.org/r/177946 - Native left/rightarrow
+
+The basic way VE handles events is probably right now, given all the constraints of the browser environment and all the features of unicode/individual scripts that must be supported. Any unresolved dependent bugs can now be given a more specific diagnosis :-)",1424368837,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-pdqwezif4yyehpz3pomy,task_subcomment,NA
+VisualEditor: [Regression] References created in media item captions no longer appear in reference lists,"Regression of bug 52427.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384844400,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vcjosxhcqmpzxbjafscg,task_description,resolved
+VisualEditor: [Regression] References created in media item captions no longer appear in reference lists,Looks like this got fixed at some point because it works for me.,1413925579,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-vcjosxhcqmpzxbjafscg,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"Intention:
+Copyedit a page
+
+Steps to Reproduce:
+1. Open a page with pre-existing content.
+2. Type or change some of the text (I was adding a new first line).
+3. Select and cut (⌘ Command+x) some pre-existing text (I cut mine from the end of the third line).
+4. Notice that what you typed on the first line has been undone.
+5. Paste what you cut (in my case, at the end of the first line).
+6. Notice that what you typed on the first line has been redone.
+
+
+
+Expected Results:  
+That text would not magically disappear and reappear.
+
+Reproducible: Always
+
+I experienced this on office.wikipedia.org using Safari 6 on Mac OS 10.7.5.  It was confirmed at en.wikipedia.org using Vector/Chrome 30/Windows 7, with the additional discoveries that:
+
+If you type your new first line all in one go (so that 'undo' would remove the whole first line), the first character of the new line remains present.
+
+The undone text only reappears if you paste your cut text onto the line with the now-missing text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58724",1384818060,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-b5q6raassymzwkebamu6,task_description,resolved
+VisualEditor:  Cutting text undoes previous typing,Fixed at the same time as bug 58724.,1409345286,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"My computer is brand new, no custom shortcuts. Maybe VE is using a keyboard shortcut hack to make undo possible.",1408644567,PHID-USER-vj2bbc63joi46qr5a5nq,True,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"Whether it's impossible or not, it happens every time I use Command-X in Safari after closing a tab.  It only happens if ""Undo closed tab"" is listed in Safari's Edit menu as the action for undo/Command-Z.  It's bug 58724.",1408639497,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"(In reply to Mc128k from comment #1)
+> I have a similar issue that makes Safari reopen a closed tab, same with
+> cmd-x.
+> It doesn't happen immediately and in all cases though.
+
+I'm pretty sure it's impossible for VisualEditor to cause a browser to re-open a tab; you probably have a keyboard mapping clash or something similar?",1408637240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor:  Cutting text undoes previous typing,"I have a similar issue that makes Safari reopen a closed tab, same with cmd-x.
+It doesn't happen immediately and in all cases though.",1408613391,PHID-USER-vj2bbc63joi46qr5a5nq,True,PHID-TASK-b5q6raassymzwkebamu6,task_subcomment,NA
+VisualEditor: First character added to a blank dialog entry box (reference or caption) is mis-placed and never makes it into DM in Firefox,"With Vector in FF.
+Try to add a caption to an image:
+the words will be splitted on multiple lines, with the first letter being automatically placed on the second line, the other letters on the first one, and no ability to fix this.
+
+I understand that https://bugzilla.wikimedia.org/show_bug.cgi?id=38129 is coming but I thought I'd file this anyway.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384811940,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-56jj32rdepjfe2dxapzo,task_description,resolved
+VisualEditor: First character added to a blank dialog entry box (reference or caption) is mis-placed and never makes it into DM in Firefox,"This was fixed last week as part of our fix-up of how windows works, happily (or, at least, I think so – I can replicate on enwiki but not on MediaWiki.org).",1384923911,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-56jj32rdepjfe2dxapzo,task_subcomment,NA
+VisualEditor: First character added to a blank dialog entry box (reference or caption) is mis-placed and never makes it into DM in Firefox,It is.,1384815472,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-56jj32rdepjfe2dxapzo,task_subcomment,NA
+VisualEditor: First character added to a blank dialog entry box (reference or caption) is mis-placed and never makes it into DM in Firefox,"This is probably specific to Firefox.  I'm able to replicate this in Firefox 25 on a Mac, but not Safari 6.",1384815007,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-56jj32rdepjfe2dxapzo,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,"On desktop, as soon as the visual editor is loaded, the cursor is activated at the beginning of the page content. This doesn't happen in the mobile version.
+
+Clicking on the page content after the editor has loaded then has inconsistent behavior between browsers. In Firefox, clicking anywhere in the page content inserts the cursor at the beginning of the content. In Webkit browsers, it inserts the cursor at the click location.
+
+I believe that fixing the first problem will also fix the second problem in for free.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67389
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67390
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67399",1384765200,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-zcneabl26r5jk4uera2i,task_description,invalid
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,According to Juliusz this is on purpose as tablets require an actual tap to activate the virtual keyboard.,1405637552,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,"This is caused by code in MF, line 152 of VisualEditorOverlay.js:
+
+// for some reason the first time contenteditables are focused, focus
+// event doesn't fire if we don't blur them first
+this.$( '[contenteditable]' ).blur();
+
+The code was added to fix bug 61240.",1405200891,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,"(In reply to Ryan Kaldari from comment #2)
+> We would like to have this fixed before we push mobile VE to stable if
+> possible. Any update on it?
+
+… no? Bugs in VE/Mobile have been awaiting triage and action by the Mobile since this was agreed in 2012. We can have a look at it now, though.",1403728238,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,We would like to have this fixed before we push mobile VE to stable if possible. Any update on it?,1403728165,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements,This is in reference to Rob's prototype mobile visual editor. https://gerrit.wikimedia.org/r/#/c/93916/,1384842065,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-zcneabl26r5jk4uera2i,task_subcomment,NA
+Allow links in Flow topic titles,"When a topic title includes an internal link, the title should render as a working link in the topic header.
+
+This will use the edit summary parser.
+
+Examples: 
+The topic title is [[Foo]] -- it will render as Foo -- a link to the article page Foo.
+The topic title is [[Foo|Bar]] -- it will render as Bar -- a link to the article page Foo.
+~~The topic title is [http://foo.com Foo] -- it will render as Foo -- an external link to foo.com.~~ (We decided to use the edit summary parser, which does not support this.)
+
+NOTE #1: For posts, replies and edits to a post/reply -- in watchlist, recent changes and contributions, there will be a blue link that says Foo -- but this will NOT be a link to the article page Foo. It will be a link to the Topic:UUID. See screenshots below. 
+
+NOTE #2: In topic history, board history, watchlist, recent changes and contributions, when there is a change to the topic summary, or moderation actions, the topic title will be rendered as Foo, no link. 
+For example: created topic summary on Foo
+
+**Topic heading -- this should be a working link**
+{F250640}
+
+**Contributions** -- 
+For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+For editing the topic summary, the link should render as the title, not linked.
+
+{F250665}
+
+**Recent changes** --
+For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+For editing the topic summary, the link should render as the title, not linked.
+
+{F250670}
+
+**Watchlist** --
+For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+For editing the topic summary, the link should render as the title, not linked.
+
+{F250675}
+
+{F250677}
+
+**Board and Topic history** --
+For both post/reply/edit and editing the topic summary, the link should render as the title, not linked.
+
+{F250682}
+
+{F250686}
+
+See {T115910}.
+
+---
+
+previous version of the ticket: 
+
+Flow: Wikitext formatting (such as [[links]] and ''italics'') doesn't work in topic titles
+
+When you create a new Flow thread, there's a ""topic"" field. This topic field is analogous to the ""subject"" field in a wikitext talk page. The topic field currently cannot support wikitext.
+
+Example: http://ee-flow.wmflabs.org/w/index.php?title=Sandbox&workflow=0509a3b2518b34dffb6efa163e68c4ac&action=view
+
+Topic input: ""here's a new [[topic]]""
+
+Expected behavior: ""[[topic]]"" becomes an internal hyperlink
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: http://ee-flow.wmflabs.org/w/index.php?title=Sandbox&workflow=0509a3b2518b34dffb6efa163e68c4ac&action=view
+**See Also**:
+* {T23445}
+* {T59950}
+* Tech News posts to LQT pages converted to Flow: https://www.mediawiki.org/wiki/Topic:Siez4a3hsji86cay
+
+https://trello.com/c/bj3IZSE5/190-limited-wikitext-formatting-in-topic-titles",1384740180,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_description,resolved
+Allow links in Flow topic titles,">>! In T59153#1822120, @Etonkovidova wrote:
+> 4)
+>>Watchlist --
+>> For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+>> For editing the topic summary, the link should render as the title, not linked.
+> 
+> {F2993084}
+
+That looks like a bug: those brackets should not appear. I've filed {T120329} for this, so we can close this bug.",1449191233,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(This will be announced in Tech News the week after next, as there's no MediaWiki deployment next week.)",1448451190,PHID-USER-go2ym6ta2zn6ofdsrqnx,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Filed as a separate issue {T119537}
+
+- Have a title with a link in it
+- scroll up - the link exposes html code: 
+{F2993105}",1448388712,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Not sure if it's big enough to be in a separate issue: 
+
+- Have a title with a link in it
+- scroll up - the link exposes html code: 
+{F2993105}",1448062036,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Checked in betalabs according to specs. Please check below
+Talk:ET19 - the link in the title and in the Summary - [[Talk:ET1|ET1]] 
+1)
+> Topic heading -- this should be a working link
+ 
+{F2992994}
+
+2) The links to the topic ET1 are rendered as for the Recent changes - see below
+> Contributions -
+> For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+> For editing the topic summary, the link should render as the title, not linked.
+
+{F2993008}
+
+3) 
+>Recent changes --
+>For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+>For editing the topic summary, the link should render as the title, not linked.
+
+{F2993045}
+
+4)
+>Watchlist --
+> For the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.
+> For editing the topic summary, the link should render as the title, not linked.
+
+{F2993084}
+
+5)  Links are in the right place - checked.
+>Board and Topic history --
+> For both post/reply/edit and editing the topic summary, the link should render as the title, not linked.
+
+{F2993093}",1448061939,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Change 243066 merged by jenkins-bot:
+Add support for edit summary formatting in topic titles
+
+[[https://gerrit.wikimedia.org/r/243066]]",1447893298,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,See {T115910}.,1445280425,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Change 243066 had a related patch set uploaded (by Mattflaschen):
+WIP: Add support for edit summary formatting in topic titles
+
+[[https://gerrit.wikimedia.org/r/243066]]
+",1443744293,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,">>! In T59153#1439920, @Mattflaschen wrote:
+> We discussed the possibility of using the same subset the edit summary parser allows.
+
+That would be the least. You've already broken many topic titles:
+https://www.mediawiki.org/wiki/Talk:MediaWiki_Stakeholders%27_Group",1436983178,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,We discussed the possibility of using the same subset the edit summary parser allows.,1436403629,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"@DannyH https://trello.com/c/bj3IZSE5/190-limited-wikitext-formatting-in-topic-titles
+> We shouldn't do wikitext in topic titles -- titles will be used in log pages like contributions, watchlist, etc.
+Many wikis use titles with wikitext ""==[[PageInTitle]]==""  and special log pages showing simply ""PageInTitle"" and links [[ SomePage#PageInTitle ]] work fine. Why this can not further work so?
+
+",1434636335,PHID-USER-5joeladhczukimiv4rwl,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,Well it's very cool that at least one users and also users of languages who don't use formatting at all would survive. But as there are still lots of users who are not covered by that array I'd rather have wikimarkup allowed in there. We are not to force people to change their talk page editing style or even make them drop some features their language allows...,1431762837,PHID-USER-sscimmfqgfuh4pe2kfyw,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Mmmm... Page titles don't have wikitext formatting either and we survive. I never missed '''', [[]] or {{}} in page titles, although I wish I could write something <span lang=""en"" dir=""ltr"">(What's the Story?) Morning Glory</span> and <span lang=""en"" dir=""ltr"">C++</span> in a title of the respective Hebrew Wikipedia articles. But still, I survive (with {{DISPLAYTITLE}}).
+
+MediaWiki section headings can have links, and people do use them, but I have no idea why, because it is ugly, unnecessary, and untappable on mobile. This could probably be fixed in MobileFrontend, but I'd just disallow them. Italics could be useful in section headings, for book titles and such, but I could live with that, too. (DYK: It's specific to English and some other languages written in the Latin alphabet. Some languages don't actually use italics. And guess what, they survive.)
+
+And I could certainly survive without wiki syntax in Flow topic titles.",1427921803,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,Previous comments are from 2013. This task should be higher priority now.,1427517668,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Links in headers are definitely needed in final product! Links are often used on ""specialty pages"" like image workshops or administrators noticeboards to quickly give a link to the file/user in question (which/whom the whole topic is about).",1385597285,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #7)
+
+Thanks for the clarifications. :-)",1384920560,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #6)
+> (In reply to comment #5)
+> > With wikitext, it's sort of all or nothing; it would be a huge pain to
+> > disallow all wikitext except, say, italics. Of course, if anybody out there
+> > thinks it's easy, patches welcome ;)
+> 
+> This bug tracker keeps bugs open if patches are welcome. We'll just adjust
+> the
+> importance/priority to lowest/enhancement, I suppose.
+> 
+> For what it's worth, we implement partial parsers in weird places. Consider
+> edit summaries, which auto-link internal links, but don't auto-link external
+> links and magic links and don't allow formatting such as bold or italics. Not
+> that we really should continue this practice of creating new partial
+> parsers...
+> but it's certainly not unprecedented.
+> 
+> > Since this is just the MVP, I think it makes sense to keep things simple for
+> > now and just keep titles in plaintext.
+> 
+> The most valuable player? Sorry, I don't know what ""MVP"" means.
+> 
+""Minimum viable product"". Basically it's designed to be just complete enough that we can show it off without it falling over. An example would be Page Curation, where we deployed in a really, really unfinished form and then developed where people could see it.
+
+(actually, page curation is not the best example since it broke blocking for ~20 minutes, somehow. But.)
+
+Title linking may (heck, probably will) be necessary for the finished thing, but it's not necessary for the ""demo model""; while it'd be nice to have, I would rather we made the features we do have work.
+
+> > If there's a demonstrable need to have wikitext in titles that outweighs all
+> > the cons, it's something we can easily change.
+> 
+> Having watched the train wreck that was VisualEditor's deployment, I can that
+> it's often small 'features' like this that can potentially be a very big deal
+> to a wiki and its workflows. If you look at a process such as [[WP:RFPP]],
+> you
+> can see a half-dozen links in many headers, each of which correspond to
+> discrete units of work. I think attempting to de-wikify the topic title may
+> result in a lot of annoyed users.
+
+I agree it'll be a big deal, but this is the MVP; if there's a need, we can build it into the next release.",1384883007,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #5)
+> With wikitext, it's sort of all or nothing; it would be a huge pain to
+> disallow all wikitext except, say, italics. Of course, if anybody out there
+> thinks it's easy, patches welcome ;)
+
+This bug tracker keeps bugs open if patches are welcome. We'll just adjust the importance/priority to lowest/enhancement, I suppose.
+
+For what it's worth, we implement partial parsers in weird places. Consider edit summaries, which auto-link internal links, but don't auto-link external links and magic links and don't allow formatting such as bold or italics. Not that we really should continue this practice of creating new partial parsers... but it's certainly not unprecedented.
+
+> Since this is just the MVP, I think it makes sense to keep things simple for
+> now and just keep titles in plaintext.
+
+The most valuable player? Sorry, I don't know what ""MVP"" means.
+
+> If there's a demonstrable need to have wikitext in titles that outweighs all
+> the cons, it's something we can easily change.
+
+Having watched the train wreck that was VisualEditor's deployment, I can that it's often small 'features' like this that can potentially be a very big deal to a wiki and its workflows. If you look at a process such as [[WP:RFPP]], you can see a half-dozen links in many headers, each of which correspond to discrete units of work. I think attempting to de-wikify the topic title may result in a lot of annoyed users.",1384831495,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"With wikitext, it's sort of all or nothing; it would be a huge pain to disallow all wikitext except, say, italics. Of course, if anybody out there thinks it's easy, patches welcome ;)
+
+Since this is just the MVP, I think it makes sense to keep things simple for now and just keep titles in plaintext. If there's a demonstrable need to have wikitext in titles that outweighs all the cons, it's something we can easily change.",1384813132,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/471, but people from the community are welcome to contribute here and in Gerrit.",1384761822,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #1)
+> Wikitext is purposefully Plain text only. 
+
+s/Wikitext is/Topic-titles are/
+Sorry.
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > *Other?
+> > ** Is there any other wikitext that topic titles might need?
+> 
+> Magic words, covered by a separate bug. External links. Bold. Probably a
+> million other pieces of formatting.
+
+Bold is never (?) needed in topic titles. Unless there are foreign language projects that require it?
+
+External links will presumably follow whatever decision we arrive at with internal wikilinks.
+
+I'll ask the team to give more details, and potentially reconsider certain aspects (particularly italics).",1384745567,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"(In reply to comment #1)
+> ** Links generally shouldn't be in headers, because the bolded text makes it
+> harder for some people to see that the link is there.
+
+When I look at [[WP:AN]] and [[WP:AN/I]], I see many headers that contain links. When I look at [[User talk:Quiddity]] ([[Special:Permalink/581983546]]), I see headers containing italics and links. What are you talking about?
+ 
+> ** Plus it's generally counter to the (Enwiki) styleguides [[WP:LINKSTYLE]]
+> and [[WP:Header]].
+
+I'm not sure what you're talking about here. The style guidelines you're linking to obviously apply only to content, not to discussions. Flow is specifically focused on discussions (non-content). Your links seem completely irrelevant.
+
+> *Other?
+> ** Is there any other wikitext that topic titles might need?
+
+Magic words, covered by a separate bug. External links. Bold. Probably a million other pieces of formatting.",1384744852,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Allow links in Flow topic titles,"Wikitext is purposefully Plain text only. IIRC, these are the reasons why:
+
+*Links: 
+** Links generally shouldn't be in headers, because the bolded text makes it harder for some people to see that the link is there.
+** Plus it's generally counter to the (Enwiki) styleguides [[WP:LINKSTYLE]] and [[WP:Header]]. (Although, do any other projects make a standard practice of including links in section headers?)
+** Also ""editors who have their preferences set to edit sections by clicking on the header will not be able to click these links"" - [[Help:Section#Section_linking]]   (Although this might not apply to Flow)
+** Flow currently uses most of the topic-title as a clickable area to trigger the topic-collapse. This would conflict with wikilinks.
+
+*Italics:
+** I agree that this should be allowed. We need italics for proper formatting of things like media titles, court cases, etc, in Enwiki. ([[WP:ITALICS]])
+
+*Other?
+** Is there any other wikitext that topic titles might need?",1384744398,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-q6gvl4xwdjjg6spcmgi7,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"This isn't a VE bug but ...
+With google translate and chrome when you choose ""always translate"" and then hide the translate bar, the look and feel is really WP:en or WP:yourlanguage
+
+When you choose to contribute with VisualEditor, everything is translated : text, button, message but the little ""search"" in the research box.
+
+Then contributions in different language appear on WP:fr ex : https://fr.wikipedia.org/w/index.php?title=Acrosport&diff=prev&oldid=98352033
+
+A little change in text saves the all translated bloc.
+
+Maybe, the VE edit button should be block with a warning message or the text display for edition should block google translate (I don't know if it's possible) like textarea does.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Whiteboard**: aklapper-moreinfo",1384560300,PHID-USER-hhw22zfd2xzrsyc22lp5,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_description,resolved
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Change 200746 merged by jenkins-bot:
+Add class=""notranslate"" to prevent Chrome from translating the CE DOM
+
+[[https://gerrit.wikimedia.org/r/200746]]",1427750736,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Change 200746 had a related patch set uploaded (by Catrope):
+Add class=""notranslate"" to prevent Chrome from translating the CE DOM
+
+[[https://gerrit.wikimedia.org/r/200746]]
+",1427750311,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Roan's found a way to get Google Translate to be suppressed, which is awesome.",1427749597,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"BTW, I send feedback to Google Translate, requesting they ignore contenteditable areas. Probably not gonna make a difference, but you never know.",1427745864,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"I've nominated this task to Q3 blockers as it keeps damaging articles on frwiki, and I highly doubt that the snowmen are really added by google translate.
+
+https://fr.wikipedia.org/w/index.php?title=Ben_Bocquelet&diff=113382413&oldid=113108176
+https://fr.wikipedia.org/w/index.php?title=Jake_le_chien&diff=113382267&oldid=113253474
+https://fr.wikipedia.org/w/index.php?title=Miss_Rainicorne&diff=prev&oldid=113234436
+",1427744844,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"According to Drongou, this ""google problem"" would also explain that in the following edit, snowmen were added by VE to the text.
+I doubt that google translate adds snowmen to its translation, and its a recurrent problem with VE.
+
+https://fr.wikipedia.org/w/index.php?title=Touche_pas_%C3%A0_mon_pote&curid=5972689&diff=111575789&oldid=110714100",1423142463,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Unfortunately the only way to fix this is to add:
+
+  <meta name=""google"" content=""notranslate"" />
+
+to the <head> of every Wikipedia page, which is undesirable (not least because it would disable translate.google.com requests of the page, too). - See https://support.google.com/webmasters/answer/79812?hl=en
+
+I think the duty lies with Google to fix Chrome to not translate contentEditable elements. There doesn't appear to be anything we can do at Wikimedia to fix this.
+
+Marking as INVALID.",1384842276,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"With Chrome
+
+Go on a wiki with a language different of the language choosen in Chrome parameter
+
+For example, if Chrome language is english go on WP:fr
+
+For a registred account change the language in wiki preference to the language of the wiki (here français) because the button in english will block the chrome translate banner or do it on IP.
+
+Go on a WP:fr page
+The chrome translate banner appears; choose always translate and close the banner (not compulsory but better for the look and feel) 
+
+Go on VE (modifier button)
+
+Select the first word (just one word) of any paragraph. Do copy/paste. (copy the word on himself) Then save
+
+Then you get a paragraph in english in a french article.
+
+Because it's difficult to change a Chrome for french to a Chrome for english (Chrome doesn't want to forget he's in a french environment), I've done it on WP:en (in reverse, it will be difficult for you to do it on WP:en) https://en.wikipedia.org/w/index.php?title=User%3ADrongou%2FBug57124&diff=582266868&oldid=582266664",1384812313,PHID-USER-hhw22zfd2xzrsyc22lp5,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+Google Chrome's auto-translate of the contentEditable surface is very confusing for users,"Hi Drongou, 
+thanks for taking the time to report this!
+
+Please describe the actual problem, the expected outcome, and the exact steps to reproduce so somebody else could follow these steps. Also see https://www.mediawiki.org/wiki/How_to_report_a_bug . Thanks in advance!",1384785920,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-u7nbiznggvbdhjsuerpt,task_subcomment,NA
+VisualEditor: SurfaceObserver sets selection to start of document after closing reference dialog in Chrome,"1. Edit an existing reference or insert a new one
+2. When the dialog is closed, the reference is selected and a callout is displayed
+3. 200ms later the selection moves to the start of the document
+
+Somehow, for some reason, SurfaceObserver is ""fixing"" the selection here.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384381260,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qt6vdckmcwpnahubzp3f,task_description,resolved
+VisualEditor: SurfaceObserver sets selection to start of document after closing reference dialog in Chrome,"
+
+*** This bug has been marked as a duplicate of bug 58090 ***",1394659143,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qt6vdckmcwpnahubzp3f,task_subcomment,NA
+VisualEditor: SurfaceObserver sets selection to start of document after closing reference dialog in Chrome,"Happens on Chromium 25 but not on Firefox 24 (on my Ubuntu system).
+
+When the reference is inserted, the CE cursor gets reset to the start (as always happens with a ContentEditable when you change the content). But then the CE cursor updates the DM cursor, whereas it should happen the other way round.
+
+Evidence: Make SurfaceObserver.pollOnceInternal into a no-op, then right-cursor to a word and click Reference, Insert Reference. Then the CE cursor gets reset to the start of the document, whereas the DM cursor is still in the place where the reference appears.",1384396011,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-qt6vdckmcwpnahubzp3f,task_subcomment,NA
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,"reference icon after the selected text
+
+Steps to reproduce:
+
+1.Click on the edit button for a blank page
+2.Type a text on the first line
+3.Now type another text on the second line
+4.Add a template
+5.Select the second text in a way that it also selects the template
+6.Click on More>Reference 
+7.Add a reference
+
+
+[Note] This might not be the exact steps to reproduce , I am trying to figure out the correct steps.I will update the steps once I am sure.Still filing it to keep track.
+
+Observed Result:
+The reference note gets added in the middle of the template and the second line in a blank line.After that the editor gets unresponsive
+
+Also sometimes the reference icon gets added at the beginning of the first line
+
+See the screenshot attached.
+
+Browser:Chrome 26
+Environment:test 2
+OS: MAC OS X 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12555}",1384305720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_description,resolved
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,I cannot reproduce this bug anymore This got fixed couple of weeks ago.,1398451857,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_subcomment,NA
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,"Created attachment 13790
+case where reference gets added at the beginning of the text
+
+**Attached**: {F12557}",1384372015,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_subcomment,NA
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,"Confirming the steps to reproduce.
+Also, attaching the screenshots where a reference gets added at the beginning of the text",1384371955,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_subcomment,NA
+VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position,"Created attachment 13781
+Reference icon being added at the beginning of the text
+
+**Attached**: {F12556}",1384305800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7pt5q2e2t3vecx3vztw2,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"I thought it was Opera's fault,
+but tested this again today and it's not related to the browser you're using.
+It appears that when you edit as an unregistered user (on wikis which allow you to...) you'll always get an Edit conflict page when you try to save after you switched to wikitext.
+Tested on multiple wikis on both ns0 and ns2.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56767",1383991740,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_description,resolved
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,I think this is fixed now. If you notice any issues with it (easiest way to test right now is on beta) please reopen,1396640124,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Change 123795 merged by jenkins-bot:
+Fix order of start and base timestamps when switching to the wikitext editor
+
+https://gerrit.wikimedia.org/r/123795",1396639920,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Change 123795 had a related patch set uploaded by Alex Monk:
+Fix order of start and base timestamps when switching to the wikitext editor
+
+https://gerrit.wikimedia.org/r/123795",1396562980,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,Some of my confusion on this bug was caused by some extra ways MediaWiki can resolve edit conflicts which I hadn't properly taken into account when testing. It looks like swapping those values fixes this bug. Assigning this to me and bumping the milestone forward.,1396562790,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"So I think that:
+* A conflict is always detected when having switched from VE
+* Said conflict is suppressed when Revision::userWasLastToEdit is run for a logged in user, but if they're anonymous then it's not suppressed.",1396031922,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"I suspect this might have something to do with this code in ve.init.mw.Target.js:
+
+>'wpStarttime': this.baseTimeStamp,
+>'wpEdittime': this.startTimeStamp,
+
+Which seems a bit backwards to me...",1395963311,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Reported again on it.wp, I verified it on my sandbox there (http://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE?veaction=edit); I got the warning, then tried to save anyway, I apparently managed to but nothing appears in the history.",1389136587,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Change 95730 merged by jenkins-bot:
+Share code between conflict resolution and the edit source switch
+
+https://gerrit.wikimedia.org/r/95730",1385462537,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,"Change 95730 had a related patch set uploaded by Catrope:
+Share code between conflict resolution and the edit source switch
+
+https://gerrit.wikimedia.org/r/95730",1384754242,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP,(I wonder if https://bugzilla.wikimedia.org/show_bug.cgi?id=56849 is related?),1384205663,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fwj24igsgg2aqdhxz7wz,task_subcomment,NA
+VisualEditor: Indent and list-related icons' direction should depend on content dir and not GUI dir,"Right now, CSSJanus flips toolbar icons by their definitions, so an icon indent-ltr would automatically turn to indent-rtl when user GUI is set to RTL.
+
+However, the indent and list-related buttons don't depend on user GUI language but rather on the content language. If editing English content, the icon for ""increase indent"" should point from left to the right regardless of user GUI language, and the icon for ""decrease indent"" should point the other way.
+
+For a quick demo, see:
+https://www.mediawiki.org/wiki/User:Mooeypoo/IndentDemo?veaction=edit&setlang=he
+(Wiki language is English/LTR and GUI is Hebrew/RTL)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383965220,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-733eiwtp5o2tjyz7twh7,task_description,resolved
+VisualEditor: Indent and list-related icons' direction should depend on content dir and not GUI dir,This is fixed with this patch https://gerrit.wikimedia.org/r/#/c/95560/,1386782895,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-733eiwtp5o2tjyz7twh7,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"We would like to revert the fix for bug 39617.  That bug should have been fixed via the 'whitespace' CSS property.
+
+The 'fix' to bug 39617 caused Parsoid to begin creating dirty diffs (and failing its test suite) -- see https://gerrit.wikimedia.org/r/92978
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=39617",1383947760,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gays66miu6qia6yucqn2,task_description,resolved
+Newlines after </li> cause dirty diffs with Parsoid,This has since been fixed in core.,1404842267,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Change 94443 abandoned by Cscott:
+Revert ""Have list items occupy their own line"".
+
+Reason:
+Abandoned in favor of Ib7aa9449bbd994cb23b83b3f23cff944b1cddadf
+
+https://gerrit.wikimedia.org/r/94443",1402679936,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Change 134380 merged by jenkins-bot:
+Update list item newline handling to follow Parsoid's model
+
+https://gerrit.wikimedia.org/r/134380",1402337597,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Bartosz Dziewoński from comment #26)
+> (In reply to Gabriel Wicke from comment #25)
+> > PHP + tidy inserts newlines in the first case too, which is broken.
+> 
+> I'm pretty sure that this is the case only if Tidy is enabled, and that kind
+> of behavior is one of the many reasons why I want to kill it. (I really do
+> not know why no one from the Parsoid team shares my sentiment about this.)
+
+Believe me, we want to kill it just as much as you do. And we have been working hard on it for 2+ years now.",1400604941,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Change 134380 had a related patch set uploaded by GWicke:
+Update list item newline handling to follow Parsoid's model
+
+https://gerrit.wikimedia.org/r/134380",1400602936,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Gabriel Wicke from comment #25)
+> PHP + tidy inserts newlines in the first case too, which is broken.
+
+I'm pretty sure that this is the case only if Tidy is enabled, and that kind of behavior is one of the many reasons why I want to kill it. (I really do not know why no one from the Parsoid team shares my sentiment about this.)",1393027687,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Parsoid does not insert newlines where there are none:
+
+<ul><li>foo</li><li>bar</li></ul>
+
+in wikitext becomes 
+
+<ul><li>foo</li><li>bar</li></ul>
+
+It does preserve newlines from wikitext though:
+
+* foo 
+* bar
+* baz
+
+in wikitext becomes
+
+<ul><li> foo</li>
+<li> bar</li>
+<li> baz</li></ul>
+
+PHP + tidy inserts newlines in the first case too, which is broken.",1393026536,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Sorry, but it isn't. The *old* PHP parser output is:
+
+<ul><li>a
+</li><li>b
+</li><li>c
+</li></ul>
+
+No linebreak *between* list items. Parsoid goes (if I understand above correctly):
+
+<ul><li>a</li>
+<li>b</li>
+<li>c</li></ul>
+
+I want the PHP parser to behave the smae.",1392995324,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Erwin Dokter from comment #22)
+> Ah, so it is only the *tests* that are affected. I think I understand now.
+
+Not just tests. See part (2) in Comment 16.
+
+> Still my question remains: can I make the parser make a clean break *only*
+> between </li> and <li> (as that is the core issue affecting nowrap), without
+> any linebreak before or after <ul> and </ul>?
+
+That is already the case since wikitext has newlines between list items. See below for Parsoid's output.
+
+[subbu@earth tests] echo ""*a\n*b\n*c"" | node parse
+<body data-parsoid='{""dsr"":[0,9,0,0]}'><ul data-parsoid='{""dsr"":[0,8,0,0]}'><li data-parsoid='{""dsr"":[0,2,1,0]}'>a</li>
+<li data-parsoid='{""dsr"":[3,5,1,0]}'>b</li>
+<li data-parsoid='{""dsr"":[6,8,1,0]}'>c</li></ul>
+</body>",1392963187,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Ah, so it is only the *tests* that are affected. I think I understand now.
+
+Still my question remains: can I make the parser make a clean break *only* between </li> and <li> (as that is the core issue affecting nowrap), without any linebreak before or after <ul> and </ul>?",1392940301,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Erwin Dokter from comment #20)
+> OK, this discussion is not going to end in the next couple of hundred years,
+> partly because I will never understand what is really going on. 
+
+Do you want to pop onto IRC (#mediawiki-parsoid) sometime and chat with us about this? We can then post the summary here after that. It might be simpler to figure this out in a more interactive discussion than is possible via bugzilla comments. I am going to be signing off for the day shortly, but the IRC channel is usually active between 9 am PST - 4 pm PST when most of us are around.
+
+> I still
+> don't know where parsoid is getting its HTML from. Can't be from the browser
+> DOM; that has gone through Tidy. 
+
+No, Parsoid generates the HTML as I indicated in Comment 16. In the case of Visual Editor use, VE then sends that HTML (alongwith any user edits) to Parsoid to convert back to wikitext.
+
+Since Parsoid HTML will replace PHP parser HTML at some point in the foreseeable future (this year possibly), if anything requires these newlines to be present for functionality, Parsoid will also have to add them and that is what we are complaining about so far.",1392939729,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"OK, this discussion is not going to end in the next couple of hundred years, partly because I will never understand what is really going on. I still don't know where parsoid is getting its HTML from. Can't be from the browser DOM; that has gone through Tidy. 
+
+Revert the patch.
+
+I just want the parser (as long as it lasts) to emit some sanely formatted lists, just as it outputs sanely formatted tables. Is that too much to ask?
+
+If I can make the parser to make a clean break *only* between </li> and <li>, without any linebreak before or after <ul> and </ul>, would that make parsoid happy?",1392937940,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Erwin Dokter from comment #18)
+> * block level elements (including list itema) must be terminated with e
+> newline
+> * all other (inline) elements should not
+> 
+> Would that ease the situation?
+
+This would in fact complicate the situation. We don't insert newlines in HTML where there were none in the original wikitext. This preserves the semantics independent of the CSS whitespace styling (remember that 'pre' is a possible value) and helps us to round-trip wikitext correctly without introducing spurious newlines.
+
+As discussed in bug 39617, the newlines don't seem to be necessary any more now that the nowrap requirement is gone. Taking into account the cost they have for Parsoid development, I'd recommend removing the code that inserts them from the PHP parser.",1392936264,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Re: ""a\n\n*b""
+
+I don't understand where the extra newline comes from, as the parser outputs only one. Regardless... perhaps we need to go about this another way.
+
+There should be a simple set of rules that govern how parser and parsoid interact, for example:
+
+* block level elements (including list itema) must be terminated with e newline
+* all other (inline) elements should not
+
+Would that ease the situation?",1392930092,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to Erwin Dokter from comment #15)
+
+> I can't help but feel that this issue is a major blocker for any parser
+> improvement in the future, so I want to understand exactly where the problem
+> exists and come up with a solution that will prevent such issues in the
+> future.
+
+This is not a general blocker. Parser changes can be done and have been done, but changes have to be considered carefully since there are a lot of dependent users, and that is what you are seeing here in this bug report discussion.",1392928973,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Parsoid converts wikitext to HTML and back. Tidy does not enter the picture at all in the Parsoid pipeline.
+
+There are two separate issues:
+
+1. Parsoid uses the same set of PHP parser tests to make sure that Parsoid generates HTML that doesn't break existing wikitext. It uses PHP HTML to serialize back to wikitext. The extra newline that PHP parser emits introduces extra newlines in wikitext. ""a\n\n*b"" instead of ""a\n*b"". So, the extra newline is a ""dirty diff"". This now obscures our regular testing because we blacklist these failing tests and then try to compare changes in HTML output. So, not entirely unworkable, but requires greater diligence to monitor regressions during development. Ideally, we wouldn't have these failures. Alternatively, we have to fix Parsoid's HTML to wikitext conversion to ignore the extra newlines when they come from the parser's insertion rather than from source -- that means extra bookkeeping.
+
+2. If you want Parsoid HTML to have the same CSS semantics like PHP HTML, Parsoid would also have to start adding these newlines after <ul> and before </ul>. These extra newline characters would now have to be accounted for in the DSR calculations (DSR maps a range to wikitext source to a DOM subtree, ex: wikitext substring [3,9] generate <p>foobar</p> HTML) which is also additional bookkeeping. DSR calculations has been carefully tweaked to account for every single character of wikitext so that Parsoid can faithfully output original wikitext on unedited portions of the HTML. So, Parsoid would have to ignore the extra inserted newlines in its calculations. Without accounting for them, Parsoid will generate different wikitext on conversion which manifests as ""dirty diffs"". Again, all of this extra bookkeeping can be done.
+
+But, if we can avoid the extra newlines, the extra work can be avoided.",1392928746,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"I also have a problem understanding 'dirty diffs'. Where does parsoid get its HTML from? I thought it converted wikitext to HTML and then back. So how does the parser even come into play? Is Tidy also involved? Sorry to ask al this, but I simply need a basic understanding of parsoid.
+
+FYI, the nowrap has been completely removed from hlist, so there are no CSS hacks to deal with. But any locally applied nowrap may cause errors, so the linebreaks must remain.
+
+I can't help but feel that this issue is a major blocker for any parser improvement in the future, so I want to understand exactly where the problem exists and come up with a solution that will prevent such issues in the future.",1392897145,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,That is a scoping problem; Tidy should simply not touch anything that comes out of GeSHi (pre & code). This is simply two external extentions clashing.,1384007212,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Just to guide the discussion, let's try to keep this bug concentrated on the parsertest regressions in Parsoid and other extensions, and possible fixes for that.  Discussion of the hlist issue and the CSS fix (or lack thereof) goes over on bug 39617.
+
+Since most of the discussion has already happened on bug 39617, I'd say that, if in doubt, let's continue the discussion there.  I'm just trying to prevent the discussion from being scattered across gerrit and a bunch of different bugzilla items, and people's good points being lost in the shuffle. (In particular, I'm going to copy comment 10 over to bug 39617.)",1384007129,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to comment #11)
+> (In reply to bug 39617 comment #27)
+> > The Tidy bug is what caused hlists to work in the first place, according to
+> > what you're saying :)
+> 
+> Why is that even considered a bug? list items are block level elements, and
+> as such, should be on their own line per unwritten code style conventions.
+
+Tidy's overzealous newline insertion has caused problems in the past already, see bug 260 (which is still open only because of the same Tidy issue) and bug 38800 (which is basically what Gabriel reported).",1384005116,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to comment bug:39617#27)
+> The Tidy bug is what caused hlists to work in the first place, according to
+> what you're saying :)
+
+Why is that even considered a bug? list items are block level elements, and as such, should be on their own line per unwritten code style conventions.",1384004546,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"https://test.wikipedia.org/wiki/MediaWiki:Common.css contain current CSS for hlist.
+https://test.wikipedia.org/wiki/User:Edokter/sandbox contains the test cases.
+
+Any suggested changes will break one or more testcases.",1384004374,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to comment #8)
+> Unless you come up with a working CSS solution (which I doubt you will), I
+> insist my patch be reinstated and Parsoid be fixed instead.
+
+(Just a note that the patch was not reverted, but a revert has been submitted for review / consideration.)
+
+Is there a demo of hlist set up somewhere? Or a list of things it does, and a list of cases it supports? Any of these things would be very useful here.",1384000050,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Oh for crying...! Please provide a COMPLETE working set of CSS for horizontal lists that supposedly fixes all the bugs I have spent TWO YEARS trying to fix! I have tested EVERY scenario, including inline-block, which breaks nested lists in *ALL* browsers.
+
+Unless you come up with a working CSS solution (which I doubt you will), I insist my patch be reinstated and Parsoid be fixed instead.",1383992105,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"(In reply to comment #5)
+> I've already seen the patch and sadly it is not telling me anything. What
+> does
+> a ""dirty diff"" mean here? A dirty diff during after editing a page with
+> VisualEditor? Because that's the only significant definition I know.
+
+Parsoid is failing the parser tests in html2wt and html2html mode since the same parser tests are used by core and Parsoid. I blacklisted the failures for now. But this blacklisting is not ideal since we have to be a bit more careful about failures in the future when inspecting changes.
+
+That aside, if VE and Parsoid emits the same HTML that the core parser does for lists (emitting newlines around <ul> tags), then we have to deal with it.",1383953982,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Also, see https://gerrit.wikimedia.org/r/#/c/93626/ where I started messing with Parsoid to prevent these dirty diffs, but it seems a lot more pain than worth it currently -- it is mostly a distraction from other critical issues that I just left it in WIP stage. This wont be an issue in production necessarily right now, but if the CSS fix is not employed, then Parsoid will also have to emit the same kind of HTML that the core php parser emits and then this could be an issue in production with occasional dirty diffs without this WIP patch being worked out to completion. So, seems like a lot of pain for unclear benefit.",1383953825,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"I've already seen the patch and sadly it is not telling me anything. What does a ""dirty diff"" mean here? A dirty diff during after editing a page with VisualEditor? Because that's the only significant definition I know.",1383953741,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Matma(In reply to comment #3)
+> Why does this cause dirty diffs? Can I get a link to such diff?
+
+See the gerrit patch cscott linked to in the bug description (https://bugzilla.wikimedia.org/show_bug.cgi?id=56809#c0)",1383953535,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,Why does this cause dirty diffs? Can I get a link to such diff?,1383952668,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,https://bugzilla.wikimedia.org/show_bug.cgi?id=39617#c18 demonstrates a css fix. Related comment is https://bugzilla.wikimedia.org/show_bug.cgi?id=39617#c17,1383950334,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+Newlines after </li> cause dirty diffs with Parsoid,"Change 94443 had a related patch set uploaded by Cscott:
+Revert ""Have list items occupy their own line""
+
+https://gerrit.wikimedia.org/r/94443",1383949214,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gays66miu6qia6yucqn2,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Misplaced
+
+Steps to reproduce
+
+1. Click on the Edit button for an article or click on the media icon on a image
+2. Type something
+3. Go to some other window of your browser
+4.Come back to the editor after few minutes (approx. 5-10 minutes)
+5.Now select the text and click on the link icon 
+
+Observed Result:
+The link inspector appears broken or misplaced 
+
+
+
+Browser:Chrome
+Environment:test2
+Page:Any
+Reproducible: Mostly  
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12157}",1383942000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_description,declined
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,This appears to now be fixed FWICS; closing as such.,1398720912,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,Other inspectors (e.g. MWExtensionInspector) are affected as well.,1394745744,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Created attachment 14014
+reproduced on 6th december
+
+**Attached**: {F12162}",1386366426,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Reproduced it again on Betalabs:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=6th_december&veaction=edit
+
+See the screenshot attached",1386366371,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,This issue is fixed now and verified on betalabs,1386115278,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,should this have blocked deployment?,1385503716,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Yes, the issue reported here is now appearing in production/Live environment for any page.
+
+(In reply to comment #5)
+> (In reply to comment #4)
+> > Now it is live.
+> 
+> ????  You mean the problem in this bug report is deployed to production
+> servers
+> now, or how to interpret that comment?",1385404312,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"(In reply to comment #4)
+> Now it is live.
+
+????  You mean the problem in this bug report is deployed to production servers now, or how to interpret that comment?",1385133843,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,Now it is live.,1385073357,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Created attachment 13742
+Broken UI 2
+
+**Attached**: {F12161}",1383942104,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Created attachment 13741
+Broken UI
+
+**Attached**: {F12160}",1383942074,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window,"Created attachment 13740
+Broken
+
+**Attached**: {F12159}",1383942046,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dncrsb6dk5scs5lfx2nt,task_subcomment,NA
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,"Currently, if I go to https://www.mediawiki.org/wiki/User:Amire80/ve-poem and edit it using VE, I can edit the content of the <poem> tag. If my UI language is Hebrew, then the <textarea> for editing the poem is RTL. I would expect it to be LTR.
+
+Ideally the default direction for the <textarea> that this feature should be the direction of the surrounding text. If it's hard to get, then the direction of the page's content will probably suffice. (Currently it will be the same as the content language of the wiki, but it may change some day when we finally introduce page language.)
+
+There can also be some tags for which the default direction must be different, such as <source>, but that's an issue for a separate bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383920040,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-kuprsa4m7ibn5pvxkone,task_description,resolved
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,"Change 94375 merged by jenkins-bot:
+MWExtensionInspector input direction based on content
+
+https://gerrit.wikimedia.org/r/94375",1383939000,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kuprsa4m7ibn5pvxkone,task_subcomment,NA
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,"Change 94375 had a related patch set uploaded by Mooeypoo:
+MWExtensionInspector input direction based on content
+
+https://gerrit.wikimedia.org/r/94375",1383926174,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kuprsa4m7ibn5pvxkone,task_subcomment,NA
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,Related: Bug 56780.,1383920880,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-kuprsa4m7ibn5pvxkone,task_subcomment,NA
+VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction,"From IRC:
+
+<mooeypoo>	what do you mean ""must correspond to surrounding content direction?
+<mooeypoo>	of the <poem> ?
+<mooeypoo>	so, it should be content direction rather than GUI direction?
+<aharoni>	mooeypoo: It definitely shouldn't be the GUI direction. It has nothing to do with it.
+<mooeypoo>	nods
+<aharoni>	The direction of the inspector's GUI should be the GUI direction,
+<aharoni>	but the textarea needs the direction of the content.
+<mooeypoo>	yeah
+<mooeypoo>	makes sense, just wanted to make sure
+<aharoni>	Ideally, if the wiki is in English, but it's a <poem> tag inside <div lang=""fa"" dir=""rtl"">, then the textarea should be rtl.",1383920584,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-kuprsa4m7ibn5pvxkone,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"There are 2 users at least (Fram and myself)
+reporting that the new option does not seem to work when using FF (in our case, version 25).
+I tried to VEdit my sandboxes in several languages.
+You can use https://it.wikipedia.org/wiki/Utente:Elitre/Sandbox?veaction=edit if you need to.
+After you click on the Switch button, and click OK on the warning message, the surfaces is ""grayed out"", and just stays that way without actually switching.
+Please notice you can still VEdit at this time, and even save.
+The chosen skin instead does not seem to matter (it didn't work for me with any of them).
+
+In Fram's words:
+<< I get the ""you are about to change"" message, but then the VE page gets ""bleached"" out, as if an opaque glass is put in front of it, and nothing further happens. I can still use the toolbox at this time, and can edit the article in VE, but it doesn't have the normal look.>>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56835",1383909600,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_description,resolved
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94595 abandoned by Jforrester:
+Fix edit source switch in Firefox
+
+Reason:
+Not done.
+
+https://gerrit.wikimedia.org/r/94595",1384864407,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94594 abandoned by Jforrester:
+Fix edit source switch in Firefox
+
+Reason:
+Not done.
+
+https://gerrit.wikimedia.org/r/94594",1384864394,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94595 had a related patch set uploaded by Jforrester:
+Fix edit source switch in Firefox
+
+https://gerrit.wikimedia.org/r/94595",1384069041,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94594 had a related patch set uploaded by Jforrester:
+Fix edit source switch in Firefox
+
+https://gerrit.wikimedia.org/r/94594",1384069020,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94498 merged by jenkins-bot:
+Fix edit source switch in Firefox
+
+https://gerrit.wikimedia.org/r/94498",1384047723,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Change 94498 had a related patch set uploaded by Esanders:
+Fix edit source switch in Firefox
+
+https://gerrit.wikimedia.org/r/94498",1384001125,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"(Your wish is my command.
+See 56835 now, turns out it had nothing to do with Opera after all.)",1383991856,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"Dropping the Opera issue, as that appears unrelated. Open as a different bug?",1383948094,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+VisualEditor: Switch to wikitext feature does not return in Firefox,"FYI, I tried to VEdit a few sandboxes while unlogged with Opera.
+After switching to wikitext, when I try to save changes I always get an ""edit conflict"" notice. It will save if I re-add my text, but clearly this is not optimal :)",1383912386,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ok33eixi5ajoi2xq4y5b,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"beta commons localStorage nearly full
+
+seen on beta labs while logged in as Selenium_user
+seen in Chrome/Chromium, not checked in Firefox (yet)
+
+consistent behavior seen:  
+initial load of VisualEditor in beta enwiki sets localStorage to 3.5MB
+initial load of UploadWizard in beta commons sets localStorage to 2.5MB
+
+routine navigation to pages like 
+* wikitext editor
+* Flow e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA
+* Special:NewPagesFeed
+* etc
+
+continues to fill localStorage until it maxes out.
+
+inconsistent behavior: 
+
+I do not have a consistent repro to max out localStorage.  at first I thought that repeatedly hitting shift-reload/cancel on a ?veaction=edit page did it, but on my second attempt I was unable to max out localStorage that way
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56778
+
+**Attached**: {F12036}",1383847740,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_description,duplicate
+localStorage nearly or totally filled with routine operation,"(In reply to comment #9)
+> (In reply to comment #8)
+> > (In reply to comment #7)
+> > > My suspicion is that the mtimes of modules is being continuously changed
+> > > because of the way [beta] is set up.
+> > 
+> > Doesn't appear to be the case. I hacked up a quick script to check:
+> > <https://gist.github.com/atdt/7359920>. No changes were merged to master
+> > while
+> > I tested, though; still interested to know what happens then.
+> 
+> And BTW, if you do find config differences between beta enwiki and prod,
+> please
+> let me know.  I have other intermittent/unreproduceable performance problems
+> with Chrome (not Firefox) there that are becoming quite frustrating, seen in
+> particular in VE and UploadWizard.  I worry that these problems exist in
+> production but are so flaky that they are not reported.
+
+modules are updating pretty frequently on beta. 20 mins' worth here: <https://gist.github.com/atdt/7359920#file-rl-mon-log>. I'm running it again now *with* timestamps.",1383852748,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"(In reply to comment #8)
+> (In reply to comment #7)
+> > My suspicion is that the mtimes of modules is being continuously changed
+> > because of the way [beta] is set up.
+> 
+> Doesn't appear to be the case. I hacked up a quick script to check:
+> <https://gist.github.com/atdt/7359920>. No changes were merged to master
+> while
+> I tested, though; still interested to know what happens then.
+
+And BTW, if you do find config differences between beta enwiki and prod, please let me know.  I have other intermittent/unreproduceable performance problems with Chrome (not Firefox) there that are becoming quite frustrating, seen in particular in VE and UploadWizard.  I worry that these problems exist in production but are so flaky that they are not reported.",1383850834,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"(In reply to comment #7)
+> My suspicion is that the mtimes of modules is being continuously changed
+> because of the way [beta] is set up.
+
+Doesn't appear to be the case. I hacked up a quick script to check: <https://gist.github.com/atdt/7359920>. No changes were merged to master while I tested, though; still interested to know what happens then.",1383850574,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"Several points:
+- Can you isolate the size of the module storage? You can check it by running mw.loader.inspect('store') in a JavaScript console. (See 'totalSize' column).
+- Pruning old modules from the cache is deferred until the page / DOM is quiescent. What happens if you just let the page load and hang out for 5-10 seconds?
+- Is this reproducible outside the beta cluster? My suspicion is that the mtimes of modules is being continuously changed because of the way it is set up. Haven't investigated yet, but the way to check would be to load the startup module and compare module versions across reloads.",1383849242,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"Well, the limit can be worked around… 
+
+""Introducing the HTML5 Hard Disk Filler™ API"" http://feross.org/fill-disk/
+
+:P",1383848898,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"So apparently the only way to find the limit is to keep adding data until you fill it up. Awesome.
+
+http://dev-test.nemikor.com/web-storage/support-test/
+
+^ looks like a frequent limit is 5MB, which in some browsers means 2.5M *UTF-16 code points*. That's going to be pretty tight for the amount of code we want to store. :(",1383848334,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"(In reply to comment #3)
+> Can we determine the limits of available localStorage in some consistent way?
+
+I believe it is per-browser.  Empirically I found that my Chromium allows 5MB while my Chrome allows 10MB. 
+
+See http://arty.name/localstorage.html (warning: fills up your local storage upon loading the page and gives you a status message when done)",1383848242,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,Can we determine the limits of available localStorage in some consistent way?,1383847924,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"Comment on attachment 13721
+beta commons localStorage nearly full
+
+I meant beta enwiki for this attachment",1383847860,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+localStorage nearly or totally filled with routine operation,"Created attachment 13722
+beta commons localStorage after loading UploadWizard
+
+**Attached**: {F12037}",1383847809,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-zjh7rxbyat4v4fiw75ul,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"For some reason, the 'keydown' event is being unbound when the suggestions popup appears, so the function is never firing. However, it seems like they shouldn't be listening to keydown anyway because they only care about when the enter key is pressed and that event is already available on the input as the 'enter' event (from OO.ui.TextInputWidget).
+
+With love from the Wikia development team.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1383782580,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_description,declined
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"(In reply to Krinkle from comment #4)
+> There is still a tech debt here though, we should use OOjs UI's ""enter"" event 
+> (instead of manually binding keypress
+
+Done in Ia47bc8976f22dfe7e3a6fb6068dc4b6e03a3357b.",1412973553,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"Nevermind. They all work fine now. There is still a tech debt here though, we should use OOjs UI's ""enter"" event (instead of manually binding keypress and looking for keyCode=13), but it works fine.",1412973234,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"The handler from MWCategoryWidget is working fine. However, here is the code I used for comment #2
+
+In ve/ui/MWCategoryWidget.js:
+
+	this.input.$input.on( 'keypress', function () {
+		console.log( ['MWCategoryWidget', 'MWCategoryInputWidget', '$input', 'keypress'] );
+	} );
+	this.input.on( 'enter', function () {
+		console.log( ['MWCategoryWidget', 'MWCategoryInputWidget', 'enter'] );
+	} );
+
+And the 'enter' event never fired. Because there is still a mystery here. The event bound by OO.ui.TextInputWidget on $input for 'keypress' (which fires 'enter') disappears somehow.
+
+Putting the same logger in there makes it never fire.",1412972772,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"Created attachment 16743
+Screenshot of bug not happening.
+
+I can't reproduce this. When typing in the input, I see all keydowns happening as they should. From the key codes in the screenshot:
+* [shift]
+* E
+* x
+* a
+* m
+* p
+* l
+* e
+* [enter]
+
+**Attached**: {F12000}",1412971168,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything,"<Krenair> Krinkle, http://imgur.com/a39IuMk - that's handlers, handlers.length, handleObj
+<Krenair> Immediately after handlers.push( handleObj ); in jquery.event.add
+
+handlers.push( handleObj );
+if ( types.indexOf( 'keydown' ) !== -1 ) {
+	console.log( handlers );
+	console.log( handlers.length );
+	console.log( handleObj );
+}",1404762874,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-yyi4jvalwcv5dpoi7ztd,task_subcomment,NA
+VisualEditor in Flow: CE arrives much later than controls,"this may be more appropriate to assign to VisualEditor than Flow:
+
+in a fresh instance of the Chrome browser, log in and go to page http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA 
+
+* click Start a new topic
+* watch the spinner as VisualEditor loads up
+* when the spinner stops and the editor controls are visible, attempt to type in the ContentEditable surface
+
+* only some seconds after the spinner stops and the controls appear is it possible to place the cursor in the CE surface and begin typing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383754500,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-hic2xcoiiq7ialvw5olf,task_description,invalid
+VisualEditor in Flow: CE arrives much later than controls,"(In reply to comment #3)
+> (In reply to comment #2)
+> > Flow no longer supports VE
+> 
+> Eep!
+
+Clarification; the model as deployed on production intentionally does not support VE until we have some breathing room for it ;p",1387247486,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-hic2xcoiiq7ialvw5olf,task_subcomment,NA
+VisualEditor in Flow: CE arrives much later than controls,"(In reply to comment #2)
+> Flow no longer supports VE
+
+Eep!",1387247422,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hic2xcoiiq7ialvw5olf,task_subcomment,NA
+VisualEditor in Flow: CE arrives much later than controls,Flow no longer supports VE,1386881313,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-hic2xcoiiq7ialvw5olf,task_subcomment,NA
+VisualEditor in Flow: CE arrives much later than controls,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/409, but people from the community are welcome to contribute here and in Gerrit.",1383805182,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-hic2xcoiiq7ialvw5olf,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"Link inspector and Math inspector together
+
+Steps to reproduce:
+
+1.Click on the Edit beta
+2.Add a media such as image
+3.Now open the Math inspector from More>Latex
+
+Observed Result:
+The Math inspector does not open,Now if you click on link both the inspectors open together.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12805}",1383698100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_description,resolved
+VisualEditor: Math inspector does not check type of node it's inspecting,Verified the fix on production,1398988169,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,Verified the fix on test2,1398898856,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,Verified the fix on Betalabs,1398114293,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,Fixed in gerrit 125933.,1397694799,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"Created attachment 15126
+Errors and blank inspector
+
+**Attached**: {F12806}",1397691900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"It also throws the following errors and the math inspector gets completely blank.:
+Uncaught TypeError: Cannot call method 'getAttribute' of null VM977:417
+Uncaught TypeError: Cannot call method 'getOuterRange' of null",1397691870,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"Both issues caused by the math inspector not checking that what it's inspecting is really a math node, changing summary.",1383700342,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"(In reply to comment #1)
+> I couldn't reproduce the double inspector offhand.
+I can now:
+1. Insert an image
+2. Unselect and reselect the image so just the image is selected
+3. Open the math inspector. It attempts to inspect the image and crashes
+4. Post-crash, you get the double inspector thing",1383700292,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+VisualEditor: Math inspector does not check type of node it's inspecting,"At least one issue here is that MWExtensionInspector and MWMathInspector don't check that this.focusedNode is actually of the right type before doing things, so the math inspector will happily inspect references etc.
+
+I couldn't reproduce the double inspector offhand.",1383700014,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2yz76pkci3v3zvjx2tiq,task_subcomment,NA
+Move OOjs and OOjs-UI to their own repos,"Currently OOjs is mastered in github(!) and OOjs-UI within VisualEditor; instead, they should be in their own repos so that other projects can re-use them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383587220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sffy2i74xcwn56xygl5s,task_description,resolved
+Move OOjs and OOjs-UI to their own repos,This is now done.,1383932971,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sffy2i74xcwn56xygl5s,task_subcomment,NA
+Move OOjs and OOjs-UI to their own repos,"Change 94264 merged by jenkins-bot:
+Move files from modules/oojs-ui to the repository root
+
+https://gerrit.wikimedia.org/r/94264",1383932049,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sffy2i74xcwn56xygl5s,task_subcomment,NA
+Move OOjs and OOjs-UI to their own repos,"Change 94264 had a related patch set uploaded by Jforrester:
+Move files from modules/oojs-ui to the repository root
+
+https://gerrit.wikimedia.org/r/94264",1383931993,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sffy2i74xcwn56xygl5s,task_subcomment,NA
+Provide a mechanism to transclude/include translatable templates,"If a template is made translatable, {{template}} no longer works as expected. While this is hard to fix, Translate extension should provide out of the box the functionality of https://www.mediawiki.org/wiki/Template:Translatable_template.",1383283200,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ux7txrspzgavrsg33265,task_description,duplicate
+Provide a mechanism to transclude/include translatable templates,Of course I should have checked whether such tasks exists before doing changes...,1458719733,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-ux7txrspzgavrsg33265,task_subcomment,NA
+Provide a mechanism to transclude/include translatable templates,"I am going to repuspose this task. This might change when support for VisualEditor is added. In the mean time the recommended way is to use templates such as https://www.mediawiki.org/wiki/Template:Translatable_template
+
+Translate extension should provide such facility out of the box, or at least make it easier than copying that template (which requires Lua).",1458719110,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-ux7txrspzgavrsg33265,task_subcomment,NA
+Provide a mechanism to transclude/include translatable templates,"This has never been supported. Bug 48891 might change that, but I'm desperately needing help from people being able to hack the parser.",1383300585,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-ux7txrspzgavrsg33265,task_subcomment,NA
+Provide a mechanism to transclude/include translatable templates,"I meant
+
+2. Transclude page A in Page B. Sorry.",1383283298,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ux7txrspzgavrsg33265,task_subcomment,NA
+Image alt attribute resolves without alt= in wikitext,"This is related to bug #48924 and came up while working on VE's new media dialog.
+
+Symptoms :
+1. Parsoid seems to ignore adding an alt attribute to an image that had no alt attribute previously -- the image still has no alt attribute post-save, even though the DM/CE in VisualEditor were both updated properly.
+
+2. When the alt string in 'alt=something' is changed, the resulting wikitext post-save is produced without the 'alt='
+
+So, an original wikitext:
+
+[[File:Someimage.png|thumb|265x265px|some caption|right|alt=some alternate text]]
+
+After editing the alt property in VE, the wikitext post-save becomes:
+
+[[File:Someimage.png|thumb|265x265px|some caption|right|some alternate edited text]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383174540,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-vyjwvfkazlz4xdouhxqh,task_description,resolved
+Image alt attribute resolves without alt= in wikitext,"Change 103082 merged by jenkins-bot:
+Edited image attributes should override data-parsoid value.
+
+https://gerrit.wikimedia.org/r/103082",1389141626,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vyjwvfkazlz4xdouhxqh,task_subcomment,NA
+Image alt attribute resolves without alt= in wikitext,"Change 103082 had a related patch set uploaded by Cscott:
+Edited image attributes should override data-parsoid value.
+
+https://gerrit.wikimedia.org/r/103082",1387811327,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vyjwvfkazlz4xdouhxqh,task_subcomment,NA
+"VisualEditor: When cursor ends up outside of a content branch node, move it back into one","Document:
+
+ h2> Foo
+ p> Lorem ipsum.
+ h2> Bar
+ p> Bla bla bla.
+
+Steps:
+
+* Put cursor in the first heading between ""F"" and ""oo"".
+* Change text style to paragraph (via menu or or use ctrl-0).
+* Observe cursor going wild (disappears in Firefox, appears outside the document in the margin in Chrome, bug 50442)
+* Type 3 characters (""a"", ""b"", ""c"")
+
+Firefox result:
+
+3 new paragraph appear.
+
+ p> o [new]
+ p> o [new]
+ p> a [new]
+ p> Foo
+ p> Lorem ipsum.
+
+And more on every subsequent keystroke. It seems to have copied this ""o"" from ""Foo"" somehow. And ""b"" and ""c"" never appear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1383076620,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-aiigjvy5vmwd6y2u2ole,task_description,resolved
+"VisualEditor: When cursor ends up outside of a content branch node, move it back into one",I believe that this was fixed by Ed's Firefox CE re-write.,1399418779,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aiigjvy5vmwd6y2u2ole,task_subcomment,NA
+"VisualEditor: When cursor ends up outside of a content branch node, move it back into one",*** Bug 56338 has been marked as a duplicate of this bug. ***,1386028032,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aiigjvy5vmwd6y2u2ole,task_subcomment,NA
+VisualEditor: Changing text formatting dislodges the text cursor,"Screenshot of problem.
+
+1. Put cursor in a heading.
+2. Change text style to paragraph (or use ctrl-0).
+3. Observe the cursor is now outside the content area in the document margin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12115}",1383076200,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-htxalzptwgauyfiuzj3f,task_description,resolved
+VisualEditor: Changing text formatting dislodges the text cursor,"
+
+*** This bug has been marked as a duplicate of bug 56340 ***",1386028032,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-htxalzptwgauyfiuzj3f,task_subcomment,NA
+VisualEditor: Text formatting menu issues,"The text style menu has major issues. For all intends and purposes I declare it completely broken. Tracking them here in case they're related.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383076080,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5qityf526pfz6qwd7svp,task_description,invalid
+VisualEditor: Text formatting menu issues,Not needed for one bug.,1386028091,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5qityf526pfz6qwd7svp,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,"page after typing one character
+
+seen in Firefox not Chrome in master as of Oct 28
+
+Edit any page on http://en.wikipedia.beta.wmflabs.org
+
+When VE manifests, type any character
+
+Existing text of page jumps down one line, as if VE has inserted a RETURN command upon typing in the page. 
+
+Seen only in Firefox, not Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56642
+
+**Attached**: {F12001}",1382992380,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-catfculfgyiwykiyu7uj,task_description,resolved
+VisualEditor: Unexpected RETURN character upon first editing a page,"Unsetting ""VERIFIED""; we don't generally use that, and setting it will hide it from people's saved searches.",1384856020,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,"Verified for on https://test2.wikipedia.org/ with FireFox 25 on MAC OS X 10.8.5
+Example test page:https://test2.wikipedia.org/wiki/Verify_56274",1384539917,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,Verified in for any page on http://en.wikipedia.beta.wmflabs.org,1384453796,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,Looks like this issue got fixed.Verified in betalabs with FF 25.,1384390061,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,"Reproduced this bug FireFox.Also observed that , in FireFox upon clicking on the Edit-beta the value of the heading pull down menu is blank instead of the format the existing text have as soon as a character is entered and the existing line goes to the next line, the ""Paragraph"" value appears in the heading drop down.
+
+However, the case is different for chrome , the value of the heading drop down for the existing line appears as soon as user clicks on Edit-beta and this bug does not occur there.",1383156544,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Unexpected RETURN character upon first editing a page,"note that this action also seems to incorporate a BACKSPACE action as well, since the cursor ends on the same vertical axis as it begins",1383060777,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-catfculfgyiwykiyu7uj,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,"**Author:** `Wikifram`
+
+**Description:**
+This test edit[https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=809490&oldid=795427]: all I did was add [[Test]] at the end of the sentence (to check basic nowiki functionality in the new release 23). However, VE started moving the nowikis around, and now the ref, which was in the old diff a nice ""1"", is now a strange string, ""UNIQ74171d8572aa65a1-nowiki-00000018-QINU1UNIQ74171d8572aa65a1-nowiki-00000019-QINU"". This will probably be a rare occurrence, so not urgent in that regard, but it may be indicative of other problems.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382974020,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3et3rxfdnnlv6panz53k,task_description,resolved
+VisualEditor: Prevent application of link annotations to references,"Change 96238 merged by jenkins-bot:
+Prevent link-annotating MWReferences
+
+https://gerrit.wikimedia.org/r/96238",1384858902,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,"Change 96238 had a related patch set uploaded by Esanders:
+Prevent link-annotating MWReferences
+
+https://gerrit.wikimedia.org/r/96238",1384858734,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,"Otherwise, output is ill-defined (UNIQ bug) and not good for users.
+
+(Thought there was an existing bug, but couldn't find it.)",1384857259,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,*** Bug 56751 has been marked as a duplicate of this bug. ***,1383870381,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Prevent application of link annotations to references,"**Wikifram** wrote:
+
+Note that when you open the page in VE mode, it again displays the ref correctly. Strange... 
+
+Note also that a much simpler version, a link with a ref in the link, has the same behaviour, so the ""nowikis"" are probably only a distraction and this may more serious than I first thought...[https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=809494&oldid=809493]",1382974276,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3et3rxfdnnlv6panz53k,task_subcomment,NA
+VisualEditor: Vertical keyboard selection (shift+up/down cursor) over a node type boundary gives unexpected results in Firefox,"**Author:** `Wikifram`
+
+**Description:**
+I had entered this at enwiki VisualEditor/Feedback, but got no response. Apparently no bug for this has been filed, even though it is quite serious. All links are for pages on enwiki. 
+
+I'm trying to select one template, but get unexpected results. If you go to [[Karl Popper]], put the cursor at the start of the header ""Backdrop to his thought"", and use the left side ""caps arrow"" plus the up-arrow from the four direction arrows (to select the line above it), the first time you do this, your cursor disappears. The second time, you select everything including half a line of the paragraph ''above'' the ""philosophy"" section header, the philosophy section header, and the ""main"" template. This is rather unexpected. 
+
+Similarly, only using the ""up"" arrow, starting again at the same place: first time, the cursor seems to disappear (looking more closely, it stands at the right side of the infobox, at the height of the ""main article"" template. Using it again movs it to the middle of the last line of the previous paragraph, skipping the template and the ""philosophy"" section header. 
+
+The reverse is even worse. Starting from the paragraph above the ""philosophy"" header and using the ""down"" arrow, your cursor moves to the end of the ""philosophy"" header (good!); using ""down"" again, it moves to the right of the infobox (at the same line as the ""main article"" template) (not good, perhaps acceptable); using down again, and again, and again, does absoluetly nothing anymore... 
+
+Stranger and stranger: going from the ""philosophy"" header using the right button works like a charm. If you then start using the ""up"" arrow though, you are no longer scrollong inside the text, but yo uare scrolling the whole webpage instead... I stopped testing after this, having had more than enough of this!
+
+Basically, the use of arrows in VE shows some very bizarre behaviour and should be thoroughly tested and bugfixed. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 15:02, 25 October 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51957",1382972940,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-iu6hbgjioqo5cvt23aal,task_description,resolved
+VisualEditor: Vertical keyboard selection (shift+up/down cursor) over a node type boundary gives unexpected results in Firefox,"As far as I can tell these were solved when we switched up/down behaviour with regard to browser-native selections. There are some issues in this area, but this ticket doesn't capture them.",1420844427,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iu6hbgjioqo5cvt23aal,task_subcomment,NA
+VisualEditor: Vertical keyboard selection (shift+up/down cursor) over a node type boundary gives unexpected results in Firefox,"1) I can reproduce the odd two-step up-arrow selection bug in Firefox, but not in Chrome. I couldnt quickly see that bug raised.
+
+2) Likewise the down-arrow selection problem is also Firefox only, and appears to be bug 51957
+
+3) The arrow-page-scroll-down bug is also Firefox only. I couldnt find a bug for it, but it is similar to bug 53420",1383177503,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-iu6hbgjioqo5cvt23aal,task_subcomment,NA
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Perceived performance could be substantially improved by having VisualEditor optimistically request serialization of the DOM as soon as the user hits ""Save page"". If the user ends up canceling the save, the serialized DOM would be discarded.
+
+Users that take a few seconds to write the edit summary before confirming the save would experience near-instant saves this way.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55979",1382470140,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_description,resolved
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Change 93934 merged by jenkins-bot:
+Use serialization cache in MW integration
+
+https://gerrit.wikimedia.org/r/93934",1385139189,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_subcomment,NA
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Change 93109 merged by jenkins-bot:
+Implement serialization cache in VisualEditor API
+
+https://gerrit.wikimedia.org/r/93109",1385138385,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_subcomment,NA
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Change 93934 had a related patch set uploaded by Catrope:
+[WIP] Use serialization cache in MW integration
+
+https://gerrit.wikimedia.org/r/93934",1383727786,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_subcomment,NA
+"VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks ""Save page""","Change 93109 had a related patch set uploaded by Catrope:
+Implement serialization cache in VisualEditor API
+
+https://gerrit.wikimedia.org/r/93109",1383341741,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y4a7ol3ogwhv6t7beaox,task_subcomment,NA
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Previewing a page and then saving it without further modifications should result in one serialization request being made to Parsoid, not two. The serialized DOM generated in course of responding to the preview request should be re-used when saving whenever VisualEditor can determine that no modifications intervene these two operations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56011",1382397660,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-4e57g4ptze3lbabyzrzu,task_description,resolved
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Change 93934 merged by jenkins-bot:
+Use serialization cache in MW integration
+
+https://gerrit.wikimedia.org/r/93934",1385139192,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4e57g4ptze3lbabyzrzu,task_subcomment,NA
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Change 93109 merged by jenkins-bot:
+Implement serialization cache in VisualEditor API
+
+https://gerrit.wikimedia.org/r/93109",1385138382,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4e57g4ptze3lbabyzrzu,task_subcomment,NA
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Change 93934 had a related patch set uploaded by Catrope:
+[WIP] Use serialization cache in MW integration
+
+https://gerrit.wikimedia.org/r/93934",1383727790,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4e57g4ptze3lbabyzrzu,task_subcomment,NA
+"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain","Change 93109 had a related patch set uploaded by Catrope:
+Implement serialization cache in VisualEditor API
+
+https://gerrit.wikimedia.org/r/93109",1383341746,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4e57g4ptze3lbabyzrzu,task_subcomment,NA
+VisualEditor: An empty edit notice is appearing at every page,"An empty edit notice is now appearing on any page.
+
+Tested on Firefox and Safari
+
+https://en.wikipedia.org/wiki/LibreOffice?veaction=edit
+https://en.wikipedia.org/wiki/Maxi_single?veaction=edit
+https://en.wikipedia.org/wiki/Northeim?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1382307480,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-hha36vju233upi7kw3se,task_description,resolved
+VisualEditor: An empty edit notice is appearing at every page,"Only a problem for sysops – a regression in bug 43013's fix.
+
+*** This bug has been marked as a duplicate of bug 43013 ***",1394495869,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hha36vju233upi7kw3se,task_subcomment,NA
+VisualEditor: An empty edit notice is appearing at every page,"On pages that do have a notice displayed (e.g. those that are semi-protected) the empty page notice is noted as a second message, but one that it is impossible to view. 
+
+Firefox 24.0/Monobook/Linux observed at [[Tycho Brahe]]",1382877359,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hha36vju233upi7kw3se,task_subcomment,NA
+VisualEditor: An empty edit notice is appearing at every page,Also confirmed on Chrome.,1382308295,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-hha36vju233upi7kw3se,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it","Intention:  Add a parameter to a template.
+
+
+Expectation:  That the cursor would automatically be present in the ""Add parameter"" text field (where it says ""Parameter name""), so we could just start typing without having to reach for the mouse.
+
+
+Steps to reproduce and results:
+
+1)  Add or open any template.
+
+2)  Start typing the name of a parameter.
+
+3)  Discover that you are no longer able to just start typing the name, but must first reach for the mouse or trackpad, and then click to put the cursor inside the only possible place where you might be typing on that screen.
+
+
+This was reported as a new and undesirable behavior with MediaWiki version 1.22wmf21, by a user who normally uses Firefox 24, Windows 8 and Vector skin and confirmed in Safari 6 on a Mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382221620,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_description,resolved
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it",Works for me!  Thanks.,1407176685,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it","Change 148233 merged by jenkins-bot:
+Auto-open ""Add parameter"" part of template dialog when tabbed to or opening with no required/suggested params
+
+https://gerrit.wikimedia.org/r/148233",1406072263,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it","Should be done now. WhatamIdoing, feel free to reopen this if you disagree",1406072223,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it","Change 148233 had a related patch set uploaded by Alex Monk:
+Auto-open ""Add parameter"" part of template dialog when tabbed to or opening with no required/suggested params
+
+https://gerrit.wikimedia.org/r/148233",1405977031,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When adding a new template, auto-open the ""add parameter"" section and put the cursor in the search dialog's input when we tab to it",Changing this bug slightly to fit the current situation with tab indexes.,1405973106,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-jjqfhcfkk7z7pj4lsi37,task_subcomment,NA
+"VisualEditor: When a template is completely empty, it is invisible in CE","This bug came about from a misspelled parameter in a template on hewiki. The template returned a completely empty result when the required parameter was invalid, and there was no place to hover above the template and access the transclusion icon to change or remove it.
+
+To replicate:
+* Go to https://he.wikipedia.org/wiki/%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%D7%AA:Mooeypoo/%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99/%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_%D7%95%D7%9E%D7%A9%D7%97%D7%A7%D7%99%D7%9D?veaction=edit
+* Click on transclusion, and add the template ""ערך מורחב""
+* Add parameter with the name ""1""
+* Add value to the parameter (invalid value) - ""[[blah]]""
+* Apply and click anywhere else on the document to clear the selection - the template vanished. However, it was added to the wikitext and is in the page after save, but there's no way to access it from VisualEditor and remove it (or edit it)
+
+I have an idea on how to solve that, but I am not sure if the issue isn't deeper.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381957920,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-r3eqg73n7uhflvgw7eg3,task_description,resolved
+"VisualEditor: When a template is completely empty, it is invisible in CE","Change 90210 merged by jenkins-bot:
+Add a placeholder into an empty transclusion
+
+https://gerrit.wikimedia.org/r/90210",1382982138,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r3eqg73n7uhflvgw7eg3,task_subcomment,NA
+"VisualEditor: When a template is completely empty, it is invisible in CE","Change 90210 had a related patch set uploaded by Catrope:
+Adding a placeholder into an empty transclusion
+
+https://gerrit.wikimedia.org/r/90210",1381962383,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r3eqg73n7uhflvgw7eg3,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize","If you have a right-floating image, select it by clicking on it, then make the window wider on the right-hand size, the image moves to the right but the highlight doesn't. Same goes for resize handles etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55787",1381931100,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_description,resolved
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize",At least the first part of this is done.,1402446907,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize","Change 134363 merged by jenkins-bot:
+[BREAKING CHANGE] Merge ProtectedNode into FocusableNode
+
+https://gerrit.wikimedia.org/r/134363",1402442357,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize","Change 134363 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Merge protected node into focusable node
+
+https://gerrit.wikimedia.org/r/134363",1400695942,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize","The video capture for bug 62632 shows this effect:
+ http://cl.ly/0g2F0q2D3p1D",1394758925,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Highlights, resize handles, etc. not repositioned on window resize",*** Bug 60701 has been marked as a duplicate of this bug. ***,1394128066,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aiuoktdbszkgqdmpuqlq,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'clearMessage'
+
+Appears to be thrown by line 792 of modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.js: 'this.clearMessage( 'captcha' );'.
+
+Seen on MediaWiki.org after trying to solve a Captcha, in the process of saving an edit to <https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team/Quarterly_review%2C_October_2013>.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381818480,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-omdhcpi6if5gftpy7523,task_description,resolved
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""",Now cherry-picked to live.,1381879688,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Change 89794 merged by jenkins-bot:
+'clearMessage' is a method of MWSaveDialog, not ViewPageTarget
+
+https://gerrit.wikimedia.org/r/89794",1381878154,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Change 89794 had a related patch set uploaded by Catrope:
+'clearMessage' is a method of MWSaveDialog, not ViewPageTarget
+
+https://gerrit.wikimedia.org/r/89794",1381834894,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Change 89773 merged by jenkins-bot:
+'clearMessage' is a method of MWSaveDialog, not ViewPageTarget
+
+https://gerrit.wikimedia.org/r/89773",1381834542,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage""","Change 89773 had a related patch set uploaded by Krinkle:
+'clearMessage' is a method of MWSaveDialog, not ViewPageTarget
+
+https://gerrit.wikimedia.org/r/89773",1381834425,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-omdhcpi6if5gftpy7523,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Cause an exception from something with call_user_func in its stack.
+
+For example, if you use wfUseMW( '2000.0' ); inside VisualEditor::onSetup (wgExtensionFunctions), you get:
+
+
+
+Notice: Undefined index: file in /includes/Exception.php on line 725
+Notice: Undefined index: line in /includes/Exception.php on line 725
+Notice: Undefined index: file in /includes/Exception.php on line 725
+Notice: Undefined index: line in /includes/Exception.php on line 725
+
+MediaWiki 2000.0 required--this is only 1.22alpha
+
+Backtrace:
+
+#0 /extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW('1.229wmf11')
+#1 (): VisualEditorHooks::onSetup()
+#2 /includes/Setup.php(592): call_user_func('VisualEditorHooks::onSetup')
+#3 /includes/WebStart.php(153): require_once('/includes/Setup.php')
+#4 /index.php(46): require('/includes/WebStart.php')
+#5 {main}
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal",1381515180,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ebmnnccanbjpovnhy3nw,task_description,resolved
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Change 90067 abandoned by Dereckson:
+Fixes stacktrace output when an internal function is called.
+
+Reason:
+As the information isn't pertinent to the exception position.
+
+https://gerrit.wikimedia.org/r/90067",1382948111,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)",*** Bug 55479 has been marked as a duplicate of this bug. ***,1381881831,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Change 90067 had a related patch set uploaded by Dereckson:
+Fixes stacktrace output when an internal function is called.
+
+https://gerrit.wikimedia.org/r/90067",1381881576,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)",*** Bug 55479 has been marked as a duplicate of this bug. ***,1381880536,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Change 89243 merged by jenkins-bot:
+exception: Account for $call['file'] and $call['line'] being unset
+
+https://gerrit.wikimedia.org/r/89243",1381517453,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","(In reply to comment #0)
+> Notice: Undefined index: file in /includes/Exception.php on line 725
+> Notice: Undefined index: line in /includes/Exception.php on line 725
+> Notice: Undefined index: file in /includes/Exception.php on line 725
+> Notice: Undefined index: line in /includes/Exception.php on line 725
+> 
+> MediaWiki 2000.0 required--this is only 1.22alpha
+> 
+> Backtrace:
+> 
+> #0 /extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW('1.229wmf11')
+> #1 (): VisualEditorHooks::onSetup()
+> #2 /includes/Setup.php(592): call_user_func('VisualEditorHooks::onSetup')
+> #3 /includes/WebStart.php(153): require_once('/includes/Setup.php')
+> #4 /index.php(46): require('/includes/WebStart.php')
+> #5 {main}
+
+
+New output after the patch:
+
+#0 /extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW('1.229wmf11')
+#1 {internal}: VisualEditorHooks::onSetup()
+#2 /includes/Setup.php(592): call_user_func('VisualEditorHooks::onSetup')
+#3 /includes/WebStart.php(153): require_once('/includes/Setup.php')
+#4 /index.php(46): require('/includes/WebStart.php')
+#5 {main}",1381515709,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Change 89243 had a related patch set uploaded by Krinkle:
+exception: Account for $call['file'] and $call['line'] being unset
+
+https://gerrit.wikimedia.org/r/89243",1381515507,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+"Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)","Upstream bug:
+
+https://bugs.php.net/bug.php?id=64987",1381515247,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ebmnnccanbjpovnhy3nw,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,"Problems:
+* The dm.Surface constructor initializes the selection at (1,1) because (0,0) is not a selection we can render in most documents
+* ui.Surface.initialize has the following code:
+// By re-asserting the current selection and forcing a poll we force selection to be something
+// reasonable - otherwise in Firefox, the initial selection is (0,0), causing bug 42277
+this.model.getFragment().select();
+this.view.surfaceObserver.pollOnce();
+* However, when VE loses focus then regains focus, we don't restore the selection
+
+Issues caused:
+* Selections of (1,1) don't play nice with documents that start with a FocusableNode
+* The fact that ui.Surface.initialize reasserts the selection means that VisualEditor focuses itself on initialization, which Flow is now having to work around
+* When ULS blurs then refocuses VE during its initialization, the selection jumps back to the top
+
+What we should really be doing:
+* Initialize the selection at the first content offset (this is 1 for most documents, but will be different for documents that start with a FocusableNode)
+* Get rid of the model->view->model circular synchronization in ui.Surface.initialize and fix whatever problems it fixed differently
+* Restore selection on focus
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381324560,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_description,resolved
+VisualEditor: Get rid of selection rendering on init,"(In reply to Roan Kattouw from comment #4)
+> (In reply to Ed Sanders from comment #3)
+> > I certainly addressed point 1 of Roan's list of actions, he may want to
+> > follow up on 2 & 3.
+> I did 3 a while ago. As for 2, I don't know how current that is, let me take
+> a look.
+Nope, 2 seems to be gone. So this bug is fixed completely then.",1393456056,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,"(In reply to Ed Sanders from comment #3)
+> I certainly addressed point 1 of Roan's list of actions, he may want to
+> follow up on 2 & 3.
+I did 3 a while ago. As for 2, I don't know how current that is, let me take a look.",1393455953,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,"I certainly addressed point 1 of Roan's list of actions, he may want to follow up on 2 & 3.",1391716824,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,This was fixed some time ago by Ed.,1391663171,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Get rid of selection rendering on init,"Is this the bug that causes templates to be pre-selected upon loading the editor?
+
+Is this the bug that is resolved when the editor just places the cursor (""collapsed"" selection) at the visual start of the document (e.g. not selecting the first template or character, but before it, blinking on the top left).",1383075174,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nlovvj3dmzpq3qzvi5qq,task_subcomment,NA
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Right now we emit both 'live' and 'setup'/'teardown' , and some classes listen to 'live' while others use 'setup'/'teardown'. We should converge on using setup/teardown and remove live.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381315200,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pbmmp535m2nwlycrbccu,task_description,resolved
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Change 144634 merged by jenkins-bot:
+Deprecate 'live' event in favor of 'setup' and 'teardown' in MW
+
+https://gerrit.wikimedia.org/r/144634",1406072200,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pbmmp535m2nwlycrbccu,task_subcomment,NA
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Change 144586 merged by jenkins-bot:
+Deprecate 'live' event in favor of 'setup' and 'teardown'
+
+https://gerrit.wikimedia.org/r/144586",1406072089,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pbmmp535m2nwlycrbccu,task_subcomment,NA
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Change 144634 had a related patch set uploaded by Mooeypoo:
+Deprecate 'live' event in favor of 'setup' and 'teardown' in MW
+
+https://gerrit.wikimedia.org/r/144634",1404794231,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pbmmp535m2nwlycrbccu,task_subcomment,NA
+VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown',"Change 144586 had a related patch set uploaded by Mooeypoo:
+Deprecate 'live' event in favor of 'setup' and 'teardown'
+
+https://gerrit.wikimedia.org/r/144586",1404769146,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pbmmp535m2nwlycrbccu,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"Tested on both the Italian and the English Wikipedia a few days ago;
+Reach the bottom of any page: the link inspector does not present the
+list of options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55343",1381236120,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_description,resolved
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"I believe that this is now fixed, at least as far as I can tell.",1402549384,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"Yup, I can reproduce this now. It looks like in some cases, the selection dropdown isn't shown properly, it retains display:none; and height:0; (but the suggestions are there, I can see them in the DOM inspector). I think this may have to do with the unreliable behavior of nested .show() calls in jQuery in Firefox: I've observed that sometimes, calling .show() on a container doesn't immediately cause its children to evaluate as visible, which means that calling .show() on those children is a no-op because .show() refuses to touch things whose parent is hidden. The height:0 is likely due to trying to measure a hidden element.
+
+CC Trevor.",1381243824,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"Roan: right now in that page, if I click on ""California"", I get a ""page found"" text and two arrows which allow me to scroll a list of alternatives (which do not look handy since they only allow to preview one line at a time).
+A few lines below, if I click on ""architettura moderna"", I don't get alternatives.
+If I write somewhere, say, ""USA"" and try to make it a link, that will work, but I still don't get to decide which page the link should point at.
+In FF, it doesn't work with Vector. It's both browser and skin specific, for me.",1381243086,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"I can confirm this bug on en.wp, but not on nn.wp or mediawiki.org",1381241141,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"I tried reproducing this on http://it.wikipedia.org/wiki/San_Francisco in both Firefox and Chrome, but both editing existing links and adding new links works for me.",1381236525,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox,"(Please scratch the bottom of the page part, it doesn't work anywhere).",1381236267,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7hmdcwhevnhvtjp6kuea,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Filing this since subbu wanted to take a closer look (""Yes, VE/Parsoid shouldn't be making dirty diffs -- and these kind of dirty diffs is an exception rather than the rule. This is a bug.""):
+
+<<VE seems to make unnecessary changes. I wouldn't mind so much if it always helped to maintain the layout of invisible elements, but normally it just screws them (like infoboxes, or position of templates), without any effect on the rendered page but with a less easily readable wikitext editing window.
+What I notice now though are totally unnecessary and hard to explain changes to ref names. For some reason, VE decides that all ref names need to be in quotes, which is not true at all and doesn't help one bit. It also decides that between the final quote and the forward slash, there needs to be a space. All this has no effect on the rendered page, and doesn't make the wikitext page any easier (or harder) to read, so why does VE bother doing this, which only helps to make diffs a lot longer.
+Take a look at e.g. [10]: can you easily see if any significant change has been made, and what that may be?
+First difference; <ref name=""globsec-arjun""/> becomes 
+<ref name=""globsec-arjun"" /> Further: <ref name=nomorearjuns> becomes <ref name=""nomorearjuns"">
+and so on. I have not found the actual significant difference between the old and new version. What is the purpose and benefit of this? If VE would always make the ""invisible"" layout clearer and better, fine, but VE doesn't care one bit about wikitext layout, so I don't get this useless editing. Fram (talk) 09:27, 7 October 2013 (UTC)>>
+
+https://en.wikipedia.org/w/index.php?title=Arjun_%28tank%29&curid=7648336&diff=576092971&oldid=575064244
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381222380,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_description,resolved
+Quotes and whitespace normalized in unedited <ref> tags,"Closing this task since there is nothing much more to be done here since we cannot protect against varnish cache failures -- these should be a fairly rare occurrence. Once we move to RESTbase, this should not happen anymore.",1418854972,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,This is still happening regularly.  Another example is at  https://en.wikipedia.org/w/index.php?diff=629369061,1413311064,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Another one, found while looking at diffs after the deploy of d51e64097:
+https://fr.wikipedia.org/w/index.php?title=Cendrillon_(Disney)&curid=3040885&diff=105440424&oldid=104520814",1405370096,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Here's another diff that is probably the same bug:
+
+https://en.wikipedia.org/w/index.php?title=Rights&curid=51490&diff=603988349&oldid=601154438
+
+In this one, an oddly named-but-unnamed ref tag (<ref name="""">) has its whitespace normalized.",1398219709,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"This is just a note that Bug 64197, merged here, is about {{sfn}} templates, which sort of are and sort of aren't ref tags.  See https://en.wikipedia.org/w/index.php?title=Jack_Parsons_%28rocket_engineer%29&diff=604788783&oldid=604787564",1398135489,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,*** Bug 64162 has been marked as a duplicate of this bug. ***,1398116545,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,*** Bug 64197 has been marked as a duplicate of this bug. ***,1398116521,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+I've reopened this, since it appears that this still happens: [https://en.wikipedia.org/w/index.php?title=Triceratops&curid=54410&diff=584366006&oldid=584365568]",1386082882,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"I believe this was fixed by 67fca5bdc7 and 923c79102a.
+
+These test cases from comments above now round-trip fine:
+
+* comment #1: https://en.wikipedia.org/wiki/User:Gwicke/Test/Arjun_%28tank%29
+* comment #4: https://en.wikipedia.org/wiki/User:Gwicke/Test/Wrestler
+* comment #8: https://en.wikipedia.org/wiki/User:Gwicke/Test/Gray_wolf
+
+Please reopen if this problem still exists.",1386032944,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,The diff in comment #10 might have been caused by an unrelated issue with one of the Varnish caches in production.,1384823693,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"This last diff seems to have happened in the context of some error the editor encountered. Recording here for further debugging.
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=581952520#Error:Unknown_error",1384788280,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+Still happened on the 16th: [https://en.wikipedia.org/w/index.php?title=KLM&diff=581951122&oldid=581950935]",1384762981,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Yes, those were probably from cache misses. We deployed newer code y'day that should eliminate these unrelated normalizations in most cases (barring bugs). 
+
+Note however that if a <ref> is edited, Parsoid will still normalize the quotes and whitespace in the attributes of the edited ref.
+
+Let us wait for a week to see if we still see unrelaed normalizations and if not, close this as resolved.",1384476665,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+Not just the quotes, also the additional spaces: [https://en.wikipedia.org/w/index.php?title=Gray_wolf&curid=33702&diff=581450926&oldid=581450732] I can't judge whether this is fixed on most pages or not, but it certainly seems to happen quite reguilarly still.",1384334252,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+...still happens apparently: [https://en.wikipedia.org/w/index.php?title=New_%28album%29&diff=581113730&oldid=581109664] (noted by another editor on [[en:WP:VEF]])",1384264390,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"New code has been deployed with a bunch of fixes related to cache misses that would cause Parsoid to run the regular serializer on the entire dom. This should fix this issue on most pages. 
+
+We'll also make some fixes to minimize dirty diffs even when there is a cache miss -- we've identified some improvements we could make to the DOM diff algorithm.",1383892788,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,The new code I mentioned in #c3 hasn't been deployed to production yet. Will update this ticket when that happens.,1383836080,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"**Wikifram** wrote:
+
+It seems that quotes are still being added to ref tags as of today: [https://en.wikipedia.org/w/index.php?title=Sting_%28wrestler%29&curid=655575&diff=580574777&oldid=580516764]",1383827570,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Gabriel and I now think this happened when Parsoid incurred a cache miss for the HTML (rare) and also suffered a timeout on reparsing (possible on large pages since we had a timeout of 16 sec). But, a couple commits today should address this and further reduce the likelihood of selser not getting triggered on the edit.
+
+The relevant commits are:
+
+1. https://gerrit.wikimedia.org/r/#/c/93896/ (increases cache timeout to 60 sec)
+2. https://gerrit.wikimedia.org/r/#/c/93902/ (improves parse time when selser suffers a cache miss fetching original HTML).",1383716659,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,This seems to be related to bugs in selser (Parsoid) when a cache URL is set. I've set a cache URL locally and will investigate.,1383702057,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+Quotes and whitespace normalized in unedited <ref> tags,"Yup, that's a bug. VE should not be normalizing <ref name=""globsec-arjun""/> to <ref name=""globsec-arjun"" /> nor should it be normalizing <ref name=nomorearjuns> to <ref name=""nomorearjuns"">.
+
+Since the revision wasn't tagged with the visualeditor-check tag, VE didn't detect any corruption on its end, which makes me suspect that this is a Parsoid bug.",1381222931,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-rrhxw3o7tylkgfuhgckm,task_subcomment,NA
+mediawiki.notification: div#mw-notification-area remains visible and steals events after dismissing notification,"1. Trigger a notification
+2. Click on the notification to dismiss it
+3. The notification area (<div id=""mw-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.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381220760,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-trd3quxv62oo47pm6dey,task_description,resolved
+mediawiki.notification: div#mw-notification-area remains visible and steals events after dismissing notification,"Wrong bug, sorry
+
+*** This bug has been marked as a duplicate of bug 52659 ***",1409942617,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-trd3quxv62oo47pm6dey,task_subcomment,NA
+mediawiki.notification: div#mw-notification-area remains visible and steals events after dismissing notification,"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",1409942562,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trd3quxv62oo47pm6dey,task_subcomment,NA
+mediawiki.notification: div#mw-notification-area remains visible and steals events after dismissing notification,"All you VE guys really should start looking through bugs that are already reported instead of adding more copies.
+
+*** This bug has been marked as a duplicate of bug 52659 ***",1381254044,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-trd3quxv62oo47pm6dey,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"1. Edit a page with VisualEditor.
+2. Copy a line of text.
+
+Sometimes it just copies the line to the clipboard without generating any move of the content (expected behavior). But sometimes just by typing ctrl-C with text selected you will see a jump of the page.
+
+I haven't found the pattern, but it looks like doing this close to the end of long pages makes it easier to reproduce.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381170060,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-pkufios4crste37qzbra,task_description,declined
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,Can't reproduce any of the issues described in this bug.,1409070789,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"Using *any* means of copying text is making the ctrl/cmd key cause a page to jump up, not just ctrl-c/cmd-c, in Firefox. Right-click and select ""Copy"" and the same thing happens to the ctrl/cmd key. I cannot replicate this in Chrome.
+
+Using Firefox 30:
+1. Open any article of reasonable length to edit in VisualEditor, let's say 
+https://en.wikipedia.org/wiki/Cat?veaction=edit
+2. Scroll down to the middle of the article, select any portion of text, and copy it by either ctrl-c/cmd-c *or* right-clicking on the section with the mouse and selecting copy, without using a keyboard shortcut at all.
+3. Now press your control or command key while the selected text is still highlighted. It now functions as an ""up"" button.
+4. Deselect the text that you have copied and function returns to the control/command.",1404773952,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"Well, the problem also encountered on this page: 
+https://cs.wikipedia.org/wiki/Seznam_lid%C3%AD%2C_kte%C5%99%C3%AD_byli_zabiti_b%C4%9Bhem_Euromajdanu
+
+E.g. when copy&pasting ""."" between rows it also jumps. Problem confirmed in:
+*FF 27 safe mode
+*FF 27.0.1
+*FF 27.0.1 logged of
+
+In Google Chrome 33.0.1750.117 m it jumps and paste sometimes and just once. In IE 7 VE doesnt work at all.",1393311981,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"OK I tried FF 27 and safe mode and I have discovered that problem comes when there are empty list items in undordered list. E.g. If I have:
+
+
+*M. auricantha R.T. Craig
+*M. auritricha R.T. Craig
+*
+*
+*M. canelensis R.T. Craig
+*M. hertrichiana R.T. Craig
+*M. lindsayi R.T. Craig
+
+And I select whatever string on that page and type CTRL+C it ""jumps""
+
+Note: to produce empty li is just place cursor on the end of second item and hit several times enter (in this case 2 times).",1392634145,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,Can't reproduce in FF 26. What exact text did you select? Can someone else confirm?,1391609196,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"I am reopening this bug as I am obscuring such behaviour again in FF 26.0 at this page:
+https://cs.wikipedia.org/wiki/Mammillaria_standleyi
+
+Way to reproduce:
+*Select an item in the unsorted list
+*hit CTRL+C
+
+You will see a jump up and down of the page, which is pretty unconfortable during editing.",1391590240,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"Yes, fixed in gerrit 106185 (made avaiable in MW-VE in gerrit change 106731). Marking as such.",1390321343,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox,"I think Roan put in a fix this a while back, can he confirm?",1390316651,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pkufios4crste37qzbra,task_subcomment,NA
+VisualEditor: Opening the drop-down for a category in the page settings > category pane can cause a category entry to be duplicated,"Fram reports:
+<<Having looked a bit more at categories, I encountered another strange phenomenon. On Opel Laubfrosch https://en.wikipedia.org/wiki/Opel_Laubfrosch, which has a lot of categories, the order of the cats on the page settings tab changes. Initially I get 8 categories, from ""Opel vehicles"" to ""compact cars"". But when I e.g. click on the drop down button next to 1920s automobiles, and then click again in the ""categories"" window (to close the drop down without any changes), I get 10 cats instead of 8, and in a different order. ""Vehicles introduced in 1924"" and ""Sedans"" are doubled (explaining the increase from 8 to 10), and the 3rd one is now no longer ""1920s automobiles"" but ""1930s automobiles""... This can go on for quite a while, with the occasional disappearance of a cat as well apparently (normally the last one). Things start to break down, with the page settings then no longer working, or it being no longer possible to add a cat, and so on.>>
+
+I can confirm what he says, and this bug does not look browser or skin specific.
+VE will let you save in a situation where you have these cats duplicated, and a ""saved edit"" message will also pop-up, but there will be no trace of the edit in the history. Plain removal of all the categories works fine instead: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2Fsandbox&diff=576123603&oldid=576122965 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381145460,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-vtu44ya7j43gvaddcjhx,task_description,resolved
+VisualEditor: Opening the drop-down for a category in the page settings > category pane can cause a category entry to be duplicated,"Yeah, I think so.",1408096666,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vtu44ya7j43gvaddcjhx,task_subcomment,NA
+VisualEditor: Opening the drop-down for a category in the page settings > category pane can cause a category entry to be duplicated,Didn't we fix a bug like this recently? Is this still valid?,1408087302,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-vtu44ya7j43gvaddcjhx,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Erik Moeller: ""
+I agree with previous commenters that this is likely to be at the cause of a
+lot of the accidental infobox deletions and such. I understand it's a tricky
+issue, but the current behavior is extremely confusing from the user's point of
+view, so we need to look at some viable solutions. 
+
+Recapping the simple case: User is on what they perceive to be an unnecessary
+newline, presses delete to make the visual layout match the expected layout. A
+separate object (in the case of the infobox, right-aligned on the other side of
+the screen) suddenly disappears. This is very surprising and counter-intuitive
+behavior.
+
+Why don't we just suppress the delete key when pressing it would delete the
+object the slug is associated with? In some alternative editors like Google
+Docs, it is actually not possible to nuke the entire document by just pressing
+down the delete key at the top of the page -- it will stop before certain
+objects. I've never had any problems as a result.
+
+That seems like the simplest solution to me and does not require a redesign of
+the slugs.
+""
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1380963660,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nhj52cwstgebwydn6v4r,task_description,resolved
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","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.
+
+This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion.
+
+(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'? I will also copy to bug 55336.",1405114280,PHID-USER-mcyovqjor52nj3se4lq7,False,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","I'm confirming on http://en.wikipedia.beta.wmflabs.org/wiki/Greg_and_Karen_DeSanto as a test case that this is working as intended. I would encourage others who care about this issue to try as well (note you'll need to login and enable VE, just as you do on en.wp, since Beta has the same config).
+
+One small UX issue I'm noticing is that you can't consistently cursor away from the focusable nodes, which is somewhat exacerbated now that they're more frequently selected as you delete/backspace through content. I suggest tracking that as a separate bug, if it isn't one already.",1381344021,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Change 87666 merged by jenkins-bot:
+Prevent deletion of FocusableNodes from a collapsed selection
+
+https://gerrit.wikimedia.org/r/87666",1381339368,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Yes, anything you can select with a single click (focusable). We could restrict it to non-inline elements but I think it's useful for inline too.",1381297066,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Will this also cause citations and similar inline nodes to be first selected, rather than deleted, when you press backspace or delete next to them? I'm not saying that would necessarily be wrong behavior (I think it could actually be helpful), but just wanted to clarify.",1381286850,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","Change 87666 had a related patch set uploaded by Esanders:
+Prevent deletion of FocusableNodes from a collapsed selection
+
+https://gerrit.wikimedia.org/r/87666",1380969114,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+"VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated","I agree, although I would say instead of suppressing the delete/backspace key, it should cause the adjacent FocusableNode (e.g. Infobox) to become focused, so that a second keypress actually deletes it. This shouldn't be too difficult to achieve.",1380963832,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nhj52cwstgebwydn6v4r,task_subcomment,NA
+VisualEditor: Pawn appears near deleted reference in Firefox,"https://en.wikipedia.org/wiki/Konami_code?veaction=edit , in Firefox.
+Locate the sequence of references [5][6][7][8].
+Delete one of them (not the first one), hit Space, a pawn appears. 
+Easter egg *in* Konami Code!
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54712",1380898980,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-h7awbzyfjip5gjfxifz2,task_description,resolved
+VisualEditor: Pawn appears near deleted reference in Firefox,This too is fixed now.,1406599319,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-h7awbzyfjip5gjfxifz2,task_subcomment,NA
+VisualEditor: Pawn appears near deleted reference in Firefox,"James, if it's a dupe, it's still not working.",1380971910,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-h7awbzyfjip5gjfxifz2,task_subcomment,NA
+VisualEditor: Pawn appears near deleted reference in Firefox,"This is actually the same (really terrible) bug as bug 54712, which is thankfully now fixed; merging.
+
+Thanks for reporting it!
+
+*** This bug has been marked as a duplicate of bug 54712 ***",1380936671,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-h7awbzyfjip5gjfxifz2,task_subcomment,NA
+VisualEditor: Outer whitespace of first/last node in document not validated,"Because we don't store the inner whitespace of the document, we can't validate the outer whitespace its first/last children.
+
+1. Create document with wikitext:
+==Heading==
+Foo
+2. Delete 'Heading' and the empty line
+3. You now have:
+[{'type':'paragraph', 'internal': {'whitepsace': ['\n']}}, 'F' ....
+in the DM
+4. This serialises to
+\n
+Foo
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380880140,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xooewvbyzadgfzwpxeqt,task_description,resolved
+VisualEditor: Outer whitespace of first/last node in document not validated,"Change 92885 merged by jenkins-bot:
+Store inner whitespace of the body and compare it on conversion
+
+https://gerrit.wikimedia.org/r/92885",1384944306,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xooewvbyzadgfzwpxeqt,task_subcomment,NA
+VisualEditor: Outer whitespace of first/last node in document not validated,"Change 92885 had a related patch set uploaded by Esanders:
+Store inner whitespace of the body and compare it on conversion
+
+https://gerrit.wikimedia.org/r/92885",1383234851,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xooewvbyzadgfzwpxeqt,task_subcomment,NA
+VisualEditor: Outer whitespace of first/last node in document not validated,"**Wikifram** wrote:
+
+Translation for those looking to file a similar bug but no so well-versed in code-speak :-): 
+
+When you have a blank line at the start of an article, before the text of the lead, it is impossible in VE to remove this line or lines. See e.g. [https://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=575706125&oldid=575706080]",1380880521,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xooewvbyzadgfzwpxeqt,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"See test case below. For some reason the <pre> inside the <blockquote> and the p-tag before the blockquote (all of those conditions are necessary to reproduce the bug) is causing the content after the blockquote to not be wrapped in p-tags. See output below. Probably some edge case in the paragraph-wrapping code. 
+
+Based on bug report here:
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=575631753#VE_removing_paragraph_gaps
+
+[subbu@earth lib] cat /tmp/x
+a
+
+<blockquote><pre>
+b
+</pre></blockquote>
+
+c
+
+d
+[subbu@earth lib] node parse < /tmp/x
+<body data-parsoid='{""dsr"":[0,49,0,0]}'><p data-parsoid='{""dsr"":[0,1,0,0]}'>a</p>
+
+<blockquote data-parsoid='{""stx"":""html"",""dsr"":[3,42,12,13]}'><pre data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""strippedNL"":""\n"",""dsr"":[15,29,5,0]}'>
+
+b
+&lt;/pre&gt;</pre></blockquote>
+
+c
+
+d
+</body>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380841560,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-6sni25mbjuiipuy7iv24,task_description,resolved
+Unhandled <pre> tokenizing scenarios in tokenizer,"Change 87632 abandoned by Subramanya Sastry:
+(Bug 54946) Fixed unhandled <pre> tokenizing scenarios
+
+Reason:
+Old and rusty and I am not going to look at this as I originally thought.
+
+https://gerrit.wikimedia.org/r/87632",1400883820,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"Change 92469 merged by jenkins-bot:
+Bug 54946: Alternative solution for <pre> tokenization
+
+https://gerrit.wikimedia.org/r/92469",1383266080,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"Change 92469 had a related patch set uploaded by GWicke:
+WIP Bug 54946: Alternative solution for <pre> tokenization
+
+https://gerrit.wikimedia.org/r/92469",1383007333,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"Change 87632 had a related patch set uploaded by Subramanya Sastry:
+(Bug 54946) Fix unhandle <pre> tokenizing scenarios
+
+https://gerrit.wikimedia.org/r/87632",1380924024,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"This is actually a tokenizer bug. The closing </pre> is not being recognized as an end-tag when a HTML <pre> follows another literal HTML tag on the same line.
+
+Relevent snippet of output for: ""a\n\n<span><pre>\nb\n</pre></span>""
+...
+<span data-parsoid='{""stx"":""html"",""dsr"":[3,28,5,6]}'><pre data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""strippedNL"":""\n"",""dsr"":[8,22,5,0]}'>
+
+b
+&lt;/pre&gt;</pre></span>
+...",1380904499,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+Unhandled <pre> tokenizing scenarios in tokenizer,"Changing that to ""<blockquote><pre> b </pre></blockquote>"" does not trigger the bug. So, p-tags before blockquote and HTML-pre in blockquote with content on new line puts the p-wrapper in a state where p-tags are not added.",1380841845,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-6sni25mbjuiipuy7iv24,task_subcomment,NA
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them","De.WP's ref templates interact unhelpfully with VE/Parsoid, resulting in unwanted insertion of ""<ref name="":0"">""; examples:
+
+https://de.wikipedia.org/w/index.php?title=Titl%C3%A1&diff=prev&oldid=122939538
+
+template: https://de.wikipedia.org/wiki/Vorlage:Internetquelle
+
+https://de.wikipedia.org/w/index.php?title=Die_letzte_Vorstellung&diff=prev&oldid=123020177
+
+template: https://de.wikipedia.org/wiki/Vorlage:Der_Spiegel
+
+It also results in having the display of the ref being moved into another ref. This is different from the other issue debated in 53777
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1380837600,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-j7lyujcbs6zaatnh7kya,task_description,declined
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them",Closing unless and until this is shown to still be a problem.,1402003070,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-j7lyujcbs6zaatnh7kya,task_subcomment,NA
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them",Can you provide steps to reproduce?,1391717290,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-j7lyujcbs6zaatnh7kya,task_subcomment,NA
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them","(In reply to comment #1)
+> I'm not sure I understand what the issue is here? Re-used references are
+> getting a name automatically added ("":0"") so that they can be re-used…
+> 
+> Or are they not edits that are intentionally re-using a reference?
+
+First case: The ""Südtiroler Wochenmagazin"" ref eats the newly inserted ref ""ServusTV"", causing a fix:
+
+https://de.wikipedia.org/w/index.php?title=Titl%C3%A1&diff=123114172&oldid=122939538
+
+Second case: The Der Spiegel ref in the second diff doesn't appear in the ref section at the end of the article but gets eaten up by the Die Zeit ref; causing this edit:
+
+https://de.wikipedia.org/w/index.php?title=Die_letzte_Vorstellung&diff=next&oldid=123020177",1380838667,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-j7lyujcbs6zaatnh7kya,task_subcomment,NA
+"VisualEditor: New references added after existing re-used references (<ref name="":0"" />) replacing rather than proceeding them","I'm not sure I understand what the issue is here? Re-used references are getting a name automatically added ("":0"") so that they can be re-used…
+
+Or are they not edits that are intentionally re-using a reference?",1380837724,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j7lyujcbs6zaatnh7kya,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"(Second browser-specific - Firefox - bug I file today after 54322).
+It was reported by Fram at en.wp, quickest way to duplicate:
+<<cursor in front of ref, use the ""back arrow"" on your keyboard once (so the ref number gets ""blue""), and type.>>
+
+https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=575562298&oldid=575557792 (with a snowman as well).
+
+More ways:
+<<Type some text, add a ref, remove the ref using backspace, then change your mind and use the ""undo"" arrow of VE. No, change your mind again and use the ""undo"" arrow once more, again removing the ref. Now type. Notice anything strange? Yep, I'm typing backwards. https://en.wikipedia.org/w/index.php?title=User:Fram/sandbox&oldid=575553019
+[...]
+Other tests produced the snowmen, or the insertion of huge chunks of text by VE. https://en.wikipedia.org/wiki/In_My_Dreams_%28Emmylou_Harris_song%29?veaction=edit
+[...]
+Easy way to check the ""backwards typing"": go to https://en.wikipedia.org/wiki/In_My_Dreams_%28Emmylou_Harris_song%29?veaction=edit , put the cursor after ref 1, backspace, undo arrow, type.>>
+
+TeamGale adds:
+<<I tried to reproduce it because I was curious and it's a really weird bug! Although when I put my cursor at the end of the ""backwards typing"" and clicked space, I could type straight again! TeamGale 10:03, 3 October 2013 (UTC)>>
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57600
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61538",1380799920,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-c4mfirb7unow74hkyrys,task_description,resolved
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"Now fixed again, hopefully for good.",1406599273,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,*** Bug 57347 has been marked as a duplicate of this bug. ***,1385472098,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"Still being reported: yesterday, on fr.wp.",1382438555,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"Can now replicate; yes, this is very worrying.",1380909491,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"/me shouts :D
+Still happening with Firefox.",1380881622,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"**Wikifram** wrote:
+
+Not a duplicate and/or not resolved. Please just test whatever has been described before closing bugs, there are too many that need to be reopened. [https://en.wikipedia.org/w/index.php?title=In_My_Dreams_%28Emmylou_Harris_song%29&diff=575692625&oldid=565930941]",1380869618,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox,"I /think/ this is the same as bug 54712 which we're working on right now and will rush out a live patch - merging the bugs. If it proves otherwise, please shout
+
+*** This bug has been marked as a duplicate of bug 54712 ***",1380835733,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-c4mfirb7unow74hkyrys,task_subcomment,NA
+VisualEditor: JavaScript crashes if an invalid keyword is used on an image,"To reproduce, go to the URL ([[User:Amire80/ve-invalid-image-keyword]]). Notice that the save button doesn't appear in the toolbar. The JS console shows the following error:
+
+[15:59:08.469] Error: Offset could not be translated to a DOM element and offset: 3
+
+The reason for this is the invalid keyword ""no_such_keyword"" that I used on the image.
+
+A better behavior would be to show the user some kind of a warning about the wrong keyword, rather than throwing a JS error and crashing.
+
+This bug was discovered by User:Nurick in the Hebrew Wikipedia.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/User:Amire80/ve-invalid-image-keyword?veaction=edit",1380754920,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-tjmyy26tm4c7ectpe3s2,task_description,resolved
+VisualEditor: JavaScript crashes if an invalid keyword is used on an image,"This seems to have occurred because we tried to put the selection inside the image caption, which then caused an error. For whatever reason, this doesn't seem to be happening any more; opening your test page in VE doesn't reproduce the error now.",1388915037,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tjmyy26tm4c7ectpe3s2,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"The Paragraph style tool in toolbar is not working in Firefox most of the time.
+
+Steps to reproduce
+1. https://www.mediawiki.org/wiki/special:random
+2. Active VE (Click 'Edit')
+3. Place cursor on normal text
+
+Expected results:
+The paragraph style selector should change to 'Paragraph'
+
+Actual results (in Firefox 24/linux):
+9 out of 10 times, nothing changes.  The tool does not work at all.  Changing style doesnt work.
+
+This doesnt happen on enwp.
+
+In debug=true mode, the paragraph selector nearly always changes to Paragraph, but sometimes it then doesnt change to Heading if the cursor is moved to a Heading and changing the style doesnt work.
+
+There is nothing in the JS console to suggest what might be the problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1380688320,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_description,declined
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"Can't reproduce either; that's four devs (on various environments) unable to reproduce today, so I'm going to claim that this is fixed.",1393466785,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"Just for good measure, also tested extended-support release which is Firefox 24.3; seems ok there too. Either specific conditions need to trigger this which we aren't hitting, or it's gotten fixed...",1393466680,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,I'm no longer able to reproduce this in Firefox 27.0.1 or Firefox 30 nightly.,1393466075,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"(In reply to comment #2)
+> I believe that this is a regression of sorts:
+> 
+> Behavior 1: 2 click, works
+> 
+> 1. Click tool to open menu
+> 2. Move mouse to item you want to select
+> 3. Click to select item
+>..
+> Can you confirm that Behavior 1 works?
+
+yes, that works.
+ 
+> The only difference between browsers seems to be that on Chrome clicking and
+> dragging doesn't highlight items as you drag over them, but in Firefox it
+> does,
+> which is probably why you were expecting the menu to select the item using
+> click and drag on that browser.
+
+My steps to reproduce dont include any clicking, let alone dragging.  You can reproduce this bug using the only they keyboard.",1380757247,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"I believe that this is a regression of sorts:
+
+Behavior 1: 2 click, works
+
+1. Click tool to open menu
+2. Move mouse to item you want to select
+3. Click to select item
+
+Behavior 2: Click and drag, broken since recent refactor of toolbar
+
+1. Press mouse button down on tool to open menu
+2. Move mouse to item you want to select
+3. Release mouse button to select item
+
+I can confirm that Behavior 2 is broken.
+
+Can you confirm that Behavior 1 works?
+
+The only difference between browsers seems to be that on Chrome clicking and dragging doesn't highlight items as you drag over them, but in Firefox it does, which is probably why you were expecting the menu to select the item using click and drag on that browser.",1380738253,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+VisualEditor: [Regression] Text formatting menu broken in Firefox,"Confirmed in Firefox 24 on Mac OS X 10.8.5 -- I had it work once, then not work several times after reloading. Something funky!",1380731980,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-rf2ed4nqjcimz43cz4tr,task_subcomment,NA
+"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",1380573780,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-i27oymi2g7hoildczlee,task_description,resolved
+"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 ***",1380833625,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i27oymi2g7hoildczlee,task_subcomment,NA
+"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.,1380619133,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-i27oymi2g7hoildczlee,task_subcomment,NA
+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",1380325500,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l6lohkvjqdbjrls5sdjz,task_description,resolved
+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 ***",1381157444,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-l6lohkvjqdbjrls5sdjz,task_subcomment,NA
+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",1380324960,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_description,resolved
+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",1380557187,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380557130,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380556379,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380556359,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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.",1380481649,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380474667,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380474550,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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?,1380327448,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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",1380326923,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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.",1380325143,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-w6mmcf4y43jmqe4tziga,task_subcomment,NA
+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}",1380310020,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-lj6h46r7rjyl6me5nb7h,task_description,resolved
+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.",1380325542,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lj6h46r7rjyl6me5nb7h,task_subcomment,NA
+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.",1380318521,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-lj6h46r7rjyl6me5nb7h,task_subcomment,NA
+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.",1380311805,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lj6h46r7rjyl6me5nb7h,task_subcomment,NA
+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}",1380295680,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-22klbikg4fmxw7aotqvi,task_description,declined
+VisualEditor: Sometimes the edit link for VE does not appear,No recent reports.,1408096458,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+VisualEditor: Sometimes the edit link for VE does not appear,"Have you seen this issue recently? If not, this could probably be closed...",1408062252,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+VisualEditor: Sometimes the edit link for VE does not appear,*** Bug 60359 has been marked as a duplicate of this bug. ***,1397067449,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+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",1384870240,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+VisualEditor: Sometimes the edit link for VE does not appear,"Created attachment 13393
+Edit link for VE missing in manual operation
+
+**Attached**: {F12180}",1380295721,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-22klbikg4fmxw7aotqvi,task_subcomment,NA
+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",1380244140,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ipv73kunpojcr76x2cb7,task_description,resolved
+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",1382541620,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ipv73kunpojcr76x2cb7,task_subcomment,NA
+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",1382383496,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ipv73kunpojcr76x2cb7,task_subcomment,NA
+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.",1380324587,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ipv73kunpojcr76x2cb7,task_subcomment,NA
+VisualEditor: Rendering of <source> MWExtensionNode is empty after the user edits it,"1. Create a page with <source lang=""JavaScript"">some content here</source>
+2. Edit the page in VE. Note that the <source> tag renders correctly
+3. Use the alien tag inspector to edit the contents of the <source> tag
+4. The <source> tag rerenders as an empty block
+
+This is because the HTML <source> tag is self-closing and cannot have any content. This leads to strange situations like:
+
+>>> extensionNode[0]
+<source lang=​""JavaScript"">​whee​</source>​
+>>> extensionNode[0].outerHTML
+""<source lang=""JavaScript""></source>""
+
+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",1380066060,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-k77k35tkwkjkzeravyd3,task_description,resolved
+VisualEditor: Rendering of <source> 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",1385924792,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k77k35tkwkjkzeravyd3,task_subcomment,NA
+VisualEditor: Rendering of <source> 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",1385919115,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k77k35tkwkjkzeravyd3,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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",1379834280,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_description,resolved
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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).",1381323957,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","(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.",1381245792,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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",1381244614,PHID-USER-brn4v5ta45bnw4f5as3h,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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",1381175418,PHID-USER-brn4v5ta45bnw4f5as3h,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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 ***",1380836921,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","More from Red Fiona:
+<<If the page already has references, it either doesn't add the reference at all, on this page (https://en.wikipedia.org/w/index.php?title=Vladimir_Gojkovi%C4%87&diff=575208071&oldid=551414203)
+, or adds it as the second reference when it's not really the second reference (https://en.wikipedia.org/w/index.php?title=Nataliya_Pyhyda&diff=575209107&oldid=568886402) .>>",1380645202,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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!!",1380378760,PHID-USER-bug3zrlooz3bdmi4fyl7,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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}",1379834599,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+"[Regression] VisualEditor: Attribute name="":0"" inserted into <ref>","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}",1379834387,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-v44q2sk65tk423gk2wgc,task_subcomment,NA
+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",1379806800,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_description,resolved
+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",1380668740,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380668726,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,Merged into master; we'll back-port and deploy tomorrow.,1380594405,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380594325,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380594312,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380594298,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1380589982,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys,*** Bug 54722 has been marked as a duplicate of this bug. ***,1380326222,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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.,1380201051,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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.,1379996431,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-trziv3xjwkvokcwfszqm,task_subcomment,NA
+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",1379720640,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-zoji45q564z2zd5mmomf,task_description,resolved
+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.,1386031966,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zoji45q564z2zd5mmomf,task_subcomment,NA
+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]",1379716620,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_description,resolved
+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.",1394719478,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+Parsoid jobs are not dequeued fast enough during heavy editing activity,Can we close this bug now? I believe this has been fixed.,1385464680,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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",1380741132,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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. :-(",1380581906,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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",1380575437,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.),1380569455,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.,1380568465,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.,1380568375,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1380568025,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+Parsoid jobs are not dequeued fast enough during heavy editing activity,"Created attachment 13412
+Screenshot to accompany comment 3
+
+**Attached**: {F11775}",1380567824,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379977861,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379920225,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?",1379919819,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379919581,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?,1379919308,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?",1379919266,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379918396,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379916365,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379909439,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379899091,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379897340,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?",1379896974,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379880448,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379835104,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379834310,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379792185,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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""?",1379789440,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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).",1379788021,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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).",1379787771,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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}",1379780486,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+Parsoid jobs are not dequeued fast enough during heavy editing activity,"Created attachment 13342
+Screenshot to accompany comment 2
+
+**Attached**: {F11772}",1379780363,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379774099,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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...",1379755583,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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.",1379754279,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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?",1379751042,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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'"".",1379717174,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+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)",1379716743,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dzv6eikbb3qjtwxvccno,task_subcomment,NA
+"VisualEditor: Right half of toolbar disappears when <center> or <div align=""center""> appears in image on first line of page","When a page has an image on the first line and the image caption contains a <center> tag or a <div align=""...""> 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, <p align=""center""> 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",1379688840,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fl7p4f543bjhpoylmcxl,task_description,resolved
+"VisualEditor: Right half of toolbar disappears when <center> or <div align=""center""> appears in image on first line of page","This was fixed some time ago, I believe; sorry for the very slow triage.",1393531314,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fl7p4f543bjhpoylmcxl,task_subcomment,NA
+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",1379685180,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rjymkq6lc7hubjand5ea,task_description,resolved
+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",1379977305,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rjymkq6lc7hubjand5ea,task_subcomment,NA
+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",1379688103,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rjymkq6lc7hubjand5ea,task_subcomment,NA
+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",1379607000,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-zlvsszagknsbory2w3zc,task_description,resolved
+VisualEditor: Surface isn't updated properly for Language annotations,This was fixed in gerrit 90957.,1382644915,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zlvsszagknsbory2w3zc,task_subcomment,NA
+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.",1379642223,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-zlvsszagknsbory2w3zc,task_subcomment,NA
+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]]<nowiki />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",1379605860,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_description,resolved
+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",1380583290,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,"btw, the <nowiki/> is inserted by Parsoid to make sure the document we have (<a>Foo/a>ish<a>?</a>) is translated properly into what the PHP parser understands as by default the PHP parser treats ""<a> + adjecent text"" as a shortcut to extend the lable (e.g. [[book]]s becomes <a href=""book"">books</a>).",1380283588,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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",1380277908,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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.",1380065635,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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.]] .",1379618394,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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.",1379616875,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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.)",1379615722,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+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]]<nowiki />ish[[Wikipedia|?]]
+
+(In reply to comment #1)
+> I think you mean bug 51442
+
+I do. Dyslexia strikes again :(",1379606657,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail,I think you mean bug 51442,1379606464,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-aaouxso4nhg5xgscmdmm,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Firefox,"Current VisualEditor-Version:
+commit c98a964d5f8495f0d16af9229abbeb0449042d1e
+Merge: 3d01a5b e7aed52
+Author: jenkins-bot <jenkins-bot@gerrit.wikimedia.org>
+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",1379594760,PHID-USER-26asvhtv4jalaeeuigbm,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_description,resolved
+VisualEditor: [Regression] Page settings dialog broken in Firefox,Have split the new failure into bug 54928 and am re-closing this one.,1380823394,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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",1380823156,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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.",1380822772,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+VisualEditor: [Regression] Page settings dialog broken in Firefox,"Confirmed:
+
+* Working on latest master locally (Chrome).
+* Broken on mediawik.org (Chrome).",1380818645,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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:
+<<Just wanted to ask...how can we add categories with VE? In the past I could do it by clicking on ""Page settings"" but now when I click on it nothing happens! Is there somewhere else a button that adds categories? I searched everywhere but I can't find it. If it's still on the ""Page settings"" then something is not working right... Thanks TeamGale 09:54, 3 October 2013 (UTC)>>
+
+Fram tested as well:
+
+<<Tested this. FIrst click on ""page settings"" gives no results. Second click opens the page setting window. But I can't do anything there.>>
+
+I can confirm that the second click just launches an empty window, with only the ""categories"" label text on the left column.
+
+<<Actually this one with the categories is happening for a while for me. Just when I first found it I was in a hurry and couldn't leave a feedback. Then I totally forgot about it till now that I needed to use it again. It's weird that no one else mentioned it here before though.
+Elitre, I don't know if it's a cache problem but I'll try to clean my cache again and re-test it. But the ""after a few attempts"" is still not right for me. Shouldn't this happening in the first attempt? TeamGale 10:12, 3 October 2013 (UTC)
+Update: Nop, still happening the same for me even if I clean cache, cookies etc... TeamGale 10:20, 3 October 2013 (UTC)
+Hmm...it seems to be only a Mozilla issue. I just tried it with Mozilla on Greek WP and it still doesn't work. But when I tested it on Google, it was working just fine. TeamGale 11:00, 3 October 2013 (UTC)>>",1380799304,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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.",1380001984,PHID-USER-26asvhtv4jalaeeuigbm,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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",1379963945,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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",1379959272,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+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,",1379595471,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wxxlsxtwpum7ayno6uo4,task_subcomment,NA
+"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",1379589060,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-equ6rehqzaorfkk3nuw5,task_description,resolved
+"VisualEditor: A pawn appears when undoing ""select transclusion and replace with text""","This is now fixed, AFAICS. Marking as such.",1380844698,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-equ6rehqzaorfkk3nuw5,task_subcomment,NA
+VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,"From en.wp.
+
+John Broughton: <<So there is now a new toolbar, and - bizarrely - the icons for media, reference, reference list, and transclusion '''are no longer visible'''. They are now under the ""More"" menu.
+Okay, one could argue that these four are, somehow, ''advanced'' editing options (no matter how critical they are to editing articles). But I'd love to hear from someone as to why Bold and Italic (the first in particular ''rarely'' used in articles) still have icons visible on the toolbar, while five other formatting options are now under ""More"". It really, really would have been better to have a ""Format text"" drop-down menu that had all seven text formatting options on it, and to leave the media, reference, reference list, and transclusion icons where they were, visible on the toolbar. Or, worst case, leave them under the ""More"" menu [one more click, and thus one less reason for experienced editors to use VE, because this '''makes it more cumbersome to use''' those four things]; at least then they wouldn't be paired with formatting options with which they have little in common. [...] (And don't even get me started on the ''sequence'' within the new ""More"" drop-down menu - apparently the ''least'' important choices are at the ''top'' because that's the way that ''no one else'' does drop-down menus, so obviously everyone else is wrong?!?)>>
+
+Andrew Davidson: <<Bold formatting is not rarely used.  It is used in all articles right at the beginning to emphasise the name of the topic and any synonyms.  But this usage is quite specialised and subject to the conventions of our manual of style.  The VE should understand this.  Either the use of bold text should be handled by a style sheet/template/wizard approach to article creation.  Or the appearance of the bold option in the toolbar should be context sensitive so that it only appears when editing the lead of an article and warnings appears if it seems to be used incorrectly. >>
+
+Salix alba: <<One problem I get is the toolbar frequently splits into two lines. If my browser less than 1100 pixels then the toolbar wraps leaving lots of white space which could be usefully filled. I'd be happier either with single line with more drop downs or two full lines, just not empty space.
+I guess different editors will want different things on a toolbar. Doing inline maths you would want italics, sub, and sup to be easily added plus greek symbols eiπ. Other editors will have different requirements. Tooltips would be handy to get shortcuts for each action, (no I will not read the help page). The wikitext editor's toolbar manages to make a lot of things easily accessible.>>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379510460,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-agsyhe563ga6xlci4yds,task_description,resolved
+VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar,I did this in wmf7.,1389667077,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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 .",1379693737,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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",1379599183,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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.",1379527718,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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.",1379523614,PHID-USER-hirrhium5ibrtof34lwa,True,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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?",1379517590,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-agsyhe563ga6xlci4yds,task_subcomment,NA
+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`.
+",1379372820,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_description,resolved
+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.,1487640775,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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]]",1456599605,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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]]
+",1456598697,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1456598688,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,P2680,1456539439,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,Got this locally on MediaWiki-Vagrant.,1456539379,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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 (<https://gerrit.wikimedia.org/r/#/c/102557/>) and @TStarling at that time wanted the message to stay until the underlying bug was fixed.",1452556121,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,@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.,1452554163,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284,">>! 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.",1441317606,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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}
+```",1441308367,PHID-USER-e7a5lnjpgncgdxknmdxb,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1433168184,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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]]",1421437119,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1416277543,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1416276389,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1416275630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1406922819,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1387492413,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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,1387401105,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385052270,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1385043099,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385041071,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1385038063,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385032746,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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}",1385032556,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1385023044,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1385022091,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385004900,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.",1385004767,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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,1384994015,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1384295661,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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",1384277258,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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?",1384246201,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+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.,1379397762,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-u4lgntwhbwxxlocbfh5j,task_subcomment,NA
+"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 <templatedata /> 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}",1379223360,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_description,open
+"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.",1685509112,PHID-USER-3ljmcrqixyljk2wy63jb,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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}",1685508575,PHID-USER-3ljmcrqixyljk2wy63jb,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1685263240,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1685257840,PHID-USER-3imz37uve2wfuuub5eq6,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1684947002,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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",1684667542,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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).",1684664576,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.,1684658990,PHID-USER-c4xszutxtrvtj73h3rns,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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 <templatedata> will be dynamically generated during the parse time, and is available to every language/every wiki.",1545340062,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1545295664,PHID-USER-3imz37uve2wfuuub5eq6,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.
+
+",1545275829,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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,1502648392,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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 ##<templatedata>## approach needs to be supported, too.
+",1526399860,PHID-USER-3imz37uve2wfuuub5eq6,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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 ##<templatedata>## approach needs to be supported, too.
+",1490880640,PHID-USER-3imz37uve2wfuuub5eq6,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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…",1452893325,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.,1401208356,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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",1398702686,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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.",1379512241,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+"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 ?,1379497097,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-n7t7uv2o256io5ck73dn,task_subcomment,NA
+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
+<html><head><title>Error generating thumbnail</title></head>
+<body>
+<h1>Error generating thumbnail</h1>
+<p>
+Error creating thumbnail:
+</p>
+<!-- http://commons.wikimedia.org/w/thumb_handler.php/f/fb/USMC-05934.jpg/400px-USMC-05934.jpg -->
+<!-- mw1154 -->
+</body>
+</html>
+
+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 <img>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",1378941420,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_description,resolved
+Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,"[02:06:08] <Reedy> Can someone depool mw1154 from the image scaler cluster?
+[02:06:20] <paravoid> what's wrong with it?
+[02:07:40] <Reedy> It's seemingly generating a lot more errors (by a factor of 2 or so) than any of the other scalers
+[02:07:41] <Reedy> https://bugzilla.wikimedia.org/show_bug.cgi?id=54045
+[02:08:32] <paravoid> root@mw1154:~# ls /sys/fs/cgroup/memory/mediawiki/job
+[02:08:33] <paravoid> ls: cannot access /sys/fs/cgroup/memory/mediawiki/job: No such file or directory
+[02:08:35] <paravoid> blergh
+[02:09:01] <paravoid> fixed
+[02:09:58] <Reedy> is that's what's up with it?
+[02:10:05] <paravoid> yes, fixed
+[02:10:09] <Reedy> awesome
+[02:10:10] <Reedy> thanks",1379553025,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1379552717,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,Ganglia graphs suggest so (mw1154 has less activity) but I haven't specificly tested.,1379552393,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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),1379547506,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,Could this server be taken out of rotation until the issue is resolved?,1379546704,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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 <img> 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",1379391380,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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)",1379373885,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error,*** Bug 54188 has been marked as a duplicate of this bug. ***,1379373403,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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.",1378958845,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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).",1378950740,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378943525,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378943170,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378942177,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378941699,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+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",1378941647,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5ts3ggpcjypmoohi32ft,task_subcomment,NA
+"[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",1378771740,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_description,resolved
+"[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",1404843771,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link","Yay, thanks Bryan.",1404841358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1404837730,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1403864865,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1403810584,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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'.",1403805154,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.,1403743208,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.",1400529133,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.,1399426964,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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""
+      }
+    }",1399420245,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.",1399410121,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1399399638,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1399334206,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1398832805,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1398806849,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.,1398716142,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1398200919,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.",1398197371,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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)?,1398195477,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1398191798,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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. ***,1395351525,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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. ***,1392411945,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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.",1392334367,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+"[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",1378775517,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-itdw5f4y5avsmhjnkmu3,task_subcomment,NA
+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",1378584660,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_description,resolved
+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!",1404820885,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',<3,1404820538,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',The fix has been deployed at gerrit.wikimedia.org.,1404805916,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1404338417,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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!",1404309484,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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;",1404293518,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1404292325,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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!,1404290440,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1404244147,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1404228694,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1403876110,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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 <gerrit> -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",1403176280,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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 :-(",1403175765,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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/",1402965592,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Today again: https://gerrit.wikimedia.org/r/#/c/139047/,1402587645,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1402531001,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1402521845,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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"" :/",1392577169,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1391696645,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1389609979,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Is this related: https://gerrit.wikimedia.org/r/#/c/107036/ ?,1389538078,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1387292272,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1387290809,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',*** Bug 57483 has been marked as a duplicate of this bug. ***,1387290750,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1381404334,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1381388510,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',(Worked for me when I tried again),1380186401,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1380186331,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',Still seeing this error randomly.,1379791842,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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=",1378769029,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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.",1378764890,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch',We retained the same key for exactly this reason...,1378611129,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-uycqr5h5vgduf55buvs4,task_subcomment,NA
+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",1378504020,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_description,resolved
+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)",1384542962,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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.",1384509314,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+Review and deploy BetaFeatures extension,Why is this bug marked fixed?,1384493719,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+Review and deploy BetaFeatures extension,Ready to deploy.,1383178559,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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!!!!",1382980087,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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.",1380139390,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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",1379978838,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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).",1379703244,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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",1378507279,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-o4nfasrtm3o6yo3ndwdo,task_subcomment,NA
+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",1378444620,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_description,resolved
+Commit missing from mediawiki/exentions/MassMessage repo,"
+
+*** This bug has been marked as a duplicate of bug 53841 ***",1378697343,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378504584,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378499305,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378498136,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378494665,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.  =(,1378494584,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378490942,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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.",1378483919,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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",1378461586,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-gendcsutkyq5czjdhhzy,task_subcomment,NA
+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",1378345920,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-djr6oferphbxqbgynsnj,task_description,resolved
+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!",1381270319,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+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",1379609001,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+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!",1378942957,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+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",1378477476,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+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).",1378373175,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change,"Sorry 
+*7 Save button does not get enabled",1378345999,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-djr6oferphbxqbgynsnj,task_subcomment,NA
+[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.",1378338120,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_description,open
+[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. ",1686825388,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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",1682009947,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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",1682009851,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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"".",1536338087,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[EPIC] Use Parsoid HTML for all page views,Tagging this for the Web and Infrastructure teams.,1531152561,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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!",1453313802,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1446806999,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1446061348,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1446031849,PHID-USER-hxwwywcyzpooynxuo7a2,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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?",1446031440,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1443905863,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1443474280,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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.",1425275795,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[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?",1424285507,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+[EPIC] Use Parsoid HTML for all page views,*** Bug 53780 has been marked as a duplicate of this bug. ***,1378338206,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-bq2ty22xrf3ppn7g6cdz,task_subcomment,NA
+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",1378310460,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-sudk6gs3gu276aszhg6w,task_description,resolved
+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!",1381270232,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sudk6gs3gu276aszhg6w,task_subcomment,NA
+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",1379660392,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-sudk6gs3gu276aszhg6w,task_subcomment,NA
+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!",1378943075,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-sudk6gs3gu276aszhg6w,task_subcomment,NA
+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.,1378310693,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-sudk6gs3gu276aszhg6w,task_subcomment,NA
+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",1378309560,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-r65cbq4ixbupvjwfesjt,task_description,resolved
+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",1385506396,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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",1384940647,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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!",1381270119,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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",1379657853,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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!",1378943063,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-r65cbq4ixbupvjwfesjt,task_subcomment,NA
+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",1378300380,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bl2j543fwlnzihaohpzu,task_description,resolved
+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.",1399419475,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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.",1381625305,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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. """,1378382011,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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.",1378302842,PHID-USER-qlrpm27qlsmjh2pg65bg,False,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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),1378300544,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bl2j543fwlnzihaohpzu,task_subcomment,NA
+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",1378218960,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-kxfoifw5vn4mx32v4nnk,task_description,resolved
+run VE browser tests in vagrant,Closing since this looks like it has been fixed to me. Please reopen if needed.,1386002609,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-kxfoifw5vn4mx32v4nnk,task_subcomment,NA
+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=<value>
+7. export MEDIAWIKI_USER=<value>
+8. export MEDIAWIKI_PASSWORD=<value>
+9. export PATH=$PATH:/home/vagrant/.gem/ruby/1.9.1/gems/cucumber-1.3.8/bin 
+10. bundle exec cucumber <value>",1384965154,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kxfoifw5vn4mx32v4nnk,task_subcomment,NA
+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",1378156860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_description,resolved
+browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Basic test is merged and in place, so marking this bug resolved.",1392915139,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Change 111890 merged by jenkins-bot:
+[Browser test] Headless browser test(s)
+
+https://gerrit.wikimedia.org/r/111890",1392914962,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1392028920,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1391719839,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1391650517,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1391120795,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1391105926,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1391013095,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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}",1389822544,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Changing bug status since task in still WIP.",1388083976,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1387556100,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1387493238,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Created attachment 14138
+ve phantomjs
+
+**Attached**: {F11111}",1387468358,PHID-USER-fz7hkyvt4jypl76ieyol,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Created attachment 14137
+ve ff
+
+**Attached**: {F11109}",1387468337,PHID-USER-fz7hkyvt4jypl76ieyol,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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).",1387468303,PHID-USER-fz7hkyvt4jypl76ieyol,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.)",1387389239,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1387388081,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Created attachment 14130
+phantomjs screen shot
+
+**Attached**: {F11108}",1387386995,PHID-USER-fz7hkyvt4jypl76ieyol,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,Looks like phantomjs is blacklisted (or not whitelisted). There is no visual editor edit option (see screen shot).,1387386945,PHID-USER-fz7hkyvt4jypl76ieyol,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1387327633,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1386979767,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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}",1386956370,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"Created attachment 14080
+phantomjs screen shot
+
+**Attached**: {F11105}",1386926023,PHID-USER-fz7hkyvt4jypl76ieyol,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1386925978,PHID-USER-fz7hkyvt4jypl76ieyol,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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.",1386893033,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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 :-)",1386847077,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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).",1386811597,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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)",1386798514,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1386779767,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+browsertests: triggers for VisualEditor,"**jhall** wrote:
+
+Assigning to myself per an e-mail thread with Antoine, Chris, and Željko.",1386701650,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-wn3s7fg7p7dky4txupqd,task_subcomment,NA
+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",1378126200,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-l4bd6ekvg2ifcspk72da,task_description,invalid
+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.",1381269899,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l4bd6ekvg2ifcspk72da,task_subcomment,NA
+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.",1380647038,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-l4bd6ekvg2ifcspk72da,task_subcomment,NA
+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",1380442542,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-l4bd6ekvg2ifcspk72da,task_subcomment,NA
+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",1378013580,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-dvolbemwppvolpsqeen5,task_description,resolved
+VisualEditor: Removing formatting from part of a link causes a snowman,This was fixed two weeks ago; sorry for the slowness in replying.,1380838919,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dvolbemwppvolpsqeen5,task_subcomment,NA
+"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",1377807780,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-tes2snxxrdfko3p2bzft,task_description,resolved
+"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",1377813415,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tes2snxxrdfko3p2bzft,task_subcomment,NA
+"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",1377812789,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tes2snxxrdfko3p2bzft,task_subcomment,NA
+"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)",1377812736,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-tes2snxxrdfko3p2bzft,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> block with the experimental generic editor leads to brokenness because the attributes get blanked,"**Author:** `wojciech.r`
+
+**Description:**
+When I edit existing content in <source> 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",1377796560,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ikc6bitfegyn4srxsl45,task_description,resolved
+VisualEditor: Editing a <syntaxhighlight> 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.",1377958953,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> 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",1377909844,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> 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.,1377906465,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> block with the experimental generic editor leads to brokenness because the attributes get blanked,Related bug 53614,1377906431,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Editing a <syntaxhighlight> 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",1377905362,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ikc6bitfegyn4srxsl45,task_subcomment,NA
+VisualEditor: Pressing up while next to an inline image throws an exception,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377729540,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qgxcekjgfnhxpyipqdms,task_description,resolved
+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",1377732790,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qgxcekjgfnhxpyipqdms,task_subcomment,NA
+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",1377732192,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qgxcekjgfnhxpyipqdms,task_subcomment,NA
+"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",1377700800,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_description,resolved
+"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...",1397734119,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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!",1397732911,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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",1397705933,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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…",1397246077,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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. :)",1397245474,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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...",1397243067,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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).",1397241093,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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",1397151063,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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).,1396995419,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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?",1396986708,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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. :)",1396986438,PHID-USER-brn4v5ta45bnw4f5as3h,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages",*** Bug 56844 has been marked as a duplicate of this bug. ***,1384096303,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+"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.",1378409168,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-4lk6qpiuan7kbk6fch54,task_subcomment,NA
+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",1377652560,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-5jzwlml42c5fglrwtkfi,task_description,resolved
+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",1378261353,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5jzwlml42c5fglrwtkfi,task_subcomment,NA
+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",1377870978,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5jzwlml42c5fglrwtkfi,task_subcomment,NA
+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",1377652320,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bcaoiws3nuti2nsjkjz3,task_description,resolved
+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",1378261355,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bcaoiws3nuti2nsjkjz3,task_subcomment,NA
+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",1377870974,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bcaoiws3nuti2nsjkjz3,task_subcomment,NA
+"VisualEditor: Style Parsoid's <figure>s to look like MediaWiki's <div class=""thumb"">s rather than replacing them","Right now VisualEditor transforms the HTML Parsoid gives us (which is nicely-structured <figure>s) into the mess of <div>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 <div>s with known classes (and Parsoid's HTML has no <div>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",1377645300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w64szlorn34djdoon7kx,task_description,resolved
+"VisualEditor: Style Parsoid's <figure>s to look like MediaWiki's <div class=""thumb"">s rather than replacing them","Change 93417 merged by jenkins-bot:
+Render CE MWBlockImageNodes as styled <figure>s
+
+https://gerrit.wikimedia.org/r/93417",1386874034,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-w64szlorn34djdoon7kx,task_subcomment,NA
+"VisualEditor: Style Parsoid's <figure>s to look like MediaWiki's <div class=""thumb"">s rather than replacing them","Change 93417 had a related patch set uploaded by Jforrester:
+Render CE MWBlockImageNodes as styled <figure>s
+
+https://gerrit.wikimedia.org/r/93417",1386213845,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-w64szlorn34djdoon7kx,task_subcomment,NA
+"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",1377627060,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ibe45dq6vmicfsr4xdu7,task_description,open
+"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",1659473886,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ibe45dq6vmicfsr4xdu7,task_subcomment,NA
+"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.",1659377186,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-ibe45dq6vmicfsr4xdu7,task_subcomment,NA
+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",1377562620,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-cp6otuehw4hsidnwe5aw,task_description,resolved
+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. 
+
+",1421687542,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-cp6otuehw4hsidnwe5aw,task_subcomment,NA
+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. ",1421454194,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-cp6otuehw4hsidnwe5aw,task_subcomment,NA
+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",1377553200,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-uypsqiix32ng3uny23mo,task_description,resolved
+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",1378923308,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uypsqiix32ng3uny23mo,task_subcomment,NA
+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",1378548150,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uypsqiix32ng3uny23mo,task_subcomment,NA
+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",1377547260,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-epab3bnrysrclgspz74p,task_description,resolved
+VisualEditor: getNearestCorrectOffset doesn't ignore internal lists,"ElementLinearData#getRelativeOffset now checks for handlesOwnChildren, which prevents this from being an issue.",1397775737,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-epab3bnrysrclgspz74p,task_subcomment,NA
+VisualEditor: getNearestCorrectOffset doesn't ignore internal lists,May have been ameliorated by https://gerrit.wikimedia.org/r/98515,1385996866,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-epab3bnrysrclgspz74p,task_subcomment,NA
+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",1377547080,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-bzqqgbtatyk37hok3eeg,task_description,resolved
+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",1377800766,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bzqqgbtatyk37hok3eeg,task_subcomment,NA
+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",1377643119,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bzqqgbtatyk37hok3eeg,task_subcomment,NA
+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",1377545880,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7n32t2g7qmarlr4ehelo,task_description,resolved
+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",1377800814,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7n32t2g7qmarlr4ehelo,task_subcomment,NA
+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",1377545917,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7n32t2g7qmarlr4ehelo,task_subcomment,NA
+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",1377545460,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dtn35n72ll6dpl3csge6,task_description,resolved
+VisualEditor: Document loses focus after cutting a FocusableNode,Fixed in master; will be deployed on Thursday as part of the regular push.,1377634940,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dtn35n72ll6dpl3csge6,task_subcomment,NA
+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",1377634904,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dtn35n72ll6dpl3csge6,task_subcomment,NA
+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",1377545794,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dtn35n72ll6dpl3csge6,task_subcomment,NA
+VisualEditor: Document loses focus after cutting a FocusableNode,https://gerrit.wikimedia.org/r/#/c/81027/ fixes,1377545735,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dtn35n72ll6dpl3csge6,task_subcomment,NA
+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}",1377540900,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-si6erwgobtecdd3semnx,task_description,resolved
+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.",1377657008,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+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,1377638934,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+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.",1377638844,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+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).",1377633524,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13176
+example 3
+
+**Attached**: {F11316}",1377541077,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13175
+example 3
+
+**Attached**: {F11315}",1377541052,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13174
+example 2
+
+**Attached**: {F11312}",1377541029,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13173
+example 2
+
+**Attached**: {F11311}",1377541006,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?),"Created attachment 13172
+example 1
+
+**Attached**: {F11310}",1377540983,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-si6erwgobtecdd3semnx,task_subcomment,NA
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> 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",1377527760,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-2537ayvqomhm6aw6be77,task_description,resolved
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> tag in the wikitext,Fixed in master; will be deployed on Thursday as part of the regular push.,1377649422,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2537ayvqomhm6aw6be77,task_subcomment,NA
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> 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",1377649390,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2537ayvqomhm6aw6be77,task_subcomment,NA
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> 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",1377649253,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2537ayvqomhm6aw6be77,task_subcomment,NA
+VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> 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",1377621200,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-2537ayvqomhm6aw6be77,task_subcomment,NA
+"Don't allow nested <ref>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 <ref> tag (e.g., a bibliographic citation) inside another <ref> 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",1377373500,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-tht33qexrstttffqqdac,task_description,resolved
+"Don't allow nested <ref>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.",1378762753,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-tht33qexrstttffqqdac,task_subcomment,NA
+"Don't allow nested <ref>s, because Cite.php doesn't","(In reply to comment #0)
+> Adding a <ref> tag (e.g., a bibliographic citation) inside another <ref> 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?",1377510119,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-tht33qexrstttffqqdac,task_subcomment,NA
+"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",1377252120,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_description,resolved
+"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,1386984972,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",Verified in Betalabs,1386824907,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"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.,1386821195,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",okay but I checked it on Betalabs.,1386810610,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"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.",1386810532,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing",I am still seeing label Latex instead of Formula,1386810322,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"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",1386803523,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"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",1386383633,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+"VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing","I'm minded to just call it ""Formula"". Thoughts?",1385494999,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5rnk4jk4usyomimnhvgw,task_subcomment,NA
+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 (&amp;lt;nowiki&amp;gt;, or does just plain &lt;/nowiki&gt; 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 </nowiki> tag '''here'''.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377197160,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-q5vutkamr63367rd7zxs,task_description,resolved
+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",1402416475,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-q5vutkamr63367rd7zxs,task_subcomment,NA
+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",1401935637,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-q5vutkamr63367rd7zxs,task_subcomment,NA
+Nowiki tag not properly escaped when combined with other wiki markup,"This is a Parsoid serializer bug:
+
+[subbu@earth tests] echo '* &lt;/nowiki&gt; tag' | node parse --html2wt
+<nowiki>* </nowiki></nowiki> tag",1377208818,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-q5vutkamr63367rd7zxs,task_subcomment,NA
+"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",1377184320,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-jr5ycdlwcecuxieizpcv,task_description,resolved
+"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",1395076819,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"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",1395073111,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"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.,1379005591,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"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.",1377295726,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"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.",1377282757,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"Slugs are created inside empty table rows, creating pawns if used",Pawns are firmly VE territory. Moving to the VisualEditor product.,1377186019,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jr5ycdlwcecuxieizpcv,task_subcomment,NA
+"VisualEditor: Blank page, list, [enter] lose cursor","<<If I edit a blank page, press on the number list or bullet list icon and then press enter, the page remains blank but I have no cursor. Then other strange things start to happen. Pressing the link icon does not seem to do anything. I can press some icons (transclusion, references, etc) and they will appear, but if I then exit it, pressing it again or any other icon does nothing. Undo works though. FF 23.0.1 Win7. --Atethnekos (Discussion, Contributions) 21:27, 21 August 2013 (UTC) >>
+
+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",1377164400,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-l56nfzkytddrozusk6lo,task_description,resolved
+"VisualEditor: Blank page, list, [enter] lose cursor",This was fixed a long while ago.,1394678478,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l56nfzkytddrozusk6lo,task_subcomment,NA
+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",1377087600,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-oupbsd5554xmfpbxxxyj,task_description,resolved
+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",1379981366,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oupbsd5554xmfpbxxxyj,task_subcomment,NA
+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",1379981363,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oupbsd5554xmfpbxxxyj,task_subcomment,NA
+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",1379613881,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oupbsd5554xmfpbxxxyj,task_subcomment,NA
+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",1379613876,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oupbsd5554xmfpbxxxyj,task_subcomment,NA
+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",1377068880,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-gnj6uia6j4dqknm3pggn,task_description,resolved
+Implement non-linear transitions,"Change 116228 merged by jenkins-bot:
+Refactor and add non-linear tours, with tests
+
+https://gerrit.wikimedia.org/r/116228",1402332991,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gnj6uia6j4dqknm3pggn,task_subcomment,NA
+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",1395186275,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gnj6uia6j4dqknm3pggn,task_subcomment,NA
+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",1376955360,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_description,resolved
+VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),*** Bug 53317 has been marked as a duplicate of this bug. ***,1379576014,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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",1377642670,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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.,1377602894,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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",1377602821,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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 <h1> 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?",1377592907,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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",1377542371,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?),"<<First, I noticed a strange behavior where anything I typed at the end of that third line, if I then hit enter, it would be duplicated in the fourth line, and my cursor would move to the fifth (blank) line. I then took a look at the wikitext generated by VE, and it looked odd, so I copied it into a wikitext editor, and got a rather different looking result than VE was showing. Also, upon saving with VE, I got this result, which is the same as copying into wikitext editor, but not what VE was showing me. Chris857 (talk) 20:54, 25 August 2013 (UTC) >>
+
+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.",1377524357,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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.",1377524032,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+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.",1376955601,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ii6rhmjn7erj375xgev6,task_subcomment,NA
+about=null entries on <figure> 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]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 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",1376945880,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_description,resolved
+about=null entries on <figure> elements (because of dom-fragment reuse),I am marking this resolved. Haven't seen any reports about this in a while.,1389799516,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> elements (because of dom-fragment reuse),Is this still happening in production?,1386109794,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> elements (because of dom-fragment reuse),https://gerrit.wikimedia.org/r/#/c/83216/ fixes the dsr inconsistency warnings  reported in this bug.,1379553778,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> elements (because of dom-fragment reuse),"Sorry, I linked the wrong bug which is how you got the email ;-) .. fixing it.",1378333227,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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"" :)",1378333119,PHID-USER-vbyvvtbztxaeuaxelxx4,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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.",1378332012,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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.",1378331190,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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",1378326748,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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",1378323821,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> elements (because of dom-fragment reuse),"One more example:
+
+https://it.wikipedia.org/w/index.php?title=Dalmine&diff=61238476&oldid=61238456",1378225470,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+about=null entries on <figure> 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 <figure> tags with about=null",1377276929,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4oj2ukzhgtypk3cunb5o,task_subcomment,NA
+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",1376939940,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-oplpiaxofrtlrt3axphq,task_description,resolved
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"
+
+*** This bug has been marked as a duplicate of bug 45240 ***",1377348845,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-oplpiaxofrtlrt3axphq,task_subcomment,NA
+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",1376930160,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_description,resolved
+VisualEditor: Expose build number,FYI - This might be removed in {T119750},1448666920,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+VisualEditor: Expose build number,"Change 84334 merged by jenkins-bot:
+Hide version info if not available
+
+https://gerrit.wikimedia.org/r/84334",1379466654,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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",1379346926,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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.",1379107432,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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).",1379107220,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+VisualEditor: Expose build number,"Change 81877 merged by jenkins-bot:
+Expose version information in the client
+
+https://gerrit.wikimedia.org/r/81877",1377888800,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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",1377817078,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p4b2w3x4lqa7c5xyypgv,task_subcomment,NA
+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}",1376928720,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qsixjppbefsch6bho32b,task_description,resolved
+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",1377019844,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qsixjppbefsch6bho32b,task_subcomment,NA
+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",1376928825,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qsixjppbefsch6bho32b,task_subcomment,NA
+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",1376863380,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-uwxs5htjvrwhn73aykjk,task_description,resolved
+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.",1378958990,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uwxs5htjvrwhn73aykjk,task_subcomment,NA
+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!",1378943150,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-uwxs5htjvrwhn73aykjk,task_subcomment,NA
+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?",1376949133,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uwxs5htjvrwhn73aykjk,task_subcomment,NA
+"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 <click>, and I have the arrow pointer.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376814420,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-j5vjfdev7u6pvuctl7bs,task_description,declined
+"VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing","Still can't reproduce, unfortunately. :-(",1406756283,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j5vjfdev7u6pvuctl7bs,task_subcomment,NA
+"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",1376816801,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-j5vjfdev7u6pvuctl7bs,task_subcomment,NA
+"VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing","Created attachment 13119
+screenshot, I lied
+
+**Attached**: {F11406}",1376814590,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-j5vjfdev7u6pvuctl7bs,task_subcomment,NA
+"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 <return> 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}",1376813040,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-4rr6da3rjeo7zsqa7vfz,task_description,declined
+"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. :-(",1377831473,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rr6da3rjeo7zsqa7vfz,task_subcomment,NA
+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:
+
+<table><tr title=""{{echo|foo}}""></tr></table>
+
+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 '<div title=""{{echo|foo}}"">{{echo|</div>}}' | 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",1376628000,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cxh6tjsfd6x3hseyrbib,task_description,resolved
+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.",1386110602,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cxh6tjsfd6x3hseyrbib,task_subcomment,NA
+Move info about template-affected attributes from meta tags into data-mw,Meta tags in foster-parentable positions aren't really an issue anymore.,1380306722,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-cxh6tjsfd6x3hseyrbib,task_subcomment,NA
+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}",1376490900,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bdoqslcxagfk2qftlhdb,task_description,resolved
+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",1391808827,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bdoqslcxagfk2qftlhdb,task_subcomment,NA
+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",1391358454,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bdoqslcxagfk2qftlhdb,task_subcomment,NA
+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].",1391358288,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-bdoqslcxagfk2qftlhdb,task_subcomment,NA
+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",1376488380,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-4hkjv2ath5m5txk2nfy2,task_description,resolved
+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",1376509523,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4hkjv2ath5m5txk2nfy2,task_subcomment,NA
+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",1376491490,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4hkjv2ath5m5txk2nfy2,task_subcomment,NA
+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
+<meta charset='utf-8'><p data-parsoid ...</p><br class=""Apple-interchange-newline"">
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52770",1376343780,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-5nevglmngclvgx6tccw2,task_description,resolved
+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.),1381158661,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5nevglmngclvgx6tccw2,task_subcomment,NA
+VisualEditor: Pasting block level elements can lose annotations,Can't reproduce.,1381156961,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5nevglmngclvgx6tccw2,task_subcomment,NA
+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",1376320140,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-66ginvgnolmwprgt3cuj,task_description,resolved
+VisualEditor: Edit to a template somehow removing equals signs in markup?,AFAICT this is fixed; no recurrences in months have been reported.,1421281940,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-66ginvgnolmwprgt3cuj,task_subcomment,NA
+VisualEditor: Edit to a template somehow removing equals signs in markup?,Aha; sorry :).,1376321896,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-66ginvgnolmwprgt3cuj,task_subcomment,NA
+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",1376320887,PHID-USER-5c526sthsodab4l3hur6,False,PHID-TASK-66ginvgnolmwprgt3cuj,task_subcomment,NA
+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 <jenkins-bot@gerrit.wikimedia.org>
+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}",1376317860,PHID-USER-26asvhtv4jalaeeuigbm,False,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_description,resolved
+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",1376424244,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_subcomment,NA
+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",1376342314,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_subcomment,NA
+Regression: Wikitext for new lists has unnecessary newlines after bullets,git bisect shows that c0de1d5839430e9fde79ff4195caf6841baab0d3 is the culprit.  Will investigate and fix.,1376341085,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_subcomment,NA
+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 ""<ul><li><p>a</p></li></ul>"" | node parse --html2wt
+Incompatible constraints 1: LI P { a: { min: 0, max: 0 }, b: { min: 1, max: 2 }, min: 0, max: 0 }
+* 
+a",1376340885,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cclb4wsdr7iky3sqhmhw,task_subcomment,NA
+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",1376299800,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-o5baaacr6iodckukah5p,task_description,resolved
+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 ***",1377814470,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o5baaacr6iodckukah5p,task_subcomment,NA
+VisualEditor: Add a keyboard shortcut to trigger Save dialog,"> Ctrl+Shift+S
+
+Sorry, I meant Alt+Shift+S",1376299882,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-o5baaacr6iodckukah5p,task_subcomment,NA
+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",1376191500,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_description,resolved
+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!",1377202396,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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",1377164931,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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",1377027656,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,"Patch has been reverted due to other issues, sadly.",1376960981,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters,Doesn't seem to be happening any more.,1376937358,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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).",1376922530,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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.",1376585969,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-cmua6cyyxv7g5lccv5gd,task_subcomment,NA
+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",1376179080,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_description,resolved
+Enable Echo / Notifications on se.wikimedia.org,Seems like this wiki was included in the last roll-out.,1382727600,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_subcomment,NA
+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.",1376514498,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_subcomment,NA
+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 ...",1376513998,PHID-USER-dbudsaorcqut7sg3vvbi,False,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_subcomment,NA
+Enable Echo / Notifications on se.wikimedia.org,"I don't think Echo is under general deployment yet.
+
+CC'ing Fabrice",1376185892,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-l2ev3r2fbwgu3qyqlxqi,task_subcomment,NA
+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",1376107740,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7ldpzjc4tuyxvsjssopj,task_description,resolved
+VisualEditor: Register each VE experimental feature individually with the BetaFeatures extension,Done in gerrit 91108.,1383280071,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7ldpzjc4tuyxvsjssopj,task_subcomment,NA
+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",1378918492,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7ldpzjc4tuyxvsjssopj,task_subcomment,NA
+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",1376287586,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7ldpzjc4tuyxvsjssopj,task_subcomment,NA
+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",1376050440,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fbqhcge4qrnba67okcqc,task_description,resolved
+VisualEditor: Link suggestions list should vertically scroll if there's insufficient room for them on-screen,"No, it was in error. Sorry!",1393635105,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fbqhcge4qrnba67okcqc,task_subcomment,NA
+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?",1393633971,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-fbqhcge4qrnba67okcqc,task_subcomment,NA
+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.,1393632732,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fbqhcge4qrnba67okcqc,task_subcomment,NA
+[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}",1375990260,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_description,resolved
+[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",1409943658,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,*** Bug 55457 has been marked as a duplicate of this bug. ***,1409942617,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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",1409942585,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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",1393344878,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,Rephrasing bug title as it was cut-off.,1392115165,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,"Thanks, Bartosz.",1390506925,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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",1390506812,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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.",1390506798,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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.,1390406732,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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)?",1387200972,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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)?",1385396423,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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.",1381622838,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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?",1381257412,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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,1381257077,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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 (<div id=""mw-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.",1381256567,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events,*** Bug 55457 has been marked as a duplicate of this bug. ***,1381254044,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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.",1376072941,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+[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}",1375991155,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-hf3lpbfwtlmq4fqfsw75,task_subcomment,NA
+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 '<h2>Life and career</h2>' to '<h2>Life and careeer</h2>'
+$ 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<BR>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.<ref>{{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]]}}</ref> 
+-| 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'''<ref>[http://www.mlive.com/entertainment/saginaw/index.ssf/2008/08/ravensymone_steps_out_of_chara.html]</ref>, (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]]''<!-- Per http://www.imdb.com/name/nm0712368/filmoseries#tt0086687 her first episode of ""A Different World"" was Nov. 2, 1989, while her first Cosby Show episode was Sept 21, 1989. --> 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]].<ref>[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.</ref> 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.<ref name=""billboard.com"">[{{BillboardURLbyName|artist=raven-symoné|chart=Billboard 200}} Raven-Symoné]. Billboard.com. Retrieved 2012-05-19.</ref> 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,<ref name=""GKSAT"">[http://blog.vh1.com/2012-12-02/and-the-1-greatest-kid-star-of-all-time-is/ Greatest Kid Star Of All Time]</ref> and ranked number one on ''Loop21''{{'s}} ""10 Richest Black Actresses Under 40"" list.<ref name=""RBAU40"">[http://www.loop21.com/entertainment/10-richest-black-actresses-under-40 10 Richest Black Actresses Under 40]</ref>
+ 
+-==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]] <ref>http://www.tv.com/people/raven-symone/</ref><ref>http://xfinity.comcast.net/slideshow/entertainment-aachildactors/3/</ref><ref>http://ethnicelebs.com/raven-symone</ref><ref name=""imdb"">http://www.imdb.com/name/nm0712368/bio</ref><ref>http://www.nndb.com/people/017/000103705/</ref> and [[Native Americans in the United States|Native American]] ancestry.<ref name=""imdb"" /> At age three, her family moved to [[Ossining (village), New York|Ossining, New York]] where she attended Park School.<ref name=""birthplace"">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.</ref><ref>[http://ftp.rootsweb.com/pub/usgenweb/la/winn/bios/sym1569.txt Rootsweb.com]{{Dead link|date=May 2010}}</ref> 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",1375953720,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-s4knko26mc6rjznucnmu,task_description,resolved
+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.,1377029359,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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.",1376528533,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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",1375981137,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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",1375978007,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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.",1375976525,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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.",1375974012,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-s4knko26mc6rjznucnmu,task_subcomment,NA
+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",1375847280,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_description,resolved
+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 ***",1377808859,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1377808647,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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. ***,1377808418,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376142164,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376106189,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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!",1376075501,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376074801,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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).",1376074522,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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}",1376074189,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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}",1376073840,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376073813,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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.",1376073316,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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?",1375847955,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kpx3x3zovypfoultwmwq,task_subcomment,NA
+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",1375737000,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-puu746mglczm4q4dlq2x,task_description,resolved
+VisualEditor: Dragging mouse clicks VE buttons upon release,"I cant reproduce any combination supported on Linux, or Firefox/Windows/monobook.",1380610142,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-puu746mglczm4q4dlq2x,task_subcomment,NA
+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",1380546794,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-puu746mglczm4q4dlq2x,task_subcomment,NA
+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.",1375794161,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-puu746mglczm4q4dlq2x,task_subcomment,NA
+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.",1375737768,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-puu746mglczm4q4dlq2x,task_subcomment,NA
+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",1375635660,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_description,resolved
+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",1411778780,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+VisualEditor: Inspectors should not display below visible page area,"(This only affects inspectors, and they're a VE feature; moving.)",1411777234,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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",1411771949,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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",1411766928,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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",1411759324,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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?).,1405377923,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zoxqzhcrz3axmm25xk3m,task_subcomment,NA
+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",1375600380,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-qi4sreqcffmkf7rnalbq,task_description,resolved
+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",1392856750,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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",1392748395,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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.",1392403289,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+VisualEditor: Cannot apply annotations to link in specific case in Firefox,Can't reproduce in FF 27. Can someone else?,1392390005,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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.",1390418119,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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).",1375600824,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-qi4sreqcffmkf7rnalbq,task_subcomment,NA
+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",1375562940,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_description,resolved
+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.",1377557411,PHID-USER-7zhn2ep5wvjhxetsbb6n,True,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+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?",1377527169,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+VisualEditor: Top bar not staying at top,Will the fix of Bug 52441 (awaiting deployment) also solve this?,1375991784,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+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.",1375606053,PHID-USER-7zhn2ep5wvjhxetsbb6n,True,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+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.",1375604655,PHID-USER-7zhn2ep5wvjhxetsbb6n,True,PHID-TASK-bygn32hj7tnm3bhqdwpl,task_subcomment,NA
+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",1375529520,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qmrrjmfnasuu75b532kc,task_description,resolved
+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",1398959330,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qmrrjmfnasuu75b532kc,task_subcomment,NA
+VisualEditor: Protected node css with * selector breaks some template layouts,"Created attachment 15263
+Screenshot of problem and patched version
+
+**Attached**: {F11282}",1398959289,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qmrrjmfnasuu75b532kc,task_subcomment,NA
+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",1398947768,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qmrrjmfnasuu75b532kc,task_subcomment,NA
+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",1375489200,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-ov7pqqy7izua2omo6knh,task_description,resolved
+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.,1376930015,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ov7pqqy7izua2omo6knh,task_subcomment,NA
+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?,1376929509,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ov7pqqy7izua2omo6knh,task_subcomment,NA
+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 <references />)? If so then this could be related to bug 52371,1376256998,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-ov7pqqy7izua2omo6knh,task_subcomment,NA
+"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",1375482780,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-sveofxpb25owm56vn52q,task_description,resolved
+"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",1375492758,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sveofxpb25owm56vn52q,task_subcomment,NA
+"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",1375482953,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sveofxpb25owm56vn52q,task_subcomment,NA
+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",1375473840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-acmmw5etc6s3hnjsoagh,task_description,resolved
+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",1376023354,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-acmmw5etc6s3hnjsoagh,task_subcomment,NA
+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",1376021746,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-acmmw5etc6s3hnjsoagh,task_subcomment,NA
+VisualEditor: Data model should be able to default between equivalent annotations,code/tt duplicate of bug 52352,1375543016,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-acmmw5etc6s3hnjsoagh,task_subcomment,NA
+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",1375473480,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-dixea6aehlzjvgpfccvz,task_description,resolved
+Update tours for new edit tab selectors,"Change 78026 merged by jenkins-bot:
+Update VE section edit selector
+
+https://gerrit.wikimedia.org/r/78026",1376526350,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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",1375865592,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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",1375477475,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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",1375477081,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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.",1375474521,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-dixea6aehlzjvgpfccvz,task_subcomment,NA
+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",1375472100,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-vzoa67je6467j364n6nw,task_description,resolved
+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.",1375487279,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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.",1375486752,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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.",1375485996,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+VisualEditor:  User guide should open in a new tab/window,"Now fixed in the code; next scheduled deployment is not until 15 August, however. :-(",1375474715,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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",1375473897,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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",1375473255,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+VisualEditor:  User guide should open in a new tab/window,Marking as high priority like similar bug 52093,1375472396,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-vzoa67je6467j364n6nw,task_subcomment,NA
+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",1375460760,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_description,resolved
+VisualEditor: Media insertion dialog should display a message if no media is found for the given search,Verified in production,1400794526,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+VisualEditor: Media insertion dialog should display a message if no media is found for the given search,Verified the fix in Betalabs,1400537169,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400535869,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400282641,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400282181,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400280097,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+VisualEditor: Media insertion dialog should display a message if no media is found for the given search,"Created attachment 15419
+Screenshot
+
+**Attached**: {F11195}",1400268429,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400268400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1400109025,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1399963305,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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.",1391711753,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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. ***,1391659253,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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"").",1376588485,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-v2iurekb2mj5nlfaied2,task_subcomment,NA
+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",1375459440,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bpmyhnrfcuvcbkkh3dqm,task_description,resolved
+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",1378335605,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bpmyhnrfcuvcbkkh3dqm,task_subcomment,NA
+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",1378240685,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bpmyhnrfcuvcbkkh3dqm,task_subcomment,NA
+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",1375424760,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5butgjmyg5i25tvyzxlh,task_description,resolved
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52739 has been marked as a duplicate of this bug. ***,1376521783,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52789 has been marked as a duplicate of this bug. ***,1376476088,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52433 has been marked as a duplicate of this bug. ***,1375991502,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,*** Bug 52326 has been marked as a duplicate of this bug. ***,1375936189,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector,"Now fixed in the code; next scheduled deployment is not until 15 August,
+however. :-(",1375475301,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+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",1375439587,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+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",1375429015,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+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.",1375428640,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5butgjmyg5i25tvyzxlh,task_subcomment,NA
+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",1375398120,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_description,resolved
+VisualEditor: references in image captions are not included in reflists,"Re-setting as FIXED, and have raised the regression as bug 57228.",1384844452,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+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)>>.",1384812491,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+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",1375469746,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+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",1375461230,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+VisualEditor: references in image captions are not included in reflists,"**kwwilliams** wrote:
+
+52300 may also be related.",1375399091,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7i5ifep2qqvrl24ie5dq,task_subcomment,NA
+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",1375343460,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-svgbuubly7i37677eqfj,task_description,resolved
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"
+
+*** This bug has been marked as a duplicate of bug 50822 ***",1398187598,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-svgbuubly7i37677eqfj,task_subcomment,NA
+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.",1375672513,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-svgbuubly7i37677eqfj,task_subcomment,NA
+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",1375328880,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ycfuexv2jknnm72vmgj2,task_description,resolved
+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.",1375423690,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ycfuexv2jknnm72vmgj2,task_subcomment,NA
+"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",1375306080,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-rk7rg7s3j76gm4lymrcv,task_description,resolved
+"VisualEditor (and possibly other beta tools) need an exposed, easy-to-use on/off switch",BetaFeatures is in place for this now.,1392032698,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rk7rg7s3j76gm4lymrcv,task_subcomment,NA
+"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",1375314628,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-rk7rg7s3j76gm4lymrcv,task_subcomment,NA
+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 <tt> ... </tt> 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}",1375299180,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-27y3ao6udiwcetvc5juo,task_description,resolved
+VisualEditor: Selection highlighting breaks if an inline alien wraps,*** Bug 67062 has been marked as a duplicate of this bug. ***,1403696547,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+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",1402962749,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+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",1402915741,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+VisualEditor: Selection highlighting breaks if an inline alien wraps,"Created attachment 13036
+wrapped inline alien: incorrect highlighting in firefox
+
+**Attached**: {F11840}",1375300000,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+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//",1375299322,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-27y3ao6udiwcetvc5juo,task_subcomment,NA
+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}",1375281660,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7gsk7m3csraunlup7tpi,task_description,resolved
+VisualEditor: Toolbar overlaps top of page links,"I guess https://bugzilla.wikimedia.org/show_bug.cgi?id=52433 is a duplicate then?
+Thanks.",1375957512,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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 ***",1375936189,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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",1375860454,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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.",1375560255,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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]]",1375291142,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7gsk7m3csraunlup7tpi,task_subcomment,NA
+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",1375192200,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-nirzuutzqnx7m4wim5ej,task_description,resolved
+VisualEditor: Localised tag description should link to content language documentation page,Fixed; we'll deploy this later today.,1375216402,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+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",1375216159,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+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",1375213768,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+VisualEditor: Localised tag description should link to content language documentation page,This was caused by gerrit 75559 - will partially-revert.,1375213677,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+VisualEditor: Localised tag description should link to content language documentation page,Right. It should probably be [[{{MediaWiki:visualeditor-descriptionpagelink}}|VisualEditor]].,1375213343,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+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",1375212767,PHID-USER-a6jwrurphpx6yl4coupk,False,PHID-TASK-nirzuutzqnx7m4wim5ej,task_subcomment,NA
+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",1375186860,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-jtms4kp7m57ptk6ccdpu,task_description,resolved
+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.",1378248030,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jtms4kp7m57ptk6ccdpu,task_subcomment,NA
+VisualEditor: Editing a pasted template alters copy buffer. Displayed result differs from saved result.,This appears to be fixed in master.,1378232623,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jtms4kp7m57ptk6ccdpu,task_subcomment,NA
+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"".",1376043644,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-jtms4kp7m57ptk6ccdpu,task_subcomment,NA
+"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",1375145700,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-alab5hdzxtgqi3cu2eqm,task_description,resolved
+"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/,1377888175,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-alab5hdzxtgqi3cu2eqm,task_subcomment,NA
+"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.",1375145903,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-alab5hdzxtgqi3cu2eqm,task_subcomment,NA
+"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}",1375145846,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-alab5hdzxtgqi3cu2eqm,task_subcomment,NA
+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",1375125960,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-rqtkbfxffdpbdagffzia,task_description,resolved
+VisualEditor: categories being duplicated,Going out in a little while.,1375223654,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+VisualEditor: categories being duplicated,"Change 76665 merged by jenkins-bot:
+Don't duplicate categories when unlisting
+
+https://gerrit.wikimedia.org/r/76665",1375223085,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+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",1375143043,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+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.",1375141989,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+VisualEditor: categories being duplicated,http://youtu.be/1rmp5rTDPOM,1375127596,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-rqtkbfxffdpbdagffzia,task_subcomment,NA
+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",1375117380,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-uxrs32aphojxiommp53x,task_description,resolved
+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.",1377824944,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+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",1377597258,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+VisualEditor: VE will not save multiple consecutive references,*** Bug 52269 has been marked as a duplicate of this bug. ***,1376325366,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+VisualEditor: VE will not save multiple consecutive references,Fixed and will get deployed in a little while.,1375222413,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+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",1375222340,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+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",1375221066,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+VisualEditor: VE will not save multiple consecutive references,"This happens because we send Parsoid something like
+
+<span about=""undefined"" typeof=""mw:Extension/ref"" data-mw=""...""></span><span about=""undefined"" typeof=""mw:Extension/ref"" data-mw=""...""></span>
+
+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 :)",1375218845,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-uxrs32aphojxiommp53x,task_subcomment,NA
+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",1375013460,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_description,resolved
+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",1395164666,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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",1395148872,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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.",1385423957,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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 ***",1385398575,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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!",1375092200,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-dp34rjmxuoe4ud2hxyic,task_subcomment,NA
+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",1375009500,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_description,resolved
+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.",1402837149,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),Bumping; this is happening 100% of the time now.,1394224211,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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?",1383600380,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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?",1383586954,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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.",1376489457,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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,1376488978,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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}",1376488730,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),"**jonathan_haas** wrote:
+
+I still can (FF23). Just managed on first try.",1376488379,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),Can't reproduce in Chrome or FF,1376488242,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙),This is possibly bug 51532,1375059258,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+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.,1375049196,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-4vm6pqlg5hib6dju3lvl,task_subcomment,NA
+"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",1375007700,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2klcawe4zbxemkcjvd56,task_description,resolved
+"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.,1415230310,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns",Done in gerrit 159310 and related stack.,1414522013,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"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.",1381788601,PHID-USER-brn4v5ta45bnw4f5as3h,False,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns",*** Bug 53325 has been marked as a duplicate of this bug. ***,1377528014,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns","Ok, will move it elsewhere. Thanks.",1375954624,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns","**jonathan_haas** wrote:
+
+(In reply to comment #2)
+> <<I was editing my userpage with VE today, and I noticed that, in the part
+> 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.",1375954522,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns","<<I was editing my userpage with VE today, and I noticed that, in the part 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 ).",1375954013,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"Be able to add or remove tables, table rows and table columns",I couldnt find another bug for creating tables.,1375049900,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-2klcawe4zbxemkcjvd56,task_subcomment,NA
+"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//",1374996540,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-q3emmq6fhgusggcncftz,task_description,resolved
+"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.,1384857530,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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…,1384842507,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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}",1384698145,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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.",1381187062,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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",1381186920,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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. ***,1380833625,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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",1378325649,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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//",1378325442,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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. ***,1377815261,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+"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//",1375061595,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-q3emmq6fhgusggcncftz,task_subcomment,NA
+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",1374993900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_description,resolved
+VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,Confirmed now fixed.,1404955719,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,WFM in Firefox,1404940599,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+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).",1403140941,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+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",1403077926,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,Was fixed by something Ed did a while ago.,1402003336,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+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",1377077317,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox,Reproduced.,1375050259,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-r5kajbzeeq4xhzra4a5e,task_subcomment,NA
+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",1374967920,PHID-USER-2rwkb3az6uklfhh5aqw5,False,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_description,resolved
+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.",1384881631,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+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",1384837089,PHID-USER-qlrpm27qlsmjh2pg65bg,False,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+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.),1384809283,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+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.",1378073148,PHID-USER-qlrpm27qlsmjh2pg65bg,False,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+VisualEditor: [Regression] Reference list not being updated during editing session,"Confirmed.  Use existing reference shows original references, before they were modified.",1375051990,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-3gmemcjr7w4kdsoeiv6t,task_subcomment,NA
+"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",1374966180,PHID-USER-2rwkb3az6uklfhh5aqw5,False,PHID-TASK-ehj46yftpulklnhzc5nl,task_description,resolved
+"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. ***,1385374664,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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.",1377019526,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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",1377019484,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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",1377019336,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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.",1376611609,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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",1376554077,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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.",1375231690,PHID-USER-2rwkb3az6uklfhh5aqw5,False,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+"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?",1375052081,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ehj46yftpulklnhzc5nl,task_subcomment,NA
+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)
+<ref>[http://www.koreatimes.co.kr/ (The Korea Times)][http://www.koreatimes.co.kr/www/news/nation/nation_view.asp?newsIdx=5635&categoryCode=115 <!-- Bot generated title -->]</ref>
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1374878820,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-jhcapgyaxz3ow5vafpun,task_description,resolved
+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.",1406598194,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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.",1403909628,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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",1403905782,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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",1403299185,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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|Bar<!--Baz-->Quux]] and change the link target, you'll split the link: [[Foo2|Bar]][[Foo|<!--Baz-->]][[Foo2|Quux]] (that's also what happened here)
+* If you have Foo<!--Bar-->Baz, it renders as ""FooBar"". If you then make that italic, you'll get ''Foo''<!--Bar-->''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()",1403149757,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jhcapgyaxz3ow5vafpun,task_subcomment,NA
+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",1374875220,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_description,resolved
+browsertests: triggers for ULS,The job got fixed yesterday and browser tests are passing right now. It is not blocking changes yet though.,1386338190,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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.",1385574363,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+browsertests: triggers for ULS,"Change 97741 merged by jenkins-bot:
+ULS browsertests on check pipeline
+
+https://gerrit.wikimedia.org/r/97741",1385477743,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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",1385477681,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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.",1385412598,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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/",1385379817,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+browsertests: triggers for ULS,Moving this under Continuous Integration radar.,1380112899,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+browsertests: triggers for ULS,Have added bug 53691 for the same for the VisualEditor repo.,1378156956,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+browsertests: triggers for ULS,What about running the tests on patch submission?,1377877531,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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/",1377860181,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-vzhy73evvtw5m5ueeyz3,task_subcomment,NA
+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",1374869820,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_description,resolved
+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.,1376621406,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+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",1376621086,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+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",1376488129,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),It's obviusly inviting you to play chess :),1376487625,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun),I've reproduced a few of these permutations.,1374905493,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-sqeh7jyki3euhm6uvc2p,task_subcomment,NA
+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}",1374867180,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-7cagldmd3jobcif24ufn,task_description,declined
+VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),This appears to now be fixed - marking as WORKSFORME.,1394224334,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+VisualEditor: Inserting template into slug throws JS error (causing dialogs to break),I can't reproduce this.,1383172136,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+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?,1374879833,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+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.",1374870395,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+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?",1374867555,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7cagldmd3jobcif24ufn,task_subcomment,NA
+VisualEditor: Write newFromDocumentReplace so editing document slices is simple,"
+--------------------------
+**Version**: unspecified
+**Severity**: major",1374855900,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_description,resolved
+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",1380228356,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_subcomment,NA
+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",1380145599,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_subcomment,NA
+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",1379533053,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_subcomment,NA
+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",1374855973,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-oq4h4k5rxxh5mzsezcrf,task_subcomment,NA
+"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",1374846180,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-kcmkos4wcsglqvinne4e,task_description,resolved
+"VisualEditor: Make the ""wikitext"" link of the popup open in a new window",This is now done and we'll get it deployed soon.,1375203313,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kcmkos4wcsglqvinne4e,task_subcomment,NA
+"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",1375201479,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kcmkos4wcsglqvinne4e,task_subcomment,NA
+"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",1375189915,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kcmkos4wcsglqvinne4e,task_subcomment,NA
+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}",1374810540,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_description,resolved
+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.",1460010223,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,*** Bug 52895 has been marked as a duplicate of this bug. ***,1377001419,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,*** Bug 52062 has been marked as a duplicate of this bug. ***,1376490819,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+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",1375288239,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,"See also:
+* [[Wikipedia talk:Edit filter#Abusefilter bug on mobile version]]",1375279646,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+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",1374839212,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+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.",1374837132,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,Hoo suspects that this is a problem with VisualEditor. Copying a few folks accordingly.,1374832035,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+APIEditBeforeSave isn't replacing sections like the documentation claims,"Marius, can you take a look at these? Chris is on vacation right now.",1374810663,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+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",1374810629,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-v4wsjl2yostcro6yfl5m,task_subcomment,NA
+"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",1374764040,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-rlrxpsau6vww7ypqckon,task_description,resolved
+"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",1411174708,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rlrxpsau6vww7ypqckon,task_subcomment,NA
+"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",1411171994,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rlrxpsau6vww7ypqckon,task_subcomment,NA
+"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.",1376122157,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rlrxpsau6vww7ypqckon,task_subcomment,NA
+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",1374729120,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_description,resolved
+VisualEditor: floating toolbar causes scrolling of large pages to be very slow,Merged and deployed.,1375232987,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+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",1375223509,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+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",1375072077,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+VisualEditor: floating toolbar causes scrolling of large pages to be very slow,https://gerrit.wikimedia.org/r/#/c/76241/,1375057326,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+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? :-)
+
+<Krinkle> 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
+<Krinkle> most notably the fact that floating calculation for ve toolbar calls offset() each time
+<Krinkle> which is a repaint for something that is unlikely to ever change
+<Krinkle> I realised it when I was doing mwnotify but never remembered to fix it in VE",1374730873,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+VisualEditor: floating toolbar causes scrolling of large pages to be very slow,@Krinkle: How are you going to fix this? :-),1374730687,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-y7lnjkpbhgxsbrsuxizc,task_subcomment,NA
+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",1374728460,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_description,resolved
+VisualEditor: Deleting plain text from a large page with backspace or delete is very slow,Merged and deployed.,1375233739,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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",1374887599,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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",1374880443,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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.,1374854401,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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",1374853391,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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",1374849799,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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.",1374802942,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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]",1374801722,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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 ;)",1374797517,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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?",1374793855,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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]	<RoanKattouw> 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?",1374793262,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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.",1374733149,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+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().",1374731780,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-bd27gm56r2au6k3ieg34,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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",1374711420,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_description,resolved
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> with log entry,"Change 119204 merged by jenkins-bot:
+Show blockedtext message in edit notices
+
+https://gerrit.wikimedia.org/r/119204",1395874946,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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",1395091521,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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.",1395077371,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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.",1395076588,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> 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?",1392078894,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> with log entry,"Created attachment 12954
+What a blocked user sees immediately they the source editor loads
+
+**Attached**: {F11061}",1374711764,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> with log entry,"Created attachment 12953
+What a blocked user sees when they try to save an edit in VE
+
+**Attached**: {F11060}",1374711656,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-6wbe37ccwgagtoa3kdhv,task_subcomment,NA
+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",1374710220,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_description,resolved
+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",1377889947,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+VisualEditor: Can't re-use a reference belonging to non-default group,Now fixed in master and will be deployed next week.,1377889863,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+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",1377885714,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+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",1377885380,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+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.",1377881801,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-qsnt7zdtnfm5xnawmteg,task_subcomment,NA
+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",1374709740,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-a2p56mvfah4kifyqy327,task_description,resolved
+VisualEditor: Saving fails silently for some blocked users,This was fixed in the fix for bug 52004.,1396032185,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a2p56mvfah4kifyqy327,task_subcomment,NA
+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",1374742787,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-a2p56mvfah4kifyqy327,task_subcomment,NA
+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",1374704160,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_description,resolved
+VisualEditor: Thumb images are missing appropriate CSS classes,Now fixed in master and will be deployed in a few minutes' time.,1374793893,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_subcomment,NA
+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",1374792604,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_subcomment,NA
+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",1374705671,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_subcomment,NA
+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",1374705278,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xnmn6i6yc73dhywaqm2m,task_subcomment,NA
+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}",1374695580,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-ph24e22ltq2s3oztatem,task_description,resolved
+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.",1383848723,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+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",1383813525,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+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.",1383785800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+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 (?),1380836632,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+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.,1380534678,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ph24e22ltq2s3oztatem,task_subcomment,NA
+"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",1374694260,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_description,resolved
+"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.,1374700983,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_subcomment,NA
+"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",1374700767,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_subcomment,NA
+"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",1374699991,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_subcomment,NA
+"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",1374694774,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-nlgy7km52ntxkqvlqnu2,task_subcomment,NA
+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",1374691440,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_description,duplicate
+VisualEditor: Clicking the hyper link button twice breaks the button.,"
+
+*** This bug has been marked as a duplicate of bug 51404 ***",1383173187,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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""",1374864536,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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.",1374863634,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+VisualEditor: Clicking the hyper link button twice breaks the button.,I was able to reproduce following the steps in comment 3.,1374704173,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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}",1374703953,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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.",1374703277,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+VisualEditor: Clicking the hyper link button twice breaks the button.,"Error screenshot.
+
+**Attached**: {F11890}",1374702882,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+VisualEditor: Clicking the hyper link button twice breaks the button.,I can't reproduce this. Do you see any errors in your JS console?,1374691632,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wm36m5xxm3u54pgeyz4a,task_subcomment,NA
+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 &rlm; 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",1374686820,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-wfbovalkwufxdqplhata,task_description,resolved
+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.",1407753932,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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?",1407753368,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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
+> <span
+> 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 <onlyve>. This solution may be useful for other cases of
+> ""invisible
+> templates"".
+
+I love this proposal.",1383831673,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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 <span dir="""">...
+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 <onlyve>. This solution may be useful for other cases of ""invisible templates"".",1383679171,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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?",1383676142,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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.",1383642046,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+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.,1374686999,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-wfbovalkwufxdqplhata,task_subcomment,NA
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, 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' <new line> '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",1374664140,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-zc6v32lm5ytpux3undwt,task_description,resolved
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, 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.",1399418661,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zc6v32lm5ytpux3undwt,task_subcomment,NA
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, etc), leading to corruption, and prevents down arrow button navigation","In addition to <gallery>, 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.",1381624406,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-zc6v32lm5ytpux3undwt,task_subcomment,NA
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, 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.",1374680740,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zc6v32lm5ytpux3undwt,task_subcomment,NA
+"VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, 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'",1374667755,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-zc6v32lm5ytpux3undwt,task_subcomment,NA
+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}",1374655380,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-2siqskyqqgqcynauvs72,task_description,resolved
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,Both of the examples linked to work now.,1405201146,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,Partially mitigated by the above but I believe not fixed. Resetting.,1402533482,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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",1402525633,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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",1402321080,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,*** Bug 54301 has been marked as a duplicate of this bug. ***,1402294829,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,*** Bug 50970 has been marked as a duplicate of this bug. ***,1402294818,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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 .,1377775199,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access,"*overlapping blocks, or templates, or whatever, you understood me :)",1377699148,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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.",1377698588,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2siqskyqqgqcynauvs72,task_subcomment,NA
+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",1374630480,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_description,resolved
+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.)",1400621292,PHID-USER-n2ftvsjm34tosq65gpve,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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.",1400619950,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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?)",1400615811,PHID-USER-n2ftvsjm34tosq65gpve,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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. ***,1398102157,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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.",1381187048,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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",1381186917,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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",1378325620,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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. ***,1378247189,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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.""",1376643209,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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)",1375435729,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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. ***,1374880815,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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 ***",1374630794,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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.",1374630602,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-rrnwu2dnzhxx4ckh2cdj,task_subcomment,NA
+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",1374622800,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-zrcmecxwpnqso5zyiauu,task_description,resolved
+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.,1375297527,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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.",1375126356,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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.""""",1374878013,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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.",1374632435,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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.",1374623153,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zrcmecxwpnqso5zyiauu,task_subcomment,NA
+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",1374604560,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jxtza5wxkt3lvc2yga75,task_description,resolved
+VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog,Now fixed in master.,1374779912,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jxtza5wxkt3lvc2yga75,task_subcomment,NA
+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",1374776211,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jxtza5wxkt3lvc2yga75,task_subcomment,NA
+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",1374756861,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jxtza5wxkt3lvc2yga75,task_subcomment,NA
+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]].",1374683040,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-jxtza5wxkt3lvc2yga75,task_subcomment,NA
+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",1374589920,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-sqexirvlnm7n526sp3a3,task_description,resolved
+VisualEditor: Language templates replaced by snowmen at Japanese Wikipedia,I think that this was finally fixed in Roan's great re-working of snowmen.,1407061575,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sqexirvlnm7n526sp3a3,task_subcomment,NA
+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",1375214101,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-sqexirvlnm7n526sp3a3,task_subcomment,NA
+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",1375075266,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-sqexirvlnm7n526sp3a3,task_subcomment,NA
+"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",1374568080,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_description,resolved
+"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",1374625642,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+"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",1374621278,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+"VisualEditor: By default, images should not set the alignment",*** Bug 51295 has been marked as a duplicate of this bug. ***,1374619928,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+"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",1374588399,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+"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?,1374588063,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-6pam6yoqknf5n2r6w5qx,task_subcomment,NA
+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",1374514020,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-lui5vpla74335t6r63nr,task_description,resolved
+VisualEditor: Autocompletion for template names doesn't work in RTL,"Done and will be deployed tomorrow. Thanks, Moriel!",1374634378,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lui5vpla74335t6r63nr,task_subcomment,NA
+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",1374518346,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-lui5vpla74335t6r63nr,task_subcomment,NA
+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}",1374510180,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-kjhdlfcx4jhz24dn5jl5,task_description,resolved
+VisualEditor: Location of the inspector menu is wrong for floated content in RTL wikis,Merged and will go out tomorrow.,1374637806,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kjhdlfcx4jhz24dn5jl5,task_subcomment,NA
+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",1374637503,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kjhdlfcx4jhz24dn5jl5,task_subcomment,NA
+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",1374526607,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kjhdlfcx4jhz24dn5jl5,task_subcomment,NA
+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",1374316620,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jvkszokywziqndkikfj4,task_description,resolved
+VisualEditor: [Regression] Dialog panels not scrollable,Done and will be deployed tomorrow.,1374634358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+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",1374605866,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,*** Bug 51810 has been marked as a duplicate of this bug. ***,1374497316,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,Patch by Rillke from bug 51793: https://gerrit.wikimedia.org/r/75083,1374489637,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,*** Bug 51793 has been marked as a duplicate of this bug. ***,1374489509,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,*** Bug 51671 has been marked as a duplicate of this bug. ***,1374331143,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+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",1374319290,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+VisualEditor: [Regression] Dialog panels not scrollable,Caused by 8409d16f0f2392cea321aa3d8d6bc692f3f04f27,1374318944,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jvkszokywziqndkikfj4,task_subcomment,NA
+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}",1374308460,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_description,resolved
+TemplateData: Create an editor for template data (in the wikitext editor),Follow-up in 60158.,1391795279,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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}",1391198497,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.  :)",1391189938,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1391186065,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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",1391177736,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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",1390823433,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+TemplateData: Create an editor for template data (in the wikitext editor),"No, this is the GUI we developed hidden behind $wgTemplateDataUseGUI.",1390431656,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.  :)",1390336136,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1389806818,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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",1386784147,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1375139849,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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",1374777939,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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}",1374776275,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+TemplateData: Create an editor for template data (in the wikitext editor),"Created attachment 12957
+Screenshot of http://tools.wikimedia.pl/~mlazowik/templatedata/
+
+**Attached**: {F11376}",1374775628,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1374510028,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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 <templatedata> 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 <templatedata/> 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",1374495793,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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.",1374489651,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+TemplateData: Create an editor for template data (in the wikitext editor),Tool = something at least as good as the TemplateDataEditor linked above.,1374489443,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+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. :)",1374486973,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jd5jq4oxcix7nauaawh2,task_subcomment,NA
+"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<br>1"" wraps correctly
+
+""Long text
+1""
+""Long text<br>"" and
+""Long text<br>
+<!--hidden-->"" 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",1374266280,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hbtmtpgjefyo637ujihd,task_description,resolved
+"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",1403047632,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+"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",1402916033,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+"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?",1402837289,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+"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. ***,1395169574,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+"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. ***,1394223928,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hbtmtpgjefyo637ujihd,task_subcomment,NA
+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",1374237180,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lskwjin7vud63rd4ruhi,task_description,declined
+VisualEditor: unlinking via linking tool triggers weird behaviors,"Worksforus, at it.wp. Will re-open if necessary.",1380650852,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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.",1380631760,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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).",1375039918,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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.",1374656653,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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!",1374644511,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lskwjin7vud63rd4ruhi,task_subcomment,NA
+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}",1374227460,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-y2l4ooxqksxji4wptopd,task_description,resolved
+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?",1378119303,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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.",1377959027,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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",1377910117,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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",1377901233,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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.""",1374423427,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-y2l4ooxqksxji4wptopd,task_subcomment,NA
+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}",1374179880,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7rwifffi3m7nv3vjbxms,task_description,resolved
+VisualEditor: Saving fails silently when the database is locked,Fixed and will get deployed in a few minutes' time.,1374676801,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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",1374676554,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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",1374658384,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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?",1374182584,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+VisualEditor: Saving fails silently when the database is locked,"**kwang** wrote:
+
+error while editing source code.
+
+**Attached**: {F11179}",1374180001,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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.",1374179974,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7rwifffi3m7nv3vjbxms,task_subcomment,NA
+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",1374128220,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-p5bbvutzsk36zk6seh2n,task_description,resolved
+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",1385506388,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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",1384946968,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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.,1381269307,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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.",1378943326,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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.",1374128971,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-p5bbvutzsk36zk6seh2n,task_subcomment,NA
+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.",1374089160,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_description,resolved
+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]]",1426626118,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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]]
+",1426622545,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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]]",1426388603,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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).",1430162161,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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).",1426382771,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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]]
+",1425330752,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nqg4k7suwubkfsf5dkfa,task_subcomment,NA
+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",1374074040,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-usa4c4in3z4ffsufnkoi,task_description,resolved
+VisualEditor: Reverse selections break copy paste functionality,Now merged; will go out with next push.,1377195467,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-usa4c4in3z4ffsufnkoi,task_subcomment,NA
+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",1377195266,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-usa4c4in3z4ffsufnkoi,task_subcomment,NA
+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",1377120336,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-usa4c4in3z4ffsufnkoi,task_subcomment,NA
+VisualEditor: Reverse selections break copy paste functionality,I can confirm this is still happening in Firefox 23/linux,1376732778,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-usa4c4in3z4ffsufnkoi,task_subcomment,NA
+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",1374065460,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-u4mzdxdhi5v6xlyw7zkb,task_description,resolved
+VisualEditor: CTRL+Z occasionally inserts a pawn,I believe these issues are now fixed.,1406599341,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u4mzdxdhi5v6xlyw7zkb,task_subcomment,NA
+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.",1379617320,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-u4mzdxdhi5v6xlyw7zkb,task_subcomment,NA
+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,1374065788,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-u4mzdxdhi5v6xlyw7zkb,task_subcomment,NA
+"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}",1374062040,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rygkkourrlt3am2ziugg,task_description,resolved
+"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.",1449517807,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-rygkkourrlt3am2ziugg,task_subcomment,NA
+"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?).",1401474051,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rygkkourrlt3am2ziugg,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Error: Offset could not be translated to a DOM element and offset: 2409""",Confirmed still happening.,1385386045,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rygkkourrlt3am2ziugg,task_subcomment,NA
+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",1374059640,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_description,resolved
+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.",1383848681,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_subcomment,NA
+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",1383813641,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_subcomment,NA
+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.",1383784994,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_subcomment,NA
+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",1374094589,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-qnbuhg3o2v7eth5y6stx,task_subcomment,NA
+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",1374057840,PHID-USER-5tluooawvjfhtqywnxag,False,PHID-TASK-qpzhi34lem7nwd6nbsu5,task_description,resolved
+VisualEditor: Too many clicks needed to dismiss inlink editor,This is now merged and will be deployed later.,1375304932,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qpzhi34lem7nwd6nbsu5,task_subcomment,NA
+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",1375304095,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qpzhi34lem7nwd6nbsu5,task_subcomment,NA
+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",1375222020,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qpzhi34lem7nwd6nbsu5,task_subcomment,NA
+"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",1374037140,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-hju3hugjlttehugtvu7d,task_description,resolved
+"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.,1383284035,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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",1378291458,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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.",1378127567,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"VisualEditor: Add a keyboard shortcut for ""Clear formatting""","Now merged and will go out with the next production push, probably tomorrow.",1375145540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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",1375145481,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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",1375143259,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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.,1375139344,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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 + \?",1375071949,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+"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)",1375071593,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-hju3hugjlttehugtvu7d,task_subcomment,NA
+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",1374029760,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vbuyxcfsri4ye35bdcvl,task_description,resolved
+VisualEditor: Reduce event rapid fire in CE,Yes.,1384939424,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vbuyxcfsri4ye35bdcvl,task_subcomment,NA
+VisualEditor: Reduce event rapid fire in CE,Can we now deem this to have been done?,1381347404,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vbuyxcfsri4ye35bdcvl,task_subcomment,NA
+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",1374009180,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-vs2q4kkygajmjexkudzc,task_description,resolved
+VisualEditor: Typing in Devanagari puts vowels in unexpected places,master looks good to me. Thanks!,1377206151,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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!",1377202382,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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",1377164925,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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",1377027648,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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.",1376935627,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-vs2q4kkygajmjexkudzc,task_subcomment,NA
+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",1374007020,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-cfoc7zk5vj22ygiycyil,task_description,resolved
+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",1385506391,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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",1384946958,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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.,1381269293,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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.",1374161590,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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.",1374132914,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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.",1374131873,PHID-USER-i5at67w766dqxs6ncxam,False,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+VisualEditor: Backspace deletes combined character clusters together with diacritics,"Could this be a dupe of -
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49233  ?",1374125163,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-cfoc7zk5vj22ygiycyil,task_subcomment,NA
+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",1374001860,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_description,resolved
+VisualEditor: Don't extend links over wordbreaks,*** Bug 51531 has been marked as a duplicate of this bug. ***,1374679397,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_subcomment,NA
+VisualEditor: Don't extend links over wordbreaks,Fixed and will get deployed in a few minutes.,1374677110,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_subcomment,NA
+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",1374677027,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_subcomment,NA
+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",1374076760,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fqzbhpnqgjp4qad6vrii,task_subcomment,NA
+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}",1374001560,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_description,resolved
+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.",1377800127,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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.",1377772919,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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 .",1377770479,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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. :-(",1375475243,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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",1375470233,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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 <pre> elements but we should be aware that this is broken, because any element can have white-space:pre attached to it, e.g.
+
+<span style=""white-space:pre"">    Foo</span>
+
+Will now normalise to
+
+<span style=""white-space:pre"">Foo</span>
+
+Long term we should look into just warning the user.",1375449067,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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",1375443506,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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
+> 
+> <nowiki> </nowiki>Foo
+> 
+> (previously <nowiki> Foo</nowiki>)
+> 
+> This is the correct behaviour.
+
+Also, with gerrit 76223 VisualEditor users can now edit through <nowiki>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.",1375208057,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,*** Bug 52252 has been marked as a duplicate of this bug. ***,1375203763,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,"With bug 50841 we now convert 
+
+[space]Foo
+
+to
+
+<nowiki> </nowiki>Foo
+
+(previously <nowiki> Foo</nowiki>)
+
+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?)",1375201550,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid,*** Bug 51509 has been marked as a duplicate of this bug. ***,1374168615,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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 <pre>-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 &nbsp; or if nowikis are acceptable, the spaces can be left alone.  In either case, this kind of edits should hopefully be rare.",1374006352,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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.",1374005921,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+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,1374001895,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mu2vgsj5i4mlfiswzx4o,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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",1374000660,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-q5qzozhueiwufmgr5jwq,task_description,resolved
+VisualEditor: Show the <newarticletext> message when creating a new article,Fixed and will get deployed in a few minutes.,1374676711,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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",1374676401,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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",1374659039,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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",1374605847,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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.",1374535182,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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.",1374507374,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+VisualEditor: Show the <newarticletext> 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).",1374302681,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-q5qzozhueiwufmgr5jwq,task_subcomment,NA
+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",1373981940,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eto6zg3t57jsyeutf64w,task_description,resolved
+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.",1408734627,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eto6zg3t57jsyeutf64w,task_subcomment,NA
+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.",1408687329,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eto6zg3t57jsyeutf64w,task_subcomment,NA
+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. ***,1401996119,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eto6zg3t57jsyeutf64w,task_subcomment,NA
+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)",1373982044,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eto6zg3t57jsyeutf64w,task_subcomment,NA
+"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",1373936940,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_description,resolved
+"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.,1375304939,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_subcomment,NA
+"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",1375304098,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_subcomment,NA
+"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. ***,1375303309,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_subcomment,NA
+"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",1375222005,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xodrhcpq6wj3seyvlmoc,task_subcomment,NA
+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",1373927820,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-5pkp6kncu5pzdahrd6qn,task_description,resolved
+VisualEditor: Transclusion dialog should prevent adding identically-named parameters (and aliases),"I'm going to assume ""yes"" given testing.",1406062458,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5pkp6kncu5pzdahrd6qn,task_subcomment,NA
+VisualEditor: Transclusion dialog should prevent adding identically-named parameters (and aliases),Works for me... Has this been fixed since it was reported?,1405980543,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-5pkp6kncu5pzdahrd6qn,task_subcomment,NA
+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",1373927580,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_description,resolved
+VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,*** Bug 51984 has been marked as a duplicate of this bug. ***,1383173187,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,This is now merged and will be deployed later.,1375304925,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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",1375304091,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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",1375222010,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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'.",1374998678,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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.",1374444476,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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.,1374342895,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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.",1374148846,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection,"Created attachment 12854
+Screenshot of problem
+
+**Attached**: {F11587}",1373927653,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+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.",1373927630,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dke6zkvtno2ooulod6bw,task_subcomment,NA
+"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}",1373926620,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6s22kiygdurpmwpk3lqs,task_description,resolved
+"AbuseFilter: API is responding with wikitext instead of HTML in the ""warning"" property",We will deploy this fix today.,1373987077,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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",1373945021,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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.",1373930726,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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.",1373930605,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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",1373929226,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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).",1373928926,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"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,1373928143,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-6s22kiygdurpmwpk3lqs,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","Sometimes 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.",1373910060,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_description,open
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","we should distinguish between visualeditor and templatedata.
+templatedata provides a syntax to describe the template behavior, and is used not just by visualeditor, but other tools too.
+
+whatever VE decides to do with ""illegal"" values is an interesting question, but TD itself should allow distinction between ""suggested values"" and ""legal values"", because the template syntax itself makes this distinction.  VE can ignore this distinction or not, but TD should provide this information.
+
+suggestedvalues serves templates that use {{#switch, and there are several different behaviors when param value is not present as one of the options: 
+  - the switch may have #default, which does something useful - IOW, an ""unsuggested"" value is still legal
+  - it can have no #default, practically ignoring the value
+  - the #default can trigger an error.
+
+TD syntax should allow better description of the behavior, so, e.g., ""template linting"" tools can detect and flag pages where a template with ""suggested values"" is used with ""unsuggested"" value: it can be an error worth flagging (2nd and 3rd cases above, where suggested values really means legal values), and not flag it for parameters whose behavior match the 1st case. 
+
+this is not a theoretical/hypothetical issue - such tools exist, and are used on several projects (see, e.g., Module:ParamValidator on hewiki and yiwiki).
+
+peace.",1641663466,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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 :)",1615828425,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","This can most certainly be closed via {T271825}. While it's not 100% the same, it should be sufficient to resolve the relevant use case.",1615826667,PHID-USER-u6ycqhfpa3k4yvlpxjt2,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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.",1582479107,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","A suggestion from https://www.mediawiki.org/wiki/Topic:Ve06hyihctm4p86n is to allow labels different from the actual value. It can be stored for example with:
+```lang=json
+""params"": {
+	""key"": {
+		""type"": ...,
+		""values"": [
+			{""label"": ..., ""value"": ...},
+			...
+		]
+	}
+}
+```
+Maybe plain strings should also be allowed for convenience, which could be transformed by the extension to
+```lang=json
+{""label"": null, ""value"": ...}
+```
+form. (I’d also suggest to always display the actual value in addition to the label, but that’s up to the consumers, of course.)",1577874176,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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]]",1532906726,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","Is this still on the docket? It's vital. Is there some other way of specifying valid string values in TemplateData (TD)? If not, that would appear to be a large oversight if TD is supposed to help users easily interact with template params",1510282456,PHID-USER-ruf4kh5stzv33ntxol2w,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)",It would also be useful to be able to use a set of possible values provided by some template/module.,1509551476,PHID-USER-6xgsmxxl62mgxypce6oa,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","That's something which would be extremely useful.
+
+I'm currently working on a proposal for ease Wikitionary contribution through templatedata. Such a feature would for example allow to select word category (verb, adjective…). ",1509222111,PHID-USER-6xgsmxxl62mgxypce6oa,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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]]",1483653112,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","Change 263655 had a related patch set uploaded (by Alex Monk):
+[WIP] Add a parameter key to limit possible valid values to a given set
+
+[[https://gerrit.wikimedia.org/r/263655]]
+",1452629730,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)",">>! In T53375#564935, @Krinkle wrote:
+>  params: {
+>   ""key"": {
+>     ""type"": ...
+>     ""values"": [ .. ]
+
+Seems a good way of specifying it, +1",1429186483,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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.",1612418862,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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.",1427614715,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" 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.",1400616112,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)",*** Bug 52754 has been marked as a duplicate of this bug. ***,1377830925,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","(In reply to comment #2)
+> Ping @TrevorParscal.
+> 
+> Since wikitext template editing will always be possible, we can't (yet?)
+> enforce values in VisualEditor. We can only suggest.
+> 
+> E.g. if a template parameter ""foo"" is specified as values: ['a', 'b']. and
+> wikitext has {{echo|foo=x}}, we need to provide a way to edit that, while
+> still
+> being able to set it to a or b.
+
+The ""normal"" way is a drop-down with the target of the drop-down being a free-entry text field that suggests entries (but does not block other entries).",1377657781,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)",*** Bug 50760 has been marked as a duplicate of this bug. ***,1377559681,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","Ping @TrevorParscal.
+
+Since wikitext template editing will always be possible, we can't (yet?) enforce values in VisualEditor. We can only suggest.
+
+E.g. if a template parameter ""foo"" is specified as values: ['a', 'b']. and wikitext has {{echo|foo=x}}, we need to provide a way to edit that, while still being able to set it to a or b.",1377559666,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+"TemplateData: Add parameter type for selecting one of predefined values (like ""<select>"" or ENUM)","See ""bug 50760 - Support suggested values"" which is quite similar.
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50760",1373968381,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-eddbh3tcvexylixr6tiy,task_subcomment,NA
+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
+",1373840940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-67oipsmostyhug2737rz,task_description,resolved
+VisualEditor: Set i18n toolbar icons for bold/italics,This is now done; we'll deploy this within the hour.,1373918452,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-67oipsmostyhug2737rz,task_subcomment,NA
+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",1373918327,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-67oipsmostyhug2737rz,task_subcomment,NA
+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",1373916753,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-67oipsmostyhug2737rz,task_subcomment,NA
+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",1373810580,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-faltfztxkqc5daxcntnx,task_description,resolved
+VisualEditor: Handle 'meta' templates better,Additional issue with empty HTML elements produced by templates (which are used for metadata) in bug 52551.,1375720301,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,Fixed and will get deployed in a few minutes.,1374676752,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,"Change 75331 merged by jenkins-bot:
+Handle meta-only transclusions as meta items
+
+https://gerrit.wikimedia.org/r/75331",1374676162,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,"I marked this as a dup of bug 49806, not dup of 51420.",1374604232,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+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",1374586930,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+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.,1374586909,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,"
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1374447614,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+VisualEditor: Handle 'meta' templates better,Another example given on WP:VEF is {{Link FA}},1374135248,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+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.",1374135077,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-faltfztxkqc5daxcntnx,task_subcomment,NA
+"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",1373764920,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sm4xza7t5teplcefqzij,task_description,resolved
+"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.,1421282222,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+"VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues",Very odd corruption; assigning.,1373816884,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+"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",1373800417,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+"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.",1373765414,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+"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.]",1373765293,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sm4xza7t5teplcefqzij,task_subcomment,NA
+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",1373723400,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-lufoybqaultvloukxdjz,task_description,resolved
+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",1391655762,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+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",1389677127,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+VisualEditor: Set image alignment in the media dialog,"It's not a problem with right-to-left languages ;)
+
+Removing the tracking bug.",1373915285,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+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",1373897055,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+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",1373896912,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+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.",1373883475,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-lufoybqaultvloukxdjz,task_subcomment,NA
+"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",1373723100,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_description,resolved
+"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 ***",1403005130,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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.,1401418955,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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. ***,1401418881,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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?,1387304036,PHID-USER-vm462i2ffbawnuo4mh3n,True,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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.""",1375444170,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+"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. ***,1375298515,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4hclm7qlzk6wj2x4xb2q,task_subcomment,NA
+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",1373672640,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-5am5k4waw47kga4kfuau,task_description,invalid
+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.,1399324087,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5am5k4waw47kga4kfuau,task_subcomment,NA
+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.",1373681941,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-5am5k4waw47kga4kfuau,task_subcomment,NA
+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.",1373680362,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-5am5k4waw47kga4kfuau,task_subcomment,NA
+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",1373656680,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_description,resolved
+tag_summary missing records,That was bug 52077. Closing this.,1382126117,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,"Whatever is causing that (maybe just a misconfigured local filter?), it's most likely not related to this bug.",1374793514,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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).",1374793105,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1374065627,PHID-USER-fuj45iylbizjg3yhehjt,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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",1374038167,PHID-USER-fuj45iylbizjg3yhehjt,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1374013186,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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...,1374009940,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1373998200,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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...",1373998082,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1373924036,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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).",1373909518,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1373887905,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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""
+  <tag>visualeditor</tag>
+  
+  rcid=""590032703"" timestamp=""2013-07-12T00:33:31Z"" 
+  <tag>mobile edit</tag>
+
+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.",1373677187,PHID-USER-fuj45iylbizjg3yhehjt,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,"**swalling** wrote:
+
+Just checked this on-wiki as well. Seems fixed.",1373672247,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,enwiki.tag_summary rebuild is complete.,1373671971,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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.",1373667429,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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",1373662814,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,Was it determined if any other databases apart from en.wp's one were affected?,1373662581,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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)",1373662298,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+tag_summary missing records,"Only seems to affect en.wp right now (works correctly on pl.wp and mw.org, for example).",1373656951,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3hxhzuqbp3dgpcaubftg,task_subcomment,NA
+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",1373632740,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-sojoibzwruxvdv55tvoj,task_description,resolved
+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",1373662141,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sojoibzwruxvdv55tvoj,task_subcomment,NA
+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",1373637959,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sojoibzwruxvdv55tvoj,task_subcomment,NA
+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.",1373637707,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sojoibzwruxvdv55tvoj,task_subcomment,NA
+VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''<sub>''bar''</sub> -> ''foo<sub>bar</sub>''),"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",1373632620,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vq64xxj3d54xo3daemjh,task_description,resolved
+VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''<sub>''bar''</sub> -> ''foo<sub>bar</sub>''),"
+
+*** This bug has been marked as a duplicate of bug 49873 ***",1373711757,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vq64xxj3d54xo3daemjh,task_subcomment,NA
+VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''<sub>''bar''</sub> -> ''foo<sub>bar</sub>''),Also https://en.wikipedia.org/w/index.php?title=Frobenius_solution_to_the_hypergeometric_equation&curid=16407499&diff=563915886&oldid=561013687,1373632675,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vq64xxj3d54xo3daemjh,task_subcomment,NA
+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",1373598840,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-toxebubahyyw4rmtx4vj,task_description,resolved
+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",1395164023,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-toxebubahyyw4rmtx4vj,task_subcomment,NA
+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",1395094433,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-toxebubahyyw4rmtx4vj,task_subcomment,NA
+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",1373533020,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_description,declined
+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.",1374675988,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,"major->minor, so it isnt red anymore.",1374650680,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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)",1374644987,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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. :-)",1374643164,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,Resolved-Fixed -> Resolved->Invalid.  What the?!,1374642996,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary,Now resolved; thanks all :).,1374601920,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1374595261,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1374588009,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1374338671,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1374309537,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+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.",1373537154,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-m4tvj6xkn7aqhr4yajip,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) 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
+<div class=""reflist references-small"" style><references /></div>
+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",1373499540,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-re6qm3cualjp5dczcmlc,task_description,resolved
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) 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).",1383140692,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) into wikitext,I can't reproduce this now using a simple test case.  Has it still been happening on pt.wp?,1383133476,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) into wikitext,"This happened again:
+https://pt.wikipedia.org/wiki/Haroldo_Palo_Jr.?diff=36430552",1374085008,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) 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.",1373760927,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) 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]]:
+> 
+> <h2 style=""cursor:help"" title=""Esta seção não é editável por razões técnicas.
+> Edite a página toda em vez disso."">Referências</h2>
+> <div class=""reflist references-small"" style=""""><references
+> group=""""></references></div>
+> 
+> 
+> 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 <h2>).",1373658096,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) into wikitext,"I don't know if this is relevant, but the same code ""{{referências}}"" expands to something different on [[pt:special:ExpandTemplates]]:
+
+<h2 style=""cursor:help"" title=""Esta seção não é editável por razões técnicas. Edite a página toda em vez disso."">Referências</h2>
+<div class=""reflist references-small"" style=""""><references group=""""></references></div>
+
+
+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",1373500632,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-re6qm3cualjp5dczcmlc,task_subcomment,NA
+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",1373498580,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_description,resolved
+VisualEditor: Double-click on a parameter in the selection menu should insert it,*** Bug 51165 has been marked as a duplicate of this bug. ***,1377527402,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_subcomment,NA
+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.",1373932741,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_subcomment,NA
+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",1373932430,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_subcomment,NA
+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",1373922497,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6ey7x6n5abzoqr3wo43j,task_subcomment,NA
+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",1373495580,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ft4ssckvycvjlzjy3fax,task_description,resolved
+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. ***,1373928303,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text,Fixed and merged.,1373926253,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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",1373926221,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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",1373925628,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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",1373499407,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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.",1373498121,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+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 &#9817).  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.",1373498038,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ft4ssckvycvjlzjy3fax,task_subcomment,NA
+"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",1373485740,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-nilflssh5x72tinfk7a6,task_description,resolved
+"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.",1394073325,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nilflssh5x72tinfk7a6,task_subcomment,NA
+"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).",1375325511,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nilflssh5x72tinfk7a6,task_subcomment,NA
+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",1373468880,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-qjailuyl4kenb2ytqa5a,task_description,resolved
+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 ***",1373928303,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qjailuyl4kenb2ytqa5a,task_subcomment,NA
+"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",1373408400,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-sby6wjdxcouq3g5mq67p,task_description,resolved
+"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.,1373421287,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+"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",1373421247,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+"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",1373412771,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+"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",1373410794,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+"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",1373409417,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sby6wjdxcouq3g5mq67p,task_subcomment,NA
+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",1373366640,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-l2askobdymn34t55t5lm,task_description,resolved
+VisualEditor: Resizing an image without an explicit size doesn't work,"
+
+*** This bug has been marked as a duplicate of bug 50645 ***",1374106684,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l2askobdymn34t55t5lm,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Attaching screenshot...
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373337720,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_description,resolved
+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",1390877338,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+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",1390853505,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,*** Bug 52205 has been marked as a duplicate of this bug. ***,1380221526,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,Same as bug 52205?,1380219226,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+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.",1373337951,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Created attachment 12794
+<h1> protrudes into wrapped toolbar in non-HD stylesheet
+
+**Attached**: {F11631}",1373337835,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+VisualEditor: Heading overlays toolbar in non-HD Vector integration,"Created attachment 12793
+Wrapping toolbar correctly pushes down <h1> in HD stylesheet
+
+**Attached**: {F11630}",1373337806,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-u4ds5rkvr4rcsxwqaoaz,task_subcomment,NA
+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",1373307420,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-it7sgrllp5k6su66uukw,task_description,resolved
+TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,Per report. ;-),1402013615,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,"Confirmed fixed in 1.24wmf7, yay :-)",1402012066,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1400886803,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1400866371,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1400865643,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1400865567,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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.",1400864330,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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?,1399842534,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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.",1395417398,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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.",1380898648,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1380867107,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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}} }} ).",1374776002,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1374641826,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+TemplateData: TemplateData is not available to VisualEditor if the template is a redirect,*** Bug 51791 has been marked as a duplicate of this bug. ***,1374641783,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-it7sgrllp5k6su66uukw,task_subcomment,NA
+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",1373297880,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_description,resolved
+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",1380474885,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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 <p> 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.",1380309457,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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",1380309327,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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.",1380214427,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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),1379886743,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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.",1376330120,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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. ***,1375199198,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox,Looking into it now.,1374627567,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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",1374082150,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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. ***,1374079615,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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. ***,1374079583,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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.",1373444097,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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?,1373421989,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mip6kupgxcxydyy26dwa,task_subcomment,NA
+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",1373295960,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_description,resolved
+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.",1403727795,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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.",1403715476,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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.",1395196799,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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 .",1391011992,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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.",1377807543,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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, ]]<nowiki/>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.",1374080214,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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|<nowiki/>]][[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",1373870516,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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'.",1373850602,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+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""?",1373319371,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-uxowmsznm5ykbiez7tm2,task_subcomment,NA
+Extension tags are not nowiki escaped during serialization.,"Typing certain tag based code into VE such as:
+
+<math>1+2=3</math>
+<ref>Hi</ref>
+
+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",1373295960,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-7rcg5rkjl6kyyl4elbfa,task_description,resolved
+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",1373307982,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7rcg5rkjl6kyyl4elbfa,task_subcomment,NA
+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",1373301144,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7rcg5rkjl6kyyl4elbfa,task_subcomment,NA
+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",1373238780,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-ur6l6l2ezqzug2nab347,task_description,resolved
+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.,1375298816,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ur6l6l2ezqzug2nab347,task_subcomment,NA
+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.",1373351277,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-ur6l6l2ezqzug2nab347,task_subcomment,NA
+VisualEditor: Selection highlight for templates/etc. mis-placed,*** Bug 50991 has been marked as a duplicate of this bug. ***,1373351191,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-ur6l6l2ezqzug2nab347,task_subcomment,NA
+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",1373232900,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-z5vtizhnd7zq6vobiqci,task_description,resolved
+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",1377734475,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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. ***,1377187521,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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.,1376519672,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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",1376519264,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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?",1376517055,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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.",1376507435,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis,confirmed on Arch linux with FF 22.,1373233082,PHID-USER-u7udgblfyop6qd5wxot6,False,PHID-TASK-z5vtizhnd7zq6vobiqci,task_subcomment,NA
+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",1373232060,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-kt3assypvj632tuitmf6,task_description,resolved
+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",1391915675,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kt3assypvj632tuitmf6,task_subcomment,NA
+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}",1373206260,PHID-USER-ixwg3kf22idjy7x4ncxf,False,PHID-TASK-vgr63prhj7eik7b2qkwd,task_description,resolved
+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",1383255765,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vgr63prhj7eik7b2qkwd,task_subcomment,NA
+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",1383180900,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vgr63prhj7eik7b2qkwd,task_subcomment,NA
+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}",1373209810,PHID-USER-ixwg3kf22idjy7x4ncxf,False,PHID-TASK-vgr63prhj7eik7b2qkwd,task_subcomment,NA
+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}",1373208580,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-vgr63prhj7eik7b2qkwd,task_subcomment,NA
+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",1373101500,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-he62ku3noedhtzp55bhf,task_description,resolved
+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.,1415382971,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-he62ku3noedhtzp55bhf,task_subcomment,NA
+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.",1414104265,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-he62ku3noedhtzp55bhf,task_subcomment,NA
+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}",1378792955,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-he62ku3noedhtzp55bhf,task_subcomment,NA
+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",1373091660,PHID-USER-yif6nz5uhka5cnltixpc,False,PHID-TASK-ofaluihol767l3yg5fjw,task_description,resolved
+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 ***",1373145698,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ofaluihol767l3yg5fjw,task_subcomment,NA
+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.",1373145158,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ofaluihol767l3yg5fjw,task_subcomment,NA
+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.",1373093279,PHID-USER-yif6nz5uhka5cnltixpc,False,PHID-TASK-ofaluihol767l3yg5fjw,task_subcomment,NA
+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 </p><img></img><p> rather than just the image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373080620,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4v36rjb5p4c3fhjflpoq,task_description,invalid
+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?).,1377894433,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4v36rjb5p4c3fhjflpoq,task_subcomment,NA
+VisualEditor: Inspecting image immediately after inserting it causes exception,*** Bug 51863 has been marked as a duplicate of this bug. ***,1374624697,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-4v36rjb5p4c3fhjflpoq,task_subcomment,NA
+"<nowiki> 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:
+
+<p>Hello my [[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].</p>
+
+… turns into:
+
+<p>Hello my <nowiki>[[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].</nowiki></p>
+
+… whereas ideally it should be minimal rather than maximal:
+
+<p>Hello my <nowiki>[[</nowiki>name<nowiki>]]</nowiki> is Julian and I live in the city of Rochester, New York with my friend Sandy; we write <nowiki>[[</nowiki>books<nowiki>]]</nowiki>.</p>
+
+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",1373063340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_description,resolved
+"<nowiki> 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.",1374182135,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)",This will likely be deployed later today.,1374181853,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1374181486,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1374033113,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1373426923,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1373411404,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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",1373395088,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki>-{ }-</nowiki> 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.",1373395037,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki>-{ }-</nowiki> 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...",1373390406,PHID-USER-zjzhrhmn36icnzbckqy4,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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).",1373390310,PHID-USER-zjzhrhmn36icnzbckqy4,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki>[[foo]]</nowiki>.  ""Closely occurring"" will be heuristic based, say within X chars.",1373388769,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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]] ==> &#91;&#91;Foo&#93;&#93;
+> 
+> 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.",1373388668,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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...",1373344988,PHID-USER-zjzhrhmn36icnzbckqy4,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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]] ==> &#91;&#91;Foo&#93;&#93;
+
+and the like.  Am I missing something that makes this problematic?",1373343101,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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?",1373340138,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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
+
+- <nowiki>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</nowiki>
+
+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.",1373064929,PHID-USER-fuj45iylbizjg3yhehjt,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki>..</nowiki> 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.",1373064668,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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 <nowiki> on ""normal"" text disabled language conversion on it too; we may want to <nowiki> wikitext meta characters only.",1373064371,PHID-USER-zjzhrhmn36icnzbckqy4,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+"<nowiki> 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.",1373064090,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-qf4vt6acq5wtvvlwympv,task_subcomment,NA
+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 ) {
+	$( '<style>' , {type: 'text/css', rel: 'stylesheet' } )
+	.text( css )
+	.appendTo ('head' );
+}
+
+// really no need to return anything: the single callsite ignores 
+// the return value anyway. anywho, you can prepend ""return"" 
+// to make it behave more like existing code if you really want to...
+
+
+peace.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=563037747#Heavy_Javascript_load_after_loading_some_articles.
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49935
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51073",1373056800,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_description,resolved
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #21)
+> It's resolved technically, 
+
+Closing this one then,
+
+> but we want to write proper documentation and
+> tests
+> for the fix. Assigning to myself.
+
+and split this to bug 54364, to clarify status.",1379659587,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"What's the progress on this, Amir?",1375774753,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"It's resolved technically, but we want to write proper documentation and tests for the fix. Assigning to myself.",1374249445,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Why is this still open?
+as far as i can see, the patch solved the issue. is there any report about any more problems here? 
+is anyone expected to do anything more regarding this issue? 
+if it's not closed now, is there any chance of this getting closed ever?
+
+peace.",1374249308,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"What about using .eachAsync (https://git.wikimedia.org/blob/mediawiki%2Fcore.git/HEAD/resources%2Fjquery%2Fjquery.async.js) instead of the .each loop over $( '*[lang], [style], [class]' ) ? Perhaps this is not the solution for this bug, but for bug 49935, but I'm not going to read through all those comments, and I think the .eachAsync is worth a try.",1373615617,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,*** Bug 51070 has been marked as a duplicate of this bug. ***,1373495384,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"The above patch makes the webfonts code about 4x faster in my testing. While it is an improvement, it does not completely remove the problem. To go further we need to reconsider the logic instead of just optimizing the current code.
+
+This patch is already on beta labs, can be tested for example in http://en.wikipedia.beta.wmflabs.org/wiki/Barack_Obama and is planned for deployment around 1800 UTC today.",1373472779,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Change 72967 merged by jenkins-bot:
+Update jquery.webfonts from upstream
+
+https://gerrit.wikimedia.org/r/72967",1373471100,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Change 72967 had a related patch set uploaded by Amire80:
+Update jquery.webfonts from upstream
+
+https://gerrit.wikimedia.org/r/72967",1373470044,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #9)
+> SpeedyGonsales: This bug report is specifically and only about ""Loading a
+> page
+> which requires many fonts causes high CPU load"". If you want to generally
+> talk
+> about ""preferences for new things"" or what MediaWiki should be, please do
+> that
+> on some forum or Village Pump. Thanks for your understanding.
+
+it is unfortunate that ""some forum or village pump"" where the people responsible for the content of wikimedia deployment are actually listening, does not exist.
+
+there is another bug on bugzilla ( bug 46306 ), requesting/demanding a kill switch for ULS. this bug was closed with ""resolved/wontfix"".
+
+yet another open bug ( bug 51070 ) is requesting/demanding to disable ULS on enwiki. this one was not closed with ""wontfix"", but could have been just as well.
+
+so complaining about these demands/requests spilling into other bug reports is somewhat unfair, IMO.
+
+peace.",1373462060,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Just a note that the Language Engineering team responsible for ULS will be holding an office hour later today, at 17:00 UTC on
+#wikimedia-office (on Freenode): http://www.mail-archive.com/wikitech-l@lists.wikimedia.org/msg69718.html",1373455470,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,Also reported at pl.wp: https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#Ostrze.C5.BCenie:_Skrypt_nie_odpowiada,1373454616,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Eduard: I can understand frustration, but no need for rhetorical questions, plus ""I wasn't heard in the right place, so I tried again in some other, wrong place"" is not a good argument.
+Tools (like bugtrackers, mailing lists, Gerrit) serve purposes and have dedicated audiences. Bugzilla is a technical bugtracker for bug reports that refer to specific codebases. It's not for meta-level discussions on development policies, plus from experience in other open source projects I can assure you that the more comments unrelated to a bug there are in bug reports, the more devs will (understandably) also start ignoring bugmail and bug reports. I assume that's not wanted by anybody, and that's why I explained how to avoid that.",1373452499,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Since one is ignored ""on some forum or Village Pump"" (*) one tries other ways to voice one's opinion. Is it surprising that people then try it on Bugzilla where one has at least slight chances a dev will peek at one's message an comment on them?
+
+* e.g. http://www.mediawiki.org/wiki/Thread:Talk:Universal_Language_Selector/Disabling_ULS or http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#.22Opt_out.22_of_VE_needed_under_preferences",1373448080,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #8)
+
+SpeedyGonsales: This bug report is specifically and only about ""Loading a page which requires many fonts causes high CPU load"". If you want to generally talk about ""preferences for new things"" or what MediaWiki should be, please do that on some forum or Village Pump. Thanks for your understanding.",1373447177,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"If you ask me having ""disable switch"" (""kill switch"") in user preferences is a
+must for almost any new things in MediaWiki UI.
+
+If we are unable to alter closed OS (e.g. Windows or Mac) but are able to alter 
+open source one (Linux), MediaWiki should be smart and offer ""disable switches"" 
+for new things. ULS is a good idea, but the same way I like to have ""kill 
+switch"" for VisualEditor :) (""Remove VisualEditor from the user interface"" in Gadgets), I agree there should be one for ULS, period.",1373439569,PHID-USER-3hahyxmftu2sew3v6v6w,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #5)
+> ULS contains quite a lot of new JavaScript and CSS code, so it is reasonable
+> to
+> expect that a close scrutiny of the code will reveal some measure of
+> duplicate
+> work and various other performance problems. It's good that you've dug into
+> the
+> code and pinpointed some specific problems, but please be less adversarial.
+> Measuring and optimizing client-side performance is hard enough to do when
+> you
+> aren't under attack; calling a developer's code ""asinine"" or ""disgusting"" is
+> not likely to make it any easier.
+
+you are correct that my style is/was a bit abrasive, and for this i apologize. however, the ULS team demonstrated pretty bad behavior of its own: please review the way Siebard responded on bug 49935 .
+in addition, turning it on on many wikis before cleaning the very serious performance issues (and causing browsers to freeze _is_ very serious issue), and then arguing that this thing should not have a disable switch in user preference is just wrong.
+
+peace.",1373437720,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"i think you missed the main point: when we call ""load"" with a font family such that this.getCSS() returns false (e.g. ""sans-serif"" on my browser), we do not cache the result. calling getCSS() is orders of magnitude more expensive than the search, regardless of whether the search is done the right way (through hash) or the wrong way (through $.inArray).
+
+as to profiling: the real test is to have ~20 entries in the font table (like in [[en:Japan]]), and then measure how long does it take to look for a font _which is not in the list_, which is what happens today, thanks to the problem mentioned above. you'll see that the search takes significantly longer than it should.
+
+still, the main problem is not the inefficient search, but rather calling getCSS thousands (or tens of thousands - depends on the page content) of times instead of once per each font family present on the page.
+
+as to why we call ""load"" so many times: easy. set a breakpoint, and follow the call stack upward until you'll find the call that's inside an .each() loop.
+
+
+peace.",1373437177,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"(In reply to comment #1)
+> 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.
+
+I've only noted a single repaint in Chrome Dev Tools on https://en.wikipedia.org/wiki/Tower_of_babel, and I'm not sure yet if it's attributable to ULS. But any form of DOM access is expensive, so the recommendation above is entirely sound.
+
+> the function ""load"" is also asinine, and can cause a high load:
+> 
+> it has two problems: one of them is using $.inArray() to test whether this
+> fontface was already loaded: this means linear search on the array every
+> single time
+
+Hash tables lookups are worse than linear searches for arrays of this size due to the cost of computing the hash and the relatively poorer locality. (In fact, modern JS engines don't even implement property lookups as hash tables, but I figure that was what you had in mind when you recommended hasOwnProperty instead of $.inArray).
+
+https://en.wikipedia.org/wiki/Tower_of_babel has four fontFamilies: ""Amiri"", ""Akkadian"", ""AbyssinicaSIL"", and ""CharisSIL"". I used this to profile object vs. array lookup:
+
+> var myArray = [""Amiri"", ""Akkadian"", ""AbyssinicaSIL"", ""CharisSIL""];
+> console.time('$.inArray'); for(var i = 0; i < 10000; i++) $.inArray('abc', myArray); console.timeEnd('$.inArray');
+$.inArray: 18.029ms
+> var myObj = {""Amiri"": null, ""Akkadian"": null, ""AbyssinicaSIL"": null, ""CharisSIL"": null};
+> console.time('hasOwnProperty'); for(var i = 0; i < 10000; i++) myObj.hasOwnProperty('abc'); console.timeEnd('hasOwnProperty');
+hasOwnProperty: 13.161ms
+
+The difference per call works out to just under half of one millionth of a second, certainly not enough to warrant calling either approach 'asinine'. I am running a recent build of Chromium, but I'd wager the difference even for older browsers would not cross the threshold of significance.
+
+It is a bit bizarre that load() has to be called 877 times on that page, though. That should be investigated.
+
+ULS contains quite a lot of new JavaScript and CSS code, so it is reasonable to expect that a close scrutiny of the code will reveal some measure of duplicate work and various other performance problems. It's good that you've dug into the code and pinpointed some specific problems, but please be less adversarial. Measuring and optimizing client-side performance is hard enough to do when you aren't under attack; calling a developer's code ""asinine"" or ""disgusting"" is not likely to make it any easier.",1373414464,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"I've requested ULS be disabled, this has taken too long, it's annoying ppl without reason.
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51070",1373404117,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"Why was this set back to UNCONFIRMED?  Lots of people have experienced this, and kipod has even identified the fix.",1373267032,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"P.S: i used ""abnormal"" to signify that getCSS() returnd false, when called with this font family and variant ""normal"". i do not think this is a good name - maybe ""empty"" of ""builtin"" or something similar will be better, as long as one can be confident it's not a valid fontFamily name. it has to eveluate as boolean true, though, so you can;t use false or empty string.
+
+alternatively, false can work, as long as you modify the first line to
+
+if ( this.fonts.hasOwnProperty( fontFamily ) )
+
+so the thing becomes
+
+load: function( fontFamily ) {
+    if ( this.fonts.hasOwnProperty( fontFamily ) )
+        return this.fonts[fontFamily];
+    var styleString = this.getCSS( fontFamily, 'normal' );
+    if ( styleString ) {
+        injectCSS( styleString );
+        return this.fonts[fontFamily] = true;
+    }
+    return this.fonts[fontFamily] = false;
+}
+
+(for brevity, assign and return on one line - don't do it in real life).
+
+peace.",1373059269,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+Loading a page which requires many fonts causes high CPU load,"the function ""load"" is also asinine, and can cause a high load:
+
+it has two problems: one of them is using $.inArray() to test whether this fontface was already loaded: this means linear search on the array every single time (that is, for every single html element with either ""lang"", ""style"" or ""class"" attributes on the page!), and for pages with large number of elements, this can be significant. whats more, there is no reason not to add the font family to the list even when it's not found, to save us some work with future elements with same font family.
+
+even worse, when getCSS() returns ""false"" (which it does for 99% of the elemnts, e.g. when fontFamily is sans-serif), we don't mark this font family as ""tested"", so when we find the next element with sans-serif, we do all this work again.
+
+from performance POV, this is atrocious.
+
+
+here is a better version of load() - 100% untested.
+
+load: function( fontFamily ) {
+	if ( this.fonts[fontFamily] ) 
+		return this.fonts[fontFamily] != ""abnormal""; 
+// does the font have ""normal"" face?
+
+	var styleString = this.getCSS( fontFamily, 'normal' );
+	if ( styleString ) {
+		injectCSS( styleString );
+		this.fonts[fontFamily] = true;
+		return true;
+	}
+	// Font does not have ""normal"" face.
+	this.fonts[fontFamily] = ""abnormal"";
+	return false;
+}
+
+
+note that ""this.fonts"" here is an object rather than an array (to save the linear searches), so it should be initialized to  {} rather than [].
+
+peace.",1373058592,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j7v3ex7edi7dypukus5m,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"If a user hits the spam blacklist they VE responds merely by informing them ""Error: Invalid error code"". This is...not helpful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1373053740,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_description,resolved
+VisualEditor: Add support for spam blacklist errors in save dialog,Fixed and will be going out in a few minutes.,1374016034,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"Change 73964 merged by jenkins-bot:
+mw.ViewPageTarget: Add support for spam blacklist
+
+https://gerrit.wikimedia.org/r/73964",1374015128,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"Though I knew that the SpamBlacklist has logic in place for returning multiple urls (bug 30332, Ia951d5795c5cedb) it didn't seem to work.
+
+Apparently it does work now. I can't consistently reproduce it only giving one. I'll presume it was an error on my part or an edge case in the regex SpamBlacklist is using and complex wikitext as input.
+
+I've amended the patch set to display multiple urls separated by comma if there is more than one.",1374010951,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"Change 73964 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Add support for spam blacklist
+
+https://gerrit.wikimedia.org/r/73964",1373983650,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"So we get the matched url from the API. Ideally we'd get a usable message as well.
+
+Given the following sample (and latest mediawiki/core and SpamBlacklist configured with [[m:Spam_blacklist]])
+
+
+* [http://cl.ly/foo/?bar=%22%3Equ%3Cb%3Eu%3C%2Fb%3Ex%3Ca%20href%3D%22 d]
+* [http://fidosoft.de fidosoft]
+
+index.php?action=submit gives the following:
+
+> The text you wanted to save was blocked by the spam filter. This is probably caused by a link to a blacklisted external site.
+> The following text is what triggered our spam filter: http://fidosoft.de and http://cl.ly
+
+These are constructed in EditPage::spamPageWithContent by the ""spamprotectiontext"" and ""spamprotectionmatch"" messages respectively, which are actually in mediawiki core. The latter message takes $1 as parameter and EditPage.php sets that to the result of Language::listToText( Array ).
+
+The API gives:
+
+        ""edit"": {
+            ""spamblacklist"": ""http://cl.ly"",
+            ""result"": ""Failure""
+        }
+
+For some reason it isn't getting the second url? The SpamBlacklist API hook looks like it is doing `implode( '|', Array )` but aside from an array being nicer than a pipe-separated list, we're not getting either. Only the first url is returned.
+
+So either:
+
+1) SpamBlacklist needs to provide a processed message
+
+or:
+
+* SpamBlacklist needs to provide both urls, not just the first (I tested latest master, SpamBlacklist@3390081e4c6). Though this bug should be fixed either way, if we don't get a processed message, needing both is a blocker.
+* We'll load these 2 core messages as part of ve.init.mw.ViewPageTarget
+* We'll need an equivalent of Language::listToText in core mediawiki.language.js (though I suppose join(', ')  could do meanwhile).",1373983097,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"**joedecker** wrote:
+
+Sounds like y'all have screen shots, but for those of us playing the home game, when I press ""Save Page"" on a blacklist-blocked edit, that window (with the edit summary, etc.) stays up, and ""Error: Unknown error"" appears below the edit summary box, to the left of and slightly higher than the Review your edits/Save page buttons--the latter inactive.
+
+MacOSX/Chrome 28.0.1500.71, tested with an examiner.com URL at [[Chad Griffin]] with an incognito window/logged out.",1373952568,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,"Created attachment 12821
+Developer console dump
+
+A very helpful user in #wikipedia-en-help gave me this screenshot of what we get back from the API when TitleBlacklist rejects an edit.
+
+**Attached**: {F11276}",1373495540,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Add support for spam blacklist errors in save dialog,*** Bug 51139 has been marked as a duplicate of this bug. ***,1373495139,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-redwc5kkxwdmnoyvkj7r,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"Quote: Using Firefox 19.0.2 on Windows Vista, editing Relativity Media. Find ""subsidairies"", right-click, select ""subsidiaries"". The word appears changed, but the ""Save"" button is not activated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63462
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63395
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59748",1373050560,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_description,resolved
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"As far as I can tell, these issues have all been fixed now. However, there's bug 72929 which I've opened for a new issue that's developed in the past few weeks.",1415058499,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"I have issues with this locally as well (Iceweasel/Firefox 24.4.0 with VE 3b3a66763ade397b857e35efe8990ac217e5d54c , in debug mode.
+
+In my case, when I try correct the word, it does change in that spot (fixing the misspelling), and the save button enables.  However, the change also appears at the beginning of the document. In this case the required spelling fix was adding an 'r' (occurence. to occurrence), so an 'r' ended up at the beginning of the ContentEditable.
+
+However, in Review Changes (and the actual save), it then drops the original correction, and *only* puts the wrong edit at the beginning.",1399014057,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"Tried to duplicate this with FF 28 on a variety of typos on different pages.  Ran into Bug 63395 a lot, but was able to save after using FF autocorrect to alter the typo text. (On a side note, hilariously, FF autocorrect suggests that ""autocorrect"" should be changed to ""autocrat"":))",1398191795,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,*** Bug 52372 has been marked as a duplicate of this bug. ***,1398187598,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"No i don't know, it's a report from the VE/Feedback page.",1373157962,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,(Assigning to me absent confirmation that this problem is reproducible.),1373157358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Using browser native interactive spell-check tool breaks in Firefox,"(In reply to comment #0)
+> Quote: Using Firefox 19.0.2 on Windows Vista, editing Relativity Media. Find
+> ""subsidairies"", right-click, select ""subsidiaries"". The word appears changed,
+> but the ""Save"" button is not activated.
+
+Odd. I get the save dialog activated on making a spelling-correction changes in both Chrome and Firefox, including on that particular word in that particular page. Saved example: https://en.wikipedia.org/w/index.php?title=Relativity_Media&diff=563012676&oldid=559815961
+
+Is the user using a non-standard way of doing the spell-correcting, do you know?",1373052311,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2cs7ruqdiqeaisw3iea4,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Template inspector before closing
+
+Wikilinks like [[Foo|Bar]] are shown expanded in template inspector after closing it, see screenshots. 
+
+Steps to reproduce:
+
+1. Edit a template which has wikilinks like [[Foo|Bar]] as a parameter value
+2. Close the template inspector, with or w/o changes does not matter.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/VRB_H_2/3
+
+**Attached**: {F11204}",1373030040,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_description,resolved
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"We've now fixed this in master, and will back-port to production.",1373559177,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Change 73173 merged by jenkins-bot:
+Prevent escaping of piped links in wikitext parameters
+
+https://gerrit.wikimedia.org/r/73173",1373558760,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Change 73173 had a related patch set uploaded by Esanders:
+Piped links in wikitext parameters getting escaped
+
+https://gerrit.wikimedia.org/r/73173",1373553974,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,This is a wikitext escaping bug in VE,1373553234,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Screenshot of different phases:
+
+http://cl.ly/image/1X0I281n1n0G
+1) PHP rendering on Read
+2) VE initial rendering after Edit
+3) VE rendering after opening Template dialog and making no changes and clicking Apply changes
+
+Dirty diff: http://cl.ly/image/241h1I3T1d2d",1373547246,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"It doesn't show in the diff, it only shown in the live rendering in VisualEditor.",1373547049,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,Can you create a broken diff on that article for me?,1373546964,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"As can I, hence the duplicate bugs. Firefox 22, Windows 7.",1373544903,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"(In reply to comment #4)
+> Can't reproduce this at the example URL.
+
+I can still reproduce it :-(",1373544652,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,Can't reproduce this at the example URL.,1373543860,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,*** Bug 51014 has been marked as a duplicate of this bug. ***,1373521095,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,*** Bug 50909 has been marked as a duplicate of this bug. ***,1373354186,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed,"Created attachment 12761
+Template inspector after closing
+
+**Attached**: {F11205}",1373030118,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-js6dahlv3jujgj6b2lzv,task_subcomment,NA
+VisualEditor: Break lines for TemplateData description in template inspector,"Screenshot
+
+The text of the TemplateData description should have an line break (wrap into span and style per CSS?) in the template inspector.
+
+Longer descriptions flows out of the template inspector box, see screenshot.
+
+Related: Bug 50656 - Parse wikicode and/or HTML in interface text
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11203}",1373028960,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-6tlgztl4hagkm2r7xhiz,task_description,resolved
+VisualEditor: Break lines for TemplateData description in template inspector,"This is now fixed in master and will be deployed soon, probably tomorrow.",1373420952,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6tlgztl4hagkm2r7xhiz,task_subcomment,NA
+VisualEditor: Break lines for TemplateData description in template inspector,"Change 72863 merged by jenkins-bot:
+Make parameter search widget have a horizontal limit
+
+https://gerrit.wikimedia.org/r/72863",1373420566,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6tlgztl4hagkm2r7xhiz,task_subcomment,NA
+VisualEditor: Break lines for TemplateData description in template inspector,"Change 72863 had a related patch set uploaded by Trevor Parscal:
+Make parameter search widget have a horizontal limit
+
+https://gerrit.wikimedia.org/r/72863",1373415980,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6tlgztl4hagkm2r7xhiz,task_subcomment,NA
+VisualEditor: Add close icon to page notices fly-out,"At the moment the only way to close a page notice is to click on the interface element that launches them - which feels somewhat counterintuitive. Could we have a little close button in the notices themselves?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373028000,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-p53a3hhm2h3bhitmo2np,task_description,resolved
+VisualEditor: Add close icon to page notices fly-out,We did this as part of the fixes to the toolbar.,1383279877,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p53a3hhm2h3bhitmo2np,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"This happened on MediaWiki, he.wiki and en.wiki on Chrome.
+
+Open some article for editing (preferably a long one so the effect is seen)
+add some text in the middle or end, mark it and make it a ""Heading"". 
+
+Observed result: The text turns into a heading, but the entire edit section scrolls up to the top of the page. This is especially annoying when the page is long and when the edit is done in the middle.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1373007960,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_description,resolved
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),This is now fixed by the above commit; we'll get it deployed soon. Sorry for the disruption.,1373414274,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"Change 72768 merged by jenkins-bot:
+Affordances for MenuWidget to be optionally focusable.
+
+https://gerrit.wikimedia.org/r/72768",1373413453,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"Change 72768 had a related patch set uploaded by Robmoen:
+Affordances for MenuWidget to be optionally focusable.
+
+https://gerrit.wikimedia.org/r/72768",1373400275,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),*** Bug 50860 has been marked as a duplicate of this bug. ***,1373157160,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"Confirmed in Chrome, Safari and not in Firefox, for whatever reason.",1373048007,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox),"I just checked the editor on Firefox 22.0, and it does not scroll there (works as expected). The bug seems to be in Chrome only. 
+
+If it helps, that's the UserAgent for my Chrome browser:
+
+ Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36",1373009332,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-tgytmlqjykzpjs6zkq4g,task_subcomment,NA
+"VisualEditor: Move “add parameter” button to alongside the search field, not below the results list, so it can be found","**Author:** `turingt`
+
+**Description:**
+At the Transclusion dialog, after a click or double-click on the chosen parameter, nothing happens. Is the user expected to click on the ""Add parameter"" label at the top? To press Enter? To read the user guide for instruction on how  ? None of these steps help.
+
+This is a usability bug - the actual button is hidden below the fold, at the end of a very long list that is not intended to be scrolled through, and thus hard to discover. The button should be always visible in the dialog - otherwise, the dialog becomes unusable with long lists of parameters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372974060,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mlttagm5jcb3oqt5j734,task_description,resolved
+"VisualEditor: Move “add parameter” button to alongside the search field, not below the results list, so it can be found","This issue is now fixed (or, rather, the button is no longer needed), as we've gone instead with single-click-to-insert, which will be deployed in the next few minutes.",1373932787,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mlttagm5jcb3oqt5j734,task_subcomment,NA
+"VisualEditor: Move “add parameter” button to alongside the search field, not below the results list, so it can be found","Change 73865 merged by jenkins-bot:
+Single-click insertion
+
+https://gerrit.wikimedia.org/r/73865",1373932432,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlttagm5jcb3oqt5j734,task_subcomment,NA
+"VisualEditor: Move “add parameter” button to alongside the search field, not below the results list, so it can be found","Change 73865 had a related patch set uploaded by Trevor Parscal:
+Single-click insertion
+
+https://gerrit.wikimedia.org/r/73865",1373922494,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mlttagm5jcb3oqt5j734,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Especially when a template has many parameters;
+scrolling until you find the actual button to add them,
+having to add them one by one and having to do so by clicking each time on the name of the template itself to get to the list again, it's confusing users.
+There's already a bug about mandatory parameters not being enforced; I am not sure of the behaviour related to the order of the parameters, but it would be great if the editor could keep them in the same order they're being chosen with. Thanks :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372970700,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_description,invalid
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)",There is no longer such a button (as of a week ago).,1374257794,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Created attachment 12830
+Screenshot of how it used to be
+
+Note that though this is how it was. It was also true that when the text in the input field was very long (like, very very long, as long as the dialog is wide) the button would jump to *below* the parameter list (as opposed to directly below the input field or just stay where it was).
+
+
+I propose that we either keep the current behaviour of the input field having a fixed width, but making sure that width is without the width of the ""Add"" button so that that one always stays where it should be (similar to having the ""Go"" button of a search field next to the input and not at the bottom of a variable-length and scrollable list of results).
+
+Alternatively we could bring back the dynamic-width behaviour but when we'd still need to make sure it doesn't go wider than the width allotted to keep the button on the same line as well.
+
+**Attached**: {F11129}",1373539291,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Created attachment 12829
+Screenshot of the problem (current version)
+
+No add button anywhere in sight, users are likely to be blocked indefinitely with no ability to add any parameters.
+
+**Attached**: {F11128}",1373539077,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Though I don't know for sure, I think this is a recent regression. the button used to be where it should be (next to the input field). However at that time the input field width was also dynamic (widening as you type). I suspect Trevor ""fixed"" that odd overflow bug by moving the bottom out of the visible form area but probably tested it only with a small template where it was still in sight.
+
+Adding screenshots for clarity.",1373538997,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)",Works for me. Can we twiddle with the prioritisation and criticality? This is a big workflow to have practically broken.,1373538953,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","We're getting various reports of this kind, let's try and keep them somewhat focussed on a single tangible thing. If you don't mind I'll turn this into:
+
+The ""Add parameter"" confirmation button should be next to the input field
+
+  .. not at the bottom of the page after a potential long list of paramaters one has to scroll through to even discover the button.",1373538890,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)",We really need a fix on this. I just tried to add a template (cite web) and was so confused I had to reach out to Timo and Guillaume to work out how in the hells you add a parameter. It's...tremendously counterintuitive on any template with more than 5 params.,1373538824,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+"[Regression] VisualEditor: The ""Add parameter"" confirmation button should be close to the input field (at least visible)","Agreed. This is what I was going to add into a new feature request:
+
+---------
+
+In the current version of the template editor, the user needs to select a parameter, click ""Add parameter"", enter the value, go back, and rinse and repeat for all the other parameters.
+
+There are at least two issues with this workflow:
+
+* For templates with a long list of parameters, the ""Add parameter"" button is hidden at the end of the list, so it's not obvious what to do after selecting a parameter
+*: Possible solution: Give each parameter a button that adds it to the left column (like a green ""+"" sign, or something)
+
+* If the user needs/wants to add many parameters, the process can be quite long.
+*: Possible solution: Add an ""Add all parameters"" button, and possibly an ""Add all required parameters"" button as well.",1373034592,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-3x6yvjlb5kfqndi3ivao,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"The existing editing interface stores data on hidden categories, and on the templates in use. This is not displayed in the existing VE - it seems like the sort of thing the page settings page might be good for.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372964580,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-2avh7ag4txo4yazyqwg3,task_description,resolved
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"Maybe we could show these a bit more clear in the dialog, but closing for now.",1393467412,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"Change 113464 merged by jenkins-bot:
+Mark hidden categories as different in the meta-data dialog
+
+https://gerrit.wikimedia.org/r/113464",1393467180,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"Change 113464 had a related patch set uploaded by Alex Monk:
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display
+
+https://gerrit.wikimedia.org/r/113464",1392414019,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"(In reply to Alex Monk from comment #4)
+> Am I right in thinking that the category data comes from Parsoid? If so then
+> it might be useful to include whether the category is hidden or not there?
+
+Okay so after discussion with James and Gabriel on IRC, for now I'm going to query the API when the category dialog loads to get this information. Later to be replaced by a general CSS cache API query (see bug 37901).",1392400602,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,Am I right in thinking that the category data comes from Parsoid? If so then it might be useful to include whether the category is hidden or not there?,1392168563,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,Re-wording to be less confusing. Sorry!,1392062209,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,I think I'm missing something here - it appears that I can see hidden categories and add hidden categories to pages using the categories tool. Is this bug still valid?,1391984557,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display,"""A late answer to the question of whether there are hidden categories that are actually embedded in articles instead of templates: YES. For instance Category:Year of birth missing (living people) is directly embedded into some tens of thousands of them""",1373212682,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-2avh7ag4txo4yazyqwg3,task_subcomment,NA
+VisualEditor: broken <table> syntax causes VE to inject additional <table> html,"In this case, https://en.wikipedia.org/w/index.php?title=Long_Island&diff=562848384&oldid=562113547 - oh dear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372954980,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-44thcl26amo7hsho63fi,task_description,resolved
+VisualEditor: broken <table> syntax causes VE to inject additional <table> html,"
+
+*** This bug has been marked as a duplicate of bug 51217 ***",1374329698,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-44thcl26amo7hsho63fi,task_subcomment,NA
+VisualEditor: broken <table> syntax causes VE to inject additional <table> html,"A minor change in a completely unrelated part of the article causes a copy of the broken table to be injected into the article, and a '<tr' (no closing >) is also included.  Upping priority/importance as it should at least ignore elements it doesnt properly understand.  The <table> was not so broken that the wikitext up to the </table> should have been ignored.
+
+I am able to reproduce the '<tr' being added [[testwiki:User:John_Vandenberg/Table_test]], but in my test the table wasnt copied.
+
+After fixing the syntax on enwp, the problem goes away.
+
+https://en.wikipedia.org/w/index.php?title=Long_Island&action=history&offset=201307180315&limit=3",1374117478,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-44thcl26amo7hsho63fi,task_subcomment,NA
+VisualEditor: Incorrectly displaying nested references,"Copied from English Wikipedia:
+
+A similar bug was reported as #49536 , but closed as fixed a while ago. Article Otto I has a reference (""ref"") to ""Thompson"" (numbered #11 in old edit mode) inside an explanatory footnote ""efn"". The notes are generated below the article using ""notelist"". Ref 11 Thompson is not included in the reflist of VE, but shown in regular read mode. Just compare the reference lists in read and in VE edit mode to see the difference. GermanJoe (talk) 13:03, 4 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51289
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52398",1372948260,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-6255kvv4aihzvptanmel,task_description,resolved
+VisualEditor: Incorrectly displaying nested references,Filed a bug against Parsoid: see bug 69827,1408586751,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-6255kvv4aihzvptanmel,task_subcomment,NA
+VisualEditor: Incorrectly displaying nested references,"Look at [[Otto I]].  It has 63 references, including ref #18 (""Thompson"") from explanatory footnote [d].  This ref doesn't appear in VisualEditor.",1408406807,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6255kvv4aihzvptanmel,task_subcomment,NA
+VisualEditor: Incorrectly displaying nested references,I believe that this now has been fixed - compare https://en.wikipedia.org/wiki/Otto_I%2C_Holy_Roman_Emperor with https://en.wikipedia.org/wiki/Otto_I%2C_Holy_Roman_Emperor?veaction=edit to see the reference lists being the same in both cases. Sorry for the slow response.,1375383334,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6255kvv4aihzvptanmel,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60358",1372947300,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_description,resolved
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Verified the fix in production,1411682658,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Verified the fix in test2,1411081594,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Verified the fix to show confirmation dialog when trying to insert/edit a template with one or more missing required parameters,1410991738,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"There are still some remaining improvements (as always), but the thrust of this bug is now done.",1410982793,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Change 156559 merged by jenkins-bot:
+Get confirmation when trying to insert/edit template/citation with required parameters missing
+
+https://gerrit.wikimedia.org/r/156559",1410982430,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Change 156559 had a related patch set uploaded by Alex Monk:
+Get confirmation when trying to insert template with required parameters missing
+
+https://gerrit.wikimedia.org/r/156559",1409154385,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,We're also going to require the user to confirm when they try to insert a template with required parameters missing.,1409154296,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.
+
+I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter.
+
+So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor.
+
+(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.)
+
+At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.
+
+And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"(In reply to Alex Monk from comment #14)
+> Is there anything left here to do that isn't bug 60358?
+
+I believe that that will complete this.",1408762442,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Is there anything left here to do that isn't bug 60358?,1408757255,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"I haven't tested required/optional fields in depth, but some casual tests suggest that currently
+
+* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates.
+
+* Required field aren't still enforced, nor there is any warning when they are left empty.
+
+My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",1386641485,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters.
+
+It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". 
+
+As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",1374454542,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,Not enforcing mandatory params is a bug in either design or implementation.,1374447401,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. 
+
+More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis.
+
+In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Indeed, I gave up doing this for the Portuguese version for now:
+https://pt.wikipedia.org/wiki/Template:Info/Taxonomia?uselang=en",1373922302,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template
+and  John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". 
+
+I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. 
+
+BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,English Wikipedian Joe Decker recommends indicating required parameters perhaps with the standard red asterisk.,1373565271,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,%%%*** Bug 51186 has been marked as a duplicate of this bug. ***%%%,1373565194,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Change 73136 merged by jenkins-bot:
+Auto-add required params for user added templates
+
+https://gerrit.wikimedia.org/r/73136",1373560433,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Leaving at ""recommend"" for now since we can't fully ensure that requiring all parameters is consistently the desired behavior.",1373507848,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"(In reply to comment #2)
+> Change 73136 had a related patch set uploaded by Jforrester:
+> Auto-add required params for user added templates
+> 
+> https://gerrit.wikimedia.org/r/73136
+
+This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want).
+
+Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",1373503365,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Change 73136 had a related patch set uploaded by Jforrester:
+Auto-add required params for user added templates
+
+https://gerrit.wikimedia.org/r/73136",1373503236,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters,"Indeed, this seems like a low hanging fruit improvement - when inserting a new template, having all the required fields immediately be ready for use would significantly speed up template completion.",1373354062,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ob2d5ffvdmtamrwpb4u7,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),"http://en.wikipedia.org/wiki/File:VisualEditor_-_Cite_template_layout_issue_%28TemplateData%29.png
+
+Tested on Firefox 22, Mono skin:
+
+'''Steps to reproduce'''
+* Open any random page in the visual editor.
+* Add a new template - use Cite Web for this.
+
+The output will be akin to the screenshot added. Some the template parameters end up next to each other, and are thus offscreen. Even if that is not the case the description will often be to long to be displayed. Would be nice if those ended up on a new line if that occurred.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372928700,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-k2f6cmw4o3bualf2yl72,task_description,resolved
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),"I believe that this should now be fixed; marking as such. If you can reproduce, please re-open.",1373503064,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),"We believe that this is caused by a caching issue; a big change to how the CSS for dialogs is loaded is coming in this afternoon's deployment that (hopefully) will remove these issues, so I won't close this right now, but it seems likely that we will have fixed this by the end of today. Sorry for the disruption.",1373484976,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),I can repro in FF20 (in Vector too) but not in Chrome 28.,1373358083,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),Also happening in chrome.,1373357244,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?),%%%*** Bug 50738 has been marked as a duplicate of this bug. ***%%%,1372937527,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k2f6cmw4o3bualf2yl72,task_subcomment,NA
+Save action doesn't handle abort hooks very elegantly,"When your edit trips the blacklist or an editfilter, you get a very technical and uninformative message.
+
+The edit filter causes:  ""Error: The notification you tried to make was aborted by an extension hook"" to show in the 'save' dialog.
+
+The URL blacklist:  ""Invalid code error"" apparently.
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562806113#Blocked_sites
+
+Since this is quite common for newbs to trip, it should be handled better.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**URL**: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562806113#Blocked_sites",1372928040,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-pb7leo6kictiruq53qyh,task_description,resolved
+Save action doesn't handle abort hooks very elegantly,"* AbuseFilter is bug 50472; resolved fixed, and will be deployed tomorrow.
+* SpamBlacklist is bug 50826; resolved fixed, and deployed yesterday.
+
+Marking this as a dupe of 50472.
+
+*** This bug has been marked as a duplicate of bug 50472 ***",1374112342,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pb7leo6kictiruq53qyh,task_subcomment,NA
+Save action doesn't handle abort hooks very elegantly,"Bumping priority & importance as proper integration with abusefilter must be a blocker, I would think, as rules are being written to prevent VE edits that are destructive to Wikipedia content.",1374101269,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-pb7leo6kictiruq53qyh,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),"This broke during yesterdays deploy. Now shows <accesskey-ca-editsource> and no key is set. I think Timo fixed it already, but the fix might not have been deployed yet.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372926360,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_description,resolved
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),*** Bug 50817 has been marked as a duplicate of this bug. ***,1373077734,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),Merged into master; we hope to deploy this soon.,1373051656,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),"Change 72068 merged by jenkins-bot:
+mw.ViewPageTarget.init: Add missing ""accesskey-ca-editsource"" message
+
+https://gerrit.wikimedia.org/r/72068",1373048824,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),"Change 72068 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget.init: Add missing ""accesskey-ca-editsource"" message
+
+https://gerrit.wikimedia.org/r/72068",1373004195,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e),Confirmed.,1372970464,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hz3zx2etea2vvyzkz3b6,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Steps to reproduce:
+
+* Navigate to [[Mariposa botnet]] and edit the page in the visual editor.
+* Make any textual change - just add ""Test"" somewhere for example.
+* click ""Save Page""
+* Adding a reason doesn't matter. Just click to close the save page popup.
+* Immediately open it again (Don't click anywhere else)
+* Try to add a text as the reason, then press backspace or delete what you just added.
+
+For some reason delete and backspace won't work anymore. My guess is that the backspace is send to the editing canvas instead of the textbox - try the following steps as well:
+
+* (Do all the steps from the first section)
+* Press ""Review Your changes"".
+* Wait for the review to load, then press ""Return To Save"", and close the resulting form.
+* Now click the search block (In mono) and enter a random search criteria.
+* Once entered, try to remove it again.
+
+What happens for me: Entering data in the search box works fine, but pressing backspace somehow causes text to be removed from the article, instead of the search box i was just typing in.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49569",1372923300,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_description,resolved
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"The (re)fix for this is now merged and will be deployed on Thursday 10 October to MediaWiki.org, and to Wikipedias on Thursday 17 October.",1381187020,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Change 81876 merged by jenkins-bot:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1381186911,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"At bug 53332 comment 0 Elias Hedberg notes that he encountered this bug while using Chrome 29.0.1547.57 running in OS X 10.6.8
+
+Previously this seems only to have been encountered in Firefox. Will that affect the pending patch at all?",1379954053,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,*** Bug 53332 has been marked as a duplicate of this bug. ***,1379953641,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"BeroBurns at en.wp today reported experiencing this bug:
+""The save form does not allow for a keyboard backspace or to highlight text using Shift+Arrows. The only way to edit your description of the changes is to highlight the words you wish to replace with the mouse and retype.""
+
+I personally haven't encountered it since my comment above though.
+
+What is the current state, it's had a patch waiting for review nearly 20 days and is still targetted for the release a month ago yesterday?",1379924128,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Change 81876 had a related patch set uploaded by Jforrester:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1378325627,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"I do have popups, hotcat and section edit link for the lead section installed. Plus a couple of other things a conversation on the feedback page the other day established as being on by default.
+
+I tried to reproduce this when logged out, and couldn't.
+I then logged back in and tried to reproduce it and again I couldn't, even with no changes to gadgets. I didn't try to replicate the exact edit I made though.
+
+Earlier on today was the first time in a while I had experienced it though, which suggests to me that there is probably something more complicated behind when this happens and when it doesn't. I'll do some more detailed testing when I next get time, as it's too perplexing for 1:30am!",1377909365,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"(In reply to comment #12)
+> (In reply to comment #11)
+> > 
+> > With what browser?
+> 
+> I encountered it using Firefox 23 on linux, Tathbelin didn't note it in their
+> report but I'll ask.
+> 
+> Sorry
+
+OK, well, it works fine for me on enwiki right now in Firefox 23 on Mac and on Linux (doing the ^, the <, the Esc and the ""return to save form"" ways of bailing). This is perplexing. Do you have some odd gadgets loaded - does it still occur if you switch all gadgets off?",1377908358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"(In reply to comment #11)
+> 
+> With what browser?
+
+I encountered it using Firefox 23 on linux, Tathbelin didn't note it in their report but I'll ask.
+
+Sorry",1377906476,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"(In reply to comment #9)
+> I've just experienced this in my sandbox making this edit:
+> https://en.wikipedia.org/w/index.
+> php?title=User%3AThryduulf%2Fsandbox&diff=570859913&oldid=570858997
+> (testing for bug 52399)
+> 
+> In this case the series of actions was:
+> 1. Make some edits
+> 2. Review changes
+> 3. Return to editing surface (I can't remember whether I went direct using ^
+> or via the save form using <)
+> 4. make some more edits
+> 5. add an edit summary
+> 6. review changes
+> 7. return to save orm
+> 8. attempt to amend edit summary, but encounter this bug
+
+With what browser?",1377899641,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Nearly simultaneously with my writing the above comment, en.wp user Tathbelin reported on the VE feedback page:
+
+""I had the Problem that while I was writing my Change Summary after editing the page I wasn't able to delete what I had previously written i.e. couldn't use delete or backspace.""
+
+The edit in question was likely https://en.wikipedia.org/w/index.php?title=Henning_Wehn&diff=570856495&oldid=565884244",1377898123,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"I've just experienced this in my sandbox making this edit:
+https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=570859913&oldid=570858997 (testing for bug 52399)
+
+In this case the series of actions was:
+1. Make some edits
+2. Review changes
+3. Return to editing surface (I can't remember whether I went direct using ^ or via the save form using <)
+4. make some more edits
+5. add an edit summary
+6. review changes
+7. return to save orm
+8. attempt to amend edit summary, but encounter this bug",1377896367,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"I believe that this is now fixed, having followed Chris's very helpful steps to reproduce in bug 52733 comment 1 - tested in Safari, Chrome and Firefox latest on Mac just now against wmf14 as deployed on the Wikipedias right now. Marking as such.
+
+If you can re-produce, please feel free to re-open.",1377833711,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,*** Bug 52733 has been marked as a duplicate of this bug. ***,1377833584,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,I updated the summary per comment 5.,1373434182,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,I think there is no connection with ULS for this bug. The bug exists at ml.wikipedia where no ULS is installed at present.,1373424566,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"As per comment 2 and comment 3, changing the component back to VE.",1373263596,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"(In reply to comment #2)
+> Open the the dialog for entering reason? It disappears after I click ""Save
+> Page"". How do I open it again?
+
+A bit more precise:
+0) Navigate to [[Mariposa botnet]] and edit the page in the visual editor.
+1) Make any textual change - just add ""Test"" somewhere for example.
+2) Click ""Save Page""
+3) Now, the save page box titled ""Save your changes"" should pop up.
+4) Close that box by clicking the ^ icon in the top right of that box.
+
+Now, you should be where you started at step 2
+
+5) Repeat steps 2 and 3
+6) Try to add a text as the reason, then press backspace to delete what you just
+added.",1373203660,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"By default input method from ULS is disabled in en.wikipedia.org. ie by default it does not do anything on textareas.
+
+Even if it is enabled, there is no input method for English except IPA which optional. 
+
+So in the case of the above bug, before mapping it to ULS component, please tell us whether input method was activated from the cog icon in the languages menu. Also let us know whether you were using IPA.
+
+If this is not the case, the component is not ULS.
+
+(In reply to comment #0)
+> Steps to reproduce:
+> 
+> * Navigate to [[Mariposa botnet]] and edit the page in the visual editor.
+> * Make any textual change - just add ""Test"" somewhere for example.
+> * click ""Save Page""
+> * Adding a reason doesn't matter. Just click to close the save page popup.
+> * Immediately open it again (Don't click anywhere else)
+
+Open the the dialog for entering reason? It disappears after I click ""Save Page"". How do I open it again?",1373199167,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus,"Yes, this is a really horrible problem that we've narrowed-down to be related to ULS's munging of <textarea>s in Firefox (and possibly other browsers?). Referring to them.",1373159168,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uxrck24is2ussi4ctgr2,task_subcomment,NA
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,"(Tested on Firefox 22, Monobook skin)
+
+Steps to reproduce
+
+- Go to the ""The Damned Thing (short story)"" page and edit it with the visual editor.
+- Go to the ""Gothic elements"" selection, and select all the text from ""Gothic elements"" (Header) to ""inadequate."" (Last word of the section). This should also select the image.
+- Click and drag the entire section, and drop it of before the ""Analysis"" section (Just drop it right before the A in that word, make sure the text entry | is displayed. The image itself will be gone. But for the fun part: Click anywhere on the editing canvas text.
+
+Suddenly, your entire input screen will be white. What seems to happen is that the image is blanked (Replaced by a white square) and plastered full size all over the page. You can try to drag it away, but each time you try it will replace itself over the pages content.
+
+https://en.wikipedia.org/wiki/File:Visual_Editor_-_Giant_White_Image.png contains a screenshot of the problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50643",1372922700,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-a2cttzysu3oh2p7i6yls,task_description,resolved
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,"Chris: Good catch, thanks for finding that!
+
+*** This bug has been marked as a duplicate of bug 50643 ***",1375772188,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-a2cttzysu3oh2p7i6yls,task_subcomment,NA
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,I think this duplicates bug 50643,1375716716,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-a2cttzysu3oh2p7i6yls,task_subcomment,NA
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,"Drag and drop is disabled for only text content, however drag and drop is allowed (in monobook) when an image and something else are selected, and the result is nasty.",1374476411,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-a2cttzysu3oh2p7i6yls,task_subcomment,NA
+VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox,"Drag and drop should be disabled, but cant find the bug for it.
+
+I cant reproduce the problem at the mentioned page on Firefox 22 (Win or Linux) using Vector, but goodness me I can reproduce this when I use monobook skin.
+
+https://en.wikipedia.org/wiki/The_Damned_Thing_%28short_story%29?veaction=edit
+
+(page hasnt changed since the bug was raised :/)",1374475185,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-a2cttzysu3oh2p7i6yls,task_subcomment,NA
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,"Note that this is not the same as bug 50715. Though they behave the same from the user point of view, bug 50715 is for a case where aliases are not in play.
+
+e.g. given our Unsigned template with parameter ""user"", ""timestamp"" and aliases ""1"" and ""2"" respectively.
+
+Having added ""mw.log('addParameterSearch-select', name, names);"" to ve.ui.MWTransclusionDialog#getTemplatePage in the select event handler of the addParameterSearch object; editing the following invocations:
+
+ case {{Unsigned|Foo|April 1}}
+ case {{Unsigned|1=Foo|2=April 1}}
+    typing ""1""
+    >  addParameterSearch-select null [""1"", ""2""]
+    >  addParameterSearch-select ""user"" [""1"", ""2""]
+    > ""Add"" is enabled
+    typing ""user""
+    >  addParameterSearch-select null [""1"", ""2""]
+    >  addParameterSearch-select ""user"" [""1"", ""2""]
+    > ""Add"" is enabled
+
+ case {{Unsigned|user=Foo|timestamp=April 1}}
+    typing ""1""
+    >  addParameterSearch-select null [""date"", ""user""]
+    >  addParameterSearch-select 1 [""date"", ""user""]
+    > ""Add"" is enabled
+    typing ""user""
+    >  addParameterSearch-select null [""date"", ""user""]
+    >  addParameterSearch-select null [""date"", ""user""] 
+    > ""Add"" is disabled
+
+The latter case actually works as expected, although it is odd that the value given to the select callback is null and not ""user"" and that the button is already disabled (probably by the select widget?).
+
+Also weird that the callback is constantly triggered twice, once for null and once for the actual value.
+
+Anyway, the solution is to resolve the names to their alias origins before doing the names.indexOf( name ) check.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372913640,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xwzbnkc2eempknw62ukj,task_description,resolved
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,This is now fixed in master and we will push to production very soon. Sorry for the inconvenience.,1373497400,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xwzbnkc2eempknw62ukj,task_subcomment,NA
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,"Change 73010 merged by jenkins-bot:
+Retain original param names and ignore leading/trailing whitespace
+
+https://gerrit.wikimedia.org/r/73010",1373497076,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xwzbnkc2eempknw62ukj,task_subcomment,NA
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,"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",1373483212,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xwzbnkc2eempknw62ukj,task_subcomment,NA
+VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added,Working on this.,1372913735,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xwzbnkc2eempknw62ukj,task_subcomment,NA
+VisualEditor: Binding of section edit link should not be deferred to after document is loaded,"Split from bug 50540 which is entirely different. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372883340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j2nulhpv4byjb3fgfm3a,task_description,resolved
+VisualEditor: Binding of section edit link should not be deferred to after document is loaded,This was done as part of the changed integration at the beginning of the month.,1376520602,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j2nulhpv4byjb3fgfm3a,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Copying from English Wikipedia:
+
+Okay, this one is probably quite tricky: When editing the source code, if an edit conflict arises, you can simply hit the back button, copy the code, and paste it into the updated version. However, with the Visual Editor, this is no longer possible. The content goes away, so you have to re-add it all, which is a huge pain if it involves references and other templates.--¿3family6 contribs 18:25, 3 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47779
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52519
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56465",1372878900,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_description,resolved
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,*** Bug 52950 has been marked as a duplicate of this bug. ***,1393526106,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Just noting that this was broken in Firefox for a few weeks after launch due to bug 56767, which has now been fixed, and I have disabled my switch editor.",1387332793,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,verified in betalabs env,1383337965,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Change 83049 merged by jenkins-bot:
+Button tool to switch to edit source with changes
+
+https://gerrit.wikimedia.org/r/83049",1383241787,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Change 92913 merged by Catrope:
+Button tool to switch to edit source with changes
+
+https://gerrit.wikimedia.org/r/92913",1383241777,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Change 92913 had a related patch set uploaded by Catrope:
+Button tool to switch to edit source with changes
+
+https://gerrit.wikimedia.org/r/92913",1383241700,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"The patch was -2'd pending a rewrite of the toolbar. Although the button works, we have no sensible place to put it until those changes are finished. At the time that was supposed to be a few days, so apologies for the delay, but that work is nearly complete now.",1380708262,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"btw I found this was requested back in April 2013
+
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_04#London_Underground_article
+
+my hack has been broken by some change in the VE product, and the deployment of this fix has now been delayed one month. Siebrand gave the patch a +1 a week ago. What is next for this to be committed and go live?",1380680609,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"Change 83049 had a related patch set uploaded by Esanders:
+Button tool to switch to edit source with changes
+
+https://gerrit.wikimedia.org/r/83049",1378428058,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"It isnt that tricky.  Here is a prototype.
+
+https://en.wikipedia.org/wiki/User:John_Vandenberg/switch_editor
+
+The UI could be improved.",1374791298,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,Also this would be useful to allow people to save unfinished changes for later completion.,1373308518,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving,"The ability to salvage incomplete edits could have other usefulness.
+
+Copying from English Wikipedia:
+
+I can attest to that, I have done the same thing and so due to inactivity the 'invalid token' message is appearing. No idea what to do, currently my tab is still open containing my edits which cannot be saved, I don't want to start over (quite a bit of work here), any suggestions? Copy-pasting to a text editor is not an option since I did mainly lot of linking and minor fixes. -Ugog Nizdast (talk) 10:04, 3 July 2013 (UTC)",1372944038,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-x7aj5blwrrol3b4wt6un,task_subcomment,NA
+"VisualEditor: ""Undo"" of image resizing causes wonky displacement","From English Wikipedia:
+
+'''Steps to reproduce:'''
+* Edit the [[Vogrie House]] article in the visual editor.
+* Resize the image. Larger or smaller doesn't matter.
+* Press either CTRL + Z, or undo the edit using the undo button. 
+
+Instead of undoing the edit, it suddenly enlarges the image object. The image is placed in the center of the screen, and the object itself even overlaps the main navigation in the Mono interface. Of course as always: Firefox 22 used to test this. [[User:Excirial|<font color=""191970"">'''Excirial''']]</font><sup> ([[User talk:Excirial|<font color=""FF8C00"">Contact me</font>]],[[Special:Contributions/Excirial|<font color=""FF8C00"">Contribs</font>]])</sup> 18:03, 3 July 2013 (UTC)
+
+See screenshot:
+http://en.wikipedia.org/wiki/File:VisualEditor_-_Undoing_a_resize_issue.png
+
+I tried on Chrome on a Mac, and it didn't work there, either, but instead shoved the image to the left of the screen
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372875420,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-vpsb5oulcmbkksi2sshi,task_description,resolved
+"VisualEditor: ""Undo"" of image resizing causes wonky displacement","We've now fixed this, and deployed it; sorry for the issue.",1372901775,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vpsb5oulcmbkksi2sshi,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,"In https://en.wikipedia.org/w/index.php?title=List_of_socialist_countries&curid=7252916&diff=562675715&oldid=562675131
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372853220,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-u7msjuo24hkzquuc5w2p,task_description,resolved
+VisualEditor: Miscellaneous additions of nowiki tags,"(In reply to comment #4)
+> Has the fix been rolled out to svwp?
+
+It has.
+
+> Because I just got a similar error where
+> the nowiki was added far from where I was doing my actual changes:
+> 
+> http://sv.wikipedia.org/w/index.
+> php?title=Stockholm_Arlanda_Airport&diff=22544469&oldid=22428046
+
+I believe that that is actually a different bug here, with Parsoid being overly keen to add <nowiki>, rather than this motley collection of other kinds of <nowiki> issues. :-(",1373841311,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,"Has the fix been rolled out to svwp? Because I just got a similar error where the nowiki was added far from where I was doing my actual changes:
+
+http://sv.wikipedia.org/w/index.php?title=Stockholm_Arlanda_Airport&diff=22544469&oldid=22428046",1373831819,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,"First one: This is NOTABUG. User has selected/inserted the wrong text if they didn't want this - see bug 51173.
+
+Second one: Definitely a bug, and one which I believe we have now fixed with the changes to how <nowiki>s are applied in Parsoid.
+
+Third one: Same as two - appears now to be fixed. Sorry for the inconvenience. :-(
+
+Fourth one: This is NOTABUG. User has created a paragraph with some leading whitespace, which means Parsoid needs to do something to stop it turning into a preformatted block. The solution is inelegant (we don't need to select the entire paragraph to stop this), but that is bug 50841.",1373638390,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,"Here are two more in case it helps with diagnosis:
+
+https://fr.wikipedia.org/w/index.php?diff=94682339
+
+https://en.wikipedia.org/w/index.php?diff=562790609",1372941123,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: Miscellaneous additions of nowiki tags,Again at https://en.wikipedia.org/w/index.php?title=Beximco&curid=1725818&diff=562676888&oldid=561183206 (possibly related?),1372853999,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-u7msjuo24hkzquuc5w2p,task_subcomment,NA
+VisualEditor: VE interface overlapping with main WP interface in monobook w/ small resolutions,"See https://en.wikipedia.org/wiki/File:Visual_Editor_-_Overlapping_issue.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372843980,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-n27a25omdfur3socqod5,task_description,resolved
+VisualEditor: VE interface overlapping with main WP interface in monobook w/ small resolutions,Deployed and confirmed as fixed.,1372893914,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n27a25omdfur3socqod5,task_subcomment,NA
+VisualEditor: VE interface overlapping with main WP interface in monobook w/ small resolutions,I think that this was fixed in gerrit 70851 - we'll be deploying it later today.,1372867380,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n27a25omdfur3socqod5,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,"What it says on the tin; if you resize an image, it with reports ""this isn't a change, can't save"" or saves and silently doesn't do anything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372840560,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-l36v7qffhro3qiv5v3ya,task_description,resolved
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,Moved to bug 61270,1392223392,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,"I'm not sure if this is the same issue, but as reported on English Wikipedia and tested by myself, using the image resizer to ""Make full size"" resulted in either a notice that no change had been made or a silent failure to save.
+
+This was tested on FF26, W7 and Chrome 32.0.1700.107 m, W7. 
+
+The reporting editor concludes that ""These new settings, for what they are worth, only work if the image already has a size indication (200px, 250px*250px, whatever), not when it only has a 'thumb' indication. Sadly, the latter is the default and by far most common situation.""
+
+He also questions the purpose of ""Make full size"", but I'll report that separately. 
+
+See: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=595141503#Advanced_image_settings.3F_More_VisualEditor_rubbish.",1392214363,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,*** Bug 51026 has been marked as a duplicate of this bug. ***,1374106684,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,Fixed and will be going out in a few minutes.,1374015979,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,"Change 73965 merged by jenkins-bot:
+Create MWResizeableNode mixin to control defaultSize flag
+
+https://gerrit.wikimedia.org/r/73965",1374015086,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work,"Change 73965 had a related patch set uploaded by Esanders:
+Create MWResizeableNode mixin to control defaultSize flag
+
+https://gerrit.wikimedia.org/r/73965",1373983741,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l36v7qffhro3qiv5v3ya,task_subcomment,NA
+Space inserted before link after single-character deletion,"From https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE_adding_spaces.2C_messing_with_citation_access-dates:
+
+I noticed something odd when using VisualEditor. I decided to use it when snooping around for various ""it's"" typos, for removing apostrophes seemed/is faster with VE than the old fashioned way. However, some of my edits seem to have done more than take out apostrophes. Seven times today ([http://en.wikipedia.org/w/index.php?title=Highcroft_Racing&diff=prev&oldid=562630195] [http://en.wikipedia.org/w/index.php?title=So_Emotional&diff=prev&oldid=562630132] [http://en.wikipedia.org/w/index.php?title=1988_in_British_television&diff=prev&oldid=562629968] [http://en.wikipedia.org/w/index.php?title=Olmaliq_FK&diff=prev&oldid=562629768] [http://en.wikipedia.org/w/index.php?title=FC_Jazz&diff=prev&oldid=562629613] [http://en.wikipedia.org/w/index.php?title=Brian_McDaniel&diff=prev&oldid=562629235] [http://en.wikipedia.org/w/index.php?title=Highlights_(band)&diff=prev&oldid=562629182]), VE added an extra space in a random place in the article (if it's hard to tell, on the last one it added the space right after ""its""). And then it altered references on [http://en.wikipedia.org/w/index.php?title=God_of_War_(series)&diff=prev&oldid=562631132 another], including changing access-dates. I don't think that's supposed to happen... [[User:Greengreengreenred|<font color=""#014421"">Green</font>]][[User talk:Greengreengreenred|<font color=""#50C878"">green</font>]][[Special:Contribs/Greengreengreenred|<font color=""#66FF00"">green</font>]]<font color=""red"">red</font> 02:25, 3 July 2013 (UTC)
+
+
+Might be a Parsoid bug based on selser tracing. There seems to be only a single space both in the original and the edited HTML.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372821780,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-iqdlibipj4aozqzz2www,task_description,resolved
+Space inserted before link after single-character deletion,"Change 71757 merged by jenkins-bot:
+Bug 50636: Don't extrapolate DSR on change
+
+https://gerrit.wikimedia.org/r/71757",1372829298,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,The space issue will be fixed with the above patch. The accessdate diff (http://en.wikipedia.org/w/index.php?title=God_of_War_(series)&diff=prev&oldid=562631132) is bug 50637.,1372828667,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,"Change 71757 had a related patch set uploaded by GWicke:
+Bug 50636: Don't extrapolate DSR on change
+
+https://gerrit.wikimedia.org/r/71757",1372825446,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,"In the accessdate example, the old markup is bad (duplicate accessdate); the second one apparently wins, which makes sense.  However, there don't seem to be any actual changes in that paragraph, so it ideally shouldn't be affected at all.",1372824675,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,"Offhand, without having investigated this, it seems like a DSR issue.",1372822249,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+Space inserted before link after single-character deletion,"Relevant part of the selser trace (note the extra space):
+
+SS: "", an experimental racing car. The car was designed to reduce aerodynamic drag dramatically allowing for quicker straight and cornering speeds while using half as much power and half as much weight. Despite skepticism over the project, the DeltaWing made its debut at the ""
+SS: "" ""
+SS: ""[[2012 24 Hours of Le Mans]]""",1372822048,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-iqdlibipj4aozqzz2www,task_subcomment,NA
+VisualEditor: Split mw.ViewPageTarget init from integration handling,"This doesn't mean that all of the integration needs to be independent (save dialog etc.) just the initialisation.
+
+It used to be that the integration was only initialisation (instantiate the editor with the html document to edit, basically only up to a dozen lines of code) but it has become much more than that.
+
+We need to separate integration and initialisation (initialisation will be part of the platform specific integration, but code-wise it should be the tip of the pyramid, not the bottom), so that our MediaWiki initialisation should be completely isolated so we can load it from the <head> and it will do only 2 things:
+
+1) Browser compatibility test (bug 50608)
+   - May depend on jQuery and a few plugins
+   - May not depend on any VE classes since those may break in our subset
+     of supported browsers (compared to MediaWiki/jQuery)
+
+   (if passed)
+2) Perform our changes to the interface to avoid flash of ""pre-init"" state
+   - Edit tab (bug 50542)
+   - Edit section links (bug 50540)
+   - Handle setup/teardown of VE from either clicking an ""Edit"" link
+     or by url query.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50677",1372800600,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rwwvww3qvgi4ff4ivkf7,task_description,resolved
+VisualEditor: Split mw.ViewPageTarget init from integration handling,This is now fixed (and deployed).,1372894223,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rwwvww3qvgi4ff4ivkf7,task_subcomment,NA
+VisualEditor: Split mw.ViewPageTarget init from integration handling,"Change 71929 merged by jenkins-bot:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372894020,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rwwvww3qvgi4ff4ivkf7,task_subcomment,NA
+VisualEditor: Split mw.ViewPageTarget init from integration handling,"Change 71929 had a related patch set uploaded by Krinkle:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372889781,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rwwvww3qvgi4ff4ivkf7,task_subcomment,NA
+VisualEditor: Browser compatibility test should not be done in the middle of init after (pre)loading all of core,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372798800,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pt2yvsftiewkmjm3j2nx,task_description,resolved
+VisualEditor: Browser compatibility test should not be done in the middle of init after (pre)loading all of core,This is now fixed (and deployed).,1372894193,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pt2yvsftiewkmjm3j2nx,task_subcomment,NA
+VisualEditor: Browser compatibility test should not be done in the middle of init after (pre)loading all of core,"Change 71929 merged by jenkins-bot:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372894014,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pt2yvsftiewkmjm3j2nx,task_subcomment,NA
+VisualEditor: Browser compatibility test should not be done in the middle of init after (pre)loading all of core,"Change 71929 had a related patch set uploaded by Krinkle:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372889784,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pt2yvsftiewkmjm3j2nx,task_subcomment,NA
+VisualEditor: Language links do not take namespace into account,"Check page settings for https://en.wikipedia.org/wiki/User:John_of_Reading?veaction=edit - it's probably not necessary to have language linking for userspace, but if we're going to do it the ability to distinguish sandboxes from articles would be good.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372756200,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-l5hcose5p2erl7wolwnd,task_description,resolved
+VisualEditor: Language links do not take namespace into account,"
+
+*** This bug has been marked as a duplicate of bug 49226 ***",1381266333,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l5hcose5p2erl7wolwnd,task_subcomment,NA
+VisualEditor: Page notices overlap dialogs,"**Author:** `Thehelpfulonewiki`
+
+**Description:**
+Page notice overlaps the close button on page settings
+
+I tried to edit Barack Obama using the Visual Editor. The page notice came up - which is fine - but then I clicked on the page settings without dimissing the page notice and wasn't able to dismiss the page notice. The page notice covers the close button so the only button I could press is ""apply changes"" to causes the page settings window to go away, allowing me to hide the page notice.
+
+I was told in #-visualeditor that you can click anywhere in the notice itself to dismiss it - something I didn't even consider doing because that's not standard behaviour for notifications (considering Facebook and even Echo). Please can we make the page notice dismissable by clicking on the ""1 notice"" area, even if you've got the page settings window up?
+
+See attached screenshot for an illustration of the problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49059
+
+**Attached**: {F11576}",1372730460,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-geudhodnzjlx4dkfmnsc,task_description,resolved
+VisualEditor: Page notices overlap dialogs,This problem is still reproducible with the link editor dialog.,1373940337,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-geudhodnzjlx4dkfmnsc,task_subcomment,NA
+VisualEditor: Page notices overlap dialogs,"This has now been fixed by Rob; marking as such. I hope we can deploy this to production soon, possibly tomorrow.",1372809200,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-geudhodnzjlx4dkfmnsc,task_subcomment,NA
+"VisualEditor: ""[edit | edit source]"" appears jumbled in RTL wiki with LTR interface","Inside an RTL wiki, if you set your interface to English (or any other LTR language) you will see that the '[edit | edit source]' links are jumbled.
+
+(Example: https://he.wikipedia.org/wiki/%D7%A4%D7%99%D7%96%D7%99%D7%A7%D7%94 - use English interface)
+
+This is probably again a case of bidi isolation. I can take a look at the code.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372726200,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-2q5s3rnh3ragcm43w2pm,task_description,resolved
+"VisualEditor: ""[edit | edit source]"" appears jumbled in RTL wiki with LTR interface",Merged and will go out with the next deployment.,1372781960,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2q5s3rnh3ragcm43w2pm,task_subcomment,NA
+"VisualEditor: ""[edit | edit source]"" appears jumbled in RTL wiki with LTR interface","Change 71568 merged by jenkins-bot:
+Fix for edit links, RTL wikis with LTR interface
+
+https://gerrit.wikimedia.org/r/71568",1372781877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2q5s3rnh3ragcm43w2pm,task_subcomment,NA
+"VisualEditor: ""[edit | edit source]"" appears jumbled in RTL wiki with LTR interface","Change 71568 had a related patch set uploaded by Mooeypoo:
+Fix for edit links, RTL wikis with LTR interface
+
+https://gerrit.wikimedia.org/r/71568",1372728163,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2q5s3rnh3ragcm43w2pm,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"The ""Edit source"" tab loads/renders a little bit after the ""Edit"" tab, sometimes more noticeably so, sometimes less. Relatedly, clicking the ""Edit"" tab very early on sometimes invokes the wikitext editor. 
+
+It would be preferable for both tabs to be rendered simultaneously with the correct default behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372725780,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_description,resolved
+VisualEditor: Tab layout should be done from a top-loading module,"This is now done, and deployed.",1375423118,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"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",1375414262,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"(In reply to comment #10)
+> Change 71929 merged by jenkins-bot:
+> Split off setup from the rest of mw.ViewPageTarget
+> 
+> https://gerrit.wikimedia.org/r/71929
+This introduces a top-loading module, but still does the tab layout from document ready, which means there's probably still is a flash. What we should really do is change the HTML from PHP, per comment 8.",1372894234,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Change 71929 merged by jenkins-bot:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372894017,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Change 71929 had a related patch set uploaded by Krinkle:
+Split off setup from the rest of mw.ViewPageTarget
+
+https://gerrit.wikimedia.org/r/71929",1372889786,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Ideally we'd alter the HTML using a PHP hook, then have a top-loading module that just conditionally adds some CSS to make the HTML generated by the PHP hook display correctly. That should allow us to get rid of the flashing tab behavior.",1372883412,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"(In reply to comment #6)
+> Shouldn't blacklisting occur much earlier (before actually messing around
+> with any buttons at all?). Before having done *anything* actually?
+> 
+> I'm hoping for a definite answer by James (or another dev involved).
+
+Yes; that's bug 50608. We're re-working a whole bunch of items around the initialisation and integration code for VisualEditor right now - bug 50612 tracks that.",1372883259,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Shouldn't blacklisting occur much earlier (before actually messing around with any buttons at all?). Before having done *anything* actually?
+
+I'm hoping for a definite answer by James (or another dev involved).",1372860735,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"**pinkampersand.wikimedia** wrote:
+
+(In reply to comment #4)
+
+> What do you mean by ""we display:none the former if the user doesn't pass the
+> blacklist code""? What is the ""blacklist code""?
+
+I believe James is referring to the part of VE that checks a user's browser and compares it against a ""blacklist"" of non-supported browsers. ""display:none""-ing the VE edit tab thereby stops people from using VE if their browser's not going to let them.
+
+One of y'all devs can correct me if I'm wrong here.",1372852109,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Sounds good. This could also fix bug 50402 at the same time I think?
+
+What do you mean by ""we display:none the former if the user doesn't pass the blacklist code""? What is the ""blacklist code""?",1372819046,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"Re-titling slightly per discussion; the suggestion is now:
+
+* VisualEditor (?in PHP for efficiency/simplicity) hooks into the page before display
+* On this hook,
+** we add the VE edit tab (""edit"")
+** we switch out the WT edit tab with a new label and tool-tip (""edit source"")
+** we display:none the former if the user doesn't pass the blacklist code",1372817658,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,"No, this bug is about the tabs at the top of the page (Read/Edit/Edit source), while bug 50540 is about the section-level edit links.",1372729158,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+VisualEditor: Tab layout should be done from a top-loading module,Should this be merged in some way with Bug 50540?,1372729099,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-l5ckh63ssiggmz3slrqg,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","A long-standing editor feels that the delay before the ""edit source"" option in sections disadvantages those who wish to bypass VE. Is it possible to have the ""edit source"" link visible always?
+
+See:
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562471642#Very_slow_and_featureless
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56337",1372724940,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_description,resolved
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",As per https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/August_2013_update this has been fixed.,1375464355,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #50)
+
+> That RFC can provide guidance, but there are issues of ends versus means.
+
+Exactly. The ""end"" of testing Visual Editor should not include the ""means"" of having it used by the unwary. The only people using VE at this point should be people that are completely aware that they are testing in addition to editing. We can't rely that new accounts have seen some previous notice, or that anonymous editors have seen any notice at all. The only way to ensure that people are aware that it is a beta editor is in the button text itself.",1375301804,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #49)
+> The only mention of the warning that it is beta came in the ""Oppose"" section.
+> The very fact that two of the only three oppose votes mention placing the
+> warning after VE has been invoked makes it clear that people commenting are
+> commenting in the context that the *button* should warn people that it's
+> beta.
+
+That RFC can provide guidance, but there are issues of ends versus means. Changing the section edit links to read ""beta"" would be a bad idea both for the English Wikipedia and for VisualEditor generally.
+
+As suggested in comment 46, the exact wording should be customizable by editing the relevant MediaWiki message pages on-wiki. This bug should focus on removing the animation altogether and providing a sane default behavior for VisualEditor.",1375301077,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #47)
+> (In reply to comment #45)
+> > I would suggest that we go with
+> > 
+> > [beta editor | stable editor] 
+> 
+> No. That RFC (linked in comment 45) ... suggests better advertising that
+> VisualEditor is beta software. 
+
+It specifically asks about the ""user interface"", not the advertising.
+
+(In reply to comment #48)
+
+> 
+> ,,, we don't need to point out that it's beta in the
+> section edit links (it would just be more annoying). 
+
+I suggest that you go back and read that section. The question is explicit. 
+
+Answer 1: The ""edit"" button should explicitly say ""beta editor"" 
+Answer 4: Please label that Edit button more clearly as the way to the Beta version.
+Answer 7: Indeed, per Kww (i.e. per answer 1)
+Answer 17: per User:Kww (again, per answer 1)
+Answer 26: There is no reason the ""edit"" button shouldn't mention the fact it's using VE
+Answer  28: Per kww (i.e. per answer 1)
+Answer 34: Per kww
+Answer 39: Label ""Edit for beta or worse"" (just kidding). Perhaps label as ""Edit slow"" or ""Edit risky"" or such
+
+All the remaining supports were in the context of actually changing the *button text*, even if the question said ""user interface"".
+
+The only mention of the warning that it is beta came in the ""Oppose"" section. The very fact that two of the only three oppose votes mention placing the warning after VE has been invoked makes it clear that people commenting are commenting in the context that the *button* should warn people that it's beta.",1375300376,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #46)
+> [visual edit (beta) | source edit] would be better but not optimal I don't
+> think. [edit | edit visually (beta)] is the most compact that I can come up
+> with, but I'm not claiming that as perfect.
+
+As stated in comment 47, we don't need to point out that it's beta in the section edit links (it would just be more annoying). We can advertise that VisualEditor is beta software in the VisualEditor interface itself (i.e., ?veaction=edit).",1375299134,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #45)
+> I would suggest that we go with
+> 
+> [beta editor | stable editor] 
+
+No. That RFC (linked in comment 45) is specific to one wiki and doesn't suggest using [beta editor | stable editor], it suggests better advertising that VisualEditor is beta software. This request should be filed as a separate bug (and cross-referenced with [[Wikipedia:VisualEditor/Improvements]]).",1375299017,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","I don't think [beta editor | stable editor] is good as it doesn't tell you what the functional difference between them is. We probably also want to stick with ""edit"" rather than ""editor"" (verb rather than noun). 
+
+[visual edit (beta) | source edit] would be better but not optimal I don't think. 
+[edit | edit visually (beta)] is the most compact that I can come up with, but I'm not claiming that as perfect. If one of them is labelled simply ""edit"" that should be listed first (regardless of which one it is).
+
+Allowing the titles to be set by a MediaWiki: namespace page would be ideal, but that is a different request and I can't remember if it has a bug or not.",1375298923,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #44)
+> This needs to be fixed as soon as possible. Compounded annoyance is a very
+> bad
+> thing.
+> 
+> Let's go with [edit | edit source] for now.
+
+Based on the results so far at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Default_State_RFC#Question_4:_Should_the_user_interface_explicitly_warn_editors_that_pressing_the_.22edit.22_button_is_using_beta_software.3F I would suggest that we go with
+
+[beta editor | stable editor] 
+
+or there will be more calls that WMF is not paying attention to the preferences of the Wikipedia community",1375298212,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","This needs to be fixed as soon as possible. Compounded annoyance is a very bad thing.
+
+Let's go with [edit | edit source] for now.",1375296805,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**lecotegougdelaforce** wrote:
+
+Two more comments, after reading the discussion pointed by comment 30 : 
+
+- this argument from Nick White needs emphasizing : ""I don't think two small edit links by section headings constitute clutter. Rather it emphasises *the* key
+thing about wikipedia, that editing is encouraged.""
+
+- the cluttering invoked to justify the hovering solution is actually an argument *against* the hovering : in any case when you hover the link the second option appears, so at one moment the same text will be visible anyway, and actually the hovering is adding a level of cluttering, blinking (including additional blinking when the hovering occurs without the user wanting to edit the section).",1375278214,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**lecotegougdelaforce** wrote:
+
+Glad to see this report already exists.
+
+The idea of having text for VE editing and an icon for standard editing is *wrong* : you can't have two different methods (namely text and image) for advertising two options of a single choice, it's an aberration in terms of user interface (I'm no expert though), it's completely counter-intuitive.  Furthermore people use to associate text *with* image (caption), which makes it even more counter-intuitive.
+
+As far as I'm concerned, I'd be satisfied if we could just switch the default editing method.  That is, I don't want to use VE as a standard, but an advertisement saying it may be useful in certain situations, so I'd prefer to keep it at the hand in case I want to give it a try.  However, I want the default editing action to be the standard editing.  That is, I want the first ""modify"" link to open the standard editor, and the link enabled by the hovering to be the VE.  Therefore, a simple ""default editor = standard/VE"" in the preferences would be enough for me.
+
+However I understand the reading issue mentioned in comment 25, so I'd prefer if the hovering was completely disabled and both links always present (possibly with the option to hide one or both in the preferences).
+
+Furthermore, I'm strongly for the idea to give the user the choice of his editor.  And when I say ""user"", I also mean ""new user"".  Not all users are WYSIWYGers, and though people seem (and they're probably right) to think that the standard editor may frighten some new users, hiding the standard editor by default may as well repel some new users.
+
+Therefore the best solution in my opinion would be to simply disable the hovering and keeping both links, with the possibility to hide one or both in the preferences.  The argument that it's too many links is absurd : on a webpage there are links everywhere, internet users are used to ignore them.  It's even more true for WP where almost half of words are links…",1375277119,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #40 by kwwilliams@kwwilliams.com)
+
+I was assuming of course that the visual editor was working well. I think that the visual editor should be turned off for anonymous IP users until it is working well. 
+
+The VE should have true section editing (instead of whole-page editing as it does now) before IP users are allowed to use the VE. 
+
+The VE also needs to be able to add references well before it is enabled again for IP users.",1375120403,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #39)
+> (In reply to comment #38 by Chris McKenna)
+> 
+> I think completely new users would be more confused by having to choose
+> between
+> 2 edit links in text format. We want to encourage them to try the WYSIWYG
+> visual editor first. 
+> 
+Why would you want to do that? Wouldn't it be better to steer them to the working editor if you need to ""steer"" them at all?
+
+The navigation needs to remain *neutral*.",1375113009,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #38 by Chris McKenna)
+
+I think completely new users would be more confused by having to choose between 2 edit links in text format. We want to encourage them to try the WYSIWYG visual editor first. 
+
+If there is one link and one icon they see the VE ""edit"" link and so they click it to edit. Nothing could be simpler up to that point. 
+
+Then they type in some text, and maybe add bold and italic via VE. So far, it is very simple, and exactly like their email composition.  
+
+My Google Mail ""compose"" link goes directly to the WYSIWYG editor. So should the ""edit"" link in Wikipedia. 
+
+Google Mail offers a ""plain text mode"" in an unlabeled dropdown menu at the bottom right of the compose window. 
+
+We don't want to make wikitext source editing difficult to access, and so an icon is direct access. But we won't confuse completely new users by having two openly-labeled ""edit"" links.",1375091920,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","It's not about aesthetics (that's the reason we have the hover) it's about usability. 
+
+One icon and one link would not likely slow me down considerably, but it would seriously impact new users and those who are not as computer savvy as the people who comment here. UIs need to consistent and accessible. There are two editors, and they need to be accessed in the same way. One icon and one link is guaranteed to cause confusion and it will require active thought far longer than two of the same (blame human psychology).
+
+Take a look at the user interfaces of all the websites and programs you use, and look at the ones you don't regularly use because you can do the same easier elsewhere. Notice how all the ones you think of as good are clear, intuitive and internally consistent. This is not a coincidence.",1375058688,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #35 by Chris McKenna)
+
+You said the following concerning why you want consistency:
+
+> Because there are two ways to do the same job (edit the page) the ways of
+> doing this need to look the same. 
+
+...
+
+> As explained above, ""clutter"" is very significantly less important than
+> consistency. If we need it to say ""edit"" at least once then we need two text
+> links. If two text links are two cluttered then we need two icons.
+
+I still do not see how one edit link being text, and one being an icon would slow down your editing in any way. It sounds more like an esthetic preference.  
+
+You like things in order. My room is probably a lot messier than yours. ;)
+
+I think many options should be put in user preferences. The more the better as far as I am concerned. More happy editors means more editing gets done.",1375047003,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Just to point out the importance of this bug:
+
+I just deactivated VisualEditor for this exact reason. I hate the hovering, and I'm mis-clicking regularly because of the VE replacing my well known ""Edit"" button. Since it is know activated also in my Homewiki (dewiki) I can't stand it any longer. Goodby VE!
+
+Actually I *tried* to give it a chance (I did not deactivate it up to now, although there are many possibilities around how to do it!), but the agressive way the VE is replacing UI links is just not acceptable.",1375018892,PHID-USER-v3yn5qf233ggnnnmvejc,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #34)
+> Chris McKenna said that a text link and an icon link were ""a nightmare from a
+> usability perspective"". 
+> 
+Yes, because they are inconsistent. 
+
+> You are saying ""it's about consistency"". Something can be completely usable
+> and
+> not be consistent. Why is consistency important to you? I do not see the
+> need. 
+Because there are two ways to do the same job (edit the page) the ways of doing this need to look the same. 
+
+> According to your logic, we should delete the watchlist star icon because it
+> is
+> inconsistent with the text links at the top of pages. 
+
+The watchlist star is irrelevant to this discussion. It does not offer an alternative interface to achieve the same job as one of the text links. Completely different situation
+  
+> An icon avoids clutter on section header lines. We still need ""edit"" as text
+> at
+> least once, since that is what makes Wikipedia what it is; the encyclopedia
+> that anybody can *edit*.
+
+As explained above, ""clutter"" is very significantly less important than consistency. If we need it to say ""edit"" at least once then we need two text links. If two text links are two cluttered then we need two icons.",1374997623,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #33 by Eduard Braun)
+> It's not about ""being difficult"" it's about consistency!
+> 
+> We have two equivalent ways of editing an article, therefore there should be
+> two equivalent buttons.
+> 
+> Either both of them should be textual links or both of them should be icons.
+
+Chris McKenna said that a text link and an icon link were ""a nightmare from a usability perspective"". 
+
+You are saying ""it's about consistency"". Something can be completely usable and not be consistent. Why is consistency important to you? I do not see the need. 
+
+According to your logic, we should delete the watchlist star icon because it is inconsistent with the text links at the top of pages. I believe the watchlist star icon was partially implemented as a way to save space at the top of pages, and to avoid having dropdown menus in smaller screens. 
+
+The star icon allowed the viewing of Wikipedia pages at smaller screen widths before the dropdown menus showed up at the top. 
+
+With edit links we are trying to avoid dropdowns, hover, and hidden edit links. 
+
+An icon avoids clutter on section header lines. We still need ""edit"" as text at least once, since that is what makes Wikipedia what it is; the encyclopedia that anybody can *edit*.",1374980634,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","It's not about ""being difficult"" it's about consistency!
+
+We have two equivalent ways of editing an article, therefore there should be two equivalent buttons.
+
+Either both of them should be textual links or both of them should be icons.
+
+None of them should be hidden by default.",1374973998,PHID-USER-v3yn5qf233ggnnnmvejc,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #31 by Chris McKenna)
+
+I don't understand. How is it difficult to click a static icon that is there all the time (without having to go through any hovering)? There is a star icon at the top of almost every Wikipedia page for adding or removing a page from one's watchlist. 
+
+If clicking an icon to get to the source wikitext editor is a nightmare, then how is making both links icons (as you suggest) better. I agree that the icon for the source wikitext editor should have alt text and tooltip. I should have stated that to begin with, but I assumed that would be done, just as it is for the watchlist star at the top of the page.",1374973136,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #30)
+> I think the least cluttered longterm solution for them might be
+> an
+> ""edit"" link for the visual editor, and an icon for the source wikitext
+> editor.
+
+Least cluttered perhaps, but a nightmare from a usability perspective. Either make both an icon (with alt text and tooltip) or both text links. Usability is far more important than avoiding a tiny bit of clutter.",1374926926,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #26 by Erik Moeller)
+> I agree we need to revisit this, Richard. We'll kick around some options, but
+> we won't be able to get a new interface out before next week at the earliest.
+
+I see that this is being discussed here: 
+*http://lists.wikimedia.org/pipermail/design/2013-July/subject.html 
+
+I note that in this message 
+http://lists.wikimedia.org/pipermail/design/2013-July/000804.html 
+you agree with Trevor Parscal: ""The hover effect is easy to drop - if we are all willing to take the hit on the clutter."" 
+
+I agree with you on this: ""If we want experienced users to test it every once in a while, give feedback on how it can be made better, and have them see the improvements, finding a solution that poses the least burden on them will give us the biggest win.""
+
+It needs to be emphasized that there are many experienced users who edit anonymously (IP edits). They will not be able to go to preferences to choose other options. I think both hover and dropdown will irritate those experienced IP editors. I think the least cluttered longterm solution for them might be an ""edit"" link for the visual editor, and an icon for the source wikitext editor.",1374891994,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #24)
+
+> My first thought is that you are putting a lot of effort into preserving an
+> option that doesn't work. The first and easiest step is to remove the button
+> for editing sections using the source editor until you actually have a source
+> editor that can edit sections. Similarly, your preference scheme seems OK,
+> but
+> the default should be ""Edit sections as wikitext"", at least until you
+> actually
+> have a source editor that can edit sections.
+> 
+
+Sleepiness had obviously hit. Replace with 
+
+My first thought is that you are putting a lot of effort into preserving an
+option that doesn't work. The first and easiest step is to remove the button
+for editing sections using the visual editor until you actually have a visual editor that can edit sections. Similarly, your preference scheme seems OK, but
+the default should be ""Edit sections as wikitext"", at least until you
+actually have a visual editor that can edit sections.
+
+While sleepiness had hit, the point remains valid: since Visual Editor doesn't work for sections, there's no reason to damage the user interface by pretending to support it.",1374849031,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","What about my suggestion in comment 15? I still think this would be a workable solution resolving most of the controversy around section edit links.
+
+The proposed setting whether to prefer VE or the WikiEditor could also be used to relabel the buttons to improve the workflow for everybody:
+* ""Edit"" for the edit button using the preferred editor
+* ""Edit Source"" or ""Visual Edit"" for the second button
+
+This way a simple ""Edit"" button would be the default way to edit an article, regardless of which editor the user prefers, while the other option was around for special use cases.",1374837475,PHID-USER-v3yn5qf233ggnnnmvejc,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #24)
+> The first and easiest step is to remove the button
+> for editing sections using the source editor until you actually have a source
+> editor that can edit sections.
+
+To clarify, ""source"" is one of the terms VisualEditor uses for wikitext.  So, the wikitext/source section editor has not changed (other than the label).",1374829183,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","I agree we need to revisit this, Richard. We'll kick around some options, but we won't be able to get a new interface out before next week at the earliest.",1374819700,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Discussed again at [[Wikipedia:VisualEditor/Feedback#Edit Source is upsetting. When reading is upsetting]]
+
+I think this comment highlights the problem for readers, not just editors or power users, presumably this is effecting IP readers as well:
+
+It is VERY unpleaseant for me to read with the new feature. When I pass the mouse over the edi button, appears a new button saying edit source. I know these things are great for editors. But they are really distracting because one scrolls the mouse accidentally, in all the horizontal white stripe, i mean one scrolls the mouse over any place at the same height of the screen that Edit button, then Wild Edit source button appears. This is horrible. Please, make it harder to find. This distracts the eye a lot, i'm tottally serious. Plase, don't take this for a joke, i'm serious, the editors may have another way to do that, for example clicking on a small STATIC button for visual editing, that would be GREAT! Thank youSantropedro1",1374818730,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**kwwilliams** wrote:
+
+(In reply to comment #13)
+
+> Section editing links
+> (x) Hybrid edit / edit source links [default]
+> ( ) Edit sections via VisualEditor
+> ( ) Edit sections as wikitext
+> ( ) Disable section editing
+> 
+> ...
+> 
+> We don't love the [ edit ] [ edit source ] static links, because it feels
+> cluttered and not the kind of user experience that we want to support.
+> 
+> Thoughts? If either of these feels like a reasonable path forward, we can
+> re-use this bug to track it, or start a new one.
+
+My first thought is that you are putting a lot of effort into preserving an option that doesn't work. The first and easiest step is to remove the button for editing sections using the source editor until you actually have a source editor that can edit sections. Similarly, your preference scheme seems OK, but the default should be ""Edit sections as wikitext"", at least until you actually have a source editor that can edit sections.
+
+My second thought is that for any choice that presents both, the animated is far worse, and probably gets worse for anyone that uses an interface with a long word that means ""edit"". When I see a page, it has little buttons labeled ""bewerken"" next to each section header, and as I'm moving my cursor there, it suddenly animates and ""brontext bewerken"" slides out to the side (which is strange, because my main button for editing source is labeled ""bron bewerken""). Not surprisingly, I'm accustomed to having the thing I'm aiming for not purposely jump out of the way once I try to get there. I'd prefer getting a popup and having to click twice to having the thing I'm aiming for run away. Of course, I can try to remember to aim 3 cm to the right of the button and click *there*, but that is really an odd UI.
+
+In terms of the VE feature that makes me curse every time it occurs, it's accidentally launching VE because the thing I was aiming for ran away while I was aiming for it.",1374814202,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #13 by Erik Moeller)
+
+> We don't love the [ edit ] [ edit source ] static links, because it feels
+> cluttered and not the kind of user experience that we want to support.
+
+If provided as a preference then it is not clutter, at least to that user. 
+
+If you don't provide this as a baked-in MediaWiki preference in the edit tab of preferences, then probably all Wikipedias in all languages, and all MediaWiki installations outside the Wikimedia world will provide buggy gadgets to provide the 2 static links. 
+
+For example; the buggy CSS hack described here:
+*[[Wikipedia:Village pump (technical)/Archive 114]] - see section ""Removing the animation from 'edit source' section links on Visual Editor"".
+
+Is it not a thousand times better for it to be a fully-maintained, baked-in preference that will not constantly become buggy after various MediaWiki updates?",1374541092,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**turingt** wrote:
+
+> 
+> We don't love the [ edit ] [ edit source ] static links, because it feels
+> cluttered and not the kind of user experience that we want to support.
+> 
+> Thoughts? If either of these feels like a reasonable path forward, we can
+> re-use this bug to track it, or start a new one.
+
+You seem to be under the impression that [ edit ] [ edit source ] dynamic links that appear and disappear on hover feel ''less'' clutter, but that's not the case.
+
+The least possible clutter that support both editors is to show shorter links, and make them static:
+
+[ edit | source ]
+
+or maybe get rid of the square brackets - they don't look at all necessary if both links are always visible:
+
+Edit | source
+
+See? No clutter at all, and more functional for all users regardless of their javascript or pointing device availability.",1374356199,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #20)
+> Are you sure the single link was the VE one?
+> 
+> I've seen some occasional cases where only the wikitext section links showed
+> (this is also the default, e.g. if you have JavaScript disabled), but I can't
+> recall one where only the VE section links showed, since the hover code has
+> been setup.
+
+It probably was a link to Source Editor, but when 'edit' could go to VE or SE, such confusion and concern results.  On mobiles, it's not possible to see what the link is without pressing it.",1374304107,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Are you sure the single link was the VE one?
+
+I've seen some occasional cases where only the wikitext section links showed (this is also the default, e.g. if you have JavaScript disabled), but I can't recall one where only the VE section links showed, since the hover code has been setup.",1373928461,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","A user on the English Wikipedia has today commented that the hover links are not always displaying when the system is being slow or unresponsive (their local system or the WMF servers). This obviously means that section editing in the classic editor is not available when its small footprint would be most beneficial
+
+For reference they included their technical specs:
+Downstream 20 Mb/s; Safari 6.0.5; Mac OS 10.8.4; 2.7 GHz Intel Core i7 (64-bit); 8 GB 1333 MHz DDR3; Flash 11.8.800.94; Java 1.6.0_51.",1373832913,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","I'd prefer just showing them always, too (they can then be easily be hidden separately with CSS if necessary). But others prefer how it is done now (see Erik Möller's concerns in comment 13).
+
+That's why I proposed a *prefer*ence here.
+
+Anyway, if we should decide against a preference, showing them always is the way to go, because the current hovering effects are a nightmare for both, accessibility and customizeability.",1373551894,PHID-USER-v3yn5qf233ggnnnmvejc,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**gigs** wrote:
+
+Eduard Braun's preferences proposal would work to solve all the use cases, but I don't see how this is superior to just always showing both links, with a preference for reverting to the old behavior (which already exists).
+
+Users will quickly adjust to clicking on their preferred mode, if both are always shown.",1373551134,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",Custom CSS workaround available at https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=563794311#Removing_the_animation_from_.22edit_source.22_section_links_on_Visual_Editor,1373539008,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","However this will be solved: Put thought in it!
+I could imagine, that this decision will determine whether people will be disabling/hiding VE or keep using it along with the Wikitext editor.
+
+A proposal from my side which might be a better fit from a user's point of view:
+
+1) One setting (radio button) that determines which editor the user prefers for normal tasks (e.g. whether ""edit"" or ""edit source"" is shown first in toolbar or whether ""edit"" or ""edit source"" is shown as section edit link while the other one is shown on hover only)
+(o) Prefer VisualEditor
+( ) Prefer Wikitext Editor
+
+2) One setting (radio button) to control how edit section links are handled
+(o) show preferred edit link, show the other one on hover
+( ) always show both edit section links
+    ([edit|edit source] or the other way round depending on 1)
+( ) only show preferred edit section link, don't show the other one at all.
+( ) no edit section links at all",1373509125,PHID-USER-v3yn5qf233ggnnnmvejc,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #13)
+> We've been kicking around the section editing behavior a fair bit, and we
+> recognize the need for more flexibility, in part because the mouseover
+> interface doesn't translate well to touch-based user interfaces. (We also
+> recognize that section-editing in VisualEditor overall is still a bit of a
+> crutch, but that's a larger discussion.)
+
+The two issues I'm seeing from users are that:
+
+A. some editors are annoyed by the animation, particularly when scrolling or trying to target a specific link with a mouse quickly (or when using a touchscreen device, as you note); and
+
+B. some editors are annoyed by VisualEditor generally and would simply like to disable/hide all traces of it.
+
+> What James and I would like to suggest here is a multi-way pref:
+> 
+> Section editing links
+> (x) Hybrid edit / edit source links [default]
+> ( ) Edit sections via VisualEditor
+> ( ) Edit sections as wikitext
+> ( ) Disable section editing
+> 
+> The section editing feature is already disable-able, so we could just merge
+> the pref.
+
+This proposed solution solves problem A (the animation/hover issue) for the non-default case (not really helpful...), while inhibiting users who want both links but without any animation/hover. Not great. For problem B, it mitigates the impact of VisualEditor slightly (though users are still left with two tabs at the top of the page and probably slower load times as a result of VisualEditor).
+
+> If folks think that's too much, we could just have a single
+> 
+> [ ] Support section editing via VisualEditor 
+> 
+> checkbox as this point, enabled by default, which turns on or off the hybrid
+> mode.
+
+This proposed solution doesn't solve problem A (animation/hover) and doesn't solve problem B (VisualEditor being enabled at all).
+
+I'm not sure either proposed (compromise) solution is better than the current situation. However, there's already an existing user preference to disable VisualEditor that was inexplicably removed. It's difficult to tell how many editors are having problem A or are having problem B, but re-adding a user preference to disable VisualEditor would solve problem B for sure and largely solve problem A (for those who find problem A to be a problem...).",1373505406,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","We've been kicking around the section editing behavior a fair bit, and we recognize the need for more flexibility, in part because the mouseover interface doesn't translate well to touch-based user interfaces. (We also recognize that section-editing in VisualEditor overall is still a bit of a crutch, but that's a larger discussion.)
+
+What James and I would like to suggest here is a multi-way pref:
+
+Section editing links
+(x) Hybrid edit / edit source links [default]
+( ) Edit sections via VisualEditor
+( ) Edit sections as wikitext
+( ) Disable section editing
+
+The section editing feature is already disable-able, so we could just merge the pref.
+
+Having three modes may seem like overkill at this stage but James feels that having an option for VisualEditor specifically at least puts a flag in the ground that we want to continue to improve section editing usability.
+
+If folks think that's too much, we could just have a single
+
+[ ] Support section editing via VisualEditor 
+
+checkbox as this point, enabled by default, which turns on or off the hybrid mode.
+
+We don't love the [ edit ] [ edit source ] static links, because it feels cluttered and not the kind of user experience that we want to support.
+
+Thoughts? If either of these feels like a reasonable path forward, we can re-use this bug to track it, or start a new one.",1373503336,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","I misspoke. The only VE gadget now in preferences is this one: ""Remove VisualEditor from the user interface."" 
+
+But my point is that each language version of Wikipedia should not have to create gadgets to provide VE options to its editors. 
+
+Some preferences need to be provided in all MediaWiki installations. Or at least all Wikimedia installations of MediaWiki. For example:
+*Display both ""edit"" and ""edit source"" links for sections without hover.
+*Remove VisualEditor from the user interface (VE still loads, but it can not be used).
+
+The first preference will mean that far fewer people will use the second preference. And the 2 preferences should be together so that people can see why they should choose the first preference over the other. The reason being that since VE still loads, one saves no load time by blocking access to using VE.",1373171885,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","There is no way this should be ""Lowest"" in importance. Moved up to ""Normal"". I would change enhancement to ""normal"" also, but developers still seem dead set against making the choice dead simple and easy; or as one recent commenter wrote: ""I am talking about giving editors easy way to choose the way they want to edit wikipedia."" This is a common request. 
+
+This needs to be a baked-in option in the edit tab of preferences. Not an ad hoc addon gadget as it is now in English Wikipedia. At least then registered editors can keep editing most efficiently. Choosing instantly between visual editor and source editor as the need arises. Registered editors do twice as many edits each month as anomymous IP editors. See chart:
+[[File:Anonymous, registered, and bot edits. English Wikipedia timeline by percent of edits.png]]
+
+So if you can't get it right for anonymous editors, at least allow registered editors to get it right with an option.",1373171236,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**gigs** wrote:
+
+It's difficult to focus without clicking on a touchscreen as well.",1373150662,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","(In reply to comment #7)
+> It seems no one has pointed out that pads and phones and touchscreens usually
+> can't ""hover"".  Hover stuff should pretty much never be a necessary part of
+> any web UI.
+
+It's not a necessary part.  First, the 'edit source' link at the top does not require any hover.  Second, the same thing occurs ('edit source' section link is shown) when you focus on the 'edit' section link (onfocus).",1373148915,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","This should be a priority and not just an enhancement. To think that future versions of MediaWiki will be crippled longterm by this incredibly buggy and slow visual editor is very discouraging. 
+
+At the very least there needs to be a preference for direct ""edit"" and ""edit source"" links built in to MediaWiki preferences on the edit tab of preferences. MediaWiki installations should not need a ""gadget"" preference added for this by each webmaster of every MediaWiki installation. 
+
+The hidden link to ""edit source"" is slowing down many editors. For more info and other options: 
+
+[[Wikipedia:VisualEditor/Feedback/Archive_2013_07#Edit_and_edit_source_links_so_confusing_I_had_to_disable_Visual_Editor_in_preferences]]
+
+[[Wikipedia:VisualEditor/Feedback/Archive_2013_07#Note_the_many_unhappy_people_who_do_not_see_the_HIDDEN_.22edit_source.22_link]]
+
+A thread linked in a previous comment (comment 1) has been archived:
+[[Wikipedia:VisualEditor/Feedback/Archive_2013_07#How_to_disable.3F]]
+
+There have been many more comments requesting a direct link to ""edit source"" on each section. See:
+[[Wikipedia:VisualEditor/Feedback]] and its archives.
+
+Slowing down the many editors who will continue to need source editing to edit complex things more easily is a really dumb idea. What is the logic? That you will irritate and trick editors into using the visual editor? That they will click the ""edit"" link instead of the ""edit source"" by being tricked? It is extremely irritating to have to spend extra time to get to source editing. You will not lack in bug reports by providing direct links to ""edit source"". 
+
+For help on putting links in Bugzilla threads:
+[[WP:Bugzilla]]",1373094343,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","**gigs** wrote:
+
+It seems no one has pointed out that pads and phones and touchscreens usually can't ""hover"".  Hover stuff should pretty much never be a necessary part of any web UI.",1373091895,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",Clarifying.,1372801897,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","@Krinkle: I think the change of the summary is wrong.
+
+This is (from what I get from the comments, the discussions linked are a little less clear I'm afraid) not about section ""edit source"" links being loaded with delay (although this would be an issue, too).
+It's about having to hover over the ""edit"" link to be able to see the ""edit source link"". They should both be directly accessible (without hovering and visibility changes).",1372801493,PHID-USER-v3yn5qf233ggnnnmvejc,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",This is (besides bug 50542) one of the main reasons a seamless coexistence of VisualEditor and Wikitext editor is *not* possible at this time (as intended by the WMF).,1372799152,PHID-USER-v3yn5qf233ggnnnmvejc,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Note that this request is being repeated a lot, including by people who are unhappy that mousing over causes words to pop up, which they say disrupts reading the page. They would prefer the words be always visible to avoid this.",1372767720,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover",This was proposed before and even had a rejected patch by me: I13bbb954.,1372725359,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+"VisualEditor: Display both ""edit"" and ""edit source"" links for sections without hover","Sorry - wrong section.
+
+See:
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562471375#How_to_disable.3F",1372725043,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-em7qpd4h4h3xgy2ceara,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"A firefox 5.0 user is reporting that blacklisting simply isn't working - they're seeing the VE, broken. Their response to ""are you spoofing user headers"" was along the lines of ""what the heck is that?"" which answers that question.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372719060,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_description,resolved
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,This is now deployed.,1372727423,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"Change 71554 merged by jenkins-bot:
+Blacklist Firefox <= 10 per reports that it's broken
+
+https://gerrit.wikimedia.org/r/71554",1372723165,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"(In reply to comment #6)
+> I re-checked FF10 on Windows 7:  whether editing a whole page or a section
+> of a page FF10 presents the loading... bars but never presents the editor
+
+OK, we'll blacklist Firefox 10 and under per the above patch; will see if we can do a quick deploy today to avoid user confusion.",1372721478,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,I re-checked FF10 on Windows 7:  whether editing a whole page or a section of a page FF10 presents the loading... bars but never presents the editor,1372721333,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"Change 71554 had a related patch set uploaded by Jforrester:
+Blacklist Firefox <= 10 per reports that it's broken
+
+https://gerrit.wikimedia.org/r/71554",1372721244,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"(In reply to comment #3)
+> Tried FF 5, 9, and 10, VE ""Edit"" links are available in all of them along
+> with
+> ""Edit source"" links.  In each case VE only displays the loading bars and does
+> not present any usable interface.
+
+We've had a user swear blind that everything works fine in FF 10. Clearly they misled us. :-(",1372721101,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"Tried FF 5, 9, and 10, VE ""Edit"" links are available in all of them along with ""Edit source"" links.  In each case VE only displays the loading bars and does not present any usable interface.",1372719656,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"Wait, so non-whitelisted browsers are let through? Is this documented anywhere?
+
+I'd suggest anything not whitelisted be blacklisted, frankly. We've got firefoxes 5, 9 and 10 producing substantial problems.",1372719459,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Firefox 10 and under have issues and should be blacklisted,"We don't blacklist Firefox 5. We currently blacklist:
+
+* MSIE <= 10
+* Android <= 3
+* Blackberry
+* Opera
+
+We whitelist:
+* Firefox >= 11
+* Iceweasel >= 10
+* Safari >= 5
+* Chrome >= 19
+
+All other browsers are let through, with a warning.
+
+Does this mean we should blacklist Firefox 5.0?",1372719336,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-otwsyh65xhzuochbdcrh,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"**Author:** `rachelqa99`
+
+**Description:**
+enter erroneous text for existing reference
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:Rachel99/testing_070113?veaction=edit
+
+**Attached**: {F11502}",1372712580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5mroix5k2facuxaaopyg,task_description,resolved
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,On review this was specifically fixed by the changes to how the references list was constructed; marking as such.,1380559887,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"I can't reproduce this either. Time for a close as ""worksforme""?",1380546929,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"Created attachment 12928
+screenshot of dialog
+
+I can't reproduce this; maybe the UI has been fixed?
+
+Attached is the list I see.  Typing 'ux' in the input box removes references that dont match the string 'ux'.  Typing 'sys' reduces the list to one reference that does match the box.
+
+**Attached**: {F11504}",1374557703,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"**rachelqa99** wrote:
+
+first reference is picked when erroneous text typed in
+
+**Attached**: {F11503}",1372712993,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list,"**rachelqa99** wrote:
+
+I have references that already exist. I want to reuse one of them. I choose reference bookmark icon.  It lists all current references under use current reference.  It is unclear what to type here.  If I type in erroneous text, it seems to let me insert it, and it chooses the first reference [ users 1].  It does not check to see if text corresponds to existing reference.
+Need directions on what to type for a existing reference, or how to choose existing reference.",1372712923,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5mroix5k2facuxaaopyg,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"I suspect this may be related to an existing bug, but if so I can't figure out how to find it.
+
+Looking at the very bottom change on http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562259398, we see the first in a series of edits where editing elsewhere adds duplicated characters to a template that I don't believe is being edited directly. (Further duplication occurred in these edits to the same page: http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562359846, http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562363670, http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562363840)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372695120,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_description,resolved
+VisualEditor: Duplicating text in template on unrelated edit,I *believe* that this is now fixed - marking as such. Please re-open if you find it happening again.,1383006754,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,Guillaume: This is a Parsoid bug (which I was able to reproduce). This current bug seems like a generic placeholder bug. I created bug 53429 in parsoid so we can identify more specifically what went wrong. You can add yourself to that bug if you wish.,1377639799,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"In this edit, a table was duplicated (but it wasn't in a template):
+
+https://fr.wikipedia.org/w/index.php?&diff=96159772
+
+Is it the same issue or should I open a separate bug report?",1377594995,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,Can someone check and see if https://bugzilla.wikimedia.org/show_bug.cgi?id=52618 should better be marked as a duplicate of this? Thanks!,1375957426,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"(In reply to comment #3)
+> en.wp user reports that adding a single hyphen to a page trigged this bug to
+> remove part of an infbox and duplicate other templates in the middle of a
+> category.
+> 
+> https://en.wikipedia.org/w/index.
+> php?title=IBM_Personal_Computer&diff=567356453&oldid=566275349
+
+The table at the end was not closed. I [https://en.wikipedia.org/w/index.php?title=IBM_Personal_Computer&diff=567437920&oldid=567357722 fixed it (for consistency's sake, I used the s-end template)] and VE edits and saves should not introduce dupes on this.",1375817388,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"I think this diff from fr.wp is another example?
+https://fr.wikipedia.org/w/index.php?title=Gen%C3%A8ve&diff=95604102&oldid=95601955",1375804621,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"en.wp user reports that adding a single hyphen to a page trigged this bug to remove part of an infbox and duplicate other templates in the middle of a category.
+
+https://en.wikipedia.org/w/index.php?title=IBM_Personal_Computer&diff=567356453&oldid=566275349",1375801774,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"This looks like the same issue, yes.",1375377912,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Duplicating text in template on unrelated edit,"Could this bug be responsible for these edits where one templates was duplicated and the other apparently duplicated and substed in the middle of a category link?
+
+https://en.wikipedia.org/w/index.php?title=Ford_Figo&diff=566719977&oldid=566176664
+https://en.wikipedia.org/w/index.php?title=Ford_Figo&diff=next&oldid=566719977",1375370248,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-4vsqha4nxg6sirme3ghc,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Screenshot of list indent problem
+
+If I add indent to any list item, it breaks. 
+
+The indented line gets moved to the end of the previous line.
+
+The live-changes looks as it is working properly, but the edit-diff (preview your changes) always shows it as broken. (See attachment)
+
+Confirmed with:
+* Firefox and Chrome,
+* with ordered and un-ordered list items, 
+* with items added to the middle of a list, and to the end of a list,
+* and with both new items added to a list, and existing items given increased indent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F11420}",1372641600,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_description,resolved
+VisualEditor: Likely invalid HTML emitted for list items,"Change 71395 merged by jenkins-bot:
+Bug 50483: Make sure nested list serialization is newline-insensitive
+
+https://gerrit.wikimedia.org/r/71395",1372708410,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Change 71395 had a related patch set uploaded by GWicke:
+Bug 50483: Make sure nested list serialization is newline-insensitive
+
+https://gerrit.wikimedia.org/r/71395",1372706751,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,This is not a new bug.  This has been around for a long time.  I went back to commits almost 3 months back and tested.,1372704536,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Looks like Parsoid serializer is newline sensitive in this case:
+
+$ echo '<ol><li>Foo\n<ol><li>Bar</li></ol></li></ol>' | node parse.js --html2wt
+#Foo
+##Bar",1372704376,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"$ echo '<ol><li>Foo<ol><li>Bar</li></ol></li></ol>' | node js/tests/parse.js  --html2wt 
+#Foo##Bar",1372704023,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"I'm guessing that VE emits the wrong HTML here, so reassigning to VE. Please move to Parsoid again if the VE HTML is sane.",1372703188,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Also:
+echo '<ol><li>foo</li><li>bar</li></ol>' | node parse --html2wt
+#foo
+#bar",1372694554,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"Cannot reproduce:
+
+echo -e '#foo\n#bar' | node parse --wt2wt
+#foo
+#bar
+
+Can you provide the HTML the VE sends?",1372694100,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Likely invalid HTML emitted for list items,"This appears to be a (new?) bug in Parsoid - 
+
+# Foo
+# Bar
+
+-> 
+
+# Foo## Bar
+
+rather than
+
+# Foo
+## Bar
+
+Unless we're breaking something in VisualEditor somehow?",1372691714,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fn66at2vne5i62qo6jnn,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"As per http://www.mediawiki.org/wiki/Help_talk:VisualEditor/User_guide#Discoverability .
+Might be handy, since we're pretty much beginners with it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372621440,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-pcueszubfgitqkx3f2bv,task_description,resolved
+VisualEditor: Add a link to the User Guide to the interface,This has been done and will go out later today.,1372703974,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"Change 71376 merged by jenkins-bot:
+Add user guide link to beta icon drop down
+
+https://gerrit.wikimedia.org/r/71376",1372703622,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"Change 71376 had a related patch set uploaded by Jforrester:
+Add user guide link to beta icon drop down
+
+https://gerrit.wikimedia.org/r/71376",1372699824,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"That sounds good. The link should probably be something like [[mw:Special:MyLanguage/Help:VisualEditor/User guide]] and live in a MediaWiki: interface message, so that wikis can customize it to link to a local page.
+
+My feeling is that the link to the user guide should persist even after we're out of the beta, but we can discuss this then.",1372679384,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Add a link to the User Guide to the interface,"Possibly add the help icon to the ""beta"" label, and have it as an option in the menu?",1372627245,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pcueszubfgitqkx3f2bv,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"[Forked from the more general 50350.]
+
+Currently when AbuseFilter blocks an edit made with VE, the only response we can display is:
+
+| The modification you tried to make was aborted by an extension hook
+
+When bug 32216 is done - AbuseFilter is changed to use the APIEditBeforeSave hook - we can display this significantly more nicely.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372618620,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xz7of2bozktz6cktgsun,task_description,resolved
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Then I suspect the problem is an extension of bug 50058, which will be fixed in time. If so, it's probably not worth prioritising as a new bug (or reopening this one) since abusefilter triggerers are likely to be new users, ergo on vector.",1374265703,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+Of course I use Monobook, Oliver.",1374265556,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Are you, by any chance, on monobook?",1374264793,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+Tested this, now that it is deployed, and have to say that while it the change came close to being a solution, it isn't quite there. The edit-filter notice produced when using the standard editor is large, easy to read, and quite clear. The edit-filter noticed produced when using VE is tiny, uses an infinitesimal font, and is extremely difficult to read.",1374264704,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"enhancement->major, as this is an integration bug.",1374185775,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,*** Bug 50727 has been marked as a duplicate of this bug. ***,1374112342,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,Warnings will now show (once we deploy).,1374090444,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Change 74102 merged by jenkins-bot:
+mw.ViewPageTarget: Show AbuseFilter warning in save dialog
+
+https://gerrit.wikimedia.org/r/74102",1374087934,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Change 74102 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Show AbuseFilter warning in save dialog
+
+https://gerrit.wikimedia.org/r/74102",1374023516,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,Marked as blocked by 51403 in AbuseFilter.,1373928234,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Change 73877 merged by jenkins-bot:
+mw.ViewPageTarget: Surface error messages from core edit api
+
+https://gerrit.wikimedia.org/r/73877",1373927436,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+Just in case it's important to the fix, the message returned by the abuse filter is free format and generally contains templates and other markup.",1373926866,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"(In reply to comment #8)
+> Change 73877 had a related patch set uploaded by Krinkle:
+> mw.ViewPageTarget: Surface error messages from core edit api
+> 
+> https://gerrit.wikimedia.org/r/73877
+
+This is not yet sufficient since we should be surfacing the
+warning associated with the filter (or the abusefilter-warning
+message by default). The most significant part we're missing
+right now is:
+* Localization
+* The fact that (at least for some filters) they can submit
+  the edit by just trying again.
+
+This is currently blocked by the AbuseFilter not sending the parsed version of the triggered warning through the API (see http://cl.ly/image/1E2r1J2U3K0v, I'm getting raw wikitext instead of HTML).
+
+And perhaps (though less important) we could also use a boolean property to distinguish between filters that are warnings that can be bypassed by trying again and filters which prevent the user from saving.",1373926321,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"Change 73877 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Surface error messages from core edit api
+
+https://gerrit.wikimedia.org/r/73877",1373926266,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,*** Bug 51139 has been marked as a duplicate of this bug. ***,1373495105,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"(In reply to comment #5)
+> Has this actually been deployed?
+
+No.
+
+> I just tested, and the error message has changed (it now reads ""invalid
+> error code"", while it used to read ""Error: the notification you have made
+> was aborted by an extension hook"").
+
+That's almost certainly caused by the ""fixing"" of bug 32216, which changes what we need to integrate with.",1373401097,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+Has this actually been deployed? I just tested, and the error message has changed (it now reads ""invalid error code"", while it used to read ""Error: the notification you have made was aborted by an extension hook""). If that was the fix, I think it's pretty obvious that it's incomplete, as it still isn't displaying the warning from the edit filter.",1373385258,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,*** Bug 50828 has been marked as a duplicate of this bug. ***,1373054299,PHID-USER-jnta3z3spxto3vbxdngm,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"(In reply to comment #2)
+> I strongly, strongly object to the categorization of this as an
+> ""enhancement"".
+
+""Enhancement"" does not mean ""not going to be done soon""; it merely means that this is not a feature that's meant to be currently working, but instead, a feature we'd like to add.
+
+This feature in particular is on our immediate work list, and hopefully will be done in the next week or so.",1372952430,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,"**kwwilliams** wrote:
+
+I strongly, strongly object to the categorization of this as an ""enhancement"". This is a basic feature that needs to be addressed. There aren't many edit filters that block edits, but when an editor trips one of the ones that does, its important that he have an idea as to what to fix. There's no place for an editor to even begin looking to find out what is happening and what it is about his edit that is causing it to fail. It's not really even obvious from the message that it's a content issue.",1372952091,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog,*** Bug 50719 has been marked as a duplicate of this bug. ***,1372921240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xz7of2bozktz6cktgsun,task_subcomment,NA
+VisualEditor: Newest CSS not showing up in production for some users (so reference editor not correctly formatted),"Screenshot
+
+See screenshot. Firefox 21.0, Windows XP. As well as misplacing the toolbar it's also hiding the 'create new source' on articles with lots of sources.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11391}",1372617600,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-3yckz2spdz6vwpvvlsja,task_description,resolved
+VisualEditor: Newest CSS not showing up in production for some users (so reference editor not correctly formatted),Roan fixed this in his mega-CSS-rewrite.,1373852943,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3yckz2spdz6vwpvvlsja,task_subcomment,NA
+VisualEditor: Newest CSS not showing up in production for some users (so reference editor not correctly formatted),*** Bug 50455 has been marked as a duplicate of this bug. ***,1372620610,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3yckz2spdz6vwpvvlsja,task_subcomment,NA
+VisualEditor: Newest CSS not showing up in production for some users (so reference editor not correctly formatted),"Renamed (aka, I hate ResourceLoader's caching, some times :-().",1372620482,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3yckz2spdz6vwpvvlsja,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,"The formatting icons of the VisualEditor toolbar are currently ""B"" for bold, ""I"" for italics, the chain for links and the remove icon to clear formatting.
+
+This series of icon seems to indicate that links are a kind of formatting. However; ""Clear formatting"" doesn't affect links; it only removes bold and italics.
+
+Either links *are* a kind of formatting, and the ""Clear formatting"" action should remove them, or they aren't, and the Link icon shouldn't stand in the middle of icons that add and clear formatting. The current order and behavior are confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372600920,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-xid2rg44chmbsuqujmzr,task_description,resolved
+VisualEditor: Clear annotations icon no longer clearing link annotations,Fixed and will go out in a few minutes.,1373930966,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,"Change 73896 merged by jenkins-bot:
+Compare annotations by name only when clearing/toggling
+
+https://gerrit.wikimedia.org/r/73896",1373930577,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,"Change 73896 had a related patch set uploaded by Esanders:
+Compare annotations by name only when clearing/toggling
+
+https://gerrit.wikimedia.org/r/73896",1373929632,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,*** Bug 51018 has been marked as a duplicate of this bug. ***,1373504485,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: Clear annotations icon no longer clearing link annotations,This is a regression; it used to work fine - relabelling as such.,1372611822,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xid2rg44chmbsuqujmzr,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,"It is currently not possible to add a reference to an image/media caption, nor to edit existing ones.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52427
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49657",1372597320,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_description,resolved
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,*** Bug 54949 has been marked as a duplicate of this bug. ***,1380844957,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,This was completed as part of the NewFromDocumentReplace work that Roan did last week.,1380835418,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,"Changing this to reflect that now references do appear in the toolbar for media items, but can't be inserted or edited (and the list of existing references to insert is blank - suggests something's pointed at the wrong document/etc.?).",1379657377,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,"bug 51992 comment 0 :
+http://en.wikipedia.org/wiki/User:Kww/fileref is about as simple of a testcase
+as I could develop. Given this structure:
+
+[[File:Red Wine Glass.jpg|thumb|upright|A ""large"" (250&nbsp;ml) glass of
+12%&nbsp;ABV red wine has about three units of alcohol. A ""medium""
+(175&nbsp;ml) glass, such as the one shown, has about two units.<ref> Even
+though the sizes of wine glasses are defined in UK law, the terms ""large"",
+""medium"", ""standard"" etc are not defined in law.</ref>]]
+
+
+There's no way to edit the reference.
+
+----------------
+bug 51992 comment 1 :
+Simpler illustration, still in http://en.wikipedia.org/wiki/User:Kww/fileref
+
+I don't think it's possible to edit that pesky footnote.
+[[File:Red Wine Glass.jpg|thumb|upright|description<ref>pesky footnote</ref>]]
+
+{{reflist}}",1374702671,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+VisualEditor: References in media captions appear but aren't editable or successfully insertable,*** Bug 51992 has been marked as a duplicate of this bug. ***,1374702531,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-wwlsd2ozt42kgfcsmka4,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Screenshot1
+
+There are, I think, some UI improvements to be made to the reference editor - User:Popcornduff gets credit for these :).
+
+When you first open the reference editor, you're presented with something like screenshot 1, which asks you ""What do you want to reference?"" If the user is coming to try and add a new reference, this is highly confusing - the first UI element they're presented with prompts them to put time into a series of actions that cannot possibly end with them finding what they want. The cue also doesn't make clear to any user what the search bar is actually doing - filtering existing references. It seems like the blurb here might need changing to align it with what the search bar actually does; ""search existing references on this page""?
+
+If you click ""create new source"", absolutely nothing happens - it's a highlightable element, and after a bit you can puzzle out that it unlocks ""create reference"", but it's not immediately clear. Still, you end up with it highlighted (see screenshot2). The blurb in ""insert reference"" is rather confusing; what am I inserting? I'm here to /add/ a new reference, I haven't written it out yet. My suggestion would be to have ""create new source"" take you straight to the source creation interface using a one-click mechanism, rather than having it free up ""insert no references"".
+
+Still, you click it, and you get to screenshot3, of a window tagged ""reference content"". Quoth the user, ""Is it reference the verb - am I referencing content here? Or am I giving content to the reference?
+
+What is the Options heading all about, and what does ""Use this group"" mean?
+
+I have a little window here to type into. I'm not sure what to type. Do I just write out my reference in Wikimarkup and click ""Apply changes""? Or do I write them out as if I'm writing a list of references at the end of an essay?
+
+At this point I'm really disappointed. I was hoping to be given a complete list of individual fields to fill out - a box for author, a box for date, a box for date accessed, a box for the title, a box for the URL, and so on - and have this generate the reference nicely for me. Instead, I seem to have the old system in a confusing UI.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51848
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53590
+
+**Attached**: {F11364}",1372596600,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-b74srkob65ougmewgpvd,task_description,resolved
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows",This was resolved with the new citation system released last month.,1401472375,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows",*** Bug 51184 has been marked as a duplicate of this bug. ***,1377831014,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","(In reply to comment #8)
+> The ""what do you want to reference?"" field, which exists solely to filter
+> through existing references, still displays if there are zero existing
+> references.
+
+This sounds like bug 51848",1377597887,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","At en.wp user:Risker reports on feedback she received running an editathon. Relevant to this bug is:
+
+To a person, they all said that VE was *more* difficult to use than wikitext, especially with respect to references. Now, they had all had reinforced to them the importance of referencing factual information, so they were all trying to include references. They pointed out that at least with the wikitext editor, they could pull up templates that were complete and they didn't have to try to figure out the parameters. They were using mostly printed sources, not websites, so there was no URL to use as a quick-and-dirty reference insertion.",1377597769,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Change 74191 merged by jenkins-bot:
+Reference dialog commingling
+
+https://gerrit.wikimedia.org/r/74191",1374183562,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Change 74191 had a related patch set uploaded by Jforrester:
+Reference dialog commingling
+
+https://gerrit.wikimedia.org/r/74191",1374182072,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","The ""what do you want to reference?"" field, which exists solely to filter through existing references, still displays if there are zero existing references.",1372858754,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Yes, I think the ""wiki-specific workflows"" is key.  On wikis (including English Wikipedia) that use:
+
+<ref>{{some template|firstparam=a}}</ref>
+
+with a few key some templates, it's worth allowing a simplified flow for those (while still providing the full flexibility of arbitrary references and arbitrary templates where needed).
+
+Within a template, it's also verbose due to the screen layout.  E.g. I would consider keeping parameter name and value on the same screen (for named parameters), and making it easy to add the next parameter without going up to the root.  The latter can be done without the former.
+
+I'd recommend trying ProveIt (https://en.wikipedia.org/wiki/User:ProveIt_GT) on English Wikipedia if you haven't.  I don't expect you to take the same approach we did (and don't look at the ""parser"").  The reference browsing part also probably doesn't apply, but the add mode in particular shows how the GUI can be streamlined when it doesn't attempt to be fully general.",1372829687,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Please don't roll this out to everyone until this is fixed, as until it is there is going to be a lot of cleanup work needed. I agree with those above who say this might mean less references. I quickly disabled it the first time I tried to create a new citation.",1372761439,PHID-USER-wqo7db5tur74g52lu64y,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","**gwaw_2003** wrote:
+
+I'd have to agree with PamD above. If anything, just steal the RefToolbar code, and make it work with VE as a temporary fix for enwp. This cannot be rolled out to new editors the way it is, or we'll have a ton of ""well I hated how the references worked so I stopped trying to use them at all"" edits from new editors.",1372728086,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Thanks for these comments; obviously the references system is a work in progress and we had already planned to undertake (at least most of) these improvements, but we hadn't had the time to write it down in bugzilla - will use this to track those improvements now.",1372691404,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Please look at how RefToolbar behaves (I choose whether my ref is a website, book, etc; I get offered a set of useful boxes into which to input the data; I click on ""Preview citation"" to see that it looks OK; I click on ""Add citation"". Job done.), and give this sort of useful guidance to editors adding references in VE.",1372691060,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Screenshot3
+
+**Attached**: {F11366}",1372596695,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: Improvements to reference editing, including local wiki-specific workflows","Screenshot2
+
+**Attached**: {F11365}",1372596681,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-b74srkob65ougmewgpvd,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","When adding a new link to an existing page, the text is automatically capitalized, even if the user entered the text in lowercase. Many links don't need to be capitalized, so users shouldn't have to clean up after VisualEditor decides to capitalize them.
+
+Note that when you're adding a new link to a page that doesn't exist, the inserted link preserves the capitalization that was entered by the user (which is the expected behavior)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50945
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50678
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50745
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53566",1372587540,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_description,resolved
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","The above changes behaviour if the user types in the entire anchor in a different case (e.g. iPhone vs. IPhone), which is I think sufficient to close this bug for now; different ways of suggesting links might want to come off the outcome of bug 53566. (It will be deployed to the cluster from Thursday 5 September, and to Wikipedias on Thursday 12 September).",1378254877,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Change 82054 merged by jenkins-bot:
+Offer the typed text as a link suggestion if the page is valid
+
+https://gerrit.wikimedia.org/r/82054",1378254752,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Change 82054 had a related patch set uploaded by Esanders:
+Offer the typed text as a link suggestion if the page is valid
+
+https://gerrit.wikimedia.org/r/82054",1377900648,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","(In reply to comment #9)
+> I think creating a bug for
+> MediaWiki having page-level meta-data about the correct display of a page's
+> title would be great, yes.
+
+Done, see bug 53566",1377811932,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","(In reply to comment #8)
+> Until that happens I think we should preserve the case of the input, as even
+> if that isn't what people want it is easily possible to change and pretty
+> intuitive how to do it - ie, type ""foo"" get ""[[foo]]"" but wanted ""[[Foo]]"",
+> all you need to do is type ""Foo"" instead. The current behaviour means you get
+> ""[[Foo]]"" regardless of what you want or do.
+
+Possible, but a bit messy when writing certain articles like BLPs where most link targets will be proper nouns.
+
+> The only other thing I can think of is for VE to read and respect things like
+> {{lowercase title}}. Once it does that then it should also respect things
+> like {{correct title}} for a default display text, and we should probably
+> create a {{Proper noun title}} for titles that should always be capitalised by
+> default.
+>
+> Or rather than using templates we could move the title information into page
+> metadata. I have no idea whether any of this is practical, but if it is I
+> guess it would be better as one or maybe two separate bugs.
+
+Yes, certainly for this to be used in VisualEditor it would need to be a proper feature and not one hacked into a template; I think creating a bug for MediaWiki having page-level meta-data about the correct display of a page's title would be great, yes.",1377808735,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","The best thing, as noted at 48789, is for there to be two input boxes - one for the link target and one for the displayed text. 
+Until that happens I think we should preserve the case of the input, as even if that isn't what people want it is easily possible to change and pretty intuitive how to do it - ie, type ""foo"" get ""[[foo]]"" but wanted ""[[Foo]]"", all you need to do is type ""Foo"" instead. The current behaviour means you get ""[[Foo]]"" regardless of what you want or do.
+
+When the second input box is added then we should use the case as input as the default. 
+
+The only other thing I can think of is for VE to read and respect things like {{lowercase title}}. Once it does that then it should also respect things like {{correct title}} for a default display text, and we should probably create a {{Proper noun title}} for titles that should always be capitalised by default. Or rather than using templates we could move the title information into page metadata. I have no idea whether any of this is practical, but if it is I guess it would be better as one or maybe two separate bugs.",1377804697,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Clarifying what this is in the title:
+
+| New link annotations' anchors get their first character capitalised, even if you didn't want that
+
+->
+
+| When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors
+
+The problem is in the link suggester (it's the same behaviour in category and template selection, except that those always capitalise the first character so no-one cares.
+
+When you trigger the link inspector on no selection and type in ""foo"", you are given suggestions like:
+
+* Foo
+* Foobar
+* Fooian
+
+Selecting any of these picks not just the target, but also the text of that target as the anchor (good) and the capitalisation of that target (less good).
+
+However, if I've typed ""foo"", did I definitely want [[foo]] rather than [[Foo]]? Should we show both [[Foo]] and [[foo]] options in the list if you type in ""foo"", but only [[Foo]] if you type in ""Foo""?",1377803059,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","From bug 53495:
+Currently whenever a user enters a link when no text is selected the first
+character of the displayed link is always capitalised. This is often incorrect,
+e.g. in the middle of a sentence or for articles like [[iPhone]] or [[grep]].
+
+Especially until bug 50678 is fixed, correcting this is not at easy or
+intuitive.
+
+So, at least until bug 48789 and bug 50945 are fixed and the display text is
+settable in the dialog, and probably beyond that, it would be best if the
+displayed link used the same case as the search term entered. i.e.
+
+User entry ->  wikitext equivalent of desired output
+Green   ->  [[Green]]
+green   ->  [[green]]
+iPad    ->  [[iPad]]
+HAMmer  ->  [[Hammer]]
+london  ->  [[london]]
+
+Yes, this will result in some wrong captialisations, but no more than at
+present and will only be temporary (as noted above)",1377802682,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors",*** Bug 53495 has been marked as a duplicate of this bug. ***,1377802569,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","(In reply to comment #3)
+> Are you talking about:
+> 1. Ctrl+K
+> 2. Type a lcase work
+> 3. Press enter twice
+
+Yes. For step 3, it also happens when you click on a suggestion.",1377594263,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Are you talking about:
+1. Ctrl+K
+2. Type a lcase work
+3. Press enter twice
+
+because that's the only way I can reproduce, and after the first press of enter it shows you that it has capitalised the word due to autocomplete?",1377558575,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Yes, I can still reproduce it. Note that I'm talking about the behavior when you enter Ctrl+K and type text, not the behavior when you add a link to existing text.",1377175898,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors","Is this still happening, Guillaume? I can't reproduce it.",1377173293,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-3tkt5wwlr2pp4a6ayi3s,task_subcomment,NA
+VisualEditor: Link inspector in a slug can select content in the previous or following paragraphs,"If the cursor is in a slug and you press the link button, the selection jumps to the nearest content - which crosses out of the local <p> and into the <p> beforehand or afterwards (whoops).
+
+Link inspector should detect that it is in a slug and not attempt to mangle the selection with nearestContentOffset, but just trigger with a 'blank' selection.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52256",1372572900,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rxqaxhgvcsfou4tzboet,task_description,resolved
+VisualEditor: Link inspector in a slug can select content in the previous or following paragraphs,This was fixed by gerrit 81437.,1377888669,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rxqaxhgvcsfou4tzboet,task_subcomment,NA
+VisualEditor: Link inspector in a slug can select content in the previous or following paragraphs,"As a follow-up, if you have <start of document> <block slug> <block slug> <block slug> <block slug> <p> in a document, and have the cursor in the second slug, pressing Ctrl+K will move the selection to the top of the document and put the contents there (whee); in the third or fourth, to the first word of the <p>. Not great.",1372573764,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rxqaxhgvcsfou4tzboet,task_subcomment,NA
+VisualEditor: References with duplicated content are normalised away,"If you have a page like:
+
+<ref name=""foo"">Foo</ref> ...... <ref name=""foo"">Foo</ref>
+
+VE will normalize this to:
+
+<ref name=""foo"">Foo</ref> ...... <ref name=""foo"" />
+
+The contents of the second <ref> tag are obviously ignored, but we should round-trip their existence correctly.
+
+
+http://tools.wmflabs.org/visualeditor/dirtydiffs/2013-06-30_00-52/Genetic_history_of_the_Iberian_Peninsula.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372567200,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2ttmyole76xyfw5lxpgw,task_description,resolved
+VisualEditor: References with duplicated content are normalised away,This was fixed in gerrit 71275 by Roan.,1372705872,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2ttmyole76xyfw5lxpgw,task_subcomment,NA
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,"After having saved a template on a page, and edit it again, template data for the template is visible, but any parameter used is not showing templatedata, even though it displayed it correctly when I created the template
+
+test I made on beta was {{test|name = hello}}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372554600,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_description,resolved
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,"Think we have subsequently fixed this, probably as part of the re-write of the transclusion dialog/TemplateData link in July; marking as such. Please re-open if it recurs.",1384200108,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_subcomment,NA
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,Can't reproduce this bug.,1384198743,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_subcomment,NA
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,"When I make a new template entry and open the template before I've saved the page, it looks like following:
+http://i.imgur.com/HxaU7F1.png
+
+But after having saved the page, and enter template edit again, I'm getting following:
+http://i.imgur.com/VPROUwb.png",1372596044,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_subcomment,NA
+VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog,"(In reply to comment #0)
+> After having saved a template on a page
+
+By a template, you mean a template transclusion or the template itself?
+
+
+> and edit it again, template data for
+> the template is visible, but any parameter used is not showing templatedata,
+
+So when you edit the tranclusion with VisualEditor template data for the template is visible but not for the parameters? What does that mean?
+
+You say it is visible for the template but not for the parameters. So what is visible then?
+
+> even though it displayed it correctly when I created the template
+
+Displayed what?",1372557963,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey46lj4dpzgt5ypwdhi4,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"After I added the <templatedata> to [[pt:Template:Referências]], I opened a page in which it is used, setting ""uselang=pt"" and ""uselang=pt-br"" in the URL:
+1) https://pt.wikipedia.org/wiki/Arte?veaction=edit&uselang=pt
+2) https://pt.wikipedia.org/wiki/Arte?veaction=edit&uselang=pt-br
+In the first case, when I opened the Transclusion dialog (by clicking in the references section, where the template is used) the template description was shown (as expected). Typing one of the template parameters, I also get its label normally.
+
+On the other hand, for the second link the user language (pt-br) was different from the content language (pt) and the user see no description and no labels.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50888",1372534860,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_description,resolved
+TemplateData: Process language fallback and conversion server-side,"Change 87724 merged by jenkins-bot:
+Implement getInterfaceTextInLanguage and use API and Parser
+
+https://gerrit.wikimedia.org/r/87724",1381172101,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"Change 87724 had a related patch set uploaded by Krinkle:
+Implement getIntefaceTextInLanguage and use API and Parser
+
+https://gerrit.wikimedia.org/r/87724",1381078137,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #14)
+> Oh. I assumed the jQuery.i18n (or one of the other JS, MW-independent tools
+> that the Language Engineering team have built) would have this built in. Is
+> that not the case?
+
+I can't say there isn't one but I've never heard of this.
+
+BTW I also want a similar one on server side.",1374922596,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #17)
+> Also, this way we can provide good values for languages that don't exactly
+> fallback but use a language converter. Which is also something that could
+> potentially be done client side, but I don't see that happening just yet.
+
+Which isn't really doable currently I guess; or it requires delivery of huge conversion tables (for Chinese).",1374920975,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"Also, this way we can provide good values for languages that don't exactly fallback but use a language converter. Which is also something that could potentially be done client side, but I don't see that happening just yet.",1374863198,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"For now this is up to the client side to handle, which realistically means it won't be handled (current language > en > nothing).
+
+
+For the future I intend to have the templatedata API take a parameter for language code and resolve it on the server side. For three reasons:
+
+* On wikis where there is more than 1 language commonly used (which is the whole point of this bug and where it is relevant, since if there is only 1 language, the wiki author can just specify { ""description"": ""Text."" } without lang-codes)..., on those wikis there will be more than 1 language defined. This will result in a large blob of JSON being transferred to e.g. VisualEditor for each template which is quite a lot of data.
+
+* Even so, it would then still require the client-side to have knowledge of all of this and process it. Which involves a lot of language data being send to the client, a lot of translations being sent to the client, and the then client having to do all the computation for it. We can solve this the same way we solved it in ResourceLoader; We'll still cache it, but fragment it by language code based on request context.",1374863078,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #8)
+> (In reply to comment #6)
+> > So I'm not too Wikidata-savvy, but it seems this patch might be useful (if
+> > it's
+> > not, ignore me and carry on):
+> > 
+> > https://gerrit.wikimedia.org/r/72867
+> > 
+> > Right now there is no way to determine the real language of a message from
+> > the
+> > CDB cache. That patch changes this.
+> 
+> Not really. Labels and descriptions in TemplateData are stored in some JSON
+> blob in a customized format, rather than normal messages.
+
+Gotcha. Carry on. Sorry I couldn't help.",1374862510,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #13)
+> (In reply to comment #12)
+> > (In reply to comment #11)
+> > > (In reply to comment #9)
+> > > > I don't think that's a good outcome. If there isn't a description in your
+> > > > language (in this case, pt), we shouldn't magically tell you that we've given
+> > > > you a message in a different language (we don't do this for the MW messages
+> > > > framework, for instance).
+> > > 
+> > > BTW this comment means WONTFIXing this whole bug.
+> > 
+> > Why?
+> > 
+> > This is just me saying that I don't think that instead of ""Chien"", if it
+> > doesn't exist in French we should give users ""Dog -- OMG We gave you this
+> > message in English even though you asked for it in French!"", which feels
+> > significant over-kill.
+> 
+> Then I guess your point is that pt-br and pt are more similar, so falling
+> back from pt to pt-br is acceptable, while fr and en are not this case.
+
+Yes.
+
+> However technically pt-br and pt have the same relationship as fr and en,
+> or we'll have to compose some language similarity table ourselves, and manage
+> to resolve many edge cases (eg. dialects).
+
+Oh. I assumed the jQuery.i18n (or one of the other JS, MW-independent tools that the Language Engineering team have built) would have this built in. Is that not the case?",1374862470,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #12)
+> (In reply to comment #11)
+> > (In reply to comment #9)
+> > > I don't think that's a good outcome. If there isn't a description in your
+> > > language (in this case, pt), we shouldn't magically tell you that we've given
+> > > you a message in a different language (we don't do this for the MW messages
+> > > framework, for instance).
+> > 
+> > BTW this comment means WONTFIXing this whole bug.
+> 
+> Why?
+> 
+> This is just me saying that I don't think that instead of ""Chien"", if it
+> doesn't exist in French we should give users ""Dog -- OMG We gave you this
+> message in English even though you asked for it in French!"", which feels
+> significant over-kill.
+
+Then I guess your point is that pt-br and pt are more similar, so falling back from pt to pt-br is acceptable, while fr and en are not this case. However technically pt-br and pt have the same relationship as fr and en, or we'll have to compose some language similarity table ourselves, and manage to resolve many edge cases (eg. dialects).",1374859742,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #11)
+> (In reply to comment #9)
+> > I don't think that's a good outcome. If there isn't a description in your
+> > language (in this case, pt), we shouldn't magically tell you that we've given
+> > you a message in a different language (we don't do this for the MW messages
+> > framework, for instance).
+> 
+> BTW this comment means WONTFIXing this whole bug.
+
+Why?
+
+This is just me saying that I don't think that instead of ""Chien"", if it doesn't exist in French we should give users ""Dog -- OMG We gave you this message in English even though you asked for it in French!"", which feels significant over-kill.",1374858682,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #9)
+> I don't think that's a good outcome. If there isn't a description in your
+> language (in this case, pt), we shouldn't magically tell you that we've given
+> you a message in a different language (we don't do this for the MW messages
+> framework, for instance).
+
+BTW this comment means WONTFIXing this whole bug.",1374858103,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #9)
+> (In reply to comment #7)
+> > (In reply to comment #5)
+> > > Fine technically - I think users would be upset and confused.
+> > 
+> > So you'll need to prepare for some interface design to tell users that ""Some
+> > text written in English"" and ""Some other text written in Spanish"" lines are
+> > not in pt.
+> 
+> Why couldn't the TemplateData just be written in the users's language?
+
+You can't expect all templatedata blocks to have labels in all hundreds of languages which MediaWiki supports.
+
+> > And the format of JSON needs to be modified to include this info.
+> 
+> I don't think that's a good outcome. If there isn't a description in your
+> language (in this case, pt), we shouldn't magically tell you that we've given
+> you a message in a different language (we don't do this for the MW messages
+> framework, for instance).
+
+We do so in Wikibase, if the user indicates that they can read another language -- in our implementation it checks {{#babel: }} currently but some global preferences here will be nice of course.",1374858004,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #7)
+> (In reply to comment #5)
+> > Fine technically - I think users would be upset and confused.
+> 
+> So you'll need to prepare for some interface design to tell users that ""Some
+> text written in English"" and ""Some other text written in Spanish"" lines are
+> not in pt.
+
+Why couldn't the TemplateData just be written in the users's language?
+
+> And the format of JSON needs to be modified to include this info.
+
+I don't think that's a good outcome. If there isn't a description in your language (in this case, pt), we shouldn't magically tell you that we've given you a message in a different language (we don't do this for the MW messages framework, for instance).",1374857740,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #6)
+> So I'm not too Wikidata-savvy, but it seems this patch might be useful (if
+> it's
+> not, ignore me and carry on):
+> 
+> https://gerrit.wikimedia.org/r/72867
+> 
+> Right now there is no way to determine the real language of a message from
+> the
+> CDB cache. That patch changes this.
+
+Not really. Labels and descriptions in TemplateData are stored in some JSON blob in a customized format, rather than normal messages.",1374856941,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #5)
+> Fine technically - I think users would be upset and confused.
+
+So you'll need to prepare for some interface design to tell users that ""Some text written in English"" and ""Some other text written in Spanish"" lines are not in pt.
+
+And the format of JSON needs to be modified to include this info. Like:
+
+{
+    ""pages"": {
+        ""1467239"": {
+            ""title"": ""Predefini\u00e7\u00e3o:Refer\u00eancias"",
+            ""description"": {
+                ""pt"": { ""value"": ""Some text written in English"", ""language"": ""en"" }
+            },
+            ""params"": {
+                ""t\u00edtulo"": {
+                    ""label"": {
+                        ""pt"": { ""value"": ""Some other text written in Spanish"", ""language"": ""es"" }
+                    },
+                    ...
+            }
+            ...
+     }
+}",1374856866,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"So I'm not too Wikidata-savvy, but it seems this patch might be useful (if it's not, ignore me and carry on):
+
+https://gerrit.wikimedia.org/r/72867
+
+Right now there is no way to determine the real language of a message from the CDB cache. That patch changes this.",1374856762,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #4)
+> (In reply to comment #2)
+> > API call should ideally specify the fall-back language chain and return just
+> > one set for clients (so the weight is on the server).
+> 
+> Do we care about the real language info of a label.
+
+We don't, but users on multi-lingual wikis will if we send them 1 MiB of descriptions of a template when they only care about 2 KiB worth of the contents. :-)
+
+> That is, is this fine?
+> 
+> {
+>     ""pages"": {
+>         ""1467239"": {
+>             ""title"": ""Predefini\u00e7\u00e3o:Refer\u00eancias"",
+>             ""description"": {
+>                 ""pt"": ""Some text written in English""
+>             },
+>             ""params"": {
+>                 ""t\u00edtulo"": {
+>                     ""label"": {
+>                         ""pt"": ""Some other text written in Spanish""
+>                     },
+>                     ...
+>             }
+>             ...
+>      }
+> }
+
+Fine technically - I think users would be upset and confused.",1374856587,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"(In reply to comment #2)
+> API call should ideally specify the fall-back language chain and return just
+> one set for clients (so the weight is on the server).
+
+Do we care about the real language info of a label.
+
+That is, is this fine?
+
+{
+    ""pages"": {
+        ""1467239"": {
+            ""title"": ""Predefini\u00e7\u00e3o:Refer\u00eancias"",
+            ""description"": {
+                ""pt"": ""Some text written in English""
+            },
+            ""params"": {
+                ""t\u00edtulo"": {
+                    ""label"": {
+                        ""pt"": ""Some other text written in Spanish""
+                    },
+                    ...
+            }
+            ...
+     }
+}",1374856405,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"Falling back to (LanguageConverter)-converted labels is needed too.
+
+It seems my LanguageFallbackChain and related classes (currently in Wikibase) is useful here again.",1374150699,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,API call should ideally specify the fall-back language chain and return just one set for clients (so the weight is on the server).,1372535404,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+TemplateData: Process language fallback and conversion server-side,"For the record, the data returned by the API has all the information, but it is in the ""pt"" properties:
+https://pt.wikipedia.org/w/api.php?format=jsonfm&action=templatedata&titles=Predefini%C3%A7%C3%A3o%3Arefer%C3%AAncias
+E.g.:
+{
+    ""pages"": {
+        ""1467239"": {
+            ""title"": ""Predefini\u00e7\u00e3o:Refer\u00eancias"",
+            ""description"": {
+                ""pt"": ""Produz o t\u00edtulo da se\u00e7\u00e3o de refer\u00eancias e impede que seja edit\u00e1vel""
+            },
+            ""params"": {
+                ""t\u00edtulo"": {
+                    ""label"": {
+                        ""pt"": ""T\u00edtulo da se\u00e7\u00e3o""
+                    },
+                    ...
+            }
+            ...
+     }
+}",1372535216,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-uydrcj3p2rhxycgc65tn,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"VE is missing the red ""semi-protected page"" box seen at
+http://en.wikipedia.org/w/index.php?title=Muscle&action=edit and probably also the equivalent one for administrators on fully protected pages.
+
+They should be displayed as a ""notice"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51215",1372489200,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-ndmy33qu6brquwrr27nw,task_description,resolved
+VisualEditor: Protected page warning messages are missing,This is now fixed in master and we will push to production very soon. Sorry for the inconvenience.,1373497562,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"Change 73022 merged by jenkins-bot:
+Add protected & semiprotected notices to api.
+
+https://gerrit.wikimedia.org/r/73022",1373497150,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"Change 73022 had a related patch set uploaded by Robmoen:
+Add protected & semiprotected notices to api.
+
+https://gerrit.wikimedia.org/r/73022",1373487840,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"(In reply to comment #3)
+> The edit box of a protected page also uses a pick background.  That is
+> missing
+> from VE.
+
+No, this is enwiki's local CSS: [[MediaWiki:Group-sysop.css]] needs to be updated. I will file an edit request.",1372914263,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,The edit box of a protected page also uses a pick background.  That is missing from VE.,1372913884,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"This also applies to things like BLP warnings, mind; non-page-specific warnings generally seem to get cut off.",1372751625,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+VisualEditor: Protected page warning messages are missing,"In sequencing, this should probably be above everything except the not-applicable anon warning (so anon warning > protected > editing old > page notices). Maybe we need a more formal ordering?",1372614070,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ndmy33qu6brquwrr27nw,task_subcomment,NA
+<span> floats out of a table(?),"Possibly related to Bug 49892, VE is inserting random <span> parameters.  
+
+See:
+https://en.wikipedia.org/w/index.php?title=Ruger_P_series&diff=next&oldid=560801075
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372450980,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-fmgdk7zrdnkog3djzdrc,task_description,resolved
+<span> floats out of a table(?),"That diff is from before we deployed the fix in 49892.  And, the oldid html is probably coming from the cache.  So, once cache is purged, this should go away.  Closing this.  Please reopen if still an issue.",1373061530,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fmgdk7zrdnkog3djzdrc,task_subcomment,NA
+<span> floats out of a table(?),"I can reproduce this against current production VisualEditor/Parsoid on that oldid but not the current id. I'm presuming that this is a Parsoid bug, but not sure of the severity.",1373057068,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fmgdk7zrdnkog3djzdrc,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"On a CAPTCHA-triggering edit, VE does not display the CAPTCHA, instead showing an alert:
+
+Error saving data to server: Failed request: error.
+
+Marking critical, because VE is in use by 50% of new users at enwiki, none of whom are now able to add external links for sourcing purposes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372413660,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-lsxohsnqwom7fu46vsrm,task_description,resolved
+VisualEditor: Edits triggering CAPTCHA cannot be saved,[[mw:Thread:Extension talk:VisualEditor/VE and ConfirmEdit]],1395111940,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,This is now fixed in master and will be deployed on Monday.,1372582072,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"Change 71160 merged by jenkins-bot:
+mw: Implement support for ConfirmEdit and FancyCaptcha
+
+https://gerrit.wikimedia.org/r/71160",1372563855,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"Change 71160 had a related patch set uploaded by Krinkle:
+mw: Implement support for ConfirmEdit and FancyCaptcha
+
+https://gerrit.wikimedia.org/r/71160",1372537638,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"Right now the handling of any error results the following alert:
+
+> Error saving data to server: Failed request: {api.result}.
+
+The only variable we use is the result code, not the error code. And though the error code varies (badtoken, hookabort, needcaptcha) the result is always ""error"".
+
+Fortunately (at least) the ConfirmEdit extension, and specifically the FancyCaptcha variant (which Wikimedia uses) does provide an API and exposes the following through the EditPage/ApiEdit/ApiVisualEditor result:
+
+{
+    ""visualeditor"": {
+        ""result"": ""error"",
+        ""edit"": {
+            ""captcha"": {
+                ""type"": ""image"",
+                ""mime"": ""image/png"",
+                ""id"": ""626590462"",
+                ""url"": ""//alpha.wikipedia.krinkle.dev/w/index.php?title=Special:Captcha/image&wpCaptchaId=fa4e388ad7""
+            },
+            ""result"": ""Failure""
+        }
+    }
+}
+
+So it looks like we can use this to build the UI for it.",1372458780,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"This depends on MediaWiki making the CAPTCHAs available through an API, which I believe is currently not done. Timo to comment.",1372450760,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Edits triggering CAPTCHA cannot be saved,"(In reply to comment #0)
+> Error saving data to server: Failed request: error.
+
+The same error is also seen when triggering the spam blacklist.",1372422758,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-lsxohsnqwom7fu46vsrm,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"When attempting an edit that is disallowed by AbuseFilter, you get a browser alert:
+
+Error saving data to server: Unsuccessful request: The modification you tried to make was aborted by an extension hook.
+
+Instead, VE should show a less cryptic message specific to AbuseFilter.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372407600,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-yhjioiu5qdrnau76umcl,task_description,resolved
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,This has now been done and will go out today.,1372703938,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"Change 71293 merged by jenkins-bot:
+mw.ViewPageTarget: Show save errors in save dialog instead of alert
+
+https://gerrit.wikimedia.org/r/71293",1372703904,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"Given that AbuseFilter (but not others) depend on bug 32216, I'm moving that part to a new bug, bug 50472; the rest of this bug will be done today.",1372618721,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"AbuseFilter, wgSpamRegex (core), TitleBlacklist, SpamBlacklist, ..",1372617952,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VisualEditor: Message shown when edits are disallowed by API needs to be clearer,"Change 71293 had a related patch set uploaded by Krinkle:
+(DRAFT) mw.ViewPageTarget: Show unrecoverable/unknown save errors in dialog instead of alert
+
+https://gerrit.wikimedia.org/r/71293",1372617672,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yhjioiu5qdrnau76umcl,task_subcomment,NA
+VE does not support typing in Kannada,"VE's behaviour is not as expected when I invoke my own IME for entering Kannada text. If I press Enter after typing some text, it creates a blank line above the current line rather than below the line. Some conjuncts also get dissociated and show sthe constituent Unicode character instead of the conjuncts. I am using Windows 8 and Firefox (ver 21). I tried using the built-in IME as well as Baraa IME. in both cases I could not use the VE for typing in Kannada.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372403160,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_description,resolved
+VE does not support typing in Kannada,"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!",1377202358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"Change 80080 merged by jenkins-bot:
+Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",1377164912,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"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",1377027669,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"Hi, thanks for your help.
+
+I think the issue may be resolved by the following patch: https://gerrit.wikimedia.org/r/#/c/79451 . Or at least, the problems may be different now. I'm not sure it's working correctly with the ""Kannada inscript (m17n)"" ibus input method on Ubuntu+firefox, but it would be good for a Kannada reader to verify this!",1376936950,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"VE Kannada screen shot after pressing spacebar
+
+**Attached**: {F11104}",1373357251,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"VE Kannada screen shot before pressing spacebar
+
+**Attached**: {F11103}",1373357196,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"(In reply to comment #5)
+> I am not sure if the VE has been improved. But now I am able to type in
+> Kannada
+> if I use the Windows built-in IME as well as the Indic IME2 developed by
+> Microsoft-India. But the Baraha IME is still giving problems. I am waiting
+> for
+> the ULS to be enabled in VE.
+
+This was somewhat prematured comment. When I thoroughly tested I found some bugs in built-in IME as well as Indian IME2 also. It does render properly initially, but when I press space bar, the display gets spoiled. I will add the screeenshots.",1373356552,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,I am not sure if the VE has been improved. But now I am able to type in Kannada if I use the Windows built-in IME as well as the Indic IME2 developed by Microsoft-India. But the Baraha IME is still giving problems. I am waiting for the ULS to be enabled in VE.,1373353002,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,I treid the built-in IME of Windows 8 as well as a thrid party IME called Baraha.,1372417654,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"Thanks for taking the time to report this and testing VE!
+What are the exact steps to reproduce this?
+
+I tried:
+1. Make sure to be logged in on http://kn.wikipedia.org/
+2. Make sure that on http://kn.wikipedia.org/wiki/%E0%B2%B5%E0%B2%BF%E0%B2%B6%E0%B3%87%E0%B2%B7:Preferences?uselang=en#mw-prefsection-editing > ""Beta features >  Enable VisualEditor (only in the main and user namespaces)"" is enabled.
+3. Go to a random article like http://kn.wikipedia.org/wiki/ಔಷಧೀಯ_ರಸಾಯನಶಾಸ್ತ್ರ?veaction=edit
+4. I can confirm that keyboard cursor in on top of text, but I can type (Firefox 18).
+
+5. Click the cog next to ""ಇತರ ಭಾಷೆಗಳು"" (In other languages) and choose ""Input settings"".
+6. ""Input methods for ಕನ್ನಡ"" says ""Use native keyboard"".
+
+So here I have several options.
+
+Could you confirm/correct the above steps, and explain which ""built-in IME"" you exactly tried?",1372414516,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"VE screenshot just after pressing Enter key
+
+**Attached**: {F11102}",1372413796,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+VE does not support typing in Kannada,"VE screenshot just before pressing Enter key
+
+**Attached**: {F11101}",1372413758,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-2qe7sdslfntthznnkcbt,task_subcomment,NA
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears","As Rob spotted, we should (re-)place the cursor in the block.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372384440,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jidkdocy777f7fa4pk3t,task_description,resolved
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears",Merged and will be deployed shortly.,1372706749,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jidkdocy777f7fa4pk3t,task_subcomment,NA
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears","Change 71388 merged by jenkins-bot:
+Restore focus to documentNode on convert
+
+https://gerrit.wikimedia.org/r/71388",1372706703,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jidkdocy777f7fa4pk3t,task_subcomment,NA
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears","Change 71388 had a related patch set uploaded by Robmoen:
+Restore focus to documentNode on convert
+
+https://gerrit.wikimedia.org/r/71388",1372705249,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jidkdocy777f7fa4pk3t,task_subcomment,NA
+"VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears","On a note about this at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Cursor_disappears, I tested - I don't have the issue in Chrome (the cursor remains), but it is evidently still disappearing in Firefox. Just an FYI. :)",1372595247,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-jidkdocy777f7fa4pk3t,task_subcomment,NA
+VisualEditor: Category leaks out of transclusion when round-tripped through VE,"Example diff:
+
+https://en.wikipedia.org/w/index.php?title=FC_Dila_Gori&curid=6581323&diff=561887535&oldid=561367008
+
+Works in Parsoid:
+
+echo '{{commons category}}' | node parse --wt2wt
+{{commons category}}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50120",1372375380,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cc4653x6b7o5qyh3ddoy,task_description,resolved
+VisualEditor: Category leaks out of transclusion when round-tripped through VE,This was fixed by the fix for bug 50120. The DOM produced by the {{commons category}} template is very similar to the persondata template.,1373500548,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cc4653x6b7o5qyh3ddoy,task_subcomment,NA
+VisualEditor: Category leaks out of transclusion when round-tripped through VE,"Looks like a link element that is also encapsulated is not properly handled by VE:
+
+<link rel=""mw:WikiLink/Category"" href=""./Category:Commons_category_without_a_link_on_Wikidata"" data-parsoid='{""stx"":""simple"",""a"":{""href"":""./Category:Commons_category_without_a_link_on_Wikidata""},""sa"":{""href"":""Category:Commons category without a link on Wikidata""}}' about=""#mwt1"">",1373485070,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cc4653x6b7o5qyh3ddoy,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),"Screenshot
+
+Screenshot - FireFox 21.0, Mac OS X 10.6.8
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11044}",1372368720,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-q4tev2wggvrevxlx57l3,task_description,resolved
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),"Yes, this was fixed but the deployment was temporarily rolled-back until ~ 13:40 UTC today.",1372446220,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),Maybe it's fixed but not out yet? http://it.wikipedia.org/wiki/File:Schermata_2013-06-28_alle_15.15.44.png on it.wiki this afternoon.,1372444061,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),*** Bug 50364 has been marked as a duplicate of this bug. ***,1372417299,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),*** Bug 50276 has been marked as a duplicate of this bug. ***,1372387036,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),Fixed and will be going out in the next few minutes.,1372380458,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),"Change 70786 merged by jenkins-bot:
+Fix bug where the floating toolbar was on top of the save dialog
+
+https://gerrit.wikimedia.org/r/70786",1372378996,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down),"Change 70786 had a related patch set uploaded by Jforrester:
+Fix bug where the floating toolbar was on top of the save dialog
+
+https://gerrit.wikimedia.org/r/70786",1372373151,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q4tev2wggvrevxlx57l3,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"The VisualEditor doesn't currently have a mechanism for inserting special characters - while a lot of them are unnecessary (`~~~~` for example), things like en and emdashes can be quite important for content.
+
+**See Also**: {T13130}",1372349160,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_description,resolved
+VisualEditor: Provide a character insertion tool,"(In reply to comment #36)
+> 1: no one knows them/uses them
+
+Well, that disscutalbe, but I tend to think the same. No one knows them, because you dont need to know them for normal sw use.
+
+> So some ideas:
+> 1: Educate the user: Add a 'more characters' link in the insert symbol
+> editor,
+> that detects OS of user and links to a page explaining how to access this
+> panel
+> on his OS.
+
+Why to make it more difficult for users. We want them to attract to Wikipedia and we wont do do the environment as easy as possible. Our goal is not to educate them further things.",1387303644,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Change 90940 merged by jenkins-bot:
+Insert special character tool
+
+https://gerrit.wikimedia.org/r/90940",1386312904,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"""Educating"" the user strikes me as a sign of failure for a supposedly ""easier"" UI. The ""harder"" UI has it right there, after all.",1385650860,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"> Just for reference: Either I didn't read all the comments well enough or nobody
+> quite mentioned the fact that all modern desktop operating environments have a
+> built-in a Character Map tool: Windows (with pretty full Unicode since NT 4),
+> Gnome, KDE, and Mac OSX (called ""Character viewer"").
+
+On Mountain Lion, it's even simpler. (Straight in the edit menu, ctrl-cmd-space).
+
+I mentioned it, but the problem is indeed:
+1: no one knows them/uses them
+2: there is no trigger in HTML5/JS to open the panel
+
+So some ideas:
+1: Educate the user: Add a 'more characters' link in the insert symbol editor, that detects OS of user and links to a page explaining how to access this panel on his OS.
+2: Lobby HTML5 WG to expose these panels to JS",1385650141,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #34)
+> At present, however, there is no way to enter non-keyboard characters unless
+> you're much more familiar with your operating system
+Well, how doest it come, there is no way? What about to load character box available for editing on some wikies in MonoBook?
+
+> At present, however, there is no way to enter non-keyboard characters unless
+> you're much more familiar with your operating system than almost any user is.
+Do you have any statistic for this statment? I would say that most of the users are not familiar with that. But I should include it is my point of view.",1385284629,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Juan - I think that would quite definitely require actual usability lab testing. As would many of the suggestions in this bug.
+
+At present, however, there is no way to enter non-keyboard characters unless you're much more familiar with your operating system than almost any user is. So doing nothing isn't really an option either.",1383688795,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #32)
+> (In reply to comment #31)
+> > Just for reference: Either I didn't read all the comments well enough or
+> > nobody quite mentioned the fact that all modern desktop operating
+> > environments have a built-in a Character Map tool: Windows (with pretty
+> > full Unicode since NT 4), Gnome, KDE, and Mac OSX (called ""Character
+> > viewer"").
+> 
+> I said this, but everyone said it wasn't sufficient for them. :-(
+
+Lets say it differenty. Visual Editor Team was made to remove obstacles in editing, to simplify the work of Wikipedia contributors. Even there are voices, that it is a wrong way and newbies should study wikitext WFM goes the way of its goal. To offer all human knowledge to give to everybody. Our aim here is to collect the knowledge of all people. Logically higher amount of obstacles reduces the number of Wikipedians. Our aim is not to push newbies to study wikitext, internal policies or typography. Our aim is to harvest their knoledge. Thus in the new trend we are removing obstacles. So if not as a default, what about as an option to define your own characters (this was always possible in wp)? Than we can tell newbies, look here we place &ndash; - its not present in VE default, but you can install an extension to your VE.",1383688524,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #31)
+> Just for reference: Either I didn't read all the comments well enough or
+> nobody quite mentioned the fact that all modern desktop operating
+> environments have a built-in a Character Map tool: Windows (with pretty
+> full Unicode since NT 4), Gnome, KDE, and Mac OSX (called ""Character
+> viewer"").
+
+I said this, but everyone said it wasn't sufficient for them. :-(
+
+> 2. It may be easier to insert at least some characters using the keyboard
+> layout provided with ULS. It is disabled now in VE because of some bugs (can
+> anybody help me with the numbers?), but these can be fixed, of course. If we
+> know which characters are really needed (see point 1 above), we can very
+> easily add them to the keyboard layouts.
+
+Possibly. The main problem is that ""ULS"" is about twenty different tools, and some of them don't work in VisualEditor (yet). I doesn't seem possible to enable some of them and not others, however.",1383674338,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Just for reference: Either I didn't read all the comments well enough or nobody quite mentioned the fact that all modern desktop operating environments have a built-in a Character Map tool: Windows (with pretty full Unicode since NT 4), Gnome, KDE, and Mac OSX (called ""Character viewer"").
+
+That said, I am very well aware of the fact that pretty much nobody but me actually uses it. A very surprising number of people, however, do use the character insertion tool in their word processors. The one in Microsoft Word is not very different from Windows' Character Map, which in my mind makes it redundant, but apparently I'm special.
+
+Anyway, yes - a character insertion tool should be there.
+
+But, two points:
+
+1. There's one already in Vector, and it's quite good. It can be used for research - which characters are used most frequently in which project. Adding statistics for this is quite easy now with EventLogging.
+
+2. It may be easier to insert at least some characters using the keyboard layout provided with ULS. It is disabled now in VE because of some bugs (can anybody help me with the numbers?), but these can be fixed, of course. If we know which characters are really needed (see point 1 above), we can very easily add them to the keyboard layouts.",1383663006,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Well, when creating Featured or Quality articles we (on cs.wp) looks to have them correct from typograpical point of wiev. The problem is that Czech keyboard doesnt include all characters needed, as it includes other characters, which are not native to English. The most common missing characters would be *, #, &ndash;, &nbsp;. So if not all it would be nice to have in VE or nearby the table with some most used characters. E.g. list items are present in English keyboard, while &ndash; suprisingly not.",1383640351,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #27)
+> If this selection tool is ever provided, please make sure users have an
+> option not to load it at all (see bug 11130 for this problem in the context
+> of MediaWiki:Edittools)
+
+It's very unlikely that we'll start adding per-user preferences to switch things like this on and off (some VE version of bug 9754); that's a very complex and confusing thing to allow.
+
+Note BTW that bug 11130 is complaining about assuming users have JS (already known inside VE), lack of ability to cache (fixed by VE's nature), and taking up lots of screen estate (fixed by how we'll do this); I don't think it's a direct comparison. I'd also note that bug 11130 hasn't been done despite it being filed 6 years ago, which strongly suggests that it's not a priority.",1383411270,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Change 90940 had a related patch set uploaded by Jforrester:
+[WIP] Insert special character tool
+
+https://gerrit.wikimedia.org/r/90940",1383409609,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"If this selection tool is ever provided, please make sure users have an option not to load it at all (see bug 11130 for this problem in the context of MediaWiki:Edittools)",1383125351,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**eleriygarregwen** wrote:
+
+When I proposed a whole collection of sequences of characters to put into the ULS input method for Welsh, which uses a lot of diacritics, the comment from CYWP was that it would be a lot of work to memorise these character sequences, and it is not easy to find out about the ULS input methods.
+
+The bar of characters under the edit box is very easy to understand, just by looking at it, and having a go. Almost no-one needs a help page on how to use it. Once you know what it does, there is nothing to memorise, and nothing to forget. Since simplicity is the aim with VisualEditor (to encourage new users), the bar of characters wins over anything more complicated, in my opinion.",1383083841,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"I agree with James Forrester's comment #0. Character input in particular languages should be possible, but through the universal language selector, and in all text inputs on the website.
+
+I think the ideal way to handle en dashes and em dashes would be to make ""--"" be replaced by the wikitext parser by an en dash (–), ""---"" by an em dash (—) and ""----"" by an horizontal bar (―). The current horizontal rule syntax would become ""-----"" (it would require one more hyphen-minus because the current one would be taken by the horizontal bar character). There would therefore become part of the syntax. DokuWiki does this for en dashes and em dashes (https://www.dokuwiki.org/wiki:syntax#text_to_html_conversions), but not the others.
+
+As I mentioned, this is what I think would be the ideal way to handle it. Practically, this is impossible because these sequences are already used in many pages for other purposes. An acceptable solution would, I believe, be to make the editor recognize those sequences and replace them automatically by the corresponding character. This would be reasonable in the VisualEditor and would be more efficient than putting a bar of characters under the edit box and hoping beginners will use it to insert dashes. However, since the sequence ""--"" is used in signatures on talk pages and possibly for other things in wikitext, it may be preferable to avoid doing these replacements in the source editor.
+
+It might be a good idea to add sequences of characters for producing similar characters. As long as the sequences are well chosen, problems should not arise frequently, and this could reduce considerably the typographical burden put on beginners.",1382936493,PHID-USER-2rwkb3az6uklfhh5aqw5,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**lebo.beland** wrote:
+
+I didn't read the whole thread,  but I suggest to look at including Mediawiki:Edittools in the Visual Editor. For many projects, this include the special characters and useful stuff specific to each project.
+
+Thanks,",1382929831,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,*** Bug 55496 has been marked as a duplicate of this bug. ***,1381329553,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Czech editors have compiled a list of characters they find are vital for their day-to-day editing. From https://cs.wikipedia.org/wiki/Diskuse_k_Wikipedii:VisualEditor
+
+
+
+Output	Name	                                Entity	Decimal
+ 	nobreak space	                        &nbsp;	&#160;
+ 	thin space	                        &thinsp;	 
+„	curly quotation marks begin (99)	&bdquo;	&#8222;
+“	curly quotation marks end (66)	        &ldquo;	&#8220;
+‚	simple curly quotation marks begin	&sbquo;	&#8218;
+‘	simple curly quotation marks end	&lsquo;	&#8216;
+–	n-dash	                                &ndash;	&#8211;
+×	times	                                &times;	&#215;
+
+In particular, both kinds of quotation marks (we are very particular about those, like the French about theirs) could be insertable either one by one or in pairs, like so: „“ and ‚‘.
+In general, easy access to inserting those characters would be a very desirable feature for Czech editors – and even better would be the MS Word functionality that automatically converts minuses into n-dashes and ""English quotation marks"" into „Czech quotation marks“. Best, Littledogboy (diskuse) 1. 10. 2013, 11:35 (UTC)
+Important: Although I've listed their codes, we usually enter n-dash and curly quotation marks NOT as html entities, but simply like so „–“ (Alt-0132, Alt-0150, Alt-0147 – yes, I am a robot). Littledogboy (diskuse) 1. 10. 2013, 11:51 (UTC)",1380652688,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"The other problem is that with VE having no source mode as yet, I can't even resort to HTML entities.",1380018347,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Further to comment 18 and comment 19 a big use case of the character insertion toolbar is to insert characters one does not frequently use.
+
+Utilities like an external character map are very inefficient because it disrupts the work flow, requires you to find the character you want, and copy and paste the character you need. It also replaces whatever else you had in the clipboard previously that you may still need.
+
+Dead keys are useful only if you know that they exist, know how to set them up (they are not enabled by default on most US and UK systems at least), and know the combinations required to input the character you want. I have a much better memory for things like that than many people, and while I know ones like é, Ŵ, ß, ° and ö, characters like ř, Đ and ố I don't. As far as I know, characters in other scripts like д, ζ, ب ,ש, are not producible using deadkey combinations.
+
+Input methods are a very heavy weight solution to inputting characters not found natively on one's keyboard. They always require setting up in advance for each script (and some script/language combinations I think) and learning how to produce each desired character. I only use this method for IPA because I did a lot of work with pronunciations at Wiktionary and that required learning that to produce /ˌbʌɡˈzɪlə/ I need to type /%bVg""zIl@/ - hardly something we can expect a casual editor to learn.  
+
+One of the primary goals of VisualEditor is to reduce the barrier to contributing to Wikimedia projects, not having a character insertion tool is rather contradictory to this.",1380018097,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"I need to point out the irony of developing an editing interface with the good faith but technically challenged user in mind, and then expecting them to know how to use their browser/operating system to insert an emdash (a character not present on the standard English keyboard, but used over a million times on English Wikipedia). Given the target group for this extension, this isn't a low-priority enhancement, it is core functionality. In fact, the existing editorial base uses the edit tools almost exclusively over their browser/operating system, and I suspect many of them (including me) have no idea how to do use the latter.",1379917317,PHID-USER-yif6nz5uhka5cnltixpc,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Yep. When you need to add an accented character, you need to add an accented character. This is a quite definitely missing facility.",1379690527,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Another request today for [[MediaWiki:Edittools]] or an equivalent to be available in VE.
+
+I second comment 8 and comment 10 - this is one of the features of the source editor that editors really miss.",1379686473,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Sorry Lloffiwr, my bad: I thought that Welshp WP had somehow made that set of characters already available with VisualEditor as well.",1377688397,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**eleriygarregwen** wrote:
+
+""Lloffiwr, can you link to this workaround?"" - Sorry I don't know what you are asking me to do.
+
+With regard to using our own edit tools, that would be very good. It is very simple to just click on one of a number of characters sitting on a toolbar right next to the editor. You don't have to remember key combinations, there is no need to look up a help page and learn how to insert characters. The character toolbar's purpose in the normal editor is obvious and it is ready to use for all users (you don't have to enable a special keyboard as you would with the ULS).
+
+By the way, in the ""save"" dialog of the VisualEditor on CYWP, we see an image of our short character toolbar, but have no way of actually using it! I, an experienced editor, was very confused by this; the new editors for whom this tool is designed are likely to be completely floored by it.",1377641765,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Lloffiwr, can you link to this workaround? I tried enabling VE on your wiki but that was not enough, should I also enable some gadget maybe? 
+James, until this or other IME issues are not solved, isn't there a way to let these wikis use their very own edit tools, i.e. http://pms.wikipedia.org/wiki/MediaWiki:Edittools ?",1377258190,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**eleriygarregwen** wrote:
+
+To make life easy on the Welsh Wikipedia, we have added a short character set consisting only of the most commonly used special characters immediately below the edit window. We have also added a more comprehensive set of special characters further down below the edit window. I think it would be useful to add the full character set to VisualEditor as standard, but also to allow each Wikipedia to add its own special character set via an optional message.",1375136279,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,This is among the most important missing features for dewp.,1375019373,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"**eleriygarregwen** wrote:
+
+Another example of a language whose users make heavy use of the character insertion tool underneath the old edit window is Welsh (cy). Some of us work with keyboards which have been specially adapted to easily type the diacritics needed (including ŵ and ŷ) but not all hardware devices have this software loaded. This means that the VisualEditor is very difficult to use for some users, making training sessions for new users (some with, some without the diacritics software) difficult to conduct using VisualEditor.",1374356830,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Agreed with comment 8. The special characters insertion tool in WikiEditor is very convenient when editing articles about topics that involve other scripts or diacritics. Not providing such a tool in VisualEditor would seriously reduce VE's usefulness, and would certainly provide a compelling reason to use the source editor much more often than otherwise necessary.",1374264181,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"BTW, if we ever do get another symbol picker, please make it share it's table with WikiEditor, limiting the places where we need to maintain these chars. (We already have 3 [WikiEditor extension, MediaWiki:Edittools, MediaWiki:Edittools.js])",1374264087,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"""Character insertion is, in general, the responsibility of your browser/operating system""
+
+Yes and no. Yes, your computer is capable of inserting loads of characters. No, it is not always reachable.
+
+At least, I know of no operating system + browser combination, where I can put my cursor in a text area and bring up a symbol picker from the menu or a toolbar. (Unlike spellchecking).",1374263950,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,*** Bug 51120 has been marked as a duplicate of this bug. ***,1374263430,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"http://en.wikipedia.org/wiki/File:VE_modified_ui_suggestion.png shows one user's suggestion.  
+
+See http://en.wikipedia.org/w/index.php?oldid=564286664#Thoughts_about_UI_improvements for the discussion.",1373843965,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"There was a similar request on Portuguese Wikipedia[1]. A user wanted to use the kind of tool we see in the screenshot [2].
+
+
+[1] https://pt.wikipedia.org/wiki/WP:Editor_Visual/Coment%C3%A1rios?oldid=36280987&uselang=en#Adi.C3.A7.C3.A3o_de_caracteres_especial_no_Visual_editor
+[2] http://postimg.org/image/mwbyn96gn/",1372773901,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,Nonbreaking spaces would be helpful as well.,1372736869,PHID-USER-jdkjcyuluyy456zxyufo,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,We've had another comment re: emdashes here:http://en.wikipedia.org/w/index.php?title=Wikipedia_talk:VisualEditor&curid=37920680&diff=562488469&oldid=562482174,1372735991,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"Well, I'm sat on my windows machine here and can't see any way to type an emdash, for example :/",1372356235,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Provide a character insertion tool,"(In reply to comment #0)
+> The VisualEditor doesn't currently have a mechanism for inserting special
+> characters - while a lot of them are unnecessary (~~~~ for example), things
+> like en and emdashes can be quite important for content.
+
+Character insertion is, in general, the responsibility of your browser/operating system (same as spell check, IME and other general editing tools). Where your local OS fails, we have a 'standard' of providing general tools to let you get OS-level tools (most notably, ULS), rather than one-off ""insert a bunch of random characters"" micro-tools.
+
+MediaWiki has given people tools to insert random characters primarily because they do special things, and we've given up on users being able to magically know them (like ~~~~ or {{DEFAULTSORT:}}). They're all examples of system design failure. The fact that we have extended the metaphor to give ""helpful"" characters that users can trivially type themselves isn't a great reason to create it from scratch.
+
+I'm not dead-set against this, but it feels like a clunky failure. :-(",1372355885,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dawylrxmkjvn5rn6pdtf,task_subcomment,NA
+VisualEditor: Backspace at the beginning of a line before an image inserts the succeeding text as a thumbnail caption,"Screenshot
+
+See the screenshot; before and after the backspace, respectively.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51624
+
+**Attached**: {F11902}",1372341120,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-kum7spdwx5xdoe73t4u5,task_description,resolved
+VisualEditor: Backspace at the beginning of a line before an image inserts the succeeding text as a thumbnail caption,This was fixed months ago; sorry for not spotting this bug report until now.,1384944160,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kum7spdwx5xdoe73t4u5,task_subcomment,NA
+VisualEditor: Backspace at the beginning of a line before an image inserts the succeeding text as a thumbnail caption,This is the same issue as Bug 51624 that was originally reported as happening with table cells and then extended to include image captions. I'm not sure which should me marked as duplicate of the other,1374599258,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-kum7spdwx5xdoe73t4u5,task_subcomment,NA
+VisualEditor: Template/Image node shields should not not appear on top of the toolbar,"Screenshot
+
+See screenshot. The template inspector overlaps not only the document (that would be good - see 50241) - but the toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11898}",1372339980,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-7u4x4gvkmazindkefefh,task_description,resolved
+VisualEditor: Template/Image node shields should not not appear on top of the toolbar,This would have been fixed this time last week with the general z-index re-write; sorry for only getting to this now.,1373519669,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7u4x4gvkmazindkefefh,task_subcomment,NA
+VisualEditor: Template/Image node shields should not not appear on top of the toolbar,Another complaint about this - the editor was using Google Chrome 28.0.1500.63 on Ubuntu 13.04.,1372793827,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-7u4x4gvkmazindkefefh,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","Not sure if this should be filed under VisualEditor or Translate.
+
+When clicking the ""edit source"" button on a translation or a page that uses the Translate extension, it isn't possible to edit the wikitext directly; instead, the user is told to use the Translate extension to change the content.
+
+When clicking the ""edit"" button on a translation of a page that uses the Translate extension, it's possible to edit the text with VisualEditor. At first, I thought this was a feature, and that changes would be propagated to the Translate extension, until I tried to save the page and got the following error:
+
+Error saving data to server: Unsuccessful request: Unknown error: ""tpt-target-page"".
+
+If VisualEditor can't be used to edit those pages, it probably shouldn't lead users to believe it can :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48891
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61218",1372338540,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_description,resolved
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","Change 119427 merged by jenkins-bot:
+Disable VisualEditor on Page Translation output pages
+
+https://gerrit.wikimedia.org/r/119427",1395268059,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","Change 119427 had a related patch set uploaded by Jforrester:
+Disable VisualEditor on Page Translation output pages
+
+https://gerrit.wikimedia.org/r/119427",1395190355,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","(In reply to comment #9)
+> I just VEdited a page on mw.org (Communication) and it seemed to work (beyond
+> the translate tags showing up).
+
+Nope, the error happens when you try to edit a translation, not the source page :) e.g. try to edit Communication/it",1380618535,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",I just VEdited a page on mw.org (Communication) and it seemed to work (beyond the translate tags showing up).,1380277979,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",I assume VE checks whether the page is editable somewhere? I wonder if changing the hook in Translate from getUserPermissionsErrorsExpensive to getUserPermissionsErrors would solve this? Would have to make sure that the hook is efficient then.,1374942941,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","Presumably there is a simple check we can do for whether the page is under the protection of the Translate extension, so we can do
+
+if (
+  …
+  if <Translate extension installed> && !<page is Translate-protected>
+  …
+) { <do not load> }
+
+… in the code in ViewPageTarget init?",1374858968,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",*** Bug 51805 has been marked as a duplicate of this bug. ***,1374854170,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",*** Bug 51931 has been marked as a duplicate of this bug. ***,1374703814,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","e.g.
+https://www.mediawiki.org/wiki/Communication/hu?veaction=edit",1374310653,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",%%%*** Bug 51534 has been marked as a duplicate of this bug. ***%%%,1374071458,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly","I tested this on mediawiki.org following a report on the English Wikipedia, but instead of getting an error VisualEditor just silently refused to save the page - the progress bar appeared for a typical amount of time then I was back to the save dialog as if I hadn't pressed save. Lather, rinse, repeat.",1374003370,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+"VisualEditor: Disable veaction=edit on translation pages, which are not editable directly",Just a note to say that this keeps happening. Thanks!,1373956496,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-orgyqstlg3e7bpbpnpc5,task_subcomment,NA
+VisualEditor: VE eats away the end of </ref>}} templates,"It has happened to me several times that after a simple edition VisualEditor or Parsoid breaks the ""</ref>}}"" at the end of a reference template. I still don't know which is the pattern, but at least this time I realized it:
+
+http://ca.wikipedia.org/w/index.php?title=El_Chornaler&diff=11962426&oldid=11962407
+
+Other times a second editor had to come after me fixing the broken template. In the preview before saving everything looks fine.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372313340,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-oqhko7t4wfln3rpauqc5,task_description,resolved
+VisualEditor: VE eats away the end of </ref>}} templates,I can't reproduce it either. Let's say it's fixed.,1375941682,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-oqhko7t4wfln3rpauqc5,task_subcomment,NA
+VisualEditor: VE eats away the end of </ref>}} templates,I can't now reproduce this - is it still occurring?,1375486975,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oqhko7t4wfln3rpauqc5,task_subcomment,NA
+extension Campaigns (and some others?) not current,"http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version shows extension Campaigns not updated since 12 June, but should be current as of https://gerrit.wikimedia.org/r/#/c/69841/ at least.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372283340,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-erpehiwtm4uj5znmo2et,task_description,resolved
+extension Campaigns (and some others?) not current,"(In reply to comment #4)
+Yes. I made a trivial update to Campaigns, and after merging to master it was on http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version within minutes.",1372377246,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+extension Campaigns (and some others?) not current,Well Campaigns is still broken right now.  I guess it will be up to date whenever a commit is merged in that repository,1372350405,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+extension Campaigns (and some others?) not current,"A bunch of them were broken.
+
+Fixed in https://gerrit.wikimedia.org/r/#/c/70834/.",1372349281,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+extension Campaigns (and some others?) not current,And see bug 49846 mediawiki/extensions.git does not update VisualEditor,1372348373,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+extension Campaigns (and some others?) not current,I guess it is misconfigured on Gerrit side (see bug 49906).,1372348270,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-erpehiwtm4uj5znmo2et,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"if an article starts with 
+==Foo==
+Bar Baz Fizz Buzz
+
+It is impossible to remove ==Foo== without having the paragraph take on the h2 markup
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372276980,PHID-USER-n27daagbl3wqf3ghr4nk,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_description,resolved
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"**Wikifram** wrote:
+
+(ec) Yeah, I'm a bit frustrated by the number of errors in that status update, and the apparent lack of possibilities to correct these (even as an addendum or some such) and lack of care about this among the people responsible for this. Not your fault though. Thanks for filing that bug.",1380880306,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,Filed as bug 54964,1380880152,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"Steady on, they're similar bugs and easy to confuse.
+
+The case you describe at the end does sound like a separate bug.",1380879819,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"**Wikifram** wrote:
+
+(In reply to comment #10)
+> You're confusing this with bug 50100.
+
+Not my mistake though, this was reported like this in the VisualEditor weekly update - 2013-09-26 (MW 1.22wmf19) by Jdforrester:
+
+""Blanking the contents of a heading, pre-formatted block or other formatting block now deletes the block rather than leaving it empty, which is consistent with how OpenOffice and Google Docs behave (bug 50254)."" 
+
+I noted that what the VE status report describes is ''not'' fixed, and followed the link number given in the VE status report. If this bug is about something else than what the VE status report described, then this is just one more in the already long list of things wrong with that status report (for which it is apparently ""impossible"" to write an update or correction in any way, shape or form). 
+
+Anyway, you still get the behaviour as described: Go to the first word you want to keep (after the initial header), and use backspace to remove the header: your next paragraph now becomes the header. Only when you first empty the header (leaving the line beneath it), and then go to the text and use backspace, is it possible to remove a starting header without converting the following text into a header. I wouldn't call this ""solved"", perhaps ""somewhat improved"" assuming that the latter possibility / workaround didn't work in the past. (I note that you only go to the start of the heading, and then select ""downwards"" instead of ""sideways""; deleting the header like this works as well)
+
+Note also that if yu eventually get rid of that header, it seems to be impossible to remove a first empty line from an article: [https://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=575703425&oldid=575703070]. Probably needs a different bug (or already exists), but not really optimal either.",1380878361,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,You're confusing this with bug 50100.,1380876577,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"**Wikifram** wrote:
+
+Nice that this is solved, except that it isn't. I had already noted that at MediaWiki, it still blanks the header (but doesn't add nowiki). Tested today at enwiki, and sadly, even worse, again a nowiki was added inside the header instead of removing the empty header: [https://en.wikipedia.org/w/index.php?title=Robbers_Cave_State_Park&diff=575691345&oldid=558376701]
+
+Has this patch ever worked anywhere? Diff?",1380869071,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"Change 85673 merged by jenkins-bot:
+Delete empty nodes instead of merging into them
+
+https://gerrit.wikimedia.org/r/85673",1380047332,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,The delete-when-empty-merge-otherwise behaviour implemented by the patch above is also used by OO/LO & Google docs.,1379946372,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"Change 85673 had a related patch set uploaded by Esanders:
+Delete empty nodes instead of merging into them
+
+https://gerrit.wikimedia.org/r/85673",1379946235,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,This is a separate issue to bug 51829 (now bug 50100).,1379946203,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"It happens to me always, even if the heading is in the middle of the page.",1374826649,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"They definitely seem related, with the distinction that this but has the problem that there is no slug (am I using the lingo right) on the line above the first header if the header is the first element of the page. Merge however you feel is most useful.",1374524826,PHID-USER-n27daagbl3wqf3ghr4nk,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"Actually, this bug looks to be a subset of Bug 51829 is this best merged or that bug better split?",1374518185,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page,"As a workaround, it is possible to convert the header to paragraph text and then delete it. That is no better though than deleting and then converting the changed text back to a paragraph.",1374517963,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-d6skq2oyzzqzdxdbdskt,task_subcomment,NA
+VisualEditor: Yet another dirty-DOM on basic templates,"Link shows a diff made post-deploy doing (what happened to be white-space only) normalisation in two templates (that weren't touched). :-(
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=Pgeezy&curid=38061582&diff=561709972&oldid=561568473",1372274040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hjnunyjomlrvhkq4oiqo,task_description,resolved
+VisualEditor: Yet another dirty-DOM on basic templates,After today's deployment this now appears to have been fixed. Marking as such.,1373518136,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hjnunyjomlrvhkq4oiqo,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"I want to get rid of jobs on the master instance and have them all on slaves.  Master is currently gallium.wikimedia.org which also have a slave installed on it and named 'gallium'.
+
+This is a tracking bug.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1372254540,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vvu5ucedidqohifits2s,task_description,resolved
+Jenkins: migrate all jobs from master to slaves,[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343629,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,Marked master has being down.  People should use the 'gallium' slave to tie jobs to that server or they could use a label.,1373287838,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://integration.wikimedia.org/ci/computer/(master)/
+
+Master (the master Jenkins node)
+Projects tied to master
+None
+
+\O/
+
+I guess we can now remove master as an executor.",1373031852,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,Reduced number of executor on master from 4 to 2.  There are only the qunit jobs left there (bug 50231).,1372425380,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://gerrit.wikimedia.org/r/71006 migrated the wikibase jobs:
+
+mwext-Wikibase-client-tests
+mwext-Wikibase-repo-tests",1372422296,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://gerrit.wikimedia.org/r/#/c/71000/ migrates mediawiki regression jobs
+
+mediawiki-core-regression-REL1_19
+mediawiki-core-regression-REL1_20
+mediawiki-core-regression-REL1_21
+mediawiki-core-regression-master",1372415240,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://gerrit.wikimedia.org/r/#/c/70999/ migrates some doc jobs:
+
+
+mediawiki-core-doxygen-publish
+mediawiki-core-jsduck-publish
+mwext-VisualEditor-doc-publish
+operations-puppet-doc (bug 50233)",1372413785,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,"https://gerrit.wikimedia.org/r/#/c/70917/ updated jobs:
+
+mediawiki-core-phpunit-api
+mediawiki-core-phpunit-databaseless
+mediawiki-core-phpunit-misc
+mediawiki-core-phpunit-parser",1372366694,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+Jenkins: migrate all jobs from master to slaves,List of tied jobs is available at https://integration.wikimedia.org/ci/computer/(master)/  That list needs to shrink to 0 elements.,1372254654,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vvu5ucedidqohifits2s,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","e.g. ""menuitem"" for options in our select widgets.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372205340,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u2ls26f436dp4ls4xqnj,task_description,resolved
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate",Looks fine from my POV.,1406079764,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","Anything left to do here, Timo/James?",1406066234,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","Change 148253 merged by jenkins-bot:
+Add role attribute to a few widgets
+
+https://gerrit.wikimedia.org/r/148253",1406065761,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","Change 148253 had a related patch set uploaded by Alex Monk:
+Add role attribute to a few widgets
+
+https://gerrit.wikimedia.org/r/148253",1405981742,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+"VisualEditor: Add ""role"" attributes to UI elements where appropriate","Most of this has already been done in OOUI, I think.",1405702134,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u2ls26f436dp4ls4xqnj,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"**Author:** `swalling`
+
+**Description:**
+This tour step should only be shown in read mode.
+
+When starting the guided tour via the ""Show help"" help button with GettingStarted, guided tours thinks I am in read mode and displays broken steps, rather than skipping to the appropriate editing steps.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11708}",1372184520,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-x646ub2izdkijgiiwrz2,task_description,resolved
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"Change 72682 merged by jenkins-bot:
+Add tour for VisualEditor
+
+https://gerrit.wikimedia.org/r/72682",1374178920,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"Change 72677 merged by Ori.livneh:
+Add support for VisualEditor
+
+https://gerrit.wikimedia.org/r/72677",1374165359,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"**swalling** wrote:
+
+(In reply to comment #5)
+> I fixed the issue where step 1 was shown when clicked ""Show help"" while in VE
+> editor, on a page with an ambox.  That's on toro for testing.
+
+Tested and working for me on toro. Once the patches are merged I think we can call this one fixed.",1374017584,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"I fixed the issue where step 1 was shown when clicked ""Show help"" while in VE editor, on a page with an ambox.  That's on toro for testing.",1373361751,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"This should be fixed by https://gerrit.wikimedia.org/r/#/c/72677/ and https://gerrit.wikimedia.org/r/#/c/72682/, pending review.",1373340182,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"Change 72682 had a related patch set uploaded by Mattflaschen:
+Add tour for VisualEditor
+
+https://gerrit.wikimedia.org/r/72682",1373340111,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"Change 72677 had a related patch set uploaded by Mattflaschen:
+Add support for VisualEditor.
+
+https://gerrit.wikimedia.org/r/72677",1373339962,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+Guided tours cannot distinguish between read and edit modes with VisualEditor,"**swalling** wrote:
+
+Note: this only happens if the user clicks ""Show help"" after editing in VE mode. Otherwise, the tour progresses normally. The easiest solution in the interim may be to ensure that we don't show the Getting Started toolbar in VE edit mode, like we do for wikitext editing.",1372184775,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-x646ub2izdkijgiiwrz2,task_subcomment,NA
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"**Author:** `p.selitskas`
+
+**Description:**
+Dash-to-underscore conversion is frucked up yet again?
+
+When ""Edit"" is clicked, an API request is issued with params:
+action:visualeditor
+paction:parse
+page:Новая_зямля
+oldid:1630719
+token:[screened]
+format:json
+
+Response: {""servedby"":""mw1141"",""error"":{""code"":""parsoidserver-http-bad-status"",""info"":""404""}}
+
+VE works at be.wikipedia.org, but it doesn't work at be-x-old.wikipedia.org, bat-smg.wikipedia.org, and maybe other sites with dash in the site ID.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372164300,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lfvhcf2i2gcieggk662j,task_description,resolved
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"**p.selitskas** wrote:
+
+(In reply to comment #3)
+> I have fixed this in the Parsoid config.
+
+Can you publish the link to the change in Gerrit (if it is publicly available), just for my interest?
+
+Thanks for fixing, btw.",1372287816,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lfvhcf2i2gcieggk662j,task_subcomment,NA
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"(In reply to comment #2)
+> (In reply to comment #1)
+> > Roan - is this a config issue at our end or something else?
+> > 
+> > http://titanium.wikimedia.org/be-x-oldwiki/Галоўная_старонка?oldid=1535753
+> > and
+> > http://parsoid.wmflabs.org/be-x-old/Галоўная_старонка?oldid=1535753 both work
+> > fine for me, but in VE
+> > https://be-x-old.wikipedia.org/wiki/
+> > Галоўная_старонка?oldid=1535753&veaction=edit
+> > does indeed 404.
+> 
+> I think it's a config issue.
+> 
+> CommonSettings.php on line 1890 says:
+> $wgVisualEditorParsoidPrefix = $wgDBname;
+> 
+> DB names are written with underscores instead of dashes. Conversion '_'->'-'
+> should be performed here.
+> 
+Turns out we did actually have the DB names mapped correctly, but to the wrong URLs. We had stuff like:
+
+'map_bmswiki': 'http://map_bms.wikipedia.org/w/api.php',
+
+which is wrong, we need URLs with dashes.
+
+I have fixed this in the Parsoid config.",1372215518,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lfvhcf2i2gcieggk662j,task_subcomment,NA
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"**p.selitskas** wrote:
+
+(In reply to comment #1)
+> Roan - is this a config issue at our end or something else?
+> 
+> http://titanium.wikimedia.org/be-x-oldwiki/Галоўная_старонка?oldid=1535753
+> and
+> http://parsoid.wmflabs.org/be-x-old/Галоўная_старонка?oldid=1535753 both work
+> fine for me, but in VE
+> https://be-x-old.wikipedia.org/wiki/
+> Галоўная_старонка?oldid=1535753&veaction=edit
+> does indeed 404.
+
+I think it's a config issue.
+
+CommonSettings.php on line 1890 says:
+$wgVisualEditorParsoidPrefix = $wgDBname;
+
+DB names are written with underscores instead of dashes. Conversion '_'->'-' should be performed here.
+
+This is a typical error in WMF configs. I used to run against it even in MediaWiki core.",1372179812,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lfvhcf2i2gcieggk662j,task_subcomment,NA
+VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404),"Roan - is this a config issue at our end or something else?
+
+http://titanium.wikimedia.org/be-x-oldwiki/Галоўная_старонка?oldid=1535753 and http://parsoid.wmflabs.org/be-x-old/Галоўная_старонка?oldid=1535753 both work fine for me, but in VE https://be-x-old.wikipedia.org/wiki/Галоўная_старонка?oldid=1535753&veaction=edit does indeed 404.",1372172991,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lfvhcf2i2gcieggk662j,task_subcomment,NA
+"VisualEditor: Attempting to de-bold a selection causes text to become ""extra-bold""","1. Edit [[mw:VisualEditor:Sfioj]] in VE
+2. Make a selection such as
+
+     These [words are] very bold
+or 
+     These wor[ds are ve]ry bold
+
+3. Click the ""Bold"" button on the toolbar
+
+The selected text goes extra-bold, in Firefox 21. 
+
+I should mention that in my case, the font is Arial, which has an extra bold ""Arial-Black"" variant.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372162080,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-j223oppi3t252tmumwbg,task_description,resolved
+"VisualEditor: Attempting to de-bold a selection causes text to become ""extra-bold""",*** Bug 52189 has been marked as a duplicate of this bug. ***,1385398575,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j223oppi3t252tmumwbg,task_subcomment,NA
+"VisualEditor: Attempting to de-bold a selection causes text to become ""extra-bold""",Patched and merged: https://gerrit.wikimedia.org/r/#/c/70434/,1372190547,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-j223oppi3t252tmumwbg,task_subcomment,NA
+"VisualEditor: Attempting to de-bold a selection causes text to become ""extra-bold""","There is a related problem with italic: try the same STR on the second line of the Sfoij page, using the ""italic"" toolbar button instead of ""bold"". But I think it is the same issue.",1372162241,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-j223oppi3t252tmumwbg,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,"Groups of consecutive images are alienated under certain circumstances. 
+
+It might have something to do with the wikilinks in the image caption, however I really just have to throw you some testcases:
+
+---
+(1) Works fine:
+http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493135&veaction=edit
+
+(2) Similar, but doesn't work:
+http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493351&veaction=edit
+
+(3) All three groups uneditable, even the group that is identical to (1) above:
+http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493252&veaction=edit
+
+(4) One group fine, the other alienated:
+http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493194&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372155360,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cohcqit7cjc474qs3bul,task_description,resolved
+VisualEditor: Groups of images are alienated under certain circumstances,See bug 51039.,1373422404,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,"(In reply to comment #3)
+> (In reply to comment #1)
+> > Do they work for you too?
+> 
+> Sorry, yes the testcases do all work now.
+
+Yay. Marking as fixed. :-)",1372298506,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,"(In reply to comment #1)
+> Do they work for you too?
+
+Sorry, yes the testcases do all work now.",1372225473,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,Could you check [[History of Delta Air Lines#1960s_and_1970s]]?,1372225448,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: Groups of images are alienated under certain circumstances,"(In reply to comment #0)
+> Groups of consecutive images are alienated under certain circumstances. 
+> 
+> It might have something to do with the wikilinks in the image caption,
+> however
+> I really just have to throw you some testcases:
+> 
+> ---
+> (1) Works fine:
+> http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/
+> sandbox/VE2&oldid=561493135&veaction=edit
+> 
+> (2) Similar, but doesn't work:
+> http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/
+> sandbox/VE2&oldid=561493351&veaction=edit
+> 
+> (3) All three groups uneditable, even the group that is identical to (1)
+> above:
+> http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/
+> sandbox/VE2&oldid=561493252&veaction=edit
+> 
+> (4) One group fine, the other alienated:
+> http://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/
+> sandbox/VE2&oldid=561493194&veaction=edit
+
+These now all work for me - we've updated Parsoid (and purged the cached versions to avoid corruption from old things), which is (I think) the cause of these issues. Do they work for you too?",1372221560,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cohcqit7cjc474qs3bul,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"http://it.wikipedia.org/wiki/Utente:Syrio/Bozzoli, we tried changing the author's name in ref.6 to ""abbé Paul Guérin"". VE allows editing it, but after clicking twice on Apply Changes, the former name is still displayed and the page can not be saved as the button does not work. (Also, it does not allow us to re-try immediately or to edit other references, you need to reload the page for that). So I did a dummy edit to plain text, and I was allowed to save then, but the result http://it.wikipedia.org/w/index.php?title=Utente%3ASyrio%2FBozzoli&diff=59659908&oldid=59651683 has nothing to do with poor abbé Guérin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372150800,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-jgkllstpxv33sn72mt5f,task_description,resolved
+VisualEditor: VE won't let user save after editing a reference,"(In reply to comment #4)
+> You are right, it works now. Can this be due to people adding TemplateData to
+> that template?
+
+It's possible that TemplateData would mean that it was difficult to edit, yes; sorry. :-(
+
+> Since we're here, I attached the screenshot of what happens when
+> you try and edit it with Vector. You need to reach and click the light blue
+> bar in order to change something in that line. It works, though.
+
+Argh, yes, that's bug 49818 which I thought we had fixed; is this problem still happnening for you? :-(",1373417844,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"(Sorry, that was meant to be ""with Vector on Chrome"", it's ok on FF).",1373308926,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"You are right, it works now. Can this be due to people adding TemplateData to that template? Since we're here, I attached the screenshot of what happens when you try and edit it with Vector. You need to reach and click the light blue bar in order to change something in that line. It works, though.",1373308703,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"Created attachment 12788
+Reference editing window
+
+**Attached**: {F11670}",1373308463,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"[Sorry, can't check before tomorrow. Thanks.]",1373229247,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: VE won't let user save after editing a reference,"[Sorry for being so late in replying to this bug!]
+
+Can this still be reproduced? If so, in what browser? I can edit the reference fine in Firefox and Chrome.
+
+(When you edit a reference, VisualEditor goes off and asks for the reference list to be re-created; temporarily, while that is happening, the original form remains shown in the reference list. However, this behaviour should be very quick, and should not prevent the user from editing.)",1373162537,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jgkllstpxv33sn72mt5f,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"Screenshot
+
+Image dialog shows thumbnails twice, see screenshots.
+
+Maybe 1 from local wiki and 1 from Commons, which are most of the times identical?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11660}",1372146180,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_description,resolved
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),This was fixed and deployed on Thursday.,1373763691,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"Change 73190 merged by jenkins-bot:
+Normalize image titles in cache to prevent duplicates.
+
+https://gerrit.wikimedia.org/r/73190",1373578658,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"Change 73190 had a related patch set uploaded by Robmoen:
+Normalize image titles in cache to prevent duplicates.
+
+https://gerrit.wikimedia.org/r/73190",1373562735,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),^^ You are correct.  this is happening because we are getting results from both namespaces.  File and Fichier in this case.,1373499189,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"(In reply to comment #2)
+> I can't reproduce this in Forefix 21.
+
+Oh, sorry, I see you were on frwiki. This doesn't happen on enwiki or mediawikiwiki, but I can reproduce it on frwiki and dewiki.
+
+Perhaps VE doesn't know about localised names for the ""File"" namespace. That's just a guess.",1372153753,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),I can't reproduce this in Forefix 21.,1372153025,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?),"Created attachment 12632
+Screenshot
+
+**Attached**: {F11661}",1372146249,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-43bme3ubhjcp6xf3kyaw,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,"**Author:** `brassratgirl`
+
+**Description:**
+See this diff: 
+https://en.wikipedia.org/w/index.php?title=Uganda&diff=561452947&oldid=560332103
+
+adding a sentence to the lede section saved properly, but also had unwanted behavior of cutting off the first letter of the first word of a random paragraph in a later section (removed 'l' from ""Lake Kyoga"" under 'geography'). 
+
+Firefox 21.0 on Ubuntu 12.04.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372128420,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z4n2utsm2obyfevr5eud,task_description,resolved
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,I believe we have now fixed this; please re-open if it recurs.,1373056082,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,Can't reproduce in master yet.,1372175257,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,"**brassratgirl** wrote:
+
+Tried editing another, later section in the same article and got this: 
+https://en.wikipedia.org/w/index.php?title=Uganda&diff=561456536&oldid=561456189
+
+the changes I intended to make were made (added a link, copyediting) but spaces around template dates were added (more normalization) and the same initial letter (the 'l' of lake) and bracket from the same image file were removed. VisEd *really* doesn't like something about that paragraph!",1372130068,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,"(In reply to comment #1)
+> Also added some quotes to refnames
+
+That's ""just"" normalisation, which we can fix (by making sure that what we send Parsoid is exactly the same, so it leaves it alone); see bug 50071.
+
+> and removed a bracket from an image link later on.
+
+Yeah, this is very not good, and really hard to understand how it happens. Roan, thoughts?",1372129295,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Editing leads to some characters (of wikitext) cut off in later section,"**brassratgirl** wrote:
+
+Also added some quotes to refnames and removed a bracket from an image link later on.",1372128699,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z4n2utsm2obyfevr5eud,task_subcomment,NA
+VisualEditor: Indentation toolbar buttons should not be enabled by default,"They're currently enabled on page load. Even when dismissing the notice and clicking around in the first paragraph it stays.
+
+It finally disables itself after a node change (e.g. click the second paragraph and then back).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44083",1372115880,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_description,resolved
+VisualEditor: Indentation toolbar buttons should not be enabled by default,This has been fixed and will be deployed very soon.,1372381096,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_subcomment,NA
+VisualEditor: Indentation toolbar buttons should not be enabled by default,"Change 70936 merged by jenkins-bot:
+Init surface after toolbar is setup vs. before.
+
+https://gerrit.wikimedia.org/r/70936",1372375419,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_subcomment,NA
+VisualEditor: Indentation toolbar buttons should not be enabled by default,"Change 70936 had a related patch set uploaded by Robmoen:
+Init surface after toolbar is setup vs. before.
+
+https://gerrit.wikimedia.org/r/70936",1372375072,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_subcomment,NA
+VisualEditor: Indentation toolbar buttons should not be enabled by default,"From conversation earlier today:
+
+It may be possible to hack the button to be disabled by default, but that would introduce the opposite bug where the indention tool would be disabled instead of enabled in a document that starts with a list, requiring the user to move out of the list and back in to be able to indent.
+
+Basically we should make sure that our hooks that make the button enabled/disabled on node focus change also trigger when initially focussing the first node in the document (instead of only from the second node focus onwards).",1372143779,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h7bfc7jy5zuiok7zj7zv,task_subcomment,NA
+VisualEditor: Doing anything in a slug after an internal node throws an error,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372109460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tbvrdwvxvbqqobem3szn,task_description,resolved
+VisualEditor: Doing anything in a slug after an internal node throws an error,This should now be fixed.,1372113370,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tbvrdwvxvbqqobem3szn,task_subcomment,NA
+VisualEditor: Doing anything in a slug after an internal node throws an error,Related URL: https://gerrit.wikimedia.org/r/70333 (Gerrit Change I3818ebe9816e7d781233f087b15694bf7ba12965),1372112447,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tbvrdwvxvbqqobem3szn,task_subcomment,NA
+VisualEditor: Doing anything in a slug after an internal node throws an error,This is caused by CE placing a slug after internal nodes.  Fix in progress.,1372112372,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-tbvrdwvxvbqqobem3szn,task_subcomment,NA
+VisualEditor: Doing anything in a slug after an internal node throws an error,"Stack error:
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 73 ve.ce.Document.js:187
+ve.ce.Document.getNodeAndOffset ve.ce.Document.js:187
+ve.ce.Surface.showSelection ve.ce.Surface.js:1289
+ve.ce.Surface.onChange ve.ce.Surface.js:739
+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.MWReferenceDialog.onClose ve.ui.MWReferenceDialog.js:197
+ve.ui.Window.close ve.ui.Window.js:332
+(anonymous function) ve.ui.Dialog.js:118
+proxy",1372109556,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-tbvrdwvxvbqqobem3szn,task_subcomment,NA
+VisualEditor: HTML comment not removed from user pasting (? from external source),"https://en.wikipedia.org/w/index.php?title=Richard_Ned_Lebow&diff=561410032&oldid=545013166
+
+Perhaps unrelated to VisualEditor?
+
+<!-- /* Font Definitions */@font-face	{font-family:""Courier New"";	panose-1:2 7 3 9 2 2 5 2 4 4;	mso-font-charset:0;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:-536859905 -1073711037 9 0 511 0;}@font-face	{font-family:Times;	panose-1:2 0 5 0 0 0 0 0 0 0;	mso-font-charset:0;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:3 0 0 0 1 0;}@font-face	{font-family:Wingdings;	panose-1:5 0 0 0 0 0 0 0 0 0;	mso-font-charset:2;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:0 268435456 0 0 -2147483648 0;}@font-face	{font-family:""ＭＳ 明朝"";	mso-font-charset:78;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:-536870145 1791491579 18 0 131231 0;}@font-face	{font-family:""Cambria Math"";	panose-1:2 4 5 3 5 4 6 3 2 4;	mso-font-charset:0;	mso-generic-font-family:auto;	mso-font-pitch:variable;	mso-font-signature:-536870145 1107305727 0 0 415 0;} /* Style Definitions */p.MsoNormal, li.MsoNormal, div.MsoNormal	{mso-style-unhide:no;	mso-style-qformat:yes;	mso-style-parent:"""";	margin:0in;	margin-bottom:.0001pt;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph	{mso-style-priority:34;	mso-style-unhide:no;	mso-style-qformat:yes;	margin-top:0in;	margin-right:0in;	margin-bottom:0in;	margin-left:.5in;	margin-bottom:.0001pt;	mso-add-space:auto;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst	{mso-style-priority:34;	mso-style-unhide:no;	mso-style-qformat:yes;	mso-style-type:export-only;	margin-top:0in;	margin-right:0in;	margin-bottom:0in;	margin-left:.5in;	margin-bottom:.0001pt;	mso-add-space:auto;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle	{mso-style-priority:34;	mso-style-unhide:no;	mso-style-qformat:yes;	mso-style-type:export-only;	margin-top:0in;	margin-right:0in;	margin-bottom:0in;	margin-left:.5in;	margin-bottom:.0001pt;	mso-add-space:auto;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast	{mso-style-priority:34;	mso-style-unhide:no;	mso-style-qformat:yes;	mso-style-type:export-only;	margin-top:0in;	margin-right:0in;	margin-bottom:0in;	margin-left:.5in;	margin-bottom:.0001pt;	mso-add-space:auto;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:""Times New Roman"";	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}.MsoChpDefault	{mso-style-type:export-only;	mso-default-props:yes;	mso-fareast-font-family:""ＭＳ 明朝"";	mso-fareast-theme-font:minor-fareast;	mso-bidi-font-family:""Times New Roman"";	mso-bidi-theme-font:minor-bidi;}@page WordSection1	{size:8.5in 11.0in;	margin:1.0in 1.25in 1.0in 1.25in;	mso-header-margin:.5in;	mso-footer-margin:.5in;	mso-paper-source:0;}div.WordSection1	{page:WordSection1;} /* List Definitions */@list l0	{mso-list-id:85738127;	mso-list-type:hybrid;	mso-list-template-ids:1894403420 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}@list l0:level1	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Symbol;}@list l0:level2	{mso-level-number-format:bullet;	mso-level-text:o;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:""Courier New"";	mso-bidi-font-family:""Times New Roman"";}@list l0:level3	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Wingdings;}@list l0:level4	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Symbol;}@list l0:level5	{mso-level-number-format:bullet;	mso-level-text:o;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:""Courier New"";	mso-bidi-font-family:""Times New Roman"";}@list l0:level6	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Wingdings;}@list l0:level7	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Symbol;}@list l0:level8	{mso-level-number-format:bullet;	mso-level-text:o;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:""Courier New"";	mso-bidi-font-family:""Times New Roman"";}@list l0:level9	{mso-level-number-format:bullet;	mso-level-text:;	mso-level-tab-stop:none;	mso-level-number-position:left;	text-indent:-.25in;	font-family:Wingdings;}ol	{margin-bottom:0in;}ul	{margin-bottom:0in;}-->
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372105380,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-sdadbdxs63vkmq4vqjom,task_description,resolved
+VisualEditor: HTML comment not removed from user pasting (? from external source),"Change 86664 merged by jenkins-bot:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1385500071,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdadbdxs63vkmq4vqjom,task_subcomment,NA
+VisualEditor: HTML comment not removed from user pasting (? from external source),Rich paste will strip all metadata and so should solve this issue.,1381157634,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sdadbdxs63vkmq4vqjom,task_subcomment,NA
+VisualEditor: HTML comment not removed from user pasting (? from external source),"Change 86664 had a related patch set uploaded by Esanders:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1381157515,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdadbdxs63vkmq4vqjom,task_subcomment,NA
+VisualEditor: HTML comment not removed from user pasting (? from external source),"Bizarre indeed; presumably this is from a copy-and-paste and the ""give me only the plain text"" request to the browser is being ignored?",1372112566,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sdadbdxs63vkmq4vqjom,task_subcomment,NA
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text","* Go here http://en.wikipedia.org/w/index.php?title=User:ESanders_(WMF)/Sandbox&oldid=561403721&veaction=edit
+* Select from the end of the image to inside the link
+* Observe you now have a link inspector positioned over the image.
+Bonus:
+* Use the inspector to edit the link
+* Review your changes, the image has been killed, and the link as gone a bit crazy
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372102800,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-isqwpxpplzad6mrvzuhz,task_description,resolved
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text",Fixed. Will go out in next push.,1377195359,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-isqwpxpplzad6mrvzuhz,task_subcomment,NA
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text","Change 79919 merged by jenkins-bot:
+getAnnotationsFromRange should only ignore non-content data
+
+https://gerrit.wikimedia.org/r/79919",1377195128,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-isqwpxpplzad6mrvzuhz,task_subcomment,NA
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text",'Bonus' section has been filed here: https://bugzilla.wikimedia.org/show_bug.cgi?id=53151,1377090118,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-isqwpxpplzad6mrvzuhz,task_subcomment,NA
+"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text","Change 79919 had a related patch set uploaded by Esanders:
+getAnnotationsFromRange should only ingnore non-content data
+
+https://gerrit.wikimedia.org/r/79919",1376944734,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-isqwpxpplzad6mrvzuhz,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"Screenshot of the problem in the serialization
+
+I think this is caused by Parsoid trying to preserver/re-add whitespace when round-tripping.
+
+Steps to reproduce issue:
+* Create a page like the default MediaWiki main page:
+
+<<<MW
+'''MediaWiki has been successfully installed.'''
+
+Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki sandbox software. 12
+
+== Getting started ==
+* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
+* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
+* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
+* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]
+MW;
+
+* Edit it with VisualEditor
+* Put the cursor before ""MediaWiki release mailing list"" and select back until before the first character of the heading ""Getting started"".
+* Press backspace. You're now left with 2 of 4 items in the list and an empty heading.
+* Again, out the cursor before ""MediaWiki release mailing list"" and delete until you're behind ""software. 12"". You're now left with ""MediaWiki release mailing list"" in the paragraph and a list with 1 item.
+* Save page -> Review changes (Screenshot attached)
+
+It inserts a lot of new lines.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11588}",1372101840,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_description,resolved
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,Please reopen if this an issue in Parsoid.,1372370405,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"There was a typo.  It should read:  "".... where there are *NONE* ....""",1372111668,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"This seems to be a bug in the diff interface in mediawiki.  There are no extra newlines in the wikitext source as indicated by the diff.  The diff incorrectly signals newlines where there are now.
+
+Steps to reproduce:
+
+* Do everything as Krinkle says
+* Actually save the page.
+* Look at the new wikitext source and look at what the diff tells you.
+
+I am leaving this bug open so others can verify independently.",1372111612,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"(In reply to comment #2)
+> Krinkle: Could you provide a dump of VE's input and output DOM?
+
+Given the steps to reproduce the bug from comment 0, I get the following:
+
+> doc = ve.instances[0].model.documentModel;
+> d = ve.createDocumentFromHtml( ve.init.mw.targets[0].originalHtml );
+> d2 = ve.dm.converter.getDomFromData( doc.getFullData(), doc.getStore(), doc.getInternalList() );
+> copy( d.body.innerHTML );
+
+<p data-parsoid=""{&quot;dsr&quot;:[0,48,0,0]}""><b data-parsoid=""{&quot;dsr&quot;:[0,48,3,3]}"">MediaWiki has been successfully installed.</b></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[50,171,0,0]}"">Consult the <a rel=""mw:ExtLink"" href=""//meta.wikimedia.org/wiki/Help:Contents"" data-parsoid=""{&quot;targetOff&quot;:103,&quot;dsr&quot;:[62,116,41,1]}"">User's Guide</a> for information on using the wiki sandbox software. 12</p>
+
+<h2 data-parsoid=""{&quot;dsr&quot;:[173,194,2,2]}""> Getting started </h2>
+<ul data-parsoid=""{&quot;dsr&quot;:[195,535,0,0]}""><li data-parsoid=""{&quot;dsr&quot;:[195,281,1,0]}""> <a rel=""mw:ExtLink"" href=""//www.mediawiki.org/wiki/Manual:Configuration_settings"" data-parsoid=""{&quot;targetOff&quot;:253,&quot;dsr&quot;:[197,281,56,1]}"">Configuration settings list</a></li>
+<li data-parsoid=""{&quot;dsr&quot;:[282,335,1,0]}""> <a rel=""mw:ExtLink"" href=""//www.mediawiki.org/wiki/Manual:FAQ"" data-parsoid=""{&quot;targetOff&quot;:321,&quot;dsr&quot;:[284,335,37,1]}"">MediaWiki FAQ</a></li>
+<li data-parsoid=""{&quot;dsr&quot;:[336,434,1,0]}""> <a rel=""mw:ExtLink"" href=""https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce"" data-parsoid=""{&quot;targetOff&quot;:403,&quot;dsr&quot;:[338,434,65,1]}"">MediaWiki release mailing list</a></li>
+<li data-parsoid=""{&quot;dsr&quot;:[435,535,1,0]}""> <a rel=""mw:ExtLink"" href=""//www.mediawiki.org/wiki/Localisation#Translation_resources"" data-parsoid=""{&quot;targetOff&quot;:498,&quot;dsr&quot;:[437,535,61,1]}"">Localise MediaWiki for your language</a></li></ul>
+
+> copy( d2.body.innerHTML );
+
+<p data-parsoid=""{&quot;dsr&quot;:[0,48,0,0]}""><b data-parsoid=""{&quot;dsr&quot;:[0,48,3,3]}"">MediaWiki has been successfully installed.</b></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[50,171,0,0]}"">Consult the <a href=""//meta.wikimedia.org/wiki/Help:Contents"" rel=""mw:ExtLink"" data-parsoid=""{&quot;targetOff&quot;:103,&quot;dsr&quot;:[62,116,41,1]}"">User's Guide</a> for information on using the wiki sandbox software. 12<a href=""https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce"" rel=""mw:ExtLink"" data-parsoid=""{&quot;targetOff&quot;:403,&quot;dsr&quot;:[338,434,65,1]}"">MediaWiki release mailing list</a></p><ul data-parsoid=""{&quot;dsr&quot;:[195,535,0,0]}""><li data-parsoid=""{&quot;dsr&quot;:[435,535,1,0]}""> <a href=""//www.mediawiki.org/wiki/Localisation#Translation_resources"" rel=""mw:ExtLink"" data-parsoid=""{&quot;targetOff&quot;:498,&quot;dsr&quot;:[437,535,61,1]}"">Localise MediaWiki for your language</a></li></ul>",1372108572,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,Krinkle: Could you provide a dump of VE's input and output DOM?,1372104921,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM,"Subbu, could this be caused by e90e40c26cd8?",1372103979,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-edvyo63z4kmo5a2d7dvy,task_subcomment,NA
+VisualEditor: First character after a </pre> is lost on round-trip,"I edited a large page on meta (1.22wmf7) in VE. All seemed fine but review showed VE had removed the first character following several closing </pre> tags. It also removed a few characters within a <source> tag.
+
+Here's the diff showing the removal, it's self-explanatory.  <https://www.mediawiki.org/w/index.php?title=Extension%3AEventLogging%2FGuide&diff=716359&oldid=704840>.  I will restore the characters by hand.
+I'm using Firefox 21.0 on Kubuntu 13.04.
+
+I tried editing the same document again and this time VE removed more characters from the source tag, added a space after a <pre>. Hmm. I'm setting to critical as it's recoverable data loss, but maybe it's intermittent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1372098360,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ay5qiidktmoux2bli72a,task_description,resolved
+VisualEditor: First character after a </pre> is lost on round-trip,"Here is another example:
+https://www.mediawiki.org/w/index.php?title=Gerrit/Tutorial&diff=717045",1372510492,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ay5qiidktmoux2bli72a,task_subcomment,NA
+VisualEditor: First character after a </pre> is lost on round-trip,"(In reply to comment #2)
+> Can't reproduce in master.
+
+Neither can I, in production or master. I'm going to close this as fixed, but please re-open if it recurs.",1372355490,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ay5qiidktmoux2bli72a,task_subcomment,NA
+VisualEditor: First character after a </pre> is lost on round-trip,"Can't reproduce in master.
+
+An issue I am seeing is code inside <source> and <syntaxhighligh> blocks are losing their linebreaks. Might want to file a bug if we aren't aware of that.
+
+Editing inside source is now bug 50224",1372250776,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ay5qiidktmoux2bli72a,task_subcomment,NA
+VisualEditor: First character after a </pre> is lost on round-trip,"Making this primarily about the first character after a </pre> getting lost on round-trip; I'm not sure how you were able to edit inside a <source> tag, though, so that needs exploring too if it recurs.",1372113996,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ay5qiidktmoux2bli72a,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"From http://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Problem_with_using_shift%2B
+
+""Hi. I have been using the visual editor for a while on ar Wikipedia, it is very nice and smooth for fast edits. However, I am facing a very strange problem when I need to add some Arabic diacritics known as tashkil; when I press shift+diacritic button (like x, e, or z) the letter I pressed starts to repeat itself endlessly, and it can only be stopped by refreshing the page and wasting the work I have did. Any thoughts?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50631",1372087860,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-pg6duwir2q65ub4iepr6,task_description,resolved
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"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!",1377202348,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"Change 80080 merged by jenkins-bot:
+Don't emit Surface changes back to the Surface
+
+https://gerrit.wikimedia.org/r/80080",1377164920,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"**aaddira** wrote:
+
+Thank you. I have tested all possible diacritics on Arabic Wikipedia and everything is working great. Good job!",1377037457,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"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",1377027676,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"I think this may be resolved by the following patch:
+https://gerrit.wikimedia.org/r/#/c/79451 . It fixes similar bugs in other scripts with similar properties.
+
+If it's still broken, is it possible to give a specific example of:
+
+1. A piece of Arabic text where VisualEditor fails
+2. The keystrokes required to enter the text
+3. The incorrect output observed in VisualEditor
+4. The OS, browser and input method used.
+
+Thanks!",1376936389,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"(In reply to comment #2)
+> Thanks James - first bug report.
+
+No worries. :-) Welcome to the party.",1372090765,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,Thanks James - first bug report.,1372090521,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken,"Bumping priority, moving module, assigning, slight rewording; note that we can't fix things in the past (;-)), so setting to next week's deployment deadline.",1372090412,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pg6duwir2q65ub4iepr6,task_subcomment,NA
+VisualEditor: HTML comments being removed inside templates,"https://en.wikipedia.org/w/index.php?title=Jason_Bateman&curid=685922&diff=561337061&oldid=559944750
+
+https://en.wikipedia.org/w/index.php?title=David_Stewart_(photographer)&curid=24365669&diff=561336970&oldid=529664374
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372086120,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_description,resolved
+VisualEditor: HTML comments being removed inside templates,"Confirmed that this indeed now fixed, now that everyone's caches have rotated.",1373851510,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_subcomment,NA
+VisualEditor: HTML comments being removed inside templates,"comment 1 is an example that is not fixed by bug 50071, and im still seeing the problem occur.
+
+https://en.wikipedia.org/w/index.php?title=Republic_of_Texas&diff=562971813&oldid=562786837",1373029845,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_subcomment,NA
+VisualEditor: HTML comments being removed inside templates,"
+
+*** This bug has been marked as a duplicate of bug 50071 ***",1372113547,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_subcomment,NA
+VisualEditor: HTML comments being removed inside templates,https://en.wikipedia.org/w/index.php?title=Paul_Evans_(footballer_born_1973)&curid=15575267&diff=561390930&oldid=561390588,1372096563,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gqjhk4wjp2xx3zlksb5g,task_subcomment,NA
+"VisualEditor: Templates' phantoms can overlap the toolbar, hindering saving/etc.","Screenshot
+
+See screenshot; this is still happening as of [timestamp of this bug]. The VE interprets a click on 'save page' to be an attempt to interact with the infobox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49059
+
+**Attached**: {F11515}",1372081680,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-zhyimecjptsrsi7gj65o,task_description,resolved
+"VisualEditor: Templates' phantoms can overlap the toolbar, hindering saving/etc.","**orbit** wrote:
+
+This is fixed now in master.",1372205712,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zhyimecjptsrsi7gj65o,task_subcomment,NA
+"VisualEditor: Templates' phantoms can overlap the toolbar, hindering saving/etc.","Created attachment 12625
+Screenshot of blue phantom overlapping save dialog using VisualEditor on the English Wikipedia, 2013-06-24
+
+Confirmed.
+
+**Attached**: {F11517}",1372100654,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-zhyimecjptsrsi7gj65o,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,"Compare the references section of https://en.wikipedia.org/wiki/A_Slight_at_the_Opera in read and edit mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52371",1372080180,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gww3sadaua5hd4aa5mxy,task_description,resolved
+VisualEditor: Reflist sometimes not fully being populated,"No, this bug was fixed; I think that that's a different issue. Splitting.",1375381775,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,%%%*** Bug 52371 has been marked as a duplicate of this bug. ***%%%,1375381498,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,Reopening; see bug 52371 for an example of this still happening.,1375381485,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,This was fixed in the re-working of references last week; marking as fixed.,1375381274,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Reflist sometimes not fully being populated,"I can't reproduce this using the example above now, even looking at the version that was live when the comment was left. I see four references in both read and edit modes.",1375340495,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gww3sadaua5hd4aa5mxy,task_subcomment,NA
+VisualEditor: Lag when selecting complex templates (especially in big pages),"(from bug 49922 comment 1)
+
+VE is slow at selecting templates and transclusions in big pages.
+
+For example: [[World War II]]:
+
+ - attempt to select infobox by clicking on it: takes ~3 seconds in 
+   Firefox 21 and Chrome 27, with no visual indication that anything
+   is happening during the wait
+
+ - attempt to select the reflist by clicking on it: just hangs in Firefox
+   and Chrome, never actually seems to happen
+
+This either needs to be sped up, or fail more gracefully.
+
+In IE10, this is not such a problem \o/ - lag is actually less, and the reflist can be selected (takes about 22 seconds).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372048320,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_description,resolved
+VisualEditor: Lag when selecting complex templates (especially in big pages),"This is an old report that I think is now closable (but performance is of course an on-going concern).
+
+For these particular concerns, we've recently fixed a number of performance issues germane to these:
+
+* Selection of the template, and opening the dialog, takes much less than a
+  second now for me (I'd call it instant, roughly).
+* Loading the second reflist is much quicker too (the first one was already near-instant).
+
+(Note that these fixes should hit production later today.)
+
+Consequently, I'm marking this as ""FIXED"", though there's always going to be more to do.",1406824618,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_subcomment,NA
+VisualEditor: Lag when selecting complex templates (especially in big pages),"Created attachment 13765
+beyond the selected reflist
+
+**Attached**: {F11475}",1384199300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_subcomment,NA
+VisualEditor: Lag when selecting complex templates (especially in big pages),"Created attachment 13764
+Above the reflist
+
+**Attached**: {F11474}",1384199261,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_subcomment,NA
+VisualEditor: Lag when selecting complex templates (especially in big pages),"Experienced the lag in selecting both the info box and reflist on that page in chrome Version 26.0.1410.65 and firefox 20 (MAC OS X version 10.8.5)
+
+However, did not experience the hang while selecting the reflist in either of the browsers.
+
+Also,while selecting the reflist , the blue selection box progresses beyond the reflist selected in both sides.
+
+See the screenshots attached.",1384199216,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3f6rzvtal3vp7j7ok4ve,task_subcomment,NA
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed","See the unexpected changes at https://en.wikipedia.org/w/index.php?title=Thomson_Airways&diff=561270595&oldid=561268927
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372037280,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-4gxgm32h47ktjmsohfhi,task_description,resolved
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed",Fixed and will go out in about an hour.,1372089793,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4gxgm32h47ktjmsohfhi,task_subcomment,NA
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed",Related URL: https://gerrit.wikimedia.org/r/70133 (Gerrit Change Ib13bb206c49b1f5b186e40632a5c109def0f042e),1372069539,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4gxgm32h47ktjmsohfhi,task_subcomment,NA
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed",Data model issue.,1372042733,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4gxgm32h47ktjmsohfhi,task_subcomment,NA
+"VisualEditor: When a page contains two identical templates right next to each other, one is removed","When a page contains two identical templates right next to each other, VE removes one of them. 
+
+Try editing [[User:This, that and the other/sandbox/VE5]] in VE, for example.",1372039711,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-4gxgm32h47ktjmsohfhi,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","Screenshot
+
+See screenshot. What am I meant to be paying attention to?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11451}",1372035900,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-wnsljgens4avgolp5rah,task_description,resolved
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack",This has indeed be fixed by the above on-wiki change; closing.,1373037205,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","(In reply to comment #9)
+> .ve-init-mw-viewPageTarget-toolbar-editNotices-notice .editnotice-redlink {
+> display: none !important; }
+> 
+> I'd recommend the community adds this to [[MediaWiki:Group-sysop.css]]
+
+Actually, add it to [[MediaWiki:Common.css]] below "".sysop-show { display: none"" because we want it to apply to non-sysops who made this visible in their user css as well. It won't affect anything else.",1372814858,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","I agree that it isn't obvious whether the community does or doesn't want this information on the edit page. However I also want to emphasise that this is hidden by default, and thanks to our logic that strips out fake notices that have no visible content, they are hidden for the vast majority of users.
+
+If this ""Page notice"" redlink is visible, it is because the user has styles in their state (either from [[MediaWiki:Group-sysop.css]] or their user stylesheet) that make "".editnotice-redlink"" or "".show-sysops"" visible (the element in the edit notice has both classes).
+
+So one could argue showing it is the right thing to do, for they want to see it. Why would they want to see it on the edit page but not in VisualEditor? Likely because they don't use it that much in the first place, but it is more intruding in VisualEditor because notices pop up from the editor.
+
+Anyway, to hide in visualeditor without hiding it else where, you can use the following line of CSS:
+
+.ve-init-mw-viewPageTarget-toolbar-editNotices-notice .editnotice-redlink { display: none !important; }
+
+I'd recommend the community adds this to [[MediaWiki:Group-sysop.css]] right below the rules for  "".show-sysop { display: block !important; }"" and the like.
+
+Note that we can't use ve-ui-toolbar, we can only use ""ve-init-mw-viewPageTarget-toolbar-editNotices-notice"" because the other elements aren't in the notice's element tree until *after* it is already in the VE DOM, and hiding it after that will merely make the link invisible, the notice container will still be there.",1372814249,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","(In reply to comment #6)
+> There isn't much we can do. If the community insists it is useful to have
+> placeholder edit notices when there is no editnotice that allows opt-in users
+> to create them from a red link, then this is exactly what they want, is it
+> not?
+> 
+> It shows that on EditPage as well (except in there, they are less visible as
+> actual notices but appear as part of the page).
+
+I disagree that the consensus that the enwiki community achieved for having this edit notice in wikitext editor (a consensus which I have disagreed for years, but there you go) transfers to consensus that they want it displaying in VisualEditor.
+
+As a quick hack, we could sniff for the edit notice having class=""editnotice-redlink"" on it and killing that notice from the array. It's horrible, but it will stop the problem until we fix it properly.",1372813340,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","Last I checked, we're part of the community.",1372806658,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","I fixed most of these last year by supporting client-side ""hidden"" notices as non-existent through the hasVisibleText logic I wrote.
+
+These used to trigger a notice for all users, now it only triggers a notice for users that have css in their state that makes these red links visible (I think this is limited to MediaWiki:Group-sysop.css by default +  anyone else who likes to have it as well).
+
+There isn't much we can do. If the community insists it is useful to have placeholder edit notices when there is no editnotice that allows opt-in users to create them from a red link, then this is exactly what they want, is it not?
+
+It shows that on EditPage as well (except in there, they are less visible as actual notices but appear as part of the page).",1372801246,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","This really should be solved on en.wp, not in VE.",1372784144,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","I'd recommend prioritizing this very highly, it's a rather negative experience.",1372784020,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack",*** Bug 50531 has been marked as a duplicate of this bug. ***,1372727149,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","(In reply to comment #1)
+> (In reply to comment #0)
+> > Created attachment 12619 [details]
+> > Screenshot
+> > 
+> > See screenshot. What am I meant to be paying attention to?
+> 
+> That enwiki's community, in its wisdom, wants you to see that you can add a
+> page notice to every page, because you're +sysop. It doesn't appear for
+> non-sysops. If they want to commit to adding a class to it that we suppress
+> and reduce the count by one, we're happy to do that.
+
+Looking into this, it seems like we can use class=""editnotice-redlink"" to select and suppress these (including reducing the count by one). Handing to Timo to implement.
+
+**Attached**: {F11451}",1372172066,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack","(In reply to comment #0)
+> Created attachment 12619 [details]
+> Screenshot
+> 
+> See screenshot. What am I meant to be paying attention to?
+
+That enwiki's community, in its wisdom, wants you to see that you can add a page notice to every page, because you're +sysop. It doesn't appear for non-sysops. If they want to commit to adding a class to it that we suppress and reduce the count by one, we're happy to do that.
+
+**Attached**: {F11451}",1372036133,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wnsljgens4avgolp5rah,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"Click after the line ""Saptaitey Chiranjeevinaha[citation needed]"" on https://en.wikipedia.org/wiki/Chiranjivi and BANG! And the text is gone.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372035720,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_description,resolved
+VisualEditor: Deletion into a DL from a block slug breaks,Fixed and will go out in an hour.,1374186072,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"Change 73952 merged by jenkins-bot:
+Handle backspace correctly when in a slugs
+
+https://gerrit.wikimedia.org/r/73952",1374186006,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"Change 73952 had a related patch set uploaded by Esanders:
+Handle backspace correctly when in a root slug
+
+https://gerrit.wikimedia.org/r/73952",1373975739,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"(In reply to comment #4)
+> Yes; you need to backspace over the DL from the block slug underneath it to
+> trigger.
+Yeah, that breaks it. For some reason handleDelete() tries to process *two* transactions: one successfully removes the entire <dl>, and the second tries to reinsert part of it but in the middle of a paragraph, presumably because it computed the wrong offset somehow (failing to adjust for the first transaction, maybe)?",1373658227,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,Yes; you need to backspace over the DL from the block slug underneath it to trigger.,1373502736,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"I can't reproduce this any more, can anyone else?",1373500564,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"DefinitionListNode shouldn't have getAnnotatedHtml, it's not inside a content branch. Did we screw up the DM such that a definition list ended up inside a paragraph?",1373499822,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: Deletion into a DL from a block slug breaks,"Yuck. Thrown error is:
+
+  Uncaught TypeError: Object #<VeCeDefinitionListNode> has no method 'getAnnotatedHtml' 
+
+Sounds like we didn't update the CE nodes for DLs.",1373163018,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2jhlgapomh7x5pp3mfeq,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,"See https://en.wikipedia.org/w/index.php?title=Beautiful_%28Mariah_Carey_song%29&diff=561243294&oldid=561242578
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372034760,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_description,resolved
+VisualEditor: HTML comments being removed inside references,Fixed and will be going out today.,1372210324,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,Related URL: https://gerrit.wikimedia.org/r/70469 (Gerrit Change I5a844e2e0655bc1db152b3805718324ca0bb04df),1372189640,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,*** Bug 50102 has been marked as a duplicate of this bug. ***,1372113547,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,"s/templates/references/ gah, sorry",1372108420,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,Now appearing outside of templates; https://en.wikipedia.org/w/index.php?title=Lichens_%28musician%29&curid=16561703&diff=561390034&oldid=556766679,1372097824,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: HTML comments being removed inside references,"Roan, can you tell how we're dirtying the DOM such that Parsoid changes these at all?",1372036818,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k3jo2lfnt7epz4x6sikv,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,"See https://en.wikipedia.org/w/index.php?title=Riddler&diff=561149660&oldid=561096940
+
+The user reports they were nowhere near the infobox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50147
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50129",1372034400,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-67esakdk26er4uxasrc3,task_description,resolved
+VisualEditor: Nowiki-ing inside templates' parameters,This is now fixed and pushed live; sorry for the failure.,1372218685,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,*** Bug 50129 has been marked as a duplicate of this bug. ***,1372127871,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,Bug 50147 is the underlying problem in Parsoid; this bug is for fixing the dirty-DOMing that makes Parsoid trigger on the templates.,1372125589,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,"Other examples of nowiki insertion:
+
+http://en.wikipedia.org/w/index.php?title=Glenn_Greenwald&diff=561437483&oldid=561434741
+
+https://en.wikipedia.org/w/index.php?title=Schuylar_Oordt&diff=561438828&oldid=561406705",1372122627,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+VisualEditor: Nowiki-ing inside templates' parameters,"Roan, can you tell how we're dirtying the DOM such that Parsoid changes these at all?",1372036412,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-67esakdk26er4uxasrc3,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"See https://en.wikipedia.org/w/index.php?title=Port_of_Hull&diff=561131671&oldid=561056099 - an attempt to enter a dash led to bolding vanishing. Not sure what's going on there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372033860,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-5cf6g72rzkft37gbritr,task_description,resolved
+Parsoid: selser drops last three apostrophes in '''''foo''''',https://gerrit.wikimedia.org/r/70768 (Gerrit Change I69bda7db141a3302cee6ece5af5ffdc57e748d89) | change APPROVED and MERGED [by jenkins-bot],1372291023,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',Related URL: https://gerrit.wikimedia.org/r/70768 (Gerrit Change I69bda7db141a3302cee6ece5af5ffdc57e748d89),1372287578,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',Related URL: https://gerrit.wikimedia.org/r/70768 (Gerrit Change I69bda7db141a3302cee6ece5af5ffdc57e748d89),1372287575,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',*** Bug 50258 has been marked as a duplicate of this bug. ***,1372284454,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"I can't reproduce the dirtying of the paragraph locally. If I make a null change, I get a null diff. If I change anything outside the bold+italic text, I get the bad diff.
+
+There are some dirtying issues with the code that was in production at the time, and still one left for which the fix is not deployed. That said, the minimal test case for this ( https://en.wikipedia.org/w/index.php?title=User:JohnCD/VEtest5&diff=next&oldid=561489465 ) does have a neighboring change.",1372218541,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"Here are actually two bugs:
+
+1) a VE bug that causes that paragraph to be dirtied
+2) a Parsoid bug that does not round-trip the bolding properly when using selser on bold elements
+
+Should I open a separate bug for VisualEditor, or do you have one for this already?",1372218203,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"This turns out to be a Parsoid bug:
+
+$ echo ""Foo '''''bar''''' baz"" > wt
+$ node parse.js --wt2html < wt | tee html
+<body><p data-parsoid='{""dsr"":[0,21,0,0]}'>Foo <i data-parsoid='{""dsr"":[4,14,2,2]}'><b data-parsoid='{""autoInsertedEnd"":true,""dsr"":[6,12,3,0]}'>bar</b></i> baz</p>
+</body>
+$ sed 's/baz/baaz/g' < html | tee html2
+<body><p data-parsoid='{""dsr"":[0,21,0,0]}'>Foo <i data-parsoid='{""dsr"":[4,14,2,2]}'><b data-parsoid='{""autoInsertedEnd"":true,""dsr"":[6,12,3,0]}'>bar</b></i> baaz</p>
+</body>
+$ node parse.js --html2wt --selser --oldtextfile wt --oldhtmlfile html < html2
+Foo '''''bar'' baaz
+
+Note that this doesn't break if there is no DOM change (i.e. if you pipe in html rather than html2 in the last step), and it also doesn't break if selser is disabled (i.e. if you omit --selser in the last step).",1372217410,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',We've seen this come up a number of times in our testing; I haven't investigated this one yet.,1372215813,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+Parsoid: selser drops last three apostrophes in '''''foo''''',"Roan, can you tell how we're dirtying the DOM such that Parsoid changes these at all?",1372037116,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5cf6g72rzkft37gbritr,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,"Currently we don't and cause major headaches for Parsoid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1372028700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-spoxch2h3fjmkmu6pdme,task_description,resolved
+VisualEditor: Preserve ordering inside data-mw elements,"**ignatzmice.wiki** wrote:
+
+Apparently bug 50080 is a duplicate of this bug. However, that bug is still showing up: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=564509171#VE_totally_screwing_up",1373983343,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50108 has been marked as a duplicate of this bug. ***,1372101714,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50108 has been marked as a duplicate of this bug. ***,1372091701,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50106 has been marked as a duplicate of this bug. ***,1372091672,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50101 has been marked as a duplicate of this bug. ***,1372091521,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50099 has been marked as a duplicate of this bug. ***,1372091385,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,*** Bug 50080 has been marked as a duplicate of this bug. ***,1372039230,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Preserve ordering inside data-mw elements,Related URL: https://gerrit.wikimedia.org/r/70109 (Gerrit Change If0a5bcc67d3a172de0e8839cfda11efacfbf36ff),1372032121,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-spoxch2h3fjmkmu6pdme,task_subcomment,NA
+VisualEditor: Metadata is not annotated,"Which causes this dirty diff:
+
+'''Foo<!--bar-->baz'''
+
+=>
+
+'''Foo'''<!--bar-->'''baz'''
+
+Of course annotating un-deletable metadata means if 'Foobaz' is erased you will be left with:
+
+'''<!--bar-->'''
+
+but that's less of a problem, and could be fixed by Parsoid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372009920,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rghqg5jcqisid4tfv5hr,task_description,resolved
+VisualEditor: Metadata is not annotated,Related URL: https://gerrit.wikimedia.org/r/70061 (Gerrit Change I40da3d5e8e987571195142304b1a853e177e36ff),1372010156,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rghqg5jcqisid4tfv5hr,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Screenshot
+
+See the screenshot; it appears in Monobook on enwiki and mediawiki.org as of the latest release. Kiiinda a problem.
+
+(the other interstitials there - review your changes/save page - are also shrunk).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11418}",1372005660,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_description,resolved
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write",Now fixed in master and will be deployed in a few minutes' time.,1374793868,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Change 75814 merged by jenkins-bot:
+Fix font size for overlays in Monobook
+
+https://gerrit.wikimedia.org/r/75814",1374791926,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","I'd add that even on en.wp Monobook is used by many (at least if I read correctly  http://en.wikipedia.org/wiki/Wikipedia:Database_reports/User_preferences#Skin ).
+I had quite a few complaints about this now at it.wp, so it would really great if we managed to fix this ASAP. Thanks!
+
+(confl. by Gerrit: fixed now?)",1374708007,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Change 75814 had a related patch set uploaded by Esanders:
+Fix font size for overlays in Monobook
+
+https://gerrit.wikimedia.org/r/75814",1374707619,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","**mrkmg90** wrote:
+
+Review changes popup
+
+The review changes popup also has the same sizing issues...
+
+My eyes strain so hard trying to read the lines!
+
+**Attached**: {F11419}",1374501653,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","(In reply to comment #6)
+> Can I suggest that the title of this bug is changed to something more
+> meaningful?  If the words ""edit summary"" were included there would probably
+> be fewer duplicatates reported.
+
+Done.",1373807253,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Can I suggest that the title of this bug is changed to something more meaningful?  If the words ""edit summary"" were included there would probably be fewer duplicatates reported.",1373807116,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write",*** Bug 51315 has been marked as a duplicate of this bug. ***,1373805517,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write",*** Bug 51034 has been marked as a duplicate of this bug. ***,1373442406,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","You could add a CSS rule that uses the same technique for the dialog.
+
+Setting a simple relative font size (0.7em or something like that) makes it impossible to set the browser's default size to something sensible, as 0.7 * something sensible is usually too small. The non-linear nature of keyword scaling gives a good compromise between honoring a browser's font size and providing sane defaults despite 16px browser defaults.
+
+So if there are other JS-free solutions to this issue these days then that would be great.",1372103906,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","This is due to Monobook's ""interesting"" way of resetting the font-size to a consistent value cross-browser. It sets the <body> font-size to x-small, and then turn it back up to regular size with ""font-size: 127%;"" from their globalWrapper div.
+
+Due to this odd construct, any new elements attached to the <body> have an exceptionally small font size.
+
+Short of hardcoding a larger font-size for the overlay wrappers in Monobook or appending to #globalWrapper in monobook (which might cause others bugs due to not being in the <body> directly) - short of that this is a tough one to get right. Ideally core would fix this in Monobook by using the same font-size technique used by Vector.
+
+In Monobook's author's defence (Gabriel), the browsers we had to support when Monobook was being developed made it quite difficult to do right so this was probably the best way to do it at the time – but we no longer need to worry about IE5.5, IE4-for-Mac, Opera<7 etc.",1372027547,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+"VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write","Timo, what have you wrought?! ;-)",1372005848,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o6x7c2kbmm5le5grlxkj,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"You can't tab from the edit summary box to the ""Save page"" button, or the reference inspector to the ""Apply changes"" button, etc.
+
+This is important for accessibility. Currently, there is no way to confirm the action using only the keyboard.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50897",1371984240,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_description,resolved
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Hmm, yeah, this has regressed for Firefox. Yay for browser bugs. Will follow-up on bug 51918.",1400619419,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Enwiki, Firefox nightly on Mac. But does seem to work on office with Chrome.",1400616530,PHID-USER-n2ftvsjm34tosq65gpve,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"I can on enwiki, MediaWiki.org and Beta Labs – where are you having this issue?",1400616057,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"This appears to be broken again- can't tab to ""save page"" in the current release. Prefer to reopen this bug or file a new one?",1400615746,PHID-USER-n2ftvsjm34tosq65gpve,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,This bug is fixed. Will use bug 51918 to track changes to tab order instead.,1374880834,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,*** Bug 52080 has been marked as a duplicate of this bug. ***,1374818679,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"The current tab order is pants, and is not what was requested in comment 1 or comment 5.
+
+From the edit summary box, the tab order is now:
+1. the link ""minor edit"" beside the 'minor edit' checkbox.
+2. ""Save Page"" button
+3. ""Review your changes"" button
+Then three tabs for the links in the footer of this windows.
+
+Tabbing to the _link_ ""minor edit"" is a bug in the current implementation.
+
+Unless there is a good reason to do otherwise, the tab order should be the same as the source editor (muscle memory).  See also bug 51918 for a tab order request.",1374818669,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,Fixed and will get deployed in a few minutes.,1374677090,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Change 75594 merged by jenkins-bot:
+Make ButtonWidgets more accessible
+
+https://gerrit.wikimedia.org/r/75594",1374676838,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Patch above should fix original bug. Issue of tabbing from surface to 'Save page' is also partly fixed, but because of DOM order you have to shift+tab. If we want to switch these round, please open a new bug.",1374673879,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"Change 75594 had a related patch set uploaded by Esanders:
+Makes ButtonWidgets more accessible
+
+https://gerrit.wikimedia.org/r/75594",1374673699,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"There seem to be two distinct requests:
+
+* getting from the editing ""surface area"" to the edit summary input (with a tab key?)
+
+* getting from the edit summary input to the save page or review changes buttons (with a tab key)",1374631796,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"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.",1374631714,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,*** Bug 51918 has been marked as a duplicate of this bug. ***,1374630794,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,*** Bug 51913 has been marked as a duplicate of this bug. ***,1374624457,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"It's not really an enhancement, since it is preventing proper accessibility. But so long as it is looked at and fixed, that's what really matters :)",1373244830,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Dialog/flyout buttons cannot be activated with Tab key,"attr( { role: 'button', tabIndex: 0 } ) and add return keypress events to all of them.
+
+Also dialogs should have role = dialog and buttons that pop up dialogs should have  aria-haspopup",1373229137,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-jxas3inmlw4l4tcg6zyx,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371982260,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-batdg3q5jwk7z4eeddgg,task_description,declined
+VisualEditor: Right-click in IE10 causes deletion of the selected content,Totally conceivable that we fixed this in the past 15 months with the thousands of other changes (3683 since this point by my count). Marking as WORKSFORME.,1409959799,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,I can't reproduce this in IE10.,1409958482,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,"(In reply to This, that and the other (TTO) from comment #2)
+> Does not occur in IE11. Has an official decision been made on whether to
+> support IE <= 10?
+
+The ambition is to support IE9 and up; IE10 doesn't add much compared to IE9, but is probably a necessary stepping-stone. If it turns out to be too much work, we'll abandon efforts, but for now, yes, this is on the worklist.",1409441520,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,Does not occur in IE11. Has an official decision been made on whether to support IE <= 10?,1409383011,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Right-click in IE10 causes deletion of the selected content,(Does this also apply to the first comment here? :) ),1377104512,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-batdg3q5jwk7z4eeddgg,task_subcomment,NA
+VisualEditor: Transclusion editor broken in IE10 (stack overflow),"In IE10, any attempt to open the transclusion editor leads to a stack overflow. 
+
+In the dev console I get this:
+
+--- 
+SCRIPT28: Out of stack space 
+load.php, line 46 character 700 [this location is different every time]
+
+SCRIPT5: Access is denied.
+load.php, line 305 character 273
+
+SCRIPT5: Access is denied.
+load.php, line 305 character 273
+
+SCRIPT5: Access is denied.
+load.php, line 305 character 273 
+[... ad infinitum]
+
+SCRIPT2343: Stack overflow at line: 46 [different every time]
+
+SCRIPT5: Access is denied.
+load.php, line 305 character 273
+---
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371982020,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-2go6ew7f46vsl6ngyy7w,task_description,resolved
+VisualEditor: Transclusion editor broken in IE10 (stack overflow),This doesn't happen in IE10 with master.,1409958003,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2go6ew7f46vsl6ngyy7w,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"1. Use Chrome 27 to edit [[Pancytopenia#External links]] in VE
+2. Try to cut the {{Commons category}} template (using Ctrl+X/Cmd+X or right click/Cut)
+
+The browser tab crashes.
+
+Seen on Windows and Mac.
+
+No idea how to find any debugging info about the crash.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371979920,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-6doqtsezbhohs5na7asr,task_description,resolved
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,Fixed in master; will be deployed on Thursday as part of the regular push.,1377632908,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"Change 81280 merged by jenkins-bot:
+Don't render <meta>/<link>/<style> tags in GeneratedContentNode
+
+https://gerrit.wikimedia.org/r/81280",1377628116,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"Change 81280 had a related patch set uploaded by Catrope:
+Don't render <meta>/<link>/<style> tags in GeneratedContentNode
+
+https://gerrit.wikimedia.org/r/81280",1377627560,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"Since <link> and <style> don't render in a useful way in the DOM (if they would ever be in wikitext, they'd be exported to VE as generated content or some other special thing that we can visualise and edit through an inspector or dialog)..
+
+It is fixed in Chromium 30.
+
+Updated summary to mention Chromium, not Chrome. This is likely affecting Opera 15 as well, for example.
+
+Since we don't want to 2 weeks for this to land in stable, and we can safely strip these out before we render them in CE in the first place, let's do that.",1375420043,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I think this is the patch that fixed it in Chrome 30:
+
+https://codereview.chromium.org/14995014
+https://trac.webkit.org/changeset/150402
+
+Which would mean that this is the upstream bug: 
+
+http://code.google.com/p/chromium/issues/detail?id=177470
+https://bugs.webkit.org/show_bug.cgi?id=116479",1375417683,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"(In reply to comment #13)
+> @Tim: Which chromium version is the stacktrace from?
+
+It's the Ubuntu package version 28.0.1500.71-0ubuntu1.12.04.1",1375395098,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I can still reproduce this on https://en.wikipedia.org/wiki/Pancytopenia?veaction=edit#External_links with Chrome 28 (stable channel).
+
+However when testing on Chrome 30 (dev channel), I can no longer reproduce this.
+
+Confirmed that removing the [
+<link rel=​""mw:​WikiLink/​Category"" href=​""./​Category:​Commons_category_without_a_link_on_Wikidata"" data-parsoid=​""{""stx"":​""simple"",""a"":​{""href"":​""./​Category:​Commons_category_without_a_link_on_Wikidata""}​,""sa"":​{""href"":​""Category:​Commons category without a link on Wikidata""}​}​"" about=​""#mwt7"">​
+] tag from the {{commonscat}} template before cutting, prevents the crash.
+
+
+@Tim: Which chromium version is the stacktrace from?
+
+Filed upstream: https://code.google.com/p/chromium/issues/detail?id=267059",1375386614,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I'll try to isolate this to produce a minimal test case, see how we can work around it in VE, and report it to the Chrome people. It's not acceptable for a browser to segfault even on invalid HTML.",1375373236,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,The node variable in frame 3 of my backtrace is indeed a <link> element.,1375349187,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"It seems that this bug has to do with link html tag.
+
+In both examples (Pancytopenia and Lumpectomy) if I delete <link> node (using debug tools) from inside (in second example it is not a direct child) of the node to cut then when I'm cutting it browser tab does not crash anymore.
+
+Based on the w3c documentation it seems to me that we are using link tag incorrectly - value of attribute ""rel"" should be one of the values listed here http://www.w3schools.com/tags/tag_link.asp but in our case it is ""mw:WikiLink/Category"".
+
+In case of templates in VE we are simply rendering HTMLDOM that we are getting from Parsoid, so fixing it in Parsoid (not using link tag incorrectly) should solve this problem. (I'm making some assumptions here - it should be verified first in some sort of isolation - jsfiddle.)
+
+For now as a quick fix we can strip all link nodes when we are rendering template in the VE.",1375342206,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I think this is probably the most important bug in VE at the moment, and it's sad to see no progress being made on it, so I got a backtrace from stock Chromium in Ubuntu 12.04:
+
+Program received signal SIGSEGV, Segmentation fault.
+[Switching to Thread 0x7fffcd87e700 (LWP 2767)]
+WebCore::AppendNodeCommand::AppendNodeCommand (this=0x14b6f1e5eea0, parent=..., node=...)
+    at third_party/WebKit/Source/core/editing/AppendNodeCommand.cpp:39
+39	third_party/WebKit/Source/core/editing/AppendNodeCommand.cpp: No such file or directory.
+(gdb) bt
+#0  WebCore::AppendNodeCommand::AppendNodeCommand (this=0x14b6f1e5eea0, parent=..., node=...)
+    at third_party/WebKit/Source/core/editing/AppendNodeCommand.cpp:39
+#1  0x000055555752af66 in create (node=..., parent=...)
+    at third_party/WebKit/Source/core/editing/AppendNodeCommand.h:37
+#2  WebCore::CompositeEditCommand::appendNode (this=0x14b6f44c0800, node=..., parent=...)
+    at third_party/WebKit/Source/core/editing/CompositeEditCommand.cpp:372
+#3  0x0000555557535512 in WebCore::DeleteSelectionCommand::makeStylingElementsDirectChildrenOfEditableRootToPreventStyleLoss (this=0x14b6f44c0800) at third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp:431
+#4  0x0000555557538582 in WebCore::DeleteSelectionCommand::handleGeneralDelete (this=0x14b6f44c0800)
+    at third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp:445
+#5  0x000055555753a2e5 in WebCore::DeleteSelectionCommand::doApply (this=0x14b6f44c0800)
+    at third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp:836
+#6  0x00005555575273d2 in WebCore::CompositeEditCommand::apply (this=0x14b6f44c0800)
+    at third_party/WebKit/Source/core/editing/CompositeEditCommand.cpp:202
+#7  0x000055555725c6f4 in deleteSelectionWithSmartDelete (smartDelete=false, this=<optimized out>)
+    at third_party/WebKit/Source/core/editing/Editor.cpp:340
+#8  WebCore::Editor::deleteSelectionWithSmartDelete (this=<optimized out>, smartDelete=false)
+    at third_party/WebKit/Source/core/editing/Editor.cpp:335
+#9  0x000055555726498a in WebCore::Editor::cut (this=0x14b6f2019180)
+    at third_party/WebKit/Source/core/editing/Editor.cpp:982
+#10 0x000055555726c08f in executeCut (frame=0x14b6f2d5cc00, source=<optimized out>)
+    at third_party/WebKit/Source/core/editing/EditorCommand.cpp:301
+#11 WebCore::executeCut (frame=0x14b6f2d5cc00, source=<optimized out>)
+    at third_party/WebKit/Source/core/editing/EditorCommand.cpp:297
+#12 0x00005555569cd7ee in WebKit::WebFrameImpl::executeCommand (this=0x14b6f2d7ca80, name=..., value=...)
+    at third_party/WebKit/Source/WebKit/chromium/src/WebFrameImpl.cpp:1243
+#13 0x00005555583d50e1 in content::RenderViewImpl::handleCurrentKeyboardEvent (this=<optimized out>)
+    at content/renderer/render_view_impl.cc:2201
+#14 0x0000555556a155ba in WebKit::EditorClientImpl::handleKeyboardEvent (this=0x14b6f2bd45a0, evt=0x14b6f379f700)
+    at third_party/WebKit/Source/WebKit/chromium/src/EditorClientImpl.cpp:643
+#15 0x00005555573f9d13 in WebCore::EventHandler::defaultKeyboardEventHandler (this=0x14b6f1464c80, 
+    event=0x14b6f379f700) at third_party/WebKit/Source/core/page/EventHandler.cpp:3121
+#16 0x0000555556acdad8 in WebCore::Node::defaultEventHandler (this=0x14b6f40364e0, event=0x14b6f379f700)
+    at third_party/WebKit/Source/core/dom/Node.cpp:2546
+---Type <return> to continue, or q <return> to quit---
+#17 0x0000555556b13822 in dispatchEventPostProcess (preDispatchEventHandlerResult=0x0, this=0x7fffcd87bdb0)
+    at third_party/WebKit/Source/core/dom/EventDispatcher.cpp:208
+#18 WebCore::EventDispatcher::dispatch (this=0x7fffcd87bdb0)
+    at third_party/WebKit/Source/core/dom/EventDispatcher.cpp:127
+#19 0x0000555556b1337e in WebCore::EventDispatcher::dispatchEvent (node=<optimized out>, mediator=...)
+    at third_party/WebKit/Source/core/dom/EventDispatcher.cpp:56
+#20 0x0000555556ace21b in WebCore::Node::dispatchEvent (this=0x14b6f40364e0, event=...)
+    at third_party/WebKit/Source/core/dom/Node.cpp:2426
+#21 0x0000555556abd15d in WebCore::EventTarget::dispatchEvent (this=0x14b6f40364e0, event=..., ec=<optimized out>)
+    at third_party/WebKit/Source/core/dom/EventTarget.cpp:148
+#22 0x00005555573fc181 in WebCore::EventHandler::keyEvent (this=0x14b6f1464c80, initialKeyEvent=...)
+    at third_party/WebKit/Source/core/page/EventHandler.cpp:3006
+#23 0x00005555569f3ccb in WebKit::WebViewImpl::handleKeyEvent (this=0x14b6f2bd4500, event=...)
+    at third_party/WebKit/Source/WebKit/chromium/src/WebViewImpl.cpp:987
+#24 0x00005555569f743b in WebKit::WebViewImpl::handleInputEvent (this=0x14b6f2bd4500, inputEvent=...)
+    at third_party/WebKit/Source/WebKit/chromium/src/WebViewImpl.cpp:2024
+#25 0x00005555583f92b3 in content::RenderWidget::OnHandleInputEvent (this=0x14b6f2b41000, 
+    input_event=0x14b6f38f7898, is_keyboard_shortcut=true) at content/renderer/render_widget.cc:756
+#26 0x00005555583f7c5e in DispatchToMethod<content::RenderWidget, void (content::RenderWidget::*)(WebKit::WebInputEvent const*, bool), WebKit::WebInputEvent const*, bool> (method=<optimized out>, obj=0x14b6f2b41000, arg=...)
+    at ./base/tuple.h:553
+#27 Dispatch<content::RenderWidget, content::RenderWidget, void (content::RenderWidget::*)(WebKit::WebInputEvent const*, bool)> (func=
+    (void (content::RenderWidget::*)(content::RenderWidget * const, const WebKit::WebInputEvent *, bool)) 0x5555583f90e0 <content::RenderWidget::OnHandleInputEvent(WebKit::WebInputEvent const*, bool)>, obj=0x14b6f2b41000, msg=
+    0x14b6f38d9f88, sender=<optimized out>) at ./content/common/input_messages.h:39
+#28 content::RenderWidget::OnMessageReceived (this=0x14b6f2b41000, message=...)
+    at content/renderer/render_widget.cc:311
+#29 0x00005555583ed784 in content::RenderViewImpl::OnMessageReceived (this=0x14b6f2b41000, message=...)
+    at content/renderer/render_view_impl.cc:1124
+#30 0x00005555566c8fa8 in content::MessageRouter::RouteMessage (this=<optimized out>, msg=...)
+    at content/common/message_router.cc:49
+#31 0x0000555556651a8b in OnMessageReceived (msg=..., this=0x14b6f14bcb88) at content/common/child_thread.cc:271
+#32 content::ChildThread::OnMessageReceived (this=0x14b6f14bcb88, msg=...) at content/common/child_thread.cc:236
+---Type <return> to continue, or q <return> to quit---
+#33 0x00005555566280ba in IPC::ChannelProxy::Context::OnDispatchMessage (this=0x14b6f14bde00, message=...)
+    at ipc/ipc_channel_proxy.cc:261
+#34 0x0000555556296fae in Run (this=0x7fffcd87d958) at ./base/callback.h:396
+#35 base::MessageLoop::RunTask (this=0x7fffcd87da50, pending_task=...) at base/message_loop.cc:484
+#36 0x000055555629a70b in base::MessageLoop::DeferOrRunPendingTask (this=0x7fffcd87da50, pending_task=...)
+    at base/message_loop.cc:496
+#37 0x000055555629ad13 in DoWork (this=<optimized out>) at base/message_loop.cc:688
+#38 base::MessageLoop::DoWork (this=0x7fffcd87da50) at base/message_loop.cc:667
+#39 0x000055555629b459 in base::MessagePumpDefault::Run (this=0x14b6f149b7e0, delegate=0x7fffcd87da50)
+    at base/message_pump_default.cc:29
+#40 0x00005555562aa202 in base::RunLoop::Run (this=0x7fffcd87da10) at base/run_loop.cc:45
+#41 0x0000555556296444 in base::MessageLoop::Run (this=<optimized out>) at base/message_loop.cc:321
+#42 0x00005555562bb330 in base::Thread::ThreadMain (this=0x14b6f14a45a0) at base/threading/thread.cc:197
+#43 0x00005555562b8001 in base::(anonymous namespace)::ThreadFunc (params=0x14b6f0a23650)
+    at base/threading/platform_thread_posix.cc:95
+#44 0x00007ffff3df9e9a in start_thread (arg=0x7fffcd87e700) at pthread_create.c:308
+#45 0x00007ffff1ef0ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
+#46 0x0000000000000000 in ?? ()
+(gdb) info locals
+No locals.
+(gdb) up
+#1  0x000055555752af66 in create (node=..., parent=...)
+    at third_party/WebKit/Source/core/editing/AppendNodeCommand.h:37
+37	third_party/WebKit/Source/core/editing/AppendNodeCommand.h: No such file or directory.
+(gdb) info locals
+No locals.
+(gdb) up
+#2  WebCore::CompositeEditCommand::appendNode (this=0x14b6f44c0800, node=..., parent=...)
+    at third_party/WebKit/Source/core/editing/CompositeEditCommand.cpp:372
+372	third_party/WebKit/Source/core/editing/CompositeEditCommand.cpp: No such file or directory.
+(gdb) info locals
+No locals.
+(gdb) up
+#3  0x0000555557535512 in WebCore::DeleteSelectionCommand::makeStylingElementsDirectChildrenOfEditableRootToPreventStyleLoss (this=0x14b6f44c0800) at third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp:431
+431	third_party/WebKit/Source/core/editing/DeleteSelectionCommand.cpp: No such file or directory.
+(gdb) info locals
+rootEditableElement = {m_ptr = 0x0}
+nextNode = {m_ptr = 0x14b6f3107ee0}
+range = {m_ptr = 0x14b6f3e7f980}
+node = {m_ptr = 0x14b6f2d83180}",1375340841,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I experienced this on [[Narayana_Gosain_Temple]] which cutting '==References==\n{{reflist}}\n"", which may have also cut ""{{coord missing|Odisha}}"" which follows it.",1374545513,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"**ajc11123** wrote:
+
+I experience the same bug on Chrome 28.  Chrome crashes (displaying its characteristic ""Aw snap"" error page) when I try to cut certain templates, notably {{citation needed}}, {{who}}, and other in-line templates.  This does not happen with copying.  In addition, I could not reproduce the bug in my own userspace, only in article space.",1374110009,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"This also happens on Chrome 28 with reference blocks, looks like. Not sure if the same problem - try cutting the ref block on https://en.wikipedia.org/wiki/Lumpectomy",1374082463,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"It seems when I put a breakpoint in onCut and onCopy and step through slowly, it doesn't crash.",1374070133,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"I don't think I manage to remove templates only with CTRL-X, but if I select some text along and then try to cut, Chrome's tab will crash as well.",1373664045,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"**bi.llybob** wrote:
+
+Also crashes when I try to cut multiple templates in Chrome. For example, if I select the two hatnotes at the top of https://en.wikipedia.org/wiki/Mauritius",1373171102,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"**bi.llybob** wrote:
+
+(Chrome 27, Windows) I can't seem to text-select the template, and don't see ""Cut"" on the right-click menu when the cursor is over the template. However, I do get an error tone when I select the template and press Ctrl-X.",1373171014,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>,"The content makes its way into the clipboard, but yes, I can reproduce.",1372006216,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6doqtsezbhohs5na7asr,task_subcomment,NA
+Parsoid: External links are double encoded,"Intended edit (ve-edit + fixup):
+
+https://www.mediawiki.org/w/index.php?title=Wikimedia_technical_search&diff=715707&oldid=715705
+
+-  [https://github.com/search?l=&q=wgWellFormedXml+%40wikimedia Search]
++  [https://github.com/search?l=&q=ResourceLoader+%40wikimedia Search]
+
+Actual edit saved by Parsoid/VisualEditor:
+
+
+https://www.mediawiki.org/w/index.php?title=Wikimedia_technical_search&diff=715706&oldid=715705
+
+-  [https://github.com/search?l=&q=wgWellFormedXml+%40wikimedia Search]
++  [https://github.com/search?l=&q=ResourceLoader+%2540wikimedia Search]
+
+
+Note how the % got encoded to %25.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371979620,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_description,resolved
+Parsoid: External links are double encoded,"We might later want to prettify the percent encoding. Basically decode everything but some vital percent-encoded values ([%? ], probably more). But for now this is fixed.",1372442702,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_subcomment,NA
+Parsoid: External links are double encoded,"Change 71082 merged by jenkins-bot:
+Bug 50042: Don't percent-encode modified external link hrefs
+
+https://gerrit.wikimedia.org/r/71082",1372442139,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_subcomment,NA
+Parsoid: External links are double encoded,"Change 71082 had a related patch set uploaded by GWicke:
+Bug 50042: Don't percent-encode modified external link hrefs
+
+https://gerrit.wikimedia.org/r/71082",1372441280,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_subcomment,NA
+Parsoid: External links are double encoded,"Looks like a Parsoid bug. Works fine when data-parsoid is present, but for new annotations URLs are encoded.
+
+<a rel=""mw:ExtLink"" href=""https://github.com/search?l=&amp;q=ResourceLoader+%40wikimedia"">Search</a>
+
+serialises to:
+
+[https://github.com/search?l=&q=ResourceLoader+%2540wikimedia Search]",1372252496,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-p2hyhzwp54l6ohsbe4j4,task_subcomment,NA
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"Screenshot
+
+I am unable to insert a media with a given file name from Commons.
+
+Neither
+
+File:Kölnisches Stadtmuseum - 125 x gekauft - geschenkt - gestiftet-1120.jpg
+
+nor
+
+Kölnisches Stadtmuseum - 125 x gekauft - geschenkt - gestiftet-1120.jpg
+
+is accepted (and any other file name)
+
+The ""insert media"" button is still inactive, see screenhot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11348}",1371909840,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-3nquleh2aykawirbt4st,task_description,declined
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"Unable to replicate this bug in CirrusSearch. As we're in the process of migrating from Lucene to CirrusSearch, I'm marking this bug as RESOLVED WONTFIX.",1392141824,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-3nquleh2aykawirbt4st,task_subcomment,NA
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"Searching without the dashes finds the document.  Looks like -XXX excludes all matches with XXX.  I'd advise removing the dashes, at least for now.",1376493859,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-3nquleh2aykawirbt4st,task_subcomment,NA
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"Still an issue. Trying to add [[Commons:File:Kölner Dom - Abbau südöstliches Gerüst Nordturm-2933.jpg]] to [[de:Traverse (mechanischer Träger)]].
+
+This is really annoying. Makes testing the VE impossible :-(",1374756848,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-3nquleh2aykawirbt4st,task_subcomment,NA
+Search for filename with dashes on Commons does not return said file (seems to exclude string after dash),"This is… exceptionally odd. VisualEditor is just using the built-in search system from the cluster, and as you can see your image doesn't come up with that (or several sub-strings of that) as the search string:
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=K%C3%B6lnisches%20Stadtmuseum%20-%20125%20x%20gekauft%20-%20geschenkt%20-%20gestiftet-1120.jpg&fulltext=Search&profile=images&redirs=1
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=K%C3%B6lnisches%20Stadtmuseum%20-%20125%20x%20gekauft%20-%20geschenkt%20-%20gestiftet-1120&fulltext=Search&profile=images&redirs=1
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=K%C3%B6lnisches%20Stadtmuseum%20-%20125%20x%20gekauft%20-%20geschenkt%20-%20gestiftet-1120&fulltext=Search&profile=images&redirs=1
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=geschenkt%20-%20gestiftet-1120&fulltext=Search&profile=images&redirs=1
+
+Interestingly, it does come up under:
+
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=gestiftet-1120&fulltext=Search&profile=images&redirs=1",1373156554,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3nquleh2aykawirbt4st,task_subcomment,NA
+"VisualEditor: Consecutive images align incorrectly in ""edit"" mode and cannot be modified","See, for example, https://en.wikipedia.org/wiki/Kaveri_River
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371896520,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-isttvrxbjpvgt5itwu5n,task_description,resolved
+"VisualEditor: Consecutive images align incorrectly in ""edit"" mode and cannot be modified","This is a very odd bug that appears to be due to an old mis-cached version of the Parsoid result (it was marking each of the images as about=""null""); we've flushed the caches, and it no longer appears AFAICT. Please re-open if it recurs.",1371972536,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-isttvrxbjpvgt5itwu5n,task_subcomment,NA
+VisualEditor: Thumbnailed images without descriptions get pipes added on edit,"Compare https://en.wikipedia.org/w/index.php?title=User:Edgepedia/sandbox3&diff=prev&oldid=560957268 to https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2Fsandbox3&diff=560957359&oldid=560957268
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371895500,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mnsdqy6zrnvlm2uqkhcw,task_description,resolved
+VisualEditor: Thumbnailed images without descriptions get pipes added on edit,"Fixed (I think) in gerrit 70357 which we've just deployed - if we get a repeat, please re-open.",1372124850,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mnsdqy6zrnvlm2uqkhcw,task_subcomment,NA
+VisualEditor: Thumbnailed images without descriptions get pipes added on edit,*** Bug 50116 has been marked as a duplicate of this bug. ***,1372096490,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mnsdqy6zrnvlm2uqkhcw,task_subcomment,NA
+VisualEditor: Thumbnailed images without descriptions get pipes added on edit,"Inez is already working on this, but I don't think we have a bug for it?",1372017842,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mnsdqy6zrnvlm2uqkhcw,task_subcomment,NA
+Images not displayed in latest VE deployment,"I hope this is a false alarm... but it seems to be real.
+
+Compare [[Locomotive]] (images visible - en is currently on 1.22wmf7) with [[testwiki:VisualEditor:Locomotive]] (no images - test is on 1.22wmf8).
+
+Seen on Firefox latest and Chrome latest.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1371887280,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-ffl4fedejvxwcxttjfil,task_description,resolved
+Images not displayed in latest VE deployment,"Aha, I can now reproduce on that link - and looking at the HTML we get back from Parsoid, the first image comes back as
+
+<meta typeof=""mw:Placeholder"" data-parsoid='{""src"":""[[File:Net.jpg|thumb]]"",""optList"":[{""ck"":""thumbnail"",""ak"":""thumb""}],""dsr"":[0,22,null,null]}'>
+
+… and so VisualEditor dutifully doesn't display an image. Marking as a duplicate of the Parsoid bug, even though that is higher-numbered. Sorry about this. :-(
+
+*** This bug has been marked as a duplicate of bug 50035 ***",1372003922,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ffl4fedejvxwcxttjfil,task_subcomment,NA
+Images not displayed in latest VE deployment,"It seems to be mostly working again, although I couldn't see any images just a few hours ago. 
+
+I still can't see the first image on [[testwiki:Net]]. This just may be the Parsoid cache though.",1371970998,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-ffl4fedejvxwcxttjfil,task_subcomment,NA
+Images not displayed in latest VE deployment,"(In reply to comment #1)
+> … with what browser …
+
+And, of course, you told me that. Sorry! :-( Can't reproduce on latest master or in latest push of wmf8.",1371970401,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ffl4fedejvxwcxttjfil,task_subcomment,NA
+Images not displayed in latest VE deployment,"I'm afraid I can't reproduce this - was this a transient issue, or do you still get it, and if so, with what browser, and are there any error messages on the console?",1371970022,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ffl4fedejvxwcxttjfil,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Currently scheduled for w/c 15 July. It's anticipated that this will not be possible for some wikis due to failings in VisualEditor and/or Parsoid; exact list to be determined closer to the time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51792
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33126
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33077
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52202",1371860160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_description,resolved
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","(In reply to comment #14)
+> (In reply to comment #13)
+> > The patch was committed and merged (but the notification bot incorrectly
+> > reset the status), so I'm setting this back to FIXED again as the original
+> > request that this bug report is about (see subject line) has been fulfilled.
+> 
+> I'm not sure the original request (""top 15"" Wikipedias) has been fulfilled,
+> but I'm also not sure that's still the goal. I'll leave this bug to James to
+> sort out.
+
+Re-titled for clarity. I feel that this is closed.",1375125139,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Change 76199 merged by jenkins-bot:
+Enable anonymous use of VisualEditor on es/fr/he/it/pl/ru/sv
+
+https://gerrit.wikimedia.org/r/76199",1375115804,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","(In reply to comment #13)
+> The patch was committed and merged (but the notification bot incorrectly
+> reset the status), so I'm setting this back to FIXED again as the original
+> request that this bug report is about (see subject line) has been fulfilled.
+
+I'm not sure the original request (""top 15"" Wikipedias) has been fulfilled, but I'm also not sure that's still the goal. I'll leave this bug to James to sort out.",1375115210,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","The patch was committed and merged (but the notification bot incorrectly reset the status), so I'm setting this back to FIXED again as the original request that this bug report is about (see subject line) has been fulfiled.
+Note that this is not any kind of statement refering to bug 52202, it's just to reflect the current situation. For the German Wikipedia deployment, please refer to bug 52202 instead. Thanks!",1375105856,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","**wikipedia** wrote:
+
+(In reply to comment #11)
+> They more than likely mean all the major bugs that cause issues with editing
+> (eg: dirty diffs, randomly inserting pawns to name two)
+
+Exactly, thank you for clarification.",1375089579,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","(In reply to comment #10)
+> (In reply to comment #8)
+> > 3) VE to be opt-in only until all bugs are fixed: 430 votes (!)
+> 
+> Personal opinion: I am not aware of a single software that is proven to be
+> completely bug-free. This is an impossible requirement that cannot be
+> fulfiled.
+
+They more than likely mean all the major bugs that cause issues with editing (eg: dirty diffs, randomly inserting pawns to name two)",1375085597,PHID-USER-hwuumsjqciw7ji5qhpc7,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","(In reply to comment #8)
+> 3) VE to be opt-in only until all bugs are fixed: 430 votes (!)
+
+Personal opinion: I am not aware of a single software that is proven to be completely bug-free. This is an impossible requirement that cannot be fulfiled.",1375085393,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)",bug 52202 has been created based on the German Wikipedia poll.,1375058081,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","**wikipedia** wrote:
+
+In the quick poll (see #7) the results at the moment are as following:
+
+1) enabeling VE as default for all users: 21 votes
+2) VE as default for logged-in users: 6 votes
+3) VE to be opt-in only until all bugs are fixed: 430 votes (!)
+4) enabeling VE under another link name (suggestion was ""Visual Editor (beta)"" instead of ""Bearbeiten"" (""edit"")): 31 votes
+
+According to this large majority of users who oppose defaulting VE by tomorrow, I hereby ask you to put VE back to opt-in for logged-in users until the most important bugs are fixed. Thank you.",1375045061,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","the German wikipedia just started a quick poll over the weekend to at least postpone this activation for anonymous users on monday:
+
+https://de.wikipedia.org/wiki/Wikipedia:Umfragen/VisualEditor_Opt-in
+
+the poll has currently also a option for the previous state where VE was Opt-in for users instead of Opt-out if this is still possible.
+
+It would be appreciated to take the outcome on monday into account and postpone this activation for dewiki if desired.",1374879438,PHID-USER-jcypqodpdpbcicgwgh7j,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)",It's unclear whether the German Wikipedia wants this: <http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070807.html>.,1374874055,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Change 76199 had a related patch set uploaded by Jforrester:
+Enable anonymous use of VisualEditor on de/es/fr/he/it/pl/ru/sv
+
+https://gerrit.wikimedia.org/r/76199",1374873719,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)",This is now done.,1374685783,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Change 75543 merged by jenkins-bot:
+VisualEditor into beta on de/es/fr/he/it/pl/ru/svwiki for logged-in only
+
+https://gerrit.wikimedia.org/r/75543",1374685596,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","Change 75543 had a related patch set uploaded by Jforrester:
+VisualEditor into beta on de/es/fr/he/it/pl/ru/svwiki
+
+https://gerrit.wikimedia.org/r/75543",1374631008,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+"Enable VisualEditor by default for phase 2 Wikipedias (selected from the ""top 10""-ish)","According to [[meta:Tech/News/2013/30]] the list is:
+German  (de), 
+Spanish (es), 
+French  (fr), 
+Hebrew  (he) - RTL, 
+Italian (it), 
+Dutch   (nl), 
+Polish  (pl), 
+Russian (ru) and 
+Swedish (sv).",1374489687,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-o3inw6vkpkuhjrfly4eb,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Currently scheduled for w/c 1 July.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371860100,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-algalgsjyyisq2anwhms,task_description,resolved
+Enable VisualEditor by default for all users of the English Wikipedia,This is now complete.,1373921229,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Change 73852 merged by jenkins-bot:
+Stop the prevention of anons getting VisualEditor for enwiki
+
+https://gerrit.wikimedia.org/r/73852",1373921102,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Change 73852 had a related patch set uploaded by Jforrester:
+Stop the prevention of anons getting VisualEditor for enwiki
+
+https://gerrit.wikimedia.org/r/73852",1373917817,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Now done for logged-in users. Will be done for the rest next week, assuming all is well.",1372715482,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Change 71261 merged by jenkins-bot:
+Enable VisualEditor for all logged-in users (but not anons) on enwiki
+
+https://gerrit.wikimedia.org/r/71261",1372714320,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,"Change 71261 had a related patch set uploaded by Jforrester:
+Enable VisualEditor for all logged-in users of the English Wikipedia
+
+https://gerrit.wikimedia.org/r/71261",1372561707,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor by default for all users of the English Wikipedia,… with 'all users' (logged in and otherwise) for w/c 8 July.,1371860183,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-algalgsjyyisq2anwhms,task_subcomment,NA
+Enable VisualEditor experimental mode on test* wikis as well as MW.org and Beta Labs,"After spending some time with VE in our various test environments, it would be convenient to have all features available in VE available in all of our test environments.  Right now it is possible to create citations in mediawiki.org but not in test2wiki, and VE in beta labs is not usable at all. 
+
+test2wiki gives us a production wiki where it is possible to make destructive or nonsense edits that are not welcome on mediawiki.org
+
+beta labs gives us an environment to test possibly risky merged changes that are not yet deployed
+
+Enabling all of VE features in all test environments would be useful for testing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49703",1371827040,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-kd62lmqw7ntjvcrqwhvx,task_description,resolved
+Enable VisualEditor experimental mode on test* wikis as well as MW.org and Beta Labs,"Change 70440 abandoned by Cmcmahon:
+Enable VE experimental mode on test2wiki per Bug 49963
+
+Reason:
+overtaken by history
+
+https://gerrit.wikimedia.org/r/70440",1372864721,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kd62lmqw7ntjvcrqwhvx,task_subcomment,NA
+Enable VisualEditor experimental mode on test* wikis as well as MW.org and Beta Labs,"VE seems to be working correctly now in beta labs, test2wiki, and mw.o
+
+Please re-open if you find otherwise.",1372377535,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-kd62lmqw7ntjvcrqwhvx,task_subcomment,NA
+Enable VisualEditor experimental mode on test* wikis as well as MW.org and Beta Labs,Related URL: https://gerrit.wikimedia.org/r/70440 (Gerrit Change I72b68e3e0db86eb5372cd303223ef8f81111271c),1372177710,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kd62lmqw7ntjvcrqwhvx,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"When editing a page which has an image with table data in its caption, the table is dropped (only its closing tab is kept). The rest of the caption is dropped as well.
+
+Test edit: https://hu.wikipedia.org/w/index.php?title=Vall%C3%A1s&diff=13696305&oldid=13696296
+
+You don't need to interact with the image in any way for this to happen, just edit the page, change anything and save.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://hu.wikipedia.org/wiki/Vall%C3%A1s?oldid=13696307
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61064",1371799080,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_description,resolved
+Images: wikitext tables inside image captions are lost,"Change 107172 merged by Subramanya Sastry:
+(Bug 49942) Tables can show up in image captions
+
+https://gerrit.wikimedia.org/r/107172",1389647113,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"Change 107172 had a related patch set uploaded by Subramanya Sastry:
+(Bug 49942) Tables can show up in captions
+
+https://gerrit.wikimedia.org/r/107172",1389631306,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934084,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"(In reply to comment #3)
+> (In reply to comment #2)
+> > If this image is not modified by the user it should still round-trip
+> > correctly,
+> > but on modification the table would be lost.
+> 
+> The table is lost even if the user does not interact with the image in any
+> way.
+>
+> See [[hu:Vallás]] - the image caption gets garbled as soon as you open the
+> article for editing.
+
+The corruption even if you don't touch it is a bug in VisualEditor related to munging the captions of images, which we're fixing today; sorry for that.",1372114586,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"(In reply to comment #2)
+> If this image is not modified by the user it should still round-trip
+> correctly,
+> but on modification the table would be lost.
+
+The table is lost even if the user does not interact with the image in any way. See [[hu:Vallás]] - the image caption gets garbled as soon as you open the article for editing.",1372114062,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"This is a tokenizer issue. The table is not tokenized as such, likely because syntax stops prevent a pipe from being matched.
+
+If this image is not modified by the user it should still round-trip correctly, but on modification the table would be lost.",1372105294,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+Images: wikitext tables inside image captions are lost,"Horrible, relatively-rare case for Parsoid, is the use of wikitext tables inside image captions. Currently, the following wikitext:
+
+[Start]
+[[Image:Foo.jpg|thumb|200px|This is an example image thumbnail caption with a table
+
+{|
+! Foo !! Bar
+|-
+| Foo1 || Bar1
+|-
+| Foo2 || Bar2
+|}
+
+… and some more text.]]
+[End]
+
+… turns into the following output from Parsoid:
+
+[Start]
+<figure typeof=""mw:Image/Thumb"" data-parsoid=""…"">
+  <a href=""./File:Foo.jpg"" data-parsoid=""…"">
+    <img resource=""./File:Foo.jpg"" src=""http://upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/200px-Foo.jpg""
+      height=""131"" width=""200"" data-parsoid=""…"">
+  </a>
+  <figcaption class=""mw-figcaption"" data-parsoid=""…"">}
+
+… and some more text.
+  </figcaption>
+</figure>
+[End]
+
+… whereas nominally it should be (generated using an HTML table rather than a wikitext one, which seems to work fine without DOM diffs from VE end):
+
+[Start]
+<figure typeof=""mw:Image/Thumb"" data-parsoid=""…"">
+  <a href=""./File:Foo.jpg"" data-parsoid=""…"">
+    <img resource=""./File:Foo.jpg"" src=""http://upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/200px-Foo.jpg""
+      height=""131"" width=""200"" data-parsoid=""…"">
+  </a>
+  <figcaption class=""mw-figcaption"" data-parsoid=""…"">This is an example image thumbnail caption with a table
+
+    <table data-parsoid=""…"">
+      <tbody data-parsoid=""…"">
+        <tr data-parsoid=""…"">
+          <th data-parsoid=""…"">Foo</th>
+           <th data-parsoid=""…"">Bar</th>
+        </tr>
+        <tr data-parsoid=""…"">
+          <td data-parsoid=""…"">Foo1</td>
+          <td data-parsoid=""…"">Bar1</td>
+        </tr>
+        <tr data-parsoid=""…"">
+          <td data-parsoid=""…"">Foo2</td>
+          <td data-parsoid=""…"">Bar2</td>
+        </tr>
+      </tbody>
+    </table>
+
+… and some more text.
+  </figcaption>
+</figure>
+[End]",1371999975,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5dgywim5ydcwu6b7g2zz,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"1. In VE, highlight some text and open the link inspector
+2. Type some characters into the textbox, but quickly click out of the link inspector before the autocomplete dropdown appears
+
+The dropdown appears in the top-left corner of the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371798960,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_description,resolved
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,Not completely fixed; see bug 51415.,1373936995,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,Fixed and will go out soon.,1373413695,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"Change 72849 merged by jenkins-bot:
+Be sure lookupMenu input is focused before showing
+
+https://gerrit.wikimedia.org/r/72849",1373412773,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"(Cite bug 51077 comment #0)
+> Created attachment bug 51077 12810 [details]
+> 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).",1373411632,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,*** Bug 51077 has been marked as a duplicate of this bug. ***,1373411601,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"Change 72849 had a related patch set uploaded by Robmoen:
+Be sure lookupMenu input is focused before showing inputMenu.
+
+https://gerrit.wikimedia.org/r/72849",1373408156,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"(This happens particularly often on Opera for me, by the way. I haven't yet investigated the issue.)",1373331336,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,"I am raising the severity on this, because it is not just a display bug, but also causes the intended link target to be ignored -- if the user confirms the link with enter, only the link title is used and the link target is quietly discarded.",1373331185,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing,Confirmed. This also happens if you type too quickly and press enter.,1372893436,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hk4qv3of7jiwnhul5ayb,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"1. Go to [[mw:VisualEditor:TTO]] and edit in VE
+2. Double-click on a link in order to select it, or drag-select the whole link
+3. Type a new link text
+
+Only the first character you type remains linked, instead of the whole text you type.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371793260,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_description,resolved
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"With bug 51463 closed, this is now complete. Marking as fixed.",1374771607,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,See bug 51463,1374001912,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"(In reply to comment #5)
+> That's all well and good, but now if my document ends in a link (a common
+> case if I link the last thing I typed) I can't put plain text after it, which
+> is the very reason we disabled trailing annotations for links in the first
+> place...
+
+You can - you just need to press the ""clear annotations"" button, or press return to get a new context with no pre-annotations. However, yes, these suck for discoverability. I think not-extending-over-whitespace is the best solution, though it's fiddly and difficult to support.",1373992527,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"That's all well and good, but now if my document ends in a link (a common case if I link the last thing I typed) I can't put plain text after it, which is the very reason we disabled trailing annotations for links in the first place...",1373992120,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"Change 73902 merged by jenkins-bot:
+Continue links
+
+https://gerrit.wikimedia.org/r/73902",1373934716,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"Change 73902 had a related patch set uploaded by Catrope:
+Continue links
+
+https://gerrit.wikimedia.org/r/73902",1373931509,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"I agree that this behaviour is not great for users; we should reverse the decision to abandon ""pre-annotation"" (that is, if you're typing, we'll apply the same formatting as the character immediately before the one you've just typed in the same paragraph) for links.
+
+Our concern was that having links always extent would be more tiresome for editors, which I still agree with, and that extending but not over whitespace would be confusing, which I think is arguable, but the current behaviour is worse.",1373155708,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users,"A related problem is, when you change only the first character of a link, that first letter is no longer part of the link. For example, if you change [[edinburgh]] to [[Edinburgh]], it becomes E[[dinburgh]].",1372852867,PHID-USER-6hxjlzg5h4uzsyxbsm43,False,PHID-TASK-4g3nhqcki5ifz5oczcu7,task_subcomment,NA
+"VisualEditor: Clicking outside the ""Describe what you changed"" box locks it","Steps to replicate:
+
+(1)Click ""Edit"" and make some change
+(2)Click ""Save page"". The cursor is now blinking in the ""Describe what you changed"" box.
+(3)Click on another dialogue box, such as the WP search box. The cursor now blinks there.
+(4) Click back into ""Describe what you changed"". Bupkis.
+
+Chrome 27.0.1453.116, Firefox 21.0, Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371789780,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-h5i7cqn2z7j4vdb2bioo,task_description,resolved
+"VisualEditor: Clicking outside the ""Describe what you changed"" box locks it",Bug fixed,1372006698,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-h5i7cqn2z7j4vdb2bioo,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"See screenshot, which is of https://en.wikipedia.org/wiki/Craig_Short - Firefox 21.0, Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371789480,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_description,resolved
+VisualEditor: Floated templates rendering oddly and overlapping text,Follow up:  https://en.wikipedia.org/wiki/Leo_Strauss?veaction=edit is still screwed up.,1384288678,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,Shall do.,1372613847,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"(In reply to comment #18)
+> Unless the patch hasn't been deployed yet, I guess.
+
+It hasn't. Deployed on Monday alongside the config change. Not sure if the example in comment 17 will be entirely fixed by it though - please check after release?",1372613728,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Unless the patch hasn't been deployed yet, I guess.",1372613000,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Crud
+
+It doesn't :(. See new screenshot.
+
+**Attached**: {F11120}",1372612962,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,*** Bug 50416 has been marked as a duplicate of this bug. ***,1372500786,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"The above patch fixes this bug, we believe. Marking as such.",1372463194,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Change 71109 merged by jenkins-bot:
+Stop floated transclusions floating out of themselves
+
+https://gerrit.wikimedia.org/r/71109",1372463162,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Change 71109 had a related patch set uploaded by Jforrester:
+Set renderHtmlAttributes to false, for both block and inline transclusions
+
+https://gerrit.wikimedia.org/r/71109",1372450916,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,*** Bug 50381 has been marked as a duplicate of this bug. ***,1372440083,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,+another example: https://en.wikipedia.org/wiki/Aranath?veaction=edit,1372440078,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"For some reason wrapper in which we put transclusions/templates gets HTML attributes of the transclusion/template carried over - including CSS classes - that should not happen, and wasn't happening in the past.
+
+I will investigate it, however adding Roan to this ticket, it seems like it is his area.",1372428523,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Screenshot
+
+This is likely a blocker for any beta rollout on Monday. I've attached a screenshot to show how bad it can get, and why :/.
+
+**Attached**: {F11119}",1372415006,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"(In reply to comment #4)
+> I thinks it depends on the skin: Monobook might be causing this.
+
+That's a different bug - created bug 50057.
+
+This is about CE's rendering of floated templates - I've attached some example screenshots to demonstrate.",1372005661,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12614
+what the template does look like when selected
+
+**Attached**: {F11118}",1372005619,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12613
+what the template does look like (once in VE)
+
+**Attached**: {F11117}",1372005597,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12612
+what the template should look like (read mode)
+
+**Attached**: {F11116}",1372005566,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,I thinks it depends on the skin: Monobook might be causing this.,1371986282,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"I don't think I can see your attachment, Oliver, but I think the bug may have to do with to these sshots, which both refer to adding a link: in the first one, the recycle bin can barely be seen as it gets hidden, the second one shows the link icon not being displayed as a square. Looks like this can happen both with Chrome and Firefox.",1371986068,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12609
+not displaying properly
+
+//attachment link icon not square.jpg ignored as obsolete//",1371985872,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+VisualEditor: Floated templates rendering oddly and overlapping text,"Created attachment 12608
+not displaying properly
+
+//attachment overlapping recycle bin.jpg ignored as obsolete//",1371985844,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-5pskpoilrrm4nns4zugy,task_subcomment,NA
+imageinfo API returns incorrect data,"In this call http://en.wikipedia.org/w/api.php?action=query&prop=imageinfo&titles=File%3APowderfinger-My_Happiness-23s.ogg&iiprop=size%7Curl&iiurlwidth=200 it returns thumbwidth=""1913"" thumbheight=""-1"" as a size of an thumb, which is completly wrong.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1371774060,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-dvy6cixcc2nxje733xv6,task_description,resolved
+imageinfo API returns incorrect data,"This backport is now live; as such, marking this bug as fixed.",1372722142,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,"Change 71393 merged by Catrope:
+Clean up transform dimension height handling
+
+https://gerrit.wikimedia.org/r/71393",1372706216,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,"Change 71393 had a related patch set uploaded by Catrope:
+Clean up transform dimension height handling
+
+https://gerrit.wikimedia.org/r/71393",1372706194,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,"(In reply to comment #2)
+> Related URL: https://gerrit.wikimedia.org/r/69869 (Gerrit Change
+> Ide7208394f8495f5b143cbba215d4645598f1a50)
+
+This has been merged, and went out with wmf9. However, given that wmf8 is on the servers for an extra week and it makes really not-nice behaviour in VisualEditor, we probably want to back-port this.",1372581138,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,Related URL: https://gerrit.wikimedia.org/r/69869 (Gerrit Change Ide7208394f8495f5b143cbba215d4645598f1a50),1371829144,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+imageinfo API returns incorrect data,"There are actually two bugs going on here.
+
+First, TimedMediaHandler isn't normalizing dimensions for audio files, which means that the height=-1 being passed to indicate ""don't limit by height"" is being misinterpreted.
+
+And second, TimedMediaHandler is using an incorrect calculation when the height is the limiting factor on the thumbnail dimensions, leading to the width of 1913. The same happens if you pass something like iiurlwidth=220&iiurlheight=10.
+
+Since both of these are in TimedMediaHandler, I'm going to reassign this there. I'll also submit a patch momentarily.",1371829089,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-dvy6cixcc2nxje733xv6,task_subcomment,NA
+VisualEditor: Miscellaneous <span> tags added,"See https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FMet&diff=560772671&oldid=560563847 for example; I have no idea why (problem with the template itself?)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371748980,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jm7w3nmu4dvvbq4cevqz,task_description,resolved
+VisualEditor: Miscellaneous <span> tags added,"I believe we have fixed this bug; if it recurs, please re-open.",1373056128,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jm7w3nmu4dvvbq4cevqz,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Two users have reported on this. 
+
+See:
+http://en.wikipedia.org/w/index.php?title=User:AussieLegend/Vandals_etc&diff=prev&oldid=560719781
+
+And:
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Font_colors_in_signatures_changed
+
+I realize that this is probably tied into other behavior, but I lack code-fu to determine what. :)
+
+Maggie
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42803",1371732540,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_description,resolved
+VisualEditor: <span> annotations next to each other aren't necessarily the same,Merged and will go out tomorrow.,1373852393,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Change 73523 merged by jenkins-bot:
+HACK: Don't merge adjacent annotations from Parsoid
+
+https://gerrit.wikimedia.org/r/73523",1373852315,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,*** Bug 51234 has been marked as a duplicate of this bug. ***,1373711757,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Change 73523 had a related patch set uploaded by Esanders:
+HACK: Don't merge adjacent annotations from Parsoid
+
+https://gerrit.wikimedia.org/r/73523",1373664173,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Adding Parsoid bug 42803 as a dependency. We do add nowiki between most cases of adjacent quotes to ensure at least correctness, but the markup will indeed not be optimal.",1373643542,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,*** Bug 50291 has been marked as a duplicate of this bug. ***,1373632745,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"All we need to do is turn off similar annotation comparisons in VE completely, but Parsoid is not ready for that yet, for example adding new bold text next to Parsoid-generated bold text would create:
+
+<b data=parsoid="""">Old bold text</b><b>New bold text from VE</b>
+
+which Parsoid should obviously merge to:
+
+'''Old bold textNew bold text from VE'''
+
+but doesn't yet.
+
+Once this is all handled correctly, we can turn off similar annotation comparisons and the two bolds in <b>Foo</b><b>Bar</b> will no longer be merged (as they have will have different data-parsoid's). Of course Parsoid will not want to merge them either so that will factor into their logic.",1373632309,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"(In reply to comment #6)
+> I still see annotation merging on this test case:
+> 
+> http://www.mediawiki.org/wiki/User:GWicke/TestDoubleFormatting?veaction=edit
+> 
+> Steps to reproduce:
+> 
+> * append a char to 'baz'
+> * preview the change
+> 
+> Result: The bold ranges are merged, leading to a dirty diff
+> Expected result: no merging and no dirty diff
+That should be the only remaining annotation merging issue. I've been meaning to file a bug about it but I keep forgetting.
+
+Ed, we need to preserve the difference between <b>Foo</b><b>Bar</b> and <b>FooBar</b> somehow. Feel free to hit me up on IRC if you want to talk about how we should do that.",1373576556,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"I still see annotation merging on this test case:
+
+http://www.mediawiki.org/wiki/User:GWicke/TestDoubleFormatting?veaction=edit
+
+Steps to reproduce:
+
+* append a char to 'baz'
+* preview the change
+
+Result: The bold ranges are merged, leading to a dirty diff
+Expected result: no merging and no dirty diff",1373575903,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"Several of these issues are actually on the VE side, so reopening.",1372735042,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"
+
+*** This bug has been marked as a duplicate of bug 48194 ***",1371814259,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"
+
+*** This bug has been marked as a duplicate of bug 42803 ***",1371813989,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"This is the same as bug 49478. We are dependent on it being in Parsoid first, otherwise we would reintroduce bug 48110.",1371812377,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: <span> annotations next to each other aren't necessarily the same,"In this case:
+
+  <span style=""color:green;"">Aussie</span><span style=""color:gold;"">Legend</span>
+
+… is being simplified by DM into:
+
+  <span style=""color:green;"">AussieLegend</span>
+
+… which, unsurprisingly, Parsoid assumes means we wanted to combine them. :-)",1371773903,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fhtlyq5kho6tpsip3niy,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,"Click ""add template"", then ""apply changes"" without adding a template (or add one, then remove it.
+
+Expected wikitext: none
+
+Actual wikitext: <span property=""mw:PageProp/noindex"" data-mw=""{&quot;parts&quot;:[]}""></span>
+
+We're clearly putting in a placeholder that we don't delete if the block is empty; because we don't display content blocks that don't render in read, you can't see these, which sucks and lets users do The Wrong Thing(tm).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371699420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-crkiryzxavcthffyf5za,task_description,resolved
+VisualEditor: Blank transclusion block doesn't get converted into blankness,"
+
+*** This bug has been marked as a duplicate of bug 49831 ***",1371744867,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-crkiryzxavcthffyf5za,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","Something's gone wrong with our PHP parser re-render call; on re-render of block templates only, you get {{template call|param}} rather than nice lovely HTML. Presumably something to do with our hack yesterday? Plzfixkthxbai.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371699120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w3m2d62g427w2i6vbyd4,task_description,resolved
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","(In reply to comment #7)
+> I'm not sure if this is the same bug, but English Wikipedia users report that
+> when editing an infobox piped wikilinks display as [[word|word]] rather than
+> as it will appear on save. It saves correctly.
+> 
+> I managed to replicate this. If this should be split off into another bug,
+> sorry!
+
+That's bug 50801 which we're working on right now; re-closing this one. No worries. :-)",1373555274,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","I'm not sure if this is the same bug, but English Wikipedia users report that when editing an infobox piped wikilinks display as [[word|word]] rather than as it will appear on save. It saves correctly.
+
+I managed to replicate this. If this should be split off into another bug, sorry!",1373555086,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)",*** Bug 50361 has been marked as a duplicate of this bug. ***,1372690696,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)",*** Bug 50328 has been marked as a duplicate of this bug. ***,1372373510,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)",This should now be fixed and we will push it out this afternoon.,1372370057,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","Change 70865 merged by jenkins-bot:
+Fix escapeParams in transclusions to not escape other transclusions
+
+https://gerrit.wikimedia.org/r/70865",1372368607,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)","Change 70865 had a related patch set uploaded by Esanders:
+Fix escapeParams in transclusions to not escape other transclusions
+
+https://gerrit.wikimedia.org/r/70865",1372360560,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+"VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)",*** Bug 49730 has been marked as a duplicate of this bug. ***,1372015399,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w3m2d62g427w2i6vbyd4,task_subcomment,NA
+VisualEditor: Phantoms are not relative to the surface content,"Reproduce:
+
+1. Open page with a protected node
+2. Click edit (visual editor)
+3. Quickly mouse over the protected node (while VE loads)
+4. See that the editor has slid the content down but the phantom is rendered under the mouse
+
+Perhaps the local overlay should be a peer of the documentNode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371696840,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-eepem2ziuzvmflw5gpqj,task_description,resolved
+VisualEditor: Phantoms are not relative to the surface content,Merged and will go out in the next few minutes.,1372210873,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eepem2ziuzvmflw5gpqj,task_subcomment,NA
+VisualEditor: Phantoms are not relative to the surface content,Didn't investigate yet but able to reproduce.,1371699532,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-eepem2ziuzvmflw5gpqj,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","Reported initially in bug 49596:
+
+ptwiki (""direita,right""): https://pt.wikipedia.org/w/index.php?&diff=36119075
+
+plwiki (""prawo,right""): https://pl.wikipedia.org/w/index.php?diff=36790309
+
+This feels like a Parsoid issue (VisualEditor doesn't know about localisations of these terms :-)) but Inez can tell us more details.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371690720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ipvexqb24ep4dnkhsnif,task_description,resolved
+"Images: Image insertion uses both the English and the localised syntax for ""right""",[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934016,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""",https://gerrit.wikimedia.org/r/70343 (Gerrit Change I9717e9d4b3b79cc9e583fb74e3537fbb5112a7bf) | change APPROVED and MERGED [by jenkins-bot],1372115880,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""",Related URL: https://gerrit.wikimedia.org/r/70343 (Gerrit Change I9717e9d4b3b79cc9e583fb74e3537fbb5112a7bf),1372114620,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","AFAIC, there is nothing wrong in using the localized version. The problem is to use both.",1371815473,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","These magic words are translateable at (for example for Polish) http://translatewiki.net/w/i.php?language=pl&module=words&title=Special%3AAdvancedTranslate - the entry for ""right"" says ""prawo, right"", which means both ""prawo"" and ""right"" are accepted and mean the canonical ""right"".
+
+This looks as if Parsoid was calling (implicitly?) .toString() on an array of these terms instead of taking its first entry: ['prawo', 'right'].toString() == 'prawo,right'.",1371714512,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","**winne2i** wrote:
+
+(I also mentioned ""/ramka/ means /frame/"" but I suppose ""ramka"" would be localised ""thumb""…?)",1371705767,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""","**winne2i** wrote:
+
+It's not a
+ (localised 'thumb'),right
+this is
+ (localised 'right'),right
+as I mentioned in bug 49596 comment 6.",1371705686,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Images: Image insertion uses both the English and the localised syntax for ""right""",Correct - it is a Parsoid bug. Somehow it is similar to https://bugzilla.wikimedia.org/show_bug.cgi?id=48665 but definitely not a duplicate.,1371699745,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-ipvexqb24ep4dnkhsnif,task_subcomment,NA
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers","Whenever you think that you've fixed that damn script, you suddenly realize there's something else that's still wrong.
+
+
+Testing the fix for bug 49758, looking at its results:
+
+Created reports per component:
+VisualEditor           General                       33
+MediaWiki extensions   UniversalLanguageSelector     27
+VisualEditor           Editing Tools                 25
+VisualEditor           MediaWiki integration         12
+Wikimedia              Bugzilla                      11
+
+Created reports per product:
+MediaWiki                     43 
+Wikimedia                     45 
+MediaWiki extensions          104
+Security                      3  
+Tools                         5  
+
+it is clear that the ""product"" list does not list those products with the **highest** number of new tickets in the last week.
+
+This can be also seen on
+https://bugzilla.wikimedia.org/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfield=[Bug+creation]&chfieldvalue=&chfieldfrom=-7d&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap
+
+which right now lists these top 5 products:
+
+MediaWiki extensions  104
+VisualEditor          95
+MediaWiki             48
+Wikimedia             47
+Parsoid               23
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1371682740,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_description,resolved
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers",Deployed.,1372340940,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_subcomment,NA
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers","Shizzle, /me blind. ""ORDER BY foo DESC"" is teh win!",1371711921,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_subcomment,NA
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers",Related URL: https://gerrit.wikimedia.org/r/69629 (Gerrit Change Iecdc7439463f58be272cf0b73f662ac91d0b061b),1371711788,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_subcomment,NA
+"Weekly Bugzilla Report: ""Created reports per product"" lists random products, not those with highest numbers","Looking back at the very first revision of operations/puppet/templates/misc/bugzilla_report.php it already says:
+
+getBugsPerProduct() uses
+SELECT name, count(*) FROM bugs
+but
+getBugsPerComponent() uses
+SELECT name, count(*) as total FROM bugs
+
+That's the only difference I can spot in the query designs.",1371687352,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-epwwpgqwza3gwnpfjm7f,task_subcomment,NA
+VisualEditor: TemplateSpecModel should expand aliases,"TemplateSpecModel currently doesn't expand aliases, so if it knows something as ""foo"" with an alias of ""1"" and the dialog asks about ""1"", it returns nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371671820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xszasferpgmq6tda243w,task_description,resolved
+VisualEditor: TemplateSpecModel should expand aliases,"See https://www.mediawiki.org/wiki/Extension:TemplateData#Defining_a_TemplateData_block
+
+Example:
+
+{
+  params: {
+    image: {
+      label: 'File name',
+      ...,
+      aliases: ['1', 'Image', 'Filename', .. ]
+    }
+  }
+}",1374680706,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-xszasferpgmq6tda243w,task_subcomment,NA
+VisualEditor: TemplateSpecModel should expand aliases,"More a question that a bug. How do you specify an alias using templateData? There are lots of examples which use alternate capitalisation for parameters. For example {{Infobox World Heritage Site}}
+http://en.wikipedia.org/wiki/Template:Infobox_World_Heritage_Site
+uses both 'Image' and 'image' to specify an image. To specify both makes the documentation clumsy. An alias would be ideal.
+
+Also {{Quote}}}
+http://en.wikipedia.org/wiki/Template:Quote
+can be given in two forms, either positional:
+{{quote|phrase|person|source}} 
+or named:
+{{quote|text=phrase|sign=person|source=source}}
+Currently both are documented but it would be nicer to use aliases.",1374679695,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-xszasferpgmq6tda243w,task_subcomment,NA
+VisualEditor: TemplateSpecModel should expand aliases,Related URL: https://gerrit.wikimedia.org/r/70111 (Gerrit Change I37ec0e152df905844ac58ed1834fca29dccb4eec),1372033560,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xszasferpgmq6tda243w,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,"Using Chrome27.0.1453.110 m
+Replicated on Firefox 21.0
+
+Attempting to remove a template using the puzzle piece and ""remove"" function seems to succeed but leaves behind the following code:
+<span data-mw=""{&quot;parts&quot;:[]}"" class=""metadata plainlinks ambox ambox-style ambox-Orphan"" style></span>
+
+See:
+http://en.wikipedia.org/w/index.php?title=Cocking-cloth&diff=560630933&oldid=324780702
+
+and 
+http://en.wikipedia.org/w/index.php?title=Cocking-cloth&diff=560631541&oldid=560631467
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371661680,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_description,resolved
+VisualEditor: Blank transclusion block doesn't get converted into blankness,*** Bug 49970 has been marked as a duplicate of this bug. ***,1371844137,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,Merged and will be going out with next push.,1371748525,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,Related URL: https://gerrit.wikimedia.org/r/69686 (Gerrit Change Ic5d4fbf73f3d1be9cf877bc8b98096de9e98991a),1371745439,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,*** Bug 49855 has been marked as a duplicate of this bug. ***,1371744867,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+VisualEditor: Blank transclusion block doesn't get converted into blankness,*** Bug 49835 has been marked as a duplicate of this bug. ***,1371728132,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-d6c7qzgfg4jsrlzfag4r,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","When a user inserts [[links]] or {{templates}}, VisualEditor automatically wraps them into <nowiki> tags. Experienced contributors who are very used to using this syntax sometimes add it inadvertently.
+
+It would be a nice touch to show an unobtrusive warning to remind users that they need to use VisualEditor's menu to insert links, templates & other wikisyntax. LiquidThreads does this well when users insert their signature manually with ~~~ into their post
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50527
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50601",1371651600,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_description,resolved
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","The issue that caused this to be reopened (bug 52093) has been fixed and will be deployed soon; consequently, reclosing this.",1375203346,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Change 76701 merged by jenkins-bot:
+Set links in wikitext warning to load in new window
+
+https://gerrit.wikimedia.org/r/76701",1375201474,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #27)
+...
+> 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.
+
+Reported on bug 52093.",1375189962,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #27)
+> If it's not one thing, it's another ...
+
+Welcome to software development.",1375180789,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Change 76701 had a related patch set uploaded by Esanders:
+Set links in wikitext warning to load in new window
+
+https://gerrit.wikimedia.org/r/76701",1375180094,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","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.",1374794028,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #24)
+> The continued flow of markup errors shown by
+> http://en.wikipedia.org/w/index.php?title=Special:AbuseLog&wpSearchFilter=550
+> is a pretty good indication that the warning either isn't obtrusive enough or
+> clear enough. We're still seeing about 20 articles an hour corrupted because
+> of
+> this.
+> 
+
+there was a problem with the message (it opened at top of page instead of top of screen), because of bug 50870. since this bug is fixed, the message will become more effective (afaik, this fix was deployed on July 22).
+
+personally, i think that the right solution is outlined in bug 51897. however, ATM 51897 is marked as ""low"". if you think like i do, maybe you should lobby to bump up the priority of 51897.
+
+
+peace.",1374792947,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Another possibility: provide a side by side view of the two options the user has, and ask for confirmation:
+https://en.wikipedia.org/w/index.php?oldid=564535137#bug49820",1373995371,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**kwwilliams** wrote:
+
+The continued flow of markup errors shown by http://en.wikipedia.org/w/index.php?title=Special:AbuseLog&wpSearchFilter=550 is a pretty good indication that the warning either isn't obtrusive enough or clear enough. We're still seeing about 20 articles an hour corrupted because of this.
+
+I think this really needs a positive checkoff dialog, and the article shouldn't be saved until the editor has agreed that he really wants strings of brackets and pipes in his text. Having these in legitimately is an extremely rare case, especially for a novice editor. I'd block the edit with the edit filter if I could, but VE isn't able to display edit filter messages properly.",1373993008,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #19)
+> Depends on bug 51432
+
+This was already reported as bug 50870, adjusting.",1373982306,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**ignatzmice.wiki** wrote:
+
+(In reply to comment #21)
+> What about having the balloon (https://github.com/wikimedia/jquery-tipsy ?)
+> pointing exactly to the position where the wikitext was found?
+
+That might work pretty well too, especially if the balloon is a prominently ""warning"" color (as suggested somewhere by someone). I personally would be in favor of a big in-your-face notification, but I accept that not everyone will.",1373980188,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",What about having the balloon (https://github.com/wikimedia/jquery-tipsy ?) pointing exactly to the position where the wikitext was found?,1373979657,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**ignatzmice.wiki** wrote:
+
+(In reply to comment #18)
+> Created MW bug for position fixed. Due to the possibility of false positives,
+> having a blocking confirmation box may be too obtrusive.
+
+I dunno. I don't see a lot of false positives coming out of Filter 550. If you're really concerned, there could be a setting in the VE prefs to turn it off. (I definitely would NOT want a ""don't show again"" in the popup itself—too easy to get rid of it without clearly understanding what it means.)",1373973971,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",Depends on bug 51432,1373973173,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Created MW bug for position fixed. Due to the possibility of false positives, having a blocking confirmation box may be too obtrusive.",1373973112,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",Actually this is a general problem with jsMessages is general. They should be placed at a fixed position on the page.,1373956593,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Wikitext_warning_probably_won.27t_be_seen_by_most_editors for some more detailed info on pieces of it.,1373951338,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",I'm reopening this as it seems to be the best place. There is definitely an issue with the warning being only on top and so you really don't have to be scrolled down that much before you don't see the warning.,1373951190,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**ignatzmice.wiki** wrote:
+
+The little box is not nearly obtrusive enough. It should be a popup (like the ""are you sure you want to thank this user?"" popup) that says the same thing as the warning, but requires confirmation (even a sole ""OK"" button would be fine, so long as it actually disrupts the editor's typing).",1373950172,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Just tried this out - seems to be an issue.  If you are scrolled down far enough on an article, the warning is never seen.  It's tied to the top of the page. You can go all the way through the save process and only see the message once the new version loads.  I suspect this might be reducing the effectiveness of the notice.  (FF 22, OS 10.6.8)",1373949582,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",Feature to do this is now merged and will be deployed tomorrow.,1373855518,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Change 73569 merged by jenkins-bot:
+Warn users when they are typing wikitext
+
+https://gerrit.wikimedia.org/r/73569",1373855446,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","Change 73569 had a related patch set uploaded by Catrope:
+Warn users when they are typing wikitext
+
+https://gerrit.wikimedia.org/r/73569",1373854895,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","**ignatzmice.wiki** wrote:
+
+(In reply to comment #7)
+> (In reply to comment #6)
+> > A permanently dismissible first-use reminder may be sufficient. I suggest we
+> > try that and see if it significantly reduces incidents of wikitext insertion.
+> > See bug 50601 for discussion.
+> 
+> Habits die hard. When you've been entering wikitext manually for the past 12
+> years, it's _really_ hard to change your habits. I really doubt a ""first-use
+> reminder"" will be enough.
+
+Yes, this. I recognized the problem first time I did it, and it still happens.",1373844634,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #4)
+> I have already suggested bug 50527 as a possible solution to this problem. An
+> automatic tag and then manual correction would be a simple-to-implement
+> interim
+> measure, if not long term.
+
+Bug 50527 proposes that the edit go through, WITHOUT warning the editor of his/her mistake; instead, the edit summary gets a tag showing that a problem exists with the *completed* edit. Given that the software can detect this error, it makes more sense to give the editor who made the mistake a chance to fix it *before* the edit is completed - ideally, not to allow the edit to be completed with the error intact within in. That way, (a) the editor is more likely not to make the mistake again, and (b) if the editor who made the mistake fixes it before finalizing his/her edit, there is no need for a second (corrective) edit (and no need for someone to be monitoring recent changes for the tag proposed in bug 50527).",1373662680,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","(In reply to comment #6)
+> A permanently dismissible first-use reminder may be sufficient. I suggest we
+> try that and see if it significantly reduces incidents of wikitext insertion.
+> See bug 50601 for discussion.
+
+Habits die hard. When you've been entering wikitext manually for the past 12 years, it's _really_ hard to change your habits. I really doubt a ""first-use reminder"" will be enough; I still expect people to add [[ inside VisualEditor in 5 years. All drivers learn what the speed limits are before they get their driving license, but there are still speed limit signs on the roads :)
+
+A guided tour is indeed a great idea, but _in addition_ to an always-shown-when-wikitext-is-detected warning, not as a replacement, imho.",1373656626,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",A permanently dismissible first-use reminder may be sufficient. I suggest we try that and see if it significantly reduces incidents of wikitext insertion. See bug 50601 for discussion.,1372986202,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",And bug 50093 for an alternative [[ suggestion.,1372878170,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","I have already suggested bug 50527 as a possible solution to this problem. An automatic tag and then manual correction would be a simple-to-implement interim measure, if not long term.",1372862368,PHID-USER-65pjzcmoby2fsgzdrfjq,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",%%%*** Bug 50581 has been marked as a duplicate of this bug. ***%%%,1372859187,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor","""What Chris said"". I'd like to know the rationale for the priority rating on this; it's the biggest source of article corruption.",1372844611,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor",Why is this marked low priority? It is causing problems on the live wiki with people unable to figure out why their edit has not worked - the VE hides the nowiki tags it has inserted so its impossible to determine the cause unless one knows about this feature (which I've not seen in documentation) or uses the misnamed edit source.,1372844039,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k7f4ru5f6yx35p5jkdx7,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"screenshot
+
+When selecting some templates in VisualEditor, a blue rectangle appears in the top left corner of the browser's window, and disappears when the template is unselected.
+
+Encountered on https://en.wikipedia.org/wiki/User:Jdforrester_%28WMF%29/Sandbox?veaction=edit (see screenshot)
+
+Firefox 21.0 on openSUSE 12.3
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50074
+
+**Attached**: {F11783}",1371649560,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-sidkh5inlhdkyygqassz,task_description,resolved
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,Appears resolved.,1373536056,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"(In reply to comment #7)
+> As noted by JamesF in 50161, this still occurs (Vector, Chrome, Win 7).
+> Screenshot while editing ref. #6 in
+> http://it.wikipedia.org/wiki/Utente:Syrio/Bozzoli , you need to click at
+> least
+> a few times on the sentence before the puzzle piece pops up. It will allow
+> you
+> to edit the reference and save the page as usual. It might be worth noting
+> that
+> the page features a page title and a magic word. Thanks.
+
+I now can't reproduce this - can you check too? (We did a new release today which should have fixed this for good.)",1373512100,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"As noted by JamesF in 50161, this still occurs (Vector, Chrome, Win 7).
+Screenshot while editing ref. #6 in http://it.wikipedia.org/wiki/Utente:Syrio/Bozzoli , you need to click at least a few times on the sentence before the puzzle piece pops up. It will allow you to edit the reference and save the page as usual. It might be worth noting that the page features a page title and a magic word. Thanks.",1373440558,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"Created attachment 12812
+Light blue bar issue still occurring
+
+**Attached**: {F11784}",1373440247,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,Fixed and will go out in the next release.,1372461348,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"Change 71118 merged by jenkins-bot:
+Don't draw highlights over hidden elements.
+
+https://gerrit.wikimedia.org/r/71118",1372458730,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"Change 71118 had a related patch set uploaded by Robmoen:
+Don't draw highlights over hidden elements.
+
+https://gerrit.wikimedia.org/r/71118",1372452480,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,"Confirmed, happens in firefox and chrome.",1372118693,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox,%%%*** Bug 50074 has been marked as a duplicate of this bug. ***%%%,1372118661,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-sidkh5inlhdkyygqassz,task_subcomment,NA
+VisualEditor: Image dialog shows <visualeditor-dialog-media-content-section> instead of actual message,"Encountered on: https://en.wikipedia.org/wiki/Westplex?veaction=edit
+Firefox 21.0 on openSuse 12.3
+
+When opening the ""Media settings"" overlay by clicking the icon on the image, the title shows <visualeditor-dialog-media-content-section> instead of what I assume should be the actual system message.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1371649140,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-n7i2eetsofstfrmijiw5,task_description,resolved
+VisualEditor: Image dialog shows <visualeditor-dialog-media-content-section> instead of actual message,Fixed by gerrit 69497 which we will try to get pushed today.,1371657503,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n7i2eetsofstfrmijiw5,task_subcomment,NA
+VisualEditor: Pressing escape should close a dialog,"Like we do with the link inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371644280,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ovbuk7vqve57dhhhvnh7,task_description,resolved
+VisualEditor: Pressing escape should close a dialog,This fix will be pushed to production later this afternoon; closing as such.,1372378620,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ovbuk7vqve57dhhhvnh7,task_subcomment,NA
+VisualEditor: Pressing escape should close a dialog,"Change 70946 merged by jenkins-bot:
+Close dialogs on escape
+
+https://gerrit.wikimedia.org/r/70946",1372378238,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ovbuk7vqve57dhhhvnh7,task_subcomment,NA
+VisualEditor: Pressing escape should close a dialog,"Change 70946 had a related patch set uploaded by Trevor Parscal:
+Close dialogs on escape
+
+https://gerrit.wikimedia.org/r/70946",1372377665,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ovbuk7vqve57dhhhvnh7,task_subcomment,NA
+VisualEditor: Image corruption edits - garbled text inserted into image description,"See, for example, http://en.wikipedia.org/w/index.php?title=Audie_Murphy&diff=560382883&oldid=560374610 - the line ""ad a private-pilot license and"" (image description) is clearly being taken from the article text ""had a private-pilot license and a reported 8, 000 hours of flying time"", but I have no idea how.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371640500,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-rjfwlifxsqzej72hvwal,task_description,resolved
+VisualEditor: Image corruption edits - garbled text inserted into image description,These were fixed by Inez's new code from Thursday.,1372016417,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rjfwlifxsqzej72hvwal,task_subcomment,NA
+VisualEditor: Image corruption edits - garbled text inserted into image description,"**molly.white5** wrote:
+
+A user just came to IRC asking about this same issue. The user had made this edit: http://en.wikipedia.org/w/index.php?title=Harry_Belafonte&diff=560738876&oldid=560738222
+
+The user had only intended to make the changes that appear between lines 98 and 108; all of the other changes appear to be a product of this bug.
+
+The same issue occurred for the user in http://en.wikipedia.org/w/index.php?title=Harry_Belafonte&diff=560737462&oldid=560717280.",1371737760,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rjfwlifxsqzej72hvwal,task_subcomment,NA
+VisualEditor: Some template dialog loading attempts fail with 'TypeError',"Steps to reproduce:
+
+1) Visit https://en.wikipedia.org/wiki/Deliciosamente_amoral?veaction=edit
+
+2) Attempt to manipulate the contents of the infobox by clicking the puzzle piece icon associated with it.
+
+Expected behavior:
+
+Infobox parameters should be editable.
+
+Actual behavior:
+
+Template editor invocation fails with the following error on the console:
+
+Uncaught TypeError: Cannot read property 'description' of undefined 
+
+Chrome/Ubuntu
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49493",1371614460,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ic77u5udy3nvxbsnznrc,task_description,resolved
+VisualEditor: Some template dialog loading attempts fail with 'TypeError',"Yes, this is a dupe of bug 49493; sorry!
+
+*** This bug has been marked as a duplicate of bug 49493 ***",1371748994,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ic77u5udy3nvxbsnznrc,task_subcomment,NA
+VisualEditor: Some template dialog loading attempts fail with 'TypeError',"This might be linked to bug 49493 - Timo, any quick thoughts?",1371614781,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ic77u5udy3nvxbsnznrc,task_subcomment,NA
+VisualEditor: Inspector menu appears with blank entry in Firefox,"Example screenshot of the issue
+
+In the given link, for reference 7's template; only in Firefox - works fine in Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=VisualEditor:TestReferenceContents&oldid=713075
+
+**Attached**: {F11716}",1371594720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xu4scnfjjp674hs6ehjl,task_description,resolved
+VisualEditor: Inspector menu appears with blank entry in Firefox,Patched and merged: https://gerrit.wikimedia.org/r/#/c/70119/,1372190121,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-xu4scnfjjp674hs6ehjl,task_subcomment,NA
+VisualEditor: Pawn appears when Cmd-C over a selected inline image in Firefox,"https://en.wikipedia.org/wiki/List_of_highways_numbered_147?veaction=edit
+
+I selected an inline image in the editor (in itself strange, because it doesn't seem you can edit it). I then hit cmd-c, and the inline image was replaced by the pawn char.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371579000,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-eiikdpgxia5svismvu44,task_description,resolved
+VisualEditor: Pawn appears when Cmd-C over a selected inline image in Firefox,Fixed (I think) in gerrit 69503 which we will deploy this afternoon.,1371680649,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eiikdpgxia5svismvu44,task_subcomment,NA
+VisualEditor: Pawn appears when Cmd-C over a selected inline image in Firefox,"Actually, Safari 6 for me.",1371649398,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-eiikdpgxia5svismvu44,task_subcomment,NA
+VisualEditor: Pawn appears when Cmd-C over a selected inline image in Firefox,"Yet again, a Firefox bug. *sighs*
+
+(Editing images will be possible very very soon. :-))",1371580229,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eiikdpgxia5svismvu44,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","<b><b>Foo</b></b> == <b>Foo</b> so it's not /so/ bad if VE corrects it (but it's still a bit dirty, but <small><small>Foo</small></small> != <small>Foo</small> (and the same with <big> and <sup> and …)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=User:JohnCD/draft&diff=560430675&oldid=560430611",1371574560,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_description,resolved
+"VisualEditor: Nested identical annotations can be additive, not just identical",Now fixed.,1373503078,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical",Fixed on the VisualEditor side; the Parsoid upstream issue in Domino is patched but not yet released. Not marking as fixed until that's done.,1373318742,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","Change 72133 merged by jenkins-bot:
+Make all annotations additive
+
+https://gerrit.wikimedia.org/r/72133",1373313118,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","Change 72133 had a related patch set uploaded by Esanders:
+Make all annotations additive
+
+https://gerrit.wikimedia.org/r/72133",1373055582,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","(In reply to comment #4)
+> The fix sets big/small/sup/sub to be additive.
+> 
+> Arguably we should make all annotations additive, as you could add
+> 'style=""font-size:110%""' to anything, although I haven't thought through how
+> this might affect the toolbar interactions yet.
+
++1. This will also avoid dirty diffs on such content.",1372801723,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","Change 71716 merged by jenkins-bot:
+Allow annotations to be additive
+
+https://gerrit.wikimedia.org/r/71716",1372797972,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","The fix sets big/small/sup/sub to be additive.
+
+Arguably we should make all annotations additive, as you could add 'style=""font-size:110%""' to anything, although I haven't thought through how this might affect the toolbar interactions yet.",1372797053,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical","Change 71716 had a related patch set uploaded by Esanders:
+Allow annotations to be additive
+
+https://gerrit.wikimedia.org/r/71716",1372796724,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical",This causes round-trip failures.,1372723619,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+"VisualEditor: Nested identical annotations can be additive, not just identical",%%%*** Bug 49756 has been marked as a duplicate of this bug. ***%%%,1371574644,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-fox5cuz5lkwl5eb3gxrd,task_subcomment,NA
+VisualEditor: Support creation/editing of references using an existing ref-name,"The reference editor allows me to group references, and allows me to include a ref name parameter to make them reusable, but has no way of actually calling that ref name.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371535560,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_description,resolved
+VisualEditor: Support creation/editing of references using an existing ref-name,"This feature is now written and merged, and will be going out in a few minutes.",1372382660,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_subcomment,NA
+VisualEditor: Support creation/editing of references using an existing ref-name,"Change 70364 merged by jenkins-bot:
+Reference insertion, new and existing
+
+https://gerrit.wikimedia.org/r/70364",1372382035,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_subcomment,NA
+VisualEditor: Support creation/editing of references using an existing ref-name,"... this is already what's meant to happen with master; it seems that it's broken a little in this regard, so we'll need to fix.",1371573652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_subcomment,NA
+VisualEditor: Support creation/editing of references using an existing ref-name,"Proposing for July 4 milestone (alt. July 11). This is imho not a nice-to-have but a requirement since re-using of references is quite common and without it, it would seem incomplete.
+
+The ability to create such references or turn existing ones into it may be less important than the ability to edit such references (e.g. a <select> with all ref-names available on this page).",1371540715,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2hbzqzof3t5thiyrb3yz,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B","Screenshot
+
+See associated character; italics in the reference editing interface causes a pawn to appear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11627}",1371533160,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-v4v3wychksw2n5sabckt,task_description,resolved
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B",*** Bug 49877 has been marked as a duplicate of this bug. ***,1371774369,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B",*** Bug 49888 has been marked as a duplicate of this bug. ***,1371773590,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B",Fixed in gerrit 69503 which we will deploy this afternoon.,1371680618,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B","Actually, neither the console nor firebug show any errors.
+
+It is an italicised or bolded pawn, however, so we can confirm that works.",1371634405,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B","Please check your browser's JS console, there should be an error message that appears there at the same time that the pawns appear in the editor.",1371602813,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+"VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B",Also adding a pawn on bolding.,1371534835,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-v4v3wychksw2n5sabckt,task_subcomment,NA
+VisualEditor: Template inspector removing characters from header,"See associated screenshot; an attempt to add 'foo' to the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371532980,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ukps7g4li7inap7lxq46,task_description,resolved
+VisualEditor: Template inspector removing characters from header,This is an artefact of a Parsoid serialisation bug that has now been fixed.,1371657198,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ukps7g4li7inap7lxq46,task_subcomment,NA
+VisualEditor: Template inspector removing characters from header,"Screenshot
+
+**Attached**: {F11626}",1371533000,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ukps7g4li7inap7lxq46,task_subcomment,NA
+VisualEditor: Prevent headings in reference sub-editor dialogs,"**Author:** `rachelqa99`
+
+**Description:**
+Make a reference, then type text into Name content, and change format to Heading 5 or Heading 3.  When you save the file, you see the wikitext displayed for the heading format. 
+
+See page: https://www.mediawiki.org/wiki/User:Rachel99/testing_edit_source
+
+On the bottom of the page, it looks like that.
+
+    ↑ ===test===
+    ↑ =====Book reference=====
+    ↑ ===footnote text===
+    ↑ =====test5=====
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371500340,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-563eb2ikcrhdth26zmqs,task_description,resolved
+VisualEditor: Prevent headings in reference sub-editor dialogs,Merged and will be deployed very soon.,1371845722,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-563eb2ikcrhdth26zmqs,task_subcomment,NA
+VisualEditor: Prevent headings in reference sub-editor dialogs,Related URL: https://gerrit.wikimedia.org/r/69867 (Gerrit Change Ic823a90398dafca1caf8fa4142d98133ab661d7c),1371828262,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-563eb2ikcrhdth26zmqs,task_subcomment,NA
+VisualEditor: Prevent headings in reference sub-editor dialogs,"Yes, this is a definite issue - there's a wider bug about the technical functionality, bug 49657, but this is a specific example we need to do (and so soon).",1371506764,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-563eb2ikcrhdth26zmqs,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,"on beta labs only, not seen in mediawiki.org: 
+
+On any article e.g. http://en.wikipedia.beta.wmflabs.org/wiki/0.0924627428112147 
+
+Click Edit to invoke VE
+
+Page content is a different article.  In the case of http://en.wikipedia.beta.wmflabs.org/wiki/0.0924627428112147 I see the content for an article on ""TAT-1""
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49963",1371486720,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_description,resolved
+VisualEditor link to Parsoid broken in beta labs deployment?,This was fixed yesterday by Roan.,1372390935,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,Related URL: https://gerrit.wikimedia.org/r/70582 (Gerrit Change Iacc9e88ec83e9037abe9ace53deccafcf68a6bbb),1372215640,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,"This is my fault, I broke this in https://gerrit.wikimedia.org/r/#/c/68133/ . We should revert that change and figure out a way to keep deployment-parsoid2 up-to-date.",1372215604,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,"Created attachment 12594
+modal upon review or save
+
+**Attached**: {F11548}",1371760280,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+VisualEditor link to Parsoid broken in beta labs deployment?,"This still happens after upgrading VE to the latest version, with error saying ""invalid token"", see screen shot",1371760230,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-3dm4nj4f3hmvkgyfm7k2,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","Alongside the ""minor"" and ""watch"" checkboxes in the save dialog, for pages with FlaggedRevs switched on and outstanding unaccepted revisions, add a checkbox to ""accept pending revisions"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50852",1371485400,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_description,resolved
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog",Merged and will get deployed in a few hours' time.,1374649658,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","Change 75555 merged by jenkins-bot:
+Render check boxes from EditPage
+
+https://gerrit.wikimedia.org/r/75555",1374649652,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","Change 75555 had a related patch set uploaded by Catrope:
+Render check boxes from EditPage
+
+https://gerrit.wikimedia.org/r/75555",1374648415,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog",*** Bug 51833 has been marked as a duplicate of this bug. ***,1374645680,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #6)
+> I note this has been posted as an enhancement; however, as flagged revisions
+> are applied to *all* pages in article space on certain Wikipedias (de and ru
+> in particular) I'd urge that this be resolved prior to introducing VisualEditor
+> to those projects. For them, the absence of this would be more than the minor
+> inconvenience it is on English Wikipedia, where PC is applied to a very small
+> number of pages and could be switched to semi-protection if really needed.
+
+Absolutely.",1374081153,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #0)
+> Alongside the ""minor"" and ""watch"" checkboxes in the save dialog, for pages
+> with
+> FlaggedRevs switched on and outstanding unaccepted revisions, add a checkbox
+> to
+> ""accept pending revisions"".
+
+I note this has been posted as an enhancement; however, as flagged revisions are applied to *all* pages in article space on certain Wikipedias (de and ru in particular) I'd urge that this be resolved prior to introducing VisualEditor to those projects.  For them, the absence of this would be more than the minor inconvenience it is on English Wikipedia, where PC is applied to a very small number of pages and could be switched to semi-protection if really needed.",1374080923,PHID-USER-yif6nz5uhka5cnltixpc,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #4)
+> (In reply to comment #2)
+> > Just as an addition to this: I'm not sure if just the checkbox is what is
+> > needed. The current work flow has a whole separate page because we need to
+> > show the diff involved for the review. I imagine that can be done without
+> > going to a new page but either way they should be able to review the diff
+> > (and preferably leave a comment like you can in the review page now) before
+> > checking any kind of approve box since they become somewhat responsible for
+> > those edits.
+> 
+> Yes, indeed; I was imagining:
+> 
+> * on load, an alert in the edit notices saying ""You will need to accept the
+> outstanding changes before saving"" (or whatever the current message is) -
+> possibly with a link to the below?
+> * on entering the save dialog, the save button will be disabled with another
+> copy of the ""You will need to accept the outstanding changes before saving""
+> text (in the same place as the edit conflict / CAPTCHA / DOM corruption
+> warnings)
+> * in the line of buttons (""Save page"", ""Review your changes"") there should
+> be a
+> third button, ""Review outstanding changes"", which on click pops up the diff
+> of
+> outstanding changes, with a text box for the optional review comment and an
+> ""accept these changes"" button that takes you back to the save dialog, now
+> with
+> the save button enabled.
+> 
+> Feels a little clunky, though - perhaps we could make the process in-line
+> with
+> the edit summary message?
+
+Since this is going to need to be fully in javascript for VisualEditor, and the interface for this in FlaggedRevisions is already mostly in javascript (a small bit is done server-side through EditPage hooks), I recommend we not duplicate all of this logic and API handling for:
+* ""advertise you are reviewing this""
+* API handling ""leave comments""
+ ""get the diff against the latest stable version""
+* ""mark as reviewed"" 
+* etc.
+
+And instead depend on the logic being in FlaggedRevisions in a re-usable way that we can just call from within VisualEditor.
+
+Ideally they would also make their styling more pretty so that we can actually re-use it. Alternatively they'll have to make the logic re-usable separate from the UI as the current UI is not going to fit in (not just visually foreign to VisualEditor or usable interfaces in general, but also technically due to the DOM structure and layout properties).",1374008109,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #2)
+> Just as an addition to this: I'm not sure if just the checkbox is what is
+> needed. The current work flow has a whole separate page because we need to
+> show the diff involved for the review. I imagine that can be done without
+> going to a new page but either way they should be able to review the diff
+> (and preferably leave a comment like you can in the review page now) before
+> checking any kind of approve box since they become somewhat responsible for
+> those edits.
+
+Yes, indeed; I was imagining:
+
+* on load, an alert in the edit notices saying ""You will need to accept the outstanding changes before saving"" (or whatever the current message is) - possibly with a link to the below?
+* on entering the save dialog, the save button will be disabled with another copy of the ""You will need to accept the outstanding changes before saving"" text (in the same place as the edit conflict / CAPTCHA / DOM corruption warnings)
+* in the line of buttons (""Save page"", ""Review your changes"") there should be a third button, ""Review outstanding changes"", which on click pops up the diff of outstanding changes, with a text box for the optional review comment and an ""accept these changes"" button that takes you back to the save dialog, now with the save button enabled.
+
+Feels a little clunky, though - perhaps we could make the process in-line with the edit summary message?",1373149022,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog","(In reply to comment #0)
+> Alongside the ""minor"" and ""watch"" checkboxes in the save dialog, for pages
+> with
+> FlaggedRevs switched on and outstanding unaccepted revisions, add a checkbox
+> to
+> ""accept pending revisions"".
+
+I don't find that an acceptable solution, because there is a requirement that reviewers actually review the edit they are accepting; they cannot do that if they're just ticking a box.  
+
+See https://commons.wikimedia.org/wiki/File:Cropped_edit_source_admin_edit_with_existing_PC.png for what the screen looks like using Edit Source.  Note that the diff includes ALL unreviewed changes.",1373148387,PHID-USER-yif6nz5uhka5cnltixpc,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog",Just as an addition to this: I'm not sure if just the checkbox is what is needed. The current work flow has a whole separate page because we need to show the diff involved for the review. I imagine that can be done without going to a new page but either way they should be able to review the diff (and preferably leave a comment like you can in the review page now) before checking any kind of approve box since they become somewhat responsible for those edits.,1373147476,PHID-USER-f6l3bchko2ogbi4poj24,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+"VisualEditor: Add FlaggedRevs ""accept pending revisions"" to save dialog",*** Bug 50852 has been marked as a duplicate of this bug. ***,1373145699,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tyh6rgmh65nrcg5ssati,task_subcomment,NA
+VisualEditor: Templates (incorrectly) expanded,"https://en.wikipedia.org/wiki/Template:Contradictory, on https://en.wikipedia.org/wiki/Necessity - in the VisualEditor it displays as [<span title=""This text contradicts text in the article ""Necessity in English law"" (3 May 2011)"">contradictory]. Reproduced in Chrome 27/Safari 6.0.5 on a Mac, Firefox 21.0 on Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371469920,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-nbmggedatdejjopgumhd,task_description,resolved
+VisualEditor: Templates (incorrectly) expanded,"I changed the Contradict-inline template and that fixes this problem.
+
+https://en.wikipedia.org/w/index.php?title=Template%3AContradict-inline&diff=560522227&oldid=471439681",1371596252,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-nbmggedatdejjopgumhd,task_subcomment,NA
+VisualEditor: Templates (incorrectly) expanded,"This amounts to accepting <span title=""""foo"""">bar</span> as a valid span-tag. Ugh! The PHP parser seems to accept this quite fine.  Parsoid would have to perform the same magic.
+
+See http://en.wikipedia.org/w/index.php?title=Wikipedia:Sandbox&oldid=560521020
+
+Hover over the two foos and see the difference. PHP parser drops the title attribute 'bar' on the first foo since it is ofcourse a bug.
+
+Seems like a reasonable fix the Fix templat -- but I assume Fix is used in a lot of places and fixing the callers would be a lot of work ... so, we may need some ugly hack in Parsoid to support this.",1371595653,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-nbmggedatdejjopgumhd,task_subcomment,NA
+VisualEditor: Templates (incorrectly) expanded,"Reduced test case: {{Fix|text=foo|title=""bar""}}
+
+It is the quotes around ""baz"" that trips up Parsoid (probably the tokenizer).  Investigating more.",1371595194,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-nbmggedatdejjopgumhd,task_subcomment,NA
+VisualEditor: Templates (incorrectly) expanded,This is actually [[Template:Contradict-inline]] that appears broken in Parsoid - see http://parsoid.wmflabs.org/en/Template:Contradict-inline - shunting over.,1371513710,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nbmggedatdejjopgumhd,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size","See https://en.wikipedia.org/wiki/Hermann_M%C3%BCller_%28politician%29 for example; found in Chrome 27 on a Mac. In Safari 6.0.5 it displays differently (a large space appears, rather than a missing icon signifier) but is still broken. Not replicatable in Firefox 21.0/Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://parsoid.wmflabs.org/en/Hermann%20M%C3%BCller%20(politician)",1371469740,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_description,duplicate
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size","The original bug was rendering of [[:Media:Hermann Müller.ogg]].
+
+The rendering of [[File:Hermann Müller.ogg]]/[[File:La_Marseillaise.ogg]] is a different problem, as that renders as a player in source editor.  There are some underlying problems in Parsiod and even the mw API if I am understanding bug 49896 correctly.",1374915779,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size","Seems to me, this is still buggy !
+
+Have tried the following code at http://parsoid.wmflabs.org/_rtform/:
+[[File:La_Marseillaise.ogg]]
+
+This gives:
+<img resource=""./File:La_Marseillaise.ogg"" src=""//upload.wikimedia.org/wikipedia/commons/3/30/La_Marseillaise.ogg"" data-parsoid=""{&quot;a&quot;:{&quot;resource&quot;:&quot;./File:La_Marseillaise.ogg&quot;},&quot;sa&quot;:{&quot;resource&quot;:&quot;File:La_Marseillaise.ogg&quot;}}"" width=""200"">",1373452147,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size",[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934039,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size",This is now fixed in production for Parsoid (and so for VisualEditor). Sorry for the bug!,1371519787,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+"Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size","It's inserting a thumbnail image at fixed 200px width.
+
+<img resource=""./File:Hermann_Müller.ogg"" src=""http://upload.wikimedia.org/wikipedia/commons/d/d3/Hermann_M%C3%BCller.ogg"" width=""200"" data-parsoid=""{&quot;a&quot;:{&quot;resource&quot;:&quot;./File:Hermann_Müller.ogg&quot;},&quot;sa&quot;:{&quot;resource&quot;:&quot;:File:Hermann Müller.ogg&quot;}}"">",1371475842,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-d53fjwjfjlwbqoq4e52t,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Bug title may be a bit confusing; essentially, a user has suggested that the VE auto-convert wikimarkup entered ''into'' the VE, on save. The use case is users who keep typing [[link]], basically.
+
+My feelings on this are mixed; I think it's perfectly possible that this would be useful, but it sounds like a ton of work and it's also perfectly possible that, once we go live, muscle memory will adapt and there'll be no point to this. For now, sticking it in as a potential future enhancement.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49820
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51899
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47779",1371468300,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_description,declined
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to Amalthea from comment #40)
+> I really don't get why you're fighting this so hard.
+
+It should be obvious by now that VE's development has been made an ideological matter. This feature request involves some degree of the ""old way"" of doing things, thus is forbidden.",1400618098,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"I'll clarify that ""it shouldn't happen"" means just that it is not useful/desirable to have it IMHO, or at least I can't think of a situation where it would be.",1380723401,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"48891 and 53974 cover that specific problem. The wikimarkup warning is just a warning, it does not stop you from doing anything. 
+As for [[[[this situation]]]], of course it shouldn't happen. I can't recall the bug number though, right now, and since a quick search did not seem successful, I'll come back on that later.",1380722782,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Wikifram** wrote:
+
+What I mean is that you start with wikimarkup visible in the VE editing mode. When you add something (''not'' wikimarkup) inside such wikimarkup, you get the wikimarkup notice at the top right; but on saving, the existing wikimarkup remains. [https://www.mediawiki.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandboxVE&diff=794444&oldid=794415]
+
+So my questions are; why is the existing wikimarkup accepted and displayed here, why is it recognised by the wikimarkup detection error, but why is it then not changed on saving? 
+
+This behaviour may give a clue as to how wikimarkup can be accepted in VE after all (but then again, perhaps not), but it certainly is baffling me.",1380722209,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Hi there, I don't think I see your VEdit there. I did https://www.mediawiki.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandboxVE&diff=794415&oldid=794413 and https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=575429594&oldid=575429509 instead, nowikis are added as the only expected outcome. Which conversion should have happened when VEditing? Thanks.",1380717126,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Wikifram** wrote:
+
+Can someone explain why [https://www.mediawiki.org/wiki/Communication?veaction=edit this page] seems to accept wikitext markup, even in VE mode? On saving, it gives the ""nowiki"" warning, but it doesn't actually convert the existing ""[["" and ""]]"" into wikitext. A very strange page in VE mode, that one.",1380715761,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Amalthea.wikimedia** wrote:
+
+(In reply to comment #39)
+> [...] this bug is - by definition of the product - a WONTFIX.
+
+James, this is simply not true. See comment #36 about auto formatting logic in other visual word processors.
+I really don't get why you're fighting this so hard.",1377849879,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #10)
+> Marking as WONTFIX per my earlier comments and Erik's.
+
+… again. Bug 51897 is indeed different; my apologies for merging it based on my reading of the bug as filed. However, this bug is - by definition of the product - a WONTFIX.",1377819704,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"user John Broughton at en.wp comments:
+""Rather than focus on improving [the warning about entering wikitext], a better direction to go would be for VE to be able to convert wikitext to its equivalent in VE. Thus if one typed [[New York City]], for example, VE would convert that to its format for an internal link. This is fairly straight-forward, programming-wise: after VE adds a closing nowiki tag for some text, it would examine it for conversion possibilities: external link? internal link? footnote? template?""",1376340113,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #22)
+> 
+> If accidental insertion of wikitext is still an issue, we should focus on
+> other
+> ways to mitigate that issue.
+
+2 things: 
+1) it's not an ""if"", and i do not think you guys should wait for the community to prove it to you. you should go hunt for it, so you can see for yourselves that it *is* an issue (hint: look for edits with ""visualeditor"" tag that added <nowiki>: approximately 100% of those represent the problems. you have to tools to actually measure it across all projects where VE is enabled by default).
+2) ""focus on other ways to mitigate that issue"": how about solving bug 51897, instead of marking it ""low"" and basically ignoring it? this *is* exactly ""other ways to mitigate that issue"". 
+or ,alternatively, find a better way to solve it: right now, it seems the team is saying ""we'll focus on other ways to mitigate the issue"", but they do not actually mean it: what other ways? who is working on it? what do they do? where is the ""focus""?
+what you guys are doing today does not look very much like ""focus"" - it looks much more like ignoring the issue and hoping the problem will go away by itself.
+
+
+
+(In reply to comment #18)
+> Sorry, but this is not something we'll ever do, as I explained in comment 9.
+> It's not simply a matter of prioritization - it's a matter of ensuring we can
+> provide a user experience that's not modeled on markup, but on best user
+> experience practices. As James said, we provide keyboard shortcuts, and will
+> provide other user interfaces optimized for markup. But parsing markup within
+> the visual editing context is completely off the table.
+
+this is nothing more and nothing less than saying ""it's so because i said so"". 
+you made a bad decision. that's something that happened in life to (almost) all of us. the problem is not so much this bad decision - the problem your refusal to accept that it was a bad decision, and you insistence that it was a good decision, in face of all the evidence.
+
+
+The reason i am writing this is because nowhere can i find any indication that the VE team actually changed its mind or at least decided to reconsider. 
+it is very much possible that the team actually *did* decide to reconsider, and i just missed it. if this is the case, please be graceful and ignore my rant.
+
+peace.",1375729537,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Amalthea.wikimedia** wrote:
+
+Erik:
+
+(In reply to comment #18)
+> it's a matter of ensuring we can provide a user experience that's not modeled
+> on markup, but on best user experience practices.
+
+I don't think that was the suggestion above?
+
+Word processors have long supported text-based auto formatting logic, and they certainly aren't focusing on underlying markup. For example, to this day, you can *bold* and _italicize_ text in OpenOffice Writer and Microsoft Word by using the traditional markup, or define numbered and bulleted lists simply by starting the first item with ""* "", ""- "", or ""1. "".
+
+Adding auto-formatting logic does not impair the goals of the visual editor: defining a link via square brackets won't be the obvious way, and it will likely not be advertised anywhere except possibly in some settings page. It can be helpful without taking anything away from the vision.",1375614123,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Wikifram** wrote:
+
+Note that this question is included in the large [[Wikipedia:VisualEditor/Default State RFC]] on the en.wikipedia, as question 5. The current tally, for what's it worth, is 28 supporting and 22 opposing, but with many conditional comments on both sides (""yes for X but no for Y""). Many of the opposes are ""no, because this is a WYSIWYG"", but in reality, of course, this isn't a wysiwyg but a hybrid anyway... (you still need to know wikimarkup to do a lot of things in the new editor in mainspace as well)",1375426633,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**Wikifram** wrote:
+
+Erik Moeller, do you have any idea how many hours are spent on correcting these ""nowikis"" every day? Do you, on the other hand, have any data on how many ""correct"" nowiki tags are added? Is there any reason why what should be a no-brainer (not per se an easy one technically, but a no-brainer from the should-be-done point-of-view) improvement is so drastically rejected? 
+
+Have any of you considered that, as of now, new editors using only VE and only editing the mainspace still need to know the [[ ]] syntax anyway? A simple example: on the English wikipedia, I opened [[HKBK College of Engineering]] with the VE, and clicked on the infobox. Click on a parameter, e.g. city, and what you are confronted with is [[Bangalore]]. So new editors ''need'' to use it in the infobox, but are ''not allowed'' to use it in the article text, and this is supposed to be an improvement why? 
+
+What is actually the reason (apart from perhaps ""technical difficulty"") that square brackets are no longer allowed as an alternative method of creating wikilinks? No one is asking to disable the VE wikilinking methods, but no one seems to understand the insistence of the WMF on disallowing the square brackets method either.",1375350281,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #31)
+> I think that James' marking your bug as a duplicate was likely caused by his
+> misunderstanding your request. He is part of the VE team but I have met him
+> at Wikimeets a few times and I can assure you he is human.
+
+
+the last line makes me think that maybe some of my comments can be read in a way that does not fully match the spirit in which they were written.
+
+although i have criticism, especially toward the perceived attitude of VE team towards their user base, i never meant to say or hint any of them is a bad person or less than brilliant developer.
+
+as i already said in this thread, i think VE itself is a great thing, we want it, we need it, and we want it to succeed. 
+
+hope that heated and less-than-polite things said in this (and maybe other) discussions will not be taken as attacks - it is/was never the intention to attack anyone.
+
+peace.",1374758978,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #28)
+Thank you for clarifying the two requests, Chris. That was super-helpful. :-)
+
+(In reply to comment #29)
+> maybe instead of coming here, what i should have done is to reopen and remove
+> the ""duplicate"" designation. 
+
+My apologies, kipod. Thank you for patiently putting up with me. Indeed, I think bug 51897 is not a duplicate of this bug. My comments were strictly related to the original request here on bug 49686.
+
+I don't know what the VisualEditor team's view is on your request at bug 51897, so I'm going to go ahead and un-dupe bug 51897 now. Bug 51897 may also eventually be marked resolved/wontfix, but it doesn't seem to be within the scope of this bug, so it should be handled separately.",1374721119,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"I think that James' marking your bug as a duplicate was likely caused by his misunderstanding your request. He is part of the VE team but I have met him at Wikimeets a few times and I can assure you he is human.
+
+As for Bug 51899, yes that is a perfect match. Thank you.",1374712742,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"oh, and what you describe as ""the ideal solution"", sounds a lot like bug 51899 to me.
+
+peace.",1374709297,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"i think you are correct stating that these two ""definitions"" of the enhancement request are not identical.
+however, i came here to bug you guys with ""my"" definition of the request after Forrester closed  bug 51897 with ""duplicate"". the bug he closed listed my request exactly.
+maybe instead of coming here, what i should have done is to reopen and remove the ""duplicate"" designation. 
+
+my guess is that it wouldn't make a huge difference - the team would have closed it as ""WONTFIX"" instead of closing it as ""DUPLICATE"". i took them on their word about these two request being one and the same - maybe it was a mistake. (afaik, Forrester is part of VE team).
+
+as to ""[["" being ambiguous: i did not dive deeply into it, and did not conduct extensive tests, but i think that typing ""[["" anywhere on the page will cause VE to jump the ""wikicode detected"" popup. as a wikicode, ""[["" is not ambiguous at all, i think. it means ""start internal link here"".
+
+
+peace.",1374709091,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"There are at least two separate requests here. They are related in that they both want to change the current behaviour of the two character sequence ""[["" in VisualEditor but they want to change it in incompatible ways. 
+
+Kipod is asking for the key sequence [[ to be treated the same as the key sequence ctrl+k. It is not asking for, nor would it require any changes to rendering. For the purposes of this comment I'll refer to this as ""Kipod's request""
+
+MZMcBride is commenting the original request which was for the sequence [[link]] to be parsed (either at save or on the fly) as if it were a link added using the link inspector. For the purposes of this comment I'll refer to this as the ""original request"".
+
+The two are not the same and the past few posts have seen people talking past each other. 
+
+I can see the merits of the original request but I can also see where the VE team are coming from. The desire stems from people wanting the best of both worlds - they want to be able to have the structure and layout of the visual editor with the low-level control they are used to in the source editor all in one place. Long term something like this really ought to be possible, but I don't think this is the way. Rather there should be some way for the visual editor to include non-visual blobs that it sends to the parser as is without doing anything to it (other than word wrapping in the editing window); and some way for the editor to mark the start and end of such blobs. This is not what the original request is asking for though.
+
+Kipod's request is something that imho should not be included as a default, as while [[word]] or [[short phrase]] are unlikely to be anything other than links, [[ on it's own is far more ambiguous and there is more scope for the desired action to be something other than inputting a link. Rather there should either be a built-in method for users to define their own shortcuts or a simple way (an API?) for a gadget that allows users to reliably define their own shortcuts to have the same effect without needing to be rewritten every time VE or some other mediawiki component is updated. 
+
+I recommend that if anyone wants further discussion on either request that the bugs are unmerged.",1374707128,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"i still do not think you understood the request. 
+it's not about transforming [[Foo]] to a link, it's about not getting [[Foo]] into the page in the first place: as soon as the user types ""[["", the ""[["" should be removed from the page and interpreted as <Ctrl>+K.
+
+
+as to your questions about File:Foo.jpg or Category:Foo: what does VE do today when someone presses <Ctrl>+K and then feeds ""File:Foo.jpg"" or ""Category:Foo"" ?
+whatever it does today, this is what i expect it to do when someone types ""[["" and then feeds in the link form ""File:Foo.jpg"" or ""Category:Foo"".
+
+
+> (In reply to comment #25)
+> ......
+> And, of course, a certain percentage of users will want to actually include
+> brackets (""["" and ""]"") in their edits. How do they undo the magical
+> transformation?
+> 
+
+these are just straw arguments. 
+there are many many many things one can't do now using VE. it will not at all be so bad if the extremely rare case of having to add ""[["" to the page within ""nowiki"" tags will be one of them. 
+definitely much much better than current situation, where hundreds of edits with ""[["" enclosed inside ""nowiki"" tags are added to enwiki daily, when the editors actually intended to add a link (i did not count them myself - this is what i'm led to believe based on reports of editors who actually clean this mess).
+
+peace.",1374702684,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #25)
+> what we ask (at least, this is what i asked - see bug 51897, which was marked
+> as duplicate of this one) is that when the user types ""[["", VE will remove
+> the ""[["" from the page, and behave as if the user typed <Ctrl>+K, i.e. open
+> the ""Link"" form.
+
+Yep, I think everyone commenting on this bug understands the request. :-)
+
+The problem is, as stated, computers aren't very good at reading minds or understanding context. You want to support ""[["" magically transforming into a VisualEditor link. This is certainly possible to implement, but then you naturally have to support:
+
+* [[foo]]
+* [[foo]]s
+* [[foo|bar]]
+* [[w:foo]]
+* [[w:foo|]]
+* [[w:en:foo (bar)|]]
+* [[WP:FOO]]
+
+When a user types ""[[File:foo.png]]"", do they really mean they want a link to the file or do they really mean they want to include the file?
+
+What about ""[[Category:foo]]""? It's often trivial for humans to understand what we mean or to understand what other humans mean, but computers... not so much.
+
+Once we add support for [[]] magically transforming into a link, does that mean we also have to support magic words such as {{DEFAULTSORT:}}, __NOTOC__, and so on? What about ParserFunctions such as {{#time:}} and {{#if:}}?
+
+And, of course, a certain percentage of users will want to actually include brackets (""["" and ""]"") in their edits. How do they undo the magical transformation?
+
+Down this path, madness lies, I promise.
+
+> easy to do, simple, and does not go against any principle in UI design,
+> except sheer stubbornness of the VE team.
+
+The VE team has certainly exhibited some stubbornness. But I personally agree with their decision here.
+
+> unfortunately i am not able at this time to provide a patch, but 92.24% of
+> the code is already in place - just find where VE jumps the popup, and do
+> something useful instead.
+
+A patch to VisualEditor or to MediaWiki will not be accepted. However, users are welcome to create JavaScript gadgets, personal JavaScript subpages, client-side scripts (think Greasemonkey), or even implement site-wide JavaScript with appropriate community consultation and consensus.",1374701180,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"i am not sure you understand the precise nature of this request, so let me elaborate:
+
+what we ask (at least, this is what i asked - see bug 51897, which was marked as duplicate of this one) is that when the user types ""[["", VE will remove the ""[["" from the page, and behave as if the user typed <Ctrl>+K, i.e. open the ""Link"" form.
+
+simple and easy, VE already recognizes that the user typed ""[["" - all we ask is that instead of jumping less-than-useful-and-often-out-of-screen popup, VE will do something good and useful for the community, for society, and for humanity.
+
+in the same way, when the user types ""{{"", remove it from the page and behave as if she clicked on the puzzle piece, instead of jumping the less-than-useful popup.
+
+easy to do, simple, and does not go against any principle in UI design, except sheer stubbornness of the VE team.
+
+unfortunately i am not able at this time to provide a patch, but 92.24% of the code is already in place - just find where VE jumps the popup, and do something useful instead.
+
+peace.",1374690348,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #23)
+> well, in all this products, when i misspell a word, the thing silently and
+> valiantly just fix my mistake, instead of shouting at me[1]. 
+> generally, this is known as ""Auto correct"" (sometimes also [[DWIM]]: ""Do
+> What I Mean"").
+> 
+> [...]
+> 
+> when you recognize that the user did something they did not mean to do, such
+> as mispelling a word (in M$ word) or typing [[Something something]] in VE,
+> just Do What the User Meant.
+
+Computers can't read minds and they monumentally struggle with understanding context. When I type ""subst"" into OS X (as in template substitution), it autocorrects to ""subset"" because surely that's what I meant, right?
+
+I completely agree with you that [[muscle memory]] here is an issue. And I completely agree that we need to find ways to make linking as painless as possible in VisualEditor (we're not there yet). But part of meeting user expectations is to take input (such as ""[[foo]]"", which displays as ""[[foo]]"" in VisualEditor) and output it as the user saw it in the editor.
+
+These type of magical transformations won't be supported in VisualEditor and I think that's a reasonable position to take. However, it should be completely possible to create a JavaScript gadget that can enhance the user experience for those who have a deep understanding of the difference between source editing and visual editing and who would like a hybrid option. I'd pursue this. :-)",1374689458,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"please look above: in comment 15, Forrester did some namedropping: ""Microsoft
+Word, OpenOffice, Google Docs, Apple Pages and more"".
+
+well, in all this products, when i misspell a word, the thing silently and valiantly just fix my mistake, instead of shouting at me[1]. 
+generally, this is known as ""Auto correct"" (sometimes also [[DWIM]]: ""Do What I Mean"").
+
+if really you use these products as your role model, please pick the good stuff, not the crappy stuff. who cares if the shortcut for ""link"" is <Ctrl>+K or <Ctrl>+L ?
+
+why can't you adopt the real valuable features from them instead of the completely anecdotal ones?
+
+when you recognize that the user did something they did not mean to do, such as mispelling a word (in M$ word) or typing [[Something something]] in VE, just Do What the User Meant.
+
+
+peace.
+
+
+[1] i cheated - i am not actually sure if it's really ""in all those products"". i know it's in most of them.",1374688603,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"We're listening, but in this case we're saying no, and that decision is final. We can elaborate a bit more on the why if that helps, but parsing wikitext in VisualEditor is absolutely not going to happen.
+
+If accidental insertion of wikitext is still an issue, we should focus on other ways to mitigate that issue.",1374687843,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #17)
+> So, let's calm down here.
+> 
+> We're not ""pissing on"" anyone; 
+
+yes you are.
+if you look at the different wikis, and if you search here with ""product=visualeditor"" and ""search word=nowiki"", you will find that one of the main complaints of editors in many projects (specifically enwiki and nlwiki), is the fact that users type ""[[something something]]"", and VE wraps it with ""nowiki"". this is clearly not what the editor meant to do
+
+true, VE also jumps a popup message telling the editor ""this is probably not what you meant"", but there are two issues with that:
+1) because of unrelated bug, this popup message is usually not even seen by the editor.
+2) if the thing is cleaver enough to know that this is not what i meant, why can't it just Do the Right Thing (tm) ? (answer: of course it can, but the team decided to WONTFIX it).
+
+
+this attitude of VE team - pissing on and pissing off the user base at the same time, already caused the editors in nlwiki to vote not to activate it in the planned date (and they can do it - you guys removed the switch - we can bring it back through common.js or through gadgets, and we can also make it ""default"". is a fight with the user base really what you need right now?).
+
+
+why does it seem, with this and other bugs (specifically, insisting on hiding the preference to disable VE), that the VE team made a conscious (or maybe  unconscious) decision to ignore the community and shun it?
+what does the VE team expect to accomplish this way?
+
+
+we want VE and we like VE, but you guys should do a better job listening to us when we tell you where it hurts.
+
+peace.",1374687528,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Thank you very much for the clarification, Erik. I was just about to ask, following comment 17, whether this was truly a wontfix (i.e., patches will not be accepted) or whether it was simply a very low priority. :-)",1374683131,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"""other user interfaces optimized for markup"" -> ""other user interfaces optimized for completing actions quickly in VisualEditor that are fast to do in markup""",1374682618,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Sorry, but this is not something we'll ever do, as I explained in comment 9. It's not simply a matter of prioritization - it's a matter of ensuring we can provide a user experience that's not modeled on markup, but on best user experience practices. As James said, we provide keyboard shortcuts, and will provide other user interfaces optimized for markup. But parsing markup within the visual editing context is completely off the table.",1374682548,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"So, let's calm down here.
+
+We're not ""pissing on"" anyone; we're choosing to prioritise. Right now the devs have got a lot of open bugs for the VisualEditor - things that actively /don't work/. They've got a lot of features still to build, and a lot of expectations about the project. Personally, I'm incredibly impressed with the speed of change and the patches that have been submitted so far - it's a fantastic workrate. But that doesn't change the fact that there's still a lot to do.
+
+Now: we /can/ have wikitext converted to VE-compatible elements. But there are a few costs. First: from my conversations with the developers, I understand that doing it on the fly would slow the VE down very substantially. You'd have to automatically parse and re-render the page. Second: if they work on this, there's a lot of stuff that is going to get pushed back.
+
+We have a VisualEditor. It's great, it's miles better than anything else produced to do this job in MediaWiki, but it still needs a lot of work and still has a lot of active bugs - problems parsing content, problems rendering content. If enhancements such as this (which would certainly be nice) are worked on, active breakage will take a back seat: those areas where it simply doesn't have features will take a back seat. I'm not comfortable with saying that we rate ""being able to type markup into the VisualEditor"" higher than ""being able to manipulate tables"".
+
+As you note, the source editor is still available in all namespaces. Users who are actively prioritising familiarity with syntax, and their muscle memory, are welcome to use it. It's not going away. In the meantime, the VE development process should be focused on making it work full stop, not making it work for the users who are highly comfortable with source editing. That's nice, and it's something I'd love to see, but it's not going to happen if actual bugs aren't fixed first.",1374681807,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #15)
+> If you want an ""accelerator key"" for making links, use the standard one:
+> Ctrl +
+> K (or Cmd + K if you're on a Mac). This is the same shortcut as in Microsoft
+> Word, OpenOffice, Google Docs, Apple Pages and more.
+
+and ""[["" is the same one as used by tens of thousands of wikipedia editors.
+it's not even ""a thing of the past"" - source editor remains the only editor in many name spaces, and is still available in _all_ of them.
+
+pissing on your user base is not a good way to handle software projects.
+
+peace.",1374681409,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"If you want an ""accelerator key"" for making links, use the standard one: Ctrl + K (or Cmd + K if you're on a Mac). This is the same shortcut as in Microsoft Word, OpenOffice, Google Docs, Apple Pages and more.",1374679580,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**turingt** wrote:
+
+For what it's worth, I find that ""[["" is a very good accelerator key - mainly because it's already known and remembered by a huge portion of your user base, myself included.
+
+And Erik, wikitext is still awesome today - it's the only known way to allow users to create semantic-enhanced content. The VisualEditor is good for laying out formatted text on a page, but the relations between concepts placed at different pages are better created by adding tags (links, categories, templates...) to the content. The current VE interface mostly hides those tags and requires handling complex dialogs to introduce or edit them, which makes it less convenient for introducing semantics than wikitext. That's why people is requesting smoother and seamless ways to switch between the VE and the source editor.",1374678026,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"based on:
+
+bug 51554
+bug 51944
+bug 51462
+bug 50527
+
+and a dozen or so more (as seen here:
+https://bugzilla.wikimedia.org/buglist.cgi?query_format=specific&order=relevance%20desc&bug_status=__open__&product=VisualEditor&content=nowiki&list_id=219956
+
+
+i changed this one to ""reopen"" and marked it ""high"".
+
+peace.",1374671097,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,*** Bug 51897 has been marked as a duplicate of this bug. ***,1374639183,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"**nrp** wrote:
+
+WTG guys, piss off the user base even more with a WONTFIX on a no-brainer...",1374599335,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,Marking as WONTFIX per my earlier comments and Erik's.,1373002882,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Indeed, I think we should close this as WONTFIX. We should improve any efficiency or discoverability issues in VisualEditor, and help give users experienced with wikitext clues to not accidentally insert it in VisualEditor. See bug 50601 for one potential approach to the latter problem.
+
+Wiki markup was an awesome in invention in 1995, helping users not have to type HTML in order to format documents. But that doesn't mean the most efficient conceivable user experience in 2013 ought to be bound to the same design principles. (Nor should we blindly copy existing point and click interfaces -- for navigating the complexity of templates and such, we may have to come with some truly novel interfaces.)",1372986063,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #7)
+> (In reply to comment #6)
+> > > (2) it requires the use of a mouse to add a link. :-(
+> > 
+> > Not true, as discussed; I don't use the mouse to add links with VE (Ctrl+K
+> > plus keyboard-based selection, as in other editors).
+> 
+> Ah, right. I vaguely remember that cmd-K controls the hyperlink functionality
+> in Microsoft Office products. I have no idea how anyone would glean this from
+> VisualEditor.
+
+Hover over the button; the tooltip tells you the keyboard shortcut. :-)",1372016154,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #6)
+>> (2) it requires the use of a mouse to add a link. :-(
+> 
+> Not true, as discussed; I don't use the mouse to add links with VE (Ctrl+K
+> plus keyboard-based selection, as in other editors).
+
+Ah, right. I vaguely remember that cmd-K controls the hyperlink functionality in Microsoft Office products. I have no idea how anyone would glean this from VisualEditor.",1372016115,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #5)
+> (In reply to comment #4)
+> > I'm ambivalent about whether we would ever let this go live, given how
+> > complicated it would make editing for people that don't know wikitext -
+> > consequently, marking as lowest priority for now.
+> 
+> You and I discussed this idea at some point (thanks for filing this as a bug,
+> Oliver). The current issues I'm seeing with VisualEditor are that:
+> 
+> (1) it's much more time-consuming to add a link (i.e., typing ""[[]]"" is quick
+> while finding and using the link dialog box is slow, especially multiple
+> times); and
+> 
+> (2) it requires the use of a mouse to add a link. :-(
+
+Not true, as discussed; I don't use the mouse to add links with VE (Ctrl+K plus keyboard-based selection, as in other editors).
+
+> Perhaps we need a ""I'm old school"" checkbox somewhere in VisualEditor. ;-)
+
+If users are sufficiently new-school that they can't remember Ctrl+K I don't think there's much hope for them. :-)",1372015941,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #4)
+> I'm ambivalent about whether we would ever let this go live, given how
+> complicated it would make editing for people that don't know wikitext -
+> consequently, marking as lowest priority for now.
+
+You and I discussed this idea at some point (thanks for filing this as a bug, Oliver). The current issues I'm seeing with VisualEditor are that:
+
+(1) it's much more time-consuming to add a link (i.e., typing ""[[]]"" is quick while finding and using the link dialog box is slow, especially multiple times); and
+
+(2) it requires the use of a mouse to add a link. :-(
+
+Adjusting VisualEditor to interpret [[]] as a link would be a nice enhancement, though I see the danger in heading down this road.
+
+Perhaps we need a ""I'm old school"" checkbox somewhere in VisualEditor. ;-)",1372015712,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"I'm ambivalent about whether we would ever let this go live, given how complicated it would make editing for people that don't know wikitext - consequently, marking as lowest priority for now.",1372015077,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Another possibility I mentioned in bug 49820 is to display a warning of some sorts to remind people that wikicode isn't supported (similar to how LiquidThreads reminds users who insert ~~~~ that their signature will be automatically inserted). Automagical conversion might be better, but a warning could be a good first step.",1371929384,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"Sorry, just clarifying, this wasn't intended to happen ""on save"". This should probably happen as soon as (e.g.) the ]] is typed after a link, à la AutoCorrect.",1371721105,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements,"(In reply to comment #0)
+> a user has suggested
+
+This was me. Here's my comment from [[Wikipedia:VisualEditor/Feedback]]:
+
+> If you look through many of the comments on this page (in some cases you 
+> need to read between the lines), you will see that people are trying to 
+> create a wikilink in VisualEditor using [[ ]] wikitext syntax. I am 
+> suggesting that, to accommodate these users, a sort of autocorrect be 
+> implemented, so that when [[ ]] links are entered, they are automagically 
+> converted into proper VE-style links
+
+As well as a helpful ""transition"" feature from wikitext to VE, it might also be useful in the long run as a shortcut for power users, since keystrokes are generally faster than mouse interaction.
+
+Probably a lower priority enhancement though :)",1371523456,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-gmfhmaeyushutcy45y6x,task_subcomment,NA
+VisualEditor: Some template combinations make text not editable,"On Swedish Wikipedia, we have quite a few bot generated articles (some hundreds of thousands) like this one: https://sv.wikipedia.org/wiki/Macrothemis_ultima
+
+When in editing mode, somehow the first line of text cannot be edited. 
+
+If an article has a second line, it is possible to edit that one (but still not the first line), e.g. https://sv.wikipedia.org/wiki/Lepidosaphes_lithocarpi
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371462960,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-zgrdvieu55b7ilh6yt3l,task_description,resolved
+VisualEditor: Some template combinations make text not editable,Sorry for the disruption; glad we fixed it for you.,1371825507,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zgrdvieu55b7ilh6yt3l,task_subcomment,NA
+VisualEditor: Some template combinations make text not editable,"No, I cannot reproduce it anymore. The update must have taken care of it!",1371538774,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-zgrdvieu55b7ilh6yt3l,task_subcomment,NA
+VisualEditor: Some template combinations make text not editable,"I cannot reproduce this, but we did just update production to the latest code - do you still get this effect?
+
+If so, what browser/OS are you using? Is it possible to do a quick screencast video of how it doesn't work, and attach it to this bug? Thanks!",1371520067,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zgrdvieu55b7ilh6yt3l,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"[From bug 48429 comment 18]
+
+| It would be ideal to have section-edit links for [edit] and [edit source].
+| ie.
+|   Sandbox [edit]
+| replaced with:
+|   Sandbox [edit] [edit source]
+| 
+| I believe this would prevent a LOT of complaints in the short term, and it
+| would permit a lot of us to continue being active beta testers
+| (section-editing is my most frequent type of edit), that it should be High
+| priority, if at all possible. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48429
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49621
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47779
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56337",1371430320,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_description,resolved
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Saying it is fixed does not make it fixed. The link is hidden, and so I don't consider it ""displayed"" as per the current title of this bugzilla thread: ""VisualEditor: Display a link to both VE and wikitext editor on every section header"".
+
+And you did not address my points. I don't want to start another Bugzilla thread, and have to repeat everything there that was written here. Several people in this thread pointed out their dislike of multi-stage processes to be able to click an ""edit source"" link. 
+
+I am concerned about anonymous editors. I know at some point it is likely an option will be provided in preferences to provide registered editors with a direct ""edit source"" link and/or clickable icon (maybe with explanatory tooltip).
+
+But unless a direct ""edit source"" and/or clickable icon link is provided to anonymous editors, then some anonymous editors will edit less. Just like I edited less today, and almost quit editing altogether for the day, due to my annoyance with this multi-stage method, and the many times I messed up.
+
+The point of the visual editor is to get people to edit more, not less. It should not get in the way of editing. It should aid editing. 
+
+Wikia refused to provide registered editors an option to put the source editor tab on top of the visual editor tab. So people had to do a multi-stage process for every single edit in order to get to the source editor. Click edit, then wait tediously for visual editor to load, then click the source tab. For every edit... So many, if not most, regular editors disabled the visual editor in preferences. Feedback and bug reports lessened, especially the best feedback from the best editors. 
+
+Similar to here now. I have to use a multi-stage process to get to the source editor. Aim at ""edit"" link or the line it is on, mouse over that ""edit"" link or line, aim better if necessary, wait for ""edit source"" link to show up, move mouse over to that link, click. Many times I accidentally, or by habit, click the edit link, and then have to click the back button, and start over. So I have to disable the Visual Editor. 
+
+Here is a possible icon method. ""Edit source"" tooltip can show up after mousing over the icon. And the small icon can have a transparent left and right border that makes the area wider for mousing over. So people will have no problem understanding that the icon is an ""edit source"" link. The visible part of the icon will be small, similar in size to the watchlist star at the top of pages. But the clickable part would extend to the left and right a bit to allow easier clicking.",1372374914,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"This matter is fixed. If you want to suggest additional/alternative implementations, please open a new feature request, not re-open a closed one.",1372362973,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Edit and edit source links so confusing I had to disable Visual Editor in preferences today. So you have lost another beta tester. A good one too since I have written many comments and bug reports about VE here and on the Wikipedia feedback page.
+
+I disabled Visual Editor (VE) in preferences today due to constantly clicking the ""edit"" link instead of the ""edit source"" link. I am talking about section editing.
+
+The source editing link only shows up after unintuitively mousing over the edit link and so I am constantly clicking the wrong link. 
+
+I almost always prefer editing with the source editor since I make frequent edits to tables, images, navboxes, templates, and reference formatting. All at a deep level of formatting, placement, refactoring, etc.. I am very fast in the source editor, and VE only edits partially and poorly at deeper levels, if at all.  
+
+It would be better to use an icon for the ""edit source"" links for sections. For ideas:
+*[[commons:User:Timeshifter/Sandbox 10]]
+*[[commons:Category:Square brackets]]
+*[[commons:Category:MediaWiki brackets]]
+
+""edit source"" can show up after mousing over the icon. That is much more intuitive. I did not notice the ""edit source"" link at all for awhile, since I was rapidly clicking the edit link. 
+
+This could drive away many editors. Anonymous editors especially. They have no ability to fix the problem by turning off visual editor in preferences. Many anonymous editors just do not like to log in, and are very used to editing in source editor. Some will be very irritated by the confusing clicking and mousing, just like me.",1372360425,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"**swalling** wrote:
+
+(In reply to comment #22)
+> I was doing my volunteering editing at http://ca.wikipedia.org when all of a
+> sudden I realized the new section double-editing links... 
+> 
+> Well done! I'm glad about everything I said against them, but it is true that
+> I'm also glad about your implementation. A good bridge indeed.
+
+
++1. If we have to live with both edit/edit source for now, this is a pretty elegant implementation.",1372313035,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,Huge thanks. This looks and acts wonderfully.  A good mix of minimal-visuals and maximal-options. Much <3,1372312986,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"I was doing my volunteering editing at http://ca.wikipedia.org when all of a sudden I realized the new section double-editing links... 
+
+Well done! I'm glad about everything I said against them, but it is true that I'm also glad about your implementation. A good bridge indeed.",1372312829,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"This was done in gerrit 69984 which is now merged and will go out this afternoon. Thanks, MatmaRex!",1372279613,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,*** Bug 49950 has been marked as a duplicate of this bug. ***,1371827708,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Edit. Edit source [[]].
+
+Edit. [[]].
+
+-----------------
+
+Edit source [[]]. - At the top of the page. This should be one link covering both the text and the icon. 
+
+That way people are introduced to the shortcut icon for ""edit source"". One possibility: [[]]
+
+Headers will have just the shortcut icon link for ""edit source"": [[]]
+
+Some possibilities for the icon are found here:
+*[[commons:User:Timeshifter/Sandbox 10]]
+
+The graphics lab can quickly produce different icons and variations: 
+*[[Wikipedia:Graphics Lab]]
+*[[Wikipedia:Graphics Lab/Illustration workshop]]",1371747210,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Using an arrow is unintuitive and confusing (no indication what the arrow is actually for; can cause the user to expect the word next to it to be the label for the dropdown, not a separate option entirely especially given the way such arrows operate elsewhere in the skin; results in an extra step/click for something that really might as well be right there; etc). Also doesn't make sense when there are only two options anyway. Just do what James said at the beginning and put in two links.
+
+Later they can stick the edit source option into a tab or something in VE itself, but for now there is no reason to overcomplicate things elsewhere. 
+
+Good:
+
+Sandbox [edit] [edit source]",1371743257,PHID-USER-nv2bu7uh3huvidyjo4lk,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #7)
+> (In reply to comment #6)
+> > I like this idea.  It would be nice if it worked for at least Monobook (in
+> > addition to Vector).
+> 
+> Completely agree. Not sure quite whether this treatment is suitable for
+> Monobook or whether we should invent a different one there?
+
+The section edit links look the same in all skins, this shouldn't look bad. Monobook already has some Vector-y bits tacked on top and this would be just a small icon.
+
+
+(In reply to comment #10)
+> There are also a lot of section edits on most large articles, sometimes in
+> close succession. I think we should be really cautious about enabling
+> multi-level controls and options on something this ubiquitous on a single
+> page.
+
+I'm afraid this doesn't support your argument :)
+
+Only showing one link will prevent users from editing sections of wikitext until they learn to disable the option (or just disable VE entirely), which has been my point all along. Wikitext section editing is the ""default"" mode of operation for many users (at a quick glance at recent changes, around 30-50% of en.wp edits are section edits) and it'd be awful for VE to make it unaccessible.",1371543971,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"I like these bracket icons for the edit source links on headers: 
+[[commons:User:Timeshifter/Sandbox 10]]",1371529452,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #14)
+> The only other short options would be [edit (source)] or [edit (code)], but
+> they're not perfect.
+
+The main problem with that route (which I should have listed, sorry) is that though ""Edit (source)"" works OK in English, it's not a safe expectation for non-English languages to be able to split the actions into two call-to-action labels, one of which is a left sub-string of the first, sadly. Also, it's a bit clunky.",1371527558,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"I agree with James and Matthew on this. 
+
+A preferences toggle, is for things you want to change permanently. 
+
+Whereas this is an instance where I might use VE-section-edit, and use source-section-edit, many times each day, for many months to come.
+
+I really like the arrow-dropdown idea. The cog idea is also good, but would be my second choice. 
+
+The only other short options would be [edit (source)] or [edit (code)], but they're not perfect.",1371521986,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #11)
+> (In reply to comment #8)
+> > Personally I think one of these two are the only viable options. The dropdown
+> > arrow or cog is too much unnecessary choice.
+> 
+> I was assuming if you just click 'edit', it would do the same thing as
+> clicking 'edit' up top (i.e. VE for those users with VE enabled).  Only if 
+> you click the arrow would you see the choice.
+
+Yes, that's exactly our plan - sorry if this wasn't clear. It's available, but not intrusive, and if you click the word ""edit"" link you'll end up in VE at that section.",1371521707,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #11)
+> I was assuming if you just click 'edit', it would do the same thing as
+> clicking 'edit' up top (i.e. VE for those users with VE enabled).  Only if you 
+> click the arrow would you see the choice.
+
+If we do want to avoid the drop-down for non-power users, one idea is to have the preference be like this (possible default shown)
+
+[✓] Show VisualEditor section link
+[ ] Show wikitext section link
+
+You could check either, both (in which case you get some control for choosing, possibly the drop-down), or neither (no section links, which is already an option).",1371521678,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #8)
+> Personally I think one of these two are the only viable options. The dropdown
+> arrow or cog is too much unnecessary choice.
+
+I was assuming if you just click 'edit', it would do the same thing as clicking 'edit' up top (i.e. VE for those users with VE enabled).  Only if you click the arrow would you see the choice.
+
+> Most new editors will appreciate defaulting to VE, and
+> for power users who need edit source, this is where having a preference to 
+> change your default to edit source would come in handy (a preference I am 
+> guessing would free us up to also move ""Edit source"" at the top of the page in 
+> to a dropdown).
+
+As a power user, I agree with James.  Having both available on every section greatly increases the odds I'll continue to test VE when possible (and report bugs), while using wikitext when I know I have to.  Having power users opt out for all VE section edits is not conducive to that.",1371521421,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"**swalling** wrote:
+
+(In reply to comment #9)
+> (In reply to comment #8)
+> > > * ""[edit]"" going to one place unless you've got a preference in which case it
+> > > goes to another is… confusing
+> > > 
+> > > * ""[edit]"" OR ""[edit source]"" if you've got a preference is a bit messy, but
+> > > not that bad
+> > 
+> > Personally I think one of these two are the only viable options. The dropdown
+> > arrow or cog is too much unnecessary choice. The point of section edit links
+> > is to enable speedy editing of single sections, so introducing a dropdown is
+> > overloading things. Most new editors will appreciate defaulting to VE, and
+> > for power users who need edit source, this is where having a preference to
+> > change your default to edit source would come in handy (a preference I am
+> > guessing would free us up to also move ""Edit source"" at the top of the page in
+> > to a dropdown).
+> 
+> I disagree. I would say that, as an axiom, preferences are bad; they add
+> complexity for coders (expensive), bug testers (irritating) and most
+> importantly users (alienating).
+> 
+> In this case, we would also lose momentum as many power users might early-on
+> opt out of VisualEditor for section edits, and so never use it as much as
+> we'd
+> hope. We would lose their input, their bug reports and most importantly their
+> enculturation for new users of this being the 'right' way to edit. We don't
+> want another Vector roll-out disaster on our hands; ever day that Monobook
+> remains on the servers is another notch on that failure yardstick. :-(
+
+On the other hand, you potentially distract and confuse the heck out of new users by presenting a dropdown to edit source when they were about click edit. The conceptual difference between ""edit"" and ""edit source"" is not crystal clear to people who don't know the differences between VE and wikitext up front. 
+
+There are also a lot of section edits on most large articles, sometimes in close succession. I think we should be really cautious about enabling multi-level controls and options on something this ubiquitous on a single page.",1371521332,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #8)
+> > * ""[edit]"" going to one place unless you've got a preference in which case it
+> > goes to another is… confusing
+> > 
+> > * ""[edit]"" OR ""[edit source]"" if you've got a preference is a bit messy, but
+> > not that bad
+> 
+> Personally I think one of these two are the only viable options. The dropdown
+> arrow or cog is too much unnecessary choice. The point of section edit links
+> is to enable speedy editing of single sections, so introducing a dropdown is
+> overloading things. Most new editors will appreciate defaulting to VE, and
+> for power users who need edit source, this is where having a preference to
+> change your default to edit source would come in handy (a preference I am
+> guessing would free us up to also move ""Edit source"" at the top of the page in
+> to a dropdown).
+
+I disagree. I would say that, as an axiom, preferences are bad; they add complexity for coders (expensive), bug testers (irritating) and most importantly users (alienating).
+
+In this case, we would also lose momentum as many power users might early-on opt out of VisualEditor for section edits, and so never use it as much as we'd hope. We would lose their input, their bug reports and most importantly their enculturation for new users of this being the 'right' way to edit. We don't want another Vector roll-out disaster on our hands; ever day that Monobook remains on the servers is another notch on that failure yardstick. :-(",1371520516,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"**swalling** wrote:
+
+
+> * ""[edit]"" going to one place unless you've got a preference in which case it
+> goes to another is… confusing
+> 
+> * ""[edit]"" OR ""[edit source]"" if you've got a preference is a bit messy, but
+> not that bad
+
+Personally I think one of these two are the only viable options. The dropdown arrow or cog is too much unnecessary choice. The point of section edit links is to enable speedy editing of single sections, so introducing a dropdown is overloading things. Most new editors will appreciate defaulting to VE, and for power users who need edit source, this is where having a preference to change your default to edit source would come in handy (a preference I am guessing would free us up to also move ""Edit source"" at the top of the page in to a dropdown).",1371520133,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #6)
+> I like this idea.  It would be nice if it worked for at least Monobook (in
+> addition to Vector).
+
+Completely agree. Not sure quite whether this treatment is suitable for Monobook or whether we should invent a different one there?",1371519315,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,I like this idea.  It would be nice if it worked for at least Monobook (in addition to Vector).,1371516381,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"Having discussed, we think we've found a design that's consistent with other usage: instead of having ""[edit | edit source]"" or ""[edit ⚙]"", we will have ""[edit ▾]"" with the down-arrow expanding to a menu (in the same way that Vector does) for ""edit source""). This is still easily accessible for users and open for all users, not just those with a preference, but does not take lots of screen estate (problem with the first possibility), and is easily discoverable (second possibility).",1371515280,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #3)
+> I like ""[edit ⚙]"" more - what do you think? MatmaRex discussed this with me
+> last night.
+
+So if you click 'edit', it always goes to VE, and if you click ⚙ (first time I saw the 'gear' character, but good usage), it always goes to wikitext?
+
+That seems reasonable if the wikitext target is big enough that it's not frustrating to click.",1371499202,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"(In reply to comment #2)
+> There is much discussion at bug 48429 about the need for both types of edit
+> links on every header. 
+> 
+> What might also work is an ""edit"" link (for VisualEditor) and an icon that
+> when
+> clicked will take one to the source editor for that section. The icon would
+> have a popup tooltip that says ""edit source"". It would show up when the mouse
+> cursor is run over the icon.
+
+My concern with this area is three fold:
+
+* ""[edit] [edit source]"" is a huge amount of extra chrome/clutter to enable for all users
+
+* ""[edit]"" going to one place unless you've got a preference in which case it goes to another is… confusing
+
+* ""[edit]"" OR ""[edit source]"" if you've got a preference is a bit messy, but not that bad
+
+I like ""[edit ⚙]"" more - what do you think? MatmaRex discussed this with me last night.",1371498837,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"There is much discussion at bug 48429 about the need for both types of edit links on every header. 
+
+What might also work is an ""edit"" link (for VisualEditor) and an icon that when clicked will take one to the source editor for that section. The icon would have a popup tooltip that says ""edit source"". It would show up when the mouse cursor is run over the icon.",1371472595,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Display a link to both VE and wikitext editor on every section header,"See comment 23 and 24, at Bug 48429 wherein Bartosz Dziewoński has submitted a patch to Gerrit.
+
+(""https://gerrit.wikimedia.org/r/68868 (Gerrit Change
+I13bbb9549c999bb7301bbcf530706a813184425d)"")
+
+If his patch isn't accepted, then I would again urge High Priority for an alternative fix.",1371431206,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-tqom52xzffar63gwv2th,task_subcomment,NA
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,"In general, ""everything"" is allowed (text; annotations; inline and block images; headings; lists; HTML blocks; entities; transclusions; references; etc.), except for:
+
+Image captions
+-> No lists
+
+References
+-> No references (but transclusions of {{#tag:ref|text}} get around this for one level as an out ref; eww)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50459",1371422340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-osst63lnijz6dlmc57xi,task_description,resolved
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,This was completed by the toolbar re-write that was merged for the 12 September release; moving bug 50459 from a blocker (which was wrong anyway) to a see-also.,1379657458,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-osst63lnijz6dlmc57xi,task_subcomment,NA
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,"The references dialog has no references button already. Not sure about image captions as their broken on my local copy, but the code is there to specify the toolbar for each dialog.",1371816425,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-osst63lnijz6dlmc57xi,task_subcomment,NA
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,"Re references: yeah, that struck me as highly likely to confuse people (and highly unnecessary) when I saw it.",1371535012,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-osst63lnijz6dlmc57xi,task_subcomment,NA
+VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs,"Examples for captions:
+
+https://www.mediawiki.org/wiki/VisualEditor:TestImageCaptions
+
+Examples for references:
+
+https://www.mediawiki.org/wiki/VisualEditor:TestReferenceContents",1371422391,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-osst63lnijz6dlmc57xi,task_subcomment,NA
+Show change tags on edit diff views,"From bug 49602 comment 0:
+
+| 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).
+
+This is said request for a core change for this to be possible. :-)
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1371419460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-acs2ekfum76g27vb7duj,task_description,resolved
+Show change tags on edit diff views,"
+
+%%%*** This bug has been marked as a duplicate of bug 25824 ***%%%",1373019604,PHID-USER-lptfllsuhn22a4praqqo,True,PHID-TASK-acs2ekfum76g27vb7duj,task_subcomment,NA
+VisualEditor: Make some way to display display-less content (e.g. silent transclusions like {{lowercase title}}),"https://en.wikipedia.org/wiki/User:%C3%8F%C2%BF%C2%BD?veaction=edit
+
+If a template has no output (such as <https://en.wikipedia.org/wiki/Template:Lowercase_title>), it has no visible output and becomes very easy to silently remove using VisualEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49667",1371357660,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-uoptaiss5vhdq32dkswe,task_description,resolved
+VisualEditor: Make some way to display display-less content (e.g. silent transclusions like {{lowercase title}}),"(In reply to comment #2)
+> Is this the same as bug 49806? (I know that's newer but it has a lot more
+> discussion)
+
+It is indeed; merged.
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1374086311,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uoptaiss5vhdq32dkswe,task_subcomment,NA
+VisualEditor: Make some way to display display-less content (e.g. silent transclusions like {{lowercase title}}),Is this the same as bug 49806? (I know that's newer but it has a lot more discussion),1374084075,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-uoptaiss5vhdq32dkswe,task_subcomment,NA
+VisualEditor: Make some way to display display-less content (e.g. silent transclusions like {{lowercase title}}),"I don't see how this is an enhancement request. It's trivial to accidentally remove a template that has no output, resulting in damage to the page (irreversible damage in the context of using only VisualEditor).",1371441632,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-uoptaiss5vhdq32dkswe,task_subcomment,NA
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,"https://en.wikipedia.org/wiki/Digital_Forensics_XML?veaction=edit
+
+I went there, I changed a header from h3 to h2 by selecting the header and using the drop-down menu. When I click ""Page settings"" and then close the dialog box without making any changes, my change to the header is inexplicably lost.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371355920,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-zuh52jc2toouqelcucf4,task_description,resolved
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,Merged and will go out with wmf8.,1371584527,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zuh52jc2toouqelcucf4,task_subcomment,NA
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,Related URL: https://gerrit.wikimedia.org/r/69316 (Gerrit Change Ieb2e9e361afe057af93c4d374acc85df58bfb4c3),1371571111,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zuh52jc2toouqelcucf4,task_subcomment,NA
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,"Not quite, it's just doing it without checking if a new breakpoint was actually added.",1371571069,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-zuh52jc2toouqelcucf4,task_subcomment,NA
+VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway,"This looks like the code to ""undo changes made in the dialog when they don't apply them"" is doing that once too often.",1371431146,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zuh52jc2toouqelcucf4,task_subcomment,NA
+VisualEditor: mw:Placeholder issue,"If there are 2 blank lines (line breaks) then the paragraph immediately after is uneditable (green striped overlay).
+
+Confirm here: http://en.wikipedia.org/w/index.php?title=User:Quiddity/sandbox&oldid=560048320
+
+and see thread here: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Paragraph_editing_disabled.3F.3F.3F
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371319260,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-oe6mridn2bnwc6ynf3en,task_description,resolved
+VisualEditor: mw:Placeholder issue,This now works; you won't get blank lines causing the next line to be unable to be edited. Thanks for the bug report!,1371516882,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oe6mridn2bnwc6ynf3en,task_subcomment,NA
+VisualEditor: mw:Placeholder issue,This (and similar issues if you have an HTML comment on a paragraph double-line  before some content) is caused by bug 47403; I won't mark this as a duplicate of that one because we're still trying to get a comment as to what will break in VE if Parsoid reverts the hack that causes this.,1371425386,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oe6mridn2bnwc6ynf3en,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"VisualEditor should display HTML comments, which are often used as notes or warnings to other editors.  It would be nice if they were editable too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49608
+https://bugzilla.wikimedia.org/show_bug.cgi?id=46440
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49806
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53659",1371261360,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_description,resolved
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Change 140773 merged by jenkins-bot:
+[BREAKING CHANGE] Show comments inline to the user
+
+https://gerrit.wikimedia.org/r/140773",1406160260,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Change 140773 had a related patch set uploaded by Jforrester:
+[WIP] Show comments inline to the user
+
+https://gerrit.wikimedia.org/r/140773",1403205835,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),*** Bug 52036 has been marked as a duplicate of this bug. ***,1393271493,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),*** Bug 51732 has been marked as a duplicate of this bug. ***,1390416862,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(And of course, this means comments can not be easily deleted right now, in case they display obsolete information, for example.)",1379933298,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"It should go without saying, but another consequence of this, beyond the comment being ignored, is that it can easily be misplaced, ending up in places where it does not belong and it does not make much sense, as user:Fram points out at en.wp today.",1379932587,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"I've just discovered that, at present at least, <!-- blah --> does not get nowikied so html comments are creatable in VE but not visible once saved so this functionality really very useful yet.
+Other HTML tags do get nowikied so this behaviour may subsequently change - see [[Wikipedia:VisualEditor/Feedback#HTML comments not nowikied - should they be?]]",1378460438,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Like Pam I think it is best that these notices are visible and in-your-face so there is no doubt that you have seen them. Hover also causes issues on touch screen devices I think.
+
+One thing that would be possible would be for there to be an icon associated with the comment that collapsed it to get a more WYSIWYG view (and then expanded it again on a subsequent click). The default display would be shown. I guess that custom css/js to have them hidden by default would be possible if people wanted, but I don't suggest the devs do anything other than make it possible for users to write this. I don't know how difficult any of this would be to program though.
+
+On the issue of rendering, I know that some comments contain links, for example from [[Patrick Stewart]]: <!--Do not change this to KBE, see [[Knight Bachelor]]-->
+Obviously this is shown like any other link in the source editor, but it makes it clear that it is a link to an article and people with navpopups can select it and get a preview of the link. If VE could parse links (and I guess external links) then that would be a nice to have.",1377774240,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #18)
+> I agree with James Forrester that this should be done in stages, and that the
+> first stage would be to ""show comments and let them be deleted.
+> 
+> In terms of isolating hidden (aka ""invisible"") comments, the logic is pretty
+> much the same as for templates, except easier: look for <!-- as the left
+> boundary, then look for --> as the right boundary. Treat the result as a
+> block
+> that can be deleted or moved.
+> 
+> Looking at https://en.wikipedia.org/wiki/Help:Hidden_text , it's not clear
+> that
+> text within an invisible comment is essentially nowikied, but that is in fact
+> the case, because - by definition - the text can't be seen in either read or
+> preview mode. From a programming viewpoint, this means that even if, for
+> example, there is an http link within the comment, or a reference - both
+> quite
+> possible - no rendering is needed: all text should be treated as text, NOT
+> interpreted.
+> 
+Of the two options I would be much happier with (1): in many circumstances these comments need to be obvious to the naive editor, who will not necessarily have the savvy or curiosity to hover over an icon. Please display these comments clearly on screen for all editors, at the point in the article where they have been inserted: different font on coloured background sounds good.
+
+> What the person doing the edit sees is really the critical question. It seems
+> to me that there are two options:
+> 
+> (1) Display as a text, mixed in with regular text, but in a different color
+> font and background color. This is what is done with templates. Regarding the
+> color: Hidden comments are typically warnings/notices to editors, so perhaps
+> yellow? The font/coloring will, ideally, make it clear that the text is not
+> part of the article. 
+> 
+> (2) Treat like a comment in Excel - put a character (I suggested a warning
+> icon
+> - see http://findicons.com/search/warning; in yellow) into the visible text
+> that, when a person hovers on the icon, displays the hidden/invisible text.
+> While this is less visible to editors, in some sense - they have to hover to
+> read - it's more visible in the sense that hidden comments, in wikitext
+> editing
+> mode, are in the same font as everything else, and thus less likely to be
+> noticed than a bright yellow warning icon.
+> 
+> Option (2) lends itself nicely to the second phase mentioned by James: Here
+> there would be an icon on the toolbar, for adding a new comment. In addition,
+> if a person hovers over an existing comment, then an editing icon appears
+> nearby, which allows the person to edit the comment or to delete it [via
+> trashcan icon].",1377758963,PHID-USER-7zhn2ep5wvjhxetsbb6n,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #18)
+> In terms of isolating hidden (aka ""invisible"") comments, the logic is pretty
+> much the same as for templates, except easier: look for <!-- as the left
+> boundary, then look for --> as the right boundary. Treat the result as a
+> block that can be deleted or moved.
+
+The parsing part is solved.  Comments are already preserved (as HTML comments) in the Parsoid DOM.",1377752273,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"I agree with James Forrester that this should be done in stages, and that the first stage would be to ""show comments and let them be deleted.
+
+In terms of isolating hidden (aka ""invisible"") comments, the logic is pretty much the same as for templates, except easier: look for <!-- as the left boundary, then look for --> as the right boundary. Treat the result as a block that can be deleted or moved.
+
+Looking at https://en.wikipedia.org/wiki/Help:Hidden_text , it's not clear that text within an invisible comment is essentially nowikied, but that is in fact the case, because - by definition - the text can't be seen in either read or preview mode. From a programming viewpoint, this means that even if, for example, there is an http link within the comment, or a reference - both quite possible - no rendering is needed: all text should be treated as text, NOT interpreted.
+
+What the person doing the edit sees is really the critical question. It seems to me that there are two options:
+
+(1) Display as a text, mixed in with regular text, but in a different color font and background color. This is what is done with templates. Regarding the color: Hidden comments are typically warnings/notices to editors, so perhaps yellow? The font/coloring will, ideally, make it clear that the text is not part of the article. 
+
+(2) Treat like a comment in Excel - put a character (I suggested a warning icon - see http://findicons.com/search/warning; in yellow) into the visible text that, when a person hovers on the icon, displays the hidden/invisible text. While this is less visible to editors, in some sense - they have to hover to read - it's more visible in the sense that hidden comments, in wikitext editing mode, are in the same font as everything else, and thus less likely to be noticed than a bright yellow warning icon.
+
+Option (2) lends itself nicely to the second phase mentioned by James: Here there would be an icon on the toolbar, for adding a new comment. In addition, if a person hovers over an existing comment, then an editing icon appears nearby, which allows the person to edit the comment or to delete it [via trashcan icon].",1377735584,PHID-USER-hirrhium5ibrtof34lwa,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"resetting priority to high. I didn't intend to change it and didn't realise I had, sorry.",1377724382,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"John Broughton suggests as a first step that hidden comments could very easily be made visible but not editable. He suggests putting the comments in a different colour, possibly white on black, to distinguish them from regular content.
+
+Obviously being able to edit hidden comments is needed functionality too, but that is less urgent than displaying them.",1377724285,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"It has been reported on en.wp today that a user of VE was:
+[..] continually making changes to articles contrary to comments in the wikisource (''two examples of such comments being ""<!-- DO NOT CHANGE THIS NATIONALITY WITHOUT DISCUSSION ON TALK PAGE -->""  and ""<!-- This is, as Wikipedia guidelines suggest, as he self-identifies and by long-term consensus -->"")
+
+This bug is already marked as high priority and has been for over 2 months. It really needs to be fixed before much longer.",1377721939,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"**ignatzmice.wiki** wrote:
+
+Bump. https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=567981801",1376162739,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Another example: http://en.wikipedia.org/w/index.php?title=Jacques_Lacan&diff=566246717&oldid=561090875 We are getting multiple reports about this specific issue, so thanks for your attention on this.",1375547447,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Example of edit where displaying the hidden comment would have been very useful (because the edit goes against what is stated in the comment) :
+http://en.wikipedia.org/w/index.php?title=List_of_English-language_book_publishing_companies&curid=746089&diff=564359255&oldid=563535930",1373895474,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Is there any progress or movement on this? Specifically, will hidden comments at least be displayed by the Monday deployment?",1373875721,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #9)
+> (In reply to comment #8)
+> > I don't think it was officially decided.  Most likely, it will be wikitext
+> > first, but that could change if the VE API is ready.
+> 
+> I don't know what you mean by ""the VE API"", let alone it being ""ready"". :-)
+> 
+> We negotiate with people to build whatever hooks they need (and we felt were
+> justified) in the normal way. However, a commenting system like this feels
+> more like core VE work than a plugin
+
+Okay, based on that, I think it makes sense not to use VE for the inline comment prototype.",1371498950,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #8)
+> I don't think it was officially decided.  Most likely, it will be wikitext
+> first, but that could change if the VE API is ready.
+
+I don't know what you mean by ""the VE API"", let alone it being ""ready"". :-)
+
+We negotiate with people to build whatever hooks they need (and we felt were justified) in the normal way. However, a commenting system like this feels more like core VE work than a plugin (so it wouldn't be a matter of hooks available for code in general); it'd sit well with the planned real-time collaborative editing functionality we're building in the new financial year, for which a chat/comment-like tool would be wanted.",1371429119,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"I don't think it was officially decided.  Most likely, it will be wikitext first, but that could change if the VE API is ready.",1371426788,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #6)
+> (In reply to comment #5)
+> >The second phase might be postponed indefinitely if the ""co-ment"" work comes to something. A treatment for in-line comments will be needed; possibly just a span of some kind. Will look at this.
+> 
+> I'm mentoring that (along with Tyler).  I don't think Richa's looked yet at
+> integrating with VE.  But it's still early. If you think the VE API is mature
+> enough that it integration is feasible, you can suggest that at bug 46440.
+
+I know - see your own comment at bug 46440 comment 13 :-) - but I thought that the proposal was to build this for wikitext editor and then we'd take on porting it over to VE once it was done?",1371425605,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #5)
+>The second phase might be postponed indefinitely if the ""co-ment"" work comes to something. A treatment for in-line comments will be needed; possibly just a span of some kind. Will look at this.
+
+I'm mentoring that (along with Tyler).  I don't think Richa's looked yet at integrating with VE.  But it's still early. If you think the VE API is mature enough that it integration is feasible, you can suggest that at bug 46440.",1371424966,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"(In reply to comment #4)
+> Quiddity, yeah, I know, I just filed that (bug 49608).
+
+For clarity, that's a problem with HTML comments in transclusions rather than in general, which does still work. Sorry. :-(
+
+We'd probably need to do this enhancement in stages - first, show comments and let them be deleted; later, make them editable and creatable. The second phase might be postponed indefinitely if the ""co-ment"" work comes to something. A treatment for in-line comments will be needed; possibly just a span of some kind. Will look at this.",1371420628,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"Quiddity, yeah, I know, I just filed that (bug 49608).",1371265691,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"That bug isn't fixed then (or was re-broken), because Hidden Comments are being deleted when we save.
+
+(This problem is now worse, because it is now only noticeable if we opt to ""Review your changes"" before saving.)
+
+See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Removal_of_comments_in_Infobox
+and test with adding text anywhere in the article http://en.wikipedia.org/wiki/Bleak_House for example. It always removes the comments from the infobox.
+
+There are additional threads on that page mentioning the same thing.",1371265603,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),I don't think so.  That one's just about preventing them from being silently removed on save.  This is about actually displaying them to the editor.,1371264951,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable),"I think this is a duplicate of Bug 42124 ?
+
+It doesn't specifically mention HTML or Hidden, so I'm not positive.",1371264902,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-nvkr7m44ao53f5uftwjr,task_subcomment,NA
+VisualEditor: Swallowing of empty text annotations leads to dirty diffs and unexpected Parsoid normalisation,"VisualEditor caused this dirty diff (https://en.wikipedia.org/w/index.php?title=List_of_South_Korean_idol_groups_%282010s%29&diff=559356009&oldid=559228059) when editing a table.  Note the removal of the empty small elements, and the change to the align syntax.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371258600,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-r3xcog5g6murfqlx2fpo,task_description,resolved
+VisualEditor: Swallowing of empty text annotations leads to dirty diffs and unexpected Parsoid normalisation,"(In reply to comment #0)
+> VisualEditor caused this dirty diff
+> (https://en.wikipedia.org/w/index.
+> php?title=List_of_South_Korean_idol_groups_%282010s%29&diff=559356009&oldid=5
+> 59228059)
+> when editing a table.  Note the removal of the empty small elements, and the
+> change to the align syntax.
+
+The removal of empty text annotations has been fixed as of wmf7 (gerrit 68213 and gerrit 68190), which is now deployed a week early on enwiki to fix this and other issues - sorry about that. This will stop ""the removal of the empty small elements"", and consequently the changes to the table syntax that Parsoid does on lines that aren't otherwise changed.
+
+The non-semantic syntactical change of the HTML syntax is, I believe intentionally  done by Parsoid to normalise the wikitext; it is only done on lines of wikitext that are changed anyway by user action (unless there's a bug in VisualEditor which causes the contents of the HTML to change unexpectedly, as was the case here).
+
+Consequently marking as ""fixed"".",1371419290,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r3xcog5g6murfqlx2fpo,task_subcomment,NA
+VisualEditor: Revive Inez's way of doing sub-surfaces,"Per Roan - ""we were initially going to use this for references and captions, and then chose to use separate documents instead, but this is not compatible with the collaborative editing work; a VE instance should be able to collaborate with another instance on the same page, although I suppose there was some stuff about limiting the scope successfully as well"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371181800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-s72q22vgyujmcogxkisx,task_description,declined
+VisualEditor: Revive Inez's way of doing sub-surfaces,Instead we're going to go with sub-documents directly.,1416360265,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-s72q22vgyujmcogxkisx,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,"Clicking the section edit link into VE has three minor issues:
+
+* The cursor is positioned at the start of the heading of that section; it should probably go to the start of the next element straight after the section (in most cases, a paragraph)
+* The page doesn't actually scroll to the correct area; ideally the page should be deliberately scrolled to that section (as it happens, you normally end up on roughly the right part because the page is already scrolled, but there are cases where VE pages are lengthier or shorter than PHP pages and so this can't be relied upon).
+* The toolbar only appears once you scroll (because it's triggered on page movement, and the page doesn't move at first to get to the section because it's already there) - this means that it suddenly pops into view a bit too late.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371180060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zptqvqstkrfianknvktj,task_description,resolved
+VisualEditor: Section edit link behaviour tweaks,"Both changes merged, so marking as fixed.",1372109901,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,#3 in your list is fixed by #2,1372102079,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,^^^ Moves cursor to next non-heading,1372101985,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,Related URL: https://gerrit.wikimedia.org/r/70238 (Gerrit Change I6fcc463aeeae40278f5caf04ae251c8ecfe65472),1372101813,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,^^^ Fixes scroll,1372100335,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: Section edit link behaviour tweaks,Related URL: https://gerrit.wikimedia.org/r/70229 (Gerrit Change I3a57e64f54289a3263814b4fbfe00c63de4a490b),1372100128,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zptqvqstkrfianknvktj,task_subcomment,NA
+VisualEditor: CSS broken in RTL,"We have plans to use ResourceLoader which will fix a lot of this, but noting it here.
+
+Most obviously, the toolbar has two sections which in LRT appear as ABCDE  1234; in RTL they should be 4321  EDCBA, but instead appear as EDCBA  4321. Also issues in dialogs etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1371155280,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-o4e72bpfvnzueqs77k5k,task_description,resolved
+VisualEditor: CSS broken in RTL,"(In reply to comment #2)
+> This is fixed in general by the introduction of Roan and Trevor's css-frame
+> fixes, and the popup menu fixes (in TextMenuWidget) - and I think that the
+> rest would likely result in spot-fixes, like the ones with the transclusion
+> editor.
+> 
+> Also, as far as I could see, the toolbar bug was fixed as well.
+> 
+> I think we can close this bug and rely on the main BIDI/RTL tracking bug to
+> continue work on any individual bugs as they happen.
+
+OK, done.",1374592563,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-o4e72bpfvnzueqs77k5k,task_subcomment,NA
+VisualEditor: CSS broken in RTL,"This is fixed in general by the introduction of Roan and Trevor's css-frame fixes, and the popup menu fixes (in TextMenuWidget) - and I think that the rest would likely result in spot-fixes, like the ones with the transclusion editor.
+
+Also, as far as I could see, the toolbar bug was fixed as well.
+
+I think we can close this bug and rely on the main BIDI/RTL tracking bug to continue work on any individual bugs as they happen.",1374592211,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-o4e72bpfvnzueqs77k5k,task_subcomment,NA
+VisualEditor: CSS broken in RTL,"I went through the Link Inspector CSS issue and it gave me an insight into what may be happening here. 
+
+Using CSSJanus will probably help 90% of this problem, but it might not completely solve it. A lot of the position settings are inline, calculated dynamically and inserted into the element itself. I'm not entirely sure CSSJanus knows how to deal with those. We may have to split the calculation up into RTL and LTR positions, or find some other solution to the popups that are calculated dynamically.",1371575347,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-o4e72bpfvnzueqs77k5k,task_subcomment,NA
+VisualEditor: Incorrectly handling nested reference tags (blocked by Parsoid),"This is a particular problem with 'note' sections, and references used as notes; they commonly include citations for their statements, and you end up with markup that looks like <ref> some text here <ref> a citation for that text</ref></ref>
+
+The VE is for some reason displaying it as a citation template, ""some text here"", a second citation template and a random </ref> tag. See note 1 in https://en.wikipedia.org/wiki/Fomitiporia_ellipsoidea for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371143340,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-comswpptjs3uwf7ztbnb,task_description,resolved
+VisualEditor: Incorrectly handling nested reference tags (blocked by Parsoid),"This is now ""fixed"" (but we may want to make it a nicer experience in the future).",1371782246,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-comswpptjs3uwf7ztbnb,task_subcomment,NA
+VisualEditor: Incorrectly handling nested reference tags (blocked by Parsoid),"This is because Parsoid doesn't support the ""#tag:ref"" hack to let you do multi-level references (which were explicitly not allowed because of the insanity this creates :-)).
+
+Creating a secondary bug (VE currently assumes you can't have nested references, which is indeed what Parsoid gives us), bug 49555. Once Parsoid supports this, we'll need to check that we correctly handle this from a UX perspective (amongst other things).",1371168461,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-comswpptjs3uwf7ztbnb,task_subcomment,NA
+VisualEditor: Dropdown text style menu overlaps with other interface elements,"See https://upload.wikimedia.org/wikipedia/en/8/8f/Visual_editor_pulldown_menu_problem.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371122520,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mu7u3eco45xxsfwg4vhq,task_description,resolved
+VisualEditor: Dropdown text style menu overlaps with other interface elements,This was fixed in the re-write of the toolbar two weeks ago; sorry for not updating until now.,1372007755,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mu7u3eco45xxsfwg4vhq,task_subcomment,NA
+VisualEditor: Dropdown text style menu overlaps with other interface elements,"(In IE9, I'd note).",1371122580,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mu7u3eco45xxsfwg4vhq,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","Have a link [[Foo]] which is a redirect to [[Foobar]].
+
+Inspect link; it will suggest:
+
+New pages
+  Foo
+Existing pages
+  Foobar
+
+This is because ""Foo"" does not come back in the list of pages you can link to - which is filtered to remove redirects - but we should special-case the existing link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50240",1371075060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_description,declined
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","AFAICT this underlying bug was fixed in October; the issue that MediaWiki's search system sometimes comes back with bad results from time to time (falsely claiming that short titles don't exist) is distinct, as part of bug 54361.",1395441844,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","Another couple of examples I found:
+I write Indian religion, select the two words and try to add the relevant link; it doesn't recognize the page as an existing redirect, while it lists Indian religions as ""matching page"".
+Same story for Tafkap; in this case, a couple of all caps variants are listed as redirects.
+In these cases the ""click in the text field"" trick didn't work.",1394543448,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","There are a bunch of bugs about this, so I'm pretty sure I'm adding my comment to the wrong one :D
+Anyway, it is possible that the inspector does not recognize immediately a page as an existing redirect. See https://en.wikipedia.org/wiki/File:VE_wrong_link_state_in_link_editor.png .
+https://en.wikipedia.org/wiki/New_York_Kennedy is a valid redirect page.
+Unfortunately this is not easy to reproduce. 
+(I never managed to do it by just typing New York Kennedy and then wikiling those words, anyway.)
+I sometimes managed to reproduce by selecting a completely random word (or even more than one), clicking on the chain icon, writing New York Kennedy in the dialog. Every time though it does correct itself if, after observing the same result from the screenshot above, you click again in the text field, so the page will correctly appear as a blue link listed as a redirect.",1394541885,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",James couldn't either so RESOLVED WORKSFORME,1391312264,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",I can't reproduce this bug.,1391312206,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","Many redirects exist because they respond to expected (simplified) alternative names, plurals, synonyms, non-complete names of people and places, and popular uses in general. It is likely that these popular uses are also used in articles. When selecting a word, the difference between VE recognizing or not these redirects is important:
+
+* If the redirect is recognized and the destination page is shown, most editors will understand the difference and will choose the complete name.
+
+* If the redirect is not shown then you can be a lazy editor and insert the link (having no idea whether it will result in a red or blue link), you can avoid the link altogether just in case, or you can be a good editor (as I try to be), open a new tab, and search that term only to find that many times such term is a known redirect.
+
+Do the latter 20 times in a long article and you will come to this bug report as I did. I found this to be a big nuisance in real editing. (with the side benefit that I tested Cirrus Search more and I even found a bug, thanks to these deviations caused by VE)
+
+PS: or simply show the redirects in italics, as they are already displayed in some MediaWiki lists.",1390032494,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",*** Bug 59208 has been marked as a duplicate of this bug. ***,1390024134,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","I'd say the desired behavior would be that the link inspector show the existing redirect in different way (such as blue but with a parenthetical note that this is a redirect).
+
+In most cases, the link to the target article is the preferred link choice, but in many cases the redirect is also valid. For cases where the redirect points to a subsection, the redirect is probably the preferred link most of the time.",1377278376,PHID-USER-nyv6rqxnzdy3oe323a3d,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",*** Bug 50274 has been marked as a duplicate of this bug. ***,1373519588,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages","In my local copy, the redirect URL is not filtered out, but I did notice another bug in that code: https://gerrit.wikimedia.org/r/69871",1371830218,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+"VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages",*** Bug 49540 has been marked as a duplicate of this bug. ***,1371153385,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cdmjeut7byvwilwzjfyv,task_subcomment,NA
+VisualEditor: Capitalisation does not register as a change,"If someone capitalises a character(see https://en.wikipedia.org/w/index.php?title=Founder_effect&diff=559607253&oldid=558757694 for example) the VisualEditor does not recognise it as an alteration to page text and rejects their edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371063300,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-clapsacnmffdpmc6uic3,task_description,resolved
+VisualEditor: Capitalisation does not register as a change,"Filed 53210 for my last comment which I see it now, it was unrelated.",1377174192,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-clapsacnmffdpmc6uic3,task_subcomment,NA
+VisualEditor: Capitalisation does not register as a change,It is actually being reported now on itwp: in order to do this http://it.wikipedia.org/w/index.php?title=DNasi_attivata_da_caspasi&diff=60101664&oldid=60089990 I had to delete the word and link it back again. Our guidelines about style require pages in that section to appear with the capital letter. I'll also add a link to https://bugzilla.wikimedia.org/show_bug.cgi?id=50452 which looks related. Thanks.,1373719943,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-clapsacnmffdpmc6uic3,task_subcomment,NA
+VisualEditor: Capitalisation does not register as a change,Ed's fix on Friday corrected this; sorry for the bug. Now live in production.,1372015558,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-clapsacnmffdpmc6uic3,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,"Screenshot
+
+See associated screenshot - this is for https://www.mediawiki.org/wiki/Template:Extension
+
+When clicking the inspector icon, the window opens up but remains entirely blank and happily sits there like it for minutes* at a time. More worryingly, if I follow the normal workflow for a broken element (hit the X, make it go away, try and open it again) the inspector refuses to open at all, not just for that template but for other elements on the page.
+
+*I gave up waiting; it may load, eventually, or never load.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49797
+
+**Attached**: {F11051}",1371060840,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_description,resolved
+VisualEditor: Transclusion inspector blank on opening some templates,*** Bug 50016 has been marked as a duplicate of this bug. ***,1371969869,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,*** Bug 49958 has been marked as a duplicate of this bug. ***,1371832175,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,Related URL: https://gerrit.wikimedia.org/r/69806 (Gerrit Change I0b661744d0388345561897c9631f15e691737031),1371766188,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,*** Bug 49797 has been marked as a duplicate of this bug. ***,1371748994,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,*** Bug 49862 has been marked as a duplicate of this bug. ***,1371745099,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,"I found this as well. Here are the steps to reproduce:
+
+1. Open up [[mw.VisualEditor:Template test]] in edit mode.
+2. Click on any template, then click on the icon to open the template inspector.
+3. Click on the cross in the top-right-hand corner to close it.
+4. Click on the template inspector icon for the same template again. (It appears to still be there from the first time it was clicked.) This time the inspector appears blank.
+5. Click on the cross in the top-right-hand corner to close it again.
+6. Now, clicking on the template icon for any template on the page will have no effect (i.e. the template inspector doesn't load at all).",1371541325,PHID-USER-rjtk3h6l2quifuajiime,False,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Transclusion inspector blank on opening some templates,"Never loads. Trevor, is it selecting the wrong thing, so can't fetch it, or selecting the right thing, but can't fetch it for some other reason?",1371248265,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qb2vdcmk4mrkuu43ivqi,task_subcomment,NA
+VisualEditor: Some block objects when selected not triggering the inspector menu (no template/image icon),"Screenshot
+
+Screenshot attached - from https://www.mediawiki.org/wiki/Extension:Syntax_Highlighting
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F11040}",1371059580,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mgaib3olu55b5fa25dcw,task_description,resolved
+VisualEditor: Some block objects when selected not triggering the inspector menu (no template/image icon),Marking as fixed.,1372037973,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mgaib3olu55b5fa25dcw,task_subcomment,NA
+VisualEditor: Save dialog should not preserve history when opening a second time,"1. Make a change and press save
+2. close the save dialog (^)
+3. Press save again
+
+Note there is now a back button (<) which does nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371048240,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nqjwrvv7obmoxabd6boz,task_description,resolved
+VisualEditor: Save dialog should not preserve history when opening a second time,Related URL: https://gerrit.wikimedia.org/r/70113 (Gerrit Change I297a7d1458e5a1c33b9dcb85272fe5f40893dd88),1372034145,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nqjwrvv7obmoxabd6boz,task_subcomment,NA
+VisualEditor: Bad HTML when link seems to have been edited,"From a bug report in /mnt/bugs on parsoid.wmflabs.org.
+
+The edited HTML snippet in question looks like this:
+
+""<a href=""./Turkish_sparrow"" rel=""mw:WikiLink"" data-parsoid='{""a"":{""href"":""./Turkish_sparrow""},""sa"":{""href"":""Turkish sparrow""},""stx"":""simple"",""dsr"":[92,111,2,2]}'><a href=""American%20sparrow"" rel=""mw:WikiLink"">American sparrow</a></a>""
+
+The editor may tried to edit a link from Turkish -> American sparrow
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370981400,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4g3tuqan3yhuka5pdfba,task_description,resolved
+VisualEditor: Bad HTML when link seems to have been edited,Speculatively marking as fixed; please re-open if it recurs.,1372215957,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4g3tuqan3yhuka5pdfba,task_subcomment,NA
+VisualEditor: Bad HTML when link seems to have been edited,I think this is one of the bugs that has been fixed by https://gerrit.wikimedia.org/r/70434,1372215765,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4g3tuqan3yhuka5pdfba,task_subcomment,NA
+VisualEditor: Bad HTML when link seems to have been edited,"Another instance from /mnt/bugs/2013-06-11T19:33:15.924Z-VPN_blocking (on enwp)
+
+<a rel=""mw:WikiLink"" href=""protocol%20tunnel""><a rel=""mw:WikiLink"" href=""protocol%20tunnellng"">protocol tunnell</a></a><a rel=""mw:WikiLink"" href=""protocol%20tunnellng"">ing</a>",1371055575,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4g3tuqan3yhuka5pdfba,task_subcomment,NA
+VisualEditor: Bad HTML when link seems to have been edited,From: /mnt/bugs/2013-06-10T19:18:14.190Z-Golden-Crowned_Sparrow (editing done on mediawiki.wikimedia.org).,1370981817,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4g3tuqan3yhuka5pdfba,task_subcomment,NA
+VisualEditor: Surface should be able to inherit commands and toolbar from other surface,"Right now, we have to do the following in ve.ui.MWReferenceDialog and ve.ui.MWMediaDialog to set up the sub-editor's surface correctly:
+
+this.referenceSurface.addCommands( ve.init.mw.ViewPageTarget.static.surfaceCommands );
+
+Instead of accessing ve.init.mw (and assuming all surfaces with MW*Dialogs will be instantiated by ve.init.mw.ViewPageTarget), we should just be able to say ""initialize this new surface based on this existing surface"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1370964780,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-uk5g2utei5kls5xo2fer,task_description,resolved
+VisualEditor: Surface should be able to inherit commands and toolbar from other surface,"Not just inherit, but also block from inheritance for specific instantiations (e.g. the caption of an image inside a reference can't take a reference - bug 58270).",1386877772,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uk5g2utei5kls5xo2fer,task_subcomment,NA
+VisualEditor: Surface should be able to inherit commands and toolbar from other surface,"Stylesheets should be inherited as well (and be loaded by the surface rather than the dialog) so we don't have to do things like
+
+ve.ui.MWReferenceDialog.static.addLocalStylesheets( [
+	've.ce.Node.css',
+	've.ce.Surface.css',
+	've.ui.Surface.css',
+	've.ui.Context.css',
+	've.ui.Tool.css',
+	've.ui.Toolbar.css'
+] );",1370964956,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-uk5g2utei5kls5xo2fer,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","**Author:** `swalling`
+
+**Description:**
+When attempting to remove an entire section with an h2 header, removing the text of the header does not remove the line separator underneath the header. 
+
+Additionally, one additional delete/backspace action deleted the entire preceding section, and it seems from the resulting content that I merely blanked the header but the wikitext for it remains.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370932440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d25o2mdf4mdptqcqy2de,task_description,declined
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)",AFAICT this is now fixed - marking as WORKSFORME. Please re-open if it recurs.,1386029219,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","Change 70949 had a related patch set uploaded by Inez:
+(bug 49424) Add empty lines before/after new block level images
+
+https://gerrit.wikimedia.org/r/70949",1372379464,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)",Could someone provide step by step instruction how to reproduce this problem?,1372371000,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)",The latter; my apologies for not reading correctly! :),1371242772,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","The first part of this bug is a duplicate of bug 49452 (""Whitespace-only headings should be collapsed to (blank) paragraphs""), so re-purposing to be about the deletion issue.
+
+@Steven - could you give more details about this bug with deletion magically hiding large blocks of text but not deleting them - was it in Chrome/Mac? Does it happen reliably (and can you reproduce now) or is it occasional?
+
+@Oliver - is the ""this"" that users have seen the deletion causing a paragraph to no longer appear but still be there, or the heading-not-being-fully-deleted issue?",1371242518,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","This has also been reported by other users, and is something I observed in the usertesting videos we did, too.",1371126627,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","**swalling** wrote:
+
+Result
+
+Note empty header
+
+**Attached**: {F11801}",1370932504,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+"VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)","**swalling** wrote:
+
+Diff
+
+**Attached**: {F11799}",1370932479,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d25o2mdf4mdptqcqy2de,task_subcomment,NA
+VisualEditor: Activation of a selected block which is the first content not possible,"You can select it but the inspector menu doesn't trigger. Works fine if there's any content before the block.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370912820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ws46dvvtpsd7zfz4gkae,task_description,resolved
+VisualEditor: Activation of a selected block which is the first content not possible,Now fixed and will be put into production very soon.,1371844292,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ws46dvvtpsd7zfz4gkae,task_subcomment,NA
+VisualEditor: Activation of a selected block which is the first content not possible,Related URL: https://gerrit.wikimedia.org/r/69707 (Gerrit Change I8bcdea0f7a6951216bf8368865d23ef6246880ea),1371753495,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ws46dvvtpsd7zfz4gkae,task_subcomment,NA
+VisualEditor: Activation of a selected block which is the first content not possible,"Happens if it's a block or floated template, or an inline or floated (thumb) image. Doesn't happen on an inline template or an inline-block template.",1371746901,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ws46dvvtpsd7zfz4gkae,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,"Editing a page in a Hebrew wiki (possibly also in other RTL languages), adding a link does not show the popup. The word automatically becomes a wiki-link, no option to change the destination or make it an external link.
+
+The link seems to work well in English wikis.
+
+Tested on both my local install with the latest VE (VE-wmf6+) and on the hebrew wikipedia (VE-wmf5) and on both Firefox and Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1370904180,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ze4pocno64vkraksutzp,task_description,resolved
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,"Change 69281 abandoned by Mooeypoo:
+[WIP] Link surface fix for RTL
+
+Reason:
+Fixed in master.
+
+https://gerrit.wikimedia.org/r/69281",1373484938,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,This works for me and seems to work in the hebrew wikipedia. Can be marked as resolved.,1373001408,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,Give Moriel the credit given that she's done all the work on this bug so far - we'll try to get the patch properly reviewed so we can (hopefully?) merge and deploy it very soon.,1372001761,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,"I've been working on a fix for this but I may need some help with an issue.
+
+The position definition had to be changed in RTL, as it is hard-coded (calculated by the location of the word/selection.) That was completed successfully and the link surface appears correctly below the marked word in both LTR and RTL. 
+
+However, I am running into problems setting up the proper ""right"" dynamically-calculated value for the sub-popup TextInputMenuWidget, and my attempts to play around with left/right and windowWidths has failed. It appears ""almost right"" (a little to the left, a little to the right, skewed, etc) and I think I may be missing a property.
+
+I wonder if there is a possibility to get the ""right"" value of the link surface (that appears correctly) to implement it in the TextInputMenuWidget without having to call the element specifically.
+
+The fix below is still work in progress (Don't Merge!) but it should be completely fixed if I manage to figure out the position of the TextInputMenuWidget.",1371535364,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,Related URL: https://gerrit.wikimedia.org/r/69281 (Gerrit Change I312610ca630a8f75f1a0778e97f227f35a003b41),1371534862,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,And the opposite is also true: The inspector is visible in the Hebrew Wikipedia if the interface language is English.,1371315442,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left,"This also happens in the English wikipedia when the user interface is set to any rtl language.
+
+I tested with ?uselang=he ?uselang=ar and ?uselang=fa",1371058014,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ze4pocno64vkraksutzp,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"Screenshot of VisualEditor on the English Wikipedia
+
+I'm not even really sure how to explain this. I'll just include a screenshot.
+
+I went to <https://en.wikipedia.org/wiki/Ready,_Willing_and_Able_(Daron_Norwood_song)> and clicked ""edit this page"". This is what appeared.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11769}",1370897160,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_description,resolved
+Parsoid sometimes loads content from another wiki,I am assuming this is not an issue any more given that we have had no reports after launch.  The launch should have caused a lot of corruptions if this bug had been around.  Closing.,1373560843,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934035,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,Please let us know if there are any new cases.,1372463719,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"Still happening - PamD reports that {{User sandbox}} on enwiki displayed in Japanese and gave the wrong user name (Apparently she's now User:Ichiro Kikuchi). It's stopped, but...worrying.",1372082680,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,https://gerrit.wikimedia.org/r/69905 (Gerrit Change I495c294a5dbafadac133c0b377b576d297ca529d) | change APPROVED and MERGED [by jenkins-bot],1371845667,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,Related URL: https://gerrit.wikimedia.org/r/69905 (Gerrit Change I495c294a5dbafadac133c0b377b576d297ca529d),1371845423,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,https://gerrit.wikimedia.org/r/69880 (Gerrit Change I52abbc10e5fe6a6b9d97ef6d842943809c8f6d6d) | change APPROVED and MERGED [by jenkins-bot],1371834699,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,Related URL: https://gerrit.wikimedia.org/r/69880 (Gerrit Change I52abbc10e5fe6a6b9d97ef6d842943809c8f6d6d),1371834091,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,*** Bug 49939 has been marked as a duplicate of this bug. ***,1371829646,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,New report: But 49939,1371829621,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,Since there are no new reports it seems that this bug has been fixed by our config clean-up. Please reopen if you encounter this bug again.,1371774436,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,I think this is now fixed.,1371774406,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,*** Bug 49687 has been marked as a duplicate of this bug. ***,1371510441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,We deployed a few clean-ups to our wiki configuration handling recently which might have improved the handling of API errors when retrieving the per-wiki config fails. Has this bug been seen in the wild recently?,1371510235,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"We've seen a bunch of reports of content from different wikis showing up, usually German content (plus one case of Russian, and now one of French apparently). Moving this to Parsoid.",1371172273,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"Happened for me on pl.wp earlier today, too, with ""Vorlage"" as well. I didn't make a screenshot and I don't remember the aricle, sorry.",1371171596,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"Created attachment 12510
+Screenshot of VisualEditor on the English Wikipedia being all weird
+
+""Vorlage""? Blergh.
+
+My suspicion is Parsoid cache pollution.
+
+**Attached**: {F11771}",1370899423,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+Parsoid sometimes loads content from another wiki,"In attachment 12508, we can see that instead of the templates being shown with a green striped area atop them, there is ""Modèle:Infobox Single↵"", ""Modèle:Lari White↵↵↵↵↵"" and ""Modèle:1990s-country-song-stub"".
+
+I'm not sure what language this is (French, maybe?), but my account is set to use English and the site is supposed to be in English.",1370897328,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6dfe6wmnmfcjqgh27brf,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Create a document:
+
+Foo <ref>Bar</ref> Baz
+<references />
+
+=>
+
+Foo [1] Baz
+1. Bar
+
+
+==Test==
+1. Select and copy from '[' to ']' (no whitespace)
+2. Try to paste
+3. Note you now just have plain text [1]
+4. Note also if you make a larger selection (e.g. from 'o' to 'B'), copy/paste works fine.
+
+This might be to do with whitespace truncation, and probably applies to other inline nodes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52271
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54410",1370888760,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_description,resolved
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"No, this was and remains fixed. Test in Chrome or Firefox, for example.",1415030920,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"I think this is still occurring (https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox&diff=68973564&oldid=68973535 ).
+I'm using Safari, and I don't know if this is related to Bug 70143.",1415020432,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Change 83222 merged by jenkins-bot:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",1378923314,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Change 83222 had a related patch set uploaded by Esanders:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",1378548154,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"This is still broken in FF, see bug 53375",1377643048,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,Fixed in master; will be deployed on Thursday as part of the regular push.,1377634922,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Change 80301 merged by jenkins-bot:
+Copy-paste data fixes
+
+https://gerrit.wikimedia.org/r/80301",1377634864,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"Change 80301 had a related patch set uploaded by Jforrester:
+Copy-paste data fixes
+
+https://gerrit.wikimedia.org/r/80301",1377546588,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,https://gerrit.wikimedia.org/r/#/c/80301/ fixes,1377544792,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,Note this behaviour also occurs with templates,1376695565,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,*** Bug 52212 has been marked as a duplicate of this bug. ***,1375134084,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,"**bi.llybob** wrote:
+
+Note that, at least in Chrome, whitespace is <i>not</t> enough to count as additional text.",1373170390,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Can't copy/paste a reference or template unless you select text either side,*** Bug 50594 has been marked as a duplicate of this bug. ***,1372794209,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m2xsnbv7vbfet2rfctjx,task_subcomment,NA
+VisualEditor: Restoring oldids broken,"On attempting to edit and restore an oldid, everything works fine (oldid contents appear, diff shows correct wikitext change, etc.) but on save VE appears to send the wrong page version (presumably the 'newer' version that's meant to be replaced?) to MW so nothing gets saved.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1370882100,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-465skcravcf5ewxwsyd2,task_description,resolved
+VisualEditor: Restoring oldids broken,Merged and will go out with next deployment.,1371588446,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Restoring oldids broken,Related URL: https://gerrit.wikimedia.org/r/69344 (Gerrit Change Icacaa5101386e52309278c8d9871ca1193aa86a9),1371583097,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Restoring oldids broken,Ed is exactly right. EditPage appears to set basetimestamp this way as well.,1371576196,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Restoring oldids broken,"I can reproduce it. Tellingly, if you make a change and then press save you get an edit conflict. I suspect the problem is we are providing the timestamp of the version you choose to edit as the 'basetimestamp' which I don't think is right. When you hit save the API thinks all the versions ahead of the version you're editing were created since you loaded the page (hence the edit conflict scenario).
+
+I think 'basetimestamp' should always be populated with the timestamp of 'cur', regardless of which version you are editing, but would like confirmation from someone who knows the MW API better.",1371573224,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Restoring oldids broken,I can't reproduce this bug. I'll keep the assignment to Ed but it looks like this has been resolved in the mean time.,1371511602,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-465skcravcf5ewxwsyd2,task_subcomment,NA
+VisualEditor: Inspector buttons appear above save dialog,"1. Focus a node which triggers an inspector icon
+2. Hit save
+3. http://i.imgur.com/5YPyQL5.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49275
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49059",1370781420,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dbpbmbo7zjpy256zvcs6,task_description,resolved
+VisualEditor: Inspector buttons appear above save dialog,Merged and will go out later today.,1371766472,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dbpbmbo7zjpy256zvcs6,task_subcomment,NA
+VisualEditor: Inspector buttons appear above save dialog,Related URL: https://gerrit.wikimedia.org/r/69614 (Gerrit Change I2fbc4c8af943f1b096b8912191924961405d5c47),1371688630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbpbmbo7zjpy256zvcs6,task_subcomment,NA
+VisualEditor: Inspector buttons appear above save dialog,Probably related: http://i.imgur.com/E5SFyv0.png,1370902428,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dbpbmbo7zjpy256zvcs6,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"Because we want to be able to make certain properties non-cloneable, e.g. in ve.dm.MWReferenceNode.prototype.getClonedElement we strip 'contentsUsed'.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370612580,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_description,resolved
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,Fixed and will go live in a few minutes.,1372379856,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"Change 70913 merged by jenkins-bot:
+Invoke getClonedElement() on each element on copy
+
+https://gerrit.wikimedia.org/r/70913",1372372301,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"""We should verify...""",1372366801,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"We should very that copy/pasting a named reference with contents, doesn't copy the contents.",1372366747,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement,"Change 70913 had a related patch set uploaded by Catrope:
+Invoke getClonedElement() on each element on copy
+
+https://gerrit.wikimedia.org/r/70913",1372365026,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sxoh4wnqppbjcq4eftvq,task_subcomment,NA
+VisualEditor: Review dialog obfuscated by phantoms,"Screenshot of VisualEditor on the English Wikipedia using the Monobook skin, 2013-06-06
+
+VisualEditor's review dialog box can be obfuscated by the green striped area from restricted areas of a page. This is when using Monobook, at least. Maybe Vector too, I don't know. I've attached a screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11508}",1370571600,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ypcnrwup72gw33jiae5x,task_description,resolved
+VisualEditor: Review dialog obfuscated by phantoms,"We solved this specific issue as part of the minor re-work of the save dialog, but see bug 50096 and bug 49059.",1372084364,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ypcnrwup72gw33jiae5x,task_subcomment,NA
+VisualEditor: Review dialog obfuscated by phantoms,"Yes, this is a mess; phantoms' z-index is higher than the review panel (which is bad), and trigger when the mouse moves over them even though you're in a ""different"" interface component. This would be solved by switching to the new dialogs (as they're iframes), but we don't have time for that.",1370622142,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ypcnrwup72gw33jiae5x,task_subcomment,NA
+VisualEditor: Images loaded over HTTP unconditionally,"https://en.wikipedia.org/wiki/Jeffrey_Chiesa?veaction=edit
+
+When I go here currently, I get HTTPS warnings.
+
+---
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/5/5f/New_Jersey_Attorne…effrey_S_Chiesa.jpg/144px-New_Jersey_Attorney_General_Jeffrey_S_Chiesa.jpg.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/f/f0/Seal_of_the_United_States_Senate.svg/80px-Seal_of_the_United_States_Senate.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/8/8d/Seal_of_New_Jersey.svg/90px-Seal_of_New_Jersey.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/9/92/Flag_of_New_Jersey.svg/75px-Flag_of_New_Jersey.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/5/5f/New_Jersey_Attorne…effrey_S_Chiesa.jpg/144px-New_Jersey_Attorney_General_Jeffrey_S_Chiesa.jpg.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/f/f0/Seal_of_the_United_States_Senate.svg/80px-Seal_of_the_United_States_Senate.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/8/8d/Seal_of_New_Jersey.svg/90px-Seal_of_New_Jersey.svg.png.
+ Jeffrey_Chiesa:1
+The page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/9/92/Flag_of_New_Jersey.svg/75px-Flag_of_New_Jersey.svg.png.
+ Jeffrey_Chiesa:1
+---
+
+action=view is fine (no console warnings). When I go to veaction=edit, the console fills with warnings. It looks like VisualEditor is loading thumbnails unconditionally through HTTP. This should be changed to be protocol-relative.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/wiki/Jeffrey_Chiesa?veaction=edit",1370571480,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hljkwvij7ri6zsnlv4ny,task_description,resolved
+VisualEditor: Images loaded over HTTP unconditionally,"
+
+*** This bug has been marked as a duplicate of bug 43015 ***",1371576350,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hljkwvij7ri6zsnlv4ny,task_subcomment,NA
+VisualEditor: Images loaded over HTTP unconditionally,"This is odd - I thought this was fixed, but I can reproduce on enwiki but not on MW.org.
+
+I think this may be fixed by the new image code the Inez has written (which is still 'experimental' and so not available in production except for MW.org). Will check with him and update you.",1370621859,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hljkwvij7ri6zsnlv4ny,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","**Author:** `swalling`
+
+**Description:**
+Screenshot
+
+In attempting to test (as anon) on the MediaWiki.org sandbox, the page header template overlaps the diff and save functions, preventing me from saving my edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49361
+
+**Attached**: {F11481}",1370553900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-io3sncftadpkbmrqampw,task_description,resolved
+"VisualEditor: Phantoms appear above the save dialog, preventing saving",Merged and will go out later today.,1371766465,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving",Related URL: https://gerrit.wikimedia.org/r/69614 (Gerrit Change I2fbc4c8af943f1b096b8912191924961405d5c47),1371688627,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","Just a note that this also happens with editable elements like images, as their blue overlay extends on top of the VE menu bar.",1371652418,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","Instead of an arms race between z-index, the much easier solution would be to ensure the DOM structure of these two elements are nested properly so that their natural order is correct. z-index can be used to adjust display, but it is not capable (by design) to transcend the relative DOM position.
+
+I haven't tested the following so this exact example could be wrong, but generally it means that in the following sample:
+
+ <div style=""position: relative;"" id=""foo""> </div> 
+ <div style=""position: relative;"" id=""bar""> </div> 
+
+
+Naturally #bar will be on top of #foo as it comes later in the DOM. Though #foo and #bar can be interchanged at the root (through their common parent), any child of #bar will always be on top of any child of #foo.
+
+So not only is DOM ordering easier to manage (due to not having to worry about conflicting numbers), in some cases it is the only way.
+
+I'll see what the easier way to fix this is, we can perfect it later if suboptimal.",1370850847,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","And I had a similar issue attempting to save a page with an (uneditable) InfoBox on the right hand side. Luckily a simple workaround for the moment is to scroll down!
+
+Obviously the proper solution is to ensure the zorder of the ""Review your changes"" and ""Save your changes""/""Report a problem"" is above the ""phantoms"".",1370776701,PHID-USER-fgul5wwrgbtdpd5fved3,False,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Phantoms appear above the save dialog, preventing saving","Whoops, thanks for the spot, Steven!",1370554710,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-io3sncftadpkbmrqampw,task_subcomment,NA
+"VisualEditor: Add a temporary option to have section edit links go to wikitext editor, not VisualEditor","Necessary for beta rollout. Wording needs to be smithed carefully to ensure that it's clear that this is a temporary option.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1370536440,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-a7khjsiws3kuhgw3dtj5,task_description,resolved
+"VisualEditor: Add a temporary option to have section edit links go to wikitext editor, not VisualEditor",Done and deployed.,1371161777,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-a7khjsiws3kuhgw3dtj5,task_subcomment,NA
+"VisualEditor: Add a temporary option to have section edit links go to wikitext editor, not VisualEditor",Related URL: https://gerrit.wikimedia.org/r/68569 (Gerrit Change I5ce7ea8c1e47e8243b619fc61aa957f767d22b48),1371161078,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-a7khjsiws3kuhgw3dtj5,task_subcomment,NA
+VisualEditor: [Regression] Arrow keying around multibyte unicode characters fails after an inline node,"For example in the second line of the multibyte.html test file in the standalone demo (after '<tt>香港</tt>' [Hong Kong])
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370520480,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vtupkd2hzxpp7w3fyltw,task_description,resolved
+VisualEditor: [Regression] Arrow keying around multibyte unicode characters fails after an inline node,Above fixed is merged and will go out with wmf7 from Thursday.,1370969172,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vtupkd2hzxpp7w3fyltw,task_subcomment,NA
+VisualEditor: [Regression] Arrow keying around multibyte unicode characters fails after an inline node,Related URL: https://gerrit.wikimedia.org/r/67971 (Gerrit Change Iff1dfb90130685bb710821f8386cfa2f296f2f95),1370954363,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vtupkd2hzxpp7w3fyltw,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Visual Editor doesn't behave correctly when editing and adding text with combining diacritics.
+
+For example insert the text ""ɛ́"" (ɛ is character U+025B, combining acute is U+0301).
+When the cursor is behind ""ɛ́"":
+- pushing the left arrow doesn't move the cursor
+- adding text like ""ɛ́abcdef"" is fine but:
+  - pushing backspace gives ""ɛ́abcda"" instead of expected ""ɛ́abcde""
+  - pushing return ives ""ɛ́abcde\na""
+
+Some languages require combining diacritics, many keyboard layouts allow their input or user can insert them by copying and pasting from somewhere else.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51472",1370504280,PHID-USER-i5at67w766dqxs6ncxam,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_description,resolved
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"(In reply to comment #10)
+> I believe this is related (or a dupe?) of this:
+> https://bugzilla.wikimedia.org/show_bug.cgi?id=51472
+
+Related but not a dupe, I think; adding a see-also.",1374157250,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,I believe this is related (or a dupe?) of this: https://bugzilla.wikimedia.org/show_bug.cgi?id=51472,1374125073,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Great! It works as it should now.
+Thanks a lot!",1374124846,PHID-USER-i5at67w766dqxs6ncxam,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,Now fixed and will be deployed very soon; sorry for this.,1371844259,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,Related URL: https://gerrit.wikimedia.org/r/69814 (Gerrit Change If9c0860e2fe7b01eb0b27aae67c671062799a0fa),1371771158,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Yes, this is still reproduceable on Chrome and Firefox on Ubuntu, Chrome, Firefox and Safari on OS X, Chrome, Firefox, IE on Windows 8.
+The steps I tried on http://en.wikipedia.org/wiki/User:ESanders_(WMF)/Sandbox are :
+- move cursor to end of ""ɛ́abcdef""
+- type g
+- press return
+result: ""ɛ́abcdeff"" and new line instead of expected ""ɛ́abcdefg"" and new line.",1371444604,PHID-USER-i5at67w766dqxs6ncxam,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Denis, can you still reproduce (and if so, where and with what browser/system)?",1371162059,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Can't reproduce in master or live, except for a bug where if I select all then paste an exception is thrown (but that is unrelated).
+
+
+See:
+http://en.wikipedia.org/wiki/User:ESanders_(WMF)/Sandbox",1371159350,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,Reopening and assigning.,1371154520,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Yes this is still reproduceable on en.wikipedia.org or fr.wikipedia.org as well as www.mediawiki.org. I guess ""on the cluster everywhere as of yesterday"" means the bug 48630 is fixed so this is not a duplicate.
+Or is there a specific place I should try to reproduce the bug on where this has been fixed?
+
+Quickly looking at bug 48630 it seems the behaviour described here is different, although the solution to 48630 might fix this one, just not the current solution.
+
+Furthermore there are other broken behaviours.
+- In some situations the line following ""ɛ́"" would just be duplicated every unknown time interval until the input cursor is moved.
+- If the ""ɛ́"" is in the middle of a line, some following characters are duplicated each interval with or without the combining diacritic on them.
+- If inputing two base characters with each a combining character, an unexpected next line return is produce when finishing the sequence.
+- When moving the cursor past the base character with the combining character, the cursor jumps to the next line even if there are still characters on the current (actually now previous) line.",1370582711,PHID-USER-i5at67w766dqxs6ncxam,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"This appears to be a duplicate of an already-fixed bug (bug 48630), which is live on the cluster everywhere as of yesterday. Can you reproduce this now, and if so, on what wiki? Support for graphemes like this is important for us, as you can imagine, and it's worrying to hear that it's not working?
+
+*** This bug has been marked as a duplicate of bug 48630 ***",1370531722,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tfgena4tsev5hzwqh7g,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,"grey text, no diff appears after Review and save
+
+Seen in IE9 and below, works OK in FF and Chrome: 
+
+Make an edit with VE
+Click Review and save
+
+Page text is greyed out; no diff appears; Review and save button remains clickable; user cannot complete edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11329}",1370450340,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_description,resolved
+VisualEditor: IE9/10 incompatibilities with saving process,This is working for me now: I saved https://www.mediawiki.org/w/index.php?title=User:Catrope%2FSandbox&diff=1137641&oldid=740030 in IE10.,1409958443,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,*a user,1377104818,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,"An user reports:
+<<I just got a Edit beta tab on The Adventure of the Reigate Squire, even though I'm in IE 10. What's weirder is that this is the only page where I've seen a VE tab. Also, I can't make any edits with it: I changed a few words in one sentence and added an edit summary, but the thing's just hanging there. I got a message of Warning: Your edit may have been corrupted – please review before saving. However, I've been unable to find anything corrupt, even though I reviewed everything that I'd done. Nothing of WP:EF came up, either. 2001:18E8:2:1020:202A:8DD6:6403:B77 (talk) 16:25, 21 August 2013 (UTC)
+
+After several minutes of fruitless waiting, I gave up and reloaded the page. I then tried to add Category:Reigate and Banstead to the article (it's where the story is set), but after typing an edit summary of ""Add category"", I was forced to see that it's just been hanging there again. 2001:18E8:2:1020:202A:8DD6:6403:B77 (talk) 16:30, 21 August 2013 (UTC) >>
+
+Is this due to some tests or deployment sanity checks? Thanks.",1377104779,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,*** Bug 50086 has been marked as a duplicate of this bug. ***,1372084871,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,Relabelling; this is a blocker to IE9/10 use.,1372037486,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,IE10 exhibits the same behaviour.,1372032122,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,Related URL: https://gerrit.wikimedia.org/r/70108 (Gerrit Change I2ee2e33c89cac58863c9911fc3ad250c72a46206),1372031261,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,"I can consistently reproduce:
+
+* Saving the page results in an uncaught exception ""Permissions denied"" originating from ve.bind -> $.proxy -> line ""proxy = function () { return fn.apply( ..""
+  Presumably this is caused by IE9 (undocumented?) non-standard security model
+  that rejects certain interaction between functions originating from different
+  http requests (regardless of the origin, e.g. in this case they're both from
+  load.php on the local wiki, no CDN involved)
+
+* Generating a diff (""Review changes"") has a silent failure, no notification
+  is emitted that allows us to hide the spinner or display an error message.",1372031200,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: IE9/10 incompatibilities with saving process,IE8 and below aren't supported at all (and you shouldn't ever manage to get to use VE with them); assigning.,1370534281,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wgabwxsulvcboqwjus4t,task_subcomment,NA
+VisualEditor: Arrow keying off end of throws an exception,"* Move cursor to start/end of document
+* Press left (start) or right (end)
+* An exception is thrown by handleLeftOrRightArrowKey
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370295780,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-b63g5k3ztoignbyr5s5w,task_description,resolved
+VisualEditor: Arrow keying off end of throws an exception,Apparently fixed by gerrit 66322.,1370297945,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b63g5k3ztoignbyr5s5w,task_subcomment,NA
+"VisualEditor: Attribute order preservation is hopeless, get rid of it","
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369928220,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wynzwypqafg7laiqaomg,task_description,resolved
+"VisualEditor: Attribute order preservation is hopeless, get rid of it",Related URL: https://gerrit.wikimedia.org/r/68618 (Gerrit Change I1463d06db4900083dd4c565292bbabef09194b43),1371192190,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wynzwypqafg7laiqaomg,task_subcomment,NA
+"VisualEditor: Attribute order preservation is hopeless, get rid of it","It works fine in Chrome, but Firefox does not preserve the order in the attributes array:
+
+
+>>> var div = document.createElement('div')
+undefined
+>>> div.innerHTML='<a href=""foo"" data-parsoid=""bar""></a>';
+""<a href=""foo"" data-parsoid=""bar""></a>""
+>>> div.children[0]
+<a data-parsoid=""bar"" href=""foo"">
+>>> div.children[0].attributes
+[data-parsoid=""bar"", href=""foo""]",1369928377,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wynzwypqafg7laiqaomg,task_subcomment,NA
+VisualEditor: Add support for multi character grapheme clusters in UnicodeJS,"So that we can correctly calculate boundaries in unicode.wordbreak.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1369926300,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vocovg5zyvqjxex3mwtr,task_description,resolved
+VisualEditor: Add support for multi character grapheme clusters in UnicodeJS,Basic support added. Leaving open to work on full grapheme boundary detection.,1370531840,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vocovg5zyvqjxex3mwtr,task_subcomment,NA
+VisualEditor: Add support for multi character grapheme clusters in UnicodeJS,"This is fixed in the above commit, which is merged and will go out with wmf6.",1369932362,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vocovg5zyvqjxex3mwtr,task_subcomment,NA
+VisualEditor: Add support for multi character grapheme clusters in UnicodeJS,Related URL: https://gerrit.wikimedia.org/r/66123 (Gerrit Change I202b98199d2780534d1e02519b72579ba796f08f),1369928399,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vocovg5zyvqjxex3mwtr,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Currently we don't -> lots of broken imagery in /w/index.php etc. entry points.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59196",1369779540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_description,resolved
+VisualEditor: Respect Parsoid's <base>,"Change 90952 merged by jenkins-bot:
+Render resolved URLs for href and src attributes in CE
+
+https://gerrit.wikimedia.org/r/90952",1382986517,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Change 86065 merged by jenkins-bot:
+Resolve rendered URLs according to the provided <base>
+
+https://gerrit.wikimedia.org/r/86065",1382985176,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Change 90952 had a related patch set uploaded by Catrope:
+Render resolved URLs for href and src attributes in CE
+
+https://gerrit.wikimedia.org/r/90952",1382383425,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"(In reply to comment #13)
+> Change 86065 had a related patch set uploaded by Catrope:
+> Resolve rendered URLs according to the provided <base>
+> 
+> https://gerrit.wikimedia.org/r/86065
+This addresses the most common symptoms of this bug. It fixes rendering of link targets for internal links (at least on initial rendering; the href attribute doesn't update correctly when the link is edited), and it fixes href and src attributes of things inside of generated content nodes (templates, mostly).
+
+While the change in Gerrit fixes href/src attribute rendering for uneditable href/src attributes, we still have to do something for models that manage their own href/src and edit it, or generate it from another editable attribute.
+
+ve.dm.LinkAnnotation, ve.dm.MWExternalLinkAnnotation: href attribute is edited directly; in practice MWExternalLinkAnnotation is a full URL and LinkAnnotation isn't used in the MW integration, but we should still fix them.
+
+ve.dm.MWInternalLinkAnnotation: Generates href based on title attribute, which can be edited. Links that came directly from Parsoid now render correctly due to a hack (see bug 51487), but edited links don't render correctly.
+
+ve.dm.ImageNode, ve.dm.MWInlineImageNode, ve.dm.MWBlockImageNode: src attribute is edited directly; in practice, the MW ones use full URLs (the user doesn't edit the src directly, and the UI widget gets full URLs from the API) and ImageNode isn't used in the MW integration, but we should still fix them.
+
+ve.dm.MWCategoryMetaItem, ve.dm.MWLanguageMetaItem: these manage hrefs that can be edited, but they're never rendered and always absolute, so we don't really care",1380241433,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Change 86065 had a related patch set uploaded by Catrope:
+Resolve rendered URLs according to the provided <base>
+
+https://gerrit.wikimedia.org/r/86065",1380161671,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 53190 has been marked as a duplicate of this bug. ***,1377727533,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Fun fact: this is the most often duped VE bug ever, and it's in the top 30 of most often duped open bugs on our entire bugzilla, alongside classics such as bug 738 or bug 156. https://bugzilla.wikimedia.org/duplicates.cgi",1377727467,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 53491 has been marked as a duplicate of this bug. ***,1377718799,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 50466 has been marked as a duplicate of this bug. ***,1377445192,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,Also reported today at it.wp (this was the result https://it.wikipedia.org/w/Tsonga_%28popolazione%29 ). Thanks.,1375819931,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"To hopefully help people find this bug, here is the description from bug 51122 ""link targets assumed to be same namespace when opened with ctrl+click"" updated to reflect that it now happens with all links, not just those in image captions:
+
+When opening a link from the editing interface using ctrl+click (or ""open in a new tab"" from the right button menu) the link target is assumed to be in the same namespace as the currently edited page.
+
+For example a link to [[Bridgnorth Cliff Railway]] from the page [[User:Thryduulf/sandbox]] is opened as [[User:Thryduulf/Bridgnorth Cliff Railway]]. A link to [[User:Thryduulf/sandbox2]] on the same page opens [[User:Thryduulf/User%3AThryduulf%2Fsandbox2]]. A link to that sandbox page
+from a page in the article namespace opens as [[User%3AThryduulf%2Fsandbox2]], but this does get you to the correct page.",1375706105,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Come on guys, this is ""high major"" since May.",1375705817,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 51122 has been marked as a duplicate of this bug. ***,1375705754,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 51585 has been marked as a duplicate of this bug. ***,1375705742,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 50764 has been marked as a duplicate of this bug. ***,1372984971,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,*** Bug 50216 has been marked as a duplicate of this bug. ***,1372270074,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+VisualEditor: Respect Parsoid's <base>,"Timo says we can get the browser to do the resolution by getting the .href and .src properties in the original Parsoid document, so all we need to do is figure out which attributes are affected. I can think of href and src, are there others?",1369780004,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-aqxcn24qtgiw3ubxzs6h,task_subcomment,NA
+"VisualEditor: {Ctrl,Option}+{Delete,Backspace} doesn't delete a word in an RTL wiki","Pressing Ctrl-Backspace deletes a word in a <textarea> in Firefox. It works the same way in VisualEditor when the wiki's language is English, but if it's Hebrew, it only deletes one character.
+
+A GWT testing scenario for this would be something like this:
+
+Given $wgLanguageCode is 'he'
+        And I am editing an article
+        And I wrote 'אחת שתיים שלוש'
+When I press Ctrl-Backspace
+Then the remaining text is 'אחת שתיים '
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369777380,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-xrh4kcflnord5zllknj6,task_description,resolved
+"VisualEditor: {Ctrl,Option}+{Delete,Backspace} doesn't delete a word in an RTL wiki","According to my test, this was fixed, and the behavior is as predicted on my local install. It doesn't work properly in the VE that exists in he.wikipedia, so whatever was done is new.
+
+The fact this works without fixes is incredibly weird, since the handleDelete() function uses offsets, and those are supposed to be opposite between Hebrew and English. I'm checking into potential causes, but as far as I've seen, Inez' re-implemented code works.
+
+Amir, if you can verify this works on your local installation, that'll be helpful. I am a bit concerned about this since it doesn't make sense (it *shouldn't* work) and I am concerned that it doesn't work on he.wiki. I want to verify it isn't some local fluke before we close this bug as resolved.",1371511847,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-xrh4kcflnord5zllknj6,task_subcomment,NA
+"VisualEditor: {Ctrl,Option}+{Delete,Backspace} doesn't delete a word in an RTL wiki","This will (should?) get fixed when Inez does the re-write of this area, but assigning to Moriel to bug him and make sure he does it right. :-)",1369782783,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xrh4kcflnord5zllknj6,task_subcomment,NA
+VisualEditor: Cursor before first character of heading and hitting Enter advances cursor one position,"Place the cursor at the first position of some heading (before the heading's first character). Hit Enter. As expected, an empty line appears before the heading, but the cursor is unexpectedly advanced by one position and is now located *after* the heading's first character.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369603080,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-leu57abgm2tb4hkx7knq,task_description,resolved
+VisualEditor: Cursor before first character of heading and hitting Enter advances cursor one position,*** Bug 50168 has been marked as a duplicate of this bug. ***,1373162663,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-leu57abgm2tb4hkx7knq,task_subcomment,NA
+VisualEditor: Cursor before first character of heading and hitting Enter advances cursor one position,This was fixed and is now deployed.,1372901377,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-leu57abgm2tb4hkx7knq,task_subcomment,NA
+VisualEditor: Block-level media items' placement is incorrect (no clear after thumbs),"Open the VisualEditor on the page https://en.wikipedia.org/wiki/Battle_of_Paris_(1814) . The two images are placed side by side between the lead paragraph and the infobox; they should be placed below the infobox. 
+
+It appears that the VisualEditor generally arranges two images horizontally rather than vertically, unlike the wikitext renderer.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369599780,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-s4cphi53nj54xruaarhy,task_description,resolved
+VisualEditor: Block-level media items' placement is incorrect (no clear after thumbs),This is now fixed in master and will go live from tomorrow.,1371083774,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s4cphi53nj54xruaarhy,task_subcomment,NA
+VisualEditor: Block-level media items' placement is incorrect (no clear after thumbs),*** Bug 49010 has been marked as a duplicate of this bug. ***,1370635551,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s4cphi53nj54xruaarhy,task_subcomment,NA
+VisualEditor: Block-level media items' placement is incorrect (no clear after thumbs),"This is because we haven't been rewriting the image HTML to be like the normal display mode; this is now done for thumbs (you can see it as experimental code on MediaWiki.org) and mostly done for inline images, and will be deployed next week.",1370634398,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s4cphi53nj54xruaarhy,task_subcomment,NA
+VisualEditor: List langlinks (readonly) in the meta-data dialog,"This is to make the categories pane less lonely; we will want to do this 'properly' (writable) later, though this is… challenging given the Wikidata complexities.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369497420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7stkkrpd65tx5rjkp4fg,task_description,resolved
+VisualEditor: List langlinks (readonly) in the meta-data dialog,Related URL: https://gerrit.wikimedia.org/r/67245 (Gerrit Change I897da1cf06c79ee40e29fb632d09cddb57144ada),1370518722,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7stkkrpd65tx5rjkp4fg,task_subcomment,NA
+VisualEditor: List langlinks (readonly) in the meta-data dialog,Now merged and will go out with wmf6.,1370489154,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7stkkrpd65tx5rjkp4fg,task_subcomment,NA
+VisualEditor: List langlinks (readonly) in the meta-data dialog,This is being done in gerrit 65432.,1370462536,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7stkkrpd65tx5rjkp4fg,task_subcomment,NA
+VisualEditor: Content is LTR even when the page language is RTL,"This is using Firefox under Ubuntu 13.x:
+
+
+The problem:
+If the wiki is RTL (Hebrew, for instance), start editing an empty page. The caret appears on the left side and the typing is done LTR.
+
+
+I did a quick check, and noticed that there is a class added to the content box - ""ve-ui-surface mw-content-ltr"" even when the page language is rtl (defined in the <html dir=""rtl""..>
+
+I found this addition in the ve.init.mw.ViewPageTarget line 786:
+this.surface.$.addClass( 'mw-content-' + mw.config.get( 'wgVisualEditor' ).pageLanguageDir );
+
+In my system this produced ""mw-content-ltr"" despite the fact the page language was Hebrew and the html direction was defined as rtl. 
+
+However, I then tried to forcefully change it to rtl, just to test, and while the class appeared correctly (mw-content-rtl), the direction of the typed text was still LTR. It remained LTR when I changed the language to English.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux",1369379280,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-bs4iwunmzd4mvfoqwfmx,task_description,declined
+VisualEditor: Content is LTR even when the page language is RTL,As agreed.,1369782964,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bs4iwunmzd4mvfoqwfmx,task_subcomment,NA
+VisualEditor: Content is LTR even when the page language is RTL,"(In reply to comment #1)
+> Okay, I figured out the problem, but this isn't precisely a bug and it
+> depends
+> on what you want the behavior to be.
+> 
+> First off, the issue seemed to be that the definition of the page language
+> was
+> always LTR in VE, regardless of what language I was using. Even when my page
+> was Hebrew/RTL, VE's config showed it as english/ltr. That was quite
+> frustrating, I was starting to think the problem is that the hooks page reads
+> the language too early (which made no sense, really, since all other
+> extensions
+> read it the same way) 
+> 
+> Not so. Here's the issue:
+> 
+> I didn't notice that when I switched languages in MediaWiki, I did that
+> through
+> my own user preferences (since I was going frequently from English to Hebrew
+> and back for testing). That meant that the *page* and global language was
+> indeed English, and so VE read the global/page language *correctly* as
+> EN/LTR.
+> 
+> So, while I was working in my own rtl preferences, VE corrected me by
+> injecting
+> LTR in there, and switching my marker to the left. 
+> 
+> When I changed the global settings of my wiki to hebrew, it all worked out
+> perfectly again, and all is well.
+> 
+> So now a question for you guys -- this seems to be a decent behavior (though
+> maybe for the sake of users it may be nice to say it somewhere?) -- however,
+> there *is* an option to read the user language instead of the global language
+> in the VisualEditor.hooks.php page, by using the $context->getLanguage()
+> method
+> instead of the currently used $out->getTitle()->getPageLanguage()
+> 
+> That would mean that the direction of the marker will be defined by the
+> *user*
+> defined language rather than by the page- or wiki-defined language
+> direction. 
+> 
+> I can think of reasons this can be good, but I can also think of reasons this
+> can be bad. I am not sure which is better. On one hand, the page probably
+> defines the proper language, and the user language is mostly for the GUI, but
+> on the other, if the user language is RTL, we usually expect the marker to
+> follow suit.
+> 
+> Whatever is decided, this will definitely affect any and all RTL buttons
+> (direction changes for paragraphs/page/etc) and the marker movement (whose
+> bug
+> I was going to look at next.
+> 
+> Should it stay with page language, or switch to user language when deciding
+> marker direction in VE?
+
+I think that the behaviour is as intended - language of content is a wiki-level not user-level decision. This means that if your interface is in RTL but the content is LTR (or vice versa) the buttons need to work in the content context, not the user language, yes. Do they currently not?",1369387531,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bs4iwunmzd4mvfoqwfmx,task_subcomment,NA
+VisualEditor: Content is LTR even when the page language is RTL,"Okay, I figured out the problem, but this isn't precisely a bug and it depends on what you want the behavior to be.
+
+First off, the issue seemed to be that the definition of the page language was always LTR in VE, regardless of what language I was using. Even when my page was Hebrew/RTL, VE's config showed it as english/ltr. That was quite frustrating, I was starting to think the problem is that the hooks page reads the language too early (which made no sense, really, since all other extensions read it the same way) 
+
+Not so. Here's the issue:
+
+I didn't notice that when I switched languages in MediaWiki, I did that through my own user preferences (since I was going frequently from English to Hebrew and back for testing). That meant that the *page* and global language was indeed English, and so VE read the global/page language *correctly* as EN/LTR.
+
+So, while I was working in my own rtl preferences, VE corrected me by injecting LTR in there, and switching my marker to the left. 
+
+When I changed the global settings of my wiki to hebrew, it all worked out perfectly again, and all is well.
+
+So now a question for you guys -- this seems to be a decent behavior (though maybe for the sake of users it may be nice to say it somewhere?) -- however, there *is* an option to read the user language instead of the global language in the VisualEditor.hooks.php page, by using the $context->getLanguage() method instead of the currently used $out->getTitle()->getPageLanguage()
+
+That would mean that the direction of the marker will be defined by the *user* defined language rather than by the page- or wiki-defined language direction. 
+
+I can think of reasons this can be good, but I can also think of reasons this can be bad. I am not sure which is better. On one hand, the page probably defines the proper language, and the user language is mostly for the GUI, but on the other, if the user language is RTL, we usually expect the marker to follow suit.
+
+Whatever is decided, this will definitely affect any and all RTL buttons (direction changes for paragraphs/page/etc) and the marker movement (whose bug I was going to look at next.
+
+Should it stay with page language, or switch to user language when deciding marker direction in VE?",1369387045,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-bs4iwunmzd4mvfoqwfmx,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"Select an inline node (e.g. an inline image) on it's own (i.e. no whitespace either side of it), and trying to copy will throw an exception (ve.dm.Document.js:786 selection[0].range is undefined)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368892860,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_description,resolved
+VisualEditor: Selecting and copying one node throws an exception,Fixed in master; will be deployed on Thursday as part of the regular push.,1377634914,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"Change 80301 merged by jenkins-bot:
+Copy-paste data fixes
+
+https://gerrit.wikimedia.org/r/80301",1377634861,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"Change 80301 had a related patch set uploaded by Jforrester:
+Copy-paste data fixes
+
+https://gerrit.wikimedia.org/r/80301",1377546583,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,https://gerrit.wikimedia.org/r/#/c/80301/ fixes,1377544788,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"Nope, ignore comment 5, it adds the linebreaks no matter which way the selection is generated. Similar outcome but apparently independent.",1374074350,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,The second half of comment 4 might be bug 51538,1374074228,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"No exception now, it just fails to copy at all if you select a focusable node.
+
+In what looks like a separate bug, if you select around a focusable node, pasting creates a new paragraph, e.g.
+
+Foo ""Bar [1] Baz"" Quux
+
+copy range marked with double quotes ([1] is a reference) then paste in the middle of Qu_ux and you get:
+
+Foo Bar [1] Baz Qu
+Bar [1] Baz
+ux
+
+instead of
+
+Foo Bar [1] Baz QuBar [1] Bazux",1373993120,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,I can't reproduce this now in Chrome or Firefox…,1373336346,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"@Ed, @Christian: In which browsers are you guys able to confirm it?",1372710956,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Selecting and copying one node throws an exception,"**orbit** wrote:
+
+ooh... that's true.",1371773691,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-vhlmolnzsp5kd7qoa2nn,task_subcomment,NA
+VisualEditor: Edit triggered repeated inserts of existing text with snowman,"I used VE in Firefox 21.0 on Ubuntu to edit https://www.mediawiki.org/wiki/Backporting_Fixes . I changed a few headings, then pressed Enter between a heading and a numbered list below it to insert a new line (not sure if the caret was on the end of the heading or the start of the first item, I'm not sure if I started typing.
+
+VE began inserting the first sentence of the numbered list but with its link changed to two snowmen, about 15 times. Every time I clicked it would prepend some more.  Even scrolling would trigger this.
+
+Before, the document contained
+
+== WMF Cluster Backports ==
+# Make sure there is a bug registered in [[mw:Bugzilla|Bugzilla]] for the issue.
+
+I couldn't edit the document, but VE's review and save button worked fine. The new document showed as
+
+== ==
+# Make sure there is a bug registered in ☃☃ for the issue.Make sure there is a bug registered in ☃☃ for the issue. <repeated 269 more times>Make sure there is a bug registered in [[mw:Bugzilla|Bugzilla]] for the issue.
+
+I don't know what happened to the heading, I didn't blank it out. I might have attempted a cut and paste, maybe that's what's going haywire, though I'm pretty sure the last thing I did was pressed Enter to add a sentence after the heading.
+
+I assume this is an Easter egg in the VE codebase: if you manipulate the document near an exhortation to file a bug, Parsoid detects it and repeats the phrase, with snow people 8-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368826620,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-lyuwrgvbcgimricw6omw,task_description,resolved
+VisualEditor: Edit triggered repeated inserts of existing text with snowman,"I /believe/ that we fixed this (rather worrying bug) last week with some changes on the CE side; if it recurs, please re-open!",1371147355,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lyuwrgvbcgimricw6omw,task_subcomment,NA
+Spaces added before colons and links in some cases,"See https://fr.wikipedia.org/w/index.php?title=COE&diff=prev&oldid=93166267 for example.
+
+I only removed the link, but VisualEditor added a space before the colons.
+
+Another example: https://fr.wikipedia.org/w/index.php?title=MSS&diff=prev&oldid=93166411
+
+There was already two spaces, but VisualEditor added a third.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51024",1368776580,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-dlmzlny66znupvw7flge,task_description,resolved
+Spaces added before colons and links in some cases,"According to a cs.wp editor such changes are intentional, so possibly no need to investigate further. Thanks.",1423674753,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"(Sorry if I'm adding to the wrong task, I think a more relevant one was closed as dupe of this one. I haven't heard from cs.wp yet but it looks like there are [[ https://cs.wikipedia.org/w/index.php?title=Speci%C3%A1ln%C3%AD:Z%C3%A1znam_filtr%C5%AF_zneu%C5%BEit%C3%AD&wpSearchFilter=69 | too many occurrences ]] to be the case, IMHO).",1423496314,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,@Elitre: This doesn't look like space before colons or links .. Could they be null edits / edit undos that might have left behind spaces in VE that Parsoid is preserving?,1423494381,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Can it be this is happening again? At cs.wp [[ https://cs.wikipedia.org/wiki/Speciáln%C3%AD:Filtry_zneužit%C3%AD/69 | they are filtering ]] edits adding extra spaces, like [[ https://cs.wikipedia.org/w/index.php?title=Románská_architektura&diff=prev&oldid=12201516 | this ]] or [[ https://cs.wikipedia.org/w/index.php?title=Ptakopysk&diff=prev&oldid=12204327 | this ]] (I haven't much info ATM).",1423328803,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Change 84701 merged by jenkins-bot:
+(Bug 48570) Fix subtle selser bug handling separator-only nodes
+
+https://gerrit.wikimedia.org/r/84701",1379696165,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,*** Bug 50637 has been marked as a duplicate of this bug. ***,1379613746,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Change 84701 had a related patch set uploaded by Subramanya Sastry:
+(Bug 48570) Fix subtle selser bug handling separator-only nodes
+
+https://gerrit.wikimedia.org/r/84701",1379466252,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Confirmed on simple test case. Investigating.
+---------------------------------------
+
+[subbu@earth tests] echo ""foo : bar"" > /tmp/wt
+[subbu@earth tests] node parse < /tmp/wt > /tmp/old.html
+[subbu@earth tests] cat /tmp/old.html | sed 's/bar/bars/g;' > /tmp/new.html
+[subbu@earth tests] node parse --html2wt --selser --oldtextfile /tmp/wt --oldhtmlfile /tmp/old.html < /tmp/new.html
+foo  : bars",1379461368,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,Bug 51024 has several more examples of this bug occurring if anyone is looking for them.,1379455350,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,*** Bug 51024 has been marked as a duplicate of this bug. ***,1379455266,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,See also bug 51024,1379448597,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Still present: see https://fr.wikipedia.org/w/index.php?title=Julot,_l%27Apache&diff=96678299&oldid=95213076 for example.",1379252830,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"This looks like 1. a Parsoid issue, 2. fixed in master. Reassigning to Parsoid to confirm.",1376931075,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"Ignore last comment, should be: Could the fix to bug 52035 be related to this?",1375442806,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,Could the fix to bug 2035 be related to this?,1375442771,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"It's not just ' either, also seen when removing - and "" in my sandbox https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=566841354&oldid=566840716
+
+spaces were added before internal and external links, except in the first instance where a space was added before a colon instead.",1375442619,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"We unfortunately can:
+http://en.wikipedia.org/w/index.php?title=Little_Mosque_on_the_Prairie&diff=prev&oldid=566820635
+
+It seems to be triggered by removal of '.
+Another user verified this (not actually saving, only preview mode) in http://en.wikipedia.org/wiki/Indian_Bank , removing the ' after ""Binny&Co"" would cause a whitespace to be added right before the next wikilink.",1375441882,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"(In reply to comment #0)
+> See https://fr.wikipedia.org/w/index.php?title=COE&diff=prev&oldid=93166267
+> for example.
+> 
+> I only removed the link, but VisualEditor added a space before the colons.
+> 
+> Another example:
+> https://fr.wikipedia.org/w/index.php?title=MSS&diff=prev&oldid=93166411
+> 
+> There was already two spaces, but VisualEditor added a third.
+
+These have been now fixed - sorry for the difficulty.
+
+(In reply to comment #1)
+> The same happens when you edit the first word of a sequence ""word + word +
+> wikilink"", it will add an unnecessary space before the link. Examples,
+> http://it.wikipedia.org/w/index.php?title=Amazon.
+> com&diff=prev&oldid=59604951 - 
+> http://it.wikipedia.org/w/index.php?title=Google&diff=59622535&oldid=59377529
+> (<<talmente popolare ch in  [[lingua inglese|inglese]] >>).
+> This last one is a deliberate vandalism from me to check the issue, I later
+> rollbacked.
+
+I *think* this is also fixed but I'm not absolutely sure; please re-open if you can still reproduce this.",1372017555,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+Spaces added before colons and links in some cases,"The same happens when you edit the first word of a sequence ""word + word + wikilink"", it will add an unnecessary space before the link. Examples,
+http://it.wikipedia.org/w/index.php?title=Amazon.com&diff=prev&oldid=59604951 - 
+http://it.wikipedia.org/w/index.php?title=Google&diff=59622535&oldid=59377529 (<<talmente popolare ch in  [[lingua inglese|inglese]] >>).
+This last one is a deliberate vandalism from me to check the issue, I later rollbacked.",1371983634,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dlmzlny66znupvw7flge,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368753300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_description,resolved
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"Change 81876 merged by jenkins-bot:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1381186926,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"Change 81876 had a related patch set uploaded by Jforrester:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1378325639,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,*** Bug 50903 has been marked as a duplicate of this bug. ***,1377814666,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"Removing from a milestone; as discussed, we're not going to have time to get to this before next week, and the EventLogging integration needs to be done RSN.",1370566097,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,"Setting milestone to 2013-06-27 since it is marked as blocker for ""Beta"" (2013-07). It may be moved to an earlier milestone as we see fit. But no later than 06-27. Setting it since I use milestone to sort ""My bugs"".",1370298479,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Convert save dialog to use ve.ui.Dialog,Trevor has some thoughts about this. :-),1368753519,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7mo2ly5r5mqfuju3u5ar,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,"Not sure how to reproduce, but I get two items in the ""Matching categories"" section; I can only move to the top one, and pressing down doesn't work (but pointer-highlighting and selection does).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1368749160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_description,resolved
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,Now fixed by Trevor.,1371002039,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,Related URL: https://gerrit.wikimedia.org/r/68130 (Gerrit Change If48e001b92c217bee0a35b6da41d1c1ff0e3271c),1371001969,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,"(In reply to comment #3)
+> I can't reproduce this on master.
+
+But I can. :-(
+
+Requires two extant (on page and in wiki) categories which start with the same character sequence (I have ""DoG and ""DooooG"")
+
+On suggesting 'd', I get:
+
+New category
+  d
+Move this category here
+Matching categories     <--- This should not be here at all
+  DoG                   <--- This should be in the ""Move this category here"" block
+  DooooG                <--- This should also be in ""Move this category here""",1371000702,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,I can't reproduce this on master.,1370978406,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,Seemingly not; Trevor investigating.,1369407946,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Can't move to last item in category dialog suggester box with cursors,Now fixed in master.,1369404163,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pj4cd4p4ynmavre5zsn7,task_subcomment,NA
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1368747960,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-koardc3to3cjpsgjsemv,task_description,resolved
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,Related URL: https://gerrit.wikimedia.org/r/65314 (Gerrit Change Ie87a3c7dde2f29c3898c08d4cade5c0ba2f937dd),1369420191,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-koardc3to3cjpsgjsemv,task_subcomment,NA
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,Merged and will go out in wmf5.,1369416082,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-koardc3to3cjpsgjsemv,task_subcomment,NA
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,Related URL: https://gerrit.wikimedia.org/r/65303 (Gerrit Change Ibf63329a53bcd8043d46315239c19be4e681a18a),1369410443,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-koardc3to3cjpsgjsemv,task_subcomment,NA
+VisualEditor: Make a toolbar button to trigger the meta-data inspector,"We will also want to kill the non-Category panels (or populate them, if you're feeling sprint-y).",1368748032,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-koardc3to3cjpsgjsemv,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"Do we need to trigger a re-render of the catlinks div? Can we?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52403",1368747000,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_description,resolved
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,Verified the fix on test 2,1389901362,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"Change 107036 merged by jenkins-bot:
+Update categories HTML on page save
+
+https://gerrit.wikimedia.org/r/107036",1389638149,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"Change 107036 had a related patch set uploaded by Esanders:
+Update categories HTML on page save
+
+https://gerrit.wikimedia.org/r/107036",1389536961,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,*** Bug 57924 has been marked as a duplicate of this bug. ***,1386089449,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"Note that the categories on the page are not refreshed even after multiple VE sessions.  i.e. VE add category -> save -> VE add category -> save : results in a page that _displays_ only the categories at the beginning of the process.
+
+Categories added via templates are also not displayed.",1384389210,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,*** Bug 56683 has been marked as a duplicate of this bug. ***,1383767137,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,*** Bug 50737 has been marked as a duplicate of this bug. ***,1373556875,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,*** Bug 50072 has been marked as a duplicate of this bug. ***,1372036218,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Category changing in page doesn't cause footer to be updated on save,"It depends on what we get back from the server.
+
+If we get back something that is compatible with what api.php?action=parse gives (prop.categorieshtml, from Skin::getCategories), which is what live preview in core uses as well, then we can just update it by replacing the old with the new html.
+
+If we can't get that, we'll have to re-implement Skin::getCategories in javascript. However I'd like to avoid that since it is skin-specific (skins can do all kinds of weird stuff to it, hard to predict. Ideally this would fall under the parts of the page output (like mw-content-text, htmlhead and script loader) that has a fixed html layout that skins can't alter the html itself of (it has enough css hooks to style anyway they like, they shouldn't need to modify the html). But that's not the reality.
+
+--
+
+Oh wait, this isn't from the server (not MediaWiki, not Parsoid). I mean, it shouldn't. This is reflected live when editing the document. We'll have to do it in javascript somehow I'm afraid.",1370851294,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-2astjxmuxt2yyso6g3kb,task_subcomment,NA
+VisualEditor: Clicking link button while link inspector is already open throws error,"The button should probably not do anything if the inspector is already open.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368737040,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-7d3wwwbypeipgqn42o5c,task_description,resolved
+VisualEditor: Clicking link button while link inspector is already open throws error,Merged and will go out with wmf5.,1369256685,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7d3wwwbypeipgqn42o5c,task_subcomment,NA
+VisualEditor: Clicking link button while link inspector is already open throws error,Related URL: https://gerrit.wikimedia.org/r/64818 (Gerrit Change Ia97b6e3d862e02f5c55cac3f490fd8f26052027a),1369150090,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7d3wwwbypeipgqn42o5c,task_subcomment,NA
+VisualEditor: Image resize handles persist on close,"If the image has focus when you click back on the 'Read' tab, the four circles stay on the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368698040,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2nyantno3ds7ohrifauv,task_description,resolved
+VisualEditor: Image resize handles persist on close,Merged and will go out with wmf5.,1369454138,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2nyantno3ds7ohrifauv,task_subcomment,NA
+VisualEditor: Image resize handles persist on close,Related URL: https://gerrit.wikimedia.org/r/64917 (Gerrit Change I807a0f32d3d1eb490456d887f7bf867bdb896df4),1369220160,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2nyantno3ds7ohrifauv,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,"Once it exists being the relevant part. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368662820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_description,resolved
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,"Change 127362 merged by jenkins-bot:
+Use Parsoid API for action=parsefragment
+
+https://gerrit.wikimedia.org/r/127362",1397866425,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,"Change 127362 had a related patch set uploaded by Esanders:
+Use Parsoid API for action=parsefragment
+
+https://gerrit.wikimedia.org/r/127362",1397852463,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,Does the API actually exist yet?,1397845488,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,This should be done sooner rather than later.,1394493707,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,*** Bug 62516 has been marked as a duplicate of this bug. ***,1394493657,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,https://www.mediawiki.org/wiki/Parsoid#The_Parsoid_web_API has the API docs.,1386358351,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,More detail please?,1386336562,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists,Not going to make beta at this rate.,1371780475,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nu3747gtrfgcnn6ifzlx,task_subcomment,NA
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,"In ve.init.mw.ViewPageTarget.prototype.tearDownToolbar, this.toolbar is undefined if the editor hasn't finished loading.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368653280,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-f3bksoxide4n4n2plcfg,task_description,resolved
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,Merged; will go out with wmf5.,1368885093,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f3bksoxide4n4n2plcfg,task_subcomment,NA
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,Related URL: https://gerrit.wikimedia.org/r/64333 (Gerrit Change Ide5def0e983bab49108b40008fc170957c7fc2a2),1368809326,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f3bksoxide4n4n2plcfg,task_subcomment,NA
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,"Actually, this is distinct.",1368655857,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f3bksoxide4n4n2plcfg,task_subcomment,NA
+VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception,"
+
+*** This bug has been marked as a duplicate of bug 47813 ***",1368654670,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f3bksoxide4n4n2plcfg,task_subcomment,NA
+VisualEditor: MWLinkTargetInputWidget should grok case sensitivity of suggested page title vs. the inputed text,"Screenshot of problem
+
+Scenario:
+* Document contains "" ... esams ... ""
+* Wiki has a page called ""Esams"".
+* Wiki does not have case-sensitive first character in the main namespace.
+* Select ""esams"" and turn it into a link
+* UI shows:
+  [ esams            ]
+  New page:
+    <redlink> esams
+  Matching page:
+    Esams
+    Esams cluster
+    Esams patches
+
+That first redlink is incorrect, it should show the same as when the input is ""Esams"" (with capital E), namely no ""redlink"" since the first match is in fact the input.
+
+It needs to account for the $wgCapitalLinkOverrides and $wgCapitalLinkOverrides configuration etc. This is abstracted in PHP by MWNamespace::isCapitalized, which is exposed in javascript as 'wgCaseSensitiveNamespaces' in mw.config.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F10838}",1368573360,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ukhmjz446wmy32ws4rzz,task_description,resolved
+VisualEditor: MWLinkTargetInputWidget should grok case sensitivity of suggested page title vs. the inputed text,Related URL: https://gerrit.wikimedia.org/r/64867 (Gerrit Change I66f5fc56554984af58d6223dc6cd76b3ab9940bd),1369174848,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ukhmjz446wmy32ws4rzz,task_subcomment,NA
+VisualEditor: MWLinkTargetInputWidget should grok case sensitivity of suggested page title vs. the inputed text,"Basically any normalisation causes this bug.
+
+also things like user:krinkle -> User:Krinkle, and localized namespaces and alias namespaces (Image>File).",1369174621,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ukhmjz446wmy32ws4rzz,task_subcomment,NA
+VisualEditor: MWLinkTargetInputWidget should grok case sensitivity of suggested page title vs. the inputed text,*** Bug 48433 has been marked as a duplicate of this bug. ***,1368720868,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ukhmjz446wmy32ws4rzz,task_subcomment,NA
+VisualEditor: Heading on a slug is created on the wrong line in Firefox,"1 Go to a page with several paragraphs. Edit with VisualEditor.
+
+2. Place cursor at the end of paragraph N and press Enter to create a new line. See the cursor blinking in a new line after paragraph N.
+
+3. Select ""Heading 2"" in the dropdown menu.
+
+EXPECTED
+
+A Heading 2 line appears at the end of paragraph N.
+
+
+ACTUAL OUTCOME
+
+A Heading 2 line appears at the end of paragraph N-1.
+
+
+As a matter of fact I find no way to place the header where I want, unless going to the end of paragraph N+1 only to trick the bug. Selecting an existing line and trying to make a header out of it doesn't seem to work either (but this is probably a different bug).
+
+Happens at least in mediawiki.org with Firefox 22.0a2 (2013-05-07).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368554100,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-frnef4dwspf2gymmanpq,task_description,resolved
+VisualEditor: Heading on a slug is created on the wrong line in Firefox,"(In reply to comment #2)
+> Yes, this works now. Thank you!
+> 
+> Just a little usability detail: after selecting the type of heading there is
+> no
+> cursor blinking. You can type and characters will appear where expected, but
+> of
+> course our old friend cursor-blinking is missed.
+
+Yes; Rob noticed this too, and is working on it - just created bug 50338 to track.",1372384505,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-frnef4dwspf2gymmanpq,task_subcomment,NA
+VisualEditor: Heading on a slug is created on the wrong line in Firefox,"Yes, this works now. Thank you!
+
+Just a little usability detail: after selecting the type of heading there is no cursor blinking. You can type and characters will appear where expected, but of course our old friend cursor-blinking is missed.",1372375315,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-frnef4dwspf2gymmanpq,task_subcomment,NA
+VisualEditor: Heading on a slug is created on the wrong line in Firefox,I believe we've fixed this now in production - please re-open if it recurs.,1372371426,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-frnef4dwspf2gymmanpq,task_subcomment,NA
+VisualEditor: Remove alpha notice,"When I go to use the VisualEditor (e.g., <https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals> --> click ""edit""), there's a bothersome notice every time the VisualEditor form loads about how it's the alpha version of the tool. There's no way to dismiss the notice and it gets a bit grating after a while.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1368496800,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_description,resolved
+VisualEditor: Remove alpha notice,Merged and will go out with wmf7 tomorrow.,1371057658,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_subcomment,NA
+VisualEditor: Remove alpha notice,Related URL: https://gerrit.wikimedia.org/r/68128 (Gerrit Change I725beec4e76dadfb1ccca873758f8f37b7f58a73),1370999898,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_subcomment,NA
+VisualEditor: Remove alpha notice,Change-Id: Ie289c39b963072e8a20aa29926dee1d199b6e4e8,1370298333,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_subcomment,NA
+VisualEditor: Remove alpha notice,"To do just before the ""alpha"" becomes a ""beta"".",1368497309,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dl4wjvv5i2ofxqjlq7lh,task_subcomment,NA
+VisualEditor: Pre-beta needs (tracker),"Tracker for the bugs/enhancements that should be done for the beta.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368493800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tzlbyq77mfgatrefsaj3,task_description,invalid
+VisualEditor: Pre-beta needs (tracker),[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343629,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-tzlbyq77mfgatrefsaj3,task_subcomment,NA
+VisualEditor: Pre-beta needs (tracker),Bugs tracking bugs that track bugs aren't hugely useful; let's kill this one.,1393640096,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tzlbyq77mfgatrefsaj3,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,"[[:File:SpecialPage_Filter_JS.png]]
+
+is being converted to:
+
+<a rel=""mw:Image"" href=""../File:SpecialPage_Filter_JS.png"" data-parsoid=""{&quot;tsr&quot;:[21446,21481],&quot;src&quot;:&quot;[[:File:SpecialPage Filter JS.png]]&quot;,&quot;dsr&quot;:[21446,21481,null,null]}""><img src=""../Special:FilePath/SpecialPage_Filter_JS.png?width=200"" alt=""SpecialPage_Filter_JS.png"" width=""200"" style=""vertical-align: middle;"" data-parsoid=""{}""></a>
+
+It should be an <a> without the <img> inside it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://parsoid.wmflabs.org/mw/User:Dantman/Code_Ideas",1368389040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_description,resolved
+Images: Image links are interpreted as image inclusions,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934030,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,*** Bug 49891 has been marked as a duplicate of this bug. ***,1371769152,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,Fixed by https://gerrit.wikimedia.org/r/#/c/69612/.,1371764117,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,"(In reply to comment #2)
+> This affects VisualEditor on the English Wikipedia.
+
+I'm adding bug 48426 as a blocker.",1370921421,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,*** Bug 49384 has been marked as a duplicate of this bug. ***,1370883912,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,*** Bug 48669 has been marked as a duplicate of this bug. ***,1369114571,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,This affects VisualEditor on the English Wikipedia.,1368981137,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+Images: Image links are interpreted as image inclusions,*** Bug 48596 has been marked as a duplicate of this bug. ***,1368979809,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4k5gqkncjczqm4ffrhqk,task_subcomment,NA
+VisualEditor: Whitespace preservation for auto-links not working sometimes(?),"Putting this in DM because it seems the most likely suspect.
+
+Original bug occurred on enwiki (text in the test stolen from there). This feels like a bit of bug 43543 - which was fixed?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=VisualEditor:TestAutolinks&diff=688670&oldid=688669",1368315240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-miessklckuwapsejbpw4,task_description,resolved
+VisualEditor: Whitespace preservation for auto-links not working sometimes(?),"Confirmed as fixed in master.
+
+*** This bug has been marked as a duplicate of bug 43543 ***",1368379914,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-miessklckuwapsejbpw4,task_subcomment,NA
+VisualEditor: Can't delete-merge two paragraphs together if the first one ends with an inline-alien,"This was happening with <ref>s, but it looks like it'll be an issue with an paragraph that ends with an inline alien:
+
+| Foo.<ref>Ref</ref>
+| Bar.
+
+Backspace with the cursor to the left of the 'B', or delete with the cursor to the right of the <ref> block, has no effect.
+
+The problem with <ref>s will go away(?) when that node handler code is enabled, but is this a wider issue?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368313200,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lyjnjxdzskobjhrp4tgf,task_description,resolved
+VisualEditor: Can't delete-merge two paragraphs together if the first one ends with an inline-alien,This seems to be not an issue anymore - since I rewrote handleDelete method.,1372369220,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-lyjnjxdzskobjhrp4tgf,task_subcomment,NA
+VisualEditor: Re-factor key detection to be more robust and not occasionally break/pawn in Firefox,"Inez has some ideas about how to do this, so marking to him for now. Would be nice to document here /home/ we want to do this so someone can pick it up at some point. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1368215940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6w7ima76rbpczpaozizw,task_description,resolved
+VisualEditor: Re-factor key detection to be more robust and not occasionally break/pawn in Firefox,Now merged and will go out with wmf8 from Thursday 20 June.,1371180920,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6w7ima76rbpczpaozizw,task_subcomment,NA
+VisualEditor: Re-factor key detection to be more robust and not occasionally break/pawn in Firefox,https://gerrit.wikimedia.org/r/68296 (Gerrit Change Ie00becf1162f145134f006b0b4514ba874de9c43) | change APPROVED and MERGED [by jenkins-bot],1371180886,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6w7ima76rbpczpaozizw,task_subcomment,NA
+VisualEditor: Re-factor key detection to be more robust and not occasionally break/pawn in Firefox,Related URL: https://gerrit.wikimedia.org/r/68296 (Gerrit Change Ie00becf1162f145134f006b0b4514ba874de9c43),1371074644,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6w7ima76rbpczpaozizw,task_subcomment,NA
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,"Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
+Put the cursor somewhere in the text.
+Type ""Enter"" 2 times.
+Type ""Up"".
+Type a
+Type Enter
+Type b
+Type Up
+Type Left
+Press Shift and hold it
+Type Down
+
+Expected: selection of 1 line
+Actually: selection of 2 lines
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368090660,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_description,resolved
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,Fixed in the above.,1372465847,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_subcomment,NA
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,"Change 71143 merged by jenkins-bot:
+Firefox misplaces cursor when moving between lines
+
+https://gerrit.wikimedia.org/r/71143",1372465519,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_subcomment,NA
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,"Change 71143 had a related patch set uploaded by Christian:
+Firefox misplaces cursor when moving between lines
+
+https://gerrit.wikimedia.org/r/71143",1372459066,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_subcomment,NA
+VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox,Can confirm in Firefox (and not in Chrome); it sometimes occurs upwards as well as downwards.,1368130754,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xwv2yy4yt35rtaqt27uj,task_subcomment,NA
+VisualEditor: Tab in a slug in Firefox causes a pawn character to be inserted,"Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
+Put the cursor somewhere in the text.
+Type ""Enter"" 2 times.
+Type ""Up"".
+Type ""Tab""
+
+Wild pawn appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368090300,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-7v5fwi2od2mzskuipoyb,task_description,resolved
+VisualEditor: Tab in a slug in Firefox causes a pawn character to be inserted,"This is a duplicate of bug 48022 which was fixed for wmf4 (so should now work beautifully on enwiki). Sorry for the delayed response.
+
+*** This bug has been marked as a duplicate of bug 48022 ***",1369093388,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7v5fwi2od2mzskuipoyb,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,"Examining with user what browser/etc. to investigate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: http://en.wikipedia.org/w/index.php?title=Indo-Pakistani_War_of_1965&diff=prev&oldid=552704403",1367950620,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vqvckkamqnznu7z5ud6j,task_description,resolved
+VisualEditor: Dirty diffs causing some citations to be duplicated,"On review, this is already fixed in master and will be deployed (as part of wmf4) to the English Wikipedia on 20 May.",1368803220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,"(In reply to comment #4)
+> To me it looks like the VE is dropping a link (with template encapsulation
+> info) near '165 Pakistan tanks' when editing
+> http://en.wikipedia.org/w/index.php?title=Indo-
+> Pakistani_War_of_1965&oldid=551447483.
+> So it looks like a VE bug to me. Can you verify?
+That bug is fixed in the most recent VE release, which is live on mw.org but hasn't hit enwiki yet. Compare https://en.wikipedia.org/wiki/User:Catrope/India-Pakistan and https://www.mediawiki.org/wiki/User:Catrope/India-Pakistan .",1368773561,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,To me it looks like the VE is dropping a link (with template encapsulation info) near '165 Pakistan tanks' when editing http://en.wikipedia.org/w/index.php?title=Indo-Pakistani_War_of_1965&oldid=551447483. So it looks like a VE bug to me. Can you verify?,1368724692,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,Can you provide us with a test case and verify that the DOM change looks sane?,1368720633,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,"Gabriel - As far as I can tell, this bug is coming from Parsoid rather than VisualEditor - can you confirm? I can replicate in VE and Parsoid master locally.",1368720428,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Dirty diffs causing some citations to be duplicated,"There was a Parsoid bug to this effect earlier, maybe it came back?",1367950671,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-vqvckkamqnznu7z5ud6j,task_subcomment,NA
+VisualEditor: Typing at the end of linked causes DM and CE to get out of sync,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367866920,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zzjrcgydauwz7h5g6ufd,task_description,resolved
+VisualEditor: Typing at the end of linked causes DM and CE to get out of sync,Trevor's commit has been merged; assigning to Inez for the IE-specific fixes to come.,1367886453,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zzjrcgydauwz7h5g6ufd,task_subcomment,NA
+VisualEditor: Typing at the end of linked causes DM and CE to get out of sync,Related URL: https://gerrit.wikimedia.org/r/62481 (Gerrit Change I5f279b06b098960be7bd4ad3f5e6f74b67e31d1a),1367870942,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zzjrcgydauwz7h5g6ufd,task_subcomment,NA
+VisualEditor: Typing at the end of linked causes DM and CE to get out of sync,"This doesn't happen in IE.
+
+1. Place the cursor at the end of a link.
+2. Type some text
+3. See that the text doesn't appear to be linked, but the link inspector option is available
+
+Short term solution as decided by Trevor, Inez and James: Make links not auto-extend in the model, and fix IE so it doesn't auto-extend in the view (to make it work like other browsers).",1367867552,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-zzjrcgydauwz7h5g6ufd,task_subcomment,NA
+VisualEditor: Unexpected non-pawn characters appear after CTRL-B and CTRL-I,"unexpected untyped characters
+
+Upon loading page in VE: 
+
+Click CTRL-B and type some characters; 
+click CTRL-I and type some characters; 
+
+* often but not always reproducible, seen in Chrome/OSX, also reported in IE and FF: upon typing after ctrl-B or ctrl-I for ""bold"" or ""italic"", characters appear that have not been entered.  see screen shot
+
+* possibly related, seen but not reproducible:  some combination of actions will cause VE to type a string into a page over and over and over without any action on the part of the user.  I'll file a new bug if I can figure out how to repron that behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11070}",1367863980,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-zoij2t4he6jsr6wfqjde,task_description,resolved
+VisualEditor: Unexpected non-pawn characters appear after CTRL-B and CTRL-I,I believe we fixed this with the new insertion logic last week. Please re-open if you can reproduce still.,1371781126,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zoij2t4he6jsr6wfqjde,task_subcomment,NA
+VisualEditor: Unexpected non-pawn characters appear after CTRL-B and CTRL-I,@James: Feel free to assign to me.,1367864226,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-zoij2t4he6jsr6wfqjde,task_subcomment,NA
+VisualEditor: Pre-annotations not working in spans,"From this bug report on parsoid.wmflabs.org: /mnt/bugs/2013-05-04T01:11:28.439Z-Style_guide%252FAssets_and_gallery
+
+""I typed some text in this paragraph that is styled as a span italic, and VE decided to close and reopen the span on either side of the link. I think that happened before I made the text a link. (This is User:S Page (WMF) here.)""
+
+Relevant diff line below:
+
+− 	
+:<span style=""font-style: italic;"">See Also: [[Commons:Category:MediaWiki style guide]]</span>
+
++ 	
+:<span style=""font-style: italic;"">See also: </span>[[Wikimedia Foundation Design/Agora Icon Set]] and<span style=""font-style: italic;""> [[Commons:Category:MediaWiki style guide]]</span>
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1367852460,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_description,resolved
+VisualEditor: Pre-annotations not working in spans,"(In reply to comment #3)
+> Can you explain more clearly how this is still broken? What do you mean by
+> pre-annotation?
+
+On re-testing, this comes down to copy-and-paste inserted content not continuing the existing annotations of the styles into which it had been inserted. Marking as such.
+
+*** This bug has been marked as a duplicate of bug 48720 ***",1369247921,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_subcomment,NA
+VisualEditor: Pre-annotations not working in spans,Can you explain more clearly how this is still broken? What do you mean by pre-annotation?,1369221776,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_subcomment,NA
+VisualEditor: Pre-annotations not working in spans,"OK, we've fixed the secondary issues I was having; have narrowed down the original bug to pre-annotations not being applied to the insertion of text into this context - changing this to suit.",1368719960,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_subcomment,NA
+VisualEditor: Pre-annotations not working in spans,"I think that this partially interacts was a bug that Ed found independently - bug 48110 (now fixed in master). I do not get the span adjusted, but instead get:
+
+:<span style=""font-style: italic;"">See Also: <a href=""Wikimedia_Foundation_Design%2FAgora_Icon_Set"" rel=""mw:WikiLink"">Wikimedia Foundation Design/Agora Icon Set</a> and [[Commons:Category:MediaWiki style guide|<nowiki/>]]<a href=""Commons%3ACategory%3AMediaWiki"" rel=""mw:WikiLink"">Commons:Category:MediaWiki</a> style guide</span>
+
+... which is a total mess.",1367876474,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wiwrmd5v2ykgptbszxoc,task_subcomment,NA
+VisualEditor: [Regression] Link insertion annotation makes it difficult to add plain text after a link,"If you add a link to the last word in your paragraph (quite common I'd imagine if you're in the middle of typing a sentence), the insertion annotation behaviour makes any text typed after the link part of that link - which in most cases is not what you meant to do.
+
+Insertion annotations make sense for text style annotations, but not link annotations. This is what Google Docs & LibreOffice do aswell.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367794320,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hwpwpa3athddhod7xlp4,task_description,resolved
+VisualEditor: [Regression] Link insertion annotation makes it difficult to add plain text after a link,Fixed by https://gerrit.wikimedia.org/r/#/c/62481/,1368373764,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hwpwpa3athddhod7xlp4,task_subcomment,NA
+VisualEditor: [Regression] Link insertion annotation makes it difficult to add plain text after a link,"This is a regression - it used to be that there were two types of annotations - one (bold/italics/etc.) would pre-annotate over word breaks, and the other wouldn't. I believe that the code to do this used to sit in CE - has it been removed, or is it not working somehow?",1367808687,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hwpwpa3athddhod7xlp4,task_subcomment,NA
+"VisualEditor: Access keys - leave Ctrl+Option+e for the (newly-relabelled) ""edit source"" tab; Add Ctrl+Option+v for the VisualEditor ""edit"" tab","Currently we steal all the things on action=edit for veaction=edit (so Ctrl-Option-e goes to VisualEditor, leaving nothing for the wikitext editor). We should add a new one - Ctrl-Option-s (for *s*ource) - though that's used for save in the wikitext editor, which is a bit odd. Ideas?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1367769060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uhuq2co3arbcvjn3js5m,task_description,resolved
+"VisualEditor: Access keys - leave Ctrl+Option+e for the (newly-relabelled) ""edit source"" tab; Add Ctrl+Option+v for the VisualEditor ""edit"" tab",Fixed in master.,1368232252,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uhuq2co3arbcvjn3js5m,task_subcomment,NA
+"VisualEditor: Access keys - leave Ctrl+Option+e for the (newly-relabelled) ""edit source"" tab; Add Ctrl+Option+v for the VisualEditor ""edit"" tab",Related URL: https://gerrit.wikimedia.org/r/63231 (Gerrit Change I598177bc75ed84dea35952a3b2b1b2111aac89b2),1368223225,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uhuq2co3arbcvjn3js5m,task_subcomment,NA
+"VisualEditor: Access keys - leave Ctrl+Option+e for the (newly-relabelled) ""edit source"" tab; Add Ctrl+Option+v for the VisualEditor ""edit"" tab","Change of plans:
+* Leave -e for the wikitext editor tab
+* Add -v for the VisualEditor tab",1368209183,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uhuq2co3arbcvjn3js5m,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"I changed a link here: http://sv.wikipedia.org/w/index.php?title=Intellektuell_s%C3%A4rbeg%C3%A5vning&diff=21539781&oldid=21539483
+
+In the VisualEditor interface, the word ""Känsla"" is showed with a lower case k, but when you are looking at the article, or source it is K.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367618160,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_description,resolved
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"(In reply to comment #4)
+> As we're generating the correct HTML surely this is just a Parsoid bug, not a
+> VE bug.
+
+Yeah, point.
+
+*** This bug has been marked as a duplicate of bug 48477 ***",1368631481,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"As we're generating the correct HTML surely this is just a Parsoid bug, not a VE bug.",1368628645,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],Depends on a Parsoid regression being fixed.,1368574562,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"I just hit the same again.
+
+* Text ""foo"".
+* Link it, page ""Foo"" exists.
+* Close link editor.
+* Page shows ""text <a href=""./Foo"">foo</a> text"".
+* Saving turns it into [[Foo]], thus ignoring the case of the label.",1368573811,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]],"Thank y(In reply to comment #0)
+> I changed a link here:
+>
+> http://sv.wikipedia.org/w/index.php?diff=21539781&oldid=21539483
+> 
+> In the VisualEditor interface, the word ""Känsla"" is showed with a lower case
+> k, but when you are looking at the article, or source it is K.
+
+Thank you for your bug report, Jan! Hope to get this fixed soon.",1367895881,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fkhtpgjkzrvqucqxny7q,task_subcomment,NA
+VisualEditor: Pawn characters created when moving cursors around inline images in Firefox,"All the pawns
+
+See attached image, basically the idea is that indenting or de-indenting a list item will cause there to be a pawn in the list item. Also, when I used the arrow keys to navigate past some images, it put pawns next to the images.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10767}",1367532360,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-sw2uw4ekzaqwybdqmbq6,task_description,resolved
+VisualEditor: Pawn characters created when moving cursors around inline images in Firefox,This is now fixed in wmf4 (which is the current in-production version); marking as such.,1369098863,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sw2uw4ekzaqwybdqmbq6,task_subcomment,NA
+VisualEditor: Pawn characters created when moving cursors around inline images in Firefox,"Nothing about the list or indenting, just the cursor keys trigger it (Firefox only).",1367545948,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sw2uw4ekzaqwybdqmbq6,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",The order should be Edit then Edit tab. Looks like a hard-coded left somewhere?,1367527740,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_description,resolved
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381217 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.init.mw.DesktopArticleTarget: Fix the code to reorder tabs
+
+[[https://gerrit.wikimedia.org/r/381217]]
+",1506613751,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381217 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.init.mw.DesktopArticleTarget: Fix the code to reorder tabs
+
+[[https://gerrit.wikimedia.org/r/381217]]
+",1506606897,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","After trying to verify the fix during the SWAT deployment, I found out that this entire feature (fixing up the tab order if wgVisualEditorTabPosition was changed and we're seeing cached HTML with the tabs in wrong order) is actually entirely broken and just does nothing. The deployment was essentially a no-op. This is actually convenient because had it worked, it would have been messing up the tabs.",1506606636,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AV7ItYHmF4fsM4DBdIoK} [2017-09-28T13:38:12Z] <zfilipin@tin> Synchronized php-1.31.0-wmf.1/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.DesktopArticleTarget.init.js: SWAT: [[gerrit:381210|ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector (T50017)]] (duration: 00m 50s)",1506605892,PHID-USER-j4uyesgqhubl2dywl4xd,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381210 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@wmf/1.31.0-wmf.1] ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector
+
+[[https://gerrit.wikimedia.org/r/381210]]
+",1506604497,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381210 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@wmf/1.31.0-wmf.1] ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector
+
+[[https://gerrit.wikimedia.org/r/381210]]
+",1506602050,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381167 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector
+
+[[https://gerrit.wikimedia.org/r/381167]]
+",1506589079,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",(This will need to be backported to 1.31.0-wmf.1.),1506577515,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","Change 381167 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.init.mw.DesktopArticleTarget: Remove hack for reversed tabs in RTL in Vector
+
+[[https://gerrit.wikimedia.org/r/381167]]
+",1506576918,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","With the underlying issue T48947 being fixed, our workaround is now unnecessary and in fact reintroduces this issue. We should remove it.",1506576890,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",*** Bug 47684 has been marked as a duplicate of this bug. ***,1368639099,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",Merged into master.,1368232328,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""",Related URL: https://gerrit.wikimedia.org/r/63153 (Gerrit Change Ie1214b08450aefed893739a2b862cb1e9b23a2ef),1368210908,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+"VisualEditor: In RTL, the ""Edit"" tab appears down-tab (to the left) rather than up-tab (to the right) of ""Edit source""","This is caused by bug 46947 – the HTML order of tabs is reversed, then reversed again in the CSS...",1367527956,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-l6veaqa2gygvcgf2ywhf,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,"There are probably two solutions - make it work - or disable list buttons while in block slug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367431680,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-ht3d5xeklsjuq5qulguj,task_description,resolved
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,Fixed and will be deployed later today.,1372704235,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,"Change 71353 merged by jenkins-bot:
+Allow creating lists in block slugs
+
+https://gerrit.wikimedia.org/r/71353",1372704109,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,"Change 71353 had a related patch set uploaded by Jforrester:
+(bug 47947) Allow creating lists while selection is collapsed and in block slug
+
+https://gerrit.wikimedia.org/r/71353",1372691992,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,"Change 71353 had a related patch set uploaded by Inez:
+(bug 47947) Allow creating lists while selection is collapsed and in block slug
+
+https://gerrit.wikimedia.org/r/71353",1372689599,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,*** Bug 50242 has been marked as a duplicate of this bug. ***,1372271165,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug,Make it work is better. :-),1367545095,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ht3d5xeklsjuq5qulguj,task_subcomment,NA
+VisualEditor: heading removal adds ♙,"The user was trying to edit http://de.wikipedia.org/w/index.php?title=Reiniger,_Gebbert_%26_Schall&direction=prev&oldid=117917379 to remove the first heading but keep the image. The result was http://de.wikipedia.org/w/index.php?title=Reiniger,_Gebbert_%26_Schall&direction=next&oldid=103767568 and the didn't manage to do it without adding the ♙.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367427120,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_description,resolved
+VisualEditor: heading removal adds ♙,I think our changes related to pawns also has fixed this bug; marking as closed.,1368548559,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,"Sorry, yes. It's Firefox (20.0.1, Windows 7).
+
+Steps to reproduce according to user:
+* open http://de.wikipedia.org/w/index.php?title=Reiniger,_Gebbert_%26_Schall&oldid=103767568
+* edit with VisualEditor
+* select first heading ""Aufbau und Expansion des Unternehmens""
+* remove using del-key
+* ♙ appears",1368536309,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,Lydia: Any response on that?,1368216819,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,I asked at http://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Alpha2013-04#Absatzmarker_.28.E2.99.99.29,1367511693,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,I think it might be the FF specific bug for which we already have fix (but it is not released yet).,1367434380,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: heading removal adds ♙,Could you provide steps to reproduce (I tried and I can't) and information about browser/OS?,1367430685,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-rf6xvihdg3l2eowhdgrm,task_subcomment,NA
+VisualEditor: Support <div> blocks,"This just means supporting their use, not being able to set their parameters, but will de-alienate a large amount of content for trivial work at our end. The parameter setting/editing will need to come later.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1367371680,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-erliezrdqnohfykefn5r,task_description,resolved
+VisualEditor: Support <div> blocks,Merged; will go out with wmf4.,1367372802,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-erliezrdqnohfykefn5r,task_subcomment,NA
+VisualEditor: Support <div> blocks,"(In reply to comment #1)
+> Feel free to assign it to me.
+
+Too late, already written the code. :-)",1367372023,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-erliezrdqnohfykefn5r,task_subcomment,NA
+VisualEditor: Support <div> blocks,Related URL: https://gerrit.wikimedia.org/r/61737 (Gerrit Change I794927a881082e0113c0ce8ee8f1d908b0960899),1367371959,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-erliezrdqnohfykefn5r,task_subcomment,NA
+VisualEditor: Support <div> blocks,Feel free to assign it to me.,1367371782,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-erliezrdqnohfykefn5r,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","Screenshot of LQT thread with </div> in title
+
+Should be treated the same as regular page titles: Escape everything.
+
+
+Or, if we want to keep wikitext parsing (e.g. for wikilinks, sometimes done in section headings), then parse as inline block (not allowing any block level elements like <div> or <table>) and make sure open/close tags match (run Tidy).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://www.mediawiki.org/wiki/Thread:Project:Support_desk/visible_html_on_pages%3A
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=31244
+https://bugzilla.wikimedia.org/show_bug.cgi?id=29564
+
+**Attached**: {F10533}",1367340180,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_description,invalid
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true",[We don't use Tidy anymore](https://www.mediawiki.org/wiki/Parsing/Replacing_Tidy) since 2016,1644958499,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","Suggest decline this task, such problem are mostly from PHP which is a bit more #upstream ed",1553220752,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","Suggest decline this task, such problem are mostly from PHP which is a bit more #upstream-ed",1553220744,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","LiquidThreads has been replaced by #Flow on all Wikimedia production wikis (except one, which will be done soon). It is no longer under active development or maintenance, so I'm re-classifying all open LQT tasks as ""Lowest"" priority.",1470353645,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","A similar problem in a topic named ""Handling <pre><ref></pre> with trailing slash does not work correctly"":
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Handling_ref_with_trailing_slash_does_not_work_correctly",1413467796,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true",This is one of the many places with poor or inconsistent escaping in LQT.,1377841711,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","(In reply to comment #1)
+> @Krenair: You change the summary to include ""with wgUseTidy = true;"" Are you
+> saying that when Tidy is disabled this bug does not happen?
+
+
+Yes. I have to add that to my configuration to replicate this bug.",1367358730,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+"Thread title containing ""</div>"" destroys entire page with $wgUseTidy = true","@Krenair: You change the summary to include ""with wgUseTidy = true;"" Are you saying that when Tidy is disabled this bug does not happen?
+
+Seems more like the opposite?",1367355713,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-o6h5thx2nxd7xpm2ferq,task_subcomment,NA
+VisualEditor: Blanked page content in edit mode using Firefox,"VisualEditor (50e8693)
+Parsoid (ba0b080)
+MW: 1.22/wmf2 (814f75e)
+
+While editing a page in Firefox 20.0, the existing page content is blank in the editor.
+
+The issues seems to be an issue with Firefox only, as Chrome and Safari work as expected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**OS**: Mac OS X 10.7
+**Platform**: Macintosh",1367254380,PHID-USER-evwol34rsld7viokxokd,False,PHID-TASK-njwlhw4yezfqfiviad2b,task_description,resolved
+VisualEditor: Blanked page content in edit mode using Firefox,We have identified this bug and fixed it in live (for mediawiki.org - other wikis will be going out in the next few days); sorry for the difficulty.,1367288171,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-njwlhw4yezfqfiviad2b,task_subcomment,NA
+VisualEditor: Blanked page content in edit mode using Firefox,"Is this on the Wikimedia cluster or locally? If on the cluster, is it on all pages or just one or two?",1367275473,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-njwlhw4yezfqfiviad2b,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,"VE error when not completely loaded
+
+on any page editable by VE:
+
+invoke VE
+immediately click Preferences or other live link
+
+an alert appears saying ""Error loading data from server: error. Would you like to retry?""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10400}",1367196780,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-s7xxo6pqgoai7qxiqran,task_description,resolved
+VisualEditor: Clicking away before VE loads completely throws JS error,Merged; will go out with wmf5.,1368885099,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,Related URL: https://gerrit.wikimedia.org/r/64333 (Gerrit Change Ide5def0e983bab49108b40008fc170957c7fc2a2),1368809323,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,"Actually, this looks like a different bug (but in the same loop).",1368655903,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,"From Ed's comment:
+
+In ve.init.mw.ViewPageTarget.prototype.tearDownToolbar, this.toolbar is
+undefined if the editor hasn't finished loading.",1368654683,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Clicking away before VE loads completely throws JS error,*** Bug 48520 has been marked as a duplicate of this bug. ***,1368654670,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s7xxo6pqgoai7qxiqran,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,"Hi,
+
+The problem is that when I have created a bullet list in Visual Editor and try to erase back the text using Backspaces, the numbers or bullet points don't delete even if I have deleted the whole text. Here is a trivial demonstration :
+
+1. Hello1
+2. Hello2
+3. Hello3
+
+Now when I try to delete it from the Hello3 using backspaces, all the text upto first bullet is deleted, but those bullet points are left as it is. 
+
+1.
+
+2.
+
+3.
+
+
+Images:
+
+https://docs.google.com/file/d/0B3eGCB261PalaDhqa1ZhcmFPUk0/edit?usp=sharing
+https://docs.google.com/file/d/0B3eGCB261PalbndsZEFSdXpEZGM/edit?usp=sharing
+
+Tested on Firefox 20.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367169780,PHID-USER-d3oiyxwdmebcjszfff7w,False,PHID-TASK-4rlrewbrchltpzty4e37,task_description,resolved
+VisualEditor: Backspace over lists doesn't delete the LIs,And now fixed in wmf4.,1368565464,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,This is now broken again in master. :-(,1368211380,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,*** Bug 48293 has been marked as a duplicate of this bug. ***,1368129697,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,Wmf4 which will begin deployment on 13 May. :-),1367373980,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,"Fixed here: https://gerrit.wikimedia.org/r/61520
+It is not released yet, James, can you put appropriate milestone tag?",1367359540,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+VisualEditor: Backspace over lists doesn't delete the LIs,Thanks for the bug report; I can confirm in Chrome and Safari as well.,1367170322,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rlrewbrchltpzty4e37,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Add button to WikiEditor and VisualEditor for switching back and forth.
+
+* Only shown if in WE you have VE enabled (otherwise don't show)
+* If no changes, switch immediately
+* If there are changes, prompt the user (with the same OOUI message dialog we use in VE) whether to switch with or without their changes",1367087280,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_description,resolved
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 250965 merged by jenkins-bot:
+Target init: Add edit mode switch icons to VE and WE toolbars
+
+[[https://gerrit.wikimedia.org/r/250965]]",1446648058,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 250965 had a related patch set uploaded (by Jforrester):
+Target init: Add edit mode switch icons to VE and WE toolbars
+
+[[https://gerrit.wikimedia.org/r/250965]]
+",1446646795,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 250939 merged by jenkins-bot:
+Target init: Add edit mode switch icons to VE and WE toolbars
+
+[[https://gerrit.wikimedia.org/r/250939]]",1446646490,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"More prominent VE switcher:
+{F2913511}
+
+WikiEditor switcher (top right):
+{F2913515}",1446632107,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 250939 had a related patch set uploaded (by Esanders):
+Target init: Add edit mode switch icons to VE and WE toolbars
+
+[[https://gerrit.wikimedia.org/r/250939]]
+",1446631989,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 245593 merged by jenkins-bot:
+Allow switching from wikitext to VE
+
+[[https://gerrit.wikimedia.org/r/245593]]",1446506314,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Change 245593 had a related patch set uploaded (by Alex Monk):
+[WIP][POC][DONOTMERGE] Allow switching from wikitext to VE
+
+[[https://gerrit.wikimedia.org/r/245593]]
+",1444684486,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,">>! In T49779#1172521, @Jdforrester-WMF wrote:
+>>>! In T49779#1172511, @Krenair wrote:
+>> We should talk to #Parsoid to work out what dependencies this has from them, if any
+> 
+> It's mostly a RESTbase dependency, at this point.
+
+Perhaps we should make a separate task for the RESTbase/Parsoid dependencies here.",1435777029,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,This would be a great enhancement!,1431055639,PHID-USER-p6hvqn5njgnxuagekh4b,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,">>! In T49779#1172511, @Krenair wrote:
+> We should talk to #Parsoid to work out what dependencies this has from them, if any
+
+It's mostly a RESTbase dependency, at this point.",1427931868,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"We should talk to #Parsoid to work out what dependencies this has from them, if any",1427931774,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to Alex Monk from comment #17)
+> So with the resolution of bug 50687, this is effectively ""Provide a way for
+> the user to switch from the wikitext source editor to VisualEditor, keeping
+> changes but not saving"", right?
+
+Yes, as I understand it.  Adding that direction would then allow bidirectional switching.",1407181934,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"So with the resolution of bug 50687, this is effectively ""Provide a way for the user to switch from the wikitext source editor to VisualEditor, keeping changes but not saving"", right? Or have I misunderstood?",1407032261,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Sweedish Wikipedians including User:Jan Ainali and User:FrankieF are discussing/requesting an enhancement to VisualEditor here [1] and translate the thread as follows:
+
+""What we are missing is way to easily switch between wikitext and VE without saving or loosing stuff. Just like you can in Wordpress between the WYSIWYG and HTML editor."" 
+
+[1]
+https://sv.wikipedia.org/wiki/Wikipedia:VisualEditor/%C3%85terkoppling#Saknade_funktioner_i_Redig.l.C3.A4get",1381789003,PHID-USER-brn4v5ta45bnw4f5as3h,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #14)
+> (In reply to comment #13)
+> > (In reply to comment #12)
+> > > This functionality was requested back in December 2011 in bug 33124.
+> > 
+> > No? The diff view of the wikitext is not even a read-only view of the entire
+> > document's wikitext, let alone an editable one? Also, quickly editing the
+> > diff
+> > in a pop-over window is fundamentally different paradigm from having a proper
+> > wikitext editor available to all users at all times, and being able to switch
+> > back and forth, which is what this bug requests.
+> 
+> From what I remember about the feature which existed in the prototype which
+> motivated the request made on bug 33124, it actually displayed the entire
+> document's wikitext (not just the diff).
+
+Oh, yes, you are right. My apologies.
+
+This means that that bug is even further from ""this functionality"", however.",1381334205,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #13)
+> (In reply to comment #12)
+> > This functionality was requested back in December 2011 in bug 33124.
+> 
+> No? The diff view of the wikitext is not even a read-only view of the entire
+> document's wikitext, let alone an editable one? Also, quickly editing the
+> diff
+> in a pop-over window is fundamentally different paradigm from having a proper
+> wikitext editor available to all users at all times, and being able to switch
+> back and forth, which is what this bug requests.
+
+From what I remember about the feature which existed in the prototype which motivated the request made on bug 33124, it actually displayed the entire document's wikitext (not just the diff).",1381333880,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #12)
+> This functionality was requested back in December 2011 in bug 33124.
+
+No? The diff view of the wikitext is not even a read-only view of the entire document's wikitext, let alone an editable one? Also, quickly editing the diff in a pop-over window is fundamentally different paradigm from having a proper wikitext editor available to all users at all times, and being able to switch back and forth, which is what this bug requests.",1381329923,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,This functionality was requested back in December 2011 in bug T35124.,1434266616,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,This functionality was requested back in December 2011 in bug 33124.,1381301841,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #10)
+> Im not immediately inclined to work on SE->VE, as that could facilitate
+> people
+> playing games with the wikitext in order to put dodgy entries into the
+> 'VisualEditor' tagged edit list, which would be impossible to debug.
+
+That could be mitigated with an editfilter or some other indication that an editor had used both modes. Whether such would be possible or desirable is another matter",1375211326,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"I have built a script which switches from VE to SE.
+https://en.wikipedia.org/wiki/User:John_Vandenberg/switch_editor
+
+I havent looked at whether the API and VE codebase can support switching from SE back to VE, but it seems like JS could obtain rendered HTML (action=parse?) and load it into VE.
+
+Im not immediately inclined to work on SE->VE, as that could facilitate people playing games with the wikitext in order to put dodgy entries into the 'VisualEditor' tagged edit list, which would be impossible to debug.",1374296995,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,*** Bug 50698 has been marked as a duplicate of this bug. ***,1373855340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #7)
+> See also:
+> * [[Thread:VisualEditor/Feedback/ Side-by-side view (no more?)]]
+
+Helder. I corrected the link (I hope):
+* [[mw:Thread:VisualEditor/Feedback/ Side-by-side view (no more?)]]
+
+See: [[WP:Bugzilla]] and the section currently titled ""Links from within Bugzilla"".
+
+Hey Helder. Maybe you can develop a preview mode for Bugzilla? :) Bugzilla needs a ""preview"" mode:
+*https://bugzilla.mozilla.org/show_bug.cgi?id=40896",1372983348,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"See also:
+* [[Thread:VisualEditor/Feedback/ Side-by-side view (no more?)]]
+* Old demo with side-by-side view:
+http://blog.wikimedia.org/2011/12/13/help-test-the-first-visual-editor-developer-prototype/visual-editor-demo-2/",1372878442,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,Adding 'source' to subject line to make this easier to search.,1372787226,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,*** Bug 49986 has been marked as a duplicate of this bug. ***,1371855868,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"**winne2i** wrote:
+
+I'm asking again if this is very difficult to achieve this by adding (even temporarily!) a regular Preview button, which will allow us to see the source code of already changed content? As I said before we can already see diffs so seeing a preview should be quite easy IMO.
+
+As far as refs are concerned – I agree that's very important. But let me notice that introducing such Preview button would allow to add references in that later step (editing the source code). That would be a great instant (but somewhat temporary) solution for both problems. Then one may work on pretty way of adding refs.
+
+Doesn't it sound good? :)",1371556666,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"(In reply to comment #2)
+> Just pointing out that this is very frequently requested by enwiki users at
+> [[Wikipedia:VisualEditor/Feedback]]. 
+> 
+> I know bug priority is technically up to the developers, but just letting you
+> know that a lot of people want this.
+
+We understand, and I really want to be able to provide this, but in the choice between this and being able to add references (say) we have to prioritise. However, I'm going to see if we can try to get it done in the next few weeks. Sorry for not being able to make a firm commitment.",1371521807,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"Just pointing out that this is very frequently requested by enwiki users at [[Wikipedia:VisualEditor/Feedback]]. 
+
+I know bug priority is technically up to the developers, but just letting you know that a lot of people want this.",1371521045,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving,"**winne2i** wrote:
+
+To me that doesn't seem to be compliacted to acheive. The way could be to add a button which opens regular Preview (with wikitext editing).
+We already can see the diff, so adding regular preview should not be difficult.
+
+And this can be a big convenience because it's easier to edit in VE but we still can't edit/insert some elements like templates.",1369048522,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rrfiavqqnofzrlok2ea7,task_subcomment,NA
+"VisualEditor: Edit vs. edit source tab split not preserved across action=history, action=edit, Special:Undelete, …","Right now you get | Edit | Edit source | on read and on VE edit (which are the same thing) but nowhere else, which is confusing.
+
+(Whilst we're at it, logs, diff view pages, and probably a few dozen others have edit links which will need to be replaced or augmented.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367086560,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zcmfiyirjhsjlqbiehnf,task_description,resolved
+"VisualEditor: Edit vs. edit source tab split not preserved across action=history, action=edit, Special:Undelete, …",This was fixed by Ed in his commit last week.,1367860149,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zcmfiyirjhsjlqbiehnf,task_subcomment,NA
+"VisualEditor: Edit vs. edit source tab split not preserved across action=history, action=edit, Special:Undelete, …","Once we're deployed for all users, we could simply replace the ""Edit"" message with ""Edit source"" in core which would manage the first half; we'd still need to add the (VE) ""Edit"" tab to these extra places (and the other stuff like ""(edit)"" links in diff views).",1367097655,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zcmfiyirjhsjlqbiehnf,task_subcomment,NA
+"VisualEditor: Edit vs. edit source tab split not preserved across action=history, action=edit, Special:Undelete, …","Setting ""High"" for action=edit; the others can be fixed, I guess.",1367086643,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zcmfiyirjhsjlqbiehnf,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"In [[en:User:Yamaha5/sandbox]] I tested it for Farsi every thing was OK except <div dir=""rtl""><div> which cause the test disable. in fa.wiki because of mixture of farsi and english or LTR Math formulas we use direction inside the text so it will cause problem for RTL languages
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367020500,PHID-USER-dswbdv7ibhsefllcqarz,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_description,resolved
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 95051 merged by jenkins-bot:
+MediaWiki language inspector updates
+
+https://gerrit.wikimedia.org/r/95051",1390007205,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 95051 had a related patch set uploaded by Jforrester:
+MediaWiki language inspector updates
+
+https://gerrit.wikimedia.org/r/95051",1390006945,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,Splitting the block level items into bug 60187.,1390006865,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"The main work is merged. Some designs tweaks are still needed, but now language for <span>s can be set.",1375256723,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 72634 merged by jenkins-bot:
+Language Inspector UI
+
+https://gerrit.wikimedia.org/r/72634",1375254898,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 72634 had a related patch set uploaded by Mooeypoo:
+Language Inspector UI
+
+https://gerrit.wikimedia.org/r/72634",1374630395,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 70560 merged by jenkins-bot:
+Language Inspector: CE / DM
+
+https://gerrit.wikimedia.org/r/70560",1373483622,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Change 70560 had a related patch set uploaded by Mooeypoo:
+Language Inspector: CE / DM
+
+https://gerrit.wikimedia.org/r/70560",1373482614,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,*** Bug 41009 has been marked as a duplicate of this bug. ***,1373002468,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"(In reply to comment #5)
+> Oy, I mean Bug 41009. Both speak of the same features that the Language
+> Inspector will attempt to solve.
+
+Given that this is more advanced in discussion, I'll up-merge that into this.",1373002441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Oy, I mean Bug 41009. Both speak of the same features that the Language Inspector will attempt to solve.",1372987705,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,I think this is a dupe of Bug 47759,1372987615,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Work on this has began, we will be using <span lang='xx' dir='yyy'> tags to start with and add functionality for broader usages in the future.",1372962330,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"This would be a task for a language inspector, presumably? Marking as an enhancement - this might be something for Moriel if she is going to be working with us on language support.",1367293379,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s,"Clarification: the bug report is about text within <div dir=""rtl""></div> being alienated. I'm not sure how we can intelligently not alienate text with such a direction override.",1367275242,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-yygcicr6m5mpgdgpjccs,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"Ubuntu/Firefox
+Go to http://en.wikipedia.org/wiki/Alfresco_%28software%29
+At the end of a line, add a space and remove it
+Click ""Save""
+No changes should have happen, but there actually are changes, in the infobox:
+
+| caption = Alfresco Share / Repository Browser <br/> (Community Edition)
+became
+| caption =Alfresco Share / Repository Browser <br></table> (Community Edition)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366964340,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_description,resolved
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"(In reply to comment #10)
+> http://en.wikipedia.org/wiki/Anne_Hendershott still shows the same symptoms.
+> Is
+> this fix not yet deployed?
+
+Sorry, the meaning of ""VE-deploy-2013-05-13"" is meant to be pretty clear, but evidently isn't! It'll go out with 1.22wmf4, so on the English Wikipedia on 20 May.",1367901947,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,http://en.wikipedia.org/wiki/Anne_Hendershott still shows the same symptoms. Is this fix not yet deployed?,1367897162,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,We're now three bugs fixed into this stack. Closing. Others should be opened as other bugs.,1367871544,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,Related URL: https://gerrit.wikimedia.org/r/61919 (Gerrit Change I42daaf142e548e5b221ff0a52df0ad24ec6a4fd0),1367449312,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"I tested the following 4 pages and am recording my findings here.  Once we go through the other pages, we should close this bug and create new bugs where necessary.
+
+On the following two pages, I can reproduce in Firefox, but the edit is clean in Chrome.  So, this is definitely Firefox specific, not sure if it is JQuery-related or something else.
+
+* http://en.wikipedia.org/wiki/Timeline_of_portable_computers
+* http://en.wikipedia.org/wiki/Neritina_rubricata
+
+On the following two pages, I can reproduce the spurious diffs in both Firefox and Chrome even though I didn't edit the relevant areas. I haven't looked at the diffs yet.  So, this is quite likely some kind of whitespace change in the DOM that VE sends Parsoid.
+
+* http://en.wikipedia.org/wiki/Timeline_of_portable_computers -- It appears that the table is being marked as edited even though I didn't edit the table.
+
+* http://en.wikipedia.org/wiki/Anne_Hendershott -- the list is being marked as edited because of some whitespace normalization when VE loads/saves the DOM.",1367075006,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"(In reply to comment #4)
+> Do you mean all of the problem mentioned on this page are due to this bug?
+
+Please open separate bug tickets for each bug in future. :-)",1366994200,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,I believe the whitespace changes are a separate issue. Reopening so that those don't get lost.,1366992962,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"Do you mean all of the problem mentioned on this page are due to this bug?
+Cheers!
+Nicolas",1366992621,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"This is an instance of the jQuery bug 47737 - marking as a duplicate.
+
+*** This bug has been marked as a duplicate of bug 47737 ***",1366992520,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"http://en.wikipedia.org/wiki/Anne_Hendershott
+http://ja.wikipedia.org/wiki/BMW_801
+On the contrary, here spaces got inserted.
+
+http://en.wikipedia.org/wiki/List_of_Mexican_telenovelas
+* ''[[Mañana Es Para Siempre]]-''Tomorrow Is Forever''
+becomes
+* ''[[Mañana Es Para Siempre]]-''Tomorrow Is Forever
+
+http://en.wikipedia.org/wiki/Sonic_the_Hedgehog_Vocal_Traxx:_Several_Wills
+http://ja.wikipedia.org/wiki/%E6%9C%A8%E6%A2%A8%E3%82%AC%E3%82%A4%E3%83%89%E3%83%BB%E9%80%B1%E6%9C%AB%E3%81%AE%E9%81%94%E4%BA%BA
+http://ja.wikipedia.org/wiki/%E3%82%A4%E3%83%B3%E3%83%89%E3%82%B7%E3%83%A5%E3%83%A2%E3%82%AF%E3%82%B6%E3%83%A1
+<br/> becomes <br></table>
+
+http://en.wikipedia.org/wiki/Barunga,_Northern_Territory
+| pop = 282 (2006 Census)<ref name=Census2006Y />
+becomes
+| pop =282 (2006 Census)<ref name=Census2006Y ></span>
+
+http://en.wikipedia.org/wiki/Aerial_toll_house
+whole references are duplicated
+
+etc... using http://en.wikipedia.org/wiki/Special:Random and http://ja.wikipedia.org/wiki/%E7%89%B9%E5%88%A5:%E3%81%8A%E3%81%BE%E3%81%8B%E3%81%9B%E8%A1%A8%E7%A4%BA about half of the articles don't roundtrip.",1366966146,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip,"Other faulty roundtrips:
+
+http://en.wikipedia.org/wiki/Neritina_rubricata
+Removes space at end of line
+
+http://en.wikipedia.org/wiki/Timeline_of_portable_computers
+--> || becomes -->||
+
+Should I continue reporting space removals like these 2 ones?
+Or are these spaces removed on purpose?",1366964740,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-hk3rab5lb2jvryjrgppj,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Edit an article
+Press down your keyboard's SHIFT key
+While maintaining SHIFT pressed, press the RIGHT key a few times
+
+EXPECTED: Characters are selected
+ACTUALLY: Characters are deleted
+
+Ubuntu/Firefox
+
+Looks like https://bugzilla.wikimedia.org/show_bug.cgi?id=41062 which had been fixed in October.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366963620,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-czooq62xjeisscbrllhg,task_description,resolved
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"(In reply to comment #8)
+> Still actin' crazy: firefox 20.0, linux.  I hard-refreshed just in case.
+
+You may have hard-refreshed, but you didn't wait for the deployment train which was only three hours ago. :-) Sorry for not mentioning that it's ""fixed pending deploy"" (it'd be great if Bugzilla had that as a status).
+
+Can confirm that it's now fixed in live in Firefox 20.0/Mac.",1367286853,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,This bug is currently fixed in master. It is going to be live on Wikipedia by Wednesday next week. In the meantime it is possible to test on mediawiki.org. However currently (for another 2-3 hours) VE on mediawiki.org is completly broken for FF.,1367281288,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"It would be worthwhile to mention the bug 47795 here, with similar nature of problem.",1367223121,PHID-USER-d3oiyxwdmebcjszfff7w,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Sorry, comment #10 has been split off into bug 47817.",1367217111,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Okay, the turd was a separate bug:
+
+1. Edit a page with an unordered list.
+
+2. Delete all the text on the last line.
+
+3. Press the <delete key>. The bullet should be erased.  Instead, it will remain and the cursor will move to the end of the previous line.
+
+4. down-arrow
+
+5. down-arrow off of the empty line.
+
+Turd appears in the empty line.
+
+6. I did something else with the arrow keys, all of the document's lines were erased (not all part of the <ul>), and the undo buffer could not step backwards.  Aaaa, will reproduce later.",1367216836,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Confirmed. It still doesn't work in Firefox 20.0. Shift+Selection Keys isn't working in normal way. When up or down keys are pressed, the text is selected for the first time, but pressing them for second time gets the selected text deleted.",1367216493,PHID-USER-d3oiyxwdmebcjszfff7w,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Still actin' crazy: firefox 20.0, linux.  I hard-refreshed just in case.
+
+In fact, I had some text highlighted and tried to use <ctrl>-<shift>-left to extend the selection.  My text was deleted, plus a character or two, and then a freakin snail character appeared.  I have yet to find the unicode for that.  It wasn't 1F40C, OMG it was 1f4a9 I was just about to say it looked more like a turd than snail.",1367215830,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,And /now/ it's fixed. :-),1367010986,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,https://gerrit.wikimedia.org/r/61055 (Gerrit Change I1aff295a0958b75697c4d362e0d6095283f37fe8) | change APPROVED and MERGED [by jenkins-bot],1367010696,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Just for my sanity, marking as unfixed until it's merged.",1367010554,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,Fixed in here: https://gerrit.wikimedia.org/r/#/c/61055/,1367004734,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,Related URL: https://gerrit.wikimedia.org/r/61055 (Gerrit Change I1aff295a0958b75697c4d362e0d6095283f37fe8),1367004696,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,"Confirmed, will work on it.",1366997433,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Shift-Right deletes characters instead of selecting in Firefox,Confirm that this occurs in Firefox but not in Chrome.,1366996702,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-czooq62xjeisscbrllhg,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,"Steps to reproduce:
+
+1. Open http://en.wikipedia.org/wiki/CMIS
+2. Press Edit
+3. Press your keyboard's Down key
+4. Wild pawn ♙ appears
+
+Also reproduced on http://ja.wikipedia.org/wiki/%E3%83%95%E3%83%AB%E3%83%BC%E3%83%AB%E3%83%BB%E3%83%89%E3%83%BB%E3%82%BB%E3%83%AB
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366963320,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-3whynfwz7dddsiybr7nr,task_description,resolved
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,Fixed in here: https://gerrit.wikimedia.org/r/#/c/61055/,1367004998,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-3whynfwz7dddsiybr7nr,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,"Confirmed, will work on it.",1366997922,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-3whynfwz7dddsiybr7nr,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,"Reproduced on Firefox 20 on OS X 10.8. 
+
+
+Following error reported in console when pressing down key.
+
+[19:49:36.737] TypeError: this.storeIndexes.slice is not a function @ http://bits.wikimedia.org/ja.wikipedia.org/load.php?debug=false&lang=zh-hans&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Crangy%7Cunicodejs.wordbreak&skin=vector&version=20130426T114825Z&*:48
+
+
+
+Reproduced even when everything is in English:
+
+https://zh.wikipedia.org/w/index.php?title=User:Bencmq-test/2&diff=26351189&oldid=26351184
+
+
+No issue on Chrome or Safari. I took the liberty of marking it as FireFox only.",1366978000,PHID-USER-hoj4lurwi6bejyjy5qlp,False,PHID-TASK-3whynfwz7dddsiybr7nr,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox,"If you keep the Down key pressed, the caret will travel down, dumping a pawn at the end of some paragraphs.
+I am not sure how pawn leaving is decided: For the same paragraph of the same article, sometimes a pawn is dumped and sometimes not.",1366967706,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-3whynfwz7dddsiybr7nr,task_subcomment,NA
+VisualEditor: Hard-coded strings in ve.ui.MWLinkTargetInputWidget.prototype.populateMenu,"From user report:
+
+'externalLink', { '$$': menu$$, 'label': 'External link' }
+'newPage', { '$$': menu$$, 'label': 'New page' }
+'matchingPages', { '$$': menu$$, 'label': 'Matching page' }
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366955760,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-fa5biiyjbod7exipkpqs,task_description,resolved
+VisualEditor: Hard-coded strings in ve.ui.MWLinkTargetInputWidget.prototype.populateMenu,In the end fixed by gerrit 60700 just to be confusing; now merged and will be deployed in the Monday deploy train.,1367019435,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fa5biiyjbod7exipkpqs,task_subcomment,NA
+VisualEditor: Hard-coded strings in ve.ui.MWLinkTargetInputWidget.prototype.populateMenu,Fixed by gerrit 61035. Thanks for the catch!,1366996007,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fa5biiyjbod7exipkpqs,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Matanya/%D7%90%D7%A8%D7%92%D7%96_%D7%97%D7%95%D7%9C_2&diff=14076208&oldid=14076205
+
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Matanya/%D7%90%D7%A8%D7%92%D7%96_%D7%97%D7%95%D7%9C_2&diff=14076218&oldid=14076208
+
+(Others.)
+
+User says they get this when switching he/en and back again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366933140,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_description,declined
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"I cannot reproduce it any more (Firefox 22, Fedora 18). Marking WORKSFORME, but reopen if it still happens.",1373221327,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"Steps to reproduce:
+
+1) open https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Matanya/%D7%90%D7%A8%D7%92%D7%96_%D7%97%D7%95%D7%9C_2&diff=14076208&oldid=14076205
+
+in VE mode.
+
+2) open a new line and go to the beginning of the line. switch for he to en or vice versa on your keyboard.
+
+3) you have a pawn. 
+
+tested on firefox 21 on ubuntu 13.04",1369123443,PHID-USER-u7udgblfyop6qd5wxot6,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),Ping to Amir / matanya for steps to reproduce.,1369093796,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),I still can't reproduce this one. Can I get step-by-step instruction please?,1368216144,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"I don't think this is a dupe of bug 41067 - pawns appearing can have lots of causes (all bugs, but not necessarily the same bug).",1367274946,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"
+
+*** This bug has been marked as a duplicate of bug 41067 ***",1367254472,PHID-USER-u7udgblfyop6qd5wxot6,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),"Firefox 20 on ubuntu 13.04 too. 
+
+Didn't see any error in the JS console.",1367254368,PHID-USER-u7udgblfyop6qd5wxot6,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),I saw it in Firefox 20 on Fedora 18.,1366969520,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),Also - it would be very valuable to know if there are any errors in JS console.,1366934353,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?),Any information about web browser and OS?,1366934083,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-p24deoao7z7cqo3jfmi7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,"EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366932300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_description,resolved
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,Merged and will go out with wmf5 on 27 May.,1369409008,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,Related URL: https://gerrit.wikimedia.org/r/65291 (Gerrit Change I216cdd68014173aa65cad42ddd3d870334be9ead),1369406998,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,"(In reply to comment #2)
+> EditPage uses msg: editingold[1].
+> 
+> [1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en
+
+Ah, yes, whoops. Good catch.",1369256829,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,"EditPage uses msg: editingold[1].
+
+[1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en",1369244923,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page,This looks to be <Revision-info>. :-),1367275878,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hmeryxjc5h5ucj6zkjj7,task_subcomment,NA
+"VisualEditor: After saving a page, the VisualEditor tab points at the oldid content not the new one","Edit a page in VE, press save; enter VE again.
+
+What should happen: You edit the newly-updated page.
+
+What does happen: You edit the content of the page before you updated it (and VE doesn't know it's doing this).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1366932180,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-25426wyep677h7baqpvx,task_description,resolved
+"VisualEditor: After saving a page, the VisualEditor tab points at the oldid content not the new one",*** Bug 48395 has been marked as a duplicate of this bug. ***,1368643696,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-25426wyep677h7baqpvx,task_subcomment,NA
+"VisualEditor: After saving a page, the VisualEditor tab points at the oldid content not the new one","
+
+*** This bug has been marked as a duplicate of bug 47420 ***",1367614840,PHID-USER-3uecblbxq24ycewm2cog,True,PHID-TASK-25426wyep677h7baqpvx,task_subcomment,NA
+"VisualEditor: After saving a page, the VisualEditor tab points at the oldid content not the new one",*** Bug 48021 has been marked as a duplicate of this bug. ***,1367530293,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-25426wyep677h7baqpvx,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,"The VE becomes active on .js and .css pages in the user namespace, even though it is not capable of handling this content type.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/wiki/User:TheDJ/common.js",1366469700,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-mw76lciqtgo7k33dnexw,task_description,resolved
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,*** Bug 48471 has been marked as a duplicate of this bug. ***,1368569378,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,Merged by Catrope.,1368463148,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,Gerrit change 63341,1368307015,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,*** Bug 47768 has been marked as a duplicate of this bug. ***,1367097296,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+VisualEditor: VE should not become active on non-wikitext ContentHandler-type,"Yup, we should expand this more generally to all things that have a different ContentHandler type. We already depend on MW 1.21 in general, so I guess(?) this shouldn't be too much of a problem.",1366470309,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mw76lciqtgo7k33dnexw,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab doesn't become 'active'","If in a page you click 'Edit source', the tab does not receive the 'selected' styling/class as it is supposed to.
+
+This was confirmed with Safari 6 mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1366463880,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_description,resolved
+"VisualEditor: ""Edit source"" tab doesn't become 'active'",*** Bug 48316 has been marked as a duplicate of this bug. ***,1368150918,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab doesn't become 'active'",Now merged and will go live with wmf4.,1367602843,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab doesn't become 'active'",Related URL: https://gerrit.wikimedia.org/r/62145 (Gerrit Change Ic2d42bb3034be25f388b587a00c3f523cfcc163c),1367583532,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab doesn't become 'active'","Pretty sure I made this work a couple of weeks ago, but it might have been broken by the more recent changes to this code.",1366998791,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zn4qygjgu7jjo6j7f6is,task_subcomment,NA
+VisualEditor: data-parsoid attribute sometimes not preserved properly,"a </table> tag is sometimes inserted into data-parsoid when set on a table element, for example in the 'Infobox settlement' at http://en.wikipedia.org/wiki/Beale_Township,_Juniata_County,_Pennsylvania.
+
+Original data-parsoid (part of):
+Beale Township,<br/>Pennsylvania\n
+
+VE output (editedHtml):
+Beale Township,<br></table>Pennsylvania\n
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366407120,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-coiafysv5fwnb2coli72,task_description,resolved
+VisualEditor: data-parsoid attribute sometimes not preserved properly,"
+
+*** This bug has been marked as a duplicate of bug 47417 ***",1366992022,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-coiafysv5fwnb2coli72,task_subcomment,NA
+VisualEditor: Deleting to/from a blank lines fails,"If you have lines like so:
+
+| A
+| B
+| 
+| C
+
+Deleting backwards from up-page of C, or from within the blank line above C, causes the cursor to move (as expected) but no deletion.
+
+Deleting forwards from down-page of B, of from within the blank line below B, causes the cursor to stay (as expected) but no deletion.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366397400,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-na7hdsgn5rcikyp6dgpv,task_description,resolved
+VisualEditor: Deleting to/from a blank lines fails,This is now fixed with the deletion re-write.,1371781860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-na7hdsgn5rcikyp6dgpv,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"(a) open a page in VE and edit it
+(b) save in VE 
+(c) reopen the same page right away in VE
+
+The previous version (rather than saved version) is fetched.  I looked at POST params in chrome and looks like revision id (oldid) being sent is of the older version rather than the saved version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366393860,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-l3samzhuiftku6aijqqt,task_description,resolved
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"(In reply to comment #11)
+> That is bug 50441.
+
+Yes; sorry! :-)",1373061922,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,That is bug 50441.,1373061758,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,Re-closing; new breakage is being tracked as bug 47420.,1373061639,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"This bug was closed as fixed on May 3 but I am still seeing this behavior on mediawiki.org. The second edit after saving loads the previous version of the page, not the current version. A warning ""You are editing an out-of-date revision of this page"" appears, but that doesn't help.",1373015887,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,*** Bug 48021 has been marked as a duplicate of this bug. ***,1367614853,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,*** Bug 47682 has been marked as a duplicate of this bug. ***,1367614840,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,Now merged and will go into wmf4.,1367602814,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,Related URL: https://gerrit.wikimedia.org/r/62168 (Gerrit Change I12ce27c8dc57f7aa753bcf5840635d5fea6b4e80),1367601065,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"(In reply to comment #3)
+> The JSON we get back after a save only contains the plain html and some
+> timestamps. In order for us to update this.oldid we'll need Parsoid to tell
+> us what it is, I think.
+
+Parsoid doesn't know; it's VisualEditor.php which does the actual saving to the DB.",1367595038,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"The JSON we get back after a save only contains the plain html and some timestamps. In order for us to update this.oldid we'll need Parsoid to tell us what it is, I think.",1367578702,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,This is because we don't update this.oldid after saving.,1366998865,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+VisualEditor: Reopening page in VE immediately after saving page in VE loads old version,"Feels like we need to properly review how the integration around oldids works, given the number of issues. :-(",1366395770,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l3samzhuiftku6aijqqt,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","See https://en.wikipedia.org/w/index.php?title=User:Fluffernutter/Kinne&diff=551148728&oldid=551148307
+
+To investigate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366387680,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_description,resolved
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>",This is an instance of the jQuery bug 47737 - marking as FIXED (in the specific instance) but we need a wider fix.,1366992579,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>",*** Bug 47430 has been marked as a duplicate of this bug. ***,1366992022,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","(In reply to comment #7)
+> (In reply to comment #6)
+> > This is a bug in jQuery. To reproduce:
+> 
+> That confirms my suspicion. The bug appeared first after you started using it
+> to avoid dropping figure elements.
+Yup, which is why we can't just go back, because that would break <caption> elements again.
+
+Filed upstream as http://bugs.jquery.com/ticket/13821",1366906990,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","The reason this doesn't happen in Chrome is because Chrome normalizes < to &lt; in attribute values in .innerHTML. Firefox doesn't do this and gives us the original < as originally provided by Parsoid.
+
+The presence of these <> then triggers a jQuery regex looking for self-closing tags:
+
+/<(?!area|br|col|embed|hr|img|input|link|meta|param)(([\w:]+)[^>]*)\/>/gi
+
+...which believes our span (!) is self-closing because it starts with <span and contains /> later, so it helpfully ""fixes"" our HTML and replaces the /> with </span>",1366906954,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","Ed's quick hack is now merged, but we still need to fix this - upstream bug in jQuery or just a work around?",1366906093,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","(In reply to comment #6)
+> This is a bug in jQuery. To reproduce:
+
+That confirms my suspicion. The bug appeared first after you started using it to avoid dropping figure elements.",1366904572,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","This is a bug in jQuery. To reproduce:
+
+>>> $( '<div>' ).html( '<span data-parsoid=""{&quot;src&quot;:&quot;<ref name=\&quot;Foo\&quot; />&quot;,&quot;tsr&quot;:[32,50],&quot;dsr&quot;:[32,50,null,null]}"">' ).html();
+
+""<span data-parsoid=""{&quot;src&quot;:&quot;<ref name=&quot;Foo&quot; ></span>&quot;,&quot;tsr&quot;:[32,50],&quot;dsr&quot;:[32,50,null,null]}""></span>""",1366904257,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","This is what I see using wget, FF, and the parse.js in the shell:
+
+<span id=""cite_ref-rfc3092-1-0"" class=""reference"" about=""#mwt5"" typeof=""mw:Object/Ext/Ref"" data-parsoid='{""src"":""<ref name=\""rfc3092\"" />"",""tsr"":[416,438],""dsr"":[416,438,null,null]}'><a href=""#cite_note-rfc3092-1"" data-parsoid=""{}"">[1]</a></span><meta typeof=""mw:Ext/Ref/Marker"" about=""#mwt5"" group="""" name=""rfc3092"" content="""" skiplinkback=""0"" data-parsoid='{""tsr"":[416,438],""selfClose"":true,""src"":""<ref name=\""rfc3092\"" />"",""dsr"":[416,438,22,0]}'>
+
+Make sure you are not looking at a pretty-printed inspect tool. Either use innerHTML (which will use non-smart quoting) or the actual page source (ctrl-u in Firefox).
+
+From what I see Firefox parses our HTML just fine on the way in, with the entire JSON string being parsed as the attribute value. Do you actually see a parsing difference on the way in resulting in a different DOM?
+
+Changing the title back, as I am pretty sure this is not a bug on our end.",1366902121,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","The problem appears to be with the output from Parsoid with regard to <ref> tags not being escaped.
+
+To give http://parsoid.wmflabs.org/en/Foobar as an example, in Chrome this looks fine:
+
+<span id=""cite_ref-rfc3092-1-0"" class=""reference"" about=""#mwt5"" typeof=""mw:Object/Ext/Ref"" data-parsoid=""{&quot;src&quot;:&quot;<ref name=\&quot;rfc3092\&quot; />;&quot;,&quot;tsr&quot;:[416,438],&quot;dsr&quot;:[416,438,null,null]}""><a href=""#cite_note-rfc3092-1"" data-parsoid=""{}"">[1]</a></span>
+<meta typeof=""mw:Ext/Ref/Marker"" about=""#mwt5"" group="""" name=""rfc3092"" content="""" skiplinkback=""0"" data-parsoid=""{&quot;tsr&quot;:[416,438],&quot;selfClose&quot;:true,&quot;src&quot;:&quot;&lt;ref name=\&quot;rfc3092\&quot; /&gt;&quot;,&quot;dsr&quot;:[416,438,22,0]}"">
+
+
+... but in Firefox the browser presumably doesn't like the un-escaped ""<ref name=... />"" in the attribute of the <span> and so it does this:
+
+<span id=""cite_ref-rfc3092-1-0"" class=""reference"" about=""#mwt5"" data-parsoid=""{""src"":""<ref name=\""rfc3092\"" />"",""tsr"":[416,438],""dsr"":[416,438,null,null]}"" typeof=""mw:Object/Ext/Ref""></span>
+<meta typeof=""mw:Ext/Ref/Marker"" about=""#mwt5"" group="""" name=""rfc3092"" content="""" skiplinkback=""0"" data-parsoid=""{""tsr"":[416,438],""selfClose"":true,""src"":""<ref name=\""rfc3092\"" />"",""dsr"":[416,438,22,0]}""></meta>
+
+I.e., closing the <span> early and throwing away the contents. Note that the following meta is also fragile as it contains unescaped JSON as well.
+
+The result of this is that <ref name=""…"" /> is wrongly expanded to <ref name=""…"" ></span> and so corrupted on save by Firefox users.",1366898909,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>",Related URL: https://gerrit.wikimedia.org/r/60840 (Gerrit Change Ib6a0cfb880e769f28b42c9fa63ddc1abc75c399d),1366898453,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>",*** Bug 47419 has been marked as a duplicate of this bug. ***,1366391720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"VisualEditor: Re-used refs wrongly expanded to <ref name=""…"" ></span>","This seems to be Firefox specific.  I am seeing this on a lot of pages in Firefox, but not in Chrome.  Gabriel can reproduce as well.",1366388687,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-sipzssmp2cg3ixlpwvsi,task_subcomment,NA
+"[TUX] Cannot confirm outdated translation on ""page"" view","Screenshot of the problem
+
+On the ""page"" view, when an outdated translation is opened, the editor shows a disabled ""save translation"" as the main action.
+
+It should show an enabled ""Confirm translation"" button instead (as it is the case for the ""list"" view).
+
+I found the bug on outdated translations at https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-visualeditor&language=ca&filter=&action=page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10395}",1366356360,PHID-USER-c47vnc2yxmwfvvc4367q,True,PHID-TASK-4ifg7mkk6tb64fjj6xsp,task_description,resolved
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,"Ordinarily there's an accesskey (e.g. alt+shift+E in Firefox) on the ""Edit"" tab in Vector. The accesskey is made known to the user through a tooltip. VisualEditor eliminates this accesskey and tooltip, and adds a new ""Edit source"" tab without an accesskey or tooltip. 
+
+Ideally both the ""Edit"" and ""Edit source"" tab should have accesskeys and tooltips to allow quick switching between the modes for power users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366355400,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-app5etuemqiwaqysxa3i,task_description,resolved
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,Code is now merged and will go out on Thursday.,1366745664,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-app5etuemqiwaqysxa3i,task_subcomment,NA
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,"Change-Id: If598552fac639da645a8b1273c5fc6028695fcc1
+
+> @@ -777,10 +778,10 @@ ve.init.mw.ViewPageTarget.prototype.setupSkinTabs
+>  			this.veEditUri,
+> -			$caEdit.text(),
+> +			$caEditA.text(),
+>  			$caEdit.attr( 'id' ),
+> -			$caEdit.attr( 'title' ),
+> -			$caEdit.attr( 'accesskey' ),
+> +			$caEditA.attr( 'title' ),
+> +			$caEditA.attr( 'accesskey' ),
+>  			caVeEditSource
+>  		);
+>  	}",1366618061,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-app5etuemqiwaqysxa3i,task_subcomment,NA
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,Related URL: https://gerrit.wikimedia.org/r/60241 (Gerrit Change If598552fac639da645a8b1273c5fc6028695fcc1),1366617728,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-app5etuemqiwaqysxa3i,task_subcomment,NA
+[Regression] VisualEditor: Edit tab should have tooltip and accesskey,"When mw.ViewPageTarget has its tabLayout in ""replace"" mode (where it replaces the regular Edit tab with a VE-version and adds an Edit source tab) the code explicitly copies over the label, tooltip and accesskey.
+
+It appears this isn't working anymore. I worked a week ago. The code hasn't changed so it looks like something else has broken it.
+
+Moving bug to Integration (perhaps the component should be renamed to ""MediaWiki integration"")",1366362135,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-app5etuemqiwaqysxa3i,task_subcomment,NA
+VisualEditor: Double-click to overwrrite is broken,"1. Open http://ve-change-marking.instance-proxy.wmflabs.org/wiki/Test
+2. Double-click a word and type a single-char
+   (you see that the selected word continues to show in the interface after the char you typed)
+3. Look at review-and-save.
+4. The word has actually been deleted => the interface is not updated as it should
+
+(4) causes the user (=me in this case) to repeatedly try and delete that word and is instead deleting newer words which will all show up in the diff without realizing that they are being deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366326300,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-qwln7sdc2jjjjhdroshx,task_description,resolved
+VisualEditor: Double-click to overwrrite is broken,Inez fixed this.  Possibly https://gerrit.wikimedia.org/r/#/c/59965/,1366340774,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-qwln7sdc2jjjjhdroshx,task_subcomment,NA
+VisualEditor: Double-click to overwrrite is broken,What browser/version are you using? I cannot reproduce in Chrome/Mac or Firefox/Mac - see http://ve-change-marking.instance-proxy.wmflabs.org/srv/mediawiki/index.php?title=Test&diff=45&oldid=44 for a successful run. (Or maybe the code got fixed between the report and my looking at it?),1366331132,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qwln7sdc2jjjjhdroshx,task_subcomment,NA
+VisualEditor: Round-tripping failure - Extra newline added at end of body,"When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366312920,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-akpipntp36njlfgkew56,task_description,resolved
+VisualEditor: Round-tripping failure - Extra newline added at end of body,"(In reply to comment #3)
+> This might be fixed by bug 48344.
+It most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine). Closing this bug unless and until someone can get a newline to show up again.",1368557767,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-akpipntp36njlfgkew56,task_subcomment,NA
+VisualEditor: Round-tripping failure - Extra newline added at end of body,This might be fixed by bug 48344.,1368552325,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-akpipntp36njlfgkew56,task_subcomment,NA
+VisualEditor: Round-tripping failure - Extra newline added at end of body,"Eh, disregard that link- belongs to bug 47419.",1366388820,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-akpipntp36njlfgkew56,task_subcomment,NA
+VisualEditor: Round-tripping failure - Extra newline added at end of body,Example edit: https://en.wikipedia.org/w/index.php?title=User:Fluffernutter/Kinne&curid=37842561&diff=551148728&oldid=551148307,1366388778,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-akpipntp36njlfgkew56,task_subcomment,NA
+VisualEditor: Lazy-update SurfaceFragment,"For performance reasons, we should lazy-update SurfaceFragments rather than updating them through a transact event handler.
+
+The performance problem occurs when you create a bunch of fragments, then throw them away. The fragments are never actually destroyed, if only because the surface still has references to them because of the event binding. The discarded fragments continue to receive events about transactions and update themselves in response, but no one is using them any more.
+
+Instead, I propose the following:
+
+* The surface should have an ordered array of [transaction, direction] pairs that tracks everything that has ever been applied. This is not the same as the undo/redo stacks: this particular array is append-only
+* Every SurfaceFragment has a property indicating which transaction (by index in the big array) is the last one that it knows about
+* SurfaceFragments do not listen for transact events
+* Instead, every time getRange() is called, the fragment asks the surface whether there are new transactions (with indices greater than the stored index), and if so it translates its range for them
+** For this to work, all internal uses of this.range need to be changed to this.getRange()
+
+This'll make the fragment lazy-update its range, and we won't spend any time updating fragments that aren't being used.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366245060,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-g5zcpdywgfveewvgyndn,task_description,resolved
+VisualEditor: Lazy-update SurfaceFragment,Now merged.,1366656030,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g5zcpdywgfveewvgyndn,task_subcomment,NA
+VisualEditor: Lazy-update SurfaceFragment,Related URL: https://gerrit.wikimedia.org/r/60256 (Gerrit Change I9e9818da1baa8319a3002f6d74fd1aad6732a8f5),1366630459,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g5zcpdywgfveewvgyndn,task_subcomment,NA
+VisualEditor: Lazy-update SurfaceFragment,Trevor is adding a bunch of .destroy() calls to SurfaceFragment uses to mitigate the problem. These should be removed once this is implemented.,1366245134,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-g5zcpdywgfveewvgyndn,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"In advance of fixing bug 47328 (which will probably be after the July release), we need to prevent the broken behaviour outlined by C. Scott in bug 47328 comment 1 - so just refuse to load on a page which is a redirect?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47328",1366224540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yop2zgg7fofkoppm6y4x,task_description,resolved
+VisualEditor: Refuse to load for pages which are redirects,Merged; will go out with wmf5.,1368884901,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,Related URL: https://gerrit.wikimedia.org/r/64275 (Gerrit Change I68836156c35c796aa2156c382992b0c105ae34cf),1368789913,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"(In reply to comment #3)
+> It seems like it would be trivial to check whether the page is a redirect and
+> simply disable VisualEditor if so. I'm adding the ""easy"" keyword to this bug.
+
+It gets a bit trickier if the page does not yet exist, though.",1368665165,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"It seems like it would be trivial to check whether the page is a redirect and simply disable VisualEditor if so. I'm adding the ""easy"" keyword to this bug.",1368574217,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"(In reply to comment #1)
+> For me, if you tried to edit a redirect page, it loads with the redirected
+> page.
+
+Yes, this is current behaviour from Parsoid that will be fixed by fixing bug 47328, but that will leave users with a very confusing blank page. That is why I made this bug. :-)",1366384860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+VisualEditor: Refuse to load for pages which are redirects,"**dayuloli** wrote:
+
+For me, if you tried to edit a redirect page, it loads with the redirected page.",1366371378,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-yop2zgg7fofkoppm6y4x,task_subcomment,NA
+"VisualEditor: Fix ""Report problem"" button, broken by IVStore change","In ve.init.mw.Target.prototype.reportProblem, we pass an HTMLDocument to getDataFromDom(), but this function now takes two parameters, with the IVStore coming first, so it fatals with ""doc is undefined"".
+
+In addition to passing in a store, we'll also need to expand the returned data before transmitting it, per bug 47318.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366215060,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-66lb2jf7kuruqajpygry,task_description,resolved
+"VisualEditor: Fix ""Report problem"" button, broken by IVStore change",This is now merged.,1366652317,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-66lb2jf7kuruqajpygry,task_subcomment,NA
+"VisualEditor: Fix ""Report problem"" button, broken by IVStore change",Related URL: https://gerrit.wikimedia.org/r/59642 (Gerrit Change I761523d22e51ac560e37ae991d01a6b84224ca40),1366216629,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-66lb2jf7kuruqajpygry,task_subcomment,NA
+VisualEditor: Provide a way to expand data using an IVStore for transmission over the wire,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366214880,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-u4ghwr7nh5cniopiuid3,task_description,resolved
+VisualEditor: Provide a way to expand data using an IVStore for transmission over the wire,Related URL: https://gerrit.wikimedia.org/r/60925 (Gerrit Change I4819cf06d1bd0ae4f8b896052e278ca75c9551bf),1366925797,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u4ghwr7nh5cniopiuid3,task_subcomment,NA
+VisualEditor: html/* attributes shouldn't be cloned when cloning elements,"We're cloning html/data-parsoid which Subbu tells me messes with selser correctness
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366155600,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-p6hdrbkwl7jmyhc7wdyj,task_description,resolved
+VisualEditor: html/* attributes shouldn't be cloned when cloning elements,This is now merged.,1366652364,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p6hdrbkwl7jmyhc7wdyj,task_subcomment,NA
+VisualEditor: html/* attributes shouldn't be cloned when cloning elements,Related URL: https://gerrit.wikimedia.org/r/59836 (Gerrit Change I428becf95c70d0ed8af5b0c408e3966dc47fd8c3),1366300913,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p6hdrbkwl7jmyhc7wdyj,task_subcomment,NA
+VisualEditor: html/* attributes shouldn't be cloned when cloning elements,"Roan clarified on IRC that this is not happening right now, but about and typeof attributes should not be cloned either. Just adding here to track info. in one place.",1366155988,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-p6hdrbkwl7jmyhc7wdyj,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"To give an example:
+mediawiki.page.ready.js runs on mobile (it specifies targets=>mobile) however attempts to lazy load the tablesorter plugin which is not available on mobile (it specifies targets=>desktop)
+
+This currently throws an exception.
+
+Avoiding a bike shedding conversation about whether jquery.tablesorter should be available on mobile, it is wrong to make the assumption that a module will always be available.
+
+Expected: Instead of seeing an exception I would like to allow the user to handle the error themselves - allowing optional modules to die silently.
+
+e.g.
+mw.loader.using( 'jquery.tablesorter', function () {
+	$sortableTables.tablesorter();
+}, function( e ) {
+throw e;
+});
+
+or 
+mw.loader.using( 'jquery.tablesorter' ).done( function () {
+	$sortableTables.tablesorter();
+});
+
+Another example of this being a problem is on the edit page which asumes mediawiki.action.edit is available:
+
+mw.loader.using(""mediawiki.action.edit""
+
+Currently there is a hack in MobileFrontend to get around this [1]
+
+
+[1] https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/MobileFrontend.git;a=blob;f=includes/skins/SkinMobile.php;h=27ab4ef44fc138566bbf3e1ab32cd5af20daf246;hb=HEAD#l241
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal",1366152300,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_description,declined
+mw.loader.using should not throw an exception when an optional module doesn't exist,"I'll tentatively close this, then, to have less stuff seemingly blocking the release.",1383254422,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"I am happy for someone to agree with Krinle and close this as WONTFIX
+The mobile skin doesn't load mediawiki.page.ready now since we introduced Skin::getDefaultModules so the original problem isn't a problem.
+
+If someone really wants to load something optionally they can use a try / catch",1383252679,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"Is this blocking the release, and if yes, why has nobody done anything about it? I sympathise with Krinkle's comment 7.",1383248523,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"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.",1380208136,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"This is now less of a problem in mobile as we have reduced the possibility of this happening to only situations where a module has been renamed/typed incorrectly/ is not available due to being in mobile mode rather than desktop. The tablesorter exception is no longer called.
+
+My main worry about this is that since ResourceLoader concatenates code one module failing can prevent the execution of another module. This seems wrong. I can understand an entire module from throwing an exception and not executing but stopping all javascript from executing seems wrong.
+
+I really don't understand the need for an exception under all circumstances. Could we not default the error handler to throwing an exception to at least allow developers to override it. For example a gadget might want to do something with a module if it's available but fail silently if it's not so it can be used on as many wiki's as possible that may or may not have the module it does something with)
+
+// module 1
+mw.loader.using( 'foobar', function() {
+} );
+
+// module 2
+(function(){ alert( 4 ); })()
+
+On a similar subject it would be great to see mw.loader.using return a jQuery.deferred object.",1370024390,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,See bug 47882 to discuss my side note about mediawiki.page.ready - please leave discussion on this bug simply about behaviour for when a module doesn't exist.,1367334019,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"jQuery.tablesorter seems to be an optional dependency - the code is loaded in the client only on pages which need it (otherwise the 'mediawiki.page.ready' resource loader module would specify it as a hard dependency in its dependencies)
+
+If jquery.tablesorter was listed in the module manifest [1] for mediawiki.page.ready I could understand it throwing an exception when mediawiki.page.ready uses it - but it is /NOT/ thus the code in mediawiki.page.ready is making a bad assumption that that module exists and is available. In this case it is an optional module (otherwise it would be in the module manifest of a module that /has/ been knowingly added to the page) and the page will survive without it. I am sure however in other cases an exception might make more sense e.g. mw.using( 'mediawiki.modulethatwasrenamed' ). I don't know the resource loader code well enough but it seems it would be useful to distinguish between modules that do not exist and modules that have the wrong target.
+
+On a side note mediawiki.page.ready doesn't look very useful to mobile - input placeholders are not really a problem on modern mobile browsers, we don't use the collapsible code, as this bug reveals the tablesorter isn't expected to work, access keys are useless on mobile and CheckboxShiftClick - I have no idea what that is but doesn't sound very mobile friendly. For our particular problem we should probably simply disable this module on the mobile site - yet it seems to be needed for qunit (wtf)?! [2]
+
+[1]
+'mediawiki.page.ready' => array(
+		'scripts' => 'resources/mediawiki.page/mediawiki.page.ready.js',
+		'dependencies' => array(
+			'jquery.checkboxShiftClick',
+			'jquery.makeCollapsible',
+			'jquery.placeholder',
+			'jquery.mw-jump',
+			'mediawiki.util',
+		),
+		'targets' => array( 'desktop', 'mobile' ),
+	),
+
+
+Krinkle I disagree that we should enable jquery.tablesorter on mobile and we certainly shouldn't do it 'simply' - but that's another bug/discussion (see my comments on bug 47858) - let's not discuss that here.
+
+
+[2] Change-Id: I84e0512590de9ff2dbdf519d983a0c1c2d007194",1367333875,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"For the curious, you can find the problematic behavior exemplified on:
+https://en.m.wikipedia.org/wiki/Wikipedia:Sortable_table",1367281374,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"**jgonera** wrote:
+
+Krinkle, I agree. If we deprecate the error callback, then throwing an error is OK. But let's make it consistent.
+
+Also, Jon, this particular mediawiki.action.edit case will become less important to us because we can, and hopefully soon will, provide our own custom edit form, instead of the one generated by EditPage.php.",1367280531,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"(In reply to comment #5)
+> That change should go out during next Tuesday's regular deployment
+
+For the deployment I think it is more feasible to simply enable jquery.tablesorter on mobile. We can decide whether to surpress error reporting on missing dependencies later.",1367280280,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"I'm not convinced that this should be solved by suppressing the exception and turning it into an optional callback.
+
+When a dependency is specified in the module manifest that doesn't exist[1], we throw. This is currently the case and (afaik) acceptable behaviour because it is a fatal problem. The code must not be attempted to run without that other module.
+
+When a dependency is specified inline at runtime (wrapping the code in a function) which doesn't exist, we throw. I don't see why that would be any different.
+
+Yes, mw.loader.using has an error callback. But aside from this being almost never used (I haven't seen it in use, ever), it is unlikely that an implementation would be anything other than throwing an error. The module ought to be there.
+
+When a module is added to the page by an extension or by core, it is with the intention to make something happen on that page. If that module is unable to load its code, that should throw.
+
+ext.wikiLove.init, ext.articleFeedback.init, VisualEditor, mediawiki.page.ready. All of these load modules after a check or event. They should not be loaded on the page if their dependencies are not available, and loading it anyway should throw.
+
+I'd recommend: Look at this error and fix it.
+
+In this case it means a module is loaded on mobile but one of its dependencies is not yet compatible with mobile. That means it (=jquery.tablesorter) should either be made compatible, or the containing module removed from mobile for the mean while (=mediawiki.page.ready). This isn't my own idea, I've seen this happen before with various other modules and I'm merely suggesting we act the same.
+
+This error is good, because without it you wouldn't have known that we made a mistake and forgot one of the dependencies of mediawiki.page.ready when you enabled it on mobile. This is how we found them before as well, except before they were server-side dependencies and now they're inline.
+
+
+Having said that, I'd like a view from Roan and/or Trevor on this as well. Personally I'd like to keep this exception and instead deprecate the error callback.
+
+
+[1] Exist as in, in the current execution. Because since the 'target' property was created a module can exist in general, but be invisible to the current request context based on the 'target' parameter, thus making any errors related to it somewhat ambiguous (not visible in this target vs. module not existing in general - very different problems).",1367280136,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,Re-opening. Please don't mark bug fixed until they are approved and landed in master.,1367278982,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,That change should go out during next Tuesday's regular deployment,1367012844,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,Related URL: https://gerrit.wikimedia.org/r/60346 (Gerrit Change Ic2f81b725acac2086178e33033f10c4c80ae1573),1366670776,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"Well it's more a historic problem. If a module has been added via out->addModules previously requesting a module vs mw.loader.using was unlikely to throw an exception.
+
+Now with the targets property this becomes more muddled.. a module may or may not be there - it's at the mercy of the current target.
+
+My suggestion is to alter the implementation mw.loader.using so instead of throwing an error it accepts an error callback or even better is rewritten to return a deferred object.
+
+It should be up to the developer to throw an exception.",1366352302,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"**jgonera** wrote:
+
+So what is the problem exactly? How the proposed solutions fix it? Why wouldn't the developer do:
+
+try {
+    mw.loader.using( ...
+} catch ( e ) {
+    ...
+}",1366328222,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+mw.loader.using should not throw an exception when an optional module doesn't exist,"""allow the user to handle the error themselves"" should read ""allow the developer to handle the error themselves""",1366152465,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-foy2pwxdiqiuemtnxzak,task_subcomment,NA
+VisualEditor: ve.getHash custom hashes are double-hashed,"Our current setup for custom hashing objects to to give them a method .getHash() which looks like this:
+
+T.prototype.getHash = function () {
+  var someSubsetOfT = // code here
+  return ve.getHash( someSubsetOfT );
+}
+
+and to invoke we use
+
+ ve.getHash( instanceOfT );
+
+However ve.getHash( instanceOfT ) === ve.getHash( ve.getHash( someSubsetOfT ) )
+which isn't really what we want.
+
+One solution would be to rename getHash to getHashableObject (or something) and have it return just someSubsetOfT directly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1365087000,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-kdifvxztyisvsjamslc7,task_description,resolved
+VisualEditor: ve.getHash custom hashes are double-hashed,"Reopened for 58241, but now that is done am closing again.",1365506219,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-kdifvxztyisvsjamslc7,task_subcomment,NA
+VisualEditor: ve.getHash custom hashes are double-hashed,"Ed, did you re-open because there's more to do, or because Jenkins dying meant the changes weren't merged? :-)",1365469450,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kdifvxztyisvsjamslc7,task_subcomment,NA
+VisualEditor: ve.getHash custom hashes are double-hashed,Related URL: https://gerrit.wikimedia.org/r/58241 (Gerrit Change I6a9b42facd97fbf49042d3a082121ec93659b9f1),1365463023,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kdifvxztyisvsjamslc7,task_subcomment,NA
+VisualEditor: ve.getHash custom hashes are double-hashed,Related URL: https://gerrit.wikimedia.org/r/58235 (Gerrit Change If11071d4b04a01e25102ffb57240882f650ee10d),1365460226,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kdifvxztyisvsjamslc7,task_subcomment,NA
+VisualEditor: Inserting two paragraphs inside another paragraph results in the original paragraphs being separated by a blank paragraph,"e.g. inserting <p>c</p><p>d</p> into <p>ab</p> between a and b results in
+
+<p>a</p><p>c</p><p></p><p>d</p><p>b</p>
+
+This is because fixUpInsertion fixes c & d separately and after inserting c (by closing out a) it decides to re-open the paragraph it closed (sensible), but the d comes along as splits that new paragraph (not sensible), resulting in a blank paragraph between the two.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364923620,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yqzsqc62wfjcfr3spvjk,task_description,resolved
+VisualEditor: Inserting two paragraphs inside another paragraph results in the original paragraphs being separated by a blank paragraph,NB: this bug is not restricted to paragraphs,1364923756,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yqzsqc62wfjcfr3spvjk,task_subcomment,NA
+VisualEditor: Inserting two paragraphs inside another paragraph results in the original paragraphs being separated by a blank paragraph,https://gerrit.wikimedia.org/r/#/c/55791/,1364923669,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yqzsqc62wfjcfr3spvjk,task_subcomment,NA
+VisualEditor: Inserting content at start/end of paragraph leaves leading/trailing empty paragraph,"e.g. inserting a <p>Bar</p> into <p>Foo</p> after the last 'o' results in:
+
+<p>Foo</p><p>Bar</p><p></p>
+
+The original paragraph is split, then the Bar is inserted, then the paragraph is reopened again.
+
+Or in transaction terms:
+
+insert: '<p>Bar</p>'
+
+coverts to
+
+insert: </p><p>Bar</p><p>'
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364923440,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-oohwmpwpyrfuvog4u4ox,task_description,resolved
+VisualEditor: Inserting content at start/end of paragraph leaves leading/trailing empty paragraph,Gerrit 61048 is now merged; marking as fixed - will go out in Monday's deploy train.,1367020450,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oohwmpwpyrfuvog4u4ox,task_subcomment,NA
+VisualEditor: Inserting content at start/end of paragraph leaves leading/trailing empty paragraph,For some reason the bug isn't reporting this: https://gerrit.wikimedia.org/r/#/c/61048/ addresses this and is waiting for jenkins-bot to merge it.,1367016710,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-oohwmpwpyrfuvog4u4ox,task_subcomment,NA
+"VisualEditor: Store rendered html of MW aliens in index-value store, hashed on parameters","This is in preparation for performing transactions on templates and having to update the html asynchronously.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364316180,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pxkrw7ecjvb7q433anxa,task_description,resolved
+"VisualEditor: Store rendered html of MW aliens in index-value store, hashed on parameters",This has been done in https://gerrit.wikimedia.org/r/#/c/57326/,1366130654,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pxkrw7ecjvb7q433anxa,task_subcomment,NA
+VisualEditor: Create meta item for defaultsort,"If Parsoid has a meta thing for defaultsort that is
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363989120,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4o3l42xhur3szmao22jr,task_description,resolved
+VisualEditor: Create meta item for defaultsort,This is now merged.,1367275094,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4o3l42xhur3szmao22jr,task_subcomment,NA
+VisualEditor: Create meta item for defaultsort,Related URL: https://gerrit.wikimedia.org/r/61374 (Gerrit Change I604a79c25e5b0315f7e6437da657977b0efa77db),1367246090,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4o3l42xhur3szmao22jr,task_subcomment,NA
+VisualEditor: Create meta item for defaultsort,"Now defined as:
+
+  {{DEFAULTSORT:foo}}
+
+->
+
+  <meta property=""mw:PageProp/categorydefaultsort"" content=""foo"">
+
+From https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Category_default_sort_key
+
+[Parsoid does not yet support editing of these items.]",1366665947,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4o3l42xhur3szmao22jr,task_subcomment,NA
+VisualEditor: Over-eager link inspector suggestion tool inhibits linking,"I am just trying at w:en:Vojníkov hyperlink from ""Louka"" to ""Louka (village)"". The actual link is incorrect. Using VisualEditor and FF 19.0 or G Chrome 25.0.1364.152 m. If I start to type ""Louka"" it adds ""Loukas Vyntra"" automaticaly. If I use backspace it allows me to delete ""Vyntra"" and when I delete ""s"" of ""Loukas"", it adds again ""Loukas Vyntra"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362608460,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-xbcm5bbrtpu22jkr7ofg,task_description,resolved
+VisualEditor: Over-eager link inspector suggestion tool inhibits linking,Confirming that this is now fixed. Sorry for the delay in responding.,1367548440,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xbcm5bbrtpu22jkr7ofg,task_subcomment,NA
+VisualEditor: Over-eager link inspector suggestion tool inhibits linking,Thanks for the report; this is a known issue - I think we've fixed it but it's not yet pushed to live - throwing to Trevor to confirm.,1362617782,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xbcm5bbrtpu22jkr7ofg,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,"VisualEditor should be deployed to the Hebrew Wikipedia as soon as possible. I did some basic testing on my machine, and I see that it's more or less as functional as it is on the English - basic formatting works, and even basic RTL is correct.
+
+Obviously, there are many RTL issues to test there. I am doing such testing myself every now and then, but letting more people test will be far more beneficial.
+
+Of course, I am talking about a dark launch at this point - it should only be available to users who specifically request it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1362513780,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-p6aosiypctjfd3m7mled,task_description,resolved
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,"\ס/
+
+Thank you!",1366913248,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,This is now deployed to hewiki (and 13 others).,1366909636,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,Related URL: https://gerrit.wikimedia.org/r/60293 (Gerrit Change Ic9ee32df65ee9d885bf19a1592e1e8e3a8d54db0),1366652184,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,This is now scheduled for 2013-04-25.,1366396701,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,"This is very high priority for us (for hewiki and all the others of course), but as Roan says it's blocking on a version of Parsoid that we can deploy that will work with non-English wikis - see bug 43332 for details.",1362520790,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing,"I support this, but I will make one observation. The version of Parsoid that's running in production is fairly old (2012-12-12 or thereabouts), so if there's anything in Parsoid that Hebrew depends on that was added after mid-December, it won't be live yet.
+
+We can't upgrade Parsoid right now because the Parsoid team is rewriting the serializer and master is too broken to deploy right now. We'll probably make a deployment attempt within the next two weeks, but until then, we'll keep running this ancient (but apparently stable, for English at least) version of Parsoid.",1362514401,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-p6aosiypctjfd3m7mled,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"**Author:** `afeldman`
+
+**Description:**
+The FORCE INDEX provided in this query results in a /much/ slower query plan than without.  This is the case with both MySQL 5.1-facebook, and MariaDB 5.5, so it should just be removed.
+
+Query:
+
+SELECT /* IndexPager::buildQueryInfo (contributions page unfiltered) user */  rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,user_name,page_namespace,page_title,page_is_new,page_latest,page_is_redirect,page_len,ts_tags  FROM `revision` FORCE INDEX (user_timestamp) INNER JOIN `page` ON ((page_id = rev_page)) LEFT JOIN `user` ON ((rev_user != 0) AND (user_id = rev_user)) LEFT JOIN `user_groups` ON ((ug_user = rev_user) AND  ug_group = 'bot') LEFT JOIN `tag_summary` ON ((ts_rev_id=rev_id))  WHERE (rev_user >18370655) AND (ug_group IS NULL) AND ((rev_deleted & 4) = 0) AND (rev_timestamp<'20130301192103')  ORDER BY rev_timestamp DESC LIMIT 51;
+
+Times of the query as above:
+
+production enwiki master - mysql 5.1-facebook:  51 rows in set (7 min 23.03 sec) 
+mariadb 5.5.29:  51 rows in set (1.29 sec)
+
+Times with the FORCE INDEX (user_timestamp) removed
+production enwiki master - mysql 5.1-facebook:  51 rows in set (0.26 sec)
+mariadb 5.5.29:  51 rows in set (0.20 sec)
+
+The EXPLAIN without the FORCE INDEX looks worse on 5.1 without than with, based on number of rows examined, but it avoids a filesort.  It looks better without the FORCE INDEX on mariadb than mysql 5.1 with or without.  In both cases, rev_timestamp is used instead of user_timestamp.
+
+--------------------------
+**Version**: 1.21.x
+**Severity**: normal",1362175380,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_description,resolved
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"I think this reappeared, but given the age of this ticket, I will open a new one (probably not related to the original issue anymore).",1520352668,PHID-USER-gzd4fguky5ixnvz46fvu,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,Presumed fixed.,1386216223,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Change 96228 merged by jenkins-bot:
+remove specific FORCE INDEX clauses causing trouble
+
+https://gerrit.wikimedia.org/r/96228",1384883673,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Change 96228 had a related patch set uploaded by Aaron Schulz:
+remove specific FORCE INDEX clauses causing trouble, bug 45619
+
+https://gerrit.wikimedia.org/r/96228",1384883143,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Change 96228 had a related patch set uploaded by Springle:
+remove specific FORCE INDEX clauses causing trouble, bug 45619
+
+https://gerrit.wikimedia.org/r/96228",1384855075,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Not entirely sure why I was CCed on this, but...
+
+Regarding the FORCE INDEX (user_timestamp) in comment 0, that appears to be coming from includes/specials/SpecialContributions.php, ContribsPager::getUserCond() and ContribsPager::getQueryInfo(). git archeology finds that this force index was added way back in 2005, r9796.
+
+Regarding the FORCE INDEX (change_tag_tag_id) in comment 3, that's coming from ChangeTags::modifyDisplayQuery(), added in r49068 with a comment ""fix tag filtering by adding a FORCE INDEX to the relevant queries"". There's also forcing of that index in API modules that do the same sort of thing added in r58399, which refers to bug 22032, which makes it sound like r49068 was fixing some issue where a bad query was bringing down the site. Since I have no idea of the background on that and the problematic queries don't seem to be mentioned in the change summaries, I'm CCing some of the people involved in those revisions.",1378484433,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Found another example of this with a slightly different query form:
+
+SELECT /* IndexPager::buildQueryInfo (contributions page unfiltered) 14.0.143.195 */ rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,user_name,page_namespace,page_title,page_is_new,page_latest,page_is_redirect,page_len,ts_tags FROM `revision` INNER JOIN `page` ON ((page_id = rev_page)) LEFT JOIN `user` ON ((rev_user != 0) AND (user_id = rev_user)) LEFT JOIN `tag_summary` ON ((ts_rev_id=rev_id)) INNER JOIN `change_tag` FORCE INDEX (change_tag_tag_id) ON ((ct_rev_id=rev_id)) WHERE rev_user = '3030741' AND ((rev_deleted & 4) = 0) AND ct_tag = 'visualeditor' ORDER BY rev_timestamp DESC LIMIT 51;
+
+On enwiki, forcing the index hits ~900000 rows with a temp table and filesort. Without the force: ~50000 rows, no temp table or filesort.
+
+Both 5.1 and 5.5 EXPLAIN look the same, so removing this FORCE on change_tag_tag_id would also be a win across the board.",1377847274,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"Bump. These queries forcing user_timestamp are running for 5+ minutes on slaves for several of the bigger WMF wikis.
+
+Multiple identical copies running simultaneously too, presumably when clients assume slow == failure and blindly retry.
+
+Re comment 2: Example would be good. Best to review EXPLAIN output for one forcing usertext_timestamp. It might be a completely different story.",1377745498,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning,"(In reply to comment #0)
+> The EXPLAIN without the FORCE INDEX looks worse on 5.1 without than with,
+> based
+> on number of rows examined, but it avoids a filesort.  It looks better
+> without
+> the FORCE INDEX on mariadb than mysql 5.1 with or without.  In both cases,
+> rev_timestamp is used instead of user_timestamp.
+
+	function getIndexField() {
+		return 'rev_timestamp';
+	}
+
+
+
+There is also code using usertext_timestamp:
+
+			if ( $uid ) {
+				$condition['rev_user'] = $uid;
+				$index = 'user_timestamp';
+			} else {
+				$condition['rev_user_text'] = $this->target;
+				$index = 'usertext_timestamp';
+			}
+
+
+CREATE INDEX /*i*/user_timestamp ON /*_*/revision (rev_user,rev_timestamp);
+CREATE INDEX /*i*/usertext_timestamp ON /*_*/revision (rev_user_text,rev_timestamp);
+
+
+I guess we should remove the force index for that one too?",1362175775,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-3dsaxavgxklzocfpg2pl,task_subcomment,NA
+VisualEditor: 'generated' property should not be preserved when unwrapping,"When we unwrap lists, we currently preserve the internal 'generated' property on paragraphs inside those lists, but we really shouldn't. The fact that we don't currently clear this when unwrapping results in the following serious bug:
+
+1. Create a page with the following content
+Foo
+Bar
+* Baz
+* Quux
+* Whee
+Yay
+2. Open the page in VE
+3. Select across the three list items and click the list button to unlist them
+4. VE now shows five paragraphs
+5. Click ""Review and save"" and observe the diff.
+
+Expected diff: the asterisk and space before ""Baz"", ""Quux"" and ""Whee"" are removed.
+
+Actual diff: the second line becomes ""BarBazQuuxWhee"", followed by three blank lines, then ""Yay"".
+
+This happens because the converter unwraps paragraphs with the 'internal': { 'generated': 'wrapper' } property, even if these paragraphs now appear in a different context and even if there are multiple such paragraphs adjacent to each other.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362090720,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dh3tjq2uz3nbefcu74t6,task_description,resolved
+VisualEditor: 'generated' property should not be preserved when unwrapping,Code now merged.,1363139748,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dh3tjq2uz3nbefcu74t6,task_subcomment,NA
+VisualEditor: 'generated' property should not be preserved when unwrapping,https://gerrit.wikimedia.org/r/#/c/52046/,1362414620,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dh3tjq2uz3nbefcu74t6,task_subcomment,NA
+VisualEditor: You cannot create pre-formatted blocks spanning multiple lines,"1. Create a document ""First line.Second line""
+2. Select this text and insert a newline between the '.' and the 'S' (currently, using the Enter key).
+
+Expected result: a single <pre> block with a single newline after the full stop, converting to "" First line.\n Second line"" in wikitext. Note that this is trivially-obvious on MW Vector due to the ""border: 1px dashed #2f6fab;"".
+
+Actual result: two separated <pre> blocks (with a slug between them), converting to "" First line.\n\n Second line"" in wikitext.
+
+I presume that we'll want to retain Enter as a break-me-out-of-this-context newline, and use Shift-Enter to allow insertion of the above.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361768160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iadcnxx6h6rf3uwphvzc,task_description,resolved
+VisualEditor: You cannot create pre-formatted blocks spanning multiple lines,"**orbit** wrote:
+
+Fixed here: https://gerrit.wikimedia.org/r/#/c/50862/",1361841038,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-iadcnxx6h6rf3uwphvzc,task_subcomment,NA
+VisualEditor: Split out MediaWiki-specific dm stuff into a separate directory,"Stuff like ve.dm.MWInternalLinkAnnotation , ve.dm.modelRegistry.registerExtensionSpecificType( /^mw:/ ), etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1361572320,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3jc7jvjjcdtgrshlnq7r,task_description,resolved
+VisualEditor: Split out MediaWiki-specific dm stuff into a separate directory,Fixed as part of a larger move in https://gerrit.wikimedia.org/r/71755,1372875174,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3jc7jvjjcdtgrshlnq7r,task_subcomment,NA
+VisualEditor: Split out MediaWiki-specific dm stuff into a separate directory,"Roan, is this now closeable?",1367548264,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3jc7jvjjcdtgrshlnq7r,task_subcomment,NA
+VisualEditor: Split out MediaWiki-specific dm stuff into a separate directory,"Some more MW specific nodes:
+https://gerrit.wikimedia.org/r/#/c/51621/",1362185032,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3jc7jvjjcdtgrshlnq7r,task_subcomment,NA
+VisualEditor: Editing in a section causes changes elsewhere to be deleted (Parsoid selser bug?),"Changes made in screen
+
+Issues of editing when making changes in a section of https://en.wikipedia.org/wiki/William_Francis_Magie - probably Parsoid selser issue. JDF to re-check when new Parsoid deployed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10305}",1361474460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lemidsivs6ktavbh7gts,task_description,resolved
+VisualEditor: Editing in a section causes changes elsewhere to be deleted (Parsoid selser bug?),"This is now fixed given the Parsoid update, yay.",1366396637,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lemidsivs6ktavbh7gts,task_subcomment,NA
+VisualEditor: Editing in a section causes changes elsewhere to be deleted (Parsoid selser bug?),"Created attachment 11825
+Diff coming back with only changed area
+
+**Attached**: {F10306}",1361474511,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lemidsivs6ktavbh7gts,task_subcomment,NA
+VisualEditor: Create isolate method in SurfaceFragement,"The method should isolate a selection of siblings from the siblings either side of it by creating close/open tags with either side of it where necessary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361474340,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-zbiughyq34hw6tacnlnj,task_description,resolved
+VisualEditor: Create isolate method in SurfaceFragement,This code was merged.,1363280996,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zbiughyq34hw6tacnlnj,task_subcomment,NA
+VisualEditor: Create isolate method in SurfaceFragement,https://gerrit.wikimedia.org/r/#/c/50199/,1361564493,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-zbiughyq34hw6tacnlnj,task_subcomment,NA
+VisualEditor: Remove all code related to change markers,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1360974360,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-njupimbksvxhw4nnmsfy,task_description,resolved
+VisualEditor: Remove all code related to change markers,This is now merged.,1367527194,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-njupimbksvxhw4nnmsfy,task_subcomment,NA
+VisualEditor: Remove all code related to change markers,Public documentation at http://www.mediawiki.org/wiki/VisualEditor/Change_markers should be deleted or marked as deprecated once this has been merged.,1361228878,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-njupimbksvxhw4nnmsfy,task_subcomment,NA
+VisualEditor: Remove all code related to change markers,https://gerrit.wikimedia.org/r/#/c/49363/,1360975640,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-njupimbksvxhw4nnmsfy,task_subcomment,NA
+VisualEditor: Support transactions on metadata,"In order to implement a category editor, we'll need to be able to process transactions on metadata.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1360890960,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-266a7gondg6gygyomb2r,task_description,resolved
+VisualEditor: Support transactions on metadata,https://gerrit.wikimedia.org/r/#/c/49182/,1360891883,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-266a7gondg6gygyomb2r,task_subcomment,NA
+VisualEditor: Wikitext preview doesn't refresh in new page creation mode,"1. Load a new (i.e. not currently existing) page into VE
+2. Type some text
+3. Click ""Review and save"". The corresponding wikitext appears in a flyout
+4. Close the flyout using the up arrow
+5. Change the text in the editor
+6. Click ""Review and save"" again.
+
+The flyout that appears in #6 will display the same wikitext as in #3, even though you changed the document. The diff flyout handles this correctly (i.e. it caches the old diff until you change something), but the serialization flyout for new page creation never clears its cache.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1360878660,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tqdmz6elwsrngx5orrvl,task_description,resolved
+VisualEditor: Wikitext preview doesn't refresh in new page creation mode,"
+
+*** This bug has been marked as a duplicate of bug 44446 ***",1360878886,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tqdmz6elwsrngx5orrvl,task_subcomment,NA
+VisualEditor: Parsoid selective serialisation failure when deleting an LI (artefact of old version of Parsoid?),"**Author:** `phil`
+
+**Description:**
+shows the result after a save with 'friend' being duplicated
+
+Text was several lines long
+Placed cursor at start of last line
+Pressed delete to move the line up to the same line as the second to last
+Saved
+The last line has not been deleted and it also present on the second to last
+
+Screenshot attached
+This
+is
+the
+end
+my
+friend
+
+- put cursor at start of friend and pressed delete and then added a space
+
+Screenshot shows the result, 'friend' is now in twice
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10875}",1360124400,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jnxq7ir4c6munsrkbn2f,task_description,resolved
+VisualEditor: Parsoid selective serialisation failure when deleting an LI (artefact of old version of Parsoid?),This is now fixed given the Parsoid update. Sorry for the delay.,1366396569,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jnxq7ir4c6munsrkbn2f,task_subcomment,NA
+VisualEditor: Parsoid selective serialisation failure when deleting an LI (artefact of old version of Parsoid?),"Thanks for this, report Phil; I can confirm the issue.
+
+It is probably due to us running quite an old version of Parsoid on the live service; we need to update it to a newer version (which has been delayed for other before I can determine if we still have action to take here).",1360210562,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jnxq7ir4c6munsrkbn2f,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"**Author:** `phil`
+
+**Description:**
+Page after cut and paste of 'a b c' only showing the 'a'
+
+Created a simple file
+a
+b
+c
+
+Copied all the text, placed the cursor after the 'c' and pasted it
+The 'a' from the copy was pasted, the 'b' and 'c' were lost
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10869}",1360122240,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_description,resolved
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),This is now fixed given the Parsoid update. Sorry for the delay.,1366396479,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"Ah, right. This is, I think, a Parsoid-related bug, which should get fixed when the new version of Parsoid can be deployed; assigning to myself for review when we get that out.",1361403605,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"**orbit** wrote:
+
+I think this is a serialization bug. The linear model shows the full data after paste:  
+[
+Object
+, ""a"", 
+Object
+, 
+Object
+, ""b"", 
+Object
+, 
+Object
+, ""c"", ""a"", 
+Object
+, 
+Object
+, ""b"", 
+Object
+, 
+Object
+, ""c"", 
+Object
+]
+but it's not correctly saving. Testing here: http://www.mediawiki.org/wiki/VisualEditor:CopyPaste",1361401270,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"**phil** wrote:
+
+This was Safari/Mac - I have just tried it on Chrome/Mac and was able to reproduce
+
+Just to confirm the steps
+a
+b
+c
+
+Save this - this is 3 separate lines
+Edit
+Copy all the text, paste after the 'c'",1360210696,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?),"Phil, what browser were you using? I'm afraid I cannot reproduce on Chrome/Mac or Safari/Mac; Firefox has wider issues (that mean I can't copy-and-paste anything; to follow-up).",1360210375,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tzp63nj3bg2h6gjxrpwx,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Screenshot
+
+When edited in VisualEditor, the following table:
+
+```
+{| class=""wikitable""
+|- 
+! Header
+|-
+| {{Yes}}
+|}
+```
+... shows the following string in place of the {{Yes}} template:
+
+style=""background: #90ff90; color: black; vertical-align: middle; text-align: center; "" class=""table-yes""|Yes
+
+See screenshot.
+Live at http://en.wikipedia.org/wiki/User:Nicolas1981/Sandbox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50589
+
+**Attached**: {F10493}",1359530280,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_description,resolved
+Template creating CSS in a table's cell does not come through,"Change 76861 abandoned by Subramanya Sastry:
+WIP: first draft of td reparse.
+
+Reason:
+Not required anymore. A DOM-based solution is already merged and in production.
+
+https://gerrit.wikimedia.org/r/76861",1386964245,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,Minor niggle: The caches are not yet cleared as we don't have the rights to do so. Cached pages will only update to the correct rendering after that has happened.,1377187050,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"(In reply to comment #31)
+> (In reply to comment #19)
+> > Scott, is the glitch with the certification tables at
+> > http://en.wikipedia.org/w/index.
+> > php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> > another effect of 50589, this bug, or should I open a new bug report for it?
+> 
+> That was bug 50589, which is now fixed.
+
+Correction: It was very similar to 50589, but not quite the same.
+
+In other news about this bug, https://gerrit.wikimedia.org/r/#/c/79943/ is now deployed, which covers the vast majority of cases including the ones mentioned here. Closing as fixed.",1377186266,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"(In reply to comment #19)
+> Scott, is the glitch with the certification tables at
+> http://en.wikipedia.org/w/index.
+> php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> another effect of 50589, this bug, or should I open a new bug report for it?
+
+That was bug 50589, which is now fixed.",1377035994,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,The DOM handler is now ready for review in https://gerrit.wikimedia.org/r/#/c/79943/.,1377032382,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,I'm working on a DOM-based handler for this. Re-assigning the bug to myself.,1376945009,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Parsoid support for this and a related table parsing issue is tracked in bug 50603, and should be ready in the next weeks.",1375651884,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #26)
+> On the enwiki-20130102-pages-articles-multistream.xml.bz2 dump, there are:
+>  13,057,082 articles, of which
+
+That looks like all namespaces, not just articles.
+
+>  11,877 (0.091%) have some use of [[Template:Table_cell_templates]], and
+>  1,875 (0.014%) have a non-trivial use (ie, the preceding character is not
+> |).
+
+That sounds about right. As a percentage of our most frequently edited articles, I suspect the percentage is much higher, though. The primary use is in award tables, and while the millions of articles about ghost towns, obscure shellfish, and asteroids tend not to discuss awards, while the ones about modern music, television, and films frequently do.",1375230977,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"On the enwiki-20130102-pages-articles-multistream.xml.bz2 dump, there are:
+ 13,057,082 articles, of which
+ 11,877 (0.091%) have some use of [[Template:Table_cell_templates]], and
+ 1,875 (0.014%) have a non-trivial use (ie, the preceding character is not |).",1375230080,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76861 had a related patch set uploaded by Cscott:
+WIP: first draft of td reparse.
+
+https://gerrit.wikimedia.org/r/76861",1375228678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #23)
+> (In reply to comment #22)
+> > (In reply to comment #19)
+> > > Scott, is the glitch with the certification tables at
+> > > http://en.wikipedia.org/w/index.
+> > > php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> > > another effect of 50589, this bug, or should I open a new bug report for it?
+> > 
+> > No, this is bug 52254 (which Roan already opened based on your report).
+> 
+> 52254 is relative to the incorrect italicization and bolding in the lead. It
+> does not cover the corrupted certification table (near the bottom), which is
+> another case of a template creating table markup which is displayed
+> incorrectly.
+
+Opened https://bugzilla.wikimedia.org/show_bug.cgi?id=52296 
+
+The more I play with it, the more it feels like a third related bug. It's clearly not 50589 because Parsoid can't parse it correctly, but I don't think it's a duplicate of this one, either.",1375219011,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #22)
+> (In reply to comment #19)
+> > Scott, is the glitch with the certification tables at
+> > http://en.wikipedia.org/w/index.
+> > php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> > another effect of 50589, this bug, or should I open a new bug report for it?
+> 
+> No, this is bug 52254 (which Roan already opened based on your report).
+
+52254 is relative to the incorrect italicization and bolding in the lead. It does not cover the corrupted certification table (near the bottom), which is another case of a template creating table markup which is displayed incorrectly.",1375213651,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"(In reply to comment #19)
+> Scott, is the glitch with the certification tables at
+> http://en.wikipedia.org/w/index.
+> php?title=Metallica_%28album%29&oldid=566196578&veaction=edit
+> another effect of 50589, this bug, or should I open a new bug report for it?
+
+No, this is bug 52254 (which Roan already opened based on your report).",1375212812,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76758 merged by jenkins-bot:
+Add new parserTests for table cell attributes coming from templates.
+
+https://gerrit.wikimedia.org/r/76758",1375212224,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76758 had a related patch set uploaded by Cscott:
+Add new parserTests for table cell attributes coming from templates.
+
+https://gerrit.wikimedia.org/r/76758",1375211044,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+Scott, is the glitch with the certification tables at http://en.wikipedia.org/w/index.php?title=Metallica_%28album%29&oldid=566196578&veaction=edit another effect of 50589, this bug, or should I open a new bug report for it?",1375200034,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,rewritten in a more-or-less straightforward manner.,1375196456,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Having looked into it a bit, I agree that the current bug is related to bug 50589.  However, bug 50589 *should* work -- the template is still well structured, it is just generating content for more than one table cell.  This bug, on the other hand, has a template which spans structural boundaries in the HTML.  For example:
+
+{|
+|align=center {{table_attribs}}
+|}
+
+where {{table_attribs}} expands to 'style=""color: red""|Foo'.  This wants to generate something like the following HTML:
+<table><tr>
+<td align=""center"" style=""color: red""> Foo
+</td></tr></table>
+
+Note that the <td> and some of its attributes come from the article text, and the rest of the attributes come from the template. I might be able to hack this through Parsoid, but VE will probably never be able to edit the result.  (Imagine how you'd present the table cell editing UI for something like this.) So the bot approach should probably be used to clean up constructs like these, to something like:
+
+{|
+{{table_attribs|align=center}}
+|}
+
+Now the template is well-structured in the resulting html.
+
+My current approach is to attempt to get these cases parsed by parsoid, resulting in uneditable-but-visually-correct output.  We will still want a bot to rewrite the templates so to make them editable in the articles using them.
+
+As MZMcBridge correctly guessed, I'm currently running a grep over an enwiki dump to figure out exactly how many articles use table cell templates.  It's not done running yet so I don't have exact statistics, but the short answer is, ""a lot"".  So far nothing that can't be",1375196416,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #15)
+> (In reply to comment #12)
+> > Bots that modify existing articles to bypass bugs in Parsoid should be off
+> > the table as a solution.
+> 
+> [[Hard cases make bad law]]. :-)
+> 
+> As a general rule, Parsoid should be handle wikitext in the wild. However, we
+> need more information about the prevalence of these constructs on Wikimedia
+> wikis and the amount of work required to properly handle them before we can
+> make any real decisions here. Scott's Gerrit change #76626 seems to be a step
+> in the right direction.
+
+I'm more an adherent to the concept that rigorous adherence to fundamental principles always pays off in the long run, and ""Parsoid should handle all wikitext currently in existence in English Wikipedia"" strikes me as one of those fundamentals.
+
+I'm concerned by the existence of this one and its interplay with 50589. It appears that Parsoid and VE made some assumptions about how templates, wikimarkup, and tables would interact that aren't true.
+
+Take a look at the certification table in http://en.wikipedia.org/w/index.php?title=Metallica_%28album%29&oldid=566196578&veaction=edit for example. There's something going on in http://en.wikipedia.org/wiki/Template:Certification_Table_Top or http://en.wikipedia.org/wiki/Template:Certification_Table_Entry that's causing more weirdness. I don't know if that's this one, 50589, or yet another related bug.",1375138733,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"(In reply to comment #12)
+> Bots that modify existing articles to bypass bugs in Parsoid should be off
+> the table as a solution.
+
+[[Hard cases make bad law]]. :-)
+
+As a general rule, Parsoid should be handle wikitext in the wild. However, we need more information about the prevalence of these constructs on Wikimedia wikis and the amount of work required to properly handle them before we can make any real decisions here. Scott's Gerrit changeset 76626 seems to be a step in the right direction.",1375134893,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76626 merged by jenkins-bot:
+Add 2 more dumpGrepper patterns to get a handle on bug 44498.
+
+https://gerrit.wikimedia.org/r/76626",1375132104,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Change 76626 had a related patch set uploaded by Cscott:
+Add 2 more dumpGrepper patterns to get a handle on bug 44498.
+
+https://gerrit.wikimedia.org/r/76626",1375131923,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+(In reply to comment #11)
+> We are definitely not trying to make life harder for editors.  We are just
+> trying to figure out the best solution going forward.
+
+The best solution going forward is to repair Parsoid. While I agree that we can do things with wikitext that no sane person would *want* to, there's no way to prevent us from doing so, and VE cannot fail based on things that work fine in the standard editor.
+
+Bots that modify existing articles to bypass bugs in Parsoid should be off the table as a solution.",1375126397,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"We are definitely not trying to make life harder for editors.  We are just trying to figure out the best solution going forward.
+
+Visual editing is a HTML-based operation, and HTML has structural semantics.  Longer-term, it would make for a better and simpler software and editing interface if templates generated entire html elements instead of part of elements (which these templates do).  We are just trying to reconcile wikitext structural information with HTML structural information with a view towards the long-term.
+
+While we definitely welcome participation and support of existing template/bot authors here, we are definitely not planning to offload this job of writing bots or updating pages onto editors.
+
+All that said, resolving this issue might well involve a temporary interim fix and a strategy for a longer-term resolution that moves wikitext and templates towards a more cleaner solution that is more aligned with HTML DOM semantics.",1375125861,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+Why would we change the contents of articles to match something that Parsoid likes instead of repairing Parsoid? 
+
+The specification of Parsoid surely must have included a spec that all templates and wikitext syntax in widespread use in English wikipedia needed to be handled properly. Since Parsoid doesn't meet that requirement, repair Parsoid.",1375124914,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"From an email thread with Subbu & C.Scott:
+
+Subbu writes:
+
+Gabriel and I started discussing this the week before he headed out on vacation ... we'll continue once he is back ... we might either have to hack or use other tricks to support these templates.  A bot pass (https://bugzilla.wikimedia.org/show_bug.cgi?id=50547) is one idea we've considered (first fix up the templates, and then use a bot to go and fix pages that use the templates).
+
+---
+I asked:
+
+If we wanted to improve the markup of these templates so they can be more sanely parsed, what instructions would we provide?
+
+---
+Subbu responds:
+
+Instead of generating just style attributes of a table cell, make the ""|"" char part of the template.  So, the templates should produce a styled-cell rather than just the cell-style. And, that also means that the pages that use these should not have ""|"" char before the transclusion -- but we may be able to work around by recognizing that pattern (I say that without working through the details).
+
+So, instead of (old wikitext):
+{|
+| {{yes}}
+|}
+
+they would have to code this as:
+{|
+{{yes}}
+|}
+
+Looks like there are quite a few of these here: https://en.wikipedia.org/wiki/Template:Table_cell_templates  I haven't investigated all the various ways these templates are used, but at first pass, I think that approach should fix the problem.
+
+---
+
+C.Scott responds:
+
+It's probably worth bringing the VE team into this discussion.  I
+think that VE would probably struggle trying to edit table cell(s)
+generated with a template containing a style + cell contents in this
+fashion and/or have difficulty processing whatever markup we decide
+Parsoid ""should"" generate for this case.  My intuition is that fixing
+the templates to include the leading vertical bar, so that the
+template is clearly a cell, not part-of-a-cell, is a better long-term
+solution for editing (Parsoid+VE).  It seems like a bot to make this
+change could be implemented + deployed relatively quickly, although I
+haven't actually written a bot before, maybe there are community or
+other factors limiting the speed at which bot edits are made?
+ --scott
+ps. who'd be interested in writing said bot, because he's never done
+that before, although I suspect it would be best farmed off to someone
+who's done this sort of thing before.
+
+And also adds:
+
+Note that there are some anomalous usages, for example:
+
+! {{yes}}
+| rowspan=2 {{n/a}}
+
+The first case would have to be {{yes|type=header}} and the second
+something like {{n/a|rowspan=2}}, both with additional changes to the
+table cell template.  In other words, the issue isn't just that the
+style and cell content boundary is spanned, it's that some of the
+style comes from outside the template and some comes from inside.
+
+I still think a bot might be the best long-term fix, but it's not
+entirely straightforward.  If we were to fix it inside parsoid, we'd
+have to introduce something like an ""open style context"", probably
+buffering the style information and spitting it out only after we've
+seen the style context closed.  It would still be an ""interesting""
+editing challenge in VE -- some of the table style information would
+be editable, some would come from the template (and be editable only
+inside the template editor?).
+ --scott",1375122625,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"Bumping up the importance, per comment 7.",1374874237,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"**kwwilliams** wrote:
+
+This one as well: http://en.wikipedia.org/w/index.php?title=List_of_Big_Time_Rush_episodes&diff=prev&oldid=565906957
+
+This really isn't a ""low importance"" bug by any stretch of the imagination. It affects most discographies, most television episode lists, and most award lists.",1374858786,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,Could aftereffects of this be responsible for the nightmare at https://en.wikipedia.org/w/index.php?title=Bosnia_and_Herzegovina_in_the_Eurovision_Song_Contest&diff=565659865&oldid=565498623 ?,1374704447,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,*** Bug 50366 has been marked as a duplicate of this bug. ***,1374455443,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"There are many templates in this set.
+https://en.wikipedia.org/wiki/Template:Table_cell_templates
+
+And the most commonly used ones are copied to other languages.  See the interwikis for {{Yes}}
+https://en.wikipedia.org/wiki/Template:Yes",1374454995,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,*** Bug 50772 has been marked as a duplicate of this bug. ***,1374454764,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"This will be hard to support, as the nested template produces part of the table cell syntax plus the table cell content. Moving the pipe starting the table cell into the template would avoid this issue as the template would then expand to a self-contained table cell with content.
+
+Are there other templates following this pattern apart from Yes (and probably No)?",1360210956,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+Template creating CSS in a table's cell does not come through,"This is a Parsoid bug; couldn't find the master with which to mark as dupe (sorry, Gabriel!).",1360209226,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jer6pedsydbmctp5xlhb,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"diff about to delete existing text
+
+I've seen this a few times and I think this is the simplest reproduction. 
+
+Start with a page that has a line of text ""this text should be preserved but is not""
+
+In VE, position the cursor at the front of the line and move it two spaces down. 
+
+Move the cursor back to the top of the page. 
+
+Type a new line ""totally different stuff""
+
+Save.  Note the incorrect diff. The string ""this text should be preserved but is not"" has been deleted erroneously upon save.  
+
+Repeat the operation but this time use strings that share words, like ""this text should be preserved"" and ""this text is new""
+
+The behavior is the same, the old text is erroneously deleted, but the diff seems to have intertwined the two strings, keeping their common elements.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Cmcmahon(WMF)&oldid=535559576
+
+**Attached**: {F10454}",1359488700,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_description,resolved
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"This is now fixed given the Parsoid update. Sorry for the delay! (Note that there is a distinct error that this has just thrown up, yayfuntimes.)",1366396947,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11741
+'text should be preserved' is not
+
+real screen shot from real computer, my apologies
+
+**Attached**: {F10457}",1360210415,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11740
+text with string that will be deleted before save
+
+real screen shot from real computer
+
+**Attached**: {F10456}",1360210348,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,This looks to be a Parsoid bug (and is highly dependent on the rest of the page's content); will re-visit when Parsoid is updated before progressing.,1360208728,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"The content of attachment 11709 has been deleted by
+    James Forrester <jforrester@wikimedia.org>
+who provided the following reason:
+
+Not intended to be on Bugzilla?
+
+The token used to delete this attachment was generated at 2013-02-07 03:38:14 UTC.",1360208305,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"The content of attachment 11710 has been deleted by
+    James Forrester <jforrester@wikimedia.org>
+without providing any reason.
+
+The token used to delete this attachment was generated at 2013-02-07 03:36:53 UTC.",1360208263,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"(In reply to comment #2)
+> Created attachment 11709 [details]
+> preview of page before save has correct text
+
+(In reply to comment #3)
+> Created attachment 11710 [details]
+> saved page, existing text deleted erroneously
+Ahm.... these are pictures of deer. Just sayin'.
+
+//attachment 2012-12-30 11.02.48.jpg ignored as obsolete//",1360208240,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11710
+saved page, existing text deleted erroneously
+
+//attachment 2013-01-13 15.01.28.jpg ignored as obsolete//",1359488894,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11709
+preview of page before save has correct text
+
+//attachment 2012-12-30 11.02.48.jpg ignored as obsolete//",1359488849,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Parsoid/aliens combinations causes data to be over-written on save,"Created attachment 11708
+better view of intertwined strings
+
+**Attached**: {F10455}",1359488791,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ok3b6bw3cne4xry4dq2k,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"Go to a new page. Enter some content. Press review-and-save. Observe diff. Press the ""leave this context"" button (""^""). Change the content. Press review-and-save again. Observe diff.
+
+Expectation: The diff shows the changes against the new content.
+Reality: The diff shows the changes against the original content (not re-done).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1359415380,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_description,resolved
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"Code now merged; thanks, Timo! Will go out in next branch.",1368043283,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,Related URL: https://gerrit.wikimedia.org/r/62847 (Gerrit Change I9eddebbdf9294ee3d46286bdf1b157e00252d300),1368037459,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"The comments above are wrong. Actual timeline:
+
+# Page load, enter text
+     ve.Surface/Model/on/transact
+     onSurfaceModelTransact Clear the diff html
+     ve.Surface/Model/on/transact
+(2x) ve.Surface/Model/on/transact
+# Press ""Review and save""
+# Close dialog
+# Enter more text
+(3x) ve.Surface/Model/on/transact
+# Press ""Review and save""
+# Close dialog",1366839502,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"Using the following debug calls:
+
+diff --git a/modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js b/modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js
+index 859d4f8..cee2505 100644
+--- a/modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js
++++ b/modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js
+@@ -390,6 +390,7 @@ ve.init.mw.ViewPageTarget.prototype.onSaveError = function ( jqXHR, status ) {
+  * @param {string} diffHtml
+  */
+ ve.init.mw.ViewPageTarget.prototype.onShowChanges = function ( diffHtml ) {
++       mw.log( 'onShowChanges', 'Invalidate the diff (by calling proxiedOnSurfaceModelTransact) on transact event' );
+        // Invalidate the diff on next change
+        this.surface.getModel().on( 'transact', this.proxiedOnSurfaceModelTransact );
+ 
+@@ -562,6 +563,7 @@ ve.init.mw.ViewPageTarget.prototype.onToolbarFeedbackToolClick = function () {
+  * @param {ve.dm.Transaction} tx Processed transaction
+  */
+ ve.init.mw.ViewPageTarget.prototype.onSurfaceModelTransact = function () {
++       mw.log( 'onSurfaceModelTransact', 'Clear the diff html' );
+        // Clear the diff
+        this.$saveDialog
+                .find( '.ve-init-mw-viewPageTarget-saveDialog-slide-review .ve-init-mw-viewPageTarget-saveDialog-viewer' )
+@@ -691,6 +693,9 @@ ve.init.mw.ViewPageTarget.prototype.setUpSurface = function ( doc ) {
+        this.surface = new ve.Surface( this, doc, this.surfaceOptions );
+        this.surface.getContext().hide();
+        this.$document = this.surface.$.find( '.ve-ce-documentNode' );
++       this.surface.getModel().on( 'transact', function () {
++               mw.log( 've.Surface/Model/on/transact' );
++       } );
+        this.surface.getModel().on( 'transact', this.proxiedOnSurfaceModelTransact );
+        this.surface.getModel().on( 'history', this.proxiedOnSurfaceModelHistory );
+        // Transplant the toolbar
+
+
+I've determined that the ""transact"" event does indeed continue to be emitted. But onSurfaceModelTransact only gets called once. It is not being rebound:
+
+
+ # Page load, enter text
+ ve.Surface/Model/on/transact load.php:11256
+ # Press ""Review and save""
+ onSurfaceModelTransact Clear the diff html load.php:11256
+ # Close dialog
+ # Enter more text
+ ve.Surface/Model/on/transact load.php:11256
+ ve.Surface/Model/on/transact load.php:11256
+ # Press ""Review and save""
+ # Close dialog
+ # Enter more lots more text
+ (14x) ve.Surface/Model/on/transact  load.php:11256",1366839306,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"(In reply to comment #3)
+> (In reply to comment #2)
+> > Which I assume means ve.dm.Surface for some reason didn't emit any - or
+> > mw.ViewPageTarget is binding it wrong, but that looks fine to me.
+> > 
+> > @Roan, any ideas?
+>
+> I'm pretty sure ve.dm.Surface emits the events correctly. You can check this
+> by
+> placing a breakpoint on the line where Surface calls this.emit().
+> 
+> It's possible there's a bug in EventEmitter with detaching and reattaching
+> though.
+
+Hm.. could be. All I know is that the attached callback didn't get fired.",1363989548,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"(In reply to comment #2)
+> Which I assume means ve.dm.Surface for some reason didn't emit any - or
+> mw.ViewPageTarget is binding it wrong, but that looks fine to me.
+> 
+> @Roan, any ideas?
+I'm pretty sure ve.dm.Surface emits the events correctly. You can check this by placing a breakpoint on the line where Surface calls this.emit().
+
+It's possible there's a bug in EventEmitter with detaching and reattaching though.",1363287954,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,"Confirmed and hunt down.
+
+From what I can see the problem may be in ve.dm.Surface not emitting any 'transact' events.
+
+Adding a log() call in ve.init.mw.ViewPageTarget.prototype.onSurfaceModelTransact, shows me the following.
+
+* When entering the first characters on a new page it is called.
+  The callback then properly unbinds itself after the first call.
+* Go to ""Review and save""
+  Now it binds the event again, so that it is notified of the first
+  change (if ever) when the dialog is closed.
+  This happens in ve.init.mw.ViewPageTarget.prototype.onShowChanges
+* Close the dialog
+* Altering the document again
+
+> the method is not called
+
+Which I assume means ve.dm.Surface for some reason didn't emit any - or mw.ViewPageTarget is binding it wrong, but that looks fine to me.
+
+@Roan, any ideas?",1361815269,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted,*** Bug 45021 has been marked as a duplicate of this bug. ***,1360878886,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fvybwsx2pzn3o2pbtxx6,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,"For the forthcoming Template Inspector to work, we will need a way to ""hint"" for the Inspector how the parameters of the VE should be used - we're intending for now for this to be a template-hinting extension that allows editors to specify in the wikitext source what the parameters are called and how they should be used, akin to the Template documentation template on Commons.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1359413640,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_description,resolved
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,"This is now deployed to all wikis. Closing.
+
+(In reply to comment #5)
+> (In reply to comment #4)
+> > We should get this deployed everywhere this coming week.
+> 
+> I'd like see to a working demo of this feature and expanded documentation at
+> [[mw:Extension:TemplateData]] before this is deployed elsewhere.
+
+I've made some quick updates, but you're right, it does need proper documentation.",1369075541,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,"(In reply to comment #4)
+> We should get this deployed everywhere this coming week.
+
+I'd like see to a working demo of this feature and expanded documentation at [[mw:Extension:TemplateData]] before this is deployed elsewhere.",1369069065,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,We should get this deployed everywhere this coming week.,1368767092,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,Live on mw.org and testwiki now.,1367277258,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,I will need to review and deploy this soonish.,1363988695,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector,"Initial code in gerrit 49840 which is now merged.
+
+To come - review, deployment and usage.",1363288858,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nwfeyfjfrxwame6u7ux5,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"empty review pane, should show heading markup for non-Latin string
+
+Using a string like ""āæǣ"" or special characters like ""☺☻♥♦""
+
+Highlight the string in VE
+Choose ""Heading 1""
+
+VE displays the string larger, as expected
+
+Click ""Review and save""""
+
+Note that review pane is empty, see screen shot. 
+Click ""Looks good to me"" and finish saving. 
+
+The non-Latin string has not been affected and the Heading not been applied. 
+
+Note that normal ASCII latin strings work fine. 
+Also note that the regular editor applies the Heading markup to non-latin strings correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Cmcmahon(WMF)&oldid=535414434
+
+**Attached**: {F10377}",1359412320,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-piflhuji3l6moqmh3nbj,task_description,resolved
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"The underlying issue (with Parsoid) has been resolved with the new version of Parsoid finally running on the cluster; marking as FIXED.
+
+[I have forked comment 6 into bug 47436.]",1366414342,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"**guanhao7** wrote:
+
+I found it is impossible to use Sogou Input or other Input software to type Chinese with this tool.
+
+You may download a Sogou Input(which is the most popular one in china, on the Windows） to test it.
+
+Here is the download link: http://download.ime.sogou.com/sogou_pinyin_65f.exe?st=lTJ11fWyCsrUkj6oWiGI_Q&e=1359462829&fn=sogou_pinyin_65f.exe",1359463674,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,This would make a nice automated browser regression test,1359423892,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"OK, interesting. This is actually a quite complicated bug, and is not actually correctly-named.
+
+The problem appears to be the '[http://barbarbar bar]' beforehand - if you remove this, the diff magically ""works"" - BUT it fails to show the '[http://barbarbar bar]' being removed, and indeed puts it after the header too, with another paragraph of 'āæǣ'. The diff is the behaviour that results from the save, even though this isn't a fair representation of the document model (the '[http://barbarbar bar]' is removed from the DM).
+
+RK: this feels like a Parsoid bug (or two?), but might be on our side related to SelSer? - can you confirm before we sling it at them?",1359422565,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,Also repro'd on Chrome/Linux,1359417612,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"
+Chrome, OSX, enwiki. I can reproduce this reliably on my User page on enwiki.",1359417285,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup,"Afraid I can't reproduce this (it works fine for me with Firefox, Safari and Chrome from here - I get as-expected diffs, which also then save appropriately) - what wiki / version of the software was this on, and with what browser?",1359415631,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-piflhuji3l6moqmh3nbj,task_subcomment,NA
+VisualEditor: Handle Parsoid error messages and codes sanely,"VE gets some error codes and messages from Parsoid, but not a lot. I'm expanding that a little bit in a new patch [0], and it would be cool if VE could handle the errors I've added.
+
+401: Unauthorized: Should be handled as a user-visible error. Usually this means that the API isn't readable by anonymous users, but could be later used for something else. The text of the HTTP response has details about the error, so showing that to the user might be an OK solution.
+
+404: Not found: Usually means that we couldn't find anything for the article you're trying to parse or serialize. This shouldn't usually happen, but when it does, it *probably* means that the interwiki isn't set properly. Maybe hint that the user should compare their localsettings.js file to the example.
+
+500: Server error: This is a catch-all, but we'll send as much information as we can in the text of the HTTP response. Showing the user the text would go a long way towards more useful bug reports (I currently see roughly 4 suggested duplicates that have roughly the same summary....differentiating them might be helpful)
+
+These are all implemented in js/lib/mediawiki.ApiRequest.js in functions that inherit from the native Error object, so you can read it if you don't want to take my word for it.
+
+We could implement other error codes as we see cases that require them, but these are the big three. And of course 200 is the main success code.
+
+We might also be able to use some of the 3xx codes to represent redirects, but I'm not sure it would be totally useful. File a bug against Parsoid if it would be :)
+
+[0] https://gerrit.wikimedia.org/r/45794
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43147",1359142560,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-ocokyzlkygrkgdcs4rdx,task_description,resolved
+VisualEditor: Handle Parsoid error messages and codes sanely,"Marking this as done as the code's been committed; we may want to review in future (e.g. i18n of the error messages), but Gabriel has indicated that that entire area of code will be removed anyway, so marking as closed for now.",1362522586,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ocokyzlkygrkgdcs4rdx,task_subcomment,NA
+VisualEditor: Handle Parsoid error messages and codes sanely,"(In reply to comment #1)
+> Code in Gerrit change #52249
+
+This patch passes through the error messages from Parsoid to the existing error alert in VE. Mark's comment talks about providing suggestions based on the error code. Although maybe this could be done by Parsoid.
+
+This change should at least provide users with more specific errors for filing bugs.",1362505236,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ocokyzlkygrkgdcs4rdx,task_subcomment,NA
+VisualEditor: Handle Parsoid error messages and codes sanely,Code in gerrit 52249,1362504750,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ocokyzlkygrkgdcs4rdx,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"See http://inimino.org/~inimino/blog/javascript_cset for some work in this area.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1358469000,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_description,resolved
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"Like this: https://gerrit.wikimedia.org/r/#/c/54480 (well, apart from non-BMP characters...)",1363625285,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"The Unicode standard has a fair amount to say on the matter. Ideally we would implement their standard.
+
+http://www.unicode.org/reports/tr29/#Word_Boundaries",1363433728,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"As an incremental improvement I've expanded the letters and numbers groups to their Unicode categories: https://gerrit.wikimedia.org/r/#/c/53583/
+We still need to think about which punctuation categories to add.",1363195148,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"If you're going to do lexicon-based word boundary detection in Chinese, maybe you could use a word list stored in a client-side Bloom Filter. 
+
+I don't know if it's as much of a problem in Japanese; you could probably use (?<=\P{Han})(?=\p{Han}) as a good start (i.e. there is a word break be.",1363192283,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,To begin with a patch to add some test structure and fix what we have already: https://gerrit.wikimedia.org/r/#/c/53564,1363182596,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,http://xregexp.com/ has unicode character class support. We may be able to pick out the data we need from it instead of using the whole library.,1363178581,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,Acutually Chinese & Japanese don't have any word boundaries at all. The only way to detect them is with a dictionary. We'll need a special case for these languages so we don't end up selecting entire sentences.,1363176312,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries,"Bit of clarification:
+
+When the user clicks the link button in the toolbar and they haven't selected any text, we expand the selection in both directions from the cursor position and select the word the cursor is in, make that a link, then show the link inspector. The code that expands the selection to a full word is in ve.dm.SurfaceFragment, and apparently treats non-ASCII characters as word boundaries. The practical bug that this leads to is that if you put the cursor in the middle of ""Möckernbrücke"" (or ""égalité"", if you prefer French) and click the link button, only ""ckernbr"" (or ""galit"", respectively) will be selected and linkified. Obviously this is a problem for i18n in languages using an extended Latin alphabet like German, French and Polish, but it's a total nightmare for non-Latin languages like Russian, Hebrew and Japanese.",1363054412,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eskw2sna4jhs2lvvjvcw,task_subcomment,NA
+"VisualEditor: Insertion tools (link inspector, media inserter, reference, reference list, …) don't work in slugs","Related to bug 44083
+
+Because there is not yet a paragraph to insert content in, the link inspector won't be able to insert the new link text into a slug, even if bug 44083 is fixed.
+
+The solution is probably to make the automatic paragraph insertion code in ve.ce.Surface.handleInsert more generic and moving it into ve.dm.SurfaceFragment.insertContent, triggered when inserting at a slug location.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44083",1358467500,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-iw27jj4bhfweo22d2lg4,task_description,resolved
+"VisualEditor: Insertion tools (link inspector, media inserter, reference, reference list, …) don't work in slugs",This has now been fixed and deployed.,1372462623,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iw27jj4bhfweo22d2lg4,task_subcomment,NA
+"VisualEditor: Insertion tools (link inspector, media inserter, reference, reference list, …) don't work in slugs",Noting that this is more severe.,1372253678,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iw27jj4bhfweo22d2lg4,task_subcomment,NA
+VisualEditor: Placing the cursor in a slug doesn't cause a contextChange event,"1. Make an article that begins with an alien followed by a paragraph with some text
+2. Click on a word in the paragraph
+3. Click on the slug
+4. Press the link button
+5. See that rather than the link inspector knowing to begin inserting a new link inside the slug, it inspects the word you clicked on in the paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44084
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50141",1358467260,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-6nqkzsnqx67qeicoilm6,task_description,declined
+VisualEditor: Placing the cursor in a slug doesn't cause a contextChange event,Actually closing it.,1383060862,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6nqkzsnqx67qeicoilm6,task_subcomment,NA
+VisualEditor: Placing the cursor in a slug doesn't cause a contextChange event,"Confirming that this is now fixed, and was done so some time ago - back-dating to approximately when I think it was fixed.",1382654223,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6nqkzsnqx67qeicoilm6,task_subcomment,NA
+VisualEditor: Placing the cursor in a slug doesn't cause a contextChange event,"Hm.. I can't reproduce this.
+
+
+1. Opening a MediaWiki page with the following source in VisualEditor:
+
+<<<MW
+<templatedata>{
+    ""params"": {}
+}</templatedata>
+
+Foo bar baz.
+MW;
+
+2. Selecting word ""bar"".
+3. Clicking in the slug area above the green templatedata alien.
+4. Pressing the link button.
+
+Shows a link inspector with an empty input field. Upon entering some text in the link input widget and closing the link editor, the link target page is inserted as plain text (different bug?)",1380747300,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6nqkzsnqx67qeicoilm6,task_subcomment,NA
+"VisualEditor: Key commands should be ""platform-able"".","Key commands should be able to vary based on language/locale and platform. E.g. toggling something as Bold could be:
+
+* Ctrl + b (Windows, English)
+* Cmd  + b (Mac OS X, English)
+* Meta + b (Solaris, English)
+
+* Ctrl + f (Windows, German)
+* Cmd  + f (Mac OS X, German)
+* Meta + f (Solaris, German)
+
+... etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42919",1358279820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-obbqrn6j222whjin4fm6,task_description,resolved
+"VisualEditor: Key commands should be ""platform-able"".","Now merged, will go out in 2013-02-04 release cycle.
+
+Note that the internationalisation aspect (Ctrl+F rather than Ctrl+B for Bold in German) is WONTFIX as directed by the Language Engineering team, who advised against.",1358469781,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-obbqrn6j222whjin4fm6,task_subcomment,NA
+"VisualEditor: Key commands should be ""platform-able"".",Patched in https://gerrit.wikimedia.org/r/#/c/44347/,1358375043,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-obbqrn6j222whjin4fm6,task_subcomment,NA
+VisualEditor: Clean up canHaveGrandchildren mess,"""Can have grandchildren"" is a misnamed check that should be cleaned up. What it really appears to mean is ""is this a non-content-containing branch node"", given that it checks that the node can have children, is not content, and is not a content container.
+
+canHaveGrandchildren seems to still be used in some places, it should be renamed and documented adequately.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1357966200,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xzuyfy5phfxcgoae52f6,task_description,resolved
+VisualEditor: Clean up canHaveGrandchildren mess,https://gerrit.wikimedia.org/r/#/c/53750/,1363266054,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xzuyfy5phfxcgoae52f6,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"We should use pushState such that pressing the back button after clicking VisualEditor takes you back to read mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1357863540,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_description,resolved
+VisualEditor: Browser back button should work as expected,"(In reply to Lokal_Profil from comment #11)
+> (In reply to Andre Klapper from comment #10)
+> > Lokal_Profil: Where? Example link? Browser? Reopening not helpful without
+> > giving instructions to reproduce... :-)
+> 
+> Sorry ;)
+> 
+> Confirmed in both Firefox and Chorme running on Ubuntu
+> 
+> Tested on both sv.wp[1] and en.wp[2] (logged out on sv.wp to make sure no
+> personal settings were affecting it)
+> 
+> [1] https://sv.wikipedia.org/wiki/Bonsai?uselang=en
+> [2] https://en.wikipedia.org/wiki/Bonsai
+
+Moved to bug 63739 as a new regression.",1397067880,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"(In reply to Andre Klapper from comment #10)
+> Lokal_Profil: Where? Example link? Browser? Reopening not helpful without
+> giving instructions to reproduce... :-)
+
+Sorry ;)
+
+Confirmed in both Firefox and Chorme running on Ubuntu
+
+Tested on both sv.wp[1] and en.wp[2] (logged out on sv.wp to make sure no personal settings were affecting it)
+
+[1] https://sv.wikipedia.org/wiki/Bonsai?uselang=en
+[2] https://en.wikipedia.org/wiki/Bonsai",1395932065,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Lokal_Profil: Where? Example link? Browser? Reopening not helpful without giving instructions to reproduce... :-),1395925983,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,This seems to be broken again (back button changes URL but doesn't take user back to read state),1395924522,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Merged and will go out with wmf7 (from tomorrow).,1371042698,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,*** Bug 49336 has been marked as a duplicate of this bug. ***,1370840639,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Related URL: https://gerrit.wikimedia.org/r/67172 (Gerrit Change I5c345c1526852a84b04436955845bf1b56d94402),1370472014,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Related URL: https://gerrit.wikimedia.org/r/67171 (Gerrit Change Ia4b949d9c066a3f7b07217aa3d51de9908734e85),1370472012,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"Setting milestone to 2013-06-27 since it is marked as blocker for ""Beta"" (2013-07). It may be moved to an earlier milestone as we see fit. But no later than 06-27. Setting it since I use milestone to sort ""My bugs"".",1370298472,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"We currently use ?veaction=edit as trigger for VisualEditor from a permanent url.
+
+This is implemented by checking the query parameter on page load and triggering init (just like a click on ""VisualEditor"" would do), and then we replace (without refresh) the url to drop this query parameter using the HTML5 History api (replaceState).
+
+I'd recommend we build on this by using pushState when VisualEditor is initialised (we can then remove the current behaviour as there's no longer any reason to remove it from the url).
+
+Note that it is slightly more complicated than just calling replaceState on init. We also need to listen on('popstate') to move back to read mode if the user presses Back to a url within the history that contains HTML5 history state data from VisualEditor.",1368496708,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,"To further clarify what the issue here is:
+
+* a user visits <https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals>;
+* user clicks ""edit"";
+* VisualEditor form loads;
+* user tries to escape the form by pressing the ""back"" button in his/her browser;
+* browser's ""back"" button doesn't work as expected (it should take the user back to the implicit view action where he/she started).",1368496497,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+VisualEditor: Browser back button should work as expected,Is this an easy bug?,1368496332,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-b2euwwfrbpmnfl2aq75y,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message","When the diff result is null (no changes), don't show a confusing blank diff but instead a message like ""There are no changes detected in your edit"" so that users aren't confused.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1357693440,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_description,resolved
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Merged; re-closing.,1368575229,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Related URL: https://gerrit.wikimedia.org/r/63691 (Gerrit Change I537bcae91f51a3f30ca4736c41f7a5619bbf321d),1368553503,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Re-opening to provide less hacky fix.,1368553470,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Merged into master and will go out in wmf4.,1368311679,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Related URL: https://gerrit.wikimedia.org/r/63236 (Gerrit Change I8daae124b060ccf54ce5ca7c1e1a6d18b7265ade),1368225175,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message",Working on this now.,1366738661,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-tbgpmmiggp5mn7bvnvbe,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,"For whatever reason (may be a bug in the DM, or in the seralizer, or in selser), whitespace preservation didn't work in this edit https://en.wikipedia.org/w/index.php?title=International_Air_Transport_Association_airport_code&diff=530666305&oldid=526301045 . The whitespace changes didn't show in the initial diff I was asked to verify, only in the final change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1356989040,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_description,resolved
+VisualEditor: Whitespace preservation for list items not working,*** Bug 48367 has been marked as a duplicate of this bug. ***,1368379914,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,Merged.,1366206699,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,"(In reply to comment #3)
+> Related URL: https://gerrit.wikimedia.org/r/59570 (Gerrit Change
+> Ic4c93510518163894201a693ab50331413715967)
+
+This commit fixes the bug. CC Gabriel and Subbu because they'd probably like to test it.",1366161752,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,Related URL: https://gerrit.wikimedia.org/r/59570 (Gerrit Change Ic4c93510518163894201a693ab50331413715967),1366161678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,"It looks like this is happening because getDomFromData() somehow messes up the whitespace information. Then when getDomFromData() runs a second time (because you go back, change things, then diff again, or if you save after diffing), it sees inconsistent whitespace information and refuses to serialize it.",1366160823,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: Whitespace preservation for list items not working,"Confirm not happening in live - but /does/ happen with heads of VisualEditor and Parsoid (and MediaWiki) in testing. As Roan says, doesn't appear in diff, does appear in the final change.",1362784369,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jrdnntjfzxsr3v7pxbff,task_subcomment,NA
+VisualEditor: JS TypeError when Parsoid returns an error,"Steps to reproduce issue:
+* Load VisualEditor on a page where the server will return in error
+  (to simulate, call mw.loader.load('ext.visualEditor.viewPageTarget') from the console on a page where VE is not enabled, e.g. the Manual namespace on mw.org)
+* Click Cancel on the server error alert()
+* Witness said error on your console.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355786940,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-i3m3gsgv7zrvvcskhdat,task_description,resolved
+VisualEditor: JS TypeError when Parsoid returns an error,"Now fixed - you get the message: ""Error loading data from server: novenamespace: VisualEditor is not enabled in namespace 100. Would you like to retry?""
+
+Arguably the option to retry should be skipped, but marking this as now fixed.
+
+J.",1364318463,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i3m3gsgv7zrvvcskhdat,task_subcomment,NA
+VisualEditor: JS TypeError when Parsoid returns an error,"**Coiby.Xu** wrote:
+
+I meet this problem, too",1358937264,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-i3m3gsgv7zrvvcskhdat,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**Author:** `swalling`
+
+**Description:**
+On English Wikipedia, we should add a tag (https://www.mediawiki.org/wiki/Manual:Tags) to edits made to articles chosen from Special:GettingStarted by new editors. 
+
+We are logging actions anonymously with EventLogging, but providing a public tag of edits made through this interface has additional advantages:
+
+* It will allow product managers and analysts the ability to see a real time stream of the edits
+* It will help community members inspect the overall stream of edits, and assess them for quality
+* It will explain to anyone who is watching a page how new editors found the article, and why they are editing it
+* It will allow us to find and contact the new editors who use Special:GettingStarted (right now vandals are being warned, but good editors are being ignored for the most part)
+
+If we're adding a tag, we should assume that most community members won't know what Special:GettingStarted is. With that in mind, I propose the following for the tag text: [[Special:Tags|Tag]]: new editor [[Wikipedia:GettingStarted|getting started]]
+
+This is also appropriately agnostic to the task type (copyediting, wikifying, etc.), which is likely to change as the project evolves. You can see other tags in use on English Wikipedia at Special:Tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355729280,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_description,resolved
+Tag edits made through Special:GettingStarted,https://gerrit.wikimedia.org/r/#/c/42198/ is mostly done.,1357771169,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,The specs for the server-side logging API that Dario hashed out with S and me earlier this morning would totally cover this. I think we can do it. I'll shoot for getting this done in time for the deployment window next Thursday (Jan 10th).,1357164189,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"They're using a totally different VisualEditor-specific API back/middleend, calling the API, then calling ChangeTags::AddTags after the save is done:
+
+https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=blob;f=ApiVisualEditor.php;h=b0fe2048a450cf9ee2e158931a10bf98d8ab5723;hb=refs/heads/master#l220
+
+That approach is not workable for us.  
+
+They also use a hook to list it as an available tag, which we could do:
+
+https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=blob;f=VisualEditor.hooks.php;h=d4660cb0eda0fe54e2ea00905c29182a9d2f4828;hb=refs/heads/master#l53",1355796068,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"(In reply to comment #3)
+> Adding Maxsem as well, since he did this for MobileFrontEnd.
+
+No, what I did was a quick AbuseFilter hack. Look in VE for real solution:)",1355793937,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**tchay** wrote:
+
+Only newly registered users that have been onboarded, but your point is taken.
+
+We could log a different event since logging stores log_page and join against that.",1355791694,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**swalling** wrote:
+
+I'm not sure a time window and tagging of all edits by newly-registered users within the window works. Lots of users edit shortly after account creation, but are not editing one of the articles selected from the list on Special:GettingStarted. We only want edits to those pages, by people who came from the Special page.",1355791571,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**tchay** wrote:
+
+Oops! Adding Andrew Garret.
+
+The code is in ChangTags.php
+
+Possibility?
+
+1. Use the tags interface to create a tag on the getting started event during account creation: say ""onboarded""
+
+2. During an edit save, you check the tags database for the tag for that user
+
+SELECT count(*) from change_tag as ct AND logging as log WHERE ct.ct_log_id=log.log_id AND log.log_type=1 AND ct.tag=""onboarded"" AND log.log_user=$user_id AND (some time window filter?)
+
+3. If this returns anything then you add a (different) tag to the edit tags that allows this to be tracked.",1355790756,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**tchay** wrote:
+
+Possibility?
+
+You use the tags interface to",1355790322,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**swalling** wrote:
+
+Adding Maxsem as well, since he did this for MobileFrontEnd.",1355789222,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"**swalling** wrote:
+
+Adding Kaldari, since he has experience adding tags for WikiLove.",1355783504,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+Tag edits made through Special:GettingStarted,"Does anyone know how to pass this along the chain (view->edit->save)?  Ideally, we could use a query string parameter.  There are no useful docs at https://www.mediawiki.org/wiki/Manual:Tags , so we'll have to dig into the code.",1355781256,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-sqgxilqkeecvprvfh7ro,task_subcomment,NA
+"Inline aliens behaving incorrectly in some cases, seems to depend on selection","Inline image (used as icon) is incorrectly alienated, sometimes (?).
+
+Test case:
+
+Open https://en.wikipedia.org/wiki/User:Raymond/inline_image in VisualEditor mode:
+
+1. Thumbed image and inline image are alienated
+2. Dismiss the notice bubble
+3. Thumbed image is alienated, but inline image is NOT. It is clickable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/inline_image",1355677860,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-xtwsiyvycjjuwkmu2mcm,task_description,resolved
+"Inline aliens behaving incorrectly in some cases, seems to depend on selection","(In reply to comment #2)
+> I'm not able to reproduce it. Please confirm if this still occurs to you -
+> and
+> if o - please provide information about your platform as well. Thanks.
+
+As reporter of this bug I cannot reproduce it now.",1360359290,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-xtwsiyvycjjuwkmu2mcm,task_subcomment,NA
+"Inline aliens behaving incorrectly in some cases, seems to depend on selection",I'm not able to reproduce it. Please confirm if this still occurs to you - and if o - please provide information about your platform as well. Thanks.,1360356597,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-xtwsiyvycjjuwkmu2mcm,task_subcomment,NA
+"Inline aliens behaving incorrectly in some cases, seems to depend on selection","4. Click in the paragraph containing the inline image. It's now behaving correctly again.
+
+
+I've seen this bug with references as well: inline aliens have incorrect hover behavior in some cases, seems to be related to where the selection is.",1355693611,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xtwsiyvycjjuwkmu2mcm,task_subcomment,NA
+VisualEditor: A slug's new contents appear not to get inserted into the DM in at least once case,"* Click into VE on https://en.wikipedia.org/wiki/User:Thehelpfulone/test
+* Click cursor into one of the many LI slugs of the multiply-indented list.
+* Type some contents into the slug
+* Press ""left""; suddenly, the cursor is back at 0,0
+* Click into the ultimate LI with ""real"" content (not the one just created) and outdent repeatedly; you will over-write the new LI as if it wasn't there (indeed, it never reaches the DM).
+
+This may be similar to other slug bugs, given the core issue. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355530440,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-czuwyblk43urnavypsbt,task_description,resolved
+VisualEditor: A slug's new contents appear not to get inserted into the DM in at least once case,"(In reply to comment #1)
+> @James: Are you still able to reproduce it?
+
+No; partially invalid because we no longer show lots of distinct slugged LIs for lists. :-)
+
+> Also, I wonder if it is correct behavior that if you have completely empty by
+> multiply-indented list and you press backspace in the deepest li - it delete
+> entire list. Check out this video:
+> https://dl.dropboxusercontent.com/u/1026938/multiplyindented.mov
+
+This feels a bit wrong, yeah; maybe just decrease by one?",1371171784,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-czuwyblk43urnavypsbt,task_subcomment,NA
+VisualEditor: A slug's new contents appear not to get inserted into the DM in at least once case,"@James: Are you still able to reproduce it?
+
+Also, I wonder if it is correct behavior that if you have completely empty by multiply-indented list and you press backspace in the deepest li - it delete entire list. Check out this video: https://dl.dropboxusercontent.com/u/1026938/multiplyindented.mov",1371002735,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-czuwyblk43urnavypsbt,task_subcomment,NA
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,"Screenshot showing the diff and the editor
+
+Steps to reproduce problem:
+* Open VisualEditor on https://en.wikipedia.org/wiki/Buri_Ram_Airport
+* The cursor will be on top of the article in a paragraph-placeholder with bold styling (because the first word of the article is bolded)
+* Type ""a""
+
+Expected result:
+The character is inserted. Showing the diff now shows the addition of ""'''a'''"" (either above or below the {{infobox}}, doesn't really matter). Preferably below so that it is next to the paragraph it was added before.
+
+Actual result:
+The character is inserted. Visually nothing else changed (the infobox and the rest of the article are stil there). However, clicking ""Review and save"" now will show a diff where the infobox and the entire article have been removed and ""'''a'''"" was added in its place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9591}",1355443440,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_description,resolved
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,This seems to be fixed already (try to reproduce on English Wikipedia).,1371063948,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_subcomment,NA
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,I think I know what's the reason of this problem. I will work on it next week.,1364152745,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_subcomment,NA
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,*** Bug 46506 has been marked as a duplicate of this bug. ***,1364127463,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_subcomment,NA
+VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article,"This is fundamentally an ""editing what appears to be a blank space but is actually a slug means this behave in a way I did not anticipate"" - assigning to CE, but we really need to talk about this and what we should do longer-term.",1357598884,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2hzsnhrqn3e44r3w5wpx,task_subcomment,NA
+VisualEditor: Slug oddness - new text in list item before alien node is ignored,"Screenshot
+
+Steps to reproduce problem:
+* Open VisualEditor on https://en.wikipedia.org/wiki/Buri_Ram_Airport
+* Put cursor in the placeholder slug in the second list item of the External links. There is an alien node here as the external link is generated with a template.
+* Type ""a""
+* Press ""Review and save""
+
+Expected result:
+A diff adding the letter ""a"".
+
+Actual result:
+Empty diff (see attachment)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9589}",1355442900,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xsynpfa72ixj4q44cgdk,task_description,resolved
+VisualEditor: Slug oddness - new text in list item before alien node is ignored,This seems to be fixed already (try to reproduce on English Wikipedia).,1371067225,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-xsynpfa72ixj4q44cgdk,task_subcomment,NA
+"VisualEditor: ""localStorage is null"" error message","Firefox 17.0.1 and Ubuntu 12.10; using the VE causes a failure with a ""localStorage is null"" error.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355424480,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-zi2tai4mmhmdntkaup52,task_description,invalid
+"VisualEditor: ""localStorage is null"" error message","**orbit** wrote:
+
+We're going to resign (for now at least) from using localStorage for copy and paste. Although I was unable to reproduce this error, we're only using localStorage for copy and paste.",1361832521,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zi2tai4mmhmdntkaup52,task_subcomment,NA
+"VisualEditor: ""localStorage is null"" error message","@James: Yes, it is. I will look into it.",1360357578,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-zi2tai4mmhmdntkaup52,task_subcomment,NA
+"VisualEditor: ""localStorage is null"" error message",Sounds like a CE-issue (for the copy-and-paste code?).,1355508197,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zi2tai4mmhmdntkaup52,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations","Here is normal behavior:
+
+1. In VisualEditor, type a line of text.
+2. Position your cursor at the beginning of that line.
+3. Press the Home key on your keyboard, to move the cursor to the beginning of the line.
+4. Wait a moment.
+5. Press Enter, and the current text is pushed downward one line. This is correct and expected.
+
+Here is the buggy behavior:
+
+1. In VisualEditor, type a line of text.
+2. Position your cursor at the beginning of that line.
+3. VERY QUICKLY, press the Home key followed by the Enter key.
+4. The cursor moves down one line, so it is positioned below the line of text. The text did not move. This is incorrect behavior. The line of text should have been pushed downward.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355422260,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-zvx6cpsh2puavdxxft2q,task_description,resolved
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations","Fixed and will go out with wmf8, from Thursday 20 June.",1371169075,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations",https://gerrit.wikimedia.org/r/68300 (Gerrit Change I35c892581943057acbf9ddd638576e998cc82c1a) | change APPROVED and MERGED [by jenkins-bot],1371169013,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations",Related URL: https://gerrit.wikimedia.org/r/68300 (Gerrit Change I35c892581943057acbf9ddd638576e998cc82c1a),1371076469,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations",I've just created a test that covers this problem: https://github.com/inez/VE-tests/commit/4c1a444b207b37f90dc5d5ce969b5af00ee893ef (solution still not pushed).,1371002298,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations",This issue is not browser specific.,1371000914,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations","Sounds like a polling issue. ""Very quickly"" probably means ""before the polling loop gets a chance to run""; it runs every 200ms.",1355558848,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Race condition between ""Beginning of Line"" and ""New Line"" operations","Crap... I made a mistake in my report.
+
+In line (2) of both examples, change ""beginning of the line"" to ""end of the line."" The cursor needs to be at the END of the line.",1355422346,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-zvx6cpsh2puavdxxft2q,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally","1. Using VisualEditor, edit an article that already has some text in it.
+2. Select all text with Ctrl-A.
+3. Press the DELETE key. All text disappears as expected.
+4. Click ""Review and Save"". The diff shows that text is STILL PRESENT in the article.
+5. Finish saving. You will see that text is still in the article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1355422080,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-i4afw6okkvtcnnnerpcr,task_description,resolved
+"VisualEditor: Select All + Delete removes all text from sight, but not internally",This is now fixed (as of the new deletion code).,1371505460,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally","**orbit** wrote:
+
+Reproducible in Firefox.",1356133772,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally","I can reproduce this with backspace too. Does seem to be a CE issue, because the linear model isn't emptied (it could also have been a selser issue).",1355693980,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally","More widely, it looks like the CE layer doesn't bind to delete the way it does to backspace; assigning.",1355429997,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+"VisualEditor: Select All + Delete removes all text from sight, but not internally",The problem also occurs if you highlight all the article text with your mouse and press DEL.,1355423978,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-i4afw6okkvtcnnnerpcr,task_subcomment,NA
+VisualEditor: Some elements not alienated,"The coord template is not hatched but still visible and the links are still clickable.
+
+https://en.wikipedia.org/wiki/User:Raymond/coords
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1355413560,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-bhfeaa4hp3iuxtp7inrp,task_description,resolved
+VisualEditor: Some elements not alienated,This (first part; second part is now bug 43155) is fixed in gerrit 39834 which is now merged; will be deployed as part of the 2013-01-16 release cycle.,1357678877,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bhfeaa4hp3iuxtp7inrp,task_subcomment,NA
+VisualEditor: Some elements not alienated,"(In reply to comment #0)
+> The coord template is not hatched but still visible and the links are still
+> clickable.
+> 
+> https://en.wikipedia.org/wiki/User:Raymond/coords
+
+Inspecting it shows that this is being alienated correctly, but for some reason it's not getting hatched out and not behaving quite correctly. That's a CE bug.
+
+Inspecting the coords element shows:
+
+<div contenteditable=""false"" class=""ve-ce-leafNode ve-ce-alienNode ve-ce-alienInlineNode""><span typeof=""mw:Object/Template "" about=""#mwt1"" ...>[lots of scary stuff here, including nested <span>s]</span></div>
+
+
+(In reply to comment #1)
+> There are a few templates that aren't hatched. For example, the tables
+> created
+> by [[w:en:Template:Canadian_first_minister_list]] are editable with
+> VisualEditor, and trying to do so results in a mess of wikitext.
+This is actually a different bug. Tables of Canadian prime ministers aren't alienated at all due to a bug in Parsoid, while on Raymond's coords page the template is alienated correctly but the alien itself is misbehaving. Keeping this bug for the coords bug, splitting off the Canadian prime ministers bug to bug 43155.",1355560412,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bhfeaa4hp3iuxtp7inrp,task_subcomment,NA
+VisualEditor: Some elements not alienated,"**jnichols** wrote:
+
+There are a few templates that aren't hatched. For example, the tables created by [[w:en:Template:Canadian_first_minister_list]] are editable with VisualEditor, and trying to do so results in a mess of wikitext.",1355426222,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bhfeaa4hp3iuxtp7inrp,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'left'  / call method 'getOuterLength'.""","A couple more uncaught TypeError, a la https://bugzilla.wikimedia.org/show_bug.cgi?id=43014:
+
+Uncaught TypeError: Cannot read property 'left' of undefined
+
+Uncaught TypeError: Cannot call method 'getOuterLength' of undefined
+
+Reported http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Error_loading_data_from_server:_Server_error
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355346720,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-alx56wytsjcuj4hvxv6h,task_description,invalid
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'left'  / call method 'getOuterLength'.""","Cannot reproduce this without a deep stack trace; also, this is from three months ago, and we're unlikely to still have the same issue.",1364318251,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-alx56wytsjcuj4hvxv6h,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'left'  / call method 'getOuterLength'.""","Given errors sounds like a selection issue; assigning to CE, but please advise if not.",1355429701,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-alx56wytsjcuj4hvxv6h,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Example Page: http://en.wikipedia.org/wiki/Ansaldo_Poggi
+
+1. Go to the top, click into the empty line above the ineditable image (the normally right floating image). This empty line should not exist. It can however, be deleted (press ""delete"" on the keyboard) which causes the start text to jump in front of the ""Modern Bolognese Violin-Making Table"" image.
+
+2. Click somewhere inside ""References"". Move the cursor with the keyboard  to the position after the ""s"". Press ""delete"" on the keyboard. The line starting with ""Tito Gotti"" will be merged with the heading (ignoring the uneditable ""references"" tag and ""cite"" template).
+
+3. Similar to the above: Click somewhere inside ""References"". Move the cursor with the keyboard  to the position after the ""s"". Move one more right into the (errorneously existing) empty line between the heading and the uneditable references tag. Press ""delete"" on the keyboard. The line starting with ""Tito Gotti"" will jump above the uneditable ""references"" tag and ""cite"" template.
+
+4. Do the same as above, i.e. go to the empty line after the References-Heading. However, this time click with the mouse into the line. Press ""delete"" on the keyboard. This time the behavior is different, nothing is deleted and the cursor jumps to the start of the article. This in itself seems again to be an error in the ordering of page objects. Now try to repeat this with different browser windows screen or zoom sizes, so that the originally, the start of the article is not visible before clicking delete. It can be seen that the focus is not updated, the cursor is outside of the visible area. Press ""delete"" again and with seeing it, parts of the text can be deleted.
+
+5. Do the same as above, click on line below reference with the mouse, delete once, cursor jumps to top. Do not delete again, but put the cursor again into the line below the reference heading with the mouse. This time the ineditable <references> tag is deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355334540,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-qr4la5fjep3uvnewafhr,task_description,resolved
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),These are all moot since the redesign of slugs over a year ago.,1420844082,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Would having an object inspector on the non-editable non-text things that provides options to ""insert text before""/""insert text after"" be a solution to the problem?",1360616789,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Created attachment 11767
+Mockup of VisualEditor in various modes
+
+Just wanted to note that slugs were an experimental solution to the problem of ""how do you allow users to insert content between non-text things?
+
+We have had a lot of ideas, but so far the direction we intend to go is to remove them entirely from the existing ""layout"" mode and provide an ""outline"" mode to the editor which includes them. There could also be a ""source"" mode where we could integrate the markup editing experience directly into VisualEditor.
+
+**Attached**: {F10138}",1360609163,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Gladly: Windows 7, continuous updates, Google Chrome, Version 23.0.1271.95 m",1355343138,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?),"Thank you for the bug report.  Though I am unable to reproduce the first step in Firefox or Chrome.  To help with debugging, would you please include your browser information?",1355341412,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-qr4la5fjep3uvnewafhr,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"According to <https://test.wikipedia.org/wiki/Special:Version>, the VisualEditor extension is installed, but it doesn't seem to be enabled. I think VisualEditor should be enabled for all namespaces, all skins, all users, etc. on test.wikipedia.org.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1355330700,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3qimgh7ycaviacztiyae,task_description,resolved
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,This is now deployed. Marking as fixed.,1367270827,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"(In reply to comment #9)
+> Yeah; it would be helpful if gerrit changes which mentioned bugs were either
+> always or never proxied by the bot to bugzilla, instead of the half-way house
+> of being unknown. :-)
+
+Feel free to file a new ticket with reference to bug 17322. :)",1367251782,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"Yeah; it would be helpful if gerrit changes which mentioned bugs were either always or never proxied by the bot to bugzilla, instead of the half-way house of being unknown. :-)
+
+Apologies, all!
+
+J.",1367250758,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"(In reply to comment #7)
+> Related URL: https://gerrit.wikimedia.org/r/61382 (Gerrit Change
+> I56906c123e924b84eb9ee076cd67254f8935911d)
+
+Result of a typo. ^",1367249638,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,Related URL: https://gerrit.wikimedia.org/r/61382 (Gerrit Change I56906c123e924b84eb9ee076cd67254f8935911d),1367247867,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"(In reply to comment #5)
+> Related URL: https://gerrit.wikimedia.org/r/61250 (Gerrit Change
+> I98028df0bcb621e8f13a2f8ab130e86a9010ebeb)
+This change enables VisualEditor on test2wiki, and will be deployed on Monday.
+
+I fixed the namespace configuration last week, it's now the same on all wikis: VisualEditor is enabled in the main and user namespaces, as well as the VisualEditor namespace where it exists (testwiki and mediawikiwiki have this namespace for historical reasons).",1367130629,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,Related URL: https://gerrit.wikimedia.org/r/61250 (Gerrit Change I98028df0bcb621e8f13a2f8ab130e86a9010ebeb),1367130305,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"http://test.wikipedia.org/wiki/Special:Preferences#mw-prefsection-editing allows to ""Enable VisualEditor (only in the main and user namespaces)""
+http://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-editing does not offer enabling VisualEditor.
+
+Roan: As this is assigned to you, do you plan to work on this and is this high priority? If not, please reset. Thanks.",1366908803,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,"I can see ""Enable VisualEditor"" checkbox at en.wikipedia.org[1] but not at test2.wikipedia.org[2].
+
+[1] http://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-editing
+[2] http://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-editing",1355926606,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,I believe Roan will be doing this later today.,1355343355,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org,Apparently there's interest in having VisualEditor enabled on test2.wikipedia.org as well (cf. <http://lists.wikimedia.org/pipermail/wikitech-l/2012-December/065034.html>).,1355341331,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3qimgh7ycaviacztiyae,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"When I go to <https://en.wikipedia.org/wiki/User:Trevor_Parscal> and click the ""visualeditor"" tab, my browser console says:
+
+---
+The page at https://en.wikipedia.org/wiki/User:Trevor_Parscal displayed insecure content from http://en.wikipedia.org/w?title=Special:FilePath/California_Bay_Area_county_map.svg&width=.
+---
+
+Consequently, the pretty green lock icon in Google Chrome turns yellow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1355327160,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_description,resolved
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934071,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),https://gerrit.wikimedia.org/r/70344 (Gerrit Change I253b9b7a9b463439e86d7cf7975cd92f9c851e70) | change APPROVED and MERGED [by jenkins-bot],1372119634,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),The fix will go out with tomorrow's Parsoid deployment.,1372119634,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),https://gerrit.wikimedia.org/r/70348 (Gerrit Change Ied95c87fda13dbea2b8c46ad1e96fde1c50c1517) | change APPROVED and MERGED [by jenkins-bot],1372119224,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Related URL: https://gerrit.wikimedia.org/r/70348 (Gerrit Change Ied95c87fda13dbea2b8c46ad1e96fde1c50c1517),1372117100,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Related URL: https://gerrit.wikimedia.org/r/70344 (Gerrit Change I253b9b7a9b463439e86d7cf7975cd92f9c851e70),1372115462,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),*** Bug 49984 has been marked as a duplicate of this bug. ***,1371855005,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"We used to use a special page redirect hack, but now use the API to properly retrieve image information including the path. So the new code needs to implement some similar protocol-relative massaging for image URLs, at least for the domains we know to support both http and https.",1371603843,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"Per Roan's comments, moving to Parsoid so they can fix.",1371603429,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"(In reply to comment #7)
+> This seems to have been unfixed in production.
+> 
+Specifically, Parsoid is now once again returning http:// URLs for images (except in labs, where it returns https:// URLs). MZ submitted a fix in December to make these URLs protocol-relative, but this seems to have been unfixed somehow.
+
+Perhaps the repository URL is being grabbed from the API? That would explain why it's now a fully qualified URL, and it might explain the difference between labs and production.",1371603136,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"This seems to have been unfixed in production.
+
+Strangely, parsoid.wmflabs.org is now giving me https URLs for images.",1371583342,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),*** Bug 49283 has been marked as a duplicate of this bug. ***,1371576350,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),The page at https://en.wikipedia.org/wiki/User:Trevor_Parscal?veaction=edit displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/f/ff/California_Bay_Area_county_map.svg/38px-California_Bay_Area_county_map.svg.png.,1371574794,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),"I am getting this issue, on the test page referenced in the bug and others, again. The URLs do not contain Special:FilePath anymore, so perhaps something was changed about  how images are handled that introduced a regression? Reopening this bug since the issue appears to be essentially the same.",1371531045,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Tagging with deploy-train cycle.,1357578934,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Fixed by <https://gerrit.wikimedia.org/r/38673>.,1355449078,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs),Upstream Parsoid bug: bug 42976,1355339026,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2fap3nvdrgza3a4h2sj6,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","[Wikitech-l] Alpha version of the VisualEditor now available on the English Wikipedia
+
+I tried it on enwiki in my sandbox. 
+
+It does not work: when I want to ""Review and save"" a box pops up ""Review your changes"" --- but nothing happens.
+
+* MediaWiki 	1.21wmf5 (f4a44f9)
+* VisualEditor (Version 0.1.0) 	(2e6425a)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355299800,PHID-USER-ppvnwr24o32pux3le5ov,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_description,resolved
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","For completeness: This was fixed in https://gerrit.wikimedia.org/r/38382, because I broke new page creation in the Selective Serializer by not properly handling the error that was raised on not finding page content. Sorry about that folks, there was some turbulence, but we're looking to arrive at our destination ahead of schedule.",1355515620,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","Just a note: this affected all page creations, not just subpages. The selective serializer mode did not deal properly with the fetch failure for the original (non-existing) page source.",1355436359,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them",Happy to help. :-),1355436247,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","@James Yes I confirm that it now works for me on my subpage ! Well and quickly fixed.
+
+:-)",1355434816,PHID-USER-ppvnwr24o32pux3le5ov,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","This appears to now be fixed, following an update to the Parsoid service yesterday; I can now edit and create articles with ""/""s in their title. Closing as fixed.",1355429392,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","There are going to be lots of things that are broken... that's why it's an experimental alpha release. It works on lots of pages but it still doesn't on lots of others. Personally I'd say the hype is valid but so are the huge cautions of how many things don't work :). 
+
+Roan et.al: After some quick experimentation this looks like a possible issues with sub pages in general. The 'hang and not do anything' error that Wikinaut is talking about happens when you're trying to create the subpage (Also experienced it trying to create a subpage in mainspace with the VE). If you try to edit a subpage with VE after it already existed (was created with normal editor) then you get a pop up warning ""Error loading data from server: Server error. Would you like to retry?"". Trying a couple times on a couple different pages the situation appears to be the same each time.
+
+Tested pages:
+
+User:Jalexander/sandbox
+Wikipedia/History?redirect=no
+User:Wikinaut/sandbox
+Wikipedia/test
+
+I can do screenshots if you need them easily.",1355357679,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","Big hype about non working VE...
+
+this page does not work with VE https://en.wikipedia.org/wiki/User:Wikinaut/sandbox",1355355946,PHID-USER-ppvnwr24o32pux3le5ov,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","(In reply to comment #6)
+> VE alpha == not mature yet
+That's what we've been telling everyone all along. There's a reason we called it an alpha release ;)
+
+Could you link to the page that was failing for you?",1355338217,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","I tried other pages, saw different page formatting when using template {{ok}}  and got immediately 
+
++ ""Error loading data from server: Unsuccessful request: Error contacting the Parsoid server""
+
+when trying to edit and ""Review and save""
+
+VE alpha == not mature yet",1355309356,PHID-USER-ppvnwr24o32pux3le5ov,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","@James
+
++ works on my User page
++ does not work on User:username/Sandbox page (personal link portlet ""Sandbox"")
+
+I modified the bug title.",1355302660,PHID-USER-ppvnwr24o32pux3le5ov,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","Not totally sure what's up with the Firefox piece other then see if you can try again a couple minutes later or another page (though your sandbox shouldn't be a problem) so I'll leave that for JamesF and the VE crew ;). 
+
+For IE 8, however, it's likely because VE isn't supported in IE8 yet ( per https://en.wikipedia.org/wiki/Wikipedia:VisualEditor#Current_limitations Chrome/Firefox/Safari only). If I remember correctly it's because it actually needs a fair bit of refactoring specifically for IE (and possibly only 9 and 10 and never 8) because it handles things totally differently.",1355301776,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them","IE8 shows errors
+Details zum Fehler auf der Webseite
+
+Benutzer-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C)
+Zeitstempel: Wed, 12 Dec 2012 08:18:19 UTC
+
+
+Meldung: Bezeichner, Zeichenfolge oder Zahl erwartet
+Zeile: 5
+Zeichen: 746
+Code: 0
+URI: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Cjquery.multiSuggest%7Crangy&skin=vector&version=20121212T032708Z&*",1355300330,PHID-USER-ppvnwr24o32pux3le5ov,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them",http://i.imgur.com/gsL16.png,1355300009,PHID-USER-ppvnwr24o32pux3le5ov,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+"VisualEditor: Parsoid call on ""Review and save"" slide hangs for pages with ""/""s in them",* Firefox 17.0.1,1355299935,PHID-USER-ppvnwr24o32pux3le5ov,False,PHID-TASK-vhisdvekk4sgvgkkuben,task_subcomment,NA
+VisualEditor: Removing copy/pasted link annotations removes the original as well,"1. Add a link to some text
+2. Copy the text
+3. Paste the text somewhere else
+4. Remove the link using the link inspector's trash icon
+5. See that both links are gone
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1355191860,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-rifozrrb2mk5wki2qrw4,task_description,resolved
+VisualEditor: Removing copy/pasted link annotations removes the original as well,Now landed in master.,1355193795,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rifozrrb2mk5wki2qrw4,task_subcomment,NA
+VisualEditor: Removing copy/pasted link annotations removes the original as well,Fixed in gerrit 38009.,1355192089,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rifozrrb2mk5wki2qrw4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,"**Author:** `orbit`
+
+**Description:**
+Steps to reproduce:
+1. Copy part of a headline and part of a following paragraph
+2. Paste into a paragrah
+
+The linmod being inserted will look something like this:
+[""s"", ""u"", ""m"", ""?"", Object, Object, ""C"", ""o"", ""n"", ""t""]
+
+The objects are closing heading and opening paragraph.
+
+The error is in ve.dm.Document.js on 1145.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354837920,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-upsvylaxm2favfgmiub4,task_description,resolved
+VisualEditor: Type mismatch when inserting unbalanced content,Now merged into master.,1354916275,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,Id9269a29e51ca213508de8f155d3feec5e5b0774 should resolve this,1354907772,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,I believe Trevor meant ab</p></li></ol><p>cd breaking.,1354904980,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,"**orbit** wrote:
+
+ab</p></li><p>cd is invalid markup anyway.",1354903732,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,"I0d2b593e05ebdee807e2cc6eeb902d542db3895f is a start, but there's still some issues.
+
+Given the target: <p>12[cursor]34</p>
+
+OK: ab</p><p>cd
+OK: ab</h2><p>cd
+BAD: ab</p></li><p>cd",1354843715,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Type mismatch when inserting unbalanced content,Now being done by Trevor; reassigning.,1354841984,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-upsvylaxm2favfgmiub4,task_subcomment,NA
+VisualEditor: Deleting across inline alien errors,"**Author:** `orbit`
+
+**Description:**
+Try creating ""some text <inlinealien>blah</inlinealien> more text"" and select across the inline alien and delete. 
+
+Uncaught TypeError: Cannot call method 'getDataFromNode' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354669260,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3mbtnybtpij42l625lvd,task_description,resolved
+VisualEditor: Deleting across inline alien errors,Fix in gerrit 37056.,1354738462,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3mbtnybtpij42l625lvd,task_subcomment,NA
+VisualEditor: Deleting across inline alien errors,"Argh. I figured out why this happens.
+
+* .splice() is called on the dm.ParagraphNode to remove the alien
+* which calls .adjustLength() on the dm.ParagraphNode
+* which emits an update event on the dm.ParagraphNode
+* which causes .renderContents() to be called on the ce.ParagraphNode
+* which attempts to rerender its ce.TextNode children
+* one of which is now associated with a detached dm.TextNode
+* which means it crashed when trying to get the data from the linear model
+
+I'm not entirely sure what the solution should be. Perhaps ce.ContentBranchNode shouldn't rerender for an update on the node itself, only on its children?",1354733644,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3mbtnybtpij42l625lvd,task_subcomment,NA
+VisualEditor: Backspace over a slug at the end of the document throws an error,"Pressing backspace in a slug at the end of the document throws an error:
+
+* Create a new page (or go to an existing one), and enter ""ABCD\n"" at the end
+* With the cursor in the new slug, press backspace; this throws an error:
+
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 9 is out of bounds
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1354563780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bsg3qk2puigbios7b56m,task_description,resolved
+VisualEditor: Backspace over a slug at the end of the document throws an error,Fixed here: https://gerrit.wikimedia.org/r/#/c/37162/,1354755508,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-bsg3qk2puigbios7b56m,task_subcomment,NA
+VisualEditor: Link inspector doesn't close when moving cursor to a different link,"Inspect a link, then click on a different link, the inspector moves to the new cursor location and remains open.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354217520,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-mutotkwptjvzfn2nuk4y,task_description,resolved
+VisualEditor: Link inspector doesn't close when moving cursor to a different link,"Resolved in I859123a5fcd36bc2afb2e578f81f30a944c8583a
+
+This bug was introduced somewhere in the recent context rewrite.",1354227540,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-mutotkwptjvzfn2nuk4y,task_subcomment,NA
+VisualEditor: Save dialog triggers error (selection bug?),"On launching the save dialog, a console error is thrown:
+
+Uncaught TypeError: Cannot read property 'nodeType' of null /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:117
+ve.ce.getOffset /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:117
+ve.ce.SurfaceObserver.poll /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:136
+ve.ce.SurfaceObserver.stop /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:82
+ve.ce.Surface.documentOnBlur /w/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js:324
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354155360,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bp5lorruinm7xnzv76mb,task_description,resolved
+VisualEditor: Save dialog triggers error (selection bug?),"
+
+*** This bug has been marked as a duplicate of bug 41504 ***",1354155569,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-bp5lorruinm7xnzv76mb,task_subcomment,NA
+VisualEditor: Integrate edit conflict confirmation into the save dialog,"As of I002c5aa23704c1c46ef46fa1970a4254614b9eb1 when saving and an edit conflict occurs the user is shown a browser-provided confirmation box which allows them to either cancel or resolve the conflict manually.
+
+It would be much better if this was integrated into the save dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1354147200,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-2iww52jmzvuwmwgsjy5e,task_description,resolved
+VisualEditor: Integrate edit conflict confirmation into the save dialog,Merged into master and will go out with wmf5.,1368574606,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2iww52jmzvuwmwgsjy5e,task_subcomment,NA
+VisualEditor: Integrate edit conflict confirmation into the save dialog,Related URL: https://gerrit.wikimedia.org/r/63679 (Gerrit Change I709d936d998b130515b62de880c6e7aa7978786b),1368550555,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2iww52jmzvuwmwgsjy5e,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"It isn't just that this would throw an exception:
+
+ new mw.Uri('http://krinkle.dev/mediawiki/alpha/index.php?title=VisualEditor:S@box&action=edit');
+
+Although that is also bad (when done on non-@ pages), it is especially bad that on pages containing an @ in the url, the module won't even finish loading because of this line:
+
+ defaultUri = new Uri( documentLocation );
+
+So instead, mw.Uri stays undefined.
+
+--------------------------
+**Version**: 1.19
+**Severity**: critical",1354127040,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vrsv454ata26ui2zocei,task_description,resolved
+mediawiki.Uri crashes in pages with '@' in their url,"I know mine doesn't work, because I put it together in five minutes, but it's definitely proper. Here's the code I used to construct it: http://pastebin.com/ELJ4LdKy",1358706140,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"Tyler, this looks way too short on the first glance and doesn't work. It also explicitly doesn't support protocol-relative URIs.
+
+Here's one that works (this is used by Ruby's URI parsing library). Of course it's not hardcoded in the code like this, but constructed on the fly from regexes for specific URI parts. I could port this to JS in a reasonable way, if anybody except for me actually wants this.
+
+/^(?:[a-zA-Z][\-+.a-zA-Z\d]*:(?:(?:\/\/(?:(?:(?:[\-_.!~*'()a-zA-Z\d;:&=+$,]|%[a-fA-F\d]{2})*@)?(?:(?:[a-zA-Z0-9\-.]|%\h\h)+|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}|\[(?:(?:[a-fA-F\d]{1,4}:)*(?:[a-fA-F\d]{1,4}|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})|(?:(?:[a-fA-F\d]{1,4}:)*[a-fA-F\d]{1,4})?::(?:(?:[a-fA-F\d]{1,4}:)*(?:[a-fA-F\d]{1,4}|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}))?)\])(?::\d*)?|(?:[\-_.!~*'()a-zA-Z\d$,;:@&=+]|%[a-fA-F\d]{2})+)(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*)?|\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*)(?:\?(?:(?:[\-_.!~*'()a-zA-Z\d;\/?:@&=+$,\[\]]|%[a-fA-F\d]{2})*))?|(?:[\-_.!~*'()a-zA-Z\d;?:@&=+$,]|%[a-fA-F\d]{2})(?:[\-_.!~*'()a-zA-Z\d;\/?:@&=+$,\[\]]|%[a-fA-F\d]{2})*)|(?:\/\/(?:(?:(?:[\-_.!~*'()a-zA-Z\d;:&=+$,]|%[a-fA-F\d]{2})*@)?(?:(?:[a-zA-Z0-9\-.]|%\h\h)+|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}|\[(?:(?:[a-fA-F\d]{1,4}:)*(?:[a-fA-F\d]{1,4}|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})|(?:(?:[a-fA-F\d]{1,4}:)*[a-fA-F\d]{1,4})?::(?:(?:[a-fA-F\d]{1,4}:)*(?:[a-fA-F\d]{1,4}|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}))?)\])(?::\d*)?|(?:[\-_.!~*'()a-zA-Z\d$,;:@&=+]|%[a-fA-F\d]{2})+)(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*)?|\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*|(?:[\-_.!~*'()a-zA-Z\d;@&=+$,]|%[a-fA-F\d]{2})+(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*(?:\/(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*(?:;(?:[\-_.!~*'()a-zA-Z\d:@&=+$,]|%[a-fA-F\d]{2})*)*)*)?)(?:\?(?:[\-_.!~*'()a-zA-Z\d;\/?:@&=+$,\[\]]|%[a-fA-F\d]{2})*)?)?(?:#(?:[\-_.!~*'()a-zA-Z\d;\/?:@&=+$,\[\]]|%[a-fA-F\d]{2})*)?$/",1358688372,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"BTW, for whoever's curious, here is what an official URI regular expression would look like (it does't work, needs debugging; it's probably missing a parentheses or something):
+
+/^[A-Za-z][A-Za-z0-9\+\-\.]*:(\/\/(([:A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2})@)?(\[(|v[A-Fa-f]+\.[:A-Z0-9-\._~!\$&'\(\)\*\+,;=]+)\]|([0-9]|[1-9][0-9]|2[0-4][0-9]|25[0-5])\.([0-9]|[1-9][0-9]|2[0-4][0-9]|25[0-5])\.([0-9]|[1-9][0-9]|2[0-4][0-9]|25[0-5])\.([0-9]|[1-9][0-9]|2[0-4][0-9]|25[0-5])|([A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))(:[0-9]*)?(\/(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))*)*|\/(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))+(\/(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))*)*|(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))+(\/(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2}))*)*|)\?((([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2})|[\/\?])*)?(#(([:@A-Z0-9-\._~!\$&'\(\)\*\+,;=]|%[A-Fa-f]{2})|[\/\?])*)?$/",1358636139,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,Change-Id: I4954bfd3750d5c990e91cc0dc8a175225ccbad1e,1358621587,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"Yes, but is it truly necessary to validate that much? I mean, for example, take the (invalid) URI ""https://www.google.com/search?q=test test"". The URI is invalid because it has a space character in the query, but if you were to do something like ""location.href = <that uri>"", it would work perfectly fine, because the browser automatically percent-encodes the space.
+
+Basically, I'm wondering for what the mw.Uri class is being used for that requires such strict validation.",1358556627,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #10)
+> I wouldn't attempt to make a comprehensive URI parsing library in JavaScript.
+
+> The first reason is because it's unnecessary. With the fix I just uploaded to
+> Gerrit, there should not be any more bugs in this function. 
+
+I just pointed out a glaring one above.
+
+(In reply to comment #8)
+> What about whitespace in the authority part? (This isn't allowed,
+> but those regexes match it just fine.)
+
+I'm sure there are more, waiting to be uncovered.
+
+
+> Secondly, the
+> regular expression would be absurdly complicated. URIs have specific sets of
+> characters that can be included only in certain sections. I wrote a regex for
+> an official URI once when I was working on the PHP version of this class
+> (still
+> in Gerrit), and it was so confusing it took days to get it working properly.
+
+Of course, I know this. That's why I'm suggesting using the work of someone who has already spent time pulling his hair out to get this right; or at least just taking those crazy regexes in from some other library.",1358549728,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"I wouldn't attempt to make a comprehensive URI parsing library in JavaScript. The first reason is because it's unnecessary. With the fix I just uploaded to Gerrit, there should not be any more bugs in this function. Secondly, the regular expression would be absurdly complicated. URIs have specific sets of characters that can be included only in certain sections. I wrote a regex for an official URI once when I was working on the PHP version of this class (still in Gerrit), and it was so confusing it took days to get it working properly.",1358545565,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #8)
+> (In reply to comment #6)
+> > On further investigation and following links from that gist, it looks like
+> > the
+> > regexes in mw.Uri aren't so half-baked.
+> > 
+> > They actually come from here:
+> > http://blog.stevenlevithan.com/archives/parseuri
+> 
+> If they weren't half-baked, mw.Uri wouldn't crash on '@' in the URL. 
+> 
+> These regexes are already awful (177 characters? Seriously?), and are bound
+> to
+> get worse as we discover more edge-cases. 
+> 
+> What about password with a '@' in it? (Yeah, this is allowed as far as I
+> know,
+
+No, those need to be url escaped afaik. At least in Chrome and in the nodejs modules I used it the password (especially the @ symbol) needs to be url escaped or it won't work.
+
+> While on second though the <a>-abuse I linked isn't a good idea, we really
+> need a serious parsing library.
+
+I'm open to suggestions, though it'll need to be flexible and be replaceable in-place to allow smooth transition (same API and and unit tests, different internal implementation).
+
+The module is generic enough to easily allow a different parser.
+
+But there is some ambiguity on the fields to be extracted and their meaning[1], so even a ""perfect"" library may need modification to work for us and our interpretation of those terms.
+
+[1] http://tantek.com/2011/238/b1/many-ways-slice-url-name-pieces",1358542770,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #6)
+> On further investigation and following links from that gist, it looks like
+> the
+> regexes in mw.Uri aren't so half-baked.
+> 
+> They actually come from here:
+> http://blog.stevenlevithan.com/archives/parseuri
+
+If they weren't half-baked, mw.Uri wouldn't crash on '@' in the URL. 
+
+These regexes are already awful (177 characters? Seriously?), and are bound to get worse as we discover more edge-cases. 
+
+What about password with a '@' in it? (Yeah, this is allowed as far as I know, and works.) What about whitespace in the authority part? (This isn't allowed, but those regexes match it just fine.)
+
+While on second though the <a>-abuse I linked isn't a good idea, we really need a serious parsing library.",1358532368,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #6)
+> (In reply to comment #3)
+> > I googled a little for a reasonable JS URI parsing library that could replace
+> > those half-baked regexes, and found this: https://gist.github.com/2428561
+> > 
+> > It seems genius and is 100% correct. Is it a good idea to use something like
+> > this? If it is, I can implement it.
+> 
+> That's not a URI parsing library, that's an unreliable hack using <a href="""">
+> parsing. See the comments there.
+> 
+> On further investigation and following links from that gist, it looks like
+> the
+> regexes in mw.Uri aren't so half-baked.
+> 
+> They actually come from here:
+> http://blog.stevenlevithan.com/archives/parseuri
+
+Indeed. You'll also notice that the user and password aren't parsed at all in that implementation.
+
+Also, https://gerrit.wikimedia.org/r/44665",1358531480,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"(In reply to comment #3)
+> I googled a little for a reasonable JS URI parsing library that could replace
+> those half-baked regexes, and found this: https://gist.github.com/2428561
+> 
+> It seems genius and is 100% correct. Is it a good idea to use something like
+> this? If it is, I can implement it.
+
+That's not a URI parsing library, that's an unreliable hack using <a href=""""> parsing. See the comments there.
+
+On further investigation and following links from that gist, it looks like the regexes in mw.Uri aren't so half-baked.
+
+They actually come from here:
+http://blog.stevenlevithan.com/archives/parseuri",1358530663,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,Found the problem. Expect a patch in the near future.,1358530566,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,It should be noted that those are HTML5-specific properties.,1358529061,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"I googled a little for a reasonable JS URI parsing library that could replace those half-baked regexes, and found this: https://gist.github.com/2428561
+
+It seems genius and is 100% correct. Is it a good idea to use something like this? If it is, I can implement it.",1355779261,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"Not yet, but if nobody does I will eventually.",1355764277,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+mediawiki.Uri crashes in pages with '@' in their url,"Krinkle: As dependency bug 42306 is assigned to, do you work on this?",1355708459,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vrsv454ata26ui2zocei,task_subcomment,NA
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,"Wikitext to reproduce:
+
+<span>
+[bunch of newlines]
+</span>
+
+Parsoid generates <span><p></p></span> for this, but it doesn't mark the span.
+
+Todo:
+* Make the failure a bit more graceful
+* Investigate whether p inside span is legal
+* Investigate other cases where this breakage occurs
+* File bug with Parsoid for proper protection of user-generated tags
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354071720,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_description,resolved
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,Resolved in If420ae80ab0777424a9a5517335ef9d0170e87ae,1354826179,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_subcomment,NA
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,"Slight tweak to the approach: it was easier not to back up to the outer node, but instead just inline-alienate the inner node.
+
+https://gerrit.wikimedia.org/r/37172",1354756947,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_subcomment,NA
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,"(In reply to comment #1)
+> This content would be in violation of the HTML spec, I believe.
+Yes. But Gabriel argues this is bound to occur in some cases anyway.
+
+Proposed approach: detect these cases (block node inside inline node or annotation node) without crashing, and handle them by backing out and alienating the outer node.",1354146377,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_subcomment,NA
+VisualEditor: Converter crashes if a page has a <span> element with a <p> elements,"This content would be in violation of the HTML spec, I believe.",1354124174,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vagtkpb7zm3ecw5cnsap,task_subcomment,NA
+VisualEditor: Still get a pawn when select-all->replace in Firefox,"Go to demos/ve/?page=aliens in Firefox; select all:
+
+  TypeError: end is undefined    ve.ce.Surface.js (line 980)
+
+Press ""a"" (or backspace and then ""a""):
+
+  TypeError: start is undefined  ve.ce.Surface.js (line 995)
+  
+  (And a pawn appears in its own <p> above the a.)
+
+On any click thereafter,
+
+  TypeError: node is null        ve.ce.Surface.js (line 1073)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57355",1353725160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j3shvug7fft7t4wshe6d,task_description,resolved
+VisualEditor: Still get a pawn when select-all->replace in Firefox,"I resolved this in Ia7347527e6466262e819f456404b32926fd95e34 by correcting the offsets before showing selection. This seems to work well so far, but really getNodeAndOffset is a nasty function that needs some love soon.",1353971144,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-j3shvug7fft7t4wshe6d,task_subcomment,NA
+"VisualEditor: Selective serialisation has landed in Parsoid, now VE needs to handle that","Due to gerrit 31118 being merged, Parsoid now has selective serialisation live. This means that VisualEditor needs to include Mark's patch to handle this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1353721680,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hgicqduvx6exq6mle75r,task_description,resolved
+"VisualEditor: Selective serialisation has landed in Parsoid, now VE needs to handle that",gerrit 35340,1353981072,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-hgicqduvx6exq6mle75r,task_subcomment,NA
+VisualEditor: Failure in saving integration code,"this.emit( 'saveError', null, 'Unsuccessful request: ' + data.result, null );
+
+(ve.init.mw.Target.js line 131)
+
+causes ""TypeError: data is undefined""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353719400,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-76qxn5mqf3hcvdkgf2kt,task_description,resolved
+VisualEditor: Failure in saving integration code,Fixed in gerrit 34959,1353724364,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-76qxn5mqf3hcvdkgf2kt,task_subcomment,NA
+VisualEditor: Clean up meta nodes,"For after December:
+* consolidate 'type': 'metaInline' / 'metaBlock' into 'type': 'meta'
+* get rid of ve.{ce,dm}.Meta{Inline,Block}Node
+* create ve.dm.MetaNode with converter stuff but don't inherit ve.dm.LeafNode
+** eventually integrate that into the new node API
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353702180,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-o3u5ojlmiw3bdf7dgyiu,task_description,resolved
+VisualEditor: Clean up meta nodes,This is fixed in gerrit 39847 which is now merged; will be deployed as part of the 2013-01-16 release cycle.,1357679596,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o3u5ojlmiw3bdf7dgyiu,task_subcomment,NA
+VisualEditor: Clean up meta nodes,"Turns out this could only be fixed partially. Consolidating metaBlock and metaInline was not possible and will have to wait until the node API rewrite, so I removed ce.Meta{Block,Inline}Node in https://gerrit.wikimedia.org/r/39847 and wrote up some ideas for the node API rewrite at https://www.mediawiki.org/wiki/User:Catrope/Node_API",1356175301,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-o3u5ojlmiw3bdf7dgyiu,task_subcomment,NA
+VisualEditor: Delete and backspace broken around inline aliens in Firefox,"When I place the cursor before the template output, and press ""Delete"", it deletes the template and one more character after the template. When I place the cursor after the template output and press ""Backspace"", it does not delete the template (simply does nothing).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353576600,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-75uqqg6zbs3w4jxdyn43,task_description,resolved
+VisualEditor: Delete and backspace broken around inline aliens in Firefox,Resolved in I73215df88519450965be35d9e04cf4e621d1e90d,1354149956,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-75uqqg6zbs3w4jxdyn43,task_subcomment,NA
+VisualEditor: Delete and backspace broken around inline aliens in Firefox,"Confirmed.
+
+Trivial test case: Start with an article with an inline alien - e.g. ""ABC<tt>:-)</tt>DEF"". Place the cursor immediately after C, and press (forwards) delete; instead of just deleting the alien, it also deletes D.
+
+Undo; place cursor immediately before D (just after the alien), and press backspace; instead of deleting the alien, it does nothing.
+
+Confirmed in Firefox.",1353718829,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-75uqqg6zbs3w4jxdyn43,task_subcomment,NA
+"VisualEditor: Link inspector suggestions box should instantly show, then populate with more as API returns","Right now the link inspector's suggestions box displays only after the ; instead, it should show instantly, then populate with more data as API returns with a spinner. Trevor has some ideas if you want to bug him. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353543420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-smsvykwx7lxu2tyag7ye,task_description,resolved
+"VisualEditor: Link inspector suggestions box should instantly show, then populate with more as API returns","Patched in https://gerrit.wikimedia.org/r/#/c/36110/1
+Awaiting merge.",1354231674,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-smsvykwx7lxu2tyag7ye,task_subcomment,NA
+VisualEditor: Annotation of inline nodes fails,"Annotation of inline nodes fails - the data model is not updated to have any annotations added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1353542940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jml4yae3q65u4srebbyl,task_description,resolved
+VisualEditor: Annotation of inline nodes fails,https://gerrit.wikimedia.org/r/#/c/34958/,1354054132,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-jml4yae3q65u4srebbyl,task_subcomment,NA
+VisualEditor: Handle percent-encoding in MWInternalLinkAnnotation,"Per conversation with Gabriel, MWInternalLinkAnnotation needs to deal with percent-encoded hrefs. At least question marks (?) and percent signs (%) will be encoded. We need to decode these before presenting them to the user, encode the user input on the way out, and use href shadowing to make sure we don't change the href if the user didn't change the target (even if that would otherwise happen due to complete vs partial percent-encoding).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353441780,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jazf6d7oefzddss6mv36,task_description,resolved
+VisualEditor: Handle percent-encoding in MWInternalLinkAnnotation,"It's resolved on our end, we have bug 41116 to track the other issues.",1354921807,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-jazf6d7oefzddss6mv36,task_subcomment,NA
+VisualEditor: Handle percent-encoding in MWInternalLinkAnnotation,"I5e1de9244d727641c10b6f0a89acc61afba7ecad will not actually fix the problem. I'm cleaning up our link serialization handler right now, which should also fix this issue.",1354916743,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jazf6d7oefzddss6mv36,task_subcomment,NA
+VisualEditor: Handle percent-encoding in MWInternalLinkAnnotation,If5d22e88904d6b2c438caac403ac2d78d440b017 resolves this issue. It's still dependent on bug 41116 (which has a patch that needs merging: I5e1de9244d727641c10b6f0a89acc61afba7ecad ),1354912585,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-jazf6d7oefzddss6mv36,task_subcomment,NA
+VisualEditor: Clicking link toolbar button with zero-length selection makes UI go crazy,"...presumably because the link becomes a pre-annotation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353376740,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-idkrdic2vphpfwclosyo,task_description,resolved
+VisualEditor: Clicking link toolbar button with zero-length selection makes UI go crazy,Fixed in I38995d4101fda71bfb2e6fe516603507ce820937 and Ibf6b26de299e54ae8688a2653bf5d5538927f8c3,1353971585,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-idkrdic2vphpfwclosyo,task_subcomment,NA
+VisualEditor: Clicking link toolbar button with zero-length selection makes UI go crazy,This was resolved in the recent inspector rewrite.,1353971422,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-idkrdic2vphpfwclosyo,task_subcomment,NA
+VisualEditor: Provide a way of users seeing the edit-notices and page protection level warnings as they're editing,"From Max's bug 42142
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42142",1353122280,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uxbnfma4ejiksnkp2e7x,task_description,resolved
+VisualEditor: Provide a way of users seeing the edit-notices and page protection level warnings as they're editing,Resolved in I581bf5a005a9c18422f952d71064d17d0ba9b540,1354317270,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-uxbnfma4ejiksnkp2e7x,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,"1. Go to https://www.mediawiki.org/wiki/VisualEditor:Testy and click edit
+2. Select all using Ctrl-A (or Cmd-A) and press backspace
+3. Press any content key (e.g. ""a"")
+
+What should happen:
+
+: You get a document with an ""a"" in its own paragraph.
+
+What does happen:
+
+: You get a document with an ""a"" in its own paragraph, and two console errors:
+
+TypeError: this.data[offset] is undefined
+
+...ation)===false){return null;}while(start>0){start--;if(this.offsetContainsAnnota...
+
+load.p...4105Z&* (line 89)
+
+
+TypeError: this.data[offset] is undefined
+
+...ation)===false){return null;}while(start>0){start--;if(this.offsetContainsAnnota...
+
+load.p...4105Z&* (line 89)
+
+
+Thereafter, pressing return in the new context gives:
+
+TypeError: node is null
+
+...ve.Node.call(this,type);this.model=model;this.$=$element||$('<div>');this.parent...
+
+Etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1353120840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_description,resolved
+VisualEditor: Trivial way to get a lot of errors,"Confirmed fixed, will be pushed live on Monday.",1353541840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,https://gerrit.wikimedia.org/r/#/c/34597/1,1353535425,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,"There were actually two cases, with two different root causes.
+
+If the last node in the document was not a paragraph, comment #2 applies: the document is empty and the pre-annotations code was asking for annotations at offset 0. This was fixed a while ago.
+
+If the last node in the document was a paragraph (this is common), the document wouldn't actually be emptied. Instead, all nodes would be removed except the last paragraph, which gets stripped. So after removing ""everything"", we are left with a document that only contains an empty paragraph. However, in the model tree, this empty paragraph is truly empty and does not contain a zero-length text node (most other empty paragraphs do have one).
+
+Once you type a character, CE pawns it first, processing a transaction that inserts a pawn in the paragraph. The transaction processor gets confused by the lack of any content nodes in the paragraph, and issues a rebuild for the contents of the paragraph, which fails spectacularly. The model tree ends up in an inconsistent state with a text node being a direct child of the document node and the paragraph node being gone. This then caused offset computations to be off by one, which caused other parts of CE to do strange things, culminating in an exception in openAnnotations(). When the exception occurs, the pawn hasn't been unpawned yet, so there's pawn leakage.
+
+Trevor has a commit queued up that will fix this.",1353530127,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,"After deleting all the content document if completely empty (data.length = 0),
+however view still askes what are the annotations at offset 0 - and that's what
+fails.
+Possible fix it to make method getAnnotationsFromOffset return empty set if
+given offset does not exists.",1353138590,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a lot of errors,%%%*** Bug 42218 has been marked as a duplicate of this bug. ***%%%,1353138404,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-vsfkgcc5kyalos6vc4gl,task_subcomment,NA
+VisualEditor: Trivial way to get a pawn (♙) appearing,"1. Go to https://www.mediawiki.org/wiki/VisualEditor:Testy and click edit
+2. Select all using Ctrl-A (or Cmd-A) and press backspace
+3. Press any content key (e.g. ""a"")
+
+What should happen:
+
+: You get a document with an ""a"" in its own paragraph.
+
+What does happen:
+
+: You get a document with an ""a"" in its own paragraph, and a pawn.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1353120720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6hldnmgl7xtnj7zwjyv,task_description,resolved
+VisualEditor: Trivial way to get a pawn (♙) appearing,"
+
+%%%*** This bug has been marked as a duplicate of bug 42219 ***%%%",1353138404,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-p6hldnmgl7xtnj7zwjyv,task_subcomment,NA
+VisualEditor: Inserting text content around inline alien nodes throws an exception,"Specifically it fails when trying to insert text content between two inline aliens or after last inline alien inside its parent.
+
+Exception:
+Uncaught TypeError: Cannot read property 'start' of undefined ve.dm.TransactionProcessor.js:259
+ve.dm.TransactionProcessor.processors.replace
+
+// Set change markers on the parents of the affected nodes
+for ( i = 0; i < selection.length; i++ ) {
+	this.setChangeMarker(
+		selection[i].parentOuterRange.start + this.adjustment,
+		'content'
+	);
+}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353106740,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-murhom53ypttvsazncwz,task_description,resolved
+VisualEditor: Inserting text content around inline alien nodes throws an exception,https://gerrit.wikimedia.org/r/34224,1353366778,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-murhom53ypttvsazncwz,task_subcomment,NA
+VisualEditor: Inserting text content around inline alien nodes throws an exception,It also happens when inserting text content before inline alien if that alien is a first child of its parent.,1353137908,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-murhom53ypttvsazncwz,task_subcomment,NA
+"VisualEditor: Sync availability of ""minor edit"" with MW backend","Currently when using VisualEditor to create a new page, the ""Save page"" dialog box offers two checkboxes below the edit summary field: ""This is a minor edit"" and ""Watch this page"".
+
+When creating a page, ""This is a minor edit"" does not typically show up. It's a bug that the checkbox appears when creating a page with the VisualEditor interface.
+
+This bug is closely related to bug 40774.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1352957280,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cougiswjchh3cn6khldz,task_description,resolved
+"VisualEditor: Sync availability of ""minor edit"" with MW backend",Code now live in master; will get deployed in the next cycle.,1354565365,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cougiswjchh3cn6khldz,task_subcomment,NA
+"VisualEditor: Sync availability of ""minor edit"" with MW backend",Change-Id: I9c659845feebb3e9bbf8e13ee67be27c6adb4321,1354426566,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cougiswjchh3cn6khldz,task_subcomment,NA
+"VisualEditor: Sync availability of ""minor edit"" with MW backend","The EditPage backends has this logic in three places:
+
+* Getting html of checkboxes (only if user has minoredit right and if not on a  new page)
+* Setting initial values of checkboxes (if user has minordefault preference)
+* Processing the save action with the minoredit flag (only if has user right and not on a new page)",1354418381,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cougiswjchh3cn6khldz,task_subcomment,NA
+VisualEditor: Floated nodes don't get shields in Chrome,"If you have a floated table inside an alien, it gets a shield (and a phantom) in Firefox but not in Chrome. This is because the table is floated with external CSS triggered by class=""infobox"", rather than an inline style attribute. At the time when we check for $this.css('float'), $this hasn't been attached to the main DOM yet. Firefox computes styles on unattached nodes correctly, but Chrome doesn't.
+
+The solution is to wait until after the entire CE rendering has been built and attached to the DOM before generating shields and phantoms. Possible implementations:
+
+1. Add an onAttach function to ce.Node. After attaching, traverse the entire CE tree and invoke onAttach() on every node (bottom up). This is expensive, though, because you have to traverse the entire tree just to invoke onAttach on the few nodes that use it.
+
+2. Make the ce.Surface throw an 'attached' event after attaching to the DOM, and make the ce.AlienBlockNode constructor listen for this event. This is not as clean, but more efficient, because only nodes that need processing are processed.
+
+I have a slight preference for #2, but I can be convinced either way.
+
+In both cases, the call to onUpdate() in the ce.AlienBlockNode constructor would be removed, otherwise the HTML would be set twice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352948940,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-oxmalsbaodappytqtaoo,task_description,resolved
+VisualEditor: Floated nodes don't get shields in Chrome,Fixed here: https://gerrit.wikimedia.org/r/#/c/33661/,1353018780,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-oxmalsbaodappytqtaoo,task_subcomment,NA
+VisualEditor: Spinner keeps spinning after save fail,"If you try to save a page and it fails (e.g. because of an edit conflict, blocked user, Parsoid down, or whatever), then click Cancel, the spinner keeps spinning and the Save page button remains greyed out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352940660,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-kk4vhnmofck2qdxtjn2o,task_description,resolved
+VisualEditor: Spinner keeps spinning after save fail,"
+
+*** This bug has been marked as a duplicate of bug 37837 ***",1354054812,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-kk4vhnmofck2qdxtjn2o,task_subcomment,NA
+VisualEditor: Paragraph generated for an empty document should not be unwrapped on the way out,"Currently, the DOM->data converter generates an empty paragraph if the input is an empty string. This paragraph is marked with .internal.generated=='wrapper', so it's unwrapped on the way out. This is bad because we lose change markers that way, and have no way to propagate them.
+
+Instead, it should use another generated marker which causes the paragraph to be unwrapped only if it is empty, and be preserved if it's not empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352938920,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lag2eyarvgkricqxqmeh,task_description,resolved
+VisualEditor: Paragraph generated for an empty document should not be unwrapped on the way out,*** Bug 41905 has been marked as a duplicate of this bug. ***,1353133977,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lag2eyarvgkricqxqmeh,task_subcomment,NA
+VisualEditor: Paragraph generated for an empty document should not be unwrapped on the way out,https://gerrit.wikimedia.org/r/33854,1353123761,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lag2eyarvgkricqxqmeh,task_subcomment,NA
+VisualEditor: Converter should inline-alienate inline tags in wrapping mode even in the mw:unrecognized case,"Normally, unrecognized tags in wrapped blocks are alienated as inline or block depending on the tag name. This is broken for tags with unrecognized mw: types (and for about groups), which are always alienated as block when in wrapping mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352938680,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hfb6u2us7tcoc2xke4cf,task_description,resolved
+VisualEditor: Converter should inline-alienate inline tags in wrapping mode even in the mw:unrecognized case,https://gerrit.wikimedia.org/r/34261,1353386649,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hfb6u2us7tcoc2xke4cf,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg","When loading a page with VE enabled, the ""edit"" tab is changed from the ""vector-view-edit"" message to the ""edit"" message. This is apparent on enwiki, where these messages have different values. It's also apparent when using ?uselang=qqx
+
+This shouldn't happen, the message for the edit tab should be consistent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1352937420,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_description,resolved
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg",Now merged.,1365036328,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg","Rephrased summary.
+
+The problem is that different skins use a different message for the Edit button. Vector uses msg key ""vector-view-edit"". Monobook (and most other skins) use msg key ""edit"".
+
+By default the messages are equal but on en.wikipedia.org, as example, classic msg ""edit"" has been changed to contain ""Edit this page"".
+
+This lead to the tab replacement causing a weird change from ""Edit"" to ""Edit this page"" when in VE mode.",1365027641,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg",Change-Id: I2e7dd85cd14049101e2d49751d37797d77bc7c9d,1365027456,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg","De-prioritising for December; instead, bug 42221 will take on this need, as discussed with Trevor and Roan.",1353122866,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+"VisualEditor: Replaced Edit tab should use original label instead of fetching message ""edit"" msg","Problem is in ViewPageTarget, which assumes that the name of the action and the action's label are the same ('edit' or 'create') or something, per hurried conversation with Trevor. :-)
+
+More widely, we might want our own label for this at first anyway to make it clear which editor people are using during the initial integration - just call it ""VisualEditor"" and leave the other tab visible next to it?",1353017565,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5jn5rxhygbvz6pzdt2uo,task_subcomment,NA
+VisualEditor: Change marking branch appears to be live on MWwiki,"Possibly the wrong version of Parsoid updated? See https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=next&oldid=604180 as an example of '<p data-ve-changed=""[...]"">' elements being created.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352858220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jh7jzzemygqrgcfg25dq,task_description,resolved
+VisualEditor: Change marking branch appears to be live on MWwiki,Fixed in https://gerrit.wikimedia.org/r/#/c/33410/,1352939134,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-jh7jzzemygqrgcfg25dq,task_subcomment,NA
+VisualEditor: A wild pawn character appeared!,"Roan told me that, if I ever saw one of your comical placeholder Unicode characters, that it was a pretty well-defined bug. So here:
+
+1. Create an unordered list
+2. Enter some items
+3. Hit enter twice
+4. Type something
+
+Expected: Whatever I typed should appear on the screen.
+
+Actual: Pawn character! It also prints my text, but only after '♙\n'.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352856780,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-az3twbgyfogcznpnnndd,task_description,declined
+VisualEditor: A wild pawn character appeared!,"**orbit** wrote:
+
+This must've been something that was fixed as part of some other work. I'm unable to reproduce.",1354656971,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-az3twbgyfogcznpnnndd,task_subcomment,NA
+VisualEditor: A wild pawn character appeared!,"Potentially deeper meaning: The list-creation code is really buggy and needs to be fixed. I can't seem to *end* an unordered list, once I create it.",1352857130,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-az3twbgyfogcznpnnndd,task_subcomment,NA
+"VisualEditor: In bullet list, SHIFT-LEFT selection reseted when reaching deeper item","Steps to reproduce:
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press ""Edit""
+3) Click at the end of an item in the big list at the bottom of the page.
+4) Press SHIFT and LEFT, maintaining them pressed for a while
+
+Expected behavior: Text is selected as long as SHIFT-LEFT is pressed
+Actual behavior: Text is selected until deeper-level bullet is reached. When it is reached, the previous selection is unselected, and a new selection starts.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351564200,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-qacmwzmv3ujwgmodf5y7,task_description,resolved
+"VisualEditor: In bullet list, SHIFT-LEFT selection reseted when reaching deeper item",Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306610,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qacmwzmv3ujwgmodf5y7,task_subcomment,NA
+"VisualEditor: In bullet list, SHIFT-LEFT selection reseted when reaching deeper item",Resolved in Iba55cfc3d531e7d1333b78c94912ff22179aace8,1354222673,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-qacmwzmv3ujwgmodf5y7,task_subcomment,NA
+"VisualEditor: In bullet list, SHIFT-LEFT selection reseted when reaching deeper item",Confirmed in Firefox and Chrome.,1351565870,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qacmwzmv3ujwgmodf5y7,task_subcomment,NA
+VisualEditor: ve.ce throws Uncaught TypeError: Cannot read property 'nodeType' when suface loses focus,"In Chrome, when I click inside the editor, then right-click outside the editor, I get an exception:
+
+
+Uncaught TypeError: Cannot read property 'nodeType' of null /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:118
+ve.ce.getOffset /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:118
+ve.ce.SurfaceObserver.poll /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:135
+ve.ce.SurfaceObserver.stop /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:81
+ve.ce.Surface.documentOnBlur /w/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js:322
+proxy l.php:775
+jQuery.event.dispatch l.php:3063
+elemData.handle.eventHandle l.php:2681
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351539120,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-f2x5ytlsmyx24xetmj5s,task_description,resolved
+VisualEditor: ve.ce throws Uncaught TypeError: Cannot read property 'nodeType' when suface loses focus,Fixed in gerrit 36687.,1354581344,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f2x5ytlsmyx24xetmj5s,task_subcomment,NA
+VisualEditor: ve.ce throws Uncaught TypeError: Cannot read property 'nodeType' when suface loses focus,*** Bug 42525 has been marked as a duplicate of this bug. ***,1354155569,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f2x5ytlsmyx24xetmj5s,task_subcomment,NA
+VisualEditor: ve.ce throws Uncaught TypeError: Cannot read property 'nodeType' when suface loses focus,"Confirm issue in Chrome, Safari; not in Firefox.",1351541465,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f2x5ytlsmyx24xetmj5s,task_subcomment,NA
+VisualEditor: Clicking inside an alien node throws an TypeError,"Uncaught TypeError: Cannot call method 'getModel' of undefined ve.ce.js:208
+ve.ce.getOffsetFromElementNode ve.ce.js:208
+ve.ce.getOffset ve.ce.js:121
+ve.ce.SurfaceObserver.poll ve.ce.SurfaceObserver.js:135
+ve.ce.SurfaceObserver.start ve.ce.SurfaceObserver.js:66
+ve.ce.Surface.onMouseUp ve.ce.Surface.js:352
+proxy jquery.js:775
+jQuery.event.dispatch jquery.js:3063
+elemData.handle.eventHandle
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1351536660,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-hrsow4jckaq52vpprzud,task_description,resolved
+VisualEditor: Clicking inside an alien node throws an TypeError,Assigning this to a release milestone so it's clear when at the latest to expect it to have been fixed; it may have been fixed beforehand.,1354306603,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hrsow4jckaq52vpprzud,task_subcomment,NA
+VisualEditor: Clicking inside an alien node throws an TypeError,This has been resolved.,1354222915,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-hrsow4jckaq52vpprzud,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","We have this dude in the Vector skin next to the user name:
+
+{F26476317,size=full,layout=inline} http://bits.wikimedia.org/static-1.21wmf2/skins/vector/images/user-icon.png
+
+If one specifies their gender in preferences as female, it would be cool to see a female user icon instead of the dude. :)  If we're interested in gender gap, this could be one tiny thing to help make the software more welcoming.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45056
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51927
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53732",1351487760,PHID-USER-lzhljhpbm3qfphvqyill,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_description,resolved
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**Jason_quinn** wrote:
+
+Postscript:
+
+Blue is for boys. Pink is for girls. Yellow or green are neutral.
+
+This is a cultural convention for gender through the Western world and much of the rest of the World, especially for example in nurseries, and has been for the better part of a century. This is *why* many here associate blue with male. If you are from the Western world and don't have at least some mental association about that, you're an oddity. The suggestion of ""red"" rather than ""pink"" to denote female is puzzling. (In fact, the red icon suggested above for female and the old icon's blue color are clearly similar to the red and blue used for instance by Olympic boxers.) It is also puzzling why ""yellow"" or ""green"" weren't mentioned as possible general neutral colors.
+
+I'm not saying that this color convention (or any color convention) should be used for the icon. There would be many issues to discuss about it. Some people might object saying it re-enforces gender stereotypes and so on. There may be countries where the conventions are totally different (I'm unaware of any but this same issue came up when color-coding Asian family tree charts in the encyclopedia and nobody has yet complained). All I am saying is that it wasn't clear to me from the above discussion that anybody even was even consciously aware of the convention so it needed to be mentioned explicitly. Getting rid of the icon altogether may be the best course of action anyhow so this might be moot except to better understand the issue.
+
+Regardless, it was a fantastic suggestion that the icon should not have an indefinable skin color. Bravo on that.",1411440166,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Change 157990 merged by jenkins-bot:
+Make profile icon gender neutral and remove from login link in Vector
+
+https://gerrit.wikimedia.org/r/157990",1410560713,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Change 146979 abandoned by Robmoen:
+Make profile icon gender neutral and remove from login link in Vector
+
+Reason:
+Abandoned in favor of new patch in skins directory.
+https://gerrit.wikimedia.org/r/#/c/157990/
+
+https://gerrit.wikimedia.org/r/146979",1409694538,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Change 157990 had a related patch set uploaded by Robmoen:
+Make profile icon gender neutral and remove from login link in Vector
+
+https://gerrit.wikimedia.org/r/157990",1409694478,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","While we wait for screenshots here, I've loaded the icon at its default size of 13px and out of context I would have called it a sunset over a hill. I guess that *is* gender neutral, no idea how clear it is.
+
+See also bug 45056 comment 15.",1405584342,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Change 146979 had a related patch set uploaded by Robmoen:
+Make profile icon gender neutral.  Remove from Login link
+
+https://gerrit.wikimedia.org/r/146979",1405552771,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**wmf.amgine3691** wrote:
+
+This idea has already been discussed in this bug (starting around comment 9, 17) and was discussed in other bugs (35341) and has its own bug (45056).",1405106440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**swalling** wrote:
+
+(In reply to Nemo from comment #57)
+> The problem in this bug is very well defined and it has nothing to do with
+> your proposed solution. Your proposal is a solution for the supposed problem
+> ""personal toolbar personalises"", which is a) different, b) not agreed upon
+> as a problem. It's possible that the two problems will be resolved by a
+> single solution in the end, but collapsing them in a single report doesn't
+> help anything.
+
+When a problem comes up with a current design (whether it's an icon, a button, or a whole feature), it is extremely useful to go back to basic principles and talk about why something is needed in the first place. Questioning whether a design element is necessary hones in on why it's important. If we understand why it's important, then if we want to keep it, we can be clearer about what it's supposed to be doing. 
+
+TL;DR: all options are on the table. If you don't like it, we can always go discuss this on the more open-ended bug I filed. But berating a designer for having ideas is not progress.",1405099573,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I don't know what ""personal toolbar personalises"" means, can you explain/clarify?",1405099452,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","The problem in this bug is very well defined and it has nothing to do with your proposed solution. Your proposal is a solution for the supposed problem ""personal toolbar personalises"", which is a) different, b) not agreed upon as a problem. It's possible that the two problems will be resolved by a single solution in the end, but collapsing them in a single report doesn't help anything.",1405098958,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Nemo, bugs shouldn't neccesarily express a solution, the problem here is ""icon represents gender"" it's easy to assume the fix is ""make a better icon"" when the problem could just as easily be ""don't have an icon"" when we presuppose a solution we close ourselves off to many possible correct conclusions for the same issue. 
+
+Pre- and post- login icons are currently the same asset by the way, to answer your question.",1405097844,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","What is the pre-login or post-login icon? Jared, please file a separate bug report for separate issues. This bug is not about removing the icon.",1405075490,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Created attachment 15907
+post login
+
+see post login sketch
+
+- icon removed
+- additional per item padding added
+- right margin adjusted to align with search.
+
+**Attached**: {F9746}",1405057269,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I propose we remove the post-login icon for now, and when wikifont is in core we can add the updated icon then. We have personal bar instrumented right now, so we'll be able to see if there is any dropoff from users based on the removed icon.",1405056730,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**swalling** wrote:
+
+(In reply to Jared Zimmerman (WMF) from comment #51)
+> Created attachment 15906 [details]
+> no icon -> mediawiki.ui controls
+> 
+> How about for now we just remove the icon altogether, pre-login we should
+> use medaiwiki.ui controls, and post login, just remove the existing icon.
+
+I think this is the right way to go for login. 
+
+Not sure about removing the icon for once you're logged in. It does provide value, in that it denotes that the menu items are related to you personally. I think if we try something simpler (the version May did pushed things a bit in terms of personality and verve) then we can easily replace it. Munaf is working on something in conjunction with our designs for a task suggestions alpha.
+
+**Attached**: {F9744}",1405056372,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Created attachment 15906
+no icon -> mediawiki.ui controls
+
+How about for now we just remove the icon altogether, pre-login we should use medaiwiki.ui controls, and post login, just remove the existing icon.
+
+**Attached**: {F9744}",1405056147,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel",*** Bug 67837 has been marked as a duplicate of this bug. ***,1405052255,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Hi RituS! Actually I don't think this bug at this point is the best first task for a new contributor. We have many other bugs to choose from at 
+
+https://www.mediawiki.org/wiki/Annoying_little_bugs
+
+The reason is...
+
+(In reply to comment #39)
+> Removing easy keyword; the implementation may be easy, but as we still
+> haven't 
+> agreed on what to do with this, it's probably not something we'd necessarily
+> want to bring a new person into.
+
+I agree. Have we agreed on a plan? If so, a new comment summarizing the work that needs to be done is welcome. With 48 comments and 5 attachments, the chances to work on something that won't be directly merged are high.",1386775181,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Hi RituS, thanks for your interest! Please see https://www.mediawiki.org/wiki/Developer_access and https://www.mediawiki.org/wiki/Gerrit/Tutorial for information and also for where to receive help with the general development setup.",1386769884,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**ritusparks** wrote:
+
+Hey!
+I'm a newbie to mediawiki and I would like to work on this bug! Could somebody navigate me through the required procedure?",1386766074,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #40)
+> 
+> As you point out, it should likely be anthropomorphic. Blue is used for
+> accent in the skin, but every icon and graphic is monochromatic grey
+> (http://ur1.ca/fx8u3, search) - as should be this one.
+
+Good point - I must have been thinking of some extension icons I'd seen that were link-coloured.
+
+(In reply to comment #44)
+> Created attachment 13548 [details]
+> Profile icon
+
+As I said, an icon like that defeats the purpose of having a user icon in the first place, as it is not immediately recognisable as 'user account' related and thus does not adequately function as a graphical label for the personal tools. Indeed, that it is so similar to the echo thanks thing should help explain why it isn't appropriate here.
+
+The one Munaf made or one of the ones thehelpfulone linked would be much more appropriate and effective. May need to fix the colours/weight for the skin, but that is the direction this should be taking. Or rather that it should never have left.
+
+//attachment profile.svg ignored as obsolete//",1382493376,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #43)
+> Created attachment 13547 [details]
+> Example use of icon
+
+I want to say that I appreciate all of the work that the design team does. Good design on our projects and in our products is important. A rich, meaningful, and aesthetically pleasing user experience is something that every user who visits our sites or uses our services should have.
+
+That said, sweet Jesus no, we will not be putting that icon anywhere near MediaWiki core or Wikimedia wikis. It conjures up [[blackface]] in the mind and will be viewed by many users to be offensive and completely inappropriate. This icon flatly will not work.
+
+In seeing another squared-headed smiley face in the wrong color, I'm reminded of bug 51927. (Oh, it's already marked as a ""see also."" Hrm.)
+
+//attachment Screenshot 2013-10-22 16.06.53.png ignored as obsolete//",1382492283,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Profile icon
+
+//attachment profile.svg ignored as obsolete//",1382486305,PHID-USER-tjeabpzbwsqw3xciydvb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Example use of icon
+
+//attachment Screenshot 2013-10-22 16.06.53.png ignored as obsolete//",1382486273,PHID-USER-tjeabpzbwsqw3xciydvb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Realized the asset uploaded was slightly out of date, May is uploading the correct asset and mockup now. 
+
+I feel that the asset she's uploading (a variation on the original she posted) head and shoulders (ha!) better than what we have now. its a small change, I'd prefer to integrate it, since its in-line with the user icon on mobile as well as upcoming multi-media features. Stay tuned for the updated asset in just a bit.",1382481068,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**wmf.amgine3691** wrote:
+
+Hmmph. https://bits.wikimedia.org/static-1.22wmf21/extensions/UniversalLanguageSelector/resources/images/cog-sprite.svg?2013-10-10T16:45:00Z works just fine... <grumbles>",1382480808,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**wmf.amgine3691** wrote:
+
+(In reply to comment #39)
+...
+> It seems rather like we're stuck on a choice - whether to be intuitive and
+> clear or to not offend people. Strange choice, since no matter what you do
+> you'll pretty much always wind up offending or disturbing someone if you've a
+> broad enough audience.
+
+Nonsense.
+
+As you point out, it should likely be anthropomorphic. Blue is used for accent in the skin, but every icon and graphic is monochromatic grey (http://ur1.ca/fx8u3, search) - as should be this one.
+
+Aesthetically not the best choice for some people, but it's likely the least offending (even to the designers) compromise and we're all just waiting for someone to point this out and force the stakeholders to grow up and accept the compromise.",1382480582,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Removing easy keyword; the implementation may be easy, but as we still haven't agreed on what to do with this, it's probably not something we'd necessarily want to bring a new person into.
+
+There are arguments here that an icon is not needed at all, but based on what Trevor said, even if it isn't needed, it's definitely useful. To remain useful, however, it needs to also remain a recognisable 'user' icon - that rules out anything with too much abstraction that wouldn't necessarily have the same meaning to the user, like a smiley face or animal (even without added issues those might present such as those Siddhartha Ghai points out), and brings us back to the more standard head and shoulders, which arguably tend to look male. Blue, which fits the skin, is apparently also problematic because in some cultures blue is associated with masculinity.
+
+It seems rather like we're stuck on a choice - whether to be intuitive and clear or to not offend people. Strange choice, since no matter what you do you'll pretty much always wind up offending or disturbing someone if you've a broad enough audience.",1382479349,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #28)
+> Another design practice that I'm a fan of is to go with more abstract user
+> icons or animal icons e.g. github's
+> https://dribbble.s3.amazonaws.com/users/8063/screenshots/873671/
+> github_icon_vector_shape_teaser.png
+
+I'd just like to point out that animal icons would not be wise since languages may associate certain animals with certain genders by default. For example, a user with native language hindi might consider a cat icon to be female and a lion to be male. Cat: male: बिल्ला, female: बिल्ली, latter is what is generally default usage. Lion invokes a male idea since hindi, like English, defaults to lion (शेर), not lioness (शेरनी)",1380860683,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Can we get someone to integrate this, we've recently updated the general user icon used in mobile for user talk, article history, and watchlist, so it would be great to get this one in sync sooner rather than later.",1380748396,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Removed May (visual designer) as the assignee, not that she's uploaded the new asset from the Echo icon set. Please assign a developer to submit a patch as needed.",1375220836,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Profile icon
+
+//attachment User_web.svg ignored as obsolete//",1375121322,PHID-USER-tjeabpzbwsqw3xciydvb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Thanks Jared; please leave correct terminology too in the bug summaries for the purposes of discoverability (the area is called ""personal tools"").",1372369546,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel",We'll address this icon as part of a a visual alignment exercise we're doing with the echo notifications,1372368686,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #5)
+> (In reply to comment #3)
+> > Thanks for pointing this out, Aude.  For ideas on how to rework the default
+> > icon to make it more gender-neutral, here's the ""gallery of default
+> > anonymity"":
+> > http://www.murketing.com/journal/?p=3098
+> 
+> Flickr is IMHO the best.
+
+BTW, apparently Flickr disagreed :) , they replaced the default buddy icon with a purple square containing a rainbow camera.",1369728557,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**Thehelpfulonewiki** wrote:
+
+What about https://commons.wikimedia.org/wiki/File:Gnome-stock_person.svg or https://commons.wikimedia.org/wiki/File:Crystal_Clear_app_personal_gray.png (I prefer the former).",1366938313,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Looks like it wasn't linked yet: monobook icon on Commons, ""Racially, gender neutral icon"". https://commons.wikimedia.org/wiki/File:User-variant.png
+
+(In reply to comment #29)
+> I say we keep it, and when we make all the other icons monochrome (going
+> along
+> with work like Agora and VisualEditor) it should become a silhouette.
+
+I don't understand, are you saying it can't be changed before that for some reason of consistency? Also, does ""silhouette"" mean that in
+
+(In reply to comment #28)
+> abstract
+> head + shoulders or an abstract face in b&w.
+
+you recommend the former?",1363515550,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Just adding my 2 cents in here.
+
+The icon was chosen, by me, in 2009. It was the standard generic user icon in the Tango icon library, which we were embracing at the time.
+
+I agree with some of comments here that using stereotypes to make the icon more gender specific is going to be offensive. Should we also assume their nationality based on their location or language and adjust the icon accordingly? Obviously this is going to be a nightmare. Besides, none of this would any value.
+
+The use of the icon was inherited from Monobook. As many people are aware, Vector was more of a riff on Monobook than a new skin. At the time especially, Monobook had become this iconic skin that everyone was so attached to after years of staring at it, that every tiny adjustment we proposed was highly controversial.
+
+Do we still need the icon? I think so. It's actually one of the more reasonable uses of iconography - which we use very selectively in Vector - because it is...
+
+1. Identifiable (must be obvious what it means)
+2. Necessary (icons for the sake of icons are bad)
+3. Important (icons for obscure tasks bring attention to the wrong things)
+
+I say we keep it, and when we make all the other icons monochrome (going along with work like Agora and VisualEditor) it should become a silhouette.",1361994999,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**sumanah** wrote:
+
+symbolic variant from gnome-icon-theme courtesy Mizmo (Máirín Duffy of Red Hat)
+
+I asked a few other designers who work in open source to comment.  Georgia Bullen wrote:
+
+""Hmmm...
+
+Well there are the options of just stick figure gender-less icons e.g.
+http://wikieducator.org/images/1/16/Dummy_user.png and if you avoided
+colors, and went with gray or something like that then it wouldn't even
+have gender color implications.
+
+Another design practice that I'm a fan of is to go with more abstract user
+icons or animal icons e.g. github's
+https://dribbble.s3.amazonaws.com/users/8063/screenshots/873671/github_icon_vector_shape_teaser.png
+
+Or this awesome site: https://diy.org/ which uses animal avatars to avoid
+issues with COPA for children.
+
+Hope that's helpful!
+
+-georgia""
+
+
+Máirín Duffy of Red Hat wrote:
+
+""The best gender- and race-neutral icons of people are basically abstract
+head + shoulders or an abstract face in b&w. One of the links you posted
+in the bug had a few good examples:
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/garageband.gif
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/myspacenophoto.jpg
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/nopic_192.gif
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/vimeo.jpg
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/identica.png
+
+http://www.murketing.com/journal/wp-content/uploads/2009/04/npr.gif
+
+FWIW the icon you guys are using now is one of the old gnome-icon-theme
+icons. I am attaching a copy of the same icon from the newer
+gnome-icon-theme, symbolic variant - it's licensed GPL, I've pasted the
+link with license details below:
+
+http://git.gnome.org/browse/gnome-icon-theme/tree/COPYING
+
+You may of course feel free to use it!
+
+~m""
+
+//attachment avatar-default-symbolic.svg ignored as obsolete//",1361566851,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**sumanah** wrote:
+
+(In reply to comment #24)
+
+> Speaking on this issue, I think we should avoid any kind of gender cues in
+> the
+> icon. The concept of ""gender"" is intensely personal, mercurial, and
+> ephemeral.
+
+I completely get what you're saying here (and nudge you to potentially undo the WONTFIX on Bug 25834 to expand the currently binary gender options MediaWiki preferences offer users).  But is it really possible to avoid *any* gender cues in an icon given that ""male"" is, to the perception of most users, the default state of any head-and-shoulders icon unless it includes specific ""not male"" markers?  Defeating the unmarked state is tough.
+
+> This bug actually points to a larger issue that we have within the software
+> itself (which is that gender is a binary switch, rather than something that
+> accommodates individuals who identify as ""genderqueer"").
+
+> (And yes, I know that namespace translations for user pages based on gender
+> is
+> a whole other ball of wax, and I can't hope to think we'll ever solve for
+> gender-identification problems that are fundamental to a language itself).
+
+Solve entirely?  No.  *Improve* how we deal with genderqueer people in all languages?  Sure.
+
+People opining on this bug ought to also look at Bug 30442 - give the user a chance to specify the gender when opening the account - and Bug 31816 - Improve the wording of gender selection option.
+
+> As far as the icon itself goes, I would prefer that we also would move
+> towards
+> an image that is also racially neutral (thus, Munaf's grey icon is probably
+> the
+> best choice).
+
+Seconding the request for the icon's ""skin color"" to be neutral. :-)",1361014746,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I don't necessarily think I need to address them; my position is that the icon isn't needed at all and I think it distracts as clutter rather than providing a visual cue.
+
+However, I'm not married to killing it off, and if people decide that we want to keep it, I'm fine with that, but I also want to make sure that we're working inside some rational guidelines.",1360986464,PHID-USER-ua75tm4u7cmt4mdof6vb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Brandon, thanks for adding your points about older comments, but I hope you can also address comment 20, comment 23 and bug 45056 comment 6: instead of explaining your position you just restated it in a post-scriptum. Thanks.",1360985671,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #4)
+
+> How do you make a ""female"" icon anyway, short of giving it breasts? Long
+> hair?
+> Tell that to Brandon and Sumana!
+
+Are you suggesting that I could be mistaken for a woman? ;)
+
+Speaking on this issue, I think we should avoid any kind of gender cues in the icon. The concept of ""gender"" is intensely personal, mercurial, and ephemeral. This bug actually points to a larger issue that we have within the software itself (which is that gender is a binary switch, rather than something that accommodates individuals who identify as ""genderqueer"").
+
+(And yes, I know that namespace translations for user pages based on gender is a whole other ball of wax, and I can't hope to think we'll ever solve for gender-identification problems that are fundamental to a language itself).
+
+As far as the icon itself goes, I would prefer that we also would move towards an image that is also racially neutral (thus, Munaf's grey icon is probably the best choice).
+
+That said, I still want to get rid of the icon entirely.",1360985052,PHID-USER-ua75tm4u7cmt4mdof6vb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**massaf** wrote:
+
+
+> But why did you change the color of userpage link in that mockup?
+> This just distracts from the purpose of the change :/
+
+Unintentional. I habitually plugged in Agora red (#cc0000) instead of our current link red (#ba0000) so there's a weird differential.
+
+> Actually I'm starting to lean towards just killing the icon per bug 45056.
+
+Not sure I'm convinced of that yet. Just one icon does make the user tool list more scannable (ideally they'd be re-arranged or redesigned altogether).",1360984917,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I agree with the three comments above (as said on bug 45056). Finding a better icon doesn't seem that hard, and we're not in a hurry: the current one is not doing any severe harm, it's just imperfect (and in monobook probably even good enough).",1360983710,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel",Agora doesn't really work with Vector.,1360981328,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I kind of find the icon to be a sort of visual cue. Without it the personal bar is just a collection of unidentified links. While with the icon it's instantly identified as a series of links related to the user.
+
+Stuff like proper padding and lining up of whitespace are invisible when they are present and done right. But when they are not there they give uncomfortable feelings, usability issues, etc... I think the personal icon fits into that category.
+
+Why don't we try Agora-fying the icon?
+https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_Icon_Set",1360977067,PHID-USER-gibrlx54k2riiuit5paf,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Two things: One, that is not a male icon. Blue does not make it male. Blue matches the skin, and I really don't understand why there is a fuss about that in particular. Two, killing the icon entirely would make sense with current skins especially since it has no functional significance anyway.
+
+GRAW. Arg. Chickidee?",1360972762,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #17)
+> Personally, I say kill the icon.  It's the only one we have, and it stands
+> out because of it.  Maybe we revisit them in the future, but for now I don't
+> see a purpose.
+
+We may one day have an avatar up there (similar to Facebook). Definitely something to think about for [[mw:GlobalProfile]]. For now, I think you're probably right that no icon is better than the current icon.",1360971005,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Personally, I say kill the icon.  It's the only one we have, and it stands out because of it.  Maybe we revisit them in the future, but for now I don't see a purpose.",1360970770,PHID-USER-ua75tm4u7cmt4mdof6vb,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #14)
+> Created attachment 11794 [details]
+> testing out a gender-neutral icon
+> 
+> Not sure I see what you're seeing. It fits fine when you scale and color it
+> based on context. 
+
+Okay, it's considerably better when appropriately colored (but still looks like a pawn). But why did you change the color of userpage link in that mockup? This just distracts from the purpose of the change :/
+
+Actually I'm starting to lean towards just killing the icon per bug 45056.
+
+//attachment gender-icon-test.png ignored as obsolete//",1360967877,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #9)
+> Killing this icon was briefly proposed at bug 35341.
+
+Filed separately as bug 45056.",1360967497,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**massaf** wrote:
+
+testing out a gender-neutral icon
+
+Not sure I see what you're seeing. It fits fine when you scale and color it based on context. 
+
+A shade of gray would work if each user portlet item had an icon alongside it, which we're talking about in other bugs.
+
+//attachment gender-icon-test.png ignored as obsolete//",1360965592,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","So, I don't want to be a buzzkill and mean, but Munaf, have you actually tried putting that icon into the interface?
+
+Because it looks awful. It doesn't fit the rest of the skin and hardly resembles a human, especially scaled-down. Maybe it would be a little better if made blue-ish, but I'm still skeptical about the new look.",1360955260,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**massaf** wrote:
+
+an attempt at a gender-neutral icon
+
+Here's a first attempt. I agree with Krinkle that it shouldn't draw attention. Link blue (#3366bb) might be appropriate, but for now it's gray. Thoughts?
+
+//attachment GenderNeutralPerson.png ignored as obsolete//",1360954184,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Well, as Sumana notes, the current icon can be perceived as conforming to some gender stereotypes, so it's not ""neutral"" in its common perception. I've clarified the summary further.",1360949789,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I agree with Krinkle.  I don't see what makes this icon (https://bits.wikimedia.org/static-1.21wmf9/skins/vector/images/user-icon.png) male.  I don't think a blue shirt makes it male.
+
+As he said, Vector uses a lot of blue.  In particular, light blue.  We could change the shirt color to light blue to make it further match the theme, but I don't know that this is really necessary.",1360947541,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel",Killing this icon was briefly proposed at bug 35341.,1360946866,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #6)
+> I ask our designers to figure out how to make a more gender-neutral icon
+> (perhaps dispensing with the requirement that it look like a person).
+
+Species-neutral too, I like it :)",1360945647,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","Sorry for double comment.
+
+(In reply to comment #5)
+> Flickr is IMHO the best. Should also be {{PD-ineligible}} and in compliance
+> with the colour scheme per Krinkle above.
+
+(Same for Yahoo and identi.ca, very similar.)
+
+(In reply to comment #6)
+> The current icon is
+> https://bits.wikimedia.org/static-1.21wmf9/skins/vector/images/user-icon.png
+> .
+
+Ah, right, I forgot that monobook is different! You can see the old good one e.g. in the screenshot at https://creativecommons.org/weblog/entry/13967
+I've never considered it particularly manly: the hair always looked to me like a bun (if this is the correct term for the hairstyle), which is indeed particularly rare for men. :-)
+Hence the ? in the bug summary.",1360945543,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**sumanah** wrote:
+
+The current icon is https://bits.wikimedia.org/static-1.21wmf9/skins/vector/images/user-icon.png .
+
+(In reply to comment #4)
+> I prefer a single, neutral icon to gender specific icons. 
+> 
+> How do you make a ""female"" icon anyway, short of giving it breasts? Long
+> hair?
+> Tell that to Brandon and Sumana!
+
+For people who haven't met us: Brandon is a man with long hair, and I am a woman with short hair.
+
+These kinds of avatars are usually heads, head-and-shoulders, or stick figures of the whole body, so some designers use long hair, earrings, or a skirt as a shorthand for ""female.""
+
+I ask our designers to figure out how to make a more gender-neutral icon (perhaps dispensing with the requirement that it look like a person).",1360945018,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","(In reply to comment #3)
+> Thanks for pointing this out, Aude.  For ideas on how to rework the default
+> icon to make it more gender-neutral, here's the ""gallery of default
+> anonymity"":
+> http://www.murketing.com/journal/?p=3098
+
+Flickr is IMHO the best. Should also be {{PD-ineligible}} and in compliance with the colour scheme per Krinkle above.",1360944568,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","I prefer a single, neutral icon to gender specific icons. 
+
+How do you make a ""female"" icon anyway, short of giving it breasts? Long hair? Tell that to Brandon and Sumana!",1360943543,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**sumanah** wrote:
+
+Thanks for pointing this out, Aude.  For ideas on how to rework the default icon to make it more gender-neutral, here's the ""gallery of default anonymity"": http://www.murketing.com/journal/?p=3098",1360943098,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","The MediaWiki Vector skin is primarily white/grey oriented with focus on blue and activity on orange (mouse down).
+
+Blue is not male in this context, it is theme colours. Using red would grab wrong attention to the icon.
+
+Removing 'easy' keyword until it is clear whether we want this in the first place. Adding 'design' and CC-ing Trevor for his opinion.",1355997451,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"Vector: Default icon for ""profile"" in personal tools should be gender neutral and fit with other site icons look & feel","**p.selitskas** wrote:
+
+If the icon from Vector is this[1], then we can pick a red one for girls[2]. If red is not OK, then anyone can just change the color in SVG and it's done.
+
+--
+[1] https://commons.wikimedia.org/wiki/File:Emblem-person-blue.svg
+[2] https://commons.wikimedia.org/wiki/File:Emblem-person-red.svg",1355924272,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y3luskovb4jkrwp3ep3w,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","Tested with IE 8 and latest RC of FF.
+
+Current behaviour:
+When clicking the ""preview"" or ""show diff"" button, the page reloads.
+
+Evidence:
+...after the DOM is ready...
+...executed in JavaScript console...
+> mw.loader.getState('mediawiki.action.edit.preview');
+'registered'
+
+Expected behaviour:
+When clicking the ""preview"" or ""show diff"" button, live preview just replaces some elements in the DOM. No page reload.
+
+> mw.loader.getState('mediawiki.action.edit.preview');
+'ready'
+
+How to reproduce:
+Set your interface language to de or en, enable ""Use live preview"" in [[Special:Preferences]], go to a page, edit a section, click preview.
+
+Note:
+Using manually
+mw.loader.load('mediawiki.action.edit.preview');
+works perfectly: After it is loaded, LivePreview works as expected.
+
+--------------------------
+**Version**: 1.20.x
+**Severity**: normal",1350898080,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-rjnvooe4gramc7frhovi,task_description,resolved
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","(In reply to comment #5)
+> https://bugzilla.wikimedia.org/show_activity.cgi?id=41267
+> 
+> I am confused. Please tell me what is ""right"" now?
+> 
+> Using [Regression] in bug title or Keyword ""code-update-regression"" or both?
+
+They keyword is what counts. The reason various people prefer to (sometimes) include (parts of) keywords or components (e.g. ""[Regression]"", ""VisualEditor: .."" etc.) is because most interfaces with bugzilla content lack proper indication of components and tags, so we put them in the subject so that they can be seen directly (e.g. in irc notifications for bug changes and in e-mail notifications[1]).
+
+[1] Yes, for some of the fields there are mail headers sent, but that is only useful for querying e-mails, not when browsing them in any mail applications plain list view.",1351012277,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","I guess different people have different habits, so I change my mind and say: Do what you want with the bug subject, but having the keywrod set would be really great."" Sorry for any confusion.",1351008994,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","https://bugzilla.wikimedia.org/show_activity.cgi?id=41267
+
+I am confused. Please tell me what is ""right"" now?
+
+Using [Regression] in bug title or Keyword ""code-update-regression"" or both?",1351008627,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","In the 1.20 release-notes:
+
+* Live preview functionality has been improved and moved into the
+ 'mediawiki.action.edit.preview' module. The old 'mediawiki.legacy.preview' module
+  has been removed.
+
+Looking at core, the only usage of 'mediawiki.action.edit.preview' is in the resource definition
+
+Original commit:
+https://github.com/mediawiki/core/commit/4d4bfc27a1bedf6b0d1670707ac812fe36fe85ad
+
+EditPage.php now:
+
+		if ( $wgUser->getOption( 'uselivepreview', false ) ) {
+			$wgOut->addModules( 'mediawiki.legacy.preview' );
+		}
+
+It got killed by https://github.com/mediawiki/core/commit/bb51a58e575b13eb8b6c496482f7066a7081f676
+
+https://gerrit.wikimedia.org/r/29339",1350924643,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]",(Regression => keyword code-update-regression),1350923316,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]",Used Vector skin to test,1350898685,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+"[Regression] mediawiki.action.edit.preview is not loaded at Commons despite ""Use live preview"" (wpuselivepreview) is activated in [[Special:Preferences]]","Commons runs 1.21wmf2
+
+Also tested at dw.wp which runs 1.21wmf1 and there it works. So my guess is that the bug slipped-in between the two versions.",1350898365,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-rjnvooe4gramc7frhovi,task_subcomment,NA
+VisualEditor: Strange behavior after overwriting nowiki block,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Put cursor within the nowiki block
+2) Press a
+3) Press Left
+4) Press b
+5) Problem: ""a"" has disappeared
+
+
+(off-topic: with more complex moves I have spotted a self-replicating snowman ☃, now hunting him down)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1350624900,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-c65rdnrtnbgfg3a46ubp,task_description,resolved
+VisualEditor: Strange behavior after overwriting nowiki block,Now fixed as part of the alienation re-write.,1360205998,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c65rdnrtnbgfg3a46ubp,task_subcomment,NA
+VisualEditor: Strange behavior after overwriting nowiki block,Confirmed.,1350939018,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c65rdnrtnbgfg3a46ubp,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Put cursor at end of nowiki line
+2) Select a different style
+3) Problem: Style not applied
+
+The style is applied if the line contains simple text instead.
+The style is applied if selecting the whole nowiki line instead of just putting the cursor at end of line.
+
+I guess nowiki in headers is not usual, though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350623940,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-5pbz4o5r22cqczijgvqj,task_description,resolved
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,Merged and will go out in the deploy train tomorrow.,1367181672,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,https://gerrit.wikimedia.org/r/#/c/61157/,1367020557,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,"This is a bug in newFromContentBranchConversion(), and is caused by selectNodes() returning the paragraph rather than a text node, because the selection is between the open/closing paragraph and the alien.",1363988049,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,"Can't reproduce. Note that it is nowiki in paragraph, not in a header.",1360361449,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,And in Chrome.,1360205937,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Paragraph containing nowiki block does not change style unless block selected,Confirmed in FF.,1350928759,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5pbz4o5r22cqczijgvqj,task_subcomment,NA
+VisualEditor: Backspace does not remove paragraph when previous paragraph contains nowiki block,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Put cursor at end of nowiki line
+2) Press Enter
+3) Press Backspace
+4) Cursor moves back but newly created paragraph remains
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350622500,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-7erbrnp4x3oao3bdre67,task_description,resolved
+VisualEditor: Backspace does not remove paragraph when previous paragraph contains nowiki block,Still a CE issue (?).,1360205834,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7erbrnp4x3oao3bdre67,task_subcomment,NA
+VisualEditor: Backspace does not remove paragraph when previous paragraph contains nowiki block,Confirmed.,1350928635,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7erbrnp4x3oao3bdre67,task_subcomment,NA
+VisualEditor: Text entered at left of nowiki block replaced with a slug character (pawn) when saved,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Put cursor at end of line
+2) Press Left
+3) Press a
+4) Problem: ""a"" does not seem to appear. Instead, it seems like the beginning of the block is being selected.
+5) Save
+6) Where ""a"" is expected, there is a pawn ♙
+
+= Heading 1a =
+♙<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Linux
+**Platform**: PC",1350615420,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-peotted4ituorcv5mtdk,task_description,resolved
+VisualEditor: Text entered at left of nowiki block replaced with a slug character (pawn) when saved,"This has been fixed in the ensuing 3 months, probably when aliens was re-written.",1360205789,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-peotted4ituorcv5mtdk,task_subcomment,NA
+VisualEditor: Text entered at left of nowiki block replaced with a slug character (pawn) when saved,Confirmed.,1350928483,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-peotted4ituorcv5mtdk,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Author:** `orbit`
+
+**Description:**
+This used to work by using localStorage, but was removed due to problems with stringifying and parsing annotationSets.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350601440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_description,resolved
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #25)
+> I did a quick test on mediawiki.org just now using [[mw:VisualEditor:What A]]
+> and [[mw:VisualEditor:What B]]. It seems to mostly work in my browser, though
+> it inserted a non-breaking space before the header. I'll file a separate bug
+> about this.
+
+Filed as bug 58563.",1387246854,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"I did a quick test on mediawiki.org just now using [[mw:VisualEditor:What A]] and [[mw:VisualEditor:What B]]. It seems to mostly work in my browser, though it inserted a non-breaking space before the header. I'll file a separate bug about this. This bug report seems to be resolved/fixed and I'll echo others in suggesting that new bug reports be filed for cases in which copying and pasting misbehaves. Basic support appears to be implemented, however.",1387246576,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #22)
+> @Quim somewhat true, but we should also not forget that if you have a title
+> like: ""support copy and paste from other VE instances"", which basically reads
+> as a user story, that you can expect folks to judge the ticket as a user
+> story as well.
+
+Yes, I fully agree. This is what I meant in previous post when qualifying this bug report (perhaps too nicely) as far from perfect. We have a title and a one-line comment that doesn't provide any details about the feature expected.
+
+It was filed more than a year ago, when VisualEditor was basically a feature developed and used by one small team. The note to remember is that even in those circumstances reports filed must be minimally descriptive in order to set a clear expectation about the requirement to fix it.
+
+Anyway, back to the actual problem. Many more bug reports have been added to tracking Bug 33105 (thank you!) which is clearly the report that will define the quality of copy&pasting in VisualEditor.",1386861491,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(In reply to comment #21)
+> This discussion is not helpful. Please read 
+> 
+> https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquette
+> 
+> This report is far from perfect since Comment 0 since all we have to evaluate
+> is
+> 
+> ""VisualEditor: Support copy and paste from other VE instances (surfaces)""
+> 
+> Now this support is in place. You are saying that it doesn't work in certain
+> circumstances. Are there file bugs opened for the circumstances you can
+> reproduce? Currently we have
+> 
+> Bug 33105 - VisualEditor: Preserve rich text formatting when pasting from
+> internal or external sources (tracking)
+> 
+> which tracks 6 bug reports. Are the problems you are encountering covered
+> there? I didn't read the whole conversation at the wiki page, but the
+> problems
+> seemed to be related with formatting being lost from copy to paste, which is
+> what Bug 33105 is tracking. 
+> 
+> If not, please create new bugs for the cases that are missing.
+
+This discussion is not helpful? On the contrary, it has made the position of many devs a lot clearer, and the gap between them and their ""customers"", for lack of a better word. That it may have violated your Bugzilla Etiquette is the least of my concerns, and that my Bugzilla access may be taken away is your loss, not mine. 
+
+I am not saying that ""it doesn't work in certain circumstances"", I'm saying that it doesn't work in nearly all circumstances. 
+
+Are there file bugs opened for it? Don't know, don't really care. I have done your (devs) job, testing the software, and have reported at length what I encountered in those far from exhaustive tests. Perhaps now you (devs) can do what is apparently my job, and file the bugs? The arrogance of this thread and these statements may escape you, but it is unmistakeable for an outsider. 
+
+What bugs are coupled at the moment to the mythical bug 33105 (""The main work is done' Priority back to normal"")? Bug 37932 is not relevant, 48172 may be related, 48720 is not relevant, 50126 has nothing to do with my reported problems, 51725 doesn't seem to be about what the title describes, 52091 is about copying from read mode (which WhatamIDoing (WMF) claimed was not what this was about)... So no, the many problems I reported are not yet noted, or at least not coupled to 33105. 
+
+""If not, please create new bugs for the cases that are missing."" No, even though you ask nicely, but the treatment by others, the ones that should have found these problems in the first place, doesn't give me any reason to waste my time repeating the errors I reported here once again, where they will be closed at the whim of a dev anyway, sometimes fixed, sometimes not. I hope that someone who should have tested this from the WMF devs or the in-name-only QA team will be a tiny bit ashamed about all that's happened here, and file the bugs themselves. I doubt it though. It's easier to blame the messenger than to look at your own faults.",1386837060,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"@Quim somewhat true, but we should also not forget that if you have a title like: ""support copy and paste from other VE instances"", which basically reads as a user story, that you can expect folks to judge the ticket as a user story as well.
+
+We say that this is fixed because the basic technical backbone work for it has been done and that the 'content' part of it is separate tracked in it's parent ticket, but that is a very narrow definition of course when the line between user/developer is as thin as it often is on bugzilla. Such differences are bound to create friction.",1386808905,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"This discussion is not helpful. Please read 
+
+https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquette
+
+This report is far from perfect since Comment 0 since all we have to evaluate is
+
+""VisualEditor: Support copy and paste from other VE instances (surfaces)""
+
+Now this support is in place. You are saying that it doesn't work in certain circumstances. Are there file bugs opened for the circumstances you can reproduce? Currently we have
+
+Bug 33105 - VisualEditor: Preserve rich text formatting when pasting from internal or external sources (tracking)
+
+which tracks 6 bug reports. Are the problems you are encountering covered there? I didn't read the whole conversation at the wiki page, but the problems seemed to be related with formatting being lost from copy to paste, which is what Bug 33105 is tracking. 
+
+If not, please create new bugs for the cases that are missing.",1386804166,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(In reply to comment #18)
+> (In reply to comment #17)
+> > Have you actually looked at and read (and understood) the linked enwiki
+> > thread? And you can straight-faced claim that this is ""fixed""?
+> 
+> I am aware that this bug, though fixed, does not encompass the entirety of
+> what
+> we want to see. There are other bugs, many of which we are trying to fix but
+> are being distracted by people who think it's productive to edit-war on
+> Bugzilla and sling insults and threats rather than actually engaging.
+> 
+> If you had bothered to ask, rather than just assume, we could have pointed
+> this
+> out before you got so very excited. But you seem more content to scream than
+> talk, and then act surprised when we choose to spend our time more
+> productively.
+
+
+""Though fixed"". Right... 
+
+""Does not encompass the entirety of what we want to see"" is newspeak for ""actually screws up nearly every edit""?
+
+""People who think it is productive to edit-war on Bugzilla and sling insults and threats rather than actually engaging""; history has shown that complacency isn't productive with you (plural), so another approach is needed. ""Actually engaging""? The section about this bug and these problems has been open for days at enwiki, I have done ''all'' the work on it, I am the only one that actually tested this bugfix (and the rest of the deployment as well, clearly). Your ""engagement"" was a hardly relevant reply focusing on one minor aspect, but ignoring the larger picture; 
+
+""Being distracted""; well, I didn't see any positive results when you weren't being distracted either...
+
+""If you had bothered to ask""? Instead of e.g. reclosing this without even commenting? 
+
+I would be very happy if you spent your working hours productively, but the results are lacking. Of course, if you consider something that is as extremely buggy as this thing ""a fix"", then I understand your replies; I can't use them though.",1386801157,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(edit conflict)
+As for rewriting history, I reopened this here with the comment
+
+""As reported at
+[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.3F],
+this is clearly not yet fixed. Testing at MediaWiki shows that copying between
+VisualEditor pages (both within MediaWiki, and from enwiki to MediaWiki) gives
+very poor results. I have made four tests, none of them anything extreme (only
+one section header and text, no images, templates, ...), and none of them gave
+a satisfactory result.""
+
+Can you indicate where you replied to this comment and/or adressed the issues I highlighted in them? Are you seriously claiming that your comment at the Status page was a reply (never mind a sufficient reply) for problem reports like what happened [https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=837324&oldid=837321 here]? You didn't at least think about retesting this when you thought that this was ""resolved""? It still happens, FYI. And when I reopened this, you didn't think that just perhaps I didn't believe that this was resolved onwiki or offwiki? 
+
+I have pointed out countless bugs, probably more than anyone else the last half year: perhaps it is time you start taking them seriously, and consider that I may have a point, instead of blundering on blindly.",1386800636,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #17)
+> Have you actually looked at and read (and understood) the linked enwiki
+> thread? And you can straight-faced claim that this is ""fixed""?
+
+I am aware that this bug, though fixed, does not encompass the entirety of what we want to see. There are other bugs, many of which we are trying to fix but are being distracted by people who think it's productive to edit-war on Bugzilla and sling insults and threats rather than actually engaging.
+
+If you had bothered to ask, rather than just assume, we could have pointed this out before you got so very excited. But you seem more content to scream than talk, and then act surprised when we choose to spend our time more productively.",1386799884,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+Oh, my edit rights at Bugzilla? I'm scared now. What will I do without the possibility to edit Bugzilla? I imagine that if you continue to bury your head in the sand, someone will take away your job, but my imagination and reality sadly don't always match. 
+
+Have you actually looked at and read (and understood) the linked enwiki thread? And you can straight-faced claim that this is ""fixed""? This is comparable to ""operation successful, patient dead"".",1386799712,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"Your attempts to re-write history notwithstanding, Fram, this is and remained fixed. If you edit war again, I imagine someone will end up taking your edit rights away. Please stop.",1386799249,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+[https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=585650020&oldid=585645740]
+
+This thing is so not ready that it is laughable to claim otherwise. I would seriously urge you to keep this on open now, read and check all the comments (bug reports), and only then come back. This is more serious than any of you seems to understand. 
+
+THIS FIX IS ABSOLUTELY NOT READY TO BE DEPLOYED. 
+
+Read the fucking linked section, [[en:Wikipedia:VisualEditor/Feedback#Who needs bugs when you get ""fixes"" like this?]], don't bury your heads in the sand.",1386797989,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(In reply to comment #13)
+> Fram,
+> 
+> I closed this without comment because we'd already discussed this, and it
+> didn't seem like a worthwhile expenditure of my time or yours to re-hash the
+> issue when we already agreed about things. I'm sad that you think I did it
+> out
+> of malice. AGF clearly doesn't apply to your attitude. :-( Please be less
+> aggressive in future.
+
+No, I'll only get more aggressive, just read my last post at enwiki or my next post here, which will be a link to enwiki. 
+
+""We'd already discussed this""? You mean your replies at [https://www.mediawiki.org/wiki/Talk:VisualEditor/status]? No, I don't see where we actually agreed upon things. You were pinged about the enwiki discussion as well, which contained further examples. 
+
+But I don't said you did it out of malice, there are a number of other possible reasons, including (but probably not limited to) laziness, incompetence, stupidity, or a hopefully well-founded fear of losing your job after the umpteenth VE fiasco.",1386797730,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #12)
+> (In reply to comment #11)
+> > Wikifram: Sorry, I won't read through the entire
+> > https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.
+> > 3F -
+> > summarize clear testcases in Bugzilla in separate followup tickets to keep
+> > things constructive, change your passive-aggressive tone, keep this ticket
+> > closed as FIXED (as functionality exists but obviously is extremely
+> > error-prone
+> > for your testcases), and discuss high-level stuff refering to general testing
+> > on the mailing list instead. Thanks.
+> 
+> My tone isn't passive-agressive, it is simply agressive, as in thoroughly fed
+> up with the way the WMF handles things. I love it though that theDJ has
+> added a
+> ticket that blocks this one, but that you closed it again nevertheless. 
+> 
+> I am not interested in discussing things on the mailing list, I am discussing
+> it at enwiki which has the largest and least biased audience of all public
+> discussion places (compared to MediaWiki, which has a rather more slanted and
+> smaller audience, Foundation, where there are no public discussion spaces,
+> and
+> Bugzilla, which is not suited for this). 
+> 
+> Closing tickets without any explanation, like Product Manager Forrester did,
+> is passive-agressive and completely unconstructive though.
+
+Fram,
+
+I closed this without comment because we'd already discussed this, and it didn't seem like a worthwhile expenditure of my time or yours to re-hash the issue when we already agreed about things. I'm sad that you think I did it out of malice. AGF clearly doesn't apply to your attitude. :-( Please be less aggressive in future.",1386795057,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+(In reply to comment #11)
+> Wikifram: Sorry, I won't read through the entire
+> https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.
+> 3F -
+> summarize clear testcases in Bugzilla in separate followup tickets to keep
+> things constructive, change your passive-aggressive tone, keep this ticket
+> closed as FIXED (as functionality exists but obviously is extremely
+> error-prone
+> for your testcases), and discuss high-level stuff refering to general testing
+> on the mailing list instead. Thanks.
+
+My tone isn't passive-agressive, it is simply agressive, as in thoroughly fed up with the way the WMF handles things. I love it though that theDJ has added a ticket that blocks this one, but that you closed it again nevertheless. 
+
+I am not interested in discussing things on the mailing list, I am discussing it at enwiki which has the largest and least biased audience of all public discussion places (compared to MediaWiki, which has a rather more slanted and smaller audience, Foundation, where there are no public discussion spaces, and Bugzilla, which is not suited for this). 
+
+Closing tickets without any explanation, like Product Manager Forrester did, is passive-agressive and completely unconstructive though. Perhaps you can lecture him on these things instead. My posts have been constructive, trying to improve Wikipedia and VE, but the format and tone hasn't been to your liking. Tough luck. If you wan to know what is wrong with this ""feature"", either read the enwiki thread or (better still) test it or get your team to test it thoroughly, but don't expect me to repeatedly seek the shabby treatment the WMF people routinely handle out to critics, by submitting new bugs about this.",1386773010,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"Wikifram: Sorry, I won't read through the entire https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.3F - summarize clear testcases in Bugzilla in separate followup tickets to keep things constructive, change your passive-aggressive tone, keep this ticket closed as FIXED (as functionality exists but obviously is extremely error-prone for your testcases), and discuss high-level stuff refering to general testing on the mailing list instead. Thanks.",1386769779,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+But can't we expect new functionality to work sometimes? ''Every'' test I have done produced errors. You could copy and paste before this ""fix"", it didn't give any layout though. With this fix, you get some layout, and a lot of botched layout.
+
+I really can't believe that any of you believe this ""fix"" is sufficiently reliable, stable, mature to be implemented in live environments. Sometimes, like here, ''not'' having a feature is a lot better than having an extremely poor attempt at one. I don't expect it to work 100% in all cases, but I do expect it to work 100% in some cases, and 95% in most cases. I don't believe this can truthfully be claimed of this. 
+
+As for ""provide exact steps to reproduce"": RTFM. I have given a link to the many tests I have done, I have described there what goes wrong. I have only received evasive or plainly incorrect answers from WMF people there. I am not going to repeat all of that here, you can just as easily follow the link I provided and try do to the same. 
+
+No thanks for your (WMF collective) help.",1386766093,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"> Why do you reclose a bug as resolved -fixed without any improvement or comment
+
+Because the functionality to copy and paste from other VE instances exists with the given patch having been merged, so this request is FIXED.
+
+This bug report never was about ""Implement functionality to copy and paste from other VE instances and make sure that it works in 100% of all cases"".
+Software always has issues. But the request in this bug report has been fixed.
+
+Hence please create separate followup bug reports on issues that don't work and provide exact steps to reproduce. Comment 7 does not have steps to reproduce.
+Thanks for your help!",1386765597,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+James Forrester, get lost. 
+
+Why do you reclose a bug as resolved -fixed without any improvement or comment, when people take the time to test this, report their findings, and show where the problems are? 
+
+The least you can do is explain why this is resolved - fixed despite my remarks; the best you can do is test this, correct it, and only then close it as fixed. 
+
+How many times will you make the same mistakes, how often will you close bugs as duplicates when they are not, as fixed when they are not, or present things as finished when they aren't even tested? Please change your approach to this or leave it to people who seem to be more competent or less defensive. You are not doing yourself, WMF, or Wikipedia a favour by your continued behaviour wrt VisualEditor.",1386749798,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**Wikifram** wrote:
+
+As reported at [https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Rich_content.3F], this is clearly not yet fixed. Testing at MediaWiki shows that copying between VisualEditor pages (both within MediaWiki, and from enwiki to MediaWiki) gives very poor results. I have made four tests, none of them anything extreme (only one section header and text, no images, templates, ...), and none of them gave a satisfactory result.",1386577251,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"Change 86664 merged by jenkins-bot:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1385500079,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"Change 86664 had a related patch set uploaded by Esanders:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1381157521,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),*** Bug 50421 has been marked as a duplicate of this bug. ***,1373407947,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"(In reply to comment #2)
+> Also, question to the other of this ticket: Do you mean copying content from
+> VisualEditor opened in one tab to VisualEditor opened in another tab of the
+> same browser (Chrome for instance)?
+
+This is still not working:
+
+1. Open two different articles with VisualEditor.
+2. Copy or cut content from one and paste it to the other one.
+
+Format is lost. Links are lost. Not worth even trying in an average wiki page.
+
+This is a relatively frequent action when cleaning, reorganizing archiving content in articles.",1372456721,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"In order to support this functionality we need to develop some sort of annotations serializer and deserializer.
+
+Also, question to the other of this ticket: Do you mean copying content from VisualEditor opened in one tab to VisualEditor opened in another tab of the same browser (Chrome for instance)?",1351118896,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: Support copy and paste from other VE instances (surfaces),"**orbit** wrote:
+
+Assigning to myself.",1350601508,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fgmvecleq7bixt5aoemb,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"At first the last letter is not linked but after save-reload it becomes linked.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350557280,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-7cd6puxwf2ufvh73gnet,task_description,resolved
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"(In reply to comment #6)
+> It could be actually a problem in Parosid/Serializer.
+Yup, this is a Parsoid bug, duped as such.",1363987478,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"
+
+*** This bug has been marked as a duplicate of bug 33091 ***",1363987427,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"It could be actually a problem in Parosid/Serializer.
+
+@Liangent: Could you please provide exact steps to reproduce?",1360363577,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"Apparently, not fixed.  Link trails get included in the link and not preserved.",1354217293,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,This is fixed in master.,1354217237,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"(In reply to comment #1)
+> If a link is set on a selection, need to special-case extend the annotation to
+> the first breaking character on from the selection (but only forwards) to
+> re-create how wikitext works.
+
+Remember though it's less used, there's also linkprefix, like:
+
+som[[eth]]ing -> [[eth|something]]",1350625179,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,This is because the document is out of sync with the model.  This is a CE bug.,1350585606,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: LinkTrailed links appear differently before and after save-reload,"If a link is set on a selection, need to special-case extend the annotation to the first breaking character on from the selection (but only forwards) to re-create how wikitext works.",1350583959,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7cd6puxwf2ufvh73gnet,task_subcomment,NA
+VisualEditor: Backspace can't remove Preformatted,"1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Press: a Enter b Enter c
+3) Select b with the mouse, set style to Preformatted
+4) Click after c
+5) Backspace as much as you can
+
+Expected result: c, b, a disappear
+Actual result: c disappears, subsequent newline disappears, then nothing disappears anymore.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350547200,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-hbxpldwjo7edx75sbrgd,task_description,resolved
+VisualEditor: Backspace can't remove Preformatted,"Confirm similar bug in Firefox, not in Chrome or Safari - c disappears, then b looses its PRE formatting and the cursor jumps to the left side of b, then a disappears.",1350580959,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hbxpldwjo7edx75sbrgd,task_subcomment,NA
+VisualEditor: Give user some notice if their browser is not supported,"I had a look at its code and finally found the compatibility map. See gerrit 41147.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350542220,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-vezbsxzq3qktiqaner6o,task_description,resolved
+VisualEditor: Give user some notice if their browser is not supported,"We've changed our plans for how the overall integration will work, so marking this as a DUPE of 38128 now.
+
+*** This bug has been marked as a duplicate of bug 38128 ***",1368039230,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vezbsxzq3qktiqaner6o,task_subcomment,NA
+VisualEditor: Give user some notice if their browser is not supported,For browsers that support JS but don't have VE support - e.g. Opera or Iceweasel - have a notice somewhere (above the wikitext edit page?) to inform users of why they don't get the nice editor...,1350580343,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vezbsxzq3qktiqaner6o,task_subcomment,NA
+VisualEditor: Give user some notice if their browser is not supported,* bug 41147,1350542281,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-vezbsxzq3qktiqaner6o,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"**Author:** `orbit`
+
+**Description:**
+If the linmod is 
+ABC<alienInline></alienInline>DEF
+0123            4             5678
+
+When the cursor is at 5, getOffset returns 3. Programmatically setting selection to 5 will correctly place the cursor, but once again, getting the offset will return 3.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350495360,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-peieofedvf7rbivy6oia,task_description,invalid
+VisualEditor: Offset is incorrect after alienInline in Firefox,"**orbit** wrote:
+
+Yeah, fixed through various re-writes. We're going to leave aliens as ce=""false"" for standards-based browsers and we'll have to programmatically fix IE if the cursor ends up inside.",1364248074,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"Is this still an issue, or has it been fixed through the various re-writes of this area?",1360205444,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"Having contentEditable=""false"" is the original idea but unfortunately it does not work for IE (IE does not respect contentEditable=""false"" inside contentEditable=""true""). Now we are experimenting with having contentEditable=""true"" and blocking interaction with JavaScript but this approach has its downsides as well - for instance you would get a spellcheck underlines for misspelled words inside alien (majority of browsers we want to support does not respect spellcheck=""false"" inside spellecheck=""true"").
+We might end up with different approaches for different browsers (of course this is not the preferred solution due to possible high costs of maintenance and testing).",1351101271,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"(In reply to comment #1)
+> This is if aliens are contentEditable=""true"".
+Aren't they supposed to be contentEditable=""false""?",1351099924,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Offset is incorrect after alienInline in Firefox,"**orbit** wrote:
+
+This is if aliens are contentEditable=""true"".",1350591225,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-peieofedvf7rbivy6oia,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"**Author:** `hydrogen_cyanide`
+
+**Description:**
+when adding a link with Chinese characters, [[天安门广场]] in wikitext, the unicode character in the wikilink are percent-encoded, and the result i get after saving is [[%E5%A4%A9%E5%AE%2589%E9%2597%A8%E5%B9%BF%E5%9C%BA|天安门广场]]. 
+
+it seems to be linked with the browser. my browser is firefox 14.0.1. the link added by others before are also encoded. see 
+http://www.mediawiki.org/w/index.php?diff=594584
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=40004",1350493800,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_description,resolved
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,Confirmed fixed in master.,1355171819,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"(In reply to comment #5)
+> I5e1de9244d727641c10b6f0a89acc61afba7ecad looks to be the commit that will
+> resolve the dependency - it's not the whole solution and it's not done yet
+> though, so don't go and resolve this bug just yet.
+
+That change was abandoned, I45fb3206 is the successor (and has been merged).",1355166897,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"I5e1de9244d727641c10b6f0a89acc61afba7ecad looks to be the commit that will resolve the dependency - it's not the whole solution and it's not done yet though, so don't go and resolve this bug just yet.",1354842287,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"Whatever patch we make, it's going to depend on I9cb862f8498ba62ad7fc7669d70ea2b8e2eddbef and whatever additional patch comes after it to finish fixing what that didn't quite accomplish.",1354833640,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"Per bug 41152 , the Parsoid team decide to keep non-urlencoded form in <a href="" ""> so VisualEditor shouldn't send an encoded form for newly created links, at least by default (except when user manually input an encoded link target).",1353389516,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,*developer tool,1350494436,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Unicode in links is percent-encoded when saved as wikitext,"This does not happen in Chromium. From developer I see, in Firefox, href of a[rel=mw:WikiLink] is urlencoded in generated DOM but in Chromium it is not.
+
+The second issue is bug 40004.",1350494393,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-yiyhc6t4upjvxr35iuyv,task_subcomment,NA
+VisualEditor: Complex script (Indic) compatibility,"The tests mentioned in the link fail for Indic text.
+
+* Using styling icons.
+* Deleting text properly using delete / backspace keys.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://www.mediawiki.org/wiki/VisualEditor/Typing/Indic",1350483960,PHID-USER-3stle7x2whgjz463c4zz,False,PHID-TASK-73dsmojov4fu5z4edh64,task_description,resolved
+VisualEditor: Complex script (Indic) compatibility,Works in current version of the editor (thanks to IME support). However I will make sure to keep executing tests from this page: http://www.mediawiki.org/wiki/VisualEditor/Typing/Indic (at this moment we have problems with automating IME tests).,1360364417,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-73dsmojov4fu5z4edh64,task_subcomment,NA
+VisualEditor: Cursor jumps at the top/bottom of page after particular deletions/moves,"1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Put your cursor anywhere in simple text
+3) Press: Enter, Enter, Up
+4) Click the bullet list icon
+5) Press: Backspace, Enter, Down
+6) Problem: Cursor jumps at the bottom of the page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350451500,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-tlecjwjjkrzbeglszhlp,task_description,resolved
+VisualEditor: Cursor jumps at the top/bottom of page after particular deletions/moves,"**orbit** wrote:
+
+It appears both of these are fixed. Probably due to list fixes from Roan and cursor fixes from Inez.",1371773435,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tlecjwjjkrzbeglszhlp,task_subcomment,NA
+VisualEditor: Cursor jumps at the top/bottom of page after particular deletions/moves,"**orbit** wrote:
+
+Yeah, the second example is a different bug which has been fixed. First one is still a problem though.",1350603378,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tlecjwjjkrzbeglszhlp,task_subcomment,NA
+VisualEditor: Cursor jumps at the top/bottom of page after particular deletions/moves,"Easier way to reproduce (might be a different bug):
+
+1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Select a paragraph with the mouse
+3) Press Delete
+4) Press Up
+6) Problem: Cursor jumps to the top of the page",1350452011,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-tlecjwjjkrzbeglszhlp,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Put your cursor anywhere in simple text
+3) Press: Enter, Enter, Up
+4) Click the bullet list icon
+5) Press: Backspace, Enter, Down
+6) Surprise: A wild pawn appears! ♙
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350376800,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_description,resolved
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"Marking back as fixed as of October. If you have new bugs, please create new reports rather than re-open ones tangentially-related.",1369911007,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,This seems to be fixed already in master and on mediawiki.org.,1369874909,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,*** Bug 47687 has been marked as a duplicate of this bug. ***,1367254472,PHID-USER-u7udgblfyop6qd5wxot6,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"I think that this happens again, but only on Firefox.
+
+Here's another simple test:
+
+https://www.mediawiki.org/wiki/VisualEditor:Pawn
+
+Edit this page in VE and start moving with the arrow keys forward (right). A pawn appears in the beginning and the end of every list item.",1367079084,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,I (original reporter) confirm the fix.,1351563924,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"**orbit** wrote:
+
+All pawn problems have been resolved and pushed to mediawiki.org.",1350450678,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"Confirming bug.
+
+It also occurs in this simplified sequence:
+(1) Click anywhere on the text
+(2) Enter, enter, up
+
+(Note: Christian, Konami code is an easter egg, not a bug. It doesn't occur with normal operations. I agree the sequence enter enter up backspace enter down appears to be a little like a up up down down left right left right b a (enter) but ... the sequence Nicolas use is a legit one to edit text.)",1350380046,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,"**orbit** wrote:
+
+It's like the Konami code of the Visual Editor. :) I'll take a look at this. We're specifically using a pawn for a certain trick that we need to do so that if it ever appears, we know where the problem is.",1350378115,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Pawn ♙ appears after deleting list and moving cursor,Linux Ub,1350377919,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-jqxpftgvocz6dbwkyo26,task_subcomment,NA
+VisualEditor: Implement keyboard command registry,"From Trevor:
+> [1] https://gerrit.wikimedia.org/r/#/c/26703/
+> [2] https://github.com/madrobby/keymaster
+> [3] https://github.com/ccampbell/mousetrap
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1349804760,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wfbwa6r6kerlfz6umih6,task_description,resolved
+VisualEditor: Implement keyboard command registry,This has been implemented now.,1353111407,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-wfbwa6r6kerlfz6umih6,task_subcomment,NA
+VisualEditor: Implement keyboard command registry,"(In reply to comment #1)
+> Change-Id: Ic69a3c70759052094aefbeab623d885f8b118e14
+
+This has been merged, keeping bug open as implementation isn't finished yet.",1351544052,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wfbwa6r6kerlfz6umih6,task_subcomment,NA
+VisualEditor: Implement keyboard command registry,Change-Id: Ic69a3c70759052094aefbeab623d885f8b118e14,1350974080,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wfbwa6r6kerlfz6umih6,task_subcomment,NA
+VisualEditor: Pre-annotations don't work if at first character of a blank line (paragraph or list item),"Go to a blank paragraph. Press Ctrl-B or the Bold button; the button depresses, but if you type the text comes out unannotated.
+
+This does not occur when the caret is at any point in the paragraph or list item which has any content in it, only when it is blank.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1349133000,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-43hyj7572ppndylnp2wq,task_description,resolved
+VisualEditor: Pre-annotations don't work if at first character of a blank line (paragraph or list item),"**orbit** wrote:
+
+This is now fixed.",1349999541,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-43hyj7572ppndylnp2wq,task_subcomment,NA
+VisualEditor: Pre-annotations don't work if at first character of a blank line (paragraph or list item),"**orbit** wrote:
+
+Inez is working on pre-annotations + slug replacement. Reassigning to him.",1349896863,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-43hyj7572ppndylnp2wq,task_subcomment,NA
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,"Little hard to reproduce but has come up several times. Selecting some text, playing around with the inspector and pasting some text.
+
+Stack:
+
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null
+> ve.dm.Document.getNodeFromOffset
+> ve.ui.Toolbar.updateTools
+> ve.EventEmitter.emit
+> ve.dm.Surface.change
+> ve.ce.Surface.onPaste
+> jQuery.extend.proxy.proxy
+> jQuery.event.dispatch
+> jQuery.event.add.elemData.handle.eventHandle
+
+
+ve.dm.Document.prototype.getNodeFromOffset = function(offset) {
+        var node = this.documentNode.getNodeFromOffset(offset);
+        if (!node.canHaveChildren
+Uncaught TypeError: Cannot call method 'canHaveChildren' of null
+        ()) {
+            node = node.getParent();
+        }
+        r
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348451460,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_description,resolved
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,This was fixed in Ia7347527e6466262e819f456404b32926fd95e34,1354054590,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_subcomment,NA
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,Pushing to next milestone as they did not make it to master by yesterday.,1352832079,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_subcomment,NA
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,"Aside from Surface.change, Surface.showSelection also has a similar problem:
+
+http://cl.ly/image/1v1h3f2M2722",1349127029,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_subcomment,NA
+VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions,"Thought this one got fixed, but clearly not. :-)",1348507765,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gpw7j3jiv4sk67tvdv7b,task_subcomment,NA
+VisualEditor: Backspace deletes the wrong character,"The backspace button is sometimes deleting the character immediately ahead of the caret, instead of the character behind it. Other times, the backspace button functions fine, though I don't know which situations it works or doesn't work in. 
+
+For example, in [[VisualEditor:Test]], if one selects the place between the ""n"" and ""l"" in the word ""only"" on the third line and presses backspace, ""oly"" is displayed for a split second before changing to ""ony"".
+
+Tested on Chrome/IE9/FF15 on Windows 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348189080,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-wg7j7pyuulwf75hox73z,task_description,resolved
+VisualEditor: Backspace deletes the wrong character,"**orbit** wrote:
+
+This was fixed by Roan.",1349896759,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wg7j7pyuulwf75hox73z,task_subcomment,NA
+VisualEditor: Backspace deletes the wrong character,"**orbit** wrote:
+
+Leaving a note for myself... This is caused when a paragraph begins with a breaknode. The breaknode is sluggable and the slug is inserted before the breaknode. I'm going to discuss with Inez next week.",1348874855,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wg7j7pyuulwf75hox73z,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1348007700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-innmgpodu5aq5mgfve6a,task_description,resolved
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,Fixed in gerrit 36597.,1354574782,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,"Confirmed still a problem in master as of 2012-11-27; now is a properly-thrown error from ve.dm.Document.prototype.getNodeFromOffset:
+
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 26 is out of bounds ve.dm.Document.js:546
+ve.dm.Document.getNodeFromOffset ve.dm.Document.js:546
+ve.dm.Surface.change ve.dm.Surface.js:212
+ve.ce.Surface.onSelectionChange ve.ce.Surface.js:260
+[...]",1354059513,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,Reassigning to Trevor because Rob is out,1353115172,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,Pushing to next milestone as they did not make it to master by yesterday.,1352832078,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,Confirmed still an issue.,1350326626,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,"The correct stack error for this is:
+Uncaught TypeError: Cannot read property 'html/data-parsoid' of undefined ve.js:357
+ve.compareObjects ve.js:357
+ve.dm.Transaction.newFromContentBranchConversion ve.dm.Transaction.js:284
+ve.ui.ListButtonTool.list ve.ui.ListButtonTool.js:66
+ve.ui.ListButtonTool.onClick ve.ui.ListButtonTool.js:175
+VeUiButtonTool.tool.$.on.mouseup ve.ui.ButtonTool.js:40
+jQuery.event.dispatch load.php:3060
+jQuery.event.add.elemData.handle.eventHandle
+
+Fixed in https://gerrit.wikimedia.org/r/25974",1349134475,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Un-listing when the caret is at the end of the document throws an error,"Details:
+
+Uncaught TypeError: Cannot read property 'annotations' of undefined ve.dm.Document.js:529
+> ve.dm.Document.getAnnotationsFromOffset ve.dm.Document.js:529
+> ve.dm.Surface.change ve.dm.Surface.js:123
+> ve.ui.ListButtonTool.unlist ve.ui.ListButtonTool.js:161
+> ve.ui.ListButtonTool.onClick ve.ui.ListButtonTool.js:177
+> VeUiButtonTool.tool.$.on.mouseup ve.ui.ButtonTool.js:40
+> jQuery.event.dispatch load.php:3060
+> elemData.handle.eventHandle",1349116126,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-innmgpodu5aq5mgfve6a,task_subcomment,NA
+VisualEditor: Support templates,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=46521",1345761720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_description,resolved
+VisualEditor: Support templates,"**vladjohn2013** wrote:
+
+Hi, this project is still listed at  https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Work_on_RefToolbar 
+
+Should this project be still listed in that page? If not, please remove it. If it still makes sense, then it could be moved to the ""Featured projects"" section if it has community support and mentors.",1385912543,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"The main template editing functionality is now live. Though there are some fixes to make, I'm marking this one as closed.",1371609890,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,Change-Id: I9174ed7c9012522246a6defc859276bf36763f5b,1368646678,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"VE will support template editing quite soon (famous last words!) which will replace (alongside the TemplateData extension) pretty much all of what the RefToolbar does in terms of telling users how to use the templates and what each parameter means.
+
+We should certainly look at some accessor functionality to make it easy and obvious when in a reference to know what templates to use, but that would be in longer time.
+
+My concern is that we're currently targetting this landing in the middle of the GSoC period - too late for someone working on GSoC to react to it and extend it, and so soon into the period (and so obviously-about-to-happen) to make working on the area that VE will replace it. :-(",1364245751,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"**brassratgirl** wrote:
+
+Fair enough. Maybe the project should be ""work on citation stuff"" broadly -- not sure how to frame that :) There is plenty of work that should overlap between the reftoolbar and the VE, though; like figuring out what citation template parameters need to be used, figuring out how to work with Lua conversions, and so on. I wonder if reftoolbar could be converted into a VE plugin -- the interface is actually pretty good, no need to reinvent the wheel on handling citations.",1364245075,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"Phoebe is recommending to Work_on_RefToolbar improvements at
+http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Work_on_RefToolbar
+
+However, I wonder whether our focus shouldn't be put in VisualEditor support for the Cite templates, either out of the box or via plugin. Any advice?",1364187670,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,*** Bug 46520 has been marked as a duplicate of this bug. ***,1364167729,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support templates,"Maybe this ""Template Parameter Wizard"" is of some interest:
+
+http://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_103#Template_Parameter_Wizard",1357401262,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-fsq7dtwwt7ruqbvnri5t,task_subcomment,NA
+VisualEditor: Support categories,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345761720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-txytmd2sbsfb7usyegll,task_description,resolved
+VisualEditor: Support categories,"Now live in master, going out in tomorrow's branch.",1370485998,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Support categories,Speculatively putting this in the -27 deploy.,1368323555,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Support categories,DM support for categories in https://gerrit.wikimedia.org/r/55120,1363988651,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Support categories,Fixing test broken by 50045 https://gerrit.wikimedia.org/r/#/c/53180/,1363020764,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Support categories,https://gerrit.wikimedia.org/r/#/c/50045/,1363017773,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-txytmd2sbsfb7usyegll,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,"The edit summary length counter (which counts backwards from 255) counts characters, not bytes. However, in languages that heavily rely on unicode charaters, a character is usually more than a byte.
+
+When saving an edit with a summary that is accepted by the counter but with more than 255 bytes, a part of the summary is cut off.
+
+Ceterum censeo bug 4715 esse delendam.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=4715",1345637520,PHID-USER-j27ofmod3h6tzafsujyq,False,PHID-TASK-yhyqhzgc2jfbifybi6up,task_description,resolved
+VisualEditor: Edit summary length counter counts characters instead of bytes,"Fixed in I25e93862a39134961bf80835f46cbf531d8109e0.
+
+Though see also bug 40035.",1346892931,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,"Should use either $.fn.byteLimit (jquery.byteLimit) or $.byteLength (jquery.byteLenght).
+
+byteLength is for calculating the byte count, byteLimit is an application of that but VE might need its own implementation.",1345820343,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,"Oh, I was describing the comment for the normal editor. Yes, the comment counter for the visual editor seems wrong. Sorry.",1345640999,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,Is that a recent fix? On https://www.mediawiki.org/wiki/VisualEditor:Test it does not work as described by you (though it might be that the live version is out of date).,1345638543,PHID-USER-j27ofmod3h6tzafsujyq,False,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Edit summary length counter counts characters instead of bytes,"The db accepts 255 bytes. The php code sets the input maxlength to 250 (instead of 255) to account for some of that overhead, and then a javascript is used to adjust it to the real space.
+This is a fixed duplicate, unless it is somehow not working right.",1345637951,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-yhyqhzgc2jfbifybi6up,task_subcomment,NA
+VisualEditor: Select all then replace causes 'Return' to act as 'cursor-left' in Heading mode,"To reproduce:
+
+Go to a blank VisualEditor page, click edit, change entry mode to Heading 1 (or whichever Heading mode), select all (Ctrl-A or Cmd-A), type in some content, press 'Return'.
+
+The content will appear (subject to bug 39517), but the 'Return' will cause the cursor to move to the left rather than inserting a newline. Indeed, further 'Returns' will insert newlines only to split a Heading, or when transitioning to a Paragraph or Pre-formatted block.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=39517",1345503180,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mvbvbyjoydgdze5uwazb,task_description,resolved
+VisualEditor: Select all then replace causes 'Return' to act as 'cursor-left' in Heading mode,"**orbit** wrote:
+
+I just fixed this here:
+https://gerrit.wikimedia.org/r/#/c/21397/
+
+This fix should release to mediawiki.org on September 3.",1345846642,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-mvbvbyjoydgdze5uwazb,task_subcomment,NA
+VisualEditor: #<nowiki><p>http://www.wikipedia.de</p></nowiki> round-trips to #<nowiki><p><p>http://www.wikipedia.de</p></p></nowiki>,"http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&diff=569290&oldid=569131
+
+I didn't touch Line 29 at all.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1344201300,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-6xoak4ts4kf6g44ewytz,task_description,resolved
+VisualEditor: #<nowiki><p>http://www.wikipedia.de</p></nowiki> round-trips to #<nowiki><p><p>http://www.wikipedia.de</p></p></nowiki>,"This is completely fixed on my localhost. In production, it's kind of fixed but not completely, see https://www.mediawiki.org/w/index.php?title=VisualEditor%3ABug39059&diff=571884&oldid=571883 .",1344907812,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6xoak4ts4kf6g44ewytz,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode","Steps to reproduce:
+* Go to a page
+* Switch to Edit mode
+* Switch to Read mode
+* Go to a different page (e.g. ""View history"" or ""Main Page"")
+
+> Uncaught TypeError: Cannot call method 'getModel' of null
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343783700,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7fkwhekj4glhqvjvdax3,task_description,resolved
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode",Fixed a long time ago (September?). Closing.,1392750003,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode","Not fixed - that fixes a type error for undefined, not a range error.",1372388545,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode",Resolved in I13a2f02d256937b7da3aca3ad3c3404bd8f31244 by checking that the surface object was still around before using it.,1345671883,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode","Also:
+
+> Uncaught RangeError: Maximum call stack size exceeded
+> >  jQuery.extend.proxy.proxy
+> >  ve.init.mw.ViewPageTarget.onBeforeUnload
+> >  jQuery.extend.proxy.proxy
+> >  ve.init.mw.ViewPageTarget.onBeforeUnload
+> >  [..]
+> >  jQuery.extend.proxy.proxy
+> >  ve.init.mw.ViewPageTarget.onBeforeUnload
+> > jQuery.extend.proxy.proxy
+> >  ve.init.mw.ViewPageTarget.onBeforeUnload",1343802836,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+"VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from ""Read"" mode","Either onbeforeunload() needs logic that we might have already torn down the surface and not complain if that's happened, or we need to not clean up after switching from the Edit tab to the Read tab. :-)",1343785459,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7fkwhekj4glhqvjvdax3,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"The `position` CSS attribute is allowed in wikitext and TemplateStyles CSS; it can be used to position parts of the user-generated content in places which are normally software-generated, e.g. on top of the sidebar menu or the search box. (Depending on the skin, `z-index` might or might not be also needed to achieve this.) A similar effect can be achieved with negative margins as well.
+
+This is occasionally used for vandalism, e.g. [[https://hu.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Adminisztr%C3%A1torok_%C3%BCzen%C5%91fala&diff=19674665&oldid=19670961|flipping the contents of the page]] or [[https://en.wikipedia.org/w/index.php?title=Module:Dynkin&diff=prev&oldid=669919700|obscuring everything using absolute or fixed positioning]]. This is confusing for patrollers as it also affects difflinks, but still relatively easy to revert using the undo/rollback links in recent changes / page history / etc.
+In theory it could also be used for more dangerous things, by overlaying transparent links on top of clickable areas of the interface area it's possible to hijack clicks.
+[[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5392|CVE-2012-5392]] has been reserved for this.
+
+On the other hand, positioning is a fundamental part of anything with a nontrivial amount of formatting, and is regularly used in infoboxes, amboxes and similar templates. Even the ability to break out of the content area is (ab)used for displaying various indicators on top of the page (such as a featured star, or the coordinates of the article subject). [[https://www.mediawiki.org/wiki/Help:Page_status_indicators|Page status indicators]] have been provided as a replacement for this, but the old method is still being used, so fixing this issue is blocked on finishing that migration. (See T135802#2332298 for some problems communities have with using indicators.) They are also used decoratively on user pages (e.g. to modify the site logo); breaking that probably would not be the end of the world.
+
+Some potential solutions that were dicussed in the comments:
+* Make the content are a stacking context (done in df10f03a7a28) and make sure everything else has a higher z-index (and non-transparent background, although positioning content behind a transparent interface block is harder to abuse). This would have to be done for every skin.
+* Make the content area `overflow: hidden` (and either ban `position: fixed`, or make the content area a 3D rendering context). See T40848#1913661 for more details.
+* Use [[https://caniuse.com/#feat=css-containment|CSS containment]]. Not widely supported yet though.
+
+Per T40848#1938655 the plan is to use `overflow: hidden`, first on a larger area so it's still possible to overlay the interface area where status indicators are, then on the content area once status indicator migration is finished. Status indicator blocks themselves would have to be secured (T135802). ",1343661300,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_description,open
+Security: CSS positioning can be used to break out of the content area,"Given @matmarex' notes above and some additional discussion off-Phab, I'm comfortable making this bug public due to its age, its likely risk and the confounding factors described by @matmarex above.",1669060154,PHID-USER-dccizlq7dtc2zihfk7cd,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"One of the places this came up was T322702, where the proposed patch would change the behavior of legacy Vector to this [see test case in my previous comment]:
+| Before | After
+| -- | --
+| {F35735231} | {F35735298} |
+
+I left a -1 on the patch referring to this task, and I think we should find a different way to solve that (an overlay as proposed by Sam), but I'm not sure if we're still treating this as a security issue. This problem has been known for years (looks like we missed the 10th anniversary in July…), without being fixed in any other skins, and it has become newly broken in new Vector. Do we still care? (I think we should, but I'd like to hear some third opinions.)
+
+Also – this problem has been known for years, there are many references to it in public on the wikis and in other tasks, and the fact that it's secret makes it difficult to explain to people why positioning on Vector is the way it is, and easy to forget the purpose of these styles (as evidenced by new Vector losing the fix, and the proposed patch for legacy Vector). Could we make this task public?",1668030092,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"This problem came up a few times recently, so I wanted to check the current status.
+
+I am using the following as a test case, just putting it on a wikitext page:
+```lang=html
+<div style=""background: grey; position: fixed; z-index: 999999; top: 0; left: 0; bottom: 0; right: 0;""></div>
+```
+
+Except for legacy Vector, all skins deployed on Wikimedia wikis (including new Vector) are vulnerable :
+| vector | vector-2022 | minerva | monobook | timeless | cologneblue | modern
+| -- | -- | -- | -- | -- | -- | --
+| {F35735231} | {F35735233} | {F35735235} | {F35735237} | {F35735239} | {F35735241} | {F35735243}
+| Okay! (although some nav elements are transparent) | Fail  | Fail  | Fail  | Fail  | Fail (deprecated skin) | Fail (deprecated skin)
+",1668029238,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,Indeed,1629215003,PHID-USER-ctchvhisqfvk4rz7nt7d,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Yes, it used `position:fixed` ([[https://en.wikipedia.org/w/index.php?title=Template:Wbr&diff=1039070194&oldid=1039070019&unhide=1&diffmode=source|diff]]; now revdeleted). Although I doubt that limiting the image to the content area would have reduced the impact much.",1629157949,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,I don't know if the attacks today (https://www.businessinsider.com/wikipedia-pages-briefly-showed-pictures-of-swastikas-2021-8) took advantage of this security issue or not but it looks like it.,1629129396,PHID-USER-ctchvhisqfvk4rz7nt7d,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"cc @Jdrewniak who's working on a DOM restructuring in new Vector, and needs to know about this issue so he can make sure the fix for this is maintained",1601310218,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Yeah, `contain: content` will perform better than `overflow: hidden`, but has imho a different semantic purpose and meaning. Either way, it's too new to cover us from a security perspective. Either way, this is blocked in migration of indicators to use <https://www.mediawiki.org/wiki/Help:Page_status_indicators>. Last I checked, many major wikis still aren't using it (much) yet.
+
+See T40848#1938655 and T40848#1913661 for the next steps after that.",1487996779,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"https://developer.mozilla.org/en-US/docs/Web/CSS/contain describes the CSS Containment Module 3, which is supported in Chrome 52 & up. This modules offers a general way to restrict the rendering of styled content to its parent element's dimensions: `contain: content`",1485474766,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"https://developer.mozilla.org/en-US/docs/Web/CSS/contain describes the CSS Containment Module 3, which is described as supported in Chrome 52 & up. This modules offers a general way to restrict the rendering of styled content to its parent element's dimensions: `contain: content`",1485474738,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"It would probably be possible to sandbox away the content area (make sure the top skin, left skin and content are in different stacking contexts and the skin ones have positive z-index). There is no way for content in a stacking context to ever overlap content in sibling stacking contexts with higher z-index, even with `position:fixed`.",1485474759,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"It would probably be possible to sandbox away the content area (make sure the top skin, left skin and content are in different stacking contexts and the skin ones have positive z-index. There is no way for content in a stacking context to ever overlap content in sibling stacking contexts with higher z-index, even with `position:fixed`.",1485474733,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Negative margins combined with z-index can be used for similar re-dressing attacks. Example:
+
+ <div style=""margin-top: -340px; margin-left: 100px; color: red"">Hello there</div>",1485473964,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Negative margins combined with z-index can be used for similar attacks. Example:
+
+ <div style=""margin-top: -340px; margin-left: 100px; color: red"">Hello there</div>",1485473941,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Just to comment that `position:fixed` also affect extensions, such as Flow. I suggest sanitize it completely.",1453246689,PHID-USER-lprp4ui4cwnnwdkp4vyj,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I chatted with Krinkle about this bug yesterday, I think we have a clear roadmap for fixing it. We'll start by pushing method A to our sites, which is the least risk to our sites. It will affect some users who have updated their user pages to ""customize"" the wiki logo, so those users will notice as soon as we patch the cluster. Due to that, we'll need to push the fix to our sites, and release this as a mediawiki tarball update in quick succession. We'll time it so that we also alert ambassadors and tech-news, so that technical people in the movement all hear about this soon after we push it onto the site.
+
+Once that is in place, we'll work towards change C as a public followup. Wikis will need some time to finish converting indicators, and we can test ways of fixing the margin collapse issue.
+
+Before we can start this, we need to do some more testing with method A. Maybe we can use Tim's visual-diff to see what it would affect. Target of Early Feb might be realistic.",1452905131,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"In light of recent attacks, reviving this task.
+
+First of all, the current state of things has changed over the past year. Some layer security patches have been applied as part of other security bugs.
+
+Current state of Vector (using example code from T40848#425108):
+
+{F3198387}
+
+* Logo: Safe, but transparent
+* Sidebar: Safe, but transparent
+* Personal: Safe, but transparent
+* Page tabs: Safe, but transparent
+* Search: Safe, but transparent
+* Sitenotice: Not safe
+* Page name: Not safe
+
+""Safe"" refers to the visibility and click-ability of the above listed components' contents. Not their container overall. Meaning, an attacker is not able to change the link target of any of our user interface links and cannot overlap e.g. the logo. However, as you can see, the space in between the sidebar links and page tabs etc is still vulnerable because things can be layered underneath. This is why the z-index approach is only effective as an attack, not as a defence.
+
+Overflow-hidden is still the best way forward. However as mentioned, this is non-trivial because of established use cases from the community surrounding ""hacks"" that place icons outside the page content area (e.g. Geo coordinates, Featured article status, Spoken Wikipedia, etc.). This use case has been recognised by MediaWiki in 2014 in the MediaWiki 1.25 release cycle ([mw:Help:Page status indicators](https://www.mediawiki.org/wiki/Help:Page_status_indicators)). I don't know how well this has been adopted by now. I'd say we give communities a heads up through mailing lists, ambassadors and tech news and then go ahead with it.
+
+Proposed change A:
+```lang=css
+.mw-body {
+    overflow: hidden;
+}
+```
+
+Impact:
+{F3198404}
+
+This has no bad side sides (compared to status quo) and protects transparency from all currently safe areas. It still leaves page title and site notice unsafe, however. This proposal exists because of the side effects and complications with the following proposals. I'd recommend this as a transitional change to cover most of our problem space while we work on the rest.
+
+Proposed change B:
+```lang=css
+.mw-body-content {
+    overflow: hidden;
+}
+```
+{F3198430}
+
+
+This makes all listed areas safe (including the previously unsafe site notice and page title). Side effects:
+* This would break any ""top icons"" and ""indicators"" that haven't migrated from absolute-position to using `<indicator>` yet. (Because change B shrinks the overflow area from mw-body to mw-body-content, meaning content can't overlay icons and images next to the page title. An otherwise desirable change.)
+* This breaks anti-margin collapse between contentSub and elements inside the text content. This element is unfortunately within mw-body-content in most skins. It is empty by default and enjoys CSS auto margin collapse and takes up no space. Setting overflow-hidden on its container (mw-body-content) means it is no longer able to collapse its margin with the page title. As such, creating a relatively large white gap between the page title and the start of the content.
+
+Proposed change C:
+```lang=css
+#mw-content-text {
+    position: relative;
+    overflow: hidden;
+}
+```
+{F3198450}
+
+This makes all listed areas safe (including the previously unsafe site notice and page title). Side effects:
+* Breaks any indicators that haven't migrated yet (same as B).
+* This breaks margin collapse between page title (firstHeading) and page content . Even if we move out `contentSub` to be child of mw-body directly before mw-body-content, the same effect will still affect margin collapse between the first heading of the content area. We can probably avoid that by setting margin-bottom to zero for the page title.",1452824841,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"In light of recent attacks, reviving this task.
+
+First of all, the current state of things has changed over the past year. Some layer security patches have been applied as part of other security bugs.
+
+Current state of Vector (using example code from T40848#425108):
+
+{F3198387}
+
+* Logo: Safe, but transparent
+* Sidebar: Safe, but transparent
+* Personal: Safe, but transparent
+* Page tabs: Safe, but transparent
+* Search: Safe, but transparent
+* Sitenotice: Not safe
+* Page name: Not safe
+
+""Safe"" refers to the visibility and click-ability of the above listed components' contents. Not their container overall. Meaning, an attacker is not able to change the link target of any of our user interface links and cannot overlap e.g. the logo. However, as you can see, the space in between the sidebar links and page tabs etc is still vulnerable because things can be layered underneath. This is why the z-index approach is only effective as an attack, not as a defence.
+
+Overflow-hidden is still the best way forward. However as mentioned, this is non-trivial because of established use cases from the community surrounding ""hacks"" that place icons outside the page content area (e.g. Geo coordinates, Featured article status, Spoken Wikipedia, etc.). This use case has been recognised by MediaWiki in 2014 in the MediaWiki 1.25 release cycle ([mw:Help:Page status indicators](https://www.mediawiki.org/wiki/Help:Page_status_indicators)). I don't know how well this has been adopted by now. I'd say we give communities a heads up through mailing lists, ambassadors and tech news and then go ahead with it.
+
+Proposed change A:
+```lang=css
+.mw-body {
+    overflow: hidden;
+}
+```
+
+Impact:
+{F3198404}
+
+This has no bad side sides (compared to status quo) and protects transparency from all currently safe areas. It still leaves page title and site notice unsafe, however. This proposal exists because of the side effects and complications with the following proposals. I'd recommend this as a transitional change to cover most of our problem space while we work on the rest.
+
+Proposed change B:
+```lang=css
+.mw-body-content {
+    overflow: hidden;
+}
+```
+{F3198430}
+
+
+This makes all listed areas safe (including the previously unsafe site notice and page title). Side effects:
+* This would break any ""top icons"" and ""indicators"" that haven't migrated from absolute-position to using `<indicator>` yet. (Because change B shrinks the overflow area from mw-body to mw-body-content, meaning content can't overlay icons and images next to the page title. An otherwise desirable change.)
+* This breaks anti-margin collapse between contentSub and elements inside the text content. This element is unfortunately within mw-body-content in most skins. It is empty by default and enjoys CSS auto margin collapse and takes up no space. Setting overflow-hidden on its container (mw-body-content) means it is no longer able to collapse its margin with the page title. As such, creating a relatively large white gap between the page title and the start of the content.
+
+Proposed change C:
+```lang=css
+#mw-content-text {
+    position: relative;
+    overflow: hidden;
+}
+```
+{F3198450}
+
+This makes all listed areas safe (including the previously unsafe site notice and page title). Side effects:
+* Breaks any indicators that haven't migrated yet (same as B).
+* This breaks margin collapse between page title (firstHeading) and page content . Even if we move out `contentSub` to be child of mw-body directly before mw-body-content, the same effect will still affect margin collapse between the first heading of the content area. We can probably solve this by setting margin-bottom to zero for the page title.",1452824832,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"In light of recent attacks, reviving this task.
+
+First of all, the current state of things has changed over the past year. Some layer security patches have been applied as part of other security bugs.
+
+Current state of Vector (using example code from T40848#425108):
+
+{F3198387}
+
+* Logo: Safe, but transparent
+* Sidebar: Safe, but transparent
+* Personal: Safe, but transparent
+* Page tabs: Safe, but transparent
+* Search: Safe, but transparent
+* Sitenotice: Not safe
+* Page name: Not safe
+
+""Safe"" refers to the visibility and click-ability of the above listed components' contents. Not their container overall. Meaning, an attacker is not able to change the link target of any of our user interface links and cannot overlap e.g. the logo. However, as you can see, the space in between the sidebar links and page tabs etc is still vulnerable because things can be layered underneath. This is why the z-index approach is only effective as an attack, not as a defence.
+
+Overflow-hidden is still the best way forward. However as mentioned, this is non-trivial because of established use cases from the community surrounding ""hacks"" that place icons outside the page content area (e.g. Geo coordinates, Featured article status, Spoken Wikipedia, etc.). This use case has been recognised by MediaWiki in 2014 in the MediaWiki 1.25 release cycle ([mw:Help:Page status indicators](https://www.mediawiki.org/wiki/Help:Page_status_indicators)). I don't know how well this has been adopted by now. I'd say we give communities a heads up through mailing lists, ambassadors and tech news and then go ahead with it.
+
+Proposed change A:
+```lang=css
+.mw-body {
+    overflow: hidden;
+}
+```
+
+Impact:
+{F3198404}
+
+This has no bad side sides (compared to status quo) and protects transparency from all currently safe areas. It still leaves page title and site notice unsafe, however. This proposal exists because of the side effects and complications with the following proposals. I'd recommend this as a transitional change to cover most of our problem space while we work on the rest.
+
+Proposed change B:
+```lang=css
+.mw-body-content {
+    overflow: hidden;
+}
+```
+{F3198430}
+
+
+This places all listed areas in safety (including the previously unsafe site notice and page title). Side effects:
+* This would break any ""top icons"" and ""indicators"" that haven't migrated from absolute-position to using `<indicator>` yet. (This shrinks the overflow area from mw-body to mw-body-content, meaning content can't overlay icons and images next to the page title. An otherwise desirable change.)
+* This breaks `<div id=""contentSub"">` anti-margin collapse. This element is unfortunately within mw-body-content in most skins. It is empty by default and enjoys CSS auto margin collapse and takes up no space. Setting overflow-hidden on its container (mw-body-content) means it is no longer able to collapse its margin with the page title. As such, creating a relatively large white gap between the page title and the start of the content.
+
+Proposed change C:
+```lang=css
+#mw-content-text {
+    position: relative;
+    overflow: hidden;
+}
+```
+{F3198450}
+
+This places all listed areas in safety (including the previously unsafe site notice and page title). Side effects:
+* Breaks any indicators that haven't migrated yet (same as B).
+* This breaks content heading anti-margin collapse. Even if we move out `contentSub` to be child of mw-body directly before mw-body-content, the same effect will still affect margin collapse between the first heading of the content area (e.g. wikiPreview's ""Preview"" in the screenshot, or something like the heading atop the sandbox page). This creates an even bigger gap. Something that could be worked around by targeting the first mw-heading and cancelling its top margin manually. I'd like to avoid this as it significantly complicates future changes.",1451854681,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,">>! In T40848#1449889, @csteipp wrote:
+> Krinkle mocked up the interface if we also had overflow: hidden, and the result visually (imo) looks much less like a security issue and more like vandalism,
+> 
+>> If we had done overflow-hidden, the page would've looked like this: http://i.imgur.com/TrPeYxG.png
+>> Instead of the current: http://i.imgur.com/MFN8cBo.png
+> 
+> @Krinkle, can you post the style updates that you used to get that result? It looks as Trevor said, setting overflow:hidden isn't quite enough.
+
+It turns out that result was a lucky match between screen height and the exact code used by that piece of vandalism. It used `width: 100%; height: 100%;` which means in an overflow scenario with sufficient page content and a short window, it wouldn't extend far enough to peak out.
+
+Ignoring `position: fixed` for a second (see T123811 for that), `overflow: hidden` is enough and addresses this issue entirely for both Vector, MonoBook and any other skin. The core patch will affect modern skins using the `mediawiki.skinning` base; other skins can adopt the same in their own CSS.
+
+As for `position: fixed`. That can be reliably addressed by giving the content its own rendering context using `transform: translateZ(0);`. See http://jsfiddle.net/Loezmm7y/4/. However that impacts rendering performance. Supported in 90%+ of browsers per http://caniuse.com/#feat=transforms2d (not in IE<=8).
+
+However I suggest we simply forbid `position: fixed` in the Sanitizer. I don't see any valid use case for it. Fixed position is bound to rendering context (= window by default) and can always peek out if allowed. The original issue here was absolute position and relative position.",1452902490,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,">>! In T40848#1449889, @csteipp wrote:
+> Krinkle mocked up the interface if we also had overflow: hidden, and the result visually (imo) looks much less like a security issue and more like vandalism,
+> 
+>> If we had done overflow-hidden, the page would've looked like this: http://i.imgur.com/TrPeYxG.png
+>> Instead of the current: http://i.imgur.com/MFN8cBo.png
+> 
+> @Krinkle, can you post the style updates that you used to get that result? It looks as Trevor said, setting overflow:hidden isn't quite enough.
+
+It turns out that result was a lucky match between screen height and the exact code used by that piece of vandalism. It used `width: 100%; height: 100%;` which means in an overflow scenario with sufficient page content and a short window, it wouldn't extend far enough to peak out.
+
+Ignoring `position: fixed` for a second, `overflow: hidden` is enough and addresses this issue entirely for both Vector, MonoBook and any other skin. The core patch will affect modern skins using the `mediawiki.skinning` base; other skins can adopt the same in their own CSS.
+
+As for `position: fixed`. That can be reliably addressed by giving the content its own rendering context using `transform: translateZ(0);`. See http://jsfiddle.net/Loezmm7y/4/. However that impacts rendering performance. Supported in 90%+ of browsers per http://caniuse.com/#feat=transforms2d (not in IE<=8).
+
+However I suggest we simply forbid `position: fixed` in the Sanitizer. I don't see any valid use case for it. Fixed position is bound to rendering context (= window by default) and can always peek out if allowed. The original issue here was absolute position and relative position.",1436812682,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(documenting my email to security@, and Timo's writeup)
+
+Last week Jerry Hoff from WhiteHat Security posted https://twitter.com/jerryhoff/status/617340137689755653?s=03.
+
+> The page the Twitter user in question was viewing is:
+> https://en.wikipedia.org/wiki/Thomas_Sowell
+> 
+> This page uses Template:Hlist in the infobox, which was changed briefly to include Lua Module ""Dynkin"" (edit made by an experienced user):
+> https://en.wikipedia.org/w/index.php?title=Template:Hlist&diff=prev&oldid=669920021
+> 
+> Which in turn was vandalised to include the red box (edit made by an anonymous user):
+> https://en.wikipedia.org/w/index.php?title=Module:Dynkin&diff=prev&oldid=669919700
+
+Because https://gerrit.wikimedia.org/r/#/c/178086/ was deployed last December, on Vector
+
+> So all that happened is a big red box was displayed *behind* the interface menus.
+
+For monobook, much of the interface was obscured. Fixing this issue on monobook seems unlikely.
+
+Krinkle mocked up the interface if we also had overflow: hidden, and the result visually (imo) looks much less like a security issue and more like vandalism,
+
+> If we had done overflow-hidden, the page would've looked like this: http://i.imgur.com/TrPeYxG.png
+> Instead of the current: http://i.imgur.com/MFN8cBo.png
+
+@Krinkle, can you post the style updates that you used to get that result? It looks as Trevor said, setting overflow:hidden isn't quite enough.",1436807288,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,">>! In T40848#1122583, @Anomie wrote:
+> Hiding overflow will also hide content when someone with a very wide screen resolution makes something that won't fit for people with lower resolutions. Horizontal scrollbars suck, yes, but is just cutting it off necessarily better?
+
+This task is about elements placing themselves outside the content area to overlap interface elements. Capturing overflow doesn't mean it has to be inaccessible. `overflow: auto;` (e.g. scroll when overflow) would work just as well. The scrollbar would be on the content area instead of on the window. Unless scrolled to the bottom of the page the user wouldn't notice much difference in behaviour. Except that the excess content would be correctly displayed on a white background instead of against the outer the skin body (which is grey in Vector).
+
+Example: https://codepen.io/Krinkle/debug/eNEwYo.
+
+The only difference is that (on desktop) the sidebar would stay in view. On mobile the sidebar may be out of view depending on the viewport and how far away you scroll (virtual depth is applied). This is making its way to desktop browsers as well.
+
+http://www.quirksmode.org/mobile/viewports.html
+http://www.androidpolice.com/2015/01/09/chrome-beta-v40-new-zoom-behavior-makes-fixed-headers-scrollable-less-aggravating/",1434565219,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Hiding overflow will also hide content when someone with a very wide screen resolution makes something that won't fit for people with lower resolutions. Horizontal scrollbars suck, yes, but is just cutting it off necessarily better?",1426533532,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Giving content its own rendering context (e.g. using `translateZ(0)`) would also restrict `position: fixed;`. It's similar to ""visual"" security provided by iframes. Perhaps `overflow: hidden;` and translate can be used together.
+
+Note that mw-indicators has been introduced in MediaWiki core and projects can now migrate templates such as Coordinates, Featured article etc. to using that instead. Which, to my knowledge, was the last remaining (valid) use case for allowing position: absolute; outside the content area. Which means, once migration period settles, we are free to apply `overflow: hidden;`. We may want to additionally add z-indexes in various places, but we should hide overflow no matter what.",1426532220,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Turns out applying overflow: hidden to .mw-body doesn't solve for fixed positioned content[1].
+
+I looked at various techniques, including using backface-hidden which works in certain cases on certain browsers, but nothing appears to be reliable.
+
+The only safe approach I can see is to combine z-indexing with obscuring content behind UI areas using positioned divs that fully block out the UI area and have opaque backgrounds[3].
+
+[1] https://en.wikipedia.org/wiki/User_talk:Bababa67
+[2] http://jsfiddle.net/w119kpwL/
+[3] http://jsfiddle.net/Loezmm7y/1/",1421358403,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"The Vector skin has been moved into a separate repository and the element is now targeted as `.mw-body-content` instead of `#bodyContent`.
+
+Part of task has been resolved with T76965.",1417984117,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,*** Bug 24667 has been marked as a duplicate of this bug. ***,1415456361,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I see you've found the issue with the navigation tabs in monobook. Those rely on the content being on top because they are longer than they have to be.
+
+Note that these are longer on purpose because of relative font-size differences on different browsers. I see you shortened them to arbitrary values 0.2em and 0.3em.
+
+Presumably, after you moved the content behind the tabs and removed the z-index from the tabs, you trimmed those values until they no longer stick out, but not so short that they leave a gap and would no longer touch the content container.
+
+As you can guess by now, those em values would expand to different sizes and most certainly in one of the browsers Monobook supports this will now leave a gap (as if they're shorter), or cause an ugly border to stick it (as if they're longer).",1399246331,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15282
+Patch for Monobook
+
+Changed it to use #column-one > *, which seems to work.
+
+**Attached**: {F9561}",1399068340,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to Chris Steipp from comment #58)
+> Which seems to fix the issue, but would break some of the widgets that
+> position elements outside of the content area. Do those usually work with
+> monobook?
+
+Yes, they do. And since this would break common things like enwiki's ""featured article"" star, I recommend against doing this.
+
+A better fix would be to apply the z-index to the contents of div#column-one rather than to the whole thing; you could either target them individually by id or by targeting something like ""#column-one > *"" (do we still care about browsers old enough to not support "">""?).",1399048997,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I wasn't seeing a great way to fix monobook with z-index=0, so I used another fix that Krinkle had also mentioned
+
+#bodyContent {
+	position: relative;
+	overflow: hidden;
+}
+
+Which seems to fix the issue, but would break some of the widgets that position elements outside of the content area. Do those usually work with monobook? I looked at https://en.wikivoyage.org/wiki/Clearwater with Vector and Monobook, and the map widget is gone in monobook.",1399046601,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Thanks Bartosz,
+
+Testing this on my dev system, the monobook patch doesn't seem to be working right. Since div#column-one covers over the top of everything in the content area, it prevents clicking on any forms / links in that area. So it breaks all special pages.
+
+I'm testing it on master as of this afternoon, so might be a recent change?",1398982508,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15223
+Patch for Modern
+
+**Attached**: {F9560}",1398601963,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15222
+Patch for Monobook
+
+I ended up just guessing better padding values for the tabs to allow them to always have a higher z-index than content.
+
+At first I tried to properly calculate the necessary heights and to not mix pixels and ems, but it required changing the code considerably (mostly to keep IE6 from breaking). The end result was not really prettier than what we have now, and definitely not something appropriate for a security patch.
+
+//attachment 0003-SECURITY-Monobook-Secure-interface-layer-from-page-c.patch ignored as obsolete//",1398601909,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15221
+Patch for CologneBlue
+
+**Attached**: {F9559}",1398601483,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 15220
+Patch for Vector
+
+Patch from attachment 14981 no longer applies, here's a rebased version.
+I'm going to work on patches for other skins today (finally; sorry for the delay).
+
+I'm using this very simple test case:
+  <div style=""background: red; position: fixed; z-index: 999999;
+  top: 0; left: 0; bottom: 0; right: 0;"">&nbsp;</div>
+…and verifying that all of the elements listed by Krinkle in earlier comments (logo, sidebar, personal, tabs, search, sitenotice, page name) are visible and clickable (unless any of them are missing in given skin, of course).
+
+**Attached**: {F9558}",1398594547,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to Bartosz Dziewoński from comment #51)
+> My personal opinion is that we should either WONTFIX this bug
+
+I disagree. The advantage to fixing this bug, even if it's not perfect with respect to the TOC and other in-content ""chrome"", is that when some vandal tries to take advantage of it then people don't have to know about manually editing the URL to include ""?action=edit"" to be able to fix it.",1397053662,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"For Monobook, we could make the top border of content area be actually generated by <div id=""p-cactions""/> or one of its descendants, which should make applying Krinkle's idea reasonably straightforward. (Or, someone could sit down with pen and paper and actually calculate what exactly is the height of the tabs, with all of the em sizings applied, which would let us avoid z-index hacks.)
+
+Modern and CologneBlue should also be straightforward to adjust.
+
+I could do that (when I find the time, probably the soonest could be this weekend), but I'm not entirely sure if the fix is really worth the effort: we would still have important UI bits interspersed with the content (table of contents, section edit links), and the whole exercise is rendered pointless if such easily exploitable elements remain. (Moving them out of content would require a pretty big redesign of all skins, including third-party ones.)
+
+My personal opinion is that we should either WONTFIX this bug (I actually thought that this ""bug"" was almost common knowledge…) or combine Krinkle's solution with something that would also protect inter-content chrome (possibly the z-index limiting mentioned earlier, if we can't come up with anything less nasty – I'm all out of ideas). But I can prepare the skin patches anyway.",1396994010,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"MatmaRex, Brad had noticed specifically that I07223ba4 made fixing Monobook more difficult.",1396472315,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Adding MatmaRex, in case he can help out with the Monobook and Cologne Blue skins",1396472047,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 14983
+Screenshot of test case (on master, with patch)
+
+**Attached**: {F9557}",1396302249,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 14982
+Screenshot of test case (on master, before patch)
+
+**Attached**: {F9556}",1396302212,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 14981
+Patch for Vector skin
+
+//attachment security-vector-zindex.patch ignored as obsolete//",1396302192,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Okay, updated the patch one more time with a check. A few things have changed in the Vector skin since last time.
+
+Test case:
+
+<div style=""
+ position: absolute;
+ top: -180px; left: -10%;
+ z-index: 99999;
+ width: 120%; height: 400px;
+ background: rgba(0, 0, 255, 0.8);
+ outline: 1px solid orange;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid blue;
+"">[[File:Transparent.gif|4000x4000px|link=//example.org|Click]]</div>
+<div style=""position: absolute; bottom: 0; text-align: center;"">Navigation/Search</div>
+</div>
+
+<div style=""
+ position: absolute;
+ top: -170px; left: -190px;
+ z-index: 99999;
+ width: 240px; height: 640px;
+ background: rgba(0, 255, 255, 0.8);
+ outline: 1px solid red;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""position: absolute; bottom: 0; text-align: center;"">Logo/Sidebar</div>
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid green;
+"">
+[[File:Transparent.gif|350x350px|link=//example.org|Click]]
+</div>
+</div>
+
+
+Current mediawiki/core.git@master:
+
+== Vector skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Not safe
+- Tabs:       Not safe
+- Search:     Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+After my patch:
+
+== Vector skin ==
+- Logo:       Safe
+- Sidebar:    Safe
+- Personal:   Safe
+- Tabs:       Safe
+- Search:     Safe
+- Sitenotice: Safe
+- Page name:  Safe",1396302130,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,So I'd recommend we move ahead with just the Vector fix.,1396301184,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Monobook can't get fixed, it is currently relying on insecure z-index overrides. It needs to be refactored in general.
+
+I think we can do so in public without exposing or explaining this bug though, but it's more than a bug fix, we basically need to re-make the same visual layout with a different It requires a few changes to the html as well, which always make this more complicated with regards to caching and backwards compatibility while the html cache rolls over but stylesheets are on a separate request that will roll over separately (earlier).",1395013208,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to Chris Steipp from comment #41)
+> Timo, any chance you were able to get Monobook fixed?
+
+Timo: ping?",1394632548,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #39)
+> Created attachment 13731 [details]
+> Patch for Vector skin
+> 
+> As for Monobook, can't take the same approach due to it purposely having the
+> navigation behind the content (because of the overflow of the tabs). So we'll
+> need to take a different approach there (or, preferably, refactor it to not
+> use
+> that weird nesting).
+
+Timo, any chance you were able to get Monobook fixed? It would be great to get this fixed on the cluster once fundraising's big push is done in Jan. I think Monobook is the only non-default skin that many admins use.
+
+Also adding Jared so UX is aware of this.
+
+//attachment bug38848.patch.diff ignored as obsolete//",1388098293,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"By far the easiest way to solve this problem for all skins is to apply ""overflow: hidden;"" to #mw-content-text. That is both skin agnostic (the element is output by the page output handler around only the wiki page content and nothing else) and water tight.
+
+However the difference is that that doesn't just move content to its own layer, it also restricts its boundaries. Meaning, the skin interface isn't just on top of any content sticking out, the content sticking out will be invisible (cropped) at the border of the content area.
+
+However I don't think that is feasible at the moment due to the large number of icons and semi-genuine use cases we don't yet provide natively (e.g. article quality icons, coordinates, interproject links etc.).
+
+So for now the approach we've been taking seems fine (although this time it'll actually work), which is ensuring layer security. That way none of the skin interfaces are affected (e.g. logo, personal links etc.) however any empty space outside the wikipage content that isn't covered by interface components  (e.g. the space between logo and personal links, space between logo and first sidebar link etc. anything that is colored purple or blue in the screenshot) could still be hijacked, though it is much less frighting in those cases. And that can only be prevented if we completely crop content. Which we can't do until we drop support for positioning of icons such as Featured Article, and Coordinates to the top right of the article (just outside the content area, next to the title).
+
+As crazy as it sounds, we can actually drop support for that relatively soon because we only have to drop support for icons positioned there from wikitext. Most wikis don't actually do that anymore, instead they give those templates a css classes, and move the icons to the ""proper"" place in the DOM outside the content area through site javascript. Though that is somewhat evil too, it is what we'd do in an extension as well. And from javascript, any changes uncontrollable anyway and must be presumed safe (due to user right restrictions).",1383881287,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 13731
+Patch for Vector skin
+
+As for Monobook, can't take the same approach due to it purposely having the navigation behind the content (because of the overflow of the tabs). So we'll need to take a different approach there (or, preferably, refactor it to not use that weird nesting).
+
+//attachment bug38848.patch.diff ignored as obsolete//",1383880586,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"
+Meanwhile, a year later.
+
+Updated the test html to 'cover' all skins (mostly increasing dimensions and offset).
+
+!!! If testing on production wiki, please *DO NOT SAVE* but use preview as we don't want to hand the below hack on a plate for someone to find and abuse.
+
+Content:
+
+<div style=""
+ position: absolute;
+ top: -180px; left: -10%;
+ z-index: 99999;
+ width: 120%; height: 400px;
+ background: rgba(0, 0, 255, 0.8);
+ outline: 1px solid orange;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid blue;
+"">[[File:Transparent.gif|4000x4000px|link=//example.org|Click]]</div>
+<div style=""position: absolute; bottom: 0; text-align: center;"">Navigation/Search</div>
+</div>
+
+<div style=""
+ position: absolute;
+ top: -170px; left: -190px;
+ z-index: 99999;
+ width: 240px; height: 640px;
+ background: rgba(0, 255, 255, 0.8);
+ outline: 1px solid red;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""position: absolute; bottom: 0; text-align: center;"">Logo/Sidebar</div>
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid green;
+"">
+[[File:Transparent.gif|350x350px|link=//example.org|Click]]
+</div>
+</div>
+
+
+Current mediawiki/core.git@master:
+
+== Vector skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Not safe
+- Tabs:       Not safe
+- Search:     Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+== Monobook skin ==
+- Logo:       Safe
+- Sidebar:    Not safe
+- Personal:   Safe
+- Tabs:       Not safe
+- Search:     Safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+== Modern skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Not safe
+- Tabs:       Not safe
+- Search:     Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+Monobook has weird z-index overrides all over the place. For example the
+following have an overriden z-index that made them safe for this test:
+
+- li a.selected (the selected tab in the tabs)
+- #p-search (portlet for search in the sidebar)
+- #p-logo (portlet for the logo in the sidebar)
+- #p-lang (porlet for interwiki links in the sidebar)
+
+But the other tabs or the tab bar itself, and the other portlets or the sidebar
+itself were all not safe.
+
+
+After my patch:
+
+
+== Vector skin ==
+- Logo:       Safe
+- Sidebar:    Safe
+- Personal:   Safe
+- Tabs:       Safe
+- Search:     Safe
+- Sitenotice: Safe
+- Page name:  Safe
+
+Tested to confirm proper compatibility with jQuery UI and VisualEditor dialogs and overlays etc. (e.g. personal portlet stays behind the overlay that mutes the page, as it should).",1383880423,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,Krinkle: Do you plan to rework your patch in comment 36 (as you obsoleted it)?,1378758027,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Comment on attachment 11395
+Updated combined patch for 1.21, with Brad's fixes.
+
+Obsoleting this patch set. Also I see you fell into the same clean up trap as I did for Monobook. The z-indexes there for the tabs are needed to 1) display the tabs underneath #content (since they are taller than they should be), and 2) make the selected tab go on top so it overlaps the top border of #content.",1375079731,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Meanwhile, a year later.
+
+Updated the test html to 'cover' all skins (mostly increasing dimensions and offset).
+
+!!! If testing on production wiki, please *DO NOT SAVE* but use preview we don't want to hand the below hack on a plate for someone to abuse
+
+Location: http://mw.local.dev/wiki/Sandbox?action=edit
+Content:
+
+<div style=""
+ position: absolute;
+ top: -180px; left: -10%;
+ z-index: 99999;
+ width: 120%; height: 270px;
+ background: rgba(0, 255, 255, 0.8);
+ outline: 1px solid red;
+ font-size: 2em;
+ text-align: center;
+"">
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid blue;
+"">
+[[File:Transparent.gif|4000x4000px|link=//example.org|Click]]
+</div>
+Navigation/Search overlay
+</div>
+
+<div style=""
+ position: absolute;
+ top: -170px; left: -190px;
+ z-index: 99999;
+ width: 170px; height: 340px;
+ background: rgba(0, 255, 255, 0.8);
+ outline: 1px solid red;
+ font-size: 2em;
+ text-align: center;
+"">
+Logo overlay
+<div style=""
+ position: absolute;
+ top: 0; right: 0; bottom: 0; left: 0;
+ overflow: hidden;
+ background: rgba(255, 255, 255, 0.8);
+ outline: 1px solid blue;
+"">
+[[File:Transparent.gif|350x350px|link=//example.org|Click]]
+</div>
+</div>
+
+
+Current mediawiki/core.git@master:
+
+== Vector skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Safe
+- Tab bar:    Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+== Monobook skin ==
+- Logo:       Safe
+- Sidebar:    Not safe
+- Personal:   Safe
+- Tab bar:    Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+There are weird z-index overrides all over the place. For example the following have an overriden z-index that made them safe for this test:
+
+- li a.selected (the selected tab in the tabs)
+- #p-search (portlet for search in the sidebar)
+- #p-logo (portlet for the logo in the sidebar)
+- #p-lang (porlet for interwiki links in the sidebar)
+
+But the other tabs or the tab bar itself, and the other portlets or the sidebar itself are all not safe.
+
+== Modern skin ==
+- Logo:       Not safe
+- Sidebar:    Not safe
+- Personal:   Not safe
+- Tabs:       Not safe
+- Search:     Not safe
+- Sitenotice: Not safe
+- Page name:  Not safe
+
+
+
+Working on a revised patch set now based on a more solid approach.",1375079605,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,It does. It's just been a little lower priority.,1372373729,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Chris, does this still need to happen?",1372369898,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #19)
+> In monobook, the left-hand menu is still covered up. I wasn't able to fix that.
+
+Set position:relative on .portlet?
+
+(In reply to comment #28)
+> * Sitenotice: Fail (wikipage remains on top)
+
+Since the Sitenotice is inside the #content area, that's going to be a bit difficult.",1366310500,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11403
+Screenshot of attachment 11395 fix in Modern
+
+**Attached**: {F9555}",1353518782,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11402
+Screenshot of attachment 11395 fix in Monobook
+
+**Attached**: {F9554}",1353518768,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11401
+Screenshot of attachment 11395 fix in Vector
+
+//attachment ba11395-vector.png ignored as obsolete//",1353518754,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #27)
+> Created attachment 11395 [details]
+> Updated combined patch for 1.21, with Brad's fixes.
+> 
+> Updated patch. Should apply with `git am` with current master
+
+
+Given the test of comment #2 on my local wik (with different top-offsets depending on the skin)i:
+> Location:
+> https://www.mediawiki.org/w/index.php?title=Project:Sandbox&action=edit
+> 
+> <div style=""
+> position: absolute;
+> top: -178px;
+> left: 0;
+> z-index: 2;
+> width: 100%;
+> height: 195px;
+> background: rgba(0, 255, 255, 0.2);
+> text-align: center;
+> ""> Breaks Nav </div>
+> 
+> 
+> <div style=""
+> position: absolute;
+> top: -120px;
+> left: -180px;
+> z-index: 2;
+> width: 150px;
+> height: 150px;
+> background: rgba(0, 255, 255, 0.2);
+> text-align: center;
+> ""><div style=""position: absolute; -webkit-user-select: none; -moz-user-select:
+> none; user-select: none;"">Goes to
+> Toolserver.org</div>[[File:Transparent.gif|150x150px|link=//toolserver.org|Go
+> to the Main Page, or... Tooserver.org?]]</div>
+
+
+I confirm that this patch does not effect the visual appearance of Vector, Monobook and Modern. Now as for the effectiveness in removing the ability of wikipage content to overtake the interface:
+
+Vector: Improvement
+* Logo: Success (unclickable: wikipage layered behind)
+* Tabs: Success (wikipage layered behind)
+* Personal: Success (wikipage layered behind)
+* Sitenotice: Fail (wikipage remains on top)
+
+Monobook: Improvement
+* Logo: Success (unclickable; wikipage layered behind)
+* Tabs: Success (wikipage layered behind)
+* Personal: Success (wikipage layered behind)
+* Sitenotice: Fail (wikipage remains on top)
+
+Modern: Improvement
+* Sitename/logo: Fail (clickable; wikipage layered on top)
+* Tabs: Success (wikipage layered behind)
+* Personal: Success (wikipage layered behind)
+* Sitenotice: Fail (wikipage remains on top)
+
+So overal an improvement, but some areas still vulnerable.
+
+//attachment 38848m_20121120.patch ignored as obsolete//",1353518615,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11395
+Updated combined patch for 1.21, with Brad's fixes.
+
+Updated patch. Should apply with `git am` with current master
+
+//attachment 38848m_20121120.patch ignored as obsolete//",1353434225,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11363
+Combined patch for 1.19 branch
+
+Tested with REL1_19
+
+//attachment 38848m-119.patch ignored as obsolete//",1353010821,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11362
+Combined patch for vector, monobook, modern, and Brad's fixes - 1.21
+
+Just tested on 1.21-master, and works / fixes the issue
+
+//attachment 38848m.patch ignored as obsolete//",1353010048,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11282
+Patch to fix monobook inactive tabs
+
+(In reply to comment #19)
+> One part that may cause problems is Monobook had a z-index of 2 for
+> div#content, which I set to 0. I wasn't sure why it was set to 2, but I'm
+> guessing there was a reason, so we may need to bring the other elements to a
+> z-index of 2 or higher.
+
+It's for the tabs. Monobook has the links in #p-cactions overlap the top edge of div#content. Then it uses z-index 0 on inactive tabs and z-index 3 on active tabs to get the effect of the active tab looking like ""part of"" div#content. See screenshots such as [[File:Wp-main-page-20100513-monobook.png]] to see this in action. But there would be no point in raising div#content back to z-index 2 in monobook because we'd just have to make #p-cactions z-index 2 or higher too.
+
+It looks like we can achieve the same effect in another way, though. See patch.
+
+//attachment 0001-Fix-monobook-inactive-tab-appearance.patch ignored as obsolete//",1351782105,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #21)
+> Using CVE-2012-5392 to track this
+
+Took me a while to figure out what this is (horrible website)
+
+Future reference: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5392",1351226207,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11245
+Patch for Modern skin
+
+After the email about supporting skins today, I thought we should try and support a patch for modern and Colognblue. This patch for modern has been working well on my localhost, and tested on beta.
+
+//attachment modern.patch ignored as obsolete//",1351224348,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,Using CVE-2012-5392 to track this,1351202383,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Krinkle, I think you said you had some comments on the patch. I'll try and get it tested with browserstack too, but if you think this looks ok, I'd like to get this patched in production and rolled into the 1.19.3 release this week.",1350358309,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 11157
+z-index:0 for Vector & Monobook
+
+This seems to work for me, but I would appreciate more eyes on it. It prevents a div in the content body from blocking the edit button and the footers. In monobook, the left-hand menu is still covered up. I wasn't able to fix that.
+
+One part that may cause problems is Monobook had a z-index of 2 for div#content, which I set to 0. I wasn't sure why it was set to 2, but I'm guessing there was a reason, so we may need to bring the other elements to a z-index of 2 or higher.
+
+//attachment zindex_css.patch ignored as obsolete//",1349279915,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #16)
+> Would position relative (with no additional top/left/right/bottom properties)
+> work ? Or does it have to be position absolute?
+
+Trevor mentioned this, and iirc, he said it was any position except static
+
+(In reply to comment #17)
+> So as being ineffective and problematic towards non-evil markup, I'd say lets
+> drop wgMaxZIndex and go with setting z-index: 0; on the page container and
+> treat it as a skin vulnerability as opposed to a wikitext vulnerability.
+
+I completely agree. Draft deleted.
+
+Krinkle, is setting a z-index: 0 on each of the skins something you can help with? Like I said, I was able to do it for Vector/Monobook, but I wasn't able to get it working with many of the other ones.",1346971089,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I'd recommend dropping the wgMaxZIndex implementation (as drafted in I92b2821c3).
+
+I'd prefer this to be a fix for the skins (something that custom skins would have to implement themselves) as opposed to implementing it in the wikitext parser. Doing it in the parser/sanitizer complicates things and can cause weird issues because it sets an arbitrary limit that:
+
+1) doesn't fully kill the vulnerability
+2) also kills unrelated markup that doesn't go beyond the page container
+
+For instance things could easily be stacked above 50 (or whatever value) and not be outside the body content. Because in order to go outside the body content I'd have to use absolute or relative position. z-index on itself is harmless.
+
+Also, to go outside the page container, one doesn't even need a high z-index value at all. As demonstrated in comment 2 z-index: 2; can do the trick already. So to actually cover it we'd need the z-index: 0; restriction on the page container still. And when doing that, we won't need wgMaxZIndex.
+
+So as being ineffective and problematic towards non-evil markup, I'd say lets drop wgMaxZIndex and go with setting z-index: 0; on the page container and treat it as a skin vulnerability as opposed to a wikitext vulnerability.",1346970000,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #15)
+> I tested this out for some other skins, and many do not work with this, because
+> the menu section does not have a position attribute, so the stacking is not
+> applied to effectively prevent this bug. 
+
+Would position relative (with no additional top/left/right/bottom properties) work ? Or does it have to be position absolute?",1346969553,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I tested this out for some other skins, and many do not work with this, because the menu section does not have a position attribute, so the stacking is not applied to effectively prevent this bug. So, to make this method work, we would need to also add some positioning to the rest of the skin, which is beyond my css skills.
+
+I'd like to get a security fix rolled out before the end of the month, and include a patch for this. Krinkle (or maybe Trevor), would that be possible?
+
+As a compromise, we could just roll this out for Vector and Monobook, which would be simple.",1345480433,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I tested setting z-index: 0 directly on the bodyContent div in the vector skin, and it seems to prevent the clickjacking in Chrome, Opera and Firefox for everything outside of the article body. Obviously it can take over the article, but it seems to prevent overlaying the menus.",1345165993,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #12)
+> Positive integers can start with ""+"":
+> 
+> <http://www.w3.org/TR/CSS2/syndata.html#numbers>
+> 
+> Otherwise I think it will work, as long as the entire user interface is
+> elevated to some z-index larger than $wgMaxZIndex. IIRC, IE imposes a fairly
+> low limit on the maximum z-index, like 2^15 or 2^16, so it should be tested if
+> the user interface is raised to a high z-index.
+> 
+> However, I have an idea that I think will work without changing the z-index of
+> any user interface elements, and without limiting the z-index values in user
+> supplied CSS. 
+> 
+> Z-index values are only valid within a single ""stacking context"". Applying
+> z-index: 0 to the #bodyContent div would establish a separate stacking context
+> for the content area, and should prevent any descendant from overlapping
+> anything with z-index: 1 or higher in the UI.
+> 
+> http://tstarling.com/stuff/z-index-context.html
+> 
+> I tested it in Firebug on Wikipedia and it seems to work.
+I played with this in Firebug on mediawiki.org, adding the following rules:
+
+#bodyContent { z-index: 0; }
+#toc { position: absolute; left: -17em; top: -12em; z-index: 50 }
+
+The latter attempts to move the TOC such that the [hide] link clickjacks part of the logo. This works without the z-index:0 rule and breaks with it.
+
+CC Trevor because this is about CSS magic and Krinkle is on vacation.",1344990922,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Positive integers can start with ""+"":
+
+<http://www.w3.org/TR/CSS2/syndata.html#numbers>
+
+Otherwise I think it will work, as long as the entire user interface is elevated to some z-index larger than $wgMaxZIndex. IIRC, IE imposes a fairly low limit on the maximum z-index, like 2^15 or 2^16, so it should be tested if the user interface is raised to a high z-index.
+
+However, I have an idea that I think will work without changing the z-index of any user interface elements, and without limiting the z-index values in user supplied CSS. 
+
+Z-index values are only valid within a single ""stacking context"". Applying z-index: 0 to the #bodyContent div would establish a separate stacking context for the content area, and should prevent any descendant from overlapping anything with z-index: 1 or higher in the UI.
+
+http://tstarling.com/stuff/z-index-context.html
+
+I tested it in Firebug on Wikipedia and it seems to work.",1344989381,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Thanks Roan.
+
+Change is now here https://gerrit.wikimedia.org/r/#/c/19651/2",1344984488,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #9)
+> (In reply to comment #8)
+> > Created attachment 10958 [details]
+> > Strip user styles with high zindex
+> > 
+> Because the second \s is non-optional and not repeated, it looks like
+> ""z-index:30000"" and ""z-index:    30000"" would fool the regex.
+Confirmed that this is the case.
+
+Also, an invalid z-index leads to the entire style attribute being stripped, which isn't very nice. It would be nicer to just strip the rule (or clamp the value maybe). This probably requires using preg_replace_callback() instead.
+
+//attachment zindex.patch ignored as obsolete//",1344978120,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(In reply to comment #8)
+> Created attachment 10958 [details]
+> Strip user styles with high zindex
+> 
+Because the second \s is non-optional and not repeated, it looks like ""z-index:30000"" and ""z-index:    30000"" would fool the regex.
+
+//attachment zindex.patch ignored as obsolete//",1344977890,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Created attachment 10958
+Strip user styles with high zindex
+
+Patch to Sanitizer's checkCss() to strip out css that has a z-index over a site's defined $wgMaxZIndex.
+
+Sites can determine appropriate $wgMaxZIndex values, and skins can set a z-index over this value for important items (menus, buttons, etc).
+
+//attachment zindex.patch ignored as obsolete//",1344885003,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"(links: bug 8679, bug 9526)",1344047096,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"After thinking through some more abuses of this, it makes me nervous having this out there.
+
+How much would break if we:
+1) Add a fairly high z-index on whatever container is holding the main menu links
+2) Prevent setting inline z-indexes to anything equal to or greater than or menu's z-index",1344014431,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Related bugs: 8679 and 9526, which both use inline styles to do unexpected things with the user experience.
+
+The comforting thing is that if this becomes a common vector for vandals, we can easily block specific cases with an abusefilter rule.
+
+That being said, have we considered having different css/style rules for different namespaces? So we could prevent position styles in articles, but not templates or user pages?
+
+Or adding !important and high z-indexes to the navigation areas?",1343936081,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"I'm afraid so, yes.
+
+Both on their user page (e.g. to stylize the heading of their user name or the Wikipedia logo), as well as in templates on actual articles. E.g. to create graphs and such (the latter is much less evil since the absolute positioning there is only relative to the wrapper div of the template - this I'd say is genuine and to-be-supported use of absolute css).
+
+Usage of position absolute outside the page wrapper (e.g. to overlap #firstHeading, which some users do on their User page to make it look nicer, or to overlap the #p-logo with something they think looks cooler - again only on their user page)",1343762312,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,Thanks for the demo Krinkle. So editors are actively using position styles on wiki?,1343762080,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"Both position relative and position absolute are very common. Especially because CSS absolute positioning is relative to the closest parent that has relative positioning.
+
+So a user can have an element with relative position and in there another element with absolute position and negative values, and still be within the page viewport.
+
+As for linkability, there is no way to execute javascript within the session from there (since there is no way to do that anywhere in wikitext, regardless). However it is possible to link to an external link.
+
+
+Location: https://www.mediawiki.org/w/index.php?title=Project:Sandbox&action=edit
+
+<div style=""
+position: absolute;
+top: -118px;
+left: 0;
+z-index: 2;
+width: 100%;
+height: 100px;
+background: rgba(0, 255, 255, 0.2);
+text-align: center;
+""> Breaks Nav </div>
+
+
+<div style=""
+position: absolute;
+top: -120px;
+left: -180px;
+z-index: 2;
+width: 150px;
+height: 150px;
+background: rgba(0, 255, 255, 0.2);
+text-align: center;
+""><div style=""position: absolute; -webkit-user-select: none; -moz-user-select: none; user-select: none;"">Goes to Toolserver.org</div>[[File:Transparent.gif|150x150px|link=//toolserver.org|Go to the Main Page, or... Tooserver.org?]]</div>",1343757488,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+Security: CSS positioning can be used to break out of the content area,"It is certainly possible to cover useful buttons and sections of the page with a div, which could prevent users from being to click a button or a link (DoS, effectively).
+
+<div style=""position:absolute; top:-118px; left:0px; z-index:2; width: 100%; height: 100px""> Breaks Nav </div>
+
+However, there should *not* be a way to get the click to do anything that is attacker controlled-- run javascript, or navigate to an external link. If either of those becomes possible, then this becomes a major security issue. Otherwise, this is probably more of an annoyance, that we can easily revert if we encounter it.
+
+We could disable setting position, or only allow position:relative with positive values and within certain limits. I'm not sure how common it is for editors to use div positioning, so we would need to research that. I'll try and find someone on the UI team to comment.",1343755934,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-eru2tiwghisa2sl7pdsv,task_subcomment,NA
+"VisualEditor: Pressing 'Esc' in Save-dialog should exit saving, return to editor","[From a user report.]
+
+""If the user press ESC while the save popup is open, it should just return to the edit mode, but it does nothing unless we click in the [x] button.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1343084880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bw4tf22xsrw2meuuvmyr,task_description,resolved
+"VisualEditor: Pressing 'Esc' in Save-dialog should exit saving, return to editor",Fixed in https://gerrit.wikimedia.org/r/16782,1343341026,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-bw4tf22xsrw2meuuvmyr,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,"Arrow keys move the caret in the opposite direction in RTL environment. Simple textareas in browsers do this correctly, so as much as possible, the Visual Editor should rely on the browsers' behavior.
+
+See https://www.mediawiki.org/wiki/VisualEditor/Internationalization_requirements .
+
+Related: bug 38000.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342868640,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-6xsc6lb6uvcf633e32tb,task_description,resolved
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,Merged and will go out in wmf6.,1369780070,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,Related URL: https://gerrit.wikimedia.org/r/65703 (Gerrit Change Ic01e110a5e6094cd275327a2e8cea90c900f1bd1),1369693188,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,"@Amir: Your guess it correct, we are capturing keyboard events (keydown to be specific) and then moving cursor forward (right arrow) or backward (left arrow). We implemented it in this way because it let's us block user from moving cursor inside a non-editable element (alien node - like rendered template for instance). It seems that we will have to work a little bit more on this, I will try to just let browser handle cursor movement but then ""fix"" it in JavaScript if it ends up in wrong place.",1343170407,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,"Try it with text that is actually RTL :)
+
+Without looking at the code, I guess that you capture keypress events, and if it's a right arrow, you move it one character forward, and vice versa. But for RTL right is backward etc.
+
+Simply reversing the direction for RTL text will not be enough, because an LTR word in the middle of an RTL paragraph will mess things up. And that's just one of the many complications. It took Gecko and Webkit developers years to get it right and both still have bugs.
+
+The best way to handle arrow events is to simply let the browser handle them.",1343080494,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment,"**orbit** wrote:
+
+Amir, I'm pretty sure that this should be working properly in the new contenteditable-based editor. Can you double-check for me? Here's my RTL demo: http://framezero.com/work/wikia/VisualEditor/demos/ve/index.php",1343079723,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6xsc6lb6uvcf633e32tb,task_subcomment,NA
+VisualEditor: Build out support for Monobook,"The VisualEditor extension currently only works with the Vector skin. It should work with other skins such as Monobook.
+
+From [mediawiki/extensions/VisualEditor.git] / VisualEditor.hooks.php (<https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=blob;f=VisualEditor.hooks.php;h=e43fef59dd678ba5309f2335829dd6fe1e041a2d;hb=4fea35acd451c939a522ab7a4d7bd13e4ac95e76>):
+
+---
+class VisualEditorHooks {
+	/**
+	 * Adds VisualEditor JS to the output if in the correct namespace.
+	 *
+	 * This is attached to the MediaWiki 'BeforePageDisplay' hook.
+	 *
+	 * @param $output OutputPage
+	 * @param $skin Skin
+	 */
+	public static function onBeforePageDisplay( &$output, &$skin ) {
+		global $wgTitle;
+		if (
+			// Vector skin supported for now.
+			$skin->getSkinName() === 'vector' &&
+			(
+				// Article in the VisualEditor namespace
+				$wgTitle->getNamespace() === NS_VISUALEDITOR ||
+				// Special page action for an article in the VisualEditor namespace
+				$skin->getRelevantTitle()->getNamespace() === NS_VISUALEDITOR
+			)
+		) {
+			$output->addModules( array( 'ext.visualEditor.editPageInit' ) );
+		}
+		return true;
+	}
+---
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1341350580,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-kxjmckaitcfmwxa44pgn,task_description,resolved
+VisualEditor: Build out support for Monobook,"(In reply to comment #4)
+> I've added support for Monobook in Ia39e034229204ae5f1f70dce5d74c6c4db42277b
+
+Awesome. Thank you, Trevor!",1345771635,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,The primary request here was monobook support - I've renamed the bug and am now closing it.,1345745134,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,"I've added support for Monobook in Ia39e034229204ae5f1f70dce5d74c6c4db42277b
+
+This doesn't mean ""all"" skins are supported, so I am not sure I should close the bug, but for most purposes this is sufficient.",1345745065,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,"(In reply to comment #2)
+> Enhancement, not bug. Resource issues are non-trivial. To discuss as part of
+> the product strategy.
+
+I've found the cost of all the noise switching back and forth between bug and enhancement to far outweigh any benefit. I don't care what you call this ticket and neither does nearly any other ticket filer.
+
+The VisualEditor extension should work with non-Vector skins. (And the fact that it doesn't is getting in the way of power-users, a good number of whom use Monobook.)
+
+You can classify the request as whatever you'd like or just disable the stupid categorization altogether. Nobody cares.",1341351777,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,"Enhancement, not bug. Resource issues are non-trivial. To discuss as part of the product strategy.",1341351016,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+VisualEditor: Build out support for Monobook,Bumping the importance of this as it's annoying the shit out of me when trying to play with the extension.,1341350663,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-kxjmckaitcfmwxa44pgn,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","More for the wishlist...
+
+Need a dialog to manipulate image properties (size, alignment, border, caption).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1341271020,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-mxnglgs5g63joubkufdc,task_description,resolved
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Moving all of these out into their own bugs and closing this:
+
+(In reply to James Forrester from comment #18)
+> * media thumbnail over-ride: not yet done, low priority
+
+Now bug 62669.
+
+> * alignment (baseline/middle/…): not yet done, low priority
+
+Now bug 62670.
+
+> * need a ""set as 'upright'"" size value setting (default to 75%)
+
+Now bug 62671.
+
+> * link: not yet done, low priority
+
+Now bug 62672.
+
+> Non-image things:
+> * page (for multi-page items, e.g. PDFs): not yet done, low priority
+
+Now bug 62673.
+
+> * noicon (for multimedia items): not yet done, low priority
+
+Now bug 62674.
+
+
+> * start: not yet done, low priority
+
+Now bug 62675.
+
+
+> * thumbtime: not yet done, low priority
+
+Now bug 62676.
+
+
+> * merging with the (future) gallery editing dialog: not yet done
+
+Now bug 62677.
+
+
+> * CE-surface fixes to make TMH's media items display correctly: not yet done
+
+Now bug 62678.
+
+Closing this one as an unhelpful semi-tracker.",1394835371,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Updated list of not-yet-done items from comment #16:
+
+* which media item is shown (but keeping other options): bug 51033
+* media thumbnail over-ride: not yet done, low priority
+* alignment (baseline/middle/…): not yet done, low priority
+* need a ""set as 'upright'"" size value setting (default to 75%)
+* link: not yet done, low priority
+
+Non-image things:
+* page (for multi-page items, e.g. PDFs): not yet done, low priority
+* noicon (for multimedia items): not yet done, low priority
+* start: not yet done, low priority
+* thumbtime: not yet done, low priority
+
+Other things:
+* preview of media item: bug 52461
+* remove from page button: bug 51764
+* merging with the (future) gallery editing dialog: not yet done
+* CE-surface fixes to make TMH's media items display correctly: not yet done",1394082712,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 105247 merged by jenkins-bot:
+Add image type change to media edit dialog
+
+https://gerrit.wikimedia.org/r/105247",1391820350,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","A quick review of the settings functionality for the media dialog right now:
+
+* which media item is shown (but keeping other options): bug 51033
+* media item type (thumb, frame, frameless): underway in gerrit 105247
+** media thumbnail over-ride: not yet done, low priority
+* border: not yet done, low priority
+* location (left/right/centre/non): bug 51293, done
+* alignment (baseline/middle/…): not yet done, low priority
+* size: mostly done; needs some fixes
+** need a ""set at default size"" button
+** need a ""set as 'upright'"" value setting (default to 75%)
+** logic rule changes when image is frame not thumb (no upscaling of image)
+* link: not yet done, low priority
+** Possibly needs to know licence to avoid linking in violation of licence, e.g. CC-BY?
+* alt text: done
+* caption: done
+
+Non-image things:
+* page (for multi-page items, e.g. PDFs): not yet done, low priority
+* noicon (for multimedia items): not yet done, low priority
+* start: not yet done, low priority
+* thumbtime: not yet done, low priority
+
+Other things:
+* preview of media item: bug 52461
+* remove from page button: bug 51764
+* merging with the (future) gallery editing dialog: not yet done
+* CE-surface fixes to make TMH's media items display correctly: not yet done",1391658048,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 105247 had a related patch set uploaded by Jforrester:
+[WIP] Add image type change to media edit dialog
+
+https://gerrit.wikimedia.org/r/105247",1391657049,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 105098 merged by jenkins-bot:
+Adding alternate text to media edit dialog
+
+https://gerrit.wikimedia.org/r/105098",1391655563,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 103193 merged by jenkins-bot:
+Changing image size in MWMediaEditDialog
+
+https://gerrit.wikimedia.org/r/103193",1390445864,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 105098 had a related patch set uploaded by Jforrester:
+Adding alternate text to media edit dialog
+
+https://gerrit.wikimedia.org/r/105098",1389677199,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 103193 had a related patch set uploaded by Jforrester:
+Changing image size in MWMediaEditDialog
+
+https://gerrit.wikimedia.org/r/103193",1389677179,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 92767 abandoned by Mooeypoo:
+[WIP] Add further image attribute editing to the media dialog
+
+Reason:
+Split into separate dependent commits
+
+https://gerrit.wikimedia.org/r/92767",1388787172,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",*** Bug 53937 has been marked as a duplicate of this bug. ***,1383759270,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 92767 had a related patch set uploaded by Jforrester:
+[WIP] Add further image attribute editing to the media dialog
+
+https://gerrit.wikimedia.org/r/92767",1383759257,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","We have another request for ""alt text"" support in the media dialog.  As this is an accessibility concern for the visually impaired in our reader base, it's an important option to offer (the dialog will have to explain this field, and why it's desirable).",1375634468,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Change 74082 had a related patch set uploaded by Jforrester:
+Base for media settings size widget.
+
+https://gerrit.wikimedia.org/r/74082",1374168350,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",*** Bug 51126 has been marked as a duplicate of this bug. ***,1373481769,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",Just adding another urge for alt.text at English Wikipedia. :),1372976750,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",*** Bug 50709 has been marked as a duplicate of this bug. ***,1372900959,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)","Caption editing is now done and will be live in a few minutes; setting size, alignment, type and border will come later.",1371603773,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+"VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)",Speculatively putting into the next release.,1368323694,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mxnglgs5g63joubkufdc,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Example: Android 2.x browser (tested Kindle Fire), iOS < 5 browser.
+
+The editor initializes, but since there's no ContentEditable support you can't actually type anything. In iOS 4.3.2 simulator initialization never quite completes...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1341270660,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_description,resolved
+VisualEditor should not try to initialise if no ContentEditable support,Related URL: https://gerrit.wikimedia.org/r/67082 (Gerrit Change Ic38992e04b5f3932cf18f2dfc217cd733196efb8),1370436939,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,Related URL: https://gerrit.wikimedia.org/r/66993 (Gerrit Change Idc5f4a23a2709264d869a91d00873c4e187bc470),1370370120,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"@Ed Feature tests:
+
+* Engine is ECMAScript5 compliant.
+
+  Avoid testing things like Object.create or Function#bind which can easily
+  be polyfills (and asserting the difference between native and polifill can
+  be tricky). Assert that strict mode works. 
+
+  supportsStrictMode = ( function () {
+      ""use strict"";
+      function x() {
+          return this;
+      }
+      return x() === undefined;
+  }() );
+
+  Perhaps you could even take out x() and just return this === undefined.
+  Though that appears to work and seems more straight forward, I see all
+  patterns out there use a function inside. Let's figure out if its needed
+  and only do it if needed.
+
+* Browser supports ContentEditable.
+
+  DOMElements have all supported properties defined in their default state.
+  e.g. all input fields have property 'placeholder' (empty string as value
+  by default).
+  supportsPlaceholder = 'placeholder' in document.createElement( 'input' );
+
+  For content editable we don't need to create an element, we can just
+  use document.body as test target since it works body as well. 
+
+  supportsContentEditable = 'contentEditable' in document.body;",1369526726,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,Setting milestone per James.,1368554214,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,*** Bug 41149 has been marked as a duplicate of this bug. ***,1368039230,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Having discussed this with Timo just now, ua-parser has now moved even further away from being appropriate for client-side use, so here's the new plan:
+
+* We will have some basic up-front tests of browser functionality - contentEditable, localStorage, etc.
+
+If the browser is detected to not have this, we will fail with an error message along the lines of ""Sorry, this browser does not support some of the core technologies used in VisualEditor and so it will not load. <Oh well>""
+
+* Then we have two lists - a known-good list (i.e., currently the IE9+/Firefox10+/Chrome16+/Safari5+ list) and a known-bad list (e.g., Android<=2, Opera) If the browser is in the former, VE loads; if in the latter we will fail with an error message along the lines of ""Sorry, this browser is known to have serious issues with VisualEditor and so it will not load. <Oh well>""
+
+If we reach this point (seems to have the technologies, not a known-bad or a known-good), we give the user a choice about whether to proceed - ""We do not know if this browser works perfectly with VisualEditor; do you wish to proceed? <OK> <Cancel>"" - and set the answer in localStorage.",1367944191,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"I submitted a pull request to ua-parser just now.
+
+Once they merge it I'll add that as a new module and let VisualEditor use that instead. I should probably keep jquery.client in core so that extensions using that can continue to do so (maybe as a wrapper though, to avoid repetition).",1349120569,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"I'll see if its possible to extend jQuery.client. Otherwise we may want re-consider replacing this module with something more solid.
+
+There's two major parsers I know work very well and have been proven to work by ""the mass"":
+
+* browscap [1] (supported by PHP's get_browser functionality)
+  - Currently PHP only, and the source is a hugely inefficient .ini file that isn't very future proof. Not the kind of thing we'd want to port to javascript, not to mention the huge manifest.
+
+* ua-parser [2] (forked from 
+ - Currently in many languages, including javascript. Though nodejs, we'll have to export the yaml file to JSON and figure out if there is any nodejs modules we need to substitute.
+
+
+[1] http://browscap.org | https://browsers.garykeith.com/ | https://github.com/GaretJax/phpbrowscap
+[2] https://github.com/tobie/ua-parser | https://github.com/tobie/ua-parser/tree/master/js",1348076962,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Timo, can you work on getting Android support into jQuery.client so we can close this out?",1347302938,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Now that bug 38857 is fixed, this is easy... Or is it?
+
+This is what I got from $.client.profile() on Jon's phone which runs Android 4.04:
+
+{""name"":""safari"",""layout"":""webkit"",""layoutVersion"":534,""platform"":""linux"",""version"":""4.0"",""versionBase"":""4"",""versionNumber"":4}
+
+Maybe we could enhance jQuery.client so it can cope with Android user agent strings.",1345673017,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"According to http://stackoverflow.com/questions/1882205/how-do-i-detect-support-for-contenteditable-via-javascript you can check for the contentEditable property in the DOM, but this gives false positives on iOS and Android versions where the engine supports it but provides no way to edit things.
+
+So possibly a test combined with a blacklist for Android browser < 3 and iOS < 5?",1341271526,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor should not try to initialise if no ContentEditable support,"Is there a nice way to test for CE functionality automatically, or do we need to create a whitelist-of-doom?",1341270976,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmzxtthtzpwj4eczkcbn,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,"(Save needs to be selected as default action?) Very irritating for those of us that don't use the mouse much when we edit. ;-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50897",1340916180,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2egq3hlgvj5ljxkovvce,task_description,declined
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,This was deliberately removed by bug 40034.,1374613842,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,"**ignatzmice.wiki** wrote:
+
+Was going to file a new bug, but this popped up as a possible duplicate. I notice that rather than doing *nothing*, it does create a newline in the edit summary box, which is then transformed into a space on saving. I too use Monobook, not that I image it makes a difference.",1373849913,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,"Agree with comment #4, this is still an issue, and it's now more problematic due to a higher number of experienced users being used to hit 'Enter' to save.
+
+Has Rob's code (committed almost a year ago) been merged?",1373532785,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,"**KilliondudeWP** wrote:
+
+This is an issue and has been for at least a few weeks. I'll note that I use Monobook in case that is relevant.",1373411137,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,*** Bug 38735 has been marked as a duplicate of this bug. ***,1343347540,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,Fixed in https://gerrit.wikimedia.org/r/16782,1343340991,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys,*** Bug 38039 has been marked as a duplicate of this bug. ***,1340916283,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-2egq3hlgvj5ljxkovvce,task_subcomment,NA
+VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination,"When copy-pasting from the VisualEditor into LibreOffice 3 (tested 3.5.2.2 on Ubuntu 12.04), links are copied with the target URL of the wiki page being edited plus ""#"" on the end, eg <https://www.mediawiki.org/wiki/VisualEditor:Welcome#>
+
+This doesn't happen when copy-pasting from the view mode.
+
+See also bug 33239 comment 6 -- if we retain the original href and use JavaScript to suppress regular clicking, I think this would lead to more natural cut-n-paste behavior with other apps.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33105",1340905200,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-qttnmog5m4ro2nv4m5sn,task_description,resolved
+VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination,This is now fully correct; closing as fixed.,1361834067,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qttnmog5m4ro2nv4m5sn,task_subcomment,NA
+VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination,"This is a bit better now, but not quite there yet. External links now point to the correct destination, but internal links don't, they just contain the name of the page in the href.",1352597120,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qttnmog5m4ro2nv4m5sn,task_subcomment,NA
+VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination,Add see-also to bug 33105 which wants rich copy-and-paste - this is distinct but related.,1340930523,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qttnmog5m4ro2nv4m5sn,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Once basic image support is included, and there's some integration with UploadWizard or similar, it should be possible to initialize the upload tool with drag-and-dropped image files.
+
+This would allow simply dragging one or more files from your file manager over to the spot in the document where you want them, ending up with a single image or gallery at the end.
+
+Compared to {T40030}, needs to be able to initialize the wizard with given File objects received via a drop.
+
+**See also**: {T11133}",1340904000,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_description,resolved
+VisualEditor: Initiate file upload by drag-and-drop,@Aklapper Understood. ,1540797650,PHID-USER-cb53pyjz3ccu7fvgd7m2,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"@Thedonquixotic : This task is resolved (see top bar). If something does not work for you, see https://www.mediawiki.org/wiki/VisualEditor/Portal for where to discuss issues. Thanks!",1540785805,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Hey, just curious if this feature is actually in Visual Editor or not? I can't seem to find it, or figure out how to use it. ",1540769669,PHID-USER-cb53pyjz3ccu7fvgd7m2,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Change 246185 merged by jenkins-bot:
+Media upload: Initialize booklet before setting file on drag drop
+
+[[https://gerrit.wikimedia.org/r/246185]]",1444827161,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Change 246185 had a related patch set uploaded (by Prtksxna):
+Media upload: Initialize booklet before setting file on drag drop
+
+[[https://gerrit.wikimedia.org/r/246185]]
+",1444816024,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Change 244331 merged by jenkins-bot:
+Media upload: Initiate upload process on image drop
+
+[[https://gerrit.wikimedia.org/r/244331]]",1444760995,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Change 244331 had a related patch set uploaded (by Esanders):
+Media upload: Initiate upload process on image drop
+
+[[https://gerrit.wikimedia.org/r/244331]]
+",1444249087,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"VE's drop handler needs a list of allowed file extensions on the target remote wiki. You can get this via the API – http://commons.wikimedia.org/w/api.php?action=query&meta=siteinfo&siprop=fileextensions – but we'll need T114765 before we can scrape it. It also/instead needs a list of MIME types; not sure if that's possible in MW, sadly.",1444183790,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"(In reply to comment #3)
+> If using UploadWizard itself is not feasible at this stage, a lightweight
+> uploader UI similar to what's available on mobile might be good -- this does
+> a cross-origin POST to Commons for the upload, so we don't have to leave the
+> page or open an iframe or anything weird like that.
+
+Opening up an iframe isn't too hard for VisualEditor (every dialog is one already), but re-using UploadWizard (and refactoring it so this is possible) seems like a much better solution than writing our own.
+
+There's wider product questions about whether to allow uploading to local, or just to Commons (given that relatively few wikis allow local uploads, and that those are only meant to be used in special circumstances, making it too easy to upload copyvios/etc. and having licence proliferation might be the wrong approach).",1373477183,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"I think roughly what we'd want to happen is something like this:
+
+* user drag-and-drops an image file from Explorer/Finder/file manager into the document.
+** if possible, show a rectangular placeholder box around the cursor position while dragging
+* on drop, save the cursor position so we know where in the document to insert...
+* ...and spawn the UploadWizard or similar interface, handing it the file we've received to start the actual upload process, select a license, save a description etc.
+* At the end of the UploadWizard, instead of showing you the link to the file we transition straight back to the editor...
+* ...and you can then modify the positioning/sizing/caption/etc with the VisualEditor's existing dialogs.
+
+
+If using UploadWizard itself is not feasible at this stage, a lightweight uploader UI similar to what's available on mobile might be good -- this does a cross-origin POST to Commons for the upload, so we don't have to leave the page or open an iframe or anything weird like that.",1373477004,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,"Request for similar functionality made at MediaWiki today:
+
+Hi, I see a number of requests for the ability to easily upload local images (from our local HD to Wiki I guess). I'd like to add my vote for this request. How is this progressing? How would it work? Simply browse for an image locally and then go through the captioning, sizing, aligning, positioning, licensing — then upload for it to appear immediately in the desired location with also the hi-res and info immediately in Wikimedia Commons?
+
+Robertwhyteus (talk)‎20:27, 9 July 2013",1373423973,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+VisualEditor: Initiate file upload by drag-and-drop,This is not on schedule for before the next big release; noting as such.,1365636093,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-duiplk7fkjkz4nppzcgi,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","Our traditional editor toolbars have buttons to insert a [[File:Foo.png]] or similar, but not that would help you with the actual editing process.
+
+A button that launches the UploadWizard -- possibly uploading to Commons -- and ends with inserting the image(s) into the article would be a big leap forward.
+
+--------------------------
+
+User journey:
+# User clicks on ""insert media""
+# In the dialog, user clicks on ""upload new""
+{F176539}
+
+ //… or 'User drags a file into the editor', see T40031 //
+
+3. Dialog is launched
+{F176534}
+
+4. User confirms that the media file is theirs, and accepts that it will thus be under the default licence (CC-BY-SA-3.0); file starts uploading with a progress bar (indeterminate for now)
+
+{F176541}
+
+ //… or user is directed to Special:Upload if local uploads are available.//
+> ""To upload a file which cannot be freely re-used, please use the __restricted form__.""
+
+ //… or user is directed to Special:UploadWizard on Commons.//
+> ""To upload a file created by someone else, or under a different licence, please use the __advanced form__.""
+5. User enters a title.
+{F176543}
+
+6. User enters a description (default in the user's interface language, with a control to set the language to something else).
+{F1000}
+
+7. User optionally over-rides the date of creation from 'today'.
+{F1000}
+
+8. User optionally enters (Commons) categories.
+{F176551}
+
+9. User clicks ""Publish and Insert"", and file is un-gated on the stash and published on Commons, and inserted locally as a `thumb|right` (or `|left` on RTL) at default size with the description as the caption (if the description is in the content language).
+{F176555}
+
+ //… or user clicks ""Cancel Publishing"" and the file is left in the stash for garbage collection, never published.//
+
+10. Done.",1340903820,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_description,resolved
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","Change 240116 merged by jenkins-bot:
+Add image upload tab to media dialog
+
+[[https://gerrit.wikimedia.org/r/240116]]",1444182861,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","Change 240116 had a related patch set uploaded (by Esanders):
+[WIP] Image uploading
+
+[[https://gerrit.wikimedia.org/r/240116]]
+",1442950783,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","@nirzar, @matmarex, @marktraceur, please clarify if I've missed or misunderstood anything.",1439369004,PHID-USER-gc5hdyw5p4np7atqjynz,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","Notes from `#wikimedia-multimedia`, with @matmarex and @marktraceur //(logs are edited to keep only relevant messages)//:
+
+{P1870}
+
+***
+
+**tl;dr**
+Our first step is to make a tool that can upload a file from enwiki to commons with a default license. The local vs remote and license choices can come later. 
+The commons specific subclass of [[https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.Upload.Dialog|mw.Upload.Dialog]] can go to [[https://www.mediawiki.org/wiki/Extension:CommonsMetadata|CommonsMetadata]]. The `mw.CommonsUpload` model will take care of the `{{information}}` template on Commons. 
+This new code could live in VE-mediawiki, or in core, after naming it `MediaRepoUpload` instead of `CommonsUpload`.
+",1439368960,PHID-USER-gc5hdyw5p4np7atqjynz,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","I had a discussion with @nirzar, on how we can integrate the [[https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.Upload.Dialog|upload dialog in core]] with VisualEditor. @nirzar explained to me the expectations of the user when in VE, and how a simplified workflow would work best. @marktraceur was talking about a bare bones version for the first iteration too, more in my next comment. In simplifying the workflow, we wanted to cut some details currently required to upload, but aren't sure if it is  acceptable from a product or legal point of view—
+
+1. Isolate global and local information to avoid cognitive overload.
+2. Pick sane license defaults and don't give the user too much choice
+3. Auto-categorize the image to— //from-VE//, or some such, making it easier to find these images on Commons.
+4. Hide where the image is going (local wiki vs commons). Inform user later that the image went to commons — //Thanks for uploading to Commons. [[https://commons.wikimedia.org/wiki/Commons:Welcome|Learn More]].//
+
+***
+
+When uploading through VE there would be two entry points—
+1. An //Add more// button in the Insert Media (//Media settings//) dialog //[1]//.
+2. Dropping a file into VE.
+
+The first option would lead to the first pane of the upload dialog //[2]//. The second option would jump straight to the second pane //[3]//. For VE we'll always skip the last, //Usage// pane and directly insert the image on the page. 
+
+@nirzar wanted the local editing to be more inline in VE, but, it currently opens up a dialog //[4] (this isn't exactly in the purview of making upload work with VE, but deserves mentioning)//. We need to decide whether we want to automatically open up this dialog or let the user initiate the action.
+He has also requested User Research for this workflow, but I don't know much about that yet.
+
+***
+
+1. F1359538
+2. F1359743
+3. F1360116
+4. F1360346
+",1439368885,PHID-USER-gc5hdyw5p4np7atqjynz,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","//Comments from the pitch meeting last week//
+* Show a preview of the image in the dialog? Easier in VE but useful for WE.
+* Licensing imposition info and user click-through
+** Let them choose? Danger of choice turning into what we have with UW?
+* Build a preview whilst you go through the steps – show where the caption will be rendered, anticipate the final result.
+* Description and caption. If we’re doing it in an article, do users have that distinction? Hard to provide them as separate things?
+** Separation between local information and global information? Do local activities after the ‘publish’ step?
+** Show caption as part of preview?
+** Just use caption as description?
+** Call out //“how it will appear in the article”// vs //“how it will appear to re-users”//?
+** Each step may have a different license, need to split them by those lines
+* Split licences – possibly CC0 for description/etc. but CC-BY-SA-3.0 [or whatever] for the image and possibly CC-BY-SA-3.0 or CC-BY-SA-4.0 or PD or … for the caption (and may be different)
+
+",1439364784,PHID-USER-gc5hdyw5p4np7atqjynz,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","//Comments from the pitch meeting last week//
+* Show a preview of the image in the dialog? Easier in VE but useful for WE.
+* Licensing imposition info and user click-through
+** Let them choose? Danger of choice turning into what we have with UW?
+* Build a preview whilst you go through the steps – show where the caption will be rendered, anticipate the final result.
+* Description and caption. If we’re doing it in an article, do users have that distinction? Hard to provide them as separate things?
+** Separation between local information and global information? Do local activities after the ‘publish’ step?
+** Show caption as part of preview?
+** Just use caption as description?
+** Call out “how it will appear in the article” vs “how it will appear to re-users”?
+** Each step may have a different license, need to split them by those lines
+* Split licences – possibly CC0 for description/etc. but CC-BY-SA-3.0 [or whatever] for the image and possibly CC-BY-SA-3.0 or CC-BY-SA-4.0 or PD or … for the caption (and may be different)
+
+",1439364250,PHID-USER-gc5hdyw5p4np7atqjynz,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion","//Comments from the product pitch meeting today//
+
+* @Esanders: inline inspectors are there for things that probably shouldn’t be easily dismissed
+* Need to think about when information should be required - some things can be postponed
+* Can we use a non-linear workflow for this?  Additional information is recorded non-modally
+* Doesn’t provide any user education about what’s allowed on Commons and what’s not
+** @Jdforrester-WMF: almost all users skip straight past that page in the UploadWizard anyway
+",1433984120,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion",*** Bug 64158 has been marked as a duplicate of this bug. ***,1398101283,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+"Way in VisualEditor to initiate Commons file uploading, and insert image on completion",This is not on schedule for before the next big release; noting as such.,1365636099,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vyxifsvid5dvxvr4vi6e,task_subcomment,NA
+VisualEditor: Triple-click to select block level element,"From user feedback. Expected behaviour is to select entire current context (i.e. paragraph or if you're in a table, the table cell).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340834460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nicumpfbj5y55eeu3oq3,task_description,resolved
+VisualEditor: Triple-click to select block level element,Merged and will be pushed to production in a few minutes.,1372090012,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nicumpfbj5y55eeu3oq3,task_subcomment,NA
+VisualEditor: Triple-click to select block level element,"We could trivially extend the functionality as it has just been implemented so that each subsequent click beyond the third expands the selection to the next block parent. Might be useful for selecting multiple paragraphs within a table cell, table rows, full tables etc. Or might be annoying. Thoughts?",1372024524,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-nicumpfbj5y55eeu3oq3,task_subcomment,NA
+VisualEditor: Triple-click to select block level element,Related URL: https://gerrit.wikimedia.org/r/70104 (Gerrit Change Ic80d24581535766714d80104222924f7a0d20f1a),1372024243,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nicumpfbj5y55eeu3oq3,task_subcomment,NA
+VisualEditor: Triple-click to select block level element,I just encountered this again when editing a table on a wiki. Especially in table cells it is tedious to have to manually select the contents of a table cell.,1367895234,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-nicumpfbj5y55eeu3oq3,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"## Requirements
+
+- Identify links to pages that do not exist.
+- Support different red link behavior on desktop (class, link to edit view) and apps (remove links).
+- Support re-styling of red links for skins & accessibility.
+- Perform well, both server & client side.
+
+## Non-requirements
+
+- Stub thresholds: These can be implemented client side with a separate API request, for users that have this option enabled.
+
+## Solutions
+
+### 1) Separate metadata
+
+Provide a JSON array containing hrefs of pages that do not exist. On most pages, this array will be very short or empty.
+
+Clients can then use this array to find links to non-existing pages, and apply the transformations they would like.
+
+Advantages:
+
+- Easy to implement server side.
+- Avoids latency overheads of server-side DOM parsing.
+- Can be consistently applied to old content. However, a general limitation of red link updates for old revisions is that current link tables are only available for the latest revision, which means that links in old revisions might not be updated.
+- Consistent matching interface helps clients render red links for specific use cases.
+
+Disadvantages:
+
+- Client requirements:
+  - Process JSON and run JS.
+  - Extra API request.
+- API complexity: Need to expose metadata in separate API.
+
+
+### 2) Parsoid DOM pass
+
+Retrieve list of red links in page (as in separate metadata solution), and rewrite href / add classes in DOM processing pass.
+
+Advantages:
+
+- Still relatively easy to implement server side.
+- Low extra cost.
+- No need for JS on the client.
+- Compatible with existing skins.
+- No need for extra API.
+- Records accurate 'at the time' snapshot of how a page looked.
+
+Disadvantages:
+
+- Implements a specific kind of handling / rewriting, which then needs to be undone / changed for other use cases.
+- Changes in href (ex: linking to edit views) complicate matching for further post-processing. Not touching the href would mean that clients would need to modify the href dynamically, negating the advantage of not needing to execute JS.
+- Does not automatically update for old revisions.
+- Increases fraction of re-renders that change the content.
+
+
+### 3) Parsoid DOM pass + html2html update end point
+
+As in `Parsoid DOM pass`, but also update red link markup in old revisions through a Parsoid HTML2HTML end point.
+
+Advantages: 
+
+- As for `Parsoid DOM pass`.
+- More up-to-date red link information in old revisions.
+
+Disadvantages:
+
+- Extra complexity in Parsoid and RESTBase.
+- Increased latency and cost for accesses to old revisions, especially if the update is applied on each request.",1340566560,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_description,resolved
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVzly25pU4b8yJAIAY5X} [2017-06-26T19:05:33Z] <mobrovac@tin> Finished deploy [restbase/deploy@3975ab2]: Update Parsoid HTML version to 1.5.0 - T39902 (duration: 06m 16s)",1498503933,PHID-USER-j4uyesgqhubl2dywl4xd,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVzlxbBhU4b8yJAIAY5J} [2017-06-26T18:59:17Z] <mobrovac@tin> Started deploy [restbase/deploy@3975ab2]: Update Parsoid HTML version to 1.5.0 - T39902",1498503557,PHID-USER-j4uyesgqhubl2dywl4xd,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVzlvvIiU4b8yJAIAY40} [2017-06-26T18:51:55Z] <arlolra> Updated Parsoid to b59045f2 (T39902, T149794)",1498503115,PHID-USER-j4uyesgqhubl2dywl4xd,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Change 351537 merged by jenkins-bot:
+[mediawiki/services/parsoid@master] Implement rendering of redlinks, etc. as a post-processor
+
+[[https://gerrit.wikimedia.org/r/351537]]
+",1497459707,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Change 351537 had a related patch set uploaded (by Arlolra; owner: Arlolra):
+[mediawiki/services/parsoid@master] WIP: Port VE's LinkCache::styleElement
+
+[[https://gerrit.wikimedia.org/r/351537]]
+",1493764578,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,See https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/HEAD/modules/ve-mw/init/ve.init.mw.LinkCache.js,1493069684,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,To highlight one of the blocked tasks: T119266 makes for a pretty bad user experience in the Android app.,1484055996,PHID-USER-wlku5ja6envbi4cz2etp,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Change 303827 abandoned by Arlolra:
+[WIP] Add redlinks to a doc
+
+Reason:
+Per offsite
+
+[[https://gerrit.wikimedia.org/r/303827]]",1476815077,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@ssastry, I put this on the list for the next services / parsoid sync meeting. Red links are frequently requested, and we now have the tools to implement this efficiently.",1475787000,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2537871, @Legoktm wrote:
+> Unfortunately, relying on the links API or the current database state isn't enough. We also have to be aware of `Title::isKnown()`, so things like special pages are blue if they exist, foreign files/global user pages (and future shadow namespaces) are looked up remotely.
+
+I see {T141963} already exists.
+
+Also, BTW, the suggested API query already handles Special- and Media-namespace links. That does leave MediaWiki-namespace links and anything using the 'TitleIsAlwaysKnown' hook.",1471285541,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2537460, @Pchelolo wrote:
+> So at this point #changeprop knows which particular redlink was updated and can give this information to #restbase and #parsoid. So if #parsoid implements this an an html2html endpoint with the semantics of 'add/remove redlink information to this one particular title' - it wouldn't need to call MW API at all.
+
+It should watch out for races.  Two pages are created in close succession.  The creation of Page_1 triggers a job to update that in the DOM to blue/exists.  While that is running, Page_2 is created, triggering another job.  It needs to not clobber the first.",1471049555,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,Per @gwicke at E258,1470861583,PHID-USER-edlps6xg553cjlnvd4ao,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2537460, @Pchelolo wrote:
+>
+> So at this point #changeprop knows which particular redlink was updated and can give this information to #restbase and #parsoid. So if #parsoid implements this an an html2html endpoint with the semantics of 'add/remove redlink information to this one particular title' - it wouldn't need to call MW API at all.
+
+The base case is not solved ... you are talking about steady state behavior after a revision has been rendered and stored. But, on page edit, when the page is reparsed, you need to set up red links which requires getting information from the API.
+
+>>! In T39902#2537871, @Legoktm wrote:
+> Unfortunately, relying on the links API or the current database state isn't enough. We also have to be aware of `Title::isKnown()`, so things like special pages are blue if they exist, foreign files/global user pages (and future shadow namespaces) are looked up remotely.
+
+This is not a problem per se. Whatever code in Mediawiki provides this functionality can be implemented in the ParsoidBatchAPI extension / API call providing the functionality, unless I am missing something.",1470773166,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Unfortunately, relying on the links API or the current database state isn't enough. We also have to be aware of `Title::isKnown()`, so things like special pages are blue if they exist, foreign files/global user pages (and future shadow namespaces) are looked up remotely.",1470772294,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2537353, @GWicke wrote:
+>> Rely on Change Propagation to provide Parsoid the information about what redlinks to update
+> 
+> This is a possible optimization, but if that precise information is not available right away we could perhaps start by indicating ""update all red links"" only. See {T114413} for more on the html2html end point.
+
+Basically we already have (partially) code in CP to propagate redlinks updates, but it's not enabled. What it would do is on each new page creation/deletion it would go over the links table to see which pages were linking to this one and send rerender requests to each of those pages.
+
+So at this point #changeprop knows which particular redlink was updated and can give this information to #restbase and #parsoid. So if #parsoid implements this an an html2html endpoint with the semantics of 'add/remove redlink information to this one particular title' - it wouldn't need to call MW API at all.
+
+We could even not involve parsoid and do it with a regex in #restbase (I'm joking)",1470766766,PHID-USER-gpb2ynmxbgmy4ld2555w,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"> I am not opposed to this, but, can someone summarize what led to this change?
+
+Red links change rarely, and we do have information & infrastructure to propagate those changes. This means that it is significantly cheaper (esp. for the PHP API) to only process red links on change, rather than on each view.
+
+> Rely on Change Propagation to provide Parsoid the information about what redlinks to update
+
+This is a possible optimization, but if that precise information is not available right away we could perhaps start by indicating ""update all red links"" only. See {T114413} for more on the html2html end point.",1470765567,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Thanks @RobLa-WMF for the summary and the poke. :) Looks like @arlolra submitted a wip patch already, but a bunch of details still need to be ironed out. So, I am moving that discussion here.
+
+So, it appears that the original idea of storing HTML (without redlinks) and doing a post-process on that HTML (in a html2html) pass has morphed into something different:
+* Render red links in Parsoid as part of the normal render.  Internally, the code can continue to be structured as a DOM transformation on the parsed HTML.
+* Rely on Change Propagation to provide Parsoid the information about what redlinks to update which can be done efficiently as a html2html transform (without reparsing the page from scratch).  T39902#2199600 has some options.
+
+I am not opposed to this, but, can someone summarize what led to this change? @GWicke ?
+
+But, in any case, no matter how / when the redlink transform happens, in order to get the redlinks info, we would have to query the mediawiki API. Here are a few different options for doing so:
+* @Anomie provided a link to the links API. That can work, but to get the full list of links the continue links would have to be navigated which is a bunch of API calls (in series, not parallel) in the general case which makes this inefficient and adds to the parse time.
+* It would be better would be to have a redlinks api call that only returns missing links (if that can be done efficiently). But, I understand that this is Parsoid-specific which brings me to the next alternative.
+* This can be done as part of the ParsoidBatchAPI extension (which has some custom Parsoid functionality already).
+* However, as far as I understand, all the 3 solutions above assume / require that the core parser to have already processed the page and is an unnecessary dependency. Instead, a better alternative would be to have Parsoid send a bunch of links to the API and request a list of links that don't have a corresponding page entry in the database. This functionality is probably best done in the ParsoidBatchAPI and also eliminates the dependency on the core parser.
+
+Thoughts?",1470765376,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Thanks @RobLa-WMF for the summary and the poke. :) Looks like @arlolra submitted a wip patch already, but a bunch of details still need to be ironed out. So, I am moving that discussion here.
+
+So, it appears that the original idea of storing HTML (without redlinks) and doing a post-process on that HTML (in a html2html) pass has morphed into something different:
+* Render red links in Parsoid as part of the normal render.  Internally, the code can continue to be structured as a DOM transformation on the parsed HTML.
+* Rely on Change Propagation to provide Parsoid the information about what redlinks to update which can be done efficiently as a html2html transform (without reparsing the page from scratch).  T39902#2199600 has some options.
+
+I am not opposed to this, but, can someone summarize what led to this change? @GWicke ?
+
+But, in any case, no matter how / when the redlink transform happens, in order to get the redlinks info, we would have to query the mediawiki API. Here are 3 different options for doing so:
+* @Anomie provided a link to the links API. That can work, but to get the full list of links the continue links would have to be navigated which is a bunch of API calls (in series, not parallel) in the general case which makes this inefficient and adds to the parse time.
+* It would be better would be to have a redlinks api call that only returns missing links (if that can be done efficiently). But, I understand that this is Parsoid-specific which brings me to the next alternative.
+* Aternatively, this can be done as part of the ParsoidBatchAPI extension (which has some custom Parsoid functionality already).
+* However, as far as I understand, all the 3 solutions above assume / require that the core parser to have already processed the page and is an unnecessary dependency. Instead, a better alternative would be to have Parsoid send a bunch of links to the API and request a list of links that don't have a corresponding page entry in the database. This functionality is probably best done in the ParsoidBatchAPI and also eliminates the dependency on the core parser.
+
+Thoughts?",1470765232,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Comment from Arlo's [Gerrit change 303827](https://gerrit.wikimedia.org/r/303827):
+> [WIP] Add redlinks to a doc
+> * Makes use of the suggestion here: T39902#2209625
+> * Since this is still a WIP, provides an internal qs param (_redlinks) to add them to wt2html requests.
+>This probably belongs in html2html, as described here: T39902#2240375
+> However, it's not clear that there's a consensus on doing that yet.
+> See the discussion [in T114413]
+",1470764678,PHID-USER-edlps6xg553cjlnvd4ao,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Change 303827 had a related patch set uploaded (by Arlolra):
+[WIP] Add redlinks to a doc
+
+[[https://gerrit.wikimedia.org/r/303827]]
+",1470762648,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2535493, @Arlolra wrote:
+>> @Anomie provided advice how to use the Action API to get redlink information.
+> 
+> Can you put that here?
+
+See his April 2016 comments, starting at T39902#2209625
+",1470705533,PHID-USER-edlps6xg553cjlnvd4ao,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"> @Anomie provided advice how to use the Action API to get redlink information.
+
+Can you put that here?",1470703746,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@Jdlrobson and I just had a really good conversation about this.  The thing #ArchCom (or someone) needs to provide is guidance for what code that someone (possibly Jon?) can contribute in order to accelerate progress on the redlink issue.  @anomie provided advice how to use the Action API to get redlink information.  @gwicke, is there any guidance you're waiting on the rest of #ArchCom for?  @ssastry, do you agree with @gwicke that Parsoid needs modification to provide redlink information in the HTML?",1470702038,PHID-USER-edlps6xg553cjlnvd4ao,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Here's my understanding of the chronology so far:
+1.  Filed by @jdforrester-wmf in 2012-06-24
+   * Title: ""//VisualEditor: Parsoid needs to hint on each 'internal' link as to the status of its target (redlink; stub; interwiki)//"" 
+   * Description: ""//For the arbitrary stub threshold preference, perhaps just hint with the character length of the link and leave it to the UI to decide how to render based on user preferences? This would mean that we wouldn't fragment the parser cache...//""
+   * Assignee: @GWicke
+2.  @Gwicke drops priority to lowest priority on 2012-06-29
+3.  Jan 2013: new title ""Implement rendering of redlinks and stubs"" (moved out of #Parsoid and into Bugzilla's ""General"" project) T39902#413848
+2.  Discussion in 2013, suggesting Action API changes, and hinting that ""bug 11"" (T2011) could be fixed by this
+3.  Feb 2014: James reports that @Catrope will attempt to implement this, ""at least as a first run"" and raises to high priority (T39902#413952).
+4.  March 2014: James fixes related issue T39901
+4.  Early 2015: James drops Roan as assignee, @ssastry drops priority to normal
+8. Sept 2015: @Jdlrobson expands the task description (T39902#1690785)
+1.  March 2016: @gwicke flags this as an #ArchCom-RFC
+8. April 2016:
+   * #ArchCom very briefly discusses this in E161 as part of our planning/triage
+   * @gwicke posts an implementation strategy, but remarks ""As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article."" (T39902#2208376)  
+   * @anomie responds, advising about how to do this, but cautions: ""//We might have to disable it (or reduce the functionality) in miser mode though, like we do with various other parameters, to avoid bugs like T97797.//"" (T39902#2209625)
+   * @gwicke ties this to the change propagation service (T133221) and suggests Parsoid would need to provide redlink markup as part of the re-render request (T114413). (T39902#2240375)
+9. August 2016: @Jdlrobson cross posts ""[Redlinks in Android app](https://lists.wikimedia.org/pipermail/wikitech-l/2016-August/086242.html)"" on mobile-l and wikitech-l: ""//I've cced wikitech in case anyone has an update.//""  
+
+Next steps?  I suppose #ArchCom can discuss this in E258, and possibly make this a candidate for one of our office hours in the not-to-distant future.  We can discuss the #ArchCom-RFC triage process in Z425.
+",1470601404,PHID-USER-edlps6xg553cjlnvd4ao,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"We are currently working on implementing the update logic in the change propagation service: T133221. This will trigger HTML re-renders for all pages linking to a created / deleted page. As part of the re-render request (see T114413), we will supply
+
+- an update mode ('redlinks', 'brokenlinks' or the like),
+- whether this is a deletion or creation, and
+- the created / deleted title (so that updates can be targeted).
+
+The number of update requests from this will be fairly small, so optimizations are not critical. However, for this to actually result in red links being inserted / updated, Parsoid will need to mark up red links as part of the normal render process.
+",1461690900,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2209625, @Anomie wrote:
+>>>! In T39902#2208376, @GWicke wrote:
+>> This end point already supports restricting links to a specific namespace using the `plnamespace` parameter.  Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. 
+> 
+> We might have to disable it (or reduce the functionality) in miser mode though, like we do with various other parameters, to avoid bugs like T97797.
+
+The current query for this module is reasonably simple, basically
+```
+-- Generic
+SELECT pl_from, pl_namespace, pl_title FROM pagelinks WHERE pl_from IN (...) ORDER BY pl_from ASC, pl_namespace ASC, pl_title ASC LIMIT 501;
+
+-- With plnamespace
+SELECT pl_from, pl_namespace, pl_title FROM pagelinks WHERE pl_from IN (...) AND pl_namespace IN (...) ORDER BY pl_from ASC, pl_namespace ASC, pl_title ASC LIMIT 501;
+```
+
+Adding a `plbrokenlinks` parameter would require joining with `page`, though:
+```
+SELECT pl_from, pl_namespace, pl_title FROM pagelinks LEFT JOIN page ON (pl_namespace = page_namespace AND pl_title = page_title) WHERE pl_from IN (...) AND page_id IS NULL ORDER BY pl_from ASC, pl_namespace ASC, pl_title ASC LIMIT 501;
+```
+Just a join there is probably not too bad (it's an `eq_ref` which isn't a bad join type, although it's still a join on a 261-byte key so it's not the greatest), but using the join as a filter where the vast majority of the time the filter is going to fail would certainly be a T97797 issue waiting to be reported.
+
+So what you'd end up with on WMF wikis is that using your `plbrokenlinks` parameter would do a query more like
+```
+SELECT pl_from, pl_namespace, pl_title, page_id FROM pagelinks LEFT JOIN page ON (pl_namespace = page_namespace AND pl_title = page_title) WHERE pl_from IN (...) ORDER BY pl_from ASC, pl_namespace ASC, pl_title ASC LIMIT 501;
+```
+then on the PHP side it would filter out the rows with `$row->page_id !== null`, typically leaving zero to actually be returned and a continuation for it to do the same check on the next batch of links.",1461004303,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@anomie, thanks for the input! And sorry to hear about the flu- hope you are better soon!",1460743811,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#2208376, @GWicke wrote:
+> As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest).
+
+You could use something like https://en.wikipedia.org/w/api.php?action=query&generator=links&titles=User:GWicke/LinkTest.
+
+> This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. 
+
+We might have to disable it (or reduce the functionality) in miser mode though, like we do with various other parameters, to avoid bugs like T97797.
+
+I'll try to remember to look at it next week when I'm over the flu.",1460723870,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Based on the performance information we have from elematch, I think it is clear that updating red link information server-side is doable at very moderate cost. Here is a proposal:
+
+### Implement red link updates in change propagation
+
+The recently deployed change propagation service will follow page creation / deletion events, and will initiate red link updates for all pages linking to the created / deleted pages. (#services)
+
+### Parsoid to mark red links with an attribute by default
+
+Regular parse: Parsoid will request a list of red links from the API, and annotate <a> elements with appropriate attributes in a DOM pass. 
+
+Update: When getting a 'red link update' request from the change propagation service, RESTBase will pass the current HTML and **the update mode (""redlinks"")** to Parsoid, the same way it already does right now for template or image updates. Parsoid will then update red links using any technique of its choosing. For example, it could do this using elematch, avoiding the need for expensive DOM parsing. (#parsing-team)
+
+### Issue: API for red links
+
+As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest). Nor does it support only retrieving red links.
+
+This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. 
+
+@Anomie @ssastry @Pchelolo @mobrovac @Arlolra, does this sound sane to you?
+
+(#services or #parsing-team)",1460667870,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Based on the performance information we have from elematch, I think it is clear that updating red link information server-side is doable at very moderate cost. Here is a proposal:
+
+### Implement red link updates in change propagation
+
+The recently deployed change propagation service will follow page creation / deletion events, and will initiate red link updates for all pages linking to the created / deleted pages. (#services)
+
+### Parsoid to mark red links with an attribute by default
+
+Regular parse: Parsoid will request a list of red links from the API, and annotate <a> elements with appropriate attributes in a DOM pass. 
+
+Update: When getting a 'red link update' request from the change propagation service, RESTBase will pass the current HTML and **the update mode (""redlinks"")** to Parsoid, the same way it already does right now for template or image updates. Parsoid will then update red links using any technique of its choosing. For example, it could do this using elematch, avoiding the need for expensive DOM parsing. (#parsing-team)
+
+### Issue: API for red links
+
+As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest). Nor does it support only retrieving red links.
+
+This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. @Anomie, does this sound sane to you?
+
+(#services or #parsing-team)",1460667723,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Based on the performance information we have from elematch, I think it is clear that updating red link information server-side is doable at very moderate cost. Here is a proposal:
+
+### Implement red link updates in change propagation
+
+The recently deployed change propagation service will follow page creation / deletion events, and will initiate red link updates for all pages linking to the created / deleted pages. (#services)
+
+### Parsoid to mark red links with an attribute by default
+
+Regular parse: Parsoid will request a list of red links from the API, and annotate <a> elements with appropriate attributes in a DOM pass. 
+
+Update: When getting a 'red link update' request from the change propagation service, RESTBase will pass the current HTML and **the update mode (""redlinks"")** to Parsoid, the same way it already does right now for template or image updates. Parsoid will then update red links using any technique of its choosing. For example, it could do this using elematch, avoiding the need for expensive DOM parsing. (#parsing)
+
+### Issue: API for red links
+
+As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest). Nor does it support only retrieving red links.
+
+This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. @Anomie, does this sound sane to you?
+
+(#services or #parsing-team)",1460667711,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Based on the performance information we have from elematch, I think it is clear that updating red link information server-side is doable at very moderate cost. Here is a proposal:
+
+### Implement red link updates in change propagation
+
+The recently deployed change propagation service will follow page creation / deletion events, and will initiate red link updates for all pages linking to the created / deleted pages. (#services)
+
+### Parsoid to mark red links with an attribute by default
+
+Regular parse: Parsoid will request a list of red links from the API, and annotate <a> elements with appropriate attributes in a DOM pass. 
+
+Update: When getting a 'red link update' request from the change propagation service, RESTBase will pass the current HTML and **the update mode (""redlinks"")** to Parsoid, the same way it already does right now for template or image updates. Parsoid will then update red links using any technique of its choosing. For example, it could do this using elematch, avoiding the need for expensive DOM parsing. (#services)
+
+### Issue: API for red links
+
+As far as I am aware, there is currently no API that lets us efficiently retrieve the list of red links in the current version of a given article. https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blinks provides a full list of links, but [does not mark red links specially](https://en.wikipedia.org/w/api.php?action=query&prop=links&titles=User:GWicke/LinkTest). Nor does it support only retrieving red links.
+
+This end point already supports restricting links to a specific namespace using the `plnamespace` parameter. Along the same lines, we could add a `plbrokenlinks` flag parameter, which would restrict the returned list of titles to broken / red links only. @Anomie, does this sound sane to you?
+
+(#services or #parsing-team)",1460667674,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"A patch for element & attribute matching is now up at https://github.com/wikimedia/elematch/pull/5. Performance results for Obama (1.5mb):
+
+- match / replace all figures: 1.95ms
+- match / replace all links: 13.9ms
+- **match / replace a *specific* link (`a[href=""./Riverdale,_Chicago""]`): 1.9ms**
+- match / replace references section (`ol[typeof=""mw:Extension/references""]`): 3.7ms
+
+Other options:
+- libxml XML DOM round-trip (no matching): 51.1ms
+  - plus xpath match: ~15ms
+- domino round-trip (no matching): 255.3ms
+
+This means that we can dynamically update red links in large documents using less than ~2ms of cpu time. This is over a magnitude less than libxml in XML mode, the next best option.",1460479663,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"A patch for element & attribute matching is now up at https://github.com/wikimedia/elematch/pull/5. Performance results for Obama (1.5mb):
+
+- match / replace all figures: 1.95ms
+- match / replace all links: 13.9ms
+- **match / replace a *specific* link: 1.9ms**
+- match / replace references section (`ol[typeof=""mw:Extension/references""]`): 3.7ms
+
+Other options:
+- libxml XML DOM round-trip (no matching): 51.1ms
+  - plus xpath match: ~15ms
+- domino round-trip (no matching): 255.3ms
+
+This means that we can dynamically update red links in large documents using less than ~2ms of cpu time. This is over a magnitude less than libxml in XML mode, the next best option.",1460479419,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a full DOM parse + XPath match, but incurs some extra cost for DOM serialization.
+
+The cost is directly proportional to the number of elements matched. For comparison, matching only <figure> elements in Obama takes only 2ms.
+
+Edit: Updated benchmark results at https://github.com/wikimedia/elematch#performance
+
+Edit 2: Assuming XML spec compatible serialization, it turns out that we should actually be able to implement relatively efficient matches on attribute values as well. There are several gotchas around optional entity encoding, but they look solvable so far. I'll try to explore this approach in [elematch](https://github.com/gwicke/elematch).",1459546168,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a full DOM parse + XPath match, but incurs some extra cost for DOM serialization.
+
+The cost is directly proportional to the number of elements matched. For comparison, matching only <figure> elements in Obama takes only 2ms.
+
+Edit: Updated benchmark results at https://github.com/wikimedia/elematch#performance",1458948750,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a full DOM parse + XPath match, but incurs some extra cost for DOM serialization.
+
+The cost is directly proportional to the number of elements matched. For comparison, matching only <figure> elements in Obama takes only 2ms.",1458762366,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a full DOM parse + XPath match, but incurs some extra cost for DOM serialization.",1458762273,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a rough idea of the cost of server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of CPU time. LibXML offers similar performance for a pull DOM parse + XPath match, but incurs some extra cost for DOM serialization.",1458762250,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"To provide a lower bound on server-side link processing, matching / processing all 1852 links in [[Barack Obama] using https://github.com/wikimedia/elematch takes about 32ms of cpu time. LibXML offers similar performance for a pull DOM parse + XPath match, but incurs some extra cost for DOM serialization.",1458762059,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"cscott: the image blocklist is actually very very small, much fewer than 1000 images on there.
+cscott: i'm not worried about caching the image as blocked in the archive.  it's the same as any other template dependency; the page ""as it looks right now"" depends on the current state of the image blocklist.
+cscott: because it's small and a corner case, i don't think it should drive redlink discussions/decisions.
+
+redlinks are orders of magnitude more common.  let's not try to make these two cases the same thing.",1458761460,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@ssastry, I have added option 3) as an extension in the task description.
+
+One question we should make up our mind on is whether we would rewrite href attributes to point to edit views, to match what is currently done on the web. Doing so would complicate further processing:
+
+- VisualEditor would need to strip ?action=edit from its link widget. The same will likely be true for other clients, like mining of link graphs.
+- Matching could not rely on the plain href, but would need to either match on a mangled href, or use other attributes like a class instead.
+
+If we decide to not mangle href, then web clients would need to do so after the fact, negating the advantage of not needing to run JS.
+
+Another consideration is that link updates in old revisions are currently only efficiently possible using link information from the latest revision. This means that links that were only present in the older revision won't be checked for existence in queries based on the latest revision's links.
+
+In the context of the API-driven front-end effort, it seems likely that we'll serve metadata about a page separately. This metadata would contain red links, language links (from wikidata), categories, table of content hints and more. If we assume that we'll need this anyway for other bits of metadata, then the extra cost of a general page metadata request is becoming less of an issue in this discussion.
+
+So, overall I'm still torn, but am starting to lean more towards 1) than 2) / 3).",1458755702,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"@ssastry, I have added option 3) as an extension in the task description.
+
+One question we should make up our mind on is whether we would rewrite href attributes to point to edit views, to match what is currently done on the web. Doing so would complicate further processing:
+
+- VisualEditor would need to strip ?action=edit from its link widget. The same will likely be true for other clients, like mining of link graphs.
+- Matching could not rely on the plain href, but would need to either match on a mangled href, or use other attributes like a class instead.
+
+If we decide to not mangle href, then web clients would need to do so after the fact.
+
+Another consideration is that link updates in old revisions are currently only efficiently possible using link information from the latest revision. This means that links that were only present in the older revision won't be checked for existence in queries based on the latest revision's links.
+
+In the context of the API-driven front-end effort, it seems likely that we'll serve metadata about a page separately. This metadata would contain red links, language links (from wikidata), categories, table of content hints and more. If we assume that we'll need this anyway for other bits of metadata, then the extra cost of a general page metadata request is becoming less of an issue in this discussion.
+
+So, overall I'm still torn, but am starting to lean more towards 1) than 2) / 3).",1458755650,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Soln 3: Provide a Parsoid API endpoint that transforms stored HTML with red link info added in. But, this will require some caching / temporary storage  (and associated invalidation) to alleviate performance impact of a secondary api request.
+Soln 2 will cause old revisions to render broken.
+Soln 1 is the ideal solution.
+
+That said, this question will surface again for ""bad images"". For ""bad images"", we do not have the luxury of breaking old revisions. Bad images are probably expected to be blacklisted in all revisions. Plus, client-side solution for that will probably not be acceptable for the no-js case since those images will render in full glory.
+
+It seems like we should pick a solution that works in both scenarios => solution 3?",1458689807,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Soln 3: Provide a Parsoid API endpoint that transforms stored HTML with red link info added in. But, this will require some caching / temporary storage  (and associated invalidation) to alleviate performance impact of a secondary api request.
+Soln 2. => old revisions will render broken.
+Soln 1 is the ideal solution.
+
+That said, this question will surface again for ""bad images"". For ""bad images"", we do not have the luxury of breaking old revisions. Bad images are probably expected to be blacklisted in all revisions. Plus, client-side solution for that will probably not be acceptable for the no-js case since those images will render in full glory.
+
+It seems like we should pick a solution that works in both scenarios => solution 3?",1458689368,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Soln 3: Provide a Parsoid API endpoint that transforms stored HTML with red link info added in. But, this will require some caching / temporary storage  (and associated invalidation) to alleviate performance impact of a secondary api request.
+Soln 2. => old revisions will render broken.
+Soln 1 is the ideal solution.
+
+That said, this question will surface again for ""bad images"". For ""bad images"", we do not have the luxury of breaking old revisions. Bad images are probably expected to be blacklisted in all revisions. Plus, client-side solution for that will probably not be acceptable for the no-js case since those images will render in full glory.
+
+It seems like we should pick a solution that works in both scenarios. ",1458689321,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"We discussed this again in today's Reading / Services sync-up meeting. We really need to figure out a general solution for this to avoid each client needing to implement their own.
+
+In the discussion, the consensus was that external metadata might also be workable, but inline information would be easier to work with. I have updated the task description with some use cases, requirements & pros / cons of each approach. Please update / add your view, so that we can decide on the way forward soon.",1458681763,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"I wouldn't hold that patch up as an example, though, at least in its current form; we had to un-deploy it because of memory issues.",1457654688,PHID-USER-d2tiurktk2jgxzcpd2jw,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,https://gerrit.wikimedia.org/r/#/c/274638/ has a patch implementing red link hiding in the mobile app content service.,1457651778,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#1694428, @GWicke wrote:
+>>>! In T39902#413952, @Jdforrester-WMF wrote:
+>> Roan's going to try to work on this, at least as a first run.
+> 
+> Famous last words ;)
+
+This was complete two weeks later – {T39901}.
+
+> I am wondering if we could implement this at the edge / client after all, as part of a setup like T111588. Idea would be:
+> 
+> 1) API providing an array of links in the page that don't exist, and
+> 2) JS skin code running in a service worker or in nodejs on the edge generating CSS to style red links, or JS code running on the DOM to add classes.
+
+{T64803} is the task to turn the current client-side VE code into a service that provides an additional stylesheet per your recommendation – something like:
+
+  restbase/styleContent/page/Foobar/revision/123456
+
+… which returns a stylesheet like
+
+  a[href=LinkDoesNotExist],
+  a[href=AnotherLinkDoesNotExist]
+  { color: red; }
+
+… or whatever.",1446686133,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"I would prefer to add a class to the DOM. The app can provide the CSS rules to style it or do something else with it (like replace the link with a span).
+
+This task is very old already. Any chance of getting this in soon?",1446576329,PHID-USER-tjyfydvd4ncrfvvr6mkr,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,">>! In T39902#413952, @Jdforrester-WMF wrote:
+> Roan's going to try to work on this, at least as a first run.
+
+Famous last words ;)
+
+I am wondering if we could implement this at the edge / client after all, as part of a setup like T111588. Idea would be:
+
+1) API providing an array of links in the page that don't exist, and
+2) JS skin code running in a service worker or in nodejs on the edge generating CSS to style red links, or JS code running on the DOM to add classes.",1443726232,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Roan's going to try to work on this, at least as a first run.",1393538172,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(In reply to comment #14)
+> (In reply to comment #13)
+> > As a note, if we did this cross-cluster, that would fix bug 11 (!) which
+> > would be a lovely additional feature.
+> 
+> Sounds doable with separate API requests to each target wiki. Or even HEAD
+> requests for external links, so that even non-wiki external links could be
+> redlinked ;)
+
+That would just be showing off. :-)",1378418392,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(In reply to comment #13)
+> As a note, if we did this cross-cluster, that would fix bug 11 (!) which
+> would
+> be a lovely additional feature.
+
+Sounds doable with separate API requests to each target wiki. Or even HEAD requests for external links, so that even non-wiki external links could be redlinked ;)",1378418353,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"As a note, if we did this cross-cluster, that would fix bug 11 (!) which would be a lovely additional feature.",1378416210,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"For stub thresholds, the API could also return an array of linked articles and their respective size. I think it would be fine to put the burden of an additional request onto those few users using stub indicators (they are disable d by default). The actual rendering can be done client-side based on that user's stub thresholds, which can sadly be arbitrary byte sizes.",1364588810,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(In reply to comment #10)
+> Presumably an optional parameter to that core API is ""stub length
+> preference"".
+
+That could work, but feels a little messy. Gabriel as guardian of all that is appropriate coding might well have some thoughts. :-)",1364365941,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Presumably an optional parameter to that core API is ""stub length preference"".",1364354581,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(In reply to comment #8)
+> One option might be to merge in information from another API into the <head>
+> of the document which parsoid returns, to minimize round trips -- but in that
+> case the API should first be added to core.  The simplest possible API would
+> supply the name of an article and get back an array of stubbed or red links
+> in that article.
+
+Only problem is that this doesn't solve the ""colouring stubs differently at a user-set arbitrary byte length"" preference; I'd be reasonably OK with us removing that feature anyway, but that should be an actual decision discussed with people rather than just over-looked. :-)",1364351527,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"One option might be to merge in information from another API into the <head> of the document which parsoid returns, to minimize round trips -- but in that case the API should first be added to core.  The simplest possible API would supply the name of an article and get back an array of stubbed or red links in that article.",1364335396,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,Changing component to general- this would either happen in MediaWiki PHP/DOM post-processing or the client side.,1359413223,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"Moving this to the CPP DOM subcomponent for now, as this would be something to implement on the DOM if it is going to be done on the server side. A JS-only implementation could also use node to work on the server-side DOM as a fall-back for non-js clients.",1344288190,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,Mass-moving bugs into the new 'Parsoid' product.,1344281141,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"IMO this should not be the task of the parser however, hence the low priority on this bug.",1342990813,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"I'm a bit surprised about the importance. Coloring for stub may be an enhancement, but a link to a nonexistent page definitely shouldn't be blue.",1342869964,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,"(Mark as ASSIGNED for completeness.)
+
+Yes, worth discussing.",1340568633,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+RFC: Implement rendering of redlinks in Parsoid HTML as post-processor,See my reply in bug #37901. I'd prefer to take the opportunity and move as many user preferences out of the parser as possible.,1340568582,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yny6sbrvi7mgfvctnaj2,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"To show red links (and stub links) correctly, Parsoid will need to hint on each link as to the status of its target. Also some work in CE and UI. ;-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=38726",1340565720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_description,resolved
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Verified, working fine on the English and Italian Wikipedias.",1396033621,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to pamdavies7 from comment #25)
+> It doesn't seem to be resolved. I found
+> https://en.wikipedia.org/wiki/Demented_Are_Go#Studio_albums by hitting
+> ""Random article"" until I found a redlink, tried to edit it in VE, and the
+> red link (""Welcome back to Insanity Hall "") looked blue. Am I missing
+> something?
+> 
+> In case it was any of my settings, I tried again using my (declared)
+> alternative account which has default settings for everything: went to
+> preferences to enable VE, tried editing that article, still a blue link.
+
+The code is not yet deployed to the English Wikipedia. It will be deployed today to MediaWiki.org (hence the date in the ""milestone""), and to the English Wikipedia in a week, following the regular schedule.",1395333876,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"It doesn't seem to be resolved. I found https://en.wikipedia.org/wiki/Demented_Are_Go#Studio_albums by hitting ""Random article"" until I found a redlink, tried to edit it in VE, and the red link (""Welcome back to Insanity Hall "") looked blue. Am I missing something?
+
+In case it was any of my settings, I tried again using my (declared) alternative account which has default settings for everything: went to preferences to enable VE, tried editing that article, still a blue link.",1395333779,PHID-USER-7zhn2ep5wvjhxetsbb6n,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Change 118045 merged by jenkins-bot:
+Display links to nonexistent pages as red
+
+https://gerrit.wikimedia.org/r/118045",1395283464,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Change 118045 had a related patch set uploaded by Jforrester:
+[WIP] Red link support
+
+https://gerrit.wikimedia.org/r/118045",1395179140,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Change 118045 had a related patch set uploaded by Jforrester:
+[WIP] Red link support
+
+https://gerrit.wikimedia.org/r/118045",1394500950,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Revert. Lots of ""basic"" features are enhancements. Bugs are ""this should already be working and its lack of presence is a code failure"". Noting however that this is high priority.",1385369238,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Changing importance to ""Normal"". Even though it's not a regression compared to the source editor, common sense says that it should be a basic feature of VE and not an ""Enhancement"".",1385369038,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 56442 has been marked as a duplicate of this bug. ***,1383277462,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"**jonathan.haas** wrote:
+
+(In reply to comment #16)
+> * Internal links
+> ** If the page does not exist, colour it red
+> ** If the page does exist but is a disambiguation page, colour it yellow
+> ** If the page does exist but is under (arbitrary) stub threshold, colour it
+> purple
+> ** Elsewise, colour it dark blue
+
+Don't forget about redirection pages. In some Wikipedia's it is probably bad practice to link them. In german Wikipedia, it's okay to link them, but only if the link target makes more sense than the main page title. So in any case it's nice to see that the link target is a redirect. A bonus would be a tooltip which shows the page the redirect redirects to.
+
+(In reply to comment #6)
+> This can be implemented with a generated CSS file containing attribute
+> selectors matching red link targets like this:
+> 
+> a[href=""./Foo""],
+> a[href=""./Bar""] { color: red }
+
+This is a really horrible idea. About 5% of the population are color blind, you really don't want to hardcode colors like this in any way. If embedding this information in the page source is technically impossible for whatever reason, then load a list of external pages using JS and add css classes or other attributes on the fly.",1378103629,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to comment #16)
+
+> * Internal links
+> ** If the page does not exist, colour it red
+> ** If the page does exist but is a disambiguation page, colour it yellow
+> ** If the page does exist but is under (arbitrary) stub threshold, colour it
+> purple
+> ** Elsewise, colour it dark blue
+
+If the link is a redirect, will the system pick up the properties of the target page or just code it as a stub because it's short? (Target could be a dab page, stub, or normal page).",1378073610,PHID-USER-7zhn2ep5wvjhxetsbb6n,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to comment #14)
+> This is an 80/20 issue - 80% of the value comes from fixing just the coloring
+> of internal wikilinks. Coloring of external links isn't critical. (There can
+> be
+> significant time-delay in getting 404 or similar error codes for page
+> non-existence, as well as false negatives when a website is temporarily
+> down.)
+> And of the internal wikilinks, most of the value is redlinks, some of the
+> value
+> is disambiguation pages, and little of the value is stubs (which, again, are
+> subject to false positives, since article assessments aren't automated).
+> 
+> In short, the priority ought to be to code internal wikilinks that go to
+> non-existent pages (as red), and internal wikilinks that go to disambiguation
+> pages (as yellow, I think), and not to worry all that much about anything
+> else.
+
+The solution we're considering is a service that, given an array of links, returns a set of CSS selectors that VE applies to the page, to give the appropriate hinting on links.
+
+To be very specific, we are talking about:
+
+* Internal links
+** If the page does not exist, colour it red
+** If the page does exist but is a disambiguation page, colour it yellow
+** If the page does exist but is under (arbitrary) stub threshold, colour it purple
+** Elsewise, colour it dark blue
+
+* External links
+** If the link is to a wiki that is ""internal"" (i.e., an interwiki), colour it mid-blue
+** Elsewise, colour it mid-blue with an ""external link"" icon.
+
+It is a mistake to think that doing this but only for internal link state and only for existence/non-existence is 20% of the work for 80% of the gain; it's much more like 90% of the work for 80% of the gain. :-) Building the service itself is definitely the hard part of this.",1377959776,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to comment #14)
+> This is an 80/20 issue - 80% of the value comes from fixing just the coloring
+> of internal wikilinks. Coloring of external links isn't critical.
+
+
+I don't think anyone suggested (or has ever implemented?) coloring of external links. They only change color based on your browser settings, for clicked/unclicked links (essentially).
+
+
+> And of the internal wikilinks, most of the value is redlinks, some of the
+> value
+> is disambiguation pages, and little of the value is stubs (which, again, are
+> subject to false positives, since article assessments aren't automated).
+
+
+Stubs are colored based on byte-count, not whether they're tagged-as-a-stub. You can change the byte-count in your [[special:preferences]], under ""Appearance->Threshold for stub link formatting (bytes):[dropdownmenu]""
+
+
+> In short, the priority ought to be to code internal wikilinks that go to
+> non-existent pages (as red), and internal wikilinks that go to disambiguation
+> pages (as yellow, I think), and not to worry all that much about anything
+> else.
+
+
+Agreed that only redlinks are crucial. 
+
+For disambig links, possibly the new Property system can help?
+https://en.wikipedia.org/wiki/Special:PagesWithProp?propname=disambiguation&propname-other=
+
+For anything more complex than that, Anomie's Linkclassifier code might be useful/insightful. 300+ users have it installed. I recommend the ""run on demand"" version. https://en.wikipedia.org/wiki/User:Anomie/linkclassifier
+code at https://en.wikipedia.org/wiki/User:Anomie/linkclassifier.js",1377929906,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"This is an 80/20 issue - 80% of the value comes from fixing just the coloring of internal wikilinks. Coloring of external links isn't critical. (There can be significant time-delay in getting 404 or similar error codes for page non-existence, as well as false negatives when a website is temporarily down.) And of the internal wikilinks, most of the value is redlinks, some of the value is disambiguation pages, and little of the value is stubs (which, again, are subject to false positives, since article assessments aren't automated).
+
+In short, the priority ought to be to code internal wikilinks that go to non-existent pages (as red), and internal wikilinks that go to disambiguation pages (as yellow, I think), and not to worry all that much about anything else.",1377917820,PHID-USER-hirrhium5ibrtof34lwa,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),Right now the linking problems detected only after saving the page. So please raise the importance of this bug and fix it on priority.,1376796900,PHID-USER-4jecvpv4h62htut6pxez,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"(In reply to comment #10)
+> There has just been another editor on en.wp requesting this functionality. 
+> 
+> (In reply to comment #9)
+> > Would it be possible also to make other kinds of pages to appear in different
+> > colours, by changing CSS pages on the local wikis? I know that some wikis
+> > have
+> > different colours for redirects (green), others make links to disambiguation
+> > pages appear highlighted in yellow.
+> 
+> That is bug 52173. Although there was some discussion about whether that was
+> a duplicate of this the consensus seemed to be that it wasn't.
+
+That bug was asking for the same problem to be fixed, but was suggesting a different technical solution (and one which is a WONTFIX from the Parsoid team, as it makes the cached pages get invalidated by other pages getting created/deleted/expanded out of the stub threshold/made into/out of a redirect/made into/out of a disambiguation page). Sorry for the confusion.",1375303713,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 52173 has been marked as a duplicate of this bug. ***,1375303572,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"There has just been another editor on en.wp requesting this functionality. 
+
+(In reply to comment #9)
+> Would it be possible also to make other kinds of pages to appear in different
+> colours, by changing CSS pages on the local wikis? I know that some wikis
+> have
+> different colours for redirects (green), others make links to disambiguation
+> pages appear highlighted in yellow.
+
+That is bug 52173. Although there was some discussion about whether that was a duplicate of this the consensus seemed to be that it wasn't.",1375303150,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Would it be possible also to make other kinds of pages to appear in different colours, by changing CSS pages on the local wikis? I know that some wikis have different colours for redirects (green), others make links to disambiguation pages appear highlighted in yellow.",1374836101,PHID-USER-myojicphhrv5eiqtoq52,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"We don't want to encode this information in the DOM to avoid cache updates for the page content. There is really no need to do so since CSS selectors work well these days, and purging / regenerating CSS is much cheaper than updating page content.",1373556054,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"Normally, in article view mode, redlinks have CSS class ""new"" and I'm suggesting doing it in the same way for the sake of consistency.",1373555910,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"This can be implemented with a generated CSS file containing attribute selectors matching red link targets like this:
+
+a[href=""./Foo""],
+a[href=""./Bar""] { color: red }
+
+Alternatively a JSON file containing the redlink targets could be fetched and a redlink class set on each of them. CSS seems to be the more elegant solution without a need for JS and DOM changes though.
+
+In the longer term this is something we should implement for core too.",1373386102,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 50974 has been marked as a duplicate of this bug. ***,1373353929,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 50020 has been marked as a duplicate of this bug. ***,1371912053,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),*** Bug 49475 has been marked as a duplicate of this bug. ***,1371049016,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"It is actually shown as blue links which are considered to be existing pages. This is confusing.  I understand the parsoid isn't doing existence checks at all, so better use a natural color for all links.",1366924344,PHID-USER-u7udgblfyop6qd5wxot6,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate),"So far my idea is to keep link existence checks out of Parsoid, and add the colors from JS or CSS instead. This should avoid some parser cache invalidations and makes the parser output less dependent on user preferences.
+
+To do this, a data structure with the status of all outgoing links in a page would need to be fetched separately. This could be a JSON structure, or a CSS file that directly matches some target-hash-based classes on links.
+
+Doing the same for media or images would be harder, and is not something we plan to do right now. We'll instead render them normally, and perform the existence check in the parser while retrieving the image dimensions.",1340568470,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7km7sjcw27m7salmhqyx,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Tested in Firefox 16 nightly.
+
+Steps to repro:
+* go to https://www.mediawiki.org/wiki/VisualEditor:Welcome
+* hit 'edit'
+* click in, select all, copy to clipboard
+* go to https://www.mediawiki.org/wiki/VisualEditor:Blorpo etc
+* hit 'edit'
+* click in, paste
+
+Expected results:
+Beautiful pasted HTML
+
+Actual results:
+All formatting lost. Newlines are turned into little newline symbols.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340418900,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_description,resolved
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Sorry, not ""fixed"" but duplicate of bug 33105.
+
+*** This bug has been marked as a duplicate of bug 33105 ***",1375942744,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Just copy content from a page (e.g. https://it.wikipedia.org/wiki/Fire?veaction=edit) and paste in another one (e.g. https://it.wikipedia.org/wiki/Phantom?veaction=edit) :-) all the links, italics, lists etc. are lost.",1374852759,PHID-USER-myojicphhrv5eiqtoq52,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Francisco: Exact steps to reproduce highly welcome, so developers can take a look.",1374852358,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,I have to confirm that this bug still occurs on it.wiki.,1374845048,PHID-USER-myojicphhrv5eiqtoq52,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"(In reply to comment #6)
+> Bug 33105 is *not* general c'n'p, it's only c'n'p from external sources.
+
+You're right, sorry, I didn't update the title. Fixed. (Also, another VE instance is definitely an external source.)",1373143762,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Bug 33105 is *not* general c'n'p, it's only c'n'p from external sources.",1373142524,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"This was replaced with bug 33105 (general copy-and-paste)
+
+*** This bug has been marked as a duplicate of bug 33105 ***",1372795675,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"This bug seems to be occurring again.  Same issue- format loss.
+
+Ref:
+https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=561998028&oldid=561996397",1372444393,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,will thst work between wikis?,1340990138,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"**orbit** wrote:
+
+This is fixed in:
+https://gerrit.wikimedia.org/r/#/c/13423/
+
+Previously, copied data was stored in a local JS variable. Only copy and paste from within a single document was supported. Now, using localStorage, rich content may be copied from one article to another on the same wiki in the same browser.",1340929791,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Cut-n-paste from one window to another loses formatting,"Same behavior in Firefox 13, Chrome 19, Safari 5.1.7 (though Chrome & Safari don't show the little newline symbols, you just don't get line breaks at all).
+
+This makes common editing tasks like moving text from one page to another impossible, so might want to bump priority up.",1340470722,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-hlh4ejepruxcb5g2rrjr,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,"VE should give nice error messages (where possible, graceful degradation?) to users without JavaScript or not using Vector as their skin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340417940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jb33pbb73nuyy4d6ar52,task_description,declined
+VisualEditor: Nice error message for users without JavaScript,VE already gracefully degrades. It simply doesn't appear. I don't think there's anything more we should do at this point.,1345671293,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,This might be a partial duplicate of bug 38154,1345668931,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,"If you don't have JavaScript, then nothing will happen at all - there's no need for a ""nice error message"".
+
+And even if there was, you would do what? Implement something in PHP that detects if JavaScript is enabled on the client and then output a custom page, just for that user, that tells them they can't use VisualEditor because they don't have JavaScript enabled? So - that part of this bug is useless (sorry to be snarky, just having fun)
+
+As for other skins - VisualEditor skin integration is something we are still working on. We want it to be skin-independent, and soon it will be, but we have to make an API for this, and in the mean time we are just hacking in support for a couple skins. That part of the bug is valid - maybe we should rename this to ""VisualEditor lacks skin integration API"".",1345659493,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,"(In reply to comment #1)
+> What currently locks things into Vector skin? This shouldn't be skin-dependent,
+> in theory.
+
+I split the lack of support for other skins out to bug 38154.
+
+Changing this bug's summary from ""VisualEditor: Nice error messages for no-JS/no-Vector users"" to ""VisualEditor: Nice error message for users without JavaScript"". VisualEditor isn't going to be Vector-only, so there's no reason to work on an error message for that.",1341350822,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+VisualEditor: Nice error message for users without JavaScript,"What currently locks things into Vector skin? This shouldn't be skin-dependent, in theory.",1340468013,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-jb33pbb73nuyy4d6ar52,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,"Create some text - e.g. ""Expe dit ious"". Set the first seven characters as bold, and the last seven as italics. Round-trip.
+
+Expected wikitext: '''Expe''dit'''''<nowiki></nowiki>''ious''
+
+Expected HTML: <strong>Expe<em>dit</em></strong><em>ious</em>
+
+Actual wikitext:'''Expe''dit'''''''ious''
+
+Actual HTML: <strong>Expe<em>dit''</em></strong>ious
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340397840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_description,resolved
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,Patch committed in https://gerrit.wikimedia.org/r/37985.,1355186279,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,"Confirmed that the HTML send from VE to Parsoid is:
+
+""<p data-parsoid=""{&quot;dsr&quot;:[0,25]}""><b>Expe<i>dit</i></b><i>ious</i></p>""
+
+But that behaviour by Parsoid is as before. Assigning there.",1353121539,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,"Please try to reproduce again, if it's still broken, move it into Parsoid.",1353115094,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,Pushing to next milestone as they did not make it to master by yesterday.,1352832079,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>,Mass-moving items into VisualEditor product,1340402753,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pax76pmwwhkfmzx3qyu2,task_subcomment,NA
+VisualEditor: Handle edit conflicts,"From
+https://www.mediawiki.org/w/index.php?title=Visual_editor/Feedback&oldid=553398#Are_there_edit_conflicts.3F
+----
+I've removed content[1] from previous edits but got no warning about that.
+:Yes, we discovered this during deployment. A priority right away, certainly!
+[1] https://www.mediawiki.org/w/index.php?diff=next&oldid=552684
+----
+
+From
+https://www.mediawiki.org/w/index.php?title=Visual_editor/Feedback&oldid=553398#mid-air_collisions_are_not_detected_.28currently.29
+----
+I ""lost"" my edits due to a mid-air collision. Currently there appears to be no mechanism to detect if someone edits a text which you opened and changed and saved before... I thought we have edit tokens
+----
+
+From
+https://www.mediawiki.org/wiki/Thread:VisualEditor_talk:Welcome/Some_issues
+----
+It looks like the editor disables edit conflict handling. As I appear to have ended up overwriting an other user's edit.
+----
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker
+**URL**: https://www.mediawiki.org/w/index.php?diff=next&oldid=552684",1340368080,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-evnmq44e74m2oihqgr55,task_description,resolved
+VisualEditor: Handle edit conflicts,This is resolved in I002c5aa23704c1c46ef46fa1970a4254614b9eb1 but could be improved as per bug 42522,1354147235,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-evnmq44e74m2oihqgr55,task_subcomment,NA
+VisualEditor: Handle edit conflicts,"Sorry, I should have modified; this is a blocker to deployment in December, but is mostly a transient artefact of the (temporary) integration we're using for MWwiki deployment. The deployments to 'real' wikis from December onwards will be different, and this will not be an issue in the same way.
+
+Thanks for the reminder.",1350932595,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-evnmq44e74m2oihqgr55,task_subcomment,NA
+VisualEditor: Handle edit conflicts,Roan / James: As highest priority was set for this report four months ago I wonder if there's been any progress / work to follow? If not this should probably have a lower priority set.,1350930363,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-evnmq44e74m2oihqgr55,task_subcomment,NA
+VisualEditor: Handle edit conflicts,Mass-moving items into VisualEditor product,1340402765,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-evnmq44e74m2oihqgr55,task_subcomment,NA
+VisualEditor: Unable to edit an old revision,"On https://www.mediawiki.org/w/index.php?title=VisualEditor:Welcome&oldid=551728 I click ""edit"", then I'm editing the current version of text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340342220,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-yuwu5opgb5rp2g46lbs3,task_description,resolved
+VisualEditor: Unable to edit an old revision,Resolved in I9e957e6f5bc7920093481ffe3c33e299f87ce50a,1345748642,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-yuwu5opgb5rp2g46lbs3,task_subcomment,NA
+VisualEditor: Unable to edit an old revision,"This is now fixed in Parsoid, please provide the oldid parameter for both GET (DOM retrieval) and POST (DOM -> Wikitext conversion).",1344283134,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-yuwu5opgb5rp2g46lbs3,task_subcomment,NA
+VisualEditor: Unable to edit an old revision,Mass-moving items into VisualEditor product,1340402754,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yuwu5opgb5rp2g46lbs3,task_subcomment,NA
+HTML/JS/XSS injection in visual editor (attribute sanitation on links),"Create a new link in the visual editor. Add this text as the link target (including quotes exactly):
+
+"" onmouseover=""alert(document.cookie)"" alt=
+
+When mousing over the link in the editor, you'll get an alert popup with cookie contents. Same occurs in the HTML serialization (""preview"").
+
+
+I notice that ve.Html.makeAttributeList() doesn't do any escaping. Changing it locally to escape the text before putting it into an attribute seems to help on the preview (HTML serialization) but not in the editor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://test.wikipedia.org/wiki/Special:VisualEditorSandbox",1328826240,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-lowef3zhz3so2jcgpngl,task_description,resolved
+HTML/JS/XSS injection in visual editor (attribute sanitation on links),Noting bugs closed in the 2012-10-15 release.,1351534215,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lowef3zhz3so2jcgpngl,task_subcomment,NA
+HTML/JS/XSS injection in visual editor (attribute sanitation on links),Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341875,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lowef3zhz3so2jcgpngl,task_subcomment,NA
+HTML/JS/XSS injection in visual editor (attribute sanitation on links),"This is a bug report against old code, but the new code had a similar issue. Now fixed with https://gerrit.wikimedia.org/r/#/c/12550/1",1340319728,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lowef3zhz3so2jcgpngl,task_subcomment,NA
+Narayam not working in contenteditable div,"Narayam not working in contenteditable div. Example for such a  page:  https://www.mediawiki.org/wiki/Special:WebFonts?uselang=ta
+
+Also has impact on visualeditor if contenteditable div is used, as discussed in Bug 33076
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**:   https://www.mediawiki.org/wiki/Special:WebFonts?uselang=ta",1328503560,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-arynstjhbybir4k6knmy,task_description,resolved
+Narayam not working in contenteditable div,https://gerrit.wikimedia.org/r/3731 has the patchset for this issue.,1332756638,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-arynstjhbybir4k6knmy,task_subcomment,NA
+Narayam not working in contenteditable div,"jquery.textselection.js will not work in contenteditable divs. The caretposition, selection range etc are bit different from input fields or textarea. I am looking into this bug",1328505036,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-arynstjhbybir4k6knmy,task_subcomment,NA
+Narayam not working in contenteditable div,"**junu.pv+public** wrote:
+
+I just tried with:
+
+$.narayam.addInputs( '#webfonts-preview-area' );
+
+It does not work.",1328504889,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-arynstjhbybir4k6knmy,task_subcomment,NA
+inArray's use of strict equals in es.ContentView.js may be inappropriate (FIX attached),"**Author:** `acocaracha`
+
+**Description:**
+I've noticed a problem with es.ContentView.js when implementing tex equation support.  When you click text outside an annotation and then click back into the annotation, the new content is determined to have a different type than the surrounding text.  I believe this is because inArray uses strict equals and really the only thing it should be comparing is the type key and I don't think that necessarily needs to be strict (although I guess it could be).
+
+Here is a copy of the old code: https://jalto.net/equationdb/VisualEditor_save/demo/
+
+And the new code: https://jalto.net/equationdb/VisualEditor_old/demo/
+
+Steps to reproduce in old code:
+1) Create an inline equation
+2) Click a different section of the text
+3) Click in the middle of the inline equation
+4) Type something
+
+The new code is working fine.  The commits are:
+
+https://github.com/jalto/VisualEditor/commit/5e544447e5d54b260f5c0333f4dc9da5f15124d7
+
+and
+
+https://github.com/jalto/VisualEditor/commit/0f5a139d24870f200070a95cd70539b04dc0ce33
+
+Thanks,
+
+John
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1326072600,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-x54eh7ootvdxv4yravzz,task_description,invalid
+inArray's use of strict equals in es.ContentView.js may be inappropriate (FIX attached),Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341829,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-x54eh7ootvdxv4yravzz,task_subcomment,NA
+inArray's use of strict equals in es.ContentView.js may be inappropriate (FIX attached),Fixed with new version of VE (code replaced).,1340400649,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-x54eh7ootvdxv4yravzz,task_subcomment,NA
+inArray's use of strict equals in es.ContentView.js may be inappropriate (FIX attached),"**acocaracha** wrote:
+
+Rereading this I should have mentioned I'm new to javascript and in general a bit rusty in programming.  Here is a new commit to fix some of the mistakes I made in the previous ones.  I've done more testing and I think this actually is working now.
+
+https://github.com/jalto/VisualEditor/commit/f9b3cd519420df518c4d0189c32c36ae77a908c6
+
+Again you can see the working copy at https://jalto.net/equationdb/VisualEditor_old/demo/ .  The reason for the old is that I plan to made future changes and I wanted to keep a static copy.",1326303680,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-x54eh7ootvdxv4yravzz,task_subcomment,NA
+MediaWiki Vagrant broken,"I am following [[ https://www.mediawiki.org/wiki/MediaWiki-Vagrant#Quick_start | quick start ]] instructions on a Mac.
+
+```
+$ sw_vers -productVersion
+10.9.5
+```
+
+```
+$ git --version
+git version 2.1.3
+```
+
+```
+$ vboxmanage --version
+4.3.18r96516
+```
+
+```
+$ vagrant -v
+Vagrant 1.6.5
+```
+
+```
+$ git clone ssh://Zfilipin@gerrit.wikimedia.org:29418/mediawiki/vagrant
+Cloning into 'vagrant'...
+remote: Counting objects: 1015, done
+remote: Finding sources: 100% (390/390)
+remote: Getting sizes: 100% (259/259)
+remote: Compressing objects: 100% (127427/127427)
+remote: Total 7887 (delta 94), reused 7780 (delta 91)
+Receiving objects: 100% (7887/7887), 1.88 MiB | 379.00 KiB/s, done.
+Resolving deltas: 100% (3831/3831), done.
+Checking connectivity... done.
+```
+
+```
+$ cd vagrant/
+```
+
+```
+$ git submodule update --init --recursive
+Submodule 'puppet/modules/cdh' (https://gerrit.wikimedia.org/r/operations/puppet/cdh) registered for path 'puppet/modules/cdh'
+Submodule 'puppet/modules/mariadb' (https://gerrit.wikimedia.org/r/operations/puppet/mariadb) registered for path 'puppet/modules/mariadb'
+Submodule 'puppet/modules/nginx' (https://gerrit.wikimedia.org/r/operations/puppet/nginx) registered for path 'puppet/modules/nginx'
+Submodule 'puppet/modules/wikimetrics' (https://gerrit.wikimedia.org/r/operations/puppet/wikimetrics) registered for path 'puppet/modules/wikimetrics'
+Cloning into 'puppet/modules/cdh'...
+remote: Counting objects: 92, done
+remote: Finding sources: 100% (5/5)
+remote: Getting sizes: 100% (4/4)
+remote: Compressing objects: 100% (5690/5690)
+remote: Total 1292 (delta 0), reused 1288 (delta 0)
+Receiving objects: 100% (1292/1292), 250.13 KiB | 171.00 KiB/s, done.
+Resolving deltas: 100% (677/677), done.
+Checking connectivity... done.
+Submodule path 'puppet/modules/cdh': checked out '65335f7d027c635065966a15a7b4467c1ce311b5'
+Cloning into 'puppet/modules/mariadb'...
+remote: Counting objects: 26, done
+remote: Finding sources: 100% (18/18)
+remote: Getting sizes: 100% (8/8)
+remote: Compressing objects: 100% (4224/4224)
+remote: Total 70 (delta 6), reused 66 (delta 6)
+Unpacking objects: 100% (70/70), done.
+Checking connectivity... done.
+Submodule path 'puppet/modules/mariadb': checked out 'b5690999702552cc7fea48b2206f4bb92191d8ca'
+Cloning into 'puppet/modules/nginx'...
+remote: Total 61 (delta 0), reused 61 (delta 0)
+Unpacking objects: 100% (61/61), done.
+Checking connectivity... done.
+Submodule path 'puppet/modules/nginx': checked out '10a1e925fa707654102f39092b46a64c61710614'
+Cloning into 'puppet/modules/wikimetrics'...
+remote: Counting objects: 40, done
+remote: Finding sources: 100% (19/19)
+remote: Getting sizes: 100% (12/12)
+remote: Compressing objects: 100% (23171/23171)
+remote: Total 263 (delta 4), reused 253 (delta 4)
+Receiving objects: 100% (263/263), 57.59 KiB | 0 bytes/s, done.
+Resolving deltas: 100% (118/118), done.
+Checking connectivity... done.
+Submodule path 'puppet/modules/wikimetrics': checked out '5f416bbce4188914f48a044a8df09f1c34b07183'
+```
+
+```
+$ ./setup.sh
+Plugin vagrant-vbguest is already installed
+Installing plugin mediawiki-vagrant-0.2.1.gem
+- Installing the 'mediawiki-vagrant-0.2.1.gem' plugin. This can take a few minutes...
+- Installed the plugin 'mediawiki-vagrant (0.2.1)'!
+Your git/Gerrit username
+Enter 'anonymous' for anonymous access, leave blank to manage it yourself
+git_user: Zfilipin
+
+
+You're all set! Simply run `vagrant up` to boot your new environment.
+```
+
+```
+$ vagrant roles list
+Available roles:
+
+  accountinfo                gwtoolset                  popups                  
+  analytics                  hadoop                     proofreadpage           
+  antispam                   hive                       renameuser              
+  antispoof                  https                      scholarships            
+  apisandbox                 hue                        scribunto               
+  apparmor                   iegreview                  securepoll              
+  babel                      imagemetrics               simple_miser            
+  betafeatures               interwiki                  simple_performant       
+  categorytree               jsduck                     sitematrix              
+  centralauth                jsonconfig                 smtplog                 
+  centralnotice              labledsectiontransclusion   svg                     
+  chromium                   mantle                     templatedata            
+  cirrussearch               massmessage                textextracts            
+  cite                       math                       thumb_on_404            
+  cldr                       mathoid                    timedmediahandler       
+  codeeditor                 mathsearch                 translate               
+  cologneblue                memcached                  uls                     
+  commons                    mleb                       uploadwizard            
+  commonsmetadata            mobileapp                  urlshortener            
+  confirmedit                mobilefrontend             usermerge               
+  doublewiki                 modern                     vectorbeta              
+  echo                       molhandler                 visualeditor            
+  education                  monobook                   warnings_as_errors      
+  elk                        multimedia                 wikidata                
+  eventlogging               multimediaviewer           wikidiff2               
+  featuredfeeds              navigationtiming           wikieditor              
+  flow                       newusermessage             wikigrok                
+  fss                        nuke                       wikihiero               
+  fundraising                oauth                      wikilove                
+  gadgets                    oozie                      wikimediaevents         
+  gadgets2                   pagedtiffhandler           wikimediaincubator      
+  geodata                    pageimages                 wikimediamessages       
+  geshi                      pagetriage                 wikimetrics             
+  gettingstarted             parserfunctions            wikitech                
+  globalcssjs                parsoid                    xhprof                  
+  globaluserpage             pdfhandler                 zend                    
+  graph                      phptags                    zero                    
+  guidedtour                 poem                                               
+
+Roles marked with '*' are enabled.
+Note that roles enabled by dependency are not marked.
+Use `vagrant roles enable` & `vagrant roles disable` to customize.
+```
+",1416497151,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-faneqy7veketsdzp7dgx,task_description,invalid
+MediaWiki Vagrant broken,`vagrant up` worked fine when I deleted //everything// and started with an empty repository.,1416519382,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-faneqy7veketsdzp7dgx,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"Write a Parsoid backend for VirtualRestService, and replace VisualEditor's and Flow's hacks with that. Incorporate the cookie forwarding hacks from VE as well.
+
+See https://www.mediawiki.org/wiki/Requests_for_comment/PHP_Virtual_REST_Service and https://github.com/wikimedia/mediawiki/tree/master/includes/libs/virtualrest
+
+This would also be a good opportunity to clean up the way the Parsoid URL (and whether it's available) is configured in mediawiki-config
+
+See also: T74988",1415656386,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_description,resolved
+Use PHP Virtual REST Service to access Parsoid,"Change 181011 merged by jenkins-bot:
+Use ParsoidVirtualRESTService
+
+[[https://gerrit.wikimedia.org/r/181011]]",1420595467,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"Change 181706 merged by jenkins-bot:
+Make a VirtualRESTService class for Parsoid
+
+[[https://gerrit.wikimedia.org/r/181706]]",1420594186,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"Change 181706 had a related patch set uploaded (by Alex Monk):
+Make a VirtualRESTService class for Parsoid
+
+[[https://gerrit.wikimedia.org/r/181706]]
+
+#patch-for-review",1419380807,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"@krenair: Ahh, great news! @aaron: Thank you! ",1419022316,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,">>! In T1218#935534, @Krenair wrote:
+> I ran into issues with the way I was trying to use VirtualRESTService. My onResponses function was not getting called. Aaron said ""seems like there should be a $execReqsByService for the second loop to over so onReponse is called for non-replaced requests too"" (referring to code in VirtualRESTServiceClient::runMulti)
+
+We fixed the issue I was running into in https://gerrit.wikimedia.org/r/181121, @Aaron made https://gerrit.wikimedia.org/r/181119 to fix the issue we found last night.",1419021688,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"Change 181011 had a related patch set uploaded (by Alex Monk):
+Make a VirtualRESTService class for Parsoid, and use it
+
+[[https://gerrit.wikimedia.org/r/181011]]
+
+#patch-for-review",1419020274,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"I ran into issues with the way I was trying to use VirtualRESTService. My onResponses function was not getting called. Aaron said ""seems like there should be a $execReqsByService for the second loop to over so onReponse is called for non-replaced requests too"" (referring to code in VirtualRESTServiceClient::runMulti)",1418956514,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"It might be nice to model the internal interface somewhat similar to the way the RESTBase interface will look like:
+
+- `GET /v1/local/page/Foo/html/123456` -- HTML for page Foo at revision 123456
+- `GET /v1/local/page/Foo/data-mw/123456` -- data-mw for same
+- `POST /v1/local/convert/html/to/wikitext` -- convert html to wikitext, body tbd
+
+The `local` bit here could be shorthand for the local domain / wiki. Page titles are percent-encoded, so slashes are no problem.
+
+The cookie authentication business should be doable in the virtualrest backend handler for the parsoid end point, so that users don't need to deal with it. The backend is also the only place that needs to deal with actual host names etc from the config.",1418767738,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"It might be nice to model the internal interface somewhat similar to the way the RESTBase interface will look like:
+
+- `GET /v1/local/page/Foo/html/123456` -- HTML for page Foo at revision 123456
+- `GET /v1/local/page/Foo/data-mw/123456` -- data-mw for same
+- `POST /v1/local/convert/html/to/wikitext` -- convert html to wikitext, body tbd
+
+The `local` bit here could be shorthand for the local domain / wiki. Page titles are percent-encoded, so slashes are no problem.
+
+The cookie authentication business should be doable in the parsoid backend handler, so that users don't need to deal with it. The backend is also the only place that needs to deal with actual host names etc from the config.",1418767709,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+Use PHP Virtual REST Service to access Parsoid,"It might be nice to model the internal interface somewhat similar to the way the RESTBase interface will look like:
+
+- `GET /v1/local/page/Foo/html/123456` -- HTML for page Foo at revision 123456
+- `GET /v1/local/page/Foo/data-mw/123456` -- data-mw for same
+- `POST /v1/local/convert/html/to/wikitext` -- convert html to wikitext, body tbd
+
+The `local` bit here could be shorthand for the local domain / wiki. Page titles are percent-encoded, so slashes are no problem.",1418767609,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-q3ldi6tymbhxe2lm6rjl,task_subcomment,NA
+RfC: Allow styling in templates,"Currently the MediaWiki markup allows the inclusion of html elements with style attributes. Mixing layout with content causes various problems with reusability, maintainability and is not future proof. Already on the mobile version of MediaWiki problems are being seen with inline styles with how pages render on smaller screens which could be solved via css3 media queries, however these cannot be done in inline styles.
+
+It should be possible for templates to have associated stylesheets so that media queries can be applied where necessary. This is related to T37704.
+
+This RFC was proposed in 2013, discussed at two separate RFC meetings in 2014, and the status is unclear as of 2016-03-29.  More detailed status in the comments of this task
+
+Full writeup:
+[[ https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates | Allow styling in templates RfC ]].
+",1411645188,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-urypd4qwlje662u65qd3,task_description,resolved
+RfC: Allow styling in templates,"Nevertheless, it can be closed. The RfC was accepted and the feature implemented, reviewed and deployed; nothing actionable left in this task.",1519785718,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"To be less confusing, let's make this a sub-task instead.",1519319580,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Once {T133410} is done, then the exact functionality this task has requested will be in production. So, functionally, this task is a duplicate of that task, which is in process right now.",1519319400,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Once {T483} is done, then the exact functionality this task has requested will be in production. So, functionally, this task is a duplicate of that task, which is in process right now.",1519319385,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,,1505694925,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,,1505665883,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2316983, @MZMcBride wrote:
+> I'm hoping to find some time to play around with TemplateStyles this week. I'm curious whether features such as `url()` will be totally banned or only banned for non-Wikimedia domains. If we're going to disallow certain kinds of CSS (i.e., if we're only going to allow a subset of CSS), we'll want to make sure that the documentation and user interface both make this clear early and often to prevent headaches and frustration.
+
+I presume that anything banned inline is banned in TemplateStyles as well, as they are both 'public access' so to speak. What would be cool is to have some directive to import stylesheets from MediaWiki: space, where CSS is unrestricted.",1464003950,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2239190, @coren wrote:
+> Regardless, it is probably worthwhile to ask what the communities around templates think before we figure it out - at least on the bigger projects.  Ima do this this week.
+
+Is there any follow-up to this? I agree with Brion that restricting TemplateStyles to the Template namespace seems unnecessary. I'm pretty wary of global configuration variables, so if we can kill `$wgTemplateStylesNamespaces`, I think that's a win.
+
+>>! In T483#2293604, @GWicke wrote:
+>> It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?
+> 
+> The <style> tag in the header requires a page-global aggregation pass to collect styles, which would need to be implemented in the PHP parser, Parsoid, VisualEditor, and any other application composing wiki content (such as apps).
+> 
+> The inline stylesheet on the other hand keeps each template expansion self-contained, and avoids the complexity of global passes. It is both easier to implement, and easier to consume.
+
+I looked at T124966 a bit recently. The TemplateStyles extension is scheduled for a security review the week of May 30, according to T133408#2281285. Do you think your implementation concerns are hard blockers to deploying the TemplateStyles extension to Wikimedia wikis in the next few months?
+
+>>! In T483#2289858, @TheDJ wrote:
+> This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+
+It's funny, when I was skimming T133408 and starting to consider the various security concerns, one thought I had was ""thank God we're not trying to start with a CSS preprocessor, variables and functions and a whole embedded programming language would make this crazy difficult to review."" If we get really comfortable with being able to fully sanitize CSS output, I suppose adding a preprocessor wouldn't be totally insane. You'd still need to either do the processing client-side in JavaScript or do sandboxing server-side, the latter being similar to how we deal with embedded Lua, I believe.
+
+I don't think we need to block the deployment of TemplateStyles over preprocessor support, though. Support for a preprocessor would probably happen in this extension at around the same time or after it happens for MediaWiki core (cf. T56864).
+
+I'm hoping to find some time to play around with TemplateStyles this week. I'm curious whether features such as `url()` will be totally banned or only banned for non-Wikimedia domains. If we're going to disallow certain kinds of CSS (i.e., if we're only going to allow a subset of CSS), we'll want to make sure that the documentation and user interface both make this clear early and often to prevent headaches and frustration.",1463973740,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Hi @coren. We're looking at goal options for [[ https://www.mediawiki.org/wiki/Reading/Quarterly_planning/FY2016-2017/Q1#Reading_Infrastructure | Reading Infrastructure in Q1 FY 2016-2017]].
+
+The question arose: is the following something that's still relevant and that you were thinking to pursue?
+
+> Safety/security notes:
+> * need to parse/validate CSS rules for safety anyway -- avoid external refs, scary things
+>  * probably have to do a 'real' CSS parse rather than blacklisting a few keywords like we do on inline styles
+>  * doing this reliably may be the hardest part!
+
+@coren, if it's not on your list (yet still in scope), we were thinking this might be something Reading Infrastructure could work on starting July 2016. If it's already on your list, we would consider a different Reading Infrastructure goal for Q1 FY 2016-2017.
+
+CC @JKatzWMF, @tgr, @anomie",1463679811,PHID-USER-srhlj2447vmpmrfhqnfa,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2294327, @matmarex wrote:
+> We do care about IE 8, and even IE 6, as allowing users to view the site with correct styling is a basic core feature of MediaWiki, and therefore we should strive to support grade C browsers here. See https://www.mediawiki.org/wiki/Compatibility#Basic for details.
+
+I'm not sure about this requirement. Right now we are just talking about template styles. Would it be a travesty if these styles didn't apply but an IE6 browser could still use the content? If we were talking about disabling skin styles I would understand but an unstyled infobox is not the end of the world.
+",1463185950,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> We do care about IE 8, and even IE 6
+
+The read-only JS fix for IE8 would work in earlier IE versions as well.",1463180219,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@matmarex, do you expect a drastic increase in the size of the CSS associated with templates? If anything, being able to migrate some inline styles to rules should reduce CSS size somewhat, and compression would pick up repetitions & avoid a significant impact on download sizes. 
+
+Less styles in the <head> can also unblock rendering of above-fold content more quickly, which matters especially on mobile (see T124966).
+
+In any case, I would expect very frequently used transclusions like cite to still be predominantly styled globally. Changing some linked / global CSS is a lot cheaper than re-rendering all of Wikipedia to update a detail in citation styling.",1463180616,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@matmarex, do you expect a drastic increase in the size of the CSS associated with templates? If anything, being able to migrate some inline styles to rules should reduce CSS size somewhat, and compression would pick up repetitions & avoid a significant impact on download sizes. 
+
+Less styles in the <head> can also unblock rendering of above-fold content more quickly, which matters especially on mobile (see T124966).
+
+In any case, I would expect very frequently used transclusions like cite to still be predominantly styled globally. Changing some linked CSS is a lot cheaper than re-rendering all of Wikipedia to update a detail in citation styling.",1463180568,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@matmarex, do you expect a drastic increase in the size of the CSS associated with templates? If anything, being able to migrate some inline styles to rules should reduce HTML size somewhat, and compression would pick up repetitions & avoid a significant impact on download sizes. 
+
+Less styles in the <head> can also unblock rendering of above-fold content more quickly, which matters especially on mobile (see T124966).
+
+In any case, I would expect very frequently used transclusions like cite to still be predominantly styled globally. Changing some linked CSS is a lot cheaper than re-rendering all of Wikipedia to update a detail in citation styling.",1463180280,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@matmarex, do you expect a drastic increase in the size of the CSS associated with templates? If anything, being able to migrate some inline styles to rules should reduce HTML size somewhat, and compression would pick up repetitions & avoid a significant impact on download sizes. 
+
+Less styles in the <head> can also unblock rendering of above-fold content more quickly, which matters especially on mobile (see T124966).
+
+In any case, I would expect very frequently used transclusions like cite to still be predominantly styled globally. Changing some linked CSS is a lot cheaper than re-rendering all of Wikipedia to update a detail in citation styles.",1463179968,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@gwicke Are you suggesting that we duplicate the template stylesheet for every template invocation? That's crazy, and it would be literally the opposite of what this feature is being developed for.",1463179015,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"We do care about IE 8, and even IE 6, as allowing users to view the site with correct styling is a basic core feature of MediaWiki, and therefore we should strive to support grade C browsers here. See https://www.mediawiki.org/wiki/Compatibility#Basic for details.",1463178881,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> Just as side-note: Why would you base64 text? That might result in more data over the wire –after gzipping– like with SVGs laid out here.
+
+Good point! The following seems to work just as well:
+
+```lang=html
+<div id=""mw12345"">
+  <link rel=""stylesheet""
+    href=""data:text/css,#mw12345 { color: red }"">
+  This text is styled red.
+</div>
+```
+
+The main limitation with data URLs is [limited support in IE8](http://caniuse.com/#search=data). Only IE9+ supports stylesheets in data URLs. If we care about IE8, then we could create some JS for a read-only fix-up. VisualEditor does not support IE8, so there is no need to support the more complex editing scenarios.",1463178193,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2293454, @GWicke wrote:
+>             href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+Just as side-note: Why would you base64 text? That might result in more data over the wire –after gzipping– like with [[ https://css-tricks.com/probably-dont-base64-svg/ | SVGs laid out here ]].",1463175760,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2289858, @TheDJ wrote:
+> I was thinking a bit about variance, maintainability etc. And in the mobile-friendly content meeting we were also discussing: How do we document this so that editors know what they should do ?
+> 
+> Lets say we have a block like:
+> ```lang=css
+> @media print and (min-width: 480px)
+> ```
+> 
+> How do we make sure that not every single template has a different cutoff width and thus triggers a reflow? In every single language ?
+> 
+> This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+> 
+> This would make templatestyles a lot more maintainable and consistent, still give lot's of flexibility to editors and also allow us to make changes from the MediaWiki/Wikimedia side.
+
+:thumbsup: This seems very reasonable to me. From user experience _and_ developer perspective it makes sense to choose the media query breakpoints wisely and provide them in a central stylesheet. Less and future CSS offers this capability! ",1463175484,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?
+
+The <style> tag in the header requires a page-global aggregation pass to collect styles, which would need to be implemented in the PHP parser, Parsoid, VisualEditor, and any other application composing wiki content (such as apps).
+
+The inline stylesheet on the other hand keeps each template expansion self-contained, and avoids the complexity of global passes. It is both easier to implement, and easier to consume.",1463169597,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?
+
+The <style> tag in the header requires a page-global aggregation pass to collect styles, which would need to be implemented in the PHP parser, Parsoid, VisualEditor, and any other application composing wiki content (such as apps).
+
+The inline stylesheet on the other hand keeps each template expansion self-contained, and avoids the complexity of global passes.",1463169256,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?
+
+The <style> tag in the header requires a page-global aggregation pass to collect styles, which would need to be implemented in the PHP parser, Parsoid, VisualEditor, and any other application composing wiki content (such as apps).
+
+The inline stylesheet on the other hand keeps each template self-contained, and avoids the complexity of global passes.",1463169189,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2293454, @GWicke wrote:
+> All modern browsers support <link rel=""stylesheet""> in the body
+
+It's not immediately clear to me what the fundamental difference is between that and the current scheme (a <style> tag in the header)?",1463168868,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox, [JSFiddle](https://jsfiddle.net/xpL878ev/)):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in this example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we might be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463168516,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox, [JSFiddle](https://jsfiddle.net/xpL878ev/)):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in this example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we might be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463168014,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox, [JSFiddle](https://jsfiddle.net/xpL878ev/)):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in this example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463167963,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox, [JSFiddle](https://jsfiddle.net/xpL878ev/)):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in the example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463167905,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in the example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future, but for now inline stylesheets with selector prefixing should get us what we need while keeping page components self-contained.",1463167698,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prefixing CSS selectors as in the example: `#mw12345 { color: red }`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future.",1463167560,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,I213MTIzNDUgeyBjb2xvcjogcmVkIH0="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prepending all CSS selectors in the example with `#mw12345`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future.",1463167043,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome [is explicitly working on further improvements in how it handles rendering of such styles](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,Ym9keSB7IGNvbG9yOiByZWQgfQ=="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prepending all CSS selectors in the example with `#mw12345`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future.",1463166918,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"@coren: When implemented as proposed here, Parsoid and VisualEditor both would need to reimplement the same logic independently. Additionally, any application composing content on the client would need to implement similar aggregation passes, which would make our content a lot less modular than desirable.
+
+There are several alternatives that don't suffer from this issue:
+
+## Inline stylesheets
+
+All modern browsers [support <link rel=""stylesheet""> in the body](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). While this was not sanctioned by the HTML4 spec, [it has recently been allowed in the HTML5 spec](https://github.com/whatwg/html/commit/179983e9eb99efe417349a40ebb664bd11668ddd). Chrome is explicitly working on further improvements in how it handles rendering of such styles [1](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ZAPP8aTnyn0). Among other things, the technique is used [to speed up time to first paint](https://jakearchibald.com/2016/link-in-body/) by deferring the loading of below-fold CSS until it is needed.
+
+While this could be used to pull in external styles, that would add some network requests. However, the styles we are talking about here should be fairly small, so inlining them would be preferable. This can be done using data URLs like this (tested in Chrome and Firefox):
+
+```lang=html
+    <body>
+        <div id=""mw12345"">
+            <link rel=""stylesheet""
+            href=""data:text/css;base64,Ym9keSB7IGNvbG9yOiByZWQgfQ=="">
+            This text is styled red.
+        </div>
+    </body>
+```
+
+This solves the primary issue of avoiding global state, but still requires styles to be explicitly prefixed to enforce scoping, for example by prepending all CSS selectors in the example with `#mw12345`.
+
+## Shadow DOM
+
+The [Shadow DOM spec](https://www.w3.org/TR/shadow-dom/) is aiming to fully encapsulate styling and DOM behavior of components. It is pushed by Google & others as the successor to <style scoped>. In recent months the spec has been shaping up quickly, but I expect it to still take some time until implementations are consistent enough & polyfills have caught up.
+
+In summary, we should be able to leverage Shadow DOM for cleaner style isolation in the future.",1463166868,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2289895, @GWicke wrote:
+> Adding the parsing team, as this would introduce page-global state, and also needs to work in Parsoid and VE.
+
+I've been pondering on that issue for a bit; clearly there needs to be an API endpoint for parsoid to hit - but I'm not certain what data would be most useful to return; would the final ""merged"" stylesheet be apropriate?
+",1463162334,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Adding the parsing team, as this would introduce page-global state, and also needs to work in Parsoid and VE.",1463073496,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Adding the parsing team, as this would introduce page-global state, and also needs to be implemented in Parsoid and VE.",1463073450,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"I was thinking a bit about variance, maintainability etc. And in the mobile-friendly content meeting we were also discussing: How do we document this so that editors know what they should do ?
+
+Lets say we have a block like:
+```lang=css
+@media print and (min-width: 480px)
+```
+
+How do we make sure that not every single template has a different cutoff width and thus triggers a reflow? In every single language ?
+
+This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+
+This would make templatestyles a lot more maintainable and consistent, still give lot's of flexibility to editors and also allow us to make changes from the MediaWiki/Wikimedia side.",1463072821,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"I was thinking a bit about variance, maintainability etc. And in the mobile-friendly content meeting we were also discussing: How do we document this so that editors know what they should do ?
+
+Lets say we have a block like:
+```css
+@media print and (min-width: 480px)
+```
+
+How do we make sure that not every single template has a different cutoff width and thus triggers a reflow? In every single language ?
+
+This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+
+This would make templatestyles a lot more maintainable and consistent, still give lot's of flexibility to editors and also allow us to make changes from the MediaWiki/Wikimedia side.",1463072785,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"I was thinking a bit about variance, maintainability etc. And in the mobile-friendly content meeting we were also discussing: How do we document this so that editors know what they should do ?
+
+Lets say we have a block like:
+```
+@media print and (min-width: 480px)
+```
+
+How do we make sure that not every single template has a different cutoff width and thus triggers a reflow? In every single language ?
+
+This made me realize: We need to make this a less sheet and MediaWiki/Wikimedia should have a centralized less sheet with predefined variables, functions/mixins etc. We could properly document those variables and functions and use them in our examples. We could put complicated CSS magic in descriptively named functions/variables, so that people don't have to understand all the CSS details, they can just be ""in this situation i need to use this function"".
+
+This would make templatestyles a lot more maintainable and consistent, still give lot's of flexibility to editors and also allow us to make changes from the MediaWiki/Wikimedia side.",1463072677,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2232623, @brion wrote:
+> If volunteers are +2'ing config updates and deploying them, I'm impressed. :)
+
+Regardless, it is probably worthwhile to ask what the communities around templates think before we figure it out - at least on the bigger projects.  Ima do this this week.",1461674644,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"If volunteers are +2'ing config updates and deploying them, I'm impressed. :)",1461436854,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2232450, @brion wrote:
+> on communities to deal with the question, and on wmf releng to handle updating the setting.
+
+I don't know if you've been watching #wikimedia-site-requests lately but the credit for handling that process really should go to the volunteers involved.",1461436624,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"It seems like an unnecessary burden on users to figure out why it didn't work and ask their communities for permission to change, on communities to deal with the question, and on wmf releng to handle updating the setting.
+
+What downside is there to just having it always on everywhere?",1461430224,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2232314, @brion wrote:
+> Note that people do like to use templates outside the template NS, for user or project pages for instance. Not sure if we want to support that explicitly/implicitly/not at all, etc. :)
+
+It's supported via $wgTemplateStylesNamespaces; whether that is left to just Template: or not when that gets deployed to prod seems to me to be a decision best left to the individual communities.",1461429975,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Note that people do like to use templates outside the template NS, for user or project pages for instance. Not sure if we want to support that explicitly/implicitly/not at all, etc. :)
+",1461423840,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"With the latest rounds of merges, the TemplateStyles extension appears to be in a reasonable state and implements the major substantive part of this RfC as discussed in Jerusalem.
+
+An interesting side effect of the current implementation is that a `<templatestyles>` tag appearing on a page //not// appearing in the list of allowed namespaces will not - as designed - affect pages transcluding it but it **does** style //itself// regardless of namespace.
+
+I'm not sure that shouldn't simply be documented as a feature.  :-)",1461419944,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Change 283772 merged by jenkins-bot:
+Add unit tests for CSSParse and CSSRender
+
+[[https://gerrit.wikimedia.org/r/283772]]",1461183515,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2223326, @Edokter wrote:
+> I think scoping to `#mw-content-text` should be enough. Any tempate appearing outside actual content is usually protected anyway.
+
+I would tend to agree; let's not overcomplicate the first go at this and aim for an implementation that is simple to implement //and// describe: template styles allow styling of contents.
+
+I think there's a good case to be made that styling UI elements is outside the scope of this extension; it's a marginal use at best and should probably be left to some other mechanism (especially since fiddling with the UI is very skin-specific and depends a great deal on the actual interface in use).
+",1461168666,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,I think scoping to `#mw-content-text` should be enough. Any tempate appearing outside actual content is usually protected anyway.,1461158655,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Would it be safer to introduce this feature as only available on admin-protected templates?  Then we could relax that requirement gradually once the issues are better understood and have been prevented..?,1461120083,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2218236, @Edokter wrote:
+> Actually, plenty of templates can appear outside 'content' space, such as edit notices. Those should be able to be styled. The risk of clashing CSS classes is pretty low anyway.
+
+In addition to the desirability of avoiding clashes, there is also the issue that part of the objective of placing styling in templates is to allow non-administrator the ability to edit styles - which means that we need to protect most UI elements from accidental (or malicious) alteration.
+
+It might be worthwhile to consider alternatives by which UI elements can be styled in controlled contexts, but I think this is a good project for a future version.  :-)
+",1461119524,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2215393, @Entlinkt wrote:
+> It should probably be avoided that templates can leak styles into that area.
+
+Actually, plenty of templates can appear outside 'content' space, such as edit notices. Those should be able to be styled. The risk of clashing CSS classes is pretty low anyway.",1461079820,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2211010, @TheDJ wrote:
+> We have `#mw-content-text` that contains all generated output for wikitext pages, but more importantly the classes `mw-content-ltr` and `mw-content-rtl`.
+
+Please note that in diff views, `#mw-content-text` also contains the `table.diff` element with the actual diff, revert links etc. It should probably be avoided that templates can leak styles into that area.
+
+I don't know of any selector that precisely catches user-generated content. Currently, `#mw-content-text` is just an approximation.",1461009856,PHID-USER-4j6uu43bpl65dnji6462,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Change 283772 had a related patch set uploaded (by coren):
+Add unit tests for CSSParse and CSSRender
+
+[[https://gerrit.wikimedia.org/r/283772]]
+",1460823433,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2211010, @TheDJ wrote:
+> Right, found a quite important point... We are now scoping using:
+> `mw-body-content` it seems. But that is a skin specific class, amongst others not used by the mobile minerva skin.
+> 
+> We have `#mw-content-text` that contains all generated output for wikitext pages, but more importantly the classes `mw-content-ltr` and `mw-content-rtl`.
+
+Aha.  Good catch.  Fixing.",1460772104,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Right, found a quite important point... We are now scoping using:
+`mw-body-content` it seems. But that is a skin specific class, amongst others not used by the mobile minerva skin.
+
+We have `#mw-content-text` that contains all generated output for wikitext pages, but more importantly the classes `mw-content-ltr` and `mw-content-rtl`.",1460743734,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2210556, @Legoktm wrote:
+>>>! In T483#2209954, @TheDJ wrote:
+>> Tried [[ http://ts.wmflabs.org/w/index.php?title=Template%3AWide_image&type=revision&diff=124&oldid=121 | using wikimarkup inside the style block ]], but that doesn't seem to work (and scary if it would..)
+> 
+> What if you used `{{#tag:templatestyles}}` so the wikitext is processed? I'm not sure how the extension is storing the actual styles though.
+
+It's stored as a serialized parse tree of the rules; the processing would happen exactly once on save, then parsed as CSS and stored in a fixed format.
+",1460738047,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209954, @TheDJ wrote:
+> Tried [[ http://ts.wmflabs.org/w/index.php?title=Template%3AWide_image&type=revision&diff=124&oldid=121 | using wikimarkup inside the style block ]], but that doesn't seem to work (and scary if it would..)
+
+What if you used `{{#tag:templatestyles}}` so the wikitext is processed? I'm not sure how the extension is storing the actual styles though.",1460736262,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209954, @TheDJ wrote:
+> Tried [[ http://ts.wmflabs.org/w/index.php?title=Template%3AWide_image&type=revision&diff=124&oldid=121 | using wikimarkup inside the style block ]], but that doesn't seem to work (and scary if it would..)
+
+That wouldn't have worked even if the tag was parsed: the stylesheet is parsed on save and stored as a page property for use by transcluding pages, so it cannot differ from one transclusion to another.",1460736209,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209954, @TheDJ wrote:
+> Some first practical experiences:
+> 1: i quickly found a situation, where in lieu of inline styles, i'll have to use a unique (per parserrun) class or ID. we have no good options for this right now. For now, i'll keep using inline styles for those situations. (width specific to the image being transcluded)
+
+There isn't a good option for this that I can think of.  Certainly, ""new"" best practices would be to avoid such parametrization entirely whenever at all possible since they play poorly with window width and mobile in all cases.  I expect most cases can be reduced to a smaller set of limited options, though (say, ""auto, 75%, 100%"").
+
+At the very least, it then becomes possible to override such variation in a `@media` block with a `!important`; so the situation is ""less bad"" than it otherwise might have been.
+
+> 2: the style block should probably be inserted AFTER the <meta name=""ResourceLoaderDynamicStyles"" content=""""/>
+
+The point of insertion is actually picked by core (in `OutputPage::addInlineStyle()`); we'd need to check whether that's the best spot in all contexts.
+
+> 3: These style blocks will have to be exposed in the api, so that something like LivePreview can update them.
+> 4: The style block will need an identifying attribute, so that something like livepreview can replace it.
+
+I'm not familiar enough with LivePreview to evaluate what that entails.  I'll have to look into it.
+
+> 5: Every conditional styling option of a template will require it's own class (always included). For instance, even if I don't use the border option of  http://ts.wmflabs.org/w/index.php/Template:Wide_image, I will always have to include the .noborder styling class. This might be more bytes and more unused styling classes for uses of certain templates.
+
+I //expect// that's not a significant issue in practice; that duplication is probably offset by the fact that multiple inclusions of the same template cause the styles to be inlined only once and that using a class more than once within the same template removes the repetition of the inline style.
+
+That said, it's theoretically possible to omit classes that are not in fact used on the page - the selectors for every rule are known at the point of insertion.  That would, however, require non-trivial parsing of the document and is probably best left to after we have determined that there is an issue to fix.
+",1460736023,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209954, @TheDJ wrote:
+> Some first practical experiences:
+> 1: i quickly found a situation, where in lieu of inline styles, i'll have to use a unique (per parserrun) class or ID. we have no good options for this right now. For now, i'll keep using inline styles for those situations. (width specific to the image being transcluded)
+
+There isn't a good option for this that I can think of.  Certainly, ""new"" best practices would be to avoid such parametrization entirely whenever at all possible since they play poorly with window width and mobile in all cases.  I expect most cases can be reduced to a smaller set of limited options, though (say, ""auto, 75%, 100%"").
+
+At the very least, it then becomes possible to override such variation in a `@media` block with a `!important`; so the situation is ""less bad"" than it otherwise might have been.
+
+> 2: the style block should probably be inserted AFTER the <meta name=""ResourceLoaderDynamicStyles"" content=""""/>
+
+The point of insertion is actually picked by core (in `OutputPage::addInlineStyle()`); we'd need to check whether that's the best spot in all contexts.
+
+> 3: These style blocks will have to be exposed in the api, so that something like LivePreview can update them.
+> 4: The style block will need an identifying attribute, so that something like livepreview can replace it.
+
+I'm not familiar enough with LivePreview to evaluate what that entails.  I'll have to look into it.
+
+> 5: Every conditional styling option of a template will require it's own class (always included). For instance, even if I don't use the border option of  http://ts.wmflabs.org/w/index.php/Template:Wide_image, I will always have to include the .noborder styling class. This might be more bytes and more unused styling classes for uses of certain templates.
+
+I ''expect'' that's not a significant issue in practice; that duplication is probably offset by the fact that multiple inclusions of the same template cause the styles to be inlined only once and that using a class more than once within the same template removes the repetition of the inline style.
+
+That said, it's theoretically possible to omit classes that are not in fact used on the page - the selectors for every rule are known at the point of insertion.  That would, however, require non-trivial parsing of the document and is probably best left to after we have determined that there is an issue to fix.
+",1460735945,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Some first practical experiences:
+1: i quickly found a situation, where in lieu of inline styles, i'll have to use a unique (per parserrun) class or ID. we have no good options for this right now. For now, i'll keep using inline styles for those situations. (width specific to the image being transcluded)
+2: the style block should probably be inserted AFTER the <meta name=""ResourceLoaderDynamicStyles"" content=""""/>
+3: These style blocks will have to be exposed in the api, so that something like LivePreview can update them.
+4: The style block will need an identifying attribute, so that something like livepreview can replace it.
+5: Every conditional styling option of a template will require it's own class (always included). For instance, even if I don't use the border option of  http://ts.wmflabs.org/w/index.php/Template:Wide_image, I will always have to include the .noborder styling class. This might be more bytes and more unused styling classes for uses of certain templates. Not really sure what to do about that... Tried [[ http://ts.wmflabs.org/w/index.php?title=Template%3AWide_image&type=revision&diff=124&oldid=121 | using wikimarkup inside the style block ]], but that doesn't seem to work (and scary if it would..)",1460729380,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Done.  I added ParserFunctions and Scribunto, and reimported Template:Wide image recursively to make sure it worked.",1460726048,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2209633, @TheDJ wrote:
+> Coren, can you add parserfunctions extension to your experimental wiki ?
+> i'd like to test a few actual en.wiki templates, and almost all of those need parserfunctions and/or scribunto
+
+Yeah, those and a couple others really - will do so shortly.",1460724697,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Coren, can you add parserfunctions extension to your experimental wiki ?
+i'd like to test a few actual en.wiki templates, and almost all of those need parserfunctions and/or scribunto",1460724423,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#2207021, @coren wrote:
+> The current WIP can be played with [[ http://ts.wmflabs.org/w/index.php/Main_Page | on an experimental wiki ]].  The main page is an example of a transclusion of a style template.
+
+[[http://ts.wmflabs.org/w/index.php?title=Template:Boilerplate&action=edit|Direct link to the styled template]]",1460652612,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,The current WIP can be played with [[ http://ts.wmflabs.org/w/index.php/Main_Page | on an experimental wiki ]].  The main page is an example of a transclusion of a style template.,1460645012,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Change 282155 merged by jenkins-bot:
+TemplateStyles extension prototype
+
+[[https://gerrit.wikimedia.org/r/282155]]",1460227082,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Change 282155 had a related patch set uploaded (by coren):
+[WIP] TemplateStyles extension prototype
+
+[[https://gerrit.wikimedia.org/r/282155]]
+",1460065630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Current plan summary based on the etherpad notes (in case they get lost):
+* use mechanism similar to TemplateData
+ * extension tag to encapsulate a CSS chunk directly in the template's wikitext
+ * note supporting media queries is super important for mobile & narrow-window views!
+ * use save hook to validate & store the style data
+* have parser pull up the style data of all used templates when rendering out a page
+ * build them into a <style> tag (this keeps style & html versions consistent within parsercache, and is simpler than trying to load lots of deps via ResourceLoader)
+
+That much should be pretty easy to prototype.
+
+Encapsulation notes:
+* one idea is to do the template styles only on properly balanced templates
+ * encourage people to 'do the right thing' with templates ;)
+* this allows wrapping the template in a (custom?) html element which can be added to the prefix of any CSS rules in the template
+ * should prevent leakage of defined rules outside the template
+ * which should also prevent conflicts in styles and class/id names between templates
+ * but requires parsing the CSS well enough to be able to reliably prefix all selectors
+
+Safety/security notes:
+* need to parse/validate CSS rules for safety anyway -- avoid external refs, scary things
+ * probably have to do a 'real' CSS parse rather than blacklisting a few keywords like we do on inline styles
+ * doing this reliably may be the hardest part!
+
+Editor helper tools:
+ * jon is interested in a helper tool to look for suspicious inline styles and warn users on edit that their page or template is likely to render badly on mobile/narrow window
+ * if we're parsing & storing metadata on the css styles, we can build a tool to look for common/duplicated styles and suggest moving truly common ones to MediaWiki:Common.css
+
+Open questions:
+* what about style libraries to be shared between templates? (maybe not a high prio; truly common styles can go in existing MediaWiki:Common.css)",1459685891,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"After some architecture discussion with @Brion and @jdlrobson, we came up with a fairly good plan for which I'm going to do a first prototypical implementation.
+
+The summary: styles are to be added inline to the template (with a mechanism comparable to that of templatedata and/or outright coopting that mechanism), combined at page rendering time, and placed inline with the page.  We avoid redundancy by eschewing true scoped styles, opting to make them global instead.
+
+//Faux//-scoping is provided for balanced templates by making certain they are encapsulated and given a class that is then used as a selector for the template's declared classes; this would ideally rely on T114445 to avoid duplicating effort.",1459685613,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Notes from @Jdlrobson @coren & @brion at Wikimedia Hackathon 2016: https://etherpad.wikimedia.org/p/WikiHack16_TemplateStyles
+
+@coren is interested in doing some prototyping work.
+",1459685142,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,">>! In T483#1884696, @Jdlrobson wrote:
+> Any update on this?
+
+This was moved into the ""Approved, but not resourced"" column in T483#1073658 (@daniel, 2015-02-27).  The answer to ""what happens next?"" when an RFC reaches that state is admittedly unclear; #ArchCom doesn't have the ability to assign developers to things, and should be very stingy about volunteering their own time.  There are some old action items documented @brion and @tstarling from the RFC meeting on 2014-10-15, but that doesn't seem relevant today.
+
+Given that the  [[ https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates | Allow styling in templates RfC ]] writeup on mw.org states that the author is ""Jon Robson who no longer has time to move this forward"" and the state marked there is ""stalled"", it's tempting to treat the RFC as abandoned, were it not for the frequent mentions this task gets, and @Jdlrobson adding this as a blocker to resolving @ori's bug report T130846.
+
+Looking at the history on the  [[ https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates | Allow styling in templates RfC ]] page, it would seem that this needs a new driver who is probably not @brion.  For tasks in the #ArchCom-RFC, we have been provisionally using (misusing?) the assignment field as where we assign the shepherd.  I think it potentially makes sense for @brion to remain the shepherd, but someone else needs to be the driver for this.
+
+Any volunteers to drive this? 
+",1459319067,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Any update on this?,1450282910,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"From https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-10-15-21.02.html
+
+* ACTION: tim interested in helping with the css parsing, may port some tools from node if nothing good already in php (brion, 21:46:56)
+* ACTION: accepted styling in templates, work & final details to be done by brion & tim (brion, 21:50:58)",1425052965,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Found logs that say APPROVED here: https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-10-15-21.02.html,1425052920,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"Seems to be stalled after an inconclusive discussion on 2014-03-26: https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-26
+
+** ''LINK:'' https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates  (sumanah, 21:11:10)
+** ''LINK:'' https://www.mediawiki.org/wiki/Requests_for_comment/Deprecating_inline_styles was an older RfC that Jon abandoned in favour of ""Allow styling in templates""  (sumanah, 21:11:10)
+** ''LINK:'' https://www.mediawiki.org/wiki/Talk:Architecture_Summit_2014/UI_styling#Allow_styling_in_templates We discussed this topic during the Architecture Summit in January  (sumanah, 21:11:10)
+** the next steps from January said - Jon & friends would lock down some details, code up a prototype/working beta with some sample templates, and so on by about the end of March.  (sumanah, 21:11:31)
+** Jon wants: ""some agreement on the way forward and someone with time to write the code to get this kicked off :)  i've been a bit swamped recently""  (sumanah, 21:12:00)
+** (we were supposed to talk about this in February https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-02-27 but ran out of time in that meeting)  (sumanah, 21:12:54)
+** ''LINK:'' https://www.mediawiki.org/wiki/Requests_for_comment/Associated_namespaces  (marktraceur, 21:14:15)
+** Jon looked at supporting style tags rather than separate wiki pages for styles, per discussion at the summit, and it was nasty and required messing with the parser.  https://gist.github.com/anonymous/9262427  (sumanah, 21:23:36)
+** discussion of having a separate Template:Foo.css page; see https://gerrit.wikimedia.org/r/68123  (sumanah, 21:23:36)
+** discussion of sanitizing/making secure CSS and <style> content, and performance implications of having a separate CSS bundle  (sumanah, 21:23:36)
+** ''IDEA:'' could we have ResourceLoader bundle it?  (sumanah, 21:23:36)
+** ''HELP:'' Jon needs help writing the code to get this kicked off  (sumanah, 21:30:20)
+** <YuviPanda> However we do this, this would definitely need ops buy in of some sort (at least notifications)  (sumanah, 21:33:01)
+",1425052262,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Also related: {T37704}.,1418413724,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,Related: {T52644}.,1418413421,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+RfC: Allow styling in templates,"> Brion interested in this
+> will update the RfC w/ implementation plans and schedule it for next weekish
+
+https://www.mediawiki.org/wiki/Architecture_committee/2014-10-08#RFCs_to_triage",1412804918,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-urypd4qwlje662u65qd3,task_subcomment,NA
+Document a process to request new projects,"On Day 1 we will need a process to request a new project, because plain users will not be able to create projects themselves.
+
+In fact, we need such progress already now in this Labs instance. We can define the process as we document it, and fine tune it as we see fit, real request after real request.
+
+I have started a draft at https://www.mediawiki.org/wiki/Phabricator/Help. @aklapper & co, feel free fine tuning it while satisfying the current requests for Labs.",1405443204,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_description,resolved
+Document a process to request new projects,//importing issue status//,1410486132,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-08-04 16:42:20 (UTC)`
+
+I'm resolving this task because we have a process in place:
+
+https://www.mediawiki.org/wiki/Phabricator/Help#Requesting_a_new_project
+
+We will mature the process as we define T68, and with the experience acquired.",1410486132,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**aklapper** wrote on `2014-07-28 19:32:47 (UTC)`
+
+Heja, let's please move the naming scheme discussion to T68 where we have more target audience (PMs). I will comment on concerns and thoughts brought up here in T68.",1410486132,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-28 14:50:42 (UTC)`
+
+@Rush, thank you for the long explanation but I have to say that I still disagree.
+
+Your argument is based on the assumption that people memorize and type entire URLs. This is why having ""sane"" URLs is key for you, and the rest needs to be adapted to this assumption, sacrificing the use of natural language in the UI.
+
+I believe for most users the UI goes first, and using natural language there makes them happier. Phabricator, web links, search engines, and users' browsers will deal with the full URLs. This is what happens nowadays in most web services, including Wikipedia and our developer infrastructure sites.
+
+Summarizing my opinion:
+
+* Using original project names in Phabricator makes them easier to type and find.
+* Project names are used as simple tags, except in the case of explicit subprojects of an existing project à la ""Product - Component"". No ""MediaWiki-Extensions-Etc"".
+* Since projects are proper nouns, by default they use the regular Title Case. Other uses of case are allowed only when the original project name uses them (e.g. GoogleLogin, VisualEditor, MySQL, FOSDEM)
+
+> mediawiki-extensions-googlelogin ftw
+
+Two reasons why this is not a good solution:
+
+# If you search for ""googlelogin"" or any substring, you will not find this project in the search engine or via typeahead in a new task. If the project has separate words like ""MediaWiki Extensions GoogleLogin"" then yes, starting to type ""Goo..."" the project will appear and the user can just select it. Test this by typing ""Dashes"" or ""dashes"". ""[[ http://fab.wmflabs.org/project/view/61/ | test-project-dashes ]]"" will never show up, while ""[[ http://fab.wmflabs.org/project/view/62/ | Test Project Dashes Searchable ]]"" will as soon as you type ""D"" or ""d"". If all what users know is the project name, they will find it only with separate words.
+# Considering the importance of typeahead in Phabricator, we want to avoid having hundreds of entries starting with ""mediawiki..."" or ""wikimedia..."". Users with a problem in ""GoogleLogin"" will come and start typing that string directly. This is not Git/Gerrit or Bugzilla, we don't need to reflect any tree structure. Phabricator is about tags. What is important about ""GoogleLogin"" is that users can find it or reference it easily. Therefore the best is to use the name as is.",1410486131,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Florian** wrote on `2014-07-28 12:02:33 (UTC)`
+
+@Rush: So you would suggest to use always lowercase project namens? But the extension/project itself can still be named ""as it is"" with CamelCase and/or whitespaces?",1410486131,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Rush** wrote on `2014-07-25 18:38:35 (UTC)`
+
+Sorry, my lack of response to that wasn't meant to be opaque or rude, I've been trying to figure out the best way to make the argument.
+
+I've been here before and the culmination of my thinking boils down to 'oh no not again!', but that's a really difficult thing to communicate.  I'm hoping I can at least relate challenges I see here from previous experience.
+
+===The case of tags===
+
+This exists: http://fab.wmflabs.org/project/view/40/
+
+Only nobody remembers project 40, everyone remembers the name shown at the top as `Trusted User Tool`, the most common way to reference a project when projects reach a certain scale, especially in Phabricator, is via the `/tag/name` mechanism.  Only that doesn't work out for this name. 
+
+This doesn't exist: http://fab.wmflabs.org/tag/Trusted%20User%20Tool/
+This doesn't exist: http://fab.wmflabs.org/tag/Trusted_User_Tool/
+
+This does exist: http://fab.wmflabs.org/tag/trusted_user_tool/
+
+Technically per [spec](http://en.wikipedia.org/wiki/URL_encoding) the above should work out the spacing UTF8 as %20 and that should be fine, but as anyone who has done url encoding is aware users do not understand URL encoding.  Thus the human option of replacing %20 control character with '_'.  Which I think is the sanest option, and we should mimic it, to do otherwise is to intentionally create a disparity in how a project is referenced.
+
+If we don't follow the Phabricator standard we now have two names for one thing.  This inconsistency means we end up with a page in the wiki that boils down to ""how to translate your project name into the tag name"".  Because it isn't precisely URL spec, even if you ignore the case sensitivity issues.
+
+Versus:
+
+This exists: http://fab.wmflabs.org/project/view/47/
+This exists: http://fab.wmflabs.org/tag/operations-core/
+
+===On readability and flat namespacing===
+
+Taking the case of https://www.mediawiki.org/wiki/Extension:GoogleLogin
+
+Because the project namespace is flat we have to infer hierarchy (sub grouping) with a mostly sane single string naming scheme
+
+Bugzilla:
+
+    Mediawiki
+      -> Extensions
+         -> GoogleLogin
+
+Phabricator:
+
+    mediawiki-extensions-googlelogin
+
+Or
+
+    Mediawiki-Extensions-GoogleLogin
+
+We are representing the same hierarchy and maintaining namespace isolation consistency with this paradigm.  googlelogin is ambiguous while mediawiki-extensions-googlelogin is not.
+
+Taking this camel case idea down the line it becomes things like:
+
+ResearchAndReview-GrantProposals-Ready
+
+versus encouraging lower case and readability:
+
+research-grantmaking
+
+We are labeling things more than we are naming them.  Eventually it becomes necessary to follow proper noun usage with things like: GoogleReady-OAuth-LoginProtocol.  The limitations of flat namespacing mean we end up with 10, 20, 30 and up character strings for which the CAmELCase usecase is not more readable except in the simplest of cases.  
+
+Once we start doing camel case it will be an issue of having to respect all proper nouns which make strings less readable, and going back because we realize it's adding far more problems than it creates readability it will be impossible.  The intangible problem of why some `Projects` are now `projects` is essentially very difficult culturally.  External references all end up inconsistent if we try to change this later.
+
+===URL's and Case===
+
+So when creating a project name we are really creating a URL reference for a bucket of objects.  This isn't the same with other things within the Phabricator landscape.  We don't try to hit phab.com/theawesometicket or phab.com/myawesomelegalagreement.  We do reference phab.com/tag/project-foo.  When you get right down to [it](http://tools.ietf.org/html/rfc4343) case sensitivity and URL's is confusing.  Technically, case should be ignored in the FQDN.  Google.com and GOOGLE.com are equivalent, but should be respected in the trail.  GOOGLE.com/foo and google.com/Foo are distinct.  Even that falls apart though because different server implementations can handle those cases in different ways.  Even the w3 takes a pragmatic approach.  See http://www.w3.org/TR/WD-html40-970708/htmlweb.html and http://www.w3.org/tr/wd-html40-970708/htmlweb.html where rather than respecting the case sensitivity they just redirect, which is pretty much the sane approach for reference documentation like that I guess.  But demonstrates the weirdness.
+
+Shown out of love:
+
+yes: http://en.wikipedia.org/wiki/case_sensitivity
+yes: http://en.wikipedia.org/wiki/Case_sensitivity
+no: http://en.wikipedia.org/wiki/CASE_SENSITIVITY
+
+So projects are going to be directly referenced as URL's and URL's are finicky.  There are [characters](http://tools.ietf.org/html/rfc3986#section-2) that are OK to use as project names in the absolute sense -- it won't stop you, but are not valid in a URL
+
+I've been doing a lot of testing for how we can move the namespace from bugzilla to phabricator and it has only reinforced these ideas.
+
+Right now in bugzilla we have names that when translated look like: one-two-three/four
+
+This isn't a valid project reference, because it is not a valid URL.  That only works as phab.com/tag/one-two-three_four/
+
+If we allow characters in project names that are not valid in a URL we are going to make things much harder for us and users.
+
+===Referencing===
+
+Projects are also referenced in remarkup as well but this comes with its own inconsistencies. As an example you can refer to user @rush and project #operations-requests.  But if we allow non-standard URL characters such as spaces we end up with these cases:
+
+no : #Trusted User Tool
+yes: #Trusted_User_Tool
+yes: #trusted_user_tool
+
+Note the same happens for ampersand:
+
+project `foo_and_bar` is fine: `foo_and_bar`
+project `foo&bar` is *not* fine: `foo_bar`
+
+The way this is handled under the covers is this reference is a ""hashtag"", and since it's infeasible to parse out spaced tags it is converted to the i_am_snake_case whenever a project with a space is created. That means we have two cases within the context of phabricator ignoring the /tag/Trusted User Tool fiasco, it can't be referenced as project in remarkup within any text field as written.
+
+===Character Groupings===
+
+Probably allowed: 
+
+`abcdefghijklmnopqrstuvwxyz0123456789-._~:[]!'()*+,;=`
+
+Missing due to custom use: 
+
+`# @`
+
+Missing due to inconsistency in reference or incompatbility:
+
+ `ABCDEFGHIJKLMNOPQRSTUVWXYZ&?/`
+
+
+===tl;dr=== 
+
+we are going to regret allowing things to be named in ways that create inconsistent references across the application.  please let's not do this and condemn ourselves to explaining it every day for the next ten years 
+
+
+`mediawiki-extensions-googlelogin` ftw",1410486131,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-25 13:55:28 (UTC)`
+
+@Rush, see {T495}. It's a project creation request with a strict CamelCase name. You said this is a problem. I asked why and provided my reasons to avoid project names with lower case only and dashes. What is the conclusion?",1410486130,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-17 11:38:14 (UTC)`
+
+I had what I needed, I only couldn't see it.
+
+Anyway, I have simplified the instructions to request a new project. It all boils down to create a task specifying the name and description of the project, and a reasoning for special access permissions if the defaults don't work for you. 
+
+There is a note for teams expecting to create several projects. Those will need to start with a project for the team.
+
+https://www.mediawiki.org/wiki/Phabricator/Help#Requesting_a_new_project
+
+I will start testing this process with {T458}.",1410486130,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Rush** wrote on `2014-07-16 19:01:19 (UTC)`
+
+@qgil, I""m not sure what you are looking at?
+
+your a phab admin (meant in both senses)
+your in security group
+phabricator-request-project is all users for all fields
+http://fab.wmflabs.org/T458 is all users for all fields
+
+what perm screen are you looking for?
+",1410486129,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-16 18:57:07 (UTC)`
+
+@Rush I still can't access the admin options to check the possible permissions...",1410486129,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Rush** wrote on `2014-07-16 15:26:16 (UTC)`
+
+@qgil you are now security! ",1410486129,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-16 12:05:52 (UTC)`
+
+>>! In T457#7, @Rush wrote:
+> * I'm not sure how we limit comment ability unless it's the broader view/edit permissions?
+
+This might be because I had to recall the types of permission by heart. Can I get momentarily admin access to check those permissions, document accordingly, and then give back (again) the admin rights, please?",1410486128,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**qgil** wrote on `2014-07-16 11:54:30 (UTC)`
+
+>>! In T457#7, @Rush wrote:
+> * Naming scheme should depend on the type of project (these determine the icon and picture and maybe color?)
+> 
+> -- work queues (buckets for work to be organized into...overlapping)
+> -- group of people
+> -- straight up tag
+
+Documented at https://www.mediawiki.org/wiki/Phabricator/Help
+ 
+>  * In order to have a naming scheme projects can't be editable by users once created?  Otherwise we spend a lot of time ensuring consistent levels of abstraction, and organization and then it's all out the window post-creation process.  
+
+Yes, ideally projects can only be renamed by the Phabricator Request Project members.
+
+ 
+> * Project creation isn't a super user priv, just one that requires understanding how this stuff is organized for consistency across the install.   I would say, team leads, etc can create?  Assuming reasonable good faith in the context for people we trust.
+
+I would leave it to Phabricator Request Project memberr, or even something more precise like ""Phabricator Project Creators"", and then invite there whoever needs to create projects regularly and understands the drill.
+
+
+> * This one is sure to be fun :)  projects should be not be camel case, also known as lower case only please.
+
+??? ""Wikimedia Phabricator Day 1"" results in http://fab.wmflabs.org/tag/wikimedia_phabricator_day_1/ automatically.
+
+> this type of reference being pretty standard we are going to dig ourselves into a weird space where Security is a project in the project field, yet /tag/Security doesn't reference the object (/tag/security does).
+
+How do you get "" /tag/Security"" apart from typing it manually? Why is this is a problem? I'd rather give preference to a human friendly interface, where projects can be defined with natural names.
+
+About project members, is there a need to define them when requesting a new project? We can create ""Project X"" with the user requesting its creation as member, and then set permissions so that the ""Project X"" team can invite new members, right?",1410486128,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**Rush** wrote on `2014-07-15 18:13:13 (UTC)`
+
+@MissGayle I'm not sure yet how to respond since the process itself doesn't exist :)
+
+Ok, so a few general thoughts re: project creation I have been hoarding...
+
+* Naming scheme should depend on the type of project (these determine the icon and picture and maybe color?)
+
+-- work queues (buckets for work to be organized into...overlapping)
+-- group of people
+-- straight up tag
+
+ * In order to have a naming scheme projects can't be editable by users once created?  Otherwise we spend a lot of time ensuring consistent levels of abstraction, and organization and then it's all out the window post-creation process.  
+
+* Project creation isn't a super user priv, just one that requires understanding how this stuff is organized for consistency across the install.   I would say, team leads, etc can create?  Assuming reasonable good faith in the context for people we trust.
+
+* This one is sure to be fun :)  projects should be not be camel case, also known as lower case only please.
+
+There are a few reasons but the most overt can be demonstrated like this:
+
+this exists: http://fab.wmflabs.org/project/view/40/
+
+Often referenced within the install as http://fab.wmflabs.org/tag/<project>
+
+But, only lower case non-space references work:
+
+http://fab.wmflabs.org/tag/trusted_user_tool/
+
+this type of reference being pretty standard we are going to dig ourselves into a weird space where Security is a project in the project field, yet /tag/Security doesn't reference the object (/tag/security does).  That is how it works currently, and it's already confusing and weird.
+
+That means spaces and capitals within a project name force an inconsistency in reference
+
+* Before creating people centric projects for assigning of rights, etc.  An effort should be made to ensure it doesn't exist as another name already. (same logic applied all around I guess)
+
+* For non-people oriented projects restricting who can join them, not sure if it makes sense?
+
+* I'm not sure how we limit comment ability unless it's the broader view/edit permissions?
+
+* The who can join/edit/see type permissions need to be specified in phabricator user account terms
+or group terms
+
+Using the request here as a first-through-the-breach  instance I have done this:
+
+http://fab.wmflabs.org/T458
+
+Mostly for discussion...
+
+
+tl;dr to get a new project:
+
+* create a request task and associate http://fab.wmflabs.org/tag/phabricator-request-project/
+* gets reviewed in same manner as a gerrit change, etc.  Can be commented on, certain people can do the work, etc
+
+",1410486128,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+Document a process to request new projects,"**MissGayle** wrote on `2014-07-15 17:42:18 (UTC)`
+
+What're the naming conventions?
+
+project name following the naming conventions (link)
+- Talent & Culture Office
+description including the purpose of the project -- you will be able to edit it after the project has been created
+- Tracking HR projects and key deliverables in a transparent manner
+access policies -- the defaults are public view and equal access for all registered users
+- public 
+who can view the project and tasks (list options, default Public)
+- public 
+who can join the project (list options, default ?)
+- anyone in HR (Gayle, Anna Stillwell, Joady Lohr, Anna Lantz, Emanuela Neagu, Heather McAndrew, Emily Blanchard, Jenn Suzuki, Elena Hernandez) 
+who can edit tasks (list options)
+- anyone in HR (Gayle, Anna Stillwell, Joady Lohr, Anna Lantz, Emanuela Neagu, Heather McAndrew, Emily Blanchard, Jenn Suzuki, Elena Hernandez) 
+who can add comments (list options)
+- anyone
+(are there more sensible options?)",1410486127,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-x3hpjdsv6mi5u6x6aket,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects",Currently the process (except for security) https://www.mediawiki.org/wiki/Backporting_fixes implies usage of flags.,1397887689,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_description,resolved
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","@MarkAHershberger, @Mglaser: Task 76168 got backported to 1.24. Not sure if you want the #MediaWiki-Tarball-Backports project to be added to that task. https://www.mediawiki.org/wiki/Backporting_fixes#Backports_to_stable.2Fsupported_release does not cover this ""retroactively"" - whatever works for you and isn't overhead.",1417656886,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects",">>! In T101#11104, @Aklapper wrote:
+> Project names: ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports""
+> 
+> as usual confused whether the action to create and set up these two projects should now be separate tasks...
+
+@greg, @MarkAHershberger, @mglaser: I have created #WMF-Server-Backports and #MediaWiki-Tarball-Backports and added you accordingly. Was unsure which [[ https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Type%20project | type/kind of project ]] these are so I sticked with the default (briefcase/blue) for the time being.",1417057965,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","We do not migrate any flag data from Bugzilla so this does not block T259.
+
+Project names: ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports""
+
+Closing the ""figure out a process"" part as resolved, as usual confused whether the action to create and set up these two projects should now be separate tasks...",1413283003,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","Are there any more details that must be decided here? We really need to close this task, or at least have it in a state where it is not blocking T259 anymore.
+
+In other words, the period for input to the migration script needs to end. We can always file tasks based on the results of {T552}.",1413026975,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects",">>! In T101#9607, @Aklapper wrote:
+> **Project naming:**
+> 
+> ""WMF-Backports"" and ""MediaWiki-Backports"" doesn't feel explanatory enough to me. Sounds too similar to other subprojects which have a defined codebase area. ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" will work for me. Let's go for that?
+
+I'll probably make a short version for WMF-Server-Backports (aka ""WMF-Backport""), but sure :)   (just like I made ""#releng"" for ""#Release-Engineering"")
+
+
+> **Bugzilla Backport Flags migration aspect only:**
+> 
+> Tickets with any of our two Bugzilla flags (Backport_WMF and Backport_to_Stable) set will not have the flag information migrated to Phabricator. I don't see any historical need to know whether something was backported at some undefined point in the past (and that information is available in comments anyway if somebody is curious).
+> 
+> Regarding currently open tickets with Backport requests that have not been decided on, there are less than 10 of them hence the effort is not worth it to write migration code covering that.
+> I have cleaned up WMF backport requests yesterday and I've sent an email today to the Tarball Release Team to please take a look at the queue of undecided tarball backport requests. 
+> Furthermore Bugzilla will be available as read-only for some time after the migration so we could still look up which Bugzilla tickets had this flag if we wanted.
+
+Probably fine. We can get backport information from git but it'll obviously not have the bug info (if there was a bug).",1412806878,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**Project naming:**
+
+""WMF-Backports"" and ""MediaWiki-Backports"" doesn't feel explanatory enough to me. Sounds too similar to other subprojects which have a defined codebase area. ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" will work for me. Let's go for that?
+
+**Bugzilla Backport Flags migration aspect only:**
+
+Tickets with any of our two Bugzilla flags (Backport_WMF and Backport_to_Stable) set will not have the flag information migrated to Phabricator. I don't see any historical need to know whether something was backported at some undefined point in the past (and that information is available in comments anyway if somebody is curious).
+
+Regarding currently open tickets with Backport requests that have not been decided on, there are less than 10 of them hence the effort is not worth it to write migration code covering that.
+I have cleaned up WMF backport requests yesterday and I've sent an email today to the Tarball Release Team to please take a look at the queue of undecided tarball backport requests. 
+Furthermore Bugzilla will be available as read-only for some time after the migration so we could still look up which Bugzilla tickets had this flag if we wanted.",1412781221,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","No strong opinion either, and no willingness to bikeshed at all. Just trying to apply a principle of starting simple, knowing that we can write more complex names if the simple are confusing.",1411569958,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","> WMF-Backports?
+
+No strong opinion - just not sure if that's clear enough, keeping in mind that we will also have projects like ""Wikimedia-Site_requests"" after importing from Bugzilla, see T43
+
+> MediaWiki-Backports?
+
+...and that would be in a Product-Component row with stuff like ""MediaWiki-Categories"", ""MediaWiki-Page_editing"" and so on, but the different color and tag (like a keyword) might be sufficient.",1411568380,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","Could we simplify the name? WMF-Backports?
+What about backports to MediaWiki releases? MediaWiki-Backports?",1411560539,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","Alright, let's keep it simple for the start: Create a ""Backport_to_WMF_servers"" project in Phabricator and ask interested people (@greg, SWAT) to become members of that project (so they are subscribed to the project) or even ""watch"" that project (more or less the same).
+
+Anybody can propose a backport for the fix of a task by adding ""Backport_to_WMF_servers"" to the Projects list for a task (similar to setting that flag in Bugzilla which also wasn't very discoverable, so not much worse). 
+We'll fall back to adding comments (and closing tasks) for clarification when a commit has been backported. 
+It's not better or worse than Bugzilla currently, where there's also some ambiguity whether to keep a ticket open or resolved when a fix has been merged into git master vs. all the wmf branches: It boils down to defining social workflows.
+
+Documentation in https://www.mediawiki.org/wiki/Backporting_fixes will need updates.
+
+We can still iterate on a more sophisticated solution after having migrated Bugzilla content.",1411558630,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","We need to define the process to be applied here and now.
+
+>>! In T101#21, @flimport wrote:
+> **greg** wrote on `2014-08-28 22:27:10 (UTC)`
+>> **Question2**: I //do not// see a way in Herald to define a rule ""Projects | name includes the string | WMF_server_deployment"" though, so somebody tell me I'm wrong that this would require subscribing to each project created every week? Uhm.
+> 
+> I couldn't find anything useful. I assume some script somewhere will be creating this projects (not Phab itself), so maybe the logic of who should be subscribed could stay in that script for now?
+
+Such script doesn't exists today...
+
+>> **Fallback:** If my questions above indeed do make things complicated, we could also start simple and stupid with a generic ""Backport_to_WMF_servers"" project, and could switch to a more sophisticated process later on when Phabricator provides more functionality (cf. release notes) needed.
+> 
+> I'm fine with that.
+
+So this might be it for now.",1411312636,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**Mglaser** wrote on `2014-08-28 22:33:43 (UTC)`
+
+Sounds like a good start. I assume the project ""MediaWiki_tarball_release"" will be generic and always points to the next maintenance release. It is then within the scope of the release team to decide whether to backport this to legacy and lts releases as well, right? ",1410485344,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**greg** wrote on `2014-08-28 22:27:10 (UTC)`
+
+>>! In T167#36, @aklapper wrote:
+> So it sounds like James and Greg want separate ""WMF server deployment 2014-05-29 (1.24wmf7)""-style projects for each weekly deployment.
+
+something, even just 1.XXwmfYY would be fine with me (dates may change due to holidays etc, so predicting them is hard, and we may change our deploy cycle/cadence in the future, too)
+ 
+> **Question1**: If above was possible (release notes) and we automatically set such a project: If a task with that ""deployment of the week""-project set is reopened (e.g. not entirely fixed) and that project entry isn't removed from the task, wouldn't the next person looking at the task interpret it as a backport request, if I understand the proposed logic correctly?
+
+If a task is reopened then who ever is triaging those should move the project to the latest 1.XXwmfYY project. That should be clear enough.
+(This is where I want Launchpad's per project status... but I digress)
+
+> **Question2**: I //do not// see a way in Herald to define a rule ""Projects | name includes the string | WMF_server_deployment"" though, so somebody tell me I'm wrong that this would require subscribing to each project created every week? Uhm.
+
+I couldn't find anything useful. I assume some script somewhere will be creating this projects (not Phab itself), so maybe the logic of who should be subscribed could stay in that script for now?
+
+> **Fallback:** If my questions above indeed do make things complicated, we could also start simple and stupid with a generic ""Backport_to_WMF_servers"" project, and could switch to a more sophisticated process later on when Phabricator provides more functionality (cf. release notes) needed.
+
+I'm fine with that.
+",1410485344,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-08-27 19:23:17 (UTC)`
+
+And to summarize what this task is about in one sentences: ""define a process to mark tasks which have merged commits in git master and those commits should be backported into 1.24wmf123 and deployed on the Wikimedia servers, and automatically notify those folks doing backports and deployments by adding such a ""backport"" project to such a task""",1410485344,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-08-27 19:20:32 (UTC)`
+
+@greg, @jdforrester: Any comments? I'm leaning towards ""keep it simple and stupid"" at the beginning, due to the open questions in my previous comment which sound cumbersome and error-prone.",1410485343,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-08-18 13:54:53 (UTC)`
+
+So it sounds like James and Greg want separate ""WMF server deployment 2014-05-29 (1.24wmf7)""-style projects for each weekly deployment.
+
+I have not tried yet if we can add such a ""deployment of the week""-project by default: ""If task is closed as ""resolved"" in certain timeframe, automatically set project X"" for the sake of getting release notes by running one Maniphest query. Need to play more with [[https://secure.phabricator.com/book/phabricator/article/herald/ | Herald]] rules which are pretty powerful.
+
+**Question1**: If above was possible (release notes) and we automatically set such a project: If a task with that ""deployment of the week""-project set is reopened (e.g. not entirely fixed) and that project entry isn't removed from the task, wouldn't the next person looking at the task interpret it as a backport request, if I understand the proposed logic correctly?
+
+So currently the summary would currently be:
+* Security issues will be handled via a ""Security"" project. Out of discussion/focus here.
+* For non-security fixes/bugs that are candidates to backport, we are going to use projects/tags:
+** ""WMF_server_deployment_2014-05-29_(1.24wmf7)"" (specific)
+** ""MediaWiki_tarball_release"" (generic, we can still change that)
+* People can and should follow (=receive mail notifications from Phabricator) these projects by setting up a personal [[ https://secure.phabricator.com/book/phabricator/article/herald/ | Herald ]] rule in Phabricator. **Question2**: I //do not// see a way in Herald to define a rule ""Projects | name includes the string | WMF_server_deployment"" though, so somebody tell me I'm wrong that this would require subscribing to each project created every week? Uhm.
+* General info: Projects can be marked as archived (e.g. tarballs that have been released) so they are not offered anymore.
+
+**Fallback:** If my questions above indeed do make things complicated, we could also start simple and stupid with a generic ""Backport_to_WMF_servers"" project, and could switch to a more sophisticated process later on when Phabricator provides more functionality (cf. release notes) needed.
+
+General reminder on the old ""one task can only have one task status"" vs. ""we have 'branches' being git master, versions on servers, and tarballs"" problem: Each Project board allows custom columns, and a task can belong to more than one project.
+
+(And now to bikeshed about our [[http://fab.wmflabs.org/project/query/advanced/ | favorite icon and color]]. Not!)",1410485343,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**Mglaser** wrote on `2014-07-17 09:29:33 (UTC)`
+
++1 to @greg wrt security releases. 
+
+Another question is whether we need to be able to differentiate between backport to current stable and backport to legacy/lts. In particular, this would be useful during pre-release / RC phases, where we want to get some of the master changes still into the tarball. Using a separate flag might be a bit over-organized, though.",1410485342,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**greg** wrote on `2014-07-16 16:58:31 (UTC)`
+
+>>! In T167#32, @aklapper wrote:
+>>>! In T167#28, @Nemo_bis wrote:
+>> Discussion above is focused on 1 out of 3 backport processes. Were MediaWiki release managers asked to comment?
+> 
+> The ""backport to deployed version on WMF servers"" process isn't that different to the ""backport to stable branch for next tarball release"" process and feels sufficiently covered to me.
+
++1 to ""backport to WMF servers"" and ""backport to stable releases"" are basically the same; I see zero substantial difference. So that's 2 of 3 use cases.
+
+The last use case, security releases, will be handled differently than the other 2 use cases, and it basically won't change in the world of Phab. We'll still have a Security private project, and we'll still make security releases from those bugs, er, tasks. We don't have a ""Backport to Security Release"" flag because all security bugs are private and in the same queue together already, a flag would be redundant.",1410485342,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-07-16 14:57:33 (UTC)`
+
+>>! In T167#28, @Nemo_bis wrote:
+> Discussion above is focused on 1 out of 3 backport processes. Were MediaWiki release managers asked to comment?
+
+The ""backport to deployed version on WMF servers"" process isn't that different to the ""backport to stable branch for next tarball release"" process and feels sufficiently covered to me.
+
+As written in T166, subprojects in https://secure.phabricator.com/T3670 will probably the way to go here too.",1410485342,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**Nemo_bis** wrote on `2014-06-12 06:40:48 (UTC)`
+
+Discussion above is focused on 1 out of 3 backport processes. Were MediaWiki release managers asked to comment? https://www.mediawiki.org/wiki/Backporting_fixes#Backports_to_stable.2Fsupported_release
+(Added Markus; I don't find hexmode.)",1410485341,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**jdforrester** wrote on `2014-05-30 15:56:48 (UTC)`
+
+>>! In T167#23, @greg wrote:
+>>>! In T167#21, @jdforrester wrote:
+>> We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" //etc.//. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+> 
+> I think that might be overkill initially, honestly. But I can be convinced otherwise.
+
+If we don't do it for WMF-wide we'll need to do it for VisualEditor at least to preserve the existing milestones which are used to tracking bugs, regressions, patches and so on… The feedback we've had from community members is that the clarity of deployment target on every bug (for Phabricator, read: task) and patch is that it's been very helpful and clear for them in understand what has changed and when.
+
+Also, I'd presume (hope!) that it would allow us to no longer create [[ https://www.mediawiki.org/wiki/MediaWiki_1.24/wmf7/Changelog | mw:MediaWiki 1.24/wmf7/Changelog ]] and its ilk, but instead have it neatly and usefully listed on the project ""WMF server deployment 2014-05-29 (1.24wmf7)"".",1410485341,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**jdforrester** wrote on `2014-05-30 15:55:32 (UTC)`
+
+>>! In T167#26, @aklapper wrote:
+>> We'd discussed creating a project for each deployment – so reproducible etc.. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+> 
+> I've also copied this comment to T166 as it relates not only to **backporting**. If we managed to //automatically// add a ""WMF server deployment 2014-05-29 (1.24wmf7)"" project to tasks whose status is set to resolved based on a timeframe, that would be lovely and would drop the need for a separate ""Backport to WMF servers"" project, as one could query for open tickets where that project was //manually// added.
+
+Yeah; I was thinking that it would also answer the ""what things are being proposed for backport to MW 1.23?"" with a ""MediaWiki 1.23"" project.",1410485341,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-05-30 15:37:56 (UTC)`
+
+> We'd discussed creating a project for each deployment – so reproducible etc.. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+
+I've also copied this comment to T166 as it relates not only to **backporting**. If we managed to //automatically// add a ""WMF server deployment 2014-05-29 (1.24wmf7)"" project to tasks whose status is set to resolved based on a timeframe, that would be lovely and would drop the need for a separate ""Backport to WMF servers"" project, as one could query for open tickets where that project was //manually// added.",1410485340,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**greg** wrote on `2014-05-29 22:17:33 (UTC)`
+
+>>! In T167#24, @jdforrester wrote:
+> Also, I'd presume (hope!) that it would allow us to no longer create [[ https://www.mediawiki.org/wiki/MediaWiki_1.24/wmf7/Changelog | mw:MediaWiki 1.24/wmf7/Changelog ]] and its ilk, but instead have it neatly and usefully listed on the project ""WMF server deployment 2014-05-29 (1.24wmf7)"".
+
+I'm convinced.",1410485340,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**greg** wrote on `2014-05-29 21:52:29 (UTC)`
+
+>>! In T167#21, @jdforrester wrote:
+> We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" //etc.//. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+
+I think that might be overkill initially, honestly. But I can be convinced otherwise.
+
+
+
+>>! In T167#19, @aklapper wrote:
+> Greg: Any opinions here?
+> 
+> Currently I favor creating a generic ""Backport to WMF servers"" project and making you subscribe to that project's notifications by you setting up a rule in Maniphest's Herald.
+
+I like this. Also a ""Backport to MediaWiki Releases"" project that the Release Team subscribe to.",1410485340,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**jdforrester** wrote on `2014-05-29 15:36:02 (UTC)`
+
+>>! In T167#19, @aklapper wrote:
+> Greg: Any opinions here?
+> 
+> Currently I favor creating a generic ""Backport to WMF servers"" project and making you subscribe to that project's notifications by you setting up a rule in Maniphest's Herald.
+
+We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" //etc.//. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.",1410485339,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-05-26 13:44:20 (UTC)`
+
+Greg: Any opinions here?
+
+Currently I favor creating a generic ""Backport to WMF servers"" project and making you subscribe to that project's notifications by you setting up a rule in Maniphest's Herald.
+
+(Note to myself: Updating the docs on https://www.mediawiki.org/wiki/Backporting_fixes is covered by T350)",1410485339,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**qgil** wrote on `2014-04-23 13:51:20 (UTC)`
+
+""query that project regularly"" = [[ https://secure.phabricator.com/book/phabricator/article/herald/ | Herald ]]
+
+We still need to play with that tool and see what can it offer.",1410485339,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**aklapper** wrote on `2014-04-23 06:37:15 (UTC)`
+
++1 for using a project and making people responsible for backports receive automatic notifications about it, or query that project regularly (social thing to solve, not technical).",1410485338,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**qgil** wrote on `2014-04-22 18:02:51 (UTC)`
+
+It looks like Phabricator provides enough elements for us to define this process.",1410485338,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+"Figure out a process for backports: Create ""WMF-Server-Backports"" and ""MediaWiki-Tarball-Backports"" projects","**qgil** wrote on `2014-04-19 16:11:19 (UTC)`
+
+Create a ""Backport WMF"" project and add the related tasks to that project? This could be used in combination with release projects and what not, see T166. ",1410485337,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-prw46t5ok4y7p3lhivye,task_subcomment,NA
+Decide how to organize iterations and releases,"Related task upstream: [[ https://secure.phabricator.com/T390#21 | Implement project types ]].
+
+I don't understand how we're going to mark release milestones: each release a blocked task, kept open for each sub-point release until the RELX_Y branch in question is frozen?
+(Due to http://fab.wmflabs.org/T164 we can't have two levels of dependency so I suppose we'll instead give up on granularity.)
+
+A handful of MediaWiki extensions are maintained by teams who use sprints, so the sprints could then be mapped to the RELX_Y branch in which they first appear and to the corresponding task; in this case (in theory) we'd gain, for no cost, that WMF work would be visible to tarball users.
+",1397886924,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_description,resolved
+Decide how to organize iterations and releases,I consider this task decided/resolved/closed.,1413266763,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,Works for us.  I like the rainbow.,1413247789,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"Thumb ups from me, this fits my team's workflow.",1413203234,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"Are there any more details that must be decided here? We really need to close this task, or at least have it in a state where it is not blocking T259 anymore.
+
+In other words, the period for input to the migration script needs to end. We can always file tasks based on the results of {T552}.",1413026715,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,">>! In T100#9608, @Aklapper wrote:
+> Trying to keep it simple for the start: Combine one color with one icon.
+
+Deal.
+
+> * Projects have a {icon briefcase} Briefcase icon (and blue color).
+> * Releases have a {icon truck} Release icon (and orange color).
+> * Sprints have a {icon calendar} Deadline icon (and some other color - indigo? shrug).
+> * For completeness: Cross-project 'keywords' (Bugzilla terminology) have a {icon tag} Tag icon (and red color I think).
+
+Yes to most points, but look what I've done instead: {M4}
+
+Let's finish the discussion about icons and colors in the mockup.",1412790085,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"Happy for the VisualEditor TMs to be magically transformed into projects to which each Bugzilla item is transferred as appropriate, but yes, we really need to keep that data if at all possible.",1412784445,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**Target Milestone data migration:**
+
+Sorry, this fell through the cracks and this is not entirely 'ready to go' yet but close.
+
+I'm currently checking the use of Target Milestones in Bugzilla products, and which TMs are in the past so I can disable setting these TMs in Bugzilla (cleaning up but need to talk to several teams), and which TMs are rubbish (see e.g. https://bugzilla.wikimedia.org/show_bug.cgi?id=71807 ).
+
+Projects in Bugzilla using Target Milestones:
+* Huggle (3 TMs, 3 of them active)
+* MediaWiki (15 TMs, 6 of them active)
+* MediaWiki extensions (8 TMs, 5 of them active)
+* MediaWiki skins (1 TMs, 1 of them active but TM set on 0 tickets)
+* VisualEditor (89 TMs, 89 of them active but asked James if past ones could be made inactive)
+* Wikimedia (1 active TM called 'Mysterious future' which I want to delete, see https://bugzilla.wikimedia.org/show_bug.cgi?id=71807)
+* Wikipedia App (2 TMs, 0 active)
+
+**Question:** Not sure if that makes things more complicated or not in the migation logic hence question might not make sense: I'm wondering whether we could/should ignore past TMs (TMs that are 'not active' / cannot be set anymore on Bugzilla tasks) and not necessarily migrate them into //archived// projects in Phabricator. On the other hand we'd lose data, e.g. which VisualEditor bug was fixed at which time, hence probably going for archived makes more sense.
+
+In any case, Bugzilla TMs should become deadline or release projects. See my previous comment.",1412784244,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"Different/separate tags for project (e.g. '{icon briefcase} VisualEditor') which covers all tasks in a project, vs. release (e.g. '{icon truck} VisualEditor 1.0.1') and vs. deadline (e.g. '{icon calendar} VisualEditor 2014-12-24').
+
+Trying to keep it simple for the start: Combine one color with one icon.
+
+* Projects have a {icon briefcase} Briefcase icon (and blue color).
+* Releases have a {icon truck} Release icon (and orange color).
+* Sprints have a {icon calendar} Deadline icon (and some other color - indigo? shrug).
+* For completeness: Cross-project 'keywords' (Bugzilla terminology) have a {icon tag} Tag icon (and red color I think).",1412782089,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"I just created a project for the [[ https://phabricator.wikimedia.org/T18 | Engineering Community October 2014 ]] sprint. A sprint is not a release, so I used another icon: {icon calendar}
+
+Sprints could have a color on their own, or they could have the same as releases, not to end up with a full-fledged rainbow.",1412715249,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"I got a bit lost with the discussion above and what we will start doing right now. Different tags for project and release, or single tags ""project + release""?
+
+Above you have covered stable MediaWiki releases 1.xx and also WMF weekly releases 1.xx-wmfZZ. Could we also add months as in yyyy-mm for those teams organizing monthly sprints? This is the case of at least Engineering Communty, but I imagine we are not the only ones.
+
+PS: enthusiastic thumbs up for {icon truck}!",1411312173,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"I got a bit lost with the discussion above and what we will start doing right now. Different tags for project and release, or single tags ""project + release""?
+
+Above you have covered stable MediaWiki releases 1.xx and also WMF weekly releases 1.xx-wmfZZ. Could we also add months as in yyyy-mm for those teams organizing monthly sprints? This is the case of at least Engineering Communty, but I imagine we are not the only ones.
+
+PS: enthustastic thumbs up for {icon truck}!",1411312160,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"I got a bit lost with the discussion above and what we will start doing right now. Different tags for project and release, or single tags ""project + release""?
+
+Above you have covered stable MediaWiki releases 1.xx and also WMF weekly releases 1.xx-wmfZZ. Could we also add months as in yyyy-mm for those teams organizing monthly sprints? This is the case of at least Engineering Communty, but I might imagine we are not the only ones.
+
+PS: enthustastic thumbs up for {icon truck}!",1411312112,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-08-10 19:58:22 (UTC)`
+
+For the time being (as implementing subprojects might take too long for us in upstream), the basic idea is to use projects (tags) in Phab, differentiating types via icons and colors. For releases (""target milestones"" in Bugzilla), imagine a truck tag for example, or check out the preliminary screenshot. 
+
+Not entirely set in stone yet and just to show the basic idea. All kudos goes to Chase.
+Sigh, as I get an ""Upload Failure"" both with Chrome and Firefox here, external link to screenshot: [[ http://home.arcor.de/ak-47/tmp/Phab-Project-Tags-T46.png ]]",1410485335,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**SG** wrote on `2014-07-10 20:27:36 (UTC)`
+
+That does seem like it would fit our needs. It's slightly less clunky than our proposed solution.",1410485335,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-07-06 20:35:34 (UTC)`
+
+Upstream decided to try subprojects in https://secure.phabricator.com/T3670 (makes our T240 a WONTFIX), which ""will make an attack on sprints/milestones/versions."" This might make our life easier?",1410485334,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**jdforrester** wrote on `2014-06-09 18:16:52 (UTC)`
+
+>>! In T166#40, @aklapper wrote:
+>  * Planning to fix a task in a past version (backporting to servers; only applies for //WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//)
+
+Actually, we also do this for releases – tagging bugs as things that need to get fixed in 1.23.1 for example.  However, I don't think it makes a major difference.
+
+> So.... does this novel make any sense?
+
+Yes! It looks good. I'd suggest having a ""Backport to MediaWiki releases"" project for the MW release maintainers as well, but yes, it works for us.",1410485334,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**mmodell** wrote on `2014-06-09 17:51:24 (UTC)`
+
+Documenting when a big fix got released should be simple because you can link a git commit to a task as well as linking differential revisions. It would be trivial to traverse the git log from the newest commit to find the next release tag that occurs between the relevant commit and HEAD. That version tag can be exposed In the task ui as the first release containing the fix.",1410485334,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-06-06 17:14:12 (UTC)`
+
+Spent the afternoon thinking about this item. Please show me that I'm wrong and that this can be made less complex.
+
+**Underlying assumptions:**
+* On branching for a new //xx// in //WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//: No fix for a task / commit can be included in //WMF server deployment 1.xx-wmfZZ// which would not also automatically be included in //tarball 1.xx-rc// or //tarball 1.xx.0//. In other words: When switching from //WMF server deployment 1.23-wmf26// to //WMF server deployment 1.24-wmf0//, the //tarball// branch for 1.23 gets created at the very same time.
+* The term ''version'' in the rest of this comment refers to a string like //1.xx.y// or //1.xx-wmfZZ// or //Sprint 1// or //yyyy-mm-dd//. It might also be an //iteration// or a //sprint// (simplified as several //iterations// can become a //release// / //version//, but I really got to start somewhere).
+* We do not rename projects which include versioning in their names as it would make ChangeLog creation (and burndown charts?) impossible. Discussed above in T166.
+
+**Situations we face:**
+ * Planning to fix a task in a future version (//WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//, would automatically also end up in //tarball 1.xx.0//)
+ * Planning to fix a task in a past version (backporting to servers; only applies for //WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//)
+ * Documenting that a task got resolved in a timeframe (cf. ChangeLog), hence fixed in //WMF server deployment 1.xx-wmfZZ (yyyy-mm-dd)//, would automatically also end up in //tarball 1.xx.0//. (TODO: No idea if this could be set automatically, but that would be lovely.)
+ * Documenting that a task planned for a version (well, rather explicitly //sprint// in this case) was planned but did //not// get resolved in that timeframe.
+
+**Conflict about interpreting versions (//affected// vs //fixed in//):**
+* If we reflect //versions// in or via //project names//, we easily end up with a semantic conflict when the task is closed as resolved: Was that version //affected// by the bug reported in the task? Or did that version include a //fix// for the bug reported in the task?
+* I tend towards using //Versions which include a fix for a problem/task// because planning is more important in a task management tool than info about the version used by the task's reporter. This must be clearly expressed in our docs (T350).
+* Making this clear is also important for projects with sprints / release cycles not aligned with WMF deployment cycles (also keep 3rd party development in mind).
+
+**Getting notified about backporting requests (T167):**
+ * Refering to the situation //Planning to fix a task in a past version (backporting to servers)//; the third assumption says //We do not rename projects which include versioning in their names//.
+ * In practice it means that when 1.xx-wmfZZ gets deployed on the first WMF servers, Release Management (Greg etc) would have to subscribe via Herald to watch the project //WMF server deployment 1.xx-wmfZZ// in order to get notifications whenever a task is added to that project (= a request to backport).
+ * The same thing would happen every 7 days (for //WMF server deployment 1.xx-wmfZZ+1//, etc.) which sounds really cumbersome and error-prone.
+ * Instead we might want to have a ""static""/""generic"" //Backport to WMF// project so people don't have to subscribe to its notifications every week?
+ * Once a backport has been granted and merged, the task must be edited by removing the //Backport to WMF// project and by adding the //WMF server deployment 1.xx-wmfZZ// project. Disadvantage here: We'd lose statistics on how often we need to backport stuff.
+ * TODO: We might also have to document that the task whose fix should get backported must remain open (T350), not sure how flexible the notification system is.)
+
+Based on that above assumptions can be considered correct, we might end up with these things //in parallel//:
+ * generic projects: //MediaWiki// (covered in T68; task reporters are encouraged to set them)
+ * sprint/iteration projects: //Team XYZ Sprint 23 (2014-05-08)//
+ * WMF server deployment projects: //Fixed in WMF server deployment 1.xx-wmfZZ//
+ * One generic WMF backport request project release management should subscribe to: //Backport to WMF servers//
+ * For projects not following the WMF server deployment or MediaWiki tarball release schedule: //Fixed in $projectname x.y.z//
+
+Tarball release projects (like //MediaWiki release 1.xx.y//) for fixed/resolved tasks would not be needed if the aforementioned first assumption on branching holds true, as one could query for all tasks in project //WMF server deployment 1.xx-wmfZZ// where 0 ≤ ZZ ≤ 26. 
+Though I am not convinced if that would be discoverable enough to 3rd party MediaWiki users in order to find out in which tarball version a fix is supposed to be included - TODO: might need to document that.
+
+So.... does this novel make any sense?",1410485333,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-05-30 21:40:04 (UTC)`
+
+In this case, renaming projects is not an option.
+
+Wouldn't the workboard of <sprint/deployment> be enough?",1410485333,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**jdforrester** wrote on `2014-05-30 21:35:40 (UTC)`
+
+>>! In T166#37, @qgil wrote:
+> Maybe this sounds silly, but what about
+> 
+> # Work on the tasks at project ""WMF server deployment 2014-05-29 (1.24wmf7)"".
+> # By the end of 2014-05-29, some tasks will be resolved and forgotten, others will remain open.
+> # Rename the project to ""WMF server deployment 2014-06-05 (1.24wmf8)"".
+> # Add the new tasks you want to complete in addition to the ones you still have open.
+> 
+> If you don't like the idea of simply renaming projects for whatever obscure archiving reason, then ""Edit batch"" selecting ll open tasks of a project can make wonders. Not automatic but still pretty simple.
+
+Where would the static links to ""tasks fixed in <sprint/deployment>"" and ""code landed in <sprint/deployment>"" live? That's one of the key needs from my POV. ",1410485333,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-05-30 19:19:49 (UTC)`
+
+Maybe this sounds silly, but what about
+
+# Work on the tasks at project ""WMF server deployment 2014-05-29 (1.24wmf7)"".
+# By the end of 2014-05-29, some tasks will be resolved and forgotten, others will remain open.
+# Rename the project to ""WMF server deployment 2014-06-05 (1.24wmf8)"".
+# Add the new tasks you want to complete in addition to the ones you still have open.
+
+If you don't like the idea of simply renaming projects for whatever obscure archiving reason, then ""Edit batch"" selecting ll open tasks of a project can make wonders. Not automatic but still pretty simple.",1410485332,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**jdforrester** wrote on `2014-05-30 15:53:56 (UTC)`
+
+>>! In T166#33, @aklapper wrote:
+> Copying @jdforrester's comment from T167:
+> 
+>> We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" etc.. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+> 
+> If we did that, we might want to be able to //close projects if they are in the past// (disable adding a project to a task). Now I need to find out if that's possible already, and if not I'll upstream.
+> 
+> The problem I see is that we'd want to add such a ""Deployment Target Milestone"" project to tasks automatically in the long run: Closing a task in a certain timeframe in a certain project should automatically add this project to the task. Which will be a complex feature request.
+
+That'd be a nice-to-have, but we don't have it on Bugzilla and I manage it manually instead. The important thing would be an automtic ""add change to project"", which presumably we could do as part of the script that currently posts the list on MediaWiki.org?",1410485332,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-05-30 15:39:17 (UTC)`
+
+Answering my own question thanks to upstream IRC:
+
+> we might want to be able to close projects if they are in the past (disable adding a project to a task).
+
+<mikkn>  If you go to Projects then click on the project in question, then edit, you will have an ""Archive Project"" button there",1410485331,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-05-30 15:16:16 (UTC)`
+
+Copying @jdforrester's comment from T167:
+
+> We'd discussed creating a project for each deployment – so ""WMF server deployment 2014-05-29 (1.24wmf7)"" etc.. This would potentially leave us with a lot of projects, but it would map well to the workflow of ""are there any outstanding code commits for deployment?"" which is common.
+
+If we did that, we might want to be able to //close projects if they are in the past// (disable adding a project to a task). Now I need to find out if that's possible already, and if not I'll upstream.
+
+The problem I see is that we'd want to add such a ""Deployment Target Milestone"" project to tasks automatically in the long run: Closing a task in a certain timeframe in a certain project should automatically add this project to the task. Which will be a complex feature request.",1410485331,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-05-15 14:07:55 (UTC)`
+
+At the teampractices mailing list there is a discussion about [[ http://lists.wikimedia.org/pipermail/teampractices/2014-May/000411.html | how to organize sprints ]]. While [[ https://secure.phabricator.com/T390#21 | the upstream solution ]] arrives, it would be good to know how Phabricator users do this nowadays.
+
+As far as I can see, the process seems to be something like this:
+
+# A //Project X// exists containing several tasks. Optionally, a team is created for it.
+# A new //Project X Sprint 1// project is created. The tasks from //Project X// to be included in the sprint are tagged accordingly. The only relation between these projects is their naming convention. For Phabricator these are independent projects. Herald rules can be created to assign to //Project X// any task created for //Project X*// automatically.
+# At the end of the sprint, //Project X Sprint 1// is archived and //Project X Sprint 2// is created. The remaining tasks of Sprint 1 can be moved to the next sprint with a single batch edit.
+
+There are some manual steps that in the future should be automatized, but other than that the process seems to be simple enough? Creating projects is simple, you only need to add a title and, if you wish, you can copy & paste a stock description. Membership of these subprojects is not relevant. If you want to set some special permissions for the developer team you can simply set those permissions to the //Project X// team.",1410485331,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**mattflaschen** wrote on `2014-04-29 04:30:12 (UTC)`
+
+>  (Due to http://fab.wmflabs.org/T164 we can't have two levels of dependency so I suppose we'll instead give up on granularity.)
+
+Do you mean that you can't visualize two levels in a chart?  You can have arbitrary dependencies, as far as I can tell.  Two-level example: T248 depends on T249, which depends on T250.",1410485330,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-04-28 13:14:48 (UTC)`
+
+Moving here this comment from @awjrichards at {T44}
+
+* The concept of bucketing 'tasks' into an 'iteration'
+** This also includes the ability to look at past iterations (and what was contained in them)
+** As well as the ability to look at future iterations (and what will be contained in them)
+* The concept of bucketing 'iterations' into a broader 'release'",1410485330,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-04-24 14:05:29 (UTC)`
+
+There is a plan to [[ https://secure.phabricator.com/T390#21 | implement project types ]] that would include 
+
+  ( ) Tag
+    Tags are lightweight projects that don't have members or wiki pages.
+    
+  ( ) Sprint
+    Sprint projects organize work into a series of iterations. Iterations
+    are created automatically and incomplete tasks roll from one iteration to
+    the next.
+
+In the meantime, I think we could work with specific projects and queries. According to some comments in that task, this is how some orgs are doing it.",1410485330,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**aklapper** wrote on `2014-04-24 09:15:47 (UTC)`
+
+Projects + queries (like ""open tickets in all these projects: '1.23.0 release' && 'MediaWiki'"").",1410485329,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-04-22 18:03:22 (UTC)`
+
+It looks like Phabricator provides enough elements for us to define this process.",1410485329,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize iterations and releases,"**qgil** wrote on `2014-04-19 16:05:43 (UTC)`
+
+Why not creating project ""1.23.0 release"", and add the relevant tasks there? Release managers would even get a workboard to mark mark the status of each task from that release point of view.",1410485329,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-yrvvt5gp7rnhtwez34gc,task_subcomment,NA
+Decide how to organize projects,"> Project behavior in Maniphest is similar to keywords behavior in Bugzilla
+
+Right, but then... what about keywords? Are they supposed to be enabled separately or are we using projects literally as keywords?
+
+By the way, since we may have finally a common system for keywords/tags across different tools, this might be relevant: https://www.mediawiki.org/wiki/Project:New_contributors/One_ontology
+
+**UPDATED**: 
+
+Projects are keywords, keywords are projects, components might be projects if we want... We need to come up with a default organization of projects, knowing that user will come and create the projects they miss (unless we stop them by restricting permissions), just like wiki editors create categories.
+
+**RULES FOR MIGRATING PROJECT NAMES**
+
+
+  buginfo[""product""] = buginfo[""product""].replace('-', '_')
+  buginfo[""product""] = buginfo[""product""].replace(' ', '_')
+  buginfo[""component""] = buginfo[""component""].replace('/', '_and_')
+  buginfo[""component""] = buginfo[""component""].replace('-', '_')
+  buginfo[""component""] = buginfo[""component""].replace(' ', '_')
+
+  component_separator = '-' 
+  project = ""%s%s%s"" % (buginfo[""product""],
+                       component_separator,
+                       buginfo[""component""])
+
+
+Examples:
+
+| Bugzilla product | Bugzilla component | Phabricator project |
+| MediaWiki | Change tagging | MediaWiki-Change_tagging |
+| MediaWiki‑Vagrant | labs-vagrant | MediaWiki_Vagrant-labs_vagrant |
+| Wikimedia | Git/Gerrit | Wikimedia-Git_and_Gerrit |
+| Wiki Loves Monuments | Unused images | Wiki_Loves_Monuments-Unused_images |",1397154942,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_description,resolved
+Decide how to organize projects,">>! In T43#15328, @Qgil wrote:
+> It's not a bug, it makes sense that URLs of projects follow the names of the projects, and if you edit one, the other follows.
+
+Lack of redirects after renaming a project is almost certainly a bug, as I laid out in T910.
+
+>>! In T43#15314, @Qgil wrote:
+> Please, could you revert your changes and open a new tasks to discuss specifically the substitution of dashes and underscores by spaces?
+
+I filed T911 to track this issue.",1414278905,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"True, the URLs. I have reverted your renaming of ""Bugzilla-Preview"" to make sure that this URL that we have sent to everybody in the past 48h works:
+
+https://phabricator.wikimedia.org/tag/bugzilla-preview/
+
+If you change the dash for a space, then you get
+
+https://phabricator.wikimedia.org/tag/bugzilla_preview/
+
+It's not a bug, it makes sense that URLs of projects follow the names of the projects, and if you edit one, the other follows. You can also link to the project number (https://phabricator.wikimedia.org/project/view/40/) but we opted to promote the self-explanatory URL.
+
+",1414278460,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,">>! In T43#15315, @chasemp wrote:
+> Changing this broke links currently shared to the migration effort.  I have locked this project to prevent this from happening again as people are trying to follow up on emails sent with details about the coming changes.  It would be more appropriate to start a discussion on whether another name is preferable rather than taking action that has unintended consequences.
+
+Uhh, that sounds like a Phabricator bug. I filed T910 to track this issue.",1414278151,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,">>! In T43#15276, @MZMcBride wrote:
+> I changed ""Bugzilla-Migration"" to ""Bugzilla migration"" because MediaWiki/Wikimedia development typically uses sentence case and standard word demarcation.
+> 
+> If Phabricator can't handle spaces, a very basic component of English and other languages, in project display names, then Phabricator will need to be fixed. But as a label, ""Bugzilla-Migration"" and similar awkwardly hyphenated and capitalized project names are pretty bad and should be avoided, in my opinion.
+
+Changing this broke links currently shared to the migration effort.  I have locked this project to prevent this from happening again as people are trying to follow up on emails sent with details about the coming changes.  It would be more appropriate to start a discussion on whether another name is preferable rather than taking action that has unintended consequences.",1414277785,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,">>! In T43#15276, @MZMcBride wrote:
+> I changed ""Bugzilla-Migration"" to ""Bugzilla migration"" because MediaWiki/Wikimedia development typically uses sentence case and standard word demarcation.
+> 
+> If Phabricator can't handle spaces, a very basic component of English and other languages, in project display names, then Phabricator will need to be fixed. But as a label, ""Bugzilla-Migration"" and similar awkwardly hyphenated and capitalized project names are pretty bad and should be avoided, in my opinion.
+
+Changing this broke links currently shared to the migration effort.  I have locked this project to prevent this fromhappening again as people are trying to follow up on emails with details about the coming changes.  It would be more appropriate to start a discussion on whether another name is preferable rather than taking action that has unintended consequences.",1414277751,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"@MZMcBride, we invested a fair amount of time, energy and patience in order to decide [[ https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Guidelines | the current guidelines ]]. You can challenge the guidelines with better arguments, and if the guidelines change then we can change the names of project accordingly. Please, could you revert your changes and open a new tasks to discuss specifically the substitution of dashes and underscores by spaces?",1414277598,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"I changed ""Bugzilla-Migration"" to ""Bugzilla migration"" because MediaWiki/Wikimedia development typically uses sentence case and standard word demarcation.
+
+If Phabricator can't handle spaces, a very basic component of English and other languages, in project display names, then Phabricator will need to be fixed. But as a label, ""Bugzilla-Migration"" and similar awkwardly hyphenated and capitalized project names are pretty bad and should be avoided, in my opinion.",1414275908,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"We aim at having a clear and consistent migration script logic. MediaWiki has 43 components; Wikimedia 34; MediaWiki_extensions a few more; we can rename stuff after importing, but please not in the migration script logic.
+
+Redundancy: Depends. Seeing component names such as ""Uploading"" you're supposed to have different teams working on uploading related stuff on different architecture levels (Core upload handling code, low-level media storage, Multimedia team's UploadWizard etc.).",1411653583,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"Some time ago I proposed to get rid of ""MediaWiki"" and ""Wikimedia"" since most of the times they are redundant, but I can see how that might be easier to do manually than with a magical instruction in the scrip.
+
+I find the combination of -_-_ disturbing. Possible scenarios:
+
+# Leave it as it is now and wait until our eyes get used to them.
+# Leave it as it is now and convert everything to dashes manually where makes sense.
+# Convert everything to dashes with the script, editing manually if this option is confusing in a project name.
+
+My preferred is 3, although 2 would be fine, an even 1 if I'm the only one being picky about this.  :)",1411649710,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"| Bugzilla product | Bugzilla component | Phabricator project |
+| MediaWiki | Change tagging | MediaWiki-Change_tagging |
+| MediaWiki‑Vagrant | labs-vagrant | MediaWiki_Vagrant-labs_vagrant |
+| Wikimedia | Git/Gerrit | Wikimedia-Git_and_Gerrit |
+| Wiki Loves Monuments | Unused images | Wiki_Loves_Monuments-Unused_images |",1411645395,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"Could you give some examples of the result of this pattern? I think I get it, but maybe I'm wrong.",1411587325,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"Yeah, done.
+
+Pasting the name replacement rules here, for the records:
+
+  buginfo[""product""] = buginfo[""product""].replace('-', '_')
+  buginfo[""product""] = buginfo[""product""].replace(' ', '_')
+  buginfo[""component""] = buginfo[""component""].replace('/', '_and_')
+  buginfo[""component""] = buginfo[""component""].replace('-', '_')
+  buginfo[""component""] = buginfo[""component""].replace(' ', '_')
+
+  component_separator = '-' 
+  project = ""%s%s%s"" % (buginfo[""product""],
+                       component_separator,
+                       buginfo[""component""])",1411557406,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"Naming guidelines as discussed here are have been drafted at https://www.mediawiki.org/wiki/Phabricator/Help#Requesting_a_new_project 
+
+[[ https://phabricator.wikimedia.org/project/query/o8VA7EyUUHZT/#R | Active projects ]] in this instance have been renamed accordingly.
+
+Is there anything else left in this task?",1411142613,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-09-08 15:48:20 (UTC)`
+
+at this point we can leave existing?  Mainly these restrictions are for imported content atm, I'm sure the ongoing etymology will provide plenty of conversation and change opportunities :)",1410485032,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-09-07 20:45:35 (UTC)`
+
+Is there anything else to be decided before closing this task?
+
+>>! In T68#68, @aklapper wrote:
+> Once issues created by **spaces** for URLs and referencing have been handled/fixed in upstream, we can still pretty up project names in our instance if we want.
+
+Is it worth renaming now the projects that will be migrated to follow all the same guideline?
+
+* Project
+* Great-Project
+
+I can do it in the next hours. Or we can wait and do it after the migration if you prefer.",1410485032,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-08-10 19:25:38 (UTC)`
+
+Once issues created by **spaces** for URLs and referencing have been handled/fixed in upstream, we can still pretty up project names in our instance if we want. 
+
+Currently we cannot entirely judge how often referencing is needed and used e.g. in Differential (pre-push code review tool) etc. Upstream does avoid spaces in project names, so I'd like to follow upstream here, even if things don't look pretty for use at first.",1410485031,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-08-05 20:14:10 (UTC)`
+
+Indeed! Regardless of the outcome, it is very good to see that this discussion is helping making Phabricator more robust with project names. Thank you @Rush.",1410485031,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Florian** wrote on `2014-08-05 19:03:19 (UTC)`
+
+@Rush That seems to solve one problem and looks very good :) Thanks!",1410485031,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-08-05 00:11:53 (UTC)`
+
+for fun:
+
+http://fab.wmflabs.org/tag/mediawiki/
+http://fab.wmflabs.org/tag/MEDIAWIKI/
+http://fab.wmflabs.org/tag/MeDiAwIkI/
+",1410485030,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-08-05 00:10:34 (UTC)`
+
+Case sensitivity in urls is now handled by normalizing to lower case:
+
+https://github.com/phacility/phabricator/commit/1e375c97c594e029d8e796c3fa937a7522e3b42f
+
+applied to fab for testing :)",1410485030,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-08-04 20:49:25 (UTC)`
+
+>>! In T68#60, @aklapper wrote:
+> So whenever people wanted to link to ""Project Name"" as in ""#project name"", we'd recommend to write ""#Project_Name"" and replace spaces by underscores. Question is how many users (non-heavy Phabricator users) we can make aware of it
+
+How many non-heavy Phabricator users are going to know that they can type ""#project"" in the first place? How often do you see this Markup feature in use? It sounds like a minor case even without spaces. Being project with spaces a minority, the relevance of the problem becomes smaller. And the worse that can happen is that a user can't type properly a reference of a project; not a big problem either.
+
+> plus I really don't know how much referencing is used in e.g. Differential and what other stuff we might break by using spaces in project names.
+
+Do we have specific examples? Phabricator supports spaces in project names. If this causes a problem we can file a bug upstream.",1410485029,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-08-04 20:03:35 (UTC)`
+
+thanks andre for that update :)  
+
+
+
+Pretty much my thought, get wider input on spaces if we are (in my eyes at least) overriding technical consistency for readability, and push along the case sensitivity mixup if that is a need for us.  FWIW, evan seemed to indicate the case strictness wasn’t too hard of a fix",1410485029,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-08-04 20:00:06 (UTC)`
+
+So whenever people wanted to link to ""Project Name"" as in ""#project name"", we'd recommend to write ""#Project_Name"" and replace spaces by underscores. Question is how many users (non-heavy Phabricator users) we can make aware of it, plus I really don't know how much referencing is used in e.g. Differential and what other stuff we might break by using spaces in project names.
+
+On the latter, //input from folks who have been using Phabricator extensively would help//. Chase and I don't feel entirely comfortable deciding for everybody here - it's clear that developers and engineering is the primary customer of Phab, but we'd also have HR and Legal and others here in the long run.
+
+As we'd like to not only use lower-case for project names, we want to get https://secure.phabricator.com/T5728 fixed first. Because if things don't work properly, people //will// work around them. I've asked in the upstream tickets for pointers.
+
+The general tradeoff we're discussing here is readability for humans vs. technical consistency (the value and use of referencing in Markup).",1410485029,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-07-30 21:00:36 (UTC)`
+
+Than you for the summary! Everything sounds sensible, except the bit about underscores in project names that I still (almost apologize for) disagree(ing) with.  :)
+
+>>! In T68#58, @aklapper wrote:
+> * Spaces //do not work// in the context of Remarkup in Phabricator. Hence we should avoid spaces in tag/project names. Make spaces become underscores.
+
+Phabricator converts automatically spaces in project names into underscores in their corresponding hastags in Remarkup. For what is worth, it even ignores the case style (while names with dashes/underscores seem to be case sensitive, one annoyance more to consider): 
+
+  #Wikimedia_Phabricator_Day_1, #Developer_Hub, #Human_Resources, #Trusted_User_Tool
+  #wikimedia_phabricator_day_1, #developer_hub, #human_resources, #trusted_user_tool
+  #WikImediA_pHabRicator_DaY_1, #deVELoper_HUB, #HUMAN_resources, #trustEd_User_tOoL
+renders as
+ #Wikimedia_Phabricator_Day_1, #Developer_Hub, #Human_Resources, #Trusted_User_Tool
+ #wikimedia_phabricator_day_1, #developer_hub, #human_resources, #trusted_user_tool
+ #WikImediA_pHabRicator_DaY_1, #deVELoper_HUB, #HUMAN_resources, #trustEd_User_tOoL 
+
+Therefore, substituting spaces with underscores in project names doesn't add anything apart from the inconvenient case sensitivity and the lack of tokenization.
+
+Also note that the labels above look visually good and feel human, natural. Put the underscores between words, and it will look like computer generated text with a slightly broken UI (like a string without localization). Project names are visible everywhere in Phabricator. If they look nice, our Phabricator will look nicer.
+
+> (Underscores however are not tokenized (yet), same problem for dashes in https://secure.phabricator.com/T5727.) I don't see this as a big issue for type-ahead in the Project field. If some consider it, it is fixable.
+
+Tokenization works fine with spaces in projects names.",1410485028,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-07-30 18:11:30 (UTC)`
+
+We have two aspects and we've mixed them up so far. My fault.
+1) Migrating data from Bugzilla to Phabricator, in a consistent way, via a script. That's T423.
+2) Fixing some of Bugzilla's product and component taxonomy. For example, ""MediaWiki extensions"" should have never been a product in Bugzilla as it's not ""one codebase/shared ownership"". Instead, its components should have been products in Bugzilla. A few years too late.
+
+In today's Phab meeting there was pretty much agreement on:
+* Fix Bugzilla's broken taxonomy //after// migrating, instead of trying to cover and fix lots of cornercases in the migration script itself. (Not sure if we can (mass-)rename via API. If not, I'll spend a long night on coffee.)
+* Convert forward slashes like in ""General/Unknown"" to underscores or just drop the part after the slash, because slashes would break project URLs. There are 15 components affected in Bugzilla.
+* Spaces //do not work// in the context of Remarkup in Phabricator. Hence we should avoid spaces in tag/project names. Make spaces become underscores. (Underscores however are not tokenized (yet), same problem for dashes in https://secure.phabricator.com/T5727.) I don't see this as a big issue for type-ahead in the Project field. If some consider it, it is fixable.
+* The ""Product Component"" pair in Bugzilla should become ""Product:Component"", with a colon as separator. (And I just renamed two components in Bugzilla to not include colons.)
+* As Bugzilla's keywords and ""Product Component"" pairs will be in the same namespace in Phabricator, a Bugzilla keyword becomes a tag, ""Product Component"" becomes a project. These would be two different types and Mukunda said this should not be too hard to fix if I got it right at the end.",1410485028,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**jdforrester** wrote on `2014-07-28 23:59:55 (UTC)`
+
+@qgil's suggestions all make sense to me.
+
+Spaces in project names is a fact of life, but we should discourage it unless it's needed; in general, the first space being a subproject is a neat enough design idea.
+
+My only concern is where we have clashes in name (//e.g.// we used to have Vector the skin and Vector the extension), but I think we can manage our way around those as needed.",1410485028,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-07-28 21:53:35 (UTC)`
+
+I summarized my opinion about this topic at T457#19. In short:
+
+> * Using original project names in Phabricator makes them easier to type and find.
+> * Project names are used as simple tags, except in the case of explicit subprojects of an existing project à la ""Product - Component"". No ""MediaWiki-Extensions-Etc"".
+> * Since projects are proper nouns, by default they use the regular Title Case. Other uses of case are allowed only when the original project name uses them (e.g. GoogleLogin, VisualEditor, MySQL, FOSDEM)
+
+If the VisualEditor team wants to have a ""VisualEditor Data Model"" project, that's fine, but I don't see the usefulness of adding ""MediaWiki Extension"" to the project name. Especially when with the same principle we will add the same string to hundreds of extension projects, ruining type-ahead for any users typing ""MediaWiki"" and/or ""extension""
+
+As the description of this task says, in Phabricator projects are keywords, keywords are projects. Search and type-ahead are essential in Phabricator (and in MediaWiki itself, btw). The tree structure that Bugzilla and Git/Gerrit enforce doesn't need to be replicated here. What's the use? Project naming should focus on proper tagging instead of trying to emulate a tree structure.",1410485027,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Rush** wrote on `2014-07-28 20:47:30 (UTC)`
+
+@aklapper @qgil
+
+I took this to mean that we qgil does not want either categorization or hierarchy in the googlelogin case
+
+> What is important about ""GoogleLogin"" is that users can find it or reference it easily. Therefore the best is to use the name as is.
+
+@qgil can you maybe clarify so we aren't shadow boxing here?",1410485027,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-07-28 19:35:14 (UTC)`
+
+Would love to get feedback from more parties on this:
+
+There have been discussions on project naming schemes with good and valid arguments by all involved parties in T457 but those discussions seems to fit better here to keep T457 focused on //documenting//.
+
+The three main aspects I see mentioned which are intermingled:
+* allowing spaces in project names,
+* expressing hierarchy in project names,
+* ""discoverability"" of existing projects when using type-ahead to make Phabricator list project proposals for matching strings in the ""Projects"" field.
+
+For the fourth and minor aspect of //enforcing lower case names// for projects: Currently, not using a lower case project name would break URL redirecting from e.g. http://fab.wmflabs.org/tag/trusted_user_tool/ to http://fab.wmflabs.org/project/view/40/ . Treating lower and upper case the same way //should be fixed upstream// in https://secure.phabricator.com/T5728 and IMHO we as downstream should not really bother about this.
+
+In order to understand ""discoverability"", here is the current behavior of type-ahead in Phabricator's ""Projects"" field: Type-ahead is not restricted to the very beginning of a project name but to words (tokens). We have a project named ""Wikimedia Phabricator Maintenance (after Day 1)"" in fab.wmflabs.org. If you go to http://fab.wmflabs.org/maniphest/task/create/ and enter ""after"" or ""Day"" in the ""Projects"" field, it will be proposed. It does not match random substrings though - entering ""fter"" does not propose ""after"".
+
+=== Hierarchy or Categories ===
+
+It seems we all agree that we do need some level of organization and rules in that flat Projects namespace, otherwise things will get messy, ambigious, colliding in the long run.
+
+Question is whether we want to express //hierarchy// like ""MediaWiki extension: VisualEditor: Data Model"" or ""MediawikiExtension-VisualEditor-DataModel"" or instead //categorization// like ""VisualEditor: Data Model (extension)"".
+
+The latter feels more readable for the human eye but not sure if that's reason enough.
+
+=== Spaces in Project Names ===
+
+If we did //not// allow spaces in project names, like in ""mediawikiextensions-visualeditor-datamodel"", entering ""datamodel"" in the ""Projects"" field would currently not propose the given project via type-ahead. I consider this problematic as reporters should be able to try entering and finding the correct project, and the first thing they'd try is the actual name, if aware of. On a related note, Chase proposed treating hyphens/dashes the same way as spaces for type-ahead proposals in upstream https://secure.phabricator.com/T5727 (and Evan was in favor on IRC).
+
+If we did allow using spaces in project names, referencing a ""#project name"" in text via the # suffix will not work for these projects, as Chase brought up in http://fab.wmflabs.org/T457#17 , plus entering a URL replacing spaces by %20 HTML entities (instead of underscores) like in http://fab.wmflabs.org/tag/Trusted%20User%20Tool/ will not work.",1410485027,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-07-23 14:54:41 (UTC)`
+
+A note aside: there is an RfC about Bugzilla taxonomy: https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy
+
+We should check which concerns still are relevant in the context of Phabricator, even if here we don't have trees, product-component pairs, and restrictions to file reports only under one product-component.",1410485026,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-07-02 16:20:51 (UTC)`
+
+Refering to differentiating between types of projects (e.g. keywords and components in Bugzilla language), it looks like upstream is going towards project tags. That means that https://secure.phabricator.com/T390 (Implement Project Types) might not gonna happen, but https://secure.phabricator.com/D9709 and https://secure.phabricator.com/T2628 (Add project tags to Pholio, Ponder, Differential, and other applications) instead.
+
+As one example, upstream Phabricator shows a different (kind of transparent) background on umbrella projects now, see e.g. https://secure.phabricator.com/T1205",1410485026,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**Nemo_bis** wrote on `2014-06-15 10:36:47 (UTC)`
+
+> (Phab doesn't list project names first which start with the entered substring).
+
+Doesn't?",1410485025,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-06-12 18:11:33 (UTC)`
+
+>>! In T68#42, @qgil wrote:
+> Let's avoid repetitive mentions to ""Wikimedia"" and ""MediaWiki"". Think again about the side effects this creates in type-ahead when a user starts typing ""Wiki..."" when actually the request is the very licit WikiLove.
+
+Good point, as type-ahead proposals for the Project field always have the alphabetical order of project names it would clutter a lot (Phab doesn't list project names first which //start// with the entered substring).
+""skin"" and ""extension"" implicitly refer to MediaWiki nowadays; crossing fingers it'll stay like this.",1410485025,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-06-11 22:17:57 (UTC)`
+
+I wouldn't patch anything before receiving consistent feedback from real users. I still believe type-ahead will just work as a method, and we might just fix nmes of projects based on what people is not finding easily.
+
+Let's avoid repetitive mentions to ""Wikimedia"" and ""MediaWiki"". Think again about the side effects this creates in type-ahead when a user starts typing ""Wiki..."" when actually the request is the very licit WikiLove.
+
+I would keep keywords as projects. It is easier to get rid of those projects we won't user than to fix missing keywords after the migration.",1410485025,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**jdforrester** wrote on `2014-06-11 18:23:28 (UTC)`
+
+>>! In T68#40, @aklapper wrote:
+> * Please help: What are further potential categories (skins, extensions, tool labs, mobile apps) you can imagine?
+
+I think the main one will be cross-cutting pieces of work, which currently are represented as you say as either:
+* a tracking bug, often in a in poor location
+** //e.g.// ""All repositories should pass jshint test (tracking)"" https://bugzilla.wikimedia.org/show_bug.cgi?id=60619 which is in the component for Wikimedia's CI infrastructure rather than being a cross-tracked ""code quality"" compontent
+* a keyword, often poorly understood, abused or ignored
+** //e.g.// ""shell"" https://bugzilla.wikimedia.org/buglist.cgi?keywords=shell&list_id=321010&resolution=--- which really just means ""deployment rights needed"" and so duplicates the ""Site requests"" component a chunk.
+
+I would suggest that:
+
+* All tracking bugs should be merged into existing projects / components or tasks within a larger cross-cutting project
+* All keywords should become projects (with overlap with the above), or just be killed.
+
+Examples:
+
+* //Code quality// is clearly something we'd want as a cross-cutting project (taking on the tracking bugs around CI/etc.); some keywords (//e.g.// hiphop) would want to be a task underneath this project.
+* //Language support// would replace the i18n and utf8 keywords
+
+> * Keywords like ""community-consensus-needed"" - will that become a column in the //Wikimedia Site Requests// project?
+
+Sounds good to me.",1410485024,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-06-11 16:49:54 (UTC)`
+
+General thoughts:
+We have no hierarchy. Project description text (providing further info/context) is //only// visible on project homepages but not when filing a task.
+We may want to ""patch in"" a link to the list of projects at http://fab.wmflabs.org/project/query/all/ or http://fab.wmflabs.org/project/query/active/ (also see T52) but that's bonus. We may want to patch in an explicit ""Leave Project field empty if you don't know"" on /maniphest/task/create/.
+
+In any case: We need to guess what people would enter into the //Project// field to describe the area they have in mind when creating a new task. Think in search terms attitude. We do have full type-ahead searching for project names available. So we can express alternative names, context, categories in brackets as part of the project name.
+
+James' proposal above is a great start (thanks!). Extending/iterating on this:
+
+* For Wikimedia and MediaWiki products in Bugzilla: By default, try to merge product and component (Bugzilla's ""Wikimedia→Foo"" becomes ""Wikimedia Foo"". ""MediaWiki→Bar"" becomes ""MediaWiki Bar""), or even drop the ""Wikimedia"" product if distinct enough (""Continuous integration"": I hope we'll never get a MediaWiki extension offering that functionality. Yeah, unlikely, but you get the thinking).
+* Categorize specific skins as such: ""Vector (MediaWiki skin)"" / ""Chameleon (MediaWiki skin)""; Skins Bugzilla product got requested in https://bugzilla.wikimedia.org/show_bug.cgi?id=66441
+* Categorize extensions as such, mention alternative names: ""AbuseFilter (MediaWiki extension)""; ""Echo (Notifications; MediaWiki extension)""; ""Popups (Hovercards; MediaWiki extension)""
+* Categorize tools on Tool Labs as such: ""lists (tool on Tool Labs)""
+* Maybe categorize mobile applications as such?
+* (We can always rename projects after Day 1 but would be cool to keep that to a minimum.)
+* Please help: What are further potential categories (skins, extensions, tool labs, mobile apps) you can imagine?
+
+Going deeper / Followup issues at some point: 
+* Browse for / decide on specific conflicts (examples: //i18n// keyword vs //MediaWiki→Internationalization// component; //analytics// keyword vs //Analytics// product; //parser// keyword vs //MediaWiki→Parser// component):
+ * Components: https://bugzilla.wikimedia.org/describecomponents.cgi
+ * Keywords: https://bugzilla.wikimedia.org/describekeywords.cgi
+ * Tracking tickets: https://bugzilla.wikimedia.org/showdependencytree.cgi?id=2007&maxdepth=1&hide_resolved=1
+* Historically (organic growing), we do have quite some duplication between Keywords and Tracking tickets, e.g. //tracking// keyword ∪ //blocking bug 2007//. We should treat tracking tickets as if they were keywords if the blocked ticket itself is not actionable && is not technically blocked on a depending task. (I'll add this in a future comment in T39.)
+* Decide to merge some components (e.g. //WM→Extension setup// ∪ //WM→Site requests//?)
+* Keywords like ""community-consensus-needed"" - will that become a column in the //Wikimedia Site Requests// project?
+* Kill some rather uncommon keywords after wondering whether anybody ever really queries for tickets with those keywords set (e.g. //mobile-lang//, //utf8//?)",1410485024,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**jdforrester** wrote on `2014-05-11 09:31:45 (UTC)`
+
+> Sounds good to me. Ultimately, whoever works on the migration script will request the discrete mapping from Bugzilla products-components to Phabricator projects, with the exact names (or name schema) for each combination. Maybe this is a task on its own?
+
+Yeah, that makes sense; or maybe a ""present the final mapping of fields/values/etc. for comment before running the import""?",1410485024,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-05-11 09:20:26 (UTC)`
+
+Sounds good to me. Ultimately, whoever works on the migration script will request the discrete mapping from Bugzilla products-components to Phabricator projects, with the exact names (or name schema) for each combination. Maybe this is a task on its own?",1410485023,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**jdforrester** wrote on `2014-05-11 08:01:31 (UTC)`
+
+> I don't think we should make project hierarchy a blocker of Day 1, though.
+
+Agreed.
+
+I'd suggest instead some careful implicit hierarchy in naming of like things, and where there are duplicates clear them up with a disambiguating term, but otherwise leave things to be named naturally.
+
+For example:
+* ""MediaWiki"" for MediaWiki core
+* ""Vector"" for the MediaWiki skin (not ""MediaWiki"" > ""Skin and page rendering"" (!))
+* ""Vector (extension)"" for the MediaWiki extension (not ""MediaWiki extensions"" > ""Vector"")
+* ""Continuous integration"" for continuous integration issues (not ""Wikimedia"" > ""Continuous integration"")
+* ""Wikimedia site configuration"" for configuration of Wikimedia's hosted sites (not ""Wikimedia"" > ""Site configuration"")
+* ""VisualEditor"" for VisualEditor core
+* ""VisualEditor MediaWiki integration"" for VisualEditor's MediaWiki integration (not ""VisualEditor"" > ""MediaWiki"")
+
+Thoughts?
+",1410485023,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-05-10 23:40:05 (UTC)`
+
+> I'd strongly recommend having project hierarchies implemented before giving in to the flatness.
+
+Status of project hierarchies feature upstream:
+
+* ~~[[ https://secure.phabricator.com/T333 | Allow projects to have subprojects ]]~~ (Closed, Wontfix)
+* [[ https://secure.phabricator.com/T390 | Implement Project Types ]] (Open since August 2011, Normal)
+
+Looks good and they will eventually implement different types of project hierarchy. I don't think we should make project hierarchy a blocker of Day 1, though.",1410485023,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**parent5446** wrote on `2014-05-10 14:46:10 (UTC)`
+
+As much as naming rules will ""work"" for this, I'd strongly recommend having project hierarchies implemented before giving in to the flatness.",1410485022,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-05-10 09:17:11 (UTC)`
+
+Since Day 1 is defined by the Bugzilla migration, I think we should focus on the projects that would be automatically generated out of that migration. Once we see the situation after 65k tasks have been migrated, we can decide whether this is good enough for Day 1, or we want to fine tune projects before opening the gates for everybody.
+
+A simple proposal for this first iteration:
+
+* Every ""[[ https://bugzilla.wikimedia.org/describecomponents.cgi | Product - Component ]]"" combination is a project.
+* Every [[ https://bugzilla.wikimedia.org/describekeywords.cgi | keyword ]] is a project.
+
+Project names can be edited without causing any disruption, therefore the members of the ""MediaWiki extensions - TorBlock"" project can just rename it to ""TorBlock"".
+
+Good enough for a first decision?",1410485022,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-05-10 09:05:14 (UTC)`
+
+I created [[ http://fab.wmflabs.org/herald/rule/3/ | a Herald rule ]] to add an identified parent project automatically every time a child project is added. Testing this here for the first time right now.
+
+PS: it works.  :)",1410485021,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-05-03 16:56:06 (UTC)`
+
+Another aspect to think about which I run into this afternoon when giving porting my Bugzilla Greasemonkey triagescripts to Phabricator a shot: //Deployed/planned-to-get-deployed vs. 3rd party extensions//, as a random WMF triager has more interest in making sure that bug reports on extensions which are more relevant to WMF (=deployed on WMF servers) get handled sufficiently. Differentiation isn't currently done in Bugzilla either. I do differentiate though in my (client-side) Greasemonkey script for Bugzilla, by dully comparing component name strings against a hardcoded list (not cool, I know).
+
+As a task can have more than on project in Phabricator, something less cumbersome could be having a general ""MediaWiki extension"" product and an additional ""Deployed on WMF servers"" project, but only //if// this could be automatically set via a ""if task in Project A, also automatically add Project B"" rule, and if this differentiation isn't considered visual overkill making the ""Projects"" field too noisy. Don't know yet either.",1410485021,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-04-18 17:26:18 (UTC)`
+
+I don't think it is messy at all. It is just different of the (inflexible and problematic) hierarchy of products and components in Bugzilla.
+
+We have well defined items out there: products usually tied to code repositories (VisualEditor, Flow, PyWikiBot...), Wikimedia projects (en.wiki, Commons...), Bugzilla keywords (i18n, design, shell...), and we have the current Bugzilla taxonomy, of course.
+
+We could start with this, and see what happens. Tasks filed without a project specified might show lazy users... and might show also gaps in our current taxonomy. And, as said, users will create also projects, which is another way to provide feedback.
+
+If we agree on the basic idea, we can start thinking on the specific case of the Bugzilla migration.",1410485021,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-04-18 17:10:08 (UTC)`
+
+◀ Merged tasks: T54.",1410485020,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-04-18 08:39:30 (UTC)`
+
+Git repositories, useful Bugzilla keywords (assuming we use keywords instead of dependencies to express the relation of a task to a certain area), and Bugzilla components when one repository is big/complex enough that it needs subareas for developers to find stuff that they work on. Sounds a bit messy, I know...",1410485020,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-04-17 21:45:05 (UTC)`
+
+In practice this means that we would create the initial list of projects based on... Bugzilla components? Git repositories? ",1410485020,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**qgil** wrote on `2014-04-17 19:01:35 (UTC)`
+
+Also relevant: T54#9",1410485019,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Decide how to organize projects,"**aklapper** wrote on `2014-04-10 21:15:27 (UTC)`
+
+AFAIK there's no separate keyword concept in Phabricator, so if we don't want code changes, keywords would become projects (as tasks can have more than one project). In a kind of way that's even more consistent, as current Bugzilla keywords like ""accessibility"", ""i18n"" or ""easy"" could be considered projects across projects too, and Phabricator's Advanced Query allows AND and OR queries for the Projects field. 
+
+I expect a few people to complain about missing free-form tagging (in Bugzilla: globally visible ""Status Whiteboard"" and private ""Tags"" field) though. Translating this functionality to Phabricator terminology, I'd probably call it ""private projects"" if a user could define her/his own projects only visible to her/him in the project field, e.g. via a prefix being the username in Phabricator so they'd be easy to find via the autocomplete (type ""aklapper"", find ""aklapper-moreinfo"" and others and have these items only be available and visible to the user ""aklapper"" in the projects field).
+Damn, I didn't plan to propose an implementation, but I guess I just did.",1410485019,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-6tvdmfknnn6daqnwcthv,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"Which features would Trello users really miss? If you are not sure whether feature X is supported, under development, roadmapped... just ask. Let's create new subtasks for features considered blockers.",1396569879,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gm3iscenilyd5pim7stg,task_description,resolved
+Identify features Trello users would miss in Phabricator,"@spage 
+
+I think porting trello checklists into this type of checklist is acceptable for a migration, but it is definitely something that people will miss ( actual interactive checklists) ",1417739912,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,">>! In T21#305, @connorshea wrote on `2014-04-22 01:43:08 (UTC)`
+> 
+> As far as I can tell, there's no checklist functionality in Phabricator. There are numbered lists, but that isn't particularly convenient in comparison to the checklist functionality of Trello.
+
+If you make the items subtasks, then Phabricator tracks them in **Blocked by**.
+
+If you want an internal checklist, [[ https://secure.phabricator.com/book/phabricator/article/remarkup/ | Phabricator's ""Remarkup""]] turns `[]` and `[x]` at the start of a line into a checklist:
+[x] buy eggs
+[] scramble eggs
+
+The task's ""card"" in the Phabricator workboard doesn't show an indicator there's a checklist or a ""2/6"" completion count next to it, and the single task view doesn't show a ""33%"" progress bar under the checklist. The latter I think is simply client-side JavaScript. I don't find any of these indicators particularly useful, but T1141 covers them.",1417741277,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,">>! In T21#305, @connorshea wrote on `2014-04-22 01:43:08 (UTC)`
+> 
+> As far as I can tell, there's no checklist functionality in Phabricator. There are numbered lists, but that isn't particularly convenient in comparison to the checklist functionality of Trello.
+
+If you make the items subtasks, then Phabricator tracks them in **Blocked by**.
+
+If you want an internal checklist, [[ https://secure.phabricator.com/book/phabricator/article/remarkup/ | Phabricator's ""Remarkup""]] turns `[]` and `[x]` at the start of a line into a checklist:
+[x] buy eggs
+[] scramble eggs
+
+The task's ""card"" in the Phabricator workboard doesn't show an indicator there's a checklist or a ""2/6"" completion count next to it, and the single task view doesn't show a ""33%"" progress bar under the checklist. The latter I think is simply client-side JavaScript. I don't find any of these indicators particularly useful.",1417739764,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,//importing issue status//,1410484891,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**qgil** wrote on `2014-04-30 23:49:39 (UTC)`
+
+The current list of subtasks seems to be accurate. No blockers have been identified. Some missing features would make our life easier and nicer, but the integration with bug reporting and code review would pay off.
+
+If there are relevant Trello features not listed here, please add them as subtasks.
+
+Resolving this task. Your attention is welcome especially in the subtasks above, {T238}, and {T61}.",1410484890,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**qgil** wrote on `2014-04-28 06:15:27 (UTC)`
+
+After reading all the current a previous feedback related to the RfQ, including [[ https://blog.wikimedia.org/2014/04/15/agile-and-trello-the-planning-cycle/ | Tomasz's recent blog post ]], I cannot find any blocker due to Trello features missing in Phabricator. Trello does perform better in its territory, but I couldn't find anything that would outweigh the benefits of moving to one single open source tool hosted in Wikimedia servers and integrated with bug reporting and software development. The missing features reported could be contributed locally and/or upstream, if we would really need them.
+
+Do you agree with this? If you see any Trello related blocker, please highlight it.",1410484890,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**mattflaschen** wrote on `2014-04-24 21:18:33 (UTC)`
+
+> Is this provided by the mobile app or the web? In Phabricator you can check your notifications in mobile, but you have to click the ""flame"" button (or your mailbox) to find out. Which minimum improvement would you welcome in this direction?
+
+""Push notifications"" means there is no need to check.  I don't use Trello notifications (though I know other people do).  However, the general idea of push notifications is that the notification is sent directly to your phone, and it typically buzzes or beeps, similar to if you received a text (of course, this depends on your phone configuration).  Then, you check a notification list on your phone.  So there is no need to keep opening the app or mobile web site until you get notified.
+
+> The ability to develop a product roadmap (as opposed to just a task list/project management tool) using a board.
+
+This might be doable by just having a separate workboard for the roadmap.
+
+> Easy customization. The labels/task columns/themes/ etc. are so easy to change at a whim.
+
+Phabricator does let you change the task columns freely (and per-workboard), albeit a different UI from Trello.
+",1410484890,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**qgil** wrote on `2014-04-24 21:06:49 (UTC)`
+
+Important question for Trello users:
+
+**If you could get one thing  implemented in Phabricator tomorrow, only one thing, which one would that be?**
+
+As commented in {T44}, there is currently a mess of Mingle/Trello features being requested without a clear ranking of priorities. Let's focus on Trello first. And let's focus on what matters most. 
+
+Feel free creating cards for any of the tasks below, or just comment here with more details, and I will do it.
+
+> Real-time collaborative updating (it's an amazing way to task an issue without copying the breakdown work back and forth between tools)
+
+What does this mean in terms of features missing in Phabricator?
+
+> Great mobile support. Trello gives me push notifications for a board/card I am following. 
+
+Is this provided by the mobile app or the web? In Phabricator you can check your notifications in mobile, but you have to click the ""flame"" button (or your mailbox) to find out. Which minimum improvement would you welcome in this direction?
+
+> The ability to develop a product roadmap (as opposed to just a task list/project management tool) using a board.
+
+Could you link to an example, please?
+
+> Easy customization. The labels/task columns/themes/ etc. are so easy to change at a whim.
+
+What specifically do you miss most in Phabricator? When you say the ""theme"", do you mean the design of the cards or the UI in general?
+
+> Team independence and control over task management styles.
+
+How specifically do you see your workflow is conditioned by general policies or settings in Phabricator? Interesting and possibly related link upstream: [[ https://secure.phabricator.com/T390 | Implement project types ]].
+
+> Markdown
+
+Well, ok, although the toolbar makes the syntax irrelevant in basic usage. Is there any difference that really annoys you? See {T165}.
+
+> A pretty interface
+
+Understood, but the starting point is very decent, especially considering that the same team members that enjoy the beauty of Trello have to spend several hours in Bugzilla and Gerrit. Therefore, the total percentage of UI beauty vs ugliness would ultimately increase.  ;)  Please create tasks for the specific features you think we should push upstream.",1410484889,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**kevinator** wrote on `2014-04-22 15:31:49 (UTC)`
+
+I logged a bug (er task) because I believe task titles should not get truncated in the Workboard View.  Trello wraps titles and makes its cards taller to accommodate for long titles.  
+http://fab.wmflabs.org/T195
+",1410484889,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**connorshea** wrote on `2014-04-22 01:43:08 (UTC)`
+
+As far as I can tell, there's no checklist functionality in Phabricator. There are numbered lists, but that isn't particularly convenient in comparison to the checklist functionality of Trello.",1410484889,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**swalling** wrote on `2014-04-11 00:42:53 (UTC)`
+
+Here's a list off the top of my head:
+
+- Great **mobile** support. Trello gives me push notifications for a board/card I am following. The mobile website + email for Phabricator is a workable but not perfect replacement. 
+- The **ability to develop a product roadmap** (as opposed to just a task list/project management tool) using a board. Ultimately this is a ""nice to have"" feature and we can easily switch to using another tool like MediaWiki. 
+- **Easy customization**. The labels/task columns/themes/ etc. are so easy to change at a whim. It really support ongoing refinement of a team's project management toolkit, in an agile fashion. 
+- **Team independence and control** over task management styles. Each team also has a high degree of independence, since settings can be different across boards. Once we all move to Phabricator there is more interdependence between project management styles across teams. 
+- **Markdown** Phrabricator has some weird mix of Markdown and MediaWiki-like syntax which we will all have to learn. Trello just formats with Markdown. 
+- **A pretty interface** Trello has a nice clean friendly UI. Enhancements like turning image attachments in to covers for tasks, setting stickers, emoji, and more are all features that make a task management system more fun and easy. We //really need// to continue to support memes and other fun interface elements of Phabricator to achieve parity here. Turning on serious business mode is not fun!
+
+To expand, here's a list of **things I //won't// miss** about Trello:
+
+- No dependencies. You can only manually list dependencies in Trello.
+- Not easy for community members to use. You have to login to a third party site to use it, and it clearly is not a Wikimedia-run tool, which scares community/volunteer participants away. 
+- Paying for Business Class license. This costs a (small) fee for the WMF. ",1410484888,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**swalling** wrote on `2014-04-11 00:12:19 (UTC)`
+
+@kevinator have you seen the board view of Phabricator task lists? We have customizable boards like that now, such as [[ http://fab.wmflabs.org/project/board/1/ | VisualEditor test board ]]. You can find it via ""Workboards"" on any project. ",1410484888,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**kevinator** wrote on `2014-04-11 00:02:31 (UTC)`
+
+found this on quora:
+http://www.quora.com/Phabricator/If-you-had-to-choose-between-Phabricator-or-Pivotal-Tracker-what-would-you-choose-and-why
+
+Here's what I love about trello:
+
+Where cards appear on the screen has meaning (column denotes stage, top is importance).
+It's easy to move things around.",1410484888,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+Identify features Trello users would miss in Phabricator,"**milimetric** wrote on `2014-04-09 00:01:51 (UTC)`
+
+  - Real-time collaborative updating (it's an amazing way to task an issue without copying the breakdown work back and forth between tools)
+
+",1410484887,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-gm3iscenilyd5pim7stg,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Paste the following table (or any table from a non-Mediawiki source) into VE. While in edit mode, it will look fairly normal, with borders and a grey background for header cells (due to VE's own style rules). But after the page is saved, it will appear in read mode without any borders or background.
+
+| Animal | Ferocity | Cuddliness
+| ------- | ---------- | -------------
+| Bunny | 0 | 9
+| Cat | 4 | 10
+| Tiger | 10 | ? 
+ 
+{F25893} 
+
+This is because pasted tables do not get `class=""wikitable""` which provides the normal table styling.
+",1419983289,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-eo27t627sh27uj66uxst,task_description,resolved
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Change 265812 merged by jenkins-bot:
+Follow-up I9714cf3: Add tests for wikitable paste
+
+[[https://gerrit.wikimedia.org/r/265812]]",1453494073,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Change 265812 had a related patch set uploaded (by Esanders):
+Follow-up I9714cf3: Add tests for wikitable paste
+
+[[https://gerrit.wikimedia.org/r/265812]]
+",1453493669,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Change 265785 merged by jenkins-bot:
+MWTableNode: Apply wikitable class to pasted tables
+
+[[https://gerrit.wikimedia.org/r/265785]]",1453489842,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","Change 265785 had a related patch set uploaded (by Esanders):
+MWTableNode: Apply wikitable class to pasted tables
+
+[[https://gerrit.wikimedia.org/r/265785]]
+",1453488324,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","I just got bit by this while helping some folks copy over existing information from a Word document. 
+
+Perhaps a solution would be to allow tables to have a modal like Media and Templates where one could click to bring up a window to make configuration changes to the table? One option could be to apply styles - directly by class name or perhaps language indicating ""with borders"" or some such. Less ambiguity in the language is better for editors unfamiliar with language such as ""class=wikitable"" but also understandably more difficult to implement consistently.
+
+Or, conversely (and I can't believe I'm taking inspiration from Microsoft Word) upon paste there is a modal to ask editors 'match default style' or ""keep existing style""?
+
+Tables created in VE-MW do get class=""wikitable"" applied by default, correct?
+
+",1449855907,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",Question: Are we //stripping// any table classes these days?,1453286581,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",Question: Are we stripping any table classes?,1447410555,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","So it sounds like `.wikitable` is, in fact, just one style out of many. So I think task will remain limited to what it says in the title: automatically give pasted tables `class=""wikitable""` in VisualEditor-Mediawiki.",1436215566,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">>! In T85577#1379805, @Neil_P._Quinn_WMF wrote:
+> In fact, I'd go further and ask why Vector doesn't style all tables like this by default? In the rare cases when people actually want the default style, //that// could be applied using a class. 
+
+fwiw... The use of `.wikitable` is relegated almost exclusively to discussions and help pages on Wikisource at best -- where the last thing we want is a table that renders //nothing// like the ones found in works we're transcribing.
+
+Go ahead and make it the default for VE but please provide a way to override/usurp that or it will just wind up as another never-used dialog in our case.",1435211161,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">>! In T85577#1398663, @Izno wrote:
+>>>! In T85577#1379898, @Jdforrester-WMF wrote:
+>> It's important to note that we only want this to be the case in VE-MW, not VE-core. :-)
+> 
+> Last I checked .wikitable ships in core. Am I crazy, or is there some other reason why not?
+
+You're not crazy, it's just that the naming is confusing :). ""VE-core"" (VisualEditor core) is a rich text editor independent of MediaWiki. ""VE-MW"" (VisualEditor MediaWiki) is what everyone knows as **the** VisualEditor, the extension to MediaWiki. We want this behavior in VE-MW, but not VE core.
+
+
+>>>! In T85577#1380307, @Neil_P._Quinn_WMF wrote:
+>>>In fact, I'd go further and ask why Vector doesn't style all tables like this by default? 
+>> 
+>> To answer my own question, it's probably that this would break tables used as a poor man's layout tool by Mediawiki editors
+> 
+> These very rarely, if ever, occur in mainspace on en.wp. Probably rare on the other wikis. Why doesn't someone do the research of getting a dump of mainspace of x or y or z MW wikis and look for tables without the class assigned?
+
+We wish :) https://en.wikipedia.org/wiki/San_Francisco has 39 `table` elements without the `wikitable` class. This includes the infobox, some nested infobox bits which have their own tables, all the navboxes, all the maintenance templates, assorted templates which generate infobox-like or thumbnail-like structures, and some other bits and pieces.",1435195599,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">>! In T85577#1379898, @Jdforrester-WMF wrote:
+> It's important to note that we only want this to be the case in VE-MW, not VE-core. :-)
+
+Last I checked .wikitable ships in core. Am I crazy, or is there some other reason why not?
+
+>>! In T85577#1380307, @Neil_P._Quinn_WMF wrote:
+>>In fact, I'd go further and ask why Vector doesn't style all tables like this by default? 
+> 
+> To answer my own question, it's probably that this would break tables used as a poor man's layout tool by Mediawiki editors
+
+These very rarely, if ever, occur in mainspace on en.wp. Probably rare on the other wikis. Why doesn't someone do the research of getting a dump of mainspace of x or y or z MW wikis and look for tables without the class assigned?",1435193161,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",I've asked at https://en.wikipedia.org/wiki/Help_talk:Table#Where_is_class.3Dwikitable_not_used.3F,1434674736,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">In fact, I'd go further and ask why Vector doesn't style all tables like this by default? 
+
+To answer my own question, it's probably that this would break tables used as a poor man's layout tool by Mediawiki editors",1434662558,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","It's important to note that we only want this to be the case in VE-MW, not VE-core. :-)",1434657142,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","I agree with @Quiddity. From the user's perspective, `wikitable` styling //is// how Mediawiki tables look. We should definitely apply `class=""wikitable""` automatically. 
+
+In fact, I'd go further and ask why Vector doesn't style all tables like this by default? In the rare cases when people actually want the default style, //that// could be applied using a class. ",1434655792,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW",">>! In T85577#1105146, @Catrope wrote:
+> This is ""correct"" behavior: tables in MW read mode do not have borders unless `class=""wikitable""` is explicitly set. Perhaps pasted tables should automatically get `class=""wikitable""`, like newly created tables do?
+
+I believe that would be good. All tables I've ever seen in articles use this (or more complex) styling, and it's used almost everywhere in https://www.mediawiki.org/wiki/Help:Tables",1434587068,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+"Automatically give pasted tables class=""wikitable"" in VE-MW","This is ""correct"" behavior: tables in MW read mode do not have borders unless `class=""wikitable""` is explicitly set. Perhaps pasted tables should automatically get `class=""wikitable""`, like newly created tables do?",1426005863,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eo27t627sh27uj66uxst,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,"Seen as both anon and while logged in: 
+
+Edit any page at http://en.wikipedia.beta.wmflabs.org
+
+Use insert menu to insert almost anything: I had the same experience with Formula, Table, and Media. 
+
+Save the page after inserting the element. 
+
+After save, click the wikitext edit link, whether logged in or anonymous.  Nothing happens. 
+
+I see no javascript errors when clicking the wikitext edit, but I do see a warning on saving the page in VE, but I'm not sure it's relevant: 
+
+ load.php:61
+""Invalid _currentGuiderID.  Returning early"" load.php:153
+console.trace(): load.php:154
+mw.log</log.warn() load.php:154
+transition/<()",1419973179,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-2fasjdalcvfhpa6dgghm,task_description,resolved
+Edit source link broken after editing the page with VisualEditor,Checked in betalbs - Edit source works after VE Save.,1420491349,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,"Change 181679 merged by jenkins-bot:
+Don't break ""Edit source"" link after VE has closed
+
+[[https://gerrit.wikimedia.org/r/181679]]",1420464524,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,"I just saw the patch, thanks!",1419973731,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,Sounds like this is something I already spotted and uploaded a patch for.,1419973665,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Edit source link broken after editing the page with VisualEditor,"Change 181679 had a related patch set uploaded (by Alex Monk):
+Don't break ""Edit source"" link after VE has closed
+
+[[https://gerrit.wikimedia.org/r/181679]]
+
+#patch-for-review",1419973626,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2fasjdalcvfhpa6dgghm,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"Seen in Firefox and Chrome: 
+
+Edit any page in VE, e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click Insert/Template
+
+The input text field briefly shows a cursor and a blue bar indicating that the element has focus, but then the focus disappears. User should be able to type directly into text field without needing to click the text field element first, but no longer can. 
+
+This is the failure at https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/423/testReport/(root)/VisualEditor%20Transclusion/Add_parameter_to_template/",1419893532,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-xtbmxjggz7gkbjodpajo,task_description,resolved
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"On Firefox 35 Mac, I am editing Wikipedia with the Visual Editor.
+
+By habit, I type ""{{cit"". This brings a dialog for choosing a template with one field for typing the name. But the ""cit"" went nowhere. And typing the name does nothing. I have to click in the field first. It would be nice to have the focus in the field. Thus, when we type, by habit, ""{{cit"", the characters ""cit"" would go in the field for the template name.
+
+Thank you.
+",1423492732,PHID-USER-fjve3gq5wsmaaccti7pb,False,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,Fixed/checked in beta.,1422565427,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"Change 186505 merged by jenkins-bot:
+Focus the add template input in the template dialog
+
+[[https://gerrit.wikimedia.org/r/186505]]",1422069884,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"Change 186505 had a related patch set uploaded (by Mooeypoo):
+Focus the add template input in the template dialog
+
+[[https://gerrit.wikimedia.org/r/186505]]
+
+#patch-for-review",1422050824,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,Duplicate to https://phabricator.wikimedia.org/T86040,1420664997,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,"Still happening for me - Mac - betalabs FF, Chrome and Windows7 IE. ",1419962342,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Insert/Template inspector should put focus on input text_field when invoked but no longer does,This no longer happens,1419959811,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-xtbmxjggz7gkbjodpajo,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"As a logged in user with access to VE in MobileFrontend, bring up a random page and click the pencil icon to edit with VE e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/0.6922277312143298#/random. 
+
+Note that in the upper left, the back-arrow icon ""escape"" button appears before the other controls. 
+
+Click the back-arrow escape icon as the page loads, before the page is finished loading. Nothing happens. 
+
+This is the failure at https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/455/testReport/(root)/VisualEditor%20Mobile/Going_back_from_save_screen_in_VisualEditor/",1419890942,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_description,resolved
+Back arrow appears before other VE controls in MobileFrontend but does nothing,Verified the fix in en.wiki,1421363585,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,Verified the fix in Betalabs and test2,1420605576,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"https://gerrit.wikimedia.org/r/#/c/181698/ also needs to get deployed.
+",1420562666,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"I stand corrected, this is now fixed in master. The error above is in wmf13, so we seem to have missed another patch that should be cherry-picked.",1420562558,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"`Uncaught TypeError: boolean is not a function in Overlay.extend.hide`
+
+ It's trying to call `this._hasChanged()` , while `this._hasChanged` is a boolean property (set to true). Appears to be related to https://gerrit.wikimedia.org/r/#/c/182113/ , which was cherry-picked to wmf13 but doesn't seem to have solved everything.",1420561914,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Back arrow appears before other VE controls in MobileFrontend but does nothing,"```Uncaught TypeError: boolean is not a function in Overlay.extend.hide```. It's trying to call ```this._hasChanged()``` , while ```this._hasChanged``` is a boolean property (set to true). Appears to be related to https://gerrit.wikimedia.org/r/#/c/182113/ , which was cherry-picked to wmf13 but doesn't seem to have solved everything.",1420561885,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-o2wsm7xh6lrm5c2z6lwk,task_subcomment,NA
+Lua error: too many language codes requested,"When trying to assemble the December's issue of VE multilingual newsletter,
+I got this message after [[ https://meta.wikimedia.org/w/index.php?title=VisualEditor%2FNewsletter%2FSandbox&diff=10833033&oldid=10815060  |  this edit ]] (I guess LUA can't actually handle so many languages. If I'm right, this needs to change - 20-something languages aren't ""many"" at all.)
+
+More info:
+
+Backtrace:
+[C]: in function ""isRTL""
+mw.language.lua:99: in function ""isRTL""
+mw.language.lua:132: in function ""getDir""
+Module:Assemble_multilingual_message:46: in function ""chunk""
+mw.lua:490: ?",1419877407,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_description,resolved
+Lua error: too many language codes requested,Wouldn't it be nice to automatically set the value of whether manual recache is enabled or not? Hopefully things will be faster when we start hitting the 200 languages limit :),1526991905,PHID-USER-732lqsmz4v6bss3kln2v,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Change 430068 **merged** by Tim Starling:
+[operations/mediawiki-config@master] Raise Scribunto maxLangCacheSize to 200
+
+[[https://gerrit.wikimedia.org/r/430068]]",1526813253,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Change 430068 had a related patch set uploaded (by Anomie; owner: Anomie):
+[operations/mediawiki-config@master] Raise Scribunto maxLangCacheSize to 200
+
+[[https://gerrit.wikimedia.org/r/430068]]",1525183146,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"I just run into this issue again at https://commons.wikimedia.org/wiki/Module_talk:Name/testcases Maybe some functions do not need to be in the language objects, like: mw.language:isRTL or mw.language:lc. 
+
+One consequence of this error is that lua code writers avoid calling mw.language functions and use  frame:callParserFunction instead. For example [[ https://commons.wikimedia.org/wiki/Module:Date| c:Module:Date]] (used on 46M pages) uses `datestr = mw.getCurrentFrame():callParserFunction( ""#time"", { dFormat, timeStamp, lang } )` instead more logical `datestr = mw.language.new(lang):formatDate( dFormat, timeStamp) `. The output is the same except for no ""Lua error: too many language codes requested"".  From performance point of view, is there a difference between mw.language.new(lang) and mw.getCurrentFrame():callParserFunction calls?",1525181352,PHID-USER-j4jntnatcouoxfrk74sh,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Change 343590 merged by jenkins-bot:
+[mediawiki/extensions/Scribunto@master] Make the maximum language cache size configurable
+
+[[https://gerrit.wikimedia.org/r/343590]]
+",1490279834,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Alright @Elitre, I wrote the patch for option 2. https://gerrit.wikimedia.org/r/#/c/343590/",1489979106,PHID-USER-k6tmz5ylx4rzfl3bitse,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Change 343590 had a related patch set uploaded (by Tim Starling):
+[mediawiki/extensions/Scribunto] Make the maximum language cache size configurable
+
+[[https://gerrit.wikimedia.org/r/343590]]
+",1489979057,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,Thanks Tim. What needs to be done here? Do we need to involve someone in particular in this conversation? (I'd really love to be able to deliver the next visual editor newsletter into more than 20 languages.),1489592232,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"IIRC my concern was that there was no eviction from the cache in LocalisationCache::$data, which continues to be the case. If recaching is required, memory usage is about 1.5MB per language, measured locally today. So a limit of 20 implies 30MB, which seems reasonable compared to the Lua memory limit of 50MB.
+
+However, in the WMF production setup, l10n recaching is done in advance, so there's no way recaching would be done in response to a Lua request. It only needs to load the preloaded messages plus the data actually requested (isRTL). Using eval.php on a production server, I measured 145KB per language, which is not so concerning.
+
+So I think the options are:
+# Fix LocalisationCache so that it doesn't use unlimited amounts of memory when recaching on demand. Implementation ideas can be found in LocalisationCacheBulkLoad.
+# Make MAX_LANG_CACHE_SIZE configurable and set it to say 200 on WMF, leave it at 20 by default. We would probably need to add ScribuntoEngineBase::getOptions() so that Scribunto_LuaLanguageLibrary::register() can get access to the configuration options, which are stored in a protected variable.
+# Increase the default MAX_LANG_CACHE_SIZE very modestly, say to 30. This seems like a bad choice since in a month or two someone will reopen the same bug, having found a really important use case for loading 31 languages.
+
+Somewhat off topic, but speaking of lightweight Language object construction, I think having $wgLangObjCacheSize = 10 by default is actually bit rot, I don't think there's any reason for that anymore. Language objects used to hold message arrays, presumably that is the reason for it being so low.",1489556381,PHID-USER-k6tmz5ylx4rzfl3bitse,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Would it be feasible to raise the cap to, say, 30 languages (although that's a limit the VE newsletter has already crushed at least once) and see how it goes?",1485854372,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"This seems to go back to the issue that constructing language objects was slow and memory consuming. The most likely culprit was the preloading a big set of language data and some messages every time a language object was constructed. But I was under the impression that this has been improved enough a long time ago, so maybe the restriction in Lua is not necessary anymore. Or if it turns out there are still issues, Language object construction should be made light-weight.",1485853303,PHID-USER-732lqsmz4v6bss3kln2v,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,Yes.,1460741037,PHID-USER-go2ym6ta2zn6ofdsrqnx,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"@johan, I gather this is a problem you may also have at some point.",1457976468,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"This limit is also why Commons template:Dir (https://commons.wikimedia.org/wiki/Template:Dir ), which is the most transcluded template on Commons (with 32,721,515 pages transcluding it) is not using Lua's ""isRTL"" function. ",1436464033,PHID-USER-j4jntnatcouoxfrk74sh,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Thank you, Anomie! The VE newsletter is quite popular, so I'd really like to get rid of the restriction somehow if possible (/bragging).",1419885375,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,">>! In T85461#947512, @Elitre wrote:
+> Has this never occurred for Tech News?
+
+No, we've never had so many translations in Tech News.",1419881226,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"I note the restriction was added by Tim (see [[https://gerrit.wikimedia.org/r/#/c/36496/|Gerrit change 36496]], which was the original source of [[https://gerrit.wikimedia.org/r/#/c/42050/|Gerrit change 42050]] that was actually merged), so adding him as a CC here.",1419880981,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,"Thanks, Guillaume. Splitting the page doesn't seem very feasible though - one would have to split recipients' lists as well, and maintaining them... doesn't really look sustainable. Has this never occurred for Tech News?",1419880694,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+Lua error: too many language codes requested,See also https://www.mediawiki.org/wiki/Extension_talk:Scribunto/Lua_reference_manual#Lua_error:_too_many_language_codes_requested.,1419879839,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-uwqdkdxx5tmkmhzfjwvz,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","The first time I open a link inspector using ""[["", Ctrl-K, or the toolbar button, it takes about 5 seconds on my laptop. The subsequent times I do it in the same editing session it opens immediately.",1419347942,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_description,resolved
+"the first time that the VisualEditor link inspector appears, it takes a very long time","Awesome, thanks.",1420932762,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","What happened is that inspector dialogs no longer use isolation, so my
+guess was probably correct.",1420932545,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","I'm not sure what happened, but I cannot reproduce it on Firefox in the version that is currently deployed in Wikipedia. The link inspector appears immediately.",1420930784,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","What do you know, it's indeed faster on Chrome - about 1.5 seconds.",1419360301,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","I also vaguely recall this having been reported already, but can't find it. I only found T72467, which was actually an entirely separate issue.",1419350684,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","This also happens for me when using Opera 12 (which is somewhat slow compared to more modern browsers). The inspector dialogs are still using isolation (rendered inside an `<iframe>`) and I can reproduce using isolated dialogs in the demo, so that's probably the reason. We're apparently working on killing isolation, though.",1419348629,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+"the first time that the VisualEditor link inspector appears, it takes a very long time","(This may be a dupe. I remember reporting it a few weeks ago, but I cannot find it now.)",1419348170,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-s7lpkaw3xu6zlj3jjwqm,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#Schedule
+Monday 26, 10:30am
+
+@Tfinc is the owner of the Mobile theme at the #MWDS15. He is also in charge of organizing the Mobile plenary session, or find someone to organize it.
+
+meeting notes: http://etherpad.wikimedia.org/p/MWDS2015_multi-device_world",1419267000,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_description,resolved
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,">>! In T85151#1068841, @MZMcBride wrote:
+> Is there a reason this task is still open?
+
+Let's find out.",1424916580,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,Is there a reason this task is still open?,1424915627,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,Please update the description with the achievements of this session. Thank you in advance.,1422341688,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,Etherpad for today: https://etherpad.wikimedia.org/p/MultiDeviceWorld,1422292449,PHID-USER-qmantxp3p7omhisp3qgq,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Currently you have 45 minutes for this plenary session, and right after you have another 45' slot in the main room for a non-plenary session to be defined. If you want to pre-schedule this second session, we need urgently a task describing it. Or perhaps you want to extend this topic, having a short break after the first 45' leading to a discussion among those staying in the room?",1421226727,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Good discussion today about the plenary and focusing it on the challenges of preparing for a multi device world and what technological blockers/opportunities we have. We've done a quick pass on what we'd like to highlight:
+
+* Desktop <-> Mobile convergence
+** Highlight success/challenges of building for both
+* Building mobile-relevant applications
+** Wikirgrok, infoboxes, etc
+* WikiData
+** How recent mobile app work can enable new desktop workflows
+* Editing/Micro Contributions (Gabriel/JonR)
+* What's slowing us down?
+** API availability
+
+Which may change as the week goes on. Over the next days we'll prepare a short plenary on this, room for discussion, and the the relevant breakout sessions.
+
+notes: http://etherpad.wikimedia.org/p/DevSummitMain
+
+
+",1421100694,PHID-USER-qmantxp3p7omhisp3qgq,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Personally I want people to come out of the session with the mind to explore the limitations of our existing software when it comes to editing and challenges these issues.
+
+From Mobile Web perspective, summarising what @Kaldari and I have said I can see the tdlr as
+* People have less time and need new ways to contribute especially on mobile
+* We are exploring new was such as Wikigrok and infoboxes (we could refer to mobile uploads and how that showed a thirst to edit but wasn't the right fit)
+* Editing does not have to be editing a big chunk of text e.g. wikitext/VisualEditor full edit page
+* Take away: How can we do more of this? How can we break down our current editing model using things like wikidata and Parsoid? Let's spend the summit exploring that.
+",1420824213,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Here's a quick outline for a presentation on WikiGrok:
+
+Motivation:
+* Give readers an easy way to make contributions on mobile
+* Help build Wikidata for the semantic future
+* Experiment with game-like contribution methods
+
+History:
+* Magnus's Wikidata Game
+* Consulted Magnus at Wikimania 2014 and built prototypes
+* First working versions October 2014 (A and B versions)
+* Rewrote backend to be scalable
+* Removed dependency on Magnus's Wikidata query API
+* Test for logged in users (December 2014)
+* Test for anonymous readers (January 2014)
+* WikiGrok Roulette (January 2014)
+
+Future:
+* Pick an interface version
+* Push data to WikiGrok
+* Add new campaigns
+* Use to verify existing data or data from other databases
+* New Wikidata query engine for asking better questions
+* Desktop version?
+* More gamification?",1420792533,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Thoughts so far:
+The goal of the native Mobile Apps is to bring the contents of Wikipedia as close as possible to the user's fingertips.  This means:
+1) Integrating more tightly with the OS on the user's device (notifications, widgets, location-based things, etc). This would require things like server-side APIs/infrastructure for push notifications.
+2) Presenting content in ways that the user ""expects"" to see, based on other patterns and behaviors in the mobile OS.  In this vein, Wikipedia content has to become more ""parceled"" into factoids for consumption on mobile. (Thus, an ever-growing dependency on Wikidata)
+We've started to tackle some of #2, with our implementation of Lead Images, as well as the Gallery feature (not to mention Wikidata descriptions throughout the app).  
+We could begin by demoing our work on lead images, and the associated successes and challenges that came out of it.  We'll show a few articles where the lead image looks excellent and really transforms the first-glance experience of the article. We'll also show some articles where the lead image is ""suboptimal"", which would lead to a discussion about face detection for proper alignment of the image, a possible microcontribution for the proper cropping/alignment of the image (or indeed which image to use as the lead image), etc.",1420766517,PHID-USER-pbvnfgskfwsdalhpd7np,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"**Apps! Try all the things!  **
+
+Native apps provide a unique opportunity to showcase Wikipedia media and data, in boundary pushing, even beautiful ways.   
+
+With ""lead image styling"" we've mixed article title, main image and Wikidata descriptions seamlessly at the top of the article.  
+
+With search results, saved pages, recent and nearby items we've incorporated Wikidata descriptions.  
+
+With native article image galleries, users get instant access to a liquid smooth image browsing interface.  
+
+With nearby we've leveraged location awareness and native performance to guide readers to article geodata coordinates.  
+
+APIs for search, nearby and article data were enhanced to return Wikidata descriptions so we didn't have to make separate requests. Other API clients can now do this as well.      
+
+
+
+**Challenges & Opportunities.  ** 
+
+One challenge we encountered with lead image styling was intelligent cropping for constrained lead image presentation. It can be difficult, given widely varying image dimensions, to determine what the ""focal area"" of an image is so we don't crop through it. Happily, apps can performantly determine certain image focal areas, so we don't crop a notable person's face noticeably in half.   
+
+However, there are edge cases. But we see these challenges as opportunities. If apps could hit a ""commons data"" endpoint for images, they could report back apps-detected image focal areas, and apps interfaces for users to curate focal area data would be trivial to implement as well. Then any consumer of commons images could easily perform intelligent cropping. ",1420766288,PHID-USER-ohzzl3maortma7y4znpb,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"@deskana, we'll have a plenary and several other sessions about SOA at the summit. See T85154 and T86028.
+
+I'm not sure yet whether there will be a dedicated evangelization session, but there should be an evangelizing effect in any case.",1420758125,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,">>! In T85151#961900, @RobLa-WMF wrote:
+> 
+> @Maryana, I have heard in meetings the murmurings of putting desktop on hold.  Not from you, and I don't think the suggestion has truly taken root in our planning process, but I believe it's well worth spelling out (or discussing) in a plenary a very general sense of the size and shape of our investment in desktop vs mobile user interface in the next year or two.  I'll grant you that there's no master plan, but I've also heard many intelligent and compelling hunches about what the right strategy is.  
+> 
+> We will probably need to state the (only seemingly obvious) point that it's not a zero sum game where more mobile investment == less desktop investment.  For example, while our work on Wikidata querying (T85159) was motivated by a mobile use case, there is absolutely nothing mobile specific about the service.  In fact, the heart of our strategy almost certainly needs to be minimizing the cases where we are making zero sum tradeoffs.
+
+Investments into creating a service-oriented architecture for our projects is another example of this choice often not being zero-sum; the mobile apps as pure API consumers benefit greatly from having cleanly defined services, but in actuality this benefits any API consumer, and there are plenty of API consumers on desktop! And, although the discussion about front-end standardisation is of prime importance to mobile web and desktop, it's irrelevant for the mobile apps as they use the front-end frameworks and design patterns that come with the iOS and Android SDKs and platforms. So, even that isn't as zero-sum as it appears! :-)
+
+On the topic of service-oriented architecture, Rob raised the astute point that although service-oriented architecture may seem obvious to us at the WMF, it may not be obvious to others. Our developer community is very decentralised, and one of the disadvantages of a decentralised community is that a bit harder to get people to rally around a totally new concept and way of doing things, such as SOA. And since there is clearly a big belief that service-oriented architecture is the future, the developer summit is a prime opportunity to speak to this decentralised community and evangelise service-oriented architecture to them. Is @gwicke planning anything such as this for the summit?",1420736803,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,">>! In T85151#961318, @Maryana wrote:
+> It sounds like these ""mobile skeptics"" you're alluding to assume that WMF has already formulated some big mobile master plan (and perhaps cynically believe it involves ditching desktop development altogether...?),
+
+@Maryana, I have heard in meetings the murmurings of putting desktop on hold.  Not from you, and I don't think the suggestion has truly taken root in our planning process, but I believe it's well worth spelling out (or discussing) in a plenary a very general sense of the size and shape of our investment in desktop vs mobile user interface in the next year or two.  I'll grant you that there's no master plan, but I've also heard many intelligent and compelling hunches about what the right strategy is.  
+
+We will probably need to state the (only seemingly obvious) point that it's not a zero sum game where more mobile investment == less desktop investment.  For example, while our work on Wikidata querying (T85159) was motivated by a mobile use case, there is absolutely nothing mobile specific about the service.  In fact, the heart of our strategy almost certainly needs to be minimizing the cases where we are making zero sum tradeoffs.
+
+However, there are going to be cases where it is zero sum.  Good user interface is messy like that.  We need to have a frank conversation about how much to invest in which area.
+
+> but the reality is that our mobile teams and projects are still very new/emergent, we're still in the exploratory phase with a lot of our work, and there are still many ideas floating around for the directions mobile could go in the future.
+
+I don't think this part needs a great deal of consensus building.  It needs some, because we have a lot of people working on it, and so one could argue we could scale back a little, but that's not the most urgent aspect that requires a big group conversation, and that's not what I was thinking of.
+
+> So I think a ""group alignment conversation"" is a bit premature. It might be better just to provide a space to talk openly about all these possible future directions (mobile as a service! mobile as the one skin to rule them all! mobile as the shiny new unicorn!, etc.), without necessarily forcing any sort of consensus on the process or making it seem like any of these things are going to happen tomorrow ;)
+
+Sure, there are limits to what we can accomplish in one session or even over the course of two days.  Just having the open conversation might be enough.  And, we don't have to ""force"" consensus in any way.  However, I think we should inject some amount of urgency and relevance to the conversation, and aspire to actually get something done by having the conversation.
+
+BTW, as long as we're using quotes here, I am going to have to point out that I did say ""mobile strategy skeptics"" and not ""mobile skeptics""  :-)",1420699618,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,">>! In T85151#961318, @Maryana wrote:
+> It sounds like these ""mobile skeptics"" you're alluding to assume that WMF has already formulated some big mobile master plan (and perhaps cynically believe it involves ditching desktop development altogether...?), but the reality is that our mobile teams and projects are still very new/emergent, we're still in the exploratory phase with a lot of our work, and there are still many ideas floating around for the directions mobile could go in the future.
+
+I'm not sure where you get new/emergent from. MobileFrontend is not new. And there was a completely separate mobile site before it and a completely separate mobile site before that, so we're talking about many years of experience here.
+
+A lot of mobile development has come about as the result of either stripping everything away and slowly and painfully re-implementing it (category links at the bottom of the page is a small example of this) or the result of trying to inject features into mobile first as a means of bypassing what would likely be outright rejection, for better or worse, on desktop (Special:UserProfile and the last edit strapline at the top of the page are two examples of this).
+
+So, scare quotes or not, yeah, there needs to be a discussion about what mobile development has looked like and what it should look like going forward. The cold hard truth is that writing an encyclopedia (or a dictionary or a whatever) on the desktop site continues to be a pretty agonizing process. It's basically currently impossible to do serious editing on a mobile device and may remain so indefinitely, again for better or worse. The best we can probably hope for is optimizing micro-contributions, as kaldari says, and reunifying the desktop and mobile experiences, work on which has thankfully finally started.",1420693651,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,We should definitely have at least one presentation about microcontributions via Wikidata. This would probably show off WikiGrok and possibly the experimental infobox and description editing. I would really like to have Jon's ForiegnApi code (https://gerrit.wikimedia.org/r/#/c/182134/) implemented as a core mediawiki module before then so that people can hack with it in the break-out sessions (on both desktop and mobile). Other possible things to demo include the experimental lead section styling in alpha and the mobile Media Viewer.,1420682543,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"
+
+
+
+
+
+>>! In T85151#961235, @RobLa-WMF wrote:
+> I think we need to have a large group alignment conversation about our engineering strategy around mobile, and what the organization as a whole should be doing.  I repeatedly hear skepticism about the fall of desktop and rise of mobile as a reason to drop what we're doing and have everything be about mobile.  It's not so much skepticism about the fact that it's happening (though there is a little misplaced skepticism there), but cynicism about what that fact is being used to justify.
+> 
+> The temptation on this session would be to ""go with what we know"", which is lots of presentations and demos.  These will be utterly unconvincing and unengaging to mobile strategy skeptics.  I think it likely needs to be a conversation rather than a presentation in order to win over skeptics, but exactly what this looks like is a bit unclear to me.
+
+It sounds like these ""mobile skeptics"" you're alluding to assume that WMF has already formulated some big mobile master plan (and perhaps cynically believe it involves ditching desktop development altogether...?), but the reality is that our mobile teams and projects are still very new/emergent, we're still in the exploratory phase with a lot of our work, and there are still many ideas floating around for the directions mobile could go in the future. So I think a ""group alignment conversation"" is a bit premature. It might be better just to provide a space to talk openly about all these possible future directions (mobile as a service! mobile as the one skin to rule them all! mobile as the shiny new unicorn!, etc.), without necessarily forcing any sort of consensus on the process or making it seem like any of these things are going to happen tomorrow ;)",1420676428,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"I think we need to have a large group alignment conversation about our engineering strategy around mobile, and what the organization as a whole should be doing.  I repeatedly hear skepticism about the fall of desktop and rise of mobile as a reason to drop what we're doing and have everything be about mobile.  It's not so much skepticism about the fact that it's happening (though there is a little misplaced skepticism there), but cynicism about what that fact is being used to justify.
+
+The temptation on this session would be to ""go with what we know"", which is lots of presentations and demos.  These will be utterly unconvincing and unengaging to mobile strategy skeptics.  I think it likely needs to be a conversation rather than a presentation in order to win over skeptics, but exactly what this looks like is a bit unclear to me.",1420674906,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"What are we aiming to achieve in this Mobile plenary session? You will have all the Summit attendees in one room, right after the opening. Which are the key messages you want to push? What do you want from them?
+
+>>! In T85151#959834, @Jdlrobson wrote:
+> explore other ways to edit that are not via the traditional wikitext model.
+> (...)
+> I think essentially the role of mobile is to break down the complicated wikitext markup language that we have built over the last 10 years and encourage our projects to dogfood Wikidata more and make wikitext easy for newbies to understand again.
+
+I wonder how this 'role of mobile' you are describing fits with the role of VisualEditor and the Editing plans altogether. CCing JamesF.",1420649507,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Early thoughts:
+""Think outside the wikitext""(play on think outside the box) In addition to demoing the obvious Wikigrok, in the plenary I would like to propose demoing the Wikidata infobox editing/lead photos in alpha [1]. Although we currently have no plans to productise this and this is an experimentation project, I think it would be a useful thought exercise to imagine a world where we start breaking down wikitext and reducing our dependency on {{template markup}} and explore other ways to edit that are not via the traditional wikitext model.
+
+I'm not sure what the reaction to this will be. For instance if infoboxes were generated from Wikidata and not within the markup how would our existing community react to that? But I'd hope it might polarise the crowd and lead to some interesting conversations going out of it.
+
+I think essentially the role of mobile is to break down the complicated wikitext markup language that we have built over the last 10 years and encourage our projects to dogfood Wikidata more and make wikitext easy for newbies to understnd again. Microedits are proving successful in mobile and we need to find better ways to support that. @GWicke and I have talked about how Parsoid can help do things such as insert citations in place of 'citation needed' text and I'm hoping we can have a session around Parsoid/Mobile in one of the later sessions to continue this theme.
+
+[1] http://en.m.wikipedia.beta.wmflabs.org/wiki/Albert_Einstein?wikidataid=Q937&mobileaction=alpha",1420647216,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Picking this back up now that were all back. 
+
+Tech leads: @kaldari @Dbrant @Mhurd @jdlrobson
+
+We have a 45min plenary that were going to be creating here. I'd like to have your list of topics by Thur of this week to review and be able to run the by Damon on Friday. Each topic should take up 10-20 if your presenting with someone else or 10-15 if your on your own. Out of these we'll need to think about the potential breakout sessions we brainstormed last month [1] and get them on the MediaWiki Developers Summit Schedule [2] 
+
+No need to create slides at this point (or at all if your demoing), keep them at high level bullet points so that we can validate with Damon and move forward. 
+
+If there are others that want to jump in on the planning of this then please let me know.
+
+[1] - http://etherpad.wikimedia.org/p/Mobile-WMDS
+[2] - https://docs.google.com/spreadsheets/d/15pMDR_h84KUTQK7IR95etVJyJBYC5nVxoG9k_9danV0
+",1420586285,PHID-USER-qmantxp3p7omhisp3qgq,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Picking this back up now that were all back. 
+
+Tech leads: @kaldari @Dbrant @Mhurd @jdlrobson
+
+We have a 45min plenary that were going to be creating here. I'd like to have your list of topics by Thur or this week to review and be able to run the by Damon on Friday. Each topic should take up 10-20 if your presenting with someone else or 10-15 if your on your own. Out of these we'll need to think about the potential breakout sessions we brainstormed last month [1] and get them on the MediaWiki Developers Summit Schedule [2] 
+
+No need to create slides at this point (or at all if your demoing), keep them at high level bullet points so that we can validate with Damon and move forward. 
+
+If there are others that want to jump in on the planning of this then please let me know.
+
+[1] - http://etherpad.wikimedia.org/p/Mobile-WMDS
+[2] - https://docs.google.com/spreadsheets/d/15pMDR_h84KUTQK7IR95etVJyJBYC5nVxoG9k_9danV0
+",1420582333,PHID-USER-qmantxp3p7omhisp3qgq,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit,"Current feeling is to have the tech leads from mobile web @kaldari and apps @dbrant @mhurd present on at least 1 and at most 2 products/features that they've shipped over the last 6 months to highlight what's possible on mobile and what is difficult and/or impossible to do. It would be interesting to have @maryana and @deskana weigh in on those too. I'm going to be eager to paint the narrative of opportunity and highlight where we can do better. Especially along API's, services, etc.
+
+We spent some time earlier this week brainstorming some potential sessions to get us started
+
+http://etherpad.wikimedia.org/p/Mobile-WMDS",1419301604,PHID-USER-qmantxp3p7omhisp3qgq,False,PHID-TASK-chdbjfofb5zihbj3xecj,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"{F22740}
+
+This is caused by MobileFrontend setting box-sizing: border-box on every element.",1419112500,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_description,resolved
+Inspector titles clipped in VisualEditor on mobile,"Belay that. now that T86366 is fixed, this is fixed too in master. Thanks!",1429205383,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,Yes. We're waiting for the stalled patch in Mobile to be merged.,1429205322,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Is this still a problem?
+",1429205262,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"I'm waiting for a reply here: https://phabricator.wikimedia.org/T86366#1136772
+",1428450186,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"So I tried VE on mobile using the latest MobileFrontend master with ""Experimental"" (alpha) enabled. It looks to me like it's still getting clipped because of that `height: @icon-size` on `.oo-ui-processDialog-location`?",1428443967,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Change 180775 abandoned by Jdlrobson:
+Remove border-box rule from reset.less
+
+Reason:
+https://gerrit.wikimedia.org/r/183987 is merged now so removing this from the review backlog. We can always restore it later depending on the outcome of that patch. Thanks for your patience.
+
+[[https://gerrit.wikimedia.org/r/180775]]",1422893603,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Change 183987 merged by jenkins-bot:
+Turn off universal box-sizing in alpha
+
+[[https://gerrit.wikimedia.org/r/183987]]",1422665702,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Change 183987 had a related patch set uploaded (by Jdlrobson):
+Turn off universal box-sizing in alpha
+
+[[https://gerrit.wikimedia.org/r/183987]]
+
+#patch-for-review",1420840039,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"I think my fix is the only sensible way to fix the bug. I'm happy with the patch in its current state, but ideally I'd like someone from mobile to give it a test.",1420657204,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"@Jdlrobson, @Esanders: What's the status on this? If Ed's change isn't going to be merged, we should at least fix this specific bug.",1420656568,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,"Change 180775 had a related patch set uploaded (by Esanders):
+Remove border-box rule from reset.less
+
+[[https://gerrit.wikimedia.org/r/180775]]
+
+#patch-for-review",1420456979,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+Inspector titles clipped in VisualEditor on mobile,Every element? So... Fix MobileFrontend?,1419509177,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-aekjxzlbg6hbymq5ylwp,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request","The output of the embedded `user.tokens` module changes on every request. I'm not entirely sure whether this was on purpose.
+
+Traced it back to https://github.com/wikimedia/mediawiki/commit/b1e4006b44
+{b1e4006b44}
+
+This is a bit of a problem since we minify this module, and by default all minifications are cached at a key that is the hash of the unminified contents. We should implement a way to bypass the minification cache.
+
+As such, we're creating a new cache key and populating it on every page view for every logged in user. And that key is never used again.
+
+Example from localhost:
+
+```
+<script>...mw.loader.implement(""user.tokens"",function($,jQuery){mw.user.tokens.set({""editToken"":""5da7f8da8cc2c12b40e63510d3b83f3754937d96+\\"",""patrolToken"":""bc1e366f8f7806ed27d067667cdeebe554937d96+\\"",""watchToken"":""c52e9fcc036b315fe8ba3e0135cb928d54937d96+\\""});},{},{},{});
+/* cache key: alphawiki:resourceloader:filter:minify-js:7:aed9432283c8152b3eaff1761844e771 */
+```",1418952452,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qguei6bgca37llfakum,task_description,resolved
+"Embedded ""user.tokens"" module changes on every request","With the cache issues resolved, this is no longer a performance problem.
+
+The constant regeneration isn't actually a problem since they are not actually all stored. MediaWiki uses encoding and encryption to restrict internal tokens with a timestamp salt.
+
+> 6fa4893928 — resourceloader: Don't cache minification of user.tokens
+> https://gerrit.wikimedia.org/r/210845
+",1435036147,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request","Here's a graph showing a successful drop in RL-minification cache lookups after deploying [I6016e4b01e44](https://gerrit.wikimedia.org/r/#/q/I6016e4b01e44,n,z).
+
+Labels added to match relevant events from the [Server Admin Log](https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&oldid=161613).
+{F173780}
+
+Source: https://graphite.wikimedia.org/render?from=-4weeks&until=now&width=900&target=MediaWiki.rl-minify-js-cache-misses.count
+",1433343594,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#1284121, @Anomie wrote:
+>>>! In T84960#1284083, @Krinkle wrote:
+>> I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes.
+> 
+> Except that's not true. I see nothing in MediaWiki core or WMF-deployed extensions that uses the $maxage parameter for User::matchEditToken() except the ApiCheckTokens module. Maybe Restbase is doing it, but nothing currently in PHP is considering tokens expired any sooner than the end of the session.
+
+I'm guessing VE is submitting to restbase, and restbase is using ApiCheckTokens to check the token. I've lost track of who did that integration (Roan? Gwicke?), but I'm guessing that call needs to fix the maxtokenage param?",1431620193,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#1284083, @Krinkle wrote:
+> I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes.
+
+Except that's not true. I see nothing in MediaWiki core or WMF-deployed extensions that uses the $maxage parameter for User::matchEditToken() except the ApiCheckTokens module. Maybe Restbase is doing it, but nothing currently in PHP is considering tokens expired any sooner than the end of the session.",1431572729,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#950866, @Anomie wrote:
+> The point isn't to make the tokens last **longer** than the session. [...] You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or [..]
+
+I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes. Similarly it seems useless that VisualEditor and other uses of tokens almost always have to make two or three round trips just to make a write action. Right now its three. 1) Failed write action for token expired, 2) get new token, 3) Re-try write again. Not only does it make two more http requests then desired, it also transmits a potentially large amount of data to the server multiple times. We could cut this back to 2 requests by making the client-side aware of how long the tokens are valid for. While that is better, it is imho not good enough.
+
+Two facts:
+
+* In the past we made the decision to embed the user.tokens module in the page because we saw performance problems with the client-side having to request a token for write actions by JavaScript (for e.g. watch star click, or VE edit save).
+* In the past we made the observation that saving content with VisualEditor is a performance bottle neck, that we worked hard to cut down. Due to this token expiration problem, we basically nullified all that effort by having to submit everything twice for a lot of users.
+
+As such, I would recommend strongly that we **figure out a feasible way to allow MediaWiki frontend to perform write actions with the API without needing to fetch a token over a separate HTTP request**. The client's cookie is already authority enough to request as many tokens as it wants during the session, so in theory it seems really stupid that we need a token at all when making a write action. Clearly whatever origin can make or forge one request, can also forge the other. Raising the bar might make sense to just make it a tiny bit harder, but I'm questioning whether that's worth it.
+
+From this perspective, this change was a significant regression as both of these two expectations are no longer met by the system.
+
+The naive approach of not making the tokens change every request is understandably not acceptable from a security perspective because of ""BREACH""-type reflection attacks. The only option I left then is to continue issuing new tokens each page view but have those tokens (that are embedded in the page) be valid for the entire duration of a page view (or otherwise, at least for an hour or so).",1431569278,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#950866, @Anomie wrote:
+> The point isn't to make the tokens last **longer** than the session. [...] You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or [..]
+
+I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes. Similarly it seems useless that VisualEditor and other uses of tokens almost always have to make two or three round trips just to make a write action. Right now its three. 1) Failed write action for token expired, 2) get new token, 3) Re-try write again. Now only does it make two more http requests then desired, it also submits a potentially large amount of data multiple times.
+
+Two facts:
+
+* In the past we made the decision to embed the user.tokens module in the page because we saw performance problems with the client-side having to request a token for write actions by JavaScript (for e.g. watch star click, or VE edit save).
+* In the past we made the observation that saving content with VisualEditor is a performance bottle neck, that we worked hard to cut down. Due to this token expiration problem, we basically nulled that effort by now having to submit everything twice.
+
+As such, I would recommend strongly that we figure out a feasible way to allow MediaWiki frontend to perform write actions with the API without needing to fetch a separate token over HTTP. From this perspective, this change was a significant regression as both of these two expectations are no longer met by the system.
+
+The naive approach of not making the tokens change every request is understandably not acceptable from a security perspective because of ""BREACH""-type reflection attacks. The only option I see right now would be to continue issuing new tokens each page view but having those tokens (that are embedded in the page) be valid for the entire duration of a page view (or otherwise, at least an hour or so).",1431568900,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#950866, @Anomie wrote:
+> The point isn't to make the tokens last **longer** than the session. [...] You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or [..]
+
+I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes. Similarly it seems useless that VisualEditor and other uses of tokens almost always have to make two or three round trips just to make a write action. Right now its three. 1) Failed write action for token expired, 2) get new token, 3) Re-try write again. Now only does it make two more http requests then desired, it also submits a potentially large amount of data multiple times.
+
+Two facts:
+
+* In the past we made the decision to embed the user.tokens module in the page because we saw performance problems with the client-side having to request a token for write actions by JavaScript (for e.g. watch star click, or VE edit save).
+* In the past we made the observation that saving content with VisualEditor is a performance bottle neck, that we worked hard to cut down. Due to this token expiration problem, we basically nulled that effort by now having to submit everything twice.
+
+As such, I would recommend strongly that we figure out a feasible way to allow MediaWiki frontend to perform write actions with the API without needing to fetch a separate token over HTTP. From this perspective, this change was a significant regression as both of these two expectations are no longer met by the system.
+
+The naive approach of not making the tokens change every request is understandably not acceptable from a security perspective because of ""BREACH""-tpe reflection attacks. The only option I see right now would be to continue issuing new tokens but having tokens that are embedded in the page be valid for the entire page view session (or otherwise, at least an hour or so).",1431568844,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#950866, @Anomie wrote:
+> The point isn't to make the tokens last **longer** than the session. [...] You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or [..]
+
+I understand that. My point is that it seems useless to embed tokens in the html that client-side JavaScript (from core, extensions or gadgets) cannot reliably use because by design it will always expire after a few minutes. Similarly it seems useless that VisualEditor and other uses of tokens almost always have to make two or three round trips just to make a write action. Right now its three. 1) Failed write action for token expired, 2) get new token, 3) Re-try write again. Now only does it make two more http requests then desired, it also submits a potentially large amount of data multiple times.
+
+Two facts:
+
+* In the past we made the decision to embed the user.tokens module in the page because we saw performance problems with the client-side having to request a token for write actions by JavaScript (for e.g. watch star click, or VE edit save).
+* In the past we made the observation that saving content with VisualEditor is a performance bottle neck, that we worked hard to cut down. Due to this token expiration problem, we basically nulled that effort by now having to submit everything twice.
+
+As such, I would recommend strongly that we figure out a feasible way to allow MediaWiki frontend to perform write actions with the API without needing to fetch a separate token over HTTP. From this perspective, this change was a significant regression as both of these two expectations are no longer met by the system.",1431568646,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request","I have no idea what distinction you're making between ""client-side"" tokens and other tokens. All tokens are sent from the server to the client via a channel that CSRF attackers shouldn't have access to, and then sent from the client back to the server to detect CSRF.
+
+The point isn't to make the tokens last **longer** than the session. That won't happen anyway, if the session is lost then all the tokens go away too just as they have always done. The point is to make it possible for tokens to expire **before** the session does to reduce the window of vulnerability if an attacker somehow manages to compromise a single token, with a predictable lifetime after generation for each token. You won't get a 5-minute token and be able to extend it indefinitely by re-requesting it, or get a 5-minute token but then requesting it again after 4 minutes gives you the same token that will expire in only 1 minute, or get a 5-minute token but then it expires early because some other code requests another instance of the same token, and you won't be able to flood the session with hundreds of tokens waiting to expire. The constantly-changing nature of the tokens also protects against attacks such as BREACH which depend on multiple requests to reveal individual bits or bytes of a constant token.
+
+
+Now, if the caching situation really can't be worked around by requesting the tokens from the API as needed, we might be able to make User::getEditTokenAtTimestamp() public and use that to generate a token with a constant distant-past timestamp for your JS. Uses of the token that don't specify a maximum age will accept such a token as long as the session is valid, while uses that do will still treat them as expired. But I'd wait for Chris to look that plan over before spending a lot of time on it.",1420041856,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request",">>! In T84960#936308, @Anomie wrote:
+> Why is this bug marked as private? I'm not seeing anything obviously sensitive here.
+
+I filed it under security because the varying tokens, while sensible in general, wasn't necessarily applied on purpose for API requests from the web interface. There also seems potential abuse against the minification cache. Or at the very least a performance/scale hazard for sites without LRU in their cache system. MediaWiki's the default DB cache, for instance, would get blown up by this (my localhost install did).
+
+>>! In T84960#936308, @Anomie wrote:
+> Or the tokens could just be fetched from the API when they're needed instead of being served with every request.
+
+That would require fair amount of token fetching from the client-side for AJAX actions originating from core modules (e.g. watch), as well as gadgets and extensions.
+
+I'd like to better understand why tokens are time-limited. I assume it has to do with reducing impact of compromise. However does that apply to client-side tokens? The client is able to fetch tokens whenever using its session cookie (which doesn't mutate on every request). Sessions do expire, however. And having tokens last longer than the session seems odd. Perhaps we can associate them with a session and only give clients new tokens once per session? If I recall correctly, that was the previous behaviour as well for CSRF tokens used in HTML (e.g. for EditPage). Or was there a problem with that?",1419989593,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Embedded ""user.tokens"" module changes on every request","Why is this bug marked as private? I'm not seeing anything obviously sensitive here.
+
+> I'm not entirely sure whether this was on purpose.
+
+The fact that tokens change based on the time they're generated is necessary behavior of the time-limiting: the timestamp must be included (in ""plain"" text) in the token so it can be checked, and it must be included in the hash so it can't be faked.
+
+> We should implement a way to bypass the minification cache.
+
+Or the tokens could just be fetched from the API when they're needed instead of being served with every request.",1418999026,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-2qguei6bgca37llfakum,task_subcomment,NA
+"Release VisualEditor-MediaWiki as ""1.0""","Lots of things to do here, but broadly they break down into six categories:
+
+[ ] Functionality – mostly done
+[ ] Performance – main focus area left
+[ ] User experience – the current integration is a bit lacking, but otherwise this is not far off
+[ ] Language support – still a lot of work for IME support here
+[ ] Browser support – mostly done
+[ ] Major bugs – not many of these left (he says…)",1418941653,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-supxiuf2snjkiztaupce,task_description,open
+"Release VisualEditor-MediaWiki as ""1.0""",1.0,1598446543,PHID-USER-mqxfovqi5o53vonvhaeh,True,PHID-TASK-supxiuf2snjkiztaupce,task_subcomment,NA
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,"In betalabs: 
+
+1. On a page in VE open Find/Replace - not typing anything in it, just open - a cursor will be in the Find field.
+1. Open an existing template on the page for editing.  
+2. Place a cursor in the first field of the transclusion box and click Tab to navigate to the next field.
+
+The cursor will be placed into Replace field; clicking Tab one more time brings the cursor back into Transclusion box. 
+
+The same issue is with Citation.",1418935912,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-woqxqv6iluugikztqpwo,task_description,resolved
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,It seems that I fixed this in 2015 with this change to use natural tab order: <https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/243527>.,1611951130,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-woqxqv6iluugikztqpwo,task_subcomment,NA
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,"Or maybe listen for events to make sure things focus in the order I wanted, or something",1420046868,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-woqxqv6iluugikztqpwo,task_subcomment,NA
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,"So we could work out the current highest tabindex in the page and then add it to all our tabindexes in the template dialog. Which is horrible.
+
+Or I wonder if we should really just have the info button next to the parameter name and the remove button immediately following the value field, or something. Then the actual order of the elements might be logical and we could remove the tabindexes.",1419900981,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-woqxqv6iluugikztqpwo,task_subcomment,NA
+Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background,The find and replace dialog also sets tabindexes... Guess the transclusion dialog is setting the same indexes.,1419509992,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-woqxqv6iluugikztqpwo,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","In our quest to convert the whole cluster to trusty and HHVM, we've got to the imagescalers.
+
+From what I can see from puppet/the current image scalers is that we have the following packages custom-built at the moment:
+
+  - ffmpeg2theora (disabled libav multithreading)
+  - librsvg (external resources loading protection)
+  - libvips31 (backport)
+  - libvpx1 (backport)
+
+We also need to evaluate the performance of HHVM under the peculiar imagescalers load, which is probably going to be non-optimal.
+
+Finally, testing should be very accurate to assess any rendering differences on trusty vs precise.",1418890706,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_description,resolved
+"Convert eqiad imagescalers to HHVM, Trusty","Just for cross-reference, a regression was found with rsvg - svgs > 10 MB (there's about 9000 such files) don't render. We'd need to upgrade to a later version of rsvg to fix, see T111815",1442126072,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227967 merged by Giuseppe Lavagetto:
+imagescalers: convert the last two servers to HAT
+
+[[https://gerrit.wikimedia.org/r/227967]]",1438686339,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227967 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescalers: convert the last two servers to HAT
+
+[[https://gerrit.wikimedia.org/r/227967]]
+",1438252852,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227676 merged by jenkins-bot:
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227676]]",1438186253,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227733 merged by jenkins-bot:
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227733]]",1438186235,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227732 merged by jenkins-bot:
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227732]]",1438186180,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227733 had a related patch set uploaded (by BryanDavis):
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227733]]
+",1438184069,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227732 had a related patch set uploaded (by BryanDavis):
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227732]]
+",1438184036,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227676 had a related patch set uploaded (by Giuseppe Lavagetto):
+Add Content-Length header to thumb.php redirects
+
+[[https://gerrit.wikimedia.org/r/227676]]
+",1438164978,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","I think I found what is the latest gotcha with imagescalers:
+
+```
+curl -H 'X-Forwarded-Proto: https' -H 'Host: commons.wikimedia.org' 'http://mw1152/w/thumb_handler.php/7/75/John_Bauer-Tyr_and_Fenrir.jpg/180px-John_Bauer-Tyr_and_Fenrir.jpg' -v
+* About to connect() to mw1152 port 80 (#0)
+*   Trying 10.64.16.132... connected
+> GET /w/thumb_handler.php/7/75/John_Bauer-Tyr_and_Fenrir.jpg/180px-John_Bauer-Tyr_and_Fenrir.jpg HTTP/1.1
+> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
+> Accept: */*
+> X-Forwarded-Proto: https
+> Host: commons.wikimedia.org
+> 
+< HTTP/1.1 302 Found
+< Date: Wed, 29 Jul 2015 09:56:29 GMT
+< Server: Apache
+< X-Powered-By: HHVM/3.6.1
+< X-Content-Type-Options: nosniff
+< Cache-control: no-cache
+< Expires: Wed, 29 Jul 2015 21:56:29 GMT
+< Vary: X-Forwarded-Proto
+< Location: https://upload.wikimedia.org/wikipedia/commons/thumb/1/18/Tyr_and_Fenrir-John_Bauer.jpg/180px-Tyr_and_Fenrir-John_Bauer.jpg
+< Transfer-Encoding: chunked
+< Content-Type: text/html; charset=utf-8
+```
+
+while on non-HHVM ones
+```
+curl -H 'X-Forwarded-Proto: https' -H 'Host: commons.wikimedia.org' 'http://mw1159/w/thumb_handler.php/7/75/John_Bauer-Tyr_and_Fenrir.jpg/180px-John_Bauer-Tyr_and_Fenrir.jpg' -v
+* About to connect() to mw1159 port 80 (#0)
+*   Trying 10.64.16.139... connected
+> GET /w/thumb_handler.php/7/75/John_Bauer-Tyr_and_Fenrir.jpg/180px-John_Bauer-Tyr_and_Fenrir.jpg HTTP/1.1
+> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
+> Accept: */*
+> X-Forwarded-Proto: https
+> Host: commons.wikimedia.org
+> 
+< HTTP/1.1 302 Found
+< Date: Wed, 29 Jul 2015 09:58:24 GMT
+< Server: Apache
+< X-Content-Type-Options: nosniff
+< Cache-control: no-cache
+< Location: https://upload.wikimedia.org/wikipedia/commons/thumb/1/18/Tyr_and_Fenrir-John_Bauer.jpg/180px-Tyr_and_Fenrir-John_Bauer.jpg
+< Expires: Wed, 29 Jul 2015 21:58:24 GMT
+< Vary: X-Forwarded-Proto
+< Content-Length: 0
+< Content-Type: text/html
+< 
+```
+
+In this case we have the same problem we had with 404s: thumb.php doesn't set the content-length, which makes apache assume the transfer-encoding is chunked, which for a 0 sized body makes varnish barf.",1438163989,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227160 merged by Ori.livneh:
+Re-introduce ProxyPass rule for thumb_handler.php, with corrected docroots
+
+[[https://gerrit.wikimedia.org/r/227160]]",1437952373,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 227160 had a related patch set uploaded (by Ori.livneh):
+Re-introduce ProxyPass rule for thumb_handler.php, with corrected docroots
+
+[[https://gerrit.wikimedia.org/r/227160]]
+",1437946163,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 226738 merged by Ori.livneh:
+Follow-up for Ie17cb06: add thumb_handler.php ProxyPass rule to all vhosts
+
+[[https://gerrit.wikimedia.org/r/226738]]",1437756519,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 226738 had a related patch set uploaded (by Ori.livneh):
+Follow-up for Ie17cb06: add thumb_handler.php ProxyPass rule to all vhosts
+
+[[https://gerrit.wikimedia.org/r/226738]]
+",1437756390,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 226658 merged by Ori.livneh:
+Add ProxyPass rule for thumb_handler.php
+
+[[https://gerrit.wikimedia.org/r/226658]]",1437697040,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 226658 had a related patch set uploaded (by Ori.livneh):
+Add ProxyPass rule for thumb_handler.php
+
+[[https://gerrit.wikimedia.org/r/226658]]
+",1437696974,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1473663, @Krenair wrote:
+> ```2015-07-23 00:06:38 mw1153 commonswiki exception ERROR: [d68c4bb1] /w/thumb_handler.php/2/2e/Mirage_III_A_01_Mus%0Aee_du_Bourget_P1020118.JPG/424px-%0AMirage_III_A_01_Musee_du_Bourget_P1020118.JPG   MWException from line 171 of /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php: CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. {""exception"":""[object] (MWException(code: 0): CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. at /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php:171)""}```
+> Seen from mw115[2-8]
+
+See {T106743}",1437692346,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1473663, @Krenair wrote:
+> ```2015-07-23 00:06:38 mw1153 commonswiki exception ERROR: [d68c4bb1] /w/thumb_handler.php/2/2e/Mirage_III_A_01_Mus%0Aee_du_Bourget_P1020118.JPG/424px-%0AMirage_III_A_01_Musee_du_Bourget_P1020118.JPG   MWException from line 171 of /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php: CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. {""exception"":""[object] (MWException(code: 0): CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. at /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php:171)""}```
+> Seen from mw115[2-8]
+
+Ummm, why/how do we have HHVM boxes without APC enabled?",1437692170,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","```2015-07-23 00:06:38 mw1153 commonswiki exception ERROR: [d68c4bb1] /w/thumb_handler.php/2/2e/Mirage_III_A_01_Mus%0Aee_du_Bourget_P1020118.JPG/424px-%0AMirage_III_A_01_Musee_du_Bourget_P1020118.JPG   MWException from line 171 of /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php: CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. {""exception"":""[object] (MWException(code: 0): CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC. at /srv/mediawiki/php-1.26wmf15/includes/objectcache/ObjectCache.php:171)""}```
+Seen from mw115[2-8]",1437610749,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","New imagescalers fun found today: 
+
+an high level of 5xx were going on today, so I intercepted a few urls that were returning a 503 - for example, I requested
+
+https://upload.wikimedia.org/wikipedia/commons/thumb/0/01/Casquette-IMG_0922.jpg/600px-Casquette-IMG_0922.jpg
+
+from my browser and got a 503:
+
+```
+...
+If you report this error to the Wikimedia System Administrators, please include the details below.
+Request: GET http://upload.wikimedia.org/wikipedia/commons/thumb/0/01/Casquette-IMG_0922.jpg/600px-Casquette-IMG_0922.jpg, from 10.64.32.81 via cp1048 cp1048 ([10.64.32.100]:3128), Varnish XID 3696382267
+Forwarded for: 79.58.168.196, 10.64.32.81, 10.64.32.81
+Error: 503, Service Unavailable at Wed, 22 Jul 2015 16:21:18 GMT
+```
+
+while if I do a plain curl I get the correct behaviour, a 302:
+
+```
+curl -I https://upload.wikimedia.org/wikipedia/commons/thumb/0/01/Casquette-IMG_0922.jpg/600px-Casquette-IMG_0922.jpg
+HTTP/1.1 302 Found
+Server: nginx/1.9.3
+Date: Wed, 22 Jul 2015 16:30:29 GMT
+Content-Type: text/html
+Content-Length: 0
+Connection: keep-alive
+X-Content-Type-Options: nosniff
+Expires: Thu, 23 Jul 2015 04:22:53 GMT
+Vary: X-Forwarded-Proto
+Location: https://upload.wikimedia.org/wikipedia/commons/thumb/9/99/Casquette_d%27administrateur_colonial_-IMG_0922.jpg/600px-Casquette_d%27administrateur_colonial_-IMG_0922.jpg
+Cache-Control: no-cache
+```
+
+So I tought this could have to do with compression. But subsequent requests were successful from the browser as well, so no idea what is going on here - maybe one imagescaler doing something wrong?
+
+",1437582881,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1466863, @Joe wrote:
+> FTR, I am going to depool all remaining Zend imagescaler today to test any outstanding problems with those. If none arise, I'm going to upgrade the last three tomorrow.
+
+Great. Sounds like a good plan. Thanks for pushing forward.",1437498908,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","FTR, I am going to depool all remaining Zend imagescaler today to test any outstanding problems with those. If none arise, I'm going to upgrade the last three tomorrow.",1437486922,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 225285 merged by Giuseppe Lavagetto:
+imagescalers: re-image mw115[6-8] to trusty, HHVM
+
+[[https://gerrit.wikimedia.org/r/225285]]",1437114439,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 225285 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescalers: re-image mw115[6-8] to trusty, HHVM
+
+[[https://gerrit.wikimedia.org/r/225285]]
+",1437114386,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 224594 merged by Giuseppe Lavagetto:
+imagescalers: reimage mw1154, mw1155 to HAT
+
+[[https://gerrit.wikimedia.org/r/224594]]",1436868273,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 224594 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescalers: reimage mw1154, mw1155 to HAT
+
+[[https://gerrit.wikimedia.org/r/224594]]
+",1436867484,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 223331 merged by Giuseppe Lavagetto:
+imagescalers: reimage mw1153 with HAT
+
+[[https://gerrit.wikimedia.org/r/223331]]",1436347245,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 223331 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescalers: reimage mw1153 with HAT
+
+[[https://gerrit.wikimedia.org/r/223331]]
+",1436284180,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","(codfw imagescalers are all HHVM+Trusty already, so we're just left with mw1153-1160)",1435969942,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","For the past several weeks, this task was blocked on the fact that the HHVM renderer (mw1152) would cause 5xx spikes whenever it was pooled. The issue appears to have been a corruption in the cached byte-code for `/w/404.php` which caused Varnish to be unable to parse 404 responses generated by HHVM on mw1152. These responses were transformed by varnish into 503s. Touching the file fixed it.
+
+The remaining task is to re-image the other scalers.",1435968941,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Bah, edit conflicts.",1435619612,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Since the latest test I did after ori found we needed that file was unsuccessful, and I have zero time to work on this at the moment, I'll release this ticket so that somebody else can grab it.
+
+As matanya clearly stated ""We've been waiting forever for this"".",1433252548,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 213228 merged by Ori.livneh:
+mediawiki: Touch /etc/wikimedia-image-scaler on image scalers
+
+[[https://gerrit.wikimedia.org/r/213228]]",1432463202,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 213228 had a related patch set uploaded (by Ori.livneh):
+mediawiki: Touch /etc/wikimedia-image-scaler on image scalers
+
+[[https://gerrit.wikimedia.org/r/213228]]
+",1432463124,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1306421, @greg wrote:
+> What ya'll think now? :)
+
+We should probably not schedule this until we resolve the issue Giuseppe spotted in T84842#1265055.",1432462003,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","```
+greg moved this task to This week: May 4-8 on the Roadmap workboard.
+greg moved this task to This week: May 11-15 on the Roadmap workboard.
+greg moved this task to May 18-22 on the Roadmap workboard.
+
+```
+
+What ya'll think now? :)",1432460828,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Ok so, after a lot of battles with HHVM 3.6.1, the mysterious 503s on the imagescalers continued.
+
+One possible cause is the fact that apparently some images require more memory to be converted on trusty:
+```
+curl -H 'Host: commons.wikimedia.org' 'http://mw1152/w/thumb_handler.php/1/17/HawkridgeBarton_Chittlehampton_NorthDevon.PNG/1000px-HawkridgeBarton_Chittlehampton_NorthDevon.PNG' -I
+HTTP/1.1 500 Internal server error
+Date: Wed, 06 May 2015 15:13:17 GMT
+Server: Apache
+X-Powered-By: HHVM/3.6.1
+X-Content-Type-Options: nosniff
+Cache-control: no-cache
+X-MW-Thumbnail-Renderer: mw1152
+Connection: close
+Content-Type: text/html; charset=utf-8
+```
+
+which results in the kernel recording
+
+```
+May  6 15:13:20 mw1152 kernel: [4775538.759268] memory: usage 307200kB, limit 307200kB, failcnt 50
+May  6 15:13:20 mw1152 kernel: [4775538.759269] memory+swap: usage 0kB, limit 18014398509481983kB, failcnt 0
+May  6 15:13:20 mw1152 kernel: [4775538.759270] kmem: usage 0kB, limit 18014398509481983kB, failcnt 0
+May  6 15:13:20 mw1152 kernel: [4775538.759271] Memory cgroup stats for /mediawiki/job/15592: cache:0KB rss:307200KB rss_huge:202752KB mapped_file:0KB writeback:0KB inactive_anon:0KB active_anon:307132KB inactive_file:0KB active_file:0KB unevictable:0KB
+May  6 15:13:20 mw1152 kernel: [4775538.759282] [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
+May  6 15:13:20 mw1152 kernel: [4775538.759334] [15592]    33 15592     5222      426      16        0             0 bash
+May  6 15:13:20 mw1152 kernel: [4775538.759336] [15594]    33 15594     2867      167      11        0             0 timeout
+May  6 15:13:20 mw1152 kernel: [4775538.759337] [15595]    33 15595    93743    77414     186        0             0 convert
+May  6 15:13:20 mw1152 kernel: [4775538.759339] Memory cgroup out of memory: Kill process 15595 (convert) score 1010 or sacrifice child
+May  6 15:13:20 mw1152 kernel: [4775538.768545] Killed process 15595 (convert) total-vm:374972kB, anon-rss:307004kB, file-rss:2652kB
+May  6 15:15:01 mw1152 CRON[15698]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
+```
+
+Also, I tested that at smaller resulting sizes this doesn't cause the 500 to be emitted.
+
+This is the mediawiki error log: P612
+
+I'm still unsure this is really the cause of the larger number of 503s I see.
+",1430925671,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Ok so, after a lot of battles with HHVM 3.6.1, the mysterious 503s on the imagescalers continued.
+
+One possible cause is the fact that apparently some images require more memory to be converted on trusty:
+```
+curl -H 'Host: commons.wikimedia.org' 'http://mw1152/w/thumb_handler.php/1/17/HawkridgeBarton_Chittlehampton_NorthDevon.PNG/1000px-HawkridgeBarton_Chittlehampton_NorthDevon.PNG' -I
+HTTP/1.1 500 Internal server error
+Date: Wed, 06 May 2015 15:13:17 GMT
+Server: Apache
+X-Powered-By: HHVM/3.6.1
+X-Content-Type-Options: nosniff
+Cache-control: no-cache
+X-MW-Thumbnail-Renderer: mw1152
+Connection: close
+Content-Type: text/html; charset=utf-8
+```
+
+which results in the kernel recording
+
+```
+May  6 15:13:20 mw1152 kernel: [4775538.759268] memory: usage 307200kB, limit 307200kB, failcnt 50
+May  6 15:13:20 mw1152 kernel: [4775538.759269] memory+swap: usage 0kB, limit 18014398509481983kB, failcnt 0
+May  6 15:13:20 mw1152 kernel: [4775538.759270] kmem: usage 0kB, limit 18014398509481983kB, failcnt 0
+May  6 15:13:20 mw1152 kernel: [4775538.759271] Memory cgroup stats for /mediawiki/job/15592: cache:0KB rss:307200KB rss_huge:202752KB mapped_file:0KB writeback:0KB inactive_anon:0KB active_anon:307132KB inactive_file:0KB active_file:0KB unevictable:0KB
+May  6 15:13:20 mw1152 kernel: [4775538.759282] [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
+May  6 15:13:20 mw1152 kernel: [4775538.759334] [15592]    33 15592     5222      426      16        0             0 bash
+May  6 15:13:20 mw1152 kernel: [4775538.759336] [15594]    33 15594     2867      167      11        0             0 timeout
+May  6 15:13:20 mw1152 kernel: [4775538.759337] [15595]    33 15595    93743    77414     186        0             0 convert
+May  6 15:13:20 mw1152 kernel: [4775538.759339] Memory cgroup out of memory: Kill process 15595 (convert) score 1010 or sacrifice child
+May  6 15:13:20 mw1152 kernel: [4775538.768545] Killed process 15595 (convert) total-vm:374972kB, anon-rss:307004kB, file-rss:2652kB
+May  6 15:15:01 mw1152 CRON[15698]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
+```
+
+Also, I tested that at smaller resulting sizes this doesn't cause the 500 to be emitted.
+
+This is the mediawiki error log: P612
+
+I'm still unsure this is really the cause of the larger 503s I see.
+",1430925624,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","OK, let's schedule to a specific week once we have confidence on the ETA.",1428004554,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1175265, @Eloquence wrote:
+> @Joe, do we need to push this to next week?
+
+At minimum. Giuseppe ran into segfaults with Tim's output buffer patch and that's blocking the rollout of a new package, which the scalers need.",1428004454,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Joe, do we need to push this to next week?",1428004192,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 196173 merged by Giuseppe Lavagetto:
+mediawiki: install fonts metric-compatible with Calibri and Cambria
+
+[[https://gerrit.wikimedia.org/r/196173]]",1427696479,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","This was scheduled for March, is this happening next week or should we bump it to April?",1426819491,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","The HHVM upstream bug tracked in {T91468} should block this rollout. See analysis in T89918#1052318 for full gory details, but the TL;DR is that HHVM's async i/o and fcgi bridge interact in such a way that a slow consumer and a fast producer can OOM the HHVM process resulting in a 503 from Apache.",1426268546,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">>! In T84842#1112319, @Joe wrote:
+> @brion problem confirmed, but this would be relevant for the videoscalers, right?
+
+ah good if video scalers are a separate config then please regard my comment as belonging to them and ignore it here :D",1426183149,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","ok, then it was probably a false positive. I'm a bit in the dark about what is timing out here then, will need to investigate further",1426162058,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","What happens with those requests is that the web server queries the image scalers internally to have them scale an image which isn't public yet.
+
+What I don't know yet, and am trying to figure out in that bug, is if any error happens at the image scalers' level, or if it's a timeout happening higher in the chain (in varnish, for example). My main theory is that the image scaler is taking too long to generate the requested thumbnail and *something* times out in the chain, causing a nasty 503 instead of the cleaner error that should happen if the curl request to the image scalers hit the timeout setting.",1426161732,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",Special:UploadStash has a known 503 issue happening at the moment: T90599,1426161590,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","I re-pooled the HHVM imagescaler and got confirmation that SVG files rendered correctly.
+
+However, I was still seeing a significant amount of 503s, but nothing stood out in any log apart from a few occurrencies of errors in Special:UploadStash, like e.g.
+```
+http://commons.wikimedia.org/wiki/Special:UploadStash/thumb/13091utfih7k.ab6yzc.1488278.jpg/71px-13091utfih7k.ab6yzc.1488278.jpg
+```
+
+but this is just a shot in the dark, as those are probably handled by the general appserver pool. I will have to ask someone with expertise on UploadWizard to confirm how the thumb request is performed in this case.",1426159486,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 196186 merged by jenkins-bot:
+imagescaling: remove legacy option for HHVM imagescalers
+
+[[https://gerrit.wikimedia.org/r/196186]]",1426156122,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 196186 had a related patch set uploaded (by Giuseppe Lavagetto):
+imagescaling: remove legacy option for HHVM imagescalers
+
+[[https://gerrit.wikimedia.org/r/196186]]
+",1426155115,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","If the new rsvg version doesn't need a specific option turned on to avoid external resources, then it's just a matter of having a slightly different mediawiki configuration for the hhvm image scaler.
+
+Set wgSVGConverter to 'rsvg-broken' for it instead of the default 'rsvg-secure'.
+
+Relevant code is in:
+mediawiki-config/wmf-config/CommonSettings.php
+mediawiki-config/wmf-config/InitialiseSettings.php",1426153770,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Gilles I imagined that - given our svg code now supports the security model in the more modern rsvg versions I guessed it would work automagically. It is not the case, I am still looking at the code to be sure of what's wrong here.",1426152998,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",--no-external-files is an option that was coming from our custom patches to librsvg,1426152382,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","I had to depool the server, as quite a lot of unexpected errors were spawning.
+
+E.G. when rescaling http://commons.wikimedia.org/w/thumb_handler.php/c/ca/Alarilla_Guadalajara_-_Mapa_municipal.svg/39px-Alarilla_Guadalajara_-_Mapa_municipal.svg.png I got the following error
+
+```
+<!DOCTYPE html>
+<html><head>
+<meta charset=""UTF-8"" />
+<title>Error generating thumbnail</title>
+</head>
+<body>
+<h1>Error generating thumbnail</h1>
+<p>
+Error creating thumbnail: Unknown option --no-external-files<br />
+
+</p>
+<!-- /w/thumb_handler.php/c/ca/Alarilla_Guadalajara_-_Mapa_municipal.svg/39px-Alarilla_Guadalajara_-_Mapa_municipal.svg.png -->
+<!-- mw1152 -->
+
+</body>
+</html>
+```
+
+Probably the imagescaling code needs to be corrected? I'll look at rsvg options later today",1426151938,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@brion problem confirmed, but this would be relevant for the videoscalers, right?",1426150660,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",The imagescaler is now into rotation.,1426150632,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Change 196173 had a related patch set uploaded (by Giuseppe Lavagetto):
+mediawiki: install fonts metric-compatible with Calibri and Cambria
+
+[[https://gerrit.wikimedia.org/r/196173]]
+",1426149856,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","May you add some additional fonts, e.g. [[https://wiki.debian.org/SubstitutingCalibriAndCambriaFonts|Caladea and Carlito]] for easier SVG rendering?
+
+See also https://commons.wikimedia.org/wiki/File:MediaWiki_SVG_fonts.svg",1426148245,PHID-USER-mpi3m7v2orbtizvqa43q,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",Announcement made https://commons.wikimedia.org/wiki/Commons:Village_pump#Upgrade_of_image_rendering_servers ( permalink: https://commons.wikimedia.org/w/index.php?title=Commons:Village_pump&oldid=152736923#Upgrade_of_image_rendering_servers ),1426016825,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Joe here's a test case for the webm->ogv ffmpeg2theora conversion:
+
+```
+wget https://upload.wikimedia.org/wikipedia/commons/c/c8/Sneak_Preview_-_Wikipedia_VisualEditor.webm
+
+ffmpeg2theora \
+  --width 640 --height 360 -V 512 -a 1 -H 44100 -c 2 --no-upscaling --keyint 128 --buf-delay 256 \
+  -o Sneak_Preview_-_Wikipedia_VisualEditor.360p.ogv \
+  Sneak_Preview_-_Wikipedia_VisualEditor.webm
+```
+
+Lots of errors about audio format during conversion, then the resulting .ogv is unplayable.
+",1425932726,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Bawolff none of the new links you posted presented any issue. I think we can move on and put at least one machine in rotation by thursday 10 AM UTC; are you able to make the announcement on Commons:VP about it?
+
+@brion: if you have a good example I'll test it.",1425915948,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",Another thing to test: .ogg / .ogv transcoding output (from .webm or opus source). I've had some troubles with ffmpeg2theora on Trusty (though the note above about multithreading disabled might have resolved that?),1425669302,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Some other GIF files since that's where we ran into problems (These are from the most popular list, most will be really small cases that don't stress the server, so I expect they will render fine):
+
+* https://upload.wikimedia.org/wikipedia/commons/thumb/2/26/Mug_and_Torus_morph.gif/120px-Mug_and_Torus_morph.gif
+* https://upload.wikimedia.org/wikipedia/commons/thumb/8/86/Qxz-ad137.gif/320px-Qxz-ad137.gif
+* https://upload.wikimedia.org/wikipedia/commons/thumb/1/19/Second_world_war_europe_animation_small.gif/215px-Second_world_war_europe_animation_small.gif
+* https://upload.wikimedia.org/wikipedia/commons/thumb/8/81/ADN_animation.gif/100px-ADN_animation.gif
+* https://upload.wikimedia.org/wikipedia/commons/thumb/9/9b/Lang-fr.gif/220px-Lang-fr.gif",1425659471,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Animated gifs have always been memory intensive. File:Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif was already on the edge of what was running out of memory in the old config. I guess the newer image magick uses a bit more memory to push it over the edge.
+
+If a memory limit is set by ulimit (or via a command line option to image magick), image magick will try to trade memory usage for time, which could be a solution to this issue.
+
+For VP9: The default libvpx on trusty should be new enough, but the default libav is too old. Needs at least libav10
+
+-----
+
+Some other things that might possibly be fixed on trusty (Not sure, either way not a regression):
+
+* https://upload.wikimedia.org/wikipedia/commons/thumb/1/18/Zentralbibliothek_Solothurn_S_I_498_Kosciuszko_Inventarium_02.tif/lossy-page1-800px-Zentralbibliothek_Solothurn_S_I_498_Kosciuszko_Inventarium_02.tif.jpg is purple currently. Rumour is that this may be fixed on newer image magick, but I haven't tested.
+* 16 bit tiff files don't render on vips. I've heard this is fixed on newer vips, but I'm not sure at what point. example https://upload.wikimedia.org/wikipedia/commons/thumb/a/a9/Amelia_earhart_received_by_president_coolidge.tif/lossy-page1-464px-Amelia_earhart_received_by_president_coolidge.tif.jpg (This issue is possible to work around on MW side if the upgrade doesn't fix it)
+",1425656260,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","animated gif conversion seems to take a lot of memory
+
+
+```
+[4844824.480807] convert invoked oom-killer: gfp_mask=0xd0, order=0, oom_score_adj=0
+[4844824.480813] convert cpuset=/ mems_allowed=0-1
+[4844824.480816] CPU: 0 PID: 4631 Comm: convert Not tainted 3.13.0-24-generic #47-Ubuntu
+[4844824.480817] Hardware name: Dell Inc. PowerEdge R410/01V648, BIOS 1.5.3 10/22/2010
+[4844824.480819]  ffff88009c842c00 ffff8801a4eebc48 ffffffff81715ac4 ffff880070972fe0
+[4844824.480823]  ffff8801a4eebcd0 ffffffff817103ff 0000000000000246 ffff88009c842c00
+[4844824.480826]  ffff8801a4eebc90 ffff8801a4eebca0 ffffffff81151587 0000000000000001
+[4844824.480829] Call Trace:
+[4844824.480838]  [<ffffffff81715ac4>] dump_stack+0x45/0x56
+[4844824.480843]  [<ffffffff817103ff>] dump_header+0x7f/0x1f1
+[4844824.480848]  [<ffffffff81151587>] ? find_lock_task_mm+0x27/0x70
+[4844824.480850]  [<ffffffff8115197e>] oom_kill_process+0x1ce/0x330
+[4844824.480854]  [<ffffffff812d0135>] ? security_capable_noaudit+0x15/0x20
+[4844824.480860]  [<ffffffff811b184c>] mem_cgroup_oom_synchronize+0x4fc/0x540
+[4844824.480862]  [<ffffffff811b0da0>] ? mem_cgroup_charge_common+0xa0/0xa0
+[4844824.480864]  [<ffffffff81152104>] pagefault_out_of_memory+0x14/0x80
+[4844824.480866]  [<ffffffff8170ea48>] mm_fault_error+0x8e/0x180
+[4844824.480869]  [<ffffffff81721d41>] __do_page_fault+0x4a1/0x560
+[4844824.480875]  [<ffffffff811112fc>] ? acct_account_cputime+0x1c/0x20
+[4844824.480879]  [<ffffffff8109d76b>] ? account_user_time+0x8b/0xa0
+[4844824.480880]  [<ffffffff8109dd84>] ? vtime_account_user+0x54/0x60
+[4844824.480882]  [<ffffffff81721e1a>] do_page_fault+0x1a/0x70
+[4844824.480886]  [<ffffffff8171e288>] page_fault+0x28/0x30
+[4844824.480889] Task in /mediawiki/job/4628 killed as a result of limit of /mediawiki/job/4628
+[4844824.480891] memory: usage 307200kB, limit 307200kB, failcnt 54
+[4844824.480892] memory+swap: usage 0kB, limit 18014398509481983kB, failcnt 0
+[4844824.480893] kmem: usage 0kB, limit 18014398509481983kB, failcnt 0
+[4844824.480894] Memory cgroup stats for /mediawiki/job/4628: cache:16KB rss:307184KB rss_huge:145408KB mapped_file:12KB writeback:0KB inactive_anon:0KB active_anon:307160KB inactive_file:0KB active_file:0KB unevictable:0KB
+[4844824.480907] [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
+[4844824.480948] [ 4628]    33  4628     5223      427      15        0             0 bash
+[4844824.480950] [ 4630]    33  4630     2868      168      11        0             0 timeout
+[4844824.480952] [ 4631]    33  4631    94085    77321     185        0             0 convert
+[4844824.480953] Memory cgroup out of memory: Kill process 4631 (convert) score 1009 or sacrifice child
+[4844824.490074] Killed process 4631 (convert) total-vm:376340kB, anon-rss:306800kB, file-rss:2484kB
+```",1425644502,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","So I'd have to debug the animated gif problem, and after that I guess we can throw the new imagescaler in the ring as soon as this is resolved.",1425643709,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","I found no other regressions, and - good news! - https://upload.wikimedia.org/wikipedia/commons/thumb/3/3b/WorldAviation.198409.BackCover.pdf/page1-342px-WorldAviation.198409.BackCover.pdf.jpg gets rendered by the new imagescaler. So does https://upload.wikimedia.org/wikipedia/commons/thumb/7/70/John_Stuart_Mill%2C_Considerations_on_Representative_Government_%281st_ed%2C_1861%29.pdf/page1-382px-John_Stuart_Mill%2C_Considerations_on_Representative_Government_%281st_ed%2C_1861%29.pdf.jpg",1425643534,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","the animated gif test throws an error on the HHVM imagescaler:
+
+  <!DOCTYPE html>
+  <html><head>
+  <meta charset=""UTF-8"" />
+  <title>Error generating thumbnail</title>
+  </head>
+  <body>
+  <h1>Error generating thumbnail</h1>
+  <p>
+  Error creating thumbnail: /srv/mediawiki/php-1.25wmf19/includes/limit.sh: line 101: 30955 Killed                  /usr/bin/timeout $MW_WALL_CLOCK_LIMIT /bin/bash -c &quot;$1&quot; 3&gt;&amp;-<br />
+  <br />
+  Error code: 137
+  </p>
+  <!-- /w/thumb_handler.php/5/5d/Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif/850px-Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif -->
+  <!-- mw1152 -->
+
+  </body>
+  </html>
+
+I am still unsure of the reason, I'll investigate this further.",1425642012,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Ok, first bad news: 
+
+the VP9 encoding still doesn't work, but it may just need some additional codecs to be installed. At least this is not a regression :)",1425635091,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","@Bawolff first of all, thanks for the list of urls to test, this is a great starting point.
+Then, I apologize for lagging behind on this, but I have been busy with other priorities after the dev summit, but since this is blocking other tasks, I'll try to get back to this as soon as possible.
+
+I'll plan a migration schedule next week, so that we can also make an announcement.
+
+",1425128064,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",Ping on this?,1424972464,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","A random assortment of images to test that covers a wide variety of formats we use (Just going to give thumbnail urls, hope that's good):
+
+* Super large tiff file: https://upload.wikimedia.org/wikipedia/commons/thumb/3/39/Zentralbibliothek_Z%C3%BCrich_-_Mittelalterliche_Stadt_-_000005203.tif/lossy-page1-1024px-Zentralbibliothek_Z%C3%BCrich_-_Mittelalterliche_Stadt_-_000005203.tif.jpg
+* Small tiff file: https://upload.wikimedia.org/wikipedia/commons/thumb/8/89/%2215th_or_16th_century_Benin_king%22_-_NARA_-_558985.tif/lossy-page1-179px-%2215th_or_16th_century_Benin_king%22_-_NARA_-_558985.tif.jpg
+* large PNG file https://commons.wikimedia.org/wiki/File:Arab_West_Midlands_2011_census.png
+* large full colour png file https://upload.wikimedia.org/wikipedia/commons/thumb/d/d0/Welland_cafe_inside_02.png/450px-Welland_cafe_inside_02.png
+* small png https://upload.wikimedia.org/wikipedia/commons/thumb/9/98/P_sports.png/120px-P_sports.png
+* Thumbnail of VP8 webm file https://upload.wikimedia.org/wikipedia/commons/thumb/d/d3/%27Trick_or_Treat%27_-_Kinetic_Typography.webm/540px--%27Trick_or_Treat%27_-_Kinetic_Typography.webm.jpg
+* VP9 thumbnail: https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/VP9test.webm/512px--VP9test.webm.jpg (This doesn't work on old image scalars, I hope it works on the new one).
+* ogg thumbnail: https://upload.wikimedia.org/wikipedia/commons/thumb/7/75/Reflex-Control-of-Robotic-Gait-Using-Human-Walking-Data-pone.0109959.s016.ogv/300px--Reflex-Control-of-Robotic-Gait-Using-Human-Walking-Data-pone.0109959.s016.ogv.jpg
+* xcf file https://upload.wikimedia.org/wikipedia/commons/thumb/9/90/%22What_a_Brilliant_Idea!%22_Barnstar.xcf/111px-%22What_a_Brilliant_Idea!%22_Barnstar.xcf.png (Note, newer image magick has fixed a bunch of xcf bugs, this file may render differently but ""better"" on the new version)
+* Random djvu image thrown in for good measure: https://upload.wikimedia.org/wikipedia/commons/thumb/3/3b/%27A_morte.djvu/page11-398px-%27A_morte.djvu.jpg
+* PDF that is landscape oriented https://upload.wikimedia.org/wikipedia/commons/thumb/b/b0/GA20891.pdf/page1-800px-GA20891.pdf.jpg (make sure that dimensions are right)
+* Animated GIF https://upload.wikimedia.org/wikipedia/commons/thumb/5/5d/Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif/800px-Cigarette_sales_per_Capita_in_the_United_States%2C_1970_-_2012.gif
+* SVG lang option - make sure https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/SystemLanguage.svg/320px-SystemLanguage.svg.png says ""en"" and https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/SystemLanguage.svg/langfr-320px-SystemLanguage.svg.png says ""fr""
+* Do the svg fonts change significantly https://upload.wikimedia.org/wikipedia/commons/thumb/4/4e/Meta_SVG_fonts.svg/1024px-Meta_SVG_fonts.svg.png (or https://upload.wikimedia.org/wikipedia/commons/thumb/d/d8/MediaWiki_SVG_font_list.svg/920px-MediaWiki_SVG_font_list.svg.png but that would be a pita to compare)
+** SVGs is probably the place that's most likely to get a regression, but unfortunately I don't really know enough to give specific svg features to test.
+
+Some other things that probably won't work, but worth testing on the off chance the update fixes the issue:
+
+* https://upload.wikimedia.org/wikipedia/commons/thumb/3/3b/WorldAviation.198409.BackCover.pdf/page1-342px-WorldAviation.198409.BackCover.pdf.jpg (Currently doesn't work because it takes way to long to render, just curious if that changes with the new server)
+* https://upload.wikimedia.org/wikipedia/commons/thumb/7/70/John_Stuart_Mill%2C_Considerations_on_Representative_Government_%281st_ed%2C_1861%29.pdf/page1-382px-John_Stuart_Mill%2C_Considerations_on_Representative_Government_%281st_ed%2C_1861%29.pdf.jpg JPEG2000 chunks in pdf files. Didn't used to work, maybe upgrade fixed?
+
+-----
+When are you planning to put the new server in rotation? I'd like to make an announcement on Commons:VP before that happens so that users can be on the look out for any rendering changes.",1421251705,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","The first HAT imagescaler is reimaged, and basic testing shows it's working fine.
+
+I would need suggestions on how/what to test before taking it into rotation.",1421081714,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","ffmpeg2theora already includes the patch to disable libav threads in trusty, so we don't have any additional need to repackage things for trusty imagescalers.",1420797761,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Librsvg 2.40.2-1+wm1 is on apt.wikimedia.org and includes the patch at https://git.gnome.org/browse/librsvg/commit/?id=5ba4343bccc7e1765f38f87490b3d6a3a500fde1
+
+I'll look at ffmpeg2theora, then I'll repurpose mw1152 as the test HAT imagescaler",1420796912,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","The patch that @PleaseStand referenced cleanly applies on the librsvg package in trusty, so I'll rebuild it using it alone. I don't think we need a repository, the source package upload should be enough.
+",1420792801,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","Thanks for the feedback.
+
+@Bawolff I guess ffmpeg2theora was there because the package lists are shared with the videoscalers.",1418918016,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","There's also a second patch to librsvg ([[https://gerrit.wikimedia.org/r/#/c/173639/|80dd6ad665610979]]), which fixes a parsing bug in the library. I think even trusty's version of librsvg is too old to already have the patch, which was only applied upstream last month.",1418901297,PHID-USER-3ampiwske4lc434cm6ot,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty",">ffmpeg2theora (disabled libav multithreading)
+
+(Unless I missed something) That's only used in the encoding process (on the video scalars), not during thumbnailing. So I don't think that's needed on image scalars. Additionally, I'm not entirely sure why we have multithreading disabled, but we do use 2 threads (since f1675415) when encoding webm videos with libav (on the video scalars), so the disabling of multithreading for theora videos might not be needed anymore. But I don't know the history behind that, so I may be wrong.",1418891954,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","This might be slightly off-topic, but... Video support on commons would be significantly improved with support of VP9 codec (T55863). In order for MediaWiki (as it currently stands) to make the static placeholder thumbnails for VP9 videos, it would need libav10 backported to the image scalars. So if it is possible to backport the newer version of libav while rebuilding the image scalars, that would be really cool.",1418891525,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","the newer librsvg supports a different security mechanism that should only load resources in the same directory. Given it seems to me that we're already processing SVG images in a dedicated temporary directory, this should be good enough without patching, but I'd like Tim to comment on this",1418890993,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+"Convert eqiad imagescalers to HHVM, Trusty","So, libvps31 and libvpx1 are both at newer versions on trusty and don't need backporting",1418890855,PHID-USER-fdo23otm6ztt674vjqko,False,PHID-TASK-5yndg4e2xdepto2tr2wh,task_subcomment,NA
+Search text for inserting media should be selected on open,"On a page such as http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click Insert/Media
+
+Note that the default text in the search box is the title of the page. 
+
+Click inside the search box.
+
+Default text should disappear but does not. RETURN also does not remove the default text.
+
+Compare to the Link interface which looks similar but behaves correctly. 
+",1418848456,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p76q3pkvm3ujbswasdmd,task_description,resolved
+Search text for inserting media should be selected on open,Also seen in Chrome as of 23 January,1422038288,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p76q3pkvm3ujbswasdmd,task_subcomment,NA
+Search text for inserting media should be selected on open,"On closer examination, I believe that the default text in the media search box is briefly selected, but the selection disappears. Again, compare to Link which does the same thing correctly.
+
+Seen in Firefox. ",1418849300,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p76q3pkvm3ujbswasdmd,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"CSS via load.php sometimes takes as long as 10  seconds to be returned on my local instance.
+If I run
+> redis-cli
+> monitor
+
+I will notice that the log will considerably slow on lines which look like this:
+""GET"" ""wiki:resourceloader:filter:minify-css:7:ef038bf45ab521177624638cbeb85f3d""
+
+Anyone know why this might be happening?
+",1418775220,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_description,resolved
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"This hasn't been an issue for a while afaik.
+
+Related issues that contributed to this:
+* {T112035}
+* {T107377}
+* and more..",1470362201,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Removing the #resourceloader tag. I don't see an easy fix for this, and it does not make sense to optimize ResourceLoader for VirtualBox Shared Folders or NFS. ",1442613254,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 201616 merged by jenkins-bot:
+Allow use of cachefilesd to speed up file system operations
+
+[[https://gerrit.wikimedia.org/r/201616]]",1435623174,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 201616 restored by BryanDavis:
+Use cachefilesd to speed up file system operations
+
+[[https://gerrit.wikimedia.org/r/201616]]",1435251140,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 201616 abandoned by Ori.livneh:
+Use cachefilesd to speed up file system operations
+
+[[https://gerrit.wikimedia.org/r/201616]]",1434390630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 194217 abandoned by BryanDavis:
+Enable stat cache for HHVM fcgi container
+
+Reason:
+Makes things worse rather than better unfortunately.
+
+[[https://gerrit.wikimedia.org/r/194217]]",1428282440,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Relevant:
+* {7a46e84d69a3c912ba9e3c19c0943dba13026ae3}
+* {4ebdd607f5de4fbdf2cfba732452c4df239847c8}
+* {061904a913db144b1d81835b37896cec6a7e5e6d}
+* {3897868db104b88f70569a22613829031fa64f5c}",1448413416,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Relevant:
+* {7a46e84d69a3c912ba9e3c19c0943dba13026ae3}
+* {4ebdd607f5de4fbdf2cfba732452c4df239847c8}
+* {061904a913db144b1d81835b37896cec6a7e5e6d}
+* {3897868db104b88f70569a22613829031fa64f5c}",1428063298,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 201616 had a related patch set uploaded (by BryanDavis):
+Use cachefilesd to speed up file system operations
+
+[[https://gerrit.wikimedia.org/r/201616]]
+",1428018451,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,">>! In T78733#972401, @Jdlrobson wrote:
+> It seems to become an issue as soon as I install multiple wikis
+
+Do we have independent verification of this? It would be significant if true.
+
+",1427791072,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,">>! In T78733#1130869, @Yurik wrote:
+> i wonder if enabling ""zend"" role (switch back to PHP engine) would have solved it.
+
+I would also like to see if anyone has disabled NFS and seen an ongoing performance improvement.  I realize NFS was supposed to //improve// performance, but IIRC it was originally put in before HHVM, and both VirtualBox and our setup have changed since then.",1427346633,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"i wonder if enabling ""zend"" role (switch back to PHP engine) would have solved it.",1426726635,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"I did some debugging with legoktm and less seemed to be the issue. We'd need someone who knows #ResourceLoader inside out. Maybe @Catrope to get to the bottom of this.
+
+I've actually stopped using Vagrant now. It was becoming impractical but the URL I was using was:
+
+http://localhost:8080/w/load.php?debug=false&lang=en&modules=mediawiki.sectionAnchor%7Cmediawiki.ui.button%2Cicon%7Cmobile.pagelist.styles%7Cskins.minerva.beta.images%2Cstyles%7Cskins.minerva.chrome.styles%7Cskins.minerva.content.styles%7Cskins.minerva.drawers.styles%7Cskins.minerva.icons.images%2Cstyles%7Cskins.minerva.tablet.styles&only=styles&skin=minerva&target=mobile&*
+
+I had Flow, MobileFrontend, Apisandbox, Echo, Cite, ConfirmEdit, EventLogging, MultimediaViewer, PageImages roles installed.
+",1426720504,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"@Jdlrobson can you provide the URL of the request that's taking so long? I fear we're all working off the same symptom here (slowness) but not necessarily the same root cause (general NFS performance vs. less compilation, etc.). We need to single in on a particular request that can be consistently profiled. Providing your currently enabled roles would help as well (`vagrant roles list -e`).",1426537801,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Any way forward with this? Any idea of timeline to fix this? Anything I, a frontend engineer can do to help move this along?",1426530689,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Disabling tests made no difference for me @Legoktm
+This hook is only run in test mode anyhow so that didn't surprise me.
+I think the issue is here is purely lots of RL modules and thus files and thus lookup times.
+I'm going to be forced to move off Vagrant next week if this continues, this is very impacting my ability to get things done.
+",1426197873,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Some controlled tests verify that NFS + stat is a part of this performance issue, but maybe not the whole problem.
+
+First I created 5000 files in `vagrant/tmp/mtime` and dropped this into `/var/www/w/mtimes.php`:
+```
+<?php
+
+chdir('/vagrant/tmp/mtime');
+array_map('stat', scandir('.'));
+```
+
+I experimented with NFS [[ http://linux.die.net/man/5/nfs | mount options ]] dealing with the [[ http://docstore.mik.ua/orelly/networking_2ndEd/nfs/ch18_06.htm#nfs2-CHP-18-SECT-6.html | attribute cache ]] and requests to `mtimes.php`.
+
+Using the default options the performance is variable depending on how long you wait between requests. Quick subsequent requests can preempt the default file attribute cache timeout (which is between 3 and 30 seconds, `acregmin`/`acregmax`), while waiting longer results in uncached results. The first two requests below show that the PHP `stat` calls resulted in NFS `getattr` calls to the server, while the final request was made quickly enough that it preempted the cache expiration (no `getattr` calls).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   775067
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.750s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   780068
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m4.228s
+user	0m0.009s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785070
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.249s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785074
+```
+
+Using a fixed attribute cache timeout of 30 (`actimeo=30`) instead of the variable min/max, I was able to get the improved performance more reliably (after an initial warmup).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,acregmin=30,acregmax=30,acdirmax=30,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   790086
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.695s
+user	0m0.010s
+sys	0m0.009s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795087
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.240s
+user	0m0.008s
+sys	0m0.008s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795088
+```
+
+Anyway... upping the NFS attribute cache improves performance drastically in this controlled experiment (~ 90%). However, running the same experiment using the curl request that @Mattflaschen posted yields a lesser (but still significant) performance gain (~ 25%), and the overall request time is still an attrocious 4+ seconds for me.
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   804036
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m5.758s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805076
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m4.270s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805098
+```",1426107959,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Some controlled tests verify that NFS + stat is a part of this performance issue, but maybe not the whole problem.
+
+First I created 5000 files in `vagrant/tmp/mtime` and dropped this into `/var/www/w/mtimes.php`:
+```
+<?php
+
+chdir('/vagrant/tmp/mtime');
+array_map('stat', scandir('.'));
+```
+
+I experimented with NFS [[ http://linux.die.net/man/5/nfs | mount options ]] dealing with the [[ http://docstore.mik.ua/orelly/networking_2ndEd/nfs/ch18_06.htm#nfs2-CHP-18-SECT-6.html | attribute cache ]] and requests to `mtimes.php`.
+
+Using the default options the performance is variable depending on how long you wait between requests. Quick subsequent requests can preempt the default file attribute cache timeout (which is between 3 and 30 seconds, `acregmin`/`acregmax`), while waiting longer results in uncached results. The first two requests below show that the PHP `stat` calls resulted in NFS `getattr` calls to the server, while the final request was made quickly enough that it preempted the cache expiration (no `getattr` calls).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   775067
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.750s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   780068
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m4.228s
+user	0m0.009s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785070
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.249s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785074
+```
+
+Using a fixed attribute cache timeout of 30 (`actimeo=30`) instead of the variable min/max, I was able to get the improved performance more reliably (after an initial warmup).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,acregmin=30,acregmax=30,acdirmax=30,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   790086
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.695s
+user	0m0.010s
+sys	0m0.009s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795087
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.240s
+user	0m0.008s
+sys	0m0.008s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795088
+```
+
+Anyway... upping the NFS attribute cache improves performance drastically in
+this controlled experiment (~ 90%). However, running the same experiment using the curl request that @Mattflaschen posted yields a lesser (but still significant) performance gain (~ 25%), and the overall request time is still an attrocious 4+ seconds for me.
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   804036
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m5.758s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805076
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m4.270s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805098
+```",1426107936,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Some controlled tests verify that NFS + stat is a part of this performance
+issue, but maybe not the whole problem.
+
+First I created 5000 files in `vagrant/tmp/mtime` and dropped this into `/var/www/w/mtimes.php`:
+```
+<?php
+
+chdir('/vagrant/tmp/mtime');
+array_map('stat', scandir('.'));
+```
+
+I experimented with NFS [[ http://linux.die.net/man/5/nfs | mount options ]] dealing with the [[ http://docstore.mik.ua/orelly/networking_2ndEd/nfs/ch18_06.htm#nfs2-CHP-18-SECT-6.html | attribute cache ]] and requests to `mtimes.php`.
+
+Using the default options the performance is variable depending on how long you wait between requests. Quick subsequent requests can preempt the default file attribute cache timeout (which is between 3 and 30 seconds, `acregmin`/`acregmax`), while waiting longer results in uncached results. The first two requests below show that the PHP `stat` calls resulted in NFS `getattr` calls to the server, while the final request was made quickly enough that it preempted the cache expiration (no `getattr` calls).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   775067
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.750s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   780068
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m4.228s
+user	0m0.009s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785070
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.249s
+user	0m0.010s
+sys	0m0.010s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   785074
+```
+
+Using a fixed attribute cache timeout of 30 (`actimeo=30`) instead of the variable min/max, I was able to get the improved performance more reliably (after an initial warmup).
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -m
+/vagrant from 10.11.12.1:/Users/dduvall/Projects/mediawiki/vagrant
+ Flags:	rw,noatime,vers=3,rsize=16384,wsize=16384,namlen=255,acregmin=30,acregmax=30,acdirmax=30,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.11.12.1,mountvers=3,mountport=629,mountproto=udp,local_lock=none,addr=10.11.12.1
+
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   790086
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m2.695s
+user	0m0.010s
+sys	0m0.009s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795087
+vagrant@mediawiki-vagrant:~$ time curl http://127.0.0.1/w/mtimes.php
+
+real	0m0.240s
+user	0m0.008s
+sys	0m0.008s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   795088
+```
+
+Anyway... upping the NFS attribute cache improves performance drastically in
+this controlled experiment (~ 90%). However, running the same experiment using the curl request that @Mattflaschen posted yields a lesser (but still significant) performance gain (~ 25%), and the overall request time is still an attrocious 4+ seconds for me.
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   804036
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m5.758s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805076
+vagrant@mediawiki-vagrant:~$ time curl -s 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' > /dev/null
+
+real	0m4.270s
+user	0m0.010s
+sys	0m0.011s
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl | grep getattr
+nfs v3 client      getattr:   805098
+```",1426107853,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"The following tests are with HHVM and NFS:
+
+Before:
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl
+nfs v4 client        total:   696869 
+------------- ------------- --------
+nfs v4 client         read:     3114 
+nfs v4 client        write:   156537 
+nfs v4 client       commit:     6120 
+nfs v4 client         open:   129880 
+nfs v4 client    open_conf:       37 
+nfs v4 client        close:   129397 
+nfs v4 client      setattr:      129 
+nfs v4 client       fsinfo:        4 
+nfs v4 client        renew:      478 
+nfs v4 client    setclntid:        4 
+nfs v4 client      confirm:        2 
+nfs v4 client         lock:        1 
+nfs v4 client        locku:        1 
+nfs v4 client       access:    59190 
+nfs v4 client      getattr:   194778 
+nfs v4 client       lookup:    11294 
+nfs v4 client  lookup_root:        4 
+nfs v4 client       remove:       35 
+nfs v4 client       rename:        6 
+nfs v4 client       create:        1 
+nfs v4 client     pathconf:        3 
+nfs v4 client       statfs:        2 
+nfs v4 client      readdir:      213 
+nfs v4 client  server_caps:        7 
+nfs v4 client  delegreturn:     5629 
+nfs v4 client  rel_lkowner:        1 
+nfs v4 client      secinfo:        2 
+```
+
+Request (made from outside, generated from using Firefox's Copy as cURL):
+
+time curl 'http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*' -H 'Host: 127.0.0.1:8080' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.5.0' -H 'Accept: */*' -H 'Accept-Language: en-us,en;q=0.9,eng-us;q=0.8,eng;q=0.7,en-gb;q=0.6,en-au;q=0.4,en-ca;q=0.3,en-us.utf-8;q=0.2,en-local;q=0.1' -H 'Accept-Encoding: gzip, deflate' -H 'DNT: 1' -H 'Referer: http://127.0.0.1:8080/wiki/Main_Page' -H 'Cookie: wikiUserName=Admin; mediaWiki.user.bucket%3Amoodbar%403-trigger=3%3Aediting; ext.moodBar%403-tooltip=1; wikiEditor-3-booklet-colors-page=colors; wikiEditor-3-booklet-emoticons-page=emoticons; wikiUserID=1; stopMobileRedirect=true; wikiEditor-0-toolbar-section=advanced; wikiEditor-0-booklet-characters-page=latin; mediaWiki.user.sessionId=cc8787424e30789f; wiki_session=svsh89804l89ns69fpgrv7rbf7' -H 'Connection: keep-alive' -H 'If-Modified-Since: Wed, 11 Mar 2015 00:11:04 GMT'
+
+(output omitted)
+
+    0.01s user 0.00s system 0% cpu 1:10.11 total
+
+After:
+
+```
+vagrant@mediawiki-vagrant:~$ nfsstat -ncl
+nfs v4 client        total:   706258 
+------------- ------------- --------
+nfs v4 client         read:     3114 
+nfs v4 client        write:   159015 
+nfs v4 client       commit:     6290 
+nfs v4 client         open:   131533 
+nfs v4 client    open_conf:       38 
+nfs v4 client        close:   131019 
+nfs v4 client      setattr:      129 
+nfs v4 client       fsinfo:        4 
+nfs v4 client        renew:      482 
+nfs v4 client    setclntid:        4 
+nfs v4 client      confirm:        2 
+nfs v4 client         lock:        1 
+nfs v4 client        locku:        1 
+nfs v4 client       access:    59751 
+nfs v4 client      getattr:   197448 
+nfs v4 client       lookup:    11464 
+nfs v4 client  lookup_root:        4 
+nfs v4 client       remove:       35 
+nfs v4 client       rename:        6 
+nfs v4 client       create:        1 
+nfs v4 client     pathconf:        3 
+nfs v4 client       statfs:        2 
+nfs v4 client      readdir:      213 
+nfs v4 client  server_caps:        7 
+nfs v4 client  delegreturn:     5689 
+nfs v4 client  rel_lkowner:        1 
+nfs v4 client      secinfo:        2 
+```",1426036784,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"I'm using NFS with a Debian Jessie host, with 3000 MB allocated in .settings.yaml, out of 8 GB on my host.
+
+Performance got a lot worse for me recently.  Talking about it with @bd808, I think the cause of it suddenly getting worse may have been enabling VisualEditor (many JS files could interact badly with any MediaWiki-Vagrant and/or RL stat problems).
+
+I'm also currently using the memcached role (currently with 300 MB, but that's one thing I'm experimenting with).  Before, I was using Redis, but Flow is not as well tested with that.  Just recently before switching to memcached, I got some errors that may or may not have been related to caching.
+
+Finally, I had wgResourceLoaderStorageEnabled set to true (but may experiment with turning that off) and I have:
+
+    $wgCacheEpoch = '20141008025959';",1426035181,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"If MF is installed, T91659 could be related.",1426034821,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Enabling HHVM's stat cache is a bust. The implementation in HHVM awesomely uses `inotify` to have the kernel notify it of changes to files on disk. Sadly `inotify` doesn't work on NFS mounts, so HHVM never gets clued in that files are changing.",1425441502,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Magnitudes faster with that patch 12 seconds -> 4 seconds. Still room for improvement though. cc @rmoen @jhernandez who have been having similar issues.
+",1425423870,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,We looked at this for a bit today and may be narrowing in on some parts of the problem. ResouceLoader is doing a lot of file mtime operations. The patch I've posted is one attempt at applying a bandaid to the bleeding patient. I want to dig deeper though and see if there are other settings we can change to make RL happier.,1425423639,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Change 194217 had a related patch set uploaded (by BryanDavis):
+Enable stat cache for HHVM fcgi container
+
+[[https://gerrit.wikimedia.org/r/194217]]
+",1425423205,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"yup. My vagrant is a complete mess right now. :-/ Was hoping to get some time during the dev summit to debug but didn't get the chance.
+",1422576272,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"@jdlrobson, have you experienced this same issue since bumping up your VM's memory?",1422565797,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"This is resurfacing. It seems to become an issue as soon as I install multiple wikis (I just had a fresh install and installed both wikidata and commons roles)
+",1421105335,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Still hitting this issue with a new install.
+Changed less to 0.4.0.
+and then sshing into my vagrant instance and ran `composer update`
+Switched back to 0.5.0 and ran `composer update` and the problem seems to have gone. Strange. Will keep investigating and updating this bug report if/when it comes back.",1420571476,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,">>! In T78733#937057, @matmarex wrote:
+> It upgraded the lessphp library from 0.4.0 to 0.5.0, so I guess they had a performance regression.
+
+Actually https://gerrit.wikimedia.org/r/#/c/174448/ is what upgraded the library, bringing it via composer should have been the same version since Krinkle created a new tag from master.",1419023178,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"It upgraded the lessphp library from 0.4.0 to 0.5.0, so I guess they had a performance regression.",1419022998,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"@legoktm any idea why this has had just a negative effect on performance for me?
+",1419022825,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"This is the commit where it all went wrong for me
+https://gerrit.wikimedia.org/r/#/c/175485/",1419022791,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"I can't view T84960 :(
+Okay now I'm getting somewhere. If I checkout commit Id0221e9f68786758e10b2f222f5e9170898e320d it only takes 1 second. Going to keep investigating till I find the core change that introduced my woes...",1419022343,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Depending on how recently you mean. The result of some `compileFile` calls used to be cached separately some time ago, now it isn't (only the final CSS is).
+
+Perhaps you have some modules there that are being invalidated (incorrectly) too often?",1419019112,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,The cache misses may be due to T84960.,1419019043,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Okay so I debugged this and the source of slowdown seems to be $result = $compiler->compileFile( $fileName ); in compileLessFile
+
+Did something change to do with less recently?
+
+To replicate install MobileFrontend vagrant role and load:
+http://localhost:8080/w/load.php?debug=false&lang=en&modules=mediawiki.ui.button%7Cmobile.pagelist.styles%7Cskins.minerva.alpha.styles%7Cskins.minerva.chrome.styles%7Cskins.minerva.content.styles%7Cskins.minerva.content.styles.beta%7Cskins.minerva.drawers.styles%7Cskins.minerva.icons.styles%7Cskins.minerva.tablet.styles%7Cskins.minerva.tablet.styles.beta&only=styles&skin=minerva&target=mobile&forceprofile=1
+
+On my machine this is taking over 16s to load. Can anyone else confirm similar slowdown?
+",1419018835,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"I'm rarely changing the css. I'm seeing lots of rl-minify-css-cache-misses in the redis trace though. Is it possible my caching isn't setup correctly? Will take look at profiling
+
+Reloading and stopping/starting not helping.
+
+@dduval yeh updating LocalSettings.php to support development for MobileFrontend and installing certain pages seems like a good idea.",1419013265,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Also, since it sounds like you're dependent on a fair amount of custom wiki configuration and content/templates for your development, you might want to consider packaging it as a local or published Vagrant role. (Watch @bd808's part of the recent [[ https://www.mediawiki.org/wiki/File:What%27s_new_with_MediaWiki-Vagrant.webm | tech talk ]] for examples; I'm also available to pair on it.)",1418848863,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"From what I remember when we were troubleshooting this yesterday, HHVM was tacking the CPU during those same moments which makes me think it's not any sort of IO wait on redis that's hanging things up. I second the profiling and maybe restarting HHVM (or `vagrant reload`) for good measure.",1418847882,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"Are you constantly changing your CSS? All the info you've posted looks like RL is either minifying the CSS each time (cache misses), or contacting redis in vagrant is slow.
+
+Have you tried profiling to see what exactly is slow?",1418847540,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+ResourceLoader slow under MediaWiki-Vagrant with VirtualBox,"This is making it near impossible for me to work now :-(
+I really don't want to vagrant destroy as setting up a new wiki instance will take up most of my day.
+",1418847345,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-soqe2cuy2qnpxktzzeed,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"ve.ce.Surface is a 130k beast (>4000 lines) - more than twice as long as Converter and Transaction, the next largest files. Working on it will kill your mouse wheel and sanity.
+
+We should try and break it up by functionality, e.g.
+
+* Key strokes
+* Copy/paste
+* Drag/drop",1418756950,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_description,open
+Break up ve.ce.Surface.js by functionality,"Change #1079329 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (0e82a6db8)%%%
+https://gerrit.wikimedia.org/r/1079329",1730315223,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079329 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (69d7ca482)%%%
+https://gerrit.wikimedia.org/r/1079329",1730223714,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1080733 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Move drag/drop handling code to DragDropHandler%%%
+https://gerrit.wikimedia.org/r/1080733",1730213735,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079324 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Move selection handling code to SelectionManager%%%
+https://gerrit.wikimedia.org/r/1079324",1730213526,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1081991 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (bae9101b7)%%%
+https://gerrit.wikimedia.org/r/1081991",1730211475,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1081991 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (bae9101b7)%%%
+https://gerrit.wikimedia.org/r/1081991",1729522997,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079286 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Move paste handling code to ve.ce.ClipboardHandler%%%
+https://gerrit.wikimedia.org/r/1079286",1729279978,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1080733 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] Move drag/drop handling code to DragDropHandler%%%
+https://gerrit.wikimedia.org/r/1080733",1729090254,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079324 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Move selection handling code to SelectionManager%%%
+https://gerrit.wikimedia.org/r/1079324",1728581141,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change #1079286 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Move paste handling code to ve.ce.PasteHandler%%%
+https://gerrit.wikimedia.org/r/1079286",1728567923,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"After the above patch it dropped to 3,400 lines. Today it is 5,400 (!)",1701814187,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,"Change 248911 merged by jenkins-bot:
+Introduce key down handlers to separate logic from ce surface
+
+[[https://gerrit.wikimedia.org/r/248911]]",1446233373,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+Break up ve.ce.Surface.js by functionality,https://gerrit.wikimedia.org/r/#/c/248911/,1446135119,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-j5vmxwhgpdua5wcyruej,task_subcomment,NA
+When I changed the website link in an infobox all other links got redlinks,"I tried to edit an infobox with the VisualEditor in the German Wikipedia. I changed the website address there.
+But when I closed the ""infobox editor"" all links in the infobox (except of the link I changed) got redlinks.
+
+I think this is only a display error, but anyway I didn't saved the changes I made.",1418491053,PHID-USER-qq2c7r7m35tr32zlbsc3,False,PHID-TASK-dgumy74z3zd6vmd4zme2,task_description,duplicate
+When I changed the website link in an infobox all other links got redlinks,"James, did you confirm this?",1421804311,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-dgumy74z3zd6vmd4zme2,task_subcomment,NA
+When I changed the website link in an infobox all other links got redlinks,This feels like a duplicate.,1419523069,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-dgumy74z3zd6vmd4zme2,task_subcomment,NA
+Performance issues in Internet Explorer 11,"This problem with VisualEditor's performance was reported at MediaWiki.org by User:Leaderboard, who was editing on the English Wikibooks.  The problem is intermittent or at least variable in severity.  It may depend on the size of the page.  It appears to happen at MediaWiki (testing in the sandbox) as well, after about a page's worth of text has been added.  Here's the problem in his own words:
+
+> First , it is too slow to display text which I am typing. It shows it in a slow and slideshow speed. Looks like it's quite slow. And , on Task Manager , it shows that it is using one and only 1 full(utilizes 100% CPU for that) thread for this. It stays at full utilization when I'm typing and becomes very slow. I'm using Internet Explorer 11.
+>
+> When testing using Performance Dashboard , it stays at 5-15% during idle and while typing , it spikes to 50-55% of total CPU usage.
+>
+> %%% Running on a Dell Inspiron 6400 with Intel Core2Duo T7200 @ 2Ghz and 4GB DDR2 with Windows 8.1 tested.""
+",1418411665,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-c2lpx2p2cpizjy235cz3,task_description,declined
+Performance issues in Internet Explorer 11,IE11 support will end within the next year. Not worth making new investments that are specific to how certain browser APIs may perform less well in IE11.,1632431721,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-c2lpx2p2cpizjy235cz3,task_subcomment,NA
+Don't text-transform: capitalize; section headers in the special character inserter,"In Polish, headlines are written with 1st-letter uppercase only. That's why there are ""Polskie diakrytyzowane"" and ""Inne diakrytyzowane"" in [[https://translatewiki.net/wiki/MediaWiki:Visualeditor-specialcharinspector-characterlist-insert/pl|Translatewiki:MediaWiki:Visualeditor-specialcharinspector-characterlist-insert/pl]]. VE displays it wrong (as if English Case Style was Default). {F20866}",1418328634,PHID-USER-gf5juv3z3p75bykrcrhf,False,PHID-TASK-fxifnazewrqgvu4gcnog,task_description,resolved
+Don't text-transform: capitalize; section headers in the special character inserter,"Change 179957 merged by jenkins-bot:
+SpecialCharacterInspector: Don't auto-capitalise the headings
+
+[[https://gerrit.wikimedia.org/r/179957]]",1418744358,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fxifnazewrqgvu4gcnog,task_subcomment,NA
+Don't text-transform: capitalize; section headers in the special character inserter,"Change 179957 had a related patch set uploaded (by Jforrester):
+SpecialCharacterInspector: Don't auto-capitalise the headings
+
+[[https://gerrit.wikimedia.org/r/179957]]
+
+#patch-for-review",1418664161,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fxifnazewrqgvu4gcnog,task_subcomment,NA
+Parameter entries aren't indented in the transclusion dialog's booklet layout in VisualEditor when using the OOUI MediaWiki theme,"See screenshot:
+
+{F20244}",1418326903,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sqhibubgcam4rw6zg2im,task_description,resolved
+Parameter entries aren't indented in the transclusion dialog's booklet layout in VisualEditor when using the OOUI MediaWiki theme,"Change 179198 merged by jenkins-bot:
+MediaWiki theme: Copy .theme-oo-ui-outline{Controls,Option}Widget from Apex
+
+[[https://gerrit.wikimedia.org/r/179198]]",1418335593,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sqhibubgcam4rw6zg2im,task_subcomment,NA
+Parameter entries aren't indented in the transclusion dialog's booklet layout in VisualEditor when using the OOUI MediaWiki theme,"Change 179198 had a related patch set uploaded (by Bartosz Dziewoński):
+Copy .theme-oo-ui-{outlineControlsWidget, outlineOptionWidget} from Apex to MediaWiki
+
+[[https://gerrit.wikimedia.org/r/179198]]
+
+#patch-for-review",1418332521,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sqhibubgcam4rw6zg2im,task_subcomment,NA
+"""Uncaught TypeError: Cannot read property 'getSurface' of null"", on undoing a comment in block quote.","Environment- test2, beta, Production
+Browser- Chrome 39
+
+1> Insert a comment.Click on ""Insert"" button to close the dialog.
+2> While the comment is still highlighted, select any option from the Heading format list.For ex- select Block quote
+3> Click to undo(keeping the comment highlighted).Notice the icon and the comment pop-up get detached. Also, JS error ""Uncaught TypeError: Cannot read property 'getSurface' of null"" shows up in console.
+
+See screenshot.
+",1418315290,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-fpwsjr2z43gzastjf6ak,task_description,declined
+"""Uncaught TypeError: Cannot read property 'getSurface' of null"", on undoing a comment in block quote.","There are over 300+ calls to .getSurface() in VisualEditor.
+
+It's important to distinguish between instances of an error and categories of errors. Sometimes errors are unique by their message, other times they are unique by their cause or stack. Cases of bad method calls vary by their caller.
+
+Let's assume the 2014 reproduction steps for a specific case of a bad method call ocurred are not related.",1692891005,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fpwsjr2z43gzastjf6ak,task_subcomment,NA
+"""Uncaught TypeError: Cannot read property 'getSurface' of null"", on undoing a comment in block quote.","Seeing quite of a few errors in log:
+```
+at ve.ce.FocusableNode.getBoundingRect  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:501:932
+at ve.ce.LinearSelection.getSelectionBoundingRect  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:610:833
+at ve.ce.LinearSelection.getSelectionFocusRect  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:612:871
+at ve.ui.Surface.scrollSelectionIntoView  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:694:403
+at ve.ui.Surface.adjustVisiblePadding  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:698:804
+at ve.ui.Surface.onViewPosition  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:696:537
+at OO.EventEmitter.emit  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.centralNotice.choiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2CstartUp%7Cext.centralauth.ForeignApi%2Ccentralautologin%7Cext.cite.ux-enhancements%7Cext.cx.entrypoints.languagesearcher.init%7Cext.cx.entrypoints.mffrequentlanguages%7Cext.cx.eventlogging.campaigns%7Cext.cx.model%7Cext.dismissableSiteNotice%2CeventLogging%2CnavigationTiming%2Cpopups%2CshortUrl%2CwikimediaEvents%7Cext.echo.centralauth%7Cext.growthExperiments.SuggestedEditSession%7Cext.relatedArticles.readMore.bootstrap%7Cjquery%2Coojs%2Csite%7Cjquery.client%2Ccookie%7Cmediawiki.ForeignApi%2CString%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Crouter%2Cstorage%2Ctemplate%2Cuser%2Cutil%2CvisibleTimeout%7Cmediawiki.ForeignApi.core%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.page.watch.ajax%7Cmediawiki.template.mustache%7Cmediawiki.ui.anchor%7Cmobile.init%2Cstartup%7Cmobile.ooui.icons%7Cmobile.pagelist.styles%7Cmobile.pagesummary.styles%7Cmobile.placeholder.images%7Cmobile.startup.images%7Cmw.cx.SiteMapper%7Cmw.externalguidance.init%7Cskins.minerva.icons.images.scripts.misc%7Cskins.minerva.icons.page.issues.default.color%7Cskins.minerva.icons.page.issues.medium.color%7Cskins.minerva.icons.page.issues.uncolored%7Cskins.minerva.messageBox.styles%7Cskins.minerva.scripts&skin=minerva&version=bxy2z:302:399
+at https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2Cdiffing%2CeditCheck%2Cicons%2Clanguage%2Cmediawiki%2CmobileArticleTarget%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2CsupportCheck%2Cwelcome%7Cext.visualEditor.core.mobile%2Cutils%7Cext.visualEditor.mwimage.core&skin=minerva&version=l4yl8:816:614
+at mightThrow  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.centralNotice.choiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2CstartUp%7Cext.centralauth.ForeignApi%2Ccentralautologin%7Cext.cite.ux-enhancements%7Cext.cx.entrypoints.languagesearcher.init%7Cext.cx.entrypoints.mffrequentlanguages%7Cext.cx.eventlogging.campaigns%7Cext.cx.model%7Cext.dismissableSiteNotice%2CeventLogging%2CnavigationTiming%2Cpopups%2CshortUrl%2CwikimediaEvents%7Cext.echo.centralauth%7Cext.growthExperiments.SuggestedEditSession%7Cext.relatedArticles.readMore.bootstrap%7Cjquery%2Coojs%2Csite%7Cjquery.client%2Ccookie%7Cmediawiki.ForeignApi%2CString%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Crouter%2Cstorage%2Ctemplate%2Cuser%2Cutil%2CvisibleTimeout%7Cmediawiki.ForeignApi.core%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.page.watch.ajax%7Cmediawiki.template.mustache%7Cmediawiki.ui.anchor%7Cmobile.init%2Cstartup%7Cmobile.ooui.icons%7Cmobile.pagelist.styles%7Cmobile.pagesummary.styles%7Cmobile.placeholder.images%7Cmobile.startup.images%7Cmw.cx.SiteMapper%7Cmw.externalguidance.init%7Cskins.minerva.icons.images.scripts.misc%7Cskins.minerva.icons.page.issues.default.color%7Cskins.minerva.icons.page.issues.medium.color%7Cskins.minerva.icons.page.issues.uncolored%7Cskins.minerva.messageBox.styles%7Cskins.minerva.scripts&skin=minerva&version=bxy2z:199:881
+at process  https://hi.m.wikipedia.org/w/load.php?lang=hi&modules=ext.centralNotice.choiceData%2Cdisplay%2CgeoIP%2CimpressionDiet%2CkvStore%2CstartUp%7Cext.centralauth.ForeignApi%2Ccentralautologin%7Cext.cite.ux-enhancements%7Cext.cx.entrypoints.languagesearcher.init%7Cext.cx.entrypoints.mffrequentlanguages%7Cext.cx.eventlogging.campaigns%7Cext.cx.model%7Cext.dismissableSiteNotice%2CeventLogging%2CnavigationTiming%2Cpopups%2CshortUrl%2CwikimediaEvents%7Cext.echo.centralauth%7Cext.growthExperiments.SuggestedEditSession%7Cext.relatedArticles.readMore.bootstrap%7Cjquery%2Coojs%2Csite%7Cjquery.client%2Ccookie%7Cmediawiki.ForeignApi%2CString%2CTitle%2CUri%2Capi%2Cbase%2Ccldr%2Ccookie%2Cexperiments%2CjqueryMsg%2Clanguage%2Crouter%2Cstorage%2Ctemplate%2Cuser%2Cutil%2CvisibleTimeout%7Cmediawiki.ForeignApi.core%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%7Cmediawiki.page.watch.ajax%7Cmediawiki.template.mustache%7Cmediawiki.ui.anchor%7Cmobile.init%2Cstartup%7Cmobile.ooui.icons%7Cmobile.pagelist.styles%7Cmobile.pagesummary.styles%7Cmobile.placeholder.images%7Cmobile.startup.images%7Cmw.cx.SiteMapper%7Cmw.externalguidance.init%7Cskins.minerva.icons.images.scripts.misc%7Cskins.minerva.icons.page.issues.default.color%7Cskins.minerva.icons.page.issues.medium.color%7Cskins.minerva.icons.page.issues.uncolored%7Cskins.minerva.messageBox.styles%7Cskins.minerva.scripts&skin=minerva&version=bxy2z:200:544
+```
+https://logstash.wikimedia.org/app/dashboards#/doc/logstash-*/logstash-default-1-7.0.0-1-2023.06.12?id=cGYgsIgBEBRX9obd4Pwh",1686613889,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-fpwsjr2z43gzastjf6ak,task_subcomment,NA
+"""Uncaught TypeError: Cannot read property 'getSurface' of null"", on undoing a comment in block quote.","Screenshot 
+{F20838}",1418315346,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-fpwsjr2z43gzastjf6ak,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"1. Click on https://www.mediawiki.org/w/index.php?title=VisualEditor/status&veaction=edit
+2. Wait for editor to load
+3. Use find-and-replace
+4. Try to type ""now support ""
+5. Observe system die in flames after 'n' was typed, not letting you type 'o' yet, let alone the rest.
+6. Cry.
+
+250ms is our normal threshold. Let's do that.",1418275115,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_description,resolved
+Limit effect of search-and-replace assessment on long documents,"This is now better, but not great in very extreme cases.",1420467860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Change 180635 merged by jenkins-bot:
+Use viewport clipping when lots of search results found
+
+[[https://gerrit.wikimedia.org/r/180635]]",1420466184,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Change 180195 merged by jenkins-bot:
+Limit number of find and replace results to render
+
+[[https://gerrit.wikimedia.org/r/180195]]",1420465915,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Change 180635 had a related patch set uploaded (by Esanders):
+Use viewport clipping when lots of search results found
+
+[[https://gerrit.wikimedia.org/r/180635]]
+
+#patch-for-review",1418849860,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"getVisibleRange is only ever going to be an estimate due to floats and position absolute, and you'll probably add +/- 50% for good measure. Throwing in a computed style calls ( .css('position') ) is going to make it several times slower.",1418755519,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Yeah I was thinking of binary search too, but I don't know how reliable it'll be because the DOM sequence is similar to but not the same as the rendered visual sequence (due to floated things; good call on absolute positioning but I don't think you'll see absolutely positioned editable text very often).
+
+getVisibleRange() sounds interesting, and that may well be binary search-able if you stick to known-safe things (like .css( 'position' ) === 'static' maybe?)",1418755060,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"So I considered the render on screen things, and as you point out you'd have occasional problems with floated things or worse, position absolute things. As you point it your approach doesn't help you work out where to start rendering and calculating if something is on screen is basically as expensive as rendering it (getClientRects being the bottleneck). As viable solution might be to do a binary search. Even on a document of 100k characters that would only be 16 checks.
+
+That shouldn't be too difficult to implement, the only problem being we'd have to re-evaluate on window resize and scroll (although debounced), but being a binary search it should be efficient enough. In might even make sense to push that functionality up to the surface view, so you can just ask it to getVisibleRange.",1418754195,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"Change 180195 had a related patch set uploaded (by Esanders):
+Limit number of find and replace results to render
+
+[[https://gerrit.wikimedia.org/r/180195]]
+
+#patch-for-review",1418745343,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"I wonder how much not rendering off-screen would save. You'd save on a bunch of DOM modification, but you'd still have to find every result and compute a rect for it to find out whether it's off-screen. I don't know how much time is spent in the DM search vs the highlight rendering, let's find out.
+
+We could also refactor the DM code so it returns one result at a time instead of all at once, then stop once we hit the first off-screen result. This isn't quite perfect (there might be results in floated image captions that appear significantly above/below the text immediately before/after in the DM/DOM), and it would break the ""Kth of N results"" thing, so maybe we could try a hybrid approach where we only do full rendering (i.e. the current approach, maybe without off-screen highlights) if there are <=50 results, and above that we aggressively try to stop searching and rendering as soon as we can, while still allowing the user to force the next result to be found and highlighted by pressing next. Or we could base the approach on finding and rendering at most 10 results before and 10 after the currently highlighted one.
+
+(Another problem that I don't quite have a solution for: if the user is scrolled most of the way down the page, how do you know where results start being visible without just trying them all in sequence)",1418743887,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+Limit effect of search-and-replace assessment on long documents,"That makes it less likely to explode, but doesn't fix the problem, which is that rendering 16000 highlights is too much. There should either be a cap, or some smartness about not rendering off screen.",1418742498,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-qhw2xsmje3nm75l6hyqw,task_subcomment,NA
+"Chinese full stop disappears at the end of paragraphs, if preceded by ref tags","In VisualEditor, it is not always possible to save a paragraph that ends with <ref>(cite source)</ref>。 Upon saving the page, the full stop disappears.  See [[ https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&offset=20141206172053#Symbol_after_citation_disappear_after_edit_50625 | the original report ]].
+
+I successfully added one [[ https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=1309016&oldid=1228107 | in my sandbox at MediaWiki ]], but (a) I pasted the Chinese full stop into the text, rather than entering it normally, and (b) when I pasted it after the ref, it gave me a black sun before the full stop.  Also, I'm running Safari on a Mac, so it may be browser or OS dependent.",1418190956,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gpbnxuzghyxgmcl5cika,task_description,resolved
+"Chinese full stop disappears at the end of paragraphs, if preceded by ref tags",I've re-tested and this seems to now work.,1440120521,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gpbnxuzghyxgmcl5cika,task_subcomment,NA
+"Japanese text disappears (kanji and maybe hiragana, not katakana) when you are writing list entries","[[ https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&offset=20141204053320#Japanese_in_lists_51392 | Original report from MediaWiki.org: ]] from a logged-out editor, on 4 December 2014:
+
+""I just tried to add list items in Japanese. Katakana seemed ok in lists but kanji and maybe hiragana too seemed to delete automatically when pressing enter to go to the next list item.""
+
+I believe that this is different from T74619 in which katakana can't be typed at all.",1418188190,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yfvk4vo7aqne3mus4xte,task_description,resolved
+"Japanese text disappears (kanji and maybe hiragana, not katakana) when you are writing list entries","As far as I can tell, this issue and other Japanese text entry issues are all now fixed. Sorry it took so long to confirm!",1435941289,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yfvk4vo7aqne3mus4xte,task_subcomment,NA
+"Japanese text disappears (kanji and maybe hiragana, not katakana) when you are writing list entries","Confirmed in production. Somehow all works in betalbs and test2. 
+
+This issue is most likely the same bug as T74619.",1418260874,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-yfvk4vo7aqne3mus4xte,task_subcomment,NA
+"Bottom border of text box in save dialog only appears when zoomed in, in VisualEditor when using the OOjs UI MediaWiki theme","See screenshot:
+
+{F20270}",1418156285,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hmqwa7xe2lrqdvsrno4s,task_description,resolved
+"Bottom border of text box in save dialog only appears when zoomed in, in VisualEditor when using the OOjs UI MediaWiki theme",Can't reproduce.,1420929029,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-hmqwa7xe2lrqdvsrno4s,task_subcomment,NA
+Layout of the image size options is jarring in VisualEditor when using the OOjs UI MediaWiki theme,"See screenshots:
+
+{F20264}{F20266}",1418156178,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xfimimrnkl7a4samm5xn,task_description,resolved
+Layout of the image size options is jarring in VisualEditor when using the OOjs UI MediaWiki theme,This was fixed in the great MediaWiki theme re-write for wmf13.,1420853400,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xfimimrnkl7a4samm5xn,task_subcomment,NA
+Layout of the image size options is jarring in VisualEditor when using the OOjs UI MediaWiki theme,"One of the screenshots got converted to TIFF locally, it seems.",1418327272,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xfimimrnkl7a4samm5xn,task_subcomment,NA
+Layout of the image size options is jarring in VisualEditor when using the OOjs UI MediaWiki theme,It doesn't seem very different from Apex to me. Also what's up with the attachments on this task?,1418327170,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-xfimimrnkl7a4samm5xn,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"See screenshot:
+
+{F20251}
+
+(A problem in Apex too, but feels worse in MW.)",1418155768,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_description,resolved
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,Verified the fix in Betalabs and test2,1421366652,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,Checked in betalabs - see the attached screenshot.{F28262},1421103113,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,">>! In T78039#966523, @Krenair wrote:
+> I checked the resolution to this bug on deployment-prep and found that to close the category popup you actually have to click outside the button which opened it. But I would expect that clicking the button again (while the popup is still open) would close it.
+
+Open a ticket?",1420833547,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,I checked the resolution to this bug on deployment-prep and found that to close the category popup you actually have to click outside the button which opened it. But I would expect that clicking the button again (while the popup is still open) would close it.,1420833140,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"@Ricordisamoa, since you subscribed the same minute that @Jdforrester-WMF resolved this (and removed your subscription in the process), I'm assuming it was just Phabricator's lack of conflict detection. See T78236",1420832447,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,@Jdforrester-WMF Why shouldn't I be subscribed?,1420821946,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"Change 183486 merged by jenkins-bot:
+Fix styling of MWCategoryWidget to match MW theme
+
+[[https://gerrit.wikimedia.org/r/183486]]",1420821413,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,The rounded corners are just left over the from Apex skin where they looked less out of place. Fixed in patch above.,1420721158,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"Change 183486 had a related patch set uploaded (by Esanders):
+Fix styling of MWCategoryWidget to match MW theme
+
+[[https://gerrit.wikimedia.org/r/183486]]
+
+#patch-for-review",1420721044,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"(The category selector really should be implemented using the kind of multiselect widget used here by Phabricator for lists of projects or people subscribed to the task, etc. (Phab calls them ""tokenizers"", which if you ask me is a pretty silly name.) Some of MediaWiki's forms also use something similar, e.g. on <https://wikitech.wikimedia.org/wiki/Special:NovaSecurityGroup> (alas, you need to be logged in to view that page, apparently).)",1420679005,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"Whatever you call it, (nearly) everything else in VE is using the standard form style first used in MediaWiki UI, while this is using something different and therefore looks weird and silly. ",1420678026,PHID-USER-2z6624adiq3sr74fvzu6,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,">>! In T78039#942748, @Jay8g wrote:
+> Why aren't we just using a standard mw-ui form for this?
+
+Nothing in VisualEditor or the new OOjs UI front-end has anything to do with MediaWiki UI, which was built as an //ad hoc// provision for systems not yet using OOjs UI.",1420657809,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,"I agree, lets use the standard form field for this.",1420485532,PHID-USER-flenunkasbjk4topxvaj,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme,Why aren't we just using a standard mw-ui form for this?,1419391070,PHID-USER-2z6624adiq3sr74fvzu6,True,PHID-TASK-wegjd34ahvbrxxjftgql,task_subcomment,NA
+Local Info and Discussions for Visual Editor,"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/64 //
+
+== Narrative ==
+
+As a user, I want localinfo and discussion pages forVisual Editor Beta Features, so I can read them and respond in my language.
+
+
+
+== Acceptance Criteria ==
+
+Enable local links for info and discussion pages forthe VisualEditor Beta Features.
+
+
+
+== Related Bugs ==
+
+== Related Stories ==
+
+See more VE BF feature requirements here:
+
+ [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] ",1418054449,PHID-USER-64gvupsl7ajewpshylma,False,PHID-TASK-tobiwpavuldjyxvbgv2n,task_description,resolved
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,This would be hugely appreciated.,1417905944,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-t6gmkam4z4t2upv65tdm,task_description,resolved
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,Thanks!,1418681597,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,Herald rule H10 created.,1418681581,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,">>! In T76954#849205, @Aklapper wrote:
+> Summarizing to check I get this right before executing:
+> 
+> So whenever a task's projects include any of
+> * VisualEditor-ContentEditable
+> * VisualEditor-ContentLanguage
+> * VisualEditor-CopyPaste
+> * VisualEditor-DataModel
+> * VisualEditor-EditingTools
+> * VisualEditor-Initialisation
+> * VisualEditor-InterfaceLanguage
+> * VisualEditor-MediaWiki
+> * VisualEditor-MediaWiki-Links
+> * VisualEditor-MediaWiki-Media
+> * VisualEditor-MediaWiki-Mobile
+> * VisualEditor-MediaWiki-References
+> * VisualEditor-MediaWiki-Templates
+> * VisualEditor-Performance
+> * VisualEditor-Tables
+> automatically add project ""VisualEditor""?
+
+Yes.
+
+> Note there are two options: Take this actions //every time// or //only the first time// this rule matches. I guess you want everytime.
+
+I think that would make sense, yes.
+
+> Also note that whenever you create a new VE-* project the rule needs to be adjusted. It's not possible to define some placeholders like * for parts of project names like ""begins with the string"".
+
+Yeah, I guessed as much.",1418680979,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,">>! In T76954#848827, @Qgil wrote:
+> If the Phabricator team would be included in the Herald policy, I could help you. @aklapper, your choice.  :)
+
+I think that makes sense, still would like to discuss with the team first due to security implications.",1418680245,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,"Summarizing to check I get this right before executing:
+
+So whenever a task's projects include any of
+* VisualEditor-ContentEditable
+* VisualEditor-ContentLanguage
+* VisualEditor-CopyPaste
+* VisualEditor-DataModel
+* VisualEditor-EditingTools
+* VisualEditor-Initialisation
+* VisualEditor-InterfaceLanguage
+* VisualEditor-MediaWiki
+* VisualEditor-MediaWiki-Links
+* VisualEditor-MediaWiki-Media
+* VisualEditor-MediaWiki-Mobile
+* VisualEditor-MediaWiki-References
+* VisualEditor-MediaWiki-Templates
+* VisualEditor-Performance
+* VisualEditor-Tables
+automatically add project ""VisualEditor""?
+
+Note there are two options: Take this actions //every time// or //only the first time// this rule matches. I guess you want everytime.
+Also note that whenever you create a new VE-* project the rule needs to be adjusted. It's not possible to define some placeholders like * for parts of project names like ""begins with the string"".",1418680167,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor,"If the Phabricator team would be included in the Herald policy, I could help you. @aklapper, your choice.  :)",1418675152,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-t6gmkam4z4t2upv65tdm,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","When editing the infobox in https://fr.wikipedia.org/w/index.php?title=S%C3%A9bastien_Texier&veaction=edit , the heading is misaligned (overlapping with button), see screenshot.
+
+{F19186}",1417892100,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_description,resolved
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","The main place people encounter this is where all three labels are very long; this ""fix"" doesn't actually help them.",1433457500,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Well, no, it doesn't change anything except for the case where the label would be clipped.
+
+| | Normal label | Long label
+| | -- | -- |
+| Before | {F174792,size=full} | {F174794,size=full}
+| -- |
+| After | {F174798,size=full} | {F174796,size=full}
+| -- |",1433457742,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Well, no, it doesn't change anything except for the case where the label would be clipped.
+
+| | Normal label | Long label
+| | -- | -- |
+| Before | {F174792,size=full} | {F174794,size=full}
+| -- |
+| After | {F174796,size=full} | {F174798,size=full}
+| -- |",1433457714,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Well, no, it doesn't change anything except for the case where the label would be clipped.
+
+Before:
+{F174787}
+After:
+{F174790}",1433457448,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",">>! In T76947#1339343, @matmarex wrote:
+> Worth a #user-notice, I think? I believe this improves our UI in several languages significantly. :)
+
+And makes it look worse in others. We'll need to test it post-release to see what further tweaks we need to make VE-side.",1433457396,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Worth a #user-notice, I think? I believe this improves our UI in several languages significantly. :)",1433457357,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Change 160812 merged by jenkins-bot:
+ProcessDialog: Don't center the title label if there's not enough space
+
+[[https://gerrit.wikimedia.org/r/160812]]",1433457158,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Change 160812 had a related patch set uploaded (by Bartosz Dziewoński):
+ProcessDialog: Don't center the title label if there's not enough space
+
+[[https://gerrit.wikimedia.org/r/160812]]
+",1433347960,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",">>! In T76947#1187412, @Whatamidoing-WMF wrote:
+> A few images to add to this problem (images show Russian): 
+
+""tempfile.ru"" is not very reassuring about the lifetime of these links, so let's copy here.
+
+>   - save: http://img1.tempfile.ru/14007/217cf59a63/72ca3ef85264e46dc8940df5.png
+{F109767}
+>   - review: http://img5.tempfile.ru/14007/21e2c7cd06/db0830133840b484326c1ae5.png
+{F109769}
+>   - in templates: http://img1.tempfile.ru/14007/2141f10bfd/81132103a7b84539c4196b6c.png
+{F109771}
+>   - when add already used ref: http://tempfile.ru/view/14007/21b40770ca/cd799edc8198704e4665e283.png
+{F109774}",1428439216,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","A few images to add to this problem (images show Russian): 
+
+  - save: http://img1.tempfile.ru/14007/217cf59a63/72ca3ef85264e46dc8940df5.png
+  - review: http://img5.tempfile.ru/14007/21e2c7cd06/db0830133840b484326c1ae5.png
+  - in templates: http://img1.tempfile.ru/14007/2141f10bfd/81132103a7b84539c4196b6c.png
+  - when add already used ref: http://tempfile.ru/view/14007/21b40770ca/cd799edc8198704e4665e283.png
+",1428438606,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",FYI this was brought up again by a user [[ https://phabricator.wikimedia.org/F103020 | testing Citoid ]].,1427231816,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","https://www.mediawiki.org/wiki/VisualEditor/Feedback#terrible_title_in_the_form_of_saving_the_page_52517
+
+save:
+{F38963}
+
+review: 
+{F38964}
+
+in templates: 
+{F38965}
+
+when add already used ref:
+{F38966}",1423569342,PHID-USER-5joeladhczukimiv4rwl,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",https://www.mediawiki.org/wiki/VisualEditor/Feedback#terrible_title_in_the_form_of_saving_the_page_52517,1421176643,PHID-USER-5joeladhczukimiv4rwl,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","This just became worse with the new design, IMHO.",1421163821,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Same at the German Wikipedia (check the Saving dialog). The French workaround to this one was changing the equivalent of ""Save your changes"" to ""Contribution""...",1417895052,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","Thanks, Bartosz. The current behavior is clearly undesirable (useless or partially overlapping dialog titles); we may need to do both (shorten some button labels and optimize placement). I defer to @Jdforrester-WMF on the final approach.",1417892855,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","The solution would be not to absolutely center the title if it can't fit.
+
+| Before | After |
+| ---------|------------ |
+| {F19192,size=full} | {F19190,size=full} |
+",1417892482,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages","This is the same issue as T70571, where this has been declined (the suggested solution is to make the button labels shorter). The abandoned patch https://gerrit.wikimedia.org/r/160812 would probably still work.",1417892327,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+"Heading of template editor is centered; hence most text currently covered by ""Apply changes"" button in some languages",{F19186},1417892184,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hlzqzpsz6w4c5bzdi4i5,task_subcomment,NA
+A number of VisualEditor dialogs do not cover full screen when 'full' size,"A number of VisualEditor dialogs do not cover full screen when 'full' size.
+
+I can't reproduce this in OOUI demo.
+
+To reproduce:
+
+1. Open a page in VisualEditor
+2. Insert → Template (or Insert → Media, or (hamburger) → Options, or others)
+3. Resize browser window until it is narrower than the dialog
+
+{F19019}",1417791464,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_description,resolved
+A number of VisualEditor dialogs do not cover full screen when 'full' size,"Checked in beta(Chrome, Safari) - VE dialogs fill up the reduced browser window.",1421784791,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_subcomment,NA
+A number of VisualEditor dialogs do not cover full screen when 'full' size,"Change 185094 merged by jenkins-bot:
+ToolbarDialogWindowManager: Don't pollute parent's .static.sizes
+
+[[https://gerrit.wikimedia.org/r/185094]]",1421286417,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_subcomment,NA
+A number of VisualEditor dialogs do not cover full screen when 'full' size,"Change 185094 had a related patch set uploaded (by Bartosz Dziewoński):
+ToolbarDialogWindowManager: Don't pollute parent's .static.sizes
+
+[[https://gerrit.wikimedia.org/r/185094]]
+
+#patch-for-review",1421280963,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_subcomment,NA
+A number of VisualEditor dialogs do not cover full screen when 'full' size,Caused by 5eb7294a748231dca841d49896ccfdd630baef7c (https://gerrit.wikimedia.org/r/#/c/174491/).,1421280019,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wxrtx43jaw7tpwg7bd7l,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"[x] Deprecate
+[x] Replace all code instances in Wikimedia core & deployed extensions
+  [x] `iconTitle` https://codesearch.wmflabs.org/search/?q=iconTitle&i=nope&files=&repos=
+    [x] Kartographer
+    [x] BlueSpiceVisualEditorConnector
+    [x] CollaborationKit
+    [x] CX
+    [x] LanguageTool
+    [x] PerformanceInspector
+    [x] WikibaseQualityConstraints
+  [x] `setIconTitle` https://codesearch.wmflabs.org/search/?q=setIconTitle&i=nope&files=&repos=
+    [x] MW core APISandBox
+  [x] `indicatorTitle` https://codesearch.wmflabs.org/search/?q=indicatorTitle&i=nope&files=&repos=
+  [x] `setIndicatorTitle` https://codesearch.wmflabs.org/search/?q=setIndicatorTitle&i=nope&files=&repos=
+    [x] VE
+[x] Remove – https://gerrit.wikimedia.org/r/#/c/oojs/ui/+/495949/",1417635365,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_description,resolved
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 484850 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Re-introduce: Replace deprecated `setIndicatorTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/484850]]",1548117786,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482145 **merged** by jenkins-bot:
+[mediawiki/core@master] Replace deprecated `setIconTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/482145]]",1548116383,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 484850 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/VisualEditor@master] Re-introduce: Replace deprecated `setIndicatorTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/484850]]",1547705628,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 483796 **merged** by jenkins-bot:
+[mediawiki/core@master] Update OOUI to v0.30.1
+
+[[https://gerrit.wikimedia.org/r/483796]]",1547227735,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 483796 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/core@master] Update OOUI to v0.30.1
+
+[[https://gerrit.wikimedia.org/r/483796]]",1547223618,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),VE change caused T212975. Also inspired T212977,1546899248,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482132 **merged** by jenkins-bot:
+[mediawiki/extensions/ContentTranslation@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482132]]",1546600138,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482130 **merged** by jenkins-bot:
+[mediawiki/extensions/CollaborationKit@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482130]]",1546599778,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482128 **merged** by jenkins-bot:
+[mediawiki/extensions/Kartographer@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482128]]",1546599775,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482138 **merged** by jenkins-bot:
+[mediawiki/extensions/WikibaseQualityConstraints@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482138]]",1546595634,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482137 **merged** by jenkins-bot:
+[mediawiki/extensions/PerformanceInspector@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482137]]",1546575123,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482136 **merged** by jenkins-bot:
+[mediawiki/extensions/LanguageTool@master] Use standard `title` and add better supported screen reader label on top
+
+[[https://gerrit.wikimedia.org/r/482136]]",1546550390,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482127 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Replace deprecated `setIndicatorTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/482127]]",1546549021,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482145 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/core@master] Replace deprecated `setIconTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/482145]]",1546548267,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482138 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/WikibaseQualityConstraints@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482138]]",1546547455,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482137 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/PerformanceInspector@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482137]]",1546547141,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482136 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/LanguageTool@master] Use standard `title` and add better supported screen reader label on top
+
+[[https://gerrit.wikimedia.org/r/482136]]",1546546921,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482132 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/ContentTranslation@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482132]]",1546546342,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482130 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/CollaborationKit@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482130]]",1546546054,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482128 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/Kartographer@master] Replace deprecated `iconTitle` with `title`
+
+[[https://gerrit.wikimedia.org/r/482128]]",1546545808,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 482127 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/VisualEditor@master] Replace deprecated `setIndicatorTitle` with `setTitle`
+
+[[https://gerrit.wikimedia.org/r/482127]]",1546545190,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 480696 **merged** by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE]: Deprecate `iconTitle` and `indicatorTitle`
+
+[[https://gerrit.wikimedia.org/r/480696]]",1546542514,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Change 480696 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[oojs/ui@master] [DEPRECATING CHANGE]: Deprecate `iconTitle` and `indicatorTitle`
+
+[[https://gerrit.wikimedia.org/r/480696]]",1545196091,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter),"Potential violators:
+```
+
+core/resources/src/mediawiki.special.apisandbox/apisandbox.js:
+  104  					ok = ok || suppressErrors;
+  105  					that.setIcon( ok ? null : 'alert' );
+  106: 					that.setIconTitle( ok ? '' : mw.message( 'apisandbox-alert-field' ).plain() );
+  107  				} );
+  108  			}
+  ...
+  186  				var ok = this.getApiValue() !== undefined || suppressErrors;
+  187  				this.setIcon( ok ? null : 'alert' );
+  188: 				this.setIconTitle( ok ? '' : mw.message( 'apisandbox-alert-field' ).plain() );
+  189  				return $.Deferred().resolve( ok ).promise();
+  190  			}
+  ...
+  234  
+  235  				this.setIcon( ok ? null : 'alert' );
+  236: 				this.setIconTitle( ok ? '' : mw.message( 'apisandbox-alert-field' ).plain() );
+  237  				return $.Deferred().resolve( ok ).promise();
+  238  			},
+  ...
+  292  				var ok = this.getValue() !== null || suppressErrors;
+  293  				this.setIcon( ok ? null : 'alert' );
+  294: 				this.setIconTitle( ok ? '' : mw.message( 'apisandbox-alert-field' ).plain() );
+  295  				return $.Deferred().resolve( ok ).promise();
+  296  			}
+  ...
+  469  					} );
+  470  					widget.setIcon = widget.input.setIcon.bind( widget.input );
+  471: 					widget.setIconTitle = widget.input.setIconTitle.bind( widget.input );
+  472  					widget.getValidity = widget.input.getValidity.bind( widget.input );
+  473  					widget.paramInfo = pi;
+  ...
+ 1364  		this.outlineItem.setLabel( this.displayText );
+ 1365  		this.outlineItem.setIcon( this.apiIsValid || suppressErrors ? null : 'alert' );
+ 1366: 		this.outlineItem.setIconTitle(
+ 1367  			this.apiIsValid || suppressErrors ? '' : mw.message( 'apisandbox-alert-page' ).plain()
+ 1368  		);
+ ....
+ 2009  				if ( that.getOutlineItem() ) {
+ 2010  					that.getOutlineItem().setIcon( that.apiIsValid || suppressErrors ? null : 'alert' );
+ 2011: 					that.getOutlineItem().setIconTitle(
+ 2012  						that.apiIsValid || suppressErrors ? '' : mw.message( 'apisandbox-alert-page' ).plain()
+ 2013  					);
+
+extensions/CollaborationKit/modules/ext.CollaborationKit.list.ui.js:
+  289  					framed: false,
+  290  					icon: 'trash',
+  291: 					iconTitle: mw.msg( 'collaborationkit-list-delete' )
+  292  				} );
+  293  
+  ...
+  298  						framed: false,
+  299  						icon: 'move',
+  300: 						iconTitle: mw.msg( 'collaborationkit-list-move' )
+  301  					} );
+  302  				}
+
+extensions/ContentTranslation/modules/ui/widgets/mw.cx.ui.TitleOptionWidget.js:
+   53  			languageIcon = new OO.ui.IconWidget( {
+   54  				icon: 'language',
+   55: 				iconTitle: mw.msg( 'cx-page-number-of-languages' )
+   56  			} );
+   57  			languageLabel = new OO.ui.LabelWidget( {
+
+extensions/Kartographer/modules/dialog/dialog.js:
+   64  						label: mw.msg( 'kartographer-sidebar-togglebutton' ),
+   65  						icon: 'newWindow',
+   66: 						iconTitle: mw.msg( 'kartographer-sidebar-togglebutton' )
+   67  					} );
+   68  					dialog.mapDetailsButton.connect( dialog, { change: 'toggleSideBar' } );
+
+extensions/Kartographer/modules/wikivoyage/wikivoyage.js:
+   80  				icon = new OO.ui.IconWidget( {
+   81  					icon: 'linkExternal',
+   82: 					iconTitle: mw.msg( 'kartographer-wv-warning-external-source-message' ),
+   83  					classes: [ 'leaflet-control-layers-oo-ui-icon' ]
+   84  				} );
+
+extensions/LanguageTool/modules/ext.LanguageToolDialog.js:
+   71  	this.sendButton = new OO.ui.ButtonWidget( {
+   72  		icon: 'check',
+   73: 		iconTitle: 'LanguageTool'
+   74  	} );
+   75  	this.previousButton = new OO.ui.ButtonWidget( {
+   76  		icon: 'previous',
+   77: 		iconTitle: ve.msg( 'visualeditor-find-and-replace-previous-button' ) + ' ' +
+   78  			ve.ui.triggerRegistry.getMessages( 'findPrevious' ).join( ', ' )
+   79  	} );
+   80  	this.nextButton = new OO.ui.ButtonWidget( {
+   81  		icon: 'next',
+   82: 		iconTitle: ve.msg( 'visualeditor-find-and-replace-next-button' ) + ' ' +
+   83  			ve.ui.triggerRegistry.getMessages( 'findNext' ).join( ', ' )
+   84  	} );
+
+extensions/PerformanceInspector/modules/collectors/ext.PerformanceInspector.modulescss.js:
+  167  						label: mw.msg( 'performanceinspector-modules-css-show-details' ),
+  168  						icon: 'info',
+  169: 						iconTitle: mw.msg( 'performanceinspector-modules-css-show-details' )
+  170  					} );
+  171  				button.on( 'click', function () {
+
+extensions/VisualEditor/modules/ve-mw/ui/pages/ve.ui.MWParameterPage.js:
+   62  		this.statusIndicator
+   63  			.setIndicator( 'required' )
+   64: 			.setIndicatorTitle(
+   65  				ve.msg( 'visualeditor-dialog-transclusion-required-parameter' )
+   66  			);
+   ..
+   75  		this.statusIndicator
+   76  			.setIndicator( 'alert' )
+   77: 			.setIndicatorTitle(
+   78  				ve.msg( 'visualeditor-dialog-transclusion-deprecated-parameter' )
+   79  			);
+   ..
+  378  			this.outlineItem
+  379  				.setIndicator( 'required' )
+  380: 				.setIndicatorTitle(
+  381  					ve.msg( 'visualeditor-dialog-transclusion-required-parameter' )
+  382  				);
+  ...
+  385  			this.outlineItem
+  386  				.setIndicator( 'alert' )
+  387: 				.setIndicatorTitle(
+  388  					ve.msg( 'visualeditor-dialog-transclusion-deprecated-parameter' )
+  389  				);
+
+extensions/WikibaseQualityConstraints/modules/gadget.js:
+  212  	 * @param {jQuery} $container The container to which the button is appended.
+  213  	 * @param {string} icon Identifier for an icon as provided by OOUI.
+  214: 	 * @param {string} iconTitleMessageKey The message key of the title attribute of the icon.
+  215  	 * @param {string} [flags] Optional custom flags the {@link OO.ui.PopupButtonWidget} can understand.
+  216  	 */
+  217: 	SELF.prototype._buildPopup = function ( $content, $container, icon, iconTitleMessageKey, flags /* = '' */ ) {
+  218  		var widget = new OO.ui.PopupButtonWidget( {
+  219  			icon: icon,
+  220: 			iconTitle: mw.message( iconTitleMessageKey ).text(),
+  221  			flags: flags || '',
+  222  			framed: false,
+
+extensions/WikidataPageBanner/includes/WikidataPageBanner.functions.php:
+   50  				$iconName = Sanitizer::escapeClass( $iconname );
+   51  				$iconUrl = Title::newFromText( $value );
+   52: 				$iconTitleText = $iconName;
+   53  				$finalIcon = [ 'url' => '#' ];
+   54  				// reference article for icons provided and is valid, then add its link
+   ..
+   56  					$finalIcon['url'] = $iconUrl->getLocalURL();
+   57  					// set icon title to title of referring article
+   58: 					$iconTitleText = $iconUrl->getText();
+   59  				}
+   60  				$finalIcon['icon'] = $iconName;
+   61: 				$finalIcon['title'] = $iconTitleText;
+   62  				$iconsToAdd[] = $finalIcon;
+   63  			}
+```",1545174186,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-tjkkepz2glxx6dypkoab,task_subcomment,NA
+Rename a lot of getters for consistency,"[x] OO.ui.BookletLayout.prototype.getPageName ➞ OO.ui.BookletLayout.prototype.get**Current**PageName https://gerrit.wikimedia.org/r/#/c/177799/
+
+[x] OO.ui.BookletLayout.prototype.getClosestPage ➞ OO.ui.BookletLayout.prototype.**find**ClosestPage
+** [x] Deprecate https://gerrit.wikimedia.org/r/#/c/375935/
+** [x] Fix https://gerrit.wikimedia.org/r/#/c/375937/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/375936/
+
+[x] OO.ui.SelectWidget.prototype.getTargetItem ➞ OO.ui.SelectWidget.prototype.**find**TargetItem https://gerrit.wikimedia.org/r/#/c/375938/
+
+[x] OO.ui.SelectWidget.prototype.getFirstSelectableItem ➞ OO.ui.SelectWidget.prototype.**find**FirstSelectableItem
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/376171/
+** [x] Fix
+*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/#/c/376172/
+*** [x] VE ➞ https://gerrit.wikimedia.org/r/#/c/376177/
+*** [x] VE extension ➞ https://gerrit.wikimedia.org/r/#/c/376175/
+*** [x] MediaWiki core ➞ https://gerrit.wikimedia.org/r/#/c/376176/
+*** [x] TemplateData extension ➞ https://gerrit.wikimedia.org/r/#/c/376174/
+** [x] Break ➞ https://gerrit.wikimedia.org/r/#/c/376173/
+
+[x] OO.ui.SelectWidget.prototype.getHighlightedItem ➞ OO.ui.SelectWidget.prototype.**find**HighlightedItem
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/376501
+** [x] Fix ➞ https://gerrit.wikimedia.org/r/376502
+** [x] Break ➞ https://gerrit.wikimedia.org/r/376503
+
+[x] OO.ui.SelectWidget.prototype.getRelativeSelectableItem ➞ OO.ui.SelectWidget.prototype.**find**RelativeSelectableItem
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/376183
+** [x] Fix
+*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/376184
+*** [x] Mediawiki core: RCFilter ➞ https://gerrit.wikimedia.org/r/376186
+** [x] Break ➞ https://gerrit.wikimedia.org/r/376185
+
+[x] OO.ui.ToolGroup.prototype.getTargetTool ➞ OO.ui.ToolGroup.prototype.**find**TargetTool https://gerrit.wikimedia.org/r/#/c/375940/
+
+[x] OO.ui.GroupElement.prototype.getItemFromData ➞ OO.ui.GroupElement.prototype.**find**ItemFromData
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398004/
+** [x] Fix 
+*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/#/c/398209/
+*** [x] ContentTranslation ➞ https://gerrit.wikimedia.org/r/#/c/398217/
+*** [x] AdvancedSearch ➞ https://gerrit.wikimedia.org/r/#/c/398223/
+*** [x] Echo ➞ https://gerrit.wikimedia.org/r/#/c/398224/
+*** [x] Flow ➞ https://gerrit.wikimedia.org/r/#/c/400466/
+*** [x] CentralNotice ➞ https://gerrit.wikimedia.org/r/#/c/400467/
+*** [x] TemplateData ➞ https://gerrit.wikimedia.org/r/#/c/400468/
+*** [x] VisualEditor ➞ https://gerrit.wikimedia.org/r/#/c/400470
+*** [x] VisualEditor-MediaWiki ➞ https://gerrit.wikimedia.org/r/#/c/400469/
+*** [x] MediaWiki ➞ https://gerrit.wikimedia.org/r/#/c/398221/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415227/
+
+[x] OO.ui.GroupElement.prototype.getItemsFromData ➞ OO.ui.GroupElement.prototype.**find**ItemsFromData
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398004/
+** [x] Fix
+*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/#/c/398209/
+*** [x] ContentTranslation ➞ https://gerrit.wikimedia.org/r/#/c/398217/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415227/
+
+[x] OO.ui.SelectWidget.prototype.getSelectedItem ➞ OO.ui.SelectWidget.prototype.**find**SelectedItem
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398005/
+** [x] Fix
+*** [x] OOUI: https://gerrit.wikimedia.org/r/#/c/403934/
+*** [x] {T184037}
+*** [x] {T184041} 
+*** [x] {T184040}
+*** [x] {T184039}
+*** [x] Kartographer: https://gerrit.wikimedia.org/r/#/c/404669/
+*** [x] CentralNotice: https://gerrit.wikimedia.org/r/#/c/414935/
+*** [x] CollaborationKit: https://gerrit.wikimedia.org/r/#/c/414936/
+*** [x] Math: https://gerrit.wikimedia.org/r/#/c/404671/
+*** [x] ContentTranslation: https://gerrit.wikimedia.org/r/414937
+*** [x] UploadWizard: https://gerrit.wikimedia.org/r/414942
+*** [x] ProofreadPage: https://gerrit.wikimedia.org/r/#/c/404673/
+*** [x] MultimediaViewer: https://gerrit.wikimedia.org/r/#/c/414943/
+*** [x] VE: https://gerrit.wikimedia.org/r/#/c/404667/
+*** [x] VE-MW: https://gerrit.wikimedia.org/r/#/c/404666/
+*** [x] Mediawiki core: https://gerrit.wikimedia.org/r/414944
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415229/
+
+[x] OO.ui.MultiselectWidget.prototype.getSelectedItems ➞ OO.ui.MultiselectWidget.prototype.**find**SelectedItems
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398006/
+** [x] Fix
+*** [x] Mediawiki core: https://gerrit.wikimedia.org/r/#/c/415224/
+*** [x] UploadWizard: https://gerrit.wikimedia.org/r/#/c/415225/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415231/
+
+[x] OO.ui.MultiselectWidget.prototype.getSelectedItemsData ➞ OO.ui.MultiselectWidget.prototype.**find**SelectedItemsData
+** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398006/
+** [x] Fix
+*** [x] UploadWizard: https://gerrit.wikimedia.org/r/#/c/415226/
+** [x] Break https://gerrit.wikimedia.org/r/#/c/415231/
+",1417634878,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_description,resolved
+Rename a lot of getters for consistency,Excellent work!,1525726664,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415227 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] GroupElement: Remove getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/415227]]",1525726268,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415231 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] MultiSelectWidget: Remove getSelectedItems and getSelectedItemsData
+
+[[https://gerrit.wikimedia.org/r/415231]]",1525726232,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415229 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/415229]]",1525726231,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415226 **merged** by jenkins-bot:
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItemsData instead of getSelectedItemsData
+
+[[https://gerrit.wikimedia.org/r/415226]]",1519928715,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415224 **merged** by jenkins-bot:
+[mediawiki/core@master] Use findSelectedItems instead of getSelectedItems
+
+[[https://gerrit.wikimedia.org/r/415224]]",1519862527,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415225 **merged** by jenkins-bot:
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItems instead of getSelectedItems
+
+[[https://gerrit.wikimedia.org/r/415225]]",1519861874,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415231 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] MultiSelectWidget: Remove getSelectedItems and getSelectedItemsData
+
+[[https://gerrit.wikimedia.org/r/415231]]",1519799131,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415229 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/415229]]",1519798953,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415227 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] GroupElement: Remove getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/415227]]",1519798385,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415226 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItemsData instead of getSelectedItemsData
+
+[[https://gerrit.wikimedia.org/r/415226]]",1519797741,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415225 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItems instead of getSelectedItems
+
+[[https://gerrit.wikimedia.org/r/415225]]",1519797536,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 415224 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] Use findSelectedItems instead of getSelectedItems
+
+[[https://gerrit.wikimedia.org/r/415224]]",1519797222,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414935 **merged** by jenkins-bot:
+[mediawiki/extensions/CentralNotice@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414935]]",1519758949,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414944 **merged** by jenkins-bot:
+[mediawiki/core@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414944]]",1519758271,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414936 **merged** by jenkins-bot:
+[mediawiki/extensions/CollaborationKit@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414936]]",1519757512,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414937 **merged** by jenkins-bot:
+[mediawiki/extensions/ContentTranslation@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414937]]",1519757067,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414942 **merged** by jenkins-bot:
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414942]]",1519752092,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414943 **merged** by jenkins-bot:
+[mediawiki/extensions/MultimediaViewer@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414943]]",1519748620,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414944 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414944]]",1519711589,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414943 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/MultimediaViewer@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414943]]",1519711087,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414942 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/UploadWizard@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414942]]",1519710546,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414937 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/ContentTranslation@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414937]]",1519709947,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414936 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/CollaborationKit@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414936]]",1519709660,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 414935 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/CentralNotice@master] Use findSelectedItem instead of getSelectedItem
+
+[[https://gerrit.wikimedia.org/r/414935]]",1519709383,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400467 **merged** by jenkins-bot:
+[mediawiki/extensions/CentralNotice@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400467]]
+",1517262540,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 404513 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (d5428e9b3)
+
+[[https://gerrit.wikimedia.org/r/404513]]
+",1516210175,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 404513 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (d5428e9b3)
+
+[[https://gerrit.wikimedia.org/r/404513]]
+",1516127047,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398224 **merged** by jenkins-bot:
+[mediawiki/extensions/Echo@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398224]]
+",1515634648,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398221 **merged** by jenkins-bot:
+[mediawiki/core@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/398221]]
+",1515616772,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398223 **merged** by jenkins-bot:
+[mediawiki/extensions/AdvancedSearch@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398223]]
+",1515616625,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398217 **merged** by jenkins-bot:
+[mediawiki/extensions/ContentTranslation@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398217]]
+",1515616624,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400469 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400469]]
+",1515614073,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400468 **merged** by jenkins-bot:
+[mediawiki/extensions/TemplateData@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400468]]
+",1515613877,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400466 **merged** by jenkins-bot:
+[mediawiki/extensions/Flow@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400466]]
+",1515613876,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400470 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400470]]
+",1515613572,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398006 **merged** by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] MultiSelectWidget: Rename getters
+
+[[https://gerrit.wikimedia.org/r/398006]]
+",1515014388,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398005 **merged** by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getSelectedItem to findSelectedItem
+
+[[https://gerrit.wikimedia.org/r/398005]]
+",1515014345,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400470 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[VisualEditor/VisualEditor@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400470]]
+",1514442501,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400469 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/VisualEditor@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400469]]
+",1514442228,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400468 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/TemplateData@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400468]]
+",1514441803,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400467 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/CentralNotice@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400467]]
+",1514441613,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 400466 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/Flow@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/400466]]
+",1514441206,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398209 **merged** by jenkins-bot:
+[oojs/ui@master] Use findItem(s)FromData instead of getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398209]]
+",1513362323,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398004 **merged** by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] GroupElement: Rename getItem(s)FromData to findItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398004]]
+",1513361286,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398224 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/Echo@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398224]]
+",1513238791,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398223 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/AdvancedSearch@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398223]]
+",1513238413,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398221 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] Use findItemFromData instead getItemFromData
+
+[[https://gerrit.wikimedia.org/r/398221]]
+",1513237626,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398217 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/ContentTranslation@master] Use findItem(s)FromData instead getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398217]]
+",1513236102,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398209 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Use findItem(s)FromData instead of getItem(s)FromData
+
+[[https://gerrit.wikimedia.org/r/398209]]
+",1513230421,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398006 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] MultiSelectWidget: Rename getters
+
+[[https://gerrit.wikimedia.org/r/398006]]
+",1513149733,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398005 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getSelectedItem to findSelectedItem
+
+[[https://gerrit.wikimedia.org/r/398005]]
+",1513149172,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 398004 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] GroupElement: Rename getItemFromData to findItemFromData
+
+[[https://gerrit.wikimedia.org/r/398004]]
+",1513148429,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"> OO.ui.SelectWidget.prototype.getSelectedItem ➞ OO.ui.SelectWidget.prototype.findSelectedItem
+
+We should also change this for `MultiSelectWidget` (not just `SelectWidget`) and thus `getSelectedItemsData`.",1513147727,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,">>! In T76630#3833381, @Volker_E wrote:
+> @Prtksxna Yes, please. Also `getSelectedItemsData` ➞ `findSelectedItemsData`.
+
+Yes, thanks, just writing a comment about that.",1513147592,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,">>! In T76630#3833381, @Volker_E wrote:
+> @Prtksxna Yes, please. Also `getSelectedItemsData` ➞ `findSelectedItemsData`.
+
+Yes, that one is already filed in the description.",1513147493,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"@Prtksxna Yes, please. Also `getSelectedItemsData` ➞ `findSelectedItemsData`.",1513147439,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"> OO.ui.GroupElement.prototype.getItemFromData ➞ OO.ui.GroupElement.prototype.findItemFromData
+
+Just confirming, we should also change the plural, OO.ui.GroupElement.prototype.getItem**s**FromData ➞ OO.ui.GroupElement.prototype**.find**Item**s**FromData",1513147274,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"@Prtksxna Would you please care about the two last open items here, as well? Want to get this in for v0.25.0.",1513122808,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376173 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376173]]
+",1513122104,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376185 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376185]]
+",1513113113,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375936 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] Remove BookletLayout#getClosestPage
+
+[[https://gerrit.wikimedia.org/r/375936]]
+",1513112666,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376503 **merged** by jenkins-bot:
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376503]]
+",1513112664,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376186 merged by jenkins-bot:
+[mediawiki/core@master] RCFilters: Use findRelativeSelectableItem instead of getRelativeSelectableitem
+
+[[https://gerrit.wikimedia.org/r/376186]]
+",1506018081,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376176 merged by jenkins-bot:
+[mediawiki/core@master] apisandbox.js: Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376176]]
+",1506017666,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376174 merged by jenkins-bot:
+[mediawiki/extensions/TemplateData@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376174]]
+",1506017591,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376175 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376175]]
+",1506017590,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376177 merged by jenkins-bot:
+[VisualEditor/VisualEditor@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376177]]
+",1506017237,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376184 merged by jenkins-bot:
+[oojs/ui@master] Use findRelativeSelectableItem instead of getRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376184]]
+",1505852457,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376183 merged by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getRelativeSelectableItem to findRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376183]]
+",1505852456,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376172 merged by Prtksxna:
+[oojs/ui@master] Use findFirstSelectableItem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376172]]
+",1505391686,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376502 merged by jenkins-bot:
+[oojs/ui@master] Use findHighlightedItem instead of getHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376502]]
+",1504798452,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376501 merged by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getHighlightedItem to findHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376501]]
+",1504798356,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376171 merged by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getFirstSelectableItem to findFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376171]]
+",1504798320,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376503 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376503]]
+",1504785155,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376502 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Use findHighlightedItem instead of getHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376502]]
+",1504785154,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376501 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getHighlightedItem to findHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376501]]
+",1504785153,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376182 abandoned by Prtksxna:
+[BREAKING CHANGE] SelectWidget: Rename getHighlightedItem to findHighlightedItem
+
+Reason:
+> As these are public methods, we should deprecate them even if they're unused in git. They might be used on wiki, or by third parties.
+
+Yeah makes sense. Abandoning this because its easier for me :/
+
+[[https://gerrit.wikimedia.org/r/376182]]",1504784613,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376186 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] RCFilters: Use findRelativeSelectableItem instead of getRelativeSelectableitem
+
+[[https://gerrit.wikimedia.org/r/376186]]
+",1504683857,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376185 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376185]]
+",1504683834,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376184 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Use findRelativeSelectableItem instead of getRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376184]]
+",1504683833,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376183 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getRelativeSelectableItem to findRelativeSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376183]]
+",1504683832,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"> OO.ui.SelectWidget.prototype.getHighlightedItem ➞ OO.ui.SelectWidget.prototype.**find**HighlightedItem
+
+There is a `getHighlightedItem` being used in #mediawiki-recent-changes but it isn't related to this change and doesn't use `OO.ui.SelectWidget`. Could someone please confirm my observation?",1504682251,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"> OO.ui.SelectWidget.prototype.getHighlightedItem ➞ OO.ui.SelectWidget.prototype.**find**HighlightedItem
+
+There is a `getHighlightedItem` being used in #mediawiki-recent-changes but it isn't related to this change and doesn't use `OO.ui.SelectWidget`.",1504682001,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376182 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] SelectWidget: Rename getHighlightedItem to findHighlightedItem
+
+[[https://gerrit.wikimedia.org/r/376182]]
+",1504681933,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376177 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[VisualEditor/VisualEditor@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376177]]
+",1504676888,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376176 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/core@master] apisandbox.js: Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376176]]
+",1504676878,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376175 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/VisualEditor@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376175]]
+",1504676871,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376174 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/TemplateData@master] Use findFirstSelectableitem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376174]]
+",1504676868,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376173 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] SelectWidget: Remove getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376173]]
+",1504676858,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376172 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Use findFirstSelectableItem instead of getFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376172]]
+",1504676857,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 376171 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] SelectWidget: Rename getFirstSelectableItem to findFirstSelectableItem
+
+[[https://gerrit.wikimedia.org/r/376171]]
+",1504676856,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375937 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWTemplateDialog: BookletLayout: Use findClosestPage instead of getClosestPage
+
+[[https://gerrit.wikimedia.org/r/375937]]
+",1504658314,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375935 merged by jenkins-bot:
+[oojs/ui@master] [DEPRECATING CHANGE] BookletLayout: Rename getClosestPage to findClosestPage
+
+[[https://gerrit.wikimedia.org/r/375935]]
+",1504633553,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375938 merged by jenkins-bot:
+[oojs/ui@master] SelectFileWidget: Rename getTargetItem to findTargetItem
+
+[[https://gerrit.wikimedia.org/r/375938]]
+",1504627531,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375940 merged by jenkins-bot:
+[oojs/ui@master] Toolgroup: Rename getTargetTool to findTargetTool
+
+[[https://gerrit.wikimedia.org/r/375940]]
+",1504627530,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375940 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] Toolgroup: Rename getTargetTool to findTargetTool
+
+[[https://gerrit.wikimedia.org/r/375940]]
+",1504579758,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375938 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] SelectFileWidget: Rename getTargetItem to findTargetItem
+
+[[https://gerrit.wikimedia.org/r/375938]]
+",1504579127,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375937 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[mediawiki/extensions/VisualEditor@master] MWTemplateDialog: BookletLayout: Use findClosestPage instead of getClosestPage
+
+[[https://gerrit.wikimedia.org/r/375937]]
+",1504577626,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375936 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [BREAKING CHANGE] Remove BookletLayout#getClosestPage
+
+[[https://gerrit.wikimedia.org/r/375936]]
+",1504577519,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 375935 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
+[oojs/ui@master] [DEPRECATING CHANGE] BookletLayout: Rename getClosestPage to findClosestPage
+
+[[https://gerrit.wikimedia.org/r/375935]]
+",1504577518,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,I don't see anything stalled here.,1479485224,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"I don't really see the value in changing this, sorry. (But won't oppose if someone does it, I guess.)",1424183629,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,Ping. What's happening with this?,1424129889,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"The idea was simply that there were three classes of getters.
+
+1. Get a single thing that is always there - like input.getValue()
+2. Get a single thing that may or may not be there - like booklet.getOutline()
+3. Get one of the 0+ items inside something - like select.getItemFromData()
+
+I was feeling like there were too many cases where class 2 and 3 getters were being chained, which causes problems since they may or may return null. Since the method names don't hint at whether they are safe to chain - and in the case of class 1 they are perfectly safe to chain, code that is dangerous is very easy to mistake for code that is safe.
+
+I don't have a solution for class 2 yet. I'm very interested in ideas.
+
+The solution I came up with for class 3 is to use find instead of get. I think this hints at the method being unsafe to chain, makes the code clearer that you are asking for one of 0+ items, and is a very simple change in the code.",1418162918,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 177799 merged by jenkins-bot:
+[BREAKING CHANGE] Rename BookletLayout#getPageName → #getCurrentPageName
+
+[[https://gerrit.wikimedia.org/r/177799]]",1417825555,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,But why?! :),1417825403,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,Consistency with what Trevor wants OOUI to look like. :-),1417805658,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Hm.. consistency with what? At first glance I'd guess that a ""get"" method returns a reference or value that is computed or gathered on-demand. It typically takes either no argument or a unique identifier for a single item. A ""find"" method on the other hand seems different, maybe something that might takes a search query and return varying results (0 or more). ack-grep found 0 matches for `prototype.find` in oojs/ui, and 2 matches in lib/ve/*.",1417791056,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"The BookletLayout#getPageName → #getCurrentPageName one was an obvious improvement and is entirely painless, but I would like to hear the rationale for get→find replacements before I spend tons of time replacing tons of usages across the repos.",1417790475,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+Rename a lot of getters for consistency,"Change 177799 had a related patch set uploaded (by Bartosz Dziewoński):
+[BREAKING CHANGE] Rename BookletLayout#getPageName → #getCurrentPageName
+
+[[https://gerrit.wikimedia.org/r/177799]]
+
+#patch-for-review",1417790387,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3o2r6t4wgzcrj2zuvlkx,task_subcomment,NA
+K3. Run Flow tests with Parsoid on Jenkins,"@EBernhardson said that they are currently run with wikitext (without Parsoid).  It would be good to run them with Parsoid (since that's our main backend) in addition to or instead of wikitext.
+
+--------------------------
+**Trello card**: [[ https://trello.com/c/YpgazY2B/701-k3-run-flow-unit-tests-with-parsoid-3 | YpgazY2B ]]",1417606214,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-rtdocuudreaisizzfzfc,task_description,open
+K3. Run Flow tests with Parsoid on Jenkins,"I think @Ebernhardson changed most/all of these to use a fixture (mock output for given input) if Parsoid is not available.  We'd still like the real thing, but that should help.",1424461437,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-rtdocuudreaisizzfzfc,task_subcomment,NA
+K3. Run Flow tests with Parsoid on Jenkins,"@hashar: How far of do you think those proposed ideas are?
+Would it make sense to contact an existing Parsoid, until we can properly clone & run it in isolation?
+We're not in a huge rush, but it would be nice to have our tests run with Parsoid.
+
+
+Possible implementation suggestion, copied from [Trello](https://trello.com/c/YpgazY2B/701-k3-run-flow-unit-tests-with-parsoid-3):
+
+http://www.mediawiki.org/wiki/Parsoid/API says ""A production version of Parsoid on the Wikimedia cluster can be accessed at http://parsoid-lb.eqiad.wikimedia.org/"", so I guess that one would be good to use.
+
+I'm no Jenkins expert, but I think we should add a build step ""Execute shell"" with the following command on https://integration.wikimedia.org/ci/view/Extensions/job/mwext-Flow-testextension/configure - this would override the default Parsoid settings:
+
+```
+# Load context (namely: MW_INSTALL_PATH)
+. ""/srv/deployment/integration/slave-scripts/bin/mw-set-env.sh""
+
+# Configure Parsoid
+echo -e \
+ ""<?php\n\$wgFlowParsoidURL = 'http://parsoid-lb.eqiad.wikimedia.org/';\n""\
+ ""\$wgFlowParsoidPrefix = 'enwiki';\n""\
+ ""\$wgFlowParsoidTimeout = 100;\n"" >> ""$MW_INSTALL_PATH/LocalSettings.php""
+```",1421168395,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-rtdocuudreaisizzfzfc,task_subcomment,NA
+K3. Run Flow tests with Parsoid on Jenkins,"So i know that doing this ""correct"" is of big benefit, but could we have most of the benefits now just by setting Flow config to point to already existing parsoid in labs? Without having to install or boot a parsoid instance the changes required become trivial, as long as the jenkins runners have network access to the labs machines.",1417818190,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-rtdocuudreaisizzfzfc,task_subcomment,NA
+K3. Run Flow tests with Parsoid on Jenkins,"Copying @hashar's comment on Trello:
+
+Sorry for the rather long delay. To run tests with Parsoid as a backend, we would need a job that:
+
+  - spawn a Parsoid daemon like we do for some Parsoid integration tests
+  - setup MediaWiki behind a web server which we do for qunit tests
+
+The mwext-Flow-testextension job execute the PHPUnit test suite which combines unit tests for the Flow function as well as integration tests against mediawiki/core.
+
+It is totally doable to spawn a Parsoid daemon and run whatever tests you want. That being said, I would prefer to avoid rushing a solution that would match just the Flow extension in favor of a system that would work for other use cases (such as VisualEditor).
+
+During the summer, I worked on a set of utilities that would let us clone core + vendor + extensions and run them all together with the appropriate patches/branches checked out. That will yield a state of code to be tested and is subject of an RFC: https://www.mediawiki.org/wiki/RFC/Extensions_continuous_integration
+
+Once we have that stack of code available, everything is loaded via include() and we will run: the PHPUnit test suite the qunit page
+
+That will supersede all the testextension and extension-qunit jobs in favor of a two jobs that are used by all repositories.
+
+We can come up with a third job that would have a bit more backend configured such as ElasticSearch or Parsoid. But that will take a bit more time since I want the other two jobs to be setup first.
+
+As I understand, running Flow tests with Parsoid is more of a nice to have feature than a breaker and I guess it can wait a bit. In short: yes, but a bit later and on a wider scale :-)
+
+I am subscribed to this Trello card so we can keep the discussion here 8-)",1417633169,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-rtdocuudreaisizzfzfc,task_subcomment,NA
+Explore performance gains from progressive (JIT?) de-alienation of content types in VisualEditor,"See {T54365} for the same idea, but for content blocks.",1417567272,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yja5lvncvpyih4flmthe,task_description,open
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Somehow(?) load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document.
+
+Will probably need {T49344} for the document splitting.
+",1417566671,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_description,resolved
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","I think the testing of this re-factor is pretty much done. I'm going to go ahead and mark it as verified. If we find more bugs as part of more integration testing, we will create new bugs. At least this one won't have to sit around under QA column. ",1551990955,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Currently this  is disabled behind a feature flag, so QA should just check that editing/section editing is unaffected by the code refactor. We will do a separate QA for the feature itself when we get around to enabling it by default.",1550691051,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 440809 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Support only surfacing part of the document
+
+[[https://gerrit.wikimedia.org/r/440809]]",1550689592,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 489319 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (c4d559b29)
+
+[[https://gerrit.wikimedia.org/r/489319]]",1549761425,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 489319 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (b629aa8b1)
+
+[[https://gerrit.wikimedia.org/r/489319]]",1549660398,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 433753 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Support only surfacing part of the document
+
+[[https://gerrit.wikimedia.org/r/433753]]",1549655229,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 440809 had a related patch set uploaded (by Divec; owner: Divec):
+[mediawiki/extensions/VisualEditor@master] WIP Support only surfacing part of the document
+
+[[https://gerrit.wikimedia.org/r/440809]]",1529298219,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","As well as the approach in https://gerrit.wikimedia.org/r/433753 , we should also consider the following alternative:
+- A class provides the LinearData interface on a live slice of the linear data (performing offset translation and bounds checking)
+- ve.dm.Document builds on top of that class
+That approach would more robustly prevent access outside the slice. But one drawback would be apparent dangling references in the slice.",1526802428,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","Change 433753 had a related patch set uploaded (by Divec; owner: Divec):
+[VisualEditor/VisualEditor@master] WIP POC: Support only surfacing part of the document
+
+[[https://gerrit.wikimedia.org/r/433753]]",1526802127,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","We already support fetching specific HTML sections by ID in the REST API (see https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_html_title), but until consistent <section> wrapping with a sensible granularity & perhaps a predictable section ID for the lead section are implemented in Parsoid (T114072), this is not as useful in practice as it could be.
+
+Behind the scenes, the section-by-id retrieval is currently based on byte offset mappings provided by Parsoid and stored in Cassandra. Given the performance we see in [web-html-stream](https://github.com/wikimedia/web-html-stream) (the library @cscott mentioned), we could however get rid of the explicit section offsets stored in cassandra, and do the matching / extraction dynamically instead.
+
+Apart from the server side section retrieval API, clients will need to discover the page outline & section ids. The reading team has already been doing some section loading in apps & mobile web. This is not yet fully general, but is moving in that direction. Metadata about sections is exposed in [the page summary end point](https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_summary_title). Another source of metadata is the [lead section end point](https://en.wikipedia.org/api/rest_v1/#!/Mobile/get_page_mobile_sections_lead_title_revision) used by apps, which additionally includes the lead section content itself. Eventually, I hope that we will have standard <section>s in Parsoid output, and can refer to those in these summary end points for easy section retrieval.",1504895813,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+"Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document","We've had a somewhat-related discussion in Parsoid-land about being able to fetch only subsets of the DOM tree from restbase.  The idea there was that restbase would do the actual subtree extraction from the full document, using the fancy fast regexp-based stuff that @gwicke wrote.  But you'd also want to extract and fetch data-mw and data-parsoid for the same subtree.  We've talked about tree-structuring the data-mw and data-parsoid JSON blobs to make that possible (using a variant of @gwicke's HTML regexp technique), but I'm not sure we've actually implemented that yet.",1504891814,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-5dur2e4zsk6uu6tgyilj,task_subcomment,NA
+VisualEditor image resize icon must be flipped and moved to the opposite edge for RTL wikis,"The VisualEditor image resize icon must appear on the inner side of the page (inner in relation to the page). For RTL now it appears on the outer edge, which makes it not really usable. The direction of the arrow heads must be flipped, too.",1417526272,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-np6rbo55hknbpzfqqpzh,task_description,open
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","This is valid HTML:
+```
+<blockquote>
+<p>
+Foo
+</p>
+<p>
+Bar
+</p>
+</blockquote>
+```
+But when such structure is edited in VE, the inner paragraphs get alienated.
+//*sighs*//
+
+>>! In T154231, @dchan wrote:
+> At present, BlockquoteNode behaves like a ContentBranchNode ; it should not.
+> 
+> Right now, ve.ce.BlockquoteNode extends ve.ce.ContentBranchNode, but ve.dm.BlockquoteNode extends ve.dm.BranchNode . I would say BranchNode is the correct parent, because HTML blockquote elements can contain flow content such as paragraph elements (see https://html.spec.whatwg.org/multipage/semantics.html#the-blockquote-element ).
+> 
+> If however there's some special weird reason to treat BlockquoteNode as a ContentBranchNode, then I'll implement that instead and document the special weird reason.
+
+>>! In T154231#2913587, @Jdforrester-WMF wrote:
+> ISTR there is — or at least, was — a solid reason for doing this. But I don't recall at all what it was.
+
+>>! In T154231#4000786, @matmarex wrote:
+> It seems the reason was that we treat it as a top-level block element, like paragraphs or heading.
+> 
+>>>! @Esanders in https://gerrit.wikimedia.org/r/#/c/329448/
+>> This is probably correct but it means we have to come up with a new tool for inserting block quote, as it is currently treated as a CBN conversion in the format dropdown. I think we did it that way because most blockquotes are only one paragraph.
+>> 
+>> Alternatively, we could go the other way and make it fully ContentBranchNode, at least for the time being.
+> 
+> It was actually changed to be fully ContentBranchNode in 94dbb244dd.
+
+",1417481643,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_description,resolved
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","There is formal QA approval on T209162… I think we can skip the rest, things seem to work fine.",1559171278,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","QA note: please also check the parent tasks, I think they should all be resolved by the fixes here:
+
+* {T120827}
+* {T54398}
+* {T86794}
+* {T209162}",1556049031,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",">>! In T76426#5086359, @matmarex wrote:
+> The patches now only resolve the technical issue of multi-paragraph blockquotes not being editable. I'll file a separate task to consider the toolbar changes later.
+
+I filed: {T221692}",1556048047,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475962 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (7cd15cfe9)
+
+[[https://gerrit.wikimedia.org/r/475962]]",1556033496,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475961 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Make blockquote a non-content branch node
+
+[[https://gerrit.wikimedia.org/r/475961]]",1555695456,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",The patches now only resolve the technical issue of multi-paragraph blockquotes not being editable. I'll file a separate task to consider the toolbar changes later.,1554405157,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475962 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] [PULLTHROUGH] Update stuff for making blockquote a non-content branch node
+
+[[https://gerrit.wikimedia.org/r/475962]]",1554404541,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475961 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[VisualEditor/VisualEditor@master] Make blockquote a non-content branch node, update tools and stuff accordingly
+
+[[https://gerrit.wikimedia.org/r/475961]]",1554404537,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",moving this to Blocked/Waiting because I suspect that the work in https://phabricator.wikimedia.org/T211255 will impact the decisions on this.,1553002269,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",Process question - is this something that we should focus on in conjunction with T211255?,1549901114,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","An issue I'd careful with is putting the blockquotes underneath “list”. It's often close to the lists in other interfaces, but I wonder if people will actually assume or find it there. I wouldn't. Point taken, that it might be one of the least used features anyways.",1547510447,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","To the icon: Blockquote command is basically done in every Rich Text Editor GUI (email/web) with the beginning (English!) quotes “ that we use for “Cite” function in VE. 
+Gmail as example {F27892598 size=thumb}
+
+We've prob locked ourselves out for using the same icons for those two different use cases, although I wonder how many new editors are confused by finding a functionality that the assume to know resulting in a different action.
+",1547510262,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",">>! In T76426#4878309, @iamjessklein wrote:
+> Re: changing the location of blockquotes: I know that @cmadeo did some kind of audit when she was look at editing app UIs. Carolyn - did you find the block quotes functionality located in other places in the UI? (Other than nested under the dropdown for paragraph styles). I'd like to be a bit mindful before moving this because we are trying to maintain consistency as much as possible across the different interfaces. 
+
+Unfortunately block quote was not a common formatting option:
+- The Notion app places block quotes in with both what we consider paragraph stylings and list styles
+- The Medium app has block quotes as it's own toolbar level option (eg. not related to paragraph stylings)
+
+Currently on the iOS app we're following suit with how VE is handling this, but I'm happy to move this out of paragraph styling if you all come to a different conclusion. 
+
+Not based on any testing, but I could see this falling under text stylings (same as computer code), but it does seem like block quote and preformatted text should be grouped together. Is this issue (alienated paragraphs) occurring with preformatted text from VE? ",1547493537,PHID-USER-rblpzor23smiqjmaezyw,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Re: changing the location of blockquotes: I know that @cmadeo did some kind of audit when she was look at editing app UIs. Carolyn - did you find the blockquotes functionality located in other places in the UI? (Other than nested under the dropdown for paragraph styles). I'd like to be a bit mindful before moving this because we are trying to maintain consistency as much as possible across the different interfaces. 
+
+Re: identifying an appropriate icon for blockquotes: In terms of icon, most folks have it as quotes (even phabricator). Medium has an interaction where you click the button multiple times and cycle through the different options for quote formatting, but I find that to be a touch unintuitive. I'm not sure what to use in terms of the icon though, I suspect that if we have multiple quote icons it could begin to complicate the issue. cc/ @Volker_E ",1547490322,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Copying replies from gerrit:
+
+> Should the tool remain in the ""Format"" menu? Probably not, ...
+Agreed.
+
+> Should Ctrl+8 remain as the keyboard shortcut? ...
+Meh. We have ctrl+shift+5 for strikethrough, and we short on available shortcuts
+
+> Should the tool have an icon? ...
+Yeah - ""quotes"" is fine for now - if we don't like the duplication we can fix it later.
+
+> Should we have some styles that make it easier to tell where a blockquote begins and ends...
+Possibly - they should be subtle/greyed out so it's clear they aren't part of the read mode styling, a bit like how we have default table cell styling. Some wikis do have blockquote styling though.",1543334481,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","cc @iamjessklein 
+
+The patch proposes moving the tool from ""Format"" to ""Structure"":
+| {F27317563}| {F27317557} 
+…and some interesting changes to how the tool behaves – blockquotes can now be nested in other nodes (e.g. lists) and have other nodes nested inside them (e.g. also lists, but more simply, paragraphs and headings etc.). They can also be nested in each other.
+
+Open questions:
+* Should the tool remain in the ""Format"" menu? Probably not, as that
+  would allow two items in that menu to be active at the same time,
+  which looks silly.
+* Should Ctrl+8 remain as the keyboard shortcut? It doesn't really
+  make sense anymore now that this is not the 8th item in the ""Format""
+  menu.
+* Should the tool have an icon? There is space for one now. I wanted
+  to use 'quotes', but it has been usurped by Citoid.
+* Should we have some styles that make it easier to tell where a
+  blockquote begins and ends, especially in case the user inserts
+  multiple next to each other?
+",1543307404,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475962 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] Update stuff for making blockquote a non-content branch node
+
+[[https://gerrit.wikimedia.org/r/475962]]",1543306862,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 475961 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[VisualEditor/VisualEditor@master] Make blockquote a non-content branch node, update tools and stuff accordingly
+
+[[https://gerrit.wikimedia.org/r/475961]]",1543306847,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",This has become a priority because of {T209162}.,1543305873,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",We can resurrect https://gerrit.wikimedia.org/r/329448 if we provide a tool for blockquote insertion,1519655235,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 329448 abandoned by Divec:
+Make BlockquoteNode fully non-ContentBranchNode
+
+Reason:
+We went the opposite way (fully ContentBranchNode) in 94dbb244dd
+
+[[https://gerrit.wikimedia.org/r/329448]]",1519645073,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are","Change 329448 had a related patch set uploaded (by Bartosz Dziewoński; owner: Divec):
+[VisualEditor/VisualEditor@master] Make BlockquoteNode fully non-ContentBranchNode
+
+[[https://gerrit.wikimedia.org/r/329448]]",1519644702,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",">>! In T76426#801853, @Whatamidoing-WMF wrote:
+> What is a CBN?
+
+Content branch node.",1417540280,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are",What is a CBN?,1417540133,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6gtwxeyvjyc66bmigmaz,task_subcomment,NA
+New search interface for link dialogue,"As a new editor I want to see more information about pages so that I can choose the correct 1 to link to.
+
+Problem: The existing search interface doesn't look like a list of articles on Wikipedia. 
+Based on usability testing, this is rated a 3 - Major usability problem: important to fix, so should be given high priority.
+https://www.mediawiki.org/wiki/VisualEditor/Usability#Creating_a_link
+
+View click-through prototype here http://invis.io/NP2TOI4GU
+
+{F34278}
+
+Title area of dialogue shows Link icon, ""Link to page"" and ""External link"". Clicking External link will take user to T76398
+
+The search field will be filled with the text the user has selected to link.
+
+The search items show:
+Image thumbnail, article title, wikidata description
+Article icon if no lead image
+Indicate Redirect to [[article]] with redirect icon
+Indicate disambiguation page with its icon
+Empty page icon if redlink
+
+",1417474573,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-llwgzv3tlimidw6znewt,task_description,resolved
+New search interface for link dialogue,"Based on usability testing, this is rated a 3 - Major usability problem: important to fix, so should be given high priority.
+Summary: Users don't realize that the link's search results are actual pages on Wikipedia.
+2 out of 5 tested were able to link to a page with a title different from link text. 
+https://www.mediawiki.org/wiki/VisualEditor/Usability#Creating_a_link
+",1429124247,PHID-USER-flenunkasbjk4topxvaj,True,PHID-TASK-llwgzv3tlimidw6znewt,task_subcomment,NA
+New search interface for link dialogue,I have a WIP patch for a page selector widget at https://gerrit.wikimedia.org/r/#/c/195240/ - in case it helps.,1427167676,PHID-USER-m2yck6646cdt5t6zkta4,True,PHID-TASK-llwgzv3tlimidw6znewt,task_subcomment,NA
+New search interface for link dialogue,"Content Translation also need this component to enhance our link adaptation features, also for providing a better source article selector.
+
+Is this currently planned as  a reusable component so that other projects can use it? Is there any rough timeline for implementation?",1425883552,PHID-USER-m2yck6646cdt5t6zkta4,True,PHID-TASK-llwgzv3tlimidw6znewt,task_subcomment,NA
+New search interface for link dialogue,"For the option to create a red link, we may consider a language more related to the user action. So instead of ""Page does not exist yet"", we can label that option as ""Link as a missing page"" or something along those lines.",1424687811,PHID-USER-c47vnc2yxmwfvvc4367q,True,PHID-TASK-llwgzv3tlimidw6znewt,task_subcomment,NA
+Incorrect Parsoid output for image wrapped in bold and paragraph,"For this wikitext: 
+```
+<p>'''[[File:Wiki.png|thumb]]'''</p>
+```
+Parsoid produces HTMLDOM that has bold tag inside anchor tag inside figure tag - which is not consistent with https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec
+```
+<!DOCTYPE html>
+<html prefix=""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/""><head prefix=""mwr: http://en.wikipedia.org/wiki/Special:Redirect/""><meta property=""mw:articleNamespace"" content=""0""/><meta property=""mw:parsoidVersion"" content=""0""/><link rel=""dc:isVersionOf"" href=""//en.wikipedia.org/wiki/Main%20Page""/><title></title><base href=""//en.wikipedia.org/wiki/""/><link rel=""stylesheet"" href=""//en.wikipedia.org/w/load.php?modules=mediawiki.legacy.commonPrint,shared|mediawiki.skinning.elements|mediawiki.skinning.content|mediawiki.skinning.interface|skins.vector.styles|site|mediawiki.skinning.content.parsoid&amp;only=styles&amp;debug=true&amp;skin=vector""/></head><body data-parsoid='{""dsr"":[0,37,0,0]}' lang=""en"" class=""mw-content-ltr sitedir-ltr ltr mw-body mw-body-content mediawiki"" dir=""ltr""><p data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""dsr"":[0,6,3,0]}'><b data-parsoid='{""autoInsertedEnd"":true,""dsr"":[3,6,3,0]}'></b></p><figure class=""mw-default-size"" typeof=""mw:Image/Thumb"" data-parsoid='{""optList"":[{""ck"":""thumbnail"",""ak"":""thumb""}],""dsr"":[6,29,2,2]}'><a href=""./File:Wiki.png"" data-parsoid='{""a"":{""href"":""./File:Wiki.png""},""sa"":{},""dsr"":[8,27,null,null]}'><b data-parsoid='{""tsr"":null,""autoInsertedEnd"":true,""autoInsertedStart"":true}'><img resource=""./File:Wiki.png"" src=""//upload.wikimedia.org/wikipedia/en/b/bc/Wiki.png"" height=""155"" width=""135"" data-parsoid='{""a"":{""resource"":""./File:Wiki.png"",""height"":""155"",""width"":""135""},""sa"":{""resource"":""File:Wiki.png""}}'/></b></a></figure><p data-parsoid='{""autoInsertedStart"":true,""stx"":""html"",""dsr"":[32,36,0,null]}'></p>
+</body></html>
+```
+It breaks rendering for such wikitext in VisualEditor.",1417463326,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-2krxsenupth53kalib2f,task_description,resolved
+Incorrect Parsoid output for image wrapped in bold and paragraph,This should now be fixed in latest master. New code will be deployed to production on Monday. Please verify and reopen if not fixed.,1438291931,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-2krxsenupth53kalib2f,task_subcomment,NA
+Incorrect Parsoid output for image wrapped in bold and paragraph,"This is a variation of T70395  where the paragraph tags are present as HTML tags in the wikitext rather than being added by the paragraph wrapper.
+
+```a
+
+'''[[File:Wiki.png|thumb]]'''
+
+b```
+
+renders properly. So, the fixes for T70395 need to be expanded to deal with HTML <p> tags as well.",1417514118,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-2krxsenupth53kalib2f,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"NOTE: This Google Summer of Code project has been completed successfully. Thank you @tinaj1234 for your contributions, and thank you @01tonythomas for your technical mentoring. This team has worked very well so far!
+
+For details, read {T109288}.
+
+The work continues at {T110170}. As always, your feedback and contributions are welcome. This is not an internship project anymore; patches are very welcome.  :)
+
+== Newsletter extension ==
+
+An extension allowing publishers to create newsletters and announce new issues, and allowing users to browse and subscribe to newsletters.
+
+A #Google-Summer-of-Code-2015 project lead by @tinaj1234, mentored by @01tonythomas and @qgil.
+
+Currently working on {T99784} and blockers.
+
+Weekly reports: T100997
+Weekly meetings: every [[ http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150605T1030 | Thursday at 10:30 UTC ]] (4pm IST, 12:30 CEST, 3:30 PST) in `#wikimedia-ect` IRC. 
+URL of web proxy of Labs instance where development takes place : http://newsletter-test.wmflabs.org/
+
+== Plan ==
+
+=== Readers ===
+
+* **A catalog of newsletters in one multilingual wiki** (Meta). Let's start defining a single translatable location to find all the newsletters. Meta is the logical choice. No matter which project the newsletter authors come from, all of them would create and organize their newsletters in a common location.
+* Easy subscription. As a logged-in user, click a button. As anonymous user, log in or create an account. (Ideally just entering an email address would work too, with confirmation). Question: should an email address in your profile be required? Can this be checked? Echo probably has solved this.
+* A notification is received when a new issue is published. Notifications are handled via Echo, and therefore they can be received via web or email according to user preferences.
+* Easy to unsubscribe. As a logged-in user, click a button. Accessing a URL from notifications should unsubscribe you as well, after confirmation.
+* Usernames and emails of subscribes should be kept private. The number of users subscribed to a newsletter would be public (and eventually used to promote popular newsletters).
+
+=== Publishers ===
+
+* A process defining the conditions in which a newsletter can be created, featured, demoted, closed (actions that might imply database changes). Just a basic framework to promote best practices and prevent abuse.
+* Once a newsletter is created, maintaining the content (homepage, subpages) could be done in a plain wiki way for creating pages, watching, editing, reverting, protecting if needed... New content is in practice a draft, since it hasn't been announced to the subscribers. Whoever wants to watch changes can read the drafts and get involved.
+* Once a new issue (a page) is ready, the owners of the newsletter send a notification. This requires special permissions.
+
+**Permissions**
+Any autoconfirmed user can become a publisher - create newsletters, announce issues, manage newsletters because of two particular reasons ( quoting Quim ):
+  # Autoconfirmed users can create newsletter pages and issues anyway (even anonymous can).
+  # Even if a publisher were to cause any kind of damage it will affect popularity of their newsletters as well. The extension takes care of subscriptions to the newsletter and notifications from newsletters and hence the creation of newsletters and issues are external to our extension.
+=== Newsletters ===
+A newsletter generally has one or more of the following properties (some newsletters have more of these than others):
+
+* Home page: a page that contains information about the newsletter and what it contains
+* Current issue page: self-explanatory
+* Archive pages: past editions of the newsletter that were previously published
+* Authors / Editors: a group of people that are allowed and/or expected to contribute content
+* Publishers: a group of people that are allowed to finalize an edition and publish it to readers
+
+Most likely, showing a user (on the preferences page mentioned above) a link to the home page, a description of the newsletter, and maybe a link to the current issue and archive pages would be useful.
+
+As mentioned in a comment below, it would probably be best to shift management of authors and editors to the existing page protection feature, i.e., if the newsletter really needs to be protected from unauthorized editing, make a restriction level and assign authors the necessary permission. Publishers would probably need separate management, and would probably be maintained in the same interface that information about the newsletter itself is maintained.
+
+===Backend===
+Check this Etherpad entry on discussions with hoo: https://etherpad.wikimedia.org/p/newsletterExtension
+While discussing with other developers, we realized there are two options for the extension's backend architecture - either use Contenthandlers or use Database( sql tables ). As of now while we prepare the patches for MVP, the database approach is taken. To choose the best for the extension out of all available options at it's earliest stages of development would be the apt thing to do, hence opening up this section for further discussions.
+
+=== See also ===
+
+* https://www.mediawiki.org/wiki/Extension:Newsletter
+* https://meta.wikimedia.org/wiki/Grants:IdeaLab/Newsletter_extension_for_MediaWiki
+
+===Proposed Schedule===
+
+| **Tasks to be completed **|**Timeline**|**Remarks**|
+|Create Wikimedia Labs project, create instance, community bonding| 28/03/15 - 30/04/15| Created Labs project 'newsletter' and instance, 'newsletter-test'. Successfully ssh-ed to the instance|
+|Decide on MVP plan and create necessary tasks|01/05/15 - 05/05/15|Done |
+|Create the Special:NewsLetterCreate interface, and design DB ( the new table )| 06/05/15 - 10/05/15|Done |
+|Create the Special:NewsLetterManage interface - Publisher's view, Newsletter skeleton| 20/05/15 - 30/05/15|Done |
+|Create Special:Newsletters and deploying features on vagrant| 31/05/15 - 15/06/15|Done |
+|Adding newsletter in Notifications tab of Special:Preferences and completing T101546| 16/06/15 - 24/06/15|Done |
+|  Mid Term Evaluation| 26/06/15 - 03/07/15|Done |
+| Work on Blockers and complete extension considering case of Meta alone and no inter wiki newsletters| 04/07/15 - 20/07/15|Done |
+| Work on T102945, T101832, T104829| 21/07/15 - 10/08/15|Done |
+| Writing unit tests, testing the work flow, documentation, deployment | 11/08/15 - 20/08/15|Done|
+| Final Report Submission| 21/08/2015|Done |",1417165348,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_description,resolved
+Goal: Newsletter extension for MediaWiki,"@ResheilA: Hi! Whatever page called ""CA"" you refer to, it's unrelated to this software development task about creating a MediaWiki extension called ""Newsletter"". Please either use https://www.mediawiki.org/wiki/Project:Support_desk for general software problems, or the village pump of your Wikimedia site instead. Thanks.",1464173003,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#2325761, @ResheilA wrote:
+> Hello !
+> Its long I have been active in this group. Can someone help me up ? I have
+> a page called CA. Uttam Agrawal. And its been deleted by the community. I
+> worked hard on it and all my coded stuff are gone. Help me up !! I need it
+> urgent.
+
+Was your page on a wiki? If yes, I think you should contact the people who maintain the wiki in which your page was in.",1464172981,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hello !
+Its long I have been active in this group. Can someone help me up ? I have
+a page called CA. Uttam Agrawal. And its been deleted by the community. I
+worked hard on it and all my coded stuff are gone. Help me up !! I need it
+urgent.
+
+
+
+Resheil Agarwal,
+Founder,
+Webportal.in",1464170352,PHID-USER-sututmegiourdiellndf,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"If you try to say that there is no way to fix the issues I bring up in this particular software development, yes I am aware of that. I try to give feedback not just for the moment, but also for future developments.
+
+> please correct me if I'm not understanding your recommendations
+You are not understanding my recommendations.
+
+And I finish reacting here, I have made my points clear. Other people seem to understand them, and being ridiculed is not something I would like to continue.",1440768632,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, the problem I see is that you leave us no reasonable options following your line of argument. According to your standards, what specific requirements should we handle in this project to guarantee this continuity? A full-time position hired by the Wikimedia Foundation with budget assured for the years to come? And if we don't reach your standards, should we stop this project altogether? This is literally what I understand reading your comments, please correct me if I'm not understanding your recommendations.
+
+As said several times, there is a process to evaluate extensions willing to be deployed in Wikimedia servers (T110170). That process is open for community enquiries and feedback. I will be the first one not pushing for this extension if its development and maintenance plan has open blockers or other flaws. The people that can seriously stop this initiative are the ones that will have to eventually maintain it if the three current contributors involved suddenly disappear from planet Earth. It's free software, all the code and documentation is available, and this is the ultimate guarantee that if there is a serious problem, it can be solved by someone with the skills. This is how the actual economy of open source software works, at Wikimedia and mostly every project maintaining a large codebase.
+
+> If important factors for end-users are missing in software, the software is incomplete.
+
+Please, file tasks for any feature you are missing.",1440568412,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, the problem I see is that you leave us no reasonable options following your line of argument. According to your standards, what specific requirements should we handle in this project to guarantee this continuity? A full-time position hired by the Wikimedia Foundation with budget assured for the years to come? And if we don't reach your standards, should we stop this project altogether? This is literally what I understand reading your comments, please correct me if I'm not understanding your recommendations.
+
+As said several times, there is a process to evaluate extensions willing to be deployed in Wikimedia servers (T110170). That process is open for community enquiries and feedback. I will be the first one not pushing for this extension if its development and maintenance plan has open blockers or other flaws. The people that can seriously stop this initiative are the ones that will have to eventually maintain it if the three current contributors involved suddenly disappear from planet Earth. It's free software, all the code and documentation is available, and this is the ultimate guarantee that if there is a serious problem, it can be solved by someone with the skills. This is how the actual economy of open source software works, at Wikimedia and mostly every project maintaining a large codebase.",1440568359,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, the problem I see is that you leave us no reasonable options following your line of argument. According to your standards, what specific requirements should we handle in this project to guarantee this continuity? A full-time position hired by the Wikimedia Foundation with budget assured for the years to come? And if we don't reach your standards, should we stop this project altogether? This is literally what I understand reading your comments, please correct me if I'm not understanding your recommendations.
+
+As said several times, there is a process to evaluate extensions willing to be deployed in Wikimedia servers (T110170). That process is open for community enquiries and feedback. I will be the first one not pushing for this extension if its development and maintenance plan has open blockers or other flaws. The people that can seriously stop this initiative are the ones that will have to eventually maintain it if the three current contributors involved suddenly disappear from planet Earth. It's free software, all the code and documentation is available, and this is the ultimately guarantee that if there is a serious problem, it can be solved by someone with the skills. This is how the actual economy of open source software works, at Wikimedia and mostly every project maintaining a large codebase.",1440568298,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I think we keep too much talking around the core of the problem.
+
+> disappears one day, users of this extension would be able to go back to the current way keeping whatever subscribers they have.
+You are with this confirming the problem I indicated.
+Unless a software development is intended to be temporary, one of the most important parts for end users is continuity. As I said in my initial post about the problems in the process, this is an example of such problem. The continuity as important aspect would have come up if there was a genuine involvement of the stakeholders/end users.
+
+I was concerned about the process, but I am now really surprised. If important factors for end-users are missing in software, the software is incomplete. If I tell this to my community, they find this crazy. Not to mention the waste of resources.
+
+",1440544451,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I think we keep too much talking around the core of the problem.
+
+> disappears one day, users of this extension would be able to go back to the current way keeping whatever subscribers they have.
+You are with this conforming the problem I indicated.
+Unless a software development is intended to be temporary, one of the most important parts for end users is continuity. As I said in my initial post about the problems in the process, this is an example of such problem. The continuity as important aspect would have come up if there was a genuine involvement of the stakeholders/end users.
+
+I was concerned about the process, but I am now really surprised. If important factors for end-users are missing in software, the software is incomplete. If I tell this to my community, they find this crazy. Not to mention the waste of resources.
+
+",1440544423,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, what @bawolff said.
+
+{T110170} has a long and complex review process ahead, designed to test the appropriateness and robustness of this piece of software and their maintainers. 
+
+Even if one day this extension is implemented in Wikimedia, newsletter owners will not be forced to use it. If you want to keep your current way of managing your newsletter, just keep it. And in the way it is designed, even if the extension blows up and disappears one day,  users of this extension would be able to go back to the current way keeping whatever subscribers they have.
+
+So really, I don't see which harm we are causing by trying to develop and contribute the right thing. ",1440541827,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> In this particular case, I believe yes, because several Foundation-led efforts---the Research Newsletter and Tech/News---will come to rely on it. A cynical answer but a correct one.
+
+This is really an important part of developing software. If newsletters, like mine, are going to use an extension, it is important that continuity is arranged.
+And again, general, I see too little commitment in the Wikimedia Foundation to secure the continuity.
+
+> if Wikimedia would have deployed only software written by people guaranteed to stay around in the long term
+Sorry, but this is not the essence. It is not about individual people. It can be various people. The essence is that WMF gives a guarantee.
+
+> I still think this feature is needed and will be welcome by many authors of current and future newsletters.
+I think not, the number one overall complaint from the community what I see (beyond the irritations of changes and worse styles of implementations) is that the community gets bored that again and again and again software is failing and no longer repaired, while the community makes active use of it. Sure there will be lots of people who have not the previous experience of failing software due lack of maintenance, and like the extension, but that is overall only a short term situation of continuity is not guaranteed.",1440540344,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> But will the Foundation commit to maintaining this extension in the long term?
+
+WMF and volunteer developers do critical maintenance on all extensions deployed to Wikimedia. Whether or not there will be long term resources dedicated to improving the extension depends on a lot of factors which are anyone's guess, but if it is deployed, it will at least be kept in working order.",1440536867,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> But will the Foundation commit to maintaining this extension in the long term?
+
+This is a discussion for {T110170}. See you there.  :)
+
+PS: I'm well aware of of the problem of software maintenance. Then again, if Wikimedia would have deployed only software written by people guaranteed to stay around in the long term, we would have never got MediaWiki and friends. I still think this feature is needed and will be welcome by many authors of current and future newsletters.",1440518091,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Qgil Unlike communications interns, tech interns create products that the community has to rely on in the long term. But will the Foundation commit to maintaining this extension in the long term?
+
+In general, no (you say ""that's not the point""). In this particular case, I believe yes, because several Foundation-led efforts---the Research Newsletter and Tech/News---will come to rely on it. A cynical answer but a correct one.",1440512851,PHID-USER-rtxvf2yd2qd3qmsps3bk,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This Google Summer of Code project has been completed successfully. Thank you @tinaj1234 for your contributions, and thank you @01tonythomas for your technical mentoring. This team has worked very well so far!
+
+For details, read {T109288}.
+
+The work continues at {T110170}. As always, your feedback and contributions are welcome. This is not an internship project anymore; patches are very welcome.  :)",1440494638,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Ohh,1440442926,PHID-USER-muobtocub3solbj4sz5f,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"For what is worth, {T108205} is still open, to be closed this week.",1440442224,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas - okay, thanks, that's helpful. I don't know if giving someone credit for code he didn't write is ""perfect"" - it could confuse people (at least, it confused me). Those credits, like the ""author"" field in mediawiki.org infoboxes, are not just there to give respect; they also give helpful information, like whom to contact if you're thinking of submitting a patch. What about adding a ""History"" section to the mediawiki.org page, to be able to credit Siebrand while clarifying the current situation?",1440438738,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1568209, @Yaron_Koren wrote:
+> @01tonythomas - when you say ""built from scratch"", does that mean that the old extension code was simply wiped out? Looking at the mediawiki.org page, it doesn't look that way - Siebrand is still listed as the author of the extension.
+
+Yeah - the first commit by @Tinaj1234 wiped out everything ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/commit/f0e8491e0c1abda0117b67f05db42fbc708568ca ) if you ignore $wgExtensionCredits entries in Newsletter.php :).  Since @siebrand made an inital commit of the extension in https://github.com/wikimedia/mediawiki-extensions-Newsletter/commit/8cf079a2c2cb71670728eef36c9e42ccbff077be back in 2013 - I think @Tinaj1234 wants to give him credit for his work - which is perfect. ",1440436842,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas - when you say ""built from scratch"", does that mean that the old extension code was simply wiped out? Looking at the mediawiki.org page, it doesn't look that way - Siebrand is still listed as the author of the extension.",1440436546,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"In the Internet most newsletters have a private list of subscribers. If you want to discuss this topic further, please create a new task.
+
+Google Summer of Code has strict deadlines. Projects have to deliver functional code in less than four months. We cannot spend half of that time waiting for feedback without writing any code.
+
+On resources, Tina is a volunteer receiving a stipend from Google, Tony is volunteering as primary mentor, and I'm dedicating about 1-2 hours/week as secondary mentor. Other people has been involved in this project in a smaller capacity, most of them by personal initiative and as volunteers.
+
+I have re-read your comments above, and I still don't see which specific problems can we address. You say
+
+> * MediaWiki is not designed for global navigation, nor navigation across wikis.
+
+I'm not sure what that means, but in any case this extension is not read for interwiki use today. This was left out of scope for the GSoC project and needs to be revisited now.
+
+> * the MediaWiki software is very primitive - it is for example not possible to create a simple button in what someone can (un)subscribe or one of the many other limitations that prevent it to be easy.
+
+This extension allows users to subscribe and unsubscribe from newsletters using checkboxes.
+
+Again, you are encouraged to file tasks for specific problems.",1440415565,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> I'm sorry you received such notifications in your busiest time, but I hope you understand that we cannot wait for the best spot in everybody's agendas. In terms of communication and feedback, I think we have covered the minimum and more.
+That was not my point. It reacted on this:
+> worked upon for 4-5 months and was open to anyone interested
+But only 2 months time was actually given to react.
+
+As said before, I am especially disappointed in the problem definition and how the plan in post 1 is described. I gave feedback on that. I have described problems in the process, but I do not get the impression that it is taken seriously.
+
+@Tinaj1234 & @01tonythomas My apologies to you both if my messages are unpleasant. The problems I notice are outside your involvement in this project (so far I understand). I am personally concerned about how the resources (like you) are used in software development. So please do not take this as criticism on your work, so far I can see you have done in the given circumstances a great job. ",1440410042,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> User expectations, user privacy.
+Those are choices. Here it is chosen to give users privacy. I think it is thought too easy about this.
+
+> It is a usual practice in the Internet that only admins of a newsletter can see who is subscribed to it. For what is worth, by default Wikimedia mailing lists don't disclose the identity of their subscribers either, and only their admins can access to this data.
+It is a usual practice thanks to Twitter and other social media that it is publicly known who is watching what. The comparison with mailing lists is not accurate enough imo.
+",1440409090,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1564774, @Romaine wrote:
+> 
+>> Usernames and emails of subscribes should be kept private. The number of users subscribed to a newsletter would be public (and eventually used to promote popular newsletters).
+> 
+> I do not see a reason for this.
+
+User expectations, user privacy. It is a usual practice in the Internet that only admins of a newsletter can see who is subscribed to it. For what is worth, by default Wikimedia mailing lists don't disclose the identity of their subscribers either, and only their admins can access to this data.",1440407054,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1564774, @Romaine wrote:
+> 
+>> Usernames and emails of subscribes should be kept private. The number of users subscribed to a newsletter would be public (and eventually used to promote popular newsletters).
+> 
+> I do not see a reason for this.
+
+User expectations, user privacy. It is a usual practice that only admins of a newsletter can see who is subscribed to it. For what is worth, by default Wikimedia mailing lists don't disclose the identity of their subscribers either, and only their admins can access to this data.",1440402234,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, @ResMar, here goes some background and a request to be respectful with the open and documented work that others are doing. The summary is: I think this project and its lead developer don't deserve the tone of your first posts here, feel free to learn and ask about the steps we have done, and by all means please bring all the specific objections you might have about this project.
+
+Since 2013, I have been advocating for a newsletter type of functionality for MediaWiki, to be deployed in Wikimedia servers (if you want me to dig in wikitech-l archives, I will). Anybody working on a project in our context knows about the difficulty of setting up one-to-many communications with regular Internet users, not necessarily familiar with watching pages (and following watchlists) or subscribing to services MassMessage style.
+
+https://www.mediawiki.org/wiki/Extension:Newsletter was created on 10 September 2013‎, after I proposed @Siebrand to fork the code related to notifications in the Translate extension. That path didn't progress further.
+
+After some discussions in the context of MassMessage tasks, it was clear that that project would not be the solution for this use case. In 28 November 2014 I created this task. 
+
+The rest can be read in this task. On 10 February 2015 I proposed it as a #Possible-Tech-Projects, and from that point it entered the community review process. @01tonythomas (a former GSoC student, sticking around) volunteered as technical mentor. @Tinaj1234 stepped in as a Google Summer of Code candidate, together with several other students. Tina was selected, and we started to work following the GSoC deadlines. We had a couple of scheduled sessions at the Wikimedia Hackathon in Lyon on May, in June we contacted all the newsletter admins we found in several Wikimedia projects... 
+
+I'm sorry you received such notifications in your busiest time, but I hope you understand that we cannot wait for the best spot in everybody's agendas. In terms of communication and feedback, I think we have covered the minimum and more.
+
+As of today this GSoC project is actually completed, awaiting only its evaluation. We are already discussing the next steps, which include addressing the open tasks, and go through the process to have this extension deployed in Beta, Meta, and then we'll see. Even if you just joined the discussion now, you still have time and chances to bring your feedback and objections.
+
+This is about the project. Now let me add something about the developer that has put hundreds of hours on it in the past months. @Romaine @ResMar,  our new developers deserve a welcoming attitude from all of us. Especially when they are volunteers and interns in programs like GSoC, where Wikimedia decides to participate with a tailored community review process. Nobody knows whether these newcomers will be around in three years. And by the way, the same could be said about all of us (yourselves included) when we joined, and still today.
+
+But you know what? In this specific case it is not even accurate to call @tinaj1234 a newcomer. [[ https://gerrit.wikimedia.org/r/#/q/owner:%22Tinaj1234+%253Ctinajohnson.1234%2540gmail.com%253E%22,n,z | Her first patches ]] for Wikimedia were uploaded on December 2013 and since then she has got code merged in MediaWiki core and some extensions. She has a [[ https://www.mediawiki.org/wiki/User:Tinaj1234 | user account in mediawiki.org ]] since February 2014, when she started to prepare a GSoC proposal. She wasn't accepted because another candidate was chosen for the same project instead (@wctaiwan, who is another example of a GSoC student sticking around until today). So really, Tina has shown a remarkable level of commitment and perseverance even before the end of her GSoC internship.",1440407501,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, @ResMar, here goes some background and a request to be respectful with the open and documented work that others are doing. The summary is: I think this project and its lead developer don't deserve the tone of your first posts here, feel free to learn and ask about the steps we have done, and by all means please bring all the specific objections you might have about this project.
+
+Since 2013, I have been advocating for a newsletter type of functionality for MediaWiki, to be deployed in Wikimedia servers (if you want me to dig in wikitech-l archives, I will). Anybody working on a project in our context knows about the difficulty of setting up one-to-many communications with regular Internet users, not necessarily familiar with watching pages (and following watchlists) or subscribing to services MassMessage style.
+
+https://www.mediawiki.org/wiki/Extension:Newsletter was created on 10 September 2013‎, after I proposed @Siebrand to fork the code related to notifications in the Translate extension. That path didn't progress further.
+
+After some discussions in the context of MassMessage tasks, it was clear that that project would not be the solution for this use case. In 28 November 2014 I created this task. 
+
+The rest can be read in this task. On 10 February 2015 I proposed it as a #Possible-Tech-Projects, and from that point it entered the community review process. @01tonythomas (a former GSoC student, sticking around) volunteered as technical mentor. @Tinaj1234 stepped in as a Google Summer of Code candidate, together with several other students. Tina was selected, and we started to work following the GSoC deadlines. We had a couple of scheduled sessions at the Wikimedia Hackathon in Lyon on May, in June we contacted all the newsletter admins we found in several Wikimedia projects... 
+
+I'm sorry you received such notifications in your busiest time, but I hope you understand that we cannot wait for the best spot in everybody's agendas. In terms of communication and feedback, I think we have covered the minimum and more.
+
+As of today this GSoC is actually completed, awaiting only its evaluation. We are already discussing the next steps, which include addressing the open tasks, and go through the process to have this extension deployed in Beta, Meta, and then we'll see. Even if you just joined the discussion now, you still have time and chances to bring your feedback and objections.
+
+This is about the project. Now let me add something about the developer that has put hundreds of hours on it in the past months. @Romaine @ResMar,  our new developers deserve a welcoming attitude from all of us. Especially when they are volunteers and interns in programs like GSoC, where Wikimedia decides to participate with a tailored community review process. Nobody knows whether these newcomers will be around in three years. And by the way, the same could be said about all of us (yourselves included) when you joined, and still today.
+
+But you know what? In this specific case it is not even accurate to call @tinaj12143 a newcomer. [[ https://gerrit.wikimedia.org/r/#/q/owner:%22Tinaj1234+%253Ctinajohnson.1234%2540gmail.com%253E%22,n,z | Her first patches ]] for Wikimedia were uploaded on December 2013 and since then she has got code merged in MediaWiki core and some extensions. She has a [[ https://www.mediawiki.org/wiki/User:Tinaj1234 | user account in mediawiki.org ]] since February 2014, when she started to prepare a GSoC proposal. She wasn't accepted because another candidate was chosen for the same project instead (@wctaiwan, who is another example of a GSoC student sticking around until today). So really, Tina has shown a remarkable level of commitment and perseverance even before the end of her GSoC internship.",1440401343,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Romaine, @ResMar, here goes some background and a request to be respectful with the open and documented work that others are doing. The summary is: I think this project and its lead developer don't deserve the tone of your first posts here, feel free to learn and ask about the steps we have done, and by all means please bring all the specific objections you might have about this project.
+
+Since 2013, I have been advocating for a newsletter type of functionality for MediaWiki, to be deployed in Wikimedia servers (if you want me to dig in wikitech-l archives, I will). Anybody working on a project in our context knows about the difficulty of setting up one-to-many communications with regular Internet users, not necessarily familiar with watching pages (and following watchlists) or subscribing to services MassMessage style.
+
+https://www.mediawiki.org/wiki/Extension:Newsletter was created on 10 September 2013‎, after I proposed @Siebrand to fork the code related to notifications in the Translate extension. That path didn't progress further.
+
+After some discussions in the context of MassMessage tasks, it was clear that that project would not be the solution for this use case. In 28 November 2014 I created this task. 
+
+The rest can be read in this task. On 10 February 2015 I proposed it as a #Possible-Tech-Project, and from that point it entered the community review process. @01tonythomas (a former GSoC student, sticking around) volunteered as technical mentor. @Tinaj1234 stepped in as a Google Summer of Code candidate, together with several other students. Tina was selected, and we started to work following the GSoC deadlines. We had a couple of scheduled sessions at the Wikimedia Hackathon in Lyon on May, in June we contacted all the newsletter admins we found in several Wikimedia projects... 
+
+I'm sorry you received such notifications in your busiest time, but I hope you understand that we cannot wait for the best spot in everybody's agendas. In terms of communication and feedback, I think we have covered the minimum and more.
+
+As of today this GSoC is actually completed, awaiting only its evaluation. We are already discussing the next steps, which include addressing the open tasks, and go through the process to have this extension deployed in Beta, Meta, and then we'll see. Even if you just joined the discussion now, you still have time and chances to bring your feedback and objections.
+
+This is about the project. Now let me add something about the developer that has put hundreds of hours on it in the past months. @Romaine @ResMar,  our new developers deserve a welcoming attitude from all of us. Especially when they are volunteers and interns in programs like GSoC, where Wikimedia decides to participate with a tailored community review process. Nobody knows whether these newcomers will be around in three years. And by the way, the same could be said about all of us (yourselves included) when you joined, and still today.
+
+But you know what? In this specific case it is not even accurate to call @tinaj12143 a newcomer. [[ https://gerrit.wikimedia.org/r/#/q/owner:%22Tinaj1234+%253Ctinajohnson.1234%2540gmail.com%253E%22,n,z | Her first patches ]] for Wikimedia were uploaded on December 2013 and since then she has got code merged in MediaWiki core and some extensions. She has a [[ https://www.mediawiki.org/wiki/User:Tinaj1234 | user account in mediawiki.org ]] since February 2014, when she started to prepare a GSoC proposal. She wasn't accepted because another candidate was chosen for the same project instead (@wctaiwan, who is another example of a GSoC student sticking around until today). So really, Tina has shown a remarkable level of commitment and perseverance even before the end of her GSoC internship.",1440401294,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1566016, @ResMar wrote:
+> I think that Romaine is implicitly criticizing a problem that's plagued the movement for a long time: outside contractors are brought in, write a feature, and then leave. No offense to you, Tinaj, but I //highly// doubt that say three years from now you will be maintaining this codebase, or even contactable.
+
+Just for the record, there are several developers who had GSOC projects and stuck around for 3 or more years. I have no idea if Tinaj will be one of them, and s/he certainly has no obligations past the end of his/her project but its entirely possible that s/he could be.
+
+> 
+> In your absence no one attached to the movement will be familiar with the code, causing it to trip up other extensions, suffer legacy rot, and eventually become completely unusable. This turnover problem is one half of the legacy dependence problem of the Wikimedias (a total lack of intercommunal standards across Wikimedias is the other half).
+> 
+> In this case the extension backs into a ""platform for the future"", Echo, that's in continual development. Hopefully that will keep this extension alive.
+
+I'm not sure its fair to have this discussion here. These sound more like generic issues surrounding the GSOC/OPW program and doesn't have much to do with this particular project.
+
+Keep in mind, creating a feature for use by the Wikimedia movement over the long term is not necessarily the goal of the GSOC/OPW program.",1440395825,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1566284, @Yaron_Koren wrote:
+> Can someone briefly explain the goal of this project? From the title and description, it sounds like a project to create a new extension. But instead, this project seems to have modified an existing extension, [[ https://www.mediawiki.org/wiki/Extension:Newsletter | ""Newsletter""]]. Is that the case? If so, did the task change at some point? And what is the goal that was achieved?
+
+The goal of the project was to build a 'Newsletter' extension which must allow: 
+
+
+  # Newsletter Authors to easily create and manage Newsletters with scope limited to his rights
+  # A usual wiki user to subscribe/unsubscribe to available newsletters in his Wiki ( inter-wiki is post GSoC scope ) 
+  # Receive notifications via web/email using Echo whenever a Newsletter creates a new issuse. 
+
+The project took place basically from the description of this task, and was built from scratch ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/commits/master )  - now live at http://newsletter-test.wmflabs.org/wiki/Main_Page - You can find the instructions on how to use the same over there. @Tinaj1234 will work on it further to cross the arch/sec and performance review to take it to production which is of course, not in the scope of GSoC 2015. 
+",1440394972,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Can someone briefly explain the goal of this project? From the title and description, it sounds like a project to create a new extension. But instead, this project seems to have modified an existing extension, [[ https://www.mediawiki.org/wiki/Extension:Newsletter | ""Newsletter""]]. Is that the case? If so, did the task change at some point? And what is the goal that was achieved?",1440393491,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Thanks ResMar!
+What ResMar is describing is indeed a part of the issue I see. I am concerned about both the process of the development of this software as the general situation of software development. I am concerned about a long term stability.
+
+",1440375449,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I think that Romaine is implicitly criticizing a problem that's plagued the movement for a long time: outside contractors are brought in, write a feature, and then leave. No offense to you, Tinaj, but I //highly// doubt that say three years from now you will be maintaining this codebase, or even contactable.
+
+In your absence no one attached to the movement will be familiar with the code, causing it to trip up other extensions, suffer legacy rot, and eventually become completely unusable. This turnover problem is one half of the legacy dependence problem of the Wikimedias (a total lack of intercommunal standards across Wikimedias is the other half).
+
+In this case the extension backs into a ""platform for the future"", Echo, that's in continual development. Hopefully that will keep this extension alive.",1440372300,PHID-USER-rtxvf2yd2qd3qmsps3bk,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"(Please remember that this bug is about developing a newsletter extension for *MediaWiki*, not *Wikimedia*.)",1440366890,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"> 4-5 months
+We received a message only 2 months ago: 9 June 2015. Just before the most busiest time of the year.
+
+> I don't think the plan [...] is insufficient at all.
+Reading the plan, as described in the first post in this Task, it is insufficient to judge.
+
+> The answer is a 'yes'.
+I doubt that. I think the difference in answering is likely caused by interpreting the questions differently than how they were intended.
+
+I am not necessary negative about the idea, but the plan described in post 1 is insufficient. And the involvement from stakeholders was also insufficient. (Yes, insufficient with the current level of participation.)
+Based on the provided information I get too much the idea that this extension is //developed for// instead of //developed with//. Of course you then say that you have asked newsletter to give feedback, but that makes it still insufficient. The biggest pain in the ass for the Wikimedia community is that they are too little considered to be stakeholder, and are to little involved from the first plan until the end during the whole process.
+
+> I don't quite get what you meant here.
+I described two large issues we experience working on wikis too often. The problem description on Meta can be completely derived from these two large issues. This makes ""fixing"" the described problem a form of treating symptoms, instead of the core problems.
+
+It gives me this feeling: https://xkcd.com/927/
+
+> But we have brought up a beautiful extension which works fine( with tables and buttons and what not ) and is believed to benefit many, do have a look.
+This sounds like a car salesman. I do not think it is a good idea if a developer him/herself is saying that it is beautiful, fine working, benefit many, etc. That is up to the stake holders and end users to judge.
+",1440349365,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1564783, @Romaine wrote:
+> Reading this plan, no publisher is able to give feedback as the actual contents are missing. The actual things that matter to publishers is not described in the plan. The plan described is too vague.
+> 
+> It is like describing a new car: it has doors, a steering wheel, seets, a roof, lights and more. This is completely insufficient.
+I don't think the plan ( which was worked upon for 4-5 months and was open to anyone interested ) is insufficient at all. The extension pretty much makes easy any task a publisher or an owner is required to do. Please go through the features implemented as well because the extension has evolved very much from its initial stages. 
+> Also some other issues:
+> * Where there any publishers and readers involved in the plan?
+> * Has there been any priority check for which software developments are really needed and make a big difference for the movement?
+> * Where there any publishers and readers involved during the development process?
+> 
+> Reading more pages I get the impression that these three questions are to be answered with ""no"".
+The answer is a 'yes'. I see you've gone through T100604 and we waited over a week before closing that task to collect reviews and opinions of stakeholders. A message was left on each page( the list of links in T100604 ) to inform existing newsletters and various other developers about the extension and we were encouraged by a lot of positive replies from many editors and publishers to move forward with the extension. 
+> Seeing what problem description is [[ https://meta.wikimedia.org/wiki/Grants:IdeaLab/Newsletter_extension_for_MediaWiki | given ]], I can only think it is too simplistic and not reaching to the core of the problem: 
+> * MediaWiki is not designed for global navigation, nor navigation across wikis.
+> * the MediaWiki software is very primitive - it is for example not possible to create a simple button in what someone can (un)subscribe or one of the many other limitations that prevent it to be easy.
+I don't quite get what you meant here. But we have brought up a beautiful extension which works fine( with tables and buttons and what not ) and is believed to benefit many, do have a [[ http://newsletter-test.wmflabs.org/wiki/Main_Page | look ]]. ",1440322710,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,,1440311866,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,,1440311815,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Reading this plan, no publisher is able to give feedback as the actual contents are missing. The actual things that matter to publishers is not described in the plan. The plan described is too vague.
+
+It is like describing a new car: it has doors, a steering wheel, seets, a roof, lights and more. This is completely insufficient.
+
+Also some other issues:
+* Where there any publishers and readers involved in the plan?
+* Has there been any priority check for which software developments are really needed and make a big difference for the movement?
+* Where there any publishers and readers involved during the development process?
+
+Reading more pages I get the impression that these three questions are to be answered with ""no"".
+
+Seeing what problem description is [[ https://meta.wikimedia.org/wiki/Grants:IdeaLab/Newsletter_extension_for_MediaWiki | given ]], I can only think it is too simplistic and not reaching to the core of the problem: 
+* MediaWiki is not designed for global navigation, nor navigation across wikis.
+* the MediaWiki software is very primitive - it is for example not possible to create a simple button in what someone can (un)subscribe or one of the many other limitations that prevent it to be easy.
+
+Instead of improving this limited and too often too difficult situation, effort is taken to fight only a symptom of the core problems.
+
+I am afraid that this extension appears to be a waste of energy and resources.",1440311808,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I believe @Qgil was referring to the case of http://newsletter-test.wmflabs.org/wiki/Special:Newsletters where a user need not know who is subscribed to the newsletter instead we tell him/her the popularity of the newsletter through the subscriber count.,1440310566,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"
+> Usernames and emails of subscribes should be kept private. The number of users subscribed to a newsletter would be public (and eventually used to promote popular newsletters).
+
+I do not see a reason for this.
+
+
+",1440309938,PHID-USER-pwdu7zlsq3lcr63acm5c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hi, I have associated two blocked-by tasks with this project. 
+
+**For the student:** 
+1. Please go through the checklist in the end-term evaluation and fill out the fields which require any links. The checkboxes are for the mentor(s) only. Adding information on the past projects page is your task. 
+2. Ensure that you have completed //all// the items listed in the end-term evaluation task. If there's a strong reason about why a particular item was not completed, please comment on the task and we shall look into it. 
+3. Wrap-up report is //mandatory// and so is a demo-able link to the project (either in production or in a demo server). 
+4. If you want your project to be featured in the blogpost on the Google OSPO blog, kindly comment back with a short, catchy description of the project along with a screenshot. ",1439822789,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Great. @Tinaj1234, please write up a short description of the project when you get time for the blog. Also add one, most relevant screenshot which I can include in the post. Thanks!",1439402096,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1528553, @Dzahn wrote:
+> It would be great if you could import the repo to Gerrit instead of working off of github.
+
+Ah. We were committing to Gerrit from the start of the project. We have it over here http://git.wikimedia.org/tree/mediawiki%2Fextensions%2FNewsletter",1439320942,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,It would be great if you could import the repo to Gerrit instead of working off of github.,1439319909,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"In our case, ""merged"" is what exists in the Newsletter extension repo, fully functional in Labs. ""Deployed in Wikimedia"" is a goal for us, but definitely out of scope of GSoC.",1439319554,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1514646, @NiharikaKohli wrote:
+> A few questions (for both mentors and student):
+> - Are you confident in completing the project on time?
+Of course. Almost all the blockers are resolved as of now, and looking at the open tasks at https://phabricator.wikimedia.org/T76199 - its more of the design elements still there. The strictly planned MVP which came as a result of discussions from Lyon and weekly meetings made sure that we have the minimum features ready even before mid-term. This made it easy for @Tinaj1234, as most of the post-mid term works were design stuff. Most features lacked documentation, but @Tinaj1234 was impressive with getting it done. 
+ 
+> - By when do you think you can merge the code, if at all?
+Almost all of the patchsets that showed up in Gerrit was reviewed and merged to the github repo in < 2 days - and if you are talking about deployment to production, it might take a bit long to go through the security, arch and performance review through beta to prod - and I expect these to happen in the coming month. Deployment to production was not a part of the GSoC project, anyway. 
+> - Are there any major blockers or important missing features?
+I dont think there is anything critical as of now. 
+
+Great work till date. You can see the code produced over here : https://github.com/wikimedia/mediawiki-extensions-Newsletter, and test it live at newsletter-test.wmflabs.org
+",1439310932,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1514646, @NiharikaKohli wrote:
+> 
+> A few questions (for both mentors and student):
+> - Are you confident in completing the project on time?
+Yes, ofcourse.
+> - By when do you think you can merge the code, if at all?
+Most of the completed features are merged already. Everything will be merged before 17th August.
+> - Are there any major blockers or important missing features?
+No, all important features are almost done. Remaining high priority tasks will be completed in the coming week.
+
+",1438881037,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hello!
+
+End of GSoC is fast approaching. 17 August is ""Suggested pencils down"" deadline and 21 August is ""Firm pencils down"" deadline. It is expected that you don't dive into new features which might take longer than two weeks to complete and instead work on polishing up your project, testing thoroughly and getting your code merged into the main branch. I hope this project is almost complete so you can merge it and make it available to everyone as quickly as possible. :)
+
+A few questions (for both mentors and student):
+- Are you confident in completing the project on time?
+- By when do you think you can merge the code, if at all?
+- Are there any major blockers or important missing features?
+
+We are looking for projects which are (nearly) complete to feature on our post on Wikimedia and Google OSPO's blogs (for example: http://google-opensource.blogspot.in/2015/02/google-summer-of-code-wrap-up-processing.html). If you're interested in getting yours up there, hurry up and get this finished!
+
+The hard deadline on getting code merged is September. {T101393} for details. 
+
+We'll be asking the students to demo their projects towards the end of the program as well. 
+
+Good luck!",1438873949,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1428602, @ResMar wrote:
+> I do wonder if a short tagline could not be added to the Echo notification (something along the lines of ""In this issue: see what really goes in the Phabricator"")
+Yes, it would be more informative for the readers if the notification can contain more details indicating what the new issue is about. Thank you! I'll add a blocker task for this.
+
+",1436162055,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I tested it a bit. Looking good so far! I do wonder if a short tagline could not be added to the Echo notification (something along the lines of ""In this issue: see what really goes in the Phabricator""), but other than that it's already a dream come true.",1436158629,PHID-USER-rtxvf2yd2qd3qmsps3bk,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I tested it a bit. Looking good so far! I do wonder if a short tagline could not be added to the Echo notification, but other than that it's already a dream come true.",1436158445,PHID-USER-rtxvf2yd2qd3qmsps3bk,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"The criteria to define a blocker should be: 
+
+  Bugfix or feature required to handle newsletters hosted in Meta. 
+
+Let's leave the multi-wiki scenario for the next milestone (hopefully to be still address during this GSoC round, will depend on the blockers for the single wiki scenario).",1435848198,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"The criteria to define a blocker should be: 
+
+ Bugfix or feature required to handle newsletters hosted in Meta. 
+
+Let's leave the multi-wiki scenario for the next milestone (hopefully to be still address during this GSoC round, will depend on the blockers for the single wiki scenario).",1435848184,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Since the MVP is completed we are in position to discuss on our next milestone!
+
+You can see a number of blockers listed in #MediaWiki-extensions-Newsletter workboard. But we think there is a possibility for more blockers and if anyone finds one feel free to create a task and add it to the workboard. The blockers to be closed by end of July will be decided on the next week's meeting ( 9th June 10:30 AM UTC ) and it would be convenient to have all the blockers out by then.
+
+Test MVP here: http://newsletter-test.wmflabs.org/ ( Check description on Main Page to find which page to go to )
+
+@quiddity, @Bawolff, @legoktm Awaiting reviews and comments especially from you guys :)
+  ",1435847222,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Just a note to say that mentoring this project until completion is one of my individual goals for {T101100}.
+
+| Goal |	Measurement of success | Dependency | ETA | Status
+| ----- | ----- | ----- | ----- | ----- |
+| Mentor {T76199} successfully | New extension deployed in Labs and ready to start Wikimedia's review process | @Tinaj1234 @01tonythomas | #ECT-September-2015 | In progress |
+",1435678504,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@MGChecker, Thanks for pointing it out. Fixed it.",1435093814,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"If I open Special:Preferences in your devwiki, I get
+
+
+```
+[25a347c3] /wiki/Special:Preferences MWException from line 182 of /srv/vagrant/mediawiki/includes/Hooks.php: Invalid callback NewsletterHooks::onGetPreferences in hooks for GetPreferences
+
+Backtrace:
+
+#0 /srv/vagrant/mediawiki/includes/Preferences.php(99): Hooks::run(string, array)
+#1 /srv/vagrant/mediawiki/includes/Preferences.php(1260): Preferences::getPreferences(User, RequestContext)
+#2 /srv/vagrant/mediawiki/includes/specials/SpecialPreferences.php(60): Preferences::getFormObject(User, RequestContext)
+#3 /srv/vagrant/mediawiki/includes/specialpage/SpecialPage.php(384): SpecialPreferences->execute(NULL)
+#4 /srv/vagrant/mediawiki/includes/specialpage/SpecialPageFactory.php(581): SpecialPage->run(NULL)
+#5 /srv/vagrant/mediawiki/includes/MediaWiki.php(285): SpecialPageFactory::executePath(Title, RequestContext)
+#6 /srv/vagrant/mediawiki/includes/MediaWiki.php(634): MediaWiki->performRequest()
+#7 /srv/vagrant/mediawiki/includes/MediaWiki.php(431): MediaWiki->main()
+#8 /srv/vagrant/mediawiki/index.php(41): MediaWiki->run()
+#9 /var/www/w/index.php(5): include(string)
+#10 {main}
+
+```
+
+I think this schould be fixed.
+",1435085653,PHID-USER-4z6eerx3m7iocsrcpku5,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Currently, we are implementing T99784 with two of them merged already, T101505 and T100125. When it comes to communication, if you look at the description you'll see that we have weekly meetings every Thursday and also like Quim said there was a task open for Stakeholder Outreach. You might get a better idea of what is going on if you look at the [[ https://phabricator.wikimedia.org/T100997 | weekly reports task ]] and [[ https://phabricator.wikimedia.org/tag/mediawiki-extensions-newsletter/ | corresponding tasks ]] created for each feature maybe.",1434926239,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Thanks for the clarifications.
+
+Is this task's description supposed to be an accurate reflection of the current development and implementation plan? I was responding directly to screenshots such as M12 that are included in this task's description. In addition to a mock-up, there are also comments such as ""Adding Newsletter tab to Special:Preferences"" in the timeline... this seems pretty confusing to me.
+
+I can appreciate wanting to break down a large task into smaller tasks, but fracturing discussion among dozens of tasks has very real communications costs. There should be a centralized place to discuss this proposal and review its current implementation plan. I thought that place was this task, but perhaps I'm mistaken?",1434918146,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@MZMcBride, this proposal has gone through a review process as part of #Google-Summer-of-Code-2015 and now we are in full development mode. Let's  help @Tinaj1234 (our GSoC student for this project) focus on the existing plan, which right now welcomes implementable feedback and suggestions for improvement. The result of this work should be a functional extension running in a Labs instance by the end of September (latest). From there we will discuss whether this makes sense for Wikimedia and, if so, what is missing for deployment.
+
+>>! In T76199#1386184, @MZMcBride wrote:
+> Parts of this proposal feel like natural complements to the existing work that's already been done in MassMessage.
+
+Just for the background: in T59935 we decided to detach newsletter types of features from MassMessage. Legoktm has been following this project and I think both extensions will be good neighbors accomplishing complementary but not equivalent objectives.
+
+> Are users really interested in the flexibility of receiving the Military history newsletter via e-mail, but the Signpost via talk page message (which would trigger an e-mail for most users anyway...)? Are per-newsletter delivery preferences something we actually want or need?
+
+We are not planning per-newsletter delivery preferences, see {T100492} and comment there if you have feedback.
+ 
+> As always, I'm wary of yet another preferences tab, especially sitting next to an existing ""Notifications"" tab.
+
+There is no new preferences tab, just a new entry for Newsletters in the Notifications tab, as this will be integrated with Echo. If you want to discuss further, see {T101546}.
+
+ 
+> I'm not yet convinced of the need for a separate MediaWiki extension here. Publishing content is what the core wiki software should be good at already. I don't see the great value in a specialized layer for creating newsletters specifically.
+
+For what is worth, we made a {T100604} and authors of actual newsletters think this project is useful for their needs. This extension doesn't deal with publishing content per se, as this is done through regular wiki pages. What this extension aims to solve are problems that our current software doesn't solve well: possibility to subscribe/unsubscribe easily to newsletters (without relying on watchlists) and possibility to announce new issues of newsletters via email or web notification (without relying on Talk pages). While advanced users of watchlist and talk pages might see little difference / value, we expect this extension to help newsletter authors to get a lot more subscribers (even among new users feeling more comfortable about subscribing to a newsletter than about start editing on a regular basis) and a lot more actual readers not missing their issues as easily as they might miss changes in their watchlists.
+
+I hope this reply is good enough to see the point of this GSoC project. Your attention to detail is welcome in the ongoing tasks or in new tasks that you are encouraged to create.",1434917690,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@MZMcBride, this proposal has gone through a review process as part of #Google-Summer-of-Code-2015 and now we are in full development mode. Let's  help @Tinaj1234 (our GSoC student for this project) focus on the existing plan, which right now welcomes implementable feedback and suggestions for improvement. The result of this work should be a functional extension running in a Labs instance by the end of September (latest). From there we will discuss whether this makes sense for Wikimedia and, if so, what is missing for deployment.
+
+>>! In T76199#1386184, @MZMcBride wrote:
+> Parts of this proposal feel like natural complements to the existing work that's already been done in MassMessage.
+
+Just for the background: in T59935 we decided to detach newsletter types of features from MassMessage. Legoktm has been following this project and I think both extensions will be good neighbors accomplishing complementary but not equivalent objectives.
+
+> Are users really interested in the flexibility of receiving the Military history newsletter via e-mail, but the Signpost via talk page message (which would trigger an e-mail for most users anyway...)? Are per-newsletter delivery preferences something we actually want or need?
+
+We are not planning to per-newsletter delivery preferences, see {T100492} and comment there if you have feedback.
+ 
+> As always, I'm wary of yet another preferences tab, especially sitting next to an existing ""Notifications"" tab.
+
+There is no new preferences tab, just a new entry for Newsletters in the Notifications tab, as this will be integrated with Echo. If you want to discuss further, see {T101546}.
+
+ 
+> I'm not yet convinced of the need for a separate MediaWiki extension here. Publishing content is what the core wiki software should be good at already. I don't see the great value in a specialized layer for creating newsletters specifically.
+
+For what is worth, we made a {T100604} and authors of actual newsletters think this project is useful for their needs. This extension doesn't deal with publishing content per se, as this is done through regular wiki pages. What this extension aims to solve are problems that our current software doesn't solve well: possibility to subscribe/unsubscribe easily to newsletters (without relying on watchlists) and possibility to announce new issues of newsletters via email or web notification (without relying on Talk pages). While advanced users of watchlist and talk pages might see little difference / value, we expect this extension to help newsletter authors to get a lot more subscribers (even among new users feeling more comfortable about subscribing to a newsletter than about start editing on a regular basis) and a lot more actual readers not missing their issues as easily as they might miss changes in their watchlists.
+
+I hope this reply is good enough to see the point of this GSoC project. Your attention to detail is welcome in the ongoing tasks or in new tasks that you are encouraged to create.",1434917656,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@MZMcBride, this proposal has gone through a review process as part of #Google-Summer-of-Code-2015 and now we are in full development mode. Let's  help @Tinaj1234 (our GSoC student for this project) focus on the existing plan, which right now welcomes implementable feedback and suggestions for improvement. The result of this work should be a functional extension running in a Labs instance why the end of September (latest). From there we will discuss whether this makes sense for Wikimedia and, if so, what is missing for a deployment.
+
+>>! In T76199#1386184, @MZMcBride wrote:
+> Parts of this proposal feel like natural complements to the existing work that's already been done in MassMessage.
+
+Just for the background: in T59935 we decided to detach newsletter types of features from MassMessage. Legoktm has been following this project and I think both extensions will be good neighbors accomplishing complementary but not equivalent objectives.
+
+> Are users really interested in the flexibility of receiving the Military history newsletter via e-mail, but the Signpost via talk page message (which would trigger an e-mail for most users anyway...)? Are per-newsletter delivery preferences something we actually want or need?
+
+We are not planning to per-newsletter delivery preferences, see {T100492} and comment there if you have feedback.
+ 
+> As always, I'm wary of yet another preferences tab, especially sitting next to an existing ""Notifications"" tab.
+
+There is no new preferences tab, just a new entry for Newsletters in the Notifications tab, as this will be integrated with Echo. If you want to discuss further, see {T101546}.
+
+ 
+> I'm not yet convinced of the need for a separate MediaWiki extension here. Publishing content is what the core wiki software should be good at already. I don't see the great value in a specialized layer for creating newsletters specifically.
+
+For what is worth, we made a {T100604} and authors of actual newsletters think this project is useful for their needs. This extension doesn't deal with publishing content per se, as this is done through regular wiki pages. What this extension aims to solve are problems that our current software doesn't solve well: possibility to subscribe/unsubscribe easily to newsletters (without relying on watchlists) and possibility to announce new issues of newsletters via email or web notification (without relying on Talk pages). While advanced users of watchlist and talk pages might see little difference / value, we expect this extension to help newsletter authors to get a lot more subscribers (even among new users feeling more comfortable about subscribing to a newsletter than about start editing on a regular basis) and a lot more actual readers not missing their issues as easily as they might miss changes in their watchlists.
+
+I hope this reply is good enough to see the point of this GSoC project. Your attention to detail is welcome in the ongoing tasks or in new tasks that you are encouraged to create.",1434917496,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Please see that we are not going to affect Special:Preferences - and - what we have would be a Special:Newsletter which would list down the available newsletters for the wiki, and the user can click on each - read its shorty bio and see some stats - and click on Subscribe button to subscribe. Populating the overpopulated Special:Preference more is definitely a bad idea. 
+
+The extension is designed in such a way that existing Newsletters can be easily added to the extension to increase manageability. The Newsletter admins would be given something like http://newsletter-test.wmflabs.org/wiki/Special:NewsletterCreate ( log-in required ) which would allow addition of existing Newsletters - which are wiki pages. Maybe in the later steps, we would have a feature to readily create a newsletter with pre-defined templates right from the Special:NewsletterCreate
+
+",1434916067,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"On-wiki newsletters are an interesting idea, though I wonder if we're not just painfully duplicating the features of a mailing list.
+
+Parts of this proposal feel like natural complements to the existing work that's already been done in MassMessage. For example, ContentHandler-backed MassMessage subscription lists should be trivially query-able to retrieve and expose numbers of subscribers.
+
+Adding on-wiki notification (Echo) support to MassMessage might be nice and would begin to expose a need for some kind of extension to manage a user's contact preference, perhaps. However, I'm not sure many users want to get that granular. Are users really interested in the flexibility of receiving the Military history newsletter via e-mail, but the Signpost via talk page message (which would trigger an e-mail for most users anyway...)? Are per-newsletter delivery preferences something we actually want or need?
+
+As always, I'm wary of yet another preferences tab, especially sitting next to an existing ""Notifications"" tab.
+
+I'm not yet convinced of the need for a separate MediaWiki extension here. Publishing content is what the core wiki software should be good at already. I don't see the great value in a specialized layer for creating newsletters specifically.",1434915380,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Works for me too! See you guys tomorrow at 15:00 IST,1433431873,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"[[ http://www.timeanddate.com/worldclock/meetingdetails.html?year=2015&month=6&day=5&hour=9&min=30&sec=0&p1=311&p2=771 | This time ]] works for me, yes.",1433424615,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Qgil, @Tinaj1234 : How about we having a meeting, tomorrow ( 5 June 2015 ) at 3-4 pm IST ?",1433423347,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"How about we having a meeting, tomorrow ( 5 June 2015 ) at 3-4 pm IST ?",1433423328,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1315875, @Qgil wrote:
+> 
+> @Tinaj1234, I think this is a good idea. Could you create a task for this?
+
+T100604 created for further discussions.",1432785980,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1314246, @Tbayer wrote:
+> Is it planned to do some kind of stakeholder outreach to the people who will be using this new software, in particular publishers of existing newsletters?
+
+@Tinaj1234, I think this is a good idea. Could you create a task for this? There @tbayer and @quiddity will tell us the best to reach to the publishers of newsletters.  ;)  (MassMessage against... a list of Newsletters somewhere? Please discuss in the new task, so we keep this one relatively quiet.)",1432764107,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1314246, @Tbayer wrote:
+> Is it planned to do some kind of stakeholder outreach to the people who will be using this new software, in particular publishers of existing newsletters? (I understand ""community bonding"" refers to something different.) It would seem prudent to get their feedback on the planned features, to make sure they will actually get used.
+
+Oops! Sorry for the confusion, but this project is scheduled to be done as part of the Google Summer of Code 2015 program, and @Tinaj1234 is the student assigned with 'us' mentoring. 'Community Bonding' is the phase 1 of the project workflow when the candidate gets to know the community and the project. We are preparing the bare minimum product for a start before the mid term ( https://developers.google.com/open-source/soc/ ) and you we welcome existing stakeholders like you to start creating 'sub tasks' to this phab task so that we make sure its delivered before hitting production. 
+
+",1432731110,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Very exciting to see work progressing in this area! (Speaking as someone who has been regularly sending out newsletters since 2010, and author of one of the pages that Nick linked.)
+
+Is it planned to do some kind of stakeholder outreach to the people who will be using this new software, in particular publishers of existing newsletters? (I understand ""community bonding"" refers to something different.) It would seem prudent to get their feedback on the planned features, to make sure they will actually get used.",1432728023,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Just FYI, here's my bookmark folder for ""Newsletters"", which has many useful parts, many outdated pages, and much potential for distraction. ;-)
+
+* https://meta.wikimedia.org/wiki/Newsletters
+* https://meta.wikimedia.org/wiki/Internal_news_media
+* https://en.wikipedia.org/wiki/Wikipedia:News
+* https://de.wikipedia.org/wiki/Wikipedia:Nachrichten
+* https://www.mediawiki.org/wiki/Communication
+* https://www.mediawiki.org/wiki/Extension_talk:Newsletter and https://www.mediawiki.org/wiki/Extension:Newsletter
+* https://www.mediawiki.org/wiki/Movement_broadcasting",1432038992,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Discussions #2  ( 19/05/2015 ) paste: 
+https://phabricator.wikimedia.org/P653
+",1432031867,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Qgil: Since we wont be able to do much of code work, since a student is assigned for the same, I think we are looking for something in the 'Meeting' category where we can list out what we are planning to do with the NewsLetter. We should be looking at: 
+
+
+  # How the SpecialPage(s) should look like, what all functions should be made public
+  # Who should be given the right to create/edit NewsLetters 
+  # More design inputs for the NewsLetter SpecialPage 
+  # Showcase our current idea of creating/storing a NewsLetter - and get more inputs about its feasibility
+  # Possibility of handling subscription from the Special:Preferences 
+
+I think we will have to prepare few mockups ( I can take care of that ) !
+
+",1431949127,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"It is time to promote #Wikimedia-Hackathon-2015 activities in the [[ https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015/Program | program ]] (training sessions and meetings) and [[ https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015#Activities_confirmed | main wiki page ]] (hacking projects and other ongoing activities). [[ https://phabricator.wikimedia.org/T97121 | Follow the instructions ]], please. If you have questions, about this message, ask [[ https://phabricator.wikimedia.org/T97121  | here ]].",1431947539,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Log of IRC meeting on #wikimedia-newsletter - P627.,1431102000,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Created web proxy for the Labs instance and can now be accessed using: http://newsletter-test.wmflabs.org/ !,1430765379,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I associated this task to #Wikimedia-Hackathon-2015 when I was trying to get development hours for it from anywhere possible.  :)  Are we going to have any specific activity there, though? If so, please create a specific task for this activity.
+
+In general, we need to keep this task as silent as possible, blocking it by the main tasks of this project (that will have their own subtasks).",1430391456,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas, @Qgil - Thanks a lot for the opportunity. Created subtask, T97413 to start off with the community bonding period. Looking forward to working with everyone involved !",1430229839,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1241220, @Qgil wrote:
+> Alright, let's start with the [[ https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#Community_bonding_period | community bonding period ]]. Please create a subtask as described in T94166, and let's discuss there the tasks related with this phase (i.e. starting our routine of weekly meetings). 
+> 
+> @01tonythomas, thank you for your efforts providing microtasks and support to all candidates. Let's leave no excuse to Tina to deliver this extension.  ;) 
+@qgil True! Cant wait to start this one :) Congrats @Tinaj1234!
+Thanks to everyone who came forward with their proposals! 
+
+",1430228651,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Congratulations @Tinaj1234 and welcome to #Google-Summer-of-Code-2015 with {T93583}! I'm looking forward to working with you on a first release of the Newsletter extension.
+
+Alright, let's start with the [[ https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#Community_bonding_period | community bonding period ]]. Please create a subtask as described in T94166, and let's discuss there the tasks related with this phase (i.e. starting our routine of weekly meetings). 
+
+@01tonythomas, thank you for your efforts providing microtasks and support to all candidates. Let's leave no excuse to Tina to deliver this extension.  ;) 
+
+Anybody interested in seeing this extension deployed one day in Wikimedia, please step in and get involved.",1430217577,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"goodreads.com is my current ideal model - just look at this delicious malleability!   (I know developers are very wary of adding preferences (because extra complexity, and testing, and maintenance) but users tend to love them, especially the broad diversity of powerusers in highly-complex projects. ;-)
+{F109890}",1428461024,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Please see the updated comment ! ,1427965454,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,ohh yeaah :),1427956944,PHID-USER-sututmegiourdiellndf,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"There was an extra ""]"" at the end of the link:
+https://github.com/wikimedia/mediawiki-extensions-BounceHandler/blob/master/includes/ProcessUnRecognizedBounces.php",1427919275,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Github link is non existent.,1427918734,PHID-USER-sututmegiourdiellndf,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This task to add an echo notification came directly to the BounceHandler project - T94436 - and would be a relevant micro-task to the project as you need to be doing that to notify the subscribers.
+Hints: 
+* You have the failing recipient ( to be notified ) user object in here [ https://github.com/wikimedia/mediawiki-extensions-BounceHandler/blob/master/includes/BounceHandlerActions.php#L93 ]
+* Follow http://www.mediawiki.org/wiki/Echo_(Notifications)/Developer_guide to see how you can integrate Echo notifications to an extension!
+* You can see how Extension:Thanks hook into 'Echo' notifications in line 33 - 37 here ( https://etherpad.wikimedia.org/p/newsletterExtension )",1427965416,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This task to add an echo notification came directly to the BounceHandler project - T94436 - and would be a relevant micro-task to the project as you need to be doing that to notify the subscribers.
+Hints: 
+* You have the failing recipient ( to be notified ) email id passed as $email in processUnRecognizedBounces( ) [https://github.com/wikimedia/mediawiki-extensions-BounceHandler/blob/master/includes/ProcessUnRecognizedBounces.php]
+* Follow http://www.mediawiki.org/wiki/Echo_(Notifications)/Developer_guide to see how you can integrate Echo notifications to an extension!
+* You can see how Extension:Thanks hook into 'Echo' notifications in line 33 - 37 here ( https://etherpad.wikimedia.org/p/newsletterExtension )",1427881434,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This task to add an echo notification came directly to the BounceHandler project - T94436 - and would be a relevant micro-task to the project as you need to be doing that to notify the subscribers.
+Hints: 
+* You have the failing recipient ( to be notified ) email id passed as $email in processUnRecognizedBounces( ) [https://github.com/wikimedia/mediawiki-extensions-BounceHandler/blob/master/includes/ProcessUnRecognizedBounces.php]
+* You can see how Extension:Thanks hook into 'Echo' notifications in line 33 - 37 here ( https://etherpad.wikimedia.org/p/newsletterExtension )",1427820609,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"More microtasks, if you're still looking for it: T55564 ! and you can find few over here too : T67673#1074667
+
+Basically, search in here for more : https://phabricator.wikimedia.org/maniphest/query/Wi.yo3mXEjwF/",1427484627,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"More microtasks, if you're still looking for it: T55564 ! and you can find few over here too : T67673#1074667",1427484517,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"More microtasks for grabs :  T59414 
+( Will add more soon )! 
+
+
+",1427376286,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1145330, @koustuvcse wrote:
+> okay... I will look into it.. but what is the GMT of the irc?
+
+err. Its just normal humans ( is it? :P ) and bots hanging around in a public chat-place. So,  normal GMT = IRC GMT :). Please click on the date-time link in https://phabricator.wikimedia.org/T76199#1138098 to get exact conversions and maybe, Google a little :) ",1427213688,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,okay... I will look into it.. but what is the GMT of the irc?,1427213339,PHID-USER-muobtocub3solbj4sz5f,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1145323, @koustuvcse wrote:
+> I am new to the irc ecosystem. can you please guide me through it? please
+
+You can find loads of (Mediawiki+IRC) relevant links over here : https://www.mediawiki.org/wiki/MediaWiki_on_IRC ",1427213247,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I am new to the irc ecosystem. can you please guide me through it? please,1427213132,PHID-USER-muobtocub3solbj4sz5f,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Hello! The IRC meeting tomorrow has been shifted to #wikimedia-ect channel. Looking forward to seeing you there. :),1427213058,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"We're holding an IRC meeting on [March 25, at 1700 UTC](http://www.timeanddate.com/worldclock/fixedtime.html?msg=MediaWiki+GSoC%2FOutreachy+IRC+party&iso=20150325T17&p1=%3A&ah=1) for prospective GSoC and Outreachy participants with Wikimedia, on #wikimedia-office channel. Do join us! ",1426943754,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@resheila A project being selected for GSoC or not is decided by the quality of proposals received. If we get a good proposal for the same, we'll keep this project for the upcoming GSoC round, else not. ",1426620405,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Yes, it is. https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015#MediaWiki_extensions",1426620361,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Is this project for sure there in Gsoc?,1426619536,PHID-USER-sututmegiourdiellndf,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"If someone is still in search of microtasks : T72784 
+
+If you think you're enough cool with the codebase and extensions, please follow the link in Quims comment above, and start preparing your proposal. ",1426612367,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Hi @ResheilA thank you for your interest in this project idea. See https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015#Add_your_proposal,1426593919,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hey,
+This project seems interesting, I would like to work on it. And I can make it more efficient and look good. Can any one tell me how to add it for summer of code?  ",1426593626,PHID-USER-sututmegiourdiellndf,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hi @koustuvcse, thank you for your interest in contributing to Wikimedia. Please read the conversation and try to solve one of the microtasks suggested in the task description. If you have questions, just ask.",1426541879,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,this project is cool.. i am from gsoc and i want to work for this project.. the requirements for this project matches my skill set... ,1426536779,PHID-USER-muobtocub3solbj4sz5f,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Ricordisamoa, could be... although the current Newsletters proposal already relies on leveraging existing features. If I understand you correctly, your proposal is based on apparently significant modifications to Flow and the implementation of 'tags', a new type of content in Flow. This might be more work than offering plain wiki pages for newletters, Flow for their discussion pages, Echo for notifications and relatively straightforward special pages for managing subscriptions, and the catalog of newsletters. 
+
+I mean, wiki pages are good for publishing articles, and newsletters are articles. Flow is good for discussion, and ""instantly-locked threads with certain tags through which users would subscribe"" sounds more of a stretch. Besides, wiki pages are a solid and stable basis, with VisualEditor and full-fledged wikitext, while Flow is probably too young to be used as a platform. For a GSoC 2015 project, I think the current proposal is sensible.",1426511488,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Ricordisamoa, could be... although the current Newsletters proposal already relies on leveraging existing features. If I understand you correctly, your proposal is based on apparently significant modifications to Flow and the implementation of 'tags'. This might be more work than offering plain wiki pages for newletters, Flow for their discussion pages, Echo for notifications and relatively straightforward special pages for managing subscriptions and the catalog of newsletters. 
+
+I mean, wiki pages are good for publishing articles, and newsletters are articles. Flow is good for discussion, and ""instantly-locked threads with certain tags through which users would subscribe"" sounds more of a stretch. Besides, wiki pages are a solid and stable basis, with VisualEditor and full-fledged wikitext, while Flow is probably too young to be used as a platform. For a GSoC 2015 project, I think the current proposal is sensible.",1426511390,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I find this a bit redundant to Flow, where newsletters could be cross-wiki instantly-locked threads with certain <spam>[[ //www.mediawiki.org/wiki/User:Ricordisamoa/Flow | tags ]]</spam> through which users would subscribe, leveraging the existing integration with watchlist & Echo.
+Just my 2 cents.",1426507049,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Looks like you've finished most of the microtasks listed in the description. You can leave the echo notif as of now ( as people say : 10:32 PM <legoktm> Echo isn't really easy to work with :/ ) :D. To help you gain expertise more with the code base, consider these easy tasks: T4335, T92728, ",1426485759,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1109430, @01tonythomas wrote:
+> * Design : 
+> https://phabricator.wikimedia.org/T62725 
+> https://phabricator.wikimedia.org/T62725
+-- since it belongs to UI standardization, you can always see how it's one over here ( https://phabricator.wikimedia.org/project/sprint/board/24/query/Z6mtlWoK9aIj/) - or check this one - https://gerrit.wikimedia.org/r/#/c/192282/
+",1426146769,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1109612, @Tinaj1234 wrote:
+> Yes, that's pretty much all about me. Thanks, @Qgil !
+> 
+> Starting with the microtasks. Is there something like claiming the tasks? Do I have to comment under the bug ? Or just start right away with the bug ? 
+
+I think you can just start working on the same, and submit the patch with the correct Bug: <id> in the commit message. www.mediawiki.org/wiki/Gerrit/Tutorial would help you prepare the patch to gerrit",1426087706,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Yes, that's pretty much all about me. Thanks, @Qgil !
+
+Starting with the microtasks. Is there something like claiming the tasks? Do I have to comment under the bug ? Or just start right away with the bug ? ",1426087337,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"See https://www.mediawiki.org/wiki/User:Tinaj1234/MassMessage . She applied but at the end the project was for wctaiwan (who finished the project and has continued contributing until today). With this I mean that @Tinaj1234 is in a good starting point, with good experience and clear perseverance. 
+
+Anyway, let's go back to Extension:Newsletter. Sorry for the interlude.",1426084828,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"See https://www.mediawiki.org/wiki/User:Tinaj1234/MassMessage . She applied but at the end the project was for wctaiwan (who finished the project and has continued contributing until today). With this I mean that @Tinaj1234 is in a good starting point, with good experience and clear perseverance. 
+
+Anyway, let's go back to Extenmsion:Newsletter. Sorry for the interlude.",1426084818,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,See https://www.mediawiki.org/wiki/User:Tinaj1234/MassMessage,1426084534,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I was wondering if @Tinaj1234 was a previous GSoC/OPW intern with us. I didn't find an entry on GSoC Past projects pages though.,1426084198,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hi @Tinaj1234, thank you for your interest in this project. Wow, looking at tasks and commits related to your profile one can clearly see that you are not new here. Very interesting.",1426083980,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas, add it to the task description. :) ",1426083549,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"That looks great. Adding few microtasks. I think most of the work would go similar to the Echo/MassMessage extensions + some SpcialPage works, so hacking on them would get you familiar with the same: 
+https://phabricator.wikimedia.org/T56533 - from echo - this would help you understand the procedure of adding a new notification. 
+* Design : 
+https://phabricator.wikimedia.org/T62725 
+https://phabricator.wikimedia.org/T62725
+* Special Pages hacks: 
+https://phabricator.wikimedia.org/maniphest/query/VXEJAQ_oaxCM/#R
+
+Good luck :) ",1426083443,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I'm very much interested in working on this project. I believe I'm equipped with most of the skills required for the projects. Looking forward to the microtasks !,1426082324,PHID-USER-3pzrnfkwxgwn4v6askvo,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Awesome @01tonythomas! :) 
+
+You and @qgil can hack on it together in the Lyon Hackathon to iron out the details (unless either/both of you have made commitments otherwise :). ",1425994097,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,">>! In T76199#1104168, @Qgil wrote:
+> @01tonythomas, the structure of a newsletter is basically an index of issues, yes, but the design could glorify a bit each issue: the most recent one could be featured at the top and the other ones could be in a list, more compact, but still making room to i.e. a thumbnail if the newsletter contains an image.
+Yeah. the design can come later through the project though. It would be great if we can complete the desired functions in the 2 month period, and polish the design later. 
+> ... Anyway, these are details. I'd rather focus now in finding a main mentor and filling the template in the description.  :)
+Something this cool should not be stalled due to a mentor not turning up, and I am positive to play the mentor role, expecting @legoktm, @parent5446, @Qgil and other devs support ( just like we completed bouncehandler :) )",1425993894,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@01tonythomas, the structure of a newsletter is basically an index of issues, yes, but the design could glorify a bit each issue: the most recent one could be featured at the top and the other ones could be in a list, more compact, but still making room to i.e. a thumbnail if the newsletter contains an image.
+
+... Anyway, these are details. I'd rather focus now in finding a main mentor and filling the template in the description.  :)",1425991356,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Dissecting it for fun :  
+>>! In T76199, @Qgil wrote:
+> Publisher: 
+>A process defining the conditions in which a newsletter can be created, featured, demoted, closed (actions that might imply database changes). Just a basic framework to promote best practices and prevent abuse.
+So that would mean a Special:NewsLetter page, that would be something similar to the LiquidThreads template ( https://www.mediawiki.org/wiki/Extension_talk:LiquidThreads ), and the publisher can ""Create a new Newsletter"" over there, give the subject, and body of his newsletter.
+Below that, the user can see the NewsLetters ( subjects ) he has created followed by the ones he is currently subscribed to. 
+When the publisher clicks on one of the Newsletter he had created, we should have editing options coming up below the suject with JS, I think. The options over there should be simialr to ""New page"", ""View pages"", ""Trash  Newsletter"", ""Stop publishing"" etc.
+
+@qgil: above looks similar to something you expected ?
+",1425920054,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Yes, let's try GSoC/Outreachy first.
+
+I have edited the description adding the template for GSoC / Outreachy. Your help filling skills and microtasks is welcome.
+
+Then we need a technical mentor. As a co-mentor, I can contribute the product and community perspective, but we need a developer as main mentor. ",1425547238,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Pine, it'd take one technical mentor devoting a little of his time for three months to a student. :) ",1425546988,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"What would it take to bump up the priority of this project? This is a high impact project for community communications and wikiprojects, and it's a pity to let this sit here waiting for resources. I'm not sure how many other projects could be considered higher priorities from the consumer and community standpoints.",1425544940,PHID-USER-l7v72q5tq6vg6zclrld6,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@ImPacific, Hello! This project is still under discussion. Although I believe the required skills would be PHP, JavaScript, HTML, CSS. 
+",1425376567,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Hi all,
+I find this newsletter extension interesting. I would like to take it up as GSOC project and would like to know what skills would be required to accomplish the required tasks. If required skills are mentioned it would be easier to know whether I meet the minimum skill requirement or not.
+Thanks.",1425375186,PHID-USER-zlgwinzlyyz4gescprcx,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"My only motivation for the centralization is the need to offer a catalog with all the newsletters available in a wiki farm, and the possibility to subscribe/unsubscribe and receive notifications without having to visit or be an active editor of any wiki. If we solve these use cases, then I agree that each wiki community should be able to manage their own newsletters. Anyway, the first prototype will be most likely a single Labs instance, so this is not the most urgent aspect we need to solve.
+
+About notifications, I think we should focus first on strict notifications, a short message telling you that a new issue can be found at URL. Email notifications are a must (directly or via Echo, I don't know) because this is the simplest process that new users and many others will prefer. Web notifications as a logged in Wikimedia user are also good, but make sense only when email is resolved. 
+
+I'm not convinced at all with ""deliveries"", as in the full content of an issue pasted in Talk pages etc. If you are on web, then it is better to go to the canonical source and eventually read / join the discussion in its canonical place. Email deliveries make sense, though, as many people will prefer to read the content at the moment, even if they are offline.",1425036986,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I'm interested in how this will interact with existing notification systems like MassMessage, Echo, and TranslationNotifications. 
+
+MassMessage has a not-yet-super-advertised feature which makes signing up for deliveries significantly easier: <https://test.wikipedia.org/wiki/Yay_mm-ch!>. Creating a central listing of these pages and allowing creation of MediaWiki messages to add descriptions would come close to what is being proposed in M12 I think.",1424984155,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"@Se4598: If we're accommodating something like the Signpost, then I'd imagine that we'd definitely have to support local distributions. I think the MassMessage approach is a good one, i.e., having centralized but also allowing locally managed mass messaging.",1424983810,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I don't like the idea of centralizing newsletter definition. I'm also for centralizing specific newsletters but let communities handle their own (custom to the wiki) newsletters themself, like it's possible to use MassMessage on any wiki, managed by local admins/senders, but also send messages from Meta to all wikis.
+to clarify: My main point here is not the central place, but who will have which rights and how that integrates with local community wishes.
+
+Also a extension probably worth a look at the features is [[https://www.mediawiki.org/wiki/Extension:TranslationNotifications|Extension:TranslationNotifications]], where you can choose where to recieve the notifications (email, local or a remote wiki).",1424971498,PHID-USER-jcypqodpdpbcicgwgh7j,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Good questions, @Parent5446! I have started drafting a more precise plan in the task description, addressing your points and other elemental factors. Feel free to fine tune the plan with questions and edits. ",1424970520,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"This definitely seems like a cool idea, and somewhat of an extension of Extension:MassMessage. The only thing to think about is what the interface for authors and administrators would be. Specifically:
+
+  - How do admins define what newsletters are available to users?
+  - Where do authors put drafts, and can other people edit them?
+  - How do authors publish a draft? How do admins define who can publish?
+  - Can authors set a draft to auto-publish at a specific time?
+
+Assuming we attempt to not disturb current workflows, then we'd probably opt for having newsletters on normal wikipages, and rely on page protection (if necessary) to prevent unauthorized editing. Admins would change an interface message containing all the newsletters and the wikipage they are published on. And finally, we have a special page to pull it all together that allows authors to specify when an edition is published.",1424965950,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"https://meta.wikimedia.org/wiki/Grants:IdeaLab/Newsletter_extension_for_MediaWiki
+
+All fronts covered!",1424951395,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,Call for a GSoC / Outreachy co-mentor or a hackathon buddy sent to wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2015-February/081022.html,1424949582,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I have marked {T30085} if only to think about this scenario:
+
+# Anonymous user finds an interesting Wikimedia newsletter.
+# Anonymous only needs to submit an email address to subscribe and receive notifications.
+# Eventually, anonymous can complete their Wikimedia username registration.
+
+This is a model that in my opinion works well in many contemporary newsletters from interesting services: the first time they only require an email address (which is a sensible requirement), and once you are in the hook, slowly slowly you feel like more encouraged to be more involved, create your user profile etc.",1424854487,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I have marked {T30085} if only to think about this scenario:
+
+# Anonymous user finds an interesting Wikimedia newsletter.
+# Anonymous only needs to introduce an email address to subscribe and receive notifications.
+# Eventually, anonymous can complete their Wikimedia username registration.
+
+This is a model that in my opinion works well in many contemporary newsletters from interesting services: the first time they only require an email address (which is a sensible requirement), and once you are in the hook, slowly slowly you feel like more encouraged to be more involved, create your user profile etc.",1424854116,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"I'm willing to co-mentor this project, which I consider very much needed in Wikimedia and MediaWiki in general. But I need a technical mentor.
+
+If we miss this GSoC/Outreachy round, another possibility is to propose an activity for the Wikimedia Hackathon in Lyon, although in that case I will also need a technical mentor of sorts.
+
+Sigh.",1424694142,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Wikimedia will [[ https://phabricator.wikimedia.org/T921 | apply to Google Summer of Code and Outreachy ]] on Tuesday, February 17. If you want this task to become a featured project idea, please follow [[ https://phabricator.wikimedia.org/project/view/1042/ | these instructions ]]. ",1423662274,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I guess any pixel helps.  :),1417721793,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"Alright, but it already has&had a project in BZ/Phab so wondering whether to associate that here. :)",1417701293,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,"https://www.mediawiki.org/wiki/Extension:Newsletter is not a real project, just one of my attempts (with @siebrand) to kick this feature in a productive direction.",1417694390,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Goal: Newsletter extension for MediaWiki,I assume this is about resource allocation? Or does this also refer to technically enhancing functionality in https://www.mediawiki.org/wiki/Extension:Newsletter (so that project should be associated to this task)?,1417623925,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2c6nxv3lw3wwpzottiyw,task_subcomment,NA
+Create Spelling-Dictionary project,"**Name:** Spelling-Dictionary
+
+**Type of Project:** Project, #spelldict
+
+**Policy:** Visible To Public 
+
+**Description:** Spelling dictionaries for the major languages of the world (English, Italian, French) help make Wikipedia articles in these languages more readable and professional and provide an opportunity for participation in improving spelling. Many languages, however, don’t have spelling dictionaries.
+
+This project aims at developing a collaborative dictionary which shall also have an additional feature of checking spellings of the words. This is to be achieved with the collaborative efforts of the mediawiki community using crowd-sourcing, as a MediaWiki extension integrated with VisualEditor, and possibly using Wikidata as a backend. We need to create something that's useful as VE module.
+
+The essence of the project shall aim to develop an admin panel where the administrator/moderator will be able to manage the submissions: verify the suggested spellings of the words, accept them, reject them, filter and build new versions of the spelling dictionary upon them. A simple start to the project could be by starting with a simple list of words.
+
+The detailed time line can be read [[ http://www.mediawiki.org/wiki/User:Ankitashukla/Proposal | here ]]",1417122558,PHID-USER-vktcpyhhgydpo36f44uz,False,PHID-TASK-6gmrv6d3roeydcelmnyh,task_description,resolved
+Create Spelling-Dictionary project,Please also add yourself to the project members to receive updates. See https://www.mediawiki.org/wiki/Phabricator/Help#Receiving_updates_and_notifications for more information.,1417619687,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Create Spelling-Dictionary project,"#spelldict created. If for some reason you want to rename it, please check https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Renaming_projects
+
+Enjoy!",1417602843,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Create Spelling-Dictionary project,I'm OK with this name.,1417592846,PHID-USER-abr5ge6gl2ovg7jokpst,False,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Create Spelling-Dictionary project,">>! In T76160#792226, @Qgil wrote:
+> @amire80, @kartikmistry, are you ok with this name of project? CCing @Jdforrester-WMF as well, since this is a project related to VisualEditor.
+
+Ping? I want to create this project today, if possible.",1417592611,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Create Spelling-Dictionary project,"@amire80, @kartikmistry, are you ok with this name of project? CCing @Jdforrester-WMF as well, since this is a project related to VisualEditor.",1417123002,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-6gmrv6d3roeydcelmnyh,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,The job: [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/ | browsertests-VisualEditor-language-screenshot-windows_8.1-firefox ]],1417084690,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-sgoczofqmqi4d2v3nizb,task_description,resolved
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,That job has been deleted by https://gerrit.wikimedia.org/r/#/c/183480/ which replaced it with a mac os version.,1421169278,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"Most of the jobs is green, but a few failed.
+
+https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/",1417877349,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"The job is green now.
+
+https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/LANGUAGE_SCREENSHOT_CODE=ar,label=contintLabsSlave%20&&%20UbuntuTrusty/7/consoleFull",1417612127,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"The only [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/LANGUAGE_SCREENSHOT_CODE=ar,label=contintLabsSlave%20&&%20UbuntuTrusty/4/console | failing scenario ]] at the moment is caused by T76134.",1417101292,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"Change 176235 merged by jenkins-bot:
+[BrowserTest] Fixed a couple of page elements
+
+[[https://gerrit.wikimedia.org/r/176235]]",1417088814,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job,"Change 176235 had a related patch set uploaded (by Zfilipin):
+[BrowserTest] Fixed a couple of page elements
+
+[[https://gerrit.wikimedia.org/r/176235]]
+
+#patch-for-review",1417084758,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sgoczofqmqi4d2v3nizb,task_subcomment,NA
+[Regression wmf10] <visualeditor-formatdropdown-format-blockquote> is displayed in Headings menu ,"Open VE-> Heading - under sub-heading 4, visualeditor-formatdropdown-format-blockquote will be displayed from <span class=""oo-ui-tool-title-text"">&lt;visualeditor-formatdropdown-format-blockquote&gt;</span>(see the attached screenshot).
+{F16461}",1417031233,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ymyyonb4npnvudsmny5o,task_description,declined
+[Regression wmf10] <visualeditor-formatdropdown-format-blockquote> is displayed in Headings menu ,This functionality was released in wmf10 so shouldn't show up in wmf9 wikis; on MediaWiki.org and test2.wikipedia.org it appears fine for me (and also on Beta Labs). Deployment issue?,1417228531,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ymyyonb4npnvudsmny5o,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"There's a range of different loading indicators in Wikimedia Foundation products. 
+Let's unify them.
+
+=== Standard progress indicators
+==== Progress bar (application, elevated above view)
+- **VisualEditor** -   [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=widgets&theme=wikimediaui&direction=ltr&platform=desktop#Progress-bar | ProgressBarWidget (OOUI widget)]] as elevated application loading indicator
+{F33930009 width=50%}
+
+==== Progress indicator (in page)
+- **Three (bouncing) dots** for in-view loading content, for example RCFilters
+  [[ https://codepen.io/Volker_E/pen/yqNXMe | CodePen with dots indicator example at 16px ]]. Depending on context product designers can also choose to go for 12px dot sizes. 
+
+
+---
+
+=== //Outdated, non-standard// progress indicators in Foundation products
+
+**Content translation** - loading article (content). 
+{F3067365}
+
+**Notifications** - loading notifications (content) 
+{F3067366}
+
+**Structured Discussion** - loading more topics (content) 
+|{F27614503}|{F3067367} 
+
+loading contents on infinite scroll
+{F3068028}
+
+**MobileFrontend** - loading ""nearby"" articles (content) 
+|{F27614726}|{F3067368}
+
+---
+**Related notes:**
+- User:Splarka has done some analysis [[ https://www.mediawiki.org/wiki/User:Splarka/Throbber | here ]] to see how loaders work in different colored backgrounds. 
+- Relevant [[ https://phabricator.wikimedia.org/T95137 | task about loading indicators should accelerate as it nears completion ]]
+- {T78062}
+
+",1416989044,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_description,open
+Loading indicators / Progress indicators are inconsistent. ,"hi @Volker_E - here's an example on Growth of how we are using skeleton shimmer instead of the loading indicators due to the large area of content elements all being loaded at different times (Image, article title, extract, page views):
+{F33930219}",1606840372,PHID-USER-ejp5b4zwkqh7wf62j2gh,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,CodePen now also includes small variant and variant with inverted colors for dark background usage.,1532003120,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"A follow-up note on mobile app discussion at T75972#845549
+Apps should make use of the OS specific loading indicators if any possible. ",1531397743,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"Ok, I think //Base30 is a good compromise// as long as designers are aware of the context and consider upping contrast if indicator is used on a dark(er) background in order to stay well recognizable for affected users.",1531393168,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,">>! In T75972#4417813, @Volker_E wrote:
+> From a conversation in Contributors Design meeting this week, let's declare the 3 dots animation our in-view loading animation. 
+> One small amendment that we should be making is increasing the contrast slightly, from `@colorGray12` (`#c8ccd1`) currently to `#54595d` in order to ensure visibility.
+> We can still revisit this later for improvements or alternative animation proposals.
+
+I'm ok in increasing the contrast, but using Base20 (#54595d) seems a bit too dark for a non-interactive element that we want to communicate background activity. I made examples for [[ https://codepen.io/anon/pen/WKvGRj | Base20 ]], [[ https://codepen.io/anon/pen/BPNLZQ | Base30 ]] and [[ https://codepen.io/anon/pen/QBbKaq | Base50 ]]. I think that Base30 (#72777d) could be a good option if we want good-enough contrast without attracting too much attention.",1531393001,PHID-USER-c47vnc2yxmwfvvc4367q,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"From a conversation in Contributors Design meeting this week, let's declare the 3 dots animation our in-view loading animation. 
+One small amendment that we should be making is increasing the contrast slightly, from `@colorGray12` (`#c8ccd1`) currently to `#54595d` in order to ensure visibility.
+We can still revisit this later for improvements or alternative animation proposals.",1531347981,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,I changed from indeterminate to just a discussion of loading indicators so we can look at loading indicators as a whole. Documented here on MW: https://www.mediawiki.org/wiki/Wikimedia_User_Interface/Use_cases/Loading_Indicators,1449814259,PHID-USER-tjeabpzbwsqw3xciydvb,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,Over on T61699 I've got a hi-dpi update to jquery.spinner in MW core that doesn't change its design -- should I go ahead and try to land that as-is for now or wait on this design to replace it?,1436477741,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"@prtksxna yes, here's my first cut http://nirzar.github.io/prototypes/ui/primary-button-loading.html",1436477184,PHID-USER-ed7ta55b47bd3ag6cnuw,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"@nirzar, didn't you at some point make prototypes of this indicator along with buttons? Is this same/related? Could you please add a link to that task?",1435823360,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"sure, @Pginer-WMF has designs for an in-page indeterminate loading indicator, I'd like for us to consistently use this when we have in-page indeterminate loaders. On the app this could be… loading search results, long articles, large images, nearby lists, etc. ",1418671203,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,">>! In T75972#848540, @Jaredzimmerman-WMF wrote:
+> @Deskana, There are other other in-page loaders that you see occasionally, are these all inherited from mobile web?
+
+From the engineering perspective, we don't inherit anything about our UI from mobile web or desktop. It's nontrivial to inherit UI elements from mobile web for a variety of technological reasons. It's possible that they were designed the same way and therefore look very similar, however. You'd have to ask your designers about that. :-)
+
+> As far as inconsistency with Material Design or iOS guidelines, I feel we've already settled on a look and feel that is wikimedia, rather than being platform specific. I know that we've made subtle platform adjustments, but overall we've diverged pretty far from each platform's design in order to have something that is unique to the application. 
+
+Yes and no. We use material design icons in the Android app almost everywhere for things like search, table of contents, hamburger menu, etc. We also use an Android-spec progress bar for page load indication. For pretty routine operations like this, it means if someone's used another app on their phone then they reasonably know what to expect from ours. As mentioned, I would be reluctant to break that pattern.
+
+In other places, we don't pay much attention to their guidelines (e.g. progressive action buttons in the editing workflow are not in line with Android). For editing I think that makes sense, because the editing workflow is so unique to our application.
+
+But anyway, this is a pretty high level discussion. To figure out our next steps, could you say specifically what you're proposing we do in the iOS app and the Android app? Thanks!",1418670441,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"@Deskana, There are other other in-page loaders that you see occasionally, are these all inherited from mobile web? As far as inconsistency with Material Design or iOS guidelines, I feel we've already settled on a look and feel that is wikimedia, rather than being platform specific. I know that we've made subtle platform adjustments, but overall we've diverged pretty far from each platform's design in order to have something that is unique to the application. ",1418669449,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"This doesn't make much sense as a task for mobile apps. For system controls like loading indicators, it's much important to use the platform's built-in controls rather than making our own arbitrary ones, because our app should be consistent with other apps in the platform.
+
+For example, the Android platform has the Toolbar class (which we use for our toolbar) which has a built in progress bar; that's the standard paradigm on the platform, and we'd need a //really// good reason to intentionally make our apps incompatible with material design.",1418448174,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"Here are some details:
+- [[ http://codepen.io/anon/pen/VYYvXM | Live example ]]
+- [[ https://gerrit.wikimedia.org/r/#/c/144873/ | Patchset from the Language team implementing it in Content Translation]]
+- More details in [[ https://trello.com/c/2u8W6qn8/53-consistent-load-more-animation-in-core | this Trello card ]]
+
+{F20240}",1418154713,PHID-USER-c47vnc2yxmwfvvc4367q,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,"
+
+
+- [[ http://codepen.io/anon/pen/VYYvXM | Live example ]]
+- [[ https://gerrit.wikimedia.org/r/#/c/144873/ | Patchset from the Language team implementing it in Content Translation]]
+- More details in [[ https://trello.com/c/2u8W6qn8/53-consistent-load-more-animation-in-core | this Trello card ]]
+",1418154686,PHID-USER-c47vnc2yxmwfvvc4367q,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+Loading indicators / Progress indicators are inconsistent. ,@pginer-wmf can you link to the indeterminate loaders that are being used in flow/CX please?,1417811605,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-tuxjn2c5glhsmp3uc4wx,task_subcomment,NA
+A message key appears instead of the actual message in visualeditor-dialog-meta-settings-newsectioneditlink-help,"In the help bubble that shows the message visualeditor-dialog-meta-settings-newsectioneditlink-help, the message ""vector-view-edit"" is mentioned. It is supposed to show ""Edit"" to the user, but it shows ""[vector-view-edit]"" instead. The value of the message should probably be sent as a parameter instead of using {{int:vector-view-edit}}.",1416984339,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-zmcluk2i4zmrgthivhmp,task_description,resolved
+A message key appears instead of the actual message in visualeditor-dialog-meta-settings-newsectioneditlink-help,"Change 176071 merged by jenkins-bot:
+i18n: Pass value to <visualeditor-dialog-meta-settings-newsectioneditlink-help>
+
+[[https://gerrit.wikimedia.org/r/176071]]",1417462535,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zmcluk2i4zmrgthivhmp,task_subcomment,NA
+A message key appears instead of the actual message in visualeditor-dialog-meta-settings-newsectioneditlink-help,"Change 176071 had a related patch set uploaded (by Jforrester):
+i18n: Pass value to <visualeditor-dialog-meta-settings-newsectioneditlink-help>
+
+[[https://gerrit.wikimedia.org/r/176071]]
+
+#patch-for-review",1417036737,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zmcluk2i4zmrgthivhmp,task_subcomment,NA
+Create technical-debt project,"Name: technical-debt
+Type of project: Tag
+Description:
+
+Technical debt (also known as design debt[1] or code debt) is a recent metaphor referring to the eventual consequences of poor system design, software architecture or software development within a codebase. The debt can be thought of as work that needs to be done before a particular job can be considered complete or proper. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on. Unaddressed technical debt increases software entropy. - https://en.wikipedia.org/wiki/Technical_debt
+Examples: Missing unit tests, duplicate code.
+",1416928132,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_description,resolved
+Create technical-debt project,We need to tag existing bugs with the keyword. But this ticket can be closed. Thanks for creating the keyword.,1418076477,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"What needs to be done here for Wikidata, or can we mark this as Resolved?",1418075295,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,">>! In T75892#831488, @Qgil wrote:
+>> Editable By VisualEditor (Project)
+> 
+> You do it.  :)
+
+Done: https://phabricator.wikimedia.org/project/view/609/
+I also merged all the MobileFrontend tasks into it, archived that project with a note, and added the old projects' tags to the new one.",1418075139,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"> Editable By VisualEditor (Project)
+
+You do it.  :)",1418071319,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,">>! In T75892#824439, @Qgil wrote:
+>>>! In T75892#790593, @Jdforrester-WMF wrote:
+>> Rather than create a new project, just re-label one of the existing two and be done with it?
+> 
+> Should we go for renaming #VisualEditor-TechnicalDebt ?
+
+That would involve the fewest tasks needing to have a project added, so WFM. Let's do it?",1418054800,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,">>! In T75892#790593, @Jdforrester-WMF wrote:
+> Rather than create a new project, just re-label one of the existing two and be done with it?
+
+Should we go for renaming #VisualEditor-TechnicalDebt ?",1418031720,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,">>! In T75892#793155, @JanZerebecki wrote:
+> This ""old bugs and feature requests that are standing somewhere and we never had the time to address"" definitively does not describe _technical_ debt. Some specific technical debt may at the same time also be a functionality bug, but neither is a sufficient condition for the other.
+> 
+> See the link to en.wp in the description. do you think that does not sufficiently define the term?
+
+Indeed, the definition on enwiki is very badly worded. Technical debt covers ""poor"" decisions about code structure, but it also covers great decisions that turn out five years later to be inadequate for future needs. //E.g.// a reasonable technical debt bug would be ""Have MediaWiki use a NoSQL rather than RDBMS back-end""; the ""decision"" not to use NoSQL never happened, because MediaWiki's design and creation pre-dates that technology.
+
+Some real-world examples of types from VisualEditor: T51439 is (was) a criticism of our code that we made when we built the original; T49344 is a subsequent decision about what architecture would be better given developing needs.",1417198682,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"Yes, yes, I agree with you and I am glad that we have such a good description in Wikipedia. I wasn't referring to the theoretical description but to the deviation in regular use that might occur if we don't pay attention.",1417176934,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"This ""old bugs and feature requests that are standing somewhere and we never had the time to address"" definitively does not describe _technical_ debt. Some specific technical debt may at the same time also be a functionality bug, but neither is a sufficient condition for the other.
+
+See the link to en.wp in the description. do you think that does not sufficiently define the term?",1417175501,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"+1 to renaming an existing project and consolidating the rest (tracking bug etc) around it.
+
++1 also on sharing a clear definition of what is and what is not ""technical debt"". Frequently I have heard this term in product management and management management conversations with the meaning of ""old bugs and feature requests that are standing somewhere and we never had the time to address"".",1417161566,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"Rather than create a new project, just re-label one of the existing two and be done with it?",1417073613,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"Shouldn't we maybe just convert T2700 from a tracking bug into a [[ https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Type_of_project | tag project ]]? :)
+
+Also wondering if that means that tasks in #VisualEditor-TechnicalDebt should be moved to the generic VisualEditor project && that new Technical-Debt tag project (or whatever it will be called). 
+And maybe same for #MobileFrontend-Hygiene ?",1417059498,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Create technical-debt project,"+1, this would be useful. How much tech debt vs. feature work gets done is a sort of project health metric (as is the number of tech debt tickets, of course). A team might decide to spend X% of its time on working off tech debt, etc. An explicit way of marking tech debt tasks would make it much easier to track that.",1416953103,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ncbhpeaekx466zjaq6at,task_subcomment,NA
+Cancel button does not work for Insert-Template and some Cite options in VisualEditor in Monobook,"The dialog boxes that have extremely small font(T75800)  get stuck on the screen when Cancel button is clicked. 
+
+1. VE in beta with redirect=no&veaction=edit&useskin=monobook
+2. Insert -> Template - click Cancel- nothing happens; the dialog box gets stuck on the screen, need to refresh.
+
+The same issue with Cancel in Cite-Website, Book, News, Journal.
+ ",1416870621,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-twc6oxttivmbeivgzrtf,task_description,resolved
+Update bits of VisualEditor still referring to Bugzilla,"The ""Leave feedback"" option in VE allows to report a bug:
+The ""list of known bugs"" link should point to its equivalent here;
+The ""I checked, report a new bug"" button needs to point to the (possibly partially pre-filled) task creation form here.
+",1416833813,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-h4m4lscojm4qbgfbthk7,task_description,resolved
+Update bits of VisualEditor still referring to Bugzilla,"Links refer to Phabricator - however, what happened to the color of links? 
+
+From color: #0b0080; in test2 and production to color: #362b36 in beta? 
+https://phabricator.wikimedia.org/T85857 is filed.",1420492721,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"Change 182464 merged by jenkins-bot:
+Update bugzilla links to phabricator
+
+[[https://gerrit.wikimedia.org/r/182464]]",1420459663,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"Change 182462 merged by jenkins-bot:
+Update bugzilla links to phabricator
+
+[[https://gerrit.wikimedia.org/r/182462]]",1420459657,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"Change 182464 had a related patch set uploaded (by Alex Monk):
+Update bugzilla links to phabricator
+
+[[https://gerrit.wikimedia.org/r/182464]]
+
+#patch-for-review",1420214863,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"Change 182462 had a related patch set uploaded (by Alex Monk):
+Update bugzilla links to phabricator
+
+[[https://gerrit.wikimedia.org/r/182462]]
+
+#patch-for-review",1420213367,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Update bits of VisualEditor still referring to Bugzilla,"To be precise, the 2 messages are MediaWiki:Feedback-bugornote and MediaWiki:Feedback-bugcheck.
+",1420203433,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-h4m4lscojm4qbgfbthk7,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"The ""Alternative text"" label in the VisualEditor media adding dialog is not entirely clear to people who aren't familiar with web authoring and accessibility technologies. It would be useful to add a little explanation in a small font near that label, that would explain what is alternative text for and how to write it so it will be really useful.",1416831637,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-rqmz2t77d5756bkn77xp,task_description,resolved
+Add an explanation about Alternative text in the media adding dialog,Checked in betalabs. ,1422916476,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"Change 187447 merged by jenkins-bot:
+Add help icon for FieldsetLayout
+
+[[https://gerrit.wikimedia.org/r/187447]]",1422571846,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"Change 187447 had a related patch set uploaded (by Mooeypoo):
+Add help icon for FieldsetLayout
+
+[[https://gerrit.wikimedia.org/r/187447]]
+
+#patch-for-review",1422557955,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"Change 186108 merged by jenkins-bot:
+MWMediaDialog: Add contextual help for controls
+
+[[https://gerrit.wikimedia.org/r/186108]]",1422488523,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Add an explanation about Alternative text in the media adding dialog,"Change 186108 had a related patch set uploaded (by Jforrester):
+MWMediaDialog: Add contextual help for controls
+
+[[https://gerrit.wikimedia.org/r/186108]]
+
+#patch-for-review",1421798146,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rqmz2t77d5756bkn77xp,task_subcomment,NA
+Decide what to do with tracking bugs,"There are a lot of them, see T4007 and the #tracking tag.
+
+I suppose they should eventually all be closed and replaced with tags or projects.
+
+See also T266.",1416790347,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-flyugauog5dd6v4unsi7,task_description,resolved
+Decide what to do with tracking bugs,"Removed {{draft}}, linked from https://www.mediawiki.org/w/index.php?title=Phabricator%2FProject_management&diff=1426794&oldid=1425629
+
+Closing as resolved.",1425050149,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,Draft: https://www.mediawiki.org/wiki/Phabricator/Project_management/Tracking_tasks,1424897051,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"Copying my steps from T86232#1034556:
+* Requested project has been created: MediaWiki-jQuery-Tablesorter
+* Dependency tasks of tracking task 33601 have been added to the new project.
+* Subscribers of 33601 have been added as project members to the new project.
+* Tracking task 33601 has been closed and its summary updated. Also added new summary as a comment as mail notification settings differ among folks.",1423759341,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,">>! In T75703#936981, @Qgil wrote:
+> So what about this guideline:
+> 
+> * Subtasks and blockers of real tasks are totally fine.
+> * If someone wants to convert a tracking task in a project, they just need to follow the regular process to request a new project, announcing the proposal in the own tracking task. 
+> * New tracking tasks are discouraged. If we find one, let's propose the promoter(s) to create a project instead.
+
++1. Should move these bullet points plus the workaround in T75703#937036 to some wikipage. 
+Probably some subpage of https://www.mediawiki.org/wiki/Phabricator/Project_management and linking from ""Tasks cannot be worked on yet"" (covers dependencies) or ""Scope of tasks"" (covers subtasks)?
+
+Should also note that the actual work (mass-add new project to open and closed tasks; close old tracking bug by editing description saying ""This task is not used anymore for tracking. Tickets have been moved to project #Foobar"") to convert a tracking task to a project could be done by the requester having batch-edit permissions.
+Might also want to mention advantages: Workboard for project.
+
+After moving this to a wikipage I consider this task done.",1423175791,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,">>! In T75703#1006222, @Ciencia_Al_Poder wrote:
+> Now in Phabricator I find it a lot harder to do.
+
+See T33.",1422737387,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"Adding a bug to a tracking bug in bugzilla was easy, because there were 2 ways of doing that: from the tracking bug or from the bug itself. And it was a matter of adding the bug number in the comma-separated list of bug numbers.
+
+Now in Phabricator I find it a lot harder to do. You can only do that from the tracking task, which usually contains **tons** of blocked tasks (see T2384). It presents you a search to type the task number or description, and below the interminable list of blocked tasks, and you need to scroll until the end of the list to add the new task. I find it crappy enough to comment this situation.
+
+This situation could be alleviated if Phabricator allowed to edit the blocking tasks from the inverse perspective (add the tracking task from the child task itself) as Bugzilla allowed.
+
+Converting tracking tasks into projects would be more helpful",1422708507,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"# Select all the blocking tasks
+# Paste in Gedit or equivalent
+# Save as csv
+# Open in Calc or equivalent, using ""space"" as separator
+# Copy the column with the reference numbers
+# Paste it in Gedit or equivalent
+# Ctrl-H to substitute all colons by commas
+# Copy the list of task numbers with commas
+# Paste it in ""Task IDs"" field in Maniphest advanced search and hit ""Search""
+
+Sounds complicated but it takes just a couple of minutes. See an example from T2745 to https://phabricator.wikimedia.org/maniphest/query/bKU3kGuAWKFB/#R (278 tasks)
+",1419022698,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"# Select all the blocking tasks
+# Paste in Gedit or equivalent
+# Save as csv
+# Open in Calc or equivalent, using ""space"" as separator
+# Copy the column with the reference numbers
+# Paste it in Gedit or equivalent
+# Ctrl-H to substitute all colons by commas
+# Copy the list of task numbers with commas
+# Paste it in ""Task IDs"" field in Maniphest advanced search and hit ""Search""
+
+Sounds complicated it takes just a couple of minutes. See an example from T2745 to https://phabricator.wikimedia.org/maniphest/query/bKU3kGuAWKFB/#R (278 tasks)
+",1419022657,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"# Select all the blocking tasks
+# Paste in Gedit or equivalent
+# Save as csv
+# Open in Calc or equivalent, using ""space"" as separator
+# Copy the column with the reference numbers
+# Paste it in Gedit or equivalent
+# Ctrl-H to substitute all colons by commas
+# Copy the list of task numbers with commas
+# Paste it in ""Task ID"" field in Maniphest advanced search and hit ""Search""
+
+Sounds complicated it takes just a couple of minutes. See an example from T2745 to https://phabricator.wikimedia.org/maniphest/query/bKU3kGuAWKFB/#R (278 tasks)
+",1419022631,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,">>! In T75703#936981, @Qgil wrote:
+> So what about this guideline:
+> 
+> * Subtasks and blockers of real tasks are totally fine.
+> * If someone wants to convert a tracking task in a project, they just need to follow the regular process to request a new project, announcing the proposal in the own tracking task. 
+> * New tracking tasks are discouraged. If we find one, let's propose the promoter(s) to create a project instead.
+
+Sounds good. Note that the line between real tasks and tracking bugs can get a little blurry, though — e.g. ""Get Xyz ready to go"" or ""Release Abc version 1.0"", so some judgement may be needed. ",1419021948,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,">>! In T75703#936775, @Aklapper wrote:
+> I wonder if there's a sane way to get all the tasks under ""Blocked by"" on (e.g. T2745 for T78670) into a ""Maniphest search query"" format to then use the ""Batch editing"" mode and mass-add a newly created project tag. I am afraid there isn't, which will make converting really cumbersome.
+> 
+> https://phabricator.wikimedia.org/maniphest/query/advanced/ does not offer a field ""Blocking: T9876543"" either.
+> 
+> Even if I had a list, ""Batch editing"" does not offer a ""Remove Blocker bug T9876543"" either so I guess I'd just leave that as is, and add a comment to the tracking bug that it's replaced by a project tag and close it as invalid.
+> 
+> Meh.
+
+Yeah, I filed this upstream but I'm on my phone right now so can't find it. Consequently all the VisualEditor tracking bugs are waiting for me to have some time and being bored as hell. :-)",1419021824,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"So what about this guideline:
+
+* Subtasks and blockers of real tasks are totally fine.
+* If someone wants to convert a tracking task in a project, they just need to follow the regular process to request a new project, announcing the proposal in the own tracking task. 
+* New tracking tasks are discouraged. If we find one, let's propose the promoter(s) to create a project instead.",1419021397,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I wonder if there's a sane way to get all the tasks under ""Blocked by"" on (e.g. T2745 for T78670) into a ""Maniphest search query"" format to then use the ""Batch editing"" mode and mass-add a newly created project tag. I am afraid there isn't, which will make converting really cumbersome.
+
+https://phabricator.wikimedia.org/maniphest/query/advanced/ does not offer a field ""Blocking: T9876543"" either.
+
+Even if I had a list, ""Batch editing"" does not offer a ""Remove Blocker bug T9876543"" either so I guess I'd just leave that as is, and add a comment to the tracking bug that it's replaced by a project tag and close it as invalid.
+
+Meh.",1419017988,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"@Lydia_Pintscher: Yes, sorry, I meant T54385. Comment edited.",1418039157,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,@Qgil: I think that is the wrong ticket id you linked? We have a few tasks in Wikidata that are not worth their own project like T73519 but would still be good to mark as tracking somehow. The tag works fine for that for me.,1418038537,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I think we could decide the deprecation of the Tracking tag, but without getting too obsessed about it. The idea is that tracking tasks are either converted to projects or to regular tasks with blockers, having a chance to have more projects associated with them now.
+
+#tracking includes a list of recent changes, which is useful to see which tracking tasks are seeing activity. We could start with these. 
+
+For instance, {T37707} has Tracking and an own project, so Tracking could be safely removed there. 
+
+T54385 is a less clear candidate for an own project, but it seems that its scope fall almost entirely within Wikidata/Wikibase. We could ask @Lydia_Pintscher what does she prefer to do with it.
+
+",1418038918,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I think we could decide the deprecation of the Tracking tag, but without getting too obsessed about it. The idea is that tracking tasks are either converted to projects or to regular tasks with blockers, having a chance to have more projects associated with them now.
+
+#tracking includes a list of recent changes, which is useful to see which tracking tasks are seeing activity. We could start with these. 
+
+For instance, {T54385} has Tracking and an own project, so Tracking could be safely removed there. 
+
+T37707 is a less clear candidate for an own project, but it seems that its scope fall almost entirely within Wikidata/Wikibase. We could ask @Lydia_Pintscher what does she prefer to do with it.
+
+",1418038897,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I think we could decide the deprecation of the Tracking tag, but without getting too obsessed about it. The idea is that tracking tasks are either converted to projects or to regular tasks with blockers, having a chance to have more projects associated with them now.
+
+#tracking includes a list of recent changes, which is useful to see which tracking tasks are seeing activity. We could start with these. 
+
+For instance, {T37707} has Tracking and an own project, so Tracking could be safely removed there. 
+
+T37707 is a less clear candidate for an own project, but it seems that its scope fall almost entirely within Wikidata/Wikibase. We could ask @Lydia_Pintscher what does she prefer to do with it.
+
+",1418033300,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"I'm not sure if this needs a ""generic solution"". I'm curious to see which tracking tasks will actually see activity (adding and removing items) and which ones were and are mostly forgotten.
+
+In general and when still actively used, tracking tasks sound like something to convert into tag projects (as tracking tasks were a workaround in Bugzilla to emulate keywords; keywords needed to be set up by a Bugzilla admin who might have asked questions why something is actually needed, while some folks loved to just go ahead and categorize items).",1417218535,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+Decide what to do with tracking bugs,"In #VisualEditor I'm in the process of converting them all into projects, which is quite painful without the bulk edit right. :-)",1416791649,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-flyugauog5dd6v4unsi7,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","Goal:
+
+Save page with edit summary ""Copyedit"".
+
+
+(Almost) result:
+
+Save page with no edit summary, but with the word 'Copyedit' added in the middle of the link that I had just fixed.
+
+
+Steps to reproduce:
+
+1) Edit any page.
+
+2) Click the save button.
+
+3) Start typing your edit summary.
+
+4) Stop typing your edit summary and start backspacing.
+
+5) Click inside the Save dialog.
+
+6) Type your edit summary again.
+
+7) File another bug in Bugzilla.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416516180,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uonptigegjibdzpnxm6t,task_description,resolved
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","Change 182976 merged by jenkins-bot:
+Re-focus edit summary input when save dialog is ready
+
+[[https://gerrit.wikimedia.org/r/182976]]",1420549052,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","Change 182976 had a related patch set uploaded (by Alex Monk):
+Re-focus edit summary input when save dialog is ready
+
+[[https://gerrit.wikimedia.org/r/182976]]
+
+#patch-for-review",1420505772,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog",Oh I did manage to reproduce what I think is this issue when I tried it on testwiki though - the focus moves from the summary field to somewhere else when I press save again.,1420504423,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","The cursor always goes back to the summary field for me, after following those instructions.",1420504284,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","Tricky to reproduce - happens only in test2: 
+
+- make some changes on a page - click Save
+- in 'Save your changes dialog box' check(or uncheck) 'This is minor edit' check box - notice that the cursor will be gone from the Summary area.
+- click 'Resume editing' and make some changes again
+- click Save - the cursor won't be placed in the Summary area anymore",1417567033,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog",Did anyone other than the reporter ever manage to reproduce this issue?,1417481630,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog","James also tried this and couldn't reproduce it. I think I may have asked someone else as well since... not sure.
+
+If anything caused this, it's probably https://gerrit.wikimedia.org/r/172658/ (and -maybe- another thing related to the de-isolation of windows?)",1416863565,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog",Worksforme...,1416528682,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+"VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog",Is this a regression? I thought it used to work…,1416524958,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uonptigegjibdzpnxm6t,task_subcomment,NA
+VisualEditor: mw.Target / ViewPageTarget re-write,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416365160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-e3w6zshniruifvkfks6d,task_description,open
+VisualEditor: mw.Target / ViewPageTarget re-write,"Not really a tracking bug, on reflection.",1416436188,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-e3w6zshniruifvkfks6d,task_subcomment,NA
+VisualEditor: Decide whether this.active should be in mw.Target or mw.ViewPageTarget,"Right now ViewPageTarget defines this.active, but it's set to true by mw.Target. This is horrible. The obvious fix is to push the setting to true down to ViewPageTarget, but we should consider whether the Target class itself should have some sort of active state.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416364980,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-x62ljudld7jl6ovaojqy,task_description,open
+VisualEditor: Improve FileDropHandler API,"From comments at https://gerrit.wikimedia.org/r/#/c/173296/1/src/ui/filedrophandlers/ve.ui.DSVFileDropHandler.js :
+
+* Right now every child class calls createProgress( insertableDataDeferred.promise() ); in its process() method. This seems like something that should be in the base class instead. Would you ever want to not do that, or pass a different promise?
+
+* Child classes should not have to override abort() just to add this.reader.abort();, because this.reader is added by the base class.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416338940,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2aag2u6vtt53677npv2w,task_description,open
+VisualEditor: Warn if editing a citation that is used multiple times,"The fix 52792 will display a warning ""This reference is used [n] times on this page."" when editing Basic citation only. 
+
+Apply the same warning when editing mutliple instances of any kind of citations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1416331860,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-a44mepuutxluyfml3j5g,task_description,open
+VisualEditor: Warn if editing a citation that is used multiple times,"This is the same issue as editing the group of a non-basic citation.
+
+It's possible by simply selecting the reference, opening the menu and selecting 'Basic' (even if it isn't basic).",1416345549,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-a44mepuutxluyfml3j5g,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"Hi, I'm posting this request on behalf of the https://ca.wikiquote.org admins. They want to bring VisualEditor to their users. We have discussed this idea, and I see no problem at all. At the end, most articles there have a very simple structure with initial paragraph, some pictures, and then the same template used always for adding quotes.
+
+I would be happy to help adding template data to the templates affected, and act as bridge in this test.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://ca.wikiquote.org/wiki/Viquidites:La_taverna#Editor_Visual_a_Viquidites",1416135000,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_description,resolved
+Enable VisualEditor in ca.wikiquote.org,Indeed. Sorry for the mistake and thank you for fixing it so quick.,1416330309,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,This was due to an edit to the {{Cita}} template. I've reverted it. https://ca.wikiquote.org/w/index.php?title=Plantilla:Cita&diff=50689,1416330141,PHID-USER-lsveyqlsb4acoowxr5yj,False,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"PLEASE REVERT THIS CHANGE ASAP
+
+Something very weird is happening. In all pages ""}}}}}}"" appears instead of quotes. I mean all pages, not the ones edited with VE. Seeing the source and the history, I can't find any explanation.
+
+See for instance https://ca.wikiquote.org/wiki/Pensaments_den_Goethe",1416329864,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"Now done:
+https://ca.wikiquote.org/w/index.php?title=Especial:Canvis_recents&tagfilter=visualeditor",1416326792,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"Change 174036 merged by jenkins-bot:
+Enable VisualEditor by default on Catalan Wikiquote (cawikiquote)
+
+https://gerrit.wikimedia.org/r/174036",1416326446,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"Change 174036 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on Catalan Wikiquote (cawikiquote)
+
+https://gerrit.wikimedia.org/r/174036",1416271699,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,"(In reply to Glaisher from comment #1)
+> Posting a link here to community consensus might be helpful.
+
+Fair enough. I posted https://ca.wikiquote.org/wiki/Viquidites:La_taverna#Editor_Visual_a_Viquidites
+
+Note that the ca.wikiquote.org community of regular contributors is very small (this is why they are so interested in VisualEditor). Docosong is the only admin. Unapersona is the second most active contributor currently. ESM, KRLS, and ArnauGir are veteran contributors (the last two also ca.wiki admins helping bridging this project with the rest of Catalan-speaking sister projects).
+
+You can wait for more voices, or you can trust the current result.  :)
+
+> Also should it
+> be enabled by default or should it be enabled as a Beta Feature?
+
+In our discussion at the conference, they said that they preferred to have it side by side next to the ""edit source"", because new users are very unlikely to find the option to enable it, or even know that such thing exists.",1416265635,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+Enable VisualEditor in ca.wikiquote.org,Posting a link here to community consensus might be helpful. Also should it be enabled by default or should it be enabled as a Beta Feature?,1416149548,PHID-USER-lsveyqlsb4acoowxr5yj,False,PHID-TASK-77gxvnl3q3ubn5mtomzv,task_subcomment,NA
+VisualEditor: Undefined index: newtimestamp in …/ApiVisualEditorEdit.php,"Nov 15 12:32:30 mw1023:  #012Notice: Undefined index: newtimestamp in /srv/mediawiki/php-1.25wmf7/extensions/VisualEditor/ApiVisualEditorEdit.php on line 137
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1416055080,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-devcuj6oy6zi6ehpdryq,task_description,resolved
+VisualEditor: Undefined index: newtimestamp in …/ApiVisualEditorEdit.php,"Change 173747 merged by jenkins-bot:
+Don't try to get newtimestamp from edit if no change was made
+
+https://gerrit.wikimedia.org/r/173747",1416246526,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-devcuj6oy6zi6ehpdryq,task_subcomment,NA
+VisualEditor: Undefined index: newtimestamp in …/ApiVisualEditorEdit.php,"Change 173747 had a related patch set uploaded by Alex Monk:
+Don't try to get newtimestamp from edit if no change was made
+
+https://gerrit.wikimedia.org/r/173747",1416186618,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-devcuj6oy6zi6ehpdryq,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","edit a page on beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Click the Link inspector. Note the local link created.
+
+Click Remove. 
+
+Click the Link inspector again. 
+
+See an entirely different UI showing ""New page/Matching pages""
+
+Click in the ContentEditable part. ""New page/Matching pages"" UI disappears. 
+
+Click the Link inspector again. 
+
+Nothing happens. Link inspector stops working completely.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415985480,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_description,resolved
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE",This looks like it was fixed a while ago.,1444488231,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Also, happens when you type a text and select that and try to open link inspector for it",1416857350,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Environment:betalabs,test2, en.wiki",1415995223,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Steps to reproduce:
+
+1.Go to this page:http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+2.Click on link inspector icon from the toolbar , but make sure you do not place your cursor in the article first
+
+3.Once the link inspector opens for the first text ""Media"" , click on ""Done"" or ""Remove"" to close the link inspector.Again, do not place the cursor inside CE
+
+4.Click on link inspector icon from the toolbar again
+
+At this step, you will see a broken UI for link inspector,just the link suggestions are appearing as the screenshot.
+
+Also, after this step link inspector stops working completely, clicking on the link icon from the toolbar does not open link inspector for any other text in the article .",1415993491,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","FWIW, I can repro this consistently in Firefox 32.0.3",1415992428,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Created attachment 17126
+clicking Link no longer invokes the Link inspector at all
+
+**Attached**: {F15328}",1415991325,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Created attachment 17125
+after clicking Remove and then clicking Link inspector again
+
+This is clearly wrong
+
+**Attached**: {F15327}",1415991284,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","Created attachment 17124
+after invoking Link inspector the first time, before clicking Remove
+
+**Attached**: {F15326}",1415991225,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE",I cannot reproduce this issue following these steps either.,1415990480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE","On http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit - the link was applied to a specific word(s)? 
+
+I tried to follow your scenario with the word Test on that page - ""New page/Matching pages"" seems to be identical with any attempts.",1415988998,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: Link inspector does not function correctly after closing it using ""Done""/""Remove"" button in Firefox while the cursor is never active on CE",Note: this behavior is seen in Firefox. Chrome seems to be OK.,1415985719,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-wejuqtqqsktmkabwdqxr,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","Gallery with caption gets added to the table inside the image
+
+Environment- test2, beta, production
+
+1> Insert -> media 
+2> insert a table in the caption sub- editor of Media Settings.Click to insert to the main editor.
+2> Highlight the media, insert a gallery with just caption(no filename).
+3> Now drag and drop the gallery on to the table inside the image. Notice the gallery gets added to the table inside the image.
+4> click on the image’s context menu to go to media settings, notice the gallery shows up in the caption pane.See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15189}",1415890380,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-evrokwipdbub7qma7gbx,task_description,resolved
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",Verified the fix in test2.,1416442198,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",Verified the fix in betalabs.,1416262501,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","**gerritadmin** wrote:
+
+Change 173442 merged by jenkins-bot:
+Don't allow dropping inside a handlesOwnChildren node
+
+https://gerrit.wikimedia.org/r/173442",1416256931,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","**gerritadmin** wrote:
+
+Change 173442 had a related patch set uploaded by Catrope:
+Don't allow dropping inside a handlesOwnChildren node
+
+https://gerrit.wikimedia.org/r/173442",1416255192,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",Step 3 should not be possible and is fixed by https://gerrit.wikimedia.org/r/#/c/173442/,1416155394,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","(In reply to etonkovidova from comment #5)
+> Yes, I checked the functionality of inserted tables - all is fine(a tiny bug
+> 73435 was filed). 
+> 
+> Btw, Gallery can be dragged to a Media's Caption.
+yes, if there is something in the media's caption(not just tables even plain text)the gallery gets added to the media's caption.
+
+or
+
+if you had something in the media caption and you deleted it.And then if you drag a gallery to the media's caption part it gets added.
+
+steps- 
+1> go to media settings dialog. 
+2> type in some text in the caption pane,and apply changes.
+3> insert a gallery.
+4> reopen the media settings dialog and delete the caption you put in, at step#2.
+5> now drag the gallery to where the media's caption was. Notice a line is gets drawn and the gallery gets added.",1416069039,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","Yes, I checked the functionality of inserted tables - all is fine(a tiny bug 73435 was filed). 
+
+Btw, Gallery can be dragged to a Media's Caption.",1416002830,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","Tables inside captions are okay. They probably shouldn't be encouraged but in the cases where they exist, we need to provide the tools to edit them.",1415994298,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption","Gallery(with just caption) can be added to a table in the main editor.
+Gallery cannot be added to an image otherwise and is also not available as an insert sub menu option in the media settings toolbar .But if the image has a table it gets added to it.",1415983259,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",In addition to bug 73341 - should tables be allowed for insertion in Media settings?,1415919842,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption",Also in FF 33.1.,1415890448,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-evrokwipdbub7qma7gbx,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"See https://tl.wikipedia.org/wiki/Wikipedia:VisualEditor/Komentaryo#Did_you_know_why.3F .
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://tl.wikipedia.org/wiki/Wikipedia:VisualEditor/Komentaryo#Did_you_know_why.3F",1415886300,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hjiff2rve77sfx43cqpe,task_description,resolved
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),Now done.,1416271503,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"**gerritadmin** wrote:
+
+Change 172993 merged by jenkins-bot:
+Enable VisualEditor by default on Tagalog Wikipedia
+
+https://gerrit.wikimedia.org/r/172993",1416271230,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"(In reply to Roan Kattouw from comment #3)
+> Once the schedule for next week is put on the wiki page, I'll schedule this
+> change again, probably for either Monday 16:00-17:00 UTC or Tuesday
+> 00:00-01:00 UTC.
+> 
+Now scheduled for 00:00-01:00 UTC on Tuesday November 18.",1416003869,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"(In reply to Gerrit Notification Bot from comment #2)
+> Change 172993 had a related patch set uploaded by Jforrester:
+> Enable VisualEditor by default on Tagalog Wikipedia
+> 
+> https://gerrit.wikimedia.org/r/172993
+
+We planned to deploy this about 6 hours ago, but because of an issue with other VisualEditor changes scheduled for the same time, the deployer overlooked this change and I didn't notice that he hadn't deployed it until it was way too late :(
+
+Once the schedule for next week is put on the wiki page, I'll schedule this change again, probably for either Monday 16:00-17:00 UTC or Tuesday 00:00-01:00 UTC.
+
+Sorry for spacing on this :(",1415946788,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),"**gerritadmin** wrote:
+
+Change 172993 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on Tagalog Wikipedia
+
+https://gerrit.wikimedia.org/r/172993",1415889146,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there),Sure.,1415889017,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hjiff2rve77sfx43cqpe,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,"Link inspector opens at the upper left corner
+
+Only Safari(betalbs, test2, production)
+
+1. In VE type a word and convert it into a link.
+
+2. Place a cursor at the end of the word - the link inspector opens at the upper left corner of the screen. The screenshot is attached. 
+
+Note: The link inspector opens correctly if the cursor is placed in the middle of an inserted link. Place a cursor at the end of the link and start moving left - the position of the link inspector will be changed from the correct.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15101}",1415833020,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-23kytwe342kbpmgthgmt,task_description,resolved
+VisualEditor: Link inspector opens in a upper left corner in Safari,"Duplicate to 76083.
+",1423174446,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,"Created attachment 17174
+Safari link inspector
+
+**Attached**: {F15102}",1416432429,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,"**gerritadmin** wrote:
+
+Change 173007 merged by jenkins-bot:
+Update RangeFix library 0.1.0 -> 0.1.1
+
+https://gerrit.wikimedia.org/r/173007",1416246799,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,"**gerritadmin** wrote:
+
+Change 173007 had a related patch set uploaded by Esanders:
+Update RangeFix library 0.1.0 -> 0.1.1
+
+https://gerrit.wikimedia.org/r/173007",1415891713,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor: Link inspector opens in a upper left corner in Safari,Safari browser bug. Applying patch upstream in rangefix.,1415890348,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-23kytwe342kbpmgthgmt,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"This is bug 72251 for magic words.  
+
+{{cite book|isbn=1234567890}} displays as a redlink, and it shouldn't.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415816280,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-luvruzm46k3dlau5z6wg,task_description,resolved
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"(In reply to etonkovidova from comment #4)
+> I copied  
+> {{cite book|isbn=123456789X|url = http://www.amazon.com|title = Fish}} from
+> http://en.wikipedia.beta.wmflabs.org/wiki/User:Jdforrester_(WMF)/Bug_73320
+> and pasted it into test2 - look at the attached screenshot. 
+> 
+> 
+> <a
+> href=""/w/index.php?title=International_Standard_Book_Number&amp;
+> action=edit&amp;redlink=1"" class=""new"" title=""International Standard Book
+> Number (page does not exist)"">ISBN</a>
+> 
+> @media screen
+> 
+> a.new:visited, #p-personal a.new:visited {
+> 	.	
color: #a55858;
+> 
+> 
+>  ISBN is still red.
+
+Yeah, because the word ""ISBN"" links to a page that doesn't exist. This is about the number being red.",1415918355,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"I copied  
+{{cite book|isbn=123456789X|url = http://www.amazon.com|title = Fish}} from http://en.wikipedia.beta.wmflabs.org/wiki/User:Jdforrester_(WMF)/Bug_73320 and pasted it into test2 - look at the attached screenshot. 
+
+
+<a href=""/w/index.php?title=International_Standard_Book_Number&amp;action=edit&amp;redlink=1"" class=""new"" title=""International Standard Book Number (page does not exist)"">ISBN</a>
+
+@media screen
+
+a.new:visited, #p-personal a.new:visited {
+	.	
color: #a55858;
+
+
+ ISBN is still red.",1415918297,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"Created attachment 17122
+ISBN is  displayed in red
+
+**Attached**: {F15070}",1415918147,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,Confirmed with http://en.wikipedia.beta.wmflabs.org/wiki/User:Jdforrester_(WMF)/Bug_73320 – marking as FIXED.,1415916533,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor:  Magic words like ISBN links in templates are rendered as red links now,"I can reproduce this at en.wp today, but not at en.wikipedia.beta.wmflabs.org, so presumably the problem has already been fixed.",1415860817,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-luvruzm46k3dlau5z6wg,task_subcomment,NA
+VisualEditor: Drag-and-drop of a block image doesn't remove the marker lines sometimes (?),"screenshot in chrome
+
+Environment- test2, beta
+
+1> Insert a media with default settings.
+2> keeping the media highglighted,insert a gallery with just caption(no filename).
+3> Now drag and drop the gallery to the image and then image to the gallery. Either way it draws focusablenode dropmarker lines above and below the media content. See screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14939}",1415724180,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-isjhm5lhynj6lgf5pve2,task_description,open
+VisualEditor: Drag-and-drop of a block image doesn't remove the marker lines sometimes (?),"Confirmed - the ""extra"" element that appears during drag-and-drop is <p contenteditable=""false"" class=""ve-ce-branchNode-slug ve-ce-branchNode-blockSlug"">
+
+However, the saved page does not have any traces of extra lines.",1415815891,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-isjhm5lhynj6lgf5pve2,task_subcomment,NA
+VisualEditor: Drag-and-drop of a block image doesn't remove the marker lines sometimes (?),"Created attachment 17095
+screenshot in FF 33.1
+
+**Attached**: {F14940}",1415724365,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-isjhm5lhynj6lgf5pve2,task_subcomment,NA
+"VisualEditor: When selecting FocusableNode with arrow keys, context flickers at position of last mouse click","1. Open a document that contains a line of plain (not linked) text with an inline focusable node (e.g. template or reference)
+2. Use the mouse to put the cursor on this line, some distance away from the text
+3. Use the arrow keys to move the cursor to the focusable node
+4. When the node is focused, the context flickers in the position where you clicked in step 2 before moving to the focusable node
+
+This doesn't happen when you use the mouse to focus the node. It also doesn't happen when the context appears for an annotation (e.g. link).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1415654940,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-sojeywgrcg6knl7y5dzy,task_description,resolved
+"VisualEditor: When selecting FocusableNode with arrow keys, context flickers at position of last mouse click",Verified the fix in beta.,1416443096,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-sojeywgrcg6knl7y5dzy,task_subcomment,NA
+"VisualEditor: When selecting FocusableNode with arrow keys, context flickers at position of last mouse click","Change 173804 merged by jenkins-bot:
+Don't always use updateDimensionsDebounced
+
+https://gerrit.wikimedia.org/r/173804",1416256925,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sojeywgrcg6knl7y5dzy,task_subcomment,NA
+"VisualEditor: When selecting FocusableNode with arrow keys, context flickers at position of last mouse click","Change 173804 had a related patch set uploaded by Esanders:
+Don't always use updateDimensionsDebounced
+
+https://gerrit.wikimedia.org/r/173804",1416229923,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sojeywgrcg6knl7y5dzy,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Proposed in #community-wishlist-survey-2016. Received 41 support votes and was ranked #31 out of 265 proposals. [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | View full discussion and votes here ]].  
+
+----
+
+As a use who is preparing an edit, I'd like to be confident that if some bad interruption happens before I save it (e.g. power outage) I'll likely be able to recover most of my work when I try to edit the page again, even if other countermeasures (e.g. browser cache, local copy) are missing or failed.
+
+Local vs. remote storage, frequency of autosave, expiry etc. are negotiable. The less interface there is, the better; there should be no added preference(s).
+
+Creating because of https://lists.wikimedia.org/pipermail/wikitech-l/2014-November/079378.html and the lack of a bug in core to track this.
+
+----
+
+Something else that I have had in the pipeline for a long while is autosave drafts. Basically, whenever you type, the article is saved to your local computer. If the browser crashes, and you visit the same article, it will prompt you for recovery. Making a Special:Autosave drafts index page would be trivial.
+
+Implementation:
+https://gerrit.wikimedia.org/r/#/c/5130/ <https://gerrit.wikimedia.org/r/#/c/5130/>
+
+Of this, I also have an alternate implementation:
+https://gerrit.wikimedia.org/r/#/c/157818/ <https://gerrit.wikimedia.org/r/#/c/157818/>
+https://gerrit.wikimedia.org/r/#/c/159626/ <https://gerrit.wikimedia.org/r/#/c/159626/>
+
+The original one is based on code by Joancreus and uses localStorage. It works, quite well actually, but while improving it, I became of the opinion that localStorage is basically so limited in storage and gives you so little feedback as an API and an enduser, that it's not really suited for much more than usersettings (big cookies). Not for saving potentially multiple 1MB articles, with structured details.
+
+As a storage layer, indexedDB is much nicer in that regard. API wise, it's a bit convoluted, but a jQuery plugin makes it usable and readable. There are WebSQL polyfills for platforms that don't have indexedDB, which would allow us to support browsers of the past 6 years.
+
+I would like some opinions on which way to go here. Additionally, i would love to hear what else people think would be required to make this usable for the Wikipedia audience and the naming. Would this be Drafts ? Autosave drafts ? autosave ? Would you say 'recover' when asking the user to use the version from drafts, or just 'use draft' etc?
+
+Note that the '2nd' version also has a few more improvements like a separate RL module and a preference option, but those can easily be added to the first implementation as well. 
+
+----
+
+Clearly, I prefer the word ""autosave"", which reminds people of the recovery features endemic in any document editing software; rather than ""draft"", which in the past caused a lot of confusion. LibreOffice, when restarted, asks if you want to ""recover"" a previous document, and many other FLOSS productivity softwares use the same terminology: what do they do on the devil's side (M$ and Apple)?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**Possible consumers**:
+* VisualEditor ({T57370})
+* ContentTranslation, T113221#1844393 (currently DB-based: {rECTX00ebcc6e3e31b278092abde755cbd9009ef65cf4})
+**See Also**:
+* {T39992}
+* {T11749}",1415654160,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_description,resolved
+Auto-save to increase chances of lost edits recovery,"Boldly resolving this as the first part of an autosave feature is now in core, and further improvements are being tracked in the #Edit_Recovery project (which is the terminology we decided on, although I'm sure there's more bikeshedding possible with that if anyone's keen).",1690505060,PHID-USER-hlhhe6qw6qfkl7wyfhxk,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Editing/Autosave_edited_or_new_unpublished_article,1651238704,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,I really need him.,1630387852,PHID-USER-4a5dsnuy5lyy72ieqsb2,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Editing/Make_edits_auto-recoverable_if_the_editor%27s_network_crashes,1608818448,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Change 5130 abandoned by TheDJ:
+mediawiki.action.edit: Autosave edit textareas in localStorage
+
+Reason:
+No progress on this for the past year, abandoning.
+
+[[https://gerrit.wikimedia.org/r/5130]]",1502404558,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,Doesn't fit the definition of stalled. https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle,1465390171,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Change 5130 had a related patch set uploaded (by Jdlrobson):
+mediawiki.action.edit: Autosave edit textareas in localStorage
+
+[[https://gerrit.wikimedia.org/r/5130]]
+",1462483745,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,Looks stalled to me.,1462483736,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Merged in ContentTranslation: 00ebcc6e3e31b278092abde755cbd9009ef65cf4
+No idea how much of its code/idea is reusable.",1416304650,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"(In reply to Umherirrender from comment #3)
+> You have linked the bug, but there should also be a link to
+> [[mw:Extension:Drafts]], which supports auto saving on the server side.
+
+Sure, though that's not ready and even if it was, is not getting deployed to Wikimedia wikis, for reasons explained at length.",1415907123,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"You have linked the bug, but there should also be a link to [[mw:Extension:Drafts]], which supports auto saving on the server side.",1415722646,PHID-USER-qaoxfiqu6bxhd5ehlwhc,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Change 159626 had a related patch set uploaded by Nemo bis:
+Drafts: Refactor with IndexedDB
+
+https://gerrit.wikimedia.org/r/159626",1415654297,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+Auto-save to increase chances of lost edits recovery,"Change 5130 had a related patch set uploaded by Nemo bis:
+mediawiki.action.edit: Autosave edit textareas in localStorage
+
+https://gerrit.wikimedia.org/r/5130",1415654282,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-utpcvnudjvnmrf5n2mpi,task_subcomment,NA
+VisualEditor: Drag-and-drop in IE9 doesn't work,"I can successfully drag-n-drop an image from one part of the page to another in VE while using Chrome and Firefox, but not IE.
+
+Chrome and FF provide feedback, indicating where the object will land if it is dropped, but IE doesn't.  Nor does dropping the object move it.
+
+I don't see any errors in the js console on IE during this process.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51669",1415653560,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-k7ndkr4spt2bt7mgctja,task_description,resolved
+VisualEditor: Drag-and-drop in IE9 doesn't work,"Change 284361 merged by jenkins-bot:
+Fix node drop in IE9
+
+[[https://gerrit.wikimedia.org/r/284361]]",1461111218,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7ndkr4spt2bt7mgctja,task_subcomment,NA
+VisualEditor: Drag-and-drop in IE9 doesn't work,"Change 284361 had a related patch set uploaded (by Esanders):
+Fix node drop in IE9
+
+[[https://gerrit.wikimedia.org/r/284361]]
+",1461101719,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k7ndkr4spt2bt7mgctja,task_subcomment,NA
+VisualEditor: Drag-and-drop in IE9 doesn't work,"Filed the exception as a different bug. Apart from that works in IE11/10 but not 9, where I get a different exception (cannot slice undefined).",1461099325,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-k7ndkr4spt2bt7mgctja,task_subcomment,NA
+VisualEditor: Drag-and-drop in IE9 doesn't work,"Just re-tested against https://en.wikipedia.org/w/index.php?oldid=678508180 ([[Ray County, Missouri]]) and drag-n-drop of images didn't work on IE still.  It did work on FF and Chrome, though.
+
+In IE, clicking on the Route 13 sign ([[File:MO-13.svg]]) shows the Media highlight.  Click off of that and you get the following exception:
+   SCRIPT5022: Nested change of newModelSelection File: load.php, Line: 832, Column: 517
+
+IE's debugger has this call stack:
+
+    ve.ce.Surface.prototype.changeModel [Line: 832, Col: 517], load.php
+    ve.ce.Surface.prototype.handleObservedChanges [Line: 819, Col: 510], load.php
+    ve.ce.SurfaceObserver.prototype.pollOnceInternal [Line: 836, Col: 73], load.php
+    ve.ce.SurfaceObserver.prototype.pollOnceSelection [Line: 835, Col: 625], load.php
+    ve.ce.Surface.prototype.onDocumentSelectionChange [Line: 791, Col: 569], load.php
+    jQuery.event.dispatch [Line: 65, Col: 907], load.php
+    elemData.handle [Line: 60, Col: 384], load.php
+    ve.selectElement [Line: 62, Col: 281], eval code (48)
+    ve.ce.Surface.prototype.preparePasteTargetForCopy [Line: 816, Col: 530], load.php
+    ve.ce.Surface.prototype.onModelSelect [Line: 815, Col: 591], load.php
+    oo.EventEmitter.prototype.emit [Line: 65, Col: 545], eval code (46)
+    ve.dm.Surface.prototype.setSelection [Line: 578, Col: 532], load.php
+    ve.dm.Surface.prototype.changeInternal [Line: 580, Col: 371], load.php
+    ve.dm.Surface.prototype.change [Line: 579, Col: 351], load.php
+    ve.ce.Surface.prototype.changeModel [Line: 832, Col: 609], load.php
+    ve.ce.Surface.prototype.handleObservedChanges [Line: 819, Col: 510], load.php
+    ve.ce.SurfaceObserver.prototype.pollOnceInternal [Line: 836, Col: 73], load.php
+    ve.ce.SurfaceObserver.prototype.pollOnceSelection [Line: 835, Col: 625], load.php
+    ve.ce.Surface.prototype.onDocumentSelectionChange [Line: 791, Col: 569], load.php
+    jQuery.event.dispatch [Line: 65, Col: 907], load.php
+    elemData.handle [Line: 60, Col: 384], load.php
+    ve.ui.LinearContext.prototype.onContextChange [Line: 904, Col: 976], load.php
+    oo.EventEmitter.prototype.emit [Line: 65, Col: 545], eval code (46)
+    ve.dm.Surface.prototype.emitContextChange [Line: 575, Col: 206], load.php
+    ve.dm.Surface.prototype.setSelection [Line: 578, Col: 682], load.php
+    ve.dm.SurfaceFragment.prototype.select [Line: 590, Col: 861], load.php
+    Anonymous function [Line: 760, Col: 529], load.php
+    ve.ce.FocusableNode.prototype.onFocusableMouseDown [Line: 760, Col: 436], load.php
+    jQuery.event.dispatch [Line: 65, Col: 907], load.php
+    elemData.handle [Line: 60, Col: 384], load.php
+",1447172508,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-k7ndkr4spt2bt7mgctja,task_subcomment,NA
+VisualEditor: Removing table row where rowspanned cell starts un-merges the remaining spanned cells,"Removing the table row where rowspanned cell starts un-merges the remaining spanned cells.
+
+1. Look at the tables.html demo.
+2. In ""Merged cells"" example, place cursor at the ""10"" cell.
+3. Delete row.
+
+The ""4"" cell has correctly changed from spanning three to two rows. However, the ""9"" cell has split into three cells, while it should have been changed from spanning four to three rows instead.
+
+Analogous behavior occurs when removing the column where a colspanned cell starts. (Try with the ""16"" cell.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415582400,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xmwils3vchvzzdbgegip,task_description,resolved
+VisualEditor: Removing table row where rowspanned cell starts un-merges the remaining spanned cells,"Change 172193 merged by jenkins-bot:
+Don't unmerge spanned cells when spanned cell is removed
+
+https://gerrit.wikimedia.org/r/172193",1415645918,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xmwils3vchvzzdbgegip,task_subcomment,NA
+VisualEditor: Removing table row where rowspanned cell starts un-merges the remaining spanned cells,"Change 172193 had a related patch set uploaded by Bartosz Dziewoński:
+[WIP] Don't un-merge spanned cells when spanned cell is removed
+
+https://gerrit.wikimedia.org/r/172193",1415589726,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xmwils3vchvzzdbgegip,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","VisualEditor: ""Insert table"" tool should be (also?) in the ""Table"" menu, not (or in addition to?) ""Insert"" menu. I was quite confused for a moment by the table icon being grayed out, and I've been told I'm not the only one.",1415582100,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-paw5zcxophppwlal7wbs,task_description,resolved
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","Change 267532 merged by jenkins-bot:
+Introduce table and table cell context
+
+[[https://gerrit.wikimedia.org/r/267532]]",1454351829,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","Change 267532 had a related patch set uploaded (by Esanders):
+Introduce table and table cell context
+
+[[https://gerrit.wikimedia.org/r/267532]]
+",1454239081,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","My client asked about this and I told her ""That's how it is on Wikipedia"" and found this bug (before I filed my own, yay!).
+
+I vote for enabling the icon when not in a table to allow for table creation.
+
+If I were really sick, I'd say that the option to insert a table should remain available even when in a table cell, so that we could do 90s style webpage layouts in the VisualEditor.
+
+But I'm only a little sick, so activating it to enable table creation/insertion is what I'm going with.",1429629534,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","Alternatively, we could put the table inspector in the proper place (i.e., on the table) rather than over-loading the toolbar, which would remove the confusion.",1415642030,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","The current option is highly temporary, AFAIK.",1415607025,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"VisualEditor: ""Insert table"" tool in a separate menu to the other table tools (delete/merge/caption)","+1. When user wants to create a new table, he can see the icon in the toolbar, but it's marked as displayed. Really confusing. Imho, if we have a special menu for tables, ""Insert table"" should be placed there instead of being in ""Insert menu"". The current solution is reasonable, but unintuitive. (Maybe ""Insert table"" could be visible alternatively with ""Delete table"" #brainstorm).",1415583523,PHID-USER-gf5juv3z3p75bykrcrhf,False,PHID-TASK-paw5zcxophppwlal7wbs,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed","After editing an unreviewed page using VisualEditor, reviewing the page doesn’t review the just-made edit if the page isn’t reloaded between publishing the edit and pressing review.
+
+How to reproduce:
+1) go to some article that hasn't been reviewed yet
+2) make an edit to the article using Visual Editor. save the edit
+3) review the article
+4) when you look at the article history you can see that the article you marked as reviewed has one unreviewed change (the one you just did using VE)
+
+I tried this at https://test2.wikipedia.org/wiki/Testing_something",1415453100,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-d3c74irtdh5bydamc36k,task_description,open
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed","I tried to rephrase the description to be easier to understand (I hope I understood it correctly). However, when I tried to reproduce it on test2wiki, I couldn’t – when I opened VisualEditor, the FlaggedRevs interface disappeared, and when I published the edit, it didn’t come back, so there was no button that could have worked incorrectly. Well that’s also a way to fix this bug…",1731774911,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed","If this is still issue, add more details.",1731542149,PHID-USER-i2ki3npptssmkwi5oirg,False,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed","But if you try to change it, you get ""Invalid inclusion parameter key"".
+That key is actually a hash of several things (including the oldid): https://github.com/wikimedia/mediawiki-extensions-FlaggedRevs/blob/master/business/RevisionReviewForm.php#L211-L213
+We'd need to regenerate it somehow I guess...",1438130013,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",We're not updating the mw-fr-input-oldid hidden input in the FlaggedRevs page review form when we update the page contents.,1438129166,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",We're not updating the oldid hidden in the FlaggedRevs page review form when we update the page contents.,1438129144,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",We're not updating the oldid in the FlaggedRevs page review form when we update the page contents.,1438129136,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",">>! In T75171#1471012, @Jdforrester-WMF wrote:
+> Is this still an issue?
+
+It is. Just tested it again at https://test2.wikipedia.org/wiki/Testing_something",1437583466,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+"When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed",Is this still an issue?,1437581122,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d3c74irtdh5bydamc36k,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Splitting the bug from 72392.
+
+Open a page in VE and insert a link with the shortcut - Ctrl+K - the link inspector opens and closes momentarily. 
+
+The console displays the following(consistently): 
+
+DOM7009: Unable to decode image at URL: 'data:image/gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA'.  File: gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415390280,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-urgeoycg3qunrfzhjulb,task_description,resolved
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,Seems to work fine now - please re-open if it is still broken for you.,1460644310,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Re: ""Strange presentation""
+
+On further examination, The ""File:"" bit was presented as a link with the full URL. Clicking the link took me to the contents of a 1x1 pixel.  That is, where you normally see source code or raw HTML in the debugger, I saw:
+  1. GIF87a□□□Ü□,□□□□□□□□□
+
+Maybe the data urls are messing with IE's head?
+",1426282563,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Just updated to the 1.25wmf21 branch and I'm seeing the message in IE11:
+
+  DOM7009: Unable to decode image at URL: 'data:image/gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA'.
+  File: gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA
+
+There is a [[ http://stackoverflow.com/a/28426679 | stackoverflow answer ]] that indicates this may be related to OOM problems -- and the strange presentatoin of this (""File: gif;base64..."") leads me to believe that might be  the case.
+
+Note that I'm seeing this blatted on the console multiple times while simply selecting text.",1426280123,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"@Etonkovidova: Why was ""Verified-in-Phase0"" set here?",1422893851,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Yes, the message in the console is unrelated to the issue. 
+
+Reproducible **only in production** - inserting a link with a Ctrl+K displays flickering link inspector and move the cursor to the beginning of a paragraph. The link will, in fact, inserted, and can be edited afterwards without any problems. 
+
+Inserting links with a short cut [[ or from Tool menu does not present any issues.",1419371203,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Can't reproduce. I get the message in the console, but only while VE is loading, unrelatedly to link inspector; the inspector opens and works perfectly fine.",1419349851,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily,"Wait, the link inspector actually closes? I thought it was just the error...",1415390374,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-urgeoycg3qunrfzhjulb,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,"Preformatted text in tables
+
+In betalabs
+
+1. In VE insert a table and double-click in any cell to make it editable.
+
+2. Select the 'preformatted' option - the cell will be yanked from the table(similar to bug 72990). The preformatted are will be displayed outside of the table. 
+
+The same happens when you apply preformatted to the cells' text.
+
+Look at the screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15190}",1415313600,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-osvgc2rrhwadyji7x6hl,task_description,resolved
+VisualEditor: handling preformatted text in tables,Verified the fix in test2 and production.,1416434768,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,Verified the fix in Betalabs.,1415658523,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,"Definitely fixed, I ran into this in prod today, wanted to file a bug and couldn't reproduce on master. Now I know why. :)",1415581929,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,"Change 171835 merged by jenkins-bot:
+Support pre's in tables
+
+https://gerrit.wikimedia.org/r/171835",1415382974,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+VisualEditor: handling preformatted text in tables,"Change 171835 had a related patch set uploaded by Esanders:
+Support pre's in tables
+
+https://gerrit.wikimedia.org/r/171835",1415375088,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-osvgc2rrhwadyji7x6hl,task_subcomment,NA
+Flow: Use PHP Virtual REST Service to access Parsoid,"From gerrit 170869:
+> Gabriel suggested that in the future we migrate to the PHP Virtual REST Service and through that share code between Flow, VE and anything else that wants to talk with parsoid.
+https://www.mediawiki.org/wiki/Requests_for_comment/PHP_Virtual_REST_Service
+
+With [[ https://gerrit.wikimedia.org/r/#/c/181011/ | gerrit 181011]] VisualEditor is doing this, so Flow can do the same and remove whatever cookie hacks @Ebernhardson needed to access Parsoid from the private officewiki.
+
+--------------------------
+**Version**: master
+**Severity**: minor",1415138880,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-cz3rtgfxbykofx4kvsia,task_description,open
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"screenshot of JS errors in beta
+
+Environment- test2, beta
+
+1> In a blank page, open the Language inspector.
+2> While the inspector is open ,select any Heading format from the drop-down,for ex- select Heading.
+2> The inspector closes and you see the language context menu. 
+3> type in some text, it doesn’t take the language annotation(looks like plain paragraph text)
+4> Hit enter and JS error “Uncaught Error: Inserted data is trying to close the root node (at index 0)”. See screenshot.
+5> Notice no matter where your cursor is on the page, the language context menu never moves from its place or closes for a new line.
+
+In beta an additional  JS error appears at step#2, “Uncaught Error: Offset could not be translated to a DOM element and offset: 2”.
+
+Reproducible in FF too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows XP
+
+**Attached**: {F14776}",1415115600,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-wt57zr2htyhkzzgovt4f,task_description,resolved
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"I've tried various variations of these steps including with some text to start with (since the original sequence of ""language inspector tujrns into language context, when no text is typed and heading selected"" no longer happened).
+
+No error found in that testing. I suppose this code has likely changed numerous since 2014, and propose any related issue that can be reproduced today be filed as a new task.",1629314979,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"This is surfacing today in the production error logs.
+https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-2020.09.14/clienterror/?id=AXSNst-8c14jQX20-BU0
+
+```
+at writeElement URL1:293:914
+at URL1:296:984
+at URL1:171:877
+at URL1:260:949
+at URL1:535:424
+at URL1:534:922
+at URL1:527:727
+at URL1:523:520
+
+URL1: https://www.mediawiki.org/w/load.php?lang=en&modules=ext.visualEditor.articleTarget%2Cbase%2Ccore%2CdesktopArticleTarget%2CdesktopTarget%2Cdiffing%2Cicons%2Clanguage%2Cmediawiki%2Cmwalienextension%2Cmwcore%2Cmwextensions%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlanguage%2Cmwlink%2Cmwmeta%2Cmwsave%2Cmwsignature%2Cmwtransclusion%2Csanitize%2Cwelcome%7Cext.visualEditor.core.desktop%2Cutils%7Cext.visualEditor.mwextensions.desktop%7Cext.visualEditor.mwimage.core&skin=vector&version=18e9q
+```",1600106182,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"Yes, it is. 
+Here, I was also pointing at the typed text appearing plain, i.e., without any language annotation.",1420914110,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,Isn't that already reported as T76717?,1420898423,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"{F27349}Screenshot of the JS Error ""Offset could not be translated to a DOM element and offset: 2"".",1420866363,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,"I could not reproduce it either.But I did get the JS  error “Uncaught Error: Offset could not be translated to a DOM element and offset: 2” and the text typed was just plain paragraph-like.
+
+Here are the steps-:
+
+Environment- test2, beta
+
+1> In a blank page, open the Language inspector.
+2> While the inspector is open ,select any Heading format from the drop-down,for ex- select Heading.
+3> The inspector closes and you see the language context menu. 
+4> Type some text, it doesn’t take the language annotation(looks like plain paragraph text).JS error “Uncaught Error: Offset could not be translated to a DOM element and offset: 2” appears.
+
+See the screencast at http://youtu.be/qXID9SlMClo",1420865941,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,I can't reproduce this.,1420852027,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.,Confirmed in betalabs Chrome.,1415124077,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-wt57zr2htyhkzzgovt4f,task_subcomment,NA
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"To reproduce:
+
+- Navigate to an article
+- Open Chrome's Developer Tools
+- Click 'Profiles'
+- Select 'Collect JavaScript CPU Profile'
+- Click 'Start'
+- Click 'Edit [beta]'
+- Wait for VisualEditor to finish loading
+- Click 'Stop'
+
+Result:
+
+Both oo.Factory.create or oo.EventEmitter.emit are flagged by the profiler with the warning: ""Not optimized: Inlining bailed out.""
+
+To investigate, I recommend reading <https://github.com/GoogleChrome/devtools-docs/issues/53>
+
+v8 comes with a 'd8' executable that can be used for getting some performance debug info from v8. If you can craft a file that utilizes these functions without depending on the DOM API, you can try running it with:
+
+> d8 --trace-opt --trace-bailout some-js-file.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1415064480,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_description,resolved
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"Change 186244 merged by jenkins-bot:
+v8 opt: Copy arguments into new array rather than use [].slice
+
+[[https://gerrit.wikimedia.org/r/186244]]",1422038468,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_subcomment,NA
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"Change 186244 had a related patch set uploaded (by Jforrester):
+v8 opt: Copy arguments into new array rather than use [].slice
+
+[[https://gerrit.wikimedia.org/r/186244]]
+
+#patch-for-review",1421948376,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_subcomment,NA
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"EventEmitter.emit also seems to be because of arguments. I checked, though, and there's very little ""self"" time spent in EventEmitter.emit and Factory.create: 25ms and 53ms respectively for Obama. But I'll see what that drops to after optimizing them.",1415216420,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_subcomment,NA
+OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit,"For oo.Factory.create, my version of Chrome tells me ""Not optimized: Bad value context for arguments value"" which seems to be a consequence of doing args = Array.prototype.slice.call( arguments, 1 ); . I don't really see a way around that, unless there's some way of making the arguments list a real array that V8 is able to optimize.
+
+For oo.EventEmitter.emit it does say ""Inlining bailed out"". I'm installing d8 now to investigate.
+
+I saw a bunch of other ""not optimized"" warnings too, but most of those seem to be about try-catch statements. The only other one that jumped out at me was in oo.copy: ""ForInStatement is not fast case"". Will investigate that too.",1415131201,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5vjdcr5yqcamhgt2wymw,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,"Edit summary textbox is black
+
+Steps to reproduce: 
+
+ In IE 11 perform some editing in VE and click Save page.
+
+Observe: 'Edit summary' text box is displayed black. When clicked in it - it becomes white. 
+
+The screenshot is attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15398}",1415045640,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-vcg3kzlidjqghgcegqdp,task_description,resolved
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,"Can't reproduce even if I display input.focus() (which has always worked, I think). ",1461096698,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,"Well you said:
+> When clicked in it - it becomes white.
+
+So I assume you focusing it was just hiding the problem, and we now do it automatically.",1421203405,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,"Is it black if we don't focus? If so, what other dialogs are affected by this IE bug?",1421202864,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,So I can't reproduce this in IE11 but I assume that's because we auto-focus that text box now? What shall we do about this task?,1421202773,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11,So I can't reproduce this in IE11 but I assume that's because we auto-focus this now? What shall we do about this task?,1421202750,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-vcg3kzlidjqghgcegqdp,task_subcomment,NA
+"VisualEditor: Restore selection when user exits the save dialog (on clicking ""Resume editing"")","Edit any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit
+
+Perform some action, for example highlight text and indent some. 
+
+Click Save page and then click Resume editing from the Save modal dialog.
+
+Upon returning to the edit page, VE edit tools should be enabled but are not enabled.  User must click again in the CE area to enable edit tools.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1415037480,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-4kpfmliccubzixbhguff,task_description,resolved
+"VisualEditor: Restore selection when user exits the save dialog (on clicking ""Resume editing"")",Verified in test2.,1416439167,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-4kpfmliccubzixbhguff,task_subcomment,NA
+"VisualEditor: Restore selection when user exits the save dialog (on clicking ""Resume editing"")","Change 172658 merged by jenkins-bot:
+Restore selection after closing save dialog
+
+https://gerrit.wikimedia.org/r/172658",1415816987,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4kpfmliccubzixbhguff,task_subcomment,NA
+"VisualEditor: Restore selection when user exits the save dialog (on clicking ""Resume editing"")","Change 172658 had a related patch set uploaded by Alex Monk:
+Restore selection after closing save dialog
+
+https://gerrit.wikimedia.org/r/172658",1415750293,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4kpfmliccubzixbhguff,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"screenshot showing multiple Categories with same title
+
+Environment- production, test2
+
+1>Select Categories. Add a category for ex- “Japan”.
+2>The cursor moves to the next input field. Type in “Japan” again. Click somewhere else in the modal, to move the focus. 
+3>Click back in the input field. While the cursor is in the field,hit enter key.
+4>The category with the same name Japan gets added.See screenshot.
+
+In beta, at step#2, after typing in the title, just click twice in the input field(to close the drop-down) and hit enter key. The category with the same title gets added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15381}",1415029080,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_description,resolved
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,Verified in production.,1416425972,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,The fix is verified in betalabs and test2.,1415232622,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"**gerritadmin** wrote:
+
+Change 171033 merged by jenkins-bot:
+Kill MWCategoryWidget#onLookupEnter
+
+https://gerrit.wikimedia.org/r/171033",1415150298,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"**gerritadmin** wrote:
+
+Change 171033 had a related patch set uploaded by Alex Monk:
+Kill MWCategoryWidget#onLookupEnter
+
+https://gerrit.wikimedia.org/r/171033",1415133439,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"Sorry, Alex.",1415056909,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+VisualEditor: [Regression] Don't let the user insert the same category multiple times,"Confirmed in betalabs, test2, and production.",1415051897,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-bvr7nre4pjr3pofdoq6o,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,"There is text in these forms that can only be seen when selecting.
+
+The same issue as described in bug 72188 applies in VisualEditor; namely that dark system settings lead to unreadable text in certain forms. This is almost certainly because the background colour has been defined and the text colour has been left to the system, leading, in this case, to white text on a white background.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15230}",1414819200,PHID-USER-uku6gl4xeqbtbrcbr5ig,False,PHID-TASK-kjvvoq653qna4dsuzabo,task_description,resolved
+OOjs UI: Unreadable input box text with dark colour schemes,"**gerritadmin** wrote:
+
+Change 172174 merged by jenkins-bot:
+Match 'color' rules to 'background-color' rules for accessibility
+
+https://gerrit.wikimedia.org/r/172174",1415612177,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,"(In reply to etonkovidova from comment #1)
+> Is it duplicate to 72192? 
+
+It's not a duplicate of bug 72192, but it's the same issue. The codebases are unfortunately still separate.",1415567523,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,"**gerritadmin** wrote:
+
+Change 172174 had a related patch set uploaded by Bartosz Dziewoński:
+Match 'color' rules to 'background-color' rules for accessibility
+
+https://gerrit.wikimedia.org/r/172174",1415567453,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,I'll look into this.,1415410462,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+OOjs UI: Unreadable input box text with dark colour schemes,"Is it duplicate to 72192? 
+
+Tried it with Chrome(Mac) and with 'Cite web' template - it's not reproducible.",1415401708,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-kjvvoq653qna4dsuzabo,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,"Steps to reproduce:
+
+1.  Open a page in Firefox (v. 32.0.3 on Mac 10.8.5) that contains several refs in a row:  [1][2][3][4].
+
+2.  Decide that refs 1, 2, and 3 are inappropriate.  Place cursor between refs 3 and 4.
+
+3.  Press shift + back arrow to start selecting the refs.
+
+
+Results:
+
+Press shift + left arrow once:  [3] is highlighted.  Press it again (i.e., to extend the selection to include [2]):  [3] is no longer highlighted.  Press it again:  [3] is highlighted again.  
+
+Repeat cycle of select-deselect as long as you would like.
+
+
+Workaround:
+
+Place cursor before ref [1], and select the three refs by pressing shift + forward arrow.
+
+
+I cannot reproduce this in Safari 6.1.2.  I haven't tested it in a LTR (left-to-right) language.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1414787400,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-xmktwdgi2pttbrlspf73,task_description,resolved
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,Verified the fix in production(in FF) - backward selection(highlighting) works smoothly and no js errors are displayed.,1416426666,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,The fix is confirmed in test2 and betalabs.,1415235623,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,"Change 170697 merged by jenkins-bot:
+Catch backwards selection error in Firefox
+
+https://gerrit.wikimedia.org/r/170697",1415040198,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,"Change 170697 had a related patch set uploaded by Esanders:
+Catch backwards selection error in Firefox
+
+https://gerrit.wikimedia.org/r/170697",1415023482,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox,"Confirmed in FF  test2: cannot select a group of reference with Shift+left arrow(highlighting nackward) - NS_ERROR_FAILURE is displayed.
+
+This is perfectly functioning in Chrome - a group of references can be selected with Shift+right arrow and back wards.",1414794323,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-xmktwdgi2pttbrlspf73,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"Screenshot
+
+Steps to reproduce:
+
+1.Insert a table
+2.Insert an empty caption to the table
+3.Save the page
+4.Now select any cell in the table
+
+Observe that,the column editing icon at the top of the empty space which looks odd 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15173}",1414784820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_description,resolved
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,Verified the fix in production,1416445927,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,Verified the fix in Betalabs and test2,1416265420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"**gerritadmin** wrote:
+
+Change 172225 merged by jenkins-bot:
+Position the table context relative to the first section node
+
+https://gerrit.wikimedia.org/r/172225",1415648045,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"**gerritadmin** wrote:
+
+Change 172191 abandoned by Bartosz Dziewoński:
+TableNode: Position row/column overlays better when caption is present
+
+Reason:
+Superseded by I3d790d71
+
+https://gerrit.wikimedia.org/r/172191",1415631406,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"**gerritadmin** wrote:
+
+Change 172225 had a related patch set uploaded by Esanders:
+Position the table context relative to the first section node
+
+https://gerrit.wikimedia.org/r/172225",1415623133,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"(In reply to Bartosz Dziewoński from comment #2)
+> To the unfortunate soul tasked with resolving this
+
+Nevermind, it was fun.",1415587110,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"**gerritadmin** wrote:
+
+Change 172191 had a related patch set uploaded by Bartosz Dziewoński:
+TableNode, TableContext: Position row/column overlays better when caption is present
+
+https://gerrit.wikimedia.org/r/172191",1415587016,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"To the unfortunate soul tasked with resolving this: there exists a CSS
+'caption-side' property, which allows the caption to be placed on every of the four usual sides (at least on Firefox, Chrome only supports 'top' and 'bottom'). (It is also supposed to accept a number of other unorthodox values, but it seems no one cares much about those.)",1415584893,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd,"(In reply to Rummana Yasmeen from comment #0)
+> 3.Save the page
+> 4.Now select any cell in the table
+
+Not necessary, this is immediately visible when you add the empty caption and move selection back to a table cell.",1415581775,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-v6lbymq7s3dov27etrxo,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,"Screenshot in Betalabs
+
+Compare the screenshots taken from Betalabs and test2 for the Page Settings tab and see how they are all cramped in Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F15065}",1414705140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_description,resolved
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,Verified the fix in production,1415833384,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,Verified the fix in test2,1415228918,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,Verified the fix in Betalabs,1415060464,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,"Change 170789 merged by jenkins-bot:
+Followup d3367bb: make FieldsetLayout <label>s display: block;
+
+https://gerrit.wikimedia.org/r/170789",1415047423,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,"Change 170789 had a related patch set uploaded by Catrope:
+Followup d3367bb: make FieldsetLayout <label>s display: block;
+
+https://gerrit.wikimedia.org/r/170789",1415047132,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped,"Created attachment 16970
+Screenshot in test2
+
+**Attached**: {F15066}",1414705217,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hwrlm3m5llfqtt2m3frc,task_subcomment,NA
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Type a template name in the textbox
+4.Now click on the ""Show Options"" button without selecting anything from the dropdown and closing it
+
+Observed Result:
+The drop down for search results stays in the dialog in the middle of the left panel and add template panel
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15056}",1414704060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-re6vwytcthwmzpbqbfoy,task_description,resolved
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown",Verified the fix in production,1415834939,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-re6vwytcthwmzpbqbfoy,task_subcomment,NA
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown",Verified the fix in Betalabs and test2,1415061702,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-re6vwytcthwmzpbqbfoy,task_subcomment,NA
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown","**gerritadmin** wrote:
+
+Change 170280 merged by jenkins-bot:
+MWTransclusionDialog: Blur active input when switching modes
+
+https://gerrit.wikimedia.org/r/170280",1414796126,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-re6vwytcthwmzpbqbfoy,task_subcomment,NA
+"VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on ""Show Options"" button without closing the dropdown","**gerritadmin** wrote:
+
+Change 170280 had a related patch set uploaded by Catrope:
+MWTransclusionDialog: Blur active input when switching modes
+
+https://gerrit.wikimedia.org/r/170280",1414725289,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-re6vwytcthwmzpbqbfoy,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Basic References or References list dialog
+3.Place cursor inside the ""Use this group"" combo box
+
+
+Observed Result:
+The group names for reference list are appearing in a short form
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15039}",1414701480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xnyble5ko7cj77odceh5,task_description,resolved
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Verified the fix in production,1415833112,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Verified the fix in test2,1415228995,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Verified the fix in Betalabs,1415060041,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","**gerritadmin** wrote:
+
+Change 170784 merged by jenkins-bot:
+MWReferenceGroupInputWidget: Remove dummy call to onInputChange()
+
+https://gerrit.wikimedia.org/r/170784",1415052587,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","(In reply to Gerrit Notification Bot from comment #6)
+> Change 170784 had a related patch set uploaded by Catrope:
+> MWReferenceGroupInputWidget: Remove dummy call to onInputChange()
+> 
+> https://gerrit.wikimedia.org/r/170784
+
+This patch doesn't look like it fixes this bug?",1415048514,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","**gerritadmin** wrote:
+
+Change 170784 had a related patch set uploaded by Catrope:
+MWReferenceGroupInputWidget: Remove dummy call to onInputChange()
+
+https://gerrit.wikimedia.org/r/170784",1415046188,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session","(In reply to Elitre from comment #4)
+> (Is this different from Bug 72785?)
+
+Yes. That's about the height of the box, this is about the width of the text.",1415030641,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",(Is this different from Bug 72785?),1415002692,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Confirmed that this is a regression from https://gerrit.wikimedia.org/r/#/c/169968/,1414778255,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",Trevor says it's probably caused by the menu being shown too early.,1414777850,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The group names inside ""Use this group"" field are appearing in a short form like ""g..."" for both ""References list"" and ""Basic Reference"" dialog when you open these dialogs first time in a session",James thinks this may be a regression from https://gerrit.wikimedia.org/r/#/c/169968/,1414777686,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xnyble5ko7cj77odceh5,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"Please.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1414624320,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_description,resolved
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,Slugs are now inserted with buttons which are ce=true,1433773199,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"(In reply to Ed Sanders from comment #3)
+> *sigh* Chrome doesn't even let you set such a selection programmatically, so
+> it appears book-ending is required. Although I'd like to do programmatic
+> handling too to catch things like table and focusable node selections (where
+> the native selection is in the paste target).
+
+So… gerrit 172039 didn't fix this. Is it do-able?",1416257031,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"*sigh* Chrome doesn't even let you set such a selection programmatically, so it appears book-ending is required. Although I'd like to do programmatic handling too to catch things like table and focusable node selections (where the native selection is in the paste target).",1414702058,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"Solutions:
+
+1. Book-end the document with selectable but invisible content. Have to make sure this doesn't break ve.ce.getOffset.
+
+2. Register CTRL+A as a trigger and do it programmatically.
+
+
+Further complicating the issue is CE true inside CE false inside CE true, as is the case with table cell editing. In this case CTRL+A should only select the cell contents, so any programmatic solution would have to be aware of that, and any book-end solution would have to work in these ""sub-surfaces"" as well.",1414686261,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome,"Chromium bug, has been around for a year, but maybe we've made it more common by having ce=false slugs?
+
+https://code.google.com/p/chromium/issues/detail?id=322444
+
+http://jsfiddle.net/edg2s/afhq6ef0/",1414685832,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-dunm4q3cjegrnqlbrlnx,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Convert several MW core special pages to OOUI as a demonstration that it's possible now.
+
+Part of ""front-end standardisation"" Q2 priority project.",1414621860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_description,resolved
+Convert some MW core special pages to OOUI,For further work see T107037.,1446661792,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"I think this task, as written (""Convert some MW core special pages to OOUI""), is sufficiently resolved. We have converted some special pages, and then some more (although most of the relevant commits weren't linked to this bug).
+
+Quick tally:
+
+* Special:ChangeContentModel (fa31bf1675af7255431aeffd9757066e0ce572e2)
+* Special:ChangeEmail (b51076a84446d157bed511246450e70d26e0f945)
+* Special:LinkSearch (5bd98dacfaaf08e9645fdb215a6e18e9d7f80c04)
+* Special:PageLanguage (b51076a84446d157bed511246450e70d26e0f945)
+* Special:PasswordReset (b51076a84446d157bed511246450e70d26e0f945)
+* Special:ResetTokens (2550de9552230585e33b45f37cada0f13e396953)
+
+Several more are in progress or waiting for reviews.
+",1437833883,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"> Are you going to Cc a designer to review? E.g. the label was intended to sit closer to the field underneath, which is still the case on login form.
+
+I don't know who would review these, or if there's anyone willing to at all? If anyone has any feedback to offer, we'll be happy to hear it. Just note that this is the same interface as used in VisualEditor's dialogs and any changes should fit both use cases.
+
+There is about twice as much spacing between the label and widget in OOUI-styled forms than in the old ones, but the widgets are also about twice as big. I agree that the OOUI style might be a bit too whitespacey, though.
+
+> vform stood for ""vertically-stacked form"", everything was intended to be the same width. It was a $displayFormat different from the existing div, table, and raw which also used mediawiki.ui styles. I think clients should be able to request buttons styled as OOUI without getting the vform layout e.g. OOUI buttons in 'table' display format.
+
+It should be possible to use OOUI widgets for existing forms, let's just be cautious about this to avoid breaking interfaces. OOUI integrates seamlessly with HTML, so you can just replace, say, `Html::input( $name, $value, 'submit' )` with `new OOUI\ButtonInputWidget( array( 'name' => $name, 'value' => $value, 'type' => 'submit' ) )`. We could do the same in `HTMLFormField` subclasses, possibly controlled by some config, if anyone desires. I'm not sure how useful this would be in general, though.
+
+The various display formats of HTMLForm are terribly confused, eh. I think a better naming would be 'horizontal' instead of 'table' and 'vertical' instead of 'div', since that's basically what these two result with. 'vform' would then be 'vertical-mediawikiui' and 'ooui' would be 'vertical-oui'. But this is probably not worth doing.
+
+While we're using a vertical layout in OOUI HTMLForm, and while this is the generally recommended layout for OOUI forms, we do sort of kind of support a more horizontal one too – you can it by setting `align: 'left'` rather than `align: 'top'` for individual FieldLayouts. It doesn't exactly behave like 'table' HTMLForm, though, especially for individual checkboxes/toggles. It looks like this: {F175554}
+
+> When you specify 'vform' as displayFormat, the form width needs to be constrained. (Picking a width for vform was challenging, it ended up being determined by the width of the restyled FancyCaptcha on the login form.).
+
+OOUI form widgets' widths are generally limited to 50em (~600px, depending on the skin) for sanity (to avoid input fields stretching across the whole width of 4k display, for example), but this isn't a hard limit.",1433597091,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"This is excellent!
+
+Are you going to Cc a designer to review? E.g. the label was intended to sit closer to the field underneath, which is still the case on [[ https://en.wikipedia.org/wiki/Special:UserLogin | login form ]].
+
+> These pages were previously using the ""VForm"" style and switching them over to the new ""OOUI"" style
+vform stood for ""vertically-stacked form"", everything was intended to be the same width.  It was a `$displayFormat` different from the existing div, table, and raw which also used mediawiki.ui styles. I think clients should be able to request  buttons styled as OOUI without getting the vform layout e.g. OOUI buttons in 'table' display format.
+
+When you specify 'vform' as displayFormat, the form width needs to be constrained. (Picking a width for vform was challenging, it ended up being determined by the width of the restyled FancyCaptcha on the login form.).",1433469430,PHID-USER-gbl4hfak3cfurt3c7skd,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Change 208285 had a related patch set uploaded (by Mattflaschen):
+[WIP] Switch some HTMLForms in special pages to OOUI
+
+[[https://gerrit.wikimedia.org/r/208285]]
+",1433464615,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Change 208285 had a related patch set uploaded (by Jforrester):
+[WIP] Switch some HTMLForms in special pages to OOUI
+
+[[https://gerrit.wikimedia.org/r/208285]]
+",1432556477,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Also, once the value is changed, we can take out some of the weird special-casing in forms that use OOUI or mwui in part - BetaFeatures comes to mind immediately (so Special:Preferences in general), but OAuth and many other core forms will benefit.",1431441992,PHID-USER-nvavrb7ko66hv3xap6sb,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Here are some screenshots of the ""first iteration"", brought to you by @marktraceur's work on T85291. These pages were previously using the ""VForm"" style and switching them over to the new ""OOUI"" style, once implemented, is a matter of changing a single value.
+
+# Special: ChangeEmail
+| VForm | OOUI |
+| -- | -- |
+| {F163967,height=240} | {F163969,height=260} |
+
+# Special: ResetPassword
+| VForm | OOUI |
+| -- | -- |
+| {F163952,height=250} | {F163954,height=250} |
+
+Issues:
+* The help icon looks slightly blurry, this will be fixed after T97631.
+* The checkbox is smaller, this is a design decision being discussed on T86003.
+
+# Special: PageLanguage
+| VForm | OOUI |
+| -- | -- |
+| {F163958,height=170} | {F163960,height=180} |
+
+Issues:
+* The extremely long dropdown list with languages has usability issues, most importantly T91126.
+* Radio buttons are not OOUI-like yet, we're working on this on T98855.
+",1431442191,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Here are some screenshots of the ""first iteration"", brought to you by @marktraceur's work on T85291. These pages were previously using the ""VForm"" style and switching them over to the new ""OOUI"" style, once implemented, is a matter of changing a single value.
+
+# Special: ChangeEmail
+| VForm | OOUI |
+| -- | -- |
+| {F163967,height=240} | {F163969,height=260} |
+
+# Special: ResetPassword
+| VForm | OOUI |
+| -- | -- |
+| {F163952,height=250} | {F163954,height=250} |
+
+Issues:
+* The help icon looks slightly blurry, this will be fixed after T97631.
+* The checkbox is smaller, this is a design decision being discussed on T86003.
+
+# Special: PageLanguage
+| VForm | OOUI |
+| -- | -- |
+| {F163958,height=170} | {F163960,height=180} |
+
+Issues:
+* The extremely long dropdown list with languages has usability issues, most importantly T91126.
+* Radio buttons are not OOUI-like yet, we're working on this on T91126.
+",1431441796,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"Change 208285 had a related patch set uploaded (by Bartosz Dziewoński):
+[WIP] Switch some HTMLForms in special pages to OOUI
+
+[[https://gerrit.wikimedia.org/r/208285]]
+",1431439690,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+Convert some MW core special pages to OOUI,"This would be a lot less unpleasant if somebody did T19312, or maybe even T12317, first.",1419440091,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-7fjtjpvxdar4zf4p2zn5,task_subcomment,NA
+"VisualEditor: When applying the <pre> formatting to multiple paragraphs, make them instead a single <pre> with newlines between the paragraphs","I was wondering if we could have a feature whereby multiline selected text could be enveloped in one <pre> or <code> when the corresponding heading level or text formatting option is clicked from the toolbar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414619520,PHID-USER-srhlj2447vmpmrfhqnfa,False,PHID-TASK-a2u5v6wtvnxub3uml7uz,task_description,open
+"VisualEditor: When applying the <pre> formatting to multiple paragraphs, make them instead a single <pre> with newlines between the paragraphs","Ignore the ""Viewing Profile Info"" part. It could be any section :)",1414685721,PHID-USER-srhlj2447vmpmrfhqnfa,False,PHID-TASK-a2u5v6wtvnxub3uml7uz,task_subcomment,NA
+"VisualEditor: When applying the <pre> formatting to multiple paragraphs, make them instead a single <pre> with newlines between the paragraphs","Suppose one visits an article using Google Chrome for Mac OS. After selecting two consecutive paragraphs in the ""Viewing Profile Info"" section, then choosing either ""Preformatted"" from the heading level dropdown, or ""{ } Computer code"" from the text formatting popover ""pane"", two <code> or two <pre> sections are created, not one. Furthermore, if one starts a new stanza with ""Preformatted"" or ""{ } Computer code"" heading level / formatting, upon pressing the Enter key (as well as Command+Enter for the typical non-terminating line break in Mac OS or Shift+Enter), the editing context switches out of <pre> or <code> mode.",1414685696,PHID-USER-srhlj2447vmpmrfhqnfa,False,PHID-TASK-a2u5v6wtvnxub3uml7uz,task_subcomment,NA
+"VisualEditor: When applying the <pre> formatting to multiple paragraphs, make them instead a single <pre> with newlines between the paragraphs","(If I select multiple lines, I'm able to wrap them in code tags using the corresponding option in the toolbar. How is this different from your request?)",1414670124,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-a2u5v6wtvnxub3uml7uz,task_subcomment,NA
+VisualEditor: [Regression wmf6] deleting text formatted as computer code produces: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.) in Safari,"Found in Safari test2.
+
+1. In VE type some text(spanned several lines), highlight it and apply computer code formatting option. 
+
+2. Delete one line of code - Console shows: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414614240,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-cf7sodft5apnwjetm2ek,task_description,open
+VisualEditor: [Regression wmf6] deleting text formatted as computer code produces: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.) in Safari,This sounds… odd.,1414623296,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cf7sodft5apnwjetm2ek,task_subcomment,NA
+VisualEditor: [Regression wmf6] deleting text formatted as computer code produces: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.) in Safari,"Actually, the console error: ""Failed to load resource: The operation..."" shows for all formatting options - underline, bold, strikethrough etc
+
+The error is displayed when the previously formatted chunk of text is deleted.",1414614535,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-cf7sodft5apnwjetm2ek,task_subcomment,NA
+VisualEditor: Edit notices popup shows out of screen in RTL,"a screenshot with the problem
+
+To reproduce, edit an old version of a Hebrew Wikipedia article, e.g.:
+https://he.wikipedia.org/w/index.php?title=ASCII&oldid=15904477&veaction=edit
+
+The popup with the edit notice about editing an old version appears immediately. It's misaligned and shown mostly out of screen.
+
+See the screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14738}",1414586280,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-67cctylbfobidrbv3hfd,task_description,resolved
+VisualEditor: Edit notices popup shows out of screen in RTL,Attached is a screenshot from betalabs -Page settings menu box  still overflows. The browser window was  Maximized.,1414799613,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-67cctylbfobidrbv3hfd,task_subcomment,NA
+VisualEditor: Edit notices popup shows out of screen in RTL,"Created attachment 16988
+Page settings menu overflow
+
+**Attached**: {F14739}",1414799516,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-67cctylbfobidrbv3hfd,task_subcomment,NA
+VisualEditor: Edit notices popup shows out of screen in RTL,This was fixed in wmf5 by Roan.,1414623664,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-67cctylbfobidrbv3hfd,task_subcomment,NA
+VisualEditor: Edit notices popup shows out of screen in RTL,"Confirmed on https://he.wikipedia.org/w/index.php?title=ASCII&oldid=15904477&veaction=edit 
+
+Both 'Page options' and 'Help' boxes are cut off.",1414600629,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-67cctylbfobidrbv3hfd,task_subcomment,NA
+VisualEditor: Content menu is embedding off-screen for left-floated node in RTL environment,"To reproduce:
+
+1. Edit the Hebrew Wikipedia article about Haifa:
+https://he.wikipedia.org/wiki/%D7%97%D7%99%D7%A4%D7%94?veaction=edit
+
+2. Click the infobox on top left.
+
+Observed: The pop-up puzzle bubble for editing the template appears to the left of the infobox, goes off-screen and creates a horizontal scroll-bar.
+
+Expected: The pop-up puzzle bubble must appear in a visible convenient place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414580160,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-tihohw65um5nqiof2m35,task_description,resolved
+VisualEditor: Content menu is embedding off-screen for left-floated node in RTL environment,Checked in beta/test2/production  including the page https://he.wikipedia.org/wiki/%D7%97%D7%99%D7%A4%D7%94?veaction=edit  - all look good to me too. ,1419733251,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-tihohw65um5nqiof2m35,task_subcomment,NA
+VisualEditor: Content menu is embedding off-screen for left-floated node in RTL environment,Looks good to me now. Not sure when it was fixed.,1419722431,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-tihohw65um5nqiof2m35,task_subcomment,NA
+VisualEditor: Content menu is embedding off-screen for left-floated node in RTL environment,"Did we fix this in master? It looks ""fine"" (different breakage) on http://he.wikipedia.beta.wmflabs.org/wiki/%D7%95%D7%99%D7%A7%D7%98%D7%95%D7%A8_%D7%9B%D7%A8%D7%99%D7%A1%D7%98%D7%A0%D7%A7%D7%95?veaction=edit&uselang=he",1414609808,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tihohw65um5nqiof2m35,task_subcomment,NA
+VisualEditor: [Regression] Clicking on an image with wikilink opens up link inspector,"screenshot
+
+Environment- test2
+
+1> In a blank page insert an image with a wikilink as caption.
+2> Now click on the image in the main editor. Notice in the context menu,  along with the name of the image now the link also appears.
+3> click on the context menu and it opens the link inspector for you populated with the target.
+
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15374}",1414558140,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-scoh4xqxum72mhxquk27,task_description,open
+VisualEditor: [Regression] Clicking on an image with wikilink opens up link inspector,Confirmed that the bug exists in betalabs and test2.,1414605250,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-scoh4xqxum72mhxquk27,task_subcomment,NA
+VisualEditor: [Regression] Clicking on an image with wikilink opens up link inspector,"(In reply to Ritu Swain from comment #1)
+> Also see 72431.
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72431",1414558240,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-scoh4xqxum72mhxquk27,task_subcomment,NA
+VisualEditor: [Regression] Clicking on an image with wikilink opens up link inspector,Also see 72431.,1414558213,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-scoh4xqxum72mhxquk27,task_subcomment,NA
+VisualEditor: Be able to serialise the linear model,For things like auto-save (T57370) and collaboration.,1414551060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qsgnrw34off5kbfx52lz,task_description,resolved
+VisualEditor: Be able to serialise the linear model,"Change 231017 merged by jenkins-bot:
+Provide methods to (de)serialize transactions
+
+[[https://gerrit.wikimedia.org/r/231017]]",1472060773,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qsgnrw34off5kbfx52lz,task_subcomment,NA
+VisualEditor: Be able to serialise the linear model,"Change 231017 had a related patch set uploaded (by Esanders):
+Provide methods to (de)serialize transactions
+
+[[https://gerrit.wikimedia.org/r/231017]]
+",1439477911,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qsgnrw34off5kbfx52lz,task_subcomment,NA
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,"IE11 transparency flaws
+
+Steps to reproduce: 
+
+
+1. Open any page in VE on IE11(test2). 
+
+2. Click on 'Page option' icon and select 'Options'
+
+3. Options-Advanced settings have three small info icons - click on each of them - the box becomes transparent(look at the attched screenshot). There is also a screenshot of how it behaves in Chrome, for comparison. 
+
+Another way to reproduce the bug - when in Step 3 you click on the first info icon, open another browser tab, go and return back - the box for Options will become transparent.  
+
+Note: does not happen with Insert-Template(a template should have one info icon).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15339}",1414526520,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_description,resolved
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,Also can't reproduce. Please re-open if it re-occurs.,1460644121,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_subcomment,NA
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,"Cannot reproduce on beta with IE11... @Etonkovidova, is this still an issue for you?",1421201256,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_subcomment,NA
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,The dialog box 'Are you sure?' which appears when switching from Edit mode to Read is transparent too.,1414529408,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_subcomment,NA
+VisualEditor: Some dialogs are showing with transparent backgrounds in IE11,"Created attachment 16934
+Chrome shows correct transparency - to compare
+
+**Attached**: {F15341}",1414526648,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ssmxrwedkkwjcdz3pkfv,task_subcomment,NA
+OOjs UI: [Regression] Menu width isn't working in IE11 any more – see VisualEditor's 'Page options' drop down menu,"Page options drop down horizontal scroll bar
+
+Steps to reproduce: 
+
+1. In IE 11 in full screen- open any page for edit in VE.
+2. Click on Page option icon - the drop down menu options will be displayed partially and a horizontal window scroll bar will be displayed.
+
+{F15330}
+
+--------------------------
+**See Also**:
+{T74592}",1414523340,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-z7lqudiqsx3toqxfmyrh,task_description,resolved
+OOjs UI: [Regression] Menu width isn't working in IE11 any more – see VisualEditor's 'Page options' drop down menu,"This is caused by some IE bugs with `display: inline-table`. Applying the set of patches from T78499, which gets rid of it, fixes the issue.",1418584468,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-z7lqudiqsx3toqxfmyrh,task_subcomment,NA
+OOjs UI: [Regression] Menu width isn't working in IE11 any more – see VisualEditor's 'Page options' drop down menu,"Probably the same bug as bug 72592, but leaving distinct for now.",1415884633,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z7lqudiqsx3toqxfmyrh,task_subcomment,NA
+OOjs UI: [Regression] Menu width isn't working in IE11 any more – see VisualEditor's 'Page options' drop down menu,"As it was described in 56713 - the bug ""alternates""  i.e. 
+
+IE11 test2: Open a page in VE and click on the 'Page options' icon - the drop-down menu options are partially displayed. Then switch to 'Maximize' browser view(or if you were in  'Restore down', switch to 'Maximize'), the menu options will be displayed in full.",1414524734,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-z7lqudiqsx3toqxfmyrh,task_subcomment,NA
+VisualEditor: Text in Japanese disappears,"First reported by miya at ja.wp:
+write something in Japanese; press Enter; the whole line disappears. This also happens when adding a picture - in the Caption field.
+This does not seem to be browser or OS-specific.
+miya says that adding a ""single-byte character"" or a number at the beginning of the line, the line doesn't disappear - I don't seem able to confirm this (my tests are in Safari/X Yosemite).
+I'm able to reproduce the general issue at mediawiki.org (using the laptop input system for Katakana; hope I'm doing this right).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72508",1414497360,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-setrj27w67t7gktol4z3,task_description,resolved
+VisualEditor: Text in Japanese disappears,"As far as I can tell, this issue and other Japanese text entry issues are all now fixed. Sorry it took so long to confirm!
+
+>>! In T74619#977974, @Yukichi99 wrote:
+> Why did you change the priority?
+> I recognize this bug is blocked against using by Japanese.
+> If you have a reason, let me know.
+
+Sorry, this was done in a mass action for everything we were not working on that month.",1435941327,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-setrj27w67t7gktol4z3,task_subcomment,NA
+VisualEditor: Text in Japanese disappears,"Why did you change the priority?
+I recognize this bug is blocked against using by Japanese.
+If you have a reason, let me know.",1421280936,PHID-USER-6b5wxetq6egh6g7rvdjd,True,PHID-TASK-setrj27w67t7gktol4z3,task_subcomment,NA
+VisualEditor: Text in Japanese disappears,"Thanks for changing its priority!
+
+For your information, I tried the above case with Google Input method and Google chrome on Mac OS X Yosemite, got the same result. 
+
+Let me know if you need other test cases.",1418266930,PHID-USER-6b5wxetq6egh6g7rvdjd,True,PHID-TASK-setrj27w67t7gktol4z3,task_subcomment,NA
+VisualEditor: Text in Japanese disappears,"Confirmed in betalabs with hirogana, katakana(and, of course, not for romaji), and kanji. 
+
+Sometime it takes two hit of Enter to delete the entered text in such languages- but the text gets deleted. For English text, 'Enter' behaves normally  - a cursor goes to the new line.",1414804224,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-setrj27w67t7gktol4z3,task_subcomment,NA
+"VisualEditor Mobile: When the context menu appears in mobile, the button alignment for ""Next"" and ""Page Settings"" option at the top right gets a bit lower","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Select a link or a citation so that the context menu for it appears on the top
+
+Observed Result:
+When the context menu appears observe the positions of the buttons at the left-""Save"" and ""Settings"" icon also gets changed to a much lower position , they should be fixed while the context menu opens at the bottom of the menu bar
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15145}",1414436160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-au5g35tuuylapsk7eubl,task_description,resolved
+"VisualEditor Mobile: When the context menu appears in mobile, the button alignment for ""Next"" and ""Page Settings"" option at the top right gets a bit lower",Needs re-testing.,1430336288,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-au5g35tuuylapsk7eubl,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,"I just tested the feature
+https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2014-October/000991.html
+with VisualEditor and it seems to be using a low resolution image instead of MathMl (while editing). When I save the page,
+https://pt.wikipedia.org/w/index.php?diff=40380507
+the formula disappears and it only reappear after I reload the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414357320,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-qetvgvrqjisxdxa4u7np,task_description,resolved
+VisualEditor: Math rendering 2.0 does not work in edit mode,Verified in production  - used the sample from https://pt.wikipedia.org/w/index.php?diff=40380507: \frac{\sqrt{(x+1)}}{y^2} ,1417045436,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,"Verified the fix in test2
+
+- resolution of an edited/inserted formula in VE is the same as after saving the page
+
+- <meta name=""generator"" content=""MediaWiki 1.25wmf8""> is present",1415909541,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,"**gerritadmin** wrote:
+
+Change 172775 merged by jenkins-bot:
+Allow <meta> tags in GeneratedContentNodes
+
+https://gerrit.wikimedia.org/r/172775",1415821938,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,"**gerritadmin** wrote:
+
+Change 172775 had a related patch set uploaded by Esanders:
+Allow <meta> tags in GeneratedContentNodes
+
+https://gerrit.wikimedia.org/r/172775",1415815050,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: Math rendering 2.0 does not work in edit mode,Isn't this what gerrit 130828 was for?,1414625185,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qetvgvrqjisxdxa4u7np,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"Environment:
+Ubuntu 14.04.1 LTS
+IBus 1.5.5
+mozc 1.13.1651.102-2
+
+Test sequence:
+0. Open a blank page with VisualEditor.
+1. Switch to Japanese input.
+2. Enter ""nihongo"".
+3. Convert it (usually by pushing down the space key). You'll see it converted ""日本語"" here.
+4. Disable Japanese input.
+5. Enter ""a"". You'll see here ""日本語"" removed and only ""a"" remaining.
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72619",1414234140,PHID-USER-meyjnh7zdarfb7u7upzo,False,PHID-TASK-32waecquxrqyav4wai64,task_description,resolved
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"As far as I can tell, this issue and other Japanese text entry issues are all now fixed. Sorry it took so long to confirm!
+
+>>! In T74508#1014577, @whym wrote:
+> @Jdforrester-WMF: do you have any idea which change fixed it? We'd want to link it here, if possible.
+> 
+> Anyway, I think it's safe to close this task as resolved already.
+
+Sadly we've done dozens of changes to the typing support system in the past few years to fix this issue and ones like it, and we only added systematic tests for Japanese typing support this week, which helped us confirm that it was working as expected.",1435941596,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"@Jdforrester-WMF: do you have any idea which change fixed it? We'd want to link it here, if possible.
+
+Anyway, I think it's safe to close this task as resolved already.",1423061060,PHID-USER-meyjnh7zdarfb7u7upzo,False,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"Unsure of what changed, but I'm not experiencing this problem now on MediaWiki.org anymore.",1419134889,PHID-USER-meyjnh7zdarfb7u7upzo,False,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"Changed to critical as it involves loss of data, and affects significantly many (effectively all trials of editing in Japanese).",1416107856,PHID-USER-meyjnh7zdarfb7u7upzo,False,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,the similar issue is bug 72619.,1415296033,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"I first experienced the same bug around 2014-10-24.
+Environment:Windows 7　PC （Firefox 33.0.1,　Chrome 38.0.2125.104 m, IE 11.0.13）
+
+Test sequence 1: 
+0 - 5. All the same as Yusuke Matsubara's.
+(note: you cant move the cursor with right or left key on ""日本語"")
+
+Test sequence 2: 
+0 - 4. same as Yusuke Matsubara's.
+5. Push ""Enter key"" to make a br there. You'll see here ""日本語"" vanished and nothing remaining. 
+(It drove me panicky at first: I couldnt even copy the Japanese text there to　salvage. )
+
+Test sequence 3:
+0. Open a blank page with VisualEditor.
+1-1. Enter ""1"" (or any alphabet, any number or any sign like ""@"", ""#"", ""*"", ""^"", ...).   
+1-2. Switch to Japanese input.
+2. Enter ""nihongo"" after ""1"".
+3. Convert it (usually by pushing down the space key). You'll see it converted ""日本語"" - you'll see here ""1 日本語"" 
+4. Disable Japanese input.
+5. Enter ""a"". You'll see here ""1 日本語 a"" remaining.",1415262576,PHID-USER-uy4w45ngb7c554efp3rq,False,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input,"Above was tested browsers below:
+Mozilla Firefox 33.0
+Chromium Version 37.0.2062.120 Ubuntu 14.04 (281580) (64-bit)",1414237159,PHID-USER-meyjnh7zdarfb7u7upzo,False,PHID-TASK-32waecquxrqyav4wai64,task_subcomment,NA
+"VisualEditor: Clicking on somewhere else in the document after opening a link inspector inside a slug throws error ""TypeError: Cannot read property 'previousSibling' of undefined""","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a bullet list
+3.Add some indentation 
+4.Now click on any slug that got created due to indentation
+5.Open a link inspector on that position
+6.While the link inspector is open, click somewhere else in the document to close the inspector
+
+Observed Result:
+The link inspector stays opened in that position and there is an error in the console:
+TypeError: Cannot read property 'previousSibling' of undefined
+
+See the screenshot attached
+
+Environment:Betalabs,test2 and en.wiki
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72558
+
+**Attached**: {F14916}",1414183680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2ik4qr5eikvbxsyx7ihu,task_description,resolved
+"VisualEditor: Clicking on somewhere else in the document after opening a link inspector inside a slug throws error ""TypeError: Cannot read property 'previousSibling' of undefined""","Change 190022 merged by jenkins-bot:
+Simplify slug behaviour
+
+[[https://gerrit.wikimedia.org/r/190022]]",1424725247,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2ik4qr5eikvbxsyx7ihu,task_subcomment,NA
+"VisualEditor: Clicking on somewhere else in the document after opening a link inspector inside a slug throws error ""TypeError: Cannot read property 'previousSibling' of undefined""","Change 190022 had a related patch set uploaded (by Esanders):
+Simplify slug behaviour
+
+[[https://gerrit.wikimedia.org/r/190022]]
+
+#patch-for-review",1423756455,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2ik4qr5eikvbxsyx7ihu,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Search for any image and select one 
+
+Observed Result:
+As soon as you select any image and the Media Settings dialog appears,the following error appears in the console
+
+Uncaught TypeError: Cannot read property 'isDefault' of undefined
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14910}",1414181520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_description,resolved
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image",Verified the fix in production,1415226630,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image",Verified the fix in Betalabs,1414433153,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image","**gerritadmin** wrote:
+
+Change 168675 merged by jenkins-bot:
+Make sure initialHash exists before checking its value
+
+https://gerrit.wikimedia.org/r/168675",1414380313,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf6] ""TypeError: Cannot read property 'isDefault' of undefined"" appears when Media Settings dialog appears while adding a new image","**gerritadmin** wrote:
+
+Change 168675 had a related patch set uploaded by Mooeypoo:
+Make sure initialHash exists before checking its value
+
+https://gerrit.wikimedia.org/r/168675",1414182012,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oxbr6v2mpytzioyqp4ma,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"There are different controls for the Cache-Control headers for the API and MediaWiki's OutputPage.  This may have seemed innocuous in the past, but it is causing problems now that VisualEditor is moving page editing to the API.
+
+On my local wiki pages are served with:
+
+  Cache-Control: private, must-revalidate, max-age=0
+
+and, when mCacheMode is set to 'private', the default, API responses are sent with:
+
+  Cache-Control: private
+
+[[ http://www.ietf.org/rfc/rfc2616.txt | RFC 2616 ]] says:
+
+  private
+      Indicates that all or part of the response message is intended for
+      a single user ... A private (non-shared) cache MAY cache the response.
+
+and:
+
+   A cache MAY be configured to return stale responses without
+   validation, but only if this does not conflict with any ""MUST""-level
+   requirements concerning cache validation (e.g., a ""must-revalidate""
+   cache-control directive).
+
+and:
+
+   If a cache receives a 5xx response while attempting to revalidate an
+   entry, it MAY either forward this response to the requesting client,
+   or act as if the server failed to respond. In the latter case, it MAY
+   return a previously received response unless the cached entry
+   includes the ""must-revalidate"" cache-control directive (see section
+   14.9).
+
+**old description:**
+IE 11 seems to cache faulty parsoid responses.
+
+I had a misconfigured server and, even after I fixed the problem and other browsers were able to continue after clicking ""edit"", IE didn't even attempt to make a request but just kept showing the alert box with the error message.
+",1414164780,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_description,resolved
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,Since this was merged...,1426119916,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Change 194208 merged by jenkins-bot:
+Browser should clear cache for API responses
+
+[[https://gerrit.wikimedia.org/r/194208]]",1425574879,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Change 194208 had a related patch set uploaded (by MarkAHershberger):
+Browser should clear cache for API responses
+
+[[https://gerrit.wikimedia.org/r/194208]]
+",1425421093,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Updated description with my findings.  I think this shows that while IE's behavior may be different, it isn't out-of-spec, especially given that the urls providing the content for reading are different than the urls providing content for the VisualEditor.
+
+Patch to arrive shortly.",1425419400,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Like {T73119}, my client has specified this as an important issue.  I'm looking for information on tracking down these issues.  Any pointers? ",1419810857,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"Please don't use ""MSIE""; we normally call it ""Internet Explorer"" for clarity.",1415902721,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,"It isn't just caching errors.  It looks like it is caching all sorts of responses.  I think I've seen this in more than just IE, but I can reliably reproduce it with IE.",1415902171,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers,Not sure how we could work around browser-intentional behaviour like this…,1414625653,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jrcdwxsp3bh53xuhlofi,task_subcomment,NA
+VisualEditor: MWTitleInputWidget should return titles,"MWTitleInputWidget should have a .getTitle() getter (which can return null, if the value isn't a valid title). Using this getter should be preferred over .getValue(). Callers of MWTitleInputWidget.getValue() should be converted to .getTitle(), and they should check for null-ness, because we probably have more bugs like bug 71998 hiding in various places.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414114860,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nhmtatolxkhjgn54hngt,task_description,resolved
+VisualEditor: MWTitleInputWidget should return titles,"Change 169603 merged by jenkins-bot:
+Introducing getTitle() in MWTitleInputWidget
+
+https://gerrit.wikimedia.org/r/169603",1414606448,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nhmtatolxkhjgn54hngt,task_subcomment,NA
+VisualEditor: MWTitleInputWidget should return titles,"Change 169603 had a related patch set uploaded by SuchetaG:
+Introducing getTitle() in MWTitleInputWidget
+
+https://gerrit.wikimedia.org/r/169603",1414534602,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nhmtatolxkhjgn54hngt,task_subcomment,NA
+VisualEditor: MWTitleInputWidget should return titles,"Also, per bug 71249, now that we have isValid() in TextInputWidget, it makes sense for MWTitleInputWidget to reimplement isValid() as a check for getTitle() not being null.",1414117466,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nhmtatolxkhjgn54hngt,task_subcomment,NA
+VisualEditor: Reorganize and restrategize how Scalable information works with all existing images,"Make the API call for scalable information unified on load, and make sure the call only comes out once per image (at least) and is persistent between the image and the image model in the edit dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414088400,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-uzavsh7jiyrspclcykx3,task_description,open
+VisualEditor: Reorganize and restrategize how Scalable information works with all existing images,Unassigning myself - but I'm pretty sure this is irrelevant now after the many many refactorings done to the code?,1468967195,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-uzavsh7jiyrspclcykx3,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"inspector opens up on the left side in FF 33.0
+
+Environment- beta
+
+1> In VE, insert a media(with any settings but no content in ""Caption"") to blank page.
+
+2> Highlight the image and select link or language from the toolbar.The inspector opens and closes quickly.
+
+This happens in chrome 38 only.
+
+In FF 33.0, when you do the above steps, the inspectors do not open on top of the image.But always on the left side in the CE .See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14768}",1414082160,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-vexowcgnl3zfx2wx744e,task_description,open
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"Also see 72660, https://bugzilla.wikimedia.org/show_bug.cgi?id=72660",1414558284,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"Created attachment 16939
+Caption appearing in the link target field
+
+**Attached**: {F14769}",1414556839,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"(In reply to James Forrester from comment #2)
+> I believe that this is describing intentional functionality for links? You
+> can't make an image into a link in wikitext (there's a distinct feature
+> about image target but that's tracked elsewhere).
+> 
+> But yes, this needs to be cleaned up a bit (especially the different
+> behavior between Firefox and Chrome).
+
+I also noticed that when i try to apply link to images having caption,the link inspector opens with the caption text as link target in the input field(which i thought was fine).
+
+Environment-test2, beta, production
+steps-
+1> insert a media with a caption(could be an internal link or text).Highlight the image and select to apply link.
+2> Link inspector opens on top of the image, populated with the caption in the input field.
+3> Click done and the inspector closes.See screenshot.
+
+Is this expected?",1414556756,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"I believe that this is describing intentional functionality for links? You can't make an image into a link in wikitext (there's a distinct feature about image target but that's tracked elsewhere).
+
+But yes, this needs to be cleaned up a bit (especially the different behaviour between Firefox and Chrome).",1414441147,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox,"Now reproducible in test2.
+
+1> insert a media with no captions.Highlight the image and select to apply link or language.
+2> Link or language inpsector opens and closes quickly.",1414164069,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-vexowcgnl3zfx2wx744e,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Parsoid output has broken output because Mediawiki:common.css is not included.
+
+For example:
+http://parsoid-lb.eqiad.wikimedia.org/frwiki/Guerre_froide?oldid=108085194
+
+Here the original version:
+https://fr.wikipedia.org/w/index.php?title=Guerre_froide&oldid=108085194
+
+And with the visual editor:
+https://fr.wikipedia.org/w/index.php?title=Guerre_froide&oldid=108085194&veaction=edit
+
+Like you can see the infobox width is huge probably because there is no rule for the ""infobox_v2"" CSS class.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414054260,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_description,resolved
+"Navbox rendering incorrect, all items in the same line","Tidy is no longer around and Remex and Parsoid have the same HTML5 behavior. So, this is no longer an issue.",1592506990,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",I've just filed {T155634} which also has some spaces inserted (which may be relevant).,1484754322,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Also, see https://www.mediawiki.org/wiki/Parsing/Replacing_Tidy .. especially Sections 2.2 and 2.5 on that page.
+
+As part of T89331, we are working to replace Tidy with a proper HTML5 parser which will require wikitext fixes of the kind that @Od1n did above.",1466083632,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",Please note I have workarounded the above issue since: https://fr.wikipedia.org/w/index.php?title=Mod%C3%A8le:Portail&diff=prev&oldid=126720710,1466056889,PHID-USER-povcbbfr2b6v4te3anc7,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Same issue occurs with <li> tags.
+[[https://fr.wikipedia.org/w/index.php?title=Utilisateur:Pols12/brouillon_eve&oldid=126290496|An example]] on fr.wiki: there are a <li> per line in HTML code however all <li> tags are displayed on the same line with VisualEditor (with Template:Portail)",1463595328,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Same issue occurs with <li> tags.
+[[https://fr.wikipedia.org/w/index.php?title=Utilisateur:Pols12/brouillon_eve&oldid=126290496|An example]] on fr.wiki: there are a <li> per line in HTML code however all <li> tags are displayed on the same line with VisualEditor.",1463595253,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","We'll have to figure out what to do about this Tidy-caused discrepancy. Template edit to not depend on this Tidy effect might be the simplest. For now, moving this out of Q4.",1433276814,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Tidy decodes and moves the space:
+
+```
+> print MWTidy::tidy('<span class=""a""><span class=""b"">x</span>&#32;</span>y');
+
+<p><span class=""a""><span class=""b"">x</span></span> y</p>
+
+> $opt = new ParserOptions;
+
+> print $wgParser->parse('<span class=""a""><span class=""b"">x</span>&#32;</span>y', Title::newMainPage(), $opt)->getText();
+
+<p><span class=""a""><span class=""b"">x</span>&#32;</span>y
+</p>
+
+> $opt->setTidy(true);
+
+> print $wgParser->parse('<span class=""a""><span class=""b"">x</span>&#32;</span>y', Title::newMainPage(), $opt)->getText();
+
+<p><span class=""a""><span class=""b"">x</span></span> y</p>
+```",1433201054,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",">>! In T74416#1322436, @ssastry wrote:
+> The second part to this puzzle here is: even if the space char entity was *outside*, Parsoid would wrap that entity with a mw:Entity span which would also likely break the CSS rendering in this case.
+
+So, I was wrong it looks like, thankfully. If I manually edited the HTML to:
+```</span><span typeof=""mw:Entity""> </span><span class=""nowrap""```
+the rendering is correct, of course, since the nowrap class doesn't apply to the entity span.
+
+So, if we can figure out the action=parse vs action=expandtemplates difference, we might be on our way to solving this issue. We need to figure out whether one of those API endpoints has a bug and/or the template needs fixing.
+",1432942780,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",@tstarling: any clue what is going on there with action=expandtemplates vs action=parse ? Can also dig into code next week.,1432942282,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","This is interesting.
+
+Compare: 
+https://fr.wikipedia.org/w/api.php?action=parse&format=json&text={{Palette|Seconde%20Guerre%20mondiale|Guerre%20froide|Communisme|Histoire%20des%20%C3%89tats-Unis}}
+vs.
+ https://fr.wikipedia.org/w/api.php?action=expandtemplates&format=json&text={{Palette|Seconde%20Guerre%20mondiale|Guerre%20froide|Communisme|Histoire%20des%20%C3%89tats-Unis}}
+
+So, action=expandtemplates returns:
+```... </span>&#32;</span><span class=""nowrap"" ... ```
+and action=parse returns:
+```... </span></span> <span class=""nowrap"" ...```
+
+How did the &#32; (which is a space char) move from inside the span to outside because of parsing? Parsoid is of course processing the result of action=expandtemplates and faitfully preserves the whitespace char where it exists .. inside the previous span. Something is goofy with the PHP parser there .. Or is it Tidy that is doing this?
+
+The second part to this puzzle here is: even if the space char entity was *outside*, Parsoid would wrap that entity with a mw:Entity span which would also likely break the CSS rendering in this case.",1433199968,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","This is interesting.
+
+Compare: 
+https://fr.wikipedia.org/w/api.php?action=parse&format=json&text={{Palette|Seconde%20Guerre%20mondiale|Guerre%20froide|Communisme|Histoire%20des%20%C3%89tats-Unis}}
+vs.
+ https://fr.wikipedia.org/w/api.php?action=expandtemplates&format=json&text={{Palette|Seconde%20Guerre%20mondiale|Guerre%20froide|Communisme|Histoire%20des%20%C3%89tats-Unis}}
+
+So, action=expandtemplates returns:
+```.. </span>&#32;</span><span class=""nowrap"" ```
+and action=parse returns:
+```</span></span> <span class=""nowrap"">```
+
+How did the &#32; (which is a space char) move from inside the span to outside because of parsing? Parsoid is of course processing the result of action=expandtemplates and faitfully preserves the whitespace char where it exists .. inside the previous span. Something is goofy with the PHP parser there .. Or is it Tidy that is doing this?
+
+The second part to this puzzle here is: even if the space char entity was *outside*, Parsoid would wrap that entity with a mw:Entity span which would also likely break the CSS rendering in this case.",1432942154,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",I verified by manually adding that single space between the spans and the navbox table at the bottom renders properly. The infobox at the top has the same problem and is fixed if I manually added that single space between spans.,1432941323,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Okay, I checked. There is a subtle but important difference that is causing this.
+
+In the PHP output, between the individual links in that column, there is a single whitespace character.
+```
+... </span> <span class=""nowrap""> ...
+```
+In Parsoid output, there is no whitespace  between the individual links
+```
+ ...</span><span class=""nowrap"" data-parsoid='{""stx"":""html""}'> ...
+```
+Without the whitespace, and with the nowrap class on the links, this means that there is no place for the browser to break the line, and hence that column stretches out forever. So, we need to figure out the reason why that single whitespace is being lost in Parsoid output.",1432941000,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line",I don't think it is mw:Entity entirely ... I am testing a html dump from that page where I replaced the mw:Entity with space or the entity as in the PHP html and it didn't change the rendering substantially. This requires some more digging into the HTML diffs between the two.,1416234700,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+"Navbox rendering incorrect, all items in the same line","Mediawiki:Common.css is included by the parsoid-rendered page, you can see this inspecting the infobox table with Firebug (or similar).
+
+The rendering problem comes from the navboxes at the end, which have all the links in each cell in the 2nd column in the same line, instead of wrapping them. If (using Firebug) the .nowrap style (or just ""white-space: nowrap;"") is disabled, the page returns to a more appropriate width.
+
+The only difference I can see in the HTML is the presence of multiple mw:Entity elements to indicate the white-space present in wikitext, so maybe that's what's interfering with nowrap.",1414511626,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-j6fh2cs3wbb53aewhrnh,task_subcomment,NA
+VisualEditor Mobile: The Citation icon does not get highlighted upon clicking or tapping on it in Mobile VE using desktop Safari and iOS safari,"Screenshot
+
+Steps to reporduce
+
+
+When you tap on Bold, Italic or Link buttons from the toolbar, the icons for these become highlighted in the toolbar.but when you tap on citation icon , there is no highlight on it, which looks a bit inconsistent
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14712}",1414024140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-irwbawwd34nibsp6cr6n,task_description,resolved
+VisualEditor Mobile: The Citation icon does not get highlighted upon clicking or tapping on it in Mobile VE using desktop Safari and iOS safari,Toolbar has changed a lot since this.,1438966850,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-irwbawwd34nibsp6cr6n,task_subcomment,NA
+VisualEditor Mobile: Cannot overwrite a text entered in CE in mobile VE using desktop Firefox,"Steps to reproduce:
+
+1.Open any page with mobile VE
+2.Type a text
+3.Select the text and type something else to overwrite it'
+
+Observed Result:
+Nothing gets entered into the CE and does not replace the old text
+
+
+Environment: Production, test2 and Betalabs",1414023600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iybf6jspgbrl4k2sojui,task_description,resolved
+VisualEditor Mobile: Cannot overwrite a text entered in CE in mobile VE using desktop Firefox,I can't reproduce this on Firefox 70.0b5 on Mac 10.14.6.,1568158597,PHID-USER-cbjanejnwkkrbnj77d2d,False,PHID-TASK-iybf6jspgbrl4k2sojui,task_subcomment,NA
+VisualEditor Mobile: Double clicking on citation note in Mobile using desktop Safari opens up the Basic reference dialog which was explicitly disabled for Mobile,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE which has citation note in it using desktop Safari
+
+2.Now double click on citation 
+
+Observed Result:
+It opens the Basic Reference dialog , which we explicitly disabled because there were lot of things we didn't implement inside that dialog
+
+See the screenshot attached
+
+Environment: Betalabs, test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15388}",1414022220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-urbyde4ziyfvfk6kwccx,task_description,declined
+VisualEditor Mobile: Double clicking on citation note in Mobile using desktop Safari opens up the Basic reference dialog which was explicitly disabled for Mobile,"In the weekly triage on 2015-04-22, this task was discussed. We decided to decline this task, as making all functions available is part of the plan for mobile.",1429738870,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-urbyde4ziyfvfk6kwccx,task_subcomment,NA
+VisualEditor Mobile: The context menu for Citations are not appearing after tapping on it when the keyboard is closed,"Screenshot
+
+Steps to reproduce:
+
+1.Load a page with Citations with Mobile VE in iOS safari or desktop Safari
+2.Keep the keyboard closed in iOS Safari so that the cursor is not active in CE, for desktop just click somewhere out of CE to keep the cursor inactive on CE
+3.Now click or tap on Citation note
+
+Observed Result:
+The context menu for it does not appear and a light shade of highlight appears on top of it when I click but it also goes away
+
+
+  
+See the screenshot attached
+
+Environment:test2, Betalabs and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15386}",1414020240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wljrwrl4avglyuy7j5wi,task_description,resolved
+VisualEditor Mobile: The context menu for Citations are not appearing after tapping on it when the keyboard is closed,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488130,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wljrwrl4avglyuy7j5wi,task_subcomment,NA
+VisualEditor Mobile: The context menu for Citations are not appearing after tapping on it when the keyboard is closed,Needs re-testing.,1430336136,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wljrwrl4avglyuy7j5wi,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE which does not have any reference in it to re-use.
+
+
+Observed Result:
+
+The ""Re-use"" label for the button is not greyed out even if the button icon is 
+
+See the screenshot attached
+Environment:Production,test2 and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15377}",1414019340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n73esked2uknidkk6dcc,task_description,resolved
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)",Verified the fix in production,1415834434,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)",Verified the fix in test2,1415229246,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)",Verified the fix in Betalabs,1415059679,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","**gerritadmin** wrote:
+
+Change 170790 merged by jenkins-bot:
+VE: Don't set @grayDark colour for tool titles in disabled widgets
+
+https://gerrit.wikimedia.org/r/170790",1415054928,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","**gerritadmin** wrote:
+
+Change 170790 had a related patch set uploaded by Alex Monk:
+VE: Don't set @grayDark colour for tool titles in disabled widgets
+
+https://gerrit.wikimedia.org/r/170790",1415047180,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","(In reply to Alex Monk from comment #1)
+> Looks like this is caused by MobileFrontend's
+> less/modules/editor/VisualEditorOverlay.less file - specifically this part:
+> .oo-ui-tool-title {
+>     color: @grayDark;
+>     font-size: .9em;
+> }
+> Which is taking precedence over the styles for the oo-ui-widget-disabled
+> stuff.
+> 
+> What if we changed it to this?
+> .oo-ui-widget-enabled > .oo-ui-tool-title {
+>     color: @grayDark;
+> }
+> .oo-ui-tool-title {
+>     font-size: .9em;
+> }
+
+Eurgh. Another reminder that we need to kill VisualEditorOverlay.less.",1415031272,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+"VisualEditor Mobile: The label for ""Re-use"" tool is not greyed out when the tool is disabled (icon is greyed out)","Looks like this is caused by MobileFrontend's less/modules/editor/VisualEditorOverlay.less file - specifically this part:
+.oo-ui-tool-title {
+    color: @grayDark;
+    font-size: .9em;
+}
+Which is taking precedence over the styles for the oo-ui-widget-disabled stuff.
+
+What if we changed it to this?
+.oo-ui-widget-enabled > .oo-ui-tool-title {
+    color: @grayDark;
+}
+.oo-ui-tool-title {
+    font-size: .9em;
+}",1414882548,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-n73esked2uknidkk6dcc,task_subcomment,NA
+VisualEditor: Move default value and autoValue code from MWParameterPage (UI) to MWParameterModel (DM),"Half of dm.MWParameterModel is dedicated to looking things up in the parent template's spec. Despite that, ui.MWParameterPage manually looks up the default value and autoValue because there are no getters in dm.MWParameterModel for those things, for no good reason whatsoever. Those getters should be added.
+
+What's even worse is the ""if there is no real value, set the value to the autoValue"" logic (added in https://gerrit.wikimedia.org/r/168204 ). Currently this logic (which is fundamentally DM logic) is in ui.ParameterPage as well. Instead, MWParameterPage.getValue() should be smart enough to return either the real value or the autoValue if there is no real value.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414019220,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gsdjjehs7duzg6p7efj3,task_description,resolved
+VisualEditor: Move default value and autoValue code from MWParameterPage (UI) to MWParameterModel (DM),"**gerritadmin** wrote:
+
+Change 168926 merged by jenkins-bot:
+Move autoValue logic from ui.MWParameterPage to dm.MWParameterModel
+
+https://gerrit.wikimedia.org/r/168926",1414433710,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gsdjjehs7duzg6p7efj3,task_subcomment,NA
+VisualEditor: Move default value and autoValue code from MWParameterPage (UI) to MWParameterModel (DM),"**gerritadmin** wrote:
+
+Change 168926 had a related patch set uploaded by Alex Monk:
+Move autoValue logic from ui.MWParameterPage to dm.MWParameterModel
+
+https://gerrit.wikimedia.org/r/168926",1414380772,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gsdjjehs7duzg6p7efj3,task_subcomment,NA
+VisualEditor: Move default value and autoValue code from MWParameterPage (UI) to MWParameterModel (DM),"(In reply to Roan Kattouw from comment #0)
+> Instead, MWParameterPage.getValue() should be
+> smart enough to return either the real value or the autoValue if there is no
+> real value.
+
+MWParameterModel.getValue()?",1414336868,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-gsdjjehs7duzg6p7efj3,task_subcomment,NA
+VisualEditor: Pasting in text containing a tab character causes VE to scroll to the top,"Intention:
+Paste bibliographic information from Google books
+
+Steps to Reproduce:
+1. Almost any book will do for this, but to pick an example http://books.google.co.uk/books?id=VYvS7MyaEE8C
+2. Scroll down to the ""Bibliographic information"" section at the end
+3. Select everything between the name of the publisher and the first ISBN number.  Ignoring whitespace, you should have something like ""Academic Press, 2012 ISBN 0123914213"" on the clipboard. It is important that the selection spans at least two lines and includes at least one tab character.  Other than that it is not vital what infomation from the bib is selected, but this is what I would normally select and gives me problems.
+4. Choose a Wikipedia page with a substantial amount of text, or create one in sandbox
+5. Launch VE and scroll down far enough so the top of the article is no longer visible.
+6. Start a new line and type some text such as ""Author name, Book Title, "" (this step is essential)
+7. Paste the clipboard contents immediately at the end of this line (this currently has to be done with right-click paste rather than CTrl-V due to another bug, but this was still happening before Ctrl-V got broke)
+
+
+Actual Results:  
+The part of the article you are working on (this will usually be the references or bibliography section right at the end of the article) disappears from sight as VE scrolls right to the top of the article.
+
+Expected Results:  
+The focus should stay at the pasting insertion point.
+
+Scrolling to the top also occurs when a tab is typed from the keyboard, which I assume is related.  Possibly this is meant to be a feature, but it is not a very helpful one - I find myself typing tabs while in tables expecting to tab to the next cell as is common on internet forms.  I know VE doesn't do this, but the expected behaviour is so ingrained I keep getting caught out.  In any case, a tab pasted in with text doing this is definitely a bug.
+
+Reproducible: Didn't try
+
+The bug is quite intrusive to me, I am frequently pasting in source bibliographic information, almost every session.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**: {T73728}",1414014540,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-nngads3asyp22g2mfznd,task_description,resolved
+VisualEditor: Pasting in text containing a tab character causes VE to scroll to the top,"Works for me on en.wiki. Feel free to reopen if necessary.
+",1433463442,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-nngads3asyp22g2mfznd,task_subcomment,NA
+VisualEditor: Pasting in text containing a tab character causes VE to scroll to the top,"Seems to work for me on En.wiki. Reopen if necessary.
+",1433463416,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-nngads3asyp22g2mfznd,task_subcomment,NA
+VisualEditor: Pasting in text containing a tab character causes VE to scroll to the top,"Confirmed in test2 and betalbs.
+
+Steps to reproduce: 
+
+1. Copy all(or part of) Bibliographic information on http://books.google.co.uk/books?id=VYvS7MyaEE8C. It's a html table.  
+
+2. Paste it at the end of an existing line in a chunk of text of test2 or betalabs.  The amount of text should be large enough to allow you to scroll down the page and then paste the table at the end of any line. 
+
+
+Observed result: after pasting, the page scrolls up. The pasted table is correctly placed though. The issue does not happen if a table is pasted on a new line.",1414079652,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-nngads3asyp22g2mfznd,task_subcomment,NA
+"VisualEditor: Pasting invalidly parented <figcaption> throws ""Uncaught TypeError: Cannot read property 'type' of undefined"" in ve.dm.LinearData.static.getType","1. Copy to the clipboard the below invalid rich content from NYTimes.com:
+   <div><div …><a …><img …></a></div><figcaption …>Foo</figcaption></div>
+
+2. Go to any page in VE
+
+3. Paste; observe crash of paste engine.
+
+Paste rules are probably not checking parentage (HTML spec says no <figcaption>s except as children of <figures>s) and it's breaking things. Instead, we should… eh. Downcast to <div>?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414011120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pwgzlrz42g3jw6le42cr,task_description,resolved
+"VisualEditor: Pasting invalidly parented <figcaption> throws ""Uncaught TypeError: Cannot read property 'type' of undefined"" in ve.dm.LinearData.static.getType","Although I don't have the example from NYTimes.com, copy-pasting similar HTML from a local page doesn't crash anymore (the caption text is discarded).",1535731341,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-pwgzlrz42g3jw6le42cr,task_subcomment,NA
+"Use the local namespace for files, instead of the English default","If you add a file in VisualEditor, then it sometimes adds the file using the English namespace or other English terms.  Examples:
+
+https://ca.wikipedia.org/w/index.php?diff=14187112&oldid=14185423 – ""File"" is not a Catalan word
+
+https://es.wikipedia.org/w/index.php?diff=77684034&oldid=73098946 – ""File"" is not a Spanish word
+
+https://de.wikipedia.org/w/index.php?diff=135103424&oldid=135103377 – German uses ""mini"" instead of ""thumb""
+
+https://ro.wikipedia.org/w/index.php?diff=8882945&oldid=7944846 – ""File"" is not a Romanian word
+
+https://ru.wikipedia.org/w/index.php?diff=66358996&oldid=55356951 – or Russian
+
+https://sv.wikipedia.org/w/index.php?diff=28184524&oldid=20202611 – or Swedish
+
+https://pl.wikipedia.org/w/index.php?title=Pawe%C5%82_z_Eginy&diff=40760929&oldid=38644980 – or Polish 
+
+https://it.wikipedia.org/w/index.php?title=Paolo_di_Egina&diff=68773170&oldid=63002904 – or Italian
+
+
+In other cases, it did use the local name, including French, Hungarian, and Estonian.  I'm not sure what the common thread is.  It's possible that some of these communities deliberately choose to use the English namespace, but at least a few change such edits.  If we can use the local name more often, then we should be able to reduce the burden on local communities.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1414004040,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gglnxexerzlpc27dmjou,task_description,open
+"Use the local namespace for files, instead of the English default","Thought this was already filed with Parsoid, but I can't find it. Please merge if I've missed it!",1414004465,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gglnxexerzlpc27dmjou,task_subcomment,NA
+Give a hint there is a save button in action=edit,"While observing three librarians editing each their own page, I noticed that they had uncertainties when asked to save their edit. I had to explain them they have to scroll the page, and exactly where to scroll: not the text area, the whole page.
+
+Indeed, the save button is easily outside the screen, even without overly long copyrightwarning areas. We should always give a hint to users so that they know where to proceed.
+
+Something as simple as a biggish button on top of the text area, linking the [[#wpSave]] anchor, might even suffice. Worth some prototyping and usability testing IMHO.
+
+I filed a twin report for VisualEditor without realising:  T90864
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413971040,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-3l67fot6jvz627mticzv,task_description,open
+Give a hint there is a save button in action=edit,This is really usability rather than accessibility.,1520998387,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-3l67fot6jvz627mticzv,task_subcomment,NA
+Give a hint there is a save button in action=edit,"Created attachment 16839
+Save buttons outside of screen
+
+**Attached**: {F15242}",1413971086,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-3l67fot6jvz627mticzv,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open Link inspector in an empty line 
+
+
+Observed Result:
+A scroll bar is appearing inside the link inspector
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15203}",1413931380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xm2mk6rfi3neidlarp5g,task_description,resolved
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,Verified the fix in production,1414613285,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,Verified the fix in test2,1414101630,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,"**gerritadmin** wrote:
+
+Change 168206 merged by jenkins-bot:
+Increase inspector height by 1 to deal with Chrome opacity bug
+
+https://gerrit.wikimedia.org/r/168206",1414020472,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,"**gerritadmin** wrote:
+
+Change 168206 had a related patch set uploaded by Esanders:
+Increase inspector height by 1 to deal with Chrome opacity bug
+
+https://gerrit.wikimedia.org/r/168206",1414018115,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector,"Proximate cause is https://gerrit.wikimedia.org/r/#/c/167446/ , it was working before that change.
+
+What seems to be going on is that there's a browser bug in Chrome that causes the inspector's body to immeasurably have a slightly greater height if the opacity of the Open button is not equal to 1. That's why this bug is only reproducible in creation mode, and the scrollbar goes away as soon as you type: the Open button is initially disabled (opacity:0.5), then enabled when you type something (opacity:1).
+
+If you want entertainment, inspect an enabled Open button, add opacity:0.999; to it and toggle it off and on a few times.",1413936016,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xm2mk6rfi3neidlarp5g,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"This site, https://wiki.transitionnetwork.org/ is running on amd64 Debian Wheezy with Parsoid installed using apt as per the instructions at https://www.mediawiki.org/wiki/Parsoid/Setup#Ubuntu_.2F_Debian_on_amd64
+
+Today the new GPG siging key was installed and Parsoid updated (see https://trac.transitionnetwork.org/trac/ticket/692#comment:103 ) to version 0.1.15 and this has caused all edits using the VisualEditor to generate 500 errors, this is what is logged when you try to save a page:
+
+  [info][localhost/Sandbox2?oldid=946] started parsing
+  [fatal/request][localhost/Sandbox2?oldid=946] undefined is not a function
+  TypeError: undefined is not a function
+      at TreeBuilder.resetState (/usr/lib/parsoid/src/lib/mediawiki.HTML5TreeBuilder.node.js:61:17)
+      at new TreeBuilder (/usr/lib/parsoid/src/lib/mediawiki.HTML5TreeBuilder.node.js:28:7)
+      at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:231:17)
+      at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:227:17)
+      at ParserPipelineFactory.getPipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:363:15)
+      at ParserPipelineFactory.parse (/usr/lib/parsoid/src/lib/mediawiki.parser.js:311:20)
+      at /usr/lib/parsoid/node_modules/prfun/lib/index.js:436:24
+      at new Promise (/usr/lib/parsoid/src/node_modules/es6-shim/es6-shim.js:1228:11)
+      at /usr/lib/parsoid/node_modules/prfun/lib/index.js:419:14
+      at /usr/lib/parsoid/src/api/routes.js:152:62
+
+The error presented to editors is:
+
+> Error loading data from server: parsoidserver-http-bad-status: 500. Would you like to retry?
+
+I have reverted to the old version of parsoid to get around this issue:
+
+  apt-get install parsoid=0.1.12
+
+There are some more details on this ticket https://trac.transitionnetwork.org/trac/ticket/799
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Linux
+",1413895440,PHID-USER-hlhhdspdobxg2jb5lyms,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_description,declined
+Parsoid 0.1.15 generates 500 errors when editing pages,"@chrisc, I'm sadly a bit out of ideas. I haven't been able to reproduce this so far (but am running sid), and it seems to be working fine for most users. I would just put it down to wheezy, except that it's a JS error that would be specific to running old JS code.
+
+Is your `sources.list` line matching the one recommended at https://www.mediawiki.org/wiki/Parsoid/Setup#Ubuntu_.2F_Debian_on_amd64 ?",1424471190,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"@chrisc, I'm sadly a bit out of ideas. I haven't been able to reproduce this so far (but am running sid), and it seems to be working fine for most users. I would just put it down to wheezy, except that it's a JS error that would be specific to running old JS code.",1424471080,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"Yes, I tried that and it didn't make a difference I'm afraid, anything else I could try?",1419078211,PHID-USER-hlhhdspdobxg2jb5lyms,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,@ChrisC Is the error message still the same after a `apt-get remove --purge parsoid` followed by `apt-get install parsoid`?,1418941862,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"This is with `0.10.29~dfsg-1~bpo70+1` on Wheezy, with `nodejs/wheezy-backports` and `nodejs-legacy/wheezy-backports`:
+
+  cat /etc/debian_version 
+  7.7
+
+  aptitude search node | grep ^i
+  i A nodejs                          - evented I/O for V8 javascript             
+  i   nodejs-legacy                   - evented I/O for V8 javascript (legacy syml
+
+  dpkg --print-avail nodejs
+  Package: nodejs
+  Priority: optional
+  Section: web
+  Installed-Size: 2811
+  Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
+  Architecture: amd64
+  Version: 0.10.29~dfsg-1~bpo70+1
+  Depends: libc-ares2 (>= 1.8.0), libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), libssl1.0.0 (>= 1.0.1), libstdc++6 (>= 4.1.1), libv8-3.14.5, zlib1g (>= 1:1.1.4)
+  Size: 900744
+  Description: evented I/O for V8 javascript
+   Node.js is a platform built on Chrome's JavaScript runtime for easily
+   building fast, scalable network applications. Node.js uses an
+   event-driven, non-blocking I/O model that makes it lightweight and
+   efficient, perfect for data-intensive real-time applications that run
+   across distributed devices.
+   .
+   Node.js is bundled with several useful libraries to handle server
+   tasks:
+   .
+   System, Events, Standard I/O, Modules, Timers, Child Processes, POSIX,
+   HTTP, Multipart Parsing, TCP, DNS, Assert, Path, URL, Query Strings.
+  Homepage: http://nodejs.org/
+
+  dpkg --print-avail nodejs-legacy
+  Package: nodejs-legacy
+  Priority: extra
+  Section: web
+  Installed-Size: 101
+  Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
+  Architecture: all
+  Source: nodejs
+  Version: 0.10.29~dfsg-1~bpo70+1
+  Depends: nodejs (>= 0.6.19~dfsg1-3~)
+  Conflicts: node
+  Size: 80428
+  Description: evented I/O for V8 javascript (legacy symlink)
+   Node.js is a platform built on Chrome's JavaScript runtime for easily
+   building fast, scalable network applications. Node.js uses an
+   event-driven, non-blocking I/O model that makes it lightweight and
+   efficient, perfect for data-intensive real-time applications that run
+   across distributed devices.
+   .
+   This package contains a symlink for legacy Node.js code requiring
+   binary to be /usr/bin/node (not /usr/bin/nodejs as provided in Debian).
+   .
+   No other Debian packages should depend on this package.  For more
+   information, see
+   <http://lists.debian.org/debian-devel-announce/2012/07/msg00002.html>
+  Homepage: http://nodejs.org/
+  
+  dpkg -L nodejs | grep bin/
+  /usr/bin/nodejs
+  
+  dpkg -L nodejs-legacy | grep bin/
+  /usr/bin/node
+
+  ls -lah /usr/bin/node
+  lrwxrwxrwx 1 root root 6 Aug  3 02:41 /usr/bin/node -> nodejs
+  
+  ps -lA | grep node
+  5 S     0  2738     1  0  80   0 - 12885 -      ?        00:13:29 munin-node
+  0 S   110 28296 28294  0  80   0 - 150789 -     ?        00:00:00 nodejs
+  0 S   110 28298 28296  0  80   0 - 184463 -     ?        00:00:02 nodejs
+  0 S   110 28299 28296  0  80   0 - 163198 -     ?        00:00:00 nodejs
+
+",1417743339,PHID-USER-hlhhdspdobxg2jb5lyms,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"I built & tested the 0.2.0 package on sid. Could this perhaps be a wheezy-specific issue? Which node version are you running? There are 0.10 package available in backports: https://packages.debian.org/wheezy-backports/nodejs
+
+We are generally running 0.10 these days, but used to support 0.8 until fairly recently.",1417710631,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"No change, switched to the latest version and when I tried to edit a page I got:
+
+//""Error loading data from server: parsoidserver-http-bad-status: 500. Would you like to retry?""//
+
+So I have reverted to the old version.
+
+Is there anything else I could do to help debug this?",1417695182,PHID-USER-hlhhdspdobxg2jb5lyms,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,We just released v0.2.0 to both npm and the Debian repository. Could you check if this issue is fixed?,1417572579,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"The HTML5 library was updated in the deploy repo at the end of August, which was after the 0.1.12 deb release. I'm not sure if the deb packages that (@Gwicke?) but did you try running `npm install`?",1416959240,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,gwicke: Any clue about the published debian package? Is this just a matter of updating the debian package?,1416235849,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"Yes, looks to me like a conflict with the html5 library. I don't know much about our Debian packaging though.",1413946419,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+Parsoid 0.1.15 generates 500 errors when editing pages,"This sounds like it's caused by the silently-breaking-change made by one of the upstream npm modules – Parsoid team, could you advise?",1413914687,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g4sqyb3luctzxk2bog3r,task_subcomment,NA
+VisualEditor: Categories set in wikitext not showing up in category dialog on a category page,"Open https://it.wikipedia.org/wiki/Categoria:Personalità_del_buddhismo?veaction=edit .
+Notice that no categories appear in the category dialog, while that page features 2 of them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61921",1413894840,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-sxtng5ghv2nfoij5k4cf,task_description,resolved
+VisualEditor: Categories set in wikitext not showing up in category dialog on a category page,"
+
+*** This bug has been marked as a duplicate of bug 72080 ***",1413917443,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-sxtng5ghv2nfoij5k4cf,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Screenshot
+
+Steps to reproduce:
+
+1.Load a page from http://en.m.wikipedia.beta.wmflabs.org/wiki/
+2.Open the page in Edit Source mode first
+3.Now go to the Settings icon and try to open the page with Mobile VE
+
+Observed Result:
+The following error appears in the console and VE does not open, stays in Edit Source mode:
+""TypeError: Cannot set property 'MWMobileContext' of undefined""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15064}",1413842040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zetzc2ngsimcakpv3og3,task_description,resolved
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears",Verified the fix in test2,1414103122,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears",Verified the fix in Betalabs,1413932523,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Change 167850 merged by jenkins-bot:
+Followup fbc7ecb: make mediawiki.mobile depend on core.mobile, not core
+
+https://gerrit.wikimedia.org/r/167850",1413922833,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Change 167850 had a related patch set uploaded by Catrope:
+Followup fbc7ecb: make mediawiki.mobile depend on core.mobile, not core
+
+https://gerrit.wikimedia.org/r/167850",1413915635,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Change 167715 merged by jenkins-bot:
+Followup e20b47f: make .mediawiki.mobile depend on .core
+
+https://gerrit.wikimedia.org/r/167715",1413844553,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console ""TypeError: Cannot set property 'MWMobileContext' of undefined"" appears","Change 167715 had a related patch set uploaded by Catrope:
+Followup e20b47f: make .mediawiki.mobile depend on .core
+
+https://gerrit.wikimedia.org/r/167715",1413842758,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zetzc2ngsimcakpv3og3,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"From a Wikia staff member working on ZH communities:
+
+Basically we need to type Pinyin (English words) first to select Chinese characters, but the New VisualEditors react very slowly or over fast. Before I make a Chinese word, the en words already pop up and are put in the editor.
+
+Here's a video of the bug happening on Mediawiki.org: http://youtu.be/G1WStvYrPPA 
+
+Report comes from Mac/Chrome but it could be happening on more.
+
+I asked if this was the same issue as T63429 but he said it was not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1413825840,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_description,invalid
+ZH IME input sometimes inserts latin characters,VulpesVulpes825: Thanks for the quick reply and thanks for re-testing!,1589878465,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"@Aklapper, I cannot reproduce it using the Pinyin IME on macOS 10.15.4 using Safari 13.1, Chrome 81.0.4044.138, and Firefox 76.0.1. Hence I have closed this task as invalid. If anyone can reproduce this phenomenon, please update steps to reproduce and feel free to reopen the task.",1589877303,PHID-USER-pb7r4bwzfkqxwgliqtet,False,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"@Liuxinyu970226: Can you explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle))?
+
+Also, three years later: Does anyonw still see this problem? And if yes, can provide updated steps to reproduce? Thanks!",1589876469,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,">>! In T74268#3136097, @Arthur2e5 wrote:
+> This happens on zhwiki too. And well, the reporter mentioned MediaWiki.org itself! No reason to keep it in ""Non-WMF sites"".
+> 
+> Certain pinyin IMEs (e.g. MS Pinyin) like to give the latin characters in the ""pinyin buffer"" area ahead of time, since it helps the application (e.g. search engine) make predictions. Visual Editor sometimes randomly trips over a point and keeps prematurely engulfing these characters. The code editor for Lua and JavaScript, on the other hand, consistently displays this problem with near-zero randomness.
+> 
+> My personal workaround to this problem occurs is switching to RIME until I finish one edit.
+
+Thank you for your clarification, however, I doubt if you have a fixme way due to T155928#3015470:
+>>! In T155928#3015470, @dchan wrote:
+> Change 336648 (which I've just merged) makes Tab step directly into the next cell. So you still get this problem, but only once when editing multiple adjacent cells.
+> 
+> I think that's probably the best we can do on this, until/unless Javascript/IME integration improves. (See https://w3c.github.io/input-events/ for current activity in this area).",1490677441,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"This happens on zhwiki too. And well, the reporter mentioned MediaWiki.org itself! No reason to keep it in ""Non-WMF sites"".
+
+Certain pinyin IMEs (e.g. MS Pinyin) like to give the latin characters in the ""pinyin buffer"" area ahead of time, since it helps the application (e.g. search engine) make predictions. Visual Editor sometimes randomly trips over a point and keeps prematurely engulfing these characters. The code editor for Lua and JavaScript, on the other hand, consistently displays this problem with near-zero randomness.
+
+My personal workaround to this problem occurs is switching to RIME until I finish one edit.
+
+",1490666413,PHID-USER-2qhtjovziou4utiyiop5,False,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"This happens on zhwiki too. And well, the reporter mentioned MediaWiki.org itself! No reason to keep it in ""Non-WMF sites"".
+
+Certain pinyin IMEs (e.g. MS Pinyin) like to give the latin characters in the ""pinyin buffer"" area ahead of time, since it helps the e.g. search engine make predictions. Visual Editor sometimes randomly trips over a point and keeps prematurely engulfing these characters. The code editor for Lua and JavaScript, on the other hand, consistently displays this problem with near-zero randomness.
+
+My personal workaround to this problem occurs is switching to RIME until I finish one edit.
+
+",1490666391,PHID-USER-2qhtjovziou4utiyiop5,False,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+ZH IME input sometimes inserts latin characters,"This happens on zhwiki too. And well, the reporter mentioned MediaWiki.org itself! No reason to keep it in ""Non-WMF sites"".
+
+Certain pinyin IMEs (e.g. MS Pinyin) like to give the latin characters in the ""pinyin buffer"" area ahead of time, since it helps the e.g. search engine make predictions. Visual Editor sometimes randomly trips over a point and keeps prematurely engulfing these characters. The code editor for Lua and JavaScript, on the other hand, consistently displays this problem with near-zero randomness.
+
+My personal workaround when this problem occurs is switching to RIME until I finish one edit.
+
+",1490666374,PHID-USER-2qhtjovziou4utiyiop5,False,PHID-TASK-lgqyw65pbs63v6sqiv4j,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Annotation continuation is working but the browser styles it wrongly (i.e., not at all)","Red color for link and blue background for language is not applied to the text
+
+Environment- test2
+
+1> Insert an internal link, the target is shown in red color. 
+2> Now while the cursor is at the last character of the link ,select the language annotation.
+3> Click Done on the inspector and type in some text. Notice although the context menu shows both Language and link labels, but the text typed is not red in color(indicating a link) and also the background color for language annotation is not applied to it. Appears as plain paragraph text.Move the cursor back and forth on the  entire text , still no change.However, when you go to new line by pressing enter key it does appear.
+
+See screenshot.
+
+In beta, the background color for language gets applied immediately but the link color takes effect only after you hit enter key to go to a new line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72108
+
+**Attached**: {F15009}",1413819600,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-y2ze4622w2dwciygcnjb,task_description,resolved
+"VisualEditor: [Regression wmf4] Annotation continuation is working but the browser styles it wrongly (i.e., not at all)","I widened the scope of bug 72108 to include this bug without realizing this bug existed, so I might as well merge them now.
+
+*** This bug has been marked as a duplicate of bug 72108 ***",1413940204,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-y2ze4622w2dwciygcnjb,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Annotation continuation is working but the browser styles it wrongly (i.e., not at all)","(In reply to Ritu Swain from comment #0)
+> Created attachment 16820 [details]
+> Red color for link and blue background for language is not applied to the
+> text
+> 
+> Environment- test2
+> 
+> 1> Insert an internal link by selecting the link icon from toolbar and typing in a name, the target is shown in red color. 
+> 2> Now while the cursor is at the last character of the link ,select the
+> language annotation.
+> 3> Click Done on the inspector and type in some text. Notice although the
+> context menu shows both Language and link labels, but the text typed is not
+> red in color(indicating a link) and also the background color for language
+> annotation is not applied to it. Appears as plain paragraph text.Move the
+> cursor back and forth on the  entire text , still no change.However, when
+> you go to new line by pressing enter key it does appear.
+> 
+> See screenshot.
+> 
+> In beta, the background color for language gets applied immediately but the
+> link color takes effect only after you hit enter key to go to a new line.
+
+**Attached**: {F15009}",1413821318,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-y2ze4622w2dwciygcnjb,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open","JS error in test2
+
+Environment- test2
+
+1> In VE,insert a media to a blank page with any settings, but without captions.
+
+2> highglight the image and then select the language from toolbar, the inspector opens on top of the image. JS error in console- ""Uncaught TypeError: Cannot read property 'resolve' of null"". clicking on done or Remove does not close the inspector.
+
+In beta , the inspector does not open when an image is highlighted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72258
+
+**Attached**: {F15001}",1413815040,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_description,resolved
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open",Verified the fix in production,1414625481,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open",Verified the fix in test2.,1414105836,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open", verified the fix in beta.,1413993678,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open","**gerritadmin** wrote:
+
+Change 168021 merged by jenkins-bot:
+Prevent JS error in getNativeRange()
+
+https://gerrit.wikimedia.org/r/168021",1413943158,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open","**gerritadmin** wrote:
+
+Change 168021 had a related patch set uploaded by Catrope:
+Prevent JS error in getNativeRange()
+
+https://gerrit.wikimedia.org/r/168021",1413942956,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] ""Uncaught TypeError: Cannot read property 'resolve' of null"" when applying language annotation to an image, the inspector remains open",Almost certainly the same flaw as bug 72258.,1413817346,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lfzhnijm7hbfk3gvny5g,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open","JS errors in test2
+
+Environment- test2, beta
+
+1>In VE, insert a media(with any settings but no content in ""Caption"") to blank page.
+
+2> Highlight the image and select link from the toolbar.JS Error-
+
+Uncaught TypeError: Cannot read property 'from' of null 
+Uncaught TypeError: Cannot read property 'resolve' of null 
+Uncaught TypeError: Cannot read property 'from' of null
+
+at this point.The inspector stays open and clicking on Remove or done does not close it.See screenshot. 
+
+In beta, the JS error(following the above steps) is - Uncaught TypeError: Cannot read property 'from' of null.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72259
+
+**Attached**: {F14995}",1413814140,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_description,resolved
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open",Verified the fix in production.,1414626645,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open","Verified in test2(wmf5) - FF, Chrome are fine. 
+
+Safari does not display Language and Link inspectors.",1414106930,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open",verified the fix in beta.,1413993600,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open","**gerritadmin** wrote:
+
+Change 168021 merged by jenkins-bot:
+Prevent JS error in getNativeRange()
+
+https://gerrit.wikimedia.org/r/168021",1413943162,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+"VisualEditor: [Regression wmf4] Applying link to an image gives ""Uncaught TypeError: Cannot read property 'from' of null "", inspector stays open","**gerritadmin** wrote:
+
+Change 168021 had a related patch set uploaded by Jforrester:
+Prevent JS error in getNativeRange()
+
+https://gerrit.wikimedia.org/r/168021",1413942992,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2ixdh6dr2flnvqm77pxq,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,"Since a few days all externl links, incl. coordinates in the upper right edge, are rendered as red links on dewiki. I guess this is a regression?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1413800400,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-3ukvlx3ldefokpkbnka7,task_description,resolved
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,Verified the fix in en.wiki,1414625832,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,Verified in test2 and betalabs(with 'Cite web' template).,1414434953,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,*** Bug 72376 has been marked as a duplicate of this bug. ***,1414007362,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,*** Bug 72287 has been marked as a duplicate of this bug. ***,1413849744,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+VisualEditor: [Regression wmf3] External links in templates are rendered as red links now,This was fixed in gerrit I35c9bea4.,1413816867,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ukvlx3ldefokpkbnka7,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied (all template and wikitext blocks in it have been removed), because the button is disabled.
+
+Split off from bug 71701.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413566460,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_description,resolved
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied",Verified the fix in production.,1416270229,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","https://www.mediawiki.org/wiki/MediaWiki_1.25/Roadmap has some more details about what version (see 'Target Milestone') goes to which Wikimedia production wiki and when. Right now this change should be on the following sites in Wikimedia production: mediawikiwiki, testwiki, test2wiki, testwikidatawiki",1415051834,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","Hey Elena, it has not yet made it to production(en.wiki), since it got fixed in wmf6.Lets check it on production after wednesday deployment.",1415051636,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied",test2 is in production.,1415050161,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","Works correctly in test2.  The bug still exists in production. 
+
+To check if my steps are correct: 
+
+1.Insert a template 'Cite web' 
+
+2. Open template properties for editing - and click 'Show options'. 
+
+3. Click on a trash can symbol - all fields should be empty, but 'Apply changes' is active.
+
+4. clicking on 'Apply changes' should delete the template.",1415050084,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied",Verified in betalabs.,1414442831,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","**gerritadmin** wrote:
+
+Change 168721 merged by jenkins-bot:
+Allow removing all parts from a transclusion to remove the transclusion
+
+https://gerrit.wikimedia.org/r/168721",1414433591,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","**gerritadmin** wrote:
+
+Change 168721 had a related patch set uploaded by Alex Monk:
+Allow removing all parts from a transclusion to remove the transclusion
+
+https://gerrit.wikimedia.org/r/168721",1414192463,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: It's not possible to ""Apply changes"" from the transclusion dialog after it has been emptied","Yeah; this should be available when there are changes (and on clicking it should remove the transclusion), but it should still be disabled in ""insert"" mode (as there's nothing to insert).",1413568314,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aj6cx3ygftk3motxe7xa,task_subcomment,NA
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Change the image size to a custom one
+4.Reopen the media Settings dialog
+5.Click on ""Make full size""
+Observed Result:
+Its changing the size values in the fields inside the dialog it does not enable the ""Apply Changes"" button
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14737}",1413496980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-peyhafaf5o5etsa2l5gh,task_description,resolved
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size",Verified the fix in production,1414613837,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-peyhafaf5o5etsa2l5gh,task_subcomment,NA
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size",Verified the fix in test2,1414103035,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-peyhafaf5o5etsa2l5gh,task_subcomment,NA
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size","**gerritadmin** wrote:
+
+Change 167964 merged by jenkins-bot:
+Add 'valid' event to MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/167964",1413936281,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-peyhafaf5o5etsa2l5gh,task_subcomment,NA
+"VisualEditor: [Regression] ""Make full size"" is not enabling ""Apply Changes"" button when the image has been set to a custom size","**gerritadmin** wrote:
+
+Change 167964 had a related patch set uploaded by Mooeypoo:
+Add 'valid' event to MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/167964",1413930065,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-peyhafaf5o5etsa2l5gh,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Steps to reproduce:
+
+1.  Open a page that already contains an external link without a label: [http://example.com].
+
+2.  Try to change that link to [http://example.com anything].  No fair removing the whole link and re-adding it.
+
+
+Results:
+
+Yeah, I couldn't figure out how to do that either.
+
+
+(According to the bug titles, bug 51309, bug 53505, and maybe some others address this, but the descriptions don't seem to match the titles very closely.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413492960,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_description,resolved
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"**gerritadmin** wrote:
+
+Change 168030 merged by jenkins-bot:
+Open the linkNode inspector when pressing Ctrl+K on a link node
+
+https://gerrit.wikimedia.org/r/168030",1413947014,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"**gerritadmin** wrote:
+
+Change 168030 had a related patch set uploaded by Catrope:
+Open the linkNode inspector when pressing Ctrl+K on a link node
+
+https://gerrit.wikimedia.org/r/168030",1413946095,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Phatom87 says he's been using ""the tab that shows up after clicking on the link.""  He's running Mozilla browser version is 32.0.3 and kde Linux 4.14.1.",1413847030,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Aha, the trick is you're using the toolbar button (or keyboard shortcut) rather than the context menu item. 
+
+This is a regression. It's loading the link annotation editor rather than the link node editor. Clicking the context menu works just fine. Boo.",1413575134,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"(Also, works fine in both skins.)",1413559784,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"I tried this earlier and works for me in Chrome/Win8 and Safari on my Air. (6.2 isn't the most recent Safari version, but I don't think that matters). Can it be some kind of cache issue?",1413559671,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Steps to reproduce:
+
+1.  1.  Open a page that already contains an external link without a label: [http://example.com], such as   https://en.wikipedia.org/wiki/User:Whatamidoing_%28WMF%29/sandbox?veaction=edit (scroll down to the ==External links== section).
+
+2.  Open the link dialog.
+
+I get the 'wrong' dialog in both Safari 6.2 and Firefox 32 on en.wp, mw.org, and beta labs, so it's not just one version.  Perhaps it's Mac specific?  I've asked Phatom87 (Mozilla Firefox user) for browser and OS information.",1413559316,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"(In reply to WhatamIdoing from comment #4)
+> Not done.  There's no ""Add label"" button (see screenshot).
+
+How did you get the wrong link dialog to trigger? Link and reproduction steps please.",1413503822,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Not done.  There's no ""Add label"" button (see screenshot).",1413503759,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Created attachment 16793
+Screenshot of link dialog
+
+**Attached**: {F14724}",1413503736,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"1. Select link.
+2. Edit link.
+3. Click ""Add label"".
+
+Done?",1413500706,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector,"Add label
+Change selection to select all except the last letter
+type : anything
+delete last letter
+
+not ...",1413495952,PHID-USER-hhw22zfd2xzrsyc22lp5,True,PHID-TASK-22uqtxwdglxq7a27zivv,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","buggy link dialog
+
+Links don't correctly autocomplete when adding them from the references dialog and not the main editor (see screenshot; Chrome, en.wp today).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F15331}",1413424800,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-r4igd57u7iobs63xxnge,task_description,open
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","Change 636522 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/extensions/VisualEditor@master] [WIP] ve.ui.MWMediaDialog: Use an overlay%%%
+Reason:
+%%%%%%
+https://gerrit.wikimedia.org/r/636522",1706727607,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","Change 636522 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] [WIP] ve.ui.MWMediaDialog: Use an overlay
+
+https://gerrit.wikimedia.org/r/636522",1603758933,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","This is still an issue today, although somehow it has changed back to clipping the inspector, like in the original report from 2014.
+{F32415818}",1603758035,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","This is still an issue, with the minor difference that the inspector is not clipped, but rather forces the dialog to have a scrollbar:
+
+{F12139380}
+
+It should look like this: (mockup)
+
+{F12139527}",1514605651,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small",">>! In T74121#3702775, @Elitre wrote:
+> Is this still relevant?
+
+The link dialogue is still contained inside the basic reference form, so this is still a valid report. I don't expect a great many people use the basic reference form, so I think the priority here can stay as it is.",1508750551,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small",Is this still relevant?,1508748075,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","I need to pick Trevor's brain about this. Right now the WindowManager for inspectors is in the localOverlay, which is a sibling of the ce-surface (and so is inside the iframe). It would be interesting to explore putting this in the globalOverlay, but then that would be nasty for scrollable surfaces (or even surfaces embedded in a scrollable container; like, for example, an iframe) where the anchor moves as you scroll: in a globalOverlay situation, we'd have to manually reposition the inspector to account for scrolling, but with the localOverlay as it is we get this for free.",1413942295,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+"VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small","The links are autocompleting just fine, it's just that the dropdown is so small that you only see one suggestion, and the rest can be accessed by scrolling (notice the scrollbar).
+
+What we should really be doing though, is not clip the link inspector against the boundaries of the dialog it's in, but allow it to go beyond those boundaries. That's a bit fiddly but probably not very hard.",1413941873,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-r4igd57u7iobs63xxnge,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,"Screenshot of Zuul status
+
+A few hours ago the Zuul queue started to get stuck. A stack of three changes in mediawiki-extensions-DonationInterface was reviewed with CodeReview+3. The top one (commit C, depending on B, depending on A) had a merge conflict in it.
+
+C https://gerrit.wikimedia.org/r/#/c/166678/3
+B https://gerrit.wikimedia.org/r/#/c/166803/1
+A https://gerrit.wikimedia.org/r/#/c/166889/2
+
+Somehow this caused Zuul's gate-and-submit pipeline to get stuck indefinitely. Even changes from mwext-VisualEditor, mediawiki-core, mwext-MobileFrontend were all waiting.
+
+Debug information from Zuul's log
+
+-------
+
+```
+$ cat /var/log/zuul/zuul.log.2014-10-15 | grep '166678,3'
+2014-10-15 19:17:14,453 INFO zuul.Gerrit: Updating information for 166678,3
+2014-10-15 19:17:15,169 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline check-only>
+2014-10-15 19:17:15,169 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline check-voter>
+2014-10-15 19:17:15,170 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline test>
+2014-10-15 19:17:15,171 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes []
+2014-10-15 19:17:17,470 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes []
+2014-10-15 19:17:17,470 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0ff0590 166678,3> with dependent changes []
+2014-10-15 19:17:17,474 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0ff0590 166678,3> with dependent changes []
+2014-10-15 19:17:19,481 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes []
+2014-10-15 19:17:19,481 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0ff0590 166678,3> with dependent changes []
+2014-10-15 19:18:08,759 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f17b0ff0590 166678,3>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 2}>]
+2014-10-15 19:18:08,842 INFO zuul.Gerrit: Updating information for 166678,3
+2014-10-15 23:21:16,969 INFO zuul.Gerrit: Updating information for 166678,3
+2014-10-15 23:21:17,284 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline gate-and-submit>
+2014-10-15 23:21:17,284 INFO zuul.DependentPipelineManager: Reporting start, action [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 0}>] change <Change 0x7f17b0ff0590 166678,3>
+2014-10-15 23:21:17,359 INFO zuul.Gerrit: Updating information for 166678,3
+2014-10-15 23:21:17,362 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes [<Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:30,406 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,790 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,790 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,794 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,798 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:48:30,564 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:50:13,976 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:50:13,976 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,864 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,864 INFO zuul.Gearman: Launch job mwext-VisualEditor-qunit for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,868 INFO zuul.Gearman: Launch job mwext-VisualEditor-bundle-rubocop for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,876 INFO zuul.Gearman: Launch job mwext-VisualEditor-phpcs-HEAD for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,884 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,888 INFO zuul.Gearman: Launch job mwext-VisualEditor-npm for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,893 INFO zuul.Gearman: Launch job mwext-VisualEditor-lint for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,957 INFO zuul.Gearman: Launch job mwext-VisualEditor-doc-test for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:56,023 INFO zuul.Gearman: Launch job experiment-gating-dependencies for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+[00:45 UTC] zuul at gallium.wikimedia.org in /srv/org/wikimedia/integration ((no branch)%)
+```
+
+-------
+
+```
+$ cat /var/log/zuul/zuul.log.2014-10-15 | grep '166803,1'
+2014-10-15 19:38:32,047 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 19:38:32,382 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline check-only>
+2014-10-15 19:38:32,405 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline check-voter>
+2014-10-15 19:38:32,406 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline test>
+2014-10-15 19:38:32,407 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes []
+2014-10-15 19:38:34,115 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes []
+2014-10-15 19:38:34,115 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0f64c10 166803,1> with dependent changes []
+2014-10-15 19:38:34,119 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0f64c10 166803,1> with dependent changes []
+2014-10-15 19:38:35,718 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes []
+2014-10-15 19:38:35,718 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0f64c10 166803,1> with dependent changes []
+2014-10-15 19:38:48,199 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f17b0f64c10 166803,1>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 2}>]
+2014-10-15 19:38:48,273 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 19:40:23,214 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 19:40:23,668 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 23:47:29,998 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 23:47:30,326 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline gate-and-submit>
+2014-10-15 23:47:30,327 INFO zuul.DependentPipelineManager: Reporting start, action [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 0}>] change <Change 0x7f17b0f64c10 166803,1>
+2014-10-15 23:47:30,402 INFO zuul.Gerrit: Updating information for 166803,1
+2014-10-15 23:47:30,406 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,790 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,790 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,794 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:47:31,798 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:48:30,564 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:50:13,976 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:50:13,976 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Resetting builds for change <Change 0x7f17b0c3d250 166918,2> because the item ahead, <QueueItem 0x7f180b290c10 for <Change 0x7f17b13caed0 166889,2> in gate-and-submit>, is not the nearest non-failing item, <QueueItem 0x7f17b10042d0 for <Change 0x7f17b0f64c10 166803,1> in gate-and-submit>
+2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,864 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,864 INFO zuul.Gearman: Launch job mwext-VisualEditor-qunit for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,868 INFO zuul.Gearman: Launch job mwext-VisualEditor-bundle-rubocop for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,876 INFO zuul.Gearman: Launch job mwext-VisualEditor-phpcs-HEAD for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,884 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,888 INFO zuul.Gearman: Launch job mwext-VisualEditor-npm for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,893 INFO zuul.Gearman: Launch job mwext-VisualEditor-lint for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:55,957 INFO zuul.Gearman: Launch job mwext-VisualEditor-doc-test for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+2014-10-15 23:59:56,023 INFO zuul.Gearman: Launch job experiment-gating-dependencies for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]
+```
+
+-------
+
+```
+$ cat /var/log/zuul/zuul.log.2014-10-15 | grep '166889,2'
+2014-10-15 22:33:35,953 INFO zuul.Gerrit: Updating information for 166889,2
+2014-10-15 22:33:36,261 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline check-only>
+2014-10-15 22:33:36,261 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline check-voter>
+2014-10-15 22:33:36,262 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline test>
+2014-10-15 22:33:36,263 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes []
+2014-10-15 22:33:39,803 INFO zuul.IndependentPipelineManager: Unable to merge change <Change 0x7f17b13caed0 166889,2>
+2014-10-15 22:33:39,803 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f17b13caed0 166889,2>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': -1}>]
+2014-10-15 22:33:39,876 INFO zuul.Gerrit: Updating information for 166889,2
+2014-10-15 23:48:30,171 INFO zuul.Gerrit: Updating information for 166889,2
+2014-10-15 23:48:30,484 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline gate-and-submit>
+2014-10-15 23:48:30,484 INFO zuul.DependentPipelineManager: Reporting start, action [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 0}>] change <Change 0x7f17b13caed0 166889,2>
+2014-10-15 23:48:30,559 INFO zuul.Gerrit: Updating information for 166889,2
+2014-10-15 23:48:30,564 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]
+2014-10-15 23:48:31,761 INFO zuul.DependentPipelineManager: Unable to merge change <Change 0x7f17b13caed0 166889,2>
+2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Resetting builds for change <Change 0x7f17b0c3d250 166918,2> because the item ahead, <QueueItem 0x7f180b290c10 for <Change 0x7f17b13caed0 166889,2> in gate-and-submit>, is not the nearest non-failing item, <QueueItem 0x7f17b10042d0 for <Change 0x7f17b0f64c10 166803,1> in gate-and-submit>
+```
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://launchpad.net/bugs/1358517
+
+**Attached**: {F15298}",1413420420,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hlivvhccoogrytjztz4v,task_description,resolved
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,Patch got merged upstream.,1461058704,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,"The patch solved the issues of patches being stuck in the event queue whenever the connection is lost with the Gearman server. That happened yesterday on the Wikimedia setup, on reestablishing the connection, all the pending merger:merge function have been executed and the event queue processed everything :-)
+
+Keeping bug open until the patch is approved by upstream.",1414856489,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,The patch has been deployed. Lets monitor the issue for a few days.,1414703006,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,I am now deploying https://review.openstack.org/#/c/128921/3 by merging in our Zuul fork at integration/zuul.git,1414684508,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,I have proposed a change at https://review.openstack.org/#/c/128921/ with a test which most probably has a race condition :D,1413837673,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,"Turns out I already filled a bug upstream in August.  The case was the connection to Gearman timing out while preparing a reference (same code path): https://bugs.launchpad.net/zuul/+bug/1358517
+
+I have replied there with a potential solution to the issue.
+
+
+Marking bug as an upstream issue.",1413466078,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+[upstream] Zuul prepareRef does not handle failure to connect to Gearman,"Looking at debug.log.2014-10-15
+
+
+23:21:17
+- receives a code review +2 event for change 166678,3
+- triggers a merge:merge function
+
+23:21:47 (30 seconds later):
+
+ ERROR gear.Client.unknown:
+   Connection <gear.Connection 0x1ca7f90 host: 208.80.154.135 port: 4730>
+   timed out waiting for a response to a submit job request:
+      <gear.Job 0x7f1809f1dd50
+          handle: None
+          name: merger:merge
+          unique: d928090c54474fa59b51d1661263750b>
+ NoConnectedServersError: No connected Gearman servers
+
+Zuul forks to spawn a Gearman server and both process communicate over TCP 4730 via the host public IP.
+
+The Zuul code that handles the creation of the reference (zuul.scheduler.BasePipelineManager.prepareRef() ) does not handle exceptions when submitting the job to Gearman, so it is raised up to the main loop and leave the enqueued change in an inconsistent state.
+
+
+I am not familiar with that part of the code.  I guess exceptions should be caught and some internal status (there is a `ready` variable) be set accordingly.
+
+
+To unblock such issue either:
+
+A) potentially a new patchset could be sent (that would remove the previous one from the Zuul queues) then +2ed again to reenter the gate-and-submit pipeline
+
+B) use the Zuul client to move the change ahead in the queue (an action known as 'promote') which would reorder the changes in the pipeline and retrigger merge jobs. Ie:
+
+ zuul promote --pipeline gate-and-submit --changes 166678,3
+
+See doc at http://ci.openstack.org/zuul/client.html#usage
+
+
+Adjusting priority, we can't have everything highest/critical.",1413464929,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-hlivvhccoogrytjztz4v,task_subcomment,NA
+VisualEditor Mobile: The down-arrow is not appearing in against the cite menu's icon in Mobile VE,"Screenshot
+
+See the screenshot attached to see the position of the arrow
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15292}",1413419460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gx6gtxwaujgia6xrg3cb,task_description,resolved
+VisualEditor Mobile: The down-arrow is not appearing in against the cite menu's icon in Mobile VE,The icon was actually missing before; reversing the logic of this bug and marking it FIXED. :-),1413830564,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gx6gtxwaujgia6xrg3cb,task_subcomment,NA
+VisualEditor Mobile: The down-arrow is not appearing in against the cite menu's icon in Mobile VE,What's wrong about the position?,1413817191,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gx6gtxwaujgia6xrg3cb,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a group reference
+3.Now go to Insert>References list
+4.Click on the arrow to bring up the drop down box for the ""Use this group"" field
+
+
+Observe Result:
+The drop down box with options of group names are not opening unless you type something in the textfield
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15267}",1413412800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dr7acvvfxto6plbboi4q,task_description,resolved
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box",Verified the fix in production,1414100945,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box",Verified the fix in test2,1413504297,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box",Verified the fix in Betalabs,1413423082,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box","**gerritadmin** wrote:
+
+Change 166512 merged by jenkins-bot:
+TextInputMenuWidget: Handle undefined value properly when toggling visibility
+
+https://gerrit.wikimedia.org/r/166512",1413413173,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] Cannot open the dropdown box  for ""Use this group"" field inside References List dialog box","**gerritadmin** wrote:
+
+Change 166512 had a related patch set uploaded by Alex Monk:
+TextInputMenuWidget: Handle undefined value properly when toggling visibility
+
+https://gerrit.wikimedia.org/r/166512",1413412930,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dr7acvvfxto6plbboi4q,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the basic reference dialog
+3.Place the cursor inside the field ""Use the group""
+4.Type something or keep it empty while the drop down is open.
+5.Place cursor somehwhere else in the dialog to close it
+
+Observed Result:
+The drop down box does not get closed
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15265}",1413411180,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b2w334geyn6xehtamxqg,task_description,resolved
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Verified the fix in production,1414101205,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Verified the fix in test2,1413504179,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Verified the fix in Betalabs,1413423117,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Now fixed?,1413413104,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing","**gerritadmin** wrote:
+
+Change 166898 merged by jenkins-bot:
+Support MenuWidget's config.widget being in a different document
+
+https://gerrit.wikimedia.org/r/166898",1413412564,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing","**gerritadmin** wrote:
+
+Change 166898 had a related patch set uploaded by Catrope:
+Support MenuWidget's config.widget being in a different document
+
+https://gerrit.wikimedia.org/r/166898",1413412220,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor: [Regression wmf3] The dropdown box for ""Use this group"" field inside Reference dialog is not closing upon de-focusing",Ugh yeah this is because it's in the outer overlay :(,1413411380,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-b2w334geyn6xehtamxqg,task_subcomment,NA
+"VisualEditor:  If I click on ""show all fields"" and add a parameter, then leave the list of all fields open so I can add another (and another and another)","This is from Salix alba, and I don't believe that I can improve upon his description:
+
+
+I wanted to add {{tl|Infobox musical artist}} to an article and it proved to be much more painful than it needs to be. 
+
+If you want add one of the minor fields like {{param|genre}} you have to
+#Click on '''Add more information'''
+#Click on '''Show 17 more fields'''
+#scroll down to find the field you want and click on it
+#The window will then scroll to the top of the form so you have to
+#scroll down again to find the field you want and fill in the value
+#repeat the whole process again.
+
+This could be made easier. Why do I need to click twice to show all fields? Why do I need to go back to square one after adding a field? Why does it not auto scroll to the correct place (actually why not simply show the field under it description in the list of fields).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69734",1413395280,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wfyoixdybjp6v6matvrj,task_description,open
+"VisualEditor:  If I click on ""show all fields"" and add a parameter, then leave the list of all fields open so I can add another (and another and another)","This task appears to be the closest to what we think might be a solution to this wishlist survey proposal: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Editing/Customised_infobox
+
+The #TemplateWizard design for template parameters is to always have the list visible in the dialog's sidebar. Perhaps something similar would be appropriate for VE?
+",1643335561,PHID-USER-hlhhe6qw6qfkl7wyfhxk,True,PHID-TASK-wfyoixdybjp6v6matvrj,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown","--------------------------
+**Version**: unspecified
+**Severity**: normal",1413386880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rdtadfeyhzed33gkdvtq,task_description,resolved
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown","Change 166863 merged by jenkins-bot:
+Follow normalisation response from category status query
+
+[[https://gerrit.wikimedia.org/r/166863]]",1416967349,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown","Change 166863 had a related patch set uploaded (by Alex Monk):
+Follow normalisation response from category status query
+
+[[https://gerrit.wikimedia.org/r/166863]]
+
+#patch-for-review",1416958578,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown",*** Bug 72303 has been marked as a duplicate of this bug. ***,1413917443,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown","**gerritadmin** wrote:
+
+Change 166863 had a related patch set uploaded by Alex Monk:
+Follow normalisation response from category status query
+
+https://gerrit.wikimedia.org/r/166863",1413404106,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"[Regression ?wmf3] Non-normalised category names cause ""Uncaught TypeError: Cannot read property 'hidden' of undefined"" to be thrown",E.g. on https://www.mediawiki.org/wiki/VisualEditor - extra invisible characters at the end of each category name seems to be causing this,1413402055,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rdtadfeyhzed33gkdvtq,task_subcomment,NA
+"VisualEditor: When auto-filling citations using citoid, don't add any empty parameters","See the empty author parameters in this:  https://en.wikipedia.org/w/index.php?diff=629488479&oldid=629487984
+
+Empty, non-required parameters would ideally not be added by Citoid.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413235020,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-x35ncnimbtqjngphowun,task_description,resolved
+"VisualEditor: When auto-filling citations using citoid, don't add any empty parameters","There isn't any VE code using citoid yet, just a user script… however, assigning to Marielle.",1413915180,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-x35ncnimbtqjngphowun,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","screenshot
+
+Environment- test2, beta, production.
+
+1> Select template. In the Add a Template dialog when the cursor is in the input box, hit spacebar.
+2> The Add a Template button becomes active.click on it. 
+JS console error-“Uncaught Error: Unable to parse title”.
+
+Screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14999}",1413214140,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ptvgwefznutknxfidbsh,task_description,resolved
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template",Verified the fix in production along with the bug fix for 71249.,1416427523,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template",the fix is a part of 71249.,1415232901,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template",Fixed for validating template titles - verified in betalabs FF,1415133290,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","**gerritadmin** wrote:
+
+Change 170071 merged by jenkins-bot:
+Replacing MWTitleInputWidget.getValue() with MWTitleInputWidget.getTitle()
+
+https://gerrit.wikimedia.org/r/170071",1415063921,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","**gerritadmin** wrote:
+
+Change 170071 had a related patch set uploaded by SuchetaG:
+Replacing MWTitleInputWidget.getValue() with MWTitleInputWidget.getTitle()
+
+https://gerrit.wikimedia.org/r/170071",1415061379,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","(In reply to Gerrit Notification Bot from comment #3)
+> Change 168531 merged by jenkins-bot:
+> Add template button remains disabled when entering space as a template
+> 
+> https://gerrit.wikimedia.org/r/168531
+
+This fixes the issue as filed: when you type a space, the Add template button remains disabled. However, there are still a few values that you can use to make it crash, like ""Talk:"" (I was expecting ""|"" to break to, but surprisingly it doesn't because of unrelated evil hacks).
+
+That is part of a larger issue though, which I've filed as bug 72468.",1414114978,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","**gerritadmin** wrote:
+
+Change 168531 merged by jenkins-bot:
+Add template button remains disabled when entering space as a template
+
+https://gerrit.wikimedia.org/r/168531",1414114574,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","**gerritadmin** wrote:
+
+Change 168531 had a related patch set uploaded by SuchetaG:
+Add template button remains disabled when entering space as a template
+
+https://gerrit.wikimedia.org/r/168531",1414113846,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: “Uncaught Error: Unable to parse title” when entering ""Talk:"" as a template","Confirmed - test2, Betalabs, produciton(Chrome, FF)
+
+The following error is dispayed: 
+Uncaught Error: Unable to parse title VM5621:36
+TitleVM5621:36

+ve.dm.MWTemplateModel.newFromNameload.php?debug=false&lang=en&modules=ext.disambiguator.visualEditor%7Cext.math.visualEditor%7Cext.v…:257

+ve.ui.MWTemplatePlaceholderPage.onAddTemplateload.php?debug=false&lang=en&modules=ext.disambiguator.visualEditor%7Cext.math.visualEditor%7Cext.v…:277

+oo.EventEmitter.emitVM5625:7

+OO.ui.ButtonWidget.onClickload.php?debug=false&lang=en&modules=ext.visualEditor.core%2CviewPageTarget%7Cmediawiki.feedback%7C…:615

+jQuery.event.dispatchload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141017T2…:65

+elemData.handleload.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141017T2…:60",1413842881,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ptvgwefznutknxfidbsh,task_subcomment,NA
+"VisualEditor: ""Categories"" dialog behaves differently for existing values and entered values","Screenshot of initial render with 1 category present
+
+When opening the dialog and one category is already on the page, that category is rendered on its own line and the input field has its own line too (full width).
+
+When removing that category and re-adding it, the input field shrinks and the category bubble is in front of it on the same line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14793}",1412973900,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x2js3cwk25pg7q5wraqv,task_description,resolved
+"VisualEditor: ""Categories"" dialog behaves differently for existing values and entered values",Can't reproduce. It works as expected now.,1420773172,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x2js3cwk25pg7q5wraqv,task_subcomment,NA
+"VisualEditor: ""Categories"" dialog behaves differently for existing values and entered values","Created attachment 16746
+Screenshot of later rendering when adding a category
+
+**Attached**: {F14794}",1412973930,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x2js3cwk25pg7q5wraqv,task_subcomment,NA
+First line in edit window is sometimes hidden in Safari,"Intermittent bugs are the worst.
+This is happening to me randomly in Safari 7.1: when I try to create a new page, what I type won't show up sometimes. It seems like the first line (or two) of the edit window is ""hidden"" under the edit toolbar. It just happened to me several times in a row on a page similar to https://meta.wikimedia.org/w/index.php?title=Talk:Tech/News/2014/39&action=edit&redlink=1 .
+It also happens on existing pages: I remember I had difficulties placing templates at the top of a page on Meta, so I just tried to edit https://meta.wikimedia.org/w/index.php?title=Talk:Community_Engagement_(Product)/Media_Viewer_consultation/Other&action=edit , and the first two lines are ""missing"". Nothing happens if I try to scroll up and down, with mouse or keyboard (except I can't see the cursor blinking if it is on one of those lines).
+
+--------------------------
+**Version**: 1.25-git
+**Severity**: normal
+**OS**: Mac OS X 10.9",1412932980,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hrzcgmgl37xcbzoguhtx,task_description,invalid
+First line in edit window is sometimes hidden in Safari,Haven't noticed this in a while.,1458573763,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hrzcgmgl37xcbzoguhtx,task_subcomment,NA
+First line in edit window is sometimes hidden in Safari,"Actually, I just had this again in Chrome, while trying to update https://meta.wikimedia.org/wiki/VisualEditor/Newsletter/Sandbox :(",1415385867,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hrzcgmgl37xcbzoguhtx,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE with Firefox
+2.Edit the page
+3.Save the page or just navigate to Readmode after discarding the edit
+
+
+Observed Result:
+Cursor appears in the last line of the page in readmode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71829
+
+**Attached**: {F15300}",1412806320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_description,resolved
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Verified the fix in production,1415834858,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Verified the fix in test2,1415227620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Verified the fix in Betalabs,1415219458,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Change 144089 merged by jenkins-bot:
+Blur contentEditable node while destroying surface
+
+https://gerrit.wikimedia.org/r/144089",1415150050,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Still fixed, we're just moving it to a better place.",1415139852,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Change 144089 had a related patch set uploaded by Jforrester:
+Blur contentEditable node while destroying surface
+
+https://gerrit.wikimedia.org/r/144089",1415139296,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Change 169546 merged by jenkins-bot:
+Clear selection after tearing down surface to work around Firefox bug
+
+https://gerrit.wikimedia.org/r/169546",1414624899,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","Change 169546 had a related patch set uploaded by Catrope:
+Clear selection after tearing down surface to work around Firefox bug
+
+https://gerrit.wikimedia.org/r/169546",1414520612,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox","This issue is not fixed by the way, the cursor is still appearing the end of the document after saving a page in Firefox",1413831246,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Gah.,1413829922,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",Different issue.,1413829912,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+"VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox",This now seems fixed from my testing?,1413819892,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4zyamq2uzqay4psf2mpk,task_subcomment,NA
+VisualEditor Mobile: Can't select an image node if the cursor is active?,"If you open the editor and click on an image it works fine (albeit alienated), but once you've dropped the cursor anywhere in the document, even in a slug, it doesn't seem possible to select the node any more?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412803320,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3unnspcgavr6xhail2er,task_description,resolved
+VisualEditor Mobile: Can't select an image node if the cursor is active?,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488283,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3unnspcgavr6xhail2er,task_subcomment,NA
+VisualEditor: Copying text causes browser to scroll to the top of the page and move the cursor to the top in Safari,"Steps to reproduce:
+
+1.  Open a long page in Safari 6.2 (maybe others?)
+
+2.  Scroll down a ways and select some text.
+
+3.  Copy (Command-C) that text.
+
+
+Results:
+
+After a brief delay (one second?), the page scrolls all the way to the top.  The cursor is located at the very beginning of the page.  (The text is correctly copied.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**: {T74390}",1412650920,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-remttdefwzofqhhvwg2h,task_description,resolved
+VisualEditor: Copying text causes browser to scroll to the top of the page and move the cursor to the top in Safari,"Update:  As of July 2015, this is still happening in Safari 8.0 on Mac 10.10  
+
+However, instead of scrolling all the way to the top of the page, it scrolls until the selected/copied text is at the very bottom of the screen.",1437586008,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-remttdefwzofqhhvwg2h,task_subcomment,NA
+VisualEditor: Cannot enable or disable formatting of lines starting with semicolon markup,"If there is a line on a page that includes the semicolon syntax, VisualEditor does not handle this well. For example:
+
+<example>
+;Foo
+
+Some more text.
+</example>
+
+In VE, if I place the cursor either immediately before or immediately after the (bold-formatted) text ""Foo"", and then I add several new lines, I end up with multiple lines that include the semicolon formatting, such as:
+
+<example>
+;Bar
+;
+;Foo
+;Baz
+
+Some more text.
+</example>
+
+There is no way (that I can tell) to disable such formatting, and highlighting the (apparently) bold text and trying to select ""clear formatting"" has no effect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412634780,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-bh5fnqsfor56ucbo6du7,task_description,duplicate
+VisualEditor: Cannot enable or disable formatting of lines starting with semicolon markup,"In 'Edit source' - adding ; in front of a word makes a block displayed in bold in VE You cannot un-bold it in VE.
+
+<dl class=""ve-ce-branchNode""><dt class=""ve-ce-branchNode""><p class=""ve-ce-paragraphNode ve-ce-generated-wrapper ve-ce-branchNode"">Foo sjhajshjahssdsd</p></dt><dt class=""ve-ce-branchNode""><p class=""ve-ce-paragraphNode ve-ce-branchNode"">saksjdjskadja</p></dt></dl>
+
+dt {
+	.	
display: block;
+}
+
+dt {
+	.	
font-weight: bold;
+	.	
margin-bottom: .1em;
+}",1415137453,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-bh5fnqsfor56ucbo6du7,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],"Pages with a <link rel=""mw:PageProp/redirect"" href=""./Category:Foo""> but without a <link rel=""mw:WikiLink/Category"" href=""./Category:Foo""> should be serialised to [[:Category:Foo]] per the spec, but instead are becoming [[Category:Foo]] which (a) is wrong and (b) doesn't round-trip.
+
+----
+
+//Original VE complaint://
+
+The VE's Page Settings dialog redirect options work badly for category destinations.
+
+For example, if you choose 'Category:Article stubs' as your destination, it inserts this:
+
+#REDIRECT [[Category:Article stubs]]
+
+While this does redirect the page, it also places that page in the ""Article stubs"" category.
+
+It *should* put this on the page:
+
+#REDIRECT [[:Category:Article stubs]]
+
+Note the additional "":"" - this prevents the category being interpreted wrongly.
+
+https://www.mediawiki.org/w/index.php?title=VisualEditor:Redirecttest&action=history
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1412614020,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-2xatbyajrpglcczqz7gu,task_description,resolved
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],This change was deployed on March 19.,1426846636,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],">>! In T73708#1131553, @marcoil wrote:
+>>>! In T73708#1126551, @Krenair wrote:
+>> What about files?
+> 
+> What's the situation with files? Should they also be serialized with a ':'?
+
+Hmm... After doing some more checking, I think it may be OK without a ':' actually. Ignore me.",1426802989,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],"Change 197035 merged by jenkins-bot:
+T73708: Serialize category redirects with a ':'
+
+[[https://gerrit.wikimedia.org/r/197035]]",1426789820,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],">>! In T73708#1126551, @Krenair wrote:
+> What about files?
+
+What's the situation with files? Should they also be serialized with a ':'?",1426763987,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],What about files?,1426626267,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],"Change 197035 had a related patch set uploaded (by Marcoil):
+T73708: Serialize category redirects with a ':'
+
+[[https://gerrit.wikimedia.org/r/197035]]
+",1426511258,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]],"I wonder if there is any use case for allowing the version without "":"" with these namespaces, even if it should clearly not be the default. I don't think we want to add an extra button for something so obscure to most users.",1421805384,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2xatbyajrpglcczqz7gu,task_subcomment,NA
+VisualEditor: Annotation tools should be visibly disabled when selection is a formula node (which doesn't take annotations),"Screenshot
+
+Environment: test2, beta
+
+1> Insert a formula .
+2>highlight the formula and change its formatting to Bold/Italic/Underline/Strikethrough. None of these styles get applied to it.
+
+Now select Language, it opens the language inspector. Language should be disabled for formulas.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14907}",1412612100,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-btvs2s2ihxdsixm3lt3a,task_description,open
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,"Screenshot
+
+Environment- test2, beta, production
+
+1> insert a comment in a blank page.
+2> open the Edit comment box
+3> while the cursor is still blinking in the comment box, click to add numbered / Bullet point. The comment box closes and the comment is shown as the bullet/numbered list item
+4> Now open the edit comment box again and decrease the indentation.I get ""JS console error, Uncaught Error: Cannot set attributes on closing element"".See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14904}",1412607240,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-br5a45fin6czazh3islo,task_description,resolved
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,test2 - checked both scenarios - no js errors.,1416440312,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-br5a45fin6czazh3islo,task_subcomment,NA
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,"**gerritadmin** wrote:
+
+Change 173812 merged by jenkins-bot:
+Apply comment changes using fragment
+
+https://gerrit.wikimedia.org/r/173812",1416248160,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-br5a45fin6czazh3islo,task_subcomment,NA
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,"**gerritadmin** wrote:
+
+Change 173812 had a related patch set uploaded by Esanders:
+Apply comment changes using fragment
+
+https://gerrit.wikimedia.org/r/173812",1416232442,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-br5a45fin6czazh3islo,task_subcomment,NA
+VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used,"This isn't as bad any more (no JS errors), probably thanks to Ed's change making the comment inspector use staging. But there's still a minor bug:
+
+* Insert a comment in a blank page
+* Type some text into the comment
+* While comment box is still open, click Bullet list
+* Comment inspector closes, comment ends up inside list
+* Inspect comment
+* Comment is empty (?!)
+* Close inspector. Comment is automatically removed because it is empty
+
+(If you don't type some text at step 2, the comment is removed at that point because it's empty.)
+
+(Marking as regression pre-wmf5 even though the behavior in wmf4 was much worse.)",1413943410,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-br5a45fin6czazh3islo,task_subcomment,NA
+VisualEditor: Links to Draft namespace show as red links in link inspector search,"Draft namespace articles incorrectly showing as red links in search
+
+Draft namespace articles incorrectly showing as red links in search
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14790}",1412502240,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-k2h6lp7jsa6s76ca2dx4,task_description,resolved
+VisualEditor: Links to Draft namespace show as red links in link inspector search,Verified in en.wiki - not reproducible.,1415654778,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-k2h6lp7jsa6s76ca2dx4,task_subcomment,NA
+VisualEditor: Links to Draft namespace show as red links in link inspector search,"Indeed, this was probably fixed when we modified MW's API return to always give the exact value.",1415031827,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k2h6lp7jsa6s76ca2dx4,task_subcomment,NA
+VisualEditor: Links to Draft namespace show as red links in link inspector search,Can't reproduce issue...,1414807703,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-k2h6lp7jsa6s76ca2dx4,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the Insert menu
+
+Observe that, the icon for Media and Comment are appearing a bit darker compared to other options in the menu.
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15228}",1412210640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a3rsqh3622rlfp4zpwul,task_description,resolved
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,Verified the fix in production,1414100982,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,checked in BetaLabs and test2.,1413585832,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,"Maths icon fixed in gerrit 167031, which will be in wmf5 but is relatively minor.",1413483556,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,"Created attachment 16785
+Screenshot
+
+**Attached**: {F15229}",1413423563,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,The opacity of Formula icon and Special Character did not get fixed with other icons.Is that intentional?,1413423512,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu,Fixed with gerrit 166292 and gerrit 166293.,1413303144,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a3rsqh3622rlfp4zpwul,task_subcomment,NA
+"VisualEditor: Check locally for the user preference to prompt an edit summary, rather than waiting for the API to round-trip","Right now we rely on the API moaning about this, which means you have to wait for the whole page to be serialised, returned and saved before we prompt the user to do something that takes up some cycles, and so avoids them wasting time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412202840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ivp5hiloykrq3ijnlcsd,task_description,declined
+"VisualEditor: Check locally for the user preference to prompt an edit summary, rather than waiting for the API to round-trip","Never mind me, already done. *sighs*",1412289219,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ivp5hiloykrq3ijnlcsd,task_subcomment,NA
+"VisualEditor: Check locally for the user preference to prompt an edit summary, rather than waiting for the API to round-trip","You mean ""Prompt me when entering a blank edit summary""? I'm pretty sure we're handling that locally...",1412284901,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ivp5hiloykrq3ijnlcsd,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Now that it's been created, launching this should be scheduled…
+
+Release requirements from https://www.mediawiki.org/wiki/Beta_Features/Package :
+
+[x]    Make an extension - [[https://www.mediawiki.org/wiki/Extension:VectorBeta |Extension:VectorBeta]]
+[]    Get prelim design review
+[]    Get prelim security review
+[]    Get prelim performance review
+[]    Make sure there is a wiki page on mw.org for it that is understandable to the general public
+[]    Flowify the Talk page for the project
+[]    Make sure there is someone on point for feedback - a product manager (either volunteer or WMF staff)
+[]    Make a bugzilla component for the extension
+[]    Enable the Final Version of the code on Beta Cluster at least a week before you want to go for production.
+[]    Make gerrit change (do not merge) to the BF whitelist in mediawiki config
+[]    Deploy!
+",1412100840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_description,declined
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Change 175406 abandoned by Glaisher:
+Enable ""Form Refresh"" as a BetaFeature
+
+Reason:
+Per task
+
+[[https://gerrit.wikimedia.org/r/175406]]",1432471511,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",We decided to do {T100161} instead.,1432471403,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1298356, @Mattflaschen wrote:
+> I hope we can discuss this at the Lyon Hackathon and make a commitment which approach we will take.  There are various possible resolutions:
+
+Filed as {T99827}.  Tentatively scheduled for Workplace 2, Sunday 14:00.",1432154427,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Change 211081 abandoned by Mattflaschen:
+Add margin about watchlist submit button, on MW UI
+
+Reason:
+So as to focus on the HTMLForm alternative.
+
+[[https://gerrit.wikimedia.org/r/211081]]",1432098001,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","I hope we can discuss this at the Lyon Hackathon and make a commitment which approach we will take.  There are various possible resolutions:
+
+1. Finish $wgUseMediaWikiUIEverywhere (see {T72913}, etc. for the progress that has already been made).  A beta feature is not required for this.
+2. Completely remove $wgUseMediaWikiUIEverywhere from core, leaving it as if it were false.
+3. If there is a commitment to actually convert all of core to OO UI PHP (unlike MW UI, AFAICT, OO UI PHP is available in core, but not used from core), we could consider leaving the status quo until that is done.  This only makes sense if there's actually a commitment to do this, which it doesn't sound like there is if matmarex is describing it as 'allegedly'.",1432097874,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","I hope we can discuss this at the Lyon Hackathon and make a commitment which approach we will take.  There are various possible resolutions:
+
+1. Finish $wgUseMediaWikiUIEverywhere (see {T72913}, etc. for the progress that has already been made).  A beta feature is not required for this.
+2. Roll back $wgUseMediaWikiUIEverywhere 100% in the meantime.
+3. If there is a commitment to actually convert all of core to OO UI PHP (unlike MW UI, AFAICT, OO UI PHP is available in core, but not used from core), we could consider leaving the status quo until that is done.  This only makes sense if there's actually a commitment to do this, which it doesn't sound like there is if matmarex is describing it as 'allegedly'.",1432097738,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","It should be pointed out that **these styles have been live on mobile since day one with no problem.** and have made various forms usable.
+
+I don't care how we implement these standard forms, whether it's oojs ui, mediawiki ui classes or some other library but we really should start validating our designs across all our forms and gauging reactions to changes in appearance. Bugs get fixed quicker when in front of people's eyes. The idea of the beta feature was to capture reactions to a new design, regardless of how made, and this feels like a wasted opportunity.
+
+In my opinion, this entire initiative stalled because we were given the impression that the forms would be rewritten in oojs ui and I had thought that would have happened by now. I'd love a roadmap for UX standardisation as it's been a year now on how we plan to get a standard UI across the site and from an outsiders perspective I don't see any improvement to the state of affairs since last year (apart from a much sexier VisualEditor and a tiny bit more infrastructure namely templates and icons).",1432033743,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Bah, I've been repeatedly advising against creating a BetaFeature for this, much less enabling it everywhere, until we've made it work correctly at least most of the time. Apparently it was done quietly while I wasn't looking. I've been told that this will help us spot and fix issues, but I remember reporting the same issue with radio buttons myself a year ago and I see it's still there? Sad to see that all the effort goes into enabling new features and none into polishing them.
+
+We should mark this as ""Declined"" and focus our effort on something useful that people want to work on, since clearly no one wants to work on this.
+
+The blockers for this would probably amount to a few weeks of work, and it is all redundant anyway since we are allegedly moving from ""MediaWiki UI"" to ""OOjs UI MediaWiki theme"". The designs of the two have been rapidly diverging; if the aim is supposed to unify our interfaces, this must not be deployed.",1431793770,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1287139, @Mattflaschen wrote:
+>>>! In T73477#1266924, @greg wrote:
+>> Removed Jared from assignee; who is driving this now? Let's not push something out as a beta feature that doesn't have someone to care for it.
+> 
+> @greg, there is technical debt in core for this (wgUseMediaWikiUIEverywhere).  We really need to resolve this one way or the other.  
+> 
+> This is not a 'feature' we want to maintain separately on an ongoing basis the way VE or Flow is.  It is part of core, and the code forks need to be removed.  Then, it needs to be maintained by the UX team and in general engineers leveraging it (same as any core component).
+> 
+> Using a Beta Feature temporarily is one possible path, but not the only one.  We could also just do it directly (T72424), after sufficient testing.
+> 
+
+I have no idea what will come of the BetaFeatures project/process post Jared, but there were (presumably still are) very stringent rules on what can go out as a BF. Without a PM owning it, it doesn't go out (as a BF). Really, for any big UI refresh like this, I want a PM to own it to respond to feedback and drive it to a successful conclusion. Who will be doing that for this?
+",1431704588,PHID-USER-z3l4i7dl52qicxtephy5,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","> The goal should be for the new version to be a productive interface.
+
+If the positioning of radio selects and checkboxes seemingly becomes inverted from the original, with no apparent reasoning behind it, then I call that a problem, not a productive interface.
+
+Examples of these are everywhere:
+{F165110}",1431699888,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","I'm with @Quiddity. What causes all the control to be misplaced? If checkboxes are placed on one line, I expect them to be on one line. The controls should behave as standard UI controls with regards to being placed inline or as block elements.",1431679757,PHID-USER-t4cbxxxhiswoecybwxy2,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1287132, @Quiddity wrote:
+> The radiobuttons should be on individual lines here (and in TheDJ's second image above)
+> {F165030}
+> But vice-versa for the checkboxes (and the submit button) here (they should be on the same line)
+> {F165033}
+
+It seems like you want them on the same line or not just because they were in the original version. That's not the goal here.  The goal should be for the new version to be a productive interface.",1431670164,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1266924, @greg wrote:
+> Removed Jared from assignee; who is driving this now? Let's not push something out as a beta feature that doesn't have someone to care for it.
+
+@greg, there is technical debt in core for this (wgUseMediaWikiUIEverywhere).  We really need to resolve this one way or the other.  
+
+This is not a 'feature' we want to maintain separately on an ongoing basis the way VE or Flow is.  It is part of core, and the code forks need to be removed.  Then, it needs to be maintained by the UX team and in general engineers leveraging it (same as any core component).
+
+Using a Beta Feature temporarily is one possible path, but not the only one.  We could also just do it directly (T72424), after sufficient testing.
+
+>>! In T73477#1280648, @Quiddity wrote:
+> Beyond the design problems (examples above, plus more: [[http://i.imgur.com/Algh0Se.png| eg1]], [[http://i.imgur.com/FDYzdgX.png |eg2]]), 
+> this probably also needs to be QA-checked for functionality.
+
+What exactly are you saying is wrong with the first one?  Do you want them all on one line?
+
+For the second, I guess you're referring to the button wrongly touching 'Associated namespace'.  Fixed in https://gerrit.wikimedia.org/r/#/c/211081/ ; please review.
+
+Please file bugs (you don't need to for the one I already fixed), so we can triage them and decide what's a blocker.",1431670027,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","The radiobuttons should be on individual lines here (and in TheDJ's second image above)
+{F165030}
+But vice-versa for the checkboxes (and the submit button) here (they should be on the same line)
+{F165033}
+",1431669688,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Change 211081 had a related patch set uploaded (by Mattflaschen):
+Add margin about watchlist submit button, on MW UI
+
+[[https://gerrit.wikimedia.org/r/211081]]
+",1431669626,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1241123, @TheDJ wrote:
+> {F158088}
+> {F158090}
+> Not sure if people will be too exited when stuff looks like this....
+
+I guess for the first you're referring to the slightly awkward spacing?  This is not a blocker to the Beta Feature in my opinion.  It's something we can refine at any time.
+
+For the second, I don't see anything wrong at all.  Do you just not like the style?",1431668160,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Beyond the design problems (examples above, plus more: [[http://i.imgur.com/Algh0Se.png| eg1]], [[http://i.imgur.com/FDYzdgX.png |eg2]]), 
+this probably also needs to be QA-checked for functionality.
+
+I just discovered this Bug: {T98905}
+",1431460039,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",Removed Jared from assignee; who is driving this now? Let's not push something out as a beta feature that doesn't have someone to care for it.,1430948340,PHID-USER-z3l4i7dl52qicxtephy5,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","{F158088}
+{F158090}
+Not sure if people will be too exited when stuff looks like this....",1430215982,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","{F158088}
+
+Not sure if people will be too exited when stuff looks like this....",1430215922,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",This is now available on the beta cluster. http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences#mw-prefsection-betafeatures,1429950264,PHID-USER-lsveyqlsb4acoowxr5yj,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",,1429442434,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",,1429442393,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","As I mentioned on [[ https://gerrit.wikimedia.org/r/#/c/175406/ | gerrit ]], the changes that were needed in mw.ui have been made. But, I am not sure how other parts of the work is progressing. 
+
+@jdlrobson might know more.
+
+***
+//oops, made the same comment twice//",1429442492,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","As I mentioned on [[ https://gerrit.wikimedia.org/r/#/c/175406/ | gerrit ]], the changes that were needed in mw.ui have been made. But, I am not sure how other parts of the work is progressing. 
+
+@jdlrobson might know more.",1429442377,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",">>! In T73477#1198457, @greg wrote:
+> What's the plan/timeline, yo?
+
+ETA please.",1429284925,PHID-USER-z3l4i7dl52qicxtephy5,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","What's the plan/timeline, yo?",1428686518,PHID-USER-z3l4i7dl52qicxtephy5,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production","Tagged assuming that this might go ahead, but I have no special knowledge of it. :-)",1428680638,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"Enable the MediaWiki UI / ""Form Refresh"" Beta Feature in production",https://gerrit.wikimedia.org/r/#/c/175406/,1416823928,PHID-USER-lsveyqlsb4acoowxr5yj,True,PHID-TASK-ovf2mbalohzcr6eav5wb,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","screenshot 1
+
+Environment- test2, beta
+
+1> In VE, go to Options  -> Categories. And add two categories.
+2> Now delete the categories.Click on “Cancel” to close the  options dialog.
+3> Error in console, “Uncaught TypeError: Cannot read property 'disconnect' of undefined”(see screenshot 1)
+
+After this step, reopen the Options dialog , notice the first Category is repeated( see screenshot 2).
+
+Trying to delete any of the categories throws errors in console “Uncaught Error: Cannot remove detached item” and “Uncaught TypeError: Cannot read property 'metaItem' of undefined”.Clicking on Cancel or Apply changes does not close the dialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F15029}",1412092140,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_description,resolved
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”",Verified the fix in production,1412885547,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”",Verified the fix in production,1412885539,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”",Issue is now fixed in beta too.,1412609817,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”",Verified the fix in test2,1412362082,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Change 164018 merged by Catrope:
+Account for categories being removed twice in MWCategoryWidget
+
+https://gerrit.wikimedia.org/r/164018",1412203342,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Change 164018 had a related patch set uploaded by Jforrester:
+Account for categories being removed twice in MWCategoryWidget
+
+https://gerrit.wikimedia.org/r/164018",1412127002,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Change 163887 merged by jenkins-bot:
+Account for categories being removed twice in MWCategoryWidget
+
+https://gerrit.wikimedia.org/r/163887",1412115034,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Change 163887 had a related patch set uploaded by Catrope:
+Account for categories being removed twice in MWCategoryWidget
+
+https://gerrit.wikimedia.org/r/163887",1412100892,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”","Created attachment 16634
+screenshot 2
+
+**Attached**: {F15030}",1412092199,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-sdgsqmliomodrzl3kegc,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken if the link target suggestion dropdown overlaps with the border of the page,"video capture of the bug
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a link some where towards the end of the current viewport so that when you open the link inspector the link target suggestions overlap with the border of the page
+3.After inserting the link, reopen the link inspector and place cursor inside to bring up the link target suggestion 
+4.When the link target suggestion dropdown appears, scroll up the page 
+
+Observed Result: 
+The UI for the link inspector is open. 
+
+See the video capture attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14747}",1411769040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x4n4ij754asqbc6h7jmx,task_description,resolved
+VisualEditor: Link inspector UI gets broken if the link target suggestion dropdown overlaps with the border of the page,Verified the fix in production,1412885750,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x4n4ij754asqbc6h7jmx,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken if the link target suggestion dropdown overlaps with the border of the page,Verified the fix in test2,1412367951,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x4n4ij754asqbc6h7jmx,task_subcomment,NA
+VisualEditor: Link inspector UI gets broken if the link target suggestion dropdown overlaps with the border of the page,This is fixed by https://gerrit.wikimedia.org/r/#/c/163228/ and https://gerrit.wikimedia.org/r/#/c/163280/ as a side effect of fixing bug 52526,1411778730,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-x4n4ij754asqbc6h7jmx,task_subcomment,NA
+VisualEditor: Inserting a comment before the last word in a Language (RTL direction)Text moves the word to the start of the line.,"Environment-test2, beta
+
+1> Insert Language in RTL direction.
+2>insert a comment in the language text, right before the last word. Notice the word moves to the start of line.See screencast.
+3>Now place the cursor at the end of the last char in the langauge text and press backspace to delete.
+
+This also happens while inserting a citation or a formula.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP",1411668480,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ckia45kqd4ianv3wg3rp,task_description,open
+VisualEditor: Inserting a comment before the last word in a Language (RTL direction)Text moves the word to the start of the line.,Confirmed in test2 and Betalabs in Chrome.,1413834930,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ckia45kqd4ianv3wg3rp,task_subcomment,NA
+VisualEditor: Inserting a comment before the last word in a Language (RTL direction)Text moves the word to the start of the line.,http://youtu.be/6vtjey9UcCU,1411668687,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ckia45kqd4ianv3wg3rp,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2469/console
+
+https://integration.wikimedia.org/ci/job/VisualEditor-npm/3226/console
+
+Etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: blocker",1411664160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_description,resolved
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"I've purged the .npm cache. The coffee-scripts dependency seems to have been a result of cache corruption.
+
+https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2489/console
+
+Passing now on integration-slave1006.",1411757722,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"Seems to be an entirely different issue:
+
+00:00:03.045 [mediawiki-core-npm] $ /bin/bash -xe /tmp/hudson6526668683101242560.sh
+00:00:03.051 + cd /mnt/jenkins-workspace/workspace/mediawiki-core-npm/src/tests/frontend
+00:00:03.052 + npm --version
+00:00:03.346 1.3.10
+00:00:03.351 + npm install
+00:00:03.850 npm WARN package.json mediawiki@0.0.0 No description
+00:00:03.851 npm WARN package.json mediawiki@0.0.0 No repository field.
+00:00:03.852 npm WARN package.json mediawiki@0.0.0 No README data
+00:00:03.910 + npm test
+00:00:04.290 
+00:00:04.290 > mediawiki@0.0.0 test /mnt/jenkins-workspace/workspace/mediawiki-core-npm/src/tests/frontend
+00:00:04.290 > grunt test
+00:00:04.291 
+00:00:04.390 
+00:00:04.390 module.js:340
+00:00:04.390     throw err;
+00:00:04.391           ^
+00:00:04.392 Error: Cannot find module 'coffee-script'
+
+I have took a snapshot of the workspace on integration-slave1006 in /home/hashar/bug71314/ and the issue is reproduced.
+
+Looking at the dependencies:
+
+$ npm list
+mediawiki@0.0.0 /home/hashar/bug71314/src/tests/frontend
+├─┬ grunt@0.4.2
+│ ├── UNMET DEPENDENCY async ~0.1.22
+│ ├── UNMET DEPENDENCY coffee-script ~1.3.3
+│ ├── UNMET DEPENDENCY colors ~0.6.2
+...
+
+$ ls -1 node_modules/
+grunt/
+grunt-banana-checker/
+grunt-contrib-jshint/
+grunt-contrib-watch/
+grunt-jscs/
+grunt-jsonlint/
+$
+
+There are no 'node_modules' subdirectories below.
+
+So somehow npm install does not install the dependencies :-/  Maybe it considers them as already installed because they are in the ~/.npm cache ?  I gave it a try by deleting my /home/hashar/.npm and running `npm install`.  That managed to pull all the needed dependencies and npm test is runnable.
+
+I then deleted the node_modules sub directory and ran npm install again.  It installed the dependencies properly.
+
+
+Maybe it is a cache corruption and we should delete the /mnt/home/jenkins-deploy/.npm/ directory?",1411745654,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"This is still broken today, but in a different way now.
+
+https://gerrit.wikimedia.org/r/#/c/163168/
+https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2484/console",1411743480,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"**gerritadmin** wrote:
+
+Change 163119 merged by jenkins-bot:
+Migrate mediawiki-core-npm to Zuul cloner
+
+https://gerrit.wikimedia.org/r/163119",1411718546,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,Fixed by migrating the job to Zuul cloner which does not fetch submodules.,1411718306,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"**gerritadmin** wrote:
+
+Change 163119 had a related patch set uploaded by Hashar:
+Migrate mediawiki-core-npm to Zuul cloner
+
+https://gerrit.wikimedia.org/r/163119",1411717761,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,"Timo wrote:
+
+> Hi Antoine,
+> 
+> https://integration.wikimedia.org/ci/job/mediawiki-core-npm/
+> 
+> As of build 2463[1], it's broken with some git error (there seems to be
+> a stray extension directory even though it's against master).
+> The previous build 2462[2] passed fine.
+> 
+> FYI: This is not related to switching to Ubuntu Trusty, since the jobs
+> before that were working fine and also on Trusty.
+> 
+> — Timo
+> 
+> 
+> [1] https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2463/console
+> [2] https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2462/console
+
+
+I noticed it attempt to submodule update and fails on AbuseFilter which
+is the first submodule in core wmf branches.
+
+My assumption is that a job previously ran for a wmf branch which has
+submodule which were initialized.  Then a job against master is created,
+the Jenkins git plugin clean the repo but does not uninitialise
+submodules though they are not existant, so it bails out.
+
+That is probably a behaviour change in git (Precise has 1.7.9.x while
+Trusty has 1.9.1).
+
+
+I would recommend to revert the npm jobs back to Precise nodes. Will
+look at migrating the job from the evil Jenkins git plugin to the Zuul
+cloner.
+
+
+Do NOT upgrade the Jenkins git plugin.  It is terribly bugged and would
+kill everything (I tried on labs, does not work :-D).",1411716729,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+Jenkins: *-npm jobs broken for mediawiki-core and extensions,I depooled integration-slave1006.eqiad.wmflabs and a rebuild of the last failed mediawiki-core-npm job succeeded: https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2471/,1411664961,PHID-USER-ll6tmaogat2b5q7tnqas,True,PHID-TASK-rezh53p2xm2bwsgbhpo6,task_subcomment,NA
+"VisualEditor Mobile: After tapping on ""Go back""/""Continue Anyway"" in the ""Required parameter missing"" confirmation dialog in iOS Safari, it flickers at the top of the screen","Steps to reproduce:
+
+1.Open a page with mobile VE in iOS Safari
+2.Open Cite>Website
+3.Keep one of the required parameters empty and click on Insert
+4.When the confirmation dialog for required parameter being missing shows up, click on Go back or Continue anyway.
+
+
+Observed Result:
+Observe that, the animation of the confirmation dialog appearing and disappearing is not same as how it is in desktop safari.Also, when closing the dialog, by tapping on ""Go back""/""Continue Anyway"", instead of sliding up it flickers at the top of the screen.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1411599540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jetfcrjzmljadekjnwqj,task_description,resolved
+"VisualEditor Mobile: After tapping on ""Go back""/""Continue Anyway"" in the ""Required parameter missing"" confirmation dialog in iOS Safari, it flickers at the top of the screen","Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488277,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jetfcrjzmljadekjnwqj,task_subcomment,NA
+VisualEditor: Pasting in image caption with a repeated reference causes VE to crash,"I found this bug while trying to swap the captions of two images, but it can be duplicated with just one image:
+
+1. Paste this into a page and save:
+
+Example text<ref name=Ref1>Ref 1</ref>
+[[File:Example.jpg|thumb|Example text.<ref name=Ref1/>]]
+
+2. Launch VE
+3. Click the image and open the Media settings dialogue
+4. Select all the caption text (Ctrl-A) and cut it out (Ctrl-X)
+5. Apply changes
+6. Reopen the Media settings dialogue
+7. Paste the caption text back in (Ctrl-V)
+8. Apply changes
+
+VE will now hang on the Media settings dialogue.  The dialogue will not complete and will not cancel.  It is completely impossible to carry on editing, all the changes up to that point have to be discarded.
+
+I am using FF32, Windows 7, Monobooks
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1411520940,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-3itlwc5mvcohetlwjnl4,task_description,open
+VisualEditor: Pasting in image caption with a repeated reference causes VE to crash,"Since T259038 is resolved I now get a different error:
+```
+ve.ce.MWReferencesListNode.js:245 Uncaught TypeError: Cannot read properties of undefined (reading 'getAttribute')
+    at VeCeMWReferencesListNode.eval (ve.ce.MWReferencesListNode.js:245:58)
+    at Array.forEach (<anonymous>)
+    at ve.ce.MWReferencesListNode.update (ve.ce.MWReferencesListNode.js:226:20)
+    at later (oojs-ui-core.js:251:11)
+```",1714649234,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3itlwc5mvcohetlwjnl4,task_subcomment,NA
+VisualEditor: Pasting in image caption with a repeated reference causes VE to crash,"> VE will now hang on the Media settings dialogue. The dialogue will not complete and will not cancel. It is completely impossible to carry on editing, all the changes up to that point have to be discarded.
+
+It seems like it no longer hangs this way now, although the steps still result in an exception (""TypeError: group.firstNodes[index2] is undefined"" – same one as T259038) and mess up some internal state, which causes further exceptions whenever you do basically anything (although I'm not sure what's the impact on the users, I was still able to make changes and save the page despite them).",1692565153,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3itlwc5mvcohetlwjnl4,task_subcomment,NA
+VisualEditor: Pasting in image caption with a repeated reference causes VE to crash,See also bug 60919?,1414883335,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-3itlwc5mvcohetlwjnl4,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert the template ""Citation needed""
+3.Observe that in the field for ""Month and year"", the following has been used:
+{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}
+4.Now click on ""Apply Changes""
+5.Save the page
+6.Reopen the page
+7.Open the transclusion dialog for the ""Citation Needed"" template
+
+Observed Result:
+The current month name and current year value did not get added in the field.
+
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14868}",1411432560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ljyxu64angwfdp5jfokm,task_description,resolved
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"(In reply to Rummana Yasmeen from comment #7)
+> This seem to be not working in production (en.wiki).I dont even see the
+> substitute values {{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}} for the
+> parameters.
+
+This seems to be because the Citation needed template on enwiki doesn't have the autovalue set up yet. James said he would do this, but he was waiting for this bug to be fixed.",1414627219,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,This seem to be not working in production (en.wiki).I dont even see the substitute values {{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}} for the parameters.,1414623851,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,Verified in betalabs.,1414437118,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Change 168205 merged by jenkins-bot:
+Apply pre-save transform to template previews
+
+https://gerrit.wikimedia.org/r/168205",1414435124,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Change 168204 merged by jenkins-bot:
+Actually set parameter autoValues as values
+
+https://gerrit.wikimedia.org/r/168204",1414018433,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Change 168205 had a related patch set uploaded by Catrope:
+Apply pre-save transform to template previews
+
+https://gerrit.wikimedia.org/r/168205",1414018101,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,"Change 168204 had a related patch set uploaded by Catrope:
+Actually set parameter autoValues as values
+
+https://gerrit.wikimedia.org/r/168204",1414018095,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Template parameter autovalues are not saved,Definitely VE's fault. We're somehow not sending the parameter value to Parsoid when saving.,1414014943,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ljyxu64angwfdp5jfokm,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert a bullet list or numbered list
+3.Now try to add indentation to one of the item
+
+Observed Result:
+Apart from adding indentation, it ia also adding a new line and a new bullet point/numbered point
+
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14804}",1411416780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3jv4morfdfduiqmadob2,task_description,declined
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"(In reply to Ed Sanders from comment #8)
+> Recommend wontfix. There's no regular case to start a list at double
+> indentation. This change doesn't event prevent that, just makes it visually
+> clear what structure you should use.
+
+Very well.",1416243978,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"Recommend wontfix. There's no regular case to start a list at double indentation. This change doesn't event prevent that, just makes it visually clear what structure you should use.",1416237513,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"(In reply to Mark A. Hershberger from comment #6)
+> This is probably part related to Bug #37938, Bug #48010, and Bug #58335.
+
+No, this has nothing to do with those bugs; it's about the visual display of empty structural list items.",1415878385,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"This is probably part related to Bug #37938, Bug #48010, and Bug #58335.",1415815182,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"(In reply to Ed Sanders from comment #4)
+> I think it makes sense to have a slug there, as a double indented list is
+> actually a list wrapped in a list, so you need to be able to split them and
+> insert content.
+> 
+> Also you shouldn't double indent a list without content between, so this
+> make it clear something is being done wrongly.
+
+Sure, except you were the one to change the behaviour to this a few months ago, to match read mode rendering…",1411685967,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"I think it makes sense to have a slug there, as a double indented list is actually a list wrapped in a list, so you need to be able to split them and insert content.
+
+Also you shouldn't double indent a list without content between, so this make it clear something is being done wrongly.",1411678095,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"Created attachment 16592
+Screenshot in wmf22
+
+Okay, so if I compare the behavior of indentation in wmf 22 , it didnt add any slug when I increase indentation for any bullet list.It just added indentation for that bullet point moving it to the right.But now it is adding a slug ,See the screenshot attached for wmf 22 to compare how it used to work.
+
+**Attached**: {F14805}",1411671595,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,Can you give more detailed instructions. I'm seeing slugs in lists but only in sensible places.,1411660611,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time,"Due to the changes in how slugs work, presumably?",1411417528,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3jv4morfdfduiqmadob2,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"**Author:** `d_iarnov`
+
+**Description:**
+win 8.1  сенсорный .вообще нереально написать нажимая backspace  чтоб стереть  ошибочно написанное страницу подбрасывает вверх. и на этом точка. дальше работать соответственно не возможно. мало того в плиточном браузере вообще говорится что он не поддерживается. все браузеры у меня IE
+
+**See Also**: {T73561}
+
+---
+Alternative steps to reproduce (in English, from T89196):
+
+1. Edit [[Nausea]] in VE: https://en.wikipedia.org/wiki/Nausea?veaction=edit
+2. Scroll down to the ""Medications"" section
+3. Click in the middle of a sentence and hit ""backspace"" a few times.
+
+Each time you do this, the page jumps, and the sentence in which the cursor is located always ends up at the very bottom of the viewport.
+
+4. Press ""delete"" key a few times
+
+Same behaviour.
+
+5. Now click in the middle of the very long paragraph under ""Diagnostic approach"". Hit ""backspace"" a few times.
+
+Once again, the page jumps, but now it is worse, because the page lands with the cursor offscreen.",1411392420,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_description,resolved
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Thank you, @matmarex  ",1549986756,PHID-USER-nbq4yci7flcs7evltagr,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"@Fulla07 That looks like a different, new issue. I filed a separate task with more details: T215914",1549985189,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,This bug still appears on the english wikipedia.,1549975394,PHID-USER-nbq4yci7flcs7evltagr,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"This task is about VisualEditor. It sounds like you are talking about the mobile source editor, so please file a new task.",1487404429,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"On android, mobile view, editing any wikimedia page, using backspace or cut for deleting text, makes the screen scroll up to almost top of page. For example, I try to edit https://en.m.wikipedia.org/wiki/Ringwoodite top paragraph, backspace to delete the dot on the end scrolls me back to | class... in the infobox.",1487401622,PHID-USER-igzxxrouiten65uus2an,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Change 207875 merged by jenkins-bot:
+ui.ListAction: Fix screen jumping in Internet Explorer
+
+[[https://gerrit.wikimedia.org/r/207875]]",1430567035,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Change 207875 had a related patch set uploaded (by MarkAHershberger):
+Fix screen jumping
+
+[[https://gerrit.wikimedia.org/r/207875]]
+",1430418926,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Probably not. We keep all existing documentation public, in source code or on mediawiki.org.",1419810803,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"I'd like to get a better understanding of how to troubleshoot and extend VE and this issue has been marked as very important by a client.
+
+I've poked at similar bugs, but I'm not sure how they relate to this one and their solutions confuse me.  Is there anywhere I can look for more information on tracking it down?",1419810716,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,*** Bug 72646 has been marked as a duplicate of this bug. ***,1414530966,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"For me it scrolled abruptly almost to the top of the page (but not quite) and stayed there when I continued backspacing. I was testing on https://pl.wikipedia.org/wiki/Fotografia_cyfrowa (random page), for the record.",1412369925,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,Added possibly-related bug 71561?,1412369709,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Testing VE (both mobile and desktop) on a tablet (not phone) with both
+Windows 7 and 8.1, backspacing (both using software or hardware keyboards) works, but causes the page to abruptly scroll up. Just typing text doesn't cause this behavior. I'm going to assume that this was the original issue that was meant to be reported here :)",1412369526,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Marking as ""Low"" priority until more details are provided.",1412359019,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11,"Thanks for taking the time to report this!
+
+Am I correct that this is about Windows 8.1 phone?
+Could you provide exact steps to reproduce (step by step) in English what exactly is broken with backspace, and where exactly this happens (web address)?
+
+Please also see https://www.mediawiki.org/wiki/How_to_report_a_bug because ""doesn't work"" isn't a good bug summary. :)",1411396196,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6pa7blfmoh6dhhydjpvh,task_subcomment,NA
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image with caption
+3.Reopen the media settings dialog 
+4.Now apply link to the existing caption
+
+Observed Result:
+The ""Apply changes"" button does not become enabled after applying link unless user make some other change for that image
+
+Environment: Betalabs, Test2 and Production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411156560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6x3yrgo5cawaeou4wbls,task_description,resolved
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button",">>! In T73065#959930, @Whatamidoing-WMF wrote:
+> No, this is still broken.  I could reproduce this problem at mediawiki.org this morning.
+
+Re-broken in T8… something.",1420648664,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6x3yrgo5cawaeou4wbls,task_subcomment,NA
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button","No, this is still broken.  I could reproduce this problem at mediawiki.org this morning.",1420648629,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-6x3yrgo5cawaeou4wbls,task_subcomment,NA
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button",This apparently is long-ish-fixed?,1420597574,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6x3yrgo5cawaeou4wbls,task_subcomment,NA
+"VisualEditor: Applying link to the caption of an image does not enable ""Apply Changes"" button",This was also reported in Mac OS X 10.9.5 in both Firefox and Safari.,1414085906,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-6x3yrgo5cawaeou4wbls,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","**Author:** `physik`
+
+**Description:**
+On a fresh vagrant box with the role math enabled I get the following error message while trying to run the browser tests for math
+
+ unable to obtain stable firefox connection in 60 seconds (127.0.0.1:7055) (Selenium::WebDriver::Error::WebDriverError)
+  /srv/vagrant/mediawiki/extensions/Math/tests/browser/.gem/ruby/2.0.0 /gems/selenium-webdriver-2.42.0/lib/selenium/webdriver/firefox
+see
+ https://gist.github.com/physikerwelt/8a9ff6b292609449a2df
+
+I was doing nothing else beside running
+ bundle exec cucumber features/math.feature
+
+I checked my environment variables
+MW_INSTALL_PATH=/vagrant/mediawiki
+MEDIAWIKI_API_URL=http://127.0.0.1/w/api.php
+MEDIAWIKI_USER=Selenium_user
+MEDIAWIKI_PASSWORD=vagrant
+INSTANCEPROJECT=math
+COMPOSER_CACHE_DIR=/vagrant/cache/composer
+MEDIAWIKI_URL=http://127.0.0.1:8080/wiki/
+
+but could not detect any problems there
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1411049880,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_description,resolved
+"running browser tests ""unable to obtain stable firefox connection""","**physik** wrote:
+
+Technically you are right.
+I added a section to 
+https://www.mediawiki.org/wiki/Quality_Assurance/Browser_testing/Running_tests#Running_VisualEditor_browser_tests_via_labs-vagrant",1411070693,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","X isn't required as headless mode runs Firefox through xvfb. Use of phantomjs (note the ""js"") as the browser is inherently headless so you don't need to specify the HEADLESS env var.
+
+You can also try using X forwarding but it's a little trickier since your labs instance may not allow it. You can inquire on #wikimedia-labs or #wikimedia-qa IRC channels about getting that setup.
+
+This bug is technically resolved if you're not seeing the firefox connection error. Your feature looks to be executing correctly, and the scenario is either failing positively or falsely. You'll have to jump into the browser session to find our more. Jump on the #wikimedia-qa channel or email the QA list for help! [1]
+
+[1] https://lists.wikimedia.org/mailman/listinfo/qa",1411069276,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","**physik** wrote:
+
+Thanks. This changes the problem
+And I am at page that does not exist           # features/step_definitions/math_steps.rb:13
+    And I click link Create source                 # features/step_definitions/math_steps.rb:17
+      timed out after 5 seconds, waiting for {:text=>""Create source"", :tag_name=>""a""} to become present (Watir::Wait::TimeoutError)
+      ./features/step_definitions/math_steps.rb:18:in `/^I click link Create source$/'
+      features/math.feature:18:in `And I click link Create source'
+    When I type <math>3 + 2</math>                 # features/step_definitions/math_steps.rb:25
+
+I did not setup an x environment. Is that required?
+I tried to set my environment variable BROWSER=phantom but this did not help either.",1411068061,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","Those error messages from Firefox don't necessarily indicate failure. I would kill the firefox processes and try again, running in headless mode first to rule out X-forwarding issues.
+
+HEADLESS=true bundle exec cucumber ...",1411067002,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","Those error messages from Firefox don't necessarily indicate failure. I would kill the firefox processes and try again, running in headless mode first to rule out X-forwarding issues.
+
+HEADLESS=true bundle exec cucumber ...",1411066978,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","**physik** wrote:
+
+Thanks for the tip.
+However, that did not change anything.
+tests/browser$ bundle show selenium-webdriver
+/var/lib/gems/2.0.0/gems/selenium-webdriver-2.43.0
+tests/browser$ firefox --version
+(process:21861): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
+Mozilla Firefox 32.0
+
+Even downgrading to ff28 did not help.",1411066457,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+"running browser tests ""unable to obtain stable firefox connection""","This issue was recently documented on the QA list. [1]
+
+Issue: selenium-webdriver < 2.42 doesn't work with Firefox 32.
+Solution: Update your gems by running `bundle update` in your tests/browser directory and verify that you're using selenium-webdriver >= 2.43 by running `bundle show selenium-webdriver`.
+
+[1] https://lists.wikimedia.org/pipermail/qa/2014-September/001890.html",1411062930,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-hb3ednf4d3ajqz4ggzlz,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"TODO someone needs to figure out what the visual treatment should look like
+
+The inputs in question already match :required:empty , so we can probably do most of this with CSS.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410984600,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-yd4kojpa26xd52r2dadr,task_description,resolved
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,Verified the fix in production,1414101254,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 161613 merged by jenkins-bot:
+Style required but currently-invalid parameters on the template dialog
+
+https://gerrit.wikimedia.org/r/161613",1413312187,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 162511 merged by jenkins-bot:
+TextInputWidget: Add setValidation function to change pattern used to validate text
+
+https://gerrit.wikimedia.org/r/162511",1412030888,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 162511 had a related patch set uploaded by Alex Monk:
+TextInputWidget: Determine validity in onEdit rather than in setValue
+
+https://gerrit.wikimedia.org/r/162511",1411516231,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 161516 merged by jenkins-bot:
+TextInputWidget: Determine validity on blur and change.
+
+https://gerrit.wikimedia.org/r/161516",1411503450,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 161613 had a related patch set uploaded by Alex Monk:
+Style required but currently-invalid parameters on the template dialog
+
+https://gerrit.wikimedia.org/r/161613",1411164893,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"**gerritadmin** wrote:
+
+Change 161516 had a related patch set uploaded by Alex Monk:
+Make InputWidget mixin FlaggedElement
+
+https://gerrit.wikimedia.org/r/161516",1411155876,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+VisualEditor: Highlight missing parameters in template dialog when complaining about them,"Possible options:
+
+* Put a red(?) ring/border around the field
+* Put a red(?) ring/border around the field's label
+* Make the field's indicator red(?)
+* Make the field's background red(?)
+
+This class we'd toggle on/off should probably be in OOUI.",1410985084,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yd4kojpa26xd52r2dadr,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","screenshot
+
+Environment- Test2, beta, production
+
+Highlight a citation and select any text style from the drop-down. I get ""Uncaught TypeError: Cannot read property 'getSurface' of null"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14829}",1410886020,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_description,invalid
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation",This three year old task was probably fixed a long time ago.,1519405233,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","(In reply to Rummana Yasmeen from comment #4)
+> (In reply to Ritu Swain from comment #3)
+> > (In reply to Rummana Yasmeen from comment #1)
+> > > I could reproduce it while applying the text style, but the heading styles
+> > > on Citation,your screenshot also matches with the later case.
+> > 
+> > Rummana,it happens when the citation is highlighted and i change the text
+> > style to anything(not just Heading). In the screenshot, i had changed the
+> > style from paragraph to Heading, while the citation was highlighted.
+> 
+> Ritu, yes that is what I am referring to by ""applying Heading Style"" which
+> includes any of those heading formats (Heading,sub-heading 1 etc). By ""Text
+> style"", I thought you are referring to text formatting (Bold/Italic etc),
+> which I think is not how you reproduced this issue?
+
+i am not in front of my system to actually check it. but yes by ""Text Style"" i meant the headings and not the font styles.",1410901242,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","(In reply to Ritu Swain from comment #3)
+> (In reply to Rummana Yasmeen from comment #1)
+> > I could reproduce it while applying the text style, but the heading styles
+> > on Citation,your screenshot also matches with the later case.
+> 
+> Rummana,it happens when the citation is highlighted and i change the text
+> style to anything(not just Heading). In the screenshot, i had changed the
+> style from paragraph to Heading, while the citation was highlighted.
+
+Ritu, yes that is what I am referring to by ""applying Heading Style"" which includes any of those heading formats (Heading,sub-heading 1 etc). By ""Text style"", I thought you are referring to text formatting (Bold/Italic etc), which I think is not how you reproduced this issue?",1410897811,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","(In reply to Rummana Yasmeen from comment #1)
+> I could reproduce it while applying the text style, but the heading styles
+> on Citation,your screenshot also matches with the later case.
+
+Rummana,it happens when the citation is highlighted and i change the text style to anything(not just Heading). In the screenshot, i had changed the style from paragraph to Heading, while the citation was highlighted.",1410896613,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","(In reply to Rummana Yasmeen from comment #1)
+> I could not reproduce it while applying the text style, but the heading styles
+> on Citation,your screenshot also matches with the later case.",1410890520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot read property 'getSurface' of null"" when applying a heading format on citation","I could reproduce it while applying the text style, but the heading styles on Citation,your screenshot also matches with the later case.",1410890503,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5ngxnua7ghoiwyqztxbu,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a citation in the page
+3.Now click outside the page
+
+Observed Result:
+The Cite option and the Re-use option inside it remains enabled in the toolbar
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14780}",1410820020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o2nuawja3gd5ensyabpx,task_description,resolved
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,Verified the fix in production,1411682461,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,Verified the fix in test2,1411081667,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,Verified the fix in Betalabs,1410984894,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,"Change 160556 merged by jenkins-bot:
+Check whether there is a range selected when enabling/disabling re-use citation tool
+
+https://gerrit.wikimedia.org/r/160556",1410823383,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside,"Change 160556 had a related patch set uploaded by Alex Monk:
+Check whether there is a range selected when enabling/disabling re-use citation tool
+
+https://gerrit.wikimedia.org/r/160556",1410823175,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o2nuawja3gd5ensyabpx,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","size invalid message shown
+
+Environment- Test2, beta
+
+1> Go to media settings dialog for any image.
+2>Go to Advanced Settings -> In Image size, click on custom and change its size to 0x0px.Notice message saying “Size values are invalid” shows up under the Make Full size button.
+3> Now choose a different image and for that image repeat steps #2.Notice “Size values are invalid” does not show up.
+
+Also if the image size is invalid then the insert button should get disabled, preventing the user from inserting it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14762}",1410809520,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_description,resolved
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","Not pulled through yet, but will be.",1412646271,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 164784 merged by jenkins-bot:
+Emit change event when dimensions change in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/164784",1412632008,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 164784 had a related patch set uploaded by Mooeypoo:
+Emit change event when dimensions change in MediaSizeWidget
+
+https://gerrit.wikimedia.org/r/164784",1412536024,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","When the image size is default, inserting a non-numeric char changes it to custom.And if i keep entering non-numerics, then it gives the message ""Size values are Invalid"", but the ""Insert"" button stays active.
+
+It gets disabled only when you further make any changes to the settings. for ex-uncheck the “Wrap text around this item” checkbox or change the Image type to Basic /Frameless.Notice when any change is made to the settings then only the Insert button gets disabled and not when an invalid size is detected.",1411665315,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","(In reply to Rummana Yasmeen from comment #9)
+> Right now, it is not doing what you are suggesting here,the widget just does
+> not let you type anything when you try to input 0 and ""not"" making it
+> ""default""
+
+It's making it default, which erases the visible values. Technically it does what I explained; practically it does what you say. It's the same thing, but different user experiences.
+
+I am not sure if it's right to change the current behavior on that, though.
+
+> But, this is what it is doing right now.It is changing the value
+> automatically to default when user inputs non-numeric character.So, I
+> suggested to have similar behavior for both cases.
+
+I see what you're saying, but my point is that there's a difference conceptually between the two cases, so I think it's okay that the two behaviors are different two.
+
+When a user inserts ""0"" value, they likely meant for the image to have no dimensions, which effectively means it is defaulted.
+
+When a user inserts a non-numeric letter like ""a"" or ""-"" it is very likely that it's an error and even if it's not, we have no way of knowing what the user meant. Hence, we don't assume anything and instead we mark the values as ""invalid"".",1411066989,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","(In reply to Moriel Schottlender from comment #8)
+> We didn't want to force an input on the user, which is why non-numeric input
+> is allowed (but invalid.) The only problem with 0's is that practically
+> speaking, an empty input and 0 are more or less the same, so 0 (or empty)
+> assumes the user *meant* to say they don't want to set values -- which means
+> they wanted to go with ""default"".
+
+Right now, it is not doing what you are suggesting here,the widget just does not let you type anything when you try to input 0 and ""not"" making it ""default""
+
+> 
+> Changing the value automatically when the user inputs a non-numeric
+> character can be annoying if it was done by mistake. If I want to type 156
+> and I accidentally type 15t, it wouldn't be very comfortable to have the
+> widget automatically make my values into default.
+
+But, this is what it is doing right now.It is changing the value automatically to default when user inputs non-numeric character.So, I suggested to have similar behavior for both cases.
+
+> 
+> I think that the 0-to-default makes sense, but the other behavior will be
+> more of a hinderance to the user than help.",1411065711,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","We didn't want to force an input on the user, which is why non-numeric input is allowed (but invalid.) The only problem with 0's is that practically speaking, an empty input and 0 are more or less the same, so 0 (or empty) assumes the user *meant* to say they don't want to set values -- which means they wanted to go with ""default"".
+
+Changing the value automatically when the user inputs a non-numeric character can be annoying if it was done by mistake. If I want to type 156 and I accidentally type 15t, it wouldn't be very comfortable to have the widget automatically make my values into default.
+
+I think that the 0-to-default makes sense, but the other behavior will be more of a hinderance to the user than help.",1411008386,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","Right now, if you try to input 0 , the widget just does not let you to enter it, but as soon as you type some non numeric character, it automatically sets to default size , I think both cases should have same action: set to default size.",1411002564,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 160790 merged by jenkins-bot:
+Set size to default on 0 value
+
+https://gerrit.wikimedia.org/r/160790",1410983569,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px",I can still reproduce this on Betalabs.,1410982122,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 160789 merged by jenkins-bot:
+Validate size widget when activating/deactivating apply button
+
+https://gerrit.wikimedia.org/r/160789",1410911669,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 160790 had a related patch set uploaded by Mooeypoo:
+Set size to default on 0 value
+
+https://gerrit.wikimedia.org/r/160790",1410893461,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","**gerritadmin** wrote:
+
+Change 160789 had a related patch set uploaded by Mooeypoo:
+Validate size widget when activating/deactivating apply button
+
+https://gerrit.wikimedia.org/r/160789",1410893393,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] In media dialog, ""Size values are invalid"" message does not show up, when choosing a different image and then setting its size to 0 x 0 px","Created attachment 16474
+size invalid message not shown when choosing a different image
+
+**Attached**: {F14764}",1410809614,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ne77k6a4n7agmzuuryr2,task_subcomment,NA
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog","Environment- Test2, beta
+
+1> Go to Media Search dialog, it opens with the input box populated with the user name in it.
+2> I get JS console error Uncaught TypeError: undefined is not a function   , while the media search is still in progress .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1410808800,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-2jzgntengke75ccufbeh,task_description,declined
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog","(In reply to James Forrester from comment #3)
+> This was fixed in MediaWiki core as of wmf4 (to be released tomorrow to
+> MediaWiki.org).
+
+James is talking about a different thing that was fixed in wmf4.
+
+This bug is caused by an issue in jQuery with canceling JSONP requests. It can only be fixed if jQuery fixes it upstream, and I don't think that will happen.
+
+Closing as WONTFIX for lack of a RESOLVED UPSTREAM status.",1413386695,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2jzgntengke75ccufbeh,task_subcomment,NA
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog",This was fixed in MediaWiki core as of wmf4 (to be released tomorrow to MediaWiki.org).,1413386333,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2jzgntengke75ccufbeh,task_subcomment,NA
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog","This is a problem with the API in general, and while it is throwing an error, it shouldn't actually affect anything in the system -- that is, this error is stating that the API is unhappy about uselang variable, but the system is still working through the responses properly.",1413386204,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-2jzgntengke75ccufbeh,task_subcomment,NA
+"VisualEditor: [Regression wmf21] ""Uncaught TypeError: undefined is not a function"", when using media search dialog","Created attachment 16625
+screenshot
+
+1> Open insert -> Media. click ""cancel""to close the dialog.
+2> reopen the media search dialog,JS console error at this point.
+
+**Attached**: {F14759}",1412014027,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-2jzgntengke75ccufbeh,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"The list of allowed skins of the BetaFeatures extension (in $prefs[$key]['requirements']['skins']) is not displayed in the HTML code.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-betafeatures",1410615900,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_description,resolved
+BetaFeatures: Warnings about allowed skins are not displayed,Thank you!,1411233187,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Change 161629 merged by jenkins-bot:
+Display allowed skins if and only if the current skin is not allowed
+
+https://gerrit.wikimedia.org/r/161629",1411233187,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"(In reply to Seb35 from comment #9)
+> Yes, I didn’t describe exactly the bug: the allowed skins were never
+> displayed in the HTML, neither when the current skin is an allowed skin,
+> neither when the current skin is not an allowed skin.
+> 
+> With the patch, the JS warning is now correctly triggered. When a blacklist
+> is specified for a beta feature, it is always added in the HTML.
+> 
+> For the skin, you are right, it should be displayed only when the current
+> skin is not allowed. See next patch.
+
+This looks good, thank you. :-)",1411170480,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Change 161629 had a related patch set uploaded by Seb35:
+Display allowed skins if and only if the current skin is not allowed
+
+https://gerrit.wikimedia.org/r/161629",1411170016,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Yes, I didn’t describe exactly the bug: the allowed skins were never displayed in the HTML, neither when the current skin is an allowed skin, neither when the current skin is not an allowed skin.
+
+With the patch, the JS warning is now correctly triggered. When a blacklist is specified for a beta feature, it is always added in the HTML.
+
+For the skin, you are right, it should be displayed only when the current skin is not allowed. See next patch.",1411169281,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"I'm… confused.
+
+The purpose of the Beta Feature warning section is to inform you why enabling it won't be useful to you.
+
+I.e.:
+
+* if you don't have JS working, tell you if it needs JS;
+* if you don't use Vector, tell you if it only works for that skin;
+* if you don't have Internet Explorer, tell you if it only works in that browser.
+
+If none of these are met (i.e., it should work), the warnings should not appear.
+
+The title of this bug suggests that this is not understood.",1411162604,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Hah, fascinating. Okay, let's do this then.
+
+Should we mark this as resolved after merging the patch, or do you want to actually display this information?",1411161898,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Change 160213 merged by jenkins-bot:
+Display the required skins
+
+https://gerrit.wikimedia.org/r/160213",1411161865,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Thanks for your comment, I didn’t paid attention to the JS warning who disappeared, but by further investigating:
+1/ it is a feature to hide the warning ""JS is required"" when JS is enabled (see resources/betafeatures.js, there is the comment ""We're here so JavaScript works""), and
+2/ it was previously displayed because no skins were found in BetaFeaturesHooks::getPreferences (there are warnings in the debug log ""[BetaFeatures] The visualeditor-enable BetaFeature has no valid skins installed.""), which results not to add these beta features in the wgBetaFeaturesFeatures JS variables, which results betafeatures.js don’t loop into these beta features and don’t hide the JS warning (and don’t test if the browser is supported).
+
+So the bug is deeper I first thought, and I find it worth fixing it. But I aggree the skins requirements are not necessary and it is a change from the current behaviour, so I hide them in the LESS file (to keep consistency with current behaviour).",1411080422,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Fixing this bug will result in big red warnings being displayed under most BetaFeatures. The warnings also mention the hidden Minerva skin (e.g. for VisualEditor). Furthermore, they override the warnings about JavaScript being required.
+
+The bug is real and the fix is correct, but I'm pretty sure people started relying on the bug being a feature, and fixing this brings out a few more bugs. The existing beta features need be reviewed in context of this first, and I have no idea who's going to do it. :/",1411073812,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"The current state on the Wikimedia project is without the names of the required skins. In the case it is wanted to keep the current state (for Wikimedia and/or for the master branch of BetaFeatures), this feature can be hidden with CSS, similarly to the browser requirements, by editing BetaFeatures/resources/betafeatures.less.",1410617440,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"Change 160213 had a related patch set uploaded by Seb35:
+Display the required skins
+
+https://gerrit.wikimedia.org/r/160213",1410616678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+BetaFeatures: Warnings about allowed skins are not displayed,"The problem comes from BetaFeaturesHooks::getPreferences, in the code
+
+  $prefs[$key]['requirements']['skins'] = array_intersect( $prefs[$key]['requirements']['skins'], Skin::getAllowedSkins() );
+
+because Skin::getAllowedSkins() is an array key-value and we want the key and not the value, so it should be used array_keys( Skin::getAllowedSkins() ).
+
+I prepare the patch.",1410616013,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-qwgyzixmq7444faqzt2k,task_subcomment,NA
+VisualEditor: Copying and pasting a template causes comment to be inserted in Chrome on Windows due to broken native clipboard behaviour,"**Author:** `thalia.chan`
+
+**Description:**
+Copied the heading ""Lilypond source"" and the line of text below from this page: https://commons.wikimedia.org/wiki/File:C_sharp_and_double_sharp_music.svg?veaction=edit
+
+Pasted it into a similar page, open in a different tab, and a grey circle containing a question mark appeared at the end, which I am reliably informed is a comment. (Abandoned my edit in the end, so there's nothing to clean up.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Platform**: PC",1410569820,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-u3fli75nyhvezrtxd2vp,task_description,resolved
+VisualEditor: Copying and pasting a template causes comment to be inserted in Chrome on Windows due to broken native clipboard behaviour,"**gerritadmin** wrote:
+
+Change 160179 merged by jenkins-bot:
+Strip Start/EndFragment comments from paste
+
+https://gerrit.wikimedia.org/r/160179",1410800265,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-u3fli75nyhvezrtxd2vp,task_subcomment,NA
+VisualEditor: Copying and pasting a template causes comment to be inserted in Chrome on Windows due to broken native clipboard behaviour,"**gerritadmin** wrote:
+
+Change 160179 had a related patch set uploaded by Esanders:
+Strip Start/EndFragment comments from paste
+
+https://gerrit.wikimedia.org/r/160179",1410573171,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-u3fli75nyhvezrtxd2vp,task_subcomment,NA
+VisualEditor: Copying and pasting a template causes comment to be inserted in Chrome on Windows due to broken native clipboard behaviour,"The copied element here is just the LilyPond source template. Confirmed this bug in Win8/Chrome but not Ubuntu/Chrome. The comment inserted is <!-- EndFragment --> and comes from the clipboard API, not CE paste.",1410571230,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-u3fli75nyhvezrtxd2vp,task_subcomment,NA
+Errors in one module can affect other modules via $.ready,"This is not really a ResourceLoader bug but serious enough that some workaround is needed and that probably has to be done via RL.
+
+Due to jQuery bug #10251 [1] (wontfixed), errors in a jQuery domready handler prevent all subsequently added domready handlers from running. This means that errors in less reliable scripts like gadgets or user scripts can break any production code that is loaded after them and relies on $.ready (which is true for most extensions).
+
+
+[1] http://bugs.jquery.com/ticket/10251
+",1410534420,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-wfaki2636ucppxoiacm4,task_description,declined
+Errors in one module can affect other modules via $.ready,"* This applies to any event handler, not just DOMContentLoaded. E.g. click events: http://jsfiddle.net/mj8yeLmy/. Most instances of domready-handlers should probably use a `mw.hook` if they want to work as expected in the future of partial documents changing without refresh (as is already happening in LiquidThreads, VisualEditor, Flow and core's LivePreview).
+* Regarding gadgets not breaking, the same policy as extensions applies. Extensions can interfere with core, just as gadgets. If they misbehave with a certain language/wikiproject/skin combination; that should be fixed, or the relevant module excluded from running in that case, or disabled/not-enabled by those users (it's common for gadgets to say in their description ""Vector-only""). Can you given an example of a gadget causing errors in a certain skin-browser combination? That's relatively rare in my experience (except for outdated copies of gadgets on small wikis; this is generally addressed by loading the gadget from commons/meta/enwiki/mworg directly). It's generally fixed quickly when reported to gadget maintainers.
+* I've seen gadgets affecting the DOM of MediaWiki core and extension modules plenty. It's not rare.
+
+I'm still open to exploring a workaround on our side (in MediaWiki core). Note however that:
+* The $.ready promise does not expose its internal `jQuery.Callbacks` instance. Neither does it keep track of which have fired.
+* domready handlers should become rare over time. There are very few use cases left for it in our environment.
+* Beware the inconsistency with other event handlers.",1435888619,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wfaki2636ucppxoiacm4,task_subcomment,NA
+Errors in one module can affect other modules via $.ready,"* This applies to any event handler, not just DOMContentLoaded. E.g. click events: http://jsfiddle.net/mj8yeLmy/. Most instances of domready-handlers should probably use a `mw.hook` if they want to work as expected in the future of partial documents changing without refresh (as is already happening in LiquidThreads, VisualEditor, Flow and core's LivePreview).
+* Regarding gadgets not breaking, the same policy as extensions applies. Extensions can interfere with core, just as gadgets. If they misbehave with a certain language/wikiproject/skin combination; that should be fixed, or the relevant module excluded from running in that case, or disabled/not-enabled by those users (it's common for gadgets to say in their description ""Vector-only""). Can you given an example of a gadget causing errors in a certain skin-browser combination? That's relatively rare in my experience (except for outdated copies of gadgets on small wikis; this is generally addressed by loading the gadget from commons/meta/enwiki/mworg directly). It's generally fixed quickly when reported to gadget maintainers.
+* I've seen gadgets effecting the DOM of MediaWiki core and extension modules plenty. It's not rare.
+
+I'm still open to exploring a workaround on our side (in MediaWiki core). Note however that:
+* The $.ready promise does not expose its internal `jQuery.Callbacks` instance. Neither does it keep track of which have fired.
+* domready handlers should become rare over time. There are very few use cases left for it in our environment.
+* Beware the inconsistency with other event handlers.",1420714765,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wfaki2636ucppxoiacm4,task_subcomment,NA
+Errors in one module can affect other modules via $.ready,"See the blocked bug (T72756) for an example.
+
+Broken code should definitely not be silenced; the jQuery bug is not about silencing but limiting the effect of an error to the code which caused it. Which is a good practice in general, but I can see how jQuery has no easy way of following it in this case, without causing massive B/C breaks in promise behavior (although special-casing $.ready might be easier).
+
+This wouldn't be a problem on Wikimedia sites if there was an expectation for gadgets to not break, but my experience on medium-to-small wikis is that a few gadget-skin-browser combinations are broken at any given time, so seeing errors in the console in itself is not surprising, and if a completely unrelated product starts misbehaving, gadget maintainers are not going to attach any significance to it. So I'm not sure ""loudly"" is a fair description of a gadget throwing an exception.
+
+I don't think the same if true for gadgets messing up the DOM or otherwise affecting other modules; while in theory it's possible for that to happen in such a way that the gadget is not suspected, in practice I haven't ever seen that happening.
+
+One way to handle this (that could be inside or outside of jQuery) is to set up a timeout to check whether all domready handlers were executed, and force execution manually if it was broken by an exception. That would not stop the exception from being thrown and reported, but would limit its effect to the domready handler which caused it.",1418069344,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-wfaki2636ucppxoiacm4,task_subcomment,NA
+Errors in one module can affect other modules via $.ready,"An example of where this happened would be useful to assess what kind of code did this, who the affected users were, how and by whom it was addressed, etc.
+
+Initially I'm inclined to agree with jQuery and, here too, consider this an invalid bug. Broken code should not be silenced. There's a 1001 ways for gadgets and user scripts to break unrelated modules. That's the DOM for you. 
+
+This problem is in many ways similar to extensions vs MediaWiki core. When it goes wrong, the bug is reported, the broken module is found and either fixed or temporarily disabled until a maintainer can look into it. I think it's acceptable to encourage the community to apply a similar policy to their gadgets.
+
+If a gadget is broken, you can't leave it enabled and expect everything to degrade gracefully. There's too many asynchronous paths for code to take that absorbing it would be impossible (or unpractical). That's a responsibility gadget authors carry and should be familiar with if they've been given such access. And even if we could, trying to absorb it is in my opinion not we should want to achieve.
+
+I'm all for graceful degradation and often try to address hurdles and make user experiences as smooth as we can.
+
+But in cases like this, I'm all for letting it fail loudly. That's what errors are for.",1418060154,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wfaki2636ucppxoiacm4,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"double Toolbars in VE
+
+Environment- Test2, beta
+
+1> switch from Edit beta mode to Read mode notice the toolbar has slide down and is still visible in the Read mode.
+
+2> Click on Edit beta again,the Editor is displayed with two toolbars.See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70770
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70782
+
+**Attached**: {F15240}",1410526140,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_description,resolved
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Verified the fix in production,1411681191,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,verified the backport in test2,1411666888,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162497 merged by Catrope:
+Don't drop 1px rects for FocusableNodes if all we have is 1px rects
+
+https://gerrit.wikimedia.org/r/162497",1411599824,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Verified the fix in Betalabs,1411592037,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162497 had a related patch set uploaded by Catrope:
+Don't drop 1px rects for FocusableNodes if all we have is 1px rects
+
+https://gerrit.wikimedia.org/r/162497",1411513254,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162360 merged by jenkins-bot:
+Don't drop 1px rects for FocusableNodes if all we have is 1px rects
+
+https://gerrit.wikimedia.org/r/162360",1411511065,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162359 merged by jenkins-bot:
+Tolerate null boundingRect in all code paths in DesktopContext#updateDimensions
+
+https://gerrit.wikimedia.org/r/162359",1411510662,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162360 had a related patch set uploaded by Catrope:
+Don't drop 1px rects for FocusableNodes if all we have is 1px rects
+
+https://gerrit.wikimedia.org/r/162360",1411499064,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"**gerritadmin** wrote:
+
+Change 162359 had a related patch set uploaded by Catrope:
+Tolerate null boundingRect in all code paths in DesktopContext#updateDimensions
+
+https://gerrit.wikimedia.org/r/162359",1411499058,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"Ok thanks so much Ritu! I can now reproduce it.The following error appears in the console as well:
+Uncaught TypeError: Cannot read property 'height' of null",1411493163,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"(In reply to Rummana Yasmeen from comment #11)
+> I cannot reproduce it following your steps.In steps 4, you mentioned to
+> repeat step 2, what change have you done in the page for the second time to
+> save it?
+
+http://youtu.be/CNqxmnconN8",1411486511,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"I cannot reproduce it following your steps.In steps 4, you mentioned to repeat step 2, what change have you done in the page for the second time to save it?",1411409958,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"This issue is reappearing.
+
+Steps-
+1> in a blank page insert a Reflist or Notelist Template.
+2> Save the page and reopen it in VE mode.
+3> Now cilck on the Read tab. 
+4> Repeat steps #2 and #3. Toolbars are getting added.",1411402650,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Verified the fix in test2,1410823905,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Verified the fix in Betalabs,1410559793,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,https://gerrit.wikimedia.org/r/160076 (the fix for bug 70770 fixes this too).,1410557788,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"Created attachment 16454
+Screenshot
+
+Ok, so I reproduced it on my user page too.This is happening when you just have the following on your page:
+
+ __NEWSECTIONLINK____NOTOC__
+
+**Attached**: {F15241}",1410557395,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"(In reply to Rummana Yasmeen from comment #4)
+> Ritu, can you share the link to the page where you are getting this, I can't
+> reproduce it either.
+
+links-:
+https://test2.wikipedia.org/wiki/User:Swainr?veaction=edit
+
+http://en.wikipedia.beta.wmflabs.org/wiki/User:Swainr?veaction=edit",1410556709,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"Ritu, can you share the link to the page where you are getting this, I can't reproduce it either.",1410553602,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,"(In reply to Roan Kattouw from comment #2)
+> I can't reproduce this. Does this also happen when you're logged out?
+
+I can reproduce it(tried with a clear cache). Yes, it happens even when i am logged out.",1410548856,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,I can't reproduce this. Does this also happen when you're logged out?,1410543555,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation,Browsers- FF and Chrome. Couldn't test on Safari.,1410526326,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-rurgi2fk663rrehd4j3x,task_subcomment,NA
+VisualEditor: Write unit tests for dm.Converter's use of dm.Model APIs,"There are no unit tests exercising features of dm.Converter that are currently unused by our node types, like returning null/undefined from toDataElements to trigger alienation, returning one a different type from toDataElements, returning an annotation type from a node's toDataElements, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410487620,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rcih7yd7sainywzff7di,task_description,open
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"1. place cursor in large body of text in FF
+2. Cursor up then down, everything is fine
+3. Cursor right a dozen or so times, then up
+
+Then cursor jumps up and left to the same place it was after (2).
+
+Initial investigations show that disabling handling of up/down arrows makes no difference, but disabling handling of left/right does fix, so probably something to do with the surfaceObserver state?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.mozilla.org/show_bug.cgi?id=1075901",1410456540,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_description,open
+VisualEditor: Up/down arrow in Firefox broken after using left/right,Possibly not anything we can actually fix…,1412359526,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"Workaround reverted, caused bug 71580 (ugly-looking ""NS_ERROR_FAILURE"" exceptions in some cases).",1412342877,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"More ""worked around"" than actually fixed, but…",1412266880,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"**gerritadmin** wrote:
+
+Change 164162 merged by jenkins-bot:
+ve.ce.Surface: Magic workaround for broken Firefox cursoring
+
+https://gerrit.wikimedia.org/r/164162",1412261583,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"**gerritadmin** wrote:
+
+Change 164162 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ce.Surface: Magic workaround for broken Firefox cursoring
+
+https://gerrit.wikimedia.org/r/164162",1412193248,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1075901,1412191505,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"Calling nativeSelection.collapseToStart() seems to magically fix the erroneous behavior (http://jsfiddle.net/ybawstce/3/), we can probably use that as a workaround for selections that are already collapsed.
+
+(I see no neat way to fix non-collapsed ones; randomly calling some other Selection methods might help, but they probably won't be no-ops. These are a smaller problem anyway and can wait for Firefox to fix their bug.)
+
+I'm filing this upstream.",1412190573,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,"Minimal test case: http://jsfiddle.net/ybawstce/1/
+
+(This will throw errors in some edge cases, but that's not the point; try arrowing around near the middle of the text.)",1412189941,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+VisualEditor: Up/down arrow in Firefox broken after using left/right,Looks like a browser bug with Firefox's native selection having inconsistent state. I'm going to try poking some more at this tomorrow and maybe file some upstream bugs.,1412119103,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-blqrlqqm7xzdi5yg7pna,task_subcomment,NA
+"VisualEditor: ContextItemWidget's ""edit"" label should be a sibling of the description","Per Ed:
+
+| FIXME: This should be a sibling of the description label, with enough space
+| left to the right of the description so it shows even if the description is
+| too wide (e.g. an external link)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410389880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rqg7uqc7ixojj2plkvbr,task_description,invalid
+"VisualEditor: ContextItemWidget's ""edit"" label should be a sibling of the description",This code has been substantially re-written since this task was created; the concern no longer applies.,1493661496,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rqg7uqc7ixojj2plkvbr,task_subcomment,NA
+"Dropdowns in the VE toolbar opening ""under"" the content area in the Chameleon skin","There is an issue in Chrome when using the VisualEditor extension. The dropdowns in the VE toolbar seem to be opening ""under"" the content area, hiding their contents.
+
+The problem is a bug in the jQuery 1.8 lib used in MW <1.24 (or a variation thereof): http://bugs.jquery.com/ticket/11635
+
+Todo: Backport the fix in jQuery 1.11.
+
+--------------------------
+**Version**: 1.23
+**Severity**: normal",1410377400,PHID-USER-cc6dswbtmstfsb4ldmit,False,PHID-TASK-uk3slh6vbmq3xu4fvsu3,task_description,resolved
+"Dropdowns in the VE toolbar opening ""under"" the content area in the Chameleon skin",Works with latest versions of VE and Chameleon skin.,1433587635,PHID-USER-cc6dswbtmstfsb4ldmit,False,PHID-TASK-uk3slh6vbmq3xu4fvsu3,task_subcomment,NA
+VisualEditor: LinkCache should also cache mw-redirect and mw-disambig statuses,"… and use them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410376320,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f6bgxahe6w7alqbxqvv6,task_description,invalid
+VisualEditor: LinkCache should also cache mw-redirect and mw-disambig statuses,... Doesn't it do this already?,1410437964,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-f6bgxahe6w7alqbxqvv6,task_subcomment,NA
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","screenshot1
+
+Environment- test2, beta, production
+
+1> open a page in VE, add a template. Add a Field name to the template, now delete that name.
+2>click to add more information again, notice  the previous field name entry is shown  in a list.
+3>  In the same Field name, type in another name , now delete that name.
+4> Repeat steps #2 and 3. Until you get the show one more field(this appears after the 4th entry). Click on it and it seems to add nothing to the existing Template data.
+Same behavior can be seen with Templates having at least 4 parameters, for ex- Reflist.
+See screenshots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14783}",1410275700,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-hrnl7scbkqiphhkzetoj,task_description,resolved
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","Issue fixed in test2, beta, production.",1412608950,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-hrnl7scbkqiphhkzetoj,task_subcomment,NA
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","**gerritadmin** wrote:
+
+Change 160500 merged by jenkins-bot:
+Template dialog: Show up to the limit of parameters, not up to the limit + 1
+
+https://gerrit.wikimedia.org/r/160500",1410911097,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hrnl7scbkqiphhkzetoj,task_subcomment,NA
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","**gerritadmin** wrote:
+
+Change 160500 had a related patch set uploaded by Jforrester:
+Template dialog: Show up to the limit of parameters, not up to the limit + 1
+
+https://gerrit.wikimedia.org/r/160500",1410808571,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hrnl7scbkqiphhkzetoj,task_subcomment,NA
+"VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries","Created attachment 16415
+screenshot2
+
+**Attached**: {F14784}",1410275763,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-hrnl7scbkqiphhkzetoj,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,"In Chrome and Internet Explorer it is perfectly possible to click repeatedly on the Save button and achieve nothing. On large portions of it (especially at the top, but you can also place the pointer exactly between the two words and get the same result) the pointer won't change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410254700,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-edczq7heipb4q3v2tcxp,task_description,resolved
+VisualEditor: Save page button is not fully clickable,"Nope. Just tried again incognito mode on IE, FF and Chrome.",1410544386,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,"(In reply to Elitre from comment #4)
+> It's not gone for me.
+
+It works for me. Does it work for you when you're logged out?",1410543637,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,It's not gone for me.,1410537943,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,Yes.,1410461670,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,This is probably the bug fixed by 2aebe8054eed2516ac06c62101f2793f29c416aa.,1410267366,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+VisualEditor: Save page button is not fully clickable,"Actually, Safari is probably the only browser where this doesn't happen. You can reproduce on all the 3 buttons near the Save one, but not on the dialogs' ones.",1410255470,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-edczq7heipb4q3v2tcxp,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"The LST markers <section begin=""2011-07-25"" /> and <section end=""2011-07-25"" /> used to be unparsed, but now that Parsoid parses them to <meta>s they're uneditable. Boo.
+
+(The actual transclusion {{#lst:Foo|Bar}} as a parser function ""just works"".)
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1410209220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_description,stalled
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"how would you activate the alienextensionnode editor/module on a Wiki? I've played around with the $wgVisualEditorPluginModules array, but cannot get it to work.",1467931922,PHID-USER-gqtrt6xysxqoow52i7fc,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"Ok, it seems to me that the alienextensionnode editor is activated on the Page: namespace but not on the main namespace (or something like that).
+
+But as we should definitely create an editing widget for this tag, we will fix this issue at the same time.",1467874769,PHID-USER-5paybpgtxjrhikdos3p5,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"I tried this page and unfortunately it was just changed today so that the <section> tag at the beginning was removed; so I created another page on that Wiki with a section tag:
+
+[[ https://en.wikisource.org/w/index.php?title=Sectiontest&veaction=edit | https://en.wikisource.org/w/index.php?title=Sectiontest&veaction=edit ]]
+
+unfortunately I don't see that the section tag is handled at all; it doesn't seem to be rendered. Can you take a look?",1467836993,PHID-USER-gqtrt6xysxqoow52i7fc,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"I tried this page and unfortunately it was just changed today so that the <section> tag at the beginning was removed; so I created another page on that Wiki with a section tag:
+
+[[ https://en.wikisource.org/w/index.php?title=Sectiontest&action=edit | https://en.wikisource.org/w/index.php?title=Sectiontest&action=edit ]]
+
+unfortunately I don't see that the section tag is handled at all; it doesn't seem to be rendered. Can you take a look?",1467832744,PHID-USER-gqtrt6xysxqoow52i7fc,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"It seems to me that the latest versions of VisualEditor and Parsoid provides basic support (with an editing UI) for the <section> tag.
+
+For example: https://en.wikisource.org/wiki/Page:Dictionary_of_Christian_Biography_and_Literature_(1911).djvu/161?veaction=edit (there is a <section begin=""""> tag at the beginning of the page's body.
+
+But we should definitely create a nicer UI for them.",1467790836,PHID-USER-5paybpgtxjrhikdos3p5,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,will this task be worked again?,1467783508,PHID-USER-gqtrt6xysxqoow52i7fc,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"**gerritadmin** wrote:
+
+Change 162652 had a related patch set uploaded by Jforrester:
+[WIP] In VisualEditor, show <section> elements and let them be edited
+
+https://gerrit.wikimedia.org/r/162652",1411581215,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"**gerritadmin** wrote:
+
+Change 159182 abandoned by Jforrester:
+[WIP] Show LST <section> elements and let them be edited
+
+Reason:
+Moving to LST repo.
+
+https://gerrit.wikimedia.org/r/159182",1411581079,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers,"**gerritadmin** wrote:
+
+Change 159182 had a related patch set uploaded by Jforrester:
+[WIP] Show LST <section> elements and let them be edited
+
+https://gerrit.wikimedia.org/r/159182",1410211162,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-abnrntzw5wtc5wukwim2,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button","Steps to reproduce:
+
+1.Open a page with VE
+2.Open Media Settings dialog for a Frameless/Basic type image which does not have ""Border"" set to it.
+3.Now check the ""Border"" checkbox
+
+
+Observed Result:
+It does not enable the ""Apply Changes"" button in the media Settings dialog
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1410206160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ix3up4zzzosiimtj4nop,task_description,resolved
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button",Verified the fix in production,1411071344,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button",Verified the fix in test2,1410553926,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button","Released in OOjs 1.1.1, now in MW-core etc.",1410396413,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button",Should be fixed by https://gerrit.wikimedia.org/r/#/c/159639/,1410395270,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf21] Checking ""Border"" in media settings dialog is not enabling ""Apply changes"" button","This is due to an OOjs bug.
+
+>>> OO.compare( { foo: 3 }, { foo: 4 } )
+false
+
+>>> OO.compare( { foo: false }, { foo: true } )
+true
+
+Because we have special cases for 'number' and 'string' but not 'boolean'.",1410394010,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ix3up4zzzosiimtj4nop,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","This is similar to Bug 69711.
+
+Steps to reproduce:
+
+1.  Type some text:  ""Foo bar baz bat""
+
+2.  Add a citation.
+
+3.  Finish typing the sentence.
+
+6.  Oops, where did the citation go?
+
+
+Results:
+
+When you exit the ref dialog, the new ref text remains highlighted, and typing results in it being overwritten by your next character.  
+
+Expectation:  after I've made a ref, de-select the ref and put the cursor at the end, so I can keep writing or add a second ref.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410205260,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_description,open
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","> Do you think that design decision should be reversed
+
+Yes.  Unless I'm likely to need that thing to be selected when I'm done (e.g., if I'm likely to create a link *and* italicize it – which isn't a likley case), then I want it to be de-selected by default.",1410217088,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","(In reply to Mike Christie from comment #4)
+> On reflection I agree; ""Save and add another"" isn't a common case.  I'll see
+> if I run into situations where that would be a useful option and will post
+> an enhancement request if I do.
+
+Thanks! :-)",1410213405,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","On reflection I agree; ""Save and add another"" isn't a common case.  I'll see if I run into situations where that would be a useful option and will post an enhancement request if I do.",1410208984,PHID-USER-ufjbf3qatjamiwoal5fp,True,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","(In reply to Mike Christie from comment #2)
+> I wouldn't want to make a blanket statement, and I can recall situations
+> where the fact that an object remains selected was useful -- going straight
+> back into a cite to fix an error I just realized I made, for example.  For
+> some things, such as links, I think it's definitely better to deselect --
+> it's absolutely normal for a user to want to continue typing.  For
+> templates, I can see an argument for keeping the selection.  Citations seem
+> to me more like links than templates in this way.
+> 
+> I think the design question is: what would a user who is expert in VE want
+> the system to do to maximize productivity?  I think the answer is going to
+> be to leave it unselected more often than not.
+
+That's a reasonable way of looking at it; I think I agree. There are some possible issues with block images (where, especially if you have a long infobox on a short screen, the content may have been inserted off-screen), but maybe we should optimise for the most common case? Will ask others on the team to weigh in, but broadly this seems sensible. Thanks!
+
+
+> One other thought: just as there's a ""Save"" and also a ""Save and new"" pair
+> of buttons in some interfaces, there might be a ""Save and add another
+> citation"" button on the interface, or something along those lines.  But
+> perhaps that's a separate enhancement suggestion.
+
+(Yes, this should be a new bug, but…)
+
+Hmm. I think that ""Save and also add a new one"" is really rare for inserting content, and really confusing. Wouldn't it be better to have easily-rememberable keyboard shortcuts instead?",1410208394,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","I wouldn't want to make a blanket statement, and I can recall situations where the fact that an object remains selected was useful -- going straight back into a cite to fix an error I just realized I made, for example.  For some things, such as links, I think it's definitely better to deselect -- it's absolutely normal for a user to want to continue typing.  For templates, I can see an argument for keeping the selection.  Citations seem to me more like links than templates in this way.
+
+I think the design question is: what would a user who is expert in VE want the system to do to maximize productivity?  I think the answer is going to be to leave it unselected more often than not.
+
+One other thought: just as there's a ""Save"" and also a ""Save and new"" pair of buttons in some interfaces, there might be a ""Save and add another citation"" button on the interface, or something along those lines.  But perhaps that's a separate enhancement suggestion.",1410207927,PHID-USER-ufjbf3qatjamiwoal5fp,True,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead","In VE, new stuff always gets selected after you insert it – images, references, templates, comments, …. Do you think that design decision should be reversed, or do you think that there is something special about references that deserves different treatment?",1410206978,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6u4gabtaq5rfue7qj2wa,task_subcomment,NA
+"VisualEditor: When CE gets re-enabled, the cursor always jumps to the beginning index of the first line irrespective of where user wanted to position it","Steps to reproduce:
+
+
+1.Open a page with VE which has some text in it
+2.Place somewhere outside the CE to disable it
+3.Now click at the end of a text to place your cursor on that position of article to make an edit
+
+Observed Result:
+The cursor jumps to the beginning of the first line of the article.
+
+
+Envionment:Betalabs,test2,production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410200160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-w7b6jdh4p5xzbufd7owv,task_description,open
+VisualEditor:  Insert > References list is very large in Firefox,"This may be the opposite of bug 68226:  
+
+The References List dialog in Firefox 31 on my Mac is the expected width, but it is the full height of the screen.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70317",1410150120,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-eng4eygt5qljaa7eds7p,task_description,resolved
+VisualEditor:  Insert > References list is very large in Firefox,Verified the fix in production,1411681735,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-eng4eygt5qljaa7eds7p,task_subcomment,NA
+VisualEditor:  Insert > References list is very large in Firefox,"Yeah, part of Roan's fixes.",1411417195,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eng4eygt5qljaa7eds7p,task_subcomment,NA
+VisualEditor:  Insert > References list is very large in Firefox,"Can't reproduce using Firefox 32 on Windows 7, nor any other browser. Is this still happening for you? I think it was fixed along with other dialog sizing bugs in OOjs UI recently.",1411414227,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-eng4eygt5qljaa7eds7p,task_subcomment,NA
+VisualEditor:  Insert > References list is very large in Firefox,Is this another OOUI breakage?,1410202929,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eng4eygt5qljaa7eds7p,task_subcomment,NA
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"I was cutting & pasting sentences and it worked nearly flawlessly, including the references! :)
+
+Though, somehow during cut & paste of a reference to the end of a sentence, the period ended up inside the wiki link:
+
+https://en.wikipedia.org/w/index.php?title=Tim_Hortons&diff=624612573&oldid=624559527
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410140640,PHID-USER-lzhljhpbm3qfphvqyill,False,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_description,resolved
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"Yup, good spot.",1491407105,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_subcomment,NA
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"I think this has been resolved a while ago by the ""active link"" functionality. It is still possible to paste things into a link rather than after it, but it should be clear that this is what you're doing.
+
+{F7267037}
+
+{F7267050}",1491406979,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_subcomment,NA
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"If you're typing at the end of a link and press ' ' (space), '.', or one of a bunch of other characters defined in Unicode as word-separators, we terminate the link before the new character.
+
+It's possible, however, to insert a sequence with a '.' or similar via rich copy-and-paste; I'm not sure if we should strip it here or not. Seems a bit magical…",1410203368,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_subcomment,NA
+VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s),"it's possible there is some user error involved, although see if this can be reproduced...",1410141067,PHID-USER-lzhljhpbm3qfphvqyill,False,PHID-TASK-k3frejgdyxsgnsdn5zqw,task_subcomment,NA
+VisualEditor: Inserted link annotations don't take pre-annotations (but inserted language annotations do),"cmd K (and link button) after a space lost previous italic or/and bold formatting
+
+Mac OS/X Chrome and Safari
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1410121020,PHID-USER-hhw22zfd2xzrsyc22lp5,False,PHID-TASK-wkcjdg26ppvadj2qcmne,task_description,resolved
+VisualEditor: Inserted link annotations don't take pre-annotations (but inserted language annotations do),"Change 160216 merged by jenkins-bot:
+ve.ui.AnnotationInspector: Apply existing annotations to inserted content
+
+https://gerrit.wikimedia.org/r/160216",1410802184,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wkcjdg26ppvadj2qcmne,task_subcomment,NA
+VisualEditor: Inserted link annotations don't take pre-annotations (but inserted language annotations do),"Change 160216 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ui.AnnotationInspector: Apply existing annotations to inserted content
+
+https://gerrit.wikimedia.org/r/160216",1410623352,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wkcjdg26ppvadj2qcmne,task_subcomment,NA
+VisualEditor: Inserted link annotations don't take pre-annotations (but inserted language annotations do),"> (but inserted language annotations do)
+
+That's because they don't insert any content, unlike link annotations.",1410623326,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wkcjdg26ppvadj2qcmne,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,"Steps to reproduce:
+
+1.Open a page with VE
+2.Click on the link inspector icon from the toolbar
+
+
+Observed Result:
+The link inspector is not opening up in the first session
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409954460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u7wmfggaowz3nwqsib4h,task_description,resolved
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,Verified the fix in production,1411070671,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,Verified the fix in Betalabs,1410197975,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,"**gerritadmin** wrote:
+
+Change 158807 merged by jenkins-bot:
+Followup 67f83f1: fall back to empty string to avoid 'undefined'
+
+https://gerrit.wikimedia.org/r/158807",1409958908,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,"**gerritadmin** wrote:
+
+Change 158807 had a related patch set uploaded by Catrope:
+Followup 67f83f1: fall back to empty string to avoid 'undefined'
+
+https://gerrit.wikimedia.org/r/158807",1409956827,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session,It also happens when you try to inspect an existing link,1409954648,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u7wmfggaowz3nwqsib4h,task_subcomment,NA
+"Flow: when enabled on a subpage, doesn't show ""< grandparent | parent"" crumb trail","Compare https://www.mediawiki.org/wiki/Talk:VisualEditor/Beta_Features/Language
+with https://www.mediawiki.org/wiki/Roadmap/Archive
+
+The Flow page doesn't show the < Talk:VisualEditor | Beta_Features ""crumb trail"" to parent pages that you normally see under the page title of a subpage in a <div id=""contentSub""><span class=""subpages"">.
+
+I think includes/skins/Skin.php's subPageSubtitle() normally fabricates this.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1409952060,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-aa6mqfnkyrurwc3qf3hi,task_description,open
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"Missing template field name
+
+On any page e.g. http://en.wikipedia.beta.wmflabs.org/wiki/0.2619265827018721?veaction=edit
+
+Click Insert/Template
+
+
+Type a name like ""New template"" and click ""Add template""
+
+In the resulting box, type ""New template field"" or some such. 
+
+Click the ""Unknown field"" to add the field to the template
+
+Result should show ""New template field"" but instead is blank.  Note that a ""Remove field"" icon is in place for the invisible template field. 
+
+See screen shot comparing beta labs with test2wiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14914}",1409851740,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_description,resolved
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,Verified the fix in production,1411070490,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"Yes, working properly in Betalabs and test2",1409944422,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,Seems to be working properly in beta labs now,1409866602,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,Should be fixed on master.,1409866416,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"**gerritadmin** wrote:
+
+Change 158508 merged by jenkins-bot:
+Rename $label to $labelElement in MWParameterPage to avoid naming conflict
+
+https://gerrit.wikimedia.org/r/158508",1409865732,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"**gerritadmin** wrote:
+
+Change 158508 had a related patch set uploaded by Jforrester:
+Rename $label to $labelElement in MWParameterPage to avoid naming conflict
+
+https://gerrit.wikimedia.org/r/158508",1409865386,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"**gerritadmin** wrote:
+
+Change 158503 merged by jenkins-bot:
+Rename $label to $labelElement in MWParameterPage to avoid naming conflict
+
+https://gerrit.wikimedia.org/r/158503",1409864864,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"**gerritadmin** wrote:
+
+Change 158503 had a related patch set uploaded by Alex Monk:
+Rename $label to $labelElement in MWParameterPage to avoid naming conflict
+
+https://gerrit.wikimedia.org/r/158503",1409864633,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,"If you keep it as $label, then add a parameter to a template, then get parameterPage.$label, it appears in place of the outline item widget's label.
+
+Looks like the OOUI element mixin refactor is to blame...",1409864355,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names,Renaming this.$label to something else (e.g. $labelElement) in modules/ve-mw/ui/pages/ve.ui.MWParameterPage.js fixes this,1409862506,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-kqf3ft6lr75jkeflzwo7,task_subcomment,NA
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],"We should even if it's a minuscule part of the market for tablets, because we're going to eventually support phones (and for decency's sake).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409789520,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3gsxa566npjtwodxt42a,task_description,resolved
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],Please do not break the history.,1470786015,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3gsxa566npjtwodxt42a,task_subcomment,NA
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],Moved to projects instead.,1422405435,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3gsxa566npjtwodxt42a,task_subcomment,NA
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],"(In reply to Alex Monk from comment #1)
+> Is this a tracking bug?
+
+Yes.",1415031175,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3gsxa566npjtwodxt42a,task_subcomment,NA
+[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile],Is this a tracking bug?,1414870223,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-3gsxa566npjtwodxt42a,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Kdammers is running the current version of Mozilla on Windows 7 with a dual-script keyboard.  Typing in Hangul (한글) is not working in VisualEditor:  letters can be removed but when they are typed, they just disappear.
+
+
+Stefan2 did some related testing:
+
+Ibus-hangul (Korean) seems to work correctly in Firefox 32.0. In Chromium 37.0.2062.94, it produces spaces instead of Hangul letters. However, if a syllable only consists of two letters, the syllable shows up after typing in the second letter. It seems that syllables consisting of more than two letters can't be typed in using Chromium.
+
+Anthy (Japanese) is broken in both browsers.
+
+**See Also**: {T52631}",1409765460,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_description,resolved
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,Follow-up in {T127108}.,1457046550,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,">>! In T72353#1864840, @revi wrote:
+> Nope., It's still happening, in different form now.
+
+I think that's the same as {T120156} right?",1454540912,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Nope., It's still happening, in different form now.
+
+----
+Current status of Korea page
+---
+
+(`|` means cursor)
+```
+가나다라마바사아자차카파타하|
+```
+After I put two enters,
+```
+가나다라마바사아자차카파타하
+
+|
+```
+And now I put the word ""치킨"".
+Expected behavior
+---
+```
+가나다라마바사아자차카파타하
+
+치킨|
+```
+Actual Behavior
+---
+```
+가나다라마바사아자차카파타하치킨|
+
+// blank lines still there, phabricator doesn't recognize blank lines...
+```
+
+OS: Win7, 64bit, MS default IME, UserAgent: `Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0` See also P2386.",1450170537,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Nope., It's still happening, in different form now.
+
+----
+Current status of Korea page
+---
+
+(`|` means cursor)
+```
+가나다라마바사아자차카파타하|
+```
+After I put two enters,
+```
+가나다라마바사아자차카파타하
+
+|
+```
+And now I put the word ""치킨"".
+Expected behaviors
+---
+```
+가나다라마바사아자차카파타하
+
+치킨|
+```
+Actual Behavior
+---
+```
+가나다라마바사아자차카파타하치킨|
+
+// blank lines still there, phabricator doesn't recognize blank lines...
+```
+
+OS: Win7, 64bit, MS default IME, UserAgent: `Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0` See also P2386.",1449656546,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Nope., It's still happening, in different form now.
+
+----
+Current status of Korea page
+---
+
+(`|` means cursor)
+```
+가나다라마바사아자차카파타하|
+```
+After I put two enters,
+```
+가나다라마바사아자차카파타하
+
+|
+```
+And now I put the word ""치킨"".
+Expected behaviors
+---
+```
+가나다라마바사아자차카파타하
+
+치킨|
+```
+Actual Behavior
+---
+```
+가나다라마바사아자차카파타하치킨|
+
+// blank lines still there, phabricator doesn't recognize blank lines...
+```
+
+OS: Win7, 64bit, MS default IME, UserAgent: `Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0`",1449655021,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"OK, @revi, any chance you could re-check http://deployment.wikimedia.beta.wmflabs.org/wiki/Korea?veaction=edit ? If I type 'ganada' into my Korean IME I get 가나다  correctly. However, {T120156} is a horrible bug but I think a distinct blocker from this one. Provisionally re-closing.",1449104765,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Change 247800 merged by jenkins-bot:
+Diff richtext to build model changes
+
+[[https://gerrit.wikimedia.org/r/247800]]",1449100129,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"I have optimistically tagged this bug in change 247800, because it will fix many DOM/DM synchronization errors, and I suspect that is the underlying cause of the symptoms @revi reports above.",1448871169,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Change 247800 had a related patch set uploaded (by Divec):
+Diff richtext to build model changes
+
+[[https://gerrit.wikimedia.org/r/247800]]
+",1448871004,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Typed ##가나다## in the page.
+
+It makes newline (I thought like I typed enter.) and then 가나다. When I clicked the first line, it just don't let me write there and wrote my 가  at the newline.
+
+So, more graphically.
+
+what I did:
+My browser is in this stage;
+```
+|(cursor)
+```
+type ##가나다## now.
+
+what I expected:
+```
+가나다|(cursor)
+```
+what I get:
+```
+(empty line)
+가나다|(cursor)
+```
+At this stage, further ""enter"" command does not work, and I am stuck in that particular line.
+
+If I try to put the words on empty line...
+
+```
+|
+가나다
+```
+then it becomes...
+```
+(empty)
+가|가나다
+```
+
+Really weird, isn't it?
+
+OS: Win 7, Browser: FireFox 41.0.",1443609196,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hello, does it now work correctly on http://deployment.wikimedia.beta.wmflabs.org/wiki/Korea?veaction=edit ? It works for me there with IE/Windows 8 .
+
+@Revi, Thanks for the updated log for Firefox!",1443547826,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hello, does it now work correctly on http://deployment.wikimedia.beta.wmflabs.org/wiki/Korea?veaction=edit ? It works for me there with IE/Windows 8 .",1443547680,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"OK, @dchan I updated the P2090 and P2091 to FF info.
+
+Also, @Jdforrester-WMF I still can reproduce this.",1443325286,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"I haven't got any time to sit in front of the desk, run FF, verify whether
+this is fixed (in this case I will close the bug as I did on T52631) or not
+(in this case I will provide additional debug information as requested by
+@dchan.) Since dchan cannot reproduce the bug, it seems that I am the SPoF.
+
+It's national holiday in Korea and I'm currently at a house without any
+computer. So, please wait until I can touch computers ;)",1443313193,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,Is this now resolved?,1443277648,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,">>! In T72353#1675748, @dchan wrote:
+> Thanks for the event log!
+> 
+> That's on Chrome 45 right? Are you seeing the issue in Chrome too? It seems to work correctly for me in Chrome on Windows 8, and I get an essentially identical event log, so I'm confident our IMEs are essentially the same :-)
+> 
+>  Could you also provide a log created on Firefox? Thanks!
+
+Oh well, my bad. I was proven stupid. New log will be uploaded later tomorrow or Monday. (since it's [[ https://en.wikipedia.org/wiki/Chuseok | Chuseok ]] )",1443266036,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Change 241124 merged by jenkins-bot:
+Ignore slugs and chimeras when preventing identical re-renderings
+
+[[https://gerrit.wikimedia.org/r/241124]]",1443265417,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Change 241124 had a related patch set uploaded (by Divec):
+Ignore slugs and chimeras when preventing identical re-renderings
+
+[[https://gerrit.wikimedia.org/r/241124]]
+",1443209981,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"I can reproduce similar symptoms on IE on Windows 8. It can be reproduced by pressing Enter then 'ㄱ', which triggers the issue in T91244 . Perhaps the Firefox on Windows 7 issue is essentially the same; if you provide a log I will confirm.",1443207768,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Thanks for the event log!
+
+That's on Chrome 45 right? Are you seeing the issue in Chrome too? It seems to work correctly for me in Chrome on Windows 8, and I get an essentially identical event log, so I'm confident our IMEs are essentially the same :-)
+
+ Could you also provide a log created on Firefox? Thanks!",1443205750,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Here you are. P2090 for English and P2091 for Korean.
+
+{P2090}
+{P2091}",1443172097,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hi, unfortunately I can't reproduce the problem. (I guess it may depend on the IME version, which is very common). So to help us debug this, could you help us by sending the event log when you type '가나다' on your platform?
+
+1. Go to https://rawgit.com/wikimedia/VisualEditor/master/demos/ve/eventLogger.html
+2. Click 'Start Logging Keyboard Events'
+3. Type the text (i.e. just press 'rkskek' - don't press any other key)
+4. Click on the big box full of debug info
+5. Copy the text with the mouse
+6. Paste into a file and attach the file to this bug
+
+Thanks very much!",1443151406,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hi, unfortunately I can't reproduce the problem. So to help us debug this, could you help us by sending the event log when you type '가나다' on your platform?
+
+1. Go to https://rawgit.com/wikimedia/VisualEditor/master/demos/ve/eventLogger.html
+2. Click 'Start Logging Keyboard Events'
+3. Type the text (i.e. just press 'rkskek' - don't press any other key)
+4. Click on the big box full of debug info
+5. Copy the text with the mouse
+6. Paste into a file and attach the file to this bug
+
+Thanks very much!",1443151029,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"I can reproduce this. Win 7, 64bit, (I don't know what IME I'm using but default IME for Korean in Windows). Firefox Version 41.0.
+
+== Step to reproduce==
+
+1. Go to [[https://ko.wikipedia.org/wiki/%EC%82%AC%EC%9A%A9%EC%9E%90:Gisado/VEtest?veaction=edit|https://ko.wikipedia.org/wiki/%EC%82%AC%EC%9A%A9%EC%9E%90:Gisado/VEtest?veaction=edit]]
+2. Type enter twice.
+3. Try to type ##가나다##
+
+== Expected result ==
+ ##가나다## shows up below ##가나다라마바사아자차카파타하##., like this.
+{P2083}
+
+==Result bug==
+Two enters magically removed, and two ##ㅏ##s are put after ##가나다라마바사아자차카파타하##, like:
+{P2084}
+",1443086053,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"Hi, typing phonetically with Nalgaeset keyboard seems to work for me on Windows 8, Firefox 40.0.3 (and also Chrome 45.0.2454.99 m), both on en.wikipedia.org and on VE-standalone master.
+
+Can we close this, or is anyone still seeing corruption?",1443035039,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"When I tried to do test for bug 50631 on [[en:User:Hym411/VETest]] (second line), I got this bug. bug 50631 at least returns some result - though it's full of errors - but this gives some nonsense.
+
+Test envorinment: Win7, Google Chrome version 37.0.2062.120 m",1410753008,PHID-USER-mndznmqvm6ihjfmb6xap,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,Are we sure?  Bug 50631 can get something.  I believe that this user can't get anything.,1409850815,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,Exactly same problem of bug 50631. This should be merge into 50631.,1409808290,PHID-USER-ipgdr6xrndwpztdrubk4,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"What is ""the current version of Mozilla""? Firefox? Seamonkey?",1409777133,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard,"This is probably a dupe of bug 50631, but leaving it open.",1409766034,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uhvgmgrdscjhwyvdb474,task_subcomment,NA
+VisualEditor: [Regression pre-wmf20] anoneditwarning notice displays unparsed links with $1 and $2,"Screenshot of bug.
+
+The anoneditwarning message now takes parameters apparently. ApiVisualEditor.php.
+
+See mediawiki-core's EditPage.php for example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14741}",1409736780,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3jtahafvmd46fufkeey7,task_description,resolved
+VisualEditor: [Regression pre-wmf20] anoneditwarning notice displays unparsed links with $1 and $2,Fixed in gerrit Ia28f59a34.,1409859524,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3jtahafvmd46fufkeey7,task_subcomment,NA
+VisualEditor should respect [[MediaWiki:Noarticletext]],"**Author:** `gryllida`
+
+**Description:**
+[[MediaWiki:Noarticletext]] is shown when someone is creating a page, above the edit box. See:
+
+https://en.wikiversity.org/w/index.php?title=MediaWiki:Noarticletext
+https://en.wikiversity.org/w/index.php?title=Lalala&action=edit
+
+VisualEditor should respect this and also show such text in some prominent place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409710020,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-utd4dwndfqs2xvimd262,task_description,invalid
+VisualEditor should respect [[MediaWiki:Noarticletext]],Indeed.,1409781154,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-utd4dwndfqs2xvimd262,task_subcomment,NA
+VisualEditor should respect [[MediaWiki:Noarticletext]],"https://en.wikiversity.org/w/index.php?title=Lalala&action=edit&uselang=qqx is showing 'newarticletext' (not 'noarticletext'), which VE already does...
+
+'noarticletext' is shown on action=view.",1409775654,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-utd4dwndfqs2xvimd262,task_subcomment,NA
+VisualEditor: Switch to source editing dialog too tall,"**Author:** `josephsieh`
+
+**Description:**
+screen shot of ""Switch to source editing"" dialog too tall issue on Safari.
+
+After user modified something in Visual Editor and then tries to click on ""Edit"" without clicking ""Save page"", the ""Switch to source editing?"" dialog appears to be too tall as the attached screenshot shows.
+
+It happens on 
+
+OSX 10.9.4
+Safari 7.0.6.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70545
+
+**Attached**: {F14706}",1409705580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5zoyxx73z2lluiw4akkr,task_description,resolved
+VisualEditor: Switch to source editing dialog too tall,Verified the fix in production,1411681613,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5zoyxx73z2lluiw4akkr,task_subcomment,NA
+VisualEditor: Switch to source editing dialog too tall,"Yeah, checked on a Mac.",1411417372,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5zoyxx73z2lluiw4akkr,task_subcomment,NA
+VisualEditor: Switch to source editing dialog too tall,"This might be the same issue as bug 70545 and looks similarly fixed to be, but I don't have a Mac to test on.",1411415059,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5zoyxx73z2lluiw4akkr,task_subcomment,NA
+"VisualEditor: Adding a link right before a wikilinked word leads to unexpected results, including a nowiki","This can be seen by placing the cursor right at the beginning of any existing wikilinked word, then trying to add any kind of link. 
+User's expectation is that this changes the wikilink target with no corruption.
+
+<<To reproduce this:
+* [https://fr.wikipedia.org/w/index.php?title=Boys_band&veaction=edit Edit Boys band on frwiki]
+* In the history chapter, 4th paragraph, put the cursor before the S of the link to Super Junior
+* Click on link icon in the toolbar
+* Copy the URL <code><nowiki>https://fr.wikipedia.org/wiki/B.A.P</nowiki></code> in the link inspector and click Terminé
+* When previewing modifications, you can see that it has been replaced by <code><nowiki>[[B.A.P]] [[Super Junior|<nowiki/>]][[B.A.P|Super]] Junior</nowiki></code> which shows several problems: there's a link without text displayed, the existing link has been cut in two
+* And also, what is displayed in VE doesn't match at all what the result will be when saved:
+** ""Super"" is displayed as an external link, but in the modifications preview, you see it's an internal link
+** If you hover over ""Super"", both ""Super"" and ""Junior"" get underlined, but in the modifications preview, ""Junior"" is not inside the link
+** ""Junior"" is displayed as an internal link, but in the modifications preview, you see it's now just text
+** If you hover over ""Junior"", both ""Super"" and ""Junior"" get underlined, but in the modifications preview, ""Junior"" is not inside a link .>> Instructions by NicoV.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409660820,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-d2yxda424o7uk6liddmf,task_description,resolved
+"VisualEditor: Adding a link right before a wikilinked word leads to unexpected results, including a nowiki",Resolved with this: https://gerrit.wikimedia.org/r/#/c/197425,1426638000,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-d2yxda424o7uk6liddmf,task_subcomment,NA
+"VisualEditor: Adding a link right before a wikilinked word leads to unexpected results, including a nowiki",The root cause here is very odd; I've opened {T86399} to work this out.,1420861251,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d2yxda424o7uk6liddmf,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,"The qqq documentation for the message Visualeditor-dialog-action-done is either misleading or I misunderstand it :)
+
+It says: ""Label text for button to exit from a dialog that has no changes to make.""
+
+However, this message is used in the link inspector - this is not quite a dialog, and it does make changes.
+
+I can think of three options:
+* I misunderstand something :)
+* This message shouldn't be used in the link inspector
+* This message's documentation should be changed
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409645820,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_description,resolved
+Documentation for the message Visualeditor-dialog-action-done is misleading,"Change 184642 merged by jenkins-bot:
+Create separate message for find-and-replace-done
+
+[[https://gerrit.wikimedia.org/r/184642]]",1421165213,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,I think this is just a copy and paste error from visualeditor-dialog-action-cancel,1421163995,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,"Change 184642 had a related patch set uploaded (by Esanders):
+Create separate message for find-and-replace-done
+
+[[https://gerrit.wikimedia.org/r/184642]]
+
+#patch-for-review",1421163926,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,"After reading @Jdforrester-WMF's reasoning on T85852 I am even more convinced that this is a problem.
+
+UI consistency is a good idea, but enforcing too much of it is not. In particular, reusing the same message in several different dialogs is a bad idea. See
+https://www.mediawiki.org/wiki/Localisation#Avoid_message_reuse
+
+""Done"" is used now in several contexts that may seem similar to developers, but are not actually the same. In Russian and Hebrew it's definitely wrong to apply the same message too all these different dialogs. As the localisation guide says, this may seem counter-intuitive, but it is also based on a lot of experience.",1420568195,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Documentation for the message Visualeditor-dialog-action-done is misleading,"... This caused T85852.
+
+""Done"" just doesn't sound like a button in a dialog that has no changes to make.",1420491504,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-xzvyjiqogzwcgi53p5vo,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"Just discovered this tool, and since it makes it so much easier to add TemplateData, it would be a huge improvement for us template editors, and consequently for the VisualEditor users out there. Can't see any reason it should be controversial, but if requested I'll bring it up in our village pump.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1409430780,PHID-USER-jqjb54lbf7psat6shbcc,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_description,resolved
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,Merged and deployed!,1409671057,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"**gerritadmin** wrote:
+
+Change 157476 merged by jenkins-bot:
+Enable TemplateData GUI on Norwegian Bokmål (nowiki)
+
+https://gerrit.wikimedia.org/r/157476",1409670702,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"Start to involve the projects in the decision process, or at least don't try to override existing processes. This request does _NOT_ follow due process and will interfere with the project own decision.
+
+Why does it seem like I always repeat myself.. ;/",1409566750,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"(In reply to jeblad from comment #5)
+> There is no consensus at WP:Tinget, and that would usually take at least a
+> week. There is a notice about this at WP:Torget, but this page is not used
+> for project wide decisions at nowiki.
+
+This isn't really seeking a ""decision"", in the same way that most of the hundreds of improvements which are rolled out every week.
+
+> Before final consensus is reached all system messages should be translated
+
+Your input on https://translatewiki.net/w/i.php?title=Special:Translate&action=proofread&group=ext-templatedata&language=nb&filter=translated%7C%21reviewer%3A8576%7C%21last-translator%3A8576 is of course welcome in ensuring that. :-)
+
+> and necessary help pages created.
+
+Obviously you're not suggesting that WMF should interfere with a project and re-write their help pages here, I assume. :-)",1409525530,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"There is no consensus at WP:Tinget, and that would usually take at least a week. There is a notice about this at WP:Torget, but this page is not used for project wide decisions at nowiki.
+
+Before final consensus is reached all system messages should be translated and necessary help pages created. Only then should this be scheduled.
+
+In short, this request is invalid.",1409523675,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,Currently scheduled for 15:00 UTC on Tuesday 2 September; we can postpone it if there are an issues.,1409432185,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"**gerritadmin** wrote:
+
+Change 157476 had a related patch set uploaded by Jforrester:
+Enable TemplateData GUI on Norwegian Bokmål (nowiki)
+
+https://gerrit.wikimedia.org/r/157476",1409431776,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"To be on the safe side I posted in our village pump asking if there are any objections:
+
+https://no.wikipedia.org/wiki/Wikipedia:Torget#.C2.ABManage_TemplateData.C2.BB",1409431332,PHID-USER-jqjb54lbf7psat6shbcc,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia,"Sure, no problem.",1409430901,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ku4qzbqeu24wzpgt76qw,task_subcomment,NA
+VisualEditor Mobile: Performance issue with adding Citations in Mobile,There is a noticeable lag observed while trying to add any citation in mobile in Beta labs environment.,1409339820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jleaptwiihwbszn24ore,task_description,resolved
+VisualEditor Mobile: Performance issue with adding Citations in Mobile,Tested and performance is more than adequate on my iPhone.,1439257531,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jleaptwiihwbszn24ore,task_subcomment,NA
+VisualEditor: non-editable element inserted before a colon,"*Sorry about the lame summary*
+
+This bug can probably have a better title.
+
+A rather simple and innocent edit in the Hebrew Wikipedia introduced an element that had no reason to appear in the code. Here's the edit:
+https://he.wikipedia.org/w/index.php?title=%D7%9B%D7%99%D7%91%D7%95%D7%A9%D7%99_%D7%90%D7%9C%D7%9B%D7%A1%D7%A0%D7%93%D7%A8_%D7%94%D7%92%D7%93%D7%95%D7%9C_%D7%91%D7%90%D7%A1%D7%99%D7%94_%D7%94%D7%AA%D7%99%D7%9B%D7%95%D7%A0%D7%94&diff=15812721&oldid=15812716
+
+The problematic element appears between the words ""מטרות נוספות היו"" and the colon.
+
+The element was removed in the following edit:
+https://he.wikipedia.org/w/index.php?title=%D7%9B%D7%99%D7%91%D7%95%D7%A9%D7%99_%D7%90%D7%9C%D7%9B%D7%A1%D7%A0%D7%93%D7%A8_%D7%94%D7%92%D7%93%D7%95%D7%9C_%D7%91%D7%90%D7%A1%D7%99%D7%94_%D7%94%D7%AA%D7%99%D7%9B%D7%95%D7%A0%D7%94&diff=15887470&oldid=15878013
+
+When editing it in the VisualEditor, the element appears as ""Sorry, this element can only be edited in source mode for now.""
+
+When I showed this to David, he thought that it may be somewhat related to the ""unicorn"" patch, but it is not certain.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409312820,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dx53p7272wo7nmcymv63,task_description,open
+VisualEditor: non-editable element inserted before a colon,"Confirmed in betalabs - for en wiki too.
+- Insert a colon into a paragraph text and - Important!- put white spaces around it
+
+The colon (:) will be transformed into 
+```<span typeof=""mw:Placeholder"" data-parsoid=""{&quot;src&quot;:&quot; &quot;,&quot;isDisplayHack&quot;:true,&quot;dsr&quot;:[83,84,null,0]}"" class=""ve-ce-leafNode ve-ce-focusableNode"" contenteditable=""false"">&nbsp;</span> ```
+
+with
+
+```<div class=""ve-ce-focusableNode-highlight ve-ce-alienNode-highlight"" title=""Sorry, this element can only be edited in source mode for now."" draggable=""false"" style=""top: 11px; left: 391px; width: 5px; height: 15px;""><img class=""ve-ce-focusableNode-highlight-relocatable-marker"" src=""data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==""></div>```
+
+
+",1424302398,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-dx53p7272wo7nmcymv63,task_subcomment,NA
+VisualEditor: wikitext warning doesn't auto-hide the first time you enter wikimarkup,"Verified with Chrome and Safari.
+If you type wikitext ( I tried with * ) and then delete it, the wikitext warning won't go away automatically.
+If you click on it to make it disappear, proceed to add more wikitext and delete this again, then the box will auto-hide correctly.
+
+(Two square parentheses don't seem to trigger the warning at all?)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51701",1409308440,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hzqhjjti55dwecogv2dm,task_description,resolved
+VisualEditor: wikitext warning doesn't auto-hide the first time you enter wikimarkup,"**gerritadmin** wrote:
+
+Change 157278 merged by jenkins-bot:
+Make sure mediawiki.notification is loaded -before- calling ViewPageTarget#checkForWikitextWarning
+
+https://gerrit.wikimedia.org/r/157278",1409343958,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hzqhjjti55dwecogv2dm,task_subcomment,NA
+VisualEditor: wikitext warning doesn't auto-hide the first time you enter wikimarkup,"**gerritadmin** wrote:
+
+Change 157278 had a related patch set uploaded by Alex Monk:
+Make sure mediawiki.notification is loaded -before- calling ViewPageTarget#checkForWikitextWarning
+
+https://gerrit.wikimedia.org/r/157278",1409343557,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hzqhjjti55dwecogv2dm,task_subcomment,NA
+VisualEditor: wikitext warning doesn't auto-hide the first time you enter wikimarkup,Taking this bug,1409342978,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-hzqhjjti55dwecogv2dm,task_subcomment,NA
+VisualEditor: Applying a link to an invalid title triggers an undo,"1. Type some text which is an invalid title in MW, e.g. ""|InvalidTitle""
+2. Select it and hit link
+-  Notice that there are no suggestions, and no initial link is applied
+3. Type in a valid page name, e.g. ""Main page"" and press Done
+-  Notice some of your text has been deleted (by and undo operation) before the link was applied
+
+The bug is actually in core AnnotationInspector#getTeardownProcess. We call a surface undo() to remove the initial annotation, but in the case of an invalid title there is no initial annotation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409306340,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-zznxlmtpisyv35ph3vdy,task_description,resolved
+VisualEditor: Applying a link to an invalid title triggers an undo,"**gerritadmin** wrote:
+
+Change 157053 merged by jenkins-bot:
+Only undo if an initial annotation was applied
+
+https://gerrit.wikimedia.org/r/157053",1409334982,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zznxlmtpisyv35ph3vdy,task_subcomment,NA
+VisualEditor: Applying a link to an invalid title triggers an undo,"**gerritadmin** wrote:
+
+Change 157053 had a related patch set uploaded by Esanders:
+Only undo if an initial annotation was applied
+
+https://gerrit.wikimedia.org/r/157053",1409307103,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zznxlmtpisyv35ph3vdy,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70744",1409239140,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-444jjina7afgsdohllry,task_description,resolved
+create browser test build for IE11/VisualEditor,"This build now exists at https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-windows_8.1-internet_explorer-11-sauce/
+
+Notice the rather nifty failure due to javascript error.",1410541891,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 157164 abandoned by Zfilipin:
+WIP Trying to create IE11 Jenkins job for VisualEditor
+
+Reason:
+moved to https://gerrit.wikimedia.org/r/#/c/160008/
+
+https://gerrit.wikimedia.org/r/157164",1410539112,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 157480 merged by jenkins-bot:
+browsertests: Enable VE on IE and Safari; remove Chrome on Windows XP
+
+https://gerrit.wikimedia.org/r/157480",1410037042,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 157164 had a related patch set uploaded by Zfilipin:
+WIP Trying to create IE11 Jenkins job for VisualEditor
+
+https://gerrit.wikimedia.org/r/157164",1409845273,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 156448 abandoned by Jforrester:
+browsertests: Enable VE on IE11 and Safari; remove Chrome on Windows XP
+
+Reason:
+Moved to master branch.
+
+https://gerrit.wikimedia.org/r/156448",1409433203,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 157480 had a related patch set uploaded by Jforrester:
+browsertests: Enable VE on IE11 and Safari; remove Chrome on Windows XP
+
+https://gerrit.wikimedia.org/r/157480",1409433190,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+create browser test build for IE11/VisualEditor,"**gerritadmin** wrote:
+
+Change 156448 had a related patch set uploaded by Jforrester:
+browsertests: Enable VE on IE11 and Safari; remove Chrome on Windows XP
+
+https://gerrit.wikimedia.org/r/156448",1409240289,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-444jjina7afgsdohllry,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Education Programme:
+> On page
+> https://pt.wikipedia.org/wiki/User:Alpha_Centaurus?veaction=edit&oldid=39924153&uselang=en
+> the link to
+> https://pt.wikipedia.org/wiki/Ensino:Universidade_Federal_do_Rio_Grande_do_Sul/C%C3%A1lculo_Num%C3%A9rico_%28MAT01169%29_%282014-2%29
+> is red, but it should be blue because (from the user's point of view) the page exists.
+
+GlobalUserPages:
+> Viewing https://www.mediawiki.org/wiki/Extension:TemplateData shows a blue link for ""James Forrester"". However, when editing with VisualEditor, the link is red.
+
+
+----
+See also: {T134073}",1409234640,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-kfwpka7h3inptj65moc2,task_description,resolved
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Change 315432 merged by jenkins-bot:
+mw.LinkCache: Links aren't missing if they're known
+
+[[https://gerrit.wikimedia.org/r/315432]]",1476319929,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Change 315455 merged by jenkins-bot:
+TitleWidget: Take 'known' status into account when deciding page existence
+
+[[https://gerrit.wikimedia.org/r/315455]]",1476316894,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Change 315455 had a related patch set uploaded (by Alex Monk):
+TitleWidget: Take 'known' status into account when deciding page existence
+
+[[https://gerrit.wikimedia.org/r/315455]]
+",1476234312,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Change 315432 had a related patch set uploaded (by Jforrester):
+mw.LinkCache: Links aren't missing if they're known
+
+[[https://gerrit.wikimedia.org/r/315432]]
+",1476222686,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","I filed a blocker bug to expose Title::isKnown() via the API, so VE can use it.
+
+Once that is in place, someone will need to update `ve.init.mw.LinkCache` to use it.",1470208154,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Extension:WikimediaIncubator also uses this hook so ""Valid Wx/xyz info pages should be considered as existing pages"". SemanticMediaWiki also uses it for something.
+
+There are other issues due to Title::isAlwaysKnown that aren't just the TitleIsAlwaysKnown hook - existence of files vs. file pages, and existence of system messages.",1425697754,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+"VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)","Unfortunately, that page doesn't actually exist. EducationProgram just pretends it does via the hook I mentioned in T72504#942697.",1419537917,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-kfwpka7h3inptj65moc2,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Tap somewhere in the middle of the page or towards the end
+
+Observed Result:
+The page focus bumps up to the top of the page, not getting scrolled down to the point where the cursor is actually positioned.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409181600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szhrrt6yhyfzihjpjade,task_description,resolved
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488620,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"**jgonera** wrote:
+
+Maryana said that she doesn't consider that very high priority so I might not get to it before I leave. Unassigning myself.",1409264628,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"**jgonera** wrote:
+
+Correction: the page doesn't scroll up. It should scroll up when the keyboard opens and covers up the cursor. Instead, the page stays in place.
+
+This is because we no longer scroll the whole page on iOS (we scroll inside of a div) and Safari's default mechanism for preventing the cursor from being covered by the keyboard doesn't work anymore (that's my guess).
+
+I think an easy solution would be to implement scrolling the CE on focus in such a way that the cursor ends up being close to the top of the screen. This way the keyboard won't occult it. We have to keep in mind though that this code should only run on iOS (which is easy because we already let MobileViewTarget know that we're on iOS using isIos config argument).",1409260466,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"The page scrolls up, the cursor is correctly positioned with the fix of https://bugzilla.wikimedia.org/show_bug.cgi?id=66697",1409182967,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position,"**jgonera** wrote:
+
+""The page focus bumps up to the top of the page"" - you mean the page is scrolled to the top or the cursor moves to the top?",1409182819,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-szhrrt6yhyfzihjpjade,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Click on ""Show Options""
+4.Add the template ""Cite Web""
+5.Select one of those required parameter from the left panel of the dialog
+6.Add some more template with some optional parameters and content in the transclusion dialog
+7.Now select one of the required parameter for the ""Cite Web"" template from the left panel
+8.Now from left panel,select any other template/optional parameter/content or even the ""Cite web"" template 
+
+Observe that the trash icon that used to appear at the corner of the left panel for other template/optional parameter/content or ""Cite web"" template are not appearing now.
+
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14309}",1409168760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5azsp7uzzucqdg6yukh3,task_description,resolved
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,Verified the fix in production,1409865667,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,Verified the fix in test2,1409260092,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,Verified the fix in Betalabs,1409178636,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,"Change 156671 merged by jenkins-bot:
+Toggle trash button (on transclusion dialog) visibility when changing to non-parameter pages
+
+https://gerrit.wikimedia.org/r/156671",1409174915,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,"Change 156671 had a related patch set uploaded by Alex Monk:
+Toggle trash button (on transclusion dialog) visibility when changing to non-parameter pages
+
+https://gerrit.wikimedia.org/r/156671",1409169644,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter,"Created attachment 16297
+The missing trash icon
+
+**Attached**: {F14310}",1409168921,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5azsp7uzzucqdg6yukh3,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Steps to reproduce:
+
+1.  Open page containing the {{good article}} (or similar) template in VisualEditor, such as https://en.wikipedia.org/w/index.php?oldid=622810787 (which contains only that template)
+
+2.  Click the good article icon/template
+
+3.  VisualEditor exits, and you are reading the Wikipedia:Good article page (the same one that you would be reading if you clicked that icon in 'read' mode).
+
+
+Expected behavior:
+
+1.  Open page containing {{good article}} in VisualEditor
+
+2.  Click the good article icon/template
+
+3.  Edit the template just like any other.
+
+
+It's possible that this can only be reproduced on Windows, because on my Mac, when I open the page, the template isn't even visible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409099760,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-z2d3f6p2ejg2badg7nph,task_description,resolved
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Change 161957 merged by jenkins-bot:
+Prevent page elements from displaying on top of highlights
+
+https://gerrit.wikimedia.org/r/161957",1411509996,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Ed, that's bug 23796, with the related bug 51420 in VE.",1411399971,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Change 161957 had a related patch set uploaded by Bartosz Dziewoński:
+Prevent page elements from displaying on top of highlights
+
+https://gerrit.wikimedia.org/r/161957",1411399800,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Setting topicons with CSS like this is a horrible hack. Imagine if we did the same with category links!
+
+We should create a simple extension to add topicons to a page, so that they are rendered in the correct place in the HTML (i.e. not the article body). Parsoid can then provide them to VE as metadata and we can handle them accordingly.
+
+I've discussed this with Trevor and Roan and we think it's a fairly simple project to take on.",1411399687,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","While this could possibly be fixed on-wiki for this particular case, we should prevent people from accidentally or intentionally breaking this in VE, too.",1411398987,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","Caused by ""z-index: 10;"" in [[w:en:MediaWiki:Monobook.css]].",1411398593,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia","It was reported on Firefox 31 on Windows 7, using Monobook.
+
+There's a screenshot at https://commons.wikimedia.org/wiki/File:VE_with_GA_icon.png",1409152635,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+"VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia",Which browsers are you using ?,1409132291,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-z2d3f6p2ejg2badg7nph,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Take this query from the suggester:
+
+https://en.wikipedia.org/w/api.php?format=jsonfm&uselang=en&action=query&list=allcategories&acprefix=1895+es&acprop=hidden&redirects=
+
+Now read [[mw:Manual:Category table]]:
+""Track all existing categories. Something is a category if it has an entry somewhere in categorylinks, or it once did.""
+
+So it's logical that something like 1895 establisANONYMOUS IS LEGIONhments is in the suggestion list, but it is really not desirable. It contains many 'bad' words and deleted stuff that we don't really want to present to users.
+
+
+https://en.wikipedia.org/w/api.php?format=jsonfm&uselang=en&action=query&list=allcategories&acprefix=1895+es&acprop=hidden&redirects=&acprop=size|hidden
+
+This can be easily solved by adding:
+acmin=1 to the query.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1409044020,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fypqepsh6l776gwf6e2h,task_description,resolved
+VisualEditor: Category suggestion lists no longer existing categories,*** Bug 69927 has been marked as a duplicate of this bug. ***,1409094378,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Actually, i forgot, HotCat now actually runs 2 queries on both of these tables, and then combines them into a result..
+
+
+Perhaps we should fix the api ? :)",1409083278,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Change 156250 merged by jenkins-bot:
+Categories: Don't suggest empty or old categories
+
+https://gerrit.wikimedia.org/r/156250",1409083244,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Alternative is to use the HotCat methodology:
+
+Here only categories that have their own page are considered to exist:
+https://en.wikipedia.org/w/api.php?format=json&action=query&list=allpages&apnamespace=14&aplimit=30&apfrom=1895%20es&apprefix=1895%20es",1409083001,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Category suggestion lists no longer existing categories,"Change 156250 had a related patch set uploaded by TheDJ:
+Categories: Don't suggest empty or old categories
+
+https://gerrit.wikimedia.org/r/156250",1409045158,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fypqepsh6l776gwf6e2h,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"Reference dialog in test2
+
+The size of the Reference dialog got changed to a bigger size after wmf18
+
+See the screenshots attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70601
+
+**Attached**: {F14691}",1409012040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e532vezhqz47vwem7t6o,task_description,resolved
+VisualEditor: Shrink back the Basic Reference dialog size,*** Bug 70601 has been marked as a duplicate of this bug. ***,1414137121,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,Verified the fix in production,1411681864,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,Verified the fix in test2,1411083546,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"**gerritadmin** wrote:
+
+Change 161165 merged by jenkins-bot:
+Fix automatic sizing of windows
+
+https://gerrit.wikimedia.org/r/161165",1411065126,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"**gerritadmin** wrote:
+
+Change 161165 had a related patch set uploaded by Catrope:
+Fix automatic sizing of windows
+
+https://gerrit.wikimedia.org/r/161165",1411012487,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"Many other dialogs have this problem too, including referenceList. It looks like getBodyHeight() is returning a value that's way too high.",1409680874,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Shrink back the Basic Reference dialog size,"Created attachment 16279
+Reference dialog in production
+
+**Attached**: {F14692}",1409012100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e532vezhqz47vwem7t6o,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1409011560,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-advminout52vzy4o576h,task_description,resolved
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,Verified the fix in Production,1410545808,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,So the first patch set I made (to deal with existing links when you clear the target page) should be deployed to all Wikimedia wikis. But the second one (per Rummana's comment 4) was merged a day later which just happened to put it on the next deployment version (so it should be another week).,1409869692,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,I just tested this on MediaWiki.org and it seems to have been fixed. . .,1409869210,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"Again in production, the ""open"" button remains enabled when I open a link inspector in a blank line without selecting a text.I will wait for a while to see whether it gets started working automatically like it did in Betalabs.Reopening it for now.",1409865004,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"Yeah, just started working for me! Marking as Resolved .",1409347795,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,Works for me. Gerrit change 157212 should've sent my fix to beta labs.,1409347253,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"Created attachment 16315
+Screenshot
+
+hmm..but I still see that button as active :/
+
+**Attached**: {F14688}",1409345516,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"I uploaded Gerrit change 157017 to resolve that issue, and Roan just merged it. I forgot to link it to this bug, sorry!",1409272184,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"The ""Open"" button is now getting disabled when you clear the link target name , but if you just open the link inspector in any empty line and there is no link target name specified yet , the ""Open"" button still remains enabled",1409259547,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"**gerritadmin** wrote:
+
+Change 156582 merged by jenkins-bot:
+Link target input widget: Make '' an invalid link target
+
+https://gerrit.wikimedia.org/r/156582",1409184286,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"**gerritadmin** wrote:
+
+Change 156582 had a related patch set uploaded by Alex Monk:
+Link target input widget: Make '' an invalid link target
+
+https://gerrit.wikimedia.org/r/156582",1409160980,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor: Open button in link inspector should be disabled when the link target field is empty,"Right now, when you open link inspector and keep the link target field empty, you will still be able to click on ""Open"" button as it remains active, though it serves no purpose.We should disable it in this case",1409011737,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-advminout52vzy4o576h,task_subcomment,NA
+VisualEditor:  Category names are taking long time (~6-7 secs)to appear in the Category section,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add some categories to the page
+3.Save the page
+4.Reopen the page and go to the categories section
+
+Observed Result:
+The categories are not appearing immediately,after waiting for approx. 6-7 secs they do appear in that section.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409009400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ic44hmdblr4rvvctpw5r,task_description,resolved
+VisualEditor:  Category names are taking long time (~6-7 secs)to appear in the Category section,This was happening because of HHVM issue. Now it is working fine.,1409011011,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ic44hmdblr4rvvctpw5r,task_subcomment,NA
+"VisualEditor:  {{#tag:ref}} is not processed by VisualEditor, so the references list claims that there are no refs in that group","This may be related to bug 51289 and bug 61777.
+
+
+Steps to reproduce:
+
+1.  Open a page that contains refs formatted like this:  {{#tag:ref|Text goes here. |group=n |name=Foo}}
+
+2.  Add a references list for the group.
+
+3.  Read the error message.  VisualEditor says that there are no refs in group 'n' on the page.
+
+
+Expectation:
+
+Refs would be properly recognized and displayed even if they use this rather odd format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409008680,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6fjxmlk42cz5vwd46onb,task_description,open
+VisualEditor: The article Sindhi language cannot be edited in VE if the Language tool is enabled,"Trying to edit the article [[Sindhi language]] in VE while the language tool is enabled produces gets the browser stuck with the animated loading bar and produces a JavaScript error in the console:
+Uncaught TypeError: Cannot read property 'toLowerCase' of null ve.ce.LanguageAnnotation.js:52
+
+(This is from Chrome; the error in Firefox is slightly different, but it's broken there as well.)
+
+If the language tool beta feature is disabled, then the article can be edited.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408870740,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-bdmcqwt76vyccvojptxl,task_description,resolved
+VisualEditor: The article Sindhi language cannot be edited in VE if the Language tool is enabled,"Change 156143 merged by jenkins-bot:
+Fix JS error in ce.LanguageAnnotation when dir is set but lang isn't
+
+https://gerrit.wikimedia.org/r/156143",1408987293,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bdmcqwt76vyccvojptxl,task_subcomment,NA
+VisualEditor: The article Sindhi language cannot be edited in VE if the Language tool is enabled,"Change 156143 had a related patch set uploaded by Catrope:
+Fix JS error in ce.LanguageAnnotation when dir is set but lang isn't
+
+https://gerrit.wikimedia.org/r/156143",1408985963,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bdmcqwt76vyccvojptxl,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"Sometimes you want a single quotation mark next to an italicized (or bolded) word. 
+It would be nice if VisualEditor/Parsoid did something elegant with the wikitext, like ""celui d'<nowiki/>''Homo sapiens''"" instead of wrapping half a sentence inside nowiki tags to deal with a single character.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408839360,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-nk4g5ukj6fdtvpowneko,task_description,resolved
+Improve nowiki additions to only wrap the string that needs protection,"Change 193842 merged by jenkins-bot:
+T71950: Output <nowiki> closer to quotes
+
+[[https://gerrit.wikimedia.org/r/193842]]",1425925165,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"> [[https://gerrit.wikimedia.org/r/193842]]
+
+This is a WIP that should fix the https://fr.wikipedia.org/w/index.php?title=Grand_Line&curid=4571652&diff=111992974&oldid=111360543 case, but I want to make sure it doesn't break anything else.",1425315475,PHID-USER-56wtmb23orq4pu5liyj5,True,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"Change 193842 had a related patch set uploaded (by Marcoil):
+WIP: T71950: Output <nowiki> closer to actual reason
+
+[[https://gerrit.wikimedia.org/r/193842]]
+",1425315346,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"nowiki addition for quotes has improved since this ticket was created. We should investigate what needs fixing here. But, one recent diff that could be investigated (as reported by @NicoV) is https://fr.wikipedia.org/w/index.php?title=Grand_Line&curid=4571652&diff=111992974&oldid=111360543",1424538050,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+Improve nowiki additions to only wrap the string that needs protection,"See https://fr.wikipedia.org/w/index.php?title=La_Horde_sauvage_(film,_1969)&curid=88578&diff=106771550&oldid=106771188
+
+https://fr.wikipedia.org/w/index.php?title=Archelon&curid=1273494&diff=106770342&oldid=105728402
+
+If in a long string, only a single small piece of it needs nowiki-ing, that single string can be wrapped. In general, this requires knowing that nothing else in the long string needs a nowiki wrapper, but heuristics could work for common scenarios. This seems to be a problem that affects frwiki especially.",1408998537,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-nk4g5ukj6fdtvpowneko,task_subcomment,NA
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","This might be related to Bug 49524.
+
+See https://commons.wikimedia.org/wiki/File:VE_selection_box_goes_over_menus.png
+
+When you open https://en.wikipedia.org/w/index.php?oldid=620028233 in Firefox on Windows 7, the sandbox template is autoselected.  If you click on a menu (e.g., to set bold text), the menu drops down but the items that overlap with the auto-selected template can't be chosen.
+
+I am unable to reproduce this in either Safari or Firefox on a Mac.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408839060,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-utuehsjkuc2a6rnd6nid,task_description,resolved
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","Change 156723 merged by jenkins-bot:
+Fix various bugs in our Monobook stylesheet
+
+https://gerrit.wikimedia.org/r/156723",1409247823,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-utuehsjkuc2a6rnd6nid,task_subcomment,NA
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","Change 156723 had a related patch set uploaded by Catrope:
+Fix various bugs in our Monobook stylesheet
+
+https://gerrit.wikimedia.org/r/156723",1409181526,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-utuehsjkuc2a6rnd6nid,task_subcomment,NA
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","I couldn't reproduce this bug, and realized it was specific to Monobook. There are other minor display issues with the toolbar in Monobook as well (like its height).",1409177114,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-utuehsjkuc2a6rnd6nid,task_subcomment,NA
+"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items","This appears to only happen if you are at the top of the page.  If you scroll down at all, then it works correctly.",1409007413,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-utuehsjkuc2a6rnd6nid,task_subcomment,NA
+Enable DOM editing of transclusion parameters,"This is needed to allow VisualEditor to support such lovely wikitext as {{echo|{{echo|Foo!}}}} and more complex variations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408649880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-djmwv2eookrt5vpvsei5,task_description,open
+Enable DOM editing of transclusion parameters,"A different approach that we have considered over the last few months is to generate these HTML representation of tpl params on demand rather than for Parsoid to generate this all the time and then store it.
+
+So, whenever a template is opened up for editing in VE, VE would request Parsoid for HTML representation of these parameters, and then use that to enabled HTML editing of these params. If  this is considered a workable approach, we can work out the details and this can see the light of day much faster.",1448296086,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-djmwv2eookrt5vpvsei5,task_subcomment,NA
+Enable DOM editing of transclusion parameters,"(In reply to Marc Ordinas i Llopis from comment #1)
+> With this enabled, it's possible to make Parsoid accept new transclusion
+> parameters from HTML by removing the wt ones. We are also planning on adding
+> support for detecting changes in parameters (so that the wikitext ones don't
+> have to be removed) in the future.
+
+That sounds great.
+
+> I'll be working on improving performance shortly.
+
+Excellent. :-)",1409067257,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-djmwv2eookrt5vpvsei5,task_subcomment,NA
+Enable DOM editing of transclusion parameters,"The current status for DOM transclusion parameters is: The code is there, but it is disabled by default as it affects performance. For example, it increases the rendering of [[Barack_Obama]] by more than 3s.
+
+To enable it (in case someone wants to try it out), add
+parsoidConfig.addHTMLTemplateParameters = true;
+to localsettings.js.
+
+With this enabled, it's possible to make Parsoid accept new transclusion parameters from HTML by removing the wt ones. We are also planning on adding support for detecting changes in parameters (so that the wikitext ones don't have to be removed) in the future.
+
+I'll be working on improving performance shortly.",1409047482,PHID-USER-56wtmb23orq4pu5liyj5,True,PHID-TASK-djmwv2eookrt5vpvsei5,task_subcomment,NA
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,"Save button not working after creating citation
+
+After fixing https://bugzilla.wikimedia.org/show_bug.cgi?id=69856
+
+Do everything to create a Citation as shown in the screen shot. 
+
+Click Save. Save does nothing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14354}",1408645140,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_description,resolved
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,Verified the fix in production,1409866397,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_subcomment,NA
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,"**gerritadmin** wrote:
+
+Change 155601 merged by jenkins-bot:
+Followup 67f304a: use .openWindow(), not .open(), to open save dialog
+
+https://gerrit.wikimedia.org/r/155601",1408664848,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_subcomment,NA
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,"**gerritadmin** wrote:
+
+Change 155601 had a related patch set uploaded by Jforrester:
+Followup 67f304a: use .openWindow(), not .open(), to open save dialog
+
+https://gerrit.wikimedia.org/r/155601",1408648658,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_subcomment,NA
+VisualEditor: [Regression wmf18] Save Page no longer completes save actions,"This happens while trying to save a page after adding anything in the page, not just citations.The error that appears in the console is:
+Uncaught TypeError: Cannot read property 'openWindow' of null",1408647243,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5xlpbmlhjpmu5hgvb6ks,task_subcomment,NA
+VisualEditor shows double page title after edit when 'edittop' gaget (or similar) is enabled,"Screenshot
+
+VisualEditor shows double page title after edit when the 'edittop' gaget (or similar) is enabled.
+
+This is because the code to update page's DISPLAYTITLE is too aggressive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14331}",1408638660,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2lh4x2ggoyfra3mal2dj,task_description,resolved
+VisualEditor shows double page title after edit when 'edittop' gaget (or similar) is enabled,"Change 155577 merged by jenkins-bot:
+mw.ViewPageTarget: Be more careful when updating page title
+
+https://gerrit.wikimedia.org/r/155577",1408642051,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2lh4x2ggoyfra3mal2dj,task_subcomment,NA
+VisualEditor shows double page title after edit when 'edittop' gaget (or similar) is enabled,"Change 155577 had a related patch set uploaded by Bartosz Dziewoński:
+mw.ViewPageTarget: Be more careful when updating page title
+
+https://gerrit.wikimedia.org/r/155577",1408639000,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2lh4x2ggoyfra3mal2dj,task_subcomment,NA
+"VisualEditor: Reinstate the semantic class on the ""Save page"" button","The firsteditve tour (the ""first edit"" tour, specialised for VE) relied on the ve-ui-toolbar-saveButton class to attach a guider to the ""Save page"" toolbar button. The class was removed as part of https://git.wikimedia.org/commit/mediawiki%2Fextensions%2FVisualEditor.git/cc089d6bd3334791453c6474c56f49d4a2d243dd.
+
+At the moment, there's no resilient selector that we can use to reference just that element. Can the class be reinstated?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1408547940,PHID-USER-w3pd7vqenmta6vpmhwcn,False,PHID-TASK-5djpuvo4wkwj32snxeof,task_description,resolved
+"VisualEditor: Reinstate the semantic class on the ""Save page"" button","**gerritadmin** wrote:
+
+Change 155280 merged by jenkins-bot:
+Reinstate the ve-ui-toolbar-saveButton class
+
+https://gerrit.wikimedia.org/r/155280",1408553307,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5djpuvo4wkwj32snxeof,task_subcomment,NA
+"VisualEditor: Reinstate the semantic class on the ""Save page"" button","**gerritadmin** wrote:
+
+Change 155280 had a related patch set uploaded by Phuedx:
+Reinstate the ve-ui-toolbar-saveButton class
+
+https://gerrit.wikimedia.org/r/155280",1408549473,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5djpuvo4wkwj32snxeof,task_subcomment,NA
+"Search results (for links, redirects, categories…) should select the exact match by default","This is somewhat related to {T64917}.
+
+When you add an internal link, or otherwise are looking at search results, VisualEditor should defaultly select any page that is an exact match for what you've typed.  In particular, if you search for ""Computer"", and there actually is a page at [[Computer]], then it should default to [[Computer]], not to [[Computer science]] or whatever else comes up first in the search system.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T71780}
+{T57390}
+{T64917}
+{T71716}",1408396020,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6rg4t2epelfvjth52scv,task_description,resolved
+"Search results (for links, redirects, categories…) should select the exact match by default","Current situation:
+
+* If you type ""fool"" and press return or click ""Insert"" you get a link to ""fool"", even if it doesn't appear in the suggestions list.
+* If you type ""fool"" and there are no title matches, you'll get what you've typed in as a redlink suggestion.
+* If you type ""fool"" and the only title match result is ""Fool's gold"" as a redirect to ""Pyrite"", you'll get the latter shown first with the former directly below it. You won't get a redlink suggestion.
+* If you type ""fool"" and there are several title match results, the ""best"" match from the search engine will show first even if that isn't the closest match.
+
+I think this is ""good enough"", and much better than when this task was filed.",1490394554,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6rg4t2epelfvjth52scv,task_subcomment,NA
+"Search results (for links, redirects, categories…) should select the exact match by default","This is aggravated if the exact match is a redirect, because matching redirects are in a separate section of the suggester, and the auto select only considers the first match in the 'articles' section of the suggester.
+
+
+When trying to link to the en.wp redirect ""Republic of Vietnam"" by typing this directly into the link dialog, the article ""Republic of Vietnam Airborne Division"" is selected. Ideally, as I type, I would expect that the exact redirect match of ""Republic of Vietnam is chosen and that after done, I get: [[Republic_of_Vietnam_Airborne_Division|Republic of Vietnam]].",1408402286,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-6rg4t2epelfvjth52scv,task_subcomment,NA
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation","I get ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation. This is rather insidious, as the error only happens when trying to save the page, which causes you to lose some work. (The same error happens when trying to switch to wikitext.)
+
+1. https://en.wikipedia.org/wiki/Combining_Grapheme_Joiner?veaction=edit
+2. Click the ""[1]"" link in the first paragraph, ""Add label"" from inspector
+3. Ctrl+X to cut the link (which should have been automatically selected)
+4. Click ""Cite"" → ""Basic"" to insert citation at the same spot
+5. Ctrl+V to paste the link, ""Insert reference""
+6. Click ""Save page"", receive error
+
+I'm not sure if step 2 is relevant, but I can consistently reproduce like this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1408381140,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_description,resolved
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation","Indeed, works for me too now.",1414051086,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_subcomment,NA
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation","I just followed these steps exactly (I opened the save dialog and viewed the diff, but did not actually change the content) and it worked fine. FIXED, or am I missing something?",1414008955,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_subcomment,NA
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation","(In reply to marielle.volz from comment #1)
+> I ca
+Whoops. Premature enter there.
+
+I can confirm, but in my case upon inserting the reference, I can no longer open any dialogs, including the citation dialog, nor the save dialog (i.e. when I hit save, nothing happens.)",1408381949,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_subcomment,NA
+"VisualEditor: ""TypeError: undefined is not a function"" when saving after pasting an external link into a basic citation",I ca,1408381693,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-kl7wuwhazni6b4o7mq2g,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Let's stop using inline <img> for thumbnail magnify icon. According to bug 69277 comment 11, there are 87619775 requests per day for 'magnify-clip.png'. It should be embedded in some piece of CSS.
+
+(Bug 65160 / [[mw:Thumbnail style update]] call for complete removal of the icon, but it would only affect the Vector skin.)
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: normal",1408301100,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2a4evartaeoqgwykf6un,task_description,resolved
+Stop using inline <img> for thumbnail magnify icon,"Change 161625 merged by jenkins-bot:
+Remove WMF deployment hack for 'Enlarge' image
+
+https://gerrit.wikimedia.org/r/161625",1411169229,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 154831 merged by jenkins-bot:
+Remove WMF deployment hack for 'Enlarge' image
+
+https://gerrit.wikimedia.org/r/154831",1411168756,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 161625 had a related patch set uploaded by Jforrester:
+Remove WMF deployment hack for 'Enlarge' image
+
+https://gerrit.wikimedia.org/r/161625",1411168341,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Deeming this merged now, as this is 'fixed' even without the clean-up from gerrit 154831 landing.",1408492493,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 154830 merged by jenkins-bot:
+Generate 'Enlarge' image in CSS rather than HTML (Linker)
+
+https://gerrit.wikimedia.org/r/154830",1408492283,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 154831 had a related patch set uploaded by Bartosz Dziewoński:
+Remove WMF deployment hack for 'Enlarge' image
+
+https://gerrit.wikimedia.org/r/154831",1408375536,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"Change 154830 had a related patch set uploaded by Bartosz Dziewoński:
+Generate 'Enlarge' image in CSS rather than HTML (Linker)
+
+https://gerrit.wikimedia.org/r/154830",1408375531,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"(In reply to Bartosz Dziewoński from comment #0)
+> Let's stop using inline <img> for thumbnail magnify icon. According to bug
+> 69277 comment 11, there are 87619775 requests per day for
+> 'magnify-clip.png'. It should be embedded in some piece of CSS.
+> 
+> (Bug 65160 / [[mw:Thumbnail style update]] call for complete removal of the
+> icon, but it would only affect the Vector skin.)
+
+Makes sense to me.",1408314957,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"(In reply to James Forrester from comment #2)
+> At this point this artefact would become a Monobook-only item, right? Should
+> it be moved to that repo at that point?
+
+No, it would become every-skin-but-Vector-including-custom-skins-only item.
+
+
+> VisualEditor only uses it through mediawiki.content.styling.parsoid
+
+It is also used in ve.ce.MWImageCaptionNode.js via 'magnifyClipIconURL' config item.",1408310707,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"(In reply to Bartosz Dziewoński from comment #0)
+> (Bug 65160 / [[mw:Thumbnail style update]] call for complete removal of the
+> icon, but it would only affect the Vector skin.)
+
+At this point this artefact would become a Monobook-only item, right? Should it be moved to that repo at that point?
+
+(In reply to Bartosz Dziewoński from comment #1)
+> A number of extensions also refer to this file directly, including
+> VisualEditor and WikiEditor. These will need to be updated.
+
+VisualEditor only uses it through mediawiki.content.styling.parsoid (faked Vector-like content rendering; yes yes, I know…), which should be fixed as the fixing for bug 65160.",1408310491,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+Stop using inline <img> for thumbnail magnify icon,"A number of extensions also refer to this file directly, including VisualEditor and WikiEditor. These will need to be updated.
+
+There are probably also innumerable user scripts that refer to it. Looking at bug 69277 comment 10, the Popups gadget is a big offender.",1408301230,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2a4evartaeoqgwykf6un,task_subcomment,NA
+VisualEditor Mobile: tapping into middle of link inspector text causes lots of issues,"Steps to repro:
+
+1. In prod/stable on iPad, enter VE edit mode and tap on a 2-word wikilink (e.g. [[European robin]])
+2. Open link inspector
+3. Tap on the end of the second word (e.g., after ""European"") to drop cursor between the two words
+4. Attempt to backspace and enter new text
+
+I've seen a number of weird things happen after this step:
+
+* No suggestions come up in the drop-down, even when there clearly should be some
+* Adding new text or spaces is impossible; you can only backspace
+* Backspacing too fast closes the dialog (known issue) or crashes Safari (not sure if known issue)
+
+None of these seem to happen if you tap at the end of the text in the link inspector (e.g., after ""robin"") and backspace/add new text from there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408053060,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-e5hoozp2bm6dugby2g2l,task_description,resolved
+VisualEditor Mobile: tapping into middle of link inspector text causes lots of issues,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487324,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e5hoozp2bm6dugby2g2l,task_subcomment,NA
+VisualEditor Mobile: tapping into middle of link inspector text causes lots of issues,"Sorry, that should be:
+
+3. Tap on the end of the FIRST word (e.g., after ""European"")",1408053162,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-e5hoozp2bm6dugby2g2l,task_subcomment,NA
+VisualEditor:  Category input box is too small (sometimes),"Steps to reproduce:
+
+1.  Add a short category or three.  (At en.wp, you can add Category:1, Category:2, and Category:3, etc.)  The box for adding the next cat should still be on the same (first) line.
+
+2.  Now try to add a very long category name.  If you're on Meta, try Category:Association of Wikipedians - AWWDMBJAWGCAWAIFDSPBATDMTD
+
+
+Result:  
+
+The search field pops up, but you can't really see much of it.  In particular, unless what you're trying to add can be reliably added from the first and last few characters, then you might add the wrong category.
+
+
+Expectation:  
+
+The category field will be wide enough to see what's in the search list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57200",1408050900,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-l5v5vrwex3hz2ct4owi2,task_description,duplicate
+VisualEditor:  Category input box is too small (sometimes),[[ https://www.mediawiki.org/wiki/Topic:T8cllr8xqawliza4 | We got a new report about this from Ziko. ]],1470321534,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-l5v5vrwex3hz2ct4owi2,task_subcomment,NA
+VisualEditor:  Category input box is too small (sometimes),*** Bug 71657 has been marked as a duplicate of this bug. ***,1414086378,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-l5v5vrwex3hz2ct4owi2,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots. Without this all the screenshots in these languages show squares instead of the correct characters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408020900,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_description,resolved
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"I'm closing this. Installing fonts in the future should be simple enough... I think :)
+
+Thanks a lot for the help!",1412025554,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,Amir can we close this bug or maybe we can keep it open to track the installation of fonts for all the other languages?,1412017255,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162869 merged by jenkins-bot:
+Running language screenshot job using local Firefox
+
+https://gerrit.wikimedia.org/r/162869",1412002045,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162869 had a related patch set uploaded by Zfilipin:
+Running language screenshot job using local Firefox
+
+https://gerrit.wikimedia.org/r/162869",1411648144,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162604 merged by Filippo Giunchedi:
+contint: labs slaves +mediawiki::packages::fonts
+
+https://gerrit.wikimedia.org/r/162604",1411642949,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Thanks Antoine, screenshots are fine now! :)",1411574356,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"I have installed the puppet patch on all jenkins instances:
+
+Info: Applying configuration version '1411572497'
+Notice: /Stage[first]/Apt::Update/Exec[/usr/bin/apt-get update]/returns: executed successfully
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-tamil-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-takao-mincho]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-75dpi]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-liberation]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-100dpi]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-ubuntu-font-family]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-lyx]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-punjabi-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-ezra]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-kochi-gothic]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[culmus-fancy]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-nuosusil]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-lklug-sinhala]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-wqy-zenhei]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-takao-gothic]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-mgopen]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-arphic-uming]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[culmus]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-malayalam-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-vlgothic]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-gujarati-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-lao]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-telugu-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-kannada-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-unfonts-extra]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-oriya-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-linuxlibertine]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-mplus]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-abyssinica]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-thai-tlwg]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-scheherazade]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-arphic-ukai]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-sil-padauk]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-bengali-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-kacst]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-khmeros]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-kochi-mincho]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-tibetan-machine]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-nafees]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-manchufont]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-base]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-devanagari-fonts]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Apt::Noupgrade/Package[update-manager-core]/ensure: removed
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-dejavu-extra]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-farsiweb]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[fonts-arabeyes]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[ttf-alee]/ensure: ensure changed 'purged' to 'present'
+Notice: /Stage[main]/Mediawiki::Packages::Fonts/Package[xfonts-scalable]/ensure: ensure changed 'purged' to 'present'
+Notice: Finished catalog run in 636.32 seconds",1411573386,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162604 had a related patch set uploaded by Hashar:
+contint: labs slaves +mediawiki::packages::fonts
+
+https://gerrit.wikimedia.org/r/162604",1411572428,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Kartik proposed a change to add the font 'fonts-wqy-zenhei' https://gerrit.wikimedia.org/r/#/c/154086/  but it has been abandoned.
+
+Daniel Zahn pointed out it is made by https://github.com/wikimedia/operations-puppet/blob/8f14fc7cdbfb5c6f16cb4b1a3bbc64dfd5d200e8/modules/mediawiki/manifests/multimedia.pp#L91
+
+But:
+
+hashar@integration-slave1002:~$ apt-cache policy ttf-wqy-zenhei 
+ttf-wqy-zenhei:
+  Installed: (none)
+  Candidate: 0.9.45-3.1ubuntu1
+  Version table:
+     0.9.45-3.1ubuntu1 0
+        500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
+
+
+So apparently mediawiki::packages::fonts is not applied on the continuous integration slaves though we include ::mediawiki::packages , we apparently need to explicitly add that puppet class.",1411572208,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"I have created a short script[1] and a simple jenkins job[2] to demonstrate the problem.
+
+The script opens main page using firefox in several languages and takes screenhots[3-5]. Screenshots show that Chinese and Japanese characters are not displayed properly.
+
+Are we doing something wrong? Or, is the jenkins slave where the firefox is running missing the fonts?
+
+1: https://gerrit.wikimedia.org/r/#/c/162576/2/modules/ve-mw/tests/browser/fonts.rb,cm
+2: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox-69535/
+3: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox-69535/lastSuccessfulBuild/artifact/modules/ve-mw/tests/browser/ja.png/*view*/
+4: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox-69535/lastSuccessfulBuild/artifact/modules/ve-mw/tests/browser/zh-hans.png/*view*/
+5: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox-69535/lastSuccessfulBuild/artifact/modules/ve-mw/tests/browser/zh-hant.png/*view*/",1411570315,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162576 abandoned by Zfilipin:
+WIP [BrowserTest] reproducing bug 69535
+
+https://gerrit.wikimedia.org/r/162576",1411569870,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162576 had a related patch set uploaded by Zfilipin:
+WIP [BrowserTest] reproducing bug 69535
+
+https://gerrit.wikimedia.org/r/162576",1411564868,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162569 abandoned by Zfilipin:
+WIP reproducing bug 69535
+
+https://gerrit.wikimedia.org/r/162569",1411564681,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 162569 had a related patch set uploaded by Zfilipin:
+WIP reproducing bug 69535
+
+https://gerrit.wikimedia.org/r/162569",1411560943,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Submitted Sauce Labs support ticket:
+
+https://support.saucelabs.com/requests/15238",1411556975,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"The jobs as they are configured now run on Sauce, whee we cannot control the fonts.
+
+We need to run the jobs on a machine where we can install the required fonts.",1411485994,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 154086 abandoned by Dzahn:
+Add Chinese fonts for VE screenshots feature
+
+Reason:
+abandoning because the related bug is resolved. also it's easy to restore if needed. cheers, Daniel
+
+https://gerrit.wikimedia.org/r/154086",1410565690,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"(In reply to Željko Filipin from comment #5)
+> Vikas, Amir, are Japanese and Chinese screenshots now good?
+
+ping :)",1410561749,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Vikas, Amir, are Japanese and Chinese screenshots now good?",1409595399,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Daniel Z. pointed out that ""ttf-wqy-zenhei"" works as a package name on both Precise and Trusty. On Trusty, it is a virtual package that depends on ""fonts-wqy-zenhei"", to make migration easier. And, in fact, we already install it:
+
+https://github.com/wikimedia/operations-puppet/blob/8f14fc7cdbfb5c6f16cb4b1a3bbc64dfd5d200e8/modules/mediawiki/manifests/multimedia.pp#L91",1409349346,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"""fonts-wqy-zenhei"" is available on Trusty but not Precise:
+
+    [mw1001:~] $ cat /etc/issue
+    Ubuntu 12.04.4 LTS \n \l
+
+    [mw1001:~] $ apt-get --dry-run install fonts-wqy-zenhei
+    NOTE: This is only a simulation!
+          apt-get needs root privileges for real execution.
+          Keep also in mind that locking is deactivated,
+          so don't depend on the relevance to the real current situation!
+    Reading package lists... Done
+    Building dependency tree
+    Reading state information... Done
+    Package fonts-wqy-zenhei is not available, but is referred to by another package.
+    This may mean that the package is missing, has been obsoleted, or
+    is only available from another source
+
+    E: Package 'fonts-wqy-zenhei' has no installation candidate",1409348944,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,"Change 154086 had a related patch set uploaded by KartikMistry:
+Add Chinese fonts for VE screenshots feature
+
+https://gerrit.wikimedia.org/r/154086",1408034978,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots,Moving to Wikimedia -> Quality.  Will have to figure out the font packages to install.  Maybe we could reuse the one defined in puppet class mediawiki::multimedia::fonts,1408022325,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ld45zmxdo6zli7e3kkzm,task_subcomment,NA
+VisualEditor: Undo resizing of image with explicit dimension in core doesn't render correctly,"1. Create an image in VE standalone with no width/heigh attrs (using the html editor mode)
+2. Resize the image in VE and undo
+
+The image doesn't go back to it's original size (in the view).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408015440,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hahseqx35ztkj6fz5cfs,task_description,resolved
+VisualEditor: Undo resizing of image with explicit dimension in core doesn't render correctly,"**gerritadmin** wrote:
+
+Change 154036 merged by jenkins-bot:
+Make sure image attribute is cleared if set to null
+
+https://gerrit.wikimedia.org/r/154036",1408016718,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hahseqx35ztkj6fz5cfs,task_subcomment,NA
+VisualEditor: Undo resizing of image with explicit dimension in core doesn't render correctly,"**gerritadmin** wrote:
+
+Change 154036 had a related patch set uploaded by Esanders:
+Make sure image attribute is cleared if set to null
+
+https://gerrit.wikimedia.org/r/154036",1408015486,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hahseqx35ztkj6fz5cfs,task_subcomment,NA
+Cannot copy text when dm.surface.enabled === false,"**Author:** `ryan.wold`
+
+**Description:**
+When disabling an Editor's .target.surface (by calling .disable()), the text is no longer editable, which is great.  However, the text in the disabled Editor cannot be copied and pasted.  It does not appear to make it to the clipboard. 
+
+Desired behavior is that the text can be be copied even when the editor is disabled.  Or perhaps there could be a setting/option around that.
+
+
+
+We traced this to ve.dm.Surface.prototype.changeInternal, where it returns immediately if the surface is disabled.
+
+if ( !this.enabled ) {
+  return;
+}
+
+I found this here: https://doc.wikimedia.org/VisualEditor/master/source/ve.dm.Surface.html#ve-dm-Surface-method-changeInternal
+
+
+I'm using OSX Mavericks and Google Chrome Version 36.0.1985.125.
+
+Thanks!
+
+- Ryan Wold
+  ryan.wold@neo.com
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407976320,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-faekguqj2f5hrdp6337k,task_description,declined
+Cannot copy text when dm.surface.enabled === false,The surface model also tracks selections so disabling the surface model would also disable any meaningful copy/paste functionality. dm.Surface#disable is not really intended for putting the surface into a useful read-only mode. What exactly are you trying to achieve?,1416318771,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-faekguqj2f5hrdp6337k,task_subcomment,NA
+Cannot copy text when dm.surface.enabled === false,"**ryan.wold** wrote:
+
+%%%*** Bug 69516 has been marked as a duplicate of this bug. ***%%%",1407976455,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-faekguqj2f5hrdp6337k,task_subcomment,NA
+VisualEditor:  Link tool is too small when adding captions to new images,"""Before"".  This is what you see at step #4.
+
+See attached screenshots.  
+
+Steps to reproduce:
+
+1.  Open VisualEditor and Insert > Media.
+
+2.  Pick and image and add a caption.
+
+3.  Select a word and press Command-K to make an internal link. 
+
+4.  Notice that the link inspector ought to be bigger, so you can see all the new buttons.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14165}",1407973920,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5soltwr3wdlryrbxkfmr,task_description,resolved
+VisualEditor:  Link tool is too small when adding captions to new images,Works for me in Firefox 31 and Safari 6.,1410217508,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5soltwr3wdlryrbxkfmr,task_subcomment,NA
+VisualEditor:  Link tool is too small when adding captions to new images,"This appears to now be fixed?
+
+(Tested: Vector & Monobook on wmf19, wmf20, and pre-wmf21 with Firefox and Chrome.)",1410202626,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5soltwr3wdlryrbxkfmr,task_subcomment,NA
+VisualEditor:  Link tool is too small when adding captions to new images,"Created attachment 16188
+""After"":  This is what you get when you click inside the box, to get past bug 69510's focus problem.
+
+**Attached**: {F14166}",1407973999,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5soltwr3wdlryrbxkfmr,task_subcomment,NA
+VisualEditor: Inspectors close immediately in IE,"In Internet Explorer, if you open a link or comment inspector, it closes immediately after opening. It doesn't matter if you use Ctrl+K or the context or the toolbar or double-click or enter to open the inspector, the exact same thing happens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407970620,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5jyi6gfrdcofdg2qdtbv,task_description,resolved
+VisualEditor: Inspectors close immediately in IE,Fixed in https://gerrit.wikimedia.org/r/#/c/155182/,1408666091,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5jyi6gfrdcofdg2qdtbv,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary","This is related to bug 50872.
+
+If you click the edit link on a section, then that section's heading is pre-populated in the edit summary when you save.
+
+This does not work very well if you have turned on https://en.wikipedia.org/wiki/MediaWiki:Gadget-edittop.js (""Add an [edit] link for the lead section of a page"") in the gadgets for your preferences.  Editing the first (lead) section of the page gets a suggested edit summary that includes the first section heading on the page i.e., the section heading immediately underneath the section you were actually editing.
+
+The link for 'edit source' says:
+
+https://en.wikipedia.org/w/index.php?title=User:WhatamIdoing&action=edit&section=0&summary=/*%20top%20*/%20 
+
+The link for 'edit' says:
+
+https://en.wikipedia.org/w/index.php?title=User:WhatamIdoing&veaction=edit&vesection=1
+
+The subsequent section editing links are all correct.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407969600,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-orpzganqdg7lbcpdb7jk,task_description,resolved
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary",I went back and fixed up that gadget so it should handle VE links correctly. This change to pick up 'summary' from the URL should take affect on all Wikipedias on Thursday (it should already be on test and test2).,1409953109,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary","**gerritadmin** wrote:
+
+Change 156744 merged by jenkins-bot:
+Pick up 'summary' parameter from URL to use as initial edit summary
+
+https://gerrit.wikimedia.org/r/156744",1409261350,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary","**gerritadmin** wrote:
+
+Change 156744 had a related patch set uploaded by Alex Monk:
+Pick up 'summary' parameter from URL to use as initial edit summary
+
+https://gerrit.wikimedia.org/r/156744",1409191026,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary",Although VE should probably pick up the default summary from the URL.,1407976491,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary","It looks like the gadget needs to be fixed to deal with VE. In particular, it needs to be able to deal with 've' between the '&' and 'section='.",1407975957,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-orpzganqdg7lbcpdb7jk,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work","Steps to reproduce:
+
+1.  Open VisualEditor and select a word.
+
+2.  Press Command-K to open the link inspector.
+
+3.  We're going to make an external link to http://www.example.com so start typing:  h-t-t-p-:-/-/-w-w-w-
+
+4.  Why is it trying to find an internal page for the URL I'm typing?
+
+
+If you're obviously typing in a URL, the search feature should be disabled.  Offering to make a link to the ""local page"" http://www.example.com risks broken links like this:  https://en.wikipedia.org/w/index.phpdiff=621124784&oldid=620566012
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44011",1407968460,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_description,open
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work","About external links detection, it now works well.
+
+About links to pages with URL-like names, [[https://test.wikipedia.org/w/index.php?title=User:Pols12/sandbox&diff=455494&oldid=411023 | VE adds]] `./` instead of `:` to prefix the page name, even if you manually set a colon before the URL. By the way, prefixing colon seems to don’t be required.
+
+Since VE preview is fine, I think this is a Parsoid issue, that’s why I re-add Parsoid project for a new review (sorry if I’m wrong).
+
+Related: {T222082}.",1604536570,PHID-USER-unpoeiyj52rmcfqi5rbw,True,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work","About external links detection, it now works well.
+
+About links to pages with URL-like names, [[https://test.wikipedia.org/w/index.php?title=User:Pols12/sandbox&diff=455494&oldid=411023 | VE adds]] `./` instead of `:` to prefix the page name, even if you manually set a colon before the URL.
+
+Since VE preview is fine, I think this is a Parsoid issue, that’s why I re-add Parsoid project for a new review (sorry if I’m wrong).
+
+Related: {T222082}.",1604536306,PHID-USER-unpoeiyj52rmcfqi5rbw,True,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work",See also {T76398},1417554553,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work",">>! In T71500#749617, @Krenair wrote:
+> Interesting that MediaWiki allows you to create pages that are URLs, but you can't link to them...
+
+Sorry - it turns out you can link to internal pages named like URLs in MediaWiki, but you have to use the ':' prefix.",1417554365,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work",Bug 44011 sounds slightly related,1407975023,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work","Interesting that MediaWiki allows you to create pages that are URLs, but you can't link to them...",1407974528,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-lp6gjih6erk6yxlyvwlx,task_subcomment,NA
+Use {{!}} rather than <nowiki>|</nowiki> when inserting a | in a template argument,"In https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=621079160&oldid=621075505 it is pointed out that if an argument to a template contains a | then <nowiki>|</nowiki> is added. The new magic word {{!}} might be a better alternative.
+
+See also bug 67863
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407949080,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-jbatrq3ogdwn3vlvgukn,task_description,resolved
+Use {{!}} rather than <nowiki>|</nowiki> when inserting a | in a template argument,"Change 195559 merged by jenkins-bot:
+T71482: Convert | to {{!}} in template parameters
+
+[[https://gerrit.wikimedia.org/r/195559]]",1426018520,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jbatrq3ogdwn3vlvgukn,task_subcomment,NA
+Use {{!}} rather than <nowiki>|</nowiki> when inserting a | in a template argument,"Change 195559 had a related patch set uploaded (by Marcoil):
+T71482: Convert | to {{!}} in template parameters
+
+[[https://gerrit.wikimedia.org/r/195559]]
+",1426010733,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jbatrq3ogdwn3vlvgukn,task_subcomment,NA
+Use {{!}} rather than <nowiki>|</nowiki> when inserting a | in a template argument,A relevant diff is https://en.wikipedia.org/w/index.php?title=Bone_remodeling&diff=prev&oldid=621072608,1407949415,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-jbatrq3ogdwn3vlvgukn,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","For citation template references we may also want to specify a subset of parameters to show first.
+Links and citation mocks:
+{F18090}
+
+{F18092}
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407939960,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_description,resolved
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",,1423821836,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",,1423821811,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",,1417648165,PHID-USER-flenunkasbjk4topxvaj,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",,1417570409,PHID-USER-flenunkasbjk4topxvaj,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","(In reply to Bartosz Dziewoński from comment #6)
+> (I tried messing around with ve.dm.Converter too, but it seems impossible to
+> render the contents of templated references without involving the surface,
+> probably because they're magically generated in ve.ce.)
+
+Yeah, this needs CE. I think we may have to rethink how we do descriptions a little.",1411777912,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","(I tried messing around with ve.dm.Converter too, but it seems impossible to render the contents of templated references without involving the surface, probably because they're magically generated in ve.ce.)",1411776880,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","I played with it and the following sort of works for all reference node types. There must be a better way to do it, but I can't find one. (It also doesn't update the tooltip after reference contents are changed, probably because that is done deferred or something.)
+```
+ve.ce.MWReferenceNode.static.getDescription = function ( model ) {
+  var refModel = ve.dm.MWReferenceModel.static.newFromReferenceNode( model );
+  var surface = ve.init.target.createSurface( refModel.getDocument() );
+  var text = $( surface.getView().$element ).text();
+  surface.destroy();
+  return text;
+};
+```",1424101267,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","I played with it and the following sort of works for all reference node types. There must be a better way to do it, but I can't find one. (It also doesn't update the tooltip after reference contents are changed, probably because that is done deferred or something.)
+
+ve.ce.MWReferenceNode.static.getDescription = function ( model ) {
+  var refModel = ve.dm.MWReferenceModel.static.newFromReferenceNode( model );
+  var surface = ve.init.target.createSurface( refModel.getDocument() );
+  var text = $( surface.getView().$element ).text();
+  surface.destroy();
+  return text;
+};",1410961821,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","Any attempt to ""parse"" the template parameters is going to become very complex or fail to address the needs of wikis other than the English Wikipedia. How about just displaying the parsed content of the reference, stripped of links and any block markup, and limited to some length?",1410956058,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","I think we'd much rather keep the current model of showing the name of something shown, or the value of something not shown (like for HTML comments)…",1408487253,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels","We could list template values in order until we run out of room, but this may not lead to desirable results, for example the first parameter in {{Cite web}} is URL.
+
+A more complex solution would be to come up with a format for defining how to generate the summary of a template and store it in template data, either as a value on the column (summary order):
+
+Field     Desc  Summary order
+url       ...   null
+publisher ...   2
+title     ...   1
+date      ...   3
+month     ...   null
+
+A simplified version of this would just flag one field as being used in the summary.
+
+etc.
+
+Or as a string concatenation message somewhere:
+
+""{{{title}}}, {{{publisher}}} - {{{date}}}""",1408464080,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels",*** Bug 69744 has been marked as a duplicate of this bug. ***,1408464025,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-mmjlnjyrfskgvyw6dlte,task_subcomment,NA
+"VisualEditor: If you just change an image, the border parameter setting is lost","When you just change image on a media, the border parameter is lost.
+
+https://test2.wikipedia.org/w/index.php?title=BorderLost&diff=98843&oldid=98842
+
+Safari/Mac OS X
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407887580,PHID-USER-hhw22zfd2xzrsyc22lp5,False,PHID-TASK-qfttw2uqh62xx2xebpyu,task_description,resolved
+"VisualEditor: If you just change an image, the border parameter setting is lost","Change 149217 merged by jenkins-bot:
+Make the image model persistent
+
+https://gerrit.wikimedia.org/r/149217",1409242088,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qfttw2uqh62xx2xebpyu,task_subcomment,NA
+"VisualEditor: If you just change an image, the border parameter setting is lost","Change 149217 had a related patch set uploaded by Mooeypoo:
+Make the image model persistent
+
+https://gerrit.wikimedia.org/r/149217",1408487294,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qfttw2uqh62xx2xebpyu,task_subcomment,NA
+"VisualEditor: After inserting a comment and a link, a cursor is moved at the end of the line, but typed text gets inserted between the comment and the link","screenshot
+
+1> open a page in VE, insert a comment.
+2> While the comment is still highlighted, insert a link. Notice the cursor is in between the comment and the link.
+3>Now select the Language style text. Click “Done” in the language inspector.
+Notice the cursor has now moved to the end of the comment. Type in some text, it gets inserted after the link. See screenshot.
+
+Try the above steps, but instead of comment insert a Formula.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14630}",1407858060,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-pyvddazcokg6hnj3x73g,task_description,open
+"VisualEditor: After inserting a comment and a link, a cursor is moved at the end of the line, but typed text gets inserted between the comment and the link","Confirmed in Betalabs and test2. 
+
+After inserting a comment and a link, a cursor is moved at the end of the line, but typed text gets inserted between the comment and the link.",1413910361,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-pyvddazcokg6hnj3x73g,task_subcomment,NA
+"VisualEditor: After inserting a comment and a link, a cursor is moved at the end of the line, but typed text gets inserted between the comment and the link","Environment-test2 and beta
+Found only in chrome and Safari.",1407858464,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-pyvddazcokg6hnj3x73g,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","See e.g. http://parsoid-lb.eqiad.wikimedia.org/wikimania2014wiki/Submissions%2FVisualEditor_%E2%80%94_engineering_against_the_odds?oldid=47825 vs https://wikimania2014.wikimedia.org/wiki/Submissions/VisualEditor_%E2%80%94_engineering_against_the_odds?oldid=47825
+
+Wikitext:
+
+; '''Sunday August 10, 12:30, [[Frobisher 123]]'''
+
+Parsoid HTML:
+
+<dl><dt> <b>Sunday August 10, 12</b></dt><dd><b>30, <a rel=""mw:WikiLink"" href=""./Frobisher_123"">Frobisher 123</a></b></dd></dl>
+
+
+PHP parser HTML:
+
+<dl><dt><b>Sunday August 10, 12:30, <a href=""/wiki/Frobisher_123"" title=""Frobisher 123"">Frobisher 123</a></b></dt></dl>
+
+It looks like this might be a syntax ambiguity, but hopefully we can have bug-for-bug compatibility with the PHP parser? :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407406200,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nfrlo5myv3v4eprweid5,task_description,resolved
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Change 155868 merged by jenkins-bot:
+Context aware parsing of definition list colon
+
+[[https://gerrit.wikimedia.org/r/155868]]",1418243010,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Change 155868 had a related patch set uploaded (by Arlolra):
+Context aware parsing of definition list colon
+
+[[https://gerrit.wikimedia.org/r/155868]]
+
+#patch-for-review",1418186385,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Updating the title to reflect that this is not just i/b wikitext context, but more general. As indicated in comment 2, this could use some more testing to better spec out what the right behavior is.",1408907806,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Change 155868 had a related patch set uploaded by Arlolra:
+b/i context aware parsing of definition list colon
+
+https://gerrit.wikimedia.org/r/155868",1408770525,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Thankfully, this is not related to time, but more related to context-sensitive tokenization of the "":"" char in a dt-dl list.
+
+;a:b
+;''a:b''
+
+The behavior require a bit more testing. Ideally, this is reasonably well-behaved that it can be fixed in the tokenizer without requiring a DOM transformation fixup.",1407407505,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+"The "":"" char in a definition list should be parsed differently depending on html-tag context it is found in.","Also, if you try to edit this, the resulting wikitext is something like '''Sunday August 10, 11''':30, [[Frobisher 123]]''' . It's trying to close the bolding twice.",1407406346,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nfrlo5myv3v4eprweid5,task_subcomment,NA
+VisualEditor: visualeditor-beta-warning help mentions non-existent Cancel button,"VE's help icon popup includes this ""visualeditor-beta-warning"" text:
+
+""VisualEditor is in 'beta'. You may encounter software issues, and you may not be able to edit parts of the page. To switch back to source editing at any time without losing your changes, open the dropdown next to \""{{int:visualeditor-toolbar-cancel}}\"" and select \""{{int:visualeditor-mweditmodesource-title}}\"".""
+
+But I don't see this Cancel button in the VE UI these days. The page options ""hamburger"" dropdown is now between (?) and [Save page].  It would be more helpful to show the hamburger icon in the help message, maybe WikiFont some day.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407356520,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-tsdm6dyf3irbaneuouwo,task_description,resolved
+VisualEditor: visualeditor-beta-warning help mentions non-existent Cancel button,Fixed in gerrit I36f13b2ff this morning. :-),1407361045,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tsdm6dyf3irbaneuouwo,task_subcomment,NA
+"VisualEditor: In the image advanced settings dialog, the alignment button order is wrong in RTL UI","In the image advanced settings dialog the image alignment buttons say ""right"", ""center"" and ""left"". In RTL UI their order is confusing, because the ""right"" button is on the ""left"" and vice versa. They should be in a more logical order. (The icons are correct, however.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1407316680,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-iuk3q3w2mokdzao6ks7s,task_description,resolved
+"VisualEditor: In the image advanced settings dialog, the alignment button order is wrong in RTL UI","Change 152043 merged by jenkins-bot:
+Flip direction buttons in media dialog in RTL
+
+https://gerrit.wikimedia.org/r/152043",1407331618,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iuk3q3w2mokdzao6ks7s,task_subcomment,NA
+"VisualEditor: In the image advanced settings dialog, the alignment button order is wrong in RTL UI","Change 152043 had a related patch set uploaded by Amire80:
+Correct buttons order in media advanced settings
+
+https://gerrit.wikimedia.org/r/152043",1407328384,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iuk3q3w2mokdzao6ks7s,task_subcomment,NA
+vagrant_ram overrides sometimes ignored/forgotten,"I have two overrides for vagrant_ram:
+
+* CirrusSearch has a puppet-managed override setting it to 1536
+* I have a .settings.yaml with the following contents:
+---
+vagrant_ram: 2048
+git_user: ''
+puppet_debug: true
+
+However, sometimes it's lower than both of those.  I.E.:
+------
+             total       used       free     shared    buffers     cached
+Mem:           993        933         60         18          0         23
+-/+ buffers/cache:        909         84
+Swap:            0          0          0
+------
+
+Tested with 6b27f39 (I know that's a little old, so feel free to close if you think it's been fixed since).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69720",1407194880,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-gomohetkd7ro7h36m2z2,task_description,resolved
+vagrant_ram overrides sometimes ignored/forgotten,"Probably fixed by 9da72b12c40f3e7a54870da8f6ec3c235ec6c337 (""Load settings if vagrant is run from subdirectory"")",1410294111,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-gomohetkd7ro7h36m2z2,task_subcomment,NA
+vagrant_ram overrides sometimes ignored/forgotten,"Went back to:
+
+===
+vagrant@mediawiki-vagrant:~$ free -m
+             total       used       free     shared    buffers     cached
+Mem:          2001       1037        964          8         17        370
+-/+ buffers/cache:        649       1352
+Swap:            0          0          0
+===
+
+after a vagrant reload --provision",1408850957,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-gomohetkd7ro7h36m2z2,task_subcomment,NA
+vagrant_ram overrides sometimes ignored/forgotten,"I noticed that I had this problem again after a vagrant halt, vagrant up cycle.  The reason I did the halt was that it was non-responsive, so it's possible it was already wrong even before the halt.
+
+Actual total and usage (when I have enough memory to do the free command, took a couple retries):
+
+===
+vagrant@mediawiki-vagrant:~$ free -m
+             total       used       free     shared    buffers     cached
+Mem:           993        938         55         20          0         25
+-/+ buffers/cache:        912         81
+Swap:            0          0          0
+
+===
+Roles:
+
+===
+Available roles:
+
+  accountinfo              * guidedtour               * popups                  
+  analytics                  gwtoolset                  proofreadpage           
+  antispam                   hadoop                     renameuser              
+  antispoof                  hive                       scholarships            
+  apisandbox                 https                      scribunto               
+  apparmor                   hue                        simple_miser            
+  babel                      imagemetrics               simple_performant       
+* betafeatures               interwiki                  sitematrix              
+  centralauth                jsduck                     svg                     
+  centralnotice              jsonconfig                 templatedata            
+  chromium                   mantle                     textextracts            
+  cirrussearch               massmessage                thumb_on_404            
+  cite                     * math                       timedmediahandler       
+  cldr                       mathsearch                 translate               
+* codeeditor                 mleb                       uls                     
+* cologneblue                mobileapp                  uploadwizard            
+  commons                    mobilefrontend             urlshortener            
+  commonsmetadata          * modern                     usermerge               
+  confirmedit                molhandler               * vectorbeta              
+  doublewiki               * monobook                 * visualeditor            
+* echo                       multimedia                 wikidata                
+  education                * multimediaviewer           wikidiff2               
+* eventlogging               navigationtiming         * wikieditor              
+  featuredfeeds              newusermessage             wikihiero               
+* flow                       oauth                      wikilove                
+  fss                        oozie                    * wikimediaevents         
+  fundraising                pagedtiffhandler           wikimediaincubator      
+* gadgets                  * pageimages                 wikimetrics             
+  gadgets2                   pagetriage                 wikitech                
+  geodata                  * parserfunctions            xhprof                  
+  geshi                    * parsoid                    zend                    
+* gettingstarted             pdfhandler                 zero                    
+  globalcssjs                phptags                                            
+  graph                      poem                                               
+===
+
+.settings.yaml
+
+===
+---
+git_user: ''
+vagrant_ram: 2048
+puppet_debug: true
+===
+
+vagrant.d/10-cirrussearch.yaml:
+===
+# Vagrant settings
+# Managed by puppet. Local changes will be lost on next puppet run.
+vagrant_ram: 2000
+forward_ports:
+    9200: 9200
+===",1408850801,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-gomohetkd7ro7h36m2z2,task_subcomment,NA
+vagrant_ram overrides sometimes ignored/forgotten,Possibly fixed by https://gerrit.wikimedia.org/r/154975 .,1408482768,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-gomohetkd7ro7h36m2z2,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?","The new Save dialog has two buttons at the top:  ""Cancel"" and ""Save""
+
+It's not clear whether Cancel means ""exit this dialog"" or ""lose all your work"".  Please change the label to something like ""Return to editing"" or ""Resume editing"", or something that clearly indicates that this button allows you to keep editing and will not exit VisualEditor and cause you to lose all of your work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407175800,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_description,resolved
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?",Verified the fix in production,1411681904,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?",Verified the fix in test2,1411083364,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?",Verified the fix in Betalabs,1410556935,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?","Change 159806 merged by jenkins-bot:
+Relabel the cancel button in the save dialog to ""Resume editing""
+
+https://gerrit.wikimedia.org/r/159806",1410471267,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+"VisualEditor:  ""Cancel"" button in the Save dialog is confusing.  How about ""Resume editing""?","Change 159806 had a related patch set uploaded by Jforrester:
+Relabel the cancel button in the save dialog to ""Resume editing""
+
+https://gerrit.wikimedia.org/r/159806",1410461574,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ht57jl47eqhrn5mu6y4k,task_subcomment,NA
+LivePreview doesn't allow interaction with page content outside of #wikiPreview (it is not passed to mw.hook),"Currently, LivePreview only passes the $wikiPreview to the hook
+https://github.com/wikimedia/mediawiki/blob/6709a1fd082bcbc1b89d499edeafa04fd2e8a517/resources/src/mediawiki.action/mediawiki.action.edit.preview.js#L101
+but the script changes the page content in many other places:
+https://github.com/wikimedia/mediawiki/blob/6709a1fd082bcbc1b89d499edeafa04fd2e8a517/resources/src/mediawiki.action/mediawiki.action.edit.preview.js#L31-L43
+The new content for these parts should also be made available to the user, by passing them to the hook (as VisualEditor does, for example
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/ccdc215a9882d6bb3e079ca822f64c9089c0d363/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.js#L1574
+).
+
+This would allow scripts like
+https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-featured-articles-links.js&oldid=619815637
+to update the modifications of the language links after the user makes some changes and use the live preview (in the example, the ""badges"" for featured/good articles in other languages).
+
+Also, this is likely what UniversalLanguageSelector needs in order to fix bug T53029.",1407163740,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-floz7aecowu5ipopiscf,task_description,open
+VisualEditor: Pasting <em> content into a VE-MW surface should down-convert <em>s to <i>s (and <strong>s to <b>s),"See diff at https://de.wikipedia.org/w/index.php?title=Schotts_Sammelsurium&diff=prev&oldid=132639553 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406824380,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-k65a4qbdt2vssa5txndo,task_description,resolved
+VisualEditor: Pasting <em> content into a VE-MW surface should down-convert <em>s to <i>s (and <strong>s to <b>s),"(In reply to Kurt Jansson from comment #1)
+> The ""<em>"" tag was inserted via italicised text in the clipboard. Source for
+> the text was a web page. I would expect that the VE drops the tag or
+> replaces it with two singe quotes.
+
+Yeah, good point. I thought we already did this?
+
+> Ich have no idea where the ""<nowiki>"" tag came from. I wasn't able to delete
+> it in the VE.
+
+That's because you ended up with a paragraph starting with a ' ', and to stop it turning into a <pre> block it instead – bug 66628. It's harmless, if irritating.",1414452746,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k65a4qbdt2vssa5txndo,task_subcomment,NA
+VisualEditor: Pasting <em> content into a VE-MW surface should down-convert <em>s to <i>s (and <strong>s to <b>s),"Looking at this again, I believe VE used to add those nowiki tags to prevent the line being displayed differently from the others because of the space at its beginning; and VE does retain formatting when pasting, but that can be avoided by using the shortcut Ctrl + Shift + V.",1414154500,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-k65a4qbdt2vssa5txndo,task_subcomment,NA
+VisualEditor: Pasting <em> content into a VE-MW surface should down-convert <em>s to <i>s (and <strong>s to <b>s),"The ""<em>"" tag was inserted via italicised text in the clipboard. Source for the text was a web page. I would expect that the VE drops the tag or replaces it with two singe quotes.
+
+Ich have no idea where the ""<nowiki>"" tag came from. I wasn't able to delete it in the VE.",1407345383,PHID-USER-ctff2aq5r64yvikejdwo,True,PHID-TASK-k65a4qbdt2vssa5txndo,task_subcomment,NA
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),"When resizing the window, after a certain point the MediaWiki page layout may change (media queries). This affects the offset from the left side of the page (specifically, width of the sidebar).
+
+However the toolbar caches its computed offset once and never updates it.
+
+1. Open window wider than 1024px with Vector skin in MediaWiki.
+2. Enter VisualEditor.
+3. Resize to < 980px.
+
+Expected:
+
+Sidebar shrinks (per Vector styles) and toolbar should still align with left edge of the page.
+
+Actual:
+
+Sidebar shrinks but toolbar stays behind causing an awkward gap to appear as well as odd interruption in the shadow. It results in part of the Save page button to go off-screen. 
+
+Other:
+
+The reverse happens as well. Opening a narrow window and scaling it up will cause it to stay behind in the other direction. It results in part of the toolbar overlapping links in the sidebar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1406808480,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yyipeqjrkozgykvwcduy,task_description,resolved
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),Verified the fix in production.,1416272093,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-yyipeqjrkozgykvwcduy,task_subcomment,NA
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),"Change 169232 merged by jenkins-bot:
+Recalculate toolbar size on window resize
+
+https://gerrit.wikimedia.org/r/169232",1414448177,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yyipeqjrkozgykvwcduy,task_subcomment,NA
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),"Change 169232 had a related patch set uploaded by Esanders:
+Recalculate toolbar size on window resize
+
+https://gerrit.wikimedia.org/r/169232",1414447822,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yyipeqjrkozgykvwcduy,task_subcomment,NA
+VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary),"Created attachment 16109
+Screenshot of bug.
+
+**Attached**: {F14581}",1406808595,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yyipeqjrkozgykvwcduy,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"These seem to be the leading cause of edit corruption right now.
+
+myEventWatcherDiv: https://ru.wikipedia.org/?diff=64516612 https://ru.wikipedia.org/?diff=64516412 https://pt.wikipedia.org/?diff=39659121 https://pt.wikipedia.org/?diff=39659108
+
+<embed> tags: https://pt.wikipedia.org/?diff=39696565
+
+<object> tags: https://fr.wikipedia.org/?diff=105796883 https://fr.wikipedia.org/?diff=105796959 https://fr.wikipedia.org/?diff=105797061
+
+I'm thinking we should put in hacks to remove these kinds of tags. Maybe at the point where we serialize the HTML and send it to Parsoid (ve.init.mw.Target#getHTML). If these tags are added immediately upon document creation (we'd need to get our hands on one of these bad plugins to test that) we could also consider trying to work around this in ve.createDocumentFromHtml instead. I suspect, though, that these tags are probably added asynchronously, and probably only in cases where we fall back to the iframe trick because DOMParser HTML support is not available.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406788020,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_description,resolved
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"Marking this as fixed, will keep an eye on the others in the next couple of weeks or so to see if those are resolved by it.",1412114053,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114010,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113119,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"(In reply to Alex Monk from comment #2)
+> I wonder if we can just do something like this
+> 
+> $( newDoc )
+> 	.remove( '[id=myEventWatcherDiv]' ) // Bug 51423
+> 	.remove( 'object[type=cosymantecnisbfw],
+> script[id=NortonInternetSecurityBF]' ) // Bug 63229
+> 	.remove( 'embed[id ^= xunlei_com_thunder_helper_plugin]' ) // Bug 63121
+> 	.remove( 'div[id=sendToInstapaperResults]' ) // Bug 61776
+> 	.remove( 'style[id=_clearly_component__css]' ) // Bug 53252
+> 	.remove( 'script[id=FoxLingoJs]' ) // Bug 52884
+> 	.remove( 'embed[type=application\\/x-datavault]' ) // Bug 52791
+> 	.remove( 'embed[type=application\\/iodbc]' ); // Bug 51521
+
+Yeah I was thinking about doing something like that. We have no easy way to know in advance what that will fix, but we can try it.",1412112352,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),"I wonder if we can just do something like this
+
+$( newDoc )
+	.remove( '[id=myEventWatcherDiv]' ) // Bug 51423
+	.remove( 'object[type=cosymantecnisbfw], script[id=NortonInternetSecurityBF]' ) // Bug 63229
+	.remove( 'embed[id ^= xunlei_com_thunder_helper_plugin]' ) // Bug 63121
+	.remove( 'div[id=sendToInstapaperResults]' ) // Bug 61776
+	.remove( 'style[id=_clearly_component__css]' ) // Bug 53252
+	.remove( 'script[id=FoxLingoJs]' ) // Bug 52884
+	.remove( 'embed[type=application\\/x-datavault]' ) // Bug 52791
+	.remove( 'embed[type=application\\/iodbc]' ); // Bug 51521",1412112163,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv),Here's a novel one: https://sv.wikipedia.org/?diff=27732757,1412096766,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-puc2xw4bd2b2xsnoq5zd,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,"The context menu for Basic Reference is still appearing, letting user to get stuck inside it after adding dfferent elements in it.
+We need to disable it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406774460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fvgll6ju7di7hlztbvdl,task_description,declined
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,The context menu for math and references list started appearing too.,1414614982,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,This is again appearing in mobile.,1414614819,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,Verified the fix in production.,1408653939,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,Verified the fix in test2,1408051332,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,Verified the fix in Betalabs,1407946189,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,The context menu for basic reference is still appearing in Betalabs,1407350062,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,"Change 151807 merged by jenkins-bot:
+Disable basic reference on mobile
+
+https://gerrit.wikimedia.org/r/151807",1407320455,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile,"Change 151807 had a related patch set uploaded by JGonera:
+Disable basic reference on mobile
+
+https://gerrit.wikimedia.org/r/151807",1407200132,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fvgll6ju7di7hlztbvdl,task_subcomment,NA
+VisualEditor lost the first character when inputting with some IME,"**Author:** `hu60.cn`
+
+**Description:**
+There is a strange trouble happen when I edit with Baidu Pinyin (a Chinese IME) on Firefox runing on Windows 8.1. Baidu Pinyin can input two or more characters once. When I input ""你好"" at once, display is OK. But when I save or delete some characters, the display refreshs and ""你"" lost, a blank instead of the character.
+
+Example:
+
+I input ""可视化编辑器已可用。""
+
+And save, it looks like:
+
+ 视化 辑器 可用。
+
+The first character at each input lost.
+
+However, when I switch IME to Microsoft Pinyin, the BUG disappear. All input works fine. Switch to Baidu Pinyin, the BUG continuing.
+
+I don't know what happened.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 8.1
+**Platform**: PC",1406770740,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4ptlg2ito6vzer5kk57s,task_description,open
+VisualEditor lost the first character when inputting with some IME,Does this block T51569?,1428337360,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-4ptlg2ito6vzer5kk57s,task_subcomment,NA
+VisualEditor lost the first character when inputting with some IME,"**hu60.cn** wrote:
+
+I made a mistake. The IME I use is Sogou Pinyin, not Baidu Pinyin.",1406850777,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4ptlg2ito6vzer5kk57s,task_subcomment,NA
+VisualEditor Mobile:CE is getting zoomed in on rotating the screen orientation in iPad Mini,"Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Place the cursor anywhere in CE
+3.Change the screen orientation to landscape
+4.Again rotate the screen
+
+Observed Result:
+CE gets zoomed in each time I rotate the screen
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406760900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e33lumruqobfcwjjasrw,task_description,resolved
+VisualEditor Mobile:CE is getting zoomed in on rotating the screen orientation in iPad Mini,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487201,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e33lumruqobfcwjjasrw,task_subcomment,NA
+VisualEditor Mobile:CE is getting zoomed in on rotating the screen orientation in iPad Mini,Needs re-testing.,1430336522,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e33lumruqobfcwjjasrw,task_subcomment,NA
+Parsoid: Automatic newline prepending to table-template causes incorrect rendering and messed up HTML in Parsoid parser,"+++ This bug was initially created as a clone of Bug #68297 +++
+
+On mediawiki.org, there is a family on fancy templates like [[mw:Template:MW 1.23]] that generate a right-floated MediaWiki version number in a frame.
+
+These templates generate a wikitext table (starting with '{|'), which means that due to bug 529 / bug 12974 a newline is prepended before it. This behavior is incredibly annoying in practice, but it seems that we're very much wedded to it because it made Parsoid people's lives easier.
+
+However, Parsoid rendering of this particular template is inconsistent with PHP. On [[mw:Manual:Skinning#Localisation_messages]], PHP generates an empty paragraph before the table, while Parsoid doesn't and produces an about-grouped pair of <span>\n</span><table>…</table> (the span tag only contains the prepended newline).
+
+This rendering, that looks good in Parsoid/VisualEditor, therefore looks like crap in PHP parser.
+
+Note that the <span> is not nested in a <p> or any other block-level element, it just sits there right in the <body>. (It is not visible since, as I mentioned, it just contains some whitespace.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406735100,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5bjxxerf7yoz2uejrrao,task_description,resolved
+Parsoid: Automatic newline prepending to table-template causes incorrect rendering and messed up HTML in Parsoid parser,"```
+[subbu@earth:~/work/wmf/parsoid] echo ""{{MW 1.22|and later}} MediaWiki 1.22 added support for <code>."" | php bin/parse.php --domain www.mediawiki.org --wt2wt
+{{MW 1.22|and later}} MediaWiki 1.22 added support for <code>.
+```",1590706405,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-5bjxxerf7yoz2uejrrao,task_subcomment,NA
+Parsoid: Automatic newline prepending to table-template causes incorrect rendering and messed up HTML in Parsoid parser,"The php parser no longer seems to generate an empty paragraph and the parsoid output seems comparable. The span wrapping of the newline is to mark it as template generated for suppressing on roundtrip.
+
+The `_rtselser/mediawikiwiki/Manual:Skinning?oldid=1072136` seems fine.
+
+But of note,
+
+```
+echo ""{{MW 1.22|and later}} MediaWiki 1.22 added support for <code>."" | node parse --prefix mediawikiwiki --wt2wt
+{{MW 1.22|and later}}
+<nowiki> </nowiki>MediaWiki 1.22 added support for <code>.
+```
+
+",1418932905,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-5bjxxerf7yoz2uejrrao,task_subcomment,NA
+VisualEditor Mobile: Cannot type the reference name inside Re-use existing reference dialog unless select a reference from that dialog,"Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Add few references 
+3.Now open Re-use existing reference dialog
+4.Try to type a reference name in the field
+
+Observed Result: 
+Nothing happens
+
+5.Save the page
+6.Reopen the page and try again typing reference name in the field,
+
+Observed Result:
+Nothing happens
+
+
+7.Now select any reference from the list
+8.Reopen the Re-use dialog,try typing a reference name in that dialog
+
+Observed Result
+this time it will work
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406673660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zhhx6gkxdzizm66cix7v,task_description,resolved
+VisualEditor Mobile: Cannot type the reference name inside Re-use existing reference dialog unless select a reference from that dialog,"Seems to work for me now (in Citoid), but it's a bit of a mess. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488531,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zhhx6gkxdzizm66cix7v,task_subcomment,NA
+VisualEditor Mobile: Cannot type the reference name inside Re-use existing reference dialog unless select a reference from that dialog,"Seems to work for me now (in Citoid), but it's a bit of a mess. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488526,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zhhx6gkxdzizm66cix7v,task_subcomment,NA
+VisualEditor Mobile: Cannot type the reference name inside Re-use existing reference dialog unless select a reference from that dialog,Needs re-testing.,1430336312,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zhhx6gkxdzizm66cix7v,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"screenshot1
+
+Environment- test2
+
+Steps-
+1> open a page in VE.
+2> Insert ->Media. 
+3>Select to add a media file. Opens the Media Settings dialog.
+4>Now click on “Caption” pane and Select Language from the text style menu, closes the drop down.
+5>Cursor is at the beginning of the line. Click again on the style text menu to see that the Language is selected . See screenshots.
+6> Notice typing the first letter deselects the Language from the drop-down, and so the language inspector never appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14328}",1406649060,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-psfncojk42sp2n4fkx6z,task_description,resolved
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Created attachment 16121
+screenshot
+
+**Attached**: {F14330}",1406921105,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,In Chrome and FF only the Language Inspector appears out of place when launched for the first time.The steps to reproduce are the same.See screenshot.Both in test2 and beta.,1406921066,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Change 150738 merged by jenkins-bot:
+Set a default language for ve.dm.Document if we can't guess it otherwise
+
+https://gerrit.wikimedia.org/r/150738",1406765133,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,This is… interesting.,1406764869,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Change 150738 had a related patch set uploaded by Jforrester:
+Set a default language for ve.dm.Document if we can't guess it otherwise
+
+https://gerrit.wikimedia.org/r/150738",1406764817,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null)., baehavior found in betalabs.,1406652768,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Ed, is this fixed by gerrit 149635?",1406650596,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).,"Created attachment 16089
+screenshot2
+
+**Attached**: {F14329}",1406649118,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-psfncojk42sp2n4fkx6z,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"screenshot
+
+Environment- test2,betalabs, production.
+Steps-
+1> Open a page in VE.
+2> Insert ->Media. 
+3>Select to add a media file. Opens the Media Settings dialog.
+4>Now click on “Alternative Text”. This should make the “Caption” inaccessible, but it is not. See screenshot.
+Now click on Caption pane, and then into Alternative Text, this makes the toolbar in the Caption pane blurred.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14322}",1406647800,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-qkdhag2mz377tvfw5d6p,task_description,resolved
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,Issue Resolved in test2 and beta.,1406922763,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"Change 150304 merged by jenkins-bot:
+Focus the caption surface on initialization
+
+https://gerrit.wikimedia.org/r/150304",1406664021,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"Change 150304 had a related patch set uploaded by Mooeypoo:
+Focus the caption surface on initialization
+
+https://gerrit.wikimedia.org/r/150304",1406662799,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"Okay, I seem to have misunderstood the bug, sorry about that; I thought you were talking about the entire caption field, not just the toolbar.
+
+I'll take care of this. Thank you for the report!",1406656762,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,*** Bug 68809 has been marked as a duplicate of this bug. ***,1406655142,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar,"This is a little more complicated than that, though. An image could absolutely have both a caption and an alternate text, and a caption can ""act"" like alternate text in case of inline images. 
+
+More to the point, a block image can have both a caption under the image and an alternative text (""title"" popup). An inline image doesn't have a functional caption - but the caption serves as its alternate text unless an alternate text overrides it.
+
+In short, we need to figure out a consistent way of how to handle caption and alt text in images in general. Just disabling the caption in case of alternate text is not really representative of what is allowed under all cases.",1406650739,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-qkdhag2mz377tvfw5d6p,task_subcomment,NA
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","Take this HTML:
+```
+<ul><li>asd
+sdf</li></ul>
+```
+Parse to wikitext:
+```
+* asd
+sdf
+```
+Parse back to HTML:
+```
+<ul><li>asd</li></ul>
+<p>sdf</p>
+```
+I'm not sure what should happen here, but definitely not this.
+
+It's rather easy to run into this in VisualEditor – take a paragraph with newlines and convert it to a list item. I ran into it making this edit: https://en.wikipedia.org/w/index.php?title=Polish_nationality_law&diff=prev&oldid=618961884 (I manually replaced the newlines with spaces before saving).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**: {T55568}",1406638920,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-p57423cc4ujmx5lgadoy,task_description,duplicate
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","I'm a bit confused - what was the actual list item content given in the Description of this task suppose to be -- 2 words or 1 word?
+```
+* asd sdf
+```
+OR
+```
+* asdsdf
+```
+If the desired output was the first one (2 words), then I can get that (no VE) by inserting then previewing the following:
+```
+<ul>
+<li>asd 
+sdf</li>
+</ul>
+```
+",1420995987,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-p57423cc4ujmx5lgadoy,task_subcomment,NA
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","This will need a Parsoid fix since other Parsoid users might still give it HTML that won't be preserved in the html -> wt -> html transformation. 
+
+VE can choose to fix or not independently.",1406802925,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-p57423cc4ujmx5lgadoy,task_subcomment,NA
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","In cases like this, it would probably be reasonable to just convert newlines to spaces at some point (either in VisualEditor or in Parsoid).
+
+Perhaps VisualEditor would be a better place to implement this from the user's perspective, but Parsoid doing what it does now would still be weird :) – maybe we should just fix this in both places?",1406802443,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-p57423cc4ujmx5lgadoy,task_subcomment,NA
+"Parsoid list with newlines roundtrip issue: HTML ""<ul><li>asd\nsdf</li></ul>"" → Wikitext ""* asd\nsdf"" → HTML ""<ul><li>asd</li></ul><p>sdf</p>""","Yes, this is a known issue. Parsoid currently cannot handle arbitrary HTML and convert it to wikitext in a way that preserves rendering on the html -> wt -> html path. But, we've talked about this issue more generally in the past and will address it including fallback mechanisms where some forms of HTML will have to get serialized as HTML tags rather than native wikitext. I thought we had a tracking or related set of bugs for this but, cannot find it right now.
+
+We should identify any other related breakages that arise from within VE (which doesn't necessarily generate arbitrary HTML) and fix them together in Parsoid. This fix would be simpler than support for generic HTML->wt conversion that is preserved in a html2html transformation.",1406802108,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-p57423cc4ujmx5lgadoy,task_subcomment,NA
+"VisualEditor: Opening the link inspector and then closing, while selecting an image moves the image to the previous position","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it thumbnail-left
+4.Now while the image is selected,Open the link inspector tool
+5.Without making any change, just close the link inspector by clicking on Done button
+  
+Observed Result:
+The image gets repositioned as thumbnail-right again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406577840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2kwqewofv75ewmmj7vjy,task_description,resolved
+"VisualEditor: Opening the link inspector and then closing, while selecting an image moves the image to the previous position",Verified the fix in Production,1410545977,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2kwqewofv75ewmmj7vjy,task_subcomment,NA
+"VisualEditor: Opening the link inspector and then closing, while selecting an image moves the image to the previous position",Has been fixed in d635974160ee749a344420ca18b43b401080c346.,1410031260,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2kwqewofv75ewmmj7vjy,task_subcomment,NA
+"VisualEditor: Opening the link inspector and then closing, while selecting an image moves the image to the previous position","This is almost certainly because there's an undo in AnnotationInspector, which expects there to be a corresponding transaction, but there isn't one.",1406747068,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2kwqewofv75ewmmj7vjy,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"Output of the error in commons beta lab
+
+Error: 
+
+Could not read or write file ""mwstore://local-backend/local-public/3/3d/VisualEditor_save_dialog-he.png"" due to insufficient permissions or missing directories/containers.
+
+Could not store file ""/tmp/UgKpr4"" at ""mwstore://local-backend/local-public/3/3d/VisualEditor_save_dialog-he.png"".
+
+I had got similar error while uploading images through API: 
+
+{    
+     ""servedby"": ""deployment-mediawiki02"",     
+     ""error"":
+          {         
+              ""0"": [             ""backend-fail-usable"",             ""mwstore://local-backend/local-public/6/68/VisualEditor_Insert_Menu-he.png""         ],         
+              ""1"": [             ""backend-fail-store"",             ""/tmp/owzHOG"",             ""mwstore://local-backend/local-public/6/68/VisualEditor_Insert_Menu-he.png""         ],         
+              ""code"": ""internal-error"",         
+              ""info"": ""An internal error occurred""     
+          } 
+}
+
+Scenario: 
+
+* I go to one of the image which I had already uploaded in commons[0].
+
+* I click on upload new version of this file at the bottom of the page.
+
+* I add a new image[1] by browsing my file system and I click Upload file.
+
+* Then I get the error reported above or the image in attachment.
+
+-
+[0]: http://commons.wikimedia.beta.wmflabs.org/wiki/File:VisualEditor_save_dialog-en.png
+
+[1]: http://commons.wikimedia.beta.wmflabs.org/w/index.php?title=Special:Upload&wpDestFile=VisualEditor_save_dialog-en.png&wpForReUpload=1
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14238}",1406576520,PHID-USER-b5bosdf7b7zp3vqofbug,False,PHID-TASK-waltxxgf7klwuydmvsrb,task_description,resolved
+Unable to upload new version of images in commons beta lab,"Resolving per:
+
+>>! In T70760#719880, @bd808 wrote:
+> Beta uses the NFS shared directory /data/project/upload7 to store images. 
+> 
+> I just did a permissions check on this directory for sub-directories that are not world writable and found a bunch. This is a likely cause of at least some of the failures.
+
+Swift is: {T64835}",1416949018,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"Beta uses the NFS shared directory /data/project/upload7 to store images. 
+
+I just did a permissions check on this directory for sub-directories that are not world writable and found a bunch. This is a likely cause of at least some of the failures.
+
+To check: 
+
+  $ cd /data/project/upload7
+  $ find . -type d ! -perm -o=w
+    ... lots of dirs output here ...
+
+To fix:
+
+  $ cd /data/project/upload7
+  $ sudo find . -type d ! -perm -o=w -exec chmod 0777 {} +
+
+A hack fix would be to cron this fix somewhere in beta. A better fix would be to kill NFS and use swift for image storage.",1406756728,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,cc'ing ori/bryan in case this was an effect of hhvm permission weirdness.,1406740927,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,Looks like the images which were uploaded before(i.e. before we got the some problems with beta labs recently) have this problem. I tried updating the image which was uploaded yesterday and it works fine.,1406659122,PHID-USER-b5bosdf7b7zp3vqofbug,False,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"(In reply to Chris McMahon from comment #2)
+> Let me know your user names and I can upgrade your privileges on beta labs.
+
+LanguageScreenshotBot",1406658908,PHID-USER-b5bosdf7b7zp3vqofbug,False,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"(In reply to Chris McMahon from comment #2)
+> Let me know your user names and I can upgrade your privileges on beta labs.
+
+""Greg (WMF)""",1406655871,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,Let me know your user names and I can upgrade your privileges on beta labs.,1406655159,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+Unable to upload new version of images in commons beta lab,"Showing my ignorance: Do you have the right permissions? I apparently don't as I see ""You cannot overwrite this file."" on that and other images on the beta cluster commons.",1406655034,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-waltxxgf7klwuydmvsrb,task_subcomment,NA
+VisualEditor: Comment icon is truncated,"Screenshot
+
+See screenshot, from ""Barack Obama"" on enwiki beta. I assume it's meant to be an entire orange circle...
+
+This was seen in Firefox 30.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14125}",1406541780,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-v5onbdu6jehxicnrwhag,task_description,resolved
+VisualEditor: Comment icon is truncated,Fixed and deployed to wmf15 an hour ago. Sorry!,1406594236,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v5onbdu6jehxicnrwhag,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"From User:Encyclopedant:
+
+The Save dialog should have a link to open a new window to a bug report form. This is a good time to start a bug report because you have what you need at hand to write clearly about the bug.
+
+There is no link to report a bug. There is a ""leave feedback"" item under the ? help link in the editor toolbar, but that's kind of hidden, and it doesn't take you to a real bug report form.
+
+There should be a link to open a new window to a bug report form. The link should be explicit that you won't lose what you're doing and that the bug report form will open in a new window.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406497740,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-4qeseygjikdfuaqbrolu,task_description,declined
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,We (now?) have a nice link in the help menu which leaves a comment on the local wiki's VE comments page.,1438370753,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"My second solution, then. Since that template doesn't probably exist elsewhere, my guess is we could copy it onto mediawiki and centralize that kind of feedback there.",1406708658,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,I'd assumed that such a link would be the same as the existing feedback link and go to the on-wiki feedback pages (either local or at mediawiki.org).,1406671682,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"We can't link them to Bugzilla (or Phabricator) without:
+
+* a detailed note about the different privacy policy there,
+* and that their bug reports must be written in English,
+* then the system would need to prompt them to create an account,
+* (which is not part of SUL-authorisation on Bugzilla),
+* then redirect back to opening a bug,
+
+… almost all of which will be written by someone unfamiliar with bug reporting, so they will likely waste a huge amount of time for everyone in re-writing or just closing.
+
+I'm minded to say WONTFIX…",1406668821,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"IMHO, currently that would be https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditor&component=General&format=guided . (That would probably need to point to the system which replaces Bugzilla at some point.)
+At en.wp there's also this link to report bugs through a template right on the feedback page https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&action=edit&section=new&watchthis=1&preload=Template:VE_Bug2/bug_template , but I think the first solution would be more desirable, especially since the future bug report system should be more user-friendly than the current one.",1406667036,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor:  Please mention a way of reporting bugs in the Save dialog,"What is a ""real bug report form""?",1406597486,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4qeseygjikdfuaqbrolu,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,"The version number in the help panel must be bidi-isolated so it won't mess up the date in RTL wikis.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406488800,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-zvn2wduyu4ldd2i4hote,task_description,resolved
+VisualEditor: version number in the help panel must be bidi-isolated,Now it is. :-),1406742261,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,"Change 149656 merged by jenkins-bot:
+Bidi-isolate the version in the help panel
+
+https://gerrit.wikimedia.org/r/149656",1406741972,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,It's not merged yet.,1406714107,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,Thanks!,1406566292,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: version number in the help panel must be bidi-isolated,"Change 149656 had a related patch set uploaded by Amire80:
+Bidi-isolate the version in the help panel
+
+https://gerrit.wikimedia.org/r/149656",1406489027,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zvn2wduyu4ldd2i4hote,task_subcomment,NA
+VisualEditor: Typing over a link doesn't undo correctly,"1. Select a link fully
+2. Type one letter
+3. Press undo
+
+Observer the first letter of the link is no longer linked.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406466900,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-lwcxwsesbmhskncgd577,task_description,resolved
+VisualEditor: Typing over a link doesn't undo correctly,"Change 149633 merged by jenkins-bot:
+Copy annotation indexes before returning
+
+https://gerrit.wikimedia.org/r/149633",1406584633,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lwcxwsesbmhskncgd577,task_subcomment,NA
+VisualEditor: Typing over a link doesn't undo correctly,The cause here is that the removal data in the transaction gets modified by annotationSet.removeAt(). Now the recorded removal data doesn't match the actual data that was there. If you created that link in this session then you also have have a sequence of transactions that don't connect.,1406473513,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-lwcxwsesbmhskncgd577,task_subcomment,NA
+VisualEditor: Typing over a link doesn't undo correctly,"Change 149633 had a related patch set uploaded by Esanders:
+Copy annotation indexes before returning
+
+https://gerrit.wikimedia.org/r/149633",1406473051,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lwcxwsesbmhskncgd577,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"Something wrong with the browsertests role, got after http://paste.debian.net/111811/
+
+Notice: /Stage[main]/Role::Browsertests/File[/srv/browsertests/config]/ensure: created
+Notice: /Stage[main]/Role::Browsertests/File[/srv/browsertests/config/secret.yml]/ensure: defined content as '{md5}b0aa09943ae3b5df22215876b3573a05'
+Error: Working directory '/srv/browsertests/tests/browser' does not exist
+Error: /Stage[main]/Role::Browsertests/Browsertests::Bundle[/srv/browsertests/tests/browser]/Ruby::Bundle[/srv/browsertests/tests/browser]/Exec[bundle_install_/srv/browsertests/tests/browser]/returns: change from notrun to 0 failed: Working directory '/srv/browsertests/tests/browser' does not exist
+
+[...]
+
+Notice: /Stage[main]/Browsertests/Mediawiki::User[Selenium_user]/Exec[mediawiki_user_Selenium_user]/returns: include_once ""$IP/extensions/WikimediaIncubator/WikimediaIncubator.php"";Account exists. Perhaps you want the --force option?
+Error: php5 createAndPromote.php Selenium_user vagrant returned 1 instead of one of [0]
+Error: /Stage[main]/Browsertests/Mediawiki::User[Selenium_user]/Exec[mediawiki_user_Selenium_user]/returns: change from notrun to 0 failed: php5 createAndPromote.php Selenium_user vagrant returned 1 instead of one of [0]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406399160,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-u54ktpl5srhndkfxtln2,task_description,resolved
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"Change 149921 merged by jenkins-bot:
+Removed browsertests role
+
+https://gerrit.wikimedia.org/r/149921",1406574712,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"Change 149921 had a related patch set uploaded by Dduvall:
+Removed browsertests role
+
+https://gerrit.wikimedia.org/r/149921",1406572528,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"Someone asked about removing the role on IRC about a week back. However, it doesn't look like that ever happened.",1406571386,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"The qa/browsertests repository has been emptied of content -- https://github.com/wikimedia/qa-browsertests. I thought there was a bug to remove the browsertests role altogether, but I'm not finding it at the moment.
+
+The ::mediawiki::extension define now supports a `browser_tests => true` setting to setup browser test support for an individual extension. I know the visualeditor role has been updated to use this setting, but there may be other extensions that need to be updated.",1406408257,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others),"At the next puppet run only the first is left:
+
+Notice: /Stage[main]/Apt/Exec[update_package_index]/returns: executed successfully
+Error: Working directory '/srv/browsertests/tests/browser' does not exist
+Error: /Stage[main]/Role::Browsertests/Browsertests::Bundle[/srv/browsertests/tests/browser]/Ruby::Bundle[/srv/browsertests/tests/browser]/Exec[bundle_install_/srv/browsertests/tests/browser]/returns: change from notrun to 0 failed: Working directory '/srv/browsertests/tests/browser' does not exist
+Notice: Finished catalog run in 282.18 seconds",1406401259,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-u54ktpl5srhndkfxtln2,task_subcomment,NA
+VisualEditor: Cursoring off focusable nodes scrolls viewport to the top of the document,"Steps:
+
+1. Open http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+2. Scroll to bottom
+3. Select the gallery
+4. Cursor right
+5. Press a letter.
+
+Expected outcome: Cursor ends up in slug after the gallery, with an 'a' in it; focus stays.
+
+Actual outcome: Focus moves to the top of the document, then restores when 'a' is typed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68708",1406322000,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-77b6hmihb7n4klffjkkg,task_description,resolved
+VisualEditor: Cursoring off focusable nodes scrolls viewport to the top of the document,"Change 151400 merged by jenkins-bot:
+Set selection before focusing document
+
+https://gerrit.wikimedia.org/r/151400",1407065076,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-77b6hmihb7n4klffjkkg,task_subcomment,NA
+VisualEditor: Cursoring off focusable nodes scrolls viewport to the top of the document,"Change 151400 had a related patch set uploaded by Esanders:
+Set selection before focusing document
+
+https://gerrit.wikimedia.org/r/151400",1407061967,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-77b6hmihb7n4klffjkkg,task_subcomment,NA
+VisualEditor: Cursoring off focusable nodes scrolls viewport to the top of the document,"From other reports it sounds like this may be happening for all focusable nodes, not just galleries.",1406576496,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-77b6hmihb7n4klffjkkg,task_subcomment,NA
+VisualEditor Mobile: The link text is not appearing in the link target field inside the link inspector for Android,"Steps to reproduce:
+
+1.Open a page with Mobile VE in Android with Chrome browser
+2.Type a text in CE
+3.Select the text
+4.Open the link inspector
+
+Observed Result:
+The link text is not appearing inside the link inspector in the link target field, it is just empty.
+
+Enviornment:Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406316240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-442235joepfyed6ueex4,task_description,resolved
+VisualEditor Mobile: The link text is not appearing in the link target field inside the link inspector for Android,This issue is not reproducible anymore.,1430341166,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-442235joepfyed6ueex4,task_subcomment,NA
+VisualEditor Mobile: The link text is not appearing in the link target field inside the link inspector for Android,This is issue in not reproducible anymore.,1430341151,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-442235joepfyed6ueex4,task_subcomment,NA
+VisualEditor Mobile: The link text is not appearing in the link target field inside the link inspector for Android,Needs re-testing.,1430336301,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-442235joepfyed6ueex4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,"Steps to reproduce:
+
+1.Open a page with VE which has 4 citations 
+2.Open Cite>Re-use
+3.Select the first reference to re-use
+4.Now again open the use existing reference dialog and observe that the last reference that you added is selected
+5.Try to add it in the article
+
+
+Observed Result:
+
+It does not get added, if you select some other reference and then try to add the previous one , it will work
+
+
+Environment:Betalabs, test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68869",1406311980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bmlzjgktkdmjeslkstm4,task_description,resolved
+VisualEditor: Cannot include the same existing reference after adding it once in an article,Verified the fix in production,1408047020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,Verified the fix in test2,1407191526,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,*** Bug 69027 has been marked as a duplicate of this bug. ***,1406929690,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,"Change 150708 merged by jenkins-bot:
+Unselect currently selected item in re-use citation dialog when reopening
+
+https://gerrit.wikimedia.org/r/150708",1406767242,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,"Change 150708 had a related patch set uploaded by Alex Monk:
+Unselect currently selected item in re-use citation dialog when reopening
+
+https://gerrit.wikimedia.org/r/150708",1406756572,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,Is this just because the reference is selected?,1406755218,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+VisualEditor: Cannot include the same existing reference after adding it once in an article,Sounds like an OptionWidget/SelectWidget thing? Clear the selection when reopening the dialog?,1406746563,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bmlzjgktkdmjeslkstm4,task_subcomment,NA
+The checkboxen in the save dialog wrap poorly if the texts are too long,"VisualEditor: in the saving dialog, the ""Watch this page"" box can move to the next line with very large spacing between the lines. This happens in languages where it's longer than it is in English.
+
+Here's a screenshot of the problem (in Russian):
+
+{F14387}
+
+Possible solutions include:
+* Putting these boxes on separate lines form the start.
+* Making the line spacing smaller. This is a bit problematic, because the text of the second box may appear under the second, and this may be confusing.
+",1406297400,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ohfy6lgpehsflydjpak3,task_description,resolved
+The checkboxen in the save dialog wrap poorly if the texts are too long,"Change 231300 merged by jenkins-bot:
+Convert save checkboxes to OOUI widgets
+
+[[https://gerrit.wikimedia.org/r/231300]]",1439833998,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ohfy6lgpehsflydjpak3,task_subcomment,NA
+The checkboxen in the save dialog wrap poorly if the texts are too long,"After:
+{F1471410}",1439484196,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ohfy6lgpehsflydjpak3,task_subcomment,NA
+The checkboxen in the save dialog wrap poorly if the texts are too long,"Change 231300 had a related patch set uploaded (by Esanders):
+Convert save checkboxes to OOUI widgets
+
+[[https://gerrit.wikimedia.org/r/231300]]
+",1439484177,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ohfy6lgpehsflydjpak3,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,"https://fr.wikipedia.org/w/index.php?title=M%C3%A9thyl%C3%A8nedioxypyroval%C3%A9rone&curid=7265462&diff=105673189&oldid=102426146
+
+If you change anything in the template, nowiki tags will be added into the IUPAC name field. Also happens for the same article in other languages where the name is written in the same way (i.e. English or Spanish).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406216520,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_description,resolved
+VisualEditor: Adding nowiki tags in unrelated edit,I'm unable to reproduce. I suppose this was fixed in the round of `nowiki` work last quarter. Please reopen if seen again.,1430474728,PHID-USER-56wtmb23orq4pu5liyj5,True,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,Investigating…,1430409896,PHID-USER-56wtmb23orq4pu5liyj5,True,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,Nominating as blocker since it's a pretty nasty issue. I'm not sure if it's still happening but we should make sure.,1430238633,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,This is slightly aggressive <nowiki>ing by #Parsoid – looks to still be an issue. Is it a part of a wider task?,1421378405,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Adding nowiki tags in unrelated edit,"Isolated brackets (with no letter nearby) in a template parameter (compulsory) are over-protected by nowiki tags on any change in the template
+
+see : https://test2.wikipedia.org/w/index.php?title=Drong-1&diff=101272&oldid=101271
+
+Safari - MAC OS/X",1408805547,PHID-USER-hhw22zfd2xzrsyc22lp5,True,PHID-TASK-nu5xspbn76mwgtd5gyqq,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Environment-test2
+
+steps-
+
+1> open a page in VE and open language inspector.
+2> Click upon ""English"" in the inspector, to open the Language Selector dialog.
+3> Now click on Language selector icon on top of the page, beside the username link (This extension is used for viewing pages in the language specified by the user's preferences).
+4> Notice dialog saying ""Select a Language"" appears and the Language Inspector gets closed.But the Language Selector dialog(with two-letter code for languages) is still open.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1406156220,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-7od6d3icidxgdzhb3ji2,task_description,resolved
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Hey Ritu, Can you specify the environment where you checked the fix?",1407190922,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,Issue Resolved.,1406920116,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Change 149635 merged by jenkins-bot:
+[BREAKING CHANGE] Fix ve.ui.Overlay classes
+
+https://gerrit.wikimedia.org/r/149635",1406676565,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Change 149635 had a related patch set uploaded by Esanders:
+Make the overlay used by the language dialog global
+
+https://gerrit.wikimedia.org/r/149635",1406475289,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+VisualEditor: Language dialog launched from inspector doesn't open in a global overlay,"Those links at the top shouldn't be accessible when a dialog is open. The problem is that the language dialog is launched in a slightly different way to others because it is launched from an inspector, and isn't getting a 'global' overlay which would shield those links.",1406475083,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7od6d3icidxgdzhb3ji2,task_subcomment,NA
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node","Steps to reproduce:
+
+1.Open a page with VE
+2.Place the cursor after a reference note
+3.Press return
+
+Observed Result:
+
+Uncaught TypeError: Cannot read property 'context' of undefined appears and the cursor jumps to the beginning of the document
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406141820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_description,resolved
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node",Verified the fix in production,1407187962,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_subcomment,NA
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node",Verified the fix in test2,1406327220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_subcomment,NA
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node",Verified the fix in Betalabs,1406159954,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_subcomment,NA
+"VisualEditor: ""TypeError: Cannot read property 'context' of undefined"" on pressing return after a reference node","Fixed by https://gerrit.wikimedia.org/r/#/c/148671/ , needs an oojs release.",1406143164,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jnmodmpu2b6kl3sbrqya,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","I tried editing a page. I pressed Save and received a little ""Something went wrong"" window. I pressed ""Dismiss"". I wanted to try saving again, but the ""Save page"" button was disabled.
+
+It should probably be re-enabled.
+
+VE Version: 234e4e6, on mediawiki.org.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406140800,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-jkzbviyi473qzvp6r5kd,task_description,invalid
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled",I would mark this invalid until we could find out what error it would've been. But maybe we should make it clear in the UI when an error is unrecoverable (and have related patch(es) point to this bug).,1410125346,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","<Krenair> James_F, also, to clarify about badtoken - I was talking about saveErrorNewUser
+<Krenair> for invalid session
+<Krenair> it appears VE gets a new token to check whether the user ID has changed, when a badtoken error is encountered
+<RoanKattouw> Yeah we don't expose a badtoken error to the error handling code unless the API gave us a badtoken error twice
+<RoanKattouw> In which case the server's session storage is probably broken",1409697696,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","Badtoken errors are automatically recovered from, though…",1409692566,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","Hmmmm, don't remember what it could be. Possibly badtoken.",1409685705,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled","ViewPageTarget#showSaveError allows errors to be recoverable or unrecoverable (defaulting to recoverable)
+
+The following errors should be recoverable:
+abusefilter
+badtoken
+
+The following errors are not:
+empty
+spamblacklist
+unknown
+
+Amir, what error did you run into?",1409685574,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+"VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled",I think we only show the error message for unrecoverable errors. Maybe we should prompt the user to give up rather than just exiting to an unusable save dialog?,1409669887,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jkzbviyi473qzvp6r5kd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"screenshot_chrome1
+
+In Chrome 36-
+Scenario#1-
+1> Open a page in VE and select Preformatted from text style menu.
+2> enter some text at the beginning and hit the spacebar till the cursor reaches the end of the line. Further pressing the spacebar takes the cursor out of the </pre> tag. See screenshot_chrome1.
+
+Scenario#2- tried the above steps, but with some characters at the end of the line and then inserting whitespace.See screenshot_chrome2. The cursor still  moves out.
+
+In FF 31-
+Tried the above steps without any characters at the end of the line and just inserting whitespaces. The cursor moves out.
+
+In Safari- No issue found.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14120}",1406137200,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-enbovi37zxerllyc24yd,task_description,resolved
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"I think my recent change 71ceef7dbb6ba95c84987c5c7ffbfecada9257f2 made this saner. Now preformatted text never wraps; if you insert more spaces than fit in the screen, you can still cursor out of the grey-bordered area, but the general behavior is saner (no weird scrolling inside the surface and no weird collapsing of spaces).",1429610947,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"Issue found in test2 too. 
+Steps-
+
+1> Open a page in VE and select Preformatted from text style menu.
+2> enter some text at the beginning and select Language inspector.Don't click any buttons on the inspector.
+3> Now click anywhere inside the preformatted.This closes the inspector dialog. 
+4>Now hit the spacebar till the cursor reaches the end of the line. Further pressing the spacebar takes the cursor out of the </pre> tag. See screenshot_test2.",1406217839,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"Created attachment 16033
+screenshot_test2
+
+**Attached**: {F14122}",1406215441,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,Test Environment:Production,1406139623,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.,"Created attachment 16015
+screenshot_chrome2
+
+**Attached**: {F14121}",1406137289,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-enbovi37zxerllyc24yd,task_subcomment,NA
+VisualEditor: Breadcrumb doesn't reappear upon saving page,"After using VE to edit a subpage in a namespace with subpages enabled, and saving changes, the breadcrumb link (< ParentPageName) underneath the page title does not come back.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406111820,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-xaopuar5atia63pv7slc,task_description,resolved
+VisualEditor: Breadcrumb doesn't reappear upon saving page,"Change 149351 merged by jenkins-bot:
+Don't overwrite #contentSub just to try to get the correct subtitle for redirects
+
+https://gerrit.wikimedia.org/r/149351",1406311507,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xaopuar5atia63pv7slc,task_subcomment,NA
+VisualEditor: Breadcrumb doesn't reappear upon saving page,"Change 149351 had a related patch set uploaded by Alex Monk:
+Don't overwrite #contentSub just to try to get the correct subtitle for redirects
+
+https://gerrit.wikimedia.org/r/149351",1406311070,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xaopuar5atia63pv7slc,task_subcomment,NA
+VisualEditor: Breadcrumb doesn't reappear upon saving page,"<Krenair> So what's currently broken here is how we try to deal with the 'redirect page' text under the title
+<Krenair> We just do $( '#contentSub' ).text( ve.msg( 'redirectpagesub' ) ); which will overwrite the subpage breadcrumb
+<Krenair> Unfortunately, core doesn't wrap that redirect text in a way which we could single it out.
+
+Gerrit change 148883 to fix MW core",1406157282,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-xaopuar5atia63pv7slc,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","**Author:** `misc2006`
+
+**Description:**
+The most obvious way to add a non-breaking space (other than typing it, see T53045) would be the Insert -> Special Characters dialog.
+
+--------------------------
+Alternative: {T53045}",1406106000,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_description,resolved
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888717, @Esanders wrote:
+>>>! In T70429#6888458, @ppelberg wrote:
+>> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+>> 
+>> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+> 
+> It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+Understood. I've filed T278915 as a reminder.
+> 
+>> 
+>> 
+>>>>! In T70429#6875715, @iamjessklein wrote:
+>>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+>> Good question and I'm not aware of us having an answer to it.
+> The letters nbsp are probably understood in all languages because of the html sequence `&nbsp;` used to enter them in wikitext. People are only going to be looking in the special character inserter for this if the already know what it is. If you were just trying to fix a word wrapping issue and didn't know about NBSPs you probably wouldn't be looking for a special character.
+> 
+>>> 
+>>> How common is this affordance? 
+>> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+>> 
+>> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+> 
+> No, the logging only records which group is used.
+Understood.
+
+I am going to resolve this task considering:
+- I do not think anything here requires further action at this time. 
+- The patch that introduced this behavior landed in production via `MW-1.36-notes (1.36.0-wmf.29; 2021-02-02)`
+
+
+
+",1617164550,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+The letters nbsp are probably understood in all languages because of the html sequence `&nbsp;` used to enter them in wikitext. People are only going to be looking in the special character inserter for this if the already know what it is. If you were just trying to fix a word wrapping issue and didn't know about NBSPs you probably wouldn't be looking for a special character.
+
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+",1615019685,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+The letters nbsp are probably understood in all languages because of the html sequence `&nbsp;` used to enter them in wikitext. People are only going to be looking in the special character inserter for this if the already know what it is. If you were just trying to fix a word wrapping issue and didn't know about NBSPs you would probably be looking elsewhere.
+
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+",1615019606,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+",1615019149,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+
+> 
+>> Does it actually need to be more discoverable via the menu? 
+> Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+",1615019084,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6888458, @ppelberg wrote:
+>>>! In T70429#6824562, @Esanders wrote:
+>>> For reference, it can be found here in the menus:
+>> 
+>> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+> @Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+> 
+> //Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most./
+
+It is hard coded. The intention is that it can configured per wiki, but I don't know how often that actually happens.
+
+> 
+> 
+>>>! In T70429#6875715, @iamjessklein wrote:
+>> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+> Good question and I'm not aware of us having an answer to it.
+>> 
+>> How common is this affordance? 
+> If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+> 
+> ...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar.
+
+No, the logging only records which group is used.
+
+> 
+>> Does it actually need to be more discoverable via the menu? 
+> Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+",1615019036,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6824562, @Esanders wrote:
+>> For reference, it can be found here in the menus:
+> 
+> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+@Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+
+//Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – leads me to think the section's contents could be determined by the symbols editors at a particular project use most.//
+
+
+>>! In T70429#6875715, @iamjessklein wrote:
+> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+Good question and I'm not aware of us having an answer to it.
+> 
+> How common is this affordance? 
+If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+
+...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar?
+
+> Does it actually need to be more discoverable via the menu? 
+Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+
+",1614997977,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6824562, @Esanders wrote:
+>> For reference, it can be found here in the menus:
+> 
+> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+@Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+
+//Note: the comment you posted above leads me to wonder whether the list is hard-coded while the name of the section – ""Often used"" – seems like it //could// be dynamic based on which symbols are used most by the editors at a particular project.//
+
+
+>>! In T70429#6875715, @iamjessklein wrote:
+> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+Good question and I'm not aware of us having an answer to it.
+> 
+> How common is this affordance? 
+If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+
+...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar?
+
+> Does it actually need to be more discoverable via the menu? 
+Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+
+",1614997924,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6824562, @Esanders wrote:
+>> For reference, it can be found here in the menus:
+> 
+> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+@Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+
+//Note: the comment you posted above leads me to wonder whether the list is hard-coded while the naming of the section – ""Often used"" – seems like it //could// be dynamic based on which symbols are used most by the editors at a particular project.//
+
+
+>>! In T70429#6875715, @iamjessklein wrote:
+> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+Good question and I'm not aware of us having an answer to it.
+> 
+> How common is this affordance? 
+If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+
+...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar?
+
+> Does it actually need to be more discoverable via the menu? 
+Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+
+",1614997913,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",">>! In T70429#6824562, @Esanders wrote:
+>> For reference, it can be found here in the menus:
+> 
+> The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).
+@Esanders: what currently determines the symbols that appear within the ""Often used"" section? 
+
+//Note: the comment you posted above leads me to wonder whether the list is hard-coded and the naming of the section – ""Often used"" – seems like it //could// be dynamic based on which symbols are used most by the editors at a particular project.//
+
+
+>>! In T70429#6875715, @iamjessklein wrote:
+> Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+Good question and I'm not aware of us having an answer to it.
+> 
+> How common is this affordance? 
+If it would be accurate for me to understand the above as asking how often people use the `NBSP` affordance in VE, then we //should// be able to answer this question thanks to T264146.
+
+...@matmarex: can you please confirm whether or not we would be able to leverage the instrumentation that was implemented in T264146 to determine how often people use the `NBSP` affordance within the special characters toolbar?
+
+> Does it actually need to be more discoverable via the menu? 
+Perhaps? Tho, I think we can wait on prioritizing making that work assuming people will be more likely to find the `NBSP`functionality via an explicit affordance vs. a keyboard shortcut as people would have to have done previously. 
+
+
+",1614997869,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Is nbsp understood across wikis? If not then do we need a visual representation via an icon?
+
+How common is this affordance? Does it actually need to be more discoverable via the menu? (I would really prefer if we had a search menu under the omega menu but that would be a much larger task).
+
+",1614708836,PHID-USER-ujgufealwngqoe65jj3h,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","> For reference, it can be found here in the menus:
+
+The position within the list could be changed for increased prominence (there is also an ""Often used"" section at the top that it could go in).",1613075426,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","For reference, it can be found here in the menus: 
+| Visual editor | Wikitext editor
+| -- | --
+| {F34100802} | {F34100807}
+
+This is admittedly very hidden. We have a follow-up task to add a keyboard shortcut for it: T53045.
+
+>>! In T70429#6795734, @Bdijkstra wrote:
+> [[ https://meta.wikimedia.org/wiki/Tech/News/2021/05 | Tech/News/2021/05]] suggests that this feature can currently be used. If so, how exactly can users of the 2010, 2017, and visual editors insert this character? I've tried various wikis (even test.wikipedia) and couldn't find it.
+
+It's not available on the production Wikimedia wikis yet due to a delay of the deployment train, but you can test it on <https://en.wikipedia.beta.wmflabs.org/>.
+",1613074423,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Test wiki on [[ https://patchdemo.wmflabs.org | Patch Demo ]]  by PPelberg (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/9ccca56b0e5403e33b61e9e8711b5c8c/w/ ]]~~",1612384898,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch Demo ]] by PPelberg (WMF) using patch(es) linked to this task:
+
+https://patchdemo.wmflabs.org/wikis/9ccca56b0e5403e33b61e9e8711b5c8c/w/",1612370821,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","@Bdijkstra It's in this week's train, so it'll start working today, tomorrow or on Thursday, depending on which wiki.",1612267423,PHID-USER-go2ym6ta2zn6ofdsrqnx,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","[[ https://meta.wikimedia.org/wiki/Tech/News/2021/05 | Tech/News/2021/05]] suggests that this feature can currently be used. If so, how exactly can users of the 2010, 2017, and visual editors insert this character? I've tried various wikis (even test.wikipedia) and couldn't find it.",1612268410,PHID-USER-xoa3aehuzhwg7enutrrl,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","[[ https://meta.wikimedia.org/wiki/Tech/News/2021/05 | Tech/News/2021/05]] that this feature can currently be used. If so, how exactly can users of the 2010, 2017, and visual editors insert this character? I've tried various wikis (even test.wikipedia) and couldn't find it.",1612264967,PHID-USER-xoa3aehuzhwg7enutrrl,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659378 **merged** by jenkins-bot:
+[mediawiki/core@master] Add &nbsp; to the special character list
+
+https://gerrit.wikimedia.org/r/659378",1611944794,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659376 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Implement mwPlatform#decodeEntities
+
+https://gerrit.wikimedia.org/r/659376",1611867462,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659408 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (fe9082b21)
+
+https://gerrit.wikimedia.org/r/659408",1611867086,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659408 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (fe9082b21)
+
+https://gerrit.wikimedia.org/r/659408",1611863850,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659374 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Allow HTML entities in the special character list
+
+https://gerrit.wikimedia.org/r/659374",1611863437,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Test wiki created on [[ http://patchdemo.wmflabs.org | Patch Demo ]] by ESanders (WMF) using patch(es) linked to this task:
+
+http://patchdemo.wmflabs.org/wikis/8593b7f469ef5349d6a47359e1d3b977/w/",1611861591,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659378 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/core@master] Add &nbsp; to the special character list
+
+https://gerrit.wikimedia.org/r/659378",1611860194,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659376 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Implement mwPlatform#decodeEntities
+
+https://gerrit.wikimedia.org/r/659376",1611860046,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Change 659374 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] Allow HTML entities in the special character list
+
+https://gerrit.wikimedia.org/r/659374",1611860043,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Given that https://phabricator.wikimedia.org/T53045#1947804 happened, I guess that the special character option is still more difficult to implement than the other one, even if just as a temporary workaround?",1457711072,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","Due to various implementation details this is more difficult than it looks (it's not just a matter of adding an entry to the list of available characters). If we implement {T53045}, I'm not sure if this one will be worth it.",1448821098,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","We already have the ability to use different label on the button than the character that will be inserted (we use it for more meaningful labels for combining characters, and in fact for invisible ones like zero-width non-joiner and joiner). We should probably make the label say ""NBSP"" if we do this.",1429721750,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",Or you could somehow annotate the whole word as nowrap. Arguably <nowrap>100 °C</nowrap> would be clearer than 100&nbsp;°C,1429613379,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog","A hopefully clearer rationale for this request, from User:Gnom:
+
+//Our typography rules call for a non-breaking space when discussing units and abbreviations (""a marathon is run over a distance of 42.195 km"" calls for `42.195&nbsp;km` ; ""water boils at 100 °C"" requires `100&nbsp;°C` ; ""Mary Shelley created the character of Dr. Frankenstein"" includes `Dr.&nbsp;Frankenstein` ). I frequently use it in every law-related article in relation to the ""§"" sign, an example for this would be the article on Mietvertrag (Deutschland). //
+
+(Notice the several occurrences of the NBSP in https://de.wikipedia.org/wiki/Mietvertrag_(Deutschland).)",1426530087,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+"VisualEditor: Add non-breaking space (nbsp) to the ""special character"" dialog",Adding 68425 or users will have no idea what it is.,1406598979,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xtaz4xuglw6bqqvscwvu,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"**Author:** `misc2006`
+
+**Description:**
+There are at least two dash-like characters in the ""Special character"" dialog. They should have a tooltip describing them, otherwise it won't be obvious to most users which character is to be used in which situation. Actually, why not add a descriptive tooltip to all special characters?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406103960,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_description,resolved
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"Change 205558 merged by jenkins-bot:
+Allow special characters with tooltip or that encapsulate text
+
+[[https://gerrit.wikimedia.org/r/205558]]",1429750555,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"Change 205557 merged by jenkins-bot:
+ve.ui.SpecialCharacterPage: Allow providing a tooltip for characters
+
+[[https://gerrit.wikimedia.org/r/205557]]",1429744994,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"Change 205558 had a related patch set uploaded (by Bartosz Dziewoński):
+Allow special characters with tooltip or that encapsulate text
+
+[[https://gerrit.wikimedia.org/r/205558]]
+",1429608439,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"Change 205557 had a related patch set uploaded (by Bartosz Dziewoński):
+ve.ui.SpecialCharacterPage: Allow providing a tooltip for characters
+
+[[https://gerrit.wikimedia.org/r/205557]]
+",1429608421,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"For VisualEditor-MediaWiki, we're now reusing the special characters list from the wikitext WikiEditor. It has over 2000 entries and I am positive there is no point in providing and translating a tooltip for every single one of them.
+
+However, there are at least a few which could use a tooltip. That list has them for three similar-looking characters: − (minus sign), – (en dash) and — (em dash). We currently ignore these in VisualEditor, I'm fixing it.
+
+{F131436}
+
+For VisualEditor standalone, it would be reasonable to add labels for these three, too, but it's probably not be necessary, since we display the list in a clearer form (proportional fonts and shorter sections). I won't be doing this for now, someone else can decide.
+
+{F131440}",1429607706,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"**misc2006** wrote:
+
+(In reply to Andre Klapper from comment #1)
+
+> Assuming you refer to − and — : Don't use and situations highly depend on
+> cultures (and languages) anyway?
+
+I guess so (and that's probably why de.wikipedia has a different dialog than en.wikipedia), but still these characters have names that at least help explain their meaning and make it possible to tell them apart.
+
+> Any citation for ""won't be obvious to most users""?
+
+I've fixed about 2000 typos in de.wikipedia in the last few months and typographical problems (although not limited to the dash characters) are very common.
+
+> I doubt there is a usecase for explaining every single character (and making
+> translators translate them). Which actual problem to solve?
+
+It increases confidence in what you're doing if you can see that you are actually using the right character (instead of one that maybe just looks the same - this could easily happen with then tens of thousands of unicode characters available). For translation, either use the Unicode name without translation, or an official translation (that might be available or not).",1406109963,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other,"(In reply to Daniel Naber from comment #0)
+> There are at least two dash-like characters in the ""Special character""
+> dialog. They should have a tooltip describing them, otherwise it won't be
+> obvious to most users which character is to be used in which situation.
+
+Assuming you refer to − and — : Don't use and situations highly depend on cultures (and languages) anyway? Wondering if it would be possible to generally explain at all.  Any citation for ""won't be obvious to most users""?
+
+(In reply to Daniel Naber from comment #0)
+> Actually, why not add a descriptive tooltip to all special characters?
+
+I doubt there is a usecase for explaining every single character (and making translators translate them). Which actual problem to solve?",1406108435,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6hnqd5mtozjfcpv3i3hp,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"no Message for error
+
+""Not logged in"" message has no Message text, shows placeholder id, see screen shot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14425}",1405964460,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-4itcjtumhnjkxw77si2v,task_description,resolved
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148573 merged by jenkins-bot:
+Update messages list for oojs-ui
+
+https://gerrit.wikimedia.org/r/148573",1406128714,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148550 merged by jenkins-bot:
+Update messages list for oojs-ui
+
+https://gerrit.wikimedia.org/r/148550",1406078176,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148573 had a related patch set uploaded by Jforrester:
+Update messages list for oojs-ui
+
+https://gerrit.wikimedia.org/r/148573",1406077975,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148120 abandoned by Catrope:
+Declare dependency on ooui-dialog-* messages as they're needed
+
+Reason:
+Done in MW core in https://gerrit.wikimedia.org/r/148550
+
+https://gerrit.wikimedia.org/r/148120",1406073076,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148550 had a related patch set uploaded by Catrope:
+Update messages list for oojs-ui
+
+https://gerrit.wikimedia.org/r/148550",1406073057,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported,"Change 148120 had a related patch set uploaded by Jforrester:
+Declare dependency on ooui-dialog-* messages as they're needed
+
+https://gerrit.wikimedia.org/r/148120",1405965762,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4itcjtumhnjkxw77si2v,task_subcomment,NA
+VisualEditor: Pasting more than one paragraph is painfully slow in large documents,"Pasting more than one paragraph triggers a full document re-render. This is clearly seen in the standalone client where all the paragraphs flash grey on re-render.
+
+On en:Cat in Firefox it takes ~2s.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1405887180,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-st45mendifimrc7daviy,task_description,resolved
+VisualEditor: Pasting more than one paragraph is painfully slow in large documents,"Change 147987 merged by jenkins-bot:
+Fix calculation of affectedRange in transaction processor
+
+https://gerrit.wikimedia.org/r/147987",1406081163,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-st45mendifimrc7daviy,task_subcomment,NA
+VisualEditor: Pasting more than one paragraph is painfully slow in large documents,"Change 147987 had a related patch set uploaded by Esanders:
+Fix marking of affected range in transaction processor
+
+https://gerrit.wikimedia.org/r/147987",1405887249,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-st45mendifimrc7daviy,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","(This bug notes issues with both Parsoid and VisualEditor. I think all of this is caused by the terrible mistake that is bug 529 / bug 12974. I'll leave it for you to figure out this mess. :) )
+
+----
+
+On mediawiki.org, there is a family on fancy templates like [[mw:Template:MW 1.23]] that generate a right-floated MediaWiki version number in a frame.
+
+These templates generate a wikitext table (starting with '{|'), which means that due to bug 529 / bug 12974 a newline is prepended before it. This behavior is incredibly annoying in practice, but it seems that we're very much wedded to it because it made Parsoid people's lives easier.
+
+----
+
+However, Parsoid rendering of this particular template is inconsistent with PHP. On [[mw:Manual:Skinning#Localisation_messages]], PHP generates an empty paragraph before the table, while Parsoid doesn't and produces an about-grouped pair of <span>\n</span><table>…</table> (the span tag only contains the prepended newline).
+
+This rendering, that looks good in Parsoid/VisualEditor, therefore looks like crap in PHP parser.
+
+Note that the <span> is not nested in a <p> or any other block-level element, it just sits there right in the <body>. (It is not visible since, as I mentioned, it just contains some whitespace.)
+
+----
+
+More problems appear when you try to edit text with this template in VisualEditor.
+
+For example, testing on [[mw:Manual:Skinning#Localisation_messages]]:
+
+* Place cursor before/after one of the templates.
+* Press 'Right'/'Left' keyboard key twice.
+** First press selects the template, as expected.
+** Second press scrolls the page all the way up.
+
+* Try inserting the ""MW 1.23"" template on an empty line.
+** Observe that the blue highlights are different than for the
+   templates already present on the page – there is both the table, as
+   well as a single ""space"" (?) in text flow. Observe that the context
+   menu is placed weirdly in the middle of the page.
+** Place cursor after the ""space"" and try typing. Weird things happen,
+   sometimes I get an exception ""Uncaught Error: Unbalanced set of
+   replace operations found"", sometimes my input is duplicated or I
+   get snowmen and pawns.
+** Try deleting the template in any way. It is deleted, but the page
+   is scrolled all the way up.
+
+* Edit the two paragraphs right after the ""Localisation messages""
+  heading (add a letter somewhere in the middle or something).
+* Try saving the page.
+** Observe that multiple newline-related changes appear to have been
+   made. Strangely, there are actually no changes, but the *before*
+   half of the comparison has some newlines removed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405871700,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dobhhdqzp556tigyqgiz,task_description,resolved
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]",All VE items appear fixed as of a while ago. Marking as such.,1412889795,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","Let's turn this into a mini tracking bug, then? I split off the Parsoid issue to bug 68862, together with VE bug 68733, bug 68708 and bug 58038 this seems to describe all of the problems.",1406735205,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","The pawn, snowman and offset exception bugs should be fixed by https://gerrit.wikimedia.org/r/149920 .
+
+The scrolling all the way up is bug 68589.
+
+The rendering weirdness due to the span-wrapped newline is probably unique to this bug.",1406576539,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","(In reply to Bartosz Dziewoński from comment #0)
+> * Place cursor before/after one of the templates.
+> * Press 'Right'/'Left' keyboard key twice.
+> ** First press selects the template, as expected.
+> ** Second press scrolls the page all the way up.
+
+So if you select a node that's floating right and is half way down the page, then press left or right, you scroll all the way to the top of the page (though the cursor is positioned correctly).
+
+> ** Place cursor after the ""space"" and try typing. Weird things happen,
+>    sometimes I get an exception ""Uncaught Error: Unbalanced set of
+>    replace operations found"", sometimes my input is duplicated or I
+>    get snowmen and pawns.
+
+Yeah, I get that error and other weirdness (e.g. the cursor moving around - to before/after the template I think?) when typing normally, then snowmen+pawns when I try to undo/redo things. I've also been getting some extra errors: Uncaught Error: Unbalanced input passed to document 
+At one point I got this error as well: Uncaught Error: Offset could not be translated to a DOM element and offset: 77",1406333869,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+"VisualEditor: Investigate parsing/rendering/behavior of ""{{MW 1.23}}"" on mediawiki.org [mini-tracking]","This is causing breakage in edits (that is not being detected by VE):
+https://www.mediawiki.org/w/index.php?title=Manual:Skinning&diff=1074312&oldid=1072136",1406115379,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dobhhdqzp556tigyqgiz,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"**Author:** `gabrasca2`
+
+**Description:**
+The text show/hide in the right of the navbox disappear after have edited a page where there is a navbox collapsed and the navbox appears uncollapsed, until the page is refreshed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1405797900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7zaj564v4tdljuzqups,task_description,declined
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,Please reopen if you can still reproduce this issue.,1415210380,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"(Quoting Alex Monk from comment #6)
+> Gabrasca, could you link to the page showing this issue?",1412626900,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"**gabrasca2** wrote:
+
+the issue appens only after it is saved from VE, if I reload the page the show/hide text returns.",1412408663,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"Gabrasca, please respond.",1412378459,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"Gabrasca, could you link to the page showing this issue?",1410125451,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"**gabrasca2** wrote:
+
+I tried on itwiki, in a personal sandbox with a navbox (example discography of a band).(In reply to Alex Monk from comment #4)
+> Hm.. Doesn't seem to happen with MW's built-in collapsible functionality.
+> And obviously enwiki's navbox (and related JS gadgets) is not a MediaWiki
+> feature, so this bug is probably invalid.",1406739658,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"Hm.. Doesn't seem to happen with MW's built-in collapsible functionality. And obviously enwiki's navbox (and related JS gadgets) is not a MediaWiki feature, so this bug is probably invalid.",1406734406,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"**gabrasca2** wrote:
+
+Edit a page with VisualEditor, add a template written with navbox, save, the template added is uncollapsed and in the right corner of the template there is not the text show/hide.",1406716452,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,Gabrasca: Could you clarify what you mean please? Some of the language in this bug is unclear. It sounds as if some of this might be valid for MW core's collapsible elements.,1406681224,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+VisualEditor: The show/hide text a collapsed navbox disappear afted have edited,"There's a hook or something to call to get these to re-activate; it's already used in VPT for sortable tables or another common gadget, I believe.",1406602361,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k7zaj564v4tdljuzqups,task_subcomment,NA
+"VisualEditor Mobile: In android, while trying to apply a link on a selected text, strips off the first letter of the text in the link inspector","Steps to reproduce:
+
+1.Open a page with Mobile Ve in android with Chrome browser
+2.Select a text such as ""Text""
+3.Click on link inspector tool
+
+Observed Result:
+Observe that in the link inspector, the ""text"" is appearing as ""ext""",1405725780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rltauqohawt55lchrl4d,task_description,open
+"VisualEditor Mobile: In android, while trying to apply a link on a selected text, strips off the first letter of the text in the link inspector","This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592583998,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rltauqohawt55lchrl4d,task_subcomment,NA
+"VisualEditor Mobile: In android, while trying to apply a link on a selected text, strips off the first letter of the text in the link inspector","The previous comments don't explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status.
+
+//(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}. If this task is stalled on an upstream project, then the #upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task needs retesting, then the #testme tag should be added. If this task is either out of scope and nobody should ever work on this, or nobody else managed to reproduce the problem described in this task, then this task should have the ""Declined"" status.)//",1590761756,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rltauqohawt55lchrl4d,task_subcomment,NA
+"VisualEditor Mobile: In android, while trying to apply a link on a selected text, strips off the first letter of the text in the link inspector",Needs re-testing.,1430336424,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rltauqohawt55lchrl4d,task_subcomment,NA
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to the Advanced Settings and change the image size
+4.Click on Apply changes
+5.Reopen the Advanced Settings panel for that image again
+
+
+Observed Result:
+Observe that, the size values of the image are still showing the previous ones , though the image actually got resized
+If I save the page and reopen it and then check the Advanced Settings dialog , I see the updated values then.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405722900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_description,resolved
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page",Verified the fix in production,1407189132,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_subcomment,NA
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page",Verified the fix in test2,1406322997,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_subcomment,NA
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page","Change 147219 merged by jenkins-bot:
+Make the image model work without a node
+
+https://gerrit.wikimedia.org/r/147219",1406161979,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_subcomment,NA
+"VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page","Change 147219 had a related patch set uploaded by Mooeypoo:
+Make the image model work without a node
+
+https://gerrit.wikimedia.org/r/147219",1405978515,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n4wu3wvhi3ff7lpioygq,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Go to Cite>Basic
+3.Click on ""Use an existing reference"" button
+4.Now resize down the window 
+
+Observed Result:
+The ""Use Existing Reference"" dialog suddenly gets squished in and if I drag the window to its original size it stays like that.
+Now if you click on ""Go Back"" button the basic reference dialog also appears that way
+
+See the screenshot attached
+
+Browser: Chrome and Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14226}",1405712280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_description,resolved
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,Verified the fix in production,1407188186,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,Verified the fix in test2,1406327085,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,Verified the fix in Betalabs,1406160162,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,Fixed now. :-),1406081224,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Change 148577 merged by jenkins-bot:
+Clamp height of MWReferenceDialog to between 300 and 400px to avoid it being too small
+
+https://gerrit.wikimedia.org/r/148577",1406080948,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Change 148577 had a related patch set uploaded by Jforrester:
+Clamp height of MWReferenceDialog to between 300 and 400px to avoid it being too small
+
+https://gerrit.wikimedia.org/r/148577",1406080696,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Created attachment 16010
+Screenshot
+
+**Attached**: {F14227}",1406072881,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Still happening but in a slightly different way.Also,there are now two ways of opening use existing reference dialog , but the initial size of the dialog upon opening is not same for both cases.
+
+See the screenshot attached",1406072745,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Change 147710 merged by jenkins-bot:
+Fix heights of Reference, ReferenceList and Template dialogs
+
+https://gerrit.wikimedia.org/r/147710",1406045501,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal,"Change 147710 had a related patch set uploaded by Jforrester:
+Fix heights of Reference, ReferenceList and Template dialogs
+
+https://gerrit.wikimedia.org/r/147710",1405736124,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u5svmf673m5i5zmpc5ng,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Screenshot
+
+The references list dialog is appearing a bit smaller in Firefox which also makes the text field for group name overlap with the border of the dialog.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70601
+
+**Attached**: {F14204}",1405709100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dqhaia75vamsl3rmnltp,task_description,resolved
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,Verified the fix in production,1407189700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,Verified the fix in production,1407189694,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,Verified the fix in test2,1406321895,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Change 148903 merged by jenkins-bot:
+Bump the height of the references list a little
+
+https://gerrit.wikimedia.org/r/148903",1406162585,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Change 148903 had a related patch set uploaded by Jforrester:
+Bump the height of the references list a little
+
+https://gerrit.wikimedia.org/r/148903",1406161479,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Created attachment 16027
+Screenshot
+
+This is still looking like this
+
+**Attached**: {F14205}",1406159502,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Change 147710 merged by jenkins-bot:
+Fix heights of Reference, ReferenceList and Template dialogs
+
+https://gerrit.wikimedia.org/r/147710",1406045504,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog,"Change 147710 had a related patch set uploaded by Jforrester:
+Fix heights of Reference, ReferenceList and Template dialogs
+
+https://gerrit.wikimedia.org/r/147710",1405736119,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dqhaia75vamsl3rmnltp,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","Steps to reproduce:
+
+
+1.Open a page with mobile VE
+2.Select the option ""USe existing reference"" from Cite menu options
+3.Click on the ""Go Back"" button on use existing reference
+4.It takes you to the basic reference dialog
+
+
+Issue 1: Type something in the dialog pawn appears
+Issue 2: Click on ""Insert Reference"" nothing happens
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405638780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-caaaahazbcu7qa5ilv5p,task_description,resolved
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog",Verified the fix in production,1407186733,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog",Verified the fix in test2,1406327428,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","This issue got resolved with replacing ""Go Back"" button with ""Cancel"" button in Use Existing Reference dialog",1406072380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","Change 144058 merged by jenkins-bot:
+Put ""re-use reference"" in the toolbar ""Cite"" menu, and give it an icon
+
+https://gerrit.wikimedia.org/r/144058",1406064636,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","Change 144058 had a related patch set uploaded by Jforrester:
+Put ""re-use reference"" in the toolbar ""Cite"" menu, and give it an icon
+
+https://gerrit.wikimedia.org/r/144058",1406055177,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+"VisualEditor Mobile: The ""Go back"" button in use existing reference dialog in mobile takes to Basic Reference dialog","Created attachment 15969
+Screenshot
+
+Issue 3: It also lets you add a template and get stuck there.
+
+**Attached**: {F14153}",1405639094,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-caaaahazbcu7qa5ilv5p,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf15] The highlights of the nodes are appearing over the toolbar menu,"Screenshot
+
+Steps to reproduce:
+
+1.Select any node such as reference in mobile VE using iOS or desktop safari
+
+2.Now open the cite menu option from the toolbar
+
+Observed Result:
+Observe that, the highlight of the reference node is appearing over the cite menu option.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14137}",1405637040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e6jsiulpiw5hjbfetpvc,task_description,resolved
+VisualEditor Mobile: [Regression pre-wmf15] The highlights of the nodes are appearing over the toolbar menu,Verified the fix in production,1408046907,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e6jsiulpiw5hjbfetpvc,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf15] The highlights of the nodes are appearing over the toolbar menu,Verified the fix in test2,1407265155,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e6jsiulpiw5hjbfetpvc,task_subcomment,NA
+VisualEditor Mobile: [Regression pre-wmf15] The highlights of the nodes are appearing over the toolbar menu,To check…,1406747398,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e6jsiulpiw5hjbfetpvc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Place the cursor in the CE
+3.Open Link inspector and insert a link
+4.Click on the link inspector icon again.
+
+Observed Result:
+The inspector appears a bit zoomed , which makes the title ""Link"" and the button ""Done"" on the top overlapped with the browser tabs
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14134}",1405635840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x2p7hqn3esqtuse7scxc,task_description,resolved
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab",Verified the fix in production,1408048262,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab",Verified the fix in test2,1407197493,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab","Cannot reproduce it anymore, might got fixed with windows refactor.",1406751119,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab","Created attachment 15966
+cursor position
+
+**Attached**: {F14136}",1405636258,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+"VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab","Created attachment 15965
+link suggestions
+
+Also see the other screenshots on how the cursor and the link suggestions appear when user tries to enter a link target when it appears like that.
+
+**Attached**: {F14135}",1405636232,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-x2p7hqn3esqtuse7scxc,task_subcomment,NA
+VisualEditor Mobile: The Remove button for the link inspector in mobile is not styled as Red,"Screenshot
+
+See the screenshot attached
+The ""Remove"" button in the link inspector is not styled as Red
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14123}",1405634400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3q2oh7zhspz3z3iusr7s,task_description,resolved
+VisualEditor Mobile: The Remove button for the link inspector in mobile is not styled as Red,Verified the fix in production,1408046946,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3q2oh7zhspz3z3iusr7s,task_subcomment,NA
+VisualEditor Mobile: The Remove button for the link inspector in mobile is not styled as Red,Verified the fix in test2,1407197522,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3q2oh7zhspz3z3iusr7s,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"I've set up a new labs project for ExtensionDistributor to serve tarballs instead of using github. Example tarball: http://extdist.wmflabs.org/?version=REL1_23&ext=VisualEditor
+
+This will provide better privacy for users, and also fix a few bugs like submodule support (bug 44022).
+
+Yuvi is helping puppetize the setup.
+
+I want to temporarily enable ExtensionDistributor on testwiki, point it labs, make sure there are no issues, and then turn it on on mediawiki.org.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405545060,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-nu7ycsxlgziqvsqjceef,task_description,resolved
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,Should we track download counts for the tarballs? :),1406831216,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"Deployed, nothing looks broken! :D",1406830792,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"This will go live tomorrow, when 1.24wmf16 hits mediawiki.org",1406756544,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"Change 150589 merged by jenkins-bot:
+Switch ExtensionDistributor to serve tarballs from extdist.wmflabs.org
+
+https://gerrit.wikimedia.org/r/150589",1406742934,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"Change 150589 had a related patch set uploaded by Legoktm:
+Switch ExtensionDistributor to serve tarballs from extdist.wmflabs.org
+
+https://gerrit.wikimedia.org/r/150589",1406741479,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+Use new labs project (extdist.wmflabs.org) for ExtensionDistributor,"New plan after talking with Chad: have ExtensionDistributor get a list of branches from Gerrit's API (I5c4ca2ee13f256260a7fe9b703af5fbdb902db66), and just assume that the tarballs exist on extdist.wmflabs.org. This way prod will never have to talk to labs.
+
+> Yuvi is helping puppetize the setup.
+
+I63d285612bd30d24b83718c4c8967144d146afeb 
+
+> I want to temporarily enable ExtensionDistributor on testwiki, point it
+> labs, make sure there are no issues, and then turn it on on mediawiki.org.
+
+My half-re-write of the extension makes it so this really isn't possible :/",1406360119,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-nu7ycsxlgziqvsqjceef,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Edit the page
+3.Now click on the ""Edit Source"" tab
+4.Click on the option ""Discard Changes""
+
+Observed Result:
+It redirects to the edit source mode of the main page .
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14497}",1405544880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekrm36buebgsetzut4ox,task_description,resolved
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",Verified the fix in production en.wiki,1406314095,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap is a useful reference for Wikimedia deployments,1405964514,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","(In reply to Alex Monk from comment #7)
+> Are you sure that wiki is running a version of VisualEditor with the fix for
+> this bug? I'm pretty sure Wikipedia is supposed to get this change is on
+> Thursday...
+
+I see. I thought it was already deployed to all wikis. Sorry.",1405964265,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",Are you sure that wiki is running a version of VisualEditor with the fix for this bug? I'm pretty sure Wikipedia is supposed to get this change is on Thursday...,1405964025,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","It still redirects to the main page, if you choose some version from the history page and then do the same.
+
+1) https://en.wikipedia.org/w/index.php?title=Test&oldid=614834396
+2) click edit
+3) (make some changes to the page)
+4) switch to source editing
+5) discard changes
+and you're again editing the main page",1405963079,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",Verified the fix in test2,1405720820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","Change 146956 merged by jenkins-bot:
+Set title of page to use if discarding changes when changing to the wikitext editor
+
+https://gerrit.wikimedia.org/r/146956",1405555740,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page","Change 146956 had a related patch set uploaded by Alex Monk:
+Set title of page to use if discarding changes when changing to the wikitext editor
+
+https://gerrit.wikimedia.org/r/146956",1405549014,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",This is a fun one. Are we passing '' to the API instead of the page name?,1405546990,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+"VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting ""Discard Changes"" redirects to the Edit source mode of the main page",It happens also if I switch to Edit Source mode from the Switch to Source Editing option.,1405545105,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekrm36buebgsetzut4ox,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"Script error for each citation
+
+Test Environment-test2
+Steps to Reproduce-
+
+Scenario#1-
+1> Select the ” Cite “ drop down and add a Journal, News, Book,  one of each citations.
+2> Now click on “Insert” and select “Media”. Click on any picture returned in the dialog(do not enter any search term)
+3> In the Media Settings dialog click on “Insert” again and select “Media” from the Caption toolbar. Click on any picture returned in the dialog.
+4> Now close all the dialogs. 
+5> Repeat again steps #2,3 and 4.
+6>In the main VE window  click on “Cite”  and select “Basic”. Reference dialog opens.
+5> In the Reference dialog select “Use an existing reference”.
+6> Script Error is shown as existing reference.
+
+Scenario#2-
+1> Go to the Media Settings dialog. 
+2> While General Settings is highlighted, select the ” Cite “ drop down and add a Journal, News, Book,  one of each citations to the Caption pane.
+3> Now click on “Insert “dropdown and select “Media”.
+4>Click on any picture in the media search dialog. Media Settings dialog pops. Close this dialog.
+5> Repeat steps 3 and 4 again.
+5> Notice that the previously opened Media Settings dialog is still open with the citations in the Caption pane.
+6> Click on “Cite” again and select “Basic”. Reference dialog opens.
+7> In the Reference dialog select “Use an existing reference”.
+8> Script Error is shown as existing reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14429}",1405466460,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-czceip6xh6hv5epzval5,task_description,resolved
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"okay, so there is no need to have a new bug on it I guess.",1407350346,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,Probably an effect of whatever caused this?,1407323763,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"The delay to load citations in RE-Use dialog is pretty noticeable now.Previously,it was not like that.Is it an effect of this fix?",1407263283,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,Issue Resolved in test2.,1406922194,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"This looks like it's now fixed.
+
+(Note that the ""re-use"" list can take a few seconds to update, so if you've just created a cite it may render as ""[4]"" rather than ""[4] Foo. Bar (Baz)"" which will happen later if you wait.
+
+Thanks, Krenair!",1406770961,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"(In reply to Rummana Yasmeen from comment #2)
+> However there is one issue here, when you first time add any reference, and
+> open use existing reference dialog, the reference name will not appear but
+> after that if you do any other action like adding a media, or a link or a
+> reflist it appears.
+
+That sounds like bug 67342. Is this valid?",1406769368,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"This bugs is found in test2 so the reason why it is showing script error for the Cite News,Cite Journal,Cite Book but not Cite Web, the template data for those options are not defined in test2.
+So if you just add those Cite Options and add a reflist , you will also see script errors in the reference list.
+
+
+However there is one issue here, when you first time add any reference, and open use existing reference dialog, the reference name will not appear but after that if you do any other action like adding a media, or a link or a reflist it appears.",1405538788,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work,"(In reply to Ritu Swain from comment #0)
+> Created attachment 15949 [details]
+> Script error for each citation
+> 
+> Test Environment-test2
+> Steps to Reproduce-
+> 
+> Scenario#1-
+> 1> Select the ” Cite “ drop down and add a Journal, News, Book,  one of each
+> citations.
+> 2> Now click on “Insert” and select “Media”. Click on any picture returned
+> in the dialog(do not enter any search term)
+> 3> In the Media Settings dialog click on “Insert” again and select “Media”
+> from the Caption toolbar. Click on any picture returned in the dialog.
+> 4> Now close all the dialogs. 
+> 5> Repeat again steps #2,3 and 4.
+> 6>In the main VE window  click on “Cite”  and select “Basic”. Reference
+> dialog opens.
+> 5> In the Reference dialog select “Use an existing reference”.
+> 6> Script Error is shown as existing reference.
+
+The problem here is the ""re-use existing reference"" code seems to rely on there being a reference list on the page (or there having been one at some point in this edit?) – if there's no reference list yet, it shows the references as blank or with a Lua script error. Is this something as simple as populating the internal list as needed?
+
+**Attached**: {F14429}",1405526743,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-czceip6xh6hv5epzval5,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Steps to reproduce:
+
+1.Open the media settings dialog for an image
+2.Edit something in the caption field to enable the ""Apply Changes"" button
+3.Undo the edit from the toolbar
+
+Observed Result:
+The ""Apply Changes"" button still remains enabled
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1405450800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_description,resolved
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog",Verified the fix in production,1411070271,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog",Verified the fix in test2,1410554273,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog",Verified the fix in Betalabs,1409961205,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Change 152790 merged by jenkins-bot:
+Check for changes in the model
+
+https://gerrit.wikimedia.org/r/152790",1409864834,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Change 152790 had a related patch set uploaded by Mooeypoo:
+[wip] Check for changes in the model
+
+https://gerrit.wikimedia.org/r/152790",1407431083,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Change 150478 abandoned by Mooeypoo:
+Check for changes in media dialog
+
+Reason:
+Redone in a different commit
+
+https://gerrit.wikimedia.org/r/150478",1407431002,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+"VisualEditor: Undoing the edit from toolbar does not disable the ""Apply Changes"" button inside Media Settings dialog","Change 150478 had a related patch set uploaded by Mooeypoo:
+Check for changes in media dialog
+
+https://gerrit.wikimedia.org/r/150478",1406692874,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zlsf4q2llhdhofvqvfe6,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"For repositories that we're (also) mirroring at a custom name, they are currently being mirrored twice.
+
+For example:
+
+* https://github.com/wikimedia/VisualEditor
+  https://github.com/wikimedia/VisualEditor-VisualEditor
+
+
+* https://github.com/wikimedia/oojs
+  https://github.com/wikimedia/oojs-core
+
+* https://github.com/wikimedia/puppet-kafka
+  https://github.com/wikimedia/operations-puppet-kafka
+
+This is confusing and also decentralises things like Watching and Fork tracking. But, more importantly, it also makes our Star rating and Pull requests harder to maintain.
+
+
+I don't know whether we intentionally do both, or whether it was just easier to implement this way.
+
+I'd recommend we get rid of the full names where we want to publish the repo under a different name.
+
+If it was a conscious choice to do this I'm curious why. The only reason I can think of is to make them easier to find on GitHub, which is hardly a big issue since they have excellent search for repo names right on https://github.com/wikimedia.
+
+Another reason might be being able to automatically generate a GitHub address for a Git repo, but I'm not sure that's a big issue.
+
+Also note that GitHub supports renaming of repositories and automatically keeps redirects[1]. So we can remove the ""unwanted"" names from Gerrit replication config and have our github.com/wikimedia admins delete the repos and create a redirect (by renaming the good one to the bad one and then renaming it back).
+
+As an example I've created a redirect from https://github.com/wikimedia/mediawiki to https://github.com/wikimedia/mediawiki-core. Eventually this should be done the other way around but this was easier to set up since Gerrit replag currently did not push to /mediawiki yet (unlike oojs and VisualEditor).
+
+
+[1] https://github.com/blog/1508-repository-redirects-are-here
+[2] https://help.github.com/articles/renaming-a-repository
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1405448880,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cvdip7jn2gnnatmluyma,task_description,resolved
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"Fwiw, we renamed the parsoid repository to https://github.com/wikimedia/parsoid with no ill effects. Even the travis tests kept working.",1415722581,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"Change 167162 merged by Dzahn:
+gerrit: Remove duplicate mirrors
+
+https://gerrit.wikimedia.org/r/167162",1413846804,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"Change 167162 had a related patch set uploaded by Krinkle:
+gerrit: Remove duplicate mirrors
+
+https://gerrit.wikimedia.org/r/167162",1413513240,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"The redirects GitHub has in place apply both to the HTTP protocol (web interface) as well as the Git interface itself. We can simply remove the duplicate ""pretty name"" replications and perform the renames on GitHub. That way there's only one repo Gerrit is pushing two and both urls work.
+
+I've gone ahead and done this with mediawiki-core as example.
+
+From Gerrit's perspective it's a straight up replication from gerrit:mediawiki/core to github:mediawiki-core. There is no fancy-name duplicate set up for it.
+
+On GitHub it has been renamed from mediawiki-core with a full redirect in place. Gerrit is now effectively pushing to https://github.com/wikimedia/mediawiki while all urls and logs for mediawiki-core continue to work as expected.",1413512026,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"(In reply to christian from comment #1)
+> > If it was a conscious choice to do this I'm curious why.
+> 
+> We want all gerrit repos replicated on github.
+> 
+> We could setup replication for each repository in our gerrit
+> separately. That would allow full control of repository names at
+> github. But it is tedious, time-consuming, and has other warts too.
+> 
+
+> So in order to escape such a messy, verbose replication setup, gerrit
+> replicates each and every projects to github under the name that gets
+> used on gerrit [1]. For this replication, we do not prune leading
+> paths, as that would map different names on gerrit to the same names
+> on github [2].
+
+I wasn't suggesting that we do it manually. All repos should be replicated. I'm also well-aware of naming conflicts if we were to prune leading paths. Nobody was suggesting that.
+
+> However, some people felt strongly that they needed a better
+> repository name on github, or had a following on github that they
+> would not want to loose. So they had an additional, separate
+> replication target set up. And hence, those repositories get replicated
+> twice to github. Once for the canonical name. And a second time for
+> the custom name of their liking.
+
+Exactly. And there's no reason to have to replications. It should be easy to remove the additional one. For projects using github more publicly, they tend to have a better name there to hide internal implementation details of Gerrit or Wikimedia (e.g. VisualEditor, MediaWiki and OOjs have stupidly named repos in gerrit of VisualEditor/VisualEditor and oojs/core and mediawiki/core, this is due to conventions and limitations in our use of Gerrit).
+
+> > Also note that GitHub supports renaming of repositories and
+> > automatically keeps redirects[...]
+> 
+> Thanks! That wasn't available when we added custom replication.
+> We could use that to solve most issues.
+> 
+> > As an example I've created a redirect from
+> > https://github.com/wikimedia/mediawiki to
+> > https://github.com/wikimedia/mediawiki-core. Eventually this should be
+> > done the other way around [...]
+> 
+> Not too sure about this one.
+> Doing it “the other way around” would make it even more confusing for
+> people, because the “canonical” github name would differ from the
+> gerrit name too much to be able to map it clearly.
+> 
+
+I'm not sure you understood that I meant.
+
+Right now we replicate all repos from <gerrit-id> to github:<gerrit-id-escaped> and have additional replications for those that needed better names.
+
+I'm saying: Omit the ones with custom names from the wildcard replication so that there's only one.
+
+For existing repos already replicated twice, we'll have to manually remove the (now stale) repository from the admin panel at github. While at it, we can turn those into redirects to the custom name to make sure any urls stay working.",1408969654,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+Gerrit: Use GitHub redirects instead of duplicate mirrors,"> If it was a conscious choice to do this I'm curious why.
+
+We want all gerrit repos replicated on github.
+
+We could setup replication for each repository in our gerrit
+separately. That would allow full control of repository names at
+github. But it is tedious, time-consuming, and has other warts too.
+
+So in order to escape such a messy, verbose replication setup, gerrit
+replicates each and every projects to github under the name that gets
+used on gerrit [1]. For this replication, we do not prune leading
+paths, as that would map different names on gerrit to the same names
+on github [2].
+
+However, some people felt strongly that they needed a better
+repository name on github, or had a following on github that they
+would not want to loose. So they had an additional, separate
+replication target set up. And hence, those repositories get replicated
+twice to github. Once for the canonical name. And a second time for
+the custom name of their liking.
+
+> Also note that GitHub supports renaming of repositories and
+> automatically keeps redirects[...]
+
+Thanks! That wasn't available when we added custom replication.
+We could use that to solve most issues.
+
+> As an example I've created a redirect from
+> https://github.com/wikimedia/mediawiki to
+> https://github.com/wikimedia/mediawiki-core. Eventually this should be
+> done the other way around [...]
+
+Not too sure about this one.
+Doing it “the other way around” would make it even more confusing for
+people, because the “canonical” github name would differ from the
+gerrit name too much to be able to map it clearly.
+
+
+
+[1] github does not like “/”s in repo names, so we're having them
+    replaced by “-”s.
+
+[2] For example we currently have three repositories in gerrit that
+    end in “/data”.
+    Or which of “analytics/kraken” and “analytics/vagrant/kraken”
+    should become github's “kraken”?
+    Same problems for “/Nostalgia”.",1405502216,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-cvdip7jn2gnnatmluyma,task_subcomment,NA
+VisualEditor: Scroll bar is appearing inside the language inspector,"Screenshot
+
+Open a language inspector, a scroll bar is appearing inside the inspector
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14372}",1405448700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aay645uqkadlmx7yyijx,task_description,resolved
+VisualEditor: Scroll bar is appearing inside the language inspector,Verified the fix in production,1407188930,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aay645uqkadlmx7yyijx,task_subcomment,NA
+VisualEditor: Scroll bar is appearing inside the language inspector,Verified the fix in test2,1406324116,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aay645uqkadlmx7yyijx,task_subcomment,NA
+VisualEditor: Scroll bar is appearing inside the language inspector,Verified the fix in Betalabs,1406160613,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aay645uqkadlmx7yyijx,task_subcomment,NA
+VisualEditor Mobile: Text cannot be pasted into link inspector search field from mobile browser,"Tap, or tap and hold on text input field in tablet VE, expected behavior, native iOS copy/paste flag should be shown, but it us not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405412580,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-rihr5cwlyy5m2utltcfx,task_description,resolved
+VisualEditor Mobile: Text cannot be pasted into link inspector search field from mobile browser,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487876,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rihr5cwlyy5m2utltcfx,task_subcomment,NA
+VisualEditor Mobile: Text cannot be pasted into link inspector search field from mobile browser,Needs re-testing.,1430336362,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rihr5cwlyy5m2utltcfx,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Steps to reproduce:
+
+1.Insert an image in a page
+2.Change the size of the image by going to Custom tab
+3.Click on ""Apply Changes""
+4.Now again open the media settings dialog and switch to default tab
+
+
+Observed Result:
+Previously as soon as user switched to default tab, it used to set the text fields to default size, but now its keeping the custom size values.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405363500,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_description,resolved
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Verified the fix in production,1411069966,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Verified the fix in test2,1410556646,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Verified the fix in Betalabs,1409945915,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 158395 merged by jenkins-bot:
+Set default dimensions based on original dimensions
+
+https://gerrit.wikimedia.org/r/158395",1409864506,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 158395 had a related patch set uploaded by Mooeypoo:
+Set default dimensions based on original dimensions
+
+https://gerrit.wikimedia.org/r/158395",1409844685,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Still reproducible...,1409255728,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 149217 merged by jenkins-bot:
+Make the image model persistent
+
+https://gerrit.wikimedia.org/r/149217",1409242085,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 149217 had a related patch set uploaded by Mooeypoo:
+Make the image model persistent
+
+https://gerrit.wikimedia.org/r/149217",1408487289,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","This is again happening in production for this image:https://en.wikipedia.org/wiki/File:Black_sandbox.JPG
+
+Go to this page: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&oldid=619869934
+
+Go to the Media settings>Advanced Settings for this image.Switch to default tab.
+
+Observe that, the size values are still showing 22x17 which should be 220x165 as soon as I switch to Default tab.
+If you click on Apply Changes and reopen this dialog , still you will see its showing 22x17 instead of 220x165.
+If you Save the page and then reopen the page and the media settings dialog only then you will see the size value got changed to 220x165",1407186077,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","I cant reproduce it now , the problem was after changing the custom size value, when i was clicking on default tab , it was not changing the size values into default on the size value fields.But now it seems like doing that.",1406759565,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","I can't manage to reproduce this in master or in beta labs.
+
+When a new image is inserted, the default behavior is that it has 'default' size. If the user goes to the size widget and just clicks the 'custom' button, it will transform the existing (default) values to custom values (so, the values are the same as the default, but they are literally expressed).
+
+So the values are the same because the user didn't change them, but the difference is whether the image is default or limited in size (despite the fact both sizes are functionally the same)
+
+For instance, for the image ""Chef's knife grip.jpg"" in beta labs:
+
+Clicking ""Custom"" size will result in this wikitext:
+
+[[File:Chef's knife grip.jpg|thumb|200x200px]]
+
+Clicking ""Default"" size will result in this wikitext:
+
+[[File:Chef's knife grip.jpg|thumb]]
+
+That's the expected result. Is something else happening? I can't reproduce a bug.",1406745809,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",This is happening again (!) in Betalabs now,1406744714,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size",Verified the fix in test2,1406323644,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 147219 merged by jenkins-bot:
+Make the image model work without a node
+
+https://gerrit.wikimedia.org/r/147219",1406161977,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+"VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size","Change 147219 had a related patch set uploaded by Mooeypoo:
+Make the image model work without a node
+
+https://gerrit.wikimedia.org/r/147219",1405978510,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-74pysrayjf4h6tgvqp3q,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add some categories
+3.Click on the newly added category to bring up the context menu for the category
+
+Observed Result:
+
+The context menu for the newly added category is appearing as blank with no option to specify ""sort this page as if it is called"" field value.
+
+See the screeshot attached
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14597}",1405110420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftd3677o2fooxu3axvei,task_description,resolved
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,Verified the fix in production en.wiki,1406316351,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,Verified the fix in test2,1405724443,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,BetaLabs gremlin. Blargh.,1405123633,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,Works for me without debug=true...,1405123401,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs,Goes away when debug=true is called – maybe a deployment/BetaLabs gremlin issue?,1405122521,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ftd3677o2fooxu3axvei,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"[[https://en.wikipedia.org/wiki/Wikipedia:Media_Viewer/June_2014_RfC|Wikipedia:Media Viewer/June 2014 RfC]]
+
+The consensus on the English Wikipedia is to disable Media Viewer by default.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/Wikipedia:Media_Viewer/June_2014_RfC
+**See Also**:
+* {T71080}
+* {T71292}",1405031700,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_description,declined
+Disable Media Viewer by default on the English Wikipedia,"(In reply to WhatamIdoing from comment #2)
+> Changing default user preferences means overriding the choices of registered
+> editors who actually want the feature (including thousands of editors who
+> voluntarily opted-in before MediaViewer was made avaialble by default).  
+> 
+> It's too bad that MediaWiki doesn't have a good one-click system for
+> changing prefs, like a ""Click here to enable X"" button or pop-up.  It'd be
+> so much easier than telling hundreds of users ""Go to Special:Preferences,
+> click to this tab, scroll halfway down, find this item, tick the box, scroll
+> all the way down, save the page.""
+
+That's an interesting idea and I've filed it as bug 67846.",1405075470,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"(In reply to Brent Laabs from comment #10)
+> MV tells users that they have to attribute CC0 and PD images (they don't).
+
+This is https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/736
+
+> I wanted to see the message that was in the public domain attribution message, 
+> so I clicked in the message field, and pressed the right arrow to see the end 
+> of the selection -- oops!  Next image.
+
+We try to make copying the message very easy, which means the text gets focused and preselected automatically from time to time (e.g. when switching tabs). If it would capture keystrokes on top of that, that would result in a very confusing behavior (prev/next would basically stop working when you open the panel).
+
+Opened bug 67835 about the underlying issue though, which is that it should be possible to just read these texts without copying them.",1405051614,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"(In reply to Erik Moeller from comment #9)
+> even if you are still unhappy with the result.
+
+Erik, my level of satisfaction is irrelevant. As I expressed in the Commons RfC, ""I Don't Like It""-style votes are not valuable, and should not be counted in evaluating consensus.
+
+https://commons.wikimedia.org/w/index.php?title=Commons:Requests_for_comment/Media_Viewer_software_feature&diff=128325247&oldid=128324966
+
+It seems that you and the Multimedia Team, though, don't take the same view on the other side. You seem to attach great importance to the fact that you reached out to some Wikipedians, and they responded ""I Like It.""
+
+The ""NOTCONSENT"" policy cited makes it clear that WMF must act on its own discretion on legal matters, and I have no quarrel with that. Certainly there are cases where consensus has no place. But this is not one of them. On matters that involve sophisticated judgment -- is it your position that WMF is capable of evaluating what constitutes good judgment, and local communities are not?
+
+It seems that you are quick to cite your community engagement practices when doing so serves your objective of deploying the software, but quick to dismiss community input that do not support that objective.",1405043664,PHID-USER-am4534nrql73corsejoh,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"**bslaabs** wrote:
+
+I have to admit that I didn't like MediaViewer at first, but I read Erik's comments, and decided to give it another try.  And it's definitely improving.  It's now at the quality level of an early beta release, rather than the alpha release level it was at when it was first implemented.
+
+The fullscreen button was surprising at first, but I can see the use of it.  But after that, it only took me 2 minutes to find two bugs. MV tells users that they have to attribute CC0 and PD images (they don't).  I wanted to see the message that was in the public domain attribution message, so I clicked in the message field, and pressed the right arrow to see the end of the selection -- oops!  Next image.
+
+I'm not a person with highly established workflows -- my contributions to English Wikipedia are around one edit per month, and I use other wiki software.  Media Viewer is just confusing, and feels incomplete.  It's not my workflow breaking, it's a new feature's interface being confusing.
+
+I'm really disappointed that the WMF seems to want to force this on the community, when it's so clearly a product still in need of development.  And I'm more disappointed that the only response to the community has been based on Silent Majority arguments and a disdain for experienced members of the community.
+
+If this bug is marked WONTFIX, where can I file a bug about the WMF?",1405042116,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"Pete: Not at all. We've paid close attention to the requests by readers and editors throughout the development process. In fact, there are aspects of Media Viewer (like the prominent Commons links) which I believe can be directly traced to your own early feedback, even if you are still unhappy with the result. 
+
+Recent significant changes include an off switch for readers, and an easy click-through link to the full resolution version. I think you will also appreciate the attribution hints recently added to the download tab (see here: https://www.mediawiki.org/wiki/Lightbox_demo#mediaviewer/File:Swallow_flying_drinking.jpg ). Some of these changes were made _while_ the RFC took place.
+
+We'll continue to improve Media Viewer, but we'll also focus more attention in coming weeks on the upload process and on structured data support in partnership with Wikidata (the latter should help ensure that we can more consistently pull useful metadata into applications like Media Viewer, and potentially add some basic edit functionality to the overlay as well).",1405040744,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"(In reply to Erik Moeller from comment #7)
+
+Erik, the RfC is full of critiques of the methodology that led the WMF team responsible for this feature to the conclusion that it serves the reader better. Through this action you seem to be saying that the WMF team is correct by virtue of its being the WMF team, and the English Wikipedia community is wrong by virtue of its being the English Wikipedia community.",1405039576,PHID-USER-am4534nrql73corsejoh,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"Steinsplitter:
+
+It's longstanding WMF policy and practice to apply judgment to community RFCs and requests regarding software and configuration changes on a case-by-case basis, depending on the nature of the requested change, the level of participation, the impact on readers/editors, etc. See: https://meta.wikimedia.org/wiki/Limits_to_configuration_changes
+
+In this case, we will keep the feature enabled by default (it's easy to turn off, both for readers and editors), but we'll continue to improve it based on community feedback (as has already happened in the last few weeks).",1405038276,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"@Erik Moeller:
+Why the Wikimedia Fondation as content provider overwrites community consensus?
+Is this only a ""i don't like to follow communety consensus"" WONTFIX or a Office Action?
+
+Per shellpolicy there is enough consensus to merge this change.",1405038074,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"(In reply to WhatamIdoing from comment #2)
+> It's too bad that MediaWiki doesn't have a good one-click system for
+> changing prefs, like a ""Click here to enable X"" button or pop-up.  It'd be
+> so much easier than telling hundreds of users ""Go to Special:Preferences,
+> click to this tab, scroll halfway down, find this item, tick the box, scroll
+> all the way down, save the page.""
+
+MediaViewer does provide that functionality, actually (it's at the bottom of the metadata panel).",1405037726,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"Closing WONTFIX per previously provided explanation:
+https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Media_Viewer/June_2014_RfC&diff=prev&oldid=616407785",1405037582,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"I see no reason in honoring this request. MediaViewer only displays media in a different way, *and* it can be disabled in your preferences. This is normal software evolution.
+
+It is nothing like VisualEditor, which was disruptive for all editors. This is not, and editor consensus cannot dicatate how all *readers* should experience the use of media.",1405036716,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,"Changing default user preferences means overriding the choices of registered editors who actually want the feature (including thousands of editors who voluntarily opted-in before MediaViewer was made avaialble by default).  
+
+It's too bad that MediaWiki doesn't have a good one-click system for changing prefs, like a ""Click here to enable X"" button or pop-up.  It'd be so much easier than telling hundreds of users ""Go to Special:Preferences, click to this tab, scroll halfway down, find this item, tick the box, scroll all the way down, save the page.""",1405035696,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+Disable Media Viewer by default on the English Wikipedia,Just need to set the default user option to 'false' really.,1405032080,PHID-USER-4n6zx4s5v23pjdztvtnr,False,PHID-TASK-ek6i77jrst3xdd4rkvxd,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception","Steps to reproduce:
+
+1.Open a page with VE which has a reference note in it
+2.Now place your cursor after the reference note
+3.Press backspace to select the reference note
+4.Now press down key to go to the next line
+
+Observed Result:
+The cursor does not go to the next line and an error appears in the console:
+
+Uncaught NotFoundError: Failed to execute 'selectNode' on 'Range': The node provided is null. 
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404944220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bszbfrxj2jltj2nwse7z,task_description,resolved
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception",Verified the fix in production en.wiki,1406317860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception",Verified the fix in test2,1405721607,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception",Verified the fix in Betalabs,1405553568,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception","Change 146472 merged by jenkins-bot:
+Don't handle up/down on focusableNodes even if backwards
+
+https://gerrit.wikimedia.org/r/146472",1405444891,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception","Change 146472 had a related patch set uploaded by Esanders:
+Don't handle up/down on focusableNodes even if backwards
+
+https://gerrit.wikimedia.org/r/146472",1405437014,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bszbfrxj2jltj2nwse7z,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Media
+3.Enter a search term
+4.Select the first image that appears on the search result
+4.Click on Change image immediately
+5.Enter a different search term
+6.Now try to select the first image on of the new search results 
+
+
+Observed Result:
+It throws an error:Uncaught TypeError: Cannot read property 'context' of undefined 
+
+and cannot select that image
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404935520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_description,resolved
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one",Verified the fix in production,1408046600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one",Verified the fix in test2,1407196170,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","Yeah, deeming this FIXED.",1406757740,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","When I tried to reproduce this bug (before the merge of the above fix), I kept getting this error in chrome:
+
+Uncaught TypeError: undefined is not a function commons.wikimedia.org/w/api.php?callback=jQuery1111024360889615491033_14067…set=0&prop=imageinfo&iiprop=dimensions%7Curl%7Cmediatype&iiurlheight=150:1
+
+And this in in firefox
+
+TypeError: jQuery111109862733512069084_1406742881657 is not a function
+	
+/**/jQuery111109862733512069084_1406742881657({""warnings"":{""main"":{""*"":""Unrecogn...
+
+And only after that I get an 'uncaught type error' that seems to be related to missing details in the image (like the caption document). It only happens right after the first API bug. I wasn't able to reproduce it after the 150054 fix was introduced. 
+
+The API response just before the bug appears seems to suggest that the information from the API is maybe mismatch to the loaded image, which is why I thought it was related. 
+
+The bug doesn't happen with this fix anymore (I can't reproduce it in master or in beta labs now that it's merged)",1406754030,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","(In reply to Moriel Schottlender from comment #1)
+> This seems to be the same jQuery/API issue we've had with calling the mw API
+> consecutively. When the API is queried more than once the callback function
+> goes haywire.
+> 
+> In debug mode when clicking the 'change image' (#4 in the above reproduce
+> list), the console error is
+> 
+> ""Uncaught TypeError: undefined is not a function"" 
+> api.
+> php?callback=jQuery111109575085956603289_1404944903047&format=json&uselang=en
+> &action=query&gene…:1
+
+That undefined function error is not related in any way, that's bug 59604.",1406740660,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","Change 150054 merged by jenkins-bot:
+MWMediaSearchWidget: Use json/jsonp for local/foreign api respectively
+
+https://gerrit.wikimedia.org/r/150054",1406740428,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","Change 150054 had a related patch set uploaded by Mooeypoo:
+MWMediaSearchWidget: Use json/jsonp for local/foreign api respectively
+
+https://gerrit.wikimedia.org/r/150054",1406678138,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one","This seems to be the same jQuery/API issue we've had with calling the mw API consecutively. When the API is queried more than once the callback function goes haywire.
+
+In debug mode when clicking the 'change image' (#4 in the above reproduce list), the console error is
+
+""Uncaught TypeError: undefined is not a function"" 
+api.php?callback=jQuery111109575085956603289_1404944903047&format=json&uselang=en&action=query&gene…:1",1404945249,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-wlzgvsmjnsumbns2rmzg,task_subcomment,NA
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes","Steps to reproduce:
+
+1.Open a page with VE which has image inside it
+2.Open the media settings dialog for the image
+3.Edit the values for the image size
+4.Without saving this change just close the Media Settings dialog
+5.Reopen the media settings dialog again and check the image size values
+
+Observed Result:
+It shows the changed value even though you have not saved it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67684",1404849360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gnfxkxgge6jy5yegpul5,task_description,resolved
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes",Verified the fix in production en.wiki,1406317590,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gnfxkxgge6jy5yegpul5,task_subcomment,NA
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes",Verified the fix in test2,1405723196,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gnfxkxgge6jy5yegpul5,task_subcomment,NA
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes","Change 146513 merged by jenkins-bot:
+Update VE core submodule to master (ad18102)
+
+https://gerrit.wikimedia.org/r/146513",1405550634,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gnfxkxgge6jy5yegpul5,task_subcomment,NA
+"VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes","Change 146513 had a related patch set uploaded by Mooeypoo:
+Work on a cloned scalable when editing images
+
+https://gerrit.wikimedia.org/r/146513",1405459529,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gnfxkxgge6jy5yegpul5,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Steps to reproduce:
+
+1.Open a page with VE which has an image inside it
+2.Open the advanced settings dialog for that image 
+3.Type something in the Custom fields 
+
+Observed Result:
+The Apply changes button does not get enabled upon changing the size value, it should change the tab to custom and enable the button
+
+Environment:Betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67687",1404848100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a532f3kpz7dqjttdx5l3,task_description,resolved
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button",*** Bug 68014 has been marked as a duplicate of this bug. ***,1406427644,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button",Verified the fix in production en.wiki,1406317798,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button",Verified the fix in test2,1405723080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Change 146682 merged by jenkins-bot:
+Listen to widget changes in MediaDialog
+
+https://gerrit.wikimedia.org/r/146682",1405550963,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Change 146676 merged by jenkins-bot:
+Switch to 'custom' when MediaSizeWidget updates
+
+https://gerrit.wikimedia.org/r/146676",1405543080,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Change 146682 had a related patch set uploaded by Mooeypoo:
+Listen to widget changes in MediaDialog
+
+https://gerrit.wikimedia.org/r/146682",1405477222,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button","Change 146676 had a related patch set uploaded by Mooeypoo:
+Switch to 'custom' when MediaSizeWidget updates
+
+https://gerrit.wikimedia.org/r/146676",1405476932,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable ""Apply Changes"" button",It also happens when you reopen an image which was previously has been set to a custom size and try to edit those values.,1404848767,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a532f3kpz7dqjttdx5l3,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with mobile VE with iOS Safari
+2.Tap the cursor on a link to bring up the context menu for it
+3.Now tap at the end of some other text to place the cursor there
+
+Observed Result:
+The context menu for the previous link is appearing on top of the article.
+
+
+Environment : Betalabs and test2
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67433
+
+**Attached**: {F14661}",1404773940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_description,resolved
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document",Verified the fix in production,1408047291,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document","Both the cases got resolved, checked in test2",1407265581,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document",I think this is now fixed too.,1406747354,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document","Another case to get such issue could be:
+
+
+If you delete the content of a page which had a link, it shows the context menu for the deleted link on a blank page, I suppose the fix for the original issue, should fix this case as well?",1404775519,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fyzrdfvjxxuw2ddhhqeq,task_subcomment,NA
+"VisualEditor: ""Make full Size"" is not enabling ""Apply changes"" button therefore cannot make any image fullsize","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to the Advanced Settings of an image
+4.Click on ""Make full size""
+
+
+Observed Result:
+The ""Apply Changes"" button is still disabled , cannot make any image full size
+
+Environment:test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404764520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wdsm7d6qbu5bt75ivacj,task_description,resolved
+"VisualEditor: ""Make full Size"" is not enabling ""Apply changes"" button therefore cannot make any image fullsize",Verified the fix in production,1405625917,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wdsm7d6qbu5bt75ivacj,task_subcomment,NA
+"VisualEditor: ""Make full Size"" is not enabling ""Apply changes"" button therefore cannot make any image fullsize",Verified the fix in test2,1405035306,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wdsm7d6qbu5bt75ivacj,task_subcomment,NA
+"VisualEditor: ""Make full Size"" is not enabling ""Apply changes"" button therefore cannot make any image fullsize","This was the same issue as https://bugzilla.wikimedia.org/show_bug.cgi?id=66863
+The following commit fixed it:
+
+Apply 'original size' to images
+
+https://gerrit.wikimedia.org/r/144637",1404865232,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wdsm7d6qbu5bt75ivacj,task_subcomment,NA
+Enable Visual Editor by default on pt.Wikiversity,"Ni!
+
+Since early this year we at pt.wikiversity have used the Visual Editor as an opt-in ""beta feature"".
+
+After this experimental phase, we have agreed that we want the Visual Editor to be enabled as default editor for everyone on pt.wikiversity, including unregistered users.
+
+https://pt.wikiversity.org/wiki/Wikiversidade:Esplanada#Habilitar_editor_visual_por_padr.C3.A3o
+
+We'd really appreciate if this could happen before the end of the July, since classes in Brazil start on early August.
+
+Cheers,
+Solstag
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1404719340,PHID-USER-wr7prgh3p37xrvbdr6w5,False,PHID-TASK-kckucons2r46xrc5a3xw,task_description,resolved
+Enable Visual Editor by default on pt.Wikiversity,"(Note that it will take a 30 days for the cache to be purged, so pages that aren't edited before then will appear to only have one tab to logged-out users until the pages are purged, edited, or the cache expires.)",1404775551,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kckucons2r46xrc5a3xw,task_subcomment,NA
+Enable Visual Editor by default on pt.Wikiversity,Now done.,1404775431,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kckucons2r46xrc5a3xw,task_subcomment,NA
+Enable Visual Editor by default on pt.Wikiversity,"Change 144476 merged by jenkins-bot:
+Enable VisualEditor by default on Portuguese Wikiversity
+
+https://gerrit.wikimedia.org/r/144476",1404774163,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kckucons2r46xrc5a3xw,task_subcomment,NA
+Enable Visual Editor by default on pt.Wikiversity,"Change 144476 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on Portuguese Wikiversity
+
+https://gerrit.wikimedia.org/r/144476",1404751768,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kckucons2r46xrc5a3xw,task_subcomment,NA
+Annotations are not preserved between edits,"**Author:** `drobbins`
+
+**Description:**
+Currently, any edits to a page will create a new page with no annotations, which makes this extension very difficult to use. You must look at the page history, and look at each revision for potential annotations that people may have added, and there is no icon or other indication that a revision actually *has* annotations. So they are likely to be lost or ignored.
+
+Ideally, annotations would be preserved through wiki edits and apply to newer revisions of pages. This would likely require updates to the editor.
+
+I realize that this may be technically challenging to implement. However, the preservations of annotations across edits does seem to be essential for really ensuring that this extension is useful (In fact, I wouldn't consider this annotation feature actually fully implemented until this is supported.)
+
+The true ideal implementation would be to display annotations in the editor, and like a true word processor, track changes to the underlying text to ensure that the annotation still existed even if the underlying text was modified in some way, as is how annotations work in word processors. This would have the added benefit of allowing editors to view annotations in real-time as they are editing a document, which would be extremely handy as many annotations deal with changes to the document that need to be made (or at least, should be addressed in some way during an edit cycle.
+
+Proposed design:
+
+[ editor window top ]
+
+
+[ Highlighted yellow: Editing this line in the editor.... ]
+
+
+[ editor window bottom ]
+
+[ Annotation: Display annotation(s) related to cursor position here. ]
+[ Button: add comment ] <-- editor would use this to add comment to existing annotation, related to any edits.
+
+I don't know if that is helpful for conveying how annotations could work in the editor, or not. I think this should be added to the default editor, and VisualEditor can add its own support. I don't think this feature should be VE-only.
+
+A possible work-around to make things a bit more bearable in the mean-time would be to add some kind of icon in the page history to indicate revisions that have annotations, so that the maintainer of the page can go through the page's history and look for annotations from people.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1404696600,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6tl7tgozycm2vk3qmwxb,task_description,declined
+Annotations are not preserved between edits,Declining per {T189753}. The extension is no longer maintained and has been archived.,1521636419,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-6tl7tgozycm2vk3qmwxb,task_subcomment,NA
+Annotations are not preserved between edits,"This is a valid report.  However, as you say it is technically challenging, and we did not intend the initial version to have this support.
+
+(In reply to Daniel Robbins from comment #0)
+> A possible work-around to make things a bit more bearable in the mean-time
+> would be to add some kind of icon in the page history to indicate revisions
+> that have annotations, so that the maintainer of the page can go through the
+> page's history and look for annotations from people.
+
+That's a good idea.  Filed as bug 67939.",1405227656,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-6tl7tgozycm2vk3qmwxb,task_subcomment,NA
+"VisualEditor: On wikis where anons can't create pages, you aren't told this until you try and save","Admittedly there are no links to take you to edit the page, but navigating to New_page?action=edit gives you and error, whereas New_page?veaction=edit let's you start editing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404562740,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ts644nvpin7nzxjkmyqi,task_description,resolved
+"VisualEditor: On wikis where anons can't create pages, you aren't told this until you try and save","Change 144275 merged by jenkins-bot:
+Give a notice if the user isn't allowed to create the page
+
+https://gerrit.wikimedia.org/r/144275",1406074327,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ts644nvpin7nzxjkmyqi,task_subcomment,NA
+"VisualEditor: On wikis where anons can't create pages, you aren't told this until you try and save","Change 144275 had a related patch set uploaded by Alex Monk:
+Give a notice if the user isn't allowed to create the page
+
+https://gerrit.wikimedia.org/r/144275",1404587535,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ts644nvpin7nzxjkmyqi,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Parsoid must produce/preserve the metadata about additional ResourceLoader modules required by extension tags. (I've heard some gossip that it falls back to PHP parser to do this, so this should be easy to do.)
+
+For example, in PHP parser, ""<syntaxhighlight lang=php>$foo</syntaxhighlight>"" will add up to two modules to ParserOutput's $mModuleStyles:
+* 'ext.geshi.language.php' (there is such a module for every supported language)
+* 'ext.geshi.local' (if $wgUseSiteCss is true)
+
+This information must somehow be provided by the API used by VisualEditor.
+
+The minimum set of things that have to be provided is the ones provided by OutputPage::addParserOutputContent() in PHP, that is modules, module styles, module scripts, module messages and JS config vars. (These are available via the action=parse&prop=modules API in core.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1404491460,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_description,resolved
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,Presumably this is resolved by T162399,1632170096,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"There were two requests at wikimania for the rest of the stuff included in this bug.  Namely:
+* Link to JS necessary to render the page contents.  (Especially for maps modules, etc)
+* Some sort of machine-readable enumeration of the modules required (in case you wanted to do manual loading of CSS/JS/etc).",1437516471,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 215883 merged by jenkins-bot:
+Include RL style modules from parser functions in <head>
+
+[[https://gerrit.wikimedia.org/r/215883]]",1434394337,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"* https://gerrit.wikimedia.org/r/215874 (branch master): #mw1.26, #mw1.26wmf9
+",1433784601,PHID-USER-n4kveqwjjlpsb6ydn73h,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 215874 merged by jenkins-bot:
+Expose RL modules and js config vars in action=expandtemplates
+
+[[https://gerrit.wikimedia.org/r/215874]]",1433521008,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 215883 had a related patch set uploaded (by Marcoil):
+Include RL style modules from parser functions in <head>
+
+[[https://gerrit.wikimedia.org/r/215883]]
+",1433418438,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 215874 had a related patch set uploaded (by Marcoil):
+Expose ResourceLoader modules in action=expandtemplates
+
+[[https://gerrit.wikimedia.org/r/215874]]
+",1433413960,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"A little status update:
+
+What currently works:
+* Parsoid correctly includes style modules from extensions present in the page that add them through ResourceLoader, so that when requesting the HTML directly from Parsoid it's presented correctly.
+
+What doesn't:
+* Style modules added by parser functions, as the expandtemplates API doesn't expose them yet. A patch similar to  @jackmcbarn's https://gerrit.wikimedia.org/r/162123, but without including non-RL modules would solve this.
+* All non-style modules exposed through ResourceLoader (Javascript, global vars, messages…). Parsoid's HTML output doesn't load ResourceLoader client infrastructure, so it's difficult to correctly load those modules.
+
+I'm not sure if it's even a good idea to load non-style modules in Parsoid's HTML <head>, tbh, given that it's not really used independently by anything right now. I like @cscott's proposal of exposing the information in data-mw so that clients can use them as they see fit.
+
+So my proposed next steps would be:
+* Expose all modules in action=expandtemplates, excluding non-RL modules.
+* Add the style ones to Parsoid's <head> as we do now with extension ones.
+* Expose all modules (styles and all others) through data-mw.
+
+That way, for example, when VE receives just the body of a page for editing, it would look into the data-mw and load the modules it sees there, which would fix T69515 and related. Right now VE can't get that data directly as it's in Parsoid's <head>.",1433264911,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"BTW, i'm trying to move TMH from it's global context into a more isolated one, but i'm guessing that due to the state of this ticket, that will also mean that when that patch lands, it will actually break TMH videos when added by VE right ? Since the global handlers would be gone and the 'local' ones are not loaded yet ?
+
+https://gerrit.wikimedia.org/r/172556
+https://gerrit.wikimedia.org/r/172421
+",1426927796,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"The merged patch takes care of adding the appropriate CSS modules to the load list, but only for extensions. Some parser functions (e.g. Babel) also have CSS modules, there's a patch for MW that would allow Parsoid to know about them here:
+https://gerrit.wikimedia.org/r/162123",1411490244,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 160423 merged by jenkins-bot:
+Bug 67540 - Load extension CSS modules
+
+https://gerrit.wikimedia.org/r/160423",1411487498,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"As discussed on IRC, we'll do a first patch only for CSS support, and then expand on it with the rest of extensions' resources. We can continue using this bug for this and for C. Scott's proposal of exposing the modules in metadata.
+
+Btw, does anyone have examples of pages where an extension CSS causes Parsoid to render differently from PHP? I'd like to test the visual diffs with this patch. Thanks!",1410801157,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"(12:15:15 PM) gwicke: cscott: we should expose the list separately, but for browsers it's probably more efficient to still do some bundling
+(12:15:29 PM) gwicke: good to unbundle the per-page modules from the global ones though
+(12:15:35 PM) gwicke: right now those are all mixed afaik
+(12:18:03 PM) cscott-free: gwicke: agreed.  i'm thinking of exposing the list via data-mw (for example) while still providing the resource url in a <link> tag for browsers.",1410797922,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"I think we'll want the lowlevel information about the modules available (via data-mw?), in addition to having One True Resource Loader URL which will load them all.
+
+In particular two of OCG backends, the ZIM writer and the future parsoid-phantomjs-PDF backend, will want to download the set of resources used by a (potentially large) set of pages.  We don't want to have to download the same resources in slight variations over and over again.  If there are N different resources used on a wiki, there are 2^N different resource loader URLs which load various combinations of the N resources.  We'd rather just load the N resources once, even if that means we have to do a little extra work ourselves to order and merge them.",1410797849,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"There's a WIP patch now at https://gerrit.wikimedia.org/r/160423 that adds the extensions' CSS modules to the style link.
+
+If we also want to load further extension resources, like JS or messages, I suppose we'll have to add loading ResourceLoader's client first and let it load everything else. Is this the way we should go?",1410780309,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Change 160423 had a related patch set uploaded by Marcoil:
+WIP: Bug 67540 - Load extension CSS modules
+
+https://gerrit.wikimedia.org/r/160423",1410780110,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+Produce/preserve the metadata about additional ResourceLoader modules required by extension tags,"Ex: http://en.wikipedia.org/w/api.php?action=parse&format=json&page=MathML&prop=modules 
+
+includes
+
+""modulestyles"":[""ext.rtlcite"",""ext.math.styles"",""ext.geshi.language.xml"",""ext.geshi.local"",""ext.geshi.language.html5""]
+
+CSS modules for inclusion in the <head> would be a good start and will help reduce rendering diffs.",1410554810,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-woa5qgdd2kuacxa4kj4z,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""","Screenshot
+
+Try to open any page with mobile VE in iOS Safari on Betalabs, the page does not load in VE and it shows an error at the bottom:
+""Error,can't load section""
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14353}",1404429960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-amg4rcgoazznjnphzquh,task_description,resolved
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Verified the fix in production,1405626073,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Verified the fix in test2,1405033146,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Fix by Roan unbreaking the databases.,1404755388,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",This seems to be working now :),1404755143,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Looks like this is caused by beta labs being in read-only mode. I can't edit on desktop either.,1404434217,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""","I can reproduce this on beta labs, but not in local master.",1404433574,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error ""Error,can't load section""",Sounds like it might be something on the MobileFrontend end.,1404431954,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-amg4rcgoazznjnphzquh,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Tap on a link
+3.When the context menu for that link appears tap on that
+4.Try to edit the link target name in the search box for link inspector
+5.No Link target page suggestions will appear inside the link inspector
+6.Close the link inspector
+7.Close the keyboard that is still appearing on CE
+
+Observed Result:
+The link suggestions are appearing on CE now
+See the screenshot attached
+
+
+This issue started happening after merging the new code for context menu on Mobile VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+
+**Attached**: {F14100}",1404258420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uv7harsaw6uegtz3aesy,task_description,resolved
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",Verified the fix in production,1405026565,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",Verified the fix in test2 with iOS,1404774256,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",Verified the fix in Betalabs with iOS,1404333352,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",Yay deployment.,1404331543,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open",This is still happening on Betalabs.,1404323693,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open","Change 143524 merged by jenkins-bot:
+Use globalOverlay as the contextOverlay in MobileContext
+
+https://gerrit.wikimedia.org/r/143524",1404260536,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open","Change 143524 had a related patch set uploaded by Catrope:
+Use globalOverlay as the contextOverlay in MobileContext
+
+https://gerrit.wikimedia.org/r/143524",1404260386,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uv7harsaw6uegtz3aesy,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Do not place your cursor anywhere on CE but try to select a node 
+3.Scroll down the page
+
+Observed Result:
+The toolbar also gets repositioned down while scrolling down the page.
+
+It might get resolved with :https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+
+Still I am filing it as a separate issue.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57177
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60110
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67433
+
+**Attached**: {F14695}",1404250320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_description,resolved
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected",Verified the fix in production,1408047625,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected",Verified the fix in test2,1407266218,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected","Change 145185 had a related patch set uploaded by Jforrester:
+Improve fixed header in overlays on iOS
+
+https://gerrit.wikimedia.org/r/145185",1405985194,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected","Interestingly, this bug only seems to occur in landscape mode on iPad.",1405726465,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+"VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected","This is also happening for the context menu bar in Mobile VE.When you put your cursor for the first time on a node such as link, the context menu bar appears somewhere in the middle of the screen and then scrolls down as you scroll down the page.
+However, it does not happen once you close the keyboard and try it for the second time on that session.",1404257056,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iedxgxzmnkj5w6tca2tu,task_subcomment,NA
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,"Steps:
+
+1. Create page with VE
+2. Insert New Template
+3. Enter text that is the prefix of one or more pages in the User namespace with template data
+
+Expected result:
+
+Suggestions show up as:
+ User:Foo/Template:Example
+ User:Foo/Template:Unsigned
+ User:Foo/Template:Unsigned2
+
+Actual result:
+
+Suggestions show up as
+ :User:Foo/Template:Example
+ :User:Foo/Template:Unsigned
+ :User:Foo/Template:Unsigned2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404243060,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-bcsjdeldob7pksf2jsjk,task_description,resolved
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,"(In reply to Alex Monk from comment #3)
+> So this *should* be fixed this time...
+
+Famous last words. :-)",1405472563,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bcsjdeldob7pksf2jsjk,task_subcomment,NA
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,So this *should* be fixed this time...,1405465885,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-bcsjdeldob7pksf2jsjk,task_subcomment,NA
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,"Change 144497 merged by jenkins-bot:
+MWTitleInputWidget: Remove prefixColon option and use relative title instead
+
+https://gerrit.wikimedia.org/r/144497",1405462245,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bcsjdeldob7pksf2jsjk,task_subcomment,NA
+VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon,"Change 144497 had a related patch set uploaded by Alex Monk:
+Get rid of my prefixColon config option from TitleInputWidget, use relative title
+
+https://gerrit.wikimedia.org/r/144497",1404761879,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bcsjdeldob7pksf2jsjk,task_subcomment,NA
+"""Maximum execution time"" error in JavaScriptMinifier while minifying QUnit test modules","It might possible to make this less likely by grouping them into smaller requests.
+
+The request is:
+
+---
+http://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=Base64.js%7Ceasy-deflate.core%2Cdeflate%7Cext.eventLogging%2Cmantle%7Cext.eventLogging.tests%7Cext.flow.new.handlebars.tests%7Cext.flow.new.tests%7Cext.gettingstarted.user%7Cext.gettingstarted.user.tests%7Cext.guidedTour.lib%2Cstyles%7Cext.guidedTour.lib.internal%2Ctests%7Cext.mantle.handlebars%2Ctemplates%7Cext.templateData.test%7Cext.templateDataGenerator.core%7Cext.visualEditor.base%2Ccore%2Clanguage%2Cmediawiki%2Cmwalienextension%2Cmwcore%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlink%2Cmwmeta%2Cmwreference%2Cmwtransclusion%2Cstandalone%2Ctest%2CviewPageTarget%7Cext.visualEditor.core.desktop%7Cext.visualEditor.mwimage.core%7Cext.visualEditor.viewPageTarget.init%7Cjquery.accessKeyLabel%2CautoEllipsis%2CbyteLength%2CbyteLimit%2CcheckboxShiftClick%2Cclient%2Ccookie%2CgetAttrs%2ChighlightText%2Ci18n%2Cjson%2CmakeCollapsible%2Cmw-jump%2CmwExtension%2Cplaceholder%2Cqunit%2CtabIndex%2Cthrottle-debounce%2CvisibleText%7Cjquery.qunit.completenessTest%7Cjquery.uls.data%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2Cfeedback%2CjqueryMsg%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.api.edit%7Cmediawiki.language.init%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.guiders%2Cpluralruleparser%7Cmediawiki.page.ready%2Cstartup%7Cmediawiki.skinning.content.parsoid%7Cmediawiki.special.javaScriptTest%7Cmediawiki.ui.button%7Coojs%2Coojs-ui%2Crangy%7Cskins.vector.js%7Ctest.mediawiki.qunit.testrunner%7Ctest.sinonjs%7Cunicodejs.wordbreak&skin=vector&version=20140701T185441Z&*
+
+---
+
+The error response is:
+
+
+Fatal error: Maximum execution time of 30 seconds exceeded in /vagrant/mediawiki/includes/libs/JavaScriptMinifier.php on line 428
+
+Call Stack:
+    0.0021     656184   1. {main}() /vagrant/mediawiki/load.php:0
+    0.2177   10838400   2. ResourceLoader->respond() /vagrant/mediawiki/load.php:43
+    0.4901   11686616   3. ResourceLoader->makeModuleResponse() /vagrant/mediawiki/includes/resourceloader/ResourceLoader.php:543
+    2.1315   19034048   4. ResourceLoader->filter() /vagrant/mediawiki/includes/resourceloader/ResourceLoader.php:923
+    2.1480   19272904   5. JavaScriptMinifier::minify() /vagrant/mediawiki/includes/resourceloader/ResourceLoader.php:181
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404241500,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-2ccuu4qtfxpytbz5rhoh,task_description,resolved
+"""Maximum execution time"" error in JavaScriptMinifier while minifying QUnit test modules","I can't reproduce this anymore. See also:
+
+* {b7eb243d9204a40977761fb2453070825dfeab97} 
+* {T107377}
+
+Things are now minified in smaller chunks and also better re-used as a result.",1448401810,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-2ccuu4qtfxpytbz5rhoh,task_subcomment,NA
+"""Maximum execution time"" error in JavaScriptMinifier while minifying QUnit test modules","This might be improved by enabling fsc caching for the VM: `vagrant config nfs_cache yes; vagrant reload`
+
+@dduvall and I would love feedback from power users on the pros/cons of using the fsc nfs cache.",1438044238,PHID-USER-ll6tmaogat2b5q7tnqas,True,PHID-TASK-2ccuu4qtfxpytbz5rhoh,task_subcomment,NA
+"""Maximum execution time"" error in JavaScriptMinifier while minifying QUnit test modules","I'm hitting this issue now in my local vagrant - this really shouldn't be taking 30 seconds to load should it even if it's a big file..?
+",1438043688,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-2ccuu4qtfxpytbz5rhoh,task_subcomment,NA
+VisualEditor: Converting a numbered external link to a regular one from the link inspector drops the annotations,"Converting a MWNumberedExternalLinkNode to MWExternalLinkAnnotation from the UI (link inspector) loses annotations on the node, even though there is code in place that aims handle this.
+
+See the behavior of the 'convert' variable in ve.ui.MWLinkNodeInspector.prototype.getTeardownProcess.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404236940,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kpjfjaghlnt74hhgi5cv,task_description,resolved
+VisualEditor: Converting a numbered external link to a regular one from the link inspector drops the annotations,"Change 143387 merged by jenkins-bot:
+MWLinkNodeInspector: Actually preserve annotations when converting to link annotation
+
+https://gerrit.wikimedia.org/r/143387",1406076286,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kpjfjaghlnt74hhgi5cv,task_subcomment,NA
+VisualEditor: Converting a numbered external link to a regular one from the link inspector drops the annotations,"Change 143387 had a related patch set uploaded by Bartosz Dziewoński:
+MWLinkNodeInspector: Actually preserve annotations when converting to link annotation
+
+https://gerrit.wikimedia.org/r/143387",1404244053,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kpjfjaghlnt74hhgi5cv,task_subcomment,NA
+VisualEditor: Converting a numbered external link to a regular one from the link inspector drops the annotations,This is because the node is removed from DM before its annotations are copied. Let me just fix it while I'm at it. :),1404242888,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kpjfjaghlnt74hhgi5cv,task_subcomment,NA
+VisualEditor:  The Help menu does not scroll on small screens while using Monobook,"Steps to reproduce:
+
+1.  Make your browser window short (<400 pixels?).
+
+2.  Open a page using the Monobook skin, e.g., https://en.wikipedia.org/wiki/Nicholas_Rigby?veaction=edit&useskin=monobook.
+
+3.  Click the (?) button to open the Help menu.
+
+4.  Because of the short screen, the entire menu does not fit on the screen at once.  Try to scroll down to read the last line on the Help menu.
+
+
+The Help menu is not scrolling, so you can't see anything that doesn't fit on your screen.  This is not a problem in Vector.  I have confirmed this in both Safari 6.1.4 and Firefox 30.
+
+Original report:  https://ru.wikipedia.org/w/index.php?diff=63851178 from Sunpriat
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404228840,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-nu4jynpne3safxk75oss,task_description,resolved
+VisualEditor:  The Help menu does not scroll on small screens while using Monobook,This was fixed a while ago.,1413330573,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nu4jynpne3safxk75oss,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Screenshot
+
+Steps to reproduce:
+
+1.Rotate the screen of your iOS device to landscape
+2.Open a page with mobile VE
+3.Tap on a drop down menu which has lot of options under it like for now we have ""Reference"" menu
+4.Open that menu
+5.Try to select the options from the bottom of the menu such as ""Use an existing reference"" or ""Journal""
+
+Observed Result:
+Cannot select any of those options since the keyboard is always open and overlapping with the menu,and scrolling down menu again drags the screen back to the top
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14572}",1404174840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_description,resolved
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,The design of the interface has changed so much in the intervening four years that this bug is effectively resolved; the menus look significantly different now. and additionally interacting with any of them collapses the keyboard.,1535711851,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Confirming that, it is still occurring.",1416354295,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"I attempted to reproduce this using CrossBrowserTesting.com, but whenever I click on the ""Cite"" icon using it, the entire toolbar disappears. I can't tell if it's a real bug or the testing app being broken. All in all, this was a wonderful waste of time and I'm still unable to debug, much less fix, this bug (and I still believe it shouldn't be accurring anyway in the first place per comment 5).",1416092830,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"(In reply to Roan Kattouw from comment #3)
+> Juliusz explained to me that there's a bug in iOS Safari when the keyboard
+> comes up: the viewport becomes smaller, but measuring the viewport does not
+> take this into account. The hack Juliusz is currently using in
+> MobileFrontend to compensate for this is to arrange the document such that
+> the main viewport never scrolls, instead everything is wrapped in a
+> scrollable <div> that's exactly the size of the viewport.
+
+This seems to be _fixIosHeader() in /javascripts/Overlay.js in MF.
+
+
+> To address this bug, we would have to have menus clip to this wrapper div
+> rather than the body, and we would have to have them reevaluate their
+> clipping state (by calling .clip()) every time this wrapper <div> is resized.
+
+Why doesn't this already work? ClippableElements are supposed to be clipped to the closest scrollable element, and surely the MF overlay is closer than body.",1413299032,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Bumping over to Bartosz; this is an awkward three-way bug between VE, MobileFrontend and OOUI as I understand it. Fun. :-(",1412970371,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"(In reply to Roan Kattouw from comment #2)
+> Hmm, this sounds like a bug related to ClippableElement. The menu should
+> automatically clip and become scrollable when there isn't enough screen
+> space for it. You can see this on desktop if you resize the window. Maybe
+> iOS Safari isn't emitting a resize event, or is emitting an event we're not
+> listening to, or isn't giving us the correct viewport dimensions?
+
+Juliusz explained to me that there's a bug in iOS Safari when the keyboard comes up: the viewport becomes smaller, but measuring the viewport does not take this into account. The hack Juliusz is currently using in MobileFrontend to compensate for this is to arrange the document such that the main viewport never scrolls, instead everything is wrapped in a scrollable <div> that's exactly the size of the viewport. Then he listens for focus events, and attempts to scroll the viewport down by a large amount (9999px or something?). Under normal circumstances, this has no effect, but if the keyboard is up, the viewport will be scrollable and measuring how much it scrolled by gives you the height of the keyboard. He then adjusts the sizing of the wrapper <div> so it once again fits the viewport exactly.
+
+This is also part of why things sometimes behave very strangely when focus events are dropped or emitted at the wrong time, because then Juliusz's code may not notice that the keyboard has appeared or disappeared, and it may not adjust the size of the wrapper <div> when it should.
+
+To address this bug, we would have to have menus clip to this wrapper div rather than the body, and we would have to have them reevaluate their clipping state (by calling .clip()) every time this wrapper <div> is resized.",1409695738,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Hmm, this sounds like a bug related to ClippableElement. The menu should automatically clip and become scrollable when there isn't enough screen space for it. You can see this on desktop if you resize the window. Maybe iOS Safari isn't emitting a resize event, or is emitting an event we're not listening to, or isn't giving us the correct viewport dimensions?",1407962590,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device,"Yep, I can confirm this on my iPad Air (iOS 7.1) when not using an external Bluetooth keyboard.
+
+In landscape mode with the keyboard open there is *very* little vertical space, only about 220px high, between the VE toolbar and the top of the keyboard -- vertically laid-out menus are probably not a good idea here.
+
+iOS text-selection menus tend to be laid out horizontally like a segmented toolbar presented as a popup from the selection itself; Android 4.x uses a horizontal action bar at the top of the screen.
+
+I would recommend going with some sort of horizontal button layout, perhaps as a second layer of toolbar.",1404224198,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-oe5ms72gy2uu6mjaaqe6,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","If I go to a page that has been redirected, the URL retains the original title instead of the redirected title. So if I enter VE and then refresh, I'm taken to the editing the original page instead of the redirect page.
+
+For example, go here: https://en.wikipedia.org/wiki/Zedonk, then click VE, then refresh the page. 
+
+URL should be changed to: https://en.wikipedia.org/wiki/Zebroid?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1404163440,PHID-USER-flenunkasbjk4topxvaj,False,PHID-TASK-jggh6lkqz7csocnbz4oo,task_description,declined
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title",That change has been merged and this should therefore be magically fixed. I'd appreciate if someone could verify.,1408570153,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title",Likely to be made WORKSFORME by gerrit 143852 but isn't actually a patch for VE. :-),1404401825,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","Change 143852 had a related patch set uploaded by Bartosz Dziewoński:
+On redirect, actually rewrite page URL to the target one with JavaScript
+
+https://gerrit.wikimedia.org/r/143852",1404383390,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","Note: This doesn't happen on mobile, on refresh user stays on redirect page.",1404165903,PHID-USER-flenunkasbjk4topxvaj,False,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","(In reply to Bartosz Dziewoński from comment #2)
+> (In reply to James Forrester from comment #1)
+> > Ideally MediaWiki's redirects should 307 rather than 200 so we don't have
+> > this problem… :-(
+> 
+> They shouldn't because then you can't show the ""Redirected from"" message
+> without hacks,
+
+I'm aware of that minor impact on users, but that info is normally duplicated by editorial templates anyway on Wikimedia wikis, at least.
+
+> but they probably should update the URL with JavaScript instead.
+
+> Wanna file a bug or that? (I wouldn't be surprised if there was one already.)
+
+Yes, that looks like bug 35045.",1404164118,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","(In reply to James Forrester from comment #1)
+> Ideally MediaWiki's redirects should 307 rather than 200 so we don't have
+> this problem… :-(
+
+They shouldn't because then you can't show the ""Redirected from"" message without hacks, but they probably should update the URL with JavaScript instead. Wanna file a bug or that? (I wouldn't be surprised if there was one already.)",1404163917,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+"VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title","Rewriting the URL is a bit evil, but if we don't we have the issue of users having a URL they can't share/reload without the context changing.
+
+Ideally MediaWiki's redirects should 307 rather than 200 so we don't have this problem… :-(",1404163827,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jggh6lkqz7csocnbz4oo,task_subcomment,NA
+VisualEditor:  Template dialog doesn't display very long template names gracefully,"See https://commons.wikimedia.org/wiki/File:VE_bug-Template_name_overlaps_remove_icon_in_advanced_dialog.png
+
+If the name of the template is very long, then it overlaps with the trashcan icon for removing it.
+
+This may or may not remain a consideration with the upcoming change to labels (instead of icons) and the redesign of all the boxes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1404014220,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-c27kk34icz4bpyrlvjpf,task_description,resolved
+VisualEditor:  Template dialog doesn't display very long template names gracefully,This is wrapped correctly now,1412590143,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-c27kk34icz4bpyrlvjpf,task_subcomment,NA
+VisualEditor: resizing audio file causes it to resize 0px dialogs do not report size.,"resize and size reporting issue with audio files
+
+issue is highlighed on https://en.wikipedia.org/wiki/Iceberg
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14397}",1404012180,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-zlieutzkthf2674wairs,task_description,resolved
+VisualEditor: resizing audio file causes it to resize 0px dialogs do not report size.,This no longer happens.,1701963934,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-zlieutzkthf2674wairs,task_subcomment,NA
+VisualEditor: resizing audio file causes it to resize 0px dialogs do not report size.,"197.218 has provided some useful steps for reproduction here:  https://www.mediawiki.org/wiki/Topic:Ttg05p4t0hox34jh
+",1501697887,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zlieutzkthf2674wairs,task_subcomment,NA
+VisualEditor: resizing audio file causes it to resize 0px dialogs do not report size.,"I'm seeing it start off with the 0px size (in the display), and no way to change it.  It seems to save correctly, though.
+
+This problem was reported after this edit was made:  https://en.wikipedia.org/w/index.php?title=Perry_DeAngelis&diff=660113505&oldid=653104203
+
+I cannot re-size the audio box in VisualEditor.  (In the wikitext editor, I can [only] make it smaller than default.)  
+",1430438845,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zlieutzkthf2674wairs,task_subcomment,NA
+VisualEditor: Floating toolbar is mis-aligned in non-HD vector css,"Detached toolbar when floating in non-HD Vector
+
+Works fine when normally placed, but is out by ~ 30px when floating.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14365}",1403981160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g7bdag3ouhcedtw4w7px,task_description,resolved
+VisualEditor: Floating toolbar is mis-aligned in non-HD vector css,Looks like this got fixed two weeks ago.,1405555416,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g7bdag3ouhcedtw4w7px,task_subcomment,NA
+VisualEditor: Floating toolbar is mis-aligned in non-HD vector css,"Created attachment 15773
+Non-detached static toolbar
+
+**Attached**: {F14366}",1403981244,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g7bdag3ouhcedtw4w7px,task_subcomment,NA
+VisualEditor: Merge the inserting and editing media dialogs,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403824980,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_description,resolved
+VisualEditor: Merge the inserting and editing media dialogs,*** Bug 58245 has been marked as a duplicate of this bug. ***,1412590279,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_subcomment,NA
+VisualEditor: Merge the inserting and editing media dialogs,"Change 140813 merged by jenkins-bot:
+Merge Media Edit and Media Insert dialogs
+
+https://gerrit.wikimedia.org/r/140813",1404269588,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_subcomment,NA
+VisualEditor: Merge the inserting and editing media dialogs,"Change 140813 had a related patch set uploaded by Mooeypoo:
+[wip] Merge Media Edit and Media Insert dialogs
+
+https://gerrit.wikimedia.org/r/140813",1403856246,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_subcomment,NA
+VisualEditor: Merge the inserting and editing media dialogs,Once more with feeling.,1403825005,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lfmhdqf2fp3fy5b24chh,task_subcomment,NA
+"VisualEditor:  Can't tab from Caption to Alt text fields in image media dialog box, in Safari only","Steps to reproduce:
+
+1.  Open a page containing an image in Safari.
+
+2.  Open an image in the media dialog box.  The cursor begins in the Caption field (of General settings).
+
+3.  Press tab (to get to the next field).
+
+
+Results:
+
+Nothing happens.  The cursor is stuck in the Caption field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67156",1403810760,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-bd7sldgzh3ssrxvsie4v,task_description,resolved
+"VisualEditor:  Can't tab from Caption to Alt text fields in image media dialog box, in Safari only","Hmm. Will sling into the list, then, but this feels odd…",1404954592,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bd7sldgzh3ssrxvsie4v,task_subcomment,NA
+"VisualEditor:  Can't tab from Caption to Alt text fields in image media dialog box, in Safari only","This works for me at Mediawiki.org (1.24wmf12) but not at the English Wikipedia on Safari 6.1.4 with Mac OS 10.8.5.  
+
+Presumably it will work everywhere after tomorrow's update, so I'm marking it as fixed.",1404954523,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-bd7sldgzh3ssrxvsie4v,task_subcomment,NA
+"VisualEditor:  Can't tab from Caption to Alt text fields in image media dialog box, in Safari only",WFM (Safari 5.1.7 for Windows),1404946411,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-bd7sldgzh3ssrxvsie4v,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"This is related to {T69153}, but specific to Chrome/Safari:
+
+Whatever the dialog box, once you've tabbed through whatever links and buttons are inside that dialog (and on the tab list, which isn't always all of them), then pressing tab takes you outside the dialog box to these items:
+
+1) the browser's URL bar
+2) the main Wikipedia search box 
+3) the Cancel button (on VisualEditor's toolbar)
+4) the Save button (on VisualEditor's toolbar)
+5) the top of the article
+6) the slug at the top of the article, where it gets stuck forever.
+
+and never lets you get back to the dialog box.  This means that if you press tab one time more than you meant to, you cannot use or close the dialog box without taking your hands off the keyboard.
+
+**See Also**: {T69162}",1403808420,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_description,resolved
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 237505 merged by jenkins-bot:
+Re-attempt I31ab2bace4: Try to stop user from tabbing outside of open dialog box
+
+[[https://gerrit.wikimedia.org/r/237505]]",1442834801,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 237480 merged by jenkins-bot:
+Rewrite isFocusableElement for performance and correctness
+
+[[https://gerrit.wikimedia.org/r/237480]]",1442252376,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 237480 had a related patch set uploaded (by Esanders):
+Rewrite isFocusableElement for performance and correctness
+
+[[https://gerrit.wikimedia.org/r/237480]]
+",1441922268,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 237505 had a related patch set uploaded (by Esanders):
+Re-attempt I31ab2bace4: Try to stop user from tabbing outside of open dialog box
+
+[[https://gerrit.wikimedia.org/r/237505]]
+",1441919838,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Turns out that we have a method to find focusable elements now (6ff7e5c7ae384038b314dc90036f0a8468e7e65a), but it's a bit broken (T107343). Let's try to fix it and use it.",1438203848,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Some more notes:
+* The previously suggested focus trap only works for tab, not for shift-tab
+* a focus trap only fixes keyboard navigation, not screenreader accessibility
+** You can use aria-hidden to hide everything outside the dialog, opacity does not hide things....
+
+Suggested reading:
+* http://www.w3.org/TR/wai-aria-practices/#modal_dialog
+* http://www.w3.org/TR/wai-aria-practices/#dialog_modal
+* http://www.w3.org/TR/wai-aria-practices/#dialog_nonmodal
+* http://www.w3.org/TR/wai-aria-practices/#dialog_tooltip
+",1424255489,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Let me add links for jQuery UI's :focusable and :tabbable 
+
+http://api.jqueryui.com/focusable-selector/
+http://api.jqueryui.com/tabbable-selector/",1424250704,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"if jQuery UI can add a selector focusable and 'tabbable' for this. Can't we mix those in ourselves ? We'd have to account for the situation where both jQueryUI and OOjs UI are loaded, but we can do that with prefixes I think...",1424250506,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"The reverted patch did, in fact, do something like that. But we still need to find the place inside the dialog where we want to move the focus, and it used `:focusable` for this.
+
+I did some googling and found http://accessibility.oit.ncsu.edu/training/aria/modal-window/version-2/, which uses `a[href], area[href], input:not([disabled]), select:not([disabled]), textarea:not([disabled]), button:not([disabled]), iframe, object, embed, *[tabindex], *[contenteditable]`. Sadly, I think they're wrong in both using `[disabled]` rather than `:disabled` and not checking `[tabindex='-1']`.
+
+Note also that `:focusable` implied `:visible`, we'd need to add this filter ourselves.",1423342981,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Can we do it using observe and fixup, e.g.  listen to focusin on the body, and if the event originates form outside the dialog, move it back inside the dialog.",1423341758,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Patch was reverted, so what's the status of this? We need to do the same again, but without `:focusable`? 
+
+I looked at the source code and `:focusable` can be reasonably approximated using `input:enabled:not([tabindex='-1']), select:enabled:not([tabindex='-1']), textarea:enabled:not([tabindex='-1']), button:enabled:not([tabindex='-1']), a[href]:not([tabindex='-1']), [tabindex]:not([tabindex='-1'])`, or even just `*:enabled:not([tabindex='-1']), a[href]:not([tabindex='-1']), [tabindex]:not([tabindex='-1'])`. If that's too nasty, then we might also do `[tabindex]:not([tabindex='-1'])` and probably no one will notice the difference (OOUI focusable elements generally have tabindex=0 set, even if that's not strictly necessary).",1423341062,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"The applied patch throws an exception, see gerrit.",1412938656,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,Merged. Hopefully this doesn't break anything else.,1412114329,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 159902 merged by jenkins-bot:
+Try to stop user from tabbing outside of open dialog box
+
+https://gerrit.wikimedia.org/r/159902",1412114245,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Change 159902 had a related patch set uploaded by Alex Monk:
+Try to stop user from tabbing outside of open dialog box
+
+https://gerrit.wikimedia.org/r/159902",1410473896,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"So after some confusion about this I looked into it again, and I believe that there's two issues here:
+* We perhaps shouldn't let tab take the focus out of the dialog box at all
+* Tab definitely should not be getting lost and become unable to return to the dialog
+
+Different browsers appear to do different things:
+* Chrome on Ubuntu lets it out of the dialog, but it properly goes back and doesn't get stuck.
+* Chrome and Safari on Windows just let the tabbing leave the dialog, and then it gets stuck and doesn't return to the beginning of the page
+* Firefox (on Ubuntu or Windows) does not let it out of the dialog",1405558247,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,In that case this feels like an upstream issue,1404994158,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Firefox lets me leave the dialog box, but it eventually tabs back into it.  Safari gets stuck.  I haven't checked Chrome; Safari and Chrome often have the same problems, so it might be anything WebKit/not Mozilla.",1404954736,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"I don't think we do this deliberately. This happens in Chrome for me... Are you sure this is Safari-specific, Sherry?",1404947139,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari,"Krenair, is this something that we do as part of the aria-role stuff (and is it something we should do)?",1404848207,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mawqu55vtwhutyac6fl2,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","When adding a link inside a reference in VisualEditor, if one clicks 'apply' without first clicking outside the link inspector, the link is not added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60837",1403637660,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-juabtt3jtkdtozbvwjyi,task_description,resolved
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)",Спасибо! Happy New Year!,1420072225,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","Being bold and marking as resolved.
+
+С новым годом :)",1420070837,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)",Seems to be fixed to me too - checked in betalabs/test2/production.,1420069952,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","I believe this was fixed when Roan worked on the focus issue with inspectors. I can't reproduce this either, it works as it should now with links and language inspector both.",1420050291,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","Can anybody reproduce this? I can't. Either I misunderstand the description, or it was fixed.",1419721481,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)","Maybe we just need to give the edit box focus when applying changes, like in bug 60837's fix?",1403638221,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-juabtt3jtkdtozbvwjyi,task_subcomment,NA
+VisualEditor: Toolbar is sometimes misaligned and ugly in Safari; corrects itself after interaction,"Misaligned toolbar
+
+The bottom of the bar is too high, the Cancel and Save buttons are at different heights.  
+
+However, I can't reproduce it consistently, and changing the font size caused everything to realign correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14345}",1403548380,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jjbnp6qzxgfufzean2ux,task_description,resolved
+VisualEditor: Toolbar is sometimes misaligned and ugly in Safari; corrects itself after interaction,This seems to have been fixed a long time ago.,1508930094,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-jjbnp6qzxgfufzean2ux,task_subcomment,NA
+VisualEditor: Toolbar is sometimes misaligned and ugly in Safari; corrects itself after interaction,*** Bug 67071 has been marked as a duplicate of this bug. ***,1403734997,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jjbnp6qzxgfufzean2ux,task_subcomment,NA
+VisualEditor: Toolbar is sometimes misaligned and ugly in Safari; corrects itself after interaction,"
+
+*** This bug has been marked as a duplicate of bug 67071 ***",1403700121,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-jjbnp6qzxgfufzean2ux,task_subcomment,NA
+"VisualEditor: Turn structure dropdown into a ""split button"" with ""make bulleted list"" the primary action","A split button consists of a ""command button"" and a ""dropdown button"". These are two separate clickable entities. The command button behaves like a regular toolbar button, but it displays the most recent command the user invoked from the dropdown menu.
+
+It was suggested by User:Theflyer to convert VE's list toolbar button into a split button:
+
+
+> When selecting an item from the menu, like lists, I think the button should be sticky and perform the action that is currently shown rather than requiring two clicks to take an action. The example that brought this to my attention is when creating bullets. The default icon shows a traditional bullet so when I click on that, I expect it to just start a bullet. However, the action I get is to open the menu where I then have to select which bullet list option I would prefer. I think there should be a way to act on the existing icon (and it should change to whatever I had last selected) and also a way to pull down the list if I want to change to a different type of action. This is the way Microsoft Word works. There are two clickable hotspots. Thanks. Don Theflyer (talk) 15:55, 21 June 2014 (UTC)
+
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403417400,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-ad7ys6ayrhumzmd7s5np,task_description,open
+"VisualEditor: Turn structure dropdown into a ""split button"" with ""make bulleted list"" the primary action",">>! In T68940#720833, @TTO wrote:
+> [1] http://tinypic.com/r/52jl7p/8 Sorry, it's a disgusting video hosting site, I hope you can tolerate the advertising!
+
+For future convenience:
+{F27317467}",1543305064,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ad7ys6ayrhumzmd7s5np,task_subcomment,NA
+"VisualEditor: Turn structure dropdown into a ""split button"" with ""make bulleted list"" the primary action","I think you're slightly misunderstanding what is meant by ""split button"". There is no single ""primary action""; see this video [1] for an example of how the command on the ""command button"" part of the split button changes as different options are picked from the dropdown.
+
+[1] http://tinypic.com/r/52jl7p/8 Sorry, it's a disgusting video hosting site, I hope you can tolerate the advertising!",1403694056,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-ad7ys6ayrhumzmd7s5np,task_subcomment,NA
+"VisualEditor: Turn structure dropdown into a ""split button"" with ""make bulleted list"" the primary action","Hmm. Maybe. Is bulleted list the principal structure-action people will take, over ""make blockquote"" or ""indent"" or ""insert table"" or ""insert row"" or…?",1403658694,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ad7ys6ayrhumzmd7s5np,task_subcomment,NA
+VisualEditor: Use comma-separator interface message,"There are a few places where we use the string ', ' but in all of those cases we should really be using the comma-separator message. This requires backfilling comma-separator for standalone OOUI, since we also use commas in VE core and OOUI.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403310780,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6svejr4dlr5a76d65y4o,task_description,resolved
+VisualEditor: Use comma-separator interface message,"Change 174302 merged by jenkins-bot:
+ve.ce.MWTransclusionNode: Replace last use of ', ' in VE-MW with <comma-seperator>
+
+https://gerrit.wikimedia.org/r/174302",1416396118,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6svejr4dlr5a76d65y4o,task_subcomment,NA
+VisualEditor: Use comma-separator interface message,"Change 174302 had a related patch set uploaded by Jforrester:
+ve.ce.MWTransclusionNode: Replace last use of ', ' in VE-MW with <comma-seperator>
+
+https://gerrit.wikimedia.org/r/174302",1416349471,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6svejr4dlr5a76d65y4o,task_subcomment,NA
+VisualEditor: Use comma-separator interface message,...but it gets converted. Hm.,1403628331,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6svejr4dlr5a76d65y4o,task_subcomment,NA
+VisualEditor: Use comma-separator interface message,The MW message includes HTML. Ew.,1403628205,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6svejr4dlr5a76d65y4o,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Right now we have things like mw.Title.newFromText( template ); , while really that should use something like mw.Title.newFromText( template, 10 ); or whatever. This is probably fine in practice, but theoretically matters is NS_MAIN and NS_TEMPLATE have different capitalization settings.
+
+We also currently render the titles of {{foo}} (which points to Template:Foo, renders as Foo) and {{:foo}} (which points to Foo, also renders as Foo) the same, we should fix that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403310360,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zq64ne5etzq4kohyhblm,task_description,resolved
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"(In reply to Roan Kattouw from comment #3)
+> (In reply to Roan Kattouw from comment #0)
+> > Right now we have things like mw.Title.newFromText( template ); , while
+> > really that should use something like mw.Title.newFromText( template, 10 );
+> > or whatever. This is probably fine in practice, but theoretically matters is
+> > NS_MAIN and NS_TEMPLATE have different capitalization settings.
+> > 
+> This is not fixed yet, reopening.
+> 
+Somewhat to my surprise this is in fact fully fixed in https://gerrit.wikimedia.org/r/143685",1404350702,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Change 143685 merged by jenkins-bot:
+Try some more to handle template namespace properly
+
+https://gerrit.wikimedia.org/r/143685",1404350631,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Change 143685 had a related patch set uploaded by Catrope:
+Try some more to handle template namespace properly
+
+https://gerrit.wikimedia.org/r/143685",1404350404,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"(In reply to Roan Kattouw from comment #0)
+> Right now we have things like mw.Title.newFromText( template ); , while
+> really that should use something like mw.Title.newFromText( template, 10 );
+> or whatever. This is probably fine in practice, but theoretically matters is
+> NS_MAIN and NS_TEMPLATE have different capitalization settings.
+> 
+This is not fixed yet, reopening.
+
+> We also currently render the titles of {{foo}} (which points to
+> Template:Foo, renders as Foo) and {{:foo}} (which points to Foo, also
+> renders as Foo) the same, we should fix that.
+This was indeed fixed by https://gerrit.wikimedia.org/r/141082",1404350281,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Change 141082 merged by jenkins-bot:
+Normalize titles in template descriptions in context menu
+
+https://gerrit.wikimedia.org/r/141082",1403730637,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace,"Change 141082 had a related patch set uploaded by Jforrester:
+Normalize titles in template descriptions in context menu
+
+https://gerrit.wikimedia.org/r/141082",1403314162,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zq64ne5etzq4kohyhblm,task_subcomment,NA
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a svg image with large size 
+(I found this issue with this image: https://test2.wikipedia.org/wiki/File:MO-123.svg, which has full size of 2,543 × 2,160 pixels.
+I tried with svg images of upto 2000 x 2000 pixels, but could not reproduce for them.)
+
+3.Go to Media Settings tab of this image and go to Advanced Settings
+4.Click on Make full size (it wont try to make it full size which is another bug)
+5.Now again click on Make full size
+
+Observed Result:
+It changes the size values to the full size of the images but it also says ""Size values are invalid""
+
+Page:https://test2.wikipedia.org/wiki/19thjanFF?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403223600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-axpv35jfsr4hb5ftvtac,task_description,resolved
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""",Verified the fix in production,1405035015,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-axpv35jfsr4hb5ftvtac,task_subcomment,NA
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""",Verified the fix in Betalabs,1403908612,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-axpv35jfsr4hb5ftvtac,task_subcomment,NA
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""","Change 142380 merged by jenkins-bot:
+Unimplement wgSVGMaxSize
+
+https://gerrit.wikimedia.org/r/142380",1403822223,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-axpv35jfsr4hb5ftvtac,task_subcomment,NA
+"VisualEditor: For large SVG images while trying to make it full size, it says ""Size values are invalid""","Change 142380 had a related patch set uploaded by Mooeypoo:
+Unimplement wgSVGMaxSize
+
+https://gerrit.wikimedia.org/r/142380",1403812565,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-axpv35jfsr4hb5ftvtac,task_subcomment,NA
+mediawiki.feedback: The 'submit feedback' form does not add the feedback page to the user's watchlist,"Users who submit feedback through the in-VisualEditor form may not see any responses to their feedback because the page is not added to their watchlists, and there's no option to add it.
+
+This feature comes from the `mediawiki.feedback` module in MediaWiki core.",1403195700,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rw3z2ncxhjiapf53g2dj,task_description,resolved
+mediawiki.feedback: The 'submit feedback' form does not add the feedback page to the user's watchlist,"I don't think most contributors would know to go to their watchlist to see if their feedback got a response. It's perhaps better than nothing, though, so it's certainly an understandable fallback strategy for the more experienced user. And if the feedback page is wikitext, then it would presumably have to watch the whole page and thus still not be a very good user experience.
+
+This was filed in 2014 and in the meanwhile we do have Echo notifications enabled by default. This means if the reply to the person's feedback @-mentions their name, they will be notified automatically today already.
+
+Another thing we gained is Flow being deployed and used for most of these feedback pages afaik. And from a quick look in the Flow/MessagePoster plugin (used by mediawiki.feedback), new topics that are created are by default immediately watched by the current user.
+
+Tentatively marking this as resolved.
+
+Perhaps that's an adequate solution for now?",1586711588,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-rw3z2ncxhjiapf53g2dj,task_subcomment,NA
+mediawiki.feedback: The 'submit feedback' form does not add the feedback page to the user's watchlist,"This is pretty irritating. Not sure whether it should just respect the users' default wishes, actively add the page anyway, or give an option…",1403195859,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rw3z2ncxhjiapf53g2dj,task_subcomment,NA
+Strip initial and trailing <br>s out of section headings,"https://en.wikipedia.org/w/index.php?diff=612724427&oldid=612719708 added an invalid section heading:
+
+===== <br>
+Buses =====
+
+
+VisualEditor should always strip <br> out of section headings.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403195100,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-tx3tnhbz5553iuofuywl,task_description,resolved
+Strip initial and trailing <br>s out of section headings,Should now be fixed thanks to the Parsoid munging magic.,1437698410,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tx3tnhbz5553iuofuywl,task_subcomment,NA
+Strip initial and trailing <br>s out of section headings,I can't reproduce…,1434493143,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tx3tnhbz5553iuofuywl,task_subcomment,NA
+Strip initial and trailing <br>s out of section headings,This is still happening: https://en.wikipedia.org/wiki/Special:Diff/655367592,1428429209,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-tx3tnhbz5553iuofuywl,task_subcomment,NA
+VisualEditor:  Clear the 'search memory' after making a link,"Steps to reproduce:
+
+1.  Open a page in VisualEditor and make a link:  [[Foo]].  Easy, right?  Select text, press Command–K, and hit return twice.  You know the page exists under that name and that it doesn't need to be piped, so you don't even need to wait for the link inspector to get the information back from search.
+
+2.  Make another link the same way, but to a different page:  [[Bar]].
+
+3.  Why does VisualEditor offer to point that second link to [[Foo]]?
+
+
+Steps to avoid this problem:
+
+1.  Open a page in VisualEditor and make a link:  [[Foo]].
+
+2.  Start to make another link to a different page ([[Bar]]), but after you've opened the link inspector, just stop and wait and wait and wait.
+
+3.  Ah, it's finally figured out that [[Bar]] is not [[Foo]] and stopped trying to tell me that I want to link this to [[Foo]].  *Now* you can hit return twice and go on with your editing.
+
+
+Can we make VisualEditor ""forget"" the search results in between attempts to link pages?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403144040,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-2rmkxa2is7nps4mba7xt,task_description,resolved
+VisualEditor:  Clear the 'search memory' after making a link,This is now fixed with the changed way that the search interface triggers on link creation (and about a dozen other minor changes). So… yay?,1403144528,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2rmkxa2is7nps4mba7xt,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"In advance of rewriting the skins system, MediaWiki 1.24 introduces a mediawiki.skinning.content.parsoid module which is a dependency of VisualEditor master.
+
+Making it so that downstream users can use newer versions of VisualEditor but not bleeding-edge MediaWiki would be a nice improvement for them, especially for LTS versions.
+
+However, we may want to have it settle down a bit more until now?
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: enhancement",1403122680,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rvudp57rsxh5tyqambv6,task_description,declined
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"This is going nowhere, and REL1_23 is EOL within the next two months. There's little point putting any effort into this",1489977944,PHID-USER-6vzzsmi22zem6yttr6vp,True,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"This has been in the ""MediaWiki-Tarball-Backports"" project for over a year now. Suggest we either close as WONTFIX, or someone proposes a way forward.",1450709644,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"Restoring the ""Backport_to_stable?"" flag in Bugzilla by adding this to the MediaWiki-Tarball-Backports project in Phab.",1417060060,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"(In reply to James Forrester from comment #4)
+> There are probably more to come, but this is good enough. Given that 1.23 is
+> LTS, I imagine Mark wants to support VE on it? Confused why he just rejected
+> the backport he requested…
+
+I was going through the backport request queue and didn't see anything to backport.
+
+Replacing the flag and, hopefully, I'll have time later to go through the list of patches.",1412904045,PHID-USER-ogbcrxm45oo3n3xe5q25,True,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"(In reply to Andre Klapper from comment #3)
+> Which specific, identified commits are proposed as backport candidates here?
+
+`git log --oneline resources/src/mediawiki.skinning/content.parsoid.less`:
+
+4ae23e7 Fix Parsoid's span.reference styling to match PHP's output
+5ada680 Remove Parsoid-specific padding and background
+244e1fc Apply bidi styles to references in Parsoid styles
+76a5ea6 Minor: Remove unnecessary @noflip annotation
+9573eb2 Add unfloated thumb styling in Parsoid CSS
+56300b6 Align image frame padding with core
+4f69ebe Tweaks to Parsoid CSS styles for citations.
+6f45ac4 Fix rendering of centered caption-less images
+26a39ec Hide the caption of frameless or inline images in Parsoid HTML
+4fe80f6 Minor: more specific parsoid image styling with child selectors
+a3525f0 Bug 51245: Add auto-numbered link CSS to Parsoid styles
+a6c074a Minor clarification & tweak for Parsoid render testing
+7086dad Bug 66287: Proper caption styling
+99f093a Make sure images that don't have an explicit alignment get aligned right
+e826298 Add border and background styling to the Parsoid styles for images
+295b2dc Followup dd1c7f7fd7: fix LESSification errors in Parsoid styles
+dd1c7f7 Create a version of mediawiki.skinning.content for Parsoid HTML
+
+There are probably more to come, but this is good enough. Given that 1.23 is LTS, I imagine Mark wants to support VE on it? Confused why he just rejected the backport he requested…",1412880759,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"Which specific, identified commits are proposed as backport candidates here?",1412769048,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,"(In reply to Kunal Mehta (Legoktm) from comment #1)
+> Is this still the only thing blocking VE master on 1.23? Or have there been
+> new breaking things since then?
+
+Lots of new breaking things since then, like your patches to make VE use Config, but VE-not-quite-master from a month ago or so probably would be able to go if this stuff was backported to MW REL1_23 (and more importantly, users wouldn't need to install the very confusing Parsoid PHP extension in addition to the Parsoid nodejs service).",1408566225,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there,Is this still the only thing blocking VE master on 1.23? Or have there been new breaking things since then?,1408563679,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-rvudp57rsxh5tyqambv6,task_subcomment,NA
+VisualEditor Mobile: Cursor moving handle (?) doesn't appear in Android,"On mobile devices there's the ""stick"" blinking cursor, and usually also another handle for moving the cursor around more conveniently. I'm not sure what is it called.
+
+I cannot see it in the mobile VE.
+
+I'm using ASUS Transformer with Android 4.2.1.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403098320,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ffq5hsenml5yhfful4jm,task_description,open
+VisualEditor Mobile: Cursor moving handle (?) doesn't appear in Android,"This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592583998,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ffq5hsenml5yhfful4jm,task_subcomment,NA
+VisualEditor Mobile: Cursor moving handle (?) doesn't appear in Android,"The previous comments don't explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status.
+
+//(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}. If this task is stalled on an upstream project, then the #upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task needs retesting, then the #testme tag should be added. If this task is either out of scope and nobody should ever work on this, or nobody else managed to reproduce the problem described in this task, then this task should have the ""Declined"" status.)//",1590761756,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ffq5hsenml5yhfful4jm,task_subcomment,NA
+"VisualEditor Mobile: For the first time in each edit session in Nexus 7 (Android 4.4.2), Link Inspector gets auto-zoomed in, which looks like partial rendering of the UI","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Select a text
+3.Click on the link inspector icon from the toolbar
+
+Observed Result:
+The link inspector appears a bit zoomed, which at first glance made me feel like a failure in rendering the inspector.
+
+See the screeshot attached
+
+Device: Nexus 7(Android 4.4.2)
+Environment:Production (en.wiki) and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13925}",1403051220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rwcczd2xhqirmziyxmyi,task_description,resolved
+"VisualEditor Mobile: For the first time in each edit session in Nexus 7 (Android 4.4.2), Link Inspector gets auto-zoomed in, which looks like partial rendering of the UI","Not happening anymore, tested in test2 and en.wiki.",1430340251,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rwcczd2xhqirmziyxmyi,task_subcomment,NA
+"VisualEditor Mobile: For the first time in each edit session in Nexus 7 (Android 4.4.2), Link Inspector gets auto-zoomed in, which looks like partial rendering of the UI",Needs re-testing.,1430336295,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rwcczd2xhqirmziyxmyi,task_subcomment,NA
+"VisualEditor Mobile: For the first time in each edit session in Nexus 7 (Android 4.4.2), Link Inspector gets auto-zoomed in, which looks like partial rendering of the UI",Maybe don't let users zoom at all?,1404329672,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rwcczd2xhqirmziyxmyi,task_subcomment,NA
+VisualEditor Mobile: Tapping at the end of each link duplicates the preceding link text in Nexus 7 (Android 4.4.2),"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Tap at the end of a link
+
+Observed Result:
+The link gets copied at the position your cursor was on and it will keep continue doing that everytime you place your cursor at the end of extended link.
+
+See the screenshot attached
+
+Device: Nexus 7(Android 4.4.2)
+Environment:Production (en.wiki) and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13918}",1403046960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2jqvp6o5rukgut7ypeps,task_description,declined
+VisualEditor Mobile: Tapping at the end of each link duplicates the preceding link text in Nexus 7 (Android 4.4.2),">>! In T68754#6180057, @Aklapper wrote:
+> 6 years later, is this still an issue? If nobody can reproduce (or nobody has time to reproduce), then this ticket should be closed as 'declined'. Thanks!
+
+Closing this Phabricator task as no further information has been provided.
+If this still happens, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks a lot!",1604273725,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2jqvp6o5rukgut7ypeps,task_subcomment,NA
+VisualEditor Mobile: Tapping at the end of each link duplicates the preceding link text in Nexus 7 (Android 4.4.2),"6 years later, is this still an issue? If nobody can reproduce (or nobody has time to reproduce), then this ticket should be closed as 'declined'. Thanks!",1590943697,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2jqvp6o5rukgut7ypeps,task_subcomment,NA
+VisualEditor Mobile: Tapping at the end of each link duplicates the preceding link text in Nexus 7 (Android 4.4.2),Needs re-testing.,1430336378,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2jqvp6o5rukgut7ypeps,task_subcomment,NA
+Dump the change_tag table,"https://www.mediawiki.org/wiki/Manual:Change_tag_table , no private data involved and very useful for research (public editing patterns of all sorts and now visualeditor, mobile etc.).
+
+On wikitech-l nobody could find a reason not to do it.
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070255.html
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402992420,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-5xjx5bhytilus36xtsqu,task_description,resolved
+Dump the change_tag table,"done, tested, works. closing. ",1443610896,PHID-USER-jtxavgb3caz53o45csni,False,PHID-TASK-5xjx5bhytilus36xtsqu,task_subcomment,NA
+Dump the change_tag table,"Change 242499 merged by ArielGlenn:
+dump change tag table, T68700
+
+[[https://gerrit.wikimedia.org/r/242499]]",1443610070,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5xjx5bhytilus36xtsqu,task_subcomment,NA
+Dump the change_tag table,"Since change tags can now be deleted, I'm moving this along. ",1443606034,PHID-USER-jtxavgb3caz53o45csni,False,PHID-TASK-5xjx5bhytilus36xtsqu,task_subcomment,NA
+Dump the change_tag table,"Change 242499 had a related patch set uploaded (by ArielGlenn):
+dump change tags table, T68700
+
+[[https://gerrit.wikimedia.org/r/242499]]
+",1443606009,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5xjx5bhytilus36xtsqu,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Tap somewhere in the middle of the article
+3.Insert some text
+4.Close the keypad
+5.Now again tap at the end of the text that you typed in
+
+Observed Result:
+The cursor moves to the beginning of the article, not where the user wanted to start his edit.
+
+Device: iPad Mini
+iOS:7.1.1
+Environment:Production and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402962060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oamnqxetj6ams3volnvi,task_description,resolved
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into",Verified the fix in production,1409865559,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into",Verified the fix in test2,1409260518,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","The original issue that cursor jumps to the beginning of the article is resolved, but still remains issue where the page is not actually getting scrolled down to the point where the cursor is currently positioned at.I have filed a different bug on that (https://bugzilla.wikimedia.org/show_bug.cgi?id=70111) as discussed with Roan.",1409181698,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","Change 155839 merged by jenkins-bot:
+Check for selection in ve.ce.Surface#onDocumentFocus
+
+https://gerrit.wikimedia.org/r/155839",1409098207,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","Change 155839 had a related patch set uploaded by JGonera:
+Check for selection in ve.ce.Surface#onDocumentFocus
+
+https://gerrit.wikimedia.org/r/155839",1408746801,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","**jgonera** wrote:
+
+this.dragging is false because onFocusChange is called after onDocumentMouseUp.
+
+The order of events on iOS Safari seems to be fine though:
+
+* mousedown
+* focus
+* mouseup",1408742416,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","**jgonera** wrote:
+
+It's because we call
+
+    this.getModel().selectFirstContentOffset();
+
+in ve.ce.Surface#onDocumentFocus as a workaround for Firefox. I guess we'd want this.dragging to be true when someone taps on a touch device, but it's false instead.",1408740739,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","**jgonera** wrote:
+
+Trying to figure this one out now.
+
+If you set hasFocus to false in ve.ce.Surface#onFocusChange, the problem goes away.
+
+If you already have the fix for bug 68832 [1][2], then this is easier to reproduce because it happens on every tap on the CE.
+
+[1] https://gerrit.wikimedia.org/r/#/c/155678/
+[2] https://gerrit.wikimedia.org/r/#/c/155671/",1408740409,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into","**jgonera** wrote:
+
+Might be related to bug 68832.",1407446825,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into",Might be related to the context being wrong in iOS?,1404329901,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oamnqxetj6ams3volnvi,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","As a logged in user at http://en.m.wikipedia.beta.wmflabs.org/\
+
+With beta setting enabled
+
+Click edit
+
+VE never appears, user sees just a spinner. 
+
+js error is: Uncaught Error: Unknown dependency: jquery.uls.data
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1402677300,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_description,resolved
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever",The error goes away after enabling the 'uls' role in vagrant.,1423616745,PHID-USER-grftjc3ekkyjf6bwlsqi,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever",This is happening to me. I have latest code from master.,1421196859,PHID-USER-grftjc3ekkyjf6bwlsqi,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever",Checked on betalabs and test2 mobile.,1417636413,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","Change 139484 merged by jenkins-bot:
+Add mobile target for modules that VE depends on
+
+https://gerrit.wikimedia.org/r/139484",1402692497,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","Change 139435 merged by jenkins-bot:
+Add targets missing from jquery.i18n libraries
+
+https://gerrit.wikimedia.org/r/139435",1402692446,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","Change 139484 had a related patch set uploaded by JGonera:
+Add mobile target for modules that VE depends on
+
+https://gerrit.wikimedia.org/r/139484",1402692073,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","Change 139435 had a related patch set uploaded by Esanders:
+Add targets missing from jquery.i18n libraries
+
+https://gerrit.wikimedia.org/r/139435",1402682004,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever",Error introduced by I54c0a8e5816a3c81851f95f1d3062a6091a9f4a3 in VisualEditor,1402681583,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+"VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/MuQh23gb",1402677614,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s4yzmexfuvbf2g7dwcux,task_subcomment,NA
+VisualEditor: Typing multiple deadkeys at the end of text expands selection to new line,"**Author:** `oliver.buchtala`
+
+**Description:**
+Put the cursor at the end of a text node and e.g. type ``.
+After short delay the selection expands to the begin of the next node.
+
+This happens for me under OSX Chrome 35 and Safari 7.0 for  VE@356f325ab21731e0aa5c83f90fb4fa037cc60cff.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1402673820,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zvu24wr6gapdwg6aoskt,task_description,open
+VisualEditor: Typing multiple deadkeys at the end of text expands selection to new line,"Confirmed; the re-select happens on master.
+
+When the cursor is at the start or in the middle of a paragraph and the next cursor position is text, nothing odd happens.
+
+When the cursor is at the end of the paragraph (and the next paragraph begins with text or a node), it selects from the end of the paragraph to the start of the next. However, the selection is still n,n – it's not showing as a selection n to n+2 as it is showing.
+
+When the cursor is at the start or in the middle of a paragraph and the next cursor position is a node (e.g. a reference or a link node), the cursor suddenly disappears (but the selection is still n,n).",1404248576,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zvu24wr6gapdwg6aoskt,task_subcomment,NA
+VisualEditor: Typing multiple deadkeys at the end of text expands selection to new line,"**oliver.buchtala** wrote:
+
+Animation showing the issue in Safari
+
+**Attached**: {F14132}",1402673914,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zvu24wr6gapdwg6aoskt,task_subcomment,NA
+"VisualEditor: Gallery and Math inspector closes with an animation from right to left after clicking on ""<"" to close them","Steps to reproduce:
+
+1.Open a page with VE
+2.Open the gallery inspector for an already added gallery or open the math inspector
+3.Close the gallery inspector or math inspector after inserting math function
+
+Observed Result:
+The inspector closes with an animation coming from right to left
+
+Environment:Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60501",1402602720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gbmahf2nvdgcfrdtetva,task_description,resolved
+"VisualEditor: Gallery and Math inspector closes with an animation from right to left after clicking on ""<"" to close them",Fixed in gerrit 139550.,1405375906,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gbmahf2nvdgcfrdtetva,task_subcomment,NA
+"VisualEditor: Gallery and Math inspector closes with an animation from right to left after clicking on ""<"" to close them",This is also on test with wmf9,1402618667,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gbmahf2nvdgcfrdtetva,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"**Author:** `oliver.buchtala`
+
+**Description:**
+Currently, if the menu for a FocusNode gets embedded, this also happens for the Inspector. It would be better to let the Inspector itself decide.
+
+Details:
+
+This gets executed when the menu for a focus node is shown. 'this.embedded' is set according to the size of the focus node:
+
+https://github.com/wikimedia/VisualEditor/blob/356f325ab21731e0aa5c83f90fb4fa037cc60cff/modules/ve/ui/ve.ui.DesktopContext.js#L428-L435
+
+OTOH, when the inspector gets opened, 'this.embedded' is not recomputed:
+
+https://github.com/wikimedia/VisualEditor/blob/356f325ab21731e0aa5c83f90fb4fa037cc60cff/modules/ve/ui/ve.ui.DesktopContext.js#L420-L425
+
+This has the consequence that the inspector is rendered over the focussed node.
+IMO, at least the same embedded check should be done in the 'inspector' case.
+Also the tail should be enabled accordingly.
+
+To leave the inspector implementation even more control I would suggest to add something like this to the Inspector interface:
+
+/**
+ * @returns {boolean}
+ */
+Inspector.prototype.isEmbedded = function() {};
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402596900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_description,resolved
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Change 155704 merged by jenkins-bot:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/155704",1408727876,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Change 155704 had a related patch set uploaded by Esanders:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/155704",1408711057,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,Regressed.,1408710970,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,*** Bug 67306 has been marked as a duplicate of this bug. ***,1408710950,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Change 143393 merged by jenkins-bot:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/143393",1404247817,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Change 143393 had a related patch set uploaded by Jforrester:
+Never embed the context when an inspector is present
+
+https://gerrit.wikimedia.org/r/143393",1404246534,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"[Bah]
+
+(In reply to James Forrester from comment #4)
+> Sorry for the slow triage here; between this and bug 67306 we think it'd be
+> best to actively prevent the context menu from showing over an item that is
+> inspectable (rather than just have it be a configuration), so I'm going to
+> mark this one as the primary and the other as
+
+… as possibly a WONTFIX, rather than leave it be.",1404246505,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"Sorry for the slow triage here; between this and bug 67306 we think it'd be best to actively prevent the context menu from showing over an item that is inspectable (rather than just have it be a configuration), so I'm going to mark this one as the primary and the other as",1404246476,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"**oliver.buchtala** wrote:
+
+
+(In reply to Oliver Buchtala from comment #2)
+
+> https://github.com/oliver----/VisualEditor/commit/
+> 26baf0bf57fb3fb23ce7ae5971b25f29ac8182db
+Sorry, this link was wrong.
+
+https://github.com/oliver----/VisualEditor/commit/8c0e5acb6df5bc104165e9fbbf3f9b9959f89135",1402599525,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"**oliver.buchtala** wrote:
+
+(In reply to Oliver Buchtala from comment #1)
+
+Maybe it could look like this:
+
+https://github.com/oliver----/VisualEditor/commit/26baf0bf57fb3fb23ce7ae5971b25f29ac8182db",1402599219,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases,"**oliver.buchtala** wrote:
+
+... or better:
+
+/**
+ * @returns {boolean}
+ */
+Inspector.prototype.isEmbeddable = function() {
+  return true;
+};
+
+A custom inspector can then override this to avoid embedding and existing implementations would not be influenced.",1402597991,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2c2kd5h5swrnoe5i4rnh,task_subcomment,NA
+VisualEditor: Creating a new page shows footer above the article,"Screencast of the behaviour.
+
+When I create a new article on Swedish Wikipedia with VE, the page footer is displayed above the cursor but below the title (se attached ogv).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13951}",1402561200,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-rchunvbnr26iqkmvxxy5,task_description,resolved
+VisualEditor: Creating a new page shows footer above the article,"This isn't happening any more, so I guess it was fixed at some point during the last three years.",1516116364,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-rchunvbnr26iqkmvxxy5,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Insert another image inside the caption of it.
+4.Select the image and observe the position of the context menu that appears on top of the image
+
+Observed Result:
+The context menu's position is shifted few pixels to the right.
+See the screenshot to compare the position of it .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13897}",1402515000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-flp4acupxj7fjvq4mgfw,task_description,resolved
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,Verified the fix in production,1405027609,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,Verified the fix in Betalabs and test2,1404771014,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,"Change 142797 merged by jenkins-bot:
+Add a ve direction class to all surfaces
+
+https://gerrit.wikimedia.org/r/142797",1403990446,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,"Change 142797 had a related patch set uploaded by Esanders:
+Add a ve direction class to all surfaces
+
+https://gerrit.wikimedia.org/r/142797",1403960368,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,But not for me (though the highlight is correctly aligned now).,1403713121,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,"Created attachment 15743
+Demonstration in Beta Labs
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox&oldid=108546&veaction=edit
+
+**Attached**: {F13898}",1403713110,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield,WFM in beta labs,1403709860,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-flp4acupxj7fjvq4mgfw,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","There is a difference in behavior between explicitly stating ""none"" in the image wikitext and setting no alignment (which is usually default) This difference is especially complicated when we're dealing with switching between block to inline, as inline images basic/frameless have no initial alignment (attrs.align = undefined) but if an alignment is chosen in basic/frameless they turn into blocks.
+
+There is no real way to choose ""none"" alignment for inline blocks with our current GUI.
+
+You can see the outcome and differences between default/no alignment to 'none' and other alignments in each of the different image types in this table:
+https://www.mediawiki.org/wiki/User:Mooeypoo/VE_ImageAlignment
+
+
+I've tried to explore what other programs do in this case, but there doesn't seem to be a good analogy for the difference between having 'float' value and not having a float value while mixing block with inline. 
+
+In Microsoft Word 2013, images are inserted as block image with default alignment that is the direction of the text (left for ltr, right for rtl) *BUT* without text wrapping - so no float. You can change the image to inline (""In Line with Text"") or to be wrapped (""With Text Wrapping"") but the wrapping options are limited to how close the text is around the image; the user is then allowed to manually drag the image wherever they want ti to be (no actual 'left' / 'center' / 'right')
+
+We should find a working solution to let users decide between having 'none' alignment explicitly while still having the default value available for both inline and block images.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1402440600,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-iqulbj2ddfudaregj3jn,task_description,open
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","The comparison to wikitext functionality should be something like:
+* In line: frameless/basic without alignment
+* Wrap text: thumb/frame/frameless/basic with explicit right/left alignment
+* Break line: thumb/frame/frameless/basic with either ""center"" or ""none"" alignments. No float, no text wrap.
+
+The only problem in that case would be to adjust the fine print of the behavior, but in general terms it would be more or less consistent to the user.",1402468268,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","(In reply to Moriel Schottlender from comment #6)
+> Interestingly enough, in Google Docs you seem to have three main alignment
+> options:
+> 
+> * In line - an inline image
+> * Wrap text - Block image with floating, you can then drag/drop it either
+> left, center or right in the text and choose how small the margin to the
+> text is.
+> * Break text - this is just like our ""none"" option, it's an image in its own
+> line that is automatically aligned to the text (so, left in LTR)
+> 
+> The functionality (drag/drog) and some options aren't all relevant, but
+> maybe we could get some ideas from the naming of the features.
+
+Dragging to the left/right/centre actually could be really nice, but we'd probably want both that and a way to set it in the dialog I think.
+
+""Inline"" vs. ""Break text"" vs. ""Wrap text"" seems reasonable language…",1402446964,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Interestingly enough, in Google Docs you seem to have three main alignment options:
+
+* In line - an inline image
+* Wrap text - Block image with floating, you can then drag/drop it either left, center or right in the text and choose how small the margin to the text is.
+* Break text - this is just like our ""none"" option, it's an image in its own line that is automatically aligned to the text (so, left in LTR)
+
+The functionality (drag/drog) and some options aren't all relevant, but maybe we could get some ideas from the naming of the features.",1402442352,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15627
+Image alignment in Google Docs
+
+**Attached**: {F13814}",1402442206,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15626
+Word 2013 image wrap text menu
+
+**Attached**: {F13813}",1402441159,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15625
+Word 2013 image position menu
+
+**Attached**: {F13811}",1402441084,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15624
+Word 2013 image popup menu
+
+**Attached**: {F13810}",1402441065,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Design a good solution for image alignment ""none"" vs ""default""","Created attachment 15623
+Word 2013 image alignment menu
+
+**Attached**: {F13809}",1402441044,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-iqulbj2ddfudaregj3jn,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Image
+2.Open the Media Settings dialog
+3.Now quickly double click on Apply changes Button
+
+Observed Result:
+An error appears in the console:
+
+Uncaught TypeError: Cannot read property 'getSurface' of null
+Media Settings dialog for that image and all other images on that page becomes unresponsive.
+
+This is happening in Betalabs and test , not on production(en.wiki)
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13637}",1402341840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_description,resolved
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","**Coiby.Xu** wrote:
+
+(In reply to Roan Kattouw from comment #10)
+> Right, ActionDialog.js was introduced after the 1.23 release. I thought this
+> bug was introduced after the 1.23 release though, so I'm surprised to hear
+> it's breaking for you.
+
+So will the development team resolve this bug for 1.23?",1407980375,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","Right, ActionDialog.js was introduced after the 1.23 release. I thought this bug was introduced after the 1.23 release though, so I'm surprised to hear it's breaking for you.",1407896547,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","**Coiby.Xu** wrote:
+
+Sorry, it's typo. I mean .js.
+
+There are two files related to Media Seetings dialogue, ve.ui.MWMediaInsertDialog.js and ve.ui.MWMediaEditDialog.js. There's no ve.ui.ActionDialog.js.",1407896395,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","(In reply to Coiby from comment #7)
+> (In reply to Coiby from comment #6)
+> > This problem still exist on snapshot 9883566
+> > (https://extdist.wmflabs.org/dist/VisualEditor-REL1_23-9883566.tar.gz).
+> 
+> I just look through the patch, I can't find such file
+> ve/ui/dialogs/ve.ui.ActionDialog.json in snapshot 9883566.
+
+.js , not .json . Also, try looking for lib/ve/modules/ve/ui/dialogs/ve.ui.ActionDialog.js",1407896131,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","**Coiby.Xu** wrote:
+
+(In reply to Coiby from comment #6)
+> This problem still exist on snapshot 9883566
+> (https://extdist.wmflabs.org/dist/VisualEditor-REL1_23-9883566.tar.gz).
+
+I just look through the patch, I can't find such file ve/ui/dialogs/ve.ui.ActionDialog.json in snapshot 9883566.",1407896012,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","**Coiby.Xu** wrote:
+
+This problem still exist on snapshot 9883566 (https://extdist.wmflabs.org/dist/VisualEditor-REL1_23-9883566.tar.gz).",1407895586,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that",Verified the fix in production (en.wiki),1403302531,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that",Verified the fix on test2,1402690444,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that",Verified the fix on Betalabs,1402595814,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","Change 139019 merged by jenkins-bot:
+Re-enable apply button in action dialog on close
+
+https://gerrit.wikimedia.org/r/139019",1402526941,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: Quickly clicking on ""Apply Changes"" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that","Change 139019 had a related patch set uploaded by Trevor Parscal:
+Re-enable apply button in action dialog on close
+
+https://gerrit.wikimedia.org/r/139019",1402526679,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3gju4wuwcydtmtdjrzrr,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","To reproduce:
+1. Edit an article in Arabic.
+2. Move the caret forward using the arrow keys.
+
+Observed: The Arabic letters next to which the caret moves are disconnected.
+
+Expected: Moving the caret must only move the caret. It must not change the appearance of the text.
+
+This works well in Firefox, but broken in Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402213980,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-yw4b4pmbrw2obgk33kph,task_description,resolved
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","I cannot reproduce it in recent versions of Safari, Chrome and Firefox.",1420878426,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","(In reply to Amir E. Aharoni from comment #3)
+> Well, I reported it, and I only have Chrome on Linux, so I guess I meant
+> ""Chrome"" or ""Blink"" and not ""WebKit"".
+
+If it was present in Chrome at that point in time though, depending on whether it was a recent regression in Chrome, it likely still exists in WebKit/Safari (since Blink is a fork of WebKit).",1409147282,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","Well, I reported it, and I only have Chrome on Linux, so I guess I meant ""Chrome"" or ""Blink"" and not ""WebKit"".",1409147088,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","Be sure to also test in a recent version of Safari (which runs on WebKit).
+
+Chrome hasn't been based on WebKit for almost 2 years now. It's using Chromium/Blink instead.",1409146973,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+"VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters","I am not sure what fixed it, but it works for me now in Chrome 36.0.1985.143 on Fedora 20.
+
+Can this be tested automatically to prevent regression?",1409146067,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-yw4b4pmbrw2obgk33kph,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE in test2
+2.Insert an image
+3.Change the image type to Frameless/Basic
+4.Now observe the checkbox for wrap is now unchecked
+5.Try to check the checkbox
+
+Observed Result:
+It does not check the checkbox , but all the alignment tabs becomes visible .
+
+This is happening in test2 only,
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14010}",1402096260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_description,resolved
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,Verified the fix in production (en.wiki),1403301056,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,Verified the fix in test2 running wmf9,1402696567,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"Change 138122 merged by jenkins-bot:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/138122",1402105349,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,This makes for a confusing bug history. :-),1402102858,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"Change 138122 had a related patch set uploaded by Jforrester:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/138122",1402102769,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"The patchset that fixed the wrapping textbox was merged yesterday evening. That might explain the inconsistency; it's not in mw and test2 yet.
+
+https://gerrit.wikimedia.org/r/#/c/137524/
+
+If this isn't happening in beta labs, it should show the patchset fixed the bug. (Correct me if I'm wrong?)",1402098589,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"Yes, it is also in MW.org , but not on Betalabs , not on en.wiki.
+
+So, its in wmf 8, not on wmf 7 and wmf 9",1402097353,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic,"This is happening in test2 and other wmf8 sites (like MW.org) but not wmf7s and Beta Labs, or just test2?",1402096999,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ac2zsjomwjgmhkoayiuf,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Initially the image is Thumbnail-right
+4.Now change the image type to Basic-Right-Border
+5.Apply changes
+6.Save the page
+7.Reopen the image
+8.Try to open the media settings dialog for the image
+
+Observed Result:
+Caption field is missing in the Media Settings dialog and cannot close the media settings dialog for the image.
+
+The following error appears in the console:
+
+TypeError: node is null appears in the console 
+
+This is happening in en.wiki and betalabs but not for some reason in test2
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13991}",1402092600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-otgwycebw25ej3on4cg6,task_description,resolved
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,Verified the fix in en.wiki running wmf 8,1402684839,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,"OK, let's declare this one fixed in wmf8. :-)",1402427523,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,"This is no more reproducible in Betalabs and test2 , but only on en.wiki",1402427465,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,"I can't manage to reproduce this bug in master on both Firefox and Chrome.
+
+Did this happen again?",1402426859,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session,Try the image on this page to reproduce: https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1402092670,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-otgwycebw25ej3on4cg6,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"If the alignment of an image is not explicitly set, Parsoid does not output an alignment class for the resultant figure element. This can lead to the image not being aligned/floated.
+
+We need to modify content.parsoid.less to apply the default right-alignment styling to all images and then override this in cases where the alignment is explicitly set.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: normal",1402089360,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_description,resolved
+Default image alignment is not applied to parsoid-output figure elements,Seems like it must be fixed to me as of @Aklapper comment. @Gwicke correct me if wrong.,1446511244,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"(In reply to Gabriel Wicke from comment #5)
+> Right now this is deployed to group 1 wikis, but not yet to group 2. Lets
+> keep this open until it has made its way there.
+
+gwicke: So can this ticket be closed as FIXED?",1416053543,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"Right now this is deployed to group 1 wikis, but not yet to group 2. Lets keep this open until it has made its way there.
+
+Also see tracking bug 51245 for more Parsoid-specifc CSS tweaking.",1402934215,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,*** Bug 66668 has been marked as a duplicate of this bug. ***,1402934098,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"Change 138106 merged by jenkins-bot:
+Make sure images are properly aligned in Mobile VisualEditor
+
+https://gerrit.wikimedia.org/r/138106",1402353105,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"Change 138106 had a related patch set uploaded by Kaldari:
+Make sure images are properly aligned in Mobile VisualEditor
+
+https://gerrit.wikimedia.org/r/138106",1402096895,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+Default image alignment is not applied to parsoid-output figure elements,"Change 138038 had a related patch set uploaded by Kaldari:
+Make sure images that don't have an explicit alignment get aligned right
+
+https://gerrit.wikimedia.org/r/138038",1402089519,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yhsvhbgjvy4nwgcogikw,task_subcomment,NA
+VisualEditor: vesection not removed on save/cancel,"veaction is removed on save, but not vesection.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1402021260,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-3y4bzefvz74zyiylvmg7,task_description,resolved
+VisualEditor: vesection not removed on save/cancel,"Change 145277 merged by jenkins-bot:
+mw.ViewPageTarget: Remove vesection from URL on save/cancel
+
+https://gerrit.wikimedia.org/r/145277",1405001089,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3y4bzefvz74zyiylvmg7,task_subcomment,NA
+VisualEditor: vesection not removed on save/cancel,"Change 145277 had a related patch set uploaded by Alex Monk:
+Remove vesection from URL on save/cancel
+
+https://gerrit.wikimedia.org/r/145277",1404994761,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3y4bzefvz74zyiylvmg7,task_subcomment,NA
+VisualEditor: vesection not removed on save/cancel,Same for cancel.,1404937090,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-3y4bzefvz74zyiylvmg7,task_subcomment,NA
+VisualEditor:  Some images not displayed in the correct place ? due to floating,"Where the image was displayed before saving
+
+Steps to reproduce:
+
+1.  Open an article with a lot of images.  I started with https://en.wikipedia.org/w/index.php?title=Candy&oldid=611646505
+
+2.  Pick a right-aligned image and switch it to left-aligned.
+
+3.  Think, ""That's weird:  it seems to have put it in the middle of a paragraph or something"".
+
+4.  Drag the image to a more appropriate location.
+
+5.  Think, ""Hey, I put it up there, so why is it all the way down there?""
+
+
+NB that the diff here:  https://en.wikipedia.org/w/index.php?title=Candy&diff=611749324&oldid=611748715
+also places the image in between the text and the invisible {{anchor}} template that ought to be attached to the text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62850
+
+**Attached**: {F13861}",1402010880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-kcdt6evoxb7dyclasvhr,task_description,open
+VisualEditor:  Some images not displayed in the correct place ? due to floating,"Created attachment 15579
+Where the image was (correctly) displayed after saving
+
+**Attached**: {F13862}",1402010936,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-kcdt6evoxb7dyclasvhr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"Similar to how we have ve.batchSplice for splice.apply
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401993060,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nq5cnmniruskng2atihr,task_description,resolved
+VisualEditor: Replace uses of push.apply with something safe,"Change 166799 merged by jenkins-bot:
+Replacing push.apply in VE-MW with ve.batchPush from VE core
+
+https://gerrit.wikimedia.org/r/166799",1413481493,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"(In reply to Roan Kattouw from comment #5)
+> (In reply to James Forrester from comment #4)
+> > VE-MW patch coming or not needed?
+> 
+> There are two usages in VE-MW that do need to be cleaned up. Now that 166790
+> was pulled through into VE-MW (a few minutes ago) that can be done.
+
+Ugh somehow we missed the fact that there was a patch for this that was submitted three hours ago. We're both blind :S",1413413103,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"(In reply to James Forrester from comment #4)
+> VE-MW patch coming or not needed?
+
+There are two usages in VE-MW that do need to be cleaned up. Now that 166790 was pulled through into VE-MW (a few minutes ago) that can be done.",1413411436,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,VE-MW patch coming or not needed?,1413411219,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"Change 166790 merged by jenkins-bot:
+Replacing push.apply with newly created ve.batchPush in VE core
+
+https://gerrit.wikimedia.org/r/166790",1413400701,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"Change 166799 had a related patch set uploaded by SuchetaG:
+Replacing push.apply in VE-MW with ve.batchPush from VE core
+
+https://gerrit.wikimedia.org/r/166799",1413400657,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Replace uses of push.apply with something safe,"Change 166790 had a related patch set uploaded by SuchetaG:
+Replacing push.apply with newly created ve.batchPush in VE core
+
+https://gerrit.wikimedia.org/r/166790",1413398862,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nq5cnmniruskng2atihr,task_subcomment,NA
+VisualEditor: Link inspector should catch 400 errors from sending overly-long queries to the API,"This results in a quite bad outcome for the user, totally inexplicably. Instead we should just catch these errors and state them as invalid links (or have a different message?).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66135",1401914520,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3c2zptsonkrp7vi7nbpx,task_description,resolved
+VisualEditor: Link inspector should catch 400 errors from sending overly-long queries to the API,"Change 138016 merged by jenkins-bot:
+Don't send invalid titles from the link inspector to the API
+
+https://gerrit.wikimedia.org/r/138016",1402102914,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3c2zptsonkrp7vi7nbpx,task_subcomment,NA
+VisualEditor: Link inspector should catch 400 errors from sending overly-long queries to the API,"Change 138016 had a related patch set uploaded by Alex Monk:
+Don't sent invalid titles from the link inspector to the API
+
+https://gerrit.wikimedia.org/r/138016",1402085857,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3c2zptsonkrp7vi7nbpx,task_subcomment,NA
+VisualEditor: Link inspector should catch 400 errors from sending overly-long queries to the API,Gerrit change 138016 should make it so that these show invalid title warnings. Though I haven't got CirrusSearch installed on my dev wiki so haven't tested it against the request_too_long Cirrus error.,1402085842,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-3c2zptsonkrp7vi7nbpx,task_subcomment,NA
+VisualEditor: Create distribution files for VE core,"OOJS(UI) has a build script which creates a dist folder with concatenated JS/CSS and copied images and i18n files. VE should have the same so that:
+
+* We avoid IE9 stylesheet limits (31 files, 4096 rules)
+* We can create an RTL stylesheet using Janus.
+* We can embed small images inside the stylesheets.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401887280,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5pgxr7pnqmtyrolp2ztp,task_description,resolved
+VisualEditor: Create distribution files for VE core,"Change 137367 merged by jenkins-bot:
+Grunt: Create a distribution files for the ve module
+
+https://gerrit.wikimedia.org/r/137367",1404270407,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5pgxr7pnqmtyrolp2ztp,task_subcomment,NA
+VisualEditor: Create distribution files for VE core,"Change 137367 had a related patch set uploaded by Jforrester:
+Grunt: Create a single file stand-alone distribution for demos etc.
+
+https://gerrit.wikimedia.org/r/137367",1401905976,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5pgxr7pnqmtyrolp2ztp,task_subcomment,NA
+"VisualEditor: For all drop down boxes, the first match with check mark and highlight, loses it highlight upon hovering over it and then moving mouse out of the object","Screenshot
+
+Steps to reprduce:
+
+1.Open VE
+2.Open any drop down box that comes up with a list of matching suggestions:for example:Link inspector, Category editor, template etc.
+3.Type something in the text box
+4.When the matching suggestions appear in the drop down box,observe that the first match which has a check mark next to it, is highlighted
+5.Now mouse over that match in the drop down and 
+
+Observed Result:
+The selection loses it highlight
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13596}",1401841740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6xolie2zefzogwp7ndhu,task_description,resolved
+"VisualEditor: For all drop down boxes, the first match with check mark and highlight, loses it highlight upon hovering over it and then moving mouse out of the object",Appears to have been fixed.,1402921830,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6xolie2zefzogwp7ndhu,task_subcomment,NA
+"VisualEditor: For all drop down boxes, the first match with check mark and highlight, loses it highlight upon hovering over it and then moving mouse out of the object",Not a shield issue.,1402921809,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6xolie2zefzogwp7ndhu,task_subcomment,NA
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again","Screenshot
+
+Steps to reproduce:
+
+
+1.Open VE
+2.Go to Page options>Categories
+3.Insert a new category:Ca, it appears under matching categories section according to the change on https://bugzilla.wikimedia.org/show_bug.cgi?id=49044
+4.Select the first match Ca
+4.Now again type Ca
+
+Observed Result:
+This time it appears under New Category section.
+
+
+see the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13594}",1401840480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v376iz64hfsix2c3s4lh,task_description,resolved
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again",Verified the fix in en.wiki running wmf 8,1402688290,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-v376iz64hfsix2c3s4lh,task_subcomment,NA
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again","Fixed. That function is full of horrible things to do with following redirects (where a supposed category is actually a redirect to another category) and categories which are marked as hidden, mostly my fault and probably full of bugs if you want to poke around with that. Particularly in cases where we're supposed to exclude suggestions due to already having the suggestion on the list.",1401920048,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-v376iz64hfsix2c3s4lh,task_subcomment,NA
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again","Change 137307 merged by jenkins-bot:
+Check last existing category for whether or not we're trying to re-add it
+
+https://gerrit.wikimedia.org/r/137307",1401919823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v376iz64hfsix2c3s4lh,task_subcomment,NA
+"VisualEditor: If you have added a category already, typing it in a second time doesn't show it in the list — except if the category is a ""red link"", in which case it will suggest it as a new one again","Change 137307 had a related patch set uploaded by Alex Monk:
+Check last existing category for whether or not we're trying to re-add it
+
+https://gerrit.wikimedia.org/r/137307",1401889985,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v376iz64hfsix2c3s4lh,task_subcomment,NA
+VisualEditor: Issues with shields/highlights/phantoms (tracking),"This is a tracking bug for all shields/highlights/phantoms related issues.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401819000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p7uyyr5xswg5yrofkqdd,task_description,declined
+VisualEditor: Issues with shields/highlights/phantoms (tracking),Tracking bug with no outstanding blockers. Closing.,1411510006,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p7uyyr5xswg5yrofkqdd,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"This is overdue.
+
+Various packages used by individual Grunt tasks used by local projects already throw warnings for the engine being unsupported.
+
+These are not the packages for the legacy global tools in package.json in integration/jenkins.git:/tools aka slave-scripts, but the local package.json in projects like oojs, oojs-ui and VisualEditor.
+
+As far as I can see these jobs seem to function fine, but it's really dangerous territory. The packages are explicitly indicated as requiring 0.10.x or higher (it's like executing a PHP application documented as requiring PHP 5.3 under PHP 5.1.x).
+
+Both the upstream developer, their integration tests and the developers in our teams working locally already use Nodejs 0.10.x or higher, so this is waiting for something to fail.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1401749760,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_description,resolved
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"Change 159224 merged by jenkins-bot:
+job-templates: Move {name}-npm from Precise to Trusty
+
+https://gerrit.wikimedia.org/r/159224",1411259816,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"Change 159224 had a related patch set uploaded by Krinkle:
+[WIP] job-templates: Move {name}-npm from Precise to Trusty
+
+https://gerrit.wikimedia.org/r/159224",1410222687,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"The Trusty slave is integration-slave1006-trusty.eqiad.wmflabs
+
+The label remain unchanged:  UbuntuTrusty.
+
+
+Marking this bug as fixed since npm/nodejs are available there. ""Just"" have to update the label in the job configuration.",1408703173,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"We have a Trusty Jenkins slave in labs: integration-slave1004-trusty.eqiad.wmflabs
+
+It has the label UbuntuTrusty.  The npm based jobs can be made to run on it by changing the node:  definition in Jenkins Job Builder configuration.
+
+The node has:
+
+$ npm --version
+1.3.10
+$ nodejs --version
+v0.10.25
+$",1406886366,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves,"On contint slaves we have nodejs 0.8.2 which comes from apt.wikimedia.org.  AFAIK that is the version used on parsoid servers as well.
+
+When I asked npm package to be backported with RT #6519 Faidon the plan is to migrate to Ubuntu Trusty (14.04) which ships 0.10.25.
+
+wmflabs now provides a Trusty virtual image and we run npm jobs there.
+
+So you can:
+- build an instance using Trusty image
+- attempt to apply the puppet manifest role::ci::slave::labs
+- add the slave in Jenkins (we can pair that part)
+- apply a label to the slave (ex: UbuntuTrusty) and tie some job to it
+
+
+A culprit: anything running in production with nodejs 0.8 should probably be kept with nodejs 0.8 (parsoid parser tests come to mind) or we might end up missing incompatibility.  You can sync with Gabriel Wicke for that part.
+
+
+Overall: yeah lets go!",1401752278,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-qoj6ymfjm5pgvzklinrg,task_subcomment,NA
+"VisualEditor:  Be able to specify a file name in the media or image dialog, even if search can't find the file","This might be something that could be associated with Bug 52463:
+
+If Search can't find an image—which happens fairly often with images that the user just uploaded—then please let the user specify the file name anyway.  Right now, if Search didn't happen to index your file yet, then you cannot add the image.  ""Try again tomorrow, because maybe the search index will have caught up by then"" is not an ideal user experience.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401737880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-bi34wimyectesmdx6jar,task_description,declined
+"VisualEditor:  Be able to specify a file name in the media or image dialog, even if search can't find the file",I disagree with your comment about search results working fine now. I added some findings to https://bugzilla.wikimedia.org/show_bug.cgi?id=62917#c1 .,1409737567,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-bi34wimyectesmdx6jar,task_subcomment,NA
+"VisualEditor:  Be able to specify a file name in the media or image dialog, even if search can't find the file","(In reply to Elitre from comment #1)
+> Isn't this fixed?
+> Right now I can paste the file name of the pic I want while adding a media.
+> It looks like the only way to currently get to the desired image, because
+> the search seems to be even worse than I remembered (try looking for a
+> ""European robin"" image on en.wp, give up in frustration, paste
+> File:Erithacus rubecula with cocked head.jpg in the dialog to put the image
+> on the page after you found it on Commons).
+
+Technically not done, but the search results generally work well enough.",1409583730,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bi34wimyectesmdx6jar,task_subcomment,NA
+"VisualEditor:  Be able to specify a file name in the media or image dialog, even if search can't find the file","Isn't this fixed?
+Right now I can paste the file name of the pic I want while adding a media. It looks like the only way to currently get to the desired image, because the search seems to be even worse than I remembered (try looking for a ""European robin"" image on en.wp, give up in frustration, paste File:Erithacus rubecula with cocked head.jpg in the dialog to put the image on the page after you found it on Commons).",1409569002,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-bi34wimyectesmdx6jar,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,"There should be links http://stats.wikimedia.org/EN/EditsRevertsIT.htm <-> http://ee-dashboard.wmflabs.org/dashboards/itwiki-metrics#reverts-graphs-tab and http://ee-dashboard.wmflabs.org/dashboards/itwiki-metrics#registrations-graphs-tab <-> http://ee-dashboard.wmflabs.org/dashboards/itwiki-metrics#registrations-graphs-tab .
+Only applies to the ten Wikipedias having them: https://meta.wikimedia.org/wiki/Research:VisualEditor
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401617460,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-w6vt4utuqyldv2cmmund,task_description,declined
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,We're killing ee-dashboard (and have been for three years); let's not add more cruft and links to it.,1463086361,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,">>! In T67994#1773128, @ezachte wrote:
+> What's the best way to detect which language codes have new stats? (other than screen scraping https://meta.wikimedia.org/wiki/Research:VisualEditor)
+
+I guess parsing the list of *wiki directories at https://datasets.wikimedia.org/public-datasets/",1446540387,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,What's the best way to detect which language codes have new stats? (other than screen scraping https://meta.wikimedia.org/wiki/Research:VisualEditor),1446464875,PHID-USER-m5uwh66djeylkim5chfe,False,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,"Nemo: Are you still working on this, as this ticket is assigned to you?",1416496278,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org,Good idea Nemo. Erik -- thoughts?,1401736314,PHID-USER-ud7f5gp5h3uqup6viq4e,False,PHID-TASK-w6vt4utuqyldv2cmmund,task_subcomment,NA
+VisualEditor: Do not allow creation of empty lists inside tables (?!),"This should not happen:
+https://pt.wikipedia.org/w/index.php?diff=39042930
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401531960,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-iqrozz7c5dzdomgukors,task_description,open
+Unrelated content in produced PDF,"Sample PDF
+
+1) http://eo.wikipedia.beta.wmflabs.org/wiki/Headings_VisualEditor_Test
+2) ""Elŝuti kiel WMF PDF""
+
+Result: a page with content coming from I have no idea where, see attachment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13832}",1401439440,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_description,resolved
+Unrelated content in produced PDF,I filled a bug to have an integration job that ensure puppet repo is updated before all-labs.dblist has a new wiki added. https://bugzilla.wikimedia.org/show_bug.cgi?id=68532,1406235686,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"Change 148330 merged by Alexandros Kosiaris:
+beta: update Parsoid localsettings entries
+
+https://gerrit.wikimedia.org/r/148330",1406018271,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,I have applied the puppet patch above on the beta cluster and restarted Parsoid that should fix the issue.,1406017249,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"Change 148330 had a related patch set uploaded by Hashar:
+beta: update Parsoid localsettings entries
+
+https://gerrit.wikimedia.org/r/148330",1406016978,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,Amended the add wiki documentation https://wikitech.wikimedia.org/w/index.php?title=Nova_Resource:Deployment-prep/Add_a_wiki&diff=120678&oldid=120568,1406016177,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"Matt says PDF is using Parsoid has a backend.
+C. Scott reproduces the issue with VisualEditor.
+
+That means Parsoid is badly configured on beta and use the wrong backend.  Maybe it is fetching articles from production API?
+
+And the winner is: Antoine! The list of wikis is hardcoded in a puppet configuration file http://git.wikimedia.org/blob/operations%2Fpuppet.git/c585887114/files%2Fmisc%2Fparsoid-localsettings-beta.js and the documentation to add a wiki is missing that step https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/Add_a_wiki",1406015986,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"(In reply to C. Scott Ananian from comment #3)
+> That is, the PDF renderer is misconfigured on eo.beta and is requesting
+> pages from eowiki instead.  It is communicating its request by page id...
+> with the surprising results you have noted.
+
+cc hashar",1405664326,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"The page you are trying to print is:
+http://eo.wikipedia.beta.wmflabs.org/w/index.php?title=Headings_VisualEditor_Test&oldid=11
+
+The content you are getting is:
+https://eo.wikipedia.org/w/index.php?title=Headings_VisualEditor_Test&oldid=11
+
+That is, the PDF renderer is misconfigured on eo.beta and is requesting pages from eowiki instead.  It is communicating its request by page id... with the surprising results you have noted.
+
+But ultimately this is an eo.wiki misconfiguration.  Note that http://eo.wikipedia.beta.wmflabs.org/wiki/Headings_VisualEditor_Test?veaction=edit is also ""surprising"".",1405655198,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,"**mwalker** wrote:
+
+It's not a problem per-se with the renderer; we're rendering what parsoid is giving us... I'm not sure what parsoid is doing.",1405652831,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+Unrelated content in produced PDF,That may have to do with FlaggedRevs (or with the wiki being empty): http://simple.wikipedia.beta.wmflabs.org/wiki/List_of_literary_terms worked,1401439983,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-alhxfplatrwdgk43xfb3,task_subcomment,NA
+VisualEditor: Remove gallery button from the Insert Menu,"Screenshot
+
+I dont see any option to insert gallery in the Insert medu suddenly.
+Happening in betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13825}",1401431340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s4vdrbpgig26i4hixati,task_description,resolved
+VisualEditor: Remove gallery button from the Insert Menu,Verified the fix in production,1402086311,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s4vdrbpgig26i4hixati,task_subcomment,NA
+VisualEditor: Remove gallery button from the Insert Menu,"Yes, sorry, this was done intentionally in gerit 135965.",1401471842,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s4vdrbpgig26i4hixati,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Steps to reproduce:
+
+1.Click on the Edit/Edit Beta link beside a section heading of an article
+
+Observed Result:
+It places the cursor at the beginning of the document .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401412380,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qh467vyga6czchrrd2p,task_description,resolved
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"(In reply to Tony Thomas from comment #11)
+> This still happens. Check
+> https://www.mediawiki.org/w/index.
+> php?title=WYSIWYG_editor&veaction=edit&vesection=18 from chrome !
+
+Eugh, there seems to be a regression here when clicked on the page; if you click that link it works fine… As such, rather than re-opening I've created bug 72919 for this. Thanks for the spot.",1415045956,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,This still happens. Check https://www.mediawiki.org/w/index.php?title=WYSIWYG_editor&veaction=edit&vesection=18 from chrome !,1415035976,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Verified the fix in production. There is a different issue with cursor now though 
+which has been reported in:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67106",1403892427,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"WFM; cache issue, it appears.",1403726656,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,This is still happening on FireFox in Betalabs running from master.,1403723709,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,Probably a deployment issue; fixed on MW.org and test2.,1403622161,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,WFM in Firefox at http://en.wikipedia.beta.wmflabs.org/wiki/WikiNodes and on master,1403620028,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Not fixed for Firefox , there is no cursor at all pointing anywhere in the document after clicking on Edit link for section editing.",1403305166,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,Verified the fix in Betalabs,1403043756,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Change 139677 merged by jenkins-bot:
+Wait for onDocumentFocus to happen before setting section range
+
+https://gerrit.wikimedia.org/r/139677",1402835997,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"Change 139677 had a related patch set uploaded by Esanders:
+Wait for onDocumentFocus to happen before setting section range
+
+https://gerrit.wikimedia.org/r/139677",1402833473,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article,"It seems like the dm.Surface's selection is getting set to the beginning of the section like it should be, but then when the ce/ui.Surface is intialized, the cursor isn't put there. It seems the surface isn't focused correctly on init anyway, and as soon as you interact with it SurfaceObserver will notice the cursor is at (1,1) and change the DM selection to that.",1402002772,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7qh467vyga6czchrrd2p,task_subcomment,NA
+"VisualEditor: On pages which are redirects, veaction=edit should actually do redirect=no&veaction=edit","Steps to Reproduce:
+1. Click on https://en.wikipedia.org/wiki/Sugar_candies?veaction=edit
+
+2. Wonder why it is editing https://en.wikipedia.org/wiki/Sugar_candy (the target) instead of https://en.wikipedia.org/wiki/Sugar_candies (the redirect)?
+
+
+Actual Results:  
+It first redirects me to the target page, and then opens the target page for editing.  This makes it impossible to change the redirect to some other page, unless you modify the URL to say https://en.wikipedia.org/wiki/Sugar_candies?veaction=edit&redirect=no (either manually or by first visiting to the redirect page).
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65621",1401409620,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-i33x4h5mjnat262gctqt,task_description,resolved
+"VisualEditor: On pages which are redirects, veaction=edit should actually do redirect=no&veaction=edit","Change 138585 merged by jenkins-bot:
+Suppress redirects if veaction=edit is requested
+
+https://gerrit.wikimedia.org/r/138585",1402422369,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-i33x4h5mjnat262gctqt,task_subcomment,NA
+"VisualEditor: On pages which are redirects, veaction=edit should actually do redirect=no&veaction=edit","Change 138585 had a related patch set uploaded by Alex Monk:
+Suppress redirects if veaction=edit is requested
+
+https://gerrit.wikimedia.org/r/138585",1402402998,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-i33x4h5mjnat262gctqt,task_subcomment,NA
+"VisualEditor: On pages which are redirects, veaction=edit should actually do redirect=no&veaction=edit","https://en.wikipedia.org/w/index.php?title=Sugar_candies&redirect=no&veaction=edit works fine, but https://en.wikipedia.org/wiki/Sugar_candies?veaction=edit takes you to the target. Bah.",1401412090,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-i33x4h5mjnat262gctqt,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Steps to Reproduce:
+1. Open a page that contains inline images at the start of a paragraph or list item.
+
+2. Select the image, open the image dialog, and de-select the ""Wrap text around"" item.  The item will float right.
+
+3. Change your mind.  Open the imge dialog again, and re-select the ""Wrap text around"" item.
+
+Actual Results:  
+The inline image appears to be, but isn't actually, on its own line.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401406980,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_description,resolved
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 139269 merged by jenkins-bot:
+Insert inline image inside list to the existing paragraph
+
+https://gerrit.wikimedia.org/r/139269",1403034579,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 139064 abandoned by Mooeypoo:
+Add inline images into existing paragraphs
+
+Reason:
+Moving this to the MWImageModel in a new commit
+
+https://gerrit.wikimedia.org/r/139064",1402611641,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 139269 had a related patch set uploaded by Mooeypoo:
+Don't create new paragraph for inline image inside list
+
+https://gerrit.wikimedia.org/r/139269",1402610848,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 139064 had a related patch set uploaded by Mooeypoo:
+Add inline images into existing paragraphs
+
+https://gerrit.wikimedia.org/r/139064",1402545423,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"(In reply to Gerrit Notification Bot from comment #8)
+> Change 138114 had a related patch set uploaded by Catrope:
+> [BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window
+> process cleanup
+> 
+> https://gerrit.wikimedia.org/r/138114
+
+Whoops, not relevant; my mistake.",1402533723,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Change 138114 had a related patch set uploaded by Catrope:
+[BREAKING CHANGE] Update VE core submodule to master (43a48cb) for window process cleanup
+
+https://gerrit.wikimedia.org/r/138114",1402533465,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"If we can have fixUpInsertion insert the image into an existing paragraph in the case of lists, that can be a good solution too.",1401906392,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,Why does it always add a paragraph? Surely that's for fixUpInsertion to decide?,1401905156,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"After further examination, this isn't an image bug per say, it is a list bug.
+
+When the image is transformed from block to inline it goes back to being on its own paragraph (as it does always regardless of lists) letting the user decide where it should be.
+
+The problem with the list, however, is that when the image goes back to being inline it is presented as if it is on its own line inside the list (with the text being on a different paragraph in the list item) 
+
+However, the list itself won't allow for multi paragraphs and the resulting wikitext shows the image and followup text without the extra line space.
+
+We could either add a <br> in between the image and the new text (in Parsoid?) or find a creative solution to make lists with multiline text behavior reflect that of the resulting wikitext in general.",1401904664,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Created attachment 15535
+Before moving the image.  This is what it ought to look like after I move it back, too (perhaps minus the space between image and text).
+
+**Attached**: {F13791}",1401462992,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Created attachment 15534
+Inline image has been moved back, and displays on its own line
+
+**Attached**: {F13789}",1401462938,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"Look at what happens to the ""laundromat"" image at http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=100058&oldid=100057
+
+It was inline; I made it be a normal/non-inline image (perhaps ""floating"" isn't the right word?).  Then I moved it back.  When I moved it back, it displayed oddly—on its own line in the display, although it was inline when I saved.  
+
+I'll upload some screenshots for you.",1401462772,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor:  Inline images don't display correctly if converted to floating images and then back,"I'm a bit confused. You mentioned you need to de-select the floating value of the image, but inline images aren't supposed to have floating values at all (the checkbox should be unchecked) -- are you sure you're looking at inline images, or that you unchecked the value first?
+
+Can you give me an example to look at? Thanks!",1401424249,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-5tsqijmuo4ilr7nqgjnq,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Screenshot
+
+Steps to reproduce:
+
+1.Insert an image of any type
+
+2.Uncheck the wrap option
+
+3.Check the wrap option again
+
+4.Checking the wrap option automatically selects the ""Right"" as alignment again
+
+5.Now click on one of the other alignment option:Centre/Left
+
+Observed Result:
+
+The alignment tab for ""Right"" is still selected, also the new one of step 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13768}",1401400020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2dy4aao545tjoscghlgd,task_description,resolved
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,Verified the fix in production (en.wiki),1403301154,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,Verified the fix in test2 running wmf9,1402696114,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,Verified the fix in Betalabs,1402350197,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 138122 merged by jenkins-bot:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/138122",1402105346,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 138122 had a related patch set uploaded by Jforrester:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/138122",1402102762,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 137524 merged by jenkins-bot:
+Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/137524",1402018372,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 137729 merged by jenkins-bot:
+Allow programmatic selection of options while disabled
+
+https://gerrit.wikimedia.org/r/137729",1402017589,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 137729 had a related patch set uploaded by Catrope:
+Allow programmatic selection of options while disabled
+
+https://gerrit.wikimedia.org/r/137729",1402001211,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Change 137524 had a related patch set uploaded by Mooeypoo:
+[wip] Fixing issues in the alignment select in Media Edit dialog
+
+https://gerrit.wikimedia.org/r/137524",1401935542,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option,"Also, if you set the image type to Basic, the alignment checkbox will behave really strangely:
+
+1. Set image type to basic
+2. Checkbox is unticked, left/center/right toggle is disabled
+3. Click checkbox. Checkbox is ticked and immediately unticked again, but left/center/right toggle is now enabled.
+4. Click Left. Checkbox is ticked
+5. Untick checkbox. Toggle is now disabled again
+
+Go home alignment widget, you're drunk.",1401925266,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2dy4aao545tjoscghlgd,task_subcomment,NA
+"VisualEditor: When providing a list of potential links, show redirects' destinations, not just that they are redirects","VisualEditor can determine if the link you are adding is a redirect or not (since Bug 50240), but it doesn't tell what the redirect page goes to. Just seeing ""Redirect page"" in the linking tool doesn't tell the user whether or not they're linking to the page they want to be linking to, so I think it should say ""Redirect page to $1"", where $1 is the destination of the redirect that's being linked.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401343080,PHID-USER-qze3uk4zsetjvgf7liey,False,PHID-TASK-dlmffyeaeajaau5cpsge,task_description,resolved
+"VisualEditor: When providing a list of potential links, show redirects' destinations, not just that they are redirects",This was fixed a while ago.,1435939976,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dlmffyeaeajaau5cpsge,task_subcomment,NA
+"VisualEditor: When providing a list of potential links, show redirects' destinations, not just that they are redirects","(In reply to James Forrester from comment #1)
+> The idea is that it's generally a mistake to link to a redirect, and it's
+> generally discouraged on most (all?) wikis. However, yes, this might be a
+> nice improvement.
+
+In that case, it'd be very helpful for editors for VisualEditor to show where the redirect goes to. If you're linking to a redirect and doing so is discouraged on that wiki, it's helpful to know what you should be linking to instead! :)",1401400411,PHID-USER-qze3uk4zsetjvgf7liey,False,PHID-TASK-dlmffyeaeajaau5cpsge,task_subcomment,NA
+"VisualEditor: When providing a list of potential links, show redirects' destinations, not just that they are redirects","The idea is that it's generally a mistake to link to a redirect, and it's generally discouraged on most (all?) wikis. However, yes, this might be a nice improvement.",1401377050,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dlmffyeaeajaau5cpsge,task_subcomment,NA
+VisualEditor: Changing image from floated (right+basic) to thumb does not update size correctly,"Take an image like [[File:Bigimage.png|border|right]], inspect it, and change it to a thumbnail. You get a thumbnail image of the exact same dimensions. But when you save, this serializes to [[File:Whatever.png|thumb]], which renders in read mode (and when you reopen it in VE) as a much smaller image, because it's using the default thumb size.
+
+I would argue that, when you switch to thumb, it should use the default size for thumbs right then and there, but in any case, it's clear here that what's being displayed in CE is not an accurate reflection of what's actually going to happen when the user saves, and that's a problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401325260,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-futqy7nlsvxuqr4dx2cu,task_description,resolved
+VisualEditor: Changing image from floated (right+basic) to thumb does not update size correctly,"Change 136981 merged by jenkins-bot:
+Update image size after changing type
+
+https://gerrit.wikimedia.org/r/136981",1401925856,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-futqy7nlsvxuqr4dx2cu,task_subcomment,NA
+VisualEditor: Changing image from floated (right+basic) to thumb does not update size correctly,"Change 136981 had a related patch set uploaded by Mooeypoo:
+Update image size after changing type
+
+https://gerrit.wikimedia.org/r/136981",1401780873,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-futqy7nlsvxuqr4dx2cu,task_subcomment,NA
+VisualEditor: Make SurfaceWidget constructor not depend on global target,"See discussion at https://gerrit.wikimedia.org/r/#/c/135012/ . I think the SurfaceWidget constructor shouldn't use the global target, but instead take a config option telling it what kind of surface to construct, or take a surface object, or something.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401319080,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-64xilll6eo5zib7plcyu,task_description,open
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","If the ""description"" field for TemplateData is empty, clicking the help/information button (an i with a circle around it) for the parameter produces a very skinny, empty box.  Nothing should be displayed when there is no description to display.
+
+Alternatively, it's possible that some standard text could be put in the box, like ""There is no description for this item"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401297960,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_description,resolved
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","Change 136348 merged by jenkins-bot:
+Trim description when working out whether or not we should disable the info button
+
+https://gerrit.wikimedia.org/r/136348",1401474560,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button",Thanks!,1401471687,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","Change 136348 had a related patch set uploaded by Alex Monk:
+Trim description when working out whether or not we should disable the info button
+
+https://gerrit.wikimedia.org/r/136348",1401470435,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","Ah:  the TemplateData at https://en.wikipedia.org/wiki/Template:Infobox_UK_place/doc#TemplateData says,
+
+
+""os_grid_reference"": { ""label"": ""os grid reference"", ""description"": "" "", ""type"": ""string"", ""required"": false },
+
+
+If it said this instead,
+
+""os_grid_reference"": { ""label"": ""os grid reference"", ""description"": """", ""type"": ""string"", ""required"": false },
+
+or perhaps this:
+
+""os_grid_reference"": { ""label"": ""os grid reference"", ""type"": ""string"", ""required"": false },
+
+(if it's permitted to omit the description item), then this should go away.",1401469622,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","The description is set as a single space for this parameter, so I think this is expected behaviour.",1401462759,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","Open the infobox in https://en.wikipedia.org/wiki/Aberystwyth and look at the parameter ""os_grid_reference"".
+
+The original report is at https://en.wikipedia.org/w/index.php?oldid=610519258#Info_on_template_fields",1401462539,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","WhatamIdoing, can you perhaps give an example page where it does this?",1401453961,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","If the parameter is required, I do get 'Field is required.' which should be shown still. But if it's not required, then the help/information button is disabled... No empty box.",1401453869,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+"VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button","I thought we had disabled these, but apparently not. Bah.",1401392630,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-667pdzsnat3vywzbk5ru,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a new image
+3.Select the option ""Centre"" for wrapping the text around it
+4.Select the type as ""Frameless"" or ""Basic""
+5.Save the page
+
+Observed Result:
+
+The image moves to the left side of the page 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13568}",1401230100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_description,resolved
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,Verified the fix in production,1402087975,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,Verified the fix in test2,1401403091,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,Verified the fix on betalabs,1401316525,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,"Change 135729 merged by jenkins-bot:
+Make sure <figure> has proper dimensions
+
+https://gerrit.wikimedia.org/r/135729",1401303252,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left,"Change 135729 had a related patch set uploaded by Mooeypoo:
+Make sure <figure> has proper dimensions
+
+https://gerrit.wikimedia.org/r/135729",1401241733,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kh62mq4lhvjr4fgfwe22,task_subcomment,NA
+VisualEditor: Issues with new Image model (tracking),"This is a tracking bug for all the issues related with new Image model
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401217980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cmqoovhbvvqbxuay3bwi,task_description,resolved
+VisualEditor: Issues with new Image model (tracking),Wow. This looks nice.,1403120147,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-cmqoovhbvvqbxuay3bwi,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"On mediawiki.org in both Chrome and FF. 
+
+Edit any page with VE, either logged in or not.  Note that you get the beta warning.
+
+Save your edit. Edit the page again. 
+
+See the beta warning again.
+
+After one new VE edit, the user should never see the beta warning again.  This is controlled by setting a cookie in the browser.  No betawarning cookie is being set now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1401210720,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_description,resolved
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136124 merged by jenkins-bot:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136124",1401485083,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136122 merged by jenkins-bot:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136122",1401485066,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136122 had a related patch set uploaded by Alex Monk:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136122",1401482358,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136124 had a related patch set uploaded by Jforrester:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136124",1401382643,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136120 merged by jenkins-bot:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136120",1401382641,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Change 136120 had a related patch set uploaded by Alex Monk:
+Fix beta warning appearing for some users that it shouldn't.
+
+https://gerrit.wikimedia.org/r/136120",1401381771,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,Also getting reports of this on enwiki etc. – not great.,1401217265,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Yeah, this is a worrying regression, possibly due to the bug 55551 changes.
+
+(Saw breakage for Rummana on her account on MW.org, so this is probably a timing issue related to when the accounts hit a wiki before the code changed or similar?)",1401214599,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,"Actually, this is seen on test2 only so far.",1401212317,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon,*** Bug 65710 has been marked as a duplicate of this bug. ***,1401210879,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-jc3gqyo3pxpfmohz2253,task_subcomment,NA
+Enabling TemplateData editor in Catalan Wikipedia,"/me waves with my volunteer ca.wiki tech ambassador hat on.
+
+The Catalan Wikipedia community wants to try the TemplateData editor. Can you enable it, please? Discussion (in Catalan) at
+
+https://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Ajuda#VisualEditor_global_newsletter.E2.80.94May_2014
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401145140,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-fkv4g3aqxijtbgft56ij,task_description,resolved
+Enabling TemplateData editor in Catalan Wikipedia,This is now live.,1402010019,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fkv4g3aqxijtbgft56ij,task_subcomment,NA
+Enabling TemplateData editor in Catalan Wikipedia,"Change 135580 merged by jenkins-bot:
+Enable TemplateData GUI on Catalan Wikipedia
+
+https://gerrit.wikimedia.org/r/135580",1401992640,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fkv4g3aqxijtbgft56ij,task_subcomment,NA
+Enabling TemplateData editor in Catalan Wikipedia,"Change 135580 had a related patch set uploaded by Jforrester:
+Enable TemplateData GUI on Catalan Wikipedia
+
+https://gerrit.wikimedia.org/r/135580",1401206855,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fkv4g3aqxijtbgft56ij,task_subcomment,NA
+VisualEditor: Left/right cursoring into block slug doesn't trigger animations,"--------------------------
+**Version**: unspecified
+**Severity**: normal",1401018180,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-gs7sqst6umknljvlszmu,task_description,resolved
+VisualEditor: Left/right cursoring into block slug doesn't trigger animations,"Change 190022 merged by jenkins-bot:
+Simplify slug behaviour
+
+[[https://gerrit.wikimedia.org/r/190022]]",1424725248,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gs7sqst6umknljvlszmu,task_subcomment,NA
+VisualEditor: Left/right cursoring into block slug doesn't trigger animations,"Change 190022 had a related patch set uploaded (by Esanders):
+Simplify slug behaviour
+
+[[https://gerrit.wikimedia.org/r/190022]]
+
+#patch-for-review",1423756454,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gs7sqst6umknljvlszmu,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it Frameless-right or Basic-Right
+4.Hover over the image after that
+
+Observed Result:
+The area around the image remains highlighted but not the image itself
+
+See the screenshot attached
+Environment: Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13899}",1400889120,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_description,resolved
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right",Verified the fix in production,1403900614,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right",Verified the fix in test2,1403303677,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 140747 merged by Catrope:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140747",1403200717,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 140747 had a related patch set uploaded by Jforrester:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140747",1403200681,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 140687 merged by jenkins-bot:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140687",1403200677,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 140687 had a related patch set uploaded by Esanders:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140687",1403175920,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 139824 merged by jenkins-bot:
+Fix selection after inserting nodes
+
+https://gerrit.wikimedia.org/r/139824",1403132279,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 137040 merged by jenkins-bot:
+[BREAKING CHANGE (ish)] Track original data position in insertion operations
+
+https://gerrit.wikimedia.org/r/137040",1403130608,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 139824 had a related patch set uploaded by Esanders:
+Fix selection after inserting nodes
+
+https://gerrit.wikimedia.org/r/139824",1402925757,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Change 137040 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE (ish)] Track orignal data position in insertion operations
+
+https://gerrit.wikimedia.org/r/137040",1402923261,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","
+
+*** This bug has been marked as a duplicate of bug 65706 ***",1402923208,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Selection range issue, not a shield issue.",1402921893,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+"VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right","Corrected steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it Frameless-Left or Basic-Left
+4.Now uncheck the wrapping option.
+5.Hover over the image after that.
+
+Observed Result:
+The area around the image remains highlighted but not the image itself.",1401323936,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nwx24kr2omo3papjy3ml,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400885280,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_description,resolved
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,Verified the fix in production,1403893138,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,Verified the fix in test2,1403304493,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 140747 merged by Catrope:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140747",1403200714,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 140747 had a related patch set uploaded by Jforrester:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140747",1403200685,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 140687 merged by jenkins-bot:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140687",1403200674,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 140687 had a related patch set uploaded by Esanders:
+Fix fragment after inserting an image node
+
+https://gerrit.wikimedia.org/r/140687",1403175915,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 139824 merged by jenkins-bot:
+Fix selection after inserting nodes
+
+https://gerrit.wikimedia.org/r/139824",1403132282,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"DM selection issue, not a shield bug.",1402925615,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Change 139824 had a related patch set uploaded by Esanders:
+Fix selection after inserting nodes
+
+https://gerrit.wikimedia.org/r/139824",1402925569,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,*** Bug 65716 has been marked as a duplicate of this bug. ***,1402923208,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,The previous line also gets highlighted while adding an image.,1401819912,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,This is happening in Chrome only not in Firefox,1400886178,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image,"Steps to reproduce:
+
+1.Open a page with VE
+2.Go to the end of the page 
+3.Insert a reference list
+
+Observed Result:
+It is highlighting the previous line while adding the reference list.
+This behavior has been observed as of 23rd may",1400885687,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ekjvtpnzqj4imqhj22ob,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","""Translation unit markers in unexpected position."" can just go die in Hell. Gah.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also:** {T58451}, {T73730}, {T50891}",1400786640,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_description,open
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort",FWIW [[https://www.mediawiki.org/w/index.php?title=Manual:Developing_extensions&diff=2696555&oldid=2696554|this]] worked in the end.,1516414993,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","Also results in a bunch of JS errors along the line of
+```
+Uncaught TypeError: Cannot read property 'top' of null
+    at <anonymous>:405:348
+    at Array.forEach (<anonymous>)
+    at VeUiDiffElement.ve.ui.DiffElement.positionDescriptions (<anonymous>:405:25)
+    at <anonymous>:682:225
+    at VeUiMwSaveDialog.OO.ui.Window.withoutSizeTransitions (<anonymous>:45:1)
+    at <anonymous>:682:129
+```
+and
+```
+Uncaught TypeError: Cannot read property 'getSelection' of undefined
+    at VeUiFindAndReplaceDialog.ve.ui.FindAndReplaceDialog.renderRangeOfFragments (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:952)
+    at VeUiFindAndReplaceDialog.ve.ui.FindAndReplaceDialog.renderFragments (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:952)
+    at run (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:1048)
+    at VeUiFindAndReplaceDialog.renderFragmentsThrottled (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:1048)
+    at VeUiFindAndReplaceDialog.ve.ui.FindAndReplaceDialog.onSurfaceViewPosition (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:949)
+    at VeCeMwWikitextSurface.oo.EventEmitter.emit (<anonymous>:233:445)
+    at VeCeMwWikitextSurface.<anonymous> (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:713)
+    at later (/w/load.php?debug=false&lang=en&modules=ext.CodeMirror.lib%7Cext.visualEditor.core%7Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=0okwd4t:1048)
+```
+I think those started propping up after trying visual diff for curiosity (broken by Translate, of course).",1516414841,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort",">>! In T67653#3363689, @Deskana wrote:
+> Can you give me some more details on what the problem is, and what the steps to reproduce are? 
+
+Open a translatable page for editing, do an innocent change, get useless error report.
+E.g. I'm trying to save https://www.mediawiki.org/w/index.php?title=Manual:Developing_extensions&oldid=2696554 with this diff:
+
+```lang=diff
+--- 1.txt	2018-01-19 18:12:32.130524437 -0800
++++ 2.txt	2018-01-19 18:13:50.941714520 -0800
+@@ -479,11 +479,11 @@
+ 
+ <translate>
+ 
+-==Support other core versions== <!--T:286-->
++==Support other core versions== <!--T:286--></translate>
+ <!-- keep this in sync with [[Compatibility#MediaWiki_extensions]] -->
+ 
+-<!--T:315-->
+-There are two widespread conventions for supporting older versions of MediaWiki core:</translate>
++<translate>
++<!--T:315-->There are two widespread conventions for supporting older versions of MediaWiki core:</translate>
+ 
+ <translate><!--T:316--> * Master: the master branch of the extension is compatible with as many old versions of core as possible. This results in a maintenance burden (backwards-compatibility hacks need to be kept around for a long time, and changes to the extension need to be tested with several versions of MediaWiki), but sites running old MediaWiki versions benefit from functionality recently added to the extension.</translate>
+ <translate><!--T:317--> * Release branches: release branches of the extension are compatible with matching branches of core, e.g. sites using MediaWiki 1.27 need to use the REL1_27 branch of the extension. (For extensions hosted on [[gerrit]], these branches are automatically created when new versions of MediaWiki are released.) This results in cleaner code and faster development but users on old core versions do not benefit from bugfixes and new features unless they are backported manually.</translate>
+```
+(That is, break up the flow of translatable text with an untranslatable comment. None of the translation items are changed.)
+
+I've tried a handful of different positions for the translate tag, to no avail.
+
+(FWIW this is in new wikitext editor, not normal VE. I don't imagine it makes any difference.)",1516414669,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort",">>! In T67653#3359087, @jeblad wrote:
+> With WikitextEditor this has become critical for editing translated pages.
+
+Can you give me some more details on what the problem is, and what the steps to reproduce are? ",1497971179,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","With WikitextEditor this has become critical for editing translated pages.
+",1497859187,PHID-USER-vlni4mhyozor7ghqnfkl,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to Nemo from comment #5)
+> I guess it can also be put that way. :) Does this new summary reflect the
+> aim?
+
+Not really. Putting a hack into VisualEditor to cope with another extension's model is not good. Either way, I don't care enough. :-)",1415031943,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort",I guess it can also be put that way. :) Does this new summary reflect the aim?,1415031727,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to Nemo from comment #3)
+> (In reply to James Forrester from comment #2)
+> > I don't know. You're the Translate extension expert. :-)
+> 
+> Ok. That error probably just means that some newline was inserted in the
+> wrong place before or after <!--T:1--> and similar, IIRC.
+> 
+> So if you don't have a specific intention here I guess this is one bug of
+> the series ""make VisualEditor not touch Translate stuff which otherwise
+> breaks"" (bug 56451, bug 71730), and is probably blocked on bug 48891 as its
+> friends.
+
+No, this is not a parser bug.
+
+It's just a ""VE should react to stupidly vague error responses by killing stupid comments in stupid places used by a stupid extension to do critical functions that should be done better"" bug. :-)",1415031396,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to James Forrester from comment #2)
+> I don't know. You're the Translate extension expert. :-)
+
+Ok. That error probably just means that some newline was inserted in the wrong place before or after <!--T:1--> and similar, IIRC.
+
+So if you don't have a specific intention here I guess this is one bug of the series ""make VisualEditor not touch Translate stuff which otherwise breaks"" (bug 56451, bug 71730), and is probably blocked on bug 48891 as its friends.",1415031186,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to Nemo from comment #1)
+> (In reply to James Forrester from comment #0)
+> > ""Translation unit markers in unexpected position."" can just go die in Hell.
+> > Gah.
+> 
+> Is this bug related to other bugs?
+
+I don't know. You're the Translate extension expert. :-)",1415030710,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+"VisualEditor: avoid causing ""Translation unit markers in unexpected position"" edit abort","(In reply to James Forrester from comment #0)
+> ""Translation unit markers in unexpected position."" can just go die in Hell.
+> Gah.
+
+Is this bug related to other bugs?",1414866147,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-nfr2zvfwe5lwozeia6mm,task_subcomment,NA
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"Sometimes editing a page in VisualEditor is rearranging categories so that they always end up on a single line, which is inconvenient for people looking at the wikitext source later.
+
+See https://fr.wikipedia.org/w/index.php?title=Jean-Baptiste_Vallière&diff=prev&oldid=104017086
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400782560,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6bfwstz2ygurnkr45nkj,task_description,open
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"Other example that also displays other problems (extra characters at the beginning, and strange characters in the text ☃☃)
+https://fr.wikipedia.org/w/index.php?title=Absolom_2022&diff=104059827&oldid=96660949",1400919158,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-6bfwstz2ygurnkr45nkj,task_subcomment,NA
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"Other example
+https://fr.wikipedia.org/w/index.php?title=Mines_de_Ranci%C3%A9&diff=104031209&oldid=97118583",1400821311,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-6bfwstz2ygurnkr45nkj,task_subcomment,NA
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"We only use the default newline spacing if the categories are actually new content. So if VE is just removing the newlines, but leaves the categories, a result as in the link is to be expected.
+
+Round-tripping works fine with selser:
+
+http://parsoid-lb.eqiad.wikimedia.org/_rtselser/frwiki/Jean-Baptiste_Valli%C3%A8re?oldid=95815820
+
+Even without selser the newlines are preserved:
+
+http://parsoid-lb.eqiad.wikimedia.org/_rt/frwiki/Jean-Baptiste_Valli%C3%A8re?oldid=95815820
+
+This makes it very likely that this is in fact VE removing newlines.",1400782936,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-6bfwstz2ygurnkr45nkj,task_subcomment,NA
+VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?,"Parsoid bug? We hopefully aren't dirtying these, but even if we are, Parsoid's default whitespace should insert a \n before each of these anyway…",1400782652,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6bfwstz2ygurnkr45nkj,task_subcomment,NA
+VisualEditor:  Span tags for Language tool only mark part of the page,"Intention:
+Mark almost an entire page with language (en) and direction (LTR).
+
+Steps to Reproduce:
+1.  Open the page and select almost all of the content.
+ 
+2.  Insert > Language
+
+3.  Set the language to English and the direction to LTR.
+
+Actual Results:  
+Only a small fraction of the page was marked with span tags.  See https://office.wikimedia.org/w/index.php?diff=112247&oldid=112246
+
+Expected Results:  
+I wanted this:
+
+<span lang=""en"" dir=""ltr"">
+Div box 
+Image
+Text
+Image
+Some text
+End of div box
+Lots and lots and lots of text
+</span>
+
+I got this:
+
+Div box 
+Image
+<span lang=""en"" dir=""ltr"">Text</span>
+Image
+<span lang=""en"" dir=""ltr"">Text</span>Some te</span>xt
+End of div box
+Lots and lots and lots of text
+
+
+Reproducible: Always
+
+This was exactly repeatable on this page:  the last span tag always ended in the middle of the same word.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://office.wikimedia.org/w/index.php?diff=112247&oldid=112246",1400781180,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-edh3xjjr7fz32wcyfzho,task_description,open
+VisualEditor:  Span tags for Language tool only mark part of the page,"(In reply to WhatamIdoing from comment #2)
+> When I've selected the whole page, I'd rather have the whole page marked
+> with a single pair of tags, even if defining the block content as having a
+> ""language"" is meaningless.
+
+Tough. That's not how HTML works. :-)",1402341119,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-edh3xjjr7fz32wcyfzho,task_subcomment,NA
+VisualEditor:  Span tags for Language tool only mark part of the page,"When I've selected the whole page, I'd rather have the whole page marked with a single pair of tags, even if defining the block content as having a ""language"" is meaningless.",1402341063,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-edh3xjjr7fz32wcyfzho,task_subcomment,NA
+VisualEditor:  Span tags for Language tool only mark part of the page,"The language tool only covers text, not block content, so that's expected.
+
+The not-getting-to-the-end-of-the-selection thing sounds like an odd data model bug.",1402328768,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-edh3xjjr7fz32wcyfzho,task_subcomment,NA
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"When you create a redirect with wikitext, it adds redirect=no.
+
+However, VisualEditor does not (just venotify=created), so you end up going to the target.  Besides being inconsistent, that means it's one extra step to check WhatLinksHere, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65926",1400742720,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_description,resolved
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"Change 138631 merged by jenkins-bot:
+Add redirect=no to new URL when creating a new page as a redirect
+
+https://gerrit.wikimedia.org/r/138631",1402422774,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_subcomment,NA
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"Change 138631 had a related patch set uploaded by Alex Monk:
+Add redirect=no to new URL when creating a new page as a redirect
+
+https://gerrit.wikimedia.org/r/138631",1402419495,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_subcomment,NA
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"Seems to only break if you're creating a new page as a redirect. If you're replacing an existing one with a redirect, it's fine (With the exception of the 'Redirect page' text which it should be adding to #contentSub).",1401118743,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_subcomment,NA
+VisualEditor: Add redirect=no to URL after a page is newly created as a redirect,"Ick. We shouldn't actually be refreshing the page to the extent that a redirect is triggered, however; did we change this?",1400776422,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ddcfyypc3d3cbv33i3u4,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"Intention:
+Copy a reference's contents (not including ref tags).
+
+Steps to Reproduce:
+1. Open a page in Safari.  Add a citation using the Cite tool.
+
+2. Open the new reference in the Reference dialog via Insert > Reference.
+
+3. Select the contents, and press Command-X to cut it.
+
+Actual Results:  
+Nothing happens.  The template is not cut.
+
+Expected Results:  
+It should be possible to copy and paste citation templates, so that you can modify them for other citations or display them on the page outside of <ref> tags.  
+
+Reproducible: Always
+
+This bug cannot be reproduced in Firefox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400688180,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gxjcazoxkhshpy57yk43,task_description,resolved
+VisualEditor:  Can't cut or copy citation template in Reference dialog,Can't reproduce. Given the age of the task I'll assume it's fixed. Please re-open otherwise.,1701963637,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"See attached screenshot.  On the screenshot you can see that the citation template is selected and that Edit > Cut is grayed out.  
+
+Selecting the template and pressing Command-X does nothing, no matter how many times I press it.  The cite journal template remains stubbornly in place, despite trying to cut the entire contents repeatedly.  If my problem were with pasting, then I'd have an empty box and be complaining that I'd lost work.  Instead, I have a full box and I'm complaining that it is not possible to CUT the contents out of this ref (in Safari 6.1.2, at least).",1415075849,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"Created attachment 17008
+Screenshot showing grayed-out ""Cut"" item in Edit menu
+
+**Attached**: {F13603}",1415075520,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"It's possible to cut/copy things from references, but you can't then paste them back into VE once you shut the dialog – this is bug 51725.
+
+*** This bug has been marked as a duplicate of bug 51725 ***",1415063196,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor:  Can't cut or copy citation template in Reference dialog,"Now I can reproduce this in Firefox:
+
+
+1.  Open [[Railway company]].
+
+2.  Discover that the allegedly reliable source is a wikilink to another article.
+
+3.  Open ref dialog.
+
+4.  Select entire contents (one link).
+
+5.  Be confused about why nothing appears to happen.
+
+
+I can copy the link, and I can replace it with garbage, but I cannot make it be empty.  Perhaps this is intentional?  In which case, how can I first remove the unwanted contents, and then add in good contents?",1413500353,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gxjcazoxkhshpy57yk43,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,"It's possible to have a category bubble in the category editor for a category that doesn't have a description page. It would be useful to see that it doesn't exist.
+
+In the source editor this can be achieved while editing by doing a preview and seeing that the link at the bottom is red, so this is a bit of a regression.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49044",1400565480,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-cq5fibwchbc6tbp3nqih,task_description,resolved
+VisualEditor: Categories without description pages don't show as red,Verified the fix in production,1416446905,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,Verified the fix in Betalabs.,1415663361,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,"Change 171464 merged by jenkins-bot:
+Show category items as red if they don't have description pages
+
+https://gerrit.wikimedia.org/r/171464",1415542234,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,"Change 171464 had a related patch set uploaded by Alex Monk:
+Show category items as red if they don't have description pages
+
+https://gerrit.wikimedia.org/r/171464",1415227697,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Categories without description pages don't show as red,*** Bug 69507 has been marked as a duplicate of this bug. ***,1414805875,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cq5fibwchbc6tbp3nqih,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"Right now, the way that the save button is disabled when you click it is that MWSaveDialog listens to the button's click event, in response to that it fires the 'save' event, ArticleTarget gets that event, reaches into the save dialog and disables the button.
+
+This is only one of many insane things about the totally dysfunctional MWSaveDialog - ArticleTarget relationship; the whole way these two interact should be refactored.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400545500,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qj4gnvod7alfvonyqkys,task_description,open
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"Change 140868 abandoned by Alex Monk:
+Move some stuff from ViewPageTarget to MWSaveDialog
+
+https://gerrit.wikimedia.org/r/140868",1415057440,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"Change 140868 had a related patch set uploaded by Alex Monk:
+Move some stuff from ViewPageTarget to MWSaveDialog
+
+https://gerrit.wikimedia.org/r/140868",1403220877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"Yeah, that patch wasn't really intended to fully fix this.",1403127812,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,Mostly fixed in gerrit 135945 but Roan said there are still some outstanding issues.,1403127411,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget,"This'd be lovely to get fixed properly. Alex, could you take a look at this at some point? I imagine Roan'd love to be involved in the refactor, though. :-)",1400545702,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qj4gnvod7alfvonyqkys,task_subcomment,NA
+VisualEditor: Instrument all actions in visual editing toolbar for organization and frequency of use analysis and improvements,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64711",1400535300,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-czjybdfyzr6v25qeuy65,task_description,open
+VisualEditor: Template editor is missing accessibility features,"ve-ui-mwParameterPage-actions have tabindex=-1, which makes them unreachable by keyboard, the same for the ""Add parameter"" button.
+
+
+The text area of the fields is missing the 'required' attribute for fields that are required.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65473
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62337",1400491140,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-42m5jdfxp7jxtni7uvzn,task_description,resolved
+VisualEditor: Template editor is missing accessibility features,*** Bug 63014 has been marked as a duplicate of this bug. ***,1402553868,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-42m5jdfxp7jxtni7uvzn,task_subcomment,NA
+VisualEditor: Template editor is missing accessibility features,"Change 137152 merged by jenkins-bot:
+Add tabindexes to template editor and required attribute where appropriate
+
+https://gerrit.wikimedia.org/r/137152",1401924503,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-42m5jdfxp7jxtni7uvzn,task_subcomment,NA
+VisualEditor: Template editor is missing accessibility features,"Change 137152 had a related patch set uploaded by Alex Monk:
+Add tabindexes to template editor and required attribute where appropriate
+
+https://gerrit.wikimedia.org/r/137152",1401826147,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-42m5jdfxp7jxtni7uvzn,task_subcomment,NA
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","When I access
+https://pt.wikipedia.org/w/index.php?title=Usuário(a):Helder.wiki/Testes&oldid=38949256&veaction=edit&debug=1
+with an empty cache on Firefox 29, it takes at 5+ seconds until I see any progress bar. Sometimes this makes me click in the edit link again because it seems not to be loading at all...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400418840,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-6mc64lhux5u37tjrwhgt,task_description,resolved
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","Change 167736 merged by jenkins-bot:
+Make spinner appear immediately when clicking edit
+
+https://gerrit.wikimedia.org/r/167736",1413928437,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6mc64lhux5u37tjrwhgt,task_subcomment,NA
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","Change 167736 had a related patch set uploaded by SuchetaG:
+Fixing the delay in the spinner to appear and the change in the URL on clicking edit
+
+https://gerrit.wikimedia.org/r/167736",1413865046,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6mc64lhux5u37tjrwhgt,task_subcomment,NA
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","**sucheta.ghoshal** wrote:
+
+The change in the URL with veaction=edit happens late, too. Spinner appears at about the same time as that change happnes.",1413823458,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6mc64lhux5u37tjrwhgt,task_subcomment,NA
+"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?","There are a few issues with how things are initialized. The delay until the loading animation appears is only a symptom of a larger problem: there are multiple requests being made, blocked on each other, that should really be combined.",1402595315,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6mc64lhux5u37tjrwhgt,task_subcomment,NA
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile VE which has some content in it
+2.Delete all the content
+3.Click on the Link inspector icon from the toolbar
+
+Observed Result:
+
+User gets stuck at this point , cannot close the link inspector dialog anymore by tapping on ""<"" or trash icon
+
+Test Environment: https://en.m.wikipedia.org/
+Device: iPad Mini
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13828}",1400275140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_description,resolved
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,Verified the fix in production,1405024014,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_subcomment,NA
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,Verified the fix in test2,1404775097,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_subcomment,NA
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,"Yes, not getting this issue in Betalabs.Marking it as Fixed.",1404167469,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_subcomment,NA
+VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon,Can this be re-checked? May have been fixed.,1404166413,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lir3hgqiu4i4u7zzavcu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Reproducible: Didn't try
+
+Tables like the ones seen at https://en.wikipedia.org/w/index.php?oldid=608813235#Early_years don't display with the correct row height when editing, because VisualEditor assumes that table cells' paragraphs should be styled like other paragraphs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1400272920,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-v3zkwy3tg4leghjf72lu,task_description,resolved
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Change 141923 merged by jenkins-bot:
+Add missing TableCell CSS file and Vector-specific rule
+
+https://gerrit.wikimedia.org/r/141923",1403720050,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Change 141923 had a related patch set uploaded by Esanders:
+Add missing TableCell CSS file and Vector-specific rule
+
+https://gerrit.wikimedia.org/r/141923",1403692740,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be",We should probably do a follow-up tech debt bug about margins for non-paragraphs in table cells…,1402945010,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Change 139676 merged by jenkins-bot:
+Remove margins from paragraphs inside table cells
+
+https://gerrit.wikimedia.org/r/139676",1402944760,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be","Change 139676 had a related patch set uploaded by Esanders:
+Remove margins from paragraphs inside table cells
+
+https://gerrit.wikimedia.org/r/139676",1402833547,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+"Cells in tables are styled like regular paragraphs, and they shouldn't be",https://gerrit.wikimedia.org/r/#/c/139676/,1402832802,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-v3zkwy3tg4leghjf72lu,task_subcomment,NA
+VisualEditor Mobile: VE is not appearing as an option to edit even if Beta-Experimental mode is on in iPhone 4S,"Screenshot
+
+I am not getting the VisualEditor for mobile even after enabling it through Beta-Experimental mode while trying to edit this page:https://en.m.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox
+
+see the screenshot attached:
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13822}",1400272860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-s4ok5yjksrgckoh7pb4g,task_description,invalid
+VisualEditor Mobile: VE is not appearing as an option to edit even if Beta-Experimental mode is on in iPhone 4S,Intentional behaviour.,1401417974,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s4ok5yjksrgckoh7pb4g,task_subcomment,NA
+VisualEditor Mobile: VE is not appearing as an option to edit even if Beta-Experimental mode is on in iPhone 4S,VisualEditor is only loaded when you are on a screen with a resolution of 768px width / height. Thus this will currently not work on iPhone 4S as it is not a tablet...,1400522739,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-s4ok5yjksrgckoh7pb4g,task_subcomment,NA
+VisualEditor Mobile: The tapping on Mobile VE is extremely inconsistent compared to standard,"I experienced a huge inconsistency around the precision of tapping action for Mobile VE in all kind of iOS devices I have tried so far.The devices I observed this issue are: iPad 2 with iOS 7.1.1 , iPhone 4S with iOS 7.1.1 and iPad Mini with iOS 7.0.6
+
+Some times , to open the VE and to select a menu options like Settings/Random/Username , it literally takes me to tap twice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400271360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xb4vn67r37nss6carg4t,task_description,resolved
+VisualEditor Mobile: The tapping on Mobile VE is extremely inconsistent compared to standard,"Seems to work for me well enough, now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488548,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xb4vn67r37nss6carg4t,task_subcomment,NA
+VisualEditor Mobile: The tapping on Mobile VE is extremely inconsistent compared to standard,Needs re-testing.,1430336186,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xb4vn67r37nss6carg4t,task_subcomment,NA
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with Mobile
+2.Attempt to edit it
+3.While keyboard is still appearing tap on the ""X"" button on the top left of VE or just tap on the browser back button.
+
+Observed Result:
+User is redirected to Readmode but the keyboard is still appearing .
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13816}",1400270460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iiy3kce22e4pguynjf55,task_description,resolved
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487692,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iiy3kce22e4pguynjf55,task_subcomment,NA
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,"Yes, still happens on taping on browser back button",1407868361,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iiy3kce22e4pguynjf55,task_subcomment,NA
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,Is this still an issue?,1406663136,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iiy3kce22e4pguynjf55,task_subcomment,NA
+VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE,Correction: Do not edit the page on step2 just tap on CE to place the cursor and cross the VE out to reproduce.,1400270684,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-iiy3kce22e4pguynjf55,task_subcomment,NA
+VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited,"Something like `http://example.com{{deadlink}}` cannot be properly edited in VisualEditor. It should be processed as two pieces:  one external link that is followed immediately by one template.  Instead, it is presented as the text ""http://example.com[]"", linked to `http://example.com[]`. ",1400180460,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-pxmtpggakccpl77xndne,task_description,open
+VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited,"URLs followed by templates are still broken. However, they now seem to be broken differently: they display as regular links with broken syntax, rather than as alienated nodes.",1437771402,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-pxmtpggakccpl77xndne,task_subcomment,NA
+VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited,"Supposedly the reason for this is that http://example.com{{echo|/index.php}} would produce a link to http://example.com/index.php , rather than a link followed by text. But it depends on what the template outputs; if the output starts with a space or a newline this won't happen. Maybe Parsoid is being a bit too trigger-happy with mw:ExpandedAttrs in the second case?",1400276706,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-pxmtpggakccpl77xndne,task_subcomment,NA
+VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited,"Caused by mw:ExpandedAttrs from Parsoid.
+
+Input:
+
+| http://example.com{{deadlink}}
+
+Output:
+
+<a data-mw=""…"" typeof=""mw:ExpandedAttrs"" about=""#mwt2"" rel=""mw:ExtLink"" href=""http://example.com"" data-parsoid=""…"">http://example.com</a>",1400181160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pxmtpggakccpl77xndne,task_subcomment,NA
+VisualEditor: Edit led to a <noinclude> tag being removed (?),"* https://www.mediawiki.org/w/index.php?diff=prev&oldid=1002914
+
+I performed the edit by highlighting the digit '3' with my mouse, and pressing the alphanumerical key '5' on my keyboard; my intention was only to change the date, but VE also removed the <noinclude> tag (I re-added it in a subsequent edit).
+
+Filing this bug after a request from James on IRC.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://www.mediawiki.org/w/index.php?title=MediaWiki_1.24/Roadmap&diff=prev&oldid=1002914",1400179560,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-joglrkxpvi7xbxra2nb4,task_description,declined
+VisualEditor: Edit led to a <noinclude> tag being removed (?),This looks like a temporary Parsoid issue; marking as WORKSFORME as we can't reproduce.,1403220256,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-joglrkxpvi7xbxra2nb4,task_subcomment,NA
+VisualEditor: Edit led to a <noinclude> tag being removed (?),Can't reproduce in Firefox or Chrome.,1402500896,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-joglrkxpvi7xbxra2nb4,task_subcomment,NA
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with Mobile VE which has some content in it
+2.Scroll a bit down 
+3.Tap on any text and then keep on tapping on Return until it deletes the whole line just after the toolbar 
+
+Observed Result:
+After deleting the line just after where the toolbar starts it moves over the toolbar
+
+See the screenshot attached
+
+Test Environment: https://en.m.wikipedia.org/
+Device: iPad Mini
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13595}",1400113740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_description,resolved
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434488607,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_subcomment,NA
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,Needs re-testing.,1430336273,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_subcomment,NA
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,Maybe will go away if we use a different method for a sticky header.,1404329851,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_subcomment,NA
+VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE,"This is not an iOS specific issue here, happens in Nexus 7 as well sadly.",1402962955,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4wl4oxtvtviyvxfc5oan,task_subcomment,NA
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"A more generic way of doing https://gerrit.wikimedia.org/r/133379
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400108520,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-235ze5es2nor6ps5ebbv,task_description,resolved
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"Change 133395 merged by jenkins-bot:
+Hide PageTriage curation toolbar when VE activates
+
+https://gerrit.wikimedia.org/r/133395",1400110422,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-235ze5es2nor6ps5ebbv,task_subcomment,NA
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"Change 133394 merged by jenkins-bot:
+Fire hook when VE activates/deactivates
+
+https://gerrit.wikimedia.org/r/133394",1400110176,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-235ze5es2nor6ps5ebbv,task_subcomment,NA
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"Change 133395 had a related patch set uploaded by Alex Monk:
+Hide PageTriage curation toolbar when VE activates
+
+https://gerrit.wikimedia.org/r/133395",1400110131,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-235ze5es2nor6ps5ebbv,task_subcomment,NA
+VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates,"Change 133394 had a related patch set uploaded by Alex Monk:
+Fire hook when VE activates/deactivates
+
+https://gerrit.wikimedia.org/r/133394",1400110055,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-235ze5es2nor6ps5ebbv,task_subcomment,NA
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make some edit
+3.Click on Save Page on the Save page dialog
+4.While loading bar is in progress click on ""Review your changes""
+
+
+Observed Result:
+It opens up the Review section while the loading bar is still showing up above and below the dialog.
+
+Environment:Betalabs,test2 and production
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13552}",1400099820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_description,resolved
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy","Change 171474 merged by jenkins-bot:
+Disable review button while save dialog is pending
+
+https://gerrit.wikimedia.org/r/171474",1415234119,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_subcomment,NA
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy","Change 171474 had a related patch set uploaded by Alex Monk:
+Disable review button while save dialog is pending
+
+https://gerrit.wikimedia.org/r/171474",1415230477,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_subcomment,NA
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy",It doesn't do anything while the dialog is pending now. Should we be marking it as disabled though?,1408842605,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_subcomment,NA
+"VisualEditor: The ""Review your changes"" button should be disabled when save dialog is busy",*** Bug 65485 has been marked as a duplicate of this bug. ***,1400507426,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qy3qgp5iqhli5t3ezwmr,task_subcomment,NA
+Vector: Menu items that are hidden should not be made visible by collapsibleTabs,"Add an item to the tab area with class ""collapsible"" and display none applied.
+
+Then make the window narrow (so it moves into the vector menu), and expand again (so it becomes a tab again).
+
+The item is now visible when it was previously hidden.
+
+vector.collapsibleTabs.js should not override this state.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400088600,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-c4o3u3guy4bzz3drfvag,task_description,declined
+Vector: Menu items that are hidden should not be made visible by collapsibleTabs,"I'm not sure that this is the right call, but I also don't really care. :-)",1400541756,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c4o3u3guy4bzz3drfvag,task_subcomment,NA
+Vector: Menu items that are hidden should not be made visible by collapsibleTabs,"Bug 65292 was fixed in a different way, so let's close this.",1400527665,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-c4o3u3guy4bzz3drfvag,task_subcomment,NA
+Vector: Menu items that are hidden should not be made visible by collapsibleTabs,"I am tempted to WONTFIX this. This bug is actually a proposed way of solving bug 65292 in VisualEditor and not a real bug in core. If a tab is supposed to be treated as not being there, then it just should be removed from the DOM (and bug 65292 has a pending patch that does this).",1400346722,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-c4o3u3guy4bzz3drfvag,task_subcomment,NA
+"VisualEditor: When editor is unavailable, edit menu item can re-appear","Steps to Reproduce:
+1.  Open a Wikipedia article in the article namespace. 
+
+2.  Resize the window to a very small size so that the buttons overlap to the next line. 
+
+3.  Resize the window to the original size and see that the ""Edit beta"" button shows up, which was previously not there.
+
+4.  Click on the new button to open VisualEditor.
+
+Actual Results:  
+Clicking the button produces an error message:
+
+Error loading data from server: novenamespace: VisualEditor is not enabled in namespace 4. Would you like to retry?
+
+Clicking OK closes this dialog, but immediately pops up another one of the same kind. 
+
+Expected Results:  
+That the button wouldn't ever be visible, and that if it were, that it wouldn't give an error message about namespace 4.
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1400086320,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-iplno7nvlo3lydwjjepq,task_description,resolved
+"VisualEditor: When editor is unavailable, edit menu item can re-appear","Change 133851 merged by jenkins-bot:
+Remove edit tab from the DOM if it's hidden
+
+https://gerrit.wikimedia.org/r/133851",1400521875,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iplno7nvlo3lydwjjepq,task_subcomment,NA
+"VisualEditor: When editor is unavailable, edit menu item can re-appear","Change 133851 had a related patch set uploaded by Alex Monk:
+Remove edit tab from the DOM if it's hidden
+
+https://gerrit.wikimedia.org/r/133851",1400284010,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iplno7nvlo3lydwjjepq,task_subcomment,NA
+"VisualEditor: When editor is unavailable, edit menu item can re-appear","Rephrasing bug title as bug is broader in scope.
+
+The window resize bug is actually caused by a logic error in Vector in MediaWiki core (filed as bug 65294).
+
+So it affects all browsers, and can bypass any soft restriction that we evaluate in javascript (browser support, namespace, content model, user preference etc.).
+
+Because it's basically just always made to be visible regardless of why it was hidden, when doing the resize handle trick from minimum width back out.",1400088777,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-iplno7nvlo3lydwjjepq,task_subcomment,NA
+"VisualEditor:  Using ""page down"" (PgDn) key to scroll down moves the wrong number of lines if the toolbar is on multiple lines","Steps to Reproduce:
+1. Open a long page in VisualEditor.  Press Ctrl-+ several times, until the toolbar is too wide to fit on a single line.
+
+2. Press PgDn (the page down key).
+
+
+
+Actual Results:  
+The wrong number of lines is moved, so that a couple of lines is never seen.
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399935060,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-7kyxrtyxcyoydu6uyyz6,task_description,open
+"VisualEditor:  Using ""page down"" (PgDn) key to scroll down moves the wrong number of lines if the toolbar is on multiple lines","One more thing ... I just hit Ctrl-+ a second time (my eyes are tired) and ... holy crap, the menu bar takes 3 lines, almost half the screen.
+
+Dan",1400025083,PHID-USER-k5yjhsqwhpwazgdemb6v,True,PHID-TASK-7kyxrtyxcyoydu6uyyz6,task_subcomment,NA
+"VisualEditor:  Using ""page down"" (PgDn) key to scroll down moves the wrong number of lines if the toolbar is on multiple lines","Please see https://en.wikipedia.org/wiki/File:Screenshot1_of_Lamb_article_in_VE,_monobook,_Firefox.png (Windows 7, Firefox 28.0), and after I hit ""Pgdn"" once, https://en.wikipedia.org/wiki/File:Screenshot2_of_Lamb_article_in_VE,_monobook,_Firefox.png. Note that the 2-line VE toolbar takes up enough space that 3 lines from [[Lamb]] are missing between the 2 screens, which makes ""Pgdn"" (and anything else that does the same thing) useless for reading the whole article. Also, the VE toolbar appears to be a lot bigger than it needs to be, both because it takes up 2 lines (if the user has clicked Ctrl-+ at least once, and many do), and because the icons and letters are much larger than they need to be (that is, much larger than the text font).
+
+I'm suggesting that this bug is particularly important because this will be your target viewer's first impression ... in the first few seconds they're exposed to VE, they'll be seeing a much smaller window to edit in (the WP menus including the 2-line VE toolbar take up a quarter of the vertical space), and that paging down is useless for reading the article. Some people make snap judgments based on first impressions.
+
+Dan",1399947739,PHID-USER-k5yjhsqwhpwazgdemb6v,True,PHID-TASK-7kyxrtyxcyoydu6uyyz6,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","https://en.wikipedia.org/wiki/MediaWiki:Visualeditor-cite-tool-definition.json says:
+
+   { ""name"": ""news"", ""icon"": ""ref-cite-news"", ""template"": ""Cite news"" },
+
+
+Shouldn't the ""name"" part determine the name that's showing in the list?
+
+The actual tool says ""newspaper"" instead of ""news"".  I want it to say ""news"" (because the news might come out of a news-magazine or a news-TV show or a news-website, not just a news-paper).
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1399852860,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-a3rrdosrq4m3cjifkopd,task_description,resolved
+"VisualEditor: Change ""newspaper"" to ""news""","Change 133841 merged by jenkins-bot:
+Change Cite > Newspaper to Cite > News
+
+https://gerrit.wikimedia.org/r/133841",1400279196,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","Change 133839 abandoned by Catrope:
+Change label for news citation tool from ""Newspaper"" to ""News""
+
+Reason:
+Abandoning in favor of https://gerrit.wikimedia.org/r/#/c/133841/
+
+https://gerrit.wikimedia.org/r/133839",1400279060,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","Change 133841 had a related patch set uploaded by Catrope:
+Change Cite > Newspaper to Cite > News
+
+https://gerrit.wikimedia.org/r/133841",1400278559,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","(In reply to Gerrit Notification Bot from comment #2)
+> Change 133839 had a related patch set uploaded by Catrope:
+> Change label for news citation tool from ""Newspaper"" to ""News""
+> 
+> https://gerrit.wikimedia.org/r/133839
+
+All done, just pending a yay/nay from James (since I don't wanna go around changing messages without talking to anyone).
+
+Also, sorry for the long turnaround on this, most of the team was at the hackathon in Zürich last weekend and some people took some vacation time around that as well.",1400275905,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","Change 133839 had a related patch set uploaded by Catrope:
+Change label for news citation tool from ""Newspaper"" to ""News""
+
+https://gerrit.wikimedia.org/r/133839",1400275684,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+"VisualEditor: Change ""newspaper"" to ""news""","(In reply to WhatamIdoing from comment #0)
+> https://en.wikipedia.org/wiki/MediaWiki:Visualeditor-cite-tool-definition.
+> json says:
+> 
+>    { ""name"": ""news"", ""icon"": ""ref-cite-news"", ""template"": ""Cite news"" },
+> 
+> 
+> Shouldn't the ""name"" part determine the name that's showing in the list?
+> 
+Not exactly, but close. It means that the name is taken from [[MediaWiki:Visualeditor-cite-tool-name-news]]. The default translation of that message in English is ""Newspaper"", but we could change that to say ""News"" in the software. You could also edit the MediaWiki: page locally but I'd recommend changing it in the software instead to prevent enwiki diverging from the rest of the universe.",1400275603,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-a3rrdosrq4m3cjifkopd,task_subcomment,NA
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),"Just don't.
+
+* https://pl.wikipedia.org/w/index.php?diff=39429954&oldid=38515622
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1399826160,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-kawtquvxo6egab2fazwx,task_description,resolved
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),"Maybe this was invalid. There is a ""Sort this page by default as"" option in the Categories section of the settings dialog, so now it's pretty obvious how one can change or remove that option, but I don't know when this was introduced.",1457516717,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-kawtquvxo6egab2fazwx,task_subcomment,NA
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),Can't reproduce this bug anymore.,1457475200,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kawtquvxo6egab2fazwx,task_subcomment,NA
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),"(To clarify, obviously categories can be removed from an article anytime, but from the diffs it looks like the user has selected and deleted a huge part of text at the bottom of the article, and it doesn't seem that he was there to vandalize it - hence, could be a bug.)",1404662107,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-kawtquvxo6egab2fazwx,task_subcomment,NA
+VisualEditor: Edit led to a DEFAULTSORT entry being removed(?),"Here https://fr.wikipedia.org/w/index.php?title=Henri_D%C3%A8s&diff=105153393&oldid=104979477 and here https://fr.wikipedia.org/w/index.php?title=Henri_D%C3%A8s&diff=next&oldid=105153476 the categories are gone as well. (Wasn't that impossible to do, as per bug 61858?)",1404399512,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-kawtquvxo6egab2fazwx,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,"e.g. in wiktionary semantic classes such as ""distinct feature,"" ""usage example,"" ""syllables,"" ""pronunciation,"" etc.
+
+These would likely be more important for this community than the default preformatted styles used on wikipedia.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399769820,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-uccadm75mlxcgmk4xnec,task_description,open
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,"I'd say that this //may// be wiki-specific, but it should also be possible to make it global.
+
+For now, we don't have global tools, but we should have them (T121470). For tools that are global, this definition should be as global and unified as possible.",1574890274,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,formatting bar,1399816915,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,"To confirm, is this is asking for a tool to wrap selections in templates?",1399814928,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,"It would be good if the addition of the new text styles was as simple as eg. adding of new gadget definitions (instead of having to code long javascript code to add new items in the list)
+
+example:
+
+* usage example | <span class=""usageexample"">{{{1|usage example}}}</span>
+* definition | <dfn class=""definition"">{{{1|definition}}}</dfn>
+
+etc.",1399770721,PHID-USER-xqqqgn2dels45flxw5kb,True,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up,This would likely be a site admin task to add the site specific styles.,1399770008,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-uccadm75mlxcgmk4xnec,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"Please enable VisualEditor as a Beta Feature on Wikimedia Commons, not enabled by default.
+
+Beta features are (as far as I know) completely harmless so I do not think a community discussion is necessary but I would be happy to start one if necessary.
+
+I will post a heads-up on this on Wikimedia Commons village pump.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399639800,PHID-USER-m7etbwqrv6cfrg5ymrwx,False,PHID-TASK-eyop3dml22vuj2xt5thb,task_description,resolved
+Enable VisualEditor as Beta Feature on Wikimedia Commons,Now live.,1400137590,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"Change 132409 merged by jenkins-bot:
+Enable VisualEditor as a Beta Feature on Commons
+
+https://gerrit.wikimedia.org/r/132409",1400109598,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"(In reply to Jean-Fred from comment #2)
+> James told me that by default VE will be active for File, Category, User and
+> main (gallery) namespaces.
+> 
+> Please enable it for Creator: and Institution: too, as pages in these NS use
+> one template, respectively {{Creator}} & {{Institution}}. With TemplateData
+> on them it will be very convenient to use VE to edit them.
+
+Prepared.",1399758277,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"James told me that by default VE will be active for File, Category, User and main (gallery) namespaces.
+
+Please enable it for Creator: and Institution: too, as pages in these NS use one template, respectively {{Creator}} & {{Institution}}. With TemplateData on them it will be very convenient to use VE to edit them.",1399756704,PHID-USER-m7etbwqrv6cfrg5ymrwx,False,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+Enable VisualEditor as Beta Feature on Wikimedia Commons,"Change 132409 had a related patch set uploaded by Jforrester:
+Enable VisualEditor as a Beta Feature on Commons
+
+https://gerrit.wikimedia.org/r/132409",1399640013,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eyop3dml22vuj2xt5thb,task_subcomment,NA
+VisualEditor: Standalone doesn't have an RTL stylesheet,"Build a grunt task out of https://github.com/trevorparscal/cssjanus ?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399629240,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-epbhwclyvevd6ywuakhx,task_description,resolved
+VisualEditor: Standalone doesn't have an RTL stylesheet,"Change 134802 merged by jenkins-bot:
+Use CSSJanus to generate RTL stylesheets
+
+https://gerrit.wikimedia.org/r/134802",1404322307,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-epbhwclyvevd6ywuakhx,task_subcomment,NA
+VisualEditor: Standalone doesn't have an RTL stylesheet,"Change 134802 had a related patch set uploaded by Esanders:
+Use CSS Janus to generate RTL stylesheets
+
+https://gerrit.wikimedia.org/r/134802",1400756554,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-epbhwclyvevd6ywuakhx,task_subcomment,NA
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"The concept of a block slug from a UX POV is great, but why do we need to keep them out of the DM? It seems to be the source of far too many getOffset hacks, as you can put your cursor somewhere that doesn't have a real offset (model-view inconsistency). We already have a way of marking a paragraph as to-be-ignored-by-the-converter-if-empty ({internal:'empty'}), so let's just put them in the DM, and throw them away at convert time if they're empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399621440,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_description,resolved
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"Change 135131 merged by jenkins-bot:
+Stage slugs
+
+https://gerrit.wikimedia.org/r/135131",1412897855,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_subcomment,NA
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"Change 135131 had a related patch set uploaded by Catrope:
+Stage slugs
+
+https://gerrit.wikimedia.org/r/135131",1406919176,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_subcomment,NA
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"Change 135131 had a related patch set uploaded by Jforrester:
+Stage slugs
+
+https://gerrit.wikimedia.org/r/135131",1406767762,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_subcomment,NA
+VisualEditor: Put block slugs in the DM rather than fake them in CE,"Also if we do this we can force the SurfaceObserver to always move cursor positions to content offsets (except for FocusableNodes) which should prevent bugs like Firefox select-all giving you [0,data.length].",1399622043,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hhaov2ntlzzdbxxlqyat,task_subcomment,NA
+VisualEditor: Media dialog search box is blank after the first use; should instead be reset to the page name,"page title in media search box
+
+on any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/0.8782466280521993?veaction=edit
+
+on first page load, select some text in the page, and then open Media
+
+* page title may be in Media search box. see screen shot.
+
+close the Media inspector, select text again, open Media inspector
+
+* Media search box is now blank
+
+** Sometimes selected text is in the Media inspector search box instead of page title.  see other screen shot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64655
+
+**Attached**: {F13511}",1399574700,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ycmbmogx7itnsveopvs4,task_description,resolved
+VisualEditor: Media dialog search box is blank after the first use; should instead be reset to the page name,"Re-writing the bug title; this has nothing to do with the selection.
+
+Fixed in gerrit 143749.",1404405491,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ycmbmogx7itnsveopvs4,task_subcomment,NA
+VisualEditor: Media dialog search box is blank after the first use; should instead be reset to the page name,"Created attachment 15319
+sometimes selected text is in Media inspector search box
+
+**Attached**: {F13512}",1399574773,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ycmbmogx7itnsveopvs4,task_subcomment,NA
+VisualEditor: Pasting plain text from external sources inserts spurious double new lines between paragraphs in Safari,"Intention:
+Paste some plain text.
+
+Steps to Reproduce:
+1. Type a few paragraphs of plain text.  I typed mine into an Apple Mail message with rich text turned off.  My text was:
+
+I get to play with lists.
+I like to play with lists.
+
+I wonder if this will do what I want.
+
+What I want is for this not to be in a list.
+
+
+2. Open VisualEditor.
+
+3. Copy and paste the plain text into VisualEditor.
+
+
+Actual Results:  
+Instead of getting this:
+
+I get to play with lists.
+I like to play with lists.
+
+I wonder if this will do what I want.
+
+What I want is for this not to be in a list.
+
+
+I got this:
+
+I get to play with lists.
+I like to play with lists.
+
+
+I wonder if this will do what I want.
+
+
+What I want is for this not to be in a list.
+
+
+When it saved, there were actually three blank lines between the paragraphs.  This can be seen at http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=92715&oldid=92368
+
+
+Reproducible: Always
+
+This is not the same as Bug 58283.  Also, I could not reproduce this in Firefox 29.  It happens every time in Safari 6.1.3.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399495620,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-vtl6oy2eryypamslyqf3,task_description,open
+VisualEditor: Pasting plain text from external sources inserts spurious double new lines between paragraphs in Safari,Confirmed in Safari 8.0.,1414011489,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vtl6oy2eryypamslyqf3,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","As of May 6th, I am experiencing a lag in switching from VE to Edit source mode, after clicking on Ok on ""Switch to source editing"" dialog, for 5-6 secs, it seems like nothing is happening on my browser. 
+
+This is happening even if I have perfect network speed and all other things loading properly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399489320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_description,resolved
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar",Verified the fix in production,1411682277,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar",Verified the fix in test2,1411081841,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar",Verified the fix in Betalabs,1410984389,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","Change 144505 merged by jenkins-bot:
+Show pending state on action button and keep dialog open when switching to source mode
+
+https://gerrit.wikimedia.org/r/144505",1410911064,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","Change 144505 had a related patch set uploaded by Alex Monk:
+Show pending state and block clicks when switching to source mode
+
+https://gerrit.wikimedia.org/r/144505",1404763221,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","Spinner? Hmm... I've been thinking perhaps mark the switch confirmation dialog as pending and just not close it.
+
+As for blocking overlay... Not sure about what the best way to do that is yet. I assume setting pointer-events:none; on the <body> isn't great.",1404588119,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+"VisualEditor: Switching to source mode should show a spinner, pending state or similar","This is only in beta labs, probably because beta labs is just slow. We should have a spinner and a blocking overlay, though. Right now you can even interact with the surface while we switch to source mode.",1400096282,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-p6ujqrof7r3kr32ikdjk,task_subcomment,NA
+VisualEditor: Vertical cursoring can get cursor stuck on a paragraph-terminal reference in Firefox,"From bug 50726 comment : 
+
+| 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.
+| 3. Press down. (the cursor should now be directly right of of the first reference)
+| 4. 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)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/Jos%C3%A9_Cl%C3%A1udio_Ribeiro_da_Silva?veaction=edit",1399419720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l5466yh2wfhphliediki,task_description,resolved
+VisualEditor: Vertical cursoring can get cursor stuck on a paragraph-terminal reference in Firefox,"I don't recall when, but this is long-since fixed.",1493661863,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l5466yh2wfhphliediki,task_subcomment,NA
+"VisualEditor: [Regression] ""Middle click"" / Cmd+Click on mac no longer open links' targets in a new tab","open in new tab used to work for links while in VE with CMD+Click on mac, this no longer works
+
+Mac 10.9.2 / Chrome Version 35.0.1916.86 beta
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399414860,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-4cw53y6ozxxq4jifc5pd,task_description,resolved
+"VisualEditor: [Regression] ""Middle click"" / Cmd+Click on mac no longer open links' targets in a new tab","Turns out I was wrong and this did already exist - sorry!
+
+*** This bug has been marked as a duplicate of bug 50321 ***",1402552906,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4cw53y6ozxxq4jifc5pd,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version","**Author:** `richlv`
+
+**Description:**
+mw 1.22.6. enabling latest visual editor from git results in :
+""Fatal exception of type MWException""
+
+after some testing, no specific error messages could be seen in apache error log.
+
+according to James_F, ""VE master needs MW 1.23, yes - but it should also fail gracefully when you try to start it, rather than have random fatal errors"" :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399412280,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wio2msjxwwllpptk2lsk,task_description,declined
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version","Well, we won't do anything about MW 1.22 today.
+
+Generally, VisualEditor will show an appropriate error these days when running on unsupported MediaWiki, since {c0c5a028cf82baf79db1f11b36898bd72945dae0}.",1613562732,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version",,1436994300,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version",,1436994281,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version",This also happens with master and MW 1.23,1402558884,PHID-USER-3x5zfm7iedaghxnnelco,False,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version","**richlv** wrote:
+
+master",1399413762,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+"VisualEditor: Fail gracefully (not ""fatal exception"") when being run on MW 1.22.6 rather than supported version","(In reply to richlv from comment #0)
+> enabling latest visual editor from git
+
+Which branch?",1399413414,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-wio2msjxwwllpptk2lsk,task_subcomment,NA
+VisualEditor:  A straight line appears above the image while making it (Frameless/Basic-Left/Right-border),"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it frameless-left-border or basic-left-border 
+
+Observed Result:
+A straight line appears over the image.If you now move the image to center it will go away, but if you again change it to frameless-right-border or basic-right-border from center, the straight line will appear again
+
+
+See the screenshot attacahed
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13981}",1399403760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6w5hbvxithekehcvu66c,task_description,resolved
+VisualEditor:  A straight line appears above the image while making it (Frameless/Basic-Left/Right-border),"This issue is not happening anymore, might got fixed by some changes with image .
+Marking it as resolved .",1404866921,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6w5hbvxithekehcvu66c,task_subcomment,NA
+VisualEditor:  A straight line appears above the image while making it (Frameless/Basic-Left/Right-border),This issue did not get resolved with new image model,1400202049,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6w5hbvxithekehcvu66c,task_subcomment,NA
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"Right now if you have some rich content with an image and paste it into VisualEditor, we discard the image.
+
+However, it'd be nice to add some special handling in VisualEditor's paste for the HTML of images so that those from Commons used on a MediaWiki instance get sought out and inserted instead.
+
+Perhaps via a special custom attribute VE would sniff for, that would make VE try to find the image from Commons (if the wiki was configured for InstantCommons), or other fileRepos?
+
+MediaViewer's ""embed"" HTML looks like:
+
+| <p><a href=""http://commons.wikimedia.org/wiki/File:Beach_sand.jpg#mediaviewer/File:Beach_sand.jpg""><img src=""http://upload.wikimedia.org/wikipedia/commons/c/c5/Beach_sand.jpg"" alt=""Beach sand.jpg"" height=""1200"" width=""1600""></a>[…]</p>
+
+If we asked them to add an attribute, e.g. (simplified):
+
+| <p><a href=""…""><img src=""…"" alt=""…"" ve-data=""ve-pastableImage"" ></a>[…]</p>
+
+… could we do this?
+
+(Also, yes, they should be using <figure> instead of <p><img></p>.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399337460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_description,open
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"(In reply to Tisza Gergő from comment #3)
+> We tried to avoid using the description where a caption is available; the
+> description is often less relevant and too verbose. Also, the caption might
+> be in the right language - copy-pasting images does not necessarily happen
+> across wikis. (I guess we could add a lang attribute, which is a sensible
+> thing to do anyway, and then language mismatch could be detected on paste.)
+
+Yeah, if the <figcaption> had a lang attribute it'd be a lot easier for us, and we'd use that in preference if it were in the content language of the paste target.",1399481558,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_subcomment,NA
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"We tried to avoid using the description where a caption is available; the description is often less relevant and too verbose. Also, the caption might be in the right language - copy-pasting images does not necessarily happen across wikis. (I guess we could add a lang attribute, which is a sensible thing to do anyway, and then language mismatch could be detected on paste.)",1399450066,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_subcomment,NA
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"(In reply to Tisza Gergő from comment #1)
+> At any rate, whether it is in a figure tag figure or something else, users
+> would probably expect the caption to end up inside the image wikicode, not
+> as a HTML wrapper. So I suppose the caption would need special attributes as
+> well?
+
+Sure, or we could fetch the caption from Commons in the context language automatically, so users don't have to be using the right language?",1399339115,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_subcomment,NA
+VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image,"Granted, MediaViewer's HTML format is total crap, but there isn't a clean, semantic way to mark up image captions that works in HTML4. Maybe browsers these days understand HTML5 tags no matter the doctype, and using figure is fine - we should look into that.
+
+At any rate, whether it is in a figure tag figure or something else, users would probably expect the caption to end up inside the image wikicode, not as a HTML wrapper. So I suppose the caption would need special attributes as well?",1399338461,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-63ow7n2ozd4m65ls2xnq,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"mediawiki.Uri does not support IPv6 URIs:
+
+```
+> var uri = new mw.Uri( 'http://127.0.0.1/' )
+undefined
+> var uri = new mw.Uri( 'http://[::1]/' )
+Error: Bad constructor arguments
+```",1399291380,PHID-USER-3dmql6z7s5lnn5lu2vs3,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_description,declined
+mediawiki.Uri does not support IPv6 URIs,"I did T305010 for DiscussionTools mostly as an exercise for myself while learning how to use the `URL` API. But we also had several workarounds for `mw.Uri` bugs, so it seemed like a good thing from a maintenance perspective.
+
+I wasn't planning to make similar changes in VisualEditor, but if you'd also enjoy some exercise ;) , then I'd be happy to review a patch. Generally I don't like making such changes, since they're error-prone, but it's a different thing if it's also fixing a bug (like the editor not loading on IPv6 wikis).",1649283714,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,Thanks for the answer. It’s indeed more safe not to mass-replace since there are different dialects of URLs (I discovered recently [[https://hackerone.com/reports/704621|this not-issue in curl]] and [[https://github.com/bagder/docs/blob/master/URL-interop.md|this document about URL interoperability issues]]).,1649273403,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"@Seb35 Yes and no. The two are not directly compatible, but are similar enough that it's easy for developers to change one to the other in cases where edge cases are known to happen. For example, the VisualEditor team is doing this at T305010.
+
+There are no plans at this time to mass-replace or deprecate mw.Uri. It's a stable module that incurs essentially no maintenance cost for our team to keep providing for a long time as-is. Expect handling of regressions and security issuse, and e.g. any regular maintenance as needed to keep up with external changes (coding practices, browser support etc.). A major shift to support IPv6 with a new internal parser that is yet also backwards-compatible is not currently planned to take place.",1649271885,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"Is there plans to replace `mw.Uri` by `URL`?
+
+I was interested by this task because my test installation is `https://[::1]/mediawiki/master/index.php` (I like edge cases), and the VisualEditor was failing and is still failing since it still uses `mw.Uri`, but more generally there are a lot of users of `mw.Uri`. (no issue for myself, I know how to circumvent this issue by using 127.0.0.1 when needed.)",1649271478,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"Change 759635 **abandoned** by Krinkle:
+%%%[mediawiki/core@master] mediawiki.Uri: Support IPv6 parsing%%%
+Reason:
+%%%Done.%%%
+https://gerrit.wikimedia.org/r/759635",1645032689,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,Declining in favour of T103379.,1645032574,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"Change 759635 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/core@master] Support IPv6 in mw.Uri parsing%%%
+https://gerrit.wikimedia.org/r/759635",1643939933,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"The caller is initDesktop() in Echo, but the underlying problem is T106244.",1602707398,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"The caller is initDesktop() in Echo, but the underlying problem is T265506.",1602707382,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"We don't run with IPv6 URLs in prod, we use hostnames like ""wikipedia.org"".
+
+I'll be a different issue frrom whatever the caller is in that trace, please file a separate task.",1602701569,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"This urfaces as ` TypeError: can't access property ""clone"", defaultUri is undefined` and `Unable to get property 'clone' of undefined or null reference` https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-2020.10.14/clienterror/?id=AXUm60RcLNRtRo5XyfQb",1602699242,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+mediawiki.Uri does not support IPv6 URIs,"On a MediaWiki installation with IPv6 URL like
+http://[::1]/w/index.php
+the class mw.Uri gets not created because it is initialized with
+
+mw.Uri = mw.UriRelative( document.location.href );",1399299571,PHID-USER-3dmql6z7s5lnn5lu2vs3,False,PHID-TASK-7dclqnnm72xwnpvu2eq7,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"Ctrl-Arrow is supposed to move the caret one word in the direction of the arrow.
+
+In RTL wikis it moves too far. It looks like to goes to the next reference or the next sentence rather than the next word.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1399285200,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ebuzshnkdnhhawwjczws,task_description,resolved
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"Change 131767 merged by jenkins-bot:
+unicodejs: Update moveBreakOffset to include 'HebrewLetter' category
+
+https://gerrit.wikimedia.org/r/131767",1399626961,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"Presuming that the rename of this bug is correct, marking this as FIXED.",1399626919,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"Change 131767 had a related patch set uploaded by Esanders:
+Update moveBreakOffset to include 'HebrewLetter' category
+
+https://gerrit.wikimedia.org/r/131767",1399404578,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,"This looks like just a problem with Hebrew. The new Unicode spec introduced a ""HebrewLetter"" group which we didn't add to the WordBreak checker.",1399404357,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew,On a Mac it's Alt-Arrow a.k.a. Option-Arrow.,1399285418,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ebuzshnkdnhhawwjczws,task_subcomment,NA
+VisualEditor: Keyboard shortcut dialog lists heading change incorrectly labelled on Mac,"Noticed on our Wikia integration, and saw that it was incorrect here: https://www.mediawiki.org/wiki/VisualEditor?veaction=edit
+
+http://screencast.com/t/sin5AakmN0
+
+The shortcut list shows that Command plus a number changes the heading value. This is incorrect, as it controls the browser's tabs. The correct label should be ""Command"".
+
+I tested this in latest Firefox and latest Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh",1399069920,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-studawgsnaudqrhmhjyt,task_description,resolved
+VisualEditor: Keyboard shortcut dialog lists heading change incorrectly labelled on Mac,"Change 131596 merged by jenkins-bot:
+Fix command help for CTRL+1-6 on mac
+
+https://gerrit.wikimedia.org/r/131596",1399323217,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-studawgsnaudqrhmhjyt,task_subcomment,NA
+VisualEditor: Keyboard shortcut dialog lists heading change incorrectly labelled on Mac,"Change 131596 had a related patch set uploaded by Esanders:
+Fix command help for CTRL+1-6 on mac
+
+https://gerrit.wikimedia.org/r/131596",1399322977,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-studawgsnaudqrhmhjyt,task_subcomment,NA
+Optimistic saving,"We should adapt the save prediction / optimistic parsing logic in VisualEditor and provide it for the standard wikitext editor. See T58011 for the full description.
+
+Adding Roan as CC since he implemented this for VisualEditor and thus may have useful feedback.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: enhancement",1399063020,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-qnn2vzzsqhnziozjaxbu,task_description,resolved
+Optimistic saving,"Some things to account for:
+
+* Account for use of rev ID parser functions (e.g. don't cache at all)
+* Use of parser timestamp functions lower TTL appropriately (or don't cache in some cases too)
+* Account for user prefs and options fully (they might change before the actual ""save"" click)",1399063632,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-qnn2vzzsqhnziozjaxbu,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Issues right now:
+
+* Different set of elements (e.g. #contentSub is shown in read mode, but not in edit mode. The same goes for TOC, though we do account for that one).
+
+* Different offset (the toolbar is injected which causes an abrupt visual shift).
+
+* Different scroll offset (same as before, but applies when you open the editor when scrolled down the page, after the transition, you're looking at a potentially very different part of the document, we should preserve it or jump to the top, not leave you somewhere randomly).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1399049040,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cnqs3vwq6pny7mken344,task_description,resolved
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,Enough now that I'm going to call this done.,1399344356,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Change 131071 merged by jenkins-bot:
+ve.init.mw.ViewPageTarget: Actually animate the toolbar during setup
+
+https://gerrit.wikimedia.org/r/131071",1399344331,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Change 131074 merged by jenkins-bot:
+ve.init.mw.ViewPageTarget: Hide #contentSub in addition to #toc when muted
+
+https://gerrit.wikimedia.org/r/131074",1399053819,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Change 131074 had a related patch set uploaded by Krinkle:
+ve.init.mw.ViewPageTarget: Hide #contentSub in addition to #toc when muted
+
+https://gerrit.wikimedia.org/r/131074",1399049179,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+VisualEditor: Transition between read mode and edit mode should have minimal visual shifts,"Change 131071 had a related patch set uploaded by Krinkle:
+ve.init.mw.ViewPageTarget: Actually animate the toolbar during setup
+
+https://gerrit.wikimedia.org/r/131071",1399049107,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cnqs3vwq6pny7mken344,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","In Firefox
+
+Steps to reproduce:
+
+1.Open a page with VE in Firefox
+
+2.Insert a media
+
+3.Go to Media Settings of that image
+
+4.Scroll down the dialog box 
+
+Observed Result:
+
+There is no gap between the textbox for Alternative text and the border of the dialog , its almost overlapped with the border as compared to how it appears in Chrome
+
+See the screenshots attached
+
+Test Environment:
+http://en.wikipedia.beta.wmflabs.org/ and 
+https://en.wikipedia.org/
+
+Browser: FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14031}",1398981780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6imkll3gv77iihieqgvg,task_description,resolved
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog",">>! In T66723#709422, @Catrope wrote:
+> The Firefox people disagree that this is a bug: https://bugzilla.mozilla.org/show_bug.cgi?id=748518
+
+It seems they changed their mind a couple years ago, as this bug is now marked as resolved.
+
+I can't reproduce our bug, so maybe it's fixed as a result of that (or maybe something else changed).",1697485607,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","(In reply to Roan Kattouw from comment #2)
+> The PageLayout has 1.5em of padding on all sides. In Chrome, the bottom
+> padding is taken into account in the overflow (i.e. in determining whether
+> to draw a scrollbar and how far down to allow scrolling) while in Firefox it
+> is now. Using bottom margin rather than padding does appear to sort of work
+> in Firefox, but it makes the vertical scroll bar end too early (as it
+> correctly ends before the margin).
+
+The Firefox people disagree that this is a bug: https://bugzilla.mozilla.org/show_bug.cgi?id=748518",1400095736,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","The same issue appears to be in the Reference dialog box as well ,the ""Use this group"" textbox overlaps with the border of the dialog in Firefox",1399926311,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","The PageLayout has 1.5em of padding on all sides. In Chrome, the bottom padding is taken into account in the overflow (i.e. in determining whether to draw a scrollbar and how far down to allow scrolling) while in Firefox it is now. Using bottom margin rather than padding does appear to sort of work in Firefox, but it makes the vertical scroll bar end too early (as it correctly ends before the margin).",1399332578,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog","The PageLayout has 1.5em of padding on all sides. In Chrome, the bottom padding is taken into account in the overflow (i.e. in determining whether to draw a scrollbar and how far down to allow scrolling) while in Firefox it is now. Using bottom margin rather than padding does appear to sort of work in Firefox, but it makes the vertical scroll bar end too early (as it correctly ends before the margin).",1399332503,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6imkll3gv77iihieqgvg,task_subcomment,NA
+VisualEditor: Citation tool should not add empty citation templates,"Steps to Reproduce:
+1. Citation > Cite web
+
+2. Don't add any information.  Just click ""Apply changes"".
+
+Result:  <ref>{{Cite web|url = |title = |date = |accessdate = |website = }}</ref>
+
+That's pointless.  If the fields are blank, don't add it (or remove it).
+
+
+Steps to reproduce, part 2:
+
+1. Citation > Cite web
+
+2. Don't add any information.  Delete all the parameters. 
+
+3. Click ""Apply changes"".
+
+Result:  <ref>{{Cite web}}</ref>
+
+That's even more pointless.  If there are no parameters, don't add it (or remove it).
+
+
+
+
+
+Reproducible: Didn't try
+
+(The ""invalid"" parameter in that diff was manually created by me.  I don't think you can do anything to help the person adding invalid parameters, because there's no way to differentiate between invalid parameter names and valid names that don't happen to be defined in TemplateData.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=91690&oldid=91686",1398976860,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-sfyrbpff7z277arpuv5d,task_description,resolved
+VisualEditor: Citation tool should not add empty citation templates,"Whoops, sorry, wrong bug report :(",1401993942,PHID-USER-evd3wnvnlb66lrwulch4,True,PHID-TASK-sfyrbpff7z277arpuv5d,task_subcomment,NA
+VisualEditor: Citation tool should not add empty citation templates,"Created attachment 15573
+More than one field error
+
+**Attached**: {F14012}",1401993896,PHID-USER-evd3wnvnlb66lrwulch4,True,PHID-TASK-sfyrbpff7z277arpuv5d,task_subcomment,NA
+VisualEditor: Citation tool should not add empty citation templates,"Change 136436 merged by jenkins-bot:
+Don't allow inserting blank citations
+
+https://gerrit.wikimedia.org/r/136436",1401922649,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sfyrbpff7z277arpuv5d,task_subcomment,NA
+VisualEditor: Citation tool should not add empty citation templates,"Change 136436 had a related patch set uploaded by Alex Monk:
+Don't allow inserting blank citations
+
+https://gerrit.wikimedia.org/r/136436",1401478661,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sfyrbpff7z277arpuv5d,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","Intention:
+Edit an existing citation.
+
+Steps to Reproduce:
+1.  Select an existing citation (one using a citation template).
+2.  Press the return key to open it.
+3.  That's odd, I'm in the Reference dialog.  Exit.  
+4.  Re-select the citation.  
+5.  Double-click to open it.  
+6.  That's odd, I'm in the Reference dialog.  Exit.  
+7.  Re-select the citation.  
+8.  Click the little cite-web icon.  That opens the citation tool's simplified dialog.
+
+This happens in both Safari and Firefox, so presumably everywhere. ",1398975240,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_description,resolved
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead",This was fixed some time in the past 3.5 years.,1531409201,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","@jdforrester-WMF If that sounds reasonable to you, I'd like to see this resolved as part of the citations experience work that we're doing in Q3 - it's a UI niggle that can distract from an otherwise dramatically improved experience. Obviously not an issue if made obsolete by a new UI.",1421390457,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","(In reply to Erik Moeller from comment #3)
+> As the citation experience overall has recently improved in leaps and bounds
+> this is one of those issues that sticks out -- any chance we can chop it
+> down soon?
+It's a non-trivial problem. We have some ideas for how to do this, but I need Trevor's brain, and he's been sick all week :(",1406263756,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead",As the citation experience overall has recently improved in leaps and bounds this is one of those issues that sticks out -- any chance we can chop it down soon?,1406263018,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","In talking with Trevor this is going to take quite some time to fix, sadly.
+
+(In reply to WhatamIdoing from comment #1)
+> Once you're inside the Reference dialog, if you double-click the citation
+> template, then it takes you to the Citation tool (rather than to the generic
+> template tool).  I don't know if that's intentional, but it's not obviously
+> wrong.
+
+It's intentional. :-)",1399336402,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+"VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead","Once you're inside the Reference dialog, if you double-click the citation template, then it takes you to the Citation tool (rather than to the generic template tool).  I don't know if that's intentional, but it's not obviously wrong.",1398978720,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-j62lqv2pnnbnbgw7ja53,task_subcomment,NA
+VisualEditor: Link inspector does not highlight/remove default linked text sometimes in automated testing in Chrome,"first word in page text is still in link box after clicking and typing
+
+seen in Chrome only as of 30 Apr: 
+
+as a logged in user on beta labs, invoke VE on a page containing text
+
+without typing or clicking anything else, click the Link icon
+
+the first word in the page text is in the box to create the link
+
+* problem: the text in the link box is not automatically highlighted
+
+click in the link box to create the link text
+
+* problem: default text in the link box that should be highlighted should also be removed when the user clicks in the box to type their own link
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65038
+
+**Attached**: {F13875}",1398867000,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5juvbbzvkfwawhcrnc5e,task_description,declined
+VisualEditor: Link inspector does not highlight/remove default linked text sometimes in automated testing in Chrome,No consistent repro,1401818677,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-5juvbbzvkfwawhcrnc5e,task_subcomment,NA
+VisualEditor: Link inspector does not highlight/remove default linked text sometimes in automated testing in Chrome,I can't reproduce this in Chrome or Firefox on Beta Labs now – possibly a temporary/cached deployment bug?,1398898514,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5juvbbzvkfwawhcrnc5e,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","In Vector/1.24wmf2, the ""Edit source"" tab is not highlighted when editing a page in source mode (no tab is highlighted).
+
+Example:
+http://www.mediawiki.org/w/index.php?title=Help:Preferences&action=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1398829320,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-fsxmbv5x3nocq46ayz64,task_description,resolved
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Verified the fix on Production, Betalabs and Test2",1399410116,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Change 130622 merged by Catrope:
+Preserve pre-existing css classes on edit tab link
+
+https://gerrit.wikimedia.org/r/130622",1398899133,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Change 130622 had a related patch set uploaded by Jforrester:
+Preserve pre-existing css classes on edit tab link
+
+https://gerrit.wikimedia.org/r/130622",1398875579,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Change 130594 merged by jenkins-bot:
+Preserve pre-existing css classes on edit tab link
+
+https://gerrit.wikimedia.org/r/130594",1398875491,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit",*** Bug 64645 has been marked as a duplicate of this bug. ***,1398863834,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","(For the record, yes, confirmed this is broken in production and on latest master).",1398863005,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Change 130594 had a related patch set uploaded by Krinkle:
+Preserve pre-existing css classes on edit tab link.
+
+https://gerrit.wikimedia.org/r/130594",1398862925,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: [Regression wmf22] ""Edit source"" tab for wikitext no longer selected on action=edit","Caused by Ib2e6237483338c8072d5f7919c6459bf7418946a, which overides the 'class' attribute of the original edit tab with 'collapsed'. Thus blowing away the class ""selected"" that MediaWiki core puts there when on action=edit.",1398862419,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fsxmbv5x3nocq46ayz64,task_subcomment,NA
+"VisualEditor: 500 server error from api.php and ""Unknown Error"" appears on the Save dialog box if only a newline is added to the document after a gallery","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Just add a newline by pressing the return
+3.Click on the ""Save Page"" button which got enabled 
+
+Observed Result:
+ ""Unknown Error"" appears on the Save dialog box
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/28thAprilChrome?veaction=edit
+
+**Attached**: {F13652}",1398715020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zxmvdaa5bbdoniada2kf,task_description,resolved
+"VisualEditor: 500 server error from api.php and ""Unknown Error"" appears on the Save dialog box if only a newline is added to the document after a gallery",LGTM. Maybe this was fixed by the changes to the save dialog? Not sure…,1399994453,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zxmvdaa5bbdoniada2kf,task_subcomment,NA
+"VisualEditor: 500 server error from api.php and ""Unknown Error"" appears on the Save dialog box if only a newline is added to the document after a gallery",Am I missing something or has this been fixed? http://en.wikipedia.beta.wmflabs.org/w/index.php?title=28thAprilChrome&diff=94065&oldid=91283,1399991715,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-zxmvdaa5bbdoniada2kf,task_subcomment,NA
+"VisualEditor: 500 server error from api.php and ""Unknown Error"" appears on the Save dialog box if only a newline is added to the document after a gallery","It also shows the following error in the console:
+POST http://en.wikipedia.beta.wmflabs.org/w/api.php 500 (Internal Server Error)",1398715583,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zxmvdaa5bbdoniada2kf,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.In the caption of the image add templates/images/cite notes/math/reference
+4.Click on ""Apply Changes""
+5.Now hover over the image
+
+Observed Result:
+The highlight boxes for templates/images/cite notes/math/references are appearing as well while highlighting the image
+
+See the screenshot attached.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62681
+
+**Attached**: {F13649}",1398710700,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cvfoo26a6vgdda4p5l74,task_description,resolved
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,Verified the fix in production (en.wiki),1403301350,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,Verified the fix in test2 running wmf9,1402694827,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,This seems to be working fine now.There is one single shield appearing over the image even if it has different nodes inside the caption,1402446768,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,"Change 134363 merged by jenkins-bot:
+[BREAKING CHANGE] Merge ProtectedNode into FocusableNode
+
+https://gerrit.wikimedia.org/r/134363",1402442354,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,"Change 134363 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Merge protected node into focusable node
+
+https://gerrit.wikimedia.org/r/134363",1400696169,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE,This did not get resolved with the new image model.Giving it to Moriel .,1400198811,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cvfoo26a6vgdda4p5l74,task_subcomment,NA
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add Heading
+3.Add Subheading 1
+4.Now go to Page Settings and set the option to show the TOC as Always
+
+Observed Result:
+In the TOC inside VE the link to hide the TOC appears as <hidetoc> instead of Hide
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14029}",1398468240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_description,resolved
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""",Verified the fix in production,1400011740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_subcomment,NA
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""",Verified the fix in test2,1399071175,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_subcomment,NA
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""",Verified the fix in Betalabs,1398895706,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_subcomment,NA
+"VisualEditor: When ""__FORCETOC__"" is set, inside VE instead of ""Hide"" the link to hide the TOC appears as ""<hidetoc>""","Change 129852 merged by jenkins-bot:
+Export showtoc and hidetoc messages
+
+https://gerrit.wikimedia.org/r/129852",1398470511,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6jndi54ckbh2pmkgvgw2,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"A screenshot indicating where exactly between the VisualEditor toolbar and the content being edited with VisualEditor the 'Insert' menu becomes hidden under such content being edited
+
+As shown in the attached screenshot, attempting to open VisualEditor's 'Insert' menu causes it to open behind the content of the page that you have opened within VisualEditor.  This occurs when VisualEditor is used in Safari 6.1.3 under OS X 10.8.5 'Mountain Lion' when this OS is run on a mid-2007 aluminum iMac with a 2.4-GHz Intel Core 2 Duo processor, 4 GB of 667-MHz DDR2 SDRAM, and an ATI Radeon HD 2600 Pro with 256 MB of dedicated VRAM.  For some reason, though, this bug has been somewhat intermittent over the past month or so (it showed up for a while at first, then appeared as if it had been fixed before whatever patch that fixed it was reverted or otherwise messed with.)  Is my bug a duplicate of another one even though I couldn't find a similar one via Bugzilla's search mechanism?  If so, have there been notices in the comments of this other bug about its status?
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Mac OS X 10.9
+**Platform**: Macintosh
+
+**Attached**: {F13846}",1398369840,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_description,invalid
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"This issue went away for me shortly before I updated my system to OS X 10.10.x 'Yosemite' and Safari 8.0.x and has not resurfaced since then.  I'm assuming that somebody fixed this by resolving a related issue and am, as such, closing it as 'Invalid' since it no longer describes behavior under the currently used versions of MediaWiki.  ",1427663679,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,@WhatamIdoing:  Methinks that the problem is highly exacerbated by the use of Safari Extensions (see comment 2 for the full list of stuff I had on my computer when this bug first appeared for me.),1412633895,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Assuming that the steps to reproduce are:
+
+1.  Read Wikipedia article in Safari.  Zoom in at least twice (Command-+).
+
+2.  Open page in VisualEditor.
+
+3.  Click on drop-down menus (e.g., the character formatting menu).
+
+then I cannot reproduce this today in Safari 6.2 on Mac OS 10.8.5.",1412627563,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Ah, I see; that *would* be a problem since Apple no longer supplies current versions of Safari to Windows users.  It seems to me, however, that this bug has been fixed for users of Safari 7.1 (9537.85.10.17.1), to which I updated a little while back, by recent changes to either WebKit or the MediaWiki software.  Since I no longer have either Safari 6.1.3 or Safari 7.0.5, could anybody check to see if this bug still exists for those versions of Safari?",1412543272,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,I'd love to help but I don't own a Mac. :(,1412366537,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,Any progress on fixing the zooming issue?,1411834869,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"P. P. S.:  It turns out that VisualEditor's menus load properly if you reset Safari's zoom level before clicking on 'Edit [beta]' even if you then zoom in afterwards!  Crazy, right?",1407786576,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"P. S.:  I just looked at the duplicate bug, number 67741, and I realized that I *always* zoom in by two levels when I use Wikipedia!  I will therefore check to see if VisualEditor works normally when I'm not zoomed in at all before you guys have me do any deeper testing, all right?",1407781848,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to James Forrester from comment #22)
+> (In reply to Bryce Glover from comment #21)
+> > I'm still seeing this bug with Safari 6.1.4, guys; maybe it's more serious
+> > than we all think?  It would be really nice if we could figure out what's
+> > going on here, because it's really annoying for me to not be able to use
+> > VisualEditor since it's such a great product (I can't even access the
+> > 'Switch to Source Editing' command since the menus hide behind page content!)
+> 
+> Hey, sorry, please re-open bugs if you think more work needs to be done on
+> them. This bug was lost to the mists of time (bugs marked RESOLVED/VERIFIED
+> are only looked at by happenstance). :-(
+> 
+> Unfortunately I don't have access to Safari 6.1.x here, and I still can't
+> replicate in Safari 6.0.5 or 7.0.4/5 – and given that only security updates
+> and a sidebar were added, it seems almost certain that the issue is specific
+> to your setup somehow. Re-opening but I'm not sure if there's anything we
+> can do…
+
+Well, I just updated my system to OS X 10.9.4 'Mavericks,' which contains Safari 7.0.5, and the menus *still* refuse to come out from underneath the content of any page that I might be trying to edit with VisualEditor.  (Speaking of this component, why did you change this bug's summary to indicate that it's a bug in OOJs rather than a bug in VisualEditor?  Is VisualEditor partly implemented OOJs, and do you suspect that this part of its implementation may be causing me my problems with VisualEditor?)  So, you may be right that my seeing this bug has something to do with my setup.  Do you want me to disable my Extensions again and empty my caches and then try using VisualEditor again?  How about re-enabling Safari's Extensions framework without enabling any of my installed extensions and then troubleshooting my installed extensions one by one to see which one causes the error?  I'll attach any error messages that pop up in my console when I run that test to this bug if you have me do so.  In addition, should I maybe contact either Apple or the developer of whichever Extension turns out to be the culprit and ask them to help us squash this bug once we figure out what's going on here?  I'd really *love* to solve this problem; it's driving me *nuts* that I can't use VisualEditor properly!",1407781542,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,*** Bug 67741 has been marked as a duplicate of this bug. ***,1404965618,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #21)
+> I'm still seeing this bug with Safari 6.1.4, guys; maybe it's more serious
+> than we all think?  It would be really nice if we could figure out what's
+> going on here, because it's really annoying for me to not be able to use
+> VisualEditor since it's such a great product (I can't even access the
+> 'Switch to Source Editing' command since the menus hide behind page content!)
+
+Hey, sorry, please re-open bugs if you think more work needs to be done on them. This bug was lost to the mists of time (bugs marked RESOLVED/VERIFIED are only looked at by happenstance). :-(
+
+Unfortunately I don't have access to Safari 6.1.x here, and I still can't replicate in Safari 6.0.5 or 7.0.4/5 – and given that only security updates and a sidebar were added, it seems almost certain that the issue is specific to your setup somehow. Re-opening but I'm not sure if there's anything we can do…",1404849255,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"I'm still seeing this bug with Safari 6.1.4, guys; maybe it's more serious than we all think?  It would be really nice if we could figure out what's going on here, because it's really annoying for me to not be able to use VisualEditor since it's such a great product (I can't even access the 'Switch to Source Editing' command since the menus hide behind page content!)",1403810479,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Created attachment 15289
+Safari 6.1.3 JavaScript Console Logs for https://en.wikipedia.org/wiki/Foobar?veaction=edit
+
+As this title says, this attachment contains the JavaScript console logs which Safari 6.1.3 running on OS X 10.8.5 'Mountain Lion' provided for the URL 'https://en.wikipedia.org/wiki/Foobar?veaction=edit'.
+
+**Attached**: {F13848}",1399233089,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Andre Klapper from comment #18)
+> The ""Add an attachment"" link should work, unrelated to bug status.
+
+Oh, wait; I see it, but it moved from below the 'Additional Comments:' dialog box to below the list of attachments to this bug at the top of the page.  Stupid me; I should have looked first!",1399227158,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"The ""Add an attachment"" link should work, unrelated to bug status.",1399198199,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #16)
+> (In reply to Bryce Glover from comment #15)
+> > Maybe I should disable my Extensions and then turn them back on one by one
+> > to figure out which one is causing the problem?  That way, I could contact
+> > that plug-in's developer and discuss the bug with him or her.
+> 
+> Okay, guess what?  It's apparently *Apple's* fault since this bug occurs for
+> me with Extensions enabled (it goes away when they aren't — yay!) but (get
+> this!) *no extensions enabled*.  I'll attach what my error console gives me
+> to this bug in a sec.
+
+Sorry about changing the bug status; I thought that doing so would bring back the 'UNRESOLVED' option so that I could attach a picture of my browser's console logs for that page to which you sent me a link.  Could somebody un-'RESOLVED WONTFIX' this for me so that I can do this, or am I on my own here?",1399147476,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #15)
+> Maybe I should disable my Extensions and then turn them back on one by one
+> to figure out which one is causing the problem?  That way, I could contact
+> that plug-in's developer and discuss the bug with him or her.
+
+Okay, guess what?  It's apparently *Apple's* fault since this bug occurs for me with Extensions enabled (it goes away when they aren't — yay!) but (get this!) *no extensions enabled*.  I'll attach what my error console gives me to this bug in a sec.",1399147170,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Maybe I should disable my Extensions and then turn them back on one by one to figure out which one is causing the problem?  That way, I could contact that plug-in's developer and discuss the bug with him or her.",1399146493,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #12)
+> OK, I know that the version of Firefox which I mentioned (17.0.1) works just
+> fine even when I'm logged in to Wikipedia as myself (I didn't see the
+> 'Edit^[beta]' link when I wasn't,) so it's got to be something in Safari
+> 6.1.3 that's going wrong.
+
+That's unfortunate. I've tried it with Safari 6.0.5 and it works as expected; this is either a very odd problem with a sub-version of Safari (which is unlikely) or caused by a browser plugin. I don't really like to close such bugs as ""WORKSFORME"" but there's nothing much I can offer at this point, sadly…",1399076933,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Created attachment 15283
+Screenshot of no issue in Safari 6.0.5
+
+**Attached**: {F13847}",1399076820,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #11)
+> (In reply to James Forrester from comment #10)
+> > (In reply to Bryce Glover from comment #9)
+> > > (In reply to James Forrester from comment #6)
+> > > > Would it be possible for you to visit
+> > > > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> > > > Safari, and/or in a different browser, and see if it recurs?
+> > > 
+> > > Yup; it still occurs even while I'm logged out of Wikipedia.  I've also
+> > > confirmed that all of the other menus ('Paragraph' — that's a styling menu,
+> > > right? — and the ones labeled with a question mark inside of a circle —
+> > > 'Help', maybe? — , a triangular warning sign — could this be 'Report a
+> > > Problem?' — , and a column of stacked lines — I'm assuming that this means
+> > > 'More Options') open with their menus tucked under the content of the page
+> > > that is being edited with VisualEditor.
+> > 
+> > Thanks. I take it this is still with Safari 6.1.3 with all your plugins,
+> > whilst logged out?
+> 
+> That's right.  Hold on, though; I forgot to check Firefox 17.0.1 (yeah, I
+> know; I'll remind my dad to update it as soon as I can…)
+
+OK, I know that the version of Firefox which I mentioned (17.0.1) works just fine even when I'm logged in to Wikipedia as myself (I didn't see the 'Edit^[beta]' link when I wasn't,) so it's got to be something in Safari 6.1.3 that's going wrong.",1399057745,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to James Forrester from comment #10)
+> (In reply to Bryce Glover from comment #9)
+> > (In reply to James Forrester from comment #6)
+> > > Would it be possible for you to visit
+> > > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> > > Safari, and/or in a different browser, and see if it recurs?
+> > 
+> > Yup; it still occurs even while I'm logged out of Wikipedia.  I've also
+> > confirmed that all of the other menus ('Paragraph' — that's a styling menu,
+> > right? — and the ones labeled with a question mark inside of a circle —
+> > 'Help', maybe? — , a triangular warning sign — could this be 'Report a
+> > Problem?' — , and a column of stacked lines — I'm assuming that this means
+> > 'More Options') open with their menus tucked under the content of the page
+> > that is being edited with VisualEditor.
+> 
+> Thanks. I take it this is still with Safari 6.1.3 with all your plugins,
+> whilst logged out?
+
+That's right.  Hold on, though; I forgot to check Firefox 17.0.1 (yeah, I know; I'll remind my dad to update it as soon as I can…)",1399057471,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #9)
+> (In reply to James Forrester from comment #6)
+> > Would it be possible for you to visit
+> > https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> > Safari, and/or in a different browser, and see if it recurs?
+> 
+> Yup; it still occurs even while I'm logged out of Wikipedia.  I've also
+> confirmed that all of the other menus ('Paragraph' — that's a styling menu,
+> right? — and the ones labeled with a question mark inside of a circle —
+> 'Help', maybe? — , a triangular warning sign — could this be 'Report a
+> Problem?' — , and a column of stacked lines — I'm assuming that this means
+> 'More Options') open with their menus tucked under the content of the page
+> that is being edited with VisualEditor.
+
+Thanks. I take it this is still with Safari 6.1.3 with all your plugins, whilst logged out?",1399057369,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to James Forrester from comment #6)
+> Would it be possible for you to visit
+> https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> Safari, and/or in a different browser, and see if it recurs?
+
+Yup; it still occurs even while I'm logged out of Wikipedia.  I've also confirmed that all of the other menus ('Paragraph' — that's a styling menu, right? — and the ones labeled with a question mark inside of a circle — 'Help', maybe? — , a triangular warning sign — could this be 'Report a Problem?' — , and a column of stacked lines — I'm assuming that this means 'More Options') open with their menus tucked under the content of the page that is being edited with VisualEditor.",1399057226,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to James Forrester from comment #6)
+> Would it be possible for you to visit
+> https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in
+> Safari, and/or in a different browser, and see if it recurs?
+
+Doing now…",1399056754,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Andre Klapper from comment #5)
+> (In reply to Bryce Glover from comment #4)
+> > Has this been fixed yet
+> 
+> If it was fixed, the status of this ticket was RESOLVED FIXED.
+> 
+> As long as only one user has ran into this issue and steps to reproduce are
+> unclear, it's likely not a high priority.
+
+Ah, sorry; I was getting a little impatient, not to mention worried!  I'm relatively new to Bugzilla, so, duh:  I should have thought, ""Oh!  It hasn't been marked as 'RESOLVED FIXED' yet.""  Now I feel ignorant…heh, heh.  (sheepish smile)",1399056693,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Sorry for the brief delay.
+
+I am unable to reproduce this for default-setup users on the English Wikipedia in Safari 7.0.3, in default Vector or Monobook, or whilst logged in with fewer gadgets switched on.
+
+Though it's theoretically possible that there's a rendering difference between Safari 6.1.3 and 7.0.3 in this respect, it's very unlikely, and I would assume the bug is caused by a browser plugin or a gadget.
+
+Given that you're getting the same behaviour on a different site (meta as well as enwiki), it's most likely to be a browser plugin issue (though none of your plugins look suspicious at first glance).
+
+Would it be possible for you to visit https://en.wikipedia.org/wiki/Foobar?&veaction=edit whilst logged out in Safari, and/or in a different browser, and see if it recurs?",1399045851,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"(In reply to Bryce Glover from comment #4)
+> Has this been fixed yet
+
+If it was fixed, the status of this ticket was RESOLVED FIXED.
+
+As long as only one user has ran into this issue and steps to reproduce are unclear, it's likely not a high priority.",1399031037,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Has this been fixed yet, or did everybody forget about me?",1398969156,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"I've just found out that this bug also occurs for another menu (the 'Formatting' one — that's what the menu with an icon that looks like an underlined capital 'A' is called, right?) at en:meta under my user environment.  I'll update this bug with my results as I try and use other menus in VisualEditor at other wikis.",1398538597,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"Yes; I have several modifications installed as modifications both to my local copy of Safari and to my Wikipedia account (I was experiencing this bug on the English WP.)  In Safari, I have the 'Duplicate Tab' Button 2.0, Print Plus 1.1.0.2, Middle-Click AutoScroll 1.04, TabLock 1.1, Search Preview 1.2.3, Tab Reloader 1.5.2, Session 1.3.0.2, Feedly 16.0.5.21, and Ultimate Status Bar 1.3 extensions installed and enabled and the Cuss Off 1.1, MacRumors Minimal 1.7, and Lazarus Form Recovery 3.2 extensions installed, but disabled.  The en:wp Gadgets that I have enabled in my preferences are, as listed on en:wp:Special:Gadgets, Gadget-searchFocus.js, Gadget-ImageAnnotator.js, Gadget-imagelinks.js, Gadget-popups.js/Gadget-navpops.css, Gadget-PrintOptions.js, Gadget-revisionjumper.js, Twinkle, Gadget-HideFundraisingNotice.js/Gadget-HideFundraisingBanner.css, Gadget-teahouse.js/Gadget-teahouse.css, Gadget-WatchlistChangesBold.js/Gadget-WatchlistChangesBold.css, Gadget-defaultsummaries.js, Gadget-citations.js, Gadget-HotCat.js, Gadget-wikEd.js, Gadget-afchelper.js, Gadget-DRN-wizard-loader.js, Gadget-edittop.js/Gadget-edittop.css, Gadget-UTCLiveClock.js, Gadget-mySandbox.js, Gadget-purgetab.js, Gadget-externalsearch.js, Gadget-dropdown-menus.js/Gadget-dropdown-menus.css, Gadget-CommentsInLocalTime.js, Gadget-NoSmallFonts.css, Gadget-metadata.js, Gadget-MenuTabsToggle.js/Gadget-MenuTabsToggle.css, Gadget-JustifyParagraphs.css, Gadget-righteditlinks.css, Gadget-PrettyLog.js/Gadget-PrettyLog.css, Gadget-SidebarTranslate.js/Gadget-SidebarTranslate.css, Gadget-widensearch.css, Gadget-DejaVu Sans.css, Gadget-contribsrange.js, Gadget-BugStatusUpdate.js, Gadget-RTRS.js, and Gadget-NewImageThumbs.js/Gadget-NewImageThumbs.css.  The beta features that I am using on en:wp are 'New search,' 'Media Viewer,' 'VisualEditor,' 'VisualEditor formulae editing,' and 'Compact language links.'  (Maybe I should open another new bug labeled as an 'enhancement' asking for users to have the ability to export their Gadget and Beta Features settings as a CSV file so that they don't have to type them all out when they need to submit them as pieces of technical information for help with bugs?)",1398535237,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in,"What skin are you using, and do you have any gadgets or local user scripts or styling that might be competing?",1398371393,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a4rtuxfqfzt4t5rmm2ac,task_subcomment,NA
+"VisualEditor: In Firefox, the context menu's background sometimes does not appear for items inside a media caption (but the icons appear still)","cite icon not having any layout
+
+Steps to reproduce:
+
+
+1.Open a page with VE in Firefox
+2.Insert a media file
+3.Now go the media settings for this image
+4.Add some cite options and reference inside media settings icon
+
+Observed Result:
+
+Just after adding the cite options and references, observe that the icon layouts for cite options and reference are missing
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13698}",1398292980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cdonwzrog6i3xfchvyc6,task_description,resolved
+"VisualEditor: In Firefox, the context menu's background sometimes does not appear for items inside a media caption (but the icons appear still)",Probable browser bug. Fun.,1401323667,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cdonwzrog6i3xfchvyc6,task_subcomment,NA
+"VisualEditor: In Firefox, the context menu's background sometimes does not appear for items inside a media caption (but the icons appear still)",Needs investigation as to the cause.,1400138573,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cdonwzrog6i3xfchvyc6,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Template parameter input with one line of text
+
+If I am entering text for a template parameter and then I press enter to start a new line, the input box remains the same (small) vertical size and the first line of text disappears. A very small scroll handle appears at the right, but it is not obvious that this is what it is.
+
+Press enter again to add a third line will enlarge the input box so that both the second and third lines are visible, and the dark grey scroll handle disappears (but the light grey slot for it remains. Once it gets to four lines it starts working as expected.
+
+This input box should expand enough with the first few lines, at least, that no scrolling is even necessary. By the time it becomes necessary, it should already be large enough that the scroll handle will be recognizable to users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13516}",1398186840,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-cfl3njg4dbpxcmrct57o,task_description,duplicate
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Maybe a browser bug. It happens to me (still) in Iceweasel (Debian Jessie), but not in Chromium.",1401422499,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"This is very odd. Browser bug, maybe? This isn't the behaviour for me in Chrome, Safari, Opera or Firefox here…",1401417704,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Created attachment 15164
+Template parameter input with four lines of text
+
+**Attached**: {F13519}",1398186951,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Created attachment 15163
+Template parameter input with three lines of text
+
+**Attached**: {F13518}",1398186931,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?),"Created attachment 15162
+Template parameter input with two lines of text
+
+**Attached**: {F13517}",1398186910,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-cfl3njg4dbpxcmrct57o,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,"Related to bug 48560?
+IP editor reports that when he removed categories from this category https://it.wikipedia.org/w/index.php?title=Categoria%3AMarketing&diff=65461531&oldid=60402800 , all he could see after he saved was the category description.
+The category tree and the list of the categories at the bottom only appeared after refreshing the page.
+
+His setup: Firefox 28.0 , Vector, Windows 7
+I reproduce the same issue with that setup in this edit: https://it.wikipedia.org/w/index.php?title=Categoria%3AVisualEditor&diff=65497855&oldid=64118006 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1398172860,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5gjtponbzcvgfibouvua,task_description,resolved
+VisualEditor: Need to refresh to see category tree and updated footer on category page,"Change 136311 merged by jenkins-bot:
+On category pages, only replace category description when saving
+
+https://gerrit.wikimedia.org/r/136311",1401736962,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,"Change 136311 had a related patch set uploaded by Alex Monk:
+On category pages, only replace category description when saving
+
+https://gerrit.wikimedia.org/r/136311",1401455301,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,Presumably this is pretty trivial?,1401408780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,*** Bug 65925 has been marked as a duplicate of this bug. ***,1401408756,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+VisualEditor: Need to refresh to see category tree and updated footer on category page,Sounds like the same problem as for File: pages.,1400869847,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5gjtponbzcvgfibouvua,task_subcomment,NA
+Define an official thumb API,"See also:
+* {T89971}
+
+------
+
+
+MediaWiki never had an official API for the retrieval of thumbnailed images. Existing thumb URLs are considered private, and are not designed for use as a public API. Instead, clients are supposed to request a URL individually from the action API. This complicates API design and API response caching whenever the response references a thumb, and makes it difficult to dynamically select image size or quality in a client.
+
+The move to content-based addressing could provide a good opportunity to address this by defining a simple and stable thumb API.
+
+### Use cases / problem statement
+
+- **Dynamic client-side thumb size / quality selection without extra round-trips**: Clients would like to adapt image size and quality to actual network and device characteristics. Most current techniques for lazy-loading and dynamic resource selection are using JS. Having the ability to select the thumb size and quality in this code without extra round-trips would enable interesting performance optimizations.
+
+- **Caching of API responses referencing thumbnails**: Many cached API responses (such as [summary](https://rest.wikimedia.org/en.wikipedia.org/v1/?doc#!/Page_content/get_page_summary_title) or [related pages](https://rest.wikimedia.org/en.wikipedia.org/v1/?doc#!/Page_content/get_page_related_title)) contain references to thumbnails. Currently, there is no way for clients to sanely select thumb sizes, which means that we either need to fragment caches on thumb size, or try to include several sizes in the response. Good caching of API responses is becoming more pressing as high-traffic features like hovercards (see T70860) are built as direct API consumers. The need to negotiate thumb sizes supported by API end points introduces delays, and reduces the design flexibility in clients. 
+
+- **Image info caching**: Parsoid and other clients like VisualEditor currently need to request image information in order to render thumbnails. Those requests are very common, making imageinfo one of the most-used API entry points. Currently, the request necessarily contains the desired thumb size, which renders caching of imageinfo responses ineffective. If the response was dimension-independent instead, most of these responses could be served directly from caches. This would reduce response latency and load on the API cluster and related infrastructure.
+
+### API requirements
+
+- Simple selection of thumb size and -quality without a need for extra API calls.
+- Avoid cache fragmentation with deterministic URLs.
+- Support for encoding complex options in a uniform and extensible manner, without breaking existing use cases or introducing non-determinism.
+- Optional support for content negotiation (ex: client hints) in the future.
+- Support migrating to hash-based image identification in a later stage.
+
+## API proposal: Use query strings
+
+- `/v1/someimage.jpg`: Original. Returned by API end points referencing thumbnails. 
+- `/v1/someimage.jpg?w=220`: JPG thumb 220px wide. 
+- `/v1/someimage.jpg?p=22&w=500`: 500px thumb of page 22 in a multi-page document.
+- `/v1/someimage.jpg?t=2m30s&w=220`: Thumb of a video at 2m30s.
+- `/v1/someimage.jpg?lang=fr&w=220`: Thumb of an SVG, rendered to a PNG using French texts. We aren't explicitly mentioning the file format, so the client does not need to know that the original is an SVG, or that it is rendered to a PNG image.
+
+Server side requirements:
+
+- Audit and document the [existing query string API](https://commons.wikimedia.org/w/thumb.php?f=Camera2_mgx.svg&w=100&lang=fr) in [thumb.php](https://github.com/wikimedia/mediawiki/blob/master/thumb.php). T153497
+- Add strict parameter validation. Each thumb should have only a single URL. Don't allow unknown parameters, and (generally) avoid specifying default values explicitly. Exceptions can be made for page & time offset parameters, where little actual fragmentation is expected, and consistency in the use of the parameter is important.
+- Query string order normalization in Varnish (vmod): T138093
+
+### Providing original dimensions to clients
+
+In order to accurately calculate and select thumbnail dimensions, clients need to know the original image's dimensions (where applicable). Using this informations, clients can then construct a unique URL for a given thumbnail size, independent of the constraints it applied to select this size. They can also avoid content jumping around by updating image dimensions to the exact thumbnail dimensions, before the thumbnail has loaded. 
+
+Currently, MediaWiki already provides original dimensions in `data-file-{width,height}` attributes for MediaViewer's benefit. Some API responses referencing thumbnails include the equivalent information in JSON:
+
+```
+image: {
+  src: ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12"",
+  width: 640,
+  height: 480
+}
+```
+
+We can either stick to these different formats, or consider unifying this information in the URL, either in query parameters (**`/someimage.jpg?oh=768&ow=1024&w=100`**), or separately in a fragment (**`/someimage.jpg?w=100#oh=768&ow=1024`**). The latter avoids sending back purely informational parameters to the server.
+
+
+### Pros
+
+- Familiar query string syntax with wide parsing support.
+- Does not distinguish between advanced & frequently changed properties.
+
+### Cons
+
+- Requires custom ordered query string serialization code for both simple (size, quality) & more complex use cases.
+  - Subtlety of ordering requirement (still works) means that users will often ignore it, causing client side cache fragmentation.
+- Need for general query string normalization in Varnish. Weak con, as this would be generally useful.
+
+## Options for content negotiation and -selection
+
+We would like to use modern thumbnail formats where this has a benefit for users, but need to make sure that we don't break older clients with insufficient support in the process.
+
+The two main approaches for this content negotiation process are: 
+
+a) Server-side HTTP content negotiation, using client supplied headers like `accept`, and
+b) client-side JS explicitly requesting specific formats.
+
+There are pros & cons to either method, and they aren't mutually exclusive. HTTP content negotiation can work without any client-side effort for bitmap formats (ex: Chrome advertises WebM support). Client side JS can add explicit parameters for more fine-grained control, but also has only limited information to base such decisions on.
+
+Either way, the status quo and starting point is to serve widely supported formats (JPG and PNG) by default. We don't need to solve this question right away, and the proposed API is leaving all options for content negotiation open.
+
+## Deployment strategy
+
+A change like this isn't complete without a strategy that allows us to roll out new-style thumbs gradually. To avoid performance impacts, all (simple) requests for a thumb of a given size should map to the same cache entries using either URL scheme. To this end, we can roll things out in a way that lets us *rewrite* one URL scheme to the other.
+
+- New to old style:
+
+  - Simple thumbs (only width parameter specified):
+    1) Prefix the image name with the width parameter value followed by 'px-'.
+    2) Calculate the MD5 of the image name, and prefix first & first two chars of hex encoding to path (ex: `/7/72/`).
+  - Complex thumbs: Let PHP code handle the request & cache the response separately.
+- Old to new style:
+  - Simple thumbs (need to check if we can determine this with a regex):
+    1) Extract & strip width parameter
+    2) Send a request with a query string to backend
+  - Complex thumbs: Let PHP code handle the request & cache the response separately.
+
+
+### Users / apps making assumptions about the current thumb URL format
+
+See T153498.
+
+### Migration strategies in Varnish
+
+- Feasibility of rewriting majority of ""simple"" thumbnails (no key-value parameters) in Varnish.
+- Feasibility of avoiding redirect latency penalty by resolving redirect responses from thumb service in Varnish.
+
+## Small MediaWiki installs
+
+Currently, MediaWiki defaults to serving thumbnails directly from an upload directory. This means that there is no PHP code involved in serving thumbnails. This is good for performance (especially without caching), but also means that on-demand generation & a parameter-based API cannot be supported out of the box. There are several options we can pursue:
+
+1) Start to serve all thumbs through thumb.php (or an API module). The migration to this would generally be easy (especially with the API), but we would add the overhead of serving thumbs through PHP. Authentication would be supported out of the box. Caching could eliminate the performance issue for higher volume installs, or in an appliance container install that includes Varnish.
+2) Create a new way of supporting direct file serving with 404 handler and storage based on encoded query strings. This requires an advanced web server configuration, and might not be possible with less common web servers.
+
+At this point, the default option would be 1), but we can always optimize the setup with 2). We can provide 2) by default in a container-based distribution solution.
+
+
+",1398126240,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_description,open
+Define an official thumb API,"The swap of #traffic for #traffic-icebox in this ticket's set of tags was based on a bulk action for all such tickets that haven't been updated in 6 months or more.  This does not imply any human judgement about the validity or importance of the task, and is simply the first step in a larger task cleanup effort.  Further manual triage and/or requests for updates will happen this month for all such tickets.  For more detail, have a look at the extended explanation on the main page of #traffic-icebox .  Thank you!",1630538491,PHID-USER-lhtlnmkdbzlz6pbxaqdd,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592583998,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@jdrewniak shared a pointer to the https://cloudinary.com API which I thought could be a source of inspiration for this task. Be sure to check out their [[ https://cloudinary-res.cloudinary.com/video/upload/ac_none,c_scale,h_388,q_40,w_1170/manipulation_video.mp4 | 57 second demo ]].",1530805718,PHID-USER-6tlavgtsosjuvizsej53,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ugh, I am really sorry, I don't know how I could misread that so badly :( I guess my eye is trained to react to the word ""Declined"" in Phabricator emails, without reading them properly.",1522375690,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr we are just putting it in the Declined TechCom-RFC workboard, not in Phabricator as a whole. For reference, this is how we approach declining RFCs now: https://phabricator.wikimedia.org/T184653
+
+TechCom is declining at this time but will be more than happy to discuss further RFCs on this topic in the future (noting that @Fjalapeno mentioned interest in picking this up). ",1522328886,PHID-USER-a3ndrbmqqq7sb7olfps4,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#4086547, @kchapman wrote:
+> The other issue we see is there should be multiple RFCs broken out for that. Perhaps that means this is not an RFC, but an overall task that has RFCs linked to it. 
+
+I would disagree, I don't think this RfC can be meaningfully broken up. There are a few ideas it mentions but does not actually propose to do (hash-based identification, content negotiation) and those could be removed for clarity, but that's all I can see.
+
+But regardless, even if the task is not a real RfC, that's not a good reason to decline it as a Phabricator task. Probably the RfC project tag should just be removed in that case.",1522191134,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr perhaps I was not as clear as I could have been. The other issue we see is there should be multiple RFCs broken out for that. Perhaps that means this is not an RFC, but an overall task that has RFCs linked to it. 
+
+I will bring up the process in the next TechCom meeting. ",1522188019,PHID-USER-a3ndrbmqqq7sb7olfps4,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The problem here is that TechCom is using Phabricator in a different way from the rest of the movement.
+
+The normal way is that you create one task for one concept / task, and multiple groups share that task and do their workflow management in such a way that it does not conflict with that of other groups. That means using projects or workboards (since there can be any number of those but there is only one task status). Declining a task means that it was decided that it should not be done (ie. people should be actively prevented from doing it) because it is a bad idea. Most tasks are not resourced but kept open (or stalled) nevertheless.
+
+So if TechCom insists on their current workflow, it should make it clear that it prefers a different workflow, and for every idea that goes through the TechCom process there should be a separate idea task and a separate RfC task so that the TechCom can decline the RfC task when there is no resourcing, while the idea task can be kept open as something that's potentially still valid; and the existing RfC tasks should be split in two. Or TechCom should change their workflow to match that of everyone else on Phabricator, and use a workboard column or the removal of the TechCom tag or something similar for tracking ""rejected without prejudice"".
+
+In either case please keep this task open, whether it gets resourced in the near future or not. The use cases described here are still valid, the solution proposed here still captures our best understanding of the solution space, declining it would be confusing and hamper the use of Phabricator as a technical knowledge management system.",1521830534,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,For context: We have lots of client code with work arounds for getting the right sizes of images. So much duplication and bugs. We want to get rid of this code in the client and instead use this much more flexible proposed API. ,1521822249,PHID-USER-zuzwi67gyuz7wfxvuerx,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@kchapman we are interested in picking this up in Reading Infrastructure, but haven't been able to get to it. We would still like to do this if we can find some time… I should know more in Q4 about feasibility/timing.
+
+",1521822115,PHID-USER-zuzwi67gyuz7wfxvuerx,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"TechCom discussed this at our last meeting. The problem statement is still valid, but that doesn't mean it needs to be kept open as there is currently no resourcing for this. If there is still interest in this issue it could be used as material for a new RFC but the new RFC should contain one problem statement. Note: {T149847} has already been broken out into a single issue. 
+
+We are moving this to last call to be declined closing on 2018-03-29 at 1 pm PST(21:00 UTC, 22:00 CET
+
+
+
+ ",1521762316,PHID-USER-a3ndrbmqqq7sb7olfps4,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,Thanks @Anomie my information might be old. Moving to TechCom-RFC Inbox for discussion. ,1521641658,PHID-USER-a3ndrbmqqq7sb7olfps4,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#4064480, @kchapman wrote:
+> TechCom is declining because the use case is not current.
+
+Everything listed in the task's description under ""Use cases / problem statement"" seems current to me. See also T66214#1842437.",1521557737,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,The current thumbnail URL scheme could easily start including a revision number or sha1 of the original without changing the format.,1521555174,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"TechCom is declining because the use case is not current. This needs a new owner and use case. 
+
+There is actually one current use case still , which is the idea of having the thumb urls be versioned instead of “current” (ref. Performance-Team), but we intend to address that at a later point with a different proposal.",1521550747,PHID-USER-a3ndrbmqqq7sb7olfps4,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#3256693, @Tgr wrote:
+> We'll also need a way to display old versions of images. Clients can encounter old versions without expecting to due to FlaggedRevs hiding unreviewed image changes.
+
+{T149847} is designed to provide this ability, but it looks like that will still take a while. MediaWiki currently seems to prefix a timestamp to request old revisions, as in 20161203102219%21Kyoto_Station_November_2016_-02.jpg.
+
+Either version will work with this API, since the ""name"" portion is treated as an opaque identifier.",1497985249,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,We'll also need a way to display old versions of images. Clients can encounter old versions without expecting to due to FlaggedRevs hiding unreviewed image changes.,1494533430,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2981032, @Gilles wrote:
+> Accept headers and Vary: Accept are missing from the current task description.
+
+I added a section on this, but proposed to defer this question for now. As far as I am aware we don't need content negotiation right away, and the API proposal leaves all options open for a follow-up RFC.",1487875341,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2981032, @Gilles wrote:
+> Accept headers and Vary: Accept are missing from the current task description.
+
+I added a section on this, but proposed to defer this question for now. As far as I am aware we don't need content negotiation right away, and the API proposal leaves all optiones open for a follow-up RFC.",1487875318,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I think the discussion about restricting thumbnail sizes is orthogonal to this RFC. Nothing in this RFC limits our ability to later a) prefer specific sizes in a client side library, or even b) enforce the use of a limited set of sizes by returning a standard size instead of the non-standard requested size.",1487867873,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#3030371, @cscott wrote:
+> The one exception is that the current thumbnail code arbitrarily quantizes sizes in order to reduce cache overhead.  I'm not sure that is necessary to pull forward into the new service, but presumably the original quantization was added to reduce a particular cache-exhaustion DoS.  Limiting the size query to a limited set of ""thumbnail sizes"" (or ""media styles"") might be one way of avoiding a blowup in the number of different versions of a thumbnail.
+
+The current API prefers some sizes over others but does not limit clients (IIRC sizes are rounded to the closest multiple of 5px but that's not much of a limitation). That preference manifests in three ways:
+* certain sizes are pre-rendered at upload (`$wgUploadThumbnailRenderMap`)
+* for huge images, a thumbnail of some intermediary size is used as the source for scaling, not the original (see [[https://www.mediawiki.org/wiki/Manual:$wgThumbnailBuckets|`$wgThumbnailBuckets`]])
+* thumbnail rendering for non-standard sizes is throttled more aggressively.
+Mostly this is meant to improve performance for clients which limit themselves to predefined sizes (MediaWiki HTML pages and MediaViewer); to a smaller extent to help against accidental DOS by a combination of bot uploads of huge files + getting lots of thumbnailing requests in parallel when someone visits a category/gallery of said files. Cache exhaustion attacks were AFAIK not considered.
+The cache invalidation in Varnish is currently not intelligent about standard vs. nonstandard sizes (and in Swift there is no invalidation - every thumbnail is kept forever), but if that were feasible it would certainly be nice.",1487818481,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents? I've only been working with the consuming side, not the producing side of that hash.
+
+I remember that the temp path was an exception based on the filename, but didn't realize that the general hash was based on the filename as well.
+
+Not sure why we don't just compute it in Swift's rewrite.py instead of passing it along the whole pipepline. At any rate, you can ignore my previous remark.",1487795418,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents? I've only been working with the consuming side, not the producing side of that hash.
+
+I remember that the temp path was an exception based on the filename, but didn't realize that the general hash was based on the filename as well.
+
+Not sure why we don't just compute it in Swift's rewrite.py instead of passing it along the whole pipepline.",1487795379,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents? I've only been working with the consuming side, not the producing side of that hash.
+
+I remember that the temp path was an exception based on the filename, but didn't realize that the general hash was based on the filename as well.",1487795318,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents? I've only been working with the consuming side, not the producing side of that hash.",1487795256,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Ah nevermind, it's only the md5 of some form of the filename, not the file contents?",1487795231,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"You might not have access to the file contents when you generate a URL. What I'm saying is that you can't just drop that information from the URL, Swift needs it in some form, to hit the right shard. Because it, too, can't guess the contents of the original when you ask it to look for a thumbnail in a certain shard. And when the thumbnail is missing, it also needs to hit the right shard to fetch the original.
+
+While some wikis don't have sharding for their originals/thumbnails storage and don't need that information, any attempt at defining a new API should take that information into account. Right now none of the new URL examples provided in the task description contain storage sharding information.",1487795150,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2981357, @Gilles wrote:
+> Something that's missing in the current plan, however, is the swift sharding information that is currently part of the thumb URL in production.
+
+Do you mean [the md5 of the file name](https://github.com/wikimedia/mediawiki/blob/9ac29c74edda2f457814a1ed634a19f9a44fd0a5/includes/filerepo/FileRepo.php#L685)? Calculating this on the fly is not that expensive. OpenSSL does 7248416 md5s over 16 byte data per second on my machine, which works out to about 0.1ms per md5.",1487720573,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I'll pitch {T90914} as a better solution to the ""name for different thumbnail sizes"", as it generalizes that requirement and lets wikis come up with names for arbitrary groups of image properties.  But I agree that should be mostly abstracted from the thumbnail service.  The one exception is that the current thumbnail code arbitrarily quantizes sizes in order to reduce cache overhead.  I'm not sure that is necessary to pull forward into the new service, but presumably the original quantization was added to reduce a particular cache-exhaustion DoS.  Limiting the size query to a limited set of ""thumbnail sizes"" (or ""media styles"") might be one way of avoiding a blowup in the number of different versions of a thumbnail.
+
+But better would probably be to be semi-intelligent about cache strategy, so that 1,000 different versions requested of a certain image each requested once, (a) don't necessarily push other images out of the cache (cache slots are per-image, not shared), and (b) don't necessarily push out the highest-frequency cached thumbnails of that image (ie, not just LRU strategy).",1487185083,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr, the concerns you raise are primarily about the implementation, and not really about the API. I think it is important to separate the two, and avoid relatively minor implementation concerns dictate our API design. Public APIs will stay around & affect a lot of users, while implementations can be replaced transparently.
+
+We can definitely avoid duplication of the vast majority of thumbnails by rewriting ""simple"" thumbnails in Varnish (see migration strategy section). Similarly, thumbnail serving performance for small third party installs is something we can optimize by mapping requests to file names, for example as part of the container-based distribution project.
+
+Edit: I forgot to mention that client side size selection won't work with purely static file serving in any case. At a minimum, a 404 handler would need to be configured, which is something we can do for either API, but is more complex than using thumb.php.",1487185610,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr, the concerns you raise are primarily about the implementation, and not really about the API. I think it is important to separate the two, and avoid relatively minor implementation concerns dictate our API design. Public APIs will stay around & affect a lot of users, while implementations can be replaced transparently.
+
+We can definitely avoid duplication of the vast majority of thumbnails by rewriting ""simple"" thumbnails in Varnish (see migration strategy section). Similarly, thumbnail serving performance for small third party installs is something we can optimize by mapping requests to file names, for example as part of the container-based distribution project.",1486589895,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr, the concerns you raise are primarily about the implementation, and not really about the API. I think it is important to separate the two, and avoid relatively minor implementation concerns dictate our API design. Public APIs will stay around & affect a lot of users, while implementations can be replaced transparently.
+
+We can definitely avoid duplication of the vast majority of thumbnails by rewriting ""simple"" thumbnails in Varnish (see migration strategy section). Similarly, thumbnail serving performance for small third party users is something we can optimize by mapping requests to file names, for example as part of the container-based distribution project.",1486589846,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I think the third-party MediaWiki concerns are somewhat understated and are not actually third party as we use the same arrangement via Swift (sorry, should have spotted that sooner).
+
+This is the status quo:
+* default MediaWiki setup: thumbnails are only rendered on parse, client requests for arbitrary thumbnail sizes (arbitrary being anything that's not already present in the article) are not possible. Thumbnails are referred to by URLs which mirror the filename (generated by `MediaHandler::makeParamString`) and directory structure, so setting up the web server is as easy as configuring the image directory on disk to be the webroot for `<wiki root URL>/images`. This would probably have to be deprecated if we move along with the RfC (there is not point to an API which might or might not work).
+* everything through `thumb.php`: apart from a little syntactic sugar, this is what the RfC is going for. This is a possible configuration currently although I don't think it is used much. Every image request gets streamed through PHP (or served by some external cache like Varnish).
+* 404 handling: like the default, but requests for non-existent images are sent to `thumb.php` via the web server's 404 handler, and get converted from filenames back into proper key-value querystrings (via `MediaHandler::parseParamString`), then saved to disk so the next request to the same URL gets served by the web server directly. This is probably the common setup for non-small wikis.
+* Wikimedia setup: basically same as 404 handling, with two extra layers on top: Varnish and Swift. Varnish caches URLs and is mostly agnostic of how thumbs are served. Swift (a distributed file storage) is used the same way as the disk in the previous example: the thumb URL uses a path/filename which can be represented in a filesystem, and in case of a Varnish miss, the ""web server"" (in this case a small python script) looks up the file in Swift using that path; if that fails, it forwards the request to `thumb.pgp` which transforms it into a nice query URL, renders the thumbnail, saves it to Swift then streams it.
+
+So the proposal as it is now would duplicate thumbnail storage in Swift and degrade performance in third-party wikis that don't use a reverse proxy. It makes more sense to keep the current parameter-array -> filename-on-disk mapping and document it as standard (it's ugly and ad hoc but there are seven parameters altogether in all known extensions and almost all are mutually exclusive so meh), and reimplement it in Thumbor and the Swift router script.",1486526310,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2988556, @GWicke wrote:
+>>>! In T66214#2988550, @Tgr wrote:
+>>>>! In T66214#2982093, @Fjalapeno wrote:
+>>> One piece of feedback we have been discussing is having a higher level abstraction in addition to specifying actual width.
+>> 
+>> A similar proposal on the wikitext side is {T90914}. IMO it's an interesting issue but too complicated and vaguely understood to include in the current RfC which has largely orthogonal concerns anyway.
+> 
+
+I don't think its a problem addressing outside of the current RFC.
+
+> Agreed. Such a higher-level abstraction could always be implemented in a client side library, which would select the right pixel size based on the desired high-level thumbnail type (and possibly other criteria, like device properties).
+
+
+I would like to consider not putting this type of logic in a client side library. One of the advantages of sharing an API is to prevent clients form needing to implement the same logic in multiple languages/platforms. 
+",1485980579,PHID-USER-zuzwi67gyuz7wfxvuerx,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,^ Captured in {T156910}.,1485950677,PHID-USER-w3pd7vqenmta6vpmhwcn,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2988556, @GWicke wrote:
+> Agreed. Such a higher-level abstraction could always be implemented in a client side library, which would select the right pixel size based on the desired high-level thumbnail type (and possibly other criteria, like device properties).
+
+I was one of the engineers that discussed this higher level of abstraction with @Fjalapeno. I do believe that the Reading Web team should pursue this abstraction in the projects they maintain, which are predominantly clients, and continue to discuss pushing the abstraction further down the stack when it's better understood.",1485946625,PHID-USER-w3pd7vqenmta6vpmhwcn,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2988550, @Tgr wrote:
+>>>! In T66214#2982093, @Fjalapeno wrote:
+>> One piece of feedback we have been discussing is having a higher level abstraction in addition to specifying actual width.
+> 
+> A similar proposal on the wikitext side is {T90914}. IMO it's an interesting issue but too complicated and vaguely understood to include in the current RfC which has largely orthogonal concerns anyway.
+
+Agreed. Such a higher-level abstraction could always be implemented in a client side library, which would select the right pixel size based on the desired high-level thumbnail type (and possibly other criteria, like device properties).",1485908455,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2982093, @Fjalapeno wrote:
+> One piece of feedback we have been discussing is having a higher level abstraction in addition to specifying actual width.
+
+A similar proposal on the wikitext side is {T90914}. IMO it's an interesting issue but too complicated and vaguely understood to include in the current RfC which has largely orthogonal concerns anyway.",1485908258,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Thank you all for pushing this forward! This is really great for the reading platforms where we have had lots of ambiguity with thumbnails.
+
+I'm gathering input from the platform teams (Web, Android, iOS) on the current proposal, I want to make sure we have all existing use cases covered.
+
+One piece of feedback we have been discussing is having a higher level abstraction in addition to specifying actual width. Some potential examples:
+
+- thumbnail-small
+- thumbnail-large
+- preview
+- preview-hi-resolution 
+- inline
+- inline-mobile
+- original
+
+This could have a couple advantages:
+# This allows us to evaluate sizes for each use case and specify an approbate size and canonize it in the API
+# Helps control cache fragmentation by discouraging specific size requests
+# When technology/needs change, we can update the sizes without requiring clients to update code.
+
+
+Any thoughts here?
+
+
+
+
+ ",1485790492,PHID-USER-zuzwi67gyuz7wfxvuerx,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I don't think that the existing requirements are to be touched at first. I.e. thumbnails would still be width-based only.
+
+Some adaptation of rewrite.py will probably be required, but I think for the most part it would pass along the new request format to the backend (Mediawiki or Thumbor).
+
+Something that's missing in the current plan, however, is the swift sharding information that is currently part of the thumb URL in production.",1485770318,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"WRT deployment strategy note that ATM all thumb accesses after varnish go through our [[https://github.com/wikimedia/operations-puppet/blob/production/modules/swift/files/SwiftMedia/wmf/rewrite.py | custom swift rewrite middleware]], how would that (if?) change? Would all thumbs with arbitrary height be stored alongside existing thumbs?",1485767459,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Accept headers and Vary: Accept are missing from the current task description.
+
+Standardizing entry point to thumb.php (and I guess img_auth.php) sounds great to me.
+
+Looking at existing parameters between the various handlers that we'll likely reuses as-is, I think it could be nice to use this as an opportunity to merge ""seek"" and ""page"" which are essentially the same thing in different contexts.",1485764071,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> The simplest solution would be to just move all thumb accesses to thumb.php (or an api module)
+
+I note thumb.php could probably use `MW_NO_SESSION` (see T127233), while an action API module cannot.",1485534767,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr and I discussed some more details in the office today.
+
+- General syntax: We both see general consensus around using query strings, and the (subset of) existing thumb.php parameters generally look like a sane starting point already.
+- Communicating original dimensions: We both have a preference for using the URL, with a slight preference for the hash variant (`/someimage.jpg?w=100#oh=1024&ow=768`).
+- Versioning: We expect a need to migrate the API format in the future (to content-based hashes, for example). To ensure that we can do this cleanly, we propose to prefix the thumb path with `/v1/`.
+- Third party support: We explored options for migrating third party users to the new thumb API in the future. The simplest solution would be to just move all thumb accesses to thumb.php (or an api module), but there would be a slight performance cost, which can however be addressed. Overall, we expect to be able to offer a smooth migration path.
+
+Next steps:
+
+1) Wrap up the bikeshedding on the general syntax choices & versioning. <- This is where you can contribute here & now.
+2) Audit & document the official thumb.php API. This is largely covered in {T153497}.
+3) Meet with the main stakeholders to detail an implementation plan.
+4) Finalize the RFC in a last call period.
+5) Implement. ",1485471162,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2970912, @GWicke wrote:
+> Are those key-value parameters already supported by all media handlers, or is support limited to built-in ones?
+
+`f` is magic and does not get passed to the media handlers (they receive the file as a `File` object). There are a few similar parameters, see T153497 (the ""unset..."" parts) for details.
+Apart from that, media handlers are free to do whatever. `width`/`page` is convention and supported by everything for which it makes sense, the other parameters only make sense for a single handler. (See the other task for parameters; I only reviewed the handlers which are hosted in gerrit.)",1485393372,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2970912, @GWicke wrote:
+> Are those key-value parameters already supported by all media handlers, or is support limited to built-in ones?
+
+`f` is magic and does not get passed to the media handlers (they receive the file as a PHP argument). There are a few similar parameters, see T153497 (the ""unset..."" parts) for details.
+Apart from that, media handlers are free to do whatever. `width`/`page` is convention and supported by everything for which it makes sense, the other parameters only make sense for a single handler. (See the other task for parameters; I only reviewed the handlers which are hosted in gerrit.)",1485393343,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr: That is great news. This means that we already have a means of feeding generic key-value parameters to the thumb machinery. Are those key-value parameters already supported by all media handlers, or is support limited to built-in ones?
+
+Looking at [thumb.php](https://github.com/wikimedia/mediawiki/blob/master/thumb.php#L98), it seems that some of this interface is currently considered deprecated (including the `w` and `p` shorthands). We should make a pass over this API to see if everything makes sense as-is.
+
+> That would result in URLs like https://commons.wikimedia.org/w/thumb.php?f=Camera2_mgx.svg&w=100&lang=fr, which is a bit uglier than https://commons.wikimedia.org/thumb/Camera2_mgx.svg?w=100&lang=fr but no difference in functionality
+
+The 404 handler already [tries to pull the thumb name from the path info](https://github.com/wikimedia/mediawiki/blob/master/thumb.php#L60), so it should not be that hard to support requests of the form /thumb.php/Sometitle.jpg?w=100&p=10. In production, we would probably use a prefix like /thumb/. Either way, clients would see a slightly cleaner separation between the thumb name & its parameters that is consistent between large & small installs.",1485389194,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"After thinking more about this and looking at the code I am getting more and more confused about what exactly we are trying to do. Media handlers already use two representations: a parameter array (which can be passed to `File::transform`, or by an external client to `thumb.php` - so we do have an API with sane parameters, it's just not used because there isn't any caching in front of it) and a filename prefix; `MediaHandler::makeParamString` and `MediaHandler::parseParamString` can be used to convert between the two. All that's needed for a Wikimedia thumbnail API is to set up Varnish to cache the `thumb.php` responses, and disable the `transformVia404` config flag if we also want to use query-string-style URLs in the generated HTML. That would result in URLs like [[https://commons.wikimedia.org/w/thumb.php?f=Camera2_mgx.svg&w=100&lang=fr|https://commons.wikimedia.org/w/thumb.php?f=Camera2_mgx.svg&w=100&lang=fr]], which is a bit uglier than `https://commons.wikimedia.org/thumb/Camera2_mgx.svg?w=100&lang=fr` but no difference in functionality (and it's not hard to add a wrapper if needed). Since we want to use a separate domain for uploads, we would probably change `$wgThumbnailScriptPath` to point to `https://upload.wikimedia.org/<project>/<language>/thumb.php` and use a multiwiki dispatcher script, like we used to do with bits/`load.php`. Or it could point to a RESTBase or Thumbor installation; in any case, I don't see any changes that would be needed to MediaWiki internals.",1482037109,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2850204, @Ciencia_Al_Poder wrote:
+>>>! In T66214#2827486, @GWicke wrote:
+>> Since the need for explicit control should be rare, I think using the Accept header offers the better trade-offs overall.
+> 
+> If I understand correctly, you propose to potentially send different image formats under the same request URL. That would require cache varying depending on the Accept: header (and I'm not sure about the implications of this), otherwise a cached webp response might be served to clients not supporting that format.
+
+Yes, the proposal includes setting a `Vary: accept`, and normalizing the `Accept` header value on thumb requests in Varnish. At least in the foreseeable future, the number of format variations will be very low, which keeps the normalization logic simple.",1481073842,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Not sure if it is helpful to examine, but here is a commercial image service API:
+
+https://docs.imgix.com/setup/serving-images
+https://docs.imgix.com/apis/url
+
+They do in fact pass the extension back but most other options are in query parameters (including format)
+
+
+",1481037024,PHID-USER-zuzwi67gyuz7wfxvuerx,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2827486, @GWicke wrote:
+> Since the need for explicit control should be rare, I think using the Accept header offers the better trade-offs overall.
+
+If I understand correctly, you propose to potentially send different image formats under the same request URL. That would require cache varying depending on the Accept: header (and I'm not sure about the implications of this), otherwise a cached webp response might be served to clients not supporting that format.",1481026269,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, the client can communicate the exact format(s) it prefers using either the URL, or via the Accept header. 
+
+For the vast majority of browser use cases, the Accept header has the advantage of doing the right thing implicitly, without the user needing to do anything. Advanced clients can still express their format preferences in a custom Accept header, which makes this scheme future-proof. 
+
+The downside of using Accept headers is that advanced clients would need to manually request images to control the Accept header, which will have performance disadvantages vs. native image loading.
+
+Since the need for explicit control should be rare, I think using the Accept header offers the better trade-offs overall.",1480351406,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I think it might be just a little misunderstanding. If you're talking about describing to the client what kind of media the original is, yes, a general category is probably fine. But the client needs to retain control of which mime type the thumbnail will be in. In order to avoid formats it might not support, etc. Since you bring up the Accept header, I assume that you're fine with that idea. What I think is a bad idea is the client only being able to request ""bitmap"" and getting a JPG, a PNG or a WEBP depending on criteria that only we know about without any way to control that.",1480011217,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the conversion that is interesting to clients. Do you have concrete use cases in mind that would *require* more exotic format conversions, and aren't covered by the combination of Accept header, format selector, size & quality?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later (ex: `om=image/svg+xml`), if we find an actual use case that requires it. For current use cases, I think that dealing with the low-level file types mostly adds unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server. Even if we add finer-grained information & selection control at some point, most clients will probably continue to prefer using the simplest possible solution that satisfies their requirements.",1479926154,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the conversion that is interesting to clients. Do you have concrete use cases in mind that would *require* more exotic format conversions, and aren't covered by the combination of Accept header, format selector, size & quality?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later (ex: `om=image/svg+xml`), if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479921842,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the conversion that is interesting to clients. Do you have concrete use cases in mind that would *require* more exotic format conversions, and aren't covered by the combination of Accept header, format selector, size & quality?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479919300,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the conversion that is interesting to clients. Do you have concrete use cases in mind that would *require* more exotic thumbnail conversions?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479919235,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the only one that's interesting to clients. Do you have concrete use cases in mind that would *require* more exotic thumbnail conversions?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479919207,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector (or video) to bitmap will always be possible, and is the only one that's interesting to clients. Do you have concrete use cases in mind that would *require* more exotic conversions?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479919090,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  /someimage#o=vec&oh=1024&ow=768 This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I really like this idea. It retains the advantage of encoding the information in a standard way in the URL, but avoids sending back unnecessary bits to the server. It follows the precedent of using url-encoded anchors in [media fragments](https://www.w3.org/TR/media-frags/). They are still straightforward to parse.
+
+> Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc.
+
+I believe the conversion from vector to bitmap will always be possible, and is the only one that's interesting to clients. Do you have concrete use cases in mind that would *require* more exotic conversions?
+
+> Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.
+
+We could add an exact mime type in addition to the vector / bitmap / video distinction later, if we find an actual use case that requires it. For current use cases, dealing with the low-level file types mostly seems to add unnecessary complexity to clients, and reduces flexibility for phasing in new formats on the server.",1479918464,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2816123, @GWicke wrote:
+> - Supply original format and size in the URL or metadata, and let the client choose between SVG originals & bitmap thumbs. Example using URL syntax: `/someimage?o=vec`
+>   - `o=vec` or `o=vid` (metadata): Original is a vector image or video. Can consider omitting this for bitmaps (default).
+>   - `oh=1024&ow=768` (metadata): Original width & height. Absent for SVGs when API or HTML use case recommends using SVG original.
+
+I don't understand the obsession with passing context through useless query parameters. Clients already obtain the minimum information about the file in some way (image name/hash) they can fetch more context about the file from that same source before making a thumbnail request. It's not like we're running out of bits when we inform a client of a thumbnail and its corresponding file. There is absolutely no constraint forcing it to all be in a single field. And if there were, you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  `/someimage#o=vec&oh=1024&ow=768` This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side with client-passed context that might actually not match the real values stored.
+
+I still see the video/bitmap/vector abstraction in this latest example as misguided. Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc. Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.",1479898638,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2816123, @GWicke wrote:
+> - Supply original format and size in the URL or metadata, and let the client choose between SVG originals & bitmap thumbs. Example using URL syntax: `/someimage?o=vec`
+>   - `o=vec` or `o=vid` (metadata): Original is a vector image or video. Can consider omitting this for bitmaps (default).
+>   - `oh=1024&ow=768` (metadata): Original width & height. Absent for SVGs when API or HTML use case recommends using SVG original.
+
+I don't understand the obsession with passing context through useless query parameters. Clients already obtain the minimum information about the file in some way (image name/hash) they can fetch more context about the file from that same source before making a thumbnail request. It's not like we're running out of bits when we inform a client of a thumbnail and its corresponding file. There is absolutely no constraint forcing it to all be in a single field. And if there were, you could pass it through an anchor that wouldn't make it back server side. I.e. restbase or the API would give this to the client:  `/someimage#o=vec&oh=1024&ow=768` This way we would avoid having to strip that context in Varnish and generally polluting the logs and information server-side.
+
+I still see the video/bitmap/vector abstraction in this latest example as misguided. Formats of the same ""type"" have fundamental differences already and you can't predict what new formats we'll support in the future. Knowing something is ""vector"" is of little use to the client if depending on the actual source file type one might not be able to convert it into some thumbnail types, etc. Our current set of supported file types is too limited to know with certainty that this level of abstraction makes sense in a future-proof manner, and things will get very sketchy if we want to break an existing group like ""vector"" into subgroups in the future. If we start off with mime types, that never changes.",1479898582,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We do have some information about format support from Accept & User-Agent headers in regular image requests. Chrome for example sends `accept: image/webp,image/*,*/*;q=0.8`, indicating that it prefers WEBP where available, followed by other image formats. Firefox sends `accept: */*`, which at least indicates that it does not yet support webp. 
+
+However, there is no information about SVG support levels in common browser's accept headers. While [basic support is rather good across the board at 97+%](http://caniuse.com/#search=svg), support for advanced features is less common and mature. We can't communicate very detailed information about features used in a given SVG, so I agree with you that the conservative option will be to default to bitmap thumbs when a size is requested, and let clients opt in to using the SVG original when they are sure that client support is decent. Some indication of SVG original size & render effort could be helpful for this decision, but we'd need to add more metadata to make this available client-side.
+
+Let me sketch how this could work with a combination of negotiation & explicit parameters:
+
+- Supply original format and size in the URL or metadata, and let the client choose between SVG originals & bitmap thumbs. Example using URL syntax: `/someimage?o=vec`
+  - `o=vec` or `o=vid` (metadata): Original is a vector image or video. Can consider omitting this for bitmaps (default).
+  - `oh=1024&ow=768` (metadata): Original width & height. Absent for SVGs when API or HTML use case recommends using SVG original.
+  - `w=640` (server / client controlled): Request a bitmap thumb with this width. Thumb URLs served by APIs or HTML content can recommend a bitmap or original SVG format by adding / omitting the thumb width parameter.
+- Use basic content negotiation based on accept and user-agent headers at the Varnish layer to select the most appropriate low-level bitmap image format. In particular:
+  - Serve WEBP only when the client explicitly indicates support in its `accept` header, and the UA does not match a blacklist of browsers with incomplete WEBP support. PNG and JPG are used as the safe baseline.
+  - Can also take into account quality parameter.",1479849971,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The client doesn't necessarily have to advertise what it wants, but then if it doesn't tell us anything, we would have to be conservative and not serve formats like WEBP or SVG that aren't widely supported. When the client doesn't ask for a specific format, it would be wise to stick to JPG and PNG as the only options, as we do now.
+
+I think that accept headers make the most sense, because the client can use them in two ways. Either provide us with a list of what it supports, and let our backend pick within that selection what we think is best. Or request a specific format.
+
+In either case some knowledge of what we're capable of for a given file type is needed if you're constructing a thumbnail URL from scratch and want a specific output format. But that's the same in your proposal if you ask for a ""vector"" when the original is a JPG. That request doesn't make any sense. And if we serve a JPG in that case, the client that was expecting a ""vector"" or an SVG, if the format is asked explicitly, might not be able to process it if the data is sent to a component only designed to render SVGs.
+
+I can't see how you intend to make WEBP and SVGsupport work without the client explicitly advertising its support for these formats. Asking for ""bitmap"" doesn't mean that you support WEBP, asking for ""vector"" doesn't mean that you support SVG. At the end of the day the client support list is fine-grained. Which is why I believe that the accept header is the best option, because it can give us a comprehensive list of the client's capabilities, based on which we can decide what makes the most sense for a given file.
+
+Now on the subject of the client needing some knowledge of our original type -> thumbnail type mapping. Like I mentioned above it's unavoidable regardless of your level of abstraction about the kind of output is requested. The question is how does the client know that it can request an SVG for a given file? Or rather, that it can request just SVG and it will get what it wants. I think it's the same issue as the original's dimension, it has to be provided as metadata alongside the rest of the thumbnail information in the APIs that clients consume to construct thumbnail URLs. Think of the Media Viewer case again. Right now the original sized as passed as attributes, because that's metadata that the thumbnail URL (or the original's URL) doesn't tell you. If in the future thumbnail URLs are addressed by hash and not by filename, Media Viewer becomes ""blind"" to what kind of thumbnails it can request. Therefore it would make sense to advertise either the original's mime type as another attribute, or the list of possible output mime types, if we don't want the client to need to keep a mapping up to date between original mime types and possible thumbnail mime types we support.
+
+Even when you consider the use case of constructing a thumbnail URL ""from scratch"". Right now you need to know the filename, presumably you got that from an API or from parsing some page. Granted that you know what thumbnail formats we support for each original type, that's enough to request a thumbnail, which might fail if you request something too big. When thumbnails are addressed by hash, the hash will become the new minimum. You can still request a thumbnail with just that, but we might give you a thumbnail format you don't expect. And you still have the original size issue. If you want to generate thumbnail URLs with certainty that it will work, you're going to want to get the original size alongside the hash. And if you know that you can't process some formats we might throw at you based on our list of possible output formats, you might as well get the list of possible output formats for that file while you're already getting the hash and original dimensions.
+
+Of course the ideal case is a client that supports everything we do, but I think it would be very dangerous to make the default, when the client doesn't tell us what it supports/wants, to send what we think is the best format for a given file among all possible file formats. Our content is heavily skewed towards JPG and PNG: https://commons.wikimedia.org/wiki/Special:MediaStatistics More than 90% of our content is either of those. Meaning that if we serve SVG thumbnails for SVG files when the client doesn't tell us anything about what it wants, we're quite likely to make some clients fail 3% of the time, because people who built them didn't encounter SVGs when testing (because it's easy not to stumble upon them).
+
+Which is why I think the default behavior when nothing special is requested is to stick to JPG & PNG. That creates a really safe environment where the client can ignore the metadata I've just mentioned (which mime types can this original be rendered to) and always get a JPG or PNG back, which should be universally supported. Should the client support more, it can still ignore metadata about the file at hand and advertise through the Accept header that it can treat SVGs. Then we start serving SVGs to it when appropriate. And the client can look at the mime type of the response and act accordingly. To me that's the most likely use case and it makes the extra metadata I mention in the previous paragraph less necessary. That's what browsers already do and it doesn't require prior knowledge about the URL you're requesting.
+
+To sum up, I see two scenarios from our perspective:
+
+- client doesn't tell us what format it supports of wants. We stick to serving only JPG and PNG. We can still make ""judgment calls"" about which we serve. For example if the client wants a low-quality thumbnail, PNG originals could be served as JPG.
+- client gives us a list of formats it supports (can be just one). We do the judgment call based on that list, picking what we think is best for the file at hand, given the other thumbnail parameters (eg. quality), if any. Should we not support any of the request formats for that file, we serve an error (it's the same situation as requesting a thumbnail bigger than the original - the client asked for a conversion we won't do). The solution for a client to avoid that error is to either always include JPG & PNG in the supported list (we can document that) or fetch metadata about the file, ideally at the same time it currently gets the hash/filename, to know which mime types it can be thumbnailed into.",1479807370,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, let me try to summarize how you see this working:
+
+- We supply the exact original image format (svg, pdf, png, gif, tiff, jpg, webp-lossy, webp-lossless, videos) in URL or metadata.
+- The client maintains some mapping of original to target format & quality, and rewrites URLs to match (or manually loads images, so that it can set Accept headers). For example, it would need to know that tiff & png originals are likely line art, and might map those to webp-lossless, but only if the client supports webp-lossless well.
+
+Is this understanding correct?
+
+Do you have a concrete use case in mind that requires this level of client-side control over which format to use? Would control over SVG vs. bitmap, quality & content negotiation for support issues be sufficient to cover the same use case?",1479760922,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, let me try to summarize how you see this working:
+
+- We supply the exact original image format (svg, png, gif, tiff, jpg, webp-lossy, webp-lossless, videos) in URL or metadata.
+- The client maintains some mapping of original to target format & quality, and rewrites URLs to match (or manually loads images, so that it can set Accept headers). For example, it would need to know that tiff & png originals are likely line art, and might map those to webp-lossless, but only if the client supports webp-lossless well.
+
+Is this understanding correct?
+
+Do you have a concrete use case in mind that requires this level of client-side control over which format to use? Would control over SVG vs. bitmap, quality & content negotiation for support issues be sufficient to cover the same use case?",1479760516,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, let me try to summarize how you see this working:
+
+- We supply the exact original image format (svg, png, gif, tiff, jpg, webp-lossy, webp-lossless, videos) in URL or metadata.
+- The client maintains some mapping of original to target format & quality, and rewrites URLs to match (or manually loads images, so that it can set Accept headers). For example, it would need to know that tiff & png originals are likely line art, and might map those to webp-lossless, but only if the client supports webp-lossless well.
+
+Do you have a concrete use case in mind that requires this level of client-side control over which format to use? Would control over SVG vs. bitmap, quality & content negotiation for support issues be sufficient to cover the same use case?",1479758637,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"If you're looking for hardware acceleration/battery saving, JPG is probably your best bet. If you want the most lightweight file, then Webp. Should the device you're working with be slow or buggy when dealing with a certain format, you might want to avoid it by requesting another one.
+
+The majority of our content is on Commons where editors already use file formats according to the image contents. Eg. PNG is preferred for diagrams and JPG for photos. If you upload a diagram as a JPG you'll generally be advised to reupload it as PNG. The policy is well followed for photos and has allowed the community to put in place conditional sharpening parameters for JPGs that works well on photos but would make diagrams look terrible.",1479753306,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I don't see the search for the right granularity as a contradiction, but more as a search for the best set of trade-offs along a continuum. On one end, we have no client control & possibly server-side negotiation, while on the other end we have fine-grained client control without any content negotiation. The best set of trade-offs might not lie at the extremes of this spectrum. Lets continue to evaluate options against our use cases, and add use cases to the list in case any are missing.
+
+> If you're going to override the automatic behavior, you should have precise control.
+
+Can you think of use cases that would benefit from directly selecting jpg vs. png vs. webp lossy / lossless, rather than just vector vs. bitmap & quality level? Would those use cases need more information about the image contents (ex: line art vs. photo) to usefully pick the right format?",1479751660,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I don't see the search for the right granularity as a contradiction, but more as a search for the best set of trade-offs along a continuum. On one end, we have no client control & possibly server-side negotiation, while on the other end we have fine-grained client control without any content negotiation. The best set of trade-offs might not lie at the extremes of this spectrum. Lets continue to evaluate options against our use cases, and add use cases to the list in case any are missing.
+
+> If you're going to override the automatic behavior, you should have precise control.
+
+Can you think of use cases that would benefit from directly selecting jpg vs. png vs. webp lossy / lossless? Would those use cases need more information about the image contents (ex: line art vs. photo) to usefully pick the right format?",1479743589,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I don't see the search for the right granularity as a contradiction, but more as a search for the best set of trade-offs along a continuum. On one end, we have no client control & possibly server-side negotiation, while on the other end we have fine-grained client control without any content negotiation. The best set of trade-offs might not lie at the extremes of this spectrum. Lets continue to evaluate options against our use cases, and add use cases to the list in case any are missing.
+
+> If you're going to override the automatic behavior, you should have precise control.
+
+Can you think of use cases that would benefit from such fine-grained control? Would those use cases need more information about the image contents (ex: line art vs. photo) to usefully pick the right format?",1479743479,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"There is contradiction here. You want to serve what's best for the client ""automatically"", but you want the client to retain some control just in case, but not too much as they can't pick the specific file format they're interested in. I think that while making some options more semantic makes sense, in the case of file formats it does not. Webp, JPG, PNG have very different properties and a client should be able to specifically pick one of those if it wants to. If you're going to override the automatic behavior, you should have precise control. Especially since something as simple semantically as ""bitmap"" can already contain webp, which definitely won't work on all devices. If the only thing the client can tell us about what it accepts is ""bitmaps"" we won't be able to tell if we can serve it a webp image.
+
+As for the Accept header, if the client is using the native image fetching functions, said functions should advertise Accept headers that represent file types the device is capable of displaying. Having to use lower-level functions would only be necessary if the client wants to do something custom, like wanting a specific file format and no other. I think that's acceptable. You're point is full of assumptions about what people would implement and how they would go about it, I think it's a weak argument against dismissing a mechanism that's been a standard for decades for a client to declare what file types it can consume.",1479725429,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2805495, @Gilles wrote:
+>>>! In T66214#2803304, @GWicke wrote:
+>> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+> 
+> How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.
+
+I think Accept headers as great for selecting supported formats (such as jpg vs webm), but they aren't very usable for client-driven decisions around SVG vs. bitmaps, or bitmap thumb vs. video. To control the accept header, clients would need to use `fetch` or `xhr` to fetch images, instead of highly optimized native image loading. It might work better for video, but at the same time video needs more control over quality (adaptive streaming) than accept headers alone are intended to provide.
+
+Generally, outside of video it seems that the main use case for client code driven format selection / behavior change are around vector vs. bitmap (without caring about the exact bitmap format), and quality. Something like `?f=bmp`, `?f=vec`, `?f=vid` should be sufficient to provide this information, and allow clients to choose between retrieving a vector original vs. requesting a bitmap thumbnail.",1479494974,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2805495, @Gilles wrote:
+>>>! In T66214#2803304, @GWicke wrote:
+>> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+> 
+> How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.
+
+I think Accept headers as great for selecting supported formats (such as jpg vs webm), but they aren't very usable for client-driven decisions around SVG vs. bitmaps, or bitmap thumb vs. video. To control the accept header, clients would need to use `fetch` or `xhr` to fetch images, instead of highly optimized native image loading. It might work better for video, but at the same time video needs more control over quality (adaptive streaming) than accept headers alone can provide.
+
+Generally, outside of video it seems that the main use case for client code driven format selection / behavior change are around vector vs. bitmap (without caring about the exact bitmap format), and quality. Something like `?f=bmp`, `?f=vec`, `?f=vid` should be sufficient to provide this information, and allow clients to choose between retrieving a vector original vs. requesting a bitmap thumbnail.",1479494921,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2805495, @Gilles wrote:
+>>>! In T66214#2803304, @GWicke wrote:
+>> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+> 
+> How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.
+
+I think Accept headers as great for selecting supported formats (such as jpg vs webm), but they aren't very usable for client-driven decisions around SVG vs. bitmaps, or bitmap thumb vs. video. To control the accept header, clients would need to use `fetch` or `xhr` to fetch images, instead of highly optimized native image loading. For video, 
+
+Generally, to me it seems that the main use cases for client code driven format selection / behavior change are around vector vs. bitmap (without caring about the exact bitmap format), and quality. Something like `?f=bmp`, `?f=vec`, `?f=vid` should be sufficient to provide this information, and allow clients to choose between retrieving a vector original vs. requesting a bitmap thumbnail.",1479494606,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2805495, @Gilles wrote:
+>>>! In T66214#2803304, @GWicke wrote:
+>> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+> 
+> How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.
+
+I think Accept headers as great for selecting supported formats (such as jpg vs webm), but they aren't very usable for client-driven decisions around SVG vs. bitmaps, or bitmap thumb vs. video. To control the accept header, clients would need to use `fetch` or `xhr` to fetch images, instead of highly optimized native image loading.",1479492179,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2803304, @GWicke wrote:
+> However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+How about Accept HTTP headers? That's a standard way for a client to advertise which MIME types it wants without knowing the content in advance.",1479465868,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2804824, @Tgr wrote:
+> Re: type selection, we should use real file extensions (`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12.png` instead of `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`) otherwise we are probably going to trigger some mime type guessing bug in some obscure browser when used in HTML pages (thumbnails must work for [[https://www.mediawiki.org/wiki/Compatibility#Browsers|Grade C]] browsers).
+
+Unless we have a specific list of UAs affected by a concrete problem, this is paranoia. I recall problems with URLs that would cause a mismatch (i.e. /foo-thumb.pdf but actually returning a jpeg), but not extension-less URLs.",1479465708,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Would the API cover `img_auth.php`? How about stashed uploads and thumbnails thereof (a horrible pile of hacks currently)? Or more generally the whole ""zones"" feature of FileRepo?",1479437397,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Re: original size in URL, beside feeling a bit hacky, there are some (minor) disadvantages: generating the URL to the original file based on the filename becomes more complicated (less of an issue if we use context-based addressing anyway), and B/C becomes more limited (for a MediaHandler which has not been updated, we probably want to use the old-style URL so that we prefer breaking clients doing URL rewriting over breaking displaying the file at all; and clients expecting the size to be in the URL would be more likely to break). Also, keep in mind that size information might get more complex than two numbers (e.g. SVGs have a nominal original size but can be scaled beyond that without loss of quality and we probably want to tell the client that).
+
+Re: type selection, we should use real file extensions (`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12.png` instead of `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`) otherwise we are probably going to trigger some mime type guessing bug in some obscure browser when used in HTML pages (thumbnails must work for [[https://www.mediawiki.org/wiki/Compatibility#Browsers|Grade C]] browsers).
+
+Re: format selection use cases, there is also language selection. But I don't think the API has to be aware of formats - they are just parameters to pass through.",1479437295,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the same conversation, @Pchelolo brought up a potential issue around image format conversion / selection. We do have a need to support format conversions, for example a conversion from SVG to PNG. However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+This requirement is similar to informing the client about original dimensions, except that the desired file type also //needs// to be sent to the API to avoid default parameter fragmentation. Since we also need to support uses without any rewriting (ex: HTML), including the file type in the URL (for example, as a query parameter) seems to make the most sense.
+
+Example original URL, using query string syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`
+
+Another (possibly prettier) option would be to use a custom file extension syntax, but the downside of this would be slightly more effort for parsing.
+
+Edit: Thinking about this some more, I think we should detail a bit more which kind of control over the format we need. Aspects that come to mind:
+
+- Quality selection (esp. for bitmaps). Coarse granularity (high, normal, low) is probably all we want to expose.
+- Bitmap vs. vector graphics vs. video. 
+  - Clients might want to load the original image in case it is an SVG. For this, they need to know whether an original is a SVG vs bitmap / video before making a request. Specifying the size does not make sense for SVGs in general.
+  - Videos: Some clients could offer a video player, rather than displaying a bitmap thumb.
+- Selecting a specific bitmap format. This seems questionable, but it's conceivable that there could be client support limitations that would make this useful. Content negotiation might be a better alternative for phasing in new formats like webm.
+
+Are there any other format selection related use cases that aren't covered by these options yet?",1479416227,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the same conversation, @Pchelolo brought up a potential issue around image format conversion / selection. We do have a need to support format conversions, for example a conversion from SVG to PNG. However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+This requirement is similar to informing the client about original dimensions, except that the desired file type also //needs// to be sent to the API to avoid default parameter fragmentation. Since we also need to support uses without any rewriting (ex: HTML), including the file type in the URL (for example, as a query parameter) seems to make the most sense.
+
+Example original URL, using query string syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`
+
+Another (possibly prettier) option would be to use a custom file extension syntax, but the downside of this would be slightly more effort for parsing.
+
+Edit: Thinking about this some more, I think we should detail a bit more which kind of control over the format we need. Aspects that come to mind:
+
+- Quality selection (esp. for bitmaps). Coarse granularity (high, normal, low) is probably all we want to expose.
+- Bitmap vs. vector graphics vs. video. 
+  - Clients might want to load the original image in case it is an SVG. For this, they need to know whether an original is a SVG vs bitmap / video before making a request. Specifying the size does not make sense for SVGs in general.
+  - Videos: Some clients could offer a video player, rather than displaying a bitmap thumb.
+- Selecting a specific bitmap format. This seems questionable, but it's conceivable that there could be client support limitations that would make this useful. Content negotiation might be a better alternative for phasing in new formats like webm.
+
+Can we write down some use specific use cases for format / quality selection?",1479414790,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the same conversation, @Pchelolo brought up a potential issue around image format conversion / selection. We do have a need to support format conversions, for example a conversion from SVG to PNG. However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+This requirement is similar to informing the client about original dimensions, except that the desired file type also //needs// to be sent to the API to avoid default parameter fragmentation. Since we also need to support uses without any rewriting (ex: HTML), including the file type in the URL (for example, as a query parameter) seems to make the most sense.
+
+Example original URL, using query string syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`
+
+Another (possibly prettier) option would be to use a custom file extension syntax, but the downside of this would be slightly more effort for parsing.
+
+Edit: Thinking about this some more, I think we should detail a bit more which kind of control over the format we need. Aspects that come to mind:
+
+- Quality selection (esp. for bitmaps). Coarse granularity (high, normal, low) is probably all we want to expose.
+- Bitmap vs. vector graphics. Clients might want to load the original image in case it is an SVG. Specifying the size does not make sense for SVGs in general.
+- Selecting a specific bitmap format. This seems questionable, but it's conceivable that there could be client support limitations that would make this useful.
+
+Can we write down some use specific use cases for format / quality selection?",1479413793,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the same conversation, @Pchelolo brought up a potential issue around image format conversion / selection. We do have a need to support format conversions, for example a conversion from SVG to PNG. However, in order to be able to select such a conversion where needed, clients will either need to know the original type before making the request, or will have to indicate a fixed desired type every time in order to avoid fragmentation (avoid optional default parameter).
+
+This requirement is similar to informing the client about original dimensions, except that the desired file type also //needs// to be sent to the API to avoid default parameter fragmentation. Since we also need to support uses without any rewriting (ex: HTML), including the file type in the URL (for example, as a query parameter) seems to make the most sense.
+
+Example original URL, using query string syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?f=png`
+
+Another (possibly prettier) option would be to use a custom file extension syntax, but the downside of this would be slightly more effort for parsing.",1479407982,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Anomie thanks… The explanation makes sense. 
+
+@GWicke and I spoke at the Reading Services meeting and we are good to go - the content type is enough for the client to make decision on how to render the image - along with being able to deterministically request a specific file format.",1479406414,PHID-USER-zuzwi67gyuz7wfxvuerx,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Fjalapeno, could you say a bit more about why knowing the content type *ahead of time* would be useful to you?",1479321254,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2799548, @Fjalapeno wrote:
+> I was reading over some of the Strawman API  was wondering, is the response going to specify the file type? I couldn't quite tell.
+
+The thumb API being discussed here serves the file data. It should include an appropriate Content-Type header in the HTTP response.
+
+The details of other APIs that might return a pointer to the thumb API are probably out of scope here, even though such other APIs are mentioned.",1479314564,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I was reading over some of the Strawman API  was wondering, is the response going to specify the file type? I couldn't quite tell.
+
+I ask, because for instance, the iOS app would need to handle SVGs differently than it handles handle PNGs (though it could handle both). So knowing the file type ahead of time would be convenient. 
+",1479314051,PHID-USER-zuzwi67gyuz7wfxvuerx,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Gilles, I mostly care about providing original dimensions in a uniform and convenient way across different formats (JSON and HTML). From my point of view, both a standardized JSON structure / HTML attributes, as well as URL parameters are workable, and both have advantages and disadvantages. Overall, I see URL parameters as slightly easier to use, easier to extend & more consistent across contexts, while separate attributes are conceptually cleaner, and avoid sending unnecessary information to the server.",1479145400,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"As for face recognition to guide focused cropping, this is a functionality Thumbor provides out of the box. It even supports doing the computation remotely with a service called remotecv. Which can be useful for example if you want to run that part on servers that have GPUs, which can greatly accelerate face detection.
+
+It's a project of its own to enable that in the Thumbor setup we have, though. This update of the thumbnail URL would probably be a blocker for it, as enabling this new functionality would require at least one new thumbnail parameter.",1479123673,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Passing context like the original dimensions seems like a hack. The thumbnailing server doesn't need it.
+
+The API should be agnostic of specific use cases. This was easily solved in Media Viewer, I don't see why it couldn't be solved the same way in the API calls the apps get their thumb URLs from. Instead of only passing a thumb URL, also pass the original dimensions in additional properties. This is solvable right now, without the need for a thumbnail URL overhaul, the same way this problem was solved for Media Viewer almost 3 years ago.
+
+Not every consumer of the API needs to rewrite existing thumbnail URLs. However, API calls that currently only provide the thumbnail URL as ""information about a thumbnail"" should be able to easily provide original dimensions as well. And any other additional context defined by specific use cases of that API call in the future.
+
+Shoving all functional parameters in a single URL is crowded enough already, let's not add context that could be passed differently to the client and that the server rendering thumbnails doesn't care about.
+
+I think you're conflating your specific needs and the API's needs, as if the thumbnail URL is the only thing that can be touched to achieve your goals.
+
+And the extra metadata APIs should provide about thumbnails in addition to the thumbnail URL could be standardized or even defined in code.",1479123382,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The main potential benefit I see in encoding the original dimensions in the URL would be consistency across formats, and some ease of use from only having to pass the URL to a re-scale function. That said, with some effort we could probably get away with two alternate formats:
+
+- HTML <img> tag: `data-file-{width,height}`, as used by MediaViewer.
+- JSON: A structure like `{ src: ""..."", height: 1024: width: 768 }`, as proposed in the task description.
+
+Compared to a URL only, it is slightly more work to pass those values into a scaling function.",1478881942,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The main benefit of encoding the original dimensions in the URL would be consistency across formats, and some amount of ease of use. That said, with some effort we could probably get away with two alternate formats:
+
+- HTML <img> tag: `data-file-{width,height}`, as used by MediaViewer.
+- JSON: A structure like `{ src: ""..."", height: 1024: width: 768 }`, as proposed in the task description.
+
+Compared to a URL only, it is slightly more work to pass those values into a scaling function.",1478829621,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2787573, @Tgr wrote:
+> Is there any situation where that information could not be easily provided alongside in a more structured way (HTML attribute or API reply field)?
+
+Probably not. At least none that comes to mind right now. This idea came up since I was struggling a bit with also providing an answer for T149450#2783012.
+",1478820513,PHID-USER-tjyfydvd4ncrfvvr6mkr,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786657, @bearND wrote:
+> Requirements for a long term solution should include, in addition to scaling, the ability to crop based on a focus area[1].
+
+Cropping is {T9757}. (There are experimental services which do it: IIIF (T89552) and #imagetweaks. That's less useful than thumb URL integration of course.)
+
+>>! In T66214#2786655, @bearND wrote:
+> Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path).
+
+Is there any situation where that information could not be easily provided alongside in a more structured way (HTML attribute or API reply field)?",1478815927,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786657, @bearND wrote:
+>> look into which users rely on the current thumb format
+> 
+> The apps and MCS rely on the current thumb format to resize thumbnails downwards. If we could solve T75935 or T74328 the we could also use it to resize thumbnails upwards. That alone would solve our immediate needs.
+
+Do you already have access to original dimensions in all cases? If not, then all this scaling (and especially scaling up) is likely to result in rounding errors when calculating the actual dimensions, which would lead to distorted / ugly display.
+
+> Requirements for a long term solution should include, in addition to scaling, the ability to crop based on a focus area[1].
+> 
+> [1] That area is ideally user selectable but defaults to something based on face-detection. The apps could provide the face-detection and upload the desired coordinates to a server somewhere.
+
+In the API requirements, this is covered by general key-value support. Adding the functionality is mostly a matter of implementing it in the backend, and adding the parameter.",1478814266,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786655, @bearND wrote:
+> Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path). I don't want to call it a requirement at this time. Just something that could be useful to avoid having to also provide the original dimensions in other places, like the `data-file-*` attributes in HTML or additional width/height properties for the JSON case.
+
+I think this is an intriguing possibility. This would encapsulate all information needed for scaling an image in just the URL. Example, using query string syntax:
+
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?oh=768&ow=1024`
+More compact, but slightly custom syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?o=1024x768`
+
+To avoid cache fragmentation, we would need to require these parameters in requests, and could also check that they do indeed match the original dimensions.
+
+The main downside I see is slightly larger image URLs being sent back to the server. It's only a few bytes though, which seems unlikely to make a measurable performance difference in practice.",1478813148,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786655, @bearND wrote:
+> Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path). I don't want to call it a requirement at this time. Just something that could be useful to avoid having to also provide the original dimensions in other places, like the `data-file-*` attributes in HTML or additional width/height properties for the JSON case.
+
+I think this is an intriguing possibility. This would encapsulate all information needed for scaling an image in just the URL. Example, using query string syntax:
+
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?oh=768&ow=1024`
+More compact, but custom syntax:
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?o=1024x768`
+
+To avoid cache fragmentation, we would need to require these parameters in requests, and could also check that they do indeed match the original dimensions.
+
+The main downside I see is slightly larger image URLs being sent back to the server. It's only a few bytes though, which seems unlikely to make a measurable performance difference in practice.",1478813120,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2786655, @bearND wrote:
+> Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path). I don't want to call it a requirement at this time. Just something that could be useful to avoid having to also provide the original dimensions in other places, like the `data-file-*` attributes in HTML or additional width/height properties for the JSON case.
+
+I think this is an intriguing possibility. This would encapsulate all information needed for scaling an image in just the URL. Example, using query string syntax:
+
+`/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?oh=768&ow=1024`
+
+To avoid cache fragmentation, we would need to require these parameters in requests, and could also check that they do indeed match the original dimensions.
+
+The main downside I see is slightly larger image URLs being sent back to the server. It's only a few bytes though, which seems unlikely to make a measurable performance difference in practice.",1478811801,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> look into which users rely on the current thumb format
+
+The apps and MCS rely on the current thumb format to resize thumbnails downwards. If we could solve T75935 or T74328 the we could also use it to resize thumbnails upwards. That alone would solve our immediate needs.
+
+Requirements for a long term solution should include, in addition to scaling, the ability to crop based on a focus area[1].
+
+[1] That area is ideally user selectable but defaults to something based on face-detection. The apps could provide the face-detection and upload the desired coordinates to a server somewhere.",1478802566,PHID-USER-tjyfydvd4ncrfvvr6mkr,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Another idea I brought up with GWicke on IRC yesterday is to embed the original dimensions in the URL (either as query parameters or in the path). I don't want to call it a requirement at this time. Just something that could be useful to avoid having to also provide the original dimensions in other places, like the `data-file-*` attributes in HTML or additional width/height properties for the JSON case.
+",1478802484,PHID-USER-tjyfydvd4ncrfvvr6mkr,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Related: {T74328}, {T67383}, {T75935}",1478736772,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"IRC meeting notes discussing this RFC: E355
+
+Next steps:
+
+1) look into which users rely on the current thumb format
+2) investigate effort needed to clean up the mediahandler parameter parsing
+3) discuss possible migration strategies with the traffic team
+4) reconvene with the results.",1478734948,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Maybe you didn't get it after all. There's nothing special about the ""page"" parameter, you could have the same problem with ""t=0s"" and several other options.
+
+I think you'd agree that we shouldn't allow `q=default` or `crop=none` as an alias of omitting those parameters completely.",1478718669,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> and (generally) avoid specifying default values explicitly. (Exception might be the page parameter.)
+
+Maybe you didn't get it after all. There's nothing special about the ""page"" parameter, you could have the same problem with ""t=0s"" and several other options.
+
+> Server side requirements:
+> 
+> - Query string order normalization in Varnish (vmod)
+> 
+> *Cons*
+> 
+> - Familiar query string syntax, but has ordering requirement to avoid cache fragmentation.
+>   - Need custom query string serialization in clients to avoid client cache fragmentation.
+> - Need for query string normalization in Varnish (but would be generally useful).
+
+You said the same thing (""query string normalization"") four times. Either have Varnish do it and don't even check in the API, or just make the API either error or redirect.
+
+BTW, your ""/{size}{/bandwidth}"" format is easy to misuse too, it could easily wind up with ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/330/square if a client gets the ""original spec"" confused, and it'd be possible to get confused if someone's percent-encoder is tuned to not encode characters like "";"" and ""/"" that aren't typically required to be encoded in the query portion of a URI when they're implementing special code to handle your custom format.",1478717277,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I would once again recommend that you write code that would parse, generate and cover a few known use cases for all considered schemes, in a language with decent URL parsing libraries. Limiting to bare bones string manipulation would skew things in favor of the custom formats, which I think is not a good benchmark based on modern development practices.
+
+And I mean writing that code for the existing URI scheme and the two prototype versions discussed. A lot of judgement is made here about what is practical, what is easy, what mistakes are possible, without code consuming those schemes to demonstrate those hypothetical issues.
+
+Between subjective calls on how ""hard"" something would be for client developers, to extreme examples of languages that have terrible hash behavior defaults in the context of URLs, I think the debate of the quality of each option is veering into very subjective and undemonstrative territory based on a growing army of straw men.
+
+I think future-proofness is what matters most here, but the debate of which format is best in terms of developer perspective seems hard to avoid as it keeps coming up. I just don't see a resolution coming out of people arguing that one is best based on a very hypothetical scenario.",1478715550,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I would once again recommend that you write code that would parse, generate and cover a few known use cases for all considered schemes, in a language with decent URL parsing libraries. Limiting to bare bones string manipulation would skew things in favor of the custom formats, which I think is not a good benchmark based on modern development practices.
+
+And I mean writing that code for the existing URI scheme and the two prototype versions discussed. A lot of judgement is made here about what is practical, what is easy, what mistakes are possible, without code consuming those schemes to demonstrate those hypothetical issues.
+
+Between subjective calls on how ""hard"" something would be for client developers, to extreme examples of languages that have terrible hash behavior defaults in the context of URLs, I think the debate of the quality of each option is veering into very subjective and undemonstrative territory based on a growing army of straw men.",1478715406,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"""Easy to select size and thumb type."" How is it not easy in the second example? What constitutes ""mis-use""?",1478714966,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,I'm sorry but the pros and cons you've entered are completely biased and focus on very subjective properties.,1478714839,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,The pros and cons of the current URI scheme should be included in the same matrix. Because you'll find that almost all of the upsides you're bringing up for the scheme currently in the task description also apply to the current scheme.,1478713772,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The point is that a custom ordered-querystring serialization function will be needed, while in the path-based API regular path manipulation functions will do the right thing wrt order.
+
+I think it's time to start collecting pros & cons like these for the different options, and then discuss the overall tally. API design is about finding the best trade-offs between frequently conflicting requirements. Ease of use for the most common use cases is just one of those criteria.",1478713364,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"You can look at any two formats and make up a use case that would be easier in one than the other. I don't think that should be the starting point of what the format is. That use case isn't very relevant in the infinite number of ways people might parse, transform and generate those URLs.",1478712949,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In both cases you need to parse a string and insert the value in the right place. I hope we're not going to design an API a certain way because we'd like a hypothetical developer to be able to deal with strings directly with explodes and appends rather than use a URL parsing method which nowadays should be available in all languages. If anything parsing and modifying a custom string format requires more lines of code than parsing a url and changing a value using a library designed for that.
+
+And you're making such a specific use case a first class citizen. It can't be what defines the whole format. By definition an API can be used in many ways, including many we can't foresee.",1478712842,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles: Having such author-supplied parameters in a query string means that changing the size is not just a matter of adding a *single* query parameter. This means that clients need to deal with the ordering issue, even if all they care about is the size.
+
+Compared to a URL scheme where ""advanced"" (typically author-supplied) parameters are separate from the common width & thumb type, this complicates clients and makes using the API harder.",1478712513,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles: Having such author-supplied parameters in a thumb means that changing the size is not just a matter of adding a *single* query parameter. This means that clients need to deal with the ordering issue, even if all they care about is the size.
+
+Compared to a URL scheme where ""advanced"" (typically author-supplied) parameters are separate from the common width & thumb type, this complicates clients and makes using the API harder.",1478712490,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Provided by editors in the context of wikitext, yes. I thought you meant the media's author was somehow able to set default parameters.
+
+That just means those parameters are optional. I don't see how that impacts ordering. In fact all parameters are optional if in the new scheme a lack of query parameters returns the original.",1478712274,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Provided by editors in the context of wikitext, yes. I thought you meant the media's author was somehow able to set default parameters.
+
+That just means those parameters are optional. I don't see how that impacts ordering. In fact all parameter are optional if in the new scheme a lack of query parameters returns the original.",1478712246,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Provided by editors in the context of wikitext, yes. I thought you meant the media's author was somehow able to set default parameters.
+
+That just means those parameters are optional. I don't see how that impacts ordering. In fact all parameter are optional if in the new scheme lacks of query parameters returns the original.",1478712224,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>>! In T66214#2782454, @GWicke wrote:
+>> This is because any thumbnail can have any number of author-supplied parameters already
+> 
+> Can you provide a concrete example? I don't think I'm familiar with that feature.
+
+Many advanced parameters are mostly author-supplied. Examples: page number, video thumb offset, content language for SVGs
+
+See brion's comment in T66214#1743938.
+
+Regarding API versioning & stability: Of course we can't predict the future perfectly & need mechanisms for cleanly evolving our APIs without breaking existing clients. This doesn't mean though that we should throw all caution in the wind, and ignore versioning and validation rules, or make no effort to design APIs in a thoughtful way based on our best knowledge.",1478712292,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>>! In T66214#2782454, @GWicke wrote:
+>> This is because any thumbnail can have any number of author-supplied parameters already
+> 
+> Can you provide a concrete example? I don't think I'm familiar with that feature.
+
+Many advanced parameters are mostly author-supplied. Examples: page number, video thumb offset, content language for SVGs
+
+See brion's comment in T66214#1743938.",1478711885,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2782449, @Anomie wrote:
+> I think redirects are probably //essential//. You say that the performance impact of redirects as a mechanism to encourage clients to update their code is bad, but throwing fatal errors at them is far, far worse.
+
+Where did I state that throwing a fatal error was the alternative? That's nonsense.
+
+> Sure, put a Varnish layer in front of the API as deployed for WMF to canonicalize the URLs as much as possible so the API itself doesn't have to return redirects. [[https://phabricator.wikimedia.org/T149408#2759693|But don't make a complicated Varnish layer be required for the API to be easily usable by clients of low-traffic installations.]]
+
+Nothing in what I proposed would make the URL scheme for small installations problematic. We're talking about improving cache fragmentation at the Varnish level for Varnish itself. On smaller wikis by definition the image set isn't gigantic and should they set up a caching layer the way we do with Varnish, fragmentation probably wouldn't be the end of the world. And that's assuming misbehaving clients on top of small wikis. Small wikis are quite likely to either be using well-supported extensions, which by default would probably do the right thing after this migration happens, or their own code, in which case they are responsible for their own sensible behavior when it comes to cache fragmentation at the backend caching layer. If anything the flexibility of a query string-based solution makes things easier for small wikis, as the logic behind the scheme is more universal and much less WMF-specific than what we currently have.
+
+>>! In T66214#2782563, @Anomie wrote:
+> Not necessarily. A naive query-string builder based on a python dict or a perl hash, for example, is liable to have a random parameter ordering. Perl, in particular, [[http://perldoc.perl.org/perlsec.html#Algorithmic-Complexity-Attacks|intentionally randomizes the order of hash entries for security reasons]].
+
+That's something developers using those languages should be aware of. We can't design a URL scheme or API defensively, based on terrible defaults in language X or Y. It's those languages problem, not ours. And it's probably the cause of cache fragmentation on many APIs, if constructing URLs with the helper functions in those languages results in random parameter ordering with given values. And while the example you give is for hashes, do functions in those languages that construct URLs really do that too, given who counter-productive that obviously is for caching?
+
+
+>>! In T66214#2782454, @GWicke wrote:
+> Maintaining all kinds of specific parameter validation and rewrite rules in Varnish, and keeping them in sync with the actual backend service does not sound very practicable. If we do our job of designing APIs right, then we shouldn't need to resort to such band-aids. 
+
+That's wishful thinking, because designing a URL scheme now can only be based on what you know now. You can't predict the future and unforeseen needs will come up that will directly conflict with an overly broad policy like ""we can't introduce new parameters with defaults on old urls"". The current URL scheme is testament that future needs are difficult to anticipate. Look at the history of the existing URL scheme and plan for the obvious: it will have to change and it will need massaging for backwards compatibility. If you don't plan for that, we'll get stuck again with a new format that has an equally painful migration plan as the current one. The inflexibility and hard rules need to go away, because that's exactly the source of how painful change in that area is at the moment.
+
+So far the only blocker to having a fully flexible format seems to be cache fragmentation. We can solve Varnish cache fragmentation, we just need to figure out how far that might have to go once we go down that rabbit hole. We can solve it at the client level by propagating best practices. It could be as simple as issuing a warning in headers of the response when a client doesn't have sorted parameters, in addition to documentation and communication.
+
+>>! In T66214#2782454, @GWicke wrote:
+> This is because any thumbnail can have any number of author-supplied parameters already
+
+Can you provide a concrete example? I don't think I'm familiar with that feature.",1478709245,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2782454, @GWicke wrote:
+> The bigger issue I see with query strings is that (contrary to what I thought earlier) all clients really need to implement sorted query string serialization if they want to avoid fragmenting client-side caches.
+
+I'm not opposed to this, although it does make it harder for humans to test it by putting URLs into the browser. But we'd also have to specify exactly which characters must and must not be percent-encoded (e.g. [a-zA-Z0-9._~-] must never be encoded and all others must always be) and clearly specify the sorting method (e.g. ASCIIbetical sort on encoded key=value pairs).
+
+> This is because any thumbnail can have any number of author-supplied parameters already, and changing the size of the thumb will require rewriting the query string, preserving the order. This is a loss in usability compared to separating author-supplied parameters from size & quality parameters.
+
+If size and quality are specified sanely as unique query parameters such as `size=$ABC` (or even `s=$ABC`) and `q=$XYZ`, I can't see any way that changing the specific values of $ABC or $XYZ would change the ordering of the parameters.",1478705288,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2782384, @Gilles wrote:
+> In regards to the client cache fragmentation, I think most clients are consistent with themselves and that's what matters.
+
+Not necessarily. A naive query-string builder based on a python dict or a perl hash, for example, is liable to have a random parameter ordering. Perl, in particular, [[http://perldoc.perl.org/perlsec.html#Algorithmic-Complexity-Attacks|intentionally randomizes the order of hash entries for security reasons]].",1478704998,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Currently the Varnish task seem to only focus on parameter reordering, when this is already an early sign that as the URL scheme evolves we'll want more parsing and rewriting to happen than just reordering in order to avoid cache fragmentation through future updates of the URL scheme.
+
+Maintaining all kinds of specific parameter validation and rewrite rules in Varnish, and keeping them in sync with the actual backend service does not sound very practicable. If we do our job of designing APIs right, then we shouldn't need to resort to such band-aids. For the case brought up by @anomie, there should really be little reason to bother stripping `page=1`. If we want to avoid that fragmentation internally, then we can return a redirect from the backend service for one of those, and set up a generic Varnish rule to follow those redirects on behalf of the client, avoiding round-trip penalties.
+
+The bigger issue I see with query strings is that (contrary to what I thought earlier) all clients really need to implement sorted query string serialization if they want to avoid fragmenting client-side caches. This is because any thumbnail can have any number of author-supplied parameters already, and changing the size of the thumb will require rewriting the query string, preserving the order. This is a loss in usability compared to separating author-supplied parameters from size & quality parameters.",1478703790,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Currently the Varnish task seem to only focus on parameter reordering, when this is already an early sign that as the URL scheme evolves we'll want more parsing and rewriting to happen than just reordering in order to avoid cache fragmentation through future updates of the URL scheme.
+
+Maintaining all kinds of specific parameter validation and rewrite rules in Varnish, and keeping them in sync with the actual backend service does not sound very practicable. If we do our job of designing APIs right, then we shouldn't need to resort to such band-aids. For the case brought up by @anomie, there should really be little reason to bother stripping `page=1`.
+
+The bigger issue I see with query strings is that (contrary to what I thought earlier) all clients really need to implement sorted query string serialization if they want to avoid fragmenting client-side caches. This is because any thumbnail can have any number of author-supplied parameters already, and changing the size of the thumb will require rewriting the query string, preserving the order. This is a loss in usability compared to separating author-supplied parameters from size & quality parameters.",1478703487,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781793, @GWicke wrote:
+> @anomie, I see- ""page 1"" being the default is indeed one way where there could be fragmentation. It might indeed make sense to make an exception to the ""no fragmentation"" rule in this case, and either return an identical thumbnail, or a HTTP redirect to the canonical version of this thumb.
+
+Good. I don't really care about identical thumbnail versus HTTP redirect, I was just concerned that an HTTP error as you seemed to be saying would turn out to be problematic.
+
+> In any case, existing clients wouldn't break, as none of them would be using the (new) page parameter.
+
+They would if you added it as a non-optional parameter, per your earlier statement that optional parameters wouldn't be allowed.
+
+
+>>! In T66214#2782399, @Gilles wrote:
+> I think redirects should be a last resort. An extra round trip can be very costly for users in terms of performance. Even as a mechanism to encourage clients to update their code, it's an unnecessary punishment on users who don't know how to or can't update their dated clients. 
+
+I think redirects are probably //essential//. You say that the performance impact of redirects as a mechanism to encourage clients to update their code is bad, but throwing fatal errors at them is far, far worse.
+
+Sure, put a Varnish layer in front of the API as deployed for WMF to canonicalize the URLs as much as possible so the API itself doesn't have to return redirects. [[https://phabricator.wikimedia.org/T149408#2759693|But don't make a complicated Varnish layer be required for the API to be easily usable by clients of low-traffic installations.]]",1478703358,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781793, @GWicke wrote:
+> @anomie, I see- ""page 1"" being the default is indeed one way where there could be fragmentation. It might indeed make sense to make an exception to the ""no fragmentation"" rule in this case, and either return an identical thumbnail, or a HTTP redirect to the canonical version of this thumb.
+> 
+> In any case, existing clients wouldn't break, as none of them would be using the (new) page parameter.
+
+I think redirects should be a last resort. An extra round trip can be very costly for users in terms of performance. Even as a mechanism to encourage clients to update their code, it's an unnecessary punishment on users who don't know how to or can't update their dated clients. Imho solving that at the URL sanitation level in Varnish is the way to go. Which means it should be part of the requirements for the software solution to that problem (which so far looks like a vmod, either bringing Etsy's up to date for Varnish 4 or writing a custom one). Currently the Varnish task seem to only focus on parameter reordering, when this is already an early sign that as the URL scheme evolves we'll want more parsing and rewriting to happen than just reordering in order to avoid cache fragmentation through future updates of the URL scheme.",1478702158,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781285, @GWicke wrote:
+> The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+Where is that mentioned in the task description? Are you referring to a more detailed definition hosted elsewhere? It should be linked from the task description or added to it.
+
+I fail to see how quality and cropping format are related, and it's yet another separator character for those two parameters. 
+
+>>! In T66214#2781285, @GWicke wrote:
+> /2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+
+This looks much saner to me.
+
+Considering that parameter order sanitation at the Varnish layer is desirable for many APIs, I think it makes sense to make it a dependency. Instead of designing an awkward format that enforces parameter order. If there's an upside to be had in moving to a new format without adding new features, it's that. Something based on query strings that are ordered at the Varnish layer is flexible, easy to generate/parse, extensible in ways that the existing URL scheme isn't. If we go for something that has the same constraints as the current URL scheme and is just different, then I stand by my earlier comment and @tgr's position that this is a lot of work just for aesthetics.
+
+In regards to the client cache fragmentation, I think most clients are consistent with themselves and that's what matters. I.e. if your mobile app and desktop browser don't use the same parameter ordering, it doesn't matter as they each have their separate cache. And they are are likely to request different thumbnail sizes. The reverse proxy scenario is so far fetched that I don't think it should be considered. What are the odds that different client types on the same network going through a reverse proxy request the exact same thumbnail, with the same parameter, including the same size just ordered differently? That's so narrow, I don't think we should optimize for that unlikely scenario.
+
+
+
+>>! In T66214#2781560, @Anomie wrote:
+> Say we didn't already have a parameter to select the page of a PDF. Then we add the parameter. Either the parameter needs to be optional, so probably ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?w=220"" and ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?page=1&w=220"" return the same thing, or every client that doesn't know about the new page parameter (and so uses the first URL) starts getting errors. Or, I suppose, the interface could be strange and throw an error for page=1 but not any other (valid) page.
+
+That's only problematic if we want to limit Varnish's understanding of the underlying parameters. Otherwise this is solved in the URL normalization happening at the Varnish level by stating that ""page=1"" should be stripped if encountered, because it's the default in terms of backwards compatibility. I think it will be a trade-off we'll have to consider every time we extend the available parameters. Cache fragmentation versus complexity of the code processing query parameters at the Varnish level. We'll have to make sure that whatever does the URL wrangling in Varnish performs well when we have dozens of special cases for different APIs. For something so high traffic as thumbnails I think it's kind of inevitable if we go down that road.
+
+>>! In T66214#2781961, @Tgr wrote:
+>  If we decide dropping that optimization to be able to skip some imageinfo API calls is a good tradeoff
+
+But you still can't skip imageinfo if you don't know the dimensions of the original.
+",1478701795,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781560, @Anomie wrote:
+> Say we didn't already have a parameter to select the page of a PDF. Then we add the parameter. Either the parameter needs to be optional, so probably ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?w=220"" and ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?page=1&w=220"" return the same thing, or every client that doesn't know about the new page parameter (and so uses the first URL) starts getting errors. Or, I suppose, the interface could be strange and throw an error for page=1 but not any other (valid) page.
+
+That's only problematic if we want to limit Varnish's understanding of the underlying parameters. Otherwise this is solved in the URL normalization happening at the Varnish level by stating that ""page=1"" should be stripped if encountered, because it's the default in terms of backwards compatibility. I think it will be a trade-off we'll have to consider every time we extend the available parameters. Cache fragmentation versus complexity of the code processing query parameters at the Varnish level. We'll have to make sure that whatever does the URL wrangling in Varnish performs well when we have dozens of special cases for different APIs. For something so high traffic as thumbnails I think it's kind of inevitable if we go down that road.
+
+>>! In T66214#2781961, @Tgr wrote:
+>  If we decide dropping that optimization to be able to skip some imageinfo API calls is a good tradeoff
+
+But you still can't skip imageinfo if you don't know the dimensions of the original.
+
+>>! In T66214#2781285, @GWicke wrote:
+> The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+Where is that mentioned in the task description? Are you referring to a more detailed definition hosted elsewhere? It should be linked from the task description or added to it.
+
+I fail to see how quality and cropping format are related, and it's yet another separator character for those two parameters. 
+
+>>! In T66214#2781285, @GWicke wrote:
+> /2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+
+This looks much saner to me.
+
+Considering that parameter order sanitation at the Varnish layer is desirable for many APIs, I think it makes sense to make it a dependency. Instead of designing an awkward format that enforces parameter order. If there's an upside to be had in moving to a new format without adding new features, it's that. Something based on query strings that are ordered at the Varnish layer is flexible, easy to generate/parse, extensible in ways that the existing URL scheme isn't. If we go for something that has the same constraints as the current URL scheme and is just different, then I stand by my earlier comment and @tgr's position that this is a lot of work just for aesthetics.
+
+In regards to the client cache fragmentation, I think most clients are consistent with themselves and that's what matters. I.e. if your mobile app and desktop browser don't use the same parameter ordering, it doesn't matter as they each have their separate cache. And they are are likely to request different thumbnail sizes. The reverse proxy scenario is so far fetched that I don't think it should be considered. What are the odds that different client types on the same network going through a reverse proxy request the exact same thumbnail, with the same parameter, including the ss ordered differently
+
+
+",1478701732,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The reason the current thumb URL format does not allow larger-than-original (and in most cases same-as-original) sizes is to avoid cache fragmentation (which could be circumvented in the reverse proxy but not in the client). If we decide dropping that optimization to be able to skip some imageinfo API calls is a good tradeoff, then we can keep the current URL syntax and make the original file some simple variation of that syntax (say `orig` instead of `123px`). That's a simple change, and would capture most benefits of the proposal. Granted the current URL format looks horrible, and the proposed one looks nice, but what the migration would entail is rewriting file URL generation/parsing in MediaWiki, updating every media handler extension, updating every client (or forcing their maintainers to update them), forcing everyone to change URL rewrite rules, changing VCL rules... That seems like a pretty high price to pay for aesthetics.",1478686029,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The reason the current thumb URL format does not allow larger-than-original (and in most cases same-as-original) sizes is to avoid cache fragmentation (which could be circumvented in the reverse proxy but not in the client). If we decide dropping that optimization to be able to skip some imageinfo API calls is a good tradeoff, then we can keep the current URL syntax and make the original file some simple variation of that syntax (say `orig` instead of `123px`). That's about ten lines of PHP changed, and would capture most benefits of the proposal. Granted the current URL format looks horrible, and the proposed one looks nice, but what the migration would entail is rewriting file URL generation/parsing in MediaWiki, updating every media handler extension, and updating every client (or forcing their maintainers to update them). That seems like a pretty high price to pay for aesthetics.",1478682119,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@anomie, I see- ""page 1"" being the default is indeed one way where there could be fragmentation. It might indeed make sense to make an exception to the ""no fragmentation"" rule in this case, and either return an identical thumbnail, or a HTTP redirect to the canonical version of this thumb.
+
+In any case, existing clients wouldn't break, as none of them would be using the (new) page parameter.",1478663501,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@anomie, I see- ""page 1"" being the default is indeed one way where there could be fragmentation. It might indeed make sense to make an exception to the ""no fragmentation"" rule in this case, and either return an identical thumbnail, or a HTTP redirect to the canonical version of this thumb.
+
+In any case, existing client wouldn't break, as none of them would be using the (new) page parameter.",1478663468,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Say we didn't already have a parameter to select the page of a PDF. Then we add the parameter. Either the parameter needs to be optional, so probably ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?w=220"" and ""/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?page=1&w=220"" return the same thing, or every client that doesn't know about the new page parameter (and so uses the first URL) starts getting errors. Or, I suppose, the interface could be strange and throw an error for page=1 but not any other (valid) page.",1478648190,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@anomie, adding parameters without changing the semantics of existing parameters won't break any existing clients, as none of those would be using the new parameter yet. In fact, this is another benefit of strict validation.
+
+It's possible I misunderstood you, though. If so, could you elaborate?",1478646799,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2781285, @GWicke wrote:
+> 2) Validate parameters in the backing service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed.
+
+That could be problematic if at any point in the future we want to add additional parameters, since if you don't allow optional parameters then you'll be breaking every client in existence every time you do so.
+
+For example, if we didn't already have a time-index parameter for thumbnailing videos, or a language parameter for SVGs, or a page parameter for PDFs, etc.",1478645827,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> the description mentions the response containing JSON
+
+This is about other APIs, such as pageinfo & other references to thumbnails providing original dimensions along with the base thumb URL. It is not about the thumb API itself, which returns thumbnails.
+
+> There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+```
+# Low resolution (for mobile)
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres
+# Low resolution + square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres-square
+# Extra high quality thumb
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/highres
+# Default quality, square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/square
+```
+
+If we used query strings in general for anything but the base image, this could look like this:
+
+```
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=high&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&w=220
+```
+
+To make this work without fragmenting caches, we'd need:
+
+1) Query string order normalization in Varnish: T138093
+2) Validate parameters in the backing service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed. Only a single size spec can be used to select a given thumbnail size (`w` parameter bounding the width).
+3) Query string order normalization in clients, to avoid client cache fragmentation.
+
+Points 1) and 2) are very doable I think, but the third point somewhat complicates basic tasks like selecting the thumb size. However, if we assume that most clients *only* need to select the size & thus only need a single parameter, then this should be workable.",1478642871,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> the description mentions the response containing JSON
+
+This is about other APIs, such as pageinfo & other references to thumbnails providing original dimensions along with the base thumb URL. It is not about the thumb API itself, which returns thumbnails.
+
+> There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+```
+# Low resolution (for mobile)
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres
+# Low resolution + square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres-square
+# Extra high quality thumb
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/highres
+# Default quality, square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/square
+```
+
+If we used query strings in general for anything but the base image, this could look like this:
+
+```
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=high&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&w=220
+```
+
+To make this work without fragmenting caches, we'd need:
+
+1) Query string order normalization in Varnish: T138093
+2) Validate parameters in the backing service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed. Only a single size spec can be used to select a given thumbnail size.
+3) Query string order normalization in clients, to avoid client cache fragmentation.
+
+Points 1) and 2) are very doable I think, but the third point somewhat complicates basic tasks like selecting the thumb size. However, if we assume that most clients *only* need to select the size & thus only need a single parameter, then this should be workable.",1478642828,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> the description mentions the response containing JSON
+
+This is about other APIs, such as pageinfo & other references to thumbnails providing original dimensions along with the base thumb URL. It is not about the thumb API itself, which returns thumbnails.
+
+> There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+```
+# Low resolution (for mobile)
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres
+# Low resolution + square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres-square
+# Extra high quality thumb
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/highres
+# Default quality, square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/square
+```
+
+If we used query strings in general for anything but the base image, this could look like this:
+
+```
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=high&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&w=220
+```
+
+To make this work without fragmenting caches, we'd need:
+
+1) Query string order normalization in Varnish: T138093
+2) Validate parameters in the backing service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed. Only support one size spec for a given thumbnail size.
+3) Query string order normalization in clients, to avoid client cache fragmentation.
+
+Points 1) and 2) are very doable I think, but the third point somewhat complicates basic tasks like selecting the thumb size. However, if we assume that most clients *only* need to select the size & thus only need a single parameter, then this should be workable.",1478642782,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> the description mentions the response containing JSON
+
+This is about other APIs, such as pageinfo & other references to thumbnails providing original dimensions along with the base thumb URL. It is not about the thumb API itself, which returns thumbnails.
+
+> There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+The current strawman combines quality and format in a ""type"" parameter. Some examples for illustration:
+
+```
+# Low resolution (for mobile)
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres
+# Low resolution + square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/lowres-square
+# Extra high quality thumb
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/highres
+# Default quality, square crop
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/220/square
+```
+
+If we used query strings in general for anything but the base image, this could look like this:
+
+```
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&q=low&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?q=high&w=220
+/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12?crop=square&w=220
+```
+
+To make this work without fragmenting caches, we'd need:
+
+1) Query string order normalization in Varnish: T138093
+2) Validate parameters in the service strictly, so that each unique thumb can only be accessed through one unique set of query parameters. No ignored or optional-default parameters can be allowed. Only support one size spec for a given thumbnail size.
+3) Query string order normalization in clients, to avoid client cache fragmentation.
+
+Points 1) and 2) are very doable I think, but the third point somewhat complicates basic tasks like selecting the thumb size. However, if we assume that most clients *only* need to select the size & thus only need a single parameter, then this should be workable.",1478642698,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+I'm now noticing something strange that I missed before, as the description mentions the response containing JSON? I would have expected that the response body would be the binary image, so that browsers can consume it directly in the no-JS case. Extra information like original URL path and original image dimensions can be passed via HTTP headers in the response, no need for JSON.
+
+I like the idea of ensuring the ordering in Varnish, if it is possible. I haven't seen how that works in VCL, have you checked how that would be implemented? That would allow us to maintain flexibility on the client side, as the URL scheme could simply be the classic &= separated URL format we all know, for example. Which would allow many clients to leverage existing libraries to construct and parse URLs in that format (which I believe is just a very old convention). It would be the client's responsibility to have sensible consistency in ordering across requests for client caches' sake, but cache fragmentation on our end is entirely avoided and I think that's all we should worry about, as all the clients we'll be responsible for will follow best practices in that respect.",1478640706,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"There is no example URL of the orthogonal case. Bandwidth is mentioned, but no example of its use is provided and even the path spec contradicts the ""square"" example.
+
+I'm now noticing something strange that I missed before, as the description mentions the response containing JSON? I would have expected that the response body would be the binary image, so that browsers can consume it directly in the no-JS case. Extra information like original URL path and original image dimensions can be passed via HTTP headers in the response, no need for JSON.
+
+I like the idea of ensuring the ordering in Varnish, if it is possible. I haven't seen how that works in VCL, have you checked how that would be implemented? That would allow us to maintain flexibility on the client side, as the URL scheme could simply be the classic &= separated URL format we all know, for example. Which would allow many clients to leverage existing libraries to construct and parse URLs in that format (which I believe is just a very old convention). It would be the client's responsibility to have sensible consistency in ordering across requests for client caches' sake, but cache fragmentation is entirely avoided and I think that's all we should worry about, as all the clients we'll be responsible for will follow best practices in that respect.",1478640661,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@gilles, there are several examples illustrating page and media thumbnails, as well as the (orthogonal) selection of size and thumb type / quality. The ordered key-value syntax can be used to encode rotation, cropping, effects, or other features we have not thought of yet. I'm happy to iterate through a couple of permutations if that would help to allay doubts. Dividing the API in an original spec (typically author-controlled) vs. the basic size & thumb type / quality selection was proposed by @brion earlier in this thread: T66214#1743938.
+
+I don't have overly strong opinions on the exact separators used to encode the original spec. For example, we could also use query string syntax, following the example of [media fragments](https://www.w3.org/TR/media-frags/). As long as the format is hard to abuse, and avoids cache fragmentation, a lot of options can work. If we use query strings, then we might want to strongly consider normalizing the order of parameters in Varnish, as most query string libraries don't provide any order guarantees.",1478639916,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"No examples of what rotation, cropping or effects would look like are provided.
+
+No complex examples of current capabilities are provided either, like a PDF page in low quality. Which would bring up whether the proposed format enforces optional parameter ordering. This is a property that the current scheme has and ensure good caching. At the moment it seems like things aren't thought through enough. There is no edge against the status quo, because you mention upsides that are theoretical, with no examples to back them up.
+
+To demonstrate sensibility of the proposed format, the most extreme example should be considered, just to get an idea of what it looks like to construct and parse such a URL.
+
+For example I think that using 3 different separator characters in the examples needlessly complexities parsing those URLs. Writing PoC code that generates and parses those URLs would help guide the thinking here, imho. Even better if comparing that to functions that generate and parse the current URLs. Especially if we're going to enforce ordering to ensure caching that's as good as now. Which we probably should, with the anticipated expansion of available features.",1478636541,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs, and we should aim to keep API usage for the common size & thumb type / quality selection as simple as possible. In the proposal, this is done by encoding those parameters in separate path components, making it trivial to construct the thumb URL in most cases.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.
+
+> Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL.
+
+Current thumbnail URLs are private to MediaWiki, and are explictly not intended or designed to be used as APIs. Clients can ignore this rule, but will break once we change our private thumb URL structure, for example by introducing a documented, stable thumb API.",1478635703,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs, and we should aim to keep API usage for the common size & thumb type / quality selection as simple as possible. In the proposal, this is done by encoding those parameters in separate path components.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.
+
+> Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL.
+
+Current thumbnail URLs are private to MediaWiki, and are explictly not intended or designed to be used as APIs. Clients can ignore this rule, but will break once we change our private thumb URL structure, for example by introducing a documented, stable thumb API.",1478635667,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs, and we should aim to keep API usage for the common size & thumb type / quality as simple as possible. In the proposal, this is done by encoding those parameters in separate path components.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.
+
+> Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL.
+
+Current thumbnail URLs are private to MediaWiki, and are explictly not intended or designed to be used as APIs. Clients can ignore this rule, but will break once we change our private thumb URL structure, for example by introducing a documented, stable thumb API.",1478635643,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs though, and we should aim to keep API usage for the common size & thumb type / quality as simple as possible. In the proposal, this is done by encoding those parameters in separate path components.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.
+
+> Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL.
+
+Current thumbnail URLs are private to MediaWiki, and are explictly not intended or designed to be used as APIs. Clients can ignore this rule, but will break once we change our private thumb URL structure, for example by introducing a documented, stable thumb API.",1478635575,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> It seems to me like the goal is to simplify what's currently available, with no plan to add new features
+
+The design is providing flexibility and extensibility in the specification of originals. I believe this covers the kind of extensions you mentioned when we last spoke about this, including rotation, cropping, or potentially effects. In order to avoid cache fragmentation, it defines simple deterministic rules for constructing the URL, and requires clients to adhere to them.
+
+Most clients don't need to manipulate the more complex original specs though, and we should aim to keep API usage for the common size & thumb type / quality as simple as possible. In the proposal, this is done by encoding those parameters in separate path components.
+
+> You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme.
+
+Once we decide to switch to an official thumb API, then we should clearly switch over all uses of thumbnails in MediaWiki & other services. The fact that current thumb URLs are private implementation details helps us here, as we are free to change their structure at any time. To make this happen, we need to establish a roadmap & clear ownership of different parts of the migration process. This RFC is intended to move us closer to an agreement on how a proper thumb API will look, and should be the starting point for the development of a migration roadmap.",1478635421,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2772934, @Tgr wrote:
+> Projects which can get away with being Wikimedia-only (such as the mobile apps) could just use the Thumbor API directly, though. That seems like a much less ambitious project than replacing the MediaWiki thumb API.
+
+That depends on what you want the caching and storage strategy to be. If you want to achieve reusing the same Varnish entries, as suggested in the current version of the task description, the URL translation that has to be done in Varnish becomes more complex. Furthermore, given that in the current state of affairs Thumbor is responsible for storing the resulting thumbnails in Swift, it needs Swift sharding awareness.
+
+Currently I've written an URL adapter for Thumbor for it to take care of that translation, this way Thumbor can take Wikimedia URLs directly, like so:
+
+http://127.0.0.1:8888/images/wikipedia/commons/thumb/a/a6/Chamarel_Falls_Mauritius_2.JPG/qlow-300px-Chamarel_Falls_Mauritius_2.JPG
+
+Now, you could achieve the same image by requesting this, going through the standard Thumbor URL handler:
+
+http://127.0.0.1:8888/unsafe/300x/filters:quality(40):conditional_sharpen(0.0,0.8,1.0,0.0,0.85):format(jpg)/upload.wikimedia.org/wikipedia/commons/a/a6/Chamarel_Falls_Mauritius_2.JPG
+
+But that wouldn't save the end result in Swift. Granted, we could reconstruct the Wikimedia URL from the Thumbor URL, or parse the same information from it, and make it save the output to Swift. But I felt that it was better not to mess with default Thumbor behavior because people have expressed the need to want to use Thumbor without saving the results in Swift.
+
+I would like a new service to replace what rewrite.py currently does and would be responsible for coordinating the various services involved in thumbnailing (currently Thumbor, Swift and the Mediawiki API). It would basically combine all that URL parsing/translating logic + swift sharding currently found in rewrite.py and thumbor, keeping Thumbor and Swift dumb. Thumbor would only care about returning a thumbnail, not where it gets stored. And Swift would only care about writing and reading content and Swift locations, without the need to rewrite URLs and proxy requests itself. This doesn't solve the Varnish side of things, though. If you want Varnish to support two URL schemes pointing to the same Varnish entry, there's no escaping writing some VCL or a vmod.
+
+Now, regarding the current plan of this task. It seems to me like the goal is to simplify what's currently available, with no plan to add new features, since the ""limited choice"" property ensure that a new URL scheme would be as efficient cache-wise as the old one. The deployment plan, if the Varnish side of things can be done, looks ok. But what I dislike about this plan is that it's not a migration plan. You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme. Creating that much technical debt without an owner shouldn't be allowed. I would support this plan if it was a full migration one and the project included upgrading mediawiki's built-in URL scheme to a cleaner, more extensible one.
+
+Furthermore, the value of a migration aiming for 1-to-1 mapping between two URL schemes is questionable. It's a lot of work, potentially a dual URL scheme for the foreseeable future due to the lack of plan to get rid of the old one, a new service to support. What do we get out of it that's new? A few minutes of developer time saved figuring out the existing URL scheme? These URLs will be consumed by programs that don't care about their beauty.
+
+Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL. It's just a convenience to have it made for you and to have the fallback to the original when a width that's too large is requested. The newly proposed URL scheme doesn't solve that. You still can't know the dimensions of the original in advance if you only have the filename and you are susceptible to requesting a size that can't be rendered. Just like you would be if you constructed a thumbnail URL manually without using imageinfo.",1478539413,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2772934, @Tgr wrote:
+> Projects which can get away with being Wikimedia-only (such as the mobile apps) could just use the Thumbor API directly, though. That seems like a much less ambitious project than replacing the MediaWiki thumb API.
+
+That depends on what you want the caching and storage strategy to be. If you want to achieve reusing the same Varnish entries, as suggested in the current version of the task description, the URL translation that has to be done in Varnish becomes more complex. Furthermore, given that in the current state of affairs Thumbor is responsible for storing the resulting thumbnails in Swift, it needs Swift sharding awareness.
+
+Currently I've written an URL adapter for Thumbor for it to take care of that translation, this way Thumbor can take Wikimedia URLs directly, like so:
+
+http://127.0.0.1:8888/images/wikipedia/commons/thumb/a/a6/Chamarel_Falls_Mauritius_2.JPG/qlow-300px-Chamarel_Falls_Mauritius_2.JPG
+
+Now, you could achieve the same image by requesting this, going through the standard Thumbor URL handler:
+
+http://127.0.0.1:8888/unsafe/300x/filters:quality(10):conditional_sharpen(0.0,0.8,1.0,0.0,0.85):format(jpg)/upload.wikimedia.org/wikipedia/commons/a/a6/Chamarel_Falls_Mauritius_2.JPG
+
+But that wouldn't save the end result in Swift. Granted, we could reconstruct the Wikimedia URL from the Thumbor URL, or parse the same information from it, and make it save the output to Swift. But I felt that it was better not to mess with default Thumbor behavior because people have expressed the need to want to use Thumbor without saving the results in Swift.
+
+I would like a new service to replace what rewrite.py currently does and would be responsible for coordinating the various services involved in thumbnailing (currently Thumbor, Swift and the Mediawiki API). It would basically combine all that URL parsing/translating logic + swift sharding currently found in rewrite.py and thumbor, keeping Thumbor and Swift dumb. Thumbor would only care about returning a thumbnail, not where it gets stored. And Swift would only care about writing and reading content and Swift locations, without the need to rewrite URLs and proxy requests itself. This doesn't solve the Varnish side of things, though. If you want Varnish to support two URL schemes pointing to the same Varnish entry, there's no escaping writing some VCL or a vmod.
+
+Now, regarding the current plan of this task. It seems to me like the goal is to simplify what's currently available, with no plan to add new features, since the ""limited choice"" property ensure that a new URL scheme would be as efficient cache-wise as the old one. The deployment plan, if the Varnish side of things can be done, looks ok. But what I dislike about this plan is that it's not a migration plan. You're basically solving your own problem and leaving a considerable technical debt project on mediawiki's doorstep for someone to be determined to care about. I.e. it will be some future person's job to migrate mediawiki, its extensions, etc. to use the new URL scheme. Creating that much technical debt without an owner shouldn't be allowed. I would support this plan if it was a full migration one and the project included upgrading mediawiki's built-in URL scheme to a cleaner, more extensible one.
+
+Furthermore, the value of a migration aiming for 1-to-1 mapping between two URL schemes is questionable. It's a lot of work, potentially a dual URL scheme for the foreseeable future due to the lack of plan to get rid of the old one, a new service to support. What do we get out of it that's new? A few minutes of developer time saved figuring out the existing URL scheme? These URLs will be consumed by programs that don't care about their beauty.
+
+Re-reading the older parts of the task description mentioning imageinfo, you don't need to call imageinfo to generate a thumbnail URL. It's just a convenience to have it made for you and to have the fallback to the original when a width that's too large is requested. The newly proposed URL scheme doesn't solve that. You still can't know the dimensions of the original in advance if you only have the filename and you are susceptible to requesting a size that can't be rendered. Just like you would be if you constructed a thumbnail URL manually without using imageinfo.",1478539394,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2767815, @Gilles wrote:
+> These issues have been decoupled. Thumbor is currently set to be a drop-in replacement for image scalers in Wikimedia production for public wikis. No functional, thumbnail URI change, etc. set to happen with Thumbor's initial deployment. ""Just"" switching from an open-source piece of stack to another, so to speak.
+
+Projects which can get away with being Wikimedia-only (such as the mobile apps) could just use the Thumbor API directly, though. That seems like a much less ambitious project than replacing the MediaWiki thumb API.",1478293629,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+We could clearly allow arbitrary limits on width, height, or both. However, if we did this with different URLs, then this would fragment caches. Avoiding cache fragmentation is one of the explicit goals for this API.
+
+The API strawman still supports limiting on either of those dimensions, provided that the original image's dimensions (or exact aspect ratio) are available to the client. This information is fairly easy to provide, and is in fact already provided in MediaWiki HTML for the benefit of the media viewer (see `data-file-{width,height}`).
+
+Additionally, knowledge of original image dimensions enables the client to pre-calculate the exact thumb dimensions, which is important to avoid content jumping around during HTML rendering.
+
+I added this explicitly in the strawman description. @gilles, thanks for bringing this up, it's a very good point!",1478279253,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+We could clearly allow arbitrary limits on width, height, or both. However, if we did this with different URLs, then this would fragment caches. Avoiding cache fragmentation is one of the explicit goals for this API.
+
+The API strawman still supports limiting on either of those dimensions, provided that the original image's dimensions (or exact aspect ratio) are available to the client. This is information is easy to provide, and is in fact already provided in MediaWiki HTML for the benefit of the media viewer (see `data-file-{width,height}`).
+
+Additionally, knowledge of original image dimensions enables the client to pre-calculate the exact thumb dimensions, which is important to avoid content jumping around during HTML rendering.
+
+I added this explicitly in the strawman description. @gilles, thanks for bringing this up, it's a very good point!",1478279204,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+We could clearly allow arbitrary limits on width, height, or both. However, if we did this with different URLs, then this would fragment caches. Avoiding cache fragmentation is one of the explicit goals for this API.
+
+The API strawman still supports limiting on either of those dimensions, provided that the original image's dimensions (or exact aspect ratio) are available to the client. This is information is easy to provide, and is in fact already provided in MediaWiki HTML for the benefit of the media viewer (see `data-file-{width,height}`).
+
+Additionally, knowledge of original image dimensions enables the client to pre-calculate the exact thumb dimensions, which is important to avoid content jumping around during HTML rendering.",1478279106,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+We could clearly allow arbitrary limits on width, height, or both. However, this would fragment caches, and avoiding cache fragmentation is one of the explicit goals for this API.
+
+The API strawman still supports limiting on either of those dimensions, provided that the original image's dimensions (or exact aspect ratio) are available to the client. This is information is easy to provide, and is in fact already provided in MediaWiki HTML for the benefit of the media viewer (see `data-file-{width,height}`).",1478278167,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format. The current examples perpetuate the idea of implied width-constraining always being present.
+
+In a way, the square example is a special case of defining both height and width constraints.
+
+This is the sort of thing that might be more obvious by looking at other thumbnail URI schemes for inspiration, such as Thumbor's (probably a good idea to look at that considering it will be backing it) or IIIF. Thumbor in particular offers some features that will likely be the first requested additions to be publicly exposed, like smart cropping.
+
+In we only consider existing features for the design of the new URI scheme, we risk reproducing the same mistaking of not planning enough for the future and ending up with something awkward-looking for the sake of backwards compatibility.
+
+I've been considering as a follow-up project to the Thumbor deployment extracting Swift's rewrite.py into its own service to facilitate URI rewriting and Swift/Thumbor coordination. It would be the natural place to live for code to handle a new URI scheme such as what is proposed here. I.e. a service that would sit between varnish and swift/thumbor/mediawiki/whatever comes next.",1478170986,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"In the current examples, I think it's unfortunate that height-constraining isn't considered. Not as a feature that would be available immediately, but as something to take into account in the proposed URI format.
+
+In a way, the square example is a special case of defining both height and width constraints.
+
+This is the sort of thing that might be more obvious by looking at other thumbnail URI schemes for inspiration, such as Thumbor's (probably a good idea to look at that considering it will be backing it) or IIIF. Thumbor in particular offers some features that will likely be the first requested additions to be publicly exposed, like smart cropping.
+
+In we only consider existing features for the design of the new URI scheme, we risk reproducing the same mistaking of not planning enough for the future and ending up with something awkward-looking for the sake of backwards compatibility.
+
+I've been considering as a follow-up project to the Thumbor deployment extracting Swift's rewrite.py into its own service to facilitate URI rewriting and Swift/Thumbor coordination. It would be the natural place to live for code to handle a new URI scheme such as what is proposed here. I.e. a service that would sit between varnish and swift/thumbor/mediawiki/whatever comes next.",1478170945,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2762226, @bearND wrote:
+> In addition to that I'd like to know what the relationship between this task and the Thumbor project is. I don't see it tagged here.
+
+These issues have been decoupled. Thumbor is currently set to be a drop-in replacement for image scalers in Wikimedia production for public wikis. No functional, thumbnail URI change, etc. set to happen with Thumbor's initial deployment. ""Just"" switching from an open-source piece of stack to another, so to speak.",1478169489,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2762226, @bearND wrote:
+> In addition to that I'd like to know what the relationship between this task and the Thumbor project is. I don't see it tagged here.
+
+These issues have been decoupled. Thumbor is currently set to be a drop-in replacement for image scalers in Wikimedia production for public wikis. No functional, thumbnail URI change, etc. set to happen with Thumbor's initial deployment.",1478169274,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I have refactored this RFC to focus on the public thumb API, and moved content hash based thumb naming to a sub-task.
+
+We would like to tackle the public thumb API first, and expect to be able to move to content hash based thumb naming transparently at a later point.",1478121246,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,In addition to that I'd like to know what the relationship between this task and the Thumbor project is. I don't see it tagged here.,1478059605,PHID-USER-tjyfydvd4ncrfvvr6mkr,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We are continuing to bump into the basic issue of letting clients select thumb sizes, so would really like to start tackling that part of the problem soon.
+
+@brion, has there been any movement on this during the off-site?",1478033714,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@GWicke Yes, I think we should revive it as part of a concerted effort between Editing/Parsing and Reading to improve image & multimedia handling. In particular we need to sync up parameter handling between the classic parser, parsoid, and things that use that output and then do other things (like media viewer widget) that want to be able to manipulate media parameters with fewer API roundtrips...
+
+This'll go easier if I can get another engineer or two on board, we'll see. :) But I think the priority should be raising soon. (Editing dept offsite is next week, I will be lobbying people with specific ideas. ;)",1476228988,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion, this task looks pretty stalled by now. Do you see a chance for reviving it any time soon?",1476225458,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Discussed in {E148}.  Releve
+
+3:00 PM <wm-labs-meetbot`> Minutes:        https://tools.wmflabs.org/meetbot/wikimedia-office/2016/wikimedia-office.2016-03-16-21.00.html
+3:00 PM <wm-labs-meetbot`> Minutes (text): https://tools.wmflabs.org/meetbot/wikimedia-office/2016/wikimedia-office.2016-03-16-21.00.txt
+3:00 PM <wm-labs-meetbot`> Minutes (wiki): https://tools.wmflabs.org/meetbot/wikimedia-office/2016/wikimedia-office.2016-03-16-21.00.wiki
+3:00 PM <wm-labs-meetbot`> Log:            https://tools.wmflabs.org/meetbot/wikimedia-office/2016/wikimedia-office.2016-03-16-21.00.log.html
+
+  * topic discussed: where we add extra parameters (page, time,
+    language, etc) is the format sufficiently clearly specified?
+    (robla, 21:04:13)
+  * to discuss in future: implementation details for small/large
+    installs (backlog)  (brion, 21:05:47)
+  * avoiding cache fragmentation will require normalization of
+    parameters (deterministic serialization of hashmap or other
+    ordering)  (brion, 21:19:50)
+  * daniel suggests having the failed-validation case be a redirect,
+    gwicke warns they're expensive  (brion, 21:20:24)
+  * normalizing parameters within varnish would be painful  (brion,
+    21:20:43)
+
+Log from this portion:
+{P2778}",1458167610,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"I have updated the task description to more clearly separate out use cases and requirements, especially for the API portion.",1458158302,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What problem would such a VCL rule solve?
+
+We need both a good long-term API design, as well as a migration strategy that lets us gradually move towards an API without throwing away existing caches. Such a VCL rule could potentially help with the migration.
+
+I think we should first try to work out the requirements and at least a solid outline of a longer-term solution. While the migration path is important, it should not be the single concern dictating the design of the final API.",1458155783,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2114121, @GWicke wrote:
+> This depends on how much information is available in the opaque id. For example, we could consider using the current thumb URL as the ID until we introduce hashes, which would leave the VCL to fill in the width parameter (if supplied). Format selection support could then be added at a later stage.
+
+That seems somewhat pointless, given that the current thump URL is already an API capable of interpreting itself. What problem would such a VCL rule solve?",1457754010,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Also, a 100% compatible VCL-layer mapping of nice URLs to old URL is just not gonna happen. For example the URL to a full-sized JPEG thumbnail is different depending on whether the JPEG has an EXIF rotation.
+
+This depends on how much information is available in the opaque id. For example, we could consider using the current thumb URL as the ID until we introduce hashes, which would leave the VCL to fill in the width parameter (if supplied). Format selection support could then be added at a later stage.
+
+It is also good to remember that the reason for doing this in VCL is performance for the common case. If there is a small percentage of requests that requires more complex rewriting during a transition period, then falling through to a backend service for those can be okay.",1457751314,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What data is fetched and used before knowing what thumbnail to request?
+
+Normally, no separate request should be needed beyond the original HTML or API request referencing the image:
+
+- In a page, data attributes already indicate original dimensions.
+- In API end points such as summary, relatedpages or imageinfo itself, we will provide at least:
+  - the base thumb path
+  - the original dimensions
+
+Combined knowledge of a generally supported list of formats / qualities this is sufficient to build up the appropriate thumb URL by:
+
+1) appending the size, and, optionally
+2) appending the preferred format / quality parameter.",1457750558,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2106748, @faidon wrote:
+> This isn't currently possible with the existing tech and without some rearchitecturing, so it's not just a matter of URL rewriting in VCL as has been already proposed. (upload.wikimedia.org traffic is directed directly to Swift, which knows nothing about the possible thumbnail sizes)
+
+Agreed, we'd need to at least change some of the backend logic behind thumb.php and the 404-magic to resolve those edge cases... in which case we might be halfway towards making the existing system not awful without a URL reform ;)
+
+>> Secondary use case: local caching of those images is simplified if the caching properties of those thumbnail URLs are more predictable.
+> 
+> Could you elaborate on that? Are you talking about content-hashed or other versioned URLs that always point to the same version of the image and can be locally cached or do you mean something else by predictable?
+
+Version stability yes; this can be achieved without hash-based IDs by always including a timestamp with the link/reference provided in the web pages/APIs/etc.
+
+>> Tertiary use case: there's a lot of use on mobile of squared-off images in lists/menus, and specially-cropped 'hero' images on articles. Having a cleaner thumb URL API should make it easier to extend it to move more of that cropping to the server-side, simplifying client code and reducing the amount of data transferred over mobile networks by pre-cropping unseen edges before download.
+> 
+> *Nod*, I remember hearing about this use case before. It doesn't seem to have been thought of in the existing strawman proposal so far and I agree that it's definitely something that we should keep in mind when talking about a ""thumb API"".
+
+Yeah this is mostly a 'keep in mind we need to be able to extend whatever API we end up with, cleanly' reminder. The existing parameters stuffed into the thumbnail filenames (such as time point for videos, page for multi-page PDF/TIFF/DjVu, etc) are awkward and hard to parse or generate.
+",1457630165,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105088, @brion wrote:
+> Quick note from IRC regarding the thumb-URL needs for mobile apps/web:
+
+Thanks for this — and judging from the response, I'm glad I asked :)
+
+> The primary use case for mobile apps/web here is loading an appropriately-sized thumbnail of a given image as quickly as possible. Currently this requires either an extra HTTPS round-trip for the 'imageinfo' API, or rewriting the existing thumb URLs on the client and then working around the various edge cases (having to know that .svg thumbnails to .svg.png; handling failure cases when asking for a too-big size, knowing that very long filenames in thumbnail paths are sometimes rewritten to fit a length limit, etc). A cleaner, more consistent URL-based API will allow leaving the formatting and sizing questions to the server end.
+
+This isn't currently possible with the existing tech and without some rearchitecturing, so it's not just a matter of URL rewriting in VCL as has been already proposed. (upload.wikimedia.org traffic is directed directly to Swift, which knows nothing about the possible thumbnail sizes)
+
+> Secondary use case: local caching of those images is simplified if the caching properties of those thumbnail URLs are more predictable.
+
+Could you elaborate on that? Are you talking about content-hashed or other versioned URLs that always point to the same version of the image and can be locally cached or do you mean something else by predictable?
+
+> Tertiary use case: there's a lot of use on mobile of squared-off images in lists/menus, and specially-cropped 'hero' images on articles. Having a cleaner thumb URL API should make it easier to extend it to move more of that cropping to the server-side, simplifying client code and reducing the amount of data transferred over mobile networks by pre-cropping unseen edges before download.
+
+*Nod*, I remember hearing about this use case before. It doesn't seem to have been thought of in the existing strawman proposal so far and I agree that it's definitely something that we should keep in mind when talking about a ""thumb API"".",1457618569,PHID-USER-ktuojnvco4fpzmyhzyaf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2106026, @Gilles wrote:
+> Which means that a default implementation in mediawiki would have no use in production, as it's inefficient to query mediawiki for some translation before trying to hit swift if the thumbnail already exists.
+
+Given that the old format is based on filenames and the new one on content hashes, MediaWiki would have to be queried anyway as there is no way to do that translation without a DB lookup.
+
+Also it's generally best to keep frontend layers simple: forward misses to the MediaWiki API, and have the API set up the appropriate redirect in the frontend. Swift apparently has a [[ https://specs.openstack.org/openstack/swift-specs/specs/in_progress/symlinks.html | symlink API ]], not sure what's the equivalent in Varnish.",1457605085,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2106020, @Gilles wrote:
+> What data is fetched and used before knowing what thumbnail to request?
+* original size (cannot really be helped by the API, indeed)
+* extension (e.g. .svg -> .svg.png) and whether this file type can be scaled beyond the original size (also cannot be helped, and is a global one-time lookup anyway)
+
+Other info that's not required for looking up a thumbnail URL given a thumbnail URL of different size, but is required for looking up a thumbnail URL given a filename:
+* filename hash (can be computed, but that's not the kind of thing you want to require a client to do)
+* per-repo configuration (hash level, URL prefix, initial capital), based on which repo the file is in (which is typically not known by the client)
+* content hash (in the future)
+
+There are some idiosyncrasies which also prevent guessing the thumbnail URL but could be solved within the current system:
+* the full URL, if requesting a size larger than or equal to the original
+* knowing whether a thumbnail or the full URL must be requested when asking for the exact same size as the original (specifically for JPEG files, knowing whether they have an EXIF rotation)
+* name reduction if the filename is longer than `abbrvThreshold`
+",1457603737,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105215, @brion wrote:
+>similar to how not-yet-cached thumbnail URLs are routed through MW's thumb.php and friends the first time.
+
+The thumbnail URLs are passed verbatim to Swift, which does some translation inside a Swift plugin, checks whether it has a copy of the thumbnail, and then hits mediawiki if it doesn't have a copy.
+
+This logic would have to be extracted out of Swift into its own service sitting in front of it, then that service extended for new things. Adding to the existing Swift plugin or to VCL are both undesirable.
+
+Which means that a default implementation in mediawiki would have no use in production, as it's inefficient to query mediawiki for some translation before trying to hit swift if the thumbnail already exists.",1457598921,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105215, @brion wrote:
+>similar to how not-yet-cached thumbnail URLs are routed through MW's thumb.php and friends the first time.
+
+The thumbnail URLs are passed verbatim to Swift, which does some translation inside a Swift plugin, checks whether it has a copy of the thumbnail, and then hits mediawiki if it doesn't have a copy.
+
+This logic would have to be extracted out of Swift into its own service sitting in front of it, then that service extended for new things. Adding to the existing Swift plugin or to VCL are both undesirable.",1457598852,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105088, @brion wrote:
+> Currently this requires either an extra HTTPS round-trip for the 'imageinfo' API
+
+What data is fetched and used before knowing what thumbnail to request? Original width? The API won't solve not knowing the original size. If it's a matter of always getting something back even when the original is smaller than the requested size, that's something that can be fixed now.",1457598485,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2105138, @Tgr wrote:
+> IMO the two main questions here are:
+> # is this going to be supported by MediaWiki or just by some external service (or Varnish hack)?
+
+I think it would have to be supported by MediaWiki core (though as with many things, could be / will be in our usage enhanced by scary services/vasnish hacks). A default implementation could use a PHP endpoint similar to the existing img_auth.php and thumb.php
+
+> # is it going to support all image parameters or just some common subset?
+
+I think it would have to support all parameters that can affect the output image, otherwise you'd need to expose a second URL scheme for the actual generated thumbnails.
+
+> Some considerations:
+> * if we want to support all parameters, that should probably involve a new parameter specification/parsing interface for media handlers as the existing one is quite insane (basically just ""get full thumbnail name, read/write your parameters"" which in practice ends up in walking up the inheritance chain and throwing regexes at the string while trying to take the regexes used by all ancestors into account).
+
+Agreed it's pretty awful at present.
+
+
+>>! In T66214#2105146, @Tgr wrote:
+> Also, a 100% compatible VCL-layer mapping of nice URLs to old URL is just not gonna happen. For example the URL to a full-sized JPEG thumbnail is different depending on whether the JPEG has an EXIF rotation.
+
+I suspect this is another case where an initial mapping has to run through a service with some logic, similar to how not-yet-cached thumbnail URLs are routed through MW's thumb.php and friends the first time. Once the proper source file or internal redirect has been found it should be able to stay cached...
+
+(Might make sense to do the mapping the other way as well; letting accesses of the old URLs map to their new locations.)",1457566769,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Also, a 100% compatible VCL-layer mapping of nice URLs to old URL is just not gonna happen. For example the URL to a full-sized JPEG thumbnail is different depending on whether the JPEG has an EXIF rotation.",1457565227,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"IMO the two main questions here are:
+# is this going to be supported by MediaWiki or just by some external service (or Varnish hack)?
+# is it going to support all image parameters or just some common subset?
+
+Some considerations:
+* if the answer to #1 is no, the answer to #2 will be likewise, as MediaWiki extensions can add new thumbnail URL parameters.
+* if this ends up WMF-only, we will have to support old-style URLs forever in MediaWiki and all tools that want to remain usable outside of WMF wikis - not a happy prospect in my opinion.
+* if we end up not supporting all image parameters, then even WMF-specific tools might end up having to support both formats.
+* if we want to support all parameters, that should probably involve a new parameter specification/parsing interface for media handlers as the existing one is quite insane (basically just ""get full thumbnail name, read/write your parameters"" which in practice ends up in walking up the inheritance chain and throwing regexes at the string while trying to take the regexes used by all ancestors into account).",1457565105,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Quick note from IRC regarding the thumb-URL needs for mobile apps/web:
+
+The primary use case for mobile apps/web here is loading an appropriately-sized thumbnail of a given image as quickly as possible. Currently this requires either an extra HTTPS round-trip for the 'imageinfo' API, or rewriting the existing thumb URLs on the client and then working around the various edge cases (having to know that .svg thumbnails to .svg.png; handling failure cases when asking for a too-big size, knowing that very long filenames in thumbnail paths are sometimes rewritten to fit a length limit, etc). A cleaner, more consistent URL-based API will allow leaving the formatting and sizing questions to the server end.
+
+Secondary use case: local caching of those images is simplified if the caching properties of those thumbnail URLs are more predictable.
+
+Tertiary use case: there's a lot of use on mobile of squared-off images in lists/menus, and specially-cropped 'hero' images on articles. Having a cleaner thumb URL API should make it easier to extend it to move more of that cropping to the server-side, simplifying client code and reducing the amount of data transferred over mobile networks by pre-cropping unseen edges before download.
+",1457564647,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What's the caching strategy for this API? Will it simply redirect/proxy
+
+The most efficient option for introducing a thumb API is to rewrite requests in Varnish to directly map to the existing cached thumbs, thereby avoiding a duplication of cache entries. Given the simple URL structure, this should be relatively straightforward to do.
+
+As with any API design, we need to consider future needs carefully, while also avoiding to get stuck forever by worrying about unknown unknowns. We know that we have a concrete need to let clients select thumb sizes and optionally the quality in a sane and cacheable manner, and this RFC discusses possible solutions. I personally think that the present design is also reasonably future-proof, allowing a future use of content-negotiation for both the size and density if client-side selection doesn't end up dominating.
+
+@Gilles, do you have specific concerns or improvement ideas that you could share?",1457376174,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What's the caching strategy for this API? Will it simply redirect/proxy
+
+The most efficient option for introducing a thumb API is to rewrite requests in Varnish to directly map to the existing cached thumbs, thereby avoiding a duplication of cache entries. Given the simple URL structure, this is relatively straightforward to do.
+
+As with any API design, we need to consider future needs carefully, while also avoiding to get stuck forever by worrying about unknown unknowns. We know that we have a concrete need to let clients select thumb sizes and optionally the quality in a sane and cacheable manner, and this RFC discusses possible solutions. I personally think that the present design is also reasonably future-proof, allowing a future use of content-negotiation for both the size and density if client-side selection doesn't end up dominating.
+
+@Gilles, do you have specific concerns or improvement ideas that you could share?",1457376040,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What's the caching strategy for this API? Will it simply redirect/proxy
+
+The most efficient option for introducing a thumb API is to rewrite requests in Varnish to directly map to the existing cached thumbs, thereby avoiding a duplication of cache entries. Given the simple URL structure, this is relatively straightforward to do.
+
+As with any API design, we need to consider future needs carefully, while also avoiding to get stuck forever by worrying about unknown unknowns. We know that we have a concrete need to let clients select thumb sizes and optionally the quality in a sane and cacheable manner, and this RFC discusses possible solutions. I personally think that the present design is also reasonably future-proof, allowing a future use of content-negotiation for both the size and density if client-side selection doesn't end up dominating.
+
+@Gilles, do you have specific proposals for improving the API strawman?",1457375684,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"What's the caching strategy for this API? Will it simply redirect/proxy to the canonical thumbnail URL we already have? Or will it do caching of its own, essentially doubling the caching capacity requirements for thumbnails?
+
+What can a REST API for thumbnails do that HTTP and a URL scheme can't? In fact calling it REST API is a stretch, since we're only talking about GETs here. It's just a different URL scheme.
+
+This seems to me like a cleanup without a plan to address existing usage. There isn't much insight into how this should evolve with upcoming known technologies like client hints, let alone unforeseen needs. The reason why our current thumbnail URL scheme looks weird is because it was developed incrementally with no vision about future needs. Every time a new need appeared, some kind of parameter was added. And backward compatibility could never be broken, because our images are hotlinked. The approach here seems no different, in fact the only examples provided don't even address the existing options, only a small subset of features. If you only care about id, size and quality/format the existing URL scheme isn't that awkward to use.
+
+Explicit versioning looks nicer at a glance, but you run into the same problem of old version support and how it relates to client-side and server-side caching. And without a strategy for priming/migrating the caches for new formats, each version update would be extremely costly to deploy.
+
+I'm all for a comprehensive plan to rethink our thumbnail URL scheme, including all existing options, planning for future needs as well as addressing the issue of migration (considering that existing URLs will have to redirect to new ones forever). But I'm not seeing anything like that here, just an eagerness to create a new endpoint that's more to your liking and does less than the status quo, without careful consideration for operational consequences and homework required to do this right. As-is, this would be creating instant technical debt.
+
+I'll be at the meeting, but it'd be nice to have a draft spec to look at that addresses these issues by then.",1457356851,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We plan to discuss this in {E147}.  Based on the [2016-03-02 ArchCom meeting](https://www.mediawiki.org/wiki/Architecture_committee/2016-03-02) and what he said in T66214#2087161, I believe @GWicke hopes we can reach consensus on the format of a thumb API, possibly putting that aspect into last call.",1457323948,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> Do you think we should do them in a particular order?
+
+From a user and API design perspective, I think the public thumb API is more urgent. It is also relatively easy to implement in a way that maps to our existing thumb caching & storage systems.
+
+Moving to content hashes will require more serious backend work, as well as a translation layer. @Gilles and @aaron are working on this, but my understanding is that content hashes are still some ways out.
+
+So, my proposal is to tackle the API first, and then move to hashes in a second step.",1457053254,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#2087098, @GWicke wrote:
+> This task is really discussing two separate issues, which can be tackled in separate phases:
+> 
+> 1) Define a thumb API, which lets clients easily select thumb size and quality. Define the image identifier as an opaque string. Examples: `/thumb/{id}/{size}{/quality_format}`, value `/thumb/Wiki.png/640`.
+> 
+> 2) Switch from name-based identifiers to hash + selector based IDs. Example value: `/thumb/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/640`.
+
+Do you think we should do them in a particular order?",1457052610,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"This task is really discussing two separate issues, which can be tackled in separate phases:
+
+1) Define a thumb API, which lets clients easily select thumb size and quality. Define the image identifier as an opaque string. Examples: `/thumb/{id}/{size}{/quality_format}`, value `/thumb/Wiki.png/640`.
+
+2) Switch from name-based identifiers to hash + selector based IDs. Example value: `/thumb/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12/640`.",1457052304,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Per T125865 and the [2016-02-10 ArchCom meeting](https://www.mediawiki.org/wiki/Architecture_committee/2016-02-10), I'm assigning this to @brion",1455241975,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@GWicke: how would you like to move forward on this?  This seems like a natural candidate for you to be the shepherd on per T125865, no?",1454988544,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The lack of a stable / simple thumb API is a serious issue for cacheable REST end points that contain a reference to a thumbnail, such as [the page summary end point](https://en.wikipedia.org/api/rest_v1/?doc#!/Page_content/get_page_summary_title), and an upcoming ""related pages"" end point.
+
+We (#services) would like to make progress on the API portion along the lines of the task summary soon, and are willing to implement this in a way that maps to existing thumbnail backends. If there are no objections I am going to push for this RFC to be discussed soon.",1454356431,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Tgr, less sophisticated clients shouldn't need to select more than size and quality in any case, which both are easy enough to get right.",1450375965,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The new thumbnail api, at least on Wikimedia, needs to support one more parameter (`qlow`), as I've found in T119797#1839787, which complicates things, unless we discard it in favor of something else, like a dedicated domain, a different entry point, etc
+
+>>! In T119797#1839787, @tstarling wrote:
+> JPEG thumbnails already support a quality parameter ""qlow"", which was added to support zero, for example with Arcimboldo_Librarian_Stokholm.jpg:
+> 
+> * [[https://upload.wikimedia.org/wikipedia/commons/thumb/7/76/Arcimboldo_Librarian_Stokholm.jpg/200px-Arcimboldo_Librarian_Stokholm.jpg|200px standard quality: 14,618 bytes]]
+> * [[https://upload.wikimedia.org/wikipedia/commons/thumb/7/76/Arcimboldo_Librarian_Stokholm.jpg/qlow-200px-Arcimboldo_Librarian_Stokholm.jpg|200px low quality: 6,080 bytes]]
+
+",1450296093,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"The new thumbnail api, at least on Wikimedia, needs to support one more parameter (`qlow`), as I've found in T119797#1839787, which complicates things, unless we discard it in favor of something else, a dedicated domain
+
+>>! In T119797#1839787, @tstarling wrote:
+> JPEG thumbnails already support a quality parameter ""qlow"", which was added to support zero, for example with Arcimboldo_Librarian_Stokholm.jpg:
+> 
+> * [[https://upload.wikimedia.org/wikipedia/commons/thumb/7/76/Arcimboldo_Librarian_Stokholm.jpg/200px-Arcimboldo_Librarian_Stokholm.jpg|200px standard quality: 14,618 bytes]]
+> * [[https://upload.wikimedia.org/wikipedia/commons/thumb/7/76/Arcimboldo_Librarian_Stokholm.jpg/qlow-200px-Arcimboldo_Librarian_Stokholm.jpg|200px low quality: 6,080 bytes]]
+
+",1450296048,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,I don't think there is much overlap between the people who use broken clients and those for whom performance matters to such an extent that an extra redirect becomes problematic.,1449967165,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> redirects are expensive
+
+Much more expensive is terminating once-valid URLs. Still looking for an answer to:
+
+>>! In T66214#1855231, @Nemo_bis wrote:
+> Yes, but content of an image can vary and so will the hash-based URL. Will every single hash-based URL keep working forever?
+
+To the benefit of the mass of MediaWiki users it would also be nice to explicitly know whether this feature will cater to:
+* wikis running on Windows, which naturally have issues with filenames (T3780, already in blocked tasks);
+* wikis for which it's too hard to set up a thumb handler with the current mechanism  (https://www.mediawiki.org/wiki/Manual:Thumb.php), ideally by making thumbnails fully work in vanilla MediaWiki (cf. {T58926}, {T27958}, {T67220}; things got better now with {T114098}).",1449916816,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Anomie, redirects are expensive, and are easy to overlook by broken clients. Failing fast & loudly makes sure that broken clients are fixed quickly, rather than creating a hidden performance regression. The number of advanced clients with a need to manipulate `hash_spec` should be very small in any case.",1449877971,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1867845, @GWicke wrote:
+> Requests with `hash_spec`s not conforming to this would be rejected as invalid by the API.
+
+That doesn't seem particularly user-friendly. Any reason not to 301 redirect to the canonical ordering instead of a 500?",1449758701,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients want to select the size and image quality, so we should make it extra easy to do so. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order and syntax. Requests with `hash_spec`s not conforming to this would be rejected as invalid by the API.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+Pages are already re-parsed when images referenced in them are re-uploaded. This is to make sure that image dimensions and other metadata is correct.
+
+> Why do you only want to support square bounding boxes?
+
+Of all the fixed bounding boxes, the square one has the advantage of offering reasonably-sized images independent of aspect ratio. It is also the typical choice in other APIs such as [flickrs](https://www.flickr.com/services/api/misc.urls.html).
+
+As mentioned earlier, most clients have access to the original image dimensions from an API response, or the data attributes in HTML. This means that they can select arbitrary image sizes for their application with some simple math, independent of the bounding box scheme used.",1449711267,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients want to select the size and image quality, so we should make it extra easy to do so. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order and syntax. Requests with `hash_spec`s not conforming to this would be rejected as invalid by the API.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+Pages are already re-parsed if images referenced in them are re-uploaded. This is to make sure that image dimensions and other metadata is correct.
+
+> Why do you only want to support square bounding boxes?
+
+Of all the fixed bounding boxes, the square one has the advantage of offering reasonably-sized images independent of aspect ratio. It is also the typical choice in other APIs such as [flickrs](https://www.flickr.com/services/api/misc.urls.html).
+
+As mentioned earlier, most clients have access to the original image dimensions from an API response, or the data attributes in HTML. This means that they can select arbitrary image sizes for their application with some simple math, independent of the bounding box scheme used.",1449711222,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients only care about the size and image quality, so we should make it easy to change that. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order and syntax. Requests with `hash_spec`s not conforming to this would be rejected as invalid by the API.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+Pages are already re-parsed if images referenced in them are re-uploaded. This is to make sure that image dimensions and other metadata is correct.
+
+> Why do you only want to support square bounding boxes?
+
+Of all the fixed bounding boxes, the square one has the advantage of offering reasonably-sized images independent of aspect ratio. It is also the typical choice in other APIs such as [flickrs](https://www.flickr.com/services/api/misc.urls.html).
+
+As mentioned earlier, most clients have access to the original image dimensions from an API response, or the data attributes in HTML. This means that they can select arbitrary image sizes for their application with some simple math, independent of the bounding box scheme used.",1449706667,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients only care about the size and image quality, so we should make it easy to change that. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order (like alphabetically). Other orders need to be rejected as invalid.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+Pages are already re-parsed if images referenced in them are re-uploaded. This is to make sure that image dimensions and other metadata is correct.",1449706043,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients only care about the size and image quality, so we should make it easy to change that. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order (like alphabetically). Other orders need to be rejected as invalid.
+
+> To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version.
+
+This is already the case, as aspect ratios often change on re-upload.",1449705994,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"> What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+@Anomie, most clients only care about the size and image quality, so we should make it easy to change that. The `hash_spec` with options like time selection on the other hand needs to follow very strict rules to be deterministic, and will generally be supplied by the server / API. If there are multiple parameters, they will need to be specified in a deterministic order (like alphabetically). Other orders need to be rejected as invalid.",1449705910,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@jhobs, @yurik: another one that may interact with https://github.com/wikimedia/mediawiki-extensions-ZeroBanner/blob/e21286bf61f454a106cea5b9c728247ae2dbbc0c/includes/PageRendering.php#L1104.
+
+Reading apps and web crew: this is probably for tracking, but it's worth tracking in case there are any assumptions (e.g., regexes) about URL format for media.
+
+This is a tentative Q3 goal per https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q3_Goals#Performance.",1449622217,PHID-USER-srhlj2447vmpmrfhqnfa,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1862573, @Anomie wrote:
+> Why do you only want to support //square// bounding boxes? It doesn't seem particularly unlikely that a client has a rectangular bounding box to fill. If you only support square boxes, the client has to separately query the image's dimensions to decide what square bounding box to supply to the thumbnailer.
+
+I guess the client can get the dimensions when it requests the sha of the image. I mean, any particular client would already need to query the api to get the sha of the image to use it in the thumb URL",1449598035,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1854415, @GWicke wrote:
+> Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.
+
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;p=22/500`: 500px thumb of page 22 in a multi-page document.
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;t=2m30s/220`: Thumb of a video at 2m30s.
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;lang=fr/220`: Thumb of an SVG, rendered to a PNG using French texts.
+
+What if you have a format that supports both animation/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+>>! In T66214#1855231, @Nemo_bis wrote:
+>>>! In T66214#1854334, @ori wrote:
+>>>>! In T66214#1854329, @Nemo_bis wrote:
+>>> How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.
+>> 
+>> There would be a mapping of old URLs to content-based URLs, which we'd just keep around forever.
+> 
+> Yes, but content of an image can vary and so will the hash-based URL. Will every single hash-based URL keep working forever?
+
+It appears that the hash-based URL would always be a permalink to the version of the image at the time. To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version. In other words, it would be the equivalent of all page links including ""?oldid=12345"".
+
+>>! In T66214#1856662, @GWicke wrote:
+> @ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail.
+
+OTOH, that doesn't mean that two different URLs cannot have the same content if the semantic intent of the thumbnail differs. For example, if a video is at 1 frame per second, t=1s and t=1.5s are semantically different but in practice identical.
+
+BTW, I note in your proposed scheme, it's either easily possible to specify `t=2m30s` and `t=150s`, or else it stupidly throws an error for the latter, or else it 301 redirects one to the other and you forgot to mention that.
+
+> The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+Why do you only want to support //square// bounding boxes? It doesn't seem particularly unlikely that a client has a rectangular bounding box to fill. If you only support square boxes, the client has to separately query the image's dimensions to decide what square bounding box to supply to the thumbnailer.
+
+If you really want one canonical URL and are willing to expend network round-trips to achieve it, the thumbnailer could easily enough redirect `size=200`, `size=200x300`, and `size=266x150` to the canonical `size=200x150` for a 1024×768 image.
+
+> I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351.
+
+I note that that change was actually tried and then reverted, and T351#1649303 has some analysis proposing more flexibility for that feature.",1449595454,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1854415, @GWicke wrote:
+> Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.
+
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;p=22/500`: 500px thumb of page 22 in a multi-page document.
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;t=2m30s/220`: Thumb of a video at 2m30s.
+> * `/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12;lang=fr/220`: Thumb of an SVG, rendered to a PNG using French texts.
+
+What if you have a format that supports both animated/pagination and i18n (e.g. an animated SVG or a multi-language PDF)? At that point, why have the size as ""/200"" instead of "";size=200""?
+
+>>! In T66214#1855231, @Nemo_bis wrote:
+>>>! In T66214#1854334, @ori wrote:
+>>>>! In T66214#1854329, @Nemo_bis wrote:
+>>> How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.
+>> 
+>> There would be a mapping of old URLs to content-based URLs, which we'd just keep around forever.
+> 
+> Yes, but content of an image can vary and so will the hash-based URL. Will every single hash-based URL keep working forever?
+
+It appears that the hash-based URL would always be a permalink to the version of the image at the time. To use a newly-uploaded version of an image, the page would have to be reparsed to reference the hash of the newly-uploaded version. In other words, it would be the equivalent of all page links including ""?oldid=12345"".
+
+>>! In T66214#1856662, @GWicke wrote:
+> @ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail.
+
+OTOH, that doesn't mean that two different URLs cannot have the same content if the semantic intent of the thumbnail differs. For example, if a video is at 1 frame per second, t=1s and t=1.5s are semantically different but in practice identical.
+
+BTW, I note in your proposed scheme, it's either easily possible to specify `t=2m30s` and `t=150s`, or else it stupidly throws an error for the latter, or else it 301 redirects one to the other and you forgot to mention that.
+
+> The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+Why do you only want to support //square// bounding boxes? It doesn't seem particularly unlikely that a client has a rectangular bounding box to fill. If you only support square boxes, the client has to separately query the image's dimensions to decide what square bounding box to supply to the thumbnailer.
+
+If you really want one canonical URL and are willing to expend network round-trips to achieve it, the thumbnailer could easily enough redirect `size=200`, `size=200x300`, and `size=266x150` to the canonical `size=200x150` for a 1024×768 image.
+
+> I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351.
+
+I note that that change was actually tried and then reverted, and T351#1649303 has some analysis proposing more flexibility for that feature.",1449594481,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Thanks @GWicke for your thorough explanation. I was wondering why not pick the same semantics as wikitext, but it makes sense to use bounding box dimensions for the api.",1449433773,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leave the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the growing popularity of the 16:9 aspect ratio, as thumbs for 16:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limit shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussed here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449434560,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leave the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the growing popularity of the 16:9 aspect ratio, as thumbs for 16:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limits shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussed here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449434527,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leave the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the 16:9 aspect ratio, as thumbs for 19:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limits shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussed here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449434388,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leaves the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the 16:9 aspect ratio, as thumbs for 19:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limits shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the earlier discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussed here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449427223,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@ciencia_al_poder: An issue with offering different ways to constrain image dimensions is cache dilution. Ideally, there should be only a single URL for each thumbnail. This doesn't mean that a client can't constrain image sizes in other ways; it merely means that it might need to do some simple math to construct the URL for the size it wants.
+
+If we accept this premise, we are left with the question of which constraint to pick. Our current thumb API URLs only restrict the width of the image, and leaves the height unlimited. The alternative proposed here is to specify a bounding box, limiting both width and height at the same time.
+
+For the most common use cases, both tend to work equally well. Doubling the size / resolution of a referenced thumb can be achieved by multiplying the size parameter from the original URL in either case. Clients with knowledge of original dimensions or aspect ratio (provided in data attributes) can request any thumb size in any of the two schemes by doing some simple math. 
+
+The main differences in behavior only affect clients without knowledge of original dimensions, which are relatively rare:
+
+The bounding box approach shines for grid layouts. More generally, clients without knowledge of the original dimensions / aspect ratio can request a reasonably-sized thumb easily with the bounding box. This has become more important with the 16:9 aspect ratio, as thumbs for 19:9 portrait images end up being over 3x larger (by pixel count) than landscape ones if only the width is constrained.
+
+The width limits shines for formatting thumbs of equal width in a column. Clients can request a thumb fitting the column width without knowing the image dimensions / aspect ratio, but can end up with some very tall images, as there are no limits on the height. Since most column layouts are specified in wikitext content & original dimensions are available in that case, it is unclear to me whether any clients actually benefit from this ability in practice.
+
+Personally, I think that the avoidance of surprises gives the bounding box variant a slight but significant edge.
+
+I should also mention the discussion about changing wikitext thumb semantics to use square bounding boxes in T351. The API design discussion here is mostly independent of the semantics of wikitext syntax, but some similar considerations were surfaced there.",1449427104,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"this would effectively make 2 identical files with different name to get the same URL in this scenario. That's pretty good.
+
+As for the size parameter, it's the width of the bounding box (with variable height depending on the dimensions of the image) or just a maximum width and height?. I'd expect the first, since that will provide room for, at a later date, extend it to specify height only (`/x150`) or maximum width and height (`/200x150`), following the current thumbnail syntax in wikitext.",1449316697,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1854334, @ori wrote:
+>>>! In T66214#1854329, @Nemo_bis wrote:
+>> How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.
+> 
+> There would be a mapping of old URLs to content-based URLs, which we'd just keep around forever.
+
+Yes, but content of an image can vary and so will the hash-based URL. Will every single hash-based URL keep working forever?",1449306683,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449273780,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion (especially T66214#1743371), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449273721,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449273684,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion (especially T66214#1743938), @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449273650,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Based on the earlier discussion with @brion, @BGerstle-WMF, @Tgr and others, I extended the task description with a section describing a possible stable thumb API layout that lets clients dynamically select thumb size and format/quality.",1449272794,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,">>! In T66214#1854329, @Nemo_bis wrote:
+> How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.
+
+There would be a mapping of old URLs to content-based URLs, which we'd just keep around forever.",1449271319,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"How would permalinks work in such a scenario? It's very important for URLs to keep functioning forever, unless the file (or file revision) is deleted.",1449271147,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"This doesn't really **block** T89971, but if the sort of thing being discussed here happens then one of the more nebulous bits of that (fixing iiurlwidth/iiurlheight/iiurlparam into something multi-valued but still sane) would just go away since we could just point to the ""/api/rest_v1/media/img/{original-sha1}"" bit and let the client fill in the width/height/page/seek-time/language/etc. when it talks to that endpoint.
+
+But that, of course, depends on (1) someone actually working on this any time soon and (2) the end result actually existing for all MediaWiki installations and not just as an optional bespoke service like too many things seem to be planned as these days.",1448997067,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,,1447900314,PHID-USER-tjyfydvd4ncrfvvr6mkr,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,,1447899356,PHID-USER-tjyfydvd4ncrfvvr6mkr,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,T117082 is an example for how better support for client-side thumb size selection would simplify the API design for end points like page previews.,1447088584,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Imageinfo responses are perfectly cacheable (apart from invalidation when the file changes, but that's a generic problem with the action API (or, rather, with varnish) and not easy to solve). That said, they are a distraction. Most of the time, clients want the image, not information about the image. IIRC when we were writing MediaViewer, using the API to fetch image URLs would have been a 200ms delay for the median user. I'm sure it's much less after the HHVM switch but even cutting down a few dozen ms is a win.",1446621369,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We recently considered making imageinfo responses cacheable in T116840, but in a subsequent discussion @tstarling made good points about the current response & associated APIs not facilitating client-side decisions on dimensions, format or quality. There are a lot of irregularities around multi-page images, vector and video formats etc that are currently left to the client to figure out, and all this is ignoring that our thumb urls are not considered a public API.
+
+To address the need for more client-side control over thumb parameters, as well as improved caching of image metadata responses, it seems that we'll need to address the thumb URL as API question raised in the discussion on this task. The move to content-based addressing seems to provide a good opportunity to do this.",1446599988,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion: In your distinction, the 'author-supplied' parameters are all closely related to selecting the base image for a thumb. I wonder if we could leverage a syntax similar to section identifiers for this:
+
+- `p=20` for page selection
+- `t=20` for time offset selection (following the HTML5 temporal fragment standard)
+- `lang=en` for the language
+
+Example URL, using `;` as delimiter: `/api/rest_v1/media/img/90edff310ba1420a7b6e2e5f49a0820c96450a35;t=20/{size}`
+
+Instead of using the width, we could also consider interpreting the size parameter as a square bounding box. This would be more useful for preview applications where the image has to fit in a limited space, and would still support retrieval of exact widths / heights if the client has information about the original dimension and thus the aspect ratio. This is for example true for Parsoid HTML, which provides the original dimensions in data attributes.
+ 
+> With sizes we also have the question of whether to again support every size under the sun or specific size steps. 
+
+We have discussed limiting thumb sizes a couple of times before, without a clear consensus. I don't think that this is necessarily an issue for the API, though. If we determine that client-side re-scaling quality is acceptable, we can start to return approximate (rounded) thumbs in response to requests for odd numbers later.
+
+> Video derivatives are produced at specific size steps... but per video convention, based on a max height, not a specific width. If this is an API, then either we need to accept any input parameter and return a sensible file, or clients have to know what the acceptable set of sizes they can specify is.
+
+I think it makes sense to focus on the thumb use case first, as the considerations for video are quite different. For example, we might want to move to manifest files for adaptive streaming with MPEG-DASH (see T44591), which could again be stored using the original video file's hash.",1445555854,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion: In your distinction, the 'author-supplied' parameters are all closely related to selecting the base image for a thumb. I wonder if we could leverage a syntax similar to section identifiers for this:
+
+- `p=20` for page selection
+- `t=20` for time offset selection (following the HTML5 temporal fragment standard)
+- `lang=en` for the language
+
+Example URL, using `;` as delimiter: `/api/rest_v1/media/img/90edff310ba1420a7b6e2e5f49a0820c96450a35;t=20/{size}`
+
+Instead of using the width, we could also consider interpreting the size parameter as a square bounding box. This would be more useful for preview applications where the image has to fit in a limited space, and would still support retrieval of exact widths / heights if the client has information about the original dimension and thus the aspect ratio. This is for example true for Parsoid HTML, which provides the original dimensions in data attributes.
+ 
+> With sizes we also have the question of whether to again support every size under the sun or specific size steps. 
+
+We have discussed limiting thumb sizes a couple of times before, without a clear consensus. I don't think that this is necessarily an issue for the API, though. If we determine that client-side re-scaling quality is acceptable, we can start to return approximate (rounded) thumbs in response to requests for odd numbers later.
+
+> Video derivatives are produced at specific size steps... but per video convention, based on a max height, not a specific width. If this is an API, then either we need to accept any input parameter and return a sensible file, or clients have to know what the acceptable set of sizes they can specify is.
+
+I think it makes sense to focus on the thumb use case first, as the considerations for video are quite different. For example, we might want to move to manifest files for adaptive streaming with MPEG-DASH, which could again be stored using the original video file's hash.",1445555824,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion: In your distinction, the 'author-supplied' parameters are all closely related to selecting the base image for a thumb. I wonder if we could leverage a syntax similar to section identifiers for this:
+
+- `p=20` for page selection
+- `t=20` for time offset selection (following the HTML5 temporal fragment standard)
+- `lang=en` for the language
+
+Example URL, using `;` as delimiter: `/api/rest_v1/media/img/90edff310ba1420a7b6e2e5f49a0820c96450a35;t=20/{size}`
+
+Instead of using the width, we could also consider interpreting the size parameter as a square bounding box. This would be more useful for preview applications where the image has to fit in a limited space, and would still support retrieval of exact widths / heights if the client has information about the original dimension and thus the aspect ratio.
+ 
+> With sizes we also have the question of whether to again support every size under the sun or specific size steps. 
+
+We have discussed limiting thumb sizes a couple of times before, without a clear consensus. I don't think that this is necessarily an issue for the API, though. If we determine that client-side re-scaling quality is acceptable, we can start to return approximate (rounded) thumbs in response to requests for odd numbers later.
+
+> Video derivatives are produced at specific size steps... but per video convention, based on a max height, not a specific width. If this is an API, then either we need to accept any input parameter and return a sensible file, or clients have to know what the acceptable set of sizes they can specify is.
+
+I think it makes sense to focus on the thumb use case first, as the considerations for video are quite different. For example, we might want to move to manifest files for adaptive streaming with MPEG-DASH, which could again be stored using the original video file's hash.",1445555714,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"It probably makes sense to conceptually separate the params into author-supplied and client-selectable portions:
+
+Author-supplied:
+* page (if relevant - PDF/DjVu/TIFF)
+* seek time (if relevant - WebM/Ogg)
+* text rendering language (if relevant - localizable SVGs)
+
+Client-selectable:
+* target size (width and/or height?)
+* output format (potential to override default .png/.jpg output with .webp or other formats in future)
+
+With sizes we also have the question of whether to again support every size under the sun or specific size steps. Video derivatives are produced at specific size steps... but per video convention, based on a max height, not a specific width. If this is an API, then either we need to accept any input parameter and return a sensible file, or clients have to know what the acceptable set of sizes they can specify is.
+
+Ditto with output formats -- if we support only .png for SVG rasterization, but either .png or .jpg (or .png or .jpg or .webp someday?) as options for PDF .... how does the client know which to safely select from?",1445462229,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@brion, that is indeed a long list of optional parameters, and will require some thinking to accommodate in a clean and cacheable API. 
+
+Generally, I think the APIs we are defining for media are public in any case; cached and stored content relies on those APIs being reasonably stable. It's worth using an opportunity like the move to content-addressable media to clean them up.",1445455846,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We know we already have parameters for width (base images), page (SVG, PDF, etc), thumbtime (TimedMediaHandler), and language (SVG). Custom handlers, or additional extensions, could add more.
+
+Additionally we have the format conversions, where we currently add a second extension ('.svg.png', '.djvu.jpg', whatever); we may want to add additional output formats such as .webp.
+
+Further, we have derivative files for TimedMediaHandler -- transcodes to various output formats at various bitrates and resolutions, which are currently stashed in similar infrastructure to the thumbnail images but not in the same place.
+
+So if we're going to make those URLs predictable instead of extensible, we need to at least cover all that territory...?",1445454392,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@GWicke +1, having a RESTful interface for requesting thumbnails would be nice.  Your suggestion, however, assumes prior knowledge of the ""prefix,"" which might not always be at hand.  IMHO, ideally, the interface would only require clients to specify the filename/hash/identifier and (optionally) desired width.  That way clients can:
+
+- Prevent automatic downloads of images—even when offscreen
+- Have more control over image thumbnails that are downloaded, which allows for: 
+  - taking advantage of high-bandwidth, high DPI situations
+  - requesting lower-res thumbnails initially in case the user is on a slow connection
+  - rendering images at the width of the device w/o scaling artifacts",1445454380,PHID-USER-6vqtwycrvuonr2xo7bqi,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format, page, ...), so having the width and other parameters in a deterministic and easy-to-parse / replace location would be useful.
+
+Strawman url for a basic thumb: `/api/rest_v1/media/img/{original-sha1}/{width}`
+
+Edit: Modified strawman URL to clarify that the 'prefix' is a path to a stable API entry point.",1445455175,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format, page, ...), so having the width and other parameters in a deterministic and easy-to-parse / replace location would be useful.
+
+Strawman url: `/api/rest_v1/media/img/{original-sha1}/{width}`
+
+Edit: Modified strawman URL to clarify that the 'prefix' is a path to a stable API entry point.",1445455030,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format), so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/api/rest_v1/media/img/{original-sha1}/{width}`
+
+Edit: Modified strawman URL to clarify that the 'prefix' is a path to a stable API entry point.",1445454498,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format), so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/api/rest_v1/media/img/{original-sha1}/{width}`",1445454464,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb dimensions (and possibly, quality / format), so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/prefix/{original-sha1}/{width}`",1445454383,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure worthy of a public API. Clients might want to rewrite the thumb width, so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/prefix/{original-sha1}/{width}`",1445454095,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure. Clients might want to rewrite the thumb width, so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Strawman url: `/prefix/{original-sha1}/{width}`",1445453909,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"New thumb paths should ideally follow a very regular structure. Clients might want to rewrite the thumb width, so having the width parameter in an easy-to-parse / replace location would be useful.
+
+Example url: `/prefix/{original-sha1}/{width}`",1445453876,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Subfader, in Parsoid HTML [the image name is already provided in an RDFa `resource` attribute](https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images). @Prtksxna is also [working on](https://gerrit.wikimedia.org/r/#/c/196532/) bringing the PHP thumb HTML structure closer to the Parsoid output. We should make sure to include the resource attribute there as well.",1433361426,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Subfader, in Parsoid HTML [the image name is already provided in an RDFa `resource` attribute](https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images). There is also [work by @Prtksxna ongoing](https://gerrit.wikimedia.org/r/#/c/196532/) to bring the PHP thumb HTML structure closer to the Parsoid output. We should make sure to include the resource attribute there as well.",1433361384,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"@Subfader, in Parsoid HTML [the image name is already provided in an RDFa `resource` attribute](https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images). There is also [work ongoing](https://gerrit.wikimedia.org/r/#/c/196532/) to bring the PHP thumb HTML structure closer to the Parsoid output. We should make sure to include the resource attribute there as well.",1433361343,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Some JS scripts in extensions rely on the image name as they grab it from the src-URL to pass it to the API or thumb.php.
+
+So if this comes, please make sure to provide the proper image name in a data parameter at least.
+",1420023336,PHID-USER-qjb2hbe663dhrrpskylp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"Some JS scripts in extensions rely on the image name as they grab it to pass it to the API or thumb.php.
+
+So if this comes, please make sure to provide the proper image name in a data parameter at least.
+",1420023314,PHID-USER-qjb2hbe663dhrrpskylp,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,See also T1210.,1419899961,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"(In reply to Tisza Gergő from comment #1)
+> By content-based thumbnail URL do you mean the URL is based on the content
+> of the thumbnail, or on the content of the original file? 
+
+Definitely the latter. Example: <sha1 of orig>-300.jpg",1398181397,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"(In reply to Bawolff (Brian Wolff) from comment #2)
+> I believe there is already a bug for this, but cant find it.
+
+Bug 44428 comment 0?",1398149823,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"We already have support for content disposition headers on files (for swift backend anyways). I imagine we could still use htcp for quick purging.
+
+There are very definite advantages here related to caching. Among other things, It would also let us set more aggresive cache headers for the client.
+
+File moving would also become much ""better"".
+
+I believe there is already a bug for this, but cant find it.",1398144820,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+Define an official thumb API,"By content-based thumbnail URL do you mean the URL is based on the content of the thumbnail, or on the content of the original file? None of the advantages seem to apply to the former, it makes quick purging even harder, and makes it impossible to guess the URL needed for resizing the image (which can be used for some fairly significant speed improvements).",1398128071,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-llsmiww6l77wds4q4ajz,task_subcomment,NA
+VisualEditor: Don't bind the 'v' accesskey for VisualEditor in namespaces where VE is not enabled,"Visual editor adds accesskey 'v' for visual edit in namespaces where the editor is not enabled. For example (in Firefox) pressing alt+shift+v in [[sv:Diskussion:Stockholm]] shows the error message:
+
+""Error loading data from server: novenamespace: VisualEditor is not enabled in namespace 1. Would you like to retry?""
+
+It should be possible to avoid getting an error message by removing the access key. (Also, if Visual editor is not enabled there is no point in asking users to retry.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1397938920,PHID-USER-axibsactcdotqkfh3mfe,False,PHID-TASK-fe5hswi3ghhljkcsvvmj,task_description,resolved
+VisualEditor: Don't bind the 'v' accesskey for VisualEditor in namespaces where VE is not enabled,"Change 133851 merged by jenkins-bot:
+Remove edit tab from the DOM if it's hidden
+
+https://gerrit.wikimedia.org/r/133851",1400521877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fe5hswi3ghhljkcsvvmj,task_subcomment,NA
+VisualEditor: Don't bind the 'v' accesskey for VisualEditor in namespaces where VE is not enabled,"Change 133851 had a related patch set uploaded by Alex Monk:
+Don't add ve-edit tab in namespaces where it's not available
+
+https://gerrit.wikimedia.org/r/133851",1400279284,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fe5hswi3ghhljkcsvvmj,task_subcomment,NA
+VisualEditor extension on AffCom wiki,"**Author:** `admin`
+
+**Description:**
+Greetings,
+Please add the VisualEditor extension - and any related elements - to the AffCom wiki (chapcom.wikimedia.org).
+
+Thank you!
+-greg aka varnent
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1397915580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ff5dovr2nj7hbi4mfk6d,task_description,resolved
+VisualEditor extension on AffCom wiki,Looks like that would've been done in https://gerrit.wikimedia.org/r/#/c/174793/ - sorry this bug was missed.,1433071229,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ff5dovr2nj7hbi4mfk6d,task_subcomment,NA
+VisualEditor extension on AffCom wiki,Looks like that would've been done in https://gerrit.wikimedia.org/r/#/c/174793/ - sorry it was missed.,1433071217,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ff5dovr2nj7hbi4mfk6d,task_subcomment,NA
+VisualEditor extension on AffCom wiki,"**admin** wrote:
+
+Whoops - sorry - meant to close a different one - my bad.  :/",1398701272,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ff5dovr2nj7hbi4mfk6d,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"Div tags like the ones seen in https://meta.wikimedia.org/wiki/Grants:IdeaLab cause ""alienated content""/prevent people from editing the page.  VisualEditor should support div tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1397572320,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rvzy7u46557pyglomvpy,task_description,open
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,Filed {T139388},1467737899,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"This is definitely not new, but this looks like a Parsoid problem with the selective serializer. I think the bug is different from the request in the title of the page. The bug here is that if you edit the content of a div that has a templated style, the edits are being lost. This is a bug with the DOM diff algorithm which probably is mistakenly ignoring edits in nodes marked mw:ExpandedAttrs (as far as I can tell), and has been around since the very beginning. I'll open a new bug report for this and let this task be for the original request (which is allowing edits of <div>s with templated attributes).",1467737626,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,I can confirm this problem exists at least for some months. ,1466673250,PHID-USER-bdyms27sdtgdvjm7zfz4,True,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"Eurgh, that's not good. Was there a Parsoid change recently-ish, or is it breakage at our end?",1466672862,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"Confirmed, this now silently fails to save your edits, which is VERY confusing for an end user.",1466672573,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"Unfortunately, it seems this has regressed from 'cannot edit' to 'can edit, but changes do not show up'. Could the priority be increased to reflect that?",1460920415,PHID-USER-muirnivxp5hzppn2a3z7,True,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style,"<div> tags work just fine, and have for nearly a year. The problem here is a <div> tag with a template in its style attribute.",1397587517,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rvzy7u46557pyglomvpy,task_subcomment,NA
+"VisualEditor: Existing non-positional metas (like categories) get wrapped in format changes, but new ones get appended in a terminal paragraph","Steps to reproduce:
+* go to https://test.wikipedia.org/wiki/Page466?veaction=edit
+* select the whole article content (Ctrl + A)
+* from the format menu, select one of the options (except ""Paragraph"")
+* go to ""Save page"" > ""Review your changes""
+
+No matter if you selected ""Heading"", ""Preformatted"" or something else, all existing categories would get that format. So one can accidentally put a category in a header.
+
+However, if you add one or more categories in VE using the dedicated menu, then (without saving) repeat those steps, you will see that the newly added categories are left out of the formatting change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://test.wikipedia.org/w/index.php?diff=197978",1397524380,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-r2gtjg6dw22voeqzade6,task_description,open
+"VisualEditor: Existing non-positional metas (like categories) get wrapped in format changes, but new ones get appended in a terminal paragraph",Any updates?,1414263222,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-r2gtjg6dw22voeqzade6,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,"I edited https://www.mediawiki.org/w/index.php?title=MediaWiki-Vagrant&oldid=946962 with VisualEditor.  Everything after the ""Quick Start"" section appeared in monospace.
+
+I repro'd with the smaller test page https://www.mediawiki.org/wiki/User:S_Page_(WMF)/VE_span_bug
+
+I think the issue lies in
+
+ <p style=""font-size: 1.2em; margin-top: 1.2em;"">When Vagrant is done configuring your machine, browse to <span class=plainlinks>http://127.0.0.1:8080/</span> to find your MediaWiki instance. The admin password is <code>vagrant<code>.</span>
+
+Note its incorrect second opening <code> instead of closing the code, and a second closing </span>. Yet regular wiki parsing can handle it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:S_Page_(WMF)/VE_span_bug",1396988880,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-4tie5um47m54nxlowc4v,task_description,declined
+Parsoid and Tidy differ in how they deal with misnested tags,Tidy is on the way to being removed next year. Parsoid and RemexHTML will handle broken HTML markup much more similarly since they both using HTML5 tree building to fix up broken markup.,1513635415,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,">>! In T65699#1694336, @MarkAHershberger wrote:
+> fwiw, one of the people behind tidy-html5 says [[ https://github.com/htacg/tidy-html5/issues/277#issuecomment-144808830 |  he tested ]]  and found that this issue was fixed.
+
+Thanks @MarkAHershberger. What we are getting at with the Tidy replacement and which applies here as well is that we really don't need Tidying or any such thing in mediawiki. What we need is a HTML5 parser (something that takes a string and parses it according to the well-specified HTML5 parsing algorithm). 
+
+We don't need all the extra things that the old Tidy did. So, if the new tidy-html5 project implemented what we needed, it would simply be a HTML5 tree builder that takes a string, and builds a DOM. If we needed (for backward compatibility reasons) to implement additional post-processing on the DOM (to do some of the things the old/in-production Tidy does), then we would need a full DOM API. But, if we determine as part of the work in T89331 that we can drop all the extra things the old Tidy does, then we may be able to not bother with the DOM API, as long as the tool generated a faithful serialization of the parsed DOM tree.
+
+T89331 does not mandate an external HTML5 parsing service. If we determine that tidy-html5 is ""good enough"", then, it would be an acceptable fallback for mediawiki installations that are happy with it. In fact, wikis don't even need to replace the ""old tidy"" if they don't care about all the bugs filed against it. Part of the impetus to T89331 is to pay down technical debt. It also moves PHP parser and Parsoid output closer. It also brings us closer to reducing complexity in Parsoid, and eventually in the glorious future, to maybe have a simple bidirectional parser entirely in core without need for an external service. We can chat more on IRC if you have more questions. I didn't add this explanation to T89331 since that ticket is already very long with a lot of discussion.",1443739513,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,"fwiw, one of the people behind tidy-html5 says [[ https://github.com/htacg/tidy-html5/issues/277#issuecomment-144808830 |  he tested ]]  and found that this issue was fixed.",1443724777,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,*** Bug 63798 has been marked as a duplicate of this bug. ***,1399417330,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+Parsoid and Tidy differ in how they deal with misnested tags,"(In reply to spage from comment #0)
+ 
+> Note its incorrect second opening <code> instead of closing the code, and a
+> second closing </span>. Yet regular wiki parsing can handle it.
+
+This is Tidy doing the cleanup. PHP parser does not do the fixup automatically. This is a known issue -- we have a bunch of these scenarios now where Parsoid and Tidy fixup broken code differently. We'll never match Tidy behavior (which is not always the desired behavior in any case). But, as for this specific scenario, fixing this will require us to use heuristics in the tokenizer and more complexity. At this time, it is not clear if the additional complexity is worth it, except for easy to auto-fix scenarios.",1396990520,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4tie5um47m54nxlowc4v,task_subcomment,NA
+"VisualEditor: Fatal ""SCRIPT16389: Unspecified error"" error in IE9","Turning on debugging in IE9 and then hitting ""Edit"" ends up with this in the console:
+
+  SCRIPT16389: Unspecified error. 
+  load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-
+  vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&
+  version=20140408T180250Z&*, line 642 character 159
+
+
+The line that is highlighted (running with ""Format JavaScript"" checked) is:
+
+  this.nativeSelection.addRange(getNativeRange(range).cloneRange());
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396985820,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-deyxxgilo6bu43xrinwb,task_description,resolved
+"VisualEditor: Fatal ""SCRIPT16389: Unspecified error"" error in IE9","IE9 loads fine now, just not in debug mode.",1461148432,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-deyxxgilo6bu43xrinwb,task_subcomment,NA
+VisualEditor: Newly inserted inline templates do not take annotations from the surrounding text,"When adding templates such as https://fr.wikipedia.org/wiki/Mod%C3%A8le:E (which adds a superscripted ""e"" to words), the letter will need further formatting to match the surrounding text if that is italic, bold, ... .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396954980,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-2scgn55flrrhzwl72ldr,task_description,open
+VisualEditor: Newly inserted inline templates do not take annotations from the surrounding text,Related: T140919,1579043632,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-2scgn55flrrhzwl72ldr,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","1. Log in at http://en.wikipedia.beta.wmflabs.org
+2. Enable VE
+3. Visit http://en.wikipedia.beta.wmflabs.org/wiki/File:ButtonsReversed.png
+   (or any foreign file with no local description page)
+
+You see the following views (tabs):
+    Read
+    View on Wikimedia Commons
+    Create source
+    Add local description ^beta
+
+4. Visit http://en.wikipedia.beta.wmflabs.org/wiki/File:Button_hover.svg
+   (or any foreign file with an existing local description page)
+
+You see:
+    Read
+    View on Wikimedia Commons
+    Edit source
+    Edit local description ^beta
+    View history
+
+The tab name ""Create/Edit source"" does not sit well next to ""Add/Edit local description ^beta"". The wikitext-editing tab needs a better name when viewing foreign files.
+
+Admittedly these tabs were altered in core [1] without consulting the VE people, but of course, it is the responsibility of extension authors to catch up to new core functionality.
+
+[1] Gerrit change 104182
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396949940,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-elatzf7sipmoeh7h3gfm,task_description,resolved
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","Change 124775 merged by jenkins-bot:
+Use updated tab labels on description pages for files in foreign repos
+
+https://gerrit.wikimedia.org/r/124775",1397243472,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","Change 124775 had a related patch set uploaded by Alex Monk:
+Use updated tab labels on description pages for files in foreign repos
+
+https://gerrit.wikimedia.org/r/124775",1396998747,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","(In reply to Alex Monk from comment #2)
+> So ""Edit source"" or ""Create source"" should become ""Edit local description
+> source"" or ""Add local description source"" on file description pages for
+> files in foreign repositories?
+
+I guess. It's verbose, but then that's really my fault...",1396993688,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","So ""Edit source"" or ""Create source"" should become ""Edit local description source"" or ""Add local description source"" on file description pages for files in foreign repositories?",1396985463,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor: Update integration to cope with the new ""view on <repo>"" tabs on file pages","Sorry that we missed this.
+
+BTW, changes to major MediaWiki semantics (even good ones like this) should really be highlighted on wikitech-l and/or ideally design-l before being implemented and merged. I have a bunch of ideas about how this could have been done more cleanly that it's now too late to try out. :-(",1396980948,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-elatzf7sipmoeh7h3gfm,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics","This is related to bug 50996.
+
+Open a page that contains hieroglyphics, like https://www.mediawiki.org/w/index.php?oldid=942532#Hieroglyphics
+
+You should be able to open the hieroglyphics ""node"" by double-clicking, but it isn't working.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396903680,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_description,resolved
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics",Verified the fix in test2,1397513626,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics",Verified the fix on betalabs,1397074560,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics","Change 124469 merged by jenkins-bot:
+Actually actually fix double-clicking on hieroglyphics nodes
+
+https://gerrit.wikimedia.org/r/124469",1396985397,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics","Change 124469 had a related patch set uploaded by Catrope:
+Actually actually fix double-clicking on hieroglyphics nodes
+
+https://gerrit.wikimedia.org/r/124469",1396907151,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics",https://gerrit.wikimedia.org/r/#/c/121514/,1396903898,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics","I think Trevor fixed this in an unrelated recent commit, let me find it.",1396903815,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-okbzzhxdfdpwr6xdxdko,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"**Author:** `richlv`
+
+**Description:**
+visual editor from git f8d56e6804a12248b485c2d3b49d4ff0ffa7220c
+
+edit a page with opera 12.16 on linux, place cursor on an empty line, hit 'esc' - 
+symbol ♙ is inserted.
+
+bug #51140 was about this symbol being inserted in a different situation and is supposed to be fixed.
+
+reproducible at https://www.zabbix.org/wiki/Docs/visual_editor_test (if you would like to create a test account, ""real name"" is mandatory)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396884180,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lyauywwlebuzz4wjazr5,task_description,resolved
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"Change 143322 merged by jenkins-bot:
+ve.ce.Surface: Prevent incorrect pawning in Opera 12
+
+https://gerrit.wikimedia.org/r/143322",1404371327,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"Change 143322 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ce.Surface: Prevent incorrect pawning in Opera 12
+
+https://gerrit.wikimedia.org/r/143322",1404225651,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,Seems like it wouldn't be a problem if you just filtered out those keycodes.,1404210279,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"This is probably a regression from 4e377629e39a4af9405a5ea8972bdeb1af37ddf6
+(fix for bug 48335).",1399670246,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"So, Opera 12 sends the events for the keypresses of Esc and Tab. These events reach ve.ce.Surface.prototype.onDocumentKeyPress and eventually ve.ce.Surface.prototype.handleInsertion, which decides to insert the pawn, which will not be overwritten because neither Esc not Tab produce any text.
+
+onDocumentKeyPress attempts to filter out non-character keypresses by discarding ones where the charCode is 0; Opera's event for Esc has charCode == 27,
+for Tab charCode == 9. I guess other browsers use 0 here for some weird reason and you depend on this behavior.",1399669752,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"Yes. I don't have time right now, but I'll try to get around to this sooner or later.",1398188177,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"MatmaRex, you still interested in taking on Opera 12 bugs?",1396922428,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12,"**richlv** wrote:
+
+(1) another way to get that symbol with opera - hit 'tab' on an empty line.
+
+both of these also ""work"" in an empty table cell",1396892008,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lyauywwlebuzz4wjazr5,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,"Both enwiki and frwiki (at least) use {{FULLPAGENAME}} in [[MediaWiki:newarticletext]], which is unusable, because it is replaced by “API” in VisualEditor.
+
+So the warnings contain texts like
+ — “You can also start your new article at Special:Mypage/API.” (https://en.wikipedia.org/wiki/Nawak?veaction=edit)
+ — “Comment faire pour créer l'article API ?” (https://fr.wikipedia.org/wiki/Nawak?veaction=edit)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59608",1396819500,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_description,resolved
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,*** Bug 63673 has been marked as a duplicate of this bug. ***,1402295035,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,"Change 127388 merged by jenkins-bot:
+Set context title when rendering edit notices and checkboxes
+
+https://gerrit.wikimedia.org/r/127388",1397879339,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,*** Bug 63811 has been marked as a duplicate of this bug. ***,1397866699,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,"Change 127388 had a related patch set uploaded by Catrope:
+Set context title when rendering edit notices
+
+https://gerrit.wikimedia.org/r/127388",1397866440,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,Presumably we're not passing the 'title' parameter to the URL to give it context?,1396887988,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”,*** Bug 63631 has been marked as a duplicate of this bug. ***,1396887928,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cmm2l4x3yrjzyxs5v4rl,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"Some icons need to be flipped for RTL languages. Here's what I found till now:
+
+In lib/ve/lib/oojs-ui/images/icons:
+* help.svg - This is a question mark in a circle. This should be flipped for all RTL languages, but *not* for Hebrew (he) and Yiddish (yi).
+
+In lib/ve/modules/ve/ui/styles/images/icons:
+* external-link.svg
+
+In modules/ve-mw/ui/styles/images/icons:
+* gallery.svg
+* parameter.svg
+* parameter-set.svg
+* ref-cite-book.svg
+* ref-cite-journal.svg
+* ref-cite-news.svg
+* reference.svg
+* references.svg
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396793460,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-aulut6cxxmdw4srpyjpu,task_description,resolved
+VisualEditor: Some icons need to be flipped for RTL languages,"Except for the remaining technical issue in OOjs UI, this was done 6 months ago. Closing, and follow-up for OOUI is in T76540.",1417566229,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to Ed Sanders from comment #4)
+> (In reply to James Forrester from comment #3)
+> > No; OOUI only understands RTL and LTR, not specific languages. The bold icon
+> > isn't from OOUI but from VE itself, which does. Oy.
+> 
+> Actually the per-language icon format is in OOUI (IconedElement.js line 42).
+> You need to define the language overrides every time you specify the icon
+> instead of just making it a 'feature' of the icon like directionality.
+
+Oh, interesting. OK, so we'd need to use that in downstream tools if particular languages want over-rides? Ick. See gerrit 143407 for the easy part.",1404246888,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to James Forrester from comment #3)
+> No; OOUI only understands RTL and LTR, not specific languages. The bold icon
+> isn't from OOUI but from VE itself, which does. Oy.
+
+Actually the per-language icon format is in OOUI (IconedElement.js line 42). You need to define the language overrides every time you specify the icon instead of just making it a 'feature' of the icon like directionality.",1404244142,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to Amir E. Aharoni from comment #2)
+> (In reply to James Forrester from comment #1)
+> > (In reply to Amir E. Aharoni from comment #0)
+> > > Some icons need to be flipped for RTL languages. Here's what I found till
+> > > now:
+> > > 
+> > > In lib/ve/lib/oojs-ui/images/icons:
+> > > * help.svg - This is a question mark in a circle. This should be flipped for
+> > > all RTL languages, but *not* for Hebrew (he) and Yiddish (yi).
+> > 
+> > This should (a) be an OOUI bug, and (b) is really quite hard for us to do as
+> > our build system only supports LTR or RTL, it doesn't do language-specific
+> > builds. How high priority is this?
+> 
+> Pretty important for people who write Arabic, Persian and Urdu.
+> Can't it be done the same way it's done for Bold and Italic?
+
+No; OOUI only understands RTL and LTR, not specific languages. The bold icon isn't from OOUI but from VE itself, which does. Oy.",1404229874,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to James Forrester from comment #1)
+> (In reply to Amir E. Aharoni from comment #0)
+> > Some icons need to be flipped for RTL languages. Here's what I found till
+> > now:
+> > 
+> > In lib/ve/lib/oojs-ui/images/icons:
+> > * help.svg - This is a question mark in a circle. This should be flipped for
+> > all RTL languages, but *not* for Hebrew (he) and Yiddish (yi).
+> 
+> This should (a) be an OOUI bug, and (b) is really quite hard for us to do as
+> our build system only supports LTR or RTL, it doesn't do language-specific
+> builds. How high priority is this?
+
+Pretty important for people who write Arabic, Persian and Urdu.
+Can't it be done the same way it's done for Bold and Italic?",1404194275,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: Some icons need to be flipped for RTL languages,"(In reply to Amir E. Aharoni from comment #0)
+> Some icons need to be flipped for RTL languages. Here's what I found till
+> now:
+> 
+> In lib/ve/lib/oojs-ui/images/icons:
+> * help.svg - This is a question mark in a circle. This should be flipped for
+> all RTL languages, but *not* for Hebrew (he) and Yiddish (yi).
+
+This should (a) be an OOUI bug, and (b) is really quite hard for us to do as our build system only supports LTR or RTL, it doesn't do language-specific builds. How high priority is this?
+
+> In lib/ve/modules/ve/ui/styles/images/icons:
+> * external-link.svg
+
+Not currently used, but done in gerrit 143240.
+
+> In modules/ve-mw/ui/styles/images/icons:
+> * gallery.svg
+> * parameter.svg
+> * parameter-set.svg
+> * ref-cite-journal.svg
+> * ref-cite-news.svg
+> * reference.svg
+> * references.svg
+
+Done in gerrit 143241.
+
+> * ref-cite-book.svg
+
+Not now needed (no LTR/RTL variance). Similarly for ref-cite-web.",1404186595,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aulut6cxxmdw4srpyjpu,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Try to open math inspector, it does not open up.
+Not showing any error in the console
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396636260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-adfbbfgylcnmev6236w2,task_description,resolved
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Verified the fix on production:
+https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox",1397775316,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,Verified the backported fix on test2: https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1397086948,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,Verified the fix on betalabs: http://en.wikipedia.beta.wmflabs.org/wiki/9thaprilChrome?veaction=edit,1397086640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Change 125023 merged by jenkins-bot:
+Update tool to use a command
+
+https://gerrit.wikimedia.org/r/125023",1397086016,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Change 125023 had a related patch set uploaded by Jforrester:
+Update tool to use a command
+
+https://gerrit.wikimedia.org/r/125023",1397085355,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,"Change 125017 merged by jenkins-bot:
+Update tool to use a command
+
+https://gerrit.wikimedia.org/r/125017",1397085211,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: [Regression wmf21] Math inspector is not opening up,Apparently the Gerrit bot is broken? Trevor submitted https://gerrit.wikimedia.org/r/#/c/125017/ for this and I +2ed it. Now we're waiting for Jenkins/Zuul to stop being broken so it'll actually get merged.,1397084425,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-adfbbfgylcnmev6236w2,task_subcomment,NA
+VisualEditor: Update styling of the MW format paragraph menu to match changes to Vector,"It would be nice if the new typography (e.g. serifed fonts for headlines) were reflected in VisaulEditor's ""format paragraph"" menu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63985",1396635960,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-4wvfrqahqjzbkpjnaxd4,task_description,resolved
+VisualEditor: Update styling of the MW format paragraph menu to match changes to Vector,"Change 130771 merged by jenkins-bot:
+Style the FormatTool to be more like Vector's new look
+
+https://gerrit.wikimedia.org/r/130771",1398972824,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4wvfrqahqjzbkpjnaxd4,task_subcomment,NA
+VisualEditor: Update styling of the MW format paragraph menu to match changes to Vector,"Change 130771 had a related patch set uploaded by Jforrester:
+Style the FormatTool to be more like Vector's new look
+
+https://gerrit.wikimedia.org/r/130771",1398901458,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4wvfrqahqjzbkpjnaxd4,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"`mw.util.$content` from module `mediawiki.util` seems to be needless.
+
+```lang=js
+	$( function () {
+		mw.util.$content...
+	} );
+```
+can be replaced by
+```lang=js
+	mw.hook( 'wikipage.content' ).add( function ( $content ) {
+		$content...
+	} );
+```
+`mw.hook()` is necessary to support [[https://www.mediawiki.org/wiki/Manual:Live_preview|Live Preview]].",1396517640,PHID-USER-3dmql6z7s5lnn5lu2vs3,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_description,open
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"[[https://hu.wikipedia.org/w/index.php?title=MediaWiki:Gadget-warning.js&oldid=25499069#L-474|hu:MediaWiki:Gadget-warning.js]] uses this in an event handler to put a DOM element on the top of the page. The `wikipage.content` hook is not a good replacement, for two reasons:
+* (mildly bad) it’s asynchronous, and can be fired multiple times. Since the event handler can also run multiple times, it would require a global state to ensure that not more than one hook listener is active at a time.
+* (quite bad) it may be fired with several elements, not only `mw.util.$content` (e.g. #discussiontools previews fire it too). Adding the DOM element to all sorts of parser output blocks is definitely not what the user wants to see.
+
+What should be the path forward?",1671802302,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"@TheDJ Yeah, we could mark it as deprecated, do a Tech-News round, track the usage in Grafana/mw-js-deprecate and maybe do a few Global Search queries ourselves to help mitigate a few.",1671655569,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),@Krinkle It seems this has been done for all extensions now ? Which means that only gadgets and userscripts are still users. Do we investigate the userscripts or do we simply mark as deprecated and then investigate what needs it ?,1671576912,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 766859 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/InlineCategorizer@master] Remove needless use of mw.util.$content%%%
+https://gerrit.wikimedia.org/r/766859",1654562808,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 766867 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/CirrusSearch@master] ext.cirrus.serp: Use \""wikipage.content\"" instead of mw.util.$content%%%
+https://gerrit.wikimedia.org/r/766867",1646087341,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 766867 had a related patch set uploaded (by Krinkle; author: Krinkle):
+%%%[mediawiki/extensions/CirrusSearch@master] ext.cirrus.serp: Use \""wikipage.content\"" instead of mw.util.$content%%%
+https://gerrit.wikimedia.org/r/766867",1646084271,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 766859 had a related patch set uploaded (by Krinkle; author: Krinkle):
+%%%[mediawiki/extensions/InlineCategorizer@master] Remove needless use of mw.util.$content%%%
+https://gerrit.wikimedia.org/r/766859",1646083215,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"@Fomafix: Hi, I'm resetting the task assignee due to inactivity. Please feel free to reclaim this task if you plan to work on this - it would be welcome! Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for more information - thanks!",1643840291,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),">>! In T65466#683593, @Fomafix wrote:
+> Thanks for explanation.
+> 
+> What about a new hook 'wikipage.body'?
+
+If there's a need for something subscription/offering based in that way, I think that would be useful yes.
+
+However, I think the existing use-cases for `mw.util.$content` need/want something direct and synchronous.
+
+But, based on how we solved the Notifications use case, with a dedicated interface contract to the skin, we can probably do the same for other use cases. I think that's better than the generic  `mw.util.$content` which is quite difficult to use right now (because you have to wait for `$()` before it exists), and also inverts the responsibility. The module placing stuff in the body should not be the one deciding where it goes, unless it is the skin code doing it.
+
+Re-opening this (also in light of restricted T203549). Let's identify what uses/needs it, and then migrate them to either use `mw.hook('wikipage.content')` for cases where they need to find things in the content, or to other mechanisms like we did for Notifications (if they need to add something).
+
+I don't mind keeping it long-term or providing `wikipage.body` - if we find a need for that.",1588450365,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 123559 abandoned by Krinkle:
+Deprecate mw.util.$content
+
+Reason:
+Superseded by I30bdd893e0a0a340076.
+
+https://gerrit.wikimedia.org/r/123559",1398882823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Thanks for explanation.
+
+What about a new hook 'wikipage.body'?
+
+In mediawiki.page.startup.js fire
+	mw.hook( 'wikipage.body' ).fire( mw.util.$content ) );
+
+In mediawiki.notification.js replace
+	$( function () {
+		mw.util.$content...
+	} );
+by
+	mw.hook( 'wikipage.body' ).add( function ( $body ) {
+		$body...
+	} );",1396693934,PHID-USER-3dmql6z7s5lnn5lu2vs3,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Closing as won't fix per discussion between Daniel Friesen and myself at https://gerrit.wikimedia.org/r/123559.
+
+Although the naming is unfortunate, these are different things for different use cases.
+
+mw.hook( 'wikipage.content' ) is to get a reference to #mw-content-text (the true wiki page content, no skinning around it). It is different from $( '#mw-content-text' ) in that:
+
+* It can be asynchronous (you can register the hook without needing to explicitly wait for document-ready).
+* It is more semantically correct if your intent is ""change content"" because it will re-fire when the content changes dynamically (e.g. after saving an edit with VisualEditor, or when ajax live previewing wikitext, or in some hypothetical ""ajax navigation"" feature).
+
+mw.util.$content is to get a reference to the body content wrapper (the element containing #mw-content-text, usually indicated by .mw-body). Because mw.util.$content has been around since before mw.hook, it is likely that there are existing uses out there that would benefit from using mw.hook instead. However there remain uses for mw.util.$content where mw.hook is not a suitable alternative.
+
+Having said that, I still think we should deprecate mw.util.$content because it sucks (retrieving its value is tricky because it is asynchronously initialised without a clear callback for when that happens). However until we have an alternative for it, let's keep it.
+
+Ideally we'd just mandate that all skins follow the convention to use mw-body class and then just document that as an API (similar to how addPortletLink's html structure has become more or less skin independent, though not quite there yet) that people use by waiting for domready and querying mw-body or mw-body-primary.",1396643082,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' ),"Change 123559 had a related patch set uploaded by Gerrit Patch Uploader:
+Deprecate mw.util.$content
+
+https://gerrit.wikimedia.org/r/123559",1396517857,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sg2l7bjtavldgjqjhg4m,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Screenshot of excessive whitespace on top of an in-content dialog with h2 heading
+
+Since inner padding of the dialog container and top margin of the header don't collapse, they get stacked and now have an excessive amount of whitespace (see screenshot).
+
+The margin-top of 'div#content h2' should be safe to remove. We didn't have it in the past, and in any regular text flow context it is already spaced away from the preceding element by the bottom margin of block level elements (like paragraphs and tables).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63312
+
+**Attached**: {F13341}",1396381920,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_description,invalid
+Vector: Headings have excessive top margin when used as first element in a content container,">Could we tweak it to have a !firstChild or something on H2s so it only triggers
+>for the H2s that we actually want to style?
+
+I can't think of any way to do this that would be reliable. We could do something like...
+#content h2(:not( .dialogHeader ))
+but that would still require making sure that all headers in dialogs included that class. (And if we're updating those headers anyway, we might as well convert them from h2s into something else.)
+
+We could also use jQuery to try to guess which h2s are actually section headers and which ones aren't, but that would cause a style change flash.
+
+I still haven't heard any evidence that this bug actually affects more than a single dialog box. If it's just one dialog, is it really that hard to fix, even though the code is unmaintained? What extension generates that dialog box?",1403037124,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"(In reply to Ryan Kaldari from comment #11)
+> What James says is true, although there currently isn't any way to have
+> large margins between the sections on desktop without increasing the margins
+> on "".content h2"", so unless design agrees to reduce those margins, the fix
+> will have to be to the unmaintained code (at least until the desktop DOM
+> includes some sort of section elements).
+
+Could we tweak it to have a !firstChild or something on H2s so it only triggers for the H2s that we actually want to style?",1403036084,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"What James says is true, although there currently isn't any way to have large margins between the sections on desktop without increasing the margins on "".content h2"", so unless design agrees to reduce those margins, the fix will have to be to the unmaintained code (at least until the desktop DOM includes some sort of section elements).",1403032221,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"(In reply to Jared Zimmerman (WMF) from comment #9)
+> This is as designed, as Steven said, if there are 1 one off cases where the
+> padding is too large within specific features or use cases (not articles or
+> content pages) the feature teams should write modifications to the style for
+> those cases.
+
+This is a complaint about the breakage of unmaintained code that was written with the expectation that people wouldn't unexpectedly change these, though. There are no ""feature teams"" to fix the breakage for you…",1403031342,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"This is as designed, as Steven said, if there are 1 one off cases where the padding is too large within specific features or use cases (not articles or content pages) the feature teams should write modifications to the style for those cases.",1403031035,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,CCing Jared since this is really a design issue.,1403027394,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Change 123024 abandoned by Krinkle:
+vector: Remove margin-top from 'div#content h2'
+
+Reason:
+Implementing something in a hacky way that breaks expectations about how page layout works and then putting the burden on other maintainers to make it work well with the rest of the web is imho not ideal practice. But I can't invest in this now, so snafu. You're welcome.
+
+https://gerrit.wikimedia.org/r/123024",1401852285,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Because the discussion here clearly points to a lack of consensus, I'm removing the 1.23.0 target.",1399652862,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,">I think you might've missed that I said the margin-top can be safely removed 
+>because it is ineffective. It isn't ""increasing"" the visible whitespace between 
+>sections...
+
+I don't think that's accurate. Having ""h2 { margin-top: 1em; }"" is definitely increasing the whitespace significantly between sections. With that rule in place, the whitespace is effectively 21 pixels (0.875em x 1.5em x 1em x 16px). Without it, in most cases, the whitespace is only 7 pixels (0.875em x 0.5em x 16px). That's a big difference.
+
+If we want to change the amount of whitespace between sections, we need to get input from design on this. If we don't want to change the amount of whitespace between sections, we need to find a different way to implement the whitespace. Currently, however, I don't see any better way to implement the whitespace between sections.
+
+As the bug is currently defined, I recommend WONTFIX.",1398882628,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Rephrasing bug to reflect the two most common problem cases:
+
+* Using a heading as first element on page (e.g. the first section, as opposed to between two sections).
+
+* Using a heading inside a container that isn't the root of the page (e.g. inside a bubble such as on [1], or any other kind of sub container).
+
+
+[1] https://www.mediawiki.org/w/index.php?title=Help:VisualEditor/User_guide&oldid=984581#toc",1398873871,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"I think you might've missed that I said the margin-top can be safely removed because it is ineffective. It isn't ""increasing"" the visible whitespace between sections, because all block level elements already have sufficient *bottom* margin. And browsers collapse/merge the top margin of the next element with the bottom margin of the previous element.
+
+No matter whether it's a paragraph, list, <pre>, gallery or <table>, their bottom margin is already taking care of that space. When I removed the top-margin of headings locally it made little to no visible difference.
+
+So if the goal was to increase the space between sections, it failed to do that.
+
+If we do want to increase space between sections, I suggest it is implemented in different way. Using margin-top for that is in my opinion inappropriate and bound to cause layout hazards.
+
+I agree the specific instance in which I ran into this bug is dubious, but in general you mustn't assume that a heading will only be used in the root flow of the content and only in the n+1th section of page.
+
+Using margin-top means that:
+* Using the heading in the first section on a page will cause a weird gap on top because it's trying to offset itself from the previous section when in fact that is the top of the page. Which is a problem since content wrappers already have padding, and that doesn't merge with margins of elements inside.
+
+* Using the heading inside another element (blockquote, table, infobox, form), even inside elements that aren't intended as their own block (e.g. heading bubbles such as on [1]) will now have a margin on top on the inside intended to separate itself from a section. This could in theory be worked around by resetting margins or creating negative catch margins. However that would be an unintuitive hack that doesn't scale because it's moving the responsibility to the wrong component (e.g. if you want to use a <table> on a page, you cannot be expected to have to set all kinds of inline styles to make it render properly, it is the skin's fault for changing the default of all headings to act like section separators. The skin should take care to recognise the relevant headings and style them and leave the others untouched).
+
+I'm not going to spend time on finding one of many alternate ways to implement section separation margins on desktop, but the way it is implemented right now is and will continue to cause all kinds of layout problems due to it applying top-margins that are too large when applied in a context that isn't between two sections.
+
+[1] https://www.mediawiki.org/w/index.php?title=Help:VisualEditor/User_guide&oldid=984581#toc)",1398873661,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"**swalling** wrote:
+
+I think this is probably something where special UI elements like dialogs should be adding/changing their own H2 styles, rather than reusing styles intended for content pages.
+
+Repeating Kaldari's comment on the patch:
+
+""The 1em margin was implemented on purpose by the design team. As mentioned in the FAQ, they wanted to significantly increase the whitespace between sections. Unfortunately on desktop we don't have any ""section"" DOM element, so adding top margin to h2s is the best way to accomplish that.
+
+Since dialogs don't often belong to the content div, it seems like better solutions to bug 63390 would be:
+
+1. Move the dialog outside the content div;
+2. Don't use h2s in that dialog, or...
+3. Override the h2 style in that case.
+Is there more than 1 dialog affected by this bug?""",1397201147,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Vector: Headings have excessive top margin when used as first element in a content container,"Change 123024 had a related patch set uploaded by Krinkle:
+vector: Remove margin-top from 'div#content h2'
+
+https://gerrit.wikimedia.org/r/123024",1396382016,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h3rnvqmaajhu7cd26sul,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Intention:
+Add a value to an empty cell in a table using VE
+
+Steps to Reproduce:
+1. You need a page with a table with at least one empty cell (e.g. https://en.wikipedia.beta.wmflabs.org/wiki/User:ESanders_(WMF)/sandbox/T65356)
+2. Open page for VE editing
+3. Double click on the empty cell, then add some text
+4. Show the wikitext diff in the save dialog
+
+Actual Results:  
+In addition to the entered text a line-break is added
+
+Expected Results:  
+No additional line-break
+
+Reproducible: Always
+
+Note that this does not happen for cells which already contains a value
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396347240,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-b2kjds44fcmdnsoqczzm,task_description,resolved
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Change 670606 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (145cf95d8)
+
+https://gerrit.wikimedia.org/r/670606",1615494433,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Change 670606 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (145cf95d8)
+
+https://gerrit.wikimedia.org/r/670606",1615417291,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Change 667411 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Use wrapper paragraphs in empty branch nodes
+
+https://gerrit.wikimedia.org/r/667411",1615417123,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Change 667411 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] Use wrapper paragraphs in empty branch nodes
+
+https://gerrit.wikimedia.org/r/667411",1614528761,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Hmm, the difference seems to be that if you click once on the empty cell and start typing, VE doesn't wrap the text in a `<p>`,
+
+```
+<td data-parsoid=""{&quot;stx_v&quot;:&quot;row&quot;,&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[38,41,2,0]}"">haha</td>
+```
+
+However, doubling clicking and then typing does,
+
+```
+<td data-parsoid=""{&quot;stx_v&quot;:&quot;row&quot;,&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[38,41,2,0]}""> <p>haha</p></td>
+```
+
+Serializing the paragraph introduces a newline which would break the row syntax, so Parsoid switches the other format.  I suppose we could be smarter about the p/td nl constraints, or VE maybe avoid introducing the paragraph to begin with?",1490804735,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,*** Bug 73215 has been marked as a duplicate of this bug. ***,1415618411,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format,"Created attachment 14994
+Screenshot
+
+Screenshot showing the result to the source of editing a filled and an empty cell using VE.
+
+**Attached**: {F13280}",1396347330,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-b2kjds44fcmdnsoqczzm,task_subcomment,NA
+VisualEditor: Double colons when linking to File/Category,"Intention:
+Linking to a file using visual editor
+
+Steps to Reproduce:
+1. Edit page on using VE
+2. Click add link
+3. Enter a filename with File-prefix (e.g. File:Foo.svg)
+4. Press enter
+5. Press enter again
+
+The same thing happens for categories or if the preceding colon is added manually.
+
+
+Actual Results:  
+4. Inserted text is changed to :File:Foo.svg
+5. Inserted text is changed to ::File:Foo.svg
+
+Expected Results:  
+4. As result
+5. No change
+
+Reproducible: Sometimes
+
+The same thing happens for categories or if the preceding colon is added manually. I can get this to happen repeatedly but occasionally VE will correctly know not to add the second colon (have not identified when though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63355",1396343280,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-vkbfyitznumudqoxqfgs,task_description,resolved
+VisualEditor: Double colons when linking to File/Category,"Dupe of 50279 (and now fixed).
+
+*** This bug has been marked as a duplicate of bug 50279 ***",1403995088,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vkbfyitznumudqoxqfgs,task_subcomment,NA
+VisualEditor: Double colons when linking to File/Category,"Here's a variation:
+
+1.  Edit page on using VisualEditor.
+
+2.  Type the file name you want (with or without the colon prefix that you want):  File:Example.jpg
+
+3.  Open the link inspector, which will offer to link these files (at least on en.wp):
+
+:File:Example.jpg
+File:Example.jpg
+File:Example.JPG
+
+4.  Choose the first.  Press enter.  Now it has changed the link target to ""::File:Example.jpg"" and says ""Invalid page title"".  (Saving this link will work correctly anyway.)
+
+5.  Alternatively, choose the second, and press enter.  This also works and does not produce the error message.",1401819333,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-vkbfyitznumudqoxqfgs,task_subcomment,NA
+VisualEditor: Double colons when linking to File/Category,"Also happening with FF, Win8.
+The resulting wikilink works, though.",1401801899,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-vkbfyitznumudqoxqfgs,task_subcomment,NA
+VisualEditor: Double colons when linking to File/Category,"Created attachment 14992
+Screencast
+
+Added video since this is not 100% reproducible
+
+**Attached**: {F13270}",1396344427,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-vkbfyitznumudqoxqfgs,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Template
+3.Click on Show Options
+4.Click on the trash icon.
+5.Click on ""Add Content""
+
+Observed Result:
+The ""Insert transclusion"" button becomes enabled and an empty transclusion with empty content gets added upon clicking on it.
+
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13225}",1396312320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pxydfaaecdb2drrqo3x6,task_description,resolved
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,Verified the fix in production,1415835803,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,Verified the fix in test2,1415229959,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Change 169638 merged by jenkins-bot:
+MWTransclusionModel: Exclude parts serialising to '' from the plain object
+
+https://gerrit.wikimedia.org/r/169638",1414624850,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Change 169638 had a related patch set uploaded by Alex Monk:
+MWTransclusionModel: Exclude parts serialising to '' from the plain object
+
+https://gerrit.wikimedia.org/r/169638",1414545036,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"See also bug 63340, which was duped to this one but is actually subtly different: it's about when the only part is a TemplatePlaceholderPage",1414117605,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,*** Bug 63340 has been marked as a duplicate of this bug. ***,1414098890,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Also, there is an error in the console:
+Uncaught TypeError: Cannot read property 'length' of null",1414091215,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+VisualEditor: Remove transclusion node if we were just going to set it to empty content,"Created attachment 14990
+Screenshot
+
+**Attached**: {F13226}",1396312398,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pxydfaaecdb2drrqo3x6,task_subcomment,NA
+"VisualEditor: ""Insert Transclusion""  button becomes enabled after adding a second empty template","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open the transclusion add dialog box by going to Insert>Template
+3.Click on the ""Show Options"" button
+4.Now click on the ""Add template"" button
+
+Observed Result:
+The ""Insert Transclusion"" button becomes enabled and clicking on that does nothing 
+
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13220}",1396311480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cgka64ivffbox23apkiw,task_description,resolved
+"VisualEditor: ""Insert Transclusion""  button becomes enabled after adding a second empty template","
+
+*** This bug has been marked as a duplicate of bug 63341 ***",1414098890,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cgka64ivffbox23apkiw,task_subcomment,NA
+"VisualEditor: ""Insert Transclusion""  button becomes enabled after adding a second empty template","Yeah , this one I filed for adding empty template and bug 63341 was specifically for adding empty content,but they might get fixed at one shot.In that case I guess we should merge these two?",1414097061,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cgka64ivffbox23apkiw,task_subcomment,NA
+"VisualEditor: ""Insert Transclusion""  button becomes enabled after adding a second empty template",Is this the same as bug 63341?,1414096243,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cgka64ivffbox23apkiw,task_subcomment,NA
+VisualEditor: There is no keyboard function to exit the Math Inspector and Gallery,"Right now, there is no keyboard function to exit the Math Inspector and Gallery inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396306440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gyyhelxas56x6xvw7n7w,task_description,declined
+VisualEditor: There is no keyboard function to exit the Math Inspector and Gallery,Escape works for me…,1402296299,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gyyhelxas56x6xvw7n7w,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"The media selector (both in WikiEditor and Visual Editor) does not find local images in a private wiki. When the same wiki is set to public, it works.
+
+I've tried this with 3 different installations (1.22 and 1.23wmf20) on two different servers, both with Visual Editor and WikiEditor. 
+
+The relevant setting is
+
+$wgGroupPermissions['*']['read'] = false;
+
+When this is set to false, when a user (logged in and registered) edits a page and starts typing the name of an existing file in the media selector, the input box remains empty and does not suggest existing file names. 
+
+When the read permission is set to true, then it works as expected (giving a list of suggestions in the input box) - but of course then the wiki is no longer private.
+
+On the other hand, the link selector finds the files when I type ""File:Filename.."". Also, the image is actually shown in the article when I insert it with Wiki markup, or when I type in the correct filename in the selector and click on ""insert"".
+
+So somehow the media selector (but not the link selector) does not understand the permission correctly for a logged-in user.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396213080,PHID-USER-mn2oreq3jstq45jm3fp5,False,PHID-TASK-qlnckdanskw255gs5et4,task_description,resolved
+Media selector doesn't find local media in private wiki,Related and more recent: T188236,1717452855,PHID-USER-3baphe4xso6l4kkryqex,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,See also T63151 and https://www.mediawiki.org/wiki/Topic:Rb7adzuz9pt6ifno,1444632168,PHID-USER-wtbw6n3qdyre3vir7o3z,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"I could not reproduce the error on officewiki (a private wiki which is about a week behind master). Both your examples return a `readapidenied` error (which is a bug on its own right, reported as T106425). The VE media selector works fine, with or without an asterisk.
+
+You could try to reproduce the bug in a controlled environment by using [[ https://www.mediawiki.org/wiki/MediaWiki-Vagrant | MediaWiki-Vagrant ]] with the `private` and `visualeditor` roles.",1437516326,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"Yes, this is the API request that fails to find the image:
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+It results in: 
+
+```
+/**/jQuery1113038504008506424725_1437475882811({""batchcomplete"":""""})
+```
+
+If I add an astericks at the end of the search-term, it works:
+
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server*&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+
+Results in:
+
+```
+/**/
+jQuery1113038504008506424725_1437475882811({
+    ""continue"": {
+        ""iistart"": ""2015-06-23T05:30:36Z"",
+        ""continue"": ""||""
+    },
+    ""query"": {
+        ""pages"": {
+            ""6672"": {
+                ""pageid"": 6672,
+                ""ns"": 6,
+                ""title"": ""Datei:Server\u00dcbersicht.png"",
+                ""index"": 1,
+                ""imagerepository"": ""local"",
+                ""imageinfo"": [{
+                    ""timestamp"": ""2015-06-23T05:31:57Z"",
+                    ""size"": 188839,
+                    ""width"": 3000,
+                    ""height"": 1606,
+                   ....
+                    ""mediatype"": ""BITMAP""
+                }]
+            }
+        }
+    }
+})
+```
+
+When using the astericks, the VE request works, but is repeated endlessly:
+
+{F203227}",1437479949,PHID-USER-wtbw6n3qdyre3vir7o3z,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"Yes, this is the API request that fails to find the image:
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+It results in: 
+
+```
+/**/jQuery1113038504008506424725_1437475882811({""batchcomplete"":""""})
+```
+
+If I add an astericks at the end of the search-term, it works:
+
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server*&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+
+Results in:
+
+```
+/**/
+jQuery1113038504008506424725_1437475882811({
+    ""continue"": {
+        ""iistart"": ""2015-06-23T05:30:36Z"",
+        ""continue"": ""||""
+    },
+    ""query"": {
+        ""pages"": {
+            ""6672"": {
+                ""pageid"": 6672,
+                ""ns"": 6,
+                ""title"": ""Datei:Server\u00dcbersicht.png"",
+                ""index"": 1,
+                ""imagerepository"": ""local"",
+                ""imageinfo"": [{
+                    ""timestamp"": ""2015-06-23T05:31:57Z"",
+                    ""size"": 188839,
+                    ""width"": 3000,
+                    ""height"": 1606,
+                    ""thumburl"": ""http://10.248.8.1/wiki/images/thumb/6/6c/ServerÜbersicht.png/300px-ServerÜbersicht.png"",
+                    ""thumbwidth"": 300,
+                    ""thumbheight"": 161,
+                    ""url"": ""http://10.248.8.1/wiki/images/6/6c/ServerÜbersicht.png"",
+                    ""descriptionurl"": ""http://10.248.8.1/wiki/index.php/Datei:ServerÜbersicht.png"",
+                    ""extmetadata"": {
+                        ""DateTime"": {
+                            ""value"": ""2015-06-23T05:31:57Z"",
+                            ""source"": ""mediawiki-metadata"",
+                            ""hidden"": """"
+                        },
+                        ""ObjectName"": {
+                            ""value"": ""Server\u00dcbersicht"",
+                            ""source"": ""mediawiki-metadata"",
+                            ""hidden"": """"
+                        }
+                    },
+                    ""mediatype"": ""BITMAP""
+                }]
+            }
+        }
+    }
+})
+```
+
+When using the astericks, the VE request works, but is repeated endlessly:
+
+{F203227}",1437479899,PHID-USER-wtbw6n3qdyre3vir7o3z,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"Yes, this is the API request that fails to find the image:
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+It results in: 
+
+```
+/**/jQuery1113038504008506424725_1437475882811({""batchcomplete"":""""})
+```
+
+If I add an astericks at the end of t he search-term, it works:
+
+
+```
+api.php?callback=jQuery1113038504008506424725_1437475882811&action=query&format=json&iiurlheight=200&generator=search&gsrnamespace=6&continue=&iiprop=dimensions%7Curl%7Cmediatype%7Cextmetadata%7Ctimestamp&prop=imageinfo&gsrsearch=Server*&iiurlwidth=300&gsroffset=0&gsrlimit=30
+```
+
+Results in:
+
+```
+/**/
+jQuery1113038504008506424725_1437475882811({
+    ""continue"": {
+        ""iistart"": ""2015-06-23T05:30:36Z"",
+        ""continue"": ""||""
+    },
+    ""query"": {
+        ""pages"": {
+            ""6672"": {
+                ""pageid"": 6672,
+                ""ns"": 6,
+                ""title"": ""Datei:Server\u00dcbersicht.png"",
+                ""index"": 1,
+                ""imagerepository"": ""local"",
+                ""imageinfo"": [{
+                    ""timestamp"": ""2015-06-23T05:31:57Z"",
+                    ""size"": 188839,
+                    ""width"": 3000,
+                    ""height"": 1606,
+                    ""thumburl"": ""http://10.248.8.1/wiki/images/thumb/6/6c/ServerÜbersicht.png/300px-ServerÜbersicht.png"",
+                    ""thumbwidth"": 300,
+                    ""thumbheight"": 161,
+                    ""url"": ""http://10.248.8.1/wiki/images/6/6c/ServerÜbersicht.png"",
+                    ""descriptionurl"": ""http://10.248.8.1/wiki/index.php/Datei:ServerÜbersicht.png"",
+                    ""extmetadata"": {
+                        ""DateTime"": {
+                            ""value"": ""2015-06-23T05:31:57Z"",
+                            ""source"": ""mediawiki-metadata"",
+                            ""hidden"": """"
+                        },
+                        ""ObjectName"": {
+                            ""value"": ""Server\u00dcbersicht"",
+                            ""source"": ""mediawiki-metadata"",
+                            ""hidden"": """"
+                        }
+                    },
+                    ""mediatype"": ""BITMAP""
+                }]
+            }
+        }
+    }
+})
+```
+
+When using the astericks, the VE request works, but is repeated endlessly:
+
+{F203227}",1437476343,PHID-USER-wtbw6n3qdyre3vir7o3z,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,Presumably some permission is missing. Can you post the exact API requests and responses?,1436560729,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,,1435749957,PHID-USER-wtbw6n3qdyre3vir7o3z,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,,1435734088,PHID-USER-wtbw6n3qdyre3vir7o3z,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"I've got the same problem (on a private wiki).
+
+I've tryed the permission fix. Still no effect on the first glance.
+
+However, If i type ""*"" or the complete name (including the namespace), it finds my image, if I type the only the name (or a part of the name) nothing appears.
+
+This seems to be an issue with the MediaWiki API. It's search algorithm is so strict, that you already need to know the exact name in order to get a result.
+
+Appending / prepending an astericks helps, though. Maybe VE should do that by default?
+
+VisualEditor-REL1_25
+MediaWiki	1.25.1
+PHP	5.5.9-1ubuntu4.9 (apache2handler)",1435750120,PHID-USER-wtbw6n3qdyre3vir7o3z,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"I've got the same problem (on a private wiki).
+
+Couldn't change that with the proposed permission fix.
+
+Interestingly, If i type ""*"", it finds my image, if I type the name (or part of the name) nothing appears.",1435733866,PHID-USER-wtbw6n3qdyre3vir7o3z,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"I still have the same problem in version 1.25wmf17 (d70b751)
+e.g. typing ""l"" shows only two images, adding an ""e"" shows only one, other(!) image.
+In order to find a file, I have to enter the complete name, including the extension :-( 
+Even worse, some files cannot be found at all. They can only be inserted using the text-editor.
+I cannot find the file ""At_venice.jpg"". The file appears as ""At_venice.jpg"" in the images-directory, but as ""At venice"" on the wiki-page describing the image.
+Anyway, I can't find the file Koala.jpg either, no spaces or underscores there :-( (but a capital letter...)
+
+Still the same issues as described earlier: I can find the file ""test_lego.jpg"" by typing ""test"", but not by typing ""lego"".
+
+It's getting better: I upload a file as ""jorun.jpg"" but cannot find it, unless by typing the complete name. I upload the same file as ""jorun test.jpg"". I can find this photo by typing 'jorun'.
+
+Still looks like a bug to me!
+",1426429220,PHID-USER-y4tnf7qjm6yk3pjxmhg2,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"In 1.25wmf8, it works now correctly without the (unsecure) workaround. I guess some other things with permissions were fixed which solved this one as a side effect too.",1416312559,PHID-USER-mn2oreq3jstq45jm3fp5,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"**gabriel_stelmach** wrote:
+
+Hello there,
+
+I just face this issue in my installation. There are any news about solution for this?
+
+In time. Thank you Stephan for the workaround.
+
+[]s",1414784948,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"(In reply to Bawolff (Brian Wolff) from comment #3)
+> Actually that can be exploited to get around read protection everywhere
+> (including normal web requests). Any url can have that string in it.
+
+Of course, and I don't recommend it. It was just meant as an indication that it's a bug in this specific api call for image searches and that other api calls are ok, so it's not a disabled api.",1397227191,PHID-USER-mn2oreq3jstq45jm3fp5,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"(In reply to Stephan Matthiesen from comment #2)
+> (In reply to Bawolff (Brian Wolff) from comment #1)
+> > Maybe private only wikis cause api to be disabled.
+> 
+> API is not disabled completely. All other API calls seem to work, only image
+> search is affected.
+> 
+> The following workaround in LocalSettings.php also works:
+> 
+> if ( strpos($_SERVER['REQUEST_URI'], ""prop=imageinfo"") > 0 ) {
+>     $wgGroupPermissions['*']['read'] = true;
+> }
+> 
+> This disables read protection selectively for the image search.
+
+Actually that can be exploited to get around read protection everywhere (including normal web requests). Any url can have that string in it.",1397226365,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,"(In reply to Bawolff (Brian Wolff) from comment #1)
+> Maybe private only wikis cause api to be disabled.
+
+API is not disabled completely. All other API calls seem to work, only image search is affected.
+
+The following workaround in LocalSettings.php also works:
+
+if ( strpos($_SERVER['REQUEST_URI'], ""prop=imageinfo"") > 0 ) {
+    $wgGroupPermissions['*']['read'] = true;
+}
+
+This disables read protection selectively for the image search.",1397222536,PHID-USER-mn2oreq3jstq45jm3fp5,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+Media selector doesn't find local media in private wiki,Maybe private only wikis cause api to be disabled.,1396214506,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-qlnckdanskw255gs5et4,task_subcomment,NA
+VisualEditor: Reference's highlight is misplaced if it appears after a references list block,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a Cite reference like Cite>Web/Book/Newspaper/Journal
+
+Observed Result:
+The selection highlight box is appearing a bit above the reference note
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12974}",1396046220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-twqcomuca3vkpbi4cgb7,task_description,resolved
+VisualEditor: Reference's highlight is misplaced if it appears after a references list block,"Yes, this looks like it was fixed a while ago.",1411403567,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-twqcomuca3vkpbi4cgb7,task_subcomment,NA
+VisualEditor: Reference's highlight is misplaced if it appears after a references list block,Is this still broken?,1404905022,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-twqcomuca3vkpbi4cgb7,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Guillemets, French quotation marks (https://en.wikipedia.org/wiki/International_variation_in_quotation_marks#French), are now available through the special characters tool in VE on fr.wiki.
+When you select a word and then add the guillemets in the wikitext editor, the word gets wrapped in them.
+This is not the case in VE - the symbols appear, the word gets deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396007580,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-2io5oqagajkj54tjjrwx,task_description,resolved
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Oh, great. I was wondering that quotation marks have disepeard with new charset.",1433205573,PHID-USER-vm462i2ffbawnuo4mh3n,True,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","The pairs of quotes appropriate for various languages can be inserted now (“” „“ „” «»), from the ""Symbols"" section, and if you do it while you have text selected, they will wrap it instead of replacing it.
+
+{F154006}
+
+If you wish to add items supporting this functionality to ""Often used"" characters list (https://www.mediawiki.org/wiki/VisualEditor/Special_characters#Adding_often_used_characters), the required syntax is (replace ""A"" and ""B"" with appropriate characters):
+
+```
+  ""AB"": {
+    ""action"": {
+      ""type"": ""encapsulate"",
+      ""options"": {
+        ""pre"": ""A"",
+        ""post"": ""B""
+      }
+    }
+  },
+```
+
+(Per https://www.mediawiki.org/wiki/MediaWiki_1.26/Roadmap, this change will be deployed on Wikipedias on Wednesday, 06 May 2015.)",1429770634,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Change 205558 merged by jenkins-bot:
+Allow special characters with tooltip or that encapsulate text
+
+[[https://gerrit.wikimedia.org/r/205558]]",1429750554,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Change 205556 merged by jenkins-bot:
+ve.ui.SpecialCharacterDialog: Allow encapsulation of selected content
+
+[[https://gerrit.wikimedia.org/r/205556]]",1429740887,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Change 205558 had a related patch set uploaded (by Bartosz Dziewoński):
+Allow special characters with tooltip or that encapsulate text
+
+[[https://gerrit.wikimedia.org/r/205558]]
+",1429608440,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","Change 205556 had a related patch set uploaded (by Bartosz Dziewoński):
+ve.ui.SpecialCharacterDialog: Allow encapsulation of selected content
+
+[[https://gerrit.wikimedia.org/r/205556]]
+",1429608420,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+"Quotation marks added via special characters tool should wrap selected text, not replace it","I confirm this at cs.wp. For the Czech „“ its common, to select a word click on spacial character button and insert quotatin marks arround.",1399013809,PHID-USER-vm462i2ffbawnuo4mh3n,True,PHID-TASK-2io5oqagajkj54tjjrwx,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with
+2,Add a bullet list or numbered list
+3.Add an empty bullet item 
+4.Add indentation to it
+5.Select the previous item
+6.Change the paragraph style of the previous item
+
+
+Observed Result:
+An error appears in the console
+Uncaught Error: Unbalanced set of replace operations found 
+
+Now press enter to add another item :
+Uncaught Error: Unbalanced input passed to document 
+
+Press undo:
+Uncaught Error: Offset could not be translated to a DOM element and offset
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/27thmarChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12902}",1395962100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gxhvf2p6374tnbqf755k,task_description,resolved
+VisualEditor: Changing format of a list item right above a nested list item breaks,Verified the fix in:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1397775053,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,Verified the fix on test 2,1397519641,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Change 124493 merged by jenkins-bot:
+Exclude insertions in ve.dm.SurfaceFragment#isolateAndUnwrap
+
+https://gerrit.wikimedia.org/r/124493",1397105117,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Change 123892 abandoned by Catrope:
+Adjust range manually in isolateAndUnwrap()
+
+Reason:
+Superseded by https://gerrit.wikimedia.org/r/#/c/124493/
+
+https://gerrit.wikimedia.org/r/123892",1396928035,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Change 124493 had a related patch set uploaded by Catrope:
+Exclude insertions in ve.dm.SurfaceFragment#isolateAndUnwrap
+
+https://gerrit.wikimedia.org/r/124493",1396912258,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"Change 123892 had a related patch set uploaded by Catrope:
+Adjust range manually in isolateAndUnwrap()
+
+https://gerrit.wikimedia.org/r/123892",1396634796,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,I've figured out why this bug happens and I know how to fix it. I have to go now but I'll write a patch when I get back (~1.5 hours),1396559050,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Changing format of a list item right above a nested list item breaks,"It suffices to do a format change on any list item that has a nested list item directly beneath it. In other words, if you have the list
+
+* Foo
+* Bar
+** Baz
+
+then changing ""Bar"" to a heading will break. It doesn't matter if ""Baz"" is empty, it just has to be at a deeper list level than ""Bar"".",1396558081,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gxhvf2p6374tnbqf755k,task_subcomment,NA
+VisualEditor: Link inspector icon appears after deleting the content of the page and closing the inspector causes an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 65,"Screenshot
+
+Steps to reproduce:
+
+1.Open this page: https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit
+
+2.Select all the content 
+
+3.Delete it.
+
+4.A link inspector icon appears in the page.
+
+5.Open the link inspector
+
+6.Close it 
+
+Observed Result:
+The links inspector gets all blank and an error appears in the console:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 65
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12901}",1395959940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ahuroh4hw3ltw7jphxcw,task_description,resolved
+VisualEditor: Link inspector icon appears after deleting the content of the page and closing the inspector causes an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 65,"Change 122556 merged by jenkins-bot:
+Fix handlesOwnChildren check in getRelativeOffset
+
+https://gerrit.wikimedia.org/r/122556",1396299546,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ahuroh4hw3ltw7jphxcw,task_subcomment,NA
+VisualEditor: Link inspector icon appears after deleting the content of the page and closing the inspector causes an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 65,"Change 122556 had a related patch set uploaded by Esanders:
+Fix handlesOwnChildren check in getRelativeOffset
+
+https://gerrit.wikimedia.org/r/122556",1396299373,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ahuroh4hw3ltw7jphxcw,task_subcomment,NA
+VisualEditor: Link inspector icon appears after deleting the content of the page and closing the inspector causes an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 65,"Deleting everything results in an empty document but for the internalList, i.e. [{'type':'internalList'...}, ...]. The popup tool is then look for annotations at range 0 which is then going inside the internal list and finding the link.",1396047717,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ahuroh4hw3ltw7jphxcw,task_subcomment,NA
+"VisualEditor: The link inspector opens after gallery , if there is gallery just after the text on which the link is getting applied","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a text
+3.Add a gallery right after that.
+4.Select the text by selecting whole line
+5.Click on the link inspector
+
+Observed Result:
+The link inspector opens after the gallery 
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/27thmarChrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12878}",1395952200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3nqxc32ajmzpi3hsotvq,task_description,resolved
+"VisualEditor: The link inspector opens after gallery , if there is gallery just after the text on which the link is getting applied",I /think/ Ed fixed this with his changes last fortnight. Maybe.,1402553191,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3nqxc32ajmzpi3hsotvq,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"Consequently to the success of VisualEditor on the French Wikipedia and Wikiversity, the French Wiktionary and Wikibooks have voted in favor of its utilization:
+
+https://fr.wiktionary.org/wiki/Wiktionnaire:Prise_de_d%C3%A9cision/Installation_de_l%27%C3%A9diteur_visuel
+
+https://fr.wikibooks.org/wiki/Wikilivres:Prise_de_d%C3%A9cision/Installation_de_l%27%C3%A9diteur_visuel
+
+So, thank you to deploy it on fr.wikt and fr.b please.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395927360,PHID-USER-dtdj4p6jtxbzs7trc3c6,False,PHID-TASK-nuycumir3hop5ekks7h2,task_description,resolved
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,This was done yesterday; sorry for not noting this then.,1396021903,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"Change 121439 merged by Mwalker:
+Enable VisualEditor by default on French Wiktionary & French Wikibooks
+
+https://gerrit.wikimedia.org/r/121439",1395961403,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"We will get this setting turned on this afternoon (Pacific time), in the usual deployment.",1395949344,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"Change 121439 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on French Wiktionary & French Wikibooks
+
+https://gerrit.wikimedia.org/r/121439",1395948955,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+Enable VisualEditor by default on French Wiktionary and French Wikibooks,"[Moving to ""Wikimedia"" product as this request is about settings / configuration of the website, not about the codebase of VisualEditor extension itself.]",1395928893,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-nuycumir3hop5ekks7h2,task_subcomment,NA
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Transclusion
+3.Insert a template for example : The Cite web
+4.Click on ""Show options""
+5.Keep on clicking on trash icon until you delete all the parameters and the template itself
+
+Observed Result:
+
+Observe that, even if there is no template in the dialog box , the add parameter button remains enabled , it should be disabled if there is o template.
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13393}",1395881520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3zamatwiubewzrfjcxeq,task_description,resolved
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,Verified the fix in production,1415226510,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3zamatwiubewzrfjcxeq,task_subcomment,NA
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,"Change 168379 merged by jenkins-bot:
+Disable parameter add icon when there's no transclusion parts
+
+https://gerrit.wikimedia.org/r/168379",1414442389,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3zamatwiubewzrfjcxeq,task_subcomment,NA
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,Confirmed in betalabs and test2.,1414439952,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3zamatwiubewzrfjcxeq,task_subcomment,NA
+VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box,"Change 168379 had a related patch set uploaded by Alex Monk:
+Disable parameter add icon when there's no transclusion parts
+
+https://gerrit.wikimedia.org/r/168379",1414090303,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3zamatwiubewzrfjcxeq,task_subcomment,NA
+BetaFeatures: Skin warning message pulls in skin names regardless of whether skin is available,"On beta features tab in your user preferences http://de.wikipedia.org/wiki/Spezial:Einstellungen?useskin=modern&uselang=de#mw-prefsection-betafeatures visualeditor shows a red requirement warning if the current skin is not supported. But this warning uses not available system messages:
+
+This feature only works with the following skins:
+    Vector
+    &lt;skinname-apex&gt;
+    MonoBook
+    &lt;skinname-minerva&gt; 
+
+The problem on wikimedia wikis is that both skins, apex and minerva, are not installed and so the system messages skinname-apex and skinname-minerva are missing.
+
+I think there are two options how to fix this bug:
+1. add these two messages to localisation files used by wmf
+2. test if a skin is available before adding it to the skin list of the warning message
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**URL**: http://de.wikipedia.org/wiki/Spezial:Einstellungen?useskin=modern#mw-input-wpvisualeditor-enable",1395871980,PHID-USER-rbcxdzszrm6s4izt67kj,False,PHID-TASK-p565vznerestdkazvkox,task_description,resolved
+BetaFeatures: Skin warning message pulls in skin names regardless of whether skin is available,"
+
+*** This bug has been marked as a duplicate of bug 58623 ***",1395898645,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-p565vznerestdkazvkox,task_subcomment,NA
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","I don't know what it should be, but the following is not very clear:
+
+Error loading data from server: error. Would you like to retry?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=39057
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43147",1395869100,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-yigtzgsn2qahxek7rusl,task_description,resolved
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","With the above patch, the former message:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500. Would you like to retry?
+
+… turns into:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500: Page Fetch failure for ""BADURL"": Error: getaddrinfo
+    ENOTFOUND. Would you like to retry?
+
+Which is not ideal, but at least describes things a bit. Marking this as FIXED.",1409684423,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yigtzgsn2qahxek7rusl,task_subcomment,NA
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","Change 157775 merged by jenkins-bot:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409681809,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yigtzgsn2qahxek7rusl,task_subcomment,NA
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","Change 157775 had a related patch set uploaded by Jforrester:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409669840,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yigtzgsn2qahxek7rusl,task_subcomment,NA
+"VisualEditor: When API returns HTTP 500, present a more useful error message to the user","(In reply to Roan Kattouw from comment #0)
+> I don't know what it should be, but the following is not very clear:
+> 
+> Error loading data from server: error. Would you like to retry?
+
+Maybe:
+
+| The editor's contact with the server failed (5xx). Would you like to retry?
+
+?",1395882419,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yigtzgsn2qahxek7rusl,task_subcomment,NA
+VisualEditor: Icons for citation tool don't all appear to be the same (visual) weight — the book icon looks darker than the others,"The icons for the new citation tool don't all appear to be the same weight.  The book icon looks darker than the others, which makes it seem like it's more important than other others, or perhaps that the others are non-functional/grayed out.  Perhaps it could be a dark gray?
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1395859980,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-tjsegrcnpxgmtmoqmaq2,task_description,resolved
+VisualEditor: Icons for citation tool don't all appear to be the same (visual) weight — the book icon looks darker than the others,Fixed with the new icons.,1401472252,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tjsegrcnpxgmtmoqmaq2,task_subcomment,NA
+VisualEditor:  Citation tool adds stray line break at the end of the template,"Intention:
+Add a citation with the new citing tool
+
+Steps to Reproduce:
+1. Add a citation.
+
+2. Look at the dirty diff that results.
+
+
+
+Actual Results:  
+The new cite tool produces this
+
+<ref>{{Cite web|url = http://example.com|title = Example Title|date = 2014|last = Expert|first = Alice}}
+</ref> 
+
+(on two lines) rather than one line that it should:
+
+<ref>{{Cite web|url = http://example.com|title = Example Title|date = 2014|last = Expert|first = Alice}}</ref> 
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395859560,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qp5fiwrkazudpv3vzwkc,task_description,resolved
+VisualEditor:  Citation tool adds stray line break at the end of the template,"This may possibly have been fixed? Seems to now work correctly (on one line) for me, see e.g. http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox&diff=92409&oldid=91378",1399336298,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qp5fiwrkazudpv3vzwkc,task_subcomment,NA
+VisualEditor:  Citation tool adds stray line break at the end of the template,"Do you have a link to an example diff? I'm trying to reproduce this locally but I can't, in neither Chrome nor Firefox.",1399333539,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-qp5fiwrkazudpv3vzwkc,task_subcomment,NA
+VisualEditor:  Citation tool adds stray line break at the end of the template,"That's not the meaning of the term ""dirty diff"". :-) But yes.",1395887579,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qp5fiwrkazudpv3vzwkc,task_subcomment,NA
+VisualEditor removes a colon from the first existing indented list item when adding another item to the list,"When adding an item to a list, VisualEditor is stripping the first indent (colon in wikisyntax) when adding a new one in the list.
+
+Example:
+https://www.mediawiki.org/w/index.php?title=User%3AKeegan_%28WMF%29%2Fsandbox&diff=939610&oldid=939609
+
+Steps to reproduce:
+1. Create an indented list, save
+   :*a
+   :*b
+   :*c
+2. Add a new item to the list, looks fine before saving
+   :*a
+   :*b
+   :*q
+   :*c
+3. Save, and the result is
+   *a
+   :*b
+   :*q
+   :*c
+
+Windows 7/Chrome 33.0.1750.154 m & Firefox 28.0
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1395768720,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-3egehmh4zidndvgzwfvm,task_description,resolved
+VisualEditor removes a colon from the first existing indented list item when adding another item to the list,The bug doesn't happen any more: https://en.wikipedia.beta.wmflabs.org/w/index.php?title=T65079&diff=499304&oldid=499303&diffmode=source,1625945177,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3egehmh4zidndvgzwfvm,task_subcomment,NA
+VisualEditor removes a colon from the first existing indented list item when adding another item to the list,...adding an item to *a bullet* list...,1395776546,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-3egehmh4zidndvgzwfvm,task_subcomment,NA
+VisualEditor: Long parameter names get hidden under their input fields,"This happen when you're editing a template, or, if you're just adding it instead, once you add the parameter as well.
+For example of very long names try to change Infobox settlement in https://en.wikipedia.org/wiki/Ames,_Iowa?veaction=edit .
+Since some of these parameters only differ at the very end, like Fram noted, the user can be confused when seeing what is apparently the same parameter just repeated. Some of them also lack a description, so the description alone wouldn't solve the problem.
+While he suggests that ""a pop-up that displays the full name may be some initial solution"", I think adjusting the character size or window size might work better.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395754800,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-o7phiemau5qvzpjncsca,task_description,resolved
+VisualEditor: Long parameter names get hidden under their input fields,We fixed this by making them not on the side but above.,1402553952,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-o7phiemau5qvzpjncsca,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"See reproduction below
+```
+[subbu@earth:~/work/wmf/parsoid] cat /tmp/wt
+[[Imagem:Ellipse PLS en.png|256px|thumb|Parâmetros de uma elipse.]]
+[subbu@earth:~/work/wmf/parsoid] php bin/parse.php --wt2wt < /tmp/wt
+[[Imagem:Ellipse PLS en.png|256px|thumb|Parâmetros de uma elipse.]]
+
+[subbu@earth:~/work/wmf/parsoid] php bin/parse.php --domain pt.wikibooks.org < /tmp/wt > /tmp/old.html
+[subbu@earth:~/work/wmf/parsoid] cp /tmp/old.html /tmp/new.html
+
+... edit new.html and change the image ...
+
+[subbu@earth:~/work/wmf/parsoid] php bin/parse.php --domain pt.wikibooks.org --html2wt < /tmp/new.html 
+[[Ficheiro:Ellipse_PLS_en.snv|256px|thumb|Parâmetros de uma elipse.]]
+```
+
+----------
+On this edit
+https://pt.wikibooks.org/wiki/Matem%C3%A1tica_elementar/Trigonometria/Arcos_e_%C3%A2ngulos?diff=270018
+VisualEditor replaced the good namespace ""Imagem"" by ""Ficheiro"", which is worse.
+The word ""Ficheiro"" is not appropriated here:
+* It is not used in the pt-BR variant, so per discussion in the community it should be avoided whenever it is possible[1][2]. And it is always possible to be avoid this word if the file is an image (because ""Imagem"" is a common word in pt-BR and pt-PT);
+* It replaced a precise description of the file by a generic one. There is nothing wrong in saying that ""Foo.PNG"" is a image.
+
+[1] https://pt.wikipedia.org/wiki/WP:Esplanada/propostas/Incentivar_o_uso_de_%22Imagem%22_em_vez_de_%22Arquivo%22_ou_%22Ficheiro%22_(12mar2011)
+[2] http://sourceforge.net/p/pywikipediabot/bugs/1323/
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395750540,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-orropflowqhqpd4oiqpd,task_description,open
+Parsoid should not replace namespace aliases by other translations,"Now I found the recently created and fixed {T237040}. Can we assume that after that change currently no automatic replacement happens, and that this issue can be closed, too, even if the original cause might have been different?",1572690784,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This happened in dewiki: https://de.wikipedia.org/w/index.php?title=Totengr%C3%A4ber_(K%C3%A4fer)&type=revision&diff=193594417&oldid=191699592
+And the funny thing is that some users can reproduce it, and some can't, and sometimes the behaviour just changes. When I tested a few days ago, VE/Parsoid changed every Bild (""Image"") to Datei (""File""), but when I tested again today, no such automatic changes occurred, even with the same edits in the same articles.",1572689086,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This is still happening:
+https://pt.wikipedia.org/w/index.php?diff=42819013
+https://pt.wikipedia.org/w/index.php?diff=42819531
+https://pt.wikipedia.org/w/index.php?diff=42819605
+https://pt.wikipedia.org/w/index.php?diff=42819868",1436464859,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This is still happening:
+https://pt.wikipedia.org/w/index.php?diff=42819013
+https://pt.wikipedia.org/w/index.php?diff=42819531
+https://pt.wikipedia.org/w/index.php?diff=42819605",1436462506,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This is still happening:
+https://pt.wikipedia.org/w/index.php?diff=42819013
+https://pt.wikipedia.org/w/index.php?diff=42819531",1436462430,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"This is still happening:
+https://pt.wikipedia.org/w/index.php?diff=42819013",1436459158,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,"https://pt.wikibooks.org/w/index.php?title=Matem%C3%A1tica_elementar/Trigonometria/Arcos_e_%C3%A2ngulos&oldid=264430&veaction=edit
+
+http://parsoid-lb.eqiad.wikimedia.org/_rt/ptwikibooks/Matem%C3%A1tica_elementar/Trigonometria/Arcos_e_%C3%A2ngulos?oldid=264430
+
+I tried a vedit on that version and ran rt on it, for good measure. The issue seems to be resolved but please reopen if I'm mistaken.",1416972936,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+Parsoid should not replace namespace aliases by other translations,Sorry for the slow triage here; I'm not sure if this is still an issue in Parsoid?,1411583056,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-orropflowqhqpd4oiqpd,task_subcomment,NA
+VisualEditor: Pressing delete on an indented list item does not unindent it rather merges it with the previous item in a numbered list,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add a numbered or bullet list
+3.Edit the first item of the list
+4.Add indentation to it
+5.Place the cursor just before the list
+6.Press delete
+
+Observed Result:
+Instead of unindenting it, it rather merges it with the previous line .
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page: https://test2.wikipedia.org/wiki/24thmarchrome?veaction=edit
+
+**See Also**: {T63863}",1395707640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-k5farhnvyfzzpgjvizgv,task_description,open
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"screenshot 1
+
+Steps to reproduce:
+
+1.Go to the media settings of an image
+2.Create a slug 
+3.Try to insert a special character/link/reference in the slug
+
+
+Observed Result:
+
+It shows an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 63
+Also if it is an inspector it goes all blank
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13082}",1395688860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_description,resolved
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,Verified the fix in production,1414101150,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,Verified the fix in test2,1413504401,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,This is now fixed with latest slug work I guess.,1413415239,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,Huh. Darn.,1412807923,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"Nope, this bug must have a different cause because it occurs in test2 and production as well.",1412806887,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"That was bug 71825, now fixed.",1412799442,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"This issue has resurfaced with error as ""Uncaught Error: offset -1 out of bounds"" when trying to insert a link/special character in a slug.",1412789418,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,I believe/hope this is now fixed…,1401475904,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,Try the first image on this page:http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome?veaction=edit,1395689025,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63,"Created attachment 14893
+screenshot 2
+
+**Attached**: {F13083}",1395688906,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xkubjhuxj6ibkrx7jfgp,task_subcomment,NA
+VisualEditor: Gallery code gets added in the Table of Content and gets overlapped with the next item in the VE mode,"Screenshot
+
+Steps to reproduce:]
+
+
+1.Open a page with VE
+2.Select the whole line just preceding a Heading
+3.Insert a gallery with some invalid code: for example:
+
+
+An example image. It has flowers and flowers It has flowers and flowersIt has flowers and flowersIt has flowers and flowersIt has flowers and flowersIt has flowers and flowers
+
+
+Observed Result:
+1. The text inside gallery inspector gets overlapped with the heading 
+2. After saving you will see the gallery code got inserted in the TOC 
+3.The heading got converted to paragraph format
+4.The gallery code is appearing just beside the heading in paragraph format ( in addition to appearing inside the gallery)
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Newpagetocheck62934
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12890}",1395444300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gchq7jmbvglbydxeihay,task_description,open
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"For example, action=visualeditor is an internal API for the VisualEditor client to talk to its server, isn't really useful for third parties, and isn't remotely stable. However, because it's a built-in assumption that APIs are for third-party use rather than every tool being the first client of its API, this isn't possible. Boo.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1395361800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_description,resolved
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 1010987 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] api: Tweak the 'internal' API label to explain that they shouldn't be used%%%
+https://gerrit.wikimedia.org/r/1010987",1710453188,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 1010987 had a related patch set uploaded (by Jforrester; author: Jforrester):
+%%%[mediawiki/core@master] api: Tweak the 'internal' API label to explain that they shouldn't be used%%%
+https://gerrit.wikimedia.org/r/1010987",1710367202,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 160798 merged by jenkins-bot:
+API: HTMLize and internationalize the help, add Special:ApiHelp
+
+https://gerrit.wikimedia.org/r/160798",1413238801,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,Taken over by Brad.,1412969071,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 158546 abandoned by Legoktm:
+API: Implement concept of 'internal' API modules
+
+Reason:
+Superseded by Ib14c00df06d85c2f6364d83b2b10ce34c7f513cc
+
+https://gerrit.wikimedia.org/r/158546",1412929000,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 160798 had a related patch set uploaded by Anomie:
+API: HTMLize and internationalize the help, add Special:ApiHelp
+
+https://gerrit.wikimedia.org/r/160798",1410895615,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Change 158546 had a related patch set uploaded by Alex Monk:
+Make it possible for API modules to hide their documentation behind an 'includeinternal' parameter
+
+https://gerrit.wikimedia.org/r/158546",1409874405,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"(In reply to Brad Jorsch from comment #2)
+> (In reply to James Forrester from comment #0)
+> > For example, action=visualeditor is an internal API for the VisualEditor
+> > client to talk to its server, isn't really useful for third parties, and
+> > isn't remotely stable. However, because it's a built-in assumption that APIs
+> > are for third-party use rather than every tool being the first client of its
+> > API, this isn't possible. Boo.
+> 
+> Ideally a tool's API would be perfectly usable by third parties, not
+> something overly specific to the one tool's internal implementation,
+> although that may not always be possible. I don't know which is the case for
+> VE's API or if it's just that it's not yet stable.
+
+Completely agreed in the general case that we should encourage tools to create APIs that are useful for third parties. VE, as an exclusive consumer of APIs, comes up against the problem of the existing APIs in MW and extensions not actually providing the necessary features — we're well aware of how bad this is in some areas! My view is that all tools, core and otherwise, should be expected to be the first client of their own, normally public API rather than magically and silently reach into the codebase to make changes that other tools cannot (EditPage.php, I'm looking at you).
+
+With VE's API, it's a combination of:
+
+* not yet sufficiently stable (new features and formats being added each week or so),
+* not a long-term prospect (this exists mostly to code around a lack of genericness in MW, and eventually we'll fix that rather than keep this), and
+* not being a 'real' API (much of the content of the API is available from other API calls, but having a single call improves efficiency for VE's client).
+
+As an illustrated example, see this change made this week to VE's API to add hinting to links that don't exist (so VE can add red colouring): https://gerrit.wikimedia.org/r/#/c/118045/14/ApiVisualEditor.php
+
+This:
+* changed just yesterday,
+* is intended to be replaced reasonably soon with a proper Parsoid post-processor to sit in front of the HTML+RDFa cache for making changes that are currently parser cache-busting like this, and
+* is trivially something that can be provided by the pre-existing public APIs.",1395413828,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,"Brainstorming:
+
+Add a method, something like ""isInternalApi"", to ApiBase that by default returns false.
+
+Add a boolean ""includeinternal"" parameter to ApiHelp, which when specified would include these internal API modules.
+
+Adjust ApiBase::makeHelpMsg() to take a boolean indicating whether internal API modules should be shown (i.e. whether ""includeinternal"" was given to action=help).
+
+Then ApiHelp::execute(), if not passed a ""modules"" parameter explicitly, would check the flag and isInternalApi() to decide whether to include each module in the output. Modules like ApiQuery that have submodules would use the new parameter to their ::makeHelpMsg() methods to do the same.
+
+The help output should also include indication of whether a module is internal, much like it now does for stuff like ""This module only accepts POST requests"".
+
+I'm not sure whether we should also try to adjust the output of getAllowedParams() to omit these internal modules from the valid values for ""action"", or if that would be too expensive for too little gain (if we did do that, we'd need to do like how ApiPageSet handles generators). We certainly should be sure not to omit the internal modules for action=paraminfo though.
+
+
+(In reply to James Forrester from comment #0)
+> For example, action=visualeditor is an internal API for the VisualEditor
+> client to talk to its server, isn't really useful for third parties, and
+> isn't remotely stable. However, because it's a built-in assumption that APIs
+> are for third-party use rather than every tool being the first client of its
+> API, this isn't possible. Boo.
+
+Ideally a tool's API would be perfectly usable by third parties, not something overly specific to the one tool's internal implementation, although that may not always be possible. I don't know which is the case for VE's API or if it's just that it's not yet stable.",1395410558,PHID-USER-uqcn2l4ng4murmyfnvyp,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output,Maybe we should have not deprecated the ajax interface.,1395363976,PHID-USER-dpu5hmqvprhycqlkdzrk,True,PHID-TASK-dsoezmplcqkvtg5il36e,task_subcomment,NA
+VisualEditor: Image flickers but shield stays in the correct position while dragging the page on Mac,"Steps to reproduce:
+
+If you drag a page down which contains an image large enough to go beyond the border of developer tool and has the developer tool open ,the image seems to flicker and appear again while the shield stays in the same position.
+
+Try this page.
+See the Video Capture attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395359220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2zikzspgdiyrdhq43hy6,task_description,resolved
+VisualEditor: Image flickers but shield stays in the correct position while dragging the page on Mac,"Yes, this is not happening anymore",1404855686,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2zikzspgdiyrdhq43hy6,task_subcomment,NA
+VisualEditor: Image flickers but shield stays in the correct position while dragging the page on Mac,I think this is now working.,1404851230,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2zikzspgdiyrdhq43hy6,task_subcomment,NA
+VisualEditor: Image flickers but shield stays in the correct position while dragging the page on Mac,Page:https://test2.wikipedia.org/wiki/Wmf19?veaction=edit,1395359277,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2zikzspgdiyrdhq43hy6,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a small default sized SVG image for example a SVG image with 50x50px :https://en.wikipedia.org/wiki/File:Gnome-fs-home.svg
+
+3.Now Save the page
+
+Observed Result:
+The image size that appears after saving is much larger (200x200px) 
+
+See the screenshot attached.
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13403}",1395351720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_description,resolved
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,Verified the fix in en.wiki running wmf 8,1402687864,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"Change 137442 merged by jenkins-bot:
+Followup to small SVG default size
+
+https://gerrit.wikimedia.org/r/137442",1401925466,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"Change 137442 had a related patch set uploaded by Mooeypoo:
+Followup to small SVG default size
+
+https://gerrit.wikimedia.org/r/137442",1401911708,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"Change 137054 merged by jenkins-bot:
+Small SVG images should still adhere to default thumb size
+
+https://gerrit.wikimedia.org/r/137054",1401903798,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+VisualEditor: Small default sized SVG images behave differently than small default sized PNG images,"Change 137054 had a related patch set uploaded by Mooeypoo:
+Small SVG images should still adhere to default thumb size
+
+https://gerrit.wikimedia.org/r/137054",1401817797,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nxxo6xoo5y7bzqx6ntg5,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Since Parsoid already runs an API call for each image given to it in wikitext, it would be extremely helpful for the editing in terms of user experience if the call also asked for the original dimensions.
+
+At the moment, VisualEditor asks for details from the API on each edited image to get its original dimensions. When this is done for the edit dialog the asynchronous call works fine because we don't mind letting the user wait the seconds it takes the async call to finish.
+
+But when the user resizes images with the mouse (with the resize handles) the information about original dimensions usually comes too late. The user may (and often does) resize the image to above its limits, and by the time VE gets the API response, the user is already done resizing. On top of that, calculating aspect ratio from original size is a lot more accurate than calculating it from the given (usually smaller) size, though, granted, this is a lot less crucial.
+
+We have some fall backs and we are considering an after-the-fact user experience ideas to make this work, but it would be extremely helpful if the information was already available when it comes from Parsoid -- especially since Parsoid already asks for information from the API.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395339300,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_description,resolved
+Make available original image dimensions info from the API in Parsoid DOM.,"Disregard, this was already closed",1436986700,PHID-USER-6vqtwycrvuonr2xo7bqi,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Chiming in from iOS, we'd love to know the current thumbnail and original size so we can handle scaling up to higher resolutions elegantly.  Is it worth making which properties to include configurable?  Maybe some clients don't want it, maybe some do?",1436986671,PHID-USER-6vqtwycrvuonr2xo7bqi,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"@esanders, @jdforrester-WMF: perhaps you VE guys should add one?  I think @mooeypoo was doing the original work here (a year ago!).",1428078595,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,Is there a task for VE to use this now?,1428062303,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"This will go out on Monday. Roan confirmed that there are no VE changes that are required. Also for a while, VE should be prepared to accept HTML with / without these attributes till all the revisions turn over in RESTBase.",1427414195,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Change 195666 merged by jenkins-bot:
+T64881: Add original dimension information for images.
+
+[[https://gerrit.wikimedia.org/r/195666]]",1427413837,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Change 195798 abandoned by Cscott:
+T64881: Add original dimension information for images to data-mw.
+
+Reason:
+Abandoned in favor of https://gerrit.wikimedia.org/r/195666
+
+[[https://gerrit.wikimedia.org/r/195798]]",1427406846,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,Should missing/error images have `data-file-width`/`data-file-height` attributes?  Right now I'm not adding them.,1427403950,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Restating subbu's (b) slightly, for more accuracy: Mediaviewer already adds it (to PHP parser output), and so other gadgets might expect it.",1426606626,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Summary of IRC conversation:
+
+So, if we had to add this info, it makes sense to add data-file-width and data-file-height attributes because (a) it is read only (b) mediaviewer and other gadgets already expect it and when Parsoid html is used for read views, those applications don't break suddenly (c) most pages have few images relative to the size of the DOM itself, so the DOM bloat is expected to be minor.
+
+Parsoid is probably already handling HTML invalidation (via parsoid cache update jobs, to be confirmed for sure) and so there are no new cache invalidation issues that crop up from this change.",1426544643,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Change 195798 had a related patch set uploaded (by Cscott):
+T64881: Add original dimension information for images to data-mw.
+
+[[https://gerrit.wikimedia.org/r/195798]]
+",1426029924,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Uploaded a patch ^ which uses `data-file-width` and `data-file-height` to match the PHP HTML output created by the MediaViewer extension.
+
+Perhaps this bloats the DOM, and we should use data-mw instead.  I don't have a strong opinion here.  My hand-wavy argument is that data-mw should be used for properties which are important/signficiant for editors in terms of defining a particular wikitext serialization.  These new `data-file-*` properties are not consulted for WTS, they are just ignored.
+
+(But perhaps we should consult these in order to serialize upright images correctly?)",1426020950,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"Change 195666 had a related patch set uploaded (by Cscott):
+T64881: Add original dimension information for images.
+
+[[https://gerrit.wikimedia.org/r/195666]]
+",1426020749,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"What do we want to happen if the target image doesn't exist?  Presumably leave off the attributes, right?",1426020101,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,That comes from Multimedia Viewer or some such.,1424981710,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,Mediawiki core seems to use `data-file-width` and `data-file-height` on `<img>` tags for this.  I wonder when that was added to core?,1424981266,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,Per conversations last week this should be reprioritised.,1423251809,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"The size concern also matters less once we move data-mw out of the DOM. There's still the minor nuisance of having some read-only attributes in data-mw, which is otherwise a read-write interface.
+
+Maybe it would make sense to group dimensions & image type in a separate 'imageinfo' sub-object inside data-mw that is documented to be read-only. The grouping & naming should make it clearer that this is read-only info only, even without looking at the docs.",1402005070,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"On top of the dimensions, it would also be helpful to get the 'mediatype' property of images, separating them between ""DRAWING"" and ""BITMAP"". The two types behave differently, especially with size considerations.
+
+It is useful for VE to know (we request this now with our separate api call) but it might actually make sense to categorize the difference between the images for other purposes.",1401926981,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"We have a new strategy for serializing square bounding boxes that will be helped by having original image size hanging around, so we will probably put original image size in data-mw.",1396301812,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"I do agree we should be careful, but I think this is worth including. It's really useful and costs very little.",1395342449,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"(In reply to C. Scott Ananian from comment #1)
+> I'm not convinced we should be bloating our Parsoid DOM representation with
+> original size information which can easily be obtained from the imageinfo
+> API.  In order to do a proper resize, you are probably going to have to
+> fetch the original image anyway so that things don't get blurry when you
+> scale up.
+> 
+> But I'm interesting in hearing other thoughts.
+
+We don't fetch the original image unless the new size is the image's original dimensions – we ask MW for the thumbnail of that size. We certainly don't ask e.g. for a 10MiB original 5000x4000px image when the user is just resizing from 250x200px to 300x240px. Also, we fetch the new image /after/ the image is resized.",1395341768,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+Make available original image dimensions info from the API in Parsoid DOM.,"I'm not convinced we should be bloating our Parsoid DOM representation with original size information which can easily be obtained from the imageinfo API.  In order to do a proper resize, you are probably going to have to fetch the original image anyway so that things don't get blurry when you scale up.
+
+But I'm interesting in hearing other thoughts.",1395339892,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-hzbsw24557jvqnw3xxby,task_subcomment,NA
+VisualEditor: Save dialog animates size while animating open if it was large when it was closed,"1. Open save dialog. It animates normally to small size.
+2. Click Review changes. Dialog animates to medium size.
+3. Close dialog.
+4. Open dialog again.
+
+When the dialog opens again, it's still medium size from last time, which we animate back to small. But this animation is concurrent with the scale 0.5->1.0 opening animation, and the result of the two animations combined is pretty strange-looking.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395279120,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-25trlvhkq536lvbbruzl,task_description,resolved
+VisualEditor: Save dialog animates size while animating open if it was large when it was closed,Verified the fix in production (en.wiki),1403561072,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-25trlvhkq536lvbbruzl,task_subcomment,NA
+VisualEditor: Save dialog animates size while animating open if it was large when it was closed,Yay Trevor. :-),1402551181,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-25trlvhkq536lvbbruzl,task_subcomment,NA
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,"screenshot-1
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image 
+3.Go to Media Settings>General Settings 
+4.Click outside the caption textbox
+5.Click on link inspector icon
+
+Observed Result:
+The link inspector opens outside the textbox.
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13306}",1395274860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vggdfu44niwggkew2ust,task_description,resolved
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,Verified the fix in production (en.wiki),1403301925,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vggdfu44niwggkew2ust,task_subcomment,NA
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,Verified the fix in test2 running wmf9,1402692374,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vggdfu44niwggkew2ust,task_subcomment,NA
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,I believe that this one is now fixed courtesy of Ed's changes this week or last.,1402549198,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vggdfu44niwggkew2ust,task_subcomment,NA
+VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog,"Created attachment 14866
+screenshot
+
+**Attached**: {F13307}",1395274955,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vggdfu44niwggkew2ust,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","Steps to reproduce:
+
+1.Open a page with VE
+2.Now change the image settings to Right,Basic and Border 
+3.Save the page
+
+Observed Result:
+In the wikitext the options ""Right"" and ""Border"" are missing
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395266640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_description,resolved
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext",Verified the fix in test2,1401498423,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext",Verified the fix in Betalabs,1401311647,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext",Skipping right (and just using default) is OK for thumb and frame (but not frameless or basic).,1400630689,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","So, this is still happening.In addition to that, for all Right aligned Images regardless of its type the alignment options gets missing from the wikitext",1400629615,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","CE responds correctly to the type and alignment shifts, and yet something seems to goes awry in the DM. I'm checking into the issue.",1395339648,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","Parsoid does the right thing with the input giving the expected output:
+
+<figure class=""mw-default-size mw-halign-right mw-image-border"" typeof=""mw:Image"" data-parsoid=""{&quot;optList&quot;:[{&quot;ck&quot;:&quot;thumbnail&quot;,&quot;ak&quot;:&quot;thumb&quot;},{&quot;ck&quot;:&quot;left&quot;,&quot;ak&quot;:&quot;left&quot;},{&quot;ck&quot;:&quot;caption&quot;,&quot;ak&quot;:&quot;Foo&quot;}],&quot;dsr&quot;:[0,35,2,2]}""><a href=""./File:Example.png"" data-parsoid=""{&quot;a&quot;:{&quot;href&quot;:&quot;./File:Example.png&quot;},&quot;dsr&quot;:[2,null,null,null]}""><img resource=""./File:Example.png"" src=""//upload.wikimedia.org/wikipedia/en/thumb/7/70/Example.png/220px-Example.png"" height=""238"" width=""220"" data-parsoid=""{&quot;a&quot;:{&quot;resource&quot;:&quot;./File:Example.png&quot;,&quot;height&quot;:&quot;238&quot;,&quot;width&quot;:&quot;220&quot;},&quot;sa&quot;:{&quot;resource&quot;:&quot;File:Example.png&quot;}}""></a><figcaption data-parsoid=""{&quot;dsr&quot;:[null,33,null,null]}"">Foo</figcaption></figure>
+
+->
+
+[[File:Example.png|Foo|right|border]]",1395266959,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext","Created attachment 14864
+Screenshot
+
+**Attached**: {F13291}",1395266767,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5sy4lbhaku6tjpejlwmy,task_subcomment,NA
+"VisualEditor: Centre floated image next to right floated image means image is shown partially offscreen, and shield is put in the wrong place","Screenshot
+
+Steps to reproduce:
+
+This issue was found specifically on this page for the second image:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/19thMarChrome?veaction=edit
+
+The original settings for the image was Right,Basic and Border.
+
+When I changed the image position to ""Centre"", it appeared distorted with irregular highlight box for the image
+
+See the screenshot attached:
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62590
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66228
+
+**Attached**: {F13287}",1395265200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-py5gbrzeyuwgfnhmvab3,task_description,open
+"VisualEditor: Centre floated image next to right floated image means image is shown partially offscreen, and shield is put in the wrong place","No, definitely still happening.
+
+Issue seems to be that the centre-floated image is moved down by the lack of space to below the right-floated image, but the document's length is not extended (so it runs off the edge of the window) and the shield remains in place (so you can click on the image and go to the File: page)…",1401312865,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-py5gbrzeyuwgfnhmvab3,task_subcomment,NA
+"VisualEditor: Centre floated image next to right floated image means image is shown partially offscreen, and shield is put in the wrong place",This should be fixed now.,1401312083,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-py5gbrzeyuwgfnhmvab3,task_subcomment,NA
+"VisualEditor: Centre floated image next to right floated image means image is shown partially offscreen, and shield is put in the wrong place",This doesn't happen when the image is by itself on the page (or inside a bunch of paragraphs) so I am pretty sure this is due to the fact the image is within two PRE tags.,1395339578,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-py5gbrzeyuwgfnhmvab3,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Right now, MWLinkInspector needs to know exactly how to construct a new link annotation with the right attributes. This pattern is repeated (albeit somewhat less egregiously) for every single annotation and node created by any UI component anywhere. This is horrible. The DM should provide helpers so UI classes can much more easily create linmod elements from data.
+
+----
+
+Update, 2015-08-25: We now have a bespoke method for the MW link inspector, but the general pattern across VE's UI is still there.",1395194460,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-25agkmu2ndsyxxwmvqos,task_description,open
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Change 233727 merged by jenkins-bot:
+Use new internal link builder
+
+[[https://gerrit.wikimedia.org/r/233727]]",1440518475,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Change 233727 had a related patch set uploaded (by Esanders):
+Use new internal link builder
+
+[[https://gerrit.wikimedia.org/r/233727]]
+",1440517877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Change 231155 merged by jenkins-bot:
+Builder for ve.dm.MWInternalLinkAnnotation
+
+[[https://gerrit.wikimedia.org/r/231155]]",1440176289,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"From IRC:
+> James_F: RoanKattouw says that for T64816 something that every UI tool can call (name not really thought of; #constructMe() or whatever) was what he was thinking.
+
+The patch in https://gerrit.wikimedia.org/r/231155 is just a tiny start, it makes it a little easier to construct correct `ve.dm.MWInternalLinkAnnotation` objects given a `mw.Title`.  It doesn't address the bigger picture, since I don't really have  a solid grasp on the bigger picture.",1439486649,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Create infrastructure for creating annotations/nodes from the UI,"Change 231155 had a related patch set uploaded (by Cscott):
+Builder for ve.dm.MWInternalLinkAnnotation
+
+[[https://gerrit.wikimedia.org/r/231155]]
+",1439414684,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-25agkmu2ndsyxxwmvqos,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"Duplicated logic is bad.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395179580,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_description,resolved
+VisualEditor: Extract red link API code from VE and put into Parsoid,"So I verified that the correct color is showing up for different kinds of links. Regarding the API requests, I am not sure which ones I should consider as ""additional"". I have moved this task to Engineering QA if that's a better suited task for engineers. 
+>>! In T64803#4976829, @Esanders wrote:
+> QA: Check that links are still the correct colours, and that additional API requests aren't being fired when initialising the page.
+
+",1553195405,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"Change 492358 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ApiVisualEditor: Remove red-link cache warming
+
+[[https://gerrit.wikimedia.org/r/492358]]",1550918218,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"QA: Check that links are still the correct colours, and that additional API requests aren't being fired when initialising the page.",1550862234,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"Change 492358 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] ApiVisualEditor: Remove red-link cache warming
+
+[[https://gerrit.wikimedia.org/r/492358]]",1550858154,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,">>! In T64803#3380142, @Esanders wrote:
+> Red link code is now in Parsoid so can be removed from VE
+
+Will need us to round-trip new links, though. Right now we pick how to render them with local code which is pretty speedy.",1498651711,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,Red link code is now in Parsoid so can be removed from VE,1498503516,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"(In reply to Gabriel Wicke from comment #2)
+> For static pages we should be able to do this with CSS retrieved from an
+> API. We'll provide this API for normal pages.
+
+*nods*
+
+
+> For dynamic hints during editing we'd still need to inject styles
+> dynamically. The latter would probably remain VE-specific.
+
+Yeah, but Flow/etc. may want to style too.",1411609546,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"For static pages we should be able to do this with CSS retrieved from an API. We'll provide this API for normal pages.
+
+For dynamic hints during editing we'd still need to inject styles dynamically. The latter would probably remain VE-specific.",1411608588,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Extract red link API code from VE and put into Parsoid,"(In Parsoid or whatever; the point is, this code should be re-useable by Flow, OCG and anyone else rather than buried inside VE.)",1411594065,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4cyyyuqcl5m5zuvtdeym,task_subcomment,NA
+VisualEditor: Slugs don't animate when jumping from one to another,"1. Create a page with just a table
+2. Focus the top slug (it animates)
+3. Focus the bottom slug
+
+Expected:
+Top slug collapses, bottom slug expands
+
+Observed:
+Nothing
+
+The logic for adding animation classes only checks to see if we've gone from in a slug to not in a slug, so we'll need to check if the slug has changed as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395150300,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-l2jl4edzrpyacaksfsyv,task_description,resolved
+VisualEditor: Slugs don't animate when jumping from one to another,"Change 119287 merged by jenkins-bot:
+Check if newly focused slug is different to previous slug
+
+https://gerrit.wikimedia.org/r/119287",1395164477,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l2jl4edzrpyacaksfsyv,task_subcomment,NA
+VisualEditor: Slugs don't animate when jumping from one to another,"Change 119287 had a related patch set uploaded by Esanders:
+Check if newly focused slug is different to previous slug
+
+https://gerrit.wikimedia.org/r/119287",1395150372,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l2jl4edzrpyacaksfsyv,task_subcomment,NA
+VisualEditor: The Save dialog box prompts to fill out a new captcha if a user goes to review changes section and switches back after filling out the captcha field for the first time,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an external link in the VE so that it prompts to enter a captcha 
+3.Click on the Save Page button
+4.Click on the Save Page button on the Save dialog
+5.Fill up the textbox for the captcha
+6.Click on ""Review Your Changes""
+7.Return to the save form
+
+
+Observed Result:
+It again asks you to fill up a new captcha
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395106620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jvt3xyvqjt3cysi2vihe,task_description,resolved
+VisualEditor: The Save dialog box prompts to fill out a new captcha if a user goes to review changes section and switches back after filling out the captcha field for the first time,Verified the fix in Betalabs,1398894727,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jvt3xyvqjt3cysi2vihe,task_subcomment,NA
+VisualEditor: The Save dialog box prompts to fill out a new captcha if a user goes to review changes section and switches back after filling out the captcha field for the first time,"Change 129830 merged by jenkins-bot:
+Call clearAllMessages in setup instead of swapPanel on the save dialog
+
+https://gerrit.wikimedia.org/r/129830",1398881956,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jvt3xyvqjt3cysi2vihe,task_subcomment,NA
+VisualEditor: The Save dialog box prompts to fill out a new captcha if a user goes to review changes section and switches back after filling out the captcha field for the first time,"Change 129830 had a related patch set uploaded by Alex Monk:
+Call clearAllMessages in setup instead of swapPanel on the save dialog
+
+https://gerrit.wikimedia.org/r/129830",1398462405,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jvt3xyvqjt3cysi2vihe,task_subcomment,NA
+Improve VisualEditor's performance on tablet devices,"Kenan reports some sluggishness on iPads, and will update this bug with more details.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395094920,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-bsy6cd23dxzzu4de3gqm,task_description,invalid
+Improve VisualEditor's performance on tablet devices,"General ""improve performance of X"" tasks are not actionable in the absence of specific acceptance criteria, so this isn't really a valid task. ",1534438142,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-bsy6cd23dxzzu4de3gqm,task_subcomment,NA
+Improve VisualEditor's performance on tablet devices,Not actionable as a task; this is a tracker.,1428521843,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bsy6cd23dxzzu4de3gqm,task_subcomment,NA
+Improve VisualEditor's performance on tablet devices,Is this a bug or a tracker?,1395095390,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bsy6cd23dxzzu4de3gqm,task_subcomment,NA
+VisualEditor: Provide a clean interface for rendering detached CE nodes,"In ve.ce.MWTreferenceListNode we do something quite evil, which is creating a one-off CE node, adding it's $element to the DOM, then destroying it. This happens to work because destroy doesn't abort async rendering processes, but in the future this may change. It's also quite messy to do things this way, and all we really need is a simple way to get a rendering from a model.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394842740,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-xgahiq6goif4ltykeqno,task_description,resolved
+VisualEditor: Provide a clean interface for rendering detached CE nodes,ve.ui.PreviewElement probably fits the bill here. See T94130 (which might have been a duplicate of this).,1580721921,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xgahiq6goif4ltykeqno,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add a caption to it
+3.Save the page 
+4.Reopen the page
+5.Go to the Media Settings of that image and change the image type to thumbnail/frame
+
+
+Observed Result:
+The image highlight box does not appear properly, caption also gets missing
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/14thmarchwmf18
+
+Try the image in this page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64563
+
+**Attached**: {F12893}",1394842020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_description,resolved
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"(In reply to ryasmeen from comment #7)
+> Created attachment 15871 [details]
+> Screenshot
+> 
+> Making an image frame-right or frame-left makes the highlight of the image
+> too big to go beyond the CE, not sure if this should be tagged with this bug
+> or not.
+> 
+> See the screenshot attached
+
+I think that's a distinct issue. :-(
+
+**Attached**: {F12897}",1404864095,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,bug* not bag :|,1404860275,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Created attachment 15871
+Screenshot
+
+Making an image frame-right or frame-left makes the highlight of the image too big to go beyond the CE, not sure if this should be tagged with this bag or not.
+
+See the screenshot attached
+
+**Attached**: {F12897}",1404860239,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,This now appears to be working fine?,1404851133,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Edited wrong bug, ignore change 137040 and above comment.",1402923170,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Issue is with dm selection, not shields/highlights.",1402923055,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Change 137040 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE (ish)] Track orignal data position in insertion operations
+
+https://gerrit.wikimedia.org/r/137040",1402922995,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,This issue did not get resolved with new image model.,1400199678,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame,"Created attachment 15299
+Screenshot april 5th
+
+**Attached**: {F12895}",1399317964,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-p4piwpm2qv7ndud2jr4x,task_subcomment,NA
+VisualEditor: Make CE-surface fixes to make TMH's media items display correctly,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394835240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5s7zqldna73gv3hkyshd,task_description,resolved
+VisualEditor: Make CE-surface fixes to make TMH's media items display correctly,"For the most part, this seems to have been done, sometime between 2014 and now. CE nodes for video and audio files render sensibly. 
+
+{F26280466}
+
+```
+[[File:A.png|thumb|200px|Test]]
+[[File:B.webm|thumb|200px|Test]]
+[[File:C.ogg|thumb|200px|Test]]
+
+[[File:A.png|200px|Test]]
+
+[[File:B.webm|200px|Test]]
+
+[[File:C.ogg|200px|Test]]
+```
+
+I've just filed T206022 about the obvious issue with audio thumbnails (before finding this task), so I'll just close this one, since everything else it would cover seems to be resolved.",1538513853,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-5s7zqldna73gv3hkyshd,task_subcomment,NA
+VisualEditor: Be able to set a non-image multi-paged item's display page (page=) in the media dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rmisq2mh4lmql7yzicx6,task_description,open
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"Moved out of bug T40129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_description,open
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"My personal experience is that, as a newer editor, I edited ~30 articles using the visual editor before I realized that this was happening. It seems like a straight-forward upgrade to the visual editor. By the way, I went back and modified those 30 edited articles using ""upright"". I have since noticed many articles with specific ""px"" instead of upright and manually fix those myself; so this seems to be a fairly widespread problem.",1678751805,PHID-USER-l3sssyst6wh7vey2cxpl,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,">>! In T64671#7549236, @kostajh wrote:
+>>>! In T64671#1644967, @cscott wrote:
+>> The `upright` option suffers from some severe problems.  Consensus was reached on replacing it, see https://www.mediawiki.org/wiki/Requests_for_comment/Square_bounding_boxes  -- unfortunately, the replacement agreed upon had to be reverted due to some unexpected interactions with page layout.  We need to revisit the RFC and select one of the other proposed options for implementation.
+>> 
+>> But at the moment, authoring new content using the `upright` flag is discouraged.  
+> 
+> @cscott is this advice still up-to-date? https://www.mediawiki.org/wiki/Help:Images#Syntax should probably be updated. For context, we were looking at this flag in {T296869}.
+
+Or @subbu perhaps you know the answer to this question? Thank you in advance!",1647504763,PHID-USER-jzbjfcs2csloltie4voe,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,">>! In T64671#1644967, @cscott wrote:
+> The `upright` option suffers from some severe problems.  Consensus was reached on replacing it, see https://www.mediawiki.org/wiki/Requests_for_comment/Square_bounding_boxes  -- unfortunately, the replacement agreed upon had to be reverted due to some unexpected interactions with page layout.  We need to revisit the RFC and select one of the other proposed options for implementation.
+> 
+> But at the moment, authoring new content using the `upright` flag is discouraged.  
+
+@cscott is this advice still up-to-date? https://www.mediawiki.org/wiki/Help:Images#Syntax should probably be updated. For context, we were looking at this flag in {T296869}.",1638790184,PHID-USER-jzbjfcs2csloltie4voe,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"I think that whatever solution is reached, it should comply with relevant policies on the Wikipedias that are affected by it. On enwiki, (https://en.wikipedia.org/wiki/Wikipedia:Image_use_policy#Displayed_image_size), the following policy is in place:
+
+""**Except with very good reason, do not use** px (e.g. thumb|300px), **which forces a fixed image width.** In most cases upright=scaling factor should be used, thereby respecting the user's base preference (which may have been selected for that user's particular devices).""
+
+Additionally, respecting a user's preference for image size is an accessibility issue, and needs careful consideration before any attempt is made to change or eliminate it.",1492277661,PHID-USER-cctxaafy3x73lcil6bsc,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,">>! In T64671#3130642, @Schnark wrote:
+>>>! In T64671#1734077, @Trizek-WMF wrote:
+>> So the message we have to spread is ""don't use upright anymore"" ? 
+> Is somewhere work going on  to implement a replacement for ""upright"" which will be supported in VE?
+
+It looks to me like this is being blocked by T351 and T65904. Discussion above appears to indicate that implementing what `upright` //does// is being held up by a desire to redefine what it //should// do, or even to //deprecate// it.",1490456733,PHID-USER-5afgigb2oyaaralisy55,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,">>! In T64671#1734077, @Trizek-WMF wrote:
+> So the message we have to spread is ""don't use upright anymore"" ? 
+
+Are there any updates on this? Is somewhere work going on  to implement a replacement for ""upright"" which will be supported in VE?",1490438205,PHID-USER-tyjmn7xcw6s2b6rqagj7,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"So the message we have to spread is ""don't use upright anymore"" ? ",1445243509,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"Change 238855 had a related patch set uploaded (by Cscott):
+WIP: Allow serialization of images which scale the default thumbnail size.
+
+[[https://gerrit.wikimedia.org/r/238855]]
+",1442435327,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"The `upright` option suffers from some severe problems.  Consensus was reached on replacing it, see https://www.mediawiki.org/wiki/Requests_for_comment/Square_bounding_boxes  -- unfortunately, the replacement agreed upon had to be reverted due to some unexpected interactions with page layout.  We need to revisit the RFC and select one of the other proposed options for implementation.
+
+But at the moment, authoring new content using the `upright` flag is discouraged.  There is a separate bug (T112710) that currently affects resizing images tagged with `upright`; that will be fixed.  But that will result in a serialization with an explicit bounding box, not the upright flag, and we have no current plans to emit an `upright` flag in newly-authored content.  Any existing use cases should be dealt with as part of the {T351} process (go comment over there!), so that we can come up with a way to solve these problems which doesn't rely on a broken feature.",1442415656,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,[[https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=118625212&oldid=118570520|New feedback]] concerning upright.,1442229339,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,A user on frwp [[ https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=116008432&oldid=115979310 | explains ]] that having a number of pixels instead of an upright (configurable) is an accessibility problem. ,1434637737,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,A user on frwp [[ https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=116008432&oldid=115979310 | explains ]] that having rough pixels instead of an upright is an accessibility problem. ,1434637672,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,A user on frwp [[ https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=116008432&oldid=115979310 | explains ]] this upright issue is an accessibility problem. ,1434636758,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"So the blocking status for T64666 is a little misleading here.  AFAIK, Parsoid parses the 'upright' option properly, and emits DOM with the correct size set.
+
+But we're not clear at all that we want to support *authoring* images with the 'upright' option, because we'd rather deprecate that option and replace it with something better.
+
+So, can we reset the discussion a little bit: what is the *current* behavior when you edit an image which has the 'upright' option.  What (if anything) is actually broken?",1422556136,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"(In reply to Spinningspark from comment #8)
+> One point about the upright parameter is that it does something sensible
+> with a portrait image by default without the user having to think about what
+> scaling factor he wants to use.  The scale parameter per se is a good thing
+> to have, but being forced to calculate a scale factor to get the equivalent
+> of the old upright parameter is a step backwards in my opinion (its a step
+> forward from the current two-steps-backward position of not having anything
+> at all but is still a step backwards from what we had before.)
+
+I think you're making assumptions here. :-) The idea was that we'd default to the usual value of 75% (and make it clear that this is the preferred value).",1412039580,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"One point about the upright parameter is that it does something sensible with a portrait image by default without the user having to think about what scaling factor he wants to use.  The scale parameter per se is a good thing to have, but being forced to calculate a scale factor to get the equivalent of the old upright parameter is a step backwards in my opinion (its a step forward from the current two-steps-backward position of not having anything at all but is still a step backwards from what we had before.)",1412027527,PHID-USER-imut7wxehhy35ukuzaks,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"(In reply to C. Scott Ananian from comment #6)
+> Mm.  Now I'm thinking the mw option might be `square` so that Parsoid emits:
+> 
+> [[Figure:Foobar.jpg|200px|square]]
+> [[Figure:Foobar.jpg|thumb|square]] <!-- equivalent to upright=1 -->
+> [[Figure:Foobar.jpg|upright=0.5|square]]
+> 
+> That would provide the same functionality but address James' concern in
+> comment 2.
+
+I'm not a fan of adding more work-arounds that modify older work-arounds. If we can fix this up cleanly with something like scale & square bounding box by default then we should do so IMO. That would result in cleaner wikitext like this:
+
+[[Figure:Foobar.jpg|200px]]
+[[Figure:Foobar.jpg|thumb]]
+[[Figure:Foobar.jpg|scale=0.75]]
+
+An automatic conversion that preserves existing image sizes is very much possible if the community agrees that going for a square bounding box by default makes sense. But again, lets not get ahead of ourselves to much here & focus on the Parsoid interface for now.",1395772902,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"Mm.  Now I'm thinking the mw option might be `square` so that Parsoid emits:
+
+[[Figure:Foobar.jpg|200px|square]]
+[[Figure:Foobar.jpg|thumb|square]] <!-- equivalent to upright=1 -->
+[[Figure:Foobar.jpg|upright=0.5|square]]
+
+That would provide the same functionality but address James' concern in comment 2.",1395762643,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"200x200px is what we already emit.  That's been the case for a while.
+
+Current thinking is that the new PHP image option will be called 'scale' (not 'thumbscale'), and that parsoid will mark its use with a 'mw-scale' class on the image wrapper, not a data-mw attribute.",1395436484,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"(In reply to James Forrester from comment #2)
+> That seems bad. [[Figure:Foobar.jpg|200px]] is vastly-preferred and
+> [[Figure:Foobar.jpg|200x200px]] is considered broken wikitext except in rare
+> cases.
+
+We could also omit this if we don't care about size stability on image aspect ratio change. Alternatively we could also change the default behavior to use a square bounding box. Lets make that decision when we get there. For now we'll just use upright.",1395425982,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"Related: https://www.mediawiki.org/wiki/Requests_for_comment/Standardized_thumbnails_sizes
+
+We could encourage users to use a limited set of pre-defined scaling factors. This could potentially let us handle some user pref based scaling in CSS instead of JS.
+
+For now the plan is to add a data-mw.scale factor which corresponds to a default-sized image. If the format is 'thumb' or 'frameless', the default image size is given by a *square bounding box* of the default thumb size.",1395425866,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"(In reply to C. Scott Ananian from comment #1)
+> Parsoid will *only* generate wikitext of the form:
+> 
+> [[Figure:Foobar.jpg|200x200px]]
+> or
+> [[Figure:Foobar.jpg|thumb|thumbscale=1]]
+
+That seems bad. [[Figure:Foobar.jpg|200px]] is vastly-preferred and [[Figure:Foobar.jpg|200x200px]] is considered broken wikitext except in rare cases.",1395424354,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+VisualEditor: Be able to set an item's size in upright terms in the media edit dialog,"The parsoid plan is to support only square bounding boxes.
+
+Unfortunately, PHP core doesn't have a way to specify 'a square bounding box of the default thumbnail size' yet.  So for purposes of discussion let's assume there's a wikitext option named 'thumbscale' which enforces a square bounding box of (an appropriate factor of) the default thumbnail size (then quantized to nearest 10px, like upright does, in order to avoid creating lots of odd-sized thumbs).
+
+So Parsoid will *only* generate wikitext of the form:
+
+[[Figure:Foobar.jpg|200x200px]]
+or
+[[Figure:Foobar.jpg|thumb|thumbscale=1]]
+
+We will attempt to round-trip other wikitext forms ('upright', 'x200px', 'thumb' by itself (which is a width restriction only), etc) if the image is not edited.  But if the image is edited, we will emit only a square bounding box.
+
+In the short term, we might use:
+
+[[Figure:Foobar.jpg|thumb|upright=<number>]]
+
+as an approximation to the 'thumbscale' factor, where we compute <number> as <aspect ratio>*<thumbscale>.  But this is viewed as a short term hack only.
+
+The VE UI should present this as something like 'use default thumbnail size', rather than explicitly mentioning the 'upright' parameter.",1395424134,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-p6lbsrsy4c6xtsnzfnbc,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a template
+3.Click on Add Parameter
+4.But do not add any parameter just click on ""Apply Changes""
+5.Reopen the template
+
+Observed Result:
+An undefined parameter appears inside the template dialog box
+
+See the screenshot attached
+
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F13443}",1394744880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-47vdxcoqpdotzl5weohn,task_description,resolved
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter",Verified the fix in test2 : https://test2.wikipedia.org/wiki/Wmf19?veaction=edit,1395356305,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","Change 119699 merged by jenkins-bot:
+Ignore placeholder parameters in serialization
+
+https://gerrit.wikimedia.org/r/119699",1395293566,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","Change 119699 had a related patch set uploaded by Catrope:
+Ignore placeholder parameters in serialization
+
+https://gerrit.wikimedia.org/r/119699",1395293339,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","It's technically not corrupting wikitext, just inserting oddness, but yes.",1395261213,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter","This is causing wikitext corruption on the wikis, upping severity.",1395260602,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+"VisualEditor: An Undefined parameter appears in the template dialog box after clicking on ""Add parameter"" but not adding any new parameter",*** Bug 62827 has been marked as a duplicate of this bug. ***,1395256801,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-47vdxcoqpdotzl5weohn,task_subcomment,NA
+VisualEditor: MediaWiki <source>  used between text nodes should render block instead of inline-block,"Screenshot of MediaWiki rendering
+
+Wikitext:
+
+=== Example ===
+Foo <code>bar</code> baz.
+You'll want to add <source lang=""javascript"">
+        ""predef"": [
+                ""OO"",
+        ]
+</source> x y.
+
+
+In MediaWiki's PHP parser:
+
+  <h3>..</h3>
+  <p>Foo <code>bar</code> baz.</p>
+  <p>You'll want to add</p>
+  <div> .. syntax highlgiht ..
+  <p>x y.</p>
+
+In Parsoid:
+
+  <h3>..</h3>
+  <p>Foo <code>bar</code> baz.</p>
+  You'll want to add
+  <div> .. syntax highlgiht ..
+  x y.
+
+Notice the lack of paragraphs from the Parsoid DOM, though this is odd, it still renders fine visually in browsers.
+
+In VisualEditor:
+
+  <h3 class=""ve-ce-branchNode"">Naming</h3>
+  <p class=""ve-ce-generated-wrapper ve-ce-branchNode"">
+    You'll want to add&nbsp;
+    <span class=""ve-ce-leafNode ve-ce-generatedContentNode ve-ce-mwExtensionNode ve-ce-mwAlienExtensionNode ve-ce-protectedNode"" contenteditable=""false"">
+      <div dir=""ltr"" class=""mw-geshi mw-code mw-content-ltr"" typeof=""mw:Extension/source"" data-mw="".."" about=""#mwt24"">..</div>
+    </span>
+    &nbsp;x y.
+  </p>
+
+It renders as an inline-block within a paragraph, that's where it goes wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13385}",1394734980,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7z4tlyfijoeek5deckps,task_description,open
+VisualEditor: MediaWiki <source>  used between text nodes should render block instead of inline-block,"Created attachment 14805
+Screenshot of Parsoid rendering and Parsoid DOM
+
+**Attached**: {F13389}",1394735068,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7z4tlyfijoeek5deckps,task_subcomment,NA
+VisualEditor: MediaWiki <source>  used between text nodes should render block instead of inline-block,"Created attachment 14804
+Screenshot of VisualEditor rendering
+
+**Attached**: {F13387}",1394735052,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7z4tlyfijoeek5deckps,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"* Latest mediawiki and VisualEditor master locally
+* Chrome incognito
+* Sandbox?veaction=edit
+
+Shows:
+
+ 1 notice                      X
+ ----
+ Warning: You are not logged in.
+ Your IP address will be recorded
+ in this page's edit history.
+
+When hovering over the [X], the text ""1 notice"" and ""Warning: .. "" go down 1px and then back up again.
+
+Not sure what it causing it, could be a browser rendering bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394667060,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n3jah3fg23mapojunl7u,task_description,resolved
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"Change 121279 merged by jenkins-bot:
+Don't use transitions for opacity on hover for now
+
+https://gerrit.wikimedia.org/r/121279",1395877134,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"Change 121279 had a related patch set uploaded by Catrope:
+Don't use transitions for opacity on hover for now
+
+https://gerrit.wikimedia.org/r/121279",1395876804,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"Cause of the wiggling seems to be a transition on the opacity. Going to work around this by just commenting out that transition, because it's such a minor detail.
+
+I'll also try to isolate a test case and file a bug upstream with Chrome.",1395876281,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,*** Bug 63020 has been marked as a duplicate of this bug. ***,1395876216,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,"Widening scope, the ""back"" button of the inspector context is affected as well.
+
+Screen capture of ""Toolbar notice close button""
+: http://cl.ly/2O3c2F072a02
+
+
+Screen capture of ""Inspector context back button""
+: http://cl.ly/2S3g0V0y2O1J",1394745588,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+OOjs UI: Hovering icons makes them jump around 1-2px in Chrome,Screen capture: http://cl.ly/2O3c2F072a02,1394676856,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n3jah3fg23mapojunl7u,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Save the page
+4.Reopen the page
+5.Open the media settings for the image 
+
+Observed Result:
+The following error appears in the console and Media Settings dialog box cannot be closed:
+
+Uncaught TypeError:Cannot read property 'width' of null
+Uncaught TypeError:Cannot call method 'getItemFromData'of undefined.
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=12thmarchchrome
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13283}",1394660040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_description,resolved
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load",Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754433,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Change 118601 merged by jenkins-bot:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118601",1394752327,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","(In reply to James Forrester from comment #4)
+> Still occurring after the above patch. :-(
+
+Belay that, now working. Probably browser cache issues. *sigh*
+
+(Thanks, Moriel!)",1394752129,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Still occurring after the above patch. :-(
+
+I've re-worded the bug title based on my understanding. The issue is probably in the binding of the variable – note that everything is fine as soon as you refresh the page, the problem is when you re-load VE on the same page (so re-using a lot of the VE running code).",1394748489,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Change 118427 merged by jenkins-bot:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118427",1394744961,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Change 118601 had a related patch set uploaded by Catrope:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118601",1394744862,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+"VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load","Change 118427 had a related patch set uploaded by Mooeypoo:
+Fix regression bug 'default size' change on alignment
+
+https://gerrit.wikimedia.org/r/118427",1394683659,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gy7d2blzfo6x6blcrzsj,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page in VE
+2.Insert a reference
+3.Open the reference dialog 
+4.Insert another reference inside it
+5.Save the page
+
+Observed Result:
+In read mode :Cite error: Closing </ref> missing for <ref> tag appears
+Inside VE: for the reference that is inside another reference, the wikitext appears in the reflist section
+
+See the screenshots attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13271}",1394653320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_description,resolved
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,Verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=Wmf19&veaction=edit,1395355830,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Change 119704 merged by jenkins-bot:
+Followup 861d097: actually exclude reference tool in reference dialog toolbar
+
+https://gerrit.wikimedia.org/r/119704",1395295485,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"(In reply to Roan Kattouw from comment #2)
+> Adding references inside of references shouldn't be possible. That toolbar
+> button is supposed to be hidden. Repurposing bug.
+> 
+Turned out to be an accidental overcorrection from fixing bug 62286.",1395295231,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Change 119704 had a related patch set uploaded by Catrope:
+Followup 861d097: actually exclude reference tool in reference dialog toolbar
+
+https://gerrit.wikimedia.org/r/119704",1395295209,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Adding references inside of references shouldn't be possible. That toolbar button is supposed to be hidden. Repurposing bug.
+
+However, we should verify that we deal correctly with cases where this has already been done in wikitext.",1395256513,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave,"Created attachment 14794
+Wikitext in the reflist
+
+**Attached**: {F13272}",1394653411,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6ixpggv4pjhmvx5zdw23,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"I learned today from Rob Lanphier that it has recently become possible to do this reliably in every extension repo as well as mw core: 
+
+$ git checkout wmf/1.23wmf17
+
+
+For example: 
+
+/VisualEditor$ git checkout wmf/1.23wmf17
+Branch wmf/1.23wmf17 set up to track remote branch wmf/1.23wmf17 from origin.
+Switched to a new branch 'wmf/1.23wmf17'
+
+The current branch of each wiki is tracked in https://git.wikimedia.org/blob/operations%2Fmediawiki-config/HEAD/wikiversions.json
+
+The current branch of core (which should be consistent across all extensions also) is available on https://test2.wikipedia.org/wiki/Special:Version (and theoretically in the API somewhere)
+
+It would be good if we could change our Jenkins builds with test2 as a target to pull the current wmf branch instead of master. 
+
+In the short term, we could update the build config manually every Thursday. 
+
+In the slightly longer term it should be possible to read Special:Version or the wikiversions.json file in order to determine at run time the proper version of the tests appropriate for test2 (and any other target environment not beta labs, e.g. enwiki or commons)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394483880,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_description,resolved
+investigate updating test2 Jenkins builds weekly to pull by branch,"I think this was implemented entirely back in May 2014.  The fix was to have MediaWiki API the branch it runs then have the browser test checkout the matching branch, fall backing to master if the branch is not found.",1407233064,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Gilles from the Multimedia team reported an issue with the browser tests running some outdated version of the code.   Turns out the repo was not reset to origin/master but to local master branch.
+
+Fixed up with https://gerrit.wikimedia.org/r/#/c/134576/",1400664667,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"I tested it on a few change and it seems to be working fine.
+
+The qa/browsertests.git is missing wmf branches, so I have added a fallback to the 'master' branch.
+
+Lets see what happens tomorrow :)",1400617809,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134483 merged by jenkins-bot:
+Fallback to master branch when test repo miss branch
+
+https://gerrit.wikimedia.org/r/134483",1400617745,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134483 had a related patch set uploaded by Hashar:
+Fallback to master branch when test repo miss branch
+
+https://gerrit.wikimedia.org/r/134483",1400617666,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134236 merged by jenkins-bot:
+Get mw branch from target URL and check it out
+
+https://gerrit.wikimedia.org/r/134236",1400617040,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134376 merged by jenkins-bot:
+mw-sort-wmf-branches: sort wmf branchs numerically
+
+https://gerrit.wikimedia.org/r/134376",1400602772,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134376 had a related patch set uploaded by Hashar:
+mw-sort-wmf-branches: sort wmf branchs numerically
+
+https://gerrit.wikimedia.org/r/134376",1400601941,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 134236 had a related patch set uploaded by Hashar:
+Get mw branch from target URL and check it out
+
+https://gerrit.wikimedia.org/r/134236",1400531916,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"The lame mw-api-siteinfo.py is now deployed.  We can use to query the target MediaWiki installation to grab the branch and attempt to check it out before running the browser tests.
+
+Should do git checkout -f  iirc.",1400530464,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131861 merged by jenkins-bot:
+mw-api-siteinfo: fetch siteinfo from MW API
+
+https://gerrit.wikimedia.org/r/131861",1400530340,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131936 abandoned by Hashar:
+API: Expose git branch in siteinfo
+
+Reason:
+No urgency to have this deployed in 1.24wmf3 since commit is in the branch wmf/1.24wmf4 which is going to be deployed on the remaining production wikis on May 15th ( https://wikitech.wikimedia.org/wiki/Deployment ).
+
+https://gerrit.wikimedia.org/r/131936",1399898263,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131935 abandoned by Reedy:
+API: Expose git branch in siteinfo
+
+Reason:
+1.24wmf2 is not used now
+
+https://gerrit.wikimedia.org/r/131935",1399657280,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"I will try to get it included in the currently deployed wmf installations, else the patch will land under the next two weeks.
+
+The tiny python script will let us easily get the branch of a target wiki. Knowing it, we can then git checkout that branch before starting the browsertests.
+
+I might be able to handle that during this week hackaton, no promise though.",1399492449,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131936 had a related patch set uploaded by Hashar:
+API: Expose git branch in siteinfo
+
+https://gerrit.wikimedia.org/r/131936",1399448471,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131935 had a related patch set uploaded by Hashar:
+API: Expose git branch in siteinfo
+
+https://gerrit.wikimedia.org/r/131935",1399448452,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131768 merged by jenkins-bot:
+API: Expose git branch in siteinfo
+
+https://gerrit.wikimedia.org/r/131768",1399422613,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"The mw-api-siteinfo.py script will let us do something like:
+
+ $ mw-api-siteinfo.py http://test2.wikipedia.org/ git_branch
+ 1.24wmf2
+ $
+
+We can then checkout that branch in the extensions to run the matching set of browser tests.",1399408181,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131861 had a related patch set uploaded by Hashar:
+mw-api-siteinfo: fetch siteinfo from MW API
+
+https://gerrit.wikimedia.org/r/131861",1399408053,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"Change 131768 had a related patch set uploaded by Hashar:
+Api: expose git branch in siteinfo
+
+https://gerrit.wikimedia.org/r/131768",1399404721,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,I am pretty sure I have a good idea about fixing this :-],1399394021,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,"From bug 64611:
+
+When browsertests hit the production wikis, we should fetch the extension wmf branch that match the targeted website.  The mapping of wiki vs wmf branch can be found via the dblist files in operations/mediawiki-config.git
+
+Instead of using the Jenkins git plugin, we will have to use a script to find out which branch to check.",1398788977,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+investigate updating test2 Jenkins builds weekly to pull by branch,*** Bug 64611 has been marked as a duplicate of this bug. ***,1398788949,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-dbb75rdjycfheqcgaqvh,task_subcomment,NA
+VisualEditor: Changing the format of a block slug between a list and a block template breaks badly,"In this page https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_(WMF)/Prove2&oldid=101942635, if you click Enter twice after the last sub-item of the list and then select Titre de section (Heading), that item and the Portal template below disappear, and results from the Undo action may vary (the French user who found this reports that a couple of CTRL+Z blank the page for him; for me, nothing happens, or the item comes back but the template doesn’t). 
+Nothing changes if the list is unordered or ordered, but it does seem to matter that it features sub-items and not just items (as a matter of fact I couldn't reproduce with a simple list here http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Elitest&oldid=82999).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://fr.wikipedia.org/wiki/Utilisateur:Elitre_%28WMF%29/Prove2?oldid=101942635&veaction=edit
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50250",1394455740,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-dirtzibr6cqkhuru3pvp,task_description,resolved
+VisualEditor: Changing the format of a block slug between a list and a block template breaks badly,Appears to be fixed,1423749922,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-dirtzibr6cqkhuru3pvp,task_subcomment,NA
+VisualEditor: Changing the format of a block slug between a list and a block template breaks badly,We'll see if the patch for that works :),1395857888,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-dirtzibr6cqkhuru3pvp,task_subcomment,NA
+VisualEditor: Changing the format of a block slug between a list and a block template breaks badly,Not sure if this is related to bug 50250?,1395440640,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dirtzibr6cqkhuru3pvp,task_subcomment,NA
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,"As reported by NicoV on fr.wp, 
+unrelated edits remove the syntax for an image from an external wikilink.
+See tests at https://fr.wikipedia.org/w/index.php?title=Utilisateur%3ANicoV%2FTest&diff=101782688&oldid=101782616 , https://www.mediawiki.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandboxVE&diff=924704&oldid=924702 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394446440,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lvbwtwmxsjk452ye6dto,task_description,resolved
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,"Change 639633 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.dm.MWExternalLinkAnnotation: Alienate malformed links
+
+https://gerrit.wikimedia.org/r/639633",1607350957,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lvbwtwmxsjk452ye6dto,task_subcomment,NA
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,"Change 639633 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.dm.MWExternalLinkAnnotation: Alienate malformed links
+
+https://gerrit.wikimedia.org/r/639633",1604614338,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lvbwtwmxsjk452ye6dto,task_subcomment,NA
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,"(In reply to Elitre from comment #1)
+> PS: the edit summary window correctly displays the warning that something's
+> wrong.
+
+Now that you say there's a warning, I see it, but unless you're looking for it, it's almost invisible, lost among other texts, without any highlighting. And nothing more is said when you save.",1394618321,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-lvbwtwmxsjk452ye6dto,task_subcomment,NA
+VisualEditor: Image as part of the anchor of a link is stripped on round-trip,PS: the edit summary window correctly displays the warning that something's wrong.,1394455954,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lvbwtwmxsjk452ye6dto,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","Some (many) templates do not use any parameters (e.g., hundreds of templates like https://en.wikipedia.org/wiki/Template:Stub).  However, if you add those templates, VisualEditor will ask you for parameters, just like it does for any other template.  It would be nice to have a TemplateData setting for ""no parameters here, so don't bother asking"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394239320,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_description,open
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","> How to proceed? For {{stub}} on en.wp, I don’t achieve to add any parameter […]
+
+Turns out this is an unrelated bug, see T333826. As long as this is not fixed you can use the [keyboard shortcut](https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts#Template_editor_dialog_shortcuts_and_keyboard_interactions) Ctrl+Shift+D to add undocumented parameters to any template, no matter how it is documented.",1681234486,PHID-USER-u6ycqhfpa3k4yvlpxjt2,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","> The user can proceed as before, but the option to add what we now clearly mark as ""undocumented"" parameters is much less prominent, and explained as well.
+How to proceed? For {{stub}} on en.wp, I don’t achieve to add any parameter (as requested by this task).",1680291128,PHID-USER-unpoeiyj52rmcfqi5rbw,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","As part of the #wmde-templates-focusarea we made the #VisualEditor dialog say this when the #TemplateData documentation has an empty list of `""params"": {}`: ""This template has no documented parameters and may be intended for use without them."" The user can proceed as before, but the option to add what we now clearly mark as ""undocumented"" parameters is much less prominent, and explained as well. The relevant task was {T300710}.
+
+We spend quite some time on this detail and are quite happy with the result and how it performed in user tests. I suggest to leave it like that and close this task.",1680274691,PHID-USER-u6ycqhfpa3k4yvlpxjt2,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition",Another use case suggested by an editor at https://www.mediawiki.org/wiki/Topic:Wgw42pcci4g5zjn6,1632241133,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","Here's another example for the list of use cases:  The sole contents of
+{{userboxbottom}} is the table-closing wikitext code `|}`.  There are
+dozens of similar templates on enwiki.  Adding parameters to these is
+pointless at best.",1477065683,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","But @Krinkle  why shouldn't we have a way to signal that there are no parameters in the template?
+
+Yes, it could be wrong.  There could also be incorrectly incomplete TemplateData blocks added (probably far more common, actually).  
+
+I'm not saying that you'd have to prevent the addition of parameters.  But could you **just tell me** that adding a parameter to {{France-university-stub}} is probably a bad idea?  Just a friendly note, not something that's going to break the workflow if the TemplateData is wrong.  Just a note that says something like ""According to the template documentation, this template doesn't normally use any parameters.""",1475261502,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","I don't think we should have a property specifically to indicate that there are no parameters. I agree there needs to be room for TemplateData being wrong or outdated and VisualEditor's advanced transclusion editor would always allow for parameters to be added.
+
+However I think it'd be fine to remove the ability to add parameters from the simple editor that loads by default in VisualEditor - for cases where TemplateData data //did// exist but had no parameters specified.",1472693067,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","Maybe something like that, although I'd be happy to to restrict it to an empty array (=the case when it is least likely to be wrong).
+
+Even a ""warning"" note would be an improvement.  We could probably reduce confusion if we could have it display a sentence that says,  ""This template uses no parameters.  It is technically possible to add parameters here, but they will be ignored by the template"".
+
+",1458226640,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","So maybe something like a ""This TemplateData definition is complete, don't allow any undocumented parameters."" (not necessarily restricted to an empty array of parameters).
+
+I'm not sure this is a direction we want to go in though - IIRC we want to allow  for TemplateData being wrong and therefore able to be overridden inside VE.",1452891758,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","I think I wasn't quite clear earlier.  T53429 is about saying (nicely) that no parameters have been listed in TemplateData.  I'm glad that we made that improvement, but that's not what I want here.  Instead of a nice message, I want to **define, in TemplateData, that this template actually does not accept or use any parameters**.  This is ""no parameters in the //template//"", not ""no parameters currently typed into the //TemplateData//"".
+
+When a template is so marked, I'd also like VisualEditor disable the 'field name' search box, so that people can't insert any made-up or invalid parameters.  I want TemplateData to be able to stop editors from trying to add pointless parameters.",1434061888,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+"TemplateData: Be able to specify a ""no parameters accepted"" definition","
+
+*** This bug has been marked as a duplicate of bug 51429 ***",1398711170,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uj2x5dn6fe36q7kyulaj,task_subcomment,NA
+VisualEditor: Link inspector opens up in the Alternative textbox inside Media Settings,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE which has an image inside it.
+2.Now open the Media Settings for the image
+3.Type something for the Alternative Text
+4.Select the text and click on the Link Inspector icon 
+
+Observed Result:
+The link inspector opens up in the Alternative text textbox as it appears in the screenshot.However, it does get placed inside the caption textbox
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59868
+
+**Attached**: {F12881}",1394234880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zmuntlo4o5mkodhqeydo,task_description,resolved
+VisualEditor: Link inspector opens up in the Alternative textbox inside Media Settings,"Change 117658 merged by jenkins-bot:
+Disable MW tools when surface loses focus
+
+https://gerrit.wikimedia.org/r/117658",1397158691,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zmuntlo4o5mkodhqeydo,task_subcomment,NA
+VisualEditor: Link inspector opens up in the Alternative textbox inside Media Settings,"(In reply to Gerrit Notification Bot from comment #1)
+> Change 117658 had a related patch set uploaded by Catrope:
+> Disable MW tools when surface loses focus
+> 
+> https://gerrit.wikimedia.org/r/117658
+
+This commit addresses a different issue, but once it lands this bug will be impossible to trigger.",1394660366,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zmuntlo4o5mkodhqeydo,task_subcomment,NA
+VisualEditor: Link inspector opens up in the Alternative textbox inside Media Settings,"Change 117658 had a related patch set uploaded by Catrope:
+Disable MW tools when surface loses focus
+
+https://gerrit.wikimedia.org/r/117658",1394654169,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zmuntlo4o5mkodhqeydo,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,"Intention:
+Read the description from TemplateData
+
+
+Actual Results:  
+The description of the parameter from TemplateData is too pale.  People with poor eyesight, lower quality monitors, in sunlight on their mobile devices, etc. will not be able to read it.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1394218380,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-kd7fv3uer3q4cxedaaca,task_description,resolved
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,Please open a new task. This was work done in mid-2015.,1486169504,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,"Could anybody point out in a screenshot what's meant by parameter descriptions? The dialog has several minor issues, I've tried to catch some of them:
+{F5470647 width=703}",1486164717,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,"I think this is from an old version of the template dialog. Template parameter descriptions are now black for existing fields, and #555 in the search list.",1443035549,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,"The options are ""practically white"" (when you've clicked on something else) and ""extremely pale gray"" (when you've clicked inside that parameter).
+
+I hate them both.",1394220185,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+VisualEditor: Parameter descriptions in the new template dialog are too low contrast,Do you mean when it's faded out or when it's faded up?,1394219223,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kd7fv3uer3q4cxedaaca,task_subcomment,NA
+returnto and returntoquery in login/signup links doesn't get updated on pushState or popstate,"VisualEditor uses pushState to add veaction=edit to the URL when you click the VE edit tab, without causing a true reload.  However, this does not cause a true reload.  Similarly, when you click Read, the same happens to go back to read mode.
+
+Unfortunately, this does not update the returnto and returntoquery in the login and signup links.  So if you click the tab for VE, then go to login and signup in the top right, you will no longer be in VE when you get back.
+
+VE could make a custom solution for this, but a general method might be nice.  
+
+It's possible to listen to user-initiated navigation (e.g. back/forward) with the popstate event.  That could solve the problem for back and forward.
+
+However, that doesn't tell you about pushState.  So perhaps there should be a mw.pushState that updates these links, then calls the underlying browser method.
+",1394157660,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-4cf26q6ltrha64fqtdx3,task_description,open
+returnto and returntoquery in login/signup links doesn't get updated on pushState or popstate,"<Krinkle> [15:50:38] Krenair: Sounds like a good reason to have our page managed by a composition of embedded data-bound dom-based template objects. This'd be trivial there.
+<Krinkle> [15:50:52] Krenair: But that's still a year or so away, with neccecary pushback..",1420565108,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-4cf26q6ltrha64fqtdx3,task_subcomment,NA
+returnto and returntoquery in login/signup links doesn't get updated on pushState or popstate,I have a feeling that we might need to support extensions doing things when a mw.pushState is called...,1420265812,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-4cf26q6ltrha64fqtdx3,task_subcomment,NA
+VisualEditor: Removing last char from paragraph removes entire paragraph and throws in IE,"Screenshot of bug (incl. console error)
+
+Encountered in IE9 using BrowserStack ""Windows 7/IE9"" using latest MediaWiki and VisualEditor master via a tunnel. Could either be a browser bug we have to work around, or something on our end applicable to other browsers as well.
+
+
+* Put the cursor at the end of the second paragraph in a simple document
+* Removing the last character (e.g. full stop)
+
+It suddenly removes the entire paragraph and then throws an uncaught exception:
+
+> “Offset could not be translated to a DOM element and offset: 112”
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64128
+
+**Attached**: {F13344}",1394128260,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-q2usgov5bljwewguaiq4,task_description,resolved
+VisualEditor: Removing last char from paragraph removes entire paragraph and throws in IE,Can't reproduce in IE9. CE offset code has changed a lot in the last 18 months.,1460637744,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-q2usgov5bljwewguaiq4,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","When VisualEditor deactivates itself after Parsoid fails, this exceptions thrown because the property never got set.
+
+
+
+  ve.init.mw.ViewPageTarget.prototype.deactivate = function(override) {
+    if (..) {
+      if (..) {
+        this.deactivating = true;
+        if (ve.msg('accesskey-save') !== '-' && ve.msg('accesskey-save') !== '') {
+          this.elementsThatHadOurAccessKey.attr('accesskey', ..);
+                        ^
+
+ve.init.mw.ViewPageTarget.prototype.setupToolbarButtons = function () {
+  ..
+    if (ve.msg('accesskey-save') !== '-' && ve.msg('accesskey-save') !== '') {
+      this.elementsThatHadOurAccessKey = $( .. );
+
+
+The code in deactivate() shouldn't be repeating conditions like that as they're no longer semantically relevant, and in this case even incorrect. Instead the top one (which usually runs after setupToolbarButtons) should limit its interest to elementsThatHadOurAccessKey itself which we either set to null or to a jQuery object.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394125680,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-l3o54qij3sav6s6cs6gu,task_description,resolved
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117228 merged by jenkins-bot:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117228",1394150560,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117230 merged by jenkins-bot:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117230",1394150501,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117230 had a related patch set uploaded by Jforrester:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117230",1394127076,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117228 had a related patch set uploaded by Alex Monk:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117228",1394126885,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117224 merged by jenkins-bot:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117224",1394126291,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught Type: Cannot call method 'attr' of undefined""","Change 117224 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Check elementsThatHadOurAccessKey before accessing
+
+https://gerrit.wikimedia.org/r/117224",1394125939,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l3o54qij3sav6s6cs6gu,task_subcomment,NA
+VisualEditor:  Caption of nested image is centered in image dialog box,"Screenshot of image dialog
+
+1.  Go to page with images nested iside captions, e.g., the sandboxes at http://en.wikipedia.beta.wmflabs.org/w/index.php?&oldid=82442
+
+2.  Open the images and look at the caption for the first one.  The second image is displayed there, with its own caption centered.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F13240}",1394060040,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-seke4lquqzuxgalldvtb,task_description,resolved
+VisualEditor:  Caption of nested image is centered in image dialog box,Text is now correctly aligned.,1701963258,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-seke4lquqzuxgalldvtb,task_subcomment,NA
+VisualEditor: Block slugs don't shrink back when selection moves to a FocusableNode,"1. Click in a block slug
+2. The slug expands
+3. Click in another paragraph
+4. The slug contracts, as expected
+5. Click in the slug again
+6. The slug expands
+7. Click on a FocusableNode (reference, template, etc.)
+8. The slug doesn't contract
+9. Click in a paragraph somewhere
+10. Now the slug does contract
+
+This is because contracting the slug when it's unfocused happens in pollOnceInternal, which is not invoked when selecting FocusableNodes (and only invoked by accident when changing the selection programmatically). onModelSelect in ce.Surface should probably clear the focusedness of the focused slug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394058780,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3a75i4egmmyligpq2dlv,task_description,resolved
+VisualEditor: Block slugs don't shrink back when selection moves to a FocusableNode,"Change 117214 merged by jenkins-bot:
+Fix application of slug focus classes
+
+https://gerrit.wikimedia.org/r/117214",1394240928,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3a75i4egmmyligpq2dlv,task_subcomment,NA
+VisualEditor: Block slugs don't shrink back when selection moves to a FocusableNode,"Change 117214 had a related patch set uploaded by Esanders:
+Fix application of slug focus classes
+
+https://gerrit.wikimedia.org/r/117214",1394124079,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3a75i4egmmyligpq2dlv,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"Phantoms appearing in wrong position
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image which has large enough original size to go beyond the page say for example: http://en.wikipedia.beta.wmflabs.org/wiki/File:Ho-Ho-Kus_Inn.jpg
+
+3.Make it full size 
+4.Save the page
+
+5.Reopen the editor
+6.Select the image by clicking on a but further from the border of the image
+
+Observed Result:
+The phantom for selection is appearing in the wrong position
+
+See the screenshots attached
+
+Now to observe some additional behavior:
+Set the image size back to default size and observe the shield is still appearing in the previous position in the page
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13227}",1394058180,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_description,resolved
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"I think this issue is fixed now, the only issue I see now is, for image with too big size which goes beyond CE, the phantom is also going beyond the page.Not sure if that is something we can fix or not.",1407197289,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"Yeah, this looks fixed to me.",1406752402,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,I can't replicate this. I think this was fixed after the refactor of the phantoms.,1406727411,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"(In reply to ryasmeen from comment #5)
+> I am not getting the phantom appearing at wrong position issue anymore ,but
+> what I am see now is, it takes two clicks to select that image when you have
+> made it full size.
+> If it is an unrelated issue , i will file a separate bug.
+
+Let's keep it in this one.",1400226230,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"I am not getting the phantom appearing at wrong position issue anymore ,but what I am see now is, it takes two clicks to select that image when you have made it full size.
+If it is an unrelated issue , i will file a separate bug.",1400200358,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,This also happens when I change the image position from Left to Center,1398798218,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"It the phantom remains in the previous position even if I close the editor and reopen it .
+
+Selecting the phantom also selects the image below it.
+
+Please go to this page to better understand the issue:
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=5thfebchrome&veaction=edit",1394058655,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"Created attachment 14750
+Phantom appearing in previous position after reverting it to default size
+
+**Attached**: {F13229}",1394058371,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize,"Created attachment 14749
+How it appears when you select by clicking close to the border of the image
+
+**Attached**: {F13228}",1394058286,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zbfvbqwtbhi2xzot3pbs,task_subcomment,NA
+Sizing of `framed` images,"https://www.mediawiki.org/wiki/Help:Images#Size_and_frame says:
+
+> An image with frame always ignores the size specification, the original image
+> will be reduced if it exceeds the maximum size defined in user preferences.
+
+However, as bug 53514 describes, the actual behavior seems to have regressed at some point.  The code in includes/Linker.php to check the user preference for size (which seems to be the same as the thumbnail size preference) is unreachable.  As presently written, framed images are always rendered at their ""natural"" size, *unless a height* is specified, in which case the height is honored (and the width, if any, ignored).
+
+It's not entirely clear what the proper fix should be.  There are three options:
+
+1. Leave the code as is, and update the spec on the wiki.
+2. If a height is specified, honor the height *and* width (conservative, should change few pages)
+3. Implement what I think was the original idea: *always* ignore the width and height, and limit the maximum image size with the user's thumbnail size preference.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1394031840,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_description,resolved
+Sizing of `framed` images,"I checked image documentation on mw as well as enwiki and other language-specific wikis, as well as reading the code.  It was clear that the intent was as documented -- framed images were original size.  They even called getUnscaledThumb in the code.  However, getUnscaledThumb had a bug so that it did not always return unscaled thumbs.  This affected a miniscule number of pages, all of which (upon examination) were really trying to do something else (usually 'thumb' not 'frame').  We fixed most of those pages, and fixed the bug.  This bug has been merged and closed for over a month now and is already live on all the wikis.  (See https://en.wikipedia.org/wiki/User:Cscott/framed )
+
+I think you are actually trying to review the 'square bounding box' RfC -- which is Not This Bug.",1400696244,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"(In reply to Krinkle from comment #17)
+> I can't be bothered to read through and interpret the logic of height bound
+> and width bound and square cropped box ponies.
+> 
+> But I'm confused by two things:
+> 
+> 1) I can understand why certain keywords should not result in a cropped
+> image and thus for 'frame' to now only respect height of width. But ignoring
+> both seems like a pointless change that is asking to break and upset
+> existing content.
+> 
+> Existing usage like [[File:Example.jpg|frame]] would be unaffected, but
+> existing content like [[File:Test wiki logo notext.png|frame|200x200px]]
+> will not result in a gigantic 3000px image being framed on the page[1]
+
+Note that only 200x200px was scaled so far, and is rare in combination with frame. 200px was *not* scaled with frame, and still isn't.
+
+
+> 2) Wait, we made this change because some old Help documentation page[2] on
+> mediawiki.org says[3] so? That's not by any means a specification. Also,
+> that same exact documentation page has an example of
+> [[File:Example.jpg|frame|50px]] which is now broken[4] by being way too
+> large.
+
+There should be no change here at all. Framed images with only a width bbox specified were not scaled so far.
+
+Gabriel",1400691818,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"I can't be bothered to read through and interpret the logic of height bound and width bound and square cropped box ponies.
+
+But I'm confused by two things:
+
+1) I can understand why certain keywords should not result in a cropped image and thus for 'frame' to now only respect height of width. But ignoring both seems like a pointless change that is asking to break and upset existing content.
+
+Existing usage like [[File:Example.jpg|frame]] would be unaffected, but existing content like [[File:Test wiki logo notext.png|frame|200x200px]] will not result in a gigantic 3000px image being framed on the page[1]
+
+
+2) Wait, we made this change because some old Help documentation page[2] on mediawiki.org says[3] so? That's not by any means a specification. Also, that same exact documentation page has an example of [[File:Example.jpg|frame|50px]] which is now broken[4] by being way too large.
+
+[1] https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&oldid=1011846
+[2] https://www.mediawiki.org/w/index.php?title=Help:Images&oldid=945436
+[3] ""An image with frame always ignores the size specification, the original image will be reduced if it exceeds the maximum size defined in user preferences.""
+[4] https://www.mediawiki.org/w/index.php?title=Help:Images&oldid=945436#Size_and_frame",1400688484,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"We use the parsoid HTML for the page, so we do in fact handle localized option names.  However, the caveat in comment 6 applies: ""One limitation is that it uses the wp allimages API query, so it does not include pages which include images *only from commons*.""  That seems to have been the case on the page you link to.",1400182358,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"You have missed the localized version at least for dewiki (""gerahmt""), see [1]
+There are also english aliase (""enframed"" and ""frame"")
+
+
+
+[1] https://de.wikipedia.org/w/index.php?title=Airbus_A350&oldid=129797202#Zweiter_Entwurf",1398612692,PHID-USER-qaoxfiqu6bxhd5ehlwhc,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 125885 merged by jenkins-bot:
+Match fixed PHP behavior for framed images with a height specification.
+
+https://gerrit.wikimedia.org/r/125885",1397577592,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 125885 had a related patch set uploaded by Cscott:
+Match fixed PHP behavior for framed images with a height specification.
+
+https://gerrit.wikimedia.org/r/125885",1397511789,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 125876 merged by jenkins-bot:
+Update release notes to describe user-visible change to framed images.
+
+https://gerrit.wikimedia.org/r/125876",1397510183,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 125876 had a related patch set uploaded by Cscott:
+Update release notes to describe user-visible change to framed images.
+
+https://gerrit.wikimedia.org/r/125876",1397508948,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 116995 merged by jenkins-bot:
+Ignore height as well as width for framed images.
+
+https://gerrit.wikimedia.org/r/116995",1397506081,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"(In reply to comment #8)
+cscott had already fixed the pages ""Gliederung des Feldheeres (Bundeswehr, Heeresstruktur 4)"", ""Hauptkirche Sankt Michaelis (Hamburg)"", and ""Ceylor"" and I've fixed the rest now on de.wp.",1397156460,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Full list for dewiki:
+Ceylor Datei:Lochtest.png x206px
+Ceylor Datei:Volumentest.png x206px
+Fernsehwerbung Datei:Werbeanteile.png x200px
+Fahrtanzeiger Datei:FSM_WT.png 500x300px
+Friedrich Glauner Datei:Grafik_Wertetrichter_unterlegt.png 480x367px
+Gliederung des Feldheeres (Bundeswehr, Heeresstruktur 4) Datei:II._Korps.svg x150px
+Gliederung des Feldheeres (Bundeswehr, Heeresstruktur 4) Datei:III._Korps.svg x150px
+Gliederung des Feldheeres (Bundeswehr, Heeresstruktur 4) Datei:I._Korps.svg x150px
+Hauptkirche Sankt Michaelis (Hamburg) Datei:Oratorium_zur_Einweyhung_der_Michaeliskirche_1762.JPG 180x180px
+Opernhaus vorm Salztor Datei:Salztor_NMB_1800.JPG 200x200px
+Opernhaus vorm Salztor Datei:Karte_NB_Oper.jpg 300x300px
+Raketenartilleriebataillon Datei:APP-6_MLRS.svg x80px
+Reedschalter Datei:Form_A_-_Schließer_(Normally_Open).jpg x50px
+Reedschalter Datei:Form_C_-Wechsler_bzw._Umschalter.jpg x50px
+Rheintal-Express Datei:Rheintal-Express_RABe_511.jpg 260x260px
+SV Salamander Kornwestheim Datei:Logo_TV_Kornwestheim_Kodiaks.gif x130px
+STUDIOPARK KinderMedienZentrum Datei:STUDIOPARK_KinderMedienZentrum.png x100px
+ToiToiToi Datei:Toitoitoi-symbole.svg x70px
+Spotlight (Software) Datei:Spotlight-Suche_im_Finder.png x222px
+Zwergsignal Datei:Zs-beispiel1.png 500x300px",1397155043,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Sorry, my stats were slightly wrong above:
+frwiki: 
+  60 image links using the ""framed"" option
+   1 of which uses a height bound
+dewiki:
+ 538 image links using the ""framed"" option
+  20 of which use a height bound
+
+So on dewiki/frwiki I've only been about to find 21 image links whose size would be changed by this bug fix.  I'm still collecting data on enwiki, I'll update this bug with the numbers when I have them.",1397154556,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"The patch attached to https://gerrit.wikimedia.org/r/116995 now fixes the bug in the ""right way"" -- that is, it fixes File::getUnscaledThumb.
+
+This will change the size of all images which combine a height bound and a framed image.
+
+In order to determine whether fixing this bug will affect this display of too many images, I wrote a script to grunge through all images and pages containing images on a wiki.  See https://github.com/cscott/wp-image-info
+
+One limitation is that it uses the wp allimages API query, so it does not include pages which include images *only from commons*.
+
+I'm still collecting data for enwiki, but for frwiki:
+   43,014 total non-commons images
+    8,839 of them are in portrait orientation
+1,242,985 image links on pages, of which only
+       60 use the 'framed' option with a height bound
+
+For dewiki:
+  170,701 total non-commons images
+   55,208 of these are in portrait orientation
+1,786,779 image links on pages, of which only
+      538 use the 'framed' option with a height bound
+
+I fixed some of these:
+https://de.wikipedia.org/w/index.php?title=Hauptkirche_Sankt_Michaelis_%28Hamburg%29&diff=129396939&oldid=129292349
+https://de.wikipedia.org/w/index.php?title=Ceylor&diff=129396510&oldid=129332266
+https://de.wikipedia.org/w/index.php?title=Ceylor&diff=129396510&oldid=129332266",1397153496,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"To be specific, the reason why framed images respect height (but not width) is because the linker uses:
+  $thumb = $file->getUnscaledThumb( $hp );
+but includes/filerepo/file/File.php::getUnscaledThumb forces the requested width to be the same as the images natural width *but not the height*.  So if there is a height specification, getUnscaledThumb actually returns a scaled thumb.  Which is... a bug.
+
+https://gerrit.wikimedia.org/r/116995 fixes this, but probably in the wrong way (unsets height for framed images).  File::getUnscaledThumb should probably be fixed so that it ignores the specified height if present.",1396541440,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,Parsoid commit https://gerrit.wikimedia.org/r/#/c/116983/ makes Parsoid match the old (broken) behavior. We'll need to partly undo it once this bug is fixed.,1394247126,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"Change 116995 had a related patch set uploaded by Cscott:
+Ignore height as well as width for framed images.
+
+https://gerrit.wikimedia.org/r/116995",1394040589,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"As you say, James, these are mostly questions for an RFC, and not really relevant here, though maybe blockers. A separate bug is called for.
+
+For what it's worth I would err in the direction of following the spec, but without a complaining user it may just be that the spec has fallen out of favour with reality. I would suggest asking on VPT and a few other sites that use lots of images in their work - Wikibooks and Commons come to mind - and maybe getting some CL time to help you sort out the replies, and post to more languages than just English.
+
+HTH...",1394040416,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+Sizing of `framed` images,"(In reply to C. Scott Ananian from comment #0)
+> https://www.mediawiki.org/wiki/Help:Images#Size_and_frame says:
+> 
+> > An image with frame always ignores the size specification, the original image
+> > will be reduced if it exceeds the maximum size defined in user preferences.
+> 
+> However, as bug 53514 describes, the actual behavior seems to have regressed
+> at some point.  The code in includes/Linker.php to check the user preference
+> for size (which seems to be the same as the thumbnail size preference) is
+> unreachable.  As presently written, framed images are always rendered at
+> their ""natural"" size, *unless a height* is specified, in which case the
+> height is honored (and the width, if any, ignored).
+> 
+> It's not entirely clear what the proper fix should be.  There are three
+> options:
+> 
+> 1. Leave the code as is, and update the spec on the wiki.
+> 2. If a height is specified, honor the height *and* width (conservative,
+> should change few pages)
+> 3. Implement what I think was the original idea: *always* ignore the width
+> and height, and limit the maximum image size with the user's thumbnail size
+> preference.
+
+I think option 2 is best; option 3 would be quite disruptive given that I think this is how it's been for a while (getting out git blame here might be interesting), so people aren't expecting this fundamental a thing to change much. We should talk to the Multimedia team a bit here to check with them, though.
+
+However, MediaWiki's image system needs some serious review, and I don't think a bug is the place to do it. Some possible questions, just to illustrate:
+
+*Why* does a frame image work like a thumb image except for the thumbnail and the magnifying glass icon?
+
+*Why* does frameless not operate like frame with respect to size, but does for everything else? (Though that might be just this bug, I guess?)
+
+*Why* are galleries fundamentally different in options and some of the new gallery options like hover-caption aren't implemented?
+
+Given that the proposed changes to Vector (but not Monobook, and not MediaWiki core?) in Typography Update remove the frame from frame and thumb images, should those options be merged? Should the wikitext for ""thumb"" be killed off? Should |border=1 still work in these cases? Why?
+
+… etc.",1394036538,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tp5fj2ilr35mvlgznvlo,task_subcomment,NA
+"VisualEditor: Show the ""*"" mark beside the required parameter in the Add Parameter section","screenshot
+
+Right now , we are not showing the * mark beside the required parameter in the Add Parameter section.I think we should show it there too, because if a user accidentally deletes a required parameter from the left panel of transclusion dialog then he will not have any indication on the required parameter anymore.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12919}",1393876980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7l5b3wunws2md2o6jk66,task_description,invalid
+"VisualEditor: Show the ""*"" mark beside the required parameter in the Add Parameter section","(In reply to Rummana Yasmeen from comment #0)
+> because if a user accidentally deletes a required parameter from the left
+> panel of transclusion dialog
+
+We removed the ability to do this (bug 60358).",1414085457,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-7l5b3wunws2md2o6jk66,task_subcomment,NA
+VisualEditor: Display description for selected and required parameters in transclusion dialog,"Not exactly Bug 51774, but:
+while descriptions of what a parameter is supposed to mean/do are provided in the list of available parameters inside the template inspector, this is not (no longer?) true for required and already selected parameters. The only way to read their description is to remove them from the left panel and get them back in the list, where they can be selected again, but clearly this is not optimal. Not sure a tooltip would be the way, so I'm filing this separately.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51774",1393854120,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_description,resolved
+VisualEditor: Display description for selected and required parameters in transclusion dialog,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755443,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_subcomment,NA
+VisualEditor: Display description for selected and required parameters in transclusion dialog,Verified the fix in test2,1394229550,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_subcomment,NA
+VisualEditor: Display description for selected and required parameters in transclusion dialog,Verified the fix in Betalabs,1393960662,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_subcomment,NA
+VisualEditor: Display description for selected and required parameters in transclusion dialog,This has been done by gerrit 115548 which will be coming soon. Completely agreed that it was a pain.,1393868175,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fyptj4pjp5zcqzsqxqnr,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Navigate to https://commons.wikimedia.org/wiki/File:Apthorp_south_jeh.JPG
+Now navigate to the same page via a ForeignAPI https://en.wikipedia.org/wiki/File:Apthorp_south_jeh.JPG
+
+Notice that in the latter a broken VisualEditor link appears.
+Expected: No VisualEditor link
+
+Similarly if you go to the mobile site you will see the same problem - an edit link appears in square brackets rather than an edit icon (see bug 61807). The mobile skin uses doEditSectionLink which seems to be incompatible with FileRepo.
+
+ I've spent the morning talking with Brion to understand more about how the magic commons file page works and how the page is rendered.
+
+Basically the problem is in FileRepo.php
+getDescriptionRenderUrl creates an API request to something akin to https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en
+If we can route this through the current skin this problem goes away.
+e.g.
+https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useformat=mobile
+or
+https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useskin=vector
+
+Brion is taking a look to see if he can add a hook.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54259",1393617960,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-3ntrwhhennryl3bteiii,task_description,resolved
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,">>! In T64071#675063, @MaxSem wrote:
+> Making FileRepo stuff depend on current skin would be horrible, also there's a problem with permissions/being logged in on foreign wiki which makes displaying edit links unreliable. However, I redid Bartosz's fix for bug 19415 (T21415) in https://gerrit.wikimedia.org/r/#/c/118135/
+
+Apparently, this never worked for File pages. I just fixed that with https://gerrit.wikimedia.org/r/468203. Since there will be no more section edit links in file descriptions fetched from foreign repo, I think we can consider this resolved.",1539896996,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Making FileRepo stuff depend on current skin would be horrible, also there's a problem with permissions/being logged in on foreign wiki which makes displaying edit links unreliable. However, I redid Bartosz's fix for bug 19415 in https://gerrit.wikimedia.org/r/#/c/118135/",1394568890,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Actually in the case of the file page we would like to render the edit links and make it possible to edit the content (albeit on a foreign wiki)
+
+So really it would be great if this could just pass the current skin name along with the request..",1394222399,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Hmm. You seem to be requesting the same thing as bug 19415 here – I already tried to fix it once, but there were complications. There's a patch there that needs to be reworked.
+
+(On a side note, my personal opinion about doEditSectionLink is that it should die in a fire and you should style the section edit links with CSS, as I made it possible to easily hide the brackets a few months ago.)",1393940047,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"Thanks for clarifying the VE issue is a different problem.
+
+Compare results of
+https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useskin=vector
+https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useformat=mobile
+(triggers useskin=minerva but minerva is unregistered so this is needed)
+
+The MinervaSkin overrides doEditSectionLink. There may be other skins that also override it and will thus be inconsistent.",1393623766,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,The VE bug for this is bug 54259.,1393618182,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,"That sounds like a VE/mobile bug, the links generated by core work just fine.",1393618100,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo,Apologies for the brain dump - I hope this is relatively clear.,1393618031,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-3ntrwhhennryl3bteiii,task_subcomment,NA
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Applying the patch from Ie6b47f5d192953366911 in VisualEditor did not result in a module change update.
+
+I kept refreshing and purging but nothing happened.
+
+Turns out the way we fetch files in #getModifiedTime is broken for 'skinStyles'.
+
+For some reason, this method duplicates the logic to interpret the 'skinStyles' array structure from #getStyleFiles (instead of using that method), and did so incorrectly causing it to always end up with an empty array.
+
+The bug is quite subtle in that the module is capable of including these files (they're not missing from the css build), it's just that the module cache isn't invalidated if a commit only changed files listed in that part of a module.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393615200,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_description,resolved
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Change 116143 abandoned by Krinkle:
+[WIP] resourceloader: Regression test for bug 62068
+
+https://gerrit.wikimedia.org/r/116143",1411500953,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_subcomment,NA
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Change 112837 merged by jenkins-bot:
+resourceloader: Fix broken skinStyles loop in #getModifiedTime
+
+https://gerrit.wikimedia.org/r/112837",1393618151,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_subcomment,NA
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Change 116143 had a related patch set uploaded by Krinkle:
+[WIP] resourceloader: Regression test for bug 62068
+
+https://gerrit.wikimedia.org/r/116143",1393615477,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_subcomment,NA
+ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file,"Change 112837 had a related patch set uploaded by Krinkle:
+resourceloader: Fix broken skinStyles loop in #getModifiedTime
+
+https://gerrit.wikimedia.org/r/112837",1393615472,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b3t54p4czyuwn2zt3mj7,task_subcomment,NA
+VisualEditor: Cursor navigation loops in block slugs at the start/end of the document,"Start case:
+1. Create a document that starts with {{echo|<div>foo</div>}} followed by some more content
+2. Put the cursor on the paragraph below the template
+3. Press left arrow until you're selecting the template
+4. Press left arrow; the cursor is now in the block slug
+5. Press left arrow; the cursor is now on the template
+6. Go to step 4
+
+End case:
+
+1. Create a document that ends with <references /> preceded by some content
+2. Put the cursor in the paragraph above the reflist
+3. Press right arrow until you're at the end of this paragraph
+4. Press right arrow; the cursor is now on the reflist
+5. Press right arrow; the cursor is now in the block slug
+6. Press right arrow; the cursor is now before the reflist 
+7. Go to step 4
+
+Note how the end case differs from the start case in that the loop is 3 keypresses long rather than 2.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393612500,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qlstyqepo7ltrgysuslj,task_description,duplicate
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Hello,
+
+Just to ask if it's possible to unable the Visual Editor for IP user on fr.wikiversity like fr.wikipedia.
+
+Thanks a lot and have a nice day.
+
+Lionel
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393587180,PHID-USER-mxwamhfxuzomk4umydpl,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_description,resolved
+Enable VisualEditor for all users and IPs by default on French Wikiversity,Thanks every one and have a nice day !,1396023903,PHID-USER-mxwamhfxuzomk4umydpl,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,This was done three weeks ago.,1396023734,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Change 117238 merged by jenkins-bot:
+Enable VisualEditor by default on French Wikiversity
+
+https://gerrit.wikimedia.org/r/117238",1394546232,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Ok, I didn't understand every things but it looks like I have to wait. Thank you Andre.",1394396667,PHID-USER-mxwamhfxuzomk4umydpl,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Lionel: https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle - this bug report is in PATCH_TO_REVIEW status, see comment 3.",1394309946,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Hello every one, Some body can translate in human language what's happen about the resolution of this ""bug"" because I didn't understand nothing about what's happen. What I just can see is the Visual editor still not work on fr.wikiversity for IP connection. Have a nice day.",1394297634,PHID-USER-mxwamhfxuzomk4umydpl,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Change 117238 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on French Wikiveristy
+
+https://gerrit.wikimedia.org/r/117238",1394129607,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Yep !
+
+You can already see the result of our vote about visual editor for IP on fr.wikipedia : https://fr.wikiversity.org/wiki/Projet:Wikiversit%C3%A9/Editeur_Visuel_pour_utilisateur_IP
+
+Have a nice day,
+
+Lionel",1394059713,PHID-USER-mxwamhfxuzomk4umydpl,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+Enable VisualEditor for all users and IPs by default on French Wikiversity,"Yes, this is possible, but you should confirm with the rest of the community that they are OK with doing it.",1393631019,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2nnhfwqpohjtpzziaj7g,task_subcomment,NA
+VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block),"In Thai language, it is possible that many characters (at most 3 or 4) will be on top each other. For example, ""ที่"" consists of three characters: ""ท"", ""ี"", and ""่"". In standard textbox/textarea, including normal wikieditor, when you press left, the cursor will go left by 1 block = 3 characters in case of ""ที่"". However, for VE's editor, it will go left by only 1 character, making editors feel that he unsuccessfully pressed the key. More importantly, with the way VE's editor is, it opens possibility that editors, thinking that the cursor is after ""่"", will accidentally insert text between ""ี"" and ""่"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393547460,PHID-USER-vuus2gmqsnxh6mnavgml,False,PHID-TASK-tulkkn7hqx5jvhx43ruj,task_description,resolved
+VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block),This is working now; I guess it has been since 2d8c3e799601d3eb70127b32e262dbe1d64a7e4e .,1536154773,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-tulkkn7hqx5jvhx43ruj,task_subcomment,NA
+VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block),Thank you very much for this bug report; it's very clear.,1393548166,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tulkkn7hqx5jvhx43ruj,task_subcomment,NA
+VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block),"Note that VE produces the correct behavior for deleting text. For example, ""ที่"" requires 3 backspaces in order to delete it. It has already been correct. Just only iterating through letters that is wrong.",1393547857,PHID-USER-vuus2gmqsnxh6mnavgml,False,PHID-TASK-tulkkn7hqx5jvhx43ruj,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Page Settings page
+3.Now type something 
+
+Observed Result:
+
+It inserts the text in the CE
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Imageghau&veaction=edit
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13238}",1393545840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yewo3tdl2luoyru63ra4,task_description,resolved
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE",Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754654,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE",Verified the fix in test2,1394233053,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE",Verified the fix in betalabs,1393626056,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE","Change 116114 merged by jenkins-bot:
+Blur the surface when a dialog is opened
+
+https://gerrit.wikimedia.org/r/116114",1393615316,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE","Change 116114 had a related patch set uploaded by Esanders:
+Blur the surface when a dialog is opened
+
+https://gerrit.wikimedia.org/r/116114",1393602975,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+"VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE","This issue is not just for Page Settings rather for all these dialogs :Advanced Settings,Categories,Languages and Keyboard shortcuts page",1393546933,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yewo3tdl2luoyru63ra4,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings>Advanced Settings for that image
+4.Set the position to left and image type to border
+5.Save the page
+6.Reopen the page 
+7.Select the image and open the media settings for it
+
+Observed Result:
+
+TypeError: this.typeInput.getSelectedItem(...) is null appears in the console and also I could not cross out the media settings page for that image and got stuck in VE.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27thfebff&veaction=edit
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13211}",1393541100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_description,resolved
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120690 merged by Catrope:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120690",1395705067,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120691 merged by Catrope:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120691",1395705057,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Looks like its fixed in Betalabs.I tried the bonsai image in this page after the fix has been merge , did not get that error whereas previously I was getting it there:
+http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome",1395703661,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120057 merged by jenkins-bot:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120057",1395701643,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120691 had a related patch set uploaded by Catrope:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120691",1395701490,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120690 had a related patch set uploaded by Catrope:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120690",1395701471,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 120057 had a related patch set uploaded by Mooeypoo:
+Fix 'original dimensions' async call in MediaEdit dialog
+
+https://gerrit.wikimedia.org/r/120057",1395428254,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,*** Bug 62926 has been marked as a duplicate of this bug. ***,1395424182,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"https://bugzilla.wikimedia.org/show_bug.cgi?id=62926 might be a duplicate of this. Although in a more general setting.
+
+Note though that this also occurs for a thumbnail images* (which is the default setting for images inserted by VE).
+
+*This occurs on sv.wp [1] whilst it does not seem to occur on en.wp [2]
+
+[1] https://sv.wikipedia.org/w/index.php?title=User:Andr%C3%A9_Costa_%28WMSE%29/test2&veaction=edit
+[2] https://en.wikipedia.org/w/index.php?title=User:Andr%C3%A9_Costa_%28WMSE%29/test2&veaction=edit
+
+I would also argue for bringing the priority of this up since not being able to close the dialogue window means that any unsaved data in the article is lost. We have already had this occur during a workshop.",1395415054,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Created attachment 14856
+The most recent error appeared on 18th March
+
+**Attached**: {F13215}",1395184657,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Correction: everytime you make it frameless and fullsize, it results into NaNxNaN",1395182307,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Also, observe that for every copy of that image if you make it frameless , the resulting size in wikitext becomes NaNxNaN",1395182036,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"I just reproduced it on betalabs again : http://en.wikipedia.beta.wmflabs.org/wiki/18thMarChrome?veaction=edit
+
+Try the second image
+
+See the screenshot attached.",1395181049,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755943,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,Verified the fix in test2,1394228677,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,Verified the fix in Betalabs,1394052273,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046690,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Change 115939 had a related patch set uploaded by Mooeypoo:
+[wip] Add type 'none' to the media edit dialog
+
+https://gerrit.wikimedia.org/r/115939",1393616786,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"This is the bug ed noticed this morning. 
+
+This should fix the error: https://gerrit.wikimedia.org/r/#/c/115939/",1393549487,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Small modification: It has nothing to do with the image position, just select the image type as border with whatever image position it will throw that error.",1393543498,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Created attachment 14710
+Missing caption section
+
+**Attached**: {F13213}",1393541600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format,"Also , observe in the general settings of the image with such position and format there is not caption section.
+See the screenshot attached",1393541569,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2avmt4q62mzizp4k2qoh,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content","Screenshot
+
+Steps to reproduce:
+
+1.Create a page with VE
+2.Add a bullet list
+3.Add an image as a bulleted item of that list (
+4.Save the page
+5.Reopen the editor
+
+Observed Result:
+As soon as I open the page I get the error:
+ ""Uncaught TypeError: Cannot call method 'getOffset' of null""
+
+And then clicking on Bullet list icon again does not un-bullet the list
+Also, every time I switch to this page from other window/page it shows this error again and again. 
+
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/27thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13207}",1393538400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_description,resolved
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content",Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755222,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content",verified the fix in test2,1394230476,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content",Verified the fix in betalabs,1393888306,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content","Change 116172 merged by jenkins-bot:
+Don't allow getNearestCorrectOffset to return -1
+
+https://gerrit.wikimedia.org/r/116172",1393631799,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+"VisualEditor: Getting ""Uncaught TypeError: Cannot call method 'getOffset' of null"" error when I open a page that contains a bullet list with floated content","Change 116172 had a related patch set uploaded by Esanders:
+Don't allow getNearestCorrectOffset to return -1
+
+https://gerrit.wikimedia.org/r/116172",1393629113,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6onfy2t6xjcwwmj3od5r,task_subcomment,NA
+Using the language link tool in the sidebar when inside VisualEditor loses the edit without warning,"A user at en.wp reported today that you can add interlanguage links while you're in VE. The last step when doing so means the whole page gets reloaded, so whatever was done in VE until that moment gets lost. I am not aware of ways to prevent this, and there is no indication in VE that this will happen when you start that procedure.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Whiteboard**: u=dev c=backend p=0
+**See Also**:
+{T54105}",1393520520,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-3ttlflt7d3qnjlwwyi2n,task_description,resolved
+Using the language link tool in the sidebar when inside VisualEditor loses the edit without warning,"I think this is no longer a problem.
+
+In the most common case, where the Wikidata item already exists, ""Edit links"" is just a link to wikidata.org, and it displays a browser warning if clicked while VisualEditor is open (like any other link).
+
+{F26721044}
+
+When the Wikidata item doesn't exist, it's trickier, since the ""Add links"" button open a dialog that lets you connect the pages. But this also works mostly fine: after completing the dialog, you still get the browser warning, and will not lose your changes made in VisualEditor unless you confirm that you want to reload the page.
+
+(I found a page I could test this on via Special:UnconnectedPages.)
+
+{F26721137}
+
+Video recording: 
+{F26721091}
+
+The experience could be better (e.g. Wikibase's page connect dialog could update the page rather than reloading it), but I think it is fine as it is, especially since this feels like a corner case.",1540258002,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-3ttlflt7d3qnjlwwyi2n,task_subcomment,NA
+Using the language link tool in the sidebar when inside VisualEditor loses the edit without warning,"(Filed initially as WD, thought you hadn't mentioned this detail, re-filed again as VE. Close enough.)",1393521024,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-3ttlflt7d3qnjlwwyi2n,task_subcomment,NA
+Using the language link tool in the sidebar when inside VisualEditor loses the edit without warning,"Wikidata bug, not VE bug.",1393520906,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3ttlflt7d3qnjlwwyi2n,task_subcomment,NA
+"VisualEditor: Deal with universal types like mw:Error, mw:ExpandedAttrs, mw:Placeholder","Some types like mw:ExpandedAttrs are universal, meaning they can apply to any element and their presence shouldn't be taken into account when figuring out which node handler to invoke. The node handlers themselves probably do need to make decisions based on their presence, but that's fine, they can do that already.
+
+For now the approach I'm considering is to add the concept of a universal RDFa type, which will be ignored by ve.dm.ModelRegistry#matchElement for all purposes (including the ""if not all mw: types are matched it's not a match"" logic and all of that). mw:ExpandedAttrs and mw:Error (the latter would be introduced by bug 50788) would be universal types. mw:Placeholder wouldn't be one, because it needs to trigger alienation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1393458480,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tufvyhfqrhacbhpyytqx,task_description,resolved
+"VisualEditor: Deal with universal types like mw:Error, mw:ExpandedAttrs, mw:Placeholder","We've dealt with it by introducing `allowedRdfaTypes` (in 2015: T98999). Nodes that wish to handle the ""universal"" types can do it like this:
+```
+ve.dm.MWImageNode.static.allowedRdfaTypes = [ 'mw:Error' ];
+```
+The required handling is different for each node type, so the above is not set globally, each node type has to be ""opted in"". ",1652133850,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tufvyhfqrhacbhpyytqx,task_subcomment,NA
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings of that image
+4.Insert another image inside it in the General Settings section
+5.Go to Media Settings for that image and set the Image type as Frameless and keep the position to right
+
+Observed Result:
+The image resize handlers appear at all four corners instead of appearing only at bottom left corner
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393456440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ypg6arsu3fplwmwytrtn,task_description,resolved
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,"yes, now it is fixed.",1404860737,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ypg6arsu3fplwmwytrtn,task_subcomment,NA
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,This appears to now be fixed.,1404850889,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ypg6arsu3fplwmwytrtn,task_subcomment,NA
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,*** Bug 62283 has been marked as a duplicate of this bug. ***,1404850803,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ypg6arsu3fplwmwytrtn,task_subcomment,NA
+VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor,"Created attachment 14695
+screenshot
+
+**Attached**: {F13084}",1393457058,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ypg6arsu3fplwmwytrtn,task_subcomment,NA
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again","Use Existing reference dialog  box
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Reference >Use an existing reference
+3.Type a search term in the search box
+4.Select a reference from the search result.
+5.Now again attempt to add another existing reference 
+
+Observed Result:
+When the page of existing references opens up it still keeps the search term from previous attempt and shows the search results , it should rather clear the previous search term and let user to start over.
+This issue also occurs for new media adding dialog
+
+See the screenshots attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13051}",1393447320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o4kh74skefuz5dgfcvx5,task_description,resolved
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again",verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27thmarChrome&veaction=edit,1395944703,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o4kh74skefuz5dgfcvx5,task_subcomment,NA
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again","Change 120566 merged by jenkins-bot:
+Blank the reference and media search queries when closing dialogs
+
+https://gerrit.wikimedia.org/r/120566",1395870578,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4kh74skefuz5dgfcvx5,task_subcomment,NA
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again","Change 120566 had a related patch set uploaded by Jforrester:
+Blank the reference and media search queries when closing dialogs
+
+https://gerrit.wikimedia.org/r/120566",1395682883,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4kh74skefuz5dgfcvx5,task_subcomment,NA
+"VisualEditor: Clear the previous search term while opening the ""Use an existing reference"" and ""Insert Media"" dialog again","Created attachment 14690
+New Media Add dialog
+
+**Attached**: {F13052}",1393447363,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o4kh74skefuz5dgfcvx5,task_subcomment,NA
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),"Specifically on this page, https://it.wikipedia.org/w/index.php?title=Categoria:Aggiornare_-_economia&veaction=edit .
+I tried adding all those categories to my sandbox but they work fine there (https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&oldid=64431369&veaction=edit ), same if I add the rest of the content of that page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72303",1393352640,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-742b3uk4lvclm4lzhhp4,task_description,open
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),"(In reply to Elitre from comment #3)
+> So... is there a bug about how VE needs to be doing that yet?
+
+I thought so, but no; re-opening as said bug.",1413922420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-742b3uk4lvclm4lzhhp4,task_subcomment,NA
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),So... is there a bug about how VE needs to be doing that yet?,1413920704,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-742b3uk4lvclm4lzhhp4,task_subcomment,NA
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),"The only two categories on this page directly are listed by VE. Obviously, we can't include transcluded categories.",1413902741,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-742b3uk4lvclm4lzhhp4,task_subcomment,NA
+VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated),Very odd.,1401416815,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-742b3uk4lvclm4lzhhp4,task_subcomment,NA
+"VisualEditor:  ""Notices"" tooltip says ""$1 notices"" rather than the correct number","Steps to Reproduce:
+1. Open a page (like Today's Featured Article) that will have notices.
+2. Hover over the ""Notices"" triangle.
+3. Read the tooltip.
+
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1393309740,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-evkkc4zlooiizhrujg2e,task_description,resolved
+"VisualEditor:  ""Notices"" tooltip says ""$1 notices"" rather than the correct number","Change 115826 merged by jenkins-bot:
+Don't use a changeable tooltip for edit notices
+
+https://gerrit.wikimedia.org/r/115826",1393464234,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-evkkc4zlooiizhrujg2e,task_subcomment,NA
+"VisualEditor:  ""Notices"" tooltip says ""$1 notices"" rather than the correct number","Change 115826 had a related patch set uploaded by Jforrester:
+Don't use a changeable tooltip for edit notices
+
+https://gerrit.wikimedia.org/r/115826",1393458868,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-evkkc4zlooiizhrujg2e,task_subcomment,NA
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list","Steps to reproduce:
+
+- Create a numbered list as follows:
+```
+1.item 1
+2.
+3.item 3
+```
+- Now add indentation to the third item , so it becomes:
+```
+1.item 1
+2.
+      1.item 3
+```
+- Now place the cursor just before the item 3 and press delete
+
+Instead of having the item 3 unindented the resulting list comes up as: 
+```
+1.item 1
+2. 1. item 3
+```
+See the screenshot: {F12837}
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page: http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit
+
+**See Also**: {T65051}",1393270740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_description,resolved
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list",What do you mean with “more sensibly”? I can still reproduce the visual issue described in initial report.,1701984700,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_subcomment,NA
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list",This behaves more sensibly now.,1701963109,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_subcomment,NA
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list","Actually, this seems to duplicate T54557, which refers to OpenOffice and Word for external consistency.",1650764976,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_subcomment,NA
+"VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list","Rendering has changed since the first report: now, an empty line with a “Insert paragraph” slug displays after `2.`.
+
+Yet, whatever you click on this slug (i.e. whatever you add an empty paragraph starting item 2), Parsoid strips it. This means: even if you don’t press backspace, Parsoid will merge anyway item 3 with empty item 2:
+```lang=sh
+$ echo -e ""#item1\n#\n##item3"" | php bin/parse.php --wt2wt
+#item1
+##item3
+```
+
+However, if item 2 is not empty, the current behavior seems expected, so this could be declined.",1650764486,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-hmpbfsja6fcgdvssmu4u,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","The proper order is #REDIRECT[[Whatever]], then categories and other stuff.  If you place the redirect anywhere other than the very top of the page, it won't work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1393270500,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_description,resolved
+"VisualEditor: Place redirects at the top of the page, not the bottom",Will mark this as fixed in favour of Parsoid bug 53508 then.,1393537213,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Change 115309 merged by jenkins-bot:
+Always try to put redirects at index 0, offset 0
+
+https://gerrit.wikimedia.org/r/115309",1393287020,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","(In reply to Gabriel Wicke from comment #7)
+> Moving back to VE; Position of inline metadata is the client's
+> responsibility. Our long-term solution is to move that metadata out of the
+> content altogether.
+
+This is semantically non-positional meta-data that breaks if not in a particular syntactical position…",1393281899,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom",Moving back to VE; Position of inline metadata is the client's responsibility. Our long-term solution is to move that metadata out of the content altogether.,1393280047,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Change 115287 merged by jenkins-bot:
+Always try to put redirects at index 0, offset 0
+
+https://gerrit.wikimedia.org/r/115287",1393279819,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Change 115309 had a related patch set uploaded by Catrope:
+Always try to put redirects at index 0, offset 0
+
+https://gerrit.wikimedia.org/r/115309",1393279725,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","(In reply to WhatamIdoing from comment #2)
+> If ""rendering in place"" means ""where the cursor is"", then that's not
+> happening.  It's placing the redirect at the bottom of the page even if your
+> cursor is at the top or in the middle.
+
+No, it's rendering ""in place"" in the HTML document; VE just puts meta-items at the end of the HTML string (because internal logic of what MW's parser does and doesn't prefer is a decision for Parsoid), so Parsoid renders this at the end of the wikitext, which helpfully doesn't work.
+
+(In reply to Gerrit Notification Bot from comment #3)
+> Change 115287 had a related patch set uploaded by Jforrester:
+> Always try to put redirects at index 0, offset 0
+> 
+> https://gerrit.wikimedia.org/r/115287
+
+This is a hack to make VE try to insert it right at the top, which may not work in all cases but at least should patch over the issue.",1393276720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Change 115287 had a related patch set uploaded by Jforrester:
+Always try to put redirects at index 0, offset 0
+
+https://gerrit.wikimedia.org/r/115287",1393276161,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","If ""rendering in place"" means ""where the cursor is"", then that's not happening.  It's placing the redirect at the bottom of the page even if your cursor is at the top or in the middle.",1393275826,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+"VisualEditor: Place redirects at the top of the page, not the bottom","Logically, Parsoid should decide where in the page such things go (right now it just renders in place); VisualEditor could hack around this by putting it at the top of the HTML, but that's not a scalable fix (and will likely break other things).
+
+Parsoid, what do you think?",1393270693,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-at437ap3jp2nwtfjwgi6,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"When you set a redirect in VisualEditor, it doesn't display anything, so it looks like it didn't work.",1393270380,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_description,resolved
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 273391 merged by jenkins-bot:
+Show redirect target inside target
+
+[[https://gerrit.wikimedia.org/r/273391]]",1458255280,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 273397 merged by jenkins-bot:
+Make mediawiki.action.view.redirectPage available on mobile
+
+[[https://gerrit.wikimedia.org/r/273397]]",1456445600,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 273397 had a related patch set uploaded (by Alex Monk):
+Make mediawiki.action.view.redirectPage available on mobile
+
+[[https://gerrit.wikimedia.org/r/273397]]
+",1456444980,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 271701 abandoned by Alex Monk:
+Move redirects out of the meta list into actual nodes
+
+Reason:
+Per Ed, in favour of a different commit
+
+[[https://gerrit.wikimedia.org/r/271701]]",1456443686,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 273391 had a related patch set uploaded (by Alex Monk):
+Show redirect target inside target
+
+[[https://gerrit.wikimedia.org/r/273391]]
+",1456443122,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"As discussed on IRC there are two approaches: Make the redirect render as a node (the patch just submitted) or keep it in metadata and render a new control above the document.
+
+Having it as a node gives us selection and delete for free, but there are no systems in place to make that node un-moveable, or un-copyable. Given that an unmovebale node can only ever be at the start or end of a document (by definition) I'm not sure we need to support that. 
+
+If all we need is a bit of rendering in the surface we can add a styled button above the document showing the redirect, and which launches the dialog.",1455902303,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Change 271701 had a related patch set uploaded (by Alex Monk):
+Move redirects out of the meta list into actual nodes
+
+[[https://gerrit.wikimedia.org/r/271701]]
+",1455837699,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Note that in some cases redirects actually have some content, so are not necessarily blank.",1443891375,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,Still valid.,1443036053,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,">>! In T63861#648996, @Krenair wrote:
+> When checking that I was right about the valid positioning of redirects, I found that Parsoid implements redirects wrong (or rather, differently to MediaWiki core's parser): it seems quite happy to accept a redirect that is anywhere in the document.
+
+Reported as T88081",1422591190,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"Created attachment 15753
+In this case, I re-pointed a redirect, so it was displayed, and now it *looks like* changing it caused the redirect to be removed rather than changed.
+
+**Attached**: {F12829}",1403805225,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"I spoke to Roan about what I would need to know to do this today. After some explanation we realised that this relies on meta items (e.g. redirects) having the possibility of being visible (at the moment they are just stripped from the model data so we don't know where they are). That is somewhere on his work list but he is not particularly close to starting it.
+
+Also, I thought for a moment that since a valid redirect must be in a certain position (at the top of the document - if it's under something else then it's actually just a list element starting with 'redirect' and with a link to the target page), we could perhaps rely on that to make it visible. But I suspect that would be a pretty ugly solution.
+
+When checking that I was right about the valid positioning of redirects, I found that Parsoid implements redirects wrong (or rather, differently to MediaWiki core's parser): it seems quite happy to accept a redirect that is anywhere in the document.",1397256310,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,This was mis-labelled; sorry for the confusion.,1397162060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Show something other than a blank page when editing a redirect page,"We should probably show the same as the MW-rendered redirect:
+
+https://bits.wikimedia.org/static-1.23wmf14/skins/common/images/redirectltr.png
+
+… or ideally a better system that doesn't use an image, and fix MW whilst we're at it.",1393271027,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gqge6ob2qbmzizzddum7,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,"I find the whole thing to be rather confusing. It's much too technical. Also it partially mixes the concept of ToC with that of a structure editor. It has some widgets on the ToC (add template, add content, change order) and others inside the editor (Add param, del param, del template). This is terribly inconsistent. And makes you having to scan the screen too much.
+
+Also by default it tries to introduce you to the concept of chained templates ( starttemplate, content, endtemplate ). Which is rather complex and often not even needed.
+
+This needs serious work to make the usability much more consistent and predictable. I would take the following into account.
+
+
+1: Make a decision. Is it a toc, or a structure editor ? If the latter, then put all structure controls in the structure editor. Otherwise avoid putting them in there.
+2: By default, don't show the buttons for chained/wrapping templates. Instead, only add them if Parsoid assumes there is content wrapping happening. For new templates insertion, make an addition to templatedata ""openedBy, closedBy"", and only add the buttons if the template data says they are needed.
+3: Keyboard control. I try tab key to move focus to the ""Add template"" button next to the field. Seems this is captured by the UI, so I cannot move focus that way. It seems I can only click the button. BAD... Also seems that the add button and the delete buttons do not have a :focus state. Or rather, it seems that buttons have focus state, but the focusable element is the <a> inside it, so it doesn't really work.
+4: The layout of the params view.. I don't know how to do it better right now, but this needs work. too many lines/blocks, it's too cluttered. Do you need a double line separator if you have a heading ?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393171260,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-z2cr4me55wbuu3qesrhc,task_description,resolved
+VisualEditor: Improve the UX of the template editor,"(In reply to James Forrester from comment #3)
+> Most of these points are met by the re-work of these that has been worked on
+> for months as part of the citation work – see
+> http://mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog but broadly a
+> much simplified version of the full transclusion dialog is being made
+> (provisionally I'm calling it the template dialog) which removes the TOC and
+> makes a lot of other changes.
+> 
+> There's also bug 53604 which tracks improvements in general; should we
+> factor out the unique parts of this bug (not quite sure which)?
+> 
+> (In reply to Derk-Jan Hartman from comment #0)
+> > I find the whole thing to be rather confusing. It's much too technical. Also
+> > it partially mixes the concept of ToC with that of a structure editor. It
+> > has some widgets on the ToC (add template, add content, change order) and
+> > others inside the editor (Add param, del param, del template). This is
+> > terribly inconsistent. And makes you having to scan the screen too much.
+> 
+> Add param – moved to ToC for transclusion dialog, and to bottom for template
+> dialog.
+
+{{done}}
+
+> Del param – currently being left on each param; we could move it, but not
+> sure where?
+> 
+> Del template – will not available in template dialog; being left in place
+> right now for transclusion dialog.
+
+{{done}}
+
+[Snip]
+
+> > For new templates insertion, make an addition to templatedata
+> > ""openedBy, closedBy"", and only add the buttons if the template data says
+> > they are needed.
+> 
+> This is a nice idea, though it could get very complex (""this template can be
+> opened by these four templates, or these two templates in conjunction, but
+> not following this template, except on Category: pages, but only with
+> language conversion switched on, unless it's a Tuesday…"").
+
+I've spun this out to its own bug, bug 62338.
+
+> > 3: Keyboard control. I try tab key to move focus to the ""Add template""
+> > button next to the field. Seems this is captured by the UI, so I cannot move
+> > focus that way. It seems I can only click the button. BAD... Also seems that
+> > the add button and the delete buttons do not have a :focus state. Or rather,
+> > it seems that buttons have focus state, but the focusable element is the <a>
+> > inside it, so it doesn't really work.
+> 
+> Yeah, there's some bits of keyboard work that need improvement, and the
+> tension between accessibility and utility is acute here.
+
+Partially done; OOjs UI buttons are not, which is bug 62337.
+
+> > 4: The layout of the params view.. I don't know how to do it better right
+> > now, but this needs work. too many lines/blocks, it's too cluttered. Do you
+> > need a double line separator if you have a heading ?
+> 
+> See
+> https://commons.wikimedia.org/wiki/File:VE-reference-dailog-design-05b.png
+
+{{done}}
+
+(In reply to Elitre from comment #4)
+> What about a drop-down menu with a list of most used templates (on the
+> project or chosen by the single user)? I think it was asked somewhere else,
+> but it's being brought up again on en.wp so I hope this is the right place
+> to mention it. I know something like this will be added to the referencing
+> system, but it'd be great to have it for more general purposes as well.
+
+That's bug 53590.
+
+Consequently, I'm closing this bug as ""FIXED"", which is not quite right but is a better disposal that the alternatives.",1394130209,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,"What about a drop-down menu with a list of most used templates (on the project or chosen by the single user)? I think it was asked somewhere else, but it's being brought up again on en.wp so I hope this is the right place to mention it. I know something like this will be added to the referencing system, but it'd be great to have it for more general purposes as well.",1393707727,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,"Most of these points are met by the re-work of these that has been worked on for months as part of the citation work – see http://mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog but broadly a much simplified version of the full transclusion dialog is being made (provisionally I'm calling it the template dialog) which removes the TOC and makes a lot of other changes.
+
+There's also bug 53604 which tracks improvements in general; should we factor out the unique parts of this bug (not quite sure which)?
+
+(In reply to Derk-Jan Hartman from comment #0)
+> I find the whole thing to be rather confusing. It's much too technical. Also
+> it partially mixes the concept of ToC with that of a structure editor. It
+> has some widgets on the ToC (add template, add content, change order) and
+> others inside the editor (Add param, del param, del template). This is
+> terribly inconsistent. And makes you having to scan the screen too much.
+
+Add param – moved to ToC for transclusion dialog, and to bottom for template dialog.
+
+Del param – currently being left on each param; we could move it, but not sure where?
+
+Del template – will not available in template dialog; being left in place right now for transclusion dialog.
+
+> Also by default it tries to introduce you to the concept of chained
+> templates ( starttemplate, content, endtemplate ). Which is rather complex
+> and often not even needed.
+
+Indeed, hence the split.
+
+> This needs serious work to make the usability much more consistent and
+> predictable.
+
+Which is why we've been working on this for months. :-)
+
+> I would take the following into account.
+
+> 1: Make a decision. Is it a toc, or a structure editor ? If the latter, then
+> put all structure controls in the structure editor. Otherwise avoid putting
+> them in there.
+
+See above.
+
+> 2: By default, don't show the buttons for chained/wrapping templates.
+> Instead, only add them if Parsoid assumes there is content wrapping
+> happening.
+
+See above.
+
+> For new templates insertion, make an addition to templatedata
+> ""openedBy, closedBy"", and only add the buttons if the template data says
+> they are needed.
+
+This is a nice idea, though it could get very complex (""this template can be opened by these four templates, or these two templates in conjunction, but not following this template, except on Category: pages, but only with language conversion switched on, unless it's a Tuesday…"").
+
+> 3: Keyboard control. I try tab key to move focus to the ""Add template""
+> button next to the field. Seems this is captured by the UI, so I cannot move
+> focus that way. It seems I can only click the button. BAD... Also seems that
+> the add button and the delete buttons do not have a :focus state. Or rather,
+> it seems that buttons have focus state, but the focusable element is the <a>
+> inside it, so it doesn't really work.
+
+Yeah, there's some bits of keyboard work that need improvement, and the tension between accessibility and utility is acute here.
+
+> 4: The layout of the params view.. I don't know how to do it better right
+> now, but this needs work. too many lines/blocks, it's too cluttered. Do you
+> need a double line separator if you have a heading ?
+
+See https://commons.wikimedia.org/wiki/File:VE-reference-dailog-design-05b.png",1393526920,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,That would be https://bugzilla.wikimedia.org/show_bug.cgi?id=49772 I think? (although not specific to the missing TD case).,1393526600,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+VisualEditor: Improve the UX of the template editor,"Add way to access/view /doc, if TemplateData is not visible.",1393526222,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-z2cr4me55wbuu3qesrhc,task_subcomment,NA
+Flow: Parsoid HTML for videos doesn't work,"eg. https://ca.wikipedia.org/wiki/Tema:T3edcbkgt2ns31ff 
+
+(Old example: http://ee-flow.wmflabs.org/w/index.php?title=User_talk:Quiddity&topic_postId=rpnkneesuic1rsx8&workflow=rnhr0vbpmcq1wj5m#flow-post-rpnkneesuic1rsx8 )
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: http://ee-flow.wmflabs.org/w/index.php?title=User_talk:Quiddity&topic_postId=rpnkneesuic1rsx8&workflow=rnhr0vbpmcq1wj5m#flow-post-rpnkneesuic1rsx8",1393014300,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-ilx4l4y6zoryzl6763pk,task_description,duplicate
+Flow: Parsoid HTML for videos doesn't work,"> The ""thumb"" works ok
+
+Not really. A thumbnail is created, but clicking it doesn't play the video, it leads to the File page.
+
+Reported at [[ https://ca.wikipedia.org/wiki/Fitxer:This_is_the_Wikimedia_Foundation.webm | w:ca.Tema:T3edcbkgt2ns31ff ]].",1462557739,PHID-USER-h6xz2shsbvhdtx5puurj,False,PHID-TASK-ilx4l4y6zoryzl6763pk,task_subcomment,NA
+Flow: Parsoid HTML for videos doesn't work,"Copying from merged:
+
+>>! In T72532#769902, @Amire80 wrote:
+> Link: https://he.wikipedia.org/wiki/%D7%A0%D7%95%D7%A9%D7%90:S1wm63huv90migi0
+> 
+> Thanks for the reporting.
+
+",1423511030,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-ilx4l4y6zoryzl6763pk,task_subcomment,NA
+Flow: Parsoid HTML for videos doesn't work,"fresh examples of webm video failing to render at fullsize, and ogg audio failing to display its player: https://www.mediawiki.org/wiki/Topic:S52i2un1zblzd8s8#flow-post-s5fley5jhc8a8pub (Does this bug/issue also cover audio files? I'm not sure whether to rename, or fork.)",1415046152,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-ilx4l4y6zoryzl6763pk,task_subcomment,NA
+Flow: Parsoid HTML for videos doesn't work,"This is partly the same as bug 61786 (the image HTML generated by Parsoid is different from PHP parser output), but there are additional problems for video links.
+
+For both [[File:Sequence-Test.ogv]] and [[ File:Sequence-Test.ogv|thumb]] in a Flow post, the links to the video are an invalid <a href=""./File:Sequence-Test.ogv"">. The HTML doesn't include a <video> tag, just an <img> tag. The full-size video uses the original .ogv file as the src of the nested image tag, which obviously doesn't work, while the thumb video correctly uses the Sequence-Test.ogv.jpg thumbnail.
+
+Furthermore, the resulting HTML doesn't seem to trigger the MwEmbedSupport/TimedMediaHandler RL modules that add player controls and such to the video. Maybe those look for <div class=""mediaContainer""> or the <video> tag.
+
+O VisualEditor team, do you have CSS and JS that make Parsoid video HTML work? :)",1394075239,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ilx4l4y6zoryzl6763pk,task_subcomment,NA
+VisualEditor: Extension tags that create block-level items aren't allowed inside pre-formatted rows in MW,"If you add a formula (or other inline item) to a normal paragraph, everything works in VE consistently with MW (yay).
+
+If you add a formula (or other inline item) to a pre-formatted paragraph, everything still works works (yay).
+
+If you add a gallery (or other block item) to a normal paragraph, everything works in VE consistently with MW (yay).
+
+If you add a gallery (or other block item) to a pre-formatted paragraph, VE tries to let you do that, and MW decides retroactively that the paragraph wasn't actually pre-formatted (boo), unless it's a <pre>-formatted rather than indent-pre-formatted block, in which case galleries don't work.
+
+Not tested with Headings, but there's probably similar wonkiness there too.
+
+*sighs*
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1393014300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p44y73skf774qafrhxfm,task_description,resolved
+VisualEditor: Extension tags that create block-level items aren't allowed inside pre-formatted rows in MW,Looks like this is now fixed.,1493661754,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p44y73skf774qafrhxfm,task_subcomment,NA
+VisualEditor: Extension tags that create block-level items aren't allowed inside pre-formatted rows in MW,Sounds like a Parsoid issue.,1393952314,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-p44y73skf774qafrhxfm,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"We are currently using a hack[1] to make VisualEditor to be the default edit mode on Portuguese Wikibooks.
+
+Could someone make it the default in the right way?
+
+[1] https://pt.wikibooks.org/wiki/MediaWiki:Gadget-VisualEditorByDefault.js
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://pt.wikibooks.org/wiki/T%C3%B3pico:Wikilivros_Discuss%C3%A3o:Portal_comunit%C3%A1rio/Testes_com_o_Editor_Visual_no_Wikilivros/resposta_%284%29",1393011960,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-jyfxkeisbvohmunciamd,task_description,resolved
+Make VisualEditor opt-out on Portuguese Wikibooks,Thanks!,1393327454,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"(In reply to Gerrit Notification Bot from comment #6)
+> Change 115213 merged by jenkins-bot:
+> Make VisualEditor opt-out on Portuguese Wikibooks
+> 
+> https://gerrit.wikimedia.org/r/115213
+Deployed now.",1393287705,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"Change 115213 merged by jenkins-bot:
+Make VisualEditor opt-out on Portuguese Wikibooks
+
+https://gerrit.wikimedia.org/r/115213",1393286656,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,Scheduled for 16:00 PST today.,1393271991,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"Change 115213 had a related patch set uploaded by Jforrester:
+Make VisualEditor opt-out on Portuguese Wikibooks
+
+https://gerrit.wikimedia.org/r/115213",1393268819,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"(In reply to Helder from comment #2)
+> The link is in the URL field
+
+Sorry, I missed that. If there have been no objections from the community I guess it is OK to proceed then.",1393069463,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"The link is in the URL field, but there is little activity there currently, so I doubt there will be more comments...",1393063683,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Make VisualEditor opt-out on Portuguese Wikibooks,"I assume, because the JS is in place by default, that community consensus has already been reached? Could you provide a link for completeness' sake?",1393047051,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-jyfxkeisbvohmunciamd,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Please uninstall the Flow extension from Meta-Wiki. Relevant discussion: <https://meta.wikimedia.org/w/index.php?title=Meta:Babel&curid=69328&diff=16251209&oldid=16240965>.
+
+The extension was installed in <https://gerrit.wikimedia.org/r/114088>.
+
+Explicit consensus for complete removal (and lack of consensus for any partial survival of the extension): https://meta.wikimedia.org/w/index.php?title=Meta:Babel&oldid=16337330#Proposal_to_remove_Flow_on_Meta-Wiki",1392946860,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_description,resolved
+Remove Flow from Meta-Wiki,">>! In T63729#3967503, @Alsee wrote:
+>>>! In T63729#3957407, @Mattflaschen-WMF wrote:
+>> This applies to any extension with log types, not just StructuredDiscussions.  It's expected behavior.  There is no solution other than code duplication (which is okay if that's the best solution, but no one has explained why it is in this case).
+> 
+> The Flow logs are OK as-is, but I have a possible generic solution that can handle (probably) any future extension. Wouldn't it be possible to run the logs through the extension and store the results as plaintext? Then you don't need the code anymore. Any links would generally point to non-existent objects anyway.
+
+But then users wouldnt be able to select language. It also makes searching through logs much more difficult (see issues with checkuser logs).
+",1518540335,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3957407, @Mattflaschen-WMF wrote:
+> This applies to any extension with log types, not just StructuredDiscussions.  It's expected behavior.  There is no solution other than code duplication (which is okay if that's the best solution, but no one has explained why it is in this case).
+
+The Flow logs are OK as-is, but I have a possible generic solution that can handle (probably) any future extension. Wouldn't it be possible to run the logs through the extension and store the results as plaintext? Then you don't need the code anymore. Any links would generally point to non-existent objects anyway.
+
+",1518532265,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3948471, @MarcoAurelio wrote:
+> 1 can be fixed with a rWMME entry
+
+Before we identify an alternative technical solution (e.g. code duplication to put log formatting in WikimediaMessages), we should first identify a technical problem with the simplest solution (deleting SD boards, preventing new ones from being created, and leaving the extension installed).
+
+>>! In T63729#3950882, @Alsee wrote:
+> Considering that the extension is uninstalled, I'd say those log issues are pretty insignificant.
+> 
+> However I think it suggests that new extension development should have a checklist item to consider and test uninstallation. We wouldn't want some other extension causing hard-to-reverse problems in the future.
+
+This applies to any extension with log types, not just StructuredDiscussions.  It's expected behavior.  There is no solution other than code duplication (which is okay if that's the best solution, but no one has explained why it is in this case).",1518148819,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Actually please follow the discussion at T186463. This task has been long closed. Thanks.,1517997687,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Considering that the extension is uninstalled, I'd say those log issues are pretty insignificant.
+
+However I think it suggests that new extension development should have a checklist item to consider and test uninstallation. We wouldn't want some other extension causing hard-to-reverse problems in the future.",1517958062,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"1 can be fixed with a rWMME entry as for 2 I'd not care much, as the Topics are either converted to Wikitext using the script, or deleted, or both. As for Meta-Wiki, nothing broke after uninstallation.",1517910896,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069153, @Catrope wrote:
+>>>! In T63729#3068503, @demon wrote:
+>>>>! In T63729#3068479, @Dereckson wrote:
+>>> @demon @MZMcBride The collaboration team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+>>> 
+>> 
+>> Integrity? What?
+>> 
+> 
+> The concern here was that the rendering of e.g. https://meta.wikimedia.org/wiki/Special:Contributions/Flow_talk_page_manager would break, because the Topic namespace would go away.
+
+It's also the actual logs:
+
+1. Valid log entries don't render, so you just get ""flow-delete-post (Test)"", instead of something like ""deleted a post on ""Test"" on Structured Discussions/Sandbox (delete test post)"" (these are different examples, but the same action type; correct version also has proper links): https://en.wikipedia.org/w/index.php?title=Special%3ALog&type=delete&user=Fram&page=&year=2016&month=9&tagfilter=&subtype=
+2. The namespace stops existing, which still causes breakage even with https://wikitech.wikimedia.org/wiki/Flow .  See https://en.wikipedia.org/w/index.php?title=Special%3ALog&type=&user=Roan+Kattouw+%28WMF%29&page=&year=2016&month=-1&tagfilter=&hide_thanks_log=1&hide_patrol_log=1&hide_tag_log=1&hide_review_log=1 (namespace is missing even for the workaround deletes).",1517879734,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,I would like to thank all participants in this and related tasks here on Phabricator for their communication and handling of what was and is a delicate and sometimes tense matter on the wikis. I truly appreciate it from everyone.,1488496284,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069224, @Catrope wrote:
+>>>! In T63729#3069218, @demon wrote:
+>>>> , but otherwise that plan sounds good. Let's get this on Wikitech.
+>>> It's already there, for the deployment window that's right now. Matt is doing the cawiki change, I'll coordinate with him.
+>> 
+>> I meant more a [[Uninstalling Flow]]
+> 
+> Oh, the procedure for it, gotcha. Will do that right after I do it on meta so it's fresh in my mind.
+
+Done now: https://wikitech.wikimedia.org/wiki/Flow",1488496026,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,This is now done,1488495297,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVqRM-z1lCyyDMEPvQd9} [2017-03-02T22:46:23Z] <catrope@tin> Synchronized dblists/: T63729: disable Flow on metawiki (duration: 00m 58s)",1488494784,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 333860 merged by Catrope:
+[operations/mediawiki-config] Remove Flow from Meta-Wiki
+
+[[https://gerrit.wikimedia.org/r/333860]]
+",1488494481,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069218, @demon wrote:
+>>> , but otherwise that plan sounds good. Let's get this on Wikitech.
+>> It's already there, for the deployment window that's right now. Matt is doing the cawiki change, I'll coordinate with him.
+> 
+> I meant more a [[Uninstalling Flow]]
+
+Oh, the procedure for it, gotcha. Will do that right after I do it on meta so it's fresh in my mind.",1488492925,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069212, @Catrope wrote:
+>>>! In T63729#3069205, @demon wrote:
+>> I'm not sure we need `deleteBatch.php` in this case since it's already down to just one page
+> 
+> We do need it, there is more than one topic page: https://meta.wikimedia.org/wiki/Special:AllPages/Topic:
+> 
+
+Ah ok, I understand what you mean.
+
+>> , but otherwise that plan sounds good. Let's get this on Wikitech.
+> It's already there, for the deployment window that's right now. Matt is doing the cawiki change, I'll coordinate with him.
+
+I meant more a [[Uninstalling Flow]]",1488492852,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3069205, @demon wrote:
+> I'm not sure we need `deleteBatch.php` in this case since it's already down to just one page
+
+We do need it, there is more than one topic page: https://meta.wikimedia.org/wiki/Special:AllPages/Topic:
+
+> , but otherwise that plan sounds good. Let's get this on Wikitech.
+It's already there, for the deployment window that's right now. Matt is doing the cawiki change, I'll coordinate with him.
+",1488492775,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I'm not sure we need `deleteBatch.php` in this case since it's already down to just one page, but otherwise that plan sounds good. Let's get this on Wikitech.",1488492613,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3068503, @demon wrote:
+>>>! In T63729#3068479, @Dereckson wrote:
+>> @demon @MZMcBride The collaboration team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+>> 
+> 
+> Integrity? What?
+> 
+
+The concern here was that the rendering of e.g. https://meta.wikimedia.org/wiki/Special:Contributions/Flow_talk_page_manager would break, because the Topic namespace would go away. Flow also doesn't let you delete pages in the Topic namespace, and without Flow the namespace doesn't exist. So the way I worked around this on enwiki was:
+- Uninstall Flow
+- Temporarily add `$wgExtraNamespaces[2600] = 'Topic';` to the config
+- Use `deleteBatch.php` to delete all pages in the Topic namespace
+- Remove the `$wgExtraNamespaces` config
+That's a bit ugly, but we should just do the same thing on metawiki, since there's only a test board there and the only real board was transwikied. If we ever wanted to reinstall Flow there, we could undelete the relevant pages: they wouldn't be gone forever, they just wouldn't be viewable or undeletable without reinstalling Flow (because of content model issues).
+
+I've scheduled this (the uninstall + namespace + deleteBatch dance) for the deployment window we already had (for T159047) at 22:00 UTC (i.e. 7 minutes from now).",1488491574,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"There were two flow boards: the ORES talk page has been moved to mw.org and the contributions can be seen there (also in Special:Contributions). As for the development test page, I daresay I won't miss that. The comments on there were: 1 thread of complaint and 1 thread of test. Given the clear, explicit consensus to remove the extension in the RfC, this isn't an excuse not to honour it.",1488480410,PHID-USER-q4v6ujukzx2pt3y5kogz,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3068479, @Dereckson wrote:
+> @demon @MZMcBride The collaboration team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+> 
+
+Integrity? What?
+
+> To remove the extension is possible, but will be at the detriment of the capability to explore past contributions.
+
+Why did we not have this discussion with enwiki?",1488478469,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"@demon @MZMcBride The collaboration team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+
+As much, as an alternative discussion, it's offered to keep the extension, so it's still possible to explore  the full contributions, but don't have any Flow page active.
+
+To remove the extension is possible, but will be at the detriment of the capability to explore past contributions.",1488478381,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"@demon @MZMcBride The Flow team have some reserves about the logs integrity: it will be difficult to see the previous contributions.
+
+As much, as an alternative discussion, it's offered to keep the extension, so it's still possible to explore  the full contributions, but don't have any Flow page active.",1488478281,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3066801, @MZMcBride wrote:
+> @Dereckson: I missed the discussion in `#wikimedia-operations`. I'm trying to better understand the status of this task. Are you unwilling to deploy <https://gerrit.wikimedia.org/r/333860>?
+
+I'm more than willing.",1488476273,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,@Dereckson: I missed the discussion in `#wikimedia-operations`. I'm trying to better understand the status of this task. Are you unwilling to deploy <https://gerrit.wikimedia.org/r/333860>?,1488439083,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"As @MZMcBride said, I don't think there are technical reasons for not doing this. The English Wikipedia had way more Flow boards enabled and got removed there per request of its community. Now there's this request, with large community consensus and no active Flow boards. It should be even easier to perform, even if afterwards we need some manual work to do. The community has asked clearly that they want the feature removed (@Alsee even opened a section in that discussion for if it was any doubt), not socially disabled, which is an euphemism for not doing what it was explicitly requested. I don't think they are serious problems for this not to be done, but some personal choices of not wanting Flow gone from Meta; and that is not appropriate when executing valid community consensus. The community at large had their opportunity to voice their personal opinion, and the result was that we want the feature removed. We ain't requesting anything impossible to do, or prohibited or absurd (ie: remove CheckUser or CentralAuth). Thank you.",1488388508,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I strongly agree with MarcoAurelio. Installing Flow on Meta-Wiki never had consensus and there's now a strong consensus to remove the extension completely. The discussion even specifically addressed whether this meant removing Flow from all pages or completely uninstalling the extension.
+
+If there are technical reasons that Flow cannot be uninstalled from Meta-Wiki currently, I would like to know what those reasons are specifically in Phabricator Maniphest tasks so that these issues can be addressed.",1487896471,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 333860 restored by MarcoAurelio:
+Remove Flow from Meta-Wiki
+
+Reason:
+This is not appropriate, Dereckson. The discussion at -operations is that the contribs of Flow talk page manager can stay where they are w/o any problems so far. Restoring. Please implement the community consensus. If this was done for enwiki, this can happen for Meta-Wiki as well. Nothing broke there and nothing will break here either.
+
+[[https://gerrit.wikimedia.org/r/333860]]",1487878688,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 333860 abandoned by Dereckson:
+Remove Flow from Meta-Wiki
+
+Reason:
+Per discussion on #wikimedia-operations, we'll disable it socially, but will leave the Flow extension installed.
+
+That will avoid to get an inconsistent state in the logs, contributions.
+
+The meta RFC is still satisfied as there isn't any active Flow page on meta. (and socially won't), as steps have been taken to move the last one to another wiki.
+
+[[https://gerrit.wikimedia.org/r/333860]]",1487878544,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I ran the preparatory scripts.
+
+Thanks to @Matiia for doing the 4 steps above.",1487807369,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Re {T154816} and {T156113}, the script parts are done.  Could an admin please do the following:
+1. Delete https://meta.wikimedia.org/wiki/Research_talk:ORES_paper
+2. Soft redirect from https://meta.wikimedia.org/wiki/Research_talk:ORES_paper to https://www.mediawiki.org/wiki/Talk:ORES/Paper .
+2. Delete https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page
+3. Move https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page/Wikitext to https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page .
+
+? Thanks.",1487806425,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Re {T154816} and {T156113}, the script parts are done.  Could an admin please do the following:
+1. Delete https://meta.wikimedia.org/wiki/Research_talk:ORES_paper
+2. Delete https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page
+3. Move https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page/Wikitext to https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page .
+
+? Thanks.",1487805919,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Added to the latest window available for Europeans: https://wikitech.wikimedia.org/w/index.php?title=Deployments&action=historysubmit&type=revision&diff=1555498&oldid=1555483,1487682860,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3038137, @jeblad wrote:
+> <rant>Sometimes I would really want a more firm standpoint from WMF against people moving backwards… </rant>
+
+<rant>Agreed. And the necessary prerequisite is to correctly identify ""forward"" in the first place. During the Flow prototype stage numerous community members told Flow's lead designer that the project was going in the wrong direction. He was told that it could never be successfully deployed as a replacement for Talk pages. The designer aggressively ignored critical project requirements. Uninstalling a non-viable project is a step forwards.</rant>",1487657499,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"T154816 is not a hard blocker, just a nice to have (why not make a couple persons happy if it costs us nothing). Doing T156113 before the disabling is instead definitely recommended, though not absolutely necessary per T156113#2964757.
+
+Since there is no way in Phabricator to distinguish ""real blockers"" from ""things you'd also do at the same time in an ideal world"", I'm removing the soft subtask again.",1487496677,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I asked for a status update regarding {T154816} at T154816#3038183. This task turns three years old in a couple of days. ;-)  But more seriously, I'd like to see this task resolved in the next week or two. March 1 seems like a reasonable deadline.
+
+One way or another, I'm going to call March 1, 2017 a hard deadline. We will not be saving posts to a Flow-backed version of <https://meta.wikimedia.org/wiki/Research_talk:ORES_paper> after this date.",1487442713,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Standing against the communities which gave success to the WMF movement ain't going to work. Saying that Flow is moving forward is also a disputable statement, specially when so much people has objected to its use on that project, some of those because they ain't able to use that software at all. World is not fair, but excluding community members from discussion pages is not what I'd call moving forward.",1487433981,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,<rant>Sometimes I would really want a more firm standpoint from WMF against people moving backwards… </rant>,1487427762,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#3016898, @MarcoAurelio wrote:
+> Flow board still needs to be ported to mw.org and a maintenance script run
+> afterwards to convert remaining Flow boards before being removed I think.
+
+That would be nice, but not necessary: we're not dropping the database tables any time soon. Also, if there is really an urgency to keep the content the script for conversion to wikitext is available.",1487407427,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Flow board still needs to be ported to mw.org and a maintenance script run
+afterwards to convert remaining Flow boards before being removed I think.",1486735904,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,It seems about time to schedule the configuration change and send notices. Can a week or two of windows be added to https://wikitech.wikimedia.org/wiki/Deployments ?,1486721573,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#2963875, @MZMcBride wrote:
+> I think it's reasonable to wait for {T154816} to be resolved, if possible, but we should set a firm deadline. Is four weeks enough time?
+
+4 weeks seems unnecessarily long, but should be tolerable.",1485617945,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Proposed workflow:
+
+# {T154816}, then
+# {T156113}, then
+# SWAT https://gerrit.wikimedia.org/r/#/c/333860/",1485250346,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 333860 had a related patch set uploaded (by MarcoAurelio):
+Remove Flow from Meta-Wiki
+
+[[https://gerrit.wikimedia.org/r/333860]]
+",1485249656,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I think it's reasonable to wait for {T154816} to be resolved, if possible, but we should set a firm deadline. Is four weeks enough time?",1485230338,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"[[ https://meta.wikimedia.org/w/index.php?title=Meta:Babel&curid=69328&diff=16251209&oldid=16240965 | The RFC on Meta has closed]] with a clear consensus to remove Flow. Note that this was not an RFC to reduce active Flow pages to zero, this was an RFC for the extension be uninstalled as was done on Enwiki. (T148611)
+
+",1485212471,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Note: There is an ongoing proposal to remove Flow from Meta: https://meta.wikimedia.org/wiki/Meta:Babel#Proposal_to_remove_Flow_on_Meta-Wiki,1483218188,PHID-USER-vzo36k53hgat5bwuxsn5,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#2755301, @Alsee wrote:
+> Flow is to be uninstalled on EnWiki T148611, can we just roll the two tasks into one?
+
+
+No separate tasks, should always be kept seperate",1477858479,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Flow is to be uninstalled on EnWiki T148611, can we just roll the two tasks into one?
+
+The [[ https://meta.wikimedia.org/wiki/Meta:Requests_for_comment/Enable_Flow_as_beta_feature | RFC for Flow on Meta ]] was unanimous against Flow, except for the author. I wish I heard about the RFC, I would have eagerly piled-on against Flow. The lead software designer for Flow was told during the prototyping stage, by many many editors, that the design was wrong and that it was never going to be used. He just blew-off all community input on it. (EnWiki Flow talk archives, and almost certainly anywhere else Flow was discussed at the time.)
+",1477870278,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Flow is to be uninstalled on EnWiki T148611, can we just roll the two tasks into one?
+
+The [[ https://meta.wikimedia.org/wiki/Meta:Requests_for_comment/Enable_Flow_as_beta_feature | RFC for Flow on Meta ]] was unanimous against Flow, except for the author. I wish I heard about the RFC, I would have eagerly piled-on against Flow. The lead software designer for Flow was told during the prototyping stage, by many many editors, that the design was wrong and that it was never going to be used. He just blew-off all community input on it. (EnWIki Flow talk archives, and almost certainly anywhere else Flow was discussed at the time.)
+",1477856226,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Triaged.,1468865416,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,The RfC is closed now and the closure result has not been contested for some time. Flow has no use on Meta other than the test page linked above so there should be no major fuss in removing this.,1468865374,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Also, [[ https://meta.wikimedia.org/wiki/Meta:Requests_for_comment/Enable_Flow_as_beta_feature | this RfC ]] on enabling Flow on Meta as beta feature, although few people participated, is leaning towards not allowing this.",1464026872,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"> (there was a discussion at https://gerrit.wikimedia.org/r/#/c/115412/ too)
+
+NSFW link! My eyes bleed... luckily the past is behind us.",1463344740,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,(there was a discussion at https://gerrit.wikimedia.org/r/#/c/115412/ too),1463344450,PHID-USER-qlodcndtwpolbdhncjis,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,">>! In T63729#2295518, @Nemo_bis wrote:
+> This request should probably be reopened and completed.
+
+Sure. I've re-opened this task to allow for further consideration.",1463336988,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Two years later, from https://meta.wikimedia.org/wiki/Special:AllPages?from=&to=&namespace=2600 it appears there is no meaningful content anywhere, only https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page with some garbage and complaints.
+
+This request should probably be reopened and completed.",1463307836,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 115412 abandoned by Odder:
+Remove Flow from Meta-Wiki
+
+Reason:
+This is very unlikely to ever be merged.
+
+https://gerrit.wikimedia.org/r/115412",1394645055,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I interpret comments 13 to 17 as WONTFIX for this request.
+
+Are there any further arguments that have not been brought up yet plus need answers?",1394017452,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"**wmf.amgine3691** wrote:
+
+(In reply to Erik Moeller from comment #17)
+> Yeah, sure - I agree there's no point pissing off people unnecessarily while
+> we're looking at different test scenarios. There's also no point creating
+> more drama than required about a single page test deploy. :) Preemptively
+> deleting comments on a page flagged as ""developer test page"" and then
+> raising alarm bells about the coming incursion seems a wee bit premature.
+> Let's all have a sensible chat about what makes sense on Meta, but let's
+> also give each other the benefit of the doubt as we go please.
+
+AGF is stretched a bit, since there were clear examples cited, communications channels were not used, etc. That is, AGF is not required from only one party.",1393396906,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Where does the single page test end, and using it as a backdoor to enabling it wider or sitewide without community consensus",1393396783,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Yeah, sure - I agree there's no point pissing off people unnecessarily while we're looking at different test scenarios. There's also no point creating more drama than required about a single page test deploy. :) Preemptively deleting comments on a page flagged as ""developer test page"" and then raising alarm bells about the coming incursion seems a wee bit premature. Let's all have a sensible chat about what makes sense on Meta, but let's also give each other the benefit of the doubt as we go please.",1393396061,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Erik Moeller from comment #15)
+> What practical concerns are there with the current test page deploy?
+
+I think you and I may fundamentally disagree about whether pissing off a local editing community and engendering further ill will toward these type of projects (ArticleFeedbackv5, LiquidThreads, Flow, UniversalLanguageSelector, VisualEditor, etc.) is a practical concern. The erosion of trust and collaboration between the Wikimedia Foundation and the active editing communities is a very serious and practical concern, in my opinion.
+
+As far as I know, deploying Flow will not cause anything to explode. This is _not_ the same as saying deploying Flow will not cause any harm. I think attempting to force this alpha discussion software on Meta-Wiki (and wherever else next) will actively harm already battered relations.
+
+I'll try to put it another way: if the software has virtue and merit as a product, it should be no issue for the Flow team to establish local community consensus to test it out. However there are over 800 Wikimedia wikis; if, after discussion and consultation, the Meta-Wiki community decides it doesn't want to install Flow right now, test it elsewhere. What's the issue?",1393395182,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I think everyone agrees that the communication about the single-page test wasn't sufficient. But I don't think the LQT comparison is valid. LQT comes with a rather scary per-page flag allowing any page to be LQT-enabled, and the discussions you're pointing to refer to enabling LQT across Meta.
+
+Flow has no such flag right now - pages are manually and carefully selected for testing purposes, and effects truly are pretty limited. This deploy enabled a page called ""Developer test page"". So this analogy seems _very_ stretched, and the arguments seem theoretical at this point. What practical concerns are there with the current test page deploy?",1393394462,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Erik Moeller from comment #13)
+> We can't get consensus on a per-wiki basis before enabling any software
+> change. That has never been our practice and never will be.
+
+Nobody is asking you to.
+
+> What are the actual material issues with this deploy?
+
+I think both you and Maryana are perhaps missing the point.
+
+* [[m:Wikimedia Forum/Archives/2010-04#LiquidThreads]]
+* [[m:Meta:Babel/Archives/2010-12#LiquidThreads]]
+* [[m:Meta:Babel/Archives/2012-01#Enabling Liquid Thread on meta]]
+
+The Flow team has put forward the idea that it can operate in a vacuum on a wiki. I don't believe this is acceptable or reasonable. The Flow team has also put forward the idea that hyper-local consensus (or in the case of Meta-Wiki, no visible consensus...) can override project or global consensus. This is pretty unchartered territory, no? For example, when's the last time a group of five or six users determined whether to enable an extension on the English Wikipedia?
+
+The Flow team says Flow will be opt-in software, but then unilaterally declares that it's going to deploy Flow to Meta-Wiki, with an accompanying self-merge in Gerrit, and without any on-wiki discussion or any attempt to discuss the idea with the Meta-Wiki community. Consensus is a _pillar_ of Wikimedia wikis.
+
+I can't help but think that Tomasz is correct that you're repeating the mistakes of VisualEditor by trying to steamroll communities into accepting this software. Particularly on a smaller wiki such as Meta-Wiki, Flow can't simply exist in a vacuum. Special:RecentChanges, Special:Watchlist, IRC feeds, etc. are all common and will be infected by Flow.
+
+Echoing what I said in comment 8, Meta-Wiki has repeatedly rejected LiquidThreads, but perhaps the response to Flow will be different. Has anyone asked the Meta-Wiki community about its thoughts on using alpha discussion software? If the Flow team came into this seeking collaboration, it might find users willing to test out its software.
+
+I can't directly stop you from deploying the Flow extension to Meta-Wiki or any other Wikimedia wiki against the local community's wishes, but I wouldn't recommend it: history has repeatedly shown that the insurgents quite often beat out an occupying force. If you try to force Flow onto the wikis, I think you can only expect backlash and an increasingly inhospitable discussion environment.",1393393146,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"We can't get consensus on a per-wiki basis before enabling any software change. That has never been our practice and never will be. Clear communication is another matter and it looks like we could have done better in this respect.
+
+What are the actual material issues with this deploy?",1393361884,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Maryana Pinchuk from comment #9)
+
+> We are not going to disable Flow from Meta unless there is an actual issue
+> with the software. Please do not reopen this bug again unless you can point
+> to an actual issue with the software; doing otherwise is disruptive and
+> pointless.
+
+You have conveniently avoided answering any of the questions asked by MZMcBride. The truth is, you did not ask the Meta community for their opinion on whether Flow should be enabled or not, and you refuse to acknowledge it.
+
+This is VisualEditor all over again: you have learnt nothing from that experience, and that's just sad.",1393352536,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Change 115412 had a related patch set uploaded by Odder:
+Remove Flow from Meta
+
+https://gerrit.wikimedia.org/r/115412",1393351937,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,Just as is enabling an extension on a production wiki without asking its community for opinion first.,1393351813,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,We are not going to disable Flow from Meta unless there is an actual issue with the software. Please do not reopen this bug again unless you can point to an actual issue with the software; doing otherwise is disruptive and pointless.,1393351735,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Maryana Pinchuk from comment #4)
+> This is all following along our course of enabling Flow on an opt-in, user
+> requested basis on a limited set of pages for testing purposes over the next
+> 3-6 months.
+
+I don't believe the Meta-Wiki community wants the Flow extension enabled right now. Have you tried asking the community about its thoughts on the matter?
+
+Unlike most of the Flow team, most active users at Meta-Wiki have been around for a long time. Meta-Wiki eschewed LiquidThreads (I believe I even once proposed enabling it there and it was quickly shot down). Perhaps with Flow, the Meta-Wiki community will be more receptive, but I think it would make sense to ask. Have you asked?",1393032148,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to spage from comment #6)
+> Enabling Flow on a wiki test page before enabling it on a requested Talk
+> page on that wiki is clearly the right thing to do. We found a problem with
+> Parsoid configuration on meta by doing so.  We do indeed have playgrounds
+> already so I didn't see much point in publicizing yet another test page, but
+> since people find them anyway we should do so in the future.
+> 
+> I think people's bigger objection is Flow coming to a wiki because some
+> small group requests it on ""their"" Talk page. That's implicit in the
+> roll-out strategy Maryana mentioned, which is on the main Flow page:
+>    Wider release to more WikiProject and community discussion spaces on
+> English Wikipedia and other projects, on an opt-in trial basis
+> 
+> I don't think this bug is the best place to discuss the rollout strategy,
+> I've created https://www.mediawiki.org/wiki/Flow/Rollout and it has a talk
+> page, the latter is not yet Flow-enabled :)
+
+I think you're totally missing the point about the objections raised in this bug.",1393014881,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Enabling Flow on a wiki test page before enabling it on a requested Talk page on that wiki is clearly the right thing to do. We found a problem with Parsoid configuration on meta by doing so.  We do indeed have playgrounds already so I didn't see much point in publicizing yet another test page, but since people find them anyway we should do so in the future.
+
+I think people's bigger objection is Flow coming to a wiki because some small group requests it on ""their"" Talk page. That's implicit in the roll-out strategy Maryana mentioned, which is on the main Flow page:
+   Wider release to more WikiProject and community discussion spaces on English Wikipedia and other projects, on an opt-in trial basis
+
+I don't think this bug is the best place to discuss the rollout strategy, I've created https://www.mediawiki.org/wiki/Flow/Rollout and it has a talk page, the latter is not yet Flow-enabled :)",1393011506,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,No. Meta is not your playground. Go test Flow on the Beta cluster if you need to.,1393003465,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"Andre: From https://wikitech.wikimedia.org/wiki/Deployments: Tuesday February 18th, ""enable Flow on meta test page and a few more mediawiki.org talk pages"" :)
+
+I got a request from the WMF Programs Evaluations team to enable Flow on the talk page of https://meta.wikimedia.org/wiki/Programs:Evaluation_portal/Learning_modules. The extension's been tested in production for 2 months now (on mw.org, as well as English Wikipedia for about 2 weeks now), but we wanted to be sure to enable it on a test page on Meta before releasing it on a real discussion page. 
+
+This is all following along our course of enabling Flow on an opt-in, user requested basis on a limited set of pages for testing purposes over the next 3-6 months.",1393002860,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Bawolff (Brian Wolff) from comment #2)
+>(Surely flow should add a page property
+> or something to flow pages so that they can be found sanely?)
+
+Filed as bug 61747",1392986145,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"(In reply to Andre Klapper from comment #1)
+> I did not see this mentioned anywhere on
+> https://wikitech.wikimedia.org/wiki/Deployments (link welcome if I missed
+> it). 
+> The patch is missing any link to a bug report or on-wiki discussion, as
+> MZMcBride correctly pointed out. And I have no idea what the ""one page of
+> meta"" is, as the commit message is so vague.
+> 
+
+It's https://meta.wikimedia.org/wiki/Talk:Flow/Developer_test_page . You can find flow pages by doing searches like https://meta.wikimedia.org/w/index.php?title=Special:Search&search=%22This%20talk%20page%20has%20been%20taken%20over%20by%20a%22&fulltext=Search&profile=all&redirs=1 (Surely flow should add a page property or something to flow pages so that they can be found sanely?)",1392985659,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+Remove Flow from Meta-Wiki,"I did not see this mentioned anywhere on https://wikitech.wikimedia.org/wiki/Deployments (link welcome if I missed it). 
+The patch is missing any link to a bug report or on-wiki discussion, as MZMcBride correctly pointed out. And I have no idea what the ""one page of meta"" is, as the commit message is so vague.
+
+I really hope I missed something, otherwise this would look like pretty bad communication.",1392984733,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hlvwrmmv76naf6jfq4rg,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"Screenshot
+
+Steps to reproduce:
+
+Open the VE and observe the toolbar
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13046}",1392934800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_description,resolved
+VisualEditor: Toolbar broken in Betalabs,Verified the fix in betalabs,1392939577,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"This has been resolved because the offending commit was reverted
+
+I7e8ab90f7a9f77f5cf6d7baeab586d4e0332042e",1392937691,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"Change 114637 abandoned by Trevor Parscal:
+Fix a missing { and remove some debugging CSS left in Ied29358
+
+Reason:
+Ied29358 was reverted
+
+https://gerrit.wikimedia.org/r/114637",1392936992,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"Change 114637 had a related patch set uploaded by Krinkle:
+Fix a missing { and remove some debugging CSS left in 4a067460
+
+https://gerrit.wikimedia.org/r/114637",1392936388,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: Toolbar broken in Betalabs,"Created attachment 14638
+Screenshot
+
+**Attached**: {F13047}",1392934866,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-sdsa2kuvbtigpgaepsc2,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"The file modules/syntaxhighlight/rules/mysql.json has at least one double quoted string containing unescaped double quotes. I.e something like:
+
+{
+ ""match"" : """"""
+}
+
+That cause PHP json_decode() to choke with a syntax error.  I wrote a json linter to lint json files in Jenkins.  You can try it using integration/jenkins.git and running bin/json-lint.php
+
+ ./modules/syntaxhighlight/rules/mysql.json: Syntax error
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392906540,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_description,resolved
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"hashar@gallium:~/extensions$ /srv/deployment/integration/slave-scripts/bin/json-lint.php VisualEditor/; echo $?
+0
+hashar@gallium:~/extensions$",1392926451,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,The PHP json_decode() no more reports any error. Thank you!,1392926436,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"Change 114518 merged by jenkins-bot:
+Fix broken JSON in modules/syntaxhighlight/rules/mysql.json
+
+https://gerrit.wikimedia.org/r/114518",1392925383,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"(In reply to Antoine ""hashar"" Musso from comment #0)
+> The file modules/syntaxhighlight/rules/mysql.json has at least one double
+> quoted string containing unescaped double quotes. I.e something like:
+> 
+> {
+>  ""match"" : """"""
+> }
+> 
+> That cause PHP json_decode() to choke with a syntax error.  I wrote a json
+> linter to lint json files in Jenkins.  You can try it using
+> integration/jenkins.git and running bin/json-lint.php
+> 
+>  ./modules/syntaxhighlight/rules/mysql.json: Syntax error
+
+It's in a file that's not currently used (the code needs some work), but I've fixed it.",1392923964,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string,"Change 114518 had a related patch set uploaded by Jforrester:
+Fix broken JSON in modules/syntaxhighlight/rules/mysql.json
+
+https://gerrit.wikimedia.org/r/114518",1392923895,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bmlhfoq57oujs4ajpe2q,task_subcomment,NA
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values","Right now the reference group input (in both MWReferenceDialog and MWReferenceListDialog) is a plain text input box (with a placeholder).
+
+Instead, it should be a drop-down that suggests existing groups, as well as giving the ability to write in a new value, aka a ComboBox.
+
+The default value should still have a placeholder, I think.
+
+[Blocked on OOjs UI having a ComboBox widget.]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392861240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bthorzb222zjqyyqflqv,task_description,resolved
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values",Verified the fix in Production,1410545581,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-bthorzb222zjqyyqflqv,task_subcomment,NA
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values",Verified it in Betalabs and test 2,1409872373,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-bthorzb222zjqyyqflqv,task_subcomment,NA
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values","Change 156160 merged by jenkins-bot:
+Use combo box widget to suggest existing values for reference group
+
+https://gerrit.wikimedia.org/r/156160",1409689295,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bthorzb222zjqyyqflqv,task_subcomment,NA
+"VisualEditor: Reference group input should be a ""ComboBox"" suggesting possible values","Change 156160 had a related patch set uploaded by Alex Monk:
+Use combo box widget to suggest existing values for reference group
+
+https://gerrit.wikimedia.org/r/156160",1408991900,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bthorzb222zjqyyqflqv,task_subcomment,NA
+VisualEditor: Factor out ./ stripping logic,"Right now it's in MWInternalLinkAnnotation and MWRedirectMetaItem just calls into that (see https://gerrit.wikimedia.org/r/#/c/114381/). There's also some ./ stripping regexes strewn across the rest of the codebase. This should all be factored out and centralized.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392860160,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-k52nhgcjimjne3g6enih,task_description,open
+"VisualEditor:  In the category dialog, there should be a drop down indicator on existing categories","Inside the category editor, there used to be a drop-down indicator on categories.  It's not there now.  Not at MediaWiki, not at Wikipedias, not in Safari 6, not in Firefox 26 (on Mac OS 10.8.5).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392858900,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-hwxwkjrd5ypn4cohgwlt,task_description,resolved
+"VisualEditor:  In the category dialog, there should be a drop down indicator on existing categories",Verified the fix in test2,1393009228,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-hwxwkjrd5ypn4cohgwlt,task_subcomment,NA
+"VisualEditor:  In the category dialog, there should be a drop down indicator on existing categories","Yes, this got broken some time ago due to an oversight – and we just fixed it on Friday (gerrit 113477). The fix will be going out to MediaWiki.org tomorrow. Sorry!",1392859556,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hwxwkjrd5ypn4cohgwlt,task_subcomment,NA
+VisualEditor: Burn ve.ce.getElementOffset down to the ground,"It's incredibly confusing spaghetti code that's not documented well. Kill it with fire and start from scratch.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392852060,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-caf2jml522yw7s4hrz7i,task_description,resolved
+VisualEditor: Burn ve.ce.getElementOffset down to the ground,This function doesn't actually exist. I'm assuming this refers to getOffset/getOffsetFromElementNode/getOffsetFromTextNode which have been rewritten in https://gerrit.wikimedia.org/r/#/c/121563/,1404350652,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-caf2jml522yw7s4hrz7i,task_subcomment,NA
+"VisualEditor: Don't allow users to insert images inside images' captions inside images' captions, as MediaWiki can't cope with that","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings of that image and add another image inside it
+4.Now Go to the media settings of the image that you just added
+5.Type something in the caption of the second image
+6.Apply changes
+7.Save the page
+
+Observed Result:
+The wiki text for the image shows up in the read mode
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/19thfebFF
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13390}",1392850500,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ziermjjci3oyywhcltgx,task_description,duplicate
+"VisualEditor: Don't allow users to insert images inside images' captions inside images' captions, as MediaWiki can't cope with that","I can't make three-deep nested images work in wikitext.
+
+Three deep (image1's caption contains image2, and image2's caption contains image3) causes this problem if done in VisualEditor:  
+http://en.wikipedia.beta.wmflabs.org/w/index.php?&oldid=82440  It displays correctly in VisualEditor, but makes a mess when you save.
+
+Two deep in wikitext displays correctly:  https://en.wikipedia.org/w/index.php?&oldid=598318957#List
+
+Three deep in wikitext shows me only the first image.  The other two in my (unsaved) attempts simply disappeared from view (although present in the wikitext code).
+
+It's possible that I simply haven't found the perfect sequence of nesting the images, but if wikitext can't handle more than two in a nested sequence, the VisualEditor shouldn't offer it.",1394059797,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ziermjjci3oyywhcltgx,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Parsoid's bug 49844 with link attributes has been fixed.
+
+In https://bugzilla.wikimedia.org/show_bug.cgi?id=49844#c5 James Forrester wrote:
+
+This is worked around (albeit with potentially a bit of a hack) in VisualEditor, so not so important now from VisualEditor's POV.
+
+Now that the parsoid fix has been deployed (for a while now), I'm opening a new bug to revert Visual Editor's hack.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392847560,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_description,invalid
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"As discussed, this wasn't a hack, this was the right thing to do, so INVALIDing this bug.",1395082995,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 119088 merged by jenkins-bot:
+Remove commented-out, now-confirmed-as-wrong wrong image insertion code
+
+https://gerrit.wikimedia.org/r/119088",1395082729,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 119087 merged by jenkins-bot:
+Clarified the default link for image insertion.
+
+https://gerrit.wikimedia.org/r/119087",1395081903,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 119088 had a related patch set uploaded by Jforrester:
+Remove commented-out, now-confirmed-as-wrong wrong image insertion code
+
+https://gerrit.wikimedia.org/r/119088",1395081642,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 119087 had a related patch set uploaded by Cscott:
+Clarified the default link for image insertion.
+
+https://gerrit.wikimedia.org/r/119087",1395081568,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"I believe the reversion is correct.  Clarified the spec: https://www.mediawiki.org/w/index.php?title=Parsoid%2FMediaWiki_DOM_spec&diff=931265&oldid=931084
+VE's current behavior matches the spec.",1395081459,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"This isn't fixed.
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=81525&oldid=81245
+
+*sighs*",1393637856,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 114352 merged by jenkins-bot:
+Revert ""Set href attribute of newly inserted image to image title""
+
+https://gerrit.wikimedia.org/r/114352",1392932238,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Revert image |link= hack for Parsoid bug 49844,"Change 114352 had a related patch set uploaded by Jforrester:
+Revert ""Set href attribute of newly inserted image to image title""
+
+https://gerrit.wikimedia.org/r/114352",1392848850,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zltiznjn5tevkdkrgrvo,task_subcomment,NA
+VisualEditor: Error thrown when typing something while a left aligned image is selected,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image .
+3.Go to Media Settings>Advances Settings
+4.Set the image alignment to left/None
+5.Save the page
+6.Reopen the page
+7.Select the image
+8.Start typing something
+
+
+Observed Result:
+ncaught Error: Offset could not be translated to a DOM element and offset: 143 appears in the console 
+
+See the screenshot attached
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=18thfebchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13297}",1392767520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ioicrlnneujuclmsdn76,task_description,resolved
+VisualEditor: Error thrown when typing something while a left aligned image is selected,IME cursor code has changed significantly since 2014 and I can't reproduce. Please re-open if this is still hapenning.,1701962955,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ioicrlnneujuclmsdn76,task_subcomment,NA
+VisualEditor: Error thrown when typing something while a left aligned image is selected,"Found the steps to reproduce the case with deleting the reflist:
+
+1.Add an image
+2.Go to Media Settings>Advanced Settings
+3.Set the position to left
+4.Add a reference inside the image
+5.Save the page
+6.Open the page again
+7.Delete the reflist
+
+The error Uncaught Error: Offset could not be translated to a DOM element and offset: 143 appears in the console",1392769346,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ioicrlnneujuclmsdn76,task_subcomment,NA
+VisualEditor: Error thrown when typing something while a left aligned image is selected,This is also happening while deleting the reflist of the same page,1392767690,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ioicrlnneujuclmsdn76,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"It seems Flow has not defined any HTML accesskeys for previewing/submitting posts and topics.
+
+The default accesskey ""p"" should be added to the ""Preview"" button.
+The default accesskey ""s"" should be added to the ""Reply""/""Add Topic""/""Submit changes"" buttons when replying to a topic/adding a topic or editing a post respectively.
+
+Docs (I'm not sure which of these are most uptodate):
+* https://www.mediawiki.org/wiki/Manual:Interface/Access_keys
+* https://meta.wikimedia.org/wiki/Help:Keyboard_shortcuts
+* https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+* https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts
+
+See also {T158779}
+",1392758820,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-xle733tl52tx5qckejj2,task_description,open
+Flow lacking accesskeys for preview/submit,"I use alt(+shift)+s to save in articles, which is specified when hovering over the save-button (in wikicode-mode). That should be standard for Flow as well.",1440623374,PHID-USER-4j7xntcqqwei7izzlfnd,False,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"Well, it's ""non-standard in the Wikimedia world"" because we didn't decide to use it as a standard. There is no Wiki God (sorry, Jimbo!) declaring ""the standard"". There is only us.
+
+And Echo is being introduced for the same reason Visual Editor is: Because ""our ways"" don't cut it for the mere rest of the world. There, WYSIWYG editing is standard. So is Crtl/Cmd-Enter to save.",1439992612,PHID-USER-hms7bpiczbwhx4dxgiqw,False,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"First of all the long established accesskeys (with ""S"" for saving and ""P"" for preview respectively) should be added to Flow.
+
+If we add yet another - currently non-standard (in the Wikimedia world) - possibility for submitting (like Ctrl+Enter) is not within the scope of the bug as far as I'm concerned.",1439984330,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"Frankly, I think the ULS should get a different shortcut then. Simple question:
+* How many people will use the ULS often enough to remember and use a shortcut, per day?
+* How many people will save a comment on a Flow talk page, using the pseudo-standard shortcut (used by gmail, phabricator, etc.), per day?
+
+Principle of least surprise, people...",1439368805,PHID-USER-hms7bpiczbwhx4dxgiqw,False,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"We could use the standard accesskey mechanism, and the same keys for save (corresponding to Flow submit) and preview (corresponding to Flow ""switch to VE"") as standard edit pages (mouse over the save and preview buttons).",1439331104,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,Is there a different shortcut we could use? ,1439328813,PHID-USER-37czexl6ekrvcmp2tyqq,False,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,Ctrl+Enter is currently taken over by UniversalLanguageSelector. T106700,1439326993,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"A request for Ctrl-Enter (Cmd-Enter) to ""Save"" an edit, via twitter: https://twitter.com/MagnusManske/status/631122281931112448  (and the previous onwiki discussion I linked above, also suggested this standard key combination)",1439326509,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Flow lacking accesskeys for preview/submit,"Thanks Eduard. :)
+
+Tracked at https://trello.com/c/Y8vvggBw/99-keyboard-shortcuts-accesskeys
+
+with previous discussion and notes at https://www.mediawiki.org/w/index.php?title=Talk:Flow&topic_postId=roaqtzq187eo7d74&workflow=roaqtzq187eo7d74",1392841990,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-xle733tl52tx5qckejj2,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"For projects built with npm (e.g. VE, OOjs UI) this could be relatively easy, but for MW core I imagine it's a bit harder to parse .php files.
+
+(For VE we'd want this blocking merge, but that's a distinct conversation.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392753720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-q5awmwers7vnmtk3yywm,task_description,resolved
+Have an i18n CI job that ensures there's a qqq message for each en message,Other repositories (i.e. MediaWiki extensions) will be checked using a dedicated Jenkins job. That is the purpose of bug 64045.,1397719573,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Change 125050 merged by jenkins-bot:
+Use new banana checker as a linter to avoid lacking qqq messages
+
+https://gerrit.wikimedia.org/r/125050",1397692280,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"(In reply to Gerrit Notification Bot from comment #5)
+> Change 5550 abandoned by Jforrester:
+> tests to compare En, Qqq and messages.inc
+> 
+> Reason:
+> Replaced by https://www.npmjs.org/package/grunt-banana-checker now.
+> 
+> https://gerrit.wikimedia.org/r/5550
+
+Sounds good to me :-]",1397640219,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Change 5550 abandoned by Jforrester:
+tests to compare En, Qqq and messages.inc
+
+Reason:
+Replaced by https://www.npmjs.org/package/grunt-banana-checker now.
+
+https://gerrit.wikimedia.org/r/5550",1397600038,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Done in https://www.npmjs.org/package/grunt-banana-checker – gerrit 125050 adds this to MediaWiki core; gerrit 124069, gerrit 124023 and gerrit 124021 added it to OOjs UI, VisualEditor, and VisualEditor-MediaWiki.",1397600012,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Change 125050 had a related patch set uploaded by Jforrester:
+Use new banana checker as a linter to avoid lacking qqq messages
+
+https://gerrit.wikimedia.org/r/125050",1397596499,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"Change 5550 had a related patch set uploaded by Hashar:
+tests to compare En, Qqq and messages.inc
+
+https://gerrit.wikimedia.org/r/5550",1393242023,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+Have an i18n CI job that ensures there's a qqq message for each en message,"For mediawiki/core I once wrote a test suite that compares messages in messages.inc, en and qqq https://gerrit.wikimedia.org/r/#/c/5550/
+
+They are not passing though and I don't really have the mood to complete this patch though :-(",1393242009,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-q5awmwers7vnmtk3yywm,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"Last working job:
+  https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/942/console
+
+  - Feb 16, 2014
+  - Building remotely on integration-slave01
+
+  - node v0.10.22
+  - npm v1.1.38
+
+First failing job:
+  https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/943/console
+
+  - Feb 18, 2014
+  - Building remotely on integration-slave02
+
+  - node v0.8.2
+  - npm v1.1.39
+
+16:23:41 npm ERR! Error: SSL Error: CERT_UNTRUSTED
+16:23:41 npm ERR!     at ClientRequest.<anonymous> 
+16:23:41 npm ERR!     at Socket.ondata (stream.js:38:26)
+16:23:41 npm ERR!  [Error: SSL Error: CERT_UNTRUSTED]
+
+Server log:
+  https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&diff=99596&oldid=99549
+
+
+  - February 17
+    - 16:15 hashar: Jenkins deleting slave integration-slave01
+    - 16:14 hashar: Jenkins added two labs slaves with 4 CPU: integration-slave02 and integration-slave03
+    - 08:46 hashar: Upgrading Jenkins, half an hour downtime
+
+
+
+So npm was upgraded one minor version, and nodejs was downgraded *2 major versions*, and (possibly unrelated) it seems to be unable to verify the certificate properly.
+
+According to existing bug reports, this is related to it being a self-signed certificate, however this shouldn't be a problem since a validation mechanism for their official certificate ships with the npm package. Upstream recommends upgrading to the most recent minor version, but that doesn't seem to be the problem considering the bug started happening for us overnight (no certificate change upstream) when we went from v1.1.38 to v1.1.39 (not down).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**See Also**:
+https://github.com/npm/npm/issues/4838",1392752580,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_description,resolved
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"Existing instances have been patches so marking this as fixed.
+
+The fact that we need to puppetize the patches is a separate bug.
+
+See:
+* bug 68256
+* bug 66056
+
+And the patches are documented at:
+https://wikitech.wikimedia.org/wiki/Nova_Resource:Integration/Setup",1405742229,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,The new,1405719711,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,Thank you Timo for fixing up the installation on integration-slave1003.  I guess we can close that bug since you proposed to use node 10.x on bug 66056 which would definitely fix the issue.,1401752463,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"(In reply to Antoine ""hashar"" Musso from bug 66048 comment #1)
+> Node marked offline on
+> https://integration.wikimedia.org/ci/computer/integration-slave1003/
+
+Brought back online.",1401749458,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,*** Bug 66048 has been marked as a duplicate of this bug. ***,1401749314,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&oldid=115053
+
+> 20:08 hashar: Jenkins unpolled integration-slave1003 npm is outdated there and does not trust npmregistry.org ( bug 61508 )
+> 22:37 Krinkle: Hack-patching integration-slave1003.eqiad.wmflabs per https://bugzilla.wikimedia.org/show_bug.cgi?id=61508#c2
+
+
+krinkle at integration-slave1003.eqiad.wmflabs in ~
+$ node --version
+v0.8.2
+
+$ npm --version
+1.1.39
+
+$ sudo -s
+# export HOME=/root
+# npm conf set strict-ssl false
+# l /usr/bin/npm
+
+  /usr/bin/npm -> /etc/alternatives/npm*
+
+# rm /usr/bin/npm
+# /etc/alternatives/npm install -g npm
+
+  ...
+  npm@1.4.13 /usr/lib/node_modules/npm
+
+# cd /tmp && mkdir foo123 && cd foo123
+# npm install jshint
+
+  .. success ..
+  jshint@2.5.1 node_modules/jshint
+
+# l `which npm`
+
+  /usr/bin/npm -> ../lib/node_modules/npm/bin/npm-cli.js*
+
+# npm conf set strict-ssl true
+
+# cd ~ && rm -rf /tmp/foo123/
+# npm install -g grunt-cli
+
+  .. success ..
+  /usr/bin/grunt -> /usr/lib/node_modules/grunt-cli/bin/grunt
+  grunt-cli@0.1.13 /usr/lib/node_modules/grunt-cli
+
+# npm --version
+1.4.13
+# grunt --version
+grunt-cli v0.1.13",1401748882,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,Has this recurred?,1401745339,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"I was a bit upset this morning. I have applied Timo fix from Comment #2 on all four instances:
+
+ integration-slave02.pmtpa.wmflabs
+ integration-slave03.pmtpa.wmflabs
+ integration-slave1001.eqiad.wmflabs
+ integration-slave1002.eqiad.wmflabs
+
+Seems to work now.",1395237768,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"(In reply to Nemo from comment #7)
+> I don't know if it's the same for you, but docs were wrong for me.
+> <https://www.mediawiki.org/w/index.
+> php?title=Parsoid%2FSetup&diff=930615&oldid=930612>
+
+The doc instructs to use a ppa which provides 0.10.x.  We do not use ppa.",1395227517,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,Mailed ops list.  The Parsoid and VisualEditor npm jobs are now failing and preventing changes to be merged until the SSL cert issue is properly fixed.,1395227463,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"(In reply to Antoine ""hashar"" Musso from comment #6)
+> Will mail ops list to figure out how to get nodejs 0.10.x marked for install
+> on those hosts.
+
+I don't know if it's the same for you, but docs were wrong for me.
+<https://www.mediawiki.org/w/index.php?title=Parsoid%2FSetup&diff=930615&oldid=930612>",1395226795,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"For some reason I managed to get the pmtpa slave nodes back to nodejs 0.8.x which break the VisualEditor npm jobs.
+
+I also created two new slaves in eqiad (integration-slave1001 and integration-slave1002) and they come up with nodejs 0.8.x as well.
+
+Will mail ops list to figure out how to get nodejs 0.10.x marked for install on those hosts.",1395226165,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"(In reply to Antoine ""hashar"" Musso from comment #3)
+> integration-slave01 received nodejs 0.10.x when it got added to
+> apt.wikimedia.org. It has been later removed but the instance never got
+> cleaned up.
+> 
+> npm, I have no idea, probably similar.
+> 
+> 
+> I dont want the slaves to be tweaked manually, everything must be in puppet.
+> So there is a few bugs that we should fill all related to updating packages
+> in apt.wikimedia.org:
+> 
+> * nodejs 0.10.x (that is apparently a work in progress)
+> * npm 1.3.10 should be backported from Ubuntu Trusty
+> * grunt-cli needs to be packaged
+> 
+> Then we can update the list of packages in operations/puppet.git file
+> ./modules/contint/manifests/packages/labs.pp . It list npm but no grunt-cli
+> since there is no package there.
+> 
+> Does it sound right?
+
+Yes, except for grunt-cli needing to be packaged. We explicitly don't want to do that, like the over 300 other arbitrary npm modules we fetch daily on the integration slaves based on things listed in package.json in local repositories, this yet just another package like that. We can and should (for consistency and for it being the right version) install this via npm.
+
+I'm sure there is a puppet syntax for ensuring a certain shell command has been executed (e.g. based on a certain file existing). Similar to how we use git::clone in some places and the puppet file{} syntax. They're not provisioned packages, just inline specified within our manifest created by something other than a package (a rb template file, a git clone, or, in this case, an npm install)",1394660054,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,Lowering priority and assigning back to Timo.  He applied a workaround.  Still have to fill bugs as mentioned in comment #3,1393240120,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"integration-slave01 received nodejs 0.10.x when it got added to apt.wikimedia.org. It has been later removed but the instance never got cleaned up.
+
+npm, I have no idea, probably similar.
+
+
+I dont want the slaves to be tweaked manually, everything must be in puppet. So there is a few bugs that we should fill all related to updating packages in apt.wikimedia.org:
+
+* nodejs 0.10.x (that is apparently a work in progress)
+* npm 1.3.10 should be backported from Ubuntu Trusty
+* grunt-cli needs to be packaged
+
+Then we can update the list of packages in operations/puppet.git file ./modules/contint/manifests/packages/labs.pp . It list npm but no grunt-cli since there is no package there.
+
+Does it sound right?",1392827453,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"krinkle at integration-slave03:
+
+# Enter root and fix HOME so that npm doesn't put cache in /home
+# which is read-only in labs (why?)
+$ sudo -s
+$ export HOME=/root
+
+# Temporarily disable ssl check
+$ npm conf set strict-ssl false
+
+# Remove symlink to apt-get installed version
+# because npm is not allowed to to delete this shadow 
+$ l /usr/bin/npm
+  /usr/bin/npm -> /etc/alternatives/npm*
+$ rm /usr/bin/npm
+
+# Upgrade npm
+$ /etc/alternatives/npm install -g npm
+
+ npm@1.1.39
+ ...
+ npm@1.4.3
+
+# Re-enable ssl check
+$ npm conf set strict-ssl true
+
+# Verify that stuff works by doing an
+# install of an example package (jshint)
+# in a tmp dir
+$ cd /tmp && mkdir foo123 && cd foo123
+$ npm install jshint
+ ...
+ success
+$ cd ~
+$ rm -rf /tmp/foo123
+
+# Install Grunt
+$ npm install -g grunt-cli
+
+ ...
+ success",1392755172,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves,"So the certificates partially ship with nodejs, not the npm package.
+
+Upstream nodejs takes care to backport these cert changes to v0.8, however the slaves not only downgraded from v0.10 to v0.8 but also to an way older minor release of the v0.8 branch.
+
+There have been 24 (!) minor releases since v0.8.2, latest is v0.8.22.
+
+In case this particular cert change can be mitigated by only upgrading npm, I've done a manual upgrade of npm on the individual instances using npm itself:
+
+ $ sudo -s
+ $ npm conf set strict-ssl false
+ $ npm install -g npm
+ npm 1.1.39
+ ...
+ npm 1.4.3
+ $ npm conf set strict-ssl true
+ $ cd /tmp && mkdir foo123 && cd foo123
+ $ npm install jshint
+ success
+
+The jobs still fail after this because the new labs slaves are also missing grunt.
+
+ $ sudo -s
+ $ npm install -g grunt-cli
+ success
+
+
+Note that I couldn't interact with npm the normal way because for some reason /home is read-only on the integration instances (even in root, npm still uses your original home as location to do some temporary work and caching).
+
+Had to set `export HOME=/root` to bypass that.",1392754229,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tpdzsfwsce2gxm3hlxzp,task_subcomment,NA
+Reusing references inside the VE template dialog,"The VE template dialog can - with the help of #templatedata - show input fields for a template's parameters. Usually these are simple text fields that offer no editing tools.
+
+As a user it would be nice to have a simple way to add references or re-use reference from the main article to input fields in dialog.
+
+A way to move forward here could be:
+- For a specific template parameter type (e.g. `content`) add...
+- ...either a button that opens the Citation dialog and adds wikitext, similar to how it's done in the WTE2017
+- ...or add a ""inline"" VisualEditor similar to what's done for the image dialog's caption field ",1392748620,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-fuicnfjgm4dh24qhshha,task_description,open
+Reusing references inside the VE template dialog,{T52896} seems closely related.,1510253286,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-fuicnfjgm4dh24qhshha,task_subcomment,NA
+VisualEditor: Automatically remove empty ref tags (and refuse to insert new ones),"If you add an empty, unnamed reference in wikitext (""<ref />""), then you get an empty, invalid reference.
+
+If you add an empty, unnamed reference in VisualEditor (Insert>Reference, then ""Add reference"" without typing anything), then you get an empty, invalid reference.
+
+VisualEditor should do better than wikitext:  it should detect empty, unnamed ref tags and refuse to insert them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392746820,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-e22m3ew36smar7n5obdf,task_description,resolved
+VisualEditor: Automatically remove empty ref tags (and refuse to insert new ones),We fixed this a while ago. Sorry for the slow triage!,1403743200,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-e22m3ew36smar7n5obdf,task_subcomment,NA
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,"**Author:** `duongxvu`
+
+**Description:**
+I was wondering whether it is possible for VisualEditor to work with other skins besides the officially supported ones (which I believe to be Vector, Monobook, and Apex). I’ve been tasked with creating a custom skin to meet my organization’s existing design standards, but it does not seem so easy to add support for VisualEditor in this regard. And documentation addressing similar issues to mine seem to be rare at the moment.
+
+For now, I've heavily modified Vector as a workaround, but would prefer a more long-term solution if one exists. I assume that the Vector skin will continue to receive regular updates in the future, and I’d like to avoid having to modify it every time that happens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://www.mediawiki.org/wiki/VisualEditor/Skin_requirements",1392743160,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-adi2ks5r3obfupmjeuws,task_description,resolved
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,I'm going to deem this fixed based on the details in https://www.mediawiki.org/wiki/VisualEditor/Skin_requirements now available.,1401204582,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-adi2ks5r3obfupmjeuws,task_subcomment,NA
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,"I have a skin ([[Skin::Cameleon]]) that's based on Dantmman's excellent tutorial ([[Manual:Skinning/Tutorial]]). All I really did (aside from installing Visual Editor) was to add my skin's name to the $wgVisualEditorSupportedSkins global array variable.
+
+We already found a number of CSS issues, that need fixing, but aside from that it seems to work.",1399754193,PHID-USER-cc6dswbtmstfsb4ldmit,False,PHID-TASK-adi2ks5r3obfupmjeuws,task_subcomment,NA
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,"I started writing some notes about what VE expects of skins in https://docs.google.com/a/wikimedia.org/document/d/1awG4IKujTFd72RJzr_4DVInKDO1BqRxRHbTnCHvYLr4/edit (Obviously, when I started a Google doc I expected to end up writing more. :/). Looking for feedback.
+
+Currently it starts with the IDs it expects to be present and then a note relating to Gerrit change 130085 and Gerrit change 130656.
+
+Never having made a skin myself I'm not 100% confident about what we need to make clear here or what's wanted by the bug reporter.",1399062940,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-adi2ks5r3obfupmjeuws,task_subcomment,NA
+VisualEditor: Document what is needed in terms of support for custom MediaWiki skins,"Yes, we currently don't document well what requirements we have on skins (because we're adding requirements as we go). We should improve documentation so that it's easier for skin maintainers to know what they need to do.",1394503143,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-adi2ks5r3obfupmjeuws,task_subcomment,NA
+VisualEditor: Using auto select zhu-yin input and it keeps bouncing duplicate chinese characters,"Please go to the youtube link for fully demo http://www.youtube.com/watch?v=DZ90EDLqHUI
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Mac OS X 10.6
+**Platform**: Macintosh",1392515640,PHID-USER-adqeptkffhhfdhukexph,False,PHID-TASK-n7aygelprycptenbqxi4,task_description,open
+VisualEditor: Using auto select zhu-yin input and it keeps bouncing duplicate chinese characters,"**Coiby.Xu** wrote:
+
+Same problem on Ubuntu 13.04, Firefox 26 and Chrome 33. I've tested both on wikipedia and local server.
+
+For the details, see https://www.mediawiki.org/wiki/Talk:VisualEditor#first_line_comes_out_extra_words_when_typing_chinese.",1396437642,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-n7aygelprycptenbqxi4,task_subcomment,NA
+VisualEditor: Ref group does not get updated when the group name is changed from References List dialog,"Steps to reproduce:
+
+1.Open a page with VE
+2.Add a reference with a group name ""first group""
+3.Now Add a references list but under Use this group, type ""first group one""
+4.Apply changes.(""there are no references with this group"" will appear which is correct)
+5.Now reopen the References list dialog again.
+6.Just delete the ""one"" from ""first group one"" to make it ""first group""
+7.Apply changes
+
+Observed Result:
+Even this time it says ""there are no references with this group"" which is wrong.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392415980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2f5c5qfnz7mu3qheybrb,task_description,resolved
+VisualEditor: Ref group does not get updated when the group name is changed from References List dialog,"This appears fixed, although I have no idea which patch and when could have fixed it.",1540268768,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2f5c5qfnz7mu3qheybrb,task_subcomment,NA
+VisualEditor: A black shadow is appearing in the Cite Web template dialog inside Media Settings after scrolling down a bit,"The shadow
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings for that image
+4.Go to Insert>Transclusion
+5.Search for the Cite Web template
+6.Add a value for URL and Source Title
+7.Apply Changes
+8.Now again re-open the cite web dialog for the template you just added
+9.When all the parameter list appears in the dialog box , scroll down a bit.
+
+Observed Result:
+
+Observe that,there is a black shadow appearing on the border above the Apply Changes button, it seems to me coming from the ""URL Access Date"" field as it was initially aligned with that border.
+
+
+See the screenshot attached to better understand the problem
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12975}",1392411060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ceazwtjwm6a7jnascqca,task_description,resolved
+VisualEditor: A black shadow is appearing in the Cite Web template dialog inside Media Settings after scrolling down a bit,Verified the fix.,1401476052,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ceazwtjwm6a7jnascqca,task_subcomment,NA
+VisualEditor: A black shadow is appearing in the Cite Web template dialog inside Media Settings after scrolling down a bit,"This appears to now be fixed, AFAICT, due to the changes to this layout. Closing.",1401418554,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ceazwtjwm6a7jnascqca,task_subcomment,NA
+VisualEditor: A black shadow is appearing in the Cite Web template dialog inside Media Settings after scrolling down a bit,"Created attachment 14594
+The position of URL access date field when the dialog is opened
+
+**Attached**: {F12976}",1392411126,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ceazwtjwm6a7jnascqca,task_subcomment,NA
+VisualEditor: Be able to access a display file's description page from within VE (e.g. in the media settings dialog),"On inserting an image, or editing an image, it should be possible to visit the file description page. Currently it's not even possible to get the filename of an image when in VE.
+
+Why this is needed: In order to access the captions on the image page or verify the license or similar. E.g. on inserting an image of Obama shaking hands with some other important person into the Obama article you might want to find out who this other person is
+
+Suggested solution: Add a link to the filepage in media settings.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392369960,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-tv45m2ck4vwdr4ovivkr,task_description,resolved
+VisualEditor: Be able to access a display file's description page from within VE (e.g. in the media settings dialog),"This was implemented during the last major work on the media dialog.  Choose an image from the search results, and click on the ""More information"" link (at the end of list of information about the image).",1434918715,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-tv45m2ck4vwdr4ovivkr,task_subcomment,NA
+VisualEditor: Uncaught SyntaxError: Invalid flags supplied to RegExp constructor 'index'  appears in production while saving any change from Edit Source mode,"Screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Make some changes
+3.Switch to edit source mode
+4.Save the page from Edit source mode
+
+Observed Result:
+Uncaught SyntaxError: Invalid flags supplied to RegExp constructor 'index' appears in the console
+
+Test Environment: production
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12828}",1392322440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pikh7ix5hnqd4nnyiadm,task_description,invalid
+VisualEditor: Uncaught SyntaxError: Invalid flags supplied to RegExp constructor 'index'  appears in production while saving any change from Edit Source mode,Bug caused by the Citation expander gadget.,1392335656,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pikh7ix5hnqd4nnyiadm,task_subcomment,NA
+VisualEditor: Rich paste fails and crashes surface with (? specific) content,"Steps to replicate:
+
+1. Edit an article in VisualEditor (or start a new one)
+2. Go to http://git-scm.com/download/linux
+3. Copy the list, from ""Debian/Ubuntu"" to the end of the content in the white space.
+4. Paste into the article in VE.
+
+Observed: 
+
+""Uncaught TypeError: Cannot call method 'getComparableObjectForSerialization' of undefined""
+
+After that, interaction with the CE - mostly with link inspector and surface widgets produces errors or is unresponsive (Without console error)
+
+I got this when I tried to add a link: ""Uncaught TypeError: Cannot call method 'getSurface' of null""
+""
+
+
+
+Chrome 32.0.1700.107 under Ubuntu 12.04.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1392321600,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ps7lp2luxy7m2thoc7zr,task_description,resolved
+VisualEditor: Rich paste fails and crashes surface with (? specific) content,"Committed while bugzilla was down:
+https://gerrit.wikimedia.org/r/#/c/113538/",1392744740,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ps7lp2luxy7m2thoc7zr,task_subcomment,NA
+VisualEditor: Rich paste fails and crashes surface with (? specific) content,"This is a bug in remapStoreIndexes, so this only happens when the target document already has some annotations, and the content being pasted has annotated elements (in Moriel's case, a <br> inside a <code>)",1392476991,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ps7lp2luxy7m2thoc7zr,task_subcomment,NA
+VisualEditor: Rich paste fails and crashes surface with (? specific) content,WFM in standalone and MediaWiki. Can anyone else reproduce?,1392374805,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ps7lp2luxy7m2thoc7zr,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"**Author:** `swalling`
+
+**Description:**
+Francais
+
+Edit beta is specific to English Wikipedia but we hard coded it in the tour text for GettingStarted, so it is showing up incorrectly in translated versions such as French etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12815}",1392312420,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lfp625smnes4vmcpcaey,task_description,resolved
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"Change 114698 merged by Phuedx:
+Use VisualEditor configuration for appendices (e.g. beta).
+
+https://gerrit.wikimedia.org/r/114698",1392999633,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"Change 114698 had a related patch set uploaded by Mattflaschen:
+Use VisualEditor configuration for appendices (e.g. beta).
+
+https://gerrit.wikimedia.org/r/114698",1392962475,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,This is in a firsteditve message in the GuidedTour extension.,1392937652,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"See the attachment for the issue.  Note how the guider says ""Modifier bêta"", but the actual tab just says ""Modifier"".  We want to fix the guider to check the configuration and always match the tab.",1392402776,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"(In reply to Nemo from comment #2)
+> (In reply to Matthew Flaschen from comment #1)
+> > It's easy to detect if this is enabled (mw.config.get(
+> > 'wgVisualEditorConfig' ).tabMessages).  However, I need to decide whether to
+> > make separate messages or substitute it in.
+> 
+> Can you pass two messages to it directly?
+
+Sorry, I'm a little unclear what you mean.  What would the two messages be, and what would I pass them to?
+
+> If the message(s) are just '{{int:vector-view-edit}}
+> {{int:visualeditor-beta-appendix}}' it's not less lego to have two. You can
+> pass to the tab a message '{{int:vector-view-edit}}$1"" where $1 is nothing
+> or ""&#160;{{int:visualeditor-beta-appendix}}"".
+
+I'm not controlling the text of the tab (sorry, the bug title was misleading).  I'm controlling the text of the guider (a kind of modal popup), which refers to the text of the tab.
+
+However, I think your suggestion of using a parameter just for the second part could still apply.",1392402667,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"(In reply to Matthew Flaschen from comment #1)
+> It's easy to detect if this is enabled (mw.config.get(
+> 'wgVisualEditorConfig' ).tabMessages).  However, I need to decide whether to
+> make separate messages or substitute it in.
+
+Can you pass two messages to it directly?
+
+> 
+> Is this an acceptable use of a parameter (passing either
+> '{{int:vector-view-edit}} {{int:visualeditor-beta-appendix}}""' or
+> '{{int:vector-view-edit}}' depending on configuration?
+> 
+> Or should I make separate messages?
+
+If the message(s) are just '{{int:vector-view-edit}} {{int:visualeditor-beta-appendix}}' it's not less lego to have two. You can pass to the tab a message '{{int:vector-view-edit}}$1"" where $1 is nothing or ""&#160;{{int:visualeditor-beta-appendix}}"".",1392362941,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description,"It's easy to detect if this is enabled (mw.config.get( 'wgVisualEditorConfig' ).tabMessages).  However, I need to decide whether to make separate messages or substitute it in.
+
+Is this an acceptable use of a parameter (passing either '{{int:vector-view-edit}} {{int:visualeditor-beta-appendix}}""' or '{{int:vector-view-edit}}' depending on configuration?
+
+Or should I make separate messages?",1392340028,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-lfp625smnes4vmcpcaey,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"After a discussion with no objections amongst the OTRS administrators on our mailing list, we would like to have the Translate extension enabled on OTRS wiki to facilitate translating messaging. Thanks!
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1392259920,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-fde4qftmev4t5neslgqj,task_description,resolved
+Enable Extension:Translate on OTRS wiki,"Just to make it clear, {{autotranslate}} ({{int:Lang}}), LangSelect (+ {{mld}}), LanguageSelection, LangSwitch have nothing to do with the Translate extension.",1393409802,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"(In reply to Steinsplitter from comment #11)
+> {{autotranslate}} dos not work. The template seems okay. (problems with
+> {{int:*}} ?).
+> 
+> Can someone pleas take a look?
+
+They actually do work, I just overlooked something and told Steinsplitter that they don't seem to work...",1393368243,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"{{autotranslate}} dos not work. The template seems okay. (problems with {{int:*}} ?).
+
+Can someone pleas take a look?",1393366880,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Bungled jargon. Tomasz for the patch/commit,  Reedy deploy. Thanks.",1392370885,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Thanks for the patch, Tomasz, thanks for the commit, Reedy, thanks for the comments, all. This should a very small but useful tool in agent onboarding. :)",1392368934,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,Merged & deployed by Reedy; the extension is now available on the wiki (and working).,1392368737,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Change 113160 merged by jenkins-bot:
+Enable Translate extension on OTRS wiki
+
+https://gerrit.wikimedia.org/r/113160",1392333185,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Change 113160 had a related patch set uploaded by Odder:
+Enable Translate extension on OTRS wiki
+
+https://gerrit.wikimedia.org/r/113160",1392315891,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"(In reply to Keegan Peterzell from comment #0)
+> After a discussion with no objections amongst the OTRS administrators on our
+
+Who? The OTRS admins, the admins on OTRS wiki, the end users on OTRS wiki?
+
+From what i've heard the end users (aka the otrs agents that use the wiki) haven't even been really asked for consensus…",1392289630,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,You would have to do without a translation memory if the content is private.,1392286498,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Eh, I'd rather see OTRS pick up VisualEditor (which is incompatible with the Translate extension...) than the Translate extension. It's a bit of a rough user experience. However the Translate extension _is_ supported on the cluster and if the OTRS admins want it (after consulting with the relevant stakeholders), it's fine to enable there.
+
+This happens to be MediaWiki configuration related to OTRS rather than OTRS configuration related to Wikimedia, so this goes into ""Site requests"" with the ""shell"" keyword.",1392264928,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"Yes, it would be useful for providing documentation pages (like Help: space) in other languages for agents.",1392261727,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+Enable Extension:Translate on OTRS wiki,"(In reply to Keegan Peterzell from comment #0)
+> wiki to facilitate translating messaging. Thanks!
+
+For such a small wiki, Do you really want it? It does complicate the subpage management workflow for some simple functions.",1392260690,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-fde4qftmev4t5neslgqj,task_subcomment,NA
+"VisualEditor: Using ""Make full size"" doesn't work when size is default","Maggie Dennis on bug 50645:
+> I'm not sure if this is the same issue, but as reported on English Wikipedia
+> and tested by myself, using the image resizer to ""Make full size"" resulted in
+> either a notice that no change had been made or a silent failure to save.
+> 
+> This was tested on FF26, W7 and Chrome 32.0.1700.107 m, W7. 
+> 
+> The reporting editor concludes that ""These new settings, for what they are
+> worth, only work if the image already has a size indication (200px,
+> 250px*250px, whatever), not when it only has a 'thumb' indication. Sadly, the
+> latter is the default and by far most common situation.""
+> 
+> He also questions the purpose of ""Make full size"", but I'll report that
+> separately. 
+> 
+> See:
+> https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Feedback&oldid=595141503#Advanced_image_settings.
+> 3F_More_VisualEditor_rubbish.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392223320,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-gwz2iw7f66yzzxl37lvc,task_description,resolved
+"VisualEditor: Using ""Make full size"" doesn't work when size is default","Change 112942 had a related patch set uploaded by Jforrester:
+Update image size properly when size is default
+
+https://gerrit.wikimedia.org/r/112942",1392238144,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gwz2iw7f66yzzxl37lvc,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"In an effort to allow the legal and lca team to work directly on a wiki more often (including for legally sensitive work) and to move away from google docs and the like as much as possible we would like to set up a private wiki for the team.
+
+In general Ombudsmanwiki would be a good wiki to copy settings from but for the ones I can think of off the top of my head:
+
+Wiki domain should be legalwiki.wikimedia.org.
+Language should be English.
+Logo can be $stdlogo.
+Favicon can be wmf.ico
+Canonical server should be https (forced should be on).
+Account creation should be bureaucrat only (not sysop).
+Transwiki destinations of office, collab and meta would be helpful. (Not sure if private wikis can be tw destinations though... if not that's fine.
+wmgUseDisableAccount should be true
+
+I can be the original sysop/crat.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1392140760,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_description,resolved
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,All done here methinks! Enjoy your new wiki.,1394607638,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 117377 merged by jenkins-bot:
+Add logo for legalteamwiki
+
+https://gerrit.wikimedia.org/r/117377",1394546157,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 117377 had a related patch set uploaded by Jalexander:
+Add logo for legalteamwiki
+
+https://gerrit.wikimedia.org/r/117377",1394162684,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to Sam Reed (reedy) from comment #21)
+> (In reply to Sam Reed (reedy) from comment #20)
+> > Does $stdlogo work on other privte wikis?
+> > https://upload.wikimedia.org/wikipedia/legalteam/b/bc/Wiki.png 404s
+> 
+> Because it won't have been uploaded yet... Duh.
+
+Yup, but you are indeed correct, it doesn't work for private wikis because it puts it into a different (private) file url scheme which you have to be logged in to use. I'm uploading a config patch with the logo.",1394162386,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to Sam Reed (reedy) from comment #20)
+> Does $stdlogo work on other privte wikis?
+> https://upload.wikimedia.org/wikipedia/legalteam/b/bc/Wiki.png 404s
+
+Because it won't have been uploaded yet... Duh.",1394120051,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"This is mostly done now...
+
+Does $stdlogo work on other privte wikis? https://upload.wikimedia.org/wikipedia/legalteam/b/bc/Wiki.png 404s",1394120010,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112717 merged by jenkins-bot:
+Enable VisualEditor for legalteamwiki by default
+
+https://gerrit.wikimedia.org/r/112717",1394119668,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112850 merged by jenkins-bot:
+Initial setup for legalteamwiki
+
+https://gerrit.wikimedia.org/r/112850",1394117165,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 116219 merged by Mark Bergsma:
+Apache config for legalteamwiki
+
+https://gerrit.wikimedia.org/r/116219",1394116057,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 116220 merged by Mark Bergsma:
+DNS setup for legalteamwiki
+
+https://gerrit.wikimedia.org/r/116220",1394115465,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 116220 had a related patch set uploaded by Jalexander:
+DNS setup for legalteamwiki
+
+https://gerrit.wikimedia.org/r/116220",1393646524,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 116219 had a related patch set uploaded by Jalexander:
+Apache config for legalteamwiki
+
+https://gerrit.wikimedia.org/r/116219",1393645632,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112716 merged by jenkins-bot:
+Add support for new private legalteamwiki
+
+https://gerrit.wikimedia.org/r/112716",1393343728,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112850 had a related patch set uploaded by TTO:
+Initial setup for legalteamwiki
+
+https://gerrit.wikimedia.org/r/112850",1392185679,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #10)
+> I note that ombudsmenwiki assigns no rights to the autoconfirmed and
+> confirmed
+> groups (except OAuth and transcode rights). Is this required for
+> legalteamwiki?
+
+hmm, no, I just saw that... not entirely sure why that was done but it would be best to still allow the normal options on legalteamwiki. I don't anticipate semi protection being a thing on the wiki obviously but no reason to turn something off (especially upload) without reason.",1392171922,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,I note that ombudsmenwiki assigns no rights to the autoconfirmed and confirmed groups (except OAuth and transcode rights). Is this required for legalteamwiki?,1392171322,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"
+> How about legalteam.wikimedia.org? Using the name legalwiki.wikimedia.org
+> could
+> be confusing, as wiki internal names are by convention formed by taking the
+> subdomain and adding ""wiki"".
+
+> I also disagree with 'legalwiki.wikimedia.org', especially if you see the
+> potential of using legal.wikimedia.org in the future (which would probably
+> be a
+> wiki too, the difference between the two then actually being access controls
+> -
+> and obviously content).
+
+I'm fine with legalteam if we prefer, I don't really care I just want it to make sense and get done :).",1392170704,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"I also disagree with 'legalwiki.wikimedia.org', especially if you see the potential of using legal.wikimedia.org in the future (which would probably be a wiki too, the difference between the two then actually being access controls - and obviously content).",1392170512,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #5)
+> (In reply to comment #1)
+> > Why not legal.wikimedia.org?
+> 
+> To keep legal.wikimedia free incase it's wanted for something broader and
+> more
+> open then a confidential wiki.
+
+How about legalteam.wikimedia.org? Using the name legalwiki.wikimedia.org could be confusing, as wiki internal names are by convention formed by taking the subdomain and adding ""wiki"".",1392170239,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #0)
+> Transwiki destinations of office, collab and meta would be helpful. (Not sure
+> if private wikis can be tw destinations though... if not that's fine.
+
+I don't know that either but would guess that not. Even if, you'd have the problem that any sysop on the target wiki could then make guesses which pages exist on the private wiki and try to import them.",1392142192,PHID-USER-7e4yonmruupxzg23swum,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #1)
+> (In reply to comment #0)
+> 
+> > Wiki domain should be legalwiki.wikimedia.org.
+> 
+> Why not legal.wikimedia.org?
+
+To keep legal.wikimedia free incase it's wanted for something broader and more open then a confidential wiki.",1392142072,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Above patches will allow VisualEditor support; it needs to be created first, however (obviously).",1392141490,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112717 had a related patch set uploaded by Jforrester:
+Enable VisualEditor for legalwiki by default
+
+https://gerrit.wikimedia.org/r/112717",1392141396,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"Change 112716 had a related patch set uploaded by Jforrester:
+Add support for new private legalwiki
+
+https://gerrit.wikimedia.org/r/112716",1392141273,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Create wiki (legalteamwiki) for Wikimedia Foundation legal team,"(In reply to comment #0)
+
+> Wiki domain should be legalwiki.wikimedia.org.
+
+Why not legal.wikimedia.org?",1392140983,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-cpftde25rzzyhyrt3v2b,task_subcomment,NA
+Enable VisualEditor on frwikiversity,"Per e-mail request
+
+Consensus: https://fr.wikiversity.org/wiki/Projet:Wikiversit%C3%A9/Editeur_Visuel
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1392067440,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3i3uyys5czodi4h5dtpg,task_description,resolved
+Enable VisualEditor on frwikiversity,This is now done.,1392253986,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3i3uyys5czodi4h5dtpg,task_subcomment,NA
+Enable VisualEditor on frwikiversity,"Change 112582 had a related patch set uploaded by Jforrester:
+Enable VisualEditor in opt-in mode for French Wiktionary
+
+https://gerrit.wikimedia.org/r/112582",1392067948,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3i3uyys5czodi4h5dtpg,task_subcomment,NA
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to Media Settings>Advanced Settings for the image
+4.Select the value ""None"" under the postion 
+
+Observed Result:
+Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page
+
+See the screenshot attached.
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/10thFeb
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13027}",1392061500,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_description,declined
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page",Think this is OK now?,1395354482,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_subcomment,NA
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page","When I try this in betalabs, the image shifts to the left of the page when I select ""None"", as expected.
+
+There is, however, another bug where the image doesn't have an *initial* position visible in the editor. That is fixed in the upcoming commit that I mentioned above.",1392158997,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_subcomment,NA
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page","I can't manage to replicate this bug in master. ""None"" shifts the image to the left in an English wiki, and right in an RTL wiki (Hebrew on my local machine)
+
+That said, this fix changes the behavior of the position widget. I tested it under that commit as well and couldn't replicate in both Chrome and Firefox.
+
+https://gerrit.wikimedia.org/r/#/c/112041/",1392155216,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_subcomment,NA
+"VisualEditor: Selecting ""None"" as position in Media Settings>Advanced Settings shifts the image to the right of the page","After that , Selecting Right moves the image to the left",1392061763,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dpqe4m25ofueoo7qs7ie,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"'Cos we do most of the others.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1391818800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fm5h62v32kkok5qvd6go,task_description,resolved
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"Change 133037 merged by jenkins-bot:
+Allow VisualEditor users to set if a page whether a Disambiguation
+
+https://gerrit.wikimedia.org/r/133037",1402341616,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"Change 130328 merged by jenkins-bot:
+Allow extensions to add extra meta item checkboxes to the page settings dialog
+
+https://gerrit.wikimedia.org/r/130328",1401323601,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"Change 133037 had a related patch set uploaded by Alex Monk:
+Allow VE users to set whether a page is for Disambiguation or not
+
+https://gerrit.wikimedia.org/r/133037",1399936920,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"Change 130328 had a related patch set uploaded by Alex Monk:
+Allow users to set whether a page is for Disambiguation or not
+
+https://gerrit.wikimedia.org/r/130328",1398775468,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,"I guess we could query action=paraminfo&querymodules=querypage and look for ""DisambiguationPages"" in data.paraminfo.querymodules[0].parameters[0].type
+
+Would prefer not to though. Might have to pass whether or not Disambiguation is there via paction=parse (ugh)",1398773973,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel,Looks like we need to try to detect the Disambiguation extension somehow...,1398126883,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-fm5h62v32kkok5qvd6go,task_subcomment,NA
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"Appears towards the end of the page
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Select a text in such way that it selects the whole line
+3.Now open the link inspector
+
+Observed Result:
+
+Sometimes the link inspector appears in a broken way and sometimes it appears little below the text towards the end of the page
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12833}",1391817120,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-db4a2ffve3au67ttwvrv,task_description,resolved
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"On discussion, we'll leave this as is.",1406322759,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-db4a2ffve3au67ttwvrv,task_subcomment,NA
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"Created attachment 15640
+12thjune
+
+The broken UI issue seems like got fixed, but if a gallery follows a line and I select the whole line and try to open the link inspector , it still opens at the end of the page after the gallery.
+See the recent screesnhot attached:12thjune
+
+**Attached**: {F12836}",1402620035,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-db4a2ffve3au67ttwvrv,task_subcomment,NA
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"I think that we fixed this recently, though I can't pin it down.",1402549804,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-db4a2ffve3au67ttwvrv,task_subcomment,NA
+VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link,"Created attachment 14528
+Broken UI
+
+**Attached**: {F12835}",1391817253,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-db4a2ffve3au67ttwvrv,task_subcomment,NA
+"VisualEditor: After inserting a gallery, the newly inserted gallery does not remain highlighted but the inspector icon shows up at the corner of the page","Screenshot
+
+steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Gallery 
+3.Insert a gallery
+
+Observed Result:
+The newly inserted gallery is not highlighted but the gallery inspector icon is appearing at the corner of the page which is not consistent with the behavior observed with other link inspectors like Math/Hiero
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12822}",1391814840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zvvrmcmz4eig3vs37trj,task_description,resolved
+"VisualEditor: After inserting a gallery, the newly inserted gallery does not remain highlighted but the inspector icon shows up at the corner of the page","mwGallery is not in the insert menu anymore, but testing locally they do appear to highlight correctly if they are re-enabled.",1402921585,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-zvvrmcmz4eig3vs37trj,task_subcomment,NA
+"VisualEditor: After inserting a gallery, the newly inserted gallery does not remain highlighted but the inspector icon shows up at the corner of the page","Actually, every time when I try to select the newly inserted gallery , it seems its not selecting it as it does not get highlighted like the usual selection behavior, however the gallery inserter icon appears at the far right end.",1392765753,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zvvrmcmz4eig3vs37trj,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,"Steps to reproduce:
+
+1.Open a page with VE which contains an image
+
+2.Open the media settings for the image
+
+3.Go to the advanced settings page
+
+4.Now switch the browser tab or window and then again switch back
+
+
+Observed Result:
+
+The tab in Media Settings got switched to General Settings from Advanced Settings.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391813340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_description,resolved
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,yeah! Not reproducible anymore at my end as well.,1416264866,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,Rummana?,1416182261,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,"I can't reproduce this in Chrome on my local wiki. Rummana, can you still reproduce this issue?",1408842460,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,"As noted in bug 61226, I can't reproduce this in Firefox.  
+
+I can reproduce it at the English Wikipedia, not only at Beta Labs.",1392156155,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings,*** Bug 61226 has been marked as a duplicate of this bug. ***,1392144760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ozvmsbsv7fj3xaensg4b,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Steps to reproduce:
+
+1.Open the page in VE
+2.Insert an image
+3.Go to Media Settings>Advanced Settings
+4.Now delete the first digit of the size.For example:if you have size :600*450
+Just attempt to make it 500*450
+
+Observed Result:
+The Width and the Height both values turned into 0.User have to again type the input of Height value which he might not wanted to change.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1391812020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_description,resolved
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394754565,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,Verified the fix in test2 environment.,1394233667,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Change 115939 merged by jenkins-bot:
+Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1394046692,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Change 115939 had a related patch set uploaded by Mooeypoo:
+[wip] Deal with 'none'/'border' and default size in media edit
+
+https://gerrit.wikimedia.org/r/115939",1393991576,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"I'm working on trying to get default size to work. There are several technical problems I am trying to sort through now, but once those are solved, we'll be able to have more options with default size, like a 'default' button and reverting to default on 0 value.",1392851126,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"What about making any ""0"" immediately become the wiki's default size?  
+
+Right now, there's no way to remove a size and return to unspecified default (see bug 50379).",1392850649,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"The problem is that the size widget constantly adjusts both values numerically, so value ""00"" in the width is read as the number '0', which actively changes the value in the height input (to 0). 
+
+Now, since a change occurred in height, that triggers an automatic change to width, which brings it down to the number 0.
+
+We can fix this by not triggering the adjustment on keypress but rather when you leave the input (so, onChange event) but that has several other issues it may raise. For instance, what happens if I changed a width without moving away from the input (technically no 'change' input event) and then clicked the ""Apply"" button? The corresponding dimension didn't get updated, and while the 'change' event will trigger when I click the button (because the input loses focus) it will be too late to notify the user of a changed dimension.
+
+I am not sure how this can be fixed without removing the functionality of updating both dimensions simultaneously. We should discuss this further.",1392178859,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"If the size is ""400"" and you delete the first character (4), it becomes ""00"", which instantly becomes ""0"". Undoing this restores the 4… so it becomes ""40"" (and there's nothing left on the browser undo stack).
+
+Maybe if you change the value such that it doesn't make sense, rather than cleaning up ""00"" or ""0"" and then complaining, we should just blank the field?",1392162652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Cannot replicate in master.
+
+Changing the size in either width or height (by deleting or changing the first digit or typing from scratch) changes the corresponding input.
+
+Example:
+
+- Inserted an image with initial size 182x150
+- Media settings -> Advanced settings, deleted '1' to result in width: 82
+- Result: Height adjusted to 68 (Expected)
+- Marked the first digit in Width (8) and changed to 9
+- Result: Height adjusted to 76
+
+This works for me in both Chrome and Firefox.
+
+Am I missing any details to replicate?",1392156609,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields,"Created attachment 14524
+Screenshot
+
+**Attached**: {F12816}",1391812142,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-aaoipsgz7oyqufzeblee,task_subcomment,NA
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"Intention:
+Add a link to a template using {{tl}} on English Wikipedia.
+
+Steps to Reproduce:
+1.  Add Template:Tl.
+2.  Add any template name, and press return afterwards (so that the parameter field is name+return)
+3.  Apply changes.
+
+Expected Results: No newline is inserted.
+
+Actual Results:  
+The template is broken because the parameter can't support the inclusion of a return.
+",1391799720,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_description,open
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"`modules/ve-mw/ui/pages/ve.ui.MWParameterPage.js` actually has `// TODO: Use spec.type` :) (should be `getParameterType()`, rather).",1423675992,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_subcomment,NA
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"This is now being done for named parameters per T52439, which do not preserve whitespace. However, it must not be done for positional parameters (like in {{tl}}) per T53484, because these do actually preserve whitespace.
+
+Like Krenair says, VE shouldn't use multiline text inputs for single-line parameters, like this one (I just fixed the templatedata on en.wp). Let's rephrase the bug.",1423675689,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_subcomment,NA
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"I wonder if this parameter should be marked with TemplateData type ""line"" and VE should enforce this in the input.",1421887933,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_subcomment,NA
+VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input),"If it's not desirable to always strip returns (or spaces) from the end of parameters, then perhaps we should be able to specify in TemplateData how they should be handled.",1391799788,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yuhi6ibmivh2wft5t4tf,task_subcomment,NA
+VisualEditor:  Pipe trick in templates displays wikitext rather than link,"Intention:
+Add more information to an infobox.
+
+Steps to Reproduce:
+1. Open the infobox.
+
+2. Add a parameter with a link to a disambiguated page name.
+
+3. Use the pipe trick to label the link: [[Wooden spoon (award)|]]
+
+4.  Apply changes.
+
+Actual Results:  
+In VisualEditor, the template displays raw wikitext for that item:   [[Wooden spoon (award)|]] 
+
+Expected Results:  
+That VisualEditor would display the same blue link with the same link label as the page will when it is saved (""Wooden spoon"")
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=594279537&oldid=593922721",1391726580,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-wvcdfkoucmmc4frpdguw,task_description,resolved
+VisualEditor:  Pipe trick in templates displays wikitext rather than link,"Change 112829 merged by jenkins-bot:
+Pass 'pst' as true in parse request for fragments
+
+https://gerrit.wikimedia.org/r/112829",1392175345,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wvcdfkoucmmc4frpdguw,task_subcomment,NA
+VisualEditor:  Pipe trick in templates displays wikitext rather than link,"Change 112829 had a related patch set uploaded by Jforrester:
+Pass 'pst' as true in parse request for fragments
+
+https://gerrit.wikimedia.org/r/112829",1392167341,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-wvcdfkoucmmc4frpdguw,task_subcomment,NA
+VisualEditor:  Pipe trick in templates displays wikitext rather than link,This looks like we're passing the wrong flag to action=parse; will try to fix this myself.,1392167168,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wvcdfkoucmmc4frpdguw,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"CTRL/CMD+B for bolding highlighted text
+CTRL/CMD+I for italicising highlighted text
+CTRL/CMD+U for underline highlighted text
+
+CTRL+1,2,3 for H1,H2, H3, etc
+
+CTRL/CMD+K for linking highlighted text
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1391648220,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-bothhqbjosqeckagzghn,task_description,resolved
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I disagree that those are not basic action keyboard shortcuts, especially as they were mentioned in the task description, but nonetheless created {T380087}.",1731695395,PHID-USER-3ljmcrqixyljk2wy63jb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"You can file a separate task for that – those are more controversial as they conflict with browser shortcuts for navigating between tabs on Windows. This ticket is for ""basic formatting and action keyboard shortcut commands"". (Not to mention being harder to implement as the VE behaviour is to use Control key instead of Cmd on Mac.) ",1731675074,PHID-USER-52k2lmr37woy42l6kdmv,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,I still think Ctrl+1/2/3/4/5/6 should’ve been also added. It was also in the task description. I don’t think resolving this task without it is satisfactory enough.,1731672860,PHID-USER-3ljmcrqixyljk2wy63jb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,Suggested blurb: `The 2010 wikitext editor now supports common keyboard shortcuts such Ctrl-B for bold and Ctrl-I for italics.` (?) Full list of shortcuts: [[https://www.mediawiki.org/wiki/Help:Extension:WikiEditor#Keyboard%20shortcuts|mw:Help:Extension:WikiEditor#Keyboard_shortcuts]].,1731648287,PHID-USER-52k2lmr37woy42l6kdmv,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1080802 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/CodeMirror@master] CodeMirror support for WikiEditor keyboard shortcuts%%%
+https://gerrit.wikimedia.org/r/1080802",1730823154,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1079588 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/WikiEditor@master] Retry adding keyboard shortcuts for formatting tools in WikiEditor 2010%%%
+https://gerrit.wikimedia.org/r/1079588",1729708413,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1080802 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/CodeMirror@master] CodeMirror support for WikiEditor keyboard shortcuts%%%
+https://gerrit.wikimedia.org/r/1080802",1729108501,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#10230819, @SD0001 wrote:
+> To turn on syntax highlighting, click the highlighter icon in the toolbar.
+> 
+> {F57617417}
+
+Aah, thanks! That workaround does work well.",1729020018,PHID-USER-b54igy3ozftikuepd4t5,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#10230819, @SD0001 wrote:
+> To turn on syntax highlighting, click the highlighter icon in the toolbar.
+> 
+> {F57617417}
+
+Aah, thanks!",1729020005,PHID-USER-b54igy3ozftikuepd4t5,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"To turn on syntax highlighting, click the highlighter icon in the toolbar.
+
+{F57617417}",1729017459,PHID-USER-52k2lmr37woy42l6kdmv,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,This is quite frustrating for dvorak users ... any timeframe for it being reverted / help pointing out how to turn syntax highlighting on? Surprised this wasn't mentioned in yesterday's Tech News.,1729016245,PHID-USER-b54igy3ozftikuepd4t5,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1079588 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/WikiEditor@master] Retry adding keyboard shortcuts for formatting tools in WikiEditor 2010%%%
+https://gerrit.wikimedia.org/r/1079588",1728724103,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1078960 **abandoned** by SD0001:
+%%%[mediawiki/extensions/WikiEditor@master] shortcuts: Use KeyboardEvent.key instead of KeyboardEvent.code%%%
+Reason:
+%%%KeyboardEvent.key is no good either, will%%%
+https://gerrit.wikimedia.org/r/1078960",1728724023,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Both of those links work fine! The only issue for me is in the normal editor (""action=edit""), when syntax highlighting is off.",1728689571,PHID-USER-2vkn56bsbelr5lsqnrwf,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"@Leijurv @jhsoby as Dvorak keyboard users, can you tell us if this problem is also present in VisualEditor? https://en.wikipedia.org/w/index.php?title=Draft:Sandbox&veaction=edit (visual mode) or https://en.wikipedia.org/w/index.php?title=Draft:Sandbox&veaction=editsource (source mode)
+
+If it is, it might be good to create/use a JS solution to solve a separate issue for all editing environments. There is also a possibility that people with QWERTZ layout (German) might be confused when Ctrl+Z/Ctrl+Y work differently. I’ve found some attempts from people to solve this, though maybe it is already solved in VE: https://stackoverflow.com/questions/70211837/keyboard-shortcuts-commands-on-non-latin-alphabet-keyboards-javascript",1728683487,PHID-USER-3ljmcrqixyljk2wy63jb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#10222826, @SD0001 wrote:
+> Workaround is to turn on syntax highlighting. The shortcuts don't work with CodeMirror enabled.
+That seems like another issue to fix if this gets re-added, btw. https://ru.wikipedia.org/wiki/Участник:Stjn/wikiEditorShortcuts.js#L-132 shows how.",1728682757,PHID-USER-3ljmcrqixyljk2wy63jb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Thanks, that works!",1728682698,PHID-USER-2vkn56bsbelr5lsqnrwf,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,Workaround is to turn on syntax highlighting. The shortcuts don't work with CodeMirror enabled.,1728682480,PHID-USER-52k2lmr37woy42l6kdmv,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Noting that I am now unable to copy/paste in the editor since I use Dvorak. It looks like this will be reverted by next Thursday, but any workaround in the meantime?
+
+
+{F57606954}",1728682028,PHID-USER-2vkn56bsbelr5lsqnrwf,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1078939 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/WikiEditor@master] Revert ""Keyboard shortcuts for formatting tools in WikiEditor 2010""%%%
+https://gerrit.wikimedia.org/r/1078939",1728581579,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Sure, done.",1728576037,PHID-USER-52k2lmr37woy42l6kdmv,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Restating [[ https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikiEditor/+/1078939/comment/d51e1dc6_57d42d3f/ | my comment ]] on the gerrit changeset, I'd suggest that we revert first and try again after. Is that okay @SD0001?",1728570239,PHID-USER-hu7nuhczm4gmfufd4qmg,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Only like this:
+```
+$( '#wpTextbox1' ).on( 'keydown', ( e ) => {
+	console.log( e.key );
+} );
+```
+{F57601389}",1728492687,PHID-USER-3ljmcrqixyljk2wy63jb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#10214676, @stjn wrote:
+> AFAIK he new provided patch and the suggestion would make it impossible to use this feature for people on non-Latin keyboards (since `e.key` for `K` doesn’t match to `K` or `k` on a Russian keyboard, it would match to `Л` or `л`), therefore reducing the usability of this tremendously. I understand the concern with Dvorak keyboards, but maybe there are better ways to resolve this than this.
+
+Did you test this? My understanding is that when Cmd/Ctrl modifiers are held pressed, `e.key` will be `k` even on a non-Latin keyboard. Caps lock also doesn't make a difference with Cmd/Ctrl pressed, `e.key` is always in lowercase.",1728492460,PHID-USER-52k2lmr37woy42l6kdmv,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"AFAIK he new provided patch and the suggestion would make it impossible to use this feature for people on non-Latin keyboards (since `e.key` for `K` doesn’t match to `K` or `k` on a Russian keyboard, it would match to `Л` or `л`), therefore reducing the usability of this tremendously. I understand the concern with Dvorak keyboards, but maybe there are better ways to resolve this than this.",1728486467,PHID-USER-3ljmcrqixyljk2wy63jb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1078960 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/WikiEditor@master] shortcuts: Use KeyboardEvent.key instead of KeyboardEvent.code%%%
+https://gerrit.wikimedia.org/r/1078960",1728484462,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Submitted the revert above because the patch basically makes it impossible for me to copy/paste things, since it hijacks Ctrl+C and Ctrl+V on dvorak keyboards (and possibly other layouts too?). The revert commit message has suggestions for how to fix this.",1728481422,PHID-USER-jqjb54lbf7psat6shbcc,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1078939 had a related patch set uploaded (by Jon Harald Søby; author: Jon Harald Søby):
+%%%[mediawiki/extensions/WikiEditor@master] Revert ""Keyboard shortcuts for formatting tools in WikiEditor 2010""%%%
+https://gerrit.wikimedia.org/r/1078939",1728480582,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"@SD0001 also, just as a note, is Ctrl+1/2/3/4/5 not being a thing intentional? Those are available in the visual editor and seem very useful to have.",1728337911,PHID-USER-3ljmcrqixyljk2wy63jb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"The currently merged patch is a step in the good direction, but it doesn’t contain any indication for editors that they can press certain shortcuts to press the buttons. Would be good to add that.",1728042761,PHID-USER-3ljmcrqixyljk2wy63jb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1077335 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/WikiEditor@master] Keyboard shortcuts for formatting tools in WikiEditor 2010%%%
+https://gerrit.wikimedia.org/r/1077335",1728042228,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Change #1077335 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/WikiEditor@master] Keyboard shortcuts for formatting tools in WikiEditor 2010%%%
+https://gerrit.wikimedia.org/r/1077335",1727863734,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,">>! In T62928#4779443, @TheDJ wrote:
+> I think it is very unlikely this will ever be added to #wikieditor, now that we have #visualeditor-mediawiki-2017wikitexteditor providing this functionality.
+
+As time has shown, the majority of users didn't migrate to that.",1711379875,PHID-USER-p6gpvwnc6ske65oxuoof,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I'm about to implement the shortcuts in #convenient-discussions as this is requested by users and I would rather not implement this apart from WikiEditor which Convenient Discussions employs. But if there is no activity in this task, I will have to.",1711379545,PHID-USER-p6gpvwnc6ske65oxuoof,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I'm about to implement the shortcuts in #convenient-discussions as this is requested by users and I would rather not implement this apart from WikiEditor. But if there is no activity in this task, I will have to.",1711379514,PHID-USER-p6gpvwnc6ske65oxuoof,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"In the meantime, https://ru.wikipedia.org/wiki/Участник:Stjn/wikiEditorShortcuts.js provides similar functionality. But I do think that all modes of editing need to have the same keyboard shortcuts (at least where that makes sense) for a better user experience.",1624989209,PHID-USER-3ljmcrqixyljk2wy63jb,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I think it is very unlikely this will ever be added to #wikieditor, now that we have #visualeditor-mediawiki-2017wikitexteditor providing this functionality.",1543356971,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I'm not sure which of these is most uptodate, but... here are some known knowns.
+
+* https://www.mediawiki.org/wiki/Manual:Interface/Access_keys
+* https://meta.wikimedia.org/wiki/Help:Keyboard_shortcuts
+* https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+* https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts",1728063933,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"I'm not sure which of these is most uptodate, but... here are some known knowns.
+
+    https://www.mediawiki.org/wiki/Manual:Interface/Access_keys
+
+    https://meta.wikimedia.org/wiki/Help:Keyboard_shortcuts
+
+    https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+
+    https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts",1403684232,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+WikiEditor: Provide some basic formatting and action keyboard shortcut commands,"Moving to WikiEditor; we're probably going to kill the difference between the two, but for now…",1403657041,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bothhqbjosqeckagzghn,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page","Screenshot
+
+Steps to reproduce:
+
+1.Open the page with VE
+2.Add a text with reference
+3.Add an image
+4.Go to Media Settings for the image
+5.Go to Insert>Reference
+
+Observed Result:
+Observe that, the ""Use an existing reference "" button remains disabled even if there is a reference added in the page
+
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Wmf12chrome?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13113}",1391638020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qkmndwu7hujefvxd4fpz,task_description,open
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page",">>! In T62919#3709391, @Deskana wrote:
+> This specific problem doesn't happen any more, although there is some really weird UI stuff going on...
+> 
+> {F10426560}
+
+Actually this issue is still happening. It was about ""Use an existing reference"" button  inside Media Settings>Cite> Basic reference dialog remaining disabled. 
+
+Updated screenshots:
+
+{F10521929}
+",1509395078,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page",">>! In T62919#3709391, @Deskana wrote:
+> This specific problem doesn't happen any more, although there is some really weird UI stuff going on...
+
+For posterity, the weird UI stuff is filed as {T178986}.
+
+",1508929740,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page","This specific problem doesn't happen any more, although there is some really weird UI stuff going on...
+
+{F10426560}",1508929246,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page","This is blocked by bug 47344, the infamous sub-documents bug.",1415054491,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page","(In reply to Ed Sanders from comment #1)
+> Looks like we aren't copying over the internalList object from the parent dm
+> document.
+
+Does that explain bug 58322 or bug 71214?",1414883288,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+"VisualEditor: ""Use an Existing Reference"" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page",Looks like we aren't copying over the internalList object from the parent dm document.,1391644762,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qkmndwu7hujefvxd4fpz,task_subcomment,NA
+Enable VisualEditor in the Projekt namespace on se.wikimedia.org,"Please enable VisualEditor also in the ""Projekt"" namespace on the wmse chapters wiki.
+
+Please note that this is not the same as the NS_PROJECT/Wikimedia
+namespace.
+
+Poll/request at: https://se.wikimedia.org/wiki/Tr%C3%A5d:Wikimedia:Bybrunnen/VisualEditor_p%C3%A5_Projekt:-sidorna
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1391599320,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-pkc5qf2xz72ywhnd6t26,task_description,resolved
+Enable VisualEditor in the Projekt namespace on se.wikimedia.org,Merged & deployed by Reedy (thank you!).,1392330904,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-pkc5qf2xz72ywhnd6t26,task_subcomment,NA
+Enable VisualEditor in the Projekt namespace on se.wikimedia.org,"Change 113141 merged by jenkins-bot:
+Enable VisualEditor for Projekt: NS on sewikimedia
+
+https://gerrit.wikimedia.org/r/113141",1392327485,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pkc5qf2xz72ywhnd6t26,task_subcomment,NA
+Enable VisualEditor in the Projekt namespace on se.wikimedia.org,"Change 113141 had a related patch set uploaded by Odder:
+Enable VisualEditor for Projekt: NS on sewikimedia
+
+https://gerrit.wikimedia.org/r/113141",1392311448,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pkc5qf2xz72ywhnd6t26,task_subcomment,NA
+Create an API module to allow apps to set global preference,"Discussion: {T196314}
+
+Deliverables:
+* API module to allow apps to set global value for a preference.
+
+See also:
+* {T197259}
+* {T197260}
+",1391567760,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-52g62pbs7jogl5cwjmrs,task_description,resolved
+Create an API module to allow apps to set global preference,"Change 442219 **merged** by jenkins-bot:
+[mediawiki/extensions/GlobalPreferences@master] Add an API module to set global preferences
+
+[[https://gerrit.wikimedia.org/r/442219]]",1530849525,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"Change 442218 **merged** by jenkins-bot:
+[mediawiki/core@master] Refactor ApiOptions for reusability
+
+[[https://gerrit.wikimedia.org/r/442218]]",1530080174,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"Change 442219 had a related patch set uploaded (by MaxSem; owner: MaxSem):
+[mediawiki/extensions/GlobalPreferences@master] Add an API module to set global preferences
+
+[[https://gerrit.wikimedia.org/r/442219]]",1530053782,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"Change 442218 had a related patch set uploaded (by MaxSem; owner: MaxSem):
+[mediawiki/core@master] Refactor ApiOptions for reusability
+
+[[https://gerrit.wikimedia.org/r/442218]]",1530053670,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,I think the biggest use case for this is to support setting the edit tabs preference across all wikis at once from the VisualEditor popup.,1519666006,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"OK, thank you Sam. We'll keep it on the GlobalPrefs backlog for now.",1519665689,PHID-USER-5s7hp7zjreoi3dmulai3,False,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,"It probably wouldn't be too hard to add, but without a use case in mind I think it can be postponed.
+",1519434599,PHID-USER-hlhhe6qw6qfkl7wyfhxk,False,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+Create an API module to allow apps to set global preference,@Samwilson  Do we need to do anything with this task? Herald says hi.,1519430411,PHID-USER-5s7hp7zjreoi3dmulai3,False,PHID-TASK-52g62pbs7jogl5cwjmrs,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"**Author:** `jhall`
+
+**Description:**
+While developing a browser test for bug 60797, I've noticed that some production wikis where VisualEditor is expected to be available do not load VE as expected.  In each case, the error message captured at the browser level is (with some variation in the specific line numbers referenced):
+
+
+[Error] Error: JavaScript parse error: Parse error: Missing operand in file 'MediaWiki:Common.js' on line 125
+	global code (load.php, line 1)
+
+
+
+Repro steps:
+
+1) Visit a production wiki where VE is expected to be available, and request a random article with a VE edit param: http://cv.wikipedia.org/wiki/Special:Random?veaction=edit
+
+2) In browser error console, note JavaScript error mentioned above, and note also that the VE editing surface simply never loads (although it appears to keep trying!)
+
+
+I'll add list(s) of production wikis where this problem occurs as I uncover them in comments on this bug ticket.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60797",1391544360,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_description,resolved
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"Change 127373 merged by jenkins-bot:
+[Browser tests] Updated list of production wikis to check
+
+https://gerrit.wikimedia.org/r/127373",1397858649,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"Change 127373 had a related patch set uploaded by Jforrester:
+[Browser tests] Updated list of production wikis to check
+
+https://gerrit.wikimedia.org/r/127373",1397857736,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"Updated current list of failures:
+
+http://bpy.wikipedia.org
+http://cv.wikipedia.org
+http://mzn.wikipedia.org
+http://new.wikipedia.org
+
+I have fixed:
+
+> http://af.wikipedia.org
+> http://am.wikipedia.org
+> http://kaa.wikipedia.org
+> http://ln.wikipedia.org
+> http://szl.wikipedia.org",1394501677,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"**jhall** wrote:
+
+Found one more, so here's a consolidated list of ""broken"" wikis identified so far:
+
+http://af.wikipedia.org
+http://am.wikipedia.org
+http://bpy.wikipedia.org
+http://cv.wikipedia.org
+http://kaa.wikipedia.org
+http://ln.wikipedia.org
+http://mzn.wikipedia.org
+http://new.wikipedia.org
+http://szl.wikipedia.org",1391554304,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"**jhall** wrote:
+
+Some more wikis with the same problem:
+
+http://kaa.wikipedia.org
+http://ln.wikipedia.org
+http://mzn.wikipedia.org
+http://new.wikipedia.org
+http://szl.wikipedia.org",1391548251,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+VisualEditor: Broken local Common.js causes VE not to be available on some wikis,"**jhall** wrote:
+
+Wikis where this problem has been seen:
+
+http://af.wikipedia.org
+http://bpy.wikipedia.org
+http://cv.wikipedia.org",1391544768,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hg2cfd2lpoag3lfyqcii,task_subcomment,NA
+"Native Mac OS special character inserter fails to get content into DM, just CE, in Safari","Intention:
+Add a special character from the built-in Mac OS character inserter.
+
+Steps to Reproduce:
+1. Using Safari, open a page in VisualEditor.
+
+2. In Safari's menu bar, choose Edit > Special Characters...
+
+3. Double-click on special characters to add them.
+
+Actual Results:  
+The special characters display on the screen, but are not present when you try to save the text.  Characters that were typed from the keyboard are saved.  No characters (even if they are 'normal' ones) are saved if they were added with the character inserter.
+
+
+Reproducible: Always
+
+It works in Firefox 26.  It does not work in Safari 6.  I haven't tested Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391541420,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5dustpsver5abqahxsbc,task_description,resolved
+"Native Mac OS special character inserter fails to get content into DM, just CE, in Safari","This is now working, presumably through the same fix that fixed {T61748}.",1428511594,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5dustpsver5abqahxsbc,task_subcomment,NA
+"Native Mac OS special character inserter fails to get content into DM, just CE, in Safari",Confirmed in Safari 8.0 in VE master as of now; almost certainly the same issue as {T61748} and {T63884}.,1417578194,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5dustpsver5abqahxsbc,task_subcomment,NA
+"Native Mac OS special character inserter fails to get content into DM, just CE, in Safari","Created attachment 14484
+The red oval on the far left shows the three characters (one normal 'r' and two fancier ones) added with the OS's special character inserter.  These should appear in the Review Changes diff, but don't
+
+**Attached**: {F12931}",1391541678,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5dustpsver5abqahxsbc,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image in the page
+3.Open the Media Settings for that image
+4.Insert another image inside it.
+5.Apply Changes
+6.Save the page
+7.Reopen the page again
+8.Open the media settings again for the image on the page
+
+
+Observed Result:
+VE stops reposnding.Cannot cross out the dialog box.""Apply Changes"" does not close the dialog box.
+An error appears in the console
+Error: Offset could not be translated to a DOM element and offset: 22
+	
+
+(297 out of range 182)
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/3rdfebFF?veaction=edit
+
+See the screenshot attached,
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12818}",1391467620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o64myfteta7sv33kwhio,task_description,resolved
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1391734538,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111695 merged by jenkins-bot:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111695",1391731445,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,Verified the fix in Betalabs,1391712726,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111695 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111695",1391650882,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111694 abandoned by Catrope:
+Make globalOverlay really global
+
+Reason:
+Wrong branch
+
+https://gerrit.wikimedia.org/r/111694",1391650784,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111694 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111694",1391650754,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111690 merged by jenkins-bot:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111690",1391649998,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"Change 111690 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111690",1391649620,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor: VE stops responding while opening Media Settings for an image that contains another image,"This error also appears when you delete the reflist that contains a reference which has image inside:
+
+Error: Offset could not be translated to a DOM element and offset: 31
+	
+
+(297 out of range 182)",1391473010,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-o64myfteta7sv33kwhio,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Insert an image and a reference
+3.Open the Media Settings for the image and include another image
+4.Click on the Media Settings icon on the second image that you just inserted
+OR
+5.Open the reference dialog box
+6.Add an image inside
+7.Click on the Media Settings icon on the image you just inserted
+
+Observed Result:
+In both cases after step 4 and step 7, Media Settings dialog box does not open up
+In the console following error appears:
+NS_ERROR_NOT_AVAILABLE:
+	
+
+...w Date()).getTime();}});jQuery.ready.promise=function(obj){if(!readyList){readyL...
+
+load.p...034436Z (line 11)
+
+See the screenshot attached
+
+**This is happening in FireFox only** 
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13424}",1391465040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_description,resolved
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1391734427,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111695 merged by jenkins-bot:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111695",1391731448,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,Verified the fix in Betalabs,1391712647,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111695 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111695",1391650886,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111694 abandoned by Catrope:
+Make globalOverlay really global
+
+Reason:
+Wrong branch
+
+https://gerrit.wikimedia.org/r/111694",1391650781,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111694 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111694",1391650758,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111690 merged by jenkins-bot:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111690",1391650000,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings,"Change 111690 had a related patch set uploaded by Catrope:
+Make globalOverlay really global
+
+https://gerrit.wikimedia.org/r/111690",1391649625,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ongcgoxsyk4s52fr7dbg,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,"screenshot of empty gallery in edit mode
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Go to Insert>Gallery
+3.Just close the inspector
+
+Observed Result:
+An empty gallery inspector is getting added in the page
+
+
+See the screenshot attached.
+
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:
+https://test2.wikipedia.org/w/index.php?title=31st_january&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13379}",1391456820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_description,resolved
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,Verified the fix on test2,1392254285,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,Verified the fix in Betalabs,1391720180,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,*** Bug 60914 has been marked as a duplicate of this bug. ***,1391668703,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,Fixed in gerrit 111178.,1391660307,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content,"Created attachment 14456
+Screenshot in edit source mode
+
+**Attached**: {F13380}",1391456863,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a2hfohfk5j5mwllqwzu6,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Firefox also supports CSS3 animations and transitions, see how it can be done: http://tympanus.net/Development/ModalWindowEffects/
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1391263200,PHID-USER-b27lopawgf2h6utuuqyi,False,PHID-TASK-sa4ylwldmmhrky72otw3,task_description,declined
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Now everything has the same appearance like in Chrome, so well done!",1394980634,PHID-USER-b27lopawgf2h6utuuqyi,False,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"(In reply to Andre Klapper from comment #4)
+> Hello! Nobody yet, obviously. 
+> If this functionality is important to you, providing patches speeds up
+> getting this implemented. See https://www.mediawiki.org/wiki/Developer_access
+
+Thanks Andre!",1393064445,PHID-USER-b27lopawgf2h6utuuqyi,False,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Hello! Nobody yet, obviously. 
+If this functionality is important to you, providing patches speeds up getting this implemented. See https://www.mediawiki.org/wiki/Developer_access",1393010006,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Hello? Nobody?
+Dialog animations have been already implemented(!) and work in Chrome, only!
+Could someone create some CSS love for Firefox as well?",1393005931,PHID-USER-b27lopawgf2h6utuuqyi,False,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"(In reply to comment #1)
+> Why should VE ""support"" this? I am missing a usecase / user story here so
+> far.
+
+This animation is supported in Google Chrome/Chromium, just open this dialog in this browser and see. Same effect can be done in Firefox as well. VE has this animation already implemented!",1391428321,PHID-USER-b27lopawgf2h6utuuqyi,False,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+VisualEditor: [Regression] Fix dialog animation in Firefox,"Why should VE ""support"" this? I am missing a usecase / user story here so far.",1391345406,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-sa4ylwldmmhrky72otw3,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown","For wikis with FlaggedRevs extension: After saving a page the notice on top of page ""1 change in this version is pending review ..."" is not shown.
+
+I guess due to not reloading the whole page.
+
+This is a bad experience for every editor w/o reviewer right. No chance to spot that the new revision has to be sighted first.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391255160,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-6zaw3in4igorb3k4bavq,task_description,resolved
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown","Change 172746 merged by jenkins-bot:
+When saving, return the full contentSub to the client
+
+https://gerrit.wikimedia.org/r/172746",1415911512,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown",(It's slightly less horrible now. But only slightly.),1415805215,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown","Change 172746 had a related patch set uploaded by Alex Monk:
+When saving, return the full contentSub to the client
+
+https://gerrit.wikimedia.org/r/172746",1415805160,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown",I came up with some terrible code that successfully achieves this yesterday.,1415459670,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: After saving a page, the FlaggedRevs notice ""1 change in this version is pending review ..."" is not shown",I took a look into this today... Seems that the review notice is not being made available even as part of the page subtitle to VE.,1415326465,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6zaw3in4igorb3k4bavq,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","Screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add any image 
+3.Go to Media Settings>Advanced Settings
+4.Say for example the original dimension of the image is  150x150
+5.Change the values in such way that it exceeds the original size for example: 300x300
+
+Observed Result:
+Apply Changes button remains active even though ""Size values are invalid "" appears in the dialog box.
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Sample Page:http://en.wikipedia.beta.wmflabs.org/wiki/29th_January?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12971}",1391035980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mtoupxdcw637uabefm23,task_description,resolved
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","This has been fixed in {20c4fbbc1e1ffa61a8716ead01d5efebffa11931}. Invalid dimensions now cause the ""Apply changes"" button to be disabled.
+
+{F26724268}",1540269111,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","I think this can be best ""fixed"" by altering the design and copy so that it's clear that invalid changes won't be put into effect.",1391661046,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","The problem in my opinion with #2 is that if a user spent time working on new settings (caption / alternate text / position etc) we force them to deal with size before applying the rest. In general I think that might be less convenient in the long run.
+
+I think the better approach (giving the user more leeway) is to alert the user that the parameter is wrong and won't be applied, save everything else, and allow the user to go back in and deal with the size widget specifically if they want to (or decide they don't want to deal with numerical values and resize with the mouse)
+
+I think that while it's less like ""others"" are doing, this might give the user more leeway when fixing and working on stuff. Instead of forcing the user to deal with a problem they might just want to undo, we let the user save everything else and choose if they want to go back to retrying the size specifically.",1391106128,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","> I am leaning towards #1, but we should discuss and see if we want to apply
+> #2.
+Wont #2 be more obvious ?",1391105362,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+"VisualEditor: Make it clear that invalid settings in the media dialog won't be set when ""apply changes"" button is clicks","This is actually intended behavior, but one that's not clearly explained; if the size parameters are invalid, the media edit dialog will apply all other changes except for size (so to allow other changes like image type, alternate text, etc)
+
+There are two ways to solve this bug imho:
+
+1. Adjust the message to ""Size values are invalid and will not be applied.""
+
+2. Make the 'apply' button inactive if size is invalid, forcing the user to find valid parameters or cancel -- but this will also mean that if other changes were made in the dialog, and the user doesn't know or want to change the size after seeing it is invalid (or wants to revert to the previous dimensions) we force them to cancel *all* changes and redo them again.
+
+I am leaning towards #1, but we should discuss and see if we want to apply #2.",1391104335,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-mtoupxdcw637uabefm23,task_subcomment,NA
+VisualEditor: Removing or breaking HTML tags (</small> and </code> tags vanish),"Ex. #1, https://fr.wikipedia.org/w/index.php?title=%C3%89conomie_de_la_France&diff=100357906&oldid=100354236 , the </small> tag vanishes (the user said he fixed the spaces and removed a link);
+ex. #2, https://fr.wikipedia.org/w/index.php?title=Utilisateur:NemesisIII/Brouillon&diff=100052444&oldid=99902909 , the </code> tag misses the less-than sign (the user had just added a link);
+ex. #3, https://fr.wikipedia.org/w/index.php?title=Utilisateur:NemesisIII/Brouillon&diff=99902829&oldid=99228289 the same thing happens (the user just deleted a template).
+Some curly brackets went missing as well.",1391013480,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fl6ckzrwls3bv7wziv27,task_description,resolved
+VisualEditor: Removing or breaking HTML tags (</small> and </code> tags vanish),I think this has been long-since fixed.,1437586955,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fl6ckzrwls3bv7wziv27,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"**Author:** `jhall`
+
+**Description:**
+Follow-up to a pairing session between Jeff and Željko on 1/29/2013.  In order to make headless browser testing available in as many WMF repositories as possible, we should add headless support[1] to the env.rb and hooks.rb setup in the mediawiki-selenium Rubygem[2].
+
+
+[1] http://watirwebdriver.com/headless/
+[2] https://git.wikimedia.org/tree/mediawiki%2Fselenium/ef67a1f40db97a7e0b456fcc3fbf20c6a8ec4e81/lib%2Fmediawiki%2Fselenium
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1391012400,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_description,resolved
+Add support for running headless browser tests to mediawiki-selenium Rubygem,But then he introduced the same thing in https://gerrit.wikimedia.org/r/#/c/110606 :),1391439349,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,Zeljko are you sure it is fixed ? Jeff reverted https://gerrit.wikimedia.org/r/110390,1391438764,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110390 merged by jenkins-bot:
+Make it possible to run VisualEditor tests in headless mode
+
+https://gerrit.wikimedia.org/r/110390",1391106871,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110390 had a related patch set uploaded by Zfilipin:
+Make it possible to run VisualEditor tests in headless mode
+
+https://gerrit.wikimedia.org/r/110390",1391099566,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110205 merged by jenkins-bot:
+Run browsers headlessly if HEADLESS environment variable is set to true
+
+https://gerrit.wikimedia.org/r/110205",1391094013,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"at one point CirrusSearch had this hook.  It's in the README, but I don't see the hook itself any more.",1391092901,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"I still have to test this with repositories that have at_exit hook. Looks like only VisualEditor has the hook, and it should probably be moved to the gem.",1391078414,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110335 abandoned by Zfilipin:
+WIP run browsers headlessly if HEADLESS environment variable is set to true
+
+https://gerrit.wikimedia.org/r/110335",1391076449,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110335 had a related patch set uploaded by Zfilipin:
+WIP run browsers headlessly if HEADLESS environment variable is set to true
+
+https://gerrit.wikimedia.org/r/110335",1391074845,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"We had some browser tests running on integration-selenium-driver.pmtpa.wmflabs which is an Ubuntu Precise instance. xvfb package is 2:1.11.4-0ubuntu10.14 
+
+There is apparently no package for ruby gems headless but it is going to be a dependency of mediawiki-selenium apparently ( https://gerrit.wikimedia.org/r/#/c/110205/3/mediawiki-selenium.gemspec,unified )",1391072803,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"Change 110205 had a related patch set uploaded by Zfilipin:
+WIP run browsers headlessly if HEADLESS environment variable is set to true
+
+https://gerrit.wikimedia.org/r/110205",1391026423,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+Add support for running headless browser tests to mediawiki-selenium Rubygem,"**jhall** wrote:
+
+Should note that in order to run headless browser tests, the test environment(s) needs to have two additional components installed:
+
+a) Headless Rubygem[1]
+b) Xvfb binary for your OS[2]
+
+[1] http://rubygems.org/gems/headless
+[2] http://en.wikipedia.org/wiki/Xvfb",1391012831,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atlm4jbmrywbsofx5zts,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,"Steps to reproduce:
+
+1.Open a page with VE
+2.Select a reference note or a text and open the gallery inspector or a Link inspector
+3.Close the inspector and go to the next line
+4.Again go to Insert>Gallery or Open the link inspector
+
+Observed Result:
+The inspector opens up with an animation from left to right
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66552",1390861440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cgjlomsf2qva26bhkh5o,task_description,resolved
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,Fixed in gerrit 139550.,1405375924,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,"This also happens when working with a list of links.
+
+1. Have a page with a list containing a list item with a link.
+2. Put cursor at end of list item (thus triggering the context menu).
+3. Press return (creating a new list item)
+4. Insert link.
+
+The link inspector animates in an odd way from the left of the screen.
+
+Can also be seen at the beginning of this (otherwise unrelated) recording for another bug. http://cl.ly/3s460Q442L3S",1403712295,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,This is still happening,1402690833,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,This looks like it's now fixed.,1402553325,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF
+OS: MAC OS X 10. 8. 5",1390861673,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-cgjlomsf2qva26bhkh5o,task_subcomment,NA
+VisualEditor: Diff styling in save dialog is broken,"Screenshot of the bug
+
+The diff in the save dialog isn't being styled correctly, which causes highlighted text to overlap with text above it. Timo tells me that this is due to a missing line-height style.
+
+This is exacerbated by bug 60494. which causes the save dialog to be narrower than it should be, which means lines wrap more often and highlighted text more frequently has text directly above it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13394}",1390859040,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tgchpzb2re5dhfc6dype,task_description,resolved
+VisualEditor: Diff styling in save dialog is broken,*** Bug 57300 has been marked as a duplicate of this bug. ***,1414810803,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tgchpzb2re5dhfc6dype,task_subcomment,NA
+VisualEditor: Diff styling in save dialog is broken,"This has been fixed, AFAICT.",1404168811,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tgchpzb2re5dhfc6dype,task_subcomment,NA
+VisualEditor: Diff styling in save dialog is broken,"So I think we just need to apply line-height: 1.6px to the body of the frame like MW core does for #bodyContent, .mw-body-content (but I don't think we should use those here as they apply some other changes which don't look right e.g. font-size: 0.875em)",1400029729,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tgchpzb2re5dhfc6dype,task_subcomment,NA
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.","When adding a special character via the new tool,
+this will not retain styles applied to what was being typed; that is,
+it will not appear for example in bold or italics.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1390841520,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-nlvlcsu6onawdloowc5x,task_description,resolved
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.","Change 157703 merged by jenkins-bot:
+Annotate inserted special characters
+
+https://gerrit.wikimedia.org/r/157703",1409596262,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nlvlcsu6onawdloowc5x,task_subcomment,NA
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.","Change 157703 had a related patch set uploaded by Jforrester:
+Annotate inserted special characters
+
+https://gerrit.wikimedia.org/r/157703",1409596100,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nlvlcsu6onawdloowc5x,task_subcomment,NA
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.",*** Bug 70265 has been marked as a duplicate of this bug. ***,1409596086,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nlvlcsu6onawdloowc5x,task_subcomment,NA
+"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.",*** Bug 65497 has been marked as a duplicate of this bug. ***,1400546427,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nlvlcsu6onawdloowc5x,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","Screenshot attached
+
+Steps to reproduce:
+
+
+1.Open a page with VE 
+2.Go to Insert>Transclusion
+3.Search for the template Cite Web
+4.Observe that the required parameters are now marked with * symbol
+5.Delete the required parameters
+
+Observed Result:
+
+The required parameters gets deleted
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50747
+
+**Attached**: {F13028}",1390435920,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_description,resolved
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData",Verified the fix in production,1409864356,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData",This kind of relationship between parameters was requested on bug 50407.,1409777327,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","(In reply to Helder from comment #8)
+> (In reply to James Forrester from comment #6)
+> > (In reply to Ricordisamoa from comment #5)
+> > > or a set of fields may be mutually exclusive (and yet one of them would
+> > > be required).
+> > 
+> > That doesn't make sense. ""Required"" means ""the template will die horribly if
+> > you don't include this"". It is *not* a ""we'd like you to fill this in"" –
+> > that's what ""suggested"" is for. Most templates will have no 'required'
+> > fields.
+> 
+> It seems perfectly valid for a template to require that ""either A or B be
+> provided"" and the user should be able to delete one of them if it is not
+> needed.
+
+This feels like a pretty edge case (and suggests that we should consider whether the template should be re-written to be less anti-human); maybe file a TemplateData bug to ask for a way to express this relationship?",1409771964,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","(In reply to Ricordisamoa from comment #5)
+> ...a set of fields
+> may be mutually exclusive (and yet one of them would be required).
+
+(In reply to James Forrester from comment #6)
+> > or a set of fields may be mutually exclusive (and yet one of them would
+> > be required).
+> 
+> That doesn't make sense. ""Required"" means ""the template will die horribly if
+> you don't include this"". It is *not* a ""we'd like you to fill this in"" –
+> that's what ""suggested"" is for. Most templates will have no 'required'
+> fields.
+
+It seems perfectly valid for a template to require that ""either A or B be provided"" and the user should be able to delete one of them if it is not needed.",1409711953,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","(In reply to James Forrester from comment #6)
+> The wikitext editor lets you do lots of things that are stupid.
+
+I do 'stupid' things all the time.
+Now I understand that VE will always be a toy for newbies, and never a valid replacement for the wikitext editor.",1409701206,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","(In reply to Ricordisamoa from comment #5)
+> VisualEditor should only make edits easier,
+
+I agree.
+
+> not restrict the users' capabilities.
+
+I think this is a false dichotomy.
+
+> As long as the wikitext editor allows removing required fields from
+> templates (and it should, indeed), VE should too.
+
+The wikitext editor lets you do lots of things that are stupid. VisualEditor's job is to make it easy to make good content, not easy to make broken pages. :-)
+
+> Sometimes the TemplateData information may be incorrect, 
+
+Then the TemplateData should be fixed.
+
+> or a set of fields may be mutually exclusive (and yet one of them would
+> be required).
+
+That doesn't make sense. ""Required"" means ""the template will die horribly if you don't include this"". It is *not* a ""we'd like you to fill this in"" – that's what ""suggested"" is for. Most templates will have no 'required' fields.
+
+> Sometimes a user may want to remove a wrong value, and a template may
+> show a warning for missing arguments (always better than wrong data).
+
+If the template outputs an error, that's probably a required parameter.
+
+> Instead, a warning should be shown when a required parameter is going to be
+> removed.
+
+I disagree, for the reasons above.",1409696656,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","VisualEditor should only make edits easier, not restrict the users' capabilities.
+As long as the wikitext editor allows removing required fields from templates (and it should, indeed), VE should too.
+Sometimes the TemplateData information may be incorrect, or a set of fields may be mutually exclusive (and yet one of them would be required). Sometimes a user may want to remove a wrong value, and a template may show a warning for missing arguments (always better than wrong data).
+Instead, a warning should be shown when a required parameter is going to be removed.",1409616727,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData",Verified the fix in test2,1409260648,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData",Verified the fix in Betalabs,1409166948,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","Change 154133 merged by jenkins-bot:
+Remove delete button from required parameters in template dialog
+
+https://gerrit.wikimedia.org/r/154133",1409133882,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+"VisualEditor: Stop users from deleting parameters in the template dialog if they're marked as ""required"" in TemplateData","Change 154133 had a related patch set uploaded by Alex Monk:
+Don't add delete button to required parameters in template dialog
+
+https://gerrit.wikimedia.org/r/154133",1408048592,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wicgwgtwpynij2ce4n4w,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"**Author:** `jhall`
+
+**Description:**
+The time has come to create additional VisualEditor browser tests for accessing VE via the Mobile interface.
+
+James F had great feedback on which repo (MobilefrontEnd vs. VisualEditor) these tests belong in:
+
+""​One way of looking at it is on the blocking model. If (when!) these tests were to block merge, which repo's changes should they be triggered by? In this case, I think there's a case for some basic browser tests for VE-on-Mobile to be in VisualEditor (specifically, in the MediaWiki VisualEditor repo) with the major tests be in MobileFrontend.""
+
+An example URL for accessing VE via Mobile UI is: [1]
+
+
+[1] http://en.m.wikipedia.beta.wmflabs.org/wiki/0.04730373828804457?mobileaction=alpha#editor/0
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1390322220,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_description,open
+VisualEditor: Create browser tests for using VE via Mobile UI,In the Triage meeting we felt that this wasn't a clear enough ask for Q4.,1428521913,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"So.. MobileFrontend has some basic ones [1]. I wonder if we should have a dedicated extension for MobileFrontendVETests that depends on MobileFrontend and VisualEditor? It seems silly having two (might even be worth breaking out MobileFrontendVE into its own extension?)
+
+[1] e.g. https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/440/testReport/(root)/VisualEditor%20Mobile/I_can_edit_a_page_using_VisualEditor/",1420843913,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,">>! In T62290#967236, @Cmcmahon wrote:
+> I'll take this on. Having refactored both MF and VE at the end of 2014, both repos are in good shape to support new feature coverage.
+
+Awesome. :-)",1420843497,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"I'll take this on. Having refactored both MF and VE at the end of 2014, both repos are in good shape to support new feature coverage.",1420843401,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"Change 108987 abandoned by Jforrester:
+[Browser test] WIP New test(s) for editing with VisualEditor via mobile user interface.
+
+Reason:
+Not currently being worked on AFAICT.
+
+https://gerrit.wikimedia.org/r/108987",1396279296,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"**jhall** wrote:
+
+Setting status back to ASSIGNED since Gerrit is a little over-eager to mark even WIP patch sets as being ready for review!",1390429368,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Create browser tests for using VE via Mobile UI,"Change 108987 had a related patch set uploaded by Jhall:
+[Browser test] WIP New test(s) for editing with VisualEditor via mobile user interface.
+
+https://gerrit.wikimedia.org/r/108987",1390429176,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6fwnwpvm5g7pybmx2eaw,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Daniel on Mediawiki.org says they use strikethrough a lot and would like a shortcut for it.
+",1390231620,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_description,resolved
+VisualEditor: Add a shortcut for strikethrough (?which?),"Re-confirmed in production. It's availabe in the formatting menu, and the indicated shortcut works as expected (Note: on macOS, you may have to use fn+shift+cmd+5 instead of shift+cmd+5 given the latter is by default used by the system's screengrab utility).
+{F31513593}",1579113752,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),I'm not currently working on this.,1579112937,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Google Docs uses Cmd+Shift+X on OSX (as opposed to +5): https://support.google.com/docs/answer/179738?co=GENIE.Platform%3DDesktop&hl=en
+
+~~Happy to switch to this...~~
+
+Unfortunately VE uses Cmd+Shift+X for ""Change directionality""...",1556472660,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Google Docs uses Cmd+Shift+X on OSX (as opposed to +5): https://support.google.com/docs/answer/179738?co=GENIE.Platform%3DDesktop&hl=en
+
+Happy to switch to this...",1556472553,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"@Jdforrester-WMF Since macOS Mojave, Shift-Command-5 is now used for an additional screenshot option, which conflicts with strikethrough. Is it possible to reconfigure? https://support.apple.com/en-us/HT201236",1543241693,PHID-USER-ep6ujeg6mjkhz4d7yx25,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),Verified the fix in production,1411681786,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),Verified the fix in Betalabs and test2,1411150108,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),Re-fixed.,1411088342,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"We need to change the shortcut key for code annotation on mac from ""cmd+shift+3"".Because,its a shortcut to take screenshot so it does not work there.",1411064760,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Change 160174 merged by jenkins-bot:
+Add keyboard shortcuts for strikethrough and code annotations
+
+https://gerrit.wikimedia.org/r/160174",1410823315,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Change 160174 had a related patch set uploaded by Jforrester:
+Add keyboard shortcuts for strikethrough and code annotations
+
+https://gerrit.wikimedia.org/r/160174",1410570238,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"I added your comment to Mediawiki.org. 
+I think I noticed that the numbers 8 and 9 are still available?
+Or at least this is what I read in the new keyboard shortcuts list.
+(Which, BTW, is not available for me by its shortcut, since / is located on the numeric pad or above number 7, thus won't work).",1390478424,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),"Sure. But what short-cut? Remember that it needs to:
+
+* not clash with
+** any existing VE shortcut,
+** any expected VE shortcut for future uses (e.g. edit image/template/table), or
+** any OS or browser shortcut (e.g. Ctrl+C for copy, Cmd+Q for quit);
+* be available on most users' keyboards;
+* be type-able; and
+* ideally be the ""standard"" shortcut.
+
+This doesn't leave many options. :-(",1390415278,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Add a shortcut for strikethrough (?which?),*he uses,1390231974,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-b4is7j2fhz7cdny4tfr2,task_subcomment,NA
+VisualEditor: Provide a language inspector to handle <div lang='xx' dir='yyy'> blocks and similar,"[Split from bug 47759 to cover block level items.]
+
+Bug 47759 covers a language inspector to handle <span lang='xx' dir='yyy'>s, but for <div lang='xx' dir='yyy'> blocks and similar (like annotations on <ul>s or <li>s) we'll need a totally different editing concept.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1390006800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-e27vu3d74mxw2xwf3ahr,task_description,open
+VisualEditor: Provide a language inspector to handle <div lang='xx' dir='yyy'> blocks and similar,*** Bug 69892 has been marked as a duplicate of this bug. ***,1408734760,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-e27vu3d74mxw2xwf3ahr,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Opt-in state, per community member requesting.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://pt.wikibooks.org/wiki/Tópico:Wikilivros_Discussão:Portal_comunitário/Testes_com_o_Editor_Visual_no_Wikilivros",1389996660,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_description,resolved
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Thank you James, it's working great now =)",1391716631,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"(In reply to comment #20)
+> Hi,
+> 
+> Well, something got through because, though it's still not working, it no
+> longer pops up that error message, just quietly hangs while ""loading"" the VE.
+> 
+> Is this a different issue? Or just consequence of stuff that went wrong on
+> monday? I mean, will it get fixed with the next deployment?
+
+Sorry for the slow response - the issue has now (finally) been fixed. See https://pt.wikiversity.org/w/index.php?namespace=&tagfilter=visualeditor&title=Especial%3AMudan%C3%A7as+recentes for a list of all edits with VisualEditor on Portuguese Wikiversity (just my test one so far).",1391711278,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Hi,
+
+Well, something got through because, though it's still not working, it no longer pops up that error message, just quietly hangs while ""loading"" the VE.
+
+Is this a different issue? Or just consequence of stuff that went wrong on monday? I mean, will it get fixed with the next deployment?",1391608662,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,I'm afraid that the deployment went slightly wrong and this fix did not get merged. Sorry. :-(,1391467046,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Hi, thanks, that's useful information. The workshop is not about wikis (it's a permaculture course promoted by the city, that will use wikiversity for classes), and in fact starts at 21:30, so we can plan to start introducing wiki editing after 22:00 and get a better chance of meeting the fix =) Cheers!",1391450361,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"This is scheduled to happen in the hour-long block from 21:00 to 22:00 UTC today (see https://wikitech.wikimedia.org/wiki/Deployments#Week_of_February_3rd row three); it's quite a tricky operation this time around due to other changes, so unfortunately you shouldn't expect it to be available until later in that hour, sorry.",1391448826,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Thank you James,
+
+Any indication this might be shipped by 21:00 UTC today?
+
+[]s",1391444623,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"OK, the configuration change has been merged; this should now ship on Monday (Pacific time); sorry for the confusion and disruption. I'll get a more exact time when I know.",1391212862,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 110660 merged by jenkins-bot:
+Add Wikiversity to site list in ParsoidConfig
+
+https://gerrit.wikimedia.org/r/110660",1391212784,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 110660 had a related patch set uploaded by Jforrester:
+Add Wikiversity to site list in ParsoidConfig
+
+https://gerrit.wikimedia.org/r/110660",1391211712,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"(In reply to comment #11)
+> Ni!
+> 
+> Any idea of whether/when will this get fixed for Wikiversity?
+> 
+> I am giving a workshop Monday evening and I was really really expecting to be
+> able to show people the Visual Editor working on Wikiversity.
+> 
+> Cheers
+> .~´
+
+
+Sorry, this is because https://gerrit.wikimedia.org/r/#/c/108158/ wasn't merged and deployed, so Parsoid has no idea what Wikiversity is. :-(
+
+Working on getting it fixed now.",1391210395,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Ni!
+
+Any idea of whether/when will this get fixed for Wikiversity?
+
+I am giving a workshop Monday evening and I was really really expecting to be able to show people the Visual Editor working on Wikiversity.
+
+Cheers
+.~´",1391137660,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"I confirm it is working on Portuguese Wikibooks[1] but not on Portuguese Wikiversity[2].
+
+[1] https://pt.wikibooks.org/wiki/Special:RecentChanges?tagfilter=visualeditor
+currently has 3 edits.
+[2] https://pt.wikiversity.org/wiki/Álgebra_linear?veaction=edit&uselang=en
+shows the message ""Error loading data from server: parsoidserver-http-bad-status: 404. Would you like to retry?""",1390989577,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Ni!
+
+It ain't working on pt.wikiversity.
+
+After activating VisualEditor, clicking ""Edit"" pops up a floaty with this error:
+
+""Erro ao carregar dados do servidor:  parsoidserver-http-bad-status: 404. Gostaria de tentar novamente?""
+
+I guess that freely translates to
+
+""Error loading data from server: parsoidserver-http-bad-status: 404. Would you like to try again?""
+
+Does seem to be working on pt.wikibooks though.",1390967668,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 108156 merged by Reedy:
+Enable VisualEditor on ptwikibooks, ptwikiversity for testing
+
+https://gerrit.wikimedia.org/r/108156",1390938311,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"(In reply to comment #6)
+> Community consensus for this is where?
+
+It's enabling a widely-deployed code path as an opt-in beta feature for testing…",1390005711,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,Community consensus for this is where?,1390003943,PHID-USER-hwuumsjqciw7ji5qhpc7,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 108158 had a related patch set uploaded by Jforrester:
+Add ptwikiversity to interwiki map
+
+https://gerrit.wikimedia.org/r/108158",1389998250,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Yes, this is OK. Thank you!",1389997301,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"^^^
+
+Done by that config change; we should be able to get that pushed out w/c 27 January (next week we're in lock-down because people are busy at a conference).
+
+Will this be OK? If there's a major issue, we may need to switch it back off, though this hasn't been a problem so far.",1389997117,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Change 108156 had a related patch set uploaded by Jforrester:
+Enable VisualEditor on ptwikibooks, ptwikiversity for testing
+
+https://gerrit.wikimedia.org/r/108156",1389996953,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+Enable VisualEditor on ptwikiversity and ptwikibooks for testing,"Ni!
+
+Community member here.
+
+.~´",1389996844,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-3lzxk25gwjfyhhw6s2ps,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"screenshot
+
+Steps to reproduce:
+
+1.Open VE for a page
+2.Now resize the window down
+2.Go to Settings>Keyboard shortcuts
+
+Observed Result:
+There is no scroll bar in this window therefore cannot see the last line of it as it is getting cut off.
+
+See the screenshot
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13257}",1389992460,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_description,resolved
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Verified the fix in production: https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1394827175,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Verified the fix in test2 environment,1394153262,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Verified the fix in Betalabs,1393959948,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Should now be fixed.,1393880384,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Change 116479 merged by jenkins-bot:
+Increase keyboard shortcut height hack to work in FF
+
+https://gerrit.wikimedia.org/r/116479",1393877733,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Change 116479 had a related patch set uploaded by Esanders:
+Increase keyboard shortcut height hack to work in FF
+
+https://gerrit.wikimedia.org/r/116479",1393852600,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,Both the scroll bars:Horizontal and vertical remains active in the same time which seems like moving the whole page instead of scrolling in a specific direction,1392941342,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Change 109483 merged by jenkins-bot:
+Fix layout of keyboard shortcuts page
+
+https://gerrit.wikimedia.org/r/109483",1392853095,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Change 109483 had a related patch set uploaded by Esanders:
+Fix layout of keyboard shortcuts page
+
+https://gerrit.wikimedia.org/r/109483",1390677240,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window,"Created attachment 14334
+screenshot
+
+**Attached**: {F13260}",1389992554,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ep2xq5qhopjkqsqft6tl,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"Once we're happy with it. Currently feature-flagged off.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389930720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_description,resolved
+Deploy TemplateData's GUI editing tool to all wikis,"Change 157478 merged by jenkins-bot:
+Enable TemplateData GUI for all wikis; move config to CommonSettings.php
+
+https://gerrit.wikimedia.org/r/157478",1415297440,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,Scheduled for 6 November.,1412884407,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"Change 157478 had a related patch set uploaded by Jforrester:
+Enable TemplateData GUI for all wikis; move config to CommonSettings.php
+
+https://gerrit.wikimedia.org/r/157478",1409431787,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"(In reply to James Forrester from comment #4)
+> (In reply to Lokal_Profil from comment #3)
+> > What is the current status on deployment to other wikis?
+> 
+> The GUI is deployed on MediaWiki.org but has had little use; we're working
+> on improvements to it, and we'd be interested in feedback. It might be a
+> little premature to deploy it to other wikis, but if you've tried it and
+> think your community would like it, please do ask.
+
+Mainly asking since VisualEditor is now default on many wikis yet the knowledge on how to prepare the templates is sparse and the understanding of how the json works is even more so.
+
+Would an embedded solution (as on Commons) work better/feel more natural? I.e. a ""normal"" template for documenting the template which also produces TemplateData behind the scenes.",1400743392,PHID-USER-uu7wg6g3b37dcktbje3a,True,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"(In reply to Lokal_Profil from comment #3)
+> What is the current status on deployment to other wikis?
+
+The GUI is deployed on MediaWiki.org but has had little use; we're working on improvements to it, and we'd be interested in feedback. It might be a little premature to deploy it to other wikis, but if you've tried it and think your community would like it, please do ask.",1400718826,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,What is the current status on deployment to other wikis?,1397294591,PHID-USER-uu7wg6g3b37dcktbje3a,True,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,*** Bug 63815 has been marked as a duplicate of this bug. ***,1397293229,PHID-USER-3uecblbxq24ycewm2cog,True,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Deploy TemplateData's GUI editing tool to all wikis,"From bug 51734 comment 14:
+| 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
+
+First I think we should deploy it to MediaWiki.org to let people try it out.",1391795259,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nvbt37dfbyf2ilz2wcwc,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"The OOjs UI library has a useful demos directory, which shows off each of the widgets available. Similarly, VisualEditor also has a demos directory, and I imagine other projects do (or would if it became an established pattern.
+
+It would be really great if we could somehow expose these alongside their projects' documentation, so we can point people to a living thing rather than telling them to checkout the repo and play. Something like…
+
+https://doc.wikimedia.org/visualeditor/master/
+https://doc.wikimedia.org/visualeditor/master/demo/
+
+https://doc.wikimedia.org/visualeditor/v0.1.0/
+https://doc.wikimedia.org/visualeditor/v0.1.0/demo/
+
+https://doc.wikimedia.org/oojs-ui/master/
+https://doc.wikimedia.org/oojs-ui/master/demos/
+
+https://doc.wikimedia.org/oojs-ui/v1.0.6/
+https://doc.wikimedia.org/oojs-ui/v1.0.6/demos/
+",1389900720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_description,resolved
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#1165994, @Krinkle wrote:
+> The main this this is blocked on now is:
+> * Setting up a redirect.
+
+Redirect for what?
+
+> * Upstream OOjs UI and VisualEditor need to have their demo-directory be standalone (like docs). So must not reference `../` but instead build and copy relevant files.
+
+For OOUI, {e538462cbd8f7dcf2423a8ee49b8ebd329f10c84} introduces a `npm demos` command to build the standalone demos directory.",1435891858,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,Timo worked on generic templates to publish /cover/ directories. It can be reused now to publish the /demos/ directories.,1428411882,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#1162486, @hashar wrote:
+> We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+The main blocker for this used to be the ability to run a build script. That is resolved now that we migrated jsduck to labs. The OOjs UI publication job for documentation already makes use of `npm-install` ([example](https://github.com/wikimedia/integration-config/blob/96fa3fd720d13c2f52454ab283382fd0cd38802a/jjb/misc.yaml#L28-L36)).
+
+The main this this is blocked on now is:
+* Setting up a redirect.
+* Upstream OOjs UI and VisualEditor need to have their demo-directory be standalone (like docs). So must not reference `../` but instead build and copy relevant files.
+
+After that, it's just a simple change to update publication job to call push-doc a second time (once for `docs/` to `visualeditor/:version` and a second time for `demos/` to `visualeditor/:version/demo`
+
+> That is similar to {T87490}.
+
+That one is primarily blocked on {T93558}. Trivial otherwise.",1427785748,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#1162486, @hashar wrote:
+> We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+The main blocker for this used to be the ability to run a build script. That is resolved now that we migrated jsduck to labs. The OOjs UI publication job for documentation already makes use of `npm-install` ([example](https://github.com/wikimedia/integration-config/blob/96fa3fd720d13c2f52454ab283382fd0cd38802a/jjb/misc.yaml#L28-L36)).
+
+The main this this is blocked on now is:
+* Setting up a redirect.
+* Upstream OOjs UI and VisualEditor need to have their demo-directory be standalone (like docs). So must not reference `../` but instead build and copy relevant files.
+ 
+ After that, it's just a simple change to update publication job to call push-doc a second time (once for `docs/` to `visualeditor/:version` and a second time for `demos/` to `visualeditor/:version/demo`
+
+> That is similar to {T87490}.
+
+That one is primarily blocked on {T93558}. Trivial otherwise.",1427785735,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#1162486, @hashar wrote:
+> We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+The main blocker for this used to be the ability to run a build script. That is resolved now that we migrated jsduck to labs. The OOjs UI publication job for documentation already makes use of `npm-install` ([example](https://github.com/wikimedia/integration-config/blob/96fa3fd720d13c2f52454ab283382fd0cd38802a/jjb/misc.yaml#L28-L36)).
+
+The main this this is blocked on now is:
+* Setting up a redirect.
+* Upstream OOjs UI and VisualEditor need to have their demo-directory be standalone (like docs). So must not reference `../` but instead build and copy relevant files.
+ 
+ After that, it's just a simple change to update publication job to call push-doc a second time (once for `docs/` to `visualeditor/:version` and a second time for `/demos` to `visualeditor/:version/demo`
+
+> That is similar to {T87490}.
+
+That one is primarily blocked on {T93558}. Trivial otherwise.",1427785693,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"From https://www.mediawiki.org/wiki/Continuous_integration/meetings/2015-03-30/minutes
+
+We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+I have not much time available to handle this though. So it is going to sit in the backlog for now :/
+
+That is similar to {T87490}.",1427724674,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"From https://www.mediawiki.org/wiki/Continuous_integration/meetings/2015-03-30/minutes
+
+We should be able to craft a job that triggers doc-publish-sync job with source /demos/ and dest /visualeditor/<version>/demos/ .  The job would be triggered on postmerge.
+
+I have not much time available to handle this though. So it is going to sit in the backlog for now :/",1427724642,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#962939, @hashar wrote:
+> Can you ship the demo directly in the doc ? Ie: https://doc.wikimedia.org/visualeditor/v0.1.0/doc/demos/ ? The demos could be linked from the documentation main page.
+
+No, they don't nest well and are independent web entry points. Keep them as `doc/` and `demos/`. The `doc/` dir is auto-generated and managed by jsduck. The `demo/` on the other hand is in git and should work after a plain git clone and running install/build.",1420733528,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,">>! In T62143#962939, @hashar wrote:
+> Can you ship the demo directly in the doc ? Ie: https://doc.wikimedia.org/visualeditor/v0.1.0/doc/demos/ ? The demos could be linked from the documentation main page.
+
+No, they don't nest well and are independent web entry points. Keep them as `doc/` and `demos/`. The `doc/` dir is auto-generated completely. The `demo/` on the other hand is in git and should work after a plain git clone and running install/build.",1420733509,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,Can you ship the demo directly in the doc ? Ie: https://doc.wikimedia.org/visualeditor/v0.1.0/doc/demos/ ? The demos could be linked from the documentation main page.,1420729268,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,Can you ship the demo directly in the doc ? Ie: https://doc.wikimedia.org/visualeditor/v0.1.0/doc/demos/ ? They could be linked from the main page.,1420729253,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"Once we have dev.wikimedia.org up and running, we should migrate documentation to there, which will help remove the awkward terminology overlap/ambiguity between ""documentation"" and ""demo"". We'd e.g. have:
+
+* dev.wikimedia.org/visualeditor/documentation/
+* dev.wikimedia.org/visualeditor/demo/
+
+But for the time being on doc.wikimedia.org, we can just do the same and don't mind the fact that there is already ""doc"" in the url somewhere.
+
+So there's nothing blocking us from having additional directories up on doc.wikimedia.org. The blocking aspects of this are specific to each project.
+
+>>! In T62143#666023, @Spage wrote:
+> This is similar to bug 58620.  Since the OOjs UI demos require nodejs/npm setup similar to building the KSS documentation, fixing this will require similar steps as hashar outlined in comment 1 there.
+
+The blocker for OOjs UI is being able to run Grunt and arbitrary npm dependencies on the server. Which is blocked on migrating that job from gallium to labs slaves.
+
+For VisualEditor, the main blocker was directory management (it doesn't require a build step).",1420733430,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"Once we have dev.wikimedia.org up and running, we should migrate documentation to there, which will help remove the awkward terminology overlap/ambiguity between ""documentation"" and ""demo"". We'd e.g. have:
+
+* dev.wikimedia.org/visualeditor/documentation/
+* dev.wikimedia.org/visualeditor/demo/
+
+But for the time being on doc.wikimedia.org, we can just do the same and don't mind the fact that there is already ""doc"" in the url somewhere.",1420729145,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"This is similar to bug 58620.  Since the OOjs UI demos require nodejs/npm setup similar to building the KSS documentation, fixing this will require similar steps as hashar outlined in comment 1 there.",1390635527,PHID-USER-gbl4hfak3cfurt3c7skd,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"(In reply to comment #1)
+> Do the demo require a server side backend or are they 100% executing in the
+> browser?  If we need to serve content, that would need to be done on another
+> server.  Else, it is ""just"" about enhancing the doc jobs to publish the demo
+> to
+> the document root.
+
+Fully stand-alone client-side JS only, providing static files. Theoretically they could just be linked off beta's bits – e.g. http://bits.beta.wmflabs.org/static-master/extensions/VisualEditor/lib/ve/demos/ve/eventLogger.html – but this is ugly (and doesn't work for OOjs UI because it's only deployed in compiled form without demos).",1389930597,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org,"Do the demo require a server side backend or are they 100% executing in the browser?  If we need to serve content, that would need to be done on another server.  Else, it is ""just"" about enhancing the doc jobs to publish the demo to the document root.",1389903054,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-j4fy326x5cwxfcmowqlo,task_subcomment,NA
+VisualEditor: Math inspector live preview double-escapes angle brackets,"1. Create a new math node (Insert -> Formula)
+2. Type L' = \{\<x, \underbrace{1111\dots1111}_{s(|x|)}0\> | x \in L\} into the input box
+3. Observe &lt; and &gt; in the preview :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1389829140,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qqtn53sr5xr6josxp5cm,task_description,resolved
+VisualEditor: Math inspector live preview double-escapes angle brackets,"
+
+*** This bug has been marked as a duplicate of bug 57429 ***",1404431099,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qqtn53sr5xr6josxp5cm,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Intention:
+Delete a template.
+
+Steps to Reproduce:
+1. Open an article containing a template.
+2. Select the template.
+3. Try to press the delete key on the now-non-existent keyboard.
+
+Actual Results:  
+The keyboard closes, so you can't delete them.
+
+
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67390",1389825480,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_description,resolved
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 230592 merged by jenkins-bot:
+MobileContext: Provide a delete button for nodes' context
+
+[[https://gerrit.wikimedia.org/r/230592]]",1439307483,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Mobile styling:
+{F1273774}",1439290242,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 163662 abandoned by Esanders:
+[WIP] Add a ""Remove"" context button to all Focusable nodes
+
+Reason:
+Context items have moved on a fair bit. See I41109537d for latest attempt.
+
+[[https://gerrit.wikimedia.org/r/163662]]",1439244361,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 230592 had a related patch set uploaded (by Esanders):
+[WIP] Delete button for node context items
+
+[[https://gerrit.wikimedia.org/r/230592]]
+",1439233247,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","I have a patch which adds a delete action. The only question is should we hide it on desktop, because it looks okay and could be useful:
+
+{F1182099}
+",1439233080,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 163662 had a related patch set uploaded (by Jforrester):
+[WIP] Add a ""Remove"" context button to all Focusable nodes
+
+[[https://gerrit.wikimedia.org/r/163662]]
+",1428510131,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","(In reply to Ed Sanders from comment #11)
+> Of course this behaves completely differently in iOS 8 (the keyboard stays
+> up). *sigh*
+
+Re-prioritising.",1412469153,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",Of course this behaves completely differently in iOS 8 (the keyboard stays up). *sigh*,1412437336,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Change 163662 had a related patch set uploaded by Jforrester:
+Add a ""Remove"" context button to all Focussable nodes
+
+https://gerrit.wikimedia.org/r/163662",1412020628,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","This seems to be because we programmatically move focus from the surface to the pasteTarget, and iOS Safari is very picky about when it allows a programmatic focus move to open the keyboard. Something like, it only works if you do it in direct response to a mouse/touch event. I tried a few solutions I found on the internet but I haven't gotten any of them to work yet.",1408469978,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",*** Bug 67257 has been marked as a duplicate of this bug. ***,1407064915,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","(In reply to Brion Vibber from comment #6)
+> I've noticed a few bugs coming through related to certain operations hiding
+> the keyboard and then that killing focus and causing selections and menus to
+> disappear. Is there a general problem where losing keyboard focus causes VE
+> to lose state?
+
+Quite possibly; escalating.",1404332970,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",I've noticed a few bugs coming through related to certain operations hiding the keyboard and then that killing focus and causing selections and menus to disappear. Is there a general problem where losing keyboard focus causes VE to lose state?,1404331255,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Yes, for all block items such as image, reference note, template ,math function: selecting it hides the keyboard.",1404168367,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",Can this be rechecked?,1404166204,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","Aaaah, OK. Updating summary to reflect that.",1389833609,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted","No, I mean the keyboard.  It's an iPad without an attached physical keyboard.  The keyboard is displayed on the screen, like the one shown in the picture at https://commons.wikimedia.org/wiki/File:Apple_iPad_Event03.jpg
+
+(Presumably the same problem happens on any mobile device.)",1389831224,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+"Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted",Did you mean the cursor instead of the keyboard? Surely VisualEditor didn't make your physical keyboard dissolve into a pool of molten plastic?,1389826148,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-qoe2ftyvquvdpbv4iapa,task_subcomment,NA
+VisualEditor: Namespace mixin properties,"Especially now that we have mixins adding properties with very generic names like this.min and this.max (ResizeableNode), we should look at namespacing them. Maybe an object to contain them all, like this.resizeableNode = { min: 1, max: 1000 }; ?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389822180,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xkdnjrereisoecj453z5,task_description,open
+Zuul: python git assert error assert len(fetch_info_lines) == len(fetch_head_info),"Spotted by EdSanders on https://gerrit.wikimedia.org/r/#/c/107036/
+
+
+2014-01-12 14:29:20,163 INFO zuul.IndependentPipelineManager: Change <Change 0x7f30084dcf10 107036,1> depends on changes []
+2014-01-12 14:29:20,165 DEBUG zuul.Repo: Resetting repository /srv/ssd/zuul/git/mediawiki/extensions/VisualEditor
+2014-01-12 14:29:20,165 DEBUG zuul.Repo: Updating repository /srv/ssd/zuul/git/mediawiki/extensions/VisualEditor
+2014-01-12 14:29:24,064 DEBUG zuul.Repo: Checking out master
+2014-01-12 14:29:26,280 DEBUG zuul.Merger: Unable to merge <Change 0x7f30084dcf10 107036,1>
+Traceback (most recent call last):
+  File ""/usr/local/lib/python2.7/dist-packages/zuul/merger.py"", line 206, in _mergeChange
+    repo.merge(change.refspec, 'resolve')
+  File ""/usr/local/lib/python2.7/dist-packages/zuul/merger.py"", line 97, in merge
+    self.fetch(ref)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul/merger.py"", line 111, in fetch
+    origin.fetch(ref)
+  File ""/usr/lib/python2.7/dist-packages/git/remote.py"", line 593, in fetch
+    return self._get_fetch_info_from_stderr(proc, progress or RemoteProgress())
+  File ""/usr/lib/python2.7/dist-packages/git/remote.py"", line 539, in _get_fetch_info_from_stderr
+    assert len(fetch_info_lines) == len(fetch_head_info), ""len(%s) != len(%s)"" % (fetch_head_info, fetch_info_lines)
+AssertionError: len([""3d35f5b84a26171535e869fed4a1c73dbeaeec69\t\t'refs/changes/36/107036/1' of ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor\n""]) != len(['Total 9 (delta 7), reused 9 (delta 7)', ' * branch            refs/changes/36/107036/1 -> FETCH_HEAD'])
+2014-01-12 14:29:26,318 INFO zuul.IndependentPipelineManager: Unable to merge change <Change 0x7f30084dcf10 107036,1>
+2014-01-12 14:29:26,319 DEBUG zuul.IndependentPipelineManager: Reporting change <Change 0x7f30084dcf10 107036,1>
+2014-01-12 14:29:26,319 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f30084dcf10 107036,1>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x25821d0>, {'verified': -1}>]
+2014-01-12 14:29:26,319 DEBUG zuul.reporter.gerrit.Reporter: Report change <Change 0x7f30084dcf10 107036,1>, params {'verified': -1}, message: Build failed.
+
+This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset.
+
+
+
+There is a few occurrences in the Zuul debug log: fgrep assert /var/log/zuul/debug*
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1389609900,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-cfrv36eokvo6qttirzvb,task_description,resolved
+Zuul: python git assert error assert len(fetch_info_lines) == len(fetch_head_info),"The Zuul Debian package embeds some python modules including `GitPython` which is now `>=0.3.3`.
+
+",1446722644,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-cfrv36eokvo6qttirzvb,task_subcomment,NA
+Zuul: python git assert error assert len(fetch_info_lines) == len(fetch_head_info),That is apparently solved in v3.2.  Now pending upgrade of Zuul.,1428919361,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-cfrv36eokvo6qttirzvb,task_subcomment,NA
+Zuul: python git assert error assert len(fetch_info_lines) == len(fetch_head_info),"Possible upstream bug: https://github.com/gitpython-developers/GitPython/issues/94
+
+Got to find a way to reliably reproduce the issue :(",1389610881,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-cfrv36eokvo6qttirzvb,task_subcomment,NA
+VisualEditor: Exception thrown placing cursor at end of document with no content offsets,"1. Create a document with just a block image [[File:Foo.jpg|thumb]] on one line
+2. Edit the document and try to place the cursor in the second slug (after the image)
+3. An exception is thrown (getNearestContentOffset(selection.end) returns -1 and this is fed into getAnnotationsFromOffset)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389539280,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2pul64ax3wl2rgoic6ap,task_description,resolved
+VisualEditor: Exception thrown placing cursor at end of document with no content offsets,verified the fix in test2,1389911469,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2pul64ax3wl2rgoic6ap,task_subcomment,NA
+VisualEditor: Exception thrown placing cursor at end of document with no content offsets,"Change 107134 merged by jenkins-bot:
+Check for valid offset when calculating insertion annotations
+
+https://gerrit.wikimedia.org/r/107134",1389641853,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2pul64ax3wl2rgoic6ap,task_subcomment,NA
+VisualEditor: Exception thrown placing cursor at end of document with no content offsets,"Change 107134 had a related patch set uploaded by Esanders:
+Check for valid offset when calculating insertion annotations
+
+https://gerrit.wikimedia.org/r/107134",1389616550,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2pul64ax3wl2rgoic6ap,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"In the read mode
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a reference to a text by going to Insert>Reference
+3.When the reference dialog box opens up insert a numbered list and then type the reference for example as: 1.reference
+4.Click on ""Insert Reference""
+5.Save the page
+
+Observed Result:
+In the read mode,the serials of the numbered list are appearing in wikitext with #.
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan7th
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12322}",1389122340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_description,resolved
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"The PHP parser requires a \n before every *, including the first one. So it should be:
+
+Hey!<ref>
+* foo
+* ...
+
+Unless you want to start messing with the PHP parser...",1392388249,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"(In reply to Ed Sanders from comment #5)
+> Todo: create a ticket for the Parsoid side if this bug (not inserting line
+> breaks before */#)
+
+Ed, what's the specific problem Parsoid's doing wrong?
+
+<p>Hey!<span class=""reference"" data-mw=""{&quot;name&quot;:&quot;ref&quot;,&quot;body&quot;:{&quot;html&quot;:&quot;&lt;ul &gt;&lt;li &gt; foo&lt;/li&gt;&lt;li &gt; bar&lt;/li&gt;&lt;li &gt; baz&lt;/li&gt;&lt;/ul&gt;&quot;},&quot;attrs&quot;:{}}"" id=""cite_ref-1-0"" rel=""dc:references"" typeof=""mw:Extension/ref""><a href=""#cite_note-1"">[1]</a></span></p>
+
+… goes neatly to …
+
+Hey!<ref>* foo
+* bar
+* baz</ref>
+
+With \n as needed.",1392320541,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,Todo: create a ticket for the Parsoid side if this bug (not inserting line breaks before */#),1391676490,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,https://gerrit.wikimedia.org/r/#/c/111507/,1391630644,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,One really shouldn't put lists inside a reference. References are supposed to be a single paragraph. I'll remove the tools for doing so which should reduce the impact of this.,1391630603,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"This issue is also occurring for bullet list thats is added inside Reference dialog bix, they appear as * in the Read mode",1389213301,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box,"Created attachment 14250
+In Edit mode
+
+**Attached**: {F12323}",1389122417,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6i3c2xat3qhxsq5ee23u,task_subcomment,NA
+VisualEditor:Special Character option remains selected even after closing the window,"screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select Insert>Special Character
+3.Close the special character window.
+4.Go to Insert option in the toolbar
+
+Observed Result:
+The Special Character option is still appearing selected even after closing the window
+
+See the screenshot attached.
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Jan7th?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12316}",1389120960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-46ixfpirqh7liqxoja7t,task_description,resolved
+VisualEditor:Special Character option remains selected even after closing the window,This issue got fixed with https://gerrit.wikimedia.org/r/#/c/107193/,1389900742,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-46ixfpirqh7liqxoja7t,task_subcomment,NA
+mediawiki/extensions.git is broken again (so VisualEditor isn't getting updated on betalabs),"Bug 49846 was this happening last time around. Possibly the same cause.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389084780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3recwohppy6wk6kediy2,task_description,resolved
+mediawiki/extensions.git is broken again (so VisualEditor isn't getting updated on betalabs),"Merging into 49846 then.
+
+*** This bug has been marked as a duplicate of bug 49846 ***",1389149751,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3recwohppy6wk6kediy2,task_subcomment,NA
+mediawiki/extensions.git is broken again (so VisualEditor isn't getting updated on betalabs),"Ok, so it's definitely bug 49846 coming back again.
+
+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)
+
+Which is wrong Wrong WRONG! There's a bug here, will need to report upstream.
+
+In the meantime: we can't have submodule subscriptions where there's a repo with the same base name. Gerrit gets confused.
+
+VisualEditor.git will have to be renamed or something if we expect mw/ext/VisualEditor to update properly.",1389115077,PHID-USER-oetk6bbl6omm354ejz3b,True,PHID-TASK-3recwohppy6wk6kediy2,task_subcomment,NA
+mediawiki/extensions.git is broken again (so VisualEditor isn't getting updated on betalabs),"Trying to update manually on deployment-bastion.pmtpa.wmflabs in /home/wikipedia/common/php-master/extensions
+
+Looking at VisualEditor:
+
+
+$ git submodule VisualEditor
+ 3e925e634398ab80711819ee4c10a29b89854588 VisualEditor (remotes/origin/wmf/1.23wmf9-1-g3e925e6)
+
+Although the HEAD of mediawiki/extensions.git checkout is up to date :(",1389085980,PHID-USER-orzyp3dswemhdgdznro5,True,PHID-TASK-3recwohppy6wk6kediy2,task_subcomment,NA
+VisualEditor: Add tooltips to drop-down menus,"Especially if the icon for a menu button is a mere symbol, add a tooltip to that button (i.e., the three-bars icon).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389017400,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ckbwvojthagfr3sxjhi7,task_description,resolved
+VisualEditor: Add tooltips to drop-down menus,"Change 108855 had a related patch set uploaded by Jforrester:
+Add tooltips to the drop-down menus explaining what they do
+
+https://gerrit.wikimedia.org/r/108855",1390348682,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ckbwvojthagfr3sxjhi7,task_subcomment,NA
+VisualEditor: Use multipart/form-data encoding when POSTing HTML,"Per Gabriel's report via email, when VE POSTs HTML, it uses multipart/x-www-urlencoded to encode the POST body, which results in a lot of URL-encoding of special characters (especially <>"") in the HTML. We should instead use multipart/form-data , which is more efficient for such large POST bodies with many special characters.
+
+TODO: Figure out how to tell the browser to use this encoding when sending an AJAX request.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388891640,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-buhdykqbpmicqrkqd7ao,task_description,resolved
+VisualEditor: Use multipart/form-data encoding when POSTing HTML,"Change 105486 merged by jenkins-bot:
+Add multipart/form-data emulation to ve.init.mw.Target#apiRequest
+
+https://gerrit.wikimedia.org/r/105486",1389824910,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-buhdykqbpmicqrkqd7ao,task_subcomment,NA
+VisualEditor: Use multipart/form-data encoding when POSTing HTML,"Change 105486 had a related patch set uploaded by Catrope:
+Add multipart/form-data emulation to ve.init.mw.Target#ajax
+
+https://gerrit.wikimedia.org/r/105486",1388901240,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-buhdykqbpmicqrkqd7ao,task_subcomment,NA
+"VisualEditor:  Can't add new paragraphs to the end of the page, if the last line is an empty section heading == <nowiki/> ==","Intention:
+Add a new paragraph at the bottom of a page that ended in == <nowiki/> == (not counting the category after the empty section heading).
+
+I was hoping that adding a new paragraph underneath the blank section heading would allow me to select, and therefore to remove, the blank section heading.
+
+
+Steps to Reproduce:
+1. Edit a page that ends in a == <nowiki/> ==, like https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox2&oldid=589158823
+
+2. Place the cursor in the empty section heading.
+
+3. Hit return.
+
+Actual Results:  
+Pressing return adds blank paragraphs *above* the empty section heading. 
+
+If you type anything into the section heading, then it starts behaving normally.
+
+Expected Results:  
+Doing the same thing for an empty (or non-empty) section heading anywhere else on the page adds new paragraphs *under* the empty section heading.  Pressing return in a section heading should produce the same behavior everywhere on the page.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388854920,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rmjvwpvg64vxchilw4se,task_description,resolved
+"VisualEditor:  Can't add new paragraphs to the end of the page, if the last line is an empty section heading == <nowiki/> ==","Change 160215 merged by jenkins-bot:
+ve.ce.Surface: Insert new paragraphs after empty nodes rather than before
+
+https://gerrit.wikimedia.org/r/160215",1410802196,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rmjvwpvg64vxchilw4se,task_subcomment,NA
+"VisualEditor:  Can't add new paragraphs to the end of the page, if the last line is an empty section heading == <nowiki/> ==","Change 160215 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ce.Surface: Insert new paragraphs after empty nodes rather than before
+
+https://gerrit.wikimedia.org/r/160215",1410622295,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rmjvwpvg64vxchilw4se,task_subcomment,NA
+"VisualEditor:  Can't add new paragraphs to the end of the page, if the last line is an empty section heading == <nowiki/> ==","This is also reproducible with other block nodes, like preformatted text.
+
+There's code in ve.ce.Surface#handleEnter to ""If we're at the start/end of something that's not a paragraph, insert a paragraph before/after"". The quirk is that it checks for the ""at the start"" case before checking the ""at the end"" case, and for empty elements both of these are true. Let's just flip the order.",1410622014,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-rmjvwpvg64vxchilw4se,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63600",1388780520,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_description,resolved
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","Change 127388 merged by jenkins-bot:
+Set context title when rendering edit notices and checkboxes
+
+https://gerrit.wikimedia.org/r/127388",1397879336,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","Change 127388 had a related patch set uploaded by Alex Monk:
+Set context title when rendering edit notices and checkboxes
+
+https://gerrit.wikimedia.org/r/127388",1397873423,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","In FlaggablePageView::addReviewCheck, $this->article->isReviewable() returns false.
+
+I made some uncommitted live hacks on deployment-apache01.eqiad.wmflabs and replayed the API request in Chrome until I got the right server. Turns out, $this->article represents the ""API"" title. Why is this not happening on my machine?",1397848981,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing","I see the same thing on Wikimedia sites, but cannot replicate the issue locally.",1394068668,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+"VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox ""Accept this version (includes n pending changes)"" in save dialog is missing",The message is <revreview-check-flag-p>. Presumably this doesn't get fetched in the new save dialog like it used to?,1394064108,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-25jxvzvuaojvd6jgwcvc,task_subcomment,NA
+VisualEditor: adding a reference duplicates infobox on da.wp,"https://da.wikipedia.org/w/index.php?title=F-35_Lightning_II&diff=prev&oldid=7409486
+and
+https://da.wikipedia.org/w/index.php?title=Enhedslisten&diff=prev&oldid=7414100 seem a few examples of what the title says. 
+
+I couldn't reproduce because of {T61599}.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See also**: {T51823}",1388769180,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-42a5ngyvptb5lztis6k3,task_description,resolved
+VisualEditor: adding a reference duplicates infobox on da.wp,I tried reproducing this and got nothing. Feel free to reopen if I've missed something.,1437602936,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-42a5ngyvptb5lztis6k3,task_subcomment,NA
+VisualEditor: adding a reference duplicates infobox on da.wp,"If you can't reproduce any longer, given how old the task is, feel free to close - it can be reopened if and when the need arises.",1432646744,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-42a5ngyvptb5lztis6k3,task_subcomment,NA
+VisualEditor: adding a reference duplicates infobox on da.wp,Is this still valid?,1421888145,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-42a5ngyvptb5lztis6k3,task_subcomment,NA
+VisualEditor: Make it more obvious when the user is doing something foolish with links (e.g. extending the wrong one),"Minor corruption:
+
+<https://www.mediawiki.org/w/index.php?title=Architecture_Summit_2014/Straw_poll&diff=870066&oldid=870065&diffonly=1> and <https://www.mediawiki.org/w/index.php?title=Architecture_Summit_2014/Straw_poll&diff=870064&oldid=870063&diffonly=1>
+
+More serious corruption:
+
+<https://www.mediawiki.org/w/index.php?title=Architecture_Summit_2014/Straw_poll&diff=870067&oldid=870066&diffonly=1>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1388701200,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-b6gfeng3ezs2u5pyporj,task_description,resolved
+VisualEditor: Make it more obvious when the user is doing something foolish with links (e.g. extending the wrong one),Should be fixed by the new link cartouching.,1443035624,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-b6gfeng3ezs2u5pyporj,task_subcomment,NA
+VisualEditor: Make it more obvious when the user is doing something foolish with links (e.g. extending the wrong one),@Trevor: Do you know already how you are going to handle this?,1389993157,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-b6gfeng3ezs2u5pyporj,task_subcomment,NA
+"VisualEditor: Copying part of a table into an existing cell should over-write cell values, not insert it as a sub-table","Steps to reproduce:
+
+1) Begin with an existing wikitext table (e.g., 4 rows, 4 columns).  Open the page in VisualEditor.
+
+2) Copy part of a different table or spreadsheet (e.g., 2 rows, 4 columns).
+
+3) Place cursor inside a cell of the table in VisualEditor.
+
+4) Paste the copied table.
+
+
+Results:
+
+VisualEditor places the entire new/rich-copied table, including wikitext formatting, inside the first cell.  The wikitext parser does not deal very gracefully with table-within-table formatting.
+
+
+Desired outcome:
+
+VisualEditor should overwrite the contents of the cells with the new material.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/w/index.php?diff=588462959&oldid=588405367#Create_and_copy_table.",1388613660,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-fz6jo77atbl2ydzv46s4,task_description,resolved
+"VisualEditor: Copying part of a table into an existing cell should over-write cell values, not insert it as a sub-table",I wasn't wrong. Done in wmf.12.,1454136198,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fz6jo77atbl2ydzv46s4,task_subcomment,NA
+"VisualEditor: Copying part of a table into an existing cell should over-write cell values, not insert it as a sub-table","This'll be… hard, to put it mildly. We should think about whether it's what we want to achieve in terms of UX before embarking on it.",1390025021,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fz6jo77atbl2ydzv46s4,task_subcomment,NA
+mw.user.tokens does not include all token types,"mw.user.getToken only supports edit, watch and patrol.
+It should support all other types of token.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: enhancement",1388444160,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-asfp6tebtqdcuww7w2ty,task_description,declined
+mw.user.tokens does not include all token types,"The `user.tokens` module is an internal optimisation to avoid one extra API roundtrip for built-in ajax actions such as ""Ajax watchstar"" and submitting edits to the API for e.g. VisualEditor and such.
+
+The tokens should be retrieved via `mw.Api#getToken` which already supports all other token types. There are no plans to expand the set of preloaded token types as there is no performance reason to do so (yet).
+
+Note that since 2014, most token types (such as `move`, `edit`, `delete` etc.) have been deprecated in favour of a single `csrf` token type, which should already significantly reduce the number of cases where `mw.Api#getToken` would actually need to fetch a token.",1571098112,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-asfp6tebtqdcuww7w2ty,task_subcomment,NA
+mw.user.tokens does not include all token types,Apologies mw.user.tokens.get,1388678493,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-asfp6tebtqdcuww7w2ty,task_subcomment,NA
+mw.user.tokens does not include all token types,"???
+
+I can't find mw.user.getToken. mw.api.getToken exists and it supports all tokens.",1388664579,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-asfp6tebtqdcuww7w2ty,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"screenshot of the error
+
+Steps to reproduce:
+
+1.Open a page using VE in Chrome browser.
+2.Copy a math function or item from that page
+3.Open another page with VE in FireFox
+4.Paste the copied math item in this page
+
+Observed Result:
+The math item does not get copied and in the console there is an error appearing:
+ TypeError:Item is undefined
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12369}",1388093400,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a3gencpajun7iccgc53o,task_description,resolved
+VisualEditor: Copy paste is not working for Math elements,Fixed a while ago,1442495255,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"No, I mean it renders fine for me.",1416332653,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"(In reply to Rummana Yasmeen from comment #4)
+> you mean, its fine if the copied math math function does not render on the other
+> page?
+
+*Does not*
+
+Because , right now it is not rendering unless I save the page",1416266416,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"you mean, its fine if the copied math math function does render on the other page?",1416266350,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,This... Appears to work now.,1416182975,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"Not getting the error - presumably that got fixed, but the copy does not *appear* to do anything. When I run the target in debug mode, I see that we're getting mwMath entries in the model, and you can select them. They just don't render as anything.",1407252211,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor: Copy paste is not working for Math elements,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=26th_paste_ff&veaction=edit",1388093526,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-a3gencpajun7iccgc53o,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,"screenshot of the link after copy paste
+
+Steps to reproduce:
+
+1.Open an editor in Firfox which contains a link
+2.Copy the link 
+3.Paste it into another VE and save it
+
+Observed Result:
+The link is appearing within [] bracket and with a lock icon beside it.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12199}",1387823880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_description,resolved
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,*** Bug 60379 has been marked as a duplicate of this bug. ***,1390515118,PHID-USER-4cgt73x34j35pnbem65l,False,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,Possibly got fixed by https://gerrit.wikimedia.org/r/#/c/106253/ as it was happening even just before wmf11 deployment in test2,1389902753,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,This is also happening for Chrome Browser.,1389821557,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,Test Environment should be test2 in above comment,1387824115,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox,"Test Environment:betalabs
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/23rd_paste",1387824027,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pmwa76p7ooaxhmfvsbmw,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"[14:38] <gwicke> in native CE shift-enter inserts a newline in a pre
+[14:38] <gwicke> normal enter splits it
+[14:40] <gwicke> woah: shift-enter actually works in VE as long as it is not on the last line of a pre
+[14:41] <gwicke> it does not work when the cursor is on the first or last char in a pre
+[14:41] <gwicke> before first char a paragraph is inserted before the pre
+[14:41] <gwicke> after last char a paragraph is inserted after the pre and the cursor moves there
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1387579680,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-el7cvjkat7q3jypwgavh,task_description,resolved
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"Change 809024 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (c5804af0a)%%%
+https://gerrit.wikimedia.org/r/809024",1656367024,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"Change 809024 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (c5804af0a)%%%
+https://gerrit.wikimedia.org/r/809024",1656365029,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"Change 806917 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Handle Shift+Enter at the start/end of pre nodes too%%%
+https://gerrit.wikimedia.org/r/806917",1656350224,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"Change 806917 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[VisualEditor/VisualEditor@master] Handle Shift+Enter at the start/end of pre nodes too%%%
+https://gerrit.wikimedia.org/r/806917",1655736623,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"The (ugly) workaround I'm using since years on this issue:
+- type an 'x' and the end
+- move the cursor left next to the 'x'
+- press shift-enter a couple of times to get the blank lines needed
+- edit those lines
+- finally remove the trailing 'x'
+
+I would really like to see a more user-friendly fix on this.",1639733697,PHID-USER-hhjjrf7an2jltkq76hub,False,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"And ran into this again :( quite annoying for preformatted sections in VE, I need to switch back to source editing",1639732555,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"I've also ran into this and was wondering what the status/plan for fixing or working around this bug is, thanks!",1633591756,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Adding newlines at start/end of preformatted text is broken,"I just ran into this bug while using VisualEditor and preformatted text. I consider this a severe issue in the preformatted editor, so I wonder if this could be raised and fixed.",1559285876,PHID-USER-hhjjrf7an2jltkq76hub,False,PHID-TASK-el7cvjkat7q3jypwgavh,task_subcomment,NA
+VisualEditor: Pasting formulæ isn't working in Firefox,"screenshot
+
+Steps to reproduce:
+
+1.Create a new page in FF
+2.Copy a math function from another VE 
+3.Paste it in this new page
+4.Click on Save Page
+
+Observed Result:
+""Error: Creating new, empty pages is not allowed"" appears
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12772}",1387577640,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ikkzdnx32gvzflyd7h5m,task_description,resolved
+VisualEditor: Pasting formulæ isn't working in Firefox,"Actually, Math functions are not at all getting copy pasted in FF.For a new page it says this error ""Error: Creating new, empty pages is not allowed"" and for any other existing page when you copy a math function and paste it into another VE,it shows it in the edit mode but after saving it just disappears.",1387577982,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ikkzdnx32gvzflyd7h5m,task_subcomment,NA
+VisualEditor: Pasting formulæ isn't working in Firefox,"Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5",1387577688,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ikkzdnx32gvzflyd7h5m,task_subcomment,NA
+VisualEditor:Math formula does not appear immediately after copy-paste in test2,"Steps to reproduce:
+
+1.Open the editor for a page
+2.Open the latex window and insert ""\sqrt\pi""
+3.Click on the ""<"" button to close the latex window
+4.Copy the formula immediately
+5.Paste it onto another page
+
+Observed Result:
+The math elements does not appear on the page after pasting.However after saving it appears there are multiple of those 
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/19th_december?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387485660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bcrdaw3njczs7zhzj3to,task_description,resolved
+VisualEditor:Math formula does not appear immediately after copy-paste in test2,We fixed this a while ago. :-),1415881871,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bcrdaw3njczs7zhzj3to,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,"Copied from bug 58347:
+
+1.Create a page ""A"" with three links in three consecutive lines.
+2.Create another page ""B"" where you will copy these links to.
+3.Copy the first and second link to ""B""
+4.Save it.
+5.Reopen the editor.
+6.Now copy the third link and paste it to the third line of ""B""
+7.Save it.
+
+Observed Result:
+The second and the third link in page B is getting merged.
+
+Example Pages:
+
+A:http://en.wikipedia.beta.wmflabs.org/wiki/19th_december_source?veaction=edit
+B:http://en.wikipedia.beta.wmflabs.org/wiki/19th_destination
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387471560,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2j26u6grwn6r7iymvg75,task_description,open
+New line at end of document sometimes merged into previous line on paste,"In ryasmeen's HTML dump the last paragraph contains both the text and the pasted citation. Apparently the VE rendering showed the citation in a separate line, so the discrepancy in the HTML emitted by VE (citation actually in the preceding paragraph) seems to be a bug in VE. Moving this to VE for that reason.",1389059559,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,"HTML dump:
+
+Request URL:http://en.wikipedia.beta.wmflabs.org/w/api.php
+Request Method:POST
+Status Code:200 OK
+Request Headersview source
+Accept:application/json, text/javascript, */*; q=0.01
+Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
+Accept-Encoding:gzip,deflate,sdch
+Accept-Language:en-US,en;q=0.8
+Connection:keep-alive
+Content-Length:10758
+Content-Type:application/x-www-form-urlencoded; charset=UTF-8
+Cookie:uls-previous-languages=%5B%22en%22%5D; mediaWiki.user.sessionId=IWxgkz08OFNZxaGwaIxUNKilap37xFbY; mediaWiki.user.bucket%3Aext.articleFeedbackv5%4011-tracking=11%3Aignore; mediaWiki.user.bucket%3Aext.articleFeedbackv5%406-form=6%3A6; mediaWiki.user.bucket%3Aext.articleFeedbackv5%405-links=5%3AX; centralnotice_bucket=1-4.2; enwikiLoggedOut=1389029323; centralauth_LoggedOut=1389029332; enwikiUserID=1348; enwikiUserName=RYasmeen+%28WMF%29; enwikiSession=568d9870c44e9934b5912175d6faaea9; centralauth_User=RYasmeen+%28WMF%29; centralauth_Session=0d74cc0544d444b6ba6b684092f01228; edittoolscharsubset=0; ve-beta-welcome-dialog=1
+Host:en.wikipedia.beta.wmflabs.org
+Origin:http://en.wikipedia.beta.wmflabs.org
+Referer:http://en.wikipedia.beta.wmflabs.org/wiki/Copy-paste6th?veaction=edit
+User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31
+X-Requested-With:XMLHttpRequest
+Form Dataview sourceview URL encoded
+action:visualeditor
+paction:serializeforcache
+html:<!doctype html><html prefix=""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/"" about=""http://en.wikipedia.beta.wmflabs.org/wiki/Special:Redirect/revision/73736""><head prefix=""mwr: http://en.wikipedia.beta.wmflabs.org/wiki/Special:Redirect/""><meta property=""mw:articleNamespace"" content=""0""><link rel=""dc:replaces"" resource=""mwr:revision/73705""><meta property=""dc:modified"" content=""2014-01-07T01:05:54.000Z""><meta about=""mwr:user/1348"" property=""dc:title"" content=""RYasmeen (WMF)""><link rel=""dc:contributor"" resource=""mwr:user/1348""><meta property=""mw:revisionSHA1"" content=""a473161a3483e47f6d590fd9f039238f9303b459""><meta property=""dc:description"" content=""""><meta property=""mw:parsoidVersion"" content=""0""><link rel=""dc:isVersionOf"" href=""//en.wikipedia.beta.wmflabs.org/wiki/Copy-paste6th""><title>Copy-paste6th</title><base href=""//en.wikipedia.beta.wmflabs.org/wiki/Copy-paste6th""></head><body data-parsoid=""{&quot;dsr&quot;:[0,277,0,0]}""><p data-parsoid=""{&quot;dsr&quot;:[0,20,0,0]}""><a href=""./Link_to_catapult"" rel=""mw:WikiLink"" data-parsoid=""{&quot;stx&quot;:&quot;simple&quot;,&quot;a&quot;:{&quot;href&quot;:&quot;./Link_to_catapult&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;link to catapult&quot;},&quot;dsr&quot;:[0,20,2,2]}"">link to catapult</a></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[22,31,0,0]}""><a href=""./LinkA"" rel=""mw:WikiLink"" data-parsoid=""{&quot;stx&quot;:&quot;simple&quot;,&quot;a&quot;:{&quot;href&quot;:&quot;./LinkA&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;linkA&quot;},&quot;dsr&quot;:[22,31,2,2]}"">linkA</a></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[33,42,0,0]}""><a href=""./LinkB"" rel=""mw:WikiLink"" data-parsoid=""{&quot;stx&quot;:&quot;simple&quot;,&quot;a&quot;:{&quot;href&quot;:&quot;./LinkB&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;linkB&quot;},&quot;dsr&quot;:[33,42,2,2]}"">linkB</a></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[44,101,0,0]}"">[<a href=""http://en.wikipedia.beta.wmflabs.org/wiki/LinkC|linkC"" rel=""mw:ExtLink"" data-parsoid=""{&quot;targetOff&quot;:99,&quot;contentOffsets&quot;:[99,99],&quot;dsr&quot;:[45,100,54,1]}""></a>]</p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[103,119,0,0]}""><img class=""tex"" alt=""\pi"" src=""//upload.beta.wmflabs.org/math/5/2/2/522359592d78569a9eac16498aa7a087.png"" typeof=""mw:Extension/math"" data-mw=""{&quot;name&quot;:&quot;math&quot;,&quot;attrs&quot;:{},&quot;body&quot;:{&quot;extsrc&quot;:&quot;\\pi&quot;}}"" data-parsoid=""{&quot;src&quot;:&quot;&lt;math&gt;\\pi&lt;/math&gt;&quot;,&quot;dsr&quot;:[103,119,2,2]}"" about=""#mwt7""></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[121,174,0,0]}"">text<span class=""citation web"" about=""#mwt2"" typeof=""mw:Transclusion"" data-mw=""{&quot;parts&quot;:[{&quot;template&quot;:{&quot;target&quot;:{&quot;wt&quot;:&quot;Cite web&quot;,&quot;href&quot;:&quot;./Template:Cite_web&quot;},&quot;params&quot;:{&quot;url&quot;:{&quot;wt&quot;:&quot;http://yahoo.com&quot;},&quot;title&quot;:{&quot;wt&quot;:&quot;yahoo&quot;}},&quot;i&quot;:0}}]}"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;,&quot;dsr&quot;:[125,174,null,null],&quot;pi&quot;:[[{&quot;k&quot;:&quot;url&quot;,&quot;named&quot;:true},{&quot;k&quot;:&quot;title&quot;,&quot;named&quot;:true}]]}""><a rel=""mw:ExtLink"" href=""http://yahoo.com"" data-parsoid=""{&quot;targetOff&quot;:45,&quot;contentOffsets&quot;:[45,52],&quot;a&quot;:{&quot;href&quot;:&quot;http://yahoo.com&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;A]]\n\n[[linkB]]\n\n&quot;}}"">""yahoo""</a>.</span><span title=""ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.beta.wmflabs.org%3ACopy-paste6th&amp;rft.btitle=yahoo&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fyahoo.com&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook"" class=""Z3988"" about=""#mwt2"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;}""><span style=""display:none;"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;}""><span typeof=""mw:Entity"" data-parsoid=""{&quot;src&quot;:&quot;&amp;nbsp;&quot;,&quot;srcContent&quot;:&quot;&nbsp;&quot;}"">&nbsp;</span></span></span></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[176,180,0,0]}"">text</p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[182,198,0,0]}""><img class=""tex"" alt=""\pi"" src=""//upload.beta.wmflabs.org/math/5/2/2/522359592d78569a9eac16498aa7a087.png"" typeof=""mw:Extension/math"" data-mw=""{&quot;name&quot;:&quot;math&quot;,&quot;attrs&quot;:{},&quot;body&quot;:{&quot;extsrc&quot;:&quot;\\pi&quot;}}"" data-parsoid=""{&quot;src&quot;:&quot;&lt;math&gt;\\pi&lt;/math&gt;&quot;,&quot;dsr&quot;:[182,198,2,2]}"" about=""#mwt9""></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[200,204,0,0]}"">text</p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[206,222,0,0]}""><img class=""tex"" alt=""\pi"" src=""//upload.beta.wmflabs.org/math/5/2/2/522359592d78569a9eac16498aa7a087.png"" typeof=""mw:Extension/math"" data-mw=""{&quot;name&quot;:&quot;math&quot;,&quot;attrs&quot;:{},&quot;body&quot;:{&quot;extsrc&quot;:&quot;\\pi&quot;}}"" data-parsoid=""{&quot;src&quot;:&quot;&lt;math&gt;\\pi&lt;/math&gt;&quot;,&quot;dsr&quot;:[206,222,2,2]}"" about=""#mwt11""></p>
+
+<p data-parsoid=""{&quot;dsr&quot;:[224,277,0,0]}"">text<span class=""citation web"" about=""#mwt5"" typeof=""mw:Transclusion"" data-mw=""{&quot;parts&quot;:[{&quot;template&quot;:{&quot;target&quot;:{&quot;wt&quot;:&quot;Cite web&quot;,&quot;href&quot;:&quot;./Template:Cite_web&quot;},&quot;params&quot;:{&quot;url&quot;:{&quot;wt&quot;:&quot;http://yahoo.com&quot;},&quot;title&quot;:{&quot;wt&quot;:&quot;yahoo&quot;}},&quot;i&quot;:0}}]}"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;,&quot;dsr&quot;:[228,277,null,null],&quot;pi&quot;:[[{&quot;k&quot;:&quot;url&quot;,&quot;named&quot;:true},{&quot;k&quot;:&quot;title&quot;,&quot;named&quot;:true}]]}""><a rel=""mw:ExtLink"" href=""http://yahoo.com"" data-parsoid=""{&quot;targetOff&quot;:45,&quot;contentOffsets&quot;:[45,52],&quot;a&quot;:{&quot;href&quot;:&quot;http://yahoo.com&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;A]]\n\n[[linkB]]\n\n&quot;}}"">""yahoo""</a>.</span><span title=""ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.beta.wmflabs.org%3ACopy-paste6th&amp;rft.btitle=yahoo&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fyahoo.com&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook"" class=""Z3988"" about=""#mwt5"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;}""><span style=""display:none;"" data-parsoid=""{&quot;stx&quot;:&quot;html&quot;}""><span typeof=""mw:Entity"" data-parsoid=""{&quot;src&quot;:&quot;&amp;nbsp;&quot;,&quot;srcContent&quot;:&quot;&nbsp;&quot;}"">&nbsp;</span></span></span></p><span typeof=""mw:Transclusion"" data-mw=""{&quot;parts&quot;:[{&quot;template&quot;:{&quot;target&quot;:{&quot;wt&quot;:&quot;Cite web&quot;,&quot;href&quot;:&quot;./Template:Cite_web&quot;},&quot;params&quot;:{&quot;url&quot;:{&quot;wt&quot;:&quot;http://yahoo.com&quot;},&quot;title&quot;:{&quot;wt&quot;:&quot;yahoo&quot;}},&quot;i&quot;:0}}]}"" data-ve-no-generated-contents=""true"" class=""citation web""></span><p></p></body></html>
+page:Copy-paste6th
+oldid:73736
+format:json
+Response Headersview source
+Accept-Ranges:bytes
+Age:0
+Cache-control:private
+Connection:keep-alive
+Content-Encoding:gzip
+Content-Length:97
+Content-Type:application/json; charset=utf-8
+Date:Tue, 07 Jan 2014 01:12:09 GMT
+Server:Apache
+Vary:Accept-Encoding
+Via:1.1 varnish, 1.1 varnish
+X-Cache:deployment-cache-text1 miss (0), deployment-cache-text1 frontend miss (0)
+X-Content-Type-Options:nosniff
+X-Frame-Options:SAMEORIGIN
+X-Powered-By:PHP/5.3.10-1ubuntu3.9+wmf1
+X-Varnish:239733000, 2143990872
+X-Vary-Options:Accept-Encoding;list-contains=gzip",1389057352,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,"Created attachment 14240
+Screenshot of template getting merged with the previous line
+
+**Attached**: {F12624}",1389048178,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,"The original issue described in this bug is not occurring anymore but a similar issue is found not sure if they are related or not.If not, I will file a separate issue:
+
+1.Create a page ""A"" with a template Cite Web
+2.Create another page ""B"" where you will copy the template.
+3.Add some text or any other element like math function/Link to Page ""B""
+4.Copy the CiteWeb template created in page A and paste it into the next line of B
+
+Observed Result:
+The template gets merged with the previous element/line.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Copy-paste6th
+
+See the screenshot attached.",1389048141,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+New line at end of document sometimes merged into previous line on paste,Can you provide a sample of the relevant HTML your are producing in VE?,1387495467,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2j26u6grwn6r7iymvg75,task_subcomment,NA
+TemplateData: Add property to indicate in which namespaces a template should be used,"**Author:** `prlpz`
+
+**Description:**
+I suggest including in TemplateData a field about the namespaces where the template is intended to be used. VisualEditor should use this field to suggest the template only in the right namespaces.
+
+For example, nowadays VisualEditor suggest using template documentation templates while editing articles, but such templates should only be used in template namespace. TemplateData could make VisualEditor know that those templates shouldn't be suggested there.",1387393320,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cu3bvvy2inqyghkz63xu,task_description,duplicate
+TemplateData: Add property to indicate in which namespaces a template should be used,"@Krinkle, @Jdforrester-WMF: Any thoughts on this one? If we decided this is a good idea, we'd need to figure out which is the best format for users to express the namespaces in.",1452891227,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cu3bvvy2inqyghkz63xu,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Core has a build system to generate HTML from kss-formatted CSS/LESS (docs/kss). It would be nice if this documentation appeared in doc.wikimedia.org along with other generated documentation.
+
+This sounds like T50337. Presumably there's some Zuul job somewhere building the doc that appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1387336620,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_description,declined
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,Old school cc @Volker_E ,1532486031,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,kss is still in core.,1464911476,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,We are no longer using kss in MobileFrontend. It wasn't being maintained due to lack of visibility and shift to OOjs UI.,1464025554,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Seems fine: npm-run-script doc
+
+In Jenkins Job Builder, I have generic templates for python tox and ruby bundler:
+
+'{name}-tox-{toxenv}'
+'{name}-bundle-{bundlecommand}'  https://gerrit.wikimedia.org/r/#/c/160983/
+
+So we can probably come up with a '{name}-npmrunscript-{npmscript}' command which would be realized as:
+
+- project:
+  name: VisualEditor
+  npmscript:
+   - doc
+  jobs:
+   - '{name}-npmrunscript-{npmscript}'
+
+
+And the template would contain:
+
+ npm run-script {npmscript}
+
+Might need to add an 'npm install' before, not sure.",1411573308,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"(In reply to Antoine ""hashar"" Musso from comment #14)
+> > Do you mean Grunt (which runs on node.js)?  That's the node.js build tool
+> > I normally see used.
+> 
+> I guess npm as an entry point for jenkins (i.e. npm test) which would then
+> use grunt to run a wide range of different tests :d
+
+Hmm, thanks.  This is not a test though.
+
+While ""npm test"" exists (https://www.npmjs.org/doc/cli/npm-test.html), ""npm doc"" does not.  There is apparently a way to have custom scripts (https://www.npmjs.org/doc/misc/npm-scripts.html , https://www.npmjs.org/doc/cli/npm-run-script.html), but we would need to standardize on a name (e.g. npm-run-script doc).
+
+Is there such a convention already?",1411530930,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Change 161998 had a related patch set uploaded by Prtksxna:
+kss: Add Gruntfile
+
+https://gerrit.wikimedia.org/r/161998",1411409150,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"> Do you mean Grunt (which runs on node.js)?  That's the node.js build tool
+> I normally see used.
+
+I guess npm as an entry point for jenkins (i.e. npm test) which would then use grunt to run a wide range of different tests :d",1411372542,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"(In reply to Antoine ""hashar"" Musso from comment #11)
+> Can you reach out to Timo about it?  I think for Javascript purposes he
+> would like developers to define npm entry points.  So we would simply invoke
+> 'npm doc' or something and publish whatever is generated under a given dir
+> (ex: /doc/).
+
+Do you mean Grunt (which runs on node.js)?  That's the node.js build tool I normally see used.",1411185072,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,Timo is in the office this week.. Maybe you could grab him S?,1411152851,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Can you reach out to Timo about it?  I think for Javascript purposes he would like developers to define npm entry points.  So we would simply invoke 'npm doc' or something and publish whatever is generated under a given dir (ex: /doc/).
+
+That would let you define whatever you want to run to build documentation which is much more scalable than having to handle defines in jenkins.",1411138490,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,yardoc is now being used and Jenkins is populating https://doc.wikimedia.org/rubygems/mediawiki-ruby-api/ and https://doc.wikimedia.org/rubygems/mediawiki-selenium/ .  So that's something to study when implementing this.,1411083312,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"In the interim, `ssh tools-login.wmflabs.org; become styleguide` is generating http://tools.wmflabs.org/styleguide/ in a cron job. I don't understand misc.yaml, mediawiki.yaml, zuul-config/layout.yaml enough to work on this.",1411077493,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,*** Bug 64221 has been marked as a duplicate of this bug. ***,1400706420,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Since mss is a node module, we could have it added to the integration/jenkins.git repository which has tools/package.json. It currently provides:
+
+ {
+	""name"": ""wikimedia-integration-jenkins"",
+	""version"": ""0.2.5"",
+	""dependencies"": {
+		""grunt"": ""0.4.1"",
+		""grunt-cli"": ""0.1.13"",
+		""grunt-contrib-qunit"": ""0.4.0"",
+		""phantomjs"": ""~1.9.0-1"",
+		""grunt-contrib-csslint"": ""0.2.0"",
+		""jshint"": ""2.4.4""
+	}
+ }
+
+So maybe add kss in there and forget about git-deploy and integration/kss.",1399032201,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,Pending upload of kss in integration/kss.git so we can get it deployed on Jenkins slaves.  Then we need some script to generate the doc and move the generated doc under the doc website.,1393241708,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Change 103095 merged by Alexandros Kosiaris:
+Add integration/kss to deployment repo config
+
+https://gerrit.wikimedia.org/r/103095",1388491753,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,I have created a .gitreview file for integration/kss.git repository so we can add it in the deployment system.,1388491699,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Change 103095 had a related patch set uploaded by Spage:
+Add integration/kss to deployment repo config
+
+https://gerrit.wikimedia.org/r/103095",1387626505,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"Target url should indeed me something like one of these this:
+
+
+https://doc.wikimedia.org/mediawiki-core/master/less/
+https://doc.wikimedia.org/mediawiki-core/master/css/
+https://doc.wikimedia.org/mediawiki-core/master/style-guide/css/
+
+Preferences, anyone?
+
+(where master can also be REL1_22, and in the future tags like 1.23.0)
+
+With a shortcut from the https://doc.wikimedia.org/ home page, of course.
+
+PS: I'm planning on renaming /mediawiki-core to /mediawiki at some point (with redirects and symlinks of course).",1387430906,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org,"S, as a first step we need a way to deploy kss on the Jenkins slave.
+
+It seems that is a nodejs application so I guess we want to use our own repository that would provide kss and ALL the required modules.  We did such a thing to provide ruby bundler (integration/bundler.git) and phpunit (integration/phpunit.git).
+
+Could you take care of having an integration/kss.git repository created and upload there the kss + its npm modules ?
+
+
+Once done, register that repository in git-deploy configuration. That is done in operations/puppet.git under manifests/role/deployment.pp.  The deployment would then be done from tin.eqiad.wmnet.
+
+
+Then, we need a shell script wrapper that would execute the script (deployed somewhere under /srv/deployment/integration/kss ).  https://doc.wikimedia.org/ document root is under /srv/org/wikimedia/doc/  the following sub directories are usually: <project-name> / <branch> / <doc component>.  Example:
+
+ /srv/org/wikimedia/doc/mediawiki-core/REL1_22/js
+
+
+So I guess you would want to have kss generate the doc to  /srv/org/wikimedia/doc/mediawiki-core/master/css
+
+
+Once done, we need a new job-template in Jenkins Job Builder configuration, apply it to mediawiki/core project.  The job will need to be added in Zuul configuration (integration/zuul-config.git) in the postmerge pipeline.",1387357961,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ew5qrcq2dqqfmtj4zhhi,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"This causes the test 'document with meta elements: data' in ve.dm.MWConverter to fail. Not sure if it is any more serious than that.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387307700,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-irztrimblav2ughjnygh,task_description,open
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"Is this still a problem? I don't see any such test failing, at least.",1574099357,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"(In reply to comment #3)
+> (In reply to comment #0)
+> > This causes the test 'document with meta elements: data' in ve.dm.MWConverter
+> > to fail. Not sure if it is any more serious than that.
+> 
+> Are you comparing a HTML serialization or the DOM attribute? A diff in the
+> former is fine, but a diff in the latter would be a bug.
+
+Actually, a diff in the *percent-decoded* DOM href attribute would be a bug.
+
+We decode all hrefs in the serializer, so to us it makes no difference if it is encoded as %20 or a literal space in HTML.",1387572712,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"(In reply to comment #0)
+> This causes the test 'document with meta elements: data' in ve.dm.MWConverter
+> to fail. Not sure if it is any more serious than that.
+
+Are you comparing a HTML serialization or the DOM attribute? A diff in the former is fine, but a diff in the latter would be a bug.",1387563203,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"(In reply to comment #1)
+> A space is not a valid character in an URL, it must always be
+> percent-encoded.
+> https://en.wikipedia.org/wiki/URL#List_of_allowed_URL_characters
+
+Are we talking about HTTP or HTML here? If it is HTML, then I'd suggest looking at the relevant HTML5 spec.",1387559561,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+VisualEditor: Computed href in Firefox normalises ' ' to '%20',"A space is not a valid character in an URL, it must always be percent-encoded. https://en.wikipedia.org/wiki/URL#List_of_allowed_URL_characters",1387309200,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-irztrimblav2ughjnygh,task_subcomment,NA
+Cut and Paste of references occasionally fails,"Occasionally, cut and paste of text that includes a reference will fail in a weird way. I was able to isolate one reproducible case: 
+
+1. The article contains text S, followed by a reference for S, some more text T, followed by a reference for T.
+
+2. We cut (Ctrl-X) part or all of text T, including its reference.
+
+3. We paste (Ctrl-V) somewhere in the middle of text S (*not* at the beginning of S)
+
+Result: the article view is scrolled to the top, the pasted text is in wrong order, all of a sudden we have three references.
+
+See https://www.mediawiki.org/wiki/VisualEditor:TestAxelBoldt#Regression_15:_Cut.2FPaste_of_references for a sandbox where you can try it out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387229820,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-yqdyvohgcbxzehgnpq4g,task_description,resolved
+Cut and Paste of references occasionally fails,I can't reproduce either.,1436503691,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-yqdyvohgcbxzehgnpq4g,task_subcomment,NA
+Cut and Paste of references occasionally fails,"I tired it on the page where the original test is placed- https://www.mediawiki.org/wiki/VisualEditor:TestAxelBoldt?veaction=edit#Regression_15%253A_Cut.2FPaste_of_references
+
+- no scroll-up when pasting the text
+- the text pasted correctly",1419351940,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-yqdyvohgcbxzehgnpq4g,task_subcomment,NA
+Cut and Paste of references occasionally fails,Can't reproduce anymore.,1419350787,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-yqdyvohgcbxzehgnpq4g,task_subcomment,NA
+Enable VisualEditor in the Reports namespace on officewiki,"Per Guillaume's request on IRC. This is namespace 100.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1387226280,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-d7gosdnm6wposiphhgbw,task_description,resolved
+Enable VisualEditor in the Reports namespace on officewiki,Now done.,1387324738,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d7gosdnm6wposiphhgbw,task_subcomment,NA
+Enable VisualEditor in the Reports namespace on officewiki,"Change 101908 merged by Reedy:
+Make officewiki's Report: namespace VE-enabled
+
+https://gerrit.wikimedia.org/r/101908",1387315187,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d7gosdnm6wposiphhgbw,task_subcomment,NA
+Enable VisualEditor in the Reports namespace on officewiki,\o/ Thanks :),1387305647,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-d7gosdnm6wposiphhgbw,task_subcomment,NA
+Enable VisualEditor in the Reports namespace on officewiki,"Change 101908 had a related patch set uploaded by Jforrester:
+Make officewiki's Report: namespace VE-enabled
+
+https://gerrit.wikimedia.org/r/101908",1387226388,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d7gosdnm6wposiphhgbw,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Steps to reproduce:
+
+1.Open the editor.
+2.Add a template
+3.Save the page
+4.Reopen the editor
+5.Copy the template 
+
+Observed Result:
+
+It gives an error:Uncaught TypeError: Cannot convert null to object .However, it does get pasted correctly onto other VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386890940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7g7uyqfy56h27dadb2t4,task_description,resolved
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Verified the fix in test2 with MediaWiki 1.23wmf8 on page:
+https://test2.wikipedia.org/wiki/19th_december",1387484794,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,Verified the fix in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/The_destination_template,1386993261,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Change 101148 merged by jenkins-bot:
+Check values property exists before removing attribute
+
+https://gerrit.wikimedia.org/r/101148",1386963584,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"For betalabs, I could reproduce for only templates which has parameters with values",1386896635,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Change 101148 had a related patch set uploaded by Esanders:
+Check values property exists before remove attribute
+
+https://gerrit.wikimedia.org/r/101148",1386893250,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,Can you reproduce on beta labs?,1386892999,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Created attachment 14077
+screenshot
+
+**Attached**: {F12097}",1386891161,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: removeHtmlAttributes throws an exception when copying complex templates,"Test Environment: production-https://en.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5",1386891103,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7g7uyqfy56h27dadb2t4,task_subcomment,NA
+VisualEditor: The active template sprite stays at the same place when a window is resized,"To reproduce:
+
+1. Edit a page with a template.
+2. Click the template so the darker blue sprite appears.
+3. Resize the window.
+
+Observed: The transparent blue sprite stays at the same place on the screen.
+
+Expected: The transparent blue sprite should move to the new location of the template of the screen.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386863460,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-3ysx7zhkex33mtvcwvjv,task_description,resolved
+VisualEditor: The active template sprite stays at the same place when a window is resized,This is now fixed.,1394223139,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ysx7zhkex33mtvcwvjv,task_subcomment,NA
+"VisualEditor: <visualeditor-toolbar-insert> is showing up in the toolbar instead of ""Insert"" in betalabs","screenshot
+
+<visualeditor-toolbar-insert> is showing up in the toolbar instead of More in betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11989}",1386806520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yj26bqg27rohxa63lh2v,task_description,resolved
+"VisualEditor: <visualeditor-toolbar-insert> is showing up in the toolbar instead of ""Insert"" in betalabs",verified on test2:https://test2.wikipedia.org/w/index.php?title=13th_december&veaction=edit,1386982882,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yj26bqg27rohxa63lh2v,task_subcomment,NA
+"VisualEditor: <visualeditor-toolbar-insert> is showing up in the toolbar instead of ""Insert"" in betalabs",Verified in Betalabs,1386824971,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-yj26bqg27rohxa63lh2v,task_subcomment,NA
+"VisualEditor: <visualeditor-toolbar-insert> is showing up in the toolbar instead of ""Insert"" in betalabs",This is now fixed in betalabs after we caused the English messages to get re-synched.,1386821225,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yj26bqg27rohxa63lh2v,task_subcomment,NA
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion","The following pages all exist on en.wikipedia.org:
+
+* [[Bird]]
+* [[Big]]
+* [[Big!]]
+* [[Big Ten Conference]]
+
+When querying action=opensearch for:
+
+* ""Bir"": 0 => ""Bird""
+   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Bir
+   [input,[""Bird"",""Birmingham"",..]]
+
+* ""Bird"": 0 => ""Bird""
+   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Bird
+   [input,[""Bird"",""BirdLife International"",..]]
+
+* ""Big"": 
+   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Big
+   [""Big"",[""Big Ten Conference"",""Big band"",...]]
+
+* ""Big"": 
+   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Big!
+   [""Big!"",[""Big Ten Conference"",""Big band"",...]]
+
+In the last two, ""Big"" and ""Big!"" are nowhere in the response.
+
+Filing against Wikimedia for now, because this seems related to one of our search backends, not plain MediaWiki core or plain MediaWiki core with Extension:TitleKey installed.
+
+This is currently causing issues in VisualEditor when making a link to a page called ""Big"", or ""Big!"" as it will think the page doesn't exist and suggest to make a red link, as, thus far, we've always assumed that if a page by the exact title exists, it should be the first suggestion.
+
+It normalising casing and/or special characters is fine, but shouldn't make it not give an exact match as first result.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**Whiteboard**: cirrus-fixed",1386736380,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_description,resolved
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion",This issue is now fixed.,1478802678,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_subcomment,NA
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion","Some good news, at least.  Cirrus does what you'd expect.  If you have a page named ""Big!"" and type ""Big!"" into the search box it'll return Big! as the suggestion.",1386774325,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_subcomment,NA
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion","I'm pretty sure 'OpenSearchXml' is not the right component. Also, cc-ing search people.",1386773876,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_subcomment,NA
+"opensearch: Querying for ""Big"" or ""Big!"" should include ""Big"" or ""Big!"" as first suggestion","VisualEditor screenshots:
+
+- Big! http://cl.ly/image/3U3V1h1B3i0r
+- Big  http://cl.ly/image/193c290i1X0z",1386736491,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kvwonhqh7mk3tnuapkuo,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/w/index.php?title=Toronto_Maple_Leafs&diff=585067098&oldid=584791615",1386701940,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_description,duplicate
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",Last report a year ago; presumably this was a Parsoid issue that was since fixed?,1429611978,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","No steps to reproduce; no-one managed to reproduce; no new known occurrences for nearly a year. Setting status to STALLED.
+
+>>! In T60282#642603, @Whatamidoing-WMF wrote:
+> I'll ask the user who encountered this one:
+
+The reply of that user was ""I am using Mozilla Firefox on a Dell Inspiron One desktop computer.""",1426770504,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",Thanks!,1397773016,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","It happened yesterday:
+
+https://en.wikipedia.org/w/index.php?title=IPhone&curid=8841749&diff=604427150&oldid=604113181
+
+I'll ask the user who encountered this one:
+
+https://en.wikipedia.org/w/index.php?title=Michael_Jackson&curid=14995351&diff=603943260&oldid=603918451
+
+since she's pretty active.",1397772982,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","I can't reproduce this in Chrome, Safari, Opera or Firefox. Is it possible that this is a browser plug-in or a very odd browser corruption?",1397761334,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Here's another:  
+
+https://en.wikipedia.org/w/index.php?title=Fandango_%28wrestler%29&curid=21330399&diff=602066359&oldid=601951852
+
+This one broke over ""&quot;""",1396282951,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Here's another:
+
+https://en.wikipedia.org/w/index.php?title=The_National_%28band%29&curid=2308112&diff=600606533&oldid=600023816
+
+This time, the ref name contained a template:  <ref name=""{{BillboardURLbyName|artist=the national|chart=Billboard 200}}"">
+
+Like most of the others, this is probably the result of a sloppy script.",1395856532,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Other example on frwiki https://fr.wikipedia.org/w/index.php?title=Salon_international_de_l%27agriculture&curid=205829&diff=101773303&oldid=101729054
+
+Apparently, the user didn't even modify the chapter where the problem occurs.",1393949199,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",According to https://en.wikipedia.org/w/index.php?title=Colours_in_the_Dark_%28album%29&curid=39317223&diff=595492480&oldid=593715294 it appears that this happens on HTML codes for things other than non-breaking spaces.  #124 is a vertical bar.,1392491240,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""","Another diff, this time involving a {{nowrap}} template:  https://en.wikipedia.org/w/index.php?title=Michael_Jackson&curid=14995351&diff=595247974&oldid=595208734
+
+This only seems to affect nbsp's that are present in ref names (where they probably oughtn't be anyway).",1392333395,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",Another report of this: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=590211100&oldid=590159444,1389446531,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+"VisualEditor: HTML non-breaking spaces (&nbsp;) converted to "",[object Object], ,[object Object],""",This also affects vertical bars ( &#124; ) as seen at ttps://en.wikipedia.org/w/index.php?title=Paper_Planes&diff=585505452&oldid=581736416,1386881945,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-abahz4qyzn3wpoxxwffa,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"We're seeing more and more JSON files entering our repos, and there is an RfC in discussion[1] to move to JSON files for our localisation.
+
+Please add standard JSON linting when patch sets that have Jenkins jobs configured.
+
+[1] https://www.mediawiki.org/wiki/Requests_for_comment/Localisation_format
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: major",1386696900,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_description,resolved
+Jenkins: Add a lint job for JSON,"Whether ideal for the long term or not, it was resolved by Antoine by including it in the jslint job.
+
+For the long term, projects should include a jsonlint task in their own test pipeline.
+
+For localisation json files in particular, see T66045#962750.",1420726011,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Whether ideal for the long term or not, it was resolved by Antoine by including it in the jslint job.
+
+For the long term, projects should include a jsonlint task in their own test pipeline.",1420725969,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to Bawolff (Brian Wolff) from comment #26)
+> (In reply to Bawolff (Brian Wolff) from comment #25)
+> > Re-opening. I just managed to submit a patch (
+> > https://gerrit.wikimedia.org/r/#/c/147754/ ) with a rather stupid json
+> > error, and jenkins did not complain.
+> 
+> Its been pointed out to me that the jslint job (which is non-voting on
+> TimedMediaHandler) is what verifies json files (Although
+> https://integration.wikimedia.org/ci/job/mwext-TimedMediaHandler-jslint/497/
+> consoleText doesn't seem to say anything about an i18n file failing). I'd
+> like to suggest that the job be split. As missing a coding convention and a
+> fatal error are rather different types of issues.
+
+I agree it shouldn't be part of the jslint job. But I don't think we should change that for the time being. The jslint job in general is an older one that is being phased out by having projects adopt Grunt instead. Where they can add jshint, jscs, banana-checker, and (if they have non-i18n json files) json-lint to their pipeline.
+
+TMH repo should be updated by adding the appropriate jshint config and ignores so that their non-voting exemption may be lifted. Because right now, obvious syntax errors in javascript files aren't caught, either. Which is just as important as json syntax errors.",1416447458,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to Bawolff (Brian Wolff) from comment #25)
+> Re-opening. I just managed to submit a patch (
+> https://gerrit.wikimedia.org/r/#/c/147754/ ) with a rather stupid json
+> error, and jenkins did not complain.
+
+Its been pointed out to me that the jslint job (which is non-voting on TimedMediaHandler) is what verifies json files (Although https://integration.wikimedia.org/ci/job/mwext-TimedMediaHandler-jslint/497/consoleText doesn't seem to say anything about an i18n file failing). I'd like to suggest that the job be split. As missing a coding convention and a fatal error are rather different types of issues.",1406487694,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Re-opening. I just managed to submit a patch ( https://gerrit.wikimedia.org/r/#/c/147754/ ) with a rather stupid json error, and jenkins did not complain.",1406486678,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,All 275 jobs updated.,1396269337,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 113958 merged by jenkins-bot:
+Add json-lint.php command to -jslint jobs
+
+https://gerrit.wikimedia.org/r/113958",1396267695,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,I forgot to deploy https://gerrit.wikimedia.org/r/#/c/113958/ last monday. Updating jobs now.,1396266829,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to Nemo from comment #19)
+> > Will be done next Monday: March 17th.
+> 
+> Was it?
+
+Seems not.
+
+Setting severity from Siebrand's duplicate.",1396254075,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,*** Bug 63293 has been marked as a duplicate of this bug. ***,1396253986,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to Antoine ""hashar"" Musso from comment #18)
+> Mailled wikitech-l about it
+> http://lists.wikimedia.org/pipermail/wikitech-l/2014-March/075092.html
+> 
+> Will be done next Monday: March 17th.
+
+Was it? Another example: https://gerrit.wikimedia.org/r/#/c/121910/
+All extensions should have JSON files checked for validity (locally I use a simple json_verify < $FILE.json ).",1396088633,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Mailled wikitech-l about it http://lists.wikimedia.org/pipermail/wikitech-l/2014-March/075092.html
+
+Will be done next Monday: March 17th.",1394468825,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 114464 merged by jenkins-bot:
+json syntax error with escaped single quotes
+
+https://gerrit.wikimedia.org/r/114464",1392909530,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 114464 had a related patch set uploaded by Hashar:
+json syntax error with escaped single quotes
+
+https://gerrit.wikimedia.org/r/114464",1392906623,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"I have run the json linter on all extensions and three files are not understood by PHP json_decode() :-(
+
+hashar@gallium:~/extensions$ /srv/deployment/integration/slave-scripts/bin/json-lint.php .
+./TemplateData/spec.templatedata.json: json decode error.
+./VisualEditor/modules/ve-mw/i18n/qqq.json: json decode error.
+./VisualEditor/modules/syntaxhighlight/rules/mysql.json: json decode error.
+hashar@gallium:~/extensions$",1392904903,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 113958 had a related patch set uploaded by Hashar:
+Add json-lint.php command to -jslint jobs
+
+https://gerrit.wikimedia.org/r/113958",1392734924,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 107163 merged by jenkins-bot:
+json-lint.php: recursively lint json files with PHP
+
+https://gerrit.wikimedia.org/r/107163",1390853068,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to comment #11)
+> Have you verified that it warns for double quotes in *.json files as well?
+
+Yes I did (comment #4) which prompted me to repurpose this bug in writing a wrapper around PHP json_decode() which I did in Gerrit change #107163.
+
+I guess jshint would have the same issue with trailing comma in arrays (none in json) or keys having to be enclosed by quotes.",1389643526,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to comment #4)
+> json files requires double quotes which jshint complains about. So I guess we
+> need a different job that would use jshint with a specific configuration.
+
+Have you verified that it warns for double quotes in *.json files as well?
+
+I don't think JSHint will parse json files exactly the same as js files, even if explicitly told to via ` --extra-ext json` because a plain JSON object is not a valid JS statement.
+
+Meaning, if you feed { ""foo"": ""bar"" } to a javascript parser as a statement, it will not be an object (it will be a block statement with a label foo and a statement with an unassigned string ""bar"").
+
+As such, using jshint to parse json files would either be
+1) pointless, as it would be validated as javascript instead of json, likely causing all kinds of false positives not even related to coding or quoting style
+
+or 2) JSHint recognises it as a JSON file and therefore one would expect it to not warn for double quotes.",1389629338,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 107163 had a related patch set uploaded by Krinkle:
+json-lint.php: recursively lint json files with PHP
+
+https://gerrit.wikimedia.org/r/107163",1389629045,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"Change 107163 had a related patch set uploaded by Hashar:
+json-lint.php: recursively lint json files with PHP
+
+https://gerrit.wikimedia.org/r/107163",1389627596,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"I guess one can write a basic lint script that would wrap around PHP json_decode() ?   If we can decode it, I guess we are safe :]",1389359970,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"I have an example of invalid JSON that got merged, and caused issues in the L10n process:
+
+Line 215 of https://gerrit.wikimedia.org/r/#/c/106460/1/data/i18n/qqq.json has a trailing comma that, when a JSON linter is there, should have blocked the merge of that patch set.",1389359446,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to comment #5)
+> (In reply to comment #4)
+> > json files requires double quotes which jshint complains about. So
+> > I guess we need a different job that would use jshint with a specific
+> > configuration.
+> 
+> If we're using JSON, we might as well do it right, so I guess those
+> complaints
+> are justified?
+
+Oh, wait. Yes, of course, Antoine :).",1389004291,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"(In reply to comment #4)
+> json files requires double quotes which jshint complains about. So I guess we
+> need a different job that would use jshint with a specific configuration.
+
+If we're using JSON, we might as well do it right, so I guess those complaints are justified?",1389004257,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,json files requires double quotes which jshint complains about. So I guess we need a different job that would use jshint with a specific configuration.,1389003947,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,"The jslint job is already present for extension and is triggered by Zuul whenever a .jshint*, *.js or *.json file is modified.
+
+A culprit is that by default jshint does not parse .json files, so we want to instruct it to parse such files using:
+
+ jshint --extra-ext json .",1389003835,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,Any updates on this yet?,1389002205,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+Jenkins: Add a lint job for JSON,Timo thoughts?  Should we incorporate that in the jslint job that runs jshint ?,1386697332,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-op7hsmyyqri3qvye5pcj,task_subcomment,NA
+VisualEditor: Make the media dialog one dialog again,"Merge MWMediaInsertDialog and MWMediaEditDialog into one dialog that has an insert page and an edit page, and a BookletLayout without an outline. This way we can switch between modes without closing one dialog and opening another.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1386638100,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-o26zcq73b7wls4nly65z,task_description,resolved
+VisualEditor: Make the media dialog one dialog again,"
+
+*** This bug has been marked as a duplicate of bug 67170 ***",1412590279,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-o26zcq73b7wls4nly65z,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Toolserver has a limited and anonimized view of the user_properties table available. This is used for reports like https://en.wikipedia.org/wiki/Wikipedia:Database_reports/User_preferences
+
+mysql> describe user_properties;
+| Field       | Type           | Null | Key | Default | Extra |
+| -----  | -----  | -----   | ----- | ----- | ----- |
+| up_user     | int(11)        | NO   |     | 0       |       |
+| up_property | varbinary(255) | YES  |     | NULL    |       |
+| up_value    | blob           | YES  |     | NULL    |       |
+3 rows in set (0.00 sec)
+
+mysql> describe user_properties_anonym;
+| Field                   | Type           | Null | Key | Default | Extra |
+| -----  | -----  | -----   | ----- | ----- | ----- |
+| up_property             | varbinary(255) | YES  |     | NULL    |       |
+| up_value                | blob           | YES  |     | NULL    |       |
+| ts_user_touched_cropped | varbinary(8)   | NO   |     |         |       |
+3 rows in set (0.00 sec)
+
+Only preferences that are considered to be public are replicated, the list from enwiki_p is:
+mysql> select distinct(up_property) from user_properties;
+| up_property    |
+| -----  |
+| disablemail    |
+| fancysig       |
+| gender         |
+| language       |
+| nickname       |
+| skin           |
+| timecorrection |
+| variant        |
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+* {T27302}
+* {T21288}",1386566220,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_description,resolved
+Tool Labs: Provide anonymized view of the user_properties table,The underlying data has been backfilled.,1448850365,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Re-opening since the `user_properties_anon` table is still missing the `upa_touched` timestamp field (per @coren earlier's comment, this is blocked on T92841).
+",1442982359,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Re-opening since the `user_properties_anon` table is still missing the `upa_touched` field (per @coren earlier's comment, this is blocked on T92841).
+",1442982341,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"T66115 has been resolved, but `user_properties_anon` isn't working properly yet since `upa_touched` is null everywhere. (Depends on T92841).
+
+Due to the lack of this column, utility queries previously common on Toolserver like ""How many active users are using gadget X"" are not possible. And essential queries for gadget maintainers when making decisions about deprecated gadgets being replaced, etc.
+
+Now we get shell requests for these (or over IRC) and run them in production. But it'd be better if people can run these themselves in labs or via Quarry.",1442981844,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"T66115 has been resolved, but `user_properties_anon` isn't working properly yet since `upa_touched` is null everywhere. (Depends on T92841).
+
+Previously common utility queries like ""How many active users are using Cologne Blue"" are not possible yet. And essential queries for gadget maintainers when making decisions about deprecated gadgets being replaced.
+
+Now we get shell requests for these (or over IRC). But it'd be better if they can run those themselves.",1434502044,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"The view exists, and is working.  Whitelisting other properties is fairly easy, but requests for this should be made in separate tasks.",1427309623,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#1123999, @Ricordisamoa wrote:
+> AFAICS, and as noted in this task's description, the user_properties table already contains ""preferences that are considered to be public"", such as the ones you mentioned.
+> 
+> Just tried:
+> ```lang=sql
+> SELECT up_value FROM user_properties INNER JOIN user ON user_id = up_user AND user_name = 'Ricordisamoa' AND up_property = 'gender';
+> ```
+
+Huh, fair play. I guess most of this database report got fixed with the resolution of {T66115}.",1426556503,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#1123825, @MZMcBride wrote:
+> Thank you for <https://gerrit.wikimedia.org/r/197055>!
+> 
+> Looking at <https://en.wikipedia.org/wiki/Wikipedia:Database_reports/User_preferences/Configuration>, it looks like ""gender"", ""language"", and ""skin"" would be the easiest targets next. If anyone would prefer to close this task as resolved and file new tasks for additions to the whitelisted user properties list, I'm fine with that.
+
+AFAICS, and as noted in this task's description, the user_properties table already contains ""preferences that are considered to be public"", such as the ones you mentioned.
+
+Just tried:
+```lang=sql
+SELECT up_value FROM user_properties INNER JOIN user ON user_id = up_user AND user_name = 'Ricordisamoa' AND up_property = 'gender';
+```",1426553237,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"It was `user_properties_anonym` on the Toolserver and it's `user_properties_anon` now. Probably doesn't really matter, just noting.
+
+Thank you for <https://gerrit.wikimedia.org/r/197055>!
+
+Looking at <https://en.wikipedia.org/wiki/Wikipedia:Database_reports/User_preferences/Configuration>, it looks like ""gender"", ""language"", and ""skin"" would be the easiest targets next. If anyone would prefer to close this task as resolved and file new tasks for additions to the whitelisted user properties list, I'm fine with that.",1426549384,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Change 197055 merged by coren:
+Update maintain-replicas
+
+[[https://gerrit.wikimedia.org/r/197055]]",1426519887,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"The view has been created (on all but size 1 wikis) but the timestamps currently return NULL because none of the user_touched values are on the replicas at this time (they are redundantly nulled during replication and in the views).
+",1426519618,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Change 197055 had a related patch set uploaded (by coren):
+Update maintain-replicas
+
+[[https://gerrit.wikimedia.org/r/197055]]
+",1426519411,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#1120423, @MZMcBride wrote:
+> Can we start with ""gadget-*"" and then decide on the others in a separate future task?
+
+Sounds like a reasonable first pass.  I'll have to do some testing to see if wildcard matching is sufficiently efficient for the view to be usable; but otherwise I'll collect the existing gadget- names and use those as our first whitelist.",1426511590,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#1109452, @coren wrote:
+> The one thing I am missing to implement this at this time is either
+> (a) the whitelist of properties to collate or
+> (b) the method by which that whitelist is generated.
+
+Can we start with ""gadget-*"" and then decide on the others in a separate future task?",1426468431,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"The one thing I am missing to implement this at this time is either
+(a) the whitelist of properties to collate or
+(b) the method by which that whitelist is generated.
+",1426083857,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"A brief summary of past discussion and verification that we understood each other.
+
+A database view with a whitelisted set of keys is available with connections to individual accounts (`fancysig`, `language`, `nickname`, `timecorrection`, etc.). This information is already available by other means and is provided as convenience to perform queries on. This database view has since been created!
+
+An anonymised database view will be created as follows:
+* `up_user`: omit. This view will not associate preferences with users.
+* `up_property`: included. As was Toolserver, the set of properties exposed may be quite large and controlled by a whitelist (to avoid exposing new sensitive properties by accident). The whitelist includes wildcard patterns for things like `gadget-*`.
+* `up_value`: included.
+* `_user_touched_cropped`: generated based on `user.user_touched` value where `user.user_id = up_user`. Trimmed to YYYY-MM. Values for the current month are displayed as last month's.
+
+
+The reason the current month is displayed as last month's is to reduce chances of identifying users via their activity at the start of a month (which is not limited by the size of a wiki). This because using timestamps of YYYY-MD essentially reset every month. This in contrary to Special:ActiveUsers, which rolls continuously using relative timespan of ""last 30 days"". Without this modification, one could link a recently active user on a wiki at the start of a month. This modification would extend that timeframe from mere seconds to two full months (a user would have to be the only one active for two months). Note that this is for a timespan for two months, not one. Is that acceptable or should be still disable this view on small wikis? (Toolserver had it enabled for all wikis.)",1419127106,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"There are, in essence, two steps.  The underlying table needs to be replicated, and a view need to be created to it.
+
+Access to the underlying table is already there (it is used to provide the view into limited number of keys); all that is needed is the creation of a new view that carefully aggregates the data and respects the size limits, etc.
+
+The script that creates the views is there:
+
+https://git.wikimedia.org/blob/operations%2Fsoftware/HEAD/maintain-replicas%2Fmaintain-replicas.pl
+
+I'm usually the one who creates views, but my schedule is a bit on the buried side.  I'd be happy to review a patch adding the view - look starting line 90, it should be fairly evident how to add one.
+",1418343424,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,">>! In T60196#630652, @LuisV_WMF wrote:
+> If the users are OK with the month-filtered view, and exclusion of small wikis, that seems like a workable compromise to me.
+
+Okay, this sounds like sign-off to me.
+
+Who does this typically? @coren or @Springle? Is there documentation for what's needed to add/remove a database table or column from Labs' views? I vaguely remember there now being two filters in place, maybe.
+
+If anyone has links to the code repos or documentation (or even another task where we did something similar), that would likely help move this forward. At this point, it sounds like there's general consensus to move forward, this just hasn't been written out and gone through Gerrit/code review.",1418341468,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #51)
+> If the users are OK with the month-filtered view, and exclusion of small
+> wikis, that seems like a workable compromise to me.
+
+Well to speed up the process and keep compatibility at the same time, it would be better to add the view now, with YYYYMMDD rewritten as YYYYMM01 on larger wikis, and as 19700101 on small wikis, and we can keep discussing afterwards...",1402676577,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"If the users are OK with the month-filtered view, and exclusion of small wikis, that seems like a workable compromise to me.",1402600465,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Silke Meyer (WMDE) from comment #49)
+> * As far as we know, ""live"" tools depended on #64115 (filtered view) which
+> has been resolved. But no live tools seem to depend on this one. Please
+> correct me, if I am wrong!
+
+http://toolserver.org/~liangent/gadget_usage/",1402560424,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Summary of what was discussed during office hour (https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-office/20140611.txt, from [17:17:25] on):
+
+* This will probably take longer for WMF Legal, so it's unlikely that it will be done before Toolserver shutdown.
+* As far as we know, ""live"" tools depended on #64115 (filtered view) which has been resolved. But no live tools seem to depend on this one. Please correct me, if I am wrong!
+
+Still, it would be interesting to get an update from Luis. :)",1402557988,PHID-USER-qqgzlefcbycpok45pchr,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Hi Luis, do the comments 46 and 47 provide the answers you need? If not, who can help? We are ... sort of in a hurry by now.",1402504494,PHID-USER-qqgzlefcbycpok45pchr,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Active editors are not the only users changing preferences on a wiki, there are also many global users changing preferences everywhere (or in many places); only user_touched knows that.",1401947943,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Hi Luis, thanks for the update.
+
+(In reply to Krinkle from comment #40)
+> 
+> To avoid strange statistical variance like that, I'd recommend making
+> timestamp of the currently running month appear as last month's. That way no
+> data is excluded. This seems like a simple enough variance that tools should
+> be able to work with without much hassle.
+
+I think it is good solution. The timestamp is used mainly for filtering active vs non-active users.
+
+
+(In reply to Luis Villa (WMF Legal) from comment #42)
+> (In reply to Tisza Gergő from comment #35)
+> > Maybe instead of a live view, this table could be generated by a query which
+> > runs at the end of the day; that way no information is leaked by the timing
+> > of the change. Although that still does not solve the issue for small wikis
+> > since we probably want to run it more often than once a month.
+> 
+> If we only provide one month granularity in the answer, then it can be run
+> only once a month, right? Sounds like the use cases here don't need
+> precise/fine-grained answers to this question?
+
+*My use case: the user_properties_anonym table is used for generating[[meta:Gadgets]] - statistics on the most popular gadgets accross Wikimedia projects.
+* (other example for use case) User preferences statistics are provided by MZMcBride in [[en:Wikipedia:Database reports/User preferences]]
+So I belive one month resolution is fine for statistics use cases, and running it once a month could be enougth.
+As Krinkle wrote above, month resolution (YYYY-MM) make it hard to associate it to specific user.
+
+
+However for very very small wikis I think it isn't possible to provide such statistics: refering to http://stats.wikimedia.org/EN/TablesWikipediansEditsGt5.htm (Wikipedias by active users) some languages such as Tsonga or Oromo have only one active user. I think there should be a threshold on the number of active users in a wiki.",1401919915,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Current status of the bug is ""questions have been posed about privacy concerns"". It would be helpful to have feedback from people who use the field; in particular, my question in comment 42 and response to Krinkle's last statement in comment 40 would be good.",1401906930,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Changing to major per previous comment.,1401888473,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"What is the current status of the bug?
+It becomes very importantly to fix it in the very soon future, as the toolserver is going to be down in 3 weeks
+
+http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2014-June/000722.html",1401882015,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Tisza Gergő from comment #35)
+> Maybe instead of a live view, this table could be generated by a query which
+> runs at the end of the day; that way no information is leaked by the timing
+> of the change. Although that still does not solve the issue for small wikis
+> since we probably want to run it more often than once a month.
+
+If we only provide one month granularity in the answer, then it can be run only once a month, right? Sounds like the use cases here don't need precise/fine-grained answers to this question?",1399486602,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"> To avoid strange statistical variance like that, I'd recommend making timestamp of the currently running month appear as last month's.
+
+I don't see how that would help (other than making the window of opportunity smaller). You could still poll the data on the first day of the month to get an accurate edit timestamp. Since the attack is based on reading *when* the timestamp changes and correlating that with edit times, *what* the timestamp changes to is irrelevant. If you want users of the table to have a precision of T, you could protect users who edit more often than T by setting the timestamps to some deterministically chosen point within T so that changes within that interval are suppressed, but information would still leak about users who edit less often. For T = 1 day, that's hardly acceptable, even on large wikis.
+
+We could randomize the last few bits of the date, that would make it hard to tell when it changes, but it would still be doable via statistical means... really the only reliable way to mitigate this is to use a temporary table instead of a view, and only update it once a day/week/whatever so that the timing of the field changing becomes completely disconnected from the timing of the edit.",1399262606,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Tim Landscheidt from comment #39)
+> (In reply to Krinkle from comment #38)
+> > [...]
+> 
+> > In theory this could still be exploited by being a patient person and
+> > waiting for the moment one month has ended. Then the first user to become
+> > active in the new month would be the only person with a newer month
+> > timestamp.
+> 
+> > [...]
+> 
+> Could this be mitigated by excluding data for the current month?
+
+Essentially, yes. See my comment 17:
+
+(citing comment #17 from Krinkle)
+> [..] no matter how much we crop the timestamp (even if we'd crop it to the
+> month or year), one could in theory still retrieve the preferences of one
+> user by performing queries in a loop until the next day, month or year
+> starts and correlate that to the one user currently editing on that wiki..
+>
+> The only way I can think of that would mitigate that is forcing the current
+> matching crop of the date being delayed (e.g. all users active today on
+> 2014-03-17 would be listed under 2014-03-16 until this day is over, so that
+> all active users have had a chance to be active that day).
+
+However ""excluding data"" isn't trivial. It'll make statistics and sum queries act very counter intuitive. If you'd exclude all rows where timestamp == current YYYY-MM, that would essentially hide all values of active users, and make them re-appear next month and back and forth like that.
+
+To avoid strange statistical variance like that, I'd recommend making timestamp of the currently running month appear as last month's. That way no data is excluded. This seems like a simple enough variance that tools should be able to work with without much hassle.",1399258655,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Krinkle from comment #38)
+> [...]
+
+> In theory this could still be exploited by being a patient person and
+> waiting for the moment one month has ended. Then the first user to become
+> active in the new month would be the only person with a newer month
+> timestamp.
+
+> [...]
+
+Could this be mitigated by excluding data for the current month?",1399252416,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Changing the timestamp in this table based on wiki size would be a mistake in my opinion. It would make the data too arbitrary and hard to maintain. It also probably won't scale well into the MySQL mapping and relevant configuration.
+
+The reason we don't want to provide the full timestamp is because it exposes rather detailed information that would be trivial to map to an individual on most wikis (even large wikis) based on when an edit has happened.
+
+Shortening this to a month minimised this ability greatly, reducing it to only being able to tell that those with the current month as their last-active timestamp (YYYY-MM) are one of the users listed on Special:ActiveUsers.
+
+In theory this could still be exploited by being a patient person and waiting for the moment one month has ended. Then the first user to become active in the new month would be the only person with a newer month timestamp.
+
+For this particular exploit it is irrelevant how much we crop the timestamp (year, month, date, it's all the same, it only reduces how often one can make such attempt and with that the usefulness the data in the first place).
+
+If we consider that possibility important enough to warrant a solution, then that solution will work equally for year, month and day. I don't think there is any reason to trim it further than month, nor is there any reason to bring small/medium/large into the balance.",1399244062,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Small/medium/big wikis have 10/100/1000 thousands total pages or more. You can see the lists at https://noc.wikimedia.org/conf/ The lists were originally made as rough indication of how expensive certain heavy database operations are (you can easily find the bugs in question).,1399223320,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #34)
+> Sorry for the slow response, Liangent - email slipped through the cracks for
+> some reason. Q: what's the criteria for small/medium/large? And how often is
+> that updated? 
+
+I have no idea about the criteria, but I guess generally wikis only grow larger, and if the list is not updated in time, we're just anonymizing more, not less.",1399210199,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Tisza Gergő from comment #33)
+> As for timestamp anonimization, showing the (truncated) date of the last
+> edit of the user which did not happen in the current day(/month/year) should
+> be pretty straightforward.
+
+Nevermind, I see this comes from user_touched, not the edit log, and we do not keep a past record of that.
+
+Maybe instead of a live view, this table could be generated by a query which runs at the end of the day; that way no information is leaked by the timing of the change. Although that still does not solve the issue for small wikis since we probably want to run it more often than once a month.",1398906049,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Sorry for the slow response, Liangent - email slipped through the cracks for some reason. Q: what's the criteria for small/medium/large? And how often is that updated? 
+
+And Gergo's q is a good one too.",1398903291,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Is the order of rows randomized? Being able to correlate other preferences with, say, fancysig based on row number would be bad.
+
+As for timestamp anonimization, showing the (truncated) date of the last edit of the user which did not happen in the current day(/month/year) should be pretty straightforward.",1398899591,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #31)
+> So, let's keep this bug focused on the question of the ""anonymized"" table;
+> i.e., the table that currently has most (but not all) rows, with userID
+> removed but last active timestamp available. 
+> 
+> The current proposal is to provide this table on labs. It has also been
+> suggested that:
+> 
+> 1) we remove the whitelist altogether and provide everything; and/or
+> 2) we sample down the timestamp to YYYY-MM so that it is more difficult to
+> map ""last active"" to editors on small wikis.
+> 
+> I still have a few concerns:
+> 
+> 1) I still don't know how we created the original whitelist, or how we plan
+> to create the new one. (Note that if we trust our anonymization, having a
+> whitelist probably isn't necessary.)
+
+Note that some user_properties rows are not actually preferences. eg. watchlisttoken.
+
+> 
+> 2) I'm still concerned about the impact on anonymity of small wikis.
+> Rounding to months helps, but could still be problematic in at least some
+> cases (as Krinkle pointed out).
+
+So ... wikis are already grouped as small, medium and large, then YYYYMMDD in large, YYYYMM in medium and YYYY in small wikis?
+
+https://noc.wikimedia.org/conf/highlight.php?file=large.dblist
+https://noc.wikimedia.org/conf/highlight.php?file=medium.dblist
+https://noc.wikimedia.org/conf/highlight.php?file=small.dblist
+
+> I do not have a great solution to these questions. Trying to
+> brainstorm/think out loud here: maybe we could provide aggregate totals for
+> all editors, for active editors, and for new editors (based on the standard
+> analytics definition of active editors/new editors), instead of access to
+> individually anonymized rows?",1397868671,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"So, let's keep this bug focused on the question of the ""anonymized"" table; i.e., the table that currently has most (but not all) rows, with userID removed but last active timestamp available. 
+
+The current proposal is to provide this table on labs. It has also been suggested that:
+
+1) we remove the whitelist altogether and provide everything; and/or
+2) we sample down the timestamp to YYYY-MM so that it is more difficult to map ""last active"" to editors on small wikis.
+
+I still have a few concerns:
+
+1) I still don't know how we created the original whitelist, or how we plan to create the new one. (Note that if we trust our anonymization, having a whitelist probably isn't necessary.)
+
+2) I'm still concerned about the impact on anonymity of small wikis. Rounding to months helps, but could still be problematic in at least some cases (as Krinkle pointed out).
+
+I do not have a great solution to these questions. Trying to brainstorm/think out loud here: maybe we could provide aggregate totals for all editors, for active editors, and for new editors (based on the standard analytics definition of active editors/new editors), instead of access to individually anonymized rows?",1397862031,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"I'm cloning this bug so that we can have two discussions - one about the anonymized data, one about the filtered data. The discussion about a filtered view (with the handful of properties described in the original bug description and in comment #23) is now in bug 64115. I will continue the other discussion in my next comment.",1397861019,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"FYI, a ""ghost infrastructure"" makes this data available to select users, per http://lists.wikimedia.org/pipermail/analytics/2014-April/001768.html : folks should/can ask [[wikitech:EventLogging]] access if they need it.",1396991344,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,ASSIGNED != pending,1396617774,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"There's no reason to change the status of the bug, it remains pending an all-clear from Legal and a short implementation away.",1396616976,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to silke.meyer from comment #24)
+> Hello! What's the status on this?
+
+No movement in 4 months: resetting status.",1396616836,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,*** Bug 56491 has been marked as a duplicate of this bug. ***,1396616715,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Hello! What's the status on this?,1395998164,PHID-USER-qqgzlefcbycpok45pchr,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #22)
+> To confirm: INTERSECT here is the whitelist; DIFF 1 is properties that never
+> made it onto the whitelist?
+
+That is correct.
+
+INTERSECT are properties present in both Toolserver's anonymized view and in wikimedia production databases.
+
+DIFF 1 are properties present in production and not visible in Toolserver anonymized view.
+
+DIFF 2 are properties only present in Toolserver's anonymized view (none).
+
+
+The Toolserver's non-anonimized filtered view has a much stricter whitelist:
+
+nlwiki_p at toolserver> SELECT DISTINCT(up_property) FROM user_properties;
++----------------+
+| up_property    |
++----------------+
+| disablemail    |
+| fancysig       |
+| gender         |
+| language       |
+| nickname       |
+| skin           |
+| timecorrection |
+| variant        |
++----------------+
+8 rows in set",1395951431,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,To confirm: INTERSECT here is the whitelist; DIFF 1 is properties that never made it onto the whitelist?,1395678287,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Comparison for nlwiki.
+
+nlwiki at wmf> DISTINCT(up_property) FROM user_properties
++--------------------------------------------+
+| ajaxsearch
+| autopatrol
+| betafeatures-auto-enroll
+| betafeatures-geonotahack
+| betafeatures-vector-typography-update
+| ccmeonemails
+| cirrussearch-default
+| cols
+| contextchars
+| contextlines
+| date
+| diffonly
+| disablemail
+| disablesuggest
+| echo-email-format
+| echo-email-frequency
+| echo-email-last-batch
+| echo-show-alert
+| echo-subscriptions-email-article-linked
+| echo-subscriptions-email-edit-thank
+| echo-subscriptions-email-education-program
+| echo-subscriptions-email-mention
+| echo-subscriptions-email-reverted
+| echo-subscriptions-web-article-linked
+| echo-subscriptions-web-edit-thank
+| echo-subscriptions-web-education-program
+| echo-subscriptions-web-mention
+| echo-subscriptions-web-reverted
+| editfont
+| editondblclick
+| editsection
+| editsectionondblclick
+| editsectiononrightclick
+| editwidth
+| enotifminoredits
+| enotifrevealaddr
+| enotifusertalkpages
+| enotifwatchlistpages
+| ep_bulkdelcourses
+| ep_bulkdelorgs
+| ep_showdyk
+| ep_showtoplink
+| extendwatchlist
+| externaldiff
+| externaleditor
+| fancysig
+| forceeditsummary
+| gadget-Achtergrondkleur
+| gadget-Berichtbalk
+| gadget-Diffkleuren
+| gadget-Direct-link-to-Commons
+| gadget-Externe_links
+| gadget-Extra_bewerkingsknoppen
+| gadget-Geavanceerde_bijdragen
+| gadget-GoogleTrans
+| gadget-HideFundraiser
+| gadget-HotCat
+| gadget-IProject
+| gadget-LocalLiveClock
+| gadget-Navigatie_popups
+| gadget-OldDiff
+| gadget-OpenStreetMapFrame
+| gadget-OpenStreetMapFrameUit
+| gadget-ProtectionTemplates
+| gadget-ReferenceTooltips
+| gadget-Sneltoetsen
+| gadget-Twinkle
+| gadget-UTCLiveClock
+| gadget-Uitleg_verwijderlijst
+| gadget-VectorSearchNav
+| gadget-Verbergding
+| gadget-WhatLeavesHere
+| gadget-Zeusmodus
+| gadget-fixhoofdbetekenis
+| gadget-hoofdbetekenis-titelwijziging
+| gadget-labelfilter
+| gadget-mijnKladblok
+| gadget-purgelink
+| gadget-searchFocus
+| gadget-updatemarker
+| gadget-verwijderreden
+| gender
+| hideminor
+| hidepatrolled
+| highlightbroken
+| hover
+| imagesize
+| justify
+| language
+| math
+| mfWatchlistFilter
+| mfWatchlistView
+| minordefault
+| moodbar-disable
+| multimedia-viewer
+| newpageshidepatrolled
+| nickname
+| nocache
+| norollbackdiff
+| numberheadings
+| prefershttps
+| previewonfirst
+| previewontop
+| quickbar
+| rcdays
+| rclimit
+| rcshowwikidata
+| rememberpassword
+| rows
+| searchNs-1
+| searchNs0
+| searchNs1
+| searchNs10
+| searchNs100
+| searchNs101
+| searchNs11
+| searchNs12
+| searchNs13
+| searchNs14
+| searchNs15
+| searchNs2
+| searchNs3
+| searchNs4
+| searchNs4294967295
+| searchNs446
+| searchNs447
+| searchNs5
+| searchNs6
+| searchNs7
+| searchNs8
+| searchNs828
+| searchNs829
+| searchNs9
+| searcheverything
+| searchlimit
+| showhiddencats
+| showjumplinks
+| shownumberswatching
+| showtoc
+| showtoolbar
+| skin
+| stubthreshold
+| thumbsize
+| timecorrection
+| uls-compact-links
+| uls-enable
+| uls-preferences
+| underline
+| usebetatoolbar
+| usebetatoolbar-cgd
+| useeditwarning
+| uselivepreview
+| usenewrc
+| userjs-already-set-common-preferences
+| variant
+| vector-collapsiblenav
+| vector-noexperiments
+| vector-simplesearch
+| visualeditor-betatempdisable
+| visualeditor-enable
+| visualeditor-enable-mwmath
+| watchcreations
+| watchdefault
+| watchdeletion
+| watchlistdays
+| watchlisthideanons
+| watchlisthidebots
+| watchlisthideliu
+| watchlisthideminor
+| watchlisthideown
+| watchlisthidepatrolled
+| watchlisttoken
+| watchmoves
+| wllimit
+| wlshowwikibase
++--------------------------------------------+
+176 rows in set (4.95 sec)
+
+nlwiki_p at toolserver> DISTINCT(up_property) FROM user_properties_anonym
++-----------------------------------------+
+| up_property
++-----------------------------------------+
+| ajaxsearch
+| autopatrol
+| ccmeonemails
+| cols
+| contextchars
+| contextlines
+| date
+| diffonly
+| disablemail
+| disablesuggest
+| echo-email-format
+| echo-email-frequency
+| echo-show-alert
+| echo-subscriptions-email-article-linked
+| echo-subscriptions-email-edit-thank
+| echo-subscriptions-email-mention
+| echo-subscriptions-email-reverted
+| echo-subscriptions-web-article-linked
+| echo-subscriptions-web-edit-thank
+| echo-subscriptions-web-mention
+| echo-subscriptions-web-reverted
+| editfont
+| editondblclick
+| editsection
+| editsectiononrightclick
+| editwidth
+| enotifminoredits
+| enotifrevealaddr
+| enotifusertalkpages
+| enotifwatchlistpages
+| extendwatchlist
+| externaldiff
+| externaleditor
+| fancysig
+| forceeditsummary
+| gadget-Achtergrondkleur
+| gadget-Berichtbalk
+| gadget-Diffkleuren
+| gadget-Direct-link-to-Commons
+| gadget-Externe_links
+| gadget-Extra_bewerkingsknoppen
+| gadget-fixhoofdbetekenis
+| gadget-Geavanceerde_bijdragen
+| gadget-GoogleTrans
+| gadget-HideFundraiser
+| gadget-hoofdbetekenis-titelwijziging
+| gadget-HotCat
+| gadget-IProject
+| gadget-labelfilter
+| gadget-LocalLiveClock
+| gadget-mijnKladblok
+| gadget-Navigatie_popups
+| gadget-OldDiff
+| gadget-OpenStreetMapFrame
+| gadget-OpenStreetMapFrameUit
+| gadget-ProtectionTemplates
+| gadget-purgelink
+| gadget-ReferenceTooltips
+| gadget-searchFocus
+| gadget-Sneltoetsen
+| gadget-Twinkle
+| gadget-Uitleg_verwijderlijst
+| gadget-updatemarker
+| gadget-UTCLiveClock
+| gadget-VectorSearchNav
+| gadget-Verbergding
+| gadget-verwijderreden
+| gadget-WhatLeavesHere
+| gadget-Zeusmodus
+| gender
+| hideminor
+| hidepatrolled
+| highlightbroken
+| hover
+| imagesize
+| justify
+| language
+| math
+| minordefault
+| newpageshidepatrolled
+| nocache
+| norollbackdiff
+| numberheadings
+| previewonfirst
+| previewontop
+| quickbar
+| rcdays
+| rclimit
+| rememberpassword
+| searcheverything
+| searchlimit
+| searchNs-1
+| showhiddencats
+| showjumplinks
+| shownumberswatching
+| showtoc
+| showtoolbar
+| skin
+| stubthreshold
+| thumbsize
+| timecorrection
+| underline
+| usebetatoolbar
+| usebetatoolbar-cgd
+| useeditwarning
+| uselivepreview
+| usenewrc
+| variant
+| vector-noexperiments
+| visualeditor-enable
+| watchcreations
+| watchdefault
+| watchdeletion
+| watchlistdays
+| watchlisthideanons
+| watchlisthidebots
+| watchlisthideliu
+| watchlisthideminor
+| watchlisthideown
+| watchlisthidepatrolled
+| watchmoves
+| wllimit
++-----------------------------------------+
+122 rows in set (51.05 sec)
+
+INTERSECT: 
+
+| ajaxsearch
+| autopatrol
+| ccmeonemails
+| cols
+| contextchars
+| contextlines
+| date
+| diffonly
+| disablemail
+| disablesuggest
+| echo-email-format
+| echo-email-frequency
+| echo-show-alert
+| echo-subscriptions-email-article-linked
+| echo-subscriptions-email-edit-thank
+| echo-subscriptions-email-mention
+| echo-subscriptions-email-reverted
+| echo-subscriptions-web-article-linked
+| echo-subscriptions-web-edit-thank
+| echo-subscriptions-web-mention
+| echo-subscriptions-web-reverted
+| editfont
+| editondblclick
+| editsection
+| editsectiononrightclick
+| editwidth
+| enotifminoredits
+| enotifrevealaddr
+| enotifusertalkpages
+| enotifwatchlistpages
+| extendwatchlist
+| externaldiff
+| externaleditor
+| fancysig
+| forceeditsummary
+| gadget-Achtergrondkleur
+| gadget-Berichtbalk
+| gadget-Diffkleuren
+| gadget-Direct-link-to-Commons
+| gadget-Externe_links
+| gadget-Extra_bewerkingsknoppen
+| gadget-Geavanceerde_bijdragen
+| gadget-GoogleTrans
+| gadget-HideFundraiser
+| gadget-HotCat
+| gadget-IProject
+| gadget-LocalLiveClock
+| gadget-Navigatie_popups
+| gadget-OldDiff
+| gadget-OpenStreetMapFrame
+| gadget-OpenStreetMapFrameUit
+| gadget-ProtectionTemplates
+| gadget-ReferenceTooltips
+| gadget-Sneltoetsen
+| gadget-Twinkle
+| gadget-UTCLiveClock
+| gadget-Uitleg_verwijderlijst
+| gadget-VectorSearchNav
+| gadget-Verbergding
+| gadget-WhatLeavesHere
+| gadget-Zeusmodus
+| gadget-fixhoofdbetekenis
+| gadget-hoofdbetekenis-titelwijziging
+| gadget-labelfilter
+| gadget-mijnKladblok
+| gadget-purgelink
+| gadget-searchFocus
+| gadget-updatemarker
+| gadget-verwijderreden
+| gender
+| hideminor
+| hidepatrolled
+| highlightbroken
+| hover
+| imagesize
+| justify
+| language
+| math
+| minordefault
+| newpageshidepatrolled
+| nocache
+| norollbackdiff
+| numberheadings
+| previewonfirst
+| previewontop
+| quickbar
+| rcdays
+| rclimit
+| rememberpassword
+| searchNs-1
+| searcheverything
+| searchlimit
+| showhiddencats
+| showjumplinks
+| shownumberswatching
+| showtoc
+| showtoolbar
+| skin
+| stubthreshold
+| thumbsize
+| timecorrection
+| underline
+| usebetatoolbar
+| usebetatoolbar-cgd
+| useeditwarning
+| uselivepreview
+| usenewrc
+| variant
+| vector-noexperiments
+| visualeditor-enable
+| watchcreations
+| watchdefault
+| watchdeletion
+| watchlistdays
+| watchlisthideanons
+| watchlisthidebots
+| watchlisthideliu
+| watchlisthideminor
+| watchlisthideown
+| watchlisthidepatrolled
+| watchmoves
+| wllimit
+
+DIFF 1: 
+| betafeatures-auto-enroll
+| betafeatures-geonotahack
+| betafeatures-vector-typography-update
+| cirrussearch-default
+| echo-email-last-batch
+| echo-subscriptions-email-education-program
+| echo-subscriptions-web-education-program
+| editsectionondblclick
+| ep_bulkdelcourses
+| ep_bulkdelorgs
+| ep_showdyk
+| ep_showtoplink
+| mfWatchlistFilter
+| mfWatchlistView
+| moodbar-disable
+| multimedia-viewer
+| nickname
+| prefershttps
+| rcshowwikidata
+| rows
+| searchNs0
+| searchNs1
+| searchNs10
+| searchNs100
+| searchNs101
+| searchNs11
+| searchNs12
+| searchNs13
+| searchNs14
+| searchNs15
+| searchNs2
+| searchNs3
+| searchNs4
+| searchNs4294967295
+| searchNs446
+| searchNs447
+| searchNs5
+| searchNs6
+| searchNs7
+| searchNs8
+| searchNs828
+| searchNs829
+| searchNs9
+| uls-compact-links
+| uls-enable
+| uls-preferences
+| userjs-already-set-common-preferences
+| vector-collapsiblenav
+| vector-simplesearch
+| visualeditor-betatempdisable
+| visualeditor-enable-mwmath
+| watchlisttoken
+| wlshowwikibase
+
+DIFF 2: 
+
+(none)",1395206347,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Do we know how that whitelist was created?,1395164140,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #18)
+> (In reply to Krinkle from comment #17)
+> > So if I understand correctly, the whitelist of properties you approved in
+> > comment 12 are in fact allowed for identifiable queries (e.g. with
+> > user_id/user name attached to it), as opposed to the anonymized view.
+> 
+> Yes, that is correct, for those categories. 
+> 
+> As far as implementation, we'll want to review new fields as they are added,
+> which is why I prefer a whitelist approach (review what is released; hard to
+> accidentally release data accidentally) to a blacklist approach (review what
+> is not released; easy to release data accidentally by not adding it to the
+> blacklist).
+> 
+> > And when you say ""OK in principle"" for the anonymized view, that means all
+> > properties?
+> 
+> Yes, based on my understanding that they are already available on toolserver
+> in user_properties_anonym and/or via the API. If they aren't already public
+> (via API or toolserver) we should probably review one-by-one, and/or do a
+> more careful scrutiny of the anonymization procedures. Maybe that deserves a
+> separate bug?
+
+anonym on Toolserver is also whitelist based. I don't have access to the original list ts_global.user_properties_anonym_whilelist, but it's possible to sniff it with select distinct up_property from user_properties_anonym; (a slow query).",1395104663,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Krinkle from comment #17)
+> So if I understand correctly, the whitelist of properties you approved in
+> comment 12 are in fact allowed for identifiable queries (e.g. with
+> user_id/user name attached to it), as opposed to the anonymized view.
+
+Yes, that is correct, for those categories. 
+
+As far as implementation, we'll want to review new fields as they are added, which is why I prefer a whitelist approach (review what is released; hard to accidentally release data accidentally) to a blacklist approach (review what is not released; easy to release data accidentally by not adding it to the blacklist).
+
+> And when you say ""OK in principle"" for the anonymized view, that means all
+> properties?
+
+Yes, based on my understanding that they are already available on toolserver in user_properties_anonym and/or via the API. If they aren't already public (via API or toolserver) we should probably review one-by-one, and/or do a more careful scrutiny of the anonymization procedures. Maybe that deserves a separate bug?",1395101959,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"So if I understand correctly, the whitelist of properties you approved in comment 12 are in fact allowed for identifiable queries (e.g. with user_id/user name attached to it), as opposed to the anonymized view. That's great news. I wasn't expecting a non-anonymized view of the properties table at all. Having one with this limited set of properties can be useful indeed.
+
+And when you say ""OK in principle"" for the anonymized view, that means all properties?
+
+Good point on the user activity measure being potentially identifying on small wikis. I suppose a month crop of the timestamp (YYYY-MM) would still be good enough for practical applications and be a lot less likely to reveal identifying information.
+
+Though no matter how much we crop the timestamp (even if we'd crop it to the month or year), one could in theory still retrieve the preferences of one user by performing queries in a loop until the next day, month or year starts and correlate that to the one user currently editing on that wiki.. The only way I can think of that would mitigate that is forcing the current matching crop of the date being delayed (e.g. all users active today on 2014-03-17 would be listed under 2014-03-16 until this day is over, so that all active users have had a chance to be active that day).",1395017899,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Retitling then :) 
+
+For the filtered table: I am OK with this in principle, but would like to better understand (1) how we choose which fields to filter and (2) how we prevent new fields from leaking.
+
+For the anonymized table: Again, OK in principle; it would be good (but not a must-have) to know more about the impact on users of small wikis.",1394823426,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to Luis Villa (WMF Legal) from comment #14)
+> Ah! Thanks for explaining more clearly, Krinkle. The first comment now makes
+> a lot more sense to me :) 
+> 
+> One question on the anonymization - this data is still per-wiki, right?
+> Would last-active dates at the day-level allow deanonymization for those
+> users?
+
+Those are two different requests: one table (view) containing user identifiable info (user id) with fewer properties includes, and another anonymized one with more properties.",1394778923,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Ah! Thanks for explaining more clearly, Krinkle. The first comment now makes a lot more sense to me :) 
+
+One question on the anonymization - this data is still per-wiki, right? Would last-active dates at the day-level allow deanonymization for those users?",1394751837,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"I'm hoping we can get permission to provide this view on Tool Labs without a whitelist of keys like that and instead allow all, or at least a more liberal subset.
+
+The main request is to provide what Toolserver provided which is:
+
+An anonimized view of the user_properties table with an extra column that shows the date (not the time) of when the associated user was last active (which allows consumers of the data to focus on (or reject) recently active users vs. abandoned user accounts).
+
+The raw user_properties database in Wikimedia production contains:
+
+- up_user: The user_id of the user, this must of course not be exposed
+   because that would allow consumers of the data to know which preferences
+   belong to the same user, and in addition, since user ids are already public,
+   to also know which user it belongs to).
+
+- up_property: The preference names (disablemail, gender, language, skin, gadget-Foo, gadget-Bar etc.)
+
+- up_value: The value of the preference. For most preferences these are boolean values (0 of off, 1 for on). Others are one of a finite set of values (like ""language"" and ""skin""). And then there are some that take free numerical input (like ""rclimit"" which can be any number, e.g. 10 or 500, for the number of results to show by default on Special:Search or Special:RecentChanges). And lastly, there are some that take free textual input (like nickname and fancysig). This last category is usually identifying to a person. So I could understand why one might keep these hidden (though Luis already said those two were fine). I imagine it's fine because they're public (people use their signature and nickname all the time), and anonymised (not connected to other preferences of that same user).
+
+Of these, the anonimized view would expose:
+
+- up_property
+- up_value
+
+This will allow tools to know how popular certain preferences are (e.g. How many people use the Monobook skin, How many people change their interface language to French on German Wikipedia). I think however that this view should not be restricted to certain preferences. Especially because:
+
+ 1) Extensions and core add new preferences all the time.
+
+ 2) Gadgets are enabled through preferences as well, so if we do use a
+    whitelist, it should whitelist any preference starting with ""gadget-*"".
+
+ 3) BetaFeatures also comes and goes with new preferences.
+    The case of BetaFeatures is interesting, because it actually tracks
+    and exposes the usage of its own preferences publicly (doesn't even
+    require making a Tool of some kind).
+
+
+In addition to these two columns, it would be very useful to have some kind of indicator to interpret these values. Toolserver did this by adding a shadow column showing a trimmed part of the timestamp of when the associated user was last active (trimmed to only show the date in YYYY-MM-DD, not the exact time of day). With this, statistics about preferences are much more useful due to the large number of abandoned accounts polluting the results.
+
+Here's a query showing which keys are currently exposed in Toolserver's  user_properties_anonym table:
+
+krinkle at willow.toolserver.org$ sql nlwiki_p
+mysql> SELECT DISTINCT(up_property) FROM user_properties_anonym;
++-----------------------------------------+
+| up_property                             |
++-----------------------------------------+
+| ajaxsearch                              |
+| autopatrol                              |
+| ccmeonemails                            |
+| cols                                    |
+| contextchars                            |
+| contextlines                            |
+| date                                    |
+| diffonly                                |
+| disablemail                             |
+| disablesuggest                          |
+| echo-email-format                       |
+| echo-email-frequency                    |
+| echo-show-alert                         |
+| echo-subscriptions-email-article-linked |
+| echo-subscriptions-email-edit-thank     |
+| echo-subscriptions-email-mention        |
+| echo-subscriptions-email-reverted       |
+| echo-subscriptions-web-article-linked   |
+| echo-subscriptions-web-edit-thank       |
+| echo-subscriptions-web-mention          |
+| echo-subscriptions-web-reverted         |
+| editfont                                |
+| editondblclick                          |
+| editsection                             |
+| editsectiononrightclick                 |
+| editwidth                               |
+| enotifminoredits                        |
+| enotifrevealaddr                        |
+| enotifusertalkpages                     |
+| enotifwatchlistpages                    |
+| extendwatchlist                         |
+| externaldiff                            |
+| externaleditor                          |
+| fancysig                                |
+| forceeditsummary                        |
+| gadget-Achtergrondkleur                 |
+| gadget-Berichtbalk                      |
+| gadget-Diffkleuren                      |
+| gadget-Extra_bewerkingsknoppen          |
+| gadget-fixhoofdbetekenis                |
+| gadget-Geavanceerde_bijdragen           |
+| gadget-HideFundraiser                   |
+| gadget-HotCat                           |
+| gadget-IProject                         |
+| gadget-Navigatie_popups                 |
+| gadget-purgelink                        |
+| gadget-ReferenceTooltips                |
+| gadget-Twinkle                          |
+| gadget-UTCLiveClock                     |
+| gender                                  |
+| hideminor                               |
+| hidepatrolled                           |
+| highlightbroken                         |
+| hover                                   |
+| imagesize                               |
+| justify                                 |
+| language                                |
+| math                                    |
+| minordefault                            |
+| newpageshidepatrolled                   |
+| nocache                                 |
+| norollbackdiff                          |
+| numberheadings                          |
+| previewonfirst                          |
+| previewontop                            |
+| quickbar                                |
+| rcdays                                  |
+| rclimit                                 |
+| rememberpassword                        |
+| searcheverything                        |
+| searchlimit                             |
+| searchNs-1                              |
+| showhiddencats                          |
+| showjumplinks                           |
+| shownumberswatching                     |
+| showtoc                                 |
+| showtoolbar                             |
+| skin                                    |
+| stubthreshold                           |
+| thumbsize                               |
+| timecorrection                          |
+| underline                               |
+| usebetatoolbar                          |
+| usebetatoolbar-cgd                      |
+| useeditwarning                          |
+| uselivepreview                          |
+| usenewrc                                |
+| variant                                 |
+| vector-noexperiments                    |
+| visualeditor-enable                     |
+| watchcreations                          |
+| watchdefault                            |
+| watchdeletion                           |
+| watchlistdays                           |
+| watchlisthideanons                      |
+| watchlisthidebots                       |
+| watchlisthideliu                        |
+| watchlisthideminor                      |
+| watchlisthideown                        |
+| watchlisthidepatrolled                  |
+| watchmoves                              |
+| wllimit                                 |
++-----------------------------------------+
+102 rows in set
+
+
+Are there any preferences we would explicitly not want to expose?",1394750751,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Sorry, this got lost in the shuffle. To respond to Silke: I'm still not entirely clear which fields we're talking about replicating. If the list from en_wikip: 
+
++----------------+
+| up_property    |
++----------------+
+| disablemail    |
+| fancysig       |
+| gender         |
+| language       |
+| nickname       |
+| skin           |
+| timecorrection |
+| variant        |
++----------------+
+
+Is what we're actually talking about, then yes - no legal barrier to making that information available.",1394746288,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"The gender gap plots by emijrp also depends on this:
+
+https://toolserver.org/~emijrp/wmcharts/
+
+(they don't work atm. for some other reason)",1394745066,PHID-USER-53x4y44yt43qjivfzsqf,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #9)
+
+> Legoktm, which of your tools depends on this to migrate?
+
+Database reports, specifically [[Wikipedia:Database reports/User preferences]].",1391540347,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"So, am I right in assuming there is no legal barrier to make that table available? 
+Legoktm, which of your tools depends on this to migrate?",1391532830,PHID-USER-qqgzlefcbycpok45pchr,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #7)
+> Ah, didn't know that, thanks. Though, given that the AbuseFilter has been
+> giving out emailconfirmed timestamps (bug 20005), it's probably a moot point.
+
+That seems to me a good reason to fix 20005 more than anything (especially since that isn't in the dumps).",1387510467,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #6)
+> (In reply to comment #4)
+> > For example, if you go to Special:EmailUser, you can tell if a user has
+> > disabled email or not (disableemail).
+> 
+> That's not actually correct; you can know whether someone has disabled their
+> email /or/ never confirmed one to begin with (i.e.: it's emailconfirmed &&
+> !disableemail).
+
+Ah, didn't know that, thanks. Though, given that the AbuseFilter has been giving out emailconfirmed timestamps (bug 20005), it's probably a moot point.",1387505659,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #4)
+> For example, if you go to Special:EmailUser, you can tell if a user has
+> disabled email or not (disableemail).
+
+That's not actually correct; you can know whether someone has disabled their email /or/ never confirmed one to begin with (i.e.: it's emailconfirmed && !disableemail).",1387503916,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"If a field is already exposed by the API/website, then that's fine. Just wasn't clear which of those fields that was already true for.",1387503572,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"(In reply to comment #3)
+> Legoktm, when you say ""Only preferences that are considered to be public are
+> replicated, the list from enwiki_p is..."" is that the list of things
+> currently
+> considered public? Or the list of things that could be made public?
+
+Since it's already replicated onto the Toolserver, I assume they are currently considered to be public.
+
+For example, if you go to Special:EmailUser, you can tell if a user has disabled email or not (disableemail). fancysig/nickname are just a user's signature, which is public as soon as a user adds ~~~~ to any page. gender is also exposed by the software and the API.",1387503366,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"I don't think we've formally set out a policy that new field replication has to run through legal, but it's a good habit to be in.
+
+Legoktm, when you say ""Only preferences that are considered to be public are replicated, the list from enwiki_p is..."" is that the list of things currently considered public? Or the list of things that could be made public?",1387492207,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,Adding Luis Villa so that he can chime in.,1387480184,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+Tool Labs: Provide anonymized view of the user_properties table,"Coren says there's a requirement that the Wikimedia Foundation legal team sign off on changes of this nature. I'm not able to verify this requirement. The process seems to be largely undocumented, though as far as I'm aware, there was never any such requirement during the Toolserver's reign: it was merely left to root discretion.",1386566431,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ey2zjvufzkixpyfo3wvk,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Steps to reproduce:
+
+
+1.Open the editor for a page which contains a link
+2.Copy the link
+3.Now open VE for another article and paste the copied link onto it
+4.Save the page
+
+
+Observed Result:
+
+The copied link appears as a plain text on the read mode where as in the Edit Source/Edit mode it appears as a link
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58138",1386376320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_description,resolved
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",Verified the fix on test 2,1391132245,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 108954 merged by jenkins-bot:
+Relativise URLs against target document
+
+https://gerrit.wikimedia.org/r/108954",1390445932,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",Possibly now fixed. Hopefully.,1390442043,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 108953 had a related patch set uploaded by Krinkle:
+Resolve URLs against correct document when copying.
+
+https://gerrit.wikimedia.org/r/108953",1390424401,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 108954 had a related patch set uploaded by Esanders:
+Relativise URLs against target document
+
+https://gerrit.wikimedia.org/r/108954",1390421253,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",Sorry 16th January :),1390343484,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Ed, I tested it on 16th december(Last thursday) after the deployment on test2.So it should have been merged to test2 by that time right? Also, I am still getting it on test2",1390339282,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",The last fix was merged on 15th Jan. The test environment you point to says it is running code from 14th Jan. Please re-open if broken with master.,1390316590,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",*** Bug 59216 has been marked as a duplicate of this bug. ***,1390024188,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","The testing environment is test2, wmf 11.
+Broswer:Chrome/Firefox",1389901609,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","The issue described later in this bug still exists in test.Again giving the steps here:
+This issue is still occurring for following case:
+
+1.Open the editor for a page ""A"" which contains a link to another page ""B""
+2.Copy the link and Paste it into ""B""
+3.Save the page
+
+Observed Result:
+The link to the same page is appearing as plain text in the read mode.",1389901513,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 105706 merged by jenkins-bot:
+Support external links in MWInternalLinkAnnotation
+
+https://gerrit.wikimedia.org/r/105706",1389824850,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 106253 merged by jenkins-bot:
+Always use absolute URLs in external links in the clipboard
+
+https://gerrit.wikimedia.org/r/106253",1389641923,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 106253 had a related patch set uploaded by Esanders:
+Always use absolute URLs in external links in the clipboard
+
+https://gerrit.wikimedia.org/r/106253",1389191918,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 105706 had a related patch set uploaded by Esanders:
+Always use absolute URLs in external links in the clipboard
+
+https://gerrit.wikimedia.org/r/105706",1389028307,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","This issue is still occurring for following case:
+
+1.Open the editor for a page ""A"" which contains a link to another page ""B""
+2.Copy the link and Paste it into ""B""
+3.Save the page
+
+Observed Result:
+The link to the same page is appearing as plain text in the read mode.
+
+Found in :http://en.wikipedia.beta.wmflabs.org/wiki/The_paste_destination",1387397886,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=13th_december,1386984067,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",Verified in betalabs,1386790162,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)",A fix for this is going out in about 4 minutes' time. Sorry for the disruption.,1386633329,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 100493 merged by jenkins-bot:
+Only strip style attributes on rich paste from VE
+
+https://gerrit.wikimedia.org/r/100493",1386632961,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 100422 merged by jenkins-bot:
+Only strip style attributes on rich paste from VE
+
+https://gerrit.wikimedia.org/r/100422",1386629947,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 100493 had a related patch set uploaded by Jforrester:
+Only strip style attributes on rich paste from VE
+
+https://gerrit.wikimedia.org/r/100493",1386629891,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Change 100422 had a related patch set uploaded by Esanders:
+Only strip style attributes on rich paste from VE
+
+https://gerrit.wikimedia.org/r/100422",1386618650,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+"VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)","Page: Observe the second ""Edit source"" text on the page:
+http://en.wikipedia.beta.wmflabs.org/wiki/To_edit_source
+
+Test Environment: Betalabs
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5",1386376423,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nms5tkiqwi23vyk5dc7p,task_subcomment,NA
+VisualEditor:The icon for underline option is missing in betalabs,"screenshot
+
+The icon for underline option is missing in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/The_link?veaction=edit
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12362}",1386364620,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fk5w6cwyl6t7fo226qow,task_description,resolved
+VisualEditor:The icon for underline option is missing in betalabs,Verified,1386370145,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fk5w6cwyl6t7fo226qow,task_subcomment,NA
+VisualEditor:The icon for underline option is missing in betalabs,"Change 99755 merged by jenkins-bot:
+Followup 418f2606e03b82a5ae0afc853406c7e9f2d1e35f: put <?xml tag back.
+
+https://gerrit.wikimedia.org/r/99755",1386366847,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fk5w6cwyl6t7fo226qow,task_subcomment,NA
+VisualEditor:The icon for underline option is missing in betalabs,"Change 99755 had a related patch set uploaded by Catrope:
+Followup 418f2606e03b82a5ae0afc853406c7e9f2d1e35f: put <?xml tag back.
+
+https://gerrit.wikimedia.org/r/99755",1386366381,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fk5w6cwyl6t7fo226qow,task_subcomment,NA
+VisualEditor: <ooui-toolbar-more> is showing up instead of More button in betalabs,"Screenshot
+
+<ooui-toolbar-more> is showing up instead of More button in betalabs
+http://en.wikipedia.beta.wmflabs.org/wiki/6th_december?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12338}",1386356940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-du3trqyxzlr7pus3ud55,task_description,declined
+VisualEditor: <ooui-toolbar-more> is showing up instead of More button in betalabs,"Deployment bug, now fixed.",1386392274,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-du3trqyxzlr7pus3ud55,task_subcomment,NA
+VisualEditor: <ooui-toolbar-more> is showing up instead of More button in betalabs,"Created attachment 14009
+screenshot of the notification
+
+**Attached**: {F12339}",1386358017,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-du3trqyxzlr7pus3ud55,task_subcomment,NA
+VisualEditor: <ooui-toolbar-more> is showing up instead of More button in betalabs,"Also instead of the notification message after saving a page <visualeditor-notification-saved> is appearing.
+
+See the screenshot attached.",1386357987,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-du3trqyxzlr7pus3ud55,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),"**Author:** `Wikifram`
+
+**Description:**
+When you have made changes to a page in VE, you can use the ""undo"" button to reverse these. However, the page doesn't scroll when doing this, so you don't ""see"" what the undo is actually doing. The same probably applies to the ""redo"" button, I haven't checked that one
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51911",1386321060,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_description,resolved
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),This was probably fixed a while ago.,1456235332,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),"(In reply to Alex Monk from comment #3)
+> Dupe then?
+
+Doing it for the undo/redo stack is probably complicated, so I was leaving them distinct.",1415046177,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),Dupe then?,1415045955,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),"(In reply to Alex Monk from comment #1)
+> Hmm... Shouldn't this be a case of scrolling to the new location of the
+> cursor when you undo/redo?
+
+Pretty much, which is bug 51911.",1415045652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?),Hmm... Shouldn't this be a case of scrolling to the new location of the cursor when you undo/redo?,1414813862,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2lksrv5vv6rqnzdrzgxv,task_subcomment,NA
+"VisualEditor: Auto context links (#contentSub) under the title in the User: namespace is only hidden, not suppressed, so can still be clicked","Screenshot
+
+Steps to reproduce:
+
+1.Open the VE for a page in a User's namespace
+2.Hover your mouse over the position where the link to user namespace appears in the Read mode.
+3.Click on that position
+
+Observed Result:
+It redirects to user namespace from VE.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52243
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54325
+
+**Attached**: {F12247}",1386288540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bgaxa5whdy4rwfmma5hm,task_description,resolved
+"VisualEditor: Auto context links (#contentSub) under the title in the User: namespace is only hidden, not suppressed, so can still be clicked","Environment:Production (https://en.wikipedia.org/)
+Browser:Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5",1386288748,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bgaxa5whdy4rwfmma5hm,task_subcomment,NA
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted","Screenshot
+
+Steps to reproduce:
+
+1.Open the editor
+2.Place the cursor in the middle of a text
+3.Then click on More>Hieroglyphics
+4.The inspector does not open just the < icon in that position.
+5.Save the page
+6.Reopen the editor.
+
+
+Observed Result:
+The text after that cursor position gets shifted to the newline and a return arrow appears after reopening the editor.
+
+For a text which is not link it just goes to the next line but the return arrow does not get added.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12190}",1386269880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zzarel5lh2xkfhzr752t,task_description,resolved
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted","I believe that this is now fixed… can't really check any more, though.",1410033747,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zzarel5lh2xkfhzr752t,task_subcomment,NA
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted",While going to the next line it also adds an empty <hiero> tags in that position.,1386286227,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zzarel5lh2xkfhzr752t,task_subcomment,NA
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted","Test Environment: betalabs
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=The_something&veaction=edit",1386270837,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zzarel5lh2xkfhzr752t,task_subcomment,NA
+"VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted","Created attachment 13994
+Screenshot of the < appearing instead of the hieroglyphics inspector
+
+**Attached**: {F12191}",1386270471,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zzarel5lh2xkfhzr752t,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Screenshot
+
+Steps to reproduce:
+
+
+1.Open the editor.
+2.Select an image
+3.Select the option More>Latex/Hieroglyphics
+
+Observed Result:
+
+A small input window opens up over the window where text can be inserted.
+
+In the console I get the following error:
+Uncaught TypeError: Cannot read property 'body' of undefined load.php:521
+ve.ui.MWExtensionInspector.setup load.php:521
+(anonymous function) load.php:113
+proxy load.php:10
+listenerWrapper load.php:98
+oo.EventEmitter.emit load.php:98
+(anonymous function) load.php:110
+pollExternalStylesheets
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60804
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56644
+
+**Attached**: {F12183}",1386268980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_description,resolved
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies",Verified the fix in production,1398988445,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies",Verified the fix in test2,1398898363,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Change 129622 merged by jenkins-bot:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/129622",1398384373,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Change 129622 had a related patch set uploaded by Jforrester:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/129622",1398384262,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Change 126900 merged by jenkins-bot:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/126900",1397845436,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies","Change 126900 had a related patch set uploaded by Esanders:
+Create MWLiveExtensionInspector base class
+
+https://gerrit.wikimedia.org/r/126900",1397780745,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+"VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies",WFM,1397778331,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3x6ghzfmxd6n4cvw7pxm,task_subcomment,NA
+VisualEditor: Cursoring off the page with left/right doesn't scroll the cursor in to view,"Contrast with up/down which always keeps the cursor in view.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68708",1386258480,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sjbb3upxz7oa72molxbx,task_description,resolved
+VisualEditor: Cursoring off the page with left/right doesn't scroll the cursor in to view,Seems to work now. ,1443036355,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-sjbb3upxz7oa72molxbx,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"LQT intercepts section=new from users to add a new thread (but not via the API, see bug 41276). It'd be really awesome if Flow could let you add a new topic like this, using the old API.
+
+https://www.mediawiki.org/wiki/API:Edit#Example
+
+--------------------------
+**See Also**: 
+* {T43276}
+* {T85197}",1386178920,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_description,declined
+S2. Flow API: Let code add a new topic with action=edit&section=new,"Note that will work for both wikitext and Flow, so the gadget does not need to know which the page is.
+
+The above is for if you're trying to create the post immediately through the script.
+
+---
+
+It looks like for this example, you just want to prefill it (rather than use the API), then let the user edit before saving.  Flow supports that too:
+
+https://www.mediawiki.org/wiki/User_talk:Mattflaschen-WMF?topiclist_preloadtitle=Preloaded%20title&topiclist_preload=User:Mattflaschen-WMF/Preloaded%20body%20example
+
+The preloadtitle is inlined.  The preload is a template (in this example [User:Mattflaschen-WMF/Preloaded body example](https://www.mediawiki.org/wiki/User:Mattflaschen-WMF/Preloaded_body_example).
+
+This is basically the same as for old-style talk pages.  For old-style, it's:
+
+https://en.wikipedia.org/wiki/User_talk:Mattflaschen-WMF?preloadtitle=Preloaded title&preload=User:Mattflaschen-WMF/Preloaded body example&action=edit&section=new
+
+In that case, you do currently need to check what kind of page it is, though, using prop=info:
+
+https://en.wikipedia.org/w/api.php?action=query&titles=User%20talk:Mattflaschen-WMF&prop=info
+
+vs.
+
+https://www.mediawiki.org/w/api.php?action=query&titles=User%20talk:Mattflaschen-WMF&prop=info
+
+There is a possibility to make this use case easier for script writers: {T107637}",1439852916,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"Note that will work for both wikitext and Flow, so the gadget does not need to know which the page is.
+
+The above is for if you're trying to create the post immediately through the script.
+
+---
+
+It looks like for this example, you just want to prefill it (rather than use the API), then let the user edit before saving.  Flow supports that too:
+
+https://www.mediawiki.org/wiki/User_talk:Mattflaschen-WMF?topiclist_preloadtitle=Preloaded%20title&topiclist_preload=User:Mattflaschen-WMF/Preloaded%20body%20example
+
+The preloadtitle is inlined.  The preload is a template (in this example [User:Mattflaschen-WMF/Preloaded body example](https://www.mediawiki.org/wiki/User:Mattflaschen-WMF/Preloaded_body_example).
+
+This is basically the same as for old-style talk pages.  For old-style, it's:
+
+https://en.wikipedia.org/wiki/User_talk:Mattflaschen-WMF?preloadtitle=Preloaded title&preload=User:Mattflaschen-WMF/Preloaded body example&action=edit&section=new
+
+In that case, you do currently need to check what kind of page it is, though, using action=info:
+
+https://en.wikipedia.org/w/api.php?action=query&titles=User%20talk:Mattflaschen-WMF&prop=info
+
+vs.
+
+https://www.mediawiki.org/w/api.php?action=query&titles=User%20talk:Mattflaschen-WMF&prop=info
+
+There is a possibility to make this use case easier for script writers: {T107637}",1438383435,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,">>! In T59989#1499951, @tarlocesilion wrote:
+> I believe, I should emphasize that this gadget is old (2006) and //very// popular among experienced Wikipedians, the core of plwiki community, who are likely to be //concerned// about next Flow releases, not only on personal talk pages. Just for the record, if action=edit&section=new isn't to be supported, please, create something instead.
+
+Our recommended solution is to use mw.messagePoster (which we implemented for this purpose).  Usage:
+
+```
+	var title = new mw.Title( 'titleString' );
+	var posterPromise = mw.messagePoster.factory.create( title );
+	posterPromise.done( function ( poster ) {
+		poster.post( 'This is the topic title', 'This is the body of a message posted with MessagePoster' );
+	} );
+```
+
+The gadget should also depend on 'mediawiki.messagePoster' and 'mediawiki.Title' (user scripts can depend on those with mw.loader.using).
+
+If you need further technical assistance, please ask (e.g. in #wikimedia-collaboration on IRC).",1438382035,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"I believe, I should emphasize that this gadget is old (2006) and //very// popular among experienced Wikipedians, the core of plwiki community, who are likely to be //concerned// about next Flow releases, not only on personal talk pages. Just for the record, if action=edit&section=new isn't to be supported, please, create something instead.",1438381026,PHID-USER-gf5juv3z3p75bykrcrhf,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"Note: This has consequences (breakage) for some gadgets, such as 
+https://pl.wikipedia.org/wiki/Wikipedia:Narz%C4%99dzia/Odpowiedzi_z_linkami - A ""replylinks"" gadget at the Polish Wikipedia that adds an ""`[odp]`"" (or  ""`[reply]`"") link after all userpage links, and when clicked, it creates a new user_talkpage section, using the heading of the section that the [reply] link was in.
+
+E.g. Clicking [reply] at: 
+{F292406}
+then opens that user's talkpage, and starts a new section, like so:
+{F292405}
+
+",1438379382,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"@legoktm convinced us not to take this approach, at least for now.
+
+We're instead going to target the sources (e.g. {T91805}), inform early adopters of user talk of this risk ({T90383}), and keep an eye out for reports of missing messages (then fix, or help authors' fix, them to support Flow).",1426116024,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,">>! In T59989#1067648, @Mattflaschen wrote:
+>>>! In T59989#1067094, @Legoktm wrote:
+>> I still think this is a bad idea. It makes transition just a little bit easier, but it means that bots or tools that aren't Flow-aware are just going to more serious issues later on.
+>> 
+>> Tools like mw.feedback should allow Flow to override them to use its API or something.
+> 
+> I think this will be good enough for some write-only tools (they may never need to update to explicitly be Flow-aware).  Others definitely will need to, but this will hopefully ease the transition.
+
+There are no 'write-only' tools, they all have some read actions. What happens if a page is protected? Or they trigger a captcha? Or (spam|title)blacklist/AF is hit? Is Flow going to re-write all of those error cases into their wikitext equivalents? Are we going to strip ~~~~ from posts because (last I checked) that doesn't work in Flow?
+
+It will ease the transition by putting a band-aid over it, but it's going to hurt a lot more when you take that band-aid off.
+
+> We definitely plan on working towards all tools handling Flow correctly; this is just one aspect of that.
+
+Why not just do that from the beginning? If someone tries action=edit on a Flow page, return an error so they're forced to fix the tool.",1426100381,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"hmm, i guess we could be evil and give them the rev id of the page we just created in NS_TOPIC for it, but that probably wont be what they expect :)  Will have to ponder this a bit.",1424904263,PHID-USER-r5pzlcquei6f4hb53rfg,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"Yeah, that sounds right.  It [looks like](https://www.mediawiki.org/wiki/API:Edit#Example) we're have to do some tricks with the revid (we also need to support at least XML and JSON, preferably all the output formats).",1424904162,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"I was initially thinking this was basically going to be a rewrite procedure:
+
+* receive api request, rewrite to flow api request
+* receive flow response, rewrite to look like normal api response.",1424903218,PHID-USER-r5pzlcquei6f4hb53rfg,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"I was initially thinking this was basically going to be a rewrite procedure:
+
+* receive api request, rewrite to flow api request
+* receive flow response, rewrite to look like normal api request.",1424903203,PHID-USER-r5pzlcquei6f4hb53rfg,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"We should discuss whether to try to make the output match, or just use the Flow output.",1424903160,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,">>! In T59989#1067094, @Legoktm wrote:
+> I still think this is a bad idea. It makes transition just a little bit easier, but it means that bots or tools that aren't Flow-aware are just going to more serious issues later on.
+> 
+> Tools like mw.feedback should allow Flow to override them to use its API or something.
+
+I think this will be good enough for some write-only tools (they may never need to update to explicitly be Flow-aware).  Others definitely will need to, but this will hopefully ease the transition.
+
+We definitely plan on working towards all tools handling Flow correctly; this is just one aspect of that.",1424899878,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"I still think this is a bad idea. It makes transition just a little bit easier, but it means that bots or tools that aren't Flow-aware are just going to more serious issues later on. 
+
+Tools like mw.feedback should allow Flow to override them to use its API or something.",1424894374,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"This really doesn't have anything to do with LQT except that ""It worked in LQT; it should work in Flow"".  We're not proposing any change to LQT, though.",1421290668,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,"It also affects various other things, e.g. MoodBar (I know, I know, MoodBar's not widely used, but I hit it recently when testing an unrelated fix in MoodBar).
+
+Plus, I'm sure it affects many things we're not thinking of.",1420745630,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,We can't convert the https://www.mediawiki.org/wiki/VisualEditor/Feedback LQT page to Flow until this is fixed. :-(,1420737319,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,">>! In T59989#602152, @Jdforrester-WMF wrote:
+> See also bug 49636 which means that pointing MW's feedback tool at a Flow board won't work. Boo.
+
+Now {T51636}",1420667668,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+S2. Flow API: Let code add a new topic with action=edit&section=new,See also bug 49636 which means that pointing MW's feedback tool at a Flow board won't work. Boo.,1386179090,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lfuu4csnnqoanjnouo7z,task_subcomment,NA
+VisualEditor: Deleting a reflist along with some content and saving the page keeps the previous the content on the page,"Steps to reproduce:
+
+1.Click on the Edit button for a page
+2.Type two paragraphs
+3.Add a text with reference
+4.Add a reflist
+5.Save the page
+6.Re-open the editor
+7.Delete the reference and the reflist and the second paragraph
+8.Save the page
+Observed Result:
+The second paragraph and the text with reference did not get deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386119340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zgtluxsdmxcciykkdi5g,task_description,declined
+VisualEditor: Deleting a reflist along with some content and saving the page keeps the previous the content on the page,ryasmeen: If there is no identifiable code commit this should not be closed as FIXED but as WORKSFORME. See https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle,1387318251,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zgtluxsdmxcciykkdi5g,task_subcomment,NA
+VisualEditor: Deleting a reflist along with some content and saving the page keeps the previous the content on the page,Cannot reproduce it now,1387299115,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zgtluxsdmxcciykkdi5g,task_subcomment,NA
+VisualEditor: Deleting a reflist along with some content and saving the page keeps the previous the content on the page,"Test Environment: betalabs
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Example:http://en.wikipedia.beta.wmflabs.org/wiki/New_page_on_latex",1386119422,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zgtluxsdmxcciykkdi5g,task_subcomment,NA
+VisualEditor:  Print/Export tools are enabled while editing,"Actual Results:  
+When you open VisualEditor, the Print/Export section in the sidebar is still present.  It is not displayed when you open the same page in the wikitext editor.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1386098520,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jskdpgwlerlkftfmfqxh,task_description,resolved
+VisualEditor:  Print/Export tools are enabled while editing,"Change 129059 merged by jenkins-bot:
+Hide some tools when VE is open
+
+https://gerrit.wikimedia.org/r/129059",1398294414,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jskdpgwlerlkftfmfqxh,task_subcomment,NA
+VisualEditor:  Print/Export tools are enabled while editing,"Change 129059 had a related patch set uploaded by Alex Monk:
+Hide some tools when VE is open
+
+https://gerrit.wikimedia.org/r/129059",1398206983,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jskdpgwlerlkftfmfqxh,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"screenshot
+
+Steps to reproduce:
+
+1.Click on the Edit beta button
+2.Switch to Edit Source
+3.Switch back to VE
+4.Click on Cancel
+5.Reload the page
+
+
+Observed Result:
+Even after cancelling the edit, in the URL ""&veaction=edit"" still remains appended , therefore after reloading the page, VE opens up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12776}",1386028200,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_description,resolved
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"Change 118357 merged by jenkins-bot:
+mw.ViewPageTarget: Tag our state changes and reject foreign states
+
+https://gerrit.wikimedia.org/r/118357",1394659811,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"Rephrasing bug.
+
+There is explicit logic in place to not update the url sometimes. This is for when we're reacting to a popstate event (e.g. you open VisualEditor from the read page, this activates the editor without a refresh, if you then click back, the browser has already updated the url and it is now telling us to react to that, we don't want to update the url again in that case).
+
+Whenever the editor is initialised in Chrome by direct query parameter  (e.g. by clicking ""Edit"" on a page where we don't load visualeditor, e.g. MediaWiki's Edit source page), the weird initial popstate fired by Chrome was misinterpreted as a dynamic state change.
+
+Then, when leaving the editor, we still think we're reacting to a popstate event so we don't touch the url.",1394659627,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"Change 118357 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Tag our state changes and reject foreign states
+
+https://gerrit.wikimedia.org/r/118357",1394659617,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"It should be reliably reproducible on all of the above.
+
+It happens when you access veaction=edit directly in the url on a fresh load.
+
+Chrome has the nasty habit of firing a popstate event (sometimes?) on a regular load that wasn't via the history.
+
+This can be worked around by storing a piece of data with the state and using that to tell events apart (to distinguish between a state pop to one we pushed/replaced into the history, from a pop state to one some other application pushed in or one the browser is faultily firing, like Chrome does).
+
+jquery-pjax (the plugin GitHub uses to ajax navigate everywhere, powered by popState), does the same thing. Generate an ID or tag, store that with the push/replace state, and on the popstate, use that to identify ours and ignore others.
+
+This will fix lots of other potential bugs as well.
+
+Assigning back to me as it's on my mind now, might as well fix it.",1394655517,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,I can reproduce it on en.wikipedia.org but not on mediawiki.org,1394648854,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,"I can't reproduce this on mediawiki.org or en.wikipedia.org, but I can locally and on en.wikipedia.beta.wmflabs.org",1394648234,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,This appears to be to do with actFromPopState in ve.init.mw.ViewPageTarget,1393868716,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+VisualEditor: Deactivating editor after activating by url query leaves veaction=edit,*** Bug 57902 has been marked as a duplicate of this bug. ***,1386035934,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3iie7vgp5rstgp2jfvqp,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","Screenshot
+
+Steps to reproduce:
+
+1.Click on Edit for a page
+2.Add a reference
+3.Use same reference multiple times in the page
+4.Now again while adding reference click on ""Use an Existing reference""
+
+Observed Result:
+On this dialog box beside the reference [1] the ref name "":0"" appears.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12716}",1386013680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r6noyqq7rq63j346ezyr,task_description,resolved
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","This bug seems to be back. I'm experiencing it on Chrome, and thought they were invalid references until Google-ing 
+```
+<ref name="":0"" />
+```
+
+brought me here",1463358964,PHID-USER-z5numv3lbo6csllpqb73,False,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations",Verified the fix in test2,1392254661,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations",Verified the fix in Betalabs,1391719877,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","Change 111626 merged by jenkins-bot:
+Hide automatic reference names
+
+https://gerrit.wikimedia.org/r/111626",1391648543,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","Change 111626 had a related patch set uploaded by Esanders:
+Hide automatic reference names
+
+https://gerrit.wikimedia.org/r/111626",1391641248,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","I noticed this while fixing the reference content bug. We used to detect the auto numbering pattern, but not any more. I think we should hide these.",1391633875,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Ref name "":0"" appears in the dialog box of adding existing reference which has repeated citations","Test Environment: production
+Browser: Chrome Version 26.0.1410.65 &       FF 25
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/addimage&veaction=edit",1386013741,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-r6noyqq7rq63j346ezyr,task_subcomment,NA
+"VisualEditor: Pressing ""undo"" deletes the content of an article making the ""save page"" button disable for that session","Screenshot of the error
+
+Steps to reproduce:
+
+1.Click on the ""Edit"" button for a page
+2.Type something with a link on the main page
+3.Add a template for example:Bronze Age
+4.Add another line with a reference
+5.Add reflist to the article
+6.Save the page
+7.Reopen the editor
+8.Press Delete (Deletes the first line)
+9.Press Delete again (Nothing happens)
+10.Press Undo
+
+Observed Result:
+
+1.Deletes all the content of the article.
+2.Only the blue empty highlighted box remains at the right
+3.Save Page button becomes disabled
+4.Make further edit but still the ""Save Page"" button remains disabled for that session
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12501}",1385853780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fs5utskfc7v7hpp4u6fl,task_description,resolved
+"VisualEditor: Pressing ""undo"" deletes the content of an article making the ""save page"" button disable for that session",Fixed by Ed as part of bug 57217.,1410461760,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fs5utskfc7v7hpp4u6fl,task_subcomment,NA
+"VisualEditor: Pressing ""undo"" deletes the content of an article making the ""save page"" button disable for that session","Test Environment: production
+Browser: Chrome Version 26.0.1410.65
+OS: MAC OS X 10. 8. 5 
+Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/twicedeleted",1385853865,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fs5utskfc7v7hpp4u6fl,task_subcomment,NA
+VisualEditor: newFromDocumentInsertion not implemented properly for reference/media insertions,"Currently inserting a new reference fails because of changes to newFromDocumentInsertion. The first thing that looks wrong is that the 'empty' document we generate for new references/media captions contains one paragraph and an empty internal list, I suspect we need to copy the existing internal list over.
+
+Even with that fixed it appears we aren't generating the correct sequence of transactions so they need to be reviewed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385836200,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-orj2erahi5zpz3pkgwc6,task_description,resolved
+VisualEditor: newFromDocumentInsertion not implemented properly for reference/media insertions,Fixed a while ago.,1386931739,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-orj2erahi5zpz3pkgwc6,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,"On fr.wp, see:
+https://fr.wikipedia.org/w/index.php?title=Indicateur_du_d%C3%A9veloppement_durable&diff=98505933&oldid=98352104
+
+https://fr.wikipedia.org/w/index.php?title=Dan_Flavin&diff=prev&oldid=98639433
+
+Somehow, categories (and in one case, DEFAULTSORT) move from the bottom of the page and get inside a reference.
+
+I'll very roughly translate for you the comment of Drongou, who tried to replicate but didn't manage to:
+
+<<I can't reproduce this bug (on Mac OS X) but what they have in common is the suppression of a template at the top of the page. For the reference, I have tried to manipulate one several times but that didn't lead to anything. Since it's always the first reference which is affected, I think this [...] is probably due to the template being deleted but not in an usual way. Regards.>>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385747760,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_description,invalid
+VisualEditor: All metadata moved from bottom of the page into a reference,@Pols12 I haven't seen it recently,1593613982,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,Would probably be never reproducible… @NicoV have you seen it since your last report in 2014?,1593613921,PHID-USER-unpoeiyj52rmcfqi5rbw,True,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,"Still happening, any plan on fixing this bug that has been reported for 6 months now ?
+
+https://fr.wikipedia.org/w/index.php?title=Richard_Orlinski&diff=prev&oldid=103966506",1400701246,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,"(In reply to Trevor (Wikia) from comment #1)
+> This may also be related to this kind of dirty diff:
+> https://www.mediawiki.org/w/index.
+> php?title=VisualEditor%3ATest123&diff=933910&oldid=933905
+> 
+> Essentially, it seems to happen if you edit right at the page end - I simply
+> pressed enter on the last line of text, changed the format to a heading, and
+> typed. Then pressed enter and typed a line of normal text. Saved page.
+> 
+> Wikia's ticket for this is VE-802
+
+That's unrelated. The title of this bug was a red herring: the data was moved across large distances (which didn't happen in your case) into a <ref> tag (which didn't happen in your case), and it so happened that that <ref> tag was in a heading in one case. This bug isn't related to headings, it's related to references.",1395257038,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: All metadata moved from bottom of the page into a reference,"This may also be related to this kind of dirty diff: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ATest123&diff=933910&oldid=933905
+
+Essentially, it seems to happen if you edit right at the page end - I simply pressed enter on the last line of text, changed the format to a heading, and typed. Then pressed enter and typed a line of normal text. Saved page.
+
+Wikia's ticket for this is VE-802",1395253868,PHID-USER-2mvmxqtefj5cyyzm7jks,True,PHID-TASK-lbfh6wptvtd5xpjhoeon,task_subcomment,NA
+VisualEditor: Expand commands (keyboard shortcuts) to target level commands,"Currently commands are executed on the surface, and don't fire at all when not in a surface context (e.g. a dialog), however we want to have target level shortcuts (save, show menu, show help, etc.) that don't just fire when the document is fired.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385674920,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fc5nfpvuhrxs4qd4v73j,task_description,resolved
+VisualEditor: Expand commands (keyboard shortcuts) to target level commands,"Is this now fixed? We now have save-page, show-help and other target-level shortcuts…",1401473606,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fc5nfpvuhrxs4qd4v73j,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"We are trying to debug a failure with the way parsoid is set up in the Labs-Vagrant visualeditor role setup
+<https://wikitech.wikimedia.org/wiki/Talk:Labs-vagrant#Parsoid_errors_using_VisualEditor_role>
+
+When the client gets 404 errors, the error in /var/log/upstart/parsoid.log is just 
+  ERROR in localhost:Main_Page
+  Stack trace: DoesNotExistError: Page Fetch failure for null
+  worker 25269 died (1), restarting.
+
+but it doesn't say what the error is.
+ebernhardson tweaked the second line to actually say what's going wrong by adding error to the output, so the second line becomes
+
+  Stack trace: DoesNotExistError: Page Fetch failure for null : Error: Invalid URI ""undef/w/api.php?format=json&action=query&meta=siteinfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensiontags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols""
+
+, and now we can get somewhere :)
+
+Two-line patch on its way
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385598780,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_description,resolved
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Change 101336 merged by GWicke:
+More informative DoesNotExistError logging.
+
+https://gerrit.wikimedia.org/r/101336",1386964611,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Change 101336 had a related patch set uploaded by GWicke:
+More informative DoesNotExistError logging.
+
+https://gerrit.wikimedia.org/r/101336",1386964549,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,I changed the title so we can review that we do have useful logging in all handlers and wanted to keep this open till we have actually reviewed it.,1386271167,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Change 98038 merged by jenkins-bot:
+More informative DoesNotExistError logging.
+
+https://gerrit.wikimedia.org/r/98038",1386183235,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Let us leave this bug open even after this patch is merged. We should review all our response handlers and make sure we are emitting informative log messages based on the error that is returned. Looking at the code, I see that we return early in many handlers.",1386171798,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.,"Change 98038 had a related patch set uploaded by Spage:
+More informative DoesNotExistError logging.
+
+https://gerrit.wikimedia.org/r/98038",1385599614,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m25vw4w7d3ob5tvtvkwx,task_subcomment,NA
+VisualEditor: Pre-annotation in a block slug should never read from the next character,"Screenshot
+
+Steps to reproduce:
+
+1.Click on the Edit button.
+2.Add a template to a page.
+3.Add another template on it.
+4.Type something on the next line of second template and format it to Preformatted ,Bold,Italic,Subscript/Underlined.
+5.Now type something between the two templates.
+
+Observed Result:
+The text added between two templates takes the format of the next line to the second template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12332}",1385588100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-brz6dzyxm67j6sqaxjdh,task_description,resolved
+VisualEditor: Pre-annotation in a block slug should never read from the next character,"Fixed some time ago, it seems.",1409596597,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-brz6dzyxm67j6sqaxjdh,task_subcomment,NA
+VisualEditor: Pre-annotation in a block slug should never read from the next character,"Test Environment: production
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+Example Page:
+https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test2511?veaction=edit",1385588180,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-brz6dzyxm67j6sqaxjdh,task_subcomment,NA
+VisualEditor: Save dialog not torn down properly after edit,"Consequently the second time you edit a page, it thinks the save dialog already exists so it isn't set up again, and it fails to render.
+
+We should add a ""double edit"" workflow to our Selenium or manual tests.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1385559240,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ucrlmd4fhqqckto7xviu,task_description,resolved
+VisualEditor: Save dialog not torn down properly after edit,"Change 97913 merged by jenkins-bot:
+Tear down the save dialog and remove it from memory on surface teardown
+
+https://gerrit.wikimedia.org/r/97913",1385936588,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ucrlmd4fhqqckto7xviu,task_subcomment,NA
+VisualEditor: Save dialog not torn down properly after edit,"Change 97913 had a related patch set uploaded by Esanders:
+Tear down the save dialog and remove it from memory on surface teardown
+
+https://gerrit.wikimedia.org/r/97913",1385561026,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ucrlmd4fhqqckto7xviu,task_subcomment,NA
+VisualEditor: Save dialog not torn down properly after edit,Specifically when the surface is torn down the surface overlays are detached.,1385559985,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ucrlmd4fhqqckto7xviu,task_subcomment,NA
+VisualEditor: Adjacent lists should be easily joinable,"It is quite easy to create two adjacent lists that appear to be one list (but for a small amount of extra spacing) through copy/paste or deletion. More often than not this is not what the user means semantically, so such a situation should be highlighted to the user and they should be given an easy way to fixup the code.
+
+I have yet to see an editor which does this well, but that shouldn't stop us being the first.
+
+==Steps to reproduce==
+Just as a helpful example.
+
+1. Create a list.
+1. Decide to end the list by pressing enter while on a blank bullet.
+1. Change your mind and decide to continue the list by clicking the list buttons.
+1. Now the document has two separate lists, but your mental model only has one.",1385558520,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-kjvmewrqq2l7f4hcprhb,task_description,open
+VisualEditor: External paste of list into list should unwrap pasted list,"Currently pasting a list into a list creates a sub-list. From a technical point of view this is correct (the paste contents will always be a full list) but from a user expectation point of view this will be wrong 99% of the time, so we should unwrap the pasted list so it flattens to the same list level as the target.",1385558160,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yzpiypk2d2inixzpoytj,task_description,open
+VisualEditor: There should be tests asserting we use code points as opposed to grapheme clusters,"Timo astutely observed that no tests had to be changed in https://gerrit.wikimedia.org/r/#/c/80689 despite the change from grapheme clusters to code points. I share his feeling that there should have been tests that would have been broken by that change. It's never too late to write some :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385507220,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5vxcaydqorsjojhwsdme,task_description,open
+VisualEditor: Get rid of ve.splitClusters,"It has a comment that says TODO: strip out calls to splitClusters then delete this method.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385506740,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_description,resolved
+VisualEditor: Get rid of ve.splitClusters,"Change 165433 merged by jenkins-bot:
+Getting rid of ve.splitClusters in VE core
+
+https://gerrit.wikimedia.org/r/165433",1412756070,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"Change 165430 merged by jenkins-bot:
+Getting rid of ve.splitClusters in ve-mw
+
+https://gerrit.wikimedia.org/r/165430",1412756028,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"Change 165430 had a related patch set uploaded by SuchetaG:
+Getting rid of ve.splitClusters in ve-mw
+
+https://gerrit.wikimedia.org/r/165430",1412755760,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"Change 165433 had a related patch set uploaded by SuchetaG:
+Getting rid of ve.splitClusters in VE core
+
+https://gerrit.wikimedia.org/r/165433",1412755689,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"Hi, yes, we wrote ve.splitClusters because we wanted to make the document model be a list of grapheme clusters, instead of a list of raw Javascript characters (i.e. Unicode code units, so each surrogate pair like '\uD860\uDEE2' is treated as two separate entities '\uD860' and '\uDEE2').
+
+However, we've subsequently decided against that, because browsers will not always agree what constitutes a grapheme cluster. The example of Malayalam, where the font can affect the number of clusters, is one example of how problematic it could be to try to match the browser's clusterings exactly.
+
+Therefore, the DM is to remain a list of raw Javascript characters, and support related to clustering is being developed at a level on top of the DM.",1412697433,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"(In reply to Sucheta Ghoshal from comment #1)
+> Well, if we are going beyond BMP, we need to take surrogate pairs into
+> account, too. JavaScript does not do that natively, AFAIK. Would code points
+> be enough in that case?
+
+I think the idea is that at the DM layer, we won't be combining anything beyond code points, but David (CC) can confirm.",1412696779,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+VisualEditor: Get rid of ve.splitClusters,"**sucheta.ghoshal** wrote:
+
+Well, if we are going beyond BMP, we need to take surrogate pairs into account, too. JavaScript does not do that natively, AFAIK. Would code points be enough in that case?",1412696686,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-g3vdqa5vzvi25aw23qzs,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Insert a reference with no content.
+3.Save the page
+
+Observed Result:
+
+The error message that appears on the page is ""Cite error: The opening <ref> tag is malformed or has a bad name"" where as 
+when you edit a reference (not first time insert) to an empty content the error message that appears is ""Cite error: There are <ref> tags on this page without content in them""
+
+The later one is more understandable for a user.So maybe we can change the message to the later one.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385497740,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uontdax7p5isoaavstyc,task_description,resolved
+Cite: Error message for an empty reference should be more appropriate and helpful,"VisualEditor does not any more allow adding empty reference, so the VE side of the issue is no more reproducible.
+ 
+Maybe, VE was converting empty reference as <ref/> and therefore it was showing ""Cite error: The opening <ref> tag is malformed or has a bad name"" , which seems like expected behavior. 
+
+Therefore, closing this bug.",1506637627,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"The VisualEditor does not any more allow adding empty reference, so the VE side of the issue is no more reproducible.
+ 
+Maybe, VE was converting empty reference as <ref/> and therefore it was showing ""Cite error: The opening <ref> tag is malformed or has a bad name"" , which seems like expected behavior. 
+
+Therefore, closing this bug.",1506637608,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,I'm not convinced this is a tone matter.,1446209841,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Error messages are controlled by MediaWiki interface pages. Enter `MediaWiki:Cite error ref no key` into the search box and it will open the interface page. These pages have a default, so if it is not customized, the page does not actually exist as such and when you edit it, it shows as if you are creating a brand new page but it shows the default message. If you go to `Special:AllMessages` you can enter `Cite error ref no key` and it will show the default and the custom if it exists. If you enter `Cite error` is will show all cite error interface pages.
+
+Cite.php is the software extension for all of this.
+https://www.mediawiki.org/wiki/Extension:Cite
+
+The error messages are set up through `cite body.php` and then there are language files in the i18n folder.
+
+
+The English Wikipedia is VERY customized. We use {{broken ref}} to control the message display and the namespace. Every message links to a help page. See https://en.wikipedia.org/wiki/Help:Cite_errors#Error_messages for a list of all messages. Each help page has a Technical section that has a link to the MediaWiki interface page.",1425242197,PHID-USER-zqde3skdzpqiwny4dxt4,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,,1425242226,PHID-USER-nk32pihw2thyf2uczoq5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,,1425241010,PHID-USER-nk32pihw2thyf2uczoq5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Ah.
+
+<ref /> is indeed invalid and triggers `MediaWiki:Cite error ref no key` which displays `Invalid <ref> tag; refs with no content must have a name` by default and is customized to `The opening <ref> tag is malformed or has a bad name (see the help page).` on the English Wikipedia which is a better description.",1425236652,PHID-USER-zqde3skdzpqiwny4dxt4,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"{F51632} 
+when i entered the reference with no content still i had this error
+Cite error: Invalid <ref> tag;
+refs with no content must have a name
+{F51634}
+so what should i do
+both of them are set to the same message in my en.json
+""cite_error_ref_no_key"": ""Invalid <code>&lt;ref&gt;</code> tag;\nrefs with no content must have a name"",
+	""cite_error_ref_no_input"": ""Invalid <code>&lt;ref&gt;</code> tag;\nrefs with no name must have content"",
+",1425236169,PHID-USER-nk32pihw2thyf2uczoq5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"{F51632} 
+when i entered the reference with no content still i had this error
+Cite error: Invalid <ref> tag;
+refs with no content must have a name
+
+{F51634}",1425235969,PHID-USER-nk32pihw2thyf2uczoq5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Looking at the original issue:
+
+----
+1.Click on the ""Edit"" button
+2.Insert a reference with no content.
+3.Save the page
+
+Observed Result
+
+The error message that appears on the page is `Cite error: The opening <ref> tag is malformed or has a bad name.`
+----
+
+I don't see this. I create a test page with <ref></ref> and save. The page shows Cite error: There are <ref> tags on this page without content in them (see the help page). which is customized on the English Wikipedia from `MediaWiki:Cite error ref no input`. This is correct.",1425234889,PHID-USER-zqde3skdzpqiwny4dxt4,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Looking at the original issue:
+
+----
+1.Click on the ""Edit"" button
+2.Insert a reference with no content.
+3.Save the page
+
+Observed Result:
+
+The error message that appears on the page is `Cite error: The opening <ref> tag is malformed or has a bad name.`
+----
+
+I don't see this. I create a test page with <ref></ref> and save. The page shows Cite error: There are <ref> tags on this page without content in them (see the help page). which is customized on the English Wikipedia from `MediaWiki:Cite error ref no input`. This is correct.",1425234871,PHID-USER-zqde3skdzpqiwny4dxt4,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Looking at the original issue:
+
+----
+1.Click on the ""Edit"" button
+2.Insert a reference with no content.
+3.Save the page
+
+Observed Result:
+
+The error message that appears on the page is ""Cite error: The opening <ref> tag is malformed or has a bad name.""
+----
+
+I don't see this. I create a test page with <ref></ref> and save. The page shows ""Cite error: There are <ref> tags on this page without content in them (see the help page)."" which is customized on the English Wikipedia from 'MediaWiki:Cite error ref no input'. This is correct.",1425234812,PHID-USER-zqde3skdzpqiwny4dxt4,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful," ""cite_error_ref_no_key"": ""Invalid <code>&lt;ref&gt;</code> tag;\nrefs with no content must have a name"", is already set to this in the local environment.
+should i create a patch for this.",1425231591,PHID-USER-nk32pihw2thyf2uczoq5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,Rits: See https://en.wikipedia.org/wiki/Help:Cite_errors/Cite_error_ref_no_key,1425230436,PHID-USER-zqde3skdzpqiwny4dxt4,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"i am working on this bug i am unable to generate  ""Cite error: The opening <ref> tag is malformed or has a bad name"" although i am able to generate the  ""Cite error: There are <ref> tags on this page without content in them"" . ",1425227409,PHID-USER-nk32pihw2thyf2uczoq5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"The test page in question includes '<ref />' which is invalid. This triggers 'MediaWiki:Cite error ref no key'.
+
+The default error message is ""Invalid <ref> tag; refs with no content must have a name""
+
+The customized message on enwiki is ""The opening <ref> tag is malformed or has a bad name (see the help page)."" The linked help page explains the issue in depth.",1405983491,PHID-USER-zqde3skdzpqiwny4dxt4,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"The examples are on the English Wikipedia, where the cite errors are heavily customized.
+
+* ""Cite error: The opening <ref> tag is malformed or has a bad name"" is through ""MediaWiki:Cite error ref no key""
+
+
+* ""Cite error: There are <ref> tags on this page without content in them"" is through ""MediaWiki:Cite error ref no input""",1398941036,PHID-USER-zqde3skdzpqiwny4dxt4,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,(Not a VisualEditor-specific issue.),1392747737,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Created attachment 13913
+Screenshot of the error
+
+**Attached**: {F12187}",1385497954,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+Cite: Error message for an empty reference should be more appropriate and helpful,"Created attachment 13912
+screenshot
+
+**Attached**: {F12186}",1385497847,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uontdax7p5isoaavstyc,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"To figure out:
+* Does this work in all browsers we support? I have anecdotally confirmed support in Firefox 25 and Chrome 30
+* Protocol-relative URLs in <base> are broken, because documents created this way don't have a creator context or whatever.
+
+Benefits:
+* Not a hack involving iframes :)
+* Faster than the iframe hack
+* Does not have issues with HTTPSEverywhere in Firefox
+
+For the <base> issue, it looks like something like this will work:
+
+>>> d.querySelector('base')
+<base href=​""/​/​example.com"">​
+>>> d.baseURI
+null
+>>> d.querySelector('base').getAttribute('href')
+""//example.com""
+>>> d.querySelector('base').setAttribute('href', 'http://example.com');
+undefined
+>>> d.baseURI
+""http://example.com/""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385472240,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_description,resolved
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"Change 120836 merged by jenkins-bot:
+Use DOMParser in ve.createDocumentFromHtml() if available
+
+https://gerrit.wikimedia.org/r/120836",1395875951,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"(In reply to Roan Kattouw from comment #2)
+> ...or use DOMParser, which actually does *precisely* what we want. We could
+> use it in browsers where it's available as a replacement for
+> ve.createDocumentFromHtml, because it's supported only in FF 12+, Chrome 30+
+> (!), IE 10+, Opera 17+ (!) and not at all (!!) in Safari.
+This is what I ended up going with.",1395771178,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"Change 120836 had a related patch set uploaded by Catrope:
+Use DOMParser in ve.createDocumentFromHtml() if available
+
+https://gerrit.wikimedia.org/r/120836",1395771153,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"...or use DOMParser, which actually does *precisely* what we want. We could use it in browsers where it's available as a replacement for ve.createDocumentFromHtml, because it's supported only in FF 12+, Chrome 30+ (!), IE 10+, Opera 17+ (!) and not at all (!!) in Safari.",1392850210,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML,"(In reply to comment #0)
+> For the <base> issue, it looks like something like this will work:
+>
+I read the spec some more and it looks like the trick I outlined is actually something that the spec specifically covers and says should work.
+
+Other issue: we can't parse doctypes or <html> tags this way, so we can't respect non-HTML5 doctypes and we won't see any attributes on the <html> element. This isn't a problem for Parsoid documents at this time, although it'll be pretty annoying if we ever want to respect things like <html lang=""nl"">.",1387370415,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ogfzjtubgzf6pn6yfvz3,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28proposals%29&oldid=582561035#Proposed_new_Draft_namespace
+
+I believe this discussion demonstrates sufficient community consensus to create a ""Draft"" namespace on the English Wikipedia.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28proposals%29&oldid=582561035#Proposed_new_Draft_namespace
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57315",1385425560,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-atmvpvsegseglymt64gn,task_description,resolved
+"Create ""Draft"" namespace on the English Wikipedia","thx, i have done. 
+
+i suggest this namespace be added to MediaWiki. ",1522881510,PHID-USER-klaycnqc3osjrltt7lu4,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","@Johnywhy No, but you can setup this yourself following https://www.mediawiki.org/wiki/Manual:Using_custom_namespaces
+
+You can also check the changes above if you've Visual Editor or wants to configure robotx.txt to discourage crawling",1522880965,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","hi, i noticed the Draft namespace doesn't exist in my off-the-shelf MediaWiki installation 1.30. Any plans for that? -thx",1522880797,PHID-USER-klaycnqc3osjrltt7lu4,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Thank you Matt, Steven, and everyone else for your work on this. :-)",1387337581,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","This is deployed to English Wikipedia.
+
+You can also resume testing on Beta.  The old drafts are at http://en.wikipedia.beta.wmflabs.org/wiki/Special:PrefixIndex/Draft .  They can be moved back into the Draft space if desired.",1387326342,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Change 97675 merged by jenkins-bot:
+Create ""Draft"" namespace on the English Wikipedia
+
+https://gerrit.wikimedia.org/r/97675",1387325866,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia",The VE stuff has now been included into the main change (https://gerrit.wikimedia.org/r/#/c/97675/).,1387318226,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia",VisualEditor will be enabled in the namespace for opt-in users.  See https://www.mediawiki.org/wiki/Draft_namespace and https://gerrit.wikimedia.org/r/#/c/102311/ .,1387317317,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #33)
+> FYI: we're testing the new namespace on Labs
+> (http://en.wikipedia.beta.wmflabs.org). Please help give it a try.
+
+Thank you for testing.
+
+Please hold off on creating additional Drafts for now, until it is deployed (this is due to the namespace ID change mentioned at https://bugzilla.wikimedia.org/show_bug.cgi?id=57315#c44).",1387275142,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #29)
+> Change 99600 merged by jenkins-bot:
+> Test under-review English Wikipedia draft namespace on Labs
+> 
+> https://gerrit.wikimedia.org/r/99600
+
+FYI: we're testing the new namespace on Labs (http://en.wikipedia.beta.wmflabs.org). Please help give it a try.",1386634272,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","I used to have very strong opinions on easy with shell bugs, but that was back in the svn days where you actually needed to be shell to do anything useful on these bugs. Now anyone can submit changes, so that argument is less compelling.",1386422563,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #30)
+> We don't use easy keyword for shell bugs, as they're advertised not as ""easy
+> bug to write"" but as ""easy bugs for new contributors to discover the code"".
+> Shell bugs ask a knowledge of community consensus, and so they aren't
+> suitable for newcomers.
+
+I'm not sure this logic is sound. The ""easy"" keyword is associated with technical complexity. Couldn't we presume that the person adding the ""easy"" keyword is capable of making a full judgment of the bug, evaluating both the technical complexity and the social implications?
+
+That is, committing a change for an ""easy"" shell ticket still allows new users to learn and experience Git and code review without them needing to be able to divine Wikimedia wiki consensus. On bugs where consensus, technical or otherwise, is unclear, there's a strong case for not marking the bug as ""easy."" I don't believe that's the case here or in many other cases of ""shell"" bugs.",1386407353,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #8)
+> (In reply to comment #6)
+> > We're talking about a two-line configuration change here.
+> 
+> Probably a few more than two lines to create the namespace, the talk
+> namespace,
+> and set noindex. Maybe a half-dozen to a dozen lines? In any case, this seems
+> fairly easy to implement to me.
+
+We don't use easy keyword for shell bugs, as they're advertised not as ""easy bug to write"" but as ""easy bugs for new contributors to discover the code"". Shell bugs ask a knowledge of community consensus, and so they aren't suitable for newcomers.",1386320427,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Change 99600 merged by jenkins-bot:
+Test under-review English Wikipedia draft namespace on Labs
+
+https://gerrit.wikimedia.org/r/99600",1386302568,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Change 99600 had a related patch set uploaded by Mattflaschen:
+Test under-review English Wikipedia draft namespace on Labs
+
+https://gerrit.wikimedia.org/r/99600",1386298083,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**equazcion** wrote:
+
+> (In reply to comment #25)
+> > I have a hard time understanding what is going on here? If this was any other
+> > wiki, we would note that their is community consensus, and implement the
+> > change.
+> > 
+> > The only thing slightly iffy thing here is to be able to let anons create
+> > pages
+> > in this namespace - that might require someone taking 10 seconds writing a
+> > hook
+> > (Or even better, someone fixing mediawiki so we have proper per-namespace
+> > permissions). However that can easily be done later. the robots thing is
+> > already a config option.
+> > 
+> > Furthermore, all these various ""config"" related changes are trivial to change
+> > after the fact if people discover they want something different.
+> > 
+> > New namespaces get created for other wikis all the time. This has
+> > traditionally
+> > been something that has entirely been up to the community to decide for
+> > themselves. I don't understand why enwiki gets treated so differently.
+> > 
+> > >Key minimum requirements for launch are being hashed out at
+> > >https://www.mediawiki.org/wiki/Draft_namespace 
+> > 
+> > Kind of seems odd this is being written up on mediawiki.org, for something
+> > that
+> > is in essence a config change coming out of enwikipedia community. Its not
+> > like
+> > there are non-user facing technical hurtles to surmount. There's no new db
+> > schema being proposed or anything like that.
+
+Bawolff has a hard time understanding what most of us are having a hard time understanding. The piece you're missing, Bawolff, is that after this new namespace was proposed and passed as simply a new namespace, Steven Walling took it over by submitting the supposed bug for implementation (bug 57315), which was actually for something much more than a new namespace. 
+
+While I'm sure he originally had the best of intentions, it was pointed out thereafter that his plan for implementation was markedly different from the accepted proposal that was supposed to have originated it. Rather than admit his error as a good Wikipedia administrator should, he's made every effort to outwardly cling to his original position like a good infallible corporate manager would: He attempted to pass off the bloat in his proposed implementation as ""requirements"" for the namespace, when they had actually been some new ideas he wanted to tinker with. The claim that these were ""requirements"" was again pointed out as erroneous, but he still insisted on making some list of requirements regardless, rather than simply letting it go. This is the show of complexity where none is actually necessary that you're seeing now and have astutely pointed out. 
+
+And this is, in my mind, an example of the type of behavior that has brought the relationship between the WMF and the Wikipedia community to the sour state it is. And it felt good to get that out. 
+
+Hope we can get some actual stuff done now.",1385604994,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #25)
+> I have a hard time understanding what is going on here? If this was any other
+> wiki, we would note that their is community consensus, and implement the
+> change.
+> 
+> The only thing slightly iffy thing here is to be able to let anons create
+> pages
+> in this namespace - that might require someone taking 10 seconds writing a
+> hook
+> (Or even better, someone fixing mediawiki so we have proper per-namespace
+> permissions). However that can easily be done later. the robots thing is
+> already a config option.
+> 
+> Furthermore, all these various ""config"" related changes are trivial to change
+> after the fact if people discover they want something different.
+> 
+> New namespaces get created for other wikis all the time. This has
+> traditionally
+> been something that has entirely been up to the community to decide for
+> themselves. I don't understand why enwiki gets treated so differently.
+> 
+> >Key minimum requirements for launch are being hashed out at
+> >https://www.mediawiki.org/wiki/Draft_namespace 
+> 
+> Kind of seems odd this is being written up on mediawiki.org, for something
+> that
+> is in essence a config change coming out of enwikipedia community. Its not
+> like
+> there are non-user facing technical hurtles to surmount. There's no new db
+> schema being proposed or anything like that.
+
+I suggest you check out the mediawiki.org page and the associated bug 57315. They both include some explanation, including the technical discussions involved about implementation, and about future plans.",1385596480,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","I have a hard time understanding what is going on here? If this was any other wiki, we would note that their is community consensus, and implement the change.
+
+The only thing slightly iffy thing here is to be able to let anons create pages in this namespace - that might require someone taking 10 seconds writing a hook (Or even better, someone fixing mediawiki so we have proper per-namespace permissions). However that can easily be done later. the robots thing is already a config option.
+
+Furthermore, all these various ""config"" related changes are trivial to change after the fact if people discover they want something different.
+
+New namespaces get created for other wikis all the time. This has traditionally been something that has entirely been up to the community to decide for themselves. I don't understand why enwiki gets treated so differently.
+
+>Key minimum requirements for launch are being hashed out at
+>https://www.mediawiki.org/wiki/Draft_namespace 
+
+Kind of seems odd this is being written up on mediawiki.org, for something that is in essence a config change coming out of enwikipedia community. Its not like there are non-user facing technical hurtles to surmount. There's no new db schema being proposed or anything like that.",1385596241,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Key minimum requirements for launch are being hashed out at https://www.mediawiki.org/wiki/Draft_namespace .  Some are pretty definite already (e.g. NOINDEX), while others are not 100% certain yet.  We may also have omitted some questions, so if you think of any that need to be resolved before launch, add them.",1385595280,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #22)
+> Ori's point was partly that acting in a hasty manner and populating the
+> namespace with content right, so that it's less flexible to essential changes
+> in the near future, *will* make the situation worse.
+
+Worse than hypothetical future is not worse than the present, so it's still a gradual improvement. Populating a ""drafts"" namespace doesn't seem to pose any risk to me: it's completely normal to move pages in and out new namespaces (Wikipedia<->Draft in this case) and this namespace is supposed to be purged regularly anyway. If you're so worried about workload, you can run a move script yourself when it's time; the only real risk when creating namespace is forgetting to run namespaceDupes.php‎.",1385537497,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #21)
+> (In reply to comment #19)
+> 
+> I agree with most of what you wrote, though a lot of it is relevant to bug
+> 57315 rather than this bug.
+> 
+> > Steven Walling is well-positioned to enlist some developer time within the
+> > Foundation for this project. If he is asking for additional time to grok the
+> > requirements, the sensible and gracious thing to do is to grant it. If you
+> > can railroad the patch through today, you can do it two weeks from now, too.
+> 
+> Requirements are still being gathered. As I understand it, no implementation
+> ideas have been formally proposed yet, much less coded, and we're fast
+> approaching the U.S. holiday season. I don't imagine we'll see any real work
+> on
+> bug 57315 before 2014. While it's possible to wait a few weeks (or months) to
+> add this namespace, I don't see any benefit to doing so. The current system
+> is
+> so bad and so hackish that there's very little that could make it worse.
+
+Ori's point was partly that acting in a hasty manner and populating the namespace with content right, so that it's less flexible to essential changes in the near future, *will* make the situation worse. Or at the very least, replicate the current bad situation. Considering the patch you put up for review literally does replicate the current problem (IPs can't create actual drafts, just Talk pages), I am convinced by this argument. 
+
+What I've asked for, and stated on-wiki, is that we need to at least do two things:
+
+1). Actually write down the requirements for the namespace, and agree on them. I can commit to making this happen _far_ before 2014. Ideally in the current week.
+2). Test the functionality on Labs or similar environment before deploying, with feedback from the community. People have responded positively to this idea, and we're using it with features like Flow as well. Giving people a chance to test drive the new namespace before dropping it on enwiki seems wise to me. 
+
+Neither of these things necessarily require that all the potential features extending and improving the namespace be implemented. I do believe in releasing something that's ""minimum viable product"" quickly as is reasonable. But considering we have no agreement on what the minimum viable product is, we need to settle that first.",1385516798,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #19)
+
+I agree with most of what you wrote, though a lot of it is relevant to bug 57315 rather than this bug.
+
+> Steven Walling is well-positioned to enlist some developer time within the
+> Foundation for this project. If he is asking for additional time to grok the
+> requirements, the sensible and gracious thing to do is to grant it. If you
+> can railroad the patch through today, you can do it two weeks from now, too.
+
+Requirements are still being gathered. As I understand it, no implementation ideas have been formally proposed yet, much less coded, and we're fast approaching the U.S. holiday season. I don't imagine we'll see any real work on bug 57315 before 2014. While it's possible to wait a few weeks (or months) to add this namespace, I don't see any benefit to doing so. The current system is so bad and so hackish that there's very little that could make it worse.",1385514221,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #16)
+> I might even support it, once it's clear what the proposed changes are (all
+> I've seen spelled out so far are a new landing page and some sort of special
+> permission changes, which are both still pretty vague).
+
+It's vague because that's one of the things we're still trying to figure out (before adding the namespace).",1385505493,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #4)
+> As I stated at the other bug, these are not questions that need to block
+> creation of the namespace.
+
+There are no blockers; you can have the namespace. I do think it is being rushed, though.
+
+I never quite understood how consensus is determined, so I may be getting this wrong, but reading over the RFC, I think a detect a shared conviction that a namespace by itself may not do the trick, and that some additional software support may be required. This much is entailed by the very thought of having a namespace in the first place, right?
+
+Once the namespace exists, it will begin to be populated with content, and at that point the range of things you can practically do with it are severely limited. For example: MediaWiki provides an abstract framework for expressing an edit and review workflow called ContentHandler (<http://www.mediawiki.org/wiki/Manual:ContentHandler>). Taking the default content handler for articles (WikitextContentHandler) as a starting point and extending it so that it provides guided page creation and peer review interfaces seems like a potentially fruitful direction to take, and saddling it with the additional requirement of migrating existing content is a great way to ensure that it will never get done.
+
+Steven Walling is well-positioned to enlist some developer time within the Foundation for this project. If he is asking for additional time to grok the requirements, the sensible and gracious thing to do is to grant it. If you can railroad the patch through today, you can do it two weeks from now, too.
+
+I would recommend making the mapping of requirements collaborative by provisioning a MediaWiki instance in Labs, granting shell access to all interested parties, and using it as a staging area for hashing out how the namespace would work and how its purpose and function would be presented to editors.",1385492693,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #17)
+> I am fine with whichever proposal
+> gets
+> this done, as long as it does through whatever procedure it is normally
+> expected to.
+
+Don't worry: the procedure is [[m:Requesting wiki configuration changes]]. It seems to be clear that there is consensus and we already have a patch, so now you only need the patch to be approved by a shell user, after it's verified that the code in question does what asked. Typically, that takes about a week or two of waiting; namespace creation is among the simplest and most routinary configuration changes happening in here, so I don't expect any problem.",1385486372,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #14)
+> (In reply to comment #2)
+> > (In reply to comment #1)
+> > > Like I said on bug 57315, there are still too many unanswered questions about
+> > > this namespace to roll it out in a hasty way.
+> > 
+> > Does anyone else share your view?
+> 
+> I fully share this view.  
+
+As do I. If a quick six-lines-of-code patch can work, then that is good. But if the long run requires a more comprehensive approach, then so it be. As far as I am concerned, the enwiki just needs the namespace in a reasonable amount of time. If those two requirements are met, I am fine with whichever proposal gets this done, as long as it does through whatever procedure it is normally expected to.",1385474421,PHID-USER-65pjzcmoby2fsgzdrfjq,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**equazcion** wrote:
+
+(In reply to comment #14)
+> I fully share this view.  I've been toying with the idea of an extension here
+> for some time.  There is this new namespace, there is the new userright that
+> the community agreed upon, there are the common complaints that AfC templates
+> and scripts don't do this or that (and can't be modified as the wiki stands
+> to
+> without creating an on-by-default gadget or adding code to
+> MediaWiki:Common.js
+> or possibly by creating a guided tour (which is a fairly new option that was
+> introduced as I've been developing the extension)).  There are a LOT of
+> factors
+> that need to go into draft creation alone, not to mention I think (as I
+> stated
+> in bug 57315) that I think requested articles could be rolled into articles
+> for
+> creation and the whole process could be streamlined.  I'm constantly seeing
+> stuff about editor retention and we need to do this and that and that is
+> great,
+> but what I have a problem with is the fact that our current fairly difficult
+> to
+> use system turns new editors away... Maybe stating the obvious, but if there
+> are fewer new editors, then there is a much smaller pool to work from for
+> retention.
+
+It's fine that you share Steven's view on that -- but the question was whether these things are a block to the Draft namespace implementation. An extension may be a good idea and I don't necessarily dispute that, but it wasn't part of this proposal and it regards changes that should be proposed separately. I might even support it, once it's clear what the proposed changes are (all I've seen spelled out so far are a new landing page and some sort of special permission changes, which are both still pretty vague).",1385472289,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #4)
+> As I stated at the other bug, these are not questions that need to block
+> creation of the namespace. It rather seems apparent that you saw this
+> proposal
+> as something other than it was -- a more substantial change to AFC that you
+> had
+> already envisioned prior -- but it wasn't, and the closure states that pretty
+> clearly. 
+> 
+> Anyone is allowed to create drafts because anyone was allowed to before. This
+> is just a change to their location.
+> 
+> Publishing drafts will continue to merely require a move to mainspace,
+> because
+> that's all that was required before. 
+> 
+> We don't need to tell anyone anything other than through altered
+> documentation
+> at AFC, because nothing other than that will be changing. 
+> 
+> Phrasing these added proposals as questions doesn't make them requirements
+> that
+> apply to this proposal. They are merely possible additions that should be
+> proposed and discussed separately. As concerns this proposal, we need only
+> create a draft namespace.
+
+Wait, IP editors aren't allow to create pages in this new draft: namespace?  They will still have to create in Draft_talk:?  At least that's what I'm reading here, exactly the same as before only people will use ""Draft( talk):"" instead of ""Wikipedia( talk):Articles for creation/""?",1385471608,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #2)
+> (In reply to comment #1)
+> > Like I said on bug 57315, there are still too many unanswered questions about
+> > this namespace to roll it out in a hasty way.
+> 
+> Does anyone else share your view?
+
+I fully share this view.  I've been toying with the idea of an extension here for some time.  There is this new namespace, there is the new userright that the community agreed upon, there are the common complaints that AfC templates and scripts don't do this or that (and can't be modified as the wiki stands to without creating an on-by-default gadget or adding code to MediaWiki:Common.js or possibly by creating a guided tour (which is a fairly new option that was introduced as I've been developing the extension)).  There are a LOT of factors that need to go into draft creation alone, not to mention I think (as I stated in bug 57315) that I think requested articles could be rolled into articles for creation and the whole process could be streamlined.  I'm constantly seeing stuff about editor retention and we need to do this and that and that is great, but what I have a problem with is the fact that our current fairly difficult to use system turns new editors away... Maybe stating the obvious, but if there are fewer new editors, then there is a much smaller pool to work from for retention.",1385471383,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","I've not read the discussion but I have to say the closure is quite straightforward: «the heart of the proposal: a new namespace for Drafts [...] This community discussion does not change the AfC process». It obviously doesn't entail any extension, nor special user permissions for the namespace for that matter; those can come later if wanted.",1385447453,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","Change 97675 had a related patch set uploaded by MZMcBride:
+Create ""Draft"" namespace on the English Wikipedia
+
+https://gerrit.wikimedia.org/r/97675",1385439190,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #6)
+> > We still need to specify things like:
+> > 
+> > * who is allowed to create drafts. (e.g. Are anonymous users allowed to do
+> > so?
+> > I assume so but the proposal summary and closure don't specify.)
+> > * how to publish drafts
+> > * who is allowed to publish drafts
+> > * how do we tell users they can create/publish drafts, on search, redlinks,
+> > and other places
+> > * do we want to let people make drafts of pages that already exist?
+> 
+> None of this is relevant to adding a new namespace and you know this.
+
+All of those questions are relevant.  Some I certainly consider blockers.  For example, I am strongly inclined to determine an initial permission model before we deploy it (that's not the only one).  
+
+It is irrelevant how many lines it takes to create a dumb namespace.  The questions are how it will function initially (which may include A/B testing multiple possibilities) and how it will relate to other features.",1385437989,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #3)
+> (In reply to comment #2)
+
+> * who is allowed to create drafts. (e.g. Are anonymous users allowed to do
+> so?
+> I assume so but the proposal summary and closure don't specify.)
+
+I've left Tom Morris (the RfC closer) a note asking him to clarify - [[Special:Permalink/583319065]].
+
+That said, I don't think that question specifically blocks the creation of the namespace, a hook can be added to userCan later on to allow anon's to create pages in it.",1385429337,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**equazcion** wrote:
+
+(In reply to comment #7)
+> I'm not talking about articles for creation at all. That's a community
+> process,
+> not a software feature that has direct overlap with a drafts namespace, with
+> the exception of what we want to appear on search.
+
+The accepted proposal we seek to implement here doesn't concern any software feature. If you want one, propose one separately. You've stated nothing that couldn't also be applied without a draft namespace, or after it's already created. They are separate suggestions, and they may be useful ones, but still have no bearing on the implementation of this namespace.",1385429155,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #6)
+> We're talking about a two-line configuration change here.
+
+Probably a few more than two lines to create the namespace, the talk namespace, and set noindex. Maybe a half-dozen to a dozen lines? In any case, this seems fairly easy to implement to me.",1385429101,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+> None of this is relevant to adding a new namespace and you know this.
+> 
+> If you want to improve the articles for creation process, great! I've filed
+> several bugs in this area. :-)  No objections from me.
+> 
+> But the two ideas (adding a new namespace on the English Wikipedia and
+> improving the articles for creation process) are not tied to each other in
+> any
+> meaningful way. We're talking about a two-line configuration change here.
+
+I'm not talking about articles for creation at all. That's a community process, not a software feature that has direct overlap with a drafts namespace, with the exception of what we want to appear on search.",1385428945,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #3)
+> This is not about consensus. We don't know basic things about how the
+> namespace would work.
+
+I'm pretty sure we know how namespaces work. :-)
+
+> We still need to specify things like:
+> 
+> * who is allowed to create drafts. (e.g. Are anonymous users allowed to do
+> so?
+> I assume so but the proposal summary and closure don't specify.)
+> * how to publish drafts
+> * who is allowed to publish drafts
+> * how do we tell users they can create/publish drafts, on search, redlinks,
+> and other places
+> * do we want to let people make drafts of pages that already exist?
+
+None of this is relevant to adding a new namespace and you know this.
+
+If you want to improve the articles for creation process, great! I've filed several bugs in this area. :-)  No objections from me.
+
+But the two ideas (adding a new namespace on the English Wikipedia and improving the articles for creation process) are not tied to each other in any meaningful way. We're talking about a two-line configuration change here.",1385428674,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #4)
+> As I stated at the other bug, these are not questions that need to block
+> creation of the namespace. 
+
+Deciding the basics of who can do what in a new namespace, and how, are things that block creating a new namespace. 
+
+I really don't see why you're in such a huge hurry. This is quite a large new feature, so understanding the basics of how it will function in relation to regular page creation, the permissions involved, and so on seem quite obviously basic things we need to figure out before we deploy a major new namespace to English Wikipedia.",1385428346,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**equazcion** wrote:
+
+As I stated at the other bug, these are not questions that need to block creation of the namespace. It rather seems apparent that you saw this proposal as something other than it was -- a more substantial change to AFC that you had already envisioned prior -- but it wasn't, and the closure states that pretty clearly. 
+
+Anyone is allowed to create drafts because anyone was allowed to before. This is just a change to their location.
+
+Publishing drafts will continue to merely require a move to mainspace, because that's all that was required before. 
+
+We don't need to tell anyone anything other than through altered documentation at AFC, because nothing other than that will be changing. 
+
+Phrasing these added proposals as questions doesn't make them requirements that apply to this proposal. They are merely possible additions that should be proposed and discussed separately. As concerns this proposal, we need only create a draft namespace.",1385427644,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > Like I said on bug 57315, there are still too many unanswered questions about
+> > this namespace to roll it out in a hasty way.
+> 
+> Does anyone else share your view?
+
+This is not about consensus. We don't know basic things about how the namespace would work. We still need to specify things like:
+
+* who is allowed to create drafts. (e.g. Are anonymous users allowed to do so? I assume so but the proposal summary and closure don't specify.)
+* how to publish drafts
+* who is allowed to publish drafts
+* how do we tell users they can create/publish drafts, on search, redlinks, and other places
+* do we want to let people make drafts of pages that already exist?
+
+There are numerous other smaller details to work out as well.",1385427328,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","(In reply to comment #1)
+> Like I said on bug 57315, there are still too many unanswered questions about
+> this namespace to roll it out in a hasty way.
+
+Does anyone else share your view?",1385426645,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+"Create ""Draft"" namespace on the English Wikipedia","**swalling** wrote:
+
+Like I said on bug 57315, there are still too many unanswered questions about this namespace to roll it out in a hasty way. Please be patient. It's only been a week since the RFC on enwiki was closed.",1385426291,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-atmvpvsegseglymt64gn,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"The browser tests for MobileFrontend should be triggered by Gerrit just like it is going to be the case for ULS (T54120) or VisualEditor (T55691).
+
+The tests need to be carefully filtered out since they are expecting content or behavior which are not to be found on a freshly installed wiki.
+
+
+CC:
+- Zeljkof  our Selenium Guru
+- Arthur our Mobile scrum master
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53691
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52120",1385415180,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-bphj5ytqpxc666bbt2xo,task_description,resolved
+browsertests: triggers for MobileFrontend,Reflecting the true state.,1440045549,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"We do not have the capacity yet to had browser tests on patchset proposals. The VE (T55691) and ULS (T54120) jobs have been removed because they were too slow and ill conceived.
+
+We will revisit it when we have improved the browser test speed (ex: {T92613}) and most importantly the CI isolation project which will provide us fresh VM to install all of what we need ensuring a clean environment.
+
+I guess when we are ready we will poke the parent task {T55697}.",1427208623,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,Adding Dan to this bug as his work on MF tests in Vagrant will probably inform some of this.,1405455476,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"Change 97497 abandoned by Hashar:
+QA: profile for default settings
+
+Reason:
+Indeed those preferences have been moved elsewhere (mediawiki selenium gem).
+
+https://gerrit.wikimedia.org/r/97497",1391529850,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,Patchset 9 of https://gerrit.wikimedia.org/r/#/c/97497/ pass on a fresh wiki with mobilefrontend having no specific configuration. That is done by ignoring any scenario relying on a specific feature/setting on the target wiki.,1386692405,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"Most of the tests do not work against a freshly installed wiki. Either because of Watir timeout or because the test is expecting something which is only on some specific wiki.
+
+The features definition need a bunch of improvements before we can trigger the tests from Gerrit.",1385479428,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+browsertests: triggers for MobileFrontend,"Change 97497 had a related patch set uploaded by Hashar:
+browsertests: profile for default settings
+
+https://gerrit.wikimedia.org/r/97497",1385478671,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bphj5ytqpxc666bbt2xo,task_subcomment,NA
+VisualEditor: Make fakeIme QUnit testing more rigorous,"The fakeIme tests pass IME-like event sequences into the CE Surface and check that it behaves reasonably. Currently the tests are too weak, in that they don't detect certain problematic behaviour:
+
+1. Calls to the simulated preventDefault do nothing at all.
+
+2. Some tests are disabled because they fail.
+
+3. Only plain text in a single blank paragraph is tested.
+
+4. In real usage, changing the CE surface content/selection during input will close the candidate window and commits the candidate text. The tests currently do not check for this. The test data does not show which pieces of text are candidates, since there is no way to detect this from Javascript, but we can infer that at least any text which is subsequenctly changed was a candidate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385387460,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-fxi2rdyqsib2css4ztr4,task_description,open
+VisualEditor:  Please add a shortcut for adding a reference to a page (?which?),"Intention:
+Add a reference
+
+Steps to Reproduce:
+1. Took hands off the keyboard.
+2. Grabbed mouse.
+3. Clicked ""More"" menu.
+4. Scrolled down.
+5. Clicked on ""Reference"".
+
+Actual Results:  
+Works as designed.
+
+Expected Results:  
+That it would work better than as designed:  Leave hands on keyboard, press a couple of keys, and have the reference dialog pop open.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385161380,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jxecea6ezbybvmmufndn,task_description,duplicate
+VisualEditor:  Please add a shortcut for adding a reference to a page (?which?),"My first choice is ctrl-alt-r, which unfortunately is in use as a shortcut to open Special:RecentChanges, and command-R is in use by the browsers to reload pages.
+
+I'll personally use this enough that I'll be able to get used to just about anything.  Maybe ctrl-alt-1, if you want this to work across multiple languages?  Adding citations has ""number one"" importance to many Wikipedia editors.",1385400305,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jxecea6ezbybvmmufndn,task_subcomment,NA
+VisualEditor:  Please add a shortcut for adding a reference to a page (?which?),"Let's avoid symbols not available on non-English keyboards for a start, like backslash :p",1385397735,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-jxecea6ezbybvmmufndn,task_subcomment,NA
+VisualEditor:  Please add a shortcut for adding a reference to a page (?which?),What would you suggest as the shortcut?,1385394792,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jxecea6ezbybvmmufndn,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Copied from bug 43058 
+
+Screenshot of editing a math block
+
+Some small tweaks are needed to the dialog box. Editing the last equation at
+https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+there are a a few problems
+
+1) The dialog obscures the actual equation
+2) The dlalog is too small to see the whole source text of the equation
+
+This could be solved the making the dialog, moveable and resizeable.
+
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=12223
+
+//attachment missing in source//",1385145960,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_description,open
+Allow the VE dialog for math elements to be movable and resizable,"In T51969 TrevorParscal write
+
+> The idea of the dialog being modal is that you aren't multi-tasking with it at all.
+
+There is a question as to whether a modal dialog is appropriate here or a modeless dialog. A typical modal dialog would be password entry which must happen before continuing. 
+
+Here we are multi-tasking editing an equation is a subtask of the job of editing the whole page. You do want to switch back and forward to see how changing the equation will affect the look of the whole page. To me, the use-case suggests a modeless dialog is appropriate here. ",1573915077,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,">>! In T59437#5658604, @John_Broughton wrote:
+> https://ux.stackexchange.com/questions/81134/should-modal-dialogs-be-movable seems to show a (rough) consensus that when a proposed solution to a dialog is to make it moveable, the dialog itself is poorly designed. That implies looking for a different solution that addresses the underlying user problem.
+
+See discussion of this in T51969 ",1573913848,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"https://ux.stackexchange.com/questions/81134/should-modal-dialogs-be-movable seems to show a (rough) consensus that when a proposed solution to a dialog is to make it moveable, the dialog itself is poorly designed. That implies looking for a different solution that addresses the underlying user problem.",1573598939,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"The second point in this task is really annoying when working with large equations; The dialog is too small to see the whole source text of the equation.
+
+Workaround is to use the plain old editor, but then it is easy to do an error and the whole equation bombs out.",1538784516,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"This is only done for auto-resizing and auto-positioning, not manual resizing and positioning (""dragging"") which this bug is asking for (and which depends on bug 49969). Reopening.",1413835705,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"**physik** wrote:
+
+Change was merged. Seems to be fixed.",1413748422,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"**physik** wrote:
+
+Can someone look at https://gerrit.wikimedia.org/r/#/c/105647/ ... It would be great to merge this before it has to rebased manually again.",1391900695,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Re-positioning of OOjs UI windows is a really major piece of work, yes.
+
+Re-sizing is very do-able, however.",1387222681,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"I'm still trying to get a Google Code-in task or more out of these VE Math plugin reports...
+
+If I understand the comments, the ""movable"" part can't be fixed for this plugin because it depends on VE's current capacity to do so (bug 49969), right?
+
+Can the size of the window be controlled? If so, could this be a GCI task?",1387222391,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"(In reply to comment #5)
+> Change 97750 had a related patch set uploaded by Catrope:
+> Fix moving over an image with the arrow keys in Firefox
+> 
+> https://gerrit.wikimedia.org/r/97750
+
+Mis-targeted, sorry!",1385485858,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Change 97750 had a related patch set uploaded by Catrope:
+Fix moving over an image with the arrow keys in Firefox
+
+https://gerrit.wikimedia.org/r/97750",1385485737,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"(In reply to comment #3)
+> Just to note I'm just an end user, so don't really know much about how the
+> Visual Editor code works. It might be an idea to consult with the VE people
+> for
+> the best way to achieve this. I've not found any other VE dialog which is
+> movable or resizable, so I'm not sure if there is code you can copy.
+
+See bug 49969 (and maybe bug 49549).
+
+> (...)
+> What might also be possible would be to detect if the equation is inline or a
+> block mode.
+
+See bug 12223.",1385224372,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Just to note I'm just an end user, so don't really know much about how the Visual Editor code works. It might be an idea to consult with the VE people for the best way to achieve this. I've not found any other VE dialog which is movable or resizable, so I'm not sure if there is code you can copy.
+
+What is really important is that the box is big enough. Following from Helders comment you could detect the size of the original equation and size accordingly. 
+
+What might also be possible would be to detect if the equation is inline or a block mode. (In the tex world this would be $eqn$ vrs $$eqn$$) a larger edit window is preferred for block mode equations. Its a little tricker to detect the difference in wikitext, suronding text on the same line indicates inline mode. Being a single item in a list element <li><math> ...</math></li> indicates block mode.",1385224018,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"Cross-posting from previous bug
+
+@Richard/others: Thinking about making the dialog draggable and resizable...
+
+The solution I initially think of is installing jquery.ui and then adding some
+parameters to OO.ui.Window that allow it to be made resizable and/or draggable.
+However, if I recall correctly one of the principles of OOJS was to be
+self-contained... so would this be wrong? Could someone else with a bit more
+firsthand experience chime in here?",1385161048,PHID-USER-wgpse4towjiaqbzotzgo,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+Allow the VE dialog for math elements to be movable and resizable,"But it should also be smart enough not to present a tiny box when the formula is already very large. E.g. the last example from
+https://www.mediawiki.org/w/index.php?title=VisualEditor:TestMath&oldid=749189&veaction=edit
+
+Otherwise the user will need to resize the box on every formula of some pages",1385146969,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-wsfvt6m45cmlqsrx2ft3,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"There are many templates in Wikipedia that create right floated content other than info boxes and images.
+
+Examples are for instance Template:Stack, but there are many similar templates. These are currently not rendering as right floated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384944720,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-22g4j3j7uwe6d4goqunf,task_description,resolved
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"I vaguely think there was another task (since fixed) which this duplicates, but I have no idea what it was called.",1427403972,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,">>! In T59296#1154512, @TheDJ wrote:
+> If I remember correctly, it would be that the right floating stack, was opened in VE as full width and left aligned, pushing all visual adjacent content to be positioned underneath the stack template.
+
+Seems to be fixed to me - not happenning anymore: inserting Stack template(with/without specifying float- right) will position the template on the right.
+
+Btw, left - puts the template on the left.
+
+",1427403906,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"If I remember correctly, it would be that the right floating stack, was opened in VE as full width and left aligned, pushing all visual adjacent content to be positioned underneath the stack template.",1427402176,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"I checked in production some samples from https://en.wikipedia.org/wiki/Template:Stack:
+
+ {{stack |[[File:Test.png|thumb|right|Example 2a]] [[File:Test.png|thumb|right|Example 2b]]}}
+
+Without  float=left/right parameter - default is right. Is that what's been fixed? ",1427401123,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,This seems mostly fixed to me. Is that correct team ?,1427400395,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Right floated elements other than images and info boxes are not placed correctly,"This is caused by the div block surrounding it, that should receive 'similar' traits in that case.
+
+It is worsened, because in the case of stack in particular also takes fullwidth, due to the broken implementation of inline images with captions. These currently feature a figcaption that has display block, and no width constraint (shouldn't be allowed to be wider than the image frame, but it is).",1384945379,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-22g4j3j7uwe6d4goqunf,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,"https://en.wikipedia.org/w/index.php?title=Mozarteum_University_of_Salzburg&oldid=582046262
+
+https://parsoid.wmflabs.org/enwiki/Mozarteum_University_of_Salzburg?oldid=582046262
+
+Yet when opened in VE, the dom shows border=""1""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384944240,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_description,declined
+VisualEditor: Table with attribute border=0 is displayed as if border=1,"(In reply to Raimond Spekking from comment #5)
+> Sorry, but border=1 is very different from border=0. Your ""some light
+> default styling"" shows a border. This means, this bug is not fixed. 
+> 
+> If it has no priority, ok. But please leave it open.
+
+No. VisualEditor is not intended to be and will not reach a perfect simulacrum of read mode. First and foremost, VisualEditor is an editor; the borders are explicitly shown to make editing tables sane.",1412114211,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,"Sorry, but border=1 is very different from border=0. Your ""some light default styling"" shows a border. This means, this bug is not fixed. 
+
+If it has no priority, ok. But please leave it open.",1412096474,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,"(In reply to Raimond Spekking from comment #3)
+> Maybe a regression: the VE renders the table in
+> https://de.wikipedia.org/w/index.
+> php?title=Landschaftsversammlung_Rheinland&oldid=134477792 with border=1
+> instead of the given border=0. Or is this another bug?
+
+This is what ""some light default styling"" looks like.",1412096042,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,Maybe a regression: the VE renders the table in https://de.wikipedia.org/w/index.php?title=Landschaftsversammlung_Rheinland&oldid=134477792 with border=1 instead of the given border=0. Or is this another bug?,1412060228,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,We fixed this last week with some light default styling,1404172600,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+VisualEditor: Table with attribute border=0 is displayed as if border=1,*** Bug 57368 has been marked as a duplicate of this bug. ***,1385123360,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-sgdd3ezfcgiwqqplkpsn,task_subcomment,NA
+Images: {{Gallery}} template parsed differently by PHP parser and Parsoid,"{{Gallery}} is implemented by a Lua template here: https://en.wikipedia.org/wiki/Module:Gallery
+
+See example below
+
+```
+[subbu@earth lib] cat /tmp/gallery
+{{Gallery
+| lines = 2
+| File:Arc de Triomphe de l'Etoile - Projet Chalgrin - 02.jpg|1806: Architectural drawing project of [[Jean Chalgrin]]
+}}
+[subbu@earth lib] node parse --dump tplsrc < /tmp/gallery
+=================================
+Template:Gallery
+---------------------------------
+<table style=""background:transparent;border:1px solid #f0f0f0;margin-top:0.5em;""><tr><td><table style=""width:200px;float:left;border-collapse:collapse;margin:3px;""><tr><td style=""height:200px;border:1px solid #CCCCCC;background-color:#F8F8F8;padding:0px;text-align:center;"">[[File:Arc de Triomphe de l'Etoile - Projet Chalgrin - 02.jpg|center|border|180x180px|alt=|1806: Architectural drawing project of [[Jean Chalgrin]]]]</td></tr><tr style=""vertical-align:top;""><td style=""display:block;font-size:1em;height:3.2em;padding:0px;""><div class=""gallerytext"" style=""height:3.1em;width:187px;line-height:1.3em;padding:2px 6px 1px 6px;overflow-y:auto;margin:0px;border:none;border-width:0px;"">1806: Architectural drawing project of [[Jean Chalgrin]]&nbsp;</div></td></tr></table></td></tr></table>
+---------------------------------
+```
+
+So, the {{Gallery}} template emits the image in a <td> and the caption in a separate <tr> below. As far as I can tell, Parsoid therefore (correctly) duplicates the caption in both the <tr>s. However, somehow, the PHP parser magically suppresses the first caption (see https://en.wikipedia.org/w/index.php?title=User:Ssastry/sandbox&oldid=582405791)
+
+This is based on a report on VE/F @ https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=582367222#Pages_that_go_wrong_in_VE",1384885800,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-psruyhkjwka6oelbiqmt,task_description,resolved
+Images: {{Gallery}} template parsed differently by PHP parser and Parsoid,"Seems to be covered by,
+https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.skinning/content.parsoid.less#L150-L158",1491864814,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-psruyhkjwka6oelbiqmt,task_subcomment,NA
+Images: {{Gallery}} template parsed differently by PHP parser and Parsoid,"Is this still an issue?
+
+https://en.wikipedia.org/api/rest_v1/page/html/User:SSastry%20(WMF)%2Fsandbox/582405791 and https://en.wikipedia.org/w/index.php?title=User:Ssastry/sandbox&oldid=582405791 look identical to me.",1491863620,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-psruyhkjwka6oelbiqmt,task_subcomment,NA
+Add a link to the new guided format in the Navigation menu,"Pretty much what the Summary says:
+I would have used the new format but I keep forgetting how to reach it!
+I had proposed that the link reads ""Enter a new bug (guided)"" but in the end everything is actually ok for me as long as it's easy to discover for everyone, obviously.
+Cheers.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1384878480,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-qjeerptbgnssiimoy3ki,task_description,declined
+Add a link to the new guided format in the Navigation menu,"http://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia&component=Bugzilla now says at the top ""If you prefer a simpler way to create a bug report, try the guided bug entry form."" linking to it. To me this feels sufficient.",1389089823,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-qjeerptbgnssiimoy3ki,task_subcomment,NA
+Add a link to the new guided format in the Navigation menu,"Some products need that kind of depth that the new guided form provides (i.e., VisualEditor :p ). I guess experienced users can find the way to add the link to the left column anyway, if they need to.",1384879246,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-qjeerptbgnssiimoy3ki,task_subcomment,NA
+Add a link to the new guided format in the Navigation menu,"I wonder if that wording would be clear enough if both links provide the
+same functionality.
+
+So I have the naive idea that this could be based on how ""new"" (recently
+registered) the Bugzilla user account is. I have no idea if I have
+sufficient coding skills though. :)
+bugzilla.mozilla.org displays a ""(New to Bugzilla)"" string next to some
+user names, so it must be possible to gather such information and use
+it. I (or somebody else) ""just"" need to investigate their code a bit...",1384879011,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-qjeerptbgnssiimoy3ki,task_subcomment,NA
+VisualEditor: Don't use deprecated mw.util.wikiGetlink function,"When in debug mode the browser console always shows a message
+
+MWDeprecationWarning: Use of ""wikiGetlink"" property is deprecated. Use mw.util.getUrl instead.
+
+caused somewhere in VE's startup module. When you are trying to find uses of deprecated functions in your own scripts this message is a bit annoying, as you can't do anything about it and it shows up on every page. So please replace all calls to .wikiGetlink with .getUrl (in startup module and possibly elsewhere).
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1384856940,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-qf5vsjv66k5lg7t737hz,task_description,resolved
+VisualEditor: Don't use deprecated mw.util.wikiGetlink function,"This was done in gerrit 94263 which is in wmf3, which will be deployed to Wikipedias on Thursday.",1384857395,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qf5vsjv66k5lg7t737hz,task_subcomment,NA
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction","Steps to reproduce:
+
+
+1.Click on the edit button
+2.Click on a link and click on the link insertion icon.
+3.Without making any change just close the link inspector
+
+Observed Result:
+The ""Save Page"" button becomes active though if you review the changes it will say that this revision matches the lastest version of the page.
+
+Expected Result:
+If there is not modification in the content it is probably better to keep the ""Save Changes"" button inactive.
+
+Sample Page:
+
+https://en.wikipedia.org/w/index.php?title=Tea_tree_oil&veaction=edit
+
+Browser: Chrome Version 26.0.1410.65
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384800900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wgfiyucmntqggrzaytku,task_description,resolved
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction",Verified the fix in production (en.wiki),1403301720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wgfiyucmntqggrzaytku,task_subcomment,NA
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction",Verified the fix in test2 running wmf 9,1402694232,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wgfiyucmntqggrzaytku,task_subcomment,NA
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction",Now fixed by Trevor's work on the link inspector and window transactions.,1402549147,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wgfiyucmntqggrzaytku,task_subcomment,NA
+"VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction",Instead we should check to see if the new annotation is actually different before applying it.,1384841672,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wgfiyucmntqggrzaytku,task_subcomment,NA
+VisualEditor: Allow users to set/edit __HIDDENCAT__ status in the page metadata panel,"Checkbox flag, category namespace only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754520,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fdmergs3gf3rbdk5e44x,task_description,resolved
+VisualEditor: Allow users to set/edit __HIDDENCAT__ status in the page metadata panel,"Change 126015 merged by jenkins-bot:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1398123272,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fdmergs3gf3rbdk5e44x,task_subcomment,NA
+VisualEditor: Allow users to set/edit __HIDDENCAT__ status in the page metadata panel,"Change 126015 had a related patch set uploaded by Alex Monk:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1397579986,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fdmergs3gf3rbdk5e44x,task_subcomment,NA
+VisualEditor: Allow users to set/edit __HIDDENCAT__ status in the page metadata panel,"Change 95726 had a related patch set uploaded by Jforrester:
+[WIP] Create remaining meta items in DM
+
+https://gerrit.wikimedia.org/r/95726",1384754690,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fdmergs3gf3rbdk5e44x,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Syntax highlighting doesn't work with Flow.
+
+Example input:
+
+```
+<syntaxhighlight lang=""css"">
+.foo {
+    font-weight: bold;
+}
+</syntaxhighlight>
+```
+Output is not appropriately highlighted: https://www.mediawiki.org/wiki/Topic:Sb29d13fybslwgjh
+It should look like this: https://www.mediawiki.org/w/index.php?title=User:Quiddity_%28WMF%29/sandbox&oldid=1397603
+
+----
+TheDJ notes (in comment below) that this might be related (plus its blockers): {T69540}",1384750140,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_description,open
+Flow: syntax highlighting tags (GeSHi) don't get styled,"This issue also affects the `highlight=` attribute, by the way – marked lines aren’t distinguished either.",1616345188,PHID-USER-7raa3vx5zsq6a56gil3q,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,">>! In T59159#6923746, @Krinkle wrote:
+> As a recent example, this can be seen at <https://www.mediawiki.org/wiki/Topic:W5dh34nv202fzq7f>.
+
+Other examples of likely affected features include Cite `<ref>`, Math, WikiHiero, TemplateData docs, TimedMediaHandler video player, 3D graphics, and more ([Codesearch](https://codesearch.wmcloud.org/deployed/?q=par.%2BaddModuleStyles&i=nope&files=&excludeFiles=&repos=))",1616029370,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"As a recent example, this can be seen at <https://www.mediawiki.org/wiki/Topic:W5dh34nv202fzq7f>.",1616028925,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Note: the ResourceLoader module missing is `ext.pygments`. You can load it unconditionally using `mw.loader.load( 'ext.pygments' )`, and I guess you could add this to your `common.js` to work around this bug if it’s very important :)",1517502237,PHID-USER-hrcsuxxosiyjqpef64tc,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Ok. I make rollback to 1.28.2
+No one fixes the bug.",1507572566,PHID-USER-ckht4z43xrkznivuzxeu,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,News? Solutions? Anything?,1507204315,PHID-USER-ckht4z43xrkznivuzxeu,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,{T174374} may solve this task. I'll ask.,1505898511,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,Any news?,1505857887,PHID-USER-ckht4z43xrkznivuzxeu,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,">>! In T59159#3548628, @aka_sektor wrote:
+> @Aklapper : Just let them return it as it was in 1.28.2
+> I do not know what exactly they broke.
+
+I only know that this problem affects board too: https://www.mediawiki.org/w/index.php?title=Flow/Sandbox&header_revId=twwnd0zvz6kx6bhb&action=view-header",1504100705,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"@Aklapper : Just let them return it as it was in 1.28.2
+I do not know what exactly they broke.",1503584278,PHID-USER-ckht4z43xrkznivuzxeu,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"@aka_sektor: The status of this task is ""open"", see the upper corner. Hence this issue is not fixed and we all know that. :) No need to comment and tell. If you would like to [[ https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker | contribute a code change ]] to fix this problem, you are very welcome to use [[ https://www.mediawiki.org/wiki/Developer_access | developer access ]] to submit the proposed code changes as a [[ https://www.mediawiki.org/wiki/Git/Tutorial | Git branch directly into Gerrit ]].",1503584022,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Setup 1.29.1: https://releases.wikimedia.org/mediawiki/1.29/mediawiki-1.29.1.tar.gz
+
+Bug with syntax highlight - stiil not fixed.",1503583157,PHID-USER-ckht4z43xrkznivuzxeu,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Release new MW version 1.29.1: https://www.mediawiki.org/wiki/Release_notes/1.29#MediaWiki_1.29.1
+
+Bug with syntax highlight fixed?",1503578921,PHID-USER-ckht4z43xrkznivuzxeu,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"I'm having the same problem.
+
+All codes is not styled.
+
+In the log, nothing is printed.
+
+Any help?",1474649170,PHID-USER-hhc5rqrodlqteaizzxd7,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"I'm having the same problema.
+
+All codes is not styled.
+
+In the log, nothing is printed.
+
+Any help?",1474031299,PHID-USER-hhc5rqrodlqteaizzxd7,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Another example from hewiki:
+https://he.wikipedia.org/wiki/%D7%A0%D7%95%D7%A9%D7%90:T8azrr7jamnrqfuy",1469334564,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"I just noticed this problem on Portuguese Wikipedia too:
+https://pt.wikipedia.org/w/index.php?title=T%C3%B3pico:Sav6mxon1ianxj4l&topic_showPostId=sb8xryegdo65sq73#flow-post-sb8xryegdo65sq73",1423164901,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"Flow needs 2 things here. When rendering the original page, it needs to pick up the resources and add them into the parser output, so they end up on the head. Additionally, they need to be transferred in api results, preferably similar to how action=parse does it for prop=modules.
+
+
+This is probably closely related to bug 67540:
+
+And specifically you might want to look at one of it's blockers:
+Bug 51245, bug 58388 and bug 67515 which detail similar problems for VE..",1410256700,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,On trello at https://trello.com/c/qb7ulCmy/,1410232630,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"TheDJ notes, ""ah, I see that Resourceloader modules don't work yet :)"".[1]
+
+So perhaps this bug should be expanded to cover that? 
+I'll leave that up to the devs.
+
+[1] at https://www.mediawiki.org/w/index.php?title=Talk:Flow&workflow=rxtlvx7tsc2qqf1b#flow-post-ry5zwru18qpuglqk",1405618171,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"another example at https://www.mediawiki.org/w/index.php?title=Talk:Sandbox&workflow=050c27a75b2dcc146adc842b2b77e796#flow-post-050c27dd37d200e9aae290b11c2788d8
+
+which is copied from https://www.mediawiki.org/wiki/Talk:About_Beta_Features#HTML
+
+(possibly the same as bug 55533 (""VisualEditor: MWSyntaxHighlight* is badly broken"") ?)",1387499812,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+Flow: syntax highlighting tags (GeSHi) don't get styled,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/475, but people from the community are welcome to contribute here and in Gerrit.",1384761854,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u7imfvtjqvaumjzh3knn,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"The browser tests are acting on User:Selenium_user. On a default VisualEditor installation, the User namespace does not have VisualEditor enabled.
+
+The easiest would be to enable VisualEditor on user page I guess.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384522740,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_description,resolved
+VisualEditor: Browser tests assume the User namespace is VE-editable,"Change 118029 merged by jenkins-bot:
+Enable VisualEditor by default in NS_USER as well as $wgContentNamespaces
+
+https://gerrit.wikimedia.org/r/118029",1394660374,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"Change 118029 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default in NS_USER as well as $wgContentNamespaces
+
+https://gerrit.wikimedia.org/r/118029",1394496845,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"Yup the VisualEditor.php entry point has:
+
+ $wgVisualEditorNamespaces = $wgContentNamespaces;
+
+Which does not include the User namespace.  So the tests should probably only hit the content namespaces.",1393926141,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,Is this still true?,1393640526,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"**jhall** wrote:
+
+Ignore previous comment - I meant to put that comment in BZ 57103.",1386263501,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"**jhall** wrote:
+
+This issue was resolved with the following commit:
+
+https://gerrit.wikimedia.org/r/#/c/99257/",1386263310,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,I have just noticed that it is already assigned to Chris (_after_ adding him to cc).,1386256237,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,And Chris. :),1386256197,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume the User namespace is VE-editable,"Jeff, Željko that might be appealing to you :-]",1386252913,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-irtxbpca23zxuomdrg5i,task_subcomment,NA
+VisualEditor: Browser tests assume User:Selenium_user exists,"The browser tests are assuming the user Selenium_user exist. It should instead rely on the user passed within the environment variable MEDIAWIKI_USER and its associated password in MEDIAWIKI_PASSWORD.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384522140,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-3tvzg52f222bnnwlfsai,task_description,resolved
+VisualEditor: Browser tests assume User:Selenium_user exists,"The wmf6 (2013-12-05) cut hasn't been made yet, so this actually goes into the cut for today, not wmf7. :-)",1386264422,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3tvzg52f222bnnwlfsai,task_subcomment,NA
+VisualEditor: Browser tests assume User:Selenium_user exists,"**jhall** wrote:
+
+This issue was resolved with the following commit:
+
+https://gerrit.wikimedia.org/r/#/c/99257/",1386263541,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3tvzg52f222bnnwlfsai,task_subcomment,NA
+VisualEditor: Selecting text with command+down actually selects the whole current paragraph and also the 0th character of the next one; show this more obviously,"Paragraph turned into heading format
+
+Steps to reproduce:
+
+1.Click the edit button on a page
+2.Write down a paragraph and the text for its heading 
+3.Select the text to be heading of the paragraph
+
+Observed Result:
+
+The whole paragraph including the text turns into heading format.
+
+See the screenshot attached
+
+Found in:
+
+http://en.wikipedia.beta.wmflabs.org/
+(Example Page:http://en.wikipedia.beta.wmflabs.org/wiki/Test_52608?veaction=edit)
+
+Browser:FireFox 25 
+OS:MAC OS X 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11950}",1384472820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-qooshzhaumbtp7cw7ahy,task_description,declined
+VisualEditor: Selecting text with command+down actually selects the whole current paragraph and also the 0th character of the next one; show this more obviously,"The rendering is consistent with native selections. We should ignore the empty partial selection for most actions, but that is T52419.",1701814075,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qooshzhaumbtp7cw7ahy,task_subcomment,NA
+VisualEditor: Selecting text with command+down and then pressing command+right takes the cursor to the end of the next line,"Steps to reproduce:
+
+1.Click on the Edit button of a page which has multiple lines
+2.Select the text in the first line by pressing command+down
+3.Press on command+right 
+
+Observed Result:
+
+Instead of moving to the end of the line for the selected text, the cursor goes to the end of the second line.
+
+However, when you select the text with command+right/left it goes to end of the selected line.
+
+Found in:
+
+http://en.wikipedia.beta.wmflabs.org/
+Browser:FireFox 25, Chrome Version 26.0.1410.65
+OS:MAC OS X 10.8.5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384469880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vqb2npuzjlgfxcuruzpi,task_description,open
+Add CSS classes based on writing system code,"It would be useful to have the languages that MediaWiki supports be aware of the alphabet in which they are written.
+
+ISO 15924 writing systems code can be used for the most part, so it will be ""latn"" for English, French, Vietnamese, etc.; ""cyrl"" for Russian, Udmurt, etc.; ""deva"" for Hindi, Marathi, etc. - and so on.
+
+This is useful for applying special styles that are common to all languages written in a script. For example the notorious line-height fix is applied in shared.css by element name and language code, and it could be greatly simplified by using the relevant script codes so instead of having selectors for bh, bho, hi, ks, mr, mai, ne, new, pi and sa, there would only be one selector for class deva.
+
+Of course, it will have to take into account language variants (Serbian Cyrillic / Latin, Kazakh Cyrillic / Latin / Arabic etc.) and also special cases not covered by ISO 15924, such as the internal differences between styles of Arabic (so Arabic may use ""arab"" and Urdu may use something like ""arab-nastaleeq"").
+
+An easy way to implement this would be to add a variable to each Messages file, similarly to $rtl. (In fact, this can make $rtl obsolete, because the direction is inherent in the writing system.)
+
+Comment 1: In this bug, ""writing system"", ""script"" and ""alphabet"" are synonyms. I mentioned all to make it easier to find.
+
+Comment 2: I vaguely recall that there is a bug for this, but I cannot find it. If there is one, please mark this one as a dupe.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384410720,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_description,open
+Add CSS classes based on writing system code,"Late to the party, but I am thinking about how such a grouping could optimize our CSS here: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1053076",1722301447,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,">>! In T59045#6510311, @Volker_E wrote:
+> @Amire80 I was incredibly happy to have stumbled into this task.
+
+Thanks, it means a lot :)
+
+For years, I've been having these big ideas, and it's not always easy to convince people they're necessary.
+
+> When developing on several of our products, I've been asking a similar question about 3 years ago, but one that should in the mid-term be resolved by the W3C in CSS standard in my opinion. We've got `:lang()` selector, why not `:lang-script()` as additional pseudo-class.
+> Maybe you are interested to work together on a write-up for when such a selector would come helpfully into play?
+
+It would be nice to do it in a universally standard way, as you suggest, but my experience with the W3C till now has been that they are very reluctant about deriving a writing system from a language. I recommended deriving the `dir` from the `lang`: if `lang=""he""`, shouldn't the renderer assume `dir=""rtl""` by default? Apparently, they really didn't want it. Their argument was that it will hurt ""small"" languages like Azerbaijani and Punjabi, which can be written in both LTR and RTL alphabets. I disagree with this argument, at least as far as these two languages go, because these languages have different codes for the LTR and RTL versions (az/azb, pa/pnb), and we have fairly active Wikipedias in all four of them, but this didn't convince them.
+
+(I did manage to convince them to apply bidi isolation by default to elements that have an explicit `dir` attribute. My little contribution to the HTML/CSS standard.)
+
+So yeah, it would be nice, but because it's similar to that thing in which I failed, I suspect that it will not be easy to actually get done. But hey, I'm willing to try again! Share a doc or a wiki page with me or something.
+
+But until it succeeds, perhaps we should do something by ourselves, and it will be a real-world proof of concept for them...",1601584001,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"@Amire80 I was incredibly happy to have stumbled into this task. When developing on several of our products, I've been asking a similar question about 3 years ago, but one that should in the mid-term be resolved by the W3C in CSS standard in my opinion. We've got `:lang()` selector, why not `:lang-script()` as additional pseudo-class.
+Maybe you are interested to work together on a write-up for when such a selector would come helpfully into play?",1601583317,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,Slightly related: Bug 56908,1386233337,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"(In reply to comment #4)
+> I have two points related to this bug:
+> 
+> 1/ Is the information of the ""ISO 15924 <-> language code"" somewhere in
+> MediaWiki? I quickly searched and didn’t find.
+
+Not in core, but it's available in the UniversalLanguageSelector extension's ""langdb"" feature. Its most readable version can be found here:
+https://github.com/wikimedia/jquery.uls/blob/master/data/langdb.yaml
+
+(It's tracked in GitHub and periodically updated in Gerrit.)
+
+I occasionally fantasize about separating the langdb into an independent jQuery library and adding it to core.",1386167081,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"I have two points related to this bug:
+
+1/ Is the information of the ""ISO 15924 <-> language code"" somewhere in MediaWiki? I quickly searched and didn’t find.
+
+2/ Rethinking about the CSS classes, there is a problem in adding multiple levels of CSS classes: if there is
+
+  <html class=""writing-Latn""><div class=""writing-Cyrl"">здесь</div></html>
+
+then the inner <div> is affected by the classes ""writing-Latn"" and ""writing-Cyrl"", and there is no mean to know what is the most inner class between the two.",1386165812,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"(In reply to comment #2)
+Some Day Soon, when VisualEditor
+> will
+> have full support for marking pieces of text in another language, then there,
+> too. (It's already a beta feature.)
+
+... Just checked, and it doesn't seem to be deployed anywhere in Wikimedia. But it has been in development for months already.",1386139010,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"(In reply to comment #1)
+> Where do you think adding these CSS classes? If I understand correctly the
+> structure of the page, the <html> tag has the language and directionality of
+> the user interface language and the <div id=""mw-content-text""> tag has the
+> language and directionality of the page language. Adding these CSS classes on
+> these two places?
+> 
+> Interwikis could perhaps also be considered.
+
+Actually, any place where we currently use lang and dir.
+
+<html>, <div id=""mw-content-text"">, interlanguage links, ULS, various elements of the Translate and Wikibase extensions. Some Day Soon, when VisualEditor will have full support for marking pieces of text in another language, then there, too. (It's already a beta feature.) Many of these are not in the core, but they will need it just as well, so there probably should be core PHP and JS functions that make it easy to add them everywhere.",1386138855,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+Add CSS classes based on writing system code,"Where do you think adding these CSS classes? If I understand correctly the structure of the page, the <html> tag has the language and directionality of the user interface language and the <div id=""mw-content-text""> tag has the language and directionality of the page language. Adding these CSS classes on these two places?
+
+Interwikis could perhaps also be considered.",1386111823,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-dlrnznpa3flmvxcmva4s,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","Steps:
+* Edit page
+* Add heading ""External links""
+* Press Enter, click ""Bulleted list"" in toolbar
+* Click on the link tool and paste a url in the link input widget
+* Type a label where the cursor is
+
+Expected:
+
+ <h2>External links
+ <ul><li> <a>Typing</a>
+
+Actual:
+
+ <h2>External links
+ <ul><li> <a>http://example.org/foobarTyping</a>♙
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384301160,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_description,resolved
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","Change 98116 merged by jenkins-bot:
+Close inspectors when surface is focused but selection doesn't change
+
+https://gerrit.wikimedia.org/r/98116",1386106765,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","Change 98116 had a related patch set uploaded by Catrope:
+Close inspectors when surface is focused but selection doesn't change
+
+https://gerrit.wikimedia.org/r/98116",1385662232,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","Clarification:
+
+* Create an empty list item
+* Open the link inspector
+* Type a link target
+* CLICK to position the cursor at the SAME PLACE where it was before
+* The inspector DOES NOT close
+* Type
+* The first key press is ignored and inserts a pawn instead, the remaining key presses insert characters before the pawn
+
+Root cause: when the document is focused, the inspector should close. We currently close the inspector when the selection changes, and usually clicking out of the inspector does change the selection, but in creation mode this isn't necessarily true.",1385473056,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content","(In reply to comment #1)
+> Is there a JS error or exception in the console?
+
+There is not.
+
+Reduced steps:
+
+
+Steps:
+* Edit page with a list (or create a new unordered list)
+* Create a new list item
+* Click on the link tool and enter a url (e.g. ""http://example.org"") in the link input widget
+* Type a label (e.g. ""example"") where the cursor is
+
+Expected:
+<a href=""http://example.org"">example</a>
+
+Actual:
+<a href=""http://example.org"">http://example.orgxample</a>♙
+
+
+Note how the first character typed was ignored.",1384301747,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+"VisualEditor: Pawn (""♙"") appears when clicking into the blank space above a new link inspector and inserting content",Is there a JS error or exception in the console?,1384301470,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cvyf4p3q6gk7j36ju3mz,task_subcomment,NA
+VisualEditor:The language selector takes user to the top of a page making user to scroll down again to the line where he was editing.,"Taking user to the top of the page
+
+Steps to reproduce:
+
+1.Click on the Edit button for a page with long article(For Example:https://test2.wikipedia.org/wiki/First_line?veaction=edit)
+2.Go to the end of the article
+3.Click the button More>Language
+
+Observed Result:
+The language selector takes user at the top of the page which is a bit inconvenient for user editing long article as he has to scroll down again to the point where he was editing.
+
+See the video attached
+
+Browser: Chrome Version 26.0.1410.65
+OS:MAC OS X 10.8.5
+Environment:test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12431}",1384218720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-i4u3xd3ofse5i6zio6uu,task_description,resolved
+VisualEditor:The language selector takes user to the top of a page making user to scroll down again to the line where he was editing.,This was fixed last month as part of the suite of such fixes.,1399641526,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i4u3xd3ofse5i6zio6uu,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"A limited rich text box, defaulting to page title.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53566
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49076",1384101420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rierearzanexovgzmq5m,task_description,resolved
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"Change 129065 merged by jenkins-bot:
+Allow VE users to change displaytitle in advanced settings dialog
+
+https://gerrit.wikimedia.org/r/129065",1402536738,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"Change 129065 had a related patch set uploaded by Alex Monk:
+Basic VE code for changing displaytitle as wikitext in metadata panel
+
+https://gerrit.wikimedia.org/r/129065",1398208005,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"Okays, turns out I hadn't read this properly and it's blocked on Parsoid recognising this as a meta item rather than a transclusion of 'DISPLAYTITLE'.",1398197686,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"(In reply to Alex Monk from comment #1)
+> This is more complicated than it looked.  For now we might have to just
+> accept wikitext (like the edit summary) instead of using a VE surface widget
+> (like the reference dialog), because DISPLAYTITLE can do crazy things like
+> accept templates.
+
+That works for now, though it's imperfect. :-)",1398184736,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel,"This is more complicated than it looked.  For now we might have to just accept wikitext (like the edit summary) instead of using a VE surface widget (like the reference dialog), because DISPLAYTITLE can do crazy things like accept templates.",1398127502,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rierearzanexovgzmq5m,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTOC__ status in the page metadata panel,"A checkbox, setting:
+
+  <meta property=""mw:PageProp/notoc"">
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384101120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ccm3vufixpqdiieyj7mc,task_description,resolved
+VisualEditor: Allow users to set/edit __NOTOC__ status in the page metadata panel,"Change 95103 merged by jenkins-bot:
+Let users set __NOTOC__ & __FORCETOC__ status
+
+https://gerrit.wikimedia.org/r/95103",1388919566,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ccm3vufixpqdiieyj7mc,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTOC__ status in the page metadata panel,"Change 95103 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT, __NOTOC__, & __FORCETOC__
+
+https://gerrit.wikimedia.org/r/95103",1384313409,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ccm3vufixpqdiieyj7mc,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTOC__ status in the page metadata panel,See also bug 56867 comment 1,1384185698,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-ccm3vufixpqdiieyj7mc,task_subcomment,NA
+VisualEditor: Allow users to set/edit behaviour flags in the page metadata panel (tracker),"Tracking bug for support for setting #REDIRECT, __NOTOC__, etc. behavioural flags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384100940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-664j7lcmpr3idv6utx47,task_description,resolved
+VisualEditor: Allow users to set/edit behaviour flags in the page metadata panel (tracker),No remaining children tickets; closing for now. We can re-open if it turns out to be necessary.,1402547626,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-664j7lcmpr3idv6utx47,task_subcomment,NA
+VisualEditor: Allow users to set/edit behaviour flags in the page metadata panel (tracker),*** Bug 52248 has been marked as a duplicate of this bug. ***,1385384185,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-664j7lcmpr3idv6utx47,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","tab not adding indentation to newline
+
+Steps to reproduce:
+
+1.Add a numbered/bulleted list in the editor 
+2.Go to a newline afte the list
+3.Now click on ""tab"" from keyboard
+
+Observed Result:
+Instead of adding indentation to the new line, it keeps on adding indentation to first line of the numbered list.
+
+Sometimes it also selects other items outside the editor.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12204}",1383948660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hu5muegrlrswr533nsfw,task_description,open
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list",Check the attachment with video capture of the steps.,1386960227,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","Created attachment 14090
+video capture of the bug
+
+**Attached**: {F12206}",1386960184,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list",This still works for me.,1386932363,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","There is modification in the steps to reproduce this issue:
+
+1.Add a numbered list in the document
+2.Add the first item ""item1""
+3.Press enter and add the second item of the list ""item2""
+4.Place the cursor just before the text item2 and press tab.
+5.Now click on bullet list icon from the toolbar
+6.Go the end of second line and press enter (another bullet gets added to the newline)
+7.Now press enter again.
+8.Then keep on pressing tabs
+
+Observed Result:
+It is adding indentation to the first line of the page like 1.1.1.1.1 
+
+Page:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/wrong_serial&veaction=edit",1386106735,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","Created attachment 13970
+Screenshot of the error
+
+**Attached**: {F12205}",1386098757,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","I just reproduced it on production on this page:
+https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/wrong_ref_serial?veaction=edit
+
+Go to the last line of the page and keep pressing tab.",1386098669,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","I can't reproduce the behaviour described. Note the expected behaviour is either nothing or the document loses focus, not that the line is indented (yet).
+
+Re-open if you can reproduce.",1385746433,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list",Note that we don't support any sort of indentation outside of lists yet.,1384079747,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","Browser: Chrome Version 26.0.1410.65
+OS:MAC OS X Version 10.8.4",1384054314,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","(In reply to comment #1)
+> Found this bug on:
+> 
+> Browser:Chrome
+
+Please *always* add your browser version.
+
+> OS:MAC
+
+Please *always* add your OS version.",1384020820,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+"VisualEditor: Instead of adding indentation to the new line, pressing ""Tab"" from the keyboard adds indentation to other numbered/bulleted list","Found this bug on:
+
+Browser:Chrome
+Environmenr:test 2
+Page: https://test2.wikipedia.org/wiki/Teetly
+OS:MAC",1383949245,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-hu5muegrlrswr533nsfw,task_subcomment,NA
+VisualEditor: Math inspector(LaTeX) does not open up after adding a reference to the article,"Steps to reproduce:
+
+1.Click on the Edit button
+2.Add a reference to a text from More>Reference
+3.Now try to open up LaTeX window for any text in the article
+
+Observed Result:
+
+The math inspector does not open up after adding a reference to the article
+
+
+Environment:Test 2
+Page:Any
+Browser:FireFox 20 and Chrome Version 26.0.1410.65
+Reproducible: Yes
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383940080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ybs7n5eiujqyko2jnore,task_description,resolved
+VisualEditor: Math inspector(LaTeX) does not open up after adding a reference to the article,This issue might got resolved.Cannot reproduce it anymore.,1386024583,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ybs7n5eiujqyko2jnore,task_subcomment,NA
+VisualEditor: The default direction of the <textarea> for editing the content of <source> must be LTR,"Currently, if I go to https://www.mediawiki.org/wiki/User:Amire80/ve-source and
+edit it using VE, I can edit the content of the <source> tag. If my UI language
+is Hebrew, then the <textarea> for editing the poem is RTL. I would expect it
+to be always LTR by default, because source code is almost always LTR. (There are some RTL programming languages like Hebrew Logo and Arabic Alb, but these are very rare exceptions and the <source> tag doesn't support them anyway.)
+
+This is comparable to Bug 56779, but unlike in that bug, here the request is that the direction will be explicitly set to ltr rather than the surrounding direction.
+
+There may be other tags for which something like this would be useful, but I can't think of any at the moment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383920820,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-fmxzdu423cuvq3v2z6tl,task_description,resolved
+VisualEditor: The default direction of the <textarea> for editing the content of <source> must be LTR,"Change 94424 merged by jenkins-bot:
+Force LTR direction in MWSyntaxHighlightDialog
+
+https://gerrit.wikimedia.org/r/94424",1383964966,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fmxzdu423cuvq3v2z6tl,task_subcomment,NA
+VisualEditor: The default direction of the <textarea> for editing the content of <source> must be LTR,"Change 94424 had a related patch set uploaded by Mooeypoo:
+Force LTR direction in MWSyntaxHighlightDialog
+
+https://gerrit.wikimedia.org/r/94424",1383944480,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fmxzdu423cuvq3v2z6tl,task_subcomment,NA
+VisualEditor: The default direction of the <textarea> for editing the content of <source> must be LTR,Another nice thing to do would be to use CodeEditor instead of <textarea>.,1383920931,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-fmxzdu423cuvq3v2z6tl,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","When cite web is used, webpage title, and access date should be filled automatically for 1 click web citations.
+
+
+**Status:**  Title and other information is done via #citoid, but auto-adding the current date to the access-date parameter is a problem because of {T4700}.",1383914040,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_description,open
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically",,1677437245,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically",,1677400700,PHID-USER-vtpndgjtp2crb6jslv5y,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically",T96000 ?,1451388644,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically",Is it Citoid ?,1444861009,PHID-USER-unpoeiyj52rmcfqi5rbw,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","Here's what I did: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Template:Cite_web/doc&diff=prev&oldid=216044
+
+The problem is indeed that substitution does not work inside 'ref' tags (T4700), so there's no way in its current form to autofill the 'access date' field via TemplateData.
+
+It seems like this could be solved just within VE, though, by adding some way of directly adding the current date as the default for a field and leaving the parser out of it altogether. But! It looks like there's a shiny new patch for review for actually fixing that hoary bug!",1429824718,PHID-USER-nyv6rqxnzdy3oe323a3d,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","@Capt_Swing: can you please clarify? What did you test, and where? Links are appreciated. Thank you.",1429795695,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","@ragesoss tried this on enwiki beta, and it doesn't work: the subst; template is not rendered. ",1429123834,PHID-USER-i6la3rbocleoqjqldvzu,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","Web page title is done by citoid, I'm not sure if we can migrate the operation to the Cite web template automatically.
+
+However (as per irc chat) filling in the date automatically is exactly what the TemplateData autofill property is for. It can be set up with a template substitution for current date, and VE will fill it in automatically.",1429122286,PHID-USER-zq6nzfwxwkyliljd4lfy,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","I created https://gerrit.wikimedia.org/r/#/c/137824/ a while ago. I'll try to get around to reworking it to make it work, which will allow you to do this.",1415032827,PHID-USER-3qsavo6roa5h32xcsgng,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","(In reply to Alex Monk from comment #3)
+> It should be possible to achieve the accessdate part of this by editing
+> TemplateData to use the autovalue field from bug 52029 (subst: the date in
+> automatically).
+> 
+> Webpage title - isn't that something Citoid would do?
+
+Unfortunately bug 2700 means this isn't very trivial…",1415032174,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","(actually, leaving this as reopened for now due to the citoid bit...)",1414807310,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","It should be possible to achieve the accessdate part of this by editing TemplateData to use the autovalue field from bug 52029 (subst: the date in automatically).
+
+Webpage title - isn't that something Citoid would do?",1414807261,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","This has not been implemented, as of the version in English Wikipedia.",1405252019,PHID-USER-bug3zrlooz3bdmi4fyl7,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+"VisualEditor: When using citation templates, the page title and access date fields should be filled automatically","Merging this with bug 50768.
+
+*** This bug has been marked as a duplicate of bug 50768 ***",1384845303,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5oobwv46vr3i7ha7vl3i,task_subcomment,NA
+VisualEditor: Present the wikitext warning to users writing <ref> tags,"Intention:
+To add a ref (incorrectly, by typing out the wikicode)
+
+Steps to Reproduce:
+1.  Open a page. 
+2.  Type <ref>Whatever</ref>
+3.  Discover that there is no warning about wikitext markup being detected.
+
+Actual Results:  
+Nothing.
+
+Expected Results:  
+It should display the same wikitext markup warning that typing ''' produces.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383875160,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lh72hjfjcfl6ttsyvwlr,task_description,resolved
+VisualEditor: Present the wikitext warning to users writing <ref> tags,"Verified in test2 with Firfox 25 on MAC OS X 10.8.5.
+Example test page:
+https://test2.wikipedia.org/wiki/Verify_56274",1384548147,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-lh72hjfjcfl6ttsyvwlr,task_subcomment,NA
+VisualEditor: Present the wikitext warning to users writing <ref> tags,"Change 94311 merged by jenkins-bot:
+Add <ref> tags to wikitext detection regex
+
+https://gerrit.wikimedia.org/r/94311",1383936986,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lh72hjfjcfl6ttsyvwlr,task_subcomment,NA
+VisualEditor: Present the wikitext warning to users writing <ref> tags,"Change 94311 had a related patch set uploaded by Catrope:
+Add <ref> tags to wikitext detection regex
+
+https://gerrit.wikimedia.org/r/94311",1383875277,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lh72hjfjcfl6ttsyvwlr,task_subcomment,NA
+VisualEditor: wiki markup for link shows up if a template is selected with another text and applied link onto them together,"wiki markup
+
+Steps to reproduce:
+
+1.Click on the Edit button for any page 
+2.Type a text in the editor.
+3.Add a template for example:citation needed,
+4.Now select both the text and the template and press command+l or link icon
+5.Apply a link to them through link inspector
+
+Observed Result:
+The wiki markup for link shows up in the view mode
+
+See the screenshot attached.
+
+
+Found this bug using firefox 20 or chrome Version 26.0.1410.65 in MAC OS
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12078}",1383868860,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pdnnreco64cgppyjvp4j,task_description,resolved
+VisualEditor: wiki markup for link shows up if a template is selected with another text and applied link onto them together,This appears to be fixed from what I can tell. Maybe part of the work we did in late February?,1402553588,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pdnnreco64cgppyjvp4j,task_subcomment,NA
+VisualEditor: The link inspector and the language selector opens up outside the editor while selecting a text outside the editor,"Link inspector
+
+Steps to reproduce:
+
+1. Click on the Edit button on any page 
+2. Go to a new line by pressing enter
+3. Now click at the top of the page or select the current user's name.
+4. Click on the link icon or More>Language from the toolbar
+
+Observed Result:
+The link inspector and the language selector opens up at the top right corner of the page ,outside the editor
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12072}",1383866520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lgpuuxaum6kkmmaplhbc,task_description,resolved
+VisualEditor: The link inspector and the language selector opens up outside the editor while selecting a text outside the editor,Fixed by Ed's null selection change.,1398726576,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lgpuuxaum6kkmmaplhbc,task_subcomment,NA
+VisualEditor: The link inspector and the language selector opens up outside the editor while selecting a text outside the editor,"Found in FireFox 20 and Chrome Version 26.0.1410.65 with MAC OS in both test2 and betalabs for any page.
+
+For FireFox, it opens somewhere at the bottom of the page.",1383867035,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lgpuuxaum6kkmmaplhbc,task_subcomment,NA
+VisualEditor: The link inspector and the language selector opens up outside the editor while selecting a text outside the editor,"Created attachment 13726
+Language selector
+
+**Attached**: {F12073}",1383866627,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lgpuuxaum6kkmmaplhbc,task_subcomment,NA
+Launch the 'gettingstartedtasktoolbar' tour by default,"**Author:** `swalling`
+
+**Description:**
+Right now, the workflow for GettingStarted tours is as follows:
+
+- The user gets 'gettingstartedtasktoolbarintro' once and immediately on their first view of a suggested task page. This is a one step intro tour, and then is never seen again. 
+- The user is then shown the task page, with the GettingStarted toolbar. They can click ""Show me how"" in the toolbar, which launches the 'gettingstartedtasktoolbar' tour. 
+
+Without changing the toolbar behavior, let's automatically launch the 'gettingstartedtasktoolbar' tour after the user completes the intro tour. Right now, only 9% of users are using the tour provided by ""Show me how"", which is fewer than we intended.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383779160,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_description,resolved
+Launch the 'gettingstartedtasktoolbar' tour by default,"Change 107726 merged by jenkins-bot:
+Auto-launch full tour, not just intro
+
+https://gerrit.wikimedia.org/r/107726",1391540557,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_subcomment,NA
+Launch the 'gettingstartedtasktoolbar' tour by default,"Change 107726 had a related patch set uploaded by Mattflaschen:
+Auto-launch full tour, not just intro
+
+https://gerrit.wikimedia.org/r/107726",1390890093,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_subcomment,NA
+Launch the 'gettingstartedtasktoolbar' tour by default,"My understanding is it should still be auto-launched only once.  The difference is that now it's the full tour, not the one step intro.
+
+Let me know if I have the wrong idea.",1389816682,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_subcomment,NA
+Launch the 'gettingstartedtasktoolbar' tour by default,"**swalling** wrote:
+
+Note: ideally, we want to launch 'gettingstartedtasktoolbar' or 'gettingstartedtasktoolbarve' conditionally based on whether the user has VisualEditor enabled.",1383779699,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-sbvrcvwdbi27giwzj5gb,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"mw.Api has nice features now like automatically retrying bad tokens, we should migrate to it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383724260,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bggjq452trm2zbnm5rkp,task_description,resolved
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"Change 186548 merged by jenkins-bot:
+Use mw.Api to run requests rather than our own stuff in ve.init.mw.Target
+
+[[https://gerrit.wikimedia.org/r/186548]]",1424885189,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"Change 186548 had a related patch set uploaded (by Alex Monk):
+Use mw.Api to run requests rather than our own stuff in ve.init.mw.Target
+
+[[https://gerrit.wikimedia.org/r/186548]]
+
+#patch-for-review",1422060600,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,Done in https://gerrit.wikimedia.org/r/#/c/98713/ AFAICT.,1415890693,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"Yeah, you're right, the automatic retry without regard for the user changing is not what we want.",1383762753,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Use mw.Api library in mw.Target instead of our own functions,"One of the intentional functionality points in current VE is warning users when the token is bad because they user has changed (i.e. you've been logged out, or logged in as someone else), and explicitly asking for the user to consent to continue.
+
+This avoids the repeated cause of pain for users of the current wikitext editor where if you get logged out for some reason, it just saves as your IP, outing you (and needing revision deletion, drama and anguish). We should be fixing the wikitext editor to mirror the protocol in VisualEditor.
+
+It's unclear from how this is written whether ""automatically retrying"" means getting a new one, but only for a given user, or getting a new one regardless. If the latter, I think this is a WONTFIX. Advice?",1383754942,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bggjq452trm2zbnm5rkp,task_subcomment,NA
+VisualEditor: Restore selection after blur+focus,"When the surface is blurred, then focused, we should restore the selection. Right now we don't, and that causes section editing to break when ULS is present.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383702120,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bl52d56tzpumlzzhbr7q,task_description,resolved
+VisualEditor: Restore selection after blur+focus,"Change 93925 merged by jenkins-bot:
+Restore selection when editor is refocused
+
+https://gerrit.wikimedia.org/r/93925",1383856735,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bl52d56tzpumlzzhbr7q,task_subcomment,NA
+VisualEditor: Restore selection after blur+focus,"Change 93925 had a related patch set uploaded by Catrope:
+Restore selection when editor is refocused
+
+https://gerrit.wikimedia.org/r/93925",1383718783,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bl52d56tzpumlzzhbr7q,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"1. Insert an image from Commons
+2. Press Ctrl+Z quickly
+
+When you undo the image insertion, there's still an API request pending. When it comes back, ve.ce.GeneratedContentNode.prototype.doneGenerating crashes because the node is now detached.
+
+GCNode should protect against being detached, and should abort any pending requests when it's detached (the latter alone is not enough: GCNode promises aren't guaranteed to be abortable).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383699720,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-akovpzpidyf5rwspkfmg,task_description,resolved
+VisualEditor: Exception when undoing foreign image insertion,"(In reply to comment #3)
+> I am getting this following errors while undoing an image insertion quickly
+> on
+> both FireFox 25 and Chrome Version 26.0.1410.65 with MAC OS X 10.8.5.
+> 
+> Uncaught TypeError: Cannot read property 'imageinfo' of null
+> ve.ui.MWMediaInsertDialog.teardown
+> OO.ui.Window.close
+> (anonymous function)
+> proxy load.php:10
+> 
+> 
+> See the screenshots.
+> 
+> Not sure if it is related with this bug or not.For now, I am reopening it.If
+> it
+> is a different issue I will create a separate ticket for that if required.
+
+Unrelated issue caused by a buggy gadget, ""popups"".",1384945498,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Created attachment 13808
+Screenshot of errors
+
+**Attached**: {F12811}",1384542540,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"After getting this error,cannot open the media dialog box again on that session.Attaching some more screenshots of the error.",1384542414,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Created attachment 13807
+Screenshot of the error
+
+**Attached**: {F12810}",1384542198,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Created attachment 13806
+Screenshot of the error
+
+**Attached**: {F12809}",1384542076,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"I am getting this following errors while undoing an image insertion quickly on both FireFox 25 and Chrome Version 26.0.1410.65 with MAC OS X 10.8.5.
+
+Uncaught TypeError: Cannot read property 'imageinfo' of null
+ve.ui.MWMediaInsertDialog.teardown
+OO.ui.Window.close
+(anonymous function)
+proxy load.php:10
+
+
+See the screenshots.
+
+Not sure if it is related with this bug or not.For now, I am reopening it.If it is a different issue I will create a separate ticket for that if required.",1384541718,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Change 93920 merged by jenkins-bot:
+Guard against detached nodes in ve.ce.GeneratedContentNode#doneGenerating
+
+https://gerrit.wikimedia.org/r/93920",1384258517,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Exception when undoing foreign image insertion,"Change 93920 had a related patch set uploaded by Catrope:
+Guard against detached nodes in ve.ce.GeneratedContentNode#doneGenerating
+
+https://gerrit.wikimedia.org/r/93920",1383715166,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-akovpzpidyf5rwspkfmg,task_subcomment,NA
+VisualEditor: Insert media dialog lets you select an image via mouseup even if mousedown occurred elsewhere,"Steps to reproduce:
+
+1.Click on the ""Edit"" button
+2.Click on More>Media
+3.Now attempt to drag the dialog downward
+
+Observed Result:
+The dialog box for media inclusion closes upon dragging down
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383699180,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2c2keu6qpdpobf5algrr,task_description,resolved
+VisualEditor: Insert media dialog lets you select an image via mouseup even if mousedown occurred elsewhere,This was fixed a while ago.,1404866655,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2c2keu6qpdpobf5algrr,task_subcomment,NA
+VisualEditor: Insert media dialog lets you select an image via mouseup even if mousedown occurred elsewhere,"Amended steps to reproduce:
+
+1. Mousedown on the title bar of the dialog
+2. Move mouse (i.e. drag) onto an image
+3. Mouseup on the image
+4. Dialog closes and inserts the image",1383699477,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2c2keu6qpdpobf5algrr,task_subcomment,NA
+VisualEditor: Make byte counter in save dialog use widget accessors rather than $textarea,"var $textarea = this.editSummaryInput.$input is bad, should just use .getValue() or whatever it is.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383698880,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-yyxfhtfwvvpwlkr3s2rr,task_description,resolved
+VisualEditor: Make byte counter in save dialog use widget accessors rather than $textarea,Masked by bug 71837.,1412800505,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yyxfhtfwvvpwlkr3s2rr,task_subcomment,NA
+VisualEditor: Make byte counter in save dialog use widget accessors rather than $textarea,"Change 165597 merged by jenkins-bot:
+Replacing $input in save dialog
+
+https://gerrit.wikimedia.org/r/165597",1412799985,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yyxfhtfwvvpwlkr3s2rr,task_subcomment,NA
+VisualEditor: Make byte counter in save dialog use widget accessors rather than $textarea,"Change 165597 had a related patch set uploaded by SuchetaG:
+Replacing $input in save dialog
+
+https://gerrit.wikimedia.org/r/165597",1412799370,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yyxfhtfwvvpwlkr3s2rr,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,"Empty inspector
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.Click on More>LaTeX
+3.Type something on the dialog box
+4.While keeping this dialog box open , Click on More>Reference
+5.Add something as reference 
+6.Click the button ""Insert Reference""
+
+Observed Result:
+A blank inspector comes up which also does not get closed unless user reopens the editor
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58045
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60850
+
+**Attached**: {F12800}",1383696720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_description,resolved
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,Appears to work now,1426003673,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,Ping on this bug.,1400701651,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,*** Bug 64915 has been marked as a duplicate of this bug. ***,1399333995,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,"Indeed; but not on a non-blank page.
+
+Minimum test:
+
+* Open VE on new (blank) page
+* Enter ""a"", <return>
+* Insert > Formula; enter ""1=1""
+* Insert > Reference; enter ""a""
+
+Voilà.",1399047179,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,Working fine locally and on beta labs with a blank page. Chrome && FF,1399044233,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,"Not for me still though,I am  giving the steps again :
+
+1.Open the editor
+2.Open the math inspector
+3.Put the cursor inside the inspector and type something in it
+4.While keeping the math inspector open , go to Insert>Reference
+5.Type something in the reference dialog box and click on Insert Reference
+
+Observed Result:
+The following error appears in the console and a blank inspector shows up:
+
+Uncaught Error: Cannot set attributes to non-element data 
+
+See the latest screenshot.",1398978174,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,Works for me.,1398942286,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,This is not fixed in Betalabs or Test 2.I can still reproduce this one on both the environments.,1398906203,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,*** Bug 63783 has been marked as a duplicate of this bug. ***,1397757927,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…,*** Bug 60801 has been marked as a duplicate of this bug. ***,1397757894,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-al3lhhw2b2pdp5sbs2i4,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""","The search text box
+
+Steps to reproduce:
+
+1. Click on the ""Edit-beta"" button on beta-labs
+2.Click on the Language option from the toolbar
+3. Click the button ""Change language""
+
+Observed Result:
+The search textbox is going beyond the dialog box for selecting language.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12789}",1383691440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_description,resolved
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""",This was fixed in a ULS update.,1399641326,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""",This bug is found in betalabs on MAC OS with Chrome Version 26.0.1410.65 and FireFox 20.0,1383762862,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""","I can't manage to reproduce this in MediaWiki.org with Chrome 30.0.1599.101 m and Firefox 24.0 in Windows.
+
+ULS works properly for me. Can you share the browser and OS this happened in?",1383703924,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""",seems likely.  Ccing Amir and Zeljko,1383692271,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+"VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on ""Change Language""","CC Moriel.
+
+Is this a bug in ULS, perhaps?",1383691945,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mmalwnjfjku6bqhnzsw6,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"We want to cache gzipped responses in Varnish. For this to work all clients need to send an Accept-Encoding header that includes 'gzip'.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383635820,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_description,declined
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"Change 101454 abandoned by Jforrester:
+[WIP] Accept-Encoding: gzip for read requests from Parsoid
+
+Reason:
+Abandoning for now.
+
+https://gerrit.wikimedia.org/r/101454",1401227823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,Appears intractable. :-(,1401227796,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"And also I should mention that on my local setup with no Varnish in the middle, and cURL installed, MW requests a gzipped copy from Parsoid and receives it. And decodes it properly.
+
+If I force it to use the PHP engine instead of cURL, it requests a non-gzipped version and receives it fine. This should be fixed in core rather than VE having to change anything.",1393294777,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"As far as I can tell from reading the code, this should currently only be necessary if the PHP cURL extension is not installed. (And it would also be necessary to decode the response you get back.)
+
+And really it should never be necessary - see bug 61507",1393294483,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"Varnish actually transparently decompresses stored compressed content and strips the supplied Accept header in its backend request. Since mid-November we always return compressed content, and Varnish stores it in compressed form for a much better hit rate. So the impact is not as high as I thought:
+
+1) it causes some extra CPU load in Varnish for decompression
+
+2) it results in a larger network transfer on the internal network
+
+Both have a very small performance impact. The Parsoid Varnish is basically idle CPU-wise and the internal network is fast.
+
+Lowering the priority to reflect this.",1388953957,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"Change 101454 had a related patch set uploaded by Jforrester:
+Accept-Encoding: gzip for read requests from Parsoid
+
+https://gerrit.wikimedia.org/r/101454",1386978406,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Send Accept-encoding: gzip to Parsoid service,"This is important for performance, so setting priority to reflect that. Currently this causes Varnish to store uncompressed HTML, which reduces the hit rate significantly.",1384887489,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cn5fpeogq2gpk4m4ftlz,task_subcomment,NA
+VisualEditor: Templates with a conditional <li> asterisk in the beginning render in VE with it always visible,"Some frequently-used templates in the Hebrew Wikipedia, for example {{ynet}} have an asterisk in the beginning, which is inserted conditionally according to a parameter.
+
+They don't appear in the rendered article, but they appear as bullets when editing the article in VE.
+
+For an example see the URL.
+
+I demonstrated the issue to Moriel.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://he.wikipedia.org/wiki/%D7%A9%D7%9C%D7%93_%D7%91%D7%95%D7%A8%D7%A1%D7%90%D7%99",1383564420,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-zlmgxm2zkcke3qpckzhj,task_description,open
+VisualEditor: Templates with a conditional <li> asterisk in the beginning render in VE with it always visible,Possible Parsoid bug?,1394223034,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zlmgxm2zkcke3qpckzhj,task_subcomment,NA
+VisualEditor: Templates with a conditional <li> asterisk in the beginning render in VE with it always visible,"Created attachment 14508
+A video of the behaviour in Swedish Wikipedia.
+
+Perhaps the video might be an additional issue as the first template in the video; https://sv.wikipedia.org/wiki/Mall:IMDb-titel does not contain an conditional asterisk but just a plain one, which seem to be handled well in the parser.
+
+**Attached**: {F12610}",1391701100,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-zlmgxm2zkcke3qpckzhj,task_subcomment,NA
+VisualEditor: line breaks are added before and after image description when it is changed,"I'm not sure that it happens always, but in this edit I changed the description of an image, and line breaks were added:
+
+https://he.wikipedia.org/w/index.php?title=%D7%90%D7%95%D7%A4%D7%A7_%28%D7%A4%D7%93%D7%95%D7%9C%D7%95%D7%92%D7%99%D7%94%29&diff=14768833&oldid=13742934
+
+It's the first change in the diff.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383561060,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-acfakt67yvd2rrao52i6,task_description,resolved
+VisualEditor: line breaks are added before and after image description when it is changed,Is this still happening? I can't reproduce.,1420843420,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-acfakt67yvd2rrao52i6,task_subcomment,NA
+Rename the BetaFeatures extension,"I realize it's probably already water under the bridge, but I believe
+this should be said anyway. Just WONTFIX the bug if we can't do
+anything about it.
+
+The name ""BetaFeatures"" is bad. Like, really bad. And I don't think
+this is just my personal opinion (but I don't like it personally
+either).
+
+* We have so many things named ""beta"" right now live on the wikis that
+  it's not even funny. VisualEditor is beta. MobileFrontend has some
+  beta stuff. Now we're also going to have ""beta"" features.
+  Depending on the person, the ""beta"" label has either lost its
+  meaning or is negatively associated with past deployment failures.
+
+* It's non-descriptive. It may be the non-native English speaker in
+  me, but it sounds like marketing-speech. ""beta"" doesn't mean much
+  these days (see point 1); ""feature"" is a catch-all buzzword.
+
+* It's stupidly hard to translate:
+  * Most languages don't even have a word for ""beta"" – unless somebody
+    talented does the translation, these will keep using the English
+    word in likely very awkward ways – most of currently translated
+    messages just keep the ""beta"" label tacked onto a normal word:
+    [[translatewiki:Special:Translations/Mediawiki:Prefs-betafeatures]],
+    some went with ""experimental"" instead.
+  * Similarly, most languages don't have a word for ""feature"" – in the
+    link above, most translations say the equivalent of
+    ""functionality"" or ""function"", and neither is a friendly word.
+    Basically, any translation of this will consist solely of
+    English/Latin loanwords in almost all languages, which may make it
+    sound ""remote"" or ""unfriendly"".
+
+
+So what do we do about it?
+
+* We can try renaming the project. We could go with the lowest
+  friction option and call it ""Experimental features"", which would be
+  at least a little better.
+
+* Or we could use others' experiences and name that section
+  ""Laboratory"", which would also give us an obvious, clear icon to use
+  (laboratory beaker) – Google does this with their experimental
+  options and it has always seemed like a great idea to me.
+
+
+No idea if ""rebranding"" as this point is still viable – it might be
+possible, as I don't think it was widely announced yet. But I'm just
+saying.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383491580,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ainrxat373d2ajxvqix6,task_description,declined
+Rename the BetaFeatures extension,"OK, since Nemo added me here...
+
+* ""Beta"" is kinda OK to translate in the languages that I know well, but it will probably be really understood only by techie people. Maybe that is the intention anyway.
+* ""Features"" is an awful English word to translate. It's very common in software, and it's always hard to interpret well.
+* I am working on the development of a big new Beta Feature (ContentTranslation), and everybody - everybody! - keeps confusing the word ""beta"" in ""beta feature"" and ""beta labs"", which is a completely different thing. At least one of these should be renamed.",1419938174,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"10.21 < aharoni> YuviPanda|zzz: kart_ hallo.
+10.21 < aharoni> it's about https://phabricator.wikimedia.org/T85106
+10.21 < aharoni> beta features
+10.21 < aharoni> not beta cluster
+10.22 < aharoni> on the production cluster.
+10.22 < aharoni> the beta feature is not installed there yet, but should be in two weeks.
+10.22 < YuviPanda|zzz> aharoni: yeah, indeed. kart_ was trying to do this on the betacluster, which is why I was confused
+10.23 < aharoni> WE REALLY NEED A DIFFERENT NAME FOR THE BETA CLUSTER
+",1419937330,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"As suggested at <http://lists.wikimedia.org/pipermail/design/2013-November/001200.html>, we could rename the extension ""FeaturesFeedback"". :-)",1385524345,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #19)
+> Are extension names ever translated? I believe the canonical (English) name
+> is
+> always used when referring to the extension name itself.
+
+Surely not. There is no general rule for this (every language's translators coordinate as do as they see fit), but most extensions ""are"" special pages and it is standard to translate the name of the special page/extension: https://www.mediawiki.org/wiki/Manual:Special_pages#The_Messages.2FInternationalization_File
+In Special:Version, the name shown is not what ""used when referring to the extension"" but a quotation, as shown by the italics.
+
+You could also try an ack-grep ""\-desc"" /mnt/user-store/git/extensions and try to find out how many translate the name when it's used in it, but in general the name lives elsewhere.",1384410819,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"I wonder how many native English speakers in different ages/gender/geographical/technical ability distributions will be able to guess what the ""Beta Feature"" is.
+It is an IT slang that pretends it went mainstream, that's all.",1384394260,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #18)
+> It is frustrating to see how the original issue, i.e. how to translate the
+> name of that feature into other languages, is addressed.
+
+Are extension names ever translated? I believe the canonical (English) name is always used when referring to the extension name itself.
+
+For interface messages, we should use what makes the most sense in whatever language is being used, of course. That languages other than English don't contain the word ""beta"" is a non-issue: they also don't contain words like ""category"" or ""visual"" or whatever else. We approximate based on the intended meaning and context (e.g., by substituting ""experimental"" for ""beta"").
+
+Again, this isn't to say that we'll never change the extension's name, but I don't think _not_ doing so is an insult to non-English speakers.",1384393478,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"It is frustrating to see how the original issue, i.e. how to translate the name of that feature into other languages, is addressed.
+
+I'll take a liberty to name it as I find appropriate in my language, then - just don't force me into ""please communicate with the community"" thing when the issue should be fixed in messages/ui/translations and not into wasted time explaining to surprised users, what Beta Features are.",1384393058,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #16)
+> (In reply to comment #0)
+> > Just WONTFIX the bug if we can't do anything about it.
+> 
+> As it is, I think this bug should be marked resolved/worksforme
+> (not resolved/wontfix), though as I said in comment 4, I don't
+> have the same visceral reaction to the name that you do. :-)
+
+Your wish is my command. :-)
+
+We may wish to revisit this later, however.",1384293799,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #0)
+> Just WONTFIX the bug if we can't do anything about it.
+
+If we hadn't gotten rid of it, I think this bug would be a reasonable case for using resolved/later (""later"" being ""until such a time that a better name is available for discussion""). As it is, I think this bug should be marked resolved/worksforme (not resolved/wontfix), though as I said in comment 4, I don't have the same visceral reaction to the name that you do. :-)",1384291417,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #11)
+> Face it. These are ""Upcoming features"". They will be deployed no matter if a
+> few angry users don't like them.
+
+Well, yeah. A few angry users don't outweigh the importance of building new, potentially better things for the good of the projects.
+
+If we let emotion and a few individual opinions affect our ability to get things done, I doubt even the people we'd appeased by backing out would respect us. Certainly nobody else would, including ourselves.
+
+We're not in ""beta"" because we expect to have to scrap the project. That's almost certainly not going to happen. We deployed to get feedback. Guess what? We got it! And now we're building an even more kickass bunch of projects for the next iteration.
+
+(In reply to comment #14)
+> Why does WMF build a separate one that can't be controlled by
+> the communities and calls it ""Beta"" instead of what it really is?
+
+Do you want to help maintain these projects? We have infrastructure for that. I'll happily sponsor you for +2 rights on them after a few patches and demonstrating that you're playing nice as a contributor.
+
+> After looking at the actual implementation of the ""Typography Update"" I hope
+> you are right. This is not even ""Beta"". I'm afraid deploying such ""half-baked
+> ideas"" will make things worse, no matter how you call it.
+
+If you're concerned, file a bug against it and make noise there. This isn't the arena for that discussion.
+
+And now I'm going to hit ""save changes"", and hopefully be able to talk about this bug instead of some topic that doesn't belong here.",1384281528,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"**mr.heat** wrote:
+
+(In reply to comment #13)
+> This comment probably adds more heat [...]
+
+My comments aren't intended to add something. All I'm trying to do is to find honest words for what's already there.
+
+> significant cost to Wikimedia community relations [...]
+
+Let me put it that way: If you are being criticized for adding non-requested features why are you adding an other non-requested feature that can be criticized for the exact same reasons? It's not that we don't have a Gadget infrastructure. Why does WMF build a separate one that can't be controlled by the communities and calls it ""Beta"" instead of what it really is?
+
+> I think there may be some value in explicitly marking particularly
+> half-baked ideas or implementations. I think that's more honest.
+
+After looking at the actual implementation of the ""Typography Update"" I hope you are right. This is not even ""Beta"". I'm afraid deploying such ""half-baked ideas"" will make things worse, no matter how you call it.",1384270667,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #11)
+> Face it. These are ""Upcoming features"". They will be deployed no matter if a
+> few angry users don't like them. These features are coming like the Google+
+> integration in YouTube. So call it what it really is, please. Be honest, at
+> least.
+
+This comment probably adds more heat than light (punintentional). Both ArticleFeedback and VisualEditor were scaled back following a barrage of negative feedback from their deployments (albeit not without significant cost to Wikimedia community relations...).
+
+I'd recommend focusing on specific problems with each of the proposed 'beta' features rather than continuing to 'bikeshed' over the extension name.
+
+> ""Beta"" doesn't mean anything nowadays. All we do in all Wikimedia projects is
+> ""Beta"". Nothing will ever be finished.
+
+Sure, but I think there may be some value in explicitly marking particularly half-baked ideas or implementations. I think that's more honest. :-)",1384263599,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #11)
+> These are ""Upcoming features"".
+
+I actually like this proposal, simple and to the point.",1384256768,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"**mr.heat** wrote:
+
+Face it. These are ""Upcoming features"". They will be deployed no matter if a few angry users don't like them. These features are coming like the Google+ integration in YouTube. So call it what it really is, please. Be honest, at least.
+
+""Beta"" doesn't mean anything nowadays. All we do in all Wikimedia projects is ""Beta"". Nothing will ever be finished.",1384250949,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #9)
+> ""Proving ground""? No idea how well it translates.
+
+Sounds like ""sandbox"".",1383614386,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #5)
+> I still like ""Laboratory"", but James has a point – even though the same point
+> can be made about ""Beta"" (I pointed out some examples in comment 0, another
+> would be the beta cluster, ironically also called ""beta labs"").
+
+Please, no more Labs/Laboratory names. In Wikimedia land we already have Labs, Tool Labs, IdeaLab, Labs²...
+
+> 
+> Other ideas for a name: something related to ""innovation"" or ""pioneering""?
+> (I quite like the second one, it gives off a nice vibe.)
+
+""Proving ground""? No idea how well it translates.",1383577308,PHID-USER-grgqimagqq3ankitlzm5,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #2)
+
+> * The language using the term ""beta"" is intentionally consistent with the
+>   Mobile team's beta channel - this is the same concept (and will likely
+>   cover Mobile technologies at some point too) and so should be translated
+>   the same.
+
+Excuse me, I can't understand the above paragraph at all :(
+
+btw. I posted https://www.mediawiki.org/wiki/Talk:About_Beta_Features#Name few days back",1383570493,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"Sure, I just set a high priority since this would be best FIXED or WONTFIXed before deployment, and deployment is happening very soon.",1383560392,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"I'm sorry, MatmaRex, I'd love to think that this was an important bug, but it's really not. I mean, as wonderful as a pioneering-based name would be, it's not like ""stop everything and work on this"" sort of stuff.",1383558037,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"Unlike those, BetaFeatures' name can probably still be changed. And we don't have Vector anymore, since I killed it (bug 45051).
+
+I still like ""Laboratory"", but James has a point – even though the same point can be made about ""Beta"" (I pointed out some examples in comment 0, another would be the beta cluster, ironically also called ""beta labs"").
+
+Other ideas for a name: something related to ""innovation"" or ""pioneering""?
+(I quite like the second one, it gives off a nice vibe.)",1383518755,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"We have a lot of poorly named extensions (""Vector"" and ""AbuseFilter"" come to mind). I'm not sure ""BetaFeatures"" is terrible, though.",1383510539,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #0)
+>     Basically, any translation of this will consist solely of
+>     English/Latin loanwords in almost all languages, which may make it
+>     sound ""remote"" or ""unfriendly"".
+
+And where I said ""Latin"", what I actually meant was Greek for ""beta"" and Latin for ""function"".",1383494293,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"Five points:
+
+* The language using the term ""beta"" is intentionally consistent with the
+  Mobile team's beta channel - this is the same concept (and will likely
+  cover Mobile technologies at some point too) and so should be translated
+  the same.
+
+* ""Experimental"" sounds clinical, complicated and confusing in English,
+  which is why it wasn't used.
+
+* If you are translating from English into a language that doesn't use the
+  Greek word 'beta', and also does not have an equivalent, calling it
+  ""experimental"" sounds fine.
+
+* The language using the term ""features"" is intentionally broad, to cover
+  new functionality, new UX approaches to existing functionality, new
+  design concepts, new skins, and other new things. Translations should
+  use a broad, inclusive term to cover all of these.
+
+* ""Labs"" is unfortunately already taken by WMF Labs. It would have been a
+  great name for this, I agree, but that's life. Unless you have a time-
+  machine handy, we can't fix the confusion that naming these the same
+  would cause.",1383494265,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+Rename the BetaFeatures extension,"(In reply to comment #0)
+> * We can try renaming the project. We could go with the lowest
+>   friction option and call it ""Experimental features"", which would be
+>   at least a little better.
+
+I think this was rejected in the past because it may include features thought or meant to be stable, just too ""new"" to be enabled for everyone at once.
+
+> 
+> * Or we could use others' experiences and name that section
+>   ""Laboratory"", which would also give us an obvious, clear icon to use
+>   (laboratory beaker) – Google does this with their experimental
+>   options and it has always seemed like a great idea to me.
+
+No idea if ""Laboratory"" is better than ""Beta"", they seem equally generic. ""Beta"" is just the most common way across the web/software industry to brand something as ""the last thing"" and tell people not to blame you if it breaks something; it doesn't have ""a meaning"" apart from that. I don't know if ""Laboratory"" has an equally wide usage/understanding.
+The main confusion here might be that not all features branded ""beta"" are controlled by this ""beta"" general switch; no idea if this is temporary.",1383492885,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ainrxat373d2ajxvqix6,task_subcomment,NA
+VisualEditor: Saving a page should update both wgRevisionId and wgCurRevisionId,"When we open a random page, we get
+wgCurRevisionId === wgRevisionId
+and if we make an edit using the source editor, both variables are increased to a new Id.
+
+On the other hand, if the edit is made using the VisualEditor, only the wgCurRevisionId is updated.
+
+This inconsistent behavior should be fixed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383474420,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-o3kocsqzjyadygy3bp6m,task_description,resolved
+VisualEditor: Saving a page should update both wgRevisionId and wgCurRevisionId,"Change 127441 merged by jenkins-bot:
+Update wgRevisionId when we change wgCurRevisionId
+
+https://gerrit.wikimedia.org/r/127441",1398107206,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o3kocsqzjyadygy3bp6m,task_subcomment,NA
+VisualEditor: Saving a page should update both wgRevisionId and wgCurRevisionId,"Change 127441 had a related patch set uploaded by Alex Monk:
+Update wgRevisionId when we change wgCurRevisionId
+
+https://gerrit.wikimedia.org/r/127441",1397926805,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o3kocsqzjyadygy3bp6m,task_subcomment,NA
+"VisualEditor: Shows ""<""  icon on the last clicked link, if user clicks on the link icon from the toolbar on a blank space","The ""<"" icon on last clicked link
+
+Steps to reproduce:
+
+1.Click on the Edit button
+2.click on a text which has link on it but do not open the link inspector
+3.Now click on a blank space
+4.Click on the link icon from the toolbar.
+
+Observed Result:
+
+The ""<"" icon shows up at the end of the text in step 2.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12481}",1383350520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-zwu66cvpdyxa3rt4yxqv,task_description,resolved
+"VisualEditor: Shows ""<""  icon on the last clicked link, if user clicks on the link icon from the toolbar on a blank space",This was fixed a while ago; sorry for not catching it then.,1402329509,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zwu66cvpdyxa3rt4yxqv,task_subcomment,NA
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"Steps to reproduce:
+
+-Click on the Edit button
+-Click on the icon to insert a link from the toolbar or press ctrl+k or command+k -Now type a valid URL without http:// for example:yahoo.com
+
+Observed Result:
+There is no option for selecting this link as external link other than creating a new page.
+
+It would be better if the external link option is made available to user when they type a valid URL (text with ""."" inside it), and then transforms it into a HTTP link if no prefix is provided.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383339600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_description,resolved
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"
+
+*** This bug has been marked as a duplicate of bug 50360 ***",1402609062,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_subcomment,NA
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Change 97733 had a related patch set uploaded by Marcoil:
+> > Bug 56490: Use the HTTP API in round-trip testing
+> > 
+> > https://gerrit.wikimedia.org/r/97733
+> 
+> I don't think this has anything to do with that?
+
+Sorry! I entered the wrong bug for git-review.",1385471440,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_subcomment,NA
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"(In reply to comment #1)
+> Change 97733 had a related patch set uploaded by Marcoil:
+> Bug 56490: Use the HTTP API in round-trip testing
+> 
+> https://gerrit.wikimedia.org/r/97733
+
+I don't think this has anything to do with that?",1385471279,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_subcomment,NA
+VisualEditor: Make the external link option available when a user types a valid URL pattern,"Change 97733 had a related patch set uploaded by Marcoil:
+Bug 56490: Use the HTTP API in round-trip testing
+
+https://gerrit.wikimedia.org/r/97733",1385468513,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lbjifl56xpkfw4ti3gs6,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","Difference in the view mode
+
+Steps to reproduce:
+
+1.Click on the Edit-beta button
+2.Type a text to apply link on it, For example: CNN
+3.Now click on the link icon from the tool bar or press ctrl+k/ Command+K
+4.Now type the link as http://cnn.com as an external link.
+5.Now type again another text CNN
+6.Now apply link insertion onto it as : http://cnn.com as new page
+7.Press the button ""Save""
+
+Observed Result:
+Now observe that the link created in step 4 looks reasonable to have an external
+link when the URL is specific in the link inspector.
+But user wont usually want a new page while specifying the URL itself and might accidentally to do that without any intention to do that.
+
+Also, observe the output format of step 6 looks wrong as the wiki markup for link shows up in the CE in view mode with a number.Though functionally, it works same as a link to external page.   
+
+Expected Result:
+As a suggestion,collapse the ""New Page"" part of the link inspector when a URL pattern detected.
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12432}",1383333240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-reos2ubqqepoytoaxumu,task_description,resolved
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","(In reply to Alex Monk from comment #4)
+> (In reply to James Forrester from comment #3)
+> > We don't want to do this, because ""http://www.amazon.com"" is a valid page
+> > name and someone might actually want to use it - for example, [[en:Http://]]
+> > is a page (specifically, a redirect to the HTTP article).
+> > 
+> > However, maybe we should demote the ""new"" section below the external link
+> > one, to make it clearer?
+> 
+> It looks like this has already been done? Am I missing something?
+
+You're completely right, we did this a while ago. Never mind me! Sorry for wasting your time. :-(",1402680839,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","(In reply to James Forrester from comment #3)
+> We don't want to do this, because ""http://www.amazon.com"" is a valid page
+> name and someone might actually want to use it - for example, [[en:Http://]]
+> is a page (specifically, a redirect to the HTTP article).
+> 
+> However, maybe we should demote the ""new"" section below the external link
+> one, to make it clearer?
+
+It looks like this has already been done? Am I missing something?",1402680333,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","We don't want to do this, because ""http://www.amazon.com"" is a valid page name and someone might actually want to use it - for example, [[en:Http://]] is a page (specifically, a redirect to the HTTP article).
+
+However, maybe we should demote the ""new"" section below the external link one, to make it clearer?",1402550055,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","Created attachment 13657
+Difference in the review mode
+
+**Attached**: {F12433}",1383333707,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"VisualEditor: Demote the ""New Page"" part of the link inspector to below the ""External link"" one when inserting a link as URL pattern","Also, if I review my changes it shows the attached format.",1383333678,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-reos2ubqqepoytoaxumu,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","==== Problem
+The orange ""You have new messages"" talkpage-message Notification, currently leads just to the top of the user's Talk page. (Ie. [User talk:Quiddity])
+This is potentially confusing and makes it harder for users to locate the new message.
+{F26220991}
+
+==== Proposed solution
+* Tapping on ""new messages"" should take the user to the specific subsection (if known, and if there's just one new message); and
+* Append the message with a ""(view changes)"" link which takes the user to the diff (if subsection is unknown, or if there are multiple new talkpage messages).
+
+(Note: This essentially follows the same message format as shown to users of the gadget to ""Display a floating alert for new talk page messages"" (link to [[ https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets | gadget on enwiki ]])
+
+
+// One user has requested that it *always* lead to the diff, which /would/ be more consistent, but I also understand the desire to not confront everyone with a diff (VE, newcomer friendliness, etc etc). ( https://en.wikipedia.org/wiki/Wikipedia_talk:Notifications#Two_clicks_instead_of_one:_Why.3F ) //
+
+",1383326040,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-dknub327yjfltf5egogv,task_description,resolved
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Yes. (But I have one pedantic clarification: it takes you to the top of the section, rather than precisely to the message.)",1630508980,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","@matmarex: would it be accurate for @ryasmeen and I to think that this patch has the following impact?
+
+**Impact**
+- This patch **does** make it so when someone clicks/taps the `new messages` yellow banner they //are// taken to the precise location on the talk page where that new comment was posted.
+- This patch does **not** make it so said new comment will appear highlighted in blue. [i]
+
+---
+i. The blue highlight depends on T281590 being resolves as [you noted in gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Echo/+/683932/): ` Together with the changes proposed in T281590, this would allow linking directly to individual messages (and highlighting them), rather than just the section`",1630455300,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","@matmarex: would it be accurate for @ryasmeen and I to think that this patch has the following impact?
+
+**Impact**
+- This patch **does** make it so when someone clicks/taps the `new messages` yellow banner they //are// taken to the precise location on the talk page where that new comment was posted.
+- This patch does **not** make it so said new comment will appear highlighted in blue. [i]
+
+---
+i. The blue highlight depends on T281590 being resolves as [you noted in gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Echo/+/683932/): ` Together with the changes proposed in
+T281590, this would allow linking directly to individual messages (and highlighting them), rather than just the section`",1630455275,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Change 683932 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Echo@master] Link to the section (if known) from the orange banner%%%
+https://gerrit.wikimedia.org/r/683932",1628242062,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Change 683932 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/Echo@master] Link to the section (if known) from the orange banner%%%
+https://gerrit.wikimedia.org/r/683932",1619801630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","5. Add an icon ""diff"" just after the regular message.
+",1535578022,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Notes: 
+**Functionality**: The [[ https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets | gadget ]] on Enwiki (""Display a floating alert for new talk page messages"" ([[https://en.wikipedia.org/wiki/MediaWiki:Gadget-topalert.js|.js]]/[[https://en.wikipedia.org/wiki/MediaWiki:Gadget-topalert.css|.css]])) provides the desired link. 
+E.g. For 2 test messages at my talkpage, it provides [[https://en.wikipedia.org/w/index.php?title=User_talk:Quiddity%20(WMF)&oldid=855470833&diff=cur|a ""view changes"" diff link that shows both of them]]. 
+It displays the link (and a plain link to the top of the talkpage) in a floating-top-center overlay.
+{F25502484}
+**Design**: As discussed above, the main question is how to integrate this link with the existing ""New message indicator"", because we probably don't want to have the default link to go to a diff (because that's extra confusing for a newcomer who was writing in VisualEditor, and receives some huge welcome or warning templates (e.g. [[https://en.wikipedia.org/w/index.php?title=User_talk:157.48.244.85&oldid=857134302&diff=cur|semi-relevant example]] pulled from recentchanges showing 2 changes)). 
+Options include:
+# add a ""(view changes)"" link to the end of the existing New message indicator. -- This would make it a bit longer in English, but still not too bad. The [[https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3AEcho-new-messages&namespace=8 |French default]] is a good example of a longer string, as is [[https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3ANotification-link-text-view-changes&namespace=8|the French for ""View changes""]]. [demo below]
+# add a ""(diff)"" link to the end [...]. -- This would potentially confuse newcomers. It's short in English, but [[https://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki%3ADiff|quite a bit longer in some other languages]].
+# add either of those options //below// the existing New message indicator. -- Kinda messy?
+# other??
+
+A (hacked-HTML) demo of option #1 would look like this in French:
+{F25503614}",1535577889,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Notes: 
+**Functionality**: The [[ https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets | gadget ]] on Enwiki (""Display a floating alert for new talk page messages"" ([[https://en.wikipedia.org/wiki/MediaWiki:Gadget-topalert.js|.js]]/[[https://en.wikipedia.org/wiki/MediaWiki:Gadget-topalert.css|.css]])) provides the desired link. 
+E.g. For 2 test messages at my talkpage, it provides [[https://en.wikipedia.org/w/index.php?title=User_talk:Quiddity%20(WMF)&oldid=855470833&diff=cur|a ""view changes"" diff link that shows both of them]]. 
+It displays the link (and a plain link to the top of the talkpage) in a floating-top-center overlay.
+{F25502484}
+**Design**: As discussed above, the main question is how to integrate this link with the existing ""New message indicator"", because we probably don't want to have the default link to go to a diff (because that's extra confusing for a newcomer who was writing in VisualEditor, and receives some huge welcome or warning templates (e.g. [[https://en.wikipedia.org/w/index.php?title=User_talk:157.48.244.85&oldid=857134302&diff=cur|semi-relevant example]] pulled from recentchanges showing 2 changes). 
+Options include:
+# add a ""(view changes)"" link to the end of the existing New message indicator. -- This would make it a bit longer in English, but still not too bad. The [[https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3AEcho-new-messages&namespace=8 |French default]] is a good example of a longer string, as is [[https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3ANotification-link-text-view-changes&namespace=8|the French for ""View changes""]]. [demo below]
+# add a ""(diff)"" link to the end [...]. -- This would potentially confuse newcomers. It's short in English, but [[https://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki%3ADiff|quite a bit longer in some other languages]].
+# add either of those options //below// the existing New message indicator. -- Kinda messy?
+# other??
+
+A (hacked-HTML) demo of option #1 would look like this in French:
+{F25503614}",1535577853,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Change 94506 abandoned by Aude:
+Link ""You have new messages"" to user talk diff
+
+Reason:
+since ext.echo.alert.js is deleted, shall try new approach :)
+
+https://gerrit.wikimedia.org/r/94506",1390511546,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","Change 94506 had a related patch set (by Aude) published:
+Link ""You have new messages"" to user talk diff
+
+https://gerrit.wikimedia.org/r/94506",1384321229,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","(In reply to comment #3)
+> I could have sworn this was a duplicate bug... I may be remembering the bug
+> about the Echo drop-down nav thing not including a ""view changes"" link.
+
+You're probably thinking of bug 54391 - which I've been told is just to do with the email bundled diff (or something).",1384320811,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","I could have sworn this was a duplicate bug... I may be remembering the bug about the Echo drop-down nav thing not including a ""view changes"" link.",1384320470,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","(In reply to comment #0)
+> The orange ""You have new messages"" talkpage-message Notification, currently
+> leads just to the top of the user talkpage. (Ie. [User talk:Quiddity])
+
+This is one of the things I probably miss the most about the OBOD, that I could get a direct diff to the new edits.
+
+> 
+> It should lead to either:
+> * the subsection (if known, and if there's just one new message), or 
+> * to the diff (if subsection is unknown, or if there are multiple new
+> talkpage
+> messages).
+
+From a code standpoint, either of these are probably doable.
+
+> 
+> One user has requested that it *always* lead to the diff, which /would/ be
+> more
+> consistent, but I also understand the desire to not confront everyone with a
+> diff (VE, newcomer friendliness, etcetc).
+
+I don't think always going to the diff is a good idea, for some of the reasons you mentioned.
+
+Adding a ""You have new messages (diff)"" thing to the personal tools menu would be icky and add some more clutter. I don't know where else we could add the link.
+
+CC'ing Jared for some design input.",1384316580,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+"Echo: The ""You have new messages"" link should go to a diff and/or subsection of the user's talk page where the talk page resides","The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/395, but people from the community are welcome to contribute here and in Gerrit.",1383589314,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-dknub327yjfltf5egogv,task_subcomment,NA
+VisualEditor: Track in some way (add tag to revision?) edits where user switched into wikitext editor,"Since bug 50687 was fixed, I was wondering if wouldn't be a good idea to identify which edits made using the wikicode editor were actually started using Visual Editor. This could be useful to identify potential areas of improvement of Visual Editor, providing a list of actions which users are unable to complete using it.
+
+A way to do this would be the use of a new tag (similar to the ""visualeditor"" and ""visualeditor-needcheck"" tags).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50687",1383304560,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-5jz7sjvvr5dsv6ewj3sj,task_description,resolved
+VisualEditor: Track in some way (add tag to revision?) edits where user switched into wikitext editor,"Change 113665 merged by jenkins-bot:
+Track edits where user switched into wikitext editor from VE
+
+https://gerrit.wikimedia.org/r/113665",1393464958,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5jz7sjvvr5dsv6ewj3sj,task_subcomment,NA
+VisualEditor: Track in some way (add tag to revision?) edits where user switched into wikitext editor,"Change 113665 had a related patch set uploaded by Alex Monk:
+Track edits where user switched into wikitext editor from VE
+
+https://gerrit.wikimedia.org/r/113665",1392564041,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5jz7sjvvr5dsv6ewj3sj,task_subcomment,NA
+"VisualEditor: Add a second keyboard shortcut for Clear Formatting for keyboards without a ""\""","Split from bug 51507 which introduced Ctrl/Cmd + \ as a trigger for this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51507",1383283920,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nlj7q7vdqadglucet365,task_description,resolved
+"VisualEditor: Add a second keyboard shortcut for Clear Formatting for keyboards without a ""\""","Change 116967 merged by jenkins-bot:
+Add cmd/ctrl+m as alternative shortcut for clear formatting
+
+https://gerrit.wikimedia.org/r/116967",1394054776,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nlj7q7vdqadglucet365,task_subcomment,NA
+"VisualEditor: Add a second keyboard shortcut for Clear Formatting for keyboards without a ""\""","Change 116967 had a related patch set uploaded by Esanders:
+Add cmd/ctrl+m as alternative shortcut for clear formatting
+
+https://gerrit.wikimedia.org/r/116967",1394029152,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nlj7q7vdqadglucet365,task_subcomment,NA
+"VisualEditor: Add a second keyboard shortcut for Clear Formatting for keyboards without a ""\""",Changing priority to 'normal' since 51507 was 'high' and I'm hesitant to make this 'low'; please feel free to re-adjust.,1383331671,PHID-USER-hxjysvdvogekpjub3nd3,True,PHID-TASK-nlj7q7vdqadglucet365,task_subcomment,NA
+VisualEditor: It should be possible to add a link with only pressing enter once,"Steps to reproduce:
+1.Click on the ""Edit-Beta"" button
+2.Type a text on which to insert link
+3.Press ""Enter"" to select the suggested links or if there is no match just press ""Enter""
+4.Then again press ""Enter""
+
+Observed Result:
+To insert a link the step 4 is a redundant step , Pressing enter once should just add the link.
+
+Pressing the ""Enter"" twice seems justified in the case, where the content of the link box is different from what user initially typed into.
+
+[Suggested by Erik Moeller]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383255660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bfggoy34bkzy45f7kcpd,task_description,resolved
+VisualEditor: It should be possible to add a link with only pressing enter once,Verified the fix in production,1403306780,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bfggoy34bkzy45f7kcpd,task_subcomment,NA
+VisualEditor: It should be possible to add a link with only pressing enter once,Verified the fix in test2,1402690628,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-bfggoy34bkzy45f7kcpd,task_subcomment,NA
+VisualEditor: It should be possible to add a link with only pressing enter once,Now fixed with the changes to the link inspector.,1402552625,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bfggoy34bkzy45f7kcpd,task_subcomment,NA
+VisualEditor:The cursor position for newly inserted link should be at the end of the link that is being created,"Screenshot showing cursor at the beginning of the text ""Yahoo""
+
+Steps to reproduce:
+-Click on the Edit-beta button
+-Type a text on which you will insert a link.
+-click on the link icon from the toolbar or use shortcut keys ctrl+k/command+k(MAC)
+-Type the link on the dialog box that appears .
+-Press ""Enter"" to apply that.
+
+Observed Result:
+The cursor position postion moves to the beginning of the text on which the link inserted making user to reposition it to the end of it to continue editing.
+
+Expected Result:
+The cursor position for newly inserted link should be at the end of the link to ease user experience.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12328}",1383251880,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-eusx3radyuz75qavwdhm,task_description,resolved
+VisualEditor:The cursor position for newly inserted link should be at the end of the link that is being created,"This was fixed a few months ago (the cursor returns to the original position if you exit normally, or goes to the beginning of the document if you exit with escape).",1402552556,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eusx3radyuz75qavwdhm,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","VisualEditor deliberately drops <span typeof=""mw:Nowiki""> annotations on changed content to prevent originally-necessary <nowiki> blocks interfering with editing. This means that HTML editors don't need to know or care about <nowiki>s, and they are just magically sorted out in the back-end so the resultant wikitext is the most like what a human would create.
+
+However, <nowiki />s come out as a <meta typeof=""mw:Placeholder"">, which VisualEditor doesn't show to users but also won't ever remove, leading to potential issues where a no-longer-needed <nowiki /> sits in the wikitext, disruptively confusing to wikitext editors.
+
+If Parsoid instead represented it as <span typeof=""mw:Nowiki""></span> or similar, VisualEditor could do the same (well, a bit more work) and so drop it when the context has been edited, letting Parsoid re-generate it if needed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=Footprints_%28film%29&curid=39472392&diff=579475542&oldid=579357688",1383161460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_description,resolved
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","@Jdforrester-WMF Do we actually need any work in VE? This seems to be magically working okay in my testing. If I'm missing something, is there a task?",1488384460,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVo97A6WHQCSeVEJfLNq} [2017-02-14T18:39:24Z] <arlolra> Updated Parsoid to 79ccfb93 (T58381, T108216)",1487097565,PHID-USER-j4uyesgqhubl2dywl4xd,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",Thank you!,1486494471,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Parsoid now represents them as <span typeof=""mw:Nowiki""></span>, but VisualEditor still needs to do the work to drop them when the context has been edited.",1486493729,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 281076 merged by jenkins-bot:
+Treat html pre and nowiki as extension tags
+
+[[https://gerrit.wikimedia.org/r/281076]]",1486493070,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 281076 had a related patch set uploaded (by Arlolra):
+WIP: Tokenize html pre as an extension tag
+
+[[https://gerrit.wikimedia.org/r/281076]]
+",1481072290,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 232313 abandoned by Arlolra:
+WIP: Edited nowiki content should invalidate the nowiki
+
+Reason:
+For now ... until I pick it up again.
+
+[[https://gerrit.wikimedia.org/r/232313]]",1459809667,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 191096 abandoned by Subramanya Sastry:
+WIP: T58381: Represent <nowiki/> as a mw:Nowiki meta tag
+
+Reason:
+Once we figure out how to not generate HTML for <nowiki>s and instead add them back where needed, this is going to be irrelevant.
+
+[[https://gerrit.wikimedia.org/r/191096]]",1450473413,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 232313 had a related patch set uploaded (by Arlolra):
+WIP: Edited nowiki content should invalidate the nowiki
+
+[[https://gerrit.wikimedia.org/r/232313]]
+",1449177908,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 232313 had a related patch set uploaded (by Arlolra):
+T58381: Edited nowiki content should invalidate the nowiki
+
+[[https://gerrit.wikimedia.org/r/232313]]
+",1440021958,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",Works for me.,1424474368,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","I agree that fixing nowiki issues are important. But, we should add specific nowiki corruption tasks to the board rather than have a generic longer-term solution like this. I will go over our current nowiki list and add any specific nowiki corruption scenarios to the VE Q3 board. Sound good?",1424474321,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",">>! In T58381#1055479, @ssastry wrote:
+> Based on all this, I am not sure that this task should be on the VE Q3 blocker list anymore. These fixes are more of a longer-term nature than what is required immediately for VE in Q3. @Jdforrester-WMF, thoughts?
+
+I'm not sure. Reducing the frequency of <nowiki>s is a key ""corruption"" concern of users, and as such is a key blocking focus for Q3. I don't particularly see this task as the one-true-fix, and happy for this to be removed if the other work in this area addresses the concerns. What do you think?",1424473082,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Based on an IRC discussion y'day during the VE/Parsoid/Services check-in, it seems that more than fixing the representation for nowiki, VE wants Parsoid html2wt to be more aggressive removing existing <nowiki/> from edited content rather than emit those back as is. Something to be considered.
+
+A related idea that came up during the discussion was: maybe Parsoid shouldn't emit the nowiki markup anymore in its HTML. This will work only if:
+(a) selser is smart enough to add nowikis wherever required (even for unedited content)
+(b) selser is smart enough to not introduce dirty diffs  by optimizing / moving around nowikis because of (a). This is especially a concern fwiki, itwiki, etc. where quotes are used in non-italic/non-bold scenarios more heavily. So, any fixes we do should be tested more heavily against these wikis.
+
+A related discussion around (a)/(b) here can be found in https://phabricator.wikimedia.org/T87708#1055269 and later comments.
+
+But, based on all this, I am not sure that this task should be on the VE Q3 blocker list anymore. These fixes are more of a longer-term nature than what is required immediately for VE in Q3. @Jdforrester-WMF, thoughts?",1440022256,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Based on an IRC discussion y'day during the VE/Parsoid/Services check-in, it seems that more than fixing the representatoin for nowiki, VE wants Parsoid html2wt to be more aggressive removing existing <nowiki/> from edited content rather than emit those back as is. Something to be considered.
+
+A related idea that came up during the discussion was: maybe Parsoid shouldn't emit the nowiki markup anymore in its HTML. This will work only if:
+(a) selser is smart enough to add nowikis wherever required (even for unedited content)
+(b) selser is smart enough to not introduce dirty diffs  by optimizing / moving around nowikis because of (a). This is especially a concern fwiki, itwiki, etc. where quotes are used in non-italic/non-bold scenarios more heavily. So, any fixes we do should be tested more heavily against these wikis.
+
+A related discussion around (a)/(b) here can be found in https://phabricator.wikimedia.org/T87708#1055269 and later comments.
+
+But, based on all this, I am not sure that this task should be on the VE Q3 blocker list anymore. These fixes are more of a longer-term nature than what is required immediately for VE in Q3. @Jdforrester-WMF, thoughts?",1424470082,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Based on an IRC discussion y'day during the VE/Parsoid/Services check-in, it seems that more than fixing the representatoin for nowiki, VE wants Parsoid html2wt to be more aggressive removing existing <nowiki/> from edited content rather than emit those back as is. Something to be considered.
+
+A related idea that came up during the discussion was: maybe Parsoid shouldn't emit the nowiki markup anymore in its HTML. This will work only if:
+(a) selser is smart enough to add nowikis wherever required (even for unedited content)
+(b) selser is smart enough to not introduce nowikis by optimizing / moving around nowikis because of (a). This is especially a concern fwiki, itwiki, etc. where quotes are used in non-italic/non-bold scenarios more heavily. So, any fixes we do should be tested more heavily against these wikis.
+
+A related discussion around (a)/(b) here can be found in https://phabricator.wikimedia.org/T87708#1055269 and later comments.
+
+But, based on all this, I am not sure that this task should be on the VE Q3 blocker list anymore. These fixes are more of a longer-term nature than what is required immediately for VE in Q3. @Jdforrester-WMF, thoughts?",1424469867,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","<meta> tags will be metadata in VE, so may end up somewhere else if content is deleted. Also <meta> and <link> tags suffer from being destroyed by copy/paste and so require special treatment (we also do this for HTML comments).",1424217065,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",Uploaded a WIP there in case that would work. The meta tag seems the right approach and fits in with the use of marker meta tags for various other wikitext constructs.,1424198389,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","Change 191096 had a related patch set uploaded (by Subramanya Sastry):
+WIP: T58381: Represent <nowiki/> as a mw:Nowiki meta tag
+
+[[https://gerrit.wikimedia.org/r/191096]]
+
+#patch-for-review",1424198157,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","How about <meta typeof=""mw:Nowiki"" ../>. Can VE handle that instead?",1424197863,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",*** Bug 59650 has been marked as a duplicate of this bug. ***,1390023730,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",*** Bug 53659 has been marked as a duplicate of this bug. ***,1390023708,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?",*** Bug 59829 has been marked as a duplicate of this bug. ***,1390023700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","(In reply to comment #1)
+> If we want to perform clean-up like this, then we should perhaps implement
+> that in Parsoid rather than VE so that other users benefit from it as well.
+
+Happy for it to be done in Parsoid instead, and for us to remove the dropping from VE.",1384481135,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Change DOM rendering of <nowiki /> to be <span typeof=""mw:Nowiki""></span> or similar?","If we want to perform clean-up like this, then we should perhaps implement that in Parsoid rather than VE so that other users benefit from it as well.",1384474548,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-iptvwjtzvbnrwojokpim,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Blurred Autonym font
+
+Interwiki names blurred and legible with difficulty (using the hardcoded ""Autonym"" font)
+
+Firefox 25 / WinXPSP3 / standard antialiasing (= no ClearType)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Windows 7
+**Platform**: PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=40874
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56552
+https://github.com/santhoshtr/AutonymFont/issues/38
+https://github.com/santhoshtr/AutonymFont/issues/50
+
+**Attached**: {F12122}",1383081900,PHID-USER-xqqqgn2dels45flxw5kb,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_description,resolved
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",Thanks for confirming.,1390379901,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #87)
+> (In reply to comment #86)
+> > With the tofu detection that recently added into ULS, users no longer see
+> > degradation of text quality for fonts they have. I think that addresses the
+> > main concern of this bug report.
+> 
+> That was https://gerrit.wikimedia.org/r/#/c/108024/
+> 
+> Given https://gerrit.wikimedia.org/r/#/c/108735/ I think the change can
+> currently be tested (only) on test.wikipedia.org. The main page may suffice:
+> https://test.wikipedia.org/wiki/Main_Page
+
+So, the fix is apparently not deployed on testwiki, but it *is* deployed on beta labs: http://en.wikipedia.beta.wmflabs.org/ (after you register and enable ULS). And it does seem to help there, most language names are displayed in normal fonts for me; the list still looks pretty silly with some language names being pretty and antialiased and some not, but it's definitely better.",1390378545,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #87)
+> (In reply to comment #86)
+> > With the tofu detection that recently added into ULS, users no longer see
+> > degradation of text quality for fonts they have. I think that addresses the
+> > main concern of this bug report.
+> 
+> That was https://gerrit.wikimedia.org/r/#/c/108024/
+> 
+> Given https://gerrit.wikimedia.org/r/#/c/108735/ I think the change can
+> currently be tested (only) on test.wikipedia.org. The main page may suffice:
+> https://test.wikipedia.org/wiki/Main_Page
+
+This has not fixed the issue for me; the list of languages still looks just like in the screenshots provided here.",1390377652,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #82)
+> This bug cannot be marked ""fixed"" but should become a tracker, [...]
+
+But the tracked bugs are on another bug tracker; that's the difficulty.
+
+(In reply to comment #86)
+> With the tofu detection that recently added into ULS, users no longer see
+> degradation of text quality for fonts they have. I think that addresses the
+> main concern of this bug report.
+
+That was https://gerrit.wikimedia.org/r/#/c/108024/
+
+Given https://gerrit.wikimedia.org/r/#/c/108735/ I think the change can currently be tested (only) on test.wikipedia.org. The main page may suffice: https://test.wikipedia.org/wiki/Main_Page",1390375567,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","With the tofu detection that recently added into ULS, users no longer see degradation of text quality for fonts they have. I think that addresses the main concern of this bug report.
+
+For the fonts users don't have, the issue is still present. However, going from completely unreadable tofu to more readable autonym font is an improvement in my opinion.",1390369610,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #78)
+> ULS has been disabled on all wikis except Wikidata (bug 46306 +
+> https://gerrit.wikimedia.org/r/108735), so this bug is not relevant for WMF
+> wikis right now. Considering we also have two duplicate reports on GitHub I
+> think it's clearer to close this one.
+
+This isn't in keeping with standard practice. We usually tag the local bug as upstream and leave the local bug open in order to make discovery easier.
+
+Thank you for adding the GitHub links to the ""see also"" section.",1390347616,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I'd also reopen this bug. Only because ULS can be switched off now does not mean it will not be used by people who find it useful. Additionally I could personally imagine the default state of the newly created option to be switched to ""enabled"" in future (therefore enabling ULS by default unless the user opts out).
+
+The bad font rendering was one of the worst annoyances around ULS (and probably the most visible one). Especially since it basically broke something that worked without problems before.
+
+I'd keep this bug open to track the progress of the ""upstream"" bug in Git.",1390344289,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #82)
+> I also agree that forcing ULS completely off is a bad situation. At least it
+> should remain as an optional gadget in user preferences, possibly in the Beta
+> preferences...
+
+You can still enable it in the user preferences > User profile > Internationalisation.",1390343760,PHID-USER-zzlez5ppzytn7ghyo6sc,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I also agree that forcing ULS completely off is a bad situation. At least it should remain as an optional gadget in user preferences, possibly in the Beta preferences.
+
+I really love the possibility of switching user langguage of the interface in one click, notably for testing translatable pages, usng the ULS icon at top of pages, even if I did not like much the ugly look of the Autonym font
+
+Nothe that the Autonym font lacks is still lacking a BOLD version, for example in language navboxs displayinf the current language in Bold black instead of a normal link, or usable with the LangSelect template or the ""multilingual"" on Commonns, where all language autonyms are displayed. If the ""autonym"" class is present, and Autonym webfont downloaded, the browser will use synthetic bold which is almost unreadable in sme scripts like Hebrew.
+
+This bug cannot be marked ""fixed"" but should become a tracker, expecting for more work to be done. IT should remain open or at least replaced by a new tracking bug collecting the efforts in ULS and all the various things to do to improve it.
+
+So please reenable ULS at least in Beta preferences, and split ULS into several separate gadgets (Webfonts alone independantly of languages, IME, script variant selector for Chinese with automated transliterators, per-languuage font preferences with or without webfonts, and UI language selector) even if there remains a central dialog to setup all these components.",1390343377,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",Now that ULS is disabled by default the usage of webfonts is totally broken: https://de.wikipedia.org/wiki/Benutzer:Raymond/Webfonts :-(,1390339861,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #79)
+> This still applies if somebody chooses to enable ULS. I suggest reopening.
+
+Indeed we don't know what was the rationale for bug 46306, but I suppose it was that one will just disable ULS if one doesn't see a benefit. So if the Autonym font gives you problems you won't enable it. Unregistered users can't enable preferences, so the ""if somebody chooses to enable ULS"" scenario doesn't apply to them.
+So, yes, technically the issue still exists but not in default code.",1390339529,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",This still applies if somebody chooses to enable ULS. I suggest reopening.,1390338559,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","ULS has been disabled on all wikis except Wikidata (bug 46306 + https://gerrit.wikimedia.org/r/108735), so this bug is not relevant for WMF wikis right now. Considering we also have two duplicate reports on GitHub I think it's clearer to close this one.
+
+General discussion continues at bug 56292, bug 60304 tracks the revert of bug 46306, the future is unknown but should be bug 56433 comment 22.",1390338333,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",*** Bug 57999 has been marked as a duplicate of this bug. ***,1388320739,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","importing glyphs from some free fonts is not enough; some scripts need that you also borrow the OpenType features allowing their contextual selection (for now only the Arabic contextual forms are borrows, Indic scripts are ignored so you only get the isolated forms of their letters, e.g. in Devenagari or Myanmarese). The result is then incorrect.
+
+The mandatory features should be obeyed, even if we can safely ignore optional features  such as variant forms, decorated forms (unless they are usually used in autonyms, but anyway even in HTML these optional features are not rendered unless you activate them specifically with specific CSS styles).
+
+-- see the OpenType specs about which opentype feature is mandatory for each documented script; note that some scripts are still not documented, OpenType specifications are still a work in progress, even for scripts which are already encoded in Unicode, notably for the most recently added ones. For example the Myanmarese and Tibetan scripts require some mandatory features still not documented, but that have been tried by various font vendors with more or less success. Only the Arabic script is very precisely documented, not just informatively in OpenType, but normatively in the Unicode specifications for its contextual joining types, which become madatory features in the OpenType specs, and similar features in other font technologies like AAT, Graphite, or SVG fonts. --
+
+Thanks for pointing where the fonts are developed.
+
+I note that your Github repository contains a ""languages.txt"" file that you maintain yourself manually, when it should be generated from the wiki, using a Lua or PHP script enumerating all supported language codes (from the Site matrix, or from languages.php) and generating the list using te equivalent of {{#language:code}} in wiki syntax. This list may evolve over time when the Language Committee will add new wikis, or when it will decide to change the preferred language names.
+
+Your list is completely unordered, and as it is long, it will be hard to see if it does not contain duplicates, or alternate names no longer supported, or typos. I suggest you sort this list by importing it in an Excel column to sort it in CLDR order (make sure you've selected the English language in your Excel document so that its CLDR collation tailoring will be correct and stable).
+
+The other option is to prefix each line in languages.txt by the language code and a TAB or SPACE before the autonym, allowing to sort the file simply by language code. These language codes (using lowercase Badic latin letters a-z and the hyphen-minus) and TAB or SPACE will not pollute the list of characters to include into the Autonym font which already need these characters for the autonyms themselves (the only addition would be the TAB or SPACE separator and the newline characters which are already mapped in the font, so you  don't need specific character filters for these, when your script will generate the list of Unicode characters to map in the generated font).
+
+For stability of the font (if there are several deployed versions of MediaWiki with different lists of languages supported by #language), you may want to add an additional ""mul"" language for adding additional characters to keep, or use a versioned line (such as ""kk-x-1.2"" containing the language autonym for Kazakh in version 1.2), so that the Autonym font for ULS will work on all wikis with different versions of their language support.
+
+Note also that these generated language names may contain RLM/LRM marks (which you don't need to map to glyphs in the geenrated fonts, are they are to be supported only by the text renderers themselves; but if you map glyphs for these controls, they should be completely empty with a zero-width advance, or should be mapped to symbols for visible controls, but this is not a good thing to do for this Autonym font which is not intended to be used in text editors with a ""visible controls"" mode).",1385275154,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Nux, (In reply to comment #68)
+> Hi. Not sure what you've used for generating the font, but if you've used
+> fontsquirrel.com, then consider the following:
+> 1. Generate SVG font (if you're not doing it already).
+> 2. Use ttf above woff.
+> 3. Preserve original hinting if it was available.
+
+ULS Preserve the hints in woff and eot. See
+https://gerrit.wikimedia.org/r/#/c/95987/ (Nov 20)
+
+Documentation about how the fonts are developed: https://github.com/santhoshtr/AutonymFont/
+
+And about how webfonts are created: see http://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector#Preparing_webfonts
+
+Note the 200% size increase in your version of the font from fontsquirrel.",1385272433,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","> For this project, just uploading the generated fonts into the MediaWiki
+repository is clearly not enough, there should exist a full project containing
+or documenting the build tools used to perform these conversions.
+
+I don't agree. The generated font is better in practice. In practice all fonts are visible and selectable (or at least in all browsers I tried).
+
+Also note that there is a configuration in the attachment describing the process (""generator_config.txt""). So the effect should be reproducible without any problems.
+
+If you can make a better font go ahead. Seriously. I know that the tool (fontsquirrel) is not perfect. I've converted a different font and had to do a lot tweaking to get good results. BUT we should progress to a better solution then the current one and then fix other issues (if we can).",1385213144,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Also the ""missinglyph"" item of the SVG is just mapped with an advance-width equal to the space character; it has no path for the glyph itself, where it should have a path drawing an empty box in that space.
+
+The unselectable glyphs seem to come from an incomplete conversion tool, that does not know really how to map the glyphs selectable by OpenType features into the necessary mappings for making them selectable by the SVG font.
+
+An SVG font cannnot use OpenType feature, because it lacks the logic included in the OpneType renderers to select these features. OpenType features have implicit selection rules from the script and character properties. Then each feature adds GSUB and GPOS rules for mapping glyph definitions. In an SVG font, all the implicit rules must be mapped (the only exception supported by current relase of the SVG font spec being the Arabic joining type). This means that Indic script cannot work with simple one-to-one mappings of a character code to a glyph, with their required features. You need to map Unicode strings (not characters) into a SVG glyph definition to support the equivalent of contextual substitutions, and use the ""hkern"" (or ""vkern"") definitions to support the equivalent of OpneType GSUB (for contextual positioning).
+
+I think that the tool used to convert OpenType fonts to SVG font is insufficient for ""complex scripts"" (those that have REQUIRED features needed; see the OpenType specfiications). This means that extra manual tweaking are needed in the SVG font to make it work correctly (the existing tool is not doing things properly with its one-to-one character-to-glyph mappings, and its bogous unselectable zero-to-one mappings).
+
+For this project, just uploading the generated fonts into the MediaWiki repository is clearly not enough, there should exist a full project containing or documenting the build tools used to perform these conversions.",1385174944,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I don't why are those glyphs present but I think they won't be used anyway if they don't have `unicode` attribute. If someone knows for sure they are not needed, then I guess they can be removed. BTW selecting characters (and copy&paste) works fine for me for all characters used for Main Page.",1385165474,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Note that the SVG version includes 76 glyphs which are not selectable at all (they have no unicode attribute and no id attribute referenced by some assigned glyph with script features. I wonder how they can be present, or if the tool converting TTF fonts to SVG fonts simply lacks info on how to map the opentype features needed to select and render these contextual glyphs. Some of these glyphs are also non-spacing (no horiz-adv-x attribute) but also not correctly selected. Some of them are for mandatory ligatures, and should be selectable by an unicode attribute specifying 2 Unicode characters, or sometimes more.
+Only the contextual forms of letters in the Arabic script (up to 3 in addition to the default isolated form) are selectable.",1385148146,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #69)
+> Created attachment 13871 [details]
+
+Nice! Thank you Maciej!
+It looks great on Windows XP too (Windows 7 was the worse).
+
+Now, could we replace the current
+
+https://bits.wikimedia.org/static-current/extensions/UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.ttf?version=20131112
+and
+https://bits.wikimedia.org/static-current/extensions/UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.woff?version=20131112
+
+with these uploaded by Maciej?
+
+This should then allow us to close this bug.
+
+**Attached**: {F12132}",1385125998,PHID-USER-mapumhlp3gw5qefhvafn,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13871
+Fixed font - notice how the font is defined in stylesheet.css!
+
+Fontsquirrel to the rescue :-). Attaching fixed font (made from automnym.ttf).
+
+Have tested on IE 10, Opera 12, Chrome 31 and Firefox 25 (Windows 7). All glyphs in all sizes seem fine and readable beyond font size 11.
+
+Also tested in IE compatibility modes. The font remains readable even in IE 8, though kerning seem worse in this version (better from IE 9 up). If you see this as a problem then you can set `letter-spacing:.1em`.
+
+**Attached**: {F12132}",1385077916,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Hi. Not sure what you've used for generating the font, but if you've used fontsquirrel.com, then consider the following:
+1. Generate SVG font (if you're not doing it already).
+2. Use ttf above woff.
+3. Preserve original hinting if it was available.
+
+You might want to experiment a bit, but that was the best options for me when generating web fonts from open type font.",1384968104,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Autonym font is a soulution for a problem, that never existed before ULS. Even now I didn't understand the reason to serve (load) webfonts by default to Latin languages. Nowadays even problematic Indic languages have much better support in OSs, a situation which makes Webfonts less than a necessity there. So I think most favorable solution may be disabling webfonts than 'temporarily intelligent' solutions like problematic Autonym font.",1384967107,PHID-USER-zmjwaqq2chic4csbxwuy,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Here some screenshot on Firefox 25, Windows LCD rendering (*).
+
+12px (en.wikipedia): http://files.espace-win.org/2013/Capture.PNG
+13px (fr.wikipedia): http://files.espace-win.org/2013/Capture2.PNG
+
+(*) There are two fonts rendering mode on Windows, one with LCD support when ClearView option is enabled, one without.",1384964635,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Then the font in this one sidebar section would be larger than in all the other ones, which is going to look even more silly than the current state. I suggest not doing that.",1384959098,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","To achieve comment 63 suggestion:
+
+  #p-lang-list li {
+      font-size: 0.8125em !important;
+  }",1384957802,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #62)
+> The critical bad rendering occurs:
+> * when rendering font sizes below 13px (for example, small text: you loose
+> important pixels: don't render lists of languags with a reduced font size;
+> unfortunately the default font-size of MediaWiki is reduced from the browser
+> standard, so you see these effects with lost pixels).
+
+Actually, 13px (0.8 x 16px) is the default for Vector, and Autonym looks acceptable at 13px. However, the navbar has its font-size set to 0.75em, which causes Autonym to drop to 12px, and the problem is very apparent.
+
+Seems like a little CSS tweaking on #p-lang might solve the primary concern.",1384889978,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Note that it's true that the Autonym font lacks hinting; but my test page demonstrates that it should not be used with all CSS styles, but that it works quite well within some limits (font-size:13px;font-weight;normal;font-style:normal;letter-spacing:normal), provided that the browser does not zoom in, on displays with low pixel densities (96dpi).
+
+Displays with high pixel densities look OK (example: smartphones that typically have densities around 190 dpi or more). With their default zoom (you'll experience poor readability only if you soom out).
+
+The critical bad rendering occurs:
+* when the browser zoom is around 120-150 dpi, because glyphs are just scaled up from a low dpi rendering (around 96 dpi on desktops/notebooks displays) without hinting, or
+* when rendering font sizes below 13px (for example, small text: you loose important pixels: don't render lists of languags with a reduced font size; unfortunately the default font-size of MediaWiki is reduced from the browser standard, so you see these effects with lost pixels).",1384869728,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #37)
+> Against this common sense ULS was designed to load webfonts for a huge bunch
+> of
+> languages. Therefore we started to load additional font support for every
+> Wikipedia user, even if it was most unlikely that a user actually needed it.
+
+You're wrong! Autonym in ULS was designed to load ONLY this font instead of a bunch of fonts.
+
+Performance tests show that
+* the download bandwidth uis highly reduced because ULS no longer needs to download many fonts (OK you don't download fonts for your installed system fonts)
+* the time to render the page is faster (the Autonym webfont is normally cached by your brower, it won't load again when you navigate, unless it has been updated on the server)
+* the browser needs to load many less fonts to render lists of language names: with your many system fonts configured for each script or language by your CSS preferences or by your browser settings, the browser will need to load all these system fonts in memory (even if the browser also uses a font rendering cache).
+* Nothing is changed for the rest of the page content (outside language autonyms): the content still uses your own choice of fonts
+* You can tweak webfonts used by ULS to use other more complete (and hinted) webfonts proposed by ULS: they will override the Autonym font if the span element containing the language name does not only use the CSS class ""autonym"", but also sets the lang="""" attribute to specify its language.
+* You can tweak you own CSS rules to provide other local fonts you have for a specific language using CSS lang() selectors.",1384869013,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Note that the rendering of the Autonym font may be tweaked with ULS, provided that the span using the autonym class also sets the lang attribute (as it should).
+
+So you can use ULS to select another supported webfont for each language supported by ULS. The Autonym font will be used only if you select ""use system font"" in ULS for that language. If you select another proposed webfont, it will override the font specified in that class (and this other webfont will be loaded by your browser to render this language).",1384868416,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","For reference, you may look at this page which tests the Autonym font with all Active Wikimedias, under various styles:
+
+https://meta.wikimedia.org/wiki/Wikimedia_Forum/Autonym_font_test_with_active_Wikipedias",1384868152,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+(In reply to comment #57)
+> (In reply to comment #41)
+> > (In reply to comment #37)
+> > > Autonym (which will by definition never be as good as a native font like Arial on Windows)
+> > 
+> > I don’t understand the logic of this. Arial is hardly a great typeface
+> > anyway.
+> 
+> Don't confuse design with legibility. Arial is the default sens-serif on
+> Windows, and renders *very* well on Windows. Autonym renders *very* bad on
+> Windows, because the font (and its source FreeSans) were never desigend with
+> Windows in mind, and therefor lack any hinting.
+
+Sure, the design of a typeface doesn’t matter as much if your system distorts the character shapes to fit a pixel grid. As higher-resolution displays are becoming common, screen hinting is going away and good font design is starting to be considered good font design. 
+
+Anyway, the immediate fix is to import hinted character outlines from a better free font. Yes, easier said than done, but there’s no reason it couldn’t match Arial’s quality in any particular OS or browser.
+
+
+> 
+> > A simple fix for much of this would be to embrace installed fonts, and push
+> > Autonym to the bottom of a font stack that includes the default sans-serif
+> > fonts on the various platforms. I wonder if, indeed, “font-family:
+> > sans-serif, autonym;” would work to make this font the fallback’s fallback.
+> > Ideally, it should only be rendering text that would show up as tofu. Ideally.
+> 
+> I doubt it. Windows usually uses the first available font in the font stack
+> and
+> sticks with it, and revert to its default unicode font if it can't find a
+> glyph
+> (usually Lucida Sans Unicode).
+
+I think it might be more complicated than that. MSIE 6 ignores fallbacks for individual characters missing from a font, but I understand that newer versions have improved on this. As far as I know, Firefox uses its own font choice and rendering engine.",1384798166,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #41)
+> (In reply to comment #37)
+> > Autonym (which will by definition never be as good as a native font like Arial on Windows)
+> 
+> I don’t understand the logic of this. Arial is hardly a great typeface
+> anyway.
+
+Don't confuse design with legibility. Arial is the default sens-serif on Windows, and renders *very* well on Windows. Autonym renders *very* bad on Windows, because the font (and its source FreeSans) were never desigend with Windows in mind, and therefor lack any hinting.
+
+> A simple fix for much of this would be to embrace installed fonts, and push
+> Autonym to the bottom of a font stack that includes the default sans-serif
+> fonts on the various platforms. I wonder if, indeed, “font-family:
+> sans-serif, autonym;” would work to make this font the fallback’s fallback.
+> Ideally, it should only be rendering text that would show up as tofu. Ideally.
+
+I doubt it. Windows usually uses the first available font in the font stack and sticks with it, and revert to its default unicode font if it can't find a glyph (usually Lucida Sans Unicode).",1384796366,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #52)
+> Created attachment 13824 [details]
+> ENWP Sidebar, Windows 8, IE 10
+
+Seems like ordinary Arial. In other words, it does not use Autonym in this screenshot.
+
+**Attached**: {F12131}",1384795823,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #54)
+> (In reply to comment #51)
+> > Screenshot on a default Windows 8, IE 10
+> > 
+> > Good news? It seems better on Windows 8.
+> 
+> From your screen-shots, it seems there's something fundamentally wrong with
+> your font rendering(besides anything Autonym may cause):
+> - Do you notice the uneven thickness of vertical lines? This should not occur
+> if Hinting works as expected.
+> - You seem to have Subpixel-anti-aliasing (alias ClearType) turned off, but
+> you
+> seem to be still utilizing some sort of grayscale-anti-aliasing. Is this on
+> purpose?
+
+I have no idea at all. I happened to be using a Windows 8 PC (not mine) and took those screenshots.",1384789243,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #51)
+> Screenshot on a default Windows 8, IE 10
+> 
+> Good news? It seems better on Windows 8.
+
+From your screen-shots, it seems there's something fundamentally wrong with your font rendering(besides anything Autonym may cause):
+- Do you notice the uneven thickness of vertical lines? This should not occur if Hinting works as expected.
+- You seem to have Subpixel-anti-aliasing (alias ClearType) turned off, but you seem to be still utilizing some sort of grayscale-anti-aliasing. Is this on purpose?",1384788368,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #51)
+> Good news? It seems better on Windows 8.
+
+Could you test it with either Firefox/Chrome/Opera to make sure it's not just IE?",1384787796,PHID-USER-mapumhlp3gw5qefhvafn,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13824
+ENWP Sidebar, Windows 8, IE 10
+
+**Attached**: {F12131}",1384785419,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13823
+Screenshot on a default Windows 8, IE 10
+
+Good news? It seems better on Windows 8.
+
+**Attached**: {F12129}",1384785375,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Also setting ""Windows 7"" as the most recent Windows cited as having the problem (""PC"" is a bit too generic).",1384761625,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #48)
+> (In reply to comment #47)
+> > (In reply to comment #44)
+> > > @Nemo: Thanks for comment 43, very helpful!
+> > > 
+> > > @Erik: Could you clarify comment 36? Which other systems did you experience
+> > > the
+> > > problem with?
+> > > 
+> > > (In reply to comment #42)
+> > > > It would help if this bug identified the specific code revisions (Gerrit
+> > > > links) that are responsible for this recent regression.
+> > > 
+> > > @MZMcBride:
+> > > https://blog.wikimedia.org/2013/10/28/the-autonym-font-for-language-names/
+> > > links to https://bugzilla.wikimedia.org/show_bug.cgi?id=40874 which links to
+> > > https://gerrit.wikimedia.org/r/#/c/84850/ and
+> > > https://gerrit.wikimedia.org/r/#/c/84851/
+> > 
+> > Um, now I must admit I had not tested it on any other systems until now. Don't know why I thought it was cross-platform. Mea culpa.
+> > --Eric",1384749410,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #47)
+> (In reply to comment #44)
+> > @Nemo: Thanks for comment 43, very helpful!
+> > 
+> > @Erik: Could you clarify comment 36? Which other systems did you experience
+> > the
+> > problem with?
+> > 
+> > (In reply to comment #42)
+> > > It would help if this bug identified the specific code revisions (Gerrit
+> > > links) that are responsible for this recent regression.
+> > 
+> > @MZMcBride:
+> > https://blog.wikimedia.org/2013/10/28/the-autonym-font-for-language-names/
+> > links to https://bugzilla.wikimedia.org/show_bug.cgi?id=40874 which links to
+> > https://gerrit.wikimedia.org/r/#/c/84850/ and
+> > https://gerrit.wikimedia.org/r/#/c/84851/
+> 
+> Um, now I must admit I had not tested it on any other systems until now. Don't > know why I thought it was cross-platform. Mea culpa.
+> --Eric",1384749365,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #44)
+> @Nemo: Thanks for comment 43, very helpful!
+> 
+> @Erik: Could you clarify comment 36? Which other systems did you experience
+> the
+> problem with?
+> 
+> (In reply to comment #42)
+> > It would help if this bug identified the specific code revisions (Gerrit
+> > links) that are responsible for this recent regression.
+> 
+> @MZMcBride:
+> https://blog.wikimedia.org/2013/10/28/the-autonym-font-for-language-names/
+> links to https://bugzilla.wikimedia.org/show_bug.cgi?id=40874 which links to
+> https://gerrit.wikimedia.org/r/#/c/84850/ and
+> https://gerrit.wikimedia.org/r/#/c/84851/
+
+Um, now I must admit I had not tested it on any other systems. Don't know why I thought it was cross-platform. Mea culpa.
+--Eric",1384749167,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #43)
+> (In reply to comment #42)
+> > It would also help, for triaging, to know how many operating systems/browsers
+> > are affected (or rather, what percentage of typical users)? Only Windows
+> > users?
+> 
+> So far the only information provided pointed exclusively to Windows problems;
+> Erik removed Windows from the platform/OS fields shortly after comment 36
+> without clarifying why.
+
+Sorry, I switched the platform/OS to ""all"" because I thought this problem was not restricted to Windows. However, just now I checked on a Mac in Firefox and Chrome and did not encounter the text-blurring problem. But I'll leave it to someone else to switch back as I have not tested it on any other systems.
+--Eric",1384749061,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+language-choice text blurring on Commons
+
+screenshot of language-choice link text blurring, Win7 64-bit, Firefox 25, Chrome 31.0.1650.57 m
+
+**Attached**: {F12128}",1384748728,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","@Nemo: Thanks for comment 43, very helpful!
+
+@Erik: Could you clarify comment 36? Which other systems did you experience the problem with?
+
+(In reply to comment #42)
+> It would help if this bug identified the specific code revisions (Gerrit
+> links) that are responsible for this recent regression.
+
+@MZMcBride:
+https://blog.wikimedia.org/2013/10/28/the-autonym-font-for-language-names/ links to https://bugzilla.wikimedia.org/show_bug.cgi?id=40874 which links to https://gerrit.wikimedia.org/r/#/c/84850/ and https://gerrit.wikimedia.org/r/#/c/84851/",1384741481,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #42)
+> It would also help, for triaging, to know how many operating systems/browsers
+> are affected (or rather, what percentage of typical users)? Only Windows
+> users?
+
+So far the only information provided pointed exclusively to Windows problems; Erik removed Windows from the platform/OS fields shortly after comment 36 without clarifying why.",1384737391,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","It would help if this bug identified the specific code revisions (Gerrit links) that are responsible for this recent regression.
+
+It would also help, for triaging, to know how many operating systems/browsers are affected (or rather, what percentage of typical users)? Only Windows users?",1384737203,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+(In reply to comment #37)
+
+I don’t completely agree with Eduard Brown.
+
+WikiMedia hosts an unusual multilingual range of websites on unusual multilingual software. Text in some languages appears broken on many computers. There is nothing wrong with aspiring to fix the breakage when the technology is available.
+
+
+> Common sense dictates that users have fonts installed for their native
+> languages.
+
+An ideal. The reality is that millions of people cannot install fonts on the devices they depend on, for many different reasons. Smartphone users? Refugee immigrants relying on library computers configured in a language they barely know? They deserve access to information.
+
+
+> Autonym (which will by definition never be as good as a native font like Arial on Windows)
+
+I don’t understand the logic of this. Arial is hardly a great typeface anyway.
+
+
+> I'm afraid there is definitely room for improvement right now!
+
+True. I don’t know why this was pushed out without some basic testing on common platforms. 
+
+Most modern browsers on modern OSes render most language scripts these days. A simple fix for much of this would be to embrace installed fonts, and push Autonym to the bottom of a font stack that includes the default sans-serif fonts on the various platforms. I wonder if, indeed, “font-family: sans-serif, autonym;” would work to make this font the fallback’s fallback. Ideally, it should only be rendering text that would show up as tofu. Ideally.",1384732866,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+(In reply to comment #38)
+> [Removing random added keywords, see
+> https://bugzilla.wikimedia.org/editkeywords.cgi ]
+
+Sorry my addition of those keywords seemed random, Andre. It wasn't, but I'm not very experienced with Bugzilla. It seemed several commenters felt this bug was not drawing enough attention, and my reading of the design and community-consensus-needed keywords led me to believe they would be appropriate here and might draw more attention.
+--Eric",1384698800,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #38)
+> [Removing random added keywords, see
+> https://bugzilla.wikimedia.org/editkeywords.cgi ]
+
+https://bugzilla.wikimedia.org/describekeywords.cgi
+
+The original link doesn't work for normal users.",1384692209,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","[Removing random added keywords, see https://bugzilla.wikimedia.org/editkeywords.cgi ]",1384692058,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I share the opinion of many others:
+
+Autonym is actually
+a) a fix for a problem that most people never experienced.
+b) making thinks even worse as they would have been without ULS and Autonym in the first place
+
+
+The whole sad story from my point of view:
+
+Common sense dictates that users have fonts installed for their native languages. If they work multilingual they're most likely do also have all fonts necessary for those languages installed on their system. On top of that we can assume that on all modern systems there's support for even more languages that a normal user never ever needs anyway.
+
+Against this common sense ULS was designed to load webfonts for a huge bunch of languages. Therefore we started to load additional font support for every Wikipedia user, even if it was most unlikely that a user actually needed it.
+
+It turned out, that ULS was detrimental to performance. The additional traffic due to webfonts loading seems to have been so large, that even WMF saw the need for a change (I'm quite sure WMF would not have even cared to develop Autonym if it had only affected client performance).
+
+Now we have Autonym, which brings all sorts of problems, including the extremely bad rendering we're discussing in this bug...
+And now we're trying hardly to fix font rendering of Autonym (which will by definition never be as good as a native font like Arial on Windows), because we put much effort into Autonym, which was a fix for the bad performance for ULS, which was a huge project supported by WMF which was supposed to fix problems and add features... that users never faced and seldom requested!
+
+
+The whole thing seems pretty messed up to me, like many things that come from WMF lately. Since I see Siebrand Mazeland is active on this bug (who is the ""Product Manager Language Engineering"" of the WMF after all and therefore probably the one in charge for everything we're discussing here): Think about the doubts many users have about ULS, Autonym and all the other new language features. And think about why there are no users praising ULS, while there are tons of users facing problems with ULS and everything that is connected to it... I don't want to blame you for doing a bad job - but I'm afraid there is definitely room for improvement right now!",1384563438,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+Comment on attachment 13809
+screenshot font-rendering, en.wp in Firefox 25, Win7
+
+Seeing problem in Commons as well in language choice link (upper right).",1384556433,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**e.martinson** wrote:
+
+screenshot font-rendering, en.wp in Firefox 25, Win7
+
+Similar to ""Autonym glyphs are missing pixels"" shot.
+
+**Attached**: {F12127}",1384542694,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",Has there been any progress with this? What is the status? Is it supposed to be fixed? (Because it's not.),1384542094,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #31)
+> ULS master has hinting added for the Autnym font. This is active in the
+> Wikimedia branch 1.23wmf3.
+
+I see no difference. Do I need to do something? (Tested on pl.wikt, which is at wmf3 now.)",1384280994,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+(In reply to comment #30)
+> What's the plan for this bug?
+
+I wonder why you are asking this question. There is no ""plan"". For the average Bugzilla report it's often like ""ignore it long enough to make the users give up and stop complaining about, then pretend there is no problem"". It doesn't even matter if a report is almost 10 years old and received 50 votes (e.g. bug 674). There is no developer assigned and there are no developers to assign. WMF always moves them to the next project in the moment a feature is deployed. Sometimes the original developers even left WMF. If you are lucky a volunteer will make a pull request.
+
+I really, really don't understand why such bad changes aren't reverted (which would be simple), fixed (which may be hard) and deployed again (which is again simple). It's like WMF is more afraid of reverting something than being criticized for making bad changes. Why is that?
+
+I'm sorry, Andre, I'm just trying to explain what many users actually think. Reports like this are just tips of the iceberg.
+
+(In reply to comment #31)
+> ULS master has hinting added for the Autnym font.
+
+What about excluding the Wikidata link from using the font? What about excluding all Latin languages from using a font they don't need? What about delivering the font only to browsers that would show rectangles otherwise?",1384268462,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #30)
+> What's the plan for this bug?
+
+ULS master has hinting added for the Autnym font. This is active in the Wikimedia branch 1.23wmf3.",1384267110,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",What's the plan for this bug?,1384262802,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","As I quickly realized, and confirmed at the Autonym website, the majority of Latin glyphs were extracted form FreeSans, possibly the worst-rendering (at leats on Windows) open source font available. FreeSans (as well as the other UCS/GNU FreeFonts) lack *any* type of hinting, on which Windows relies for proper font rendering. We could blame Windows, but that will not solve anything.
+
+Autonym should find a better source for its Latin glyphs, preferably Nimbus Sans L (on which FreeSans is based!), which include at least some basic hinting.",1384194021,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #0)
+> Created attachment 13624 [details]
+> Blurred Autonym font
+> 
+> Interwiki names blurred and legible with difficulty (using the hardcoded
+> ""Autonym"" font)
+> 
+> Firefox 25 / WinXPSP3 / standard antialiasing (= no ClearType)
+
+Screenshot of
+https://www.mediawiki.org/w/index.php?title=UniversalLanguageSelector/AutonymFont
+using FF22 on Windows XP SP3 with the latest version of font http://app.crossbrowsertesting.com/public/id1b2af101bb8ef7/livetests/1196568/snapshots/zb68cdfaa35be26924f1 , font size 13px
+
+**Attached**: {F12122}",1384007121,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #26)
+> IE6? OK. Let's be serious. Majority of other users INCLUDING users of IE6 are
+> served with a bad font.
+
+
+IE 6(or anything less) will not get this font as per latest changes. Screenshot of https://www.mediawiki.org/w/index.php?title=UniversalLanguageSelector/AutonymFont using IE6 on Windows XP
+
+http://app.crossbrowsertesting.com/public/id1b2af101bb8ef7/livetests/1196571/snapshots/z7f7810ca035e37ef94c",1384006480,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","IE6? OK. Let's be serious. Majority of other users INCLUDING users of IE6 are served with a bad font. Users that are interested in certain language will have glyphs for the font they are interested. So using a bad font just creates a bad experience for all users.
+
+BTW. The font looks good only for 13px. So if you must please at least change default size.
+
+Also BTW, notice this font rendering is bad in almost any other size then 13px.",1384004758,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+(In reply to comment #24)
+> I see that MSIE 6 accounts for 0.83% of traffic, well over the 0.1%
+> threshold,
+
+Holy Hannah, MSIE 5.5 also qualifies with 0.11%!",1383948834,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+Thanks for the enlightening links, all. 
+
+I see that MSIE 6 accounts for 0.83% of traffic, well over the 0.1% threshold, and thus remains supported as a grade B browser, for reading, but not necessarily having all features working. The same applies to MSIE 7 (1.47%) and 8 (4.71%). 
+
+All these guidelines carry out-of-date warnings, and don’t account for the conflicted grey area wherein MSIE 6 and 7 are supported for reading, but not for the ULS which provides fonts that may be necessary for reading. 
+
+I think the gist is that if you are using MSIE 6, you are more-or-less on your own, and may need to install some fonts. Editors and developers don’t want to abandon MSIE 6 users, but no one will invest time and energy into testing MSIE 6 and 7, so the realistic support level is “good luck, mate.”
+
+Also good to know that WikiMedia is, or was, supposed to work without CSS3, without JavaScript, and in text-only browsers.
+
+One more question: does the ULS try to work in MSIE 6 and 7, or is it disabled in these browsers?",1383948467,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(Yes, that's VE, which is not going to work with IE 6, but I guess the ""less than 0,1%""-rule is generic? It's also mentioned at https://www.mediawiki.org/wiki/Compatibility#Grade_B .) :)",1383931810,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #21)
+> https://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix
+
+That's VE. :) There's also https://www.mediawiki.org/wiki/Compatibility#Software_for_using_MediaWiki in general.
+
+https://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector states:
+""Not compatible with Internet Explorer 7 or lower.""",1383931585,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Michael: here https://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix (warning, old data) I read:
+""The unofficial rule for Wikimedia's browser support is that we try to support reading (and not necessarily other functions) for all browsers used by at least 0.1% of page hits based on the WikiStats data.""
+
+If I read http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm correctly, MSIE 6.0 does not meet that requirement.",1383930913,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+> #p-lang a[lang=ja], #p-lang a[lang=th] { ... }
+> 
+> Selectors like this work in all browsers including very old ones. Problem
+> solved.
+
+Doesn’t work in MSIE 6. Sadly, millions use it and I think we still intend to support it. See http://www.ie6countdown.com/
+
+Is there any official or community statement on which browsers we do support?
+
+
+> Don't you think all users
+> that are able and interested in a specific language have the proper fonts
+> installed? 
+
+No. I think the point is to make wikis accessible to people who can’t or won’t install software on their machines. This means tens of millions who rely on library or work PCs, or the latest mobile devices, or almost anything in between. Not only techies need to read their own language.
+
+That said, it would be nice if the font spec only applied to the necessary language names, whichever those may be.",1383929643,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+(In reply to comment #18)
+> something like "" font-family: sans-serif, ""Autonym""; ""
+
+Unfortunately this is not how it works. My suggestion was to apply the font only to language names with otherwise missing glyphs. For example, the list in the sidebar looks like this:
+
+<ul>
+<li class=""interwiki-en""><a lang=""en"" hreflang=""en"">English</a></li>
+<li class=""interwiki-fr""><a lang=""fr"" hreflang=""fr"">Français</a></li>
+<li class=""interwiki-ja""><a lang=""ja"" hreflang=""ja"">日本語</a></li>
+</ul>
+
+Remove the current rule:
+
+#p-lang ul { font-family: ""Autonym"", sans-serif; }
+
+Instead use a rule set like this for all non-latin language names:
+
+#p-lang a[lang=ja], #p-lang a[lang=th] { ... }
+
+Selectors like this work in all browsers including very old ones. Problem solved.
+
+At least exclude the Wikidata ""Edit links"" item from the rule by applying it only to items that are in an other language (this may be an other issue, please tell me if I should split this):
+
+#p-lang a[lang] { ... }
+
+Besides, what was the problem in the first place? Don't you think all users that are able and interested in a specific language have the proper fonts installed? In think missing glyphs or rectangles are only visible to people that aren't interested in these languages anyway. Again, I'm very sorry to say that but this looks like a fix without a real world problem to me. I'm aware that it may help a few people but the current way the font is used creates more problems than it solves.",1383927388,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","As suggested by TMg (comment #6), is it not possible to let the browser choose the Autonym font only if there are missing glyphs? I’m not very knowledgeable about the details, but I know it is the global goal of the CSS list of fonts in font-family; is something like "" font-family: sans-serif, ""Autonym""; "" would achieve the goal by only searching missing glyphs in Autonym?",1383916058,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #15)
+> Isn't this a regression, since it worked before?
+
+Technically no because it's a new feature, no fonts have been served for interwikis in the last few weeks to save on bandwidth etc.",1383549438,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13681
+Comparison Autonym Arial
+
+I made a sample to show the problem: Two times ""Nederlands"" is shown, first with Autonym and then with Arial. The font size (height) is the same, even though Arial is slightly wider. Arial is better readable, just compare the first ""e"" of ""Nederlands"" or the lower-case ""n"": they seem to have holes.
+
+**Attached**: {F12126}",1383530954,PHID-USER-ayv2najkcouorpblxvzo,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I also experience this bug, with FF 24.0 on Windows 7.
+Isn't this a regression, since it worked before?",1383523242,PHID-USER-7e4yonmruupxzg23swum,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+Firefox/Opera 12/IE 9 with ClearType enabled
+
+Here is an other screenshot with ClearType enabled. From left to right:
+
+* Firefox with hardware acceleration disabled
+* Opera 12
+* IE 9
+
+Same bug in Firefox and Opera, some pixels are completely missing. Enabling or disabling ClearType has no effect on this bug, obviously.
+
+IE 9 uses hardware acceleration by default. Because of this the font looks different. But it's also distorted. The glyphs are more narrow and more blurred compared to the default font (seen in the upper half of the screenshot). Some glyphs are distorted. Look at the ""g"" from ""English"" and the ""S"" from ""Suomi"".
+
+Enabling ClearType *and* hardware acceleration in Firefox makes it the same as IE 9. Enabling hardware acceleration *without* ClearType makes it worse. A lot worse. That's why I have no other choice than do disable both.
+
+Why don't you use the default fonts for simple words like ""English"" that don't contain any problematic characters?
+
+**Attached**: {F12125}",1383321748,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+The problem seems to be “missing pixels.” Only one of three screenshots shows anything “blurred” that isn’t also occurring in the default font. Might both be caused by lack of hinting, but might be two different bugs.",1383320257,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**michael** wrote:
+
+The language names on en.wiktionary.org’s home page render correctly on Safari 6.1/Mac, Firefox 25/Mac, and Chrome 30/Mac (on OS X Mountain Lion).
+
+They also renders correctly on iPad Safari (iOS 5), except that Burmese and Khmer characters are broken anyway.
+
+But they render correctly on the Mac with the Autonym font disabled. Every language name renders every character with the font spec set to “sans-serif.” Developers, please stop trying to “fix” an OS that doesn’t need help. Just serve this font to systems that need it, and do a reasonable amount of testing before releasing.",1383320023,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Just for the record:
+
+The same issue is with the <languages/> box.
+
+(-> changing the summary to be more general)",1383313682,PHID-USER-xqqqgn2dels45flxw5kb,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(Strike that, answer is in comment 0; setting Platform.)",1383303490,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","(In reply to comment #6)
+> Suggested reading:
+> http://www.smashingmagazine.com/2012/04/24/a-closer-look-at-font-rendering/
+
+TL;DR: Windows is bad. Danny, do you use Windows?",1383303436,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+(In reply to comment #6)
+> Suggested reading:
+> http://www.smashingmagazine.com/2012/04/24/a-closer-look-at-font-rendering/
+
+See my ""Subpixel rendering is a lie"" comment there.",1383303226,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","I'm guessing there's not hinting information in the font; Windows' TrueType font renderer is notorious for relying on good hinting for on-screen resolutions, while OS X and Linux tend to ignore it and optimize their rendering without hinting.
+
+I've gone ahead and filed an entry on the Autonym github issue tracker and copied the images (they're viewable inline there, for easier reference): https://github.com/santhoshtr/AutonymFont/issues/38",1383302524,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",Suggested reading: http://www.smashingmagazine.com/2012/04/24/a-closer-look-at-font-rendering/,1383301324,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","**mr.heat** wrote:
+
+Autonym glyphs are missing pixels
+
+Please tell me if I should post this as a separate issue.
+
+I'm using Opera 12 on Windows 7 with ""Clear Type"" rendering turned off (on purpose, because I get headaches from the red and blue blurry shadows it adds around the glyphs). Unfortunately the rendering of Autonym is a mess (sorry to say that, it's the best word to describe what I see, see my screenshot). This makes the situation a lot worse compared to the situation before where a few glyphs may be missing or displayed as rectangles. Now some pixels are completely missing. An ""o"" looks like an ""u"" and ""m"" looks like ""rri"", for example.
+
+Proposed solution: Either fix the font or simply don't use it on systems that don't have a problem with displaying the glyphs in the interlanguage links. If I disable Autonym (using the web developers tools) everything is back to normal, no glyphs are missing and no rectangles are displayed. In other words: Don't ""fix"" things that aren't broken. Thanks.
+
+**Attached**: {F12124}",1383300531,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Temporarily it can be fixed by adding in personal css:
+#p-lang div.body ul { font-family: sans-serif; }",1383297916,PHID-USER-jbysj3sdbucij47t2xt3,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Created attachment 13642
+Screenshot from en.wp
+
+**Attached**: {F12123}",1383262405,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers",I am getting very similar messed up rendering on Opera 12 on Windows XP with ClearType rendering enabled.,1383262199,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Language names blurred and difficult to read using the hardcoded ""Autonym"" font on Windows computers","Cannot reproduce with Win8, FF25 and 1024x768 on https://cs.wikipedia.org/wiki/ on crossbrowsertesting.com (only offering FF23 for XPSP3).",1383241926,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-du3phlfbnb3yvb3jrnn5,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page","An unclosed <ref> tag on the page eats up the rest of the page, typically including the requisite <reference> tag at the bottom of the page. However, VisualEditor handles the unclosed <ref> tag more gracefully, treating it as plain text.
+
+At the URL above, the wikitext:
+
+    Before <ref> during
+    after
+    <references />
+
+is rendered:
+
+    Before[1]
+    Cite error: <ref> tag found without <references/>
+
+whereas VisualEditor shows:
+
+    Before <ref> during↵after
+    There are no references on this page to include on this list.
+
+This issue was brought to my attention by an editor who somehow created the unclosed <ref> tag in VisualEditor. (See the initial revision of [[vi:Danh sách các chi tiết gợi nhớ đến Disney trong phim Enchanted]].) I’ve reached out to the editor for information on how they might’ve gotten into that state.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/User:Mxn/56306",1383041940,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-7y5mvenxogghsfr7glsa,task_description,declined
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page",https://gerrit.wikimedia.org/r/#/c/255258/ fixes PHP parser behavior. Nothing to do in Parsoid land.,1453350985,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page",The bug for the PHP parser is T17712.,1448403047,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page","I'm not sure; that depends what the more graceful behavior would be, but I would expect Parsoid to match Cite in any case. Does Parsoid's current behavior seem like a more reasonable way for Cite to handle unclosed <ref> tags?",1401478701,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page","So is this a request for matching the more graceful behavior in the PHP Cite implementation, or is it a request for Parsoid to truncate the page as well?",1401461783,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+"Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page","Never mind about that last part. It looks like they introduced the unclosed <ref> tag by hand, not using VisualEditor.",1383042640,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-7y5mvenxogghsfr7glsa,task_subcomment,NA
+Make ULS more lightweight,"For many users, ULS serves no practical purpose. It is also quite large, which can be problematic if you're not on a first-world internet connection (or are in rural US), is occasionally host to somewhat problematic bugs, and generally is not worth the trouble if you're not part of the target audience.
+
+So there should be a way for such people to just turn the thing off, not load it at all, and be happy.
+
+I appreciate that adding an option for this has been been wontfixed, though I don't know why, but even without there being an option in the interface, there SHOULD be support in the extension itself to disable it, regardless of where it actually appears.
+
+There should be a way for users who are truly and consistently inconvenienced by it to actually solve the underlying problem (such as with a hidden preference or cookie), instead of just hiding it. There should also be a way for third-party hosts to add such an option for their users who also fit the target audience, even if they don't necessarily want it on for everyone.
+
+As it is it seems to inconvenience as many people as it helps on wikimedia projects, and isn't very appealing to third-party hosts, either, despite it solving some very real problems facing some of our users as well.
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1383019140,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_description,resolved
+Make ULS more lightweight,Things have been improved. We are no longer loading lots and lots of code before user interaction. Now I get `jquery.uls.data` (31 KB) and few other modules <10 KB.,1468323414,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,Does someone know if this issue is still present and relevant for T15097? Seems not according to T58464#2452190,1468323163,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"https://www.mediawiki.org/wiki/Universal_Language_Selector/Announcement_Feb2014
+https://www.mediawiki.org/wiki/Universal_Language_Selector/Upcoming_development_plan",1392822875,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"Change 113957 merged by jenkins-bot:
+resources/images: Optimize all SVGs (partially by hand)
+
+https://gerrit.wikimedia.org/r/113957",1392799823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"Change 113957 had a related patch set uploaded by Bartosz Dziewoński:
+resources/images: Optimize all SVGs (partially by hand)
+
+https://gerrit.wikimedia.org/r/113957",1392734042,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"The table is from the output of mw.loader.inspect(). You can also run it from your developer tools console of your browser.
+
+But the result of that has a few caveats. ULS has to serve a small svg file(cog icon) to UI. See https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector/blob/master/resources/css/ext.uls.interlanguage.css#L1
+
+You can see the svg with 'embed' more than once. Also note that the ResourceLoader module will have css  with the image data embedded. So the RL module have  this repeated svg data at client side, it is an image, so it will have some size. While calculating the module size, the total size is javascript, css and this image data(potentially duplicated) at client side. But what matters is bandwidth usage and in this case you will see a big difference between actual bandwidth usage and the uncompressed RL module size at client side. This is because the module is gzip compressed while serving. Gzip is efficient in compressing the duplicated strings. In short, don't take the output of mw.loader.inspect literally.",1392695488,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to Amir E. Aharoni from comment #12)
+> (In reply to Bryce Glover from comment #11)
+> > I just added up how many kilobytes the ULS loader's scripts take up once
+> > loaded onto client systems using my Mac's Calculator.app, and it came out to
+> > 450.2 KB!!!  This definitely needs to be fixed!
+> 
+> In which conditions did you make this calculation?
+
+Oops; I should have mentioned that I just used my Mac's built-in Calculator.app application to add up all of the script sizes from the right-hand side of the table provided as an attachment by MZMcBride in Comment #5.  I thought that my source would be obvious!  Now that I think about it, though, where exactly did the results provided by that table come from again?",1392682911,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to Bryce Glover from comment #11)
+> I just added up how many kilobytes the ULS loader's scripts take up once
+> loaded onto client systems using my Mac's Calculator.app
+
+Such comments are not helpful if you do not provide exact steps to reproduce.",1392578194,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to Bryce Glover from comment #11)
+> I just added up how many kilobytes the ULS loader's scripts take up once
+> loaded onto client systems using my Mac's Calculator.app, and it came out to
+> 450.2 KB!!!  This definitely needs to be fixed!
+
+In which conditions did you make this calculation?",1392572510,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to MZMcBride from comment #5)
+> Created attachment 13629 [details]
+> Screenshot of mw.loader.inspect() from the English Wikipedia, 2013-10-30
+
+I just added up how many kilobytes the ULS loader's scripts take up once loaded onto client systems using my Mac's Calculator.app, and it came out to 450.2 KB!!!  This definitely needs to be fixed!
+
+**Attached**: {F12024}",1392569418,PHID-USER-tulrxb4ebie42howqlxj,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"So, as far as we know and until corrected the plan still is, per Erik Moeller, bug 56433 comment 22:
+> OK, then I'd like to request that the language engineering team implement
+> that
+> approach for now, unless there are issues we're overlooking. As noted, we can
+> attach EventLogging to font activation, and we could potentially also run
+> notices or calls-to-action in specific affected wikis. We can figure out in
+> the
+> next couple weeks if we want to prioritize getting back into a default-on
+> state
+> for automatic font delivery for some users/languages quickly, or if this
+> should
+> take a backseat to the language team's other priorities.
+> 
+> But, considering the significant payload added by automatic font delivery, I
+> think that's a reasonable compromise for now. I appreciate the team's efforts
+> to improve ULS performance across the board.
+
+https://gerrit.wikimedia.org/r/#/c/108024/ was already merged and is supposed to serve webfonts only when strictly necessary. So, once the way forward is detected, we need another report for what's needed to complete the plan.",1390339174,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,Removed dependency on bug 56514. It no longer is relevant after gerrit 93035.,1383550424,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to comment #6)
+> (In reply to comment #4)
+> > This isn't a helpful comment.
+> 
+> The way to avoid this is to define when a report can be considered fixed. 
+> ""Make X faster"" is an invalid report as everybody can disagree when it's
+> considered fast enough. Instead, ""Make X load within Y seconds"" has clear
+> criteria.
+
+On what hardware? On what connection? Where, geographically? This is not a clear criterium either, and I'd argue that you can't define a ""clear"" one.",1383156611,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"Lego, Ori, or anyone else who might know: is there a reason that ULS loads anything more than the init script by default? This is what VisualEditor does, as I understand it.",1383156306,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to comment #4)
+> This isn't a helpful comment.
+
+The way to avoid this is to define when a report can be considered fixed. 
+""Make X faster"" is an invalid report as everybody can disagree when it's considered fast enough. Instead, ""Make X load within Y seconds"" has clear criteria.  It's up to requesters to explain and define issues well enough to avoid invalid bug reports, so I disagree with your interpretation.",1383140125,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"Created attachment 13629
+Screenshot of mw.loader.inspect() from the English Wikipedia, 2013-10-30
+
+**Attached**: {F12024}",1383138633,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to comment #3)
+
+This isn't a helpful comment. Please don't leave unhelpful comments.
+
+Nobody is required to justify a bug report's existence to you. If you can't understand the bug, that's a personal problem. Try following the steps laid out in comment 2 (i.e., run mw.loader.inspect() on the English Wikipedia and look at its output).",1383138573,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"(In reply to comment #2)
+> I'm re-opening this bug with a focus on making ULS more lightweight and
+> acceptably performant.
+
+As it sohuld be possible for bug reports to define when they are fixed: 
+When exactly would ULS be ""lightweight enough"" and ""acceptably performant""? 
+
+Currently I consider this bug report unfixable (and hence INVALID) as requirements are highly subjective and it's impossible to say ""and now ULS is performant and lightweight enough so we can close this bug report"".",1383125871,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"According to mw.loader.inspect(), ULS appears to be by far the largest contributor to JavaScript load on <https://en.wikipedia.org/wiki/Main_Page>:
+
+* jquery.uls
+* jquery.uls.data
+* ext.uls.init
+* ext.uls.webfonts.repository
+* ext.uls.interface
+* ext.uls.languagenames
+* ext.uls.ime
+
+And possibly others. This is all for a feature that most users do not use. This is unacceptably large given that the vast majority of users on the English Wikipedia don't use ULS. This is disproportionate resource usage and is a valid bug to address.
+
+I'm re-opening this bug with a focus on making ULS more lightweight and acceptably performant.",1383053550,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+Make ULS more lightweight,"
+
+*** This bug has been marked as a duplicate of bug 46306 ***",1383031315,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-yf4ddfqwtxz3ayykgrqd,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","When editing a category page in VE, the page contents, such as a Subcategories heading and the list of categories in the cat, do not display.  
+
+A requested enhancement would be to display these items using the greyed/lined out display VE uses for other non-editable items.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383010800,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-tqu2xxzwj77ml37wgx66,task_description,resolved
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","Change 290653 merged by jenkins-bot:
+Genericise target initialisation across namespaces
+
+[[https://gerrit.wikimedia.org/r/290653]]",1464277796,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","Change 290653 had a related patch set uploaded (by Esanders):
+Genericise target initialisation across namespaces
+
+[[https://gerrit.wikimedia.org/r/290653]]
+",1464173756,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","Change 171155 had a related patch set uploaded by Alex Monk:
+[WIP] Show non-editable parts of pages in their normal places
+
+https://gerrit.wikimedia.org/r/171155",1415145586,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place",*** Bug 70821 has been marked as a duplicate of this bug. ***,1415046616,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place","(In reply to comment #1)
+> This
+
+… also applies to File: pages.",1383011121,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+"VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their ""normal"" place",This,1383010939,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqu2xxzwj77ml37wgx66,task_subcomment,NA
+VisualEditor: Get rid of ve.ce.Surface.prototype.setContentBranchNodeChanged,"Was introduced as a hack in https://gerrit.wikimedia.org/r/#/c/91786 but we should really find a way to make this unnecessary.
+",1382983860,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ezapkfj5jvedysawagen,task_description,open
+VisualEditor: Hatnote cleanup problem,"User reports:
+There does not seem to be a way to delete the first of two hatnotes without leaving extra space at the top of the article. 28bytes (talk) 03:20, 15 October 2013 (UTC)
+
+Link: https://en.wikipedia.org/w/index.php?title=Maxi_single&diff=577225537&oldid=568995072
+
+User config: Firefox 24.0/Windows 7/Monobook, but the same's true for Safari and for Macs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382954280,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-xdltfrkzgw4ix3sbkszo,task_description,resolved
+VisualEditor: Hatnote cleanup problem,"Re-checked: seems that it's not happening  anymore - look at the screenshots {F29287} {F29290}.
+
+Closing as Resolved.",1421687619,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-xdltfrkzgw4ix3sbkszo,task_subcomment,NA
+VisualEditor: Hatnote cleanup problem,"Re-checked: seems that it's not happening  anymore - look at the screenshots {F29287} {F29290}.
+
+Closing as Invalid.",1421452520,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-xdltfrkzgw4ix3sbkszo,task_subcomment,NA
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference","I think this is a code regression:
+
+The ""Watch this"" checkbox is always checked in Save dialog regardless of the user preference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382820900,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-tswnyxkeiir5xgyyjogc,task_description,resolved
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference","Change 95729 merged by jenkins-bot:
+Move setting of minor/watch defaults from MWSaveDialog to Target
+
+https://gerrit.wikimedia.org/r/95729",1385401101,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tswnyxkeiir5xgyyjogc,task_subcomment,NA
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference",*** Bug 57191 has been marked as a duplicate of this bug. ***,1384843375,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tswnyxkeiir5xgyyjogc,task_subcomment,NA
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference","Change 95729 had a related patch set uploaded by Jforrester:
+Move setting of minor/watch defaults from MWSaveDialog to Target
+
+https://gerrit.wikimedia.org/r/95729",1384768890,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tswnyxkeiir5xgyyjogc,task_subcomment,NA
+"VisualEditor: [Regression] ""Watch this"" checkbox checked in Save dialog regardless of the user preference","Probably solved by https://gerrit.wikimedia.org/r/#/c/95729/ ? That fixes a bug where if you had the 'watchcreations' preference set, ""Watch this"" would always be checked.",1384754215,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tswnyxkeiir5xgyyjogc,task_subcomment,NA
+VisualEditor: Refactor CSS so CE doesn't need to position things relative to the UI surface,"I see a lot of code like this:
+
+ve.Element.getRelativePosition( [something], this.getRoot().getSurface().getSurface().$ );
+
+Ideally, CE classes wouldn't need to reach into the UI surface for stuff like this. Positioning against the CE surface should just work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382473500,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5e3qnrqbc3plh3qb6zjr,task_description,open
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Seen in Reference and Transclusion, anywhere with an overlay containing a button saying 'Apply changes'. 
+
+* Hover the cursor over an existing Reference or Transclusion. 
+* Click the icon to invoke the Reference or Transclusion overlay
+* Without making any changes, click 'Apply changes'
+
+* Save page button goes from grey to active.
+
+* Click Save page
+* Click Review your changes. 
+
+Get message ""Could not start the review because your revision matches the latest version of this page.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1382388360,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_description,resolved
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","A single patch fixes the majority of the issues here, see the subtasks.",1420510877,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",">>! In T57976#823066, @Krenair wrote:
+> So this is now a tracker?
+
+No, it's a single task made up of sub-tasks.",1417830995,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",So this is now a tracker?,1417830684,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",">>! In T57976#823009, @Krenair wrote:
+> I kind of wish this had been broken into one bug for each dialog.
+
+Done. :-)",1417830313,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",I kind of wish this had been broken into one bug for each dialog.,1417828926,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Change 177944 merged by jenkins-bot:
+Don't re-enable apply changes in reference dialog if the changes have been undone
+
+[[https://gerrit.wikimedia.org/r/177944]]",1417827372,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Change 177944 had a related patch set uploaded (by Alex Monk):
+Don't re-enable apply changes in reference dialog if the changes have been undone
+
+[[https://gerrit.wikimedia.org/r/177944]]
+
+#patch-for-review",1417823506,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Change 176861 merged by jenkins-bot:
+Disable Apply Changes in reference dialog until changes have been made
+
+[[https://gerrit.wikimedia.org/r/176861]]",1417819588,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","Change 176861 had a related patch set uploaded (by Alex Monk):
+Disable Apply Changes in reference dialog until changes have been made
+
+[[https://gerrit.wikimedia.org/r/176861]]
+
+#patch-for-review",1417483872,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present",*** Bug 58231 has been marked as a duplicate of this bug. ***,1416357284,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","No, I think this still applies to the places mentioned in the description (transclusions and references).",1414192705,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+"VisualEditor: Dialogs should disable ""Apply changes"" until a change is present","This is not an OOUI bug, moving back to VE. Rather, it's a bug in the individual dialogs in VE that apparently commit no-op transactions when you click Apply changes without changing anything. Also, in most dialogs we disable the Apply changes button when there is nothing to change.
+
+Since this bug was filed in 2013, I imagine it might be mostly fixed now? We have some bugs in this area (filed individually as ""Apply changes is enabled even though XYZ"") but my impression is that generally we're pretty good about this now.",1414118984,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-owm5ukn67i2uhxyue7qi,task_subcomment,NA
+VisualEditor: Clean up constructor params to dm.Node subclasses,"* dm.LeafNode has (length, element), where length is ignored and forced to 0 by all subclasses except for dm.TextNode
+* dm.BranchNode has (children, element), length is computed while children are added
+
+The code in dm.Document constructing node trees needs to be aware of this, but at the same time it doesn't even use these parameters, because branch nodes are created as childless nodes that have their children added later, and text nodes are created with length zero and have the correct length set later. So we should just get rid of these parameters and make the constructors take a single element parameter, that would get them in line with other dm.Model subclasses (dm.Annotation and dm.MetaItem) as well.
+
+While we're at it, we should also fix the documentation that claims that the element parameter is optional, it really isn't.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382100600,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2thfovp27y2lm7rjxegt,task_description,resolved
+VisualEditor: Clean up constructor params to dm.Node subclasses,https://gerrit.wikimedia.org/r/#/c/135878/,1412590447,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2thfovp27y2lm7rjxegt,task_subcomment,NA
+VisualEditor: Clean up constructor params to dm.Node subclasses,"(In reply to comment #0)
+> While we're at it, we should also fix the documentation that claims that the
+> element parameter is optional, it really isn't.
+
+
+It is in fact optional. The lowest class (ve.dm.Model) has:
+> element || { 'type': this.constructor.static.name }",1382108417,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2thfovp27y2lm7rjxegt,task_subcomment,NA
+Removing stub template removes too many lines,"Intention:  To remove a stub template
+
+
+Expectation:  That the stub template would disappear and everything else (references list, navbox) would remain the same
+
+
+Steps to reproduce:
+
+1)  Go to https://en.wikipedia.org/w/index.php?title=Gastric_volvulus&oldid=567517399 or (probably) any other article that contains these items on separate, adjacent lines:
+
+ * A list of references (in this case, a single bulleted list item)
+ * A blank line
+ * A stub template
+ * A navigation template
+
+2)  Open the article in VisualEditor.
+
+3)  Click on the the stub template to select it.
+
+4)  Press the delete/backspace key (it's same key on a Mac) one time to delete the stub template (and nothing else).
+
+
+Result:
+
+Instead of getting the slightly shorter expected list:
+
+ * A list of references (in this case, a single bulleted list item)
+ * A blank line
+ * A navigation template
+
+this produced a single line containing both the reference list item and the navbox, with no intervening spaces or lines:
+
+ * A list of references (in this case, a single bulleted list item)Navigation template
+
+This broke the navbox formatting for readers.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Gastric_volvulus&diff=577403274&oldid=576282874",1382053680,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-2jrwjzhk56qqi6hbuy6z,task_description,open
+Removing stub template removes too many lines,"Confirmed on Firefox 25/Linux
+
+It seems from very quick experimentation that deleting a template also deletes the preceding line.",1383574643,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-2jrwjzhk56qqi6hbuy6z,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"1. Create a page with two links that point to the same page or URL, and a link that points to a different page/URL
+2. Inspect one of the twin links with the link inspector. The suggestions dropdown is displayed (*)
+3. Inspect the other twin link. The suggestions dropdown isn't displayed
+4. Inspect the third link. The suggestions dropdown is displayed again
+5. Inspect the link from #3. The suggestions dropdown is displayed now
+6. Close the inspector, the inspect the same link again. The suggestions dropdown isn't displayed
+
+This is because the value in the text input doesn't change when you inspect the same link twice or inspect two links with the same target. The link inspector should consistently display the dropdown when it opens.
+
+(*) I would argue that we should /not/ display the dropdown in this case, IMO it's useless and confusing. But the point of this bug is that we should have consistent behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382019060,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fhofyq422q3wz75cdddw,task_description,resolved
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"This is now fixed, but anyway masked by the expedient of not opening the suggestion box until the user changes something.",1402548843,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"Created attachment 13670
+showing wrong suggestions at the end of the previously selected link
+
+**Attached**: {F11975}",1383349835,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"Created attachment 13669
+Showing suggestions in blank space
+
+**Attached**: {F11974}",1383349782,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"Created attachment 13668
+Showing suggestions in blank space
+
+**Attached**: {F11973}",1383349564,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"In step 3, if i click on the link icon from the tool bar instead of pressing ctrl+k or command+k , then the link inspector opens up at the end of the text created in step 1.
+
+See the screenshots for more reference.",1383349480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link,"Another issue which might be related with this follows the following steps:
+
+1.Create any link with a target URL
+2.Inspect another link of the page with a different target URL
+3.Now point to a blank space and press ctrl+k or command+k
+
+Observed Result:
+
+The link inspector appears in a swipe way from right to left and the content of the link inspector is the suggestion of the link that was created in step 1.
+
+I am not sure how the expected result should be in this case when a user press command+k in an empty space.I think there should not be any pre-set suggestion for that.",1383346779,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fhofyq422q3wz75cdddw,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"According to https://gerrit.wikimedia.org/r/#/c/54984 , the new wikibugs code (not yet deployed) will split the wikibugs output into a myriad of channels (this is independent from the name of the default channel).
+
+This fragmentation is very annoying because it effectively subtracts important parts of the code/development/discussion from the normal public view on the main channel (whatever its name is) even though they are offtopic, hiding them in some secondary channel.
+The secondary channels should receive additional copies of the relay, but not remove them from the main channel if they are on topic (for instance, the visual editor for MediaWiki obviously is on topic for #mediawiki and #wikimedia-dev).
+ 
+As a fallback, if people really think those products are so unimportant/trashy (""noise"") as to be ignored by people on the main channel, I'd like a single unified feed somewhere, e.g. #mediawiki-feed (it's not clear to me what wm-bot4 [~wm-bot@wikimedia/bot/wm-bot] is doing there exactly).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52529
+https://bugzilla.wikimedia.org/show_bug.cgi?id=10760",1381952940,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-mb365ltelmuwscrj3lep,task_description,declined
+Don't fragment bugzilla conversation/IRC output,Sigh. http://lists.wikimedia.org/pipermail/wikitech-l/2014-May/076522.html,1400568876,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,Now done by pywikibugs.,1398198198,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"+1 to all bugs continuing to go to #mediawiki. and all commit output (At least to mediawiki + ext) go to either #mediawiki or #wikimedia-dev
+
+Having bug output in these channels helps bring new contributors in, and allows them to see what is being worked on. Moving it to #mediawiki-feed would destroy this.",1393012958,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"Yeah, wikibugs-l is a global watcher, and wikibugs bot just relays all mail that is sent there. So *everything* goes to #mediawiki, apart from security bugs.",1381956514,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"(In reply to comment #4)
+> This bug is not about ""all the feeds"": pywikibot is already on another
+> channel,
+> because it's not sent to wikibugs-l.
+
+Actually Pywikibot bugs show up in #mediawiki, and I wrote a python script which copies the output of wikibugs into #pywikipediabot if it's one of our bugs.",1381954492,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"(In reply to comment #3)
+> (In reply to comment #2)
+> > The conversation
+> 
+> Where is this conversation happening? I have opinions but I'd rather read
+> first
+> what has been discussed.
+
+I mean the development conversation.
+
+(In reply to comment #2)
+> The conversation is currently fragmented between #mediawiki (wikibugs) and
+> #wikimedia-dev (grrit-wm).
+
+That's another bug.
+
+> 
+> grrit-wm can also post to other channels on demand, such as #-operations and
+> #-visualeditor, which is a very useful feature (both of these are completely
+> useless in #mediawiki and only tangenially related in #wikimedia-dev).
+
+This is also another issue, and only in part overlapping this (gerrit changes are apparently considered more ""noisy"", otherwise they wouldn't have been moved first).
+
+> 
+> A separate channel that would *mirror* all other feeds would be okay, but a
+> *separate* one.
+
+This bug is not about ""all the feeds"": pywikibot is already on another channel, because it's not sent to wikibugs-l.",1381954287,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"(In reply to comment #2)
+> The conversation
+
+Where is this conversation happening? I have opinions but I'd rather read first what has been discussed.",1381953572,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,"The conversation is currently fragmented between #mediawiki (wikibugs) and #wikimedia-dev (grrit-wm).
+
+grrit-wm can also post to other channels on demand, such as #-operations and #-visualeditor, which is a very useful feature (both of these are completely useless in #mediawiki and only tangenially related in #wikimedia-dev).
+
+A separate channel that would *mirror* all other feeds would be okay, but a *separate* one.",1381953308,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+Don't fragment bugzilla conversation/IRC output,+1 to having it in #mediawiki-feed so people who want the full force of the firehose can have it.,1381953079,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-mb365ltelmuwscrj3lep,task_subcomment,NA
+VisualEditor: Support the Command+Delete keyboard command on Mac (delete current line) and others,"On Chrome Version 30.0.1599.69 on Mac OSX 10.8.5 the Command+Delete keyboard shortcut is ignored. In most text editors it deletes the entire line of content (try it in gmail or on bugzilla!)
+
+The Option+Delete keyboard key (to delete the previous word) and Option+Fn+Delete (to delete the following word) do work correctly. There is no Command+Fn+Delete shortcut.
+
+I do not have easy access to test this shortcut on other versions of Chrome, nor do I know what the shortcut is on Firefox.",1381942500,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-k4x357kadd74krhi4jsl,task_description,resolved
+VisualEditor: Support the Command+Delete keyboard command on Mac (delete current line) and others,Command + Delete works for me in Chrome 43 and Firefox 40 on OS X 10.10.3. Tentatively closing.,1434667851,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-k4x357kadd74krhi4jsl,task_subcomment,NA
+VisualEditor: Highlights triggered while resizing aren't moved correctly,"While resizing an image with live preview, the highlight on the image is updated correctly. But if you mouse over another image while resizing, then that image's highlight isn't updated for the resize. This is a problem in situations where resizing the first image moves the second image, in that case the highlight stays where it was when you first entered the image.
+
+Maybe we just shouldn't show highlights at all while dragging?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55789",1381926000,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-du4fblehtatuv452azlx,task_description,resolved
+VisualEditor: Highlights triggered while resizing aren't moved correctly,"Agreed, I think we did back in January.",1400696049,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-du4fblehtatuv452azlx,task_subcomment,NA
+VisualEditor: Highlights triggered while resizing aren't moved correctly,I think we fixed this ages ago.,1400695667,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-du4fblehtatuv452azlx,task_subcomment,NA
+VisualEditor: Move floating functionality from SurfaceToolbar to Toolbar?,"The floating code is in ve.ui.SurfaceToolbar instead of OO.ui.Toolbar, but cursory inspection of the code indicates that it doesn't reach into the surface and doesn't receive any events from the surface, apart from a minor bit that ensures the cursor isn't obscured by the toolbar.
+
+Wanting to float a toolbar seems generic enough, so couldn't this be made into generic OO.ui functionality?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381921260,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ooymibfombnrpq5ugplm,task_description,open
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""","Intention:  To create a block of text to check line wrapping.
+
+
+Expectation:  That I'd end up with a block of plain paragraph-formatted text.
+
+
+Steps to reproduce:
+
+1)  Start with a page containing some text and a few section headings.  In my case, it was a list.  
+
+2)  Select all the text in one section using arrow/cursor keys, including all of the last line (including the blank part at the end of the paragraph), but none of the section heading that follows.
+
+4)  Copy this.
+
+5)  Make a new, blank paragraph-formatted line.
+
+6)  Paste the copied text into the new line.
+
+
+Results:  You get the desired paragraph, followed by a == <nowiki /> == section heading.
+
+See https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=577354576&oldid=577352415
+
+(For bonus points, if you skip step #5, you'll get your pasted text set to ==Section heading== formatting.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T52100}
+{T61647}",1381881120,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_description,resolved
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""","Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output <p> instead of <h#>
+
+[[https://gerrit.wikimedia.org/r/162310]]",1426893388,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_subcomment,NA
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""","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",1424197333,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_subcomment,NA
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""","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",1411496979,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_subcomment,NA
+"VisualEditor: Copying and pasting results in new blank section heading: ""== <nowiki /> ==""",This may be related to bug 49452 and/or bug 50100,1381881210,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-4m3elcu2mghgs5wp7t2j,task_subcomment,NA
+Multiline list items rendering differently in ContentEditable than the resulting wikitext,"This is an interesting issue that, as far as I understand, can be either (or both) VE and Parsoid, and seems to be limited by wikitext. 
+
+I'm not entirely sure what the strategy here should be -- If the final article markup is ""the way things are supposed to be"" then the fix should be to correct the way things look to the user in ContentEditable so they match the final article display. 
+
+However, there might be a creative way to manipulate the wikitext in Parsoid (or the html VE sends to Parsoid) so that the end result fits what VisualEditor presents.
+
+The first solution will disallow multiline list items. The second solution would run the risk of having html tags in wikitext, or worse, having the dreaded dirty diffs if the desired multiline list item is more complex.
+
+Here's how to see the issue:
+(Refer to this image: http://mg.viewskew.com/mgoblin_media/media_entries/432/ve_listbug.png )
+
+1. Edit some wiki page (can be empty/new)
+2. Type 3-4 lines
+3. Mark the lines and make them a list with the list button
+4. Go to the second element (or whatever one that is in the middle of the list)
+5. Go to the end of that listItem's line, and hit ""Shift-Enter""
+6. In VisualEditor, the behavior is similar to other word processors with multiline list element -- you get a second line that is indented the same as the list item you're under.
+7. Type something so you have text on that multiline segment. (#1 in the image) 
+8. Click 'save' and review changes; wikitext is not representing what we see on the screen (see #2 in the image)
+9. Save the article -- the article presents a different format than what VE showed (#3 in the image) and presents a different content to edit if we want to edit that article again (#4 in the image)
+
+The way I see it (and I may well be wrong, as I'm not that familiar with wikitext) -- we can either fix this bug so VE presents the same display as the final article (as in, disallow shift-enter in lists) or we need to split multiline items into paragraphs that can render as such into wikitext (not sure if that's possible) -- the other alternative is to force a <br /> on multiline lists, which would make the wikitext into something like
+
+* item 1
+* item 2
+* item 3<br />and its multiline
+* item 4
+
+And that works perfectly in the article and in edit mode -- but it can be limited in what can be done inside a multiline list item, and requires the use of <br /> tag inside the wikitext. 
+
+Also, there may be more cases of complex list items with VE's expanding features. For instance, there can be cases where a multiline list item should contain a certain language block, or a short code highlight segment, or a <math> block. Right now they render proplery in CE if added as multiline list item, but break the list and become separate paragraph items on save.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381854300,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-dpieimh3wxp5zjcp2w6f,task_description,duplicate
+Multiline list items rendering differently in ContentEditable than the resulting wikitext,"Duplicate of T110986. This one is older, but the other has more discussion on it (sorry @Mooeypoo)",1701961617,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dpieimh3wxp5zjcp2w6f,task_subcomment,NA
+Multiline list items rendering differently in ContentEditable than the resulting wikitext,">>! In T57746#968491, @matmarex wrote:
+> The link to the image is dead now. Is this the same issue as T70800?
+
+According to the reproduction steps, this seems rather the same issue as T110986.
+
+I’m not sure about set child task.",1636496570,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-dpieimh3wxp5zjcp2w6f,task_subcomment,NA
+Multiline list items rendering differently in ContentEditable than the resulting wikitext,The link to the image is dead now. Is this the same issue as T70800?,1420909208,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dpieimh3wxp5zjcp2w6f,task_subcomment,NA
+VisualEditor: Wrong link rendered in edit mode when you click link in drop-down,"To reproduce:
+
+1. Goto https://en.wikipedia.org/w/index.php?title=Lancaster,_Pennsylvania&oldid=576777823&veaction=edit
+3. Highlight 'Brownfields'
+4. Press Ctrl-K
+5. Type 'brownfield land' as target.
+6. Click matching entry in drop-down once to accept.
+7. Click on unrelated text to hide the link widget.
+
+The internal representation is correct (as shown in e.g. 'Review your changes'), but the displayed/rendered link goes to https://en.wikipedia.org/w/Brownfields , not the correct target.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381813980,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-2iussc7hskb3wyvivj3j,task_description,resolved
+VisualEditor: Wrong link rendered in edit mode when you click link in drop-down,"This was fixed by Ed's re-working of these recently, I think.",1402549905,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2iussc7hskb3wyvivj3j,task_subcomment,NA
+VisualEditor: Fetch new image rendering after resize,"To prevent images which have just been scaled up from looking pixelated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381761840,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yhklbztfy4qioy5s3nw3,task_description,resolved
+VisualEditor: Fetch new image rendering after resize,"Change 89809 merged by jenkins-bot:
+Re-render images after resize
+
+https://gerrit.wikimedia.org/r/89809",1381961020,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yhklbztfy4qioy5s3nw3,task_subcomment,NA
+VisualEditor: Fetch new image rendering after resize,"Change 89809 had a related patch set uploaded by Esanders:
+Re-render images after resize.
+
+https://gerrit.wikimedia.org/r/89809",1381839582,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yhklbztfy4qioy5s3nw3,task_subcomment,NA
+Add mediawiki.ui dialogs,"mediawiki.ui should have dialogs/modals.  The new dialogs in GettingStarted can be used as a starting point, but more work is needed.  This includes choosing the right level of abstraction, and how to implement them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381359000,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_description,declined
+Add mediawiki.ui dialogs,"The mediawiki-ui styles in core are still maintained a little while longer, but dialogs seems like quite a significant task to take on. Engineering effort that is probably better invested elsewhere.
+
+Closing for now, though patches welcome if someone can volunteer reviewing it.",1426301201,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,">>! In T57534#943582, @Spage wrote:
+> OOUI's dialogs with the mediawiki.ui skin are probably a viable alternative.
+
+Yeah.  If there is a general consensus to move to OOJS-UI, this is probably a WONTFIX.",1421193543,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"Matt originally wrote:
+> The new dialogs in GettingStarted can be used as a starting point, but more work is needed
+
+Flow has implemented a general-purpose `mw.Modal` in [[ https://github.com/wikimedia/mediawiki-extensions-Flow/blob/master/modules/engine/misc/mw-ui.modal.js | mw.ui.modal.js]], see  Shahyar's e-mail to the design list in October ""MW UI Modals First Version & Concept"" ([[https://lists.wikimedia.org/pipermail/design/2014-October/002183.html | in ASCII]], but much easier to read the original HTML). There are a lot of features in Flow's modal tailored to [[ https://trello.com/c/uAoYLKf1/3-multi-step-modal-dialog | the design spec in Trello ]]. It use OOjs' EventEmitter.
+
+OOUI's dialogs with the mediawiki.ui skin are probably a viable alternative.
+",1419880579,PHID-USER-gbl4hfak3cfurt3c7skd,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"Matt originally wrote:
+> The new dialogs in GettingStarted can be used as a starting point, but more work is needed
+
+Flow has implemented a general-purpose `mw.Modal` in
+[[ https://github.com/wikimedia/mediawiki-extensions-Flow/blob/master/modules/engine/misc/mw-ui.modal.js | mw.ui.modal.js]], see  Shahyar's e-mail to the design list in October ""MW UI Modals First Version & Concept"" ([[https://lists.wikimedia.org/pipermail/design/2014-October/002183.html | in ASCII]], but much easier to read the original HTML) There are a lot of features in Flow's modal tailored to [[ https://trello.com/c/uAoYLKf1/3-multi-step-modal-dialog | the design spec in Trello ]]. It use OOjs' EventEmitter.
+
+OOUI's dialogs with the mediawiki.ui skin are probably a viable alternative.
+",1419481997,PHID-USER-gbl4hfak3cfurt3c7skd,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #8)
+> As for centring, the iframes don't particularly help there but I do know that
+> in VE we have a satisfying way of centring the dialog
+> vertically/horizontally.
+> 
+> The centring of dialogs is generally a solved problem in web development
+> afaik.
+> There's different ways to go about it, but there's at least 1 commonly used
+> way that works.
+
+I have a working solution, but it doesn't work in IE 6 or 7 (bug 55487).  If you have a recommendation, I'd be glad to look at it.
+
+> On the subject, oo.ui dialogs do have an interesting aspect that is worth
+> mentioning. They don't require a fixed width/height. CSS min-height /
+> max-height is dynamically honoured (it can shrink/grow, and overflow:auto
+> will show scrollbars if needed), and browser resizing as well.
+
+Unfortunately, that's an example of a compatibility issue which we're going to have to grapple with.  IE6 apparently can't support both min-height and max-height on the same element (http://stackoverflow.com/questions/1467664/how-to-implement-cross-browser-min-height-and-max-height-at-the-same-time)
+
+> As for the CSS, that's going to be the area that'll need most manual testing
+> and fixing. I think most browser bugs we account for date back pretty far (we
+> tend to IE8, Opera 12 and recent Firefox/Chrome).
+> 
+> Though IE6, IE7 and Firefox 4 (which would be the main browsers missing
+> between
+> VE requirements and MW requirements) do have a ton of specific quirks, afaik
+> those are all bugs that can be worked around, not actual missing CSS features
+> that would be blockers (aside from CSS3 enhancements, which will be absent
+> but
+> those degrade gracefully).
+
+Yeah, I primarily meant CSS and rendering.  I agree some have relatively simple workarounds.  However, others are a bit more complicated.",1381366742,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #7)
+> (In reply to comment #6)
+> > (In reply to comment #4)
+> > oo.ui is about two years ahead of mw.ui in development time, but we built
+> > things as we needed them in VisualEditor so there might be certain kinds of
+> > widgets that mw.ui has that aren't in oo.ui yet. Things like dialog support,
+> > though, have existed in oo.ui for a long time. oo.ui also fully supports
+> > running all of its widgets in iframes (which is how dialogs are done as
+> > well).
+> 
+> I don't really know much about the advantages of iframes for this kind of
+> thing.  However, I did have some issues (e.g. full horizontal and modal
+> centering), so if it solves that, that would be nice.
+
+
+iframes are mostly to allow text selection, focus and other complicated and cross-browser unstable states to remain while the dialog is up.
+
+As for centring, the iframes don't particularly help there but I do know that in VE we have a satisfying way of centring the dialog vertically/horizontally.
+
+The centring of dialogs is generally a solved problem in web development afaik. There's different ways to go about it, but there's at least 1 commonly used way that works.
+
+On the subject, oo.ui dialogs do have an interesting aspect that is worth mentioning. They don't require a fixed width/height. CSS min-height / max-height is dynamically honoured (it can shrink/grow, and overflow:auto will show scrollbars if needed), and browser resizing as well.
+
+(In reply to comment #7)
+> 
+> We'll be supporting more browsers than VE does, so oo.ui will need to do the
+> same if we take that approach.
+
+As far as javascript code itself, we currently require the browser to support most ES5 features (IE8 is missing some ES5 features, but we haven't needed those yet, and we keep an eye out for those with feature tests).
+
+At this point we only use ES5 features that have established polyfills (Array#filter, Function#bind, Object#create, String#trim, JSON.stringify etc., full list at[1]). We don't polyfill them right now because we don't have to, but we can easily bring in an es5shim if we have to.
+
+As for the CSS, that's going to be the area that'll need most manual testing and fixing. I think most browser bugs we account for date back pretty far (we tend to IE8, Opera 12 and recent Firefox/Chrome).
+
+Though IE6, IE7 and Firefox 4 (which would be the main browsers missing between VE requirements and MW requirements) do have a ton of specific quirks, afaik those are all bugs that can be worked around, not actual missing CSS features that would be blockers (aside from CSS3 enhancements, which will be absent but those degrade gracefully).
+
+
+[1] https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/4da68b71d11f15b10e2e1f418025b438954e7da5/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js#L68-L85",1381363772,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #6)
+> (In reply to comment #4)
+> > Are you planning to put oo.ui in core?  If so, are you going to merge it with
+> > mediawiki.ui?
+> oo.ui is going to be a standalone library, but we're planning for MW core to
+> depend on it and bundle it, same as with e.g. jQuery.
+
+Makes sense.
+
+> I personally would like to make mw.ui an extension of oo.ui, making
+> MW-specific things in mw.ui extensions of generic things in oo.ui, and moving 
+> any generic functionality from mw.ui into oo.ui if oo.ui doesn't already have 
+> it.
+
+That seems reasonable, though it might take some practice drawing that line.
+
+> oo.ui is about two years ahead of mw.ui in development time, but we built
+> things as we needed them in VisualEditor so there might be certain kinds of
+> widgets that mw.ui has that aren't in oo.ui yet. Things like dialog support,
+> though, have existed in oo.ui for a long time. oo.ui also fully supports
+> running all of its widgets in iframes (which is how dialogs are done as
+> well).
+
+I don't really know much about the advantages of iframes for this kind of thing.  However, I did have some issues (e.g. full horizontal and modal centering), so if it solves that, that would be nice.
+
+We'll be supporting more browsers than VE does, so oo.ui will need to do the same if we take that approach.",1381361993,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #4)
+> Are you planning to put oo.ui in core?  If so, are you going to merge it with
+> mediawiki.ui?
+oo.ui is going to be a standalone library, but we're planning for MW core to depend on it and bundle it, same as with e.g. jQuery.
+
+I personally would like to make mw.ui an extension of oo.ui, making MW-specific things in mw.ui extensions of generic things in oo.ui, and moving any generic functionality from mw.ui into oo.ui if oo.ui doesn't already have it.
+
+oo.ui is about two years ahead of mw.ui in development time, but we built things as we needed them in VisualEditor so there might be certain kinds of widgets that mw.ui has that aren't in oo.ui yet. Things like dialog support, though, have existed in oo.ui for a long time. oo.ui also fully supports running all of its widgets in iframes (which is how dialogs are done as well).",1381360769,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"Created attachment 13462
+Modal from GettingStarted
+
+This shows an example modal from GettingStarted.  This appearance is not necessarily exactly how the core version would look.
+
+**Attached**: {F12155}",1381359724,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"Are you planning to put oo.ui in core?  If so, are you going to merge it with mediawiki.ui?",1381359603,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"(In reply to comment #1)
+> Trevor and Roan mentioned that they may be trying to make ve.ui (aka oo.ui)
+> dialogs available to non-VisualEditor products and wikis. Those may be
+> appropriate to use/adapt for our purposes, we just need to compare it all.
+A WIP for that was just put in Gerrit: https://gerrit.wikimedia.org/r/#/c/88896/",1381359434,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"This should include the grey overlay as well.  Ideally, this dialog code will be general enough that GuidedTour can be ported to use it as well.",1381359407,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+Add mediawiki.ui dialogs,"**swalling** wrote:
+
+For reference, the dialogs being used in the currently-released GettingStarted A/B test are in Extension:GettingStarted's resources. 
+
+Trevor and Roan mentioned that they may be trying to make ve.ui (aka oo.ui) dialogs available to non-VisualEditor products and wikis. Those may be appropriate to use/adapt for our purposes, we just need to compare it all.",1381359330,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-dgyqtyk3mbic5zgwmitl,task_subcomment,NA
+VisualEditor: MWSyntaxHighlight* is badly broken,"ve.dm.MWSyntaxHighlightNode.static.toDataElements:
+* Assumes it always receives two DOM elements, one div and one span. This is dependent on an interaction issue between Parsoid and MediaWiki, and isn't always the case.
+* Stores the span and the div as two separate attributes, rather than a single domElements attribute containing an array
+* Stores the span and the div by reference rather than cloning them
+
+ve.dm.MWSyntaxHighlightNode.static.toDomElements:
+* Assumes attributes.span is always set, although per the above it may be undefined. In case it is undefined, this function returns [<div>, undefined] which ends up crashing VE with a DOM error (""DOM Exception 8"") because undefined is fed to appendChild() by the converter
+* Uses attributes.div and attributes.span by reference. This is bad because:
+** calling .appendChild() on a node that's already attached elsewhere removes it from its old location
+** the original nodes received by toDataElements() are in a different document than the output of this function is supposed to be, so we end up attaching nodes to the wrong document
+** the correct way to do this is ve.copyDomElements( originalDomElements, doc ) where doc is the second parameter
+* Unconditionally sets the data-mw attribute, without checking if anything actually changed. This should be avoided, because reordering of keys in the JSON blob may dirty the DOM and trigger a corruption warning. See the last bit of ve.dm.MWReferenceNode.static.toDomElements (dealing with originalMw) for an example of how to do this correctly
+** Note that this .setAttribute() call is once again modifying the original <div> by reference
+* Assumes attributes.div is always set, which won't be true for newly created MWSyntaxHighlightNodes that didn't come from Parsoid but were created by the user in VE. For such nodes, the .setAttribute() call will crash the editor. But we never get there because ...
+
+ve.ui.MWSyntaxHighlightDialog.prototype.onOpen:
+* Assumes that there's always a FocusedNode when the dialog opens. However, this isn't true in creation mode (i.e. when opening the dialog from the toolbar without selecting an existing node), and so opening the dialog in creation mode crashes the editor when trying to do this.sourceNode.getModel(). This means it's impossible to create new MWSyntaxHighlightNodes with VE
+* Note that there's also no if ( this.sourceNode instanceof ve.dm.MWSyntaxHighlightNode ) check, which means this dialog will attempt to edit other types of nodes if it's opened while such a node is focused
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381358700,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_description,open
+VisualEditor: MWSyntaxHighlight* is badly broken,"Another bug discovered:
+
+On every click in the edit area in the dialog, an error appears in the console:
+
+TypeError: e.innerText is undefined
+parseInt(e.getAttribute('idx'),10) + e.innerText.length > model);
+
+in VisualEditor/modules/syntaxhighlight/ve.ui.MWSyntaxHighlightSimpleSurface.js
+line #1252",1383947447,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_subcomment,NA
+VisualEditor: MWSyntaxHighlight* is badly broken,"Patch to disable SyntaxHighlight is now merged, so this problem will be suppressed with the production push tomorrow morning; restoring to ""ASSIGNED"".",1381370918,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_subcomment,NA
+VisualEditor: MWSyntaxHighlight* is badly broken,"Change 88901 merged by jenkins-bot:
+Remove SyntaxHighlight from the experimental set
+
+https://gerrit.wikimedia.org/r/88901",1381361798,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_subcomment,NA
+VisualEditor: MWSyntaxHighlight* is badly broken,"Change 88901 had a related patch set uploaded by Catrope:
+Remove SyntaxHighlight from the experimental set
+
+https://gerrit.wikimedia.org/r/88901",1381361403,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ft4llcu4k2rwkptmn6t6,task_subcomment,NA
+"Enforce proper nesting of most templates, and encapsulate compound content blocks","Transclusions can currently affect arbitrary parts of the page by producing unbalanced HTML. This makes both WYSIWYG editing and efficient updates difficult. We would thus like to move towards properly nested templates as much as possible. For existing multi-transclusion content we would like to enforce nesting as a unit, possibly using a <domparse> extension-like tag wrapping such a content block. This would still let us reuse expansions for multi-template content, which is important for large list pages like http://fr.wikipedia.org/wiki/Liste_des_premiers_pr%C3%A9fets_fran%C3%A7ais_(1800-1815).
+
+The solution should:
+* work with old and new revisions, with predictable HTML diff behavior
+* support multi-transclusion/extension content reuse
+* support a mix of transclusions, extension tags and page content
+* work well with the VisualEditor preview
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381345200,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-oelrynugtph5rjeyq7u4,task_description,duplicate
+"Enforce proper nesting of most templates, and encapsulate compound content blocks",I am just going to merge this into the Balanced Templates RFC since that captures most of the requirement here. The compound content block issues would be partially ameliorated by using heredoc syntax in some cases.,1582154907,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-oelrynugtph5rjeyq7u4,task_subcomment,NA
+"Enforce proper nesting of most templates, and encapsulate compound content blocks","Lowering the priority a bit, as other issues are more pressing currently.",1386109375,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-oelrynugtph5rjeyq7u4,task_subcomment,NA
+"Enforce proper nesting of most templates, and encapsulate compound content blocks",This is roadmap item https://www.mediawiki.org/wiki/Parsoid/Roadmap#Research_.2F_prototype:_Enforce_proper_nesting_of_most_templates.2C_and_encapsulate_compound_content_blocks_.5Bhard.2C_Q3-Q4_2013.5D,1381345264,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-oelrynugtph5rjeyq7u4,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","From https://integration.wikimedia.org/ci/job/mwext-cldr-phpcs-strict/1/console:
+
+11:21:52 FILE: ...nkins-slave/workspace/mwext-cldr-phpcs-strict/CldrNames/CldrNamesMy.php
+11:21:52  643 | ERROR   | Line exceeds maximum limit of 120 characters; contains 162
+11:21:52  648 | WARNING | Line exceeds 100 characters; contains 109 characters
+
+These are the lines in question:
+
+	'UM' => 'ယူနိုက်တက်စတိတ် အပြင်ထွက် နေသည့် သေးငယ်သောကျွန်းများ',
+	'VC' => 'စိန့်ဗင့်ဆင့်နှင့် သည်ဂရဲနာဒင်းစ်',
+
+Assuming tab width is 4, the line lengths are 67 and 48 respectively.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: minor",1381318620,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-igmisx4akeh5yixglyfo,task_description,resolved
+"PHP CodeSniffer reports line length based on bytes, not on characters","I have retriggered the original build:
+
+https://integration.wikimedia.org/ci/job/mwext-cldr-phpcs-strict/4/console
+
+The phpcs command being run is:
+
+
+ phpcs -v -s . --encoding=utf-8 \
+  --standard=/var/lib/jenkins/tools/mwcodesniffer/MediaWiki \
+  --extensions=php,php5,inc,sample \
+  '--ignore=languages/messages/Messages,*.i18n.php,*.i18n.alias.php' \
+  --report-checkstyle=checkstyle-phpcs.xml \
+  --report-full
+
+And the result is a SUCCESS.  So the fix was indeed to pass '--encoding=utf-8' to phpcs :-]",1382434399,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","All jobs got refreshed. That should fix the issue now, if that is actually the case I guess we can close the bug report.",1381396600,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","(In reply to comment #5)
+> Have the jobs been pushed? The change is merged but in
+> https://integration.wikimedia.org/ci/job/mwext-VisualEditor-phpcs-HEAD/1524/
+> console
+> I don't see --encoding being passed.
+
+Good catch Timo. Something went wrong when I refreshed the jobs :(
+
+Refreshing them:
+
+
+$ grep 'encoding=utf' /var/lib/jenkins/jobs/*phpcs*/config.xml
+/var/lib/jenkins/jobs/mwext-AbuseFilter-phpcs-HEAD/config.xml: --encoding=utf-8 \
+/var/lib/jenkins/jobs/mwext-ActiveAbstract-phpcs-HEAD/config.xml: --encoding=ut-8 \
+/var/lib/jenkins/jobs/mwext-AdminLinks-phpcs-HEAD/config.xml: --encoding=utf-8 \",1381395346,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters",Have the jobs been pushed? The change is merged but in https://integration.wikimedia.org/ci/job/mwext-VisualEditor-phpcs-HEAD/1524/console I don't see --encoding being passed.,1381343238,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","Change 88743 merged by jenkins-bot:
+Specify encoding of source files as utf-8
+
+https://gerrit.wikimedia.org/r/88743",1381329601,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","Change 88743 had a related patch set uploaded by Siebrand:
+Specify encoding of source files as utf-8
+
+https://gerrit.wikimedia.org/r/88743",1381328452,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","Our PHP files should be UTF-8 encoded, so we should run CodeSniffer in that mode. I'll see if I can submit a patch...",1381326992,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+"PHP CodeSniffer reports line length based on bytes, not on characters","phpcs defaults to iso-8859-1 defined in PHP_CODESNIFFER_ENCODING
+
+CodeSniffer/Standards/Generic/Sniffs/Files/LineLengthSniff.php uses strlen(), whenever the encoding is not iso-8859-1 it would use:
+
+  iconv_strlen($lineContent, PHP_CODESNIFFER_ENCODING);
+
+So need to pass:
+
+ --encoding=UTF-8",1381320099,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-igmisx4akeh5yixglyfo,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Right now jQuery.IME is horrendously, horribly broken when using VisualEditor (a quick perusal of bugs that make it unusable include bug 54421, bug 53700, bug 53701, bug 53705, bug 53706, bug 53711, bug 54283, bug 54331, bug 54334 and others).
+
+Having the jQuery.IME icon show up when it is actively broken makes a promise to the user that we can't possibly hope to meet right now.
+
+Please disable jquery.IME from VisualEditor surfaces entirely until we can get some proper testing and work done.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1381280040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4x34z4rnugcat2zdme3x,task_description,resolved
+Disable jquery.IME operating on VisualEditor surfaces,"> We will probably just ride the train on
+> Thursday rather than introduce an out-of-sequence deployment if that's OK.
+
+Preferred.",1381329931,PHID-USER-w5a723w3wes6jd5wskgg,True,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"(In reply to comment #5)
+> Patch merged. I think you can deploy HEAD of master of ULS whenever it's
+> convenient for you guys, James. There have been no functional changes but
+> this one in the past week.
+
+Thank you, Siebrand and Santhosh. We will probably just ride the train on Thursday rather than introduce an out-of-sequence deployment if that's OK.",1381329712,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Patch merged. I think you can deploy HEAD of master of ULS whenever it's convenient for you guys, James. There have been no functional changes but this one in the past week.",1381329332,PHID-USER-w5a723w3wes6jd5wskgg,True,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Change 88727 merged by jenkins-bot:
+Disable jquery.ime for VE till IME support is improved
+
+https://gerrit.wikimedia.org/r/88727",1381329205,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Change 88727 had a related patch set uploaded by Santhosh:
+Disable jquery.ime for VE till IME support is improved
+
+https://gerrit.wikimedia.org/r/88727",1381325894,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Just to be clear, VE and jQuery.IME are making incompatible assumptions about the javascript event sequences expected when entering text in an IME.
+
+To be fair, that's not really anyone's fault because (a) de jure, the standards are still emerging, and (b) de facto, every single browser/OS/IME combination seems to generate a different weird and wonderful sequence of events.
+
+We're currently refactoring the VE CE Surface code to make as few assumptions as possible about IME events. I expect we can do work from the jQuery.IME side too, to bring the two into line.",1381306572,PHID-USER-lliyevigiycjbybglftk,True,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+Disable jquery.IME operating on VisualEditor surfaces,"Not sure I like the framing. VE mangles IME input horribly and horrendously, not the other way around may be more accurate.
+
+We can disable jQuery.IME in content editable divs of VisualEditor because it cannot handle input methods. Which class identifies editable divs of VisualEditor?",1381303119,PHID-USER-w5a723w3wes6jd5wskgg,True,PHID-TASK-4x34z4rnugcat2zdme3x,task_subcomment,NA
+VisualEditor: DM's list of the page's categories can be invalidated by e.g. adding a template that inherits a category,"When adding a template that also adds a category, after saving the list of categories is not updated until the page is reloaded.
+
+To reproduce:
+
+1. Load any page in VE
+2. Add any template that also adds a category, e.g. {{user en}}
+3. Save page
+
+Expected behaviour: The list of categories includes the newly added category, e.g. [[Category:User en-N]]
+Actual behaviour: The list of categories is not updated.
+
+It doesn't seem to matter whether the category is plain or hidden.
+
+Firefox 24 on Linux using Monobook skin
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1381104060,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gc3mafjeizbrumfuxqil,task_description,open
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"With wikitext editing, people work around this by writing long articles in word, or relying on browsers remembering form data if it crashes.
+
+Perhaps with local storage we can take periodic snapshots of DM HTML, or even the entire surface state (DM data, IV store, internal list, transaction history etc.) and offer to restore it if the changes went unsaved.
+
+See also:
+* T39992 - Review and deploy Drafts extension to Wikimedia wikis
+* T75241 - Auto-save to increase chances of lost edits recovery",1381073520,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_description,resolved
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4047400, @Kaartic wrote:
+> Nice point, but ... only if the user actually does know that there is a feature known as ""autosave"" and it recovers their edits"" **silently** in some cases. What I'm trying to say is, this might become a //misfeature// if there are possibilities that we might recover the edits it when we shouldn't have AND we don't let the user know that we recover edits silently!
+> 
+> I guess we should at least show a fade away notice when we recover the edits thus letting the user know about the feature.
+
+Sorry, when I said ""silently"" I meant without a modal dialog. We will always show at least the notification when edits are recovered. This is an improvement on the current wikitext editor where the browser can automatically recover the state of the textarea without telling the user.
+
+",1521479444,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,@Deskana ah good.  I posted the info here when I couldn't find any mention or task of the 'switching editors' issue. Should the new task be added to the Related Objects task graph?,1521041012,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4048147, @Alsee wrote:
+> Report from [[ https://www.mediawiki.org/wiki/Topic:U9ad8eelljphdgao | VisualEditor/Feedback ]]:
+> //Whenever I switch from VE to the source editor, and then switch back to VE, it literally deletes the changes I made with the source editor, and then it gives me a ridiculous message saying the following://
+> //""Changes recovered Your unsaved changes have been automatically recovered.""//
+> //Well, thanks, but how do I get rid of this? Now I can't use VE properly anymore.//
+
+T189381.",1521039768,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Aklapper are you kidding? This is clearly a serious bug in the new code, and it **directly** relates to the discussion in the previous dozen comments.",1521038715,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Alsee: Support questions are handled on https://www.mediawiki.org/wiki/VisualEditor/Feedback , not here.",1521027190,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Report from [[ https://www.mediawiki.org/wiki/Topic:U9ad8eelljphdgao | VisualEditor/Feedback ]]:
+//Whenever I switch from VE to the source editor, and then switch back to VE, it literally deletes the changes I made with the source editor, and then it gives me a ridiculous message saying the following://
+//""Changes recovered Your unsaved changes have been automatically recovered.""//
+//Well, thanks, but how do I get rid of this? Now I can't use VE properly anymore.//",1520978923,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4046224, @Esanders wrote:
+> In the common case where the document IDs do match we continue to recover silently, ...
+
+Nice point, but ... only if the user actually does know that there is a feature known as ""autosave"" and it recovers their edits"" **silently** in some cases. What I'm trying to say is, this might become a //misfeature// if there are possibilities that we might recover the edits it when we shouldn't have AND we don't let the user know that we recover edits silently!
+
+I guess we should at least show a fade away notice when we recover the edits thus letting the user know about the feature.",1520963133,PHID-USER-yjl5dukrpd7aq6u3c4h4,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4046224, @Esanders wrote:
+> Perhaps a middle ground would be to prompt the user only if the document IDs don't match. In the common case where the document IDs do match we continue to recover silently, and if the user wants to undo they can press undo (as history is preserved),
+
+This seems like a good idea to me.",1520948641,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Note that one of the use cases for this is for when mobile devices automatically unload background tabs, so having the editor prompt you to recover every time you switch tabs could be annoying.
+
+Perhaps a middle ground would be to prompt the user only if the document IDs don't match. In the common case where the document IDs do match we continue to recover silently, and if the user wants to undo they can press undo (as history is preserved),",1520941633,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"An edit is considered intentionally abandoned if you click 'Read' or 'Article' (T189380 not yet deployed). If you close the tab, reload or navigate away in any other way we have no opportunity to delete. It would not be correct to only recover if the version IDs match, as on popular articles that will happen all the time. We should expect core's merge/conflict code to handle that in the same way it would if you just had the tab open for a long time.
+
+Given that people are getting confused about when they have actually ""abandoned"" their edit, we may want to ask the user.",1520940579,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I filed {T189576}
+
+In the mean time, my testing unearthed two workarounds you can use so that your edits are not ""recovered"" when they shouldn't be:
+# Close the tab you were using, and edit the same page in a new tab.
+# Click ""Read"" to close the editor.",1520940504,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4044693, @kaldari wrote:
+> @Deskana: Do you think we should make a follow-up task to implement James's UI to deal with TheDJs issue (T57370#4037827)?
+
+I'd prefer the software do the right thing (i.e. not ""recovering"" edits that were intentionally abandoned) rather than shifting the burden of the decision onto the user. If that's not possible for whatever technical reason, asking the user would be an acceptable backup option.",1520938797,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I experienced a similar issue recently when I was testing something else. I made a few changes in the 2017 wikitext editor, abandoned my edit, and when I came back to the page my edit was ""recovered"" which wasn't helpful. I'll file a task for this.",1520938703,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037827, @TheDJ wrote:
+> I just encountered this for the first time and it's already blocking me...
+> 
+> I started writing a reply to a user with a section edit (WE 2017). Then I aborted this (Intentionally because there was a severe edit conflict because I went away for an hour or so before trying to submit). Then I went back to the same section of the new version and my change was recovered, but this caused it to reinsert the very old document. Now I don't know how to get the auto save to ignore my outdated session, so that I can properly comment on the current version of the page .....
+> 
+> Can we decide not to restore if the base revisions of the document are not the same ? Or create some way for me to be in control somehow ?
+
+I encountered the same problem when trying to recover from T189079. It definitely seems like it needs to be addressed.",1520926435,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037827, @TheDJ wrote:
+> I just encountered this for the first time and it's already blocking me...
+> 
+> I started writing a reply to a user with a section edit (WE 2017). Then I aborted this (Intentionally because there was a severe edit conflict because I went away for an hour or so before trying to submit). Then I went back to the same section of the new version and my change was recovered, but this caused it to reinsert the very old document. Now I don't know how to get the auto save to ignore my outdated session, so that I can properly comment on the current version of the page .....
+> 
+> Can we decide not to restore if the base revisions of the document are not the same ? Or create some way for me to be in control somehow ?
+
+I encountered this as well when trying to recover from T189079. It definitely seems like it needs to be addressed.",1520926420,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,@Deskana: Do you think we should make a follow-up task to implement James's UI to deal with TheDJs issue (T57370#4037827)?,1520886541,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I was under the impression it was going to be optional to restore your edit, like in James's mockup: T57370#2548772.",1520886400,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Also, I note I had predicted and summarised some of such edge cases and considerations as recently as January in related tickets... T184308#3889701 Might be worthwhile to take a quick look at that.",1520596551,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I just encountered this for the first time and it's already blocking me...
+
+I started writing a reply to a user with a section edit (WE 2017). Then I aborted this (Intentionally because there was a severe edit conflict because I went away for an hour or so before trying to submit). Then I went back to the same section of the new version and my change was recovered, but this caused it to reinsert the very old document. Now I don't know how to get the auto save to ignore my outdated session, so that I can properly comment on the current version of the page .....
+
+Can we decide not to restore if the base revisions of the document are not the same ? Or create some way for me to be in control somehow ?",1520596351,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I just encountered this for the first time and it's already blocking me...
+
+I started writing a reply to a user with a section edit (WE 2017). Then I aborted this (Intentionally because there was a severe edit conflict because I went away for an hour or so before trying to submit). Then I went back to the same section of the new version and I my change was recovered, but this causes it to reinsert the very old document. Now I don't know how to get the auto save to ignore my outdated session, so that I can properly comment on the current version of the page .....
+
+Can we decide not to restore of the base revisions of the document are not the same ? Or create some way for me to be in control somehow ?",1520596004,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037783, @Deskana wrote:
+>>>! In T57370#4037595, @TheDJ wrote:
+> To my knowledge, there aren't any cookies used for this, so I don't think so.
+
+That's an old policy, but it's about ALL client side storage: ""These generally include tracking pixels, JavaScript, and a variety of ""locally stored data"" technologies, such as cookies and local storage.""",1520596029,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037783, @Deskana wrote:
+>>>! In T57370#4037595, @TheDJ wrote:
+> To my knowledge, there aren't any cookies used for this, so I don't think so.
+
+That's an old policy, but it's about ALL client side storage. ""These generally include tracking pixels, JavaScript, and a variety of ""locally stored data"" technologies, such as cookies and local storage.""",1520596013,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037783, @Deskana wrote:
+>>>! In T57370#4037595, @TheDJ wrote:
+> To my knowledge, there aren't any cookies used for this, so I don't think so.
+
+That's an old policy, but it's about ALL client side storage.",1520595703,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#4037595, @TheDJ wrote:
+> * Session storage doesn't protect against full-on browser crashes I presume ?
+
+I induced a full browser freeze and crash in Chrome, and my edits were successfully recovered. This may not be true in other, or older, browsers.
+
+> * This might have to be noted / listed in the [[ https://wikimediafoundation.org/wiki/Cookie_statement | cookie policy ]] ?
+
+To my knowledge, there aren't any cookies used for this, so I don't think so.
+
+The other two questions are for engineers, not myself. :-)",1520594625,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I have 4 potential follow up questions/issues
+* I spotted a problem in that patch.. no try/catch around the session storage access (as with local storage usage, always needed).
+* Session storage doesn't protect against full-on browser crashes I presume ?
+* This might have to be noted / listed in the [[ https://wikimediafoundation.org/wiki/Cookie_statement | cookie policy ]] ?
+* We should actively blank this when definitively saving / cancelling. This would prevent the last edit being left in the browser's storage on things like public library computers, which we would like to avoid I think... (also, is there username info in the content being put in session storage ? because that might be a problem in that situation)",1520586054,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I have 4 potential follow up questions/issues
+* I spotted a problem in that patch.. no try/catch around the session storage access (as with local storage, usage always needed).
+* Session storage doesn't protect against full-on browser crashes I presume ?
+* This might have to be noted / listed in the [[ https://wikimediafoundation.org/wiki/Cookie_statement | cookie policy ]] ?
+* We should actively blank this when definitively saving / cancelling. This would prevent the last edit being left in the browser's storage on things like public library computers, which we would like to avoid I think... (also, is there username info in the content being put in session storage ? because that might be a problem in that situation)",1520586025,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Yeah. There may be bugs or follow-up work, but that can be in different tasks.",1520342434,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,Resolved?,1520330938,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413273 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Use session storage to auto-save
+
+[[https://gerrit.wikimedia.org/r/413273]]",1519762832,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,Note: the above patches are not intended to be a long-term saving mechanism.,1519321185,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413266 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (1a0bc9981)
+
+[[https://gerrit.wikimedia.org/r/413266]]",1519259492,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413273 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Use session storage to auto-save
+
+[[https://gerrit.wikimedia.org/r/413273]]",1519254050,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413266 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (1a0bc9981)
+
+[[https://gerrit.wikimedia.org/r/413266]]",1519251448,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413249 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] Use sessionStorage to auto-save
+
+[[https://gerrit.wikimedia.org/r/413249]]",1519249530,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Change 413249 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] Use sessionStorage to auto-save
+
+[[https://gerrit.wikimedia.org/r/413249]]",1519247754,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3924115, @cscott wrote:
+> This would be a good use of a general ""fork storage"" mechanism: the edit-in-progress would get stored as an unmerged fork of the main revision.
+
+Cool idea. But what if there is no main revision (creating a new page)?",1516952029,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"This would be a good use of a general ""fork storage"" mechanism: the edit-in-progress would get stored as an unmerged fork of the main revision.",1516949735,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,Proposed to #community-wishlist-survey-2017 ,1511107173,PHID-USER-lz5f7t47np7ftbnhn6i5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3601942, @Esanders wrote:
+> 
+> do our own memory management
+
+...or use someone else's, e.g. https://github.com/monsur/jscache",1505246413,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3416020, @Jdforrester-WMF wrote:
+> silently fail when the user's machine either has local storage disabled or is full?
+
+Well given we will be writing to LocalStorage every time a new edit session is started, this is going to happen often (and we can't rely on the edit session being closed 'gracefully'). It appears that most browsers will throw an exception when storage is exceeded, so if we do our own memory management and keep track of VE save sessions, we can prune the LRU session until their is enough free space. We can also prune sessions older than N minutes/hours so other users can still use LocalStorage (e.g. ResourceLoader).",1505246172,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I am sorry, I wanted to close and merge the other way. I try to fix it.",1505073579,PHID-USER-lz5f7t47np7ftbnhn6i5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,(wrong tab),1502377152,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Whatamidoing-WMF
+I am admittedly stretching the limits of what I know about javascript, but it appears something like
+```
+textarea.on('input', ...
+```
+solves that issue. I'm unsure, but a little extra code may be needed to catch cut/paste via right click.",1501945495,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Whatamidoing-WMF
+I am admittedly stretching the limits of what I know about javascript, but it appears something like
+```
+textarea.on('input', ...
+```
+does exactly that. I'm unsure, but a little extra code may be needed to catch cut/paste via right click.",1501945421,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Alsee, the 2010 WikiEditor doesn't know whether or not you've typed anything in the editing window yet, and therefore it cannot know whether there are any changes to be saved.
+",1501782134,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490603, @Whatamidoing-WMF wrote:
+> Because it isn't actually possible in the older wikitext editors.  
+
+My apologies, but I have to question your technical expertise on that point. I find it very difficult to imagine any reason that data-storing javascript could be added to one editor, but couldn't be added to the other.
+
+The community [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | requested this feature]]. Nearly two-thirds of the people supporting the request use VE for **zero percent** of their edits. They were quite obviously requesting this feature for the only editor that they use. 85% of supporters use Visual for 8% or less of their edits. They were also quite obviously requesting this feature for substantially-the-only-editor they use. Exactly one person uses Visual for more than half of their edits (57.6%). I'm sure no one objects to implementing autosave in the secondary editor as well.
+
+There is already a task open for this request: T75241
+
+Unless there is some clear reason not to do so, this task should be merged into  T75241 as a duplicate.
+If there is a desire for separate tasks for the two editors, the first priority work should be on the primary editor. I guess that would make this a subtask of T75241. 
+",1501748363,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490603, @Whatamidoing-WMF wrote:
+> Because it isn't actually possible in the older wikitext editors.  
+
+My apologies, but I have to question your technical expertise on that point. I find it very difficult to imagine any reason that data-storing javascript could be added to one editor, but couldn't be added to the other.
+
+The community [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | requested this feature]]. Nearly two-thirds of the people supporting the request use VE for **zero percent** of their edits. They were quite obviously requesting this feature for the only editor that they use. 85% of supporters use Visual for 8% or less of their edits. They were also quite obviously requesting this feature for substantially-the-only-editor they use. Exactly one person uses Visual for more than half of their edits (57.6%). I'm sure no one objects to implementing autosave in the secondary editor as well.
+
+There is already a task open for this request: T75241
+
+Unless there is some clear reason not to do so, this task should be merged into  T75241 as a duplicate.
+If there is a desire for separate tasks for the two editors, **the first priority work should be on the primary editor**. I guess that would make this a subtask of T75241. 
+",1501747894,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490603, @Whatamidoing-WMF wrote:
+> Because it isn't actually possible in the older wikitext editors.  
+
+My apologies, but I have to question your technical expertise on that point. I find it very difficult to imagine any reason that data-storing javascript could be added to one editor, but couldn't be added to the other.
+
+The community [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | requested this feature]]. Nearly two-thirds of the people supporting the request use VE for **zero percent** of their edits. They were quite obviously requesting this feature for the only editor that they use. 85% of supporters use Visual for 8% or less of their edits. They were also quite obviously requesting this feature for substantially-the-only-editor they use. Exactly one person uses Visual for more than half of their edits (57.6%). I'm sure no one objects to implementing autosave in the secondary editor as well.
+
+There is already a task open for this request: T75241
+
+Unless there is some clear reason not to do so, this task should be merged into  T75241 as a duplicate.
+If there is a desire for separate tasks for the two editors, **the first priority work should be on the primary editor**.
+",1501747785,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490603, @Whatamidoing-WMF wrote:
+> Because it isn't actually possible in the older wikitext editors.  
+
+My apologies, but I have to question your technical expertise on that point. I find it very difficult to imagine any reason that data-storing javascript could be added to one editor, but couldn't be added to the other.
+
+The community [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | requested this feature]]. Nearly two-thirds of the people supporting the request use VE for **zero percent** of their edits. They were quite obviously requesting this feature for the only editor that they use. 85% of supporters use Visual for 8% or less of their edits. They were also quite obviously requesting this feature for substantially-the-only-editor they use. And I'm sure no one objects to implementing it in the secondary editor as well.
+
+There is already a task open for this request: T75241
+
+Unless there is some clear reason not to do so, this task should be merged into  T75241 as a duplicate.
+If there is a desire for separate tasks for the two editors, **the first priority work should be on the primary editor**.
+",1501747091,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3490428, @Alsee wrote:
+> Why is this described as a Visual Editor task? Visual Editor is a minor secondary editor, only used for a small percentage of edits. If auto save is implemented, it's certainly reasonable to also implement it in the secondary editor as well (VE).
+
+Because it isn't actually possible in the older wikitext editors.  
+
+Most modern browsers can preserve text within the older wikitext editors (e.g., if you accidentally click the 'back' button while you're editing, then your changes are usually there if you click the 'forward' button to go back to the editing window), but that they can't do this with VisualEditor (either mode).  So, in effect, the team is planning to cover for a limitation in browsers by building this capability internally.  If you are interested in this subject, then you may want to read about HTML textareas (used in the older wikitext editors) and ContentEditable (used in online rich-text editors, including VisualEditor).
+",1501616413,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Why is this described as a Visual Editor task? Visual Editor is a minor secondary editor, only used for a small percentage of edits. If auto save is implemented, it's certainly reasonable to also implement it in the secondary editor as well (VE).",1501614519,PHID-USER-o7sy7j32bv4qerbqa3x5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#3415924, @Esanders wrote:
+>>>! In T57370#2976776, @Esanders wrote:
+>> The main concern is what happens when we run out of storage.
+> 
+> The workaround for local storage limitations is remote storage, with the downsides:
+> * slower (potentially several seconds for long articles and slow connections, but it's background and async so meh)
+> * doesn't work offline, obviously
+> * infrastructure costs of storing all the extra data
+> * would probably need user consent
+
+The trump concern is legal issues arising from holding server-side information subject to expensive discovery mechanisms, as I understand it (I'm not a lawyer, //etc.// //etc.//).
+
+How about we just go ahead with this as-is, persisting last-edit-state so restarting browsers get back to the state before the crash/whatever, and silently fail when the user's machine either has local storage disabled or is full?",1499447076,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#2976776, @Esanders wrote:
+> The main concern is what happens when we run out of storage.
+
+The workaround for local storage limitations is remote storage, with the downsides:
+* slower (potentially several seconds for long articles and slow connections, but it's background and async so meh)
+* doesn't work offline, obviously
+* infrastructure costs of storing all the extra data
+* would probably need user consent
+",1499444341,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Also the caveat for txs is that we need access to the original document state. That is fine for regular MW edits, but if they're using a restbase stash after switching that may be a problem. In those cases we could either store initial HTML or disable auto-save.",1485534255,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Also the caveat for txs is that we need access to the original document state. That is fine for regular MW edits, but if they're using a restbase stash after switching that may be a problem (although we could just disable auto-save :/ )",1485534114,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Twice HTML => maybe 3.4MiB for Obama => two unsaved edits and we've over-flowed Firefox's local storage, that sucks quite a bit, which would steer us to Transactions. OTOH, the growth characteristics of Transactions for long edits (the ones where this would be particularly useful) make me a little uncomfortable about whether it'd be better….",1485533621,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"The main concern is what happens when we run out of storage. A single document is unlikely to do this, but with multiple documents saved this would be quite common. We would need to do our own memory management to throw away old stashes.",1485533477,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"| | **Transactions** | **HTML** | **Entire linear model** |
+| **Initial storage** | None. With the caveat that we will have access to the initial document state the user saw at a later date. Could be problematic if user has switched from WT mode. Could instead use HTML storage for initial state, then transactions for changes, but wipes out storage advantage. | proportional to article size (~1.7MB for Obama) | About twice HTML |
+| **Incremental storage** | ~400 bytes to type a single character. Typing a 200 word / 3 sentence paragraph with a few annotations took 60k. | Not much more than a few bytes per character | About twice HTML |
+| **Storage edge cases** | Blanking whole document / pasting in large sections multiple times will results in really large transactions, more that the initial storage of ‘Entire linear model’ | None really, just the document length. | << |
+| **Undo stack** | Preserved | Not preserved | << |
+| **Save performance** | Very fast, small JSON.stringify | Can be a few hundred ms for long articles. If waiting for N seconds of user inactivity this may not be a big issue, but in some cases esp slow machines, edit area will become momentarily non-responsive. | Fairly fast, large JSON.stringify |",1485533164,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,">>! In T57370#2558298, @Ltrlg wrote:
+> @Jdforrester-WMF I have been working on a Confluence wiki with (server-side) auto-save for several months and they have something your current proposal do not include: being able to see a diff before choosing. It is really useful, because I often do not remember what I was doing exactly when I closed the editing page 2 or 3 days before editing again.
+
+Hmm. That's certainly a possibility, but I don't think it's a good idea to try to shoe-horn that into the first version. In particular, I'd rather we had (at least) designs for {T105173} (so that users didn't have to know wikitext to understand what they're shown) and possibly {T39931} as a better, more fluid way of showing that to users as they edit. I've created {T143341} for this idea.",1471542901,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"@Jdforrester-WMF I have been working on a Confluence wiki with (server-side) auto-save for several months and they have something your current proposal do not include: being able to see a diff before choosing. It is really useful, because I often do not remember what I was doing exactly when I closed the editing page 2 or 3 days before editing again.",1471375443,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,Hopefully,1471148521,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"I lost some work recently when I accidentally closed the wrong tab.  Will your current plan solve that problem?
+",1471098931,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"OK, so, dusting this off, my current proposal is as follows:
+
+* As you edit, we stash a copy of the edited document whilst you're editing it into indexDB or whatever (locally on your machine); this would apply both to VE and the NWE surfaces.
+* When you save, once we get confirmation back that it's saved we delete from the local machine the in-process edit.
+* On load, if there's a draft for this page which based off the current revision, we prompt you to either resume the edit, or start a fresh edit (and discard the draft), with something looking roughly like:
+{F4357662}
+
+This means that //e.g.// if your computer crashes, you lose network/power, or whatever, you can resume edits. It's optional, so if somehow you've made an edit that causes the editor to crash you can avoid re-triggering it (so you're not caught in a loop).
+
+The main downside is that it doesn't let you move computers during an edit (which is not a common issue for users right now, but is a bit of an 'oh well').
+
+If you load and there's a partial edit based on an out-of-date revision it probably isn't possible for us to help out automatically — we can't do an edit merge at that point, as that's a DB/server-side operation, and we can't tell whether or not the edit will save cleanly. Maybe just discard it silently?",1471030276,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,See also: Wikitext editor patch for this: https://gerrit.wikimedia.org/r/#/c/5130/,1397680537,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,*** Bug 52988 has been marked as a duplicate of this bug. ***,1383280899,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"If local storage is going to be seriously considered, with pages being auto-saved, some issues to consider:
+
+How many open VE's can be autosaved?  Only saving one VE session makes management very simple, but it is probably sufficient for only a small subset of the editing community.
+
+The local storage limit of 5 MB in most user agents is going to be a problem.  Also VE needs to intelligently handle the case where the offline storage is not available or the origin has exceeded its limit.  The user needs to know when their session isnt being auto-saved due to client side factors.
+
+Are these autosaved versions going to persist across browser sessions?
+
+If the VE sessions do persist, how will VE determine which VE autosaved versions are no longer needed and can be deleted to allow more VE sessions to be autosaved in the future.  Will the user be able to manage which autosaves they no longer need?",1381283422,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"(In reply to comment #1)
+> Why not deploy the drafts extension, and add any VE support needed?
+
+Have commented there explaining.",1381267333,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"(In reply to comment #1)
+> Why not deploy the drafts extension, and add any VE support needed?
+
+[[mw:Extension:Drafts]], for those unfamiliar.",1381102292,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing,"Why not deploy the drafts extension, and add any VE support needed?",1381101467,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-wqlj6yxiyvemo7hpj3z4,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Hi
+When I run parsoid linked to a wiki which is https only, it doesn't work. This can be reproduced in any installation.
+
+I set port 80 to be a redirect to port 443, and the parsoid URL is https://wiki.name/api.php in localsettings.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381073520,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-xya74ryevlevdpyqmth6,task_description,resolved
+Parsoid cannot connect to https-only host?,"Shall we close this? I know that VE functions happily on wikitech.wikimedia.org now, which always uses HTTPS.",1428265426,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I wanted to update this bug with my findings. I now have 1.23wmf7 and the latest builds of Parsoid and VisualEditor working happily with SSL as the default (and forced) connection method for users.
+
+In my LocalSettings.php I have the following:
+
+//Hook it up to Parsoid
+$wgVisualEditorParsoidURL = 'http://my.site.com:8000';
+ 
+$wgVisualEditorParsoidPrefix = 'localhost';
+
+
+In localsettings.js I have:
+
+parsoidConfig.setInterwiki('localhost' , 'http://my.site.com:81/w/api.php');
+
+You can see that we're directing traffic over port 81 to allow Parsoid access.
+
+The issue I was experiencing related to saving a page was due to having an older version (pre 1.9) of Semantic MediaWiki installed with 1.23.",1388082421,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I've followed the troubleshooting guide and I'm still having issues connecting to a https-only host.
+
+From the server I can run the following with success:
+
+curl http://my.site.com:81/w/api.php
+
+I opened port 81 to allow for http access to the api endpoint.
+
+However I cannot seem to connect to Parsoid, the app in question. 
+
+curl http://my.site.com:8000 returns the human-readable landing page for the Parsoid web service.
+
+curl http://my.site.com:8000/localhost/Introduction
+
+returns no message via the command line.
+
+I can start Parsoid via node server.js
+
+I can launch VisualEditor and edit a page normally, everything works.
+
+server.js spits out the following:
+
+starting parsing of localhost:Introduction
+completed parsing of localhost:Introduction in 1660 ms
+
+As soon as I go to save an edit, a small note appears under the Summary box.
+
+Error: Unknown error.
+
+server.js reports nothing
+
+
+While Parsoid is running (node server.js) and I attempt the following
+
+curl http://my.site.com:8000/localhost/Introduction
+
+I see the message:
+
+starting parsing of localhost:Introduction
+redirected localhost:Introduction to revision 62067",1387213772,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I know it works, it's a workaround. I am hosting the site in a CentOS server, but despite the research I have done some time ago I couldn't install the certificate in the system root, so neither PHP and node.js see the certificate. 
+
+I will try again now. Is there any documentation you know about this? (sorry if it's off-topic)",1386278143,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"(In reply to comment #8)
+> I am sorry, I can't pay for a real certificate. Is there a way to add my root
+> certificate to Parsoid? Does it use the system certificates?
+> 
+> Or as a workaround, is there a way to permit self-signed authorities?
+
+Your wiki actually works by setting the API URL to http://wiki.mc128k.info/api.php.
+
+Nodejs uses openssl, so I'm guessing that you can install additional CA certs in /etc/ssl/certs/ (assuming you are using Debian).",1386277852,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I am sorry, I can't pay for a real certificate. Is there a way to add my root certificate to Parsoid? Does it use the system certificates?
+
+Or as a workaround, is there a way to permit self-signed authorities?
+
+Thanks.",1386273347,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Parsoid is only using HTTP, so trying to connect to it via HTTPS is going to fail. It can connect to MediaWiki using HTTPS though when configured to do so in localsetting.js. Please check the steps in https://www.mediawiki.org/wiki/Parsoid/Troubleshooting to make sure Parsoid is working.
+
+> https://wiki.mc128k.info
+
+Your SSL cert does not seem to be signed by a trusted CA, which likely explains your issue. Try with a signed SSL cert.",1386270337,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Addition:
+Changing $wgVisualEditorParsoidURL to 'https://my.wiki.com:8000'; results in a different error.
+
+Error loading data from server: parsoidserver-http-curl-error: SSL connect error. Would you like to retry?
+
+
+Headers below:
+
+Start request POST /w/api.php
+HTTP HEADERS:
+HOST: my.wiki.com
+CONNECTION: keep-alive
+CONTENT-LENGTH: 60
+AUTHORIZATION: Basic bWVtY2FjadGU6cGFzc3dvcmQ=
+ACCEPT: application/json, text/javascript, */*; q=0.01
+ORIGIN: https://my.wiki.com
+X-REQUESTED-WITH: XMLHttpRequest
+USER-AGENT: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36
+CONTENT-TYPE: application/x-www-form-urlencoded; charset=UTF-8
+REFERER: https://my.wiki.com/w/index.php?title=Main_Page&veaction=edit
+ACCEPT-ENCODING: gzip,deflate,sdch
+ACCEPT-LANGUAGE: en-US,en;q=0.8
+COOKIE: infoLoggedOut=1386191878; __utma=198203634.1203293077.1386191715.1386191715.1386191715.1; __utmc=198203634; __utmz=198203634.1386191715.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); infoUserID=378; infoUserName=Clkoerne; info_session=4f15c368d4244cc2b9e72e06f65adc12; wikiEditor-0-booklet-characters-page=latin; wikiEditor-0-toolbar-section=advanced; vector-nav-p-Repository=true; vector-nav-p-tb=true
+CACHES: MemcachedPhpBagOStuff[main] MemcachedPhpBagOStuff[message] MemcachedPhpBagOStuff[parser]
+[cookie] session_set_cookie_params: ""0"", ""/"", """", ""1"", ""1""
+LocalisationCache: using store LCStoreDB
+Unstubbing $sfgFormPrinter on call of $sfgFormPrinter::setInputTypeHook from SFSelect_formSetup
+Unstubbing $wgParser on call of $wgParser::setHook from ExtDynamicPageList::setupDPL
+Parser: using preprocessor: Preprocessor_DOM
+Connected to database 0 at lnxvmiptdbt01
+Class UniversalLanguageSelectorHooks not found; skipped loading
+Fully initialised
+User: got user 378 from cache
+User: loading options for user 378 from override cache.
+User: logged in from session
+ApiMain::setCacheMode: setting cache mode private
+IP: 10.29.122.24",1386269909,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I am experincing the same bug.
+
+Attempting to evoke VisualEditor to edit any pages where we have redirected all traffic to https results in the error.
+
+
+In the browser:
+Error loading data from server:parsoidserver-hhtp-curl-error:
+Empty reply from server. Would you like to retry?
+
+
+Parsoid displays the following upon each attempt to edit a page (in this case Main Page):
+
+ERROR in localhost:Main_Page
+Stack trace: DoesNotExistError: Page Fetch failure for null
+worker 20040 died, restarting.
+
+
+MediaWiki logs show the following for the request:
+
+Start request POST /w/api.php
+HTTP HEADERS:
+HOST: my.wiki.com
+CONNECTION: keep-alive
+CONTENT-LENGTH: 60
+ACCEPT: application/json, text/javascript, */*; q=0.01
+ORIGIN: https://my.wiki.com
+X-REQUESTED-WITH: XMLHttpRequest
+USER-AGENT: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
+CONTENT-TYPE: application/x-www-form-urlencoded; charset=UTF-8
+REFERER: https://my.wiki.com/wiki/Main_Page?veaction=edit
+ACCEPT-ENCODING: gzip,deflate,sdch
+ACCEPT-LANGUAGE: en-US,en;q=0.8
+COOKIE: __utma=198203634.575160840.1386267474.1386267474.1386267474.1; __utmb=198203634.2.10.1386267474; __utmc=198203634; __utmz=198203634.1386267474.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); infoUserID=378; infoUserName=Clkoerne; info_session=7200a1cbfcef48ded410afb07850a6fc
+CACHES: MemcachedPhpBagOStuff[main] MemcachedPhpBagOStuff[message] MemcachedPhpBagOStuff[parser]
+[cookie] session_set_cookie_params: ""0"", ""/"", """", ""1"", ""1""
+LocalisationCache: using store LCStoreDB
+Unstubbing $sfgFormPrinter on call of $sfgFormPrinter::setInputTypeHook from SFSelect_formSetup
+Unstubbing $wgParser on call of $wgParser::setHook from ExtDynamicPageList::setupDPL
+Parser: using preprocessor: Preprocessor_DOM
+Connected to database 0 at lnxvmipdbt01
+Class UniversalLanguageSelectorHooks not found; skipped loading
+Fully initialised
+User: got user 378 from cache
+User: loading options for user 378 from override cache.
+User: logged in from session
+ApiMain::setCacheMode: setting cache mode private
+IP: 10.9.191.150",1386269124,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Debug log from parsoid:
+ - worker(23680) ready
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 4 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 3 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 2 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 1 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+Retrying Page Fetch request for null, 0 remaining
+{
+  ""0"": ""WARNING: RETRY:"",
+  ""1"": {}
+}
+ERROR in localhost:Main_Page:
+Page Fetch failure for null
+Stack trace: DoesNotExistError: Page Fetch failure for null
+worker 23671 died (1), restarting.
+ - worker(23690) loading...
+ - worker(23690) ready
+
+
+I don't know if the API works from the external network, this is a protected wiki, I hope login won't be necessary.
+
+https://wiki.mc128k.info",1386145344,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I just tested this with 'enwiki' and
+
+parsoidConfig.setInterwiki( 'enwiki', 'https://en.wikipedia.org/w/api.php' );
+
+We don't set the port explicitly and use the API uri as-is, so in theory https-only APIs should work. Do you have a public https-only API URI we can test with?",1386118696,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"I'm sorry, I thought Parsoid was part of VisualEditor. Corrected. Thanks.
+Latest git versions, of parsoid, mediawiki, visualeditor.",1381092220,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+Parsoid cannot connect to https-only host?,"Hmm, shouldn't this be filed under product ""Parsoid""? :)
+Which Parsoid version and which MediaWiki version is this about?",1381092082,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xya74ryevlevdpyqmth6,task_subcomment,NA
+VisualEditor: Link tooltip is not updated if link inspector is not explicitly closed,"Germanjoe reports:
+""A small (very small) bug: mouse display of links doesn't get actualized, when the editor leaves the small edit dialog to change links without pressing the ""<"" button (just by clicking somewhere else in the text the edit dialog closes aswell). 
+
+Example: change German to ""German language|German"" in some test article and leave the link editor without pressing ""<"". The mouse display should show ""German language"" as internal link info, but still shows ""German"". However, ""German language|German"" is correctly saved to the source text (just the display is wrong).""
+
+Further testing shows that this can be demonstrated multiple ways. In all cases close the link input widget by clicking elsewhere on the editing surface, do not click < (that works as expected)
+
+*Change ""[[German]]"" to ""[[German language|German]]"". Tooltip is ""German"" (expected ""German language)
+*Change ""[[Welsh language]]"" to ""[[Welsh language literature|Welsh language]]"". Tooltip is ""Welsh language"" (expected ""Welsh language literatue"")
+*Change ""French"" to ""[[French language|French]]"". Tooltip is ""French"" (expected ""French language"")
+*Change ""Portuguese"" to ""[[Brazillian|Portuguese]]"". Tooltip is ""Portuguese"" (expected ""Brazillian"")
+*Change ""Polish language"" to ""[[Polish Language Council|Polish language]]"". Tooltip is ""Polish language"" (expected ""Polish Language Council"")
+
+The tooltip is corrected as soon as one of the following actions happens:
+*The link input widget is opened on that link again. Even if no changes are made and it is closed by clicking elsewhere.
+*The link display text is amended on the editing surface, e.g. ""[[Polish Language Council|Polish language]]"" → ""[[Polish Language Council|Polish informal language]]""
+*Text is typed adjacent to either end of a link, e.g. [[Italian]] → [[Italian]]s
+*Annotation is applied to the display text.
+
+I've marked the severity as ""trivial"" because in all cases the correct target is displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1380909000,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-cefkpaw5jsqxys54667r,task_description,resolved
+VisualEditor: Link tooltip is not updated if link inspector is not explicitly closed,This has now been fixed.,1402549108,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cefkpaw5jsqxys54667r,task_subcomment,NA
+VisualEditor: Spellcheck freaks out in Firefox when focusable nodes are focused,"* Open a document in a language that is not your default language,
+  for example:
+  https://fr.wikipedia.org/wiki/Cumul_des_mandats_en_France?veaction=edit
+  (if you're not French).
+* Assuming your browser does have a French dictionary, the article should
+  have few to 0 red-underlined words.
+* Click on a [1] reference.
+* Observe suddenly almost every word is spellcheck invalidated by red lines
+* Moving the cursor by keyboard arrows still keeps them invalid.
+* As soon as you actually use the mouse to click for a cursor move, that is
+  when it switches back to the correct language (or perhaps it disables
+  spellcheck)
+
+Not sure, but I think this is a regression.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380896700,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mpgdokvlglkvrsqagxhx,task_description,resolved
+VisualEditor: Spellcheck freaks out in Firefox when focusable nodes are focused,Can't reproduce this issue anymore.,1530906787,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-mpgdokvlglkvrsqagxhx,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","I simply deleted a word from the leading paragraph in the article below, and got this as diff:
+https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%3ANurick%2F%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_-_%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99&diff=14670508&oldid=14667916
+
+To reproduce: Revert to the previous version in that diff, edit the article in VE, and delete a word from the leading paragraph.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380822960,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_description,resolved
+"Parsoid renders template as comment, breaking serialization",*** Bug 56722 has been marked as a duplicate of this bug. ***,1383851745,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","Change 90687 merged by jenkins-bot:
+Match all characters when testing comments for JSON
+
+https://gerrit.wikimedia.org/r/90687",1382551909,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","Change 90687 had a related patch set uploaded by Arlolra:
+Match all characters when testing comments for JSON
+
+https://gerrit.wikimedia.org/r/90687",1382152168,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","On second thought, I think it's because `.` doesn't match newline chars.",1382152030,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","The problem here is that the contents of that comment isn't matching this regex,
+
+  /^\{.*\}$/.test( content )
+
+https://github.com/wikimedia/mediawiki-extensions-Parsoid/blob/master/js/lib/mediawiki.DOMPostProcessor.js#L95
+
+It's not recognizing the last character as }. Taking content.charCodeAt( content.length - 1 ) returns undefined. Probably because of the unicode characters. Switching to something like,
+
+  /^\{\""@type\""/.test( content )
+
+seems to work but I'm interested to see where exactly things are going wrong.",1382149987,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+"Parsoid renders template as comment, breaking serialization","This is due to a Parsoid bug.
+
+Example that Moriel gave me: http://parsoid.wmflabs.org/he/%D7%93%D7%A0%D7%99%D7%90%D7%9C_%D7%A8%D7%93%D7%A7%D7%9C%D7%99%D7%A3
+
+HTML starts with:
+
+<html><head>...</head><body>
+<!--{""@type"":""mw:Transclusion"",""attrs"":[{""name"":""typeof"",""value"":""mw:Transclusion""},{""name"":""about"",""value"":""#mwt1""},{""name"":""id"",""value"":""mwt1""},{""name"":""data-mw-arginfo"",""value"":""{\""dict\"":{\""target\"":{\""wt\"":\""שחקנים
\\n\"",\""href\"":\""./תבנית:שחקנים\""},\""params\"":{\""שם\"":{\""wt\"":\""דניאל רדקליף\""},\""תמונה\"":{\""wt\"":\""[[קובץ:Daniel Radcliffe Paris 2012.jpg|200px]]\""},\""כיתוב\"":{\""wt\"":\""<small> דניאל רדקליף, [[2012]]</small>\""},\""תאריך לידה\"":{\""wt\"":\""23 ביולי 1989\""},\""מקום לידה\"":{\""wt\"":\""[[לונדון]], [[אנגליה]], [[הממלכה המאוחדת]]\""},\""כינוי\"":{\""wt\"":\""דן\""},\""דמות\"":{\""wt\"":\""[[הארי פוטר (דמות)|הארי פוטר]]\""},\""בכורה\"":{\""wt\"":\""בסדרה [[דייוויד קופרפילד]], 1999\""},\""אתר אינטרנט\"":{\""wt\"":\""http://www.danradcliffe.co.uk/\""},\""קישור\"":{\""wt\"":\""0705356\""}}},\""paramInfos\"":[{\""k\"":\""שם\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""
\\n\""]},{\""k\"":\""תמונה\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""כיתוב\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""תאריך לידה\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""מקום לידה\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""כינוי\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""דמות\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""בכורה\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""אתר אינטרנט\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]},{\""k\"":\""קישור\"",\""named\"":true,\""spc\"":[\""\"",\""\"",\""\"",\""\\n\""]}]}""},{""name"":""data-parsoid"",""value"":""{\""tsr\"":[0,356],\""src\"":\""{{שחקנים
\\n|שם=דניאל רדקליף
\\n|תמונה=[[קובץ:Daniel Radcliffe Paris 2012.jpg|200px]]\\n|כיתוב=<small> דניאל רדקליף, [[2012]]</small>\\n|תאריך לידה=23 ביולי 1989\\n|מקום לידה=[[לונדון]], [[אנגליה]], [[הממלכה המאוחדת]]\\n|כינוי=דן\\n|דמות=[[הארי פוטר (דמות)|הארי פוטר]]\\n|בכורה=בסדרה [[דייוויד קופרפילד]], 1999\\n|אתר אינטרנט=http://www.danradcliffe.co.uk/\\n|קישור=0705356\\n}}\"",\""tagId\"":1}""}]}-->
+<table class=""infobox"" style=""width:18em; font-size:85%;"" cellspacing=""5"" about=""#mwt1"" data-parsoid=""{}"">[....]</table>
+<meta typeof=""mw:Transclusion/End"" about=""#mwt1"" data-parsoid=""{&quot;dsr&quot;:[null,356,null,null]}"">
+
+Note how:
+* The transclusion starts with a comment (!) which tries to be in the #mwt1 about group
+* The transclusion continues with a table in that same about group
+* The about group ends with a meta tag in that same about group
+
+This doesn't serialize cleanly at all, the template gets inserted into the wikitext and the table gets serialized as wikitext as well. Even the <meta> tag gets serialized: http://parsoid.wmflabs.org/_rt/he/%D7%93%D7%A0%D7%99%D7%90%D7%9C_%D7%A8%D7%93%D7%A7%D7%9C%D7%99%D7%A3
+
+In VisualEditor, this causes:
+* corruption on save like in the diff Moriel linked
+* the user to be able to edit inside the infobox, because the comment is ignored and there are no attributes on the <table> telling VE it's part of a template (there's about=""#mwt1"" but that doesn't refer back to a valid about group, so it's interpreted as the start of an about group)",1382031725,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-d75ni2yenyhhlzg2tn2q,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"Repro:
+
+1. Create a new page with wikitext ""[[中文]]"" on zhwiki
+2. VisualEditor-edit this page and type ""s"" at the end
+3. The whole document now looks as if it has a link to ""中文"" with text ""中文s""
+4. Save the page
+5. Resulting wikitext is ""[[中文]]s"", and in rendered HTML (both PHP and Parsoid - bug 41151), ""s"" is not a part of the link text
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380741240,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_description,declined
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,I do not get the reported problem in Firefox 18 (And Chromium 25).,1381273288,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"I downloaded versions 21, 22 and 23 from: https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/21.0/ (etc.)
+
+I didn't get your reported behaviour in any of them. :-(",1380761975,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #7)
+> (In reply to comment #6)
+> > (In reply to comment #4)
+> > > I get:
+> > > 
+> > > <p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation
+> > > ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+> > > 
+> > > … when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+> > > 
+> > > Very odd. :-(
+> > 
+> > Hmm in Firefox 24 it's no longer reproducible here...
+> 
+> If you can reproduce in Firefox 22 again, once it's in the broken state in
+> the
+> ContentEditable surface please place the cursor to the left (up-page of) the
+> link and insert a new line. This should trigger a re-render and cause the
+> shown
+> HTML to be corrected to what it should be?
+
+Unfortunatly I don't know how to get it back now :(
+
+I simply APT updated it. Does any have some hint about downgrading a package?",1380761514,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #6)
+> (In reply to comment #4)
+> > I get:
+> > 
+> > <p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation
+> > ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+> > 
+> > … when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+> > 
+> > Very odd. :-(
+> 
+> Hmm in Firefox 24 it's no longer reproducible here...
+
+If you can reproduce in Firefox 22 again, once it's in the broken state in the ContentEditable surface please place the cursor to the left (up-page of) the link and insert a new line. This should trigger a re-render and cause the shown HTML to be corrected to what it should be?",1380759700,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #4)
+> I get:
+> 
+> <p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation
+> ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+> 
+> … when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+> 
+> Very odd. :-(
+
+Hmm in Firefox 24 it's no longer reproducible here...",1380758934,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #4)
+> I get:
+> 
+> <p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation
+> ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+> 
+> … when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+> 
+> Very odd. :-(
+
+btw I can't reproduce it using Chrome either.",1380757200,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"I get:
+
+<p class=""ve-ce-branchNode"">s<a title=""中文"" class=""ve-ce-LinkAnnotation ve-ce-mwInternalLinkAnnotation"" rel=""mw:WikiLink"" href=""../中文"">中文</a>s</p>
+
+… when using Firefox 24, Chrome 29, and Opera 12.16 (on Mac).
+
+Very odd. :-(",1380756967,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #2)
+> Are you absolutely sure it showed as <a>中文s</a> (because it really
+> shouldn't!)?
+
+Yes - already checked with inspector.
+
+> What browser were you using?
+
+Firefox 22.",1380754494,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"(In reply to comment #0)
+> Repro:
+> 
+> 1. Create a new page with wikitext ""[[中文]]"" on zhwiki
+> 2. VisualEditor-edit this page and type ""s"" at the end
+> 3. The whole document now looks as if it has a link to ""中文"" with text ""中文s""
+> 4. Save the page
+> 5. Resulting wikitext is ""[[中文]]s"", and in rendered HTML (both PHP and
+> Parsoid
+> - bug 41151), ""s"" is not a part of the link text
+
+I can't reproduce that - I got <a>中文</a>s in the edit surface, and it saved as expected:
+
+* https://zh.wikipedia.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox&diff=28804968&oldid=28804967 (for linktrail)
+
+https://zh.wikipedia.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox&diff=28804969&oldid=28804968 (for linkhead)
+
+Are you absolutely sure it showed as <a>中文s</a> (because it really shouldn't!)? What browser were you using?",1380753439,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be,"Linkprefix is also affected - type ""s"" at the beginning instead of the end in the repro above.",1380741412,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-sy5wjdxwr4pa75h3r2tc,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,"See https://fr.wikipedia.org/wiki/Fichier:Bug_%C3%A9diteur_visuel_barre_de_menu_style_de_texte_sur_deux_lignes.png .
+In languages like French and Italian some options in that menu are long (multiple words names like Titre de section) and the last word will appear under the toolbar itself.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380711000,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-xkup4dal7lu2v5on7iek,task_description,resolved
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,*** Bug 50639 has been marked as a duplicate of this bug. ***,1385378243,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,Fixed and will go out next week.,1380837026,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,"Change 87450 merged by jenkins-bot:
+Allow menu tool groups to be wider if needed
+
+https://gerrit.wikimedia.org/r/87450",1380836998,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,"Change 87450 had a related patch set uploaded by Trevor Parscal:
+Allow menu tool groups to be wider if needed
+
+https://gerrit.wikimedia.org/r/87450",1380835506,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines,"It happens with Firefox/Chrome, Monobook/Vector, and the zoom used in the page does not matter.",1380711110,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-xkup4dal7lu2v5on7iek,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","Best seen on a slow connection e.g at crossbrowsertesting.com; I used Chrome 29 on OSX 10.7
+
+Seen on beta labs and test2wiki with a fresh browser instance: 
+
+* Click Edit/beta, invoke VE
+
+** View of page appears, then disappears, refreshes and appears again before ""Welcome to..."" iframe appears
+
+* Click X to dismiss iframe
+
+** iframe disappears for a moment, then reappears, then disappears again
+
+Given a slow enough connection, this behavior could be bothersome for regular users of VE.  
+
+It definitely causes constant failures in the browser tests for Chrome on both beta labs and test2wiki. 
+
+This is not seen in Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55756",1380670380,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-g37szxauflfw6qlavwpb,task_description,declined
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page",This bug was reported and is reproducible against Chrome version 29 but does not appear in Chrome version 30.  Closing.,1381934805,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","This may only happen in Chrome 29, I have yet to repro in Chrome 30",1381871567,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","
+Because both the underlying page and the Welcome to... overlay appear and disappear and reappear and then finally disappear for good, there is a chance that the correct elements will be in place at the times that the test looks for them.  On rare occasions the  build will hit everything with perfect timing. 
+
+The other interesting artifact of this issue is that the tests in each build fail for different reasons, because the page and the overlay are appearing and disappearing and reappearing.
+
+Watching the behavior in crossbrowsertesting as noted above is instructive.  The appear/disappear/reappear/disappear-again behavior is easily seen, I just checked it again.
+
+And while the appearance of the 'You are not logged in' notice despite being logged in is more difficult to reproduce, it seems to be a symptom of the same issue.",1381853242,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","I'm confused as to how the browser tests for Chrome passed 9 days after this bug was filed - https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/72/ - only to fail again immediately thereafter, where the only intervening change in VisualEditor's code base was an alteration to the browser tests - https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/73/ - which feels like a different issue, and one where the problem is with the tests, not the code they are testing?",1381851780,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: ""Welcome to VisualEditor"" iframe causes Chrome to re-render the page","still seeing this in automated tests
+
+also, I reproduced this again manually using the slow connection at crossbrowsertesting.com as noted, and in addition to seeing the double-load of the page and double-load of the welcome notice, after clearing the notice I am presented with a message ""You are not logged in"".  This is impossible of course, since I have to be logged in with the opt-in preference set in order to be able to invoke VE at all. 
+
+The ""You are not logged in"" notice does not appear consistently.",1381497555,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-g37szxauflfw6qlavwpb,task_subcomment,NA
+"VisualEditor: Pressing ""enter""/""return"" on a selected node should open its dialog","When a template is selected in the VE editing surface pressing enter should open the transclusion dialog.
+
+When an image is selected in the VE editing surface pressing enter should open the media settings dialog.
+
+These will be of benefit to people making textual changes to the surrounding context who want to make textual changes to the template output / image caption.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50996",1380637920,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-6g5do6pkec5ll56oa4cb,task_description,resolved
+"VisualEditor: Pressing ""enter""/""return"" on a selected node 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",1395274517,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6g5do6pkec5ll56oa4cb,task_subcomment,NA
+"VisualEditor: Pressing ""enter""/""return"" on a selected node should open its dialog","Change 103062 had a related patch set uploaded by Robmoen:
+Create mixin for ce nodes that responds to dblclick
+
+https://gerrit.wikimedia.org/r/103062",1395182321,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6g5do6pkec5ll56oa4cb,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"**Author:** `romaine.wiki`
+
+**Description:**
+The VisualEditor substitutes templates that shouldn't been substituted. The largethumb template got substituted on several occasions, like:
+
+https://nl.wikipedia.org/w/index.php?title=Managua_%28stad%29&diff=38749742&oldid=38743043
+
+If this continues to happen too long, we are forced to disable the VisualEditor for everyone as it changes things that absolutely should not be changed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54315",1380575880,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_description,resolved
+Images: {{largethumb}} template on nlwiki getting substituted on save,Scheduled for deployment next Wednesday.,1392422883,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"Change 110095 merged by jenkins-bot:
+Set up data-mw for all templated image attributes.
+
+https://gerrit.wikimedia.org/r/110095",1392413847,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"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",1391639496,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"If the Parsoid will be able to parse this, this would at least avoid bad rendering (thumbnail at the right size) and fix (selfishly) my concern :)",1386531660,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"We can parse it (so that it renders as expected), but I don't see a sane way to represent multiple attributes generated by the same template for visual editing.",1386440765,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"@Gabriel Do you mean Parsoid won't be able to parse this template in the same way like the PHP one does?
+
+After discussing a little bit about that on the nlwiki IRC channel, they are (of course) not so happy about that. Not only because the thousands of pages but also because the template is old and a lot of people would have then to change their habits.",1386437138,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"(In reply to comment #4)
+> Wanted to create an offline copy of nlwiki; but this bug is, for this usage,
+> a
+> showstopper.
+> 
+> The rendering is awful (but this is nothing new), for example:
+> http://parsoid-lb.eqiad.wikimedia.org/nlwiki/Abraham_Lincoln?oldid=39371115
+> 
+> ... and such type of templates are widely used: ~10.000 articles only for
+> {{largethumb}} on nlwiki. This bumps the whole size of the dump by a factor
+> 2.
+> 
+> @James, good news: I have had a look a little bit around and I don't have
+> found
+> other templates working on the same principle.
+
+@Kelson, that is great news! Scott is looking into image rendering issues, so assigning to him. We should be able to add a special-case hack for this template and edit-protect affected images.
+
+For proper editing the thumb parameter should be pulled out, as in |thumb|{{large}} with large returning just something like '400px'. That will require some convincing and bot activity.",1386358615,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"Wanted to create an offline copy of nlwiki; but this bug is, for this usage, a showstopper.
+
+The rendering is awful (but this is nothing new), for example:
+http://parsoid-lb.eqiad.wikimedia.org/nlwiki/Abraham_Lincoln?oldid=39371115
+
+... and such type of templates are widely used: ~10.000 articles only for {{largethumb}} on nlwiki. This bumps the whole size of the dump by a factor 2.
+
+@James, good news: I have had a look a little bit around and I don't have found other templates working on the same principle.",1386332566,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,This doesn't round trip in Parsoid.,1382449752,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"**romaine.wiki** wrote:
+
+I haven't seen it happen with other templates so far.",1381767772,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+Images: {{largethumb}} template on nlwiki getting substituted on save,"Is this just the {{largethumb}} template, or are there others? (Templates that define some but not all of the parameters of an image are particularly troublesome.)",1380833746,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2pa34yqzcieje3dwrtub,task_subcomment,NA
+VisualEditor: Linebreaks not preserved when converting preformatted text to paragraph text. ↵ Displayed in VE but not saved.,"Screenshot explaining issue with visualeditor
+
+Hi
+These are the steps:
+
+*Create a preformatted multiline text, inserting a space before each line, in source mode.
+*Open visualeditor, select the text inside the box (the preformatted text)
+*Change text type to ""paragraph""
+*The text is badly converted, return characters appear on the line. If the text is saved the return characters are lost.
+*This happens in other cases too, tab symbols are displayed sometimes.
+
+Thank you.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12384}",1380563940,PHID-USER-vj2bbc63joi46qr5a5nq,False,PHID-TASK-iesy7n57vtjmvbveuqa4,task_description,open
+VisualEditor: Linebreaks not preserved when converting preformatted text to paragraph text. ↵ Displayed in VE but not saved.,The ↵ characters indicate that the newline is preserved as if you edit the page subsequently and convert the paragraph to preformatteed the line breaks return.,1380644617,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-iesy7n57vtjmvbveuqa4,task_subcomment,NA
+"VisualEditor: Provide a way (beyond Ctrl-Click, middle-click, or right-click/tab) to open links in another window","I couldn't find a way to click the links while editing and go to the target page. It's not easily available in the source editor, so it's not really a regression, but I find myself needing this features every time I edit, because the links are blue and look like links.
+
+GMail and Google have reasonably good ways of going to links' targets in editing mode, so hints can be taken from them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50321",1380443280,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ge3lxw5vifprlb3diogc,task_description,resolved
+"VisualEditor: Provide a way (beyond Ctrl-Click, middle-click, or right-click/tab) to open links in another window",Fixed in gerrit 139550.,1405375886,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ge3lxw5vifprlb3diogc,task_subcomment,NA
+"VisualEditor: Provide a way (beyond Ctrl-Click, middle-click, or right-click/tab) to open links in another window","Right-click and 'open in new tab' works for me (tested in Firefox 24), but it'd be better to have something findable in the edit toolbar (or at *least* the link edit dialog) with a 'regular' click.
+
+Right-click or long-press for context menus aren't something everybody knows well or jumps straight to.",1380484636,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-ge3lxw5vifprlb3diogc,task_subcomment,NA
+VisualEditor: Show user that drag-and-drop of textual content is not supported,"+++ This bug was initially created as a clone of Bug #50643 comment 6 +++
+
+Steps to reproduce:
+1. Edit a page in VE
+2. Select a piece of textual content without any fancy stuff in it.
+3. Drag it to another location in the page
+
+Expected results:
+The cursor should be a disabled-drop icon
+
+Actual results:
+The cursor is an 'image' icon
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1380437160,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-g2els4untqmatfgmtodr,task_description,declined
+VisualEditor: Show user that drag-and-drop of textual content is not supported,"Given we are about to support text drag and drop with bug 49981, marking as wontfix.",1403008828,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g2els4untqmatfgmtodr,task_subcomment,NA
+VisualEditor: Show user that drag-and-drop of textual content is not supported,"What the?  Drag and drop text appears to be not working in Chrome either; I am pretty sure I remember dragging and dropping text in Chrome in July, but maybe I am mistaken.",1380601042,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-g2els4untqmatfgmtodr,task_subcomment,NA
+VisualEditor: Dropdown clipping is a bit too aggressive,"Dropdown clipping
+
+Referring to the attached screenshots there are two issues:
+
+1. The width is not adjusted to account for the OS scrollbacks. I assume this is because has one of those fancy Macintosh computers that doesn't know how to draw a big chunky old-fashioned scroll bar.
+
+2. The assumption is made the the height of the VE container is the maximum height the scrollbar expand to. Here that is clearly not the case. It may be the case that because we don't know what lies beyond the borders of VE (e.g. z-index 9999 banner), we can't do anything about this. Maybe we can make the assumption the page content is sane, and if the dropdown ends up obscured, leave that as an integration problem for the user?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69707
+
+**Attached**: {F12176}",1380295440,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5udersenidwseo6m5grs,task_description,resolved
+VisualEditor: Dropdown clipping is a bit too aggressive,Fixed in OOjs UI with gerrit 157295.,1415881674,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5udersenidwseo6m5grs,task_subcomment,NA
+VisualEditor: Dropdown clipping is a bit too aggressive,"Corrections:
+scrollbacks -> scroll bars
+is because has -> is because Trevor has",1380301150,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5udersenidwseo6m5grs,task_subcomment,NA
+VisualEditor: Switching from categories to languages while suggestion popup is open doesn't close popup,"Screenshot of languages dialog tab with the new-category popup in front
+
+Switching from categories to languages while suggestion popup is open doesn't close popup -- see screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12105}",1380219960,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-4y6au3cwi5b6pobrhrz5,task_description,resolved
+VisualEditor: Switching from categories to languages while suggestion popup is open doesn't close popup,This was fixed a while ago.,1398184329,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4y6au3cwi5b6pobrhrz5,task_subcomment,NA
+VisualEditor: Category editing tool should preview or at least link to the input categories,"Screenshot of category dialog, showing no apparent way to get at the listed categories
+
+The category suggestion tool seems to provide a simple typeahead search, but provides no way to go and see if the categories you've found are relevant.
+
+At a minimum, you should be able to open up the category page via a link from the search box and and the little tag display.
+
+Better still might be a little preview that pulls the description text (if any) and some sample contents right within the dialog box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12103}",1380219780,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-w3ca2knqurlwdolz6rth,task_description,open
+VisualEditor: Category editing tool should preview or at least link to the input categories,Seems like a nice idea. Provide a link in the category menu?,1415881475,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-w3ca2knqurlwdolz6rth,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"This is kind of a meta bug and not an actual issue in BZ. Couldn't think of a better place to file it...
+
+Filing bugs/enhancements is difficult for some people to figure out. We can lower the barrier pretty easily by making a 1 or 2 minute video showing you how. Upload to commons, link to from BZ main page.
+
+Key components:
+- Sign up
+- Choosing the right product
+- Giving clear description of the problem/request
+-- Screenshots are fantastic
+-- Providing links is great too
+- Make sure to emphasize to not worry about filling all the fields out properly, the important step is opening the bug!
+
+Major props to User:Biosthmors on enwiki for coming up with the idea.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**Whiteboard**: gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks
+**URL**: https://commons.wikimedia.org/wiki/File:How_to_file_a_report_in_Bugzilla.webm
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52696",1380129240,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_description,resolved
+Make tutorial video on how to use Bugzilla,Excellent work Shujat! Thank you very much :-),1389707273,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Shujat completed the tutorial, which is available at https://commons.wikimedia.org/wiki/File:How_to_file_a_report_in_Bugzilla.webm
+
+Your help featuring it in mediawiki.org and other projects is welcome!
+
+Thank you very much, Shujat.",1389653591,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,*** Bug 58965 has been marked as a duplicate of this bug. ***,1389276275,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"
+
+(In reply to comment #33)
+> That's totally fine. Is the address bar (where the URL is shown) still
+> visible?
+> I'd say that's preferable to have.
+> 
+Well, I got that fixed by now, so its not a problem anymore, only the address bar is visible.
+But the g-mail will would be appearing, can't fix that.",1387984472,PHID-USER-oyf7m4w6q3dcftbg22jg,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #30)
+> Hello, I'm a student from GCI, and I've been assigned this task.
+> So, about the screencast, I have an idea: how about once the user account has
+> been created successfully, I go to http://www.mediawiki.org/wiki/MediaWiki,
+> then search for How to report a bug. From there I move to the new guided
+> form.
+
+OK
+
+(In reply to comment #32)
+> The script tells to go to your e-mail client, and I went to my gmail account
+> to get the mail, is that okay?
+
+Let's see how it looks like. The idea about not showing browser/email/OS chrome is to make the video as generic and as brand-free as possible. Don't worry, we can always cut.",1387811170,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #31)
+> Well, in the video, the windows taskbar or chrome logo is not there but tabs
+> are visible, that okay?
+
+That's totally fine. Is the address bar (where the URL is shown) still visible? I'd say that's preferable to have.
+
+(In reply to comment #32)
+> The script tells to go to your e-mail client, and I went to my gmail account
+> to get the mail, is that okay?
+
+Yes, but if you prefer to not show your real private email address and inbox at that time to the world, you might want to create another email account just for testing and making this video.",1387809225,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"The script tells to go to your e-mail client, and I went to my gmail account to get the mail, is that okay?",1387789082,PHID-USER-oyf7m4w6q3dcftbg22jg,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Well, in the video, the windows taskbar or chrome logo is not there but tabs are visible, that okay?",1387787959,PHID-USER-oyf7m4w6q3dcftbg22jg,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Hello, I'm a student from GCI, and I've been assigned this task.
+So, about the screencast, I have an idea: how about once the user account has been created successfully, I go to http://www.mediawiki.org/wiki/MediaWiki, then search for How to report a bug. From there I move to the new guided form.",1387787509,PHID-USER-oyf7m4w6q3dcftbg22jg,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Thank you Richard!
+
+The task about writing a script has been completed. I just created the task to produce the screencast:
+
+http://www.google-melange.com/gci/task/view/google/gci2013/5787018130882560",1385741411,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+Ok, i think its just about there, Did i seem to mention anything
+Link for convenience: https://www.mediawiki.org/wiki/User:Richardusername/BugzillaScriptProject",1385677331,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"I have given Richard my last round of comments. The script already looks very good. If you have additional feedback don't comment: edit the script directly (""Be bold"").
+
+As soon as this task is completed I will create a new one about creating the screencast.",1385604293,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Ok Richard, you don't need to get stuck in this discussion about the origin of the link. Whenever someone (you?) creates the screencast we will use an existing entry point in a wiki page (VisualEditor would work, as specified in your script).",1385504263,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #18)
+> I'm not sure how to transition from logging in to using the new formatted bug
+> submission form, as there seems to be no link from the site homepage.
+
+Uhm. I don't have an easy answer to that either right now. :(
+
+So far I've expected users to follow links on wikipages which point to the ?format=guided form in the URL. 
+But as Elitre already wrote: Discussed in bug 57254.",1385463812,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"It's a good first draft, but still needs more work. I have left my feedback. Andre and other readers of this report are encouraged to comment there as well.",1385445031,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+The draft is finished if you're interested. Just going to clean it up and maybe add more details. Link again for CC:https://www.mediawiki.org/wiki/User:Richardusername/BugzillaScriptProject",1385427743,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+Thanks for the video! It was exactly what I was thinking of, except doing this one more to the point. Also this is my main account, was accidentally logged in to wrong one when posting the last one. (I was going through the steps again)  As for the brief sign-up , we can easily remove it if needed, so ill just leave it until final revisions.",1385426393,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Hi Richiell!
+
+Slides vs screencast, this video was well received here. Just in case it serves as source of inspiration: 
+
+> http://blog.johnath.com/2010/02/04/bugzilla-for-humans/
+
+There is another GCI task about title cards for videos, but they are not ready yet. Still, this task is about agreeing on the script, so never mind.
+
+Same for the link to the guided form. You are right, currently there is no way to reach it from Bugzilla itself. However, for your script we can assume that it will be in the home.
+
+About your script, feel free of reusing the very little I could do at https://www.mediawiki.org/wiki/Talk:How_to_report_a_bug#Screencast
+
+I also started thinking of the registration process. Then again, Bugzilla's registration is quite standard, so perhaps it is better to save that time to the viewers of the video and yourself. Mention in the script that users must be registered in order to file bugs, feel free spending 3 seconds to point to the Register link in the home and get directly to the stuff.
+
+This means that the beef of your script is ""Examples"".  :) 
+
+Sorry for not reaching to this conclusion before! Your draft helped reaching to this conclusion. This is how iterations work...",1385425713,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**richiell** wrote:
+
+Ive made a little bit of progress on the script, here's the link if anyone wants to follow it: https://www.mediawiki.org/wiki/User:Richardusername/BugzillaScriptProject",1385421755,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Hear, hear! Bug 57254.",1385418631,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+I'm not sure how to transition from logging in to using the new formatted bug submission form, as there seems to be no link from the site homepage.",1385418288,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,":) I wouldn't like to see slides in the video, but hey, that's just me. Let's see what Andre thinks, since he rules over Bugzilla here!",1385417958,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+(In reply to comment #15)
+*or girls",1385416581,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+OK, Im thinking about doing the script with part Slideshow and mostly a Guided screen recording. What do you guys think about that?",1385416522,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,Awww! Thanks a lot!,1385400061,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"**lettrich42** wrote:
+
+I am a student from Google Code in this task was assighned to, and I will start today, begining in a couple of hours. (Regular updates were required)",1385399968,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #11)
+> You should post that guided form to wikitech-l
+
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-October/072786.html",1383585826,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #10)
+> https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditor&format=guided
+
+That is REALLY nice!!  You should post that guided form to wikitech-l, I am sure other components could make use of a similar form.",1383574738,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"The guided form is now ready (i.e. https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditor&format=guided ), and I'd really love to have a screencast about it!",1383570076,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Note that there are also bugzilla.mozilla.org thoughts on having video tutorials for specific Bugzilla topics: https://bmo.etherpad.mozilla.org/bugzilla-tips-videos
+I don't know how much upstream this would be though.",1381787304,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Currently I'd use the normal form with ""Hide Advanced Fields"" enabled, and either MediaWiki or Wikimedia product, plus component ""General/Unknown"".",1381763815,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,Guided form (bug 36762) is still under development and not deployed - this week was too busy with reallife but will try to get it into shape next week.,1381503809,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Well, yes, a video screencast.
+
+What I'm asking is whether we should do it using the plain Bugzilla interface or the guided form.",1381468109,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"(In reply to comment #4)
+> What interface should we use for this screencast? The traditional or this new
+> one Andre is cooking up?
+
+I'd assumed you'd create a video in .ogv format.
+
+A paginated PDF is also an option.",1381459718,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"What interface should we use for this screencast? The traditional or this new one Andre is cooking up?
+
+I have started defining a rough script at https://www.mediawiki.org/wiki/Talk:How_to_report_a_bug#Screencast",1381444276,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"For the records (and inspiration), the only pretty good (and partially Mozilla-centric) video I am aware of is http://blog.johnath.com/2010/02/04/bugzilla-for-humans/",1380150692,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"A screencast showing the shortest path to file a bug report should do. I haven't done a screencast in ages but I will try tomorrow, with the hope that someone hates what I did and produces something better.  :)
+
+In fact this could be start of something. We could have more short screencasts focusing on a specific action (advanced search, comment on a bug...) and extend the idea to other tools (get developer access, comment on Gerrit...). These short videos could be easily embedded in the right wiki pages and...
+
+But let me try with this File Your First Bug screencast first.  :)",1380145913,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Make tutorial video on how to use Bugzilla,"Maybe Victor / some designers / whoever, can produce nice video intro and outro :)",1380143726,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-gmswkf7wwjtivxzlq3hb,task_subcomment,NA
+Improve handling of stray table tags / Verify that we handle stray table tags correctly,"Occasionally, pages have stray opening table tags which may end up screwing up DSR computations (which in turns messes up selser). It is possible that our latest foster parenting code implicitly handles this by wrapping the entire table as templated and protected a large body of code (which could then serve as a flag to the user to look for bugs in the wikitext souce). So, it might be worth verifying this and adding tests to spec this behavior.
+
+See the bug report: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=574391235#Duplicated_content_when_deleting_apparently_blank_lines
+
+See my response that fixed the problem in the wikitext source: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=574483272#References_and_tables
+
+If this is not already handled by our handleUnbalancedTables and markFosteredContent DOM passes, we may need to tackle this -- by maybe adding a fixup in TokenStreamPatcher that enforces limited table scope (section boundaries is the obvious scope limiter => close unclosed tables whenever section heading tokens are encountered).
+
+To be investigated and fixed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380128640,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-s52vfnr5655l5mcn3ccw,task_description,resolved
+Improve handling of stray table tags / Verify that we handle stray table tags correctly,"We have made a bunch of fixes over the years. Since then, we also have wikitext linting that flags brokenness (fostering, missing end tags) which cover some of these cases. I don't think we should clutter the Parsoid code base trying to make sense of obviously broken markup. So, I am going to close this as resolved.",1592505284,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-s52vfnr5655l5mcn3ccw,task_subcomment,NA
+Improve handling of stray table tags / Verify that we handle stray table tags correctly,"(In reply to comment #0)
+> Occasionally, pages have stray opening table tags which may end up screwing
+> up
+> DSR computations (which in turns messes up selser). It is possible that our
+> latest foster parenting code implicitly handles this by wrapping the entire
+> table as templated and protected a large body of code (which could then serve
+> as a flag to the user to look for bugs in the wikitext souce). So, it might
+> be
+> worth verifying this and adding tests to spec this behavior.
+
+That seems to happen if a template is present, as in:
+
+  {|
+
+  {{echo|hi}}
+
+  ;Ho
+
+However, that's not the case in the bug report. It's more like,
+
+  {|
+
+  ;Off to work we go
+
+
+> 
+> See the bug report:
+> https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Feedback&oldid=574391235#Duplicated_content_when_deleting_apparently_blank_li
+> nes
+> 
+> See my response that fixed the problem in the wikitext source:
+> https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Feedback&oldid=574483272#References_and_tables
+> 
+> If this is not already handled by our handleUnbalancedTables and
+> markFosteredContent DOM passes, we may need to tackle this -- by maybe
+> adding a
+> fixup in TokenStreamPatcher that enforces limited table scope (section
+> boundaries is the obvious scope limiter => close unclosed tables whenever
+> section heading tokens are encountered).
+
+Seems reasonable.
+
+> 
+> To be investigated and fixed.",1380840132,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-s52vfnr5655l5mcn3ccw,task_subcomment,NA
+Large number of CSS rules for external links,"Assigning to Parser as I suspect this is what would need to be fixed up to support this.
+
+This patch [1] demonstrates the large number of rules exist for external links:
+
+The browser matches styles from right to left, so the rightmost selector is really important.
+
+We shouldn't need to have to resort to CSS rules in the form div#content a.external[href ^=""https://""] - a link with class external should also have a class describing what type of external link it is if it is necessary. These selectors are less efficient and are not supported by older browsers.
+
+Ideally we should simply these rules to become something like:
+
+.link-audio,
+.link-video,
+.link-document,
+.link-irc,
+.link-ftp,
+.link-https,
+.link-news,
+.link-mailto {
+padding-right: 13px;
+background: transparent center right no-repeat;
+}
+
+with rules for each of them for their correct icon.
+
+[1] https://gerrit.wikimedia.org/r/#/c/85920/2/skins/vector/externalLinks.less
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63725
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63521",1380128040,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_description,resolved
+Large number of CSS rules for external links,"Sigh.
+I'm frustrated by the removal of icons that were useful.",1418760677,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,Meh.,1418744473,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"PDF: To clarify this, the icon was always a generic document. On the English Wikipedia it uses an Adobe icon through Common.css.
+
+The Typography Refresh removed the other icons in Vector. HTTPS icons were removed per Bug 61178.
+
+So currently on the English Wikipedia we have the external link icon and the Adobe icon. Both are meaningless to our visually impaired readers since none of the icons have alt text; see Bug 45891.
+
+Since many documents are now produced by dynamic web pages, they do not have the file extension that the CSS rules trigger on, thus those documents will show the simple external link icon.
+
+Bottom line: How useful are the icons? Is there any other project using icons in this manner?",1413544350,PHID-USER-zqde3skdzpqiwny4dxt4,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"1) As I said in comment #6 - the mailto, irc, audio/video, and pdf icons are frequently useful for:
+* Readers to have ""principle of least astonishment"" when clicking on links which often have a non-typical-navigation result.
+* Editors to see that an unusual link has been used/added, which might warrant further investigation.
+
+2) Our internal Pronunciation links all have an icon added automatically: e.g. https://en.wikipedia.org/wiki/Template:Pronunciation and https://en.wikipedia.org/wiki/Template:IPA - e.g. at [[Götterdämmerung]]
+
+Then, 2 similar ""bits of information - a difference that makes a difference"" that any of our users might appreciate.
+
+3) we have a request from the Internet Archive to add icons to their links: #1 at https://www.mediawiki.org/wiki/Archived_Pages#Implementation_ideas (mentioned at https://lists.wikimedia.org/pipermail/design/2013-October/001065.html )
+
+4) we have a request from the community, (and I believe connected to The Wikipedia Library), to add icons that denote Open-Access resources: https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Open_Access/Signalling_OA-ness
+
+For all of these reasons, I hope we can re-instate these icons in Vector. 
+The patch to do so is currently -2'd based on lack of apparent consensus (https://gerrit.wikimedia.org/r/#/c/154350/). 
+I've also left a comment (the first...) at [[Help talk:External link icons]]. 
+Comments here or there, with additional rationales for supporting or opposing the re-instatement (for use-case or technical or other reasons) would be appreciated.",1413530059,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Bartosz Dziewoński from comment #81)
+> So the general agreement is that it was good in the beginning and the change
+> above was a bad idea.
+
+I don't know how you have determined this from the above. Please give me the precise quotes you are attributing to.
+
+All I see is agreement that we shouldn't use classes and should use an approach such as [href^=""https://""]
+
+Whether they are a good idea is another question.
+I wouldn't want them on my local wiki for example.",1409175468,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 154350 had a related patch set uploaded by Bartosz Dziewoński:
+Restore external links icons
+
+https://gerrit.wikimedia.org/r/154350",1408142652,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"So the general agreement is that it was good in the beginning and the change above was a bad idea. In other words, we should revert https://gerrit.wikimedia.org/r/#/c/123817/ in the Vector skin.
+
+(Also, moving this to the Vector component, since the only changes that were implemented and the entire discussion involved only that skin.)",1408140797,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 141973 abandoned by Bartosz Dziewoński:
+Linker: Add CSS classes to external links to some protocols/filetypes
+
+Reason:
+Right.
+
+https://gerrit.wikimedia.org/r/141973",1408140617,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #77)
+> Isarra. What was the motivation for putting them in in the first place?
+
+Given that this was orginally added in 2004, I couldn't say. I can, however, point you to comment #3 and comment #6, which detail specific reasons for keeping them in now.
+
+> Putting styles in both core and common.css that do the same thing is a
+> terrible terrible terrible thing and we should at least resolve that problem
+> at the same time. The fact those rules exist there show MediaWiki was not
+> serving there purpose and they were /not/ useful.
+
+As I said, the English Wikipedia is not the only project that uses this software. What they do doesn't necessarily apply to other projects, especially when we don't even know why they did what they did.
+
+> Currently each project as complete free reign to add these icons in
+> common.css if they want to. I truly don't see the value in them being here.
+
+Each project is free to write their entire skin css in common.css if they want to. Doesn't mean they should have to do that either.",1404409477,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #77)
+> PS. How can I remove myself from this bug. Since I'm the creator, it doesn't
+> seem possible.
+
+Sorry, only available in next version: https://bugzilla.mozilla.org/show_bug.cgi?id=148564 - For the time being, custom filters / thread muting.",1404409227,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Isarra. What was the motivation for putting them in in the first place?
+
+Putting styles in both core and common.css that do the same thing is a terrible terrible terrible thing and we should at least resolve that problem at the same time. The fact those rules exist there show MediaWiki was not serving there purpose and they were /not/ useful.
+
+Currently each project as complete free reign to add these icons in common.css if they want to. I truly don't see the value in them being here.
+
+Isarra making use of icons is not the same as those icons giving value.
+
+PS. How can I remove myself from this bug. Since I'm the creator, it doesn't seem possible. @Andre.. ?",1404407556,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #75)
+> The icons for audio, video etc have been gone for some time without any
+> complaints that I am aware of. Maybe because a lot of these styles are
+> implemented in MediaWiki:Common.css
+
+Yes, nobody noticing would make it more difficult for anyone to complain about it.
+
+> Let's not re-instate these classes and CSS rules. The status quo is
+> currently fine. Let's not add back css rules for the sake of adding back css
+> rules. I feel like we are wasting far too much energy on this bug.
+
+MediaWiki serves more than just the English Wikipedia. While the icons often do serve little purpose on individual projects, many other projects do indeed make use of these icons, especially third-party technical projects which will not have seen that change at all due to generally being on stable releases (1.19, 1.22, 1.23 etc). This is not adding back css rules for the sake of adding them back, this is adding them back with a reasoned technical discussion about how best to do so considering the current technology, with the understanding that projects do use them, that there are real-life use cases speaking to their usefulness, and that there was no consensus to remove them in the first place.",1404403168,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"The icons for audio, video etc have been gone for some time without any complaints that I am aware of. Maybe because a lot of these styles are implemented in MediaWiki:Common.css
+
+Let's not re-instate these classes and CSS rules. The status quo is currently fine. Let's not add back css rules for the sake of adding back css rules. I feel like we are wasting far too much energy on this bug.",1404401835,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Phew .. long discussion. I could have gone either way (selectors or css classes) till I hit Gabriel and Roan's comments and now Krinkle's about client burden and code duplication to support classes/attributes. If there were no alternatives and this were the spec, of course, all clients would have to implement it, but given that there are no serious drawbacks to picking selectors over classes, I too think that it is a better idea to use css for icon-styling of links.",1404399874,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Bartosz Dziewoński from comment #54)
+> (In reply to Gabriel Wicke from comment #52)
+> > Do we have actual measurements that verify that this benefits total page
+> > view performance in practice?
+> 
+> We don't. Jon provided some funky tool in comment 11 but I've been unable to
+> get it to work. Krinkle provided a theoretical explanation on why this
+> should make a difference in comment 10.
+
+The performance impact is quite negligible actually. I'd rather let browsers worry about that. This shouldn't be a main driving factor in this case because it is too insignificant. My main point there was maintenance overhead:
+
+(Citing comment #10 from Krinkle)
+> * Hardcodes details that (other) stylesheets should not have to know or hardcode, thus causing maintenance issues (e.g. the fact that it is an <a>, and is inside #bodyContent. The container can change, and links might be wrapped for presentational reasons)
+
+This would be mitigated by using a selector like:
+
+.mw-body-content a[href^=""https://""] {}
+
+This doesn't have the added weight of an ID selector (#bodyContent) and is quite minimal and straight forward.
+ 
+
+(In reply to Gabriel Wicke from comment #62)
+> (In reply to Daniel Friesen from comment #61)
+> > What if we ""don't"" want an icon?
+> 
+> The .plainlinks class was normally used to mark this up, and applied to all
+> links inside a content block. How does this work with classes on each link?
+
+That is indeed an important one to remember. Let's make sure we're compatible with that.
+
+(In reply to Gabriel Wicke from comment #69)
+> One issue I didn't mention yet is editor complexity. Every editor for our
+> HTML including VE will need to replicate the class logic from the parser.
+> This includes future micro-contribution tools like 'fix this link'. It seems
+> likely that this will lead to rendering inconsistencies when the logic
+> replication is not perfect.
+
+I agree. Adding all these classes to the Parser will inflate Parser output with information that can trivially be derived from the href attribute, doesn't really provide value to customers of the HTML (other than saving a few characters in stylesheet), and adds more or less random complexity to other producers of HTML such as VisualEditor content editable preview nodes and Parsoid. All the information about the url is right in the href. I think keeping classes like these out of page HTML would be optimal for maintenance overall:
+
+* Avoid imposing requirements on VE and Parsoid to add arbitrary attributes that the applied stylesheets should maintain instead. Separating responsibility and concerns; Unless it's a huge performance penalty we really shouldn't consider adding hooks like these inside the Parser for the skins' convenience.
+
+* Avoid optimising arbitrarily for the needs of one skin (the classes we add would only be for certain protocols and include certain file extensions in the media types. If another consumer doesn't agree with our grouping or wants more, they'd be back to square one in using href-matching; ergo, the approach doesn't scale and signifies that it'd wrongly divide responsibility between parser and stylesheet.
+
+
+I'd recommend going with something like:
+
+.mw-body-content .external[href^=""https://""] {}",1404397752,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Re performance, I have not been able to find anything on the web that indicates that CSS selector performance is a significant issue in practice.
+
+This SO articles seems to provide a good overview:
+http://stackoverflow.com/questions/12279544/which-css-selectors-or-rules-can-significantly-affect-front-end-layout-renderi",1404340285,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,+1 to Roan and Gabriel.,1404337326,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #69)
+> One issue I didn't mention yet is editor complexity. Every editor for our
+> HTML including VE will need to replicate the class logic from the parser.
+> This includes future micro-contribution tools like 'fix this link'. It seems
+> likely that this will lead to rendering inconsistencies when the logic
+> replication is not perfect.
+
+This is also a problem for VisualEditor. Even in the current system, not including any micro-contribution tools that Gabriel talks about, we would need three entirely separate copies of this logic, in:
+* MediaWiki's wikitext->HTML parser
+* Parsoid, to generate correct HTML
+* VisualEditor, to display newly created links correctly
+
+VE generally deals well with styling that comes from the parser side and displays it correctly, but in this case the user could create a link entirely from scratch, and that link might be a .pdf link. Then even though there may not be another .pdf link anywhere on the page, we still need to know that .pdf is magical and should trigger a certain CSS class in order to produce the correct rendering. That's why we need a full duplicate of the icon logic.
+
+So in general, we try to move this kind of logic fully *into* CSS, rather than *out of* CSS and into *code*. Last year this was done for auto-numbered external link numbering: instead of implementing a bunch of numbering logic both in Parsoid and in VE, we were able to number them entirely in CSS using CSS3 counters.
+
+With that in mind, I would much prefer that link icons be done in pure CSS, with attribute selectors in their full ""glory"". That way VisualEditor and any other clients that need to generate new HTML will not have to reimplement the logic from scratch, and instead will just be able to load the CSS. Unless attribute selectors are horrendously slow (which they're probably not, the original CSS rules for link icons date back to 2004), moving to classes just makes things worse, not better.",1404267558,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,One issue I didn't mention yet is editor complexity. Every editor for our HTML including VE will need to replicate the class logic from the parser. This includes future micro-contribution tools like 'fix this link'. It seems likely that this will lead to rendering inconsistencies when the logic replication is not perfect.,1404264536,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Oh, MediaWiki uses more advanced things for styling (like… LESS?), that was never the problem. The only problem was unspecified performance issues.
+
+But I really don't feel like introducing two new ways of doing such a little feature is the right thing to do from a maintainability standpoint (both the maintainability of core, and maintainability of any skins that might want to use different icons).",1404260905,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Bartosz Dziewoński from comment #66)
+> As I said before, I'm okay with doing this either way (we can revert the old
+> patch that removed this feature in Vector), but let's please not do both
+> ways at once.
+
+We are using attribute matches for a bunch of things in any case, so it's not like somebody working on MediaWiki CSS would now be exposed to new CSS 2 selectors. The main change would be the introduction of classes to eliminate overly complex attribute matches on file extensions, which I think is fairly easy to understand.",1404145601,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #64)
+> Looking at the linked CSS [1], to me it seems that the most complex rules
+> are those matching on file extensions to figure out video / audio / document
+> links. As those links are not that common relative to the total number of
+> links I'd expect classes to be a win overall for those.
+> 
+> Protocol matches on the other hand are a single selector only (no need for
+> upper case variants), and a large chunk of external links is neither to
+> videos, audio or document files. This seems to favor keeping those matches
+> in CSS to keep the document size down.
+> 
+> Does this sound like a promising solution to you?
+
+Eh, I'd prefer if we decided on only one way of doing this and stuck to it. This seems to be the worst of both worlds.
+
+As I said before, I'm okay with doing this either way (we can revert the old patch that removed this feature in Vector), but let's please not do both ways at once.",1404067893,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #62)
+> The .plainlinks class was normally used to mark this up, and applied to all
+> links inside a content block. How does this work with classes on each link?
+
+.plainlinks .link-https has higher specificity than .link-https, so it's easy to disable the icon for plain links, if desired.
+
+(In reply to Gabriel Wicke from comment #64)
+> Looking at the linked CSS [1], to me it seems that the most complex rules
+> are those matching on file extensions to figure out video / audio / document
+> links. As those links are not that common relative to the total number of
+> links I'd expect classes to be a win overall for those.
+> 
+> Protocol matches on the other hand are a single selector only (no need for
+> upper case variants), and a large chunk of external links is neither to
+> videos, audio or document files. This seems to favor keeping those matches
+> in CSS to keep the document size down.
+
+I don't really know the performance details, but that seems reasonable.  PDF links are probably more common than audio/video, but still a minority.",1403925613,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Looking at the linked CSS [1], to me it seems that the most complex rules are those matching on file extensions to figure out video / audio / document links. As those links are not that common relative to the total number of links I'd expect classes to be a win overall for those.
+
+Protocol matches on the other hand are a single selector only (no need for upper case variants), and a large chunk of external links is neither to videos, audio or document files. This seems to favor keeping those matches in CSS to keep the document size down.
+
+Does this sound like a promising solution to you?
+
+[1]: https://gerrit.wikimedia.org/r/#/c/85920/2/skins/vector/externalLinks.less",1403807205,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #62)
+> > I'd like to see us moving away from descendant selectors and explore OOCSS
+> > [1] as a solution to our CSS mess we have created. We really should be
+> > making better uses of classes, and not be restricted by the implementation
+> > restrictions of Parsoid.
+> 
+> I don't have a strong opinion on what's done in skins. My interest is
+> restricted to the content area. In general, we are currently moving away
+> from any skin- and pref- specific HTML (including classes) in the page
+> content. Our goal is to speed up page views for editors to the level of
+> current anonymous views. This means that any variation in rendering between
+> skins should be implemented in CSS only, and should not rely on different
+> classes being set depending on skin or user preferences.
+
+The suggested link classes are universal, they are not skin or user specific they are always in the dom dependent on what is in the dom.
+
+> (In reply to Daniel Friesen from comment #61)
+> > What if we ""don't"" want an icon?
+> 
+> The .plainlinks class was normally used to mark this up, and applied to all
+> links inside a content block. How does this work with classes on each link?
+
+.plainlinks will continue to work for content, in fact it'll work even better since classes have less specificity than attribute selectors.
+But I'm not talking about content, but rather code. Adding links to elements or parts of the skin that happen to be under the root the link styles are defined on. With classes all an extension has to do is not use a link class. It can also add that link class to links that wouldn't normally match the selector (an extension could decide to link to a PDF reader with a document link style even though the url wouldn't have matched a .pdf$ selector.
+And to top that off by using classes instead of attribute selectors we can drop the root (#content / #bodyContent / .mw-body) since interface links won't be ruined by them anymore, and code can opt-in to link styles outside of content.
+
+> (In reply to Daniel Friesen from comment #60)
+> > Are the byte sizes of a few link classes really a big deal for actions as
+> > infrequent as a save?
+> 
+> Page size is a big deal for uncompressed uploads, as upload speeds are
+> normally much slower than download speeds. Uploading a large article like
+> [[San Francisco]] from a DSL connection in San Francisco takes many seconds
+> (23 with current inline Parsoid metadata, around 7 without it), so a change
+> of 5% in the page size does have a measurable impact on save times, even on
+> a relatively fast connection. Things are worse than that when you are on a
+> bad connection in India.
+
+Which brings me to my other point:
+""Also I thought delta based saves were being done which make small byte size differences moot.""
+
+So in theory changing %5 of [[San Francisco]] should not involve uploading all of San Francisco. Unless VE is implemented really inefficiently, tiny additions like link classes shouldn't have as much effect on small edits. And if it is implemented that inefficiently, we have a larger problem than the bytes add to link classes.
+
+> > If they are, isn't there any serverside sanitization of the DOM? These are
+> > internally generated classes, so if it were an issue couldn't you just strip
+> > them before transmission and let the sanitizer or parsoid generate the
+> > classes?
+> 
+> We are working towards using Parsoid HTML for both views and editing, so
+> that you don't even loading a new page when switching to VE.
+
+Not relevant, my suggestion is that if you want size reduction on upload, then you could strip the link classes right before upload (which are automatically generated based on a set of rules) since and the server-side sanitizer (which should exist anyways to prevent the rules of the parser being intentionally screwed with or broken by an old VE version) would add them back. The parsoid output and view content (which are compressed and delivered by the faster download bandwidth) would still have the classes.",1403749130,PHID-USER-gibrlx54k2riiuit5paf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #59)
+> Another reason is styles written in this way are not reusable.
+> 
+> What if we want to use the same audio icon elsewhere?
+> 
+> With an icon-audio selector class we can.
+> With a selector based on href we can't.
+
+This seems to overstate the case a bit. There's nothing stopping us from adding a selector in the CSS, and I don't see why that's more complex than adding the class in HTML. 
+
+> I'd like to see us moving away from descendant selectors and explore OOCSS
+> [1] as a solution to our CSS mess we have created. We really should be
+> making better uses of classes, and not be restricted by the implementation
+> restrictions of Parsoid.
+
+I don't have a strong opinion on what's done in skins. My interest is restricted to the content area. In general, we are currently moving away from any skin- and pref- specific HTML (including classes) in the page content. Our goal is to speed up page views for editors to the level of current anonymous views. This means that any variation in rendering between skins should be implemented in CSS only, and should not rely on different classes being set depending on skin or user preferences.
+
+All these decision are engineering trade-offs, not implementation restrictions. If there are good engineering reasons (performance and CSS sanity for example) for generally adding more classes in the DOM & dumbing down the CSS selectors, then I'd be all for it.
+
+So far our strongest performance data seems to be page sizes, as that's easy to measure. Quantitative data on the relative importance of selector performance on total page render time is missing so far. My anecdotal evidence is that it wasn't noticeable when I added external link icons in 2004, on a laptop that would be considered a feature phone these days.
+
+(In reply to Daniel Friesen from comment #61)
+> What if we ""don't"" want an icon?
+
+The .plainlinks class was normally used to mark this up, and applied to all links inside a content block. How does this work with classes on each link?
+
+(In reply to Daniel Friesen from comment #60)
+> Are the byte sizes of a few link classes really a big deal for actions as
+> infrequent as a save?
+
+Page size is a big deal for uncompressed uploads, as upload speeds are normally much slower than download speeds. Uploading a large article like [[San Francisco]] from a DSL connection in San Francisco takes many seconds (23 with current inline Parsoid metadata, around 7 without it), so a change of 5% in the page size does have a measurable impact on save times, even on a relatively fast connection. Things are worse than that when you are on a bad connection in India.
+
+> If they are, isn't there any serverside sanitization of the DOM? These are
+> internally generated classes, so if it were an issue couldn't you just strip
+> them before transmission and let the sanitizer or parsoid generate the
+> classes?
+
+We are working towards using Parsoid HTML for both views and editing, so that you don't even loading a new page when switching to VE.",1403744805,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #59)
+> Another reason is styles written in this way are not reusable.
+
+I'll add one more reason.
+
+What if we ""don't"" want an icon? This should be as simple as not including the class. Using selectors this means you have to override a skin specific css rule, with an unknown weight to it. The selectors aren't even standardized yet, Vector used to use #content, MonoBook uses #bodyContent, and commonElements of course uses .mw-body (though for non-icon styles).",1403741384,PHID-USER-gibrlx54k2riiuit5paf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to C. Scott Ananian from comment #57)
+> @Daniel: long story, but basically gzip compression in HTTP only works in
+> the download direction.  There is no equivalent content negotiation for
+> uploads in HTTP.
+
+Oh you're talking about save sizes.
+
+Are the byte sizes of a few link classes really a big deal for actions as infrequent as a save?
+
+If they are, isn't there any serverside sanitization of the DOM? These are internally generated classes, so if it were an issue couldn't you just strip them before transmission and let the sanitizer or parsoid generate the classes?
+
+Also I thought delta based saves were being done which make small byte size differences moot.",1403738770,PHID-USER-gibrlx54k2riiuit5paf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Another reason is styles written in this way are not reusable.
+
+What if we want to use the same audio icon elsewhere?
+
+With an icon-audio selector class we can.
+With a selector based on href we can't.
+
+I'd like to see us moving away from descendant selectors and explore OOCSS [1] as a solution to our CSS mess we have created. We really should be making better uses of classes, and not be restricted by the implementation restrictions of Parsoid.
+
+[1] http://www.smashingmagazine.com/2011/12/12/an-introduction-to-object-oriented-css-oocss/",1403738706,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to C. Scott Ananian from comment #57)
+> @Daniel: long story, but basically gzip compression in HTTP only works in
+> the download direction.  There is no equivalent content negotiation for
+> uploads in HTTP.
+
+JS implementations aren't universally a win on all browsers & hardware either. See https://bugzilla.wikimedia.org/show_bug.cgi?id=66914 for some related discussion.",1403737647,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"@Daniel: long story, but basically gzip compression in HTTP only works in the download direction.  There is no equivalent content negotiation for uploads in HTTP.",1403737425,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #52)
+> We have use cases where uncompressed HTML is sent over the wire (HTML save
+> from VE), so uncompressed DOM size does matter.
+
+Why is it not compressed?",1403737169,PHID-USER-gibrlx54k2riiuit5paf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Bartosz Dziewoński from comment #54)
+> (In reply to Gabriel Wicke from comment #52)
+> > Do we have actual measurements that verify that this benefits total page
+> > view performance in practice?
+> 
+> We don't. Jon provided some funky tool in comment 11 but I've been unable to
+> get it to work. 
+
+Same here, it wouldn't even load for me.
+
+> Krinkle provided a theoretical explanation on why this
+> should make a difference in comment 10.
+
+Both of these aren't really telling us whether it's an overall win, draw or loss to add extra classes in the DOM & use those rather than match on existing properties. They both focus on one part of the picture only, and lack quantitative data. Only measurements can really answer this question.
+
+> (In reply to Gabriel Wicke from comment #53)
+> > One more note on browser support: IIRC these selectors were already
+> > supported by IE 6 in 2004.
+> 
+> Not by IE 6, but by every other browser, yes. IE 7+ supports them too.
+
+Ah, okay. Misremembered that then ;)",1403736790,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Gabriel Wicke from comment #52)
+> Do we have actual measurements that verify that this benefits total page
+> view performance in practice?
+
+We don't. Jon provided some funky tool in comment 11 but I've been unable to get it to work. Krinkle provided a theoretical explanation on why this should make a difference in comment 10.
+
+
+> If there is no measurable improvement on page
+> view / rendering even on mobile, then I'd propose to keep this in CSS to
+> avoid slowing down use cases like VE saves.
+
+You are actually proposing restoring this to CSS :), because it's already been removed (in spite of working well since 2004). I wouldn't mind that, personally.
+
+
+(In reply to Gabriel Wicke from comment #53)
+> One more note on browser support: IIRC these selectors were already
+> supported by IE 6 in 2004.
+
+Not by IE 6, but by every other browser, yes. IE 7+ supports them too.",1403735921,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,One more note on browser support: IIRC these selectors were already supported by IE 6 in 2004.,1403734881,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"We have use cases where uncompressed HTML is sent over the wire (HTML save from VE), so uncompressed DOM size does matter.
+
+Do we have actual measurements that verify that this benefits total page view performance in practice? If there is no measurable improvement on page view / rendering even on mobile, then I'd propose to keep this in CSS to avoid slowing down use cases like VE saves.",1403734104,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to C. Scott Ananian from comment #50)
+> Hm, Parsoid does not tag links with classes.  The only CSS would work fine
+> for parsoid-generated HTML; the new CSS will not.
+
+That is a bug in parsoid. We've required the .external class at minimum for years, parsoid should be able to handle link classes.",1403733775,PHID-USER-gibrlx54k2riiuit5paf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Hm, Parsoid does not tag links with classes.  The only CSS would work fine for parsoid-generated HTML; the new CSS will not.",1403733257,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"We'll have https (secure) and external link icons in wiki font soon (probably already) but wiki font isn't in core yet, these issues are related but could be separate too.",1403727638,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 141973 had a related patch set uploaded by Bartosz Dziewoński:
+Linker: Add CSS classes to external links to some protocols/filetypes
+
+https://gerrit.wikimedia.org/r/141973",1403727424,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"I've looked at this again now that things have cooled down. I still do not like this solution, and I still like this alternative proposed a long time ago:
+
+(In reply to Bartosz Dziewoński from comment #13)
+> (In reply to Jon from comment #11)
+> > That aside use of a single class .link-https rather than a
+> > combination of class .link-https, div#content a.external[href
+> > ^=""https://""] would be preferable for a variety of reasons
+> > readability, maintainability, reduced file size... are you really
+> > telling me this is not a no-brainer?
+> 
+> Using the classes as you proposed does seem sane and mostly non-troublesome
+> (apart from the classic caching issues). I am perfectly fine with doing that
+> (as long as I'm not the one who will have to jerry-rig the Parser).
+
+So I looked at the Parser, or in fact the Linker, and doing this is actually amusingly trivial. Pity no one did this the first time around.
+
+A patch will follow momentarily.",1403727235,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Regardless of everyone's opinions the patch has been merged, so this is fixed.",1399940828,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 124618 merged by jenkins-bot:
+Follow-up: If985b16c – Vector external link change release notes
+
+https://gerrit.wikimedia.org/r/124618",1397145263,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 124618 had a related patch set uploaded by Jdlrobson:
+Follow up to If985b16c4f682d737683597ed80951c6d6644c8f
+
+https://gerrit.wikimedia.org/r/124618",1396972855,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"I can tell you that it's customary on sites like Reddit to add a ""PDF warning"" to a description of a link that points directly to a PDF document. (Other file types don't really come up often enough for such a custom to develop.)",1396952733,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #37)
+> As stated above external links were removed as part of the typography beta
+> feature. Actually, not a single person wrote about this on the talk page
+> (https://www.mediawiki.org/wiki/Talk:Typography_Update) during the 6 months
+> it was live. This evidence leads me to believe that they are /not/ important
+> and it is the basis for removing them.
+
+However, anyone who used a wiki (like English Wikipedia, which has such rules at https://en.wikipedia.org/wiki/MediaWiki:Common.css and https://en.wikipedia.org/wiki/MediaWiki:Vector.css) with local rules would not have seen any difference.
+
+Thus, it's a valid question how many people who used the Beta feature saw a visible change to the main (PDF and HTTPS seem like the biggies for article space, with the audio being used a decent amount, but not as much, but I don't have data) icons.  If a tiny number were affected, then ""not a single person wrote about this"" is not a convincing argument.
+
+I think English Wikipedia Beta users saw neither change, since PDF is at [[MediaWiki:Common.css]] and HTTPS is at [[MediaWiki:Vector.css]].
+
+However, it is certainly true that we are not going to be able to do dedicated research for every change, and this may be one such example.  I agree that this feature affects both readers and editors, and we need to consider the impact on both.  Having tools to do A/B tests on readers would certainly help, but it wouldn't solve everything.
+
+It can definitely be iterated on regardless.  In particular (if we proceed without the format-specific icons), there should be at least one follow-up change to do the following:
+
+1. Remove obsolete FIXME comment from externalLinks.css.
+2. Release notes
+3. Fixes from https://gerrit.wikimedia.org/r/#/c/123817/3/skins/vector/components/externalLinks.less .  Note the point about div#content on the left, and might as well do the formatting fix on the right (space before right paren) since there needs to be a commit anyway.
+
+Marking open again and assigning to Jon.",1396921020,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #37)
+> Commits and reverts are cheap.
+
+No. There's almost no evidence to suggest that commits and reverts of this nature are cheap. There's a ton of evidence to suggest that commits and reverts of this nature are expensive (in terms of community time and developer time).
+
+> We have a huge editor decline and here we are arguing about some icons next to
+> links.
+
+No fearmongering here, please. The stated editor decline is dubious, bordering on spurious. This bug is strictly about ""some icons next to links."" You (Jon) are sidetracking the technical conversation with FUD about an editor decline. Focus on the issue at hand, please.",1396920224,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jared Zimmerman (WMF) from comment #36)
+> (In reply to Isarra from comment #34)
+> We did a beta feature, it was called typography refresh, and little to no
+> feedback (negative or positive) addressed the removal of these icons, that
+> was the impetus for moving forward with this as a simple patch. 
+
+Lumping multiple changes together and then testing the entire pile is problematic by its very nature: it can become very difficult to differentiate between the effects of different changes, and getting meaningful feedback on any specific one often becomes very difficult. Thus you can wind up with an overall positive response despite individual aspects which significantly detract from the experience, and then wind up thinking those, too, are positive when they really aren't (or visa versa).
+
+Thus, to say anything specific about the external link icons and potential changes, I would suggest that you need to test or otherwise investigate those specifically, and distinctly, first. Jon's not wrong that this is a relatively minor thing, but while that means a full-on battery of tests probably isn't actually necessary here, like with any other change, discussion is definitely in order in order to establish some sort of consensus as to what best serves the users. So here we are. Discussing. Or we were, before the entire thing got a wee bit sidetracked.",1396918242,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #37)
+> The world is not breaking. The world of Vector is just going through
+> turbulence.
+
+I didn't mean to point fingers at any specific event, and wasn't actually thinking of typo refresh when making my comment (Or the actual subject of this bug. Oh well guess this bug is pretty hijacked). I wanted to address in the abstract the attitude in comment 23 of making changes willy nilly (which I flippantly phrased as ""breaking the world"") and then iterating on them until people like them (or cynically: until they become fait accompli), as being a good way to get feedback. I think its a good way to piss off people, and self-justify changes via confirmation bias.
+
+
+> 
+> The fact we have to actively discuss trivial changes like this concerns me
+> greatly. We have a huge editor decline and here we are arguing about some
+> icons next to links.
+
+I'm not sure I follow. Not asking editors for feedback on changes is somehow going to increase editor retention?
+
+> 
+> Also I think you mean /editors/ when you say /readers/ here. I think most
+> /readers/ care simply if a link will take them to an external site or not.
+
+I was responding as if ""readers"" = Users without an account who only read. For the actual change I think both groups care. My comment was aimed solely at attitudes for getting feedback. I'm not actually that concerned about the actual change",1396916621,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,I'm just going to leap in here in the middle of this heated discussion and change the title of the bug to be grammatically correct. It's been bugging me. Sorry.,1396915976,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"The world is not breaking. The world of Vector is just going through turbulence.
+
+As stated above external links were removed as part of the typography beta feature. Actually, not a single person wrote about this on the talk page (https://www.mediawiki.org/wiki/Talk:Typography_Update) during the 6 months it was live. This evidence leads me to believe that they are /not/ important and it is the basis for removing them.
+
+If this proves to be wrong, then we react and restore/amend it, it's no big deal. Commits and reverts are cheap.
+
+The fact we have to actively discuss trivial changes like this concerns me greatly. We have a huge editor decline and here we are arguing about some icons next to links.
+
+Also I think you mean /editors/ when you say /readers/ here. I think most /readers/ care simply if a link will take them to an external site or not.",1396915738,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Isarra from comment #34)
+We did a beta feature, it was called typography refresh, and little to no feedback (negative or positive) addressed the removal of these icons, that was the impetus for moving forward with this as a simple patch. 
+
+If you read on the Beta Features page, you'll see that Beta Features should not be only subtractive in nature, e.g. packaging up the removal of these icons as its own feature makes very little sense. — https://www.mediawiki.org/wiki/Beta_Features/Package",1396915523,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"
+> 
+> Its relevant because asking for feedback on ""the usual channels"" completely
+> omits the target user, when the target users is a reader. Jon's point that
+> we can do it and then iterate speaks to the fact that it is one of our only
+> ways to get reader feedback. To roll the change out publicly then iterate.
+> We can get better at this eventually, but at the current juncture, I think
+> this is a sound plan based on our infrastructure for eliciting feedback from
+> readers and others who aren't aware of, or participate in ""the usual
+> channels""
+> 
+> Hope that makes sense.
+
+breaking the world, and then seeing who complains isn't really a good way to get feedback from readers. First off, most people who complain aren't going to be ""readers"" they are going to be active users who are familiar with the regular channels. If you actually get readers angry enough that they figure out how to complain, you've probably massively screwed up the site. Second, that's prone to a massive confirmation bias of ""Well nobody or not that many people complained out of a group of people who don't know how to complain, therefore it must be a good idea""
+
+I really think this is an extraordinarily dangerous line of reasoning to go down.",1396914965,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"In reply to Jared Zimmerman (WMF) from comment #31)
+> Its relevant because asking for feedback on ""the usual channels"" completely
+> omits the target user, when the target users is a reader. Jon's point that
+> we can do it and then iterate speaks to the fact that it is one of our only
+> ways to get reader feedback. To roll the change out publicly then iterate.
+> We can get better at this eventually, but at the current juncture, I think
+> this is a sound plan based on our infrastructure for eliciting feedback from
+> readers and others who aren't aware of, or participate in ""the usual
+> channels""
+
+I would think that 'users' here would include readers and editors both, and even then, editors often know their readers better than one might expect (such as by talking to them, or being them). So talking to the editors is probably exactly the right place to start. They could tell you things like the fact that some of these external link styles, such as IRC, will never appear in article space (on a non-technical project, anyway - mw.org or archwiki and similar probably have quite a few irc links in various articles), but are often used in project and user space (so changes to that style would be purely editor-facing on projects like Wikipedia, not reader). Or that readers often complain when <blah> or have trouble with <blah>.
+
+And there is also ample infrastructure in place to test potential changes, is there not? For instance you could do:
+* A/B tests to determine if readers are less likely to click on external if they are or aren't visibly marked as whatever kind of link they are. 
+* Scripted tests on usertesting.com to gain insight into possible reactions to unexpected pdfs, audio files, IRC links, etc vs regular external links, and to the external link icons themselves when they are used, such as if they even figure out what they mean.
+* A betafeature for users to see if removing the special icons affects their workflows, or if they prefer it outright.
+
+If there is a problem, you should be able to prove it without just deploying it first and asking questions later. Also what Derk-Jan said.",1396914365,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Users of a product are aware (although not always consciously) of the absence of something equally well as the awareness of and existence of something (cruft). A user does not need to be aware of something, an ""absence,"" say to be aware that a product is better because of design choices to remove, and simplify. 
+
+
+""Good design is as little design as possible — Less is more – because it concentrates on the essential aspects and the products are not burdened with non-essentials. Back to purity, back to simplicity"" —Dieter Rams
+
+""Perfection is achieved perfection not when there is nothing left to add, but when there is nothing left to take away"" –Antoine de Saint-Exupery",1396914062,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Then again, can you expect a casual reader to ever appreciate that which is not there? A removal like this is hard to notice, because most links don't have these icons.
+
+Your proposal is basically: Ah, people asked for this 10 years ago. but there is a bunch of annoying css rules, so let's remove them and wait how long it takes for people to ask if they can have the feature back. This feature contributes to the rule of least astonishment, and you are removing it without considering replacing it with an alternative.
+
+I find that somewhat presumptuous if i'm honest. But then again, I thought messing with fonts was a dangerous plan and that turned out just splendid, so what do I know....",1396913306,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Isarra from comment #28)
+> And there is a right way to make change happen - by proposing changes and
+> getting feedback. By implementing this, you have inherently proposed it, and
+> now you are getting feedback. Whether or not they should be merged depends
+> on what consensus is established either here or in other appropriate
+> channels; we have these channels for a reason.
+
+Its relevant because asking for feedback on ""the usual channels"" completely omits the target user, when the target users is a reader. Jon's point that we can do it and then iterate speaks to the fact that it is one of our only ways to get reader feedback. To roll the change out publicly then iterate. We can get better at this eventually, but at the current juncture, I think this is a sound plan based on our infrastructure for eliciting feedback from readers and others who aren't aware of, or participate in ""the usual channels""
+
+Hope that makes sense.",1396911689,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jared Zimmerman (WMF) from comment #29)
+> Isarra, I've mentioned it before and I'll mention it here again, that
+> process makes total sense for editor or logged-in user features. It doesn't
+> make sense for reader facing features, as these users are not part of this
+> conversation.  
+> 
+> You know how to do cross site links but many users do not, and the systems
+> are not smart enough to automatically convert them in many cases.
+
+I agree, new users often don't appreciate the significance of many features. But how is this relevant to the matter at hand?",1396911306,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Isarra, I've mentioned it before and I'll mention it here again, that process makes total sense for editor or logged-in user features. It doesn't make sense for reader facing features, as these users are not part of this conversation.  
+
+You know how to do cross site links but many users do not, and the systems are not smart enough to automatically convert them in many cases.",1396910718,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #26)
+> To be clear, we still show an external link icon.
+> Yes I suspect it may annoy people but this can be easily remedied. Change is
+> also a trend that needs to start.
+
+And there is a right way to make change happen - by proposing changes and getting feedback. By implementing this, you have inherently proposed it, and now you are getting feedback. Whether or not they should be merged depends on what consensus is established either here or in other appropriate channels; we have these channels for a reason.
+
+(In reply to Jared Zimmerman (WMF) from comment #27)
+> Isarra, from a technical perspective a PDF hosted on commons while I'm on
+> wikipedia is ""leaving the site"" but this isn't how most readers or casual
+> editors see it. That was my point. I appreciate your point about it from a
+> literal perspective.
+
+External links appear if the external link format is used, regardless of where the link points. They are only supposed to be for links that go off the site (in other words, ones that are 'external'); we normally use wikilinks (ones formatted [[like this]]) to link to local and sister project pages, which do not result in external link formatting.
+
+For more information about how links work in MediaWiki, please see https://www.mediawiki.org/wiki/Links",1396910489,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Isarra, from a technical perspective a PDF hosted on commons while I'm on wikipedia is ""leaving the site"" but this isn't how most readers or casual editors see it. That was my point. I appreciate your point about it from a literal perspective.",1396903714,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"To be clear, we still show an external link icon.
+Yes I suspect it may annoy people but this can be easily remedied. Change is also a trend that needs to start.",1396903563,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jared Zimmerman (WMF) from comment #23)
+> From my understand the external/file format link icons are only relevant
+> when you are actually leaving the site, or when it would cause your browsers
+> to download a file rather than loading it in some kind of built in player,
+> either on site or in-browsers. The original code for this I assume was
+> created prior to mediawiki being able to natively handle many of these file
+> formats. 
+
+Generally external links do leave the site. This is what 'external link' means.
+
+(In reply to Jon from comment #24)
+> That said, I am happy to deal with any after effects of this change. I'd
+> hope such a drastic change would surface the icons that are important.
+> 
+> I think the removal of them although somewhat extreme, will make it clearer
+> and easier to restore ones that are vital.
+
+I would suggest that breaking everything and then seeing what people complain about the most may not be the best way to determine what is important. Yes, it may work, but more than anything it's probably just going to annoy people, and needlessly alienating users is a trend that needs to stop, not continue.",1396902884,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Apologies if I misunderstood and this had been the agreement.
+
+That said, I am happy to deal with any after effects of this change. I'd hope such a drastic change would surface the icons that are important.
+
+I think the removal of them although somewhat extreme, will make it clearer and easier to restore ones that are vital.
+
+A lot of these icons may be better done in something like MediaWiki:Vector/Monobook/Common.css on a per project basis anyhow.",1396902298,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"From my understand the external/file format link icons are only relevant when you are actually leaving the site, or when it would cause your browsers to download a file rather than loading it in some kind of built in player, either on site or in-browsers. The original code for this I assume was created prior to mediawiki being able to natively handle many of these file formats. 
+
+That said I think most if not all of these are no longer needed and confuse many users. Overall I would urge us to move towards simplicity when it comes to links, designating only links that take you out of the WMF sites, and links that point to non-existent articles. 
+
+If knowing target file types is relevant to a small subset of users I've argue that this code should be gadgetized by someone who cares to retain this feature.",1396900073,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to Jon from comment #14)
+> Great. I'm agnostic about killing the icons or not. My main goal is to start
+> cleaning up and improving all the desktop CSS.
+
+I thought we'd agreed to clean up the expensive CSS, and not to delete the icons (which is what https://gerrit.wikimedia.org/r/123817 does).
+
+:/",1396809360,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 123817 merged by jenkins-bot:
+Vector: Simply style external links
+
+https://gerrit.wikimedia.org/r/123817",1396736501,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"If they're not affected, they're not representative. It doesn't sound rational to mention them in the commit message.",1396631124,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"I don't understand the question/problem. All wikis got the beta features experiment.
+
+If those wiki's have local icons, that is fine, they won't be effected by this change to Vector, and will get a performance boost by having a simpler set of css selectors for these icons.",1396630023,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"> During the typography experiment, these were removed, no one raised this as an 
+> issue during the 5 months it was live, suggesting that explicit pdf icons etc
+> are not as useful as we like to believe.
+
+How many of the (English) wikis in question did not have *local* icons? How do you know how many were actually affected by these changes?",1396629807,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Change 123817 had a related patch set uploaded by Jdlrobson:
+Vector: Simply style external links
+
+https://gerrit.wikimedia.org/r/123817",1396625023,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"See http://lists.wikimedia.org/pipermail/wikitech-l/2013-October/072642.html
+
+Main highlights:
+
+* We shouldn't confuse English Wikipedia's overrides with code in core.  However, there is room to clean that up, even if they want to keep a different icon from core (e.g. moving the Modern-specific code to Modern.css).
+* I like the idea of doing it in the parser, but it obviously requires more testing than a CSS change.  To expand on what I said in the email, we could do something generic like 'mw-link-extension-pdf'.  We would need to decide whether to do it for all extensions, or just the ones where core styles it.
+* We could consider using the Commons PDF icon in core, if it's freely licensed (have not investigated).",1382663777,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #14)
+> Great. I'm agnostic about killing the icons or not. My main goal is to start
+> cleaning up and improving all the desktop CSS.
+
+Sensible thing to do, indeed. Just bear in mind caching issues. >.<",1380781960,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,Great. I'm agnostic about killing the icons or not. My main goal is to start cleaning up and improving all the desktop CSS.,1380661301,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #11)
+> That aside use of a single class .link-https rather than a
+> combination of class .link-https, div#content a.external[href
+> ^=""https://""] would be preferable for a variety of reasons
+> readability, maintainability, reduced file size... are you really
+> telling me this is not a no-brainer?
+
+Using the classes as you proposed does seem sane and mostly non-troublesome (apart from the classic caching issues). I am perfectly fine with doing that (as long as I'm not the one who will have to jerry-rig the Parser).
+
+Killing the icons as suggested in comment 1 is a completely different thing and, apart from what I mentioned in comment 7, I will vehemently oppose doing it.
+
+
+(In reply to comment #11)
+> If you really feel the need for a citation check out:
+> http://stevesouders.com/efws/css-selectors/csscreate.php
+
+Either I am unable to figure it out, or it doesn't work. Reflow time is 0 for me no matter what I do. ""page load time"" is measuring the speed of my connection if anything.
+
+(In reply to comment #12)
+> CSS rule efficiency table:
+> http://csswizardry.com/2011/09/writing-efficient-css-selectors/
+
+This looks interesting; sorry, I don't have time to dig into it right now, but hopefully I will later. (Hopefully it's still relevant - it was apparently written in 2011, and two years is like a few decades at least ;) )",1380661163,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,CSS rule efficiency table: http://csswizardry.com/2011/09/writing-efficient-css-selectors/,1380657589,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #9)
+> (In reply to comment #8)
+> > The CSS is pretty ridiculous. Let's not forget that CSS parses from the
+> > rightmost rule so something like a.external[href ^=""news:""] can be a pretty
+> > expensive operation.
+> 
+> [citation needed]. I don't see why would it be particularly more expensive
+
+If you really feel the need for a citation check out:
+http://stevesouders.com/efws/css-selectors/csscreate.php
+
+That aside use of a single class .link-https rather than a combination of class .link-https, div#content a.external[href ^=""https://""] would be preferable for a variety of reasons readability, maintainability, reduced file size... are you really telling me this is not a no-brainer?",1380657176,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #9)
+> (In reply to comment #8)
+> > The CSS is pretty ridiculous. Let's not forget that CSS parses from the
+> > rightmost rule so something like a.external[href ^=""news:""] can be a pretty
+> > expensive operation.
+> 
+> [citation needed]. I don't see why would it be particularly more expensive
+> than
+> any of the hundreds of other rules we have. Assuming that the hypothetical
+> browser does indeed naively match from the right side always, [href^=""news:""]
+> will immediately not match (most elements don't even have a href attribute)
+> and
+> the ten or so of such rules should not be noticeable.
+
+Afaik selector engines have quick lookup maps for IDs, classes and elements. In the case of "".mw-link-pdf"" that is a very quick lookup.
+
+In the case of ""#bodyContent a.external[href=..]"" it is a lookup for elements of 'a', then for each the classname and the attribute is matched, and then it recursively does a parent check until it finds #bodyContent or the document element.
+
+In theory it could optimise if it had a quick lookup for elements having a certain attribute. But afaik they don't have that, and even if they did, I isn't more efficient per se, cause then the post-check would have to verify tag name and class name for each.
+
+Either way, none of this in particular is bad, it's the whole package of:
+* A very strong selector (#bodyContent)
+* A parent selector
+* Both element and class name (should never be used together)
+* Additional attribute matching and string operations on that
+* Hardcodes details that (other) stylesheets should not have to know or hardcode, thus causing maintenance issues (e.g. the fact that it is an <a>, and is inside #bodyContent. The container can change, and links might be wrapped for presentational reasons)
+
+Up sides of using a simple class:
+* Faster query (one could argue about how much, but it is certainly faster)
+* Support for older browsers (this is not a priority though, since all our grade A browsers support it, and it's a minor enhancement with graceful degradation)
+* Easier to extend from other components as there is no need to have any knowledge about implementation details (container element, tag name etc.)",1380569631,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #8)
+> The CSS is pretty ridiculous. Let's not forget that CSS parses from the
+> rightmost rule so something like a.external[href ^=""news:""] can be a pretty
+> expensive operation.
+
+[citation needed]. I don't see why would it be particularly more expensive than any of the hundreds of other rules we have. Assuming that the hypothetical browser does indeed naively match from the right side always, [href^=""news:""] will immediately not match (most elements don't even have a href attribute) and the ten or so of such rules should not be noticeable.",1380567205,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"The CSS is pretty ridiculous. Let's not forget that CSS parses from the rightmost rule so something like a.external[href ^=""news:""] can be a pretty expensive operation. These rules should be killed with fire in favour of specific classes like link-pdf if needed.
+
+I don't care if we kill or keep rules I just want these rules to die and the CSS in general to be cleaned up.",1380561554,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"Per Isarra and Quiddity, I think that the only ones that should be killed are the HTTPS and FTP ones. That CSS is not ridiculous, it's just a little uncool.",1380371064,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #5)
+> My gut says remove them all esp. the https links, as @Isarra mentioned the
+> only
+> one that seems to make any real sense is links that point to files, like
+> PDFs,
+> however  internal (Commons) links have their own viewer. External PDFs seem
+> like the only file that marking their links seems relevant in any way. Most
+> modern browsers have built-in PDF renders so even the days of PDFs being
+> treated special is soon becoming irrelevant. 
+> 
+
+Isarra mentioned mailto and IRC links too, which I'd agree are instances where the icon is useful. 
+
+The audio/video icons are also good to have, per principle of least astonishment (eg, someone adds a link to a loud .wav file into an article's external links, and someone else in a quiet office clicks on it).
+
+They also help editors to notice that these uncommon link types are present, and hence to check whether they're really suitable/wanted or not. (If I see an audio-file icon, I often click it to check for spam/vandalism).
+
+
+> My recommendation would be to remove all special formatting other than
+> wikilinks vs external links. 
+> 
+> If we could determine and mark wikilinks that are to other sister projects,
+> I'd recommend they be treated as regular wikilinks as well.
+
+Interwiki links (everything in https://meta.wikimedia.org/wiki/Interwiki_map )
+are already styled with a slightly-lighter blue, via class ""extiw"" (external interwiki) located in https://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/skins/common/commonElements.css?view=markup and skins/monobook/main.css",1380345239,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"My gut says remove them all esp. the https links, as @Isarra mentioned the only one that seems to make any real sense is links that point to files, like PDFs, however  internal (Commons) links have their own viewer. External PDFs seem like the only file that marking their links seems relevant in any way. Most modern browsers have built-in PDF renders so even the days of PDFs being treated special is soon becoming irrelevant. 
+
+My recommendation would be to remove all special formatting other than wikilinks vs external links. 
+
+If we could determine and mark wikilinks that are to other sister projects, I'd recommend they be treated as regular wikilinks as well.",1380340657,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #1)
+> Honestly I'd recommend just killing these link icons outright...
+
+One of the things to consider is when and where the links are actually used, and if special treatment is even sensible anymore. 
+
+Generally we'd probably only want special icons for things that are both fairly commonly used and where the browser reaction would be significantly different from general browsing - for things like PDFs, which are often used for sources, that can open up in a new window or rearrange the tab depending on browser, or mailto and IRC which often send the request out of the browser entirely and open a new window. Users do like warning when it comes to that sort of thing, indeed.
+
+Whereas we probably don't want anything special for things like https, ftp, etc where the browser just opens it like normal, especially since for instance https is becoming more and more common as the default...",1380323575,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #1)
+> Honestly I'd recommend just killing these link icons outright...
+
+Some of the other icons could /possibly/ be removed without screaming. 
+
+But the PDF icon is important. Users get frustrated when they click a PDF without warning.
+
+(The only alternative is [[Template:PDFlink]] which makes article/citation code more complicated, so that's not good.)",1380179977,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,"(In reply to comment #1)
+> Honestly I'd recommend just killing these link icons outright...
+
+This is a design question, I think. Adding the Bugzilla keyword accordingly.",1380173289,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+Large number of CSS rules for external links,Honestly I'd recommend just killing these link icons outright...,1380131401,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-a4ziafykxquhrim4wrm3,task_subcomment,NA
+"VisualEditor: this.referenceSurface should be a Surface, not a SurfaceWidget","In ve.ui.MWReferenceDialog, this.referenceSurface changed from being a Surface to a SurfaceWidget. I noticed this because I rebased some old code that used this.referenceSurface.getModel() and broke, but this seems to have happened a while ago with the introduction of SurfaceWidget.
+
+When a variable name is 'fooSurface', it should be a Surface, not something else. In particular, you shouldn't have to do this.referenceSurface.getSurface() to get the surface.
+
+The same applies to this.captionSurface in ve.ui.MWMediaEditDialog.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1380077400,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dlrbz5yirqhdlb5ixx32,task_description,resolved
+"VisualEditor: this.referenceSurface should be a Surface, not a SurfaceWidget","These are now fooTarget instace of TargetWidget, however TargetWidget behaves like target, not a target wrapper, so this bug is resolved.",1533388170,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dlrbz5yirqhdlb5ixx32,task_subcomment,NA
+VisualEditor: Inserting a reference breaks up annotations around it,"When you insert a reference in the middle of a bolded word, the reference itself doesn't receive a bold annotation, and so the resulting text is something like '''He'''<ref name=""hello"" />'''llo''', with the bold breaking around the reference.
+
+When we insert inline nodes like references from the UI, they should take annotations. This is probably a wider problem beyond just references.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380074640,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-y3zmidmzskha5h7ldgcc,task_description,open
+VisualEditor: Inserting a reference breaks up annotations around it,See bug 48720.,1382626276,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-y3zmidmzskha5h7ldgcc,task_subcomment,NA
+VisualEditor: Inserting a reference breaks up annotations around it,"(In reply to comment #2)
+> Also, I'm not sure this is desirable behaviour.
+
+But we are. :-)",1380755694,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y3zmidmzskha5h7ldgcc,task_subcomment,NA
+VisualEditor: Inserting a reference breaks up annotations around it,"Also, I'm not sure this is desirable behaviour.",1380472840,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-y3zmidmzskha5h7ldgcc,task_subcomment,NA
+VisualEditor: Inserting a reference breaks up annotations around it,"The dialogs generate insertion transactions directly with newFromInsertion, and have no insertion annotation logic.",1380279978,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-y3zmidmzskha5h7ldgcc,task_subcomment,NA
+VisualEditor: MWExtensionNode/GeneratedContentNode should avoid emitting 'rerender' twice when rendering <img>s,"ce.MWExtensionNode.onParseSuccess contains the following code:
+
+	// Rerender after images load
+	this.$.find( 'img' ).on( 'load', ve.bind( function () {
+		this.emit( 'rerender' );
+	}, this ) );
+
+Problems:
+* Why is this in MWExtensionNode? Shouldn't it just be in GCNode?
+* This potentially emits multiple rerender events, one for each image
+* The first rerender event has already been emitted because we've already resolved the promise and attached the nodes to the DOM
+
+What we should really do is attach the nodes somewhere else (where?) so that the images load, then reattach them to a wrapper and resolve the promise with that. That way we only emit rerender once, and we correctly only resolve the promise once everything has actually loaded.
+
+In practice, this means the math inspector moves around twice after typing LaTeX in certain cases: once because of the 'rerender' event caused by the <img> tag being put on the page (at which point it measures 0x0), and once because of the 'rerender' event caused by the image actually loading (at which point it measures correctly).
+
+Open questions:
+* How does this work for images with invalid/unavailable sources?
+* Really what we care about here is the dimensions of the images. If those are known, we can render the node without its dimensions changing later
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380072600,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-d2izuitwfayrxbyhcjil,task_description,resolved
+VisualEditor: MWExtensionNode/GeneratedContentNode should avoid emitting 'rerender' twice when rendering <img>s,https://gerrit.wikimedia.org/r/#/c/86167/ fixes this,1380232745,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-d2izuitwfayrxbyhcjil,task_subcomment,NA
+"VisualEditor: ce.GeneratedContentNode.generateContents() should be static, so we can cache based on config objects alone","Right now, GCNode caching uses both the model hash and the hash of the config object. However, when properties in the config override properties in the model, the preview of a change and the new model node after the actual change will be the same but have different hashes (because the model is different, and because in the second case the config object is empty/undefined).
+
+We should make generatedContents() static, so it can't inspect the model or any object state, and have a function that provides the default config that is then used to extend the provided config. That way we don't end up duplicating things in cache and rendering things twice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1380071580,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pvtq3ysdgbspx2ubicva,task_description,open
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Currently http://korma.wmflabs.org/browser/its-repos.html shows that the Bugzilla products scanned are MediaWiki, All extensions, VisualEditor and Parsoid. However, this list must be in sync with http://korma.wmflabs.org/browser/scm-repos.html - which in turn is synced with https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects
+
+Let's update that wiki page with the relevant products / components. A 100% match is probably impossible, but a 90% (or so) should be feasible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49744",1379952300,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_description,resolved
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"(In reply to comment #6)
+> ==Core Extensions==
+> Don't want to spend too much time going through the list and syncing with
+> https://bugzilla.wikimedia.org/editcomponents.
+> cgi?product=MediaWiki%20extensions
+> however noteworthy naming differences from the top of my head:
+
+Currently korma lists all the extensions in a single project. This is good enough for now, but for the Bugzilla Response Time KPI [1] we will need to be more precise:
+
+* Including only the key projects.
+* Treating each component separately, just like we do with code repos.
+
+[1] https://www.mediawiki.org/wiki/Community_metrics#Bugzilla_response_time",1382560830,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Ok guys, you have the viz in:
+
+http://korma.wmflabs.org/browser/its-repos.html",1382549565,PHID-USER-lepsd737p6wqwsowcou2,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Great, I have programmed for adding to the report the next repos:
+
+Analytics > Kraken: https://bugzilla.wikimedia.org/buglist.cgi?product=analytics&component=kraken&list_id=243545
+Datasets > Webstatscollector: https://bugzilla.wikimedia.org/buglist.cgi?product=datasets&component=Webstatscollector&list_id=243568
+Analytics > Wikimetrics https://bugzilla.wikimedia.org/buglist.cgi?product=analytics&component=wikimetrics
+Analytics > Wikistats https://bugzilla.wikimedia.org/buglist.cgi?product=analytics&component=wikistats
+Analytics > Limn https://bugzilla.wikimedia.org/buglist.cgi?product=analytics&component=limn
+Analytics > General/Unknown https://bugzilla.wikimedia.org/buglist.cgi?product=Analytics&component=General%2FUnknown
+Commons App > iOS (iPhone or iPad) https://bugzilla.wikimedia.org/buglist.cgi?product=Commons%20App&component=iOS%20%28iPhone%20or%20iPad%29
+Wikipedia App https://bugzilla.wikimedia.org/buglist.cgi?product=wikipedia%20app
+Wiki Loves Monuments > Mobile https://bugzilla.wikimedia.org/buglist.cgi?product=Wiki%20Loves%20Monuments&component=Mobile
+Wikimedia > Continuous integration https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=Continuous%20integration
+Wikimedia > DNS https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=dns
+Wikimedia > OTRS https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=otrs
+Wikimedia > Bugzilla https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=bugzilla
+Wikimedia > wikibugs IRC bot https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=wikibugs%20IRC%20bot
+Wikimedia > Blog https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=blog
+Wikimedia > Fundraising: Misc. https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=Fundraising%3A%20Misc.
+Wikimedia > Fundraising: Requirements https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=Fundraising%3A%20Requirements
+Tools > code-utils https://bugzilla.wikimedia.org/buglist.cgi?product=tools&component=code-utils
+Tools > mw-dumper https://bugzilla.wikimedia.org/buglist.cgi?product=tools&component=mwdumper
+Pywikibot > * https://bugzilla.wikimedia.org/buglist.cgi?product=Pywikibot
+MediaWiki-Vagrant > * https://bugzilla.wikimedia.org/buglist.cgi?product=MediaWiki-Vagrant
+Wikimedia Labs > tools https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia%20labs&component=tools
+openZIM > * https://bugzilla.wikimedia.org/buglist.cgi?product=openZIM
+Wikimedia > Quality Assurance https://bugzilla.wikimedia.org/buglist.cgi?product=wikimedia&component=quality%20assurance
+
+I have checked all of them and works. So tomorrow you should have the new info.",1382519999,PHID-USER-lepsd737p6wqwsowcou2,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,Yes!,1382370607,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Ok guys, is this ready to start downloading all those bugzilla product and components and adding them to the korma browser?",1382353678,PHID-USER-lepsd737p6wqwsowcou2,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"I guess we all know that there are no clear 1:1 mapping is possible, but instead 1:n or n:1. I just hope to avoid n:n. :)
+
+
+[[wikitech:Key_Wikimedia_software_projects]] -- Bugzilla product > component
+
+
+==Analytics==
+analytics/kraken                 --  Analytics > Kraken
+analytics/webstatscollector      --  Datasets > Webstatscollector
+analytics/wikimetrics            --  Analytics > Wikimetrics
+analytics/wikistats              --  Analytics > Wikistats
+github.com/wikimedia/limn        --  Analytics > Limn
+analytics/*                      --  Analytics > General/Unknown
+==Mobile apps==
+apps/android/commons 
+github.com/wikimedia/Commons-iOS --  Commons App > iOS (iPhone or iPad)
+github.com/wikimedia/WikipediaMobile  --  Wikipedia App
+github.com/wikimedia/WikipediaMobileFirefoxOS  --  Wikipedia App
+github.com/wikimedia/WLMMobile   -- Wiki Loves Monuments > Mobile
+==Integration==
+*                                --  Wikimedia > Continuous integration
+==Operations==
+Hard to define, mostly in rt.wikimedia.org, some in Bugzilla under ""Wikimedia > General"" with keyword ""ops"".
+operations/dns                   --  Wikimedia > DNS
+operations/software/otrs         --  Wikimedia > OTRS
+==Wikimedia==
+====Bugzilla====
+wikimedia/bugzilla/modifications --  Wikimedia > Bugzilla
+wikimedia/bugzilla/triagescripts --  Wikimedia > Bugzilla
+wikimedia/bugzilla/wikibugs      --  Wikimedia > wikibugs IRC bot
+====Communication====
+wikimedia/communications/WMBlog  --  Wikimedia > Blog
+====Fundraising====
+Mostly using CiviCRM; related components in Bugzilla are:
+                             --  MediaWiki extensions > FundraiserLandingPage
+                                 --  MediaWiki extensions > FundraiserPortal
+                                 --  Wikimedia > Fundraising Misc.
+                                 --  Wikimedia > Fundraising Requirements
+==MediaWiki misc==
+mediawiki/php/FastStringSearch
+    mediawiki/php/NativePreprocessor
+    mediawiki/php/luasandbox     --  MediaWiki extensions > Scribunto
+    mediawiki/php/wikidiff2      --  MediaWiki extensions > wikidiff2
+mediawiki/tools/code-utils       --  Tools > code-utils
+mediawiki/tools/mwdumper         --  Tools > mw-dumper
+==Pywikibot==
+pywikibot/*                      --  Pywikibot > *
+==Other==
+mediawiki/vagrant                --  MediaWiki-Vagrant > *
+labs/toollabs                    --  Wikimedia Labs > tools
+openzim                          --  openZIM > *
+qa/browsertests                  --  Wikimedia > Quality Assurance
+==Core Extensions==
+Don't want to spend too much time going through the list and syncing with https://bugzilla.wikimedia.org/editcomponents.cgi?product=MediaWiki%20extensions however noteworthy naming differences from the top of my head:
+
+PageTriage                       --  MediaWiki extensions > PageCuration
+Parsoid                          --  Parsoid > *
+SyntaxHighlight_GeSHi     --  MediaWiki extensions > SyntaxHighlight (GeSHi)
+VisualEditor                     --  VisualEditor > *
+Wikibase                         --  MediaWiki extensions > WikidataRepo",1382025323,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Andre, if you could point to the Bugzilla product/component of each project at https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects that would be perfect!",1381773164,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"(If there is something I can specifically help with as Bugzilla admin, please tell me what I need to do for you folks.)",1381764843,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Quim, for the Bugzilla components mapping, do you have some plan in mind for gathering the info from Wikimedia Community? Maybe we can start doing the mapping of the more clear components, but it there is a complete process to cover all of them, much better!",1381760730,PHID-USER-lepsd737p6wqwsowcou2,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Yes Quim, we can scan only components.",1380184604,PHID-USER-lepsd737p6wqwsowcou2,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Bugzilla data scanned for tech metrics must be aligned with repos scanned,"Álvaro, can MetricsGrimoire scan only specific components of a Bugzilla product? The reason to ask is that, ideally, we wouldn't scan the whole MediaWiki Extension product but only the relevant components.",1379952721,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-rmkl7hs2ktj4cx7nvrl4,task_subcomment,NA
+Broken wikitext with bold inside and outside a label wrongly interpretted as correct by Parsoid,"**Author:** `jmichrina`
+
+**Description:**
+Example:
+Line from ""International_Air_Transport_Association_airport_code""
+
+DFW for Dallas–Fort Worth, DTW for Detroit–Wayne County, RDU for Raleigh–Durham, MSP for Minneapolis–St. Paul and LBA for Leeds Bradford (Airport).
+
+Line appears correctly formatted in editor [caps represent bold]:
+dfw for Dallas-Fort Worth, dtw for DetroiT-Wayne county, rdu for Raleigh-DUrham, msp for Minneapolis-St. Paul and lba for Leeds Bradford (Airport).
+
+Line appears incorrect on page [caps represent bold]:
+dfw for DALLAS-FORT WORTH, stw for dEtROIT-wAYNE COUNTY, rdu for RALEIGH-DURHAM, msp for mINNEAPOLIS-sT. pAUL and lba for LEEDS BRADFORD (AIRPORT).
+
+Note that the correct version appears in the editor even after it's saved.
+
+Possibly related to bug 53208, but I didn't have time to verify.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1379880120,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-geakkjwdr2b6k3vobqx7,task_description,resolved
+Broken wikitext with bold inside and outside a label wrongly interpretted as correct by Parsoid,"This has long been merged, so closing as fixed. Please reopen if there is still an issue.",1386117085,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-geakkjwdr2b6k3vobqx7,task_subcomment,NA
+Broken wikitext with bold inside and outside a label wrongly interpretted as correct by Parsoid,"Tidy should result in non-broken HTML (unless there is a bug in Tidy). I just checked and Tidy fixes PHP parser's broken HTML and generates: <p><b><a href=""/wiki/Foo"" title=""Foo"" class=""mw-redirect"">F<b>oo</b> B<b>ar</b></a></b></p> (Can be verifed at https://en.wikipedia.org/wiki/User:Ssastry/sandbox)
+
+As for Parsoid, yes, this kind of broken wikitext was not being handled properly so far, but that is set to change with https://gerrit.wikimedia.org/r/#/c/83216/ which is awaiting review.
+
+That patch generates the following HTML on the snippet which is similar to what Tidy generates
+
+<p data-parsoid='{""dsr"":[0,27,0,0]}'><b data-parsoid='{""autoInsertedEnd"":1,""dsr"":[0,27,3,0]}'><a rel=""mw:WikiLink"" href=""./Foo"" data-parsoid='{""stx"":""piped"",""a"":{""href"":""./Foo""},""sa"":{""href"":""Foo""},""dsr"":[3,27,6,2]}'>F<b data-parsoid='{""dsr"":[10,19,3,3]}'>oo </b>B<b data-parsoid='{""autoInsertedEnd"":1,""dsr"":[20,25,3,0]}'>ar</b></a></b></p>",1380680793,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-geakkjwdr2b6k3vobqx7,task_subcomment,NA
+Broken wikitext with bold inside and outside a label wrongly interpretted as correct by Parsoid,"I have fixed the particular problem with this edit: https://en.wikipedia.org/w/index.php?title=International_Air_Transport_Association_airport_code&diff=574406042&oldid=574202912
+
+This is caused by a bug in Parsoid, I believe, which is wrongly interpretting wikitext as valid when it should be invalid. Specifically:
+
+  '''[[Foo|F'''oo '''B'''ar]]
+
+… as …
+
+  <b><a href=Foo>F</a></b><a href=Foo>oo </a><b><a href=Foo>B</a></b><a href=Foo>ar</a>
+
+… whereas it should result in broken HTML, per the PHP parser (post-Tidy), as:
+
+  <b><a href=Foo>F<b>oo </b>B<b>ar</b></a>
+
+The broken wikitext was added in https://en.wikipedia.org/w/index.php?title=International_Air_Transport_Association_airport_code&diff=568156811&oldid=568156261 which isn't tagged as a VisualEditor edit but possibly could have been (and a secondary bug means it isn't tagged) - will investigate separately.",1380075628,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-geakkjwdr2b6k3vobqx7,task_subcomment,NA
+VisualEditor: Editor incorrectly selects slug and infobox onload,"Screenshot
+
+https://en.wikipedia.org/w/index.php?title=Daniel_Rowe_%28footballer%29&oldid=570278760&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11872}",1379834460,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-uw2trpgzgq47w4uqfske,task_description,resolved
+VisualEditor: Editor incorrectly selects slug and infobox onload,"Change 85866 merged by jenkins-bot:
+Detect collapsed range inside focusable node in ve.ce.Surface#onChange
+
+https://gerrit.wikimedia.org/r/85866",1380043305,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uw2trpgzgq47w4uqfske,task_subcomment,NA
+VisualEditor: Editor incorrectly selects slug and infobox onload,"Change 85866 had a related patch set uploaded by Esanders:
+Detect collapsed range inside focusable node in ve.ce.Surface#onChange
+
+https://gerrit.wikimedia.org/r/85866",1380038162,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uw2trpgzgq47w4uqfske,task_subcomment,NA
+VisualEditor: Editor incorrectly selects slug and infobox onload,"This is cause by ve.ce.Surface#showSelection not being aware of the slug at the start of the document. Also, because the focusableNode logic takes places before showSelection is called, it tries to do a native selection.",1380036773,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-uw2trpgzgq47w4uqfske,task_subcomment,NA
+VisualEditor: Editor incorrectly selects slug and infobox onload,"Created attachment 13347
+Screenshot of page after trying to Undo
+
+Causes loss of data as it makes it really easy to accidentally delete that selection when you start typing.
+
+When you then try to do Undo, the following exception is thrown:
+
+Uncaught Error: Cannot roll back a transaction that has not been committed 
+
+Also, for some reason the font has become noticably smaller (only in the affected paragraph; see screenshot)
+
+**Attached**: {F11873}",1379834796,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-uw2trpgzgq47w4uqfske,task_subcomment,NA
+VisualEditor: Automatic Incorrect caret movement with ULS,"This is a separate report for automatic caret movement from one place to another when using VE with ULS.
+
+This problem has been seen with some other bugs, specifically, in the fourth[1], seventh[2] and tenth[3] comments of Bug 53708 and the original report of Bug 54421
+
+I also suspect that the problem in Bug 53701 is a form of this bug only.
+
+However, I am reporting this as a separate bug since I was able to reproduce it independent of these bugs.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit
+
+Steps:
+1 Enable ULS IME hindi transliteration
+2 Take the caret to the end of the first paragraph using the mouse (i.e click at the end of the first paragraph to take the caret there)
+3 Input [RETURN KEY][RETURN KEY]a
+
+Expected output:
+[NEWLINE][NEWLINE]अ
+
+Actual Output:
+[NEWLINE]अ[NEWLINE]
+
+As long as the return keys have been pressed, everything is fine and the caret is in the second newline. However, as soon as a is pressed, the input is in the first new line and not the second. The caret has hence moved up one line before the input is placed into the output text. The caret does not move back and is after the output अ
+
+This text is selectable, but can't be copy-pasted into an external text editor.
+The text is removable, so this is not entirely Bug 53708 . However, pressing a backspace when the caret is after अ removes अ along with the newline that precedes it.
+
+[1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c4
+[2]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c7
+[3]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c10
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379768640,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-nql2oht74xidzmey66vl,task_description,resolved
+VisualEditor: Automatic Incorrect caret movement with ULS,"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.",1453748489,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nql2oht74xidzmey66vl,task_subcomment,NA
+VisualEditor: Automatic Incorrect caret movement with ULS,"Hi,
+
+Confirming the above problem for VE+ULS (Typing input Marathi:अक्षरांतरण) Tested with Win 7 + Firefox 24.0 
+
+*Plus additional issue observed after Automatic Incorrect caret movement when I kept typing It started eating up text on right side in continuous movement simmiller to the problem described in Bug 53757 .
+
+
+
+
+Thanks and Regards",1379905436,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-nql2oht74xidzmey66vl,task_subcomment,NA
+VisualEditor: Text duplication when using jquery.IME on existing pages,"Screenshot showing text duplication
+
+This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3
+
+The entire test procedure is as follows:
+
+System Environment:
+Windows7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit
+
+Steps:
+Enable ULS IME hindi transliteration
+Take a caret to the end of the first paragraph using the mouse (i.e click at
+the end of the first paragraph to take the caret there.)
+Input ag
+Output will be अग् as expected but with incorrect selection as reported in the comment linked above
+Further input a
+This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.
+
+What should have happened:
+The original output अग् should have been changed to अग at the end of the first paragraph.
+
+So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated.
+
+Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11824}",1379764980,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-qb2engnawhn3el2wqyzm,task_description,resolved
+VisualEditor: Text duplication when using jquery.IME on existing pages,"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.",1453749108,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qb2engnawhn3el2wqyzm,task_subcomment,NA
+VisualEditor: Text duplication when using jquery.IME on existing pages,Automatic Incorrect caret movement has been reported separately as Bug 54424,1379768763,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-qb2engnawhn3el2wqyzm,task_subcomment,NA
+browsertests: configure Zuul,"This is a sub project of bug 53697 https://www.mediawiki.org/wiki/Continuous_integration/Browser_tests
+
+It covers setting up the Zuul configuration to trigger browser tests. From the wiki page:
+
+The exact workflow would need to be figured out with the VisualEditor team. A first step would be to run the browser tests after a change has been merged and report back in Gerrit for their information.
+At first we will only want to run browser tests after a change has been merged. This let us load the system progressively without disrupting the VisualEditor authors.
+
+We can later on make Zuul report back in Gerrit a message stating the result of the tests, that will raise awareness among developers and they can work on fixing the unsuccessful tests. Additionally, we can have the browser tests to be triggered on every patchset, the labs instance load will have to be carefully monitored.
+
+Once tests are properly passing and the setup has been proven useful, we can make Zuul to block patchsets not passing the browser tests. The developers would then be required to fix the code or the test to have their change merged in
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1379695800,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-3qnp2v5yec7kxc653kc7,task_description,resolved
+browsertests: configure Zuul,Being added on an ongoing basis. Already added the ULS browser tests in the Zuul 'test' pipeline.,1385993818,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-3qnp2v5yec7kxc653kc7,task_subcomment,NA
+browsertests: configure Zuul,"CCing Željko Filipin on any continuous bug related to browsertests. Main tracking bug is: bug 53697, see https://bugzilla.wikimedia.org/showdependencytree.cgi?id=53697&hide_resolved=0",1379705800,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-3qnp2v5yec7kxc653kc7,task_subcomment,NA
+Add _rtselser end point in web api,"For end users and VE folks the non-selser _rt end point is often confusing, as it shows diffs that are normally avoided by selser. It would be useful to add a _rtselser end-point that serializes to HTML, re-parses that HTML (to catch foster-parenting issues) and then serializes it back with selser enabled.
+
+This will provide us with a quick sanity check for the selser code, and a better link for end users and VE to establish that something has indeed dirtied the DOM.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379611080,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-g5cwud3usjdr2bplpq6x,task_description,resolved
+Add _rtselser end point in web api,"Change 85990 merged by jenkins-bot:
+Bug 54339: Add _rtselser endpoint in web API
+
+https://gerrit.wikimedia.org/r/85990",1380131239,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+Add _rtselser end point in web api,"Change 85990 had a related patch set uploaded by Marcoil:
+Bug 54339: Add _rtselser endpoint in web API
+
+https://gerrit.wikimedia.org/r/85990",1380124213,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+Add _rtselser end point in web api,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Just for clarity, this will catch any unhandled fostered parenting issues in
+> > Parsoid.
+> Depending on how it's written, it could catch these (or have a mode to detect
+> these), by serializing the DOM out to a string and parsing it back in again.
+
+Yes, that is the intention. 
+
+> With or without this kind of DOM normalization though, mass-testing articles
+> to find selser bugs would be very awesome.
+
+We haven't yet figured out how to do this reliably. We still have same problem that I mentioned on the VE/F page about absence of an oracle to tell us authoritative wikitext to compare against. So, the best we can do is simulate null edits, or modify text, etc. But those are, for the most part, the uninteresting bits of selser testing -- the most interesting bugs show up with more complex edits, and that is the bit that needs to be solved for using it in an automated manner in rt-testing.",1379617066,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+Add _rtselser end point in web api,"(In reply to comment #1)
+> Just for clarity, this will catch any unhandled fostered parenting issues in
+> Parsoid.
+Depending on how it's written, it could catch these (or have a mode to detect these), by serializing the DOM out to a string and parsing it back in again.
+
+With or without this kind of DOM normalization though, mass-testing articles to find selser bugs would be very awesome.
+
+> VE-DOM-dirtying will not be caught by this.
+Fortunately, VE does its own detection for this at run time: https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=visualeditor-needcheck",1379613552,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+Add _rtselser end point in web api,"Just for clarity, this will catch any unhandled fostered parenting issues in Parsoid. VE-DOM-dirtying will not be caught by this.",1379611334,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-g5cwud3usjdr2bplpq6x,task_subcomment,NA
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getOffset' of null"" triggered using jquery.IME","Screenshot of Console Error and Blanked Page
+
+This bug was found when testing per the sixth and seventh comment at Bug 53708
+This is very similar to Bug 54331 , however, this one is reproducible.
+
+System Environment:
+Windows7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/Project:Sandbox?veaction=edit
+
+Steps to reproduce:
+Enable ULS IME hi transliteration
+Input the following (below the 'Testing Area' heading):
+agar[SPACE][SPACE][BACKSPACE][BACKSPACE]
+
+What happens:
+Apart from a bunch of buggy behaviour described in the seventh comment at Bug 53708 , the template is entirely removed and the following console error shows up once the second [BACKSPACE] is pressed:
+
+Uncaught TypeError: Cannot call method 'getOffset' of null load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:231
+ve.ce.Document.getNodeAndOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:231
+ve.ce.Surface.showSelection load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:287
+ve.ce.Surface.onChange load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:274
+oo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139
+ve.dm.Surface.change load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:86
+ve.ce.Surface.handleDelete load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:286
+ve.ce.Surface.onDocumentKeyDown load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:267
+proxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10
+ve.EventSequencer.onEvent load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:19
+(anonymous function) load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:18
+jQuery.event.dispatch load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:45
+elemData.handle.eventHandle load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:38
+
+The file urls are:
+
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*
+
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11639}",1379606220,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-fkizlik3mtnbtsqbgnqs,task_description,resolved
+"VisualEditor: ""Uncaught TypeError: Cannot call method 'getOffset' of null"" triggered using jquery.IME","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.",1453749185,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fkizlik3mtnbtsqbgnqs,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","This bug was found when testing per the sixth and seventh comment at Bug 53708
+It seems somewhat heisenbuggy and I haven't been able to reproduce it yet. However, I'm sure of the steps which caused it.
+Reporting this so that it's documented in case it is ever seen again.
+
+System Environment:
+Windows7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/Project:Sandbox?veaction=edit
+
+Steps to reproduce:
+Enable ULS IME hindi (hi) transliteration (labelled लिप्यंतरण)
+Input the following:
+agar[SPACE][SPACE][BACKSPACE]
+
+What happens:
+Apart from a bunch of buggy behaviour (described in the seventh comment at Bug 53708 ), the following console error shows up once the [BACKSPACE] is pressed:
+
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:106
+ve.dm.Document.getNodeFromOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:106
+ve.dm.Surface.change load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:84
+ve.ce.Surface.onSelectionChange load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:275
+oo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139
+ve.ce.SurfaceObserver.pollOnceInternal load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:292
+ve.ce.SurfaceObserver.pollOnce load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:291
+ve.ce.SurfaceObserver.timerLoop load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:290
+proxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10
+
+The file urls are:
+
+For the last line:
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z
+
+For all other lines:
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*
+
+Also, the template's formatting was gone with the input hindi text appearing alongside the template text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379605200,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-f3qthugptx3szx2kr56o,task_description,resolved
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","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.",1453749233,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","After Comment 3, reloading the page by pressing the return key in the address bar gave the following error:
+
+Uncaught RangeError: Maximum call stack size exceeded
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload
+proxy
+ve.init.mw.ViewPageTarget.onBeforeUnload",1379611711,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","Editable content in Read mode
+
+Further, after everything stated in Comment 1 has happened, if VE editing is canceled and the js prompt about losing unsaved changes is confirmed, the second error still continues. The tab is set to Read instead of Edit, however the content is still editable and the VE toolbar remains visible (although it doesn't seem to work).
+
+**Attached**: {F11633}",1379611271,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME",Related/similar bug: Bug 51526,1379610367,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+"VisualEditor: ""Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds"" triggered using jquery.IME","Screenshot showing original error and changed template formatting
+
+I've been able to reproduce this bug in the same system environment on the same test url with the following steps:
+
+Enable ULS hi transliteration
+Input a[SPACE][BACKSPACE]a
+
+The error as specified above shows up.
+
+Pressing a space after this brings up the following errors:
+
+Error 1:
+
+Uncaught TypeError: Cannot call method 'insertBefore' of null load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:239
+ve.ce.BranchNode.onSplice load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:239
+oo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139
+ve.dm.BranchNode.splice load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:44
+(anonymous function) load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…back%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:3
+ve.dm.Document.rebuildNodes load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:107
+ve.dm.DocumentSynchronizer.synchronizers.rebuild load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:117
+ve.dm.DocumentSynchronizer.synchronize load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:119
+ve.dm.TransactionProcessor.process load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:59
+ve.dm.Document.commit load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:104
+ve.dm.Surface.change load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:84
+ve.ce.Surface.handleInsertion load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:282
+ve.ce.Surface.onDocumentKeyPress load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:268
+proxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10
+ve.EventSequencer.onEvent load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:19
+(anonymous function) load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:18
+jQuery.event.dispatch load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:45
+elemData.handle.eventHandle load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:38
+6
+
+Error 2:
+Uncaught Error: offset 805 out of bounds load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:150
+ve.dm.ElementLinearData.getAnnotationIndexesFromOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:150
+ve.dm.ElementLinearData.getAnnotationsFromOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:150
+ve.ce.Surface.onContentChange load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:277
+oo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139
+ve.ce.SurfaceObserver.pollOnceInternal load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:292
+ve.ce.SurfaceObserver.pollOnce load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:291
+ve.ce.Surface.documentOnBlur load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:264
+proxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10
+jQuery.event.dispatch load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:45
+elemData.handle.eventHandle load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:38
+
+File urls:
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*
+https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z
+
+The second error keeps repeating. Also, changing tabs makes the count in the chrome console go up.
+
+It also repeats each time a mouse click is done at the current caret position. It also repeats if the caret is taken to a different position in the text using the mouse or the arrow keys.
+
+**Attached**: {F11632}",1379608431,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-f3qthugptx3szx2kr56o,task_subcomment,NA
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,"I am trying to VEdit https://en.wikipedia.org/w/index.php?title=User:Elitre_%28WMF%29/Sandbox&oldid=573480590&veaction=edit , which is a blank version of my sandbox. There's a lot of white space between the title of the page and the point where I can start adding text, and although the source editor says the page is really empty, looks like there's still something there.
+
+If I hover with the mouse right below the comma in the tagline ""Wikipedia, the free encyclopedia"", the cursor changes as if there's an invisible link.
+1) Right under the comma, the ""link"" points to my userpage (it's clickable, and the page will open in the same tab);
+2) some pixels below, the link will point to [[Help:Page History]];
+3) going further down, it points to a diff of the sandbox.
+There are other points in the page which trigger the links, but the page history one is not easy to spot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52243
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58063",1379602440,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_description,resolved
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,"Change 107133 merged by jenkins-bot:
+Hide #contentSub properly
+
+https://gerrit.wikimedia.org/r/107133",1389633324,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_subcomment,NA
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,"Change 107133 had a related patch set uploaded by Jforrester:
+Hide #contentSub properly
+
+https://gerrit.wikimedia.org/r/107133",1389626449,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_subcomment,NA
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,Only partly a dupe of bug 52243.,1388963194,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_subcomment,NA
+VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there,"The hidden text that causes this, if selected and copy/pasted elsewhere, reads:
+< User:Elitre (WMF)
+This is an old revision of this page, as edited by Elitre (WMF)  (talk | contribs) at 10:57, 18 September 2013. It may differ  significantly from the current revision.
+Revision as of 10:57, 18 September 2013 by Elitre (WMF)  (talk | contribs)
+
+This is reported as being common also in articles.
+Thanks.",1379667965,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5eekrsnuh3slhfvi2vl5,task_subcomment,NA
+Wikitech: Install TemplateData extension,"VisualEditor is installed already. Would be nice to have TemplateData as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379590500,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ufskmzg3xlrkksp26qtv,task_description,resolved
+Wikitech: Install TemplateData extension,"This seems to have been done, I think by the wikitech config/deployment changes.",1426690252,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ufskmzg3xlrkksp26qtv,task_subcomment,NA
+(Re-) unify data and metadata,"Because about half the code in the DM is solely there to keep this delicate data structure together, and now that we don't need ±1 cursoring it seems like a lot of effort for nothing.
+
+The behaviour it provides (protecting metadata from deletion) can all be done in the transaction builders, and in fact we already do this for internal lists)
+
+Going forward this will make multi user editing a lot easier to.
+
+That said this is going to be a massive commit.
+
+-----
+
+Currently, MetaItems are stored outside the main linear data structure, in a separate meta linear data structure. This complicates the processing of linear data: transaction processing, rebasing, serialization/deserialization etc, and makes it harder to reason about document correctness. Instead:
+* Store metadata as block nodes in the main data list
+* On conversion from HTML, hoist metadata found in a content position to a legal structural position
+* On conversion back to HTML, roundtrip metadata hoisted from unmodified content branch nodes back into the original content position
+* When deleting across metadata (e.g. <p>foo[-</p><meta/><p>-]bar</p>), hoist metadata to a legal structural position as necessary",1379550420,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_description,resolved
+(Re-) unify data and metadata,Gosh.,1517245931,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 405751 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (c5fddd508)
+
+[[https://gerrit.wikimedia.org/r/405751]]
+",1517245035,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 405751 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (67548dc57)
+
+[[https://gerrit.wikimedia.org/r/405751]]
+",1516647701,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 385492 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] [BREAKING CHANGE] Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/385492]]
+",1516647435,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 336929 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] [WIP] [PULLTHROUGH] MW changes for the meta-data inlining commit
+
+[[https://gerrit.wikimedia.org/r/336929]]
+",1515616786,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 336925 abandoned by Divec:
+WIP: [BREAKING CHANGE] Store metadata as block nodes in the main data list
+
+Reason:
+Moved to Ib5174b0dcba1c24f44d889e08140bee31a064011
+
+[[https://gerrit.wikimedia.org/r/336925]]",1508543685,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 385492 had a related patch set uploaded (by Divec; owner: Divec):
+[VisualEditor/VisualEditor@master] WIP: [BREAKING CHANGE] Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/385492]]
+",1508543616,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 336925 had a related patch set uploaded (by Jforrester):
+[BREAKING CHANGE] Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/336925]]
+",1486679038,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 336899 had a related patch set uploaded (by Jforrester):
+Update VE core submodule to master (0dfc50a88)
+
+[[https://gerrit.wikimedia.org/r/336899]]
+",1486675750,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 314568 merged by jenkins-bot:
+Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/314568]]",1486668402,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,"Change 314568 had a related patch set uploaded (by Jforrester):
+Store metadata as block nodes in the main data list
+
+[[https://gerrit.wikimedia.org/r/314568]]
+",1486584604,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+(Re-) unify data and metadata,We now have ve.dm.Node.static.isDeletable.,1463763857,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vstc34ukjrx4agdul6rw,task_subcomment,NA
+VisualEditor: ResizableNode should be able to live-preview the node it's resizing as you drag,"This would also solve the problem of the resize marker having to snap into the right position at the end of a drag if you use the wrong handle (or any handle if the image is centred)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379549580,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nqqibdaciuaeyw2lnzmy,task_description,resolved
+VisualEditor: ResizableNode should be able to live-preview the node it's resizing as you drag,"Change 89814 merged by jenkins-bot:
+Resizable node live preview
+
+https://gerrit.wikimedia.org/r/89814",1381926939,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nqqibdaciuaeyw2lnzmy,task_subcomment,NA
+VisualEditor: ResizableNode should be able to live-preview the node it's resizing as you drag,"Change 89814 had a related patch set uploaded by Esanders:
+Resizable node live preview
+
+https://gerrit.wikimedia.org/r/89814",1381839789,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nqqibdaciuaeyw2lnzmy,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of the sentence/paragraph when using jquery.IME,"**Author:** `renukaalurkar`
+
+**Description:**
+1)Logged in to http://en.wikipedia.beta.wmflabs.org/wiki/Main_Page
+2)Go to your user page.
+3)Click on Languages/cog, select Input and click on Enable Input tools.
+4)Click on Edit beta tab.
+5)Click on More, and using Media, select a couple of pictures
+6)Click on the tiny keyboard/typewriter and select language as Hindi or Telugu
+7)Now start entering text in Hindi or Telugu.
+
+Observations:
+1)After typing a few letters, the cursor jumps back to the beginning of the sentence.
+2)Sometimes, when Enter is hit, the cursor goes back to the beginning of the paragraph.
+3)Sometimes, when Enter is hit one of the images disappears.Write some more and the other image also disappears.
+4)Click on Save page button
+5)Now both the images are visible again.
+
+Observed on Firefox 24.0 and Chrome 29.0.1547.66
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379529000,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hu7ibauxmtlo3ljy4pvq,task_description,resolved
+VisualEditor: Cursor jumps to the beginning of the sentence/paragraph when using jquery.IME,"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.",1453748296,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hu7ibauxmtlo3ljy4pvq,task_subcomment,NA
+VisualEditor: Cursor jumps to the beginning of the sentence/paragraph when using jquery.IME,"I've set my Language settings on https://en.wikipedia.org to using native keyboard for Hindi input.
+
+> 5)Click on More, and using Media, select a couple of pictures
+> 6)Click on the tiny keyboard/typewriter and select language as Hindi or Telugu
+
+Where exactly? In the ""alternative caption"" field of the ""Insert Image"" dialog? Some other field? The text of the page you edit?
+At least for लिप्यंतरण and इनस्क्रिप्ट I cannot reproduce any jumping back of the cursor in the ""alternative caption"" field.
+
+The steps to reproduce this problem are a bit unclear (but probably only because the user interface has changed since this problem was reported). 
+
+Clarification highly welcome.",1425553166,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hu7ibauxmtlo3ljy4pvq,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"? should be ؟ icon
+
+For  Notification Tool for  RTL languages Please change ""?"" icon in attached image to RTL icon
+
+See @Amire80's comment.  Not the same for all languages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54252
+
+**Attached**: {F11507}",1379514480,PHID-USER-dswbdv7ibhsefllcqarz,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_description,resolved
+RTL for Notification Tool: ? should be ؟ icon,"I believe that this is now long-since fixed, since we moved to OOjs UI.",1488434919,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"VisualEditor seems to deal with this issue with the help button (also presented as ?)
+
+It might help checking what lists they have to when to flip the question mark and when not to, and use that same strategy in this case.",1437684531,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"**nzmoihue** wrote:
+
+Seems dvwiki is also using ""؟"" http://dv.wikipedia.org/wiki/%DE%88%DE%A8%DE%86%DE%A8%DE%95%DE%A9%DE%91%DE%A8:%DE%A2%DE%A7%DE%82%DE%B0%DE%89%DE%AA_%DE%80%DE%AE%DE%85%DE%AA%DE%87%DE%A6%DE%81%DE%A8 (find ""؟"" on that bug using Ctrl+F)
+
+I guess something like https://github.com/wikimedia/mediawiki-core/blob/9ea365dcb2f1390e117767e0ead4a5655ad4631d/skins/common/shared.css#L240 is needed for reversed question mark",1383344041,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"This is not needed for all languages.
+
+It is definitely not needed for Hebrew and Yiddish.
+
+It is *probably* needed for all languages written in the Arabic script.
+
+I'm not sure about Divehi (dv) and Aramaic (arc).",1381915440,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"**bsitu** wrote:
+
+Oops, the patch referenced the wrong bug",1381518303,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"Change 89249 had a related patch set uploaded by Bsitu:
+Notification overlay is partially hidden in RTL language
+
+https://gerrit.wikimedia.org/r/89249",1381518148,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"**bsitu** wrote:
+
+
+
+%%%*** This bug has been marked as a duplicate of bug 54252 ***%%%",1380239232,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/252,1379969376,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+RTL for Notification Tool: ? should be ؟ icon,"To devs:
+You just need to add element like ""#mw-echo-overlay-moreinfo-link"" but with a ""transform:scaleX(-1);"" [1] to the ext.echo.overlay.css
+and call that element instead the ltr one in ext.echo.overlay.js when .sitedir-rtl is true [2]
+
+[1]: http://nicolasgallagher.com/css-background-image-hacks/
+[2]: https://www.mediawiki.org/wiki/Manual:Interface/IDs_and_classes
+
+Best",1379681684,PHID-USER-ctchvhisqfvk4rz7nt7d,False,PHID-TASK-blsktvyvk2zcdw2o4yue,task_subcomment,NA
+VisualEditor: Duplicating references groups,"See
+https://en.wikipedia.org/w/index.php?title=Fizeau_experiment&diff=573001070&oldid=572299847 - the user corrected a typo and this resulted in the references groups getting duplicated.
+Reproduced in 
+https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=573341379 and https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=573340833 while just testing wikilinks, as you can see. My first attempt to reproduce this actually resulted in more weird (although known, I think) behaviour: https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=573176079 .
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379500080,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-c45wkid72cnbk33nmpdr,task_description,resolved
+VisualEditor: Duplicating references groups,"I've tried to reproduce this using @Elitre's testcases, but couldn't; I'm tentatively closing as fixed.",1429223923,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-c45wkid72cnbk33nmpdr,task_subcomment,NA
+VisualEditor: Duplicating references groups,I wonder if this is still valid.,1421888557,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-c45wkid72cnbk33nmpdr,task_subcomment,NA
+VisualEditor: Duplicating references groups,"https://fr.wikipedia.org/w/index.php?title=Archives_sociales_suisses&diff=96769347&oldid=96768850
+
+https://fr.wikipedia.org/w/index.php?title=Jeu_vid%C3%A9o_ind%C3%A9pendant&diff=95172709&oldid=95071765",1379575952,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-c45wkid72cnbk33nmpdr,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,"Edit a page with One&nbsp;Two which displays as One Two.  Select the entire text, copy, past at end of the string.  Displays in VE fine at first.  Saving however produces One&nbsp;TwoOneTwo which displays as One TwoOneTwo. 
+
+Originally from 
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=573462315&oldid=573461696
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379493780,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_description,resolved
+Parsoid: mw:Entity not preserved if data-parsoid missing,"Change 89356 merged by jenkins-bot:
+Bug 54262: Serialize new entity to its contents
+
+https://gerrit.wikimedia.org/r/89356",1381535250,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,"(In reply to comment #2)
+> Is data-parsoid copied as well?
+
+Never mind, the title had that info.",1381532829,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,"Change 89356 had a related patch set uploaded by GWicke:
+Bug 54262: Serialize new entity to its contents
+
+https://gerrit.wikimedia.org/r/89356",1381532654,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,Is data-parsoid copied as well?,1381523696,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+Parsoid: mw:Entity not preserved if data-parsoid missing,"<p>Foo<span typeof=""mw:Entity"">&nbsp;</span>Bar</p>
+
+converts to
+
+FooBar
+
+which appears to be the problem",1381157310,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-bxknfjhi57rb6pgzrqm7,task_subcomment,NA
+VisualEditor: Show percentage of progress in loading animation,"DKqwerty at en.wp reports: ""Article Futurama took 58 seconds to load into VE, with the loading bar running the entire time. I think this is unacceptable as it is probably off-putting to inexperienced users. Further, the bar just fills, empties, fills, empties, etc. rapidly and continuously until the page is loaded... Would it be possible to make this bar actually indicate what percentage has been loaded so editors have at least a hint that something is being processed?""
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379426040,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-boxjw4hklzqeriwzj6zc,task_description,resolved
+VisualEditor: Show percentage of progress in loading animation,Implemented by Ed in https://gerrit.wikimedia.org/r/#/c/196583/,1427850989,PHID-USER-r7wrkcx7j2vutqs6hr3g,True,PHID-TASK-boxjw4hklzqeriwzj6zc,task_subcomment,NA
+VisualEditor: Show percentage of progress in loading animation,"Not sure how we'd judge progress on this one, but it'd be useful for users…",1415881533,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-boxjw4hklzqeriwzj6zc,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Moving here the following proposals:
+<https://strategy.wikimedia.org/wiki/Proposal:Text_or_Syntax_driven_Charts,_Diagrams,_Graphs_and_more>
+<https://strategy.wikimedia.org/wiki/Proposal:Editable_Graphics>
+<https://strategy.wikimedia.org/wiki/Proposal:Markup_for_charts_and_graphs>
+(with some of the participants in cc).
+
+* «By now Wikipedia has markup/code for everything—math (TeX), parser functions, location maps, and even SVG is supported. However, what is notably missing from many articles (other than high-quality portraits) are graphs and charts.»
+* «There are many types of diagrams. The need for collaborative graphics is wide ranging, from map making to biochemical pathways to flow charts to genealogy to general charting. Each type of graphic has or could have a little language, XML or other representation to define graphics of that type succinctly. Whilst all can be presented as .pngs or .SVGs, the more succinct description is necessary for editability.»
+
+This is distinct from bug 43616 (Provide a way to create interactive 2D/3D timelines and infographics e.g. Java applets, AJAX, Flash) in that it's not about *interactive* stuff and that there are some existing extensions which someone should assess and develop for Wikimedia purposes. I'd also leave maps out of it because that's being addressed (at last) elsewhere.
+Part of it will be solved by bug 38271, but only to a degree.
+
+Mentioned extensions: [[mw:Extension:Graph]], [[mw:Extension:GnuplotBasic]], [[mw:Extension:Plotters]], [[mw:Extension:WikiPlot]].
+
+Keywords from the proposals: http://bloodgate.com/perl/graph/, Java .jar, Flash .swf, Silverlight .scr, ActiveX .ocx, Vector (.svg) .svg (XML), AnyWikiDraw, AnyWikiDraw, WikiPathways, WikiTex, Graph Plugin, DPL Bundle, TeX, gluplot, pgfplots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379420040,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_description,open
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Regarding ""enabling"", see https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment if someone is interested",1643486674,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","nowadays there is an extenstion https://www.mediawiki.org/wiki/Extension:Diagrams , would enabling it be a step into the right direction?
+",1643485832,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)",{T183689} is a related task.,1591962226,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Actionable tasks are not the only use case for Phabricator; cf. for example the #Epic project.  Additionally, I think tasks with subtasks are very preferable to projects in some cases as they themselves have a status, a dependency tree, etc.
+
+This task has two blocking subtasks that have not been resolved, so this task itself does not seem to be resolved.  AFAIUI, for example you don't want to work on T56222 (which is fine), but that also means that someone else needs to do the deed to convert those cladograms to Extension:Graph (or something else).",1450709456,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@nemo_bis, this is not what the bug description states. I think the better use of phabricator would be to create small, actionable, and well scoped tasks for specific feature, and mark those with some project tag for tracking. Otherwise this task grows infinitely large and not very useful. Having small tasks allows each feature to be discussed separately, and different devs can pick them up for implementation.  The only reason why we had the [tracking] tasks in Bugzilla was because there was no good support for tagging (projects).",1450703140,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","This bug's purpose is precisely to collect requirements and map alternatives. Two of them are identified by the two blockers. :) If you think the usecase behind that extension is another, please add to blockers.",1450683051,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Closing because we now have <graph>, and because this task is too broad. Please add more specific tasks for anything that's missing :)",1450639655,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@yurik OK.  I'm happy now.  Yep, I did know d3.js was under Vega, just previously had doubts that enough of that flexibility was exposed.   We can't have end users writing arbitrary javascript, so how the functionality is exposed really matters.
+
+I think I am already now OK with this task being closed.  There is obviously tons more to do and tons more that could be done, but the basics of the template driven transform of json to svg or canvas are there, which is what this task was asking for. 
+",1450639269,PHID-USER-tkx4pj3lyasedlwiiqzm,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@jamescrook, you mean [this example](http://vega.github.io/vega-editor/?mode=vega&spec=force)?  Also here is an [interactive version](http://vega.github.io/vega-editor/?mode=vega&spec=force_drag).
+
+As for d3 - vega is based on d3, so, in theory, most of the capabilities of d3 are exposed. But yes, we will have to dig through it.",1450638578,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@jamescrook, you mean [this example](http://vega.github.io/vega-editor/?mode=vega&spec=force)?  or an [interactive version](http://vega.github.io/vega-editor/?mode=vega&spec=force_drag)
+
+As for d3 - vega is based on d3, so, in theory, most of the capabilities of d3 are exposed. But yes, we will have to dig through it.",1450638556,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@Yurik , looking at the source for that tree it looks to be d3.js rather than Vega.",1450638376,PHID-USER-tkx4pj3lyasedlwiiqzm,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@yurik Vega doesn't currently seem to support those, at least not from the examples I can find.  They are motivating examples, so should not be swept under the carpet.  Biochemical pathways, flow charts and genealogy are all similar in being based on graphs (i.e. networks).  The Vega examples I am seeing are plots and maps.
+
+I am wondering why I am seeing no force directed layouts with Vega, although the visual encoding transform is described in the documentation.  If we can get even a basic demo of some biochemical pathway done using a force directed layout then I am cool with this task being closed.  Elaboration and prettiness can come later.",1450638292,PHID-USER-tkx4pj3lyasedlwiiqzm,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Just found this [expandable tree sample](http://bl.ocks.org/alcy/raw/7702db089164c493a705/) that seems to be based on Vega with some additional hacks. Might be interesting to build something similar.  And of course there are existing samples like [heatmap](http://vega.github.io/vega-editor/?mode=vega&spec=heatmap&renderer=svg) and many other that might be useful.
+CC: @jamescrook",1450636711,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@jamescrook, we have to narrow down this task, otherwise it sounds like ""create a platform that allows everything"", which is not really actionable.  From my reading of the description, Vega 2.0 should be able to handle most of it. If not, please create separate task that we can discuss.",1450633861,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Yurik, how does this address ""biochemical pathways to flow charts to genealogy"" from the description?
+
+",1450632768,PHID-USER-tkx4pj3lyasedlwiiqzm,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)",Should this be closed?  We now have interactive graphs/charts/etc: https://www.mediawiki.org/wiki/Extension:Graph/Demo#Vega_2.0_Interactive_Examples,1450622876,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Actually, this was one of the rawest ideas in the project list and is absolutely not usable for GSoC, unless a student comes who has an extremely clear idea of a feature to add and a plan for it. I'll move the possible project tag to T56222. The other blocker, T40271, would also be suitable, but I doubt it would benefit from GSoC (iterative GSoC cycles over the same problem rarely helped anything).",1423684001,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)",This task is about wikitext. VisualEditor support for the markup is a separate issue.,1423683746,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@qgil, I can totally see this becoming a GSoC project, but most of the mentorship would have to come from the UI/Visual Editor team because they have the expertise in building custom editors.  The student would build an editor with a dynamically updated viewer for the VE.  I already have a simplified version of that [[ http://graph.wmflabs.org/w/index.php?title=Graph:Stocks&action=edit | here ]] -- click preview and try changing the graph definition.",1423664307,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Wikimedia will [[ https://phabricator.wikimedia.org/T921 | apply to Google Summer of Code and Outreachy ]] on Tuesday, February 17. If you want this task to become a featured project idea, please follow [[ https://phabricator.wikimedia.org/project/view/1042/ | these instructions ]]. ",1423662263,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","@Milimetric, @Yurik, is there a possible project related to this task that students like @Sumit could plan for in the context of Google Summer of Code 2015 (and that you would like to mentor)? Something about #MediaWiki-extensions-Graph ?",1423648511,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","> I'd like to take this up as a project. Is this still open for taking up and developing for this year?
+
+It's open, but not ready. Please choose one of the extensions mentioned by this report and start filing patches against them. When you find one you're comfortable developing, you'll know the area you can work on.",1423643389,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)",I'd like to take this up as a project. Is this still open for taking up and developing for this year?,1423640170,PHID-USER-ll7x5qhzru4lqz3xfdbm,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Sorry, meant to post last comment for bug 43616.  Yet, for this request, graph ext is still applicable, except that it is not wysiwyg unless some brave soul starts hacking a proper vega editor.",1411455023,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Graph extension might be applicable, even though it is not dynamic (yet), or even in production wikis, it does support various timelines, e.g. ""Napoleon"" at http://trifacta.github.io/vega/editor/ :)
+
+See https://www.mediawiki.org/wiki/Extension:Graph and samples at https://www.mediawiki.org/wiki/Extension:Graph/Demo 
+
+Discussion at https://meta.wikimedia.org/wiki/Wikimedia_Forum#Graphs.2C_Maps.2C_..._.28experimental.29",1411454841,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","I think what you're saying makes sense Pavel.  And no worries, to participate in this community you have to be really good at dealing with distractions.  I'm still waiting for someone else to help with mentoring on this important project.  I think someone with mediawiki extension development experience would be great.  Part of the reason I can't comment more, Pavel, is that I don't know anything about mediawiki extensions :)",1392061032,PHID-USER-vbyvvtbztxaeuaxelxx4,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Thanks, Dan. Vaga is excellent.
+
+But, for example, I need a template to draw a bar of population.
+The template takes a comma-separated list of cities.
+The population is taken from the wikidata.
+
+{{MyTemplate
+| cities=London,Berlin,Paris
+}}
+
+Source of wikipage Template:MyTemplate:
+
+... Some wiki markup ...
+<phptag>
+if ( isset($args[cities]) ) {
+  $cities = explode( $delimiter, $args[cities] );
+  $population = AskWikidata( 'Give me population of cities', $cities );
+  $data = array_combine($cities, $population);
+  echo new Vega( 
+      $data,
+      [ 'size'=>[400,200], 'scales'=>['x'=>'cities', y=>'population'] ] 
+    );
+}
+</phptag>
+... Some wiki markup ...
+
+There are:
+* functions 'explode', 'array_combine' is hooks of the extension PphTags Functions. (already done)
+* function 'AskWikidata' is fictional, but can be implemented as hook of some extension
+* objects 'Vega' is fictional, but can be implemented as hook of some extension
+* 'if', 'isset', 'echo' and '[...] (array definition)' is functions of extension PhpTags (already done)
+
+Suppose I'm developer of the extension Vega.
+I should just take the javascript source code from Vega and register hook in the extension PhpTags.
+
+source of Vega.php:
+
+$wgHooks['PhpTagsRuntimeFirstInit'][] = 'VegaExtension::initializeRuntime';
+
+class VegaExtension {
+  public static function initializeRuntime() {
+    \PhpTags\Runtime::setObjectsHook( 'VegaObject', array('Vega') );
+  }
+}
+
+class VegaObject extends PhpTags\BaseHooks {
+  public static function onObjectHook( ... ) {
+    // some code
+  }
+}
+
+The Class VegaObject will receive the arrays of data and parameters from the PhpTags,
+and when the function 'echo' is called returns all the necessary data for drowing the bar on the wikipage.
+a large part of the code (such as processing of various parameters) have to be implemented in the class PhpTags\BaseHooks.
+The class VegaObject will just have to inform PhpTags that it needs 'vega.min.js' and convey to one ready parameters.
+Since it is very simple, similar extensions can be done in one day.
+
+Maybe I'm writing all this is off topic, forgive me please.
+But I can not find anyone interested in this.
+I guess I'm looking for not out there, or can not speak understandable.
+Maybe I just doing nonsense and distract people from her work, I do not know.",1391663088,PHID-USER-qdblhomoh775qwgc6rra,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Dan, thank you for pushing this proposal. If you want to jump to the GSoC 2014 train you need to:
+
+* Take https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Support_for_text.2Fsyntax.2Fmarkup_driven_or_WYSIWYG_editable_charts.2C_diagrams.2C_graphs.2C_flowcharts_etc. , shorten the title, expand the description (one paragraph is enough), and move it under https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Featured_project_ideas
+
+* Find a second mentor.
+
+The sooner the better, since Wikimedia will be evaluated by the GSoC organizers in the next 1-2 weeks. You will know you are ready when your project looks great at https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014
+
+More: http://lists.wikimedia.org/pipermail/wikitech-l/2014-February/074277.html",1391623649,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Thanks Pavel.  I like the syntax you mention.  The advantage to using Vega JS syntax would be that it's a healthy active project and we get the parser, etc. for free.  Check it out if you haven't had a chance, I linked to it above.",1391615361,PHID-USER-vbyvvtbztxaeuaxelxx4,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","I'd suggest using a scripting language as markup for the editable charts, diagrams, graphs, flowcharts etc.
+
+For end users this may be like the example:
+
+== Extension:Graph ==
+
+ G { ""Bonn"" --> ""Berlin"" [ style: bold; ] }    
+As
+Graph( [ ""Bonn"" => [ ""Berlin"", ""style""=>""bold"" ] ] );
+or 
+$bonn = node(""Bonn"");
+$bonn->linkTo( node(""Berlin"", ""bold"") );
+Graph( $bonn );
+
+== Extension:WikiPlot ==
+
+<wikiplot height=""200"" width=""200"" caption=""Simple plot"" xspan=""-100;100"" yspan=""-100;100"">
+        <graph label=""Graph 1."" color=""255,0,0"">x+4</graph>
+        <graph label=""Graph 2."">3*x-3</graph>
+</wikiplot>
+
+as 
+
+$plot = new Plot( ['height'=>200, 'width'=>200, 'caption'=>'Simple plot', 'xspan'=>[-100, 100], 'yspan'=>[-100, 100] ] );
+
+or 
+
+$plot = new Plot();
+$plot->height = 200;
+$plot->width = 200;
+$plot->caption = ""Simple plot"";
+$plot->xspan = [-100, 100];
+$plot->yspan = [-100, 100];
+
+and
+
+$plot.addGraph( ['x+4', 'label'=> 'Graph 1.', 'color'=>[255,0,0] ]);
+
+$graph = new Graph( ""3*x-3"" );
+$graph->label = 'Graph 2.'
+$plot.add( $graph );
+
+echo $plot;
+
+It looks like directly code execution, but it is not.
+I did mw:Extension:Foxway for testing possibility of this. I ascertained that this may work and may work quickly.
+Now I do new mw:Extension:PhpTags. There any extension can register a hook as a constant, function or object.
+So far I have only worked on the functions and constants, and did not start work on objects.
+I am sure that the PhpTags will cover all the needs and will be convenient and powerful tool.
+I would like to find someone interested in discussing this.",1391598767,PHID-USER-qdblhomoh775qwgc6rra,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","tl;dr; I would be interested in being a mentor here, and probably collaborating until a solution is reached.
+
+We've done some thinking about this while we developed Limn [1] last year.  I believe Limn was headed in the wrong direction, but we (team analytics) are interested in solving this problem and it would be nice to combine efforts with anyone that is also interested.  Currently, I believe that Vega JS [2] is a very promising library.  It has a great mixture of simplicity and power.
+
+My personal opinion is that creating and editing infographics would work much like Visual Editor does.  There would be a simple JSON editor on the front end, which could evolve over time.  When saved, this would use a server to generate static infographics for consumption by the cache layer.  The dynamic infographic could be accessed through a link on the static image.  The cache could be repopulated with up-to-date infographics periodically if they depend on external data.  For this vision, Vega JS is quite suitable as it can generate PNGs server side for example.
+
+
+[1] https://github.com/wikimedia/limn
+[2] http://trifacta.github.io/vega/",1391530733,PHID-USER-vbyvvtbztxaeuaxelxx4,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","(In reply to comment #4)
+> Should this project be still listed in that page? 
+
+Yes.
+
+> If not, please remove it.
+> If
+> it still makes sense, then it could be moved to the ""Featured projects""
+> section
+> if it has community support and mentors.
+
+It lacks a mentor, plus (probably) someone to set a direction/the requirements (who may or not be the same person).",1385912944,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","**vladjohn2013** wrote:
+
+Hi, this project is still listed at  https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Support_for_text.2Fsyntax.2Fmarkup_driven_or_WYSIWYG_editable_charts.2C_diagrams.2C_graphs.2C_flowcharts_etc. 
+
+Should this project be still listed in that page? If not, please remove it. If it still makes sense, then it could be moved to the ""Featured projects"" section if it has community support and mentors.",1385912632,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Is there an interest in proposing this project for Outreach Program for Women?
+If so, and if there at least one mentor for it. please move it to the ""Featured projects"" section. This way it will be automatically transcluded in
+https://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7
+
+Thank you!",1383164696,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","Correction, the links are: [[mw:Extension:WikiTeX]] (and [[mw:Extension:WikiTex]]).",1379434198,PHID-USER-wuic4cpqakaykj6cpvt5,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+"Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)","What about reviving [[Extension:WikiTeX]] (not to be confused with [[Extension:WikiTex]])? This would have done graphs, plots, and more. It would be handy for it to also support simple circuit diagrams.",1379433154,PHID-USER-wuic4cpqakaykj6cpvt5,False,PHID-TASK-khbn3xwnzxzqjmsvryrq,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"See https://github.com/mdevils/node-jscs
+
+This is the first tool I've seen in the category of asserting coding style for javascript that actually looks like it is worth looking into further.
+
+I intend to experiment with it in the near future for 1 or 2 projects, first in non-voting mode and perhaps later to become a standard enabled job for many projects.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1379415660,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2mkgo6douokimv6febmw,task_description,resolved
+Jenkins: Use node-jscs as checkstyle for javascript coding style,">>! In T56218#973118, @adrianheine wrote:
+> Cool, thanks. I added `npm test`, although I didn't go through grunt since we are not running any other grunt jobs, yet:
+> 
+> * Wikibase: https://gerrit.wikimedia.org/r/#/c/184591/
+> * integration/config: https://gerrit.wikimedia.org/r/#/c/184592/
+
+That's quite alright. If you don't need do run bash commands like `mv`, `cp`, `rm`, `ln` etc. which might not work cross-platform if put inside `scripts.test` (so you'll want to use a nodejs script or Grunt task for that); Running programs like jscs and jshint directly is perfectly fine and actually quite common. I've recently started to use this more often as well. Only use Grunt when there's a need for it. This avoids added complexity, needless abstraction, and indirect dependencies on the underlying framework (e.g. jscs/jshint) which can be quite annoying since it doesn't like being pinned to a direct version that way.
+
+http://blog.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool/
+http://ponyfoo.com/articles/choose-grunt-gulp-or-npm",1426088335,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Cool, thanks. I added `npm test`, although I didn't go through grunt since we are not running any other grunt jobs, yet:
+
+* Wikibase: https://gerrit.wikimedia.org/r/#/c/184591/
+* integration/config: https://gerrit.wikimedia.org/r/#/c/184592/",1421144139,PHID-USER-m2zne2efu3rgmre73nl7,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,">>! In T56218#972923, @adrianheine wrote:
+> Is there work being done to get this run on ci? I'd like to push this for Wikibase as well :)
+
+You will need a package.json and a npm 'test' entry point with a devDependencies for grunt-jscs.  From there we can add a Jenkins job that invokes 'npm test' and that should run jscs.
+
+Example:
+
+https://gerrit.wikimedia.org/r/#/c/100732/
+
+More details at https://www.mediawiki.org/wiki/Continuous_integration/Test_entry_points#JavaScript :-)",1421140918,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,Is there work being done to get this run on ci? I'd like to push this for Wikibase as well :),1421137099,PHID-USER-m2zne2efu3rgmre73nl7,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,Sounds good to me Timo. That nicely scale up CI to developers :-),1409164241,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"The bug is to figure out how to properly do it. Which I define by hacking it together for one repo, and as you repeat it for more repos you refine it until it seems sensible/maintainable.
+
+I think we've reached that point. Any further repos that want it, can enable it the same way other pipelines are introduced. By patching their Gruntfile or adding a new npm-test pipeline.",1409154874,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Is this intended to be a tracking bug for every repo, a bug for it to be done automatically for all repos and then repos that now break need to fix themselves, or can it be marked as FIXED?",1395766504,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 111963 merged by jenkins-bot:
+Set up node-jscs via Grunt (and pass it)
+
+https://gerrit.wikimedia.org/r/111963",1395730881,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 111963 had a related patch set uploaded by Krinkle:
+[WIP] Set up node-jscs via Grunt (and pass it)
+
+https://gerrit.wikimedia.org/r/111963",1391746605,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 100732 merged by jenkins-bot:
+Set up node-jscs, pass it, and configure in local Gruntfile
+
+https://gerrit.wikimedia.org/r/100732",1387317987,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 100732 had a related patch set uploaded by Krinkle:
+Set up node-jscs, pass it, and configure in local Gruntfile
+
+https://gerrit.wikimedia.org/r/100732",1386727450,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Now merged locally in the repo for VisualEditor, and appears to be adding value; moving back to NEW for consideration to be added to jenkins for automated running.",1386355646,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 99596 merged by jenkins-bot:
+Set up node-jscs, pass it, and configure in local Gruntfile
+
+https://gerrit.wikimedia.org/r/99596",1386355303,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"Change 99596 had a related patch set uploaded by Krinkle:
+Set up node-jscs, pass it, and configure in local Gruntfile
+
+https://gerrit.wikimedia.org/r/99596",1386297732,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,"node-jscs would be purely for coding style, not code quality (which is what jshint is primarily for).
+
+Although there are a few minor things that jshint does in the realm of coding style, those are arguably code quality as well (like using of braces in if/else blocks).
+
+This would allow us to validate the complete coding style (especially with regards to whitespace), which right now is mostly enforced by leaving comments in code review and fixup commits pointing to [[mw:CC/JS]].",1379461361,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,Unrelated.,1379460821,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+Jenkins: Use node-jscs as checkstyle for javascript coding style,Is that a replacement for JSHint or unrelated?,1379433243,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2mkgo6douokimv6febmw,task_subcomment,NA
+VisualEditor: Language link dialog should show language names and two-letter codes,"e.g. fr -> Français, cy -> Cymraeg
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379014140,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-w7k7v4pcanwqeehqmoyp,task_description,resolved
+VisualEditor: Language link dialog should show language names and two-letter codes,"Change 98284 merged by jenkins-bot:
+Show full language names in the MW language dialog
+
+https://gerrit.wikimedia.org/r/98284",1386694855,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w7k7v4pcanwqeehqmoyp,task_subcomment,NA
+VisualEditor: Language link dialog should show language names and two-letter codes,"Change 98284 had a related patch set uploaded by Esanders:
+Show full language names in the MW language dialog
+
+https://gerrit.wikimedia.org/r/98284",1385827780,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-w7k7v4pcanwqeehqmoyp,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Around the time when VE started to support editing of pres we started to get dirty diffs like this:
+
+http://www.mediawiki.org/w/index.php?title=Parsoid&diff=779292&oldid=777387
+
+This might either be a selser issue, or VE dirtying the DOM.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379007960,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-six3hr3num5ryuty64kf,task_description,resolved
+VisualEditor: <pre> tags have leading whitespace removed,*** Bug 53775 has been marked as a duplicate of this bug. ***,1379613849,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Change 84896 merged by Catrope:
+Fix check for preformatted when stripping whitespace
+
+https://gerrit.wikimedia.org/r/84896",1379545395,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Change 84896 had a related patch set uploaded by Catrope:
+Fix check for preformatted when stripping whitespace
+
+https://gerrit.wikimedia.org/r/84896",1379545270,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Change 84332 merged by jenkins-bot:
+Fix check for preformatted when stripping whitespace
+
+https://gerrit.wikimedia.org/r/84332",1379466707,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"Change 84332 had a related patch set uploaded by Esanders:
+Fix check for preformatted when stripping whitespace
+
+https://gerrit.wikimedia.org/r/84332",1379346257,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: <pre> tags have leading whitespace removed,"There's a check tag on the edit, so VE dirtied something somewhere. That may or may not explain the whole bug, but we should fix it.",1379008191,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-six3hr3num5ryuty64kf,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"For BLP's and disambiguation pages on the English Wikipedia, an extra edit notice is provided through the https://en.wikipedia.org/wiki/Wikipedia:EDITINTRO system using Extension:InputBox and some code in MediaWiki:Common.js. VisualEditor does not work with Extension:InputBox, so the edit notice is not displayed. 
+
+This hack is being used in several Wikimedia wikis besides the English Wikipedia:
+
+* https://ja.wikipedia.org/wiki/MediaWiki:Common.js
+* https://zh.wikipedia.org/wiki/MediaWiki:Common.js
+* https://vi.wikipedia.org/wiki/MediaWiki:Common.js
+
+See also [[https://www.wikidata.org/wiki/Q10566946| Template:BLP editintro (Q10566946)]] and [[https://www.wikidata.org/wiki/Q14400704|  Template:Disambig editintro (Q14400704) ]] for more of the potentially affected wikis.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378929900,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-4a5risai7mr4y6na4dug,task_description,resolved
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931573 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Support '&editintro=…' etc. on subsequent loads via page tabs%%%
+https://gerrit.wikimedia.org/r/931573",1689089611,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931572 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Support '&editintro=…' etc. on back/forward and VE/NWE switch%%%
+https://gerrit.wikimedia.org/r/931572",1689089607,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931571 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Fix '&editintro=…' not working on Vector with some settings%%%
+https://gerrit.wikimedia.org/r/931571",1687373904,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Thank you @Ryasmeen, I figured out why that was happening. It was only broken when using single edit tab mode, and I didn't think to test that before.
+
+I also fixed the other issue, so after these changes, the message should appear after the editor is opened again as well.",1687256236,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931573 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Support '&editintro=…' etc. on subsequent loads via page tabs%%%
+https://gerrit.wikimedia.org/r/931573",1687256107,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931572 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Support '&editintro=…' etc. on back/forward and VE/NWE switch%%%
+https://gerrit.wikimedia.org/r/931572",1687256105,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 931571 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Fix '&editintro=…' not working on Vector with some settings%%%
+https://gerrit.wikimedia.org/r/931571",1687256103,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"It seems the edit intro message is appearing only when you load the page following the link that has the 'editintro' url parameter. But, it's still not showing the edit notice when you click on the 'Edit' button directly on the same page which I think what the new patch was for? 
+
+
+>>! In T56029#8889645, @gerritbot wrote:
+> Change 923769 **merged** by jenkins-bot:
+> %%%[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget.init: Support '&editintro=…' in edit links%%%
+> https://gerrit.wikimedia.org/r/923769
+
+Here is the screen capture of the issue. Also, it seems the URL on the address bar is different from what it shows when you hover over the Edit link:
+{F37101586}
+
+This is different from the special case @matmarex mentioned here:
+
+>>! In T56029#8890073, @matmarex wrote:
+> This should make the edit intros work.
+> 
+> There's one known issue: the edit intro message only appears the first time the editor is opened after loading/refreshing the page. (Afterwards editor initialization is done differently, and adding this feature without messing up the browser back/forward navigation proved difficult.) We should probably file a separate task about this.
+
+",1686587044,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"This should make the edit intros work.
+
+There's one known issue: the edit intro message only appears the first time the editor is opened after loading/refreshing the page. (Afterwards editor initialization is done differently, and adding this feature without messing up the browser back/forward navigation proved difficult.) We should probably file a separate task about this.",1685471894,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 923769 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget.init: Support '&editintro=…' in edit links%%%
+https://gerrit.wikimedia.org/r/923769",1685467180,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 923769 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] DesktopArticleTarget.init: Support '&editintro=…' in edit links%%%
+https://gerrit.wikimedia.org/r/923769",1685320256,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"This already almost works. The API used by VE to fetch edit notices supports the 'editintro' parameter. In fact, if you follow this link, you'll see the notice: <https://en.wikipedia.org/w/index.php?title=Jasmin_Fejzić&veaction=edit&editintro=Template:BLP_editintro>. But if you just click ""Edit"" on the same page, you won't. This probably only needs a tiny bit of glue code to parse the parameters from the ""Edit"" link, like we're already parsing them from the URL.",1681952881,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Just to make you know: in ruwiki, we adapted RockMFR's ""magic editintros"" to work with VisualEditor (although the resultant script is rather hackish), see https://ru.wikipedia.org/wiki/MediaWiki:Gadget-blpEditNotice.js.",1533665741,PHID-USER-p6gpvwnc6ske65oxuoof,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Just to make you know: in ruwiki, we adapted RockMFR's ""magic editintros"" to work with VisualEditor (although the resuntant script is rather hackish), see https://ru.wikipedia.org/wiki/MediaWiki:Gadget-blpEditNotice.js.",1533665333,PHID-USER-p6gpvwnc6ske65oxuoof,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 329796 merged by jenkins-bot:
+Add editintro to notices
+
+[[https://gerrit.wikimedia.org/r/329796]]",1483474748,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"Change 329796 had a related patch set uploaded (by Esanders):
+Add editintro to notices
+
+[[https://gerrit.wikimedia.org/r/329796]]
+",1483203828,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,I think it is better than editintro+JS yes.,1434999463,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"One way to fix this, as @Cenarium has observed, would be to fix {T85372} and switch wiki(?s) over to use that instead; is this the best option?",1434985888,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,">>! In T56029#945042, @Cenarium wrote:
+>
+> Adding support in VE for preload / editintro is still worthy on its own, but it looks like this task is a duplicate of T51622.
+
+Now Merging.",1434824530,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,">>! In T56029#1098976, @Cenarium wrote:
+> I've uploaded a patch for this (per-category editnotices) : [[https://gerrit.wikimedia.org/r/#/c/189178/|commit 189178]].
+
+I've updated the patch, it works properly now.",1432586632,PHID-USER-znn4xfvlp7e7mr2g3tvl,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,I've uploaded a patch for this (per-category editnotices) : [[https://gerrit.wikimedia.org/r/#/c/189178/|commit 189178]].,1425821786,PHID-USER-znn4xfvlp7e7mr2g3tvl,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,">>! In T56029#800523, @TheDJ wrote:
+> alternatively, get away from this specific implementation and try to move it into core as ""category based edit notices"" and VE gets the notice for free.
+
+I've created a specific task for per category editnotices, T85372, I had already suggested it for the more general T20596 but this didn't get implemented. 
+FYI, the English Wikipedia isn't the only wiki to use this.
+Adding support in VE for preload / editintro is still worthy on its own, but it looks like this task is a duplicate of T51622.",1419691441,PHID-USER-znn4xfvlp7e7mr2g3tvl,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"alternatively, get away from this specific implementation and try to move it into core as ""category based edit notices"" and VE gets the notice for free.",1417508902,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,"To work as desired VE would need to respect the editintro= url parameter. For example
+http://en.wikipedia.org/wiki/Paul_Bahn?veaction=edit&editintro=Template:BLP_editintro
+and use that to fill in the edit notice with Template:BLP_editintro.
+A couple of lines in MediaWiki:Common.js would add the parameters to URL's for all BLPs.",1378970400,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Provide support for BLP edit notices on enwiki,Link for InputBox https://www.mediawiki.org/wiki/Extension:InputBox,1378969899,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-4a5risai7mr4y6na4dug,task_subcomment,NA
+VisualEditor: Investigate where we can replace setTimeouts with EventSequencer,"For example, onBeforePaste/onAfterPaste in ve.ce.Surface
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378834020,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wh766os42bllzvmszxya,task_description,open
+VisualEditor: Investigate where we can replace setTimeouts with EventSequencer,"Thanks, looks like I hadn't properly updated my copy of VE to master. :P",1378839634,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-wh766os42bllzvmszxya,task_subcomment,NA
+VisualEditor: Investigate where we can replace setTimeouts with EventSequencer,"(In reply to comment #1)
+> Got a reference doc for EventSequencer?
+
+https://doc.wikimedia.org/VisualEditor/master/#!/api/ve.EventSequencer",1378839518,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wh766os42bllzvmszxya,task_subcomment,NA
+VisualEditor: Investigate where we can replace setTimeouts with EventSequencer,Got a reference doc for EventSequencer?,1378839441,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-wh766os42bllzvmszxya,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"<translate>…</translate> and the related <tvar>…</tvar> are currently un-parsed and shown as plain wikitext in VisualEditor because they're not recognised, per T50891; however, once that is fixed, the blocks won't be editable except as alien nodes (in wikitext), and won't be createable.
+
+Making a proper VisualEditor plugin to translate these in-page as a rich editor shouldn't be particularly hard (he says…).",1378773120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_description,open
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),">>! In T55974#8091892, @Tacsipacsi wrote:
+> I suppose this one, if we can call this a specification at all. I have the feeling that it was simply forgotten that translation syntax needs to be created, not only maintained…
+
+Not forgotten. What has been done so far was a necessary first step and only provides a basic support. The Language team is exploring options how to continue working towards full support. This doesn't mean adding a button or two; we want to take a deeper look to figure out what would actually be a good user experience. ",1658930211,PHID-USER-732lqsmz4v6bss3kln2v,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"I suppose this one, if we can call this a specification at all. I have the feeling that it was simply forgotten that translation syntax needs to be created, not only maintained…",1658336620,PHID-USER-ocqnoktaualicuvge2tu,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),">>! In T55974#8086214, @Tacsipacsi wrote:
+> No, there’s another “minor” caveat the blog post doesn’t mention: you can’t add new markup. The content can be edited, they can be deleted, even copied and pasted, but if there’s no `<translate>` or `<tvar>` tag on the page you edit, there’s no way to create them.
+
+Thanks for this info. Which task/subtask of this task cluster specifies the work (add new markup) that's still to be done?",1658220589,PHID-USER-lbrksgjks7nerhn7d2xm,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"No, there’s another “minor” caveat the blog post doesn’t mention: you can’t add new markup. The content can be edited, they can be deleted, even copied and pasted, but if there’s no `<translate>` or `<tvar>` tag on the page you edit, there’s no way to create them.",1658180714,PHID-USER-ocqnoktaualicuvge2tu,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),Is this task resolved by https://diff.wikimedia.org/2022/05/12/mediawiki-1-38-brings-support-for-editing-translatable-pages-with-the-visual-editor/ ?,1658172925,PHID-USER-bz37wupbujiswpiqntmt,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"I added this issue to MediaWiki Stakeholders' Group/TechConf Input:
+
+https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/TechConf_Input#Improved_Translate_-_VisualEditor_integration
+
+Please add your endorsement if you like to make this issue more visible.",1534491626,PHID-USER-yftvcvsb36qrmx4iohsm,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"I added this issue to MediaWiki Stakeholders' Group/TechConf Input:
+
+https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/TechConf_Input#Improved_Translate_-_VisualEditor_integration
+
+Please add your endorsement if you like make this issue more visible.",1534491589,PHID-USER-yftvcvsb36qrmx4iohsm,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"Also, I don't think I could do this in two weeks, which suggests this is too big for GSoC.",1457021325,PHID-USER-732lqsmz4v6bss3kln2v,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),">>! In T55974#2084495, @Micru wrote:
+> I see that the stalled bug has been marked as resolved, Could this task become a GsoC project?
+
+Eventually, yes; however this was missing a few dependencies, T49344 chief amongst them. That work might not be done for another year or more.",1457021192,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),,1555396632,PHID-USER-my5s6nat437le6q5fq7d,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),,1457021044,PHID-USER-my5s6nat437le6q5fq7d,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),">>! In T55974#1042621, @Qgil wrote:
+> If there is no interest / critical mentoring mass to promote this project for GSoC / Outreachy, then maybe the current ""Normal"" priority should be lower?
+
+It's not a matter of priority, see blockers: this is blocked on a stalled bug.",1424596006,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"If there is no interest / critical mentoring mass to promote this project for GSoC / Outreachy, then maybe the current ""Normal"" priority should be lower?",1424130694,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"Wikimedia will [[ https://phabricator.wikimedia.org/T921 | apply to Google Summer of Code and Outreachy ]] on Tuesday, February 17. If you want this task to become a featured project idea, please follow [[ https://phabricator.wikimedia.org/project/view/1042/ | these instructions ]]. ",1423662273,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"Is it true that parsoid has limitations parsing tags other than ""normal parser tags"". If yes what are they & why ? I want to make a plugin for VE to embed translate extension as mentioned above. Cant i include my own grammar for parser to do stuffs way i want.?",1422107606,PHID-USER-cqpeh4jvvexbszsxogrw,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"Pankaj: This bug depends on fixing bug 48891 first (see the ""Depends on"" field). If something is unclear with comment 0, please explain what is unclear and why. Also see [[mw:Annoying little bugs]].",1394440778,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension),"**pankaj10it45** wrote:
+
+Hello,I want to work on this bug.Can you tell me what exactly it is?
+Thank you.",1394405522,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-oxphbzmhqbxzbsixhfq4,task_subcomment,NA
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,,1378691520,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_description,resolved
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,"Change 255931 merged by jenkins-bot:
+Use white-space: pre-wrap instead of using &nbsp; for spaces
+
+[[https://gerrit.wikimedia.org/r/255931]]",1448930482,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_subcomment,NA
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,"Change 255931 had a related patch set uploaded (by Bartosz Dziewoński):
+Use white-space: pre-wrap instead of using &nbsp; for spaces
+
+[[https://gerrit.wikimedia.org/r/255931]]
+",1448813669,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_subcomment,NA
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,"Still valid:
+```
+./src/ce/nodes/ve.ce.TextNode.js:		// Replace spaces with &nbsp; where needed
+```",1426789095,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_subcomment,NA
+VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces,"From an email conversation I had with Aryeh in January 2012:
+
+(Since I'm thinking about canonicalization of whitespace, a tip: set
+white-space: pre-wrap on any contenteditable regions you use, and
+wherever you use them.  This will stop you from needing to use nbsp's
+in ways they were never intended to be used, which causes a variety of
+subtle bugs.  See
+<http://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#canonical-space-sequences>
+for a basic explanation, and click the first ""View Comments"" at
+<http://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#the-inserttext-command>
+for a more detailed explanation of how nbsp substitution works in
+practice.)",1378691662,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-sc56jdm4lxt6le2zxeuz,task_subcomment,NA
+"VisualEditor: Hide ""version false"" in the help menu if it can't be shown","== Steps ==
+1) Go to
+https://www.mediawiki.org/wiki/BUG?veaction=edit&uselang=en
+2) Click on ""BETA""
+
+== Actual result ==
+There is the text ""Version false"" generated by the HTML:
+
+<div>
+ <span class=""ve-init-mw-ViewPageTarget-version-label"">Version</span> 
+ <a class=""ve-init-mw-ViewPageTarget-version-link""
+    target=""_blank""
+    href=""false"">false</a> 
+ <span class=""ve-init-mw-ViewPageTarget-version-date""></span>
+</div>
+
+== Expected result ==
+There should be some version number instead of the ""false"" text
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378656660,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-7wslc7ru3hkj3phtleql,task_description,resolved
+"VisualEditor: Hide ""version false"" in the help menu if it can't be shown","Yes, this was exposed as part of bug 53050, but due to bug 53972 in how code is currently deployed to the WMF cluster, we can't actually make this available outside of Beta Labs (boo). Consequently this was fixed in gerrit 84334 two weeks ago before it hit ""real"" production wikis (non-MW.org).",1380740276,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7wslc7ru3hkj3phtleql,task_subcomment,NA
+"VisualEditor: Hide ""version false"" in the help menu if it can't be shown","I don't see false anymore, but currently there is no element whose class contains ""ve-init-mw-ViewPageTarget-version"" either. Was this removed on purpose?",1380708958,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-7wslc7ru3hkj3phtleql,task_subcomment,NA
+"VisualEditor: Hide ""version false"" in the help menu if it can't be shown","I dont see 'false' on mw or en.wp.  I see 'beta'.
+
+Is the originally reported problem fixed, or masked somehow.
+
+I notice that version says '0.1.0', which is not useful as there have been many deploys of the code.  beta's should have build numbers or build dates for each release.
+
+https://www.mediawiki.org/wiki/Special:Version
+
+e.g. ULS is 'Version 2013-06-17'",1380678404,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-7wslc7ru3hkj3phtleql,task_subcomment,NA
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,"Article tabs are wrong when page is protected via cascading from another page.
+
+To reproduce: visit https://pl.wikipedia.org/wiki/Wikipedia:Strona_główna?uselang=en and behold the ""Edit source"" link, even if you're anonymus.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=11700",1378575540,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_description,resolved
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,"Change 128965 merged by jenkins-bot:
+Check cascade protection and show notice if relevant
+
+https://gerrit.wikimedia.org/r/128965",1398277452,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_subcomment,NA
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,"Change 128965 had a related patch set uploaded by Alex Monk:
+Check cascade protection and show notice if relevant
+
+https://gerrit.wikimedia.org/r/128965",1398192310,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_subcomment,NA
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,"Did something change here? MW shows an edit tab on these pages. If you turn on VE then it changes that ""Edit"" to ""Edit source"" and adds a new ""Edit"", which is what I would expect it to do.
+
+What probably should be done is showing the cascade notice on VE though.",1397779435,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_subcomment,NA
+VisualEditor: Protection edit notice should also show when under cascaded protection from another page,*** Bug 58452 has been marked as a duplicate of this bug. ***,1386959355,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-m6zybnoobh3hwy2qmm6n,task_subcomment,NA
+provisioning browsertests role fails,"I added role ""browsertests"", but every time I run `vagrant provision` it fails. It seems to be trying to install an ""ffi"" (foreign function interface) module.
+
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Using rake (10.1.0)
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Using builder (3.2.2)
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): 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)
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice):
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice):         /usr/bin/ruby1.9.1 extconf.rb
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice):
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Gem files will remain installed in /home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.0 for inspection.
+Fri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Results logged to /home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.0/ext/ffi_c/gem_make.out
+
+gem_make.out has only:
+   /usr/bin/ruby1.9.1 extconf.rb
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69874",1378503240,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_description,resolved
+provisioning browsertests role fails,Forgot to tag the commit in https://gerrit.wikimedia.org/r/#/c/158564/ but the patch should have fixed this and other bugs related to botched ffi compilation. A good handful of the most problematic gems are now installed from packages.,1410462222,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"After profiling the `bundle install` process, I'm seeing around 128M as the peark memory usage. That seems like a reasonable amount of free memory to expect on the VM considering some of the other memory intensive processes that need to run (xvfb/firefox in browser testing, for example, uses around 192M).",1408742280,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,The ruby-ffi package is for Ruby 1.9. Perhaps we should try switching back to a shared directory for bundler gems. That would at least mitigate the failures by only performing ffi compilation (and other native gem compilation) once.,1408736249,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,Can we do `apt-get install ruby-ffi` instead of compiling ffi with bunder?,1408727122,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Is this still an active problem? The browsertests role has been removed, but there are now several extension specific roles which install gems via bundler to provide testing support.",1408494405,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"I managed to get tests running after increasing memory size to 1024. Is it possible to increase memory size just when gems are installing, and then decrease it back to 512?",1380204683,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Found it. Mediawiki-Vagrant[1] says to edit Vagrantfile-extra.rb. Now VM memory size is 1024.
+
+$ vagrant halt
+edit Vagrantfile-extra.rb
+$ vagrant up
+$ VBoxManage showvminfo ...
+...
+Memory size: 1024MB
+...
+
+1: https://www.mediawiki.org/wiki/Mediawiki-Vagrant",1380202260,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"I have tried this.
+
+#1 $ vagrant halt
+
+#2 changed
+
+vb.customize ['modifyvm', :id, '--memory', '768']
+
+in Vagrantfile to
+
+vb.customize ['modifyvm', :id, '--memory', '1024']
+
+#3 $ vagrant up
+   $ vagrant provision
+
+but both ""VBoxManage showvminfo"" and ""Oracle VM VirtualBox Manager"" still say ""Memory size: 768MB"".",1380201351,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Created attachment 13384
+VBoxManage showvminfo
+
+**Attached**: {F11493}",1380201068,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Created attachment 13383
+vagrant provision
+
+**Attached**: {F11492}",1380201049,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"I have the same problem. I will attach output of ""vagrant enable-role browsertests"" and ""VBoxManage showvminfo"".
+
+How do I increase VM memory size? (Looks like it is 768MB now.)
+
+In Vagrantfile[1] or ""Oracle VM VirtualBox Manager > VM > right click > Settings > System > Base Memory""?
+
+1: https://github.com/wikimedia/mediawiki-vagrant/blob/master/Vagrantfile#L65",1380201013,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"(In reply to comment #5)
+> I increased the VM to 1024, `vagrant halt` `vagrant up`!
+... that should have continued ""and the vagrant provision complete successfully, and I can run tests!""  Yay, thanks for the memory suggestion.
+
+(In reply to comment #6)
+> the way to resolve this is to document...
+I added something, https://www.mediawiki.org/w/index.php?title=MediaWiki-Vagrant&diff=783886&oldid=781408
+
+> ... one should try freeing some memory in the VM
+You mean by temporarily disabling other roles until vagrant provisions browsertests successfully?  I didn't try stopping apache/mysql/parsoid/redis in the vagrant VM, because I assumed `vagrant provision` would have restarted them before running the ruby gem bundler.
+
+I guess the opaque exception reporting is an upstream issue.",1379308175,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"(In reply to comment #5)
+> I increased the VM to 1024, `vagrant halt` `vagrant up`!
+
+And -- did it work? I guess it did, because you later speak of ""successful and unsuccessful runs"".
+
+I don't think it's viable to keep increasing the default RAM allocation just so that this one Gem can compile, so the way to resolve this is to document the fact that compiling the ffi Gem is a memory-hungry task and that if it fails one should try freeing some memory in the VM or increasing the RAM allocation.",1379306284,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Created attachment 13289
+output of `vboxmanage showvminfo ...` before I increased VM memory
+
+**Attached**: {F11491}",1379305914,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"Thanks for the updates. I did not modify the VM's memory size.
+Maybe the difference between me and Chris is my roles include eventlogging, gettingstarted (which loads redis) and visualeditor+parsoid.
+
+I increased the VM to 1024, `vagrant halt` `vagrant up`!
+
+In the vagrant VM, on both successful and unsuccessful runs, puppet spends many minutes running
+/usr/bin/ruby /usr/bin/bundle install --path /home/vagrant/.gem
+with no output.
+
+/home/vagrant/.gem/ruby/1.9.1/gems contains a bunch of old gems from May14, and the new revisions of gems from this run.
+
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:28 builder-3.2.0
+drwxr-xr-x  6 vagrant vagrant 4096 Sep  6 22:14 builder-3.2.2
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:35 childprocess-0.3.9
+drwxr-xr-x  6 vagrant vagrant 4096 May 14 04:35 chunky_png-1.2.8
+drwxr-xr-x 10 vagrant vagrant 4096 May 14 04:44 cucumber-1.3.1
+drwxr-xr-x  6 vagrant vagrant 4096 May 14 04:45 data_magic-0.14
+drwxr-xr-x  7 vagrant vagrant 4096 May 14 04:35 diff-lcs-1.2.4
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:44 faker-1.1.2
+drwxr-xr-x  7 vagrant vagrant 4096 May 14 04:29 ffi-1.8.1
+drwxr-xr-x  7 vagrant vagrant 4096 Sep 16 03:50 ffi-1.9.0    <--- the problem
+drwxr-xr-x 10 vagrant vagrant 4096 May 14 04:35 gherkin-2.12.0
+drwxr-xr-x  5 vagrant vagrant 4096 May 14 04:44 i18n-0.6.4
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:35 multi_json-1.7.3
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:45 net-http-persistent-2.8
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:45 page_navigation-0.9
+drwxr-xr-x  5 vagrant vagrant 4096 May 14 04:45 page-object-0.8.10
+drwxr-xr-x  4 vagrant vagrant 4096 May 14 04:45 parallel-0.6.4
+drwxr-xr-x  5 vagrant vagrant 4096 May 14 04:45 parallel_tests-0.12.3
+drwxr-xr-x  6 vagrant vagrant 4096 May 14 04:28 rake-10.0.4
+drwxr-xr-x  6 vagrant vagrant 4096 Sep  6 22:14 rake-10.1.0",1379305740,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,Apparently having two different people attempt to verify your report is not quite enough to warrant a follow-up. Closing as invalid.,1379144075,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.],1378939542,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,"I ran into this problem before. If I recall correctly, it's an out-of-memory error that bundler is unhelpfully catching and re-throwing as an uninformative generic exception. The memory requirements of building the ffi gem were the original impetus for bumping the VM's memory allocation to 768 Mb, but since we've done that I have not run into this problem. Have you modified the VM's memory allocation setting at all?
+
+If you have not modified the VM, can you reproduce the output of ""vboxmanage showvminfo""? It should be invoked with the machine's UUID as the final command-line argument. The UUID can be found in .vagrant/machines/default/virtualbox/id, which should exist under your Vagrant repo root.",1378632611,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+provisioning browsertests role fails,I was not able to reproduce this in a fresh VM,1378503546,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-da2sdjr5nuneldb7hbcy,task_subcomment,NA
+VisualEditor: Pasting text into VE from external text processor removes newlines,"System environment:
+Win7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a page
+Edit it in VE
+Copy-paste the following text:
+a
+b
+c
+d
+e
+
+Expected output:
+a
+b
+c
+d
+e
+
+Actual output:
+abcde
+
+The problem has been tested with notepad++ as the external editor, with line endings in windows format (CRLF), UNIX format (LF) and MAC format (CR). Newline is not copied in any of the cases.
+
+The problem has also been tested by trying to copy-paste html text from chrome itself. Newline is not copied.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52096",1378418160,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-3yhieue5lg5ipuzhildn,task_description,resolved
+VisualEditor: Pasting text into VE from external text processor removes newlines,"Change 86664 merged by jenkins-bot:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1385500082,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3yhieue5lg5ipuzhildn,task_subcomment,NA
+VisualEditor: Pasting text into VE from external text processor removes newlines,Works with gedit & chrome with the rich paste patch.,1381157678,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3yhieue5lg5ipuzhildn,task_subcomment,NA
+VisualEditor: Pasting text into VE from external text processor removes newlines,"Change 86664 had a related patch set uploaded by Esanders:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1381157509,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3yhieue5lg5ipuzhildn,task_subcomment,NA
+VisualEditor: Pasting text into VE from external text processor removes newlines,"Confirmed in Firefox 23 / Xubuntu Linux / Monobook
+
+Using kwrite:
+Tested with \n  \r and \r\n end of lines and it makes no difference.
+Tested also using UTF-8, UTF-16, ISO-8859-1, ISO-8859-2 and Windows-1258 encodings.
+
+Also tested copying from this page viewed in Firefox, Konqueror and Linuks, from a PDF, a text file in a terminal, and again from kwrite using the following:
+
+a
+
+b
+
+c
+
+d
+
+e
+
+None of it makes the slightest bit of difference.
+
+https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox3&diff=571705481&oldid=571089410 is the copy from comment 0",1378420228,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3yhieue5lg5ipuzhildn,task_subcomment,NA
+"Lazy load extensions' large resources in VisualEditor, rather than blocking load","Extensions such as Math or SyntaxHighlight may require the inclusion of large(ish) JS libraries. It would be good if we didn't load these on every VE page load, but rather when these elements are present, or become present (e.g. I add a formula to a new document)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378414320,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nydh4gpoq4wxodchwgi3,task_description,open
+mw.config doesn't expose page existence information about the target of a special page,"For special pages, no information about page existence is exposed to mw.config, which means that VisualEditor is forced to assume it exists regardless.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66885",1378324980,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_description,resolved
+mw.config doesn't expose page existence information about the target of a special page,"Change 169639 merged by jenkins-bot:
+Expose ID of relevant page in JS variables
+
+https://gerrit.wikimedia.org/r/169639",1416369714,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"Change 169639 had a related patch set uploaded by Alex Monk:
+Expose ID of relevant page in JS variables
+
+https://gerrit.wikimedia.org/r/169639",1414545533,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"'wgRelevantArticleId' => WikiPage::factory( $relevantTitle )->getId() perhaps?
+
+I'm not sure we want to introduce new variables here though...",1413833849,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,Sounds like you need the js variable 'wgIsProbablyEditable' or 'wgIsArticle' according to page under 'wgRelevantPageName' or a new variable 'wgRelevantIsProbablyEditable'/'wgRelevantIsArticle' to cover this.,1404280264,PHID-USER-qaoxfiqu6bxhd5ehlwhc,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,This bug is about giving existence information for the relevant article (i.e. the article that the special page is working on). See bug 66885,1403552699,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"(In reply to comment #3)
+> There is wgCanonicalSpecialPageName set, when you are on a special page.
+
+-> WORKSFORME",1384032206,PHID-USER-a6jwrurphpx6yl4coupk,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"There is wgCanonicalSpecialPageName set, when you are on a special page.",1378631680,PHID-USER-a6jwrurphpx6yl4coupk,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"Change 82744 merged by jenkins-bot:
+Reference core bug 53774 in bug 49000 comment
+
+https://gerrit.wikimedia.org/r/82744",1378356954,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+mw.config doesn't expose page existence information about the target of a special page,"Change 82744 had a related patch set uploaded by Jforrester:
+Reference core bug 53774 in bug 49000 comment
+
+https://gerrit.wikimedia.org/r/82744",1378325283,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rzsc7tmlupqbuaedolkl,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**Author:** `kwwilliams`
+
+**Description:**
+When articles contain items that lead VE to corrupt the article, we've been protecting them by wrapping the article with <div class=""ve-ce-protectedNode""> and </div>. This used to keep VE from being able to select any material within the article, which allowed us to keep the article from being corrupted.
+
+VE is now allowing edits to templates inside the article (see https://en.wikipedia.org/w/index.php?title=Teenage_Dream_%28Katy_Perry_album%29&veaction=edit for an example), so we now have no way to protect articles that we know VE cannot handle.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52141",1378317960,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s47345xgplfmgixnp726,task_description,declined
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","(In reply to This, that and the other from comment #13)
+> As it stands, this is a dupe of bug 52141. I've put back the original bug
+> summary; it seems to me that WONTFIX is the appropriate resolution for this
+> bug.
+
+Agreed.",1403741232,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","As it stands, this is a dupe of bug 52141. I've put back the original bug summary; it seems to me that WONTFIX is the appropriate resolution for this bug.",1403416223,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","James, that is bug 52141.  This bug was about a specific problem with the existing code.",1383886236,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","Changing this to ""Provide a way to block VisualEditor from being active on a page""; I worry that this will lead to yet another magic word, but oh well.",1381342100,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","I was very easily able to reproduce this problem; I dont have exact steps to reproduce, but with a few clicks and keypresses in the content area, all content was removed and the text I typed appeared in the body of the article.  Undo appeared to work as expected, however 'Review your changes' did not return any results - it hung, but didnt lock up the browser.  The toolbar is another way to override the protectedNode.
+
+This template is also being used to create a 'pre' text area on
+https://en.wikipedia.org/w/index.php?title=Morse_code&veaction=edit",1380637712,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+Note https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=572094345&oldid=572076135 , where another 26,000 articles that VE mutilates have been identified.
+
+We really need to have a method to shield articles from VE. It's critical to do, and beyond reason to expect that we will always modify articles to conform to VE's expectations.",1378671601,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","I tried again on my test page on a different computer running Firefox 17.0.2 (ESR) under XP.
+
+At first, it seemed that the protected node was working, but at some point (after clicking, double-clicking, typing, ...) I managed to write in the protected node: the result was an even greater mess than before: still the duplication, quotes added all over the place (they seem correct but unnecessary), pipes removed, space added, ...
+
+https://en.wikipedia.org/w/index.php?title=User%3ANicoV%2FTest&diff=571628361&oldid=571542702",1378379690,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+(In reply to comment #6)
+> On the wider point, it's not clear if there's an actual long-term need for a
+> proper VE-prevention system (or if it's all solvable with a few quick fixes
+> of
+> bad wikitext), but if there is, we should build a proper one, not rely on a
+> hack that might break.
+
+What's unclear about that?
+
+I agree that it would be better to do this with a category, but the need for VE to recognise some flag that tells it not to edit a given article seems fairly obvious. As long as VE mutilates pages in response to inputs that behaved reasonably with the working software, we will require a mechanism to tell VE not to edit certain pages.",1378324543,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","(In reply to comment #5)
+> The div has been removed, so people need to look at
+> https://en.wikipedia.org/w/index.
+> php?title=Teenage_Dream_%28Katy_Perry_album%29&oldid=571540632
+
+In this particular case, note that the reason everything was broken in editing this page was because the <ref> was defined outside of the table cell, in a the non-space between the end of the cell and the start of the row, and only happened to ""work"" in WT mode because of HTML Tidy moving it to somewhere sane - Ed's edit to the page fixed the duplication so the desired protection is no longer needed: https://en.wikipedia.org/w/index.php?title=Teenage_Dream_(Katy_Perry_album)&diff=571550633&oldid=571540632
+
+On the wider point, it's not clear if there's an actual long-term need for a proper VE-prevention system (or if it's all solvable with a few quick fixes of bad wikitext), but if there is, we should build a proper one, not rely on a hack that might break.",1378323301,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+The div has been removed, so people need to look at https://en.wikipedia.org/w/index.php?title=Teenage_Dream_%28Katy_Perry_album%29&oldid=571540632",1378322920,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+(In reply to comment #3)
+> According to the documentation, the div is only meant to block editing to a
+> section of a page (although that section can be the whole text), so adding
+> text
+> before is correct, likewise you should be able to add text after the /div.
+It's a change from the original behaviour. I agree that it's not technically wrong.",1378321376,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","According to the documentation, the div is only meant to block editing to a section of a page (although that section can be the whole text), so adding text before is correct, likewise you should be able to add text after the /div.
+
+The editing templates within the div does sound like a bug though.
+
+If VE (or Parsoid possibly) is not treating the div as invariant then the div definitely isn't doing what it was intended to do.",1378320819,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","**kwwilliams** wrote:
+
+Firefox 23.0.1 on Windows 7.
+
+To be clear, we are still prevented from editing the text. We are not prevented from editing templates, and we can insert text before div.",1378319066,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+"VisualEditor: <div class=""ve-ce-protectedNode""> not always preventing editing in VE","The original person to report this noted that they were using Chrome 29 on Windows 7.
+
+I have been unable to reproduce this in Firefox 23 on Linux.
+
+Neither kww or the ip who can reproduce this have noted their system.",1378318792,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-s47345xgplfmgixnp726,task_subcomment,NA
+VisualEditor: Range around an annotated alien calculated incorrectly,"1. Create '<p>Foo<cite>Bar</cite>Baz</p>'
+2. Select Bar
+3. Range is now [4,6] (correct as <cite/> becomes [<alien>,</alien>])
+4. Bold the selection
+5. Range is now [6,6] :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378317600,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ejnmmkuva4ygwqwckki3,task_description,resolved
+VisualEditor: Range around an annotated alien calculated incorrectly,"Change 82771 merged by jenkins-bot:
+Fix getOffsetFrom(Element|Text)Node for annotated aliens
+
+https://gerrit.wikimedia.org/r/82771",1378367478,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ejnmmkuva4ygwqwckki3,task_subcomment,NA
+VisualEditor: Range around an annotated alien calculated incorrectly,"Change 82771 had a related patch set uploaded by Esanders:
+Fix getOffsetFrom(Element|Text)Node for annotated aliens
+
+https://gerrit.wikimedia.org/r/82771",1378339784,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ejnmmkuva4ygwqwckki3,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","[Please move this to a different component if applicable, I'm not sure where the editor comes from.]
+
+It is impossible to insert the ""ę"" or ""Ę"" characters (latin letter ""e""/""E"" with ogonek) from keyboard when editing in Module: namespace with the code editor on the Polish Wikipedia.
+
+""ę"" is inserted on the Polish keyboard using AltGr+e (aka Ctrl+Alt+e). If the editor uses this as a hotkey, it shouldn't (nor should it use any other Ctrl+Alt combinations).
+
+(Reported at https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#VisualEditor_a_polskie_diakrytyki)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378316100,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-psky7k3cs2jglhz37xhh,task_description,resolved
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","This works correctly these days.
+
+It was apparently fixed by https://github.com/ajaxorg/ace/pull/1463 ([[https://github.com/ajaxorg/ace/pull/1463/commits/d4bdfe33001b4c13134515b0fa53b6b64d8b3ee1|d4bdfe33001b4c13134515b0fa53b6b64d8b3ee1]]) – which was already merged when I was filing this bug :) – and we upgraded to that version in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CodeEditor/+/104510 (early 2014).",1702336260,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","This works correctly these days.
+
+It was apparently fixed by https://github.com/ajaxorg/ace/pull/1463 – which was already merged when I was filing this bug :) – and we upgraded to that version in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CodeEditor/+/104510 (early 2014).",1702336181,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","These are all the default defined key combinations:
+https://github.com/ajaxorg/ace/blob/40ea516801332fb8e96f8ba2e5046eece2fd95d3/lib/ace/commands/default_commands.js",1388500776,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","In that case, it looks like you could follow the example in modules/jquery.codeEditor.js near line 151 to disable this command too.",1378324088,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","@Brad, depending on how exactly you remapped it, the Ctrl+Alt+E might be mapped to ""ę"" in some lower-level layer, not letting the browser even see it. (I used this a few times to wrestle with some stupid applications which take Ctrl+Alt shortcuts for themselves to take it away from them.)
+
+Some grepping shows ACE Editor uses ""Ctrl-Alt-E"" / ""Command-Option-E"" for the ""togglerecording"" command. This is most likely the culprit.
+
+This seems to be the only Ctrl-Alt shortcut involving regular letters (there are also a few with arrow keys and backspace).",1378320708,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+"Impossible to insert the ""ę"" character when editing in Module: namespace with the code editor","You want CodeEditor.
+
+I note that I can type ę and Ę fine in CodeEditor from here, where the key combinations are ""<Compose> ; e"" and ""<Compose> ; E"".
+
+I also remapped Ctrl+Alt+E to ""ę"" temporarily, and I was able to enter that character using that key combination in CodeEditor on a module page on plwiki with no issues (using Firefox 24 on Linux).",1378319184,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-psky7k3cs2jglhz37xhh,task_subcomment,NA
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,"* This is language/script specific diacritic specific bug split from {T53472}
+
+* For language Marathi Script Devanagari anuswara diacritic is  ं 
+* If one types the anuswara diacritic  ं  after any devanagari script alphabet it is usually place above the concerned alphabet. For example  क is a Marathi/Devanagari alphabet if I type क+ ं I get  कं  
+* If I place cursor before the cluster कं and press delete then whole cluster gets deleted and that is right way to happen, and this behaviour needs to be retained (since if basic alphabet is not there then no need of anuswara diacritic  ं) .
+* Problem: In Visual Editor if I place cursor after the cluster e.g. after कं and press backspace current behaviour is the whole cluster gets deleted. Example कं + Backspace key = results in whole cluster getting deleted.
+* Expected behaviour is: Cluster with anuswara diacritic (कं) + Backspace key = retain rest of cluster(retain क ) and only anuswara diacritic  ं should get deleted.
+* Reason: During spell correction many times we need to retain rest of the cluster and only change the diacritics. For anuswara   ं diacritic spell change is required frequently for various reasons like change in singular-plural tense. Every time retyping the whole cluster is cumbersome. Traditional Source editing behaviour is proper and expected and problem is coming only with VisualEditor behaviour.
+* For example please see this https://mr.wikipedia.org/w/index.php?title=कृष्ण_श्रीनिवास_अर्जुनवाडकर&diff=1198833&oldid=1198826 edit difference a user had to change this diacritic at several places.
+
+Since users would be reluctant to use VE without correct behaviour, I would prefer this being treated as a bug not just enhancement and to have  fair importance level.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378306620,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-6g646hsi3p3j73jyxxaz,task_description,resolved
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,I'm provisionally deeming this fixed. We changed this behaviour significantly since this was filed. Please re-open if you find issues.,1449602907,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6g646hsi3p3j73jyxxaz,task_subcomment,NA
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,">>! In T55754#549797 in October 2013, @Jdforrester-WMF wrote:
+> we're switching back to native cursoring and backspacing, which hopefully will fix this
+
+@Mahitgar: Do you know if this is still a problem in Devanagari? (I'm afraid I'm missing input method skills to test this myself.)",1425552598,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6g646hsi3p3j73jyxxaz,task_subcomment,NA
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,"Retitled for clarity; we're switching back to native cursoring and backspacing, which hopefully will fix this, but keeping this open and distinct in case not.",1381274519,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6g646hsi3p3j73jyxxaz,task_subcomment,NA
+VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient,"Per Bug 51472#c4 , the grapheme cluster handling for backspace is to be on a per script basis. So, this should be treated as the bug for specifically devanagari.
+
+Also note that I am confirming the bug for hindi.
+
+To further clarify the original report, devanagari has various diacritics which can be applied to base unicode characters. It also has a combining character halant (viram) ् (U+094D).
+
+Currently, pressing backspace after a grapheme cluster containing one or more base characters with one or more diacritics and/or combining character deletes the entire grapheme cluster. This is not desired behaviour. Pressing delete before a cluster deletes the entire cluster. This is desired behaviour.
+
+Examples of diacritics: ँ (Chandrabindu) U+0901 ं (Bindu) U+0902 etc.
+
+Examples of grapheme clusters:
+
+One base character with one diacritic: कं ( क + ं ), कँ ( क + ँ ), कः ( क + ः )
+
+One base character with multiple diacritics: किं ( क + ि + ं )
+
+Multiple base characters with halant: श्र ( श + ् + र ), क्ष ( क + ् + ष ), प्र ( प + ् + र )
+
+Multiple base characters with halant followed by diacritics: श्रिं (श + ् + र + ि + ं), क्षि ( क + ् + ष + ि ), प्रे ( प + ् + र + े )
+
+System environment:
+Win7 X64
+Google Chrome 29.0.1547.62 m
+Page used for testing: [[:w:hi:User:Siddhartha Ghai/sandbox]]
+
+Expected behaviour:
+Only one diacritic (the last one in the grapheme), ie one unicode character, is to be deleted. The rest of the grapheme cluster is to stay intact.
+
+Examples used (not exhaustive):
+Grapheme -> Grapheme after pressing backspace
+कं -> क
+कँ -> क
+कः -> क
+क् -> क
+किं -> कि
+श्र -> श्
+क्ष -> क्
+प्र -> प्
+श्रिं -> श्रि
+क्षि -> क्ष
+प्रे -> प्र
+
+Current behaviour (blank indicates entire grapheme cluster was removed) (these results should be verified on other browser/OS combinations):
+कं -> 
+कँ -> 
+कः -> 
+क् -> 
+किं ->
+श्र -> श्  (Working correctly)
+क्ष -> क् (Working correctly)
+प्र -> प् (Working correctly)
+श्रिं -> श् (Deletes र + ि + ं , ie three unicode characters instead of one)
+क्षि -> क् (Deletes ष + ि , ie two unicode characters instead of one)
+प्रे -> प् (Deletes र + े , ie two unicode characters instead of one)
+
+Points to note:
+Some IMEs may provide non-normalized input for characters such as फ़ (U+095E) in place of फ (U+092B) + ़ (U+093C), ढ़ (U+095D) in place of ढ (U+0922) + ़ (U+093C) etc. In such cases, the user may expect that pressing a backspace will only eliminate the diacritic, not the entire grapheme. So, VE may have to handle normalization in such cases.
+
+Results seem to indicate that halant is partially correctly handled. letter + halant + letter + backspace gives letter + halant correctly. But
+letter + halant + backspace, instead of giving the letter, deletes the entire grapheme.
+
+The remaining diacritics as of unicode 3.0 come under Nonspacing mark (Mn) and Spacing combining mark (Mc) (Note: This does not include devanagari extended added in unicode 6.0 and vedic extensions added in unicode 6.1)",1378411609,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-6g646hsi3p3j73jyxxaz,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"en.wp user Professor Hog reports:
+""If you try and use beta to edit a page, but you've forgotten to log in, so you log in directly off the beta page, once you have successfully logged in it takes you back to the edit source page instead of the beta page. Minor, but thought you may want to correct it? ""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52281",1378296540,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_description,resolved
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,I think that needs to wait until enwiki has SET.,1455934739,PHID-USER-mvx4x7ywk2flsaku2dbk,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"@Jdforrester-WMF It looks like the [workaround](https://en.wikipedia.org/wiki/MediaWiki:Anoneditwarning) at enwiki (and maybe others, though not that I know of) needs to be removed/altered.
+
+See my previous comment.",1455912954,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,This now works.,1455641681,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"Note, Steven added a [custom workaround](https://en.wikipedia.org/w/index.php?title=MediaWiki:Anoneditwarning&diff=572253350&oldid=572253272) at English Wikipedia (shortly after this was filed).  It removes the action=edit, so you don't go to //any// editor on return (otherwise, it can to the wrong one like this bug says).
+
+That was never the desired behavior, though.  The desired behavior is that it knows which editor you're using anonymously, and keeps you on the right editor when you return logged in.  Both VE and wikitext have suitable URL parameters; the issue is knowing which to use.",1416894768,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"Changing the depends on to bug 52471 (sorry, I typoed in comment 3)",1378315266,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"(In reply to comment #3)
+> To clarify the sequence I used to reproduce this was:
+> 1. log out
+> 2. load a page in VE. I tested with [[Symphony No. 8 (Mahler)]] and
+> [[user:Thryduulf/sandbox]]
+> 3. click to edit the page in VE
+> 4. Click the ""log in"" link in the notice that pops up. 
+> This loads
+> https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=User:
+> Thryduulf/sandbox&returntoquery=action%3Dedit
+> in a new tab.
+> 5. In that new tab, log in as normal
+> Get returned to the source editor.
+> 
+> The edit notice shown is that in [[MediaWiki:Anoneditwarning]] where the link
+> is hardcoded to the source editor (pre VE this would never have been an
+> issue).
+> 
+> To me this suggests that either editor-relative urls are needed or we need
+> different edit notices for the classic editor and VE (see bug 52741 for the
+> latter)
+
+Oh, I see, I was clicking on ""login"" in the personal links bar - sorry. Re-titling so I don't get confused again. :-)",1378314148,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"To clarify the sequence I used to reproduce this was:
+1. log out
+2. load a page in VE. I tested with [[Symphony No. 8 (Mahler)]] and [[user:Thryduulf/sandbox]]
+3. click to edit the page in VE
+4. Click the ""log in"" link in the notice that pops up. 
+This loads https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=User:Thryduulf/sandbox&returntoquery=action%3Dedit in a new tab.
+5. In that new tab, log in as normal
+Get returned to the source editor.
+
+The edit notice shown is that in [[MediaWiki:Anoneditwarning]] where the link is hardcoded to the source editor (pre VE this would never have been an issue).
+
+To me this suggests that either editor-relative urls are needed or we need different edit notices for the classic editor and VE (see bug 52741 for the latter)",1378313436,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"I'll ask for further clarification, but I've tested this in Firefox 23 on linux.
+
+Clicking the link in the VE popup that notes you're not logged in reproduces this bug. (Note that this loads the login window in a new tab, I logged in there and was returned to the source editor in that window).
+
+Dismissing that popup and then using the log in link at the top right of the page returned me to viewing the page not editing it in either editor.
+
+The results are the same using my Thryduulf account which has a couple of gadgets, and my Awkward42 account which has none.",1378312694,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one,"I can't reproduce this - I get back to VisualEditor (as expected) - the login link is something like https://en.wikipedia.org/w/index.php?title=Special:UserLogin&returnto=Foobar&returntoquery=veaction%3Dedit
+
+Can ""Professor Hog"" give any further details? What browser were they using? Can they reproduce? What about after a hard-refresh? Do they have any odd gadgets on the account into which they were logging-in?",1378310407,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ngyf6tjjlwso4rlid7ni,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**Author:** `rachelqa99`
+
+**Description:**
+shows error message
+
+I got this message when running a test automation script, that puts in a line of code and tries to save it. It doesn't recognize the new line of code I put in, so it gives this error message upon save. Not sure if you are aware of this particular scenario, which is why I am submitting it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11191}",1378241340,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_description,resolved
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,I'm going to provisionally mark this as fixed as it appears to now work.,1449024014,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"Is this still a problem, or can the task be resolved?",1446479363,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"A clarification about each case we tried in the automated test: 
+
+* type a string and the string is shown correctly in CE and DM
+* type a string and :return and both the string and the empty line are shown correctly in CE and DM
+
+* but type a string and :enter and CE correctly shows *both* the string *and* the empty line but DM shows *neither* the string nor the empty line.  That is, the :enter command is recognized in CE but seems to have the effect of making all the changes in CE invisible to DM.",1378312673,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"
+I think this might be a real bug, but I think it might take some particular piece of hardware to trigger it. 
+
+WebDriver/Selenium has two ways of sending a newline to the browser
+
+:enter
+:return
+
+"":return"" is intended to emulate the ""Return"" key on a normal keyboard; "":enter"" is intended to emulate the ""Enter"" key on a numeric keypad.
+
+In this test, when we type a string plus :return in VE, the diff view is correct, and the test would pass.  But when the test sends a string plus :enter in VE, VE does not recognize that the contents of the edit page has changed. 
+
+I tried to reproduce this issue manually using a Macintosh USB keyboard on a Macbook Pro laptop but both the Return key and Enter key on that particular piece of hardware worked correctly with VE. 
+
+I suggest trying out Return (on the keyboard) and Enter (on the numeric keypad) on a few keyboards to make sure we don't see this in the wild.",1378309500,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**rachelqa99** wrote:
+
+I am adding the line of text  This is a test  at the beginning of the page into the Selenium user's homepage on test2.  There is a bunch of already existing text below it, I am just trying to add a new line at the begining of the page, ""This is a test"" and hit Return key for a new line.  I can't seem to reproduce it manually.",1378302946,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"(In reply to comment #0)
+> Created attachment 13227 [details]
+> shows error message
+> 
+> I got this message when running a test automation script,
+
+Yes, this is the normal (you tried to get the diff but as far as we're concerned, no changes were made to the page).
+
+> that puts in a line of code and tries to save it. It doesn't recognize the new
+> line of code I put in, so it gives this error message upon save.
+
+What ""line of code"" does it insert? Where does it insert it? On what page? On what wiki? Can you reproduce manually or does this only happen with the script?
+
+(In reply to comment #3)
+> Possibly a situation caused by bug 53360 which is marked as resolved.
+
+The fix for bug 53360 is running on test2 right now, so almost certainly not related to that bug.
+
+**Attached**: {F11191}",1378246805,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**rachelqa99** wrote:
+
+Possibly a situation caused by bug 53360 which is marked as resolved.",1378242207,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**rachelqa99** wrote:
+
+this is running off of test2",1378241594,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?,"**rachelqa99** wrote:
+
+feature script
+
+**Attached**: {F11192}",1378241543,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y44xrgvhzk7uy25krg2j,task_subcomment,NA
+"VisualEditor: jquery.IME doesn't work in VisualEditor's iframes (template, reference, reference list, media, and page settings dialogs, and language, maths, code and link inspectors)","The ULS input methods (jquery.ime) currently do not work with the popup windows of VE. These include the template, reference, reflist, image, link and page settings popups.
+
+The problem has been tested by me on Win7 X64 with Google Chrome 29.0.1547.62 m and possibly by others on other browsers. The problem was originally reported on [1] by mr-wp users.
+
+[1]: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE_.2B_ULS_unicode_Devnagari_Script_input_issues
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378231800,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-nj4fiiksolcbit4ngngp,task_description,declined
+"VisualEditor: jquery.IME doesn't work in VisualEditor's iframes (template, reference, reference list, media, and page settings dialogs, and language, maths, code and link inspectors)",Don't need to make this work as we don't use `iframe`s any more.,1427915125,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nj4fiiksolcbit4ngngp,task_subcomment,NA
+"VisualEditor: jquery.IME doesn't work in VisualEditor's iframes (template, reference, reference list, media, and page settings dialogs, and language, maths, code and link inspectors)",*** Bug 55969 has been marked as a duplicate of this bug. ***,1382983618,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-nj4fiiksolcbit4ngngp,task_subcomment,NA
+VisualEditor: Cursor cannot move through text created with jquery.IME when editing bulleted text,"System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Either use google input tools for hindi or enable ULS hindi transliteration
+
+Input:
+Select bullet formatting from the VE toolbar
+agar[SPACE]main[SPACE]
+
+Expected output:
+with ULS: अगर[SPACE]मैन[SPACE]
+with Google input tools (depends on translation history, macros etc and may differ user-to-user): अगर[SPACE]मैं[SPACE]
+
+Actual output:
+Text output is same as expected. However, the text is partially non-navigable, ie pressing the left arrow key from the end of the text takes the caret to the beginning, and then left/right arrow key presses have no effect on the caret. Simultaneously, if the text is navigated by specifically placing the caret at a particular point using the mouse, the value shown for the formatting dropdown in the toolbar may go blank at one point in the text and become paragraph at the next.
+
+The text is also irremovable ie bug 53708
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53708",1378217520,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-bqgfek7rspw6d5gukppc,task_description,resolved
+VisualEditor: Cursor cannot move through text created with jquery.IME when editing bulleted text,"(In reply to comment #1)
+> 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!
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+The patch seems to have partially fixed the bug.
+
+Text input using google input tools is now navigable.
+
+But text input using ULS IME hindi transliteration is still non-navigable. Pressing the left arrow key from the end of the text takes the caret to the beginning, and then left/right arrow key presses have no effect on the caret. (Same behaviour as before)
+
+The text formatting at all points in the bullet text remains as paragraph though (no blanking of the formatting drop-down).
+
+Text input with ULS is still irremovable ( bug 53708 )",1379516449,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-bqgfek7rspw6d5gukppc,task_subcomment,NA
+VisualEditor: Cursor cannot move through text created with jquery.IME when editing bulleted text,"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!",1378943051,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-bqgfek7rspw6d5gukppc,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Screenshot of incorrect text placement
+
+System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Enable ULS IME hindi transliteration
+
+Input:
+[ENTER/RETURN KEY]x2 (two newlines)
+agar[SPACE]ma
+
+Expected output:
+[NEWLINE]x2 (two newlines)
+अगर[SPACE]म
+
+Actual output:
+[NEWLINE]x2 (two newlines)
+अग[NEWLINE]र[SPACE]म
+
+Once [ENTER/RETURN KEY]x2 followed by agar[SPACE] has been pressed, Bug 53706 shows up. If one continues the input, this bug is what happens. The incorrect placement is accompanied by the following incorrect bahaviours:
+
+The VE toolbar shows no format (while the editing had been begun with paragraph)
+
+Cursor movement is incorrect. When the cursor is at the end, pressing up key takes it to the end of the first line, then pressing the down key takes it in the second line after the [SPACE] and before म It is here that the incorrect behaviour occurs. Pressing either the left or the right arrow keys takes it to the end of the line (ie after म) While this should happen on right arrow key press, the left arrow key press should take the cursor(caret) to before the space.
+
+Also, when at the end of the second line, pressing backspace does nothing. Similarly pressing delete anywhere in the second line does nothing. The second line effectively becomes irremovable, while the first line can be removed.
+
+Note: Page used for this test is [[:w:hi:सदस्य:Siddhartha Ghai/sandbox]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53711
+
+**Attached**: {F11165}",1378212900,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_description,resolved
+VisualEditor: Incorrect and irremovable text placement with IMEs,Automatic Incorrect caret movement has been reported separately as Bug 54424,1379768773,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Tested out this bug for page with pre-existing devanagari text.
+
+System Environment: Same as Comment 4
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit
+
+Steps:
+1 Enable ULS IME hindi transliteration
+2 Take the caret to the end of the first paragraph using the mouse (i.e click at the end of the first paragraph to take the caret there)
+3Input k
+3.1 This will give the output of क् with the newline selected ( Bug 53706 )
+4 Now input g
+4.1 This will give an output of ग् but this output will show up in the next line
+4.1.1 This output cannot be copy-pasted into an external text editor though it can be selected in VE
+4.1.2 This output is ignored in caret movement when using the arrow keys, so the caret goes straight from the beginning of the second paragraph to the end of the first paragraph just after क् jumping past ग् in between. When right arrow key is pressed the caret goes from here to the beginning of the second paragraph इस jumping past ग्
+4.1.3 Pressing backspace from the beginning of the second paragraph joins the second paragraph with the first paragraph jumping past the ग् making it the last text in the page
+4.1.4 Taking the caret to the end of text i.e after ग् makes the formatting dropdown go blank
+4.1.5 Using the VE toolbar Undo button moves the second paragraph back to a new line but it still stays above the ग् which is still the last text on the page.
+4.1.6 Undoing everything and adding a space to the end of the second paragraph and then submitting and reviewing the changes diff shows that the ग् at the end of the page is not being added
+4.1.7 Typing something after the ग् shows the text added after both ग् and the second paragraph.
+
+So effectively the bug is present even while editing existing pages with devanagari text using VE+ULS.",1379767940,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Reported console errors in Bug 54331 and Bug 54334 per Comment 7
+
+There's possibly other console error instances which need to be reported.
+
+(In reply to comment #8)
+> If you were able to test the issues for non-blank pages that would be a great
+> help too, because it looks like the problems happen in different ways in
+> those
+> two cases.
+
+Will do.",1379608845,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Thank you very much for providing this level of detail; I can't emphasise enough how helpful it is!
+
+If you were able to test the issues for non-blank pages that would be a great help too, because it looks like the problems happen in different ways in those two cases.",1379605340,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"(In reply to comment #6)
+> Could you please try typing some text on the following page, under the words
+> ""Testing Area"":
+> 
+>   https://www.mediawiki.org/w/index.php?title=Project:Sandbox&veaction=edit
+> 
+
+System environment: same as Comment 4
+
+Here's my primary analysis of editing on that page (without ULS).
+
+1. In the beginning the formatting dropdown is blank.
+1.1 Pressing [RETURN KEY] does not have any effect no matter how many times it is pressed.
+1.2 Pressing the [TAB KEY] takes the caret to the top of the page (above the ""edit this page"" template)
+1.3 Typing an ASCII character (or an international digit) changes the value in the formatting dropdown to paragraph.
+1.3.1 If a backspace is now pressed, the formatting remains the same.
+1.3.2 Pressing the [RETURN KEY] also works once an ASCII character has been input.
+1.3.3 Undoing all actions takes one back to the original position and [RETURN KEY] doesn't work again.
+
+Here's what happens with ULS hi transliteration (labelled लिप्यंतरण) enabled:
+
+1 Enabling ULS moves the caret to the top of the page (above the ""edit this page"" template) and the IME name लिप्यंतरण appears beside the ULS icon.
+1.1 Manually taking the caret to the original location below the ""Testing Area"" can be done
+1.1.1 If the caret is taken to the original location after the api call for the transliteration rules has completed, ULS icon shows that the transliteration method is not active (i.e no IME name visible beside the icon). This is incorrect as the dropdown for the menu shows the method selected and typing with the method works. Moving the caret manually back to the top still shows no change in the icon.
+1.1.2 If the caret is taken to the original position before the api call for the transliteration rules has completed, ULS icon shows the name of the IME correctly.
+1.1.3 Points 1.1.1 and 1.1.2 seem heisenbuggy and need to be confirmed.
+2 In the beginning (i.e nothing typed before), typing with ULS works, but the formatting dropdown remains blank.
+3 Input: agar[SPACE] Expected output: अगर[SPACE]
+3.1 The output अगर appears, but the space doesn't.
+3.1.1 Point to note: Per the hi transliteration rules in ULS agar itself gives अगर् i.e there is a viram ् (U+094D) at the end. ULS removes this when a space is input, i.e pressing space causes the removal of viram as well as the addition of space (this behaviour is the fix for bug 35990 ). So ULS is recognizing the space and removing the viram, but the space itself is getting lost somwehere between ULS and VE.
+3.1.2 Copying the text node text from within the chrome console and pasting in an external text editor showed the text to be prefixed by U+FEFF (ZERO WIDTH NO-BREAK SPACE)
+3.1.2 This text is not navigable using the left or right arrow keys.
+3.1.3 The text also cannot be copied. It can be selected manually with the mouse, but copying it is not possible. Pasting the selected text in an external editor showed nothing, as if no text had been selected. Tried copying using both the Ctrl+C keyboard shortcut and the right-click menu.
+3.4 Another space press is recognized. However, VE seems to treat this as the first input character.
+3.4.1 The original text disappears, replaced by the space. ( bug 53705 )
+3.4.2 The formatting dropdown shows the formatting to be paragraph.
+
+To my noobish eye, it appears that if VE was told to consider the default formatting to be paragraph (i.e no blank formatting dropdown in the beginning) OR VE considered any text input without a formatting dropdown value to be paragraph, ULS input disappearing would stop (I'm guessing this since once the formatting is set to paragraph, the text doesn't seem to disappear.)
+
+NOTE 1: This bug is starting to look a lot like a catchall to me, with automatic caret movement, incorrect formatting in the dropdown, non-detection of ULS input by VE, and what not. Feel free to file separate bugs where you find them necessary (or tell me which ones need to be filed separately, I'll be glad to help).
+
+NOTE 2: I reported this bug (along with a bunch of other related bugs) editing on a blank page so as to minimize bugs interfering with each-other and to have the simplest possible steps to reproduce the problem. However, I think that some of these may be applicable even on non-blank pages. Do I need to separately test the issues for non-blank pages and report the behaviour in these bugs (or are the current reports sufficient)?
+
+NOTE 3: I'm also ending up with a bunch of js console errors from VE, but I haven't checked exactly which step causes them. I'' try to reproduce them and let you know.",1379601354,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"Thanks for specifying the exact keystrokes -- it really helps!
+
+There's a specific input issue when the whole page is blank (whether or not an input method is used, i.e. even if you just type ASCII characters).
+
+Could you please try typing some text on the following page, under the words ""Testing Area"":
+
+  https://www.mediawiki.org/w/index.php?title=Project:Sandbox&veaction=edit
+
+Then click ""Save Page"" and ""Review your changes"", and see whether the text appears correctly in the right-hand version. (After that, you can cancel the edit without saving).
+
+I can type देवनागरी (""devnagrI"" using my Ibus Hindi phonetic IME) there, and it appears correctly.",1379514033,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"The behaviour has also changed for the input described in Comment 1
+
+Test at hindi wikipedia:
+Test url:
+https://hi.wikipedia.org/wiki/%E0%A4%B8%E0%A4%A6%E0%A4%B8%E0%A5%8D%E0%A4%AF:Siddhartha_Ghai/sandbox?veaction=edit
+
+Input:
+agar[SPACE]main[SPACE]kahoon[SPACE][RETURN KEY]
+
+Output:
+Fine except the newline never appears, no matter how many times the return key is pressed. The newline does not appear even when google input tools are disabled and the keyboard switched back to English (United States). The formatting dropdown is blank. The text is non-navigable ( bug 53711 ). However, pressing the left and right arrow keys a bunch of times and then pressing the return key still causes the text to be replaced with a newline followed by ♙
+
+Test at Mediawiki.org:
+Test url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+The behaviour with google input tools seems to be correct with the newline being placed correctly, and the text being navigable.",1379511359,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"(In reply to comment #3)
+> 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!
+
+The patch doesn't fix the bug. The behaviour has changed, however, and on first look it appears to be for the worse.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Input and expected output:
+Same as in comment 0
+
+Test at hindi wikipedia:
+Test url:
+https://hi.wikipedia.org/wiki/%E0%A4%B8%E0%A4%A6%E0%A4%B8%E0%A5%8D%E0%A4%AF:Siddhartha_Ghai/sandbox?veaction=edit
+
+What actually happens: (is too weird to be explained without prose)
+1. After inputting 2 newlines, as soon as a is pressed, VE shows input of अ but one line above the current line, i.e caret automatically moves from line 3 to line 2.
+2. Further inputting gar[SPACE] makes bug 53706 to show up, ie we have अगर[SPACE] in the second line with the space and newline selected, and the formatting dropdown having blanked.
+3. Then inputting m makes म् appear, but its in the next line, i.e line three.
+4. The caret has also moved back to line three ahead of it.
+5. Then, when the final a is input, the अगर[SPACE] in line two changes to अग with the र[SPACE] having moved to the beginning of line three followed by म . The text in line three is irremovable.
+
+Test at Mediawiki.org:
+Test url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+Firstly the page is blanked and the formatting reset to paragraph. The input described in Comment 0 is then done.
+
+What actually happens:
+Step 1-5 same as hindi wikipedia.
+Following this, after a (noticeable) fraction of a second, the text र[SPACE]म appears in the first line and the newline between lines 1 and 2 is selected.
+Caret movement is weird. When caret is at the end of the text (i.e end of third line), pressing a left arrow key takes it straight to the beginning of the second line. A right arrow keypress takes the caret back to end of third line. This effectively means that the text in lines two and three is non-navigable ( bug 53711 ). Pressing a backspace at the end of the third line removes the entire second line text, taking the caret to the second line. The first line is both navigable and removable. The third line text however, is irremovable.",1379510564,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"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!",1378943038,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,This bug was also seen when VE testing revealed Bug 53711,1378218621,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Incorrect and irremovable text placement with IMEs,"This bug (or a variant of it) seems to happen when using Google input tools for hindi.
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Enable google input tools IME
+Type something. example keystrokes: agar[SPACE]main[SPACE]kahoon[SPACE][RETURN KEY]
+
+Expected output:
+The text is typed(exact output text would depend on the IME's translation memory, macros used etc.) with a newline at the end and the cursor (caret) in the newline.
+
+Actual output:
+The text is typed correctly, the newline is also placed, but the cursor remains in the first line. The formatting dropdown of the VE toolbar is blank. It changes back to paragraph on pressing either the right or left arrow key (haven't tested with any other key).
+
+Pressing the return key again causes the newline to disappear while the text remains (variant of Bug 53705 ?). The same behaviour (correctly) takes place on pressing the delete key.
+
+Possibly different bug: When at the end of the first line, pressing the left/right arrow keys a bunch of times and then pressing the return key made me somehow end up with ♙ as the only text and all the input text gone.
+
+Also note that this bug doesn't seem to appear when using the native windows input devanagari-INSCRIPT",1378214611,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ibmxa5xzrcmu5u7fcttq,task_subcomment,NA
+VisualEditor: Reset title opacity on API call failure,"System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Let the API call for the parsed json output fail
+VE asks if you would like to retry, press Cancel
+
+Expected behaviour:
+VE should reset the opacity for the title and sitesub back to 1 from 0.6
+
+Actual behaviour:
+Opacity is not changed, leaving it 0.6 although the user is effectively reading the article, not editing it with VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378211220,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-jvygvcsdp3dse45vpayw,task_description,resolved
+VisualEditor: Reset title opacity on API call failure,I believe we fixed this a few months ago; sorry for the slow triage.,1402329753,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jvygvcsdp3dse45vpayw,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"Screenshot of selection error
+
+System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Enable ULS IME hindi transliteration
+
+Input:
+[RETURN/ENTER KEY]x4 (four newlines)
+agar[SPACE]
+
+Expected output:
+[NEWLINE]x4 (four newlines)
+अगर[SPACE]
+
+no text selection should be there
+
+Actual output:
+[NEWLINE]x4 (four newlines)
+अगर[SPACE]
+
+the ending [SPACE] is selected with a newline. Also, the toolbar shows that VE has somehow jumped to changing the formatting to bulleted and numbered list from the original paragraph formatting.
+
+Further, pressing a backspace deletes not only the selected space/newline, but also the typed text अगर. I think this is Bug 53705 though I may be wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53700
+
+**Attached**: {F11150}",1378210380,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ejote3xjqqm7riq7xqwf,task_description,resolved
+VisualEditor: Incorrect text selection with jquery.IME,"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.",1453749350,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"Further testing Comment 3 seems to indicate that the newline selection happens when the last input is a consonant followed by a halant which can be input with one keystroke.
+
+The hindi transliteration IME inputs two characters whenever an ASCII consonant is input, the equivalent hindi consonant followed by the halant character ् (U+094D)
+
+So inputting g gives ग् i.e ग + ् , j gives ज् i.e ज + ् etc. with the newline selected.
+
+Some hindi consonants, however, need two keystrokes to be input. So gh gives घ् i.e घ + ् and jh gives झ् i.e झ + ् etc. Output for these depends on the input speed. If one is quick, the text is input correctly with no selection. However, if one is slow, Bug 54421 shows up with the grapheme containing the duplicated text at the beginning of the article being selected.
+
+This selection (or non-selection) behaviour takes place regardless of whether the input is one consonant or a word. The behaviour depends on what the last consonant is, one that can be input with one keystroke or one that is input with two keystrokes.",1379766638,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,Note: Comment 3 is ofcourse with ULS IME hindi transliteration enabled.,1379764673,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"Screenshot for comment 3
+
+**Attached**: {F11151}",1379764061,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"Per https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c8 the following report is for the bug behaviour when tested on a page with pre-existing text:
+
+System Environment:
+Windows7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test Url:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit
+
+Steps:
+Take a caret to the end of the first paragraph using the mouse (i.e click at the end of the first paragraph to take the caret there.)
+Input ag
+
+Expected output:
+अग्
+
+Actual output:
+अग् but with the newline after it selected, although the newline or space wasn't typed in this edit and existed previously.",1379763646,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.IME,"(In reply to comment #1)
+> 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!
+
+The patch doesn't fix the bug.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test URL:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+Steps:
+Enable ULS IME hi transliteration
+Blank the page and reset the formatting to simple paragraph
+Follow the input steps described in Comment 0
+
+Result:
+The output is the same as described in Comment 0 as far as content selection is concerned. The formatting however, instead of changing to bulleted and numbered list, has gone blank. The formatting dropdown shows no value and no button in the VE toolbar is selected.
+
+Pressing backspace still deletes the space and the word. It also resets the formatting to paragraph.",1379508686,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Incorrect text selection with jquery.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!",1378943020,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ejote3xjqqm7riq7xqwf,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"System environment:
+Win 7 X64
+Google Chrome 29.0.1547.62 m
+
+Steps to reproduce:
+Open a blank page
+Edit it in VE
+Enable ULS IME hindi transliteration
+
+Input 1:
+agar[SPACE][ENTER/RETURN KEY]
+
+Input 2:
+kyaa[SPACE]
+
+Expected output 1:
+अगर[SPACE][NEWLINE]
+
+Expected output 2:
+क्या[SPACE]
+
+Actual output 1:
+[NEWLINE]
+
+Actual output 2:
+[SPACE]
+
+For the first case, when the given characters are typed, everything is fine upto the pressing of the return key, ie agar[SPACE] gives अगर[SPACE] as expected. However, as soon as the return key is pressed the entire text disappears leaving only a newline.
+
+For the second case, everything is fine till [SPACE] is pressed.
+
+If the page is not blank, extreme weirdness occurs, which can only be explained with further bugs (which I'm about to file). In short though, the disappearances persist, along with other buggy effects.
+
+Note: Page used for this test is [[:w:hi:सदस्य:Siddhartha Ghai/sandbox]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1378209360,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_description,resolved
+VisualEditor: Content disappears when using jquery.IME,"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.",1453749356,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"Hi,
+
+Besides Marathi and Hindi I tested this bug for more indic languages like Bangla, Ahirani,Konkni, etc.
+
+Even after defficulties I am trying to use VE+ULS combination on Marathi Wikipedia as much as possible to have real time feel and understand the issues better.
+
+For an example on Marathi Wikipedia we do have a page https://mr.wikipedia.org/wiki/वॉर_अँड_पीस . Other than info box it is empty. In Hindi and Marathi Wikipedia we do have large(huge) number of pages which are almost empty.Not able to type first word itself is a major hindrance and challenge before VE+ULS combinations.
+
+So wish and hope bug number 53700 and 53705 remain on priority list 
+
+
+rgds",1379826886,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"HTML after input kyaa[SPACE]
+
+**Attached**: {F11140}",1379506412,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"HTML after input kyaa
+
+**Attached**: {F11139}",1379506301,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"HTML after input agar[SPACE][ENTER/RETURN KEY]
+
+**Attached**: {F11138}",1379506002,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"HTML after input agar[SPACE]
+
+**Attached**: {F11136}",1379505701,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"(In reply to comment #3)
+> Here's the HTML which is in the result:
+
+The above HTML is not entirely correct. Copy-pasting messed up the text nodes. I'll be adding screenshots for the html as seen in the chrome console.",1379505046,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,"(In reply to comment #2)
+> 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!
+
+The bug is not fixed. The behaviour for both the spaces specified in Comment 0 is still the same. Tested at https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+Here's the HTML which is in the result:
+
+HTML for Input 1:
+
+<div class=""ve-ce-documentNode ve-ce-branchNode"" contenteditable=""true"" spellcheck=""true"" lang=""en"" dir=""ltr""><p class=""ve-ce-branchNode""><span class=""ve-ce-branchNode-slug ve-ce-branchNode-inlineSlug""></span></p><p class=""ve-ce-branchNode""><span class=""ve-ce-branchNode-slug ve-ce-branchNode-inlineSlug""></span></p></div>
+
+HTML for Input 2:
+
+<div class=""ve-ce-documentNode ve-ce-branchNode"" contenteditable=""true"" spellcheck=""true"" lang=""en"" dir=""ltr""><p class=""ve-ce-branchNode"">&nbsp;</p></div>",1379503794,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.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!",1378943009,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Content disappears when using jquery.IME,The further weirdness mentioned above is explained in Bug 53706 and Bug 53708,1378213142,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-ycbizrojj6ti4ywzojyo,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"*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
+
+*Problem description =In normal speed typing,after we type first alphaabate cursor moves from right to left direction.Word marathi need to apear मराठी with VE+ULS instead is coming राठीम 	
+
+**additional details = Marathi language devanagari is written in left to right direction.But when we use ULS Method of input = अक्षरांतरण with VE cursor is moving in opposite direction after typing first charecter as if we are typing a right to left script after typing first charecter and then again moves left to right 
+
+*Screenshot will be added
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49569",1378208100,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-fzc2bascptcvyjvfz6iv,task_description,resolved
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"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.",1453749391,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"Would it be possible to test 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!",1381270429,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"Automatic Incorrect caret movement has been reported separately as Bug 54424
+
+I suspect that this bug is a special case of that bug, but I may be wrong.",1379768841,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"(In reply to comment #2)
+
+Did primary testing seems some change of behaviour and different kind of weird  aspects . will need more tests and time before confirming. 
+
+Rgds",1379657273,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.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!",1378942983,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME,"[Not a blocker, see http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity ]
+
+> *Tested Browser and OS =Firefox+Win7
+
+Which Firefox version?
+
+
+What I tried:
+1. Go to http://mr.wikipedia.org/wiki/%E0%A4%85%E0%A4%AB%E0%A4%97%E0%A4%BE%E0%A4%A3%E0%A4%BF%E0%A4%B8%E0%A5%8D%E0%A4%A4%E0%A4%BE%E0%A4%A8
+2. make sure to be logged in
+3. Go to माझ्या पसंती (Preferences), संपादन and enable last option: यथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this enables VisualEditor
+4. Click cog next to इतर भाषांमध्ये
+5. Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण
+6. Click संपादन (Edit)
+7. Make sure that URL ends with &veaction=edit
+8. Type
+
+Results are weird under Firefox 23.0.1 and Fedora 19 (new lines inserted etc), but typing is not always backwards.",1378212107,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fzc2bascptcvyjvfz6iv,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","*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
+
+*Problem description = No other text on a page> Type a word + space bar = eliminates typed text imidiately
+
+**additional details = If some text is already there on the page or we copy paste then we can give the space bar with less frequency of this problem.
+
+
+*Screen shot or Difference of edit if available = Can not create the screen shot/or edit diff
+
+
+Thanks and Regards
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49569
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53706",1378207380,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_description,resolved
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","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.",1453749416,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","Not just Marathi/Devanagari specific, apparently it's a general problem with jquery.IME in VE.",1381270732,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately",*** Bug 54960 has been marked as a duplicate of this bug. ***,1381270703,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","(In reply to comment #6)
+> (In reply to comment #4)
+> > I tested on  mr wiki
+> 
+> As comment 3 said, it's available on ***mediawiki.org***, not mr wiki (yet).
+> mediawiki.org is where to test it.
+
+Confirming this is not fixed.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Test URL:
+https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+Steps to reproduce:
+Enable ULS IME mr transliteration (labelled अक्षरांतरण)
+Blank the page (and reset formatting to simple paragraph, i.e remove bulleted list formatting)
+
+Input 1:
+agar[SPACE]
+
+Output 1:
+[SPACE]
+
+Expected Output (as seen in the old editor):
+अगर्[SPACE]
+
+Input 2:
+kyaa[SPACE]
+
+Output 2:
+[SPACE]
+
+Expected Output (as seen in the old editor):
+क्या[SPACE]",1379504653,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","(In reply to comment #4)
+> I tested on  mr wiki
+
+As comment 3 said, it's available on ***mediawiki.org***, not mr wiki (yet). mediawiki.org is where to test it.",1379323479,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","(In reply to comment #4)
+
+Hello, gave one more try during a live edit correction, result no success.
+
+*On mr wikipedia page was https://mr.wikipedia.org/wiki/नारायण_श्रीपाद_राजहंस  
+
+*During the last edit diff https://mr.wikipedia.org/w/index.php?title=नारायण_श्रीपाद_राजहंस&diff=1198688&oldid=1184350 one new user has removed  section heading to word जीवन  
+
+*I took corrective editing target to type Marathi word व्यक्तीगत (by using VE+ULS method ) before word जीवन   so it will be a two word section heading  ==व्यक्तीगत जीवन==
+** Sentence to be edited जीवन नारायण श्रीपाद राजहंस यांचा जन्म जून २६, इ.स. १८८८ रोजी जिल्ह्यातील पलुस तालुक्यात नागठाणे या गावी झाला.
+
+
+Steps tried
+
+*Visit Marathi language wikipedia
+*Enable visual editor from preferences [[Special:Preferences#mw-prefsection-editing]]
+* page https://mr.wikipedia.org/wiki/नारायण_श्रीपाद_राजहंस
+
+
+* Clicked संपादन that is edit (Visual Editor's)
+
+* Sentence appeared  जीवन ↵नारायण श्रीपाद राजहंस यांचा जन्म जून २६, इ.स. १८८८ रोजी जिल्ह्यातील पलुस तालुक्यात नागठाणे या गावी झाला. 
+
+* Display language Marathi For Input method selected ULS> 1)अक्षरांतरण (transliteration)
+
+*Clicked Enter after word जीवन  since rest of line needs to be in paragraph portion
+
+*Took cursor before word जीवन  
+
+* To transliterate Typed keys from key board 'vyaktigata >> अक्षरांतरण transliteration transliterated to>> व्यक्तिगत transliteration was success.
+
+* Then 'Pressed space bar' the result was word 'व्यक्तिगत' disappeared.
+
+
+* Repeated above with different ULS input method  ULS> 2) इनस्क्रिप्ट (Inscript)
+
+** To transliterate typed keys  bd/kdlfil transliterated to>> व्यक्तिगत transliteration was success.
+
+** Then 'Pressed space bar' the result was word 'व्यक्तिगत' disappeared.
+
+Windows 7 + tried two browsers Firefox (version mentioned earlier) and Google Chrome (is up to date Version 29.0.1547.66 m)  The results were failure.
+
+
+(VE+windows native Input method इनस्क्रिप्ट 'in script' worked successfully to type word  व्यक्तिगत + space bar was success.) 
+
+We still wait and look forward to VE +ULS success. Best wishes for the same 
+
+Rgds",1379248005,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","Hello,
+
+This is 14th Sept 18.52 pm Indian standard time. I tested on  mr wiki couple of pages and tested on en wiki my own user space . To me problem is as is and not resolved.
+
+
+Thanks and best wished for your continued effort
+
+
+Rgds",1379165121,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","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!",1378942971,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately",Possible duplicate: Bug 53705,1378228533,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately","[Not a blocker, see http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity ]
+
+Confirming for Firefox 23.0.1 and Fedora 19.
+
+Steps to reproduce:
+1. Go to non existing page like https://mr.wikipedia.org/w/index.php?title=%E0%A4%85%E0%A4%AB%E0%A4%97%E0%A4%BE
+2. make sure to be logged in
+3. Go to माझ्या पसंती (Preferences), संपादन and enable last option: यथादृश्यसंपादक कार्यान्वित करा (केवळ मुख्य(लेख) आणि सदस्य नामविश्वात) - this enables VisualEditor
+4. Click cog next to इतर भाषांमध्ये
+5. Under क्षेपन (टायपींग ईनपुट) make sure to choose अक्षरांतरण
+6. Click तयार करा (Create page)
+7. Make sure that URL ends with &veaction=edit
+8. Type a word and press spacebar.",1378212092,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3e25u2t2rvump3xhzmpi,task_subcomment,NA
+"VisualEditor: Trigger keys can end up in CE surface, but not in DM","A user reported a problem to use the ""clear formatting"" shortcut with a french AZERTY keyboard. The shortcut is ""Ctrl + \"", but ""\"" is only accessible as ""AltGr + 8"".
+
+First, even with, ""Ctrl + AltGr + 8"", the shortcut doesn't work. I was unable to find a keyboard combination that triggers the ""clear formatting"" shortcut. When using a classic QWERTY keyboard, ""Ctrl + \"" works on the same computer/browser.
+See https://bugzilla.wikimedia.org/show_bug.cgi?id=51507
+
+But, when testing, I noticed an other problem, with a behaviour depending on OS/browser when using ""Ctrl + AltGr + 8"" with text selected:
+* On W7 + Chrome 29, the selected text is replaced by ""\"", but VE doesn't see any modification: save is disabled, undo is disabled, ...
+* On W7 + Firefox 23, the selected text is replaced by ""\"", and VE sees that text has been modified
+* On Ubuntu 12.04 LTS + Firefox 20, a user report that all page is selected.
+
+Same kind of problems happen with ""Ctrl + Alt + 8"", ""Alt + 8"", ... or other digits.
+
+https://fr.wikipedia.org/w/index.php?title=Wikipédia:ÉditeurVisuel/Avis#Raccourci_clavier_pour_effacer_la_mise_en_forme
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51507",1378132560,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-kxbkw2kfnhnvqihjlumu,task_description,resolved
+"VisualEditor: Trigger keys can end up in CE surface, but not in DM","Actually I think this was already fixed before Change 247800: On Ubuntu 15.10 with French keyboard, Alt+8 into a non-collapsed selection seems to overwrite the selection with \ in both the DOM and the DM, in both Firefox 42 and Chromium 45.",1449084298,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-kxbkw2kfnhnvqihjlumu,task_subcomment,NA
+"VisualEditor: Trigger keys can end up in CE surface, but not in DM","Change 247800 had a related patch set uploaded (by Divec):
+Diff richtext to build model changes
+
+[[https://gerrit.wikimedia.org/r/247800]]
+",1449082903,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kxbkw2kfnhnvqihjlumu,task_subcomment,NA
+"VisualEditor: Trigger keys can end up in CE surface, but not in DM",Trigger issue is split to bug 56452. Re-titled.,1383283899,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kxbkw2kfnhnvqihjlumu,task_subcomment,NA
+VisualEditor: Table rows with no defined cells rendered as an empty line,"At https://en.wikipedia.org/w/index.php?title=Flight_endurance_record&oldid=571122193#Free_Balloon.2C_Manned the table begins with an empty row where there would normally be a header:
+{|class=""wikitable""
+|-
+|-
+|content
+
+In view mode this empty line is not shown, but it does appear in VE.
+
+Testing at https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=571124234#Tables_with_empty_rows shows that the same thing happens, wherever the blank line is in the table. Oddly though the line is shown at full height when its in last position but ~half height elsewhere.
+
+In itself this isn't a problem, it's just different to what happens in view mode where the second |- is ignored.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1378066380,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-c6mjvz42mmi6bswdw56d,task_description,resolved
+VisualEditor: Table rows with no defined cells rendered as an empty line,This was fixed a while ago by the Parsoid team.,1404172794,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c6mjvz42mmi6bswdw56d,task_subcomment,NA
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#deprecated"" from TemplateData","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377905520,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4ua7w7m7aik6txmrerbe,task_description,resolved
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#deprecated"" from TemplateData","Change 129856 merged by jenkins-bot:
+Restyle parameter pages
+
+https://gerrit.wikimedia.org/r/129856",1398900767,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4ua7w7m7aik6txmrerbe,task_subcomment,NA
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#deprecated"" from TemplateData","Change 129856 had a related patch set uploaded by Trevor Parscal:
+Restyle parameter pages
+
+https://gerrit.wikimedia.org/r/129856",1398469830,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4ua7w7m7aik6txmrerbe,task_subcomment,NA
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#required"" from TemplateData","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377905340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-346l3sxkrxirwfv4rf4g,task_description,resolved
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#required"" from TemplateData",Verified the fix in test2,1390422254,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-346l3sxkrxirwfv4rf4g,task_subcomment,NA
+"VisualEditor: In the transclusion dialog's panel for a parameter, use ""Param#required"" from TemplateData",Done in I8f84a9ae277e5093356f591f7a56e8cebf4a1893.,1389902644,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-346l3sxkrxirwfv4rf4g,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, cursor keys can let you select parameters in the search results off the > screen and the dialog doesn’t scroll","
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377905220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3g3rbtewmym2ch553j4x,task_description,resolved
+"VisualEditor: In the transclusion dialog, cursor keys can let you select parameters in the search results off the > screen and the dialog doesn’t scroll","Change 74566 merged by jenkins-bot:
+Scroll into view support
+
+https://gerrit.wikimedia.org/r/74566",1379434760,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3g3rbtewmym2ch553j4x,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, cursor keys can let you select parameters in the search results off the > screen and the dialog doesn’t scroll","Change 74566 had a related patch set uploaded by Jforrester:
+Scroll into view support
+
+https://gerrit.wikimedia.org/r/74566",1378774554,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3g3rbtewmym2ch553j4x,task_subcomment,NA
+VisualEditor: Transclusion dialog improvements (tracking),"[Now tracked as #VisualEditor-MediaWiki-Templates instead.]
+
+
+Fork from bug 49833, which wasn't meant to be used this way.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377900000,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3niuhnlezs7jfmugbwdy,task_description,resolved
+VisualEditor: Transclusion dialog improvements (tracking),[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343622,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-3niuhnlezs7jfmugbwdy,task_subcomment,NA
+Add a functionality to gray out gadgets on gadgets preference tab that are dependent on other gadgets.,"Gadget checkboxes should be able to be grayed out (inaccessible) dependent on if another gadget is on or off, if other extensions exist that gadgets are unable to use, or if they require a specific skin to work.  For example, on en.wikipedia the current ""Editing"" section of the gadget tab on the preferences page looks like:
+ 
+[[ https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(current).png | commons:File:Special_Preferences_mw-prefsection-gadgets_(current).png ]]
+
+There should be a way to gray out functions, like:
+ 
+[[ https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(proposed).png | commons:File:Special_Preferences_mw-prefsection-gadgets_(proposed).png ]]
+If (in this instance) VisualEditor is enabled.",1377865740,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-anwdvhxvorgu42thq5we,task_description,open
+Add a functionality to gray out gadgets on gadgets preference tab that are dependent on other gadgets.,">>! In T55584#581617, @matmarex wrote:
+> The BetaFeatures extension implements something similar, maybe it could be extended to work with Gadgets. But I'm not sure if it's a good idea, you could just use the dependency system to load other gadgets regardless.
+
+Except in cases where the user doesn't want to use that other gadget.  In those cases, the dependent gadget should be greyed out and indicate they require the other component.  This lets the editor/user decide.",1419544542,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-anwdvhxvorgu42thq5we,task_subcomment,NA
+Add a functionality to gray out gadgets on gadgets preference tab that are dependent on other gadgets.,"The BetaFeatures extension implements something similar, maybe it could be extended to work with Gadgets. But I'm not sure if it's a good idea, you could just use the dependency system to load other gadgets regardless.",1383302073,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-anwdvhxvorgu42thq5we,task_subcomment,NA
+VisualEditor: histograms are duplicated while editing,"https://fr.wikipedia.org/w/index.php?title=Polisy&veaction=edit
+or
+https://fr.wikipedia.org/w/index.php?title=Aix-en-Othe&veaction=edit
+
+The demographic histogram gets duplicated while VEditing, although everything will be fine again once you save, but I see this can confuse users.
+
+Looks like it is generated, like other parts of the Démographie section, by https://fr.wikipedia.org/wiki/Mod%C3%A8le:Section_d%C3%A9mographie_d%27article_de_commune_de_France .
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377864060,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-sqkvabmnd7cfcbr6tkhz,task_description,resolved
+VisualEditor: histograms are duplicated while editing,"I don't see anything weird either on https://fr.wikipedia.org/w/index.php?title=Aix-en-Othe&veaction=edit
+
+Closing as FIXED.",1424365332,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-sqkvabmnd7cfcbr6tkhz,task_subcomment,NA
+VisualEditor: histograms are duplicated while editing,I discovered the bug in August 2013 and it was said to be fine from November 2013 at fr.wp. It must have been fixed by chance.,1422480548,PHID-USER-4cgt73x34j35pnbem65l,True,PHID-TASK-sqkvabmnd7cfcbr6tkhz,task_subcomment,NA
+VisualEditor: histograms are duplicated while editing,Looks fine to me... Was this fixed at some point?,1421888433,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-sqkvabmnd7cfcbr6tkhz,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Have seen multiple instances of this one backing up on commonswiki slaves recently:
+
+SELECT /* IndexPager::buildQueryInfo (LogPager) 148.160.132.46 */  log_id,log_type,log_action,log_timestamp,log_user,log_user_text,log_namespace,log_title,log_comment,log_params,log_deleted,user_id,user_name,user_editcount,ts_tags  FROM `logging` FORCE INDEX (times) LEFT JOIN `user` ON ((log_user=user_id)) LEFT JOIN `tag_summary` ON ((ts_log_id=log_id))  WHERE (log_action != 'revision') AND (log_type != 'suppress') AND log_type IN ('delete','move')  AND log_namespace = '0' AND log_title = '0' AND ((log_deleted & 1) = 0)  ORDER BY log_timestamp DESC LIMIT 11
+
+It runs in excess of 10 minutes.
+
+EXPLAIN says the FORCE INDEX sends MySQL onto a very slow index scan over `times` (log_timestamp) which is hardly better than a table scan in this case.
+
+Removing the FORCE allows `page_time` index be used which reduces execution time to a few seconds.
+
+Suggest either filtering by a range on log_timestamp or removing the FORCE.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54122",1377856620,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_description,resolved
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"With partitioned slaves LogPager queries are still not super fast, but they average <10s now and no longer dominate the slow query log.
+
+Closing this.",1396153047,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"16 looks reasonable, I just wouldn't want something crazy like 256 ;)",1389312673,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"16 partitions, a number chosen after some rough back-of-napkin style calculations for the larger wikis.
+
+The effect of accessing multiple partitions is closest to UNION. I don't anticipate excessive sorting or limiting penalties for our other queries though I do want to see how range access and index scans perform.
+
+Monitoring for queries adversely affected is definitely necessary and one of the reasons for only partitioning one slave per shard.",1389312419,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,How many partitions per table? So the Special:Log (no filter) case will have to UNION/resort/limit queries from each partition?,1389305283,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Much better than it was.
+
+I'm now trialing partitioned logging tables on one slave per production shard and directing these queries to those boxes. Since most of the queries use log_user = N, partitioning on key(log_user) allows the optimizer to use partition pruning.
+
+Still have to track down and sort out the ones without log_user = N. They're infrequent and low priority.",1389304624,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Resetting status as per comment 9. Sean: Is this still high prio?,1389268532,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"You're right, most of the slow queries we've seen in spikes do filter by log_user. But there are others that don't that also run slow.
+
+Ishmael, S3, db1003:
+
+/* IndexPager::buildQueryInfo */ select log_id, log_type, log_action, log_timestamp, log_user, log_user_text, log_namespace, log_title, log_comment, log_params, log_deleted, user_id, user_name, user_editcount, ts_tags from `logging` left join `user` on ((log_user=user_id)) left join `tag_summary` on ((ts_log_id=log_id)) where (log_type not in(?+)) and (log_type != ?) order by log_timestamp desc limit ?
+
+I went to S3 because that's where I saw the query form previously (zhwiktionary at the time). A quick check on S2 slaves doesn't show the same query running slow there, though there are other versions:
+
+* IndexPager::buildQueryInfo */ select log_id, log_type, log_action, log_timestamp, log_user, log_user_text, log_namespace, log_title, log_comment, log_params, log_deleted, user_id, user_name, user_editcount, ts_tags from `logging` left join `user` on ((log_user=user_id)) left join `tag_summary` on ((ts_log_id=log_id)) where (log_type != ?) and log_type = ? and log_namespace = ? and log_title = ? and ((log_deleted & ?) != ?) order by log_timestamp desc limit ?
+
+It's possible we'll trawl some of these up with the existing patch. Just something to keep in mind.",1384674453,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Which slow queries are *not* filtering on user ID? I thought that is where the slow queries still mostly happen.,1384673187,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Change 95584 merged by Springle:
+Changed use of tag_summary to use change_tag with GROUP_CONCAT()
+
+https://gerrit.wikimedia.org/r/95584",1384671061,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"True, ct_log_id cardinality still isn't brilliant, but it's better than ts_log_id.  The index is one that fluctuates cardinality estimates quite a bit between slaves, requiring periodic ANALYZE.  Eg, today the enwiki slaves manage to report ct_log_id cardinality values between 21 and 290251 :-| 
+
+Also, ct_log_id index covers (ct_log_id,ct_tag) which is useful.
+
+I've been trying different values for innodb_stats_sample_pages (=16 and =32) on several slaves to see if cardinality for a number of flakky indexes can be stabilized without the need for regular analysis (because of http://bugs.mysql.com/bug.php?id=33278). 
+
+After our chat on IRC on Friday I applied the change_tag/subquery version to other examples of slow LogPager logged on various wikis. It is generally better overall but can still be susceptible to hitting too much cold data.
+
+I'd still really like to see consideration on:
+
+- Making log_user=N clause enforced. The examples of the query that don't filter by user id hit the most rows.
+
+- If log_user=N isn't to be used then limit exposure to the last N months of data or something or change the way it's viewed entirely.
+
+- Consideration of your suggestion to break up tag_summary into three tables, which seems like a good plan given we already denormalize for tag_summary.",1384670134,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Though actually doesn't change_tag also have similar poor cardinality problems for the log_id index?,1384640491,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Change 95584 had a related patch set uploaded by Aaron Schulz:
+Changed use of tag_summary to use change_tag with GROUP_CONCAT()
+
+https://gerrit.wikimedia.org/r/95584",1384500369,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Possibilities after talking with Aaron on IRC, assuming group_concat can be sorted in MW code for pg...
+
+Using change_tag instead of tag_summary avoids the poor cardinality of ts_log_id and allows better query plans on `logging` indexes:
+
+v1
+
+enwiki> explain SELECT log_id,log_type,log_action,log_timestamp,log_user,log_user_text,log_namespace,log_title,log_comment,log_params,log_deleted,user_id,user_name,user_editcount,group_concat(distinct ct_tag separator ' ') as ts_tags FROM `logging`  LEFT JOIN `user` ON ((log_user=user_id)) LEFT JOIN change_tag ON (ct_log_id=log_id) WHERE (log_type NOT IN ('suppress','spamblacklist','review')) AND log_user = ? AND ((log_deleted & 4) = 0) GROUP BY log_id ORDER BY log_timestamp DESC LIMIT 51\G
+*************************** 1. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: logging
+         type: index
+possible_keys: type_time,user_time,log_user_type_time
+          key: times
+      key_len: 16
+          ref: NULL
+         rows: 2583
+        Extra: Using where; Using temporary
+*************************** 2. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: user
+         type: const
+possible_keys: PRIMARY
+          key: PRIMARY
+      key_len: 4
+          ref: const
+         rows: 1
+        Extra: 
+*************************** 3. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: change_tag
+         type: ref
+possible_keys: ct_log_id,change_tag_log_tag
+          key: ct_log_id
+      key_len: 5
+          ref: enwiki.logging.log_id
+         rows: 35
+        Extra: Using where; Using index
+3 rows in set (0.31 sec)
+
+pt-visual-explain
+
+JOIN
++- Filter with WHERE
+|  +- Index lookup
+|     key            change_tag->ct_log_id
+|     possible_keys  ct_log_id,change_tag_log_tag
+|     key_len        5
+|     ref            enwiki.logging.log_id
+|     rows           35
++- JOIN
+   +- Bookmark lookup
+   |  +- Table
+   |  |  table          user
+   |  |  possible_keys  PRIMARY
+   |  +- Constant index lookup
+   |     key            user->PRIMARY
+   |     possible_keys  PRIMARY
+   |     key_len        4
+   |     ref            const
+   |     rows           1
+   +- Table scan
+      +- TEMPORARY
+         table          temporary(logging)
+         +- Filter with WHERE
+            +- Bookmark lookup
+               +- Table
+               |  table          logging
+               |  possible_keys  type_time,user_time,log_user_type_time
+               +- Index scan
+                  key            logging->times
+                  possible_keys  type_time,user_time,log_user_type_time
+                  key_len        16
+                  rows           2583
+
+v2
+
+enwiki> explain SELECT log_id,log_type,log_action,log_timestamp,log_user,log_user_text,log_namespace,log_title,log_comment,log_params,log_deleted,user_id,user_name,user_editcount,(select group_concat(distinct ct_tag separator ' ') from change_tag where ct_log_id = log_id) as ts_tags FROM `logging`  LEFT JOIN `user` ON ((log_user=user_id)) WHERE (log_type NOT IN ('suppress','spamblacklist','review')) AND log_user = ? AND ((log_deleted & 4) = 0) ORDER BY log_timestamp DESC LIMIT 51\G
+*************************** 1. row ***************************
+           id: 1
+  select_type: PRIMARY
+        table: logging
+         type: range
+possible_keys: type_time,user_time,log_user_type_time
+          key: log_user_type_time
+      key_len: 38
+          ref: NULL
+         rows: 18675
+        Extra: Using index condition; Using where; Using filesort
+*************************** 2. row ***************************
+           id: 1
+  select_type: PRIMARY
+        table: user
+         type: const
+possible_keys: PRIMARY
+          key: PRIMARY
+      key_len: 4
+          ref: const
+         rows: 1
+        Extra: 
+*************************** 3. row ***************************
+           id: 2
+  select_type: DEPENDENT SUBQUERY
+        table: change_tag
+         type: ref
+possible_keys: ct_log_id,change_tag_log_tag
+          key: ct_log_id
+      key_len: 5
+          ref: enwiki.logging.log_id
+         rows: 35
+        Extra: Using where; Using index
+3 rows in set (0.32 sec)
+
+pt-visual-explain
+
+DEPENDENT SUBQUERY
++- Filter with WHERE
+|  +- Index lookup
+|     key            change_tag->ct_log_id
+|     possible_keys  ct_log_id,change_tag_log_tag
+|     key_len        5
+|     ref            enwiki.logging.log_id
+|     rows           35
++- JOIN
+   +- Bookmark lookup
+   |  +- Table
+   |  |  table          user
+   |  |  possible_keys  PRIMARY
+   |  +- Constant index lookup
+   |     key            user->PRIMARY
+   |     possible_keys  PRIMARY
+   |     key_len        4
+   |     ref            const
+   |     rows           1
+   +- Filesort
+      +- Filter with WHERE
+         +- Index range scan
+            key            logging->log_user_type_time
+            possible_keys  type_time,user_time,log_user_type_time
+            key_len        38
+            rows           18675
+
+
+v2 appears slightly better.",1384474133,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Larger WMF wikis are seeing more spikes of LogPager queries of which an example follows. These have had some recent tuning by initially removing forced indexes that no longer suited data set sizes, which has helped (10min down to ~100s), but we need to do more.
+
+mysql wmf db73 dewiki> explain SELECT /* IndexPager::buildQueryInfo (LogPager) xxx.xxx.xxx.xxx */ log_id,log_type,log_action,log_timestamp,log_user,log_user_text,log_namespace,log_title,log_comment,log_params,log_deleted,user_id,user_name,user_editcount,ts_tags FROM `logging` LEFT JOIN `user` ON ((log_user=user_id)) LEFT JOIN `tag_summary` ON ((ts_log_id=log_id)) WHERE (log_type NOT IN ('suppress','spamblacklist')) AND log_user = ? AND ((log_deleted & 4) = 0) AND (log_type != 'review') ORDER BY log_timestamp DESC LIMIT 51\G
+*************************** 1. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: logging
+         type: index
+possible_keys: type_time,user_time,log_user_type_time
+          key: times
+      key_len: 16
+          ref: NULL
+         rows: 6705
+        Extra: Using where
+*************************** 2. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: user
+         type: eq_ref
+possible_keys: PRIMARY
+          key: PRIMARY
+      key_len: 4
+          ref: dewiki.logging.log_user
+         rows: 1
+        Extra: 
+*************************** 3. row ***************************
+           id: 1
+  select_type: SIMPLE
+        table: tag_summary
+         type: ref
+possible_keys: ts_log_id,tag_summary_log_id
+          key: ts_log_id
+      key_len: 5
+          ref: dewiki.logging.log_id
+         rows: 20172                   <-- often much larger
+        Extra: Using where
+3 rows in set (0.29 sec)
+
+The remaining problems are:
+
+- The queries are fast enough until one hits cold data leading a slave to bottleneck on disk. The buffer pool churn has a flow-on effect on other normally fast queries which become false positives in the slow log. Especially problematic when a crawler like MSNBOT triggers a spike of these.
+
+- The tag_summary table often has a relatively low cardinality for ts_log_id (many nulls, few ids).
+
+- Sometimes a slave logs multiple identical copies of a query (always a form filtered by log_user) at intervals of several seconds. Presumably someone refreshing a page that is too slow to respond.
+
+Possibilities:
+
+- Pull out only log_id,log_user first to reduce the impact of the filesort and grab user and tag data in follow-up batch query. If the query plan sitches to using Index Condition Pushdown (""Using index condition"" in explain), cold data is less of an issue as fewer table rows are hit and fewer pages read.
+
+- Limit the size of the dataset to be considered. By timestamp perhaps, last X months maybe. For heavier users only?
+
+- Improve the method of retrieving ts_tags using something other than tag_summary. Or remove it entirely.
+
+- Isolate these queries to specific slaves (like watchlist).",1384428099,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Comment 2 correct.,1381972117,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,Was this removed together with other FORCE INDEX recently?,1381520218,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+IndexPager::buildQueryInfo (LogPager) query needs tuning,"Similar:
+
+SELECT /* IndexPager::buildQueryInfo (contributions page unfiltered) AstroChemist */  rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,user_name,page_namespace,page_title,page_is_new,page_latest,page_is_redirect,page_len,ts_tags  FROM `revision` INNER JOIN `page` ON ((page_id = rev_page)) LEFT JOIN `user` ON ((rev_user != 0) AND (user_id = rev_user)) LEFT JOIN `user_groups` ON ((ug_user = rev_user) AND ug_group = 'bot') LEFT JOIN `tag_summary` ON ((ts_rev_id=rev_id)) INNER JOIN `change_tag` FORCE INDEX (change_tag_tag_id) ON ((ct_rev_id=rev_id))  WHERE (rev_user >19555425) AND (ug_group IS NULL) AND (page_namespace != '0') AND ((rev_deleted & 4) = 0) AND ct_tag = 'visualeditor' AND (rev_timestamp<'20140101000000')  ORDER BY rev_timestamp DESC LIMIT 601;
+
+With force: 10+ mins
+
+Without force: 8s",1379619643,PHID-USER-lxluxbieyr4tgfyp5jru,False,PHID-TASK-5u2adzhalmhqywlvbhji,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"Attachment 1
+
+Visual Editor became quite unusable (possibly) after a recent update in Malayalam Wikipedia. There are several selection, editing and linking problems started to appear recently. Two such problems are described here.
+
+See the example below
+
+1. Copy the following text and paste it in a test page at Malayalam Wikipedia using conventional editor and save it. 
+ഈ ദുരന്തം ഐറിഷ് രാജ്യാതിർത്തി
+
+2. Edit the page using VE.
+
+3. Change the third word ""ഐറിഷ്"" to ""അയർലൻഡ്"". To do that, select the word ""ഐറിഷ്"" by double clicking on it and type the word അയർലൻഡ്.
+
+4. Now I want to create a wikilink for അയർലൻഡ്. For that, I used shift+ctrl+left arrow. Now, instead of selecting the entire word, A PORTION OF THE WORD WAS SELECTED. See the attachment 1. 
+
+5. Select the entire word അയർലൻഡ് using double clicking on it
+
+6. Press ctrl+k. Now instead of popping up a linking suggestion for the word അയർലൻഡ്, THE WORD DISAPPEARED AND LINKING SUGGESTION FOR A PART OF NEXT WORD POPS UP. See the attachment 2
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Linux
+**Platform**: PC
+
+**Attached**: {F11751}",1377824820,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-n4sh4scopfxwny7l26we,task_description,resolved
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"(In reply to comment #9)
+> When will this be deployed in ml.wikipedia?
+
+Assuming that VE is deployed according to the roadmap for MediaWiki: [[mw:MediaWiki_1.22/Roadmap]], September 19. (Sorry, I should have mentioned that in my previous comment :) )",1379335311,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"(In reply to comment #7)
+> vssun, on which wiki? The patch is only deployed at [[mw:|MediaWiki.org]]
+> right
+> now.
+
+Thank you. The bug is about Malayalam Wikipedia (already mentioned in description)
+
+When will this be deployed in ml.wikipedia?",1379333338,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"(In reply to comment #6)
+> Still facing all the problems mentioned at comment 1
+
+Please always provide clear and exact steps to reproduce (e.g. URL testcase).
+Resetting status as I assume that this is fixed on mediawiki.org.",1379322294,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"vssun, on which wiki? The patch is only deployed at [[mw:|MediaWiki.org]] right now.",1379314575,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,Still facing all the problems mentioned at comment 1,1379313962,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"Marking this as ""FIXED"" on the expectation that it's fixed - please re-open if you find that it is still occurring.",1378958943,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"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!",1378943178,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"(In reply to comment #2)
+> Sorry for the incorrect attachment links on the above comments. Please
+> correct it if somebody can.
+
+Sorry, links in comments can't be edited in Bugzilla. :-(",1377827166,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,Sorry for the incorrect attachment links on the above comments. Please correct it if somebody can.,1377825981,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+VisualEditor: Unexpected editing behaviour for Malayalam Text,"Attachment 2
+
+**Attached**: {F11752}",1377825109,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-n4sh4scopfxwny7l26we,task_subcomment,NA
+Automatically switch from wikitext to HTML syntax in serializer when attributes were added to elements,"When editing a document that contains:
+
+* Foo
+* Bar
+* Baz
+
+Adding an attribute to one of the list items in VE doesn't roundtrip (they serialise back to * instead of forcing <ul><li>..</ul>, as it will have to).
+
+Right now VisualEditor never does this, but earlier today I was experimenting with this (the language inspector might need to do this to properly flip the directionality of an individual list item, wrapping the inner content is not an option as then the number would be on the wrong side).
+
+When trying to reproduce this I noticed that it also happens when creating a new document (e.g. there is no existing page, it has no reason to force ""*"" instead of ""<li>"" other than that being the preferred default for wikitext).
+
+
+http://parsoid.wmflabs.org/_html/:
+
+In:
+<div dir=""ltr"">
+<ul>
+<li>a
+<li lang=""he"" dir=""rtl"">b
+<li>c
+</ul>
+</div>
+
+Out:
+<div dir=""ltr"">
+
+* a
+* b
+* c
+
+</div>
+
+The only case where Parsoid kept the attributes is when not editing a document with wikitext, and not creating a new document, but when editing an existing document with ""<li>"" in wikitext already, it did roundtrip those.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68800",1377813060,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5dek6g5wc736qamv43s5,task_description,open
+Automatically switch from wikitext to HTML syntax in serializer when attributes were added to elements,"An option might be to use T230683's `<<< .... >>>` syntax to handle T242777, and T230658's `{{#attr}}` to handle this task.
+
+Right now you can't mix ""wikitext"" and ""HTML-ish"" syntax in the same list (ie, some items `*` and some items `<li>`, which means the serializer needs to go back and convert *all* of the items in the list into html-ish syntax when it finds an item which can't be represented without it (either due to newlines in the content or attributes on the tag).  We could make that work, but it would probably require either (a) backtracking and reserializing the list, which could be O(N^2) in the worst case (O(N) nested lists, where the final item in each requires going back and reserializing the list using html-ish syntax), or (b) lookahead in the serializer for problematic content, which again could be O(N^2) if done naively (O(N) nested lists, where each requires O(N) look ahead to the end).",1579033369,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-5dek6g5wc736qamv43s5,task_subcomment,NA
+Automatically switch from wikitext to HTML syntax in serializer when attributes were added to elements,"@esanders, @Catrope, @Jdforrester-WMF, Is this an use case that Parsoid should support in Q3 / Q4?",1422986235,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-5dek6g5wc736qamv43s5,task_subcomment,NA
+Automatically switch from wikitext to HTML syntax in serializer when attributes were added to elements,"Timo indicated on IRC that lists and list items will be first, but other elements will follow. We should try to use this first case to develop the general infrastructure.
+
+We will need to convert an entire list to HTML syntax if an attribute is set on either the list or any list item.
+
+Mixed templated / non-templated list items are discussed in bug 53368. We protect the entire list if any list item's bullets are template-generated. That means that we (thankfully!) won't have to consider that case here.",1377818147,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-5dek6g5wc736qamv43s5,task_subcomment,NA
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment","MyOnlyEye says, ""When I write long articles in VisualEditor the whole screen scolls - and the VisualEditor toolbar is scrolling upward and out of the screen. If I want to make a headline or instert a picture I'll have to scroll up to the top to reach the toolbar. I've tried it in the lastest edition of Firefox and Chrome in Win8 - on my own mediawiki with visualeditor and Wikipedia and Mediawiki....On every page that is longer than the screen - e.g. http://en.wikipedia.org/wiki/Electron?veaction=edit
+I've tested a bit (after I wrote the feedback) and it seems to be OK on my Win7 and Linux-box (chrome and firefox, both in 64-bit), but it's not working on Win8 (32-bit). Both the lastest 32-bit edition of Chrome and Firefox have the ""scrolling error"" on my Acer W510 Win8-laptop in desktop-mode (and in tile-mode :-)....I tried the electron-article and updated my own wiki (with git pull on mediawiki developer and visualeditor). I tried it in Firefox and Chrome (latest 32-bits editions)....I've installed a virtualbox with Win8 (32-bit, same as my Acer W510) and ran some wiki-pages with visualeditor in Chrome. No problem with the toolbar. So there seems to be two options left - 1) it's the intel screen driver (Intel HD 9.14.3.1102) or 2) it's how the browsers behave in a touch screen environment. My W510 has touch screen, the virtualbox Win8 hasn't....
+I've tested it on another Win8-machine (ASUS VivoBook S400 14"" HD touch) with different hardware than Acer W510 _but_ with a touch screen - and... the toolbox/-bar scrolled out of the screen. So my guess is that this is something that happens when the browser knows that the user can scroll the webpage with the fingers.""
+
+It is apparently not quite the same as https://bugzilla.wikimedia.org/show_bug.cgi?id=52504
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377802500,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-nkghehcsjvmpig3dnbgm,task_description,invalid
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment","**odin** wrote:
+
+Now working in the lastest Firefox v25.0 for Windows8. Still not working in latest Chrome.",1383167709,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nkghehcsjvmpig3dnbgm,task_subcomment,NA
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment","**odin** wrote:
+
+Also confirmed in Android 4.3 (with default Chrome browser) on Asus Nexus 7 (2012).",1379099403,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nkghehcsjvmpig3dnbgm,task_subcomment,NA
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment","**odin** wrote:
+
+I just testet the bug in Android 4.2.1 with Chrome (on a Samsung Galaxy S4) - and when I scroll, the toolbox moves out of the screen.",1379077160,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-nkghehcsjvmpig3dnbgm,task_subcomment,NA
+"VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment",This sounds bad for our impending work for mobile. :-(,1377835053,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nkghehcsjvmpig3dnbgm,task_subcomment,NA
+VisualEditor: nowiki tags thrown right after a template,"I am filing a related common problem we meet at it.wp.
+
+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.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377800880,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-qoahpa6ud2jrgv76kigv,task_description,open
+VisualEditor: nowiki tags thrown right after a template,"Related Parsoid behavior (this is serialization of new content):
+-----------------------
+[subbu@earth lib] echo ""<table><tbody><tr><td>foo</td></tr></tbody></table> a"" | node parse --html2wt
+{|
+|foo
+|}
+<nowiki> </nowiki>a
+-----------------------
+
+The following is for existing content in wikitext
+-----------------------
+[subbu@earth lib] echo ""{|\n|a\n|} a"" | node parse --wt2wt
+{|
+|a
+|} a
+-----------------------
+
+So, Parsoid does not split the line after the table if it is old content, but does if it is new content and can introduce a <nowiki>  Since the report states that happens no matter what is edited on the page, my suspicion is that the HTML has a newline break after the <table> added by VE.  Requires further investigation that I cannot do right now, but hope this is good for starters. Adding others who might have time to investigate.",1377802050,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-qoahpa6ud2jrgv76kigv,task_subcomment,NA
+VisualEditor: Added templates in RTL wikis should float in appropriate direction,"Templates that are inserted to a page in RTL appear first floating on the right side, then only after save and re-edit they appear correctly.
+
+Replicate:
+1. Go to hewiki (or any other rtl wiki)
+2. Add a template - for instance {{עליות}} which is supposed to be floated left - yet it is inserted floating right.
+3. Save the page. Edit it again -- the template floats in the correct direction.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377798180,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-77lwknbtryzjh4peqeh4,task_description,resolved
+VisualEditor: Added templates in RTL wikis should float in appropriate direction,This is working for me. Feel free to re-open if this is still an issue.,1701813764,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-77lwknbtryzjh4peqeh4,task_subcomment,NA
+"VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages","**Author:** `p.selitskas`
+
+**Description:**
+Entries in Page settings / Languages don't have dir attributes for the link text. It leads to bidi issues for RTL languages.
+
+Reproducing:
+1. Go to an article with a langlink to Hebrew, for instance. Here's my favourite: [[en:August 3]].
+2. Open the VisualEditor.
+3. Go to Page settings / Languages and scroll down to 'he'.
+4. Link text reads as ""3 באוגוסט"", but it should read with ""3"" after Hebrew characters (reading left-to-right, of course; in the beginning of the string, if right-to-left).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377728640,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ozeftogat7b2642er6vn,task_description,resolved
+"VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages",Merged and will go out with wmf16 (from Thursday 5 September).,1377895476,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ozeftogat7b2642er6vn,task_subcomment,NA
+"VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages","Change 81589 merged by jenkins-bot:
+VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages
+
+https://gerrit.wikimedia.org/r/81589",1377887216,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ozeftogat7b2642er6vn,task_subcomment,NA
+"VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages","Change 81589 had a related patch set uploaded by Wizardist:
+VisualEditor: RTL entries don't receive dir=""rtl"" in Page settings / Languages
+
+https://gerrit.wikimedia.org/r/81589",1377728877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ozeftogat7b2642er6vn,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","See numbers 49 and 50 in https://pl.wikipedia.org/w/index.php?title=Biurokracja&oldid=37367869 and https://pl.wikipedia.org/w/index.php?title=Biurokracja&oldid=37367869&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51289
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52300",1377708300,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-4zstjmvxiakrfapfim3n,task_description,resolved
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","Actually, on review I'm pretty sure that this is a duplicate of bug 50474.
+
+*** This bug has been marked as a duplicate of bug 50474 ***",1377823295,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue",at en.wp user:KWW wonders if this is the same issue as bug 52300?,1377814639,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","Looking again, it seems this is not the same as the earlier bug. In that case the references from the infobox didn't appear in the reflist at all. Now it seems that it is just the numbering that is wrong. At [[Ptyhon (programming language)]] for example, there are 10 references in the infobox, so the first reference in the lead is numbered 11. 
+
+Looking at in VE though the first reference in the lead (TIOBE Software Index (2012)) is numbered 1. In the reference list though TIOBE Software Index (2012) is numbered as 11 and reference 1 is the first one from the infobox.",1377801805,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","To clarify the first comment: if you look at the vedit view of the page I linked, you'll see that references 50 and 49 are both labelled ""49"". So, potentially we might be dealing with two distinct bugs here - renumbering because it's not factoring in different surfaces, and duplicate numbering.",1377796895,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue",References in infobox not populating the main references list and not being counted sounds a lot like bug 51289 which was marked fixed at the start of the month,1377775105,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue","<< Entering Visual Editor mode renumbered the references on page Python_(programming_language) https://en.wikipedia.org/wiki/Python_(programming_language)?veaction=edit , so they don't match the references listed at the end of the article. Davipo 08:36, 29 August 2013 (UTC) >>
+It will ignore the numbers in the infobox, and start again from n.1 in the first line of the article - should be 11 instead. I find it just slightly confusing, since in the end you are still able to edit footnotes correctly. Thanks.",1377770276,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-4zstjmvxiakrfapfim3n,task_subcomment,NA
+VisualEditor: Transclusion editor should not allow parameters with unmet dependencies,"The transclusion editor should not allow (or at least should warn about) template parameters with unmet dependencies.
+
+For example in [[template:For]] parameter 4 has no effect unless parameter 3 is also specified, so the transclusion editor should not allow/warn about template 4 without an accompanying parameter 3. (parameter 3 is otherwise optional and can be present without parameter 4).
+
+In at least some cite templates, parameter author2 requires the existence of author1, etc. 
+
+I'm fairly sure that this functionality depends on bug 50407, which requests that TemplateData allows dependency relationships like this to be defined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377690300,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-f6pggcvz6dsrki4glrbf,task_description,open
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Redlinks right now always take you into wikitext editor, regardless of what editor is primary on your wiki.
+
+--------------------------
+**See Also**:
+{T54162}
+{T54281}",1377650040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_description,resolved
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Makes sense. I'll do that.,1455819228,PHID-USER-go2ym6ta2zn6ofdsrqnx,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#2039758, @Johan wrote:
+> Something like this:
+> 
+> ""In the future, clicking a red link will open the page in your primary editor. Today it will open it the wikitext editor. This will only work for wikis with [[<tvar|set>mw:Special:MyLanguage/VisualEditor/Single edit tab</>|single edit tab]].""
+> 
+> (I know the change is happening now, but unless it actually affects editors because it only works for wikis with the single edit tab, it's still a future change for them.)
+
+The wording looks good. I'd push this to next week, and talk about how it will (then) be live on huwiki and people can see it there.",1455815567,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Something like this:
+
+""In the future, clicking a red link will open the page in your primary editor. Today it will open it the wikitext editor. This will only work for wikis with [[<tvar|set>mw:Special:MyLanguage/VisualEditor/Single edit tab</>|single edit tab]].""
+
+(I know the change is happening now, but unless it actually affects editors because it only works for wikis with the single edit tab, it's still a future change for them.)",1455809932,PHID-USER-go2ym6ta2zn6ofdsrqnx,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Something like this:
+
+""In the future, clicking a red link will open the page in your primary editor. Today it will open it the wikitext editor. This will only work for wikis with [[<tvar|set>mw:Special:MyLanguage/VisualEditor/Single edit tab|single edit tab]].""
+
+(I know the change is happening now, but unless it actually affects editors because it only works for wikis with the single edit tab, it's still a future change for them.)",1455809914,PHID-USER-go2ym6ta2zn6ofdsrqnx,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","So does this affect any other wikis than the test wiki at the moment? Hungarian Wikipedia is supposed to get the single edit tab, but doesn't have it yet, right?",1455798338,PHID-USER-go2ym6ta2zn6ofdsrqnx,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",(Only fixed for Single Edit Tab wikis.),1455651854,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446269, @matmarex wrote:
+>>>! In T55441#1446171, @Ricordisamoa wrote:
+>>>>! In T55441#1446154, @Krenair wrote:
+>>> We'd like to have a single edit tab where the user can chose between VE and a wikitext source editor
+>> 
+>> https://meta.wikimedia.org/wiki/Wikiafication
+> 
+> This comment is at best unfair and at worst willful ignorance or trolling. Being able to switch between editors while editing has been requested repeatedly, and using the action=edit view for editors is the obvious choice, already made by others such as CodeEditor. It is the most obvious, most intuitive and best way to present two or more editors
+
+It proves that the essay is biased and Wikiafication can be good sometimes.",1436623626,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446955, @TTO wrote:
+> Many of the MW installations that have requested this appear to be corporate/internal wikis. Would you be willing to provide the feature for them, even if you do not enable it on WMF wikis?
+
+Yes, that's fine (though ideally we'd do so in a way that doesn't create technical debt in MediaWiki which we'd have to carry).",1436578387,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Many of the MW installations that have requested this appear to be corporate/internal wikis. Would you be willing to provide the feature for them, even if you do not enable it on WMF wikis?",1436578325,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446206, @Solstag wrote:
+> This bug is about making the default choice of editor consistent. For red links. It's that simple.
+
+I understand. The current situation is poor for the majority of people who click 'edit' rather than 'edit source' and get VE rather than WT, except when it comes to red links.
+
+However, just blindly changing these from WT to VE would be a bad move for a few reasons:
+
+* It's a pretty core disruptive change to a core part of how MediaWiki works, which means it would probably break a number of scripts, gadgets, bots and other tools that have been built over the past 15 years relying on this being a certain way.
+* It would take a long time to roll out in Wikimedia production, as this would be a breaking change to the read HTML with `href`s' targets being changed, meaning the benefit for IPs would take many weeks to be fully felt (and likely breaking other things).
+* It would replace the bad system (use WT, no choice) with another bad system (use VE, no choice), rather than a 'proper' system of user choice
+* It would be particularly disruptive for 'power editors', who would be forced to switch over to WT every time they clicked edit, likely leading them to opt-out of VE in huge numbers.
+* It would be inconsistent – for namespaces which are WT-only, like `MediaWiki:` or `Template:`, would it take you to WT anyway?
+* For users who can't use VE (//e.g.// no JS, something we can't fix server-side), it would strand them on the 'read' page, rather than take then to WT
+
+Consequently, I am not willing to make this change before we have a single edit tab that solves (or obviates) each of these issues.",1436558337,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446171, @Ricordisamoa wrote:
+>>>! In T55441#1446154, @Krenair wrote:
+>> We'd like to have a single edit tab where the user can chose between VE and a wikitext source editor
+> 
+> https://meta.wikimedia.org/wiki/Wikiafication
+
+This comment is at best unfair and at worst willful ignorance or trolling. Being able to switch between editors while editing has been requested repeatedly, and using the action=edit view for editors is the obvious choice, already made by others such as CodeEditor. It is the most obvious, most intuitive and best way to present two or more editors, and not ""additional and costly bloat to a site as an unsuccessful means of ""engaging visitors"" or ""building community"""", like that page states. ",1436557895,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Please, this bug is not about having a single edit tab, or choice, or wikiafication or whatever.
+
+This bug is about making the default choice of editor consistent. For red links. It's that simple.",1436555598,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1446154, @Krenair wrote:
+> We'd like to have a single edit tab where the user can chose between VE and a wikitext source editor
+
+https://meta.wikimedia.org/wiki/Wikiafication",1436554570,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I'm not sure we want to use this hook for VE. We'd like to have a single edit tab (pointing to action=edit) where the user can chose between VE and a wikitext source editor instead, so this would be obsolete.",1436554102,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1433506, @Juandev wrote:
+> So, why it was told to me, we need a community consensus?! Dont tell me that it cannot be set differently to each project?!
+
+At the moment, it cannot, because the feature you are asking for doesn't even exist yet. That is the problem we are trying to solve with the patch linked above.
+
+Once that is dealt with, then we can potentially act upon the community consensus and enable the feature on that wiki, if the VE boffins agree that it is a good thing to do. ",1436266371,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1327857, @Krenair wrote:
+> When it happens, it'll happen on every wiki. Until then it can't be on any wiki...
+
+So, why it was told to me, we need a community consensus?! Dont tell me that it cannot be set differently to each project?!
+
+
+
+",1436264992,PHID-USER-vm462i2ffbawnuo4mh3n,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1429220, @Nemo_bis wrote:
+> Red links are the single most important entry point for article editing after the edit tabs and section editing, so it makes sense to make them smarter/configurable.
+
+I've been wondering how are articles created. Is it red links from other articles? The red links that appears when search for a page that doesn't exist? Something else?",1436182556,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Indeed, this bug is not about action=edit but about what gets linked most prominently. Red links are the single most important entry point for article editing after the edit tabs and section editing, so it makes sense to make them smarter/configurable.
+
+Then of course there are many other links to handle later (think of inputbox and so on) but divide et impera applies.",1436180945,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","@Krenair I'm a little puzzled by your comment:
+
+>>! In T55441#1412564, @Krenair wrote:
+> Sorry, but this is not a thing. MediaWiki does not let you set default=wikitext vs. default=visualeditor. You get given one editor by MediaWiki for wikitext, and it's what gets shown at action=edit (the target of all of MediaWiki's red links). 
+
+Well, isn't that part of the point of this issue - to make redlinks configurable? Of course, T102398 would render that moot, but in the interim, I have uploaded new patch sets to https://gerrit.wikimedia.org/r/178817 that allow extensions to retarget redlinks.
+
+I don't expect WMF wikis to use this, but some third-party installations are interested in it (judging by posts at Support Desk over the past few months).",1436163446,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1408724, @Solstag wrote:
+> A project that has visual editor as default for
+
+Sorry, but this is not a thing. MediaWiki does not let you set default=wikitext vs. default=visualeditor. You get given one editor by MediaWiki for wikitext, and it's what gets shown at action=edit (the target of all of MediaWiki's red links). VE hacks itself in via veaction=edit, but this cannot be considered a default by any means.",1435631163,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1408724, @Solstag wrote:
+> A project that has visual editor as default for everybody, even unauthenticated users, should open red links with the visual editor.
+
+A gadget (enabled by default) which replaces `action=edit` with `veaction=edit` might be the easiest short-term solution - it gives the ability to opt out, and does not cause cache fragmentation.",1435614861,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Hi folks! Just in case the duplicate doesn't speak by itself, I see no reason why we don't have right now:
+
+A project that has visual editor as default for everybody, even unauthenticated users, should open red links with the visual editor.
+
+All other projects should wait until you sort out the mess with picking the right editor for each user.
+
+This is definitely not hard to implement, there's not even a new config involved.
+
+Cheers and thanks for looking into this.",1435534756,PHID-USER-wr7prgh3p37xrvbdr6w5,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#1327857, @Krenair wrote:
+> When it happens, it'll happen on every wiki. Until then it can't be on any wiki...
+
+A lot of Wikimedia wikis have been happily using VisualEditor for over a year, and the wikitext editor being the default even for new editors is problematic for them. (It is somewhat ridiculous, for example, that [[ https://www.mediawiki.org/wiki/Extension:SandboxLink | SandboxLink ]], which is mainly meant to make the life of new editors easier, drops them into a wikitext editor.) I don't see what's wrong with providing a per-wiki option.",1434826324,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Updated title to reflect actual desired end result. The url structure is secondary and may actually change (see T54281).,1433993685,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","When it happens, it'll happen on every wiki. Until then it can't be on any wiki...",1433206467,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Could you enable this on cs.wv per community consensus: https://cs.wikiversity.org/wiki/Wikiverzita:Diskusn%C3%AD_prostor#Zalo.C5.BEen.C3.AD_a_editace_str.C3.A1nky_ve_VisualEditoru,1433206300,PHID-USER-vm462i2ffbawnuo4mh3n,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Change 178817 restored by TTO:
+Consistent edit links
+
+Reason:
+Seems like a valuable change.
+
+[[https://gerrit.wikimedia.org/r/178817]]",1431085942,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","This option should (must?) be available for those who wish to use VE on their own MediaWiki installations. Currently, redlinks are a ""hole"" through which unsuspecting users can ""fall"" into the ""pipework"" of the wikitext editor.
+
+Most of the discussion here deals with the social aspects of the task, which doesn't seem hugely relevant here. The functionality would presumably live behind a $wg flag, and be switched off by default.",1431085917,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Change 178817 abandoned by Ricordisamoa:
+Consistent edit links
+
+Reason:
+There ain't no such thing as a solution for this.
+
+[[https://gerrit.wikimedia.org/r/178817]]",1429130863,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I do not plan to work on it before the discussion has an outcome (nor I have any personal interest in supporting VisualEditor at the moment), but the patch is up for anyone who wants to play with it.",1422491673,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Are you going to work on it more? I got the impression from the way you unassigned this that we shouldn't review the patch before discussing this further.,1422491216,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",@Krenair: should I abandon my patch then?,1422490645,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",This has to be discussed further.,1421814853,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#849854, @matmarex wrote:
+> What I meant is that a vocal group of English Wikipedia users hates VisualEditor's guts and would enjoy the new opportunity to spit on it. I hope this clarifies the issue. :)
+> 
+> VisualEditor is also still not quite compatible with some languages and some wikis' conventions, so this would regardless need to be behind a configuration option.
+
+I thought, they asked to switch it off at all. ",1421475541,PHID-USER-vm462i2ffbawnuo4mh3n,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I support not making assumptions about the editor, but I think making action=edit point to VisualEditor would break lots of things.",1420725110,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I think the editor should initialise at a canonical url. Perhaps with a way to force a specific editor but the vast majority of urls should point to the edit page without making assumptions about what editor that is. This means when we switch the default, existing urls will work as expected.
+
+We already have two different editors for wikitext (classic toolbar and WikiEditor). Though they don't have a way to switch without changing user preferences right now, WikiEditor loads on the old edit page. I think from a user perspective, VisualEditor should be introduced the same way.
+
+action=edit:
+* Would load editor based on user preference. Default user preference being the site default. As with any user preference, this preference can be made immutable or hidden from the preferences page if we don't want it to be per-user.
+* Use `&editor=...` to force a specific editor. This is what can be used when applications need to interoperate. E.g. in gadgets needing wikitext. Or when VisualEditor submits data to the wikitext editor (though it may incorporate its own wikitext editor). And of course in links like ""Edit"" / ""Edit source"". And permalinks (VisualEditor may want to do a pushState to editor=ve once loaded via plain action=edit so that one can share permalinks).",1420722912,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","What I meant is that a vocal group of English Wikipedia users hates VisualEditor's guts and would enjoy the new opportunity to spit on it. I hope this clarifies the issue. :)
+
+VisualEditor is also still not quite compatible with some languages and some wikis' conventions, so this would regardless need to be behind a configuration option.",1418717375,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",">>! In T55441#840960, @matmarex wrote:
+> I am not sure of this change will be beneficial at this point, given that VE is currently still used by  minority of users. It might result in more people disabling VE entirely.
+
+Why do you think so? I have a reason, why I set up VE and I am disappointed it doesn not work for creating new pages. Who might be disappointed from using it on VE?
+
+",1418699501,PHID-USER-vm462i2ffbawnuo4mh3n,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I reported this as a nead to create new page with VE. In this ligt there is a not logic message ""you follow the link to the page which does not exist"" Basically yes, but I had to do the step out of the page displayed with normal wikitext editing to the different one in VE. Once this bug removed, this can stay.",1418699317,PHID-USER-vm462i2ffbawnuo4mh3n,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","One question is whether we want to just overwrite existing edit links, or to add a new one, for example in the [[ https://www.mediawiki.org/w/index.php?title=VisualEditor&action=info&uselang=en#Page_properties | page properties ]] section.
+In the first case, we probably don't want that to happen on WMF sites at all.",1418291385,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Thanks for the patch. I think we should look for a solution that neither requires a user preference nor a forced standard for all users. Can we initialize the interface in a way that reflects the user's previous choice (for the first time, it is whatever the wiki's default is)? Can this be done intuitively without going all the way to reorganizing tabs? Partially a #design question.",1418289610,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I am not sure of this change will be beneficial at this point, given that VE is currently still used by  minority of users. It might result in more people disabling VE entirely.",1418289058,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","I am not sure of this change will be beneficial at this point, given that VE is currently still used by  minority of users. It might result in more people disabling VE entirely. Especially since it still doesn't support real section editing (T50429).",1418288995,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)","Change 178817 had a related patch set uploaded (by Ricordisamoa):
+Consistent edit links
+
+[[https://gerrit.wikimedia.org/r/178817]]
+
+#patch-for-review",1418211040,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+"VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)",Let's give it a try.,1418211003,PHID-USER-je4a7kqdfgacwkyhtg4c,True,PHID-TASK-r7e6j3kldhsiy2cc57wd,task_subcomment,NA
+VisualEditor: Pressing a modifier key (Ctrl/Alt/Shift/Cmd/etc.) when cursor is offscreen or under the toolbar causes the page to scroll up,"**Author:** `p.selitskas`
+
+**Description:**
+Reproducing:
+1. Open the VisualEditor
+2. Put the cursor in a place where ""Paragraph"" (or whatever else) disappears. (For example, into the ugly and unbearable empty line in pages with infobox at the very beginning.) The content editor must be kept active and cursor blinking.
+3. Scroll it down a bit.
+4. Press Ctrl, Alt, or Shift, or every possible combination of these
+5. See the content editor scroll up step by step (or as many steps per time as many keys are in combination.
+
+I can reproduce this in Chrome 29.0.1547.57 and Firefox 23.0.1 on Windows.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377634200,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oveveoihmpyqrm3ltjzu,task_description,resolved
+VisualEditor: Pressing a modifier key (Ctrl/Alt/Shift/Cmd/etc.) when cursor is offscreen or under the toolbar causes the page to scroll up,Seems to be fixed now.,1437759675,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-oveveoihmpyqrm3ltjzu,task_subcomment,NA
+VisualEditor: Pressing a modifier key (Ctrl/Alt/Shift/Cmd/etc.) when cursor is offscreen or under the toolbar causes the page to scroll up,"fwiw, this is still happening.",1383117125,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-oveveoihmpyqrm3ltjzu,task_subcomment,NA
+"VisualEditor: Toolbar icons - ""Transclusion"" (puzzle piece) alternatives or improvements","en.wp user Risker reports from an editathon that of the participants:
+""not a one of them understood what the ""puzzle piece"" was supposed to represent, and when shown, all of them still thought it was a poorly chosen icon.  Most had no suggestion as to an alternative, although two thought ""curly brackets"" would be a good idea.  I suspect that's because they'd seen curly brackets for templates when using wikitext.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51372",1377598380,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-wnl2ydoz2ca2h7xcsvtk,task_description,open
+"VisualEditor: Toolbar icons - ""Transclusion"" (puzzle piece) alternatives or improvements",Can we close this given we now show text in the menu?,1453915511,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wnl2ydoz2ca2h7xcsvtk,task_subcomment,NA
+"VisualEditor: Toolbar icons - ""Transclusion"" (puzzle piece) alternatives or improvements","(In reply to comment #0)
+> en.wp user Risker reports from an editathon that of the participants:
+> ""not a one of them understood what the ""puzzle piece"" was supposed to
+> represent, and when shown, all of them still thought it was a poorly chosen
+> icon.
+
+Yeah; we all hate it, and are using it because it's the least-bad option suggested so far (it's historically been the icon used in attempts at visual editors for MW since 2003).
+
+>  Most had no suggestion as to an alternative, although two thought
+> ""curly brackets"" would be a good idea.  I suspect that's because they'd seen
+> curly brackets for templates when using wikitext.""
+
+Indeed - we're trying to break the linkage with wikitext, and I don't think braces make for much of an increased level of obviousness.
+
+The new toolbar which allows buttons to self-describe if they're in a drop-down may help this significantly, but for now will keep this open.",1377831641,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wnl2ydoz2ca2h7xcsvtk,task_subcomment,NA
+"VisualEditor: Toolbar icons - ""Transclusion"" (puzzle piece) alternatives or improvements","**ypnypn9** wrote:
+
+How about just using the word ""Template""? Words are more obvious than even the best icons. (A disadvantage of this is that it would require a lot of translations, but this is not a huge problem.)",1377638244,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wnl2ydoz2ca2h7xcsvtk,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"This is probably an occurrence of an existing bug, but I couldn't find one that really fitted.
+
+In these edits, the table header was duplicated several times:
+
+https://fr.wikipedia.org/w/index.php?title=CM_Punk&diff=95906046&oldid=95898800
+https://fr.wikipedia.org/w/index.php?title=CM_Punk&diff=95848040&oldid=95838194
+https://fr.wikipedia.org/w/index.php?title=CM_Punk&diff=95778036&oldid=95766921
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377596700,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_description,resolved
+Broken wikitext inside a table leads to it and the table header being duplicated,"The rts look pretty reasonable to me these days. I'll assume whatever was causing the issue has cleared up.
+
+http://localhost:8000/_rt/frwiki/CM_Punk?oldid=95898800
+http://localhost:8000/_rt/frwiki/CM_Punk?oldid=95838194
+http://localhost:8000/_rt/frwiki/CM_Punk?oldid=95766921
+http://localhost:8000/_rt/frwiki/Utilisateur%3AElitre_%28WMF%29%2FProve_VE?oldid=100438786",1418097332,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"Yes, it is:
+https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve_VE&diff=100438830&oldid=100438786 .",1390237691,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,Is thist still an issue in production?,1386113968,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"Ya, I've responded to this here: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Multiplication_of_table_headers. 
+
+This general use case of fosterable content has been handled in Parsoid. Not sure why it is failing in production when I cannot reproduce it locally. To be investigated.",1380067514,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"Trying to work out what the cause of the bug is here; certainly, it's trying to operate on completely-broken wikitext, viz.:
+
+{| bgcolor=""#f7f0ff"" border=""1"" cellpadding=""2"" cellspacing=""0"" style=""font-size: 90%; border: gray solid 1px; border-collapse: collapse;""
+** '''[[Pro Wrestling Illustrated#Top 50 Females|Top 50 Females]]
+
+(!)
+
+This looks to have DSR issues as well (see the creation broken syntax with a single close-] alongside the partial wikitext non-DOM-sensicle duplication), and as the broken edits don't get a VE-check tag I'm assuming the DOM is clean from the VE end - moving to Parsoid.",1380067021,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+Broken wikitext inside a table leads to it and the table header being duplicated,"More of them, making a lot of damages.
+Any idea when someone will look at this bug, prioritize it, assign it and fix it ?
+
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=96858939&oldid=96858743
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=next&oldid=96858939
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=96801326&oldid=96761115
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=prev&oldid=96761115
+https://fr.wikipedia.org/w/index.php?title=Kelly_Kelly&diff=96119241&oldid=96014996",1379873418,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-pdsk3nihjnd2lxdtnwus,task_subcomment,NA
+"VisualEditor: Allow multiple commands (""keyboard shortcuts"") per tool on the same platform","Right now the CommandRegistry only takes a single command that can be used as a keybinding for a tool on a given platform (i.e. Mac, PC, etc.); it's thus not possible to have two keyboard shortcuts for the same tool, such as Undo (where both Ctrl+Y and Ctrl+Shift+Z are commonly used).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377533460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j32rmxvcdit6df4qvtqi,task_description,resolved
+"VisualEditor: Allow multiple commands (""keyboard shortcuts"") per tool on the same platform","(In reply to comment #1)
+> For ""Undo"" read ""Redo"" in James' comment
+
+Err. Yes. :-)",1377535865,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j32rmxvcdit6df4qvtqi,task_subcomment,NA
+"VisualEditor: Allow multiple commands (""keyboard shortcuts"") per tool on the same platform","For ""Undo"" read ""Redo"" in James' comment",1377533902,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-j32rmxvcdit6df4qvtqi,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","VE allows to mark text as both superscripted and subscripted (<sup><sub>text</sub></sup> or the other way). That sounds like a bad idea; such text simply ends up being displayed in smaller font.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377465840,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_description,resolved
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Let's leave the bug as fixed in the original fix, not the recent minor breakage.",1405043173,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",Verified the fix in production,1405033980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Change 143756 merged by jenkins-bot:
+Follow-up: If717ef98 – Re-add subscript and superscript removes to DM nodes
+
+https://gerrit.wikimedia.org/r/143756",1404341575,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Change 143756 had a related patch set uploaded by Catrope:
+Follow-up: If717ef98 – Re-add subscript and superscript removes to DM nodes
+
+https://gerrit.wikimedia.org/r/143756",1404341432,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",I can't reproduce. Steps?,1404313005,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","This is happening again, the superscript and subscript both are getting applied at the same time.",1404239230,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",Verified the fix in betalabs,1393631391,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Change 114488 merged by jenkins-bot:
+Allow annotations to remove other annotations
+
+https://gerrit.wikimedia.org/r/114488",1393453702,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Yeah, that's what I meant. Thanks.",1392914022,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(In reply to Bartosz Dziewoński from comment #9)
+> (In reply to James Forrester from comment #8)
+> > (a) what should happen in VE when the user attempts this
+> 
+> Text should be either super- or subscripted, not both.
+> 
+> Nesting superscripts in subscripts, subscripts in superscripts,
+> subscripts in subscripts and superscripts in superscripts
+> should be impossible, just like it's impossible to nest links in other
+> links. Currently only the last two are impossible.
+
+This works for me. Re-wording bug for clarity – is this acceptable to you?",1392913756,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Change 114488 had a related patch set uploaded by Esanders:
+Allow annotations to remove other annotations
+
+https://gerrit.wikimedia.org/r/114488",1392913587,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(In reply to Ed Sanders from comment #10)
+> I don't think we need to alienate such nested content though, in the same
+> way we don't alienate a double bold tag (if someone used one). As long as
+> the user doesn't try to change the sub/superscripting, the annotations will
+> remain untouched.
+
+I'm willing to trust you on implementation details :)",1392911441,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","I agree that the sub/superscript tool should clear any other sub/superscript annotations present. As pointed out you can't do a double superscript, so clearly our goal is not to let you create any complex hierarchy you want, that's for <math>.
+
+I don't think we need to alienate such nested content though, in the same way we don't alienate a double bold tag (if someone used one). As long as the user doesn't try to change the sub/superscripting, the annotations will remain untouched.",1392911200,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(In reply to James Forrester from comment #8)
+> (a) what should happen in VE when the user attempts this
+
+Text should be either super- or subscripted, not both.
+
+Nesting superscripts in subscripts, subscripts in superscripts,
+subscripts in subscripts and superscripts in superscripts
+should be impossible, just like it's impossible to nest links in other
+links. Currently only the last two are impossible.
+
+> (b) what should happen in VE when the page already has this
+
+The same thing that happens with all other unsupported input: it
+should be alienated and left alone.
+
+> (c) what should be changed in MediaWiki's PST to stop this happening
+> in future(?).
+
+Nothing. I suppose there are very rare use cases where this could be
+wanted, we should just keep supporting them for backwards-compatibility.
+
+In fact, the only things that I see in existing articles are currently
+impossible in VE – you can't nest superscripts to produce, say,
+10<sup>10<sup>26</sup></sup> (10^{10^26}) used in [[pl:Oś czasu dalekiej
+przyszłości]]. Arguably this should just use <math/> tags though.",1392900216,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","Wikitext lets you do this too. Do you think we should just silently kill all examples of this in the database? :-)
+
+Closing again unless you can suggest (a) what should happen in VE when the user attempts this, (b) what should happen in VE when the page already has this, and (c) what should be changed in MediaWiki's PST to stop this happening in future(?).",1392749738,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","A dupe was just filed, this is not just me. Reopening.",1384111164,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",*** Bug 56795 has been marked as a duplicate of this bug. ***,1384111137,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","As input, sure. But as output, HTML lets you do lots of things that VE doesn't.",1377476809,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(In reply to comment #2)
+> Do other text editors permit that? I don't know of any that would.
+> 
+> (Or in other words, this is not fitting users' expectations.)
+
+Well, HTML lets you do this, which means VE needs to support it on the input side at the very least.",1377474493,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","(Or in other words, this is not fitting users' expectations.)",1377467182,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)",Do other text editors permit that? I don't know of any that would.,1377467085,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+"VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)","I don't see how this is a bug? Yes, it's bad, in the same way that setting text's colour to be white, or putting an image inside another image's caption, but that doesn't mean we should stop people doing it…
+
+Generally, appropriate use of the software is a social thing, not a software thing. Willing to be convinced otherwise, but for now I'll mark this as a WONTFIX.",1377466817,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oml53qiv2ffx7tuvmx47,task_subcomment,NA
+ULS support needed in VisualEditor's dialog boxes,"We need ULS support in dialog boxes-
+
+1) Template dialog boxes - adding existing template for setting paratmeters
+2) Image dialog box
+3) Adding or editing references
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377447360,PHID-USER-qpuuryo2o37amdlkb5gk,False,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_description,resolved
+ULS support needed in VisualEditor's dialog boxes,Fixed with https://gerrit.wikimedia.org/r/#/c/264577/,1454774965,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_subcomment,NA
+ULS support needed in VisualEditor's dialog boxes,"Pavanaja: Can you elaborate on what you mean by ""We need ULS support in dialog boxes"". I think you mean ""input method support"", but I'd like to be sure.
+
+Additionally, if you could please add the following:
+1. Numbered steps to reproduce.
+2. Observed behavior
+3. Expected behavior
+
+This would allow us to unambiguously understand what you expect, and work towards resolving the issue you experience.",1378119977,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_subcomment,NA
+ULS support needed in VisualEditor's dialog boxes,"(In reply to comment #0)
+> We need ULS support in dialog boxes-
+> 
+> 1) Template dialog boxes - adding existing template for setting paratmeters
+> 2) Image dialog box
+> 3) Adding or editing references
+
+Is this something that is done on the VisualEditor side, or inside ULS? I'm pretty sure that there was no change made in VE for the enabling of jquery.IME inside the main VisualEditor surface…
+
+(Please move back if I'm wrong.)",1377823487,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_subcomment,NA
+ULS support needed in VisualEditor's dialog boxes,"[New feature => setting the ""Severity"" field to ""enhancement"". 
+Feel free to do so yourself when filing a report.]
+
+(In reply to comment #0)
+> We need ULS support in dialog boxes-
+> 
+> 1) Template dialog boxes - adding existing template for setting paratmeters
+> 2) Image dialog box
+> 3) Adding or editing references
+
+Please please elaborate what that means, for example steps to reproduce, current outcome, and expected outcome. Also see https://www.mediawiki.org/wiki/How_to_report_a_bug",1377460860,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ye62pxccv2jh5w3o2yl7,task_subcomment,NA
+VisualEditor: Can't return to save dialog after reviewing null edit,"reported on en.wp by Atethnekos:
+
+""So I put a space and then a backspace. Go to save, review changes to check and make sure it is a null edit, then it goes to this ""processing"" dialogue but then it shows ""Could not start the review because your revision matches the latest version of this page."" So then I press the little back link on the dialogue, but it just goes back to the processing dialogue. If the page is small, the processing is really quick, so before I can even press back again, it goes back to the ""Could not start"" warning message. Even if I do manage to press the back a second time quickly, it will only stay at the save dialogue for a split second and then again bring me to the warning message, although then pressing back does take me to the save dialogue securely. FF 23.0.1 Win7""
+
+I've confirmed this in Firefox 23.0 on Linux.
+The issue is with the < link only. Clicking the ^ does return you to the editing screen as expected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377426420,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_description,resolved
+VisualEditor: Can't return to save dialog after reviewing null edit,"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.",1381187081,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_subcomment,NA
+VisualEditor: Can't return to save dialog after reviewing null edit,"Change 81876 merged by jenkins-bot:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1381186923,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_subcomment,NA
+VisualEditor: Can't return to save dialog after reviewing null edit,"Change 81876 had a related patch set uploaded by Jforrester:
+Make the save dialog an actual dialog
+
+https://gerrit.wikimedia.org/r/81876",1378325644,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_subcomment,NA
+VisualEditor: Can't return to save dialog after reviewing null edit,*** Bug 53314 has been marked as a duplicate of this bug. ***,1377426954,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ezxtdsztbaq4wuvaxjmv,task_subcomment,NA
+"VisualEditor: When reversing a transaction, create a new transaction rather than reusing the old one","Rather than passing around boolean parameters called 'reversed' all over the place, we should use each transaction only once, and implement a function that creates a new transaction that's the reverse of an existing transaction.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377192420,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-chjb2m7r6pmqmr457wgg,task_description,resolved
+"VisualEditor: When reversing a transaction, create a new transaction rather than reusing the old one",This was done ages ago in I3050c5430be4a12510f22e20853560b92acebb67,1394478857,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-chjb2m7r6pmqmr457wgg,task_subcomment,NA
+"VisualEditor: When reversing a transaction, create a new transaction rather than reusing the old one","But note that the code currently uses the fact that the commit and rollback transaction are the same in order to update the 'applied' field.  So the rollback transaction should still contain a pointer to the original transaction, and when it is committed both should be marked with 'applied=false' (which indicates that we can skip over these entries in the completeHistory).",1377652795,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-chjb2m7r6pmqmr457wgg,task_subcomment,NA
+VisualEditor: Undo/redo doesn't go through dm.Surface.change() code path,"dm.Surface.undo() and .redo() just call documentModel.rollback() / .commit() directly, without going through all the other stuff in .change() . Presumably this other stuff is useful, so we should figure out if bypassing it causes bugs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377191640,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-va4nmthl5rer6qeyil6y,task_description,resolved
+VisualEditor: Undo/redo doesn't go through dm.Surface.change() code path,"Change 88728 merged by jenkins-bot:
+Implement ve.dm.Surface.prototype.undo() and redo() in terms of change()
+
+https://gerrit.wikimedia.org/r/88728",1382735134,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-va4nmthl5rer6qeyil6y,task_subcomment,NA
+VisualEditor: Undo/redo doesn't go through dm.Surface.change() code path,"Change 88728 had a related patch set uploaded by Catrope:
+Implement ve.dm.Surface.prototype.undo() and redo() in terms of change()
+
+https://gerrit.wikimedia.org/r/88728",1381326083,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-va4nmthl5rer6qeyil6y,task_subcomment,NA
+VisualEditor: Undo/redo doesn't go through dm.Surface.change() code path,In theory Surface.change() should also have a corresponding Surface.unchange() method (or a 'reversed' parameter).,1377191752,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-va4nmthl5rer6qeyil6y,task_subcomment,NA
+"VisualEditor: When editing a section, don't wait for loading to be complete before scrolling to the section","When loading VisualEditor from a section edit link, the editor opens at that position on the page. However, as the TOC is not displayed in edit mode (bug 49224) the content is effectively rendered higher up so a later section in the article moves into the view (from a users point of view this is perceived as scrolling to a random point). 
+
+The view point does move to the new location of the desired section as the final step of loading, but only if the user has not scrolled at any point while waiting. 
+
+If they have attempted to find the section themselves while VE is loading then either (a) the view point subsequently doesn't move when loading completes, or (b) moves by the amount it would have done if the user had not scrolled (meaning it now points at a different point to desired). I have not worked out how to specifically induce one behaviour or indeed what causes either.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T51224}
+{T52206}
+{T54577}",1377187440,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-evkujyihqmirmqqeozmk,task_description,duplicate
+"VisualEditor: When editing a section, don't wait for loading to be complete before scrolling to the section","Should this be closed in favor of T52206?
+Also see T87556.",1423683149,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-evkujyihqmirmqqeozmk,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"I clicked to edit a section of a long article, and when I tried to file a bug, it looked like the screen just went dark - I couldn't immediately see a dialog box. It turned out to be because the feedback dialog was overlayed above the section I was editing, which was way, way down the page, and the browser didn't scroll to that part of the page when I pressed the button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377115140,PHID-USER-bug3zrlooz3bdmi4fyl7,False,PHID-TASK-5cuwqt62enm5hymwly75,task_description,declined
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"Unfortunately closing this Phabricator task as no further information has been provided.
+
+@Greenrd: After you have provided the information asked for and if this still happens, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks!",1590842330,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"Ahm, I'm sorry (obviously requires VE to be enabled to see those section heading links).
+Tried on http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Arrr0.5320366523148922&veaction=edit&vesection=2 but still the ""Submit feedback"" dialog is centered. 
+Still cannot reproduce with Chrome 41 or Firefox 36.",1425554338,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"@Greenrd: Sorry that this task has not received feedback earlier, and thank you for reporting this!
+
+> I clicked to edit a section of a long article
+
+Where did you click exactly? Link to that long article is also very welcome. :)
+
+> and when I tried to file a bug, it looked like the screen just went dark - I couldn't immediately see a dialog box. It turned out to be because the feedback dialog was overlayed above the section I was editing
+
+Does this refer to the ""Leave Feedback / Submit Feedback"" dialog available from the ""Help"" (question mark) button in VE's toolbar?
+
+I cannot reproduce in Firefox 36 and Chrome 41 trying with https://en.wikipedia.org/wiki/Hamburg?veaction=edit - is this still a problem?
+Setting task status to ""Stalled"" for the time being...",1425554071,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"(In reply to comment #1)
+> Which browser is this about?
+
+Chromium Version 27.0.1453.93 Built from source for Fedora release 18",1377160124,PHID-USER-bug3zrlooz3bdmi4fyl7,False,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Feedback dialogs not scrolled to when editing section on long page,"Thanks for taking the time to report this!
+
+Which browser is this about?",1377119887,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5cuwqt62enm5hymwly75,task_subcomment,NA
+VisualEditor: Annotating an inline alien breaks node protection,"1. Create a document with:
+   Foo <cite>Alien</cite> Bar
+2. Select all and bold
+
+Results
+3. 'Alien' is bolded, despite being protected (questionable)
+4. The shield has disappeared.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377085200,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-tyb65vkuz46fcurmj72h,task_description,resolved
+VisualEditor: Annotating an inline alien breaks node protection,"This seems to behave correctly these days.
+
+3. It is still bolded, but I think that's usually the right behavior. (We could change this by using `blacklistedAnnotationTypes`, which we use now mostly to disallow applying link annotations over nodes that already contain links.)
+4. This doesn't happen, the ""shield"" is still present and catches clicks. (I believe that's the same thing that we call ""highlights"" now, the striped overlay thing?) {F31513637}",1579117639,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tyb65vkuz46fcurmj72h,task_subcomment,NA
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Both ve.dm.ModelRegistry.js and its test file have references to  /^mw:/ . Any code relating to mw should be in modules/ve-mw/
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377084540,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-hia733wv6lu2vvjmm2xv,task_description,resolved
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Change 116487 merged by jenkins-bot:
+Update VE core submodule to master (74be717)
+
+https://gerrit.wikimedia.org/r/116487",1393875313,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hia733wv6lu2vvjmm2xv,task_subcomment,NA
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Change 116485 merged by jenkins-bot:
+Remove MW-specific config and genericise tests in ModelRegistry
+
+https://gerrit.wikimedia.org/r/116485",1393874576,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hia733wv6lu2vvjmm2xv,task_subcomment,NA
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Change 116487 had a related patch set uploaded by Esanders:
+MW configuration for modelRegistry
+
+https://gerrit.wikimedia.org/r/116487",1393858493,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hia733wv6lu2vvjmm2xv,task_subcomment,NA
+VisualEditor: Move MW-specific code out of the VE-core model registry,"Change 116485 had a related patch set uploaded by Esanders:
+Remove MW-specific config and genericise tests in ModelRegistry
+
+https://gerrit.wikimedia.org/r/116485",1393858486,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hia733wv6lu2vvjmm2xv,task_subcomment,NA
+Clean up single vs. multi-part data-mw,"We currently use { target: {}, params: {} } for single-transclusion content, and {parts: [{template:{target: {}, params: {}, i: 0}}]} for multi-part transclusions and extensions. This creates special cases and makes it necessary to know all keys to convert the single-transclusion format into the parts bit.
+
+The missing namespacing also makes it harder than necessary to add additional information to data-mw.
+
+To clean this up, we should consider moving to always using an array format like this:
+
+parts: [{""@type"":""mw:Transclusion"", target: {}, params: {}}]
+
+The change to always use an array is already supported by VisualEditor. Flattening the nested object and using a JSON-LDish @type key makes the parts structure more regular and easier to extend. It also moves it closer to the RDFa names. Both us and VE can support both formats as an input for a while to avoid caching issues, but should start by only emitting the new format.
+
+See also:
+http://json-ld.org/playground/index.html -- some example JSON-LD
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377042960,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-iwz7tbppv2hen4mzt3ny,task_description,open
+Clean up single vs. multi-part data-mw,"The other changes in this ticket will require co-ordination with VE since it will break existing code.
+
+This will also require the cached HTML versioning to be implemented to prevent weird editing errors between when parsoid is deployed and varnish caches or cleared.  Alternatively, VE and Parsoid serializer would have to handle old and new formats of data-mw temporarily.",1377558860,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-iwz7tbppv2hen4mzt3ny,task_subcomment,NA
+Clean up single vs. multi-part data-mw,"Change 81143 merged by jenkins-bot:
+(Bug 53135) Step 1: Always use parts array for transclusion data-mw
+
+https://gerrit.wikimedia.org/r/81143",1377558504,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iwz7tbppv2hen4mzt3ny,task_subcomment,NA
+Clean up single vs. multi-part data-mw,"Change 81143 had a related patch set uploaded by Subramanya Sastry:
+(Bug 53135) Step 1: Always use parts array for transclusion data-mw
+
+https://gerrit.wikimedia.org/r/81143",1377557762,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iwz7tbppv2hen4mzt3ny,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**Author:** `p.selitskas`
+
+**Description:**
+Please create an icon with bold cyrillic ""Т"" for [be] and [be-tarask].
+
+In Belarusian locales ([be] and [be-tarask]), the Bold icon is now read as ""Тл"" which may be interpreted as ""Тлусты"" (fat), but in fact it makes the selected text not fat, but bold (""Тоўсты""). :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377007260,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_description,resolved
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,This should now be fixed in production; sorry for the delay.,1379364856,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84361 merged by jenkins-bot:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84361",1379357724,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84361 had a related patch set uploaded by Reedy:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84361",1379357517,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84095 merged by jenkins-bot:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84095",1379355814,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84095 had a related patch set uploaded by Catrope:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84095",1379023642,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,You're welcome. It does.,1379019052,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #17)
+> Argh, sorry about this mess; we'll back-port the fix.
+
+Thanks for swift resolving! Does it mean the 'fix fix' will be deployed soon out of general deployment schedule?",1379015228,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Argh, sorry about this mess; we'll back-port the fix.",1379011818,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84027 merged by jenkins-bot:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84027",1379011697,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 84027 had a related patch set uploaded by Esanders:
+Fix merge conflict breaking localised bold/italic icons
+
+https://gerrit.wikimedia.org/r/84027",1379011477,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,This is the offending commit: https://gerrit.wikimedia.org/r/#/c/81522/,1379011117,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #12)
+> Looks like Trevor's toolbar rewrite didn't merge cleanly with my commits and
+> they were partially undone.
+
+Obviously. I was not aware of the rewrite and first thought that the patch was merged but hasn't appeared in the codebase (black magic).",1379008274,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,Looks like Trevor's toolbar rewrite didn't merge cleanly with my commits and they were partially undone.,1379007349,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #10)
+> (In reply to comment #9)
+> > te-el shouldn't exist as it was replaced with just te, so maybe this is a
+> > caching issue?
+> 
+> https://bits.wikimedia.org/static-1.22wmf16/extensions/VisualEditor/modules/
+> ve/ui/styles/images/icons/bold-cyrl-te-el.svg
+> 
+> 404 (PNG as well). And I'm not counting the absent CSS class that should
+> display this icon. Did the deployment come smoothly? :)
+
+Oh, I'm sorry, I checked the wrong file. Anyway, JS adds the wrong class.",1379006964,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #9)
+> te-el shouldn't exist as it was replaced with just te, so maybe this is a
+> caching issue?
+
+https://bits.wikimedia.org/static-1.22wmf16/extensions/VisualEditor/modules/ve/ui/styles/images/icons/bold-cyrl-te-el.svg
+
+404 (PNG as well). And I'm not counting the absent CSS class that should display this icon. Did the deployment come smoothly? :)",1379006874,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"te-el shouldn't exist as it was replaced with just te, so maybe this is a caching issue?",1379006381,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+Class .ve-ui-icon-bold-cyrl-te-el was not created/generated, and now there is empty space instead of a ""Bold"" icon. Reopening the bug.",1379006056,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,Now merged and will go out in about an hour.,1377035770,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,Also related: https://gerrit.wikimedia.org/r/80126,1377029951,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"The be-tarask icons are now changed (and this version of the software will go out in a few hours' time); keeping the bug open for making it work with both be and be-tarask, as part of a general fall-back mode.",1377022483,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 80049 merged by jenkins-bot:
+Change be-tarask to use Te instead of Te-El for bold
+
+https://gerrit.wikimedia.org/r/80049",1377022412,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"**p.selitskas** wrote:
+
+(In reply to comment #1)
+> We don't currently support [be], just [be-tarask]. Can you confirm that we
+> should use the same icons for [be] (bold: T, italic: K)?
+
+Yes, I confirm this suggestion.",1377017841,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"Change 80049 had a related patch set uploaded by Esanders:
+Change be-tarask to use Te instead of Te-El for bold
+
+https://gerrit.wikimedia.org/r/80049",1377017622,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon,"We don't currently support [be], just [be-tarask]. Can you confirm that we should use the same icons for [be] (bold: T, italic: K)?",1377017564,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7uqnmenedinwiui6wz4s,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","It first happened to the user who was trying to add a wikilink to a large page,  https://en.wikipedia.org/wiki/List_of_Criterion_Collection_DVD_and_Blu-ray_releases; he got the error while in VE so he made that edit with the classic editor later.
+He then copied the contents of the page to a sandbox - https://en.wikipedia.org/wiki/User:Marc_Kupper/sandbox2 -  for further testing and these are his findings:
+
+<< It took 74 seconds to load the page in VE, I made the change, save-page, give a reason (wikilink - testing VE), save-page again. After 1:45 (105 seconds) I got ""Error: Unknown error"" in the lower part of VE's edit-summary box. The save-page button is grayed out.
+I don't think the actual edit I did matters. If someone wants to reproduce using my sandbox then the edit was in the last paragraph of the lead. Where it says ""...Essential Art House, Eclipse, and Merchant Ivory Collection..."" I changed ""Eclipse"" to [[Eclipse (DVD)|Eclipse]] by double-clicking on Eclipse to select, control-K to bring up the insert/edit link box, appending "" (d"" to the link-to value, click ""Eclipse (DVD)"" in the list of offerings, and then press <enter> a couple of times to close out the box. I suspect you can make any change you want. --Marc Kupper|talk 22:06, 19 August 2013 (UTC)
+
+
+After documenting how I did the edit I tried the save again and again got the error. It happened 1:44 (104 seconds) after clicking save. I suspect the 105 seconds above is simply because I was a bit slow reacting as this time I was waiting for the error right around the 1:45 mark. --Marc Kupper|talk 22:06, 19 August 2013 (UTC)
+I then did the following tests
+I replaced all non-alphabetic characters with the letter ""x"" and can edit the page with VE. It appears the issue is with something in the page content, possibly combined with the page size.
+I removed all 'ref' tags. Saving from VE still fails after 1:44
+I removed most of the templates transcluded on the page. Saving with VE worked and took 1:17. However, I had intended to just add ""xxx"" in the middle of a word. VE also stripped a table in another part of the article of wikitext. (https://en.wikipedia.org/w/index.php?title=User%3AMarc_Kupper%2Fsandbox2&diff=569295763&oldid=569295507 ) --Marc Kupper|talk 23:16, 19 August 2013 (UTC)
+
+I don't have time to debug this further at present - particularly as we now have two VE issues. The next step is to revert back to 22:48, 19 August 2013 and to then see if I can narrow it down from there. --Marc Kupper|talk 23:11, 19 August 2013 (UTC) >>
+
+I tested on the first version of the sandbox as well, it took me almost 75 secs as well to load the page, I wikilinked a word and then hit Save - it took me 2min 15sec to get the error message while actually the edit was saved.  Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70726
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51636",1377006180,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_description,open
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)",">>! In T55093#572665, @GWicke wrote:
+> The issue does not seem to be specific to any particular page. At https://en.wikipedia.org/wiki/OpenOffice.org?veaction=edit for example an initial
+> load of 215k turns into a 3.6mb POST.
+> 
+> Possible remedies:
+> * use gzip compression for the POST request body
+> * use multipart/form-data POST encoding instead of application/x-ww-form-urlencoded to avoid percent encoding overhead
+> * send HTML as a separate POST variable without JSON wrapper to avoid JSON escaping, in particular of quotes
+
+Where are you seeing this? VE already does all of these things, which I just confirmed at https://en.wikipedia.org/wiki/OpenOffice.org?veaction=edit in Chrome. The POST that occurs when the (first) save button is pressed has a `multipart/form-data` POST body with gzipped content (the value of the `html` parameter starts with `rawdeflate,7H1rd9tGkuj3+RW9`). The POST that occurs when the second save button is pressed only sends a `cachekey` value, no large blob of HTML.
+
+You should not have been able to trigger a multi-megabyte POST upload. Perhaps you observed a cachekey miss and there's a bug where the POST body is not compressed in that case?",1440110032,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)",">>! In T55093#572665, @GWicke wrote:
+> Some additional info about the POST size issue on save:
+> 
+> To check the POST request size, I looked at the Content-Size header in the request headers once that completed (request to api.php started when opening the save dialog).
+> 
+> The issue does not seem to be specific to any particular page. At https://en.wikipedia.org/wiki/OpenOffice.org?veaction=edit for example an initial
+> load of 215k turns into a 3.6mb POST.
+
+You're saying that the page downloads gzipped at a weight of 215k and then when the browser goes to re-upload it has a weight of 3.6mb uncompressed? That sounds pretty bad to me.",1440108913,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)",Strike the last point about JSON- the HTML is already sent as a plain query parameter without JSON wrapper.,1388954245,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","Some additional info about the POST size issue on save:
+
+To check the POST request size, I looked at the Content-Size header in the request headers once that completed (request to api.php started when opening the save dialog).
+
+The issue does not seem to be specific to any particular page. At https://en.wikipedia.org/wiki/OpenOffice.org?veaction=edit for example an initial
+load of 215k turns into a 3.6mb POST.
+
+Possible remedies:
+* use gzip compression for the POST request body
+* use multipart/form-data POST encoding instead of application/x-ww-form-urlencoded to avoid percent encoding overhead
+* send HTML as a separate POST variable without JSON wrapper to avoid JSON escaping, in particular of quotes",1388703828,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","At
+https://en.wikipedia.org/wiki/List_of_Criterion_Collection_DVD_and_Blu-ray_releases?veaction=edit,
+I am seeing a 5.6mb upload on preview. This takes 47 seconds to transfer
+using my DSL connection. Connections with slower upload speeds would do
+worse, and possibly time out. The POST processing and response then
+takes 7.9 seconds according to the Chromium network console.
+
+For comparison, the HTML downloaded on VE open is 238kb in size and
+takes 3 seconds to load. Total load time until VE is ready is around 36
+seconds, again using Chromium.
+
+In my experience Firefox's client-side processing would be a bit slower.",1388698096,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","A user is reporting this problem at
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=588582743#Reliable_but_not_powerful",1388536381,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","Ok, so comment #3 should read that in one occasion,
+David got the message, the edit was not saved.
+Editing the same article, I didn't get the message, and my edit was saved.
+In other cases, it is possible to get the message and having the edit saved.",1380198153,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","I got ""Error: unknown error"", but the error saved anyway, on this edit: https://en.wikipedia.org/w/index.php?title=OpenOffice.org&curid=68227&diff=574513723&oldid=574510970 - first time I've ever had the error and it did in fact save.
+
+I'm now wondering if having the error and the edit not being saved is the same bug as having the error and the edit being saved.",1380197582,PHID-USER-gfaq55vdypjmzz6nl2kn,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","A fr.wp user reports he was confused when he got this message, since the edit was saved anyway.",1380125629,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","David Gerard and I had different experiences about this bug.
+He tried to edit https://en.wikipedia.org/wiki/Neuro-linguistic_programming , while I basically copy/pasted that article in my sandbox https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=573778358 and then attempted to change it.
+After 100 secs or so, VE managed to save our edits, but he got the error message, while I didn't. HTH.",1379794141,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","Here http://en.wikipedia.org/w/index.php?title=Fairfield%2C_Iowa&diff=569923054&oldid=569069756 is another case of the error message being thrown after an actually successful edit.
+The user wonders: "" it would be useful to know the current confidence limits around page length and the ability to edit same. Is it dependent upon local environment (i.e. PC configuration and memory allocated to browser)? Or is there a server side known performance limit?"".
+Thanks.",1377340698,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+"For very large pages on slow connections (when a timeout happens?), users get an ""Error: Unknown error"" on saving changes in VisualEditor (but change is indeed saved)","(User specs, Vista - FF23 - Vector.)",1377007870,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mx73qk7qlj7jty4xm3o5,task_subcomment,NA
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"Screenshot
+
+Blocked IP addresses can see the VisualEditor, use it, and are presented with the error in the screenshot when saving.
+
+Reporting distinctly from bug 52004 because the error message and use case are both somewhat different.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52004
+
+**Attached**: {F11450}",1376861280,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-r3aliipwenpyb4simxc3,task_description,resolved
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"As with the normal local block bug, I'm going to mark this as fixed. We don't block the user from using VE, but there is now a notice warning them when they open VE.
+
+It would be difficult to get all the useful info into some smaller alert() message or similar. Though after thinking about it a bit more we could perhaps use a small VE dialog or something, I am open to suggestions of course - but perhaps that would be better to put in a more general ""not able to edit page due to protection/block/etc. dialog error"" as this patch simply brings global blocks into line with normal blocks, protection etc.",1398210636,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-r3aliipwenpyb4simxc3,task_subcomment,NA
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"Change 127840 merged by jenkins-bot:
+Show notice if user is globally blocked
+
+https://gerrit.wikimedia.org/r/127840",1398207749,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r3aliipwenpyb4simxc3,task_subcomment,NA
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"That error message that you do get on saving is also a bug of it's own, patched in Gerrit change 127835",1398126343,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-r3aliipwenpyb4simxc3,task_subcomment,NA
+VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message,"Change 127840 had a related patch set uploaded by Alex Monk:
+Show notice if user is globally blocked
+
+https://gerrit.wikimedia.org/r/127840",1398126310,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-r3aliipwenpyb4simxc3,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer","The thermometer is important, as it explains why a radically modified document would give me an empty ""review changes"" box.
+
+Separate bugs: the thermometer never stops spinning, and my changes for review never appear--maybe Parsoid is gagging.  And, is that UI javascript running without a setTimeout?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1376813460,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-h7psvvdxqq5nurzgtxts,task_description,declined
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer","We can't reproduce this now, so closing as WORKSFORME.",1392062928,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer",I don't see a thermometer. :|,1391916090,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer","Sorry.
+
+* Edit a page, making changes
+* Click ""Save page"".  Save dialog pops down, and thermometer is spinning.
+* Click ""Review changes"" before the thermometer stops.
+The save dialog collapses down to a single line, which contains only the ""Review changes"" button, a left arrow button, and an up button.  This is strange.  The thermometer is gone.  There is no explanation of why i am presented with this damaged dialog.
+
+Apparently, with my broken VE, the loading/render/whatever the thermometer represents never finishes.  Which made it very easy to reproduce this other bug.",1376956217,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer","Trying to parse this. Is this:
+
+1. 'VisualEditor: Clicking ""Review changes"" mid-save causes the save dialog to disappear, which takes the save progress animation thermometer'
+
+… or
+
+2. 'VisualEditor: Clicking ""Review changes"" mid-save causes the save dialog to collapse but stay present, and also the save progress animation thermometer stays but stops animating'
+
+… or something else?",1376953643,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+"VisualEditor: Clicking ""Review changes"" collapses save dropdown, and disappears the thermometer",How does a thermometer spin?,1376814507,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-h7psvvdxqq5nurzgtxts,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**Author:** `jamesjoshualim`
+
+**Description:**
+Hi, everyone.  Yesterday, we had a meetup here in Manila, and I discussed with two Tagalog Wikipedia editors (including a fellow bureaucrat) about the creation of a new interface language for Tagalog in a bid to resolve long-standing differences over how the interface should be translated.  We agreed on a compromise solution, where we would accommodate Taglish (code-switched Tagalog and English) as a new interface language called ""Tagalog (informal)"" for the Tagalog-language projects, similar to how there is an interface language for formal German (de-formal).
+
+We decided that this new interface language will become the default interface language for all anonymous and new users on the Tagalog Wikipedia, in order to attract new editors who may be confused by the formal language used for the current Tagalog interface.  The current interface will be opt-in for those who want to use the interface as it currently is, and users will have the ability to select their preferred language using the Universal Language Selector which will only have Tagalog, Tagalog (informal) and English as the options.  All other languages may still be selected through the preferences.
+
+If this is possible to do, I'd love to see this come to fruition, and I hope to hear from all of you soon.  Thanks! :)
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1376723820,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_description,stalled
+Creation of tl-informal as a new interface language,"Or even better: https://www.mediawiki.org/wiki/Internationalisation_wishlist_2017#Better_support_for_formal_and_informal_variants
+
+This assumes that it is only wanted for interface, and that differences are not that big.",1511791485,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"Because language converter would need to cater to exceptions, the better way to do this is probably just open up a language and then only translate those that are different and then let the other terms fallback to Tagalog just like how zh_HK<>zh-Hant have been handled.
+
+That is provided that if a consensus are to be reached.",1511459800,PHID-USER-yba5kkq4bvwironiorlq,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,It might be possible to implement informal variants using LanguageConverter; see T33015#3183625,1492196403,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"This likely should be discussed *within* the community in order to reach consensus and support, however http://tl.wikipedia.org/wiki/WP:KAPE seems pretty inactive. Is there a better place?",1398135439,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jojit_fb** wrote:
+
+One more thing, why is it the localization project of the Mozilla Tagalog interface has no problems with retaining the technical terms untranslatable?  We can follow their example.",1398133896,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jojit_fb** wrote:
+
+(In reply to Josh Lim from comment #4)
+> (In reply to Joseph Ballesteros from comment #3)
+> > As a veteran editor in the Tagalog Wikipedia, I disagree with this.  I think
+> > it's redundant and I am for only one interface language for Tagalog.  I
+> > suggest that this should be discussed first with more editors.
+> 
+> It is not redundant when language issues are as divisive as they are on the
+> Tagalog Wikipedia.  Short of forcing everyone to abide by one standard
+> (which will not happen, given persistent conflicts between purists,
+> moderates and progressives/universalists) or creating two different
+> Wikipedias for Tagalog and Filipino, this is the best solution that can be
+> conceived.
+> 
+> (Also, I posted a discussion on this on both the Tagalog Wikipedia Facebook
+> group and the Kapihan months ago.)
+
+We cannot accommodate everyone.  We have to always look at what the majority of readers of the Tagalog Wikimedia projects understand.  They don't understand what is kasaputan, lambat-lambat and what have you. I realize the need to translate the interface after conducting editing workshops across the Philippines.  Most people in the workshops don't understand what is ""lumagda."" They understand the term ""login"" instead. 
+
+I bet that even some purists will laugh at the phrase ""Wala ka pa bang kuwenta?""  Do you even realize that in normal conversation the phrase may be translated as ""Are you still a useless person?"" instead of ""Don't have an account""?  I bet also that those so called purists also speak unpurely in normal conversation.  
+
+I believe it's still redundant and will add another burden to a handful of volunteers just to accommodate the principles of a few people.
+
+Another thing, it's not necessarily informal or Taglish when you use borrowed foreign words in a phrase or sentence.  There are words (especially technical terms) that are really untranslatable.  Forcing the translation will result to lots of misinterpretation just like with the term ""kuwenta.""  Thus, tl-informal is a misnomer and will just add to the confusion.
+
+I haven't seen a discussion in the WP:KAPE (or the Kapihan in the Tagalog Wikipedia) about this.  You are aware that I don't have a Facebook account and if you have posted that in Facebook, I haven't read it.  Instead of Facebook (where not all people who are involved in the projects are there), I recommend that you start a new section at WP:KAPE and discuss this further.  Please don't reply me here.",1398132909,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jamesjoshualim** wrote:
+
+(In reply to Joseph Ballesteros from comment #3)
+> As a veteran editor in the Tagalog Wikipedia, I disagree with this.  I think
+> it's redundant and I am for only one interface language for Tagalog.  I
+> suggest that this should be discussed first with more editors.
+
+It is not redundant when language issues are as divisive as they are on the Tagalog Wikipedia.  Short of forcing everyone to abide by one standard (which will not happen, given persistent conflicts between purists, moderates and progressives/universalists) or creating two different Wikipedias for Tagalog and Filipino, this is the best solution that can be conceived.
+
+(Also, I posted a discussion on this on both the Tagalog Wikipedia Facebook group and the Kapihan months ago.)",1398091189,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jojit_fb** wrote:
+
+As a veteran editor in the Tagalog Wikipedia, I disagree with this.  I think it's redundant and I am for only one interface language for Tagalog.  I suggest that this should be discussed first with more editors.",1398073332,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"**jamesjoshualim** wrote:
+
+(In reply to comment #1)
+> Is this asking for:
+> 
+> 1) Creating a new interface language, tl-informal, in TranslateWiki.net
+> 2) Creating a new interface language, tl-informal, in MW core
+> 3) Creating a new interface language, tl-informal, in production
+
+Just these first three.  For now, we're very undecided on pursuing the fourth option, as we have not yet agreed on having Taglish content on the Tagalog Wikipedia.  For now, we only agreed on having a new interface language, and we will get to the issue of content languages when we get there.",1378878251,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+Creation of tl-informal as a new interface language,"Is this asking for:
+
+1) Creating a new interface language, tl-informal, in TranslateWiki.net
+2) Creating a new interface language, tl-informal, in MW core
+3) Creating a new interface language, tl-informal, in production
+4) Creating a new content language in MW core, adding to tlwiki as a variant
+5) Creating a new content language in MW core, adding to a new wiki (tl-inf-wiki)?
+
+I think this is 1, 2, 3 and 4 but not 5.
+
+Note that adding variants to a wiki is do-able but makes for a sucky experience in both editing and creating wikitext, and means that tlwiki wouldn't be possible as a release target for VisualEditor for at least some time whilst we wait for building out support in VisualEditor and Parsoid.",1378834373,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tn3a37o3zgibya4bkm32,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"**Author:** `swalling`
+
+**Description:**
+Hidden VE postedit confirmation
+
+If you edit successfully via wikitext, we delay loading the GettingStarted toolbar until after the post-edit confirmation disappears. We should do the same for the new style of postedit confirmation from VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11351}",1376715240,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-osskcs5pzqf76ce4lpyj,task_description,resolved
+GettingStarted toolbar overlaps with VE post edit confirmation,"Change 112880 merged by jenkins-bot:
+Delay showing the task toolbar after VisualEditor edit
+
+https://gerrit.wikimedia.org/r/112880",1392360585,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"Thanks, James.  The change on our side is https://gerrit.wikimedia.org/r/112880.",1392263311,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"The VE patch here has been merged and will be deployed in the train tomorrow (in wmf14); not sure if this achieves the fix desired, so just setting to ""NEW"" instead.",1392254220,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"Change 112880 had a related patch set uploaded by Phuedx:
+Delay showing the task toolbar after Visual Editor edit
+
+https://gerrit.wikimedia.org/r/112880",1392205844,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+GettingStarted toolbar overlaps with VE post edit confirmation,"Change 112879 had a related patch set uploaded by Phuedx:
+Include edit status in the ve.deactivationComplete event
+
+https://gerrit.wikimedia.org/r/112879",1392205631,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-osskcs5pzqf76ce4lpyj,task_subcomment,NA
+Refactor sanitizer to work on the DOM too,"Currently we always serialize to wikitext and re-parse that to HTML, which runs the sanitizer on the token stream to ensure that our final HTML does not cause bad things to happen.
+
+Soon both us and the Flow team want to store HTML from the VisualEditor directly without first serializing to wikitext. This means that we need to perform the sanitization on the HTML instead of the token stream. For performance, sanitizing on the way in would be preferable. We should however support re-sanitization when new issues were discovered. This could potentially be coupled with the versioning discussed in bug 52937. A new sanitizer could bump the version number, and the upgrade path would then run the new sanitizer on old HTML (and probably update the storage with the newly sanitized version).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1376677680,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-zls4w4oon3y5sp6y4rot,task_description,open
+Refactor sanitizer to work on the DOM too,"Note that tokens are equivalent to SAX events. This suggests the following option for hooking up the current sanitizer to process a DOM:
+
+- Traverse the input DOM, emit SAX events
+- feed SAX events through the sanitizer
+- feed the resulting tokens / SAX events back to a HTML / XML DOM tree builder",1498752154,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-zls4w4oon3y5sp6y4rot,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"**Author:** `swalling`
+
+**Description:**
+Screenshot at 1024x768
+
+Very happy to see that VE is now using the same post-edit styling as wikitext! This is a big win for usability, since it is fixed position and so on.
+
+I did find one suboptimal fact though... Since the text of the message includes the page title, it is very variable width, depending on the page title length and the browser width. 
+
+One of the UX goals for this notification is to have new users notice it, but for it to eventually fade out of your attention as you become used to it. Since the page title produces very different widths as you edit different pages, this calls a lot more attention to the notification even if you've edit thousands of times. 
+
+My recommendation would be to match what's in the wikitext version, ""Your edit was saved."" since we A/B tested it and we know it meets the goals I mentioned above. Another good solution is simply removing the page title, so that the VE version says, ""Your changes have been saved."" That seems functionally the same, though I think using edit is good for consistency with the tab names etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11185}",1376526420,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3fcobyguspmbsv62uzbp,task_description,resolved
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Change 130968 merged by jenkins-bot:
+Switch to use MediaWiki's built-in messages for post-edit notifications
+
+https://gerrit.wikimedia.org/r/130968",1398983834,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Change 130968 had a related patch set uploaded by Alex Monk:
+Switch to use MediaWiki's built-in messages for post-edit notifications
+
+https://gerrit.wikimedia.org/r/130968",1398977566,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Change 127480 merged by jenkins-bot:
+Expand core post edit functionality to match VE
+
+https://gerrit.wikimedia.org/r/127480",1398976145,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),Now just needs VE to use the same function.,1398975938,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Change 127480 had a related patch set uploaded by Alex Monk:
+Expand core post edit functionality to match VE
+
+https://gerrit.wikimedia.org/r/127480",1398011806,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases),"Current VE messages:
+
+    ""visualeditor-notification-created"": ""\""$1\"" has been created."",
+    ""visualeditor-notification-restored"": ""\""$1\"" has been restored."",
+    ""visualeditor-notification-saved"": ""Your changes to \""$1\"" have been saved."",
+
+Current MW core message:
+
+    'postedit-confirmation'            => 'Your edit was saved.',
+
+We should:
+
+1. Expand MW core to cater to all three states (create, restore, save):
+
+** Create: ""The page has been created.""
+** Restore: ""The page has been restored.""
+** Saved: ""Your edit was saved.""
+
+2. Not use different messages in VE – instead, use the core ones.
+
+Rather than create two bugs, let's just use this one?",1393377054,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3fcobyguspmbsv62uzbp,task_subcomment,NA
+VisualEditor: <references /> empty in edit mode,"The <references /> section is empty in edit mode, see URL.
+
+Other examples:
+
+https://de.wikipedia.org/wiki/Joachim_Wiesner
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Bahnhof_K%C3%B6ln_Eifeltor",1376480280,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-clul26iiuspnnu6ubobc,task_description,resolved
+VisualEditor: <references /> empty in edit mode,"Yeah, was already fixed. Great!",1378992675,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-clul26iiuspnnu6ubobc,task_subcomment,NA
+VisualEditor: <references /> empty in edit mode,"Hi Raimond,
+in both articles I can correctly see the contents of the Einzelnachweise sections.
+(Maybe this is a duplicate and the bug was already fixed?)",1378988604,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-clul26iiuspnnu6ubobc,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-searchoptions
+
+The ""Advanced options"" section of the ""Search"" tab in MediaWiki currently looks like this:
+
+---
+Advanced options
+
+[ ] Search in all namespaces
+
+Search in these namespaces by default:
+[ ] (Main)
+[ ] Talk
+[ ] User
+[ ] User talk
+[ ] Project
+[ ] Project talk
+[ ] File
+[ ] File talk
+[ ] MediaWiki
+[ ] MediaWiki talk
+[ ] Template
+[ ] Template talk
+[ ] Help
+[ ] Help talk
+[ ] Category
+[ ] Category talk
+[ ] Thread
+[ ] Thread talk
+[ ] Summary
+[ ] Summary talk
+[ ] Manual
+[ ] Manual talk
+[ ] Extension
+[ ] Extension talk
+[ ] API
+[ ] API talk
+[ ] Skin
+[ ] Skin talk
+[ ] Module
+[ ] Module talk
+[ ] Translations
+[ ] Translations talk
+[ ] VisualEditor
+[ ] VisualEditor talk
+---
+
+This list looks silly and excessive. While {T39878} has requested a layout change, I think we need to reconsider how this list is implemented.
+
+What about adding a checkbox to [[Special:Search]]'s advanced search section that looks something like this:
+
+[ ] Use these namespaces as my default
+
+This would de-duplicate the namespace listing (between Special:Preferences and Special:Search) and would allow the search user preference to be set more easily from the search interface itself.
+
+Rather than using Special:Preferences and having heavy user interface exposure, any custom search namespace preferences could be ""hidden"" user preferences. That is, they'll still be stored if they don't match the site-wide default, but they'll not clutter up Special:Preferences.
+
+--------------------------
+**See Also**:
+{T50615}",1376420940,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ueuakppu4zprla5jwywo,task_description,resolved
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Change 250271 merged by jenkins-bot:
+Remove search preferences from Special:Preferences JavaScript
+
+[[https://gerrit.wikimedia.org/r/250271]]",1446331757,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Change 250271 had a related patch set uploaded (by saper):
+Remove search preferences from Special:Preferences JavaScript
+
+[[https://gerrit.wikimedia.org/r/250271]]
+",1446322753,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Not really. As far as I understand the current search options are handled perfectly by the  [[http://git.wikimedia.org/blob/mediawiki%2Fcore.git/0158312d4bc3de9c15064a12a73b4bf57580e45e/resources%2Fsrc%2Fmediawiki.special%2Fmediawiki.special.search.js|mediawiki.special.search.js]] ResourceLoader module, while I intend to remove this from [[http://git.wikimedia.org/blob/mediawiki%2Fcore.git/0158312d4bc3de9c15064a12a73b4bf57580e45e/resources%2Fsrc%2Fmediawiki.special%2Fmediawiki.special.preferences.js#L284|mediawiki.special.preferences.js]] in https://gerrit.wikimedia.org/r/#/c/247728/. Probably this is just a leftover from this change.",1445517570,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","> I have found that we still have JavaScript code attaching to #mw-htmlform-advancedsearchoptions and #mw-input-wpsearcheverything. I understand this can be safely removed?
+
+Do you mean the All | None buttons inserted via JavaScript?",1445449896,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","One question:
+
+In https://gerrit.wikimedia.org/r/#/c/247728 I have found that we still have JavaScript code attaching to 
+`#mw-htmlform-advancedsearchoptions` and `#mw-input-wpsearcheverything`. I understand this can be safely removed?
+
+",1445420606,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",,1445420618,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",,1445420596,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Isarra from comment #27)
+> May also want a separate page of 'all settings' or 'advanced settings' for a
+> lot of them (it could also appear collapsed or something by default - the
+> point is while this is often not the stuff folks will necessarily be after,
+> it should be there somewhere in case they are), sort of like the extra
+> 'config' heap you see in firefox and whatnot, but hopefully somewhat easier
+> to find and use.
+
+Is there an open bug report about this? I wouldn't oppose a gated (behind a checkbox, perhaps) advanced user preferences tab. Safari does this as well, I believe, with a preferences checkbox that enables a ""Developer"" drop-down menu. Similar-ish idea.",1402265111,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Created attachment 15597
+Advanced search tab in mediawiki.org as of  	1.24wmf8
+
+**Attached**: {F11964}",1402261771,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #52)
+> My complaint has ""never"" been about any checkbox, but the removal of
+> Preferences.
+
+Are you able to offer another tab of Special:Preferences and other 35 checkboxes (in the case of en.wiki) to sacrifice instead?
+Preferences have been in a process of cutting for some time now and there are some rather extreme proposals around where your time would perhaps be better spent: https://www.mediawiki.org/wiki/Requests_for_comment/Redesign_user_preferences
+
+The path I'm following is the one of least resistance for the biggest result, you'll see that I'm reducing your future pain. :)",1402261544,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","My complaint has ""never"" been about any checkbox, but the removal of Preferences.",1402252214,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",So much drama about a single checkbox… get me out of here.,1402251490,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","No, I won't sit down, shut up and enjoy the ride.
+
+Really, most other places require consensus and consultation for change. I believe that Erik himself said that in edits relating to Flow. Something along the lines of 
+
+<quote>... We do strive to communicate, solve problems real users have, and resolve conflicts, especially if there are major points of contention. What are the material issues with the deploy at this time?</quote>
+
+So you have
+* major points of contention
+* no evidence that this fix actually a major point of contention
+* communication in a newsletter that points here, but you are not prepared to listen or discuss
+* no attempt to resolve a conflict
+* a merged change that is predicted to take place where no consultation has taken place
+* an opportunity to address matters raised prior to a deployment
+
+Have I missed something from that little list?
+
+Seems more than a technical fix. It appears to be a change planned to be implemented and you are not allowing broader discussion, or the base challenge to your assumptions. The points have been raised, and yet you forge ahead with your decision without an attempt at consensus, or some conciliation. And the history of bugs is that they are discussed in situ, not fobbed off somewhere else where you can ignore them in all their glory.
+
+I would think that it would actually be incumbent on you, those bringing the change forward to mediawiki, to propose and discuss that merged change. But no, instead we hide behind the ""technical"" barrier. Then expect others to go somewhere and complain ""I don't like it."" Grow up. The mature adult thing is for me to bring concerns here, to have them reasonably listened to, and to see if we can have a compromise. Seems that the mature approach is not suitable.
+
+If you want that change, you take it out and propose it and defend it. You have identified where it should be discussed, so I look forward to seeing it there. That is basically what I said at the beginning.
+
+If I don't see it there, then I feel that I am justified in reopening this bug until there is what I consider some reasonable conversation about this bug, and means to explore the matters raised.",1402251279,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #48)
+
+This bug is technically fixed: Advanced options preferences are now handled on Special:Search itself, which is the topic of this bug, so please stop reopening it. Also, a ""resolved"" status doesn't prevent you from commenting. If you detect flaws on the implementation, feel free to open a *new* bug describing the problems of this implementation (see [1]).
+
+I'd suggest you to raise your concerns in a mailing list (mediawiki-l seems to be the the best one for your concerns) [2]. Your message will be received by more people that can share their point of view about this, while your messages on this bug report are being received by the same developers that were involved in it. Feel free to put here a link to the discussion on the mailing list if you decide to start a discussion there.
+
+----
+
+[1] https://www.mediawiki.org/wiki/How_to_report_a_bug
+[2] https://www.mediawiki.org/wiki/Mailing_lists",1402249236,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I am sorry, that is a typical dismissive response, and pretty unhelpful.  I don't see the issues raised addresses by the bugzilla.
+
+BTW no one made you the decision maker, and as it is your code I would think a little less CoI, and some more communication would be preferable.",1402245055,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Quiddity from comment #40)
+> I think the problem with the new version, is the physical distance, or
+> dis-connection, of the checkbox from the search button... 
+
+Split to bug 66342.
+
+(In reply to billinghurst from comment #46)
+> I am wondering whether the proponents of the change have had the ability to
+> review suggestions
+
+Yes.",1402240628,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I am wondering whether the proponents of the change have had the ability to review suggestions made by people who are not in favour of the holistic change and may be able to suggest a compromise position.
+
+I have reopened this bug as I do not think that it should be considered fixed in light of this extra opinion.",1402239071,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+(In reply to MZMcBride from comment #43)
+
+> My gut feeling is that the real, underlying issue here is that you, me, and
+> others want global (wikifarm-wide) user preferences. 
+
+Speaking only for myself, I usually modify my search based on my involvement with the specific wiki. My search on a project I'm involved with and editing regularly usually needs the project and often the user namespaces. Ones I'm only occasionally editing need help and project namespaces. The defaults work fine on projects where I'm only a reader. It is a workflow issue.",1401810675,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+> It was 50/50 that you were going to say that. The other option was ""if it ain't > broke don't fix it"". Both are useless clichés. 
+
+Mmm, actually the third option was ""change for the sake of change"". They are clichés because they are common, valid issues. And you have not addressed the substance of the comment.
+
+I would suggest your response - highly defensive and dismissive - is itself a cliché of ""Dev knows best"", except I also know the reason it's a cliché is because it's often true. I'm with Quiddity, Isarra, and sDrewth: let's figure out a both-and solution, because it does not need to be either-or.",1401808846,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #37)
+> Nobody has argued about sensible defaults, nor the ability for communities
+> to be able to adjust and modify. I don't see how that introduction is
+> relevant.
+
+Amgine asked, ""Do we really want every special page to be creating and maintaining its own interface for user preferences?"" I was responding by noting that the goal is having a clean, easy-to-use user interface that uses sensible defaults. The goal is not a foolish consistency.
+
+> In fact if you follow that logic, we are now cluttering up a search page
+> with an option that is going to be used rarely or not at all, and maybe by a
+> small subset of people ...  Making visible an option that is probably used
+> zero times by most user, and maybe once or two by a small number of users.
+> That is perverse.
+
+Well, not quite. :-)  Rather than having this feature (the ability to customize search preferences) take up an entire Special:Preferences tab, it's now confined to a single checkbox. This seems proportionate and reasonable to me. If the feature were more important, it might make sense to give it more prominence, but I (personally) don't think it's very important.
+
+> I have no specific issue with an improvement or option at Special:Search, my
+> issue is that Preferences = Preferences and I expect to be able to go there
+> and to be able to set my preferences for search.
+
+My gut feeling is that the real, underlying issue here is that you, me, and others want global (wikifarm-wide) user preferences. In a similar vein to what I wrote in comment 35, as a user, if you're visiting Special:Preferences often, we're doing something wrong. You should only need to visit that page maybe once a year, but it sounds as though you and a few others visit it weekly or daily. (Which is not a criticism of power-users, to be clear, just a workflow observation.) I think we should focus on figuring out how to make it so that (power-)users don't need to visit Special:Preferences on every wiki in a wikifarm.",1401800527,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Quiddity from bug 52817 comment #40)
+> Searching for help documentation is HELL unless we add the Wikipedia: ,
+> Help: , and Template: namespaces to our default search. For the first few
+> years as a new editor, I was constantly searching those namespaces for tools
+> and guides. (Note that the Template: and Category: namespaces aren't
+> included in the ""Help and Project pages"" output)
+
+I guess this is an answer to:
+
+(In reply to MZMcBride from bug 52817 comment #35)
+> If many users are customizing their search settings, we're doing something
+> wrong.
+
+Split to bug 66066.",1401788398,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Quiddity from comment #40)
+> I'm surprised that we don't already have a link to
+> [[Special:Preferences#mw-prefsection-searchoptions]] anywhere at
+> [[Special:Search]] (advanced tab or otherwise)! How did we miss that, for so
+> long?!  Forest, trees.
+
+That's a very good point, and I've just made it happen on en.wp.",1401787806,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I fall right in the middle of this disagreement. Here's some notes, and an idea.
+
+There are good reasons to have the search-option-preferences in both locations (eg. easier-discoverability for newcomers, familiarity for oldtimers), 
+and there are good reasons to centralize/unduplicate at a single location (with Special:Search->Advanced being the reasonable contender because the options-list *has* to appear there).
+
+We do need easy-discoverability for newcomers. 
+Searching for help documentation is HELL unless we add the Wikipedia: , Help: , and Template: namespaces to our default search. For the first few years as a new editor, I was constantly searching those namespaces for tools and guides. (Note that the Template: and Category: namespaces aren't included in the ""Help and Project pages"" output)
+
+I'm surprised that we don't already have a link to [[Special:Preferences#mw-prefsection-searchoptions]] anywhere at [[Special:Search]] (advanced tab or otherwise)! How did we miss that, for so long?!  Forest, trees.
+
+I do also prefer the simple process for ""Save"" at Special:Preferences. It's not perfect (see {T57966}), but it's fairly intuitive. 
+The new system isn't intuitive. (It makes sense once explained, but an explanation is needed...)
+I think the problem with the new version, is the physical distance, or dis-connection, of the checkbox from the search button... 
+
+
+So, 2 fuzzy/rough suggestions:
+
+A) Add a new Blue ""Save selection as my default, and Search"" button, at the advanced-search tab, instead of the new ""Remember selection for future searches"" checkbox line. 
+
+B) leave the ""Search"" tab at Special:Preferences, but 
+B.1) just link to Special:Search->Advanced from within it.   
+B.2) Or, when clicked, have it open Special:Search->Advanced in a new tab/window.   (New tab, because the user might have other unsaved preference-changes, so we can't change the current page. (cf. {T57966}))  
+Either of these would solve the issues of discoverability and change-aversion.  Yes, it'll still leave an annoyingly almost-empty tab, but it's *way* better than the current/old layout, ie. comment #0
+
+--
+
+All 4 links, for your quick comparison:
+https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-searchoptions
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced",1448489786,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I fall right in the middle of this disagreement. Here's some notes, and an idea.
+
+There are good reasons to have the search-option-preferences in both locations (eg. easier-discoverability for newcomers, familiarity for oldtimers), 
+and there are good reasons to centralize/unduplicate at a single location (with Special:Search->Advanced being the reasonable contender because the options-list *has* to appear there).
+
+We do need easy-discoverability for newcomers. 
+Searching for help documentation is HELL unless we add the Wikipedia: , Help: , and Template: namespaces to our default search. For the first few years as a new editor, I was constantly searching those namespaces for tools and guides. (Note that the Template: and Category: namespaces aren't included in the ""Help and Project pages"" output)
+
+I'm surprised that we don't already have a link to [[Special:Preferences#mw-prefsection-searchoptions]] anywhere at [[Special:Search]] (advanced tab or otherwise)! How did we miss that, for so long?!  Forest, trees.
+
+I do also prefer the simple process for ""Save"" at Special:Preferences. It's not perfect (see bug 55966), but it's fairly intuitive. 
+The new system isn't intuitive. (It makes sense once explained, but an explanation is needed...)
+I think the problem with the new version, is the physical distance, or dis-connection, of the checkbox from the search button... 
+
+
+So, 2 fuzzy/rough suggestions:
+
+A) Add a new Blue ""Save selection as my default, and Search"" button, at the advanced-search tab, instead of the new ""Remember selection for future searches"" checkbox line. 
+
+B) leave the ""Search"" tab at Special:Preferences, but 
+B.1) just link to Special:Search->Advanced from within it.   
+B.2) Or, when clicked, have it open Special:Search->Advanced in a new tab/window.   (New tab, because the user might have other unsaved preference-changes, so we can't change the current page. (cf. bug 55966))  
+Either of these would solve the issues of discoverability and change-aversion.  Yes, it'll still leave an annoyingly almost-empty tab, but it's *way* better than the current/old layout, ie. comment #0
+
+--
+
+All 4 links, for your quick comparison:
+https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-searchoptions
+https://en.wikipedia.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Special:Search&search=&fulltext=Search&profile=advanced",1401786703,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Amgine from comment #36)
+> This sounds so much like a solution looking for a problem.
+
+It was 50/50 that you were going to say that. The other option was ""if it ain't broke don't fix it"". Both are useless clichés. 
+
+Your comments are dripping with ""me, me, me"" privilege-based assumptions. Luckily, MediaWiki development is not based around avoiding advanced users having to have the minor inconvenience of learning a small interface change.",1401783456,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #37)
+> my
+> issue is that Preferences = Preferences
+
+Too bad this assumption is incorrect. We have plenty of preferences which have never been controlled by Special:Preferences, look https://www.mediawiki.org/w/api.php?action=query&meta=userinfo&uiprop=options&format=jsonfm again.
+Not to speak of all the preferences which are not even stored in the database, but instead on cookies or URL parameters (hence bookmarks at best).",1401778605,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to MZMcBride from comment #35)
+> (In reply to Amgine from comment #21)
+> > Sucks as UX. Do we really want every special page to be creating and
+> > maintaining its own interface for user preferences?
+> 
+> We want sensible defaults and intuitive, easy-to-use interfaces. For most
+> users, there shouldn't be a need to customize the default search settings.
+> If many users are customizing their search settings, we're doing something
+> wrong. For the few users who want to customize their search preferences,
+> there's now a checkbox in the same place as search. This seems like a good
+> thing to me.
+
+Nobody has argued about sensible defaults, nor the ability for communities to be able to adjust and modify. I don't see how that introduction is relevant.
+ 
+> Because there's now an additional checkbox that controls per-user search
+> preferences, we can de-duplicate the listing at Special:Preferences, which
+> makes for a cleaner user preferences interface (increased signal, decreased
+> noise). This also seems like a good thing to me.
+
+In fact if you follow that logic, we are now cluttering up a search page with an option that is going to be used rarely or not at all, and maybe by a small subset of people ...  Making visible an option that is probably used zero times by most user, and maybe once or two by a small number of users. That is perverse.
+
+> Perhaps a pointer from Special:Preferences to Special:Search would be
+> helpful, but I'm not sure it's needed and I'm not sure where it would
+> appropriately go.
+
+Or it could be '''at''' the search page that it says something the lines of ""Save this criteria to be your default"" and have a link to Special:Preferences.
+
+I have no specific issue with an improvement or option at Special:Search, my issue is that Preferences = Preferences and I expect to be able to go there and to be able to set my preferences for search.",1401778330,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+Would those 'few users' happen to be the experienced wikimedians (like those who have piped up here)? the ones who know (well, knew) where to modify their user preferences?
+
+This sounds so much like a solution looking for a problem.",1401772870,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Amgine from comment #21)
+> Sucks as UX. Do we really want every special page to be creating and
+> maintaining its own interface for user preferences?
+
+We want sensible defaults and intuitive, easy-to-use interfaces. For most users, there shouldn't be a need to customize the default search settings. If many users are customizing their search settings, we're doing something wrong. For the few users who want to customize their search preferences, there's now a checkbox in the same place as search. This seems like a good thing to me.
+
+Because there's now an additional checkbox that controls per-user search preferences, we can de-duplicate the listing at Special:Preferences, which makes for a cleaner user preferences interface (increased signal, decreased noise). This also seems like a good thing to me.
+
+Perhaps a pointer from Special:Preferences to Special:Search would be helpful, but I'm not sure it's needed and I'm not sure where it would appropriately go.",1401766548,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+Ah, but then how simple it is to alter the settings is also out of scope.
+
+My opinion is the people most familiar with the software are those most likely to wish to modify their search preferences. For those users, their user preferences are the most-likely first place to look to alter their user preferences. That would meet most 'least surprise' requirements. Being able to alter the search prefs elsewhere, as Isarra says, would be very cool. Being unable to set the search prefs via the least surprising interface would, in my opinion, not be cool.",1401732710,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",How well those features work is a valid question but it's out of scope for this discussion.,1401732312,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+(In reply to Scott Martin from comment #31)
+> (In reply to Scott Martin from comment #28)
+> > To get to Special:Search you click the magnifying glass
+> > icon in the search box.
+> 
+> Or search for nothing. Sorry for two posts in rapid succession, remembered
+> that a moment too late. (And also had the thought that maybe the magnifying
+> glass thing is a skin-specific feature.)
+
+Cool! and of course you have evidence that people just do this, intuitively.",1401731393,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Scott Martin from comment #28)
+> To get to Special:Search you click the magnifying glass
+> icon in the search box.
+
+Or search for nothing. Sorry for two posts in rapid succession, remembered that a moment too late. (And also had the thought that maybe the magnifying glass thing is a skin-specific feature.)",1401727475,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Nemo from comment #29)
+> (In reply to Isarra from comment #27)
+> > Ideally we'd have some way to automatically dump settings that appear in the
+> > interface elsewhere into main preferences just by telling it 'OY LOOK A
+> > SETTING'.
+> 
+> That's exactly what we did.
+> 
+> > 
+> > May also want a separate page of 'all settings' or 'advanced settings'
+> 
+> We have it:
+> https://www.mediawiki.org/w/api.
+> php?action=query&meta=userinfo&uiprop=options&format=jsonfm
+
+Oh, neat! Very nice.",1401727366,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Isarra from comment #27)
+> Ideally we'd have some way to automatically dump settings that appear in the
+> interface elsewhere into main preferences just by telling it 'OY LOOK A
+> SETTING'.
+
+That's exactly what we did.
+
+> 
+> May also want a separate page of 'all settings' or 'advanced settings'
+
+We have it: https://www.mediawiki.org/w/api.php?action=query&meta=userinfo&uiprop=options&format=jsonfm",1401727218,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Amgine from comment #26)
+> The suggested model is not as simple as Scott Martin describes it. 
+
+Actually, it is. To get to Special:Search you click the magnifying glass icon in the search box.",1401727194,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Ideally we'd have some way to automatically dump settings that appear in the interface elsewhere into main preferences just by telling it 'OY LOOK A SETTING'.
+
+May also want a separate page of 'all settings' or 'advanced settings' for a lot of them (it could also appear collapsed or something by default - the point is while this is often not the stuff folks will necessarily be after, it should be there somewhere in case they are), sort of like the extra 'config' heap you see in firefox and whatnot, but hopefully somewhat easier to find and use.",1401726928,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+@Isarra
+
+So you are saying ""both-and"", not ""eliminate one""? This would probably result in duplication of code and maintenance (which is one of my arguments against moving the preferences in the first place.)
+
+The suggested model is not as simple as Scott Martin describes it. Although setting the preference is top menu -> special: preferences -> tab, this is simpler than tools menu -> special:specialpages -> search -> settings because search is not readily found in the special:specialpages page. Yes, *if one has already done a search* you are already on the page, but if you have not, you aren't. I just attempted to land on search from the search box: foo, qux, and quux are redirs, foobar is an article, baz and asdf are disambigs, and foobaz gets me to search.",1401726027,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I guess there are two things here.
+
+1: Users will primarily care about preferences affecting a specific page when on that specific page. They will be able to most effectively see the effects when on that page, too, so giving them the option to save what works when they're there, seeing that it works, is generally quite useful.
+
+2: Users do tend to expect to find preferences in preferences. A common practice, especially for users who have used the software before but are on a new project, is to go through all of them and quickly configure things how they like them, or think they will. Alternately, if they want to go back and disable something after it behaves weirdly, or if another user tells them to change a setting, the preferences are a likely place to go for that.
+
+Yes.",1401722233,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","I don't understand how clicking into Special:Preferences and then a subpage to set options for Special:SomePage is substantially less complicated than going to Special:SomePage and setting them there the first time you use it. Given that most changes to search options will be made on the fly during search experiences, requiring users to leave the special page, go into preferences and then come back (or change preferences in a new tab then reload the search) is a degradation of the UX.
+
+> Preferences are preferences, please keep them together not scattered around the wiki.
+
+""The wiki"" is a misunderstanding here. ""Preferences"" are operational modes for programs, and the special pages are a collection of small utility programs accompanying the core. There's no objective reason why their mode controls should be grouped together remotely with the core's. It's like having the windscreen wiper speed control as a switch on the engine instead of on the dashboard; old-school advanced users of that peculiarly-designed car may be fine with opening the hood to change it because ""it's always been there"", but that doesn't make doing it easy for everyone. A new car would seem particularly old-fashioned if it were still designed this way, and we should be trying to ensure that MediaWiki lives up to the interface design expectations of modern software.
+
+> Please produce the evidence base for this change.
+
+Pretty much every UX study ever that's shown that the further away you put a control from what it affects, the harder users find it to interact with, or even find in the first place - especially new users. It's the GUI-side version of [[Action at a distance (computer programming)]].
+
+S (speaking only for myself, I'm not a MediaWiki developer)",1401721927,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Clutter is removing unnecessary items, redundant items, messy items; clutter is not (re)moving a useful and considered page. So since when is a preference page like Search preference considered clutter? It is clear and specific.  Preferences are preferences, please keep them together not scattered around the wiki.
+
+My attitude is not about any other item, please don't presume.
+
+When I am setting up my preferences for a wiki it is very easy to go into preferences and change the settings that I want. Now you are going to make someone go to the search page to do it, off via other links. That is not more helpful.
+
+If the issue that we give (too) much choice to users, and they are confronted about tabs, then produce a simple and an advanced choice plan. Please produce the evidence base for this change.
+
+To the ""maybe I missed ..."". Have you missed the meaning of the word ""consultation"" and maybe seeking a broader opinion? 
+
+That it is considered that bugzilla is a suitable place for working out a social solution is less than ideal, and yet it happens repeatedly. That a few didn't think it is worthwhile consulting with the broader community about this is disappointing.",1401720133,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to billinghurst from comment #20)
+> It is disappointing that a cabal effect has
+> taken place to what is a significant change to how things are done around
+> here.
+
+I'm sorry you see it that way; I suspect your attitude about this bug is affected by an unrelated change which got merged and reverted in these days after a MediaWiki RfC with a very obscure title. This is nothing like that. 
+
+Maybe you missed something: https://bugzilla.wikimedia.org/showdependencygraph.cgi?id=62559&display=tree&rankdir=LR
+If you did it's not your fault, implementation details discussed in each bug (like this) are just that, details; but it's safe to state that since some time ago there is wide consensus, and a strong push, towards reducing the clutter in MediaWiki by reducing interface complexity in general and Special:Preferences options specifically.",1401718043,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","**wmf.amgine3691** wrote:
+
+Sucks as UX. Do we really want every special page to be creating and maintaining its own interface for user preferences?",1401717246,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Really? Preferences are preferences and have belonged in ... umm ... ""Preferences"". Shouldn't such a change have had a wider discussion than between eight and eleven people? Maybe it could have been trialled, and checked through the UI processes. Maybe have used the beta features for testing?
+
+This seems a significant change that really could have had better rigour put to it for an implementation. It is disappointing that a cabal effect has taken place to what is a significant change to how things are done around here.",1401716325,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","There's a very similar move of preferences to page proposed at Bug 48615, for Special:Watchlist. As this change has met approval, it would be great if that bug could see movement - not least because this change will now cause a preference location inconsistency, if you see what I mean.",1401713735,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Bohdan from comment #16)
+> Also why to do a small change on specific WMF wiki's config it's community
+> must hold 1 weeks discussion but a change concerning to all MediaWiki wikis
+> it being done with no discussion at all?
+
+How is the long comment thread above, and the even longer review list on the change itself, ""no discussion at all""? There was discussion, you just didn't participate.
+
+Config changes are not handled by any of the people who were involved in this, except maybe occasionally. Ask the people who handle them about why they have their requirements.",1401661235,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Bohdan from comment #15)
+> Why on Earth I must run through lots of pages to set personal configuration
+
+Lots? As far as I know Special:Preferences contains options for about 3 special pages. It's also less common for users to set preferences for Special:Search without ever having visited it: so the action of tweaking preferences will happen in a visit to Special:Search which would have happened anyway, and the total number of special pages visited should be lower (because it's not necessary to switch to Special:Preferences to save the search options you just selected).",1401653038,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",Also why to do a small change on specific WMF wiki's config it's community must hold 1 weeks discussion but a change concerning to all MediaWiki wikis it being done with no discussion at all?,1401651920,PHID-USER-sscimmfqgfuh4pe2kfyw,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",Why on Earth I must run through lots of pages to set personal configuration for myself on a wiki? I think the best is to keep both central place for changing config in preferences and page specific on appropriate pages.,1401651761,PHID-USER-sscimmfqgfuh4pe2kfyw,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Thanks for all the help, Chad and Bartosz.
+Let's get bug 31881 fixed in 1.24. :)",1401513089,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Change 131727 merged by jenkins-bot:
+Save advanced search namespace prefs on Special:Search itself
+
+https://gerrit.wikimedia.org/r/131727",1401486201,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Well, exact colouring is debatable, however we still have to consider colour-blind and blind users. Thus I believe that colour-highlighting is not a good idea.",1401292566,PHID-USER-37d2msujvpp2rippbzoq,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #9)
+and
+(In reply to Nemo from comment #10)
+
+Use Colored-highlights, and a Legend, for 
+* These options are the site-defaults
+* These options are your customized defaults
+* These options are selected for just-this-search.
+
+This will also solve the ""what were the defaults? I (might) want to reset!"" issue.
+
+My ugly mockup/napkin-sketches, from an unrelated topic, just to inspire further thinking: 
+https://i.imgur.com/IcEWCzF.png
+https://i.imgur.com/tOJOsXG.png",1401232148,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","The behaviour is similar to what happens with the login checkbox, I can't imagine it being so confusing. Only few users very used to the wiki will set their preferred namespaces before their first search.
+
+We can grey out the checkbox when the selection wasn't changed, but that can be done on a separate patch IMHO; a visual confirmation is provided by the checkboxes themselves, which are preserved the next time.",1399498482,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","The idea is good. Now that I see the implementation, it implies you have to perform the search *after* marking that checkbox for it to be saved in your preferences.
+
+Don't get me wrong, I'd also think that you have to mark the checkbox before performing the search, but people not so familiar with web forms may find it not too obvious.
+
+A possible solution to this that I'm thinking of: add a button that on click would change the preferences using an AJAX call, with a visual feedback of the settings being saved.
+
+Also, a checkbox may look weird if you mark it, and after performing the search it remains unchecked (did I checked it when performing the search? or was it totally ignored?).",1399497275,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Created attachment 15314
+Current appearance of the feature
+
+Screenshot of the feature as currently coded. It's just one more checkbox next to a few dozens: the HTML needs to be improved a bit but it's really straightforward from an interface perspective.
+
+//attachment Bug52817.png ignored as obsolete//",1399474582,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Change 131727 had a related patch set uploaded by Nemo bis:
+[WIP] Save advanced search namespace prefs on Special:Search itself
+
+https://gerrit.wikimedia.org/r/131727",1399394092,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","You'll want to use 'type' => 'api' (which is, admittedly, somewhat misleadingly named). One core preference using this is 'watchlisttoken'.",1399319859,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","[[mw:Manual:Preferences]] and [[mw:Manual:Hooks/GetPreferences]] are not particularly helpful. To hide preferences from Special:Preferences, should they be made of ""hidden"" type? Added to $saveBlacklist? Spinned off from Preferences.php completely?",1399304670,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","Are we still collecting (re)thoughts or is this bug focused on a specific change? Seems the latter, changing subject.",1390658642,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",*** Bug 37878 has been marked as a duplicate of this bug. ***,1390582522,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself","(In reply to comment #1)
+> I really really like this idea.
+
+Should we set this ticket as for something we'd like to have in the next release (1.22) then?",1376595939,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Handle ""Search"" --> ""Advanced options"" section of Special:Preferences on Special:Search itself",I really really like this idea.,1376589869,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-ueuakppu4zprla5jwywo,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","The ""Enable section editing via [edit] links"" user preference should be removed from MediaWiki core.
+
+Users interested in hiding section-edit links can use per-user (or site-wide) CSS.
+
+This should be an easy bug to resolve; marking it with the Bugzilla keyword
+accordingly.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1376416020,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cttzml5ohhludlqqeslk,task_description,resolved
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","**troyengel** wrote:
+
+Got it -- I had to add !important, so this works:
+
+  .mw-editsection { display:none!important; }
+
+I'll get the wiki page updated with the new method, thanks!",1404052977,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to TE from comment #16)
+> Can one of y'all please post exactly what needs to go where to disable
+> site-wide this feature for anonymous, new and previous (logged in) users so
+> that this change removing the feature can be put back into CSS?
+
+You can try adding the following code to the page ""MediaWiki:Common.css"" on your wiki (untested, but should work...):
+
+.mw-editsection { display: none; }",1404052704,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","**troyengel** wrote:
+
+I'm not a MediaWiki guru to be able to figure this out, but with the 1.23 release I can't figure out how to disable this again. It's referenced above:
+
+""Users interested in hiding section-edit links can use per-user (or site-wide) CSS.""
+
+Great, but can someone update documentation on exactly *how* to do this? In my LocalSettings.php I have the old setting which is apparently ignored now:
+
+  $wgDefaultUserOptions ['editsection'] = false;
+
+I've dumped the DB and grepped and find only one reference to 'noeditsection' in the data, and my user account still shows the [Edit] on sections. The wiki indicates nothing about this change yet:
+
+  http://www.mediawiki.org/wiki/Manual:$wgDefaultUserOptions
+
+Can one of y'all please post exactly what needs to go where to disable site-wide this feature for anonymous, new and previous (logged in) users so that this change removing the feature can be put back into CSS?
+
+I'd be happy to update the above wiki page if someone just tells me *how* to go about it as a low-speed wiki operator who doesn't live & breathe this code. Thanks!",1404051842,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to Danny B. from comment #14)
+> Described in the last line of comment #11.
+
+The last line of comment 11 is:
+> And gadgets are what? Saved in preferences. Hence we are where we were.
+
+Sure, but most users and most wikis don't want or need an extra user preference for this. These links are automatically shown based on user permission and they're able to be hidden on a site-wide basis, on a per-page basis, and on a per-user basis. I don't see a need for a user preference here. What's the use-case, exactly? Why would a user want to hide these links for only their account?
+
+Regarding gadgets specifically, a few wikis might create such a gadget, but I doubt it. The overall MediaWiki experience (including that of most Wikimedia wikis) will have less clutter. This seems like a win to me.
+
+>> Out of curiosity, has this happened anywhere?
+> 
+> Yes.
+
+Where? Links welcome. :-)",1392773594,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to MZMcBride from comment #13)
+> (In reply to Danny B. from comment #11)
+> > This is nonsense. It should not have been removed.
+> 
+> Why's that?
+
+Described in the last line of comment #11.
+
+> > So there will be gadget created on sites to enable hiding.
+> 
+> Out of curiosity, has this happened anywhere?
+
+Yes.",1392772887,PHID-USER-xqqqgn2dels45flxw5kb,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to Danny B. from comment #11)
+> This is nonsense. It should not have been removed.
+
+Why's that?
+
+> So there will be gadget created on sites to enable hiding.
+
+Out of curiosity, has this happened anywhere?",1392690275,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","See comment 0 and comment 5 for reasoning, plus this request (""Remove ... user preference"") is obviously FIXED as the code commit has been merged. :)
+
+I don't think this specific bug report is the place for a generic ""I want less popular ancient options to be removed from the user preferences to reduce UI clutter"" vs. ""I want less people to have to edit their custom CSS or write Gadgets to do X"" discussion - should maybe happen on mediawiki-l instead if there is interest.
+
+However I agree that statistics on how many users have enabled such a setting might be helpful for future evaluation when killing some preferences.",1391604424,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","This is nonsense. It should not have been removed.
+
+comment #0 says: ""Users interested in hiding section-edit links can use per-user (or site-wide) CSS.""
+
+Exactly.
+
+So there will be gadget created on sites to enable hiding. (because Jorm is totally true with 'Can we just agree from this day forward that ""put it in your user css"" is not an acceptable solution for any problem, ever?'
+
+And gadgets are what? Saved in preferences. Hence we are where we were.",1391543815,PHID-USER-xqqqgn2dels45flxw5kb,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 99171 merged by jenkins-bot:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+https://gerrit.wikimedia.org/r/99171",1390589269,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 108673 abandoned by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+Reason:
+Abandoned: Original patchset at :
+https://gerrit.wikimedia.org/r/#/c/99171/
+
+https://gerrit.wikimedia.org/r/108673",1390587668,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 99171 restored by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+Reason:
+Errors in Rebasing. 
+Restoring for further tests..
+
+https://gerrit.wikimedia.org/r/99171",1390376736,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 108673 had a related patch set uploaded by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+https://gerrit.wikimedia.org/r/108673",1390310439,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 99171 abandoned by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from preferences
+
+Reason:
+Rebase errors persistant :(
+
+https://gerrit.wikimedia.org/r/99171",1390310410,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Brian's caution (asking some up to date stats) makes sense, however it should be noted that AFAIK this preference is mainly a relic of the ancient past when section editing was the last new thing. :) Maybe we'll need this preference again if VisualEditor ever finds some magic to allow section editing again. :P",1386970419,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","(In reply to comment #3)
+> Maybe the relevant code form the parser itself can also be removed?
+
+I'm not sure what you mean here.",1386225166,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Just for the record:
+
+<jorm> Can we just agree from this day forward that ""put it in your user css"" is not an acceptable solution for any problem, ever?
+
+From https://bugzilla.wikimedia.org/quips.cgi?action=show
+
+Maybe the relevant code form the parser itself can also be removed?",1386186606,PHID-USER-a6jwrurphpx6yl4coupk,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core","Change 99171 had a related patch set uploaded by 01tonythomas:
+Removed ""Enable section editing via [edit] links"" from Mediawiki Preference.
+
+https://gerrit.wikimedia.org/r/99171",1386179478,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+"Remove ""Enable section editing via [edit] links"" user preference from MediaWiki core",I would like to prepare a patch for this bug. Please assign it to me.,1386178444,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-cttzml5ohhludlqqeslk,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"A user asks if VE shouldn't now get rid of apostrophes used for formatting and use common tags instead <b>, <i>...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376398800,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-bgfttfnluju4mvokk3ud,task_description,resolved
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"Closing this as a duplicate to avoid confusion.
+
+*** This bug has been marked as a duplicate of bug 49143 ***",1380661120,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"Supporting HTML storage is indeed one of our goals for this fiscal year, and an important part of our long-term strategy. We plan to store both HTML and wikitext (plus metadata) for a while, but are working on supporting HTML-only wikis. Those will still be editable using wikitext by using Parsoid for the conversion from HTML to wikitext and then back to HTML after the edit.
+
+See our roadmap at https://www.mediawiki.org/w/index.php?title=Parsoid/Roadmap&oldid=738055 for more detail.",1376517975,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"(Can't reply right now and for a few days, but in the meantime, someone else begs to differ: http://www.flickr.com/photos/fabola/7571369108/in/set-72157630578652390 )",1376516329,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,Bug 49143 is the related bug.,1376512331,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,"To clarify, is this asking for VisualEditor to replace wikitext (WT) with HTML equivalents (but still inside a wikitext place)?
+
+If so, that's not something we will do:
+
+* it makes it hard for users to edit with WT;
+* it would be bad to have VE replace other users' WT unexpectedly;
+* it would be confusing to have mixtures of WT and HTML; and
+* it doesn't save anything technically (it'd still need to go through Parsoid).
+
+Because of these factors, that suggestion is a WONTFIX.
+
+However, there is a different goal for Parsoid to be able to store their HTML+RDFa in the database directly, either alongside, or instead of, the WT that is currently stored. This has a number of advantages but is very far off.
+
+I'm going to re-sort this to reflect the second of these, as I don't believe that there is an existing bug.",1376512174,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+Support Parsoid HTML+RDFa storage alongside or instead of wikitext,I believe this is a long-term goal.,1376447318,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-bgfttfnluju4mvokk3ud,task_subcomment,NA
+VisualEditor: Warn if editing a reference that is used multiple times,"<< When editing a reference, there is no indication at all if it is used multiple times throughout the article. This makes it very easy to screw up references, e.g. when you replace a ref for one sentence by changing it and it gets propagated throughout the article. WS (talk) 11:45, 13 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376394960,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-pdifcdlqnopvfjzdvczw,task_description,resolved
+VisualEditor: Warn if editing a reference that is used multiple times,"The warning ""This reference is used [n] times on this page."" appears for Basic citations only  - verified the fix in beta, test2, and production. 
+
+Bug 73566 was filed to apply the same warning to multiple instances of any kind of citations.",1416331982,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-pdifcdlqnopvfjzdvczw,task_subcomment,NA
+VisualEditor: Warn if editing a reference that is used multiple times,"Change 169270 merged by jenkins-bot:
+Show warning on reference dialog when editing a reference used in more than one place
+
+https://gerrit.wikimedia.org/r/169270",1414517770,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pdifcdlqnopvfjzdvczw,task_subcomment,NA
+VisualEditor: Warn if editing a reference that is used multiple times,"Change 169270 had a related patch set uploaded by Alex Monk:
+Show warning on reference dialog when editing a reference used in more than one place
+
+https://gerrit.wikimedia.org/r/169270",1414453877,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pdifcdlqnopvfjzdvczw,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52771",1376340600,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-m6mab3qibjjsonpriu5r,task_description,resolved
+VisualEditor: cutting block level elements changes the type of following element,"Change 981374 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (402570007)%%%
+https://gerrit.wikimedia.org/r/981374",1701976845,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"Change 981374 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (402570007)%%%
+https://gerrit.wikimedia.org/r/981374",1701971210,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"Change 980444 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Make headings of different levels ""un-mergeable""%%%
+https://gerrit.wikimedia.org/r/980444",1701967183,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"Change 980444 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] Make headings of different levels ""un-mergeable""%%%
+https://gerrit.wikimedia.org/r/980444",1701798922,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,Similar to T52419 in that it involves selections which overflow into the next CBN.,1701797695,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+VisualEditor: cutting block level elements changes the type of following element,"This was first raised at 
+http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Removing_line_above_header_.22de-headers.22_it.3B_lack_of_.22undo.22_facility
+
+If you have a document like
+==Heading 2==
+===Heading 3===
+====Heading 4====
+Paragraph.
+
+i.e.
+
+<h2>Heading 2</h2>
+<h3>Heading 3</h3>
+<h4>Heading 4</h4>
+<p>Paragraph.</p>
+
+and select the heading 3 block, so the selection goes all the way to the right hand side of the screen then delete, it will change the following heading to be an <h3> element. Likewise deleting the whole of the heading 4 line and deleting changes the paragraph to be a <h3> heading.
+
+I've made a test file at http://en.wikipedia.org/wiki/User:Salix_alba/VE_test",1376341181,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-m6mab3qibjjsonpriu5r,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, use TemplateData to hint the parameter's default value, if set","**Author:** `l736ewiki`
+
+**Description:**
+The data model for TemplateData allows the tag ""default"" to assign the default value for parameters which foresee it.
+
+However, when adding a template to an article via VisualEditor, the default value is not presented inside the corresponding input field, which appears empty, nor there are automatic hints about the default value (unless who generated the TemplateData object inserted it into the textual ""description"" item).
+
+I would have expected that:
+* either the user is presented with the input field already pre-filled with the default value as specified inside the TemplateData description - this would improve usability
+* or, if this pre-population of the input field is too complex/costly to achieve, at least the information about the ""default"" value is taken and highlighted using the corresponding ""default"" attribute from the parameter description.
+
+You can test this on it.wiki, by trying editing a new article using VE and adding the template named ""Azienda"", whose ""logo_dimensioni"" parameter has been defined in JSON with ""default"":""200"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376324640,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ejfpqmqzgmehdhmxzmty,task_description,resolved
+Show a message explaining how to edit references when user selects a references list,"Reports such as https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=568123469#I_can.27t_edit_the_references suggest that the references list being present but not editable is causing confusion for editors.
+
+It would therefore be helpful for VE to display a message (popup? tooltip?) whne the reference list is selected that explains how to edit references. The text of this message should be set on a MediaWiki namespace page.
+
+I don't have a suggested default wording at present.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52750",1376257440,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xffvpozuzkjhhlysn3cs,task_description,invalid
+Show a message explaining how to edit references when user selects a references list,No longer needed after {T54750} made the referenced editable inside the references list.,1724164016,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+Show a message explaining how to edit references when user selects a references list,I'm suggesting that task for the Hackathon 2019 since it is something that would ease newcomers' lives. ,1551084196,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+Show a message explaining how to edit references when user selects a references list,[[https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Questions_techniques/semaine_28_2016#Impossibilt.C3.A9_d.27apporter_des_corrections_dans_les_sections_Notes_et_r.C3.A9f.C3.A9rences|New feedback from a user]] (a beginner) who wants to change a reference rom the reflist while editing with VE. ,1468426304,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+Show a message explaining how to edit references when user selects a references list,"This would be most helpful if the backlinks took you to the position of reference while remaining in edit mode.
+
+Suggestion for the message from en.wp user Looie496:
+ ""This list of references is automatically generated and cannot be edited directly. If you would like to change the content of a reference, click on its number where it appears in the body of the article.""",1376323680,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+Show a message explaining how to edit references when user selects a references list,"If implemented, bug 52750 would make this request either unnecessary or applicable only as an interim measure. In the latter case there wouldn't be any need for the message requested here to be editable on-wiki.",1376315524,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xffvpozuzkjhhlysn3cs,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**Author:** `gitartha.bordoloi`
+
+**Description:**
+Hello,
+Visual editor was deployed as an opt-in editing tool in Assamese wikipedia about 2 months ago. However it seems the tool doesn't support Assamese script well. While writing with some tools reproduces only vowels or consonants, the in-built keyboards do not work at all. Kindly look into this matter urgently before it is released as default editing tool. The discussions can be found here: http://as.wikipedia.org/wiki/%E0%A7%B1%E0%A6%BF%E0%A6%95%E0%A6%BF%E0%A6%AA%E0%A6%BF%E0%A6%A1%E0%A6%BF%E0%A6%AF%E0%A6%BC%E0%A6%BE_%E0%A6%AC%E0%A6%BE%E0%A7%B0%E0%A7%8D%E0%A6%A4%E0%A6%BE:%E0%A6%AD%E0%A6%BF%E0%A6%9C%E0%A7%81%E0%A7%B1%E0%A7%87%E0%A6%B2_%E0%A6%8F%E0%A6%A1%E0%A6%BF%E0%A6%9F%E0%A7%B0
+
+Thank you.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1376210460,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_description,resolved
+VisualEditor: Typing problem in Assamese,No replies. Assuming this has been resolved as I can neither reproduce with Assamese input methods provided by UniversalLanguageSelector nor with Assmese input methods offered by my operating system when using VisualEditor.,1644959034,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Could somebody please answer if what's left to do in this ticket ""just"" a dup of {T51569}, or is there more to do (if so, what?)",1429647219,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Is what is left to do in this ticket ""just"" a duplicate of {T51569}? 
+Or is there more to do (if so, what?)",1426772092,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Is what is left to do in this ticket ""just"" a duplicate of {T51569}? 
+Or is there more to do (if so, what?)",1425554546,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"(In reply to comment #11)
+> NONE of the 6 in-built keyboards are working as of today.
+
+I wonder if this is the same as T60662 comment 5 which is marked as a duplicate of T51569...",1425554489,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"(In reply to comment #11)
+> NONE of the 6 in-built keyboards are working as of today.
+
+I wonder if this is the same as bug 58662 comment 5 which is marked as a duplicate of bug 49569...",1389025768,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**gitartha.bordoloi** wrote:
+
+Hello developers,
+I'm regularly checking the visual editor in Assamese wikipedia and now it supports the ""external keyboards"" nicely. There is no problem with rendering of Assamese characters as I reported earlier. However NONE of the 6 in-built keyboards are working as of today. Trying to write something with those keyboards render only Roman characters. I reported the same problem in last August also. Here is a link to my sandbox page in Assamese wikipedia where I've tested the visualeditor with different keyboards. 
+https://as.wikipedia.org/wiki/user:Gitartha.bordoloi/visualeditor_test
+
+I've tested it on Mozilla Firefox 26 and Google chrome 30 (windows 7 pc). I'll be glad to hear about any new developments. Thanks.",1389023971,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"(In reply to comment #8)
+> I tested it in Assamese wikipedia because on 5th September it was mentioned
+> that ""please re-open if you find that it is still happening after tomorrow
+> (when the code will go live on the Assamese Wikipedia)"". I tested it in
+> mediawiki today and found some problems. I'll wait until Thursday and test it
+> in aswiki again. Thank you.
+
+Would it be possible to test 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!",1381269409,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Hello Gitartha, could you also please add some screenshots if you find any problems after your next test? Thanks.",1379515454,PHID-USER-ttw4tpoosxc4pbmskrla,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**gitartha.bordoloi** wrote:
+
+I tested it in Assamese wikipedia because on 5th September it was mentioned that ""please re-open if you find that it is still happening after tomorrow (when the code will go live on the Assamese Wikipedia)"". I tested it in mediawiki today and found some problems. I'll wait until Thursday and test it in aswiki again. Thank you.",1379403525,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"(In reply to comment #6)
+> Hello. I'm reopening the bug as the problems mentioned earlier are still
+> there. Nothing has changed.
+
+Which wiki did you test? The changes only went out to MediaWiki.org last Thursday, 12 September (so you can test these at https://mediawiki.org/wiki/VisualEditor:Test or similar) - they will not be released to the Assamese Wikipedia until this Thursday, 19 September.",1379346325,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**gitartha.bordoloi** wrote:
+
+Hello. I'm reopening the bug as the problems mentioned earlier are still there. Nothing has changed.",1379327158,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,Going to provisionally mark this as fixed - please re-open if you find that it is still happening after tomorrow (when the code will go live on the Assamese Wikipedia).,1378341679,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,I think https://gerrit.wikimedia.org/r/#/c/80080/ may have solved this - let us know!,1377353858,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Hello, Thanks for reporting this. We are currently working to resolve the several issues around using Indic language scripts on the VisualEditor and we expect to resolve them soon. The problem reported in the current bug is also known and exists in other Indic scripts as well.  More discussion about this topic can also be found on bug #49569 . Thanks.",1376926685,PHID-USER-ttw4tpoosxc4pbmskrla,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"**gitartha.bordoloi** wrote:
+
+(In reply to comment #1)
+> Thanks for taking the time to report this!
+> 
+> (In reply to comment #0)
+> > doesn't support Assamese script well
+> > While writing with some tools
+> > in-built keyboards do not work at all
+> 
+> Can you please provide more information / exact steps to reproduce the
+> problems, plus information about browser and version? Also, what are ""some
+> tools"" exactly?
+> Also see https://www.mediawiki.org/wiki/How_to_report_a_bug . Thanks!
+
+Thanks for pointing out the problems with the report.
+
+* I have tested it in Mozilla Firefox 22 and Google chrome 23.
+* There are currently 6 input layouts for Assamese under ULS. While trying to write Assamese in visualeditor with any one of them, NO Assamese character comes out.
+* 'Some tools' refer various Assamese writing tools like to Rodali, Baraha, Azhagi+, Avro barnana etc.
+
+With Rodali, there seems to be problems with vowels like  ী (ঈ), ূ (ঊ), ৌ (ঔ). So while trying to write 'অসমীয়া', it becomes 'অসীয়া'. 'মূহুৰ্ত' becomes ' ূহুৰ্ত', 'কৌটি' becomes ' ৌটি' etc.
+
+with Azhagi+, the problem is more. Only the last vowel character of a word is shown in visualeditor. So 'অসমীয়া' becomes 'া'.
+
+With Baraha, the problem is again with vowel characters like ঐ and ঔ. So 'সৈমান' becomes ' ৈমান'.
+
+Similar problems exists with Avro.",1376765523,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+VisualEditor: Typing problem in Assamese,"Thanks for taking the time to report this!
+
+(In reply to comment #0)
+> doesn't support Assamese script well
+> While writing with some tools
+> in-built keyboards do not work at all
+
+Can you please provide more information / exact steps to reproduce the problems, plus information about browser and version? Also, what are ""some tools"" exactly?
+Also see https://www.mediawiki.org/wiki/How_to_report_a_bug . Thanks!",1376388861,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ltfnf6nk2htfdban76pc,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"MassMessage is an extension that allows a user to send a message to a list of pages through a special page and the job queue. It is intended to replace [[m:Global message delivery]].
+
+More details are available at [[mw:Extension:MassMessage]], and there is a test instance at http://legoktm.instance-proxy.wmflabs.org/wiki/Main_Page
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**URL**: https://www.mediawiki.org/wiki/Extension:MassMessage",1376204700,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_description,resolved
+Review and deploy MassMessage extension to Wikimedia wikis,"Change 91344 had a related patch set uploaded by MZMcBride:
+Enable MassMessage on all wikis
+
+https://gerrit.wikimedia.org/r/91344",1382635706,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #59)
+> Lego: can you please submit a changeset to enable MassMessage on all (public)
+> Wikimedia wikis?
+
+I submitted https://gerrit.wikimedia.org/r/#/c/91344/ a few days ago.",1382632875,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,Lego: can you please submit a changeset to enable MassMessage on all (public) Wikimedia wikis?,1382632099,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"I've been working with Aaron via email on the architecture review and I believe everything has been resolved (cc'd Aaron to get confirmation on that).
+
+(In reply to comment #57)
+> All of the blocking bugs have been resolved. What happens now? (Greg?)
+
+Thanks for merging :). I just added bug 55822 which is a config change for how the jobs will get processed, it would be good to get that deployed and make sure there are no issues before the full deployment.",1381975397,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,All of the blocking bugs have been resolved. What happens now? (Greg?),1381932420,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #54)
+> One more thing - we'll need to add standard licensing/ToS language to the
+> submit screen to ensure content is licensed consistent with Wikimedia
+> requirements. The wikimedia-copyrightwarning message in the WikimediaMessages
+> extension should do the trick.
+
+(The relevant function is EditPage::getCopyrightWarning(), the messages shouldn't be used directly.)",1380916155,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #53)
+> I have a quick question about the extension itself. Maybe I'm reading this
+> code
+> wrong, but the extension appears to iterate through the recipients on the
+> special page, and then make a new job for each recipient. If this is true,
+> that
+> means that this extension would be launching thousands of jobs from a single
+> web request. It kind of defeats the purpose of the job queue in the first
+> place.
+
+Yes, that's correct. I'm not sure how it defeats the purpose of the job queue though. We could do it like refreshlinks works and submit a job that submits more jobs, but I don't see how that would be any better. I did a simple test on testwiki a week ago and submitted 2k jobs at once and it seemed to work fine.
+
+> 
+> Also, do people have some sort of irrational fear of the FormSpecialPage
+> class?
+
+I actually didn't know that existed until now. I basically forked the code of TranslationNotifications and used that...",1380906728,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,One more thing - we'll need to add standard licensing/ToS language to the submit screen to ensure content is licensed consistent with Wikimedia requirements. The wikimedia-copyrightwarning message in the WikimediaMessages extension should do the trick.,1380906422,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"I have a quick question about the extension itself. Maybe I'm reading this code wrong, but the extension appears to iterate through the recipients on the special page, and then make a new job for each recipient. If this is true, that means that this extension would be launching thousands of jobs from a single web request. It kind of defeats the purpose of the job queue in the first place.
+
+Also, do people have some sort of irrational fear of the FormSpecialPage class?",1380906258,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #48)
+> (In reply to comment #39)
+<snip>
+
+I've filed bug 54954 as a blocker to this one. I've asked a few preliminary questions on how this should be implemented, so if people who have options could comment there please :)",1380863370,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #48)
+If there is any way to do global logs (alongside local ones) this would be a very good place to use that, as that would make all wikis much more easily accountable for any usage of this tool.
+
+That said you're probably right in that just enabling the sending part on meta would be better, since, on top of logs and such all being in one place, usage guidelines and crap would also be better synced. And implicitly trusting all admins isn't necessarily a good idea when different projects can have completely different methods and standards when approaching problems, and on top of that pretty much anyone can become an admin at least somewhere (which isn't even necessarily a bad thing, since if they happen to be in the right place even the most unexpected of folks can prove quite useful, but also doesn't mean it should carry weight elsewhere).
+
+So just have a request page for anyone new to use, and a right that can be added to anyone who ain't an admin if they've general use for the spammer and clearly understand what not to do, or whatever. I'm sure the meta folks can argue out some actual details there.",1380862739,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #34)
+> [...] Last year, there was a broken core change about timestamping slipped through
+> Platform review and got deployed. Because of that, a better thought-out and
+> previously-developed pending core change for the exact same feature from
+> Werdna
+> got bumped. [...]
+
+The only thing I found is https://gerrit.wikimedia.org/r/#/c/15746 which was merged after ignoring code-review for months, causing a developer and translator revolt.
+
+(In reply to comment #48)
+> So I'm not comfortable with a deploy that amounts to giving admins in every
+> wiki 'massmessage' permission to every other wiki. I'd be fine with 1)
+> limiting
+> the availability of the massmessage permission to Meta, or 2) adding back the
+> global/local message delivery distinction and enabling local delivery on all
+> wikis, and global delivery on Meta.
+> 
+> Better broadcasting tools should still continually be developed, and the
+> imperfections of this approach will hopefully feed into whatever comes next,
+> whether it's an iteration on MassMessage or an entirely new approach.
+
++1
+I think this is totally reasonable and was indeed my only true worry about the extension.
+I'd add the permission to a special group, possibly reusing centralnoticeadmin group, since the first deploy, to avoid needless requests for adminship.
+More than that, we could even try to replicate the logging of the messages content to a wiki page, for enhanced accountability.",1380862493,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,s/ReviewerBot/MessengerBot/,1380861508,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #39)
+> This was considered and it's probably easy enough to implement these
+> restrictions, but as I said above, I'm not sure they're necessary. My view
+> was
+> to take a ""wait and see"" approach. If local administrators begin to abuse or
+> misuse the tool, we can always add in restrictions later.
+
+I would actually look at it differently. Right now, as I understand it, cross-wiki message delivery is only configured to be run from Meta, where it's easy to see who's configuring what ""spams"" and for what audiences. It's easy for folks to have a shared conversation about what's appropriate and what isn't, and even for people to revert additions that they see as unreasonable.
+
+So you've actually created a very clever tool that plays well into the norms of the wiki community, and uses an existing shared space (Meta) in the intended manner.
+
+In contrast, enabling admins everywhere to _easily_ post bulk messages across wikis from anywhere, with the audit trail being HTML comments in the messages that are left, is IMO quite likely to play against the norms of the wiki, because messages _will_ be sent in a manner that's inconsistent with the norms of a given target wiki, and it'll be harder for the community to have a shared conversation about it or even to easily see what's happening (because there is no central message log at that point).
+
+Because actions such as compiling target lists are dispersed, the normal processes of community peer review won't kick in as effectively to moderate and monitor behavior.
+
+Yes, anyone can of course post anywhere today, but not everyone has access to a shared bot account that they can use on any wiki to do so, nor do they have an automated delivery tool. ReviewerBot would suddenly take bot actions on wikis and users would be tasked with figuring out what's going on. That's manageable if the only possible source is Meta, but more problematic if the source is any of our wikis.
+
+Cross-wiki bulk messages to anywhere from anywhere are a significant change from the status quo that requires more consideration. And on that point, WMF will certainly get the blame if the tool is misused.
+
+So I'm not comfortable with a deploy that amounts to giving admins in every wiki 'massmessage' permission to every other wiki. I'd be fine with 1) limiting the availability of the massmessage permission to Meta, or 2) adding back the global/local message delivery distinction and enabling local delivery on all wikis, and global delivery on Meta.
+
+Better broadcasting tools should still continually be developed, and the imperfections of this approach will hopefully feed into whatever comes next, whether it's an iteration on MassMessage or an entirely new approach.",1380861333,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+> > To the first document which has its origins in the SVN days, the first stop
+> > with Howie Fung and his product management team. To my knowledge the only
+> > person asked was a Dan Garry, and not as a first stop on anything. 
+> 
+> Dan was cc'd by Greg in comment 13. I wasn't aware that Platform and/or
+> Features were supposed to be in the loop so I never bothered to do it.
+
+It's unfortunate. Dan is new and is not really in a position to speak for product, and I don't think that was the intent of comment 13 to make him make a call.
+
+The implication of Platform or Features is in the later stage of code review for deployment. There was a time that Sumana would manage that using 20% time volunteered by Features, but that was over a year ago. :-( Since then commitment to maintain deployed extensions has fallen through the crack between Platform and Features.
+
+> Correct. I had spoken with Greg a few days earlier about emailing wikitech-l
+> /
+> Aaron / Tim for the architecture review, and he recommended that I wait for
+> your comments ;-)
+
+Oh, well then why was it added to the deploy calendar? Can we remove it backand wait for comments to make sure it's okay to deploy before adding it to the lsit of things to be deployed? As it stands now, my position is I'm okay with it because Ori is okay with helping you support and monitor it for issues that might crop up like comment 37 above.
+
+> > The second document is newly written by Platform not vetted by anyone in
+> > Features.
+> 
+> For someone outside of the WMF who is trying to get an extension deployed,
+> the
+> distinction between Platform and Features isn't very clear, nor really
+> important. Was VipsScaler (also written by a volunteer) handled by Features?
+
+No, and in earlier incarnations of the queue, I think [[mw:VipsScaler]] was linked. Development on it was started in 2011, I think multimedia team (originally a Features team, now in Platform) deployed it. That team is obviously committed to maintain. :-)
+
+> All we really want is our code deployed :P
+
+Totally understandable. :-)
+
+
+> The checklist is fine, it just seems like its missing one step according to
+> you
+> (notify Features and/or Platform teams).
+
+I'm okay with clarifying that a design review means a product design review and PM signoff and adding that a plan for engineering, product, and design maintenance needs to be in place going forward (beyond simply bugzilla).",1380858967,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+(In reply to comment #41)
+> (In reply to comment #7)
+> > == TODO/Check list ==
+> > Extension page on mediawiki.org: yes
+> > Bugzilla component: yes
+> > Extension in Gerrit: yes
+> > Design Review: no
+> > Archeticecture/Performance Review: no
+> > Security Review: no
+> > Screencast (if applicable): no
+> > Community support: no?
+> 
+> As a designer, I did a design review over IRC. I said something along the
+> lines
+> of 'looks shiny'.
+> 
+> I hope that helps, as I'm not sure what more you could want with this kind of
+> extension. Other issues beyond the interface itself have generally already
+> been
+> established by precedent (EdwardsBot).
+
+We'd have to ask Greg what he really meant by this when he added that to [[mw:Review queue]] instead of leaving the process pointing back to [[mw:Writing_an_extension_for_deployment]], but if I were to hazard a guess:
+
+I think Greg tried to clear the review queue because it was suffering from neglect. He tried summarize the original linked document: [[mw:Writing_an_extension_for_deployment#Design_review]] by saying it has a proper ""design review."" It clearly implies design review as being a product design review with a design UI design component [[mw:WMF_Project_Design_Review_Process]] probably dating back to when they were in the same department.
+
+If you look at an earlier revision [https://www.mediawiki.org/w/index.php?title=Review_queue&oldid=697844], you can see the tracking list that was its original purpose since Brion created it. Around that time, it was getting unmanageable four months ago with little movement. My guess is that there simply had been no recent Extensions (other than in-flight extensions like Math and SignupAPI) that had actually gone through this process and in an effort to systematize the process into a workable checklist, it got morphed over time from ""send it to product design for review"" to ""send an e-mail to a designer and to the design mailing list."" *shrug*",1380857974,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #40)
+> (In reply to comment #38)
+> 
+> > > The requirement for extensions to be deployed has ALWAYS been that Features
+> > > Engineering sign off on a commitment to maintain the extension.
+> > 
+> > This isn't consistent with the documentation at [[mw:Writing an extension for
+> > deployment]], [[mw:Review queue]] and Greg's checklist in comment 7.
+> 
+> Interesting links.
+> 
+> To the first document which has its origins in the SVN days, the first stop
+> with Howie Fung and his product management team. To my knowledge the only
+> person asked was a Dan Garry, and not as a first stop on anything. 
+
+Dan was cc'd by Greg in comment 13. I wasn't aware that Platform and/or Features were supposed to be in the loop so I never bothered to do it.
+
+> I mentioned
+> in my original post why that people should know better. The second stop was
+> wikitech-l. To my knowledge mine was the first post on the subject.
+
+Correct. I had spoken with Greg a few days earlier about emailing wikitech-l / Aaron / Tim for the architecture review, and he recommended that I wait for your comments ;-)
+
+
+> The second document is newly written by Platform not vetted by anyone in
+> Features.
+
+For someone outside of the WMF who is trying to get an extension deployed, the distinction between Platform and Features isn't very clear, nor really important. Was VipsScaler (also written by a volunteer) handled by Features? All we really want is our code deployed :P
+ 
+> The third link refers to someone who has been at the WMF even less time than
+> me. If we're to use MZMcBrides seniority rules, the fact that some
+> newly-minted, improperly vetted document was used by a relatively new
+> engineer
+> doesn't carry weight.
+
+The checklist is fine, it just seems like its missing one step according to you (notify Features and/or Platform teams).
+
+> I hope that documentation is updated.
+
+Be bold!",1380856387,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #41)
+> As a designer, I did a design review over IRC. I said something along the
+> lines
+> of 'looks shiny'.
+
+For reference, Isarra created [[commons:File:Massmessage preview (uncyc).png]], and pointed out a few flaws in the initial design, like using tables for the form (now switched to proper <div>s), and the submit/preview buttons stacked on top of each other (now side-by-side).",1380855315,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #39)
+> (In reply to comment #37)
+> > Is the current thinking to give users on any wiki the right to use
+> > Special:MassMessage to spam users on any other wiki?
+> 
+> Yes. The design idea here was that this is already possibly by any user.
+> Anyone
+> can open up a bunch of browser tabs and post to dozens of wikis quickly
+> without
+> even logging in. Or, for example, I've been posting to hundreds of wikis for
+> years without a privileged account using only a very simple Python script.
+
+It might be worth noting that the MassMessage bot account used automatically adds itself to the 'bot' group, but isn't able to override full protections or anything like that.
+
+> 
+> > It seems to me you'd want something like:
+> > 
+> > * Users on Meta can trigger cross-wiki notifications;
+> > * Users on any other wiki can only trigger local notifications.
+> 
+> This was considered and it's probably easy enough to implement these
+> restrictions, but as I said above, I'm not sure they're necessary.
+
+An initial version of the extension had this differentiation, but it was removed in https://gerrit.wikimedia.org/r/#/c/78047/. I don't mind revisiting the concept either (file a bug for it?), as it wouldn't be hard to implement technically.
+
+> My view was
+> to take a ""wait and see"" approach. If local administrators begin to abuse or
+> misuse the tool, we can always add in restrictions later.
+> 
+> > Otherwise you end up with an audit trail mess. Having a single log in one
+> > place and a single place to set policy around these things seems highly
+> > desirable.
+
+I actually wrote [[mw:Extension:CentralLogging]] for this problem a while back, but it wouldn't work in the WMF environment.
+
+  
+> The bot currently provides an audit trail by (optionally?) appending an HTML
+> comment containing the originating wiki, message sender's name, etc., I
+> believe. Lego can confirm this.
+
+The audit trail is not optional (though a wiki could choose to blank the message and make it useless). An example is <https://test2.wikipedia.org/w/index.php?title=User_talk:Legoktm&action=edit&section=2>, which includes the origin wiki, sender, and spamlist used.",1380855098,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #40)
+> Do you have a link to this doctrine regarding software deployments and
+> sign-offs? [...] perhaps there's a guideline you've written on mediawiki.org,
+> wikitech.wikimedia.org, or Meta-Wiki. Please share.
+
+Go on. I'll wait.",1380854469,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #7)
+> == TODO/Check list ==
+> Extension page on mediawiki.org: yes
+> Bugzilla component: yes
+> Extension in Gerrit: yes
+> Design Review: no
+> Archeticecture/Performance Review: no
+> Security Review: no
+> Screencast (if applicable): no
+> Community support: no?
+
+As a designer, I did a design review over IRC. I said something along the lines of 'looks shiny'.
+
+I hope that helps, as I'm not sure what more you could want with this kind of extension. Other issues beyond the interface itself have generally already been established by precedent (EdwardsBot).",1380854018,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+You're going to resort to ad hominem instead of attacking the argument when you're already getting what you want?
+
+I am not trying to ""dictate"" anything to volunteers. Volunteers didn't deploy the code onto test and test2, it was Reedy. Volunteers are free to develop. They're not free to have their developed code deployed on the cluster. Nobody is.
+
+As for the proof of this ""doctrine,"" just like MediaWiki core has always been the responsibility of Platform, the Extensions space has traditionally been the responsibility of Features Engineering. Historically, new extension deploy and a commitment to deploy was done by Brion and later by Roan. This used to be enforced in terms of SVN access, and the artifact still exists in the form of who has +2 on Gerrit. In the case of deploying a new extension, it requires +2 on gerrit, shell access, and an implied commitment to maintain.
+
+I've been trying to relax this as I feel this is unscalable solution, but with that right comes the responsibility. If you or other community developers are unwilling to hold yourselves to the same responsibility that every engineer of the Foundation is held to, you are free to do so. But nobody has the right to have +2, nobody has the right to shell access, etc. Just as Platform and Ops reserve the right as policy to rescind my +2 access and my non-existent shell access, they could rescind anyone else's, even yours if it existed.
+  
+
+(In reply to comment #38)
+
+> > The requirement for extensions to be deployed has ALWAYS been that Features
+> > Engineering sign off on a commitment to maintain the extension.
+> 
+> This isn't consistent with the documentation at [[mw:Writing an extension for
+> deployment]], [[mw:Review queue]] and Greg's checklist in comment 7.
+
+Interesting links.
+
+To the first document which has its origins in the SVN days, the first stop with Howie Fung and his product management team. To my knowledge the only person asked was a Dan Garry, and not as a first stop on anything. I mentioned in my original post why that people should know better. The second stop was wikitech-l. To my knowledge mine was the first post on the subject.
+
+The second document is newly written by Platform not vetted by anyone in Features. I assume that if Platform wants to operate that way then they're committed to maintaining an extension approved that that process, that's cool with me and entirely consistent to my statements. In it's original incarnation it was Sumana's way of managing code review of existing extensions.
+
+The third link refers to someone who has been at the WMF even less time than me. If we're to use MZMcBrides seniority rules, the fact that some newly-minted, improperly vetted document was used by a relatively new engineer doesn't carry weight.
+
+I hope that documentation is updated.",1380853822,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #37)
+> Is the current thinking to give users on any wiki the right to use
+> Special:MassMessage to spam users on any other wiki?
+
+Yes. The design idea here was that this is already possibly by any user. Anyone can open up a bunch of browser tabs and post to dozens of wikis quickly without even logging in. Or, for example, I've been posting to hundreds of wikis for years without a privileged account using only a very simple Python script. The difference here in functionality isn't very big. The primary difference is that we're adding a proper user interface for delivery submissions and reducing the need for an external dependency (a bot).
+
+> It seems to me you'd want something like:
+> 
+> * Users on Meta can trigger cross-wiki notifications;
+> * Users on any other wiki can only trigger local notifications.
+
+This was considered and it's probably easy enough to implement these restrictions, but as I said above, I'm not sure they're necessary. My view was to take a ""wait and see"" approach. If local administrators begin to abuse or misuse the tool, we can always add in restrictions later.
+
+> Otherwise you end up with an audit trail mess. Having a single log in one
+> place and a single place to set policy around these things seems highly
+> desirable.
+
+Again, anyone can go around posting messages to any wiki right now without even logging in. Giving local administrators the ability to send cross-wiki messages with a simpler tool doesn't seem to warrant much concern from my perspective, but if you consider this a requirement for wider deployment, Lego can add in the restrictions.
+
+The bot currently provides an audit trail by (optionally?) appending an HTML comment containing the originating wiki, message sender's name, etc., I believe. Lego can confirm this.",1380853667,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #35)
+> Ori has stepped up and is willing to commit his time to help Legoktm in
+> supporting MassMessage on an ongoing basis. According to the current standard
+> of the above, there is no longer any block on bug 52723.
+
+Thank you Ori!
+
+> The requirement for extensions to be deployed has ALWAYS been that Features
+> Engineering sign off on a commitment to maintain the extension.
+
+This isn't consistent with the documentation at [[mw:Writing an extension for deployment]], [[mw:Review queue]] and Greg's checklist in comment 7.",1380853061,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Is the current thinking to give users on any wiki the right to use Special:MassMessage to spam users on any other wiki?
+
+It seems to me you'd want something like:
+
+* Users on Meta can trigger cross-wiki notifications;
+* Users on any other wiki can only trigger local notifications.
+
+Otherwise you end up with an audit trail mess. Having a single log in one place and a single place to set policy around these things seems highly desirable. If we're on the same page on that, I'm significantly less concerned about the long term impact of the extension.",1380852890,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #35)
+> The requirement for extensions to be deployed has ALWAYS been that Features
+> Engineering sign off on a commitment to maintain the extension.
+
+You've been at the Wikimedia Foundation for, what, two years? You really feel it's appropriate to lecture me and others about how things have ""always"" been? You seem to have absolutely no sense of how software deployments have operated for the majority of Wikimedia's existence.
+
+You're attempting to dictate to volunteers as though they're your subordinates. This is wildly inappropriate.
+
+Do you have a link to this doctrine regarding software deployments and sign-offs? As far as I can tell, you've just made it up here on this bug. But perhaps there's a guideline you've written on mediawiki.org, wikitech.wikimedia.org, or Meta-Wiki. Please share.",1380851998,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+Ori has stepped up and is willing to commit his time to help Legoktm in supporting MassMessage on an ongoing basis. According to the current standard of the above, there is no longer any block on bug 52723.
+
+Time still has to be made to handle the rollout, but I'm assuming what is already in-process in Platform, and Ori can assist beyond that.
+
+The requirement for extensions to be deployed has ALWAYS been that Features
+Engineering sign off on a commitment to maintain the extension. I've relaxed it
+to be: ""If another engineering department in collaboration with product is
+willing to commit to it, Features will not block."" I'd like to someday relax
+this further to: ""If any engineering department or community development in
+collaboration with the other core competencies (features, product, design, and
+community) are willing to commit to it, no one should block."" We are not there
+yet, and trying to rail against that is winning a battle at the cost of the war
+breaking down these silos and having shared ownership and responsibility in our
+organization, in our community, and in our movement.
+
+Please realize the current state of affairs is that new Extension deploy can be done under the following frameworks:
+
+1) The traditional ""Features signs off on all extensions"" that has always been in place. For Features to sign off on this, like with our own engineering staff, we require collaboration and buy-in in affected areas like the product managers and designers who will lose productivity or might be retasked on this. We must be good stewards of each-others times, and I would not have permitted (and will not permit) my engineers to task Platform and Design engineers for MassMessage in the manner that has happened to date (water under the bridge at this point).
+2) The above can and has been be bypassed on a directive from the VPE as was the case for BetaFeatures.
+3) Like LanguageEngineering's use of TranslationNotifications instead of Echo, if another team consisting of engineering, product, and design is willing to commit to supporting on an ongoing basis, then extension deploy proceeds without the traditional rule of discussing Features. Note, in this example we have an assumption that the feature set of MassMessage is as-is so it currently doesn't involve Product or Design, nor does it require more engineering resources inside the WMF beyond Ori who is currently untasked.
+
+We still eventually want to reach the point where the criteria is not the amalgam of rules above but a simpler one based on intent, expertise-sharing and consensus-building: ""If any engineering department or community developer in collaboration with the other core competencies (engineering, product, design, and community) are willing to commit to ongoing maintenance of a feature, then no one group should block it.""
+
+We haven't reached there yet, and please realize that when me make exceptions as in this case, it compromises the larger picture of our need to break down these silos and create shared ownership and responsibility in the WMF, in our communities, and in the movement as a whole.",1380851471,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+(In reply to comment #33)
+
+> This comparison carries no value: 1) LQT can't be undeployed because we'd
+> lose
+> critical data (discussions) from the wiki, 2) AFT is being expanded right now
+> with no exit strategy I'm aware of (probably under the understanding that
+> nobody cares if all that data disappears from the wikis after undeployment).
+
+It carries more value that bug 31235 does to implement bug 52723. MassMessage is an extension, as an extension it is under the same rules as all other extensions for deployment.
+
+1) LQT can't be underplayed and we're stuck with it for an uncertainf eatures
+2) ReaderFeedback, AFT, and AFTv5 are all different extensions.
+
+> I highly doubt I do. My sentence started with an ""If"" for a reason: I've no
+> idea who's responsible for Echo.
+
+Then I apologize, it's easy to read your statement and not have the hidden assumption that someone is responsible for Echo. Nobody is, it, like everything else, is a shared responsibility.
+
+> Let me note that I asked how you planned to coordinate with other pieces of
+> code/devs working in this area already 9 months ago: [[m:IRC office
+> hours/2013-01-08]].
+
+Hmm, I didn't read what you said as being related to this, most of what was in that discussion was posted on the grandparent bug and little movement has been done since then.
+
+As to your logs: currently there is only one Dev working on Echo: bsitu. RoanKattouw and matthiasmullie never got the chance to work on this project, lwelling is no longer with us, Krenair is a community dev who I assume is wrapped up in other issues with core, kaldari is now in Mobile, fabriceflorin is in Multimedia and Werdna is on Flow. I don't know the state of [[mw:Extension:TranslationNotifications]] but I believe it's under active development/maintenance by Language Engineering. Their contributions are in this log, on mediawiki, in the code base, and in fabriceflorin's notes. When work on Echo is restarted, bsitu will be involved in it.
+
+
+> I gather that you feel insulted and circumvented or something like that and
+> I'm
+> sorry for this personal pain you're suffering, but all this talk about
+> exploiting doesn't look helpful.
+
+I'm not insulted. I pushed back one time in a close-door meeting (I prevented deployment on mediawiki.org with the understanding from all the participants of the meeting that MassMessage would not be deployed on the cluster). Since people aren't aware of it, I am trying to explain the decision and the reasoning behind it.
+
+I apologize for this language of ""exploiting."" Here was the topline of my original discussion which is relevant (but deleted from the bug comment):
+
+> When I use to loaded words like ""back-dooring"" etc, I believe that no malice was intended and the discussions so far have been in good faith from all parties. I think people have a valid concern and want it addressed and are wondering honestly how decisions have been made. In particular, my decision to not allow the MassMessage Extension to roll out onto MediaWiki last week, since that occurred during a meeting that didn't even involve or derive have consultation (except ex-post-facto) with any product manager or engineer here.
+
+It is very likely that adding the previous deploy and this one to the deploy calendar on Thursday would have someone like me either missing it or taking it at face value (that someone outside my own team added it and has adopted responsibility).
+
+Last week, I didn't have time to figure out the parameters of where the decision to deploy MassMessage came from, so I only pushed back on mediawiki.org. The understanding from me and all the participants of the Friday meeting was that MassMessage would not be deployed beyond that.
+
+The fact is at that moment this spent all of one day on the deploy calendar added by someone outside the WMF, one and a half weeks in public development on obscure parts of the wiki and bugzilla, had no discussion with product, no plan for support, etc.
+
+No new feature would have been deployed to even test or test2 without discussions from Features, Design and Product. I didn't realize that any of this had occurred.
+
+This is not a standard anymore for deployment of an extension, nor has it been for quite a while.
+
+> This is not a reply to my line you quoted.
+
+Hmm, I feel it is but I guess this depends on the definition of what is is? :-)
+
+If it is unreasonable to require sign off for Features Engineering for Extension deploy than it is an unreasonable thing that has been in place long before me. I'm trying to relax that requirement, one area of relaxing is to find another home for deployment and support.
+
+Last year, there was a broken core change about timestamping slipped through Platform review and got deployed. Because of that, a better thought-out and previously-developed pending core change for the exact same feature from Werdna got bumped. To get this fixed,the Echo team had to make a new core patch that superseded the earlier, broken patch, satisfied Language Engineering's wishlist, and handled what Echo needed which took weeks of effort and time that wasn't necessary had the timestamp patch not been put into core in the first place.
+
+It was unreasonable, but it was life.
+
+We can operate on the old rules of ""Features Engineering needs to sign on support for Extension wide cluster deploy"" or we cannot.
+
+Under the former, Features's answer is not no. Our answer is We need to hear something more urgent and important or my answer is not yet from Features. Everything WMF Features Engineering does is in collaboration with other areas: product, design, design, and community, and I refuse to allow me or my teams to operate differently.
+
+Under the latter, support for this needs to find another home just like TranslationNotifications or BetaFeatures did.
+
+Someday, I hope we can do better. Things like BetaFeatures and Workflows part of Flow may make that possible.",1380845232,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"I don't want to monopolise the discussion so I'll briefly reply to some ""personal points"".
+
+(In reply to comment #32)
+> > This appears to be a false problem. If Echo or something else in a future
+> > provides equivalent or better features, the extension will fall into disuse
+> > and/or it can be undeployed.
+> 
+> That argument may have held water back when extensions like ReaderFeedback or
+> LiquidThreads were written and deployed. 
+
+This comparison carries no value: 1) LQT can't be undeployed because we'd lose critical data (discussions) from the wiki, 2) AFT is being expanded right now with no exit strategy I'm aware of (probably under the understanding that nobody cares if all that data disappears from the wikis after undeployment).
+
+> [...]
+> 
+> > I don't get these points. If you're responsible for Echo, it's your
+> > responsibility to decide what Echo is going to incorporate, it's not the
+> > others' responsibility to guess it and be blocked for years while you figure
+> > it
+> > out.
+> 
+> I'm responsible for ENGINEERING RESOURCING on Echo. [...]
+> 
+> You have a misguided view of what I do or what works in general in our
+> movement
+> or at the WMF.
+
+I highly doubt I do. My sentence started with an ""If"" for a reason: I've no idea who's responsible for Echo.
+
+Let me note that I asked how you planned to coordinate with other pieces of code/devs working in this area already 9 months ago: [[m:IRC office hours/2013-01-08]].
+
+> [...] I'm asking that while I agree (and I think most would) that it'd be nice to
+> have movement on the parent bug, people stop trying to exploit known holes in
+> our development processes to try to get a particular implementation that is
+> not
+> derived from consensus and has bypassed every standard erected to safeguard
+> sustainable development at the WMF: either work within the system or don't
+> but
+> don't try to get something deployed and say it's Features' problem because
+> it's
+> an extension. This sort of behavior breaks down trust in our people and
+> processes many of whom and which are new, fragile,and need to be nurtured,
+> not
+> exploited.
+
+I gather that you feel insulted and circumvented or something like that and I'm sorry for this personal pain you're suffering, but all this talk about exploiting doesn't look helpful.
+
+> [...]
+> > > The above can occur independently or in parallel to the above. If Product
+> > > thinks it cool to commit Platform's constrained engineering resources to
+> > > [...] use it to take
+> > > advantage of Echo when the features roll out in some undefined future,
+> > 
+> > this looks like an unreasonable requirement
+> 
+> The requirement for extensions to be deployed has ALWAYS been that Features
+> Engineering sign off on a commitment to maintain the extension. [...]
+
+This is not a reply to my line you quoted.",1380838994,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+(In reply to comment #30)
+> (In reply to comment #28)
+> > bug 52723 is a recent bug to deploy Legoktm's MassMessage extension as a
+> > solution to bug 35306, it is less than a month old there has been little
+> > public
+> > discussion [...]
+> 
+> For your following points, it seems you're implying that the desiderata and
+> requirements for this extension are not clear. This couldn't be less true[edit]:
+> the
+> requirements are to take over EdwardsBot (a successful product) in the least
+> impactful way possible.
+
+bug 52723 on its own is clear, but as a solution to bug 35306, it is not. If we actually want to solve bug 35306 in an ideal world, nobody would use 52723, nor would Platform resources have been spent on 52723.
+
+For instance, what is the timescale necessary before EdwardsBot is unworkable? Has it failed immediately or is failure immanent? If not, why then the rush on bug 52723? If so, then we need to discuss what to do of which bug 52723 is the only option right now. No other extension in recent memory has been deployed on the cluster with so little public discussion, without any product approvals, without any commitment from Features for maintenance.
+
+> > The problem with moving on bug 52723 as a solution to bug 35306 is it commits
+> > Features Engineering to maintaining an extension that is a stop gap solution
+> > with no or very little discussion in a manner that doesn't serve a broad
+> > strategic goal about how messages, notifications, etc. should be handled on
+> > the
+> > wikis. [...]
+> 
+> This appears to be a false problem. If Echo or something else in a future
+> provides equivalent or better features, the extension will fall into disuse
+> and/or it can be undeployed.
+
+That argument may have held water back when extensions like ReaderFeedback or LiquidThreads were written and deployed. We still have those extensions cluttering the cluster with no serious commitment to support, no easy avenue for sunsetting. Unlike that time, we now real product and development processes in place. Those processes should be given a chance to work before being bypassed.
+
+It would be unfair to every engineer here and all extensions written if the old standard of, ""If something better comes along, this will die naturally"" is applied in this case barring some emergency. That standard hasn't been applied during my tenure here and I'm not going to make an exception just because Platform's checklist for covers core deployments has been gamed to cover a new extension deployment that would not reached this stage and would have received an reprimand from me (wasting Platform's resources) had my own engineers done this.
+
+While MassMessage is replacing or superseding current site functionality, this is this isn't improving or superseding a current (neglected) extension. For instance, the community-initiated work being done on the Math Extension (which I might had has had infinitely more discussion on wikitech-l) because this site functionality  If anything, the inability of Features Engineering to review and maintain the current deployed extensions should make the case against MassMessage adding to that balance sheet already deeply in the red.
+
+The simple reality is that Features Engineering will not support the MassMessage Extension as is. But if a different department like Platform Engineering is actually committed to supporting it indefinitely, I'll cede the ground entirely. I did the same to Language Engineering with Translation Notifications. This time, I'd recommend discussion with others how that experience has worked out (I don't know myself, because Feature ceded responsibility here).
+
+> > [...] After discussion during that Friday
+> > meeting among the EPMs, I compromised to let it to go out on two test wikis,
+> > but not on mediawiki. Nobody made the case that it should go out on
+> > mediawiki.
+> 
+> AFAIK, this is a MediaWiki extension. Do you mean ""not on mediawiki.org""?
+
+Yes, sorry. I meant the mediawiki.org. You can see the context of my use of mediawiki by itself from the change history I linked to above.
+
+> I don't get these points. If you're responsible for Echo, it's your
+> responsibility to decide what Echo is going to incorporate, it's not the
+> others' responsibility to guess it and be blocked for years while you figure
+> it
+> out.
+
+I'm responsible for ENGINEERING RESOURCING on Echo. Right now a full-time engineer has been devoting his full time in supporting a product that is ""done"" simply because the rollout hasn't yet happened on all the wikis. If I want to commit more time developing enhancements to it, I have to take that resource from somewhere else like VisualEditor or Flow. Because it affects those teams, I'd negotiate with the product managers on that time. In addition, I'm okay with being ordered to change that current level or resourcing by Erik, Sue, or the Board, but until then I make the resourcing decision based on my responsibility toward achieving the Annual Plan, the Strategy, and other commitments we've made.
+
+You have a misguided view of what I do or what works in general in our movement or at the WMF. What or what-not Echo incorporates, like all decisions of this nature, are not mine alone but the responsibility of Product Design in discussion with me, my teams, and others. When it comes to Echo specifically, because I have the least domain knowledge on the team, I have the least contribution and thus the least authority to do beyond a suggestion. This is a Good Thing. We should be good stewards of each others time and energy and not commit others without discussion with them.
+
+I have a lot of stuff I'd like to do and I'd like to promie, but I agree to abide by this framework and expect my teams to do the same. I make and enforce the rules with respect to Features Engineering, but I do not make all the decisions for the features, or even the most relevant ones in this matter.
+
+> Are you saying you're going to figure it out so that people can
+> understand
+> how to work with/for Echo without being just blocked by it?
+
+I am saying, ""Here is an approach we can take. I realize that it's a 3-6 month to 1 year thing, but so is everything else we've done. If you've held off for almost 2 years, can you hold off a bit longer? This approach can be done orthogonal to other approaches (like this bug), but the important thing to be is consistent so we avoid things (like ad-hoc extension deployments) that we know haven't worked in the past.""
+
+I'm saying if you can't be blocked by this bug and need Features to support it, then either go without Features or state reasons other than ""it's been in bugzilla for almost 2 years"" because that has never been a standard to get stuff fixed and deployed.
+
+I'm asking that while I agree (and I think most would) that it'd be nice to have movement on the parent bug, people stop trying to exploit known holes in our development processes to try to get a particular implementation that is not derived from consensus and has bypassed every standard erected to safeguard sustainable development at the WMF: either work within the system or don't but don't try to get something deployed and say it's Features' problem because it's an extension. This sort of behavior breaks down trust in our people and processes many of whom and which are new, fragile,and need to be nurtured, not exploited.
+
+For instance, BetaFeatures was shopped around long before MassMessage, bypassing Features Engineering. They got a bite in Multimedia and Mobile and now Multimedia wants to deploy this and move on to work on… Multimedia and is in a spot with respect to support for this extension. Part of me wants to say, ""Well you knew this was going to happen, why didn't you involve the rest of Product and Features before you got to this point?"" And that's for an extension that had far more buy-in, development, design, and direction (from the VP level even), and isn't even deployed yet!
+
+It is for exactly sort of situations that the consensus and discussions with product, design, and features is a standard for all new features in the first place. When this rule is bent as in the case of BetaFeatures, it causes problems which the people who took it on understood would come as a consequence. When this rule isn't even followed, as in the case of MassMessage, Features opts-out, but another department is welcome to take this on.
+
+> > The above can occur independently or in parallel to the above. If Product
+> > thinks it cool to commit Platform's constrained engineering resources to
+> > deploying and supporting MassMessage Extension forever 
+> 
+> This is one thing,
+> 
+> > and use it to take
+> > advantage of Echo when the features roll out in some undefined future,
+> 
+> this looks like an unreasonable requirement
+
+The requirement for extensions to be deployed has ALWAYS been that Features Engineering sign off on a commitment to maintain the extension. I've relaxed it to be: ""If another engineering department in collaboration with product is willing to commit to it, Features will not block."" I'd like to someday relax this further to: ""If any engineering department or community development in collaboration with the other core competencies (features, product, design, and community) are willing to commit to it, no one should block."" We are not there yet, and trying to rail against that is winning a battle at the cost of the war breaking down these silos and having shared ownership and responsibility in our organization, in our community, and in our movement.
+
+> (are you going to shutdown
+> message
+> bots too if they don't use Echo?).
+
+No. Message bots are not Extensions. I think the criteria to move EdwardsBot into ToolLabs is different. If MZMcBride would like assistance on this, I think the engineering community team and operations will offer it.
+
+Personally, I (and I assume you) would like a solution beyond and more sustainable than saddling MZ and EdwardsBot with more work. The original bug points out that much of the Wikimedia Foundation is dependent on MZ's bot. If MassMessage Extension is the only option or is an emergency option, so be it — people have shortcutted processes before and have had to live with the consequences.
+
+Otherwise, we need to have that discussion in front of all of WMF Tech, on Wikitech-l in front of the mediawiki community, and in front of the C-levels and the board as part of the annual plan, not just on this bug.",1380837927,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,*couldn't be less true,1380829988,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #28)
+> bug 52723 is a recent bug to deploy Legoktm's MassMessage extension as a
+> solution to bug 35306, it is less than a month old there has been little
+> public
+> discussion [...]
+
+For your following points, it seems you're implying that the desiderata and requirements for this extension are not clear. This couldn't be less clear: the requirements are to take over EdwardsBot (a successful product) in the least impactful way possible.
+
+> 
+> The problem with moving on bug 52723 as a solution to bug 35306 is it commits
+> Features Engineering to maintaining an extension that is a stop gap solution
+> with no or very little discussion in a manner that doesn't serve a broad
+> strategic goal about how messages, notifications, etc. should be handled on
+> the
+> wikis. [...]
+
+This appears to be a false problem. If Echo or something else in a future provides equivalent or better features, the extension will fall into disuse and/or it can be undeployed.
+
+> [...] After discussion during that Friday
+> meeting among the EPMs, I compromised to let it to go out on two test wikis,
+> but not on mediawiki. Nobody made the case that it should go out on
+> mediawiki.
+
+AFAIK, this is a MediaWiki extension. Do you mean ""not on mediawiki.org""?
+
+> [...]
+> 
+> For example, features in MassMessage and EdwardsBot need to be addressed in a
+> Must-Have, Should-Have, Could-Have, Won't-Have (MoSCoW) framework. 
+
+Isn't this what dependencies are for? I see one dependency and it's fixed.
+
+> [...]
+> 
+> 1) wait for some things to happen: legoktm to get an RfP, Echo to be on all
+> wikis, and Benny to do an entire Flow only sprint and balancing his time more
+> effectively wrt Echo.
+
+I don't understand how keeping to use a bot for the very same things this extension would do helps Echo.
+
+> 2) MoSCoW other features of MassMessage/EdwardsBot for integration into Echo
+> 3) Enhance and deploy a first pass to Echo to allow some sort of mass
+> notification from a wiki list
+> 4) Some sort of cross wiki notification enhancement (requires a design pass)
+> 5) Discuss how to implement must-have or should-have features of EdwardsBot
+> that can't live in Echo (permanent log of events)?
+> 6) Add those to plan and be done.
+
+I don't get these points. If you're responsible for Echo, it's your responsibility to decide what Echo is going to incorporate, it's not the others' responsibility to guess it and be blocked for years while you figure it out. Are you saying you're going to figure it out so that people can understand how to work with/for Echo without being just blocked by it?
+
+> The above can occur independently or in parallel to the above. If Product
+> thinks it cool to commit Platform's constrained engineering resources to
+> deploying and supporting MassMessage Extension forever 
+
+This is one thing,
+
+> and use it to take
+> advantage of Echo when the features roll out in some undefined future,
+
+this looks like an unreasonable requirement (are you going to shutdown message bots too if they don't use Echo?).",1380829865,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+I am not modifying this bug, to leave open the avenue that Platform Engineering commits to supporting [[mw:Extension:MassMessage]], only bug 35306.",1380828245,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"**tchay** wrote:
+
+We have two separate but related bugs here: 
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=35306
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52723
+
+bug 35306 is an tracking bug MZMcBride posted for a solution to deal with EdwardsBot. I believe it dates to around the time I was first employed almost two years ago.
+
+bug 52723 is a recent bug to deploy Legoktm's MassMessage extension as a solution to bug 35306, it is less than a month old there has been little public discussion, and until it appeared on the deploy calendar last week, I wasn't even aware of its existence.
+
+The problem with moving on bug 52723 as a solution to bug 35306 is it commits Features Engineering to maintaining an extension that is a stop gap solution with no or very little discussion in a manner that doesn't serve a broad strategic goal about how messages, notifications, etc. should be handled on the wikis. To the first, maybe there is something wrong with my e-mail client, but I have yet to find this discussion on wikitech-l or anywhere outside the bug.
+
+Because of the above, my view is that this solution is being back-doored in and just moves the ""technical debt"" from one sheet (the community and tool labs) to another that has even less capability. I am biased against that because the latter sheet (WMF Features Engineering) is my responsibility. This is just my view, I'm open for us coming to consensus on a solution for this bug, but what I have seen is not consensus.
+
+It is along these lines that, I asked to remove MassMessage from the deploy calendar when it was added to the deploy calendar without discussion from Features, Design, or Product last week. After discussion during that Friday meeting among the EPMs, I compromised to let it to go out on two test wikis, but not on mediawiki. Nobody made the case that it should go out on mediawiki. I demurred because no person at the WMF, including me as Director of Features Engineering, should fiat a decision when unaware of the status of discussions involved.
+
+But let frank: if this had been a WMF employee writing this extension, it wouldn't have made it to even the test wikis by a country mile. In fact, a lot of extensions have been written by employees and either have extensive discussion, review, and buy-in (e.g. GuidedTours), or have not been deployed (e.g. Etherpad, the org chart, BetaFeatures) even though much more work has been done on them.
+
+I also don't like that WMF resources in Platform and Design are being spent to review something that has had no adequate discussion over in the annual plan, in anyone's 20% time, in any cross-team discussion, or public discussion on wikitech-l (There was a last minute thread in the Design list, I am not on the design list, nor should I be, and the Creative Director is new and the team is just trying to get their sea legs and some consideration to that needs to be done here). Furthermore, after further discussion, nearly all of Product felt I should not have compromised earlier because the following situation might occur: Having gotten it onto ""the cluster"" people would then move to back-door it into deployment on the basis that it's already on the cluster. Their prediction is occurring right now. This is a bogus argument because nobody agreed this should be on the cluster, it's just that nobody has reviewed it in a thorough enough manner to shout ""NO!""
+
+If necessary, I'm going to shout ""NO!"" at this moment.
+
+Having said that, there is the larger issue of bug 35306 which has been sitting there unsolved for a while as well as the smaller issue of the month's work Legoktm and MZMcBride have already put into Bug 52723 and [[mw:Extension:MassMessage]] possibly going to waste if I keep blocking it. Besides, MZ is sitting there trying to hold everything up on his own shoulders with EdwardsBot, and we all know it.
+
+…
+
+Let me address the functionality overlap with Echo:
+
+LanguageEngineering built their own parallel message/notification system before Echo that lives on Meta today. They commit to supporting their own parallel message/notification system, and I'm okay with it living outside Echo (where it currently does), but there is an understanding that they've basically committed to that work with no support from Features for the duration that it does live outside Echo.
+
+In those lines, I'm glad that Platform has helped out here, but unless Platform is committing to support MassMessage indefinitely into the future and not just provide one-time security and deploy assistance, I'm not okay with them adding to Features work even though they've been super helpful to MZMcBride and Legoktm. If Dan Garry is willing to commit Platform to support MassMessage, I'll think the same precedent we've done with LE applies here.
+
+Furthermore, before *in-echo, outside-echo, use-echo) for a solution to be bug 35306, it needs to actually exhibit product discipline. The WMF gets panned for having a ""agile processes"" but not actually doing so, but we do have some process and we need to at least apply the same product discipline that we apply everywhere else to this bug.
+
+For example, features in MassMessage and EdwardsBot need to be addressed in a Must-Have, Should-Have, Could-Have, Won't-Have (MoSCoW) framework. Features like ""mass delivery from a list"" are probably a Must-Have; features like ""cross-wiki notification"" are probably a should-have, other features like ""public over private notifications"", ""page-centric over user-centric"" or ""longer stream notifications"" are either not a must-have or could have or are should-haves to  be done outside Echo by a different service (bot) using the Echo API or some extension thereof. All that is a product issue, and I nor anyone in my team is in product. Those decisions should be done in discussion with the Product team and they should not be disintermediated from it, which they have been.
+
+I understand that many people would like to see a solution to Bug 35306 would be great to have. I'd like to see a better Signpost notification system and a more generalized solution for newsletter delivery also! I'd also like a pony. But we have already committed resources and continue to commit resources without discussion from the people (Product Design, not Features Engineering) who have been tasked with this responsibility and are very good at these sort of thing. I hope everyone participating on this bug can see that dropping this bomb on a newly hired associate product manager is simply not cool on so many levels.
+
+…
+
+Here is my suggestion:
+
+(This is thinking, not a directive so don't think of this as definitive or final, I'm seeking consensus here.)
+
+First, bug 35306 is a long-standing request. I think it's important we get headway on this, but I hope others will be understanding if it doesn't happen immediately, so long as there is a commitment for this to happen.
+
+(For perspective, Flow was first proposed years ago, and was added to the annual plan almost two years ago before their first actual development sprint was completed (end of this week!). Echo was first deployed almost 8 months ago and is still not out on all the wikis. BetaFeatures has been in discussion for months and is still not deployed, nor is the commitment to maintain inside Features and that has caused a lot of issues. Fixing things right right takes time because consensus takes time and open discussion.)
+
+There is an RfP for student developer time for legoktm for things like this (Finding a solution for Bug 35306 but not [[mw:Extension:MassMessage]] because MassMessage would not be deployed if it was my own engineer). Benny Situ has been spending all his time supporting [[mw:Extension:Echo]] when he should balancing [[mw:Flow]] development time into Echo bug fixes and needs to spend at least one sprint (two weeks) solely getting up to speed on Flow before doing enhancements for [[wm:Echo]]. Furthermore, Echo is not deployed everywhere yet and is still rolling out (though I've been pushing up the timetable on this as I feel we're too slow here), so it can't reach the places that EdwardsBot cat.
+
+After the above happen, I'd like Benny and Kunal to work together to add some of the functionality of EdwardsBot into Echo for mass message delivery. Because of this, I'm moving bug 35306 into Echo as an enhancement and raising it's priority.
+
+In the meantime I'll be OK with leaving MassMessage on test and test2 wikis because the alternative would be to remove it from the cluster entirely. The experiences and code Kunal derives by that can inform the enhancement to Echo, as well as things it already does that find themselves outside Echo (Echo does not and should not post to talk pages). So I figure two stages:
+
+1) wait for some things to happen: legoktm to get an RfP, Echo to be on all wikis, and Benny to do an entire Flow only sprint and balancing his time more effectively wrt Echo.
+2) MoSCoW other features of MassMessage/EdwardsBot for integration into Echo
+3) Enhance and deploy a first pass to Echo to allow some sort of mass notification from a wiki list
+4) Some sort of cross wiki notification enhancement (requires a design pass)
+5) Discuss how to implement must-have or should-have features of EdwardsBot that can't live in Echo (permanent log of events)?
+6) Add those to plan and be done.
+
+The above can occur independently or in parallel to the above. If Product thinks it cool to commit Platform's constrained engineering resources to deploying and supporting MassMessage Extension forever and use it to take advantage of Echo when the features roll out in some undefined future, consider this thinking moot or at least orthogonal to MassMessage. IMO, it is bad enough that something important like BetaFeatures is without a home, but my answer from Features is ""No"" for MassMessage. If this was my own engineer, I'd raise hell with them for this and yell at their Product Manager for not being a good steward of Platform's time.",1380828181,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"As someone that has discussed the topic of mass notifications / announcements / newsletters with many people I agree with the approach being proposed here:
+
+* MassMessage solves a problem here and now by deprecating EdwardsBotwith a better solution.
+
+* There is a possibility to integrate an Echo plugin to MM in the future, but this is no blocker for a deployment to Wikimedia wikis now.
+
+* There are other future possibilities around announcements / newsletters in the future, in the lines proposed at https://www.mediawiki.org/wiki/Extension:Newsletter#Wishlist and MassMessages might or might not be a good project to handle this, but again this is no obstacle for a deployment now.",1380730233,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #25)
+> There is some overlap with Echo with this. 
+In general, yes. Both extensions provide a 'notification' functionality, however there are some pretty big differences as well.
+
+1) Echo notifications for the most part are private; only you can see your Echo notifications. MM is designed so that everything (target list, message content) is fully public.
+
+2) Echo is centered around users, given that you can only send notifications to users. MM can send to basically any page, which is necessary for global message delivery (most messages are sent to village pumps, not users directly).
+
+3) Echo notifications are quick short messages that usually are just a link to something else. In many cases, EdwardsBot delivers the whole message to your talk page (example: <https://en.wikipedia.org/?diff=prev&oldid=565236352>). In this regard MM has been designed so that the end user receiving the message would not see any difference.
+
+(In reply to comment #25)
+> if we enable this extension we could always disable it should
+> Echo supersede it.
+
+I don't think merging MM into Echo is a good idea. Rather, MM should use Echo notifications instead of talk page ones if $wgMMUseEcho is enabled. Or something like that...",1380729349,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"There is some overlap with Echo with this. On the other hand, there are some things that this might be suited for, such as the delivery of the Wikipedia Signpost. It's my view that an in-built solution to replace EdwardsBot would be useful, and if we enable this extension we could always disable it should Echo supersede it.
+
+I'm CCing Fabrice Florin, the product manager for notifications, to see if he has any input.",1380726099,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #19)
+> Mostly, I brought this (deploying MassMessage) up in a Deployment updates
+> meeting, and there was some push back from a product view. In short:
+> ""shouldn't this functionality be built into something like Echo?"" So, I won't
+> go around them and deploy MassMessage everywhere until that conversation is
+> settled (for some value of ""settled"").
+
+I'm still awaiting feedback from Terry, Howie, or Fabrice on bug 35306 (I also e-mailed them yesterday with a pointer to the bug), however Lego pointed out to me that Echo doesn't currently support cross-wiki notifications, so Echo integration is probably completely off the table for now.
+
+I think a month of testing is sufficient for this extension, so I've tentatively scheduled a deployment to all Wikimedia wikis for the end of October (cf. <https://wikitech.wikimedia.org/w/index.php?diff=84903&oldid=84888#Near_term>). You know the calendar much better than me, though, so let me know if that's a particularly bad time for whatever reason.",1380680719,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #22)
+
+Hah! I just came here to write pretty much the same comment. Brilliant. Thank you, Lego.
+
+Testing is underway (cf. [[testwiki:Special:Log/massmessage]]) and feedback has started to come in (cf. [[m:Talk:MassMessage]]).",1380652159,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Some updates:
+
+MassMessage was successfully deployed to test and test2 today (thanks Reedy!). I did a few simple tests making sure everything worked fine (https://test.wikipedia.org/w/index.php?title=Special%3ALog&type=massmessage&user=Legoktm&page=&year=&month=-1&tagfilter=&hide_patrol_log=1&hide_review_log=1&hide_thanks_log=1)
+
+MZMcBride has sent out a message to people who currently use EdwardsBot on enwiki and meta asking them to test it on testwiki and provide feedback (https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Spam&oldid=5895864).
+
+We're still waiting on comments from Fabrice/Howie/Terry (bug 35306 comment 20).
+
+[[mw:Help:Extension:MassMessage]] has documentation on how an administrator would use the special page to send out a message. [[m:MassMessage]] has also been created.",1380607500,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"After a couple of updates, it all looks ok from the security side.",1380131839,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Err, I mean, after Chris S gives the all clear, security-review-wise: https://bugzilla.wikimedia.org/show_bug.cgi?id=52723#c16",1380044491,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #18)
+> (In reply to comment #17)
+> > There was a request to see if this extension would make sense as an
+> > improvement to Notifications/Echo. This discussion would probably be good to
+> > have with the WMF product team (maybe including Fabrice, Terry, and Howie).
+> 
+> This already took place at bug 35306.
+
+Right, so, I'm deferring judgement on that (and related) conversations to Terry C and Howie F right now. More on why below...
+
+> > I'll default to defer for now, until that conversation happens.
+> 
+> I don't know what this means. Can you clarify?
+
+Mostly, I brought this (deploying MassMessage) up in a Deployment updates meeting, and there was some push back from a product view. In short: ""shouldn't this functionality be built into something like Echo?"" So, I won't go around them and deploy MassMessage everywhere until that conversation is settled (for some value of ""settled"").
+
+Now, what we should do is deploy MassMessage somewhere so you/others can test its functionality on a WMF production-like site. Let's get this out to test2.wikipedia this Thursday. Filed bug 54518 for that.",1380044416,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #17)
+> There was a request to see if this extension would make sense as an
+> improvement to Notifications/Echo. This discussion would probably be good to
+> have with the WMF product team (maybe including Fabrice, Terry, and Howie).
+
+This already took place at bug 35306.
+
+> I'll default to defer for now, until that conversation happens.
+
+I don't know what this means. Can you clarify?",1379779756,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"There was a request to see if this extension would make sense as an improvement to Notifications/Echo. This discussion would probably be good to have with the WMF product team (maybe including Fabrice, Terry, and Howie).
+
+I'll default to defer for now, until that conversation happens.",1379703587,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Just an update, I'm still working on the review. There were a few bits that looked odd as I was testing, so I'd like to dig into those before giving the all clear. Should be able to get that finished on Monday.",1379649523,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"I just spent a few minutes talking with Chris who said he would be able to do a security review of the extension this week.
+
+Currently waiting for a few patches to be reviewed and then I'll send an email to wikitech-l.",1379462355,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #11)
+> (In reply to comment #9)
+> >> Not sure this is relevant as this extension isn't really user-facing, but if
+> >> you want to find someone to review the design, go for it.
+> > 
+> > Well, for some definition of user, right? It has sysop user facing UI. For a
+> > design review, the Design mailing list is a good place to start (and then
+> > ping until success).
+> 
+> Lego: please go ahead and e-mail the design mailing list (include a working
+> demo of the tool, of course). If they have constructive feedback, wonderful.
+> Otherwise, I don't consider this a blocker to deployment.
+> 
+
+Email sent to design list: http://lists.wikimedia.org/pipermail/design/2013-September/000923.html",1379461042,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,CC'ing Dan Garry (new Platform PM). No action needed Dan (yet ;) ). Just using this as a way to remind us to talk about this work and how you'll interface with it.,1379002862,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"The goal is to get this extension deployed (to phase 0 wikis) by the end of September. I'm not sure if this will be possible, but I've tentatively added it to the deployments calendar for September 30: <https://wikitech.wikimedia.org/w/index.php?diff=83188&oldid=83134#Near_term>.
+
+Lego: feel free to move the date into October if necessary.",1378777053,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #9)
+>> Not sure this is relevant as this extension isn't really user-facing, but if
+>> you want to find someone to review the design, go for it.
+> 
+> Well, for some definition of user, right? It has sysop user facing UI. For a
+> design review, the Design mailing list is a good place to start (and then
+> ping until success).
+
+Lego: please go ahead and e-mail the design mailing list (include a working demo of the tool, of course). If they have constructive feedback, wonderful. Otherwise, I don't consider this a blocker to deployment.
+
+>> Greg: how do we get this extension reviewed for architecture/performance and
+>> security?
+> 
+> First pass would be to send a note to wikitech-l asking for help.
+> Unfortunately, this week is a combined Tech Days and All Hands so WMF tech
+> staff will be slower to respond than normal, but I know you know who to ping
+> as needed (Aaron/Tim for arch, Chris for security).
+
+Lego: please go ahead and e-mail wikitech-l asking for a review once you're ready and you've done your best to ensure that the extension is in a reviewable state. Test rigorously!
+
+If you could cross-reference these two mailing list posts on this bug, that would be wonderful.
+
+> Well, if there are any userfacing bits (even for non-mortals), then it'd be
+> good to have a walk-through of how the extension is supposed to work/what the
+> process is. Think of it as a required bit of user documentation :)
+
+If you write docs about how to create one of these mythical screencasts, I'll consider it. In the meantime, over a decade of development has progressed without these being a requirement. We're not going to start with this extension. :-)
+
+>>> Community support: no?
+>> 
+>> Yes, plenty of it.
+> 
+> Awesome. I believe you, but would appreciate links to where discussion has
+> happened.
+
+This request is a blocker to bug 35306. It falls outside the requirement for community consensus as it's an obvious and uncontroversial enhancement request; it is replacing a non-production, largely unsupported tool (i.e., the Python script that currently powers [[m:Global message delivery]]); and it has limited exposure (only admins will have access by default, and even most admins won't use this tool... for now).
+
+Bug 35306 gives most of the background here, but it's probably reasonable for me to point out that many (if not most) global message deliveries are connected to Wikimedia Foundation staff. The targets lists at [[m:Global message delivery/Targets]] comprise hundreds (maybe thousands) of users who have signed up for various newsletters and other mailings, in addition to a number of distribution lists used by Wikimedia volunteers and staff (including technical announcements and other breaking changes announced to [[m:Distribution list/Global message delivery]]). You could consider this a third or fourth exemption to the community consensus guideline, if you'd like. ;-)",1378776753,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #9)
+> > 
+> > > Community support: no?
+> > 
+> > Yes, plenty of it.
+> 
+> Awesome. I believe you, but would appreciate links to where discussion has
+> happened.
+
+Long wanted feature to not have to have bots making tens/thousands of edits onwiki. Not sure a discussion par se would have happened.. (if one has, great)
+
+To users, it really doesn't matter where it comes from.",1378768971,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #8)
+> Thanks for writing out a checklist.
+
+:)
+
+> (In reply to comment #7)
+> > == TODO/Check list ==
+> > Extension page on mediawiki.org: yes
+> > Bugzilla component: yes
+> > Extension in Gerrit: yes
+> 
+> Right.
+> 
+> > Design Review: no
+> 
+> Not sure this is relevant as this extension isn't really user-facing, but if
+> you want to find someone to review the design, go for it.
+
+Well, for some definition of user, right? It has sysop user facing UI. For a design review, the Design mailing list is a good place to start (and then ping until success).
+
+> 
+> > Architecture/Performance Review: no
+> > Security Review: no
+> 
+> These are the two areas needed here.
+> 
+> Greg: how do we get this extension reviewed for architecture/performance and
+> security?
+
+First pass would be to send a note to wikitech-l asking for help. Unfortunately, this week is a combined Tech Days and All Hands so WMF tech staff will be slower to respond than normal, but I know you know who to ping as needed (Aaron/Tim for arch, Chris for security).
+
+> 
+> > Screencast (if applicable): no
+> 
+> Not sure what this is about. It seems irrelevant.
+
+Well, if there are any userfacing bits (even for non-mortals), then it'd be good to have a walk-through of how the extension is supposed to work/what the process is. Think of it as a required bit of user documentation :)
+
+> 
+> > Community support: no?
+> 
+> Yes, plenty of it.
+
+Awesome. I believe you, but would appreciate links to where discussion has happened.",1378768315,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Thanks for writing out a checklist.
+
+(In reply to comment #7)
+> == TODO/Check list ==
+> Extension page on mediawiki.org: yes
+> Bugzilla component: yes
+> Extension in Gerrit: yes
+
+Right.
+
+> Design Review: no
+
+Not sure this is relevant as this extension isn't really user-facing, but if you want to find someone to review the design, go for it.
+
+> Architecture/Performance Review: no
+> Security Review: no
+
+These are the two areas needed here.
+
+Greg: how do we get this extension reviewed for architecture/performance and security?
+
+> Screencast (if applicable): no
+
+Not sure what this is about. It seems irrelevant.
+
+> Community support: no?
+
+Yes, plenty of it.",1378423432,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"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: no
+Archeticecture/Performance Review: no
+Security Review: no
+Screencast (if applicable): no
+Community support: no?",1378415175,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #5)
+> Hi Legoktm, I see that http://www.mediawiki.org/wiki/Extension:MassMessage
+> exists but where is its bugtracker? See
+> https://www.mediawiki.org/wiki/Bug_management/Project_Maintainers#To_add_a_project_or_component
+
+Filed as bug 52730.",1376239786,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Hi Legoktm, I see that http://www.mediawiki.org/wiki/Extension:MassMessage exists but where is its bugtracker? See https://www.mediawiki.org/wiki/Bug_management/Project_Maintainers#To_add_a_project_or_component",1376238095,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #1)
+> (see [[meta:User talk:EdwardsBot/Archive 1#LQT compatibility]])
+The correct link is [[User talk:EdwardsBot/Archive 1#LQT compatibility]].",1376235918,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"For reference: <https://gerrit.wikimedia.org/r/#/q/project:mediawiki/extensions/MassMessage+status:open,n,z>.",1376229430,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"(In reply to comment #1)
+> Does it have the same problem as the global message delivery system on wikis
+> which use LiquidThreads?
+> (see [[meta:User talk:EdwardsBot/Archive 1#LQT compatibility]])
+
+The real bug is that those wikis are still using LiquidThreads. :-)
+
+But if you want to add a dependency bug about MassMessage supporting LiquidThreads, it shouldn't be too painful to code.",1376228263,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Review and deploy MassMessage extension to Wikimedia wikis,"Does it have the same problem as the global message delivery system on wikis which use LiquidThreads?
+(see [[meta:User talk:EdwardsBot/Archive 1#LQT compatibility]])",1376224547,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ymnidmb2ap2g4se52stx,task_subcomment,NA
+Enable VisualEditor on se.wikimedia.org,"The Swedish chapter would like to get the VisualEditor enabled on their wiki at se.wikimedia.org. 
+
+Poll here: http://se.wikimedia.org/wiki/Tråd:Wikimedia:Bybrunnen/VisualEditor_och_Notifications
+
+/Jan
+CEO
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1376178900,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-sflxt54msumq4ifieh2r,task_description,resolved
+Enable VisualEditor on se.wikimedia.org,"This is now live - you can opt in to test VisualEditor using the Beta Features link in your personal tools at the top of the page, or through the Preferences link in the ""Beta Features"" tab.
+
+If there are any issues, please shout!",1386022170,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sflxt54msumq4ifieh2r,task_subcomment,NA
+Enable VisualEditor on se.wikimedia.org,"Change 97714 merged by jenkins-bot:
+Enable VisualEditor as opt-in on Swedish Wikimedia
+
+https://gerrit.wikimedia.org/r/97714",1386021563,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sflxt54msumq4ifieh2r,task_subcomment,NA
+Enable VisualEditor on se.wikimedia.org,"Change 97714 had a related patch set uploaded by Jforrester:
+Enable VisualEditor as opt-in on Swedish Wikimedia
+
+https://gerrit.wikimedia.org/r/97714",1385464058,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sflxt54msumq4ifieh2r,task_subcomment,NA
+"VisualEditor: In Firefox's High Contrast mode, buttons on the toolbar are unidentifiable","en.wp user Cryptic C62 reports that using Firefox with Windows Vista ""high contrast"" mode renders VE entirely unusable:
+
+""Using Windows Vista, press Shift + Alt + Print Screen to activate ""high contrast"" mode. Open VE in Firefox. Weep uncontrollably (see screenshot).""
+
+Screenshot: [[File:VE High Contrast.jpg]]
+
+
+It is worth noting that, when using the high contrast extension for Chrome, the interface is fully visible in every setting. Hooray!
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1376068440,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gysdgpu4licxwvxxosg3,task_description,invalid
+"VisualEditor: In Firefox's High Contrast mode, buttons on the toolbar are unidentifiable",id call this an OS bug...,1457161240,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-gysdgpu4licxwvxxosg3,task_subcomment,NA
+"VisualEditor: In Firefox's High Contrast mode, buttons on the toolbar are unidentifiable","Visual Editor in Windows 7 High Contrast Mode in Firefox 44 {F3524565}
+
+Google.com in Microsoft's very own Internet Explorer 11
+{F3524580}
+
+Microsoft.com in IE 11 at High Contrast Mode on Windows 7 
+{F3524584}
+
+Given those examples I highly question how many people **are actually able to use //any website with this functionality at all//** in its current implementation?! Seems poorly conceived. 
+@Jdforrester-WMF  If nobody is opposing that in a reasonable time frame (30 days?) I'd recommend closing this task as ""invalid"".",1457147578,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-gysdgpu4licxwvxxosg3,task_subcomment,NA
+VisualEditor: Welcome dialog doesn't expand/scroll to fit large fonts,"When a user has a larger font size than defualt, or a non-default font then the welcome dialog (the one controlled by the ve-beta-welcome-dialog cookie) doesn't expand or scroll to accommodate the extended length of the message and the text is cropped.
+
+Screenshot at [[File:WARNINGforVE.png]]
+
+This might be another example of bug 52602 but I'm not certain.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52602
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51755
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50885",1376041620,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7ix4hqmkcelueduz7hux,task_description,resolved
+VisualEditor: Welcome dialog doesn't expand/scroll to fit large fonts,"Change 82466 merged by jenkins-bot:
+Improve welcome dialog support for large fonts
+
+https://gerrit.wikimedia.org/r/82466",1378335727,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7ix4hqmkcelueduz7hux,task_subcomment,NA
+VisualEditor: Welcome dialog doesn't expand/scroll to fit large fonts,"Change 82466 had a related patch set uploaded by Trevor Parscal:
+Improve welcome dialog support for large fonts
+
+https://gerrit.wikimedia.org/r/82466",1378241684,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7ix4hqmkcelueduz7hux,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"en.wp user Redrose64 reports:
+With this edit: https://en.wikipedia.org/w/index.php?title=Paisley_Gilmour_Street_railway_station&diff=prev&oldid=567709873 ""the {{-}} was moved from the bottom of a section into a heading, effectively yielding the HTML <h3><span class=""mw-headline"" id=""2013"">2013<br style=""clear:both;"" /></span>[edit]</h3> ""
+
+I can reproduce that on that article by:
+1. Deleting with backspace the header ""Post-2008"" (and nothing else)
+2. Typing ""2013""
+
+I can't reproduce it in my sandbox with {{-}} (or {{clear}}) before a header and then changing the header.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375989720,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-cwptueorc4rxrgvc5shh,task_description,resolved
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1376609977,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"Because Subbu and Gabriel asked: this is a VE bug, not a Parsoid bug. Unfortunately it's not very clear where the {{-}} template is exactly because it doesn't really produce visible output. So pressing backspace or delete can cause the {{-}} to move to a different paragraph, which may be styled as a heading or restyled by the user to be a heading. And you don't really notice that you're doing this because it's not visible.",1376609124,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"Moving to VisualEditor:
+
+[16:19] <RoanKattouw> That looks like a VE issue
+[16:20] <RoanKattouw> It's probably because {{-}} doesn't produce any visible output (it outputs a <br> with clear: both;)
+[16:20] <RoanKattouw> And so people don't notice when their backspace or delete presses cause the {{-}} to be moved into a different paragraph which they then mark up as a heading",1376609113,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"I reproduced it - not precisely, but close enough.
+
+I pretended I was a brand new editor, and rather than changing the heading I created a new one, above the old. Then I deleted the old and applied formatting to the new word I typed.
+
+This rendered this: http://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29%2Fsandbox&diff=568643085&oldid=568642989
+
+The template moved, but in front of rather than behind the word.
+
+I'm using Chrome.
+
+I tried it again on Firefox, and caught the template again:
+https://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29%2Fsandbox&diff=568643930&oldid=568643677
+
+I guess that the IP editor may have positioned his cursor slightly differently, but that seems to be the behavior that led to the issue. It seems like potentially an easy decision to make.",1376567370,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"I agree with your recommendation, Chris.
+
+I think this was a valid bug, but it might have been specific to a particular set of conditions at the time of the bug (cached HTML, what the user was doing, the state that VE was in and the HTML it generated, source wikitext) which we are having a hard time reproducing now.  So, I am going to close this bug for now and we can reopen this or a new one if a similar error shows up.",1376407275,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"Having tried again, I still can't reproduce it. The original edit that caused this was by an anonymous user who hasn't edited since, so we're unlikely to get any more information from them.
+
+Should this be closed (WORKSFORME?) and then just reopened if it happens again in future?",1376388286,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"After about 5 minutes trying I can't reproduce this now on either the present or old revisions of that page. I haven't tried again in my sandbox but given the other findings I wouldn't expect it to.
+
+The only change is I'm now running Firefox 23 rather than the 22 I was running when I reported this (and I don't know how to keep separate versions of the same program available at the same time, sorry)",1376093134,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Template {{-}} can be moved into following heading because it doesn't render,"Unfortunately, I am having a hard time reproducing the bug now.  And, as you noted, I am not able to copy it to my sandbox and reproduce it either.  This may have been some glitch in how VE might have modified the DOM on editing there.
+
+Can you verify that you can reproduce the error on the latest version or that oldid?  I even added a newline space back in case that matters (since that is what was present in the oldid).",1376083679,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cwptueorc4rxrgvc5shh,task_subcomment,NA
+VisualEditor: Thai Wikipedia's coordinates template displays badly in tables,"During the edit
+
+This has been noted on the Thai wikipedia.  
+See screenshots for how it looks.  
+
+Basically, in edit mode, the sixth column of this table, containing Goehack coordinate links, displays as an HTML string in edit mode. Not only very messy, but it pushes the following columns off the page.
+
+Appears to save normally.
+
+Replicated on current FF, Chrome, on Mac OS and Ubuntu
+
+Page on Thai.wiki: https://th.wikipedia.org/wiki/%E0%B8%A3%E0%B8%B2%E0%B8%A2%E0%B8%8A%E0%B8%B7%E0%B9%88%E0%B8%AD%E0%B9%82%E0%B8%9A%E0%B8%A3%E0%B8%B2%E0%B8%93%E0%B8%AA%E0%B8%96%E0%B8%B2%E0%B8%99%E0%B9%83%E0%B8%99%E0%B8%81%E0%B8%A3%E0%B8%B8%E0%B8%87%E0%B9%80%E0%B8%97%E0%B8%9E%E0%B8%A1%E0%B8%AB%E0%B8%B2%E0%B8%99%E0%B8%84%E0%B8%A3_(%E0%B9%80%E0%B8%82%E0%B8%95%E0%B8%9E%E0%B8%A3%E0%B8%B0%E0%B8%99%E0%B8%84%E0%B8%A3_%E0%B8%9B%E0%B9%89%E0%B8%AD%E0%B8%A1%E0%B8%9B%E0%B8%A3%E0%B8%B2%E0%B8%9A%E0%B8%A8%E0%B8%B1%E0%B8%95%E0%B8%A3%E0%B8%B9%E0%B8%9E%E0%B9%88%E0%B8%B2%E0%B8%A2_%E0%B9%81%E0%B8%A5%E0%B8%B0%E0%B8%AA%E0%B8%B1%E0%B8%A1%E0%B8%9E%E0%B8%B1%E0%B8%99%E0%B8%98%E0%B8%A7%E0%B8%87%E0%B8%A8%E0%B9%8C)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11613}",1375975140,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-blwhpbgbhchhdkulxgr2,task_description,resolved
+VisualEditor: Thai Wikipedia's coordinates template displays badly in tables,"Not sure when, but this is now fixed, probably because of Ed's work on template wrapping.",1414165021,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-blwhpbgbhchhdkulxgr2,task_subcomment,NA
+VisualEditor: Transclusion dialog should validate template parameter values using TemplateData information,"If a parameter has '""type"": ""number""', VisualEditor should not allow the user to insert other kind of values. Alternativelly, it could just warn the user but still allow a value of the wrong type to be inserted.
+
+This should not be restricted just to the ""number"" type. Other types would also benefity from some validation (e.g., if at some point we have a type ""string/image-name"", VE should check if the user provided the name of an existing image).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52652",1375969680,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-c65b3wdhn2onui4dnvcj,task_description,open
+VisualEditor: Transclusion dialog should validate template parameter values using TemplateData information,"I don't agree with restricting users from only entering content as the hinting suggests (the hinting may be wrong, or may restrict users too much) - this is the same reason why we allow users to add un-hinted parameters.
+
+However, yes, we should definitely add this missing feature in soon.",1376115954,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c65b3wdhn2onui4dnvcj,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","If you want to add a ""template"" that is not in the template namespace, for example: ""User:UBX""; VE will make an API request like: ""GET https://en.wikipedia.org/w/api.php?format=json&action=templatedata&titles=Template%3AUser%3AUBX"".
+
+It should automatically detect that ""User:"" is a valid namespace, and not add the ""Template:"" prefix.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375875780,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_description,resolved
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","Change 140875 merged by jenkins-bot:
+Handle transcluding templates outside of the template namespace properly
+
+https://gerrit.wikimedia.org/r/140875",1404157149,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","What Matt pointed out is handled correctly except for main namespace titles (e.g. :Foo), where the input widget trips over itself and you always end up with Template:Foo.",1403824833,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","The commit says the purpose of the colon is ""to create a link to something that would normally be included as a File/Category"".
+
+That's true, but it also plays a role in transclusion.  It's used to transclude things in the main namespace.
+
+E.g. on English Wikipedia {{Main Page}} transcludes https://en.wikipedia.org/wiki/Template:Main_Page , whereas {{:Main Page}} transcludes https://en.wikipedia.org/wiki/Main_Page
+
+For other namespaces (e.g. {{Wikipedia:Community Portal}} / {{:Wikipedia:Community Portal}} ), it works either way.
+
+Full demo: https://en.wikipedia.org/w/index.php?title=User:Superm401/Sandbox&oldid=614564227
+
+This may be handled somewhere (e.g. Parsoid), but it needs to be tested.",1403823029,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","This was also hiding another problem (templates outside of the Template namespace ended up prefixed with ':', breaking them). This patch should fix that too (and hopefully not break any other link suggesting things).",1403224037,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","Change 140875 had a related patch set uploaded by Alex Monk:
+Handle transcluding templates outside of the template namespace properly
+
+https://gerrit.wikimedia.org/r/140875",1403223913,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided","(Okay, it's not as simple as I was hoping)",1403222822,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+"VisualEditor: When getting TemplateData, VE automatically adds ""Template:"" even if another namespace is provided",It looks like we can just pass the title to mw.Title.newFromText with mw.config.get( 'wgNamespaceIds' ).template as the (default) namespace.,1403221498,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-oqp2lj4ng622u7fiwxp2,task_subcomment,NA
+VisualEditor: Get rid of IVStore check in toDomElements in GCNode subclasses,"Some toDomElements functions reach into the store, but they shouldn't and the check is redundant.
+",1375853340,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gx6k3eekkero53hloidz,task_description,open
+VisualEditor: Add keyboard shortcut for code element/style,"A keyboard shortcut for code would be helpful, particularly for MediaWiki.org.  We'll need to think of what to use.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375852380,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-gf6k4fuodiscgbllfhpa,task_description,resolved
+VisualEditor: Add keyboard shortcut for code element/style,Verified the fix in production,1411682734,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"Change 160174 merged by jenkins-bot:
+Add keyboard shortcuts for strikethrough and code annotations
+
+https://gerrit.wikimedia.org/r/160174",1410823312,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"Change 160174 had a related patch set uploaded by Jforrester:
+Add keyboard shortcuts for strikethrough and code annotations
+
+https://gerrit.wikimedia.org/r/160174",1410570243,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"**fred** wrote:
+
+When is this planned? I was about to write that enhancement proposition as well when I saw this ticket.
+
+My personal preference would be to have a shortcut near the ctrl tab on the left of the keyboard.",1385041001,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"(In reply to comment #1)
+> One possiblity is Ctrl-{.  It takes three key strokes on some keyboards, but
+> it's memorable as long as it matches the toolbar icon, and not that hard to
+> type.
+
+We're almost certainly not going to keep '{}' for code (especially as there's <code> and <syntaxhighlight> that need to be distinguishable), but it's a possibility.",1375865906,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for code element/style,"One possiblity is Ctrl-{.  It takes three key strokes on some keyboards, but it's memorable as long as it matches the toolbar icon, and not that hard to type.",1375861847,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-gf6k4fuodiscgbllfhpa,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Some templates use numbered arguments (see for example http://en.wikipedia.org/wiki/Module:Citation/CS1/Whitelist in the numbered_arguments list). For example, you can use author1, author2, ... (no limit).
+
+Currently, there's no way to define such parameters in TemplateData, and the VE interface is not also optimal for them.
+
+Would it be possible to handle numbered arguments in TemplateData: a parameter named author# would define a numbered parameter named author with a numerical suffix. It should be possible to define lower bound (1 by default) and upper bound (no limit by default).
+
+Then VE should handle them accordingly: only propose the first parameter available in the list of parameters than can be added.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+{T53740}",1375805280,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_description,open
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,We are currently only passively maintaining template wizard. See https://meta.wikimedia.org/wiki/Community_Tech/Maintenance for more.,1706108119,PHID-USER-hc3d7yz5cqmafn4osucd,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"I’ll add #community-tech team to the task as maintainers of TemplateWizard, maybe they have ideas :)",1705603244,PHID-USER-tuy2dac6pfhknbtqmqgh,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"> If you don’t display `author-link3` until I filled `author-link2`, I can’t […]
+
+That's a great example, thanks! Sounds like an argument for the {key +} button.
+
+> templates where a trailing “1” doesn’t denote a sequence, but a year, a code (e.g. ISO 639-1) […]
+
+True, these might behave odd. We can't avoid this entirely but limit the effect by using a clever regex like `/\p{L}[\p{P}\p{Z}]*1$/u`. This will not pick up the examples you listed.
+
+> MediaWiki message-style `editor$1-last` […]
+
+Either that or `{{{1}}}` to reuse a pattern users are familiar with. However, this can't replace the current parameter name for the same backwards-compatibility reason as above but must be part of the new syntax:
+```lang=JSON
+""author1"": { ""sequence"": { ""name"": ""author$1"", ""from"": ""1"", ""to"": ""5"" } }
+```
+
+There is also another very common special case that goes like `author`, `author2`, `author3`, and so on without the `1`. Luckily this is easy to solve with the proposed syntax:
+```lang=JSON
+""author"": {},
+""author2"": { ""sequence"": { ""name"": ""author$1"", ""from"": ""2"", ""to"": ""5"" } }
+```",1669128401,PHID-USER-u6ycqhfpa3k4yvlpxjt2,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,">>! In T54582#8408107, @Tacsipacsi wrote:
+> I think there are still a lot of templates that don’t use Lua and thus support exactly as many parameters as documented. They probably don’t show error messages if unknown parameters are used, either, since that would also require Lua. This means that the extra parameters would simply not appear – which doesn’t cause visual breakage, but it’s also hard for the editors to notice. What does Citoid do now if there are more authors/whatever data than what the template – according to TemplateData – supports?
+
+Right now it silently just doesn't add the authors. If there's template data for 20, it'll add 20 and then stop. Unless it's a collapsed param, and then it concatenates them all together. So right now the results are actually better using a collapsed param because you get all the authors. 
+
+A lot of the non Lua templates are configured to use collapsed params, i.e. they have just one author field. In that case, all the authors are concatenated and make it into the template. I.e. this is the de wiki case. It'd only be non-lua templates that are also configured with citoid to use separate fields. 
+
+There's a related wishlist item for this: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Citations#Preventing_VE_from_silently_omitting_co-authors
+
+There's a suggestion to using display-authors but coming up with a system to do that is even less fleshed out in terms of how we'd decide that. I'd rather just actually add the author. 
+
+There's also the option of producing two citations, one with and one without for the user to choose.
+
+Funny edgecases for my proposed hack - a param that looks like isbn2, might accidentally produce isbn3 and isbn4 depending on how the data is configured. 
+
+",1669116447,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"To allow linking author3 without having to link the previous ones, the field author-link3 could appear when you FOCUS in author-link2, and author-link2 when you focus in author-link1, etc
+
+This would also make it more obvious to users how to access collapsed parameters.",1674485033,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Tho allow linking author3 without having to link the previous ones, the field author-link3 could appear when you FOCUS in author-link2, and author-link2 when you focus in author-link1, etc
+
+This would also make it more obvious to users how to access collapsed parameters.",1669084905,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Regarding the problem with point 1, the field author-link3 may appear when you FOCUS in author-link2, and author-link2 when you focus in author-link1, etc
+
+This would allow to link author3 without having to link the previous ones, and would also make it more obvious to users how to access collapsed parameters.",1669083437,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,">>! In T54582#8409117, @thiemowmde wrote:
+> 1. Collapse numbered parameters in VisualEditor. For example, when you start with an empty template you see only `author1`. The moment `author1` does have a value `author2` appears. And so on. But stop when the next number is not documented.
+>  * We can do this in VisualEditor without touching TemplateData.
+>  * The only thing users need to do is to make sure all possible numbers are documented.
+>  * This doesn't solve the situation where the number is unlimited, but allows for a workaround. Users just need to document //a lot// of numbers, e.g. `author1` to `author25`.
+This may not work in all cases. For example, [[https://en.wikipedia.org/wiki/Template:Cite_web|en:Template:Cite web]] have several parameters for providing authors, but to keep the example simple, let’s concentrate on the three that are included in the vertical copy sample: `firstN`, `lastN` and `author-linkN`. If only the first and third author have articles, I’d like to include the following:
+```
+{{cite web |first1=John |last1=Doe |author-link1=John Doe |first2=Jane |last2=Doe |first3=Jimmy |last3=Wales |author-link3=Jimmy Wales |… }}
+```
+If you don’t display `author-link3` until I filled `author-link2`, I can’t link to Jimbo’s article without adding a red link to Jane Doe’s article, which should not be done according to the documentation.
+
+> 2. Ask users to document an unlimited number of parameters by only documenting the first one, e.g. `author1`, but nothing else. We can use this special case to distinguish the two unlimited vs. limited scenarios.
+I have no actual example at hand, but I’m pretty sure there are templates where a trailing “1” doesn’t denote a sequence, but a year, a code (e.g. ISO 639-1), and so on.
+
+> 3. Come up with some magic syntax for numbered parameters, e.g. `""author[1-9]""` means only 9 parameters exist and `""author[1-]""` means it's unlimited.
+>  * This allows to use other number systems, e.g. Hebrew `author[א-ט‎]`.
+>  * Biggest problem with an approach like this is that it's entirely incompatible with existing software that doesn't understand the feature.
+Also, we’d need to be very careful what the syntax is, since `{{{author[1-9]}}` is for example a legal parameter name. Even `{{{a{{!}}b}}}` is legal, so pipes are neither something we can freely play with…
+
+> 4. Add a flag that does the same, e.g. `""author1"": { ""sequence"": { ""name"": ""author"", ""from"": ""1"", ""to"": ""5"" } }`. Use `""from"": ""1"", ""to"": ""1000""` to make it effectively ""unlimited"".
+>  * This can be made backwards-compatible. Users can still document `author1` to `author5` if they want. They just need to copy the sequence name to all of them, e.g. `""author2"": { ""sequence"": { ""name"": ""author"" } }`. Parameters with the same sequence are considered one by software that understands the feature.
+I like this the best. However, the counter doesn’t need to be at the end (see `editor2-last` in {{Cite web}}), so we need a syntax to indicate where the number goes. For example, it could be a printf-style `editor%d-last` (with the usual `%%` escape if the parameter name literally contains `%d`), or the MediaWiki message-style `editor$1-last` (what’s the escape here?). Also, it needs to accept not only ASCII digits, but anything that’s sequential (non-ASCII numbers, maybe even letters).
+
+> 5. Somehow make use of the unused `set` feature.
+According to the [[https://www.mediawiki.org/wiki/Extension:TemplateData|documentation]], a set is “a group of parameters that should be used together” – this doesn’t fit this use case, since `author1` can be used without `author42`.",1669065650,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"#wmde-techwish here. Our #wmde-templates-focusarea last year focused on #TemplateData and the #VisualEditor template dialog. I'm aware of two situations we need to consider here:
+1. Non-Lua templates support exactly as many parameters as documented, as @Tacsipacsi explained above. For example, there is `author1` to `author9`, but there it ends. This causes a few problems:
+ * It's a little tedious to document this.
+ * Both #VisualEditor and #TemplateWizard get messy very fast the more such parameters exist. Note that having more than one is the norm, not the exception. Here is a [simple example](https://en.wikipedia.org/wiki/Template:Singles).
+ * The person writing the documentation might decide to stop earlier and document only e.g. `author1` to `author5` exactly to avoid the problem above. `author6` ff. will still work, but can only be entered in wikitext or with the ""add undocumented parameter"" feature. Unfortunately this creates the next problem: `author6` will be listed at the very end, not after `author5`.
+2. Lua-based templates can support an effectively unlimited number of such parameters. The currently only way to document this is to document a limited number, e.g. `author1` to `author5`. This creates almost the same problems:
+ * The documentation must stop at an arbitrary number. Typically this will not be `author1` but e.g. `author5` or `author9`.
+ * This is tedious, as above.
+ * VisualEditor and such always show all of the documented parameters.
+3. Because of all the problems above and thanks to the power of Lua users create more and more templates that accept multiple comma-separated values in a single parameter.
+ * This creates effectively a custom parameter type with a custom syntax (namely being comma-separated).
+ * TemplateData has no way to document this either. I mean, other than describing it to the user. But not in a machine-readable way.
+
+A relevant consequence of all this is that we don't have a way to distinguish the first two situations when both are documented as `author1` to `author5`.
+
+What we can do, in my opinion:
+1. Collapse numbered parameters in VisualEditor. For example, when you start with an empty template you see only `author1`. The moment `author1` does have a value `author2` appears. And so on. But stop when the next number is not documented.
+ * We can do this in VisualEditor without touching TemplateData.
+ * The only thing users need to do is to make sure all possible numbers are documented.
+ * This doesn't solve the situation where the number is unlimited, but allows for a workaround. Users just need to document //a lot// of numbers, e.g. `author1` to `author25`.
+2. Ask users to document an unlimited number of parameters by only documenting the first one, e.g. `author1`, but nothing else. We can use this special case to distinguish the two unlimited vs. limited scenarios.
+3. Come up with some magic syntax for numbered parameters, e.g. `""author[1-9]""` means only 9 parameters exist and `""author[1-]""` means it's unlimited.
+ * This allows to use other number systems, e.g. Hebrew `author[א-ט‎]`.
+ * Biggest problem with an approach like this is that it's entirely incompatible with existing software that doesn't understand the feature.
+4. Add a flag that does the same, e.g. `""author1"": { ""sequence"": { ""name"": ""author"", ""from"": ""1"", ""to"": ""5"" } }`. Use `""from"": ""1"", ""to"": ""1000""` to make it effectively ""unlimited"".
+ * This can be made backwards-compatible. Users can still document `author1` to `author5` if they want. They just need to copy the sequence name to all of them, e.g. `""author2"": { ""sequence"": { ""name"": ""author"" } }`. Parameters with the same sequence are considered one by software that understands the feature.
+5. Somehow make use of the unused `set` feature.
+6. Just give the user a {key +} button at the end of numbered parameters, no matter how it's documented in TemplateData. It acts very similar to the ""add undocumented parameter"" feature but makes sure the order is consistent.
+6. …?
+
+I would like to avoid presenting an extra empty parameter at the end of every sequence of numbered parameters when the documentation explicitly says it doesn't exist, or we just don't know.",1669035722,PHID-USER-u6ycqhfpa3k4yvlpxjt2,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"#wmde-techwish here. Our #wmde-templates-focusarea last year focused on #TemplateData and the #VisualEditor template dialog. I'm aware of two situations we need to consider here:
+1. Non-Lua templates support exactly as many parameters as documented, as @Tacsipacsi explained above. For example, there is `author1` to `author9`, but there it ends. This causes a few problems:
+ * It's a little tedious to document this.
+ * Both #VisualEditor and #TemplateWizard get messy very fast the more such parameters exist. Note that having more than one is the norm, not the exception. Here is a [simple example](https://en.wikipedia.org/wiki/Template:Singles).
+ * The person writing the documentation might decide to stop earlier and document only e.g. `author1` to `author5` exactly to avoid the problem above. `author6` ff. will still work, but can only be entered in wikitext or with the ""add undocumented parameter"" feature. Unfortunately this creates the next problem: `author6` will be listed at the very end, not after `author5`.
+2. Lua-based templates can support an effectively unlimited number of such parameters. The currently only way to document this is to document a limited number, e.g. `author1` to `author5`. This creates almost the same problems:
+ * The documentation must stop at an arbitrary number. Typically this will not be `author1` but e.g. `author5` or `author9`.
+ * This is tedious, as above.
+ * VisualEditor and such always show all of the documented parameters.
+3. Because of all the problems above and thanks to the power of Lua users create more and more templates that accept multiple comma-separated values in a single parameter.
+ * This creates effectively a custom parameter type with a custom syntax (namely being comma-separated).
+ * TemplateData has no way to document this either. I mean, other than describing it to the user. But not in a machine-readable way.
+
+A relevant consequence of all this is that we don't have a way to distinguish the first two situations when both are documented as `author1` to `author5`.
+
+What we can do, in my opinion:
+1. Collapse numbered parameters in VisualEditor. For example, when you start with an empty template you see only `author1`. The moment `author1` does have a value `author2` appears. And so on. But stop when the next number is not documented.
+ * We can do this in VisualEditor without touching TemplateData.
+ * The only thing users need to do is to make sure all possible numbers are documented.
+ * This doesn't solve the situation where the number is unlimited, but allows for a workaround. Users just need to document //a lot// of numbers, e.g. `author1` to `author25`.
+2. Ask users to document an unlimited number of parameters by only documenting the first one, e.g. `author1`, but nothing else. We can use this special case to distinguish the two unlimited vs. limited scenarios.
+3. Come up with some magic syntax for numbered parameters, e.g. `""author[1-9]""` means only 9 parameters exist and `""author[1-]""` means it's unlimited.
+ * This allows to use other number systems, e.g. Hebrew `author[א-ט‎]`.
+ * Biggest problem with an approach like this is that it's entirely incompatible with existing software that doesn't understand the feature.
+4. Add a flag that does the same, e.g. `""author1"": { ""sequence"": { ""name"": ""author"", ""from"": ""1"", ""to"": ""5"" } }` Use `""from"": ""1"", ""to"": ""1000""` to make it effectively ""unlimited"".
+ * This can be made backwards-compatible. Users can still document `author1` to `author5` if they want. They just need to copy the sequence name to all of them, e.g. `""author2"": { ""sequence"": { ""name"": ""author"" } }`. Parameters with the same sequence are considered one by software that understands the feature.
+5. Somehow make use of the unused `set` feature.
+6. Just give the user a {key +} button at the end of numbered parameters, no matter how it's documented in TemplateData. It acts very similar to the ""add undocumented parameter"" feature but makes sure the order is consistent.
+6. …?
+
+I would like to avoid presenting an extra empty parameter at the end of every sequence of numbered parameters when the documentation explicitly says it doesn't exist, or we just don't know.",1669035672,PHID-USER-u6ycqhfpa3k4yvlpxjt2,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"#wmde-techwish here. Our #wmde-templates-focusarea last year focused on #TemplateData and the #VisualEditor template dialog. I'm aware of two situations we need to consider here:
+1. Non-Lua templates support exactly as many parameters as documented, as @Tacsipacsi explained above. For example, there is `author1` to `author9`, but there it ends. This causes a few problems:
+ * It's a little tedious to document this.
+ * Both #VisualEditor and #TemplateWizard get messy very fast the more such parameters exist. Note that having more than one is the norm, not the exception. Here is a [simple example](https://en.wikipedia.org/wiki/Template:Singles).
+ * The person writing the documentation might decide to stop earlier and document only e.g. `author1` to `author5` exactly to avoid the problem above. `author6` ff. will still work, but can only be entered in wikitext or with the ""add undocumented parameter"" feature. Unfortunately this creates the next problem: `author6` will be listed at the very end, not after `author5`.
+2. Lua-based templates can support an effectively unlimited number of such parameters. The currently only way to document this is to document a limited number, e.g. `author1` to `author5`. This creates almost the same problems:
+ * The documentation must stop at an arbitrary number. Typically this will not be `author1` but e.g. `author5` or `author9`.
+ * This is tedious, as above.
+ * VisualEditor and such always show all of the documented parameters.
+3. Because of all the problems above and thanks to the power of Lua users create more and more templates that accept multiple comma-separated values in a single parameter.
+ * This creates effectively a custom parameter type with a custom syntax (namely being comma-separated).
+ * TemplateData has no way to document this either. I mean, other than describing it to the user. But not in a machine-readable way.
+
+A relevant consequence of all this is that we don't have a way to distinguish the first two situations when both are documented as `author1` to `author5`.
+
+What we can do, in my opinion:
+1. Collapse numbered parameters in VisualEditor. For example, when you start with an empty template you see only `author1`. The moment `author1` does have a value `author2` appears. And so on. But stop when the next number is not documented.
+ * We can do this in VisualEditor without touching TemplateData.
+ * The only thing users need to do is to make sure all possible numbers are documented.
+ * This doesn't solve the situation where the number is unlimited, but allows for a workaround. Users just need to document //a lot// of numbers, e.g. `author1` to `author25`.
+2. Ask users to document an unlimited number of parameters by only documenting the first one, e.g. `author1`, but nothing else. We can use this special case to distinguish the two unlimited vs. limited scenarios.
+3. Come up with some magic syntax for numbered parameters, e.g. `""author[1-9]"": {}` means only 9 parameters exist and `""author[1-]"": {}` means it's unlimited.
+ * This allows to use other number systems, e.g. Hebrew `author[א-ט‎]`.
+ * Biggest problem with an approach like this is that it's entirely incompatible with existing software that doesn't understand the feature.
+4. Add a flag that does the same, e.g. `""author1"": { ""sequence"": { ""name"": ""author"", ""from"": ""1"", ""to"": ""5"" } }` or `""from"": ""1"", ""to"": ""1000""` to make it effectively ""unlimited"".
+ * This can be made backwards-compatible. Users can still document `author1` to `author5` if they want. They just need to copy the sequence name to all of them, e.g. `""author2"": { ""sequence"": { ""name"": ""author"" } }`. Parameters with the same sequence are considered one by software that understands the feature.
+5. Somehow make use of the unused `set` feature.
+6. Just give the user a {key +} button at the end of numbered parameters, no matter how it's documented in TemplateData. It acts very similar to the ""add undocumented parameter"" feature but makes sure the order is consistent.
+6. …?
+
+I would like to avoid presenting an extra empty parameter at the end of every sequence of numbered parameters when the documentation explicitly says it doesn't exist, or we just don't know.",1669035410,PHID-USER-u6ycqhfpa3k4yvlpxjt2,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"I think there are still a lot of templates that don’t use Lua and thus support exactly as many parameters as documented. They probably don’t show error messages if unknown parameters are used, either, since that would also require Lua. This means that the extra parameters would simply not appear – which doesn’t cause visual breakage, but it’s also hard for the editors to notice. What does Citoid do now if there are more authors/whatever data than what the template – according to TemplateData – supports?",1668975175,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Change 858708 had a related patch set uploaded (by Mvolz; author: Mvolz):
+%%%[mediawiki/extensions/Citoid@master] [WIP] Extrapolate from limited templatedata%%%
+https://gerrit.wikimedia.org/r/858708",1668963559,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"In lieu of a better plan, I think I'm just going to have the Citoid extension ""guess"" additional parameters from the last one rather naively by incrementing whatever integer is at the end. I.e. if it's last7, the next param will be last8
+
+If the last param doesn't have an integer, we won't do this. So if it's just ""last"" or ""isbn"" no additional parameters will be added. 
+
+Does anyone object to this? It's a bit hacky, but it's the simplest to implement. 
+
+The potential flaw of this would be if there is a parameter out there that ends in a number that we don't want incremented. I don't know if there's an example out there, but if there were, we could potentially add parameters that don't actually exist and you could see errors in the citation (which the user could then, as always, fix.)
+
+I expect this doesn't come up much, but a potential fix to that is to extend TemplateData to add a box to suppress auto params, if we needed it. 
+
+",1668963340,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"@Iniquity, the way I'd ideally like to see this work is to just have a box people could check when editing a parameter's documentation in TemplateData indicating that it's an auto-numbered parameter (and specifying the limit, if applicable). The TemplateData would then display it intuitively in the documentation and allow people to use it when adding the template to a page.",1633200407,PHID-USER-tl3o6dlackm57f3qrt4b,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,Has anyone got any new ideas? :),1564943687,PHID-USER-tuy2dac6pfhknbtqmqgh,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"For draft template I'm working on for the Wikitionary, I came with things like `|définition.1.4.exemple.2.description =`. That is description of 2nd example of the 4th subdefinition of the first main definition. That might be a somewhat extreme example, but that would be nice to take it into account while treating this ticket.",1510643874,PHID-USER-6xgsmxxl62mgxypce6oa,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"For draft template I'm working on for the Wikitionary, I came things like `|définition.1.4.exemple.2.description =`. That is description of 2nd example of the 4th subdefinition of the first main definition. That might be a somewaht extrem example, but that would be nice to take it into account while treating this ticket.",1509227971,PHID-USER-6xgsmxxl62mgxypce6oa,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"I am also thinking of templates with an unlimited number of unnamed parameters, which are not handled well in VE currently.",1508444614,PHID-USER-zrh22rct2jo5hs6nu67r,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Regarding the UX and UI of this feature, one possibility is that when a user adds content to the Author1 field, the Author2 field becomes visible, and when s/he adds content to Author2, Author3 becomes visible, and so on.",1496014248,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Regarding the visual implementation of this feature, one possibility is that when a user adds content to the Author1 field, the Author2 field becomes visible, and when s/he adds content to Author2, Author3 becomes visible, and so on.",1492548241,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"I think I may increase priority of this task. A lot of new templates, gadgets and scripts have autogenerated parameters.",1491072953,PHID-USER-tuy2dac6pfhknbtqmqgh,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"This will affect ProveIt when implemented. ProveIt relies on TemplateData to perform its work, much in the same way the VisualEditor does.",1480128425,PHID-USER-ptgz6fq66cg246bpgxzs,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Would be very useful also for, e.g., https://www.mediawiki.org/wiki/Template:Extension#TemplateData (up to hook48!)",1421099235,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"Hmm, I've messed up the JSON in the first example. Should be:
+
+{{cite web
+| authors = [{ ""last"": ""Smith"", ""first"": ""John"" }, { ""last"": ""Doe"", ""first"": ""Jane"" }]
+}}
+
+Perhaps this proves my point about users not being able to input JSON manually? :)",1410102520,PHID-USER-rjtk3h6l2quifuajiime,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"(In reply to NicoV from comment #5)
+> This solution would be awkward when several parameters are related one to
+> each other. For example, on the cite templates, you usually have several
+> fields for each author (first name, last name, page link, ...) and they are
+> easier to manage for a user if they are grouped.
+> With lists, users would have to be careful and to be sure that several lists
+> are coherent between each other.
+
+One way to deal with this could be to pass JSON blobs into template parameters. So you could have:
+
+{{cite web
+| authors = { ""last"": ""Smith"", ""first"": ""John"" }, { ""last"": ""Doe"", ""first"": ""Jane"" }
+}}
+
+This is nice from a Lua perspective, but it would be confusing for users. Mixing template syntax with JSON syntax seems ugly, and probably only a select few editors will be capable of entering syntactically correct JSON into template parameters.
+
+The established way of doing something like this is to use a sub-template. So we would have something like:
+
+{{cite web
+| authors = {{author|last=Smith|first=John}}, {{author|last=Doe|first=Jane}}
+}}
+
+One problem with this is that the {{author}} templates are expanded before they are passed to Lua, so we lose data granularity. To solve this, we can use Lua to make the {{author}} templates output JSON and then read that JSON from the Lua module implementing {{cite web}}. But then to guarantee that we get clean JSON code we would need to make a template structure like this:
+
+{{cite web
+| authors = {{author list | {{author|last=Smith|first=John}} | {{author|last=Doe|first=Jane}} }}
+}}
+
+With this we have data grouping that can be reliably processed by Lua and that editors used to using wikitext will find intuitive. However, this would be hard for VisualEditor etc. to process and display to users in a meaningful way, as there is no guarantee how the {{author list}} and {{author}} templates will be implemented on any given wiki. So, instead of using Lua to create the JSON, we could do it in PHP using a new parser function. (I suggest ""#data"".) That would give us the following: 
+
+{{cite web
+| authors = {{#data: {{#data:last=Smith|first=John}} | {{#data:last=Doe|first=Jane}} }}
+}}
+
+This would give us a data structure that could be reliably parsed from VisualEditor, as well as the other benefits mentioned above. Perhaps it could displayed as a dynamically generated data tree (I'm thinking about something like json2html, but editable).
+
+http://visualizer.json2html.com/
+
+We would need to be careful about bad input:
+
+{{cite web
+| authors = foo {{#data: bar {{#data:last=Smith|first=John}} | {{#data:last=Doe|first=Jane}} baz }}
+}}
+
+To sanitise this, we could make the #data implementation throw an error (perhaps like a cite.php error) for ""bar"" and ""baz"" in this example. For ""foo"", we could leave it to the Lua module to properly validate the input.
+
+We would also have to think carefully about what to do with templates etc. inside #data parser functions. If template expansion inside #data parser functions worked the same way that it did in normal wikitext, it would be difficult to make #data work well in VisualEditor. But perhaps it can be made to work in the same way that VE handles other instances of templates in template parameters.",1410099057,PHID-USER-rjtk3h6l2quifuajiime,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"(In reply to Krinkle from comment #4)
+> Especially now that we have Lua, specifying a parameter as taking a list
+> seems more sensible (e.g. comma separated, line-break separated, whatever).
+> Even if a template isn't converted to Lua yet, it could make use of a
+> generic Lua module to do the string split and iteration.
+
+This solution would be awkward when several parameters are related one to each other. For example, on the cite templates, you usually have several fields for each author (first name, last name, page link, ...) and they are easier to manage for a user if they are grouped.
+With lists, users would have to be careful and to be sure that several lists are coherent between each other.",1392795486,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"The foo1, foo2, foo3 etc. model exists in many templates, however in most cases the limit is quite low (when converted to Lua a user might have dropped the limit, no sure that is a good pattern). Only in cases where the value is for e.g. a table row do they have a high limit (up to 500 seems common).
+
+e.g. 
+
+{{Something
+|row1=..
+|row2=..
+|row3=..
+|=..
+
+such as {{TemplateBox@commons.wikimedia.org
+|p1=..
+|p2=..
+|p3=..
+|..
+
+However both for VisualEditor, TemplateData and any other modern program or programming language it is very visible that such dynamically named parameters are an unwanted pattern that should not be encouraged. It is hard to work with and only has downsides over alternatives (e.g. hard to re-order, requires hacks to implement in wikitext and lua, hard to document, hard to use).
+
+Especially now that we have Lua, specifying a parameter as taking a list seems more sensible (e.g. comma separated, line-break separated, whatever). Even if a template isn't converted to Lua yet, it could make use of a generic Lua module to do the string split and iteration.
+
+Also, in the interest of not implementing too soon and get stuck in a corner, I'd like to wait for VisualEditor to catch up with the features we've already recently added to TemplateData and see how those work out.",1381079832,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"This proposal is based mostly on the idea that if TemplateData exists for a template, then editors should not be permitted to add any parameters that are not already in TemplateData.  
+
+Rather than coding a variety of flexible naming/numbering schemes, it might make more sense to have a way to specify that a given template accepts (or does not accept) whatever parameters the editor chooses to name, regardless of what's in TemplateData.  If the TemplateData is complete and no unlisted parameters are useable, then editors could not add others.  If the TemplateData is incomplete, or if the number of parameters is unbounded, then editors could add whatever they wanted.",1375983254,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"In the module code they use # to represent a number placeholder.
+numbered_arguments = {
+    ['author#'] = true,
+    ['Author#'] = true,
+    ['author-first#'] = true,
+    ['author#-first'] = true,
+    ['author-last#'] = true,
+    ['author#-last'] = true,
+...
+}
+As you can see the number can be in various places.
+
+http://en.wikipedia.org/wiki/Module:Citation/CS1/Whitelist",1375823227,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion,"When implemented, this should also accept an empty string as the ""base"" (""author"" in original example above) to apply to unnamed (positional) parameters. Would be useful for some templates like [[pl:Template:Dopracować]] which currently can't be properly described using TemplateData.",1375805699,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-7agzn6t2zkyppgtkt4zy,task_subcomment,NA
+VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V),"I don't know if this is possible, or if it's been requested elsewhese, but a few users on the French-language Wikipedia have suggested that, when the user has scrolled through the page and invoked VisualEditor via the keyboard shortcut, VE should automatically scroll to that same position on the page when it opens (similarly to what the section edit link does).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53217",1375799880,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-pe6m5b3pbhmfcnu7uep4,task_description,open
+VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V),We've done the complicated part of this in T293158.,1663959026,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pe6m5b3pbhmfcnu7uep4,task_subcomment,NA
+VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V),"The complication here is that while the VE view is similar to the read mode, it is not identical, so scrolling to the same pixel offset will not necessarily leave you at the same place. We could do an approximation by finding the nearest section heading and it's pixel offset from the top.",1468335875,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pe6m5b3pbhmfcnu7uep4,task_subcomment,NA
+VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V),"**misc2006** wrote:
+
+This should always be the case, no matter how the editor is invoked. ""User's position"" when the editor is opened should be *exactly* the same as before. Use case: I want to fix a simple spelling error, so I click on the edit link on the paragraph. Often, the content has now scrolled up/down a bit and I need to find the location of the spelling error again. This is surprisingly difficult/annoying (just give it a try).",1405932609,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pe6m5b3pbhmfcnu7uep4,task_subcomment,NA
+"VisualEditor: Repetition of the parameter (""box"") icon in the transclusion dialog is a bit heavy","<< Icons can be useful to help a user navigate an interface, however in the transclusion dialog, the same box-shaped icon with the thick left border is shown so many times (when editing a template with more than a few parameters) that it is obnoxious. Almost every occurrence should be removed, keeping it displayed at at most one or two places.--[[User:Wouterstomp|WS]] ([[User talk:Wouterstomp|talk]]) 11:22, 6 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49833",1375794000,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-tb2wtwoarrokjafpdi3e,task_description,resolved
+"VisualEditor: Repetition of the parameter (""box"") icon in the transclusion dialog is a bit heavy",I disagree with this - the icon is used to identify which elements are parameters. Particularly in future they may be contrasted with sub-items such as images or sub-templates that are included in parameters but separately editable within the transclusion editor.,1375795854,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-tb2wtwoarrokjafpdi3e,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"[15:52] <T13> VE Question.  How is VE currently set up to handle users that have opted-in to gadgets that modify the editing window such as wikEd?
+...
+[15:54] <T13> Do those gadgets still load even though the hooks they use don't exist? Shouldn't having VE enabled disable those gadgets and grey out the optiobs for them in the gadgets tab of preferences?
+[15:56] <T13> I'm guessing some of the ""VE"" bugs are caused by these gadgets trying to do what they no longer can.
+...
+[16:06] <mooeypoo> T13: I think most of the edit-related gadgets work on the action=edit condition, and ve goes with action=vedit
+[16:07] <mooeypoo> but I am not sure :) you'll be safer getting the answer from the VE team
+[16:09] <MatmaRex> T13: i'm not on the team, but i'm pretty sure that's the reason
+[16:10] <MatmaRex> T13: basically there are two ways to detect if we're inedit mode - either look if 'action' is 'edit' or 'submit', or look for some elements that are parts of theedit form, like #wpTextbox1 (the main textbox)
+[16:10] <MatmaRex> VE avoids them both
+[16:11] <T13> I've seen questions on WP:THQ with a link to a screenshot of wikEd and the user thinking they were using VE.  So, I was curious how it was handled.
+[16:11] <T13> I'll add the suggestion to gray out the unusable with VE gadgets 
+[16:11] <mooeypoo> Ah, *that* kind of user errors. Hm. Not sure how you can handle those other than politely correct the user's false assumption
+[16:11] <T13> On Bugzilla...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375737720,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-u3h65rxvz452mowrmajb,task_description,open
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"Hmm. Not totally convinced by this - (a) because this is inherently transitional as gadgets are updated to work with VisualEditor, and (b) because disabling gadgets that work fine, just not in all places, seems a bit unfair. Re-titling and moving to the Gadgets pile, however.",1383282348,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"Working links:
+
+https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(current).png
+
+https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(proposed).png",1377871417,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"(In reply to comment #1)
+> Not sure what the bug is, here?
+> 
+> Gadgets can be written to work with VisualEditor, but gadgets not written to
+> do so won't work, and dated (and so now misleading) advertising on behalf of
+> these gadgets that it works with ""the editor"" will confuse people.
+> 
+> As normal, gadget authors and maintainers should make sure that they re-label
+> their gadgets to avoid this confusion.
+> 
+> Or am I missing something?
+
+I'm sorry James, I missed your question.  I've uploaded a couple screenshots of what I'm thinking (although I'm thinking this may require a change in the gadgets extension first on second thought).
+
+Currently, the ""Editing"" section of the gadgets tab on enwp looks like:
+   [[commons:File:Special_Preferences_mw-prefsection-gadgets_%28current%29.png]]
+
+What I'm proposing, is that when VisualEditor is active for the user, it should look like:
+   [[commons:File:Special_Preferences_mw-prefsection-gadgets_%28proposed%29.png]]
+
+With the options for things like dot's highlighter and wikiEd grayed out so they can't be clicked (and defaulted to off).",1377865283,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,Closing as INVALID as no response after 3 weeks (but happy to reconsider if I've mis-understood).,1377828505,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out,"Not sure what the bug is, here?
+
+Gadgets can be written to work with VisualEditor, but gadgets not written to do so won't work, and dated (and so now misleading) advertising on behalf of these gadgets that it works with ""the editor"" will confuse people.
+
+As normal, gadget authors and maintainers should make sure that they re-label their gadgets to avoid this confusion.
+
+Or am I missing something?",1375747264,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u3h65rxvz452mowrmajb,task_subcomment,NA
+VisualEditor: Backspace should not delete list and line in same action,"**Author:** `mcdevitd`
+
+**Description:**
+Typically, the expected behavior from hitting backspace at the beginning of a list line is to remove the bullet/number at that indent level so it is no longer a list, and no more. VisualEditor will completely delete the line itself and move the text to the end of the previous line. This is not how OpenOffice or Word works.",1375729680,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-vrzpbb2v2s74ml5e53ww,task_description,open
+VisualEditor: Backspace should not delete list and line in same action,"Currently (for years), pressing backspace in LibreOffice makes the paragraph exit the list **only if it is empty** (note we may split an ordered list in OpenDocuments, whereas we cannot in wikitext). Else, the behavior is pretty consistent with VisualEditor (first Backspace press: the bullet is hidden — no equivalence in VE; second Backspace press: the paragraph is merged with previous element).",1650765676,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-vrzpbb2v2s74ml5e53ww,task_subcomment,NA
+VisualEditor: Backspace should not delete list and line in same action,"Currently (for years), backspace LibreOffice make the paragraph exit the list only if it is empty. Else, the behavior is pretty consistent with VisualEditor (first Backspace press: the bullet is hidden — no equivalence in VE; second Backspace press: the paragraph is merged with previous element).",1650765546,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-vrzpbb2v2s74ml5e53ww,task_subcomment,NA
+VisualEditor: Backspace should not delete list and line in same action,"Agreed. For
+
+| <ol><li><p>|</p></li><li><p>Foo</p></li></ol>
+
+… backspace at the cursor position indicated should convert the document into:
+
+| <p>|</p><ol><li><p>Foo</p></li></ol>
+
+… with the initial <p> being a slug.
+
+For nested list items we should pop to the next level:
+
+| <ol><li><p>Foo</p></li><li><ol><li><p>|</p></li><li><p>Foo</p></li></ol></li></ol>
+
+->
+
+
+| <ol><li><p>Foo</p></li><li><p>|</p></li><li><ol><li><p>Foo</p></li></ol></li></ol>
+
+I think?",1394479004,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vrzpbb2v2s74ml5e53ww,task_subcomment,NA
+VisualEditor: Unindent should not remove lists,"**Author:** `mcdevitd`
+
+**Description:**
+The expected behavior in most word processors (Word and OpenOffice) is that the user can unindent (shift-tab) only to get to the initial list indent level but it should not actually delete the bulleting/numbering itself when you to the end. In VisualEditor, unindenting once too many times can remove the initial bullet/number entirely.
+
+This becomes particularly annoying when (because of the behavior described in bug 48051) you accidentally split a list into two lists which can't be fixed clicking the list button again to re-add the bullet/number.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375726080,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nog34g36rvrxth34pzwz,task_description,open
+VisualEditor: Unindent should not remove lists,(Still valid in current VE; is this really normal priority?),1426861555,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-nog34g36rvrxth34pzwz,task_subcomment,NA
+VisualEditor: Unindent should not remove lists,*** Bug 56344 has been marked as a duplicate of this bug. ***,1384846149,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nog34g36rvrxth34pzwz,task_subcomment,NA
+VisualEditor: Unindent should not remove lists,"**mcdevitd** wrote:
+
+(In reply to comment #1)
+> (In reply to comment #0)
+> 
+> > This becomes particularly annoying when (because of the behavior described in
+> > bug 48051) you accidentally split a list into two lists which can't be fixed
+> > clicking the list button again to re-add the bullet/number.
+> 
+> ""Undo"" fixes that instantly, of course.
+
+I wasn't trying to say that it is unfixable. I was just pointing out that the current list behavior means that the way most(?) people might naturally try to correct losing their bulleting/numbering would only compound the error. (""Undo"" fixes almost anything, of course, except frustration and time wasted.)",1375754135,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nog34g36rvrxth34pzwz,task_subcomment,NA
+VisualEditor: Unindent should not remove lists,"(In reply to comment #0)
+> The expected behavior in most word processors (Word and OpenOffice) is that
+> the user can unindent (shift-tab) only to get to the initial list indent
+> level but it should not actually delete the bulleting/numbering itself when
+> you to the end. In VisualEditor, unindenting once too many times can remove
+> the initial bullet/number entirely.
+
+This was a deliberate choice, though I can't remember why (it was over a year ago that this was implemented). We should reconsider.
+
+> This becomes particularly annoying when (because of the behavior described in
+> bug 48051) you accidentally split a list into two lists which can't be fixed
+> clicking the list button again to re-add the bullet/number.
+
+""Undo"" fixes that instantly, of course.",1375747948,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nog34g36rvrxth34pzwz,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Users are requesting VE August update (https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/August_2013_update) to be deployed in on hewiki.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**URL**: https://he.wikipedia.org/wiki/%D7%A9%D7%99%D7%97%D7%AA_%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:%D7%A2%D7%A8%D7%9F#.D7.A9.D7.99.D7.A0.D7.95.D7.99_.D7.91.D7.9E.D7.99.D7.A7.D7.95.D7.9D_.D7.94.D7.A7.D7.99.D7.A9.D7.95.D7.A8_.22.D7.A2.D7.A8.D7.99.D7.9B.D7.94_.D7.91.D7.A7.D7.95.D7.93_.D7.9E.D7.A7.D7.95.D7.A8.22_-_.D7.9B.D7.9E.D7.95_.D7.91.D7.95.D7.95.D7.99.D7.A7.D7.99.D7.A4.D7.93.D7.99.D7.94_.D7.94.D7.90.D7.A0.D7.92.D7.9C.D7.99.D7.AA",1375721160,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_description,resolved
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",Finally done; sorry for the delay.,1381515689,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Change 87645 merged by Reedy:
+Switch VisualEditor to secondary status on hewiki
+
+https://gerrit.wikimedia.org/r/87645",1381515513,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","(In reply to comment #14)
+> Change 87645 had a related patch set uploaded by Jforrester:
+> Switch VisualEditor to secondary status on hewiki
+> 
+> https://gerrit.wikimedia.org/r/87645
+
+Will try to schedule this soon.",1380938287,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Change 87645 had a related patch set uploaded by Jforrester:
+Switch VisualEditor to secondary status on hewiki
+
+https://gerrit.wikimedia.org/r/87645",1380938237,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","(In reply to comment #12)
+> Thanks for adding the welcome message. 
+> 
+> I know there are discussions regarding these changes[1], but the change of
+> the tab order (Edit and Edit source) is important for he wikipedia and Erik
+> isn't totally against it [only ambivalent] :)
+> 
+> [1]
+> http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2013-September/
+> 000419.html
+
+To speak for Erik (:-)), his ambivalence is about changing it *globally*, not about changing it on a given wiki.
+
+There's scope for a lot of concern about changing it for some wikis and not others, and so having a very inconsistent configuration for people that use multiple wikis. I think that it's probably OK to do this, but I really haven't come to ""a decision"". However, it's unfair to hewiki to have you hanging around waiting for me to make up my mind, and I'm sorry about this. :-(
+
+> Since VE is enabled only in the main NS and user NS, for editors who also
+> edit in other namespaces, addition of the VE edit tab ""in the middle"" may
+> cause confusion.
+
+That is certainly one argument. (Though surely it only applies to people with a very narrow window, or the minority who use the Monobook skin? For the others, the VisualEditor tab sits prone in namespaces they can use it in, and otherwise they get the tab they currently have to use until Flow is fully rolled out). But I see your point.
+
+> For consistency the edit source option should be alway the first
+> option [in order], while VE edit should be second.
+
+An alternative argument is that it's right that the first and primary tab is always the one they can use, and there may or may not be a secondary editor tab depending on the nature of the content they're editing.
+
+Of course, we can partially 'fix' this by enabling VisualEditor in all the other namespaces that it's safe for (at the least, File, Portal, Category, Help; not Project, as that's normally signed and so should wait with *_Talk for Flow). Not sure.
+
+In the mean time, I'm happy to move hewiki to [ Edit source | Edit ] for the time being, and would really welcome thoughts on my other points above.",1380937661,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Thanks for adding the welcome message. 
+
+I know there are discussions regarding these changes[1], but the change of the tab order (Edit and Edit source) is important for he wikipedia and Erik isn't totally against it [only ambivalent] :)
+
+Since VE is enabled only in the main NS and user NS, for editors who also edit in other namespaces, addition of the VE edit tab ""in the middle"" may cause confusion. For consistency the edit source option should be alway the first option [in order], while VE edit should be second.
+
+----
+[1] http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2013-September/000419.html",1380883041,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Change 77269 merged by jenkins-bot:
+Enable VisualEditor beta welcome notice for all wikis
+
+https://gerrit.wikimedia.org/r/77269",1378927706,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","[Sorry for the delay in responding.]
+
+The beta welcome message is now queued up to go out on all wikis with the next release when available.
+
+We're still not decided on the way forward for the edit source/edit labelling split, so this is delayed until we have a proper answer. Sorry.",1378770465,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","We are now in September so enough time have passed since August change, and the community have voted for deploying the changes. Please let us know when this change is planned for deployment.",1378147154,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","There is is large support for the change in the 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=14551521#.D7.94.D7.97.D7.9C.D7.A4.D7.AA_.D7.9E.D7.99.D7.A7.D7.95.D7.9D_.D7.94.D7.A7.D7.99.D7.A9.D7.95.D7.A8_.22.D7.A2.D7.A8.D7.99.D7.9B.D7.94_.D7.91.D7.A7.D7.95.D7.93_.D7.9E.D7.A7.D7.95.D7.A8.22_.D7.A2.D7.9D_.D7.9E.D7.99.D7.A7.D7.95.D7.9D_.D7.A7.D7.99.D7.A9.D7.95.D7.A8_.22.D7.A2.D7.A8.D7.99.D7.9B.D7.94.22_-_.D7.9B.D7.9E.D7.95_.D7.91.D7.95.D7.95.D7.99.D7.A7.D7.99.D7.A4.D7.93.D7.99.D7.94_.D7.94.D7.90.D7.A0.D7.92.D7.9C.D7.99.D7.AA",1377842346,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",All of these,1377020909,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","Hey,
+
+Which of the bits of the update do you mean?
+
+1. The re-ordered tabs and section edit links, so that the VE tab is second?
+2. Giving a welcome message when you open VisualEditor for the first time?
+3. Adding ""beta"" as a suffix after the VisualEditor tab and section edit link?
+4. Changing ""edit"" to ""edit source"" on non-VisualEditor pages for consistency?
+5. Removing the animation on section edit links?
+
+All of these? Items 4 and 5 are already done.",1376948752,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",is there any progress with the request?,1376848108,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",Gerrit change 77269 will handle part of this. They were just waiting on translations of the messages before enabling it.,1375862146,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",added in the url field.,1375792847,PHID-USER-u7udgblfyop6qd5wxot6,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary","(In reply to comment #0)
+> Users are requesting VE August update
+> (https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/August_2013_update) to
+> be deployed in on hewiki.
+
+Please provide a link to these requests, if possible.",1375791382,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+"Change the order of the ""edit"" (VE) and ""edit source"" (WT) tabs on hewiki to have WT as primary",Please mark the targeted milestone when it is known. Thanks,1375721827,PHID-USER-u7udgblfyop6qd5wxot6,False,PHID-TASK-wvcrw2fz7zto4p5xyqav,task_subcomment,NA
+VisualEditor: Empty HTML elements are not identifiable,"Slightly related to bug 51322 
+
+Take the Link FA templates on https://en.wikipedia.org/wiki/The_Adventures_of_Tintin?veaction=edit for instance. 
+
+These produce empty elements, and don't qualify under 'solely metadata' of bug 51322, even though they are somewhat similar to it.
+
+The templates are represented with the char: ↵
+Using the arrow keys to cursor trough this sequence will sometimes produce the template editor indicator. However their is little identifying these templates to the user and due to the interspersed ↵, users think they should be deleted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375720020,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-bm4l7dozmqtublm7xcao,task_description,resolved
+VisualEditor: Empty HTML elements are not identifiable,"Merging with bug 49806 (though non-transclusion empty HTML blocks do happen too).
+
+*** This bug has been marked as a duplicate of bug 49806 ***",1393529166,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bm4l7dozmqtublm7xcao,task_subcomment,NA
+VisualEditor: Empty HTML elements are not identifiable,"(In reply to comment #0)
+> The templates are represented with the char: ↵
+
+Actually, that's representing the meaningless wikitext of the newline after the template.",1380753594,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bm4l7dozmqtublm7xcao,task_subcomment,NA
+"VisualEditor: Floated node's action icon (e.g. for template) appearing in wrong location, relative to its initial position, not its actual position","From http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Quote_box
+
+In the adventures of tintin 
+http://en.wikipedia.org/wiki/The_Adventures_of_Tintin?veaction=edit
+
+the first {{quote box}} has been pushed down by the info box. The transclusion icon for this appears appear where the quote box was initially (just below the History section header on the right hand side) not where it actually appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51548",1375712940,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-g7kzupvlt4lakd72su4u,task_description,resolved
+"VisualEditor: Floated node's action icon (e.g. for template) appearing in wrong location, relative to its initial position, not its actual position",Not any more!,1519404104,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-g7kzupvlt4lakd72su4u,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?
+
+Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".
+
+We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.
+
+```
+aftv5-last-filter: null
+ccmeonemails: 0
+cols: ""120""
+date: ""mdy""
+diffonly: ""1""
+disablemail: 0
+disablesuggest: 0
+echo-email-format: ""html""
+echo-email-frequency: 0
+echo-notify-show-link: true
+echo-show-alert: true
+echo-subscriptions-email-article-linked: false
+echo-subscriptions-email-edit-thank: false
+echo-subscriptions-email-edit-user-talk: 1
+echo-subscriptions-email-mention: false
+echo-subscriptions-email-other: false
+echo-subscriptions-email-page-review: false
+echo-subscriptions-email-reverted: false
+echo-subscriptions-email-system: true
+echo-subscriptions-web-article-linked: ""1""
+echo-subscriptions-web-edit-thank: true
+echo-subscriptions-web-edit-user-talk: true
+echo-subscriptions-web-mention: true
+echo-subscriptions-web-other: true
+echo-subscriptions-web-page-review: true
+echo-subscriptions-web-reverted: true
+echo-subscriptions-web-system: true
+editfont: ""default""
+editondblclick: 0
+editsection: 1
+editsectiononrightclick: 0
+enotifminoredits: 0
+enotifrevealaddr: 0
+enotifusertalkpages: 1
+enotifwatchlistpages: 0
+ep_bulkdelcourses: true
+ep_bulkdelorgs: false
+ep_showdyk: true
+ep_showtoplink: false
+extendwatchlist: 0
+fancysig: ""1""
+flaggedrevseditdiffs: true
+flaggedrevssimpleui: 1
+flaggedrevsstable: 0
+flaggedrevsviewdiffs: false
+forceeditsummary: ""1""
+gadget-BugStatusUpdate: ""1""
+gadget-DRN-wizard: 1
+gadget-HotCat: ""1""
+gadget-Navigation_popups: ""1""
+gadget-NoAnimations: ""1""
+gadget-PrintOptions: ""1""
+gadget-ReferenceTooltips: 1
+gadget-UTCLiveClock: ""1""
+gadget-addsection-plus: ""1""
+gadget-charinsert: 1
+gadget-contribsrange: ""1""
+gadget-edittop: ""1""
+gadget-exlinks: ""1""
+gadget-metadata: ""1""
+gadget-mySandbox: 1
+gadget-purgetab: ""1""
+gadget-teahouse: 1
+gadget-widensearch: ""1""
+gadget-wikEd: ""1""
+gadget-wikEdDiff: ""1""
+gender: ""male""
+gettingstarted-task-toolbar-show-intro: """"
+hideminor: 0
+hidepatrolled: 0
+imagesize: 2
+justify: 0
+language: ""en""
+math: ""6""
+mfWatchlistFilter: ""all""
+mfWatchlistView: ""feed""
+minordefault: 0
+newpageshidepatrolled: 0
+nocache: 0
+noconvertlink: 0
+norollbackdiff: 0
+numberheadings: 0
+previewonfirst: 0
+previewontop: 1
+rcdays: 7
+rclimit: 50
+rcshowwikidata: ""1""
+rememberpassword: 0
+rows: ""30""
+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: ""1""
+searchNs15: false
+searchNs100: false
+searchNs101: false
+searchNs108: false
+searchNs109: false
+searchNs446: false
+searchNs447: false
+searchNs710: false
+searchNs711: false
+searchNs828: false
+searchNs829: false
+searchlimit: 20
+showhiddencats: ""1""
+showjumplinks: 1
+shownumberswatching: 1
+showtoc: 1
+showtoolbar: 1
+skin: ""vector""
+stubthreshold: ""2000""
+thumbsize: 4
+timecorrection: ""ZoneInfo|120|Europe/Amsterdam""
+uls-preferences: """"
+underline: 2
+usebetatoolbar: 1
+usebetatoolbar-cgd: 1
+useeditwarning: 1
+uselivepreview: 0
+usenewrc: ""1""
+userjs-curationtoolbar: ""hidden""
+variant: ""en""
+vector-collapsiblenav: 1
+vector-simplesearch: 1
+visualeditor-betatempdisable: 0
+visualeditor-enable: 1
+watchcreations: 1
+watchdefault: 0
+watchdeletion: 0
+watchlistdays: 3
+watchlisthideanons: 0
+watchlisthidebots: 0
+watchlisthideliu: 0
+watchlisthideminor: 0
+watchlisthideown: 0
+watchlisthidepatrolled: 0
+watchmoves: 0
+wikilove-enabled: 1
+wllimit: 250
+wlshowwikibase: ""1""
+```
+--------------------------
+**See Also**:
+{T29471}",1375702860,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_description,open
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","@Samwilson I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies.
+
+This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).",1519100508,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Also, just to note that `email-blacklist` is another outlier and is actually an array.",1519099509,PHID-USER-hlhhe6qw6qfkl7wyfhxk,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?",1519098837,PHID-USER-hlhhe6qw6qfkl7wyfhxk,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code.
+
+I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479716929,PHID-USER-p6gpvwnc6ske65oxuoof,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code.
+
+I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479715550,PHID-USER-p6gpvwnc6ske65oxuoof,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers.
+
+However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that.
+
+So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:
+
+```
+rclimit: 50
+rows: ""30""
+searchNs0: true
+searchNs1: false
+..
+searchNs10: ""1""
+searchNs11: false
+searchNs12: false
+searchNs13: false
+searchNs14: ""1""
+```
+
+Quite the mix up.
+
+Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1519100319,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers.
+
+However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that.
+
+So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:
+
+```
+rclimit: 50
+rows: ""30""
+searchNs0: true
+searchNs1: false
+..
+searchNs10: ""1""
+searchNs11: false
+searchNs12: false
+searchNs13: false
+searchNs14: ""1""
+```
+
+Quite the mix up.
+
+Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1423877781,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)",I have had similar difficulties and personally prefer booleans wherever possible.  They're more reliable and less likely to be unpredictable.  They are either true or false or they're invalid.,1423875937,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1)
+> ...
+> normalizing values of boolean prefs to true/false just before building this
+> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.
+
++1 for normalizing boolean preferences so that either
+> `mw.user.options.get( 'anyBooleanPreference' ) === true`
+> `mw.user.options.get( 'anyBooleanPreference' ) === false`
+and nothing else.
+
+The current behavior is ***very*** inconvenient:
+* If I do not set `$wgDefaultUserOptions['usebetatoolbar']`
+(i.e., if I use WikiEditor's default):
+  - If I don't change the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === null`
+  - If I enable the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === ""1""`
+* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]):
+  - If I don't change the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === 1`
+  - If I disable the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!)
+* On English Wikipedia
+  - If I don't change the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === 1`
+  - If I disable the preference
+    `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!)
+
+[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1466864706,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1)
+> ...
+> normalizing values of boolean prefs to true/false just before building this
+> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.
+
++1 for normalizing boolean preferences so that either
+> mw.user.options.get( 'anyBooleanPreference' ) === true
+> mw.user.options.get( 'anyBooleanPreference' ) === false
+and nothing else.
+
+The current behavior is ***very*** inconvenient:
+* If I do not set $wgDefaultUserOptions['usebetatoolbar']
+(i.e., if I use WikiEditor's default):
+  - If I don't change the preference
+    mw.user.options.get( 'usebetatoolbar' ) === null
+  - If I enable the preference
+    mw.user.options.get( 'usebetatoolbar' ) === ""1""
+* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]):
+  - If I don't change the preference
+    mw.user.options.get( 'usebetatoolbar' ) === 1
+  - If I disable the preference
+    mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!)
+* On English Wikipedia
+  - If I don't change the preference
+    mw.user.options.get( 'usebetatoolbar' ) === 1
+  - If I disable the preference
+    mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!)
+
+[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","The integer came from $wgDefaultSettings. Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.",1375735877,PHID-USER-a6jwrurphpx6yl4coupk,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"User preferences are inconsistently stored (bool/int as default, string for overrides)","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them).
+
+Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case.
+
+I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",1375703425,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-yfjwr3je2btidmhmuccx,task_subcomment,NA
+"VisualEditor: In the save dialog, also show the ""switch to wikitext"" button in the wikitext diff so they can fix last-minute issues","when saving, there is possibility to check the result visually. allow to edit it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T52687}",1375606860,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-escar4ypn3o4hbygakj4,task_description,open
+"VisualEditor: In the save dialog, also show the ""switch to wikitext"" button in the wikitext diff so they can fix last-minute issues","(In reply to comment #2)
+> agreed, james, that would be desireable. but is for sure a very different
+> feature not at all helping out when the diff reveals visual editor did
+> something unexpected.
+It does actually help: you can close the save dialog and switch to source mode, but this is not very discoverable.
+
+Maybe we should consider adding a button to the diff preview that sends you straight to source mode?",1390857782,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-escar4ypn3o4hbygakj4,task_subcomment,NA
+"VisualEditor: In the save dialog, also show the ""switch to wikitext"" button in the wikitext diff so they can fix last-minute issues","agreed, james, that would be desireable. but is for sure a very different feature not at all helping out when the diff reveals visual editor did something unexpected.",1377845408,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-escar4ypn3o4hbygakj4,task_subcomment,NA
+"VisualEditor: In the save dialog, also show the ""switch to wikitext"" button in the wikitext diff so they can fix last-minute issues","This is an interesting idea, but I think bug 50687 (with a button to switch to the wikitext editor) is probably more discoverable and more useful for some situations.",1377815545,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-escar4ypn3o4hbygakj4,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,"Greg also reproduced this.  He sees a superscript, but I have an additional issue, that the beta is roughly the same horizontal position.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375503180,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-yr55vawmutvv7jim7igv,task_description,resolved
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,*** Bug 71651 has been marked as a duplicate of this bug. ***,1412495213,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,"Upstream bug has been marked as fixed since 2014-06-19 15:05:07 (for FF33 - currently in Aurora, which seems to be fixed to me), marking this as fixed as well.",1408815618,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,Seems to be already reported as https://bugzilla.mozilla.org/show_bug.cgi?id=727125,1401826563,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,Filed as https://bugzilla.mozilla.org/show_bug.cgi?id=1009874,1400018028,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,Firefox-specific rendering bug.,1375765683,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox,"Created attachment 13057
+Screenshot of beta with overline
+
+This is from a few hours ago on enwiki.  It is reproducible (try a fresh account on enwiki), almost 100% of the time (one load seemed not to do it).
+
+**Attached**: {F11270}",1375503720,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-yr55vawmutvv7jim7igv,task_subcomment,NA
+"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects.
+
+However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.
+
+There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.
+
+As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a:
+IF editor=""VisualEditor"" THEN do X ELSE do Y
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375469280,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-lusyegvtclbce7nfsesb,task_description,open
+"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","I don't think there should be a control for separate interface messages.
+
+However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.",1378320091,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lusyegvtclbce7nfsesb,task_subcomment,NA
+"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","Yes, that does sound far simpler to implement! More difficult to keep the two in synch, but I suppose you can't have everything.",1375472876,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-lusyegvtclbce7nfsesb,task_subcomment,NA
+"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example.
+
+This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)",1375470158,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-lusyegvtclbce7nfsesb,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","What it says on the tin: The transclusion editor should have a ""cancel"" button next to ""Apply changes"". This would close the editor without saving any changes.
+Possibly it should require a confirmation if one or more templates have been selected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52386",1375460340,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_description,resolved
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","(In reply to John Broughton from comment #8)
+> If in fact the link tool and the Formula window are outside the scope of this>
+> bug, feel free to close the bug
+
+They are. This bug is about dialogs.
+
+Design questions about non-dialogs is a distinct question – raising another ticket is probably a good idea if you think they should be changed.",1410807070,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","As noted previously, there no ""Cancel"" button on the link tool (dialog? insert window?). Also, there is no ""Cancel"" button on the Formula dialog (insert window?). 
+
+I'm reopening this bug because otherwise - in ""Resolved"" status - this bug is much more likely to be ignored. If in fact the link tool and the Formula window are outside the scope of this bug, feel free to close the bug - then we'll know that we need to open a new, separate bug to address those two issues.",1407699259,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","There is still no ""Cancel"" button on the link tool.",1407651731,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""",This was done as part of the window redesign work.,1406063829,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","A user at en.wp has reported that they were unaware that the ^ button on the save page dialog would return them to the article. Consequently they were under the impression that the only options were to preview the changes, save the changes or abort the edit, i.e. there was no way to go back and make addition changes or fix ones they had already made.
+
+A cancel button as discussed in this bug would solve this, although I think labelling it something like ""return to editing"" would be better than ""cancel"" here (which could imply discarding the edit).",1377683762,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","I think a cancel button makes perfect sense from a UX point of view for dialogs.
+
+Closing would be an alias of cancel, but that's not the primary flow for a user.
+
+Closing windows is always a bit of awkward and uncertain action to take.",1375493049,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","(In reply to comment #2)
+> Yes, I've seen it mentioned a couple  of times that people aren't sure what
+> state clicking the ""X"" will leave things in. Will it cancel everything
+> they've done, cancel only unfinished/unapplied changes, or close with
+> everything in its current state finished or not.
+
+* A ""rubbish bin"" icon (on lightweight inspectors, but not dialogs) is Option 1.
+* An ""X"" icon (on dialogs, but not inspectors) is Option 2.
+* The ""apply changes"" button (on dialogs, but not inspectors) is Option 3.
+
+Clearly this isn't ""obvious"" enough; we should consider what more we can do.",1375492557,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","Yes, I've seen it mentioned a couple  of times that people aren't sure what state clicking the ""X"" will leave things in. Will it cancel everything they've done, cancel only unfinished/unapplied changes, or close with everything in its current state finished or not.",1375486468,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"VisualEditor: Dialogs should have a ""cancel"" button next to ""Apply changes""","This functionality is currently provided by the ""X"" in the top-right corner (as for all dialogs). Is a duplicate button needed?",1375482783,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ktdxstz7i62g4zy5m5ov,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","User:Wouterstomp at en.wp suggests that in the media selection dialog, the full name of an image should be shown in a tooltip when you hover over it. Either for all images or only those whose name is too long to be shown in full beneath the image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375458480,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-erdij6gvcjcryxt3xqjp,task_description,resolved
+"In the VisualEditor media selector, show the name of each file so it can be identified",Checked in betalabs.,1422573163,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","Change 183729 merged by jenkins-bot:
+Add filename to the media dialog
+
+[[https://gerrit.wikimedia.org/r/183729]]",1421430202,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","Change 183729 had a related patch set uploaded (by Mooeypoo):
+Add filename to the media dialog
+
+[[https://gerrit.wikimedia.org/r/183729]]
+
+#patch-for-review",1420760594,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified",Or not.,1411746458,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","Since no one disagrees, I'm going to make that happen.",1411743607,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","I think a better place to display the name would be in the ""Media settings"" dialog. Right now, when inserting an image, you don't even know what you're inserting (neither a file name nor a thumbnail is shown in the dialog).
+
+That would also provide a better place for the ""Choose a different image"" button, which is now awkwardly placed in the bottom-left corner.",1410955390,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"In the VisualEditor media selector, show the name of each file so it can be identified","This would be nice for desktop users, but not so good for mobile (tablet/phone) users who are using touch to navigate. Maybe something else for them, like displaying the details of the file on a page before inserting?",1375487540,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-erdij6gvcjcryxt3xqjp,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected","en.wp editor GermanJoe suggests that if you try to add a template not in the transclusion editor's list of known templates that it should give a warning or ""are you sure?"" message.
+
+Such a message would note that very new templates might not appear in he list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375435380,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-qjdwtbzzs25aurzlowwr,task_description,resolved
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected","We now have a warning which is probably sufficient:
+{F13652706}",1518444836,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected","(In reply to Alex Monk from comment #2)
+> Unknown template = template with no TemplateData?
+
+(In reply to Alex Monk from comment #3)
+> Non-existent?
+
+It means ""the API didn't claim to know about it existing"". Given MediaWiki's… awkwardness about knowing whether or not a page actually exists I didn't want to assume something when I wrote it. :-)",1414103160,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected",See comment #1?,1414099109,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected",Non-existent?,1414097282,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected",Unknown template = template with no TemplateData?,1414096922,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+"VisualEditor: Transclusion editor should should give an ""are you sure?"" message if an unknown template is selected","This feels like it could be a bit irritating as a modal alert, but maybe we could come up with something as effective whilst less in-your-face.",1375748014,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qjdwtbzzs25aurzlowwr,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Currently the the transclusion editor's list of templates includes /Doc and other subpages of templates that are not themselves actual templates.
+
+At https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_2#Removing_template_subpages_from_the_template_selection_list.3F there was a discussion about this which suggested possible ways forward:
+* Exclude all subpages except those explicitly marked as templates, e.g by magic word or category
+* Include all subpages except those explicitly marked as not being templates, e.g. by magic word or category
+
+See also:
+* {T52512}
+* {T58516}",1375434960,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_description,resolved
+Transclusion dialog should not suggest documentation sub pages as templates,"Change 483205 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWTemplateTitleInputWidget: Filter out templates named '…/doc'
+
+[[https://gerrit.wikimedia.org/r/483205]]",1548973792,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,">>! In T54448#4888682, @Johan wrote:
+> Is this done and will be deployed next week? (It's been added to Tech News.) I can't see that in the task, but I could be missing something?
+
+Nope, sorry, code still going through review. I'll go poke it now.",1547752559,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Is this done and will be deployed next week? (It's been added to Tech News.) I can't see that in the task, but I could be missing something?",1547743671,PHID-USER-go2ym6ta2zn6ofdsrqnx,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Thanks!
+I think it worth a Tech News post since some communities may see the difference. It is a good opportunity to highlight `templatedata-doc-subpage` too is not already known. ",1547561928,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,I think it worth a Tech News post since some communities may see the difference. It is a good opportunity to highlight `templatedata-doc-subpage` too is not already known. ,1547561919,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,">>! In T54448#4876695, @Trizek-WMF wrote:
+> @Jdforrester-WMF, how this would be deployed? How your change will identify language variants for `/doc`?
+
+It'd be a train patch. Communities already (can) define the template documentation sub-page for the TemplateData extension via the `templatedata-doc-subpage` message, and this just re-uses that, which defaults to `foo` (so if you create `Template:Foo/doc` it'll be hidden, but `Template:Foo/I have another sub-page to be confusing` won't). Not merged yet though. I don't think this'd be worth a Tech News post.",1547492363,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"@Jdforrester-WMF, how this would be deployed? How your change will identify language variants for `/doc`?",1547460974,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Change 483205 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] MWTemplateTitleInputWidget: Filter out templates named '…/doc'
+
+[[https://gerrit.wikimedia.org/r/483205]]",1547062350,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Change 464718 **merged** by jenkins-bot:
+[mediawiki/extensions/TemplateData@master] Don't store templatedata pageprop on doc-subpage
+
+[[https://gerrit.wikimedia.org/r/464718]]",1540999311,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Change 464718 had a related patch set uploaded (by Krinkle; owner: Krinkle):
+[mediawiki/extensions/TemplateData@master] Don't store templatedata pageprop on doc-subpage
+
+[[https://gerrit.wikimedia.org/r/464718]]",1538687276,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,">>! In T54448#1991488, @maiden_taiwan wrote:
+> Suggestion: allow the wiki administrator to designate a particular subpage string, such as `doc`, as the official place to keep TemplateData. Then VisualEditor can intelligently and unambiguously filter these pages out. See T125222.
+
+(This is an old comment but I think it would be helpful.) TemplateData already has a message for this in the configuration, `MediaWiki:Templatedata-doc-subpage`, so implementing solutions based on that shouldn’t be a problem.",1531613135,PHID-USER-3ljmcrqixyljk2wy63jb,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"[[ https://hu.wikipedia.org/w/index.php?title=Vars%C3%A1nyi_Istv%C3%A1n&diff=prev&oldid=19944747 | An example ]]: I accidentally //{{Nemzetközi katalógusok/doc}}// instead of //{{Nemzetközi katalógusok}}//, because I was not thoughtful enough. We should find a way to avoid the problem.",1526835132,PHID-USER-qdbrv6swdxlgemqwwbuw,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,">>! In T54448#1991488, @maiden_taiwan wrote:
+> Suggestion: allow the wiki administrator to designate a particular subpage string, such as `doc`, as the official place to keep TemplateData. Then VisualEditor can intelligently and unambiguously filter these pages out. See T125222.
+
+This one could work! On pt-wiki we use ""doc"" as the documentation subpage and ""dados"" as the TemplateData. Maybe blacklisting both of them could help VisualEditor interpreting them as **not** templates to be transcluded. 
+I don't think that //""excluding all subpages except those explicitly marked as templates""// would be a good idea, because there are plenty of templates (Info/Patologia, Info/Grupo étnico, Info/Facção de conflito etc.) located on subpages.",1479326628,PHID-USER-46kgwzejnrokds6ov24i,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Suggestion: allow the wiki administrator to designate a particular subpage string, such as `doc`, as the official place to keep TemplateData. Then VisualEditor can intelligently and unambiguously filter these pages out. See T125222.",1454445652,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"Another option: instead of filtering, use sorting by usage (group by on templatelinks) instead of alphabetic sorting.",1439039697,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,I think we have simple way to filter out subpages of templates.,1439039410,PHID-USER-ipgdr6xrndwpztdrubk4,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+Transclusion dialog should not suggest documentation sub pages as templates,"> Suggested possible ways forward:
+> 
+> * Exclude all subpages except those explicitly marked as templates, e.g by magic word or category
+> * Include all subpages except those explicitly marked as not being templates, e.g. by magic word or category
+
+Neither of these options are imho maintainable or author-friendly. Alternative ideas (from T98562).
+
+> * Filter out /doc (hardcoded).
+>  * Principally not as ugly as one might think, since TemplateData does this as well. Though TemplateData only uses that hardcoded value to discover related pages in the graphical interface. It is in no way enforced server-side or encouraged in its interface when inserting/editing template data.
+>  * We'd have to filter it client-side, which means the number of results shown is inconsistent. To avoid false positives with template names that actually end in ""/doc"", we'd only remove results if the other title is also in the list. (E.g. ""Template:Dac/duc/doc"" or something like that.)
+> * Filter out results that are transcluded in other results.
+>  * Requires an additional query somewhere, but might be a smart way to do it. We'd only omit results that are transcluded by others. So ""Template:Foo/doc"" would be omitted because according to the link tables, ""Template:Foo"" (also in the suggestions) transcludes ""Template:Foo/doc"". This doesn't work well because documentation pages themselves often make use of various other templates. So any template used in the preview, examples, or documentation would never show up in the suggestions.
+> * Filter out results that transclude template data.
+>  * Not sure how this would work, but since the same duplication is also present in the page-property index (which is where template data is stored), we can detect that Foo and Foo/doc both have (the same) template data. We may be able to de-duplicate results that way (and pick the one that sorts higher, or the one with a shorter name, aka not the helper page that tends to be a sub page).
+
+And of course {T56140} – which I'd say is the ideal solution. And is quite feasible to implement.",1431057318,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f6h4xzkjkkq4qb5rbp2j,task_subcomment,NA
+"VisualEditor: Copying and pasting the first reference on a page, then deleting the pasted reference results in ref ""0""","I was able to produce a reference labelled ""0"" in the VisualEditor using the following steps:
+
+1. Create a simple page with some text and a reference. (I've made an example at [[User:Mr. Stradivarius/ref0]].)
+2. Copy and paste the reference to somewhere else in the page.
+3. Delete the reference from the text that has just been copied and pasted.
+4. The first reference is automatically renumbered to ""0"".
+
+The numbering of the first is fixed (back to ""1"") if you delete the line of text that you were on, but if you add new lines of text the first reference remains laballed ""0"" even if the pasted line is subsequently removed. The numbering still starts at 0 if you add another reference, so you get ref ""0"", ref ""1"", etc.
+
+This is on Firefox 22.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375433040,PHID-USER-rjtk3h6l2quifuajiime,False,PHID-TASK-m6kobht7lswcgwklm5ra,task_description,resolved
+"VisualEditor: Copying and pasting the first reference on a page, then deleting the pasted reference results in ref ""0""","Confirming that this bug is now fixed, almost certainly in the re-write of copy-and-paste for nodes that happened for the 5 September release. Apologies for the slow triage at my end.",1379656831,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m6kobht7lswcgwklm5ra,task_subcomment,NA
+"VisualEditor: Copying and pasting the first reference on a page, then deleting the pasted reference results in ref ""0""","Also, this is just in the editing window. When the page is saved, the numbering returns to normal.",1375433127,PHID-USER-rjtk3h6l2quifuajiime,False,PHID-TASK-m6kobht7lswcgwklm5ra,task_subcomment,NA
+"VisualEditor: Firefox up-down cursoring around aliens is broken, takes user to end of page sometimes","When the first line of an article is a hatnote template that generates exactly 1 line of text in the visual editor, pressing down twice takes you to the end of the article. When the hatnote template generates more than one line then pressing down takes you to the end of the first line but no further.
+
+I have been unable to reproduce this with templates other than hatnotes. 
+
+Steps to reproduce (short hatnote):
+1. Load a page with a short hatnote in VE, e.g. [[Laurence of Canterbury]]
+2. Press the down cursor twice
+
+Expected behaviour: you end up on the third line of the page
+Actual behaviour: you end up on the last line of the page
+
+Steps to reproduce (long hatnote):
+1. Load a page with a long hatnote in VE, e.g. [[An American in Paris]]
+2. Press the down cursor three or more times.
+
+Expected behaviour: you end up on the third or fourth etc. line of the page
+Actual behaviour: you end up at the end of the first line of the hatnote.
+
+Sandbox pages to test:
+Long hatnote: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=566827194&veaction=edit
+Short hatnote: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox2&oldid=566827110&veaction=edit
+
+This might be related to bug 51708
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51708",1375432860,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k3hxvwskpoy3zkxaliwa,task_description,resolved
+"VisualEditor: Firefox up-down cursoring around aliens is broken, takes user to end of page sometimes","Have tested this again, and I believe we have fixed this bug as reported, as part of the re-writing of how ContentEditable reacts to cursor events. However, I think I've found another bug semi-related, so will open that.",1380754670,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k3hxvwskpoy3zkxaliwa,task_subcomment,NA
+"VisualEditor: Firefox up-down cursoring around aliens is broken, takes user to end of page sometimes","My testing was in Monobook in Firefox 22 on Linux.
+The original reporter was using Monobook in Firefox 22 on Windows 7.
+Rybec comments that they can reproduce it in some pages (e.g. my sandbox) but not others (e.g. [[Laurence of Canterbury]]) using Firefox ESR on Linux.
+
+It's starting to look like it might be a Firefox-only bug.",1375477103,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k3hxvwskpoy3zkxaliwa,task_subcomment,NA
+"VisualEditor: Firefox up-down cursoring around aliens is broken, takes user to end of page sometimes","I have been unable to reproduce this at all on all of the linked pages, with both Monobook and Vector on Chrome, Win7.",1375475936,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-k3hxvwskpoy3zkxaliwa,task_subcomment,NA
+"The on-page notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices, unlike all the other status notes","Flagged Revisions provides a number of edit notices about the status of the page being edited, but this one (about the status of the transcluded components thereof) isn't. This feels wrong. It also means VisualEditor can't warn people about it.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52280",1375423920,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-d3wa2dbg66dt5t24advb,task_description,duplicate
+VisualEditor: Link inspector should have bottom margin to avoid cutting the page (UX),"Screenshot of problem
+
+When the link inspector is fairly tall and the space somewhat narrow (e.g. a red link, 10 suggestions in the inspector, and the link itself is towards the bottom of the screen), the box will expand further than the page goes (triggering a scrollbar if needed).
+
+That's fine, except that it is hard to see for the user whether there is more or not. Especially with OSX hiding scroll bars by default.
+
+There should be some bottom margin so that it can be clearly seen that the bottom of the list is the bottom, ans eparated from the bottom of the (now expanded) page.
+
+See attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11124}",1375410180,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pzog36r24v5pdzjqcxdr,task_description,resolved
+VisualEditor: Link inspector should have bottom margin to avoid cutting the page (UX),We have similar logic in the dropdown menus and dialogs already. They never touch the bottom of the window.. No Touching!,1403712107,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pzog36r24v5pdzjqcxdr,task_subcomment,NA
+"VisualEditor: Extending an existing DL-indentation renders correctly in CE, but doesn't come through on save","Pressing enter at the end of a colon indented line and typing more text displays as an indented, but, on save, (and review changes) the colon has not been added to the new line.
+
+Steps to reproduce:
+
+0. Start with a simple colon indented section. (See here: http://en.wikipedia.org/w/index.php?title=User:Markhurd/Sandbox&oldid=566721115 )
+1. Edit with VE.
+2. Click at end of last indented line.
+3. Press Enter. Note this displays as continuing the indentation.
+4. Type some text.
+5. Save. Note that the colon is not included. (You can see it missing with Show Changes.)
+
+My diff: http://en.wikipedia.org/w/index.php?title=User:Markhurd/Sandbox&diff=566721183&oldid=566721115
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375368960,PHID-USER-fgul5wwrgbtdpd5fved3,False,PHID-TASK-jgayasapvffxzhq5zq6a,task_description,open
+"VisualEditor: Extending an existing DL-indentation renders correctly in CE, but doesn't come through on save",This does seem to be fixed: https://en.wikipedia.org/w/index.php?title=User:Markhurd/Sandbox&diff=662749142&oldid=646642979,1431858171,PHID-USER-fgul5wwrgbtdpd5fved3,False,PHID-TASK-jgayasapvffxzhq5zq6a,task_subcomment,NA
+"VisualEditor: Extending an existing DL-indentation renders correctly in CE, but doesn't come through on save","Created attachment 13202
+VE shows the new text as indented, but it isn't
+
+I've just reproduced this in Firefox 23/Linux/Monobook. The screenshot shows how VE displayed it, the dif showing what was actually saved is: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=570859913&oldid=570858997
+
+The trailing blank lines are bug 50995, and this may be an artefact of the same bug as the displayed blank lines do not exist in the source.
+
+**Attached**: {F11963}",1377896791,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-jgayasapvffxzhq5zq6a,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"It isn't obvious to all users that clicking on the warning about Wikitext will make it disappear.
+
+For example, PamD at en.wp said:
+""I edited an article and found I'd got the popup saying I'd been using wiki markup, I should go into Edit Source, my edits wouldn't be saved, etc. I knew I'd input a pair of ''s at one time but had then remembered the error of my ways, removed them, and marked the title as italic in VE style, so was pretty confident I hadn't used any wiki markup and went ahead and saved the edit (difficult because the popup was sitting on top of the savepage box).""
+
+The main issue there is Bug 52155, but after being pointed to that bug she replied:
+
+""so if I'd clicked on the box it would have gone away... ? Not obvious!""
+
+It would be good to add an X in the upper right corner to indicate that it can be closed. This wouldn't change the behaviour that clicking anywhere on the box dismisses it, just give a visual indication that it can be done.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51701
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52462",1375356660,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-6ytamqsj45kuhfs22bx4,task_description,resolved
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"Change 87034 merged by jenkins-bot:
+Toolbar action widgetization and UI refactoring
+
+https://gerrit.wikimedia.org/r/87034",1380932250,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"Change 87034 had a related patch set uploaded by Jforrester:
+Toolbar action widgetization and UI refactoring
+
+https://gerrit.wikimedia.org/r/87034",1380844342,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"Rephrased bug to not mention ""wikitext message"". Instead focussing on notices that pop out of the toolbar, which are indeed created by VisualEditor.",1380728868,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"These alerts are rendered by a MediaWiki core interface. VisualEditor just calls mw.notify. It does not and should not be modifying those alerts by other means.
+
+Please file a bug in core for this (or move/depends-on this bug).",1380728803,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"en.wp user Mark M comments re the wikitext warning:
+""It wasn't obvious to me how to get rid of the notice. In fact, it popped up and partially cover the ""save"" button in such a way that when I tried to click save, nothing happened, and the notice was still there! For a few seconds I thought I wouldn't be able to save my changes at all, even though I'd removed the wikitext. Fortunately I kept clicking nearby (in frustration) and the notice disappeared. But I would have been helped if there had simply been a ""dismiss"" button, or something similar, that indicates you should click on it to dismiss it. This wasn't obvious to me.""",1376486603,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: Edit notices (and other toolbar notices) should have a close button,"There have been two independent requests for this today on en.wp (one reporting an issue on he.wp).
+
+It was also noted that the close indication should be applied to edit notice popus too.",1375816630,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-6ytamqsj45kuhfs22bx4,task_subcomment,NA
+VisualEditor: <references /> not fully populated but {{reflist}} is,"In some cases it seems that <references /> is not fully populating the references list while {{reflist}} does.
+Example at: At https://en.wikipedia.org/w/index.php?title=Christian_Scott&oldid=566681769
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50094",1375341060,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-cjrfpthlsv4urm5hyivq,task_description,declined
+VisualEditor: <references /> not fully populated but {{reflist}} is,Both lists have the same references for me. Please re-open if you think there is still a problem.,1386608699,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cjrfpthlsv4urm5hyivq,task_subcomment,NA
+VisualEditor: <references /> not fully populated but {{reflist}} is,"Hi Chris, what I see there is the entire section being duplicate, in both view and edit mode. I am probably missing something :)",1378988819,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-cjrfpthlsv4urm5hyivq,task_subcomment,NA
+VisualEditor: <references /> not fully populated but {{reflist}} is,"Not a duplicate, AFAICT.",1375381795,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cjrfpthlsv4urm5hyivq,task_subcomment,NA
+VisualEditor: <references /> not fully populated but {{reflist}} is,"
+
+%%%*** This bug has been marked as a duplicate of bug 50094 ***%%%",1375381498,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-cjrfpthlsv4urm5hyivq,task_subcomment,NA
+Explore performance gains from progressive (JIT?) de-alienation in VisualEditor,"Random idea that might improve load performance: initially alienate the entire document, then progressively convert and dealienate it. This should bring the editor into view quickly and allow the first paragraph to be edited quickly while the rest of the page is still processing.
+
+Possible pitfall: reference numbering and other crazy stuff in MWReferenceNode
+
+See {T76544} for the same idea, but for content blocks.",1375323540,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vpvtoerhlbprn6ollnkr,task_description,open
+VisualEditor: <tt> annotations should be handled by the <code> annotation code,"en.wp user Cryptic C62 comments:
+""Take a look at the text this page. The first two sentences may appear to be identical. If one activates VE, one will find that the first sentence (which employs <tt>) cannot be edited, but the second one (which employs <code>) can. My question is this: If the editor is supposed to be visually intuitive, why are two (almost) visually identical elements handled differently? ""
+
+The page referred to is: https://en.wikipedia.org/w/index.php?title=User:Cryptic_C62/sandbox&oldid=566625027
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375304640,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-sug5dsmkfrgqkbno76mo,task_description,resolved
+VisualEditor: <tt> annotations should be handled by the <code> annotation code,"Change 77389 merged by jenkins-bot:
+Handle <tt> as textStyle/code
+
+https://gerrit.wikimedia.org/r/77389",1375933535,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sug5dsmkfrgqkbno76mo,task_subcomment,NA
+VisualEditor: <tt> annotations should be handled by the <code> annotation code,"Change 77389 had a related patch set uploaded by Esanders:
+Handle <tt> as textStyle/code
+
+https://gerrit.wikimedia.org/r/77389",1375476734,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sug5dsmkfrgqkbno76mo,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"It is possible to insert a substituted template (by just putting in ""subst:whatever"" as its name). This will be saved correctly (substituted), but the diff shown in the review dialog shows the non-substituted wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53201",1375301760,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-l6tecg3euv7s6vvgap3i,task_description,resolved
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Change 129251 merged by jenkins-bot:
+Apply PST when generating diff
+
+https://gerrit.wikimedia.org/r/129251",1398283390,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Change 129251 had a related patch set uploaded by Alex Monk:
+Apply PST when generating diff
+
+https://gerrit.wikimedia.org/r/129251",1398282667,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"VE's API ""diff"" option instantiates its own DifferenceEngine but fails to set the PST option.",1377903454,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Marking as ""minor"" as we don't provide a built-in way for subst: to be added (yet) to transclusion invocations.",1375303837,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Sorry, my bad. I forgot I was using custom JS to generate diffs.",1375303217,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"No, it shows the substituted code.",1375302317,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+VisualEditor: API does not apply PST (pre-save transform) when generating its diff,"Isn't this how normal diffs work? If I replace the sandbox with {{subst:test}}, it just shows the addition of the text ""{{subst:test}}"" when you hit show changes.",1375302025,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-l6tecg3euv7s6vvgap3i,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"en.wp user User:Timwi reports
+
+""On the page [[Earth]], we had the following markup code:
+
+[[File:(filename)|thumb|700px|center| (caption here) |alt= (alt text here) ]]
+
+The VisualEditor parsed this incorrectly and assumed that “alt= (alt text here)” was the ''caption''.
+
+Changing the order of the items fixed this despite having no effect on the rendered page, which indicates that it’s a bug in VisualEditor and not incorrect MediaWiki markup."" http://en.wikipedia.org/w/index.php?title=Earth&diff=566614668&oldid=566595613 
+
+I've done some testing in my sandbox and it seems like the issue is somehow related to the presence of the {{val}} template. I wasn't able to replicate the bug with the {{small}} or {{convert}} templates for example, but I've not done extensive testing with the latter or with any other template.
+
+https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=566618437&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://parsoid-lb.eqiad.wikimedia.org/enwiki/User:Thryduulf/sandbox?oldid=566618437",1375300620,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_description,resolved
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"Done now. Will be deployed tomorrow after a round of RT-testing. Can be reopened, if necessary.",1426634110,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"Change 197120 merged by jenkins-bot:
+T54341: Recover content from non-string tokens for img option alt
+
+[[https://gerrit.wikimedia.org/r/197120]]",1426608678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"Change 197120 had a related patch set uploaded (by Subramanya Sastry):
+WIP: T54341: Recover content from non-string tokens for img option alt
+
+[[https://gerrit.wikimedia.org/r/197120]]
+",1426534930,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"This is a difference in how links are handled in alt-attributes, and nothing to do with templates.
+```
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=Foo ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img alt=""Foo"" resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>Caption here</figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=[[Foo]] ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"">Foo</a> </figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt={{echo|[[Foo]]}} ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""1"":{""wt"":""[[Foo]]""}},""i"":0}}]}'>Foo</a> </figcaption></figure>
+```
+
+However, the PHP parser generates identical HTML for the ""alt=Foo"" and ""alt=[[Foo]]"" cases above.",1425937538,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"This is a difference in how links are handled in alt-attributes, and nothing to do with templates.
+```
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=Foo ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img alt=""Foo"" resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>Caption here</figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=[[Foo]] ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"">Foo</a> </figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt={{echo|[[Foo]]}} ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""1"":{""wt"":""[[Foo]]""}},""i"":0}}]}'>Foo</a> </figcaption></figure>
+```
+
+However, the PHP parser generates identical HTML for the ""alt=Foo"" and ""alt=[[Foo]]"".",1425937523,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"This is a difference in how links are handled in alt-attributes, and nothing to do with templates.
+```
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=Foo ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img alt=""Foo"" resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>Caption here</figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt=[[Foo]] ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"">Foo</a> </figcaption></figure>
+
+[subbu@earth tests] echo '[[File:Foo.jpg|thumb|Caption here|alt={{echo|[[Foo]]}} ]]' | node parse --fetchConfig false --normalize=parsoid
+<figure class=""mw-default-size"" typeof=""mw:Image/Thumb""><a href=""File:Foo.jpg""><img resource=""./File:Foo.jpg"" src=""//upload.wikimedia.org/wikipedia/commons/0/06/Foo.jpg"" height=""144"" width=""220""/></a><figcaption>alt=<a rel=""mw:WikiLink"" href=""Foo"" title=""Foo"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""1"":{""wt"":""[[Foo]]""}},""i"":0}}]}'>Foo</a> </figcaption></figure>
+```",1425937447,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"The problem seems to be with the link that the val template emits and Parsoid is somehow barfing on it. Can be reproduced with the following reduced test case:
+``` [[File:Foo.jpg|thumb|Caption here|alt=This {{echo|[[will]]}} break]]```
+Compare with output of
+``` [[File:Foo.jpg|thumb|Caption here|alt=This {{echo|will not}} break]]```",1423003789,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,"Never mind. My eyes deceived me. The following snippet still parses incorrectly.
+
+[[File:Solar Life Cycle.svg|thumb|700px|center|The life cycle of the Sun|alt=14 billion year timeline showing Sun's present age at {{val|4.6|ul=byr}}; from {{val|6|u=byr}} Sun gradually warming, becoming a red dwarf at, ""soon"" followed by its transformation into a white dwarf star]]",1406236435,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Images: Links in alt (and maybe other) attributes of images generates incorrect HTML,Verified fixed in deployed Parsoid version.,1406236095,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bcphrwlve5fbhq4ltxr3,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375286580,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-y754cxtupebi6bfunc3e,task_description,invalid
+Broken browser plugins cause cruft to be injected into the page (tracking),"If you don't replace a tracking bug with anything, you lose a useful feature to navigate between tasks…",1540255797,PHID-USER-4z6eerx3m7iocsrcpku5,True,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),Tracking bugs existed as a workaround to Bugzilla's shortcomings. There's no utility in keeping this around now.,1524218709,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),">>! In T54327#1948228, @Jdforrester-WMF wrote:
+>>>! In T54327#1948146, @Nemo_bis wrote:
+>> How to share the blacklist (or whatever cleanup method VisualEditor is currently using) with other consumers of Parsoid, such as T124152?
+> 
+> They should sub-class VisualEditor, which is tracked in {T105447} which I've now linked that to.
+
+Makes sense. What if someone else, maybe outside MediaWiki, desired to use Parsoid for two-way conversion? Should everyone subclass VisualEditor or is this sort of HTML/wikitext cleanup of more general use?",1453673063,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),">>! In T54327#1948146, @Nemo_bis wrote:
+> How to share the blacklist (or whatever cleanup method VisualEditor is currently using) with other consumers of Parsoid, such as T124152?
+
+They should sub-class VisualEditor, which is tracked in {T105447} which I've now linked that to.",1453306858,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"How to share the blacklist (or whatever cleanup method VisualEditor is currently using) with other consumers of Parsoid, such as T124152?",1453304786,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"What is this tracking, nowadays?",1432053265,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"I wonder if https://ru.wikipedia.org/?diff=65612328 is another instance of this, or if it's a copy-paste bug instead.",1410976801,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"Added #53315 for texts looking like telephone numbers changed in <a href=""tel:..."">...</a>",1377428723,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+Broken browser plugins cause cruft to be injected into the page (tracking),"On en wikipedia most of these are detected by
+http://en.wikipedia.org/wiki/Special:AbuseFilter/345
+Other common cases include
+myEventWatcherDiv
+QuickiWiki Look Up
+application/x-datavault
+end_of_the_skype_highlighting
+inlineAdmedialink
+_clearly_component
+ktg6us78hf8vdu7
+
+Most are not visible the but ktg6us78hf8vdu7 makes a right mess trying to add javascript links everywhere
+http://en.wikipedia.org/w/index.php?title=Shane_Watson&diff=prev&oldid=568280885",1376399632,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-y754cxtupebi6bfunc3e,task_subcomment,NA
+VisualEditor: Media items are clearing templates (or they're being forced to width:100%?),"Screenshot
+
+Adding an image with caption besides a list creates whitespace in edit mode, see screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/116._Panzer-Division_(Wehrmacht)
+
+**Attached**: {F11788}",1375271820,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-xoiz3tzy2fgdd4xhxob7,task_description,resolved
+VisualEditor: Media items are clearing templates (or they're being forced to width:100%?),"This is caused by bug 51708 – all inline templates assume 100% width, which breaks all floated items.
+
+*** This bug has been marked as a duplicate of bug 51708 ***",1394223928,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xoiz3tzy2fgdd4xhxob7,task_subcomment,NA
+"VisualEditor: Reference defined inside a reference list but of a different group inside template appears as part of the template and also in the appropriate reference list, but blank this time","**Author:** `kwwilliams`
+
+**Description:**
+In http://en.wikipedia.org/w/index.php?title=List_of_record_charts&oldid=566209687, notice how Note 1 gets transformed in the string ""1.0.1.1"" and the actual contents of Note 1 becomes reference 19, which is completely unused in the article body.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53486",1375225080,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ydvvzyrpkompusxbw5gr,task_description,open
+"VisualEditor: Reference defined inside a reference list but of a different group inside template appears as part of the template and also in the appropriate reference list, but blank this time","Clarify the title to explain what I think is happening:
+
+| VisualEditor: Reference defined inside a reference list but of a different group inside template appears as part of the template and also in the appropriate reference list, but blank this time",1377817614,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ydvvzyrpkompusxbw5gr,task_subcomment,NA
+"VisualEditor: Reference defined inside a reference list but of a different group inside template appears as part of the template and also in the appropriate reference list, but blank this time",I can confirm this is still happening.,1377815025,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ydvvzyrpkompusxbw5gr,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","When we edit using the visual editor, we still get
+mw.config.get( 'wgAction' ) === 'view'
+instead of
+mw.config.get( 'wgAction' ) === 'edit'
+
+See also
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070603.html
+which quotes
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070601.html
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+* {T53421}
+* {T55746}
+* {T55441}",1375206000,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-7te6uik6zxfmwlua2dgh,task_description,resolved
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","This is now mostly done, for single edit tab wikis.",1455664404,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","(per https://phabricator.wikimedia.org/T55441#962602)
+
+I agree. I don't think it's realistic or desirable to change the url of the editor. Instead we should (eventually) change the default. We can support permalinks for when the url given is semantically related to VisualEditor, but in most cases that is not the case.
+
+There are many cases where the link itself has no relation to an editor, but we do want to send traffic to VisualEditor for new users (when configured as default):
+* red links generated by the parser.
+* edit links generated by templates.
+* edit links created by extensions and gadgets.
+* third party sites.
+* existing content and discussions.
+
+The majority of those links cannot be feasibly changed, with the exception of those generated by the parser as red links. To change those, the parser would need access to user preferences (which fragments the cache) and the parser would need access the target page content model (which requires additional expensive queries, and is also variable; so it would require cascading cache invalidation).
+
+Instead of changing the url of the ""Edit"" or ""Create"" tab in the interface (and providing secondary links for other editors), it probably makes more sense to hook into EditAction (action=edit) and change the default server-side (based on page content model, and current user preferences). Then, we can use an optional query parameter (e.g. action=edit&editor=visualeditor) in case a direct permanent is wanted. Such as when switching between the editors, or when otherwise relying on exact behaviour (e.g. browser tests and gadgets).",1433993930,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","(In reply to Helder from comment #1)
+> For the sake of solving bug 51421, maybe it could use ""action=vedit""?
+
++1",1397517663,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""",See also bug 53746 comment 3.,1382125536,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","Another reason why the current method is not ideal, taken from
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Categories/reply_(8)
+
+>Lots of template transclusions also offer a specific edit link.
+>Their action uses only the wiki code editor. If both actions
+> ""edit"" and ""editVE"" were merged into a single one (with a simple
+> switch to show either the editable preview or the wiki code) it
+> would be simpler. And the ""Show preview"" button could disappear
+> below the wiki editor (it would just remain a ""Save page"" button),
+> but the ""Save"" button could also show the actual rendering
+> without the limitations of the editable preview.",1381609456,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+"VisualEditor: VE should use the existing ""action"" URL parameter instead of the new ""veaction""","For the sake of solving bug 51421, maybe it could use ""action=vedit""?",1375207110,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-7te6uik6zxfmwlua2dgh,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"When a page has pending edits and it is opened for editing using VisualEditor, there is a dropdown box with a notice about this.  When a page has a template or a file with pending changes is opened for editing, the dropdown box does not appear.
+
+An example on the Russian Wikipedia:
+https://ru.wikipedia.org/wiki/%D0%98%D1%80%D0%B3%D0%B8%D1%88
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52440",1375204500,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-rkr7k7s24b2ie267wdh5,task_description,resolved
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"Change 123875 merged by jenkins-bot:
+Show pending changes notice about unstable transclusions in VE
+
+[[https://gerrit.wikimedia.org/r/123875]]",1422422861,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"(In reply to Alex Monk from comment #6)
+> (In reply to James Forrester from comment #5)
+> > (In reply to Alex Monk from comment #3)
+> > > Shouldn't this appear on the wikitext editor too then?
+> > 
+> > Maybe create a further bug for that in FlaggedRevisions?
+> 
+> I just noticed that it was already made - by you. And it's what this bug is
+> marked as depending on.
+
+Ha. Never mind me. :-)",1396644576,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"(In reply to James Forrester from comment #5)
+> (In reply to Alex Monk from comment #3)
+> > Shouldn't this appear on the wikitext editor too then?
+> 
+> Maybe create a further bug for that in FlaggedRevisions?
+
+I just noticed that it was already made - by you. And it's what this bug is marked as depending on.",1396644489,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"(In reply to Alex Monk from comment #3)
+> Shouldn't this appear on the wikitext editor too then?
+
+Maybe create a further bug for that in FlaggedRevisions?",1396632349,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"Change 123875 had a related patch set uploaded by Alex Monk:
+Show pending changes notice about unstable transclusions in VE
+
+https://gerrit.wikimedia.org/r/123875",1396625665,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,Shouldn't this appear on the wikitext editor too then?,1396622745,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"Yes, this is intentional (as the tool interferes with VisualEditor and will need re-writing/merging into VE to work properly).
+
+The notice above the page having transcluded files or templates with outstanding changes feels like one of the things that should appear in the wikitext page's edit notices (and so on VisualEditor's panel too) - not sure why it doesn't. Is this a Pending Changes bug?",1375216355,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices,"Specifically, not only does the dropdown box not appear, but the notice that was on the page before clicking ""edit"" disappears, leaving absolutely no notice.",1375207442,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-rkr7k7s24b2ie267wdh5,task_subcomment,NA
+Improve nowiki escaping of template arguments by using global context,"When an unmatched literal square bracket is used in the title of a reference, Parsoid or VisualEditor encloses it in a nowiki tag.
+
+Example on the live wiki: https://en.wikipedia.org/w/index.php?title=Wikipedia&diff=566045928&oldid=566042453#cite_ref-209 (line 360)
+Examples in testing: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=566402676&oldid=566401436
+
+It is possible this is a reappearance of or related to T45067
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T45067}
+{T52331}",1375178760,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-x4ddesfyx6gxnu6ahuf6,task_description,open
+Improve nowiki escaping of template arguments by using global context,"Yes, this is a known problem.  There are two different forms of nowiki escaping that goes on in Parsoid.  One is applied to text strings (the common kind that appears around [[foo]] when typed literally).
+
+The one in this bug report is applied to transclusion parameters to prevent literal characters messing up transclusion parse.
+
+Ex: If {{tpl|foo|bar}} is editd to {{tpl|[[foo|bar]]}}, then the ""[[foo"" and ""bar]]"" have to be wrapped in nowikis to prevent ""[[foo|bar]]"" from being parsed as a wikilink.
+
+The current limitation of this second form of nowiki escaping is that it only checks arguments one at a time.  So, it conservatively escapes ""[foo"" in one argument right now without looking at the global context of all arguments which is why you see the nowiki escapes there.
+
+To be fixed.",1375200325,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-x4ddesfyx6gxnu6ahuf6,task_subcomment,NA
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),"**Author:** `sandrobt.wiki`
+
+**Description:**
+The (visual)edit button in a diff (such as http://it.wikipedia.org/w/index.php?title=Kawakami_Gensai&diff=20609681&oldid=18301858) makes you edit the last version (in the example above the edit button gives the link http://it.wikipedia.org/wiki/Kawakami_Gensai?veaction=edit), whereas clicking on edit source makes you edit the old version (the newest of the two compared versions).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375161360,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pey4kjm5sey6cllpuym2,task_description,resolved
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),"This was fixed some time ago, it appears.",1397598107,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pey4kjm5sey6cllpuym2,task_subcomment,NA
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),As far as I can tell the edit source and edit links point to the same oldid. Is this bug still valid?,1397523999,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-pey4kjm5sey6cllpuym2,task_subcomment,NA
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),This looks to be possibly the same issue as bug 51364,1376475898,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-pey4kjm5sey6cllpuym2,task_subcomment,NA
+VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one),Confirming this -  http://it.wikipedia.org/w/index.php?title=Salamandrina_terdigitata&diff=60451620&oldid=57566108 .,1375291261,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-pey4kjm5sey6cllpuym2,task_subcomment,NA
+VisualEditor: Subpages' link to their parent in the page strapline (#contentSub) get hidden but are still there,"Steps to reproduce:
+
+Go to any page that is a subpage, such as a user sandbox. Observe the link to the parent page, located just under ""From Wikipedia..."". Activate VE. Observe that the aforementioned link disappears.
+
+Found in firefox 22, chrome 28, in both monobook and vector. Screenshot at https://en.wikipedia.org/wiki/File:VE_Phantom_Link.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54325
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58063",1375131300,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jjtln7nquqmd5je6fmy3,task_description,resolved
+VisualEditor: Subpages' link to their parent in the page strapline (#contentSub) get hidden but are still there,"Change 107133 merged by jenkins-bot:
+Hide #contentSub properly
+
+https://gerrit.wikimedia.org/r/107133",1389633321,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jjtln7nquqmd5je6fmy3,task_subcomment,NA
+VisualEditor: Subpages' link to their parent in the page strapline (#contentSub) get hidden but are still there,"Change 107133 had a related patch set uploaded by Jforrester:
+Hide #contentSub properly
+
+https://gerrit.wikimedia.org/r/107133",1389626443,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jjtln7nquqmd5je6fmy3,task_subcomment,NA
+VisualEditor: Render absolute URLs as links inside the editor,"When you copy & paste a link into VisualEditor, it will not be recognized as a URL, but will appear as plaintext. The MediaWiki parser does render it as a clickable link, of course.
+
+This is annoying especially for references, because you might be confused why your link you're adding as a citation doesn't appear to be clickable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52204",1375129740,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-7wx6pzrxilelrduf5qci,task_description,resolved
+VisualEditor: Render absolute URLs as links inside the editor,"Merging this into 52204 as it's a sub-request.
+
+*** This bug has been marked as a duplicate of bug 52204 ***",1394489652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7wx6pzrxilelrduf5qci,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Adding ""ISBN 0-471-17864-0"" doesn't render the ISBN as a link.  This is more important in the reference tool, but should work on all rich text surfaces.
+
+See also:
+* {T54241}
+* {T63558}",1375057320,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-df6digqa5tkg4x3pko26,task_description,resolved
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Filed T109498 for the remaining ""pasted ISBN"" bit of this bug.",1439925713,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Change 230146 merged by jenkins-bot:
+Detect paste of wikitext and convert it
+
+[[https://gerrit.wikimedia.org/r/230146]]",1439913324,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Change 230146 had a related patch set uploaded (by Jforrester):
+Detect paste of wikitext and convert it
+
+[[https://gerrit.wikimedia.org/r/230146]]
+",1439910967,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Typed and pasted URLs are now merged in core.
+
+*Pasted* RFC/PMID/ISBN links is implemented  (https://gerrit.wikimedia.org/r/230146 is in review).
+
+Currently missing: *typed* RFC/PMID/ISBN links are not autolinked.",1439910724,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","Autolink when typing has been merged.  Autolink after pasting is in review, but the functionality is complete.",1439487915,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",">>! In T54204#1522662, @Amire80 wrote:
+>>>! In T54204#1507599, @ssastry wrote:
+>> T107433 (merged as a dupe here) seems to be a major source of nowikis on frwiki as per https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis/Nowiki
+> 
+> In Hebrew as well.
+
+@cscott is working on patches for this ( https://gerrit.wikimedia.org/r/#/c/230146/ and https://gerrit.wikimedia.org/r/#/c/230145/ )",1439133300,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",">>! In T54204#1507599, @ssastry wrote:
+> T107433 (merged as a dupe here) seems to be a major source of nowikis on frwiki as per https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis/Nowiki
+
+In Hebrew as well.",1439132488,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",T107433 (merged as a dupe here) seems to be a major source of nowikis on frwiki as per https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis/Nowiki,1438716820,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",*** Bug 52241 has been marked as a duplicate of this bug. ***,1394489652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","(In reply to comment #5)
+> Magic links are pretty evil.
+
+They are one of many unusual pieces of wiki syntax. And it is quite 'wikipedia' specific functionality which could be dropped from core.
+
+> Explicitly marking links with a parser function
+> is
+> much more sensible.
+
+If the goal is to replace them with a more standard syntax, a 'isbn' interwiki pointing to special:booksources/$1 would be syntax that is more similar and conceptually closer also. Ideally it would render as an internal link when the interwiki points to the local special page.
+
+> I'm not sure supporting magic links in VisualEditor is a
+> good idea.
+
+What is the impact of not supporting these magic links on a) big wikipedias like enwp where these magic works will often be used from a cite template (which can be changed without editing millions of pages) and b) small wikis which are imo more likely to use these magic words in raw wikitext.
+I.e. How many bot edits are needed, and how many tools need to be revised.",1376794728,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",Magic links are pretty evil. Explicitly marking links with a parser function is much more sensible. I'm not sure supporting magic links in VisualEditor is a good idea.,1376787661,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","(In reply to comment #3)
+
+> 
+> Clicking on the non-hyphenated ISBN, however, results in a failed attempt to
+> go
+> directly to the ISBN search page, with this resulting error:
+> 
+> Error
+> 404 – File not found
+> http://en.wikipedia.org/Special:BookSources/9781234567890
+> We could not find the above page on our servers.
+> Did you mean to type
+> http://en.wikipedia.org/wiki/Special:BookSources/9781234567890? You will be
+> automatically redirected there in five seconds.
+> Alternatively, you can visit the Main Page or read more information about
+> this
+> type of error.
+
+The incorrect URI is bug 48915 (it's even worse for non-English wikis as it always suggests a page on en.wp). Although I presume what is wanted is for the ISBN to be edited rather than taking you to the ISBN search page? If so then getting to that page from a right click/ctrl+click would potentially be useful.",1376064405,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","This works for me, but perhaps not as expected.
+
+You can add:
+
+PMIDs:  http://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=563393942&oldid=563393897
+
+ISBNs without hyphenation:  http://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=567704513&oldid=564410882
+
+ISBNs with hyphens:  http://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=567704681&oldid=567704513
+
+Exactly like the classic wikitext editor, these do not display as being links until after they are saved.  They do work correctly when saved.
+
+After they have been saved, if you go back into VisualEditor to edit again, then the PMID and hyphenated ISBNs are not editable or clickable (except to select the whole element).  Changes to them must be made by deleting the whole thing and retyping from scratch.  
+
+Clicking on the non-hyphenated ISBN, however, results in a failed attempt to go directly to the ISBN search page, with this resulting error:
+
+Error
+404 – File not found
+http://en.wikipedia.org/Special:BookSources/9781234567890
+We could not find the above page on our servers.
+Did you mean to type http://en.wikipedia.org/wiki/Special:BookSources/9781234567890? You will be automatically redirected there in five seconds.
+Alternatively, you can visit the Main Page or read more information about this type of error.",1375982678,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link","I guess the other Magic links http://www.mediawiki.org/wiki/Markup_spec/BNF/Magic_links
+for RFC and PMID should be included here.",1375941068,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+"Automatically recognise bare links and magic links (ISBN/etc.), and display as a link",Discussed at http://en.wikipedia.org/wiki/Wikipedia_talk:VisualEditor#Should_inability_to_edit_ISBNs_be_listed_in_the_limitations_section.3F,1375940866,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-df6digqa5tkg4x3pko26,task_subcomment,NA
+VisualEditor: Invocations of deleted images don't render at all,"**Author:** `wikipedia`
+
+**Description:**
+When a file is deleted and still is being used in an article, this file is shown in the article as a box with a red link in it. Starting VE to remove the link, the link is no more visible and thus cannot be removed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows 7",1375010460,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pw24nueljk2i343joyw2,task_description,resolved
+VisualEditor: Invocations of deleted images don't render at all,"
+
+*** This bug has been marked as a duplicate of bug 50788 ***",1389632313,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pw24nueljk2i343joyw2,task_subcomment,NA
+VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph,"**Author:** `jonathan_haas`
+
+**Description:**
+Steps to reproduce:
+
+1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit
+2. Position the cursor at the start of the page directly before the bold ""T"".
+3. Hit Backspace (to delete infobox)
+4. Hit Ctrl+Z (undo)
+5. Hit Backspace again
+6. Hit Ctrl+Z again
+Repeat as long as you want
+
+Actual result:
+
+On each Ctrl+Z a paragraph more is selected
+
+Expected result:
+
+Selection stays the same, undo should undo the action and not change the selection
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375008900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3wvoqjxuqinfi7bgkax4,task_description,resolved
+VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph,This was fixed in gerrit 115759 as part of fixing bug 57552.,1394503778,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3wvoqjxuqinfi7bgkax4,task_subcomment,NA
+VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph,"**jonathan_haas** wrote:
+
+Deleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2.
+
+In short: The problem is more hidden, but the underlying issue has not been fixed.",1382445971,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3wvoqjxuqinfi7bgkax4,task_subcomment,NA
+VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph,Reproduced.,1375050421,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-3wvoqjxuqinfi7bgkax4,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference","Removing the content from out of a <ref> .. </ref> should prompt the user that they need to delete the reference.  Perhaps a tooltip, or this might be an opportunity to use a hover trick to give the user something to click to acknowledge they intended to delete the ref.
+
+It shouldnt be possible to save with an empty ref, as that is an error condition.
+
+https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&diff=566133128&oldid=566132993
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50609",1375008300,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-tgtxd532icx4mnfll75r,task_description,resolved
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference","Yes, sorry, this was great. Thanks!",1405038215,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference",Ping. Anyone want to answer my question?,1405038076,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference","So Gerrit change 136496 fixed the existing intended behaviour, but didn't go as far as this bug suggests (it just disables the apply button rather than deleting the reference) - should it be changed to delete the reference still?",1401808848,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference",*** Bug 62399 has been marked as a duplicate of this bug. ***,1401479536,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference",See Gerrit change 81438 and Gerrit change 88618,1401476178,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference",length < 4 is a hack and we probably shouldn't be using it…,1401476091,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: On ""applying changes"" in a reference dialog, if the contents are blank, just delete the reference","According to ve.ui.MWReferenceDialog.prototype.onDocumentTransact, this apply button is supposed to be disabled when the length is less than 4. But when I empty the box, the length is 10 so nothing is done.
+
+Anyway, I think we should either:
+* Fix that bug (if it is one) and mark this bug as invalid (or repurposed for fixing it), or
+* Replace that with this idea",1401475699,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-tgtxd532icx4mnfll75r,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","If VisualEditor is default, why after clicking on a red link there's 'action=edit' in url and the source editor runs instead of 'veaction' and VE? I've checked it out on the enwiki and plwiki, but it concerns the rest of phase 2 as well and creating a new page in general. Furthermore, it makes inputboxes ('type=create') incompatible with VE and it can be a bothering problem on some wikis.
+
+**See Also**: {T55441}",1374969780,PHID-USER-gf5juv3z3p75bykrcrhf,False,PHID-TASK-ra3d7l6sbywnzslhiccu,task_description,open
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","This should become feasible after we implement {T223793}. We can probably use a similar mechanism to intercept the targets of inputboxes.
+
+Also, note that a `useve=true` inputbox parameter has been implemented in the meantime: {T89341}.",1558261962,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor",">>! In T54162#2590097, @Elitre wrote:
+> Did SET work affect this...?
+
+Not yet; it will need further work.",1472505814,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor",Did SET work affect this...?,1472457462,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","I don't want to make inputbox suddenly magically different. It's about ordinary users (especially the new sort 'born' after VE deployment) who want to type a new article's name, click on button and voila, start creating their article in VE. In 2 steps, after 1 click, without experience like 'why the markups? oh, I'm switching to VE'. They'd be more likely to give up in this case.
+
+Technically, you may change the default 'action' with 'veaction' or create a new parameter or sth else, it's up to you.",1412440471,PHID-USER-gf5juv3z3p75bykrcrhf,False,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","You can easily point InputBox to VE with a simple hook so that VE can change 'action' to 'veaction'. But that won't make VE magically support all the additional parameters which InputBox uses (e.g. preload, editintro, summary, minor, etc.)",1396642309,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","Ah, I see a process problem with type=fulltext too
+
+inputbox goes to search results, and search results show a red link, which the user would click on to start a new page. e.g.
+
+https://en.wikipedia.org/wiki/Special:Search/this_article_doesnt_exist
+
+I believe that some enhancement will be needed in the InputBox extension to support creating VE or SE articles.
+https://www.mediawiki.org/wiki/Extension:InputBox",1375056651,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor","In the plwiki, we have no important inputbox with 'type=create' in the main nor user namespace, but there are inputboxes in help or project pages which create a new article (for ex. [[pl:Pomoc:Tworzenie nowych haseł#Niniejsza strona]]), and after clicking the button there is 'action=edit&preload=' in url.
+
+Second, whenever we click on a red link in an article (the main), 'action=edit&redlink=1' displays. The default tab is 'Create source', not 'Create'. It's quite surprising for me and for the newbies, I believe.",1375053920,PHID-USER-gf5juv3z3p75bykrcrhf,False,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+"VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor",Could you provide a example of a 'type=create' problem affecting VE?  Is it used on main or user namespace in your wiki?,1375052410,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ra3d7l6sbywnzslhiccu,task_subcomment,NA
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"An editor on en.wp has requested that Ctrl+Y should initiate the redo action. Presently the shortcut is ctrl+shift+z.
+
+In my experience both shortcuts are used in about 50% of applications (Xubuntu Linux) so it would be ideal if both shortcuts could be used.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374931680,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-yocptvdek2u4pm4ssk5d,task_description,resolved
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"Change 116966 merged by jenkins-bot:
+Add cmd/ctrl+y as alternative shortcut for redo
+
+https://gerrit.wikimedia.org/r/116966",1394054746,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yocptvdek2u4pm4ssk5d,task_subcomment,NA
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"Change 116966 had a related patch set uploaded by Catrope:
+Add cmd/ctrl+y as alternative shortcut for redo
+
+https://gerrit.wikimedia.org/r/116966",1394051814,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yocptvdek2u4pm4ssk5d,task_subcomment,NA
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"Add cmd/ctrl+y as alternative shortcut for redo
+https://gerrit.wikimedia.org/r/#/c/116966/",1394038226,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-yocptvdek2u4pm4ssk5d,task_subcomment,NA
+VisualEditor: Add CTRL+Y as a second shortcut for redo,"**jonathan_haas** wrote:
+
+Ctrl+Y is the default undo shortcut in Firefox. It's very confusing that it doesn't work in VE using Firefox.",1375020469,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yocptvdek2u4pm4ssk5d,task_subcomment,NA
+VisualEditor: Come up with something better than .offsetOf(),"We overuse both ""index"" and ""offset"" in our vocabulary, and one of the more cringe-worthy results is the rename of .indexOf() to .offsetOf() in AnnotationSet. We should refactor our vocabulary and rename this to something saner.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374887040,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-y2db4ahscixrwviebqhf,task_description,open
+VisualEditor: Adding support to Grammar/Orthography fixes custom wiki defined button to be applied on texts visually on client side,"**Author:** `nzmoihue`
+
+**Description:**
+I think one nice/needed addition to Visual Editor would be supporting custom wiki defined scripts for fixing text [without interfering with wiki text]. For example on Persian Wikipedia we have an edit tool script [1] [2] that wiki users are very depends on it for fixing article texts and without it Visual Editor would be useless for them.
+
+
+ 1. http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%E2%80%8C%D9%BE%D8%AF%DB%8C%D8%A7:%D8%A7%D8%A8%D8%B2%D8%A7%D8%B1%D9%87%D8%A7%DB%8C_%D9%88%DB%8C%D8%B1%D8%A7%DB%8C%D8%B4%DB%8C
+ 2.http://fa.wikipedia.org/wiki/MediaWiki:Gadget-Extra-Editbuttons-Functions.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374875580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7ljydmhlfgrzwegrjhpj,task_description,open
+VisualEditor: Adding support to Grammar/Orthography fixes custom wiki defined button to be applied on texts visually on client side,"I love this idea.
+
+Wikipedias in several languages have such tools, and everywhere it's implemented differently.
+
+The Hebrew Wikipedia has a fully automatic bot making spelling correction on which there's a wide consensus (with over 700 rules), and it also a gadget that adds a button to make semi-automatic edits when fully automatic edits are not reliable enough. I believe that the tool about which Ebrahim is speaking is similar.
+
+If I'm not mistaken, Russian, Belarusian, Portuguese, Catalan and English Wikipedias have such tools, too, though there are definitely differences in implementation. Almost certainly there are more languages that have such tools.
+
+It may be challenging to make a tool that would work equally well for all languages. Different languages have very different requirements. However, acknowledging that at least some languages needs some kind a framework for this and that not being able to use it is a regression for many users, and providing some standard baseline to work with it will be a good start.
+
+What standard baseline? At least, a standard location for a button that would open such a tool. Another thing that would be useful to everybody would be an agreed API for automated or semi-automated searching and replacing in contentedtiable.
+
+A harder thing to do would be to have a standardized format for replacement rules, though this will require at least a bit of research of the current implementations.
+
+(A general comment: The standardized way of marking the text's language, which Moriel is developing in her GSoC project, should be helpful for such tools. They shall only need to work on the parts that are written in the appropriate language.)",1375135304,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-7ljydmhlfgrzwegrjhpj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"People would like to be able to edit the language links that are coming from Wikidata in the page settings dialog. A link from there to Wikidata would probably also be a good first step.
+
+**See Also**:
+{T59929}
+{T64005}
+{T74178}",1374859560,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-czxsast2el34thkj2xkj,task_description,open
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"(In reply to Elitre from comment #7)
+> Thanks. So should I file a new one, or...?
+
+Filing a new bug about the Wikidata tool destroying your current edit by navigating away sounds like a good plan, yes, sorry. :-)",1393519722,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"Thanks. So should I file a new one, or...?",1393519677,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"(In reply to Elitre from comment #4)
+> Apparently this is how it currently works? You can add links to Wikidata
+> while in VE, but then you'll miss them because the page will be reloaded?
+
+(In reply to Elitre from comment #5)
+> Sorry, rephrasing: You can add items to Wikidata while in VE, but then
+> you'll miss the other edits you made in that VE session since the page will
+> be reloaded.
+
+Yes, the Wikidata team's sidebar JS tool to add to language links ignores the existence of VE (and so breaks things, as you say).
+
+This bug is talking about being able to edit the language links inside VE, in the language panel of the ""page options"" dialog which is currently read-only. It's also meant to cover more cases and features than the sidebar JS tool currently does.",1393519436,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"Sorry, rephrasing: You can add items to Wikidata while in VE, but then you'll miss the other edits you made in that VE session since the page will be reloaded.",1393509066,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"Apparently this is how it currently works? You can add links to Wikidata while in VE, but then you'll miss them because the page will be reloaded?",1393508934,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"(In reply to comment #1)
+> This would be excellent, but potentially quite a lot of work. Would the
+> Wikidata team be interested in exploring with us how this could be done?
+
+Yes :) I don't yet know if/how we can dedicate development time to this but let's talk.",1380546193,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,bug52383 suggests the opposite approach: please do not include such complex logic in VE which is already slow. be so kind to improve the current implementation within the VE project if you feel its hacky.,1375398625,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor,"This would be excellent, but potentially quite a lot of work. Would the Wikidata team be interested in exploring with us how this could be done?",1374862588,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-czxsast2el34thkj2xkj,task_subcomment,NA
+"""loadImages bad"" error on uploading ~85MB .ogv files","**Author:** `molly.white5`
+
+**Description:**
+Twice now I've uploaded .ogv files (made with RecordMyDesktop, if that helps) and gotten a popup that very helpfully informs me, ""loadImages bad"". This appears directly after I choose the file to upload, and I'm guessing it has something to do with the inability to find a thumbnail image? Anyway, at the very least a more descriptive error message might be nice.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374796680,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s536bhjhjcxh5wim4rzu,task_description,invalid
+"""loadImages bad"" error on uploading ~85MB .ogv files","I can't find anything that says ""loadimages"" in either today's UploadWizard nor the UploadWizard of July 2013.",1449164913,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-s536bhjhjcxh5wim4rzu,task_subcomment,NA
+"""loadImages bad"" error on uploading ~85MB .ogv files","**molly.white5** wrote:
+
+Yes, it happens at Special:UploadWizard on Commons. I do not seem to be getting the error on test2.
+
+The files were https://commons.wikimedia.org/wiki/File:RefTools_rework.ogv and https://commons.wikimedia.org/wiki/File:VisualEditor_reference_tutorial.ogv, which are 84.02 and 86.73 MB, respectively.",1374880481,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s536bhjhjcxh5wim4rzu,task_subcomment,NA
+"""loadImages bad"" error on uploading ~85MB .ogv files","Hi Molly,
+where does this happen exactly? http://commons.wikimedia.org/wiki/Special:UploadWizard ? Does it also happen on http://test2.wikipedia.org/wiki/Special:UploadWizard ? Which approx. filesize do these files have?",1374852631,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-s536bhjhjcxh5wim4rzu,task_subcomment,NA
+Allow extension options to be specified in API calls,"The rendering of a page can be affected by user extension options (e.g. their choice of renderer for the Math extension) so we should be able to pass through these options to the API.
+
+This is blocking proper support of the Math extension in VisualEditor.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1374764640,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jksvrmf6seb3lzwf6tsr,task_description,open
+Allow extension options to be specified in API calls,"To do something about this, I think we'd need:
+# Put these extension options in ParserOptions, somehow. The extension would also have to depend on the ParserOptions rather than user preferences or the like to determine behavior.
+# Be able to query the options available in ParserOptions, along with their API data types. And be able to set an option generically by name.
+# Then ApiParse and other modules can use this to add relevant parameters for the parser options.",1472056142,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-jksvrmf6seb3lzwf6tsr,task_subcomment,NA
+Allow extension options to be specified in API calls,[Setting normal prio as bug 51698 (blocked by this) is also normal prio.],1395107815,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jksvrmf6seb3lzwf6tsr,task_subcomment,NA
+Allow extension options to be specified in API calls,See bug 51698,1374764852,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jksvrmf6seb3lzwf6tsr,task_subcomment,NA
+VisualEditor: ve.ui.Context#toolbar is null in MediaWiki,"Following the documentation[1] starting at ve.ui.Surface (from ve.instances[0]) one would go to #getContext and access .toolbar. But though that property is defined, it is set to null.
+
+I'm not sure why, but apparently our MediaWiki's init is instantiating its own and is only accessible from ve.init.mw.ViewPageTarget#toolbar (ve.init.mw.targets[0].toolbar).
+
+It probably shouldn't have to instantiate its own one, and certainly not make it inaccessible to the rest of VE.
+
+
+[1] https://doc.wikimedia.org/VisualEditor/master/#!/api/ve.ui.Surface
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374716460,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-27h7itsrfluxqubhrje3,task_description,resolved
+VisualEditor: ve.ui.Context#toolbar is null in MediaWiki,"There used to be a .toolbar property because the context had its own (local) toolbar to show the contextual tools in. This has been replaced with ContextWidget (which isn't a toolbar) which groups ContextItemWidget (which aren't tools), and now there is no .toolbar property.",1412590622,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-27h7itsrfluxqubhrje3,task_subcomment,NA
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out","It seems that Chrome 28 does not display the ""Minor Edit"" and ""Watch This Page"" checkboxes on the save page form. This does work in Firefox 22. Does not seem skin related - Vector and Monobook have the same problem in either browser
+
+Steps to reproduce:
+- Open any page in edit mode.
+- Make a small change, press Save page.
+- (Firefox): There will be checkboxes stating ""Watch this page"" and ""This is a minor edit""
+- (Chrome): Those checkboxes are not present.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374688740,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-egsozcckjwhatubn2cu7,task_description,invalid
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out",Then this is not the bug I thought it was; fixing settings.,1374693622,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-egsozcckjwhatubn2cu7,task_subcomment,NA
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out",Do'h! Logging in does indeed appear to be the problem - I restarted Chrome right before testing a few things iand forgot to log back after i did. Sorry for that - seems to be a storm in a teacup.,1374693512,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-egsozcckjwhatubn2cu7,task_subcomment,NA
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out","(In reply to comment #0)
+> It seems that Chrome 28 does not display the ""Minor Edit"" and ""Watch This
+> Page""
+> checkboxes on the save page form. This does work in Firefox 22. Does not seem
+> skin related - Vector and Monobook have the same problem in either browser
+> 
+> Steps to reproduce:
+> - Open any page in edit mode.
+> - Make a small change, press Save page.
+> - (Firefox): There will be checkboxes stating ""Watch this page"" and ""This is
+> a
+> minor edit""
+> - (Chrome): Those checkboxes are not present.
+Are you sure you're logged in in both browsers? If you're logged out in Chrome, then you'd be getting the expected behavior for anons (which changed recently, because we're not using smarter code that's more consistent with how the old editor does it).",1374693045,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-egsozcckjwhatubn2cu7,task_subcomment,NA
+"VisualEditor: ""Minor Edit"" and ""Watch this page"" checkboxes on the save page form are not visible when logged out",This is actually due to an underlying bug in the new code just pushed out an hour ago; we've just fixed this (reload if it doesn't show).,1374692833,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-egsozcckjwhatubn2cu7,task_subcomment,NA
+VisualEditor: Undo does not invalidate cached wikitext diff content,"English Wikipedia user Atethnekos reports: 
+""If I make 2 changes, review changes, exit review/save dialog, undo last change, and then review changes again, the review shows both changes, though saving only saves the first.""
+
+Steps to reproduce:
+1. Make two changes to a page in VE
+2. Undo one change
+3. Click save and review your changes. 
+-Expected behaviour: Only the first change is shown
+-Actual behaviour: Both changes are shown.
+4. Save the page. Only the first change has been saved.
+
+This means that the review your changes is incorrect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374660840,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-csda6oirljibl6xuzg3w,task_description,resolved
+VisualEditor: Undo does not invalidate cached wikitext diff content,"Yes, this is now fixed, almost certainly as part of the re-write Roan did last month.",1392062273,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-csda6oirljibl6xuzg3w,task_subcomment,NA
+VisualEditor: Undo does not invalidate cached wikitext diff content,Can't replicate.,1391916784,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-csda6oirljibl6xuzg3w,task_subcomment,NA
+VisualEditor: Pending Changes dropdown overlaps toolbar in Monobook,"Reported by Atethnekos on EnWiki, who also provided an image: https://en.wikipedia.org/wiki/File:Platovesample1.png
+
+""When I edit a page with the pending changes revision dropdown, and I am scrolled to the very top, the dropdown and the VE page settings link become mangled.  See highlight in included image.  Firefox 22 on Win7 Pro SP1.""
+
+I can reproduce this in both Firefox 22 and Chrome 28. The issue seems specific to the Monobook skin - Vector renders the pending changes dropdown somewhat lower in both browsers.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374647880,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-tl42tulmp4okf7khych6,task_description,resolved
+VisualEditor: Pending Changes dropdown overlaps toolbar in Monobook,Sorry about this; the good news is that we just fixed this in gerrit 75545 which will go out in about eight hours or so - that drop-down menu will be hidden once you're inside VisualEditor mode (whatever your skin).,1374648228,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tl42tulmp4okf7khych6,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"Wikitext appearing in transclusion dialog
+
+The underlying cause of this might be covered in bug 48231 or bug 51217 or others ... I thought I saw a bug about this, but cant find it now.
+
+[[template:multicol]] with wikisyntax inside it results in the attached screenshot, with wikitext visible in the transclusion dialog as 'Content' blocks.
+
+https://nl.wikipedia.org/wiki/Gebruiker:John_Vandenberg/test?veaction=edit
+
+Section headers & list items also cause this; see the last block here:
+https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=565567699&veaction=edit
+
+If it helps, this issue is present on one of the parsoid topfails:
+
+https://nl.wikipedia.org/wiki/Eerste_divisie_1996/97?veaction=edit
+
+BeginKolommen occurs on nlwp 3047 times.  11362 times in enwp.  8861 times in eswp. 40985 times on itwp!, which is roughly 4% of the content pages.
+
+Confirmed this is happening on every itwp invocation that I edit
+https://it.wikipedia.org/wiki/Speciale:PuntanoQui/Template:Colonne
+e.g.
+https://it.wikipedia.org/wiki/Aeroplano?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11763}",1374638040,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-vb4syhceqgegacimzles,task_description,open
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"(In reply to comment #5)
+> (In reply to comment #4)
+> > > 'nl:Eerste divisie 1996/97' is on the parsoid topfails list
+> > > 
+> > > http://parsoid.wmflabs.org:8001/topfails
+> > > 
+> > Oh, I see. It's not any more now :(
+> 
+> It is on page two of 16
+> 
+> http://parsoid.wmflabs.org:8001/topfails/2
+> 
+Aha! Found it.
+
+> I have no idea if the {{BeginKolommen}} or tables within it have anything to
+> do
+> with the semantic failure; just thought I should mention it.
+That doesn't appear to be the case: looking at the RT diff (which you get to by clicking on the page name), it's mostly related to the tables on the page: http://parsoid.wmflabs.org/_rt/nl/Eerste_divisie_1996/97",1374640898,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"(In reply to comment #4)
+> > 'nl:Eerste divisie 1996/97' is on the parsoid topfails list
+> > 
+> > http://parsoid.wmflabs.org:8001/topfails
+> > 
+> Oh, I see. It's not any more now :(
+
+It is on page two of 16
+
+http://parsoid.wmflabs.org:8001/topfails/2
+
+I have no idea if the {{BeginKolommen}} or tables within it have anything to do with the semantic failure; just thought I should mention it.",1374640614,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"(In reply to comment #3)
+> I think it is impressive that VE handles it
+> 
+This is mostly thanks to Parsoid handling this case very well, and VE simply building a UI around it :)
+
+> 'nl:Eerste divisie 1996/97' is on the parsoid topfails list
+> 
+> http://parsoid.wmflabs.org:8001/topfails
+> 
+Oh, I see. It's not any more now :(
+
+> Here is an itwp example where multicol consumes most of the page, and should
+> probably be removed.
+> 
+> https://it.wikipedia.org/wiki/Campagna_%28comune%29?veaction=edit
+Yes. I just fixed that page.",1374640208,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"I think it is impressive that VE handles it
+
+'nl:Eerste divisie 1996/97' is on the parsoid topfails list
+
+http://parsoid.wmflabs.org:8001/topfails
+
+Here is an itwp example where multicol consumes most of the page, and should probably be removed.
+
+https://it.wikipedia.org/wiki/Campagna_%28comune%29?veaction=edit",1374639358,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"{{BeginKolommen}} generates the beginning of a table, and {{EindeKolommen}} generates the end of that table. All content between those two is treated as one template call. This is expected behavior in the current implementation, and is exactly the same as succession boxes and all other templates that generate openings and closings separately (multipart templates).
+
+It would be nice if we could let users edit these in a nicer way, especially considering that some (but not all) of the wikitext blocks are actually innocuous wikitext that VE could reasonably edit, but right now we can't. This is part of the reason why multipart templates suck.
+
+What is the Parsoid topfail thing you're talking about? There's no link to the failure and it seems unrelated to this issue.
+
+
+Not closing this as INVALID or whatever because this is something we should actually handle better.",1374639024,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE,"Editing the wikitext appears to function correctly, which is good news.
+https://it.wikipedia.org/w/index.php?title=Matematica&diff=60342095&oldid=59678552",1374638806,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-vb4syhceqgegacimzles,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,"The bug 51905 made me realize of a potential problem. When a media, say an image, is inserted, sometimes it may be inserted outside the field of view of the user, and this may lead some users to think that it wasn't inserted at all, causing aborted edits, confusion, frustration, and even bad edits. For example if there is an infobox in the article, or a bunch of images aligned to the right, then if the user inserts an image, in many cases it will be inserted below all this, and the user will not see it without scrolling the screen.
+
+The solution to this potential problem is, I think, fairly simple: make the VisualEditor detect if the image is in the field of view of the user, and if it's not, then scroll the screen so that it is!
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58091",1374614520,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-3wggiaj4uckt3tln426a,task_description,resolved
+Scroll to an item when it is selected e.g. when it has been newly inserted,"Checked all Insert menu options in beta (Chrome, FF35, and Safari).
+
+What was checked 
+
+-  a cursor placed at the top/bottom of a page and Insert
+-  a cursor placed at the bottom of a page - and scroll up and then 'Insert'
+-  'Insert' options for Media Caption
+-  'Undo/Redo' with different cursor positions
+",1427741121,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,"Change 200243 merged by jenkins-bot:
+Scroll the selection into view when it is outside the window
+
+[[https://gerrit.wikimedia.org/r/200243]]",1427668761,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,"Change 200243 had a related patch set uploaded (by Mooeypoo):
+Scroll to newly inserted elements
+
+[[https://gerrit.wikimedia.org/r/200243]]
+",1427494007,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,"A auto-disappearing popup notice ""Your image has been inserted; scroll down to see it."" would help.",1374703747,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+Scroll to an item when it is selected e.g. when it has been newly inserted,I experienced the same problem in bug 51863.,1374703273,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-3wggiaj4uckt3tln426a,task_subcomment,NA
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"When an image file is included directly in an article (i.e not as a thumbnail and not in a frame) with an unclosed <center> tag in the caption causes Visual Editor to not render any page content after the image.
+
+See https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox2&oldid=565498603 for an example.
+
+All the following conditions must be true to see this bug:
+* Image must not be a thumbnail or in a frame
+* The image caption must contain an unclosed html tag specifying text alignment in the caption. Tested with <center>, <p align=""center""> and <div align=""right"">
+* The image placement (left, right or center) must be specified
+
+The bug does not occur with an unclosed italic html tag. I haven't tested with other tags.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374598740,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gru24gdbzlh5sitams7s,task_description,resolved
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"As we discussed and confirmed on IRC, this is not happening in production right now. So, I am going to mark this resolved-fixed. Please reopen if a similar error shows up.",1380746942,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gru24gdbzlh5sitams7s,task_subcomment,NA
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"Will provisionally mark this as in-review, then (you can see that it's still happening with production Parsoid, though that may be cache errors).",1380746013,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gru24gdbzlh5sitams7s,task_subcomment,NA
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"Unclosed tags in image caption is not that infrequent unfortunately -- the difference between <center> and <i>/<b> tags is that the former is a block tag and the latter is an inline tag. So, any other block tag that is unclosed will cause the same issue. 
+
+That said, I am surprised that this problem showed up in the first place since Parsoid has had support to deal with unbalanced tags for a long time: https://gerrit.wikimedia.org/r/#/c/43384/
+
+This was a bit of a hacky support. More robust and improved support for this is coming in https://gerrit.wikimedia.org/r/#/c/83216/
+
+So, unsure what happened here with this bug.",1380745593,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gru24gdbzlh5sitams7s,task_subcomment,NA
+VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails,"Forgot to note that although this combination of conditions is presumably uncommon, it was first observed in the wild at https://en.wikipedia.org/w/index.php?title=Typographer_%28typewriter%29&oldid=565431177",1374599024,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-gru24gdbzlh5sitams7s,task_subcomment,NA
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,"first table at [[Comparison of container formats]] rendered in a 1024px wide window. Firefox 22 on Linux
+
+In VisualEditor the editing window does not horizontally scroll to accommodate wide tables. Table cells and their contents render as if the window did scroll, but as it does not they are truncated.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51755
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51820
+
+**Attached**: {F11662}",1374578220,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-d3oejnwggmk2whlojm2x,task_description,resolved
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,This works correctly these days. The page is horizontally scrollable.,1538407902,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-d3oejnwggmk2whlojm2x,task_subcomment,NA
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,it would be nice to have a fix for horizontal scrolling for wide tables,1434875532,PHID-USER-yftvcvsb36qrmx4iohsm,False,PHID-TASK-d3oejnwggmk2whlojm2x,task_subcomment,NA
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,"en.wp user Cryptic C62 comments:
+""VE does not correctly render any table wider than the screen, nor does it allow horizontal scrolling. This effect seems to extend to any wide element, including math formulas, images, transclusions, and text with non-breaking spaces. Some other findings:
+
+* A horizontal scroll bar does appear when hovering over some elements with a mouseover effect, specifically images and uneditables (Strangely, the scroll bar does not appear when hovering over the {{Details}} template in this example). Scrolling can then occur if you have a clickable mousewheel.
+
+* By placing the text cursor near the visible end of wide text, and pressing the right arrow key, it is possible to sneak the text cursor off of the page.""
+
+Test cases: https://en.wikipedia.org/w/index.php?title=User:Cryptic_C62/sandbox&oldid=567261009",1375714875,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-d3oejnwggmk2whlojm2x,task_subcomment,NA
+VisualEditor: editing window does not horizontally scroll for wide tables or other elements,"Comment on attachment 12931
+first table at [[Comparison of container formats]] rendered in a 1024px wide window. Firefox 22 on Linux
+
+Fix MIME type",1374682835,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-d3oejnwggmk2whlojm2x,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"When VisualEditor inserts an image, the thumbnail keywords are written in English: ""File:"", ""thumb"", ""right"" (but see Bug 51851).
+
+This should not, theoretically, be a problem, because the VisualEditor is supposed to make these keywords unimportant and hidden from the end-user. However, while the source editor is still being widely used, this is a problem, especially for right to left languages: it is very hard to edit these English keywords when they are mixed with right-to-left text.
+
+These keywords should be inserted in the language of the wiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374569160,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_description,resolved
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 280792 merged by jenkins-bot:
+T53852: Serialize localized image options
+
+[[https://gerrit.wikimedia.org/r/280792]]",1459883811,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 244254 abandoned by Eranroz:
+Use local keyword for image
+
+Reason:
+See a better patch: https://gerrit.wikimedia.org/r/#/c/244254/
+
+[[https://gerrit.wikimedia.org/r/244254]]",1459809027,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 280792 had a related patch set uploaded (by Arlolra):
+T53852: Serialize localized image options for rtl languages
+
+[[https://gerrit.wikimedia.org/r/280792]]
+",1459469170,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,">>! In T53852#1735891, @Amire80 wrote:
+> General Q: Can the same patch also resolve T104057, a similar issue in ContentTranslation?
+> 
+>>>! In T53852#1735780, @cscott wrote:
+>> * Alternatively, you could do a grep over the most recent dump for that wiki to count frequency of use for each alias, and verify that the term which would be used by this patch matches the most frequent alias.
+> 
+> Sounds more practical and closer to reality.
+> 
+> Parsoid developers, don't you have some kind of a tool that queries lots of dumps quickly? I remember hearing something like this, but maybe I am just imagining.
+
+This used to be part of the parsoid repository but is now its own repo @ https://github.com/wikimedia/dumpgrepper",1445283298,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"General Q: Can the same patch also resolve T104057, a similar issue in ContentTranslation?
+
+>>! In T53852#1735780, @cscott wrote:
+> * Alternatively, you could do a grep over the most recent dump for that wiki to count frequency of use for each alias, and verify that the term which would be used by this patch matches the most frequent alias.
+
+Sounds more practical and closer to reality.
+
+Parsoid developers, don't you have some kind of a tool that queries lots of dumps quickly? I remember hearing something like this, but maybe I am just imagining.
+
+>>! In T53852#1735858, @ssastry wrote:
+> A good compromise to get this moving would be to do this analysis for the top N wikis (N = 10?)
+
+I'd guess that it's more like 50 or so.",1445280165,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,A good compromise to get this moving would be to do this analysis for the top N wikis (N = 10?) -- the expectation is that only a few wikis will need either their messages tweaked or special case exceptions added for them in the code and we can get this going from there.,1445279437,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"@eranroz's code in wikieditor: https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FWikiEditor/8fa9506e20ce5216240531686fa0bd70fdb2a6d8/WikiEditor.hooks.php#L374
+
+I'm proposing a simple process:
+* Make a table with the various options whose serialization will be changed with this patch, both before and after.
+* Send this in an email to the language team for approval.
+** Alternatively, you could do a grep over the most recent dump for that wiki to count frequency of use for each alias, and verify that the term which would be used by this patch matches the most frequent alias.
+* For any languages where this patch does *not* match that wiki's preferred term, file an issue as a blocker for this bug, and resolve it.
+** Either add special cases to this patch, or else export some general siteinfo property (a boolean to ""prefer first alias"" or ""prefer last alias""), or else work with the community to swap the aliases in mediawiki (MessageEn in core, and then perhaps the actual wikipedias need to be checked for customizations that might override this)
+* After this is done, everyone will have objectively agreed that the terms used by this patch are preferable, and this patch can be merged.",1445278545,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"It's not just english, it's also dewiki IIRC.
+
+To unblock this issue, you need to survey all the wikis (not just enwiki and hewiki) and describe how this change will affect them, then get confirmation from the language team that the change is actually ""better"" for all these languages.
+
+We were burned before by changing this prematurely; before we're going to make another change we need to be sure we are actually doing the right thing.",1445277440,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"A note specific for English: This fix will introduce ""thumbnail"" instead of ""thumb""  in parsoid. This side effect is the correct behavior as aliases are defined by the preferred order, and this is the syntax added by the current WikiEditor image dialog. If you prefer ""thumb"" and not ""thumbnail"" (personally I do too) which is shorter - you should swap the aliases in English (MessageEn in core, and enwiki.json in baseconfig) - but this should be a different task.",1444251608,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 244254 had a related patch set uploaded (by Eranroz):
+Use local keyword for image
+
+[[https://gerrit.wikimedia.org/r/244254]]
+",1444247108,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"(In reply to C. Scott Ananian from comment #8)
+> Yes, that is correct.  The patch was merged and then the language-specific
+> parts were reverted because the way it selected the aliases was fragile in
+> LTR languages.  This is still on my to-do list for a proper fix; IIRC the
+> blocking issue is we need to export a simple RTL/LTR flag in siteinfo.
+
+Would it be easier if we just had Parsoid default to the (first?) localised string over the generic wikitext? This presumably doesn't need any MW API changes…",1401220172,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Yes, that is correct.  The patch was merged and then the language-specific parts were reverted because the way it selected the aliases was fragile in LTR languages.  This is still on my to-do list for a proper fix; IIRC the blocking issue is we need to export a simple RTL/LTR flag in siteinfo.",1401220107,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"The above was merged in January, but this bug isn't fixed AFAICT. Also, we should probably use the local wikitext over the English version in all languages, not just RTL ones.",1401215876,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"Change 103082 had a related patch set uploaded by Cscott:
+Edited image attributes should override data-parsoid value.
+
+https://gerrit.wikimedia.org/r/103082",1387811331,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,I'm pretty sure our magic words support already has the appropriate localized keyword alias. We just aren't using it (yet).,1378921869,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"I went over the RTL languages and samples practical Wikipedia articles, and it seems that the first alias is always is always the most frequently used.
+
+Is there anything I can do to help move this forward? It's one of the most requested features.",1377641269,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"For the site info, look for ""rtl"" in http://he.wikipedia.org/w/api.php?action=query&meta=siteinfo&siprop=general&format=json",1376690239,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"We don't actually need to hard-code the list of rtl wikis, as that information is available in the site info returned by the API. It would still be good to check for each current rtl wiki if the first option alias is always a good one.",1376690182,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+Image options should be serialized in the wiki's language in rtl locales - localization i18n,"In most ltr wikis the English version is actually the most commonly used today, which is why we went with serializing new content with the English defaults.
+
+This is not ideal for rtl languages though, as this leads to a mix of ltr and rtl text.
+
+If you can provide us with a list of rtl language codes and check for each if a common offset in the option aliases is a good default, then we can add a list of rtl languages to the serializer and use the localized defaults for those.",1376689406,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ah63325mhbgtfpeazbnl,task_subcomment,NA
+VisualEditor: Disable 'Use existing reference' on pages without a reference,"Steps to reproduce
+1. start an empty sandbox (https://en.wikipedia.org/wiki/User:John_Vandenberg/mtgg?veaction=edit)
+2. insert reference
+3. use an existing reference
+
+Expected results:
+'Use an existing reference' should be disabled, as there are none to select.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50458",1374557100,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jx64nu32n5cymzvwwjp5,task_description,resolved
+VisualEditor: Disable 'Use existing reference' on pages without a reference,"Change 81964 merged by jenkins-bot:
+Re-build reference search index so they can be used mid-edit
+
+https://gerrit.wikimedia.org/r/81964",1377889945,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx64nu32n5cymzvwwjp5,task_subcomment,NA
+VisualEditor: Disable 'Use existing reference' on pages without a reference,Now fixed in master and will be deployed next week.,1377889832,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jx64nu32n5cymzvwwjp5,task_subcomment,NA
+VisualEditor: Disable 'Use existing reference' on pages without a reference,"Change 81964 had a related patch set uploaded by Trevor Parscal:
+[WIP] Bug 51689, bug 52000 & bug 51848 - Reusing new references
+
+https://gerrit.wikimedia.org/r/81964",1377886576,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jx64nu32n5cymzvwwjp5,task_subcomment,NA
+VisualEditor: Recursive word addition with Google Input Tools in reference tool on Firefox,"Steps to reproduce:
+1. Download and install Google input tools for windows www.google.co.in/inputtools
+2. Open any page in firefox
+3. Open VE
+4. Edit a reference
+5. Type anything in the reference. The word is input by the tools when the word is complete and one presses space/enter
+
+Expected Behaviour:
+The word is input and if the spacebar has been pressed, a space is input too.
+
+What happens instead:
+The word is entered recursively over and over. The space isn't input at all.
+
+System environment:
+Win 7 X64 SP1
+Firefox 15.0.1
+Google input tools for languages hindi and punjabi(gurmukhi script)
+
+The problem didn't seem to arise when using input tools for urdu, though its possible that's just coz the wiki is ltr and urdu is rtl.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374549360,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-6nas4q7uc475euchng3b,task_description,resolved
+VisualEditor: Recursive word addition with Google Input Tools in reference tool on Firefox,Confirming that this is fixed in Firefox 23.0.1 on Win7 X64 SP1 for both punjabi (gurmukhi script) and hindi.,1379503051,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-6nas4q7uc475euchng3b,task_subcomment,NA
+VisualEditor: Recursive word addition with Google Input Tools in reference tool on Firefox,"Marking this as ""FIXED"" on the expectation that it's fixed - please re-open if you find that it is still occurring.",1378958789,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6nas4q7uc475euchng3b,task_subcomment,NA
+VisualEditor: Recursive word addition with Google Input Tools in reference tool on Firefox,"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!",1378943165,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-6nas4q7uc475euchng3b,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Steps to reproduce:
+1. Open any page
+2. Open VE
+3. Type (or copy-paste) ग्र
+5. Press left arrow key
+
+What should happen:
+Cursor should move to the left of the glyph
+
+What happens:
+Cursor stays there
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 28.0.1500.72 m
+
+The problem arises regardless of what follows ग्र . I've tried with space, tab, the letter a, devanagari characters that do not combine with the glyph, like क, and devanagari characters that do combine with the glyph, such as ि to produce ग्रि and ी to produce ग्री
+
+The problem doesn't seem to affect firefox 15.0.1.
+
+In chrome, the problem doesn't arise in the link editing window, or when editing parameter of a template. It does, however, arise when editing a reference.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374547560,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xckf32rcb2yx56eieafj,task_description,resolved
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press",Have tested quite a lot and this seems fine.,1430334001,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Seems to be fixed now, though probably needs to be tested extensively before closing.",1424612816,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","18:32 < Sid-G> Hi. Can someone confirm if the fix for https://bugzilla.wikimedia.org/show_bug.cgi?id=51846 has been deployed to the wmf cluster?
+
+18:40 < mutante> Sid-G: hi
+18:40 < mutante> i dont know much about ve but yes, it looks deployed
+
+8:40 < mutante> checked one of those changed files on tin
+18:41 < mutante> /php-1.23wmf6/extensions/VisualEditor/modules/ve/ce/ve.ce.Document.js
+18:43 < mutante> Sid-G: and also confirmed on random app server, so not like somebody forgot to deploy
+18:43 < mutante> if it doesnt work it should actually need an additional fix
+
+18:45 < Sid-G> hmm, then i should reopen the bug
+18:45 < mutante> yes
+18:45 < mutante> please do
+
+18:58 < Sid-G> mutante: reopened. Is there an irc chan for VE?
+
+19:15 < legoktm> #mediawiki-visualeditor",1386992085,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press",We'll have to investigate. Sorry this isn't fixed yet!,1386989820,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Reopening
+
+System Environment:
+Windows 7 X64 SP1
+Google Chrome 31.0.1650.63 m
+
+Urls:
+Same as in comment 6
+
+Glyphs:
+Same as in comment 0 , comment 1 and comment 6
+
+What happens:
+Crossing the glyphs now requires three keypresses going either left to right or right to left.",1386989489,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Has this been deployed? If it has, it hasn't fixed the problem. Please reopen if this has been deployed. Tried at both urls per comment 6.",1386469991,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Change 80689 merged by jenkins-bot:
+Revert model to use simple UTF-16 code units
+
+https://gerrit.wikimedia.org/r/80689",1385506399,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","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",1384946963,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press",There's code in progress to fix this in gerrit 80689 which is currently a work-in-progress.,1381269313,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","Update:
+System Environment:
+Windows 7 X64 SP1
+Google Chrome 29.0.1547.76 m
+
+Tested at https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+
+न्स seems to now require three keystrokes. All the others listed in Comment 6 above along with ग्र भ्र श्र ष्र still require two keystrokes.",1380971530,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+It seems similar behaviour (both with and without the patch) occurs when a letter is followed by ् + स regardless of whether the glyph appears joined or not.
+
+To be clear, the same problem occurs with this cluster, and the patch works the same.
+
+Results with the patch for all consonants, tested at [1]:
+Glyph(s) -- Number of keystrokes needed (going either left to right or right to left)
+क्स ख्स ग्स घ्स ङ्स च्स छ्स ज्स झ्स ञ्स ट्स ठ्स ड्स ढ्स ण्स त्स थ्स द्स ध्स न्स प्स फ्स ब्स भ्स म्स य्स र्स ल्स व्स श्स ष्स स्स ह्स -- 2
+
+I have not tested the selection per key-press for these, but I expect the results would be same as those in Comment 5
+
+Results without the patch, tested at [2]:
+All of the clusters can be passed with one right arrow key press going from left to right. None can be passed going right to left on any number of left arrow key-presses.
+
+[1]: https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+[2]: https://hi.wikipedia.org/wiki/%E0%A4%B8%E0%A4%A6%E0%A4%B8%E0%A5%8D%E0%A4%AF:Siddhartha_Ghai/sandbox?veaction=edit",1379499369,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","(In reply to comment #4)
+> 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.
+
+System environment:
+Win 7 X64 SP1
+Google Chrome 29.0.1547.66 m
+
+Tested this out at [1]. The cursor moves past the glyph on two left arrow keypresses.
+
+I tried selecting the text with the left arrow keypresses. Then I copy-pasted the selected text into an external text editor. It seems the first keypress takes the cursor past र and the second past ग्
+However, visually the caret seems to be unmoved after the first keypress (i.e it does not move past the glyph or into the glyph) and crosses the glyph after the second keypress.
+
+The patch also introduces an unintended side-effect. Crossing the glyph from the left to the right on right arrow keypress also takes two keypresses now. Without the patch, this used to take only one right arrow keypress. This correct behaviour can be currently seen at hindi wikipedia, specifically tested at [2]
+
+So the problem is partially fixed, but with side-effects.
+
+[1]: https://www.mediawiki.org/wiki/User:Siddhartha_Ghai?veaction=edit
+[2]: https://hi.wikipedia.org/wiki/%E0%A4%B8%E0%A4%A6%E0%A4%B8%E0%A5%8D%E0%A4%AF:Siddhartha_Ghai/sandbox?veaction=edit",1379497039,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","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.",1378943340,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","(In reply to comment #2)
+> Hi,
+> 
+> You are referring problem to windows system based inscript input system , ULS
+> or any hindi devnagari input or any devnagari input including  Marathi and
+> Nepali ?
+> 
+> Regards
+
+The problem is not with the input method. It is with moving around the cursor when using visual editor. So, for example, if any letter followed by ् + र already exists on the wiki and you try to edit the page with visual editor, you can move the cursor across it from left to right, but not from right to left.
+
+As far as I understand the problem, it is specific to devanagari (not hindi), although I haven't specifically gone to mr or ne wikis to verify.",1377345735,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press","(In reply to comment #1)
+> Update: Same problem seems to arise for any other letters followed by ् + र
+> to
+> form a combined glyph. Examples:भ्र श्र ष्र etc. It does not seem to arise
+> when
+> the glyph is not combined.
+
+Hi,
+
+You are referring problem to windows system based inscript input system , ULS or any hindi devnagari input or any devnagari input including  Marathi and Nepali ?
+
+Regards",1377236465,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+"Cursor not moving past ""ग्र"" and other multiple code-unit grapheme clusters on left arrow key press",Update: Same problem seems to arise for any other letters followed by ् + र to form a combined glyph. Examples:भ्र श्र ष्र etc. It does not seem to arise when the glyph is not combined.,1374618177,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xckf32rcb2yx56eieafj,task_subcomment,NA
+VisualEditor: Reference dialog re-use search form doesn't recognise uppercase group names,"The re-use tab in the reference dialog allows searching for group names. This was always possible. However, it doesn't work when the group name is uppercase or contains an uppercase character. For example, it works when the group name is ""note"" but not when the group name is ""A"". It doesn't matter if I search for ""a"" or ""A"", it's not found.
+
+Turns out the relevant code is incomplete ever since it was written in 2013, see https://gerrit.wikimedia.org/r/70364. The relevant ticket was {T51733}.",1374525480,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-2ms2vngz2briyomwp2bg,task_description,resolved
+VisualEditor: Reference dialog re-use search form doesn't recognise uppercase group names,"Change #1055393 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Fix reference search not working with uppercase groups/names%%%
+https://gerrit.wikimedia.org/r/1055393",1721641929,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2ms2vngz2briyomwp2bg,task_subcomment,NA
+VisualEditor: Reference dialog re-use search form doesn't recognise uppercase group names,"Change #1055393 had a related patch set uploaded (by Thiemo Kreuz (WMDE); author: Thiemo Kreuz (WMDE)):
+%%%[mediawiki/extensions/Cite@master] Fix reference search not working with uppercase groups/names%%%
+https://gerrit.wikimedia.org/r/1055393",1721382014,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2ms2vngz2briyomwp2bg,task_subcomment,NA
+VisualEditor: Reference dialog re-use search form doesn't recognise uppercase group names,"I'm not sure what's missing here. The group name always was searchable ever since the code was added in June 2013. I just tested it and it works with and without #Citoid. Maybe the code was not deployed when this ticket was written?
+
+https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/70364/27/modules/ve/ui/widgets/ve.ui.MWReferenceSearchWidget.js#123",1708623279,PHID-USER-u6ycqhfpa3k4yvlpxjt2,False,PHID-TASK-2ms2vngz2briyomwp2bg,task_subcomment,NA
+VisualEditor: Transclusion editor template search should additionally find in-string matches,"Split from bug 51436, Original comment was:
+""Also typing a word only shows template names starting with that word, not
+containing it, which is a weird search behaviour.
+
+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).""
+
+A further relevant comment was:
+""This is asking for VisualEditor ... 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.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51670",1374511680,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bcumpuzgy3avff6z7fio,task_description,open
+VisualEditor: Transclusion editor template search should additionally find in-string matches,"**crypticc62** wrote:
+
+Even if in-string searching is used instead of left-string completion, there is still the problem of templates whose names are completely unsearchable, such as {{rp}} and pretty much everything in [[Category:Typing-aid templates]].
+
+What would be very useful is a TemplateData field in which editors can list relevant keywords that users might search for. Perhaps it could be called ""keywords"" or ""tags"". Without something like this, it's not clear to me how new users would ever find the templates they're looking for.",1377222496,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bcumpuzgy3avff6z7fio,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","The VisualEditor's user manual is translatable in Meta, which is a Good Thing. Currently the help link uses Special:MyLanguage. This uses the user's UI language as defined on Meta, which is likely not to be the same as the user's UI language on a non-English site.
+
+As much as possible, the link should point directly to the user manual in the language that the user is using currently for the UI.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374488220,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-likhdovodmty4qer7rsq,task_description,open
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","That is intentional. Given the logged out users and many logged in users by default have English, it prefers the provided language code instead of interface language.",1473747184,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language",">>! In T53797#564658, @Nikerabbit wrote:
+> You could point to Special:MyLanguage/Page/<current ui language>. If the user is logged on mediawiki.org (which is quite likely), their interface language there will still overrule the provided language code :(
+
+That would probably be okay, but if I go to https://ta.wikipedia.org/wiki/Mw:Special:MyLanguage/Help:VisualEditor/User_guide/ta I get Tamil, even though I am logged in and my preference is en.",1473709455,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","(In reply to comment #2)
+> You could point to Special:MyLanguage/Page/<current ui language>. If the user
+> is logged on mediawiki.org (which is quite likely), their interface language
+> there will still overrule the provided language code :(
+
+To do this we'd have to have code that explicitly mangles an i18n string. This feels… deeply wrong. :-(",1375114805,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","You could point to Special:MyLanguage/Page/<current ui language>. If the user is logged on mediawiki.org (which is quite likely), their interface language there will still overrule the provided language code :(",1375086773,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language","(In reply to comment #0)
+> The VisualEditor's user manual is translatable in Meta, which is a Good
+> Thing.
+> Currently the help link uses Special:MyLanguage. This uses the user's UI
+> language as defined on Meta, which is likely not to be the same as the user's
+> UI language on a non-English site.
+> 
+> As much as possible, the link should point directly to the user manual in the
+> language that the user is using currently for the UI.
+
+What is the recommended solution for this? Hard-code the link to be https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/<foo>? Wouldn't it be easier for the user's language to properly transfer to MW.org using ULS or whatever?",1374509348,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-likhdovodmty4qer7rsq,task_subcomment,NA
+VisualEditor: Non-English Wikipedia issues (tracking),"Tracking for VE issues of problems that are specific to a Wikipedia other than English Wikipedia, excluding RTL issues as they are tracked by bug 33126.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T51998}
+{T51999}",1374480780,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-oytsgsispcryv5y4kv3t,task_description,resolved
+VisualEditor: Non-English Wikipedia issues (tracking),Which project/tag was this replaced with?,1432541898,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-oytsgsispcryv5y4kv3t,task_subcomment,NA
+VisualEditor: Non-English Wikipedia issues (tracking),Replaced with projects.,1422425002,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oytsgsispcryv5y4kv3t,task_subcomment,NA
+VisualEditor: Non-English Wikipedia issues (tracking),"Since you dont want to track them, I have put myself as the assignee.
+
+I added issues that appear to be a much higher priority for non-English Wikipedia, or only reproducible on non-English Wikipedia.  If they affect all Wikipedia, remove them.
+
+We have had very few issues raised from non-English Wikis, and many of them had not even been confirmed until I worked through the Unconfirmed list yesterday.",1374528616,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-oytsgsispcryv5y4kv3t,task_subcomment,NA
+VisualEditor: Non-English Wikipedia issues (tracking),"It is not-unreasonable to use a tracking bug for language-specific issues, but almost all of the bugs cited here are not language-specific. Will remove those that are general VisualEditor issues.",1374508727,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oytsgsispcryv5y4kv3t,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","When you type ""[["" in visual editor, there is a ""wiki markup text"" popu (nice touch - Thanks, devs).
+
+However, this warning popup shows at top of page, so it's not visible when the page is scrolled even a few lines.
+
+VE toolbar floats at the top of the browser's page even when we edit at the middle of the article. the warning popu should do the same. 
+
+REPRODUCTION INSTRUCTIONS
+0) open [[en:The Rolling Stones]]
+1) select one of the sections from the TOC
+2) Click ""Edit""
+3) wait, wait, wait, wait...
+4) close the edit notice
+5) type ""[[""
+
+EXPECTED
+1) during the wait (3 above) there is a nice image asking you to wait: this image is expected to be visible
+
+2) when the ""edit notice"" shows up, you expect some clear way to close it.
+
+3) when typing ""[["", you expect the ""wikitext warning"" popup to show up
+
+WHAT ACTUALLY HAPPEN
+
+1) the ""please wait"" image appears, but unfortunately it's outside the screen, so you do not know why the page appears milky, and have no indication that this would eventually end.
+
+2) depending on your luck, clicking on various parts of the page *will* close the edit notice (if you're lucky), or will take you to [[en:Template:Editnotices/Page/The Rolling Stones]] (i.e., another page from the one you are trying to edit) if you're unlucky.
+
+3) the warning popup appears, but it's at the top of the page, so unless you are editing the very first part of the page, you do not see it.
+
+
+COMMENTS:
+1) VE is clever enough to have its toolbar visible even when scrolling down, using ""position:fixed"". same should be done for the ""please wait"" image and for the warning popup(s).
+
+2) the ""1 notice"" and the warning triangle on the toolbar should indicate that they are the gate to hiding the notice: e.g., change the ""1 Notice"" text to ""Hide notice"" when the notice is visible.
+
+3) it seems that the wikitext notice is not yet translated to all languages.
+
+
+peace.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374442980,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j46p5in7q2s26odkx5az,task_description,resolved
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","Sounds like the same thing.
+
+The other bug is older and the discussion on this one is mostly related to bug 50870, so I'll mark this one as a dupe of that one.
+
+*** This bug has been marked as a duplicate of bug 50206 ***",1379436668,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section",(is https://bugzilla.wikimedia.org/show_bug.cgi?id=50206 a dupe?),1379425952,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","(In reply to comment #3)
+> i know that opening a single ticket for 3 different issues is not a good
+> idea, and i apologize for doing something i know is wrong.
+
+As long as you don't do it again, no need to apologise. :-)",1374509581,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","Original bug talked about 3 (somewhat unrelated) things.
+
+The first one turned out to be duplicate of bug 50870, and not specific to VE (i think this is why i did not find it).
+
+However, the 2nd one *is* specific to VE, and i do not think bug 50870 covers it.
+
+so i changed the synopsis of this bug to indicate the 2nd problem, and i'm reopening it.
+
+i know that opening a single ticket for 3 different issues is not a good idea, and i apologize for doing something i know is wrong.
+
+(it's a bit confusing - ""1st"" and ""2nd"", appear as ""2"" and ""1"" in original ticket - i call ""2"" in comment #0 ""first"" because this was the synopsis of original ticket).
+
+peace.",1374506028,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","
+
+*** This bug has been marked as a duplicate of bug 50870 ***",1374449520,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+"VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section","(In reply to comment #0)
+> 2) depending on your luck, clicking on various parts of the page *will* close
+> the edit notice (if you're lucky), or will take you to
+> [[en:Template:Editnotices/Page/The Rolling Stones]] (i.e., another page from
+> the one you are trying to edit) if you're unlucky.
+> 
+> 
+> peace.
+
+so here is what i mean: if you click on the page outside the ""edit notice"", nothing happens.
+if you click on the edit notice itself, then it depends: 
+some parts of the edit notice are links (including the images), and will take you elsewhere. there is no indication, because the edit notice as a whole has ""cursor: pointer;"" css attribute, so the mouse pointer looks the same everywhere on the edit notice. clicking somewhere which is not a link will close the notice, and clicking somewhere which *is* a link will take you elsewhere. again, there is little indication - e.g., moving the mouse into and out of images does not give any visible sign.
+clicking on the little ""page notice"" link *inside* the notice takes you elsewhere, while clicking on the ""1 notice"" on the toolbar closes the notice.
+very confusing.
+
+(btw: the notice itself seems to be anchored to the toolbar rather than to the page, which is exactly what's needed for the ""please wait"" image and for the wikitext popup).
+
+peace.",1374443710,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-j46p5in7q2s26odkx5az,task_subcomment,NA
+VisualEditor: Structural content inside a <small> should be alienated but this fails because they are inline rather than inline-block,"In an (un)ordered list nested in a table I am unable to edit wikilinks. While hovering above a wikilink the wikilink is an active weblink, instead of showing the icon of the link inspector, see URL.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://test.wikipedia.org/wiki/User:Raymond/nested",1374430980,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-kvei76aer6u2clu7k444,task_description,duplicate
+VisualEditor: Structural content inside a <small> should be alienated but this fails because they are inline rather than inline-block,*** Bug 52285 has been marked as a duplicate of this bug. ***,1385396898,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kvei76aer6u2clu7k444,task_subcomment,NA
+VisualEditor: Structural content inside a <small> should be alienated but this fails because they are inline rather than inline-block,"Block nodes (like lists) in inline positions (like in <small>) get alienated as inline aliens. These inline aliens then don't get shields and phantoms with the right dimensions. One way to fix that could be to make alienInline display:inline-block instead of display:inline, which seems to fix the dimensions of the shield, but we'd have to carefully evaluate that as it would potentially impact a lot of things.",1385394281,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-kvei76aer6u2clu7k444,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"From the mailing list
+
+> from:	 planetenxin <planetenxin@web.de> via gmail.com 
+> reply-to:	 Wikimedia developers <wikitech-l@lists.wikimedia.org>
+> to:	 wikitech-l <wikitech-l@lists.wikimedia.org>
+> date:	 Sun, Jul 21, 2013 at 10:15 PM
+> subject:	 [Wikitech-l] Git Proxy Error
+
+> Hi folks,
+> I'm constantly getting the following error on https://git.wikimedia.org/:
+> 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
+>/Alexander
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51656
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49371",1374410040,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_description,declined
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"The gitblit software powering git.wikimedia.org is in the process of being replaced by Phabricator Diffusion. See:
+
+{T111465}
+Project: #gitblit-deprecate",1441874873,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Maybe http://git.zx2c4.com/cgit/about/ might be an alternative to gitblit as its main design criterion is speed and caching.,1396988983,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"Just a heads-up: Upstream in https://code.google.com/p/gitblit/issues/detail?id=274 asks ""for discussion with Wikimedia folks on how to improve caching since the current strategy is not ideal"".",1378204045,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"max semenik reported that gitblit should mark critical links with rel=""nofollow""",1376771529,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,mark configured the misc varnish cluster for gitblit: https://gerrit.wikimedia.org/r/#/c/78262/,1376771436,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"browser cache problem reported upstream and fixed, see here:
+https://code.google.com/p/gitblit/issues/detail?id=274",1376771021,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"https://gerrit.wikimedia.org/r/#/c/78919/
+
+As soon as the bot picks up th new copy of the robots.txt file that should take care of it for now.",1376373844,PHID-USER-jtxavgb3caz53o45csni,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,faidon lambiotis restarted it a couple of hours ago withoutout tracing it seems? and now its dead again.,1376345034,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Stupid question: is crawl-delay in robots.txt worth trying?,1376334890,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"before restarting the java process, could you trace it with:
+* jps -l to find out the process id
+* strace to see if it excessivly calls into the operating system
+* jstack
+* kill -QUIT <p> to print the stacktrace
+* jmap -heap <p> to find memory usage
+* jmap -histo:live <p> | head to find excessivly used classes
+* if you have ui, you might try jconsole or http://visualvm.java.net as well
+
+you might want to set the java -XX:+HeapDumpOnOutOfMemoryError parameter when starting, so it writes a heap dump early enough. it can be analyzed with jhat.",1376253536,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,down again at the moment... i think gitblit might behave nicer in case bots overloading it.,1376218114,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Back up again at the moment...,1376185946,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #34)
+> created a bug at gitblit:
+> https://code.google.com/p/gitblit/issues/detail?id=294.
+
+No need for that, I've already been in contact with upstream. It's mainly being overloaded from Googlebot.",1376176292,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,created a bug at gitblit: https://code.google.com/p/gitblit/issues/detail?id=294.,1376168077,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"As reported by OsamaK last night in #wikimedia-tech and again today by rupert THURNER on wikitech-l (and I personally confirmed last evening), git.wikimedia.org is down yet again.
+
+---
+$ time curl https://git.wikimedia.org/
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>
+
+real	12m1.522s
+user	0m0.010s
+sys	0m0.026s
+---",1376146093,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"For the records: https://gerrit.wikimedia.org/r/#/c/78243/
+(By the way: Ariel & Daniel, thanks for keeping this ticket updated.)",1376021981,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,chad fixed up service of robots.txt and we've unblocked the google bot.  Waiting for verification that google has picked up the file and we'll see how performance looks after that.,1375978732,PHID-USER-jtxavgb3caz53o45csni,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,(Resetting severity & priority as long as things are working again.),1375952067,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"merged this:
+
+https://gerrit.wikimedia.org/r/#/c/77909/1/templates/apache/sites/git.wikimedia.org.erb
+
+and:
+
+08:42 mutante: on overloaded antimony: stopped gitblit, ran puppet, blocked Googlebot, restarted apache and gitblit
+08:22 mutante: git.wikimedia.org back
+08:21 mutante: attempted to restart gitblit on antimony 
+
+01:44 < mutante> apergos: oh.. Googlebot-Image/1.0 != Googlebot ?
+01:44 < apergos> no
+01:44 < apergos> googlebot is the one that rate limited
+01:44 < apergos> that should be enough, it's the /zip/ paths primarily that were the problem
+01:44 < mutante> Googlebot-Image is the one still being very active
+01:44 < mutante> ok
+01:44 < apergos> it's minor compared to the rest
+01:44 < mutante> alright
+01:44 < apergos> I did a count from the logs yeasterday
+01:45 < mutante> now YandexBot kicking in :)
+01:45 < apergos> please note it on the bz report so we don't forget
+01:46 < mutante> java CPU usage isn't > 500% anymore though :)",1375951706,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"Turns out that we were serving an empty robots.txt even though there is content. Logs show lots of:
+[Wed Aug 07 21:44:15 2013] [error] [client XXX.XXX.XXX.XXX] proxy: Error reading from remote server returned by /robots.txt
+
+Chad says this is likely due to some fancy proxy rewriting sending everything to gitblit.  In the meantime the google folks have cut back both parallel open connections and req/sec until we have this sorted and can give them the heads up.",1375913787,PHID-USER-jtxavgb3caz53o45csni,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"I'm talking to the folks at google about it, will update as soon as I have more info.",1375906393,PHID-USER-jtxavgb3caz53o45csni,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Google is the one misbehaving.,1375825195,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #24)
+> > Do the misbehaving bots respect robots.txt?
+> 
+> Nope.
+
+Just to be clear, I hope that you block whatever wished and needed except Google (so that we have at least one search engine).",1375823311,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #23)
+> (In reply to comment #22)
+> > So bots aren't going to be allowed to index gitblit anymore since they can't
+> > seem to behave.
+> 
+> Do the misbehaving bots respect robots.txt?
+
+Nope.",1375822950,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #22)
+> So bots aren't going to be allowed to index gitblit anymore since they can't
+> seem to behave.
+
+Do the misbehaving bots respect robots.txt?",1375822567,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,So bots aren't going to be allowed to index gitblit anymore since they can't seem to behave.,1375822451,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #20)
+> Down again?
+
+Indeed. :-(
+
+---
+$ time curl https://git.wikimedia.org/
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>
+
+real	12m2.101s
+user	0m0.010s
+sys	0m0.028s
+---",1375816643,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Down again?,1375791780,PHID-USER-wz5bw3q6zykhqbbeohzq,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Restarted service.,1375681588,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #17)
+> It's again inaccessible (my browser doesn't receive any reply) with antimony
+> at 100 % load.
+
+Confirmed that git.wikimedia.org is inaccessible currently; no idea about antimony's load.
+
+Re-opening this bug as it's no longer resolved. Thank you, Nemo, for commenting here.
+
+---
+$ time curl https://git.wikimedia.org/
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>
+
+real	12m43.815s
+user	0m0.010s
+sys	0m0.024s
+---",1375669136,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,It's again inaccessible (my browser doesn't receive any reply) with antimony at 100 % load.,1375636764,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,Closing this as resolved/fixed for now.,1374687493,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"So, it's a little sluggish still but it's at least staying up. Did some more puppetizing and blocked some misbehaving spiders that were causing it to fall over all the time.
+
+Still want to up the heap and see if we can get some better performance out of it.",1374618927,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,I've got some new caching stuff that landed in master just for us :) Looking at turning that on today as well.,1374601182,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #5)
+> For the record, it doesn't seem to be completely down, just really slow to
+> respond.
+
+To me it just serves ""Internal error"" messages. When CPU usage goes down a bit, you may happen to get some content, maybe curl is just being very patient and retrying a lot till that happens.",1374600397,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #10)
+> git.wikimedia.org continues to be broken. This is very frustrating.
+
+You're telling me :(",1374597058,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,We cant take stack trace right now since gitblit is running with Java 6 and we are missing the jstack utility.  That is bug 51859.,1374573819,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,git.wikimedia.org continues to be broken. This is very frustrating.,1374566967,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"(In reply to comment #8)
+>  14:42 apergos: (btw docs would be nice, is that really the right way to kick
+> it?)
+> 14:42 apergos: shot and restarted gitblit: on antinomy, cd /var/lib/gitblit,
+> java -jar gitblit.jar & (see bug 51769) 
+> 
+> Can we help Ariel out? :)
+
+Peachey88 helpfully created <https://wikitech.wikimedia.org/wiki/Git.wikimedia.org> and <https://wikitech.wikimedia.org/wiki/Gitblit>. Thank you, Peachey88!",1374518718,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot," 14:42 apergos: (btw docs would be nice, is that really the right way to kick it?)
+14:42 apergos: shot and restarted gitblit: on antinomy, cd /var/lib/gitblit, java -jar gitblit.jar & (see bug 51769) 
+
+Can we help Ariel out? :)",1374511097,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,This seems to be an issue again.,1374502907,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"Restarted the service again. Nothing was suspicious in the logs, but CPU was pegged at 100% :\",1374473332,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"For the record, it doesn't seem to be completely down, just really slow to respond. When I tried again, I got:
+
+$ time curl https://git.wikimedia.org
+<!DOCTYPE html PUBLIC ""-//W3C//DTD XHTML 1.0 Strict//EN"" ""http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"">
+<html xmlns=""http://www.w3.org/1999/xhtml"" xml:lang=""en"" lang=""en"" ng-app=""""> 
+
+	<!-- Head -->
+	<head>
+		<meta name=""viewport"" content=""width=device-width, initial-scale=1.0"">
+		<meta http-equiv=""X-UA-Compatible"" content=""IE=Edge"" />
+   		<title>Wikimedia</title>
+		<link rel=""icon"" href=""gitblt-favicon.png"" type=""image/png""/>
+		
+		<link rel=""stylesheet"" href=""bootstrap/css/bootstrap.css""/>
+		<link rel=""stylesheet"" href=""bootstrap/css/iconic.css""/>
+		<link rel=""stylesheet"" type=""text/css"" href=""gitblit.css""/>
+	<link rel=""stylesheet"" type=""text/css"" href=""bootstrap/css/bootstrap-responsive.css"" />
+<style type=""text/css"">
+.navbar-inner {
+background-color: #FBFBFB;
+border-bottom: 1px solid #39688E !important;
+}
+.navbar ul li:focus, .navbar .active {
+border-bottom: 4px solid #9C000F;
+}
+.navbar ul.nav li a {
+color: #002060;
+}
+.navbar ul.nav .active a {
+color: #002060;
+}
+.navbar ul.nav li a:hover {
+color: #002060 !important;
+}
+</style>
+<script type=""text/javascript"" src=""https://www.google.com/jsapi""></script>
+<script type=""text/javascript"" ><!--/*--><![CDATA[/*><!--*/
+google.load(""visualization"", ""1"", {packages:[""corechart""]});
+google.setOnLoadCallback(drawChart);
+function drawChart() {
+var data_ffa5c540 = new google.visualization.DataTable();
+data_ffa5c540.addColumn('string', 'repository');
+data_ffa5c540.addColumn('number', 'commits');
+data_ffa5c540.addRows(85);
+data_ffa5c540.setValue(0, 0, 'mediawiki/core');
+data_ffa5c540.setValue(0, 1, 2.0);
+data_ffa5c540.setValue(1, 0, 'mediawiki/extensions');
+data_ffa5c540.setValue(1, 1, 2.0);
+data_ffa5c540.setValue(2, 0, 'mediawiki/extensions/TranslationNotifications');
+data_ffa5c540.setValue(2, 1, 2.0);
+data_ffa5c540.setValue(3, 0, 'mediawiki/extensions/PollNY');
+data_ffa5c540.setValue(3, 1, 1.0);
+data_ffa5c540.setValue(4, 0, 'mediawiki/extensions/Nuke');
+data_ffa5c540.setValue(4, 1, 1.0);
+data_ffa5c540.setValue(5, 0, 'mediawiki/extensions/LastModified');
+data_ffa5c540.setValue(5, 1, 1.0);
+data_ffa5c540.setValue(6, 0, 'mediawiki/extensions/MoodBar');
+data_ffa5c540.setValue(6, 1, 1.0);
+data_ffa5c540.setValue(7, 0, 'mediawiki/extensions/Validator');
+data_ffa5c540.setValue(7, 1, 1.0);
+data_ffa5c540.setValue(8, 0, 'mediawiki/extensions/Phalanx');
+data_ffa5c540.setValue(8, 1, 1.0);
+data_ffa5c540.setValue(9, 0, 'mediawiki/extensions/MassEditRegex');
+data_ffa5c540.setValue(9, 1, 1.0);
+var chart_ffa5c540 = new google.visualization.PieChart(document.getElementById('chartRepositories'));
+chart_ffa5c540.draw(data_ffa5c540, { title: 'active repositories', colors:['#3810a6','#7110a6','#1068a6','#a61029','#1056a6','#63a610','#a64210','#109ca6','#7610a6','#a61083',], legend: { position:'none' } });
+
+var data_39b7080b = new google.visualization.DataTable();
+data_39b7080b.addColumn('string', 'author');
+data_39b7080b.addColumn('number', 'commits');
+data_39b7080b.addRows(17);
+data_39b7080b.setValue(0, 0, 'jeroendedauw');
+data_39b7080b.setValue(0, 1, 28.0);
+data_39b7080b.setValue(1, 0, 'Ori Livneh');
+data_39b7080b.setValue(1, 1, 12.0);
+data_39b7080b.setValue(2, 0, 'Kunal Mehta');
+data_39b7080b.setValue(2, 1, 6.0);
+data_39b7080b.setValue(3, 0, 'Yuki Shira');
+data_39b7080b.setValue(3, 1, 4.0);
+data_39b7080b.setValue(4, 0, 'legoktm');
+data_39b7080b.setValue(4, 1, 3.0);
+data_39b7080b.setValue(5, 0, 'Hoo man');
+data_39b7080b.setValue(5, 1, 2.0);
+data_39b7080b.setValue(6, 0, 'Santhosh Thottingal');
+data_39b7080b.setValue(6, 1, 2.0);
+data_39b7080b.setValue(7, 0, 'Jeroen De Dauw');
+data_39b7080b.setValue(7, 1, 2.0);
+data_39b7080b.setValue(8, 0, 'Kip');
+data_39b7080b.setValue(8, 1, 2.0);
+data_39b7080b.setValue(9, 0, 'Marius Hoch');
+data_39b7080b.setValue(9, 1, 2.0);
+var chart_39b7080b = new google.visualization.PieChart(document.getElementById('chartAuthors'));
+chart_39b7080b.draw(data_39b7080b, { title: 'active authors', colors:['#a6106c','#71a610','#a1a610','#a61040','#a68010','#a68010','#a67410','#1022a6','#104ca6','#1080a6',], legend: { position:'none' } });
+
+}
+
+/*-->]]>*/</script>
+
+<script type=""text/javascript"" src=""resources/com.gitblit.wicket.ng.NgController/angular.js""></script>
+<script type=""text/javascript"" ><!--/*--><![CDATA[/*><!--*/
+<!-- AngularJS projectsCtrl data controller -->
+function projectsCtrl($scope) {
+	$scope.projectsList = [{""p"":""mediawiki"",""n"":""mediawiki"",""t"":""18 mins ago"",""d"":""2013-07-22"",""i"":"""",""c"":626},{""p"":""labs"",""n"":""labs"",""t"":""5 hours ago"",""d"":""2013-07-21"",""i"":"""",""c"":9},{""p"":""operations"",""n"":""operations"",""t"":""8 hours ago"",""d"":""2013-07-21"",""i"":"""",""c"":72},{""p"":""main"",""n"":""Main Repositories"",""t"":""15 hours ago"",""d"":""2013-07-21"",""i"":""main group of repositories"",""c"":19},{""p"":""pywikibot"",""n"":""pywikibot"",""t"":""21 hours ago"",""d"":""2013-07-21"",""i"":"""",""c"":4},{""p"":""analytics"",""n"":""analytics"",""t"":""2 days ago"",""d"":""2013-07-20"",""i"":"""",""c"":39},{""p"":""wikimedia"",""n"":""wikimedia"",""t"":""3 days ago"",""d"":""2013-07-19"",""i"":"""",""c"":24},{""p"":""integration"",""n"":""integration"",""t"":""3 days ago"",""d"":""2013-07-19"",""i"":"""",""c"":11},{""p"":""qa"",""n"":""qa"",""t"":""3 days ago"",""d"":""2013-07-19"",""i"":"""",""c"":1},{""p"":""apps"",""n"":""apps"",""t"":""4 days ago"",""d"":""2013-07-18"",""i"":"""",""c"":4},{""p"":""wiktionary"",""n"":""wiktionary"",""t"":""4 weeks ago"",""d"":""2013-06-21"",""i"":"""",""c"":1},{""p"":""test"",""n"":""test"",""t"":""8 weeks ago"",""d"":""2013-05-25"",""i"":"""",""c"":2},{""p"":""officeit"",""n"":""officeit"",""t"":""4 months ago"",""d"":""2013-04-08"",""i"":"""",""c"":1},{""p"":""VisualEditor"",""n"":""VisualEditor"",""t"":""6 months ago"",""d"":""2013-01-29"",""i"":"""",""c"":1},{""p"":""glam"",""n"":""glam"",""t"":""10 months ago"",""d"":""2012-10-11"",""i"":"""",""c"":1}];
+}
+
+/*-->]]>*/</script>
+
+<script type=""text/javascript"" ><!--/*--><![CDATA[/*><!--*/
+<!-- AngularJS activeCtrl data controller -->
+function activeCtrl($scope) {
+	$scope.activeList = [{""r"":""mediawiki/extensions.git"",""n"":""extensions"",""p"":""mediawiki/"",""t"":""18 mins ago"",""d"":""2013-07-22"",""i"":"""",""s"":0,""c"":""#7110a6"",""wc"":0},{""r"":""mediawiki/core.git"",""n"":""core"",""p"":""mediawiki/"",""t"":""2 hours ago"",""d"":""2013-07-22"",""i"":"""",""s"":0,""c"":""#3810a6"",""wc"":0},{""r"":""mediawiki/extensions/TranslationNotifications.git"",""n"":""TranslationNotifications"",""p"":""mediawiki/extensions/"",""t"":""2 hours ago"",""d"":""2013-07-22"",""i"":"""",""s"":0,""c"":""#1068a6"",""wc"":0},{""r"":""mediawiki/extensions/LaTeXML.git"",""n"":""LaTeXML"",""p"":""mediawiki/extensions/"",""t"":""5 hours ago"",""d"":""2013-07-22"",""i"":"""",""s"":0,""c"":""#a67b10"",""wc"":0},{""r"":""labs/tools/lolrrit.git"",""n"":""lolrrit"",""p"":""labs/tools/"",""t"":""5 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a6102e"",""wc"":0},{""r"":""mediawiki/extensions/PollNY.git"",""n"":""PollNY"",""p"":""mediawiki/extensions/"",""t"":""7 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61029"",""wc"":0},{""r"":""operations/puppet.git"",""n"":""puppet"",""p"":""operations/"",""t"":""8 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#106ca6"",""wc"":0},{""r"":""mediawiki/extensions/Wikibase.git"",""n"":""Wikibase"",""p"":""mediawiki/extensions/"",""t"":""9 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a310a6"",""wc"":0},{""r"":""mediawiki/extensions/EventLogging.git"",""n"":""EventLogging"",""p"":""mediawiki/extensions/"",""t"":""9 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a631"",""wc"":0},{""r"":""mediawiki/extensions/WikimediaMessages.git"",""n"":""WikimediaMessages"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64510"",""wc"":0},{""r"":""mediawiki/extensions/Wikilog.git"",""n"":""Wikilog"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a6106c"",""wc"":0},{""r"":""mediawiki/extensions/WikiLexicalData.git"",""n"":""WikiLexicalData"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#101da6"",""wc"":0},{""r"":""mediawiki/extensions/WikiForum.git"",""n"":""WikiForum"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a618"",""wc"":0},{""r"":""mediawiki/extensions/WikiEditor.git"",""n"":""WikiEditor"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#8310a6"",""wc"":0},{""r"":""mediawiki/extensions/VisualEditor.git"",""n"":""VisualEditor"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1aa610"",""wc"":0},{""r"":""mediawiki/extensions/Validator.git"",""n"":""Validator"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#109ca6"",""wc"":0},{""r"":""mediawiki/extensions/UserMerge.git"",""n"":""UserMerge"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#2ea610"",""wc"":0},{""r"":""mediawiki/extensions/UploadWizard.git"",""n"":""UploadWizard"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#3110a6"",""wc"":0},{""r"":""mediawiki/extensions/UniversalLanguageSelector.git"",""n"":""UniversalLanguageSelector"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#6510a6"",""wc"":0},{""r"":""mediawiki/extensions/TwnMainPage.git"",""n"":""TwnMainPage"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#8d10a6"",""wc"":0},{""r"":""mediawiki/extensions/Translate.git"",""n"":""Translate"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1099a6"",""wc"":0},{""r"":""mediawiki/extensions/Sudo.git"",""n"":""Sudo"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61060"",""wc"":0},{""r"":""mediawiki/extensions/SemanticMediaWiki.git"",""n"":""SemanticMediaWiki"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a627"",""wc"":0},{""r"":""mediawiki/extensions/SemanticForms.git"",""n"":""SemanticForms"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61013"",""wc"":0},{""r"":""mediawiki/extensions/SemanticDrilldown.git"",""n"":""SemanticDrilldown"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61074"",""wc"":0},{""r"":""mediawiki/extensions/SecurePoll.git"",""n"":""SecurePoll"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61079"",""wc"":0},{""r"":""mediawiki/extensions/RevisionCommentSupplement.git"",""n"":""RevisionCommentSupplement"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#102ca6"",""wc"":0},{""r"":""mediawiki/extensions/Renameuser.git"",""n"":""Renameuser"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a6a3"",""wc"":0},{""r"":""mediawiki/extensions/ProofreadPage.git"",""n"":""ProofreadPage"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#3110a6"",""wc"":0},{""r"":""mediawiki/extensions/Premoderation.git"",""n"":""Premoderation"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#7ea610"",""wc"":0},{""r"":""mediawiki/extensions/Phalanx.git"",""n"":""Phalanx"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#7610a6"",""wc"":0},{""r"":""mediawiki/extensions/PageSchemas.git"",""n"":""PageSchemas"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64510"",""wc"":0},{""r"":""mediawiki/extensions/OpenStackManager.git"",""n"":""OpenStackManager"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a62c"",""wc"":0},{""r"":""mediawiki/extensions/OAuth.git"",""n"":""OAuth"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a636"",""wc"":0},{""r"":""mediawiki/extensions/Nuke.git"",""n"":""Nuke"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1056a6"",""wc"":0},{""r"":""mediawiki/extensions/NewUserMessage.git"",""n"":""NewUserMessage"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1051a6"",""wc"":0},{""r"":""mediawiki/extensions/MoodBar.git"",""n"":""MoodBar"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64210"",""wc"":0},{""r"":""mediawiki/extensions/MobileFrontend.git"",""n"":""MobileFrontend"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#4ca610"",""wc"":0},{""r"":""mediawiki/extensions/MathSearch.git"",""n"":""MathSearch"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a63110"",""wc"":0},{""r"":""mediawiki/extensions/Math.git"",""n"":""Math"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#97a610"",""wc"":0},{""r"":""mediawiki/extensions/MassMessage.git"",""n"":""MassMessage"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#36a610"",""wc"":0},{""r"":""mediawiki/extensions/MassEditRegex.git"",""n"":""MassEditRegex"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61083"",""wc"":0},{""r"":""mediawiki/extensions/Maintenance.git"",""n"":""Maintenance"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#9910a6"",""wc"":0},{""r"":""mediawiki/extensions/LiquidThreads.git"",""n"":""LiquidThreads"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a68810"",""wc"":0},{""r"":""mediawiki/extensions/LinkFilter.git"",""n"":""LinkFilter"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1038a6"",""wc"":0},{""r"":""mediawiki/extensions/LastModified.git"",""n"":""LastModified"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#63a610"",""wc"":0},{""r"":""mediawiki/extensions/InviteSignup.git"",""n"":""InviteSignup"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a67b10"",""wc"":0},{""r"":""mediawiki/extensions/Interwiki.git"",""n"":""Interwiki"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61033"",""wc"":0},{""r"":""mediawiki/extensions/ImageMap.git"",""n"":""ImageMap"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a654"",""wc"":0},{""r"":""mediawiki/extensions/GoogleMaps.git"",""n"":""GoogleMaps"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#83a610"",""wc"":0},{""r"":""mediawiki/extensions/GlobalBlocking.git"",""n"":""GlobalBlocking"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#7610a6"",""wc"":0},{""r"":""mediawiki/extensions/GettingStarted.git"",""n"":""GettingStarted"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#4510a6"",""wc"":0},{""r"":""mediawiki/extensions/FlaggedRevs.git"",""n"":""FlaggedRevs"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#9710a6"",""wc"":0},{""r"":""mediawiki/extensions/ExpandTemplates.git"",""n"":""ExpandTemplates"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61042"",""wc"":0},{""r"":""mediawiki/extensions/EducationProgram.git"",""n"":""EducationProgram"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#65a610"",""wc"":0},{""r"":""mediawiki/extensions/Editcount.git"",""n"":""Editcount"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1036a6"",""wc"":0},{""r"":""mediawiki/extensions/Echo.git"",""n"":""Echo"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64f10"",""wc"":0},{""r"":""mediawiki/extensions/DiscussionThreading.git"",""n"":""DiscussionThreading"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a68d10"",""wc"":0},{""r"":""mediawiki/extensions/Disambiguator.git"",""n"":""Disambiguator"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a63b10"",""wc"":0},{""r"":""mediawiki/extensions/DeleteBatch.git"",""n"":""DeleteBatch"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#104fa6"",""wc"":0},{""r"":""mediawiki/extensions/DataValues.git"",""n"":""DataValues"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a64f10"",""wc"":0},{""r"":""mediawiki/extensions/DataTransfer.git"",""n"":""DataTransfer"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61018"",""wc"":0},{""r"":""mediawiki/extensions/ConfirmEdit.git"",""n"":""ConfirmEdit"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a6108d"",""wc"":0},{""r"":""mediawiki/extensions/ConfirmAccount.git"",""n"":""ConfirmAccount"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#7ba610"",""wc"":0},{""r"":""mediawiki/extensions/Configure.git"",""n"":""Configure"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#36a610"",""wc"":0},{""r"":""mediawiki/extensions/Comments.git"",""n"":""Comments"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#8f10a6"",""wc"":0},{""r"":""mediawiki/extensions/Commentbox.git"",""n"":""Commentbox"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a62910"",""wc"":0},{""r"":""mediawiki/extensions/Collection.git"",""n"":""Collection"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a66a10"",""wc"":0},{""r"":""mediawiki/extensions/CheckUser.git"",""n"":""CheckUser"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a61045"",""wc"":0},{""r"":""mediawiki/extensions/CentralNotice.git"",""n"":""CentralNotice"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a68d"",""wc"":0},{""r"":""mediawiki/extensions/CentralAuth.git"",""n"":""CentralAuth"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a65e10"",""wc"":0},{""r"":""mediawiki/extensions/Campaigns.git"",""n"":""Campaigns"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#13a610"",""wc"":0},{""r"":""mediawiki/extensions/BookManagerv2.git"",""n"":""BookManagerv2"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#56a610"",""wc"":0},{""r"":""mediawiki/extensions/Babel.git"",""n"":""Babel"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1085a6"",""wc"":0},{""r"":""mediawiki/extensions/ArticleFeedbackv5.git"",""n"":""ArticleFeedbackv5"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a65110"",""wc"":0},{""r"":""mediawiki/extensions/Ads.git"",""n"":""Ads"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a3a6"",""wc"":0},{""r"":""mediawiki/extensions/AbuseFilter.git"",""n"":""AbuseFilter"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#4aa610"",""wc"":0},{""r"":""mediawiki/extensions/APC.git"",""n"":""APC"",""p"":""mediawiki/extensions/"",""t"":""10 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#6c10a6"",""wc"":0},{""r"":""openzim.git"",""n"":""openzim"",""p"":"""",""t"":""15 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a66310"",""wc"":0},{""r"":""mediawiki/extensions/WikibaseDataModel.git"",""n"":""WikibaseDataModel"",""p"":""mediawiki/extensions/"",""t"":""15 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#6510a6"",""wc"":0},{""r"":""mediawiki/extensions/WikibaseQueryEngine.git"",""n"":""WikibaseQueryEngine"",""p"":""mediawiki/extensions/"",""t"":""16 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a68f10"",""wc"":0},{""r"":""mediawiki/extensions/UpdateMediaWiki.git"",""n"":""UpdateMediaWiki"",""p"":""mediawiki/extensions/"",""t"":""16 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#2910a6"",""wc"":0},{""r"":""mediawiki/extensions/Serialization.git"",""n"":""Serialization"",""p"":""mediawiki/extensions/"",""t"":""16 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#1045a6"",""wc"":0},{""r"":""mediawiki/extensions/WikibaseDatabase.git"",""n"":""WikibaseDatabase"",""p"":""mediawiki/extensions/"",""t"":""16 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a627"",""wc"":0},{""r"":""mediawiki/extensions/Diff.git"",""n"":""Diff"",""p"":""mediawiki/extensions/"",""t"":""17 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#a66a10"",""wc"":0},{""r"":""mediawiki/extensions/Ask.git"",""n"":""Ask"",""p"":""mediawiki/extensions/"",""t"":""17 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#10a67b"",""wc"":0},{""r"":""pywikibot/core.git"",""n"":""core"",""p"":""pywikibot/"",""t"":""21 hours ago"",""d"":""2013-07-21"",""i"":"""",""s"":0,""c"":""#22a610"",""wc"":0}];
+}
+
+/*-->]]>*/</script>
+
+</head>
+
+	<body>
+
+		<!-- page content -->
+		[a metric fuckton of HTML]
+
+		<!-- Override Bootstrap's responsive menu background highlighting -->
+		<style>
+		@media (max-width: 979px) {
+			.nav-collapse .nav > li > a:hover, .nav-collapse .dropdown-menu a:hover {
+				background-color: #002060;
+			}
+			
+			.navbar div > ul .dropdown-menu li a {
+				color: #ccc;
+			}
+		}
+		</style>
+		
+		<!-- Include scripts at end for faster page loading -->
+		<script type=""text/javascript"" src=""bootstrap/js/jquery.js""></script>
+		<script type=""text/javascript"" src=""bootstrap/js/bootstrap.js""></script>		
+	</body>
+</html>
+real	10m1.110s
+user	0m0.018s
+sys	0m0.028s",1374468963,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,"It's happening again. :-(
+
+$ time curl https://git.wikimedia.org
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>
+
+real	12m1.110s
+user	0m0.015s
+sys	0m0.021s",1374468155,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+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.",1374450350,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot,git.wikimedia.org being down is highly disruptive to support work in #mediawiki.,1374442461,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+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/
+<!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
+<html><head>
+<title>502 Proxy Error</title>
+</head><body>
+<h1>Proxy Error</h1>
+<p>The proxy server received an invalid
+response from an upstream server.<br />
+The proxy server could not handle the request <em><a href=""/"">GET&nbsp;/</a></em>.<p>
+Reason: <strong>Error reading from remote server</strong></p></p>
+</body></html>",1374427922,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-m7yoxj62gdjohzchm7zw,task_subcomment,NA
+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",1374370800,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-iycnxhmj2yiay4bvfsic,task_description,resolved
+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?",1381630832,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-iycnxhmj2yiay4bvfsic,task_subcomment,NA
+VisualEditor: Bypass browser blacklist,"You can already bypass the blacklist by using ?vewhitelist=1 - sorry, we should document this somewhere!",1377532459,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iycnxhmj2yiay4bvfsic,task_subcomment,NA
+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.",1374372834,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-iycnxhmj2yiay4bvfsic,task_subcomment,NA
+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",1374347580,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4imcgove7xglvcqm25ym,task_description,resolved
+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.",1437778276,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+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?,1430994055,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+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 <pre> 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.",1425550174,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+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...",1425486185,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+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.,1378654619,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-4imcgove7xglvcqm25ym,task_subcomment,NA
+"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",1374332100,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-6gr7275ayzz2al57mitp,task_description,resolved
+"Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit",Verified in betalabs.,1416959359,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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]]",1416955369,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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",1416955169,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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.,1395357064,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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.",1390933967,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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.",1378458535,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+"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. ***,1378458424,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-6gr7275ayzz2al57mitp,task_subcomment,NA
+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",1374320940,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_description,resolved
+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",1386964645,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1386964633,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1386964508,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1386964432,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+Default whitespace for headings should include spaces before/after ==,Yes. Will be deployed today. Closing this bug now.,1386171623,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+Default whitespace for headings should include spaces before/after ==,I assume this is fixed now? Thank you!,1386166246,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1386114683,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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",1385054475,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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.",1385053828,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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?",1385053073,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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.",1383167033,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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.",1374331135,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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.",1374330631,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+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?",1374330299,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-eebs7mwekgwvhg5ap6qk,task_subcomment,NA
+"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}",1374285540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_description,resolved
+"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.",1535731638,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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.",1450389552,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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. ***,1415063196,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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'",1374756959,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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}",1374633830,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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.",1374538584,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+"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:
+<ref>[http://gypsywaggons.co.uk/varhistory.htm ""History of the Vardo (Gypsy Caravan)""], ValleyStream Media, 2009</ref>
+
+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?",1374296176,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3ree5vwpvfff7nqhn3qg,task_subcomment,NA
+Parsoid: Output MathJax rendering for Math tags instead of images,"When MathJax is enabled we should render a <span> containing TeX, instead of an image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374264060,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-m5725ohwtikdne7f72hd,task_description,invalid
+Parsoid: Output MathJax rendering for Math tags instead of images,MathJax support is discountinued T99369,1442497839,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.,1402834289,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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).",1378528443,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378509011,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378492816,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378428362,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378426992,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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?",1378359915,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378359248,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1378354273,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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] <gwicke> do you have a node package?
+[17:03] <pkrautzberger> ah. no. The problem is that MathJax requires a dom  right now. But we plan to liberate parts.
+[17:03] <gwicke> we have a dom
+[17:03] <pkrautzberger> (a lot functionality doesn't make sense outside the DOM).
+[17:04] <gwicke> domino currently
+[17:04] <pkrautzberger> but TeX2MathML conversion could be isolated easily (MathML to SVG not as easily). BTW our internal format is MathML.
+[17:04] <gwicke> it only implements DOM4 in case that makes a difference
+[17:04] <pkrautzberger> I'm not sure if dom4 would be a problem.
+[17:04] <pkrautzberger> but we've seen people use dom runners.
+[17:04] <gwicke> we could also use JSDom for math if that helps
+[17:05] <gwicke> supports the other levels
+[17:05] <gwicke> and script tag execution
+[17:05] <pkrautzberger> well, ideally we could just isolate that from the dom.
+[17:05] <pkrautzberger> but yes, I know someone who got jsdom to work with MathJax.
+[17:06] <gwicke> ah, that sounds promising",1378339833,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+Parsoid: Output MathJax rendering for Math tags instead of images,See bug 52031.,1376614484,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+Parsoid: Output MathJax rendering for Math tags instead of images,Have we filed a bug against the mw api to support this?,1374764072,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1374265056,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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.",1374264665,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-m5725ohwtikdne7f72hd,task_subcomment,NA
+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",1374238320,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_description,resolved
+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",1380811545,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380751646,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380747187,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380746244,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380742224,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1380644334,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"I have a patch for this one, taking it.",1380644270,PHID-USER-56wtmb23orq4pu5liyj5,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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.",1376614725,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,Can't reproduce on enwp for obvious reasons.,1375060582,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki,"Created attachment 12996
+screenshot of adding a wikipedia: link
+
+**Attached**: {F11284}",1375060388,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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.",1374644195,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mdqhw3wzqwlxbr4xogeu,task_subcomment,NA
+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",1374234180,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-boasjpxas32sxaoibmuy,task_description,resolved
+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.
+",1434487685,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-boasjpxas32sxaoibmuy,task_subcomment,NA
+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.",1374236089,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-boasjpxas32sxaoibmuy,task_subcomment,NA
+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}",1374229560,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-q5ayyohzxfrkbwwrho46,task_description,resolved
+VisualEditor: Search of parameters in transclusion editor should be case insensitive,Done by gerrit 117305.,1394405793,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q5ayyohzxfrkbwwrho46,task_subcomment,NA
+VisualEditor: Search of parameters in transclusion editor should be case insensitive,*** Bug 52950 has been marked as a duplicate of this bug. ***,1377426861,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-q5ayyohzxfrkbwwrho46,task_subcomment,NA
+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.",1374229905,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-q5ayyohzxfrkbwwrho46,task_subcomment,NA
+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}",1374229080,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_description,resolved
+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.,1394073936,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_subcomment,NA
+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.",1375339576,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_subcomment,NA
+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?",1375325672,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_subcomment,NA
+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.",1374700322,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5rpxkdg4clk2xzkgyeci,task_subcomment,NA
+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",1374224700,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_description,resolved
+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.",1403019840,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_subcomment,NA
+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.,1403008896,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_subcomment,NA
+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,1380426562,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_subcomment,NA
+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.)"".",1379948638,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-nkihkps7zwe2jnpuv2vo,task_subcomment,NA
+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",1374197220,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4iqn2br77eamftwdpwfs,task_description,resolved
+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",1405459729,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+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",1405459572,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+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",1397086933,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+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",1397086880,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+VisualEditor: Remove (and stop adding) useless documentation,Note that there is one (exactly one) piece of useful information in that comment: @abstract,1374259388,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4iqn2br77eamftwdpwfs,task_subcomment,NA
+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",1374179400,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-udzfkpaotefzeteimh7e,task_description,declined
+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.",1703380210,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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.",1422061964,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+Page actions are wrong for VisualEditor,@aklapper  Hmm..  This should not be assigned to me.  I'm not sure how that happen.  ,1422052247,PHID-USER-u64h73gx226teqcym3r5,True,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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?",1421788770,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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).,1392911323,PHID-USER-qb5aoo443n6fezsozhv4,True,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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.",1392854320,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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).",1382567111,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+Page actions are wrong for VisualEditor,"Yes, good catch.  VE doesn't touch wgPostEdit, which we're using, at all.",1374191192,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+Page actions are wrong for VisualEditor,"**swalling** wrote:
+
+Would this impact page-save-success logging for VE?",1374191007,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-udzfkpaotefzeteimh7e,task_subcomment,NA
+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",1374171240,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_description,resolved
+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.",1726475742,PHID-USER-povcbbfr2b6v4te3anc7,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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.",1724605148,PHID-USER-povcbbfr2b6v4te3anc7,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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",1392851785,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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",1392846794,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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!",1392846139,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+Images specified with size foopxpx render at native size,"Yes, 'pxpx' is actually a ""feature"".  See bug 13500.
+
+Working on a fix...",1392845150,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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"".",1385033707,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+Images specified with size foopxpx render at native size,*** Bug 54371 has been marked as a duplicate of this bug. ***,1380930193,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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.",1376614949,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+Images specified with size foopxpx render at native size,*** Bug 51826 has been marked as a duplicate of this bug. ***,1374548109,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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",1374544369,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+Images specified with size foopxpx render at native size,*** Bug 51845 has been marked as a duplicate of this bug. ***,1374544099,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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,1374183991,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7uebrq6s5hgkckkrqkv5,task_subcomment,NA
+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",1374166740,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ufv5laxxz2gup5mbsoae,task_description,resolved
+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.",1429468007,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ufv5laxxz2gup5mbsoae,task_subcomment,NA
+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.",1392229924,PHID-USER-brn4v5ta45bnw4f5as3h,False,PHID-TASK-ufv5laxxz2gup5mbsoae,task_subcomment,NA
+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.""",1374224206,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ufv5laxxz2gup5mbsoae,task_subcomment,NA
+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",1374162360,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-mc4ekk7vrriv5kycc2u2,task_description,resolved
+VisualEditor: Clarify beta explanation text,I think this is now better; closing.,1374257435,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mc4ekk7vrriv5kycc2u2,task_subcomment,NA
+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.",1374162561,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mc4ekk7vrriv5kycc2u2,task_subcomment,NA
+"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",1374158040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-63tv3lkov2okxud2zyxo,task_description,resolved
+"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.,1375297757,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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",1375297187,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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",1375233664,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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",1375217200,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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",1375181969,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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' )?,1375098833,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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?",1375098410,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+"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,1375098204,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-63tv3lkov2okxud2zyxo,task_subcomment,NA
+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",1374109200,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gdwu5ick5nfagic7txm6,task_description,resolved
+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.,1380056460,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-gdwu5ick5nfagic7txm6,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"VisualEditor should support adding and editing the code tag (<code></code>).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374109140,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ktldutlvil3ngaxt2l2k,task_description,resolved
+VisualEditor: Support the <code> 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.",1374868236,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 76077 merged by jenkins-bot:
+Code annotation button
+
+https://gerrit.wikimedia.org/r/76077",1374867696,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 76074 merged by jenkins-bot:
+'CodeScript' => 'Code'
+
+https://gerrit.wikimedia.org/r/76074",1374867080,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 76077 had a related patch set uploaded by Esanders:
+Code annotation
+
+https://gerrit.wikimedia.org/r/76077",1374836628,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 76074 had a related patch set uploaded by Esanders:
+'CodeScript' => 'Code'
+
+https://gerrit.wikimedia.org/r/76074",1374836623,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"With the latest master, <code> 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.",1374255093,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 74563 merged by jenkins-bot:
+De-alienate <code>foo</code> blocks (code element)
+
+https://gerrit.wikimedia.org/r/74563",1374195080,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+VisualEditor: Support the <code> tag as a text annotation,"Change 74563 had a related patch set uploaded by Jforrester:
+De-alienate <code>foo</code> blocks (code element)
+
+https://gerrit.wikimedia.org/r/74563",1374192477,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ktldutlvil3ngaxt2l2k,task_subcomment,NA
+"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",1374104340,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_description,resolved
+"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",1675614246,PHID-USER-povcbbfr2b6v4te3anc7,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1538452334,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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).",1538452237,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1452116407,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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 ?,1452116319,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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)",1452057316,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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]]",1452034617,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1450298905,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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. ,1450297840,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.,1450294851,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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/",1450283149,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.
+",1450272250,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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),1450209312,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1449131751,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"Add more mw.hook events for wikipage: diff, categories etc.",Is this resolved? If not what's left to do?,1449100826,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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?",1449062407,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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]]",1448935559,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"Add more mw.hook events for wikipage: diff, categories etc.","Not mentioned yet, but IMHO makes sense, too: `#firstHeading`",1441362498,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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]]
+",1434906198,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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]]
+",1434320070,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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 ?",1427484714,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1403380680,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"Add more mw.hook events for wikipage: diff, categories etc.",[Bumping TM as MediaWiki 1.22.0 tarball was released today.],1386383869,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1380208131,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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.",1374111932,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kg6wsbien7yipr4dzrul,task_subcomment,NA
+"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",1374087720,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_description,resolved
+"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.,1383478009,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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} $).",1383474047,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1377303810,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1377185317,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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.,1375218658,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1375217249,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1375207097,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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.).",1375201616,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1374797897,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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,1374342847,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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.",1374274354,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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.",1374176027,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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",1374111569,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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).",1374089581,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+"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. ***,1374088447,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-a3yp2evtjuq3hjqdrvhc,task_subcomment,NA
+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}",1374077760,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-ca6crnotrmabx3jkz5wk,task_description,resolved
+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?",1423881296,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+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.",1423765790,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+VisualEditor: Node action icon (e.g. for template) appearing in wrong location,All test cases provided appear to be working now.,1405201255,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+VisualEditor: Node action icon (e.g. for template) appearing in wrong location,*** Bug 60652 has been marked as a duplicate of this bug. ***,1393455560,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+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 .,1378477636,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+VisualEditor: Node action icon (e.g. for template) appearing in wrong location,"Created attachment 13252
+An icon far, far away...
+
+**Attached**: {F11878}",1378477567,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ca6crnotrmabx3jkz5wk,task_subcomment,NA
+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",1374077220,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_description,resolved
+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. ***,1395360091,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_subcomment,NA
+VisualEditor: Abandoning VE load by navigating away before Parsoid load complete throws API error dialog,"\o/
+
+Thanks, Alex and Roan!",1391042211,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_subcomment,NA
+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",1391020997,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_subcomment,NA
+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",1390954780,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-brtl2hvq3mpywf2r3lkp,task_subcomment,NA
+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",1374063480,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_description,resolved
+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",1384506400,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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!",1384484254,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1384300982,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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.",1383942790,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1383942688,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1383940906,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1374090597,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN ),Merged.,1374090551,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+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",1374063814,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iudy2zuexclkhlwqjbkn,task_subcomment,NA
+"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",1374049980,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-ss6harhqovaxcprykzge,task_description,resolved
+"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.,1374676726,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ss6harhqovaxcprykzge,task_subcomment,NA
+"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",1374676288,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ss6harhqovaxcprykzge,task_subcomment,NA
+"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",1374674902,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ss6harhqovaxcprykzge,task_subcomment,NA
+"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.,1374478890,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-ss6harhqovaxcprykzge,task_subcomment,NA
+"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",1374026460,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7auhm5son76ryeyfeyid,task_description,resolved
+"VisualEditor: Beta notice incorrectly highlights ""Leave feedback"" link when hovering the notice",This was fixed in the toolbar re-write.,1383002871,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7auhm5son76ryeyfeyid,task_subcomment,NA
+"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).,1375825378,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7auhm5son76ryeyfeyid,task_subcomment,NA
+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 <nowiki/>}}) to protect the trailing space?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61049",1374013440,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-573oqdvpm2jqlbzsvzdg,task_description,resolved
+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.,1385385582,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-573oqdvpm2jqlbzsvzdg,task_subcomment,NA
+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",1374012600,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-unahzezsufzzdb4k4beo,task_description,resolved
+Generic first edit tour,"**swalling** wrote:
+
+Tours for 'firstedit' and 'firsteditve' are out in the wild. :)",1381904718,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+Generic first edit tour,This should also have browser tests.,1375132894,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+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.",1374013366,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+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.",1374012824,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+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",1374012729,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+Generic first edit tour,In progress at https://gerrit.wikimedia.org/r/#/c/64981/,1374012685,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-unahzezsufzzdb4k4beo,task_subcomment,NA
+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",1373998440,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-g24bxdialbz5a5bcp4qb,task_description,resolved
+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",1395869325,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g24bxdialbz5a5bcp4qb,task_subcomment,NA
+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",1395866992,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g24bxdialbz5a5bcp4qb,task_subcomment,NA
+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",1373995560,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-kg4p7wmv7m2n5tdejrm4,task_description,resolved
+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.,1437781075,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-kg4p7wmv7m2n5tdejrm4,task_subcomment,NA
+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",1373995771,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-kg4p7wmv7m2n5tdejrm4,task_subcomment,NA
+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",1373980800,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_description,resolved
+Template search results list should contain each template's descripton,Verified the fix in Betalabs,1429568922,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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]]",1429262905,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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]]
+",1428697842,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+Template search results list should contain each template's descripton,"Thanks for the explanation, I've now reported it as bug 51822.",1374511823,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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.",1374509714,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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?",1374508615,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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.",1374507636,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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).",1374502086,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+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.",1374462543,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-3es7m4cbr63gg2w4l5or,task_subcomment,NA
+"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",1373959860,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-t4nrv75pjo2r4cxn47di,task_description,resolved
+"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",1411169862,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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",1409939258,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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.",1400616978,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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?",1378952753,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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.",1375183561,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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. ***,1375183466,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+"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.",1374507813,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t4nrv75pjo2r4cxn47di,task_subcomment,NA
+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}",1373945100,PHID-USER-fuj45iylbizjg3yhehjt,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_description,open
+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",1603885261,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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?",1535697999,PHID-USER-hvywcttgalazbjxfl3tq,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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 :/",1535663319,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1535650055,PHID-USER-hvywcttgalazbjxfl3tq,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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]]",1535648306,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1535636345,PHID-USER-hvywcttgalazbjxfl3tq,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1483735245,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1482964388,PHID-USER-jqjb54lbf7psat6shbcc,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1375214945,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1375206737,PHID-USER-fuj45iylbizjg3yhehjt,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+VisualEditor: Allow AbuseFilter rules to identify VE edits,"s/invisible to VE/invisible to AF/. I swear, I did proofread that. :)",1375206441,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+VisualEditor: Allow AbuseFilter rules to identify VE edits,"s/attempts/happens/, of course.",1375206175,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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 :)",1375206102,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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?",1375203722,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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).,1375203423,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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?",1375203347,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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.",1375201847,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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).",1374075407,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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",1373946577,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-gou4ejmnkpg5lgq6cdfx,task_subcomment,NA
+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",1373924940,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-erfxy2a7265vjb4b2dj3,task_description,resolved
+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",1377205462,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-erfxy2a7265vjb4b2dj3,task_subcomment,NA
+VisualEditor: Page loading animated image is only LTR,Merged. Will go out with wmf15.,1377205420,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-erfxy2a7265vjb4b2dj3,task_subcomment,NA
+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",1377204612,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-erfxy2a7265vjb4b2dj3,task_subcomment,NA
+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",1373909880,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-mo5dvj5do74gbwyx6vrs,task_description,resolved
+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",1383945120,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mo5dvj5do74gbwyx6vrs,task_subcomment,NA
+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",1382632926,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mo5dvj5do74gbwyx6vrs,task_subcomment,NA
+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).""",1375969318,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-mo5dvj5do74gbwyx6vrs,task_subcomment,NA
+"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}",1373906820,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-643scf5lq5v72slluprm,task_description,resolved
+"VisualEditor: Toolbar icons - ""reference"" (bookmark) alternatives or improvements",I'm going to provisionally deem this solved with the new icon.,1401472548,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-643scf5lq5v72slluprm,task_subcomment,NA
+"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.",1373981836,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-643scf5lq5v72slluprm,task_subcomment,NA
+"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)",1373907050,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-643scf5lq5v72slluprm,task_subcomment,NA
+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",1373852760,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_description,resolved
+VisualEditor: Improve how we suppress reference warnings in template rendering,"Done and merged, now that wmf12 is deployed everywhere.",1375327521,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+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",1375326645,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+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",1374193845,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+VisualEditor: Improve how we suppress reference warnings in template rendering,https://gerrit.wikimedia.org/r/#/c/73614/,1373886910,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+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",1373852814,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-npqg6q6ozudz2pqkgmjm,task_subcomment,NA
+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",1373850240,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-6ana44vgeezadw6ore4y,task_description,resolved
+VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems),This flyout is now much wider.,1393633638,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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. ***,1374162111,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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.",1374079435,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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.",1374030006,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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}",1373886191,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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!",1373883699,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6ana44vgeezadw6ore4y,task_subcomment,NA
+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",1373799300,PHID-USER-7clmfrlb7fwuko4jdjbs,False,PHID-TASK-yv3kce72452r37igamnp,task_description,resolved
+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],1440343623,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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.,1386877406,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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",1374265649,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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",1374265553,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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.",1373841014,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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'.",1373834454,PHID-USER-7clmfrlb7fwuko4jdjbs,False,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+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.",1373812879,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yv3kce72452r37igamnp,task_subcomment,NA
+VisualEditor: Templated calls to <references /> (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",1373770740,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-a6e5anlp2g7eyftsen6n,task_description,duplicate
+VisualEditor: Templated calls to <references /> (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 <references /> call, and neither does Parsoid unless it re-parses it.
+
+Consequently, we are expanding the syntax for <references /> to make {{reflist}} unnecessary. WONTFIXing this bug.",1385383497,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a6e5anlp2g7eyftsen6n,task_subcomment,NA
+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",1373734200,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-6vanypiuvvogqhl2yqvj,task_description,resolved
+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 ***",1374619928,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-6vanypiuvvogqhl2yqvj,task_subcomment,NA
+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.",1373930449,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-6vanypiuvvogqhl2yqvj,task_subcomment,NA
+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?",1373883480,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-6vanypiuvvogqhl2yqvj,task_subcomment,NA
+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",1373722680,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_description,resolved
+References inside templates don't appear in the reference list in VisualEditor,"This seems to be fixed, although T52474 (which is similar) remains open.",1434419761,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,*** Bug 69066 has been marked as a duplicate of this bug. ***,1407061246,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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.",1392925788,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,Gah.,1380067199,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,This has started happening again. See [[OpenOffice.Org]] and [[Bristol]] for examples.,1379790227,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,"Ok thanks for the quick reply, now reported as bug 52427",1375398248,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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.",1375397689,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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?,1375397290,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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).,1375383745,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+References inside templates don't appear in the reference list in VisualEditor,"Sorry, that second possibly related bug should be bug 50749",1373722788,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-c2zo7myzzju4zjk7el5z,task_subcomment,NA
+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",1373722440,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-deqihdmtktthecojw62o,task_description,resolved
+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.,1377829266,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-deqihdmtktthecojw62o,task_subcomment,NA
+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
+
+",1373683500,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_description,declined
+VisualEditor: Samsung browser fails the blacklist,See {T367735},1718626061,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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!",1437858058,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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.",1437831971,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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!)",1437781263,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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!)",1437781197,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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.,1373923134,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+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.",1373916976,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+VisualEditor: Samsung browser fails the blacklist,Mobile Safari isnt just iOS.  It is the *default* web browser on many Android phones.,1373764759,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cc7gmrf5ioc7lfjjvyzo,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"For VisualEditor, we are continuously-bitten by <references /> 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 <references /> tag.
+
+Points of agreement include:
+* The main requirements are for <references /> 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 <references /> 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",1373662620,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_description,resolved
+Support editing <references /> 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]]
+",1505840824,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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]]
+",1505835365,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references> 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 <references/> 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.",1499785680,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,">For VisualEditor, we are continuously-bitten by <references /> 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 <references /> tag.
+
+>Reference incidences (<ref>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 <references /> 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.",1446974679,PHID-USER-o7sy7j32bv4qerbqa3x5,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.,1435699557,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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).,1425310977,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,@thiemowmde mentions T33597,1416834442,PHID-USER-tqvzwasywo4a7bnuwuz4,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.,1416910461,PHID-USER-u6ycqhfpa3k4yvlpxjt2,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.,1416910421,PHID-USER-u6ycqhfpa3k4yvlpxjt2,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.,1412760097,PHID-USER-u6ycqhfpa3k4yvlpxjt2,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 `<references>` 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.",1417405037,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 `<references>` 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.",1417405028,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references> 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.",1412722649,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"See also:
+Bug 31597 - generate class for references list according to the number of refs",1411551743,PHID-USER-zqde3skdzpqiwny4dxt4,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+Reason:
+ok done
+
+https://gerrit.wikimedia.org/r/123105",1409791989,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,I picked up the Cite & VE parts of this again.,1409791787,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+Reason:
+Restoring so I can do a rebase to get the VE patch working
+
+https://gerrit.wikimedia.org/r/123105",1409791573,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+https://gerrit.wikimedia.org/r/123093",1409782437,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"Change 120962 restored by Alex Monk:
+Support setting column-width and list-style in <references /> tag
+
+Reason:
+Going to use classes.
+
+https://gerrit.wikimedia.org/r/120962",1409782408,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,Bug 22265 - Allow references to be listed with letters,1405984158,PHID-USER-zqde3skdzpqiwny4dxt4,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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"".",1405787640,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+Reason:
+Abandoning all related patch sets
+
+https://gerrit.wikimedia.org/r/123093",1405780950,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"Change 120962 abandoned by Alex Monk:
+Support setting column-width and list-style in <references /> tag
+
+https://gerrit.wikimedia.org/r/120962",1405780903,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+https://gerrit.wikimedia.org/r/123105",1405780885,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,See https://gerrit.wikimedia.org/r/#/c/120962/ for more discussion on this.,1401486377,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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…",1401482644,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.",1396389434,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+https://gerrit.wikimedia.org/r/123105",1396388659,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references>
+
+https://gerrit.wikimedia.org/r/123093",1396387228,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"What? We don't do LATER, and haven't for over a year.",1395858396,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"IMO this should be a WONTFIX or LATER, and instead bug 6019 should be fixed.",1395800703,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references /> tag
+
+https://gerrit.wikimedia.org/r/120962",1395789394,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 <references /> 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 <references /> 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 <references /> OL – the ""references"" class can be over-ridden locally by wikis if they want to change it further.
+
+
+Is this what others think?",1394727173,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,Can someone sum up exactly what has been agreed to do here?,1394128243,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"(In reply to comment #8)
+> The references tag should support html attributes, than you can write
+> <references class=""***"" /> 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.",1383136097,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.",1383132465,PHID-USER-tyjmn7xcw6s2b6rqagj7,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.",1380273005,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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).
+
+</brain-dump>",1380272763,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,What about the {{reflist}} variants on en.wiki such as {{notelist}}?,1377709374,PHID-USER-zqde3skdzpqiwny4dxt4,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"The plwp infobox <references/> is here:
+https://pl.wikipedia.org/wiki/Szablon:Infobox_uwagi_dodaj",1373764541,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 (<references />s) rather than having them
+> need to invent and use the template.
+> 
+> Reference incidences (<ref>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 <references /> so people won't (often?) have to embed <references /> in templates.  However, I think db's point is that there are other reasons (besides {{reflist}}) that <references /> 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.",1373762484,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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 (<h2>, <h3>, ...):
+https://pt.wikipedia.org/wiki/Template:Referências",1373746711,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"The references tag should support html attributes, than you can write <references class=""***"" /> 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.",1373744313,PHID-USER-a6jwrurphpx6yl4coupk,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"(In reply to comment #5)
+> You will become also problems with <ref> 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 (<references />s) rather than having them need to invent and use the template.
+
+Reference incidences (<ref>s) inside templates are an entirely distinct problem for VisualEditor to worry about, and this isn't about that. :-)",1373724517,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"(In reply to comment #5)
+> You will become also problems with <ref> 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 <ref>s *and* <references group=.../>, for example pl.wp infoboxes for football players and some other sportsmen; an example can be seen on [[pl:Carles Puyol]].",1373709172,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> tags to set multi-column display on/off,"You will become also problems with <ref> 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.",1373700015,PHID-USER-a6jwrurphpx6yl4coupk,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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.",1373665020,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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",1373664227,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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"".",1373663834,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+Support editing <references /> 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).",1373663426,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-p6rccw5cwglxrbbkmq2b,task_subcomment,NA
+VisualEditor: Remove obsolete retry token logic in mw.Target,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373654940,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-glljlygxsse6ts5nyo5g,task_description,resolved
+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",1376556010,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-glljlygxsse6ts5nyo5g,task_subcomment,NA
+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",1375231529,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-glljlygxsse6ts5nyo5g,task_subcomment,NA
+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)",1373655053,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-glljlygxsse6ts5nyo5g,task_subcomment,NA
+VisualEditor: Remove obsolete retry token logic in mw.Target,"onLoad no longer requires or even considers a token, so this is now obsolete.",1373655001,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-glljlygxsse6ts5nyo5g,task_subcomment,NA
+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",1373650320,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_description,resolved
+Install Notifications (Echo) on the Polish Wikipedia,"I'm pretty sure this can be closed now :) Thanks, Fabrice!",1377773546,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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)",1376107997,PHID-USER-dbudsaorcqut7sg3vvbi,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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.",1376107269,PHID-USER-dbudsaorcqut7sg3vvbi,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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.",1375576048,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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!",1375375348,PHID-USER-dbudsaorcqut7sg3vvbi,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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.",1375362558,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+Install Notifications (Echo) on the Polish Wikipedia,And thanks for responding :) I'll forward this information to the community.,1374710826,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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.",1374710558,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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!",1374710265,PHID-USER-dbudsaorcqut7sg3vvbi,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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""?",1374361726,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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!",1373918592,PHID-USER-dbudsaorcqut7sg3vvbi,False,PHID-TASK-qxyoycuq2mw55c2oy7mm,task_subcomment,NA
+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",1373636880,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-znebtf73mavsnt4zkjtb,task_description,declined
+VisualEditor: Add the capacity for help pages in dialogs,"Instead of help /pages/ we've decided to go with help /popups/, per bug 51798.",1403824508,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-znebtf73mavsnt4zkjtb,task_subcomment,NA
+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",1373603700,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_description,resolved
+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.",1376526837,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1375981140,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1375978000,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.,1375306275,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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/,1374985971,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.,1374985901,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1374928594,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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. ***,1374701823,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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. ***,1374677927,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1374529506,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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. ***,1374329698,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+Implement way to round-trip tables with fosterable content that migrates out of the table,This looks very similar to bug 50754.,1374306109,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+Implement way to round-trip tables with fosterable content that migrates out of the table,"From IRC:
+[14:44] <gwicke> 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] <gwicke> yeah, I wonder what he is up to
+[14:45] <subbu> in that example, what do we do with the information at all .. itis not helpful since the output still looks corrupt.
+[14:45] <gwicke> 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] <gwicke> we could strip the fostered content from the DOM
+[14:46] <subbu> is it the right thing to do in general?
+[14:46] <gwicke> and rig selser so that it restores it unless the content is touched 
+[14:47] <gwicke> or we can keep it in the DOM, but mark it so that selser does not serialize it
+[14:47] <gwicke> ie, a zero-length dsr
+[14:48] <subbu> yes, the rig-selser bit is missing right now.
+[14:48] <gwicke> subbu: detecting foster-parented content and then excluding it from dsr calculations might already be pretty effective
+[14:49] <gwicke> I guess the gaps in dsr would be spanned by the dsr algorithm
+[14:49] <subbu> yes, that should work.
+[14:49] <gwicke> (the holes where content disappeared)
+[14:50] <subbu> 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] <gwicke> subbu: I'd vote for data-parsoid
+[14:50] <subbu> data-parsoid is fine for internal use.
+[14:50] <gwicke> if the user edits the fostered content, we serialize it
+[14:50] <gwicke> i.e., do the dirty diff then
+[14:51] <subbu> 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] <gwicke> when something adjacent to the former location is edited, we dirty-diff it there
+[14:51] <gwicke> subbu: IMO we should abstract such issues
+[14:52] <gwicke> bot authors would not want to deal with it either
+[14:52] <gwicke> and the DOM should reflect the rendered semantics 
+[14:53] <subbu> dom should reflect rendered semantics for sure.",1374271613,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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<ref name=""futon"" />
+ |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)
+
+... <td id=""pc{{{ProdCode}}}"">{{{ProdCode}}}</td> ...
+
+See what that will do with the parameter passed in from the page.  Here is the expanded source that Parsoid sees:
+
+... <td id=""pc101<ref name=""futon"" />"">101<ref name=""futon"" /></td> ...
+
+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.",1374266416,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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).",1374190969,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.,1374185200,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.",1374184823,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.",1374101827,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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,1374089129,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1374088970,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.",1373606553,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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.",1373604215,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fu4mfwq7s4u3wu5u6yny,task_subcomment,NA
+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",1373579640,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_description,open
+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",1650404810,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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  `<div style=""top: left: …""></div>` to  `<svg><rect x= y= …></svg>` 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 `<svg>` tag covering the whole page, but made unclickable with `pointer-events: none`, with `<rect>` or something for individual highlights.
+
+I think we should stick to smaller `<svg>` tags covering just the focusable node (like the current `<div>` 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 `<svg>` 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.)",1526820747,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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]]",1526763872,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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",1462887892,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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.",1416846887,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+Draw VisualEditor's non-CE block highlights using SVG polygons,This is not high priority,1416846552,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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.,1408985768,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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/",1373580320,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-jdnwbc5e2g3tlpeis2hc,task_subcomment,NA
+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",1373556900,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-f6islnvgxyd3d63sxooo,task_description,resolved
+Re-enable user preference to disable VisualEditor,"
+
+*** This bug has been marked as a duplicate of bug 50929 ***",1373557556,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-f6islnvgxyd3d63sxooo,task_subcomment,NA
+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.",1373557227,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-f6islnvgxyd3d63sxooo,task_subcomment,NA
+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",1373507520,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-l5pjiw32hngnewgrmmmy,task_description,declined
+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.",1373610519,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-l5pjiw32hngnewgrmmmy,task_subcomment,NA
+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),1373558667,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-l5pjiw32hngnewgrmmmy,task_subcomment,NA
+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 <yourApiURL>
+
+We should probably print this information when the config request fails. Repurposing this bug for that.",1373556483,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-l5pjiw32hngnewgrmmmy,task_subcomment,NA
+VisualEditor: Newline migration issue,"As discovered in bug 50120, we need to find out what this is and fix it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373503560,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ki7bzkbyld2qdm75nyap,task_description,open
+VisualEditor: Newline migration issue,"@Jdforrester-WMF, can we close this? T52120 has been resolved.",1440107033,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-ki7bzkbyld2qdm75nyap,task_subcomment,NA
+VisualEditor: Newline migration issue,"@Jdforrester-WMF, can we close this? T52120 has been resolved.",1437781492,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-ki7bzkbyld2qdm75nyap,task_subcomment,NA
+"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",1373500740,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-nphxjkvvi4eszdxix7bq,task_description,open
+"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 <references> tag making {{reflist}} redundant?
+
+https://phabricator.wikimedia.org/maniphest/query/7.xI5WLmYTc1/#R pffers some tasks about //specific// (not: //all//) functionality...",1436532828,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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 <references> tag making {{reflist}} redundant?,1436461261,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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.",1405353588,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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. ***,1405107160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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.,1374270748,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+"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).,1373774352,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-nphxjkvvi4eszdxix7bq,task_subcomment,NA
+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",1373497500,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_description,resolved
+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",1645468531,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+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",1644991783,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+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.",1410824403,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+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).",1410216270,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+VisualEditor: Nicer removal of Cite.php's class=error,Hello?,1410125027,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+VisualEditor: Nicer removal of Cite.php's class=error,So what is this about? There's a lot of missing context here.,1406238141,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ny6m4ujfqwfjm6dzcxsg,task_subcomment,NA
+"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",1373485620,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-7brx7poui3lgaqmgzlvg,task_description,resolved
+"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.",1393632765,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7brx7poui3lgaqmgzlvg,task_subcomment,NA
+"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.",1373855846,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7brx7poui3lgaqmgzlvg,task_subcomment,NA
+"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",1373473020,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-xxykpaxkkgrcn363ntny,task_description,declined
+"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor",I have.,1400626382,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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?",1400188965,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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.",1400188662,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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?",1400187131,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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",1397752290,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"VisualEditor: Offer ""cancel"" option in save dialog to escape VisualEditor",The user is asking to escape VE entirely.,1373474404,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+"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?",1373474231,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xxykpaxkkgrcn363ntny,task_subcomment,NA
+[[./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",1373422620,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-l4k7rc3z5agm24u46fhj,task_description,resolved
+[[./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",1397109465,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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",1397109230,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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",1396645916,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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.",1395952117,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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}}]]",1395951625,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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",1394483874,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+[[./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.",1377447763,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-l4k7rc3z5agm24u46fhj,task_subcomment,NA
+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",1373398440,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_description,resolved
+VisualEditor: Link editor requires ENTER for input,*** Bug 51177 has been marked as a duplicate of this bug. ***,1377834865,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+VisualEditor: Link editor requires ENTER for input,This is now merged and will be deployed later.,1375304913,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+VisualEditor: Link editor requires ENTER for input,"Change 76839 merged by jenkins-bot:
+Link inspector bug fixes
+
+https://gerrit.wikimedia.org/r/76839",1375304088,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+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",1375222014,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+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.",1374530988,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+VisualEditor: Link editor requires ENTER for input,Is this the same thing as bug 48789?,1374519470,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+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]",1373905446,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+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.",1373757918,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-oh3fg6fot6uziw3ctbqu,task_subcomment,NA
+"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",1373394900,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-4phtoxaof6zm4vyraue4,task_description,open
+"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.,1402590995,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4phtoxaof6zm4vyraue4,task_subcomment,NA
+"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"".",1373428513,PHID-USER-fuj45iylbizjg3yhehjt,False,PHID-TASK-4phtoxaof6zm4vyraue4,task_subcomment,NA
+"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",1373390040,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_description,resolved
+"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]]",1430268574,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]
+",1430236097,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"TemplateData: Provide property ""example"" for template parameters",Checked in betalabs - 'Example (en)' was added to Template documentation editor.,1429042468,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]",1428684541,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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.",1426695980,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]",1425936869,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]
+",1425512054,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"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]]
+",1425501224,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+"TemplateData: Provide property ""example"" for template parameters",Any progress?,1393353167,PHID-USER-6majuboi566q3ozbh27r,False,PHID-TASK-dhlp7wsucyat5r5hizgn,task_subcomment,NA
+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",1373356200,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-hqedrd262jmefrbeu2zs,task_description,resolved
+VisualEditor: OpenSearch results aren't perfect for checking for page existence,"FIXED by dint of bug 70958 being fixed. Thanks, Timo!",1412977342,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for checking for page existence,*** Bug 54361 has been marked as a duplicate of this bug. ***,1410985568,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+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.",1406658829,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+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.",1406658645,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for checking for page existence,*** Bug 65927 has been marked as a duplicate of this bug. ***,1402016305,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for checking for page existence,*** Bug 52596 has been marked as a duplicate of this bug. ***,1377808859,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+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,1377802895,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hqedrd262jmefrbeu2zs,task_subcomment,NA
+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",1373355240,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-jbywhdnkgf572tjejemv,task_description,resolved
+VisualEditor: Make defaultsort input field wider,Thanks!,1395083036,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+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",1395082709,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+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",1395082320,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+VisualEditor: Make defaultsort input field wider,"Created attachment 14834
+Other dialogs affected by change
+
+**Attached**: {F11659}",1395009220,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+VisualEditor: Make defaultsort input field wider,"Created attachment 14833
+Screenshot of 100% width in default sort field
+
+**Attached**: {F11658}",1395008155,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+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}",1395008084,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-jbywhdnkgf572tjejemv,task_subcomment,NA
+"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",1373336940,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-4thzrxadngq5mhfphtu2,task_description,resolved
+"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,1395350521,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4thzrxadngq5mhfphtu2,task_subcomment,NA
+"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,1394844008,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4thzrxadngq5mhfphtu2,task_subcomment,NA
+"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",1394666490,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4thzrxadngq5mhfphtu2,task_subcomment,NA
+"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",1394412858,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4thzrxadngq5mhfphtu2,task_subcomment,NA
+"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",1373335140,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tqk4thl22c326oiwdmgc,task_description,open
+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",1373333700,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_description,resolved
+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",1395274513,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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",1387582091,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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",1387581872,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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",1383139276,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,WIP: https://gerrit.wikimedia.org/r/#/c/84461/,1379374358,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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"".",1378832292,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog,*** Bug 51176 has been marked as a duplicate of this bug. ***,1374854828,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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.",1374854811,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-etzwcnqtxa6glyvdpt5e,task_subcomment,NA
+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",1373332680,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_description,resolved
+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.,1429467871,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_subcomment,NA
+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.",1377896960,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_subcomment,NA
+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.",1374076751,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_subcomment,NA
+VisualEditor: Backspace from (or deleteing down) into a DL breaks badly,Also note that undo doesn't seem to work on this deletion event.,1373354435,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-zy6o6x7vkuly2bz7grnv,task_subcomment,NA
+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 <sup> (like [10]) and as such isn'y styled correctly (text is too big).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11600}",1373316780,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vqebaloi6mz6p43fpars,task_description,resolved
+VisualEditor: Display references rendered by {{#tag:ref}} in superscript,Fixed and will go out later today.,1373993621,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+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",1373992966,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+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",1373991605,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"(In reply to comment #2)
+> Parsoid incorrectly renders references as <span>s. The ones directly in the
+> main documented are rendered as <sup>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 <span class=""reference""> render as a superscript, or munge it in some other way. Though ideally I'd like us to convince Parsoid to render references as <sup>s the way the PHP parser does.",1373850925,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+VisualEditor: Display references rendered by {{#tag:ref}} in superscript,"Parsoid incorrectly renders references as <span>s. The ones directly in the main documented are rendered as <sup>s by VE, but we don't control the ones in templates and other generated content (and #tag is a ParserFunction).",1373850785,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+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",1373850409,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-vqebaloi6mz6p43fpars,task_subcomment,NA
+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",1373310540,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-cc3yxgxiksoojspiwoxm,task_description,resolved
+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).",1437782973,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-cc3yxgxiksoojspiwoxm,task_subcomment,NA
+VisualEditor: Provide some way of opening external links within templates,*** Bug 66549 has been marked as a duplicate of this bug. ***,1402688065,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cc3yxgxiksoojspiwoxm,task_subcomment,NA
+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, <references />).",1395856047,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-cc3yxgxiksoojspiwoxm,task_subcomment,NA
+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",1373301660,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_description,resolved
+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",1400108562,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1400103345,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1400102698,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+VisualEditor: Clearer message when cancelling out of active edit,"Change 132113 merged by jenkins-bot:
+Add confirmation dialog
+
+https://gerrit.wikimedia.org/r/132113",1400087288,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1399588039,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1399587267,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1399497998,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1398793970,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1375976639,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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.",1374267990,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+VisualEditor: Clearer message when cancelling out of active edit,*** Bug 51655 has been marked as a duplicate of this bug. ***,1374267909,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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"".)",1374208197,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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?",1373519895,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vwwslgbmh4ftbegrc3zg,task_subcomment,NA
+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",1373299560,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_description,resolved
+VisualEditor: Handle transclusions within a table better,The table will still be broken after an edit as Parsoid doesn't run with context yet.,1404212487,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_subcomment,NA
+VisualEditor: Handle transclusions within a table better,Fixed by gerrit 140439.,1404172723,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_subcomment,NA
+VisualEditor: Handle transclusions within a table better,This might be related to VisualEditor bug 50607 and foster-parenting.,1377030328,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_subcomment,NA
+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.",1374457884,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-h7tfqm7vbzcm7dpmeabg,task_subcomment,NA
+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",1373294940,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-bmll3l66rbyvzumaunet,task_description,resolved
+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.,1552091050,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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.",1373340093,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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}",1373339872,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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)?",1373338512,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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}",1373338199,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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.",1373337830,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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.",1373335844,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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!",1373332126,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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",1373295030,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-bmll3l66rbyvzumaunet,task_subcomment,NA
+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",1373276400,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_description,resolved
+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)",1374837483,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374835048,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,So you will reopen this bug as soon as VE gets stable? Promised?,1374833237,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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. :-)",1374832672,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374832506,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374831425,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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!",1374830485,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,Fixed in VisualEditor extension itself with https://gerrit.wikimedia.org/r/#/c/75541/,1374826648,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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",1374826585,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374795200,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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?",1374790590,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374520048,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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",1374519857,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374516858,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374516605,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374512041,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.)",1374511815,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374511268,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1374510712,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,That would reopen bug 48666 Make VisualEditor a hidden preference.,1374499371,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,*** Bug 51389 has been marked as a duplicate of this bug. ***,1373926494,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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",1373712372,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373576253,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,"Great, thank you.
+
+I'm marking this bug with the ""easy"" keyword accordingly.",1373566995,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373561265,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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?",1373559939,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373559883,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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!",1373557859,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373557628,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,*** Bug 51179 has been marked as a duplicate of this bug. ***,1373557556,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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}",1373534882,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+User preference to disable VisualEditor,"This should be in the obvious place, in the editing tab of user preferences, not a gadget.",1373454425,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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.",1373357086,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+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",1373280320,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2lqrwar67hw6qvy4f5kh,task_subcomment,NA
+"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",1373273160,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_description,resolved
+"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.",1373328454,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_subcomment,NA
+"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",1373325416,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_subcomment,NA
+"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",1373303244,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_subcomment,NA
+"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?",1373301852,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4qpkfgh5ks6gaaj22qxs,task_subcomment,NA
+"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",1373241780,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-77heb24pfspzzrzifyb6,task_description,open
+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",1373235720,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-e3ikdtgrrubm3iohiewm,task_description,resolved
+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",1393088190,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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",1389062756,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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",1388994313,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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",1388991749,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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.",1388943484,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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.",1388941911,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+VisualEditor: CE CSS munging issue with specific (highly used) hewiki template,Was this fixed by the fix for bug 53436?,1388919466,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e3ikdtgrrubm3iohiewm,task_subcomment,NA
+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",1373231700,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-opmsqzsgromr47nfku4r,task_description,resolved
+VisualEditor: Label the edit summary box as such,"This was done, ages ago.",1383280539,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-opmsqzsgromr47nfku4r,task_subcomment,NA
+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",1373231160,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-delfcnij7a43xvmu5qyt,task_description,resolved
+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.,1377809024,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+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).",1376076347,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+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.",1376073277,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+VisualEditor: Link dialog lies about existence of page due to case insensitive matching,*** Bug 52251 has been marked as a duplicate of this bug. ***,1376073139,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+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",1376073087,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+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.",1373356246,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+VisualEditor: Link dialog lies about existence of page due to case insensitive matching,"Other examples: [[A]], [[B]], [[To]], [[Hi]]",1373299773,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-delfcnij7a43xvmu5qyt,task_subcomment,NA
+"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",1373228820,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_description,resolved
+"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",1392846136,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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",1392396699,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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",1392342481,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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",1391110776,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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).",1391108156,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.",1378762522,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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. ***,1378223819,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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. ***,1377814470,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.",1374687986,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.",1374630651,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.,1374417351,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.",1373480495,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+"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.,1373230813,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aq6bcd3lx5mpkayh6jkq,task_subcomment,NA
+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",1373224920,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_description,open
+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.",1703172513,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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.,1702660838,PHID-USER-tuy2dac6pfhknbtqmqgh,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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..)
+",1702544238,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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 <ref> 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 <ref> 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",1619846278,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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.",1572174420,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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"". ",1559320456,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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}",1559307018,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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. ",1543310095,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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.",1449854974,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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?",1402685083,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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.",1402684730,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-yhjup2iu6lr4ysgs743l,task_subcomment,NA
+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",1373224800,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-fgcx6r4cq4f3sp3crtxx,task_description,resolved
+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.,1373981883,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fgcx6r4cq4f3sp3crtxx,task_subcomment,NA
+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",1373934858,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fgcx6r4cq4f3sp3crtxx,task_subcomment,NA
+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",1373416527,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fgcx6r4cq4f3sp3crtxx,task_subcomment,NA
+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",1373199360,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_description,resolved
+VisualEditor: Long editnotices are truncated with no way to scroll,This was fixed last week.,1397067646,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+VisualEditor: Long editnotices are truncated with no way to scroll,*** Bug 62408 has been marked as a duplicate of this bug. ***,1397067550,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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).",1384895522,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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",1382972121,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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.",1377829536,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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.""",1377446787,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+VisualEditor: Long editnotices are truncated with no way to scroll,*** Bug 52602 has been marked as a duplicate of this bug. ***,1377446690,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-e5rh26mnuyokpvoo2c2t,task_subcomment,NA
+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",1373160600,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-hkpifvkdgtnwuojek3uj,task_description,resolved
+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",1392349574,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+VisualEditor: Remove the disablement of VisualEditor for redirect pages,*** Bug 60425 has been marked as a duplicate of this bug. ***,1390695336,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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",1384373833,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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",1384313403,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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.",1375531656,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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 :)",1375522019,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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.",1373160972,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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?",1373160777,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hkpifvkdgtnwuojek3uj,task_subcomment,NA
+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",1373160480,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_description,resolved
+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",1400888338,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_subcomment,NA
+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",1400742360,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_subcomment,NA
+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.",1373566655,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_subcomment,NA
+VisualEditor: Editor not triggered on system redirects,*** Bug 51178 has been marked as a duplicate of this bug. ***,1373566618,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wcnnt6ci2eb4mcaggjrl,task_subcomment,NA
+"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",1373152020,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_description,declined
+"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"".",1434589709,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+"VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist",re-opening since I think it works pretty well.,1434060016,PHID-USER-ogbcrxm45oo3n3xe5q25,True,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+"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.",1377033706,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+"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.",1373319033,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+"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.",1373308626,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-35rbgnr7z5e2nahfmsjs,task_subcomment,NA
+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",1373150220,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_description,resolved
+VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link,Done and will be deployed tomorrow.,1374634478,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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",1374620537,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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.",1374606424,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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. ***,1374605494,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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",1374187124,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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. ***,1373932279,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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.",1373185656,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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?",1373183092,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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. ***,1373155212,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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?",1373155090,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5kevizlj2r7opk2fmypx,task_subcomment,NA
+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 <h1> 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",1373144520,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_description,resolved
+mediawiki.notification: Notification area should remain visible when scrolled down,*** Bug 48689 has been marked as a duplicate of this bug. ***,1381254374,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374689170,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+mediawiki.notification: Notification area should remain visible when scrolled down,"@se4598, thanks for the report, I7444bf55 should fix this. Sorry!",1374689138,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374687551,PHID-USER-jcypqodpdpbcicgwgh7j,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374679819,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374679699,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374678751,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374678540,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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.",1374636514,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1374636426,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+mediawiki.notification: Notification area should remain visible when scrolled down,*** Bug 51785 has been marked as a duplicate of this bug. ***,1374449520,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1373984219,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1373982414,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+mediawiki.notification: Notification area should remain visible when scrolled down,*** Bug 51432 has been marked as a duplicate of this bug. ***,1373982177,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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 = $('<div>').appendTo($content)
+    $n = $('<div>').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 )",1373281154,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+mediawiki.notification: Notification area should remain visible when scrolled down,"Heh, I though they behave in this way. Seems like an obvious enhancement.",1373147615,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+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",1373147590,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ct4cgxz4gl6hs4fuvcpo,task_subcomment,NA
+"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",1373067480,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-jza5e4mrwocbbyclpgux,task_description,open
+"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.",1373067634,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-jza5e4mrwocbbyclpgux,task_subcomment,NA
+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",1373062140,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-qx22rnw4roeugdfib5hc,task_description,resolved
+VisualEditor: Clean up 'cache': 'false',Done in Roan's clean-up of API usage.,1393640938,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qx22rnw4roeugdfib5hc,task_subcomment,NA
+"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}",1373006760,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-x7y27baxwalxutuxi24u,task_description,resolved
+"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.",1642379774,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-x7y27baxwalxutuxi24u,task_subcomment,NA
+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",1373006100,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_description,resolved
+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]]",1431794211,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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]]
+",1431655294,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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 ",1429126077,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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.",1429123960,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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?",1429122908,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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.",1425420366,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,Marking as Resolved.,1421801167,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,"This task is open but has two ""verified-in-phaseX"" projects associated. Could someone clarify?",1421800777,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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.",1419299453,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,"[15:09] <gwicke> 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] <gwicke> while still matching CSS etc so that it renders as expected
+[15:09] <RoanKattouw> Right
+[15:09] <RoanKattouw> I guess I could hack tolerance for that into VE's type system
+[15:10] <RoanKattouw> I think it's kind of an abuse of a type but I see why you'd do it
+[15:10] <RoanKattouw> You want to have a single unified thing to easily identify error nodes
+[15:11] <gwicke> yeah; there is a chance that querySelectorAll also supports typeof
+[15:12] <gwicke> [typeof~=mw:Error]
+[15:12] <RoanKattouw> Exactl
+[15:12] <RoanKattouw> y
+[15:12] <gwicke> which is more efficient than [data-mw] and then decoding each & look for errors
+[15:14] <gwicke> RoanKattouw, I think you are already giving mw:Placeholder a high precedence
+[15:14] <gwicke> could mw:Error have a similarly high precedence?
+[15:15] <RoanKattouw> gwicke: No, mw:Placeholder is unrecognized
+[15:15] <RoanKattouw> Any unrecognized type matching /^mw:/ triggers immediate alienation
+[15:15] <RoanKattouw> For mw:Error we'd need the reverse
+[15:15] <gwicke> yeah, but aren't you handling typeof=""mw:Placeholder mw:Image"" already?
+[15:15] <RoanKattouw> 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] <gwicke> (by letting the placeholder win)
+[15:16] <RoanKattouw> No, the placeholder doesn't win
+[15:16] <gwicke> ah, I see
+[15:16] <RoanKattouw> The rules for ""special"" type prefixes (for ve-mw, that's only /^mw:/ ) are as follows:
+[15:16] <gwicke> that's a problem
+[15:16] <RoanKattouw> A class matches if:
+[15:16] <RoanKattouw> * It specifies some type that's present on the element
+[15:17] <RoanKattouw> * It specifies ALL mw: types that are present on the element
+[15:17] <RoanKattouw> (i.e. both of those have to be true)
+[15:17] <RoanKattouw> Additionally, we don't currently have a facility for saying ""I recognize either mw:Foo or mw:Foo+mw:Error""
+[15:17] <RoanKattouw> You can only do AND, not OR
+[15:17] <gwicke> RoanKattouw: I see, that makes mw:Error harder to handle for you
+[15:18] <RoanKattouw> I mean, I can do it
+[15:18] <RoanKattouw> By introducing the concept of ignored types or whatever I want to call it
+[15:18] <RoanKattouw> I could even make mw:Placeholder one
+[15:18] <RoanKattouw> Then placeholderized images could be handled
+[15:18] <RoanKattouw> Handlers for node types still have the option to trigger alienation by returning null
+[15:18] <gwicke> we already have mw:Image and mw:ExpandedAttrs
+[15:19] <gwicke> and all permutations of images of course
+[15:19] <RoanKattouw> 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] <RoanKattouw> Right, mw:ExpandedAttrs is another good candidate for an ignored typer
+[15:19] <RoanKattouw> It can apply to anything
+[15:19] <RoanKattouw> And sometimes we need to alienate and sometimes we don't
+[15:19] <RoanKattouw> Hmm, maybe the jargon should be ""universal type""
+[15:19] <gwicke> yup, so the general ability to match that kind of thing is needed in any case
+[15:20] <RoanKattouw> Yeah
+[15:20] <RoanKattouw> I will file a bug about this",1393456951,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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?",1393455910,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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?,1393439521,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,*** Bug 52186 has been marked as a duplicate of this bug. ***,1389632313,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,"So currently redlink images are returned as <meta typeof=""mw:Placeholder"">. 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.",1389631702,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,*** Bug 51968 has been marked as a duplicate of this bug. ***,1377623981,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+VisualEditor: We need a representation of red-linked images,"Yes, this is a bit of a mess.",1373155845,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rdmlp3onaqmsq2rdmrnq,task_subcomment,NA
+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",1372987020,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-2liv3ois3nnjarqe73d5,task_description,resolved
+VisualEditor: Browser blacklist issues (tracking),Replaced by #VisualEditor-Initialisation.,1422424851,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2liv3ois3nnjarqe73d5,task_subcomment,NA
+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.",1415031694,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2liv3ois3nnjarqe73d5,task_subcomment,NA
+VisualEditor: Browser blacklist issues (tracking),"I'm going to add MSIE to the list, given that we really should get it working again.",1373041481,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2liv3ois3nnjarqe73d5,task_subcomment,NA
+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",1372986900,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-zzmgok2p56thwvxkpnrv,task_description,resolved
+VisualEditor: Firefox 11 and 12 also need to be blacklisted,This is now merged.,1373048811,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373048537,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373048483,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373048462,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373048390,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+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",1373041365,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zzmgok2p56thwvxkpnrv,task_subcomment,NA
+"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",1372980600,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-snnn2o47ucaywt5ufim7,task_description,resolved
+"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.",1410034029,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-snnn2o47ucaywt5ufim7,task_subcomment,NA
+"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.",1375182193,PHID-USER-7zhn2ep5wvjhxetsbb6n,True,PHID-TASK-snnn2o47ucaywt5ufim7,task_subcomment,NA
+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",1372978080,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-smutmksr4slgk2o54suc,task_description,resolved
+VisualEditor: Add Amazon Silk browser to blacklist,"Change 72108 merged by jenkins-bot:
+Blacklist Amazon Silk
+
+https://gerrit.wikimedia.org/r/72108",1391811948,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1391810830,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1391459065,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1391392671,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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...",1391382294,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1373041368,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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",1373039832,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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. :-)",1373036364,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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*",1373036277,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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.",1373033179,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-smutmksr4slgk2o54suc,task_subcomment,NA
+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 <math> 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",1372977300,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-ubeo6o33vz5bavixyf3q,task_description,resolved
+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. :-)",1412608037,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ubeo6o33vz5bavixyf3q,task_subcomment,NA
+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 ***",1412589972,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-ubeo6o33vz5bavixyf3q,task_subcomment,NA
+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",1372926900,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-joexgd3r5nmcwbofqrlr,task_description,resolved
+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.",1399419769,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-joexgd3r5nmcwbofqrlr,task_subcomment,NA
+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.",1399419638,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-joexgd3r5nmcwbofqrlr,task_subcomment,NA
+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)",1381626499,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-joexgd3r5nmcwbofqrlr,task_subcomment,NA
+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.",1373950590,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-joexgd3r5nmcwbofqrlr,task_subcomment,NA
+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",1372923480,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-ftkzim4nufm7ey6vnaq5,task_description,resolved
+VisualEditor: Generated blocks that create images directly aren't converted to use MW's skin,"I believe that this is now long-fixed, yes.",1660956979,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ftkzim4nufm7ey6vnaq5,task_subcomment,NA
+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?",1660948019,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ftkzim4nufm7ey6vnaq5,task_subcomment,NA
+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 <figure> rather than <div class=""thumb""> 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?",1373158925,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ftkzim4nufm7ey6vnaq5,task_subcomment,NA
+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)",1372894740,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2p76xxlh44jpmzqza6ge,task_description,open
+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.",1430333636,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2p76xxlh44jpmzqza6ge,task_subcomment,NA
+Separate ve.init and ve.platform,I think @Krinkle should rewrite it.,1430159784,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2p76xxlh44jpmzqza6ge,task_subcomment,NA
+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.",1430159393,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-2p76xxlh44jpmzqza6ge,task_subcomment,NA
+"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",1372883940,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-ibes2uplyibrsadgodld,task_description,resolved
+"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.",1385377902,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ibes2uplyibrsadgodld,task_subcomment,NA
+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",1372872180,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-3jrxscvn6apol6nbrw66,task_description,resolved
+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. :-),1372901827,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3jrxscvn6apol6nbrw66,task_subcomment,NA
+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.,1372880015,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3jrxscvn6apol6nbrw66,task_subcomment,NA
+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.",1372878719,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3jrxscvn6apol6nbrw66,task_subcomment,NA
+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",1372878612,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3jrxscvn6apol6nbrw66,task_subcomment,NA
+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",1372850220,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-72xdyaasptqyeuovlab3,task_description,open
+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}.",1603447176,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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.",1454246269,PHID-USER-bd4kgtavgiydswld34tj,False,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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.,1453877263,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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.",1453857840,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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...",1452890347,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+TemplateData: Parse wikicode and/or HTML in interface text,*** Bug 51311 has been marked as a duplicate of this bug. ***,1375191068,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+TemplateData: Parse wikicode and/or HTML in interface text,Please don't mark older bugs as duplicates of newer ones.,1375191065,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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 ***",1375187353,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+TemplateData: Parse wikicode and/or HTML in interface text,Is this the same as Bug 51311?,1375183810,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-72xdyaasptqyeuovlab3,task_subcomment,NA
+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",1372836600,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-itj4sdz77n2m7ganhvyr,task_description,resolved
+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.",1380437291,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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.,1380428239,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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. ***,1377831826,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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. ***,1375772188,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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).",1373581739,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+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.",1373581336,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-itj4sdz77n2m7ganhvyr,task_subcomment,NA
+"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",1372819920,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-ce2w6vrcycpoidffw23e,task_description,resolved
+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}",1372815240,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_description,resolved
+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.",1443085392,PHID-USER-mndznmqvm6ihjfmb6xap,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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?",1443035363,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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]].",1440832509,PHID-USER-mndznmqvm6ihjfmb6xap,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418395634,PHID-USER-mndznmqvm6ihjfmb6xap,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418395428,PHID-USER-mndznmqvm6ihjfmb6xap,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418391485,PHID-USER-ipgdr6xrndwpztdrubk4,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418391287,PHID-USER-ipgdr6xrndwpztdrubk4,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418195999,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1418195570,PHID-USER-mndznmqvm6ihjfmb6xap,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1410701090,PHID-USER-mndznmqvm6ihjfmb6xap,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1381353945,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1381297658,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!).",1381268160,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1380390102,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1380388534,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1380074042,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1380073592,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1378958879,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1378943135,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1377510579,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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! :)",1377508996,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1377501235,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1377207897,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.,1377206906,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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?",1377206495,PHID-USER-ipgdr6xrndwpztdrubk4,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1377206285,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1377205809,PHID-USER-ipgdr6xrndwpztdrubk4,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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!",1377202366,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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",1377164934,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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",1377027661,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1376936141,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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)",1376553611,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1376085848,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.,1376070283,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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).,1376067911,PHID-USER-mndznmqvm6ihjfmb6xap,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1376063216,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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 .",1374283399,PHID-USER-ipgdr6xrndwpztdrubk4,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1373767362,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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",1373675877,PHID-USER-dgjw4xb5i5zdwsiwvli5,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1373024925,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1373005232,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1372981869,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.",1372975898,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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).,1372970105,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+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.,1372965335,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME,It also comes to Chrome on Win7.,1372823539,PHID-USER-mndznmqvm6ihjfmb6xap,False,PHID-TASK-v3iakko3iymlxqo43aix,task_subcomment,NA
+"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",1372801620,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-du5yifaebt3zb2zhinvr,task_description,resolved
+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 </re>.  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",1372799760,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-5ftakv5wuzkf73akgiop,task_description,resolved
+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.,1392747780,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5ftakv5wuzkf73akgiop,task_subcomment,NA
+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.",1372814647,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5ftakv5wuzkf73akgiop,task_subcomment,NA
+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.",1372814416,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5ftakv5wuzkf73akgiop,task_subcomment,NA
+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.",1372800411,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-5ftakv5wuzkf73akgiop,task_subcomment,NA
+"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",1372797900,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_description,resolved
+"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output",Fixed by gerrit 140439.,1404172672,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"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. ***,1385374740,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"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.",1384938909,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"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.",1378399018,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"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&section=1 ?,1378374796,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+"VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output","This is because the HTML looks like <td typeof=""mw:Transclusion"" about=""#mwt139"">...</td><td about=""#mwt139"">...</td> and so the group of table cells is considered a template, and so the CE rendering is wrapped in a <div>. 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.",1372872684,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-d3wyk4xxdf6fguq3hvoj,task_subcomment,NA
+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",1372780080,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-65s4zvg7e6km2enogisy,task_description,resolved
+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.",1377030097,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+Templates that create multiple table cells don't work,This seems to be related to bug 44498.,1375195683,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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",1373659290,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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?",1373236010,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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],1372934113,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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.",1372797568,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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.",1372797193,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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"",
+  }",1372794694,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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.",1372791643,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+Templates that create multiple table cells don't work,and Parsoid. ;),1372788419,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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 .",1372788394,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+Templates that create multiple table cells don't work,My apologies for assuming that these two issues were related. Re-titling.,1372782463,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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)""?",1372782364,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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).",1372782107,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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 ***",1372781089,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-65s4zvg7e6km2enogisy,task_subcomment,NA
+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",1372767420,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-spssyaufehg6a576inro,task_description,resolved
+VisualEditor: Reconsider CSS content munging,"Indeed we did, this was done by the invaluable Ed in ee5b69772963c5d3f17b15742023cf33fc5dd48a.",1429615698,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-spssyaufehg6a576inro,task_subcomment,NA
+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?",1429478089,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-spssyaufehg6a576inro,task_subcomment,NA
+VisualEditor: Reconsider CSS content munging,"CSS content munging in general is a real pain, and we should find a way around it.",1385376106,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-spssyaufehg6a576inro,task_subcomment,NA
+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",1372734720,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-kazpxbs6hxscszn2mj4j,task_description,resolved
+VisualEditor: round-trip adjacent and nested annotations,This has been fixed for some time in the DM. Marking as such.,1380845963,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kazpxbs6hxscszn2mj4j,task_subcomment,NA
+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",1372742791,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-kazpxbs6hxscszn2mj4j,task_subcomment,NA
+./ 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",1372724400,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-xduyhafmy6kenmdf7cuh,task_description,resolved
+./ still appearing in links.,"
+
+*** This bug has been marked as a duplicate of bug 50720 ***",1373020641,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-xduyhafmy6kenmdf7cuh,task_subcomment,NA
+./ 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)",1372936732,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-xduyhafmy6kenmdf7cuh,task_subcomment,NA
+./ still appearing in links.,The visualeditor-needcheck tag also suggests that there was an issue in VE round-tripping. Reassigning to VE for investigation.,1372727544,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-xduyhafmy6kenmdf7cuh,task_subcomment,NA
+./ 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?",1372726643,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-xduyhafmy6kenmdf7cuh,task_subcomment,NA
+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",1372715400,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-focb5kxme3jxk4n6xklr,task_description,open
+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",1372706340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eqiuslxuu3t7bxl7vmwb,task_description,open
+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. :-)",1387398780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eqiuslxuu3t7bxl7vmwb,task_subcomment,NA
+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",1374867310,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-eqiuslxuu3t7bxl7vmwb,task_subcomment,NA
+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",1374549781,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-eqiuslxuu3t7bxl7vmwb,task_subcomment,NA
+VisualEditor: Close icon shown at 2x size and so truncated,"Screenshot
+
+See screenshot - monobook, windows 7, firefox 22.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11469}",1372699920,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-potyqd62zizy6tkvf2ak,task_description,declined
+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.",1377830355,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-potyqd62zizy6tkvf2ak,task_subcomment,NA
+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}",1372698960,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_description,invalid
+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.",1578935420,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.),1578869465,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.",1372712317,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.,1372711488,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.",1372700082,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.",1372699315,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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.",1372699118,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ag2p4jtrgjagpo2qegcu,task_subcomment,NA
+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//",1372670160,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-rou7bduh6enhafdxh2lv,task_description,resolved
+VisualEditor: Link input widget is not oriented for RTL,The current layout is good. There's a mistake in my image. Marking as FIXED.,1374495347,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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)' >",1374445202,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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",1373483413,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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",1372981428,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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.",1372741169,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+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}",1372670380,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-rou7bduh6enhafdxh2lv,task_subcomment,NA
+"VisualEditor: <u><u> 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",1372631880,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-7n67l5aimznnhmya4iwf,task_description,open
+"VisualEditor: <u><u> 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?",1416189671,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-7n67l5aimznnhmya4iwf,task_subcomment,NA
+"VisualEditor: <u><u> 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.",1372685856,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-7n67l5aimznnhmya4iwf,task_subcomment,NA
+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",1372620960,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_description,resolved
+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",1394672072,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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",1394667684,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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 <small>Parsoid returned 504</small> or
+> <small>Parsoid not available</small> 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.",1394667530,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504),We'll help. :-),1391913718,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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),1391879277,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373502193,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373482219,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373481412,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373481211,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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 <small>Parsoid returned 504</small> or <small>Parsoid not available</small> after the general call-to-action?",1373335525,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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).,1373334999,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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.",1373133953,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+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),1372684698,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-ttp4fmqdy7axj4tku4zm,task_subcomment,NA
+"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}",1372620660,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_description,open
+"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.",1721046082,PHID-USER-k5wpqok2x66oei3wguaf,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.,1526397283,PHID-USER-qdbrv6swdxlgemqwwbuw,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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  `<ref name=""Author Date"">Author Date, page 123.</ref>` (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=data<ref>Source</ref>}}`:  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 <references /> 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.
+",1478851254,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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? ",1446421308,PHID-USER-ddcrbue3iyorn42wkwbo,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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? ",1446421206,PHID-USER-ddcrbue3iyorn42wkwbo,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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? ",1446420835,PHID-USER-ddcrbue3iyorn42wkwbo,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.,1440781886,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ",1440781461,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1430945384,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1430229351,PHID-USER-cbmsqiuerftutmt523wv,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1421203877,PHID-USER-ufjbf3qatjamiwoal5fp,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.""
+",1419470550,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1407719768,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1402332002,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1401416868,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1385381556,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1383003781,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1377843814,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1377823296,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. :-)",1377823070,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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 <references> rendering and editing.",1377822959,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1377822665,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.
+
+<ref>{{foo}}</ref> 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.",1377821853,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1377819846,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1377819444,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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 <ref> because of localization issues.,1374930557,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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. ***,1374880234,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372714617,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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",1372714324,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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",1372713484,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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",1372712260,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372700420,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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 :/.,1372699735,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372699677,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372696659,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.,1372696532,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372695038,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372633730,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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 :/,1372626164,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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""?",1372622488,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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.",1372622399,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","How it actually looks
+
+**Attached**: {F11401}",1372621957,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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//",1372620753,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.","How it should look
+
+**Attached**: {F11400}",1372620731,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-n26jfot72gcfg6mgq6wx,task_subcomment,NA
+"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",1372612320,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-xnsrcsuce62r2yfruwso,task_description,declined
+"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.,1378550137,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xnsrcsuce62r2yfruwso,task_subcomment,NA
+"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.",1374461315,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-xnsrcsuce62r2yfruwso,task_subcomment,NA
+"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).",1372612642,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-xnsrcsuce62r2yfruwso,task_subcomment,NA
+"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).",1372612568,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-xnsrcsuce62r2yfruwso,task_subcomment,NA
+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",1372555020,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-op3amukih656hqtejh6j,task_description,resolved
+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.,1383280412,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-op3amukih656hqtejh6j,task_subcomment,NA
+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.",1372558387,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-op3amukih656hqtejh6j,task_subcomment,NA
+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",1372554420,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-nopdefkge3ym2od7ufrd,task_description,resolved
+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.",1414004857,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nopdefkge3ym2od7ufrd,task_subcomment,NA
+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.",1373397301,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nopdefkge3ym2od7ufrd,task_subcomment,NA
+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 :
+<templatedata>
+{
+        ""description"": ""תבנית כלשהי."",
+        ""params"": {
+                ""שם"": {
+                        ""label"": ""שם"",
+                        ""type"": ""string/wiki-user-name"",
+                        ""required"": true,
+                        ""description"": ""שם של משתמש"",
+                        ""aliases"": [""1""]
+                }
+        },
+        ""sets"": [
+                {
+                        ""label"": ""Date"",
+                        ""params"": [""שנה"", ""חודש"", ""יום""]
+                }
+        ]
+}
+</templatedata>
+It is very hard to edit such syntax as above. (<templatedata> 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",1372540320,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-ttobixbmawcbongmnatf,task_description,resolved
+TemplateData: Creating TemplateData blocks should be direction neutral,"This is now effectively ""solved"" through general availability of the GUI to edit TemplateData.",1415310061,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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,1390051584,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1389930776,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1389887269,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+TemplateData: Creating TemplateData blocks should be direction neutral,How about marking it as a duplicate of bug 51734?,1389874215,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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?",1389807290,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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",1389753678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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",1379736870,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1375130859,PHID-USER-x7g37sf6tkkrewspco2q,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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?",1375122927,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1375122853,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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)",1375122782,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1375122472,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.,1374862129,PHID-USER-x7g37sf6tkkrewspco2q,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1374664108,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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).",1374619504,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.,1374619335,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+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.",1374353774,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+TemplateData: Creating TemplateData blocks should be direction neutral,"Timo, thoughts?",1372689806,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ttobixbmawcbongmnatf,task_subcomment,NA
+Wikitext list after implicit <td> 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",1372512240,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_description,resolved
+Wikitext list after implicit <td> not properly recognized,"Change 71744 merged by jenkins-bot:
+(Bug 50420) Recognize sol-content in implicit <td> after a <tr>
+
+https://gerrit.wikimedia.org/r/71744",1372829524,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> not properly recognized,"Change 71744 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 50420) Recognize sol-content in implicit <td> after a <tr>
+
+https://gerrit.wikimedia.org/r/71744",1372809900,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> not properly recognized,"Ok, renamed the bug to reflect the repurposing.",1372701474,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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",1372701241,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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.",1372651321,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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",1372650827,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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 <td> into an explicit <td> on serialization is a semantic error.
+
+Reduced test case:
+
+{|
+|-
+*a
+|}
+
+This cannot be fixed by selser since on editing the list item, the <td> 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.",1372565331,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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.",1372565021,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+Wikitext list after implicit <td> 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.",1372518582,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-itqhk6koq7bmakcn2wvo,task_subcomment,NA
+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}",1372468740,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-hoazjhp6o63s5rrky5qa,task_description,resolved
+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.",1377828038,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hoazjhp6o63s5rrky5qa,task_subcomment,NA
+VisualEditor: Reference list display being cut off in some pages,Could this be the same as bug 52371?,1377443863,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hoazjhp6o63s5rrky5qa,task_subcomment,NA
+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?",1374463011,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-hoazjhp6o63s5rrky5qa,task_subcomment,NA
+"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",1372462920,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-5wuwyofe6l5k2cmqjzad,task_description,declined
+"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.",1384202462,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5wuwyofe6l5k2cmqjzad,task_subcomment,NA
+"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.",1384202215,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5wuwyofe6l5k2cmqjzad,task_subcomment,NA
+"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",1372459800,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_description,resolved
+"VisualEditor: Behaviour of default ""Edit"" tab should not vary by namespace (action=edit vs. veaction=edit)",Now fixed and deployed.,1375423094,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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",1375414255,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.",1375284716,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.",1374262304,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.""",1374250805,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.""",1374250111,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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?",1372583668,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+"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.",1372471069,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-dwxii5uaohcgrtbsiwxl,task_subcomment,NA
+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",1372453440,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_description,duplicate
+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.",1396302080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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. ***,1385381652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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. ***,1377830806,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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. ***,1373164008,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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.",1372456631,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2r6x4q4bt3fqtg3es4ps,task_subcomment,NA
+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",1372429740,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_description,resolved
+VisualEditor: Do not add size for standard thumbnail images when inserting them,Done in gerrit 114420.,1393446774,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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.",1376561973,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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).,1373230571,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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"".",1373228305,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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.",1373228269,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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.",1373227900,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+VisualEditor: Do not add size for standard thumbnail images when inserting them,*** Bug 50766 has been marked as a duplicate of this bug. ***,1372966971,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-a6pw6i4cfeu2jzsduppd,task_subcomment,NA
+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. 
+",1372421640,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_description,stalled
+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. ",1708553338,PHID-USER-bommaimh4fl3xvg3ays6,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,A 7 year old task isn't UBN,1600590692,PHID-USER-2wquu5nwbdqcuzo5qiuf,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"> Quoted Text
+
+",1600590184,PHID-USER-mjtmg5ramyrkn7pbwxmq,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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",1595500486,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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",1595500463,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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",1595500429,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1554885642,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 <path_to_wiki>/maintenance/runJobs.php"".",1543413652,PHID-USER-gowqth4c6x65hhbw4z4u,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1542979491,PHID-USER-gowqth4c6x65hhbw4z4u,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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. ",1542198870,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1428122408,PHID-USER-3bnjvlq3zbpzzxdh4g4g,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,*** Bug 69647 has been marked as a duplicate of this bug. ***,1408689531,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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).",1376401137,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1376122026,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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).",1376033464,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1373338145,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372817050,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"Observation:
+
+- Edite <templatedata> 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.",1467215528,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"Observation:
+
+- Edite <templatedata> 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.",1372807585,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372802966,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372802403,PHID-USER-jdkjcyuluyy456zxyufo,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 (<templatedata>) 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",1372798204,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372774328,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"The extension page says:
+
+""The TemplateData extension works through having a <templatedata> 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).",1372748147,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372739834,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.,1372694998,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 <templatedata> 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.",1372559871,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 )",1372513536,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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?",1372457003,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.,1372456502,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372455968,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372455886,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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.",1372454024,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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?",1372451744,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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?",1372451659,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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?""",1372423465,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+Updated TemplateData from transcluded items take a long time to show up,"Belay that, {{tracked}} works.",1372423444,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ssksx6n4c7yondhu6cpg,task_subcomment,NA
+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 <https://test.wikipedia.org/wiki/Section_edit_links_bug2>. 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",1372420380,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-ogwe6d555gi7xn3bq357,task_description,open
+Templates that create part (but not all) of a table cell don't work,"Screenshot
+
+See screenshot; Windows 7, Firefox 21.0, on https://en.wikipedia.org/wiki/Rage_Against_the_Machine?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50589
+
+**Attached**: {F11166}",1372417680,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bcblwti2swge5nlt24om,task_description,resolved
+Templates that create part (but not all) of a table cell don't work,"This bug was raised five months earlier.
+
+*** This bug has been marked as a duplicate of bug 44498 ***",1374455443,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"Similar hack, but now on the table itself, instead of a table cell. See the Infobox of WikiProject Aircraft:
+
+https://en.wikipedia.org/wiki/BAC_One-Eleven",1373226373,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"FYI, we are considering a post-processing work-around in Parsoid that lets this class of templates render as expected, but might not let users edit those templated cells.
+
+Our longer-term goal is to move towards more self-contained templates. This won't happen over night, and we'll need the help of the editor community and bot authors.",1372783809,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"Bug 50589 is a different issue, so I reopened it and added detail there.",1372782144,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"**kwwilliams** wrote:
+
+50589 has been marked as a duplicate of this bug. I'm certain it's related, but I'm not certain it's a duplicate. *If* it is a duplicate, marking it as ""wontfix"" isn't an acceptable answer. 
+
+singlechart *does* return the leading | or !, depending on whether it has been ask to generate a row or a header row. It generates two row cells, separated by a |.",1372781691,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,*** Bug 50589 has been marked as a duplicate of this bug. ***,1372781089,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,*** Bug 50567 has been marked as a duplicate of this bug. ***,1372781074,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"I don't have precise figures right now, but know enough to be sure that a bot will be needed. This bot pass should also fix some other issues listed in http://www.mediawiki.org/wiki/Parsoid/limitations. Do you know a bot author who might be potentially interested in a task like this? We have it on our TODO list, but did not have the time to tackle it before the release.",1372733221,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+Templates that create part (but not all) of a table cell don't work,"(In reply to comment #4)
+> 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.",1372726569,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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",1372722914,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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",1372722454,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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.,1372720867,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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. ***,1372720818,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bcblwti2swge5nlt24om,task_subcomment,NA
+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}",1372416900,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-hadccnndpx3xlfcdq5x6,task_description,resolved
+VisualEditor: Hatnote templates not displaying properly,"Fair play; marking as duplicate.
+
+%%%*** This bug has been marked as a duplicate of bug 49784 ***%%%",1375118083,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-hadccnndpx3xlfcdq5x6,task_subcomment,NA
+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 <div>, 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.",1374878501,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hadccnndpx3xlfcdq5x6,task_subcomment,NA
+VisualEditor: Hatnote templates not displaying properly,"How the hatnote appears in subsequent VE loads.
+
+**Attached**: {F11148}",1372416940,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-hadccnndpx3xlfcdq5x6,task_subcomment,NA
+VisualEditor: Hatnote templates not displaying properly,"How the hatnote appears in ""read"" mode
+
+**Attached**: {F11146}",1372416924,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-hadccnndpx3xlfcdq5x6,task_subcomment,NA
+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",1372414260,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bygkpi2cds2ycjzl4xyf,task_description,invalid
+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.",1429468968,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-bygkpi2cds2ycjzl4xyf,task_subcomment,NA
+"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.
+
+",1372412940,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_description,open
+"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,1606394741,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1545161395,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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]]",1544646870,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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]]",1533659632,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1521578028,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1521578012,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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?",1456992621,PHID-USER-gc5hdyw5p4np7atqjynz,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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?
+",1456946077,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1456940930,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"VisualEditor: Add support for editing templates' parameters as DOM elements (""visually""), including supporting nested templates","I have literally no idea, it was in 2014.",1456932039,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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?,1456923888,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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}
+",1456797038,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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.",1408649657,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+"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 ***",1372427548,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-o63tibhphh5vfhjwesdx,task_subcomment,NA
+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",1372412100,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_description,invalid
+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).",1377906050,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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",1375794547,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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) >>",1375793484,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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. <nowiki>{{fixed}}</nowiki>, 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) >>",1375793232,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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.",1374492238,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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.",1374490962,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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"".",1373874288,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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).
+
+</brain dump>",1373369674,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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",1373069621,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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).",1373026126,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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?""",1372958401,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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)",1372947691,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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.",1372944786,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bdj7ew4y7qhxm7z7ixap,task_subcomment,NA
+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",1372411380,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vipia63usd432ltaseq6,task_description,declined
+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.",1423750227,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vipia63usd432ltaseq6,task_subcomment,NA
+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",1372389360,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_description,resolved
+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. :-)",1404356560,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+VisualEditor: Title is not updated on save if DISPLAYTITLE changed,So this appears to actually be working now.,1404250963,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1404249536,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1403537537,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1403134891,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1403133467,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+VisualEditor: Title is not updated on save if DISPLAYTITLE changed,Patch reverted; re-opening.,1403122919,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1403058210,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1402607917,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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.,1402607843,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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.",1402590458,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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",1374040482,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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).",1372778502,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+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}",1372537609,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-hhff6uyjp6fqhsgfm4vx,task_subcomment,NA
+"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}",1372367280,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_description,declined
+"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.,1438990382,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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.,1438983806,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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.",1438974040,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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.",1404214069,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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. ***,1402552906,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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.",1378727693,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+"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",1372797445,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-kmp5cza2rwu3qkvnz3gy,task_subcomment,NA
+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",1372344120,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-yelwyuxn7ull4zzjha5n,task_description,resolved
+VisualEditor: VE won't load on empty page containing only a magic word,"Fixed in the above commit, which we will push out today.",1373905170,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yelwyuxn7ull4zzjha5n,task_subcomment,NA
+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",1373905132,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yelwyuxn7ull4zzjha5n,task_subcomment,NA
+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",1373886485,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yelwyuxn7ull4zzjha5n,task_subcomment,NA
+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.,1372349806,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-yelwyuxn7ull4zzjha5n,task_subcomment,NA
+"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",1372335660,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_description,resolved
+"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]]",1427409486,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_subcomment,NA
+"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]]
+",1427406328,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_subcomment,NA
+"VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message",*** Bug 51812 has been marked as a duplicate of this bug. ***,1374702151,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_subcomment,NA
+"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}",1372490316,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-pquc72fdsgxf4k4jbbrl,task_subcomment,NA
+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",1372331940,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_description,resolved
+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. ***,1403995088,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_subcomment,NA
+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",1403746149,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_subcomment,NA
+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",1403731077,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_subcomment,NA
+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. :-)",1402549673,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xcrom5qozpxh2fsjz7v7,task_subcomment,NA
+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}",1372302300,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-s6tr75wkga6yoxhfytgb,task_description,resolved
+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.",1404168653,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-s6tr75wkga6yoxhfytgb,task_subcomment,NA
+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.,1393633426,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-s6tr75wkga6yoxhfytgb,task_subcomment,NA
+VisualEditor: enwiki template {{columns-list}} looks particularly-broken at high zoom/low width,I wonder if this is related to bug 50036?,1372325604,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-s6tr75wkga6yoxhfytgb,task_subcomment,NA
+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",1372302060,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-g7bv7yb2notx65burp7i,task_description,open
+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.",1374495419,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g7bv7yb2notx65burp7i,task_subcomment,NA
+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. ***,1374495310,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g7bv7yb2notx65burp7i,task_subcomment,NA
+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",1372267920,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_description,resolved
+VisualEditor: User personal links appear above VE dialogs,This was fixed in the deployment earlier this week.,1373077152,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_subcomment,NA
+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!,1372269171,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_subcomment,NA
+VisualEditor: User personal links appear above VE dialogs,"Created attachment 12650
+Screenshot showing issue (extracted from Word docx file)
+
+**Attached**: {F11829}",1372269063,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_subcomment,NA
+VisualEditor: User personal links appear above VE dialogs,"**rachelqa99** wrote:
+
+screenshot
+
+//attachment screenshotve.docx ignored as obsolete//",1372267984,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hnjrb6dsvhgt7tgjsyyd,task_subcomment,NA
+"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",1372262940,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_description,resolved
+"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",1391818168,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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",1391210012,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.,1387723690,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.",1375369955,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.",1374762733,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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. ***,1374488278,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.,1374011002,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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",1373931722,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.,1373921680,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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. ***,1373472822,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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.",1372332875,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+"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"".",1372323018,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-yv5u43sg36sflqbgt5oh,task_subcomment,NA
+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",1372254900,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-4pmiosnpdta6wvmtogmm,task_description,resolved
+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.,1373031803,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+Jenkins: migrate qunit jobs from master to gallium,"Change 72083 merged by Hashar:
+tie qunit jobs to slaves
+
+https://gerrit.wikimedia.org/r/72083",1373031569,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+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",1373030886,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+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",1373029884,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+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",1373029751,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4pmiosnpdta6wvmtogmm,task_subcomment,NA
+"VisualEditor: Non-primary edit tab <li> 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}",1372251780,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_description,resolved
+"VisualEditor: Non-primary edit tab <li> should have class=""collapsible""","Change 123503 merged by jenkins-bot:
+Give the edit tab <li> closest to the collapsed tabs menu class=collapsible
+
+https://gerrit.wikimedia.org/r/123503",1396639943,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_subcomment,NA
+"VisualEditor: Non-primary edit tab <li> should have class=""collapsible""","Change 123503 had a related patch set uploaded by Alex Monk:
+Give the edit tab <li> closest to the collapsed tabs menu class=collapsible
+
+https://gerrit.wikimedia.org/r/123503",1396487823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_subcomment,NA
+"VisualEditor: Non-primary edit tab <li> 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 <li> and it will magically work.",1372252025,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_subcomment,NA
+"VisualEditor: Non-primary edit tab <li> should have class=""collapsible""","Created attachment 12643
+Screenshot: High zoom
+
+**Attached**: {F11767}",1372251857,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-cc3wbqmetbmasfz6nkj6,task_subcomment,NA
+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",1372231980,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-rl6rjnnqsrrmwprvwrmk,task_description,resolved
+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 ***",1372270074,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rl6rjnnqsrrmwprvwrmk,task_subcomment,NA
+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",1372220460,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cypsptchtj5tr3ktdvxq,task_description,resolved
+VisualEditor: Possible to have links nested inside links,Merged and we'll push this to production in the next hour or so.,1372260507,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cypsptchtj5tr3ktdvxq,task_subcomment,NA
+VisualEditor: Possible to have links nested inside links,Related URL: https://gerrit.wikimedia.org/r/70644 (Gerrit Change I1cab7f3cc4fc9589eced01ad38c59fe5b9622a57),1372260143,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cypsptchtj5tr3ktdvxq,task_subcomment,NA
+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.",1372221303,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cypsptchtj5tr3ktdvxq,task_subcomment,NA
+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",1372192080,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-flrq364icuczabc3nb2z,task_description,resolved
+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",1412209365,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-flrq364icuczabc3nb2z,task_subcomment,NA
+"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}",1372175760,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-nctiyee24idgcp7llspj,task_description,open
+"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,1606768378,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1545161536,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1478109985,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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?",1477067771,PHID-USER-ijhuwuyd44xnfjon2ztf,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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. ***,1394074105,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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 <div
+> class=""mw-columns-2""> .. </div>. 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.",1374272400,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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 <div class=""mw-columns-2""> .. </div>. 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.",1374267053,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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. ***,1374014309,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1373440193,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1373054528,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1372789939,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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. ***,1372789775,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"VisualEditor: Add support for making some templates directly ""visually editable"" in the DOM, as if they were tables (e.g. infoboxes)","Something like <div class=""mw-columns-2""> .. </div> 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.",1372780602,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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]]",1372779956,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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. ***,1372427548,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+"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.",1372212497,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nctiyee24idgcp7llspj,task_subcomment,NA
+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",1372164120,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-nu54imdjney5p47v7jx7,task_description,resolved
+VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in,I think this was resolved in Gerrit change 127388,1397915597,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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..?",1381109369,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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. ***,1372796056,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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.",1372796032,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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.",1372728297,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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?",1372176869,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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.",1372172844,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nu54imdjney5p47v7jx7,task_subcomment,NA
+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",1372162920,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-f2jkrvqamprej6vbtifd,task_description,open
+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.",1372693967,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f2jkrvqamprej6vbtifd,task_subcomment,NA
+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"".",1372498760,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-f2jkrvqamprej6vbtifd,task_subcomment,NA
+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",1372158120,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eirxrxhok3puf5mpvsgj,task_description,open
+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).",1373553594,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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),1372424049,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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.",1372420020,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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)",1372169071,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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?",1372163402,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-eirxrxhok3puf5mpvsgj,task_subcomment,NA
+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",1372102560,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-coeco2n4cfz4d24eek2p,task_description,resolved
+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
+==<nowiki/>==
+```
+
+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 `<nowiki/>` in a heading at the end. I could not reproduce this on testwiki today. Closing as resolved.",1521857381,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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.",1521842541,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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.",1521842221,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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.",1443020040,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+VisualEditor: Can't copy/paste header from start of document without losing formatting,*** Bug 54728 has been marked as a duplicate of this bug. ***,1381157444,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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.",1381148291,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-coeco2n4cfz4d24eek2p,task_subcomment,NA
+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",1372091520,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gvpsurapr2wpn6mmysso,task_description,resolved
+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.,1372120126,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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],1372118250,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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),1372113630,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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<noinclude>|Example.svg</noinclude>}}}}}}}}|right|{{Str number/trim|{{{3|{{{width|250px}}}}}}}}px|{{{2|{{{caption<noinclude>|Caption goes here.</noinclude>}}}}}}]]
+
+->
+
+<figure class=""mw-halign-right"" typeof=""mw:Image"" data-parsoid=""…"">
+  <a href=""./File:Chloroplast_II.svg"" data-parsoid=""…""><img resource=""./File:Chloroplast_II.svg"" src=""…"" height=""344"" width=""360"" data-parsoid=""…""></a>
+  <figcaption class=""mw-figcaption"" data-parsoid=""{}"">Structure of a typical higher-plant chloroplast</figcaption>
+</figure>
+
+(The <figcaption> shouldn't be set, and also there should be an alt="""" set.)",1372110890,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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.",1372096750,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+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.",1372096339,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gvpsurapr2wpn6mmysso,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","https://en.wikipedia.org/w/index.php?title=AES11&diff=prev&oldid=561340674
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T57769}
+{T61647}",1372085880,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_description,resolved
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",Split that into {T96395} as it's mobile-specific.,1429293419,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",It looks like this is still happening: https://en.wikipedia.org/w/index.php?diff=655361654,1428430329,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",Indeed.,1427847427,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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).",1427822170,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",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?,1427820191,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",The same fix as for T51452 - verified in beta.,1427153983,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output <p> instead of <h#>
+
+[[https://gerrit.wikimedia.org/r/162310]]",1426893387,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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",1424197331,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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",1411496967,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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",1377222680,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",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.,1377203188,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","<< 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) >>",1375953600,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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?",1375792751,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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.",1374611501,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",*** Bug 51829 has been marked as a duplicate of this bug. ***,1374609807,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","""Encourage"" yes...",1373990534,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","(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.",1373987840,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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).",1373987554,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""","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)?",1373987470,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",%%%*** Bug 51417 has been marked as a duplicate of this bug. ***%%%,1373938091,PHID-USER-ttyyrgsrkyonct7hizgv,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+"VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output ""==<nowiki/>==""",*** Bug 50313 has been marked as a duplicate of this bug. ***,1373154763,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xd4kljcgqcwzmsvbid4p,task_subcomment,NA
+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",1372078500,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ui3plx4slven33rbf4id,task_description,resolved
+Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,"'[[' triggers Link insertion; '{{' - inserts Template.
+
+Verified in beta/test2/production",1418076035,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,ZOMG!,1418036506,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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]]",1416966721,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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",1416964645,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog,This is no longer catastrophically expensive to do. Yay.,1416960372,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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.",1372879524,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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 ""<gallery>"" into a Bugzilla bug title and expect it to say ""<gallery>"" 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.",1372786202,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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.,1372349396,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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)",1372091407,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-ui3plx4slven33rbf4id,task_subcomment,NA
+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",1372035540,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-zkfo43fncbploqynkreq,task_description,resolved
+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.,1373929765,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zkfo43fncbploqynkreq,task_subcomment,NA
+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",1373929587,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-zkfo43fncbploqynkreq,task_subcomment,NA
+VisualEditor: Reflist columns parameter getting ignored/changed for display,Can't reproduce (not anymore at least). Can you?,1373929392,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zkfo43fncbploqynkreq,task_subcomment,NA
+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}",1372035240,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-xeya3bpycvyi4743gzho,task_description,resolved
+VisualEditor: clicking on a template in the reference inspector causes odd blue shadowing,*** Bug 49768 has been marked as a duplicate of this bug. ***,1373155495,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xeya3bpycvyi4743gzho,task_subcomment,NA
+VisualEditor: clicking on a template in the reference inspector causes odd blue shadowing,"
+
+%%%*** This bug has been marked as a duplicate of bug 49818 ***%%%",1372118661,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-xeya3bpycvyi4743gzho,task_subcomment,NA
+VisualEditor: Unreferenced section template not displaying properly,"See screenshot; problem with the template or with the parsing of it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372033980,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_description,resolved
+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 ***",1373155344,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+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.",1372083906,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+VisualEditor: Unreferenced section template not displaying properly,Try https://en.wikipedia.org/wiki/Riddler#Fictional_character_biography,1372083632,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+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)",1372083538,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+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}",1372034067,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jxgfjh6zrpct7dssxnsk,task_subcomment,NA
+"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",1371995700,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vrnyctiie6ntzdrqt77a,task_description,resolved
+"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.",1642380969,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vrnyctiie6ntzdrqt77a,task_subcomment,NA
+"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, <i>Foo <sup>Bar</i> Baz</sup> 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.",1372000762,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vrnyctiie6ntzdrqt77a,task_subcomment,NA
+"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.)""",1371996216,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vrnyctiie6ntzdrqt77a,task_subcomment,NA
+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",1371977520,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-d42ybmk2s2iavorgwpdd,task_description,declined
+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",1379404668,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+Set $wgWellFormedXml = false by default,I note btw that the tidy config is also set to produce XHTML.,1375782777,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+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.",1375143938,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+Set $wgWellFormedXml = false by default,"(In reply to comment #2)
+> You could just use <script>if(jQuery)jQuery.ready()</script>, it would be
+> shorter than what you have currently: <script>window.jQuery &&
+> jQuery.ready();</script>
+
+<script>if(window.jQuery)jQuery.ready()</script>, 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.",1372758238,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+Set $wgWellFormedXml = false by default,"You could just use <script>if(jQuery)jQuery.ready()</script>, it would be shorter than what you have currently: <script>window.jQuery && jQuery.ready();</script>
+
+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.",1372740996,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+Set $wgWellFormedXml = false by default,Related URL: https://gerrit.wikimedia.org/r/70036 (Gerrit Change I4155c74042d22527dc5c9460a4af8b7b1adb36cc),1371978337,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-d42ybmk2s2iavorgwpdd,task_subcomment,NA
+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",1371896940,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-fcxjzl7orc3z55j4k4z4,task_description,resolved
+VisualEditor: cannot reposition typing cursor using the mouse in edit summary,Fixed and deployed; sorry for this.,1372007051,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fcxjzl7orc3z55j4k4z4,task_subcomment,NA
+VisualEditor: cannot reposition typing cursor using the mouse in edit summary,A fix to bug 49927 might also fix this.,1371899709,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-fcxjzl7orc3z55j4k4z4,task_subcomment,NA
+"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"".",1371864600,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-457x6imtkd7rswr4kl6x,task_description,duplicate
+"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.",1408114605,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"VisualEditor: Make defaultsort input field always use ""real"" text, not a placeholder",*** Bug 69568 has been marked as a duplicate of this bug. ***,1408096620,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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)",1394228553,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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.",1372888485,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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",1372882958,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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. ~~~~",1372881473,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-457x6imtkd7rswr4kl6x,task_subcomment,NA
+"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",1371851820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-busqmj37jbvye6nty5bt,task_description,resolved
+"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",1403052458,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"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",1403008691,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 49486 has been marked as a duplicate of this bug. ***,1380609083,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"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.,1380324429,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"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.",1380151994,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 52364 has been marked as a duplicate of this bug. ***,1375319436,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 50359 has been marked as a duplicate of this bug. ***,1373663953,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"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.,1373663569,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+"VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it",*** Bug 50183 has been marked as a duplicate of this bug. ***,1372183302,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-busqmj37jbvye6nty5bt,task_subcomment,NA
+VisualEditor: Closing a dialog scrolls you up to the top of the document,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1371844500,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_description,resolved
+VisualEditor: Closing a dialog scrolls you up to the top of the document,Fixed and being deployed right now.,1372264572,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_subcomment,NA
+VisualEditor: Closing a dialog scrolls you up to the top of the document,Related URL: https://gerrit.wikimedia.org/r/70614 (Gerrit Change I8cc12ba7845eebc6199fbcd2d355bf0d5f38264b),1372248326,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_subcomment,NA
+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.",1372246033,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_subcomment,NA
+VisualEditor: Closing a dialog scrolls you up to the top of the document,This is a regression because I fixed dialog close re-focusing.,1372245042,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-sl5n5bwvzliz5t3rwkrs,task_subcomment,NA
+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",1371833340,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-pcf2yvjdcefbppv4nmdv,task_description,resolved
+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).",1373160219,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pcf2yvjdcefbppv4nmdv,task_subcomment,NA
+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",1371829500,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-4tagph3in7nb7kiwdldq,task_description,resolved
+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.,1399325038,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4tagph3in7nb7kiwdldq,task_subcomment,NA
+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.",1371862821,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-4tagph3in7nb7kiwdldq,task_subcomment,NA
+"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'.
+",1371816900,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-ynxqancujipoqcvx5723,task_description,open
+"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).",1706714108,PHID-USER-jqjb54lbf7psat6shbcc,False,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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.",1598465114,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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.",1498746227,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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.",1498680522,PHID-USER-53x4y44yt43qjivfzsqf,False,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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:
+
+<p data-parsoid=""…"">This was <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw=""{'target':{'wt':'formatnum:1234567890','function':'formatnum'}"" data-parsoid=""…"">1,234,567,890</span> years ago.</p>
+
+… so maybe we'd want to special-case on 'function':'formatnum' so that they're easier to edit?",1371827641,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ynxqancujipoqcvx5723,task_subcomment,NA
+"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.
+",1371806460,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_description,declined
+"Window title for ""Creating"" should support parser functions","(If they're wontfix, then let's decline them.)",1428960831,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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. ",1428691205,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"Window title for ""Creating"" should support parser functions","(No ""Parse error at position 0"" since T54479 was fixed.)",1428685485,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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.",1428685233,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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.",1393633921,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"Window title for ""Creating"" should support parser functions",This seems solved now on dewp. Good to close from my side.,1372530530,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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]]).",1371813154,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-z4fhfn54bwmdzbvrehbm,task_subcomment,NA
+"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",1371799440,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-uebopddiz3ehqfkg326y,task_description,resolved
+"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.",1373328441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uebopddiz3ehqfkg326y,task_subcomment,NA
+"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",1373325381,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uebopddiz3ehqfkg326y,task_subcomment,NA
+"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",1373300386,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uebopddiz3ehqfkg326y,task_subcomment,NA
+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",1371789600,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_description,resolved
+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.",1377546664,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1377035685,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1376947589,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1376675597,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1376671455,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+Parsoid not correctly rendering bold/italic text,*** Bug 52254 has been marked as a duplicate of this bug. ***,1376606358,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+Parsoid not correctly rendering bold/italic text,See also bug 47326.,1374604512,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+Parsoid not correctly rendering bold/italic text,Just dropping this in for cross-referencing: bug 13227 (this bug made me remember that one).,1373766179,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+Parsoid not correctly rendering bold/italic text,"Taking this one, on subbu's suggestion.",1373301911,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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""",1373281341,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-gk2mpik33dhlthfx6ji5,task_subcomment,NA
+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",1371780960,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6j7kkh226srwx4yd3xob,task_description,declined
+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.,1530904214,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6j7kkh226srwx4yd3xob,task_subcomment,NA
+"VisualEditor: Rename internal use of ""Reference list"" to ""References list""","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371780900,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pg2baotfmhrts6ap3fmf,task_description,resolved
+"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",1408584637,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pg2baotfmhrts6ap3fmf,task_subcomment,NA
+"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",1408473225,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pg2baotfmhrts6ap3fmf,task_subcomment,NA
+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",1371759600,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-io6oush42k3uezzajdmy,task_description,declined
+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.",1389653066,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+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.",1385157948,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+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 ;)",1385137357,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,Greg: Was that a question to hashar?,1385134227,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,"So now ""all"" that is needed is to have this in a cronjob that mails the output to...?",1383761840,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,https://gerrit.wikimedia.org/r/#/c/70836/ adds a script to verify the extensions syncronization.,1372350237,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+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.
+$",1372349620,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+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.",1372349226,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,"Campaigns not updating, bug 50261",1372348299,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+monitor mediawiki extensions superproject misconfiguration,"Vector was not updated either, might have caused bug 49911",1372090121,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-io6oush42k3uezzajdmy,task_subcomment,NA
+"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",1371753840,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-js3thiqf6n5putzp4qaq,task_description,resolved
+"Parsoid should have template parameter key/value whitespace of "" = "" not ""=""",This has now been done in Parsoid.,1372007229,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-js3thiqf6n5putzp4qaq,task_subcomment,NA
+"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.",1371793447,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-js3thiqf6n5putzp4qaq,task_subcomment,NA
+"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.",1371777646,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-js3thiqf6n5putzp4qaq,task_subcomment,NA
+"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",1371722040,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-fzpzl3u4tnchcdvuauzd,task_description,declined
+"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.",1393526293,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fzpzl3u4tnchcdvuauzd,task_subcomment,NA
+"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.",1371777288,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-fzpzl3u4tnchcdvuauzd,task_subcomment,NA
+"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?",1371775521,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fzpzl3u4tnchcdvuauzd,task_subcomment,NA
+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",1371681900,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_description,resolved
+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",1395081900,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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",1395081559,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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.",1395081362,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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).",1395080439,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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?",1395077436,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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?",1395072264,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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.",1395071686,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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",1393637954,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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.,1392847659,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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?).,1387811244,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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
+<span typeof=""mw:Image"" ><a href=""./File:VisualEditor-logo.svg""><img src=""http://vewiki/MediaWiki/images/thumb/1/12/VisualEditor-logo.svg/300px-VisualEditor-logo.svg.png"" resource=""./File:VisualEditor-logo.svg"" width=""300"" height=""105""></a></span>
+[subbu@earth lib] node parse --html2wt < /tmp/img.html
+[[File:VisualEditor-logo.svg|300x300px]]",1385081773,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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],1372934020,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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.",1372214663,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+Images: New images get a link=… set whether or not they need it,*** Bug 49848 has been marked as a duplicate of this bug. ***,1372214626,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+Images: New images get a link=… set whether or not they need it,Related URL: https://gerrit.wikimedia.org/r/70551 (Gerrit Change I75dbbfdd248a6f5696252ef3a2d7ca6ede0fa156),1372198165,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+Images: New images get a link=… set whether or not they need it,"<span typeof=""mw:Image"" ><a href=""./File:VisualEditor-logo.svg"" data-parsoid=""{'a':{'href':'./File:VisualEditor-logo.svg'}}""><img src=""http://vewiki/MediaWiki/images/thumb/1/12/VisualEditor-logo.svg/300px-VisualEditor-logo.svg.png"" resource=""./File:VisualEditor-logo.svg"" width=""300"" height=""105""></a></span>
+
+serialises to:
+
+[[File:VisualEditor-logo.svg|300x105px]]
+
+Whereas
+
+<span typeof=""mw:Image"" ><a href=""./File:VisualEditor-logo.svg""><img src=""http://vewiki/MediaWiki/images/thumb/1/12/VisualEditor-logo.svg/300px-VisualEditor-logo.svg.png"" resource=""./File:VisualEditor-logo.svg"" width=""300"" height=""105""></a></span>
+
+(removed data-parsoid from <a> tag)
+
+serialises to:
+
+[[File:VisualEditor-logo.svg|link=File:VisualEditor-logo.svg|300x105px]]",1371815879,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+Images: New images get a link=… set whether or not they need it,This looks like a Parsoid issue:,1371815790,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-pvs5mqz2lxwkwyv7enfq,task_subcomment,NA
+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",1371667800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-q46agi2mree3c3qnk2y4,task_description,invalid
+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.",1377905614,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-q46agi2mree3c3qnk2y4,task_subcomment,NA
+VisualEditor: Quick transclusion dialog UX improvements,Have un-trackered-this;,1377900084,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-q46agi2mree3c3qnk2y4,task_subcomment,NA
+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",1373390839,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-q46agi2mree3c3qnk2y4,task_subcomment,NA
+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).",1372115134,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-q46agi2mree3c3qnk2y4,task_subcomment,NA
+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",1371653940,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-ju3g2oypj6sg3qneywp4,task_description,resolved
+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.,1373519486,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ju3g2oypj6sg3qneywp4,task_subcomment,NA
+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.  :)",1372611006,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ju3g2oypj6sg3qneywp4,task_subcomment,NA
+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",1371640200,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-fismtah5nhz3jechnxci,task_description,resolved
+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? 
+",1426194482,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1426093128,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?),{F56750}?,1425633018,PHID-USER-tjeabpzbwsqw3xciydvb,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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]]",1425595128,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ",1425336374,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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]]
+",1425335832,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1415129033,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. :-)",1407754116,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1405114018,PHID-USER-mcyovqjor52nj3se4lq7,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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"". :-)",1405095333,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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?,1405090910,PHID-USER-mcyovqjor52nj3se4lq7,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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?",1405021766,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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'?",1405021269,PHID-USER-mcyovqjor52nj3se4lq7,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1393529166,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1393271674,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1376642559,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1376609977,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1375472168,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1375471087,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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?",1374978010,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1374447614,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.,1374427617,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.,1374261491,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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. ***,1374086311,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1373895714,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1373646789,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1373610238,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1373225859,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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... ?""",1373225304,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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,1372445837,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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 <div style=""display:none;"">something</div> hidden, or what about <div class=""hidden"">something</div> when [[MediaWiki:Common.css]] contains .hidden{display:none;} ?",1372441452,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1371790287,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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.",1371755069,PHID-USER-evwol34rsld7viokxokd,False,PHID-TASK-fismtah5nhz3jechnxci,task_subcomment,NA
+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",1371595680,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_description,resolved
+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]]",1463387273,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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]]
+",1463310979,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 72045 has been marked as a duplicate of this bug. ***,1413312100,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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.",1412202934,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 52032 has been marked as a duplicate of this bug. ***,1395357259,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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 <span> 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.",1386022898,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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 <span> 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).",1386022755,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 50610 has been marked as a duplicate of this bug. ***,1385375646,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,*** Bug 54893 has been marked as a duplicate of this bug. ***,1380746310,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update,%%%*** Bug 50363 has been marked as a duplicate of this bug. ***%%%,1375118083,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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.",1371595810,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pyjlzzqqrcxthunhdjxd,task_subcomment,NA
+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",1371592380,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_description,resolved
+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",1372553711,PHID-USER-2mkpm2voxepwvz7abjug,True,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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).",1372548881,PHID-USER-jcypqodpdpbcicgwgh7j,True,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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",1372547853,PHID-USER-2mkpm2voxepwvz7abjug,True,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+VisualEditor: Template dialog should look up TemplateData for newly-added templates,Done in the above commit.,1372462774,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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",1372462602,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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",1372455529,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+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).",1372411786,PHID-USER-j5ma2nageni56xp567v5,True,PHID-TASK-4ea4xsfwmbsq76ri4xgj,task_subcomment,NA
+"VisualEditor: Images, when resized, appear on top of (rather than underneath) other UI elements","Screenshot
+
+See associated screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11694}",1371583860,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-sbmvrc3jz243m2e4aqmd,task_description,resolved
+"VisualEditor: Images, when resized, appear on top of (rather than underneath) other UI elements","Now fixed, I believe.",1372016119,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sbmvrc3jz243m2e4aqmd,task_subcomment,NA
+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",1371579720,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-2nqdcy26wu7c3ct3pti6,task_description,open
+VisualEditor: Rename [big|small]Stack variables in ve.dm.Surface,"To something which describes their function, not form.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371571320,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vaw5sbbofozchqbqlxfo,task_description,resolved
+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",1386729691,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vaw5sbbofozchqbqlxfo,task_subcomment,NA
+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",1386534617,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vaw5sbbofozchqbqlxfo,task_subcomment,NA
+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",1371521220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jdjfrc2gvkcmr2dyxdhz,task_description,resolved
+VisualEditor: You can't select text in the save dialog,This was fixed in wmf8.,1371775703,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jdjfrc2gvkcmr2dyxdhz,task_subcomment,NA
+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}",1371465120,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_description,resolved
+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.",1372863371,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+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).",1372859288,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+VisualEditor: Link duplicated,This isn't necessarily the same issue. Is it reproduceable?,1372858764,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+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,1372851661,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+VisualEditor: Link duplicated,"We fixed this as part of the DM tweaks, I believe.",1372017902,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-isdw3zrrbc3uvww3ghe4,task_subcomment,NA
+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",1371404760,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-e2zkvddmlxs36w5rmyck,task_description,resolved
+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.,1383959019,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e2zkvddmlxs36w5rmyck,task_subcomment,NA
+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.",1383957760,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-e2zkvddmlxs36w5rmyck,task_subcomment,NA
+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.",1371437921,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e2zkvddmlxs36w5rmyck,task_subcomment,NA
+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.
+",1371315660,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-3z252ihuxf33ir4how73,task_description,resolved
+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]]
+",1506354915,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1506353477,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,Adding the tag per https://www.mediawiki.org/w/index.php?title=Topic:Tys3st4u4fbxis43 .,1506344878,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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}",1505939521,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505921950,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505920720,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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&section=new",1505920852,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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&section=new",1505920393,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1505905997,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505764754,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505749186,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505747261,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1505512035,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1505511929,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.,1499341318,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]",1483474747,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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]]
+",1483203829,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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 ]]).",1481256401,PHID-USER-aklqcs2xae5ghg6icqmd,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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}",1481076359,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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,1466772802,PHID-USER-5paybpgtxjrhikdos3p5,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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?",1466694115,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,A note from @tpt that this is pretty important for successful #proofreadpage integration.,1466693905,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1434985826,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1434985691,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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!",1434967229,PHID-USER-wtbw6n3qdyre3vir7o3z,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1434831191,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,"I've merged the above, and copied the details into the description above.",1434824570,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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)",1424027843,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,Editintro/preloud are parts of inputbox extension? Or how it is related?,1424000855,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+Add support for (the equivalent of?) editintro and preload,Indeed.,1421917704,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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.",1419623366,PHID-USER-rbfsfm2cvpr37oz3wxju,False,PHID-TASK-3z252ihuxf33ir4how73,task_subcomment,NA
+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",1371313740,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-6welutlbuxohheakxhlf,task_description,resolved
+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. ***,1373162765,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6welutlbuxohheakxhlf,task_subcomment,NA
+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.,1372109956,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6welutlbuxohheakxhlf,task_subcomment,NA
+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),1372109122,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6welutlbuxohheakxhlf,task_subcomment,NA
+"""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",1371298920,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-ccjs4p2cgeia2i67aibl,task_description,resolved
+"""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",1376116309,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ccjs4p2cgeia2i67aibl,task_subcomment,NA
+"""View source"" is missing on protected LQT pages",Related URL: https://gerrit.wikimedia.org/r/68860 (Gerrit Change I99c17acea0be7b0ef650959e5e280ca5e9154b2a),1371306935,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ccjs4p2cgeia2i67aibl,task_subcomment,NA
+"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",1371297660,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-fbmrhc7yiidum6n27xww,task_description,open
+"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.",1371429262,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fbmrhc7yiidum6n27xww,task_subcomment,NA
+"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.",1371426645,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-fbmrhc7yiidum6n27xww,task_subcomment,NA
+"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.)",1371422468,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fbmrhc7yiidum6n27xww,task_subcomment,NA
+"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.",1371297776,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-fbmrhc7yiidum6n27xww,task_subcomment,NA
+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",1371261480,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_description,resolved
+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,1372103132,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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,1372103030,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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?",1372098253,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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.,1372093892,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"From <https://en.wikipedia.org/w/index.php?title=Wikipedia:Administrators%27_noticeboard&oldid=560544063#VisualEditor_-_A.2FB_test_launch_on_18_June>:
+
+---
+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.",1371610389,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"I fully agree with MZMcBride :
+* I think it's ethically questionable to run experiments on users in this manner
+* There are still severe bugs in VisualEditor at this time, so it shouldn't be deployed more widely
+
+And I've more concerns about this kind of experiments :
+* There are still a lot of minor/major bugs in VisualEditor at this time, I don't expect new users to have to handle them when discovering Wikipedia edition.
+* There are still major limitations on what can be done with VisualEditor (templates, references, ...). What will be the experience for new users if they can only edit some parts of articles ?
+
+I believe this kind of experiment should only be done when VisualEditor is fully functional (when users can do almost every modification they want) and without major bugs left.",1371286353,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,"(In reply to comment #0)
+> 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.",1371266626,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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.",1371263231,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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.",1371262864,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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),1371262367,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts,Has en.wikipedia been notified?,1371262231,PHID-USER-hwuumsjqciw7ji5qhpc7,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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),1371262153,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-esg6d3iurlxoqoaozlgc,task_subcomment,NA
+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",1371258900,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_description,resolved
+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",1373582616,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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.",1373486407,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+VisualEditor: Show VisualEditor tag in diffs,"Change 72317 merged by jenkins-bot:
+Show change tags on diffs
+
+https://gerrit.wikimedia.org/r/72317",1373483242,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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.)",1373226492,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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.",1373162088,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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.",1373150736,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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?",1373145320,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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",1373144622,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+VisualEditor: Show VisualEditor tag in diffs,"Core change request created as bug 49656. Until that's done this is a ""later"", sadly.",1371419564,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hmd3ybxvx2oovxcgcs5b,task_subcomment,NA
+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",1371201120,PHID-USER-4jecvpv4h62htut6pxez,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_description,resolved
+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.",1453749454,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 58662 has been marked as a duplicate of this bug. ***,1389025443,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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.,1377961711,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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",1377957239,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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.",1377491236,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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",1374250703,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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"".",1374241350,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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",1374238606,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 51354 has been marked as a duplicate of this bug. ***,1373968970,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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. ***%%%",1372424196,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 50345 has been marked as a duplicate of this bug. ***,1372403231,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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.",1372351337,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 50293 has been marked as a duplicate of this bug. ***,1372351064,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 49704 has been marked as a duplicate of this bug. ***,1371699225,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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. :-),1371429357,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+Make ULS input methods work in content editable divs of VisualEditor,*** Bug 49643 has been marked as a duplicate of this bug. ***,1371409196,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+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,1371204225,PHID-USER-m2yck6646cdt5t6zkta4,False,PHID-TASK-okxdqrb2z7y2e2t7su5q,task_subcomment,NA
+VisualEditor: Review behaviour in CE with <p><br /></p>s,"Need to review and get working so we can ask Parsoid to re-enable these (stop them being wrapped as <mw:Placeholder>s) - bug 47403 comment 3.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1371181020,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-txjmg5opo7xccxwery5r,task_description,open
+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",1371162780,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-mmsz5huxzdhmzpx6zlmd,task_description,open
+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).",1371163018,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mmsz5huxzdhmzpx6zlmd,task_subcomment,NA
+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",1371162120,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fruuvllzbsjlpilalc3q,task_description,resolved
+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]]
+",1433773169,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fruuvllzbsjlpilalc3q,task_subcomment,NA
+VisualEditor: Can't paste into a selection covering the end of the document,Merged and will go out with wmf8 from Thursday 20 June.,1371233886,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fruuvllzbsjlpilalc3q,task_subcomment,NA
+VisualEditor: Can't paste into a selection covering the end of the document,Related URL: https://gerrit.wikimedia.org/r/68629 (Gerrit Change I7497b5195961e46718c7382409a66b7eec1162a9),1371207127,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fruuvllzbsjlpilalc3q,task_subcomment,NA
+"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",1371158700,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_description,resolved
+"VisualEditor: Dialogs are quite big, maybe they could be smaller",We changed the sizes of dialogs a few months ago.,1399324736,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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",1372037113,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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...",1371167576,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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)",1371167012,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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.",1371166679,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+"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.",1371160792,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k2rw3gv6tegtzx4fqydd,task_subcomment,NA
+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",1371107160,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-dlisjakdxxdx6ulkcllp,task_description,resolved
+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.",1416502788,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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?,1416499941,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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.,1371688878,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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.",1371688489,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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}",1371422675,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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}",1371294885,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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.",1371145548,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-dlisjakdxxdx6ulkcllp,task_subcomment,NA
+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}",1371060180,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-pq2jmdduyi27pmzdn6fs,task_description,resolved
+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!",1371437544,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pq2jmdduyi27pmzdn6fs,task_subcomment,NA
+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:  <h3 data-parsoid='{""dsr"":[4514,4534,3,3]}'></h3>
+
+Serializes to ===<nowiki/>=== 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",1370981700,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_description,resolved
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,These look like cached code issues. Closing absent further issues.,1428879414,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1428038357,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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}
+
+
+
+",1428015629,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"No other edits with `==<nowiki/>==` for the moment, I will send an other comment if I see one",1428007868,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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 `==<nowiki/>==` that are more recent?",1427995437,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1427990524,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"Deleting headings is clean now
+
+Beta {F103264}
+vs
+current production(wmf22)
+{F103266}",1427153835,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,"Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output <p> instead of <h#>
+
+[[https://gerrit.wikimedia.org/r/162310]]",1426893388,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1424197333,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs,*** Bug 70368 has been marked as a duplicate of this bug. ***,1415886608,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1412538863,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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).,1370983752,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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).",1370982732,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cdvhznmmt4p6jcin6skh,task_subcomment,NA
+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",1370954520,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sit6vtslr7r2fqfrzugp,task_description,resolved
+VisualEditor: Grunt leaves behind temporary html file if tests fail,Related URL: https://gerrit.wikimedia.org/r/68631 (Gerrit Change I5079d00a63d43276a12dd78c306bb3819470631d),1371209624,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sit6vtslr7r2fqfrzugp,task_subcomment,NA
+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",1370952120,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-2qasjtis6bukznlqh6fa,task_description,open
+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?",1371157225,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2qasjtis6bukznlqh6fa,task_subcomment,NA
+"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",1370950980,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-4rqn2y6kag5uml6nligz,task_description,resolved
+"Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)",Fix deployed.,1372103155,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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],1372100461,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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),1372095883,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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.",1372016595,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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.",1372016463,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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.",1372016204,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+"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",1372008424,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4rqn2y6kag5uml6nligz,task_subcomment,NA
+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",1370912280,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yt5y3btrqqtcxanvipk4,task_description,invalid
+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.",1493662142,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yt5y3btrqqtcxanvipk4,task_subcomment,NA
+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' ] );""",1371579540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yt5y3btrqqtcxanvipk4,task_subcomment,NA
+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.",1370966116,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-yt5y3btrqqtcxanvipk4,task_subcomment,NA
+Images: Handle templated image options containing pipes,"Some perverse templates such as {{Largethumb}} return a string with several options separated by pipes (""thumb|<number>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",1370889600,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_description,resolved
+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.
+",1586539013,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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. ",1448822406,PHID-USER-mcyovqjor52nj3se4lq7,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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.",1445266289,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,"Nothing to be here for this quarter .. So, I am removing the VE Q3 blocker part.",1426264942,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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 <figure> 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.",1424980985,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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.",1422665790,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,All patches merged; resetting bug status,1398408280,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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?,1392422070,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1392413844,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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.",1391708056,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1391639487,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1375218314,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1375215680,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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).",1374636592,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,~ 1 in 225 nlwp articles (0.45%) have this bug.  This bug affects the whole page.,1374635889,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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}}'.",1374627506,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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.",1374598056,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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",1374571791,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,https://gerrit.wikimedia.org/r/67853 (Gerrit Change Ic7652979ec3d5fa35995aac9362c812ab4ede173) | change APPROVED and MERGED [by jenkins-bot],1370890352,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+Images: Handle templated image options containing pipes,Related URL: https://gerrit.wikimedia.org/r/67853 (Gerrit Change Ic7652979ec3d5fa35995aac9362c812ab4ede173),1370889698,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rkmnvdgo6nof3bkunyfu,task_subcomment,NA
+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 <nowiki> 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",1370887500,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_description,resolved
+VisualEditor: Misc. issues,Marking as such.,1371227728,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"The <nowiki> 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.",1371227543,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+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.",1370992657,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"The <nowiki> 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 <nowiki> 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)",1370984493,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"Expansion wtf (warning: large diff):
+
+https://en.wikipedia.org/w/index.php?title=Breast_cancer&diff=558696523&oldid=558695500",1370895676,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+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)
+> <Gallery> 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.",1370895167,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"<nowiki> funkiness:
+
+https://en.wikipedia.org/w/index.php?title=Louis-J%C3%A9r%C3%B4me_Gohier&curid=2785680&diff=558445883&oldid=542944471",1370894826,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"Misspelling trap:
+
+https://en.wikipedia.org/w/index.php?title=Pepsi_Next&curid=35519554&diff=559230837&oldid=559223494",1370889236,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+VisualEditor: Misc. issues,"<Gallery> funkiness:
+
+https://en.wikipedia.org/w/index.php?title=British_Rail_Class_50&curid=1448622&diff=559199747&oldid=558786539",1370888839,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+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 <https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=visualeditor>.
+
+
+<nowiki> corruption:
+
+https://en.wikipedia.org/w/index.php?title=Black_Country_Communion&curid=25818560&diff=559205644&oldid=547680063
+
+
+<nowiki/> weirdness:
+
+https://en.wikipedia.org/w/index.php?title=Lightning_(software)&diff=prev&oldid=559252596
+
+
+Possible unintentional HTML comment removal; <nowiki> corruption:
+
+https://en.wikipedia.org/w/index.php?title=Underworld_(band)&diff=prev&oldid=559255806",1370888558,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-oqao2yl4prg5uecpylkw,task_subcomment,NA
+"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.
+",1370728680,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-bhc7xmtcptcglmeqxvai,task_description,open
+"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). :-)",1459673675,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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. ",1459672642,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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 <ref>s */
+span.mw-ref a::after {
+  content: counter(mw-Ref,decimal);
+} 
+```",1459667425,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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.",1459667268,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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.",1459666387,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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.,1413330448,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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 <ref group=lower-alpha> 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.",1407177406,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+"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. ***,1379788309,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-bhc7xmtcptcglmeqxvai,task_subcomment,NA
+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",1370654940,PHID-USER-7e4yonmruupxzg23swum,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_description,resolved
+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.",1376684880,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"Change 79321 merged by jenkins-bot:
+Add tyv.wikipedia to projects with visualeditor
+
+https://gerrit.wikimedia.org/r/79321",1376665033,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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",1376653964,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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/",1376639564,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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",1376621641,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,RT ticket created for addition of lucene search indexes https://rt.wikimedia.org/Ticket/Display.html?id=5588,1376196871,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Done!,1376196328,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"Change 68188 merged by jenkins-bot:
+(bug 49328) Create Wikipedia in Tyvan language
+
+https://gerrit.wikimedia.org/r/68188",1376194827,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,*** Bug 52691 has been marked as a duplicate of this bug. ***,1376116627,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"Change 78332 merged by jenkins-bot:
+Add tyv to langlist
+
+https://gerrit.wikimedia.org/r/78332",1376020675,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"Change 78332 had a related patch set uploaded by Reedy:
+Add tyv to langlist
+
+https://gerrit.wikimedia.org/r/78332",1376020621,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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
+> <https://meta.wikimedia.org/w/index.php?diff=5529039&oldid=5528970>, 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 <http://incubator.wikimedia.org/wiki/Talk:Wp/tyv/%D0%9A%D0%BE%D0%BB_%D0%B0%D1%80%D1%8B%D0%BD#Localization> 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.",1374941968,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"It should not be chosen arbitrarily. It is chosen according to what was requested on the Meta request, here <https://meta.wikimedia.org/w/index.php?diff=5529039&oldid=5528970>, 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.",1374927661,PHID-USER-7e4yonmruupxzg23swum,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #15)
+> (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 Видибилиином?",1374916375,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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 ""Видибилиином"".",1374916112,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1374767554,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1374065889,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1374061512,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.)",1373968444,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1373963779,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.",1373941142,PHID-USER-7e4yonmruupxzg23swum,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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?):
+> <https://incubator.wikimedia.org/wiki/Talk:Wp/tyv/
+> %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:
+> <https://incubator.wikimedia.org/w/index.php?title=Wp/tyv/
+> %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.",1373939223,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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?): <https://incubator.wikimedia.org/wiki/Talk:Wp/tyv/%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: <https://incubator.wikimedia.org/w/index.php?title=Wp/tyv/%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.",1373897829,PHID-USER-7e4yonmruupxzg23swum,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,@MF-Warburg: Would you please tell us /what the hell/ is going on here? Your request was totally different from comment 6.,1373883715,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,"**polar_bear0901** wrote:
+
+(In reply to comment #5)
+> 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.",1373863960,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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.)",1373863597,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Waiting for Reedy to do some on-server magic.,1373803738,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Any problems with this request?,1373788651,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Related URL: https://gerrit.wikimedia.org/r/68188 (Gerrit Change I7e9a1193500b7e09a29dab1d833c712db9453422),1371051069,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,Related URL: https://gerrit.wikimedia.org/r/68188 (Gerrit Change I7e9a1193500b7e09a29dab1d833c712db9453422),1371051066,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+Create Wikipedia Tuvan,[I guess that's more of a site request than a language setup bug? Also changing priority.],1370682017,PHID-USER-hxjysvdvogekpjub3nd3,False,PHID-TASK-trlh3c7s2ff2x2avhgoo,task_subcomment,NA
+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",1370622300,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ticw62p4dy4nr4dhvsrq,task_description,resolved
+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.,1402688105,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ticw62p4dy4nr4dhvsrq,task_subcomment,NA
+VisualEditor: Sometimes ignores changing a wikilink with an underscore to one with a space,"Is this a Parsoid issue?
+
+<p><a href=""./Main_page"" rel=""mw:WikiLink"" data-parsoid=""{&quot;a&quot;:{&quot;href&quot;:&quot;./Main_page&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;Main_page&quot;},&quot;stx&quot;:&quot;simple&quot;,&quot;dsr&quot;:[0,13,2,2]}"">Main page</a></p>
+
+serialises to
+
+[[Main_page]]
+
+whereas
+
+<p><a href=""./Main_page"" rel=""mw:WikiLink"">Main page</a></p>
+
+serialises to
+
+[[Main page]]
+
+which is what we want",1371168271,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ticw62p4dy4nr4dhvsrq,task_subcomment,NA
+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}",1370617380,PHID-USER-pts53ljtnbn3jhkllas6,False,PHID-TASK-7ci67c3uih3tuev7ghu3,task_description,resolved
+VisualEditor: Images' selection blocks can overlap the toolbar and prevent saving/etc.,The problem seems to be fixed in the current version. Thank you!,1373649909,PHID-USER-pts53ljtnbn3jhkllas6,False,PHID-TASK-7ci67c3uih3tuev7ghu3,task_subcomment,NA
+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}",1370620359,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7ci67c3uih3tuev7ghu3,task_subcomment,NA
+VisualEditor: Provide full grapheme cluster boundary detection,"Per Ed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370532360,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3qm4izjirylpzskf6mlm,task_description,resolved
+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.",1371423759,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3qm4izjirylpzskf6mlm,task_subcomment,NA
+VisualEditor: Provide full grapheme cluster boundary detection,Related change: https://gerrit.wikimedia.org/r/#/c/68864/,1371420521,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-3qm4izjirylpzskf6mlm,task_subcomment,NA
+"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}",1370371920,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-inqexk3a4klng6im6ld7,task_description,resolved
+"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!",1395021940,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1394910439,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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}",1394901722,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1394900638,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1394889750,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?","Argh, yes, Kaldari got his comment in before mine. :-)",1371858127,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1371858070,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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. ***,1371857901,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.",1370806025,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"VisualEditor: ""Review your changes"" - cancel-arrow needs a tooltip; possibly replace with an ""X""?",Thanks for the catch!,1370539736,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+"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.)",1370479896,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-inqexk3a4klng6im6ld7,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Since MediaWiki allows images that are clearly separated out, we should see if we can use `<figure>` and `<figcaption>`.  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}",1370315820,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_description,resolved
+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",1637266651,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1634321226,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1634244096,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1634243825,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1634059807,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1633537791,PHID-USER-ocqnoktaualicuvge2tu,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633480989,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633480028,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633479766,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633476238,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633475767,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633475698,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633471391,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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?",1633450464,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633448058,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633448046,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633447156,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633446229,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Deployment to Meta broke global user pages appearing on wikis that still use the legacy `<div>`-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.",1633422992,PHID-USER-ocqnoktaualicuvge2tu,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Deployment to Meta broke global user pages appearing on wikis that still use the legacy `<div>`-based output, see T292498.
+",1633422717,PHID-USER-ocqnoktaualicuvge2tu,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633046282,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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] <thcipriani@deploy1002> Synchronized wmf-config/InitialiseSettings.php: Config: [[gerrit:724861|Disable legacy media dom on a few more wikis (T51097)]] (duration: 01m 08s)",1633026053,PHID-USER-j4uyesgqhubl2dywl4xd,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1633025810,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1632960717,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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} )",1632754354,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 ?",1632753845,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1631051594,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1631051550,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1631050915,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1631050878,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1630606208,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 ]]),1630083005,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 ]]),1630082994,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1630082949,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629928616,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1629924997,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1629924192,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1629924129,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1629923807,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629923159,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,I also see all the VE JS being loaded (with debug=true).. that's not normal.... ,1629922678,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629921914,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629919335,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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] <urbanecm@deploy1002> Synchronized wmf-config/InitialiseSettings.php: e6df0803e4eaca91bd725bcd376b260b97917de3: Disable legacy media dom on a few more wikis (T51097) (duration: 01m 05s)",1629915383,PHID-USER-j4uyesgqhubl2dywl4xd,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629914814,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1629844175,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.
+",1628004330,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1627999846,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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. ",1627999455,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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. ",1627999353,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]
+```
+```
+<figure class=""mw-halign-right djtest"" typeof=""mw:Image/Thumb""><a href=""/wiki/File:Onion_diagram.svg"" title=""""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/300px-Onion_diagram.svg.png"" decoding=""async"" width=""300"" height=""197"" srcset=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/450px-Onion_diagram.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/600px-Onion_diagram.svg.png 2x"" data-file-width=""875"" data-file-height=""575""></a><figcaption>In this example onion, we test image placement.</figcaption></figure>
+```
+
+```
+<div class=""thumb tright""><div class=""thumbinner"" style=""width:302px;""><a href=""/wiki/File:Onion_diagram.svg"" class=""image"" title=""""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/300px-Onion_diagram.svg.png"" decoding=""async"" width=""300"" height=""197"" class=""djtest thumbimage"" srcset=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/450px-Onion_diagram.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/600px-Onion_diagram.svg.png 2x"" data-file-width=""875"" data-file-height=""575""></a>  <div class=""thumbcaption""><div class=""magnify""><a href=""/wiki/File:Onion_diagram.svg"" class=""internal"" title=""Enlarge""></a></div>In this example onion, we test image placement.</div></div></div>
+```",1627999209,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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,
+
+```
+<figure class=""mw-halign-right"" typeof=""mw:Image/Thumb""><a href=""/wiki/File:Onion_diagram.svg""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/300px-Onion_diagram.svg.png"" decoding=""async"" width=""300"" height=""197"" srcset=""//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/450px-Onion_diagram.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Onion_diagram.svg/600px-Onion_diagram.svg.png 2x"" data-file-width=""875"" data-file-height=""575""></a><figcaption>In this example onion, we test image placement.</figcaption></figure>
+```
+
+However, on mediawikiwiki, after similarly purging we get on https://www.mediawiki.org/wiki/Parsoid
+
+```
+<div class=""thumb tright""><div class=""thumbinner"" style=""width:514px;""><a href=""/wiki/File:Parsoid_HTML-RDFa_content_model.svg"" class=""image""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/2/2e/Parsoid_HTML-RDFa_content_model.svg/512px-Parsoid_HTML-RDFa_content_model.svg.png"" decoding=""async"" width=""512"" height=""362"" class=""thumbimage"" data-file-width=""512"" data-file-height=""362""></a>  <div class=""thumbcaption"">Artist's impression of the Parsoid HTML5 + RDFa wiki runtime</div></div></div>
+```",1625002036,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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] <urbanecm@deploy1002> Synchronized wmf-config/InitialiseSettings.php: 5ec855d14b31a9392274c2bfe2e21e2ad44986bc: Enable Parsoid inspired media structure on test wikis (T51097) (duration: 00m 59s)",1624921541,PHID-USER-j4uyesgqhubl2dywl4xd,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1624921358,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1624655511,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1624580053,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Change 701449 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] Add <figure> to the never suppressing group in BlockLevelPass%%%
+https://gerrit.wikimedia.org/r/701449",1624563463,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Change 701449 had a related patch set uploaded (by Arlolra; author: Arlolra):
+%%%[mediawiki/core@master] Add <figure> to the never suppressing group in BlockLevelPass%%%
+https://gerrit.wikimedia.org/r/701449",1624562043,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,https://gerrit.wikimedia.org/r/c/507512 is the only open patch remaining.,1617354427,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1610568452,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1608245687,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1608047326,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"From an accessibility standpoint, there may be reasons to emit a descriptive `<figcaption>` 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) `<p>` 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.)",1608046662,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"From an accessibility standpoint, there may be reasons to emit a descriptive `<figcaption>` 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) `<p>` 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.",1608046292,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1608045476,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1608002858,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1608002549,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1608000898,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607994875,PHID-USER-gxcjmjpejlhfnrquksm2,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.
+",1607984896,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.
+",1607984532,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.
+",1607984390,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1607983473,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607716556,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607713852,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607705268,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1607629897,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1556663538,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1556663464,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Change 505645 **merged** by jenkins-bot:
+[mediawiki/core@master] Allow <figure-inline> attributes through Sanitizer
+
+[[https://gerrit.wikimedia.org/r/505645]]",1556305851,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 <figure-inline> attributes through Sanitizer
+
+[[https://gerrit.wikimedia.org/r/505645]]",1555952830,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1511202815,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 <figure> 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? :))",1483413867,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 <figure> 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?
+",1483413836,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,@niedzielski: cool.,1449265385,PHID-USER-srhlj2447vmpmrfhqnfa,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1449261814,PHID-USER-6tlavgtsosjuvizsej53,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1449198930,PHID-USER-srhlj2447vmpmrfhqnfa,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+Use figure and figcaption HTML5 elements when possible,"Thanks, @niedzielski!",1449198765,PHID-USER-srhlj2447vmpmrfhqnfa,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1449194986,PHID-USER-6tlavgtsosjuvizsej53,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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}
+
+ ",1449179179,PHID-USER-6tlavgtsosjuvizsej53,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1437515671,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]",1437392905,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.,1436994247,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 `<figure>` 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 `<div>` 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.",1435616576,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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 `<figure>` 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 `<div>` 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.",1435616550,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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.",1427474703,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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)?",1427411748,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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",1427275316,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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).",1427274219,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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!),1427250080,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]
+",1426227143,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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]]
+",1426227102,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+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, <figure> and <figcaption> could be thrown in around the existing <div>s and <span>s without changing the styles, assuming there's no default styles that override stuff.",1380740509,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-jjld4d5wjqxkuihohuzl,task_subcomment,NA
+VisualEditor: Reference lists should update more intelligently (i.e. less often),"Currently a reference list (<references /> 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.",1370299680,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ebn2j76ougc2mnfqb4fp,task_description,open
+Enable VisualEditor alpha on all Wikipedias,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1370286120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nlxbzrcehkp3h36untox,task_description,resolved
+Enable VisualEditor alpha on all Wikipedias,Done on 2013-06-06.,1370741034,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nlxbzrcehkp3h36untox,task_subcomment,NA
+Enable VisualEditor alpha on all Wikipedias,Related URL: https://gerrit.wikimedia.org/r/67151 (Gerrit Change I98eb9f4979ae8d1dc2fdca4d812feaee28672444),1370466138,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nlxbzrcehkp3h36untox,task_subcomment,NA
+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",1370181480,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rhsntkwc7ofl6qzz7kt4,task_description,resolved
+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.",1372809190,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rhsntkwc7ofl6qzz7kt4,task_subcomment,NA
+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.",1370851448,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rhsntkwc7ofl6qzz7kt4,task_subcomment,NA
+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",1370056740,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_description,resolved
+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.,1370467182,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+Piping used unnecessarily when modifying an existing link,https://gerrit.wikimedia.org/r/66880 (Gerrit Change I6abef05522192f667d483b4eb4e05de771496c28) | change APPROVED and MERGED [by jenkins-bot],1370467094,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+Piping used unnecessarily when modifying an existing link,Related URL: https://gerrit.wikimedia.org/r/66880 (Gerrit Change I6abef05522192f667d483b4eb4e05de771496c28),1370297438,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+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.",1370295580,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+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
+<a rel='mw:WikiLink' href='./Foo' data-parsoid='{""a"":{""href"":""./Foo""},""sa"":{""href"":""Foo""},""stx"":""simple""}'>Foo</a>
+<a rel=""mw:WikiLink"" href=""./Foo"" data-parsoid='{""a"":{""href"":""./Foo""},""sa"":{""href"":""Foo""},""stx"":""piped""}'>Foo</a>
+[subbu@earth lib] node parse --html2wt < /tmp/x
+[[Foo]]
+[[Foo|Foo]]",1370294863,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-2h7j3etzcjrazlrx7t2k,task_subcomment,NA
+"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",1369958460,PHID-USER-kc6qx3zohjybu3nzffu3,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_description,resolved
+"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).",1393380862,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",Is there anything left to do here?,1390957000,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1378356950,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1378325288,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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.",1378325065,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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 ?",1376398189,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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.",1376398041,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",Now fixed and deployed.,1375423076,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375414268,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375401594,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375397553,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375395744,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1375395639,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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.",1375394378,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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 ),1374948629,PHID-USER-myojicphhrv5eiqtoq52,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1374804903,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"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",1374515509,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+"VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?",--> VisualEditor,1370441741,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-n3tckyz3ypiasbv7mmov,task_subcomment,NA
+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",1369942140,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-3ovbcuxkngbjxrroevib,task_description,resolved
+VisualEditor: Formatting styles drop down menu rendered behind the page title,*** Bug 49430 has been marked as a duplicate of this bug. ***,1370970446,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ovbcuxkngbjxrroevib,task_subcomment,NA
+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.,1370632871,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ovbcuxkngbjxrroevib,task_subcomment,NA
+VisualEditor: MWTemplateDialog should visually distinguish between wikitext and template name,"Screenshot while editing template with wikitext-generated target
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F11029}",1369920600,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-caprohhe57u5cvvih5r4,task_description,duplicate
+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: <foo>"" rather than just ""<foo>""? Making the name italics?",1369926881,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-caprohhe57u5cvvih5r4,task_subcomment,NA
+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",1369888320,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-2qamjq3crlikvr3nahtr,task_description,resolved
+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.,1372007590,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2qamjq3crlikvr3nahtr,task_subcomment,NA
+VisualEditor: Cut-Paste of paragraphs seems broken in Firefox,Firefox 21.0,1370319799,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-2qamjq3crlikvr3nahtr,task_subcomment,NA
+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.",1369904030,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2qamjq3crlikvr3nahtr,task_subcomment,NA
+VisualEditor: Make ve.dm.Transaction chainable,"tx push
+tx push
+tx push
+tx push
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369777440,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lsb2vshfs5s363qn5xmf,task_description,declined
+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",1369760400,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_description,resolved
+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]]",1487999288,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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]]
+",1487969442,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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 #.",1439831900,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw,This has been deployed.,1418855804,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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]]",1418149485,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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",1417716645,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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",1414795698,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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.,1411654695,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1374161731,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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,1374106464,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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.",1374075574,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1374074905,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1373852602,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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,1373646156,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1373646127,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1373590970,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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],1372934117,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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. ***,1372104211,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+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.",1371782235,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-mmm6poefxi4xoohquyi4,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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}",1369744440,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_description,resolved
+Parsoid should support <translate> and <tvar> 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.",1451432369,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Change 261293 merged by jenkins-bot:
+T50891: Register <translate> and <tvar> natively
+
+[[https://gerrit.wikimedia.org/r/261293]]",1451423865,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Change 261293 had a related patch set uploaded (by Arlolra):
+T50891: Register <translate> and <tvar> natively
+
+[[https://gerrit.wikimedia.org/r/261293]]
+",1451345650,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1449004296,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,Any update on this?,1448940120,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Since <translate> 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 <translate> 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.",1422567418,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> 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.,1422482506,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> 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.",1422112321,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1412577526,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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*.",1399802210,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1399802137,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,No patch any more. :-(,1399715908,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1397663477,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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
+> > <translate> 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:
+<h2><span class=""mw-headline"" id=""Culture"">Culture</span><mw:editsection page=""Pupu"" section=""1"">Culture</mw:editsection></h2>
+
+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?",1382781712,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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
+> <translate> 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.",1382742193,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,Editing translatable pages via API seems to work now.,1382609272,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1382609061,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Issues I have found:
+
+* [MAJOR] Disabling edit section links does not work for headings inside <translate> 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.",1382608843,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1382608576,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 = '~<tvar\|([^>]+)>(.*?)</>~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.",1382602468,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"**gmaruzz** wrote:
+
+bump",1382525422,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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=<translate>foo</translate> works and does not crash.
+
+https://meta.wikimedia.org/w/api.php?action=parse&text=<translate><!--T:1-->foo</translate> 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.",1382026260,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1382022809,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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?",1381997259,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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?",1381334518,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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).",1381334222,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> and <tvar> 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 <translate> and <tvar> relies on), and that will bomb.
+
+One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",1381332394,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> and <tvar> 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.",1381331649,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.,1381311581,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 ""<translate> and <tvar>""",1381308196,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"That patch won't work well with Parsoid, see the comment in the patch set.",1381173268,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,I don't deserve the credit for Niklas's fix. :-),1381161087,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1380976648,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1380973744,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,I think I already did it yesterday.,1380972312,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1380903233,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1380870838,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1380324098,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1378773198,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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?",1378772376,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,"Niklas: If VE has to support editing for <translate>, <tvar>, 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.",1378754413,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.,1378751046,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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",1378750854,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,Ping.,1377214396,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.,1375385299,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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.",1375380363,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,@Niklas are there issues with registering them?,1375380132,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,*** Bug 52408 has been marked as a duplicate of this bug. ***,1375378489,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate>, <tvar>, <language> 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.",1375378361,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> natively as they are not normal parser tags,<translate> and <tvar> are not a normal extension tags. Please explain why I should register them.,1369809699,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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/<ext-name-here> 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.",1369765885,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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/<ext-name-here> type. All other unknown tags are pass through as plain text.
+
+The problem is that mediawiki does not report <translate> 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 <translate> as a registered extension?",1369761569,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+Parsoid should support <translate> and <tvar> 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 <translate> 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?",1369745248,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jpmjmzcf4crsjhqwquzp,task_subcomment,NA
+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",1369733100,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_description,declined
+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.",1551737186,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_subcomment,NA
+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'.",1404778634,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_subcomment,NA
+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
+} );",1404777075,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_subcomment,NA
+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.",1369734288,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4vzkkpi6vnpbfv2eknxj,task_subcomment,NA
+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",1369598340,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-cxhnj4waa436ovh4o7lz,task_description,resolved
+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.",1372007435,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cxhnj4waa436ovh4o7lz,task_subcomment,NA
+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 </small> 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",1369561740,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-c3wc4a6vunygqboimdkx,task_description,resolved
+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.",1642380960,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-c3wc4a6vunygqboimdkx,task_subcomment,NA
+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.",1371986974,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-c3wc4a6vunygqboimdkx,task_subcomment,NA
+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 <b> tags. Currently it fails compare custom attributes like ""style"" when attempting to merge equal annotation sequences.",1371986731,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-c3wc4a6vunygqboimdkx,task_subcomment,NA
+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.,1371986436,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-c3wc4a6vunygqboimdkx,task_subcomment,NA
+VisualEditor: Write test cases for ElementLinearData#getAnnotationIndexesFromOffset,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369560000,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7lzwyjbh5q62jpz2njvq,task_description,open
+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",1369423680,PHID-USER-ea6gwat27oulytc5tvsy,False,PHID-TASK-ftjpfhlr3dsluwcrrpaa,task_description,resolved
+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.,1372007371,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ftjpfhlr3dsluwcrrpaa,task_subcomment,NA
+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}",1369425726,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-ftjpfhlr3dsluwcrrpaa,task_subcomment,NA
+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",1369411380,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-jzom4aa22nn3mtwtm74t,task_description,resolved
+VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),Now tracked in #VisualEditor-MediaWiki-Links instead.,1422402760,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+VisualEditor: Improvements and  behaviour changes to the link input widget (tracking),*** Bug 57716 has been marked as a duplicate of this bug. ***,1395197341,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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.,1378765753,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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.""",1375961000,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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]].",1375212875,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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)",1375181899,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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),1373539718,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+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.",1371118580,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-jzom4aa22nn3mtwtm74t,task_subcomment,NA
+"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 <template> tags or any of the special attributes/types found on http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec
+
+If Parsoid doesn't detect these and escape/handle them somehow, Parsoid will mislead clients like VisualEditor and/or incorrectly serialize them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369392240,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-e53ehyegovylp4gigsvo,task_description,open
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","One more thing that would be good to fix:
+
+Currently, the tokenizer unconditionally escapes typeof and about attributes to data-x-typeof and data-x-about. But, if RDFa attrs from wikitext will also get escaped in this manner. Not sure if RDFa is actually used in wikitext, but that support does exist in MW. So, the escaping could be refined to leave alone any typeof and about attrs that wont confuse Parsoid and clients.
+
+Related FIXME comments from the sanitizer (ext.core.Sanitizer.js) from https://gerrit.wikimedia.org/r/#/c/81569/ that I am pasting here:
+```
+// SSS FIXME: There is a test in mediawiki.environment.js that doles out
+// and tests about ids. There are probably some tests in mediawiki.Util.js
+// as well. We should move all these kind of tests somewhere else.
+----
+// Bypass RDFa/whitelisting checks for Parsoid-inserted attrs
+// Safe to do since the tokenizer renames about/typeof attrs.
+// unconditionally. FIXME: The escaping solution in tokenizer
+// maybe aggressive. There is no need to escape typeof strings
+// that or about ids that don't resemble Parsoid types/about ids.
+```
+
+Any fix made here should also verify that the sanitization code in sanitizeTagAttrs properly strips dangerous values from unescaped typeofs even when Parsoid updates them with parsoid typeofs.
+
+```
+Ex: <tag typeof=""dangerous-text"">..</tag> gets updated by Parsoid parser to <tag typeof=""mw:ParsoidTypeof dangerous-text"">..</tag> which should then be handled by the sanitizer to yield <tag typeof=""mw:ParsoidTypeof"">...</tag>
+```",1421187810,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","One more thing that would be good to fix:
+
+Currently, the tokenizer unconditionally escapes typeof and about attributes to data-x-typeof and data-x-about. But, if RDFa attrs from wikitext will also get escaped in this manner. Not sure if RDFa is actually used in wikitext, but that support does exist in MW. So, the escaping could be refined to leave alone any typeof and about attrs that wont confuse Parsoid and clients.
+
+Related FIXME comments from the sanitizer (ext.core.Sanitizer.js) from https://gerrit.wikimedia.org/r/#/c/81569/ that I am pasting here:
+
+----
+// SSS FIXME: There is a test in mediawiki.environment.js that doles out
+// and tests about ids. There are probably some tests in mediawiki.Util.js
+// as well. We should move all these kind of tests somewhere else.
+----
+// Bypass RDFa/whitelisting checks for Parsoid-inserted attrs
+// Safe to do since the tokenizer renames about/typeof attrs.
+// unconditionally. FIXME: The escaping solution in tokenizer
+// maybe aggressive. There is no need to escape typeof strings
+// that or about ids that don't resemble Parsoid types/about ids.
+----
+
+Any fix made here should also verify that the sanitization code in sanitizeTagAttrs properly strips dangerous values from unescaped typeofs even when Parsoid updates them with parsoid typeofs.
+
+Ex: <tag typeof=""dangerous-text"">..</tag> gets updated by Parsoid parser to <tag typeof=""mw:ParsoidTypeof dangerous-text"">..</tag> which should then be handled by the sanitizer to yield <tag typeof=""mw:ParsoidTypeof"">...</tag>",1378248584,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","Patch landed as suggested in comment 5. However, Subbu mentioned that, ""we still need to deal with complexity that templates bring.""
+
+Ex: <div {{echo|about}}=""foo"">bar</div>",1375117004,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","Change 74586 merged by jenkins-bot:
+Protect Parsoid-generated attributes.
+
+https://gerrit.wikimedia.org/r/74586",1374946962,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","Or we could write a DOM postprocessor stage that was a bit smarter about which RDFa it unwrapped.  ie, it would unwrap the first example from comment 5, but not the final example there, since it would be able to see that there's parsoid RDFa inside the div which would be broken.  Or other options.",1374529924,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","If we do go that route, the fixup for rendering would have to be in client-side JS since we may not use different cached content for editing vs rendering -- or so it seems to me at this time without any sense of how user RDFa markup will need to be supported in MW content.",1374529662,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","[Discussed this on IRC with subbu]
+
+To support case 3 from comment 1 and 2, rather than *strip* the attributes, I suggest encapsulating them instead.  For example, if the user authors:
+
+<div about=""http://dbpedia.org/resource/Albert_Einstein"" typeof=""foaf:Person"">
+  <span property=""foaf:name"">Albert Einstein</span>
+  <span property=""foaf:givenName"">Albert</span>
+</div>
+
+..instead of stripping the RDFa, we're just going to rename the attributes, to:
+
+<div data-user-about=""http://dbpedia.org/resource/Albert_Einstein"" data-user-typeof=""foaf:Person"">
+  <span data-user-property=""foaf:name"">Albert Einstein</span>
+  <span data-user-property=""foaf:givenName"">Albert</span>
+</div>
+
+That ensures that the user content is safe for Parsoid and VE to manipulate.  In the future we can re-enable the RDFa in the output with a DOM post-processing (""render"") pass.  For example, the user content:
+
+<div about=""http://dbpedia.org/resource/Albert_Einstein"" typeof=""foaf:Person"">
+{{Albert Einstein}}
+</div>
+
+might have all sorts of Parsoid RDFa markup inside the {{Albert Einstein}} expansion, which the about=""http://dbpedia.org/resource/Albert_Einstein"" attribute would screw up the context for.  But for rendering to the web, the Parsoid cruft could be elided and the user's RDFa markup unwrapped.",1374529246,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","Change 74586 had a related patch set uploaded by Arlolra:
+Protect Parsoid-generated attributes.
+
+https://gerrit.wikimedia.org/r/74586",1374213999,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.",[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934056,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","1) Is not an issue, as prefix is  not allowed in the PHP sanitizer (and not in our sanitizer either).
+
+2) Is something for later. The risk here is mainly crashes during serialization.
+
+3) Should be supported. We only want to protect our own values where necessary. The typeof attribute for example is multi-valued, so we only need to strip mw:-prefixed user-supplied values. The about attribute on the other hand is single-valued, so we need to override user-supplied values unconditionally where necessary.",1371511977,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.","There are three interconnected issues:
+1)
+  <span prefix=""mw: http://evil.bad"">
+is valid wikitext, which would create malformed Parsoid DOM.  We should sanitize the wikitext (but that has to happen *before* we create the DOM, since otherwise we can't tell which prefix attributes are good and which are evil.)
+
+2) VE needs to prevent users from authoring content which sets prefix attributes, etc.  Currently it does so, but it would be nice to make Parsoid more robust against malformed DOM, and/or to add layers of protection so that front ends aren't solely responsible for sanitizing user input.
+
+3) Longer term we should probably think about use cases where the user wants to deliberately author RDFa markup on their content, and ensure that they are able to do so in a safe way.
+
+This bug is primarily about #1 (the short term issue) and I'll tackle it tomorrow.",1371511478,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-e53ehyegovylp4gigsvo,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","On my user page https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29 and now on a test page https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29/VE_bugs every time I try to add a new section VE goes haywire
+
+1. Edit (with VE)
+2. Click at start of first heading (""welcomecreation..."")
+3. Press Enter, it prepends new heading (good)
+4. Press up arrow to move up to this new blank heading.
+5. Start typing the heading, e.g. press 'X'
+6. That was wrong, so press Backspace (or left arrow)
+
+Result:
+The text of the heading underneath leaps above the new heading, joining text above it.
+I can edit other parts of the document, but whenever I return to my new heading to add or backspace, the caret jumps elsewhere.
+If I undo enough times, VE undoes to a state where the new header displays below the existing header. The document looks different to what it did before, but [Review and save] is grayed out.
+
+I created a new document https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29/VE_bugs and similar stuff happens in that.
+
+This is in Firefox 21 on Ubuntu, and mediawiki.org's VE as of today.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369264200,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-pds66u5f24d37usiicgj,task_description,resolved
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one",This should now be fixed; we will push this to production this afternoon.,1372370158,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","Change 70864 merged by jenkins-bot:
+Don't advance cursor when adding new line at start of node
+
+https://gerrit.wikimedia.org/r/70864",1372368223,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","Change 70918 merged by jenkins-bot:
+If cursor is obscured by toolbar, on keypress scroll to cursor.
+
+https://gerrit.wikimedia.org/r/70918",1372368220,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","Change 70918 had a related patch set uploaded by Robmoen:
+If cursor is obscured by toolbar, on keypress scroll to cursor.
+
+https://gerrit.wikimedia.org/r/70918",1372366669,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","Change 70864 had a related patch set uploaded by Robmoen:
+Don't advance cursor when adding new line at start of node
+
+https://gerrit.wikimedia.org/r/70864",1372359928,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","(In reply to comment #5)
+> Sounds good, though I note it's different than e.g. pressing Enter at the
+> start of the first of a set of bullet points, which adds another bullet rather
+> than a plain paragraph. A foolish consistency is the Hobnobs of little minds :)
+
+Yeah, I've been wondering whether to make these consistent for a little bit.",1371520609,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","(In reply to comment #4)
+> (In reply to comment #3)
+> > * If you press Enter with the caret at start of heading, you get a plain
+> > paragraph before (maybe OK but not what I'd expect and not how most WYSIWYG
+> > editors work)
+> 
+> This is intentional - if you have header 1\nheader 2\nheader 3\n and click
+> before header 3 and press return, you should be able to type content
+> (paragraph) by default.
+
+Sounds good, though I note it's different than e.g. pressing Enter at the start of the first of a set of bullet points, which adds another bullet rather than a plain paragraph. A foolish consistency is the Hobnobs of little minds :)",1371520249,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","(In reply to comment #3)
+> These days the behavior on mediwiki.org (with Firefox 21.0 Ubuntu 13.04) is
+> different and a little better.
+> * If you press Enter with the caret at start of heading, you get a plain
+> paragraph before (maybe OK but not what I'd expect and not how most WYSIWYG
+> editors work)
+
+This is intentional - if you have header 1\nheader 2\nheader 3\n and click before header 3 and press return, you should be able to type content (paragraph) by default. WYSIWYG editors often get this wrong, thinking that context is the most important thing, because they don't know what style ""normal"" content is. We do, and so we should do this right. (Also, VE isn't intending to be a WYSIWYG editor, just a visual one that is more and WYSIWYM editor at times.)
+
+> * The caret moves between the first and second character of the heading
+> (definitely wrong).
+
+Yeah, sorry about that; we should get that fixed soon.",1371504819,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","These days the behavior on mediwiki.org (with Firefox 21.0 Ubuntu 13.04) is different and a little better.
+* If you press Enter with the caret at start of heading, you get a plain paragraph before (maybe OK but not what I'd expect and not how most WYSIWYG editors work)
+* The caret moves between the first and second character of the heading (definitely wrong).
+But the document doesn't get out of order, your typing always appears at the caret, and what you see is what is saved. Progress!",1371501393,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","**brassratgirl** wrote:
+
+I'm getting a similar bug while trying to edit a userpage subpage, with the addition that it's blanking out the existing text. See https://en.wikipedia.org/wiki/User:Phoebe/chopo
+
+1) edit existing text, all is fine. 
+2) move cursor below existing paragraph, attempt to type new heading
+3) cursor jumps to above existing paragraph, types up there
+4) this results in uneditable blank spaces 
+5) and, on save, all text below blank spaces is gone. 
+
+My conclusion is that editing user pages is, for whatever reason, totally haywire. I have screenshots if needed. 
+
+Firefox 20.0 on Ubuntu 12.04",1369610854,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+"VisualEditor: Return at start of header causes cursor to move two characters down-page, not one","In Chromium (25.0.1364.160 Ubuntu 13.04) not logged in, the same step 3 adds blank line above (not styled as a heading) and moves the caret to the second character in the existing heading.",1369264433,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-pds66u5f24d37usiicgj,task_subcomment,NA
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,"On wikis where certain ""topicons"" are moved out of the mw-content-text wrapper into the root of #content the VisualEditor toolbar shows a weird blank space.
+
+The icons in question are invisible due to float overlap, but they do push down the toolbar and occupying space to the right of the ""Save and review"" button thus pushing it and the rest of ve-ui-toolbar-actions to the left.
+
+To reproduce this situation, run the following one or more times:
+
+    $('#content').prepend(
+        '<div class=""mw-topicon"" style=""display: block; width: 20px; height: 20px; background: pink; float: right; margin-left: 3px;"">x</div>'
+    );
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369263840,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nmn7dlmg7l34754u4bwb,task_description,resolved
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,Related URL: https://gerrit.wikimedia.org/r/64989 (Gerrit Change Ic5f73ac1eb8c41b891dd1c67b71795cb6c456141),1369264080,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nmn7dlmg7l34754u4bwb,task_subcomment,NA
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,"Created attachment 12375
+What it looks like with clear:both patch applied
+
+The icons become visible again and the actions toolbar (right hand side of the toolbar) is no longer pushed to the left but flush to the right again.
+
+**Attached**: {F10554}",1369264016,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nmn7dlmg7l34754u4bwb,task_subcomment,NA
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,"Created attachment 12374
+Current misalignment when there are extra elements in #content
+
+Such as the case currently on https://de.wikipedia.org/wiki/Berlin
+
+**Attached**: {F10553}",1369263963,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nmn7dlmg7l34754u4bwb,task_subcomment,NA
+VisualEditor: Toolbar should clear float to avoid misalignment by extra elements,"Created attachment 12373
+What the toolbar usually looks like
+
+Note absence of space between the Vector tabs and the toolbar, and the Save button is flush to the right.
+
+**Attached**: {F10552}",1369263925,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nmn7dlmg7l34754u4bwb,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"If you have some text with an annotation (e.g. bold, italics or a link) and copy in some text, the annotation is closed off, the text is insert as plain text, and then the annotation is restarted.
+
+I think users will expect ""paste as current style"" over ""paste as plain text"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369247880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_description,resolved
+VisualEditor: Paste of content does not use the context's annotation,"This seems to work as expected these days. I just tried pasting various annotated things into various other things, and everything behaves fine, with the annotations being merged. 
+
+https://en.wikipedia.org/w/index.php?title=User:Matma_Rex/sandbox&diff=773983701&oldid=773982287
+{F7268038}
+
+(Although in the meantime I discovered we're //too// good at this, merging some annotations that don't make sense, see {T162278}.)",1491408734,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"I definitely expect that text pasted into the middle of a link will still be part of the link.  `[[Link|Li]]HardToType[[Link|nk]]` is never what I want, and if you end up with that, it's hard to repair (unlike a missing or extra bit of bold text).  Since the {T130735} in Safari, then ""just (magically know about and remember to) use plain-paste"" isn't a viable solution.",1458752469,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,*** Bug 69653 has been marked as a duplicate of this bug. ***,1408272633,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,Normal paste (rich paste) should preserve the formatting of the pasted content (even if that means plain). Plain text paste should take the formatting of the target.,1381156824,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"erm, yes. Sorry.",1374776898,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"(In reply to comment #3)
+> An editor at the English Wikipedia comments that the ability to copy and
+> paste
+> a link is "" definitely not an [sic] luxury feature but core functionality.""
+> 
+> I am inclined to agree.
+
+That's presumably meant for bug 33105 which is about copying and pasting rich content, rather than this one?",1374775928,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"An editor at the English Wikipedia comments that the ability to copy and paste a link is "" definitely not an [sic] luxury feature but core functionality.""
+
+I am inclined to agree.",1374767136,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,"LibreOffice uses additive annotations, so pasting italic text into bold text results in bold+italic text. Google drive uses our current functionality.",1369294390,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Paste of content does not use the context's annotation,*** Bug 48159 has been marked as a duplicate of this bug. ***,1369247921,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ezht24x5cf4eytaekvqk,task_subcomment,NA
+VisualEditor: Clicking Notices button or closing its dialog scrolls user back to the top,"Whenever you're scrolled down in a document and close or re-open the Notices flyout, the user is brought back to the top of the page (instead of staying where they are, like any other toolbar button would).
+
+The toolbar floats and follows the user as they view the document, it is expected that interacting with it does not change the scroll offset. Most buttons abide by this except for Notices.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369144860,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7jfh3i424pezp3um3zzy,task_description,resolved
+VisualEditor: Clicking Notices button or closing its dialog scrolls user back to the top,This is now fixed.,1370972881,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7jfh3i424pezp3um3zzy,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"The newsletter update states that Visual Editor is now functioning in the content namespaces at MW, which includes the extension: and manual: namespaces (and it does).  That said, the default text for ""MediaWiki:Visualeditor-preference-enable"" just states user and main at that wiki. I am presuming that this is a WikimediaMessages update somewhere
+
+As a temporary measure I have created [[mw:MediaWiki:Visualeditor-preference-enable]] that mentions the extra two namespace.
+
+As a note the mention of {{MediaWiki:Visualeditor-extensionnamespacepagelink}} and {{MediaWiki:Visualeditor-manualnamespacepagelink}} failed, so I didn't link, and we will need to look to how these extra namespaces are going to be linked, and documented.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369100100,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_description,resolved
+Mediawikiwiki: Make VisualEditor a hidden preference,"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",1374826591,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"Change 73565 had a related patch set uploaded by Helder.wiki:
+(bug 50929) Remove 'visualeditor-enable' from $wgHiddenPrefs
+
+https://gerrit.wikimedia.org/r/73565",1374499697,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"Then someone opened Bug 50929 - User preference to disable VisualEditor
+
+The related change is  https://gerrit.wikimedia.org/r/#/c/73565/
+
+
+That effectively would reopen this bug 48666.",1374499317,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"(In reply to comment #8)
+> my intention was not to offend or attack, it was to draw attention that, to
+> the best of my understanding, hiding the user option did not actually address
+> the actual bug.
+
+The 'actual' bug was, effectively, that ""the temporary description of a temporary configuration option does not automatically expand based on a different configuration variable's setting"".
+
+However, the cause for complaint was ""the temporary description of a temporary configuration option on MW.org is wrong and confusing"", you are correct.
+
+> i think that bug 51411 you created is perfect, and once it's fixed/addressed,
+> everything will be fine.
+
+It's exceedingly unlikely to be addressed, because (a) programmatic writing of human-readable descriptions is very delicate and not something we generally do, and (b) as we have said a great many times, this is about a configuration variable that exists purely for the duration of the alpha, to provide a way to ""opt in"". Availability of VE is a system-level configuration, not a user-level preference. By the time the software is actually marked for release by anyone outside WMF (when we remove the ""here be dragons"" labels), the underlying issue will be moot.",1373987046,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"my intention was not to offend or attack, it was to draw attention that, to the best of my understanding, hiding the user option did not actually address the actual bug.
+
+i think that bug 51411 you created is perfect, and once it's fixed/addressed, everything will be fine.
+
+regarding the rewording of the synopsis: i am aware that it's common practice. actually, quite a few of the bugs i opened myself received this treatment. 
+in all the cases i can recall, the rewording was for the better. 
+my complain was not about the fact the synopsis was reworded, per se, but rather about the new description, which i do not think is a good one. 
+
+
+regarding my presumption: i am not sure if i understand your comment about this bug being specific to ""mediawiki.org"". 
+does this mean it's limited to wikimedia projects? if this is what you mean, i do not think you are correct. 
+this issue (the original one, that is) pertains to any wiki that uses the mediawiki software with visualeditor (new synopsis and your fix not withstanding).
+
+peace.",1373986460,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"(In reply to comment #6)
+> (In reply to comment #2)
+> > Simplest solution to this problem. :-)
+> 
+> an excellent case where ""simplest"" is very far from ""correct"" or ""best"".
+
+I disagree.
+
+> in addition to being a bad solution, this change only affects enwiki,
+
+Not true.
+
+> while the (original) bug is generic to all projects that install VE (and
+> even non-projects, i.e., ""3rd party"" wikis).
+
+The message is over-rideable, which is an entirely-adequate solution for most third parties. The initial request was, in my opinion, asking for a solution that didn't require a local over-ride, and met the intent of the team anyway (as part of removing VisualEditor as a local user preference, which was temporarily implemented for the opt-in alphas and is going away).
+
+> as a side, together with this wrong and bad solution, James Forrester also
+> changed the synopsis of the bug: from the original (""underlying text for
+> VisualEditor in preferences [editing] tab & variable names?""), to ""Make
+> VisualEditor a hidden preference"", i.e., instead of outlining the problem,
+> the bug synopsis now spells the ""solution"".
+
+This is perfectly standard practice here.
+ 
+> this is wrong on several levels: it creates the impression that the bug
+> originator (billinghurst) asked to hide the preference, which he didn't, of
+> course,
+
+Again, this is normal; comment 0 is the location to find what the originator wanted.
+
+> and it hides the actual problem from someone reading this bug - only
+> by digging in the history i was able to make sense of Comment #1, which looks
+> now completely disjoint from the bug synopsis.
+
+I'm sorry that you were confused.
+
+> wrong or bad solutions to problems is something that can and does happen in
+> every project. that's just life. 
+> changing the synopsis the way it was changed is not something that can or
+> should happen.
+
+I strongly disagree.
+
+> without digging too deeply, i'm going to revert the synopsis to the original
+> one, and reopen -
+
+Which I have reverted, and opened a new bug, bug 51411, for your concerns.
+
+> presuming the problem affects more then just enwiki
+
+Your presumption is wrong. Note that the title you over-ride explicitly mentioned ""Mediawikiwiki"" (i.e., MediaWiki.org).",1373933935,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"(In reply to comment #2)
+> Simplest solution to this problem. :-)
+
+an excellent case where ""simplest"" is very far from ""correct"" or ""best"".
+
+in addition to being a bad solution, this change only affects enwiki, while the (original) bug is generic to all projects that install VE (and even non-projects, i.e., ""3rd party"" wikis).
+
+as a side, together with this wrong and bad solution, James Forrester also changed the synopsis of the bug: from the original (""underlying text for Visual editor in preferences [editing] tab & variable names?""), to ""Make VisualEditor a hidden preference"", i.e., instead of outlining the problem, the bug synopsis now spells the ""solution"". 
+this is wrong on several levels: it creates the impression that the bug originator (billinghurst) asked to hide the preference, which he didn't, of course, and it hides the actual problem from someone reading this bug - only by digging in the history i was able to make sense of Comment #1, which looks now completely disjoint from the bug synopsis.
+
+wrong or bad solutions to problems is something that can and does happen in every project. that's just life. 
+changing the synopsis the way it was changed is not something that can or should happen.
+
+without digging too deeply, i'm going to revert the synopsis to the original one, and reopen - presuming the problem affects more then just enwiki, and also, with the hope that Bug 50929  (basically a request to undo this change) will be fixed soon.
+
+peace.",1373914200,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,Now done.,1372715431,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"Change 70652 merged by jenkins-bot:
+Make 'visualeditor-enable' pref hidden on wikis where VE is default
+
+https://gerrit.wikimedia.org/r/70652",1372714295,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,Related URL: https://gerrit.wikimedia.org/r/70652 (Gerrit Change Ica186b9374ddaa0f2f6b2a84e5dff851011b68a4),1372265133,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,Simplest solution to this problem. :-),1369159470,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Mediawikiwiki: Make VisualEditor a hidden preference,"(In reply to comment #0)
+> The newsletter update states that Visual Editor is now functioning in the
+> content namespaces at MW, which includes the extension: and manual:
+> namespaces (and it does).  That said, the default text for
+> ""MediaWiki:Visualeditor-preference-enable"" just states user and main at that
+> wiki.
+
+It probably shouldn't default to saying only some namespaces and not changing when the wiki config adds it to other namespaces. Moving this bug to the VisualEditor product.",1369156791,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-q322vvsm62gyx2idxtx2,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"{{foo}} -> Template:Foo
+{{:foo}} -> foo
+{{:user:Foo}} -> User:Krinkle
+{{Template:foo}} -> Template:Foo
+etc.
+
+VisualEditor needs the name of the page that ends up being transcluded by the template invocation.
+
+From conversation with Gabriel I gather that currently the entire tranclusion system (at least in production) is deferred to the PHP parser (including the invocation itself). Which means Parsoid is unable to determine it itself right now.
+
+Gabriel suggested Parsoid will provide the name the best it can for simple cases that don't dynamically construct the page name (e.g. not something like:
+ {{ {{getTemplateName|x=foo}} | bar }}
+).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369093620,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_description,resolved
+Parsoid: DOM for template objects should expose template name,https://gerrit.wikimedia.org/r/65622 (Gerrit Change I3b2fbf3b533b14680d2b881ac9fb43218d4f023a) | change APPROVED and MERGED [by jenkins-bot],1370460530,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"Latest proposal that is now pending review and merge (based on discussions on IRC).
+
+All transclusions now have ""mw:Transclusion"" typeof.
+
+data-mw.target.href will point to the template source page, if the template target is known statically.  Will not be set set if target is templated.
+
+data-mw.target.function will provide the name of the parser-function/magic-word, if the function target is known statically.  Will not be set otherwise.",1370456625,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,Related URL: https://gerrit.wikimedia.org/r/65622 (Gerrit Change I3b2fbf3b533b14680d2b881ac9fb43218d4f023a),1369577963,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"Given that transclusion targets can be dynamic ({{ {{echo|lc}}:FOO}} and such), it wont be possible to always provide a statically determined tpl/pf target.  In the general case, the user shouldn't be editing parameters for these dynamic cases without knowing that the tpl. target is specific to the current editing session and arbitrary editing of the parameters might break the transclusion in other scenarios (day-of-week or month-of-year based selection of tpl targets).
+
+So, if we cannot always provide the template or parser function target, it seems we shouldn't add that to the typeof field and leave the typeof as: ""mw:Object/Transclusion/Template"" or ""mw:Object/Transclusion/ParserFunction"" and rely on the data-mw.target json property to communicate info about the target (fully resolved url, if static OR html with transclusion wrappers, if templated).",1369480864,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"https://en.wikipedia.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=functionhooks doesn't expose the flag.
+
+We were thinking of replacing mw:Object/Template with mw:Object/Transclusion to make it clear that the object being annotated is a transclusion.  We want to retain a Transclusion type so all transclusions can be recognized for those cases where you dont need to distinguish between types.  But, I suppose we could make this: ""mw:Object/Transclusion/Template"" or ""mw:Object/Tranclusion/ParserFunction"".  Right now, the target is not part of this, since this is a type but we are being inconsistent since extensions provide the target name as part of the typeof.  So, we should probably make all those typeofs consistent in some way.
+
+Since this is not necessary for July, let us take a bit more time to work through these (and any other) details rather than make a quick fix.",1369475889,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"(In reply to comment #7)
+> We were just looking at the wiki config to see if we can recognize something
+> as
+> a parser function (instead of a template) and ran into trouble:
+> 
+> * Looks like parser functions usage comes in 2 flavours: (a) with the
+> #-prefix:
+> ex: {{#if ..}}, etc. (b) without the #-prefix: ex: {{lc:...}}
+> * config.functionhooks provides a list of parser functions, but that list
+> doesn't distinguish between (a) and (b) above.  So, the functionhooks list
+> has
+> an entry for ""lc"" and an entry of ""if"" (not #if).
+> 
+This is controlled by the SFH_NO_HASH flag in CoreParserFunctions.php. Is this flag not exposed in config.functionhooks?
+
+> If
+> knowing that something is a parser function is essential for VE, then we
+> could
+> implement this check and maybe add a flag in data-mw or add some other way of
+> marking up a parser function.  data-mw.target.isPF = true possibly?
+It's not essential for July, but it's required in order to be able to support Wikidata editing. For that purpose, we'd like for parserfunctions to be marked as something like typeof=""mw:Object/ParserFunction/#if"" , as opposed as a template with a special data-mw bit (we could deal with the latter too, but the former would be much more convenient).",1369473754,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"We were just looking at the wiki config to see if we can recognize something as a parser function (instead of a template) and ran into trouble:
+
+* Looks like parser functions usage comes in 2 flavours: (a) with the #-prefix: ex: {{#if ..}}, etc. (b) without the #-prefix: ex: {{lc:...}}
+* config.functionhooks provides a list of parser functions, but that list doesn't distinguish between (a) and (b) above.  So, the functionhooks list has an entry for ""lc"" and an entry of ""if"" (not #if).
+
+So, ostensibly we could have tested if (a) the name starts with a # in which case it is a parser function; OR (b) the name (lc/if/padleft) is present in config.functionhooks.
+
+But (b) gets us into trouble because you also have templates like ""if"".  So, {{if...}} ought to be treated as a template and not a parser function.
+
+We could then use an additional check to see if there is a "":"" in the name to distinguish between {{lc:foo}} and {{lc|foo}}.
+
+This could work, but seems a bit hacky and maybe fragile wrt edge cases. If knowing that something is a parser function is essential for VE, then we could implement this check and maybe add a flag in data-mw or add some other way of marking up a parser function.  data-mw.target.isPF = true possibly?",1369471610,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"This looks sane to me, and won't change much with the url patch. Transclusions are all treated the same in Parsoid. Would you like us to split on the colon and provide a special-case 0th parameter if something looks like a parser function?",1369469460,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"(In reply to comment #4)
+> We are exposing an 'url' format for static targets now. In a follow-up patch
+> we
+> plan to make that editable, and remove the 'wt' value for static targets. For
+> templated targets we will initially still return 'wt', but in the longer term
+> we will expose either 'url' for static targets or 'html' for templated ones.
+So while discussing WikiData integration today, we noticed that parser functions aren't recognized very well. {{#property:capital|of=Germany}} returns {'target':{'wt':'#property:captial'}, 'params':{'of':'Germany'}}
+
+Will this by improved in this URL change you're talking about?",1369404962,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,"We are exposing an 'url' format for static targets now. In a follow-up patch we plan to make that editable, and remove the 'wt' value for static targets. For templated targets we will initially still return 'wt', but in the longer term we will expose either 'url' for static targets or 'html' for templated ones.",1369318288,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,https://gerrit.wikimedia.org/r/64987 (Gerrit Change I3145a4168a2347cecc573dcc07bb4128962a5b11) | change APPROVED and MERGED [by jenkins-bot],1369318124,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,Related URL: https://gerrit.wikimedia.org/r/64987 (Gerrit Change I3145a4168a2347cecc573dcc07bb4128962a5b11),1369254139,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+Parsoid: DOM for template objects should expose template name,Related URL: https://gerrit.wikimedia.org/r/64651 (Gerrit Change Ie0114a81eead86d7a3b3e3a7a5b10d25c457b524),1369099672,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kjq6yunjdamvcihfi3va,task_subcomment,NA
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),"Toolbar in VE floats to position of last BranchNode but should instead just use the bottom of the document or something.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369088700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-djl2633o2ndbnj77h5l2,task_description,resolved
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),Fix merged and will go out with next push.,1371688425,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-djl2633o2ndbnj77h5l2,task_subcomment,NA
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),Related URL: https://gerrit.wikimedia.org/r/69478 (Gerrit Change I1c7662f2b6f1ced6f80dec16c6ed69a8cc0c06c8),1371642471,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-djl2633o2ndbnj77h5l2,task_subcomment,NA
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),"(In reply to comment #1)
+> So the problem is that it lets it go too far or not far enough? I can imagine
+> it somehow, but steps to reproduce the bug would nice.
+
+Doesn't got far enough.
+
+Steps to reproduce: find a document with a very long single BranchNode at the end (or create one). Use VE. Notice that the tool bar slips off the page when you get below the bottom.",1370883741,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-djl2633o2ndbnj77h5l2,task_subcomment,NA
+VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end),"So the problem is that it lets it go too far or not far enough? I can imagine it somehow, but steps to reproduce the bug would nice.",1370851349,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-djl2633o2ndbnj77h5l2,task_subcomment,NA
+VisualEditor: Provide clean way to clone a linmod slice,"Complete with its own sub-store and everything, for consumption by a subsurface.
+
+Right now Trevor is committing crimes against humanity to make this work (converting to DOM then back to linmod again)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369072260,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-g4wwasypneek2xwppnuc,task_description,resolved
+VisualEditor: Provide clean way to clone a linmod slice,Provided by gerrit I38d63e31.,1412608772,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g4wwasypneek2xwppnuc,task_subcomment,NA
+VisualEditor: Provide clean way to clone a linmod slice,ve.dm.Document#cloneSliceFromRange addresses this,1412590792,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-g4wwasypneek2xwppnuc,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs:
+
+1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).
+
+2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.
+
+These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character.
+
+A good start would be to abstract out away calls to string.split( '' ) into a single function like this:
+
+  ve.splitCharacters = function ( value ) {
+      return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs
+  };
+
+The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed.
+
+Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases.
+
+This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369029300,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_description,resolved
+"VisualEditor: Data model needs characters, not code points",Marking this as merged; follow-up in bug 49257.,1370532382,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points",*** Bug 49233 has been marked as a duplicate of this bug. ***,1370531722,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","Ed's main block of code is merged and will go out with wmf5; keeping this open for follow-up, and removing milestone of tomorrow.",1369497594,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes.
+
+The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",1369309137,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points",Related URL: https://gerrit.wikimedia.org/r/64965 (Gerrit Change I8d936fb15d82f73cd45fac142c540a7950850d55),1369248049,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","(In reply to comment #3)
+> Another major issue is that window.getSelection (which is what we use to get
+> cursor position, via Rangy) calculates using number of codepoints, not
+> characters, so this would need to be translated.
+
+Which would be done in ve.ce.getOffsetFromTextNode",1369049395,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","Another major issue is that window.getSelection (which is what we use to get cursor position, via Rangy) calculates using number of codepoints, not characters, so this would need to be translated.",1369048633,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g.
+
+Data: ['F','o','o']
+
+Transaction:
+  Retain: 3
+  Replace:
+    Remove: ''
+    Insert: '<accent>'
+
+Would become:
+
+Transaction:
+  Retain: 2
+  Replace:
+    Remove: 'o'
+    Insert: 'o<accent>'",1369046846,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+"VisualEditor: Data model needs characters, not code points","A related question is when invalid UTF-16 is checked and how errors are handled. 
+
+I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",1369029854,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-vqj7c3uh5ndu4ic45odq,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Toolserver has the local table toolserver.wiki on all databases that provides metadata about the wikis including the server the wiki's database is kept on:
+
+```
+| mysql> SELECT * FROM toolserver.wiki LIMIT 5;
+| +----------------+------+------------+------------------+------+---------+-----------+--------------+--------------+---------------+--------+-------------+
+| | dbname         | lang | family     | domain           | size | is_meta | is_closed | is_multilang | is_sensitive | root_category | server | script_path |
+| +----------------+------+------------+------------------+------+---------+-----------+--------------+--------------+---------------+--------+-------------+
+| | aawikibooks_p  | aa   | wikibooks  | NULL             |    3 |       0 |         1 |            0 |            0 | NULL          |      3 | /w/         |
+| | aawiki_p       | aa   | wikipedia  | NULL             |    6 |       0 |         1 |            0 |            0 | NULL          |      3 | /w/         |
+| | aawiktionary_p | aa   | wiktionary | NULL             |    1 |       0 |         1 |            0 |            1 | NULL          |      3 | /w/         |
+| | abwiki_p       | ab   | wikipedia  | ab.wikipedia.org |  807 |       0 |         0 |            0 |            0 | NULL          |      3 | /w/         |
+| | abwiktionary_p | ab   | wiktionary | NULL             |    0 |       0 |         1 |            0 |            1 | NULL          |      3 | /w/         |
+| +----------------+------+------------+------------------+------+---------+-----------+--------------+--------------+---------------+--------+-------------+
+| 5 rows in set (0.00 sec)
+
+| mysql>
+```
+
+Most of the information can probably be extracted from operations/mediawiki-config, but I don't know which sources there are authoritative.
+
+See also: {T50625}",1369024500,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-6qqicftxiu35fghejuwg,task_description,resolved
+Provide wiki metadata in the databases similar to toolserver.wiki,"Added a meta_p.legacy view that has the same column name and order as toolserver.wiki for legacy purposes.
+
+Please note that the semantics of the 'server' columns differs and there may be other subtle differences with the toolserver's table not immediately evident.  Unless the same code base has to run on both labs and the toolserver for the interval while it still has replication, transitioning to use meta_p.wiki is preferable.",1377719047,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"It would be possible, but probably unhelpful: from what I understand, the server column is numeric whereas I provide actual host names.  Keeping the column named the same with changed semantics seems to be asking for trouble IMO (i.e.: better a select fails than return a string that is misinterpreted as an integer by code with poor error checking).",1377636605,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Would be a problem to rename slice to server, in order to match the column name of toolserver?
+
+The name column looks good to me from a quick look, btw.",1377636490,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"I did not want to rely on the existence of bool, which isn't ANSI; mysql ""helpfully"" translated my numeric(1) to decimal(1,0).",1377636432,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"decimal(1,0) ? This seems strange. Shouldn't those is_* and has_* be BOOL aka. TINYINT(1) ?",1377636291,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"I've added a table with automatically maintained meta information
+about the replicated databases: meta_p.wiki (which is available on every
+shard).
+
++------------------+--------------+------+-----+---------+-------+
+| Field            | Type         | Null | Key | Default | Extra |
++------------------+--------------+------+-----+---------+-------+
+| dbname           | varchar(32)  | NO   | PRI | NULL    |       |
+| lang             | varchar(12)  | NO   |     | en      |       |
+| name             | text         | YES  |     | NULL    |       |
+| family           | text         | YES  |     | NULL    |       |
+| url              | text         | YES  |     | NULL    |       |
+| size             | decimal(1,0) | NO   |     | 1       |       |
+| slice            | text         | NO   |     | NULL    |       |
+| is_closed        | decimal(1,0) | NO   |     | 0       |       |
+| has_echo         | decimal(1,0) | NO   |     | 0       |       |
+| has_flaggedrevs  | decimal(1,0) | NO   |     | 0       |       |
+| has_visualeditor | decimal(1,0) | NO   |     | 0       |       |
+| has_wikidata     | decimal(1,0) | NO   |     | 0       |       |
++------------------+--------------+------+-----+---------+-------+
+
+There is a lingering issue with the 'name' column which seems to
+improperly encode the Wiki name when non-ascii characters are involved;
+that will get fix once I manage to beat some sense into mysql.
+
+Most columns are self-explanatory, and I can add a few more depending on
+demand.  In the meantime, (dbname, slice) provides the much requested
+mapping between databases and slices.",1377636000,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Yes, but you need to populate that table from /somewhere/.  :-)",1373664795,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,API is per wiki. toolserver.wiki is a meta table.,1373651612,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"(In reply to comment #4)
+> In addition, I think we should only rely on MediaWiki's API for this
+> information (with user authentication, as necessary).
+
+This is particularly important in that some extensions may have hard-to-evaluate effect on some configuration values (namespaces and usergroups being the more obvious cases).
+
+I should say that any necessary configuration value that cannot be fetched through the API should be /added/ to the API rather than fetched through an alternative scheme.
+
+-- Marc",1370202628,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"I think we should have a discussion about what the current ""toolserver"" database is, what we want in the future, and whether we care about breaking backward compatibility.
+
+Some of the design decisions in some of the database tables could probably be re-thought, but only if we're willing to break the current interfaces.
+
+In addition, I think we should only rely on MediaWiki's API for this information (with user authentication, as necessary). This is the cleanest and sanest way to accurately get this information, as far as I know.",1370195310,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Do we want a database table consisting of three columns: wiki, config_variable_name, and config_variable_value (as a serialized blob)?",1370194918,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"(In reply to comment #1)
+> Played around with:
+> 
+> | include ($MediaWikiRepoPath . ""/includes/Defines.php"");
+> | include ($WmfConfigRepoPath . ""/wmf-config/InitialiseSettings.php"");
+> | var_dump ($wgConf->settings);
+> 
+> but it doesn't yield for example information about de.wikipedia.org.
+
+Some experiments:
+
+$ php maintenance/eval.php 
+> $wgDBname='zhwiki';
+
+> $wmfRealm='production';
+
+> $mwConfigDir=""$IP/../operations/mediawiki-config"";
+
+> $wmfConfigDir=""$mwConfigDir/wmf-config"";
+
+> function getRealmSpecificFilename($p){global $IP,$wmfConfigDir;return str_replace($p,$IP,$wmfConfigDir);}
+
+> function wmfLoadInitialiseSettings($c){global $wmfConfigDir;require(""$wmfConfigDir/InitialiseSettings.php"");}
+
+> require(""$wmfConfigDir/wgConf.php"");
+
+> list($site,$lang)=$wgConf->siteFromDB($wgDBname);
+
+> $wikiTags=array();
+
+> $mwConfigDirHandle=opendir($mwConfigDir);
+
+> while(($f=readdir($mwConfigDirHandle))!==false){if(pathinfo($f,PATHINFO_EXTENSION)==='dblist'&&in_array($wgDBname,array_map('trim',file(""$mwConfigDir/$f"")))){$wikiTags[]=pathinfo($f,PATHINFO_FILENAME);}}
+
+> $dbSuffix = ( $site === 'wikipedia' ) ? 'wiki' : $site;
+
+> $wgConf->loadFullData();
+
+> $globals = $wgConf->getAll( $wgDBname, $dbSuffix,array('lang'    => $lang,'site'    => $site,'stdlogo' => ""//upload.wikimedia.org/$site/$lang/b/bc/Wiki.png""), $wikiTags );
+
+> print_r($globals);
+Array
+(
+    [wgLegacyEncoding] => 
+    [wgCapitalLinks] => 1
+    ...
+)
+
+>",1369467985,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+Provide wiki metadata in the databases similar to toolserver.wiki,"Played around with:
+
+| include ($MediaWikiRepoPath . ""/includes/Defines.php"");
+| include ($WmfConfigRepoPath . ""/wmf-config/InitialiseSettings.php"");
+| var_dump ($wgConf->settings);
+
+but it doesn't yield for example information about de.wikipedia.org.",1369450706,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-6qqicftxiu35fghejuwg,task_subcomment,NA
+"VisualEditor, CodeEditor, etc: User experience of editing page source directly","There are now at least three ways to edit a page via index.php (not including other crazy things like Wikidata). I couldn't find a bug tracking this user experience issue, so I'm filing this one.
+
+The three ways I'm initially focused on are:
+
+* directly editing the wikitext (which can appear as an ""edit source"" page tab when VisualEditor is enabled);
+* VisualEditor [https://www.mediawiki.org/wiki/VisualEditor]; and
+* CodeEditor [https://www.mediawiki.org/wiki/Extension:CodeEditor] (automatic for pages in the Module namespace and soon the CSS/JS pages as well; has a toggle in the edit toolbar).
+
+In particular to switch to editing the source, I'm worried about divergent approaches in the user interface. For example, a page tab v. a toggle in the edit toolbar.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1368935460,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-xka4cwtxxzprt6337pfw,task_description,invalid
+"VisualEditor, CodeEditor, etc: User experience of editing page source directly","This 2013 task with no updates in a decade does not seem to be tracking any actionable problem per Aklapper's comment above, so closing.",1725936323,PHID-USER-escte3psz5yfd2nj3jzr,False,PHID-TASK-xka4cwtxxzprt6337pfw,task_subcomment,NA
+"VisualEditor, CodeEditor, etc: User experience of editing page source directly",Slightly unclear what the bug to fix is here (and hence when it can be considered fixed). Could you elaborate?,1369397664,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xka4cwtxxzprt6337pfw,task_subcomment,NA
+"VisualEditor, CodeEditor, etc: User experience of editing page source directly","oh, and we can also add wikEd to that list :D",1368959990,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-xka4cwtxxzprt6337pfw,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"VE drops things like <i></i>, which Parsoid sometimes uses to preserve strange things.
+
+I think a solution might be to store this as an inline node or as a meta item.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368896280,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-njbgmmjxybp3rk2azuui,task_description,resolved
+VisualEditor: Empty annotations are dropped,"This works for single annotations, but not for nested ones. See https://gerrit.wikimedia.org/r/#/c/69343/ for a failing test case.",1371582191,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,Split new items out to bug 49497; closing this one.,1371065118,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"Above change fixes issue with annotations being dropped, but we still need to fix empty annotations not rendering (e.g. <span style=""display: block; background: red; width: 100px; height: 100px;""></span>), either here or in a new bug.",1371062712,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,Related URL: https://gerrit.wikimedia.org/r/68213 (Gerrit Change I0f3a194f629b054f193a61af105733a555775d79),1371062522,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"That would be nice, yes, but I don't think it's critically important.",1370298323,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"(Actually it's a yes/no question, both cases relate to the same behaviour.)",1369419847,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"(In reply to comment #1)
+> Should the inline node disappear if saved next to similarly annotated text,
+> 
+> e.g.
+> '<i><emptyAnnotation /></i><i>Foo</i>' => '<i>Foo</i>'
+> 
+> or more complex:
+> 
+> '<i><emptyAnnotation /></i><b><i>Foo</i></b>' => '<i><emptyAnnotation
+> /><b>Foo</b></i>'
+> ?
+
+I believe the latter, but Roan was going to answer this.",1369248022,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: Empty annotations are dropped,"Should the inline node disappear if saved next to similarly annotated text,
+
+e.g.
+'<i><emptyAnnotation /></i><i>Foo</i>' => '<i>Foo</i>'
+
+or more complex:
+
+'<i><emptyAnnotation /></i><b><i>Foo</i></b>' => '<i><emptyAnnotation /><b>Foo</b></i>'
+?",1368980503,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-njbgmmjxybp3rk2azuui,task_subcomment,NA
+VisualEditor: [Regression] Cursor should move to end of inserted contents after paste,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368891000,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wggr7br64lqzvnsbmef2,task_description,resolved
+VisualEditor: [Regression] Cursor should move to end of inserted contents after paste,Merged and will go out with wmf5.,1369092019,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wggr7br64lqzvnsbmef2,task_subcomment,NA
+VisualEditor: [Regression] Cursor should move to end of inserted contents after paste,Related URL: https://gerrit.wikimedia.org/r/64484 (Gerrit Change Ia2a2120cb75aa86374b594ae3f484c5161028919),1368891842,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wggr7br64lqzvnsbmef2,task_subcomment,NA
+VisualEditor: Paste is broken,"Throws an exception on line 564 of ve.ce.Surface, ve.getWindow is undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368890520,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jslagmridhbcpdvjclho,task_description,resolved
+VisualEditor: Paste is broken,Merged in master; will go out as part of wmf5.,1368978729,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jslagmridhbcpdvjclho,task_subcomment,NA
+VisualEditor: Paste is broken,Related URL: https://gerrit.wikimedia.org/r/64483 (Gerrit Change I31dc071328123b57b778aa1b21f0e1daf6405e5c),1368890997,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jslagmridhbcpdvjclho,task_subcomment,NA
+VisualEditor: 'Review and save' disabled after undo on oldid page,"'Review and save' is enabled on loading an old version of a page (as it should) but becomes disabled briefly after the first transaction is committed, and again if you undo to the top of the stack.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368819600,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-kayythzbd2m7qbeafhrw,task_description,resolved
+VisualEditor: 'Review and save' disabled after undo on oldid page,Merged; will go out with wmf5.,1368885016,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kayythzbd2m7qbeafhrw,task_subcomment,NA
+VisualEditor: 'Review and save' disabled after undo on oldid page,Related URL: https://gerrit.wikimedia.org/r/64372 (Gerrit Change I67c011ac655d4e553f9467cab10a875aaac61d03),1368820898,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kayythzbd2m7qbeafhrw,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more","When ""deselecting"" the text field of the visual editor (e.g. by clicking into the summary field) it seems to somehow loose focus.
+
+It's then not possible to directly select text (with the mouse) anymore. One needs to first click one time into the text field to be able to normally select text again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368796920,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-namz3nhksthhosxp6pjt,task_description,resolved
+"Text field seems to lose focus, selection not possible any more","I d'not know why I ever wrote VisualEditor but this definitely is about CodeEditor. And it definitely is fixed now!
+
+Thanks for bringing it up again (I remember you adding the PATCH_TO_REVIEW) but it wasn't merged back then so I couldn't test if the bug was really fixed) so we can close it for good.",1395789580,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more","Wait, this is in the CodeEditor extension group, but people are talking about the 'visual editor'. Did the reporter originally file it under the wrong Extension ?
+
+Eduard, can you clarify please ?",1395786171,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more",This seems fixed with: https://gerrit.wikimedia.org/r/104510,1388485715,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more",Is this the same issue as bug 50722?,1373479425,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more","I think I can replicate this bug, but I'm not sure I entirely understand the whole problem.
+
+If I select some text in the CodeEditor box, then click into another input element on the page to move focus there, then click back into to the CodeEditor, the cursor position within the text area does not change to the place I just clicked at and the selected text remains selected. I would expect it to deselect all text and move the cursor position to where the mouse cursor is. Major -> Minor",1368807619,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more",I'm using Firefox 21 on Windows 7.,1368803015,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"Text field seems to lose focus, selection not possible any more",Could you please provide browser information?,1368802912,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-namz3nhksthhosxp6pjt,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear in category suggestions when you've not picked one that exists","It should only appear when you're matching to a single, extant category - it doesn't appear for a new category, but appears (with no content) where you match more than one, which is confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368749040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ppxeze2biaiay2bq2ned,task_description,resolved
+"VisualEditor: ""Move this category here"" should not appear in category suggestions when you've not picked one that exists",This is fixed.,1370567377,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ppxeze2biaiay2bq2ned,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category","It's a no-op, and is confusing. (But is it more confusing to list it?)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1368745380,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-isog5p3qki3pp25ezf63,task_description,resolved
+"VisualEditor: ""Move this category here"" should not appear for the last category",https://gerrit.wikimedia.org/r/68130 (Gerrit Change If48e001b92c217bee0a35b6da41d1c1ff0e3271c) | change APPROVED and MERGED [by jenkins-bot],1371002078,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category",Related URL: https://gerrit.wikimedia.org/r/68130 (Gerrit Change If48e001b92c217bee0a35b6da41d1c1ff0e3271c),1371001967,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category",Related URL: https://gerrit.wikimedia.org/r/68130 (Gerrit Change If48e001b92c217bee0a35b6da41d1c1ff0e3271c),1371001964,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category",Now merged.,1370986001,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+"VisualEditor: ""Move this category here"" should not appear for the last category",Related URL: https://gerrit.wikimedia.org/r/67922 (Gerrit Change I93ce05f7cbb28313a3f0827539f0528c366aeb7e),1370905247,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-isog5p3qki3pp25ezf63,task_subcomment,NA
+mw.hook listeners for GuidedTour for shouldSkip,"Investigate how mw.hook could be useful for GuidedTour.  One idea is subscribing to state changes for shouldSkip.  For instance, UploadWizard has an AJAX-type interface where you go from step to step without changing pages.
+
+If we could listen to those steps, we could trigger the shouldSkip check (by calling guiders.resume or maybe another method that only checks this).
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1368612900,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-xj7stom4ugsmlhxmz6az,task_description,resolved
+mw.hook listeners for GuidedTour for shouldSkip,"Change 116228 merged by jenkins-bot:
+Refactor and add non-linear tours, with tests
+
+https://gerrit.wikimedia.org/r/116228",1402332994,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xj7stom4ugsmlhxmz6az,task_subcomment,NA
+mw.hook listeners for GuidedTour for shouldSkip,"Change 116228 had a related patch set uploaded by Mattflaschen:
+WIP: Refactor and add non-linear tours, with tests
+
+https://gerrit.wikimedia.org/r/116228",1397707892,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xj7stom4ugsmlhxmz6az,task_subcomment,NA
+mw.hook listeners for GuidedTour for shouldSkip,"This is done for VisualEditor.  I made this a tracking bug, and opened a separate one (bug 51985) for UploadWizard.",1374693237,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-xj7stom4ugsmlhxmz6az,task_subcomment,NA
+mw.hook listeners for GuidedTour for shouldSkip,I'm working on a change set right now that uses mw.hook for VE like this.,1373067339,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-xj7stom4ugsmlhxmz6az,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"We now have nginx SSL proxies in front of the beta caches (Bug T38648). We still have to fix the certificate (that is *.wmflabs.org for now).
+
+We need certificates generated by 'Labs CA' for the entries listed in role::protoproxy::ssl::beta and some more.  I guess the easiest would be to create *.beta.wmflabs.org cert that will also contains the following DNS entries:
+
+*.wikimedia.beta.wmflabs.org
+*.wikibooks.beta.wmflabs.org
+*.wikinews.beta.wmflabs.org
+*.wikipedia.beta.wmflabs.org
+*.wikiquote.beta.wmflabs.org
+*.wikisource.beta.wmflabs.org
+*.wikiversity.beta.wmflabs.org
+*.wikivoyage.beta.wmflabs.org
+*.wiktionary.beta.wmflabs.org
+
+And the mobile ones:
+
+*.m.wikimedia.beta.wmflabs.org
+*.m.wikibooks.beta.wmflabs.org
+*.m.wikinews.beta.wmflabs.org
+*.m.wikipedia.beta.wmflabs.org
+*.m.wikiquote.beta.wmflabs.org
+*.m.wikisource.beta.wmflabs.org
+*.m.wikiversity.beta.wmflabs.org
+*.m.wikivoyage.beta.wmflabs.org
+*.m.wiktionary.beta.wmflabs.org
+
+*.zero.wikipedia.beta.wmflabs.org
+
+**See Also**:
+{T56065}
+{T70387}
+{T71269}",1368604800,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_description,resolved
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Can this ticket be made public nowadays?  There is now T182927 and it seemed like a duplicate.
+
+Edit: ignore this, this comment was meant to be on T97593)",1513299970,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Can this ticket be made public nowadays?  There is now T182927 and it seemed like a duplicate.,1513299825,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Thanks to @Krenair (with reviews from @BBlack ) we got SSL on beta cluster.  That is quite an achievement.
+
+The last remaining patch has been merged in. I believe there is nothing left to do there.",1472656512,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 247587 merged by BBlack:
+beta: Use Let's Encrypt cert
+
+[[https://gerrit.wikimedia.org/r/247587]]",1472654942,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"So that is now pending review / merge of https://gerrit.wikimedia.org/r/247587 //beta: Use Let's Encrypt cert// which is already on beta cluster.
+",1472038753,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Convince someone with ops rights to merge the patch,1472028326,PHID-USER-mvx4x7ywk2flsaku2dbk,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,That is really neat @AlexMonk-WMF !  Is there anything left to do?,1472027977,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 302409 merged by jenkins-bot:
+deployment-prep: Swap config to HTTPS
+
+[[https://gerrit.wikimedia.org/r/302409]]",1470134583,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 302409 had a related patch set uploaded (by Alex Monk):
+deployment-prep: Swap config to HTTPS
+
+[[https://gerrit.wikimedia.org/r/302409]]
+",1470134511,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 247587 had a related patch set uploaded (by Alex Monk):
+beta: Use Let's Encrypt for upload, and new self-signed SSL certificate for most of text
+
+[[https://gerrit.wikimedia.org/r/247587]]
+",1470107265,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,This is now working for meta.wikimedia.beta.wmflabs.org and deployment.wikimedia.beta.wmflabs.org (and their mobile variants) as well as upload.beta.wmflabs.org. I'll try to handle all other domains tomorrow.,1470123240,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,This is now working for meta.wikimedia.beta.wmflabs.org and deployment.wikimedia.beta.wmflabs.org (and their variants) as well as upload.beta.wmflabs.org. I'll try to handle all other domains tomorrow.,1470107154,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Its puppetized now, should not be hard anymore. We already use it in prod.",1464824261,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,It may or may not be a strict blocker but we should probably wait for {T132812},1460745558,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#2210861, @csteipp wrote:
+> Ftr, I'd love to see us move in the direction of the let's encrypt model, where it's a straightforward, automated process for servers to get a valid cert for their identity. Whether it's LE specifically, or one of the projects that makes an LE-like api that organizations can run to automatically get certificates from their preferred CA.
+> 
+> I think we're going to need more of these (mysql and kafka servers / clients in the near term), and I'd like to get to the point where we're dealing with short lived certs wherever possible.
+
+That might be hard as we're not exposing those servers directly to the internet. I suppose we could use an internal CA and run our own Let's Encrypt-like setup, but this is all far outside the scope of this task :)",1460741823,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#2210736, @Krenair wrote:
+>>>! In T97593#2115226, @Krenair wrote:
+>> I am also wondering what the best way is to put the Let's Encrypt client onto the beta servers. Could we install it on the deployment-cache-text04 and deployment-cache-upload04 instances and have them get their own certificates? They're all running jessie and there is a letsencrypt package available.
+
+Ftr, I'd love to see us move in the direction of the let's encrypt model, where it's a straightforward, automated process for servers to get a valid cert for their identity. Whether it's LE specifically, or one of the projects that makes an LE-like api that organizations can run to automatically get certificates from their preferred CA.
+
+I think we're going to need more of these (mysql and kafka servers / clients in the near term), and I'd like to get to the point where we're dealing with short lived certs wherever possible.",1460741344,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T97593#2115226, @Krenair wrote:
+> I am also wondering what the best way is to put the Let's Encrypt client onto the beta servers. Could we install it on the deployment-cache-text04 and deployment-cache-upload04 instances and have them get their own certificates? They're all running jessie and there is a letsencrypt package available.
+
+>>! In T97593#2116454, @Krenair wrote:
+> I checked this in deployment-cache-upload04 today. It's from jessie-backports and depends on lots of things from there, so you end up with something like:
+> `sudo apt-get install letsencrypt python-cryptography=1.1.1-1~bpo8+1 python-pyasn1=0.1.9-1~bpo8+1 python-openssl=0.15.1-2~bpo8+1`
+> (I did not actually allow this to continue, would like someone else to review since I'm not used to messing with package versions like this)
+
+>>! In T97593#2210712, @Krenair wrote:
+> ops have started using it in production for (ubuntu|apt|mirrors).wikimedia.org and it might be puppetised soon. (see T132450)",1460740489,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T97593#2115226, @Krenair wrote:
+> I am also wondering what the best way is to put the Let's Encrypt client onto the beta servers. Could we install it on the deployment-cache-text04 and deployment-cache-upload04 instances and have them get their own certificates? They're all running jessie and there is a letsencrypt package available.
+
+>>! In T97593#2116454, @Krenair wrote:
+> I checked this in deployment-cache-upload04 today. It's from jessie-backports and depends on lots of things from there, so you end up with something like:
+> `sudo apt-get install letsencrypt python-cryptography=1.1.1-1~bpo8+1 python-pyasn1=0.1.9-1~bpo8+1 python-openssl=0.15.1-2~bpo8+1`
+> (I did not actually allow this to continue, would like someone else to review since I'm not used to messing with package versions like this)",1460738908,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I'm going around a few tasks on this subject trying to merge/close everything together (this one, T70387, T75919, T97593). I'm going to see if I can get Let's Encrypt working for this.",1457835537,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I'm going around a few tasks on this subject trying to merge everything together (this one, T70387, T75919, T97593). I'm going to see if I can get Let's Encrypt working for this.",1457835416,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#1951388, @faidon wrote:
+> Can someone repeat why we can't just flatten the beta hostnames and just procure a *.beta.wmflabs.org certificate?
+
+Presumably because that would make beta less similar to production and less useful for testing things where the domain structure is relevant (e.g. CentralAuth shared cookies).",1453575790,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#527689, @Krinkle wrote:
+> Would it be an option to flatten our subdomains?
+> 
+> We'd only need beta.wmflabs.org and *.beta.wmflabs.org to be in the certificate
+> 
+> (at e.g. DigiCert, those wildcards are $1425 for 3 years includes root and *)
+> 
+> For example:
+> 
+> * beta.wmflabs.org
+> * bits.beta.wmflabs.org
+> * wikimedia.beta.wmflabs.org
+> * commons-wikimedia.beta.wmflabs.org
+> * wikipedia.beta.wmflabs.org
+> * en-wikipedia.beta.wmflabs.org
+> * nl-wikibooks.beta.wmflabs.org
+> * en-m-wikibooks.beta.wmflabs.org
+> * en-m-wikinews.beta.wmflabs.org
+
+I've asked the same a few times and I don't remember the response. Can someone repeat why we can't just flatten the beta hostnames and just procure a *.beta.wmflabs.org certificate?",1453369421,PHID-USER-ktuojnvco4fpzmyhzyaf,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Yeah, beta.wmflabs.org was in the private beta. Don't know if it can actually work with our setup though.",1449227020,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Let's Encrypt is in Public Beta now. Everyone can get free certificates from them now.
+
+[1] https://letsencrypt.org/2015/12/03/entering-public-beta.html
+[2] User Guide for getting certs using Let's Encrypt client: https://letsencrypt.readthedocs.org/en/latest/",1449209519,PHID-USER-arjqb24x4oae7awzpfp6,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#1669896, @Chmarkine wrote:
+> [[ https://letsencrypt.org/ | Let's Encrypt ]] provides free trusted(*) DV non-wildcard certs. We have 31 domains lists [[ http://meta.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix | here ]]. If you think it's plausible, we can obtain 31 certs (one for each domain) from Let's Encrypt at zero cost. 
+> 
+> (*) They will have their CA certificate cross-signed by IdenTrust next month, so the certs they issued won't be trusted until then.
+
+Let's Encrypt has received the cross-signature, so its certificates are now trusted by all major browsers.
+
+[1] https://letsencrypt.org/2015/10/19/lets-encrypt-is-trusted.html",1445334021,PHID-USER-arjqb24x4oae7awzpfp6,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#1670596, @Lixxx235 wrote:
+> Chmarkine, there's always StartCom/StartSSL which has free certs, and they're already trusted by default in all major browsers. 
+
+Yes. But StartCom charges $24.9 for each certificate revocation.
+
+https://www.startssl.com/?app=43",1443105776,PHID-USER-arjqb24x4oae7awzpfp6,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,">>! In T50501#1670596, @Lixxx235 wrote:
+> Chmarkine, there's always StartCom/StartSSL which has free certs, and they're already trusted by default in all major browsers. 
+
+Yes. But StartCom charges $25 for each certificate revocation.",1443105592,PHID-USER-arjqb24x4oae7awzpfp6,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Chmarkine, there's always StartCom/StartSSL which has free certs, and they're already trusted by default in all major browsers. ",1443100193,PHID-USER-2hzxflhh7cwlrnz74x6y,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I think we'd also want upload.beta.wmflabs.org, maybe stream.wmflabs.org, all of the m./zero. variants? What about mx.beta.wmflabs.org?",1443097851,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"[[ https://letsencrypt.org/ | Let's Encrypt ]] provides free trusted(*) DV non-wildcard certs. We have 31 domains lists [[ http://meta.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix | here ]]. If you think it's plausible, we can obtain 31 certs (one for each domain) from Let's Encrypt at zero cost. 
+
+(*) They will have their CA certificate cross-signed by IdenTrust next month, so the certs they issued won't be trusted until then.",1443084427,PHID-USER-arjqb24x4oae7awzpfp6,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"one more reason we should have this is to avoid needing https://gerrit.wikimedia.org/r/237523  (T105794, T112195)",1441924507,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,@ArielGlenn: there's an NDA'd task at T97593 which Brandon is driving.,1439306906,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,@ArielGlenn: there's an NDA's task at T97593 which Brandon is driving.,1439306268,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,@greg  so what's the decision; there's also https://phabricator.wikimedia.org/T75919 and https://phabricator.wikimedia.org/T70387   Self-signed certs in beta or not?  ,1439287610,PHID-USER-jtxavgb3caz53o45csni,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Is T70387 a duplicate of this?,1429298534,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Matthew Flaschen from comment #93)
+> If cost is the issue, did we consider setting up our own certificate
+> authority (chained to an existing root)?  It's an upfront cost, but as I
+> understand it that means no per-cert cost.
+> 
+> Google and Microsoft both have them, just to name a couple.
+
+Getting a delegated signing certificate is a huge deal actually. Once you have one, any certificate you sign is trusted by all who trust your upstream signer. The x509 protocol does not make it possible to construct a trusted signing certificate that is restricted to a particular domain. As such, any trusted signer who issues delegate signing certificates must impose strict practices and regular audits of those practices on any delegate organization.",1406914396,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I can think of three significant problems with self-signed certificates:
+
+1. It trains people to ignore SSL warnings, which means they ignore them when it's a legit problem.
+2. It causes problems with automated tests (not clear if all of these have been worked around).
+3. It's a real pain when testing manually because you have to visit https://bits.beta.wmflabs.org/ (and maybe also upload.beta.wmflabs.org) manually in Firefox.
+
+FWIW, https://en.wikipedia.beta.wmflabs.org isn't working at all (not even invalid) right now (can't connect), but I assume that's temporary
+
+If cost is the issue, did we consider setting up our own certificate authority (chained to an existing root)?  It's an upfront cost, but as I understand it that means no per-cert cost.
+
+Google and Microsoft both have them, just to name a couple.",1398901677,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"This bug seems to be drifted away from the initial comment.
+(In reply to Antoine ""hashar"" Musso from comment #0)
+> We need certificates generated by 'Labs CA' for the entries listed in
+> role::protoproxy::ssl::beta and some more.  I guess the easiest would be to
+> create *.beta.wmflabs.org cert that will also contains the following DNS
+> entries:
+
+So
+
+(In reply to Greg Grossmeier from comment #91)
+> Won't Fix'ing this for now.
+> A) We have self-signed certs in place on Beta
+
+We still don't have valid self-signed certs for beta since eqiad migration as far as I know. At least nginx refuses to starts because of cert mismatch. As I was told in bug 63538 that this (certs) is handled here, I REOPEN. Please generate new (self-signed) certs.",1398877580,PHID-USER-jcypqodpdpbcicgwgh7j,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Won't Fix'ing this for now.
+
+A) We have self-signed certs in place on Beta
+B) Real certs are expensive
+C) There hasn't been any team come with a specific use case where buying the real certs would make sense.
+
+Feel free to reopen if any of the above changes.",1398876875,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org," > I'm afraid it can't and *.wmflabs.org is not *.beta.wmflabs.org (only one
+> level of wildcard possible). But ask RobH to make sure.
+
+Ah indeed my bad. Sorry :-]",1397643671,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Antoine ""hashar"" Musso from comment #86)
+star.wmflabs.org would cover the entries:
+
+ bits.beta.wmflabs.org
+ upload.beta.wmflabs.org
+ wikidata.beta.wmflabs.org
+
+I'm afraid it can't and *.wmflabs.org is not *.beta.wmflabs.org (only one level of wildcard possible). But ask RobH to make sure.",1397643379,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"for *.wmflabs.org, the self-signed cert has recently been replaced with one from RapidSSL , at first the chained file, which is created by puppet was wrong, the above changes should have fixed that.",1397643103,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+
+https://gerrit.wikimedia.org/r/#/c/111386/
+https://gerrit.wikimedia.org/r/#/c/126008/1",1397643019,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+The beta cluster has for Varnish instances with a Nginx HTTPS proxy installed.  Nginx refuses to start because the star.wmflabs.org certificate is invalid:
+
+root@deployment-cache-bits01:~# /etc/init.d/nginx start
+Starting nginx: nginx: [emerg]
+  SSL_CTX_use_PrivateKey_file(""/etc/ssl/private/star.wmflabs.org.key"")
+  failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)
+ nginx: configuration file /etc/nginx/nginx.conf test failed
+
+
+To fix it we would need a few certificates to be installed on the instances via the role::protoproxy::ssl::beta puppet class in manifests/role/protoproxy.pp
+
+star.wmflabs.org would cover the entries:
+
+ bits.beta.wmflabs.org
+ upload.beta.wmflabs.org
+ wikidata.beta.wmflabs.org
+
+We would need *.wikimedia.beta.wmflabs.org and *.wikipedia.beta.wmflabs.org certs as well.",1397642712,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Greg Grossmeier from comment #84)
+> * Setup was(is?) annoying because of the lack of easy way to secure these
+> private certs from other non-WMF root labs users.
+
+I thought comment 65 and comment 67 said the ""access to private keys without an NDA"" part was solved.
+
+Antoine said he did the sudo configuration (see comment 67); I'm not sure if it's checked yet.",1397014720,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(Lowering priority and unassigning from self)
+
+Status, afaict:
+* Price was annoying, but we've identified the 7 we want (comment 77, comment 79, and comment 83).
+* Setup was(is?) annoying because of the lack of easy way to secure these private certs from other non-WMF root labs users.
+
+Marc/RobH: Let me know if I have that wrong and if there's anything else we can do right now.",1396547005,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"wikidata.beta.wmflabs.org might be nice, since I know a few gadgets go cross domain to it.
+
+I think the dewiki community also wanted to have de.wikipedia.beta.wmflabs.org, but unless we get a discount for buying them at one time, it would probably be good to wait until we have browser tests running against that wiki.",1393026432,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Greg Grossmeier from comment #80)
+
+> 
+> For the avoidance of doubt: we're not doing them all, just a subset. SSL
+> certs are a racket and expensive.
+
+Oh, missed that above. Makes sense :)",1393024173,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Yeah, we can't do all; we can't even reasonably all the necessary wildcards to cover the whole matrix.
+
+I have six now; any more?",1393024132,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to Kunal Mehta (Legoktm) from comment #78)
+> http://meta.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix is the full
+> list.
+
+For the avoidance of doubt: we're not doing them all, just a subset. SSL certs are a racket and expensive.",1393023963,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,http://commons.wikimedia.beta.wmflabs.org/ is important,1393023530,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"http://meta.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix is the full list.
+
+There are some weird ones like 'ee-prototype'.",1393023457,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"login.wikipedia.beta.wmflabs.org
+meta.wikipedia.beta.wmflabs.org
+en.wikipedia.beta.wmflabs.org
+bits.beta.wmflabs.org
+upload.beta.wmflabs.org (for some icons on meta/login)
+
+That's all I can see from the network calls.
+
+Antoine/Chris/Chris: confirm?",1393023342,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Because of the necessity to have a default CA sign this, we need to buy individual certificates.  Please provide a definite list of domain names, and I'll get that ball rolling.",1393019538,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I think we do want it, on a limited set of subdomains to keep the cost down.
+
+Beta's:
+- loginwiki (so we can check SUL interactions)
+- metawiki (so OAuth works correctly and securely)
+- another wiki, maybe enwiki? (to catch other SUL login/wgSecureLogin issues)
+- Oh, and to make enwiki work, the bits domain would also need a cert",1390496204,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"We have stopped running browser tests over https. 
+
+I think we still want SSL for labs, but I don't know of anyone actively working on that right now.",1390487679,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #72)
+> Still highest priority.  We want to get that done while I am in SF, hopefully
+> this afternoon (PST time).
+
+Sorry, was referring to another bug :-/
+
+
+Regarding SSL certificates on beta, I am not sure what the status is.  Maybe Greg/Chris would know.  We might have a workaround now or simply stopped running browser tests over HTTPS.",1390442784,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Still highest priority.  We want to get that done while I am in SF, hopefully this afternoon (PST time).",1390420537,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Greg and RobLa: RT ticket states you wanted to discuss how to proceed here.
+Any updates (or should this not be highest priority)?",1390406116,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Would it be an option to flatten our subdomains?
+
+We'd only need beta.wmflabs.org and *.beta.wmflabs.org to be in the certificate
+
+(at e.g. DigiCert, those wildcards are $1425 for 3 years includes root and *)
+
+For example:
+
+* beta.wmflabs.org
+* bits.beta.wmflabs.org
+* wikimedia.beta.wmflabs.org
+* commons-wikimedia.beta.wmflabs.org
+* wikipedia.beta.wmflabs.org
+* en-wikipedia.beta.wmflabs.org
+* nl-wikibooks.beta.wmflabs.org
+* en-m-wikibooks.beta.wmflabs.org
+* en-m-wikinews.beta.wmflabs.org",1387423868,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Reason in comment 16 is past (testing of new default HTTPS access), but warning message in Selenium probably still justifies highest prio? (for four months now)
+
+(In reply to comment #68)
+> The related ticket is https://rt.wikimedia.org/Ticket/Display.html?id=6116
+
+To summarize the RT ticket: Prices offered by SSL vendors felt out of scope.
+
+Greg and RobLa: RT ticket states you wanted to discuss how to proceed here.
+Any updates?",1387200913,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Buying certs is pending approval according to RobH a few days ago.  The related ticket is https://rt.wikimedia.org/Ticket/Display.html?id=6116,1384430488,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+I have cleaned up permissions on the deployment-prep labs project (ie: beta cluster).
+
+The project admins are now limited to people from the Wikimedia ops and mw-core teams.
+
+Root access has been limited to people having signed a non disclosure agreement with Wikimedia.
+
+
+The reason for this change is to let us put real SSL certificates on the Varnish caches which would let us support HTTPS on the beta cluster.  We want to keep access to the certificates restricted, hence the change.
+
+
+Please review the list of admins and sudo policy for the deployment-prep project on:
+
+https://wikitech.wikimedia.org/wiki/Special:NovaProject
+https://wikitech.wikimedia.org/wiki/Special:NovaSudoer",1383836540,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"> 1. Remove projectadmin permissions from volunteers
+
+I also just removed TheDJ since he didn't have an NDA on file and he didn't respond to my email asking if he wanted to sign one.
+
+> 2. Clean up sudo policies to disallow root on varnish systems (that will have
+> real certs)
+
+Apparently the sudo policies are set up at https://wikitech.wikimedia.org/wiki/Special:NovaSudoer. It looks like most of them have sudo enabled for ""ALL"" hosts. I imagine disabling their root privileges on varnish systems just entails unchecking some of these hosts. Unfortunately, I'm not sure which of these hosts are varnish systems. Is it all 4 of the deployment-cache hosts? Any others?
+
+> 3. Buy * certs
+
+Good to hear that's in progress.",1383677201,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #46)
+> Summary of IRC conversation:
+> 
+> 1. Remove projectadmin permissions from volunteers
+
+{{DONE}}, see list of members at: https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep
+
+> 2. Clean up sudo policies to disallow root on varnish systems (that will have
+> real certs)
+
+Not sure what needs to happen here. Tips/Pointers? I think Antoine had some ideas?
+
+> 3. Buy * certs
+
+In progress: https://rt.wikimedia.org/Ticket/Display.html?id=6116",1383162153,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"So I took the bug thinking the cert was blocking everything, however that is not the case.
+
+I will handle the purchase of the certificate, but I am not claiming any ownership over any other part of this process =]
+
+We get purchase approvals within our closed ticketing system, RT#6116.  (I've set Hashar as requestor for that ticket.)  Once its purchased I'll post in here as well.",1383072339,PHID-USER-xy6c3ul27f336aaedx2d,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,unassigning from Ryan to reflect reality.,1383070552,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #46)
+> 2. Clean up sudo policies to disallow root on varnish systems (that will have
+> real certs)
+
+I assume this means that non-admins should not have sudo on these machines?",1383070383,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #58)
+> Anyway, this isn't blocked on ops. In comment 46 I listed the steps that need
+> to be taken, and they can be taken by anyone that has projectadmin in
+> deployment-prep. Someone needs to take ownership of this situation and run
+> with it.
+
+I think the problem is that no one is quite sure how to do those things. I'm not sure otherwise I would JFDI.",1383070340,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Secure login is disabled,1383070174,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Well, disabling secure login is easy - much better to have a couple of tests failing than not be able to run them at all.",1383069987,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"If MobileFrontend doesn't work without HTTPS it's broken. That's a different bug, though.
+
+Anyway, this isn't blocked on ops. In comment 46 I listed the steps that need to be taken, and they can be taken by anyone that has projectadmin in deployment-prep. Someone needs to take ownership of this situation and run with it. It will take us a matter of days to get SSL certs and we can start that process now, but until the other steps are taken there's no major point in doing so.",1383069913,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,This actually makes beta labs unusable for me and the rest of the mobile team. Mobile is dependent on https - it's been like this since login was first introduced. It is not easy to disentangle.,1383069706,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,No I don't. It currently redirect to HTTPS for me in Safari and fails to load completely in Firefox.,1383069532,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #54)
+> Although I have no idea why the HTTP version doesn't load.
+
+It does for me, both in browsers and using curl.  Is it possible you have HTTPS Everywhere or something enabled?",1383017052,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Any progress on this? It's been 2 weeks and we still can't do acceptance testing on beta labs.
+
+And no we can't not use https:
+http://en.m.wikipedia.beta.wmflabs.org/wiki/Main_Page
+Although I have no idea why the HTTP version doesn't load.",1383006331,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+Should be Real Soon Now: https://bugzilla.wikimedia.org/show_bug.cgi?id=55804",1381967050,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #51)
+> I guess the first part of my comment is redundant with what you already know.
+> Mostly, I wanted to convey that our automation testing is broken, in case
+> that
+> affects prioritizing.
+
+Is it possible for now to not use https? That's what other projects have done for now to workaround the issue.",1381966770,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"I guess the first part of my comment is redundant with what you already know. Mostly, I wanted to convey that our automation testing is broken, in case that affects prioritizing.",1381966629,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #49)
+> Currently getting a cert warning when trying to go to:
+> https://deployment.wikimedia.beta.wmflabs.org/
+> This is breaking our automation tests for mobile.
+
+Heh. Did you read the ticket any before posting this? :)",1381966170,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Currently getting a cert warning when trying to go to:
+https://deployment.wikimedia.beta.wmflabs.org/
+This is breaking our automation tests for mobile.",1381965216,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,It's going to be an all-inclusive * cert for beta.,1381438407,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,please don't forget about wikidata.beta.wmflabs.org,1381437836,PHID-USER-lzhljhpbm3qfphvqyill,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Summary of IRC conversation:
+
+1. Remove projectadmin permissions from volunteers
+2. Clean up sudo policies to disallow root on varnish systems (that will have real certs)
+3. Buy * certs
+
+Any volunteer that would like to have projectadmin in the project or root on the varnish systems will need an NDA.",1381437765,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 87045 merged by jenkins-bot:
+Labs: Turn off secure login on loginwiki due to untrusted SSL
+
+https://gerrit.wikimedia.org/r/87045",1381250687,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #42)
+> (In reply to comment #40)
+> 
+> > I'm still not opposed to getting a proper cert, but that requires some
+> > infrastructure and permissions changes in deployment-prep...
+> 
+> Since we've been going around on this since May, what would be the next step
+> to
+> make that happen?
+
+Maybe create another project with limited access and move the ssl terminators there. You should realize that other than advising I'm not really doing anything in beta...",1380729147,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #41)
+> (In reply to comment #29)
+> > There's also the option which had been discussed before: make a new labs
+> > project whose sole purpose would be to do SSL termination and would then
+> > relay
+> > to varnish.
+> > 
+> > Then *that* project would have the NDA req instead of the core beta project.
+> 
+> That's the dynamichttp proxy, which has been running silently for a while now
+> :)
+
+They want to have the same https infrastructure as production, which makes sense ;)",1380729060,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #40)
+
+> I'm still not opposed to getting a proper cert, but that requires some
+> infrastructure and permissions changes in deployment-prep...
+
+Since we've been going around on this since May, what would be the next step to make that happen?",1380728062,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #29)
+> There's also the option which had been discussed before: make a new labs
+> project whose sole purpose would be to do SSL termination and would then
+> relay
+> to varnish.
+> 
+> Then *that* project would have the NDA req instead of the core beta project.
+
+That's the dynamichttp proxy, which has been running silently for a while now :)",1380727770,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Has anyone considered creating a CA (http://pages.cs.wisc.edu/~zmiller/ca-howto/), generating a * cert, and adding that certificate to the browser's trust? Is that a possibility using the selenium service we're using?
+
+I'm still not opposed to getting a proper cert, but that requires some infrastructure and permissions changes in deployment-prep...",1380727437,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #33)
+> But I can't find prefershttps in Preferences to turn that off.
+
+So it turns out it only displays if wgSecureLogin is on, but it defaults true either way.  The gotcha is that it wasn't not on for Labs, *except* loginwiki.  However, loginwiki is not taken into account by the Preferences logic.  
+
+I believe the above should workaround that by disabling wgSecureLogin on loginwiki as well.  However, I haven't tested it, since I don't have a realistic CentralAuth environment.
+
+This is just intended to be temporary until there's an SSL setup on Beta that is trusted out-of-the-box by browsers.",1380704544,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Change 87045 had a related patch set uploaded by Mattflaschen:
+Labs: Turn off secure login on loginwiki due to untrusted SSL
+
+https://gerrit.wikimedia.org/r/87045",1380704074,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Calm down, what we need is to use the 'Labs CA' certificate authority to generate all the certificates we need, then add that authority as a trusted one in the browsers.
+
+I would do it myself if I had access to the 'Labs CA'.",1380701912,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #35)
+> (In reply to comment #33)
+> > (In reply to comment #32)
+> > > (In reply to comment #19)
+> > > > For those playing along at home: The Beta Cluster currently does not have
+> > > > https by default turned on for this very reason (it broke browser tests).
+> > > 
+> > > This is no longer the case.
+> > 
+> > Correction: it's enabled by default, but only for logged in users.
+> > 
+> > But I can't find prefershttps in Preferences to turn that off.
+> 
+> This means, for instance, that VisualEditor is entirely untestable on Beta
+> Labs. Yay fun. :-(
+
+That is not true, VisualEditor works just fine on beta labs, we found Bug 54791 on beta labs with an automated browser test just this week.  Beta labs is as healthy as it has ever been, and it is running the master branch with database updates all maintained automatically.  Varnish on beta is configured properly, and is working well. 
+
+What does not work on beta labs without a real SSL cert are: 
+
+* tests for IE10 are busted : https://saucelabs.com/jobs/a29bcd975ac6483195b3bd56a64fec6a
+
+* having to visit https://bits.beta.wmflabs.org manually over and over again to get styling to work in every browser is a drag",1380665184,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #33)
+> (In reply to comment #32)
+> > (In reply to comment #19)
+> > > For those playing along at home: The Beta Cluster currently does not have
+> > > https by default turned on for this very reason (it broke browser tests).
+> > 
+> > This is no longer the case.
+> 
+> Correction: it's enabled by default, but only for logged in users.
+> 
+> But I can't find prefershttps in Preferences to turn that off.
+
+This means, for instance, that VisualEditor is entirely untestable on Beta Labs. Yay fun. :-(",1380657576,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"
+Yes. Using beta continues to be a hassle, and in the near future the SSL issue is going to be a big problem.",1380641833,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #32)
+> (In reply to comment #19)
+> > For those playing along at home: The Beta Cluster currently does not have
+> > https by default turned on for this very reason (it broke browser tests).
+> 
+> This is no longer the case.
+
+Correction: it's enabled by default, but only for logged in users.
+
+But I can't find prefershttps in Preferences to turn that off.",1380587930,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #19)
+> For those playing along at home: The Beta Cluster currently does not have
+> https by default turned on for this very reason (it broke browser tests).
+
+This is no longer the case.
+
+(In reply to comment #24)
+> Let's deploy SSL either correctly or not-at-all to beta.
+
+Agreed.  I think turning SSL completely off on beta would be better than the current situation.  It's not good for people to get in the habit of ignoring certificate warnings.
+
+Of course, fixing it properly with a valid cert is best.",1380587514,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Bumping this with a note that this affects our ability to run automated tests with IE10 only.  (Demo on request) Other versions of IE seem to be OK with the current situation on labs, but I haven't found a way around IE10's paranoia. 
+
+It would be good to have some sort of solution for this in advance of support for IE10 in VisualEditor.",1379432509,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Hm. That isn't a bad idea. If we were to do that, I'd want to move the ssl terminators and the caching layer there, and strip private IP info at that layer. Then we can change beta's privacy policy to that of the projects.",1377728033,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"There's also the option which had been discussed before: make a new labs project whose sole purpose would be to do SSL termination and would then relay to varnish.
+
+Then *that* project would have the NDA req instead of the core beta project.",1377727232,PHID-USER-7ey733eainlhx5xqp4d3,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #25)
+> As I've mentioned in the past, I'm totally fine with getting an SSL cert for
+> beta, assuming we ensure every project member in deployment-prep has a signed
+> NDA.
+> 
+> In the future Yuvi's proxy will handle load balancing, HTTPS and such. We'll
+> be
+> able to drop the NDA requirement (and the SSL cert) once we have that.
+
+Not every deployment-prep member is capable of signing an NDA anyway.",1377726168,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Ah. Indeed. Well, let's treat deployment-prep like tools and require NDAs for all roots...",1377725772,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"(In reply to comment #25)
+> In the future Yuvi's proxy will handle load balancing, HTTPS and such.
+> We'll able to drop the NDA requirement (and the SSL cert) once we have that.
+
+I dont think we should use  Yuvi proxy for beta since the point of the project is to closely reproduce production. Currently the SSL connections are handled by nginx proxies, whenever varnish supports it, they will land on the varnish frontends.",1377725574,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Understandable for manual testing. I just wanted to make sure the automated tests weren't actually blocked, since there's ways to relatively easily workaround the issue.
+
+As I've mentioned in the past, I'm totally fine with getting an SSL cert for beta, assuming we ensure every project member in deployment-prep has a signed NDA.
+
+In the future Yuvi's proxy will handle load balancing, HTTPS and such. We'll be able to drop the NDA requirement (and the SSL cert) once we have that.",1377724502,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Ryan, it's possible to work around the problem, but the issue is that, for manual testing, it's too easy to blame the SSL problem for things that might be totally unrelated.  Let's deploy SSL either correctly or not-at-all to beta.",1377721482,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"My original requests was to generate certificates for the beta wildcards domains using the 'Labs CA' certificate authority.  By adding that authority certificate in the browser (or accepting it), that should make the browser trust all the generated certs.",1377721422,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,The automated tests were OK I think with maybe some small exceptions.  The hassle was having to visit all the hosts (e.g. bits) in your browser in order to use any beta wikis.,1377718091,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Is it not possible to disable certificate checking on the automated browser tests until we get a proper certificate? I remember this being possible years ago when I built a selenium cluster...,1377717965,PHID-USER-xs3vxsmgivmm2tuyxsrb,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Mostly it makes using beta labs manually a real hassle.,1377716121,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,For those playing along at home: The Beta Cluster currently does not have https by default turned on for this very reason (it broke browser tests).,1377713093,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"We should probably disable default https on beta until we have the opportunity to fix this up properly.  The proper fix, from what I understand, is pretty complicated, and isn't something we can do with just a day or two of elbow grease.",1377712492,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"There's no interface with firefox, either. The workaround is to manually go to https://bits.beta.wmflabs.org/ and accept the certificate there.",1377088410,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,It seems to me that being able to test the new [[m:HTTPS]] stuff on beta is a rather high priority; otherwise beta should be fixed for its other uses by reverting the HTTPS redirect on it.,1377084434,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Apparently the beta labs now forcefully redirect to https, which means all beta sides are unusable for me (Chrome) because there is no obvious way to accept the certificate for bits, so no resources are being loaded.",1377078117,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,*** Bug 46621 has been marked as a duplicate of this bug. ***,1377077926,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,*** Bug 49533 has been marked as a duplicate of this bug. ***,1377077878,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,*** Bug 53113 has been marked as a duplicate of this bug. ***,1377028391,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Alex: turning ssl certificate verification off when doing automated testing is reasonably common because lots of folks don't run with valid certs and don't have a good infrastructure for distributing their self signed certs.  That isn't to say it is a good practice, just a common one.",1376416702,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Upping priority (a tiny bit) as we really need the beta cluster (hosted on labs) to be as similar to production as possible for automated testing. This is needed for that (specifically for SUL2, kinnnnnda important ;) ).",1376408675,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"All browsers should force you to navigate that warning, unless you've somehow changed their configuration to somehow completely break that security feature.",1375118567,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"in the configurations we're using, other browsers don't require an automated test to negotiate a warning screen, see the screen shot on Bug 52121",1375112625,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,The other browsers don't like it either. Why is IE so special to you?,1375112429,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,We need beta labs to work for IE in default configurations for test purposes. See Bug 52121,1375110403,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,*** Bug 52121 has been marked as a duplicate of this bug. ***,1374916134,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Did not block the creation of a login wiki bug 51622
+
+But it does prevents us from using SUL2 on beta which is bug 51580",1374694229,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,"Moving out from RT to ""Labs"" > ""Infrastructure"", per Ryan :)",1369121097,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,RT #5184,1369038519,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+beta: Get SSL certificates for *.{projects}.beta.wmflabs.org,Mailled labs-l to find out who can generate the cert. http://lists.wikimedia.org/pipermail/labs-l/2013-May/001212.html,1368605321,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-p25kct7eiowcmvkmyncx,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,"We need a public API end point integrating with the general MediaWiki API that provides at least the following functionality:
+
+* HTML DOM retrieval per page and revision. Basically the /en/Foo?oldid=<n> end point.
+* HTML DOM expansion: POST a DOM (or fragment), return re-expanded DOM
+* HTML DOM saving: POST a modified DOM and a summary, and save it as a new revision.
+
+As long as we are using Wikitext as our storage format, saving requires a conversion to HTML and a separate save step. The individual steps should *internally* be exposed to other users including the VisualEditor extension. There is probably no need to expose the HTML2WT conversion. We should instead aim to provide an HTML-only public interface.
+
+The integration should use an URL schema that makes it easy to map some or all of the functionality to a stand-alone (non-PHP) backend to avoid PHP startup costs in the future.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368578460,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpywcmlyfhgff4artepd,task_description,resolved
+Expose a parsoid public web API end point in the MediaWiki API,"@anomie Seems like it was mis-tagged, sorry about that. Will remove the project.",1426257850,PHID-USER-hxwwywcyzpooynxuo7a2,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,So this was in #MediaWiki-API but didn't actually have anything to do with that project?,1426257574,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Now resolved with https://rest.wikimedia.org/ entering beta production.,1426214472,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,"Lowering the priority as this is now live:
+
+http://parsoid-lb.eqiad.wikimedia.org/
+https://parsoid-prod.wmflabs.org/  (also supports spdy)",1386109005,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Once https://gerrit.wikimedia.org/r/#/c/93527/ is merged we'll provide interim access to our internal Parsoid cluster through front-end caches at http://parsoidcache.svc.eqiad.wikimedia.org/. This implements our internal https://www.mediawiki.org/wiki/Parsoid#The_Parsoid_web_API. In the longer term it will be replaced with a more general MediaWiki content API that we are still working on.,1384293539,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,"The PHP parser output is exposed through action=parse:
+
+http://en.wikipedia.org/w/api.php?action=parse&redirects&prop=text%7Cdisplaytitle&format=xml&page=FOOBAR",1378248026,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Marco and I are taking this on.,1377273791,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Bumped the prority. We should get to this after Wikimania.,1375927194,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,Building prod. tools based on Parsoid output (for example to produce offline snasphots) needs this MW API. http://parsoid.wmflabs.org/ can only be a temporary solution...,1373488881,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Expose a parsoid public web API end point in the MediaWiki API,"(In reply to comment #0)
+> * HTML DOM saving: POST a modified DOM and a summary, and save it as a new
+> revision.
+
+Just to clarify, we don't need this for June/July (we're doing it in VisualEditor currently) - though it's a nice-to-have. :-)
+
+The real focus for us is the HTML DOM expansion, which we will want ASAP for templates and other generated content blocks.",1368669141,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lpywcmlyfhgff4artepd,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Currently the VisualEditor linkes like this: [[Glas|Glases]]
+The German-language Wikipedia prefers this though: [[Glas]]es
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51438
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49940
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52240",1368551520,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_description,open
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#4223170, @Bencemac wrote:
+> @Cirdan I mean it should fix the [[ https://tools.wmflabs.org/checkwiki/cgi-bin/checkwiki.cgi?project=enwiki&view=only&id=64 | existing ones ]]. So if somebody edit an article with `[[text|text]]`, the software would fix that (like AWB does). It could slowly but surely solve the problem.
+
+As @Cirdan says, Parsoid and the visual editor try very hard to avoid changing wikitext that already exists in the article. Different wikis have different conventions, and the most reliable way to respect those conventions is to avoid digging into bits of wikitext that don't relate directly to what the user has done.
+
+The visual editor is not intended to be a general purpose wikitext cleanup tool. As you suggest, AWB is good for that.",1527075466,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"I'm not a VE developer, but from what I learned from reporting Parsoid bugs, the VE/Parsoid try very hard to //not// alter existing wikitext. This is where quite a few of the copy & paste bugs come from.
+
+I believe syntax cleaning should be done by bots which are controlled by the local community, not through VE.",1527054738,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"@Cirdan I mean it should fix the [[ https://tools.wmflabs.org/checkwiki/cgi-bin/checkwiki.cgi?project=enwiki&view=only&id=64 | existing ones ]]. So if somebody edit an article with `[[text|text]]`, the software would fix that (like AWB does). It could slowly but surely solve the problem.",1527015724,PHID-USER-qdbrv6swdxlgemqwwbuw,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#4223073, @Bencemac wrote:
+> @Esanders I think the idea (Visual Editor should fix automatically `[[text|text]]`) could be a goal and it would have an own task. This task is related, but it is not exactly what I suggested.
+
+The problem with `[[text|text]]` was resolved in {T153107}. If it has re-appeared, that task should be re-opened. From what you wrote in [[T195215#4220491]], the problem is link trail detection/generation, which is what this task is about.",1527015152,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"@Esanders I think the idea (Visual Editor should fix automatically `[[text|text]]`) could be a goal and it would have an own task. This task is related, but it is not exactly what I suggested.",1527013628,PHID-USER-qdbrv6swdxlgemqwwbuw,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"There are several similar reports.
+
+One thing is shortening the overall link to make it easier to spot and read in wikitext, it is less cluttered, and that is a good reason to enforce use of linktrail.
+
+Use of linktrail can also be troublesome. Assume a link using one inflected word, where the inflection goes in the linktrail. Then the links are changed to another page title, but that page title has another inflection. To detect this and change it accordingly with the current bot frameworks are pretty difficult.
+
+In English plural of `book` is `books`, but in Norwegian this is `bok`and `bøker`. 
+
+Note that use of linktrail is an indication of a deeper problem. It should be possible for the writer to inflect the links themselves. That is instead of [[book]]s they should be able to write [[books]].
+
+The page titles are usually of a normalized form, and rewriting a link into this normalized form is pretty strightforward. In some cases there are alternate normalized forms, but as long as all of them identify the same page there should be no real problem. Only if different inflections targets different pages would there be a problem.",1517057368,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"There are several similar reports.
+
+One thing is shortening the overall link to make it easier to spot and read in wikitext, it is less cluttered, and that is a good reason to enforce use of linktrail.
+
+Use of linktrail can also be troublesome. Assume a link using one inflected word, where the inflection goes in the linktrail. Then the links are changed to another page title, but that page title has another inflection. To detect this and change it accordingly with the current bot frameworks are pretty difficult.
+
+Note that use of linktrail is an indication of a deeper problem. It should be possible for the writer to inflect the links themselves. The page titles are usually of a normalized form, and rewriting a link into this normalized form is pretty strightforward. In some cases there are alternate normalized forms, but as long as all of them identify the same page tere should be no real problem. Only if different inflections targets different pages would there be a problem.",1517056634,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"There are several similar reports.
+
+One thing is shortening the overall link to make it easier to spot and read in wikitext, it is less cluttered, and that is a good reason to enforce use of linktrail.
+
+Note that use of linktrail is an indication of a deeper problem. It should be possible for the writer to inflect the links themselves. The page titles are usually of a normalized form, and rewriting a link into this normalized form is pretty strightforward. In some cases there are alternate normalized forms, but as long as all of them identify the same page tere should be no real problem. Only if different inflections targets different pages would there be a problem.",1517055772,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"There are several similar reports,.
+
+One thing is shortening the overall link to make it easier to spot and read in wikitext, it is less cluttered, and that is a good reason to enforce use of linktrail.
+
+Note that use of linktrail is an indication of a deeper problem. It should be possible for the writer to inflect the links themselves. The page titles are usually of a normalized form, and rewriting a link into this normalized form is pretty strightforward. In some cases there are alternate normalized forms, but as long as all of them identify the same page tere should be no real problem. Only if different inflections targets different pages would there be a problem.",1517055748,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Since there was another [[ https://de.wikipedia.org/w/index.php?diff=173370165&oldid=173263938&title=Wikipedia:Technik/Text/Edit/VisualEditor/R%C3%BCckmeldungen | complaint]] on the de-wp VE feedback page, I'm reviving this bug report. [[ https://de.wikipedia.org/w/index.php?diff=173369735&oldid=159649392 | Here ]] the previously correctly formatted link 
+```
+[[Baudenkmal]]e
+```
+was converted to
+```
+[[Baudenkmal|Baudenkmale]]
+```
+
+Is there any hope that this problem will be fixed soon? If that's not possible, a brief explanation of why it is difficult (which we can relay to our community when this question comes up) would be helpful.",1517047661,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Since there was another [[ https://de.wikipedia.org/w/index.php?diff=173370165&oldid=173263938&title=Wikipedia:Technik/Text/Edit/VisualEditor/R%C3%BCckmeldungen | complaint]] on the de-wp VE feedback page, I'm reviving this bug report. [[ https://de.wikipedia.org/w/index.php?diff=173369735&oldid=159649392 | Here ]] the previously correctly formatted link 
+```
+[[Baudenkmal]]e
+```
+was converted to
+```
+[[Baudenkmal|Baudenkmale]]
+```
+
+Is there any hope that this problem will be fixed soon?",1517047576,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#2874249, @Cirdan wrote:
+> Thanks for the clarification. This specific case of this bug understandably decreases acceptance of the VisualEditor on de-wp, whereas the general problem regarding trailing characters is generally seen as acceptable. I asked several complaining users to provide more diffs of this specific case which I will add here.
+
+Let us unmerge T153107, retitle it, and add diffs there. [[Foo|Foo]] shouldn't be happening and is either a regression or a corner case in the HTML or something else going on that we have some missed all this while.",1481751088,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Thanks for the clarification. This specific case of this bug understandably decreases acceptance of the VisualEditor on de-wp, whereas the general problem regarding trailing characters is generally seen as acceptable. I asked several complaining users to provide more diffs of this specific case which I will add here.",1481750714,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#2870576, @Cirdan wrote:
+>> VE is an HTML editor. What kind of clean-up of HTML do you expect VE to do that would affect this?
+> 
+> Not HTML, but apparently editing pages with the VE creates links like 
+> ```
+> [[Target|Target]]
+> ```
+> in the Wikitext. I would assume that before Wikitext is saved (or delivered to the user), this is automatically cleaned to
+> ```
+> [[Target]]
+> ```
+
+Parsoid currently has code to generate simple links where necessary, but, clearly there was a bug that affected the diff you highlighted in T153107. But, in general, Parsoid does generate [[Foo]] instead of [[Foo|Foo]].",1481664094,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"> VE is an HTML editor. What kind of clean-up of HTML do you expect VE to do that would affect this?
+
+Not HTML, but apparently editing pages with the VE creates links like 
+```
+[[Target|Target]]
+```
+in the Wikitext. I would assume that before Wikitext is saved (or delivered to the user), this is automatically cleaned to
+```
+[[Target]]
+```
+",1481663806,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#2870216, @Cirdan wrote:
+>>> How is it possible that the parser does not detect two identical strings as identical?
+>> Your question assumes that it is looking for that. I don't know whether it is.
+> 
+> I just looked through what I believe to be the relevant parts of the source code, and it indeed seems that this is not how Parsoid handles this. I haven't looked at the VE implementation though. Is there no general cleanup at the end of a VE editing session?
+
+VE is an HTML editor. What kind of clean-up of HTML do you expect VE to do that would affect this?",1481662022,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">> How is it possible that the parser does not detect two identical strings as identical?
+> Your question assumes that it is looking for that. I don't know whether it is.
+
+I just looked through what I believe to be the relevant parts of the source code, and it indeed seems that this is not how Parsoid handles this. I haven't looked at the VE implementation though. Is there no general cleanup at the end of a VE editing session?
+
+",1481658837,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,">>! In T50463#2870045, @Cirdan wrote:
+> Jdforrester-WMF, thanks for merging T153107. Could you elaborate how these two are related?
+
+They are both issues where Parsoid is apparently creating wikitext sub-optimally.
+
+> How is it possible that the parser does not detect two identical strings as identical?
+
+Your question assumes that it is looking for that. I don't know whether it is.",1481657441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Jdforrester-WMF, thanks for merging T153107. Could you elaborate how these two are related? How is it possible that the parser does not detect two identical strings as identical?",1481657102,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,See also Change-Id: I78c8fc87be1777f63c84f8945ead1cc54161fb76,1374487741,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372933998,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"(In reply to comment #1)
+> Parsoid issue, moving to Parsoid.
+> 
+> Would like some input from James as to what he believes the behavior should
+> be (piped links always? linktrails where possible? configurable either way?).
+
+Canonically, linktrails should be preferred where possible (so, whenever a case-sensitive substring; except when on a $wgCapitalLinks=true, where it's a tad more complicated). I believe that linkheads should also be preferred where possible for the languages for which that applies.",1368771151,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+Parsoid: Links created with VE are piped links even when linktrail could be used,"Parsoid issue, moving to Parsoid.
+
+Would like some input from James as to what he believes the behavior should be (piped links always? linktrails where possible? configurable either way?).",1368770935,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-arvnl4rgkbslvicqgsmj,task_subcomment,NA
+VisualEditor: Green striped area doesn't align properly in Monobook,"When VisualEditor comes across a part of a page it can't edit, it adds a green striped area. However, VisualEditor seems to have very bad aim in Monobook. Screenshots forthcoming.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1368498360,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-vgio4d23zmdnqxwyja3n,task_description,resolved
+VisualEditor: Green striped area doesn't align properly in Monobook,We did a bit of a re-write of how the phantoms appear in the last push; glad this fixed it. :-),1370362551,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vgio4d23zmdnqxwyja3n,task_subcomment,NA
+VisualEditor: Green striped area doesn't align properly in Monobook,This appears to be fixed.,1370356051,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-vgio4d23zmdnqxwyja3n,task_subcomment,NA
+VisualEditor: Green striped area doesn't align properly in Monobook,"Created attachment 12310
+VisualEditor using the Monobook skin on mediawiki.org; incorrect behavior
+
+https://www.mediawiki.org/wiki/MobileFrontend/Photo_upload/Analysis?useskin=monobook&veaction=edit
+
+**Attached**: {F10761}",1368498533,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-vgio4d23zmdnqxwyja3n,task_subcomment,NA
+VisualEditor: Green striped area doesn't align properly in Monobook,"Created attachment 12309
+VisualEditor using the Vector skin on mediawiki.org; correct behavior
+
+https://www.mediawiki.org/wiki/MobileFrontend/Photo_upload/Analysis?useskin=vector&veaction=edit
+
+**Attached**: {F10760}",1368498417,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-vgio4d23zmdnqxwyja3n,task_subcomment,NA
+Enable VisualEditor on all content namespaces on mediawiki.org,"Currently VisualEditor is only enabled on the user/main namespaces on mediawiki.org. It'd be nice if it were enabled on all namespaces on mediawiki.org.
+
+Perhaps test.wikipedia.org and test2.wikipedia.org as well.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1368497580,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-azvy6g4nbj2z6hw5ydsm,task_description,resolved
+Enable VisualEditor on all content namespaces on mediawiki.org,Now complete.,1369075886,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-azvy6g4nbj2z6hw5ydsm,task_subcomment,NA
+Enable VisualEditor on all content namespaces on mediawiki.org,Related URL: https://gerrit.wikimedia.org/r/63621 (Gerrit Change I1c18ff72265ed4a33c5114141d5d97301e85c2e3),1368499865,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-azvy6g4nbj2z6hw5ydsm,task_subcomment,NA
+VisualEditor: Round-trip failures,"Bad diff from VisualEditor on mediawiki.org, 2013-05-13
+
+Go to <https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals>. Click ""edit"". VisualEditor form loads. Add a space after the sentence ""that drive editor engagement;"". Remove the space. Click ""Review and save"".
+
+Expected behavior: a diff showing no changes at all (space was added to the end of the line and then removed).
+
+Current behavior: see attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10742}",1368496740,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6r6iwczgdw2x3g22idm6,task_description,resolved
+VisualEditor: Round-trip failures,"We did a bunch of changes to avoid dirty-diffs with Parsoid; though there may be a few outstanding, I think we've got most of them licked, so closing.",1371867377,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+VisualEditor: Round-trip failures,Seems to have been fixed since the filing of this bug. Can you still reproduce this?,1371865706,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+VisualEditor: Round-trip failures,"(In reply to comment #2)
+> Are Parsoid/VisualEditor versions exposed somewhere?
+
+[[mw:Special:Version]] :-) In general, VisualEditor is branched for production at the same time as MediaWiki core right now (so, fortnightly for the rest of this month, thereafter weekly); Parsoid is updated in production more frequently but less regularly, as it's a manual process.
+
+> Or alternately, is there a public wiki running the most up-to-date version
+> of VisualEditor?
+
+No, I don't think so (but isn't beta meant to run master of everything?). Perhaps I should make a bug to build one in Labs.
+
+> I really don't like wasting my time filing bugs that no longer exist. :-/
+
+The perils of testing software that gets a dozen or so bugs fixed each week, sadly. In this particular case, I'm assuming that it's a Parsoid bug that was fixed (as I can't see anything in our git log that would suggest a VE fix changing this behaviour). Sorry!",1368979421,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+VisualEditor: Round-trip failures,"(In reply to comment #1)
+> I played around a bit locally while on the plane and tried to reproduce on
+> master from the screenshot.
+
+Blergh. I can still definitely reproduce this issue on mediawiki.org following the steps in comment 1.
+
+Are Parsoid/VisualEditor versions exposed somewhere? Or alternately, is there a public wiki running the most up-to-date version of VisualEditor? I really don't like wasting my time filing bugs that no longer exist. :-/",1368906585,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+VisualEditor: Round-trip failures,"I played around a bit locally while on the plane and tried to reproduce on master from the screenshot. I didn't reproduce your bug, but I found bug 48605 instead. Now that I have an internet connection again, I'll take a proper look at this bug once I've caught up on sleep.",1368896354,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6r6iwczgdw2x3g22idm6,task_subcomment,NA
+"VisualEditor: Categories with multiple ""../""s in their hrefPrefix broken","VisualEditor added ""../"" inside [[Category:QA]], breaking the link. I swear I didn't touch the category itself. I was just editing an unrelated paragraph.
+
+See https://www.mediawiki.org/w/index.php?title=Groups%2FProposals%2FFeatures_testing&diff=689563&oldid=689504
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368466500,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dga3eyvqthuwtl6xayui,task_description,resolved
+"VisualEditor: Categories with multiple ""../""s in their hrefPrefix broken","(In reply to comment #2)
+> We're going to put this into wmf4 with a Lightning Deploy this afternoon
+> rather
+> than wait for wmf5; thanks for the catch, Quim!
+This is now done.",1368487340,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dga3eyvqthuwtl6xayui,task_subcomment,NA
+"VisualEditor: Categories with multiple ""../""s in their hrefPrefix broken","We're going to put this into wmf4 with a Lightning Deploy this afternoon rather than wait for wmf5; thanks for the catch, Quim!",1368471008,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dga3eyvqthuwtl6xayui,task_subcomment,NA
+"VisualEditor: Categories with multiple ""../""s in their hrefPrefix broken",Related URL: https://gerrit.wikimedia.org/r/63496 (Gerrit Change I84d2b23a05585890b2d5023c7c7f38a43889fd7f),1368468797,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dga3eyvqthuwtl6xayui,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,"Any plans of having JSCover (JavaScript code coverage analysis) being integrated and run by Jenkins (in away that is usable for core and extensions as well)?
+
+[1] http://tntim96.github.io/JSCover/
+
+[2] http://tntim96.github.io/JSCover/example-qunit/out/jscoverage.html?test/index.html
+
+[3] http://tntim96.github.io/JSCover/manual/manual.xml#automatingPhantomJS
+
+[4] http://tntim96.github.io/JSCover/manual/manual.xml#automatingAnt
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1368310740,PHID-USER-ldehclaehsvglrqxywsj,False,PHID-TASK-irkp2njalgjutggxseff,task_description,declined
+Jenkins: Set up JavaScript code coverage analysis,"JSCover didn't work out very well.
+
+I've standardised on istanbul[1] for the moment. There are qunit[2] and karma[3] integrations. Both of which we've been using for OOjs and VisualEditor these past few months.
+
+They have command-line and HTML reporters.
+
+[1]
+http://gotwarlost.github.io/istanbul/
+https://github.com/gotwarlost/istanbul
+
+[2]
+https://github.com/asciidisco/grunt-qunit-istanbul
+
+[3]
+https://github.com/karma-runner/karma-qunit
+https://github.com/karma-runner/karma-coverage",1411761995,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,Javascript coverage is still something we need. Nobody looked at integrating it in Jenkins yet though.,1383584273,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,I'm not sure this will get any attention in a foreseeable future therefore closing this one.,1383363539,PHID-USER-txixdzq7tyya37eageyl,False,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,"**tntim96** wrote:
+
+The JSCover JAR (JSCover-all.jar) is all custom code and only includes the Rhino library (i.e. no Jetty, Log4J, Apache-commons or other library dependencies).
+
+Also, there is no HTML parser. When a JavaScript file is requested via JSCover's web or proxy server, JSCover instruments the specified JavaScript only. 
+
+Whether the HTML is generated dynamically or not doesn't affect JSCover in proxy-mode. 
+
+For proxy documentation, take a look at:
+http://tntim96.github.io/JSCover/manual/manual.xml#gettingStartedProxy
+
+...and a working proxy example at:
+https://github.com/tntim96/JSCover-samples/blob/master/src/test/java/jscover/webdriver/jasmine/WebDriverUnderscoreProxyTest.java
+
+Let me know if there are any changes required to JSCover that would assist you.",1378180020,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,"Both jscoverage and the new fork JSCover seem to have quite a nasty (though from a quick look, hard to avoid) implementation that involves instrumenting files. 
+
+Though that in and of itself isn't a problem, it does this by running a static file server and proxying javascript files through its instrumentor and using some kind of HTML parser (another Java class dependency) to catch inline scripts even (not sure).
+
+This isn't going to work straight up with MediaWiki since we generate HTML dynamically (e.g mediawiki-core/index.php) and load things through ResourceLoader.",1374001877,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+Jenkins: Set up JavaScript code coverage analysis,I think we want QUnit tests on a few more extensions before adding code coverage. Thus lowering priority.,1371757672,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-irkp2njalgjutggxseff,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Single newlines have no effect on the way a wiki page is displayed.
+So they should be ignored in a WYSIWYG editor.
+
+Example: Third line at http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services#Specification_progress_.26_TC_members",1368091860,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-o45i4q2kievixjidhsk7,task_description,open
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","On enwiki, one of the common uses of this is when people have a big {{Cite}} template and hit enter after it for readability.
+
+One thing having this character visible does is encourage experienced editors to delete it.
+
+When I was a newer editor, I had no idea what this character meant and it took me awhile to figure it out.
+
+Anyway, I think leaving it as is (current behavior) or removing it from being seen in the visual editor without changing any wikitext would be acceptable options. I don't think ""silently strip"" is a good option.
+",1657957730,PHID-USER-qydb7ytmqqctg7dn7fqa,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","That sounds very project-specific.  In my experience, line breaks (shown as '↵' in VisualEditor) on enwiki often mean that someone has copied and pasted the text from another document (e.g., written the text offline in a word processor).  It only rarely seems to be done intentionally.
+
+(Also, what if a line break someday stopped being interpreted as a space?)",1501341568,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Additional [[ https://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/R%C3%BCckmeldungen#Zeichen_.27.E2.86.B5.27_taucht_in_Abs.C3.A4tzen_im_VisualEditor_auf.2C_wird_aber_nicht_erkl.C3.A4rt | feedback from a German editor]] regarding this issue:
+""Wikipedians delete the '↵' in VisualEditor and replace it with a space. But this character '↵' only indicates that a break was added to the source for better readability, which is automatically translated into a space. It's often used in long citation blocks, for example. This' ↵'-character makes the Wikitext / source text more readable. The good readability of the source text in the source editor (Edit window) is still one of the quality indicators explicitly mentioned in our guidelines for good articles. The meaning in the VisualEditor is only that the user should insert a new text not to the left but to the right of the '↵' character. Just simply so that the line break in the source text remains directly behind the left character. But, when looking at the instructions, this subtlety is not mentioned. Also, no warning is displayed when you delete the '↵' character in the VisualEditer. Apparently the character can not be inserted in the VirtualEditor any more, if it was deleted. [...] I would hope that there is a warning when deleting the character or a tooltip when the mouse is hovering above the character. Thank you.""",1501320721,PHID-USER-kuuo2hpmktiqobsevyw6,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","@Jdforrester-WMF let me try to rephrase to see if I understand, the
+carriage return symbol is shown in VE because a wikitext editor has
+included a line break in the editing environment to increase readability of
+the wikitext, however this does not affect the presentation of the content
+in read mode, and is meaningless and confusing to VE editors.
+
+However there is a worry (by whom?) that not showing the character at all
+would make it much easier for a VE editor to accidentally remove the
+character because it has no visual representation. On the other hand
+visualizing it as an actual line-break causes inconsistency between edit
+and read modes (which currently exists in wikitext/read more)
+
+Is that summary clear and factual?
+
+
+
+*Jared Zimmerman * \\  Director of User Experience \\ Wikimedia Foundation
+
+M +1 415 609 4043 \\ @jaredzimmerman <http://loo.ms/g0>",1425063560,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",">>! In T50290#1074137, @Jaredzimmerman-WMF wrote:
+> Unless I'm misunderstanding Whatamidoing, I think they mean that we copy
+> line breaks in as actual linebreaks, so that reading and editing look the
+> same and no one actually sees that carriage return symbol ever.
+
+Yes, you're entirely missing the point here.
+
+* Actual reader-visible new paragraphs (from two new lines after each other in wikitext) are shown as new paragraphs.
+* Actual reader-visible line breaks (from a <br /> tag) are shown as line breaks.
+
+This is about how to represent the reader-invisible nonsense wikitext single new line. See T50290#499295 for details; nothing's changed here since May 2013.",1425062104,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Unless I'm misunderstanding Whatamidoing, I think they mean that we copy
+line breaks in as actual linebreaks, so that reading and editing look the
+same and no one actually sees that carriage return symbol ever.
+
+
+
+*Jared Zimmerman * \\  Director of User Experience \\ Wikimedia Foundation
+
+M +1 415 609 4043 \\ @jaredzimmerman <http://loo.ms/g0>",1425061938,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",">>! In T50290#1074123, @Whatamidoing-WMF wrote:
+> I like the idea of showing it as a line break.  This might make more sense to less-technical people that have just copy-pasted text out of another document (one of the apparent causes) than the insertion of an unexpected symbol.
+
+I'm not a fan of making VE less like the reading experience, though.",1425061657,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",I like the idea of showing it as a line break.  This might make more sense to less-technical people that have just copy-pasted text out of another document (one of the apparent causes) than the insertion of an unexpected symbol.,1425061578,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 57454 has been marked as a duplicate of this bug. ***,1415882814,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 68811 has been marked as a duplicate of this bug. ***,1406754254,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 65324 has been marked as a duplicate of this bug. ***,1401419217,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Indeed not WYSIWYG, but I happen to love this feature. I practically always remove these links when I see them. I'd say WONTFIX.",1400608205,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 50641 has been marked as a duplicate of this bug. ***,1394482866,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG",*** Bug 61569 has been marked as a duplicate of this bug. ***,1393537023,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","(In reply to comment #2)
+> Newline characters are more debatable, because some people use them to make
+> wikicode more readable.
+
+...and I remmember some people use them to make diffs more readable[citation needed].",1372607697,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Example of TAB characters:
+http://en.wikipedia.org/wiki/Refrigerator#Production_by_country",1368684670,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","Same for TAB characters, which are shown as ➞
+
+TAB characters have no meaning in wikicode, and I can't imagine anyone entering them for any purpose (plus they are difficult to enter in an HTML form).
+I have never seen a case where they are intended (please point me to any example if I am mistaken).
+
+I personally think TABs are a case where silent stripping would be acceptable.
+
+---
+
+Newline characters are more debatable, because some people use them to make wikicode more readable.",1368684616,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG","(In reply to comment #0)
+> Single newlines have no effect on the way a wiki page is displayed.
+> So they should be ignored in a WYSIWYG editor.
+> 
+> Example: Third line at
+> http://en.wikipedia.org/wiki/
+> Content_Management_Interoperability_Services#Specification_progress_.
+> 26_TC_members
+
+Yeah, this is a bit of a mess. In wikitext (except in some circumstances like <pre>s), \n is a whitespace character, rendered as either a space or as nothing depending on the things around it, but \n\n is ""</p><p>"".
+
+We could:
+
+* Silently strip non-conformant wikitext syntax like this on ingest, but this would mean that VisualEditor would not play well with other, wikitext-based users.
+
+* Show the newline as a line break in VisualEditor - in a way that (a) doesn't look like a new paragraph/context has started, and (b) doesn't look like <br />s will look, either, and in some way conveys the fact that it's different.
+
+* (Current behaviour) Show the newline as a special kind of character in VisualEditor - in a way that (a) doesn't look like a 'real' new line, because it isn't.
+
+* Silently not show the new line as such (but instead as… a space?), which is prone to having users accidentally alter them without intention, again causing problems for intermixed VisualEditor and wikitext editor sessions.
+
+What are your thoughts?",1368110457,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o45i4q2kievixjidhsk7,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
+Put the cursor somewhere in the text.
+Type ""Enter"" 2 times.
+Type ""Backspace"" 2 times.
+
+Expected: as original
+Actually: The newlines remain
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368089280,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-2f2dgqt54eqesg4exgwo,task_description,resolved
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox",This is now fixed in live.,1370445778,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","Just reproduced on Firefox 21.0 / fresh install of Ubuntu Linux 2013.04
+Nothing special appears in the web console.",1369662058,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox",Browser information highly welcome. Reopening for the time being.,1369661193,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","When will the master fixes be deployed?
+The situation is now horrible in production, with so many bugs that I am wondering whether it is even worth reporting them...",1369635503,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","I just tried, it is a worse problem now, text is lost.",1369277166,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+"VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox","**orbit** wrote:
+
+I'm not able to reproduce this one either. I experience other problems relating to Enter and Backspace on Firefox (fixed in Master) but not what you've described. I'm going to close this ticket, but please reopen if you have additional information.",1369260407,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2f2dgqt54eqesg4exgwo,task_subcomment,NA
+PostEdit: Core-ify this,"As discussed with Steven W. just now, we should move this into MW core (so, amongst other things, VisualEditor can depend on it and not have to re-invent the wheel).
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=16066",1368050160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ju6nd3s77iuekvlfhra5,task_description,resolved
+PostEdit: Core-ify this,"That's a cherry-pick back to wmf5, so no wikis that currently have PostEdit will lose it when we disable the extension.",1370051316,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,Related URL: https://gerrit.wikimedia.org/r/66316 (Gerrit Change I01cfc0630c3a505af82922844b5e70c1d61f3c1d),1370051236,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,"(In reply to comment #1)
+> Related URL: https://gerrit.wikimedia.org/r/66137 (Gerrit Change
+> I01cfc0630c3a505af82922844b5e70c1d61f3c1d)
+
+Merged.",1370049933,PHID-USER-r7wrkcx7j2vutqs6hr3g,True,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,"Just for posterity, I'm noting bug 16066 here.",1369960333,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,"(In reply to comment #2)
+> I should note that one extension depending on another is *not* a legitimate
+> reason for moving the dependency into the core. That said, I still agree with
+> the merging of this extension since it's a trivial feature.
+
+Yes, I agree completely. There had already been wide agreement that this should be moved into core; the VisualEditor requirement is just a spur.",1369941490,PHID-USER-r7wrkcx7j2vutqs6hr3g,True,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,"(In reply to comment #0)
+> As discussed with Steven W. just now, we should move this into MW core (so,
+> amongst other things, VisualEditor can depend on it and not have to re-invent
+> the wheel).
+
+I should note that one extension depending on another is *not* a legitimate reason for moving the dependency into the core. That said, I still agree with the merging of this extension since it's a trivial feature.",1369941304,PHID-USER-ea6gwat27oulytc5tvsy,True,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+PostEdit: Core-ify this,Related URL: https://gerrit.wikimedia.org/r/66137 (Gerrit Change I01cfc0630c3a505af82922844b5e70c1d61f3c1d),1369937979,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ju6nd3s77iuekvlfhra5,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","We use textarea which means that browsers don't suggest text from previous uses.
+
+**See Also**:
+{T53903}
+{T54859}
+{T54085}",1368048660,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_description,resolved
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Do we consider this fixed now then ?,1561123591,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",It works nicely!,1558647083,PHID-USER-dcexrhjioxqqsq4pdrfe,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",It looks nice!,1558647068,PHID-USER-dcexrhjioxqqsq4pdrfe,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5135349, @Esanders wrote:
+> The above patch stops the first item being highlighted automatically. You can test the effect on live by pasting `ve.init.target.saveDialog.editSummaryInput.lookupHighlightFirstItem = false;` into the console after the save dialog has opened.
+
+This worked nicely. Thanks much!
+
+>>! In T50274#5209037, @matmarex wrote:
+> @izno Now done in <https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VisualEditor/+/512227>. I think we were still waiting for MediaWiki to be updated to use the new version of OOUI of something.
+
+Coolio.",1558646270,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",@izno Now done in <https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VisualEditor/+/512227>. I think we were still waiting for MediaWiki to be updated to use the new version of OOUI of something.,1558639964,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5136148, @Esanders wrote:
+>>>! In T50274#5135937, @Izno wrote:
+>> BTW since you're in the area there's a TODO there that was waiting on what is now a task that you closed a week or two ago.
+> 
+> Sorry, I'm not sure what you're referring to, can you provide a link?
+
+```lang=javascript
+	// HACK: Disable pending animation. Should be made an upstream option (T220204)
+	// Parent method
+```
+
+{T220204}
+",1556156399,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5136148, @Esanders wrote:
+>>>! In T50274#5135937, @Izno wrote:
+>> BTW since you're in the area there's a TODO there that was waiting on what is now a task that you closed a week or two ago.
+> 
+> Sorry, I'm not sure what you're referring to, can you provide a link?
+
+```lang=php
+	// HACK: Disable pending animation. Should be made an upstream option (T220204)
+	// Parent method
+```
+
+{T220204}
+",1556156352,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5135937, @Izno wrote:
+> BTW since you're in the area there's a TODO there that was waiting on what is now a task that you closed a week or two ago.
+
+Sorry, I'm not sure what you're referring to, can you provide a link?",1556142593,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5135349, @Esanders wrote:
+> The above patch stops the first item being highlighted automatically. You can test the effect on live by pasting `ve.init.target.saveDialog.editSummaryInput.lookupHighlightFirstItem = false;` into the console after the save dialog has opened.
+
+BTW since you're in the area there's a TODO there that was waiting on what is now a task that you closed a week or two ago.",1556136821,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Change 506191 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] EditSummaryWidget: Don't highlight first automatically
+
+[[https://gerrit.wikimedia.org/r/506191]]",1556126337,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",The above patch stops the first item being highlighted automatically. You can test the effect on live by pasting `ve.init.target.saveDialog.editSummaryInput.lookupHighlightFirstItem = false;` into the console after the save dialog has opened.,1556125232,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Change 506191 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] EditSummaryWidget: Don't highlight first automatically
+
+[[https://gerrit.wikimedia.org/r/506191]]",1556125155,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5135228, @LucasWerkmeister wrote:
+> Is it possible to opt out of this feature until that’s fixed?
+
+No, but it shouldn't be too hard to fix. In the meantime you can press escape before ctrl+enter.
+
+",1556124739,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5106435, @Trizek wrote:
+> Great feature. <3 
+> Can we have a way to delete misspelled sentences? Thanks!
+
+The edit summaries are pulled from the API and old edit summaries are immutable so I don't see an easy fix for this without using another storage system. Suggestions welcome.",1556124638,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5107339, @Izno wrote:
+> My only problem: when I have entered a summary, the drop down appears. When I hit the hotkeys for save, the system will complete the summary with the top item whatever the value of my original summary was. (This is not how it works in old WTE.)
+
+This is a //big// problem for me as well. My most common summary on talk pages or project discussion pages is just “reply”, but the first suggestions are all like “reply (something something)”, “reply, something else”, etc. When I press Ctrl+Enter out of habit – for years, VisualEditor has trained me that Ctrl+Enter in the summary field means “save” – then it will “complete” my edit summary with some gibberish that makes no sense in the current context, and if I don’t notice it I’ll save an edit with a nonsense summary.
+
+Is it possible to opt out of this feature until that’s fixed?",1556123623,PHID-USER-7raa3vx5zsq6a56gil3q,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5107851, @Whatamidoing-WMF wrote:
+>>>! In T50274#5106435, @Trizek wrote:
+>> Great feature. <3 
+>> Can we have a way to delete misspelled sentences? Thanks!
+> 
+> No.  But if you make 200 more edits, it'll automagically go away.  The tool only looks back at your most recent 200 edit summaries.
+
+So I have to be patient. And be careful: I've already accidentally entered some bad summaries while editing. :/",1555530842,PHID-USER-fptvc452oby6t6mwcy2u,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5107874, @Whatamidoing-WMF wrote:
+> 
+> (In the meantime, the workaround is to hit the Escape key.)
+
+(And then hit Ctrl + Enter again.)",1555098678,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5107874, @Whatamidoing-WMF wrote:
+> @Esanders, Izno's problem is going to drive me nuts.  When there's an exact match, it needs to use that exact match, and not suggest something longer.  If I've typed `r`, and the options it finds are 35 instances of `r` and one of `Re-ping` in my last 200 edit summaries, then it should definitely be suggesting `r` and not the other longer one. 
+> 
+> (In the meantime, the workaround is to hit the Escape key.)
+
+(And then hit Ctrl + Enter again.)",1555098668,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","@Esanders, Izno's problem is going to drive me nuts.  When there's an exact match, it needs to use that exact match, and not suggest something longer.  If I've typed `r`, and the options it finds are 35 instances of `r` and one of `Re-ping` in my last 200 edit summaries, then it should definitely be suggesting `r` and not the other longer one. 
+
+(In the meantime, the workaround is to hit the Escape key.)",1555094625,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","@Esanders, Izno's problem is going to drive me nuts.  When there's an exact match, it needs to use that exact match, and not suggest something longer.  If I've typed `r`, and the options it finds are 35 instances of `r` and one of `Re-ping` in my last 200 edit summaries, then it should definitely be suggesting `r` and not the other longer one. ",1555094590,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5106435, @Trizek wrote:
+> Great feature. <3 
+> Can we have a way to delete misspelled sentences? Thanks!
+
+No.  But if you make 200 more edits, it'll automagically go away.  The tool only looks back at your most recent 200 edit summaries.",1555094341,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I agree, this is well done.
+
+My only problem: when I have entered a summary, the drop down appears. When I hit the hotkeys for save, the system will complete the summary with the top item whatever the value of my original summary was. (This is not how it works in old WTE.)
+
+The particular issue was that I wanted a summary of ""clean table"", but after having entered the entire thing in it removed the exact match and attempted to add the lengthier summary after hitting cntrl + enter, and then chose //not// to save. (The biggest win for me is that the hotkeys should always save regardless of the current value of the dropdown.)
+
+{F28628688}
+
+{F28628692}
+
+{F28629206}
+
+Happy to split this to a different task if it seems like a significant chunk of additional work...
+",1555081974,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I agree, this is well done.
+
+My only problem: when I have entered a summary, the drop down appears. When I hit the hotkey for save, the system will complete the summary with the top item whatever the value of my original summary was. (This is not how it works in old WTE.)
+
+The particular issue was that I wanted a summary of ""clean table"", but after having entered the entire thing in it removed the exact match and attempted to add the lengthier summary after hitting cntrl + shift + s, and then chose //not// to save. (The biggest win for me is that the hotkeys should always save regardless of the current value of the dropdown.)
+
+{F28628688}
+
+{F28628692}
+
+{F28629206}
+
+Happy to split this to a different task if it seems like a significant chunk of additional work...
+",1555080996,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I agree, this is well done.
+
+My only problem: when I have entered a summary, the drop down appears. When I hit the hotkey for save, the system will complete the summary with the top item whatever the value of my original summary was. (I am fairly certain this was not the behavior with non-VE editor.
+
+The particular issue was that I wanted a summary of ""clean table"", but after having entered the entire thing in it removed the exact match and attempted to add the lengthier summary after hitting cntrl + shift + s, and then chose //not// to save. (The biggest win for me is that the hotkeys should always save regardless of the current value of the dropdown.)
+
+{F28628688}
+
+{F28628692}
+
+{F28629206}
+
+Happy to split this to a different task if it seems like a significant chunk of additional work...
+",1555080704,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Great feature. <3 
+Can we have a way to delete misspelled sentences? Thanks!",1555059406,PHID-USER-fptvc452oby6t6mwcy2u,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Good job!,1555047671,PHID-USER-4nsetzljuvrlickb5xoz,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Wonderful and seems to be done,1555019166,PHID-USER-timi4nkerc272muhuatw,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Change 495451 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Edit summary autocomplete
+
+[[https://gerrit.wikimedia.org/r/495451]]",1554399877,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5016202, @Esanders wrote:
+> It doesn't appear to work yet in Chrome/FF: https://codepen.io/edg2s/pen/eXGdVM
+
+Nor in Safari.",1552404027,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",It doesn't appear to work yet in Chrome/FF: https://codepen.io/edg2s/pen/eXGdVM,1552338121,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#5012835, @gerritbot wrote:
+> Change 495451 had a related patch set uploaded (by Esanders; owner: Esanders):
+> [mediawiki/extensions/VisualEditor@master] Edit summary autocomplete
+> 
+> [[https://gerrit.wikimedia.org/r/495451]]
+
+Why doesn't this make use of T50274#4048873 ? It looks like Firefox, Webkit, and Chromium all support autocomplete (even though [[https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea | Mozilla.org]] indicates otherwise, the link to the Chromium indicates the bug is fixed since Jan 2018)...",1552151736,PHID-USER-yawytiq5q7eduxmvnkid,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Change 495451 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Edit summary autocomplete
+
+[[https://gerrit.wikimedia.org/r/495451]]",1552137996,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Proposed in [[https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Editing/Autocomplete_summaries_in_VisualEditor|Community Wishlist Survey]],1543326392,PHID-USER-dcexrhjioxqqsq4pdrfe,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","According to https://developer.mozilla.org/en-US/Firefox/Releases/59#HTML Firefox now supports autocompletion of textareas, so it should actually be possible to have native autocomplete suggestions, at least in Firefox.",1521014264,PHID-USER-tyjmn7xcw6s2b6rqagj7,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Proposed to #community-wishlist-survey-2017 ,1510324177,PHID-USER-dcexrhjioxqqsq4pdrfe,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#3234411, @Schnark wrote:
+> But neither will give results for users not logged in. Even if they have a static IP, `mw.user.getName()` will only return `null`.
+
+There are a bunch of features that don't work for logged-out users; I'd not worry too much about that.",1493924564,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",">>! In T50274#2137790, @Esanders wrote:
+> Fetch and filter recent commit messages:
+> 
+> https://gist.github.com/edg2s/f7db01d240ad3c83d183
+
+I don't think that `list: 'recentchanges'` is the best approach, as it will only give you summaries from the last month. When you are not very active, these are very few, so won't help much. In my script https://de.wikipedia.org/wiki/Benutzer:Schnark/js/veSummary.js, I instead decided to use `list: 'usercontribs'` instead.
+But neither will give results for users not logged in. Even if they have a static IP, `mw.user.getName()` will only return `null`.",1493889939,PHID-USER-tyjmn7xcw6s2b6rqagj7,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","A solution could also be HTML5 `contenteditable`, at least its support in browsers is acceptable. (see [[ http://stackoverflow.com/questions/13324822/autocomplete-with-contenteditable-div-instead-of-textarea-doesnt-seem-to-work | StackOverflow question about this topic ]])",1482075467,PHID-USER-dcexrhjioxqqsq4pdrfe,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","A solution could also be HTML5 `contenteditable`, at least its support in browsers is acceptable. (see [[ http://stackoverflow.com/questions/13324822/autocomplete-with-contenteditable-div-instead-of-textarea-doesnt-seem-to-work | StackOverflow question to this topic ]])",1482075451,PHID-USER-dcexrhjioxqqsq4pdrfe,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","A solution could also be HTML5 `contenteditable`, at least its support in browsers is acceptable. (see [[ http://stackoverflow.com/questions/13324822/autocomplete-with-contenteditable-div-instead-of-textarea-doesnt-seem-to-work | StackOverflow question to the topic ]])",1482075440,PHID-USER-dcexrhjioxqqsq4pdrfe,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(Actually, Chrome does support autocomplete=""street-address"", huh. But that doesn't really help us here, it doesn't remember and autocomplete values in textareas on its own and there doesn't seem to be a way to make it do that.)",1481761162,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","It's not possible to make <input> wrap. If anything, it could be possible to make <textarea> have autocomplete (nothing in the spec prohibits it, the attribute [[ https://html.spec.whatwg.org/multipage/forms.html#the-textarea-element| is valid on textarea]] and the new 'autocomplete' values include [[https://html.spec.whatwg.org/multipage/forms.html#attr-fe-autocomplete-street-address| one that is only valid on multiline content]]). But no browser seems to actually support this.",1481760141,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(That was https://gerrit.wikimedia.org/r/#/c/212795/, it tried to dynamically swap between <input type=text> and <textarea>.)",1481759634,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Bartosz had a go at this a few years ago, but then I pointed out some IME issues and he gave up. I think my API approach is probably the simplest.",1481759433,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","How plausible would it be to use `input` but magically make it word wrap, even though the HTML spec says it mustn't?",1481754213,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",Raising priority now that we have the same problem in VE source mode (NWE).,1481754015,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I have a (very hackish) user script for providing access to previous edit summaries: https://de.wikipedia.org/wiki/Benutzer:Schnark/js/veSummary.js If anybody wants to use code from there to fix this in VE itself, feel free to do so.",1473756944,PHID-USER-tyjmn7xcw6s2b6rqagj7,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Fetch and filter recent commit messages:
+
+https://gist.github.com/edg2s/f7db01d240ad3c83d183",1458492511,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","I think this should be low priority. Only power users need quick access to commonly used edit summaries, and these power users will by definition know OS-wide tools like autohotkey or ditto which can do the job much more comfortably.",1387232471,PHID-USER-zzvqlvm6i6kml4tfnqvq,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","The main threads in VE/F:
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_05#Edit_summaries_have_no_.27memory.27
+and
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_06#Predictive_texting_in_edit_summaries
+and
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_06#Edit_summaries_-_menu_of_recently-used.3F
+and
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Speed.2C_Edit_Summary.2C_and_Limitations
+
+
+
+Closely related are:
+
+Bug 42139 (""There is no preview of edit summaries"") - Wanted, so that we can test WP:shortcut links etc are correctly-targeted.
+
+Bug 50961 (""Provide simultaneous access to editor and edit summary"") - So that we don't have to remember everything we did, after a multitask edit.",1374776456,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #8)
+> A suggested list populated with recent edit summaries will be really useful
+> when VE is extended to talk namespace.
+
+We're not planning to make VisualEditor work with talk pages, but instead this will be done by Flow (which will use VisualEditor for editing content).
+
+That said, we still think this would be valuable, and it's definitely in our plans.",1373481862,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","A suggested list populated with recent edit summaries will be really useful when VE is extended to talk namespace. Almost every time I close an RfD as something other than delete, I make an edit to the redirect's talk page with the summary ""Noting old RFD"" or ""Note old RFD and tag for relevant WikiProjects"" (depending whether they are already tagged or not).",1373479736,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #6)
+> (In reply to comment #1)
+> > ...or implement our own autocomplete?
+> 
+> However, just brainstorming, to address Raimond's use-case in comment 3, it
+> may
+> be possible to query the most recent X edit summaries a user has used and
+> implement a suggestion feature based on those. That might cover the repeated
+> edits use-case.
+
+That's pretty much what I meant. The autocomplete would populate from recent commit messages, or they would just be shown in a dropdown.",1371146265,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #1)
+> ...or implement our own autocomplete?
+
+It depends what the use-case is. Personally, I like the current multi-line input and my browser stopped remembering my inputs for <input>s long ago (perhaps when I switched from Firefox to Chrome).
+
+However, just brainstorming, to address Raimond's use-case in comment 3, it may be possible to query the most recent X edit summaries a user has used and implement a suggestion feature based on those. That might cover the repeated edits use-case.",1371079046,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Rephrased bug summary. ""textbox"" doesn't exist. There is ""input"" and ""textarea"" both are ""form fields"".",1370829536,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #3)
+> Browser's autosuggestion/complete is the most used function during editing
+> Wikipedia, especially when I do similar edits. Every time I test the VE is
+> miss this function because the field is a textarea instead of an input field.
+> It's really annoying to type every time the summary instead of selecting out of
+> previous summaries.
+
+Sure, but this functionality isn't possible for proper editable surfaces with rich text, links and other HTML items that these fields will allow.",1368992892,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","Browser's autosuggestion/complete is the most used function during editing Wikipedia, especially when I do similar edits. Every time I test the VE is miss this function because the field is a textarea instead of an input field. It's really annoying to type every time the summary instead of selecting out of previous summaries.",1368991970,PHID-USER-3uecblbxq24ycewm2cog,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used","(In reply to comment #1)
+> ...or implement our own autocomplete?
+
+Possibly. Given that we are intending to replace this wikitext field with a full VE micro-surface (with the limited scope that log entries allow), that might be a bit fiddly, though. There's also not currently a useful API to query ""useful edit summaries"" from. Marking as a longer-term consideration.",1368979017,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used",...or implement our own autocomplete?,1368903301,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-rc4yhxp2tlzilezhonck,task_subcomment,NA
+"VisualEditor: Alienation shield for images in table are not the right size, so images are still clickable","Images in a table are incompleted alienated and still clickable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Liste_der_Hochh%C3%A4user_in_Deutschland",1368003600,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-x7lpmfetdbteus26qx4l,task_description,resolved
+"VisualEditor: Alienation shield for images in table are not the right size, so images are still clickable","(In reply to comment #0)
+> Images in a table are incompleted alienated and still clickable.
+
+This is fixed by the new image code which will be coming very soon (but is delayed to finish editing image properties). Marking as a dupe of that bug.
+
+*** This bug has been marked as a duplicate of bug 37870 ***",1369093449,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-x7lpmfetdbteus26qx4l,task_subcomment,NA
+VisualEditor: Don't close/re-open annotation when pasting text into a comparable context,"Not sure whether this is ContentEditable, DataModel or LinearModel.
+
+When pasting italicised text (from elsewhere on the same page) into an already italicised sentence we currently close, re-open, close, re-open that annotation.
+
+Steps to reproduce problem:
+* start with:
+  <p><i>Original text here.</i></p><p><i>Something else there.</i></p>
+* select ""else""
+* copy
+* select ""text""
+* paste to replace
+* end state:
+  <p class=""ve-ce-branchNode""><i class=""ve-ce-TextStyleAnnotation ve-ce-TextStyleItalicAnnotation"">Original </i><i class=""ve-ce-TextStyleAnnotation ve-ce-TextStyleItalicAnnotation"">else</i><i class=""ve-ce-TextStyleAnnotation ve-ce-TextStyleItalicAnnotation""> here.</i></p>
+
+Now this wouldn't be a major issue (merely inefficient) if it weren't for bug 48194 in Parsoid.
+
+Real example:
+* Intended edit: https://www.mediawiki.org/w/index.php?title=Watchlist_wishlist&diff=686477&oldid=686247
+* Actual edit as seen in the Review and save dialog of VisualEditor (and saved as-is): https://www.mediawiki.org/w/index.php?title=Watchlist_wishlist&diff=686475&oldid=686247
+
+--------------------------
+**Version**: unspecified
+**Severity**: critical",1367894520,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-altic2tebpor7cfydf6y,task_description,resolved
+VisualEditor: Don't close/re-open annotation when pasting text into a comparable context,*** Bug 48489 has been marked as a duplicate of this bug. ***,1368726943,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-altic2tebpor7cfydf6y,task_subcomment,NA
+VisualEditor: Don't close/re-open annotation when pasting text into a comparable context,Confirmed on mediawiki.org,1368554438,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-altic2tebpor7cfydf6y,task_subcomment,NA
+VisualEditor: Don't close/re-open annotation when pasting text into a comparable context,"Timo, can you confirm this in master? I think it's been fixed by Ed's change to how annotations are compared…",1368228767,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-altic2tebpor7cfydf6y,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,"* Create an English article with a <ref> tag at the end of a paragraph
+* Set $wgLanguageCode = 'en-rtl';
+* View the article. You'll see something like ]My text[1 (this rendering seems wrong)
+* Edit the article in VE. The non-contiguous reference causes problems:
+** The phantom is rendered wrongly so it's not visible
+** When you select the reference, the selection looks really strange
+
+Should we wrap things in a <bidi> tag or whatever to ensure better rendering?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367879940,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ix6ll4i6ezero6wug475,task_description,resolved
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,Merged; closing.,1369783170,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,Assigning to Moriel then. :-),1367887908,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,"And it was Roan who suggested, and Krinkle who participating in the attempt of helping me understand.. THANKS for that!",1367883167,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,Related URL: https://gerrit.wikimedia.org/r/62540 (Gerrit Change I319285d23a4f0a0522cc793f1a6661cda31a1ebf),1367882987,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode,"This is a CSS fix in the Cite extension. https://gerrit.wikimedia.org/r/#/c/61634/
+
+As Krinkle suggested, I'm fixing a small detail again (position 'top') but updating the Cite extension should fix this problem. I'll link the new correction to this bug and submit the fix shortly.",1367881902,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-ix6ll4i6ezero6wug475,task_subcomment,NA
+VisualEditor: JS error on (null) diffing [[BMW 801]] but only if debug=false,"Make a null edit (space and backspace), then trigger a diff. JS error thrown in Firefox but not Chrome:
+
+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
+
+However, for debug=true, no such error occurs. Is this just going to be a transient RL issue?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1367874000,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bdvf6u5xglbisa5hqfhd,task_description,resolved
+VisualEditor: JS error on (null) diffing [[BMW 801]] but only if debug=false,*** Bug 48193 has been marked as a duplicate of this bug. ***,1368023940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bdvf6u5xglbisa5hqfhd,task_subcomment,NA
+VisualEditor: JS error on (null) diffing [[BMW 801]] but only if debug=false,"This has been fixed for me in FF since yesterday evening. From chatting with Roan last night I think it was a deployment / ResourceLoader issue.
+
+Resolving as fixed.",1367972703,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-bdvf6u5xglbisa5hqfhd,task_subcomment,NA
+VisualEditor: JS error on (null) diffing [[BMW 801]] but only if debug=false,Happens in Chromium 26.0.1410.43 too.,1367874746,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-bdvf6u5xglbisa5hqfhd,task_subcomment,NA
+VisualEditor: Throttle or otherwise handle large copy-paste input,"I watched a user using Chrome paste a 32400-character buffer of special characters into VE.  Chrome became unresponsive. 
+
+This user then did that in multiple tabs and the entire computer became unresponsive.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367867040,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-o742mr6hjh6wsdblaanj,task_description,open
+VisualEditor: Throttle or otherwise handle large copy-paste input,Marking as an enhancement with normal priority (nice-to-have).,1367870640,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o742mr6hjh6wsdblaanj,task_subcomment,NA
+VisualEditor: Serve interface components as SVGs over PNGs to any browser which supports it,"(Provided we are happy with the rendering quality)
+
+Currently we only serve SVGs when window.devicePixelRatio > 1.
+
+On suggested test for SVG support is:
+
+document.createElementNS && document.createElementNS( 'http://www.w3.org/2000/svg', 'svg' ).createSVGRect
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367837220,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pgpcd7rvhd6x44lw4xo5,task_description,resolved
+VisualEditor: Serve interface components as SVGs over PNGs to any browser which supports it,Merged for wmf4.,1368135541,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pgpcd7rvhd6x44lw4xo5,task_subcomment,NA
+VisualEditor: Serve interface components as SVGs over PNGs to any browser which supports it,Related URL: https://gerrit.wikimedia.org/r/62959 (Gerrit Change Iafe8cd290fb195369776f51a96b6de4a51577b89),1368095219,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pgpcd7rvhd6x44lw4xo5,task_subcomment,NA
+VisualEditor: Serve interface components as SVGs over PNGs to any browser which supports it,Let's do this. Trevor says we're happy with the rendering quality and the device load for desktop; I suggest keeping the PNGs around for mobile clients.,1368050588,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pgpcd7rvhd6x44lw4xo5,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,"As the title says: when the VisualEditor is active, the drop down menu (p-caction) under Vector skin is dropped down behind the VE toolbar, making it impossible to click on. May be a simple z-index issue.",1367661720,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-6kpwltejynowd5ns5iud,task_description,resolved
+VisualEditor: Vector drop down menu hidden behind toolbar,Merged; thanks Kaldari! Will go out in wmf4.,1368205844,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,Assigning given that Kaldari's fixing it in core for us. :-),1368150497,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,Related URL: https://gerrit.wikimedia.org/r/63099 (Gerrit Change I61daea50209d040f7e0f71207a4e90998c15083f),1368146651,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,"Unfortunately, this was caused by the fix to bug 37158.
+https://gerrit.wikimedia.org/r/#/c/31288",1368144377,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,Also brought up here: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=553770320#Notifications_gadget.27s_z-index,1367845014,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Vector drop down menu hidden behind toolbar,"This also holds true for Echo, which also has z-index -100.",1367842628,PHID-USER-t4cbxxxhiswoecybwxy2,False,PHID-TASK-6kpwltejynowd5ns5iud,task_subcomment,NA
+VisualEditor: Table captions were alienated so looked wrong and couldn't be edited,"Expected layout
+
+I included two screenshots, illustrating the problem.
+
+Apple Safari 6, Mountain Lion
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/wiki/Meurchin
+
+**Attached**: {F10895}",1367650560,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-hg7swbc4ekjgxojfr5bz,task_description,resolved
+VisualEditor: Table captions were alienated so looked wrong and couldn't be edited,This is fixed in master (see gerrit 60940) and will be deployed to the English Wikipedia on Monday as part of the wmf3 roll-out. You can see how it should work in a test page on MediaWiki.org: https://www.mediawiki.org/wiki/VisualEditor:TableCaptionTest,1367681845,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hg7swbc4ekjgxojfr5bz,task_subcomment,NA
+VisualEditor: Table captions were alienated so looked wrong and couldn't be edited,"Created attachment 12258
+Content edit result
+
+**Attached**: {F10896}",1367650645,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-hg7swbc4ekjgxojfr5bz,task_subcomment,NA
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"In Firefox 20.0.1:
+
+1. Edit a page that has a bulleted list.
+2. Place the cursor on the first bullet item.
+3. Click the ""Bullet List"" button. The first bullet item loses its bullet. (Correct.)
+4. Click the ""Bullet List"" button a second time. The first bullet comes back (correct), but there is now a blank line displayed below it.
+
+Similarly, if you remove & add a bullet in the middle of the list, you get blank lines above AND below the item.
+
+Similarly, if you do this with a numbered list, the blank line breaks the numbering: the list items below the blank line start over from ""1"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367598960,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-yr7732vg2ebd5ndyalb6,task_description,open
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"FWIW, I also just checked OpenOffice.org, and they also simply remove and restore the bullet, keeping a single bulleted list.",1368137966,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-yr7732vg2ebd5ndyalb6,task_subcomment,NA
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"(In reply to comment #2)
+> Interesting point. I think nontechnical end-users will have a different
+> perspective, however. Both Microsoft Word and Google Docs will produce a
+> single bulleted list as the result. Your users are going to be accustomed to
+> that behavior.
+
+Possibly.
+
+> When an end-user clicks the button the first time, and the bullet disappears,
+> they won't be thinking that ""a bulleted list has become two lists."" They'll
+> simply think ""a bullet symbol has been removed.""
+
+Not two lists - they'll have a paragraph and a list.
+
+I'll make sure we do some real-world tests with non-technical people to come to a decision on this.",1368135721,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yr7732vg2ebd5ndyalb6,task_subcomment,NA
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"Interesting point. I think nontechnical end-users will have a different perspective, however. Both Microsoft Word and Google Docs will produce a single bulleted list as the result. Your users are going to be accustomed to that behavior.
+
+When an end-user clicks the button the first time, and the bullet disappears, they won't be thinking that ""a bulleted list has become two lists."" They'll simply think ""a bullet symbol has been removed.""",1368130302,PHID-USER-o5tv5cyrple4fn5xqopm,False,PHID-TASK-yr7732vg2ebd5ndyalb6,task_subcomment,NA
+VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?,"(In reply to comment #0)
+> In Firefox 20.0.1:
+> 
+> 1. Edit a page that has a bulleted list.
+> 2. Place the cursor on the first bullet item.
+> 3. Click the ""Bullet List"" button. The first bullet item loses its bullet.
+> (Correct.)
+> 4. Click the ""Bullet List"" button a second time. The first bullet comes back
+> (correct), but there is now a blank line displayed below it.
+> 
+> Similarly, if you remove & add a bullet in the middle of the list, you get
+> blank lines above AND below the item.
+> 
+> Similarly, if you do this with a numbered list, the blank line breaks the
+> numbering: the list items below the blank line start over from ""1"".
+
+Yes, because otherwise we'd be unexpectedly merging a <p> with a following <ul> (or whatever). You can always actively choose to merge the lists from this position by deleting the blank line between the lists (technically, this is a slug).
+
+This is the deliberately-chosen behaviour for this. I take it you'd expect lists to instead automatically merge, and you'd have to split them rather than the other way around? X followed by X is not generally a direct reverse step (that's what undo is for), but you expected it to work that way around?",1368127673,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yr7732vg2ebd5ndyalb6,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"The indent and outdent buttons are always grayed out.
+
+(reported at http://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Alpha2013-04#Link_einbinden_.2F_Einzug)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367512920,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-hvvrpcxmtlfovm73otnw,task_description,open
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"Hi,
+
+is this task still active? Indenting (of text) is a much requested feature on my companies wiki.",1542962428,PHID-USER-a5b43na73s7s5vqzeaur,False,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"(In reply to Spinningspark from comment #6)
+
+Sorry, posted this in wrong place.  It was intended for bug 59849",1412132162,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"I don't know if this is related, or whether it should be a new bug.  In this edit:
+
+https://en.wikipedia.org/w/index.php?title=User:Spinningspark/Work_in_progress/Mobility_analogy&diff=626824709&oldid=626823704
+
+VE adds a number of spurious indents.  The intended edit was to swap over the order of two blocks of text containing math markup.  Very frustrating that the problem could not even be fixed from within VE since indenting does not function in general.",1412131984,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,*** Bug 51530 has been marked as a duplicate of this bug. ***,1395359458,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"(In reply to comment #3)
+> Would this also allow the tab key to be used for paragraph indenting (like
+> for lists), or should that be filed as a separate bug report?
+
+That'd be the same (the tab and shift-tab keys are bonded to these buttons), so no need for a separate bug report.",1375765565,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"**mcdevitd** wrote:
+
+Would this also allow the tab key to be used for paragraph indenting (like for lists), or should that be filed as a separate bug report?",1375725373,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"This would be lovely (as a nice-to-have) to get done for the beta.
+
+In practical terms, it means that <p>Foo</p> gets wrapped into <dl><dd><p>Foo</p></dd></dl> and vice versa; all the DM/Parsoid plumbing is there, just needs the indent/outdent commands to be aware of how to operate in the paragraph/preformatted context.",1368836909,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.,"These are for list indenting currently, and do not (yet) do text block indenting. Setting as an enhancement, likely to be after the 'beta' is released.",1367545334,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hvvrpcxmtlfovm73otnw,task_subcomment,NA
+VisualEditor: Support language variant conversion labels,"Conversion labels shown
+
+The conversion labels (i.e. { } ) for wikis like zhwiki is shown when editing using the VisualEditor.
+
+Those labels should be hidden, or otherwise newbies using the editor will break them easily.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F10580}",1367389920,PHID-USER-ixwg3kf22idjy7x4ncxf,False,PHID-TASK-maehbrz5znwar2qitk5b,task_description,duplicate
+VisualEditor: Support language variant conversion labels,"This is a mess; Parsoid currently has no support for the language variant conversion syntax in wikitext, but when it does (bug 41716) we should work on this to make it easy to set the different variants.
+
+Sorry that we are not really ready yet for zh; I feel that this is a blocker to deployment in zh, so until it's fixed I think VisualEditor will remain in alpha opt-in deployment there for now.",1367435394,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-maehbrz5znwar2qitk5b,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"From the fall out of bug 47457's resolution:
+
+(bug 47457 comment #63 by Liangent)
+> (bug 47457 comment #54 by Krinkle)
+> > Change-Id: Ic3d0c937268d0943d2f770f3ca18bcf4e1eed346
+> 
+> This fix causes breakage of any user of site scripts which assume that
+> they're
+> loaded before $(document).ready(). Maybe someone can move jQuery.ready() call
+> to a position just before </body> and after all other script references?
+
+(bug 47457 comment #64 by matma.rex)
+> And it also breaks the old 'mwCustomEditButtons' interface to add custom
+> buttons to the old edit toolbar, which apparently everyone and their dog are
+> using across the wikis. (Since the user JS is loaded from the bottom queue,
+> but
+> the toolbar script either from the top or using inline <script> tags with
+> $.ready inside.)
+> 
+> Reopening. Moving the jQuery.ready() call after the bottom queue seems like a
+> good idea.
+
+
+(bug 47457 comment #66 by Brad Jorsch)
+> (bug 47457 comment #63 by Liangent)
+> > Maybe someone can move jQuery.ready() call to a position just before 
+> > </body> and after all other script references?
+> 
+> (bug 47457 comment #64 by matma.rex)
+> > Moving the jQuery.ready() call after the bottom queue seems like a good idea.
+> 
+> We tried that, see patchset 5 in https://gerrit.wikimedia.org/r/#/c/61057/5.
+> It didn't work.
+> 
+> But unless the browsers were delaying the DOMContentLoaded event until after
+> the async-loaded scripts in the bottom queue were loaded, I don't know how
+> this wasn't already a problem. Krinkle, any ideas?
+
+A few important questions I'd like answered:
+
+@Liangent: Can you given an example where it matters for a user script whether the document becomes ready before or after they are loaded? The user scripts are loaded from the bottom of the <body> before </body>. Practically the document is already ready at this point, just $(document).ready() hasn't fired yet. Any user script code that isn't wrapped in $(document).ready() will still execute at exactly the same time. Any user script code that *is* wrapped in $(document).ready() will now execute immediately after loading instead of... immediately after loading. Exactly the same, not?
+
+@Matma.rex: You mean the fact that the deprecated mwCustomEditButtons global (unlike the mw.toolbar interface) is inspected only once by mediawiki.action.edit.js, namely at the domready event. And if it is triggered before the user script, adding to that array will become a no-op.
+
+Though there is a lot of usage of this feature, lets not forget the context:
+
+* The mwCustomEditButtons interface is for the classic toolbar (aka ""Monobook editor"", though Vector users can also disable WikiEditor to get to it). This is already a large minority of users.
+* The mwCustomEditButtons interace has been deprecated in favour of mw.toolbar.addButton, which I created especially for the legacy toolbar users last year to address the many declined bug reports for mwCustomEditButtons which could not be otherwise addressed because mwCustomEditButtons is beyond repair, it is a flawed concept and it keeps breaking for many reasons.
+
+I don't think anything related to mwCustomEditButtons can justify a change of any kind unless it comes at absolutely no overhead and downside.
+
+@Brad Jorsch: It seems that the Firefox bug with document.write being disabled before DOMContentReady is worse than we thought. It is disabled even before the end of the </body> has been reached. We found through trial-and-error that placing it after the main content but before the bottom queue worked.
+
+As Brad pointed out, $.ready being triggered earlier makes no difference for the bottom queue because they are loaded asynchronously, they always execute without blocking the parser or the DOM ready event. In fact (while designing this) Roan and I made very sure to test this across the entire board of browsers we even remotely support (IE6-10, FF2-17, Chrome10-23, Opera9-11.x). And in any browser that we couldn't load it async, we scheduled the addScript to after dom-ready manually (only in Opera).
+
+However note that the user scripts (like the site scripts) are *not* loaded through mw.loader because we still support legacy global scope for them. They are loaded by a hardcoded script tag in the DOM. Which means they are blocking and used to block dom-ready, and now they run after dom-ready (well, they still block dom-ready, but we trigger that callback queue earlier).
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50310",1367327220,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_description,declined
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #10)
+...
+> I'd recommend we add some code to mediawiki.action.edit to periodically check
+> mwCustomEditButtons. Then immediately deprecate it (not removing it, just
+> marking it as deprecated) and phasing it out over the following weeks (I'd
+> like
+> to add it to the js-deprecations train roll-out in May which will introduce
+> mw.log.deprecate and console.warn messages that users can use to easily see
+> if
+> they are using something that is deprecated).
+
+I requested this on bug 50310 so we don't forget.",1372357726,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"Closing this as wontfix.
+
+The classic edit toolbar has long been deprecated. The default was replaced with WikiEditor on Wikimedia in a 2010 deployment. And since a few releases it is now bundled with new MediaWiki releases as well.
+
+Since then development has started on [[mw:VisualEditor]] which will be launched soon.
+
+Despite all that, I've spend a fair amount of effort over the last months to come up with a brand new API for the classic edit toolbar: mw.toolbar because mwCustomEditButtons is fundamentally flawed and cannot be repaired and kept up with the latest technologies.
+
+Any and all issues you may have with mwCustomEditButtons are from hereon invalid. Please use mw.toolbar instead. Note that mw.toolbar has nothing to do with WikiEditor or VisualEditor, it is a new API for the classic editor you are so familiar with.
+
+I can't make any promises for how long the classic toolbar and this new mw.toolbar will be supported, but at least it has been renewed to work with all the latest technologies so it should be a relatively cheap burdon for us to maintain.
+
+So, long story short: Change:
+
+> if ( wgAction === 'edit' ) {
+>     mwCustomEditButtons[mwCustomEditButtons.length] = {...};
+> }
+
+to:
+
+> if ( mw.toolbar ) {
+>     mw.toolbar.addButton( { ... } );
+> }
+
+If there are any bugs with that, please file a new bug report and be sure to mention ""mw.toolbar"" in its subject. I'll do my best to address if/when there are any issues.",1370831532,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"We fixed it with Nemo on IRC. For the record, this was because the script ran on all pages (not just edit ones). The simplest way to fix that was to wrap the button definitions in ""if ( mw.toolbar ) { ... }"".",1370805496,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #9)
+> billinghurst, this has nothing to do with switching to the new toolbar;
+> mw.toolbar.addButton works with and is intended for the old one, and the
+> change
+> is just a simple find and replace:
+> 
+>   Find:         mwCustomEditButtons[mwCustomEditButtons.length] = { ... }
+>   Replace with: mw.toolbar.addButton({ ... })
+> 
+> Just be careful about braces and parentheses.
+> 
+> Here's an example diff:
+> https://nl.wikipedia.org/w/index.php?title=Gebruiker:Romaine/vector.js&diff=37497149&oldid=37497060
+
+This solution didn't work for long, it just broke all JavaScript for me on Meta (most prominently, [[m:WM:LS]]) with:
+
+Timestamp: 09/06/2013 20:03:03
+Error: TypeError: mw.toolbar is undefined
+Source File: https://bits.wikimedia.org/meta.wikimedia.org/load.php?debug=false&lang=it&modules=user&only=scripts&skin=monobook&user=Nemo+bis&version=20130601T024617Z&*
+Line: 1
+
+[MediaWiki 	1.22wmf5 (bad4d50)]",1370801419,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #11)
+> (In reply to comment #9)
+> > billinghurst, this has nothing to do with switching to the new toolbar;
+> > mw.toolbar.addButton works with and is intended for the old one, and the
+> > change
+> > is just a simple find and replace:
+> > 
+> >   Find:         mwCustomEditButtons[mwCustomEditButtons.length] = { ... }
+> >   Replace with: mw.toolbar.addButton({ ... })
+> > 
+> > Just be careful about braces and parentheses.
+> > 
+> > Here's an example diff:
+> > https://nl.wikipedia.org/w/index.php?title=Gebruiker:Romaine/vector.
+> > js&diff=37497149&oldid=37497060
+> 
+> Thanks. This innovation had escaped me, and clearly a whole community that
+> was
+> using mwCustomEditButtons. I will relay this to the enWS community, and fix
+> our
+> help pages.
+> 
+> Can you recommend that right page to watch for these changes.  I thought
+> that I
+> had watched all the relevant pages where Krinkle does these components,
+> however, it is clear that this change wasn't evident for active changes.
+
+Clearly it was a long time ago as I have since found reference that it was broken in 1.18, but somehow it didn't break for all. Weird.",1367383460,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #9)
+> billinghurst, this has nothing to do with switching to the new toolbar;
+> mw.toolbar.addButton works with and is intended for the old one, and the
+> change
+> is just a simple find and replace:
+> 
+>   Find:         mwCustomEditButtons[mwCustomEditButtons.length] = { ... }
+>   Replace with: mw.toolbar.addButton({ ... })
+> 
+> Just be careful about braces and parentheses.
+> 
+> Here's an example diff:
+> https://nl.wikipedia.org/w/index.php?title=Gebruiker:Romaine/vector.
+> js&diff=37497149&oldid=37497060
+
+Thanks. This innovation had escaped me, and clearly a whole community that was using mwCustomEditButtons. I will relay this to the enWS community, and fix our help pages.
+
+Can you recommend that right page to watch for these changes.  I thought that I had watched all the relevant pages where Krinkle does these components, however, it is clear that this change wasn't evident for active changes.",1367382951,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #7)
+> So how hard would it be to get the site&user scripts to run first, then
+> $.ready, then the rest of the bottom queue? Then we could kill off
+> mwCustomEditButtons after announcing it properly and revert the change
+> (unless
+> there is a considerable number of other scripts this would break).
+> 
+> [Disclaimer: I know next to nothing about ResourceLoader internals.]
+
+site&user script run after the bottom queue by design. Just like the cascading stylesheets, they are intended and designed to allow overriding/customising things after everything else.
+
+Though presence of code will not make a difference (since bottom queue is async), the loading is affected.
+
+Code in site and/or user scripts that are wrapped in mw.loader.using would trigger additional http requests instead of tagging along on the already pending request for the bottom queue (this is ResourceLoader internals).
+
+I'd recommend we add some code to mediawiki.action.edit to periodically check mwCustomEditButtons. Then immediately deprecate it (not removing it, just marking it as deprecated) and phasing it out over the following weeks (I'd like to add it to the js-deprecations train roll-out in May which will introduce mw.log.deprecate and console.warn messages that users can use to easily see if they are using something that is deprecated).
+
+Then we can safely remove mwCustomEditButtons in the 1.22 release.
+
+(In reply to comment #6)
+> (In reply to comment #5)
+> > Rephrasing bug to be about mwCustomEditButtons to avoid mixed subjects.
+> 
+> See my comment above. There may be other similar structures existing there.
+
+Possible indeed, though unlikely as most legacy things have been phased out. Examples are welcome :)",1367355163,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"billinghurst, this has nothing to do with switching to the new toolbar; mw.toolbar.addButton works with and is intended for the old one, and the change is just a simple find and replace:
+
+  Find:         mwCustomEditButtons[mwCustomEditButtons.length] = { ... }
+  Replace with: mw.toolbar.addButton({ ... })
+
+Just be careful about braces and parentheses.
+
+Here's an example diff: https://nl.wikipedia.org/w/index.php?title=Gebruiker:Romaine/vector.js&diff=37497149&oldid=37497060",1367338720,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"As a comment mwCustomEditButtons functionality is used at English Wikisource. And for numbskulls like myself it is far easier to code snippets to implant code than the alternate means. I repeatedly failed to master mw.toolbar.addButton, gave up walked away, too much to do, too much to customise.
+
+The old toolbar allows for easy nulling out of buttons not required, or not prioritised, and the easy addition of little bits of personal functionality, and the new toolbar makes these things hard (IMO).  Don't blame us that we find the older tool to work better; has the requisite functionality, and meets our simple needs. We are not WP, our requirements are different, our tasks are different, our namespaces are different.
+
+I am happy to try again to be less stupid to see if I can create a core set of tools that could be used, and allow users to plug them in as they see fit, however, it isn't my core skill set. Definitely an area where better guidance would be of use.
+
+PLUS as the 'new' toolbar is still considered a BETA FEATURE (see preferences), why would we be expected to move. Stridency against us simple editors seems a little harsh. Some of us just want to get on with our tasks, and chasing and understanding the backend changes isn't easy.",1367338360,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"So how hard would it be to get the site&user scripts to run first, then $.ready, then the rest of the bottom queue? Then we could kill off mwCustomEditButtons after announcing it properly and revert the change (unless there is a considerable number of other scripts this would break).
+
+[Disclaimer: I know next to nothing about ResourceLoader internals.]",1367337892,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #5)
+> Rephrasing bug to be about mwCustomEditButtons to avoid mixed subjects.
+
+See my comment above. There may be other similar structures existing there.",1367336991,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"Rephrasing bug to be about mwCustomEditButtons to avoid mixed subjects.
+
+So in summary: mwCustomEditButtons is very ugly and undocumented. But it used to be the only way to add buttons to the toolbar. Though (as pointed out by various comments) it is a coincidence that most existing usages have survived without causing errors, but it is the case.
+
+How mwCustomEditButtons works now:
+* Initialise to empty array from top queue
+* Hook in document ready
+* Iterate through array (e.g. items added before the page load) and call mw.toolbar.addButton for each one.
+
+The state is that most existing usages of mwCustomEditButtons happen from a site or user script at run-time in the global scope. And this works fine because they are blocking script tags.
+
+Now that $.ready() (the jquery callback list, not the event itself) is triggered before site/user script load (the site/user script still load from the bottom) it means the code that iterates through the legacy array will not get any of the items because they're not in the array yet at that time.",1367336363,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #0)
+> @Liangent: Can you given an example where it matters for a user script
+> whether
+> the document becomes ready before or after they are loaded? The user scripts
+> are loaded from the bottom of the <body> before </body>. Practically the
+> document is already ready at this point, just $(document).ready() hasn't
+> fired
+> yet. Any user script code that isn't wrapped in $(document).ready() will
+> still
+> execute at exactly the same time. Any user script code that *is* wrapped in
+> $(document).ready() will now execute immediately after loading instead of...
+> immediately after loading. Exactly the same, not?
+
+Let me give a (almost) real world example (difference explained below):
+
+We have some gadgets (technically some gadgets, but socially one gadget; not using [ResourceLoader]). The first is the gadget itself, which registers some global states as data/options, then $(document).ready() its execution code. All gadgets below are modifiers for the gadget which change those global states so when the main body of the gadget is executed, the modified global states are visible to it. But now...
+
+Difference from real world: addOnloadHook() is used there instead of $(document).ready() so it finally escaped :)",1367335235,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"Created attachment 12209
+Test case for the browser issue with setTimeout and document.write
+
+I've attached my test case for the browser issue with setTimeout and document.write. Note that it should be served from a webserver that is not behind a proxy server, so the flush calls result in it slowly counting 0-9.
+
+**Attached**: {F10516}",1367334847,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #0)
+> @Brad Jorsch: It seems that the Firefox bug with document.write being
+> disabled before DOMContentReady is worse than we thought. It is disabled even
+> before the end of the </body> has been reached. We found through
+> trial-and-error that placing it after the main content but before the bottom
+> queue worked.
+
+But it works from synchronously-processed scripts, even just before </body>.
+
+I've done some more testing on this Firefox situation. More specifically, it seems that *any* document.write called from a setTimeout callback will replace the document, even if it fires during <head>. And this even avoids the check (since Gecko 2.0 (Firefox 4.0)) that is supposed to disable document.write when called from async-loaded scripts.[1]
+
+ [1]: https://developer.mozilla.org/en-US/docs/HTML/Element/script#attr-async
+
+The following browsers seem to be affected by this issue: Firefox 20, IE8, IE10, Chrome 24, Chrome 26, Opera 12.14.
+
+The following browsers seem to *not* be affected by this issue: Safari 5.1 (Windows)
+
+So runScript() should probably be forcing async when it calls addScript(), since it is called from a setTimeout in addEmbeddedCss(), as another layer of fix for bug 47457.
+
+
+> As Brad pointed out, $.ready being triggered earlier makes no difference for
+> the bottom queue because they are loaded asynchronously, they always execute
+> without blocking the parser or the DOM ready event.
+
+In fact, this should make the behavior for the bottom queue *more* predictable. Previously, depending on whether the async-loaded scripts for the bottom queue loaded extremely quickly (e.g. from cache) and whether the browser then decided to process them before firing DOMContentLoaded, they might sometimes be fired before $.ready and sometimes after. Now they'll always be after, no matter what the browser does.
+
+> However note that the user scripts (like the site scripts) are *not* loaded
+> through mw.loader because we still support legacy global scope for them. They
+> are loaded by a hardcoded script tag in the DOM. Which means they are
+> blocking and used to block dom-ready
+
+I suppose that's where these complaints about mwCustomEditButtons and other such are coming from, if someone coded something assuming pre-ready directly in a user script or site script. OTOH, scripts loaded from the site or user scripts loaded via mw.loader.load() already had the issue (thanks to the fix for bug 34542 defaulting that sort of thing to async), so it only half-worked at best before bug 47457 anyway.",1367334391,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+[Regression] mwCustomEditButtons from user script should work,"(In reply to comment #0)
+> @Matma.rex: You mean the fact that the deprecated mwCustomEditButtons global
+> (unlike the mw.toolbar interface) is inspected only once by
+> mediawiki.action.edit.js, namely at the domready event. And if it is
+> triggered
+> before the user script, adding to that array will become a no-op.
+
+Yes, precisely.
+
+
+> Though there is a lot of usage of this feature, lets not forget the context:
+
+> * The mwCustomEditButtons interface is for the classic toolbar (aka ""Monobook
+> editor"", though Vector users can also disable WikiEditor to get to it). This
+> is
+> already a large minority of users.
+
+Yeah, my guesstimate is a few hundred power-users across all of the Wikimedia wikis. (I just searched for 'mwCustomEditButtons' in user pages on a few large projects, and tried to account for inactive ones.)
+
+
+> * The mwCustomEditButtons interace has been deprecated in favour of
+> mw.toolbar.addButton, which I created especially for the legacy toolbar users
+> last year to address the many declined bug reports for mwCustomEditButtons
+> which could not be otherwise addressed because mwCustomEditButtons is beyond
+> repair, it is a flawed concept and it keeps breaking for many reasons.
+> 
+> I don't think anything related to mwCustomEditButtons can justify a change of
+> any kind unless it comes at absolutely no overhead and downside.
+
+I realize that this is deprecated, and agree that it's broken by design. But killing it should be preceded by some release notes and some Wikimedia announcements (or just fixing users' JavaScript for them, since there are comparatively few of them).
+
+I have reopened the previous bug because of the combination of Liangent's comment (which I didn't verify myself) and at least two users complaining about this on #wikimedia-tech today, including one who was kind and persistent enough to help me confirm that this was what broke the functionality ([[nl:User:Romaine]]).
+
+So I'm all for removing this legacy compatibility, but let's do it right instead of as a side-effect of an unrelated fix.",1367328242,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nvh5ejbvixlonbrch4jd,task_subcomment,NA
+"VisualEditor: For images, ensure that the HTML structure rendered in VE is the same as output by PHP parser so that styles/scripts work as expected and images look normal","Screenshot in edit mode
+
+Images on pages are normally included using the ""thumb"" syntax:
+
+[[File:Foo.jpg|thumb|description]]
+
+In the edit mode no thumb frame is shown, see screenhots.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/thumb
+
+**Attached**: {F10382}",1367185320,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-fsl2ocvagc2ct7mjj527,task_description,resolved
+"VisualEditor: For images, ensure that the HTML structure rendered in VE is the same as output by PHP parser so that styles/scripts work as expected and images look normal","This was fixed by gerrit 64367 which is now merged, but is 'experimental' and so will not go out for a short while. Marking as fixed within wmf5, though.",1369093729,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fsl2ocvagc2ct7mjj527,task_subcomment,NA
+"VisualEditor: For images, ensure that the HTML structure rendered in VE is the same as output by PHP parser so that styles/scripts work as expected and images look normal","For now we are going to fix it in VE directly. Parsoid will deliver us figure tags for block images and span tags for inline images, but VE is going to render div soup for block and image wrapped in an anchor for inline (maybe with few exceptions).",1368216297,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-fsl2ocvagc2ct7mjj527,task_subcomment,NA
+"VisualEditor: For images, ensure that the HTML structure rendered in VE is the same as output by PHP parser so that styles/scripts work as expected and images look normal","Hijacking this bug slightly. :-)
+
+(This will probably be solved with an upstream bug with Parsoid for a post-parser to transform, but could be done in VE instead. Either way are messy; long term answer is for Parsoid-output to be the ""read"" HTML too, and have skins and scripts target that structure.)",1367544520,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fsl2ocvagc2ct7mjj527,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Simple test case, see URL:
+
+* foo
+: bar
+
+adds a newline in edit mode. When removing this newline in edit mode the : is killed by the parser.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/Finissage
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60535",1367166420,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-v7tsixpel4mikkpah73h,task_description,resolved
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","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.
+
+This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion.
+
+(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'? I will also copy to bug 55336.",1405114275,PHID-USER-mcyovqjor52nj3se4lq7,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Initial version of this now merged and being deployed tomorrow. I think we'll want to revisit the styling and behaviour, but this will do for now.",1394077374,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 116742 abandoned by Esanders:
+Vector style tweaks for collapsible slugs
+
+https://gerrit.wikimedia.org/r/116742",1394042895,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 109307 merged by jenkins-bot:
+Collapse block slugs and expand on hover/focus
+
+https://gerrit.wikimedia.org/r/109307",1394040062,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 116742 had a related patch set uploaded by Esanders:
+Vector style tweaks for collapsible slugs
+
+https://gerrit.wikimedia.org/r/116742",1393942167,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 109307 had a related patch set uploaded by Esanders:
+Collapse block slugs, and expand on hover/focus
+
+https://gerrit.wikimedia.org/r/109307",1390581550,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. 
+
+Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall.
+
+I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",1381008272,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**jonathan_haas** wrote:
+
+(In reply to comment #15)
+> Why don't we just suppress the delete key when pressing it would delete the
+> object the slug is associated with?
+
+This would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout.
+
+I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.",1380964477,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes. Here is the latter: bug 55336",1380963747,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. 
+
+Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior.
+
+Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result.
+
+That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Today JohnCD asked again about this and I got another report from fr.wp, https://fr.wikipedia.org/w/index.php?title=Osmium&diff=96605232&oldid=93301425 .
+Hoping this gets some love soon :)",1379004776,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",*** Bug 52172 has been marked as a duplicate of this bug. ***,1375047891,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Created attachment 12988
+Copy of http://i.imgur.com/39QQi8U.png
+
+Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-)
+
+**Attached**: {F10355}",1374960319,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Suggestion:
+http://i.imgur.com/39QQi8U.png",1374926957,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**JohnCD67** wrote:
+
+This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",1374396945,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**joedecker** wrote:
+
+I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused.  
+
+As a separate question, can you undo deletion of slugs?  If not, I think that would explain another set of problems others and I have observed.",1374361883,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",Gotcha. A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).,1373913566,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","(In reply to comment #4)
+> Does this include the line of whitespace right at the start of articles?
+
+Yes.",1373913377,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","(In reply to comment #5)
+> It looks like this bug was fixed somehow. I cannot longer reproduce it on
+> dewiki.
+
+Yes, we removed the slugs between lists because we felt they were no longer needed given the new editing tools, but they remain more widely.",1373913366,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",It looks like this bug was fixed somehow. I cannot longer reproduce it on dewiki.,1373909882,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",Does this include the line of whitespace right at the start of articles?,1373879923,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",*** Bug 50295 has been marked as a duplicate of this bug. ***,1373854867,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines",*** Bug 50797 has been marked as a duplicate of this bug. ***,1373046915,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go.
+
+Re-purposing this bug to talk about that. :-)",1367169998,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v7tsixpel4mikkpah73h,task_subcomment,NA
+VisualEditor: Coordinate template on dewiki not alienated,"Coordinate template on dewiki not alienated. Shown as active hyperlink to the toolserver.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Breslauer_Platz_%28K%C3%B6ln%29",1367154120,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-lfunc2bgbzuuwhfvjpdv,task_description,declined
+VisualEditor: Coordinate template on dewiki not alienated,It looks like this is handled properly now. Reopen if you still experience this problem.,1374527977,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-lfunc2bgbzuuwhfvjpdv,task_subcomment,NA
+VisualEditor: Coordinate template on dewiki not alienated,"Interesting! The content (which is not labelled as an alien) is floated out from within a div (which is ve-ce-alienInlineNode). Inez/Christian, ideas?",1367173682,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lfunc2bgbzuuwhfvjpdv,task_subcomment,NA
+Enable VisualEditor on viwiki,"Per community request; will throw in a change on Monday.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1367123340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vdic7routqydx75tmmbb,task_description,resolved
+Enable VisualEditor on viwiki,This is now deployed. Marking as fixed.,1367270838,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vdic7routqydx75tmmbb,task_subcomment,NA
+Enable VisualEditor on viwiki,Change in gerrit 61382.,1367247999,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vdic7routqydx75tmmbb,task_subcomment,NA
+Enable VisualEditor on viwiki,Request was via e-mail but http://vi.wikipedia.org/wiki/WP:TL#Tr.C3.ACnh_so.E1.BA.A1n_th.E1.BB.8B_gi.C3.A1c is an announcement on the wiki that this is coming for testing.,1367247981,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vdic7routqydx75tmmbb,task_subcomment,NA
+Enable VisualEditor on viwiki,"Any link to the community request, for the records?",1367225301,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-vdic7routqydx75tmmbb,task_subcomment,NA
+VisualEditor: Toolbar tooltip text throbs when un-floated,"If you scroll down from the top of the page with the edit notice open and then scroll back up, the text content of the notice 'throbs' a little. I think it has to do with the dynamic addition / removal of the 've-ui-toolbar-wrapper-floating' class on ve-ui-toolbar-wrapper.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1367030520,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-dv6pxr32mobwf3arakop,task_description,declined
+VisualEditor: Toolbar tooltip text throbs when un-floated,Hi Ori. Can you please respond to James' comment?,1397939050,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-dv6pxr32mobwf3arakop,task_subcomment,NA
+VisualEditor: Toolbar tooltip text throbs when un-floated,"Ori, I can't reproduce this locally (on Chrome, Safari or Firefox) - what browser were you using?",1367126151,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dv6pxr32mobwf3arakop,task_subcomment,NA
+VisualEditor: A lot of time needed to load <math> blocks?,"I tested it on the [[Bayes' theorem]] which has <Math></Math> inside the article with chrome 28 and it couldn't load the page!.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367021760,PHID-USER-dswbdv7ibhsefllcqarz,False,PHID-TASK-pzrh6lxoqsxowrm5mt6k,task_description,declined
+VisualEditor: A lot of time needed to load <math> blocks?,Resolving as WORKSFORME as I cannot reproduce and there's been no further information about how to get this effect. Feel free to re-open if you have additional data to help us find out what went wrong for you.,1367548087,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pzrh6lxoqsxowrm5mt6k,task_subcomment,NA
+VisualEditor: A lot of time needed to load <math> blocks?,I'm afraid I can't reproduce this - is this using MathJax? When I load the page https://en.wikipedia.org/wiki/Bayes'_theorem?veaction=edit (in Chrome or Firefox) I always get the <math> blocks rendered as PNGs instantly. Can you give some more information? A screenshot of the failed (partial?) rendering would be particularly useful.,1367293923,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pzrh6lxoqsxowrm5mt6k,task_subcomment,NA
+VisualEditor: No warning is shown when saving a page without an edit summary despite user preference,"No warning is shown when saving a page without an edit summary even when the ""Prompt me when entering a blank edit summary"" preference is enabled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367008860,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-bltbr6dun3s6724ee3wt,task_description,resolved
+VisualEditor: No warning is shown when saving a page without an edit summary despite user preference,Merged and will go out with wmf5.,1369092004,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bltbr6dun3s6724ee3wt,task_subcomment,NA
+VisualEditor: No warning is shown when saving a page without an edit summary despite user preference,Related URL: https://gerrit.wikimedia.org/r/64313 (Gerrit Change Idba707abaea8b08a94f7fa4d5bc5b1e35261a572),1368800999,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bltbr6dun3s6724ee3wt,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),"When I edit an article in the English Wikipedia and hover over a template or an image, green diagonal stripes appear over it, meaning that it can't be edited.
+
+These green stripes don't appear in the Hebrew Wikipedia.
+
+See the URL for a demo.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://he.wikipedia.org/wiki/ASCII",1367005440,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_description,resolved
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),"**orbit** wrote:
+
+Yep, CSSJanus indeed. I've added /*@noflip*/ to the phantoms container to ensure proper positioning.",1367280330,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),https://gerrit.wikimedia.org/r/61516 (Gerrit Change Id7662362d117d6c5719b9b98d7a0dbf62e9ba3ff) | change APPROVED and MERGED [by jenkins-bot],1367280189,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),Related URL: https://gerrit.wikimedia.org/r/61516 (Gerrit Change Id7662362d117d6c5719b9b98d7a0dbf62e9ba3ff),1367280048,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),"Indeed, works in debug mode.
+
+It's just a wild guess for now, but it may have something to do with CSSJanus.",1367006685,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),It might be a cache issue - works just fine in debug mode - https://he.wikipedia.org/w/index.php?title=ASCII&debug=true,1367006326,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?),I'm able to reproduce at least in Chrome.,1367005802,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-qpmnlciz3b3w3vskmgmu,task_subcomment,NA
+VisualEditor: Moving the cursor using an arrow makes templates and footnote numbers disappear,"Steps:
+
+1. Go to the URL.
+2. Start editing the page using the VisualEditor.
+3. Move the cursor using the keyboard arrow keys forward (right).
+
+Observed:
+
+When you get to the ""Done"" template and go on moving the cursor, the whole template disappears.
+
+The same happens when you get to the reference number on the second line (""[1]"").
+
+The cursor must probably skip over them and definitely not make them disappear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/VisualEditor:Disappearing_template",1367005140,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-gfh3zyqmntwzuisuy7o2,task_description,resolved
+VisualEditor: Moving the cursor using an arrow makes templates and footnote numbers disappear,And actually the desired behavior is not skipping over - it is selecting it (so you can delete if you want) - give it a try in Chrome.,1367005498,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-gfh3zyqmntwzuisuy7o2,task_subcomment,NA
+VisualEditor: Moving the cursor using an arrow makes templates and footnote numbers disappear,I have a good reason to believe that this occurs only in Firefox and I just fixed it here: https://gerrit.wikimedia.org/r/#/c/61055/. If you get it in other browser then pelase reopen this bug.,1367005458,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-gfh3zyqmntwzuisuy7o2,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"Having users using different languages to post feedback on different pages on the same site makes it difficult to manage.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1366981200,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-xdguppbr4wppxkti274y,task_description,resolved
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"Change 74064 merged by jenkins-bot:
+Remove 'visualeditor-feedback-link' from RL module
+
+https://gerrit.wikimedia.org/r/74064",1374012412,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,Fixed. Sorry about this. Will be deployed this afternoon.,1374012385,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"Change 74064 had a related patch set uploaded by Krinkle:
+Remove 'visualeditor-feedback-link' from RL module
+
+https://gerrit.wikimedia.org/r/74064",1374010123,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"(In reply to comment #11)
+> (In reply to comment #10)
+> > pl.wiki is on 1.22wmf8 but my feedback was posted to a non-existing page with
+> > Italian title (I have Italian UI), [[pl:Wikipedia:VisualEditor/Commenti]]:
+> > https://pl.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> > Commenti&oldid=36959657
+> 
+> Confirmed, this is also happening to me. Did the code get broken somehow?
+
+Somewhere between https://gerrit.wikimedia.org/r/#/c/68216/ and its parent (I can't seem to find the commit that added it) the message was added in VisualEditor.php's resource module definition. Which caused the message from VisualEditorMessagesModule (in content-language) to be overridden at run time by the one from ResourceLoader for user language.",1374010028,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"(In reply to comment #10)
+> pl.wiki is on 1.22wmf8 but my feedback was posted to a non-existing page with
+> Italian title (I have Italian UI), [[pl:Wikipedia:VisualEditor/Commenti]]:
+> https://pl.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Commenti&oldid=36959657
+
+Confirmed, this is also happening to me. Did the code get broken somehow?",1373852430,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"pl.wiki is on 1.22wmf8 but my feedback was posted to a non-existing page with Italian title (I have Italian UI), [[pl:Wikipedia:VisualEditor/Commenti]]: https://pl.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Commenti&oldid=36959657",1372603756,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,Merged and will go out in wmf5.,1369088720,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,*** Bug 48645 has been marked as a duplicate of this bug. ***,1369068249,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,Related URL: https://gerrit.wikimedia.org/r/64498 (Gerrit Change I3804e6f91015ef9b8ae5196efb37475d714cd7d5),1368898661,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"(In reply to comment #5)
+> Yes, that would fix this particular problem; my question is more as to
+> whether
+> the core tool should default for target link to be in the content language.
+
+Based on what I see in the usage given above, you're giving a Title to core feedback tool, which points to a certain page, instead of a message name to core with feedback page name in that message.",1368814496,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"Yes, that would fix this particular problem; my question is more as to whether the core tool should default for target link to be in the content language.",1368813996,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"But there is:
+
+modules/ve/init/mw/targets/ve.init.mw.ViewPageTarget.js:
+		'title': new mw.Title( ve.msg( 'visualeditor-feedback-link' ) ),
+
+shouldn't something like:
+
+new mw.Title( ve.msg( 'visualeditor-feedback-link' ).inContentLanguage() )
+
+be used?",1368813782,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"(In reply to comment #2)
+> I'm not sure what ""core MW feedback tool"" means, but I was talking about the
+> feedback feature for [[Wikipedia:VisualEditor/Feedback]].
+
+Yes, this is a core MediaWiki feature, it just happens to be used by VisualEditor:
+
+  resources/mediawiki/mediawiki.feedback.js",1368813471,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,"I'm not sure what ""core MW feedback tool"" means, but I was talking about the feedback feature for [[Wikipedia:VisualEditor/Feedback]].",1368813368,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+VisualEditor: Message <visualeditor-feedback-link> should be used in content language,(Is this a bug in the core MW feedback tool?),1368809941,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xdguppbr4wppxkti274y,task_subcomment,NA
+[mediawiki.feedback.js] Feedback should follow redirect,"I tried to edit MediaWiki:Visualeditor-feedback-link on zhwp but it doesn't affect the feedback target page at all. Is that even the correct message to change?
+
+I then turn the target page into a redirect, but feedback are still sent to that page without following the redirect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366979940,PHID-USER-hoj4lurwi6bejyjy5qlp,False,PHID-TASK-xjswbfq6vvdy4oyl6qub,task_description,resolved
+[mediawiki.feedback.js] Feedback should follow redirect,Fixed in 96c4e453ecfaba9cc5dca904301981e9d6e3492b (https://gerrit.wikimedia.org/r/#/c/143171/).,1419984894,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xjswbfq6vvdy4oyl6qub,task_subcomment,NA
+[mediawiki.feedback.js] Feedback should follow redirect,"(In reply to comment #0)
+> I tried to edit MediaWiki:Visualeditor-feedback-link on zhwp but it doesn't
+> affect the feedback target page at all. Is that even the correct message to
+> change?
+
+Yes, that is the correct message; you can set it for all zh-hans or zh-hant projects at [0] and [1] and it will respect it (once the software is updated).
+
+[0] - https://translatewiki.net/w/i.php?title=Special:Translate&language=zh-hans&group=ext-visualeditor
+[1] - https://translatewiki.net/w/i.php?title=Special:Translate&language=zh-hant&group=ext-visualeditor
+
+> I then turn the target page into a redirect, but feedback are still sent to
+> that page without following the redirect.
+
+You're right; this is a bug in the feedback tool, which is part of MediaWiki core. Moving the bug there.",1366986213,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xjswbfq6vvdy4oyl6qub,task_subcomment,NA
+VisualEditor: using non-ASCII characters in the VisualEditor edit summary insertion can make the remaining character count negative,"Try typing non-ASCII characters in the VisualEditor edit summary field. For example, just type the Russian letter ж continuously. Towards the end it won't stop at 0, but at -1. Example screenshot from the Hebrew Wikipedia: http://j.mp/ZoQKX6 .
+
+This should be handled in a cleaner way. Either disallow typing anything that would go beyond zero, or allow all text to go beyond zero, as in Twitter or MoodBar.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1366970520,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-pruvovx7b4nd6obededc,task_description,resolved
+VisualEditor: using non-ASCII characters in the VisualEditor edit summary insertion can make the remaining character count negative,Merged; will go out with wmf5.,1368885077,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pruvovx7b4nd6obededc,task_subcomment,NA
+VisualEditor: using non-ASCII characters in the VisualEditor edit summary insertion can make the remaining character count negative,"Fixed in https://gerrit.wikimedia.org/r/#/c/64342/
+
+To clarify, we aren't letting people go over the limit, we just aren't updating the counter after keyup. (If you get to -1 then press an arrow key, you'll see you're actually under the limit).",1368812163,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pruvovx7b4nd6obededc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,"Steps:
+
+1. Write some text in VisualEditor in the Hebrew Wikipedia.
+
+2. Select a word.
+
+3. Press the link button in the toolbar. A small link insertion panel appears.
+
+Observed: The direction of the <input> element for the link is ltr.
+
+Expected: The direction of the <input> element for the link is supposed to be rtl.
+
+Comment: It does make sense to set ltr direction by default for external links (http://www.example.com). For internal links the default direction should be the same as that of that Wikipedia's content language.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366970040,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-bwileoq2fxrn6ez262yc,task_description,resolved
+VisualEditor: Link inspector input text always has LTR direction,Merged in Moriel's fix (thanks!).,1367529320,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,Related URL: https://gerrit.wikimedia.org/r/61960 (Gerrit Change Ic13b9c3b155ce2979298cac9518c7419b9d45bac),1367480866,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,Moriel wants to take a stab at this one; assigning.,1367377382,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,"(In reply to comment #1)
+> Eurgh. That's a real mess of a user interaction - in an RTL locale, it starts
+> as RTL, but then you type enough of a string that looks a bit like
+> ""http?://www"" it magically switches to LTR?
+
+This is not such a mess as a matter of fact. This works very well in GMail chat, for example. If you start typing Hebrew characters, it switches the input box to RTL and vice versa. It also goes further: if you type a few Hebrew characters, and then a lot of Latin characters, it switches to LTR.
+
+BUT -and this is very important- it is not forced: the user can switch the direction later manually. In most Windows browsers it's done using Ctrl-Shift, in Firefox on Windows and GNU/Linux it's done using Ctrl-Shift-X. I don't know about Mac browsers, but it's probably something similar. (I do know that it's impossible on Chrome in Linux, which is why I almost never use it.)
+
+> What about when your wiki page that
+> you're internally linking to is [[http://www.amazon.com]] - do you show as
+> LTR
+> even though it's actually an internal link? How does this get handled in
+> other
+> software?
+
+Same as above, essentially. One thing that could help here would be a possibility to specify the language of the page and of the title, as in bug 34514. But that's extra icing. For a link insertion dialog it is enough to do automatic detection with a possibility to override manually.",1367300169,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+VisualEditor: Link inspector input text always has LTR direction,"(In reply to comment #0)
+> Comment: It does make sense to set ltr direction by default for external
+> links (http://www.example.com). For internal links the default direction should
+> be the same as that of that Wikipedia's content language.
+
+Eurgh. That's a real mess of a user interaction - in an RTL locale, it starts as RTL, but then you type enough of a string that looks a bit like ""http?://www"" it magically switches to LTR? What about when your wiki page that you're internally linking to is [[http://www.amazon.com]] - do you show as LTR even though it's actually an internal link? How does this get handled in other software?",1367286968,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bwileoq2fxrn6ez262yc,task_subcomment,NA
+"VisualEditor: VE tab is on the left (not right) of the ""edit source"" tab in RTL languages","
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1366932480,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k5ivcykbmehlps6rrqj3,task_description,resolved
+"VisualEditor: VE tab is on the left (not right) of the ""edit source"" tab in RTL languages","
+
+*** This bug has been marked as a duplicate of bug 48017 ***",1368639099,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-k5ivcykbmehlps6rrqj3,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,"If users can't edit in nowiki blocks, they will make accidental wikitext-like items and be forever unable to edit them in future.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366930860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_description,resolved
+VisualEditor: Support editing nowiki blocks,*** Bug 51950 has been marked as a duplicate of this bug. ***,1374879593,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,Done and merged.,1374262258,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,"Change 74107 merged by jenkins-bot:
+Add a node class for mw:Nowiki
+
+https://gerrit.wikimedia.org/r/74107",1374261100,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,"Change 74107 had a related patch set uploaded by Catrope:
+Add a node class for mw:Nowiki
+
+https://gerrit.wikimedia.org/r/74107",1374027032,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,"Theoretically users should never know something's been <nowiki>'ed - possibly we could just silently drop them and Parsoid re-applies them automatically on save?
+
+(This assumes we can rely on Parsoid to do this with no or very few false negatives - false positives, which we already have a little of, wouldn't be a huge problems for VE users.)",1366931455,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Support editing nowiki blocks,*** Bug 47677 has been marked as a duplicate of this bug. ***,1366930915,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vhod5j4lmpp5giw7zjlk,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"The 'cancel' message is used confusingly.
+
+I only noticed it recently. I know of two places where it is used, though there may be more:
+
+1. As a link near the ""Show changes"" button when editing a page.
+
+2. As a button near the ""Review and save"" button in the VisualEditor.
+
+In both cases it's better to say something like ""Exit without saving"". The ""Cancel"" button is usually used in dialog boxes and not in editors' user interfaces.
+
+The message may be used in other places and in extensions, so it's probably better not to change it. For these actions a new message should be created, or maybe even two messages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1366929720,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-h6knxqbqokuwzylojsm7,task_description,declined
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',Indeed. :-),1406470421,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"Hehe, it was removed eventually :)",1406457643,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"Deciding to WONTFIX this, per discussion above. Hopefully it will be more understandable anyway, given the forthcoming changes to the save dialog.",1368804205,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"I read your concern, Amir, and my opinion is similar to that of James. In computer interaction, clicking a button that says Cancel will end the current action (in this case editing a page) without actually committing the changes that the actor made. I see no deviation from that paradigm in the two use cases you describe.
+
+I think we shoild close this issue without implementing the suggestion made.",1366959308,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving',"Worry that this is a bit long for users, and ""cancel"" is used in the dialog sense (they entered an editor, this cancels that edit) but I can see your point.
+
+(BTW, your two descriptions are for the same button, unless I'm missing something?)",1366934934,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h6knxqbqokuwzylojsm7,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Take a look at the URL.
+
+When you see the output page, the list has three items. If you edit it in the source editor, you'll see that there's an extra empty item in the end of the list. If you edit it in the VisualEditor, you'll see it rendered.
+
+The VisualEditor behavior actually makes more sense to me. Gabriel Wicke suggested on IRC to open this issue at the PHP parser.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/VisualEditor:Empty_list_item",1366928220,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_description,resolved
+Empty list items goes missing in the PHP parser when tidy is enabled,"The goal of fixing templates to not emit empty list items in the first place ( T49673#1827449 ) is not in sight. For now, the core part of this ticket has been addressed. Empty elements no longer go missing with Tidy which means we can replace Tidy without worry about breaking rendering because of this.
+
+Longer term, we should migrate to a CSS3 fix of li:empty { display:none; } and remove the mw-empty-elt class.",1494287494,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"It would be easier to fix such templates if we finally got around to allowing blank lines between list items without breaking the list. This has been requested very often, although unfortunately the narrower, more sensible proposals on the subject (e.g. T11342, T35918, T15223) have been closed as duplicates in favour of the more aggressive proposal T3115.",1448405507,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"It would be easier to fix such templates if we finally got around to allowing blank lines between list items without breaking the list. This has been requested very often, although unfortunately the narrower, more sensible proposals on the subject (e.g. T11342, T35918) have been closed as duplicates in favour of the more aggressive proposal T3115.",1448346652,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,">>! In T49673#1776557, @Jonesey95 wrote:
+> I don't have the gerrit skills to parse the code to understand whether this change will allow a page to emit a tracking category specific to monitor articles and templates that need to be updated. If it will, some instruction would be helpful. If it currently will not, please make whatever code modification is necessary to allow a page to emit such a tracking category. Thank you. 
+
+There's no tracking category at the moment. I wanted to assess it myself, to determine the size of the problem, before creating task lists for others to work through.
+
+[[https://www.mediawiki.org/wiki/User:Tim_Starling/Empty-li-log|Here is a log sample]] from parsoid listing some supposedly empty <li> elements. I have analysed some of them.
+
+[[https://en.wikipedia.org/w/index.php?title=Template:Europe_topic&oldid=675002623&action=edit |Here is a notable example]] of a template which depends on empty li removal. This navbox template allows the removal of countries from Europe depending on parameters. For example if you consider Germany to not be part of Europe, you can use {{Europe topic|DE=}} to make a navbox which omits the relevant list item. Note that you can't just take the asterisk inside the #if, because that would create paragraph breaks between adjacent list items. It could be done by taking the line break inside the #if, or by removing all the line breaks and using HTML-style <li> input.
+
+",1448343599,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Change 253514 merged by jenkins-bot:
+Add 'mobile' target to 'mediawiki.raggett' module
+
+[[https://gerrit.wikimedia.org/r/253514]]",1447723607,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Change 253514 had a related patch set uploaded (by Legoktm):
+Add 'mobile' target to 'mediawiki.raggett' module
+
+[[https://gerrit.wikimedia.org/r/253514]]
+",1447721409,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"The CSS trick for do not display element with //mw-empty-li// class works only for Desktop, not in mobile version.
+
+It's possible in this transitory period hide the empty list elements also in mobile site? Thanks
+
+See [[https://it.wikipedia.org/w/index.php?title=Discussioni_progetto:Coordinamento/Template&oldid=76516793#Errore di visualizzazione da mobile | discussion ]] (in italian) and [[https://it.m.wikipedia.org/wiki/Kriszti%C3%A1n_Adorj%C3%A1n|example]].",1447669730,PHID-USER-6ji4nw2pi3dgjy7tgmhp,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"This tasks seems to be related to a lot of odd looking [[Template:Authority control]] templates that use //hlists// which suddenly started showing rows of dots between entries
+
+# Commons issues and the fix was discussed at https://www.mediawiki.org/wiki/Talk:Snippets/Horizontal_lists
+# Czech Wiki opted for rewriting the template https://cs.wikipedia.org/wiki/%C5%A0ablona:Autoritn%C3%AD_data?diff=13027629&oldid=12931367
+# Other wikis were spared because they already rewrote the template in Lua
+",1447161101,PHID-USER-j4jntnatcouoxfrk74sh,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"I don't have the gerrit skills to parse the code to understand whether this change will allow a page to emit a tracking category specific to monitor articles and templates that need to be updated. If it will, some instruction would be helpful. If it currently will not, please make whatever code modification is necessary to allow a page to emit such a tracking category. Thank you. ",1446519651,PHID-USER-7cpk77uy2iq7bxf6hac6,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Change 246148 merged by jenkins-bot:
+Client-side migration for empty li preservation
+
+[[https://gerrit.wikimedia.org/r/246148]]",1446075996,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"Change 246148 had a related patch set uploaded (by Tim Starling):
+Client-side migration for empty li preservaton
+
+[[https://gerrit.wikimedia.org/r/246148]]
+",1444793336,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,"I'm going to introduce a migration tool to fix this bug, roughly following @cscott's suggestion, which is to preserve empty <li> tags through Tidy, but to add a class to those preserved elements which will be styled with display:none. It is believed that there are some templates which are producing empty list items because it is convenient for them as a way of omitting the list item for empty input. After the display:none hack is introduced, a user script would allow the expected changes to be visible to template maintainers. There is also a proposed change to log affected templates: https://gerrit.wikimedia.org/r/#/c/246106
+
+After a suitable migration period, the display:none rule would be removed, and list items would be visible as is desired by the multiple reporters of this bug.
+
+The empty <li> tags would be preserved through tidy by adding a datafld attribute, exploiting special case behaviour in Tidy's CanPrune() which was intended to fix http://sourceforge.net/p/tidy/bugs/337/
+",1444792377,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+Empty list items goes missing in the PHP parser when tidy is enabled,*** Bug 52374 has been marked as a duplicate of this bug. ***,1386112687,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cv5eyk43xupkutrvi7fo,task_subcomment,NA
+VisualEditor: Sequential floated images are stacking,"**Author:** `owen`
+
+**Description:**
+Looking at [[Principality of Stavelot-Malmedy]] in the Visual Editor, immediately after the heading ""Development and the High Middle Ages"" there are two images floated right.
+
+In Read mode, these images are given `float: right; clear: right;`. In VE mode, however, the `clear: right;` appears to be missing, so the images are stacking up.
+
+In case it makes a difference, I'm running Chrome 26.0.1410.64 m, on 64-bit Windows 7 Home Premium (Build 7601, Service Pack 1).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.org/wiki/Principality_of_Stavelot-Malmedy",1366925940,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-eaknwofmb4d2xflpnx7d,task_description,resolved
+VisualEditor: Sequential floated images are stacking,"This was fixed by gerrit 64367 which is now merged, but is 'experimental' and
+so will not go out for a short while. Marking as fixed within wmf5, though.",1369093844,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eaknwofmb4d2xflpnx7d,task_subcomment,NA
+VisualEditor: Sequential floated images are stacking,"This is because Parsoid outputs completely different HTML for images (using <figure> and what not) that doesn't match the MediaWiki CSS.
+
+This will be fixed once we change the ce.MWThumbImageNode rendering to match the MW rendering rather than the Parsoid rendering, and move image support out of the experimental list.",1366927394,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-eaknwofmb4d2xflpnx7d,task_subcomment,NA
+VisualEditor: Sequential floated images are stacking,"Confirmed - the DM layer for alien items (like images) apparently respects the CSS and is meant to pass it through, but CE isn't?",1366926217,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eaknwofmb4d2xflpnx7d,task_subcomment,NA
+[TUX] Page view doesn't fit long page titles,"A long title all mixed
+
+Long titles get compressed until they become unreadable, see URL and screenshot.
+
+--------------------------
+**Version**: master
+**Severity**: minor
+**URL**: https://meta.wikimedia.org/w/index.php?title=Special:Translate&language=de&group=page-Wikimedia+Blog%2FDrafts%2FTry+out+the+alpha+version+of+the+VisualEditor%2C+now+in+15+languages&filter=&action=page
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45924
+
+**Attached**: {F10857}",1366899360,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-7rd7dea5gzp4xsh4amok,task_description,declined
+[TUX] Page view doesn't fit long page titles,"So, on Vector this looks okay. On Monobook it looks like in the Vector screenshot above. Vector overrides the line-height for h1, Monobook doesn't. So the rule from Translate applies:
+``` 
+.tux-messagelist .tux-message-pagemode .tux-pagemode-translation {
+	color: #222;
+	font-size: 16px;
+	line-height: 1.5em;
+	padding-left: 20px;
+}
+```
+
+Since it is still readable and Monobook is not my favorite skin, I'm inclined to decline this as not worth fixing in Translate. It would be nice of Monobook also set the line-height when overriding font-size for headings.",1607413610,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-7rd7dea5gzp4xsh4amok,task_subcomment,NA
+[TUX] Page view doesn't fit long page titles,"Created attachment 12173
+Same long title just partly overlapping in another browser
+
+**Attached**: {F10858}",1366899451,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-7rd7dea5gzp4xsh4amok,task_subcomment,NA
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)","1. Parsoid not running, VisualEditor enabled on to-be-created page X
+2. Enter a few words 
+3. ""Review and Save""
+4. Loader keeps spinning indefinitely
+
+Request:
+
+action=visualeditor&paction=serialize&html=%3Cp+data-ve-changed%3D%22%7B%26quot%3Bcontent%26quot%3B%3A7%7D%22%3Edfgdg%3C%2Fp%3E&page=Sandbox%2F1&oldid=0&token=%2B%5C&format=json
+
+Response:
+
+{""visualeditor"":{""result"":""success"",""content"":false}}
+
+No errors.
+
+Note this bug could also be reported as ""Loader keeps spinning forever when creating a new page and trying to review/save it""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366757460,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jrrnahwoyus5omqe5ox7,task_description,resolved
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)",Merged into master; will go out with wmf5.,1368638813,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jrrnahwoyus5omqe5ox7,task_subcomment,NA
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)",Related URL: https://gerrit.wikimedia.org/r/63861 (Gerrit Change I6bdd177bc9b5a0af9107cf08d8e46470c6778e12),1368631835,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jrrnahwoyus5omqe5ox7,task_subcomment,NA
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)","(In reply to comment #1)
+> Related URL: https://gerrit.wikimedia.org/r/60613 (Gerrit Change
+> Icdf64a792c13a326f494e051be47f2946928d142)
+
+This fixed the visible problem described below:
+
+(In reply to comment #0)
+> as ""Loader keeps spinning forever when creating a new page and
+> trying to review/save it""
+
+The error is now handled by stopping the spinner (as we always do after an aborted load) and display the error.
+
+The error message in my case was ""No Wikitext content in response from server"" triggered from ve.init.mw.Target.onSerialize's patch where there are no errors and eventually finds this by type-checking the content property.
+
+Lowering priority. Todo tasks:
+
+* Don't return status ""success"" if content is missing, but use status ""error"".
+
+* Make it not just status ""error"" but actually trigger a proper API response.error property with a more direct error, namely that the Parsoid server is unavailable.",1366762868,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jrrnahwoyus5omqe5ox7,task_subcomment,NA
+"VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status ""success"" with missing content)",Related URL: https://gerrit.wikimedia.org/r/60613 (Gerrit Change Icdf64a792c13a326f494e051be47f2946928d142),1366761720,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jrrnahwoyus5omqe5ox7,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit musical scores,"As a VisualEditor plugin inside the extension, provide a visual way for users to create and edit musical scores.
+
+This would be a (very) major undertaking, even if there is an existing JavaScript-based visual Lilypond score editor, or failing that, a visual score editor with a different output format which would need to be converted to Lilypond. A brief search found a few promising leads for ABC editors, but mostly based in Flash.
+
+Still, hopefully not just a pipedream. :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366688580,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_description,open
+Create a VisualEditor plugin tool to add/edit musical scores,"Note that as of November 2015 there is a nice previewing editor for Scores, but it's still based on the Lilypond or ABC source format rather than a visual one.",1459667871,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit musical scores,">>! In T49528#1003822, @Tgr wrote:
+> Just adding a text editor with a preview button, like e.g. [[ http://lilybin.com/ | lilybin.com ]] does it, does not sound that hard.
+
+Indeed, but this task is asking for a visual drag-and-drop sheet music editor.
+
+> I wonder if that could even be a generic fallback option for tag-based parser extensions without a dedicated editor plugin.
+
+That's already provided in VisualEditor.",1422635139,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit musical scores,"Just adding a text editor with a preview button, like e.g. [[ http://lilybin.com/ | lilybin.com ]] does it, does not sound that hard. I wonder if that could even be a generic fallback option for tag-based parser extensions without a dedicated editor plugin.",1422602902,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit musical scores,"See also
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-June/069973.html",1371406501,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-ndh2cqs25x7mmcs6xaye,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"On VE load, do an ""originalHtml == serialise(linmod(originalHtml)"" or whatever and fail out of the VE if false; ideally, also allow the user to submit a failure report for debugging purposes (this will need to get checked through with legal).
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366667700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-inty44ufbm7rwhc55mom,task_description,resolved
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,Written and about to be deployed.,1372387346,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"Change 70106 merged by jenkins-bot:
+mw.ViewPageTarget: Add sanity check for DOM roundtrip
+
+https://gerrit.wikimedia.org/r/70106",1372387306,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"Change 70106 had a related patch set uploaded by Krinkle:
+mw.ViewPageTarget: Add sanity check for DOM roundtrip
+
+https://gerrit.wikimedia.org/r/70106",1372381883,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"Any news on this? 
+
+Having some automated general sanity checks on the returned wikitext (for example size, check if it starts with a doctype) would also be good, especially now that users don't see a diff by default any more. If any of the automated sanity checks fail, you should probably ask the user to review changes before saving. This should catch most major article corruption issues before they happen.",1371496468,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,Pulling.,1370449877,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,Roan's offered to do this one on his flight. Marking as such.,1368766983,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"We are diffing on the DOM on the way in, but while debugging a text diff is useful too.
+
+Order preservation is not guaranteed in the DOM4 spec afaik, but is implemented and supported nevertheless using the attributes collection and numerical indexing: https://developer.mozilla.org/en-US/docs/DOM/Node.attributes",1367265092,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"We wouldn't be doing string-based comparisons, we'd be doing DOM-based comparisons. That's what Parsoid should be doing too, IMO.
+
+If comparisons are DOM-based, quoting style and attribute order don't matter. In general, I don't believe there's a way to read or write attribute order in the DOM.",1367264016,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same,"A common issue currently is changes in attribute order and a change of quoting style for JSON attributes. It would be great if VE could preserve the order of attributes. 
+
+For the quoting, we have some smart quoting code that you could reuse. Alternatively, you can compare the innerHTML of the original DOM with the exported DOM as that implicitly changes JSON attribute quoting to the verbose style.",1367256333,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-inty44ufbm7rwhc55mom,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","The ""language conversion blocks"" are a wikitext feature that allow users to define text content in parallel scripts. The most high profile is in Chinese, which has two major writing systems and automated conversion between them, but there are 28 others, some of which are not automated conversion (so VE will need to not just mark the text with an appropriate <span>, but allow the user to understand when they have edited text that needs editing twice or thrice (possibly in scripts they cannot/do not want to use?) - see https://meta.wikimedia.org/wiki/Wikipedias_in_multiple_writing_systems
+
+Documentation of the feature (focussed on the syntax) is here: https://www.mediawiki.org/wiki/Writing_systems/Syntax
+
+Parsoid will need to add support for this first, which is {T43716}.",1366380120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_description,resolved
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis",">>! In T49411#3691289, @Deskana wrote:
+> I believe there's still more outstanding here, right?
+
+Yes, see  {T43716} - phase 1 support is complete, which brings VE to parity with the PHP parser -- in both cases, as soon as you start to edit the page you're confronted with the raw un-converted text (not the text in your preferred variant).
+
+VE can do better (in theory) -- that's ""phase 3"" of T43716.  But that's probably another bug.  Since VE is now at parity with PHP source editing, I think this task can be resolved, and we'll open specific bugs for deficiencies in the current UX (ie, T182910).  I'll open a new task for the VE side of Parsoid's phase 3, once we get there, but that's a new feature.",1513281041,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","I believe there's still more outstanding here, right?",1508260389,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 361921 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Inspectors for editing LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/361921]]
+",1505493098,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 358396 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Context item for LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/358396]]
+",1502461750,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 356739 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Display LanguageConverter markup in VisualEditor
+
+[[https://gerrit.wikimedia.org/r/356739]]
+",1500998488,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis",See https://www.mediawiki.org/wiki/Parsoid/Language_conversion#Testing_LanguageConverter_with_Parsoid_and_VisualEditor for setup & test hints.,1498753539,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 361921 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):
+[mediawiki/extensions/VisualEditor@master] WIP: Dialog for editing LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/361921]]
+",1498674768,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 358396 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):
+[mediawiki/extensions/VisualEditor@master] Node inspector for LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/358396]]
+",1497285783,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","@deskana sure:  Theres's fully-functioning Parsoid support in https://gerrit.wikimedia.org/r/140235 (T43716 phase 1).  VE currently ""alienates"" these blocks, which means they are invisible and uneditable but round-trip fine if you don't touch them.
+
+I'm currently working on some basic support for displaying/editing the language converter rules in VE (which is what this task is about).  Very rough start of a patch above; there are some representation issues to work out.  VE is a little weak on directly editing generated content.  I'll copy some discussion with @Catrope here:
+
+(05:17:05 PM) cscott-free: Roan: is there any precedent in VE for an inline BranchNode ?
+(05:17:30 PM) cscott-free: that is, a Node that behaved like an annotation: you could edit inside it, and it was laid out inline.
+(05:17:43 PM) RoanKattouw: No I don't think so
+(05:18:01 PM) RoanKattouw: There are inline nodes like images
+(05:18:14 PM) cscott-free: yes, but they are ve.ce.LeafNodes, not allowed to have any contents
+(05:18:22 PM) RoanKattouw: But no inline nodes that have children
+(05:18:33 PM) cscott-free: even BlockImage is a LeafNode, and you have to click into the inspector to edit the caption
+(05:18:38 PM) RoanKattouw: Yeah
+(05:18:52 PM) RoanKattouw: So, I would like us to have inline editing of image captions
+(05:19:01 PM) RoanKattouw: But it wouldn't be done that way
+(05:19:09 PM) RoanKattouw: What is the application you have in mind?
+(05:19:34 PM) cscott-free: I tried to use toDataElement to convince the dm that my `<span>` was actually an annotation, but that didn't work quite right with generated content.
+(05:20:24 PM) cscott-free: `-{R|foo}-` is a silly sort of `<nowiki>`, right?  But it's represented by Parsoid as `<span typeof=""mw:LanguageVariant"" data-mw-variant='{....text:""foo""}'></span>`
+(05:20:43 PM) RoanKattouw: What does that syntax mean again?
+(05:21:01 PM) cscott-free: It just means ""protect `foo` from language conversion""
+(05:21:09 PM) RoanKattouw: Aha OK
+(05:21:20 PM) cscott-free: but there are other similar forms
+(05:21:22 PM) RoanKattouw: Does it also output Foo?
+(05:21:25 PM) cscott-free: yes
+(05:21:37 PM) RoanKattouw: Then shouldn't the span be not empty?
+(05:21:49 PM) cscott-free: well... maybe.
+(05:22:16 PM) RoanKattouw: I mean, at least for display purposes you would want that, right?
+(05:22:22 PM) cscott-free: see https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec/Language_conversion_blocks#Alternative_2
+(05:22:45 PM) RoanKattouw: Also, am I allowed to have annotations inside?
+(05:22:56 PM) RoanKattouw: Can part of foo be bold, or a link?
+(05:23:01 PM) cscott-free: yes, you can have annotations inside
+(05:22:56 PM) cscott-free: the idea is that eventually we'll do the actual language conversion client-side, and so we'd fill the empty spans with the correct thing based on the currently-selected variant
+(05:23:12 PM) RoanKattouw: Oh, I see
+(05:23:30 PM) RoanKattouw: So it behaves kind of like a reference then
+(05:23:42 PM) RoanKattouw: Or a mix between that and an auto numbered link
+(05:23:43 PM) cscott-free: in other cases, there might be more than one possible output in there, and I only want to see one of them (at a time)
+(05:23:49 PM) RoanKattouw: Right
+(05:24:10 PM) RoanKattouw: So the content isn't text then, it's HTML
+(05:24:14 PM) cscott-free: yeah
+(05:24:38 PM) cscott-free: and it's got the usual ""could be block, could be inline"" thing that MWTransclusionNode deals with
+(05:24:55 PM) RoanKattouw: That's a tricky one, I'd recommend picking edsanders and David's brains too
+(05:25:12 PM) RoanKattouw: The fact that it can be block is very annoying
+(05:25:23 PM) RoanKattouw: That makes it hard to make it an annotation
+(05:26:01 PM) cscott-free: RoanKattouw: yes, and it's something I'd eventually like to fix on the PHP side.  But there are a few cases like -{zh-cn:==Foo==;zh-tw:==Bar==}-
+(05:26:15 PM) cscott-free: which should really be rewritten as == -{zh-cn:Foo;zh-tw:Bar}- ==
+(05:27:19 PM) cscott-free: usual annoying story about balance, templates, markup boundaries, etc.
+(05:26:14 PM) RoanKattouw: Right
+(05:25:13 PM) cscott-free: At any rate, I guess the easiest way to get started here is to implement it as a 'boring' LeafNode and not allow direct editing, you'll have to use an inspector
+(05:27:15 PM) RoanKattouw: If it's only annotated text, then you could make it an annotation that would have to do some magic to generate its own content and feed the right content back into data-mw
+(05:29:03 PM) cscott-free: yeah, with an annotation i just hit a roadblock in ve.dm.Converter:getDomSubtreeFromData which doesn't give me a way to return the annotation *and* the data contained as an array from toDataElement, the way that nodes can
+(05:29:30 PM) cscott-free: so I might patch that and handle the case where toDataElement returns an array of length > 1 from toDataElement
+(05:29:45 PM) cscott-free: but figured I'd check to make sure I wasn't missing something obvious first
+(05:30:01 PM) RoanKattouw: Yeah you'll have to invent something new here
+(05:30:16 PM) RoanKattouw: In both directions
+(05:30:31 PM) RoanKattouw: Or add pre- and post-processing steps
+(05:30:15 PM) cscott-free: I might also just give in an generate explicit <span typeof=""mw:LanguageVariant/raw"">foo</span> for some of these cases
+(05:30:24 PM) cscott-free: which would be a more direct analog of <nowiki>
+(05:30:43 PM) RoanKattouw: Also look at how nowiki works on the way out
+(05:31:07 PM) RoanKattouw: It's not really the same, it drops the annotation, but it might give you ideas
+(05:31:04 PM) cscott-free: If you did -{foo<div>bar}- then I *think* the usual HTML5 treebuilding would split the <span> over the <div> and you'd effectively get -{foo}-<div>-{bar}-
+(05:31:32 PM) cscott-free: that works for the ""raw output"" case, but things get really hairy if there are multiple alternatives.
+(05:31:38 PM) RoanKattouw: Well if the resulting HTML is too weird, you can just alienate it
+(05:32:25 PM) RoanKattouw: Which might even happen automatically because of special treatment of the mw: prefix and protections against misnesting
+(05:33:13 PM) cscott-free: yeah, right now VE is alienating everything which is fine but because the <span>s are empty the result is that the content goes missing
+(05:33:43 PM) cscott-free: again, maybe an indicator that this whole ""empty span to be filled with converted output"" idea isn't all that hot.  we'll see.
+(05:34:20 PM) cscott-free: anyway, I think using a Node and just dealing with non-direct editing is the way to go for the crappy-first-draft.
+(05:34:32 PM) cscott-free: although i'm curious how you planned to allow direct figure caption editing
+(05:41:02 PM) RoanKattouw: cscott: Basically, make captions work the way references work, with their contents being in an internalList item or subdocument, then create a surface on that subdoc and embed it in the image frame
+(05:41:22 PM) RoanKattouw: The subdocuments thing is a refactor I started in 2014 and never finished
+(05:42:25 PM) RoanKattouw: You could also do it without changing the DM representation if you are able to make a surface for a subset of the document
+(05:42:54 PM) RoanKattouw: But the change in representation would allow inline images to retain captions
+(05:44:55 PM) cscott-free: Yeah, I just would want to be able to cursor seamlessly ""into"" the embedded subdoc.",1496353510,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis","Change 356739 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):
+[mediawiki/extensions/VisualEditor@master] WIP: Specialized inspector for LanguageConverter markup
+
+[[https://gerrit.wikimedia.org/r/356739]]
+",1496351770,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+"VisualEditor: Support ""Language conversion blocks"" for multi-script wikis",@cscott Any updates for us on this since it's reopened? :-),1496332721,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-fqccocu2hyrbuqx5yi6l,task_subcomment,NA
+VisualEditor: MWTemplateNode should serialize original HTML if unchanged,"If we get an MWTemplateNode and the user doesn't change it, then in the data->DOM conversion we should serialize it back out the way it came in, including all the other nodes (the template contents) that we normally discard.
+
+Discarding these nodes when the user did change the template (i.e. the attributes changed) is fine and encouraged, but if we also do it when nothing changed, Parsoid's DOM diff algorithm will notice that we changed something in the DOM, causing selective serialization not to skip the template while it should.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366341300,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ctzq3dsxntnt7zcuqb4y,task_description,resolved
+VisualEditor: MWTemplateNode should serialize original HTML if unchanged,Related URL: https://gerrit.wikimedia.org/r/60110 (Gerrit Change I2bbb5d2d6a90c4eb87fa129671112c92a9b931e7),1366474230,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ctzq3dsxntnt7zcuqb4y,task_subcomment,NA
+VisualEditor: Caption tags are stripped from tables when VE converts data model to DOM,"1. Go to: http://ve-change-marking.instance-proxy.wmflabs.org/wiki/Test2
+2. Open page in VisualEditor
+3. Open browser console.
+4. Run ve.dm.converter.getDomFromData( ve.instances[0].documentModel.store, ve.instances[0].documentModel.data.data ).body.outerHTML
+5. You get the following output:
+--------------
+<body><table data-parsoid=""{&quot;tsr&quot;:[0,3],&quot;dsr&quot;:[0,49,3,2]}"">
+This is a caption
+<tbody data-parsoid=""{&quot;dsr&quot;:[24,47,0,0]}""><tr data-parsoid=""{&quot;tsr&quot;:[24,26],&quot;startTagSrc&quot;:&quot;|-&quot;,&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[24,46,2,0]}"">
+<td data-parsoid=""{&quot;tsr&quot;:[27,28],&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[27,46,1,0]}"">Table cell content</td></tr>
+</tbody></table></body>
+----------------
+
+Notice the missing <caption> .. </caption> tags.
+So, when Parsoid gets this, the caption is fostered out and shows up as a diff.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1366256040,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bflgm4moy2wypdjtiaao,task_description,resolved
+VisualEditor: Caption tags are stripped from tables when VE converts data model to DOM,...which has already been merged.,1366298405,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bflgm4moy2wypdjtiaao,task_subcomment,NA
+VisualEditor: Caption tags are stripped from tables when VE converts data model to DOM,https://gerrit.wikimedia.org/r/59780,1366298361,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bflgm4moy2wypdjtiaao,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"See bug 45808 for the corresponding Parsoid bug.
+
+Currently editing a redirected page (say ""OLPC"") causes the following Bad Things to happen.
+
+a) the edited page content is saved back to ""OLPC"", overwriting the original #REDIRECT
+
+b) the page content is from ""One Laptop Per Child"", but with an added {{Redirect:OLPC}} template at the top; this extra template gets saved back with the rest of the edits.
+
+In bug 45808, Parsoid will return a special <meta> or <link> tag in the body for redirected pages.  This bug is for the corresponding VE support to recognize that tag and provide a user-friendly interface for editing redirects.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=47329",1366223100,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_description,resolved
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"(In reply to Gerrit Notification Bot from comment #10)
+
+Neat! Is there documentation about this panel and/or a place to test it?",1392359125,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Change 95213 merged by jenkins-bot:
+Let users set #REDIRECT and __STATICREDIRECT__ status
+
+https://gerrit.wikimedia.org/r/95213",1392349578,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Change 95213 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT
+
+https://gerrit.wikimedia.org/r/95213",1384373838,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Change 95103 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT, __NOTOC__, & __FORCETOC__
+
+https://gerrit.wikimedia.org/r/95103",1384313396,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,It is also possible to fail to convert a non-redirect page into a redirect (e.g following a merge).,1372791338,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"This is likely obvious to everyone, but:  We need a way to create redirects in VisualEditor from redlinks.
+
+VE is currently (02 July 2013) turned off for editing redirect pages at en.wikipedia.org.  However, it's still possible to create these pages using VE, which end up nowiki-ed and broken.",1372755903,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,Assigning to Jiabao Wu as discussed on bug 48489 comment 4.,1368806633,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Redirect editing disabled by https://gerrit.wikimedia.org/r/64275, will need to be re-enabled when this bug is addressed.",1368789997,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"Some quick advice on this one:
+
+* There'll need to be code in DM and UI; the code in Parsoid which it will interact with has just been merged into their master.
+* I'd suggest looking at how {{DEFAULTSORT}} works as a starting point - see https://gerrit.wikimedia.org/r/#/c/61374/ for the DM side.
+* On the UI side, you'd want to create a new panel in the meta-data dialog (""Page settings"" is probably the best name, though that's also the display name of the dialog, but we can fiddle with that later) into which you'd put a checkbox with an associated text box for a page name, with auto-suggest (like the link inspector has).",1368772067,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,There's now a spec for redirects in the DOM: http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Redirects,1366225893,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel,"This is probably a post-July task; have split off a ""don't fail horribly"" bug as bug 47329, linked.",1366224646,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pp5tg5rybcmy6c6xwggf,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Since at 2013-04-05 04:29:46 UTC, Zuul no more receives events from Gerrit. It uses a CLI command such as:
+
+    ssh -p 29418  jenkins-bot@manganese.wikimedia.org gerrit stream-events
+
+I did stream-events using both the jenkins-bot user and my own account 'hashar'. While submitting a new patchset or posting a comment: nothing is reported.
+
+The end effect is that no jobs are triggered in Jenkins.
+
+--------------------------
+
+Summary (13/12/2017)
+
+The sshd daemon (Mina) would lost connection on one way connections and hitting some kind of timeout.  That affected Zuul which idles with a `gerrit stream-events`.
+
+Gerrit sshd.idleTimeout got set to 10 days as a workaround https://gerrit.wikimedia.org/r/#/c/58126/
+
+Gerrit patch:
+
+https://gerrit-review.googlesource.com/c/gerrit/+/44472 ([[ https://gerrit.googlesource.com/gerrit/+/79b91bfe746121a81a785bdd3b24df2096410c55 | 79b91bfe ]]) is the Gerrit patch.
+",1365152280,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_description,resolved
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #24)
+> We previously rolled back to a gerrit that exposed the problem again :-(
+> 
+
+To expand on this, last week when we tried upgrading to 2.7-rc1-424-gef469ac we hit a bunch of problems so we rolled back. However, I rolled too far back to 2.6-rc0-144-gb1dadd2.war instead of 2.6-rc0-154-gfcdb34b which lacked the SSH timeout fix mentioned above.",1370873901,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"We previously rolled back to a gerrit that exposed the problem again :-(
+
+In case we ever do this again: To keep the zuul<->gerrit connection
+alive, it suffices to have at least one event fed to zuul each 10
+minutes.
+
+So for example clone our gerrit-ping repo.
+Restore
+  https://gerrit.wikimedia.org/r/#/c/58060/
+Fetch patch set 1.
+And run
+
+  while true ; do date ; ssh gerrit.wikimedia.org gerrit review -m ""'recheck'"" --verified 0 75be73703978e75a25d5e3bb5685c51580af3060 ; sleep 240 ; done
+
+in a shell (I had ssh configured to automatically supply username and gerrit port).
+
+Gerrit 2.6-rc0-154-gfcdb34b is the first version that we deployed and
+contained the fix.",1370873749,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,*** Bug 49330 has been marked as a duplicate of this bug. ***,1370869884,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #21)
+> Lowering priority and severity since we have a workaround now.
+
+Now actually doing so for priority too.",1368525775,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Lowering priority and severity since we have a workaround now.,1365494859,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,*** Bug 47004 has been marked as a duplicate of this bug. ***,1365449902,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Deployed the upstream patch just now.,1365422685,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #12)
+> (In reply to comment #10)
+> > https://gerrit-review.googlesource.com/#/c/44351/
+> > got submitted to upstream gerrit.
+> > 
+> 
+> It hasn't been reviewed / merged yet however. How long are we willing to
+> wait?
+> Can we apply it to our fork for now?
+> 
+> Jenkins being down is causing lots of workflow problems throughout the
+> different projects.
+
+We don't have a fork, we use vanilla Gerrit :)
+But yes, I'm looking into deploying this now rather than waiting on upstream to merge.",1365417296,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Until we can deploy a new gerrit build, we prevent timeouts by forcing a
+recheck on
+https://gerrit.wikimedia.org/r/#/c/58060/
+every 4 minutes.",1365413039,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Related URL: https://gerrit.wikimedia.org/r/58063 (Gerrit Change I431ff970596aae03b3ab5276303ed18574892b13),1365411081,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Related URL: https://gerrit.wikimedia.org/r/58060 (Gerrit Change Ie0b3b0a5d77a2192abd09a934e780b8e622a1edd),1365410487,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Related URL: https://gerrit.wikimedia.org/r/58059 (Gerrit Change Ie0b3b0a5d77a2192abd09a934e780b8e622a1edd),1365408553,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"For the context:
+
+Zuul is a python daemon running on gallium. It establish a ssh connection as jenkins-bot on manganese.wikimedia.org and runs the 'gerrit stream-events' command.   It expect JSON object to be returned.
+
+Looking at the Zuul log (fgrep GerritWatcher /var/log/zuul/zuul.log), it does emit a stacktrace every 10 minutes:
+
+
+2013-04-08 05:50:48,028 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:00:53,176 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:10:58,266 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:21:03,383 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:31:08,472 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:41:13,594 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 06:51:18,687 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+2013-04-08 07:01:23,782 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+
+A full trace is:
+
+
+2013-04-08 00:12:10,016 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+Traceback (most recent call last):
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 68, in _run
+    self._listen(stdout, stderr)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 52, in _listen
+    self._read(stdout)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 39, in _read
+    data = json.loads(l)
+  File ""/usr/lib/python2.7/json/__init__.py"", line 326, in loads
+    return _default_decoder.decode(s)
+  File ""/usr/lib/python2.7/json/decoder.py"", line 366, in decode
+    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
+  File ""/usr/lib/python2.7/json/decoder.py"", line 384, in raw_decode
+    raise ValueError(""No JSON object could be decoded"")
+ValueError: No JSON object could be decoded
+
+
+Which is stream-events sending some invalid JSON, most probably something like ""Connection timed out after 10 minutes"".    It seems Zuul properly reconnect the ssh connection.
+
+
+Whenever the stream-events for Zuul, it is also blocked for any other user even on a fresh new connection.  For example, I could run the stream-events command using my own account, fill a comment in Gerrit and I get no event on the channel.",1365407692,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #10)
+> https://gerrit-review.googlesource.com/#/c/44351/
+> got submitted to upstream gerrit.
+> 
+
+It hasn't been reviewed / merged yet however. How long are we willing to wait? Can we apply it to our fork for now?
+
+Jenkins being down is causing lots of workflow problems throughout the different projects.",1365397526,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Raising importance, this needs fixing ASAP. We need testing. Not just to save work, but because we (and by design and intention) rely on it automatically happen and performing the merge action on approval.
+
+Also the lack of postmerge events is blocking (auto-deploy for certain projects).",1365391228,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Although I cannot reliably reproduce the problem, the culprit seems to
+be gerrit's version bump of Apache SSHD to 0.6.0, which comes with
+closing of idle ssh connections.
+
+Upon 10 minutes of inactivity, gerrit disconnects Zuul, and Zuul has
+to reconnect. Gerrit accepts the connection, but sometimes refuses to
+stream events over the new connection. There seems to be some race
+condition in gerrit when Zuul reconnects.
+
+We can mitigate the problem by having at least 1 commit every 10
+minutes... Go, programmers go :-))
+
+To also have a solution until we get that commit density 24/7,
+https://gerrit-review.googlesource.com/#/c/44351/
+got submitted to upstream gerrit.
+
+(We cannot simply downgrade gerrit to the last known good version, as
+that would require database schema downgrading, which currently is not
+supported by gerrit)",1365379934,PHID-USER-pntojlcbclwhuip53bix,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Stuck again but this time show-queue gives me:
+
+Task     State                 Command
+------------------------------------------------------------------------------
+5229a073                       git-upload-pack '/mediawiki/extensions/VisualEditor' (shirayuki)
+aad42f27 07:18:57.201          inside-wmf/mediawiki/extensions/FundraisingEmailUnsubscribe
+------------------------------------------------------------------------------
+
+Logged a message on IRC about it and pinged ops list.",1365319742,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Changing back to git/gerrit. Zuul has no issue, it is Gerrit holding the events and not emitting them.",1365318838,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"The Zuul log is full of the following:
+
+2013-04-06 17:02:55,441 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+Traceback (most recent call last):
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 68, in _run
+    self._listen(stdout, stderr)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 52, in _listen
+    self._read(stdout)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 39, in _read
+    data = json.loads(l)
+  File ""/usr/lib/python2.7/json/__init__.py"", line 326, in loads
+    return _default_decoder.decode(s)
+  File ""/usr/lib/python2.7/json/decoder.py"", line 366, in decode
+    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
+  File ""/usr/lib/python2.7/json/decoder.py"", line 384, in raw_decode
+    raise ValueError(""No JSON object could be decoded"")
+ValueError: No JSON object could be decoded",1365268135,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Restarted again, since stram-events hung. The output from the queue is kind of weird & concerning:
+
+$ ssh gerrit.wikimedia.org gerrit show-queue -w
+Task     State                 Command
+------------------------------------------------------------------------------
+9c0dc448                       com.google.gerrit.sshd.commands.StreamEvents$3@6435207f
+85d6cd95                       com.google.gerrit.sshd.commands.StreamEvents$3@5be8a53e
+c54125b8                       com.google.gerrit.sshd.commands.StreamEvents$3@6b8b896
+a0d428db                       com.google.gerrit.sshd.commands.StreamEvents$3@495e834c
+0323c3c0                       com.google.gerrit.sshd.commands.StreamEvents$3@5bfe1835
+49cc90ac                       com.google.gerrit.sshd.commands.StreamEvents$3@6e76ec2
+e9bf84a4                       com.google.gerrit.sshd.commands.StreamEvents$3@44188618
+4617a0ff                       com.google.gerrit.sshd.commands.StreamEvents$3@260bb495
+5e8f7686                       com.google.gerrit.sshd.commands.StreamEvents$3@4a7cb5b6
+fe9f4ab9 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@40811f5d
+3e416208 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7194d12c
+1e449e17 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5d3233c0
+de9a86cc waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7efe402f
+9ea40e12 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@ae3b20d
+bea9d2e8 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6abe7910
+be3472ba waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6130d9f5
+5e4a1628 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4e3595ac
+1915a152 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@417de5ee
+3943c55a waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1ff57751
+9938b1f3 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5a31e6f7
+f911ad68 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2329064
+593eb9dd waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@f04a851
+9982f1fc waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@30828dd9
+665afa9e waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2c6c773b
+066e9e41 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@507d946
+23f714d9 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4b2eba70
+0ff474d2 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@68d2359f
+6fc0906b waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@40be8f7c
+835cc5a8 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1ebe3719
+63619163 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5a135a13
+c3563d8b waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2c7ec398
+a35b09b3 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@365b46fa
+0370d533 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2290e2f7
+e36ca160 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5624d7db
+436a4d46 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@cd7970c
+23671980 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1dfd9b6a
+63fd11f8 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@74e65b87
+83fda551 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3f833806
+5d722e74 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3fd3327d
+bd77aa62 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4297cd47
+9d7c2648 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7c261278
+bdab2a74 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2786c3f5
+baa810b1 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@ab1e19
+7f44cb17 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6244fba6
+bf4ec337 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@194923d6
+df493731 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@10cfc392
+ff2f5b61 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4649853e
+1f334fd3 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4cacd7f
+7f160b2c waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1ee581b1
+046d445a waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6da59b4f
+64b8c066 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@137797c6
+848db42c waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@108d5226
+4926f573 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2e0c4547
+8bfdc551 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1e794f4e
+2b8db900 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2e459983
+6b02d146 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@27984fef
+cb073d54 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5b617f30
+ab0c4979 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5de5572e
+eb0d6177 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@45a5965c
+0b11d594 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7a3295bc
+783069a2 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@a7e838
+46810952 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@f7eb4de
+267e5542 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7bbebd2a
+868b8174 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@27754fde
+c694199b waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@6ce8c0f
+6688cd79 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@624d3046
+c6e3b962 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@479462c4
+06f1d196 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5ee05692
+554535c0 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3830aedd
+b235a762 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4284bfd
+f23f9f40 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@399c7615
+923ae350 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4f0c7a3f
+d244dbcb waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@7ac6658a
+3249b7e2 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@773485fe
+7253af98 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3c2de6a4
+1246f3d4 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@698137d9
+5250eb8b waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@5a53bbe7
+5288eb78 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2f556905
+cc3d20e4 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@1061df8a
+2c32bc16 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@2279bdac
+0c2fb8ac waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@669378e2
+0c5a59a0 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@66280ecb
+6c4e75e4 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@4fe365d2
+4c4b71d4 waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@99ae56d
+f650f82e waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@184c5c08
+e71cc87a waiting ....          com.google.gerrit.sshd.commands.StreamEvents$3@3d2e1dae
+d36dcb8e 12:18:22.186          push gerritslave@formey.wikimedia.org:/var/lib/gerrit2/review_site/git/mediawiki/extensions/FundraisingEmailUnsubscribe.git
+da7faee1 19:42:45.214          Log File Compressor
+------------------------------------------------------------------------------
+  88 tasks",1365250715,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"(In reply to comment #4)
+> Ariel restarted Gerrit on manganese. That unbroken the stream-events thus
+> cleaning the issue.
+
+Thanks. Lowering priority.",1365156991,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Ariel restarted Gerrit on manganese. That unbroken the stream-events thus cleaning the issue.
+
+I am leaving this bug open for monitoring / investigation.  There must be some regression in Gerrit since we upgraded it yesterday.",1365154819,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,Restarted Zuul just in case: nothing. Definitely on Gerrit side.,1365154404,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,"Gerrit has been upgraded with https://gerrit.wikimedia.org/r/#/c/57508/
+Which got merged on Apr 4, 2013 20:29 (UTC).
+
+Apparently Gerrit got restarted at 20:44 (UTC), the Zuul log shows errors 500 at that time.
+
+The last event received by Zuul was on 2013-04-05 04:26:56 (UTC) then the JSON events cant be decoded / are not received:
+
+2013-04-05 04:29:46,092 ERROR gerrit.GerritWatcher: Exception on ssh event stream:
+Traceback (most recent call last):
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 68, in _run
+    self._listen(stdout, stderr)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 52, in _listen
+    self._read(stdout)
+  File ""/usr/local/lib/python2.7/dist-packages/zuul-0.0.151.e9d929a-py2.7.egg/zuul/lib/gerrit.py"", line 39, in _read
+    data = json.loads(l)
+  File ""/usr/lib/python2.7/json/__init__.py"", line 326, in loads
+    return _default_decoder.decode(s)
+  File ""/usr/lib/python2.7/json/decoder.py"", line 366, in decode
+    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
+  File ""/usr/lib/python2.7/json/decoder.py"", line 384, in raw_decode
+    raise ValueError(""No JSON object could be decoded"")
+ValueError: No JSON object could be decoded",1365154348,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+Zuul: Gerrit's ssh event stream unavailable,This is a major regression in our development workflow.,1365153289,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-t6pdz2y6vcq57sem2c5t,task_subcomment,NA
+VisualEditor: Normalize all preservation to use HTML store,"All HTML preservation should be changed to store the full HTML of the node/annotation and use the HTML store. This means removing the html/* attributes from nodes, and the strange things (original tag name and attributes) we put in annotations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1364432880,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pi36geznysiuvpgm2xg5,task_description,invalid
+VisualEditor: Normalize all preservation to use HTML store,Roan tells me we went in a different direction with this.,1370307483,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pi36geznysiuvpgm2xg5,task_subcomment,NA
+VisualEditor: Normalize all preservation to use HTML store,This also needs corresponding changes in the CE code for whitelisted rendering.,1364433518,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-pi36geznysiuvpgm2xg5,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,"Though T41598 will mean that VisualEditor will be able to edit infoboxes as they are now (alongside other templates), in the near-future Wikidata will replace a great many of the entries in these infoboxes with Wikidata queries (syntax still to be locked down).
+
+For the VisualEditor to be truly useful for users in this context, users should be able to:
+* add, review, modify and remove references to existing Wikidata queries;
+* add or amend arbitrary Wikidata queries for the above; and
+* do so in both VisualEditor-mode contexts (paragraphs of text etc.) and wikitext-mode contexts (like the template dialog as it will initially be).
+
+--------------------------
+**See Also**:
+{T41598}",1364168100,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-wlq23wlr4vjsce4a5eom,task_description,open
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,Is this task related to {T131661} or vice versa?,1461569518,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,"[[ https://de.wikipedia.org/wiki/Wikipedia_Diskussion:Wikidata#Listenerstellung | Here ]] I made a detailed proposal for a mechanism to edit Wikidata claims in every mode you can view a page. (wikitext, visual editor, preview, view).
+
+If you are interested, I can transakte it form German to English.",1461510555,PHID-USER-4z6eerx3m7iocsrcpku5,True,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,"[[ https://de.wikipedia.org/wiki/Wikipedia_Diskussion:Wikidata#Listenerstellung | Here ]] I made a detailed proposal for a mechanism to edit Wikidata claims in every mode you can view a page. (wikitext, visual editor, preview, view)",1461510510,PHID-USER-4z6eerx3m7iocsrcpku5,True,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,I consider this very important. We'll unfortunately not be able to dedicate resources to this in the near future. Does your team have them? We should discuss in this case how exactly this should all look like in the end.,1383578295,PHID-USER-7n5fvppwj4ueprv2iuys,True,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+Create a VisualEditor plugin tool to insert/edit references to Wikidata queries,[replacing wikidata keyword by adding CC - see bug 56417],1383221707,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-wlq23wlr4vjsce4a5eom,task_subcomment,NA
+VisualEditor: Annotation API fixes,"* Make toHTML() return real DOM nodes, we don't need the weird construction for CE any more
+* Pass in the content so it's possible to have rules like ""if the annotation only covers whitespace, strip it""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363986660,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ywpcq2rcuhvgvzt5k6zj,task_description,resolved
+VisualEditor: Annotation API fixes,It's a T39835 issue.,1428423652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ywpcq2rcuhvgvzt5k6zj,task_subcomment,NA
+VisualEditor: Annotation API fixes,"I didn't know whether to reopen this or add a note to T39835, but looks like it's still possible to [[ https://fr.wikipedia.org/w/index.php?title=Asselin_(entreprise)&curid=8746091&diff=113502024&oldid=112208671 | create an empty wikilink ]]? ",1428045874,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ywpcq2rcuhvgvzt5k6zj,task_subcomment,NA
+VisualEditor: Annotation API fixes,Now done.,1366141186,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ywpcq2rcuhvgvzt5k6zj,task_subcomment,NA
+[Regression] VisualEditor: Error in load() leaves page in dimmed state (Uncaught TypeError: Cannot call method 'removeAllListeners' of null),"Steps to reproduce issue:
+* MediaWiki + VisualEditor (no Parsoid)
+* Edit page (dims the page while loading)
+* Error pops up (parsoidserver-http-curl-error)
+* Cancel
+
+Expected:
+ Page undims.
+
+Actual:
+ Page still dimmed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363973460,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qe3ooothxjpeykl2xzld,task_description,resolved
+[Regression] VisualEditor: Error in load() leaves page in dimmed state (Uncaught TypeError: Cannot call method 'removeAllListeners' of null),"Change-Id: I91ad2b110c2c523a4bb367407e3f33a953328ab4
+
+That should fix it for now (quick fix). I'm now going to look into how much of this can be refactored to avoid this in the first place. It's all a bit too fragile.",1363976526,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qe3ooothxjpeykl2xzld,task_subcomment,NA
+[Regression] VisualEditor: Error in load() leaves page in dimmed state (Uncaught TypeError: Cannot call method 'removeAllListeners' of null),"Caused by I7769bd5a5b79f1ab36f258ef9f2be583ca503ce6.
+
+In the refactoring Trevor moved the initialisation of the DOM element for the save/cancel buttons from the ve.init.mw.ViewPageTarget constructor to ve.init.mw.ViewPageTarget#setupToolbarButtons, which isn't called until after a successful load.
+
+So, when #load() is called from #activate() and fails a loadError is emitted. onLoadError then calls #deacativate() which calls #tearDownToolbarButtons()
+
+But tearDownToolbarButtons is unable to call this.toolbarCancelButton.removeAllListeners because the button doesn't exist yet because setupToolbarButtons was never called.",1363976008,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qe3ooothxjpeykl2xzld,task_subcomment,NA
+VisualEditor: Trying to auto select a word just after an alien node causes an exception in rangy.,"1. Load the 'aliens' example document.
+2. Place the cursor in front of the first 'Lorem' and hit the link button.
+3. Observe the exception
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363548060,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2a3roys3zrsyau3jssx7,task_description,resolved
+VisualEditor: Trying to auto select a word just after an alien node causes an exception in rangy.,Marking as fixed for -04-01 as it wasn't for -03-18.,1364223708,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2a3roys3zrsyau3jssx7,task_subcomment,NA
+VisualEditor: Trying to auto select a word just after an alien node causes an exception in rangy.,Looks to be fixed in master now. Not sure which commit did it....,1364218671,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2a3roys3zrsyau3jssx7,task_subcomment,NA
+VisualEditor: Trying to auto select a word just after an alien node causes an exception in rangy.,"Ed, I can't reproduce it the way you described it. Please note that around first 'Lorem' (first paragraph) there is no alien (inline nor block).",1363801281,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-2a3roys3zrsyau3jssx7,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"**Author:** `lukebenes`
+
+**Description:**
+I see from [http://en.wikivoyage.org/wiki/Wikivoyage:Accommodation_listings The Accomodations Listing suggested style you want people to continue to use the wikitravel tags. But I do not see any tools to automate the process. 
+
+If you look at the Add and Edit Listing Feature listing like those that can be found [http://wikitravel.org/en/Wikitravel:Small_city_article_template#Sleep here] and [http://wikitravel.org/en/Trat#Sleep here]? You'll see there is a tool to edit these tag. 
+
+This tags is extremely useful to organize data and make quick edits. For example, I have fixed many incorrect phone numbers and addresses using this helpful tool. Please consider adding this feature the MediaWiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1363453140,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tqro35vsrplftuemdxbd,task_description,declined
+Create a VisualEditor plugin tool to add/edit Listings,"{T354997}
+
+Listings nowdays are just template calls, which VisualEditor has reasonable tools to edit.",1719889959,PHID-USER-escte3psz5yfd2nj3jzr,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,">>! In T48225#2501154, @T.seppelt wrote:
+> Since listings are highly structured and can be shared across several Wikivoyage language versions, Wikidata editing should be implemented before rolling this out.
+
+Certainly, I think storing this data in Wikidata would be a good move. I'm not absolutely sure it should happen first, but I suppose it depends on who wants to work on what. :-)",1469817709,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"Since listings are highly structured and can be shared across several Wikivoyage language versions, Wikidata editing should be implemented before rolling this out. I added T141345 for this. 
+
+Note also that there is https://en.wikivoyage.org/wiki/Wikivoyage:Listing_editor, a tool especially designed for editing listings.",1469686526,PHID-USER-yyjb72nqrow4ij7mzhhm,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"Note that, in my view, this is not a blocker for enabling the visual editor on Wikivoyages for all users. This is because almost no uses of `<listing>`s are done directly in wikitext, but instead through a template, which could do with some TemplateData love, but is supported fine already.
+
+If you think I'm wrong please shout. :-)",1459668127,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"**lukebenes** wrote:
+
+Have you taken a look at WP:HOTCAT?
+
+http://en.wikipedia.org/wiki/Wikipedia:HC
+
+HotCat is a JavaScript program that helps registered users easily remove, change and add categories to Wikipedia pages. This is very similar to the functionality that we need for the Listing Editor.",1371640823,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"This is about the Listings extension which is unique (in Wikimedia land) to Wikivoyage - https://www.mediawiki.org/wiki/Extension:Listings
+
+It creates the following tags:
+
+<buy>
+<do>
+<drink>
+<eat>
+<listing>
+<see>
+<sleep>
+
+They are used to provide structured mark-up and hinting of recommendations for WV listings of places to go.
+
+Sorry for the confusion. :-)",1364934457,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"We weren't talking about any extension. This report was filed against MediaWiki core. Happy to move it to the right place, as long as we know what is the right place.
+
+Luke, are you saying those tags were created in the Wikitravel times? If so, it would be useful to know how did they handle them.",1364933198,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"Actually, on reflection this should live in the Extension we're talking about, and block against a tracker for such creations in VE itself. Sorry to mess this around.",1364926961,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"Looking at our roadmap, the implementation of this feature looks more like a candidate for a VisualEditor plugin. 
+
+MediaWiki core features must be generic enough for different wikis and must be reviewed and integrated by core maintainers. Visual Editor plugins can be developed by anybody and it is perfecty ok to have them for very specific purposes e.g. a Wikivoyage plugin.",1364925993,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Listings,"**lukebenes** wrote:
+
+There is a discussion about this feature on the wikivoyage site here:
+http://en.wikivoyage.org/wiki/Wikivoyage:Roadmap/Improved_editing_interface",1363529899,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-tqro35vsrplftuemdxbd,task_subcomment,NA
+VisualEditor: Clean up inconsistent documentation of event emissions,"Some events are undocumented (like ve.dm.Surface.prototype.change, which emits multiple events but documents none), most have the event name without quotes, but some have single quotes (ve.dm.Surface.addInsertionAnnotation) or double quotes (ve.ui.Toolbar.prototype.onContextChange). Parameters sometimes are documented and sometimes aren't, there's no clear distinction between ""parameters aren't documented"" and ""there aren't any"", and in no case do we document the types and descriptions of event parameters, we only ever document their names.
+
+We probably also don't document events with @event nearly as often as we should. It's a huge mess.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362706560,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ynwo2pb45ypgaglir47z,task_description,resolved
+VisualEditor: Clean up inconsistent documentation of event emissions,Change-Id: Id879aa769b2c72d86a0322e75dddeb868211ce28,1363763464,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ynwo2pb45ypgaglir47z,task_subcomment,NA
+VisualEditor: Clean up inconsistent documentation of event emissions,Working on it.,1363762434,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ynwo2pb45ypgaglir47z,task_subcomment,NA
+VisualEditor: VE should be able to be 'default' for some namespaces and by user preference elsewise/in others,"Right now VE is either 'default' for some given namespaces, or enabled but only exposed by user preference for some namespaces; it should be possible to have a mixed-installation for testing/etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362704940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jps6ok65jqx3whi4rc2h,task_description,invalid
+VisualEditor: VE should be able to be 'default' for some namespaces and by user preference elsewise/in others,"(In reply to comment #1)
+> If enabled by default, can be disabled by preference?
+
+Currently, yes, though we'll remove this preference when we go from ""opt-in"" to ""opt-out"" in July.
+
+However, this bug isn't really necessary any more as we've just last week switched VE to default-on for Main, User and also the VisualEditor namespaces on mediawikiwiki. Closing as we no longer need this.",1367604375,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jps6ok65jqx3whi4rc2h,task_subcomment,NA
+VisualEditor: VE should be able to be 'default' for some namespaces and by user preference elsewise/in others,"If enabled by default, can be disabled by preference?",1367604125,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-jps6ok65jqx3whi4rc2h,task_subcomment,NA
+VisualEditor: split paragraphs in a listItem should not be considered 'wrapper' paragraphs,"Start a list item and type 'a', now hit shift-enter and type b.
+
+Expected diff:
+*a<p>b</p>
+
+Actual diff:
+*ab
+
+The paragraph created when you create the list has internal.generated = 'wrapper'. This property gets copied when you split the list. Two wrapper paragraphs next to each other apparently get merged into one.
+
+The only way wikitext can have two paragraphs in a list is with HTML so extra paragraphs must be full HTML paragraphs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362418080,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-u7qyhofavuvw7qvhg5w6,task_description,resolved
+VisualEditor: split paragraphs in a listItem should not be considered 'wrapper' paragraphs,Fixed by https://gerrit.wikimedia.org/r/#/c/52046/,1363373310,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-u7qyhofavuvw7qvhg5w6,task_subcomment,NA
+[TUX] Browser support matrix,"Create a list of supported browsers and document it.
+
+Also make sure that TUX actually works with those browsers.
+
+--------------------------
+**Version**: master
+**Severity**: enhancement
+**URL**: http://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix",1362144360,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_description,resolved
+[TUX] Browser support matrix,"We will follow MediaWiki's browser support matrix for Modern (Grade A). With increasing number of linters, and since this area of code is not rather stable, it is much less likely that we introduce issues that would not work on some of the supported browsers.",1607415848,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,"On (c), https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4381 mentions IE, Firefox, Safari and Chrome, but no versions.",1408803169,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,"https://www.mediawiki.org/wiki/Compatibility was recently updated and may serve as starting point; there is no need to restate the obvious, but it's useful to highlight any deviation from common expectations.
+
+As far as I can see, Special:Translate and others have some browser tests, but:
+a) I have no idea how comprehensive they are; it would be useful to file bugs for any missing one which should be added;
+b) I don't know for sure whether they're used or how and where the outcomes are reported, though I think there is some degree of usage as part of the monthly [[mw:MLEB]] release;
+c) I have absolutely no idea about the browsers used for such tests.
+
+Is anyone able to shed some light on these questions, or point to someone who knows?",1408802235,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,Any updates on this?,1382785247,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,"Harsh: 
+Do you plan to work on this any time soon?
+Do you need any input from the QA/browsertesting team (that would mean adding chrismcmahon@ and zfilipin@ to the CC list of this bug report)?",1373281412,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,"We had triaged this bug last month and Harsh Kothari had wanted to work on this. I'm adding him on cc for this bug.
+
+Harsh, would you be working on this any time soon? Thanks.",1370235510,PHID-USER-ttw4tpoosxc4pbmskrla,False,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,Runa: this has been assigned you a month ago. Could you provide a status updated and whether you are currently working on this?,1369473003,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+[TUX] Browser support matrix,This is very much related to getting automated integration testing. Currently the scenarios are at http://etherpad.wikimedia.org/i18n-qa (ULS only so far). We should get at least 20 or so tests for TUX.,1362421102,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-yvmhgidy7jqjbjbp5sta,task_subcomment,NA
+VisualEditor: Implement remaining wrap(each) methods in SurfaceFragment,"unwrapNodes & rewrapNodes are not implemented, and wrapNodes doesn't calculate selections correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361910180,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fsxicsfwrmjxla4crdyz,task_description,resolved
+VisualEditor: Implement remaining wrap(each) methods in SurfaceFragment,Answer: yes. Marking as fixed.,1368042225,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fsxicsfwrmjxla4crdyz,task_subcomment,NA
+VisualEditor: Implement remaining wrap(each) methods in SurfaceFragment,Isn't this now (long) done?,1367028640,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fsxicsfwrmjxla4crdyz,task_subcomment,NA
+"Checkstyle report unable to fetch context, showing ""No description available. Please upgrade to latest checkstyle version.""","e.g. https://integration.mediawiki.org/ci/job/mwext-Scribunto-jslint/233/checkstyleResult/file.984307183/type.1174449419/
+
+It does that almost everywhere (including VisualEditor and MediaWiki core). Sometimes it does work though, weird.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1361834280,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jbdbttk2lguhy7gmvjn2,task_description,declined
+"Checkstyle report unable to fetch context, showing ""No description available. Please upgrade to latest checkstyle version."""," Timo said it had a very confusing output due to :
+- our builds not chaining because of different patchsets being run
+- disabled checks being listed anyway
+
+Checkstyle plugin is no more used. Closing the bug.",1372185531,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jbdbttk2lguhy7gmvjn2,task_subcomment,NA
+"Checkstyle report unable to fetch context, showing ""No description available. Please upgrade to latest checkstyle version.""","Unassigning self, I suspect that is either:
+
+- JSHint does not add a description of the error in its XML output
+- Jenkins Checkstyle plugin is missing description for JSHint errors
+
+Most probably an upstream issue.",1362978350,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jbdbttk2lguhy7gmvjn2,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"MW-specific code should be split from the VisualEditor itself; mediawiki/extensions/VisualEditor.git should only be the MW-specific items (integration; MW-specific plugins; MW-specific plugin overloading).
+
+Target repository for VE itself already exists: VisualEditor/core.git
+
+(Future plugins should be under VisualEditor/plugin/….git.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1361756160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_description,resolved
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,Now complete.,1387564647,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 102842 merged by jenkins-bot:
+Use submodule for VisualEditor core
+
+https://gerrit.wikimedia.org/r/102842",1387563773,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 102842 had a related patch set uploaded by Jforrester:
+Use submodule for VisualEditor core
+
+https://gerrit.wikimedia.org/r/102842",1387507385,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 102825 merged by jenkins-bot:
+Update .gitreview and remove MW-specific things
+
+https://gerrit.wikimedia.org/r/102825",1387492495,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 102825 had a related patch set uploaded by Jforrester:
+Update .gitreview and remove MW-specific things
+
+https://gerrit.wikimedia.org/r/102825",1387491726,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 101845 merged by jenkins-bot:
+Split ext.visualEditor.mwcore out of ext.visualEditor.core
+
+https://gerrit.wikimedia.org/r/101845",1387316087,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,"Change 101845 had a related patch set uploaded by Jforrester:
+Split ext.visualEditor.mwcore out of ext.visualEditor.core
+
+https://gerrit.wikimedia.org/r/101845",1387214862,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself,https://gerrit.wikimedia.org/r/71755 addresses part of this by splitting files between modules/ve/ and modules/ve-mw/,1372875122,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-ys5ubt2jukiwmzznrvjg,task_subcomment,NA
+VisualEditor: Generalize logic in ve.FormatAction,"* Rules for ""heading should not be in list"" in CE rather than DM
+* Function that isolates and unwraps things until they conform to the CE rules
+** FormatAction does these things, but is hardcoded for lists
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361475480,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-q2sq3hniv3ip4n5l2tv4,task_description,resolved
+VisualEditor: Generalize logic in ve.FormatAction,Reassigning to Ed because he's already doing this anyway.,1362528092,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-q2sq3hniv3ip4n5l2tv4,task_subcomment,NA
+VisualEditor: Refactor ve.FormatAction.splitAndUnwrap to use SurfaceFragment,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361474880,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lfnwgg3zbq7kwd5zrvyd,task_description,resolved
+VisualEditor: Refactor ve.FormatAction.splitAndUnwrap to use SurfaceFragment,Merged.,1361839902,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lfnwgg3zbq7kwd5zrvyd,task_subcomment,NA
+VisualEditor: Refactor ve.FormatAction.splitAndUnwrap to use SurfaceFragment,https://gerrit.wikimedia.org/r/#/c/50834/,1361834711,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-lfnwgg3zbq7kwd5zrvyd,task_subcomment,NA
+VisualEditor: Implement remaining wrapAll methods in SurfaceFragment,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361474340,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zcg333mt7cdvw4jrhfyr,task_description,resolved
+VisualEditor: Implement remaining wrapAll methods in SurfaceFragment,Merged.,1361839869,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zcg333mt7cdvw4jrhfyr,task_subcomment,NA
+VisualEditor: Implement remaining wrapAll methods in SurfaceFragment,Finished off in https://gerrit.wikimedia.org/r/#/c/50824/,1361832639,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zcg333mt7cdvw4jrhfyr,task_subcomment,NA
+VisualEditor: Implement remaining wrapAll methods in SurfaceFragment,Partially fixed in https://gerrit.wikimedia.org/r/#/c/50429/,1361572627,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zcg333mt7cdvw4jrhfyr,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"**Author:** `visionary.incident`
+
+**Description:**
+I cannot input japanese consecutive characters in the beginning of the line.
+
+Firefox version is 18.0.2 .
+
+For example
+
+inputed
+あああああ
+
+outputed
+ああ
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361473320,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_description,resolved
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,I suspect this is no longer broken. Please re-test.,1423750103,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"Just as a note, we are refactoring the Surface code in ContentEditable to make this fixable, hence the delay.",1381271546,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,*** Bug 53064 has been marked as a duplicate of this bug. ***,1377348845,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"Inez, is there an update on this bug?",1367547839,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,"Only works if the line has no text.
+Confirmed on bullet-type lines too.",1364125968,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: IME input into an empty slug causes characters to overwrite one another,I was able to confirm it (using Katakana) in Chrome on MacOS. Apparently it depends on the speed of typing (Selenium test for it is going to be interesting).,1361476901,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-wgf3mrrwn3ymravx5tvh,task_subcomment,NA
+VisualEditor: Increase test coverage of ve.FormatAction,"We currently have 0 tests for ve.FormatAction.*
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361404500,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sgmrkdjbdkbtrt6o6mwh,task_description,resolved
+VisualEditor: Increase test coverage of ve.FormatAction,Merged.,1361566138,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sgmrkdjbdkbtrt6o6mwh,task_subcomment,NA
+VisualEditor: Increase test coverage of ve.FormatAction,https://gerrit.wikimedia.org/r/#/c/50137/,1361410249,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sgmrkdjbdkbtrt6o6mwh,task_subcomment,NA
+VisualEditor: Fix dependency issues between ve.js and ve.init.platform,"In ve.js, function ve.msg:
+// TODO: Fix dependency issues between ve.js and ve.init.platform
+
+I don't know how this should be fixed exactly, Timo put this comment in in 407de829dd8f2e51c22a8378dc70c79fc6645d1e . I did notice that running the VE tests from Special:JavaScriptTest doesn't work because ve.msg() errors out with 've.init.platform' undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361311500,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zkyntw7nvnjqikzefrbn,task_description,resolved
+VisualEditor: Fix dependency issues between ve.js and ve.init.platform,Change-Id: I47d7d92495974572194700c98a219d22ecbfaf4b,1364960892,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zkyntw7nvnjqikzefrbn,task_subcomment,NA
+VisualEditor: Fix dependency issues between ve.js and ve.init.platform,"This is currently blocking us from enabling QUnit for extension VisualEditor as the race-condition is happening consistently in Chrome, Safari and PhantomJS.
+
+I tracked it down to the calls to ve.msg from the global scope, such as:
+
+
+@@ ve.ce.Surface.static.$phantomTemplate = $ (.. ) .attr( {
+		'title': ve.msg( 'visualeditor-aliennode-tooltip' ),",1364959167,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zkyntw7nvnjqikzefrbn,task_subcomment,NA
+VisualEditor: Fix dependency issues between ve.js and ve.init.platform,"(In reply to comment #0)
+> In ve.js, function ve.msg:
+> // TODO: Fix dependency issues between ve.js and ve.init.platform
+> 
+> I don't know how this should be fixed exactly, Timo put this comment in in
+> 407de829dd8f2e51c22a8378dc70c79fc6645d1e . I did notice that running the VE
+> tests from Special:JavaScriptTest doesn't work because ve.msg() errors out
+> with
+> 've.init.platform' undefined.
+
+Indeed, that's the reason why. They sometimes fail, and sometimes work.
+
+It appears to be a race-condition and/or absent dependency that should be fixed or lazy-loaded or something else to make sure one has the other.",1361312943,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zkyntw7nvnjqikzefrbn,task_subcomment,NA
+AutoLoader adds $IP to network share path,"**Author:** `kevinrose`
+
+**Description:**
+I am running under IIS with the files stored on network storage.
+I get an error from line 1142 in includes\AutoLoader.php when the $filename being passed is already a network share. Specifically in my case it then adds $IP a second time.
+
+Here are the variables from my situation:
+
+From debugging we know that:
+$IP is set to ""\\server\share\mediawiki""
+
+The offending class being loaded in LocalSettings.php:
+
+require_once(""$IP/extensions/WikiEditor/WikiEditor.php"" );
+
+After line 1142 $filename = ""\\server\share\mediawiki\\server\share\mediawiki\extensions\WikiEditor\WikiEditor.php""
+
+Line 1140 checks if the first character is a / (root), or the second character is a : (windows local drive).
+
+To work around the problem I added a third check, that the second character is a slash (windows network share):
+
+		if ( substr( $filename, 0, 1 ) != '/' && substr( $filename, 1, 1 ) != ':' && substr( $filename, 1, 1 ) != '\\') {
+
+--------------------------
+**Version**: 1.20.x
+**Severity**: normal",1360770540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_description,declined
+AutoLoader adds $IP to network share path,"Since nobody cared too much for the last seven years, we assume nobody cares too terribly much. And even if we fixed it, we couldn't test it.",1586895753,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"Tagging CPT as potentially interested party in Autoloader and third-party usees of it. I'm not sure if the above is still applicable, or whether running MediaWiki on Windows from a network share is supported or not. If not, we should probaby document that. If we do, then the above bug seems easily fixable as described in the last comment.",1586730716,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"**kevinrose** wrote:
+
+I forgot about this bug - upgraded my mediawiki to latest snapshot of 1.22 and the issue came back.
+
+The issue isn't related to a particular extension, but to the use of the AutoLoader.  Above the samples were with WikiEditor. This time I came across it with VisualEditor which uses AutoLoader.
+
+
+In 1.22 latest snapshot 7/16/2013 line 1148-1152 of file includes\AutoLoader.php:
+
+		# Make an absolute path, this improves performance by avoiding some stat calls
+		if ( substr( $filename, 0, 1 ) != '/' && substr( $filename, 1, 1 ) != ':' ) {
+			global $IP;
+			$filename = ""$IP/$filename"";
+		}
+
+
+
+This handles the case where $filename is a linux full path (starting at /) or a windows full path (with the drive letter i.e. c:) but does not handle the case of a network share on windows (\\server\path)
+
+Again fix in first message does address this:
+
+if ( substr( $filename, 0, 1 ) != '/' && substr( $filename, 1, 1 ) !=
+':' && substr( $filename, 0, 2 ) != '\\\\')
+
+Adjusted to look specifically for two forward slashes in case there's some other case where one forward slash is ok?",1373980934,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"**michael** wrote:
+
+I experienced the same issue after upgrading to the latest version of GearHost.com's cloudsites platform, which too changed from local drive storage to a network share. Like the original poster, I found the same behavior. Additionally, though, I found that commenting the require_once(""$IP/extensions/WikiEditor/WikiEditor.php"" ); line would temporarily resolve the issue and allow MediaWiki to load, which suggests some dependency between require_once and the autoloader. I applied a similar change to the autoloader file which allowed to uncomment the require_once line successfully. I am running MediaWiki 1.19.1.",1373591943,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,Please confirm that this is a MediaWiki related problem. Otherwise this issue should be closed.,1362546459,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"I think you're confusing ""require"" with ""autoloading"".
+
+The require_once() call you mention:
+> require_once(""$IP/extensions/WikiEditor/WikiEditor.php"" );
+
+that isn't a class but an extension file. This is your own code and placed in your LocalSettings.php, correct?
+
+AutoLoader isn't involved there.
+
+
+> After line 1142 $filename =
+> ""\\server\share\mediawiki\\server\share\mediawiki\extensions\WikiEditor\WikiEditor.php""
+
+Line 1142/1145 of which file? Assuming AutoLoader.php, why is WikiEditor listed in your autoloader configuration?",1360798922,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+AutoLoader adds $IP to network share path,"**kevinrose** wrote:
+
+Sorry to avoid confusion - the actual error is at line 1145 when the incorrect $filename tries to get required.",1360770629,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-m4d5tcwgzxjphwooyz2c,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"[Very much a longer-term enhancement.]
+
+Parsoid doesn't currently have support for passing on an authenticated user's read right when fetching the wikitext (because the API doesn't support that yet).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1359492240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_description,resolved
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Change 91111 merged by jenkins-bot:
+Support private wikis by forwarding Cookie: headers to Parsoid
+
+https://gerrit.wikimedia.org/r/91111",1383678031,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),Closing again.,1382479475,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Change 91111 had a related patch set uploaded by Jforrester:
+Support private wikis by forwarding Cookie: headers to Parsoid
+
+https://gerrit.wikimedia.org/r/91111",1382404256,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Cookies are now forwarded, and caching is disabled if a cookie is set. Closing this bug as fixed. A content API will have to do its own auth.",1381966182,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Change 85414 merged by jenkins-bot:
+Bug 44483: Forward Cookie header to API
+
+https://gerrit.wikimedia.org/r/85414",1381965890,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"(In reply to comment #4)
+> Random idea:
+> 
+> Could Parsoid be made private (already is, though last I checked it still
+> has a
+> public IP) and use an internal API instead of the public API. Then the
+> responsibility for user rights lays in MediaWiki land, and when the request
+> is
+> in Parsoid we can assume it is authenticated and thus Parsoid can have
+> unrestricted access.
+
+That is what we'll have to do in the longer term once we store HTML. Parsoid might not even be involved in that case, only the content API / storage is. See https://www.mediawiki.org/wiki/User:GWicke/Notes/Storage for the current WIP on that.",1381260438,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Random idea:
+
+Could Parsoid be made private (already is, though last I checked it still has a public IP) and use an internal API instead of the public API. Then the responsibility for user rights lays in MediaWiki land, and when the request is in Parsoid we can assume it is authenticated and thus Parsoid can have unrestricted access.",1380024239,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),"Change 85414 had a related patch set uploaded by GWicke:
+WIP Bug 44483: Forward Cookie header to API
+
+https://gerrit.wikimedia.org/r/85414",1379754726,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),*** Bug 44313 has been marked as a duplicate of this bug. ***,1360207511,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+Parsoid should support passing on an authenticated user's read right (when MW API supports that),Passing on the cookie header from the VisualEditor extension to Parsoid and then from Parsoid back to the API might be enough to enable this. Definitely worth a try.,1359588905,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-yycd32q4sp6a3jbmgdq4,task_subcomment,NA
+VisualEditor: Parsoid (?) issues in deleting text on [[W:User:Edinwiki]],"Deleting multiple lines of selected text
+
+When trying to delete a line of added text, the editor failed. See screenshot.
+
+When reviewing the changes I get an empty ""Latest revision"" and empty ""Your text"". Tried with Chrome and Firefox. When saving, the changes are not committed either.
+
+When trying to delete two lines (see screenshot on the right side), only one line is marked for deletion:
+
+    - Mostly active on [[:bs:Korisnik:Edinwiki|bs-wiki]].
+
+When selecting multiple lines in the same way, it seems that each time only the first line is selected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://en.wikipedia.org/wiki/User:Edinwiki
+
+**Attached**: {F10938}",1359113220,PHID-USER-qaslvze35cdv2crgkxjb,False,PHID-TASK-zjrdtyysctdr2ogcnult,task_description,resolved
+VisualEditor: Parsoid (?) issues in deleting text on [[W:User:Edinwiki]],This is now fixed given the Parsoid update. Sorry for the delay!,1366396774,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zjrdtyysctdr2ogcnult,task_subcomment,NA
+VisualEditor: Parsoid (?) issues in deleting text on [[W:User:Edinwiki]],This appears to be a Parsoid issue - to recheck when Parsoid service is updated in live.,1360207666,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zjrdtyysctdr2ogcnult,task_subcomment,NA
+VisualEditor: Link inspector doesn't function properly when opened in location surrounded by word boundaries,"1. Type 2 spaces
+2. Move the cursor between the two spaces
+3. Press link button or (command|control)+k
+4. Type text for target (if in mw integration you can also choose a suggested target)
+5. Press enter (or click outside the inspector, or press esc)
+6. See that the target text was inserted, but not annotated
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1358470200,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-3otirho2qtinxa5jdm5c,task_description,resolved
+VisualEditor: Link inspector doesn't function properly when opened in location surrounded by word boundaries,Gerrit patch merged.,1360613038,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3otirho2qtinxa5jdm5c,task_subcomment,NA
+VisualEditor: Link inspector doesn't function properly when opened in location surrounded by word boundaries,Patched in: https://gerrit.wikimedia.org/r/#/c/47822/,1360198986,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-3otirho2qtinxa5jdm5c,task_subcomment,NA
+VisualEditor: Cursor jumps when backspacing character after alien node,"Steps to reproduce:
+1. Find a paragraph that has an inline node (alien or entity) in it, but not at the end
+2. Move the cursor to the end of the paragraph
+3. Repeatedly press backspace
+4. When there is only one remaining character after the inline node, pressing backspace will remove that character (correct) and move the cursor to the beginning of the line (bad)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1358461560,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-suuligy6idoz5fgoqmha,task_description,resolved
+VisualEditor: Cursor jumps when backspacing character after alien node,I believe that this is now fixed with the new deletion model.,1371780950,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-suuligy6idoz5fgoqmha,task_subcomment,NA
+"Include git submodules, by default, or optionally","Some extensions, such as Extension:GuidedTour, require git submodules.
+
+It would be a very useful enhancement if ExtensionDistributor included these in the download, by default or optionally.
+
+--------------------------
+**Version**: master
+**Severity**: enhancement
+**URL**: https://www.mediawiki.org/wiki/Extension_talk:ExtensionDistributor#Doesn.27t_do_submodules",1358310660,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_description,resolved
+"Include git submodules, by default, or optionally","New tarball generator has been deployed, which now includes submodules.",1406830829,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","(In reply to Kunal Mehta (Legoktm) from comment #3)
+> I've set up an API endpoint for VisualEditor on labs:
+> http://tools.wmflabs.org/extdist/?version=REL1_23&ext=VisualEditor
+> 
+> I don't see any submodules in GuidedTour?
+
+Correct, we forked Guiders so there's no longer a submodule.",1406255839,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","Once we switch to the new labs tarball generator, this will be fixed.",1405547330,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","Change 146430 abandoned by Legoktm:
+Support having multiple API endpoints
+
+Reason:
+We're going to just point everything to labs instead.
+
+https://gerrit.wikimedia.org/r/146430",1405544052,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","I've set up an API endpoint for VisualEditor on labs: http://tools.wmflabs.org/extdist/?version=REL1_23&ext=VisualEditor
+
+I don't see any submodules in GuidedTour?",1405427591,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","Change 146430 had a related patch set uploaded by Legoktm:
+Support having multiple API endpoints
+
+https://gerrit.wikimedia.org/r/146430",1405427302,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+"Include git submodules, by default, or optionally","Yeah, we need this for VE too.
+
+Github doesn't support submodules, but it's easy to do this on labs (I already wrote a script to do it). Just requires a few changes to the extension...",1405423855,PHID-USER-v7vgzvvcw7v2umf737ri,True,PHID-TASK-34q3bn6uqje2mlmgmqhq,task_subcomment,NA
+VisualEditor: Diff viewer in weird state after Parsoid error,"Steps to reproduce:
+1. Open VE on a page
+2. Make changes
+3. Stop Parsoid
+4. Click ""Review and save""
+5. Get an error dialog about Parsoid being down. Click ""Cancel"".
+
+The box that's supposed to show the diff is left empty, but the ""Something's wrong"" and ""Looks good to me"" buttons are still there. I can dismiss the box with the up arrow to go back to editing, but we should be doing this (or at least *something*) automatically on failure.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1357693020,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5medlyzpqf3k4z7hksir,task_description,invalid
+VisualEditor: Diff viewer in weird state after Parsoid error,"Yeah, we completely switched around the fetching logic here so that this is now INVALID; sorry.",1392756925,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5medlyzpqf3k4z7hksir,task_subcomment,NA
+VisualEditor: Diff viewer in weird state after Parsoid error,"Everything about this seems different now... ""Review and save"" I guess has become ""Save page"", and you only get an error about Parsoid being down when you then click ""Review your changes"". This dialog offers only an ""OK"" button which simply stops the loading of the review dialog. I don't see an empty diff or ""Something's wrong""/""Looks good to me"" buttons.
+
+Is this bug still valid?",1392560898,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-5medlyzpqf3k4z7hksir,task_subcomment,NA
+Create API to expose editnotices,"Editnotices for pages are not currently exposed in the API, but are expected to be used by any interface of a Wikipedia  editor. This implies that the information should be easily retrievable.
+
+It should be noted that the VisualEditor api has it's own private implementation of listing all edit notices that should be presented to users: https://en.wikipedia.org/w/api.php?action=visualeditor&format=json&paction=metadata&page=List_of_emoticons&uselang=en&oldid=846338965
+
+This should probably be moved to core as well as be exposed via restbase or something similar.
+
+--------------------------
+**Version**: 1.21.x
+**Severity**: enhancement",1357492860,PHID-USER-a6jwrurphpx6yl4coupk,False,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_description,resolved
+Create API to expose editnotices,"Change 921405 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] Add 'preloadcontent' and 'editintro' in API prop=info%%%
+https://gerrit.wikimedia.org/r/921405",1684594877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+Create API to expose editnotices,"Change 921405 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/core@master] [WIP] Fix 'preload' and add 'editintro' in API prop=info%%%
+https://gerrit.wikimedia.org/r/921405",1684519036,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+Create API to expose editnotices,"Change 74963 abandoned by Umherirrender:
+Api: Add editnotices to prop=info
+
+https://gerrit.wikimedia.org/r/74963",1378323091,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+Create API to expose editnotices,"Change 74963 had a related patch set uploaded by Umherirrender:
+Api: Add editnotices to prop=info
+
+https://gerrit.wikimedia.org/r/74963",1374408099,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+Create API to expose editnotices,"I wonder whether it would be better for prop=info to return the names of the messages containing the notice instead of parsing them itself. The client could parse these using action=parse if it wants HTML.
+
+The main drawback to parsing them in prop=info is that parsing is expensive; prop=revisions, for example, will error out if asked to parse more than one revision, and if we'd add editnotices with parsed output to prop=info we'd have to do something similar there.
+
+
+On a side note, I still don't understand what happened with r48276. Per-page edit noticed were half removed, but the removal wasn't finished even after this was pointed out, and then they were added back 2.5 years later.",1359054060,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-chtpmgo2h5aq6i6j4niv,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","The Translate extension has very nice info icons which bring users from the interface/feature they're seeing to the relevant (translatable) help page on mediawiki.org (all components are documented). See for instance [[ https://meta.wikimedia.org/wiki/Special:PageTranslation | m:Special:PageTranslation ]].
+
+This is a huge task, but it should be done for core as well.
+
+The problem is of course that there's no real(istic) plan to get such help pages done in the next few decades, as they continue to live either on Meta for copyright reasons or even on local wikis for the same + [[ https://meta.wikimedia.org/wiki/Not_my_wiki | m:Not my wiki]] syndrome. This part of the problem should be discussed on wiki, probably the talk of the project.
+
+--------------------------
+**URL**: https://www.mediawiki.org/wiki/Project:PD_help
+**See Also**:
+{T19557}
+{T14306}
+{T46286}",1357145040,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_description,resolved
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I am afraid the lack of a doc in ##mw:## is the major problem here.
+
+Code fragments are distributed over many PHP units, and not really accessible to Wiki maintainers.",1516972788,PHID-USER-3imz37uve2wfuuub5eq6,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","You can still use MediaWiki:Whatlinkshere-helppage to override the default help link on Special:WhatLinksHere (and similar for all other special pages). You can also use such messages for override/add help links for namespaces (e.g. MediaWiki:Namespace-0-helppage) and page actions (e.g. MediaWiki:History-helppage).
+
+I don't know if this is properly documented anywhere, I just looked up how it works in source code.
+
+The default value is unfortunately not shown on these pages, due to the way we use these messages. Perhaps this could be changed to make these messages behave more normally, but as a consequence, users with non-default interface language would not see the local override (currently they do).
+
+Almost all of the built-in help links go to MediaWiki.org. There are only three exceptions: the help links for history action, Special:Import and Special:RecentChanges all go to MetaWiki. Presumably the documentation pages for these on MediaWiki.org are inferior.",1516912596,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Tried to figure out why some special page has a link to a local help page, and some has help pages at Meta and some at Mediawiki, but the previous -helppage system messages does not make sense anymore? Where is the doc for this?
+
+A local help page for WhatLinksHere has no -helppage link, so tried to move the help page to check if there was some checks on page existence, but no change, the local page is still in use somehow.",1516536097,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Imho it is understandable, when there is a link to a help page for an action or feature that a specific wiki does not offer, or at least not to the general viewer, that they want the help link not shown. Thus we should possibly make help pages very modular and independent of one another and avoid cross-linking them for the things that are based on different user rights that can be assigned individually to users or groups. Also, help links should only appear on pages where the individual feature is available.
+
+I do not know whether that is good and sufficient. At least, it contradicts the idea of offering the user a good and comprehensive Overview.
+
+Last not least, we can have wikis copy the common help pages wholesale or individually as need be, and use their local copies which they can edit to their needs.",1435734085,PHID-USER-pkzunphfdvlecngun3iz,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1411185, @Nikerabbit wrote:
+> It seems a bit blanket statement to say all of those help link are unhelpful. I would argue they are more helpful than harmful and thus there is no need to be able do disable them altogether.
+
+Maybe, maybe not. That's a third party wiki view. I can see it both ways; especially for a wiki that's not open to the public for editing, but is for public viewing. YMMV. Literally just passing on what I was told.",1435610712,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",It seems a bit blanket statement to say all of those help link are unhelpful. I would argue they are more helpful than harmful and thus there is no need to be able do disable them altogether.,1435605086,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I've just had a third-party wiki wondering what the point of this is, and as such, how to disable it
+
+```
+[15:31:40] <AA-Andrew> I can't really see how it's helpful for it to Link to a media wiki help page though 
+```
+
+Of course, hiding it with CSS isn't really disabling it, you're still loading the various assets.
+
+Should there be some sort of config flag for it? I'm not sure...",1435588663,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Ok, we can call this done for now. We should now go look for extension help pages on mediawiki.org and start adding links from their special pages.",1433346304,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","* https://gerrit.wikimedia.org/r/194418 (branch master): #mw1.26, #mw1.26wmf9
+",1433203246,PHID-USER-n4kveqwjjlpsb6ydn73h,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194418 merged by jenkins-bot:
+Add help link for 8 more special pages
+
+[[https://gerrit.wikimedia.org/r/194418]]",1433202431,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 211100 merged by jenkins-bot:
+Allow to customise addHelpLink() target via system message
+
+[[https://gerrit.wikimedia.org/r/211100]]",1431721124,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Once 8082c5f4f0a6c44bca1797470723089bc1d1ff03 is merged, this can be closed. Adding new help pages and links will then be an ongoing process as part of [[Project:PD Help]], as well as an easy matter of customisation by local wikis where needed.",1431687767,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 211100 had a related patch set uploaded (by Nemo bis):
+Allow to customise addHelpLink() target via system message
+
+[[https://gerrit.wikimedia.org/r/211100]]
+",1431686968,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 208378 merged by jenkins-bot:
+Allow to customise addHelpLink() target via system message
+
+[[https://gerrit.wikimedia.org/r/208378]]",1431686573,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 208378 had a related patch set uploaded (by Nemo bis):
+Allow to customise addHelpLink() target via system message
+
+[[https://gerrit.wikimedia.org/r/208378]]
+",1430566779,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1231734, @Multichill wrote:
+> Already disabled on dewp (https://de.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.css&diff=140838650&oldid=140486784). 
+
+And i am inclined to switch this of on commons... It is not helpful. It is not linking to the commons policy's, but to some MW page.
+
+",1430042303,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Just had a look at http://git.wikimedia.org/blob/mediawiki%2Fcore.git/0a33db75cb2afd0879512b7a3cc2ec5b63d9ae5e/includes%2FOutputPage.php#L1408 . Hardcoded url? No message? Are you serious?
+
+Already disabled on dewp (https://de.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.css&diff=140838650&oldid=140486784). 
+
+Including some help is a good idea, but the implementation should be improved so that the url is not hardcoded.",1429810113,PHID-USER-cw4amt4ewxdze5qcjdca,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1139342, @Nemo_bis wrote:
+>>>! In T45591#1139318, @matmarex wrote:
+>> Outstanding patches:
+>> * https://gerrit.wikimedia.org/r/#/c/194418/ ""[WIP] Add link to Meta-Wiki help pages from several special pages""
+> 
+> This is the one which needs most discussion/help.
+
+The pages in question are:
+* https://meta.wikimedia.org/wiki/Help:User_contributions
+* https://meta.wikimedia.org/wiki/Help:Export
+* https://meta.wikimedia.org/wiki/Help:Import
+* https://meta.wikimedia.org/wiki/Help:Linksearch
+* https://meta.wikimedia.org/wiki/Special:MyLanguage/Help:Recent_changes
+* https://meta.wikimedia.org/wiki/Help:Related_changes
+* https://meta.wikimedia.org/wiki/Help:Watching_pages
+* https://meta.wikimedia.org/wiki/Help:What_links_here",1429700039,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",https://commons.wikimedia.org/wiki/Commons:Village_pump#Help_topicons_linking_to_external_help_pages_soon_displayed_everywhere.3F,1429699178,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",Thanks Legoktm! If there is interest in a backport I can work on https://gerrit.wikimedia.org/r/#/c/194418/ this week.,1428562052,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 202968 merged by jenkins-bot:
+Add help link to three rather important pages
+
+[[https://gerrit.wikimedia.org/r/202968]]",1428541016,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 202968 had a related patch set uploaded (by Legoktm):
+Add help link to three rather important pages
+
+[[https://gerrit.wikimedia.org/r/202968]]
+",1428540221,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194414 merged by jenkins-bot:
+Add help link to three rather important pages
+
+[[https://gerrit.wikimedia.org/r/194414]]",1428540082,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1159175, @PerfektesChaos wrote:
+> Local confguration needs more emphasis.
+> * At least a system message should be taken into account by the implementation.
+
+This is valid point which can have it's own task.
+
+> * Icons might be cultural dependant (CJK, arabic, hebrew) and should be configurable per system message – a greek question mark is a semicolon.
+
+This can also be a separate task. We already do localised images in couple of places. I do disagree though that it needs to be configurable per system message.
+
+> Rather than maintaining system messages for each page by each project, a wikifarm with a wikibase could make use of that knowledge. (Okay, WMF might be the only one, but is among the top ten websites)
+
+This can already be achieved with the approach WikimediaMessages is using if we implement overrides with system messages.
+
+> I would like to see in CommonSettings.php something like
+
+Your proposal sounds very complicated, we already have standard way to handle these as explained above.
+
+> I wonder whether the entire helppage link business should stay in core or should be turned into an extension.
+
+It was just moved to core so that each extension does not implement a different way to do it. Definitely not to be moved to an extension.
+",1427541261,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","This is an interesting feature for small WMF wikis and external sites, but would confuse users on wikis with well equipped user guidance (e.g. English or German Wikipedia).
+* Most confusing are two offers, which might happen in German Wikipedia right now.
+* Local pages often provide local policies (deletion!) and specific links to related project pages which cannot be achieved with a world wide non-WMF general explanation.
+* https://www.wikidata.org/wiki/Q395887 shows present local support just for one issue. I count 60 existing local pages. (The 61st would be: mw:Help:Moving_a_page)
+
+Local confguration needs more emphasis.
+* At least a system message should be taken into account by the implementation.
+* Icons might be cultural dependant (CJK, arabic, hebrew) and should be configurable per system message – a greek question mark is a semicolon.
+
+Rather than maintaining system messages for each page by each project, a wikifarm with a wikibase could make use of that knowledge. (Okay, WMF might be the only one, but is among the top ten websites)
+
+I would like to see in CommonSettings.php something like
+  $wgHelpPages = array()
+That may be used explicitly to hard-code page links by any other site.
+
+However, one entry could look like
+  $wgHelpPages['special-movepage']['item'] = 395887;
+
+For performance reasons evaluation of the wikibase item is probably not desirable each time a special page is requested by readers.
+* Every 24h or once a week that array might be populated and refreshed like:
+```
+  lang=php
+  $wgHelpPages['special-movepage']['pages'] = array(
+            'alswiki' => 'Hilfe:Artikel verschieben',
+            'dewiki' => 'Hilfe:Seite verschieben',
+            'enwiki' => 'Wikipedia:Moving a page',
+            ...
+```
+* Time scheduling and triggering the update might be controlled by something like
+```
+  $wgHelpPages['UpdateInterval'] = 24;
+```
+* The same entries might be provided manually by external sites which happen to have their own guidance, but no wikibase and no update service.
+I wonder whether the entire helppage link business should stay in core or should be turned into an extension.
+* A (help/any) page mapping and linking mechanism might be used in many fields, not only with special pages.
+* Various configurations done with system message today might migrate towards wikibase in the future.
+* The MW TemplateData gadget e.g. could be equipped by https://www.wikidata.org/wiki/Q14505594 rather than [[MediaWiki:templatedata-helplink-target]].
+",1427533210,PHID-USER-3imz37uve2wfuuub5eq6,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1139318, @matmarex wrote:
+> Outstanding patches:
+> * https://gerrit.wikimedia.org/r/#/c/194418/ ""[WIP] Add link to Meta-Wiki help pages from several special pages""
+
+This is the one which needs most discussion/help. MediaWiki help pages can't lack coverage of RecentChanges and Watchlist... either they are rewritten on MediaWiki.org or we should change the rules to adopt/incorporate Meta-Wiki docs.",1427048506,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Outstanding patches:
+* https://gerrit.wikimedia.org/r/#/c/194418/ ""[WIP] Add link to Meta-Wiki help pages from several special pages""
+* https://gerrit.wikimedia.org/r/#/c/194414/ ""Add help link to three rather important pages""",1427047744,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1129825, @Spage wrote:
+> FWIW the icon is reachable, https://bits.wikimedia.org/static-1.25wmf21/resources/lib/oojs-ui/themes/mediawiki/images/icons/help.svg, so `url(../../lib/oojs-ui/themes/mediawiki/images/icons/help.svg)` works. I guess there's no cleaner path to library resources.
+
+True, but we were never doing that in the past (I think we even have duplicate copies of some files used in mediawiki/core, in different directories). We never had `url(…)` paths that refer to parent directory, and I think we should keep it this way, easier to figure out what depends on what.
+
+
+>> as the work on making the icons available has stalled a bit.
+> ?  They're all available if you use OOjs UI ([[ https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/#icons-mediawiki-vector-ltr | cool demo ]]). If we're making them available to non-OOjs UI code I look forward to documenting how-to.
+
+Yes. From T92551: ""Map to .mw-icon-<whatever> classes in addition to .oo-ui-icon-<whatever>"".
+
+>>! In T45591#1134815, @Nemo_bis wrote:
+> * Personally I prefer a more ""standard"" (i.e. common) blue, but it doesn't matter.
+> * VE is not ""standard"", both are icons taken from extensions and [[https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/410|made by WMF]].
+
+OOjs UI's icons are supposed to become ""MediaWiki UI"" icons, and thus be pronounced //the// standard ones. There are bumps along the way because the OOjs UI team (subset of WMF Editing) and the MediaWiki UI team (subset of WMF Design) have been disagreeing about which icons should be a part of this set, and how they should be drawn. You can see the current status at https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/#icons-mediawiki-vector-ltr – this has both the old OOjs UI icons (known from VisualEditor) and the new MediaWiki UI icons (known from Flow), and it is quite obvious that these are separate sets. (The 'help' icons comes from the old set, since for some reason it was not considered for including in the new one.) The current status is that Trevor is ~~beating some sens~~working with the designers to iron it out.",1427025201,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 197667 merged by jenkins-bot:
+mediawiki.helplink: Use a SVG PNG icon
+
+[[https://gerrit.wikimedia.org/r/197667]]",1426960241,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","One small question on https://gerrit.wikimedia.org/r/#/c/197667/2
+
+FWIW, aside trivia:
+* There's also a SVG version of the current help.png, but it's not a native one (014b5632fcc6a4200d519cf7f86e94c09639af8f).
+* Personally I prefer a more ""standard"" (i.e. common) blue, but it doesn't matter.
+* VE is not ""standard"", both are icons taken from extensions and [[https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/410|made by WMF]].",1426843326,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","One small question on https://gerrit.wikimedia.org/r/#/c/197667/2
+
+FWIW, aside trivia:
+* There's also a SVG version of the current help.png, but it's not a native one.
+* Personally I prefer a more ""standard"" (i.e. common) blue, but it doesn't matter.
+* VE is not ""standard"", both are icons taken from extensions and [[https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/410|made by WMF]].",1426843280,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1104151, @matmarex wrote:
+> Indeed, it seems that a ""Help"" icon was not considered for the new icon set.
+That's {T90414}
+
+> VisualEditor / OOjs UI has a icon for this, though: {F72837,size=full,layout=inline}. If you need it now, the file will have to be just copied into mediawiki/core,
+
+FWIW the icon is reachable, https://bits.wikimedia.org/static-1.25wmf21/resources/lib/oojs-ui/themes/mediawiki/images/icons/help.svg, so `url(../../lib/oojs-ui/themes/mediawiki/images/icons/help.svg)` works. I guess there's no cleaner path to library resources.
+
+> as the work on making the icons available has stalled a bit.
+?  They're all available if you use OOjs UI ([[ https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/#icons-mediawiki-vector-ltr | cool demo ]]). If we're making them available to non-OOjs UI code I look forward to documenting how-to.",1426705079,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 197667 had a related patch set uploaded (by Bartosz Dziewoński):
+mediawiki.helplink: Use standard SVG PNG icon
+
+[[https://gerrit.wikimedia.org/r/197667]]
+",1426699777,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194411 merged by jenkins-bot:
+Add help link to three other ""minor"" special pages
+
+[[https://gerrit.wikimedia.org/r/194411]]",1426689800,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1103929, @matmarex wrote:
+>>>! In T45591#1102455, @Krinkle wrote:
+>> I imagine if this is not changed it will need to be reverted and further worked upon for the next deployment window.
+> 
+> That strikes me as somewhat of an overreaction.
+
+It needs improvement before deployment. It wasn't my feature to implement and would not have been merged as-is in that case. As such, a revert is just returning status quo and enforcing quality criteria.",1425998891,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Indeed, it seems that a ""Help"" icon was not considered for the new icon set.
+
+VisualEditor / OOjs UI has a icon for this, though: {F72837,size=full,layout=inline}
+
+https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/themes/mediawiki/images/icons/help.svg
+https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/themes/mediawiki/images/icons/help.png
+
+Presumably that could be used. If you need it now, the file will have to be just copied into mediawiki/core, as the work on making the icons available has stalled a bit. (It is MIT-licensed, like the rest of OOjs UI.)",1425991017,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Are you talking about the blue ""?"" for 'help'?
+
+For what is worth, WikiFont has an icon from @violetto called [[ https://commons.wikimedia.org/wiki/File:Sun_help.svg | Sun help ]]. I couldn't find any incon with ""?"" in the collection.
+
+Needless to say, in Commons there are many SVGs of question mark signs in a blue circle, but... See https://commons.wikimedia.org/wiki/File:Blue_question_mark_icon.svg & friends.",1425990691,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I agree the icon needs to be improved. Do you have suggestions for a SVG-ready icon to use?
+
+That's the icon closest to a ""standard"" that we currently have in the codebase for this purpose: it's used in a MediaWiki extension already, for several special pages. We must improve it before we extend its usage to more visible places, of course.",1425988211,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1102455, @Krinkle wrote:
+> I imagine if this is not changed it will need to be reverted and further worked upon for the next deployment window.
+
+That strikes me as somewhat of an overreaction. If the icon irks you, then it's a one-line change to remove it. It would be almost as easy to replace it with a different one, too.",1425983414,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",">>! In T45591#1088866, @gerritbot wrote:
+> Change 157497 merged by jenkins-bot:
+> Add top help link to MediaWiki.org in several pages via indicator
+> 
+> [[https://gerrit.wikimedia.org/r/157497]]
+
+This uses a non-standard icon that doesn't match the any skin and did not go through Design. It also does not have an SVG or High-resolution version available. Thus regressing from our state of having HiDPI-friendly pages by default.
+
+The icon would be okay for a local gadget, but not MediaWiki core.
+
+I don't know further context, but I imagine if this is not changed it will need to be reverted and further worked upon for the next deployment window.",1425947370,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 195045 merged by jenkins-bot:
+Don't require JavaScript for addHelpLink styles
+
+[[https://gerrit.wikimedia.org/r/195045]]",1425752905,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 195045 had a related patch set uploaded (by Nemo bis):
+Don't require JavaScript for addHelpLink styles
+
+[[https://gerrit.wikimedia.org/r/195045]]
+",1425749895,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Switching order needs to be checked for each call in core.
+
+Hiding with css would work, but not tested yet.",1425673270,PHID-USER-qaoxfiqu6bxhd5ehlwhc,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Or we can switch the order. Did you try CSS, though?",1425670025,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","on de.wikipedia.beta.wmflabs.org we have changed the id, but it does not override it, see http://de.wikipedia.beta.wmflabs.org/wiki/Spezial:Verschieben/MediaWiki:Movepage-summary for the place where the wrong help link is shown and http://de.wikipedia.beta.wmflabs.org/wiki/MediaWiki:Movepage-summary for the message where the indicator is used.
+
+This seems to be happen because OutputPage::setHelpLink is called later than SpecialPage::outputHeader and than override the indicator (""In case of duplicate keys, existing values are overwritten.""). OutputPage::setIndicators needs a explicit not-overwrite-option which than can be used from OutputPage::addHelpLink.",1425668089,PHID-USER-qaoxfiqu6bxhd5ehlwhc,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","> What about wikis already have such a help link in the UI like dewiki (see https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/MediaWiki:Specialpage-helplink&limit=500&hidelinks=1 for all usages)
+
+They should switch to the usage of indicators, using the same ID. This *should* suppress the default link.
+
+> What about the local help pages like linked from https://www.wikidata.org/wiki/Q395887?
+> Why hard linking to mw.org? There should be a way to allow the local community to override the target of the help page.
+
+Local help pages are available on very few languages, but sure, customisation should be possible for wikis which care about it. Are the provided CSS class+id and the indicator system insufficient for customisation?",1425667651,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","> What about wikis already have such a help link in the UI like dewiki (see https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/MediaWiki:Specialpage-helplink&limit=500&hidelinks=1 for all usages)
+
+They should switch to the usage of indicators, using the same ID. This *should* suppress the default link.
+
+> What about the local help pages like linked from https://www.wikidata.org/wiki/Q395887?
+> Why hard linking to mw.org? There should be a way to allow the local community to override the target of the help page.
+
+Local help pages are available on very few languages, but sure, customisation should be possible for wikis which care about it. Are the provided CSS classes and the indicator system insufficient for customisation?",1425667627,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","> What about wikis already have such a help link in the UI like dewiki (see https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/MediaWiki:Specialpage-helplink&limit=500&hidelinks=1 for all usages)
+
+They should switch to the usage of indicators, using the same ID. This *should* suppress the default link.
+
+> What about the local help pages like linked from https://www.wikidata.org/wiki/Q395887?
+> Why hard linking to mw.org? There should be a way to allow the local community to override the target of the help page.
+
+Local help pages are available on very few languages, but sure, customisation should be possible for wikis which cared about it. Are the provided CSS classes and the indicator system insufficient for customisation?",1425667449,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I told you there were many. ;-) Even more ambitious, various actions or special cases thereof:
+* https://meta.wikimedia.org/wiki/Help:Diff
+* https://meta.wikimedia.org/wiki/Help:Edit_conflict
+* https://meta.wikimedia.org/wiki/Help:Image_page
+* https://meta.wikimedia.org/wiki/Help:Preview
+* https://meta.wikimedia.org/wiki/Help:Redirect
+* https://meta.wikimedia.org/wiki/Help:View_source
+
+Not sure how to split this conversation/epic. As long as it's just me talking with myself, one report and 3-4 patches probably suffice. ;-) But fixing or rewriting 15 help pages on something like half of a wiki's daily operation is unlikely to be one man's work, while being something we must to at some point.",1425514666,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194418 had a related patch set uploaded (by Nemo bis):
+Add link to Meta-Wiki help pages from several special pages
+
+[[https://gerrit.wikimedia.org/r/194418]]
+",1425513524,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194414 had a related patch set uploaded (by Nemo bis):
+Add help link to three rather important pages
+
+[[https://gerrit.wikimedia.org/r/194414]]
+",1425511854,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 194411 had a related patch set uploaded (by Nemo bis):
+Add help link to three other ""minor"" special pages
+
+[[https://gerrit.wikimedia.org/r/194411]]
+",1425510977,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I'm very happy. :) As for closure let's see: I'm considering many more possible targets for core, I'll send more patches.",1425501388,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Fixed by Nemo for a number of core special pages, which will now have a ""Help"" link in the page indicator area (https://www.mediawiki.org/wiki/Help:Page_status_indicators). The newly added `OutputPage::addHelpLink()` method can be used by extensions to provide identical functionality for their own special pages.",1425486074,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157497 merged by jenkins-bot:
+Add top help link to MediaWiki.org in several pages via indicator
+
+[[https://gerrit.wikimedia.org/r/157497]]",1425485755,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157497 had a related patch set uploaded (by Nemo bis):
+Add top help link to MediaWiki.org in several pages via indicator
+
+[[https://gerrit.wikimedia.org/r/157497]]
+
+#patch-for-review",1424441232,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157496 abandoned by Nemo bis:
+Function to add a top (right) icon link to help page
+
+Reason:
+Superseded by indicators
+
+[[https://gerrit.wikimedia.org/r/157496]]",1417711881,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","(In reply to Bartosz Dziewoński from comment #10)
+> I did that as a note-to-self to implement this later. But okay.
+
+That's appreciated, and it would be useful if bug 23796 had preserved its original bug summary (with its current summary split to some other bug), but as is it was very confusing.",1411574653,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.",I did that as a note-to-self to implement this later. But okay.,1411574311,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","(In reply to Bartosz Dziewoński from comment #8)
+> The implementation proposed by Nemo looks like it would benefit from having
+> bug 23796 solved first, so I'm marking this as such.
+
+With its current summary I see no relation whatsoever.",1411573973,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","The implementation proposed by Nemo looks like it would benefit from having bug 23796 solved first, so I'm marking this as such.",1411573690,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157497 had a related patch set uploaded by Nemo bis:
+Add top help link to MediaWiki.org in several pages
+
+https://gerrit.wikimedia.org/r/157497",1409482959,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Change 157496 had a related patch set uploaded by Nemo bis:
+Function to add a top (right) icon link to help page
+
+https://gerrit.wikimedia.org/r/157496",1409482951,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","[[mw:Category:Help]] was made almost completely translatable (and usually revamped a bit in the process).
+
+I count the following places which have a documentation page and don't link it: Special:Block, Special:MergeHistory, Special:MovePage, Special:NewPages, Special:NewImages, Special:Preferences, Special:Search, action=protect, Special:RecentChanges, action=delete, Special:AllMessages, Special:Undelete, Special:Watchlist; and in extensions, Special:MassMessage, Special:TemplateSandbox, Special:AbuseFilter.
+
+Where to start?",1409433404,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","(In reply to comment #3)
+> Speaking of implementation method, the interwiki prefix mediawikiwiki can be
+> used when necessary: ""new"" wikis have it by default, where ""new"" means after 
+> 2007-03-29 (bug 9440 / r20825 / 98333f458046102ee140f4be86fe4d2c6facae2f ).
+
+To clarify the ""when necessary"": personally, for now I'm following the path of last resistance, i.e. I use wikilink where there is already a wikilink and external where there is already an external link.
+The separate bug 54835 addresses/proposes the standardisation.",1380650218,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","Speaking of implementation method, the interwiki prefix mediawikiwiki can be used when necessary: ""new"" wikis have it by default, where ""new"" means after  2007-03-29 (bug 9440 / r20825 / 98333f458046102ee140f4be86fe4d2c6facae2f ).",1378569913,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","(In reply to comment #1)
+> I for one would prefer an ""if the local page does not exist, then
+> transparently
+> deliver the central page from www.mediawiki.org"" approach for help pages
+
+Sure, that's a possibility too. It's a choice of implementation method, let's leave it to code review. :)
+(Target pages would probably be customisable in system messages anyway, so the result would be the same: wikis could have their own pages if they really wanted.)",1366030055,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.","I for one would prefer an ""if the local page does not exist, then transparently deliver the central page from www.mediawiki.org"" approach for help pages, mainly resembling the way, pictures are handled and included from Commons if needed.
+
+Also, when user on a wiki are about to create a new help page following a red link to the help: namespace, they should most preferrably be stirred towards the central www.mediawiki.org help page creation in their language.",1366029168,PHID-USER-pkzunphfdvlecngun3iz,False,PHID-TASK-tgulnwlt3ym3t3u4alzn,task_subcomment,NA
+"Parser misinterprets en.wikipedia Infobox (inline ""style"" attribute ends up in text nodes)","Screenshot of bug and edit screens
+
+Native parser rendering:
+the Netherlands
+
+Parsoid/VisualEditor rendering:
+style=""font-size: larger; font-weight: bold"" | the Netherlands
+
+[[Flag of the Kingdom of the Netherlands]]:
+{{Infobox flag
+| Name = the Netherlands
+...
+
+[[Template:Infobox flag]]:
+> {| class=""infobox"" style=""width: 22em; font-size:88%; text-align:left; line-height: 1.5em""
+|+ style=""font-size: larger; font-weight: bold"" | <br>{{{Name|{{PAGENAME}}}}}
+|-
+...
+
+
+See attachment for rendering.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F10351}",1357121460,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-iwk4mxubemdjw56l5wqu,task_description,resolved
+"Parser misinterprets en.wikipedia Infobox (inline ""style"" attribute ends up in text nodes)",Fixed by https://gerrit.wikimedia.org/r/#/c/44170/.,1358293142,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-iwk4mxubemdjw56l5wqu,task_subcomment,NA
+VisualEditor: Mouse leaving a phantom and also the .ve-surface DIV area causes phantom to remain,"Hovering over an uneditable element in VisualEditor makes the element be covered by green stripes until the mouse is moved away, but when the cursor moves directly to the sidebar or the right margin, the stripes stay there until some part of the .ve-surface is hovered over.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1356609300,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-ojc6pzmsefmlfjvvupqg,task_description,resolved
+VisualEditor: Mouse leaving a phantom and also the .ve-surface DIV area causes phantom to remain,"**orbit** wrote:
+
+Fixed here: https://gerrit.wikimedia.org/r/#/c/50309/",1361487636,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ojc6pzmsefmlfjvvupqg,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"From user report (but I've had this myself):
+
+| HotCat is a popular gadget and any conflict with it should be avoided. For
+| example, use VisualEditor on [[User:This, that and the other/sandbox/Schfoof]]
+| with HotCat enabled. The HotCat bar appears in the wrong place. (It probably
+| shouldn't appear at all.)
+|
+| …
+|
+| The conflict now appears to be fixed... very strange.
+
+Given that it appears and also doesn't appear between refreshes - i.e., on the same page with the same version of the VE and HC code bases in the same accounts in the same browsers - I'm assuming it's some sort of race-condition, but I'm not sure.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1356129540,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pxuflqdxigvalopfqw3z,task_description,declined
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"I can't reproduce this issue... If anyone still sees this, please reopen.",1414009552,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"Created attachment 14685
+HotCat showing up in the content editable surface
+
+(from bug 55759 attachment 13500 by Chris McMahon)
+
+**Attached**: {F9984}",1393411345,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"(In reply to comment #4)
+> Created attachment 13512 [details]
+> VE iframe has gadget code before VE is invoked
+I don't think that's related at all. Gadget CSS is expected in the iframe. It should be in the <head> instead of the <body> but that's a separate issue (bug 56630).
+
+//attachment invisible_iframe_contents.png ignored as obsolete//",1383697299,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"Created attachment 13512
+VE iframe has gadget code before VE is invoked
+
+//attachment invisible_iframe_contents.png ignored as obsolete//",1381945871,PHID-USER-kqibbfgfpgocyzwe32lv,True,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,*** Bug 55759 has been marked as a duplicate of this bug. ***,1381877657,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"(In reply to comment #1)
+> Is this related?
+> 
+> ""We seem to have lost the plus and minus options of Hotcat that were one of
+> the closest to WYSIWYG features of this site. Please can they be
+> incorporated into visual editor. ϢereSpielChequers 13:46, 4 July 2013 (UTC)""
+
+That's unrelated to VisualEditor; enwiki's community switched off HotCat as a default gadget, so people who want to keep using it will need to manually switch it back on.",1372947996,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface,"Is this related?
+
+""We seem to have lost the plus and minus options of Hotcat that were one of the closest to WYSIWYG features of this site. Please can they be incorporated into visual editor. ϢereSpielChequers 13:46, 4 July 2013 (UTC)""",1372946751,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-pxuflqdxigvalopfqw3z,task_subcomment,NA
+VisualEditor: Add a (small) left margin to the CE so that users can select whole lines at once,"From a user suggestion:
+
+| Normally word processors and text editors have a left margin, allowing
+| whole lines to be selected. There would normally be a small gap of a few
+| pixels between the left column of text and the left margin, allowing a
+| ""margin of error"" for regular text selection. To the left of this gap,
+| any clicks select entire lines, and any drags up or down select many
+| lines at once. 
+|
+| I don't know if there is a need for the complete left margin
+| functionality in VisualEditor, but certainly, the editing area shouldn't
+| stop at the exact edge of the letters. Perhaps the padding on the VE
+| container needs to be increased with a compensating decrease in the
+| margin - or maybe that's totally wrong, but you get the idea.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1356128220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3d7wihxirj5lu7swsg43,task_description,declined
+VisualEditor: Add a (small) left margin to the CE so that users can select whole lines at once,"After discussion with the team, we feel that this doesn't make sense because this is mostly a feature that makes sense in line-based editors (generally, for code), and VE is not one of these.",1369426246,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3d7wihxirj5lu7swsg43,task_subcomment,NA
+VisualEditor: Add a (small) left margin to the CE so that users can select whole lines at once,"For the first part, some IDEs do this (e.g. Sublime), but LO, Google Docs & gedit don't. The downside is it reduces the target zone for placing the cursor at the start of a line.
+
+For the second part, we already have left padding into which you can click to position the cursor at the start of the line.",1369228231,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-3d7wihxirj5lu7swsg43,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,"In https://en.wikipedia.org/w/index.php?title=Lynn_Hill&oldid=528045441 (and other versions), go into VE, go to the bottom, delete the list item (and so the list) from the External links section.
+
+ve.instances[0].documentModel.data confirms that the model has this removed - ""/heading"" object followed by the alienated table from the ""{{Authority control}}"" template - but on diff Parsoid thinks that there is no change in this area. Is this is a Parsoid, or is change marking broken (or both)?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355510820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_description,resolved
+VisualEditor: Deleting content between a heading and an alien fails?,"A few more selser fixes later this should now be fixed. Repeating the test case above certainly suggests it works, so please reopen if there still are issues.",1359143154,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,(Needs verification with VE),1357343579,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,"Likely fixed by the DOM diffing functionality that landed in https://gerrit.wikimedia.org/r/#/c/41816/. Barring bugs, we now no longer depend on change markers for selective serialization to work.",1357343521,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,"I believe this ties in directly to what Gabriel is doing, so I'll add him and we can have a big bugzilla CCing party.",1355950575,PHID-USER-nvavrb7ko66hv3xap6sb,True,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+VisualEditor: Deleting content between a heading and an alien fails?,"This is probably a selser (Parsoid) issue. There is no change marking for removals, selser detects these based on DSR discontinuities.
+
+Provisionally CCing Mark, once I get time to investigate this properly and figure out what's going on, I'll move/reassign this bug as appropriate.",1355950118,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-7aedtfvbjcpnujzhsbiy,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit imagemaps,"<imagemap>....</imagemap> is unparsed but shown as plain wikitext:
+https://en.wikipedia.org/wiki/User:Raymond/imagemap
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/imagemap",1355487780,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-7akqsunetgzvscos7y7g,task_description,open
+Create a VisualEditor plugin tool to add/edit imagemaps,"> <imagemap>....</imagemap> is unparsed but shown as plain wikitext
+
+Apparently at this point it is shown as an uneditable image.
+
+An imagemap editor seems almost the same use case as an [[ https://commons.wikimedia.org/wiki/Help:Gadget-ImageAnnotator | ImageAnnotator ]] annotation editor.",1422606911,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-7akqsunetgzvscos7y7g,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"Support <syntaxhighlight> tag too. It is a synonym to <source> which works already
+
+https://en.wikipedia.org/wiki/User:Raymond/source
+
+See https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/SyntaxHighlight_GeSHi.git;a=blob;f=SyntaxHighlight_GeSHi.php#l67 for the definiton of the parser hooks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/source",1355486220,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-q2kd7nc4teibu2d6yujb,task_description,resolved
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"Change 214078 merged by jenkins-bot:
+Add VisualEditor support
+
+[[https://gerrit.wikimedia.org/r/214078]]",1435183387,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"Change 214078 had a related patch set uploaded (by Jforrester):
+Add VE support for syntax highlighting
+
+[[https://gerrit.wikimedia.org/r/214078]]
+",1432909766,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"Change 114529 had a related patch set uploaded by Jforrester:
+[WIP] Add VisualEditor support
+
+https://gerrit.wikimedia.org/r/114529",1404758239,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,Re-opening as this is now unmerged.,1404758207,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks,"This is now complete and merged, as gerrit 68615, and will go out (as an experimental option) to MediaWiki.org tomorrow. Congratulations, Tongbo!",1380739351,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q2kd7nc4teibu2d6yujb,task_subcomment,NA
+Parsoid: Second column heading missing of table with template-generated header,"Screenshot showing the regular view, visualeditor view and wikitext
+
+Steps to reproduce problem:
+* Open VisualEditor on https://en.wikipedia.org/wiki/Buri_Ram_Airport
+
+Expected result:
+Table has header on both columns.
+
+Actual result:
+Header of second column is missing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9595}",1355443620,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-woqw5jwyjb5eshocsjdw,task_description,resolved
+Parsoid: Second column heading missing of table with template-generated header,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372933991,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-woqw5jwyjb5eshocsjdw,task_subcomment,NA
+Parsoid: Second column heading missing of table with template-generated header,Patch committed for review in https://gerrit.wikimedia.org/r/46465.,1359416789,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-woqw5jwyjb5eshocsjdw,task_subcomment,NA
+Parsoid: Second column heading missing of table with template-generated header,"Appears to be a failed template expansion, so probably a Parsoid bug - Gabriel, thoughts?",1357598990,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-woqw5jwyjb5eshocsjdw,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,"Try editing the page [[:en:Buri_Ram_Airport]] with VisualEditor. Mouse over the infobox. There's an element that sticks above the alien marking, because it has a z-index attribute.
+
+I don't know how best to fix this, I assume it would be bad to simply set z-index=1000 and be on your way, but it's an inconsistent appearance and something to be fixed eventually.
+
+I suspect this may also be a good beginner bug, so if someone from the VE team can mark this as easy, then we can leave it for a newcomer.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.org/wiki/Buri_Ram_Airport",1355441880,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_description,resolved
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,Change-Id: I889074a659483ce3d48380be5f50f80abb573286,1355696389,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,"You guys have no concept of leaving a simple bug for new contributors? :)
+
+Not to worry, I'll go find more. Thanks Rob!",1355515857,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,Patch in https://gerrit.wikimedia.org/r/38669,1355446597,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,"The following CSS rule exists:
+
+> .ve-ce-alienBlockNode, .ve-ce-alienInlineNode,
+> .ve-ce-alienBlockNode *, .ve-ce-alienInlineNode * {
+>   position: relative !important;
+>   top: 0 !important;
+>   left: 0 !important;
+>   bottom: 0 !important;
+>   right: 0 !important;
+> }
+
+They have position relative, so the z-index within is relative and constraint within the alien.
+
+However that isn't the case. This is because the top node (alienBlockNode, not alienBlockNode *) needs z-index: 0; to complete this feature. It is the combination of z-index: 0; and position: relative; that makes it work.
+
+It was presumably forgotten because it needs to be on a separate rule (not inside the one above, since that would set z-index: 0; on all blocks, thus destroying the order of elements within the alien).",1355442376,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern,"Sorry, setting web browser in case it matters.",1355441973,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-e2rzlzqqfl2v7m5ms4g6,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Math is editable, but only as plain LaTeX like in the wikitext editor: https://en.wikipedia.org/wiki/User:Raymond/Math
+
+{F199473}
+Figure 1: Current non visual visual editor",1355386860,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_description,open
+Create a visual VisualEditor plugin tool to add/edit maths blocks,">>! In T45058#6101704, @BoldLuis wrote:
+> I suggest a way to implement Mediawiki links in Phabricator.  ~~~~
+
+**[offtopic]** @BoldLuis: Please use the Preview at the bottom, below the comment field, before submitting a comment. See T251657. Thanks :)
+
+Please also avoid unnecessary full quotes of previous comments when not needed.",1588406096,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,">>! In T45058#6101704, @BoldLuis wrote:
+> I suggest a way to implement Mediawiki links in Phabricator.  ~~~~
+
+**[offtopic]** @BoldLuis: Please use the Preview at the bottom, below the comment field, before submitting a comment. See T251657. Thanks :)",1588406072,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Good!!!. 
+
+>>! In T45058#475499, @SalixAlba wrote:
+> Created attachment 13550
+> Screenshot of editing a math block
+> 
+> Some small tweaks are needed to the dialog box. Editing the last equation at https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+> there are a a few problems
+> 
+> 1) The dialog obscures the actual equation
+> 2) The dlalog is too small to see the whole source text of the equation
+> 
+> This could be solved the making the dialog, moveable and resizeable.
+> 
+> **Attached**: {F10189}
+
+",1588386108,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,">>! In T45058#475389, @Jdforrester-WMF wrote:
+> (In reply to comment #3)
+>> Are there any news on this?
+> 
+> Jiabao was accepted as a GSoC student and will be working on this with us. Updates are going to be added at [[mw:User:Jiabao wu/GSoC 2013 Project Work]].
+
+I suggest a way to implement Mediawiki links in Phabricator.  ~~~~",1588382922,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor.]
+
+
+  - I suggest Math Editor, a full visual math editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition. See:** 
+https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/ . Just some ideas ;-)",1588368331,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor.]
+
+
+  - I suggest Math Editor, a full visual math editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition. See:** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588368277,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor.]
+
+
+  - I suggest Math Editor, a full visual math editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588368213,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+
+  - I suggest Math Editor, a full visual math editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588368120,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http://en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+
+  - I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588368041,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http//en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+
+  - I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367857,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula_Help:Displaying a formula Wikipedia Help:Displaying a formula]
+
+[http//en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+
+  - I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a visual calculator (keyboard). If you put / in the visual box in your keyboard, it would put the wikitext: \frac . 
+
+
+  - It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367830,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying_a_formula_Help:Displaying a formula Wikipedia Help:Displaying a formula]
+[http//en.wikipedia.org/wiki/File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a calculator. If you put / in the visual box in your keyboard, it would put the wikitext: \frac . It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367699,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying a formula Help:Displaying a formula]
+[http//en.wikipedia.org/wiki File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a calculator. If you put / in the visual box in your keyboard, it would put the wikitext: \frac . It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or **math handwriting recognition** [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367619,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"[http://en.wikipedia.org/wiki/Help:Displaying a formula Help:Displaying a formula]
+[http//en.wikipedia.org/wiki File:Editing_a_formula_using_VisualEditor.png This screenshot shows the formula ''E'' = ''mc2'' being edited using VisualEditor. The visual editor shows a button that allows to choose one of three offered modes to display a formula.]
+
+I suggest a Math Editor, a full visual editor for VisualEditor. This would work in a similar way to a calculator. If you put / in the visual box in your keyboard, it would put the wikitext: \frac . It also can link to a visual list with commons functions (as square root), mathematical input graphical environment or math handwriting recognition [https://www.texthelp.com/en-us/products/equatio/equatio-for-windows/=]. Just some ideas ;-)",1588367587,PHID-USER-7j4dq3ggca7kka2g3siq,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,I added a screenshot so that the task becomes easier to understand,1437349341,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"I was already wondering... yes when you wonder...there might be a good reason for that;-)
+Thanks for the clarification. So you mean something like
+http://saskatoon.cs.rit.edu/min_instructions/",1437349029,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"No. By ""plain wikitext"" the filer means ""in LaTeX rather than visually"", hence the title of this task.",1437348608,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"I tested
+
+```
+Math is unparsed but shown as plain wikitext: https://en.wikipedia.org/wiki/User:Raymond/Math
+```
+and i could edit without issues. I could see a renderd formula when visiting this page
+https://en.wikipedia.org/wiki/User:Raymond/Math?veaction=edit
+Ok it had the png rendering and not the MathML rendering, but I think this is a seperate bug.",1437347647,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,">>! In T45058#932936, @matmarex wrote:
+> This has been fixed a looong time ago, or needs a better summary to explain what's missing.
+
+Happy?",1418933302,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"This has been fixed a looong time ago, or needs a better summary to explain what's missing.",1418920884,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"**physik** wrote:
+
+I'm happy to see the interest in the Math extension.
+It would be really great to get some code reviews. There are a lot of unmerged improvements that are already implemented that wait for a code review.
+https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/Math,n,z
+The fromula editor for math is one example. The code for Math 2.0 that was finished in beginning of October 2013 is still waiting for review and not moving forward at all. That's really a very sad situation. (Sorry for the spamming)",1393519044,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to PiRSquared17 from comment #28)
+> I'm not sure we need to reinvent the wheel.  Aren't there already libre JS
+> formula editors that can export to LaTeX?  I just found one from Google:
+> http://mathdox.org/formulaeditor/
+
+Who is talking about re-inventing the wheel?",1393518234,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,I'm not sure we need to reinvent the wheel.  Aren't there already libre JS formula editors that can export to LaTeX?  I just found one from Google: http://mathdox.org/formulaeditor/,1393518034,PHID-USER-omdcggvudfkuawipp23i,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to Richard Morris from comment #26)
+> I hope the LaTeX editor is not going to be short term. This is the preferred
+> input method for the mathematical community. By all means develop a GUI but
+> please make sure you can still use a LaTeX input method.
+
++1",1393517762,PHID-USER-omdcggvudfkuawipp23i,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,I hope the LaTeX editor is not going to be short term. This is the preferred input method for the mathematical community. By all means develop a GUI but please make sure you can still use a LaTeX input method.,1392761006,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,*** Bug 61498 has been marked as a duplicate of this bug. ***,1392741898,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to Andre Klapper from comment #21)
+> It's a bit unclear to me which further steps are required to get this ticket
+> closed (probably creating dependency tickets for the items in comment 19?).
+
+No, the issues in comment 19 only refer to the short-term LaTeX editor. This bug is asking for a fully-featured visual interactive editor for formulae – will merge bug 61498 back into this.",1392741889,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Bug 57437 is to ""Allow the VE dialog for math elements to be movable and resizable"", which is already a blocker for this ticket. This assigned to a google code-in student, Theopolisme, who I suspect is no longer working on that bug.
+
+I've create bug 61497 to cover up the jumbled up formula in comment 16.
+
+I think Jiabao original plan was to create a GUI I've added a bug for this as bug 61498.
+
+Dialog overlapping the equation might be resolved by bug 57437 or it could possibly resolved by changing the way it is initially displayed.",1392740544,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"**physik** wrote:
+
+From what I see
+https://gerrit.wikimedia.org/r/#/c/105647/ and
+https://gerrit.wikimedia.org/r/#/c/105648/
+need to be resolved before we can make progress on that.",1392739625,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Seems that Jiabao is not currently working on this ticket, hence resetting ASSIGNED status. 
+It's a bit unclear to me which further steps are required to get this ticket closed (probably creating dependency tickets for the items in comment 19?).",1392729667,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,OK I've created bug 57437 for the tweaks to the dialog and assigned it to Theopolisme. Hope that OK.,1385146178,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"There are different problems reported here, and we should have separate reports for each. Then we will tie each bug report to a Google Code-in task:
+
+* The dialog overlaps the equation: the solution might be a combination of setting a default position with less chances of overlapping and/or allowing the dialog to be moved to a different position?
+
+* The dialog is sometimes too small: the solution might be to make the dialog resizable?
+
+* #Comment 16 deserves an own bug report but, haven't tested this plugin myself, I can't describe the problem or propose solutions.
+
+Richard, would you like to create these reports?
+
+I'm going to pull http://www.google-melange.com/gci/task/view/google/gci2013/5861921152565248 in order to create 2 GCI tasks or more. Theopolisme, you can try to work on these issues now, or you can wait until the plan is more defined (and Jiabao is back, or we have found a co-mentor able to help you).",1385134282,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Just a bit of background: Theopolisme is a Google Code-in student working on a task related to #comment 15 that was created by Jiabao:
+
+http://www.google-melange.com/gci/task/view/google/gci2013/5861921152565248
+
+Jiabao has been silent in the past days. Your help is welcome while she comes back. Thank you!",1385084439,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"@Richard/others: Thinking about making the dialog draggable and resizable...
+
+The solution I initially think of is installing jquery.ui and then adding some parameters to OO.ui.Window that allow it to be made resizable and/or draggable. However, if I recall correctly one of the principles of OOJS was to be self-contained... so would this be wrong? Could someone else with a bit more firsthand experience chime in here?",1385074537,PHID-USER-wgpse4towjiaqbzotzgo,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Also editing the last equation at https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+
+if you actually make a change to the text of the equation the displayed equation becomes very jumbled. Any vertical positioning is lost, and text from different lines are overlaid on top of each other.
+
+This happens with Chrome on a Mac, I can't seem to edit equations at all with firefox or safari.",1382509541,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Created attachment 13550
+Screenshot of editing a math block
+
+Some small tweaks are needed to the dialog box. Editing the last equation at https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
+there are a a few problems
+
+1) The dialog obscures the actual equation
+2) The dlalog is too small to see the whole source text of the equation
+
+This could be solved the making the dialog, moveable and resizeable.
+
+**Attached**: {F10189}",1382508786,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"If you have open tasks or bugs left, one possibility is to list them at https://www.mediawiki.org/wiki/Google_Code-In and volunteer yourself as mentor.
+
+We have heard from Google and free software projects participating in Code-in that students participating in this programs have done a great work finishing and polishing GSoC projects, many times mentores by the former GSoC student. The key is to be able to split the pending work in little tasks.
+
+More information in the wiki page. If you have questions you can ask there or you can contact me directly.",1382470549,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"GSoC ""soft pencils down"" date was yesterday and all coding must stop on 23 September. Has this project been completed?",1379434494,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Its important that it will be possible to enter the raw latex and that the text input area is large enough to enter a large formula. Editing the formula for atan2 at https://www.mediawiki.org/wiki/VisualEditor:TestMath now give a multi line box, but its still a bit small and wraps the formula. 
+
+It may be an idea to use a different size box for inline formula which tend to be short and display formula which tend to be larger. $ vrs $$ in latex syntax, I don't know how you would distinguish this in VE.
+
+The need for latex input was discussed at https://www.mediawiki.org/wiki/User_talk:Jiabao_wu and came up again at http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=570517247&oldid=570514963",1377691093,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,Possibly related: https://en.wikipedia.org/wiki/Wikipedia_talk:Flow#Mathematics_under_Flow,1376190076,PHID-USER-omdcggvudfkuawipp23i,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to comment #7)
+> @Richard this plugin won't be dependent on bug 36496 (MathJax as default).
+> Texvc-compatible syntax remains the internal/wikitext format. MathJax
+> provides
+> a live-preview within VE to enable visual editing. (Of course, a future
+> iteration might use MathJax to save MathML and SVG alongside the TeX.)
+
+Have removed the dependency.
+
+(In reply to comment #8)
+> Is this connect with http://www.mediawiki.org/wiki/VisualEditor:TestMath?
+
+Yes; that's the work being done by Jiabao Wu as part of Google Summer of Code. See https://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Project_Work for updates.",1373926378,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"@Richard I don't know which VE version is running there. I think I should point out that this is a GSoC project in the middle of development, not anywhere near production ready, frequently breaking etc.",1373924458,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,Is this connect with http://www.mediawiki.org/wiki/VisualEditor:TestMath? If so its a nice start but I'm having trouble editing a large formula for arctan2 at the bottom?,1373914340,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"@Richard this plugin won't be dependent on bug 36496 (MathJax as default). Texvc-compatible syntax remains the internal/wikitext format. MathJax provides a live-preview within VE to enable visual editing. (Of course, a future iteration might use MathJax to save MathML and SVG alongside the TeX.)",1373910001,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"**physik** wrote:
+
+I think a combination of MathML and MathJax would be optimal.
+See https://gerrit.wikimedia.org/r/#/c/69298/",1373790125,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"Wondering how the rendering is going to happen? Is it going to use MathJax which is the only game in town at the moment? The default texvc render won't be up to the job as it need to recreate an image for every keystroke. MathML based renders have basically failed with poor browser support. 
+
+If you use MathJax deployment will be a problem unless bug 36496 is fixed.",1373785257,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"(In reply to comment #3)
+> Are there any news on this?
+
+Jiabao was accepted as a GSoC student and will be working on this with us. Updates are going to be added at [[mw:User:Jiabao wu/GSoC 2013 Project Work]].",1370657625,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,Are there any news on this?,1370656180,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"**jiabao.foss** wrote:
+
+(In reply to comment #1)
+> This will require Parsoid to be finished and expose ParserHooks to get
+> alienated, and then a VE node handler to be written. The first bit is
+> relatively easy, but the second is a very significant undertaking, so
+> prioritising as ""lowest"".
+
+Hello James, I have designed and written my proposal for a plugin that will fix this bug. http://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Application
+
+I am not yet familiar with the VE architecture so I need some help understanding it and your comments. Is my design close to what it needed for a ""node handler"" for the maths elements in a wiki page. Also currently I have two modules named doc reader and doc writer. It would be helpful to know more about how these can interact with the document in visual editor.
+
+The design that I proposed of the User Interface for my plugin be similar to that of google docs. I am wondering if this is closer to what the community wants and needs for VisualEditor. Or if it would be better to stay closer to the existing way special characters are inserted in the traditional wikitext editor.
+
+Thanks,
+Jiabao",1367240312,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+Create a visual VisualEditor plugin tool to add/edit maths blocks,"This will require Parsoid to be finished and expose ParserHooks to get alienated, and then a VE node handler to be written. The first bit is relatively easy, but the second is a very significant undertaking, so prioritising as ""lowest"".",1355432140,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nspbk6goaacnxvuhl4ff,task_subcomment,NA
+VisualEditor: Review window behind article,"**Author:** `jnichols`
+
+**Description:**
+I can only see the very top few lines of the review-and-save window, the notices window, and the edit summary window. The rest of them seem to be behind the article window. I can scroll down the review window, looking at it three lines at a time in the little area between the top of the article and the tabs. The notices window and the edit summary windows don't scroll, which means I can't get down to the final ""save"" button.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1355378580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-63cm7igyhb5qdw236lct,task_description,declined
+VisualEditor: Review window behind article,"sorry for the criticism, and WORKSFORME is better, of course!",1366181978,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"Sorry for the lack of response; I reviewed this bug quite a few times in the months since it was reported, and each time was unable to reproduce (but quite clearly this was a repeatable bug, given the screenshot and two independent reports).
+
+This was not a 'blocker' in the sense that we use it, though obviously for a (seemingly very small) number of installations/situations it was a serious bug.
+
+Glad to hear that it works for you now; unfortunately, as we don't know what the root cause was, we can't proove that it's not going to re-occur. Thus I feel it would be inappropriate to assign it as ""FIXED"", so I will instead mark as ""WORKSFORME"".",1366178124,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"It is possible that the bug has been resolved, I had reported it, but cannot reproduce it. Closing as ""probably fixed"".
+
+A minor criticism on bug management: at the time when Jeffery and I reported this, it was a totally debilitating bug, a blocker. Simply not investigating the bug 4 months, seemingly never testing it, but then reducing the severity to ""minor"" seems odd.",1366174654,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"I can confirm with newest Chrome. Problem only happened to me on the mediawiki.org VE test page, where the en.wikipedia VE works fine.",1355400423,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"**jnichols** wrote:
+
+Screenshot of problem
+
+**Attached**: {F10179}",1355382411,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,"**jnichols** wrote:
+
+User:Arctic.gnome VisualEditor Screenshot
+
+//attachment Arctic.gnome VisualEditor Screenshot.JPG ignored as obsolete//",1355382188,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+VisualEditor: Review window behind article,Could you take a screenshot and attach it to this ticket?,1355380463,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-63cm7igyhb5qdw236lct,task_subcomment,NA
+"VisualEditor: edits marked as ""minor"" without explicit user selection","See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Marking_edits_as_minor for the report and http://en.wikipedia.org/w/index.php?title=Ginger_nut&diff=527654509&oldid=526997552 as an example.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355346240,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dmuriij6wzg4f6nemlx3,task_description,resolved
+"VisualEditor: edits marked as ""minor"" without explicit user selection",Add to deployment milestone.,1357594475,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dmuriij6wzg4f6nemlx3,task_subcomment,NA
+"VisualEditor: edits marked as ""minor"" without explicit user selection",https://gerrit.wikimedia.org/r/38480,1355363288,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dmuriij6wzg4f6nemlx3,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"There is only one notice, but it says there are 2!
+
+See the screenshot and also
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=527687053&oldid=527683727
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61335
+
+**Attached**: {F10115}",1355324760,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_description,resolved
+VisualEditor: Deal with en.wikipedia.org's edit notice system,I just fixed it with https://en.wikipedia.org/w/index.php?title=MediaWiki:Common.css&diff=624714120&oldid=624708988,1410207320,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"This is still occuring.  Pages with no edit notices pop up with ""1 notice"" when VE is launched.  It is not even useful in providing a link to where I *can* add an edit notice.",1407760794,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Fixed on-wiki.,1394664023,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"Change 118369 merged by jenkins-bot:
+mw.Target: Add class ""mw-ve-editNotice"" to edit notices
+
+https://gerrit.wikimedia.org/r/118369",1394662517,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"Change 118369 had a related patch set uploaded by Krinkle:
+mw.Target: Add class ""mw-ve-editNotice"" to edit notices
+
+https://gerrit.wikimedia.org/r/118369",1394662319,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"Looks like we do have a replacement class that isn't too generic:
+
+ .ve-ui-mwNoticesPopupTool-item ...
+
+Though it is an internal class, not one I'd recommend we promote as an API for wikis to use. Let's use that as a temporary replacement, and add another one soon for the long term.",1394661278,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"(In reply to Erik Moeller from comment #10)
+> Regression; this is happening again on en.wp.
+
+The system is an en.wikipedia hack, and can't be fixed from within VisualEditor without it knowing more than it should about English Wikipedia.
+
+It comes down to their Editnotice system explicitly creating an edit notice to tell sysops ""there are no edit notices on this page, click here to create one"", which they present as... an edit notice.
+
+Thus MediaWiki, and by extend VisualEditor, show it as an edit notice.
+
+Last year I put a system in place that allows them to hide these using a css class.
+
+(In reply to Minh Nguyễn from comment #12)
+> I've proposed a client-side workaround at [[MediaWiki talk:Common.css#Edit
+> notices and VisualEditor]].
+
+That css was adopted by en.wikipedia as of https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.css&diff=562641575&oldid=560030040 and that fixed it for them, last year with this:
+
+/**
+ * Hide the redlink generated by {{Editnotice}},
+ * this overrides the "".sysop-show { display: none; }"" above that applies
+ * to the same link as well.
+ */
+.ve-init-mw-viewPageTarget-toolbar-editNotices-notice .editnotice-redlink {
+    display: none !important;
+}
+
+
+Commit https://gerrit.wikimedia.org/r/#/c/90378/ accidentally removed this class, thus the above CSS rule no longer applies.
+
+The CSS proposed by Minh on [[MediaWiki talk:Common.css#Edit
+> notices and VisualEditor]] is a bit too generic in my opinion, I would recommend against that.",1394660986,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,*** Bug 55951 has been marked as a duplicate of this bug. ***,1394495869,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,*** Bug 61335 has been marked as a duplicate of this bug. ***,1394490038,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,I've proposed a client-side workaround at [[MediaWiki talk:Common.css#Edit notices and VisualEditor]].,1392880263,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Bug 55951 is possibly a duplicate?,1392836682,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Regression; this is happening again on en.wp.,1387305797,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Tagging with deploy-train cycle.,1357578650,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,*** Bug 43460 has been marked as a duplicate of this bug. ***,1356713507,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"(In reply to comment #6)
+> Change-Id: I65447da8b88a9bae9c24ff155544ff66b3fe9100
+Merged by Trevor",1355360215,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,Change-Id: I65447da8b88a9bae9c24ff155544ff66b3fe9100,1355358427,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"The only thing we need in core for en.wikipedia to drop this (assuming they still actively want to have these red links) is to show a red link to where the edit notice can be edited/created. Once that is in core, the enwiki's template doesn't have to generate it and thus the actual edit notice will be empty.
+
+As a workaround, I'll work on implementing a small jQuery plugin to calculate the visible text in an element. Then we can simply iterate over the edit notices in VE and ignore the ones with no visible text.",1355345877,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"So, as a way around this, could we have a hacky exception? Or should we push upstream and suggest that core editnotices are adjusted so that every wiki has enwiki's system? (Presumably this would need a new Editnotice: namespace if they want general availability.)",1355339876,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"It counts 2 because there are 2. One from VisualEditor (the default alpha-warning) and one from en.wikipedia.org.
+
+English Wikipedia has this self-invented wikitext-organised edit notice system. Long story short, it means there is never not a notice. It always shows something.
+
+In this case the edit notice that it loads is the following html:
+
+<div id=""editnotice-area"" class=""editnotice-area"" style=""clear: both; width: 100%;""><div class=""editnotice-namespace"" style=""width: 100%;"">  </div><div class=""editnotice-link editnotice-redlink sysop-show accountcreator-show"" style=""clear: both; float: right; margin: 0px 0.8em; padding: 0; line-height: 1em; display: none;""> <small><a href=""/w/index.php?title=Template:Editnotices/Page/You_Can%27t_Make_a_Heart_Love_Somebody&amp;action=edit&amp;redlink=1"" class=""new"" title=""Template:Editnotices/Page/You Can't Make a Heart Love Somebody (page does not exist)"">Page notice</a></small> </div><div style=""clear: both;""></div> </div>
+
+English Wikipedia uses Template:Editnotices to maintain their notices (embedded from a one-liner in the MediaWiki namespace) since they don't want to restrict it to sysops. Aside from that they want to advertise this template and make it easy to find. So when there is no edit notice, the template outputs a link to create one. This is not created by MediaWiki nor by VisualEditor.
+
+However it isn't a mini-notice with a red link for most users. It is only visible to sysops and account creators (via the CSS class sysop-show and accountcreator-show), so for regular users it is just empty.",1355339266,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"It looks to me like it counts the edit notice as such even when none is present?
+
+Separately but relatedly, it would probably be nicer to have features such as adding edit notices in the proposed metadata flyout, as opposed to showing a red link notice to users with the right to create notices.",1355336986,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+VisualEditor: Deal with en.wikipedia.org's edit notice system,"Yes, I just came to report the same. Confirming that VisualEditor on the English Wikipedia currently states there are two notices when only one is visible.",1355327320,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hjoe3umj3mbaqn4fu5f7,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Like this: https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=615802&oldid=615801
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355298420,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_description,open
+Automatically convert external links to local resources to local wiki links if possible,,1604534063,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,,1604532057,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,*** Bug 57019 has been marked as a duplicate of this bug. ***,1397764105,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to Liangent from comment #11)
+> (In reply to James Forrester from comment #10)
+> > No, all edits - this is the same as [http://fr.wikipedia.org/wiki/Foo Bar]
+> > being automatically converted by Parsoid to [[:fr:Foo|Bar]] which it already
+> > does.
+> 
+> I feel there're still some deliberate use cases of external local links, for
+> example, to prevent Echo notifications (see [[Template:Noping]]).
+
+Users making hacks around bugs in Echo sounds like something we should fix in Echo so users don't have to do it, though. :-)",1397756178,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to James Forrester from comment #10)
+> No, all edits - this is the same as [http://fr.wikipedia.org/wiki/Foo Bar]
+> being automatically converted by Parsoid to [[:fr:Foo|Bar]] which it already
+> does.
+
+I feel there're still some deliberate use cases of external local links, for example, to prevent Echo notifications (see [[Template:Noping]]).",1397743062,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to Liangent from comment #9)
+> (In reply to James Forrester from comment #8)
+> > Feels like this has consensus that we should convert newly-added
+> > [http://en.wikipedia.org/wiki/foo] links to [[foo]] automatically; I think
+> > that this should be done inside Parsoid, so moving there.
+> 
+> But only for VisualEditor edits? if Parsoid is going to be used in other
+> stuff eg. bots.
+
+No, all edits - this is the same as [http://fr.wikipedia.org/wiki/Foo Bar] being automatically converted by Parsoid to [[:fr:Foo|Bar]] which it already does.",1397742161,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to James Forrester from comment #8)
+> Feels like this has consensus that we should convert newly-added
+> [http://en.wikipedia.org/wiki/foo] links to [[foo]] automatically; I think
+> that this should be done inside Parsoid, so moving there.
+
+But only for VisualEditor edits? if Parsoid is going to be used in other stuff eg. bots.",1397730019,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Feels like this has consensus that we should convert newly-added [http://en.wikipedia.org/wiki/foo] links to [[foo]] automatically; I think that this should be done inside Parsoid, so moving there.",1397673447,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Also, when users create a new article and want to link back to it immediately, they end up attaching ""?venotify=created"" to the external link they're copy/pasting, and this is something VE will need to strip before converting the URL to a wikilink.",1395682999,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"I think maybe it should just recognize when a url points to an existing Wikipedia article, and offer that as an internal link option, similarly to the way that you get an internal link option for the article titled [[http://en.wikipedia.org/wiki/foo]]. That latter behavior represents a tiny edge case, though, as there are very few articles that start with http://. If there is ever going to be some sort of 'advanced' mode for links, then options to use external links to existing articles and internal links to articles starting http* should be hidden away there. In the vast majority of cases, users intend to create internal links if the article exists, and do not intend to create internal links to pages starting http*.
+
+Incidentally, we want to add the same functionality to the EducationProgram extension for when users paste in a url to the article form: bug 44397.",1377277696,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"I'd go for ""prevent"". (Also, it would be really nice to have it soon).",1377094454,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Seeing a few of these in the feed. Warn, perhaps? (In the link inspector dialog.)",1372610363,PHID-USER-n6a5asuonlcdc2xmndl2,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"(In reply to comment #2)
+> Sometimes it is done deliberately, e.g. at
+> https://en.wikipedia.org/w/index.php?title=English_Wikipedia&oldid=558847653
+> . 
+> In that case, they do use olids (permalinks), which is a way you could
+> distinguish if you wanted to do the auto-replacement.
+
+We could do an always-replace for [http://foo/wiki/* $1], but that feels like a fragile regexp. :-(",1371420809,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Sometimes it is done deliberately, e.g. at https://en.wikipedia.org/w/index.php?title=English_Wikipedia&oldid=558847653 .  In that case, they do use olids (permalinks), which is a way you could distinguish if you wanted to do the auto-replacement.",1371258257,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+Automatically convert external links to local resources to local wiki links if possible,"Ask, or just silently replace? But then it will 'dirty diff' if this has been done deliberately. Also, to do this, link inspector will need to have a concept of canonical URLs and optional other URLs for this context, which is messy as hell.",1355343159,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bbycowhblqb7wl5ri2sh,task_subcomment,NA
+VisualEditor: Retries when badtoken happened should request new tokens,"When I'm using VisualEditor, session failed for unknown reason. The VisualEditor then keep asking whether I want to try again but it always tries with the old token and error ""badtoken"" keeps coming.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355292720,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-kgk6kmve6lavlyhdrvmv,task_description,resolved
+VisualEditor: Retries when badtoken happened should request new tokens,Merged and will go out with wmf5.,1369080457,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kgk6kmve6lavlyhdrvmv,task_subcomment,NA
+VisualEditor: Retries when badtoken happened should request new tokens,Related URL: https://gerrit.wikimedia.org/r/64492 (Gerrit Change Ib43d1938ffa24bc8d1dc76a300e16e486dabd928),1368896118,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kgk6kmve6lavlyhdrvmv,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"Right now, the Save button starts disabled, but when the transaction depth is non-zero it's enabled. This means that two actions that reverse each other (rather than being formally undone) let the user make a 'null edit', which MW then silently accepts.
+
+Ideally, the Save/Create button should be disabled if dm state is identical to page when it was loaded (except for the special-case of oldid pages, where it should always be enabled). Roan suggests a string comparison of the current and original HTML is the least-bad option, given the lack of hash functions in JavaScript.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43270",1355199480,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-m3nqsseg45psoqx36exc,task_description,resolved
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,I'd suggest that once that change has been merged this bug can be closed.,1363363213,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"Fixed the zero-history case, and the onbeforeunload issue: https://gerrit.wikimedia.org/r/#/c/53988/",1363363142,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"After some more investigation is appears that comparing html might not do the trick. Doing something trivial like typing and deleting may not leave the html in it's original state. We currently have change markers (although these are queued up for deletion), but also hidden things like pawn characters and maybe other things in the future.
+
+We can still implement the transaction stack check which we don't have at the moment, but telling you if there is a non-zero diff may have to be a job for Parsoid.",1363281542,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"Agree on the window.onbeforeunload.
+
+Not totally enamoured with the idea of a modal alert telling users off for behaviour that is currently silently failing (in core wikitext editor, if you make a null save it'll look like it saved, but no new entry in the history log).
+
+Possibly we could over-ride the edit-success box to say ""You made no changes so nothing was saved"" or something similar? We should probably talk to E3 to see if this is something they'd want to see happen in core anyway...",1363280830,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded,"Right now the Save button becomes enabled after the first transaction is applied and never goes back to disabled, even if the first transaction is undone. While this isn't ideal, doing a full HTML comparison on pretty much every keystroke may be a bit of an unnecessary overhead. Even doing an transaction stack comparison is a little unnecessary.
+
+The real problem here is the creation of null edits and that only needs to be addressed when the save button is pressed. This could trigger an alert (""You haven't made any changes"") and reset the button to disabled. We should also run this check in the window.onbeforeunload handler so people can leave the page nag-free if they undo their edits.",1363254743,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-m3nqsseg45psoqx36exc,task_subcomment,NA
+VisualEditor: HTML entities following double-bracket links are not displayed correctly,"Try to VE-edit this page: http://www.mediawiki.org/wiki/VisualEditor:Extension:ConfirmAccount
+
+Compare: http://parsoid.wmflabs.org/mw/VisualEditor:Extension:ConfirmAccount
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355068140,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-log2ro3sq5p5acp2puga,task_description,declined
+VisualEditor: HTML entities following double-bracket links are not displayed correctly,"This works now, ""&nbsp;"" isn't spelled out any more, and the nbsp is rendered as a <span class=""ve-ce-MWEntity""> in the editor as it's supposed to be. There are probably some selection issues with the nbsp's and with the ampersands encoded as &amp; but that's due to a different bug.",1361383659,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-log2ro3sq5p5acp2puga,task_subcomment,NA
+VisualEditor: HTML entities following double-bracket links are not displayed correctly,"Indeed. The wikitext source reads:
+
+ [[File:Bulbgraph.png|18px|Note|link=]]&nbsp;'''Note''':
+
+The html rendering:
+
+ <img> Note:
+
+VisualEditor:
+
+ <img>&nbsp;Note:
+
+Where ""&nbsp;"" are all separate, selectable and editable characters.
+
+They do roundtrip properly though.",1355070979,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-log2ro3sq5p5acp2puga,task_subcomment,NA
+VisualEditor: Selecting multiple empty paragraphs results in selection decreasing by one line per poll interval,"Steps to reproduce:
+Edit a page with VisualEditor.
+Press return key a few times.
+Select those empty lines with mouse or shift+arrows.
+Watch in awe as the selected lines decrease one per polling interval.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354835520,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-7cmqtr6tlqrqawji66zc,task_description,resolved
+VisualEditor: Selecting multiple empty paragraphs results in selection decreasing by one line per poll interval,Fixed here: https://gerrit.wikimedia.org/r/#/c/37364/,1354844641,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-7cmqtr6tlqrqawji66zc,task_subcomment,NA
+VisualEditor: Link inspector suggestions highlight multiple items if they have the same label,"Reproduce:
+
+1. Make a link to http://www.google.com
+2. Click out of the link
+3. Inspect the link
+4. Both new page and external link are selected
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354583100,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-sqz4vnvgzmxmvjkrplhx,task_description,resolved
+VisualEditor: Link inspector suggestions highlight multiple items if they have the same label,Patched in https://gerrit.wikimedia.org/r/#/c/36799/ and merged.  Marking resolved.,1354652046,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-sqz4vnvgzmxmvjkrplhx,task_subcomment,NA
+VisualEditor: Context menu shows up in the wrong place on load if document starts with link,"When a document starts with a link, the animation on the page cause the context's location to be incorrect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354572300,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-jprjjnlynxuoul2du4w2,task_description,resolved
+VisualEditor: Context menu shows up in the wrong place on load if document starts with link,Fixed in gerrit 36653,1354573861,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jprjjnlynxuoul2du4w2,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,"https://www.mediawiki.org/w/index.php?title=VisualEditor%3APre&diff=609875&oldid=609874
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353980580,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nhhyjbko2xftjs44uuqt,task_description,resolved
+VisualEditor: Leading newlines in <pre>s get eaten,"Parsoid fixes have landed, issue confirmed fixed in VE as well.",1354757611,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,The VE portion of this is fixed in https://gerrit.wikimedia.org/r/36692 . The Parsoid portion of this is bug 42666 and bug 42667.,1354584256,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,"The approach we're taking now is that VE will work around this in cases where there are semantically meaningful newlines in the <pre> (i.e. >=1 newline read from the DOM) by adding a newline. That only leaves the ambiguity between <pre>Foo</pre> and <pre>\nFoo</pre> , which is syntactic, not semantic, and will be handled by Parsoid using round-trip data.",1354566475,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,"(In reply to comment #1)
+> We can work around this in the converter by setting a flag on these pre's on
+> the way in and checking for it on the way out.
+...or not, grah. Because of the way the DOM API works, I have no way of detecting this from within a browser.",1354563233,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+VisualEditor: Leading newlines in <pre>s get eaten,"Mark and I looked at this and discovered it was because VE round-trips the HTML in question through the browser's HTML parser, which turns ""<pre>\n"" into ""<pre>"". Shockingly, this is actually mandated by the HTML spec.
+
+We can work around this in the converter by setting a flag on these pre's on the way in and checking for it on the way out.",1354155689,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nhhyjbko2xftjs44uuqt,task_subcomment,NA
+"VisualEditor: After clicking out of link inspector, pressing enter removes wrong text","1. Type the text ""Foo bar baz""
+2. Select ""bar""
+3. Click the link toolbar button
+4. Click between the a and the z (""ba|z"") to cause the inspector to close
+5. Press enter
+
+Expected result: paragraph is split with ""z"" in a new paragraph
+Actual result: ""bar"" is removed, paragraph is split with ""baz"" in a new paragraph
+
+Occurs in both Firefox and Chrome. Isn't reproducible 100% of the time.
+
+Theory:
+1. User changes selection to ba|z
+2. SurfaceObserver notices and adjusts its selection
+3. Link inspector notices and triggers annotation on a fragment with a different range (the link)
+4. Some bug in SurfaceObserver or SurfaceFragment causes SO to believe the current selection is now the link
+5. User presses enter, SO removes what it believes is the selection
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353378540,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ca4ckkjl6hs65faqueyf,task_description,resolved
+"VisualEditor: After clicking out of link inspector, pressing enter removes wrong text",Fixed in recent inspector rewrite: I38995d4101fda71bfb2e6fe516603507ce820937 and Ibf6b26de299e54ae8688a2653bf5d5538927f8c3,1353971697,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-ca4ckkjl6hs65faqueyf,task_subcomment,NA
+VisualEditor: Zero-length selection in link should show inspector icon,"This currently works for selections within links, but not for zero-length selections. Except if you hit bug 42275, then the inspector icon will appear on every zero-length selection, anywhere, and will chase you forever and ever.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353376860,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-uv4cfp2ue45fk333wtws,task_description,resolved
+VisualEditor: Zero-length selection in link should show inspector icon,Fixed in I38995d4101fda71bfb2e6fe516603507ce820937 and Ibf6b26de299e54ae8688a2653bf5d5538927f8c3,1353971560,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-uv4cfp2ue45fk333wtws,task_subcomment,NA
+VisualEditor: Zero-length selection in link should show inspector icon,This was resolved in the recent inspector rewrite.,1353971278,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-uv4cfp2ue45fk333wtws,task_subcomment,NA
+VisualEditor: Zero-length selection in link should show inspector icon,"This bug seems to only be triggered by newly created links, not by links that were already present on the page.",1353379521,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-uv4cfp2ue45fk333wtws,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"The VisualEditor interface does not currently recognize page protection. If a user visits a protected page (a page to which he or she does not have access to edit), VisualEditor will still display a working edit form and the first click of the ""Save page"" button will work. It will produce a dialog box that will present a second ""Save page"" button that does not work. Ideally, VisualEditor would not let a user get this far without indicating that the page is uneditable.
+
+Related to this, there's no warning for administrators that a page is protected when they're editing the page. This may be a separate bug, however.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352958960,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_description,resolved
+VisualEditor: Don't offer Edit button when user cannot edit page,"Yeah, well, different ""protection"" levels for VE and non-VE editors feels like the wrong kind of solution.",1354127087,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"That's not a problem I guess, but I noticed while implementing it that it was a matter of removing the code that explicitly ignored the presence of the edit button for sysops.
+
+Change-Id: I3fe29c52b743837c2e1d66f25ccdca6115b8bd25",1354126324,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"If we do that it means we can no longer pseudo-restrict ""Edit source"" on a different level than ""VisualEditor Edit"".
+
+e.g. on MediaWiki.org we protected the namespace with sysop, but allowed users to edit it with VE.",1354067377,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"I suppose the lazy solution (use the presence of a button outputted by server side) is sufficient, especially given that if someone games it, saving will still fail. Its only for the UI.",1354054378,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,"And for the current page, I suppose wgRestrictionEdit and wgUserGroups could be used.",1353124274,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,We have mw.user.getRights()[async] now in core as well.,1353124198,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Don't offer Edit button when user cannot edit page,We should be able to detect in JS whether the user has the edit permission for this page. One way we can detect this is by checking whether the user gets an edit tab or a view source tab.,1353115536,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3ij7dtc5vwzmge2qmliq,task_subcomment,NA
+VisualEditor: Internal page links touched by VisualEditor contain underscores,"Currently when a user uses the link dialog box tool thing in VisualEditor to specify where certain text should link to, if the user specifies an internal page as the target, the wikitext for the link will use underscores.
+
+For example, I highlight some text in VisualEditor with my mouse and then click the link icon. A ""Hyperlink"" dialog box appears and I enter ""MediaWiki on IRC"" into the text input area. I hit the ""return"" key on my keyboard to make the dialog box disappear and now I have a blue link in my VisualEditor interface. If I then save this page and look at its wikitext source, I see:
+
+[[MediaWiki_on_IRC|fffffffff]]
+
+Internal links are using underscores. This is wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49310",1352957940,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-wydq63k4j2l2fgeenwfb,task_description,resolved
+VisualEditor: Internal page links touched by VisualEditor contain underscores,"This was an issue in VE's internal link handling code, not in Parsoid. Although the original reason for the code working the way it did (normalizing to underscores) was indeed to make Parsoid happy, as I found out the hard way when I tried to fix this by just normalizing to spaces instead.
+
+Fixed in https://gerrit.wikimedia.org/r/34253",1353380505,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wydq63k4j2l2fgeenwfb,task_subcomment,NA
+VisualEditor: Internal page links touched by VisualEditor contain underscores,Possibly a Parsoid issue?,1353018108,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wydq63k4j2l2fgeenwfb,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"The current VisualEditor interface has a ""Save page"" dialog box with an edit summary input field. However, this edit summary input field accepts wikitext, but has no preview feature for what the rendered wikitext will look like. This is a regression from the standard (non-VisualEditor) interface.
+
+Roan said that there be a mini-editor or mini-parser or something stuck in the edit summary area at some point.
+
+**See Also**: {T62535}",1352957640,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_description,resolved
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"Change 112490 merged by jenkins-bot:
+Show preview of edit summary in review screen
+
+https://gerrit.wikimedia.org/r/112490",1392851241,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"Change 112490 had a related patch set uploaded by Alex Monk:
+Show preview of edit summary in review screen
+
+https://gerrit.wikimedia.org/r/112490",1392057409,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"To clarify, when the diff is shown ('Review your changes' dialog pane) we want to parse the entered summary and display it, probably above the diff.",1392053170,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"(In reply to comment #1)
+> As Max says, to be resolved by the dialog being a mini-VE surface.
+
+So this has been assigned to me but I think I need a few pointers. Firstly, where can I find the code for mini-surfaces?",1392042811,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"From Bug 53729:
+A De.WP user suggested to include a preview for the edit summary. Report:
+
+https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=122207411#Vorschau_f.C3.BCr_Zusammenfassung_und_Quellen",1380545717,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,*** Bug 53729 has been marked as a duplicate of this bug. ***,1380545659,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"User:Elizium23 at en.wp comments that the current save dialog ""permits entry of an edit summary with newlines, however, no newlines are preserved in the edit summary when it is saved to the Wiki. This is confusing, because I just used a WYSIWYG editor, but what I see in the edit summary is not what I get.""
+
+While, AIUI, the current dialog is only temporary the issue of newlines (and presumably bold, italic, etc) will be applicable to the new ""surface"" unless that doesn't permit these features or edit summaries are upgraded to support them.",1373483224,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"Per bug 51125 (which has been merged into this one), we should show the edit summary if provided in the ""Review your changes"" tab",1373481003,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,*** Bug 51125 has been marked as a duplicate of this bug. ***,1373480869,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?,"As Max says, to be resolved by the dialog being a mini-VE surface.",1353018028,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f4bx3pmct7c24xmmqmka,task_subcomment,NA
+VisualEditor: Pressing a list button when covering a selection of a list should unlist only that portion,"Pressing a list button on: 
+
+1. Foo
+2. Bar
+   * Baz
+   * Bang
+     1. Boom
+3. Bing!
+
+with a selection of Bang and Boom should produce:
+
+1. Foo
+2. Bar
+   * Baz
+     Bang
+     Boom
+3. Bing!
+
+(i.e. the selected LIs should be down-converted into a <P> of the most local parent list).
+
+Also, out-dent should stop a list nest level 1, not 0.",1352498880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hh227cldfkbylq2gwxw3,task_description,open
+VisualEditor: Pressing a list button when covering a selection of a list should unlist only that portion,Need to discuss desired behaviour. Not sure we should implement as described above.,1363026409,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-hh227cldfkbylq2gwxw3,task_subcomment,NA
+VisualEditor: Pressing a list button when covering a selection of a list should unlist only that portion,Assigning to Ed; this is to be done after the list code cleanup that he's doing already.,1361381610,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hh227cldfkbylq2gwxw3,task_subcomment,NA
+"VisualEditor: ""List"" buttons causes whole list to be de-listed, or converted to other list type, when only part of it is selected","Expected behaviour is that the part of the list that is selected is transformed, and the rest of the list is left as it was.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1352482200,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ugjwuslvzh6eo2ldgto4,task_description,resolved
+"VisualEditor: ""List"" buttons causes whole list to be de-listed, or converted to other list type, when only part of it is selected",Fixed in gerrit 36675,1354579506,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ugjwuslvzh6eo2ldgto4,task_subcomment,NA
+Highlighting syntax within editing window by default,"**Author:** `IJethrobot`
+
+**Description:**
+Having read <https://bugzilla.wikimedia.org/show_bug.cgi?id=16268> and <https://bugzilla.wikimedia.org/show_bug.cgi?id=11627>, this enhancement proposal is sufficiently different and is based on different discussion.
+
+There is a wide consensus of editors who would like to see syntax highlighting in the standard editing window turned on by default, particularly for references, for wiki markup.  This consensus has been reached in two discussions on en.wiki, one at the Village Pump <http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_92#Differentiating_reference_syntax_in_the_editing_window.> and one in a Request For Comments that was a part of Centralized Discussion for 30 days:  <http://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment/Syntax_differentiation_in_editing_window>.  Given the course of the discussion, and the overwhelming support for this functionality, I decided to submit this proposal to bugzilla.  
+
+Many participants in the above discussions expressed that adding a syntax highlighter would make editing a more accessible experience for newer users.  In fact, direct feedback from new editors has suggested that this has been a problem (e.g. <http://en.wikipedia.org/wiki/Special:FeedbackDashboard/46104>).  They are also unsatisfied with 
+
+Previous proposals have stated that implementing this internally is not possible.  However, this is incorrect; there are at least some examples of non-external editors that work or could work reasonably well:
+- jsfiddle:  <http://jsfiddle.net/> (with implementation: <http://doc.jsfiddle.net/>)
+- AceWikiEditor:  <http://no.wikipedia.org/wiki/Hjelp:AceWikiEditor>
+- en.wikipedia user RememberTheDot's syntax highlighter: <http://meta.wikimedia.org/wiki/User:Remember_the_dot/Syntax_highlighter> (which I use).
+
+The only thing I would have liked to see more of in the above discussions were persons who might be able to discuss a specific implementation.  Some discussion of that is here: <http://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment/Syntax_differentiation_in_editing_window#Implementation>.  Such discussion would be helpful here, given the above information on how it may be viable to implement this internally.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1352053440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_description,declined
+Highlighting syntax within editing window by default,"**IJethrobot** wrote:
+
+Thanks.  I didn't know this could be implemented by a local admin.",1352058432,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"Won't get into core, since VisualEditor is where resources are dedicated in this area (unless a volunteer picks it up, which i doubt will happen).
+
+Default gadget seems like the simplest and most effective solution. And devs won't have to deal with all the people complaining which will inevitably follow if this is turned on by default.",1352058259,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"**thewub.wiki** wrote:
+
+If there's consensus on a particular javascript implementation, and it's been thoroughly tested, then it can be done by a local administrator - see https://en.wikipedia.org/wiki/Wikipedia:Gadget#Default_gadgets
+
+Suggest closing this bug since it doesn't require any developer intervention.",1352057194,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"**IJethrobot** wrote:
+
+Right, but I figured in order to turn something on by default for all users, it would need to come here.  Also, a specific implementation would need to be decided upon.",1352054522,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"You know that the existing javascript solutions could be installed as default gadgets, right?",1352054231,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"**IJethrobot** wrote:
+
+Screenshot of AceWikiEditor as an example of syntax highlighting.
+
+**Attached**: {F10235}",1352054136,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Highlighting syntax within editing window by default,"**IJethrobot** wrote:
+
+Example of syntax highlighting using AceWikiEditor
+
+//attachment url.txt ignored as obsolete//",1352054020,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ys2g6r2fl6x4a5jhjj5w,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"Splitting this off from bug 27311 (in light of bug 27683 comment 5).
+
+MediaWiki core should have a ""create a redirect"" form. The current system is painfully unintuitive. It requires first figuring out how to create a page at all and then figuring out that you need special ""#REDIRECT [[ ]]"" syntax. Some people make the argument that this toughens people up and prepares them for the wikitext world. I believe that a form really wouldn't kill us here.
+
+Moving a page is sort of a form for making a redirect, but that requires a page already existing. In this bug, we want a form, in MediaWiki core, for creating a redirect. Special:CreatePage or Special:CreateRedirect or something.
+
+This bug might be a dupe of bug 27311, but we can't really know until someone actually implements one or the other.
+
+**See Also**: T29311 T59315",1351128360,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-s6nknz73d36vzlhe7o7x,task_description,open
+Create simple interface for adding a page redirect to MediaWiki core,"(In reply to comment #4)
+> Can someone elaborate on some of the most common use cases for creating
+> redirects to give a bit more background to this for new users not as
+> familiar.
+> 
+> Also, is this a band aid? do we need to step back and think about the reason
+> redirects are created in the first place? Does mediawiki support the concept
+> of
+> page aliases? Does the redirected page need to continue to exist as a regular
+> wikipage after the redirect has happened?
+
+[[m:Help:Redirect]] contains the necessary educational material for the topic.",1385448204,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"**swalling** wrote:
+
+(In reply to comment #4)
+> 
+> Also, is this a band aid? do we need to step back and think about the reason
+> redirects are created in the first place? Does mediawiki support the concept
+> of
+> page aliases? Does the redirected page need to continue to exist as a regular
+> wikipage after the redirect has happened?
+
+Yes, I think the redirected page should exist as a regular wikipage after the redirect has happened. This allows any editor to un-redirect something without needing a special form or other interface, edit the redirect easily, etc. 
+
+Consider this real case from English Wikipedia:
+
+* Someone originally made ""Deforestation in Brazil"" a redirect to the Deforestation section in Amazon Rainforest. This isn't bad, but they're not actually aliases of each other precisely. This happens more than you'd think.
+* Later, someone un-redirected Deforestation in Brazil, and expanded it to be a large independent article. This was made easy by the fact that redirects are still wiki pages. Otherwise, there'd have to be new background processes to re-make a redirect as a wiki page. 
+
+Part of the challenges with the current implementation, which involves using somewhat arcane markup, will be solved by VisualEditor.",1385165137,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"Can someone elaborate on some of the most common use cases for creating redirects to give a bit more background to this for new users not as familiar.
+
+Also, is this a band aid? do we need to step back and think about the reason redirects are created in the first place? Does mediawiki support the concept of page aliases? Does the redirected page need to continue to exist as a regular wikipage after the redirect has happened?",1385164557,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"(In reply to comment #2)
+> Thanks to Daniel Friesen for pointing out that
+> https://www.mediawiki.org/wiki/Extension:CreateRedirect exists.
+
+Right. This bug is about MediaWiki core, though.",1364956227,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,Thanks to Daniel Friesen for pointing out that https://www.mediawiki.org/wiki/Extension:CreateRedirect exists.,1364928187,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+Create simple interface for adding a page redirect to MediaWiki core,"I can see plenty of Wikimedia and other MediaWiki users happy with this feature.
+
+It would be good to know whether there is a buy in from the Core maintainers or whether they think this should be handled by an extension. A rough idea of the estimated work would be useful too. It sounds like a potential candidate for http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects
+
+PS: found thanks to https://www.mediawiki.org/wiki/Bug_management/Triage/20130307",1362675063,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-s6nknz73d36vzlhe7o7x,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"resources/mediawiki/mediawiki.feedback.js is a little-known built-in software feedback feature that's used by a couple of extensions, notably UploadWizard and VisualEditor.
+
+It posts feedback to a wiki page. It used to also post user-agent information for debugging alongside the feedback. The user-agent information from posted feedback was removed in:
+
+https://gerrit.wikimedia.org/r/#/c/26417/
+
+While the fact that user-agent information is published was disclosed, there was concern that it would be preferable to add an explicit checkbox. The following text has been vetted by legal:
+
+[ ] I understand that my user agent information includes information about my exact browser and operating system version and will be shared publicly alongside my feedback. I agree to provide feedback in accordance with the Terms of Use. 
+
+On WMF sites, that would link to https://wikimediafoundation.org/wiki/Terms_of_Use - not sure we have a standard MW message that would apply here.
+
+--------------------------
+**Version**: 1.21.x
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33365",1350950160,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_description,resolved
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Change 192749 merged by jenkins-bot:
+Refactoring mw.Feedback to work with OOUI elements
+
+[[https://gerrit.wikimedia.org/r/192749]]",1425407946,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Change 32700 abandoned by Jforrester:
+Feedback includes browser info, given user permission
+
+Reason:
+Being done as part of Id1967a83a.
+
+[[https://gerrit.wikimedia.org/r/32700]]",1424890020,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Change 192749 had a related patch set uploaded (by Mooeypoo):
+[wip] Refactoring mw.Feedback to work with OOUI elements
+
+[[https://gerrit.wikimedia.org/r/192749]]
+",1424829663,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to James Forrester from comment #9)
+> When you post on a talk page you write every byte that gets inserted (except
+> for ==s for new sections and PST substitutions).
+
+Now that you mention that, I'd say that if you're not logged in, your IP address is also included on the page history.",1410702866,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to James Forrester from comment #9)
+> When you post on a talk page you write every byte that gets inserted 
+
+Definitely not,
+
+> (except
+> for ==s for new sections and PST substitutions). 
+
+as you say yourself,
+
+> That's very different from
+> auto-inserting
+
+and how about the preload parameter?
+If pre-save transform is consider radically different from preload, we could use a new magic word OMGREALLYSCARYPRIVATEDATABUTPLEASESHAREIFYOUWANTTOHELPTHESOFTWARE.",1410702649,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to Nemo from comment #8)
+> (In reply to James Forrester from comment #7)
+> > Though that sounds attractive, I'm told that that would not be appropriate,
+> > informed consent.
+> 
+> How is it different from posting on a talk page? Surely such a difference
+> can be eliminated.
+
+When you post on a talk page you write every byte that gets inserted (except for ==s for new sections and PST substitutions). That's very different from auto-inserting private data (their user agent string) and hoping that they recognise it as such and remove it if they're not comfortable with that level of privacy intrusion.",1409691151,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to James Forrester from comment #7)
+> Though that sounds attractive, I'm told that that would not be appropriate,
+> informed consent.
+
+How is it different from posting on a talk page? Surely such a difference can be eliminated.",1409689188,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"(In reply to Nemo from comment #6)
+> However I think there ought to be a much simpler solution: why can't the
+> dialog just add the requested user-agent information in the text area?
+> Instead of being blank, the ""message"" could be prefilled with ""~~~~ (using
+> Firefox 30)"" or similar (when configured to do so). The user would have a
+> very obvious way to remove the information by deleting it from the message;
+> if they don't, it will be covered by
+> https://meta.wikimedia.org/wiki/Privacy_policy#Because_You_Made_It_Public
+
+Though that sounds attractive, I'm told that that would not be appropriate, informed consent.",1409669215,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"I very much agree this is needed, especially for https://commons.wikimedia.org/wiki/Commons:Upload_Wizard_feedback where many sections are made of little use for lack of any browser information.
+
+However I think there ought to be a much simpler solution: why can't the dialog just add the requested user-agent information in the text area? Instead of being blank, the ""message"" could be prefilled with ""~~~~ (using Firefox 30)"" or similar (when configured to do so). The user would have a very obvious way to remove the information by deleting it from the message; if they don't, it will be covered by https://meta.wikimedia.org/wiki/Privacy_policy#Because_You_Made_It_Public",1409668075,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,Patch in Gerrit (link in comment 2) still needs review.,1374738778,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,Patch amended with form validation and requirement of checkbox being ticked.,1355279781,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Posting here my review about the proposed label associated to the new checkbox:
+
+(...) The message is associated to a checkbox saying 2 very different things:
+1. Willing and knowledge about sharing browser information
+2. Acceptance of Terms of Use
+
+This makes me think that I HAVE TO mark the checkbox in order to actually submit my feedback, and that along my feedback the User Agent will be visible, and if I don't mark that checkbox it means I don't agree with the Terms of Use and feedback won't be submitted.
+
+This is not what actually happens: Leaving the check unmarked still allows the user to submit the feedback, but without providing the User Agent information.
+
+If the actual behavior is the desired one, the message needs to be split, or at least provide clear ""feedback"" that the checkbox is totally unrelated to Terms of Use acceptance.",1354970468,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"Change https://gerrit.wikimedia.org/r/#/c/32700/ 
+Better ideas on msgs?",1352546161,PHID-USER-w6tinhtsh44tn3tgzjtw,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+[mediawiki.feedback.js] Add checkbox to submit user-agent info,"I have a change ready for this, will push soon.",1352541550,PHID-USER-w6tinhtsh44tn3tgzjtw,False,PHID-TASK-6vw3aq5up3oho4pbayyr,task_subcomment,NA
+VisualEditor: Cursor misplaced after clicking on nowiki block,"= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+1) Open http://www.mediawiki.org/wiki/VisualEditor:Test
+2) Click within the nowiki block
+3) Press Left
+Problem: Cursor is now at top of page
+
+Repeating from step 2, the cursor then appears in various places.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350626220,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-rdvinxanauxpvzlynziw,task_description,resolved
+VisualEditor: Cursor misplaced after clicking on nowiki block,Fixed given the alienation re-write.,1360206039,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rdvinxanauxpvzlynziw,task_subcomment,NA
+VisualEditor: Cursor misplaced after clicking on nowiki block,Confirmed.,1350939028,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rdvinxanauxpvzlynziw,task_subcomment,NA
+VisualEditor: Clicking at the left of a wikicode block does not put the cursor there.,"With this wikicode
+
+= Heading 1a =
+<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>
+
+== Heading 2aa ==
+
+
+Problem: Clicking at the left of the wikicode block does not put the cursor there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350615240,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-ncyndehe2estt3jwmggo,task_description,resolved
+VisualEditor: Clicking at the left of a wikicode block does not put the cursor there.,Fixed (https://gerrit.wikimedia.org/r/#/c/48964/).,1360795517,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-ncyndehe2estt3jwmggo,task_subcomment,NA
+VisualEditor: Clicking at the left of a wikicode block does not put the cursor there.,"@James: at this moment we don't have a way to select node yet, so I'm not sure what you are seeing.
+@Nicolas: we might not be able to find solution to this problem soon. However - you should be able to get in front of nowiki block by using your arrow keys.",1360363357,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-ncyndehe2estt3jwmggo,task_subcomment,NA
+VisualEditor: Clicking at the left of a wikicode block does not put the cursor there.,"Confirmed - instead, the nowiki'ed block is selected; the cursor appears to have its location updated though the caret isn't painted.",1350928425,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ncyndehe2estt3jwmggo,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"See https://www.mediawiki.org/w/index.php?title=VisualEditor:LinkTrailReEditBug&diff=594998&oldid=594997&vewhitelist
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350557700,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-stsksyo6vo24yafdejoq,task_description,resolved
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"mw.org is not running current master- it is still on the December code version. So this is to be expected. http://parsoid.wmflabs.org/ runs the latest code.
+
+We need to work out some issues with selective serialization before we can deploy a new version to the mw.org / enwiki backend. You'll see the fix for this bug in production after that deploy.",1360171044,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"(In reply to comment #6)
+> (In reply to comment #5)
+> > It was fixed by a rework of the link serializer I did earlier this month.
+> > That
+> > code is not yet deployed on mw.org. You can verify that it is fixed in
+> > Parsoid
+> > by following Roan's instructions in comment 2. You can also do
+> > 
+> > echo '<p><a href=""Foo"" rel=""mw:WikiLink"">foo</a></p>' | nodejs parse
+> > --html2wt
+> 
+> OK I'll retest it on Feb 4.
+
+Bug persists.
+
+https://www.mediawiki.org/w/index.php?title=VisualEditor:LinkTrailReEditBug&diff=641685&oldid=641684",1360146725,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"(In reply to comment #5)
+> It was fixed by a rework of the link serializer I did earlier this month.
+> That
+> code is not yet deployed on mw.org. You can verify that it is fixed in
+> Parsoid
+> by following Roan's instructions in comment 2. You can also do
+> 
+> echo '<p><a href=""Foo"" rel=""mw:WikiLink"">foo</a></p>' | nodejs parse
+> --html2wt
+
+OK I'll retest it on Feb 4.",1359427311,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"It was fixed by a rework of the link serializer I did earlier this month. That code is not yet deployed on mw.org. You can verify that it is fixed in Parsoid by following Roan's instructions in comment 2. You can also do
+
+echo '<p><a href=""Foo"" rel=""mw:WikiLink"">foo</a></p>' | nodejs parse --html2wt",1359426754,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"(In reply to comment #3)
+> Current output is [[foo]].
+
+I assume this was fixed a while ago because you didn't specify a commit.
+
+But this bug still exists on mw.org. See https://www.mediawiki.org/w/index.php?title=VisualEditor:LinkTrailReEditBug&diff=637012&oldid=637011
+
+I noticed that it's impossible to select a part of a word, click ""Edit link"", then trash the link (the whole word is unlinked instead), but it's still possible to select some characters, then click ""Clear formatting"" to unlink those characters.",1359423539,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,Current output is [[foo]].,1359411632,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,"This is a Parsoid bug.
+
+To reproduce: paste <p><a href=""Foo"" rel=""mw:WikiLink"">foo</a></p> into http://parsoid.wmflabs.org/_html/ . This should serialize to [[foo]], or maybe [[Foo|foo]], but not [[Foo]].",1354571718,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+Parsoid: Link targets and display are corrupted when removing annotations from part of the link,This is especially broken for the second and third case because stray characters are added.,1350557782,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-stsksyo6vo24yafdejoq,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","See [[mw:VisualEditor:ThisPageDoesNotExist]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1350557100,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-y6wx3bzrwdh7htuo432k,task_description,resolved
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong",Code now live in master.,1354565326,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","(In reply to comment #4)
+> (In reply to comment #3)
+> > Fixed in Id88a160621093e4db4cf01c0fa34793cc1a929b4.
+> 
+> Is it fixed in monobook too? 
+
+Yes, it looks fine for me in Monobook.",1354433584,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","(In reply to comment #3)
+> To reproduce this bug:
+> * Set $wgVectorUseIconWatch = true
+> * Log in (to have the ""watch"" right)
+> 
+> It is currently inserted before ""ca-history"". But on new pages there is no such
+> link, so it falls back to appending to the end.
+> 
+> Fixed in Id88a160621093e4db4cf01c0fa34793cc1a929b4.
+
+Is it fixed in monobook too? see comment 1.",1354432539,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","To reproduce this bug:
+* Set $wgVectorUseIconWatch = true
+* Log in (to have the ""watch"" right)
+
+It is currently inserted before ""ca-history"". But on new pages there is no such link, so it falls back to appending to the end.
+
+Fixed in Id88a160621093e4db4cf01c0fa34793cc1a929b4.",1354413186,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","For what it's worth, in Monobook it's even goofier.",1352956851,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+"VisualEditor: Position of VisualEditor's ""Create"" tab is wrong","Old summary: VisualEditor: Position of replacement Edit tab is wrong (to the right of 'Watch' (the star) rather than left)
+
+Updated summary: VisualEditor: Position of ""Create"" tab is wrong (to the right of 'Watch' [the star] rather than left)
+
+I believe the updated bug summary better reflects the issue in this bug.",1352956815,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-y6wx3bzrwdh7htuo432k,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,"It might be impossible to implement, but I am sure many users will wonder why it does not work, so here is the idea:
+
+1) Select some text with the mouse
+2) Press the mouse over the selected text
+3) While staying pressed, move the mouse to somewhere else, then release the mouse button.
+
+Expected: The text is cut-pasted from origin to destination.
+Actual: Nothing happens.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350544500,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-qfmwammnoff7cszevjw6,task_description,resolved
+VisualEditor: Click-dragging of media items to move them,"Images drag-and-drop positioning is now merged (in gerrit 69279) and will go live shortly; for non-media items, I've split that off as bug 49981, and am closing this.",1371851883,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,Gerrit 69279 is drag-and-drop moving for images.,1371587614,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,What's the movement on this? Not trying to rush you guys - we have some users wondering :).,1371206697,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,*** Bug 49486 has been marked as a duplicate of this bug. ***,1371058332,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,"I can see that work has started on this, with the mouse cursor changing to a ""move that item"" cursor, and the text caret trying to follow it (despite having some trouble at it sometimes).
+The text does not get moved yet, but I guess the issue is progressing :-)",1366963980,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,Probably possible (at least in Chrome and Firefox).,1360363728,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+VisualEditor: Click-dragging of media items to move them,"Good catch as an expected editing mode; in other examples of this, it could work as either a ""live"" cut-and-paste, or just flashing a caret where the new content would go.",1350580555,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qfmwammnoff7cszevjw6,task_subcomment,NA
+"VisualEditor: Add support for adding dir/lang attributes to paragraphs and similar arbitrary elements (div, p, lists etc.)","In MediaWiki pages it is frequently required to write some text in a different languages, and possibly also with different directionality. For example, an quotation in English in an article in the Hebrew Wikipedia.
+
+With the plain wikitext editor this can be achieved using HTML, for example <span lang=""en"" dir=""ltr"">. In some Wikipedias there are templates that do this.
+
+There must be a way to do this using the VE GUI. For example, the user can select the text in a different language, open a dialog with ""Language properties"" and select ""English language"" and ""Directionality: Left-to-right"".
+
+For reference and further details:
+https://www.mediawiki.org/wiki/VisualEditor/Bidirectional_text_requirements
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350148140,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-o7xyvob3g2jy33fpbism,task_description,open
+"VisualEditor: Add support for adding dir/lang attributes to paragraphs and similar arbitrary elements (div, p, lists etc.)",<span> is done. Reopening for <div>.,1375256608,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-o7xyvob3g2jy33fpbism,task_subcomment,NA
+"VisualEditor: Add support for adding dir/lang attributes to paragraphs and similar arbitrary elements (div, p, lists etc.)","
+
+*** This bug has been marked as a duplicate of bug 47759 ***",1373002468,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o7xyvob3g2jy33fpbism,task_subcomment,NA
+"VisualEditor: Add support for adding dir/lang attributes to paragraphs and similar arbitrary elements (div, p, lists etc.)",*** Bug 41010 has been marked as a duplicate of this bug. ***,1350158076,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-o7xyvob3g2jy33fpbism,task_subcomment,NA
+"VisualEditor: Only show minor edit option if user has ""minoredit"" right","Right now the ""This is a [minor edit]"" text in the save dialog appears whether or not you are logged in, which is incorrect behaviour compared to the current editor's save process, and is meaningless (anons can't have edits marked as minor).
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1349380320,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hyy5m6djppnbb3qc32pu,task_description,resolved
+"VisualEditor: Only show minor edit option if user has ""minoredit"" right",Landed in master.,1354577109,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-hyy5m6djppnbb3qc32pu,task_subcomment,NA
+"VisualEditor: Only show minor edit option if user has ""minoredit"" right",Change-Id: Ie09bb5c8bdbfbb3ec0d4983b74d0697b941153e0,1354419900,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-hyy5m6djppnbb3qc32pu,task_subcomment,NA
+"VisualEditor: Only show minor edit option if user has ""minoredit"" right",This is integration more than UI.,1353015719,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hyy5m6djppnbb3qc32pu,task_subcomment,NA
+VisualEditor: Link inspector: Width of suggested titles too short,"The width of suggested titles in the link inspector is too short for practical purposes, see: http://imgur.com/cJEnn
+
+In production wikis like en.wp this will be an issue with titles that are long and hard to disambiguate, e.g. ""List of countries by GDP (nominal) per capita"" vs. ""List of countries by GDP (PPP) per capita"", which would both be abbreviated to ""List of cou...per capita"".
+
+Perhaps the dropdown could dynamically expand in a similar manner to the search box suggestions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1349129640,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-evrtetuy2zbr3a7t4zhq,task_description,resolved
+VisualEditor: Link inspector: Width of suggested titles too short,"Styled suggestion dropdown into a single column which is a much more space conscious approach for displaying longer page titles vs the two column.
+
+Changed in https://gerrit.wikimedia.org/r/36227
+
+Possible enhancement:
+Some additional room could be gained for long titles within a specific namespace by grouping suggestions by namespace and trimming the namespace from the titles.   The label for that group would indicate the namespace for the suggested page.",1354305102,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-evrtetuy2zbr3a7t4zhq,task_subcomment,NA
+VisualEditor: High-res icons don't display if small screen is resized to large,"Broken out from bug 37849: window.devicePixelRatio is checked when loading stuff, and then either a stylesheet for 1.0x PNGs or one using scalable SVGs gets loaded depending on the ratio.
+
+This leads to being stuck with the 1.0x PNGs if you started editing on a low-resolution screen, then moved the window (or detached an external monitor) and moved it to a high-resolution screen.
+
+Per bug 37849 comment 9 there are probably two ways to fix this:
+
+1) Detect resolution changes (window.onresize?) and switch the stylesheet based on the updated window.devicePixelRatio
+
+or
+
+2) Always use SVG icon set if SVG is supported in the browser.
+
+Note that Firefox doesn't yet support window.devicePixelRatio, but it's about to come in in nightlies, before actual HiDPI support for Mac OS X :) -- https://bugzilla.mozilla.org/show_bug.cgi?id=564815
+
+IE 10 doesn't support window.devicePixelRatio at all, which is a bit annoying although it does support SVG and high-resolution screens eg on Windows 8. We can leave that as a corner case for the moment, though use of SVG at all resolutions would conveniently work around it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1347307920,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-yssbwa6yqsenmbrxptpp,task_description,invalid
+VisualEditor: High-res icons don't display if small screen is resized to large,"This is now invalid, as we actually provide the SVGs by default to every browser that doesn't fail on them (yay).",1368811438,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yssbwa6yqsenmbrxptpp,task_subcomment,NA
+VisualEditor: High-res icons don't display if small screen is resized to large,Mark as enhancement; this is nothing like a priority ahead of December. :-),1349115924,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yssbwa6yqsenmbrxptpp,task_subcomment,NA
+VisualEditor: High-res icons don't display if small screen is resized to large,"Keywords spam: High-density HiDPI Retina toolbar icons don't display if window opened on low-res screen, then moved to high-res.",1347385994,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yssbwa6yqsenmbrxptpp,task_subcomment,NA
+"VisualEditor: Links in the CE surface should have the ""cursor:pointer;"" CSS attribute","Suggested by a user.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1346774040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-a3lcwcpnaonnbhuser76,task_description,declined
+"VisualEditor: Links in the CE surface should have the ""cursor:pointer;"" CSS attribute","(In reply to comment #2)
+> A pointer implies that clicking will follow the link, when in fact it places
+> a text cursor, hence cursor:text (as it is) is more appropriate. Both LO/OO
+> and Google Docs use cursor:text for links.
+> 
+> WONTFIX unless I have misunderstood the point.
+
+Agreed.",1380214425,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-a3lcwcpnaonnbhuser76,task_subcomment,NA
+"VisualEditor: Links in the CE surface should have the ""cursor:pointer;"" CSS attribute","A pointer implies that clicking will follow the link, when in fact it places a text cursor, hence cursor:text (as it is) is more appropriate. Both LO/OO and Google Docs use cursor:text for links.
+
+WONTFIX unless I have misunderstood the point.",1380200003,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-a3lcwcpnaonnbhuser76,task_subcomment,NA
+"VisualEditor: Links in the CE surface should have the ""cursor:pointer;"" CSS attribute",Clarifying - I think this was meant to be about links in the CE surface rather than in the link inspector in any way.,1354669539,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-a3lcwcpnaonnbhuser76,task_subcomment,NA
+Scap doesn't build use correct extension versions on deployment of new versions,"I've been noticing this for a while, but I'm not quite sure why...
+
+I have put in a copy of the ExtensionMessages file from the old version to the newer one, but that uses $IP...
+
+
+On the first run of scap after adding a new version, we get a weird output:
+
+Updating ExtensionMessages-1.20wmf10.php...
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeEditor/CodeEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPage/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/E3Experiments/Experiments.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Echo/Echo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EducationProgram/EducationProgram.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GeoData/GeoData.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Interwiki/Interwiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LastModified/LastModified.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MwEmbedSupport/MwEmbedSupport.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PageTriage/PageTriage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RandomRootPage/Randomrootpage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Renameuser/Renameuser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Scribunto/Scribunto.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TimedMediaHandler/TimedMediaHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TranslationNotifications/TranslationNotifications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaIncubator/WikimediaIncubator.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaShopLink/WikimediaShopLink.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+Updating LocalisationCache for 1.20wmf10... done
+Updating ExtensionMessages-1.20wmf11.php...
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeEditor/CodeEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPage/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/E3Experiments/Experiments.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Echo/Echo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EducationProgram/EducationProgram.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GeoData/GeoData.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Interwiki/Interwiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LastModified/LastModified.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MwEmbedSupport/MwEmbedSupport.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PageTriage/PageTriage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RandomRootPage/Randomrootpage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Renameuser/Renameuser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Scribunto/Scribunto.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TimedMediaHandler/TimedMediaHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TranslationNotifications/TranslationNotifications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaIncubator/WikimediaIncubator.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaShopLink/WikimediaShopLink.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+Updating LocalisationCache for 1.20wmf11... done
+
+
+
+Upon the second run, it seems to work fine (but necessitates 2 runs of scap)..
+
+Will post output when I get round to it
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1346688240,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-e6xtogl4rredgvs524aw,task_description,resolved
+Scap doesn't build use correct extension versions on deployment of new versions,"Obsolete somewhat. I'm not sure whether it's specifically ""fixed"", but I've got a way of doing it so I only need to run it once",1357150957,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-e6xtogl4rredgvs524aw,task_subcomment,NA
+Scap doesn't build use correct extension versions on deployment of new versions,Reedy: Is that still an issue or is this obsolete now?,1356115303,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-e6xtogl4rredgvs524aw,task_subcomment,NA
+Scap doesn't build use correct extension versions on deployment of new versions,"reedy@fenari:/home/wikipedia/common$ scap rebuild 1.20wmf11 localisation cache
+Checking syntax...
+Copying to fenari...ok
+MediaWiki 1.20wmf10: Compiling texvc...ok
+MediaWiki 1.20wmf11: Compiling texvc...ok
+Done
+Updating ExtensionMessages-1.20wmf10.php...
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeEditor/CodeEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPage/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/E3Experiments/Experiments.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Echo/Echo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EducationProgram/EducationProgram.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GeoData/GeoData.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Interwiki/Interwiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LastModified/LastModified.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MwEmbedSupport/MwEmbedSupport.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PageTriage/PageTriage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RandomRootPage/Randomrootpage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Renameuser/Renameuser.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Scribunto/Scribunto.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TimedMediaHandler/TimedMediaHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TranslationNotifications/TranslationNotifications.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaIncubator/WikimediaIncubator.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaShopLink/WikimediaShopLink.php
+Loading data from /home/wikipedia/common/php-1.20wmf10/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+Updating LocalisationCache for 1.20wmf10... done
+Updating ExtensionMessages-1.20wmf11.php...
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CodeEditor/CodeEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ContactPage/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/E3Experiments/Experiments.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Echo/Echo.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/EducationProgram/EducationProgram.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/GeoData/GeoData.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Interwiki/Interwiki.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LastModified/LastModified.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MwEmbedSupport/MwEmbedSupport.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/PageTriage/PageTriage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/RandomRootPage/Randomrootpage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Renameuser/Renameuser.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Scribunto/Scribunto.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TimedMediaHandler/TimedMediaHandler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TranslationNotifications/TranslationNotifications.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikimediaIncubator/WikimediaIncubator.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/WikimediaShopLink/WikimediaShopLink.php
+Loading data from /home/wikipedia/common/php-1.20wmf11/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+Updating LocalisationCache for 1.20wmf11... done",1346692642,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-e6xtogl4rredgvs524aw,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1345842600,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_description,resolved
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"This has now (finally!) OK to merge, and has been.",1375140242,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"Change 69856 merged by jenkins-bot:
+Use postEdit mw.hook for save notifications
+
+https://gerrit.wikimedia.org/r/69856",1375140192,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"Change 69855 merged by jenkins-bot:
+Allow postEdit hook to be triggered asynchronously
+
+https://gerrit.wikimedia.org/r/69855",1373927497,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"**swalling** wrote:
+
+%%%*** Bug 50642 has been marked as a duplicate of this bug. ***%%%",1372834231,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),Related URL: https://gerrit.wikimedia.org/r/69856 (Gerrit Change Id4a8bc22c09a552ef79670b0d4fc4a70df07ec33),1371818834,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),Related URL: https://gerrit.wikimedia.org/r/69855 (Gerrit Change I778b18bc051c51de355e122d8d4517b5a651ed4c),1371818082,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"(In reply to comment #8)
+> In VE, saving an edit does not cause you to reload the page, so we
+> can't use the mechanism.
+
+It would only require a very modest refactoring to make the 'postEdit' hook triggerable by VE.",1371661499,PHID-USER-r7wrkcx7j2vutqs6hr3g,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"Looking at the code
+
+https://git.wikimedia.org/blob/mediawiki%2Fcore.git/HEAD/resources%2Fmediawiki.action%2Fmediawiki.action.view.postEdit.js
+
+it appears this extension is not designed to work asynchronously. It expects a cookie to have been set, then fires immediately on page load. In VE, saving an edit does not cause you to reload the page, so we can't use the mechanism.",1371643840,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),*** Bug 43091 has been marked as a duplicate of this bug. ***,1368638967,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"OK, after talking with Steven, [[mw:Extension:PostEdit]] is going to be moved in MW core at which point we can depend on it, and not re-implement the wheel. This means that users will get the same styling and text of messages whether they save via the wikitext editor or VisualEditor; yay.",1368050225,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"I agree 100% that we need a notification and I'm glad that there was some testing that went into it. VisualEditor currently uses the notification bubble stuff in MediaWiki for this, and I think it's an especially good example of a place where it's needed because the save occurs without very much else changing on the page (not even going to a different URL)
+
+Thank you for the clarification, I wanted to make sure we didn't have people changing the notification styles to match that until we had considered a few things first.",1348079663,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"**swalling** wrote:
+
+(In reply to comment #3)
+> Can you expand on ""previously A/B tested""?
+
+I don't want to replicate the entirety of the documentation here on Bugzilla. See the Meta link above for all details, and especially the results subpage. 
+
+The summary is that we tested this for all new registered editors on English Wikipedia for two weeks. The simple confirmation we're suggesting be implemented was the most successful when looking at  a variety of metrics, from sheer volume of edits to quality indicators like revert rates. 
+ 
+> This design is nice, but completely out of place.
+
+To be clear here: I'm _not_ suggesting this exact design be implemented in VisualEditor. I just provided the screengrab so you wouldn't have to guess what the previously tested version looked like. :) 
+ 
+> 1. That is not a safe location to put a notification because it may obscure
+> navigation controls.
+> 2. The size is out of proportion with the rest of the UI
+> 3. The colors and shading are out of sync with the rest of the UI
+> 
+> I would like to see us make notifications work together with the skin, not just
+> succeed at getting people's attention because they are sufficiently loud.
+> Blending in can be detrimental to the function of a notification, but making it
+> look out of place just causes other problems.
+
+I'm not sure if your critique is in the context of the current editor or only VisualEditor, but in addition to my comment above, I'd like to reiterate that this was an experiment, not a permanent implementation. The question we asked was: does it make a measurable difference to new editors to get a confirmation? The answer is a resounding yes. 
+
+To respond on the first point: it didn't much matter that it obscures navigation, because in our implementation of the attached design, it only persists on screen for three seconds.",1348078664,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"Can you expand on ""previously A/B tested""?
+
+This design is nice, but completely out of place.
+
+1. That is not a safe location to put a notification because it may obscure navigation controls.
+2. The size is out of proportion with the rest of the UI
+3. The colors and shading are out of sync with the rest of the UI
+
+I would like to see us make notifications work together with the skin, not just succeed at getting people's attention because they are sufficiently loud. Blending in can be detrimental to the function of a notification, but making it look out of place just causes other problems.",1348077585,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"**swalling** wrote:
+
+Confirmation previously A/B tested
+
+**Attached**: {F10123}",1348004857,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified),"**swalling** wrote:
+
+To follow up on this:
+
+* We've got requirements and implementation ideas for the current state of the editing experience: https://www.mediawiki.org/wiki/Confirmation_message
+* A/B testing documentation, including results and data: https://meta.wikimedia.org/wiki/Research:Post-edit_feedback
+
+Consistent confirmation messages are a pretty obvious usability enhancement for an editor, especially one where the update to a page is not always visually obvious. When we A/B tested this against a control and variant of the text, a plain ""your edit was saved"" with the design described in the links led to a significant increase in the productivity of new editors. 
+
+I've listed some requirements for incorporating this into MediaWiki as it exists, but haven't specified anything for VisualEditor. I would say that the essential elements for either system is that it included an icon, the text we tested, and that it is visible when editing any part of the page (i.e. it's not hidden if a section anchor is present).",1348004754,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-mwak57g5crp4aezvpr7x,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Depends on VisualEditor having a (stable) API. As soon as it is considered stable enough, we can implement support for it in the Cite extension using whatever hook/api it offers.
+
+Also needs detection since there are (obviously) wikis that have Cite but not VisualEditor. So probably some conditionally loaded module.",1345821600,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-q7nnm3osibolbwwipfib,task_description,resolved
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Change 254041 merged by jenkins-bot:
+VisualEditor: Move code for Cite into this repo
+
+[[https://gerrit.wikimedia.org/r/254041]]",1454605559,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Change 254041 had a related patch set uploaded (by Jforrester):
+[WIP] Move VisualEditor code for Cite into this repo
+
+[[https://gerrit.wikimedia.org/r/254041]]
+",1447901269,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Change 248014 merged by jenkins-bot:
+References: Don't load ext.visualEditor.mwreference if Cite is not installed
+
+[[https://gerrit.wikimedia.org/r/248014]]",1445527977,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Change 248014 had a related patch set uploaded (by Esanders):
+References: Don't load ext.visualEditor.mwreference if Cite is not installed
+
+[[https://gerrit.wikimedia.org/r/248014]]
+",1445510346,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,Re-prioritising.,1403630802,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"(In reply to Andre Klapper from comment #3)
+> In Bug 13127 comment 34 anomie wrote
+> ""Since Parsoid has reimplemented the Cite extension in their own code, any
+> fixes to Cite are going to be very difficult to get merged unless someone
+> wants to do all the work twice, once in PHP and once in nodejs.""
+
+That's a totally different issue about Parsoid's Cite vs Cite.php; this bug is about the location of code currently in the VisualEditor-MediaWiki repo that should be moved to the Cite extension's repository, like we did for <math> etc. Not sure if there's a bug about that?
+
+
+> James: Quim wondered if this means that all Cite bugs.docs can be eventually
+> and officially deprecated.
+
+That's a question for the mythical other bug (but I'd say no).
+
+
+> Any vague timeframe for this ticket, assuming that Trevor still works on
+> this?
+
+I'd want it to settle down a little more before the code was transitioned, but probably in a few months' time.",1399054655,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"In Bug 13127 comment 34 anomie wrote
+""Since Parsoid has reimplemented the Cite extension in their own code, any fixes to Cite are going to be very difficult to get merged unless someone wants to do all the work twice, once in PHP and once in nodejs.""
+
+James: Quim wondered if this means that all Cite bugs.docs can be eventually and officially deprecated.
+
+Any vague timeframe for this ticket, assuming that Trevor still works on this?",1399036675,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"Adding 'javascript' keyword, because I think this is JavaScript related...",1364291788,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+Refactor VisualEditor editing plugin for Cite back into the Cite extension,"After discussion with Timo, clarifying what this is.",1364248542,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q7nnm3osibolbwwipfib,task_subcomment,NA
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"See module's code at https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/WikiEditor.git;a=blob;f=modules/jquery.wikiEditor.dialogs.config.js;h=76a3a57e27b6b7d87266171c26baf2a82d9f703a;hb=e7a0484eb56d72e5326282a54288580fdfcd144f
+
+The if conditions at lines 201 and 203 must probably be corrected.
+
+from :  if ( page.missing )
+to   :  if ( page.missing !== undefined )
+
+and
+
+from :  if ( page.invalid )
+to   :  if ( page.invalid !== undefined )
+
+This code checks the api query result,
+which, for instance, has
+    page.missing === """"
+if queried title doesn't exist.
+
+As it is, the ""Insert link"" dialog shows ""Page exists""
+for every title inserted in the ""Target page or URL:"" field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344312120,PHID-USER-6dh2mmgw4sia7dmkixtb,False,PHID-TASK-xwuorocthdcw4tqbqq2f,task_description,resolved
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"Thank you!
+
+Next time, I'll try to search a bit more, before entering a bug.",1344442901,PHID-USER-6dh2mmgw4sia7dmkixtb,False,PHID-TASK-xwuorocthdcw4tqbqq2f,task_subcomment,NA
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"This has already been fixed and was merged in July 31st.  
+https://gerrit.wikimedia.org/r/#/c/17019/",1344362215,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-xwuorocthdcw4tqbqq2f,task_subcomment,NA
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"We also encountered this bug in the VisualEditor.
+
+Assigning to Rob who already fixed this in VisualEditor, we should be able to
+apply the same fix to WikiEditor.",1344312908,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xwuorocthdcw4tqbqq2f,task_subcomment,NA
+jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy,"(In reply to comment #0)
+
+Sorry for the link. I split the server part, so that could be read.
+
+https://gerrit.wikimedia.org
+
+/r/gitweb?p=mediawiki/extensions/WikiEditor.git;a=blob;f=modules/jquery.wikiEditor.dialogs.config.js;h=76a3a57e27b6b7d87266171c26baf2a82d9f703a;hb=e7a0484eb56d72e5326282a54288580fdfcd144f",1344312646,PHID-USER-6dh2mmgw4sia7dmkixtb,False,PHID-TASK-xwuorocthdcw4tqbqq2f,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","To reproduce, go to http://www.mediawiki.org/wiki/VisualEditor:Sandbox?veaction=edit , blank the page, save, then you get ""Error saving data to server: ..."" without too much explaination.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50475
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43147
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63149",1344201000,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_description,open
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","I agree that ""Something went wrong"" isn't very helpful.  What would be helpful is an explanation of what to do.  For example, if it's hopeless and you've just lost all of your work, then acknowledging that it's hopeless would save people the time and stress of trying to save it.",1438467773,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","For what is worth, Catalan Viquipedia users confused about an error message from Parsoid:
+
+  Alguna cosa no ha funcionat
+
+  parsoidserver-http: HTTP 500
+
+  Descarta
+
+""Something didn't work""  :)
+
+https://ca.wikipedia.org/wiki/Topic:Shssmsofmcgkqhmv",1432706998,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","I just hit this message (was about to reported a semi-dupe) on enwiki. I got the below variant:
+
+```
+Error loading data from server: parsoidserver-http-bad-status:
+404: No pages were returned from the API request for $article.
+Would you like to retry?"" (yes/no)
+```
+
+I hit yes and it worked. So... why not just retry without asking me first?
+
+If it fails again (or for X times, whatever) then give a more generalized ""ooops, sorry 'bout that"" message with a ""click here for more info"" dropdown (with the message I just pasted, minus the ""would you like to retry?"" bit, of course).",1419389820,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","With the above patch, the former message:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500. Would you like to retry?
+
+… turns into:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500: Page Fetch failure for ""BADURL"": Error: getaddrinfo
+    ENOTFOUND. Would you like to retry?
+
+Which is not ideal, but at least describes things a bit.",1409684371,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","Change 157775 merged by jenkins-bot:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409681806,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","Change 157775 had a related patch set uploaded by Jforrester:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409669828,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","Perhaps call it the ""editing server""? As in ""Sorry, we could not save your changes to the editing server"" and ""Sorry, we could not get a copy of the page from the editing server"" etc.?",1345759375,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved","I'm not really sure what else the message should say. If we talk about parsoid, the user will be pretty confused. Are there any suggestions?",1345756907,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-scyl7lhkpp7vgev5i5sy,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"**Author:** `jack`
+
+**Description:**
+Sometimes, it is necessary to fully protect a page which is already semi-protected. Often, the reason for the different protections is different (vandalism and edit warring is a common example), and will have different expiry times. However, if I choose to fully protect a page for a short amount of time, any semi-protection that is set to last longer (or indefinitely) will be erased. It would be helpful if full and semi protection could operate independently of one another, so that a week of full protection would not affect a month of semi-protection.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1344094140,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_description,duplicate
+Full protection expiry should not affect semi-protection,"The other shouldn't have been done by its lonesome, but yes, they probably should be merged at this point.",1731696684,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,See https://meta.wikimedia.org/wiki/Community_Wishlist/Wishes/Restore_long_term_protection_when_short_term_protection_expires for a Wishlist item covering this request.,1731668353,PHID-USER-ksxcfwf6vvnfvopbps4h,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,It looks like {T142209} has more details and discussion about how this could be implemented - any concerns with me merging this task into that one? As I understand it they're the same proposal.,1731668106,PHID-USER-ksxcfwf6vvnfvopbps4h,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"Simply allowing multiple, overlapping protections on a page would solve for this and other use cases. ",1725209723,PHID-USER-7rhaupbuiqkqvy5zashf,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"Instead of semiprotection being restored after temporary full protection expires, ANY longer-term protection should be restored when ANY shorter-term protection expires. That way full protection could fall back to an already existing ECP or semi, or ECP protection could fall back to an already-existing  semiprotection.
+
+Automatic restoring of prior protections might be more manageable by a bot, however.",1725209199,PHID-USER-rkee2nybd3w4nkcil7cf,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"I wrote today on meta (https://meta.wikimedia.org/w/index.php?title=User_talk:TBolliger_(WMF)&diff=18279440&oldid=17799915 ) folllowing text, not knowing of this feature request:
+
+---
+
+̈́`Disclaimer`: ... in last 10 years I saw a lot of mediawiki tinkering which surely spent a lot of man-hours, really man-years and not so much of improvement to end users, meaning Wikipedia volunteers.
+
+https://meta.wikimedia.org/wiki/Community_health_initiative/Per-user_page,_namespace,_and_upload_blocking - This is the first really good idea **I saw** in years, and now //I think// I have an idea for another one good improvement.
+
+* **Description of problem/current mediawiki behavior**: after lock of page expires, page is unlocked, meaning - no protection at all.
+* **Description of wanted mediawiki behavior**: after lock of page to sysop level (full protection) expires, page should either go to **previous** level of protection (e.g. semi-protected), if such exists, or it should be possible to set next protection state of page after full protection expires, when locking the page to set period of time.
+** **Comments**: temporary solution could be using the bot with sysop flag with accompanying tasklist page (list of pages that should be protected at which times).
+** **Answer to above comment**: that is not good software design. It should be designed better, smarter, in the first place. (//Yeah, right.// :)
+
+Maybe this idea already is written somewhere, maybe not. I have no clue. But it's written here and now.
+
+---
+
+Well, I'm glad that this feature request already exist, as that shows that other people also thought about this. I'm not glad about priority of this feature, because, IMO, this needed to be done long before VisualEditor was even first thought of. :)
+
+I copy-pasted this to let everybody know that maybe powers that decide what is important and what isn't ignored this feature request by chance, as there are lot of feature requests already. This is not critical, but implementing this could spare sysops and patrollers some time, and plug one hole in mediawiki by smart design.",1533678395,PHID-USER-3hahyxmftu2sew3v6v6w,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"(In reply to Technical 13 from comment #4)
+> Technically, I think to implement this, each protection level would have to
+> be given it's own column in the table with an expiration date
+
+That's not actually how the existing page_restrictions table is structured.
+
+What would probably have to happen is that they unique index would have to change from (pr_page,pr_type) to (pr_page,pr_type,pr_level). And then various bits of code would need to be adjusted to deal with this.
+
+> and the highest level of non-expired protection would be applied.
+
+It's not necessarily possible to decide that one protection level is ""higher"" than another. For example, you probably know that enwiki created a new ""templateeditor"" protection level. What if enwiki decided they also wanted a special protection level for policy pages, and created a ""policyeditor"" protection level.[1] Which would be higher, ""templateeditor"" or ""policyeditor""?
+
+So what would have to happen is that a page with multiple protection levels active at once could be edited only by editors who could edit through each protection level individually.
+
+There does seem to already be some support along these lines in the code, for example Title::getRestrictions() is defined to return an array of restrictions and Title::checkPageRestrictions() checks whether the user is allowed to edit through all of them. But I don't know for sure whether everything everywhere will correctly handle it.
+
+And despite Title handling multiple restriction levels for an action, there's doesn't seem to be support for the different restriction levels expiring at different times (e.g. Title::getRestrictionExpiry() assumes there's only one relevant time). And then there are the UI issues too, with making a sensible protection form dealing with different restriction levels expiring at different times.
+
+
+ [1]: Yes, this example is *incredibly* unlikely. But it illustrates the point.",1392304060,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"Technically, I think to implement this, each protection level would have to be given it's own column in the table with an expiration date and the highest level of non-expired protection would be applied.  I'm not sure how hard it would be to implement, but think it is a good idea.",1392264323,PHID-USER-qgqq35kbi5wss2tlgmhg,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"**cu.faoil.wp** wrote:
+
+I would also like to see this implemented (sysop on German language wiki). There are many pages that are prone to vandalism and should be semiprotected by default, so it would be good to be able to specify whether the page should go back to being semiprotected or not when setting it to be fully protected for any amount of time.",1353350414,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,This would be nice :). Not sure how it'd work (or if it's possible without a lot of effort) but I'm verifying the enhancement.,1345886882,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Full protection expiry should not affect semi-protection,"**davidswikipediaemail** wrote:
+
+It would definitely be nice if this could be fixed. I'm not an admin, but I could see where this could be problematic.",1344895736,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ciiqin6dnqycnrlibykn,task_subcomment,NA
+Bugzilla products could use a re-examination,"The current set of Bugzilla products doesn't make any sense to me. It's a hodgepodge of arbitrary projects, extensions, and other vague or broad categories. It'd be nice to rearrange the products to be a bit more sane. This will help bug filers and developers alike.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://bugzilla.wikimedia.org/enter_bug.cgi
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43459
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53986",1343952060,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_description,declined
+Bugzilla products could use a re-examination,"Wikimedia has migrated from Bugzilla to Phabricator. Learn more about it here: https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla - This task does not make sense anymore in the concept of Phabricator, hence closing as declined.",1416786026,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,s/malicious/pernicious/ (a comment on #mediawiki confirmed my suspicion that the inaccurate translation of the Italian word I had in mind is... pernicious).,1381953881,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"I'm adding bug 55807 as blocker, because that bug adds a malicious incentive to this organisational antipattern.",1381953374,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #15)
+> Low hanging fruit? What about moving all the Wikimedia mobile apps under a
+> same
+> umbrella called ""Wikimedia mobile apps"":
+> 
+> * Commons App
+> * Wiki Loves Monuments
+> * Wikipedia App
+
++1. We already did this once! See bug 41922.",1379955370,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"Low hanging fruit? What about moving all the Wikimedia mobile apps under a same umbrella called ""Wikimedia mobile apps"":
+
+* Commons App
+* Wiki Loves Monuments
+* Wikipedia App",1379955103,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #8)
+> I'm gonna go ahead and mark this bug as easy. It really just needs someone to
+> sit down and figure out/write down a sensible hierarchy at
+> <https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy> and
+> then get it implemented (or implement it themselves, if a current Bugzilla
+> admin takes this on). That shouldn't be very difficult to do.
+
+You misunderstood the meaning of the ""easy"" keyword. This keyword is for new developers, to find bugs to start their first commits. While ""writting a list"" is easy, the problem is ""figuring out"" what to put on that list, and a new developer is definitively not the right person to do that. Removing keyword.",1379092634,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #12)
+> For specific cases yes, however we're not after creating pieces of cake that
+> have the same sizes (components with approx. the same amount of bug reports,
+> products with approx. the same amount of components), but after a useful
+> structure that is a good compromise between development teams' areas and
+> reporters finding the right place. :)
+
+Of course! Thanks to your report and stealing some things from comment 10, I've expanded [[mw:Requests_for_comment/Bugzilla_taxonomy]]; this should also clarify other idea I expressed above.",1352477317,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #11)
+> (In reply to comment #4)
+> We also have products which then have only a single component, e.g. the ""* App""
+> products (which are very messy).
+
+What exactly is messy about the *App products?
+
+> (In reply to comment #10)
+> is someone able to generate some compact chart with, ideally, a
+> tree of all products and their components, each with its number of bugs?
+
+Not easily. Once https://bugzilla.mozilla.org/show_bug.cgi?id=385643 gets fixed (Bugzilla 4.4/4.6) it wouldn't show the number of reports.
+
+Huge product×component table for *open* tickets only: 
+https://bugzilla.wikimedia.org/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Analytics&product=CiviCRM&product=Commons+App&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s+Tools&product=Logwood&product=MediaWiki&product=MediaWiki+extensions&product=Monuments+database&product=mwEmbed&product=Parsoid&product=Security&product=Spam&product=Tools&product=VisualEditor&product=WikiLoves+Monuments+Mobile&product=Wikimedia&product=Wikimedia+Labs&product=Wikimedia+Mobile&product=Wikipedia+App&product=Wikisource+App&product=Wiktionary+App&product=Wiktionary+tools&resolution=---&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap
+
+> Products without components can probably be merged as components of a single
+> products, huge components could be split, etc.
+
+For specific cases yes, however we're not after creating pieces of cake that have the same sizes (components with approx. the same amount of bug reports, products with approx. the same amount of components), but after a useful structure that is a good compromise between development teams' areas and reporters finding the right place. :)",1352471913,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #4)
+> The reason was people wanted to be able to have components, which you can't do
+> when an extension is already a component.
+
+We also have products which then have only a single component, e.g. the ""* App"" products (which are very messy).
+
+(In reply to comment #10)
+> MW components have many too labels that are very specific, sometimes the more
+> general component exists, sometimes it doesn't.
+
+To start with, is someone able to generate some compact chart with, ideally, a tree of all products and their components, each with its number of bugs?
+Products without components can probably be merged as components of a single products, huge components could be split, etc. It's really hard to move <s>tanks</s> bullets in https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy without seeing the Risk! map.",1352470858,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"MW components have many too labels that are very specific, sometimes the more general component exists, sometimes it doesn't. Some examples:
+* DjVU 
+* change tagging
+* contenthandler
+* Page (editing|deleting|protection)
+* patrolling
+* redirects
+* resource loader
+* templates
+* user blocking
+
+Some components I think there should be:
+* Parser
+* Content handling related (various actions, diffs, etc)
+* User related
+* Scripts, styles and images (aka ResourceLoader)
+* Logging & history & recent changes
+* Unit tests
+* Maintenance scripts
+* Special pages
+* Language (I18n & l10n)
+* File handling
+* Skins",1349880111,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"For planning the structure you are certainly right, but the actual implementation part requires quite some preparation and planning (mostly because of limitations in Bugzilla).
+Only one example: Massmoving reports from one product to another requires exactly the same Versions / Target Milestones to exist for both products beforehand. Without that you cannot massmove (plus you would lose information). Other option in this case is to split up the reports in several sets with the same Version info and then to massmove each set, but that also takes time.
+
+Adding this comment as I planned and implemented a complete product / component reorg in a Bugzilla 2.22 instance of similar size (amount of bug reports) three years ago, and it took weeks of planning (though not full-time). Maybe Bugzilla 4.x has seen some improvements though in this area - haven't checked lately.",1347375464,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"I'm gonna go ahead and mark this bug as easy. It really just needs someone to sit down and figure out/write down a sensible hierarchy at <https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy> and then get it implemented (or implement it themselves, if a current Bugzilla admin takes this on). That shouldn't be very difficult to do. And don't worry: if you start on this project and head in the wrong direction, people will quickly speak up. :-)",1347333069,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #5)
+> I'm unclear how the use of categories would impact the bug-filing workflow. I
+> guess it would just add an additional click-through step?
+
+Bug filing:
+https://bugzilla.wikimedia.org/enter_bug.cgi would not show the available products as the very first page, but instead the available categories. The products of the chosen classification are listed on the (then) second page.
+
+Bug searching:
+https://bugzilla.wikimedia.org/query.cgi would show an additional list of classifications left to the current list of products.
+
+Bug viewing:
+https://bugzilla.wikimedia.org/show_bug.cgi is not affected.",1344443924,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy,1344289541,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #4)
+> I've said it before and I'll say it again: we need to move them up a level,
+> making extensions a category, individual extensions as products, which then
+> allows them to have components.
+
+I just clarified with Chad that we don't use categories currently, for those wondering.
+
+I'm unclear how the use of categories would impact the bug-filing workflow. I guess it would just add an additional click-through step?",1344289187,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"(In reply to comment #2)
+> I agree. Why are Visual editor, Huggle, mwEmbed products, Various mobile things
+> products? Visual editor should be considered an extension to start with, etc.
+> 
+
+The reason was people wanted to be able to have components, which you can't do when an extension is already a component.
+
+I've said it before and I'll say it again: we need to move them up a level, making extensions a category, individual extensions as products, which then allows them to have components.",1344271523,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"There is another abstraction level which is currently not in use in Mediawiki Bugzilla: Classifications (a product can be part of one classification). 
+Not that I propose using it here, just FYI.
+
+From an ""expectations"" point of view I personally wonder which extensions are ""3rd party / community"" ones and which ones are ""official"", assuming that it might make a difference in response times on reports, etc (as volunteers have a higher fluctuation rate and abandoning maintainership feels more likely).",1344252877,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"I agree. Why are Visual editor, Huggle, mwEmbed products, Various mobile things products? Visual editor should be considered an extension to start with, etc.
+
+I think there should be the following:
+*MediaWiki - for core stuff
+
+*MediaWiki extensions - for extension.
+**The following products should probably be here:
+**Cortando
+**mwEmbed
+
+*Wikimedia - for site config issues, and issues that specificly pertain to Wikimedia's use of MediaWiki, or other web applications installed by Wikimedia
+**Should also include:
+**CiviCRM
+**Analytics
+**DataSets
+**Wikimedia Labs (Arguably its debatable if labs belongs with the rest of the Wikimedia bugs, I lean on the side it does, but I suppose I could see an argument for it being its own product)
+
+*MediaWiki applications and tools - for things that interact with MediaWiki.
+**The following should be moved here:
+**Huggle
+**Wikimedia Mobile (or extension depending on what that tracks)
+**Wikipedia App
+**Wiktionary App
+**WikiLoves Monuments Mobile
+**Tools
+**Monumounts DB (this one is questionable if it belongs here)
+
+*Security (It should be on its own for permission reasons)
+
+*Spam
+
+---
+
+So that would bring it down to 6 products, with 2 (Security and spam) being kind of fake products",1344003404,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+Bugzilla products could use a re-examination,"Cleaning up the bug product descriptions would be nice too. Eliminating the typos, making the punctuation consistent, etc.",1343952268,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-fwiz7o6xh4rtopisteba,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],MediaWiki bugs to be fixed for WMF deployment,1343681340,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-dox25wyrywoe37jydxge,task_description,invalid
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"@greg: agreed, I prefer the project/tag over a tracking bug.",1427763864,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],">>! In T40865#1159225, @mmodell wrote:
+> @greg: By ""next train release"" do you mean the new branch that gets created on wednesday or any train deployment in general? 
+
+The perpetual next release. This bug was used by Reedy to have a place to look for bugs to be pushed out with the train.
+
+We now also have #WMF-Server-Backports, which we should probably use in lieu of this tracking bug, which is what https://www.mediawiki.org/wiki/Backporting_fixes says anyway...
+
+If that sounds ok with you (@mmodell) then let's just close this bug, bid it farewell and thank it for its use over the years...",1427748663,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"@greg: By ""next train release"" do you mean the new branch that gets created on wednesday or any train deployment in general? ",1427539819,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],">>! In T40865#1076036, @Nemo_bis wrote:
+>> What are we going to do with this task now?
+> 
+> Maybe Mukunda has opinions. :)
+
+@mmodell: how would you like to deal with ""things (like config patches) people want to be included in the next train release"".
+
+There's already #wmf-server-backports which we aren't using much at all yet.",1427484400,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"> What are we going to do with this task now?
+
+Maybe Mukunda has opinions. :)",1425168031,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],What are we going to do with this task now?,1423883371,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],Cleared backlog of next-deployment changes that have since been processed.,1417566587,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"(In reply to comment #16)
+> Greg, are we still using this tracking bug?  If not, let's just close this.
+
+Reedy is, and intends to, keep an eye on it. Andre and others are using it actively. I less so, but Andre usually beats me to the punch.
+
+There's also the request for backport flag, which is being used (9 confirmed requests, last one sept 25th). Slight overlap, but not much, really (this one being for ""things that should be done at next train start"" and backport flags being for ""this needs to happen now, now."").",1381948247,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"(For reference, Greg and Reedy say that we do.)",1381947940,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"Greg, are we still using this tracking bug?  If not, let's just close this.",1378310071,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],42512 blocks Nov 28 deployment to commons,1354128453,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"(In reply to comment #12)
+> (In reply to comment #2)
+> > This must not have any unresolved dependencies before a new wmf-branch is
+> > created and deployed.
+> 
+> Rob, just to know: is this an actual decision or just a generic hope?
+> 1.20wmf12 has been deployed to all non-Wikipedia projects without resolving
+> blockers. en.wiki is scheduled for Monday and it's completely unclear what's
+> supposed to happen before and after such deployment.
+
+I'm not sure that is a question, if it is that is a problem. Though we already knew that. Obviously we do have the principle of blocking bugs. The question is where they are listed (in this case on this bug), and secondly it is important that before deployment stuff here doesn't have loose ends.
+
+We can't demand bugs to be fixed by just dumping them on this bug, what I think is a reasonable demand however is that there are no unresolved blockers at the deployment window. Meaning either they are fixed, or removed from the blocker list. But not ignored and let to rot, which is very frustrating but current practice (!).
+
+From spending time in the office I know that's not the case they're not ignored. People do go over this blocker list and decide to either backport a fix, write a new patch or decide it is not important enough. The problem is that result is then not communicated back down to where it belongs: The bug itself and therewith the blocker list here.
+
+It can happen that a decision is made that a bug is not blocking enough, but then it should simply be removed as blocker (with a rationale in the bug comment) and either:
+* assigned to a person to work on soon after deployment
+* or if not important right now and no person available as assignee, put on a milestone for later (e.g. 1.20 release)
+* or if no milestone, adjust the overall priority.",1348244262,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],Boldly adding bug 38158 as a blocker. (I hope I'm not doing anything wrong.),1348241902,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"(In reply to comment #2)
+> This must not have any unresolved dependencies before a new wmf-branch is
+> created and deployed.
+
+Rob, just to know: is this an actual decision or just a generic hope?
+1.20wmf12 has been deployed to all non-Wikipedia projects without resolving blockers. en.wiki is scheduled for Monday and it's completely unclear what's supposed to happen before and after such deployment.",1348215547,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 39841 has been marked as a duplicate of this bug. ***,1348078058,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 37346 has been marked as a duplicate of this bug. ***,1348078033,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 38803 has been marked as a duplicate of this bug. ***,1348078024,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 29068 has been marked as a duplicate of this bug. ***,1348077968,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 36464 has been marked as a duplicate of this bug. ***,1348077960,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 36465 has been marked as a duplicate of this bug. ***,1348077949,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 36664 has been marked as a duplicate of this bug. ***,1348077939,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 36974 has been marked as a duplicate of this bug. ***,1348077921,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],*** Bug 39515 has been marked as a duplicate of this bug. ***,1348077881,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"Renaming this bug to be a generic ""rolling tracking"" bug for each wmf deployments.
+
+This must not have any unresolved dependencies before a new wmf-branch is created and deployed. After deployments, dependencies can be purged. Using a tracking bug instead of a milestone so that it can work cross-product (Tasks for configuration in Wikimedia, bugs in MediaWiki core, stuff in extensions, VisualEditor etc.).",1348077861,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports],"Note to tracking bug readers: don't take the summaries too literally, some (or most) of the tracked issues are actually handled after deployment; always check the server admin log and [[Special:Version]] carefully.",1347688250,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dox25wyrywoe37jydxge,task_subcomment,NA
+VisualEditor: Use prefix when accessing parsoid,"Use a prefix when accessing parsoid. See https://gerrit.wikimedia.org/r/#/c/15626/ for details.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1343673300,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-wvifmqwchjuqimprw5ls,task_description,resolved
+VisualEditor: Use prefix when accessing parsoid,Done in https://gerrit.wikimedia.org/r/#/c/19417/,1345485579,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-wvifmqwchjuqimprw5ls,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"This sounds to me like it might be hideously complicated, but putting it in here - e.g. a link to [http://foo.com] gets an external link notification icon on its right on the English Wikipedia, and this should show up as appropriate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=33084
+https://bugzilla.wikimedia.org/show_bug.cgi?id=37901",1343330820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_description,resolved
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),Marking this back as FIXED (as it has been fixed in Vector for a while).,1409609753,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 151395 merged by jenkins-bot:
+Use .mw-body in skins
+
+https://gerrit.wikimedia.org/r/151395",1409603434,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 151395 had a related patch set uploaded by Jforrester:
+Use .mw-body in skins
+
+https://gerrit.wikimedia.org/r/151395",1408200759,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 153740 abandoned by Catrope:
+Scope external link styling rules to #content rather than #bodyContent
+
+Reason:
+Yeah, that looks much better, thanks guys.
+
+https://gerrit.wikimedia.org/r/153740",1408143297,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 153740 had a related patch set uploaded by Catrope:
+Scope external link styling rules to #content rather than #bodyContent
+
+https://gerrit.wikimedia.org/r/153740",1407893356,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"(In reply to Spinningspark from comment #6)
+> I'm not seeing this as entirely fixed.  The redlink issue has been fixed but
+> there are still other colour issues:
+> 
+> * Visited redlinks are not shown in the visited redlink colour, they are
+> shown in the redlink colour.
+> * External links are not shown in the external links colour, they are shown
+> in the internal links colour.
+> * Link icons are omitted: external, secure, pdf etc.
+> 
+This caught my attention because external link icons have been working for me for a while. Turns out they work in Vector but not in Monobook. This appears to be a bug in Monobook, it's scoping link icon CSS to the wrong div (#bodyContent instead of #content).",1407893056,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"I'm not seeing this as entirely fixed.  The redlink issue has been fixed but there are still other colour issues:
+
+* Visited redlinks are not shown in the visited redlink colour, they are shown in the redlink colour.
+* External links are not shown in the external links colour, they are shown in the internal links colour.
+* Link icons are omitted: external, secure, pdf etc.
+
+The raison d'etre of VE is that it is WYSIWYG while editing.  Not having links in the right colour defeats this and can lead to mistakes.",1407764010,PHID-USER-imut7wxehhy35ukuzaks,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),Verified the fix in production,1400012359,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),Verified the fix in Betalabs and test2,1399406719,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 130769 merged by jenkins-bot:
+Style external links and their suggestions with the right color
+
+https://gerrit.wikimedia.org/r/130769",1398904004,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Change 130769 had a related patch set uploaded by Jforrester:
+Style external links and their suggestions with the right color
+
+https://gerrit.wikimedia.org/r/130769",1398901923,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon),"Applying the same CSS may be difficult, but internal vs external links should be rendered differently somehow.",1373671765,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-rdz73xd47uv2yacm4zi7,task_subcomment,NA
+"VisualEditor: Long preformatted nodes display content splitting words at exactly browser width, not word-wrapped","From user submission. See also https://mediawiki.org/wiki/File:VE_-_sentence_break_pre_formatted_text.png
+
+{F117608,size=full}
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1340916420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ca53s4wb5hmrmn3k5jlh,task_description,resolved
+"VisualEditor: Long preformatted nodes display content splitting words at exactly browser width, not word-wrapped",Merged and will go out with wmf5.,1369428648,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ca53s4wb5hmrmn3k5jlh,task_subcomment,NA
+"VisualEditor: Long preformatted nodes display content splitting words at exactly browser width, not word-wrapped",Related URL: https://gerrit.wikimedia.org/r/65332 (Gerrit Change I9b5e3b3e62b52c86743ee345b1cc31beec0a061e),1369427242,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ca53s4wb5hmrmn3k5jlh,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"From bug T35091:
+
+- The UI of the visual editor should have a change to the user's interaction
+with link creation to make it harder to accidentally create things like
+<a>foo</a>bar.
+
+I'm not quite sure what the ui change should be. Perhaps something like making
+it so that when you try to create a link the selection might be altered to
+cover the full word. Something that would require the user to force the editor
+to use the selection that would create a <nowiki/> instead of just accepting it
+as-is.
+
+Whatever the case, we do not want the user who partially selects a run of text
+and turns it into a link to inadvertently create a <nowiki/> when they likely
+intended to make a link of the whole thing.",1340654460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_description,open
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I think users wouldn't try to partially-select for linking if [[apple]]s worked with VE.
+And one half of fixing that would be to search for ""Apple"" for links suggestions if ""Apples"" isn't found.
+If the user then selects ""Apple"" in the suggestions, the correct
+
+```
+<a href=Apple>apples</a> -> ""[[apple]]s""
+```
+link would be created.
+
+And if ""Apple"" is found (because a redirect from ""Apples"" to ""Apple""), since it can be detected as a part of ""Apples"", the correct link can be created too.",1488146470,PHID-USER-mapumhlp3gw5qefhvafn,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I think users wouldn't try to partially-select for linking if [[apple]]s worked with VE.
+And one half of fixing that would be to search for ""Apple"" for links suggestions if ""Apples"" isn't found.
+If the user then selects ""Apple"" in the suggestion, the correct
+
+```
+<a href=Apple>apples</a> -> ""[[apple]]s""
+```
+link would be created.
+
+And if ""Apple"" is found (because a redirect from ""Apples"" to ""Apple""), since it can be detected as a part of ""Apples"", the correct link can be created too.",1488146450,PHID-USER-mapumhlp3gw5qefhvafn,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I think users wouldn't try to partially-select for linking if [[apple]]s worked with VE.
+And one half of fixing that would be to search for ""Apple"" for links suggestions if ""Apples"" isn't found.
+If the user then selects ""apple"" in the suggestion, the correct
+
+```
+<a href=Apple>apples</a> -> ""[[apple]]s""
+```
+link would be created.
+
+And if ""Apple"" is found (because a redirect from ""Apples"" to ""Apple""), since it can be detected as a part of ""Apples"", the correct link can be created too.",1488146295,PHID-USER-mapumhlp3gw5qefhvafn,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to Krinkle)
+> VisualEditor: Make it hard for users to partially-select some text for linking
+> →
+> VisualEditor: Make it easier to select a link in its entirety (instead of part it)
+
+This isn't actually the bug as filed (or the problem). It's already trivially easy to select an existing link in its entirety (you don't even need to select it); this bug is about when you've made a selection of text which doesn't have a link and are making it into one.
+
+Reverting and making a little clearer.",1403712091,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"Sorry, that second link should be bug 48789",1374776714,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #10 and comment #8)
+These issues should be solved by making it easy to explicitly set the link and the display text independently and unambiguously in the link dialog as is asked for in bug 50945 and bug 47879",1374776628,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #9)
+> (In reply to comment #7)
+> > What is the status of this bug? Currently it is not possible to link or
+> > unlink part of a word, nor to unlink part of a multi-word link.
+> 
+> That's a very worrying problem - what browser are you using that makes this
+> impossible? Does it happen on every page? When you say ""impossible"", do you
+> mean that:
+> 
+> * the link inspector doesn't open when fired on a partial selection,
+> * setting the link on a partial selection doesn't cause a link to be added,
+> * on saving the link on the partial selection, it doesn't turn into the
+> expected wikitext, or
+> * something else that I've not covered?
+> 
+> I can very much add and remove links to parts of words using the link
+> inspector, and remove parts of existing links using the ""clear formatting""
+> button. Hence the issue.
+
+The behaviour has changed since the last depot it seems. Currently when using Firefox 22 on Xubuntu Linux:
+*Selecting part of a word and pressing ctrl+k means I can link only the selected part (previously ctrl+k was selecting the whole word and then opening the link dialog). This currently works as it should.
+*Unlinking part of a word or multi-word link is not possible with the link tool: 
+**If there is the link [[Background]] and I select ""ground"" and press ctrl+k the selection is changed to ""Background"" and then the link dialog opens
+**If there is the link [[Woolwich Arsenal station]] and I select ""station"" and press ctrl+k the selection is changed to ""Woolwich Arsenal station"" and then the link dialog opens. (This has not changed since my previous comment)
+*Selecting part of a linked word or phrase and removing the formatting does remove the link only on the selection, but also removes any and all other formatting on that selection. Per Bug 51757 this is not desirable.",1374776463,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #8)
+> I fail to see the purpose of nowikiing the remainder of a partially linked
+> word.  If I link ""LC circuit"" in the string ""LC circuits"" then I expect the
+> UI
+> to create ""[[LC circuit]]s"", not ""[[LC circuit]]</nowiki>s"".  That latter
+> behaviour is entirely useless in any normal editing scenario I can think of.
+> 
+> The selection should not be expanded automatically.  The UI should assume the
+> editor knows what they are doing unless there is evidence to the contrary. 
+> When I make a partial selection like this it means I want the UI to offer ""LC
+> circuit"" as the link target and display ""LC circuits"" as the link text.
+
+That may be what you expect, with your deep understanding of wikitext, but it's very far from how normal visual editors work and so would be very confusing to users who are not immersed in the fine points of link trails.
+
+More fundamentally, making a change in one place that magically affects another is a bad user experience. Why would this magic happen with links but not, say, adding bold? Why would this happen down-word but not up (except on wikis with linkhead instead of/as well as linktrail)? Etc.",1374773573,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #7)
+> What is the status of this bug? Currently it is not possible to link or
+> unlink part of a word, nor to unlink part of a multi-word link.
+
+That's a very worrying problem - what browser are you using that makes this impossible? Does it happen on every page? When you say ""impossible"", do you mean that:
+
+* the link inspector doesn't open when fired on a partial selection,
+* setting the link on a partial selection doesn't cause a link to be added,
+* on saving the link on the partial selection, it doesn't turn into the expected wikitext, or
+* something else that I've not covered?
+
+I can very much add and remove links to parts of words using the link inspector, and remove parts of existing links using the ""clear formatting"" button. Hence the issue.",1374773288,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I fail to see the purpose of nowikiing the remainder of a partially linked word.  If I link ""LC circuit"" in the string ""LC circuits"" then I expect the UI to create ""[[LC circuit]]s"", not ""[[LC circuit]]</nowiki>s"".  That latter behaviour is entirely useless in any normal editing scenario I can think of.
+
+The selection should not be expanded automatically.  The UI should assume the editor knows what they are doing unless there is evidence to the contrary.  When I make a partial selection like this it means I want the UI to offer ""LC circuit"" as the link target and display ""LC circuits"" as the link text.",1374772448,PHID-USER-imut7wxehhy35ukuzaks,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"What is the status of this bug? Currently it is not possible to link or unlink part of a word, nor to unlink part of a multi-word link.",1374519862,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I really do not understand (my interaction with this bug was due to searching whether another bug was already reported). 
+
+I understand that ""[[Automatic|auto]]mobile"" will create a link on automobile, whereas ""[[Automatic|auto]]<nowiki />mobile"" creates a link only on auto. 
+
+However, the html conversion should work:
+<a href=Automatic>Auto</a>mobile -> ""[[Automatic|auto]]<nowiki />mobile""
+<a href=Automatic>Automobile</a> -> ""[[Automatic|automobile]]""
+and
+<a href=Auto>Automobile</a> -> ""[[Auto]]mobile"" (checking for true substring).
+
+If the discussion is about whether to preserve
+[[Automatic|auto]]mobile
+over
+[[Automatic|automobile]]
+then I believe it should not be preserved, the first is unnecessarily complicated. These are things that are possible to ""clean-up"", particularly if, as you plan for the future, you clean-up only those parts that have been edited.",1355435460,PHID-USER-grpjkpfolt5gz4ljlbfg,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #4)
+> I would warn about automatic changes here. Partially linked words are a
+> standard feature of Wikipedia, especially to link the singular substring of
+> plural words in languages that generally allow that.
+> 
+> A nice-to-have feature may be to provide a dialogue box asking: ""you have
+> only
+> marked a part of the word -  do you want to link the entire word?"".
+> 
+> I consider this a low priority enhancement however.
+
+We're talking here about creating links as <a href=Foo>Fooian</a>, and whether or not they convert to ""smart"" wikitext ([[Foo]]ian) or to the more boring form ([[Foo|Fooian]]). We're not talking about automatic changes - if the link hasn't been edited, it shouldn't be changed.
+
+I don't think that the style of wikitext that people create using the VisualEditor (as opposed to not breaking others' wikitext) is hugely important, but if you want that to be a specific change, you could create a new bug for Parsoid (which is responsible for the HTML->wikitext conversion).
+
+This is specifically about creating a link (to whatever target) on some selection of part of a word, which then on being saved is converted unintentionally. I.e.: 
+
+Automobile -> <a href=Automatic>Auto</a>mobile -> [[Automatic|auto]]mobile
+
+… whereas it should end up somehow as [[Automatic|auto]]<nowiki />mobile, or we should stop users for creating it.",1355434765,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I would warn about automatic changes here. Partially linked words are a standard feature of Wikipedia, especially to link the singular substring of plural words in languages that generally allow that.
+
+A nice-to-have feature may be to provide a dialogue box asking: ""you have only marked a part of the word -  do you want to link the entire word?"".
+
+I consider this a low priority enhancement however.",1355396945,PHID-USER-grpjkpfolt5gz4ljlbfg,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #2)
+> (In reply to comment #1)
+> > I like the idea of expanding the selection (altering it) to cover the full
+> > word, however it still have to be possible to link just a part of the word (not
+> > sure how).
+> 
+> Link a whole word then unlink a part?
+
+It is not very intuitive, but maybe we don't need this particular action to be intuitive.",1340669953,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"(In reply to comment #1)
+> I like the idea of expanding the selection (altering it) to cover the full
+> word, however it still have to be possible to link just a part of the word (not
+> sure how).
+
+Link a whole word then unlink a part?",1340669538,PHID-USER-zjzhrhmn36icnzbckqy4,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Make it hard for users to partially-select some unlinked text for linking,"I like the idea of expanding the selection (altering it) to cover the full word, however it still have to be possible to link just a part of the word (not sure how).",1340659184,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-yzml3nhjxlsx67vmqf5g,task_subcomment,NA
+VisualEditor: Support media (tracking),"I know this isn't ready yet, but that's why we need a bug in the bug tracker. :)
+
+Steps to repro:
+* create a new page in classic editor
+* include [[Image:Wiki.png]]
+* edit in visual editor
+* save
+
+Expected:
+Image should display in edit mode. After saving, nothing should have changed.
+
+Actual:
+Image becomes invisible in edit mode. After saving, it turns into literal HTML:
+<img src=""http://upload.wikimedia.org/wikipedia/commons/b/bc/Wiki.png"" alt=""Wiki.png"" height width=""200px""></img>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340471220,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_description,resolved
+VisualEditor: Support media (tracking),">>! In T39870#997795, @Jdforrester-WMF wrote:
+> Replaced with projects.
+
+Which ones? I definitely can't watch the entire VisualEditor-MediaWiki-plugins component.",1422430004,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),Replaced with projects.,1422425089,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),Related URL: https://gerrit.wikimedia.org/r/68223 (Gerrit Change I547e06dcdb92e19f0159660314187c4f1a62f3ed),1371066070,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),*** Bug 48254 has been marked as a duplicate of this bug. ***,1369093449,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),Turn back into the tracker for the overall enhancement.,1340575601,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+VisualEditor: Support media (tracking),Tested in Firefox 16 nightly.,1340471400,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-m2qyu4hp5hrjchjkpr5h,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,"If I input ~~~, it's converted to my signature. If I input <nowiki>~~~</nowiki>, the nowiki tag is escaped and wrapped and ~~~ is still PST'ed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340390580,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-vpi6cxw7fpw4iujs76of,task_description,resolved
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,Patch committed in https://gerrit.wikimedia.org/r/37996,1355190239,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,"We don't recognize tildes in the tokenizer yet, which would also be the reason why they are not yet escaped. Tildes are already included in syntactic stops used by urltext, but there is no production actually matching them. Should be relatively easy to add.
+
+For regular Wikitext->HTML parsing, those tildes need to be converted back to plain text however (essentially ignored), as they are normally only processed in a pre-save transform. 
+
+An alternative (and arguably simpler) solution would be a simple regexp-based escape rule in escapeWikitext.",1344292658,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,"Actually a Parsoid issue, moving.",1344290780,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,Tweaking summary so it's clear this is about how multiple-tilde strings are handled on save.,1340417044,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,Not sure this isn't intended behaviour. Roan?,1340413000,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly,Mass-moving items into VisualEditor product,1340402739,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vpi6cxw7fpw4iujs76of,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away","After an error message, the spinner is still there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340390280,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_description,resolved
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Merged into master.,1354834279,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Patch in: I6a697dc6bddeebecf4e2ab26805bee9f3754c714,1354832426,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",*** Bug 42125 has been marked as a duplicate of this bug. ***,1354054812,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Pushing to next milestone as they did not make it to master by yesterday.,1352832077,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Bug 39057,1344201043,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away","(In reply to comment #3)
+> Are there steps to reproduce this bug?
+
+Go to http://www.mediawiki.org/wiki/VisualEditor:Sandbox?veaction=edit , blank the page, save, then you get ""Error saving data to server: ..."" without too much explaination (this should be another bug) in an alert() box. After closing the box, ""Save page"" button keeps disabled with a spinner running.",1344200963,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Mass-moving items into VisualEditor product,1340402744,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away",Are there steps to reproduce this bug?,1340400677,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away","(In reply to comment #1)
+> (In reply to comment #0)
+> > After an error message, the spinner is still there.
+> 
+> What? Please write a proper bug description or I'm simply going to mark this
+> bug ""invalid.""
+
+See the new title.",1340395551,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+"VisualEditor: When ""Error saving data to server: Unsuccessful request: error."" the spinner for saving doesn't go away","(In reply to comment #0)
+> After an error message, the spinner is still there.
+
+What? Please write a proper bug description or I'm simply going to mark this bug ""invalid.""",1340394443,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bbdpglmzwrfptpvjc4qf,task_subcomment,NA
+Throw a clean error when user is blocked,"When you attempt to edit something using VisualEditor but you're blocked, in Chrome a ""Error loading data from server: error. Would you like to retry?"" dialog appears instead of the expected MediaWiki:Blockedtext or MediaWiki:Globalblocking-ipblocked error message(s).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340309160,PHID-USER-wqc7ciyvfzunj3l2tvjt,False,PHID-TASK-usdc5jwsnmb44rymudwh,task_description,invalid
+Throw a clean error when user is blocked,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341826,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-usdc5jwsnmb44rymudwh,task_subcomment,NA
+Throw a clean error when user is blocked,"I can only reproduce this via the proxy site that the reporter was using was broken in that accessing /w/api.php gave a 404. That same proxy site had similar issues with other URLs as well, and threw a few dozen 404s for every page load.
+
+Closing this as INVALID, feel free to reopen if this or a similar issue can be reproduced without using a proxy site.",1340311908,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-usdc5jwsnmb44rymudwh,task_subcomment,NA
+Search does not find some pages,"**Author:** `saibotrash`
+
+**Description:**
+A search for Dateiverschieber https://commons.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Dateiverschieber&fulltext=Search&ns8=1&redirs=1&profile=advanced should find [[commons:MediaWiki:RenameRequest.js]]
+
+But it does not. Similarly for other query strings. The word is on that page since at least three months.
+
+It works for other, even older pages.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**Whiteboard**: cirrus-fixed
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52782",1339634040,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4h4phdyks6plprfkjwnh,task_description,declined
+Search does not find some pages,"Verified that this bug no longer exists in CirrusSearch, as the third search result for that query for me is RenameRequest.js. As we're migrating from Lucene to CirrusSearch, I'm closing this bug as RESOLVED WONTFIX.",1391825471,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"This results in VisualEditor returning empty searches even when the exact, complete file name is given as the search term.
+
+At Commons' own Special:Search, searching for the exact, complete file name produces self-contradictory results:
+
+  There were no results matching the query.
+  There is a page named ""File:GreatNurse.jpeg"" on this wiki",1376417868,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"(In reply to comment #0)
+> A search for Dateiverschieber
+> https://commons.wikimedia.org/w/index.
+> php?title=Special%3ASearch&profile=advanced&search=Dateiverschieber&fulltext=
+> Search&ns8=1&redirs=1&profile=advanced
+> should find [[commons:MediaWiki:RenameRequest.js]]
+> 
+> But it does not. 
+
+Confirming for this example.",1360582360,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"**ForoaW** wrote:
+
+Related problems/reports:
+* [https://bugzilla.wikimedia.org/show_bug.cgi?id=6090]
+* [https://bugzilla.wikimedia.org/show_bug.cgi?id=35691]
+* [https://bugzilla.wikimedia.org/show_bug.cgi?id=30595]",1343294906,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"At the Commons Village Pump thread linked in the previous message: 
+*http://commons.wikimedia.org/wiki/Commons:Village_pump#Is_there_something_wrong_with_the_search_engine.3F
+
+LX suggests: ""since we can't trust files to be indexed on upload, we should probably have a scheduled low-priority process to rebuild the index periodically.""",1343204106,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"I came here to file a new request, and I am quite surprised to see that nobody really cares about such a major feature being broken.
+Another example. This search http://commons.wikimedia.org/w/index.php?search=chimurenga&title=Special%3ASearch does not return http://commons.wikimedia.org/wiki/File:Lettera27_-_Rucera_Seethal_(Chimurenga_magazine_staff).jpg or http://commons.wikimedia.org/wiki/File:Lettera27_-_Chairmaine_(Chimurenga_magazine).jpg .
+As suggested by another user at http://commons.wikimedia.org/wiki/Commons:Village_pump#Is_there_something_wrong_with_the_search_engine.3F , a Google search instead returns 58 more results.
+Too bad you can not use an external search to perform mass operations such as adding or removing categories. I am part of a GLAM team. Search is vital for us as well.",1343115053,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+Search does not find some pages,"Interestingly there are results for ""Request renaming of an image"" or ""rAbort"".",1339659271,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-4h4phdyks6plprfkjwnh,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"**Author:** `questpc`
+
+**Description:**
+I developed my extension in 1.18wmf1 then in 1.20 master. One of ResourceLoader modules, defined by extension has the following dependency:
+
+			'dependencies' => 'mediawiki.jqueryMsg',
+
+The 'mediawiki.jqueryMsg' module and it's script is present in 1.18wmf1, 1.19, 1.20 master, but I was really surprised that in 1.18.2 it does not exists so the page scripts where my extension module is requested were broken with the following Chrome console errors:
+
+Uncaught Error: Unknown dependency: mediawiki.jqueryMsg load.php:9427
+Uncaught TypeError: Cannot read property 'options' of undefined GmapFunc:255
+Uncaught TypeError: Cannot read property 'tokens' of undefined GmapFunc:260
+
+Can I try to catch the client-side error in load.php? I don't know how. Instead, I implemented the following server-side method to check whether the dependent modules actually exists:
+
+	static protected function checkAllModulesExists() {
+		$allModules = array_keys( self::$mapModules );
+		foreach ( self::$mapModules as $moduleName => $moduleDefinition ) {
+			if ( !array_key_exists( 'dependencies', $moduleDefinition ) ) {
+				continue;
+			}
+			if ( is_array( $moduleDefinition['dependencies'] ) ) {
+				$allModules += $moduleDefinition['dependencies'];
+			} else {
+				# We do not check for multiple matches in values:
+				# it would only decrease performance in this case.
+				$allModules[] = $moduleDefinition['dependencies'];
+			}
+		}
+		$nonExistantModules = array_diff(
+			$allModules,
+			self::$out->getResourceLoader()->getModuleNames()
+		);
+		if ( count( $nonExistantModules ) > 0 ) {
+			throw new MWException( 'Cannot find requested module(s): ' .
+				implode( ',', $nonExistantModules ) .
+				' in ' . __METHOD__
+			);
+		}
+	}
+
+Which produces the following page message, at least (that is more informative than Chrome console message):
+
+Cannot find requested module(s): mediawiki.jqueryMsg in GMFn::checkAllModulesExists
+
+It would be nice if ResourceLoader itself checked the dependencies of added modules.
+
+--------------------------
+**Version**: 1.18.x
+**Severity**: normal
+**Whiteboard**: aklapper-moreinfo",1337677620,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-w23sfro3gylh7zauvhcz,task_description,declined
+ResourceLoader does not check dependencies for existance,"I see... Pity.
+As we cannot retest, closing as per comment 1.",1376496553,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"**questpc** wrote:
+
+Andre, MediaWiki is unpopular framework here in Russia. Our education system receives much smaller financing comparing to first world countries. Grants and charities are also very small, infrequent and hard to get. Non-commercial work is self-prohibitive because the life is expensive and wages are small (not in Moscow, at least). So I was not getting enough of freelancer MediaWiki job. Thus I was forced to move to Drupal then to my own framework. Sometimes I do small MediaWiki work but not so often and I lost deep knowledge of MediaWiki internals I had back in 1.15-1.17 times (API, FileRepo, early versions of ResourceLoader).
+
+But of course previous lack of good scripting and lack of VisualEditor also contributed to low popularity of MediaWiki here in Russia. Hope it will get more popular again.
+
+The site is now running 1.22wmf1. It was not my personal site but a freelancer job.",1368802542,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"(In reply to comment #1)
+> Modules can be dynamically registered. This should be checked in mediawiki.js
+> instead. I believe this has been fixed in 1.19 or 1.20, could you confirm?
+
+Dmitriy: Still running 1.18, or have you upgraded in the meantime?
+If the latter, cxould you answer above question?",1368800186,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"**questpc** wrote:
+
+I think Extension:UploadWizard also was using this module and it should be supported in 1.18.2 as well.
+
+Is there a graceful way of catching these errors at client side in 1.20? However, 1.20 includes the forementioned module.",1338185899,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+ResourceLoader does not check dependencies for existance,"Modules can be dynamically registered. This should be checked in mediawiki.js instead.
+
+I believe this has been fixed in 1.19 or 1.20, could you confirm?",1338160804,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-w23sfro3gylh7zauvhcz,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"NOTE: this request may be superseded by {T78046}.
+
+From bug 31406 comment 0:
+> A lot of work has gone into making it possible to use MathJax to view
+> TeX on Wikipedia.  Probably more than 20,000 article use TeX (or
+> whichever variant of TeX Wikipedia uses).  I have corresponded with
+> Robert Miner, MathJax Project Director and Vice President or Research
+> and Development at Design Science, Inc. about the fact that MathJax
+> could now be used.  I told him that possibly in coming months MathJax
+> would be adopted as the default means of viewing TeX on Wikipedia.
+
+As I understand it, Michael Hardy was proposing MathJax as the **default** math mode, but since setting $wgMathUseMathJax = true on Wikimedia wikis doesn't imply that it would be the default mode, I'm opening this bug to track what still needs to be done. This will also helps to separate the blockers of a ""experimental deployment"" (which is already done) and the blockers of a ""full deployment"" of MathJax on WMF wikis.
+
+If I understood it correctly, this would be the new setting:
+ $wgDefaultUserOptions['math'] = 2;
+
+Fell free to move some blockers/dependencies from bug 31406 to this one as needed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48036",1336073820,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-5os74s4qlwnokutpo36w,task_description,invalid
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"Please comment on that bug
+https://phabricator.wikimedia.org/T78046",1429892857,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),The only report currently marked as blocker is T37186 and is being discussed there. Going through the #Math component may find some more blockers.,1429892276,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),What's the status of this now? It's been a while since it was last discussed. Are the reasons to not use MathJax just as valid now?,1429891729,PHID-USER-oy47h3fy4yjggdu33qvo,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"**physik** wrote:
+
+In the meantime the situation has changed. So it might be better to create a new bug instead of updating this.",1413742990,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"A first good step might be to resolve bug 48036 (opt-in for unregistered visitors). That way, people can vote with their feet.",1373922516,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"**physik** wrote:
+
+(In reply to comment #9)
+> I think physikerwelt idea of semantic processing of mathematics is a nice
+> idea
+> and fit with the foundations wider goals. However it a bit off topic for this
+> bug. I've created a new bug 51381 which the details where it can be explored
+> in
+> more details.
+
+Thanks... sorry for the off topic... if I just said use
+ $wgDefaultUserOptions['math'] = 7
+that would be somehow pointless.
+By the way 2 is html (deprecated) and mathjax is 6.
+
+7 includes 6 since you it can be combined with MathJax (as you can see in the demo) but it must not. The advantage to use MathJax based on MathML is that it is reasonably fast. (To my mind that's not the case if you use MathJax without MathML). Furthermore you can display MathML without a need of JavaScript support.
+
+A visual editor that is based on MathML would be easier to implement and handle than one that is based on TeX. But I would double think about doing so, since than the Tex source is gone. (OK the same holds for the visual editor in general.)
+
+To stick to the topic, which is not visual editor:
+
+I fully support the initiative to switch the rendering mode.
+However, I think we should find a well defined process for doing so.
+One opportunity could be:
+1. Collect the alternatives
+2. Compare and benchmark them
+3. Discuss the results
+4. Make a decision (Maybe even vote oOo)
+
+This sounds a bit lengthy... but due to the fact that this bug is open for more than a year now... that might be really quick.",1373921609,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),I think physikerwelt idea of semantic processing of mathematics is a nice idea and fit with the foundations wider goals. However it a bit off topic for this bug. I've created a new bug 51381 which the details where it can be explored in more details.,1373912686,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"@Richard, the GSoC project for a math-editor component is coming along nicely. The approach is along the lines of the wyiswhat editor http://oerpub.github.io/Aloha-Editor/. The OERpub folks have done some testing (with regular school teachers) see http://kefletcher.blogspot.com/2013/05/testing-editor-designs.html. 
+
+@Martin I think texvc's restricted TeX fits very well within the concept of Wikitext and texvc has (unfortunatly) proven to be ""stable, secure and long term supported"". Of course I'm biased, but I think MathJax solves the issues you describe (well except the ominous ""along with all the JS issues"" -- not sure what you're referring to). If all you're after is MathML and SVG output, then the MathJax-driven VE plugin could easily produce those as well. 
+
+This is getting off topic, but I would add: we need more rather than less client-side rendering of scientific content. Server side rendering is inherently static, in fact, MathML (which is really just the math equivalent of text) feels a lot like HTML 1 at this point -- barely acceptable, static rendering in the browser. E.g., mathapedia and mathbox show what the future of math on the web might be.",1373911389,PHID-USER-nnhp4dmr6oozfejddbom,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"**physik** wrote:
+
+PS: There is a demo at 
+http://demo.formulasearchengine.com
+
+you can click on 
+http://demo.formulasearchengine.com/index.php/Special:Random
+
+to get a random page of the english wikipedia... the pages are not cached so it might take about 20 seconds, especially if images has to be loaded from commons",1373792662,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"**physik** wrote:
+
+I think it is really important to have a stable, secure, and long term supported way of math rendering.
+As I'm working on integrating LaTeXML a rendering engine that converts tex to MathML I was running into a couple of issues.
+First, Wikipedia uses texvc and not tex, therefore I had to create a list of special user defined commands. MathJax has this list as well.
+To my mind it's a suboptiomal solution especially with regard to long term support. I propose to come up with a grammar that can be used by a wide audience (e.g. antlr) and convert that into native php code. This grammar converts texvc to tex and eliminates all commands that are not allowed.
+Second, there are some security aspects, i.e. that someone could put code that is a potential security risk for the visitors. Texvc eliminates this security risk by       returning pictures only. On the other side as texvc is a potential security risk for the server, since the rendering must take place on the same machine as the core server works.
+LaTeXML can use a separate server, but if there is an attack to the network the traffic could be redirected to another server. Therefore the output of LaTeXML must be checked again before returning it to the users browser.
+If the users browser supports mathml only bugs in the browsers mathml implementation can be a security risk. If not MathJaX is needed to convert MathML to whatever, which comes along with all the Javascript issues.
+As a result I think that it would be good to seperate the tasks somehow.
+The Wikimedia Math extension php code should convert texvc to tex and ensure that only valid tex is passed to the rendering engine.
+Than a standard rendering engine can be used and the final result can be validated according to standard methods. e.g. validate MathML out against the W3C MathML scheme.
+In summer 2012 I proposed the LaTeXML render at CICM 2012, now it's avalible as opt-in[1].
+
+[1] http://arxiv.org/abs/1304.5475",1373791916,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"So we have a problem. We need to discuss maths on our talk page. Its a central part of building the encyclopedia. Now Flow is going to be introduced for our talk pages which will not allow standard wikicode as only the VisualEditor is allowed. Hence the VE must have math support, that is Bug 43058 must be fixed. 
+
+Now a maths visual editor is a herculanean task but central to that is a render. MathJax could potentially do it, texvc cannot as you would have generate a new image on the fly with each key stroke. Any other system is just going to be an ugly kludge. 
+
+In reply to Erik's comment. You have a tradeoff between the time it take javascript to render, with the time it takes to download all the images for the equations. It can take a considerable time to download a maths heavy page like Help:Formula. I would say they just about balance each other.",1373784725,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"(In reply to comment #3)
+> I don't think that this is likely to happen in the near future. MathJax is
+> significantly slower to render even on high end computers and would likely
+> cause unacceptable slowness on math-intense pages for users of low-end
+> machines.
+
+Just to mention one of the blocker bugs, it also has no localisation (bug 35038).
+
+> I'm inclined to close this as WONTFIX for the time being. I'd suggest looking
+> into ways to expose the MathJax user preference a bit more so that
+> math-interested users can discover it more easily. For example, we could
+> integrate the right-click menu that MathJax exposes with the PNG rendering
+> mode.
+
+Closing this per Erik (blocker bugs are easily overlooked, status is clearer to readers). Reopening is cheap when issues are solved.",1370592663,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"I don't think that this is likely to happen in the near future. MathJax is significantly slower to render even on high end computers and would likely cause unacceptable slowness on math-intense pages for users of low-end machines.
+
+I'm inclined to close this as WONTFIX for the time being. I'd suggest looking into ways to expose the MathJax user preference a bit more so that math-interested users can discover it more easily. For example, we could integrate the right-click menu that MathJax exposes with the PNG rendering mode.",1336522265,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"* Adding (open) bugs which are currently marked as blockers for bug 31406
+* Removing ""shell"" keyword for now, since the blockers would need to be fixed first",1336074752,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default),"PS: Remember that when MW 1.19 went live, it caused the default option ""HTML if very simple or else PNG"" to be replaced by ""Always render PNG"", and there were complains about that because the old default was better than PNG in some sense. So this bug would be the way to ""restore"" the previous ""better than PNG"" default.",1336074581,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-5os74s4qlwnokutpo36w,task_subcomment,NA
+#mw-content-text is incorrectly placed on preview,"The id #mw-content-text, as I understand it, is normally attached to the .mw-content-ltr/rtl div so that the element directly holding the content is accessible through javascript. However, during preview, the ID is instead attached to a different element, which has #wikiPreview as a child element, which then has an ID-less (and thus inaccessible) .mw-content-ltr/rtl div holding the content. #mw-content-text should consistently be the content-holding div.
+
+--------------------------
+**Version**: 1.19
+**Severity**: normal",1336042080,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-e5n7wa77tt6s4carpjsv,task_description,resolved
+#mw-content-text is incorrectly placed on preview,"Looking at the preview page now, it has all the correct CSS rules applies. It inherits a `direction` from a `dir=""…""` element, and it is presented within an element that has `mw-content-ltr/rtl` classes applied.
+
+Is is still true today that this element does not have an ID of `#mw-content-text`. That element is elsewhere on the page, and has to be for compatibility with other code. It cannot be the same element because when previewing an edit, `#mw-content-text` is for the edit form (which is in your user language), whereas the `.mw-content-ltr#wikiPreview` element is for the page content (which is in the content language).
+
+These unfortunately cannot be the same.
+
+Focussing on the original use case, I believe you want to find the parts of the wiki content no matter whether it is a preview, oldid, or page view. Is that right? For that use case, we have `mw.hook('wikipage.content')` whicih will run for page views, previews, Live Preview, post-edit VisualEditor, Flow, Translate, Upload form, etc. anywhere where wikitext or templates may render.
+
+See [JS docs](https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.hook).
+",1588452442,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-e5n7wa77tt6s4carpjsv,task_subcomment,NA
+#mw-content-text is incorrectly placed on preview,"**alexsm333** wrote:
+
+Related issue (I think):
+
+API action=parse does not return div.mw-content-ltr
+so all ""ajax preview"" userscripts miss some global CSS,
+one example is "".mw-content-ltr .magnify {float: right}""
+for thumb images.",1337977920,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-e5n7wa77tt6s4carpjsv,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Raw TeX commands are displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1334738220,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_description,resolved
+MathJax doesn't work in LivePreview,"I see i forgot to close this one. This is basically working now, though there apparently is a bug, reported in T90808.",1424939822,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"For LivePreview, it depends on bug 24134 which isn't fixed yet, because I still need to finish https://gerrit.wikimedia.org/r/#/c/131346/. The patch that was merged was just one of the prerequisites. 
+
+VE is a separate issue.",1404905044,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,I just tested and it still doesn't seem to work (PNG images are shown).,1404903170,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Patch was merged a while ago - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?",1404896416,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Change 124064 merged by jenkins-bot:
+MathJax: Listen for wikipage.content hook
+
+https://gerrit.wikimedia.org/r/124064",1396886827,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Change 124064 had a related patch set uploaded by TheDJ:
+MathJax: Listen for wikipage.content hook
+
+https://gerrit.wikimedia.org/r/124064",1396718329,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"A specific problem is that after a session in VisualEditor a full refresh is not done and MathJax is not rerun, so the raw latex code is displayed. Apparently according to bug 51565 gadgets should listen to ""wikipage.content"". I have heard rumours that the fix to bug 48560 will fix this problem.
+
+This ha come up at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=593049936",1391069604,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Both Ajaxpreview and wikEd now use the renderTex() command to render MathJax in their ajax based preview modes:
+
+Example: https://en.wikipedia.org/w/index.php?title=User%3AJs%2Fpreview2.js&diff=558032369&oldid=520879456
+
+Soon to be improved by making use of https://gerrit.wikimedia.org/r/56762",1370210310,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"(For the record, there is now a fix in progress for bug 30713 which is a dependency here.)",1367254012,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,MathJax module now has a $().renderTex command that can be run to render domelements that contain tex commands. A preview hook can use this to postprocess the preview output.,1367143537,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"Re-opening as this needs two things:
+* Be able to get modules loaded that extensions add to the page (bug 24134)
+* Be able to run code for ""article loaded"" when the article html is loaded. Usually this is document-ready which is how we do it now, but in case of preview we have multiple ""article loaded"" points within the lifecycle of a single page. This will be made possible by 30713.",1344752641,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"
+
+*** This bug has been marked as a duplicate of bug 24134 ***",1344752405,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"
+
+*** This bug has been marked as a duplicate of bug 33399 ***",1334802665,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+MathJax doesn't work in LivePreview,"More or less the same as in bug 33399. If JavaScript features in LivePreview don't work for core features one can't expect it to work for extensions.
+A hook system as suggested in bug 23580 would be the best way to fix this bug.
+See also bug 35478.",1334742752,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-fg4qhxpyc7qgbgtrnnjy,task_subcomment,NA
+"VisualEditor: Backspace, cursor, among others not working in the insert link dialog","See title. Maybe it's due to handling the keydown event and return'ing false or preventing default, I don't know.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1333706040,PHID-USER-d2y3fvmumrowgb4efuvo,False,PHID-TASK-mo2gxuiaaf5jb54y7zdh,task_description,resolved
+"VisualEditor: Backspace, cursor, among others not working in the insert link dialog",Fixed in new version.,1340403895,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mo2gxuiaaf5jb54y7zdh,task_subcomment,NA
+"VisualEditor: Backspace, cursor, among others not working in the insert link dialog",Mass-moving items into VisualEditor product,1340402734,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mo2gxuiaaf5jb54y7zdh,task_subcomment,NA
+content-holding <div> should only contain the page text,"**Author:** `a.d.bergi`
+
+**Description:**
+The new bidirectionality-improving div should only contain the parsed page content, nothing else. This is perfect when viewing articles, and helps scripts a lot when extracting that content.
+
+But I think it is only needed for article views. For example in diff mode, it contains 
+```lang=html
+ <form id=""mw-fr-reviewform"">
+ <div id=""mw-fr-diff-headeritems"">
+ <table class=""diff"">
+ <hr class=""diff-hr""/>
+ <h2 class=""diff-currentversion-title"">
+```
+ ...and then the real content
+
+Also, in edit mode the `<div id=""mw-content-text"">` contains
+```lang=html
+ <div id=""editnotice-ns-0""/>
+ <div id=""mw-edit-longpage-hint"">
+ <div id=""wikiPreview"" class=""ontop"" style=""display: none;""/>
+ <form id=""editform"">
+```
+None of them is really content-text, I suspect. I think it would be better to have the div only appear (maybe empty) in the `#wikiPreview`.
+
+Also, it for example broke my script which tried to
+```lang=javascript
+document.getElementById(""bodyContent"").insertBefore(newElement, document.getElementById(""editform""));
+```",1331837760,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_description,resolved
+content-holding <div> should only contain the page text,"Thanks, that helps a lot. I wasn't even clear on what I should be looking for in the first place . and just found this task because it was mentioned in a comment somewhere possibly relevant...",1554995075,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#5102699, @Isarra wrote:
+> Can someone clarify for me if this is why ParserOptions::setWrapOutputClass() no longer takes 'false' as an option (this being the only sane way I could find to disable the entire wrapper when running parser->parse on a thing)?
+
+""This"" being what? This task is the reason that method exists in the first place. You can disable wrapping by using the `clearWrapperDivClass()` method or the `wrapperDivClass` option of the `getText()` method in ParserOutput.
+
+The reason false was deprecated is {T181846} (git blame is your friend...).",1554945467,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#5102699, @Isarra wrote:
+> Can someone clarify for me if this is why ParserOptions::setWrapOutputClass() no longer takes 'false' as an option (this being the only sane way I could find to disable the entire wrapper when running parser->parse on a thing)?
+
+""This"" being what? This task is the reason that method exists in the first place. You can disable wrapping by using the `clearWrapperDivClass()` method or the `wrapperDivClass` option of the `getText()` method in ParserOutput.",1554945368,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"And if this is why, this is the relevant patch that this is causing problems for: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CollaborationKit/+/502902 Is there some other way I should be doing this?
+Note that this isn't wikitext; merely contains arbitrary amounts of it.
+
+Or if this is the wrong thing, can someone point me to the correct task(s)?",1554932622,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Can someone clarify for me if this is why ParserOptions::setWrapOutputClass() no longer takes 'false' as an option (this being the only sane way I could find to disable the entire wrapper when running parser->parse on a thing)?
+
+I ask because I'm calling parser->parse on several things individually and we're just wrapping the final result in the relevant classes, and having each bit wrapped is causing other problems, but I can't figure out how to properly disable that now...",1554931704,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 352835 abandoned by Anomie:
+Add mw-parser-output to indicators container
+
+Reason:
+I'll let someone else figure out those details.
+
+[[https://gerrit.wikimedia.org/r/352835]]",1521477204,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVwNxIhIQMK9DA-FLPfy} [2017-05-15T20:20:02Z] <subbu> Updated Parsoid to a182c227 (T141226, T164792, T37247, T153107, T163091, T164006, T161151, T162920, T163549)",1494879605,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 352711 merged by jenkins-bot:
+[mediawiki/services/parsoid@master] Add mw-parser-output class to Parsoid's output
+
+[[https://gerrit.wikimedia.org/r/352711]]
+",1494425384,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 352835 had a related patch set uploaded (by Anomie; owner: Anomie):
+[mediawiki/core@master] Add mw-parser-output to indicators container
+
+[[https://gerrit.wikimedia.org/r/352835]]
+",1494339677,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"At svwiki we have
+  - https://sv.wikipedia.org/wiki/MediaWiki:Gadget-ProtectionIndicators.js 
+  - https://sv.wikipedia.org/wiki/MediaWiki:Gadget-GroupIndicators.js 
+  - https://sv.wikipedia.org/wiki/MediaWiki:Gadget-BlockIndicator.js
+to convey information about protected pages, groups and blocked users in a reliable way, unlike templates that anyone can add or remove. This is not user-generated content, so if you're going to do this, I would prefer if you can just wrap the individual indicators that come from the wikitext, not the container for all indicators.",1494280430,PHID-USER-2wcuxlzgvwfnnxqqqk67,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 352711 had a related patch set uploaded (by Subramanya Sastry; owner: Subramanya Sastry):
+[mediawiki/services/parsoid@master] Add mw-parser-output class to Parsoid's output
+
+[[https://gerrit.wikimedia.org/r/352711]]
+",1494279302,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Good question. I'd say yes, since indicators are user-generated content. It'd probably be a good idea to add the class to the indicators' wrapper element.",1494277050,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Here's a late annoying question – should contents of page status indicators (`<indicator name=""…""></indicator>` in wikitext; https://www.mediawiki.org/wiki/Help:Page_status_indicators) be wrapped in this new wrapper? ",1494276408,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#3181097, @Anomie wrote:
+> I don't know whether #VisualEditor and #Flow will get fixed up by that, though, or if they'll need some other work. I tried to set them up in mediawiki-vagrant, but neither actually functioned.
+
+Now that the patch is merged and on Beta Labs, I was able to confirm that neither VE's editing area nor Flow's comments are getting wrapped in the new class. Filed T164790 and T164791 for those extensions.",1494274545,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Note this won't be included in 1.30.0-wmf.1, but should be in 1.30.0-wmf.2.",1494273236,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350634 merged by jenkins-bot:
+[mediawiki/core@master] Wrap parser output in <div class=""mw-parser-output"">
+
+[[https://gerrit.wikimedia.org/r/350634]]
+",1494222103,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#3230407, @Krinkle wrote:
+> It's not clear to me why a separate class is needed here. How is `mw-parser-output` semantically different from `mw-body-content`?
+
+`.mw-body-content` includes a lot more than just the parser output, for example the edit form, the diff tables, and so on, and so wouldn't fix the complaints about those being affected by TemplateStyles.
+
+Also `.mw-body-content` is added by the skin. Of the 42 skins in extensions/skins, it looks like only 12 have any mention of it.[1] Of the skins on enwiki, Monobook and Vector have it while CologneBlue and Modern don't.
+
+[1]: Based on a grep for `mw-body-content`
+
+> I assume that `mw-parser-output` would solely be applied to output that literally comes from the parser, no exception.
+
+That's the plan.
+
+> 1. Is it valid for MediaWiki core interface styles and skin styles to ever target `mw-parser-output`? I propose no, they must use `mw-body-content` instead.
+
+I doubt there'd be reason for them to.
+
+> 2. Do we support outputting `mw-parser-output` on a MediaWiki-powered HTML response without being a descendant of `mw-body-content`? I propose no, an element with `mw-parser-output` must either also have `mw-body-content` or be a descendant of an element with that class.
+
+Since 70% of skins in Gerrit don't even wrap the main content of the page in `mw-body-content`, yes, we support that. I have no objection to someone deciding to fix that somehow, but let's not let it block this.
+
+> This leaves the question: What is the risk of allowing TemplateStyles to target `mw-body-content`?
+
+For affecting things it shouldn't affect, largely the same as it targeting `#mw-content-text` since in Monobook and Vector `#mw-content-text` is a child of `.mw-body-content`.
+
+For not affecting things is should affect, pretty large since 70% of skins in Gerrit don't wrap the main page content in that class.
+
+> The answer, as I understand it, is that we have some interface components (like page heading, categories, notices/banners, Translate extension controls, FlaggedRevs extension controls) that should be styled the same way as page content (e.g. their headings and links etc.) but don't always come straight out of the parser. And presumably we want to avoid these elements from being styled by a template on the current page.
+
+Yes, that seems accurate.
+
+> * Would it be appropiate to instead have these common styles use `mw-body` instead of `mw-body-content` in their CSS? E.g. for skin headings, links etc. Thus turning mw-body-content into the proposed `mw-parser-output`.
+
+Only if we kill `mw-body-content` from all skins and start adding it in core in the way the current patch adds `mw-parser-output`. I'd rather pick a new name than try to make major changes to an old one.
+
+Again, `mw-body` is added by skins. It looks like 15 of 42 skins in Gerrit don't add it, but all four of the skins on enwiki do.[2]
+
+[2]: Based on a grep for `mw-body($|[^a-z-])`
+
+> * Given that firstHeading is partially provided by Parser. And banners are entirely parsed by the parser. Will the class name apply there?
+
+Currently, it is not applied to firstHeading. I don't have banners on my local wiki to test, but if they use `Parser::parse()` rather than something like `Message::parse()` they would. Or whatever generates the banner could always add the wrapper itself if necessary.
+
+> If yes, then the current page has the ability to affect the notices, which are supposed to be restricted. If not, then notices cannot use templates properly. Perhaps it makes sense to have mw-parser-output be a dynamically generated class instead of a fixed name (e.g. mw-parser-output-123), so that TemplateStyles can be restricted to the correct context only?
+
+Hmm, that's not a bad idea. OTOH, callers that didn't want the default `mw-parser-output` could always use `ParserOptions->setWrapOutputClass()` to set something else.
+
+> * Besides elements provided by the parser (first heading, and site notices), is there a problem with moving the Translate and FlaggedRevs extension controls out of mw-body-content? Or more specifically, is there a problem with removing mw-body-content from `#bodyContent` in Vector and instead applying it to the relevant child nodes only?
+
+Just that it would be a major redefinition of what exactly `.mw-body-content` applies to.",1493824662,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"It's not clear to me why a separate class is needed here. How is `mw-parser-output` semantically different from `mw-body-content`?
+
+I assume that `mw-parser-output` would solely be applied to output that literally comes from the parser, no exception. However while that is a clear use case, the use case for styling that output seems slightly wider. Because the purpose of `mw-body-content` right now is for anything that is meant to be styled the same way as page content.
+
+While these are different technical purposes, I'd like to make sure we avoid cases where one set `mw-parser-output` to mimic certain styles, or alternatively where one would have to target both in CSS to make sure it always applies.
+
+A few questions to help narrow it down:
+
+1. Is it valid for MediaWiki core interface styles and skin styles to ever target `mw-parser-output`? I propose no, they must use `mw-body-content` instead.
+2. Do we support outputting `mw-parser-output` on a MediaWiki-powered HTML response without being a descendant of `mw-body-content`? I propose no, an element with `mw-parser-output` must either also have `mw-body-content` or be a descendant of an element with that class.
+
+This leaves the question: What is the risk of allowing TemplateStyles to target `mw-body-content`? The answer, as I understand it, is that we have some interface components (like page heading, categories, notices/banners, Translate extension controls, FlaggedRevs extension controls) that should be styled the same way as page content (e.g. their headings and links etc.) but don't always come straight out of the parser. And presumably we want to avoid these elements from being styled by a template on the current page.
+
+In that case I have a few more questions:
+
+* Would it be appropiate to instead have these common styles use `mw-body` instead of `mw-body-content` in their CSS? E.g. for skin headings, links etc. Thus turning mw-body-content into the proposed `mw-parser-output`. One problem with this is that Parsoid prefers to only use mw-body-content, and not mw-body, and still load Vector styles and have a page that looks like it was cut out from a Vector-skin page view but without the skin wrapping. Applying mw-body has the side effect of needlessly reserving space for the sidebar and such. Although it would be trivial to fix Vector to move these styles to a vector-specific class name on the same element since strictly speaking this should not have been applied to mw-body in the first place.
+
+* Given that firstHeading is partially provided by Parser. And banners are entirely parsed by the parser. Will the class name apply there? If yes, then the current page has the ability to affect the notices, which are supposed to be restricted. If not, then notices cannot use templates properly. Perhaps it makes sense to have mw-parser-output be a dynamically generated class instead of a fixed name (e.g. mw-parser-output-123), so that TemplateStyles can be restricted to the correct context only?
+
+* Besides elements provided by the parser (first heading, and site notices), is there a problem with moving the Translate and FlaggedRevs extension controls out of mw-body-content? Or more specifically, is there a problem with removing mw-body-content from `#bodyContent` in Vector and instead applying it to the relevant child nodes only?",1493780638,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"It's not clear to me why a separate class is needed here. How is `mw-parser-output` semantically different from `mw-body-content`?
+
+I assume that `mw-parser-output` would solely be applied to output that literally comes from the parser, no exception. However while that is a clear use case, the use case for styling that output seems slightly wider. Because the purpose of `mw-body-content` right now is for anything that is meant to be styled the same way as page content.
+
+While these are different technical purposes, I'd like to make sure we avoid cases where one set `mw-parser-output` to mimic certain styles, or alternatively where one would have to target both in CSS to make sure it always applies.
+
+A few questions to help narrow it down:
+
+1. Is it valid for MediaWiki core interface styles and skin styles to ever target `mw-parser-output`? I propose no, they must use `mw-body-content` instead.
+2. Do we support outputting `mw-parser-output` on a MediaWiki-powered HTML response without being a descendant of `mw-body-content`? I propose no, an element with `mw-parser-output` must either also have `mw-body-content` or be a descendant of an element with that class.
+
+This leaves the question: What is the risk of allowing TemplateStyles to target `mw-body-content`? The answer, as I understand it, is that we have some interface components (like page heading, categories, notices/banners, Translate extension controls, FlaggedRevs extension controls) that should be styled the same way as page content (e.g. their headings and links etc.) but don't always come straight out of the parser. And presumably we want to avoid these elements from being styled by a template on the current page.
+
+In that case I have a few more questions:
+
+* Would it be appropiate to instead have these common styles use `mw-body` instead of `mw-body-content` in their CSS? E.g. for skin headings, links etc. Thus turning mw-body-content into the proposed `mw-parser-output`. One problem with this is that Parsoid prefers to only use mw-body-content, and not mw-body, and still load Vector styles and have a page that looks like it was cut out from a Vector-skin page view but without the skin wrapping. Applying mw-body has the side effect of needlessly reserving space for the sidebar and such. Although it would be trivial to fix Vector to move these styles to a vector-specific class name on the same element since strictly speaking this should not have been applied to mw-body in the first place.
+
+* Given that firstHeading is partially provided by Parser. And banners are entirely parsed by the parser. Will the class name apply there? If yes, then the current page has the ability to affect the notices, which are supposed to be restricted. If not, then notices cannot use templates properly.
+
+* Besides elements provided by the parser (first heading, and site notices), is there a problem with moving the Translate and FlaggedRevs extension controls out of mw-body-content? Or more specifically, is there a problem with removing mw-body-content from `#bodyContent` in Vector and instead applying it to the relevant child nodes only?",1493780529,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350635 merged by jenkins-bot:
+[mediawiki/extensions/MobileFrontend@master] Update tests for core change If4eb5bf7
+
+[[https://gerrit.wikimedia.org/r/350635]]
+",1493750516,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,">>! In T37247#3219054, @dr0ptp4kt wrote:
+> you most likely want to double check that CSS selector expressions keep working in reading and, to the extent they're employed in the experiences you engineer, editing contexts. There may be no problem, but I would be remiss to not note it.
+
+As far as selectors, you're probably good unless you're using the direct-decendent `>` selector. Potentially more interesting would be things like MobileFrontend that try to chop up the parser output (although for MobileFrontend specifically I already submitted [[https://gerrit.wikimedia.org/r/#/c/350635/|this patch]]).",1493326380,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Yeah, ok, thanks.",1493326352,PHID-USER-2wcuxlzgvwfnnxqqqk67,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Flow or anything else that might want to put two ""pages"" of content in one HTML document. For example, a side-by-side comparison of the rendered text might make sense somewhere, maybe for translation or something.",1493326250,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,Does it have to be a class (instead of an id) because of Flow?,1493325907,PHID-USER-2wcuxlzgvwfnnxqqqk67,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350636 merged by jenkins-bot:
+[mediawiki/extensions/Wikibase@master] Update tests for core change If4eb5bf7
+
+[[https://gerrit.wikimedia.org/r/350636]]
+",1493324256,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Adding @bearND, @Mholloway, @JoeWalsh, @Jdlrobson, @MarkTraceur for visibility - you most likely want to double check that CSS selector expressions keep working in reading and, to the extent they're employed in the experiences you engineer, editing contexts. There may be no problem, but I would be remiss to not note it.
+
+CC @Fjalapeno",1493322933,PHID-USER-srhlj2447vmpmrfhqnfa,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350636 had a related patch set uploaded (by Anomie; owner: Anomie):
+[mediawiki/extensions/Wikibase@master] Update tests for core change If4eb5bf7
+
+[[https://gerrit.wikimedia.org/r/350636]]
+",1493318866,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350635 had a related patch set uploaded (by Anomie; owner: Anomie):
+[mediawiki/extensions/MobileFrontend@master] Update tests for core change If4eb5bf7
+
+[[https://gerrit.wikimedia.org/r/350635]]
+",1493318862,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Change 350634 had a related patch set uploaded (by Anomie; owner: Anomie):
+[mediawiki/core@master] Wrap parser output in <div class=""mw-parser-output"">
+
+[[https://gerrit.wikimedia.org/r/350634]]
+",1493318859,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"Maybe you could have a ParserOption for it, so that the parser tests can still pass without too much trouble? Have the wrapper be on by default, but turn it off for parser tests. Other than that, I think it should be fine to add it to Parser::parse(). Write the patch and we'll see what happens.",1493270839,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"I've become interested in this thanks to TemplateStyles. Currently, TemplateStyles scopes all styles to the `id=""mw-content-text""` element to prevent styles from accidentally messing with site UI. I just now loaded a random page in VE and noticed that its content being edited is not within that element, so the template styles won't be applied in the editor. This isn't good.
+
+At the same time, we have this bug complaining that the `id=""mw-content-text""` element sometimes contains more than just the page output, for example it contains the diff tables, the edit form, category text, image metadata, and so on. The `mw-content-ltr` and `mw-content-rtl` classes mentioned here do slightly better, they don't hold the diff tables but do hold parts of category lists, the entire Flow page, and so on. And having to target multiple classes would bloat TemplateStyles's output.
+
+It looks like the most straightforward option to getting just the parser output to be wrapped in some sort of container is to do just that: stick some code like this in near [[https://phabricator.wikimedia.org/source/mediawiki/browse/master/includes/parser/Parser.php;d038e889f72d17bbf03d2098111c928571c2c72d$592|this line in the Parser]]:
+``` lang=php
+        # Wrap non-interface ParserOutput in a class
+        if ( !$this->mOptions->getInterfaceMessage() ) {
+            $text = Html::rawElement( 'div', [ 'class' => 'mw-parser-output' ], $text );
+        }
+```
+I don't know whether #VisualEditor and #Flow will get fixed up by that, though, or if they'll need some other work. I tried to set them up in mediawiki-vagrant, but neither actually functioned.
+
+
+If we don't do that, we may be able to get by with a few more changes where ParserOutput is used.
+* `OutputPage::addParserOutputText()`, either before or after the 'OutputPageBeforeHTML' hook call, will catch most cases.
+** We'll probably need to copy the interface flag into the ParserOutput so that can only wrap the non-interface ParserOutputs.
+* `EditPage::doPreviewParse()` needs to wrap its HTML too.
+* Possibly the ""Empty content container for LivePreview"" in `EditPage::displayPreviewArea()` should have the class added.
+* `TemplateSandbox::templateSandboxPreview()` where it basically duplicates `EditPage::getPreviewText()`
+* `Translate::getDocumentationBox()` where it displays the qqq message
+* Wherever in Flow that it generates the `flow-post-content` div.
+* VisualEditor would probably need to add the class to its wrapper div, probably the same one that already has the 'mw-content-ltr' class.",1492117803,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"**a.d.bergi** wrote:
+
+> > Also, it for example broke my script which tried to
+> >  document.getElementById(""bodyContent"").insertBefore(newElement,
+> > document.getElementById(""editform""));
+> 
+> Please elaborate what you mean here.
+
+I have a script that inserted some edit tools into #bodyContent, right before #editform. Since r111647 that doesn't work, as #editform now is a child of #mw-content-text.
+
+OK, it was a minor issue and very easy to fix. I only wanted to mention that some tools may be broken that make assumptions about the child nodes of mw.util.$content, which might be quite common.",1332166667,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"(In reply to comment #0)
+> Also, it for example broke my script which tried to
+>  document.getElementById(""bodyContent"").insertBefore(newElement,document.getElementById(""editform""));
+
+Please elaborate what you mean here.",1467403389,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+content-holding <div> should only contain the page text,"(In reply to comment #0)
+> Also, it for example broke my script which tried to
+>  document.getElementById(""bodyContent"").insertBefore(newElement,
+> document.getElementById(""editform""));
+
+Please elaborate what you mean here.",1332165373,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xad4cjfvysvak3tdxloe,task_subcomment,NA
+"VisualEditor: Undoing ""Clear formatting"" does not work","Clicking ""Undo"" after using the ""Clear formatting"" button does not work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1330562220,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-oeyka3jairvoviqejllv,task_description,resolved
+"VisualEditor: Undoing ""Clear formatting"" does not work",Mass-moving items into VisualEditor product,1340402754,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oeyka3jairvoviqejllv,task_subcomment,NA
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,"* Open up https://test.wikipedia.org/wiki/Special:VisualEditorSandbox
+* click-and-drag to select...
+* ...keep dragging down to the bottom of the window and beyond
+
+Expected behavior:
+Document should scroll so we can keep selecting stuff.
+
+Actual behavior:
+Document does not scroll; cannot select anything further by mouse.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://test.wikipedia.org/wiki/Special:VisualEditorSandbox
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51669",1328824440,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-voh6lpuq6qwl3jpaliry,task_description,resolved
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,Noting bugs closed in the 2012-10-15 release.,1351534198,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-voh6lpuq6qwl3jpaliry,task_subcomment,NA
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341855,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-voh6lpuq6qwl3jpaliry,task_subcomment,NA
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,Fixed with new version of VE (built-in behaviour).,1340401398,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-voh6lpuq6qwl3jpaliry,task_subcomment,NA
+Page doesn't scroll when dragging selection off bottom of window in VisualEditor,We had this working in a demo before. I know it can be done with the document.onmousemove events we get.,1329154427,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-voh6lpuq6qwl3jpaliry,task_subcomment,NA
+Window resizing crashes VisualEditor if too small,"In certain browsers (including Chrome and IE9), if one resizes the window to smaller than a certain size, the VisualEditor will crash.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1328532960,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-47m3opkl4tk6r424d6ee,task_description,resolved
+Window resizing crashes VisualEditor if too small,Noting bugs closed in the 2012-10-15 release.,1351534204,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-47m3opkl4tk6r424d6ee,task_subcomment,NA
+Window resizing crashes VisualEditor if too small,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341861,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-47m3opkl4tk6r424d6ee,task_subcomment,NA
+Window resizing crashes VisualEditor if too small,Fixed with new version of VE (built-in behaviour).,1340401269,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-47m3opkl4tk6r424d6ee,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"**Author:** `aokomoriuta`
+
+**Description:**
+When I don't have skipcaptcha right, page translation with external link got error.
+Can we pass CAPTCHA test in translation function?",1328258040,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_description,open
+Special:Translate unable to save where CAPTCHA is required,"For searchers: this bug often comes with ""Saving the translation failed: The modification you tried to make was aborted by an extension hook"" warnings.
+https://www.mediawiki.org/wiki/Thread:Extension_talk:Translate/_%27Saving_the_translation_failed:_The_modification_you_tried_to_make_was_aborted_by_an_extension_hook%27_and_Documentation_problems/reply
+https://www.mediawiki.org/w/index.php?title=Help%3AExtension%3ATranslate%2FConfiguration&diff=1236716&oldid=1229427",1414140259,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,ContentTranslation implemented a (after the fact) solution: https://gerrit.wikimedia.org/r/#/c/146426/,1405494153,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"If this works only with FancyCaptcha, this is already a good start.",1380581640,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"(In reply to comment #9)
+> So, it seems it's possible to deal with with the extension:ConfirmEdit
+> through
+> the API:
+> https://bugzilla.wikimedia.org/show_bug.cgi?id=50356#c3
+
+Note, that comment mentions only FancyCaptcha [which is the least used component of ConfirmEdit: few wikis other than WMF use it].",1378369248,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"So, it seems it's possible to deal with with the extension:ConfirmEdit through the API:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50356#c3
+
+Would that be possible for extension:Translate to deal with it?",1378368406,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"(In reply to comment #7)
+> I'm also impacted by this issue and I agree, if the API does not provide the
+> necessary tools then it seems to me complicated to deal with this. How does
+> the
+> VisualEditor? He is impacted?
+
+It was: bug 50356 / https://gerrit.wikimedia.org/r/#/c/71160/ .",1378366693,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"I'm also impacted by this issue and I agree, if the API does not provide the necessary tools then it seems to me complicated to deal with this. How does the VisualEditor? He is impacted?",1378365600,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,*** Bug 42161 has been marked as a duplicate of this bug. ***,1353012086,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"ConfirmEdit can be configured per namespace, you can just disable it on translations: namespace with $wgCaptchaTriggersOnNamespace as a (partial) workaround?",1328450883,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"**qbphcqdw** wrote:
+
+%%%*** Bug 34197 has been marked as a duplicate of this bug. ***%%%",1328365291,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,It is not easy to fix since all edits go through the API through normal saving mechanism.,1328329139,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"**aokomoriuta** wrote:
+
+To avoid this error, I can edit the message directly (Translating:XXX) instead of editing through Special:Translate.
+So as First Aid, it seems good to modify the error message in Special:Translate ""Saving failed. Please report this error."" to ""You need edit this message directly to pass CAPTCHA."".",1328272304,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Special:Translate unable to save where CAPTCHA is required,"Nice find. Will look into this. To avoid actual spamming, I think we should only allow this if there are no warnings on the translation, ie changed links that would cause fuzzy markings.",1328261459,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-gzce6zqlyqcwjilrw6bf,task_subcomment,NA
+Spell check not working in VisualEditor interface,"**Author:** `utsavsabharwal`
+
+**Description:**
+I wrote following line and was expecting the editor to help me with the spell of gud and notify me about invalid word 'Yra' but it dint :(
+
+""Yra Utsav is gud boy ""
+
+I am using Chromium 15.0.874.106 (Developer Build 107270 Linux) Ubuntu 11.10
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1325686140,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-arr3l5eisybqnti6pj5e,task_description,resolved
+Spell check not working in VisualEditor interface,Noting bugs closed in the 2012-10-15 release.,1351534201,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341859,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,Fixed with new version of VE (built-in behaviour).,1340398658,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,"(In reply to comment #1)
+> Browser's native spell checker probably won't work with visual editor...
+
+Is this still the case?",1340395213,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,"**utsavsabharwal** wrote:
+
+Is there any possible way user can check for spells while using VE?",1325711769,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+Spell check not working in VisualEditor interface,Browser's native spell checker probably won't work with visual editor...,1325704678,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-arr3l5eisybqnti6pj5e,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","See URL for an example.
+
+Revision 97771495 is flagged as ""automatically checked"" though the previous version isn't. I think this is what happened:
+
+1. The base version is the version from 17:14 (CET), a flagged version.
+2. Elmar Nolte (with autoreview right) starts to edit.
+3. The IP starts to edit and saves first. The revision is not flagged.
+4. Elmar Nolte saves. The software detects an edit conflict which is resolved automatically. So no warning is shown. The FR extension still sees this edit based on the previous flagged version and flags the new revision as automatically checked.
+
+But in fact Elmar Nolte's revision is based on the unflagged revision by the IP and should not be flagged automatically.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://de.wikipedia.org/w/index.php?title=Emanuel_Semper&action=history&uselang=en",1325581020,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_description,resolved
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","Change 72265 merged by Demon:
+Various edit conflict handling fixes
+
+https://gerrit.wikimedia.org/r/72265",1374014464,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","Change 72265 had a related patch set uploaded by Aaron Schulz:
+Various edit conflict handling fixes
+
+https://gerrit.wikimedia.org/r/72265",1373136660,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","Neither edit is tagged as such, so no.",1373096935,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict",Does this require VisualEditor to reproduce?,1373095980,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","Reopening: This happened again in https://de.wikipedia.org/w/index.php?title=Allgemeines_b%C3%BCrgerliches_Gesetzbuch&action=history
+
+There are three relevant edits (all times in CEST):
+
+(1) IP at 20:42:00
+(2) IP at 20:42:31
+(3) Botulph at 20:42:49
+
+Edit (3) was started after (1), but before (2), and is just a revert of edit (1) via the ""undo"" function. The edit conflict with edit (2) was automatically resolved, but (3) was automatically checked, though of course it shouldn't.",1373095755,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","(In reply to comment #4)
+> Are there any other known instances?
+
+I tried to reproduce it on http://de.wikipedia.beta.wmflabs.org/w/index.php?title=Testseite&action=history, but apart from the fact that at first my login cookie get lost everything worked as expected. So I'm closing this bug for now.",1329122473,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict",Are there any other known instances?,1328915576,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","(In reply to comment #2)
+> Was Elmar editing the page for 55+ seconds for such a small change? I suppose
+> it's possible.
+
+I think 55+ seconds for: starting link dialog from WikiEditor, messing around, inserting the link, clicking preview, testing the link, wondering why it doesn't work, deciding to save anyway is not very long, so definitely possible.",1326098197,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict","(cur | prev) 2011-12-31T16:16:56‎ Elmar Nolte (Talk | contribs)‎ (1,701 bytes) (undo) [automatically checked]
+(cur | prev) 2011-12-31T16:16:01‎ 91.39.161.225 (Talk)‎ (1,542 bytes) (kat, nd, pd) (undo)
+(cur | prev) 2011-12-31T16:14:59‎ Elmar Nolte (Talk | contribs)‎ (1,162 bytes) (undo) [automatically checked]
+
+Was Elmar editing the page for 55+ seconds for such a small change? I suppose it's possible.",1326091809,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+"Revision wrongly flagged as ""automatically checked"" after edit conflict",maybeMakeEditReviewed() already checks for this (https://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/FlaggedRevs/backend/FlaggedRevs.hooks.php?revision=106746&view=markup). I'm not sure how this can happen.,1326072983,PHID-USER-bmbmvb2e5bg6ztcangbq,False,PHID-TASK-sx2ogxi3akejlbpibw6h,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"- it is documented at [[ https://www.mediawiki.org/wiki/Repositories_with_Ruby_code | Repositories with Ruby code ]] page?
+- is ruby syntax check running after every commit?
+- is rubocop  running after every commit?
+- is browser test jenkins job created? (optional)
+
+Repositories:
+
+gerrit
+
+|name|ruby|rubocop|
+|mediawiki/core|1.9.3|0.32.1|
+|mediawiki/extensions/ArticleFeedbackv5|1.9.3|0.26.1|
+|mediawiki/extensions/CentralAuth|1.9.3|0.29.1|
+|mediawiki/extensions/CentralNotice|1.9.3|0.29.1|
+|mediawiki/extensions/CirrusSearch|1.9.3|0.26.1|
+|mediawiki/extensions/ContentTranslation|1.9.3|0.29.1|
+|mediawiki/extensions/Echo|1.9.3|0.29.0|
+|mediawiki/extensions/Flow|1.9.3|0.32.1|
+|mediawiki/extensions/Gather|1.9.3|0.34.1|
+|mediawiki/extensions/GettingStarted|1.9.3|0.29.1|
+|mediawiki/extensions/Math|1.9.3|0.27.0|
+|mediawiki/extensions/MobileFrontend|1.9.3|0.29.1|
+|mediawiki/extensions/MultimediaViewer|1.9.3|0.29.1|
+|mediawiki/extensions/PageTriage|1.9.3|0.26.1|
+|mediawiki/extensions/PdfHandler|1.9.3|0.26.1|
+|mediawiki/extensions/PoolCounter|1.9.3|0.27.1|
+|mediawiki/extensions/QuickSurveys|1.9.3|0.29.1|
+|mediawiki/extensions/Translate|1.9.3|0.26.1|
+|mediawiki/extensions/TwnMainPage|1.9.3|0.26.1|
+|mediawiki/extensions/UniversalLanguageSelector|1.9.3|0.29.1|
+|mediawiki/extensions/UploadWizard|1.9.3|0.29.1|
+|mediawiki/extensions/VisualEditor|1.9.3|0.32.1|
+|mediawiki/extensions/WikiLove|1.9.3|0.26.1|
+|mediawiki/extensions/ZeroBanner|1.9.3|0.26.1|
+|mediawiki/extensions/ZeroPortal|1.9.3|0.26.1|
+|mediawiki/ruby/api|1.9.3|0.29.1|
+|mediawiki/selenium|1.9.3|0.29.1|
+|mediawiki/vagrant|1.9.3|0.33.0|
+|oojs/ui|2.0|0.27.1|
+|operations/puppet|1.9.3|0.33.0|
+|VisualEditor/VisualEditor|1.9.3|0.29.1|
+
+github
+
+|name|ruby|rubocop|
+|amire80/commons_upload|2.2.0|0.33|
+|amire80/screenshot.git|2.2.0|?|
+|wmde/WikidataApiGem|1.9.3|-|
+|wmde/WikidataBrowserTests|1.9.3|0.32.1|",1416490011,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_description,resolved
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237373 merged by jenkins-bot:
+Run Ruby syntax check for mediawiki/vagrant in experimental pipeline
+
+[[https://gerrit.wikimedia.org/r/237373]]",1442085611,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237375 merged by jenkins-bot:
+Run Ruby syntax check for operations/puppet in experimental pipeline
+
+[[https://gerrit.wikimedia.org/r/237375]]",1442085294,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237638 merged by jenkins-bot:
+Ruby Ruby syntax check and RuboCop for PoolCounter
+
+[[https://gerrit.wikimedia.org/r/237638]]",1442084457,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237638 had a related patch set uploaded (by Zfilipin):
+Ruby Ruby syntax check and RuboCop for PoolCounter
+
+[[https://gerrit.wikimedia.org/r/237638]]
+",1441974783,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237375 had a related patch set uploaded (by Zfilipin):
+Run Ruby syntax check for operations/puppet in experimental pipeline
+
+[[https://gerrit.wikimedia.org/r/237375]]
+",1441893216,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 237373 had a related patch set uploaded (by Zfilipin):
+Run Ruby syntax check for mediawiki/vagrant in experimental pipeline
+
+[[https://gerrit.wikimedia.org/r/237373]]
+",1441892621,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 200863 abandoned by Zfilipin:
+WIP Run Ruby syntax check and/or RuboCop for repositories with Ruby code
+
+[[https://gerrit.wikimedia.org/r/200863]]",1441891623,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,,1442423278,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,,1428487153,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Change 200863 had a related patch set uploaded (by Zfilipin):
+WIP Ruby Ruby syntax check and/or RuboCop for repositories with Ruby code
+
+[[https://gerrit.wikimedia.org/r/200863]]
+",1427811423,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running,"Feel free to add a step by step tutorial for ruby repositories, we have a few already: https://www.mediawiki.org/wiki/Continuous_integration/Tutorials . ",1427809449,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-a7wc4l7yt5s7l3dos7zx,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,"At the moment, we have a couple of jenkins jobs:
+
+  - [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-VisualEditor-language-screenshot-linux-firefox/ | browsertests-VisualEditor-language-screenshot-linux-firefox ]]
+  - [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-VisualEditor-language-screenshot-linux-firefox-sauce/ | browsertests-VisualEditor-language-screenshot-linux-firefox-sauce ]]
+
+The first job runs local firefox and fails randomly.
+
+Options:
+
+- check if any of the headless environment variables helps
+- check if any of the reuse browser environment variables helps
+- check if switching to local chromium helps
+
+The second job run a remote browser on sauce labs, but it does not support Chinese and Japanese fonts (at least), but only on linux host.
+
+- check if running the job on windows (or mac) helps.",1416327470,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tig5qf53lxx7q22k3ipg,task_description,resolved
+browsertests-VisualEditor-language-screenshot jenkins job failing,"It was moved to run on Mac, and now runs successfully.",1424769575,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,"Some more context:
+
+Already reported as [bug 71602 - mediawiki_selenium always use the same default xvfb display 99](https://bugzilla.wikimedia.org/show_bug.cgi?id=71602), which explains how our jobs ends up killing each other XVFB (typical race condition).
+
+Dan fixed it with https://gerrit.wikimedia.org/r/#/c/164704/ ( b6af34a40e ) which is included in mediawiki_selenium 0.4.1.
+
+The jobs need to be bumped to that library version and use the appropriate env variables as described above.",1416479930,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,"The job has `BROWSER=firefox` and `HEADLESS=false`, I am not sure what happens exactly in some case.  We probably want to set `HEADLESS=true` and set HEADLESS* env variables to avoid killing the XVFB.
+
+The relevant code for 0.4.1 is:
+
+http://git.wikimedia.org/blob/mediawiki%2Fselenium/0.4.1/lib%2Fmediawiki_selenium%2Fsupport%2Fhooks.rb#L27
+
+See also the `README.md` doc under ""Headless mode"" section: http://git.wikimedia.org/blob/mediawiki%2Fselenium/0.4.1/README.md
+
+I think we want:
+
+```
+lang=sh
+HEADLESS=true
+HEADLESS_DESTROY_AT_EXIT=false
+```
+
+That will default to use display 99, we have an XVFB listening on 99 already.
+
+If we want the headless gem to spawn a new xvfb on a different display port, we can use `HEADLESS_REUSE=false` which will make it spawn a new xvfb on a different display port.  But that is probably not needed.",1416479618,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,">>! In T1321#23186, @hashar wrote:
+> Can you confirm you have mediawiki_selenium 0.4.1 +
+
+Yes.
+
+```
+00:03:37.335 Installing mediawiki_selenium 0.4.1
+00:03:37.335 0:  mediawiki_selenium (0.4.1) from /mnt/jenkins-workspace/workspace/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/LANGUAGE_SCREENSHOT_CODE/ar/label/gems/2.0.0/specifications/mediawiki_selenium-0.4.1.gemspec
+```
+
+From:
+
+https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/LANGUAGE_SCREENSHOT_CODE=ar,label=contintLabsSlave%20&&%20UbuntuTrusty/1/console
+",1416477168,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,Related commit: https://gerrit.wikimedia.org/r/#/c/174660/,1416476604,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+browsertests-VisualEditor-language-screenshot jenkins job failing,"Can you confirm you have mediawiki_selenium 0.4.1 +
+
+And:
+
+    export HEADLESS_DESTROY_AT_EXIT=false
+
+See https://bugzilla.wikimedia.org/show_bug.cgi?id=71602#c6",1416332893,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-tig5qf53lxx7q22k3ipg,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"It's not immediately clear which projects should be in the actual message. As things are looking now, just team and project is OK, but maybe tags should also be added.
+
+See https://github.com/legoktm/wikibugs2/commit/f2d91f6e6a1d8ccba54041d3376ed7719585c8d3 -- all tags should be reported to the IRC bot, not just projects.
+
+
+See also:
+ -  T1209 - Add 'team' (purple) to output
+ - T1122 - Don't include closed projects in wikibugs2 output",1416306634,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_description,resolved
+Team (and other non-project) tags should be available for filtering,{icon umbrella},1423341471,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"Change 184864 merged by jenkins-bot:
+Disentangle tag lists for filtering vs display
+
+[[https://gerrit.wikimedia.org/r/184864]]",1421233290,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"Change 184864 had a related patch set uploaded (by Yuvipanda):
+Disentangle tag lists for filtering vs display
+
+[[https://gerrit.wikimedia.org/r/184864]]
+
+#patch-for-review",1421229729,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"VE now works, thanks.",1418937435,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"Change 179088 merged by jenkins-bot:
+T1316: Also report {icon umbrella} projects
+
+[[https://gerrit.wikimedia.org/r/179088]]",1418755053,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"Change 179088 had a related patch set uploaded (by Merlijn van Deen):
+T1316: Also report {icon umbrella} projects
+
+[[https://gerrit.wikimedia.org/r/179088]]
+
+#patch-for-review",1418283449,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,Argh. Should we remove the umbrella for now?,1418252786,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,I have been told that this is what causes tasks in #VisualEditor not to be reported on #mediawiki-visualeditor since the project has gained the umbrella icon. What do we do to fix that?,1418251394,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"> ...but should not be reported in-channel in the channel list.
+
+As said in my comment above, if you filter out tasks belonging to Team projects, it is likely that you will miss many tasks. ",1417376464,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Team (and other non-project) tags should be available for filtering,"As discussed on IRC, I see no reason why ""team"" type of projects cannot be used to handle tasks themselves, and I see no reason to treat them differently than ""suitcase"" projects. If we don't use team projects for managing the team backlog, then the only reason to create a team project would be to handle some special permissions.",1416308316,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-zf6z6dd2eewg4w66u3vr,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"We don't have any real need for 1.23wmf* and 1.24wmf* deployment branches anymore. They should probably be changed to tags.
+
+Chad, do you have a script for doing this? Timo seemed to think you had from before...
+
+-----
+**EDIT**: Krinkle used the following script for individual repositories at [https://github.com/Krinkle/dotfiles/tree/master/hosts/KrinkleMac/bin](https://github.com/Krinkle/dotfiles/tree/db0e65f/hosts/KrinkleMac/bin):
+{P3455}
+{P531}",1416143148,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_description,resolved
+Remove old wmf/* deployment branches (recurring chore),This is done.,1494861695,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),So I think the last thing to do here is to automate this a bit. I'm going to add it to `scap clean`,1486674812,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),,1486674758,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),,1468868164,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Done for all extensions, skins and vendor. No more extraneous tags. No more branches other than the currently active series, `1.28.0-wmf.N`",1468544824,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"I agree, all those old tags and branches aren't very useful after a while.",1468527573,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"One liner for all extensions and skins meta repos:
+```
+lang=bash
+# Delete all remote branches matching wmf/ that aren't 1.28-based
+git submodule foreach ""git branch -r | grep -Eo 'wmf/.*' | grep -v '1.28' | xargs -I {} git push origin :{}""
+# Delete all (remote) tags named wmf/* 
+git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git push origin :{} ||:""
+# Delete the tags locally too, so we don't re-push them.
+git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git tag -d {}""
+```
+
+Just gotta swap `1.28` for whatever branch you're wanting to retain (the current one, obviously).
+
+Just ran this for all skins and the vendor directory. Finishing up extensions now.
+
+Let's please not reintroduce these tags. And get better (via the child task) at cleaning up the branches automatically.",1468532493,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"One liner for all extensions and skins meta repos:
+```
+lang=bash
+  # Delete all remote branches matching wmf/ that aren't 1.28-based
+  git submodule foreach ""git branch -r | grep -Eo 'wmf/.*' | grep -v '1.28' | xargs -I {} git push origin :{}""
+  # Delete all (remote) tags named wmf/* 
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git push origin :{} ||:""
+  # Delete the tags locally too, so we don't re-push them.
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git tag -d {}""
+Just gotta swap `1.28` for whatever branch you're wanting to retain (the current one, obviously).
+```
+
+Just ran this for all skins and the vendor directory. Finishing up extensions now.
+
+Let's please not reintroduce these tags. And get better (via the child task) at cleaning up the branches automatically.",1468532469,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"One liner for all extensions and skins meta repos:
+  git submodule foreach ""git branch -r | grep -Eo 'wmf/.*' | grep -v '1.28' | xargs -I {} git push origin :{}""
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git push origin :{} ||:""
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git tag -d {}""
+Just gotta swap `1.28` for whatever branch you're wanting to retain (the current one, obviously).
+
+Just ran this for all skins and the vendor directory. Finishing up extensions now.
+
+Let's please not reintroduce these tags. And get better (via the child task) at cleaning up the branches automatically.",1468530442,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"One liner for all extensions and skins meta repos:
+  git submodule foreach ""git branch -r | grep -Eo 'wmf/.*' | grep -v '1.28' | xargs -I {} git push origin :{}""
+  git submodule foreach ""git tag | grep -Eo 'wmf/.*' | xargs -I {} git push origin :{}""
+Just gotta swap `1.28` for whatever branch you're wanting to retain (the current one, obviously).
+
+Just ran this for all skins and the vendor directory. Finishing up extensions now.
+
+Let's please not reintroduce these tags. And get better (via the child task) at cleaning up the branches automatically.",1468527268,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Also we should prune old branches for extensions/skins/vendor too, I only do it for core right now.",1468427386,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Actually, I'd like to repurpose this as ""Just kill old branches."" The tags are useless and clutter shit up which is why I nuked all of them a few weeks ago.",1468427366,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Ran `convert-wmf-branches 1.26` on repos `mediawiki/core` and `mediawiki/extensions/{VisualEditor,NavigationTiming}`.",1444186214,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"(Re-opening, since there are still plenty of extensions with them, and it will happen again every release cycle)",1433778273,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),Maybe the make-wmf-branch could be taught how to convert obsolete branches to tags? This way the conversion will be part of the process and we could close this task.,1430388828,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"I've ran the script for 1.25 on mediawiki/core and the following mediawiki extension repositories I have checked out:
+```
+CategoryTree
+CentralNotice
+CirrusSearch
+Cite
+Citoid
+CodeReview
+Collection
+ContentTranslation
+CvnDB
+Echo
+EventLogging
+Flow
+Gadgets
+GlobalCssJs
+GlobalUserPage
+GuidedTour
+ImageMetrics
+Interwiki
+Math
+MobileFrontend
+MultimediaViewer
+ParserFunctions
+Scribunto
+Sentry
+SyntaxHighlight_GeSHi
+TemplateData
+Thanks
+Translate
+UniversalLanguageSelector
+VisualEditor
+WikiEditor
+WikimediaEvents
+ZeroBanner
+```",1429293156,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),if there's no harm in keeping the tags around it sounds like a good idea to have them,1418979797,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Updated the script and published to P531. It now works for both MediaWiki core and extensions. And it also removes the branches afterward (instead of requiring manual action via Gerrit dashboard). Note that this requires Gerrit administrator permissions to run.
+
+{P531}",1429291127,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Tried the following on `mediawiki/extensions/TemplateData` as test. Seems to work fine.
+
+```
+#!/usr/bin/env bash
+remote='origin'
+versions=('1.23' '1.24')
+git remote update $remote
+git remote prune $remote
+for version in ""${versions[@]}""; do
+	refs=`git for-each-ref --format='%(refname)' refs/remotes/${remote}/wmf/${version}wmf*`
+	for ref in $refs; do
+		branch=$(echo $ref | cut -d '/' -f 4-6)
+		git push origin "":$branch""
+	done
+done
+git remote update $remote
+git remote prune $remote
+```",1418224167,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Tried the following on `mediawiki/extensions/TemplateData` as test. Seems to work fine.
+
+```
+#!/usr/bin/env bash
+remote='origin'
+version='1.23'
+git remote update $remote
+git remote prune $remote
+refs=`git for-each-ref --format='%(refname)' refs/remotes/${remote}/wmf/${version}wmf*`
+for ref in $refs; do
+	branch=$(echo $ref | cut -d '/' -f 4-6)
+	git push origin "":$branch""
+	if [[ $? == 0 ]]; then
+		echo ""... deleted $branch""
+	else
+		echo ""Could not delete $branch""
+	fi
+done
+git remote update $remote
+git remote prune $remote
+```",1418223467,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),I have no real strong opinions about keeping them around.,1417915635,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"@hashar At this point this is only happening to wmf branches. After a MediaWiki core wmf-branch is abandoned, we definitely wouldn't be backporting patches for an individual extension's wmf-branch as the relevant wmf-branch wouldn't be deployed anymore (and couldn't as you'd have to update the submodule pointer in the MediaWiki core branch that no longer exists).
+
+For release branches this is different. Extension authors may maintain their extensions' release branch beyond MediaWiki core's end-of-life data for a release. But so far we haven't purged any release branches.
+
+@Reedy @Chad As for wmf-branches in extensions, I'd like to remove them instead of converting to tags. Do we need them for anything? The submodule pointers from the wmf-branches in mediawiki-core refer to commits, not branches. Having said that, should we keep them even in MediaWiki core? It's not like we'd revert back an entire major release in production.",1417907159,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"That might break zuul-cloner which expects to checkout branches which is used for {T1350} among others. (link: https://www.mediawiki.org/wiki/RFC/Extensions_continuous_integration ).
+
+I have filled {T76088} to investigate whether zuul-cloner will be able to consider tags instead of branches.",1417035950,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),I don't see any reason we couldn't. It would be running the same script essentially for all of our submodules,1417024817,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),Can this also be done for extensions as well?,1417021844,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"I created tags for `wmf/1.23wmf*` and `wmf/1.24wmf*` and deleted the branches.
+
+Script:
+
+```
+#!/usr/bin/env bash
+remote='origin'
+version='1.24'
+git remote update $remote
+git remote prune $remote
+refs=`git for-each-ref --format='%(refname)' refs/remotes/${remote}/wmf/${version}wmf*`
+for ref in $refs; do
+	branch=$(echo $ref | cut -d '/' -f 4-6)
+	git tag $branch $ref > /dev/null 2>&1
+	if [[ $? == 0 ]]; then
+		echo ""... tagged $branch""
+	else
+		echo ""Could not (re)create $branch""
+	fi
+done
+echo
+echo ""Ask a Gerrit admin to delete wmf/$version branches via https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/core,branches""
+echo
+echo ""... publishing tags""
+git push $remote --tags
+git remote update $remote
+git remote prune $remote
+```",1417017368,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+Remove old wmf/* deployment branches (recurring chore),"Nope, no script for that.",1416152277,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-f7bxhifsd4lp32e2eisz,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,Something like PACE minimal or barbershop http://github.hubspot.com/pace/docs/welcome/,1415512766,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_description,resolved
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Ed reviewed and merged the changaes, and the new loading indicator can now be seen on Beta, e.g. <https://en.m.wikipedia.beta.wmflabs.org/wiki/Digital_object_identifier>. It will go live on production sites next week, 18-20 June, per the usual train deployment schedule.",1560458973,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Sure, he's alright ;) (or any engineer who has the time to look at it)",1560369147,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,code review from @Esanders? ,1560369041,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,I'm waiting for code review of the two patches linked at T217784#5179052.,1560348693,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,@matmarex what's the status of this now?,1560259122,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,👍to upload the version without the intermediate stage and add in the subtle slide down transition. ,1559750692,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Sure, done. (I'll note that this makes the editor switch dropdown inaccessible until both the editor code and the content has loaded.)",1559747247,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Looking at the animation again, I see that have you an intermediate stage once the editor switcher and publish button are available that truncates the loading message:
+|1|2|3
+|{F29232417}|{F29232426}|{F29232430}
+
+While I can see the advantage of showing progress being made by showing elements as they become available, I think the fact there is no transition from 1 to 2 and the truncation of the message means we should probably just go straight from 1 to 3.
+
+CC @iamjessklein ",1558701430,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Fine by me if that was the intention.
+
+I think this just leaves Ed's question about whether the placeholder toolbar should slide in (like the real toolbar does currently), or if it should appear instantly (as seen in the videos I posted: T1181#5179055).",1558550713,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,">>! In T1181#5179055, @matmarex wrote:
+> I am not entirely sure if you wanted the new design to remove the old blue progressbar? For now I removed it, but I feel like now it's less obvious when the loading actually completed – previously the large blue progressbar disappearing made it more noticeable, now it's only a small grey spinner that is replaced by the page title.
+
+In my opinion the text going from disabled/gray to enabled/black is the obvious indication that the editor has loaded (and also a more contextual indicator than what's happening with the header).",1558396952,PHID-USER-cjbkqgaozso5gfp3xv2n,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Migrating comments from gerrit:
+
+> Ed: Shouldn't the fake toolbar slide in though? I think it should...
+> 
+> Bartosz: I don't think it should. It appears instantly. Other overlays in MF do not have any animations like this; we only added it because it was appearing after a delay.
+> 
+> Ed: Ok, let's run this past Jess. I don't think we necessarily need to model our behaviour on what the rest of MF does, especially in this case as although VE is technically an overlay, it does its best to pretend it isn't.
+
+(ping @iamjessklein)",1558128761,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,The videos are showing the slower end of our expected loading times (~5s). I think the median load time is less than 2s and for quick loads a progress bar can feel a bit heavy. Unfortunately we can't know ahead of time how long the page will take to load.,1557839010,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"@iamjessklein I'd be interested to hear how the current take on the spinner came together. Although it might have been used in Foundation products, it has never been a standard widget as stated in T75972.
+I really like the progress made on the ticket, but share @matmarex' take on the spinner being less noticeable and think an indeterminate progressbar underneath the toolbar could be a viable alternative.
+
+Let me know about your thoughts…",1557838642,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"@iamjessklein I'd be interested to hear how the current take on the spinner came together. Although it might have been used in Foundation products, it has never been a standard widget as stated in T75972.
+I really like the progress made on the ticket, but share @matmarex' take on the spinner being less noticeable and think an indeterminate progressbar underneath the toolbar could be a viable alternative.",1557838620,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I implemented this, see patches on T217784#5179052. A few videos showing how it looks like (with artificially slowed down loading):
+
+{F29047838}
+
+{F29047839}
+
+{F29047837}
+
+I am not entirely sure if you wanted the new design to remove the old blue progressbar? For now I removed it, but I feel like now it's less obvious when the loading actually completed – previously the large blue progressbar disappearing made it more noticeable, now it's only a small grey spinner that is replaced by the page title.",1557802458,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"This is a modified rendering of the current overlay, so using the correct icons/fonts/sizes:
+
+{F28464346,size=full}",1553525562,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"*When we implement it,  let's test the longest message on the narrowest screen with an ellipsis and then troubleshoot
+* +1 to CSS
+
+So, it looks like this ticket is ready to move over into ""Ready for Pickup"" - for engineers. ",1553521801,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"> I wasn't clear on the value of the ... after the word Loading Editor. Is this a semantic thing that I'm missing?
+
+It is just commonly used affordance to indicate that the action is ongoing. It is already used in some places in MediaWiki (e.g. `""apisandbox-loading"": ""Loading information for API module \""$1\""..."",`, `""unwatching"": ""Unwatching..."",`, `""importstart"": ""Importing pages..."",`)
+
+> I defer to you on CSS vs. gif - I suspect the CSS would decrease loading time and if that's true, +1
+
+Not sure which is fewer bytes, but the CSS will look better on high DPI devices.
+
+> Re: spacing - I was thinking the spacing between the close button and divider and the divider and start of spinner would be the same and then the space between the spinner and text would be 1/3 of that space. In the image below, I've used two gifs( for the close button and spinner) so the sizes aren't 100% accurate
+
+Sounds good.",1553518050,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"@Esanders
+
+* Good call on spinner+message reading as one, but practically speaking, they are different elements.
+* The text is not bold, it just appears that way due to the contrast with the opacity of the overlay
+* I wasn't clear on the value of the ... after the word Loading Editor. Is this a semantic thing that I'm missing? 
+* I defer to you on CSS vs. gif - I suspect the CSS would decrease loading time and if that's true, +1
+* Re: spacing - I was thinking the spacing between the close button and divider and the divider and start of spinner would be the same and then the space between the spinner and text would be 1/3 of that space. In the image below, I've used two gifs( for the close button and spinner) so the sizes aren't 100% accurate
+* We should default to what is currently used for close button and text
+
+Whenever we do implement this, please shoot my way for a design review before shipping.
+
+{F28449899 width = 300}",1553343533,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Side note: we've historically used a gif for that loading spinner, but we could just as easily do it in CSS: https://loading.io/css/",1553272276,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Minor nitpicks for when we implement:
+* The text looks like it might be bold, it probably shouldn't be
+* The spacing between the spinner are the text should be reduced. If the spinner has the same spacing either side as the close icon, it looks like there are three separate componenets: close, spinner, message, whereas I think it should look more like: close, spinner+message
+* We can probably probably have a text ellipsis after the message, i.e. ""❋ Loading editor...""",1553272162,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I've iterated a bit in freehand and here's my latest proposal:
+
+{F28443955 width=300}
+
+**Notes:**
+
+* ""Editor wird geladen"" is German for ""Loading Editor""
+* The spinner animates indeterminately 
+* The height of the toolbar is 48px  here, there seems to be some back and forth about the height size though, so we should probably decouple that and resolve the issue over in T209015
+* In the event of text overflow, the string should be truncated with ellipsis 
+* This designed has been positively reviewed by @alexhollender and @cmadeo 
+
+Thoughts? Can I have 👍 or 👎 @Volker_E @Esanders ",1553270954,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"An ellipsis is a (as in one) typographic character with three dots, `…` vs `...` – depending on the font the three dots might look widely stretched, in any case they are always typographically wrong.",1553016488,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I'm not a big fan of the loading dots being used inline. They have only been used once before which is in CX (see T75972) where they are centred on the screen with more padding and at a larger size.
+
+I think it also looks odd because the three dots are based on the horizontal ellipsis in typography, and these would usually appear after text (although in this context I'm not sure that would help).
+
+In an inline context I would be more accustomed to seeing the rotating spinner used elsewhere in MobileFrontend, similar to:
+
+{F28420760}
+
+The only other animation I can think of seeing inline is an actual ellipsis, e.g. `Loading.` -> `Loading..` -> `Loading...` (repeat), but I'm not sure if this approach translates well to every script.",1553006434,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I'm thinking something pretty basic, keep the background color white and the close button on the left to have parody with the actual toolbar. In this instance, I've added the 3 loading dots as well.
+
+{F28420543 width = 300}",1553000312,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,This relates to T214477,1551721039,PHID-USER-ujgufealwngqoe65jj3h,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,Related to {T99274},1483649011,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,Thanks.,1422851460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"I didn't tag it easy, but I've removed it.",1422851437,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+VisualEditor loading indicator should feel more integrated into the mobile interface,"Is this really ""easy""?",1422849721,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ok2zr74rwqedp7qc3cko,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"The goal is to have good descriptions in the most relevant videos at https://www.youtube.com/user/watchmediawiki
+Links to all past tech talk videos: https://www.mediawiki.org/wiki/Tech_talks#Past_tech_talks
+
+Step 1: Add one-line bio of the speaker(s) of the video
+Step2: Go through the video and extract relevant links
+Step3: Add the new description to commons
+
+Template for the description:
+-Speaker Name (Their one-line bio)
+-Summary
+-Relevant links
+
+
+| Youtube video | Description in Youtube | Description in Commons | Embedded in Wikimedia pages
+| [[ https://www.youtube.com/watch?v=Qo4XIzCJZVs | Tech Talk: New readership data]] | Done | [[ https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm#.7B.7Bint:filedesc.7D.7D | Done]] | 
+|[[https://www.youtube.com/watch?v=_yr5z9Ix2f8 | Phabricator for Wikimedia projects]] | Done | [[https://commons.wikimedia.org/wiki/File:Phabricator_for_Wikimedia_projects.webm | Done]] | |
+| [[https://www.youtube.com/watch?v=ltEL-kPURKs |Automated citations in Wikipedia]] |Done | [[https://commons.wikimedia.org/wiki/File:Tech_Talk_-_Automated_citations_in_Wikipedia_-_Citoid_and_the_technology_behind_it.webm#.7B.7Bint:filedesc.7D.7D | Done]] | 
+| [[https://www.youtube.com/watch?v=sWiDimlK4bE |  Introduction to Free and Open Source Licensing at Wikimedia]] | Done | [[https://commons.wikimedia.org/wiki/File:Tech_Talk_-_Introduction_to_Free_and_Open_Source_Licensing_at_Wikimedia.webm | Done]] | |
+",1415224479,PHID-USER-vcyz3oe6mrt5w42lpqeh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_description,resolved
+Add documentation links to TechTalk Youtube Videos ,"Similarly to {T142728}, I think this task has run its course. Thank very much for your help @husn_shujaat!
+
+@Rfarrand @srishakatux from now any any new Tech Talk should have beforehand a proper plan for
+
+* being published in YouTube with a proper title, description, and whatever information will make them easier to be found
+* being published in Commons short after the event with the same
+* being embedded in the right wiki pages so they can be found by the people checking that documentation.
+
+I hope you will agree with this sensible plan not to increase our ""communication debt"" with Tech Talks.",1505207051,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,Imported as https://codein.withgoogle.com/tasks/5210795455545344/,1481282294,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@srishakatux this is perfect! Thank you :),1481280158,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@Aklapper @husn_shujaat I created a playlist for 'Tech talks' on our Youtube channel. All tech talks now lie here https://www.youtube.com/playlist?list=PLeoTcBlDanyMPuVYBZYbEORNezmemiAhv. I've created a GCI task about adding documentation for tech talk videos: https://codein.withgoogle.com/dashboard/tasks/5210795455545344/preview/. I haven't published it yet, but I have tried to frame the description as such that we could have several instances of it, where each student could choose to work on two videos at one time. If this sounds good, I will create a similar task with some additions for the one on CREDIT showcase and update the instance count to 5ish. 
+",1481242457,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@Aklapper @husn_shujaat I created a playlist for 'Tech talks' on our Youtube channel. All tech talks now lie here on Youtube https://www.youtube.com/playlist?list=PLeoTcBlDanyMPuVYBZYbEORNezmemiAhv. I've created a GCI task about adding documentation for tech talk videos: https://codein.withgoogle.com/dashboard/tasks/5210795455545344/preview/. I haven't published it yet, but I have tried to frame the description as such that we could have several instances of it, where each student could choose to work on two videos at one time. If this sounds good, I will create a similar task with some additions for the one on CREDIT showcase and update the instance count to 5ish. 
+",1481242383,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Ah, right. I'll put the page with links in the description.
+Yeah, they can add the description in the commons, I'll put it to youtube :)",1480277022,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Ah, right. I'll put the page with links in the description.",1480276983,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Alright, so this would refer to Commons only...  :)
+So as a student, how exactly would I find a video that still needs some documentation links added?",1480273284,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"If I was a student, what will I have to do after extracting relevant links? Where I am expected to add a one-line bio of the speaker?
+The thing is: We need to clearly communicate expectations to students, to avoid misunderstandings or wrong expectations on both sides :)",1480273179,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@Aklapper Take my place for the time being. Go through the video and extract the relevant links. Add a one-line bio of the speaker. :)
+The summary is usually already there.
+This all goes into the description of the video in commons",1480272846,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Aklapper Take my place for the time being. Go through the video and extract the relevant links. Add a one-line bio of the speaker. :),1480272735,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@husn_shujaat: If this was a GCI task, what exactly would be expected from a GCI student here? :)",1480271701,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I wonder if I could put this as a Google Code-In task.
+Like, 1 task would include 1 video and so this could be a recurring task.",1480178943,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,I wonder if I could put this as a Google Code-In task.,1480178732,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@husn_shujaat do you want to keep working on this task during this quarter?,1475577364,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Aklapper that worked! thanks :),1474125573,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#2554781, @husn_shujaat wrote:
+> When I add link of a speaker's profile, there is usually a ')' at its end, and youtube's code refuses to include that in the URL, so we end up with an invalid page. What to do?
+
+@husn_shujaat: Instead of entering `https://wikimediafoundation.org/wiki/User:Slaporte_(WMF)` could you try encoding the brackets by using `https://wikimediafoundation.org/wiki/User:Slaporte_%28WMF%29` maybe? Just an idea how to work around...",1473623568,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"You are right! I have tried to edit the description using Markdown syntax or HTML but it won't work either.
+
+Well... then I think it is better not to specify those wrong links and point to their team pages instead. Team pages are going to be more informative than most user pages anyway.",1471300768,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"There is tiiiiny bit problem at youtube. When I add link of a speaker's profile, there is usually a ')' at its end, and youtube's code refuses to include that in the URL, so we end up with an invalid page :/ 
+See https://www.youtube.com/watch?v=sWiDimlK4bE
+What to do?",1471289121,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,Good idea. You can [[ https://www.mediawiki.org/wiki/Phabricator/Help#Creating_a_task | create the task ]] yourself. Let me know if you have any questions.,1470826083,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Good idea. I'll get the two at commons done. 
+But I think we should create a seperate task for CREDITs . 
+Let this one be for tech talks only.",1470748299,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"A related comment:
+
+>>! In T85593#2514784, @Qgil wrote:
+> Here is another approach to this task: let's focus on assuring that current and future presentations are properly published in their related mediawiki.org pages. At least we will avoid making this problem bigger.
+
+We could apply the same idea to new videos produced. For instance, there was a [[ https://www.mediawiki.org/wiki/CREDIT_showcase | CREDIT showcase ]] last week:
+
+Stream: https://www.youtube.com/watch?v=BOj6nDbdPMA
+Stas: small WDQS GUI updates - https://www.mediawiki.org/wiki/Wikidata_query_service
+
+",1470645931,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"A related comment:
+
+>>! In T85593#2514784, @Qgil wrote:
+> Here is another approach to this task: let's focus on assuring that current and future presentations are properly published in their related mediawiki.org pages. At least we will avoid making this problem bigger.
+
+We could apply the same idea to new videos produced. For instance, there was a CREDIT showcase last week:
+
+Stream: https://www.youtube.com/watch?v=BOj6nDbdPMA
+Stas: small WDQS GUI updates - https://www.mediawiki.org/wiki/Wikidata_query_service
+
+",1470645903,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@Aklapper Sorry for missing your pings here, yes! I can give permissions to the YouTube channel. So can Byron, Quim, Chris, James A, & Tilman. 
+Happy to add anyone you want me to. ",1469031343,PHID-USER-vcyz3oe6mrt5w42lpqeh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Rfarrand: Do you know? ^^^,1468934021,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ," In T1119#2194307, @Qgil wrote:
+> while we figure out (this week, I expect) your permissions on MediaWiki's YouTube account.
+
+I'm wondering who knows about these permissions and how to go ahead when it comes to allowing more people to update description of existing Youtube videos.
+@Rfarrand maybe?",1468934009,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Rfarrand: Do you know? ^^^,1468933954,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#2194307, @Qgil wrote:
+> while we figure out (this week, I expect) your permissions on MediaWiki's YouTube account.
+
+I'm wondering who knows about these permissions and how to go ahead when it comes to allowing more people to update description of existing Youtube videos. 
+@Rfarrand maybe?",1467887357,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"So, finally my exams are over. 
+I just got done with https://commons.wikimedia.org/wiki/File:Phabricator_for_Wikimedia_projects.webm ",1465718887,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,@Qgil Thank you so much! :),1460733621,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,Of course @husn_shujaat ! First thing first. I wish you best luck with the exams.,1460699038,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I have my exams starting next week, I'm just too busy.
+I was wondering if I can resume working on this task from June 10 (that's when my exams end)
+Is that OK?",1460669665,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Yes, I'm totally ok with it. 
+I'll now start with https://www.youtube.com/watch?v=_yr5z9Ix2f8 ",1460462260,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"You can edit the list by clicking the ""Edit Task"" link above.
+
+A couple of wiki pages mentioned in the video itself is a good guidance. Let's go for more?
+
+I think it is good to do more videos available in Commons while we figure out (this week, I expect) your permissions on MediaWiki's YouTube account. Are you OK with this?",1460363313,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"That list is very helpful, thanks!
+
+I need help in deciding which tech talk video should be on which wiki page?
+For the start, let's just consider 'The readership data' one.
+So far, @Qgil embedded it in [[https://meta.wikimedia.org/wiki/Research:Characterizing_Wikipedia_Reader_Behaviour| here]] and I embedded it [[https://www.mediawiki.org/wiki/Reading/Mexico_Readers_Research|here]]. Is there any where else where the video should go?",1460311365,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,,1460311302,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,,1460311163,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Thanks so much for this work! Its great. Just a few links for you in case this helps. 
+1) I try to keep this updated with all tech talks, however I have missed a few recently. I will go back and update soon: https://www.mediawiki.org/wiki/Tech_talks
+2) Here is a collection of all of the tech talks we have done in case any are missing:
+https://www.youtube.com/user/watchmediawiki
+
+Let me know if I can help you!",1460133925,PHID-USER-vcyz3oe6mrt5w42lpqeh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Thank you! :)
+I'll see to adding the speaker's description.
+
+I will embed the videos, but I can't get how to put the links to [[ https://commons.wikimedia.org/wiki/Special:WhatLinksHere/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm | this page]]?
+Do you think I should just embed the videos in the links mentioned in the description (except for [[ https://phabricator.wikimedia.org/T113066
+ | T113066 ]] of course)? Will those be enough?
+
+The idea of the table is a great way of keeping track of our progress.",1460027710,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"This is very good! I made [[ https://commons.wikimedia.org/w/index.php?title=File%3ATech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm&type=revision&diff=192443093&oldid=192413368 | some edits ]] to link to the speaker user profile in mediawiki.org, to add some relevant links to the description, and to simplify the format of the list of links (we try to avoid HTML in wikitext when possible).
+
+It would be useful to add a one line description of the speaker, which you can usually borrow from their user profiles.
+
+Finally, clicking at [[ https://commons.wikimedia.org/wiki/Special:WhatLinksHere/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm | What links here ]] one can see that there is no relevant page linking to this video in the entire collection of Wikimedia wikis. This is not useful! You can improve this situation by finding the relevant pages, and embedding the video there.
+
+Let me do this once to provide an example: https://meta.wikimedia.org/w/index.php?title=Research%3ACharacterizing_Wikipedia_Reader_Behaviour&type=revision&diff=15506568&oldid=15428580 (I did it with the regular ""Edit"" / VisualEditor link and the Tech Talk video was already the second result suggested as media, maybe your good description is starting to work semantically?).  :)
+
+I was thinking that we could maintain a table in the description of this task to track progress, along these lines:
+
+| YouTube video | Description in YouTube | Description in Commons | Embedded in Wikimedia pages |
+|  [[ https://www.youtube.com/watch?v=Qo4XIzCJZVs | Tech Talk: New readership data ]] |  | [[ https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm#.7B.7Bint:filedesc.7D.7D | DONE ]] | ",1460010114,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Is this okay?
+https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm#.7B.7Bint:filedesc.7D.7D
+",1459987699,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,,1459987687,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,,1459987409,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"OK!
+I'll start with the description at commons.
+The youtube video is linked at commons but not the other way round.
+I think it's a good idea to have the youtube link at the source in commons as it is in this video.
+
+P.S: It was me who liked it :D",1459981017,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Great! Let's move onto the videos. It makes sense to start with the Tech Talks. We can work on a specific one, and then when we are happy about it, we can apply the same formula to the rest.
+
+I propose to start with this one:
+
+* https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm
+* https://www.youtube.com/watch?v=Qo4XIzCJZVs
+
+After almost three weeks, it has 77 views and 1 like in YouTube, 28 views in Commons. Let's see whether we can drive more YouTube attention there. :)
+
+Since it is available in Commons, we can edit the description there at will, and when we are happy about it we can copy it to YouTube. OK?",1459972680,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Great! Let's move onto the videos. It makes sense to start with the Tech Talks. We can work on a specific one, and then when we are happy about it, we can apply the same formula to the rest.
+
+I propose to start with this one:
+
+* https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm
+* https://www.youtube.com/watch?v=Qo4XIzCJZVs
+
+After almost three weeks, it has 77 views and 1 like. Let's see whether we can drive more YouTube attention there. :)
+
+Since it is available in Commons, we can edit the description there at will, and when we are happy about it we can copy it to YouTube. OK?",1459972614,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Great! Let's move onto the videos. It makes sense to start with the Tech Talks. We can work on a specific one, and then when we are happy about it, we can apply the same formula to the rest.
+
+I propose to start with this one:
+
+* https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm
+* https://www.youtube.com/watch?v=Qo4XIzCJZVs
+
+Since it is available in Commons, we can edit the description there at will, and when we are happy about it we can copy it to YouTube. OK?",1459972505,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Pleasure is all mine!
+>  in an ideal world these videos should be in https://commons.wikimedia.org, and that information would be very interesting to have in the their description pages. You have the choice of detailing this information both in YouTube (since it might attract more viewers) and Commons (the canonical location of these videos), or you can have it only in Commons, and link to there from the YouTube page. Up to you, whatever you think is more feasible.
+
+Yes, I can do that, it'll only take copy/paste to put description in both places.
+
+It's a yes from me on this template (speaker, summary, links). 
+Do you think we can move on to the videos?
+",1459963584,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Thank you @husn_shujaat !
+
+> * Speaker/Credits
+
+Yes, the main speakers are enough. All the better if we could link to their user page in mediawiki.org.
+
+> Summary
+
+Yes, paying attention to keywords that might bring more on-topic viewers to these videos.
+
+> IRC (channel)
+
+Hm. I would not get too obsessed about this. Usually the simultaneous chat is interesting only during the tech talk, but not after that.
+
+> Relevant links (All the webpages mentioned in the video, for example, link of T113066 should be in the description of Tech Talk: New readership data...) We could also mention the time of when these links/webpages were shown.
+
+If you are ready to do this work, then this will be excellent indeed. One thought though: in an ideal world these videos should be in https://commons.wikimedia.org, and that information would be very interesting to have in the their description pages. You have the choice of detailing this information both in YouTube (since it might attract more viewers) and Commons (the canonical location of these videos), or you can have it only in Commons, and link to there from the YouTube page. Up to you, whatever you think is more feasible.
+
+As soon as we agree on the description, the next step will be to agree on which videos should get priority. Not all of them are equally relevant, and you should be able to focus your time on the videos that matter most.",1459930927,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"Thanks for assigning this to me, I was looking for such tasks. 
+The plan looks good to me.
+
+I saw some techtalks videos and their descriptions give some good ideas for templates.
+ 
+  -   Speaker/Credits
+  -   Summary
+  - IRC (channel)
+  - Relevant links (All the webpages mentioned in the video, for example, link of [[ https://phabricator.wikimedia.org/T113066 | T113066]] should be in the description of [[ https://www.youtube.com/watch?v=Qo4XIzCJZVs | Tech Talk: New readership data...]]) We could also mention the time of when these links/webpages were shown.
+
+
+
+
+
+
+
+
+ 
+
+",1459897322,PHID-USER-k7tm37wvr4juk56sjsxf,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"@husn_shujaat based on T85593#2170408 I think this is a good task for you. I'm taking the liberty to steal it from @Rfarrand and assign it to you. I'm scheduling it for our currently quarterly milestone. 
+
+The goal is to have good descriptions in the most relevant videos at https://www.youtube.com/user/watchmediawiki
+
+As a first objective, I propose that you define a template for these descriptions. What information should it have, and any special format? It doesn't need to be anything complex. In fact, the simpler the better, as long as the basic information is provided. 
+
+Once we agree on the template, let's discuss on which videos would need to get it first (we have many videos, and not all of them are equally interesting nowadays).
+
+Please confirm this plan works for you, and feel free to suggest improvements.  :) Thank you!",1459888234,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#1761755, @Aklapper wrote:
+> @Rfarrand: [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner | Want to give this a shot ?]]
+
+@Rfarrand: Ping. (Though I'm not sure how S' last comment is related, or if that would be separate here.)",1447260630,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#1648391, @Qgil wrote:
+> I wonder whether Google Code-in could be of any help here.
+
+I think it could if @rfarrand defines a good ""generic"" (cloneable) [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Requirements_of_a_task | beginner task ]], like 
+""Wikimedia occassionally hosts [[ https://www.mediawiki.org/wiki/Tech_talks | Tech talks]] (FIXME: That page does not even explain what a Tech Talk is). Go to this link which is a list of Wikimedia TechTalk videos on Youtube. Pick one video, thoroughly understand which topic the Tech Talk video is about, identify a number of key terms you would associate with the Tech Talk topic, [[ https://www.mediawiki.org/wiki/Help:Searching | search ]] for documentation wiki pages on Wikimedia sites (meta.wikimedia.org, mediawiki.org, potentially commons.wikimedia.org and en.wikipedia.org, wikimediafoundation.org, FIXME: any others?) which are strongly related to the Tech Talk's topic, and provide a list of links to these wiki pages plus information which video you chose"". 
+(The action of updating the Youtube description requires special permissions so that's out of scope for GCI I'd say.)
+
+@Rfarrand: [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner | Want to give this a shot ?]]
+
+**Edit:** I hadn't seen Spage's last comment when I wrote my comment.",1446042167,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,">>! In T1119#1648391, @Qgil wrote:
+> I wonder whether Google Code-in could be of any help here.
+
+I think it could if @rfarrand defines a good ""generic"" (cloneable) [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Requirements_of_a_task | beginner task ]], like 
+""Wikimedia occassionally hosts [[ https://www.mediawiki.org/wiki/Tech_talks | Tech talks]] (FIXME: That page does not even explain what a Tech Talk is). Go to this link which is a list of Wikimedia TechTalk videos on Youtube. Pick one video, thoroughly understand which topic the Tech Talk video is about, identify a number of key terms you would associate with the Tech Talk topic, [[ https://www.mediawiki.org/wiki/Help:Searching | search ]] for documentation wiki pages on Wikimedia sites (meta.wikimedia.org, mediawiki.org, potentially commons.wikimedia.org and en.wikipedia.org, wikimediafoundation.org, FIXME: any others?) which are strongly related to the Tech Talk's topic, and provide a list of links to these wiki pages plus information which video you chose"". 
+(The action of updating the Youtube description requires special permissions so that's out of scope for GCI I'd say.)
+
+@Rfarrand: [[ https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner | Want to give this a shot ?]]",1446040603,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I created [[ https://www.mediawiki.org/wiki/Template:Tech_talk_video |  Template:Tech talk video]] `{{Tech talk video| link=` //youtube link// `| date=` //date//  `| title=` //talk title// `}}` that outputs
+* ""[[ https://www.youtube.com/watch?v=sWiDimlK4bE | Watch ]] 2015-10-19 [[https://www.mediawiki.org/wiki/Tech_talks | Tech talk ]] on ""Free and open source licensing at Wikimedia"".
+
+then just add this to the relevant pages that had tech talks. Maybe also use this template on the Tech talks page itself, though that has extra links.
+Done on MediaWiki-Vagrant, Performance team, Phabricator -- check https://www.mediawiki.org/wiki/Special:WhatLinksHere/Template:Tech_talk_video
+",1446012991,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I created [[ https://www.mediawiki.org/wiki/Template:Tech_talk_video |  Template:Tech talk video]] `{{Tech talk video| link=` //youtube link// `| date=` //date//  `| title=` //talk title// `}}` that outputs
+* ""[[ https://www.youtube.com/watch?v=sWiDimlK4bE | Watch ]] 2015-10-19 [[https://www.mediawiki.org/wiki/Tech_talks | Tech talk ]] on ""Free and open source licensing at Wikimedia"".
+
+then just add this to the relevant pages that had tech talks. Maybe also use this template on the Tech talks page itself.",1446010567,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"How about:
+
+Create a template `{{Tech talk |` //youtube link// `|` talk title `|` //date// `}}` that outputs
+* ""[[ https://www.youtube.com/watch?v=sWiDimlK4bE | Watch ]] 2015-10-19 [[https://www.mediawiki.org/wiki/Tech_talks | Tech talk ]] on ""Free and open source licensing at Wikimedia""
+
+then add this to the relevant pages that had tech talks. Maybe also use this template on the Tech talks page itself.",1445975648,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,I wonder whether Google Code-in could be of any help here.,1442480574,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I mean, linking to the videos from the project pages. For instance, a link from https://www.mediawiki.org/wiki/MediaWiki-Vagrant to the last Tech Talk about MediaWiki Vagrant.",1417463915,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,"I have the youtube videos linked from the tech talk pages - I just have not linked to documentation on each talk from YouTube. It might actually take a little while to dig around and find all of the documentation/project pages. 
+
+Past tech talks listed with YouTube links: https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event/TechTalks",1417458354,PHID-USER-vcyz3oe6mrt5w42lpqeh,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Add documentation links to TechTalk Youtube Videos ,This task is missing a description. The other way round ould be done as well: link to Tech Talk videos from the corresponding wiki pages.,1417445008,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ey56a2rp3p2o7wkxvsg6,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"https://www.mediawiki.org/wiki/2015_MediaWiki_User_Survey
+
+https://docs.google.com/forms/d/1j2ThONROvc0bGY5d3yx4tJln4Aa2Fs130j5OlHbjW14/viewform
+
+Presentation reporting preliminary results.
+
+https://commons.wikimedia.org/wiki/File:2015_MediaWiki_User_Report.pdf",1415210988,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_description,resolved
+Create a survey that MediaWiki users can use to provide us with information,"Exciting news and great job!
+",1438269463,PHID-USER-psxtq4r4r73pqtniajr2,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Exciting news and great job!
+
+----- Original Message -----
+From: ""Ckoerner"" <no-reply@phabricator.wikimedia.org>
+To: alexis@everybody.org
+Sent: Thursday, July 30, 2015 10:33:27 AM
+Subject: [Maniphest] [Commented On] T1114: Create a survey that MediaWiki users can use to provide us with information
+
+Ckoerner added a comment.
+
+Phew!
+It's been a few weeks since Wikimania and I'm just now getting my bearings.
+
+As of this morning we have 127 responses to our survey. That's a great accomplishment. Does anyone want to send out another reminder to the various mailing lists? One last hurrah?
+
+I'll close the survey tomorrow (Friday) at the end of the day (20:00 CST).
+
+Then we should put together a final report (maybe just an update of our presentation from Wikimania) with stats.
+
+I can work on making the data available publicly - anonymized of course.
+
+Then what?
+
+Might I suggest we take the feedback from the survey, add it to our wishlist, and start to prioritize?
+
+
+TASK DETAIL
+  https://phabricator.wikimedia.org/T1114
+
+EMAIL PREFERENCES
+  https://phabricator.wikimedia.org/settings/panel/emailpreferences/
+
+To: Ckoerner
+Cc: Krenair, RichardHeigl, RHeigl, Ckoerner, cicalese, Spage, Aklapper, Mglaser, Palexis, MarkAHershberger, Qgil, Legoktm, Malyacko, P.Copp",1438267912,PHID-USER-psxtq4r4r73pqtniajr2,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Phew!
+It's been a few weeks since Wikimania and I'm just now getting my bearings. 
+
+As of this morning we have 127 responses to our survey. That's a great accomplishment. Does anyone want to send out another reminder to the various mailing lists? One last hurrah? 
+
+I'll close the survey tomorrow (Friday) at the end of the day (20:00 CST).
+
+Then we should put together a final report (maybe just an update of our presentation from Wikimania) with stats.
+
+I can work on making the data available publicly - anonymized of course.
+
+Then what?
+
+Might I suggest we take the feedback from the survey, add it to our wishlist, and start to prioritize?",1438266804,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"The survey has been sent to mediawiki-l
+
+http://hexm.de/MWSurvey
+
+Alternate link: https://docs.google.com/forms/d/1j2ThONROvc0bGY5d3yx4tJln4Aa2Fs130j5OlHbjW14/viewform
+
+Please share and provide suggestions on where else to promote. We will leave it open for a little more than 2 weeks, closing on Friday, July 31st.
+
+Woo!",1436977074,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,Great! Will you be posting information for remote participation in the Stakeholders' meetup?,1436973359,PHID-USER-mpmiy5j6qf3u6jazgvcy,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"We (Mark, Marcus, and myself) are at the hackathon in Mexico City. We've created a page to host a brief introduction to the survey (and eventually the results) on Mediawiki.org.
+
+https://www.mediawiki.org/wiki/2015_MediaWiki_User_Survey
+
+",1436972925,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Ok, we're at the Hackathon at Wikimania and talked about the question about how frequently you update. 
+
+We've reworded it to ask, ""Which MediaWiki update cycle is closest to what you use?""
+",1436972088,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Sorry, I didn't mean for this to be a blocker. Despite the fact that the major/point release schedule is not currently accurate in terms of time, it is a driver for updating. I update when a new security-related point release or major release is available, regardless of whether that is every month or every six months. So, the time-based answers were not a good fit for my situation. But, some folks might use a more time based approach to updating. I think adding answers based upon release availability to the time based answers to the question would be a good solution, helping us to determine what the drivers are for updating. I don't recall if there was an ""other"" answer, but that could also help. But, I whatever you choose, this should not stop the survey from moving forward.",1436971582,PHID-USER-mpmiy5j6qf3u6jazgvcy,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"I'm stuck on the 'How frequently do you update"" question. Since the major/point release schedule isn't the most accurate, will responses tell us anything useful? Can we combine the two in a graceful way? ",1436802165,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Yes, that was why I was mentioning it. It was difficult to answer the question with a strict timeframe. We update whenever there is a release available to update to, but that does not appear to happen on schedule at this point.",1436560974,PHID-USER-mpmiy5j6qf3u6jazgvcy,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Ckoerner writes:
+
+> Which is more important to know. That folks update to major/point
+> releases or that they're updating with any sort of frequency? Do you
+> think we should combine the two answer types?
+
+No comment on either of those points, but I would point out that there
+have been questions on mediawiki-l about the lack of point releases.",1436559274,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@RHeigl Thanks for the OK and the correction.
+
+@Cicalese I can move the links to the thank you page. Good idea.
+
+As for the upgrade question, you have an interesting point. The release schedule for MediaWiki is major releases every 6 months and point releases monthly. 
+
+https://www.mediawiki.org/wiki/Version_lifecycle#Release_policy
+
+Which is more important to know? That folks update to major/point releases or that they're updating with any sort of frequency? Do you think we should combine the two answer types?",1436543850,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@RHeigl Thanks for the OK and the correction.
+
+@Cicalese I can move the links to the thank you page. Good idea.
+
+As for the upgrade question, you have an interesting point. The release schedule for MediaWiki is major releases every 6 months and point releases monthly. 
+
+https://www.mediawiki.org/wiki/Version_lifecycle#Release_policy
+
+Which is more important to know. That folks update to major/point releases or that they're updating with any sort of frequency? Do you think we should combine the two answer types?",1436543832,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@RHeigl Thanks for the OK and the correction.
+
+@Cicalese I can move the links to the thank you page. God idea.
+
+As for the upgrade question, you have an interesting point. The release schedule for MediaWiki is major releases every 6 months and point releases monthly. 
+
+https://www.mediawiki.org/wiki/Version_lifecycle#Release_policy
+
+Which is more important to know. That folks update to major/point releases or that they're updating with any sort of frequency? Do you think we should combine the two answer types?",1436543820,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"It looks great! Thank you so much for your work on this, @ckoerner!
+
+I have two very minor suggestions, but I think it is good to go regardless, even without any changes. For the ""how often do you upgrade"" question, I wanted to answer in a less time constrained manner: ""every time there is a point release"", ""every time there is a security-related point release"" or ""every time there is a major release"". And, would it be possible to move the links from the page with the Submit button (where it is tempting to click them and lose the survey results) to the Thank You page?",1436523899,PHID-USER-mpmiy5j6qf3u6jazgvcy,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Checked it. Great!
+You have my OK :-))
+
+Thank you very much!
+
+Just found a typo: Are you(r) sites public or private? 
+
+",1436517688,PHID-USER-lmzb6z33itjcncao6utg,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@krenair Fixed! Thank you.
+
+@mglaser Hmm. Good point. I've changed it to a multi-select.",1436477807,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"On the third page, I am asked how many MediaWiki sites I run. I selected more than one. In the follwing question about my MW version, I have to pick one. However, I run a range of versions. This might probably be better if I could select multiple options here.  
+
+Otherwise it's ok for me",1436476334,PHID-USER-qfsdosrnxswxjuku752n,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"On the third page, I am asked how many MediaWiki sites I run. I selected more than one. In the follwing question about my MW version, I have to pick one. However, I run a range of versions. This might probably be better if I could select multiple options here.  ",1436475867,PHID-USER-qfsdosrnxswxjuku752n,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"And "" I contribute patches and pug fixes""",1436475560,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Typo on ""What would yo like to see most improved in the community around MediaWiki?""",1436477846,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Tyop on ""What would yo like to see most improved in the community around MediaWiki?""",1436475537,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,Might be worth separating people who are actually running this week's WMF branches from those who are running really old WMF branches.,1436475081,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"The survey has been created!
+
+Please review. If you **are OK** with sending, please let me know. If you are **not OK** with sending, please let me know.
+
+I will not publish or send this until I have **at least 4 responses **in the affirmative. I don't want to send it out with the //assumption //everyone is OK with it! :)
+
+http://goo.gl/forms/XCYIdNT2gI",1436474996,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@cicalese
+
+> 3.What would you like to see improved in MediaWiki?
+> 4.What is the most important thing the Mediawiki community should be focused on?
+
+My thought was to have one question about the software itself and the other be about the community. Fishing for answers like, ""I think VisualEditor should work on the Apple Newton."" as opposed to, ""I think there should be more inclusion of people from the southern hemisphere at events.""
+
+Does that make sense? Do you think I should reword those? How does this sound?
+
+ - What would you like to see most improved in MediaWiki the software?
+ - What would yo like to see most improved in the community around MediaWiki?
+
+The other suggestions are spot on, thank you.
+
+@mglaser
+
+> When did you last update your MediaWiki? To which version (LTS version, newest release, newest patch version, or other?)
+
+
+In the longer survey I had a separate question regarding frequency. How about we keep both questions to keep it quantitative.
+
+> How many extensions do you use?
+
+I'm curious about extension usage. Is everyone using just WMF-led extensions? What's the usage of third-party extensions like?
+
+How about, ""Of the extensions you use, which are your Top Five?"" And then have 5 blanks where they can enter the name of the extension?
+
+
+Here's an updated draft based upon the feedback.
+
+
+# How long have you been using MediaWiki?
+# How many MediaWiki sites do you manage?
+# Are your sites public or private?
+# How many end users are there of your MediaWiki sites?
+# What MediaWiki version are you currently using?
+# How frequently do you update your MediaWiki installations and extensions?
+# Of the extensions you use, which are your Top Five?
+
+# Why do you use MediaWiki?
+# What would you like to see most improved in MediaWiki the software?
+# What would yo like to see most improved in the community around MediaWiki?
+# Do you make contributions to the MediaWiki community?
+# What barriers, if any, do you think exist to participation in the MediaWiki community? What can we do to help?
+
+",1436392964,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Thanks, Chris, for this list, this is good stuff. 
+
+A few comments that come to my mind:
+
+> 5. What MediaWiki version are you currently using?
+I think it is more interesting how frequently they update. So the question could be rephrased to 
+> 5. When did you last update your MediaWiki? To which version (LTS version, newest release, newest patch version, or other?)
+
+And the questions about extensions:
+> 6. How many extensions do you use?
+I am not so sure why we would be interested in that. Maybe rephrase it: 
+> 6. Did you modify your MediaWiki? How (add existing extensions, change skin, write new extensions)?
+
+In addition to @cicalese's comment,
+> 5. What barriers, if any, do you think exist to participation in the MediaWiki community?
+maybe we could ask how to help:
+> 5. What barriers, if any, do you think exist to participation in the MediaWiki community? What can we do to help?",1436223135,PHID-USER-qfsdosrnxswxjuku752n,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"This is a good short list. Perhaps the following two questions are similar enough to be combined into one:
+
+3.What would you like to see improved in MediaWiki?
+4.What is the most important thing the Mediawiki community should be focused on?
+
+And, the following two questions are thematically related and could benefit from being beside each other:
+
+2.Do you make contributions to the MediaWiki community?
+5.We're striving to increase the participation of MediaWiki users outside of Wikimedia Foundation-led initiatives. What do you think is the biggest barrier to participation?
+
+Perhaps 5 could be simplified to:
+
+5. What barriers, if any, do you think exist to participation in the MediaWiki community?
+
+Thanks for pulling this together!",1436213073,PHID-USER-mpmiy5j6qf3u6jazgvcy,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Ok, how about this as a proposal. I've removed a few questions to shorten things down to 12 questions. These are what I feel (which is neither right or wrong) on what are the important questions to ask this go round. This would assume that we keep the 4 demographic questions.
+
+ # How long have you been using MediaWiki?
+ # How many MediaWiki sites do you manage?
+ # Are your sites public or private?
+ # How many end users are there of your MediaWiki sites?
+ # What MediaWiki version are you currently using?
+ # How many extensions do you use?
+ # Of those extensions which are your Top Five?
+
+
+ # Why do you use MediaWiki?
+ # Do you make contributions to the MediaWiki community?
+ # What would you like to see improved in MediaWiki?
+ # What is the most important thing the Mediawiki community should be focused on? 
+ # We're striving to increase the participation of MediaWiki users outside of Wikimedia Foundation-led initiatives. What do you think is the biggest barrier to participation?",1436208493,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Ok, how about this as a proposal. I've removed a few questions to shorten things. This would assume that we keep the 4 demographic questions.
+
+ # How long have you been using MediaWiki?
+ # How many MediaWiki sites do you manage?
+ # Are your sites public or private?
+ # How many end users are there of your MediaWiki sites?
+ # What MediaWiki version are you currently using?
+ # How many extensions do you use?
+ # Of those extensions which are your Top Five?
+
+
+ # Why do you use MediaWiki?
+ # Do you make contributions to the MediaWiki community?
+ # What would you like to see improved in MediaWiki?
+ # What is the most important thing the Mediawiki community should be focused on? 
+ # We're striving to increase the participation of MediaWiki users outside of Wikimedia Foundation-led initiatives. What do you think is the biggest barrier to participation?",1436208455,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Regarding community surveys, this one from the Drupal community was insightful. 
+
+https://www.drupal.org/node/1399056
+
+Of note, their survey was at around 13 questions, in addition to 4 'demographic' questions.",1436202436,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,Dang. You are absolutely correct. We're at 20 + questions. What if we paired that down to say 10? I'll ask you and anyone else reading - what are the big 10 questions we want to ask? Think more about the answers. What top 10 things about MediaWiki users do we want to know? How do we ask questions that provide those answers?,1435689410,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Left my comments on the talk page.  One more, though: I feel like we don't want to bog dow the respondents just yet with too many questions.  I think @rheigl has worked on these beofe and it''d be good to know how we can make this as effective as possible.",1435678045,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Given that Wikimania is a scant two weeks away I spoke to @cicalese and offed to help finish the survey work. I have a draft of the questions here and need your feedback!
+
+http://mwstake.org/mwstake/wiki/MediaWiki_Usage_Questions
+
+Once I have a few people (I'm looking at you!) review these questions and the language around them I will create a working survey.
+
+As I mentioned earlier (T1114#1341595) I have some suggestions on the distribution of the survey. 
+
+  - What other opportunities exist that we can leverage to distribute? 
+  - What do we need to do to get approval/permission to use the channels mentioned?
+  - Does something like this need to be reviewed by the WMF in some capacity?
+
+If we want to have a window for folks to respond we must act quickly. As of today we have two weeks until Wikimania begins. I would think getting this in front of Mediawiki users ASAP would provide us with more insightful and complete information than if we wait any longer.
+
+Please review (and share) this draft. I propose a goal of sending this out by **the end of this week** - July 4th.
+",1435608698,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"We are using Google Forms for our hackathon surveys, so nothing against this option. Still, you might want to check alternatives at {T94807}.",1435596615,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Given that our budget is 0, I propose we use a Google Doc to capture the information. Any alternative suggestions?",1435596409,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,T951 is related as the survey will further our understanding of who (and how) is using MediaWiki.,1434057589,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Once we have a survey put together how do we get it in front of MediaWiki using people? A few ideas, but I'd love some more.
+* Email to mediawiki, mediawiki-enterprise, semantic-mediawiki (dev and user), mailing lists
+* Sharing on social media
+* See if the folks at WikiApiary will help. Maybe a site banner or something for a week or two
+* See if the folks behind MediaWiki.org can help. Maybe a banner as well",1433519592,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@cicalese , I put a page up on mwstake to start gathering these questions. I wanted to dump what was in my brain somewhere. Since this is your thing, feel free to delete it all. :)
+
+http://mwstake.org/mwstake/wiki/MediaWiki_Usage_Questions",1432751989,PHID-USER-xd3dshn3ykvvbsxmqbg6,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@Spage, you are right. Tag removed.",1426579800,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"@Qgil, how is this part of the Documentation project? The survey is of users of the MediaWiki software. Are you thinking the survey could pose questions like ""Are you an [] admin [] MediaWiki hacker?"" ""How could MediaWiki documentation for admins / users / developers be improved?""",1426567793,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Broad outline of the survey:
+
+* How long have you been using MW?
+* What do you use it for?
+** Documentation?
+** Coordination?
+* How could MediaWiki distribution be improved?",1423849016,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"> Need to develop the questions and find a place to host this survey.
+
+@MarkAHershberger: Where was the scope of the survey discussed and where can that discussion be found (link)?
+Currently it feels like no-one finding this task here could help because the scope feels a bit vague. Please clarify...",1423754105,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,Thanks for the pointer!  That is helpful.,1418935381,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Create a survey that MediaWiki users can use to provide us with information,"Phabricator does have a polling and questionnaire application..
+
+I don't know if there is a standard place to do this otherwise, but it's a pretty straight forward app that is in phab-01 to look at https://phab-01.wmflabs.org/vote/",1415636830,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-54hi6wjvnjjmrztmmiki,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"New report as of 2017/06/21. eventstreams is tracked at {T160644} already
+
+```
+root@graphite1001:/var/lib/carbon/whisper# du -hcs /var/lib/carbon/whisper/* | grep G | sort -rn
+433G	/var/lib/carbon/whisper/eventstreams
+199G	/var/lib/carbon/whisper/servers
+199G	/var/lib/carbon/whisper/instances
+137G	/var/lib/carbon/whisper/ores
+71G	/var/lib/carbon/whisper/MediaWiki
+50G	/var/lib/carbon/whisper/zuul
+46G	/var/lib/carbon/whisper/varnishkafka
+35G	/var/lib/carbon/whisper/frontend
+```",1415116064,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_description,resolved
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Resolving this old task, individual big users are tracked separately ",1501145271,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 358910 merged by Filippo Giunchedi:
+[operations/puppet@production] role: cleanup CI data in graphite
+
+[[https://gerrit.wikimedia.org/r/358910]]
+",1498668831,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"@ArielGlenn thanks! yeah the eventstreams/rdkafka task is T160644, `instances` is also supposed to move to labmon in T143405",1498568715,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Seen today: icinga-wm: PROBLEM - carbon-cache too many creates on graphite1001 is CRITICAL: CRITICAL: 1.67% of data above the critical threshold [1000.0]
+
+Mostly rdkafka plus some 'instances' metrics, I spot checked a couple log files: /var/log/carbon/carbon-cache\@{a,b,c}/creates.log",1498477488,PHID-USER-jtxavgb3caz53o45csni,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVzee3oNZYjxCLpCzLVP} [2017-06-25T09:00:53Z] <elukey> Executing 'sudo -u _graphite find /var/lib/carbon/whisper/eventstreams/rdkafka -type f -mtime +15 -delete' on graphite1001 to free some space (/var/lib/carbon filling up) - T1075",1498381253,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 358910 had a related patch set uploaded (by Filippo Giunchedi; owner: Filippo Giunchedi):
+[operations/puppet@production] role: cleanup zuul data in graphite
+
+[[https://gerrit.wikimedia.org/r/358910]]
+",1497429261,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 358903 merged by Filippo Giunchedi:
+[operations/puppet@production] graphite: introduce graphite::whisper_cleanup
+
+[[https://gerrit.wikimedia.org/r/358903]]
+",1497428873,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 358903 had a related patch set uploaded (by Filippo Giunchedi; owner: Filippo Giunchedi):
+[operations/puppet@production] graphite: introduce graphite::whisper_cleanup
+
+[[https://gerrit.wikimedia.org/r/358903]]
+",1497427583,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 197509 merged by Filippo Giunchedi:
+diamond: stop collecting disk IO stats for partitions
+
+[[https://gerrit.wikimedia.org/r/197509]]",1426697366,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"Change 197509 had a related patch set uploaded (by Filippo Giunchedi):
+diamond: stop collecting disk partitions stats
+
+[[https://gerrit.wikimedia.org/r/197509]]
+",1426679729,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"still occurring, big jump in disk used on graphite1001 some weeks ago:
+
+{F99837}
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs * | sort -h
+0       irc
+2.3M    test
+5.6M    deploy
+12M     gerrit
+18M     VisualEditor
+54M     jvm_memory
+108M    scap
+186M    ocg
+195M    eventlogging
+249M    parsoid
+318M    carbon
+978M    HHVM
+1.3G    ve
+2.3G    kafka
+2.4G    restbase
+3.3G    statsd
+4.1G    cassandra
+4.7G    swift
+6.2G    frontend
+13G     mw
+42G     zuul
+46G     varnishkafka
+58G     jobrunner
+78G     MediaWiki
+78G     reqstats
+341G    servers
+680G    total
+```
+
+so `servers` is the biggest offender, which could match up with the growth of turning up MW in codfw (on average ~380MB/server, i.e. ~380 metrics/server)
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs servers/* | sort -h | tail -20
+1.3G    servers/ms-be1015
+1.3G    servers/ms-be2001
+1.3G    servers/ms-be2002
+1.3G    servers/ms-be2003
+1.3G    servers/ms-be2004
+1.3G    servers/ms-be2005
+1.3G    servers/ms-be2006
+1.3G    servers/ms-be2007
+1.3G    servers/ms-be2008
+1.3G    servers/ms-be2009
+1.3G    servers/ms-be2010
+1.3G    servers/ms-be2011
+1.3G    servers/ms-be2012
+1.3G    servers/ms-be2013
+1.3G    servers/ms-be2015
+1.4G    servers/ms-be2014
+2.1G    servers/labstore2001
+2.6G    servers/labstore1002
+4.0G    servers/labstore1001
+341G    total
+```
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs servers/labstore1001/* | sort -h
+4.5M    servers/labstore1001/vmstat
+5.6M    servers/labstore1001/loadavg
+12M     servers/labstore1001/cpu
+16M     servers/labstore1001/memory
+61M     servers/labstore1001/network
+81M     servers/labstore1001/diskspace
+3.8G    servers/labstore1001/iostat
+4.0G    total
+```
+
+the `iostat` hierarchy seems the biggest offender, 48% of total `servers`
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs servers/*/iostat | sort -h | tail -10
+996M    servers/ms-be2012/iostat
+1.1G    servers/ms-be2003/iostat
+1.1G    servers/ms-be2011/iostat
+1.1G    servers/ms-be2013/iostat
+1.1G    servers/ms-be2014/iostat
+1.1G    servers/ms-be2015/iostat
+2.0G    servers/labstore2001/iostat
+2.6G    servers/labstore1002/iostat
+3.8G    servers/labstore1001/iostat
+229G    total
+```
+
+and we count both partitions and underlying devices, however just the partitions accounts for ~half of the total `iostat` space:
+
+```
+graphite1001:/var/lib/carbon/whisper$ du -hcs servers/*/iostat/sd*[0-9] | tail -5
+31M     servers/zirconium/iostat/sda1
+31M     servers/zirconium/iostat/sda2
+31M     servers/zirconium/iostat/sdb1
+31M     servers/zirconium/iostat/sdb2
+127G    total
+```
+
+so I think it makes sense to consider just disks i.e. sd* but not the partitions within those (sw raid and lvm would still be graphed of course)",1426677880,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"downgrading to normal since we've mitigated the biggest growth.
+still pending zuul patching which now has over 93k disting metrics and totalling 100+ GB",1421082509,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,Jenkins no more emits to statsd under `jenkins.ci` which can now be deleted entirely.,1416489149,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,">>! In T1075#22258, @fgiunchedi wrote:
+> I think there might be some value in having those, but not as many. Note that also zuul metrics are basically duplicating those in jenkins, not sure exactly what generates those, zuul itself?
+> 
+> ```
+> /var/lib/carbon/whisper/jenkins/ci/mwext-CentralNotice-testextension/FAILURE/count.wsp
+> /var/lib/carbon/whisper/zuul/pipeline/test/job/mwext-CentralNotice-testextension/FAILURE/count.wsp
+> ```
+
+I finally looked at the usage of Graphite jenkins.ci metrics. Turns out they are not used from anywhere. The bug report to add them was:  Jenkins: report metrics to statsdhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55412 .
+
+The reason was to generate graphs of the executors queues, but it turns out the Java plugin does not collect them ( https://bugzilla.wikimedia.org/show_bug.cgi?id=55988 ).  So instead I added a Ganglia monitor which runs a python script to collect data out of the Jenkins REST API.
+
+
+I have uninstalled the plugin ( T1278 ), still have to restart Jenkins but it is not an ideal time to do (there is some long running jobs going on which I don't want to abort).  Whenever Jenkins is restarted, we can delete the whole 'jenkins.ci.' metrics hierarchy and reclaim the disk space.
+
+
+For Zuul, the metrics are used to generate dashboards on the Zuul status page at https://integration.wikimedia.org/zuul/ , so we need to keep them. That being said, we probably do not need metrics for each jobs / results, unfortunately Zuul does not have support to finely select which metrics to send.  Can be patched and proposed upstream.",1416413857,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,">>! In T1075#22258, @fgiunchedi wrote:
+>>>! In T1075#22250, @hashar wrote:
+>> We can most probably remove the Statsd plugin from Jenkins. I have created the sub task {T1278}
+> 
+> I think there might be some value in having those, but not as many. Note that also zuul metrics are basically duplicating those in jenkins, not sure exactly what generates those, zuul itself?
+
+@hashar any ideas on this?",1416409425,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,">>! In T1075#22250, @hashar wrote:
+> We can most probably remove the Statsd plugin from Jenkins. I have created the sub task {T1278}
+
+I think there might be some value in having those, but not as many. Note that also zuul metrics are basically duplicating those in jenkins, not sure exactly what generates those, zuul itself?
+
+```
+/var/lib/carbon/whisper/jenkins/ci/mwext-CentralNotice-testextension/FAILURE/count.wsp
+/var/lib/carbon/whisper/zuul/pipeline/test/job/mwext-CentralNotice-testextension/FAILURE/count.wsp
+```",1415968699,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,We can most probably remove the Statsd plugin from Jenkins. I have created the sub task {T1278},1415968381,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"also note that the zuul/jenkins stats are pushed twice, e.g.
+
+```
+/var/lib/carbon/whisper/jenkins/ci/mwext-CentralNotice-testextension/FAILURE/count.wsp
+/var/lib/carbon/whisper/zuul/pipeline/test/job/mwext-CentralNotice-testextension/FAILURE/count.wsp
+```
+
+and account for ~half of all metrics created daily.
+
+I took a look at the jenkins statsd plugin and it seems fairly easy to change it not to differentiate timings based on the build status but only on the job name:
+
+```
+diff --git a/src/main/java/org/jenkinsci/plugins/statsd/StatsdListener.java b/src/main/java/org/jenkinsci/plugins/statsd/StatsdListener.java
+index 2409d1b..ce00eb0 100644
+--- a/src/main/java/org/jenkinsci/plugins/statsd/StatsdListener.java
++++ b/src/main/java/org/jenkinsci/plugins/statsd/StatsdListener.java
+@@ -46,7 +46,8 @@ public class StatsdListener extends RunListener<Run> {
+         jobName = jobName.replaceAll(""\\/"", ""-"");
+         jobName = jobName.replaceAll(""[^a-zA-Z_\\-0-9]"", """");
+ 
+-        String metricName = prefix + '.' + jobName + '.' + result;
++        String metricResultName = prefix + '.' + jobName + '.' + result;
++        String metricTimingName = prefix + '.' + jobName;
+ 
+         LOGGER.log(Level.INFO, ""StatsdListener: config: "" + config);
+         LOGGER.log(Level.INFO, ""StatsdListener: job: "" + jobName + "", result: "" + result +
+@@ -54,8 +55,8 @@ public class StatsdListener extends RunListener<Run> {
+ 
+         try {
+             StatsdClient statsd = new StatsdClient(host, port);
+-            statsd.increment(metricName);
+-            statsd.timing(metricName, (int)duration);
++            statsd.increment(metricResultName);
++            statsd.timing(metricTimingName, (int)duration);
+         } catch (UnknownHostException e) {
+             LOGGER.log(Level.WARNING, ""StatsdListener Unknown Host: "", e);
+         } catch (IOException e) {
+```",1415967660,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,">>! In T1075#18973, @fgiunchedi wrote:
+> another potential avenue of investigation from hashar
+> 
+> 
+> ```
+>>    I have some examples related to continuous integration:
+> 
+>>   A) jenkins.ci , emitted by Jenkins, metrics namespaced as follow:
+> 
+>>     - job_name (roughly 4000 jobs)
+>>     - build status (4: success, failure, aborted, unstable)
+> 
+>>    Each having percentiles, count, max, mean, rate etc (12 entries)
+> 
+> 
+> good catch! looks like these shouldn't get additional metrics calculated by statsd, that would cut it by 12x. definitely worth investigating what's going on
+> 
+> ```
+
+so the solution here would be to separate build status from build time, status is fine being a different metric but build-time shouldn't be tied to the status as a metric, that greatly reduces the number of metrics",1415270623,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"to find out what files have been created recently we can exploit the fact that carbon-cache logs whenever it creates a new file. reqstats is there but seems a minority:
+
+```
+root@tungsten:/var/log/upstart# zgrep  -F 'creating ' /var/log/upstart/carbon_cache-*.gz | cut -d' ' -f8 | sort | grep -i reqstats
+/var/lib/carbon/whisper/reqstats/2_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/5yojb4_en_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/Mai_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/Mai_wikipedia_org/tp50.wsp
+/var/lib/carbon/whisper/reqstats/Mai_wikipedia_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/action_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/bn_m__wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/crsio_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/crsio_org/tp50.wsp
+/var/lib/carbon/whisper/reqstats/crsio_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/during_World_War_IIwikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/edits/2013_wikipedia_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/edits/EN_wikipedia_org/edit.wsp
+/var/lib/carbon/whisper/reqstats/edits/action_wikipedia_org/edit.wsp
+/var/lib/carbon/whisper/reqstats/edits/fa_m_wikivoyage_org/submits.wsp
+/var/lib/carbon/whisper/reqstats/edits/mai_wikipedia_org/edit.wsp
+/var/lib/carbon/whisper/reqstats/edits/title_wikipedia_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/el_wikiipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/en_wikiquosity_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/hi__wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/mai_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/norb_rulez_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/pap_m_wikibooks_org/tp50.wsp
+/var/lib/carbon/whisper/reqstats/philipminhparish_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/sfair_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/wpDestFile_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_NL_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_echolalie_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_ietf_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_ja_wikiipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_sugarlabs_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_urbansim_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_veteranosracingferrol_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/www_wikimania_org/tp50.wsp
+/var/lib/carbon/whisper/reqstats/www_wikimania_org/tp99.wsp
+/var/lib/carbon/whisper/reqstats/www_za_wikiversity_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/zh_wikipedia_orgzh_wikipedia_org/pageviews.wsp
+/var/lib/carbon/whisper/reqstats/zhqvcrgkqodjbfyeuxdqaiqzx_org/pageviews.wsp
+root@tungsten:/var/log/upstart# 
+```",1415207611,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+Audit groups of metrics in Graphite that allocate a lot of disk space,"another potential avenue of investigation from hashar
+
+
+```
+>    I have some examples related to continuous integration:
+
+>   A) jenkins.ci , emitted by Jenkins, metrics namespaced as follow:
+
+>     - job_name (roughly 4000 jobs)
+>     - build status (4: success, failure, aborted, unstable)
+
+>    Each having percentiles, count, max, mean, rate etc (12 entries)
+
+
+good catch! looks like these shouldn't get additional metrics calculated by statsd, that would cut it by 12x. definitely worth investigating what's going on
+
+```",1415188804,PHID-USER-wr3pospifdaxghmtobvr,False,PHID-TASK-wfsi7vtkgqxje73iid73,task_subcomment,NA
+unable to obtain stable firefox connection in 60 seconds,"This error message happens [[ https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox/LANGUAGE_SCREENSHOT_CODE=nl,label=contintLabsSlave%20&&%20UbuntuTrusty/29/consoleFull | intermittently ]]:
+
+  unable to obtain stable firefox connection in 60 seconds (127.0.0.1:7055) (Selenium::WebDriver::Error::WebDriverError)
+
+Looks like it is a known problem:
+
+https://code.google.com/p/selenium/issues/detail?id=4967
+https://github.com/leonid-shevtsov/headless/issues/33
+",1415110910,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ufnfo3vpfoqevod6gugb,task_description,declined
+unable to obtain stable firefox connection in 60 seconds,"That is a duplicate of {T1321}
+
+See there for full explanations and details on how to fix it up.",1416479903,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ufnfo3vpfoqevod6gugb,task_subcomment,NA
+unable to obtain stable firefox connection in 60 seconds,Related commit: https://gerrit.wikimedia.org/r/#/c/170023/,1415114465,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-ufnfo3vpfoqevod6gugb,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Thanks to @Dzahn we have been collecting the number of [[ https://www.mediawiki.org/wiki/Talk:Community_metrics#Bugzilla_stats | active Bugzilla users every month ]] for almost two years now. It would be useful to collect this data --or any approximation-- on a monthly basis:
+
+[x] Number of accounts created 
+[ ] Number of users logging 
+[x] Number of users performing any action in Maniphest 
+
+Extended Play
+
+It would be interesting to know whether it is possible to extract these values as well (total and past month):
+
+[x] Number of task creators
+[ ] Number of comment posters
+[x] Number of task //closers//
+[ ] Number of workboard movers
+
+[x] Number of tasks created
+[x] Number of tasks closed
+[x] Median age in days of open tasks by priority
+
+Very Extended Play
+
+Then we could open two parallel ways:
+* Other metrics per app: who is subscribing to Projects, who uses Differential...
+* Filter these metrics by project, with a possibility to aggregate projects (i.e. let's count only the engineering projects)
+
+The extended plays are inspirational only. This task can be closed as soon as we can publish monthly metrics for total amount of users and active in the past month.
+
+**First report, sent on January 1st (for the record)**
+
+> Hi Community Metrics team,
+>
+> this is your automatic monthly Phabricator statistics mail.
+> 
+> Number of accounts created in (2014-12): 395
+> Number of active users (any activity) in (2014-12): 619
+> Number of task authors in (2014-12): 384
+> Number of users who have closed tasks in (2014-12): 213
+> Number of tasks created in (2014-12): 3424
+> Number of tasks closed in (2014-12): 2529
+> Number of tasks in the shell project closed as resolved,fixed in (2014-12): 12
+>
+> Number of open and stalled tasks in total: 18125
+>
+> Median age in days of open tasks by priority:
+> Unbreak now: 115
+> Needs Triage: 147
+> High: 199
+> Normal: 437
+> Low: 686
+> Needs Volunteer: 536
+>
+> TODO: Numbers which refer to closed tasks might not be correct, as described in T1003.
+",1414696282,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_description,resolved
+Monthly report of total / active Phabricator users,"@MelodyKramer: The file to edit is https://phabricator.wikimedia.org/source/operations-puppet/browse/production/modules/phabricator/templates/community_metrics.sh.erb
+If you feel like writing and proposing a patch in Gerrit: See https://www.mediawiki.org/wiki/Gerrit/Getting_started . The repo in this case is `operations/puppet.git`, the file is `modules/phabricator/templates/community_metrics.sh.erb`, and you'd have to replace the command `git checkout master` by `git checkout production` in this very case. And if you don't feel like I can also give it a shot. :)",1509552480,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Ah, thanks @Aklapper - is it possible to get that link (or the information contained within) added to the monthly email update I receive? I'm not sure who mans the wheels on that. ",1509550992,PHID-USER-w5dqcsw7esxdqy3say2e,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"@MelodyKramer: I nowadays dump //two// of these numbers at [[ https://meta.wikimedia.org/wiki/Technical_Collaboration/Metrics#Project_management_.28Phabricator.29 | meta:Technical_Collaboration/Metrics#Project_management_.28Phabricator.29 ]].
+(Beforehand I dumped two of these numbers at [[ https://www.mediawiki.org/wiki/Community_metrics | mw:Community_metrics ]] but the [[ https://www.mediawiki.org/w/index.php?title=Community_metrics&action=history | page scope was too blurry ]] so I split wikimedia.biterg.io documentation, displaying of some graphs with data copied out of other systems, and a link hub to random metrics pages in Wikimedia into three separate pages.)
+
+(And the usual disclaimer when it comes to interpreting numbers: ""New Phab accounts"" does not mean ""active Phab accounts"" for more than half of these accounts.)",1509550274,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Hello! I just received the monthly stats email ([Wikitech-l] Phabricator monthly statistics - 2017-10) and I'm wondering if there's a way to show a 3 or 6 month trend. I do not know from the email if new Phab users have slowed down to a trickle or doubled...and the same holds true for active users and other metrics. This is a very very low-priority ask, but I would love to see additional stats added that compare the current figures to the past 3 or 6 months, so we can learn more about the ongoing nature of the userbase. Thank you! Mel ",1509547181,PHID-USER-w5dqcsw7esxdqy3say2e,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Trying to get some comparable numbers pre and post-migration. It seems that the sum of MediaWiki (including VisualEditor and MobileFrontend) and Wikimedia products is what mapped best from Bugzilla to Phabricator. Some numbers (I hate IRC invisible characters with passion, btw):
+
+```
+# Number of active users in MediaWiki and Wikimedia products
+# January 2015
+$ curl -s 'http://bots.wmflabs.org/~wm-bot/logs/%23mediawiki-feed/%23mediawiki-feed.tar.gz' | tar xzf - -O --wildcards '201501*' | grep wikibugs | grep -E '(MediaWiki|MobileFrontend|VisualEditor|Wikimedia)' | grep -Eo ' [(][^)]{0,3}10[^)]+' | sort | uniq -c | wc -l
+473
+# October 2014
+$ ... --wildcards '201410*' ...
+462
+```",1422873038,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"I would like to propose some changes in the data ranges used in this report, but before let's agree on {T86630}. You opinions are welcome there.",1421141894,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Thank you very much! 
+
+>>! In T1003#963841, @Dzahn wrote:
+> Number of accounts created in (2014-11): 299
+> Number of active users (any activity) in (2014-11): 443
+
+These are the two numbers I really care about for November. Look credible...
+
+> Number of task authors in (2014-11): 284
+> Number of users who have closed tasks in (2014-11): 115
+
+These are also interesting. Do you think that they can be trusted?
+
+It is no problem if the stats on tasks are messed up in the month of the Bugzilla migration. Even for December (with the RT migration) I'm not expecting to read much there in task related stats.
+
+Having a continuity of user related stats is great. Thank you again.
+
+
+> Number of tasks created in (2014-11): 1916
+> Number of tasks closed in (2014-11): 814
+> Number of tasks in the shell project closed as resolved,fixed in (2014-11): 4
+> 
+> Number of open and stalled tasks in total: 18296
+> 
+> 
+> Is that sufficient? It was easier to make than the lower part.
+
+",1420752643,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,andre__ added the address as allowed sender to wikitech-l. That means the list should now receive stats starting on Feb 1st.,1420752009,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"As requested in comments above i have added wikitech-l to the recipients of this mail. More specifically wikitech-l is now one of the recipients that receive communitrymetrics@ mail which is the sender of this as configured in the puppet phabricator role.
+
+Now we need one of the admins of wikitech-l to allow that sender as a ""non-member"".  Admins of wikitech-l are demon, aklapper and platonides.",1420751162,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#961937, @KartikMistry wrote:
+> Is it possible to get teamwise statistics? (eg: Language Engineering) (Just wishlist) :)
+
+Separate tickets with specific criteria can be created. Such tickets will be wishlist/needs volunteer though; I don't think that I should spend much more time fiddling with Phabricator database schemes and SQL queries.",1420744097,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"I doubt the November numbers because ""Number of open and stalled tasks in total"" is 18296 while it was 18125 in December. This really goes into details how metadata was migrated so I would not use any November numbers. Number of tasks created in Dec is 3424 - Number of tasks closed in Dec is 2529 = +895, but 18125-18296 =  -171. And as written in that script, the numbers are not entirely correctly for December either (and I encourage anybody who wants to investigate the SQL and Phab'sDB structure to fix that).",1420743975,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#963724, @Dzahn wrote:
+> 
+> Yes, let me try to make one for November manually. I will attach it here.
+
+I can give you this part:
+
+Number of accounts created in (2014-11): 299
+Number of active users (any activity) in (2014-11): 443
+Number of task authors in (2014-11): 284
+Number of users who have closed tasks in (2014-11): 115
+Number of tasks created in (2014-11): 1916
+Number of tasks closed in (2014-11): 814
+Number of tasks in the shell project closed as resolved,fixed in (2014-11): 4
+
+Number of open and stalled tasks in total: 18296
+
+
+Is that sufficient? It was easier to make than the lower part.",1420742737,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#961920, @Qgil wrote:
+> The report send on January 1 looks good! Thank you very much. I have [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-January/079999.html | forwarded it to wikitech-l ]], wondering whether there is a way to sending it there automatically.
+
+Yes, i can send it to wikitech by just adding the list address as a recipient. But one of the list admins has to also list the sender address in list settins somewhere as a verified ""non-member"" or we have to subscribe a fake user, otherwise the list will reject mail from an address it doesn't recognize as a subscribed member.
+
+> 
+> Also, would it possible to generate one report for November 2014? It's the month of the Bugzilla migration and any data needs to be taken with a big grain of salt. Still, having Bugzilla data until October and Phabricator data from December, it would be good to cover November for posterity.
+
+Yes, let me try to make one for November manually. I will attach it here.
+",1420740255,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#961937, @KartikMistry wrote:
+> Is it possible to get teamwise statistics? (eg: Language Engineering) (Just wishlist) :)
+
+We are no thee yet (at all), but see T28.",1420710699,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,Is it possible to get teamwise statistics? (eg: Language Engineering) (Just wishlist) :),1420701318,PHID-USER-abr5ge6gl2ovg7jokpst,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"The report send on January 1 looks good! Thank you very much. I have [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-January/079999.html | forwarded it to wikitech-l ]], wondering whether there is a way to sending it there automatically.
+
+Also, would it possible to generate one report for November 2014? It's the month of the Bugzilla migration and any data needs to be taken with a big grain of salt. Still, having Bugzilla data until October and Phabricator data from December, it would be good to cover November for posterity.",1420700674,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,♥! Thanks Dzahn!,1419343197,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"resolving per: ""This task can be closed as soon as we can publish monthly metrics for total amount of users and active in the past month.""",1419342160,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Quim said:  ( for some reason I can't hit ""quote"" on his comment)
+>Is it possible to add these to the report?
+>Number of accounts created
+
+This has been added now with  https://gerrit.wikimedia.org/r/#/c/181564/
+
+""Number of accounts created in (2014-11): 299""
+",1419341992,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Change 181564 merged by Dzahn:
+phab metrics: add number of accounts created
+
+[[https://gerrit.wikimedia.org/r/181564]]",1419341847,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Change 181564 had a related patch set uploaded (by Dzahn):
+phab metrics: add number of accounts created
+
+[[https://gerrit.wikimedia.org/r/181564]]
+
+#patch-for-review",1419341700,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#939636, @Aklapper wrote:
+> @dzahn: Does that require a separate ticket, or how to proceed?
+
+It does, but it already exists. I reopened T78311 with the additional requirement and it's linked here as a blocker.",1419252608,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#852987, @Dzahn wrote:
+> Access denied for user 'phstats'@...  [...] This requires a change in DB GRANTS.
+
+@dzahn: Does that require a separate ticket, or how to proceed?",1419252523,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>>! In T1003#851249, @Aklapper wrote:
+>> Uh, //daily//? The idea was monthly (see topic), otherwise the queries using INTERVAL 1 MONTH would likely create some weird results. :)
+
+The cron job is changed now to run on the 1st of every month:
+
+Puppet Name: phabstatscron_communitymetrics
+0 0 1 * * /srv/phab/tools/community_metrics.sh
+
+The third field is ""day of the month"".
+
+
+",1418816090,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>>! In T1003#851249, @Aklapper wrote:
+>> Uh, //daily//? The idea was monthly (see topic), otherwise the queries using INTERVAL 1 MONTH would likely create some weird results. :)
+
+The cron job is changed now to run on the 1st of every month:
+
+# Puppet Name: phabstatscron_communitymetrics
+0 0 1 * * /srv/phab/tools/community_metrics.sh
+
+The third field is ""day of the month"".
+
+
+",1418816067,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#852435, @Aklapper wrote:
+> but using $sql_name in the script won't work here as that is on the ""phabricator_user"" DB instead.
+
+Access denied for user 'phstats'@...  The phstats user (and also the phuser user) don't have access to the ""phabricator_user"" database, only to the ""phabricator_maniphest"" database. This requires a change in DB GRANTS.",1418815860,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#852435, @Aklapper wrote:
+>>>! In T1003#851771, @chasemp wrote:
+>> can I get on this list?
+> 
+> You need to bribe mutante.
+
+No, there's no need for bribes. It's an exim alias defined in the private puppet repo.
+
+@palladium:~/private/modules/privateexim/files/wikimedia.org
+
+commit 38f50add7650b9ab524a7a7202bf6a3226a9d695
+
+done:  dzahn: add Chase to communitymetrics@ alias",1418814889,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"```
+Hi Community Metrics team,
+
+this is your automatic monthly Phabricator statistics mail.
+
+Number of active users (any activity) in (2014-11): 433
+Number of task authors in (2014-11): 269
+Number of users who have closed tasks in (2014-11): 115
+Number of tasks created in (2014-11): 1841
+Number of tasks closed in (2014-11): 814
+Number of tasks in the shell project closed as resolved,fixed in (2014-11): 4
+
+Number of open and stalled tasks in total: 17463
+
+Median age in days of open tasks by priority:
+Unbreak now: 130
+Needs Triage: 143
+High: 206
+Normal: 444
+Low: 683
+Needs Volunteer: 545
+
+TODO: Numbers which refer to closed tasks might not be correct, as described in T1003.
+
+Yours sincerely,
+Fab Rick Aytor
+
+(via community_metrics.sh on iridium at Tue Dec 16 15:50:10 UTC 2014)
+```
+
+>>! In T1003#851249, @Aklapper wrote:
+>>>! In T1003#850735, @Dzahn wrote:
+>> let me know if you don't receive it daily from now on
+> 
+> Uh, //daily//? The idea was monthly (see topic), otherwise the queries using INTERVAL 1 MONTH would likely create some weird results. :)
+
+-->   https://gerrit.wikimedia.org/r/#/c/180444/
+
+",1418814706,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#851771, @chasemp wrote:
+> can I get on this list?
+
+You need to bribe mutante.
+
+>>! In T1003#851812, @Qgil wrote:
+> Is it possible to add these to the report?
+
+Should be. A bit late so dropping that here instead of cooking up a Gerrit patch directly:
+
+>> Number of accounts created
+
+SELECT COUNT(id) FROM user WHERE FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+but using $sql_name in the script won't work here as that is on the ""phabricator_user"" DB instead.
+
+>> Number of users logging
+
+Already covered by ""Volume of contributors (any activity) in last month"" already, I think? If not, what's the 𝝙? 
+There's a ""dateMotified"" column but not sure what that really refers to, probably not helpful.",1418788051,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Is it possible to add these to the report?
+
+> Number of accounts created
+> Number of users logging
+
+And I agree with @Nemo_bis, sending this email to wikitech-l every month would be great.",1418767726,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,can I get on this list?,1418767095,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,This is just great. I'm so happy. Thank you!,1418766184,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#850735, @Dzahn wrote:
+> let me know if you don't receive it daily from now on
+
+Uh, //daily//? The idea was monthly (see topic), otherwise the queries using INTERVAL 1 MONTH would likely create some weird results. :)",1418754282,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"needed one more small fix:
+
+https://gerrit.wikimedia.org/r/#/c/180193/
+
+but now it works, puppet applied it and i tested it.
+
+the communitymetrics@ mail alias should now receive this. (currently qgil and aklapper)
+
+i ran it once manually for you to get it now without having to wait for the cronjob.
+
+let me know if you don't receive it daily from now on",1418745354,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"merged PS10 https://gerrit.wikimedia.org/r/#/c/177792/
+
+puppet-compiler: http://puppet-compiler.wmflabs.org/558/change/177792/html/iridium.eqiad.wmnet.html
+
+on iridium:
+
+Notice: /Stage[main]/Role::Phabricator::Main/Phabricator::Logmail[communitymetrics]/Cron[phabstatscron_communitymetrics]/ensure: created
+Notice: /Stage[main]/Role::Phabricator::Main/Phabricator::Logmail[communitymetrics]/File[/srv/phab/tools/community_metrics.sh]/ensure: created
+",1418744156,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Change 177792 merged by Dzahn:
+phabricator: community metrics stats mail
+
+[[https://gerrit.wikimedia.org/r/177792]]",1418743166,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#850592, @Aklapper wrote:
+> Works locally. Now waiting for Daniel to trigger another test email to me.
+
+yep, works for me. i ran it on iridium and triggered the test email
+",1418741492,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"I've added a few more patchsets / revisions to https://gerrit.wikimedia.org/r/#/c/177792/ :
+* worked around (fixed?) the two empty SQL query results by setting an empty column name via AS ' '
+* added the way more performant ""median age of open tasks by priority"" queries (see last comment)
+* removed backticks surrounding one variable to not get an invalid SQL query error for the median-age queries when calling those SQL queries from a bash script, works also as expected without them
+* as the new median-age queries' output is a float instead of an integer, cut the .0000 resp .5000 suffixes so there's no ""invalid arithmetic operator"" syntax error anymore
+
+Works locally. Now waiting for Daniel to trigger another test email to me.",1418740899,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#850332, @Aklapper wrote:
+> * For unknown reasons (those SQL queries work locally, maybe the  //cut -d "" "" -f3// in the script itself but hard to imagine), the following two values in that email are just empty: 
+> ** Number of tasks created in (2014-11): 
+> ** Number of open and stalled tasks in total: 
+
+when i run the query for ""tasks created"" directly on the database i get this:
+
+
+```
+MariaDB MISC m3 localhost phabricator_maniphest > SELECT COUNT(*) FROM maniphest_task WHERE 
+    ->     FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
++----------+
+| COUNT(*) |
++----------+
+|     1841 |
++----------+
+
+```
+
+in the script the variable $result_taskscreated"" becomes this though:
+
+""created: COUNT(*)
+1841"" 
+
+i added the "" , but the variable contains COUNT(*) and the line break and then the actual value.",1418734902,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Status update:
+* Daniel triggered a ""Phabricator monthly statistics"" test email to my account last week.
+* For unknown reasons (those SQL queries work locally, maybe the  //cut -d "" "" -f3// in the script itself but hard to imagine), the following two values in that email are just empty: 
+** Number of tasks created in (2014-11): 
+** Number of open and stalled tasks in total: 
+* Daniel had to kill the queries I had pasted above under //Median age of open tasks by priority// as they have a horrible runtime. Yesterday I created 2500 tasks in local Phab instance and it already took 50-75sec so I stole [[ http://stackoverflow.com/questions/1291152/simple-way-to-calculate-median-with-mysql/7263925#7263925 | a better query from stackoverflow ]]. Output difference is small enough as we're talking about days here. Comparison below.
+** Output isn't an integer though, hence the //epochnow-mediantasksopen_needsvolunteer_epoch// part in https://gerrit.wikimedia.org/r/#/c/177792/7/modules/phabricator/templates/community_metrics.sh.erb to calculate the delta between current time and the output value might bark if it expects integers? Don't know, didn't have time to test with an actual similar shell script yet and my bash script times are long ago.
+```
+MariaDB [phabricator_maniphest]> SELECT x.dateCreated from maniphest_task x, maniphest_task y WHERE (x.priority = ""80"" AND x.status = ""open"") GROUP BY x.dateCreated HAVING SUM(SIGN(1-SIGN(CAST(y.dateCreated AS SIGNED)-CAST(x.dateCreated AS SIGNED))))/COUNT(*) > .5 LIMIT 1;                           +-------------+
+| dateCreated |
++-------------+
+|  1418715703 |
++-------------+
+1 row in set (59.33 sec)
+
+MariaDB [phabricator_maniphest]> SELECT avg(t1.dateCreated) as median_val FROM (SELECT @rownum:=@rownum+1 as `row_number`, d.dateCreated FROM maniphest_task d, (SELECT @rownum:=0) r WHERE (d.priority = ""80"" AND d.status = ""open"") ORDER BY d.dateCreated) as t1, (SELECT COUNT(*) AS total_rows FROM maniphest_task d WHERE (d.priority = ""80"" AND d.status = ""open"")) as t2 WHERE 1 AND t1.row_number IN ( floor((total_rows+1)/2), floor((total_rows+2)/2));
++-----------------+
+| median_val      |
++-----------------+
+| 1418715752.0000 |
++-----------------+
+1 row in set (0.24 sec)
+```",1418733503,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#844983, @kevinator wrote:
+> This might be a cheap way to get a visualization of the data.
+
+Thanks. We might play with this once we have the actual queries in place and their text output working.",1418733497,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"When I saw the wiki with [[ https://www.mediawiki.org/wiki/Talk:Community_metrics#Bugzilla_stats | number of active bugzilla users ]],  I wondered if you knew about the graph extension that lets you embed graphs into wiki pages.  This was also an excuse for me to play with the extension:
+
+bugzilla users: https://www.mediawiki.org/wiki/Talk:KLeduc_(WMF)/test_graph_extension
+the data: https://www.mediawiki.org/wiki/Talk:KLeduc_(WMF)/test_graph_extension_data
+the extension: https://www.mediawiki.org/wiki/Extension:Graph
+
+This might be a cheap way to get a visualization of the data.
+",1418420262,PHID-USER-p3bvg5sos3lhe33uou2s,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Change 177792 had a related patch set uploaded (by Nemo bis):
+phabricator: community metrics stats mail
+
+[[https://gerrit.wikimedia.org/r/177792]]
+
+#patch-for-review",1418297404,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"> start humble with sql queries
+
+Speaking of which. As the Bugzilla weekly report is no more :[, this update could be sent directly to wikitech-l and called ""Phabricator monthly report"", with an expectation that new content might be added to it later (or not).",1418297353,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#821248, @chasemp wrote:
+> There is a ""Fact"" app that is pretty young, but it may make more sense to put our time into that https://secure.phabricator.com/fact/
+
+Upstream told us clearly that it's not worth for us to try to step in to improve Fact or surroundings, before they do some homework in the background. This is one of the reasons why I'm proposing to start humble with sql queries. See https://secure.phabricator.com/T1562#80158 and below.",1417802170,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,https://gerrit.wikimedia.org/r/#/c/177792/,1417798749,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"There is a ""Fact"" app that is pretty young, but it may make more sense to put our time into that https://secure.phabricator.com/fact/",1417787422,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Let's have a separate ticket for some stats app in Phab.
+To avoid confusion:
+This ticket was originally about the cronjob that once a month sent an email with a single number to Quim and me: The number of active users in Bugzilla in the last month.
+We want that for Phab too as we like to have some basic metrics.
+
+As Phab's reporting tools are a bit limited currently and as we have not ported the backend of korma.wmflabs.org to support Phab (see T28) we're now missing some more statistics that we had on korma.
+Hence as a poor man's solution, I'd like to extend that cronjob script by some more sql queries, for the time being. Some of them provide data that we had on korma, though now in a non-visual way, but better than nothing for the time being.
+
+Let's have a potential future ""Stats"" app in Phab either handled in T28, or in a separate ticket. :)",1417783219,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,we could probably create a 'stats' app in phabricator that would provide a simple ui for executing these queries and displaying the data in a reasonably nice way. It would be a significant amount of work but not huge or difficult.,1417647785,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"> Volume of tasks in the ""shell"" project resolved/fixed in last month, requested by Guillaume
+
+Hmm, no, I can't https://phabricator.wikimedia.org/conduit/method/maniphest.query/ see supporting that query either. Meh.
+
+This query seems to work locally for me, but it has the same problem as the other ""closed"" queries above:
+
+SELECT COUNT(DISTINCT objectPHID) FROM maniphest_transaction JOIN maniphest_nameindex JOIN edge WHERE (maniphest_nameindex.indexedObjectName=""shell"" AND maniphest_nameindex.indexedObjectPHID=edge.dst AND edge.src=maniphest_transaction.objectPHID) AND (transactionType=""status"" AND (oldValue=""\""open\"""" OR oldValue=""\""stalled\"""") AND newValue=""\""resolved\"""") AND FROM_UNIXTIME(maniphest_transaction.dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');",1417647449,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Note to myself: Add another query for ""shell requests closed in last month"" for Guillaume as the UI does not offer that and add Guillaume to recipients. (I've also had two other ideas how to get that data but for this one I know it'll work.)",1417618555,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,">>! In T1003#793868, @Dzahn wrote:
+> Once we are at the point where we have more specific SQL queries you want to be executed and results mailed to people, ping me and I can puppetize that similar to how the BZ mails worked in the past. 
+
+@Dzahn: I hereby ping you. :) 
+If you could put the above SQL queries (which at least worked locally here for me) into a monthly cronjob email like the previous ""bugzilla stats - 2014-10"" ones (we can test now by triggering the one for November), that would be lovely. 
+The last query listed here needs to be included several times to also cover those other x.priority values available.
+And I can probably finetune&review a patch in Gerrit...",1417437909,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Bringing the useful queries here...
+
+>>! In T28#793720, @Aklapper wrote:
+> I'm not patient enough to read API references for Conduit to find out if I can do what I want, so I played with SQL. 
+> Below queries are on the ""phabricator_maniphest"" database and //obviously need a second pair of eyes//.
+> 
+>> Volume of tasks created in last month
+> SELECT COUNT(*) FROM maniphest_task WHERE FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+>> Volume of tasks closed in last month
+> 
+> SELECT COUNT(DISTINCT objectPHID) FROM maniphest_transaction WHERE (transactionType=""mergedinto"" OR (transactionType=""status"" AND (oldValue=""\""open\"""" OR oldValue=""\""stalled\"""") AND (newValue=""\""resolved\"""" OR newValue=""\""invalid\"""" OR newValue=""\""declined\""""))) AND FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+> //Not sure about this one - need to make objectPHID value describing the task ID to be distinct because otherwise every status editwarring counts but not sure if DISTINCT picks the first or the last entry? Other option is to compare with ""maniphest_task.phid"" and ""maniphest_task.status"" but that one has a ""duplicate"" status while in ""maniphest_transaction.transactionType"" that's not a status, see query above.)//
+> 
+>> Volume of tasks open in total
+> 
+> SELECT COUNT(*) FROM maniphest_task WHERE (status = ""open"" OR status = ""stalled"");
+> 
+>> Volume of contributors (any activity) in last month
+> 
+> SELECT COUNT(DISTINCT authorPHID) FROM maniphest_transaction WHERE FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+>> Volume of authors in last month
+> 
+> SELECT COUNT(DISTINCT authorPHID) FROM maniphest_task WHERE FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+>> Volume of resolvers in last month
+> 
+> SELECT COUNT(DISTINCT authorPHID) FROM maniphest_transaction WHERE (transactionType=""mergedinto"" OR (transactionType=""status"" AND (oldValue=""\""open\"""" OR oldValue=""\""stalled\"""") AND (newValue=""\""resolved\"""" OR newValue=""\""invalid\"""" OR newValue=""\""declined\""""))) AND FROM_UNIXTIME(dateCreated,'%Y%m')=date_format(NOW() - INTERVAL 1 MONTH,'%Y%m');
+> 
+> //Same problem with this query as above for closed tasks.//
+> 
+>> Median age of open tasks by priority (excluding Needs Volunteer)
+> 
+> SELECT x.dateCreated from maniphest_task x, maniphest_task y WHERE (x.priority = ""80"" AND x.status = ""open"") GROUP BY x.dateCreated HAVING SUM(SIGN(1-SIGN(CAST(y.dateCreated AS SIGNED)-CAST(x.dateCreated AS SIGNED))))/COUNT(*) > .5 LIMIT 1;
+> 
+> //Output is a unix epoch of the average *ticket creation time* for that prio so still need to do the math to subtract from today's timestamp and convert to days. x.priority values are: 100=UnbreakNow, 80 = High; 50 = Normal; 90 = NeedsTriage; 25 = Low; 10 = NeedsVolunteer/Lowest. And those two casts in the query are needed to [[ http://dev.mysql.com/doc/refman/5.5/en/out-of-range-and-overflow.html | avoid an overflow ]], at least on my machine.//
+> 
+> Wondering if a dirty monthly script [[ http://git.wikimedia.org/blob/operations%2Fpuppet.git/7cc72ccf87ff2da41009f47727b8461771011634/modules%2Fbugzilla%2Ftemplates%2Fscripts%2Fbugzilla_community_metrics.sh.erb | like the one we had for Bugzilla ]] would give the Engineering Community Team at least basic insight, not expecting shiny stuff like we had on korma to appear soon?
+
+To me this is a no brainer. That dirty monthly script was very useful, and I'm missing it already.",1417295754,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,I'm afraid I pasted some useful queries for this ticket in T28#793720 instead.,1417217249,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Once we are at the point where we have more specific SQL queries you want to be executed and results mailed to people, ping me and I can puppetize that similar to how the BZ mails worked in the past. ",1417214765,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"Looking at the metrics proposed in the description, what do you think we could obtain in relation to these dates?
+
+* Opening of the production instance
+* Right before closing for the Bugzilla migration
+* Right after the migration
+* End of November
+* and then, end of every month
+
+We have our #Engineering-Community quarterly review on mid January. I want to bring Phabricator metrics there, because it would be useful, and because it is assured that Lila & co will ask for them.",1417034599,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Monthly report of total / active Phabricator users,"After having a very quick look at the database scheme: 
+In the ""phabricator_user"" database, the ""user"" table has ""id"" and ""phid"" columns to identify users. There's also ""dateModified"" and ""dateCreated"" (new registrations) columns with values stored in Unix epoch format (to base timespan queries against). The ""user_log"" table also has a ""dateModified"" column for any user's actions, stored in Unix epoch format. 
+Also wondering if the ""maniphest_transaction"" and ""maniphest_transaction_comment"" tables from the ""phabricator_maniphest"" databases could provide activity data. Need to play more if I find time.",1415566541,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-dyo7e4yq3hpypzt6oaid,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Let's track progress on the migration of this team to Phabricator. Feel free editing this task description.
+
+[ ] Team member assigned to this task
+[ ] Link(s) to the current projects in Mingle, Trello, other
+[ ] (optional) Have you scheduled a team meeting with @Qgil to discuss the migration? (yyyy-mm-dd)
+[ ] Blockers of the migration identified: (list the task numbers between {curly brackets})
+[ ] Planned date for the migration/creation of a first real project: yyyy-mm-dd
+[ ] Do you plan to have all your projects moved by the end of 2014? Yes/No, and if not, why
+(...)
+[ ] More than half of our team members and ongoing sprints are working in Phabricator now (yyyy-mm-dd)
+[ ] All our projects have been moved to Phabricator. Mission completion! (yyyy-mm-dd)",1414050574,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_description,resolved
+Migration of Research & Data to Phabricator,yup,1433943903,PHID-USER-qb5aoo443n6fezsozhv4,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Can we Close Resolved, then?",1433938999,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,Research team is in Phab.  Per @DarTar the remaining Trello boards do not need to be migrated.,1433459928,PHID-USER-boqv2doznygy3kwrkyly,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Thanks, @Spage!
+
+I think that we are done with the Research and Data board from Trello.
+
+We need to groom the Research and Data backlog board and migrate what survives....grooming is scheduled for Thurs 2015-05-21.
+
+@DarTar - does that sound correct?",1431720054,PHID-USER-boqv2doznygy3kwrkyly,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I migrated the Trello columns Completed - In Progress - Incoming requests (external) - Time sensitive - Blocked, and I think Grace has dragged the Phab tasks into shape. Are we done?
+
+𝄞 //We are Phamily, I got all my sisters with me// ♬  – Sister Sledge",1431651486,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I migrated the Trello columns Completed - In Progress - Incoming requests (external) - Time sensitive - Blocked and I think Grace has dragged the Phab tasks into shape. Are we done?
+
+𝄞 //We are Phabily, I got all my sisters with me// ♬  – Sister Sledge",1431651440,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"@Spage  Please migrate Incoming requests (external) and In Progress sequentially and check with me after each import.
+
+Then I can manually create cards fromTime Sensitive and Blocked in Trello in Phab myself.",1431642342,PHID-USER-boqv2doznygy3kwrkyly,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Thanks, @Spage!
+
+I have created column for Staged (ready to execute) in Phab Research and Data board:
+
+1.  moved cards relevant cards from backlog to Staged (ready to execute) column
+2.  reviewed each card and replicated Trello comments that didn't make it over to Phab Research and Data tasks 
+
+Please migrate the next Trello swim lane.",1431625752,PHID-USER-boqv2doznygy3kwrkyly,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I migrated ""Staged (ready to execute)"", e.g. Trello card [[ https://trello.com/c/BNf0xY6P/632-mid-article-recommendation-for-content-translation | mid Article recommendation for Content Translation ]] became T99040. Details on [[ https://www.mediawiki.org/wiki/Phabricator/Trello_to_Phabricator/Research_import | Trello to Phabricator/Research import ]] page.
+
+@ggellerman, @DarTar, step 4 above. Try creating the equivalent column in phabricator and dragging cards, look for obvious errors beyond the missing features mentioned in {T821}, let me know if it's OK to migrate the rest.",1431590979,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"@qgil Search-and-Discovery-Research-and-Data-Sprint is not related to my team, it's an internal board used by the S/D team.
+
+@spage the following are done (copied you)
+
+  # Need list of user name mappings Trello -> Phabricator
+  # Heads up migration is starting
+
+",1431563367,PHID-USER-qb5aoo443n6fezsozhv4,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @ggellerman:
+
+The main Trello board to migrate is [[ https://trello.com/b/k5N0ivoM/research-and-data | Research and Data ]]. Dario moved the one column in the Trello  ""Research and Data - backlog"" board to migrate into this.
+
+# ☑ Need list of user name mappings Trello -> Phabricator
+# ☑Heads up migration is starting
+# ☑ spage migrate one column, probably ""Staged (ready to execute)""
+# ☑ Grace and Dario look at it
+# ☑ Heads up the entire migration is happening
+# ☑ spage migrates the rest
+# ☑ Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research workboard, have tags for specific Research projects like VisualEditor //Xxx research//
+, and then filter the workboard by these tags (workboard > Filter > Advanced Filter... > Projects ) to see the status of particular projects.",1431650926,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @ggellerman:
+
+The main Trello board to migrate is [[ https://trello.com/b/k5N0ivoM/research-and-data | Research and Data ]]. Dario moved the one column in the Trello  ""Research and Data - backlog"" board to migrate into this.
+
+# ☑ Need list of user name mappings Trello -> Phabricator
+# ☑Heads up migration is starting
+# ☑ spage migrate one column, probably ""Staged (ready to execute)""
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research workboard, have tags for specific Research projects like VisualEditor //Xxx research//
+, and then filter the workboard by these tags (workboard > Filter > Advanced Filter... > Projects ) to see the status of particular projects.",1431591048,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @ggellerman:
+
+The Main Trello board to migrate is [[ https://trello.com/b/k5N0ivoM/research-and-data | Research and Data ]]. Dario moved the one column in the Trello  ""Research and Data - backlog"" board to migrate into this.
+
+# ☑ Need list of user name mappings Trello -> Phabricator
+# ☑Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research workboard, have tags for specific Research projects like VisualEditor //Xxx research//
+, and then filter the workboard by these tags (workboard > Filter > Advanced Filter... > Projects ) to see the status of particular projects.",1431575761,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @ggellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# ☑ Need list of user name mappings Trello -> Phabricator
+# ☑Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research board, have tags for specific Research projects, and then filter the workboard to show the tasks in particular projects.",1431575206,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @GraceGellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# Need list of user name mappings Trello -> Phabricator
+# Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have all tasks on a big Research board, have tags for specific Research projects, and then filter the workboard to show the tasks in particular projects.",1431558673,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @GraceGellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# Need list of user name mappings Trello -> Phabricator
+# Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# Grace renames the Trello boards to append MIGRATED TO PHAB, etc.
+
+Their plan is to have a big Research board, and then filter ",1431558481,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @GraceGellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# Need list of user name mappings Trello -> Phabricator
+# Heads up migration is starting
+# spage migrate one column, probably ""Staged (ready to execute)"" maybe do it Thursday
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# 
+
+Their plan is to have a big Research board, and then filter ",1431558428,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"meet with @DarTar and @GraceGellerman:
+In Phabricator will have:
+master project list for quarterly priorities
+Research project list
+Projects for individual tasks
+
+Main Trello board to migrate is ""Research and Data"", also a ""Research and Data - backlog"" board. Only migrate some of the latter - Dario moved the column to migrate to #Research-and-Data.
+
+# Need list of user name mappings Trello -> Phabricator
+# Heads up migration is starting
+# spage migrate one column
+# Grace and Dario look at it
+# Heads up the entire migration is happening
+# spage migrates the rest
+# 
+
+Their plan is to have a big Research board, and then filter ",1431558313,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I just learned about #Search-and-Discovery-Research-and-Data-Sprint
+
+Progress!",1431002533,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Hi, I'm preparing the Phabricator migration statistics for the #Engineering-Community quarterly review. Currently {T434} reports that your situation with Phabricator is 
+
+  0	  Not started
+
+Is this accurate?",1427461738,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"@Qgil yes we'll definitely need this, I think we're not yet ready though (we need to review the other blockers first and I want to make sure we don't start creating duplicate cards until we're completely ready for the migration).",1425496849,PHID-USER-qb5aoo443n6fezsozhv4,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"If/when you decide to move to Phabricator entirely, will you need migration of Trello cards to Phabricator tasks, aka someone to run {T821}?",1425032994,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"I removed Analytics-Engineering because their migration is complete.
+
+Note that ""Restricted Project"" in the task description refers to Analytics Research & Data. Someone tweaked its permissions.
+
+Who should be the owner of this task? It would be good to have a point of contact.",1419856213,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,@Ironholds has started a discussion about [[ https://lists.wikimedia.org/pipermail/analytics/2014-December/002894.html | Analytics Research & Data migrating to Phabricator ]] in the Analytics mailing list. It's a very interesting post that could be extrapolated to most WMF tech teams.,1418591948,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Hi Quim -- we really need the sprint extension to confirm our migration. If this doesn't meet our needs, we'll need to revisit our use of Phabricator.
+
+R&D does not have plans to move off of Trello at this time.
+
+No more teams within Analytics.
+
+-Toby",1418062562,PHID-USER-ud7f5gp5h3uqup6viq4e,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"Here are Research & Data Trello boards:
+
+https://trello.com/b/k5N0ivoM/research-and-data
+https://trello.com/b/UcQSC5Au/research-and-data-backlog
+https://trello.com/b/CSltHJXs/research-and-data-archive",1418055207,PHID-USER-boqv2doznygy3kwrkyly,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"In relation to T434,
+
+#Analytics-Engineering looks pretty active. Can we consider this team fully migrated to Phabricator, or are there still tasks / sprints / projects active elsewhere?
+
+#research-and-data seems to be still 100% in Trello. Can you provide a link to access their board(s), please?
+
+Are there more teams within in Analytics?
+
+PS: T1322 is planned for this Wednesday.",1418050182,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"In relation to T434,
+
+#Analytics-Engineering looks pretty active. Can we consider this team fully migrated to Phabricator, or are there still tasks / sprints / projects active elsewhere?
+
+#research-and-data seems to be still 100% in Trello. Can you provide a link to access their board(s), please?
+
+PS: T1322 is planned for this Wednesday.",1418050131,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"As discussed, the scrumbugz style burndowns are blockers for our migration (T1322)
+
+We're excited for this feature! Let us know if we can help.",1417457241,PHID-USER-ud7f5gp5h3uqup6viq4e,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Migration of Research & Data to Phabricator,"As per T434 , in the following days I plan to scan the levels of use of Phabricator by all the WMF product & engineering teams. Please keep the description of this task up to date.",1417075841,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-u474tffzkippspfbkwn7,task_subcomment,NA
+Deliver (global version of) VisualEditor newsletter #9 for 2014,,1414000841,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zfix24cb4ecmeq3x62k4,task_description,resolved
+Write VisualEditor newsletter #9 for 2014,,1414000792,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-4kmfp6xox5jr7cpq77bb,task_description,resolved
+Write VisualEditor newsletter #9 for 2014,Checking in to see if this needs to be modified or closed?,1422295464,PHID-USER-v7pv6vw32wp56vc4wyt7,True,PHID-TASK-4kmfp6xox5jr7cpq77bb,task_subcomment,NA
+Work on the VisualEditor newsletter for November 2014,,1413980113,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-eka3irpvy3o5kqmxjf5b,task_description,resolved
+Work on the VisualEditor newsletter for November 2014,"Change 496060 **merged** by jenkins-bot:
+[pywikibot/core@master] [tests] Fix flake8-tuple T801 error
+
+[[https://gerrit.wikimedia.org/r/496060]]",1552650409,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-eka3irpvy3o5kqmxjf5b,task_subcomment,NA
+Work on the VisualEditor newsletter for November 2014,"Change 496060 had a related patch set uploaded (by Xqt; owner: Xqt):
+[pywikibot/core@master] [tests] Fix flake8-tuple T801 error
+
+[[https://gerrit.wikimedia.org/r/496060]]",1552428207,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-eka3irpvy3o5kqmxjf5b,task_subcomment,NA
+Severity information is not being migrated,"We agreed that the Severity information would be printed in the task description, since we decided not to have such field in Phabricator. Currently this information is missing in bugzillapreview. See for instance https://bugzilla.wikimedia.org/show_bug.cgi?id=57540 (Severity: critical)",1413672057,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_description,resolved
+Severity information is not being migrated,"Available Severity values in Bugzilla are
+* blocker
+* critical
+* major
+* normal
+* minor
+* trivial
+* enhancement
+and there is no conversion; this will just be added to the task description in Phabricator. Severity cannot be unspecified.",1416401407,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"I'm not sure I understand your request. So the only problem here is that you expect that the ""Severity: "" text string is documented in /versus_Bugzilla, reflecting all the possible values, including the case where it is unspecified, right? 
+
+I expect the answer to be
+
+* blocker
+* critical
+* major
+* normal
+* minor
+* trivial
+* enhancement
+* unspecified
+
+I will ask.
+
+The way to retrieve this information is a search query.",1416389124,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Reopen because [[Phabricator/Help]] is silent on severity and [[Phabricator/versus Bugzilla]] only says «Also note that Severity, Version, URL, Whiteboard, and other fields will not be available in Phabricator, because we have decided to discontinue them. The related data available in Bugzilla reports will be added to the description of the task.» Users need documented workarounds to access the information in question, such as the translation between previous and future values that Aklapper implied in https://phabricator.wikimedia.org/T695#12650",1416387949,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"I'm having issues trying to reconcile contradictory indications:
+> Let's drop the string values of ""severity"" (and ""whiteboard"" seems also not to be in yet, looking at bugzilla_create.py) as plain text in the initial description.
+(apparently done) vs.
+> you could always query tasks in project X with the string ""Severity: Critical""
+
+What's the current status? Are we sure that users were actually able to understand how the imported tasks will look like as regards ""Severity"", even though the import was changed after the bugzilla preview? (Cf. T552 which declined the creation of a final preview.)
+
+>>! In T695#13006, @Jdforrester-WMF wrote:
+> Actually, those are indeed untriaged and should be marked as such. :-)
+
+So, if the others are triaged, this leaves us with 568 triaged tickets which received a non-default severity. https://bugzilla.wikimedia.org/buglist.cgi?bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=minor&bug_severity=trivial&bug_severity=enhancement&list_id=359859&priority=Immediate&priority=Highest&priority=High&priority=Normal&priority=Low&priority=Lowest&product=OOjs&product=OOjs%20UI&product=VisualEditor&query_format=advanced&resolution=---
+How is that triaging work being preserved?",1416387680,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,">>! In T695#12650, @Aklapper wrote:
+> [offtopic]
+> 
+> In T695#12014, @Jdforrester-WMF wrote:
+>> I'm not particularly keen to re-triage 2,000 bugs in VE/OOUI/wikitext editor and others…
+> 
+> I would recommend at some point rather sooner than later to (mass-)prioritize those open VE tickets in Bugzilla with Priority=Unprioritized even if that would only be a rough categorization (e.g. set Priority=lowest for open tickets with Priority=unprioritized && Severity=enh|trivial|minor and Priority=low for Priority=unprioritized && Severity=normal|major or whatever works). Otherwise you will end up with a large list of ""Needs triage"" tickets after the Phab migration. Also note that Target Milestones will be migrated which offers another way to plan.
+
+Actually, those are indeed untriaged and should be marked as such. :-)",1413923431,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Trust you and resolve it.  :)
+
+>>! In T695#12822, @chasemp wrote:
+> This is currently:
+> 
+> {F368}
+
+Good!
+
+> What to do w/ this ticket now?
+
+Trust you and resolve it.  :)",1413914978,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"This is currently:
+
+{F368}
+
+
+What to do w/ this ticket now?",1413914778,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"[offtopic]
+
+In T695#12014, @Jdforrester-WMF wrote:
+> I'm not particularly keen to re-triage 2,000 bugs in VE/OOUI/wikitext editor and others…
+
+I would recommend at some point rather sooner than later to (mass-)prioritize those open VE tickets in Bugzilla with Priority=Unprioritized even if that would only be a rough categorization (e.g. set Priority=lowest for open tickets with Priority=unprioritized && Severity=enh|trivial|minor and Priority=low for Priority=unprioritized && Severity=normal|major or whatever works). Otherwise you will end up with a large list of ""Needs triage"" tickets after the Phab migration. Also note that Target Milestones will be migrated which offers another way to plan.",1413878015,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Good catch, sorry for the inconsistency. Let's drop the string values of ""severity"" (and ""whiteboard"" seems also not to be in yet, looking at bugzilla_create.py) as plain text in the initial description.
+
+http://www.bugzilla.org/docs/4.4/en/html/api/Bugzilla/WebService/Bug.html#get
+
+Clueless cargo cult patch in https://gerrit.wikimedia.org/r/#/c/167548/",1413804613,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"What do you want t do with this information? If you want to search candidates for next sprints, and you want to use the Severity information to help you, you could always query tasks in project X with the string ""Severity: Critical"", and that should provide you the sample you are looking for.
+
+I don't think workboards are the right tool for this task. Are you planning to have a VisualEditor workboard where each column corresponds to a severity level? Besides, Workboards are good to handle dozens of tasks anyway, not hundreds.",1413761318,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,">>! In T695#12009, @Qgil wrote:
+> The Severity field is gone for good (and yes, we can document better this fact). This task is simply about adding to the description the Severity value of the Bugzilla reports imported.
+
+I understood that it would be replaced with project board prioritisation. If that's not going to be automatically filled in it's going to be a serious pain. I'm not particularly keen to re-triage 2,000 bugs in VE/OOUI/wikitext editor and others…",1413760753,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"The Severity field is gone for good (and yes, we can document better this fact). This task is simply about adding to the description the Severity value of the Bugzilla reports imported.",1413760435,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Indeed, must not be dropped. See also https://phabricator.wikimedia.org/T102#11218",1413727805,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+Severity information is not being migrated,"Hm, actually...
+
+T102#1539 says:
+> I would not migrate Severity as a custom field, but as a searchable text string in the task description.
+
+However, {T259} says
+> Severity: To be dropped, T102
+
+and consequently, https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Bugzilla_data_migrated says 
+> Severity - Not migrated
+
+Considering that we agreed that the latter is the canonical reference, the script works as specified. However, I believe something got lost in the requirements? If we add ""Hardware/OS"" to the description, we might as well add Severity.",1413672681,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-oymg4uxerfmmmfg76vbm,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Currently these fields are being always printed in the bugzillapreview:
+
+> URL: none
+> Version: unspecified
+> See Also: none
+> Hardware/OS: unknown/unknown
+
+See for instance https://bugzillapreview.wmflabs.org/T6408
+
+If these fields contain just the defaults, they don't offer any information and are pure noise. Can we migrate these fields only when they have specific information (not the default)?
+
+**DECISION**
+
+Fields to always keep in the initial description of a Phab task, no matter what the value is set to:
+* Version
+* Severity
+Fields to drop from the initial description of a Phab task only if set to default value ""All"":
+* Platform/Hardware
+* OS
+Fields to drop from the initial description of a Phab task only if value is entirely empty:
+* URL
+* Whiteboard
+* See Also",1413671789,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_description,resolved
+"Print URL, Version, etc only when they contain data",">>! In T694#779001, @Nemo_bis wrote:
+> I'm still seeing ""unspecified"" though. https://phabricator.wikimedia.org/T54136
+
+Consistent with the decision in the description:
+
+> DECISION
+>
+> Fields to always keep in the initial description of a Phab task, no matter what the value is set to:
+> 
+> Version
+> Severity",1416841319,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","I'm still seeing ""unspecified"" though. https://phabricator.wikimedia.org/T54136",1416841090,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","> I compared data of tickets https://bugzillapreview.wmflabs.org/T204 https://bugzillapreview.wmflabs.org/T716 https://bugzillapreview.wmflabs.org/T828 https://bugzillapreview.wmflabs.org/T939 https://bugzillapreview.wmflabs.org/T924 https://bugzillapreview.wmflabs.org/T941 with Bugzilla and all looks perfect to me. Great great great!
+
+All 404 now, but thanks for fixing this, will make things much prettier.",1416388466,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","I compared data of tickets https://bugzillapreview.wmflabs.org/T204 https://bugzillapreview.wmflabs.org/T716 https://bugzillapreview.wmflabs.org/T828 https://bugzillapreview.wmflabs.org/T939 https://bugzillapreview.wmflabs.org/T924 https://bugzillapreview.wmflabs.org/T941 with Bugzilla and all looks perfect to me. Great great great!
+
+Leaving it to Chase to close this ticket as resolved.",1415209917,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Whoops, my thumb must have slipped on the bus.",1415209853,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#19030, @chasemp wrote:
+> Fields not shown:
+> 
+> https://bugzillapreview.wmflabs.org/T11
+
+Looks great. Thank you!",1415208243,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Fields not shown:
+
+https://bugzillapreview.wmflabs.org/T11
+
+",1415205713,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Ignore my last comment; Chase already fixed this in https://git.wikimedia.org/commit/phabricator%2Ftools.git/a0822790ea39f53020ddfdc782e2577ba9ed4289
+
+I think this can be closed, leaving that to Chase.",1415043062,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",@chasemp: https://gerrit.wikimedia.org/r/#/c/170679/,1415014517,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","To summarize the proposal that I can live with: 
+* For ""OS"" and ""hardware"" fields, drop if the value is set to ""All""
+* for ""URL"", ""Whiteboard"", ""See Also"": Drop if field is entirely empty",1414763438,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","> I would go so far as to say that the default values (even ""Severity""==""normal"") should just be dropped, since chances are, no human ever cared enough about it to change it.
+
+Some triagers do, especially correcting by setting the hard to discover ""enhancement"" value. Severity information was explicitly requested in T695 hence I'd always keep it.
+
+> What about keeping Version and Severity in all cases, and the rest only when there is a value different than the default?
+
+I think I've gotten tired of discussing so I can live with that and what Quim proposes here. 
+Wondering if ""the values can be inferred by their absence"" should be ""documented"" on https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla though.
+
+More numbers for completeness, talking about 72760 tickets in Bugzilla:
+* ""Platform"" (Hardware) field ever changed (!) to current default ""All"": [[ https://bugzilla.wikimedia.org/buglist.cgi?f1=rep_platform&o1=changedto&query_format=advanced&v1=All | 2524 tickets ]]
+* ""OS"" field ever changed to current default ""All"": [[ https://bugzilla.wikimedia.org/buglist.cgi?f1=op_sys&o1=changedto&query_format=advanced&v1=All | 2502 tickets ]]
+* In both cases I can imagine that many reporters religiously filled out all fields just describing which OS and Browser s/he used though totally irrelevant for the actually reported bug (and hence set back to default ""All"" when somebody cared about metadata)
+* ""Severity"" field ever changed to current default ""Normal"": [[ https://bugzilla.wikimedia.org/buglist.cgi?f1=bug_severity&o1=changedto&query_format=advanced&v1=Normal | 2109 tickets ]]
+* (Default) Values for ""Version"" are per product and not global, hence no simple numbers.",1414694780,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","What about keeping **Version** and **Severity** in all cases, and the rest only when there is a value different than the default? Reasoning below.
+
+>>! In T694#16895, @Aklapper wrote:
+> 1) We have 4 dropdown fields with pre-defined values. By nature these fields must have one selected pre-defined value set: 
+>  * Version
+
+In fact Version is a hybrid: many products/components don't have a concept of version, and Bugzilla forces the related reports to have the only possible value: ""unspecified"" ([[ https://bugzilla.wikimedia.org/enter_bug.cgi?product=Analytics | example ]]). [[ https://bugzilla.wikimedia.org/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Analytics&product=Commons+App&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s+Tools&product=Logwood&product=Mathoid&product=MediaWiki&product=MediaWiki+extensions&product=MediaWiki+skins&product=MediaWiki-Vagrant&product=MobileFrontend&product=mwEmbed&product=OCG&product=OOjs&product=OOjs+UI&product=openZIM&product=Parsoid&product=Pywikibot&product=QRpedia&product=Spam&product=Tool+Labs+tools&product=Unofficial+Apps&product=Utilities&product=VisualEditor&product=Wiki+Loves+Monuments&product=WikiLoves+Monuments+Mobile&product=Wikimedia&product=Wikimedia+Labs&product=Wikimedia+Mobile&product=Wikipedia+App&product=Wiktionary+tools&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=LATER&resolution=DUPLICATE&resolution=WORKSFORME&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&version=.5&version=1.0.0+%28Android%29&version=1.0.3+%28Android%29&version=1.1.1+%28Android%29&version=1.3.x&version=1.4.x&version=1.5.x&version=1.6.x&version=1.7.x&version=1.8.x&version=1.9.x&version=1.10.x&version=1.11.x&version=1.12.x&version=1.13.x&version=1.14.x&version=1.15.x&version=1.16.x&version=1.17.x&version=1.18.x&version=1.19&version=1.19.0&version=1.19.1&version=1.19.2&version=1.19.3&version=1.19.4&version=1.19.5&version=1.19.6&version=1.19.7&version=1.19.8&version=1.19.9&version=1.19.10&version=1.19.11&version=1.19.12&version=1.19.13&version=1.19.14&version=1.19.15&version=1.19.16&version=1.19.17&version=1.19.18&version=1.19.19&version=1.19.20&version=1.20.x&version=1.21.x&version=1.22&version=1.22.0&version=1.22.1&version=1.22.2&version=1.22.3&version=1.22.4&version=1.22.5&version=1.22.6&version=1.22.7&version=1.22.8&version=1.22.9&version=1.22.10&version=1.22.11&version=1.22.12&version=1.23&version=1.23.0&version=1.23.1&version=1.23.2&version=1.23.3&version=1.23.4&version=1.23.5&version=1.23rc&version=1.24rc&version=1.25-git&version=2.0.21&version=2.1.19&version=2.1.21&version=2.1.22&version=2.1.23&version=3.0.0&version=3.0.1&version=3.0.2&version=3.0.3&version=3.0.4&version=3.0.5&version=3.0.6&version=3.1.0&version=3.1.0+%28iOS%29+%2F+1.1+%28Android%29&version=3.1.1&version=3.1.1+%28iOS%29&version=3.1.2&version=3.1.2+%28iOS%29&version=3.1.3&version=3.1.4&version=3.2.0&version=3.2+%28iOS%29+%2F+1.2+%28Android%29&version=Alpha&version=Android+%28alpha%29&version=Android+%28stable%29&version=Beta&version=Beta+%28Android%29&version=Beta+%28iOS%29&version=compat+%281.0%29&version=core+%282.0%29&version=iOS+%28alpha%29&version=iOS+%28stable%29&version=master&version=REL1_18+branch&version=REL1_19+branch&version=REL1_20+branch&version=REL1_21+branch&version=REL1_22+branch&version=REL1_23+branch&version=Stable&version=trunk&version=wmf-deployment&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap | 22572 reports (31%) have a version other than ""unspecified"" or ""--"" ]]. Well, ok.
+
+>  * Platform/Hardware
+
+[[ https://bugzilla.wikimedia.org/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Analytics&product=Commons+App&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s+Tools&product=Logwood&product=Mathoid&product=MediaWiki&product=MediaWiki+extensions&product=MediaWiki+skins&product=MediaWiki-Vagrant&product=MobileFrontend&product=mwEmbed&product=OCG&product=OOjs&product=OOjs+UI&product=openZIM&product=Parsoid&product=Pywikibot&product=QRpedia&product=Spam&product=Tool+Labs+tools&product=Unofficial+Apps&product=Utilities&product=VisualEditor&product=Wiki+Loves+Monuments&product=WikiLoves+Monuments+Mobile&product=Wikimedia&product=Wikimedia+Labs&product=Wikimedia+Mobile&product=Wikipedia+App&product=Wiktionary+tools&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=LATER&resolution=DUPLICATE&resolution=WORKSFORME&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&rep_platform=Macintosh&rep_platform=PC&rep_platform=Smartphone&rep_platform=Tablet+PC&rep_platform=Other&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap | 4789 reports (6.6%) have a value other than ""All"" ]]. In most cases the hardware is not even relevant, and sometimes reporters specify their hardware just because. I'm fine with migrating the values that were defined, but printing ""Platform/Hardware: All"" in 67.000 tasks is not very useful to the purpose of the task.
+
+>  * OS
+
+[[ https://bugzilla.wikimedia.org/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Analytics&product=Commons+App&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s+Tools&product=Logwood&product=Mathoid&product=MediaWiki&product=MediaWiki+extensions&product=MediaWiki+skins&product=MediaWiki-Vagrant&product=MobileFrontend&product=mwEmbed&product=OCG&product=OOjs&product=OOjs+UI&product=openZIM&product=Parsoid&product=Pywikibot&product=QRpedia&product=Spam&product=Tool+Labs+tools&product=Unofficial+Apps&product=Utilities&product=VisualEditor&product=Wiki+Loves+Monuments&product=WikiLoves+Monuments+Mobile&product=Wikimedia&product=Wikimedia+Labs&product=Wikimedia+Mobile&product=Wikipedia+App&product=Wiktionary+tools&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=LATER&resolution=DUPLICATE&resolution=WORKSFORME&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&op_sys=Windows+8.1&op_sys=Windows+8&op_sys=Windows+7&op_sys=Windows+Vista&op_sys=Windows+Server+2008&op_sys=Windows+Server+2003&op_sys=Windows+XP&op_sys=Windows+NT&op_sys=Windows+2000&op_sys=Windows+ME&op_sys=Windows+98&op_sys=Mac+OS+X+10.9&op_sys=Mac+OS+X+10.8&op_sys=Mac+OS+X+10.7&op_sys=Mac+OS+X+10.6&op_sys=Mac+OS+X+10.5&op_sys=Mac+OS+X+10.4&op_sys=Mac+OS+X+10.3&op_sys=Mac+OS+X+10.2&op_sys=Mac+OS+X+10.1&op_sys=Mac+OS+X+10.0&op_sys=Mac+System+9.x&op_sys=Linux&op_sys=FreeBSD&op_sys=NetBSD&op_sys=OpenBSD&op_sys=Solaris&op_sys=other&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap | 4930 reports (6.8%) have an OS other than the default ""All""]]. Same reasoning as Platform/Hardware. 
+
+>  * Severity
+
+Nothing to say, I agree it should be always specified. It was a relevant field and we are getting rid of it.
+
+> 2) We have 3 free-form text fields which can be entirely empty:
+
+OK. Since I had the calculator at hand, and just to have an idea about the impact...
+
+>  * URL
+
+18% have something
+
+>  * Whiteboard
+
+3.1% have something
+
+>  * See Also
+
+7.6% have something",1414622233,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",Concur with @RobLa-WMF.,1414620033,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#16896, @Dzahn wrote:
+> a key without a value is not the same as a key that doesn't exist
+
+Technically, correct.  Practically, *shrug*.  Look at this:
+> URL: none
+> Version: unspecified
+> Severity: normal
+> Whiteboard: none
+> Hardware/OS: unknown/unknown
+> See Also: none
+
+Sure, the keys might exist, but it's academic.  I would go so far as to say that the default values (even ""Severity""==""normal"") should just be dropped, since chances are, no human ever cared enough about it to change it.  It's complete clutter, and in the case that someone really cares, the values can be inferred by their absence.
+",1414617802,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",a key without a value is not the same as a key that doesn't exist,1414616933,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","We are discussing two different types of Bugzilla fields which will be dropped as ""text only"" in the initial description of a Phab ticket imported from Bugzilla (as listed [[ https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Bugzilla_data_migrated | here ]]):
+
+1) We have 4 dropdown fields with pre-defined values. By nature these fields must have one selected pre-defined value set: 
+ * Version
+ * Platform/Hardware
+ * OS
+ * Severity
+2) We have 3 free-form text fields which can be entirely empty:
+ * URL
+ * Whiteboard
+ * See Also
+
+As a compromise between ""correct and complete conversion of Bugzilla data"" vs. ""readability of initial descriptions"" (I know my wording is oversimplifying): 
+Can we agree on 
+1) keeping dropdown fields with pre-defined values (as ""Version: unspecified"" or ""OS: All"" in Bugzilla could be considered information to transfer/preserve)
+2) dropping completely empty free-form text fields from being listed in the initial description of a Phab task (as an empty Whiteboard or See Also field  in Bugzilla could be considered no information to transfer/preserve)
+?",1414616541,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",I agree with James.  Let's just not print the unused fields.,1414465151,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#14606, @chasemp wrote:
+> In regards to the principle of progressive disclosure, this not a phabricator or migration issue.  
+> 
+> https://bugzilla.wikimedia.org/show_bug.cgi?id=68559 looks like this:
+> 
+> {F420}
+> 
+> phabricator looks like
+> 
+> {F422}
+> 
+> 
+> Bugzilla chooses to display fields that have no set value, I assume because an unset field is not the same thing as //no data//.  The current approach is the least surprise approach as it most closely preserves the set of data, set and unset, in the original bug report.  Not liking it is fine, not wanting it shown on issues people are actively working on where the value of this data can be examined is fine.  It can be removed from any description, but the default migrated description would be missing valuable context without it.
+
+I agree that Bugzilla is also crap at this. :-) However, we can and should do better.",1414426713,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",Just for the records I don't have a strong opinion here and don't see an issue with 'empty' values being exposed (or not) in Phab's initial comment...,1414426597,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","In regards to the principle of progressive disclosure, this not a phabricator or migration issue.  
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=68559 looks like this:
+
+{F420}
+
+phabricator looks like
+
+{F422}
+
+
+Bugzilla chooses to display fields that have no set value, I assume because an unset field is not the same thing as //no data//.  The current approach is the least surprise approach as it most closely preserves the set of data, set and unset, in the original bug report.  Not liking it is fine, not wanting it shown on issues people are actively working on where the value of this data can be examined is fine.  It can be removed from any description, but the default migrated description would be missing valuable context without it.
+",1414177375,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#14544, @Qgil wrote:
+> One possibility could be: based on the proof of concept that bugzillapreview is, we trust the script, and we will instruct it not to print the unnecessary fields.
+
+So far I've seen no issues at all in the import in terms of missing content, so this seems sensible.",1414170927,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","One possibility could be: based on the proof of concept that bugzillapreview is, we trust the script, and we will instruct it not to print the unnecessary fields.",1414169587,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",">>! In T694#12394, @chasemp wrote:
+> We looked at this and decided it is more confusing to have different fields per ticket as it begs the question did this just fail in migration or is it truly not set?  Since descriptions can be cleaned up easily anywhere people do not like this in regards to an active task I am going to mark this as declined.
+
+Although I can understand that decision in the context of the migration, I think it's a huge mistake. This violates the principle of progressive disclosure, and so increases the confusion for non-expert and new members when they're reading each task imported from a Bugzilla bug — tasks which will be around for years to come. Instead, they will all need to be manually updated to remove this cruft. This doesn't feel very respectful of people's time.",1414166587,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data","Reopening this task only to make sure that people see it before creating a duplicate.
+
+By the way, even if I reported this task, I fully agree with the decision. Makes sense.",1414165839,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Print URL, Version, etc only when they contain data",We looked at this and decided it is more confusing to have different fields per ticket as it begs the question did this just fail in migration or is it truly not set?  Since descriptions can be cleaned up easily anywhere people do not like this in regards to an active task I am going to mark this as declined.,1413842621,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-zmu5pfwidjokjny4bfvu,task_subcomment,NA
+"Create use cases for two test cluster (""Beta Cluster"" and the yet-to-be-created and yet-to-be-named cluster)","
+Over the past two years, a growing number of teams have come to rely on having unreleased software available for use in the beta labs cluster shared test environment.  The ways that teams use beta labs has become more sophisticated, more diverse, and more important.  Disruption of service or unexpected system behavior on beta labs is therefore quite expensive across all of WMF and the development community. 
+
+At the same time, we need a shared test environment where we can test big risky system-wide software changes in a realistic test environment.
+
+A little history:
+
+Two years ago beta labs was a hodgepodge of symlinks, old versions of core and some extensions, and not much else.  There were no policies at all governing its use. Over time we made it so that beta always ran the latest version of the master branch of code. As beta became more valuable, we instituted one policy there: the only code allowed on beta labs was for extensions and features that already existed in the production cluster. Beta labs has never been a ""wild west"" environment, we have always controlled closely what software runs there. My vision was that beta labs would become the system of record for testing WMF software, and this sort of control is required for beta labs to be such a system.
+
+But as our software matured, it became more feasible to implement large-scale system-wide changes. Beta labs was the only reasonable environment in which to test such large-scale changes.  So we changed the policy: we would allow non-production software on beta labs only if that software had a scheduled release to the production environment. Our first such project in beta labs was CirrusSearch, the next was the Flow extension, then HHVM after that.  Besides these, we have also had some experiments with existing beta labs infrastructure like changing the Varnish cache and changing the database master-slave relationship. 
+
+Every one of these system-wide changes on beta labs has caused significant disruption, down time, and problems for automated testing. 
+
+But that was okay at the time.  Beta labs has always been primarily a target for automated browser tests, and very few teams used it in any meaningful way early in its history. 
+
+But that situation has changed dramatically over the last year or so.  As we discovered when HHVM testing brought down all of beta labs for extended periods of time, almost all of WMF relies on beta labs in one way or another to do their work, from testing bleeding-edge software changes, to public demonstrations of new features, to community engagement.
+
+So we need test environments to serve the parties addressed by both of our previous beta labs policies.  We need to support the latest unreleased changes to software that already exists in production; but we also need a realistic test environment for *unreleased* software with the potential to disrupt the entire cluster.
+
+So I propose two beta-labs-like test environments.  These test environments will not differ in the software features they offer, nor in their nominal response to users, but only in the policies governing their use. 
+
+Both environments would: 
+
+* be updated automatically with the master branch of core and extensions
+* have their databases updated automatically as they are today
+* be the target of automated browser test builds
+* be available to the public as beta labs is today
+* serve as the system of record for software testing and software changes
+
+Conservative beta labs would follow our original maintenance policy: no software or systems in place other than those already released to production.  This would very likely be the existing beta labs cluster, so as to disrupt the teams using it already as little as possible.   The aim of this system would be to supply as reliable a user experience as possible given that the system will be running the master branch of all production code and nothing other than production code. 
+
+Liberal beta labs would follow our amended maintenance policy: software with a projected release to production would be in use here.  If it is not in production already, liberal beta labs would be the place to make it work.  Liberal beta labs might host major changes to cross-cutting systems such as
+
+* Search (affects Core, MobileFrontend, VisualEditor, etc.)
+* System optimizations (HHVM, new caching schemes, major db changes, etc.)
+* New extensions (especially those requiring untested db updates)
+* Any system-wide config change needing testing
+* Potentially, this system could host experiments not destined for a production release, but that exist for research purposes
+
+Testing HHVM proved that we are stretching the capacity and capability of beta labs beyond what we can reliably support.  Having a conservative beta labs test environment for features bound for production would serve our existing users, while having a liberal beta labs test environment where we can manipulate the entire system would serve our future users.
+
+
+",1409872045,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-oh6abcadhuy4bmoaictt,task_description,resolved
+"Create use cases for two test cluster (""Beta Cluster"" and the yet-to-be-created and yet-to-be-named cluster)",//importing issue status//,1410486531,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-oh6abcadhuy4bmoaictt,task_subcomment,NA
+"Create use cases for two test cluster (""Beta Cluster"" and the yet-to-be-created and yet-to-be-named cluster)","**greg** wrote on `2014-09-07 21:15:42 (UTC)`
+
+Copy/pasted to https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Second_Beta_Cluster for historical purposes.",1410486531,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-oh6abcadhuy4bmoaictt,task_subcomment,NA
+"Create use cases for two test cluster (""Beta Cluster"" and the yet-to-be-created and yet-to-be-named cluster)","**cmcmahon** wrote on `2014-09-05 21:38:54 (UTC)`
+
+I think this essay answers the task",1410486531,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-oh6abcadhuy4bmoaictt,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Proposed statuses:**
+
+| **Status name in Phab** | **Explanation** | **Resembling in Bugzilla** |
+| open | Default state | {UNCONFIRMED, NEW, ASSIGNED, REOPENED, PATCH_TO_REVIEW*} {} |
+| stalled | Stalled |  |
+| resolved | A change that fixes the task has been merged. | {RESOLVED, VERIFIED, CLOSED} FIXED |
+| invalid | This is not a task, or it is out of scope in Wikimedia Phabricator. | {RESOLVED, VERIFIED, CLOSED} INVALID |
+| declined | Bad idea, can not be reproduced, missing information has not been provided, or an acceptable alternative exists. | {RESOLVED, VERIFIED, CLOSED} {WONTFIX, LATER, WORKSFORME} |
+| //(marked as duplicate)// | | RESOLVED DUPLICATE |
+
+*For PATCH_TO_REVIEW, create a project and add it to Phab tasks. See T169.
+
+---
+---
+For historical reasons: Initial task description:
+
+By default, Phabricator offers OPEN, RESOLVED, WONTFIX, INVALID as statuses (and we can resolve tasks as duplicates).
+Custom statuses can be added via /config/edit/maniphest.statuses/
+
+Subtasks I see here:
+ * Bugzilla also offers WORKSFORME (CANNOT_REPRODUCE). DO we want this?
+ * NEEDINFO/NEEDS_MORE_INFO: marking an item as not actionable is a recurring request for Bugzilla, see https://bugzilla.wikimedia.org/show_bug.cgi?id=36064
+ * INVALID sounds harsh so we might want to bikeshed on a better wording.",1401463475,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_description,resolved
+Decide which task statuses we want to have in Maniphest,"Stalled, then. Moving on. Thanks!",1415632137,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"FWIW I would just go w/ stalled.  We already use it in one of the originating import system cases, and if it is truly an issue we can revisit at a later date.",1415631087,PHID-USER-3neel27i7dyu62jbbx2l,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"""Paused"" is an alternative, sometimes appropriate, other times it's not: ""Paused"" feels more voluntarily put in waiting than ""Stalled"" does. But sometimes that's exactly what we want/mean.
+
+I don't particularly care that much, and I don't want to get into bikeshedding over this. All of this is better than the more specific ""Needs info"" IMHO.",1415628312,PHID-USER-hovi6c77qompv5qd7gtz,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"The (small) problem I see with ""Stalled"" is that it is a bit of an idiom that might confuse our international and/or non-tech userbase.
+
+A synonym of Stalled that would rhyme with Resolved, and Declined is ""Paused"". The more I see it, the better I prefer it over ""Waiting"". What do you think?
+
+Whatever it is, will be decided latest by our meeting on Monday.  :)",1415575943,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"In my brain ""Needs info"" vaguely translates to ""blocked on somebody or something"" which is close enough to ""Stalled"" or ""Waiting"". Both works for me.
+
+We need to document that well, otherwise people might come up with interpretations like ""I'm waiting for a developer to take a look at this and fix this!!!"" or such. ;)",1415381073,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"I agree that ""Needs Info"" can be renamed to something more generic. Also, we put a lot of effort trying to reduce the number of options for Status and other selectors compared to Bugzilla, and this is why you can feel my resistance to add a new status. Nothing against RT practices personally.
+
+So what about ""Waiting"". This would mark tasks as ""Open, Waiting"", showing clearly that even if the task is assigned and has ""Unbreak Now!"" priority (hypothetical extreme case"", the owner explicitly cannot do anything but wait for another event. Then we can define the reason for the wait via tags or workboard columns, tbd and in the ways that works better for every team.
+
+@aklapper, does this work for you?",1415379886,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"Hmm, maybe, we can experiment with it.
+
+I do think that ""Needs Info"" is a rather specific case of a status for a ticket which can't progress, wouldn't it be better to use something more generic (like stalled)?",1415378433,PHID-USER-hovi6c77qompv5qd7gtz,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"Have you considered using column workboards for these specific conditions? Then the label of the column appears in the description of the task. Like here, above, you can see ""(Need Discussion)"" now, you would have al the flexibility to decide other conditions your tasks are stuck on i.e. ""Stalled"".
+
+Also for what is worth, I have been thinking about proposing tags like ""2015-03"" to denote tasks that need to be acted upon at a certain point in the future, but not now.",1415378213,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"In RT we actually use ""Stalled"" sometimes, with meaning which is quite different from ""Needs Info"". Needs Info implies we're waiting on someone to provide info to be able to make progress with a bug.
+
+""Stalled"" for us can mean things like:
+
+- Waiting on a 3rd party to do/implement/deliver something (vendor or whatever)
+It's not really ""needs info"", it's also not blocked on a task we can resolve ourselves, but we can't make progress on this task either
+
+or
+- We're going to do this, we keep track of it, but the right time (or some other precondition) for it hasn't come yet
+For example, ""decommission server X at date Y."" Of course, in some such cases, being able to list the precondition (such as a defer date) in ticket metadata would be even better.
+
+Since ""Stalled"" is more generic than ""Info"" and can be used for a wider variety of things, we'd still like to have this status available for our projects...
+
+
+
+
+
+",1415376893,PHID-USER-hovi6c77qompv5qd7gtz,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,This one is implemented as well. Sorry for the noise.,1410984349,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,//importing issue status//,1410485871,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-08-18 21:20:42 (UTC)`
+
+Re last comment: We renamed some statuses in this fab.wmflabs.org instance to ""implement""/reflect the decisions made in T359, and we realized that when a status (in this case the previously existing WONTFIX) goes away, Phab resets a task's status to unknown. Next time we know better, and I fixed that manually now to not run into inconsistencies for T336.",1410485871,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-08-18 21:16:06 (UTC)`
+
+Currently we can see messages talking about tasks moving `from ""Unknown Status"" to ""Declined""`. See for instance at the end of T432. What is this ""Unknown Status""? Looks like it's ""Open"", although maybe there is another factor in play.",1410485871,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-08-15 11:45:56 (UTC)`
+
+Great! 
+
+Task completed? I volunteer documenting this in https://www.mediawiki.org/wiki/Phabricator/Help",1410485870,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-08-14 19:57:33 (UTC)`
+
+tinker...tinker...tinker...I got it to work I think.
+
+I updated the values on this install to match what i have for prod.  this install is kinda of a pain since everthing is a one-off and I can't just use the same config.
+
+anyhoo -- check it out.",1410485870,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-08-14 12:00:39 (UTC)`
+
+Ooops, sorry for resolving accidentally.",1410485870,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-08-14 12:00:11 (UTC)`
+
+Maybe this refers to the value, being different to the string shown in the UI? This instance is showing ""Resolved"", ""Wontfix"", ""Invalid"" in upper case.
+
+If this is the case, we could have ""needsinfo"" as value and ""Needs Info"" as UI string.",1410485869,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-08-13 20:13:01 (UTC)`
+
+trying just ""stalled"" as a needs info alternative",1410485869,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-08-13 20:12:41 (UTC)`
+
+ran into a problem here:
+
+needs_info is a not a valid possible status
+
+%%%[Core Exception/Exception] Key ""needs_info"" is not a valid status constant. Status constants must be 1-12 characters long and contain only lowercase letters (a-z) and digits (0-9). For example, ""open"" or ""closed"" are reasonable choices.%%%",1410485869,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Nemo_bis** wrote on `2014-07-25 19:01:48 (UTC)`
+
+>>! In T359#73, @aklapper wrote:
+> I'd STILL appreciate if no wrong data was entered. ;) Fixed.
+
+After http://fab.wmflabs.org/transactions/detail/PHID-XACT-TASK-xukns75c3p24el7/ it's ok; I have merely copied the official descriptions from mediawiki.org, UNCONFIRMED and REOPENED are practically equivalent now so they should be in the same group.",1410485868,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-24 12:31:01 (UTC)`
+
+I assume good faith when editing the description, but I'd STILL appreciate if no wrong data was entered. ;) Fixed.",1410485868,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-24 11:32:59 (UTC)`
+
+James, I think the statuses and their descriptions listed at the top of this task satisfy your concerns. I agree that we cannot just delete all what is marked Invalid. In fact, Phabricator doesn't bring any need to change the current policy for deleting reports in Bugzilla.
+
+>>! In T359#63, @jdforrester wrote:
+> * ""truly invalid"" – spam reports
+
+These will indeed be unpublished/deleted as soon as they are detected. Maybe we can have a ""Spam"" project in order to allow users to report spam. Then the right team with the right permissions can unpublish them.
+
+> * ""misplaced"" – things filed in Bugzilla which aren't dealt with in Bugzilla
+> * ""overtaken by changes"" – things asking for changes that made sense at the time but don't now
+
+""This is not a task, or it is out of scope in Wikimedia Phabricator."" Clearly ""Invalid"". Will stay.
+
+> * ""mistaken"" – things which are this way by design (more often labelled WONTFIX).
+
+""Bad idea, cannot be reproduced, missing information has not been provided, or an acceptable alternative exists."" Clearly Declined. Will stay.
+",1410485868,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-24 11:17:36 (UTC)`
+
+True! I was looking at the general advanced search instead of Maniphests' advanced search. Problem solved, then.",1410485867,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-24 11:14:45 (UTC)`
+
+>>! In T359#67, @Nemo_bis wrote:
+>> (marked as duplicate)
+> 
+> Can this status be searched?
+
+See ""Status"" section on http://fab.wmflabs.org/maniphest/query/advanced/ - there is an explicit ""Duplicate"" checkbox.",1410485867,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-24 10:37:59 (UTC)`
+
+The status that appears at the top of merged tasks is ""Closed, Duplicate"", so it should be as searchable (or not, see below) as the rest of statuses.
+
+As far as I can see, users can only search tasks by status Open/Closed. At least I can't see a checkbox for the different Closed statuses at the Advanced Search. Querying ""Merged into"" will get you pretty close ([[ https://secure.phabricator.com/search/query/HY2OHkK_zrvW/ | I hope this URL works ]]).
+",1410485867,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Nemo_bis** wrote on `2014-07-24 01:02:24 (UTC)`
+
+> (marked as duplicate)
+
+Can this status be searched?",1410485866,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**jdforrester** wrote on `2014-07-23 16:14:19 (UTC)`
+
+>>! In T359#45, @qgil wrote:
+> |invalid| no historical value will be purged eventually (spam, etc)
+
+This is a pretty big change in semantics – right now, INVALID and WONTFIX are used to distinguish between different shades of declines. I'd roughly categorise them as:
+
+* ""truly invalid"" – spam reports
+* ""misplaced"" – things filed in Bugzilla which aren't dealt with in Bugzilla
+* ""overtaken by changes"" – things asking for changes that made sense at the time but don't now
+* ""mistaken"" – things which are this way by design (more often labelled WONTFIX).
+
+We'll need to make sure people are careful not to use ""invalid"" the way they've been using INVALID. Maybe purging isn't the best idea",1410485866,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-17 23:13:16 (UTC)`
+
+>>! In T359#58, @scfc wrote:
+> A recurring problem in Bugzilla with PATCH_TO_REVIEW as a status is that, as it is used as a flag, when a patch is merged/abandoned, one has to go through all the comments to see if this was the only patch to have triggered setting the flag in the first place (and if it previously was UNCONFIRMED, NEW or ASSIGNED).  A Phabricator replacement should take into account that there is a n:m relationship between bugs and patches and ensure that the UI provides a clear picture of the existence of open patches.
+
+In phase 1 (ie: after we've only transitioned Bugzilla to Phab, not Gerrit), that's out of scope.
+
+For phase 2 (ie: after we've also transitioned Gerrit), that will be implicit in that fact that we use Phabricator :)
+
+You can see a good example of what that looks like on the upstream Phabricator instance where a Task has many Diffs associated with it, and you can quickly see how many are merged/open: https://secure.phabricator.com/T2772",1410485866,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**scfc** wrote on `2014-07-17 22:55:59 (UTC)`
+
+A recurring problem in Bugzilla with PATCH_TO_REVIEW as a status is that, as it is used as a flag, when a patch is merged/abandoned, one has to go through all the comments to see if this was the only patch to have triggered setting the flag in the first place (and if it previously was UNCONFIRMED, NEW or ASSIGNED).  A Phabricator replacement should take into account that there is a n:m relationship between bugs and patches and ensure that the UI provides a clear picture of the existence of open patches.",1410485865,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-17 17:01:14 (UTC)`
+
+@greg...I will forgo my speech on projects and organization :D
+
+But really it's that all projects function as tags at the basic level.  So we make a patch_to_review project and add and remove as appropriate for filtering.",1410485865,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-17 16:31:00 (UTC)`
+
+>>! In T359#55, @Rush wrote:
+> @greg, would it work for you if there was an automated tag for issues in this state for now instead?
+> 
+> so you could go do phab.wm.com/tag/patch_to_review and see all tasks in this status.
+> 
+> That way we don't end up with an unused ticket status in the future, and since it's automated we can ensure consistency.
+
+For me, yeah, probably. How are tags added/removed? I can't seem to find it in ""Edit task""",1410485864,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-17 14:48:37 (UTC)`
+
+@greg, would it work for you if there was an automated tag for issues in this state for now instead?
+
+so you could go do phab.wm.com/tag/patch_to_review and see all tasks in this status.
+
+That way we don't end up with an unused ticket status in the future, and since it's automated we can ensure consistency.",1410485864,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-16 23:33:21 (UTC)`
+
+>>! In T359#52, @qgil wrote:
+> Bugzilla has so many ASSIGNED reports where it is not true that ""someone is actively working on this, check the assignee field for who"".
+
+fwiw: I actively use that as a means to track work my team is doing. Some other projects/components don't have people tending the garden actively.",1410485864,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-16 18:53:44 (UTC)`
+
+so seems like we can mimic this gerrit bot that notifies bugzilla with phab, but without a PATCH_TO_REVIEW  status that step would be replaced by another comment linking to the merged patch?",1410485863,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-16 18:46:35 (UTC)`
+
+Bugzilla has so many ASSIGNED reports where it is not true that ""someone is actively working on this, check the assignee field for who"".
+
+I'd rather have us rely on Open + Assigned To + workboard OR the assignee commenting about their intentions (so nobody else steps on their toes).",1410485863,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-16 17:24:13 (UTC)`
+
+>>! In T359#50, @aklapper wrote:
+>> ""someone is actively working on this, check the assignee field for who""
+> 
+> That's what workboards are for, IMHO?
+
+If the task is in one and only one project, and that project uses workboards (not all will), sure. But if there's any deviation from that, no, not really.",1410485863,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-16 17:13:05 (UTC)`
+
+> The PATCH_TO_REVIEW status in BZ is a hack, I believe,
+
+Yes, it's done by https://gerrit-review.googlesource.com/#/admin/projects/plugins/its-bugzilla set up by qchris and setting up a status looked like the most visible way (in additional to the comment created by that plugin). See http://lists.wikimedia.org/pipermail/wikitech-l/2012-December/065046.html and https://gerrit.wikimedia.org/r/#/c/69843/ for historical data.
+
+> ""someone is actively working on this, check the assignee field for who""
+
+That's what workboards are for, IMHO?",1410485862,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-07-16 16:53:22 (UTC)`
+
+>>! In T359#48, @Rush wrote:
+> @aklapper can you help me understand more about what you mean by gerrit patch notifications?
+> 
+> I know there is some interaction between bugzilla and gerrit, but haven't used it myself.  
+
+Basically, since there is no tight integration between Gerrit and BZ, all we have is a bot that comments on BZ bugs when there's a new related patch, eg https://bugzilla.wikimedia.org/show_bug.cgi?id=67270#c26 and when said patch is merged eg https://bugzilla.wikimedia.org/show_bug.cgi?id=67270#c27 (and similar message for abandoned). When it comments that there's a related patch, it also changes the STATUS to PATCH_TO_REVIEW.
+
+You get the fancy behavior by including ""Bug: 12345"" at the bottom of the change commit message (right before the change-id gerrit needs at the very bottom).
+
+I personally think there should be an ""in-progress"" or whatever status as well, that says ""someone is actively working on this, check the assignee field for who"". The Gerrit bot could set that status when it has a related patch. (We basically use ""ASSIGNED"" in BZ for that now.)
+
+The PATCH_TO_REVIEW status in BZ is a hack, I believe, because BZ doesn't have a nice way of querying bugs that have linked Gerrit commits associated with a bug. ie: the issue that will be solved when we also transition code review to Phab from Gerrit.",1410485862,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-16 15:25:24 (UTC)`
+
+@aklapper can you help me understand more about what you mean by gerrit patch notifications?
+
+I know there is some interaction between bugzilla and gerrit, but haven't used it myself.  
+",1410485862,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-16 15:01:29 (UTC)`
+
+Since those Gerrit patch notifications are created by a bot, here we could apply the idea of Open + project ""Patches For Review"".
+
+The same bot could remove that project if the patch is merged/abandoned.",1410485861,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-16 13:28:23 (UTC)`
+
+Assuming that ""Declined"" covers both ""sorry but we really could not reproduce"" and ""we are against fixing it"", this is probably the smallest set of statuses one could come up with. Thank you Quim. :)
+
+One aspect left: **Gerrit patch notifications** in Phab in T277 (as long as we have not killed Gerrit in T42): I have no idea yet if or how we want to implement the behavior of the ""Patch to review"" status in Bugzilla. Another status, temporarily until we've fixed T42? (as I have a hard time to imagine notifications triggering changes to a column in a project's workboard, as the naming scheme of columns in per project)",1410485861,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-16 10:38:30 (UTC)`
+
+Ok, we can forget about tag-projects for Day one (and therefore the migration). They can always be added to the process at a later stage if somebody misses them or has a better idea of what to do with them.
+
+I agree that Unreproducible is a variant of Needs Info.
+
+>>! In T359#43, @Rush wrote:
+|open| default state
+|needs_info| stalled
+|resolved| closed
+|invalid| no historical value will be purged eventually (spam, etc)
+|declined|we have decided not too -- even though we could
+
+I agree with these statuses; descriptions to be fine tuned.",1410485861,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-15 20:01:46 (UTC)`
+
+andre as usual you come up with good stuff.
+
+@qgil...I really liked your thoughts, over the evening yesterday tho I became less convinced people would actually do it :)  I think it's a really cool idea within domains for people to utilize, ops could do this for their own stuff, andre could do it too.  Anyone who can ensure their own consistency it would work out for, but I don't feel like the 
+workflow of a task lends itself to the status+project combo being a good default mindset sort for the big 3 or 4 or even 5 cases.  
+
+I think the real difference tho is I don't view invalid as a subset of declined.  I do look at declined tasks as having value in a historical sense, and invalid tasks are really waiting to be purged out when they become cumbersome enough.
+
+I don't see a difference between unreproducible and declined.  Do we not decline as unreproducible?  But in general, if it's a broad enough brush to be it's own bucket.  Fine with me.
+
+I also think, unreproducible could be a form of needs_info.  that probably makes the most sense to me.
+
+Needs triage is a priority right?  Not a status.
+
+needs_info seems kind of odd, why not the suggested [incomplete]
+
+That means the status's would be something like:
+
+|open| default state
+|needs_info| stalled
+|resolved| closed
+|invalid| no historical value will be purged eventually (spam, etc)
+|declined|we have decided not too -- even though we could
+
+-> 
+
+|unreproducible| needs more info to reproduce?  should be merged with needs_info?
+
+
+invalid and declined here are also taking the place of reject which exists in rt.  we do get spam there as well.  
+
+Also, really liking andre's 'resembling' identities for the categories.",1410485860,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-15 17:09:46 (UTC)`
+
+**Generally speaking:** It's all about ""keep it simple and stupid"" vs ""I want to categorize everything"" and finding a good compromise. Before commenting, everybody should question themselves whether they do care a lot about expressing a reason //via task status// and if they really query for tickets and differentiate on that status, or if they can also survive having the reason in a project workboard column or comment only which is harder to search for.
+
+Regarding the proposal to **set projects in addition to the ""Declined"" status**, I've in the meantime gotten afraid that people won't do that. I cannot exactly prove it and the quote refers to fixed issues, but: ""Of course, the developer could change the issue category after resolution---but this happens rarely. In many cases there exists no real motivation to change the issue category once the cause for a problem is found and fixed."" from http://www.st.cs.uni-saarland.de/softevo/bugclassify/paper/icse2013-bugclassify.pdf page 396.
+
+**A status called ""Invalid"":** There are opinions in Mozilla ( http://eaves.ca/2011/07/27/lessons-for-open-source-communities-an-example-for-bug-tracking-more-efficient/ and https://bugzilla.mozilla.org/show_bug.cgi?id=592533 ) that average users who incorrectly filed a support request (configuration, on-wiki gadget issues) as a task/bug report and who are not used to dev workflows/terms, that ""invalid"" can feel derogative, but I really cannot come up with a better term after looking at other issue trackers and their terms, so I naively call it ""Invalid here"" instead of ""Invalid"".
+
+I am probably less afraid of **cluttering the status field** if people //really// want to differentiate reasons for closing. The ~dozen of Bugzillas I sometimes interact with have 5-9 statuses and 6-13 resolutions. Combining that in one field in Phab, I think we're not too bad if we ended up with 7 or 8 task statuses.
+
+**Summary:**
+* Needs Triage
+* Open
+* Needs Info
+* Resolved
+* Invalid Here (resembling ""Invalid"", ""Nothing for a Phab task"", ""Spam"", ""Support request"", ""On-Wiki issue"", ""Upstream it"", ""Works as intended"" etc.)
+* Declined (resembling ""Wontfix"", ""Out of scope"", ""Actively against fixing this"", ""Overcome by events"" etc.)
+* Unreproducible (resembling ""Works for me"", ""Insufficient data"", ""Feedback Timeout"", ""Your computer got hacked by an interwebs virus that displays ads on Wikipedia"" etc.)
+and
+* ""Verified"" as an optional workboard column per $project if $project wants it.",1410485860,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-14 17:01:42 (UTC)`
+
+>>! In T359#40, @Rush wrote:
+> are you suggesting a literal ""out of scope"" project that tasks are added to for this? or that there is a ticket state for which the option would be ""declined - out of project scope'.
+
+The former, but using the project just as a tag. Those tasks will be declined. We can forget about them. No team, sprint, dashboard, etc, will be assigned to those. You can always make elaborate queries if you need them: which tasks were ""Declined"" (Status) as ""Out Of Scope"" (tag-project) in ""Visual Editor"" (project-project)?
+
+> Work-for-me is a terrible state for a ticket to be in as it doesn't mean anything.
+
+Following the proposal above, the migration script should convert Bugzilla's WORKSFORME reports in Declined + project ""Non Reproducible"" tasks. In Bugzilla WORKSFORME sometimes is used as ""what you see as a bug is correct behavior in my eyes"", which is different than ""Non Reproducible"". I would still apply the same rule and leave the old bugs Rest In Peace.
+
+> resolved fixed is less good than resolved closed
+
+For the sake of the migration skip, I would treat both as equal.
+
+> The only thing I feel is a strong point is that invalid is a distinct state for a ticket to be in outside of normal resolution, and it is important to distinguish between this isn't possible and we are not doing this
+
+Declined + project ""Invalid"" for the migration? No matter what, they are still declined tasks. I just want to avoid if possible to have an option in the Status that will not be used in the 92% of cases (if we have to trust Bugzilla stats). Besides, if we dig deeper in the current INVALID reports we will find different reasons to reach to that resolution, including out of scope, spam, poorly written, and more. 
+
+Having one ""Declined"" resolution and specific tag projects allow us to be (optionally) more precise without cluttering the Status field.",1410485859,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-14 16:00:34 (UTC)`
+
+> 
+> Bugzilla-Phabricator mapping:
+> 
+> | Bugzilla | Phabricator |
+> | ----- | ----- |
+> | UNCONFIRMED (default) | Open + Needs Triage (default) |
+> | NEW | Open |
+> | ASSIGNED | Open + Assigned To |
+> | PATCH_TO_REVIEW | Open + Code Revisions |
+> | NEED_INFO | Needs Info |
+> | RESOLVED FIXED | Resolved |
+> | RESOLVED INVALID | Declined |
+> | RESOLVED WONTFIX | Declined + project ""Out Of Scope"" |
+> | RESOLVED WORKSFORME | Declined + project ""Non Reproducible"" |
+> | RESOLVED DUPLICATE | (merged) |
+
+I think this is a stupid question on my part, but are you suggesting a literal ""out of scope"" project that tasks are added to for this? or that there is a ticket state for which the option would be ""declined - out of project scope'.  The first I don't think will work across the gamut just because it's too big of a bucket to be meaningful across all the projects / teams / workflows, etc,.  The second seems like a very specific category of declined? 
+
+Declined does seems more diplomatic than won't fix :)
+
+Work-for-me is a terrible state for a ticket to be in as it doesn't mean anything.  It just means two people had different experiences.  It doesn't mean something needs more work, and it doesn't mean something _doesn't_ need more work.  It's not a task or issue state so much as it could be the genesis of an open/closed state, yet is neither.  It doesn't seem meaningful, and could literally be a less valuable version of NEEDS_INFO.
+
+INVALID = this cannot be done.
+
+And, dear god please forgive me for even bikeshedding to this degree, but resolved fixed is less good than resolved closed (phab default).  Closed is wide enough to include hey we talked about it and decided it's a no, but good question.  Fixed implies changes...maybe only to me...whereas an issue can definitely be moved out of an open state without anything being modified other than a requesters state of mind :)
+
+I think in some cases for resolved subtypes we are trying to cram a lot of information into this basic ticket state that doesn't necessarily fit there.  We could conceivably make a separate ticket field to indicate the resolved reasoning as in.
+
+Resolved....
+
+RATIONALE...wonfix/invalid/fixed/foo/bar/whatever/
+
+The only thing I feel is a strong point is that invalid is a distinct state for a ticket to be in outside of normal resolution, and it is important to distinguish between this isn't possible and we are not doing this",1410485859,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-14 15:13:43 (UTC)`
+
+@Rush was faster than me. I was also about to say that workboards offer all the degrees you need between Open and Resolved.",1410485859,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**Rush** wrote on `2014-07-14 15:03:38 (UTC)`
+
+could verified be a workboard status rather than a full on issue status?  
+
+some of the team specific workflow can be handled at the alternative abstraction layer I think",1410485858,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-14 14:26:09 (UTC)`
+
+Hmm, same VERIFIED question goes to the VE team, actually (@jdforrester).
+
+<Lydia_WMDE> we do use it for basically acceptance confirmation. ie ideally dev sets it to resolved fixed and then i go and set it to verified. doesn't entirely work atm though
+<andre> the question is probably ""what would you lose if it wasn't available anymore"". Plus VE and Wikidata seem to be the only teams using VERIFIED.
+<Lydia_WMDE> we would lose a second stage of review/confirmation.
+<Lydia_WMDE> so i can live without it but i think we should have it
+<andre> does anybody ever query for VERIFIED specifically (or excluding that from RESOLVED tickets)? What if this was just added as a comment instead?
+<Lydia_WMDE> i query for all resolved fixed ones to go through them and verify
+<andre> so if you could query for resolved tickets and exclude those which have a ""has been verified"" comment, would that also work? :D
+<Lydia_WMDE> doesn't feel very nice/clean
+<andre__> I'm wondering if adding a ""Wikidata verified"" (or so) project instead might work. Need to think about it.",1410485858,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-14 14:16:53 (UTC)`
+
+VERIFIED status in Bugzilla is being used by the Wikidata team - wondering how important it is to them in their development workflow, and if they could live without it for the sake of keeping it simple and stupid. I've pinged Lydia on IRC as I couldn't find an account here.",1410485858,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-14 12:43:56 (UTC)`
+
+@parent5446, if I'm not mistaken, in Bugzilla reports are by default UNCONFIRMED until some action makes them NEW. The equivalent default status in Phabricator is Open + Needs Triage. ""Needs Info"" is a status that must be set manually, therefore it cannot be the default for all new tasks.
+
+@aklapper, adding projects to declined tasks should be optional, and done when such projects help the task and the reporter somehow. Also, adding one tag-project can save you the work of typing a manual comment.
+
+If ""should be fixed in upstream"" means ""we won't work on it"", then it can be Declined + project Upstream, and additionally we could even add a project for the specific upstream e.g. ""Elasticsearch"" if that helps us tracking tasks. We can also have tasks that must be fixed upstream, but our maintainers are planning to work on them, as it is the case already now here with certain Phabricator tasks.",1410485857,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-07-14 11:30:27 (UTC)`
+
+@qgil: Thanks, this looks really really good indeed (though I wonder a little bit with regard to workflow how tedious it'll be to change task status to Declined plus also add a ""Out Of Scope"" / ""Non reproducible"" project to that task). I guess that ""Out of scope"" would also cover ""should be fixed in upstream"" as it's ""not our bug"".",1410485857,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**parent5446** wrote on `2014-07-11 14:19:18 (UTC)`
+
+@qgil, that looks pretty good. There's just a small error in your mapping table. UNCONFIRMED should map to ""Needs Info"", since, like you mentioned earlier, triage has more to do with the maintainers deciding the priority rather than the bug needing more information.",1410485857,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-07-11 13:44:43 (UTC)`
+
+Revisiting this topic, I think we can use better the possibilities of Phabricator that were limitations in Bugzilla, requiring all these different types of statuses.
+
+What about this:
+
+* Open 
+* Needs Info
+* Resolved 
+* Declined + optional tag project
+
+""Open"" means that a task is actionable. The rest is defined by its current priority and details like having someone assigned to it, or visible activity in the form of mockups, patches...
+
+""Needs Info"" deserves an own status to raise attention. These tasks may be declined (automagically?) if no info is received after some period.
+
+""Resolved"" means that the task is considered completed.
+
+""Declined"" means that the maintainers are removing the task from the plate. Reasons will differ, but the end result is the same: reporters and other contributors must do some homework if they want to reactivate them. Project tags can be used optionally to catalog tasks that might interest someone. Think of projects like ""Non Reproducible"" or ""Out Of Scope"".
+
+Bugzilla-Phabricator mapping:
+
+| Bugzilla | Phabricator |
+| ----- | ----- |
+| UNCONFIRMED (default) | Open + Needs Triage (default) |
+| NEW | Open |
+| ASSIGNED | Open + Assigned To |
+| PATCH_TO_REVIEW | Open + Code Revisions |
+| NEED_INFO | Needs Info |
+| RESOLVED FIXED | Resolved |
+| RESOLVED INVALID | Declined |
+| RESOLVED WONTFIX | Declined + project ""Out Of Scope"" |
+| RESOLVED WORKSFORME | Declined + project ""Non Reproducible"" |
+| RESOLVED DUPLICATE | (merged) |",1410485856,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**parent5446** wrote on `2014-07-10 17:35:20 (UTC)`
+
+>>! In T359#21, @scfc wrote:
+> This doesn't make sense to me.  In Bugzilla, INVALID is used when someone complains that ""expr 2 + 2"" doesn't output 5 (and it shouldn't), WORKSFORME when the complaint is that it doesn't output 4, but for the triager it does, and WONTFIX if someone wants ""expr 2.1 + 1.9"" to work, but the developers consider this outside the scope of expr.
+
+Agreed with this. WONTFIX, WORKSFORME, and INVALID are all three different, distinct resolutions, each representing a different community consensus concerning the bug reported.
+
+Also, keep in mind that in Bugzilla, all of those (as well as FIXED and DUPLICATE) are not separate statuses, but rather all kept under the umbrella of RESOLVED. In reality, Bugzilla only has five statuses: UNCONFIRMED, NEW, ASSIGNED, PATCH_TO_REVIEW, and RESOLVED (we don't really use VERIFIED, so I left it out). With that in mind, ASSIGNED is really unnecessary in both Bugzilla and Phabricator, and PATCH_TO_REVIEW also is not necessary in Phabricator.
+
+That brings us down to just three statuses: UNCONFIRMED, NEW, and RESOLVED. If there was a way to sub-categorize statuses in Phabricator, that would make things a lot simpler. In the end, though, I think it is necessary to keep the various sub-categories of RESOLVED (there names could be changed; I don't care about the naming).",1410485856,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-06-02 20:26:02 (UTC)`
+
+>>! In T359#22, @avive wrote:
+>>>! In T359#8, @greg wrote:
+>> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+> 
+> Workboards kinda-sorta-coulda support this:
+> {F6450}
+
+Interesting.... That's a hack, but yeah, that could do it.",1410485856,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-06-02 20:25:20 (UTC)`
+
+[removing not useful part of this comment]
+
+Bugzilla is still officially canonical, for the record.",1410485855,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**aklapper** wrote on `2014-06-02 18:30:11 (UTC)`
+
+CC'ing those top 10 bug closers listed on http://korma.wmflabs.org/browser/its.html who have an account here:
+
+Are any specific thoughts on task/ticket statuses in Phabricator, based on your experience in Bugzilla?",1410485855,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**avive** wrote on `2014-05-31 20:40:59 (UTC)`
+
+>>! In T359#8, @greg wrote:
+> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+
+Workboards kinda-sorta-coulda support this:
+{F6450}",1410485854,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**scfc** wrote on `2014-05-31 02:25:24 (UTC)`
+
+>>! In T359#16, @qgil wrote:
+> The problem with making ""Needs Info"" equivalent to ""Needs triage"" is that it is difficult to know who to blame. While ""Needs triage"" means that the ball is in the field of the triagers / maintainers, ""Needs Info"" shows that it is he reporter who need to do some homework.
+
+""Need(s) info"" (as a concept) isn't necessarily limited to the reporter.  It can also be used to indicate that input from ops, legal, design, etc. is needed.  In general, it should move a bug from the dashboard of the assignee to that of the designated person.
+
+>>! In T359#12, @qgil wrote:
+> What you are saying is that we can keep the current behavior, just changing the strings:
+
+> * Open --> Open
+> * Resolved --> Resolved
+> * Wontfix --> Not a Bug
+> * Invalid --> Needs Info
+> [...]
+
+This doesn't make sense to me.  In Bugzilla, INVALID is used when someone complains that ""expr 2 + 2"" doesn't output 5 (and it shouldn't), WORKSFORME when the complaint is that it doesn't output 4, but for the triager it does, and WONTFIX if someone wants ""expr 2.1 + 1.9"" to work, but the developers consider this outside the scope of expr.
+
+Also, IMHO in general if Phabricator has a different (default) set of statuses, I would be very hesitant to change them without a very good reason as it will introduce another little unnecessary hurdle for contributors.",1410485854,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**swalling** wrote on `2014-05-30 21:18:28 (UTC)`
+
+Think about the best, most beloved issue trackers currently in use (Trello, for instance). Then compare to Bugzilla, which everyone except random volunteers, Platform, and VisualEditor have pretty much abandoned as their canonical issue tracker. 
+
+Trello and most other good trackers: only two states: archived/resolved or open.
+Bugzilla: too many status, priority, target and other state options to bother counting. 
+
+This should be indicative how you're overcomplicating things. ",1410485854,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**jdforrester** wrote on `2014-05-30 21:02:13 (UTC)`
+
+Steven – Please warn if you're forking the conversation so I don't have to respond in two places! :-)
+
+I agree with Quim and disagree with Steven re. the appropriacy of not having a NEEDSINFO state in terms of user interaction.
+
+I also disagree with Steven re. polluting the ""RESOLVED"" status space with bugs that are not resolved but instead weren't appropriate bugs for whatever reason (like problems with gadgets, configuration mistakes, or issues with a localisation string or whatever else is a problem not tracked in Phabricator).",1410485853,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**swalling** wrote on `2014-05-30 19:31:31 (UTC)`
+
+>The problem with making ""Needs Info"" equivalent to ""Needs triage"" is that it is difficult to know who to blame. While >""Needs triage"" means that the ball is in the field of the triagers / maintainers, ""Needs Info"" shows that it is he reporter >who need to do some homework
+
+Someone needs to be responsible for shepherding a task forward. Adding complexity to the state of tasks doesn't really help. They need to just step up and manage the state of the task. This is why we have maintainers, product managers, bugmeister, and other people in these roles. ",1410485853,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-05-30 19:25:02 (UTC)`
+
+The problem with making ""Needs Info"" equivalent to ""Needs triage"" is that it is difficult to know who to blame. While ""Needs triage"" means that the ball is in the field of the triagers / maintainers, ""Needs Info"" shows that it is he reporter who need to do some homework.",1410485853,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**swalling** wrote on `2014-05-30 19:19:46 (UTC)`
+
+We should strive for absolutely simplicity and as small a number of states as possible. The more choices we provide the more confusing things are for all users. My thoughts, also replicated on the Product list are thus...
+
+> [Updated] proposed set from @jdforrester: 
+>
+>OPEN
+>RESOLVED
+>DECLINED (rather than WONTFIX)
+>NOTABUG (rather than INVALID, also replacing WORKSFORME)
+>NEEDSINFO (consistent with not using ""_""s, INCOMPLETE sounds like it's about the task, not the request)
+
+I don't think we need INVALID/NOTABUG or NEEDSINFO.
+
+INVALID is required when Bugzilla has a ""Resolved fixed"" status. (If something is not a bug, you can't mark it as fixed.)  We just have a resolved state now, and an issue is resolved whether we fix it with a patch or if we investigate and it was never an issue to begin with. 
+
+NEEDSINFO is just adding additional state complexity to Needs Triage. Either leave something in Needs Triage, or triage is as lowest possible priority, while requesting more info. If someone can't provide more info, then mark it as Resolved. 
+
+Declined is definitely better than WONTFIX. I will keep thinking on options there, but would be comfortable using that language. ",1410485852,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**qgil** wrote on `2014-05-30 19:04:51 (UTC)`
+
+What you are saying is that we can keep the current behavior, just changing the strings:
+
+* Open --> Open
+* Resolved --> Resolved
+* Wontfix --> Not a Bug
+* Invalid --> Needs Info
+
+> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+
+Remove the task from ""MediaWiki"" but keep it in ""MediaWiki 1.23.0""?",1410485852,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**jdforrester** wrote on `2014-05-30 18:34:42 (UTC)`
+
+[Updated] proposed set:
+
+  - OPEN
+  - RESOLVED
+  - DECLINED (rather than WONTFIX)
+  - NOTABUG (rather than INVALID, also replacing WORKSFORME)
+  - NEEDSINFO (consistent with not using ""_""s, INCOMPLETE sounds like it's about the task, not the request)
+
+Will validate these with other Product people.
+
+(Do we want to represent PATCH_FOR_REVIEW or DEPLOYED states somehow?)",1410485852,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-05-30 16:27:05 (UTC)`
+
+>>! In T359#10, @jdforrester wrote:
+>>>! In T359#8, @greg wrote:
+>> I don't find ""works for me"" useful. If anything, it should be called ""works, period"" aka ""not a bug"". The ""for me"" part bothers me.
+> 
+> I agree that it's a bit sucky; normally it's used for
+> 
+> 1. ""this is a fault you're experiencing due to something else not in our control"",
+> * ""this may be a fault, but you've given insufficient information to reproduce"", or occasionally
+> * ""this was fixed since it was filed but I don't know exactly how so, so I'm not going to mark as FIXED""
+> 
+> … so use case (2) is no longer needed if we add ""INCOMPLETE"" or ""NEEDSINFO"" or whatever, and case (1) //could// be marked as ""NOTABUG""/""INVALID""; for case (3) we could just be more lax about marking things as FIXED even when we don't know for sure that they are.
+
+Agreed. Or even NotABug for that last one. Doesn't really matter in the long run.
+
+>> I also find ""won't fix"" not useful. If it's not a bug, mark it as such. If it's way low priority, set the priority as such. Since we can have multiple projects in use by a team to track sprints and such, the product owner argument of ""I want a clean backlog"" doesn't apply.
+> 
+> I strongly disagree, and I think the term ""bug"" rather than ""task"" skews this.
+> 
+> There are totally ""valid"" requests for new features or feature enhancements which are incompatible with the direction that we want to take a product (//e.g.// ""Change the FOSS policy for Tool Labs so I can run Windows on it"" or ""Let me upload MPEG files to Commons"" or ""I want to have a button in VisualEditor to block the last editor if there are spelling mistakes""). ""Lowest"" priority for these is totally wrong – these are ""No, we will not do this ever, and we will work to stop other people doing this if they try"".
+
+Those all read like NotABug to me. ""Won't Fix"" is just a special type of NotABug. One that has reasoning based in 'product' versus 'actual code breakage.' It's the same thing in the end.
+
+>> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+> 
+> Yeah, deployment/release statuses would be a lovely nice-to-have, but maybe for post-initial-switch?
+
+Def.",1410485851,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**jdforrester** wrote on `2014-05-30 16:13:58 (UTC)`
+
+>>! In T359#8, @greg wrote:
+> My suggestion for day 1:
+> * Open
+> * Not a bug (instead of ""invalid"")
+> * Incomplete (or Needs more info)
+> * Fixed
+> 
+> I don't find ""works for me"" useful. If anything, it should be called ""works, period"" aka ""not a bug"". The ""for me"" part bothers me.
+
+I agree that it's a bit sucky; normally it's used for
+
+1. ""this is a fault you're experiencing due to something else not in our control"",
+* ""this may be a fault, but you've given insufficient information to reproduce"", or occasionally
+* ""this was fixed since it was filed but I don't know exactly how so, so I'm not going to mark as FIXED""
+
+… so use case (2) is no longer needed if we add ""INCOMPLETE"" or ""NEEDSINFO"" or whatever, and case (1) //could// be marked as ""NOTABUG""/""INVALID""; for case (3) we could just be more lax about marking things as FIXED even when we don't know for sure that they are.
+
+
+> I also find ""won't fix"" not useful. If it's not a bug, mark it as such. If it's way low priority, set the priority as such. Since we can have multiple projects in use by a team to track sprints and such, the product owner argument of ""I want a clean backlog"" doesn't apply.
+
+I strongly disagree, and I think the term ""bug"" rather than ""task"" skews this.
+
+There are totally ""valid"" requests for new features or feature enhancements which are incompatible with the direction that we want to take a product (//e.g.// ""Change the FOSS policy for Tool Labs so I can run Windows on it"" or ""Let me upload MPEG files to Commons"" or ""I want to have a button in VisualEditor to block the last editor if there are spelling mistakes""). ""Lowest"" priority for these is totally wrong – these are ""No, we will not do this ever, and we will work to stop other people doing this if they try"".
+
+
+> Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)
+
+Yeah, deployment/release statuses would be a lovely nice-to-have, but maybe for post-initial-switch?",1410485851,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide which task statuses we want to have in Maniphest,"**greg** wrote on `2014-05-30 15:58:06 (UTC)`
+
+My suggestion for day 1:
+* Open
+* Not a bug (instead of ""invalid"")
+* Incomplete (or Needs more info)
+* Fixed
+
+I don't find ""works for me"" useful. If anything, it should be called ""works, period"" aka ""not a bug"". The ""for me"" part bothers me.
+
+I also find ""won't fix"" not useful. If it's not a bug, mark it as such. If it's way low priority, set the priority as such. Since we can have multiple projects in use by a team to track sprints and such, the product owner argument of ""I want a clean backlog"" doesn't apply.
+
+Boy do I wish we could have separate statuses per project per task (eg: Fixed in master but open in 1.23.0)",1410485851,PHID-USER-nyhmztvvw4luz5mlcuvg,True,PHID-TASK-xs7dd22v62cbr3tksryr,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"I don't see a tracking of severity distinct from priority. Considering that priority has no universal meaning, but only a per-component meaning (at best), this seems very inappropriate for a disperse project like ours.
+http://c2.com/cgi/wiki?DifferentiatePriorityAndSeverity
+
+Moreover, the main use we make of ""Priority"" in bugzilla, i.e. how hard/expensive a bug is, is already covered by ""Points"".
+
+----
+
+**See also**: {T93499}",1397888043,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_description,declined
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"@Nemo_bis: You seem to mix up Severity (which had unhelpful non-discrete inconsistent values in Bugzilla like ""blocker"", ""critical"", ""major"", ""normal"", ""minor"", trivial"" and even ""enhancement"") and Task Types for categorization (think ""bug report"" vs ""feature request"").",1567372368,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,">>! In T102#11219, @Nemo_bis wrote:
+> Moreover, it's a huge culture shift. For countless years we've stressed how priority has a relative value (very subject to interpretations and context-sensitive) while severity has at least some very clear and relevant boundaries like feature request vs. bug. If the intention is to change this culture, just renaming or removing a field will not work: people will just talk past each other, each fitting the tool to their own view.
+
+It only took five years but eventually it happened: T93499, T224417#5215068. Maybe in five more years we'll be back to the place where we started, with all the bugzilla functions restored although in a messier way. :)",1567068538,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"For the records, T204138 added a `Risk` field.",1536782988,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"T109492 is rather unrelated to any ""severity"" (except for when you interpret new functionality or maintenance as always either less or more severe than the other one).",1440664451,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"Giving up on the Severity field has caused all sorts of negative consequences, in my opinion. Perhaps this decision should be revised in light of new superstructure which is being added (partly) to compensate the lack of such information, like T109492.",1440662013,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"As Priority was mentioned (though this is about Severity): Story points express estimated complexity and are not directly related to priority. I agree that priority is relative and that severity //in theory// has boundaries if well defined but I don't see a ""change to this culture"". I rather see an overcategorization via many many fields in Bugzilla that are only used by a small number of users hence I challenge the usefulness. One of the fields I consider pretty much useless is ""Severity"", explained above. In this ticket we discussed usecases for the severity field and didn't find many.",1413388287,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"I've read this discussion before, but I still don't understand the decision: either I forgot, or it was uncomprehensible. I'd like a summary of the reasoning to be added to the description of this task and/or documented, because I suspect some of the reasons may have been superseded by other decisions in the meanwhile.
+
+In its current setup, AFAICS, this instance has *three* manual ways to define priority: addition to a project (meaning a group is in theory working on it), workboard (which often says things like ""on hold"", ""next in our plate"" etc.) and points (how expensive is it). This is very confusing and inconsistent with the stated goals of this whole exercise, in particular with the idea of getting rid of the divide between priority field in bugzilla and sprint/roadmap assignments in mingle/trello.
+
+It's not even internally consistent, for instance ""Need volunteer"" is not a level (can't be sorted by any ordering method together with the others https://en.wikipedia.org/wiki/Total_order ), rather a tag/flag i.e. a project, or a workboard within an existing project, or just an expensive task which has no resources yet. So we already have a ""priority"" field which cannibalises other areas of maniphest.
+
+Moreover, it's a huge culture shift. For countless years we've stressed how priority has a relative value (very subject to interpretations and context-sensitive) while severity has at least some very clear and relevant boundaries like feature request vs. bug. If the intention is to change this culture, just renaming or removing a field will not work: people will just talk past each other, each fitting the tool to their own view. Besides, I don't see why we'd need or want to go this direction yet: for instance, there's been a lot of talk lately (mostly around https://meta.wikimedia.org/wiki/Community_Engagement_%28Product%29/Process_ideas and the countless related threads) about regressions vs. newly introduced bugs vs. feature request, and about *increasing* our ability to distinguish among them and measure them. And now we go in the opposite direction, dropping even ""enhancement"" vs. [trivial/minor/normal/major/critical] bug? Again, confusing.
+
+I'm not saying decision-makers here didn't know or consider all of this, they probably did: but I'm unable to tell, or to understand the decision. If you can't, or don't, explain the decision addressing all the topics above, then whatever you decided will not be applied in the reality of the issue tracker.",1413362360,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,//importing issue status//,1410485361,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-08-18 12:50:42 (UTC)`
+
+No replies to last comment, hence assuming that searching for the terms ""crash"" or ""NPE"" (favorized by the mobile app developers) seems to be sufficient for the ""critical severity"" case.
+
+Closing as DECLINED as we don't plan to copy the Severity field from Bugzilla to Maniphest.",1410485361,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-08-10 19:50:00 (UTC)`
+
+Remaining question: Is there interest in converting the ""crasher"" severity to a project/tag in Phabricator, similar to a keyword now in Bugzilla? Do people query explicitly for crashers in Bugzilla by querying for critival severity?",1410485360,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**mmodell** wrote on `2014-08-07 14:19:50 (UTC)`
+
+Also, FWIW: Phabricator has task dependencies to express ""blockers"" in much more useful and informative way... ""T1 blocks T2"" is much more useful than ""severity: blocker"" - that just says it's blocking _something_ but what's blocked?",1410485360,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-07-30 11:21:22 (UTC)`
+
+**tl;dr**
+
+Priority + Impact Tags + Effort points + Sprints is a better combination to plan our work. I would not migrate Bugzilla's Severity field as a custom field in our Phabricator.
+
+In detail:
+
+Considering that we are discussing the steps required before Day 1.
+
+Considering that Severity is supposed to be helpful to plan future sprints or the next task that you will work on.
+
+Considering that we have these priority options agreed for Day 1 (T436):
+
+* Needs Triage
+* Unbreak Now!
+* High
+* Medium
+* Needs Volunteer
+
+And considering that Bugzilla has these Severity options:
+
+* Blocker: 	 Blocks further development and/or testing work.
+* Critical: 	 Crashes, loss of data (internally, not your edit preview!) in a widely used and important component.
+* Major: 	 Major loss of function in an important area.
+* Normal: 	 Default/average.
+* Minor: 	 Minor loss of function, or other problem that does not affect many people or where an easy workaround is present.
+* Trivial: 	 Cosmetic problem like misspelled words or misaligned text which does not really cause problems.
+* Enhancement:    Request for a new feature or change in functionality for an existing feature.
+
+I still think that a Severity/Impact field forced onto all tasks is an overkill that will create more noise than usefulness. Our Bugzilla is a tangible proof. Think also that our Phabricator will not only be open for bugs but for all kinds of tasks. I would not migrate Severity as a custom field, but as a searchable text string in the task description.
+
+If a bug is a ""Blocker"", causes ""Crash"" or ""Data Loss"" (Blocker / Critical in Bugzilla) then we can project-tag them that way, being more specific and not making assumptions like ""It crashes, therefore it has a severe impact on many people"". If a bug blocks development, crashes applications, and destroys data in a bad way, it will be ""Unbreak Now"" or ""High"" priority, a candidate in any sprint planning meeting until it is solved.
+
+Discussing severity/impact Major-Normal, Normal-Minor, and Minor-Trivial is not very different from discussing priority High-Medium or Medium-Needs Volunteer. Basically you are discussing whether a problem is annoying enough to be considered by you / your team soon, some day in the future, or never.
+
+And Enhancement is out this equation anyway, as Andre says.",1410485360,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-07-29 22:14:35 (UTC)`
+
+>>! In T168#60, @aklapper wrote:
+>>>! In T168#57, @jdforrester wrote:
+>> As a product manager, I need an orthogonal way to represent how major an issue/problem/improvement a task is for users, distinct from whatever priority I have currently given it (""priority"") and how difficult it is for engineers to do (""points"").
+>> 
+>> This is vital when considering which tasks should go in each sprint, and reconsidering longer-term prioritisation. It is particularly important for triaging tasks reported by users and others, to gauge which ones to triage first.
+> 
+> How often do tasks go into a sprint which have lower impact (minor or trivial, in current Bugzilla terms)?
+
+All the time. Normally large-impact changes are intentionally rationed per release – both because there's often a strong correlation between size of impact and size of work, but also because we don't want to make too many large changes for users at once. Also, there's a need for balance for both scale and type of workload between individual team members, and within each engineer's workload.
+
+> With regard to longer-term prioritisation: Would that mean it's more likely that you add tasks to a future sprint which had a lower priority but a higher impact/severity?
+
+Yes, though I'd be likely (but not guaranteed) to raise the priority based on impact as well. In general, higher-priority items would be expected to be put into the sprint ahead of equivalent lower-priority ones.
+
+> If so, I'd interpret that as using Severity/Impact to ""subclassify"" tasks sharing the same lower Priority, to bump Priority later based on Severity/Impact. It's a pattern that can also be observed in Eclipse Bugzilla (according to page 4 in http://herraiz.org/papers/english/msr84cp-herraiz.pdf ).
+
+That's a possible analysis, though I think that it's used more as a signal rather than a raw sub-priority field.",1410485359,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-07-29 22:02:35 (UTC)`
+
+>>! In T168#57, @jdforrester wrote:
+> As a product manager, I need an orthogonal way to represent how major an issue/problem/improvement a task is for users, distinct from whatever priority I have currently given it (""priority"") and how difficult it is for engineers to do (""points"").
+> 
+> This is vital when considering which tasks should go in each sprint, and reconsidering longer-term prioritisation. It is particularly important for triaging tasks reported by users and others, to gauge which ones to triage first.
+
+How often do tasks go into a sprint which have lower impact (minor or trivial, in current Bugzilla terms)?
+
+With regard to longer-term prioritisation: Would that mean it's more likely that you add tasks to a future sprint which had a lower priority but a higher impact/severity? If so, I'd interpret that as using Severity/Impact to ""subclassify"" tasks sharing the same lower Priority, to bump Priority later based on Severity/Impact. It's a pattern that can also be observed in Eclipse Bugzilla (according to page 4 in http://herraiz.org/papers/english/msr84cp-herraiz.pdf ).",1410485359,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-07-29 21:51:47 (UTC)`
+
+>>! In T168#56, @Waldir wrote:
+> I stand by my proposal to have a severity/impact dual-axis priority measure, with the highest priority items at the top right of the resulting space.
+
+I'd like to see this in practice somewhere. It could work but I haven't see any tool implementing this.
+
+> I agree the current definition of severity isn't ideal, but it's certainly a good start.
+
+I don't see how it's ""a good start"".
+
+> For example, the ""important area to whom"" question can be defined, say, in terms of the WMF's strategic goals, or the Engineering team
+
+If the several stakeholders can somehow agree on something, okay. Again, designers might have a different interpretation of ""major issue"" than a performance engineer (maybe a bad example if it's unlikely that one bug report will touch both design and performance).
+
+> getting rid of the ""unspecified"" value
+
+(The Severity field in Bugzilla has no ""unspecified"" value - that's the Priority field.)
+
+> and assigning a mid-range value by default (maybe ""enhancement"", based on the 60% number cited above?) could help here.
+
+Enhancement will be expressed by the ""Priority"" value ""Wishlist"" in Phabricator. Also, ""enhancement"" is unrelated to any Severity/Impact. Instead it is a boolean value on its own. (That enhancement request to replace the joystick by a steering wheel in the car that we produce can be pretty severe if all other competitors ship that already and if we'd go bankrupt). It is wrong that Bugzilla has ""enhancement"" as a value in its Severity field.
+
+> I proposed impact as a measure of how many people the issue annoys.
+
+I don't see how ""many people"" can be defined. Estimation must be based on something, otherwise I'd call it wild guessing.
+
+> I just think two reasonably objective measures with sane defaults are better than a single, subjective priority measure that we often won't be able to agree on
+
+I miss how to concretely achieve such ""objective measures"" because currently we don't have them. If you can draw such concrete values and add them to the discussion here, that would be awesome. Right now it feels like ""things aren't great, we can improve them"" but I don't see a clear and specific proposal. And I miss why it's ""better"" - usecases.",1410485358,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-07-29 21:32:21 (UTC)`
+
+I also completely disagree with @aklapper about getting rid of some measure of severity/impact, as already stated.
+
+As a product manager, I need an orthogonal way to represent how major an issue/problem/improvement a task is for users, distinct from whatever priority I have currently given it (""priority"") and how difficult it is for engineers to do (""points"").
+
+This is vital when considering which tasks should go in each sprint, and reconsidering longer-term prioritisation. It is particularly important for triaging tasks reported by users and others, to gauge which ones to triage first.",1410485358,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Waldir** wrote on `2014-07-29 20:45:25 (UTC)`
+
+**tl;dr** I stand by my proposal to have a severity/impact dual-axis priority measure, with the highest priority items at the top right of the resulting space.
+
+I agree the current definition of severity isn't ideal, but it's certainly a good start. Nothing prevents us from working up it. For example, the ""important area to whom"" question can be defined, say, in terms of the WMF's strategic goals, or the Engineering team; and ""trivial"" could be removed since it's a measure of effort, not severity. Other improvements are certainly possible.
+
+Then there's the issue of us actually making use of it; getting rid of the ""unspecified"" value and assigning a mid-range value by default (maybe ""enhancement"", based on the 60% number cited above?) could help here.
+
+> So I guess I believe that impact (severity? frequency?) influences priority
+I proposed impact as a measure of how many people the issue annoys. Severity can be measured separately, as mentioned above, and frequency isn't really a factor in our case: bugs that appear to occur randomly are usually just those that occur under a (yet unknown) set of conditions. Instead, a simple scale based on an rough estimation of how many users are affected could work well.
+
+> An uncommon feature request won't happen and will be lowest priority as long as nobody works on it, and if somebody considers a feature crucial, s/he will assign it to her/him and its priority will be raised.
+
+These (mostly the first) seem to me like effects of an ""impact"" metric. The second scenario is true whatever the priority defined for the bug so it's irrelevant if we want a measure that's as objective as possible (i.e. predicts how soon the issue is addressed). Using the criteria that are already implicitly in use, as Quim mentions above, seems like the best way to do this.
+
+Note that I don't mean to simply cling to my previous position; I just think two reasonably objective measures with sane defaults are better than a single, subjective priority measure that we often won't be able to agree on, and tokens which depend strongly on the number of stakeholders that actually participate on the bug tracker (which historically has been very low and biased toward the more tec).",1410485358,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-07-28 20:33:10 (UTC)`
+
+I take the silence as people agreeing on my last comment. If not, please raise your voice before it's too late.",1410485357,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-07-15 23:51:33 (UTC)`
+
+**<tl;dr>:** My current position is that we do not need a general Severity or Impact field, but I'm welcome to hear more arguments, and I'd be fine with defining clear, isolated usecases for queries (and how they support our software development processes) that we might want to implement in some way (e.g. a ""crasher"" project, or via defining tokens as mentioned by Mukunda).
+
+**Long version:**
+
+Severity is only objective and informative if its values are clearly defined (see https://www.mediawiki.org/wiki/Bugzilla/Fields#Severity for our attempt which isn't too great) **and** if it is consistently used. Both is often not the case.
+
+Currently in Bugzilla, ""normal"" severity can mean anything. For ""major"", ""Major loss of function in an important area"" already has two subjective terms - what's important to you and me? An issue can be ""minor"" or ""trivial"" severity (what's the difference?) to fix when it's a typo, still a typo can trigger a crasher (defined as ""critical"" severity in Bugzilla and hence conflicting).
+
+While Wikimedia Bugzilla is one of those instances which set ""unspecified"" severity by default, it's been shown that reporters often keep the default value set by ignoring yet another field (see http://ansymo.ua.ac.be/~alamkan/wp-content/papercite-data/pdf/lamkanfi2010msr.pdf page 2), hence up to 60% of reports in some Bugzillas are misclassified as people did not find the ""enhancement"" value hidden in there and instead write ""RFE"" in the bug summary (see page 4 of https://www.st.cs.uni-saarland.de/softevo/bugclassify/paper/icse2013-bugclassify.pdf ).
+
+Currently I don't even believe currently that differentiating feature requests/enhancement and bugs make much sense because it's often impossible to draw the line (I won't drop the four quotes from papers now). An uncommon feature request won't happen and will be lowest priority as long as nobody works on it, and if somebody considers a feature crucial, s/he will assign it to her/him and its priority will be raised. So I guess I believe that impact (severity? frequency?) influences priority, among other things like ""cost of fixing"" and ""risk of fixing"" (which we didn't express via fields so far either in Bugzilla, but we got points in Phabricator). For the records, I stole these criteria from http://www.ericsink.com/articles/Four_Questions.html.
+
+If you like querying for critical and blocker bugs not just for academical reasons (though again I must warn that any bug report numbers depend first on ""the number of users using the software, and the convenience with which those users can register new bugs"" and only to lesser extend on ""the absolute number of bugs present in the software"", to quote page 26-27 from Karl Fogel's ""Producing Open Source Software"" from 2006), I would honestly love to know the usecase, and we could for example set up a ""crasher"" project, cross-codebase, or play with tokens.
+
+(PS: Yes, I like to base decisions to some extend on science as we're not the first people running into these questions.)",1410485357,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**mmodell** wrote on `2014-07-15 22:35:23 (UTC)`
+
+Phabricator's tokens are a perfectly good way to represent ""impact"" - people can individually assign tokens to express the impact that a given bug is having on them and the tokens are prominently displayed on the task with representative icons. We just need to assign some meanings to the tokens, more explicitly than they currently have in the UI.",1410485357,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Waldir** wrote on `2014-07-15 17:08:44 (UTC)`
+
+>>! In T168#50, @qgil wrote:
+> Do we really gain clarity by adding a parameter of ""Severity""? A ""Normal"" problem annoying many people will get a ""Medium"" / ""High"" priority and will be schedule in a foreseeable sprint. A ""Major"" or even ""Critical"" problem around a corner case of the likes of ""only in PostgreSQL"" will in practice fall under ""Needs Volunteer"" no matter what.
+> 
+> In other words, maybe what happens is that ""severity"" is not as objective and informative as it sounds, and what really counts is how relevant it is for those who actually can complete a task.
+
+After thinking about this some more, I'd say that ""severity"" is actually both objective and informative (it means essentially ""how much this breaks things""). On the contrary, I'd argue that what's not objective is Bugzilla's ""priority"" (i.e. timing-priority, or ""this needs to be done soon""). That should essentially be the final arbiter of what to do next, but it should be defined based on objective components, not as a subjective single-axis. Your comment goes to the core of this: the ""how many people are annoyed by this"" factor (i.e. ""impact"") is central to how we make decisions, yet it's nowhere represented in the systems we use.
+
+So perhaps instead of a single, subjective ""priority"" measure, we should keep bugzilla's two-axis system, but replacing ""priority"" with ""impact"", with impact having a stronger weight in the priority calculation. That would solve the problems you point out: a low-severity, high-impact problem will have higher priority than a high-severity, low-impact one, which is what we already observe today. And an issue with a ""blocker"" severity could then be untackled for years without diluting the meaning of severity, because we're explicitly acknowledging it's a low-impact one.",1410485356,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-07-10 17:39:30 (UTC)`
+
+Revisiting this discussion under the assumption that we would have these levels of Priority (see {T436}):
+
+> * Needs Triage
+> * Unbreak Now!
+> * High
+> * Medium
+> * Needs Volunteer
+
+Do we really gain clarity by adding a parameter of ""Severity""? A ""Normal"" problem annoying many people will get a ""Medium"" / ""High"" priority and will be schedule in a foreseeable sprint. A ""Major"" or even ""Critical"" problem around a corner case of the likes of ""only in PostgreSQL"" will in practice fall under ""Needs Volunteer"" no matter what.
+
+In other words, maybe what happens is that ""severity"" is not as objective and informative as it sounds, and what really counts is how relevant it is for those who actually can complete a task. I'd rather have a simple axis (Priority) driving what is scheduled in forthcoming sprints, and then community discussion and negotiation on whether e.g. a ""Needs Volunteer"" task will be taken by a team as ""Medium"", and from there to a sprint.
+
+Otherwise we end up in situations where ""critical"" and ""blocker"" bugs [[ https://bugzilla.wikimedia.org/buglist.cgi?bug_severity=blocker&bug_severity=critical&chfield=%5BBug%20creation%5D&chfieldto=2y&list_id=328275&product=Cortado&product=Datasets&product=Huggle&product=Kate%27s%20Tools&product=Logwood&product=MediaWiki&product=MediaWiki%20extensions&product=MediaWiki%20skins&product=MediaWiki-Vagrant&product=MobileFrontend&product=mwEmbed&product=OOjs&product=OOjs%20UI&product=openZIM&product=Parsoid&product=Pywikibot&product=QRpedia&product=Spam&product=Tool%20Labs%20tools&product=Unofficial%20Apps&product=Utilities&product=VisualEditor&product=Wiki%20Loves%20Monuments&product=WikiLoves%20Monuments%20Mobile&product=Wikimedia&product=Wikimedia%20Labs&product=Wikimedia%20Mobile&product=Wikipedia%20App&product=Wiktionary%20tools&query_format=advanced&resolution=--- | sit around for years ]], diluting the meaning of those terms. ",1410485356,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**swalling** wrote on `2014-07-02 20:16:52 (UTC)`
+
+> Ok, then I rephrase my question: is there a document (or more) summarising what's the current expectation of their meaning for those who use them?
+
+Points are used in the same way they're understood in other Agile contexts. If you're looking for documentation, all you need do is Google around. 
+
+TL;DR summary: You assign points to a task to estimate the time and effort involved in a task. You can then track how many points you completed over a given sprint (i.e. a two week period), and adjust expectations about the team's capacity in the next sprint. In other words, it helps you more accurately guess how much you can reasonably get done. 
+
+",1410485356,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Nemo_bis** wrote on `2014-07-02 20:08:33 (UTC)`
+
+> I think we should feel free to innovate.
+
+For instance by removing this field: I agree with comment #44
+
+> the two teams that use them have repeatedly said they are a critical day-0 blocker for them.
+
+Ok, then I rephrase my question: is there a document (or more) summarising what's the current expectation of their meaning for those who use them?",1410485355,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-06-30 19:46:13 (UTC)`
+
+>>! In T168#46, @Waldir wrote:
+> Merging //target milestone// and //(timing) priority// sounds like a good idea in combination with the above, since it'd provide a concrete, straightforward way to define urgency.
+
+I completely and absolutely disagree. ""Milestone"" is something like ""Alpha release 244: 2014-06-30"" or ""1.23"", and is used for short-term planning (what are we working on this week?) and retrospective listing (what did we work on in week x?). It's not a long-term planning thing at all, and trying to merge the priority concept with a short-term planning framework is doomed to failure.
+",1410485355,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Waldir** wrote on `2014-06-25 19:49:40 (UTC)`
+
+My two cents: I've been thinking a lot recently about how to define task priorities (in general) in an objective way. I looked at [bugzilla's model](https://www.mediawiki.org/wiki/Bugzilla/Fields#Importance) for inspiration, and found the terms used (importance, priority and severity) to be somewhat vague. Thinking of ""priority"" as ""urgency"", and of ""severity"" as ""impact"", allowed me to grasp their meaning (and how they relate to each other) more intuitively.
+
+Granted, ""severity"" is good enough a term, but ""impact"" is more common and can stand for both positive and negative impact, while severity is mostly negative thing. ""Priority"" definitely feels more objective when defined as ""urgency"". ""Priority"" and ""importance"" (and ""points"") are terms that should be avoided, IMO, since their meaning is not universal.
+
+Essentially, I agree with what @aklapper said in T168#14, except that I'd use the terms **urgency**, **impact** and **effort**, to mean ""timing-priority"", ""importance-priority"" and ""difficulty-priority"". Merging //target milestone// and //(timing) priority// sounds like a good idea in combination with the above, since it'd provide a concrete, straightforward way to define urgency. Impact can be defined in terms of how many people are affected, and how often (e.g. readers/editors/admins, vs. on every page view/only on a specific subset of pages/only when using parameters x and y). Effort can be just a rough estimate of hours needed to code up the required change (anything too big to be estimated should become a tracking issue anyway).",1410485355,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-06-16 18:59:59 (UTC)`
+
+>>! In T168#44, @qgil wrote:
+>>>! In T168#43, @jdforrester wrote:
+>> ""Most"" people at WMF Engineering don't use points; I'd imagine that third party and volunteer developers have even less reason to  have particular expectations of their use in the MediaWiki world, so I think we should feel free to innovate.
+> 
+> Or we could just remove them until we find a good use for them. This is a custom field that someone added, not a Phabricator feature out of the box.
+
+""Most"" !== all; the two teams that use them have repeatedly said they are a critical day-0 blocker for them.",1410485354,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-06-16 18:39:23 (UTC)`
+
+>>! In T168#43, @jdforrester wrote:
+> ""Most"" people at WMF Engineering don't use points; I'd imagine that third party and volunteer developers have even less reason to  have particular expectations of their use in the MediaWiki world, so I think we should feel free to innovate.
+
+Or we could just remove them until we find a good use for them. This is a custom field that someone added, not a Phabricator feature out of the box.
+
+",1410485354,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-06-16 18:24:58 (UTC)`
+
+>>! In T168#42, @Nemo_bis wrote:
+>> data on severity into the ""points"" field in some fashion (Blocker -> 13, Critical -> 8, Major -> 5, … or whatever).
+> 
+> This doesn't fit my (very limited) understanding of what agile points are. Is there a good concise document summarising what's the current expectation of their meaning for most people in Wikimedia/MediaWiki?
+
+""Most"" people at WMF Engineering don't use points; I'd imagine that third party and volunteer developers have even less reason to  have particular expectations of their use in the MediaWiki world, so I think we should feel free to innovate.",1410485354,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**Nemo_bis** wrote on `2014-06-15 09:29:26 (UTC)`
+
+> Priority and severity fields are just too fine-grained to be useful in seriously prioritizing tasks.
+
+I agree on this, but mostly because the recent addition of ""Highest"", ""Immediate"" and ""Lowest"" is disputable.
+
+> data on severity into the ""points"" field in some fashion (Blocker -> 13, Critical -> 8, Major -> 5, … or whatever).
+
+This doesn't fit my (very limited) understanding of what agile points are. Is there a good concise document summarising what's the current expectation of their meaning for most people in Wikimedia/MediaWiki?",1410485353,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-06-02 13:02:14 (UTC)`
+
+> I don't think a severity field per se is a useful addition,
+
++1.
+
+> and instead we should probably import the data on severity into the ""points"" field in some fashion (Blocker -> 13, Critical -> 8, Major -> 5, … or whatever).
+
+So in Phab we'd have priority, points, and columns to express 'things'.
+
+For general understanding and refering to the Severity field values in Bugzilla: Currently a bug report in Bugzilla about a crasher is critical by definition, but would be low priority if circumstances to reproduce required special rights in some rather uncommon volunteer-supported database backend (or such; to come up with one vague example). 
+Bugzilla's //critical// severity could also be expressed by a //crash// project or so; //enhancement// is already expressed via priority (instead of severity) in Phabricator. Bugzilla severities like //trivial// or //minor// don't make sense (a trivial typo could still trigger a critical crasher) and feel like sufficiently expressed by Bugzilla's //easy// keyword which would end up as another project in Phabricator.",1410485353,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-30 21:08:00 (UTC)`
+
+>>! In T168#36, @swalling wrote:
+> I'd //really really// like to try leaving the Phabricator defaults alone in terms of priority. When prioritizing Growth's last sprint in Phabricator, I found the list of current values to be very useful. Any tinkering we do is kind of bikeshedding here, IMO.
+
+I agree. I don't think a severity field //per se// is a useful addition, and instead we should probably import the data on severity into the ""points"" field in some fashion (Blocker -> 13, Critical -> 8, Major -> 5, … or whatever).
+
+
+> One of the great problems of Bugzilla is that there is just too much bullshit to deal with. Priority //and// severity fields are just too fine-grained to be useful in seriously prioritizing tasks. The same goes for Target Milestone etc... almost zero people seriously use these fields or rely on them now. 
+
+Remember that the milestones will be replaced by (sub)projects, which will be used to recording sprint activity. I'm assuming you //do// want to continue having sprints in Growth? Certainly, other teams are going to. :-)",1410485352,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-30 21:05:04 (UTC)`
+
+>>! In T168#34, @qgil wrote:
+> a casual call for opinions at wikitech-l might be interesting as well, especially if we plan to change the current Bugzilla status quo.
+
+I agree that we should definitely set out in detail what we plan to do in an e-mail to wikitech-l once we've got an idea. Maybe it's a bit premature now? Many people find it easier to find issues with a strawman/proposal than just to answer in a vacuum.
+",1410485352,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-05-30 19:33:55 (UTC)`
+
+I also think we can keep the default values and then use projects for whatever else (Easy, Security, Regressions, Sprint Candidates, etc). Custom fields bring unnecessary clutter for all tasks, most of them not needing such level of detail.",1410485352,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**swalling** wrote on `2014-05-30 19:19:29 (UTC)`
+
+I'd //really really// like to try leaving the Phabricator defaults alone in terms of priority. When prioritizing Growth's last sprint in Phabricator, I found the list of current values to be very useful. Any tinkering we do is kind of bikeshedding here, IMO. 
+
+One of the great problems of Bugzilla is that there is just too much bullshit to deal with. Priority //and// severity fields are just too fine-grained to be useful in seriously prioritizing tasks. The same goes for Target Milestone etc... almost zero people seriously use these fields or rely on them now. ",1410485351,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-05-30 00:29:56 (UTC)`
+
+>>! In T168#28, @TheDJ wrote:
+> Can we set the visibility of fields ? Then we can at least import it and initial hide it for everyone, then argue about how to follow up :)
+
+I'd argue before importing the data. What is stopping us from having this discussion?
+
+If we create the custom field, place there the severity data, and then hide it, such data will be ""lost"" from the users point of view. If we decide not to have it beforehand, or to have something else, the such data can appear in the task description as plain text.
+
+@aklapper and @jdforrester, I think you two should weigh in with an official position from the Phabmaster & PM team, if possible at all.
+
+Edited: a casual call for opinions at wikitech-l might be interesting as well, especially if we plan to change the current Bugzilla status quo.",1410485351,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**TheDJ** wrote on `2014-05-29 16:15:27 (UTC)`
+
+I'm trying this on my own instance, and i'm thus not sure if we are looking at the exact same thing, but the options is intended to be as flexible as https://fab.wmflabs.org/config/edit/differential.fields/ I presume, so I think the maniphest.fields option is currently awaiting to get the same treatment.
+
+https://secure.phabricator.com/T5011 indicates as much.",1410485351,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-29 15:33:57 (UTC)`
+
+>>! In T168#30, @aklapper wrote:
+>> Can we set the visibility of fields ?
+> 
+> Admins can add custom fields at http://fab.wmflabs.org/config/edit/maniphest.custom-field-definitions/
+> 
+> Docs in https://secure.phabricator.com/book/phabricator/article/custom_fields/ say ""The fields will then appear in the other config option for the application (for example, in maniphest.fields) and you can enable, disable, or reorder them."" so //disabling// should be possible. Haven't tried; if it does not fit our needs a hackish workaround would be using ""display: none"" CSS which I'd like to avoid.
+
+This seems a little limited unless I'm missing something – http://fab.wmflabs.org/config/edit/maniphest.fields/ lets you adjust what fields tasks have, but the only field shown (presumably, the only optional field?) is story points – I don't immediately see a way to remove other default fields. Also, it's not clear if removing the field disables it or just fails to show it, and of course it might behave differently for the built-in field for story points compared to a new field we added…
+
+BTW, editing what values the built-in fields have is trivial – see for example http://fab.wmflabs.org/config/edit/maniphest.statuses/ where (if you're an admin) you can edit the task status values available, or http://fab.wmflabs.org/config/edit/maniphest.priorities/ for the task priority values.",1410485350,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-05-28 17:00:37 (UTC)`
+
+> Can we set the visibility of fields ?
+
+Admins can add custom fields at http://fab.wmflabs.org/config/edit/maniphest.custom-field-definitions/
+
+Docs in https://secure.phabricator.com/book/phabricator/article/custom_fields/ say ""The fields will then appear in the other config option for the application (for example, in maniphest.fields) and you can enable, disable, or reorder them."" so //disabling// should be possible. Haven't tried; if it does not fit our needs a hackish workaround would be using ""display: none"" CSS which I'd like to avoid.",1410485350,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**TheDJ** wrote on `2014-05-23 18:15:22 (UTC)`
+
+Can we set the visibility of fields ? Then we can at least import it and initial hide it for everyone, then argue about how to follow up :)",1410485350,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-05-11 09:25:00 (UTC)`
+
+> It was, however, the sole proposal moved
+
+Because I wasn't paying enough attention.  :) 
+
+If we have a Severity field in Day 1, we will have it in Day 10.000. If there is a time to challenge our current classification of bug/task status, this time is now.
+
+Then again, while I do have a strong opinion about the need to revisit this topic and find an agreement now, I don't have any strong opinion about the decision itself. Whatever works for Andre will work for me.",1410485349,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-11 07:39:32 (UTC)`
+
+> To be precise, this was ""a proposal"" and not ""the proposal"".
+
+It was, however, **the** sole proposal moved, and reached unanimous approval (if not agreement), especially that this shouldn't be a block for Day 1 and could instead be changed later.
+",1410485349,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-05-10 23:26:56 (UTC)`
+
+To be precise, this was ""a proposal"" and not ""the proposal"". I the topic of priority/severity/importance deserves a good community discussion, in my opinion. We have a chance to improve the current system, if needed. After the migration will be too late. 
+
+If we discuss and reach to the conclusion that changing the current approach is not needed, fine. However, deciding after a few minutes of discussion in an afternoon doesn't look sensible to me. ",1410485349,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**jdforrester** wrote on `2014-05-10 15:06:41 (UTC)`
+
+The proposal in a meeting at the Zürich Hackathon was to mirror Bugzilla's existing `severity` field in Phabricator when we set it up, alongside the `priority` one.",1410485348,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-04-23 21:03:14 (UTC)`
+
+For what is worth, there is an interesting discussion about Important vs Urgent in the context of Phabricator at https://secure.phabricator.com/T4807",1410485348,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-04-22 07:05:18 (UTC)`
+
+.... so I don't consider ""No severity field"" a bug per se. Missing functionality to describe or categorize something would be a bug if it's considered important enough to categorize. :)",1410485348,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**aklapper** wrote on `2014-04-22 07:03:29 (UTC)`
+
+I'd like to see a broader discussion first if anybody would like to have a ""Severity"" field (or maybe ""Impact"" which would be a better name). Priority, Severity and Target Milestone in Bugzilla often feel like unneeded complication.
+
+Two examples refering to potential shortcomes of Bugzilla's concept:
+JamesF once mentioned
+  - ​Timing-priority == ""this needs to be done soon""
+  - Importance-priority == ""this is affecting lots of people / lots of actions / has major impact""
+  - Difficulty-priority == ""this is really hard to do""​
+RobLa once thought of merging Target Milestone and Priority - both should describe when / how urgent an issue should get fixed, so (simplified) high priority would be TM = next release, normal priority = release after, low priority = not planned.",1410485347,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-04-22 00:59:21 (UTC)`
+
+Marked as resolved for the purpose of this RfC. If we want Severity field we can have it.",1410485347,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Decide whether we need to add a severity (impact) field to match Bugzilla's,"**qgil** wrote on `2014-04-19 16:14:25 (UTC)`
+
+If we need a field for severity, we can create it through Phabricator's configuration options.",1410485346,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-epgl7mls74tyc7pzzpv7,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"DECISION: We will use `phabricator.wikimedia.org` as the domain for the service.
+
+cnames for any shortened version
+
+----
+
+We need to decide a domain (and therefore a name) for the Phabricator instance in Wikimedia.
+
+Do we want to use something around the ""Phabricator"" brand or do we prefer to go for a descriptive alternative, or a totally invented name?
+
+We have used bugzilla.wikimedia.org and gerrit.wikimedia.org, therefore phabricator.wikimedia.org cannot be too wrong. Still, it is long, and I'm personally not convinced of relying so much on product names.",1397747363,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_description,resolved
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,">>! In T82#808118, @Quiddity wrote:
+> searching for fl294 didn't work.
+
+It does. Go to Maniphest's advanced search and enter ""fl294"" in the Reference field. :)
+I admit it's not [[ https://www.mediawiki.org/wiki/Phabricator/Help#Searching_for_items | documented ]] though; Bugzilla felt like a more common usecase.
+
+> Where is the setting up task? Thanks :)
+
+It's T178",1417649605,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,">>! In T82#1216, @flimport wrote:
+> **aklapper** wrote on `2014-05-16 22:04:24 (UTC)`
+> 
+> This ticket is resolved when it comes to //deciding// what the URL should be. I wondered whether to keep this open for actually setting up that subdomain, but I guess that's sufficiently covered by T294.
+
+That ticket seems to be from the older phablabs test instance, and searching for fl294 didn't work. Where is the setting up task? Thanks :)",1417635269,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,//importing issue status//,1410485245,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**aklapper** wrote on `2014-06-13 15:51:17 (UTC)`
+
+Makes sense. Thanks for setting this up. 
+
+For the records, reference to current setup of Bugzilla cert and CNAMEs: https://rt.wikimedia.org/Ticket/Display.html?id=5011",1410485244,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**Rush** wrote on `2014-06-13 15:49:24 (UTC)`
+
+just a note, this idea comes into contact with the real world as I need to request SSL certificates that have to reflect these names.  If anyone wants a shortened version in addition to phab.wm.org now is the time to suggest :)",1410485244,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**Rush** wrote on `2014-06-13 15:48:07 (UTC)`
+
+I'm sorry I didn't see this ticket earlier.  So the external facing URL has a standard.  We typically use the full service url (graphite.wikimedia.org / bugzilla.wikimedia.org) and do not do shortened url's for the main A record.  That being said we do use cnames for shorter versions.  We have bugs.wikimedia.org for bugzilla for example.  
+
+Since this is the operations standard I am going to change the title url to be: phabricator.wikimedia.org
+
+...with the intention of mimicking the bugs.wm.org behavior for phab.wm.org
+
+should satisfy both and still maintain the standard?",1410485244,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**aklapper** wrote on `2014-05-16 22:04:24 (UTC)`
+
+This ticket is resolved when it comes to //deciding// what the URL should be. I wondered whether to keep this open for actually setting up that subdomain, but I guess that's sufficiently covered by T294.",1410485243,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**jdforrester** wrote on `2014-05-10 14:59:48 (UTC)`
+
+`phab.wikimedia.org` appears to be the clear winner; let's proceed on this basis.",1410485243,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**aklapper** wrote on `2014-05-03 22:40:40 (UTC)`
+
+""collabtools"" doesn't convince me either and the generic tech term ""forge"" isn't common enough yet, so I guess we could stick to phab.wikimedia.org (because we can).",1410485243,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**qgil** wrote on `2014-04-17 19:56:15 (UTC)`
+
+Alright, so maybe after all we are talking about 
+
+fab.wikimedia.org
+
+or
+
+phab.wikimedia.org",1410485242,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**jdforrester** wrote on `2014-04-17 19:25:10 (UTC)`
+
+This is and always will be a secondary location for task management for Wikimedia compared to the wikis – fundamentally, work by volunteers happens primarily on-wiki, and calling this something not specific to code and technical makes it look like we're normalising off-wiki work – an exception that is rare.
+
+Calling this `tasks` would strongly suggest that this is where the vast majority of tasks by volume (editing pages, patrolling edits, uploading images, discussing improvements, blocking users,…) happens, and I think that this would be a mistake.
+
+`ph` would intrude into the reserved https://en.wikipedia.org/wiki/ISO_3166-2 and https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 spaces for chapters.",1410485242,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**qgil** wrote on `2014-04-17 18:46:47 (UTC)`
+
+Agreed on the .wikimedia.org part.
+
+One ""problem"" with code. and other tech. references is that non-coding non-tech projects might be interested as well. This is not just an hypothesis; @MissGayle and @philippe have been playing around already, and I don't see why we couldn't recommend this environment just to any project needing to organize tasks that may or may not have a connection with code.
+
+Being also very pragmatical: if more WMF teams, chapters, etc would find this tool interesting it would be easier to find resources to maintain it properly.
+
+Anyway, more ideas:
+
+tasks.wikimedia.org (like projects, without the double meaning)
+
+ph.wikimedia.org  (just because we can)",1410485242,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**jdforrester** wrote on `2014-04-17 15:50:09 (UTC)`
+
+[Commence bike-shedding]
+
+I think ""`projects.wikimedia.org`"" is confusing with regard to which projects (Wikipedia and Wiktionary are projects of the Wikimedia movement; Military History is a [wiki]project of the English Wikipedia; //etc.//).
+
+I approve of hosting off `.wikimedia.org` rather than `.mediawiki.org` because we do rather more than just MediaWiki development nowadays (most notably operations work, but also //e.g.// VisualEditor), and we should be consistent with `git.wikimedia.org`, `bugzilla.wikimedia.org`, `rt.wikimedia.org` and so on.
+
+Personally I like `code.wikimedia.org` as it's simple and direct, and doesn't interfere with potential chapter domain names, but could be argued around.",1410485241,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org,"**qgil** wrote on `2014-04-17 15:09:38 (UTC)`
+
+  projects.wikimedia.org
+
+?",1410485241,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-iltgxch7wxmytcatl3vo,task_subcomment,NA
+Document benefits for Bugzilla users,"**Document moved to https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/versus_Bugzilla -- you are welcome to edit and discuss there.**
+
+As a bugzilla volunteer user, I want to know what I'm supposed to gain from the migration to phabricator, which is bound to add work I've not asked for.",1397721605,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-pf7labc5tuafvfstlptu,task_description,resolved
+Document benefits for Bugzilla users,//importing issue status//,1410485129,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**qgil** wrote on `2014-04-27 03:53:40 (UTC)`
+
+Actually, I wanted to see what happens when you copy text in Phabricator and paste it in MediaWiki using VisualEditor...  :)
+
+https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/versus_Bugzilla
+
+Resolving the task here, if you want to improve the document let's do it there.",1410485129,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**qgil** wrote on `2014-04-27 03:10:15 (UTC)`
+
+I have been solving the task in its own description. Please have a look and edit at will. On Monday I will public the content in mediawiki.org... where?",1410485128,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**Nemo_bis** wrote on `2014-04-19 18:59:59 (UTC)`
+
+> Nemo, could you take the lead in this task, please?
+
+I still found none. I'm editing the task description for now, space is plenty for what I found.",1410485128,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**qgil** wrote on `2014-04-19 16:17:50 (UTC)`
+
+I agree that having such document would be useful, but it would be even more useful in a wiki page closer to the RfC. Nemo, could you take the lead in this task, please? I will help editing.",1410485128,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Document benefits for Bugzilla users,"**Nemo_bis** wrote on `2014-04-17 08:36:11 (UTC)`
+
+Ideas can be found in https://bugzilla.wikimedia.org/buglist.cgi?bug_severity=enhancement&component=Bugzilla&list_id=305582&product=Wikimedia&query_format=advanced&resolution=--- : list the enhancement requests that phabricator would satisfy",1410485127,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-pf7labc5tuafvfstlptu,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Currently, {{int:}} is (ab)used to localize content, either directly by showing a localised message or by using e.g. [[ https://commons.wikimedia.org/w/index.php?title=Special%3ASearch&search=MediaWiki%3ALang&fulltext=1 | MediaWiki:Lang ]] to achieve conditional transclusion à-la {{sometemplate/{{int:lang}}}}. However, Parsoid always assumes content language for this parser function. This is generally not a problem for VisualEditor where it even makes sense to display a ""canonical"" version of text, but page views on multilingual projects like meta and commons are different because these sites rely heavily on user language to display content in it. A few examples:
+
+
+  - File description pages, compare https://commons.wikimedia.org/wiki/File:Sao_Paulo_Railway.jpg?uselang=en vs. https://commons.wikimedia.org/wiki/File:Sao_Paulo_Railway.jpg?uselang=fr
+  - Talk page templates, compare https://commons.wikimedia.org/wiki/Commons:Bistro?uselang=fr vs. https://commons.wikimedia.org/wiki/Commons:Bistro?uselang=en
+  - Esoteric templates, e.g. https://commons.wikimedia.org/w/index.php?title=Template:Localized_link&action=edit or even in Lua: https://commons.wikimedia.org/wiki/Module:Fallback
+
+We need to develop a strategy to mitigate thiese problems for Parsoid-based pageviews.",1419990114,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_description,open
+Parsoid page views: need to do something about {{int:}},"Handling your second question first, and picking one of the results from `grep -F '{{int:' languages/i18n/en.json` at random:
+```
+""resetpass-expired-soft"": ""Your password has expired and needs to be changed. Please choose a new password now, or click \""{{int:authprovider-resetpass-skip-label}}\"" to change it later."",
+```
+There isn't recursive expansion here.  The Parsoid output for the wikitext:
+```
+{{int:resetpass-expired-soft}}
+```
+is/will be (roughly, there are some slight tweaks coming in how the first argument of parser functions such as `int` are represented [gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/820243)):
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}' />
+ </span>
+</p>
+```
+That is, a span wrapper representing the parser function invocation, containing an empty span representing ""a localized message"" which is not expanded.
+
+This is the user-independent output which is stored in the parser cache.
+
+Later, when the content is taken out of the parser cache and postprocessed with a specific user/user language, we get:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""Skip\"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+That is, we expand the UX message completely before substituting it for the span.  This is similar to what we do for templates, which are similarly flattened when expanded in Parsoid output.
+
+This is partly an artifact of how Parsoid interacts with the legacy parser, which is still used for message parsing and template expansion.  In the future (when using Parsoid natively for message parsing) we might not flatten the output before embedding, but there's no real issue introduced by that:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""
+      <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""authprovider-resetpass-skip-label"",""params"":[]}}'>
+         Skip
+       </span>
+      \"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+
+The issue of ""wikitext occurring inside parameters"" is also similar to how that issue is handled in templates.  In general we treat parameters as raw strings, and don't represent the ""parsed"" form of the parameter in the HTML.  Visual Editor may know that some parameters are ""really"" wikitext, and can provide a rich editing widget for them; the `{{int}}` parser function will be given type hints in a similar way (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TemplateData/+/819740).
+
+For the other question, I'm not entirely sure what you mean by ""translatable template"".  Could you elaborate?",1663948453,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Handling your second question first, and picking one of the results from `grep -F '{{int:' languages/i18n/en.json` at random:
+```
+""resetpass-expired-soft"": ""Your password has expired and needs to be changed. Please choose a new password now, or click \""{{int:authprovider-resetpass-skip-label}}\"" to change it later."",
+```
+There isn't recursive expansion here.  The Parsoid output for the wikitext:
+```
+{{int:resetpass-expired-soft}}
+```
+is/will be (roughly, there are some slight tweaks coming in how the first argument of parser functions such as `int` are represented [gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/820243)):
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}' />
+ </span>
+</p>
+```
+That is, a span wrapper representing the parser function invocation, containing an empty span representing ""a localized message"" which is not expanded.
+
+This is the user-independent output which is stored in the parser cache.
+
+Later, when the content is taken out of the parser cache and postprocessed with a specific user/user language, we get:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""Skip\"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+That is, we expand the UX message completely before substituting it for the span.  This is similar to what we do for templates, which are similarly flattened when expanded in Parsoid output.
+
+This is partly an artifact of how Parsoid interacts with the legacy parser, which is still used for message parsing and template expansion.  In the future (when using Parsoid natively for message parsing) we might not flatten the output before embedding, but there's no real issue introduced by that:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""
+      <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""authprovider-resetpass-skip-label"",""params"":[]}}'>
+         Skip
+       </span>
+      \"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+
+The issue of ""wikitext occurring inside parameters"" is also similar to how that issue is handled in templates.  In general we treat parameters as raw strings, and don't represent the ""parsed"" form of the parameter in the HTML.  Visual Editor may know that some parameters are ""really"" wikitext, and can provide a rich editing widget for them; the {{int}} parser function will be given type hints in a similar way (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TemplateData/+/819740).
+
+For the other question, I'm not entirely sure what you mean by ""translatable template"".  Could you elaborate?",1663948402,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Handling your second question first, and picking one of the results from `grep -F '{{int:' languages/i18n/en.json` at random:
+```
+""resetpass-expired-soft"": ""Your password has expired and needs to be changed. Please choose a new password now, or click \""{{int:authprovider-resetpass-skip-label}}\"" to change it later."",
+```
+There isn't recursive expansion here.  The Parsoid output for the wikitext:
+```
+{{int:resetpass-expired-soft}}
+```
+is/will be (roughly, there are some slight tweaks coming in how the first argument of parser functions such as `int` are represented [gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/820243)):
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}' />
+ </span>
+</p>
+```
+That is, a span wrapper representing the parser function invocation, containing an empty span representing ""a localized message"" which is not expanded.
+
+This is the user-independent output which is stored in the parser cache.
+
+Later, when the content is taken out of the parser cache and postprocessed with a specific user/user language, we get:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""Skip\"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+That is, we expand the UX message completely before substituting it for the span.  This is similar to what we do for templates, which are similarly flattened when expanded in Parsoid output.
+
+This is partly an artifact of how Parsoid interacts with the legacy parser, which is still used for message parsing and template expansion.  In the future we might not flatten the output before embedding, but there's no real issue introduced:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""
+      <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""authprovider-resetpass-skip-label"",""params"":[]}}'>
+         Skip
+       </span>
+      \"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+
+The issue of ""wikitext occurring inside parameters"" is also similar to how that issue is handled in templates.  In general we treat parameters as raw strings, and don't represent the ""parsed"" form of the parameter in the HTML.  Visual Editor may know that some parameters are ""really"" wikitext, and can provide a rich editing widget for them; the {{int}} parser function will be given type hints in a similar way (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TemplateData/+/819740).
+
+For the other question, I'm not entirely sure what you mean by ""translatable template"".  Could you elaborate?",1663948191,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Handling your section question first, and picking one of the results from `grep -F '{{int:' languages/i18n/en.json` at random:
+```
+""resetpass-expired-soft"": ""Your password has expired and needs to be changed. Please choose a new password now, or click \""{{int:authprovider-resetpass-skip-label}}\"" to change it later."",
+```
+There isn't recursive expansion here.  The Parsoid output for the wikitext:
+```
+{{int:resetpass-expired-soft}}
+```
+is/will be (roughly, there are some slight tweaks coming in how the first argument of parser functions such as `int` are represented [gerrit](https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/820243)):
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}' />
+ </span>
+</p>
+```
+That is, a span wrapper representing the parser function invocation, containing an empty span representing ""a localized message"" which is not expanded.
+
+This is the user-independent output which is stored in the parser cache.
+
+Later, when the content is taken out of the parser cache and postprocessed with a specific user/user language, we get:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""Skip\"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+That is, we expand the UX message completely before substituting it for the span.  This is similar to what we do for templates, which are similarly flattened when expanded in Parsoid output.
+
+This is partly an artifact of how Parsoid interacts with the legacy parser, which is still used for message parsing and template expansion.  In the future we might not flatten the output before embedding, but there's no real issue introduced:
+```
+<p>
+ <span about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""parts"":[{""template"":{""target"":{""wt"":""int:resetpass-expired-soft"",""function"":""int""},""params"":{},""i"":0}}]}'>
+  <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""resetpass-expired-soft"",""params"":[]}}'>
+    Your password has expired and needs to be changed. Please choose a new password now, or click \""
+      <span typeof=""mw:I18n"" data-mw-i18n='{""/"":{""lang"":""x-user"",""key"":""authprovider-resetpass-skip-label"",""params"":[]}}'>
+         Skip
+       </span>
+      \"" to change it later.""
+  </span>
+ </span>
+</p>
+```
+
+The issue of ""wikitext occurring inside parameters"" is also similar to how that issue is handled in templates.  In general we treat parameters as raw strings, and don't represent the ""parsed"" form of the parameter in the HTML.  Visual Editor may know that some parameters are ""really"" wikitext, and can provide a rich editing widget for them; the {{int}} parser function will be given type hints in a similar way (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/TemplateData/+/819740).
+
+For the other question, I'm not entirely sure what you mean by ""translatable template"".  Could you elaborate?",1663868311,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},">>! In T85581#8245592, @cscott wrote:
+> @Tacsipacsi see https://www.mediawiki.org/wiki/Specs/HTML/2.6.0#Internationalization
+
+Thanks for the link! However, there are two issues with this spec for the translatable template use case:
+* It specifies how to set the MediaWiki message to be used for translation. However, a translatable template is not a MediaWiki message, for a reason: MediaWiki messages don’t work the wiki way – only admins and other privileged groups can edit them. This is a necessary precaution in case of interface elements, as they’re highly visible, and local editing to them is usually unnecessary anyway thanks to Translatewiki. Translatable templates, in contrast, are much less visible, so the risk is lower, but they can’t be edited on Translatewiki, so the need is higher.
+* It //doesn’t// specify the level of wikitext markup support within the messages to be used, or how to handle recursive i18n. The second example shows that simple HTML tags (`<code>` in this case) should be okay in placeholder elements, but what about more complicated constructs, like parser functions/tags, magic words or templates? Translatable templates usually build on other, often quite complicated, templates/modules. What if a translatable message itself contains something translatable? (`grep -F '{{int:' languages/i18n/en.json | wc -l` gives 32, and this is just MediaWiki core. This pattern is used every now and then in extensions as well; and it’s used all the time in translatable templates. In templates, often the inner template is translated into the user language, but the outer one falls back to English. While this may lead to mixed-language output, it makes sure that as much content is available in the user’s language as possible, so IMO it should be kept this way.) What if this translatable message containing a reference to another translatable message happens to be in an attribute? `<span>`s should not normally occur in attributes, but this use case should be supported. What if a //parameter// is, or contains, another translatable message? This is probably even more common when working with MediaWiki messages (i.e. not in the template world) than messages directly containing references to other messages.",1663691053,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"@ihurbain this is probably related to the Internationalization work done for {T309024}.
+
+@Tacsipacsi see https://www.mediawiki.org/wiki/Specs/HTML/2.6.0#Internationalization",1663600740,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},@ihurbain this is probably related to the Internationalization work done for {T309024}.,1663600657,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},">>! In T85581#951449, @GWicke wrote:
+> Some of the use cases for {{int:}} like commons metadata will probably go away soonish with the move to wikidata. The remaining ones seem to be typically individual transclusions, often really small ones (like the 'thanks' template). 
+It doesn’t mean the problem would also go away. Compare https://commons.wikimedia.org/w/index.php?title=Symphyotrichum_novi-belgii&uselang=la and https://commons.wikimedia.org/w/index.php?title=Symphyotrichum_novi-belgii&uselang=la&veaction=edit – “Basionymum” vs “Basionym”. The text is read from [[https://www.wikidata.org/wiki/Q810198|d:Q810198]], yet it changes from German to English when I open the page in VisualEditor (i.e. switch from legacy parser output to Parsoid output).
+
+>>! In T85581#7567938, @cscott wrote:
+> I think the story for Parsoid will be some general purpose markup for 'translatable content' in the main parsoid edit views path, and then a postprocessing step to do the per-user localization.
+Would that mean that the cache would contain all translations in some encoded form? It’d blow up. `{{Assessments}}` (used on the above file description page), for example, is translated into 69 languages. The description page of this particular file is probably never viewed in the majority of those languages, so currently those languages are not cached. However, if you want them to be present in an intermediate representation, they //will// be cached.",1648826327,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"I think the story for Parsoid will be some general purpose markup for 'translatable content' in the main parsoid edit views path, and then a postprocessing step to do the per-user localization.  This is still missing functionality, but {T267059} and T266666 have laid some of the groundwork.",1639434736,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},">>! In T85581#951449, @GWicke wrote:
+> I think it's worth thinking about moving more of the remaining work to the client. We could compile a list of such elements in each page after parse, and then deliver translations to be applied client-side to users who requested it. This should be a good performance win if translations are small relative to the overall page size. It would reduce the per-language storage needs on the server to fragments rather than entire pages. It might even be possible to share such fragments between pages if we can establish that the output does not depend on the actual page name.
+
+However, this will not work when {{int}} is used in esoteric templates to control transclusion.",1423001175,PHID-USER-aasrweh54ew7py3agvg2,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"@ssastry We could pass a language in as a parameter (and then forward that to expandtemplates), but would also need to store that separately, effectively replicating the current parser cache fragmentation.
+
+Some of the use cases for {{int:}} like commons metadata will probably go away soonish with the move to wikidata. The remaining ones seem to be typically individual transclusions, often really small ones (like the 'thanks' template). 
+
+I think it's worth thinking about moving more of the remaining work to the client. We could compile a list of such elements in each page after parse, and then deliver translations to be applied client-side to users who requested it. This should be a good performance win if translations are small relative to the overall page size. It would reduce the per-language storage needs on the server to fragments rather than entire pages. It might even be possible to share such fragments between pages if we can establish that the output does not depend on the actual page name.
+
+In any case, I think the current result of returning the content language is tolerable in the short term. There are bigger issues to tackle right now.",1420065446,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"@ssastry We could pass a language in as a parameter, but would also need to store that separately, effectively replicating the current parser cache fragmentation.
+
+Some of the use cases for {{int:}} like commons metadata will probably go away soonish with the move to wikidata. The remaining ones seem to be typically individual transclusions, often really small ones (like the 'thanks' template). 
+
+I think it's worth thinking about moving more of the remaining work to the client. We could compile a list of such elements in each page after parse, and then deliver translations to be applied client-side to users who requested it. This should be a good performance win if translations are small relative to the overall page size. It would reduce the per-language storage needs on the server to fragments rather than entire pages. It might even be possible to share such fragments between pages if we can establish that the output does not depend on the actual page name.
+
+In any case, I think the current result of returning the content language is tolerable in the short term. There are bigger issues to tackle right now.",1420065398,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Parsoid page views: need to do something about {{int:}},"Hmm .. interesting ... this could be tricky. How do we get user state into the parsing because without user state, it will return the default lang.
+
+```
+[subbu@earth lib] echo ""{{int:lang}}"" | node parse --normalize --dump tplsrc --prefix commonswiki
+=================================
+pf_int
+---------------------------------
+en
+---------------------------------
+
+<p>en</p>
+```",1420064873,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-uoqsiopafkhtpu2r5hem,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"Pasting from Excel into Chrome works.  Highlighting that content in Chrome and then pasting it into IE works.
+
+Pasting the content straight from Excel into IE11 doesn't work.
+
+How can I enable pasting straight from Excel?",1419973446,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-fddzs2tnied2swcs624k,task_description,invalid
+Pasting Excel cells into Internet Explorer doesn't work,IE11 is no longer supported.,1681402595,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,Reported: T228010,1563177232,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"Broken with Firefox, too.
+
+If I paste from Excel while editing a page in VE in Firefox, it's not pasted as a table at all, but just as text. If I paste into Chrome, it's pasted as table cells.
+
+If I paste from Google Spreadsheets into Firefox, it also works.
+
+Should it be a separate task?",1563176443,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,Not getting any crazy font tags with Excel2016 + Edge12.,1457452953,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,Appears to work with Excel2016 + Edge12.,1457452916,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"No, I was right.  I just removed all <font> tags and their children.",1420075603,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"hrm.... maybe I was wrong.  looks like it is already stripped by this point.
+",1420069459,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"Tracked down to a call in ve.js: ve.createDocumentFromHtml.
+
+Using my trusty console.log() -- who needs a debugger!?! -- I saw that before this call the text I want is there, but after it isn't:
+
+			// If there were no problems, let CE do its sanitizing as it may
+			// contain all sorts of horrible metadata (head tags etc.)
+			// TODO: IE will always take this path, and so may have bugs with span unwapping
+			// in edge cases (e.g. pasting a single MWReference)
+			htmlDoc = ve.createDocumentFromHtml( this.$pasteTarget.html() );
+",1420068558,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"From IRC:
+
+  <edsanders> hexmode, paste sanitization happens in
+            ve.ce.Surface.prototype.beforePaste
+  <edsanders> ve.ce.Surface.prototype.afterPaste
+  <edsanders> and ve.dm.ElementLinearData.prototype.sanitize
+  <edsanders> we have sanitization rules
+  <edsanders> which are strict for MediaWiki and loose for VisualEditor core
+",1420067366,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"I'll have to take a look at how the converter is handling it at the moment to see how to fix it, but I'm on holiday at the moment.",1419983538,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"So, how do I strip it?  Where would I put that in the VE code?",1419979075,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,Wow that IE html is bad. Font tags as a child of table!,1419979014,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"Sorry for being an idiot -- I was pasting into the wrong box.
+
+On Chrome, I get:
+
+  <table border=""0"" cellpadding=""0"" cellspacing=""0"" width=""270"" style=""border-collapse:
+   collapse;width:203pt""><tbody><tr height=""80"" style=""height:60.0pt"">
+    <td height=""80"" align=""right"" width=""58"" style=""height:60.0pt;width:44pt"">226</td>
+    <td width=""212"" style=""width:159pt"">LexWiki</td></tr></tbody></table>
+
+
+In IE, I get:
+  <table width=""270"" style=""width: 203pt; border-collapse: collapse;"" border=""0"" cellspacing=""0"" cellpadding=""0""><font face=""Times New Roman"">
+   </font><colgroup><col width=""58"" style=""width: 44pt; mso-width-source: userset; mso-width-alt: 2121;""><font face=""Times New Roman"">
+   </font><col width=""212"" style=""width: 159pt; mso-width-source: userset; mso-width-alt: 7753;""><font face=""Times New Roman"">
+   </font><tbody><tr height=""80"" style=""height: 60pt;""><font face=""Times New Roman"">
+  
+    </font><td width=""58"" height=""80"" align=""right"" style=""border: 0px black; width: 44pt; height: 60pt; background-color: transparent;""><font face=""Calibri"">226</font></td><font face=""Times New Roman"">
+    </font><td width=""212"" style=""border: 0px black; width: 159pt; background-color: transparent;""><font face=""Calibri"">LexWiki</font></td><font face=""Times New Roman"">
+  
+   </font></tr><font face=""Times New Roman"">
+  </font></tbody></table>
+
+In FF, I get:
+
+  <table border=""0"" cellpadding=""0"" cellspacing=""0"" width=""270""><colgroup><col width=""58""><col width=""212""></colgroup><tbody><tr height=""80"">
+    <td style=""height:60.0pt;width:44pt"" align=""right"" height=""80"" width=""58"">226</td>
+    <td style=""width:159pt"" width=""212"">LexWiki</td>
+  </tr></tbody></table>
+",1419978835,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,"It doesn't seem to matter which browser I use.  Chrome, FF, and IE all give: ""226 LexWiki ""
+
+Pasting the same thing into a VE page on chrome gives a table with two cells.",1419974167,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Pasting Excel cells into Internet Explorer doesn't work,What HTML do you get if you past into a CE box? http://edg2s.github.io/content-editable-sandbox/,1419973695,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fddzs2tnied2swcs624k,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"This is similar to T53472.
+
+Some languages or writing systems require combining diacritics.
+In theory most characters with diacritics can be input with combining diacritics, for example é (e + combining acute) is equivalent to é (eacute). **For some combinations in some languages only the use of combining diacritics is possible, for exemple ɔ́ (open o + combining acute).**
+
+When typing or pasting text with combining diacritics the following occurs:
+  - the first character after a combining diacritics is duplicated on a new line below the cursor.
+  - pressing backspace pushes the characters after the first combining diacritics to that line below, the cursor jumps to the end of the newline and the first character that was duplicated jumps behind the cursor as well.
+  - pressing backspace gets stuck a the combining diacritics, erasing the duplicated character last, after the characters that jumped and the line return but not erasing the combining diacritics and its base character.
+
+For example, typing
+
+```
+té
+```
+is fine.
+But typing other characters becomes:
+
+```
+tél
+l
+```
+then
+
+```
+télévision
+l
+```
+
+Pressing backspace with the cursor at the end of the first line:
+
+```
+té
+élvisio
+```
+with the cursor before the o, but the next backspace will delete the o and the cursor jumps before the i.
+
+The expected result should be the word ""télévision"" and pressing backspace should delete the character before the cursor or the character cluster before the cursor.",1419151474,PHID-USER-i5at67w766dqxs6ncxam,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_description,resolved
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 456507 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (8097e44c1)
+
+[[https://gerrit.wikimedia.org/r/456507]]",1535669341,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 456509 abandoned by Jforrester:
+Update VE core submodule to master (8097e44c1)
+
+Reason:
+Bartosz pushed Ieec61133d.
+
+[[https://gerrit.wikimedia.org/r/456509]]",1535667696,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 456509 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (8097e44c1)
+
+[[https://gerrit.wikimedia.org/r/456509]]",1535667557,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 456507 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (8097e44c1)
+
+[[https://gerrit.wikimedia.org/r/456507]]",1535667455,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 451669 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] ve.dm.Document: Remove incorrect handling for combining characters in #fixupInsertion
+
+[[https://gerrit.wikimedia.org/r/451669]]",1535665072,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"If you want to test this and can't easily insert combining characters from the keyboard, here is a U+0301 Combining Acute Accent for your copy-paste convenience:
+
+`́`
+
+Tasks T182404 and T198719 may be duplicates of this bug (this needs to be tested).",1533836066,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"Change 451669 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[VisualEditor/VisualEditor@master] [WIP] ve.dm.Document: Remove incorrect handling for combining characters in #fixupInsertion
+
+[[https://gerrit.wikimedia.org/r/451669]]",1533835960,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,Also impacts Flow.,1477073412,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters,"I could see the issue for diacritics characters that are entered with Shift key(both in production and betalabs):
+
+For example, using 'US extended' keyboard, 
+1) type t, after t type e
+2) then use Option+Shift+e to apply an accent mark to e,
+3)  type l (letter 'el')
+
+tél
+l
+
+Then the letter l will be duplicated and placed on the next line. There will be some issues with deleting as described.
+
+Note: Entering so called precomposed diactrics characters does not seem to present an issue. Additional info at:
+http://superuser.com/questions/339359/insert-a-character-with-multiple-accents-on-an-extended-mac-keyboard-layout
+
+
+ ",1419292625,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-juwxek3lh7qnt55hfhfo,task_subcomment,NA
+Text in Templates is not found by VisualEditor's Find / Search,"Found when investigating T62451 - a page consists entirely of text entered via Templates fields: https://pt.wikibooks.org/w/index.php?title=C%C3%A1lculo_(Volume_1)/An%C3%A1lise_de_fun%C3%A7%C3%B5es_elementares_(2)&redirect=no&veaction=edit 
+
+Text is not searchable via VE Find, but can be searched via browser Find.",1418936627,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-hvyzq7c5neh3uqybtctf,task_description,duplicate
+convert the RTL blocking bug T2745 into a tag,"The RTL blocking/tracking bug T2745 can be converted into a Phabricator tag.
+
+It also has some ""sub-tracker"" bugs, for example T35126, which is for RTL bugs in VisualEditor. These can eliminated as well. They should have the RTL tag and the appropriate project tag.",1418744270,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_description,resolved
+convert the RTL blocking bug T2745 into a tag,"Requested project #RTL has been created: https://phabricator.wikimedia.org/project/profile/1280/
+
+T2745 has been updated accordingly and closed as declined.
+
+Please encourage interested people to visit the project and to join the project as {icon users} members, and to [[ https://www.mediawiki.org/wiki/Phabricator/Help#Receiving_updates_and_notifications | subscribe themselves to the project ]] in order to receive updates!
+
+[[ https://www.mediawiki.org/wiki/Phabricator/Project_management | Recommended practices for project and workboard management in Phabricator ]] are available.
+
+And if for some reason you ever want to rename the project, please check [[ https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Renaming_projects | the guidelines ]] first.
+
+I also created H32 for automatically adding #i18n to #RTL tasks.
+
+Enjoy!",1433255137,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,">>! In T78670#1325274, @Aklapper wrote:
+> My remaining question still stands:
+>> We can make Herald automatically add the #i18n tag whenever a future #RTL tag is added to a task. Does that sound reasonable?
+> 
+> Someone please answer.
+
+Yes.",1433162289,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,"My remaining question still stands:
+> We can make Herald automatically add the #i18n tag whenever a future #RTL tag is added to a task. Does that sound reasonable?
+
+Someone please answer.",1433156310,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,"We can make Herald set the #i18n tag whenever a future #RTL tag is added to a task. Does that sound reasonable?
+
+BiDi could be an additional hashtag.
+
+For converting tracking tasks to projects there is now [[ https://www.mediawiki.org/wiki/Phabricator/Project_management/Tracking_tasks | documentation ]] available.",1425053100,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,">>! In T78670#936776, @Aklapper wrote:
+> Any naming proposal? ""RTL-bidirectional"" or such? Tag project description text could link to https://www.mediawiki.org/wiki/Directionality_support ?
+
+Just ""RTL"" or ""bidi"" should be enough, if it's possible to make something very short.
+
+Linking to https://www.mediawiki.org/wiki/Directionality_support is OK.
+
+> And I've always wondered (already in Bugzilla) how this collides or not with the existing i18n tag - is RTL always a subset of i18n?
+
+Indeed, all RTL bugs are i18n bugs, but i18n includes many more topics. If there is a way to organize a hierarchy of bugs that will automatically infer that all RTL bugs are i18n bugs, it would be a nice thing to have.
+
+RTL could be a Bugzilla tag like i18n is from the start, but somehow RTL issues ended up being tracked by a blocking bug. Now would be a good time to clean that up :)",1419071629,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,">>! In T78670#936776, @Aklapper wrote:
+> I like the idea but converting looks rather cumbersome, see my general comment in T75703#936775.
+
+https://phabricator.wikimedia.org/maniphest/query/bKU3kGuAWKFB/#R  :)",1419022517,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,">>! In T78670#936776, @Aklapper wrote:
+> I like the idea but converting looks rather cumbersome, see my general comment in T75703#936775.
+
+https://phabricator.wikimedia.org/maniphest/query/stlzyr5F2Ks3/#R  :)",1419021897,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+convert the RTL blocking bug T2745 into a tag,"I like the idea but converting looks rather cumbersome, see my general comment in T75703#936775.
+
+Any naming proposal? ""RTL-bidirectional"" or such? Tag project description text could link to https://www.mediawiki.org/wiki/Directionality_support ?
+
+And I've always wondered (already in Bugzilla) how this collides or not with the existing i18n tag - is RTL always a subset of i18n?",1419018095,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5m5zlkgduk4k4cvtcijk,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"The screenshots that are uploaded by the latest builds of the VisualEditor language screenshot job have pixelated fonts.
+
+Compare:
+* Current, pixelated: https://upload.wikimedia.org/wikipedia/commons/f/fe/VisualEditor_Toolbar_Headings-en.png
+* Older, non-pixelated: https://upload.wikimedia.org/wikipedia/commons/archive/f/fe/20141203163056!VisualEditor_Toolbar_Headings-en.png
+
+This may be happening because on the clients where the test jobs run there is a problem with the screen driver or maybe fonts anti-aliasing is disabled. Either the configuration of this client machines must be fixed, or the tests must run on a different platform, maybe Mac. (But it must be tested that they have fonts for all the languages, in particular Arabic, Japanese and Hebrew.)",1418732838,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_description,resolved
+VisualEditor language screenshots come out with pixelated fonts,"Change 184587 merged by jenkins-bot:
+Deleted Jenkins job that was running VisualEditor screenshots using a local browser
+
+[[https://gerrit.wikimedia.org/r/184587]]",1421143290,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"Change 184587 had a related patch set uploaded (by Zfilipin):
+Deleted Jenkins job that was running VisualEditor screenshots using a local browser
+
+[[https://gerrit.wikimedia.org/r/184587]]
+
+#patch-for-review",1421142699,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"Change 183480 merged by jenkins-bot:
+Run VisualEditor screenshot job on a Mac
+
+[[https://gerrit.wikimedia.org/r/183480]]",1421142263,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"This patch fixes the pixelation. Thank you. When it's merged and the new non-pixelated screenshots are uploaded to Commons, this bug can be marked as resolved.",1420724515,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor language screenshots come out with pixelated fonts,"Change 183480 had a related patch set uploaded (by Zfilipin):
+Run VisualEditor screenshot job on a Mac
+
+[[https://gerrit.wikimedia.org/r/183480]]
+
+#patch-for-review",1420717978,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4rdwdflxn4nfr6u6rtjg,task_subcomment,NA
+VisualEditor screenshots-taking tests should link to the job that uploaded them from the file description page,VisualEditor screenshots-taking tests (currently language_screenshots.feature) upload the files to Commons. It would be useful to have a link from the file description page to the Jenkins job that uploaded the file so it would be easier to debug the problems in it if there are any.,1418732537,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-msm6dhxj4earcc46fnei,task_description,open
+make-wmf-branch doesn't play nice with existing extension branches,"```
+'git' 'clone' '-q' 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git' 'VisualEditor'
+Total 73708 (delta 49816), reused 73204 (delta 49799)
+cd VisualEditor
+'git' 'checkout' '-q' '-b' 'wmf/1.25wmf12'
+'git' 'commit' '-a' '-q' '-m' 'Creating new wmf/1.25wmf12 branch'
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+'git' 'push' 'origin' 'wmf/1.25wmf12'
+To ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git
+ ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)
+error: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'
+To prevent you from losing history, non-fast-forward updates were rejected
+Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+'Note about fast-forwards' section of 'git push --help' for details.
+sleeping for 5s
+git exit with status 1
+```",1418240952,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-5uacgwuqg3wsvpphjet4,task_description,declined
+make-wmf-branch doesn't play nice with existing extension branches,"`branch.py`, the successor to `make-wmf-branches` and `make-extension-branches` handles this. Declining as the titular script is EOL.",1526375741,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-5uacgwuqg3wsvpphjet4,task_subcomment,NA
+make-wmf-branch doesn't play nice with existing extension branches,`make-extension-branches` skips when the branch already exists; we should probably duplicate that code.,1418241372,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5uacgwuqg3wsvpphjet4,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I tried to set up the MediaWiki Vagrant environment according to the steps described here: http://www.mediawiki.org/wiki/MediaWiki-Vagrant 
+I used the most current VirtualBox and Vagrant.
+When I tried to do vagrant up: mount.nfs: access denied by server while mounting. 
+
+Find the complete error here: {F20641}",1418226811,PHID-USER-pxdyvyvhcyeu5efcjcgj,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_description,declined
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","Declining for now per inactivity and the task being filed in 2014 with Ubuntu 14, which is a long time ago now.",1624383762,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#841751, @Mvolz wrote:
+> I have full disk encryption, but vagrant used to work for me (about 6 months ago?) and it's the same computer although I'm now on 14.04 instead of 13.* , since then- is this a new thing, that it's known not to work on fully encrypted disks but just on Trusty Tahr specifically?
+
+I'm using Vagrant and NFS with full disk encryption (not home directory).  However, I'm on Debian.",1504035811,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003
+
+**EDIT:** Spoke too soon again. If NFS is enabled the initial provisioning hangs on
+    ==> default: Notice: /Stage[main]/Apt/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+
+**EDIT2:** When NFS shares were off, I got LXC to work on Fedora 25. (they happened to be off when I set up LXC; I don't know what would happen if it was enabled on initial provisioning) NFS worked after reenabling NFS shares, but I felt LXC was faster without NFS, so I turned it back off.
+",1480901786,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003
+
+**EDIT:** Spoke too soon again. If NFS is enabled the initial provisioning hangs on
+    ==> default: Notice: /Stage[main]/Apt/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+
+**EDIT2:** After turning off NFS shares, I got LXC to work on Fedora 25. NFS worked after reenabling NFS shares, but I felt LXC was faster without NFS, so I turned it back off.
+",1480901745,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+~~When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:~~
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003
+
+**EDIT:** Spoke too soon again. If NFS is enabled the initial provisioning hangs on
+    ==> default: Notice: /Stage[main]/Apt/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+
+
+",1480894570,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+~~When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:~~
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+~~ from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003 ~~
+
+Spoke too soon again. If NFS is enabled the initial provisioning hangs on
+    ==> default: Notice: /Stage[main]/Apt/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as '{md5}53ce69211afabdf3f0123353515e80f4'
+
+
+",1480894512,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#846323, @Sn1per wrote:
+> 'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.
+
+When using libvirt on Fedora 25, I managed to get NFS to work by setting the following firewall settings:
+> Example for easily configuring firewalld using the ""firewall-config"" GUI:
+> 
+> choose ""Configuration: Permanent"" from the drop down menu
+> select the zone you want to modify (i chose ""internal"").
+> go to the ""Interfaces"" tab, assign vboxnet0 (or other host-only adapter) to the zone.
+> go to the ""Services"" tab, check ""mountd"", ""nfs"" and ""rpc-bind""
+> go to the global ""Services"" tab (next to ""Zones""), select NFS and add Port 2049 UDP (only TCP is predefined).
+> Finally choose ""Options/Reload Firewalld"".
+> NFS mounts now work correctly from within the VM and you can leave firewalld enabled.
+
+
+from https://github.com/mitchellh/vagrant/issues/2447#issuecomment-27763003
+
+",1480879453,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I just encountered the same issue on Lubuntu 15.10 (Vagrant 1.8.1, VirtualBox 5.0.16 r105871).
+
+Using `vagrant config nfs_shares off` solved it for me",1459503528,PHID-USER-m7etbwqrv6cfrg5ymrwx,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",I just encountered the same issue on Lubuntu 15.10 (Vagrant 1.8.1 ,1459503431,PHID-USER-m7etbwqrv6cfrg5ymrwx,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I'm getting the same mount.nfs: access denied by server while mounting error.
+
+",1449213525,PHID-USER-ie5zvlm4dg5baq5cgxu4,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I'm getting a similar NFS 'access denied' on Fedora 23 alpha, no disk or home-dir encryption:
+
+{F1567690}",1439824812,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",I wonder if there is a way we can detect the use of ecryptfs and either give a better error message/warning to the user or just automatically disable nfs like we do for Windows.,1418502257,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",'access denied' also happens on unencrypted Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.,1418502344,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",'access denied' also happens on Fedora 21 with vagrant 1.7.1 and virtualbox 4.3.20.  Turning off NFS allows it to work.,1418501870,PHID-USER-pdlnbp2w5h2rej2hikwj,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#841751, @Mvolz wrote:
+> Additional info:
+> 
+> I have full disk encryption, but vagrant used to work for me (about 6 months ago?) and it's the same computer although I'm now on 14.04 instead of 13.* , since then- is this a new thing, that it's known not to work on fully encrypted disks but just on Trusty Tahr specifically?
+
+NFS was made the default disk sharing option on 2014-05-23 (<https://gerrit.wikimedia.org/r/#/c/134995/>).  The ability to easily turn this off due to encryption was added on 2014-08-14 (<https://gerrit.wikimedia.org/r/#/c/154153/>).
+
+> I was able to complete vagrant up with NFS shares off, but unfortunately still with errors. 
+> 
+> While there is a server running at http://127.0.0.1:8080/ I get File not found: /vagrant/mediawiki/index.php. Alas! 
+> 
+> Output of vagrant up:
+> 
+> Stderr from the command:
+> 
+> stdin: is not a tty
+> Error: composer install --optimize-autoloader returned 1 instead of one of [0]
+
+This composer failure looks to be the root cause of the rest of the failures. Running `PUPPET_DEBUG=1 vagrant provision | tee puppet.log` or manually running `composer install --optimize-autoloader` in /vagrant/mediawiki may lead to more information on the reason for this failure.",1418315007,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","Additional info:
+
+I have full disk encryption, but vagrant used to work for me (about 6 months ago?) and it's the same computer although I'm now on 14.04 instead of 13.* , since then- is this a new thing, that it's known not to work on fully encrypted disks but just on Trusty Tahr specifically?
+
+I was able to complete vagrant up with NFS shares off, but unfortunately still with errors. 
+
+While there is a server running at http://127.0.0.1:8080/ I get File not found: /vagrant/mediawiki/index.php. Alas! 
+
+Output of vagrant up:
+
+Stderr from the command:
+
+stdin: is not a tty
+Error: composer install --optimize-autoloader returned 1 instead of one of [0]
+Error: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: change from notrun to 0 failed: composer install --optimize-autoloader returned 1 instead of one of [0]
+Error: /usr/local/bin/multiversion-install wiki admin --dbname wiki --dbpass vagrant --dbuser root --pass vagrant --scriptpath /w --server http://127.0.0.1:8080 --confpath /vagrant/settings.d/wikis/wiki 
+ returned 1 instead of one of [0]
+Error: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_setup]/returns: change from notrun to 0 failed: /usr/local/bin/multiversion-install wiki admin --dbname wiki --dbpass vagrant --dbuser root --pass vagrant --scriptpath /w --server http://127.0.0.1:8080 --confpath /vagrant/settings.d/wikis/wiki 
+ returned 1 instead of one of [0]
+Warning: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_include_extra_settings]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Mediawiki::Extension::Browsertests[VisualEditor]/Browsertests::Bundle[VisualEditor_browsertests_bundle]/Ruby::Bundle[VisualEditor_browsertests_bundle]/File[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/.bundle/config]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Mediawiki::Extension::Browsertests[VisualEditor]/Browsertests::Bundle[VisualEditor_browsertests_bundle]/Ruby::Bundle[VisualEditor_browsertests_bundle]/Exec[bundle_install_VisualEditor_browsertests_bundle]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Codeeditor/Mediawiki::Extension[CodeEditor]/Git::Clone[mediawiki/extensions/CodeEditor]/Exec[git_clone_mediawiki/extensions/CodeEditor]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Parserfunctions/Mediawiki::Extension[ParserFunctions]/Git::Clone[mediawiki/extensions/ParserFunctions]/Exec[git_clone_mediawiki/extensions/ParserFunctions]: Skipping because of failed dependencies
+Warning: /Stage[main]/Mediawiki/Exec[copy_LocalSettings]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Cite/Mediawiki::Extension[Cite]/Git::Clone[mediawiki/extensions/Cite]/Exec[git_clone_mediawiki/extensions/Cite]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Git::Clone[mediawiki/extensions/VisualEditor]/Exec[git_clone_mediawiki/extensions/VisualEditor]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Templatedata/Mediawiki::Extension[TemplateData]/Git::Clone[mediawiki/extensions/TemplateData]/Exec[git_clone_mediawiki/extensions/TemplateData]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Wikieditor/Mediawiki::Extension[WikiEditor]/Git::Clone[mediawiki/extensions/WikiEditor]/Exec[git_clone_mediawiki/extensions/WikiEditor]: Skipping because of failed dependencies
+Warning: /Stage[main]/Browsertests/Mediawiki::User[Selenium_user]/Exec[mediawiki_user_Selenium_user]: Skipping because of failed dependencies
+Warning: /Stage[main]/Mediawiki::Parsoid/Mediawiki::Extension[Parsoid]/Git::Clone[mediawiki/extensions/Parsoid]/Exec[git_clone_mediawiki/extensions/Parsoid]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Geshi/Mediawiki::Extension[SyntaxHighlight_GeSHi]/Git::Clone[mediawiki/extensions/SyntaxHighlight_GeSHi]/Exec[git_clone_mediawiki/extensions/SyntaxHighlight_GeSHi]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Wikieditor/Mediawiki::Extension[WikiEditor]/Mediawiki::Settings[WikiEditor]/File[/vagrant/settings.d/puppet-managed/10-WikiEditor.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Codeeditor/Mediawiki::Extension[CodeEditor]/Mediawiki::Settings[CodeEditor]/File[/vagrant/settings.d/puppet-managed/10-CodeEditor.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Cite/Mediawiki::Extension[Cite]/Mediawiki::Settings[Cite]/File[/vagrant/settings.d/puppet-managed/10-Cite.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Mediawiki::Settings[VisualEditor]/File[/vagrant/settings.d/puppet-managed/10-VisualEditor.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Templatedata/Mediawiki::Extension[TemplateData]/Mediawiki::Settings[TemplateData]/File[/vagrant/settings.d/puppet-managed/10-TemplateData.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Geshi/Mediawiki::Extension[SyntaxHighlight_GeSHi]/Mediawiki::Settings[SyntaxHighlight_GeSHi]/File[/vagrant/settings.d/puppet-managed/10-SyntaxHighlight_GeSHi.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Parserfunctions/Mediawiki::Extension[ParserFunctions]/Mediawiki::Settings[ParserFunctions]/File[/vagrant/settings.d/puppet-managed/10-ParserFunctions.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Mediawiki::Parsoid/Mediawiki::Extension[Parsoid]/Mediawiki::Settings[Parsoid]/File[/vagrant/settings.d/puppet-managed/10-Parsoid.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Scribunto/Mediawiki::Extension[Scribunto]/Git::Clone[mediawiki/extensions/Scribunto]/Exec[git_clone_mediawiki/extensions/Scribunto]: Skipping because of failed dependencies
+Warning: /Stage[main]/Role::Scribunto/Mediawiki::Extension[Scribunto]/Mediawiki::Settings[Scribunto]/File[/vagrant/settings.d/puppet-managed/10-Scribunto.php]: Skipping because of failed dependencies
+Warning: /Stage[main]/Mediawiki::Jobrunner/Service[jobrunner]: Skipping because of failed dependencies
+Warning: /Stage[main]/Apache/Service[apache2]: Skipping because of failed dependencies
+
+
+
+",1418310778,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","Sputniza, does doing
+
+vagrant config nfs_shares off
+
+then
+
+vagrant reload
+
+Work for you? ",1418300540,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04",">>! In T78153#837045, @Mvolz wrote:
+> exportfs: /home/marielle/Code/vagrant does not support NFS export
+
+This last error message sounds like /home/marielle is an encrypted partition. The only fix for this is to disable the use of nfs for your Vagrant shares. We have a command in our plugin that makes that pretty easy: `vagrant config nfs_shares off`",1418230398,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I am getting the same error on Ubuntu 14.04 with the most recent version of vagrant and virtualbox 4.3.12r93733
+
+nfsd running
+exportfs: duplicated export entries:
+exportfs: 	10.11.12.13:/home/marielle/Code/vagrant
+exportfs: 	10.11.12.13:/home/marielle/Code/vagrant
+exportfs: /home/marielle/Code/vagrant does not support NFS export
+
+default: Mounting NFS shared folders...
+The following SSH command responded with a non-zero exit status.
+Vagrant assumes that this means the command failed!
+
+mount -o 'noatime,rsize=32767,wsize=32767,async' 10.11.12.1:'/home/marielle/Code/vagrant' /vagrant
+
+Stdout from the command:
+
+
+
+Stderr from the command:
+
+stdin: is not a tty
+mount.nfs: access denied by server while mounting 10.11.12.1:/home/marielle/Code/vagrant
+",1418227215,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+"error on doing vagrant up ""mount.nfs: access denied by server while mounting"" in ubuntu 14.04","I am getting the same error on Ubuntu 14.04 with the most recent version of vagrant:
+
+nfsd running
+exportfs: duplicated export entries:
+exportfs: 	10.11.12.13:/home/marielle/Code/vagrant
+exportfs: 	10.11.12.13:/home/marielle/Code/vagrant
+exportfs: /home/marielle/Code/vagrant does not support NFS export
+==> default: Mounting NFS shared folders...
+The following SSH command responded with a non-zero exit status.
+Vagrant assumes that this means the command failed!
+
+mount -o 'noatime,rsize=32767,wsize=32767,async' 10.11.12.1:'/home/marielle/Code/vagrant' /vagrant
+
+Stdout from the command:
+
+
+
+Stderr from the command:
+
+stdin: is not a tty
+mount.nfs: access denied by server while mounting 10.11.12.1:/home/marielle/Code/vagrant
+",1418227076,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-p72kac32ipfr5e6rjj23,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"Due to a combination of factors, we haven't been able to line up a good mentorship for @memeht in the #Performance-Metrics-Dashboard project yet. This has caused a delay in her start on this program. This needs to be solved urgently. @Qgil is working on this. ",1418208428,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-xgh4sxdhab2hhybxk42k,task_description,resolved
+Sort out Performance Metrics Dashboard mentorship,"@Memeht is now more than busy with @ssastry and @jdforrester-wmf. I will continue acting as ""generic mentor"". This task is resolved now. Thank you Chrsity for your patience, and thank you Subbu and James for stepping in!",1421403221,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"Yesterday @Memeht and I had our weekly meeting. She is busy with tasks, she has questions that can find answers in the Analytics mailing list and the Parsoid IRC channel. I'm supporting her as generic mentor for now, but this is a task that I'm doing reactively when she has questions. I think this is going as good as it could during the Winter holidays, considering the situation in which we were just ten days ago.  :)",1419930584,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"@Jdforrester-wmf has volunteered to find a project for @memeht and mentor her, as soon as he is back from vacation in January. In the meantime, he proposed this task: {T84949}
+
+For the period between now and James' return, @ssastry has created {T85232}, a task that he is happy to mentor.
+
+While these tasks were defined, I started the routing of weekly meetings with Christy, and I also pointed her to look at [[ https://www.mediawiki.org/wiki/Annoying_little_bugs | annoying little bugs ]], in the case she finished with the interim work.
+
+The situation is far from ideal, but I'm personally happy for having reached to this point during these pre-holidays dates, and I'm very thankful for Subbu's and James' help.",1419359486,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"@Memeht, altough it is being extremely difficult to find a mentor available in these pre-vacation days, we are narrowing down the area where your work is welcome: improving the metrics for VisualEditor, a key feature in the modernization of Wikipedia and wiki editing in general. Here you have some pointers:
+
+* https://www.mediawiki.org/wiki/Editing (note that two former interns work in this team, @mvolz and @MSchottlender-WMF)
+* https://www.mediawiki.org/wiki/VisualEditor (check ""Statistics"" under ""See also"")
+* https://www.mediawiki.org/wiki/Editing_performance
+
+I will create some tasks under #Performance-Metrics-Dashboard",1418947048,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+Sort out Performance Metrics Dashboard mentorship,"@Memeht, altough it is being extremely difficult to find a mentor available in these pre-vacation days, we are narrowing down the area where your work is welcome: improving the metrics for VisualEditor, a key feature in the modernization of Wikipedia and wiki editing in general. Here you have some pointers:
+
+* https://www.mediawiki.org/wiki/Editing (note that two former interns work in this team, @mvolz and @MSchottlender-WMF)
+* https://www.mediawiki.org/wiki/VisualEditor (check ""Statistics"" under ""See also"")
+* https://www.mediawiki.org/wiki/Editing_performance
+
+I will create some tasks under #Performance-Metrics-Dashboard
+
+<James_F> edit-reportcard.wmflabs.org needs lots of work.
+<James_F> But it will take 3–4 hours for me to specify what might be good there.
+<James_F> Saying ""make it better"" isn't helpful for her, I imagine.
+<James_F> https://phabricator.wikimedia.org/T84926 and https://phabricator.wikimedia.org/T84927 are very basic starts.",1418946148,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-xgh4sxdhab2hhybxk42k,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","Steps to reproduce:
+
+1. Set language to Indonesian (id).
+2. Open page in VisualEditor.
+3. Insert a table, or select an existing one.
+4. Click on the ""▾"" (down arrow) indicator next to the first cell.
+5. Notice that the words end with … rather than spelling out the entire text.
+
+Proposed solution:  Make the menu wider, because some languages require more space than English.
+",1418189274,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-55xswnakobrdktp5xg5z,task_description,resolved
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","Change 236871 merged by jenkins-bot:
+Slightly increase width of table context
+
+[[https://gerrit.wikimedia.org/r/236871]]",1441743811,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","Change 236871 had a related patch set uploaded (by Esanders):
+Slightly increase width of table context
+
+[[https://gerrit.wikimedia.org/r/236871]]
+",1441741345,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)",Think this is now resolved. Tried fr/pl/de/id/etc. and they all seemed to work.,1441740277,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)",Could anybody provide a pointer to the corresponding LESS file(s) so someone could give this a shot? Cannot find the right place. Thanks.,1437052509,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","Could anybody provide a pointer to the corresponding LESS file(s)? 
+I'm kind of curious if I can fix this but cannot find the right place. Thanks :)",1429645479,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+"Menu items in table popup widget (e.g. ""Insert before"") truncated in most languages (box not wide enough)","The three options are truncated in most languages I tried in Firefox 36:
+{F55266}
+Still wondering what exactly in oojs-ui makes it calculate
+```<div style=""height: auto; margin-left: -29.5px; width: 150px;"" class=""oo-ui-popupWidget-popup"">```
+(someone with more LESS skills could provide a pointer please?). 
+Not defining/calculating a ""width"" value would solve the problem (but would it create others? Don't think so).",1425512492,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-55xswnakobrdktp5xg5z,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"See screenshot:
+
+{F20260}",1418156016,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_description,resolved
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"Change 179551 merged by jenkins-bot:
+Hide extra space at the top of the single transclusion dialogs
+
+[[https://gerrit.wikimedia.org/r/179551]]",1422924744,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"The transitions are currently broken, and I think a bit OTT given we are transitioning the width of the entire dialog. I suggest just display:none-ing them.",1422662415,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"Change 179551 had a related patch set uploaded (by Alex Monk):
+Hide extra space at the top of the single transclusion dialogs
+
+[[https://gerrit.wikimedia.org/r/179551]]
+
+#patch-for-review",1418418129,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"It's because of how we try to hide the template page label on single transclusion dialogs (e.g. templates, citations): https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/45518019eb8b668df42a5b3886be8031f578fdee/modules/ve-mw/ui/styles/dialogs/ve.ui.MWTransclusionDialog.css#L55-L61
+
+We use all of that instead of display:none so we can fade it out (see transition lines above).
+
+Just need to work out why it still takes up room.",1418336451,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+Extra space before the start of the citation/template (not multiple transclusion) dialog contents,"Seems the same in Apex to me. It's a hidden oo-ui-labelElement-label containing the template name, above the template page description.",1418327934,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-lrc5z5oojaqr6d5oluvr,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"https://wikimediafoundation.org/w/index.php?title=Special:Search&search=please%20check%20back&fulltext=Search&profile=all
+
+The search results here include files from Wikimedia Commons. This is kind of weird. It might be helpful if the Commons search results are of media that's actively used/referenced on the local wiki, but otherwise it's just kind of strange and unexpected to include a foreign wiki's search results alongside the local wiki's, especially without a clear opt-out mechanism.
+
+See also: {T94856}",1417909769,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_description,resolved
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"Thanks for the deploy, @Krenair and @ThCipriani. Closing as resolved.",1441035308,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1589458, @Jdforrester-WMF wrote:
+> Oh, interesting. When? This probably explains the complete breakage of media inserting on officewiki we had to fix a few weeks ago… 
+
+It was done in [[https://gerrit.wikimedia.org/r/#/c/204536/|this patch]], so April 2015.",1441035254,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1576570, @Deskana wrote:
+>>>! In T76957#1576565, @Jdforrester-WMF wrote:
+>> Won't this break VisualEditor for inserting images on Foundationwiki?
+> 
+> Inserting images from Commons using VisualEditor seems to work just fine on officewiki, and officewiki already had this config change applied to it.
+
+Oh, interesting. When? This probably explains the complete breakage of media inserting on officewiki we had to fix a few weeks ago… 
+",1441035072,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"Change 234040 merged by jenkins-bot:
+Remove files from Commons from search results on wikimediafoundation.org
+
+[[https://gerrit.wikimedia.org/r/234040]]",1441034644,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1576565, @Jdforrester-WMF wrote:
+> Won't this break VisualEditor for inserting images on Foundationwiki?
+
+No, what VE does is look up the actual file repositories set up on the local wiki and searches each one separately, I don't think it relies on local search to include foreign file repository results.",1440617366,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1576565, @Jdforrester-WMF wrote:
+> Won't this break VisualEditor for inserting images on Foundationwiki?
+
+No, what VE does is look up the actual file backends set up on the local wiki and searches each one separately, I don't think it relies on the local search backend to include foreign repository results.",1440617330,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1576565, @Jdforrester-WMF wrote:
+> Won't this break VisualEditor for inserting images on Foundationwiki?
+
+Inserting images from Commons using VisualEditor seems to work just fine on officewiki, and officewiki already had this config change applied to it. Given that, I find it unlikely that this will affect VisualEditor on foundationwiki.",1440615698,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,Won't this break VisualEditor for inserting images on Foundationwiki?,1440615464,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"Change 234040 had a related patch set uploaded (by Deskana):
+Remove files from Commons from search results on wikimediafoundation.org
+
+[[https://gerrit.wikimedia.org/r/234040]]
+",1440615300,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,">>! In T76957#1462538, @Krenair wrote:
+> Getting community consensus on foundationwiki sounds interesting. Who needs to approve this?
+
+Well, Discovery owns search across all of our sites, and I'm the PM for Discovery, so why don't we say me? :-)",1440615156,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,Getting community consensus on foundationwiki sounds interesting. Who needs to approve this?,1437249304,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+wikimediafoundation.org search results should not include files from Wikimedia Commons,"We can now use ""file:local:cat"" for searching local files. See https://gerrit.wikimedia.org/r/#/c/204536/",1429202861,PHID-USER-lsveyqlsb4acoowxr5yj,False,PHID-TASK-gbf4krxvukazedeyc7t6,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Upstream reports: https://secure.phabricator.com/T6102 and https://secure.phabricator.com/T8510
+
+**Workaround by valhallasw: 
+Execute `JX.TypeaheadSource.prototype.setMaximumResultCount(100)` in the javascript console (or a userscript)** to get more results displayed. Userscripts at P2444 (Chrome) and P2445 (Firefox)
+
+When typing in the ""projects"" field in the ""edit task"" or ""edit search"" view, phabricator offers up to 5 suggestions/completions. But sometimes, the exact match for what I just typed is not included in this list. This makes it impossible for me to enter these projects anywhere (for me, this happens for ""wikidata"" - I see ""wikidata.org"" etc, but not ""wikidata""). Interestingly, these suggestions look different for other users (with the same input, they do get ""wikidata"", though it's only in the 4th slot), so it seems the ranking in the suggester is user-specific (projects that I am a member of get boosted, or some such). 
+
+In any case: exact matches should always win. If I enter a full name and hit enter, this should always work if a project by this name exists.
+
+I'm setting this to ""high"" since it makes it pretty much impossible for me to work with phab.
+
+PS: I suppose the same issue exists for all fields that use the suggester/tag logic, but I did not run into any problems with other fields yet.
+
+{F39253}",1417710278,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-h64673nwftdciwancqe4,task_description,resolved
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#3040513 in February 2017, @Aklapper wrote:
+> Upstream task https://secure.phabricator.com/T8510#202060 is only still open because
+> * #Maps and #Discovery entered in the global search bar aren't in first position,
+I cannot reproduce this problem anymore.
+> * The ""In Any"" and ""Not In"" options [[ https://secure.phabricator.com/T8510#200936 | are not always offered ]] for exact project name matches in the ""Tags"" field of Maniphest's Advanced Search form. **Workaround:** Explicitly write `not(wikidata)` to get `Not in: Wikidata`.
+I'd always recommend to use `not(project`) and `any(project)`.
+I documented this in https://www.mediawiki.org/w/index.php?title=Phabricator%2FSearch&type=revision&diff=2818193&oldid=2806870
+
+As I am not aware of any further problems I am closing this task as resolved.",1530265110,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Upstream task https://secure.phabricator.com/T8510#202060 is only still open because
+* #Maps and #Discovery entered in the global search bar aren't in first position,
+* The ""In Any"" and ""Not In"" options [[ https://secure.phabricator.com/T8510#200936 | are not always offered ]] for exact project name matches in the ""Tags"" field of Maniphest's Advanced Search form. **Workaround:** Explicitly write `not(wikidata)` to get `Not in: Wikidata`.
+
+In general the situation has improved a lot since this task was created, hence lowering its priority.",1487596072,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I have tested with #visualeditor, which wouldn't show up before due to all the related subprojects. Now it appears in the first position. Good!",1479467748,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"In the search bar in the toolbar at the top of the screen, searching for ""Maps"" brings up Maps as the third option. Searching for ""Discovery"" brings up Discovery as the second option. 
+
+When editing a task and entering tags, autocomplete does bring up Maps and Discovery as the first items. 
+
+This task was originally filed for the editing case, so although I personally think both cases should be fixed, it seems the remaining issues should be captured in a separate task.  ",1479415206,PHID-USER-pmfo3xmfjado5j3dqmio,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"https://secure.phabricator.com/T8510#199629 states this should be pretty much resolved. 
+We're now running that version here, with an [[ https://secure.phabricator.com/rPb02f64f6eecd1d3b7b1c573f108d5a2c8f35497f | additional backported patch ]] on top. And so far it looks like a great improvement!
+
+Testing in the `Tags` field on https://phabricator.wikimedia.org/maniphest/query/advanced/ , some stuff surprised me:
+* Entering `Labs not` displays `Not In: Labs` as 4th item. 
+* Entering `labs not in` only displays `Not In: Labs-Infrastructure` but not `Not In: Labs`
+* Entering `Wikidata` now shows the `Wikidata` project as the first result. \o/
+* I have not been successful yet in getting `Not in: Wikidata` offered somehow. Entering `wikidata in` I only get three options related to the `MediaWiki-extensions-WikibaseMediaInfo` project.
+
+If anyone has examples of exact matches **not** getting offered first, please add them to this task.",1479412808,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"The original request was ""exact matches should always win"", which I interpret as saying they should always be the top match. And I agree. I'm frustrated that for some reason it seems like that change isn't going to be made. 
+
+If this task is closed (which I wouldn't object to at this point), I really think it should be ""declined"", not ""resolved"".  It's really not resolved/fixed. But at least in most cases the exact match seems to be shown in the list. Even if it's at the bottom rather than the top. ",1477605918,PHID-USER-pmfo3xmfjado5j3dqmio,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"The original request was ""exact matches should always win"", which I interpret as saying they should always be the top match. And I agree. I'm frustrated that for some reason it seems like that change isn't going to be made. 
+
+If this task is closed (which I wouldn't object to at this point), I really think it should be ""declined"", not ""resolved"".  It's really not resolved/fixed. But in most cases the exact match seems to be shown in the list. Even if it's at the bottom rather than the top. ",1477605894,PHID-USER-pmfo3xmfjado5j3dqmio,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"The original request was ""exact matches should always win"", which I interpret as saying they should always be the top match. And I agree. I'm frustrated that for some reason it seems like that change isn't going to be made. 
+
+If this task is closed (which I wouldn't object to at this point), I really think it should be ""declined"", not ""resolved.  It's really not resolved/fixed. But in most cases the exact match seems to be shown in the list. Even if it's at the bottom rather than the top. ",1477605870,PHID-USER-pmfo3xmfjado5j3dqmio,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I think I see the issue- by searching wikidata on the general form, #wikidata is not on top. I think that is a different issues than entering ""wikidata"" in a project-specific form (like creating a new ticket)- and not necessarily something we want (needs discussion). I would suggest to close this one as resolved and not increase the scope of it. If I write `#wikidata` or `#wikidata-query` on this very same same test form, I get exact results as expected while I am writing.
+
+Then create a new subtask, if needed, of T146843 as that is related to improve general search results, and not to auto-complete (which seems mostly fine).",1476699449,PHID-USER-gzd4fguky5ixnvz46fvu,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@lydia_pintscher to me it looks like it's fixed now. At least for the cases I've tried, #Wikidata was always at the top or at least in the list.
+{F4611530}",1476698805,PHID-USER-t4sxxglz6yyrgxeib43i,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"At least for ""Wikidata"" the situation is still bad unfortunately.",1476447894,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I see some issues, but is the original complain still valid?
+{F4602448}
+{F4602447}",1476433532,PHID-USER-gzd4fguky5ixnvz46fvu,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Removing Phabricator (2016-06-29) project since https://secure.phabricator.com/T8510 is still open and no time frame for that to be fixed.,1468242410,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I think the last one might be because there are a ton of additional hashtags on some of the wikidata related projects, causing them to win out in the relevance scoring.
+
+For example:
+
+#mediawiki-extensions-wikibaseclient has the following 'additional hashtags':
+
+`#MediaWiki-extensions-WikidataClient`, `#mediawiki-extensions-wikidataclient`, `#MediaWiki-extensions-Wikibase-Client`, `#MediaWiki-extensions-Wikibase+Client`, `#mediawiki-extensions-wikibase+client`",1466070166,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"For the records, https://secure.phabricator.com/T6102 is fixed upstream; https://secure.phabricator.com/T8510 not yet. 
+
+Status of three testcases, after latest deployment on 2016-06-15:
+
+**Discovery** (which has numerous additional hashtags):
+* ✔ Using ""Change Project Tags"" under ""Actions"" above the field to add a Comment and entering ""Discovery"", the 2nd item among the 5 proposals is ""Discovery"".
+* ✔ Using the global search in the upper right corner, ""Discovery"" is the 2nd item among the 10 proposals.
+* ✔ Using the ""Tags"" field on https://phabricator.wikimedia.org/maniphest/query/advanced/ and entering ""Discovery"", it is the 2nd item among the 5 proposals.
+
+**Labs** (which has no additional hashtags):
+* ✔ Using ""Change Project Tags"" under ""Actions"" above the field to add a Comment and entering ""Labs"", it is the 1st item among the 5 proposals.
+* ✔ Using the global search in the upper right corner, ""Labs"" is the 7th item among the 10 proposals.
+* ✔ Using the ""Tags"" field on https://phabricator.wikimedia.org/maniphest/query/advanced/ and entering ""Labs"", it is the 1st item among the 5 proposals.
+
+
+**Wikidata** (which has no additional hashtags):
+* ✔ Using ""Change Project Tags"" under ""Actions"" above the field to add a Comment and entering ""Wikidata"", it is the 1st item among the 5 proposals.
+* ✔ Using the global search in the upper right corner, ""Wikidata"" is the 10th item among the 10 proposals.
+* ✗ Using the ""Tags"" field on https://phabricator.wikimedia.org/maniphest/query/advanced/ and entering ""Wikidata"", it is **NOT** among the 5 proposals:
+{F4171138}",1466069281,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"(This is a test, clicking the search button, typing ""Wikidata"", and selecting it from the long list.)",1465982367,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#2382047, @Sjoerddebruin wrote:
+> … it's not possible to add the project Wikidata to tasks.
+
+Click the search button then select it.
+
+",1465980520,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Nothing seems to be changed, it's still not possible to add the project Wikidata to tasks.",1465980500,PHID-USER-pr6rfjdcmkknkex6dgn5,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Problem seems to became more worse, it's not possible to add the project Wikidata to tasks.",1465980343,PHID-USER-pr6rfjdcmkknkex6dgn5,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"More fixes coming this week, hopefully this one is fully fixed after the update.",1465668833,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"https://secure.phabricator.com/T8510 is not fully fixed yet, and this can still be reproduced trying to add ""Wikidata"" for example.",1465494314,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#1334152, @Nemo_bis wrote:
+> I'd also expect exact match of secondary hashtags to win.
+> 
+> {F173832}
+
+Was this supposed to happen, after T135068? It didn't.",1465492331,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@Qgil: Thanks for pointing to that. It looks like they're going to sort the projects by displayed name, which should at least fix the Discovery case.
+
+I still think their fix is ""wrong"", in the sense that I believe that an exact match should always win, no matter what order the results appear in. But it should be ""good enough"", at least for the cases I'm aware of. ",1464383656,PHID-USER-pmfo3xmfjado5j3dqmio,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Allegedly fixed upstream: https://secure.phabricator.com/T8510#177463,1464295052,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,@ksmith: I totally agree that this is a problem and also that the upstream task may not be exactly applicable. I only linked it because it seemed somewhat relevant. ,1464231555,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@mmodell : It is not clear to me that the upstream task would actually fix this issue. I think we should either get this case explicitly called out in that task, or we should file a new upstream task.  
+
+As a specific reproducible example, in case anyone needs one: Entering Discovery in the Tags field  still does not offer #Discovery, which has been frustrating us for over a year. 
+",1464148795,PHID-USER-pmfo3xmfjado5j3dqmio,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"There is still one upstream task[1] that remains open, unlike most of the related tasks about this issue which have been closed as either resolved or invlaid, without totally resolving the underlying problems. 
+
+[1]: https://secure.phabricator.com/T7858",1464050933,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I use a greasemonkey script to get around this problem.  This overrides the suggestion-limiter to 100. 
+It's documented onwiki at https://www.mediawiki.org/wiki/Team_Practices_Group/Phabricator_tips/Maniphest#Autocomplete_limit
+and quick install at https://openuserjs.org/scripts/quiddity-wp/wikimedia_phabricator_suggestion_expander
+
+However, it's only partially successful in some instances, such as the new ""Actions"" dropdown menus, and I haven't had time to investigate/fix it. (I assume z-index... but that's all a little outside my familiarity.)
+{F4036179}",1463779832,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Things got worse with the subprojects: {F3625114},1457861656,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Still an issue. Example: Enter [[ https://phabricator.wikimedia.org/project/profile/1174/ | discovery ]] (the primary name of a project) in the Projects field on https://phabricator.wikimedia.org/maniphest/query/advanced/ , the five proposals do not include the ""Discovery"" project itself.
+
+I've created https://secure.phabricator.com/T8510",1434023342,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"I'd also expect exact match of secondary hashtags to win.
+
+{F173832}",1433347649,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Yes, can confirm.",1432157106,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"This is not working for me, as described as part of T99739. I don't feel bold enough to reopen it myself, but believe that it should be reopened. 
+",1432136871,PHID-USER-pmfo3xmfjado5j3dqmio,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"This is not fixed for me by https://secure.phabricator.com/rP49ee09be3f453386c91820e990d6916887206eb6
+At least not in a way that I would have expected:
+{F166948}
+Can someone confirm?",1432074282,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,It works!!!,1424277155,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#1024884, @JanZerebecki wrote:
+> Why not deploy the fix
+
+-> T86772",1423497288,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Why not deploy the fix, that was merged upstream a month ago?",1423495096,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"At least you could type ""#Wikidata_"" and get the result. But yes, mentioning the project in comments/descriptions is simpler and cleaner.",1423478770,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"how would renaming to ""#Wikidata_"" work around the issue? Alphabetical sorting isn't the problem, as far as I can tell.",1423478544,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#1019339, @Qgil wrote:
+> What about renaming Wikidata to #Wikidata_ , as an interim solution?
+
++1, if it's technically possible.
+
+This is an intuitive solution. By ""intuitive"" I mean that I tried adding ""#Wikidata"" to a task before I gave up and asked @Lydia_Pintscher for help :)",1423472330,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"What about renaming Wikidata to #Wikidata_ , as an interim solution?",1423173349,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Any idea when this will go live here? It is super annoying for Wikidata :(,1422958874,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,Fixed upstream: https://secure.phabricator.com/T6102,1420849323,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"No.
+
+And my patch hasn't landed locally, so you won't see its effects yet.",1419526487,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"> 1) Open https://phabricator.wikimedia.org/maniphest/task/create/
+> 2) Type ""MediaWiki"" in ""Projects"" field
+>
+> I. Observed: first option offered is ""DataTypes""
+> II. Expected: first options offered start with ""MediaWiki""
+
+Chad, does your upstream patch reverse the ""normal"" behaviour and favour frequent words over non-frequent ones, or something like that. For instance, when I type ""Pha"" I'm most likely looking for #Phabricator or #Phabricator.org, not for § Phabricator Sprint Extension [2014-12-11]",1419498934,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@Jdlrobson, when this task is fixed (hopefully soon), you can expect the same results that you get typing ""mobile"" in the header search field. At least for me these are 
+
+# Mobile
+# Mobile-Apps
+# Mobile-Web
+# Blocked-on-Mobile-Apps
+# ...
+
+This sorting makes total sense.",1418939943,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"As described in T75737 by valhallasw, as a workaround for the time being, please execute
+
+```
+JX.TypeaheadSource.prototype.setMaximumResultCount(100)
+```
+
+in the javascript console (or a userscript).",1418649214,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,I'm reopening this for the time being.,1418292044,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"@daniel, can you at least select ""Wikidata"" now?
+
+I have commented in the related upstream task: https://secure.phabricator.com/T6102#87052",1418283692,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,">>! In T76732#838951, @chasemp wrote:
+> We may need to reindex search...
+
+Not for a change like that. We will anyway after [[ https://secure.phabricator.com/D10955 | Upstream D10955 ]] or something like it lands anyway.",1418244321,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,We may need to reindex search...,1418244150,PHID-USER-3neel27i7dyu62jbbx2l,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Not convinced this really got fixed - bypassing the browser cache, going to  ""edit task"" here and literally entering ""wikidata"" in the project field, that project is still shown as the fourth one to me. 
+
+Not sure if there's some caching server-side?
+
+How are the results for others?",1418242661,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Great! Resolving. According to T76522, the next upgrade should happen latest by next Wednesday.",1417766074,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"Thanks for the pointer! Reading the relevant code was fun :)
+That should indeed fix it, please update soon... ",1417730686,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Exact matches should always win when suggesting/auto-completing,"In theory this was fixed upstream on November 17: https://secure.phabricator.com/T6102
+
+I don't recall when exactly we upgraded our instance, but it was around that time. Maybe @chasemp or @aklapper can tell whether the related diff made it to our instance or not? If not, we are planning to upgrade one of these days (to install the Sprint app, among other things).",1417721698,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-h64673nwftdciwancqe4,task_subcomment,NA
+Provide real-time collaboration in VisualEditor-MediaWiki,"Exceptionally hard, many issues, yada yada yada.
+
+Still, this would be an excellent thing to provide our users.",1417568581,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-mto5lbev7aopkjbicd5f,task_description,open
+Provide real-time collaborative editing in VisualEditor,"This is about VisualEditor-core, not VisualEditor-MediaWiki for which there are a bunch of issues that would need to be solved first.",1417568021,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lddwevjhaszbxshxxywi,task_description,open
+Convert hyphens to en dashes when written in VisualEditor,"I dont know, how is it in English punctuation, but suprisinglly hyphen mark, which is naturally present on all keyboards is not so much used in the texts. Wikipedia is based especially on texts so it would be a nice feature to VE to have a choise to replace hyphen by En dash, which is much more need in the text at times when you hit hyphen bar.
+
+Now we should insert that symbol, by inserting the symbol - that is in fact not known to not skilled newbies. On the other side, it slow down the skilled editors. If they want to write a clear text from the beggining, the have to stop, insert en dash and continue.",1417305712,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_description,declined
+Convert hyphens to en dashes when written in VisualEditor,">>! In T76275#802670, @Jdforrester-WMF wrote:
+>>>! In T76275#802653, @Juandev wrote:
+>> Yes, I am suggesting that James. Em dash is also not so broadly used, so I would not take care of it.
+> 
+> OK. That's pretty easy to do, but it might be irritating (and we don't have a way to make sequence substitutions only work on some wikis or for some users), so I'd appreciate some other input on whether this is a good idea.
+
+Not a good idea. Hyphen is quite often used legally (eg. in names) and semi-legally (instead of minus), so enforcing its converting to en/em dash is wrong. Also other pars of wikitext can contain hyphens (data-* attributes, classnames, id's, template names etc. etc...)
+
+I barely remember there was a task about convertig -- to en dash and --- to em dash on page save (so the next user would see the proper Unicode character in editbox next time), but I can't find it ATM.
+
+WONTFIXing this because of the reasons above and in favour of the mentioned task.",1454199276,PHID-USER-xqqqgn2dels45flxw5kb,False,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+Convert hyphens to en dashes when written in VisualEditor,">>! In T76275#802653, @Juandev wrote:
+> Yes, I am suggesting that James. Em dash is also not so broadly used, so I would not take care of it.
+
+OK. That's pretty easy to do, but it might be irritating (and we don't have a way to make sequence substitutions only work on some wikis or for some users), so I'd appreciate some other input on whether this is a good idea.",1417559998,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+Convert hyphens to en dashes when written in VisualEditor,"Yes, I am suggesting that James. Em dash is also not so broadly used, so I would not take care of it.",1417559639,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+Convert hyphens to en dashes when written in VisualEditor,"Just to note - VE preserves hyphen, en-dash, and em-dash typed with regular keyboard shortcuts(on Mac - Option+- for en-dash and Shift+Option+- for em-dash).
+hyphen -
+en-dash –
+em-dash —",1417475354,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+Convert hyphens to en dashes when written in VisualEditor,"What are you suggesting? That if I type ""foo-bar"" it changes it to ""foo–bar""? What about em-dash? Should ""foo - bar"" be changed to ""foo — bar""?",1417474814,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7wkbsbpxb6wsld7vrucn,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to","The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to. It should probably include the ""continue"" message as a parameter.",1416988401,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_description,resolved
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to",Thanks to David for merging.,1417197627,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to","Change 176298 merged by jenkins-bot:
+Mention the ""Continue"" label as a parameter in visualeditor-recreate
+
+[[https://gerrit.wikimedia.org/r/176298]]",1417195377,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to","Change 176298 had a related patch set uploaded (by Amire80):
+Mention the ""Continue"" label as a parameter in visualeditor-recreate
+
+[[https://gerrit.wikimedia.org/r/176298]]
+
+#patch-for-review",1417120693,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to","Thanks, but I'd prefer to have it embedded. (A patch is ready.)",1417120659,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"The message visualeditor-recreate says ""Press continue"", but it's unclear what does ""continue"" refer to",The message is <ooui-dialog-process-continue>. I've updated the qqq to reflect this.,1417034694,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xtnd6wdqgp6cwmj72d3c,task_subcomment,NA
+"Load VisualEditor file from modules.json as a manifest, rather than tediously copying it into extension.json",,1416971459,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7blxbh53cp3cws3rmqek,task_description,duplicate
+VisualEditor: Calling buildNodeTree() manually should not be needed,"We explicitly call buildNodeTree() in a few places. Ideally, we would not need to do this outside of ve.dm.Document.
+
+Suspect calls (excluding dm.Document, excluding tests):
+
+lib/ve/src/ce/ve.ce.Surface.js
+1000:			doc.buildNodeTree();
+1711:		doc.buildNodeTree();
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416338280,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3iyil63ecpynuu65ebug,task_description,open
+VisualEditor: Calling buildNodeTree() manually should not be needed,"The node tree is lazily evaluated by buildNodeTree the first time you call getDocumentNode. In the examples your provide (paste and drag-drop) we call buildNodeTree after sanitisation has occurred, as sanitisation happens on the data model array.",1416340739,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3iyil63ecpynuu65ebug,task_subcomment,NA
+VisualEditor: DOM Exception (no user-facing loss of functionality?) after a long editing session,"After a prolonged session of editing in Safari, the following error was displayed: 
+
+[Error] Error: QuotaExceededError: DOM Exception 22 DOMException
+	log (load.php, line 150)
+	flush (load.php, line 173)
+
+
+No degradation in responsiveness/functionality was noticed. Should we handle this exception?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1416273720,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-v5jcyw7wftxsu6hvvjts,task_description,open
+VisualEditor: DOM Exception (no user-facing loss of functionality?) after a long editing session,"We should find out what this is before WONTFIXing, at least.",1416342245,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v5jcyw7wftxsu6hvvjts,task_subcomment,NA
+VisualEditor: Discrepancy in displaying text with <mark>  in Edit and Read modes,"Read mode - all text is highlighted
+
+1. In VE type some text. Hit enter for the second line.
+
+Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling.
+ 
+2. Open Edit source(Keep changes) and add <mark> as in the sample below: 
+
+<mark>
+Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling. 
+
+3. Save - in Read mode all text on the page will be highlighted with the yellow background. 
+
+4. Switch to Edit mode again - only the first line will be displayed as highlighted. 
+
+The screenshots are attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14967}",1416269700,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-bzsupfbaq25gtun2byod,task_description,resolved
+VisualEditor: Discrepancy in displaying text with <mark>  in Edit and Read modes,This has been fixed when Parsoid and MediaWiki were updated to use the same HTML5 parsing algorithm (T89331).,1558272914,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-bzsupfbaq25gtun2byod,task_subcomment,NA
+VisualEditor: Discrepancy in displaying text with <mark>  in Edit and Read modes,"Created attachment 17155
+Edit mode - only the first line is highlighted
+
+**Attached**: {F14968}",1416269795,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-bzsupfbaq25gtun2byod,task_subcomment,NA
+VisualEditor: ve-ce-focusableNode-dropMarker is displayed as a horizontal line when Gallery is dragged-drop to Media Caption,"dragging gallery to Media
+
+1. VE: insert media(a picture) and a gallery.
+
+2. Attempt to drag a gallery into Media and drop - a horizontal vertical line will be displayed. The screen recording is attached.  
+
+e.g.
+<div class=""ve-ce-focusableNode-dropMarker"" style=""width: 1048px;"">
+
+
+Note: happens *only* with dragging  a gallery.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14943}",1416263460,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-aiczpu2ygn72rpiek6xz,task_description,resolved
+VisualEditor: ve-ce-focusableNode-dropMarker is displayed as a horizontal line when Gallery is dragged-drop to Media Caption,"This doesn't seem to be a problem any more. It was probably caused by some exception in drag-and-drop code preventing it from cleaning up the marker after the content was dropped, but it would be a lot of effort to try to reproduce that now.",1577744177,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-aiczpu2ygn72rpiek6xz,task_subcomment,NA
+VisualEditor: ve-ce-focusableNode-dropMarker is displayed as a horizontal line when Gallery is dragged-drop to Media Caption,"Those thin lines are visible only in VE - they are not preserved upon saving, so the priority is Low.",1423275582,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-aiczpu2ygn72rpiek6xz,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"User:Tacsipacsi at the Hungarian Wikipedia reports issues with ""the new buttons"" and provides the following log:
+
+```
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/index.html
+HTML style attribute
+Invalid value for property: zoom
+Line 1:
+  display:inline;margin:0;border:0;padding:1px;width:1px;zoom:1
+  -------------------------------------------------------------^
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/oojs-ui-mediawiki.svg.css
+Linked-in stylesheet
+Invalid value for property: -webkit-transform
+Line 957:
+    -webkit-transform: translateZ(0px);
+  -------------------------------------^
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/oojs-ui-mediawiki.svg.css
+Linked-in stylesheet
+Invalid value for property: -o-transform
+Line 960:
+    -o-transform: translateZ(0px);
+  --------------------------------^
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/oojs-ui-mediawiki.svg.css
+Linked-in stylesheet
+Invalid value for property: transform
+Line 961:
+    transform: translateZ(0px);
+  -----------------------------^
+[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/styles/demo.css
+Linked-in stylesheet
+Declaration syntax error
+Line 197:
+   width: calc(100% - 40px);
+  --------------------------^
+```
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1416245640,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-jugonrend4wlvekztr4d,task_description,resolved
+OOjs UI: trouble with CheckboxInputWidget in Opera,"OK, I can go with it.",1424979350,PHID-USER-ocqnoktaualicuvge2tu,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"Hmm. I can reproduce that now – when I double-click on the checkbox label (which results in text being selected), the checkbox appears in incorrect state, and fixes itself when I mouse away. This looks like a browser bug, and it doesn't seem to be easily resolvable – honestly, I'm not sure if it's worth worrying about.
+
+(It also doesn't seem to affect OOjs UI checkboxes – the ones used mostly in VisualEditor – but only MediaWiki UI checkboxes – the ones used on the login page, for example.)
+
+As for the CSS errors, they are harmless – MediaWiki uses certain technically invalid constructs to support both old browsers (mostly IE 6) and experimental features of new browsers . Error handling in CSS is well-defined and therefore these are not a problem.",1424973444,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"@matmarex: I tested again and the error is that there isn’t disappear until I move the cursor from the box. I don’t get any error messages while trying to click on the checkbox. I get the following //error//s while loading the page (not including //information//s):
+```
+lines=12
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s/BetaFeatures/resources/images/feature-discussion.svg?2014-09-30T20:31:40Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s/BetaFeatures/resources/images/feature-discussion.svg?2014-09-30T20:31:40Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /BetaFeatures/resources/images/feature-information.svg?2014-09-30T20:31:40Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /BetaFeatures/resources/images/feature-information.svg?2014-09-30T20:31:40Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: filter
+Line 1:
+  sform:scaleX(-1);-webkit-transform:scaleX(-1);transform:scaleX(-1);filter:FlipH;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ources/skins/vector/../../images/badge-silver-star.png?2014-09-30T20:46:40Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ources/skins/vector/../../images/badge-golden-star.png?2014-09-30T20:46:40Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  px solid #aaaaaa;background-color:#f9f9f9;padding:5px;display:-moz-inline-block;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  padding:5px;display:-moz-inline-block;display:inline-block;display:table;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  lay:-moz-inline-block;display:inline-block;display:table;zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  lerybox{vertical-align:top;display:inline-block}ul.gallery,li.gallerybox{zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -align:top;display:inline-block}ul.gallery,li.gallerybox{zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  style:none;list-style-type:none;list-style-image:none;vertical-align:middle !ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  e-height:1.15em;padding:0 .4em;border-left:1px solid #AAA;margin:0.1em 0;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ding:0 .4em;border-left:1px solid #AAA;margin:0.1em 0;zoom:1;display:inline !ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  sources/src/mediawiki.legacy/images/checker.png?2014-08-30T22:43:20Z) repeat!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ter/resources/src/mediawiki.legacy/images/question.svg?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ter/resources/src/mediawiki.legacy/images/question.svg?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  style:none;list-style-type:none;list-style-image:none;vertical-align:middle !ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  eight:1.25em;border-left:1px solid #AAA;margin:0.125em 0;padding:0 0.5em;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -left:1px solid #AAA;margin:0.125em 0;padding:0 0.5em;zoom:1;display:inline !ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  er/resources/src/mediawiki.legacy/images/feed-icon.svg?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  er/resources/src/mediawiki.legacy/images/feed-icon.svg?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  x{border:1px solid;padding:.5em 1em;margin-bottom:1em;display:-moz-inline-block;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  5em 1em;margin-bottom:1em;display:-moz-inline-block;display:inline-block;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ottom:1em;display:-moz-inline-block;display:inline-block;zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  ht:1.6em;margin-left:0}li.gallerybox{vertical-align:top;display:-moz-inline-box;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  op;display:-moz-inline-box;display:inline-block}ul.gallery,li.gallerybox{zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  inline-box;display:inline-block}ul.gallery,li.gallerybox{zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /resources/src/mediawiki.legacy/images/ajax-loader.gif?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ster/resources/src/mediawiki.legacy/images/spinner.gif?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  l:lang(glk) li,ol:lang(kk-arab) li,ol:lang(mzn) li{list-style-type:-moz-persian;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  k-arab) li,ol:lang(mzn) li{list-style-type:-moz-persian;list-style-type:persian}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  rsian;list-style-type:persian}ol:lang(ckb) li{list-style-type:-moz-arabic-indic;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  }ol:lang(ckb) li{list-style-type:-moz-arabic-indic;list-style-type:arabic-indic}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  type:arabic-indic}ol:lang(hi) li,ol:lang(mr) li{list-style-type:-moz-devanagari;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  i) li,ol:lang(mr) li{list-style-type:-moz-devanagari;list-style-type:devanagari}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  tyle-type:devanagari}ol:lang(as) li,ol:lang(bn) li{list-style-type:-moz-bengali;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  lang(as) li,ol:lang(bn) li{list-style-type:-moz-bengali;list-style-type:bengali}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  :-moz-bengali;list-style-type:bengali}ol:lang(or) li{list-style-type:-moz-oriya;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-type
+Line 1:
+  le-type:bengali}ol:lang(or) li{list-style-type:-moz-oriya;list-style-type:oriya}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  esources/src/mediawiki.legacy/images/help-question.gif?2014-08-30T22:43:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  es/src/mediawiki.legacy/images/help-question-hover.gif?2014-08-30T22:43:20Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  dits a{unicode-bidi:embed}.mw-jump,#jump-to-nav{overflow:hidden;height:0;zoom:1}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -anchor{font-weight:normal;margin-left:-14px;width:14px;filter:alpha(opacity=0);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  headline-anchor,.mw-body h6:focus .mw-headline-anchor{filter:alpha(opacity=100);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  und-color:#f9f9f9;padding:5px;font-size:95%}#toc,.toc{display:-moz-inline-block;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  %}#toc,.toc{display:-moz-inline-block;display:inline-block;display:table;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  lay:-moz-inline-block;display:inline-block;display:table;zoom:1;*display:inline;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-ltr.svg?2014-11-14T23:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-ltr.svg?2014-11-14T23:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-ltr.svg?2014-11-14T23:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-ltr.svg?2014-11-14T23:33:20Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-rtl.svg?2014-11-14T23:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  ces/src/mediawiki.skinning/images/magnify-clip-rtl.svg?2014-11-14T23:33:20Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  sizing:border-box;box-sizing:border-box;-webkit-appearance:none;*display:inline;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  border-box;box-sizing:border-box;-webkit-appearance:none;*display:inline;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  );border-bottom-color:#cccccc;outline:none}.mw-ui-button:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  none}.mw-ui-button:hover::-moz-focus-inner,.mw-ui-button:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  lor:#2a62cc;outline:none}.mw-ui-button.mw-ui-progressive:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  :hover::-moz-focus-inner,.mw-ui-button.mw-ui-progressive:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  sive:focus::-moz-focus-inner,.mw-ui-button.mw-ui-primary:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  mary:hover::-moz-focus-inner,.mw-ui-button.mw-ui-primary:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  or:#008c6e;outline:none}.mw-ui-button.mw-ui-constructive:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  hover::-moz-focus-inner,.mw-ui-button.mw-ui-constructive:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  lor:#a7170f;outline:none}.mw-ui-button.mw-ui-destructive:hover::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  :hover::-moz-focus-inner,.mw-ui-button.mw-ui-destructive:focus::-moz-focus-inner
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: -webkit-transition
+Line 1:
+  ""] + label::before{-webkit-transition:0.2s cubic-bezier(0.175,0.885,0.32,1.275);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: -o-transition
+Line 1:
+  0.175,0.885,0.32,1.275);-o-transition:0.2s cubic-bezier(0.175,0.885,0.32,1.275);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: transition
+Line 1:
+  er(0.175,0.885,0.32,1.275);transition:0.2s cubic-bezier(0.175,0.885,0.32,1.275);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  sources/src/mediawiki.ui/components/images/checked.svg?2014-11-27T01:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  sources/src/mediawiki.ui/components/images/checked.svg?2014-11-27T01:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  rc/mediawiki.ui/components/images/checked_disabled.svg?2014-11-27T01:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  rc/mediawiki.ui/components/images/checked_disabled.svg?2014-11-27T01:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: display
+Line 1:
+  em;position:relative;z-index:1}.mw-body .mw-indicator{display:-moz-inline-block;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: zoom
+Line 1:
+  :1}.mw-body .mw-indicator{display:-moz-inline-block;display:inline-block;zoom:1;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  indicator{display:-moz-inline-block;display:inline-block;zoom:1;*display:inline}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  .org/static-master/skins/Vector/images/bullet-icon.svg?2015-02-14T02:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: list-style-image
+Line 1:
+  AAAAXRSTlMAQObYZgAAABNJREFUCB1jYEABBQw/wLCAgQEAGpIDyT0IVcsAAAAASUVORK5CYII=) \9;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  g/static-master/skins/Vector/images/bullet-icon.png?2014-08-07T15:20:00Z) \9!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/user-icon.svg?2014-12-24T12:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/user-icon.svg?2014-12-24T12:33:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  .org/static-master/skins/Vector/images/search-fade.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  -placeholder{color:#999}div#simpleSearch #searchInput::-webkit-search-decoration
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  it-search-decoration,div#simpleSearch #searchInput::-webkit-search-cancel-button
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  earch-cancel-button,div#simpleSearch #searchInput::-webkit-search-results-button
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+""::"" not followed by known pseudo element
+Line 1:
+  -results-button,div#simpleSearch #searchInput::-webkit-search-results-decoration
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s.org/static-master/skins/Vector/images/search-ltr.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s.org/static-master/skins/Vector/images/search-ltr.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/tab-break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/tab-break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/tab-normal-fade.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  static-master/skins/Vector/images/tab-current-fade.png?2014-08-07T15:20:00Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/tab-break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  bs.org/static-master/skins/Vector/images/tab-break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/arrow-down-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/arrow-down-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  c-master/skins/Vector/images/arrow-down-focus-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  c-master/skins/Vector/images/arrow-down-focus-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  0;display:block;width:26px;padding-top:3.1em;margin-top:0;margin-top:-0.8em !ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  org/static-master/skins/Vector/images/unwatch-icon.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  org/static-master/skins/Vector/images/unwatch-icon.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s.org/static-master/skins/Vector/images/watch-icon.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  s.org/static-master/skins/Vector/images/watch-icon.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/unwatch-icon-hl.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  /static-master/skins/Vector/images/unwatch-icon-hl.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  rg/static-master/skins/Vector/images/watch-icon-hl.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  rg/static-master/skins/Vector/images/watch-icon-hl.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  atic-master/skins/Vector/images/watch-icon-loading.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  atic-master/skins/Vector/images/watch-icon-loading.svg?2014-12-16T18:53:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Unrecognized function
+Line 1:
+  -color:#f6f6f6;background-image:-moz-linear-gradient(top,#fff 50%,#f6f6f6 100%);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: background-image
+Line 1:
+  -color:#f6f6f6;background-image:-moz-linear-gradient(top,#fff 50%,#f6f6f6 100%);
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Unrecognized function
+Line 1:
+  kground-image:-webkit-gradient(linear,left top,left bottom,color-stop(50%,#fff),
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Unrecognized function
+Line 1:
+  dient(linear,left top,left bottom,color-stop(50%,#fff),color-stop(100%,#f6f6f6))
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Unrecognized function
+Line 1:
+  ient(linear,left top,left bottom,color-stop(50%,#fff),color-stop(100%,#f6f6f6));
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Invalid value for property: background-image
+Line 1:
+  ient(linear,left top,left bottom,color-stop(50%,#fff),color-stop(100%,#f6f6f6));
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  org/static-master/skins/Vector/images/portal-break.png?2014-08-07T15:20:00Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -master/skins/Vector/images/external-link-ltr-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:31] CSS - http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.betaFeatures.styles%7Cext.echo.badge%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%2CwikimediaBadges%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.sectionAnchor%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%2Ccheckbox%7Cskins.vector.styles&only=styles&skin=vector&*
+Linked-in stylesheet
+Declaration syntax error
+Line 1:
+  -master/skins/Vector/images/external-link-ltr-icon.svg?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: zoom
+Line 2:
+  olor:#FFC0C0;color:black}   .mw-navigation-hint{overflow:hidden;height:0;zoom:1}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 2:
+  kins/Vector/skinStyles/../images/preferences/break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 2:
+  kins/Vector/skinStyles/../images/preferences/break.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 2:
+  skins/Vector/skinStyles/../images/preferences/fade.png?2014-08-07T15:20:00Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: unicode-bidi
+Line 4:
+  15px;float:right} .mw-editsection{white-space:nowrap; unicode-bidi:-moz-isolate;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: unicode-bidi
+Line 4:
+  tion{white-space:nowrap; unicode-bidi:-moz-isolate;unicode-bidi:-webkit-isolate;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: unicode-bidi
+Line 4:
+  ap; unicode-bidi:-moz-isolate;unicode-bidi:-webkit-isolate;unicode-bidi:isolate}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 4:
+  ditor/modules/ve-mw/init/styles/images/loading-ltr.gif?2014-09-30T20:46:40Z)!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 8:
+  s/src/jquery.tipsy/images/tipsy.png?2014-04-21T16:58:20Z) no-repeat top left!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:32] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+HTML style attribute
+Invalid value for property: zoom
+Line 1:
+  display:inline;margin:0;border:0;padding:1px;width:1px;zoom:1
+  -------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Invalid value for property: zoom
+Line 8:
+  ;position:relative;padding-top:15px;padding-bottom:10px; overflow:hidden;zoom:1}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 12:
+  urces/css/../images/cog-sprite.png?2015-01-24T06:23:20Z) no-repeat right top!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 12:
+  anguageSelector/resources/css/../images/cog-sprite.svg?2015-01-24T06:23:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 12:
+  anguageSelector/resources/css/../images/cog-sprite.svg?2015-01-24T06:23:20Z)!ie;
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 4:
+  tificationsPage-ltr.png?2014-09-30T20:35:00Z) no-repeat 20px 15px !important!ie}
+  --------------------------------------------------------------------------------^
+[2015.02.26. 17:58:33] CSS - http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences
+Inlined stylesheet
+Declaration syntax error
+Line 4:
+  y/../icons/Settings.png?2014-09-30T20:35:00Z) no-repeat 20px 15px !important!ie}
+  --------------------------------------------------------------------------------^
+```",1424970486,PHID-USER-ocqnoktaualicuvge2tu,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"@Tacsipacsi If that happens only the first time when you check a checkbox, then that's possible, since the image will now only be loaded when necessary (previously it was preloaded). Otherwise that should not happen, and I can't reproduce the problem myself (using Opera 12.17 on Windows 7).",1424955729,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"@matmarex: I tried it and it works, but it has a bit (sometimes several seconds) delay. Is it normal? If not, can it be fixed?",1424374555,PHID-USER-ocqnoktaualicuvge2tu,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"The issue has now been fixed, and the fix will be included in MediaWiki version 1.25wmf19. According to https://www.mediawiki.org/wiki/MediaWiki_1.25/Roadmap, that version will be deployed to Wikipedias on 4 March. You can try out the fix at beta labs (http://en.wikipedia.beta.wmflabs.org/).",1424354295,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"The issue is caused by the combination of the SVG background and the border-radius. One solution can be seen in 2b8f46c6. An other solution is to remove the CSS border completely and draw the border in the SVG instead. I once tested this and it works fine in all browsers including Opera 12.
+
+Personally I'm oscillating between two extremes:
+
+* Don't reinvent the wheel. A checkbox is a checkbox. All CSS hacks (opacity: 0, empty clip regions) to force individual styles on otherwise native form elements are horrible and should have never been invented.
+
+* Opera 12 is dead. It's performance on sites like Twitter is horrible. People should just stop using it. I did.",1416489605,PHID-USER-u6ycqhfpa3k4yvlpxjt2,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"(In reply to Bartosz Dziewoński from comment #2)
+> The solution is to stop serving SVG to Opera 12, like Thiemo has figured out
+> and did it for this new checkbox style back when it was part of BetaFeatures
+
+Note that this doesn't even cause the rendering to worsen – while Opera 12 has excellent support for the SVG format itself, it has rather lousy support for SVGs as background-images – if you zoom in, you can see the pixels appear just as if it was a PNG image. (I never tested this on a high DPI screen, but I would expect the effect to be the same.)",1416343322,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"Assuming this is about Opera 12, then this is a Opera bug where SVG background-image sometimes disappears in presence of border-radius and the right phase of the moon. If you restart your browser, you'll probably be able to see the checkmark (for a while).
+
+The solution is to stop serving SVG to Opera 12, like Thiemo has figured out and did it for this new checkbox style back when it was part of BetaFeatures (2b8f46c6dfbbe9a66029820f2b524b3aaf8fcddd). That is, however, currently impossible with the current build and ""shipping"" process of OOUI.
+
+It might also be possible to come up with a magic combination of styles that makes it all work correctly. I couldn't come up with any, but I didn't spend too much time poking at this.",1416343161,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+OOjs UI: trouble with CheckboxInputWidget in Opera,"The problem is that there's no visual difference between the checked and unchecked status of the buttons. I tested and I can use it, but I don't know whether it's in checked or unchecked state. It generated lots of ""warnings"" beside the ""errors"" in the previous comment what I didn't attach to the error report, say if you need it.",1416251839,PHID-USER-ocqnoktaualicuvge2tu,True,PHID-TASK-jugonrend4wlvekztr4d,task_subcomment,NA
+VisualEditor: FlaggablePageView::setPageContent() called incorrectly,"ApiVisualEditorEdit.php:142, $view->setPageContent() should be passing 2 parameters
+
+	public function setPageContent( &$outputDone, &$useParserCache ) {
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1416057420,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-zivj5224uzhg27lsf7rt,task_description,resolved
+VisualEditor: FlaggablePageView::setPageContent() called incorrectly,"Change 173749 merged by jenkins-bot:
+Stop warnings about calling FlaggablePageView::setPageContent with no parameters
+
+https://gerrit.wikimedia.org/r/173749",1416246459,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zivj5224uzhg27lsf7rt,task_subcomment,NA
+VisualEditor: FlaggablePageView::setPageContent() called incorrectly,"Change 173749 had a related patch set uploaded by Alex Monk:
+Stop warnings about calling FlaggablePageView::setPageContent with no parameters
+
+https://gerrit.wikimedia.org/r/173749",1416187758,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zivj5224uzhg27lsf7rt,task_subcomment,NA
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,"Inserted table with caption
+
+Steps to reproduce: 
+
+1 VE - Insert a media
+2. In Media Settings box insert a table and add a caption to a table. Click Insert.
+
+The media will be inserted with a table and the table caption will be displayed below the table. The screenshot is attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F15354}",1416001080,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3p6vhaawgb7sqodrhouz,task_description,resolved
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,"Change 264600 merged by jenkins-bot:
+Fix caption-side for tables inside figcaptions
+
+[[https://gerrit.wikimedia.org/r/264600]]",1453061211,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3p6vhaawgb7sqodrhouz,task_subcomment,NA
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,"Change 264600 had a related patch set uploaded (by Esanders):
+Fix caption-side for tables inside figcaptions
+
+[[https://gerrit.wikimedia.org/r/264600]]
+",1453051505,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3p6vhaawgb7sqodrhouz,task_subcomment,NA
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,This is an upstream issue with how Parsoid styles <figcaption>s. This rule is inherited by the table's <caption>.,1452965311,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3p6vhaawgb7sqodrhouz,task_subcomment,NA
+VisualEditor: Tables that are inserted into Media captions will display Table caption below the table,Found in test2 and beta.,1416002871,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3p6vhaawgb7sqodrhouz,task_subcomment,NA
+VisualEditor: Ctrl-v of text into a pre-formatted area ends up with <br> added to each line,"I was inserting log lines into a preformatted area.  It looked fine on the page, but after saving, there were clearly extra spaces added.  Went into wikitext to remove them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415998020,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-3gb5fng3mdx3cf25e4jj,task_description,invalid
+VisualEditor: Ctrl-v of text into a pre-formatted area ends up with <br> added to each line,"I couldn't reproduce this. It's likely to have been fixed, either by changes in our code or by improvements in the browsers. If you can still reproduce, please reopen, and please add more details (where you're copying from and where you're pasting to, and your browser/OS).",1655736850,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3gb5fng3mdx3cf25e4jj,task_subcomment,NA
+VisualEditor: Ctrl-v of text into a pre-formatted area ends up with <br> added to each line,"There are several issue with copy/paste into pre-formatted area - e.g.https://phabricator.wikimedia.org/T74456.
+Prioritizing for now as low.",1423321723,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3gb5fng3mdx3cf25e4jj,task_subcomment,NA
+VisualEditor: Tables inside references aren't allowed in wikitext (but are in VE and Parsoid),"Tables in References list
+
+Should we allow inserting tables in Basic citation? 
+
+1. VE - insert Cite->Basic 
+
+When inserting Basic citation the dialog box shows all toolbar options in Reference dialog box including tables. 
+
+2. Insert a table from the Reference dialog box for the Basic citation. Type some text in that table. 
+
+The reference list accommodate the table but does not how any table structure - see the attached screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15121}",1415840100,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ezoyokghacndpxr47zrb,task_description,open
+VisualEditor: Drag-and-drop of a block image into a table slices the table rather than inserting inside the cell,"dragging block images split tables
+
+The bug is split from 72995
+
+Dragging an image and placing the insert cursor outside a table will split the table.
+
+See the at attached screen recording.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15063}",1415813220,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-gygrr56itpwtjglimrdq,task_description,resolved
+VisualEditor: Drag-and-drop of a block image into a table slices the table rather than inserting inside the cell,I think this has been fixed since we introduced block drop targets,1452965061,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-gygrr56itpwtjglimrdq,task_subcomment,NA
+VisualEditor: Drag-and-drop of a block image into a table slices the table rather than inserting inside the cell,"It seems that formulae(display:block;) cannot be dragged into a table but are perfectly draggable over the page, including a caption of a table. 
+
+Should we make formulae draggable to tables?",1415903110,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-gygrr56itpwtjglimrdq,task_subcomment,NA
+VisualEditor: Paste from Word to Firefox inserts garbage,"Cut 'n paste from a MS Word document into FF inserts several HTML comments which appear in VE as circled exclamation marks.  Hovering reveals the lengthy MSIE-specific comments.
+
+Note that pasting the same thing into Chrome does not end up with the lengthly comments.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415765760,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-72pzweoqmhairfkznqk6,task_description,declined
+VisualEditor: Paste from Word to Firefox inserts garbage,">>! In T75292#1258930, @nshahquinn-wmf wrote:
+> @MarkAHershberger, just for clarity, could you attach a Word doc which shows this behavior?
+
+Unfortunately closing this Phabricator task as no further information has been provided.
+
+@MarkAHershberger: After you have provided the information asked for and if this still happens, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks!",1590761121,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-72pzweoqmhairfkznqk6,task_subcomment,NA
+VisualEditor: Paste from Word to Firefox inserts garbage,"@MarkAHershberger, just for clarity, could you attach a Word doc which shows this behavior?",1430776412,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-72pzweoqmhairfkznqk6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Not logged in warning
+
+In test2 and in Betalabs a warnings gets displayed ""You are not logged in..."". The page displays a user status as being logged in in the upper right corner.(see the attached screenshot).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14878}",1415667240,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-4aaydfvos3g3vz7sutt6,task_description,open
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Thx, @matmarex for following up!  Yes, presently the issue is reproducible exactly as you described. And yes, before (in 2014) there were no additional warning (popup) before publishing. 
+
+There are several points: 
+(1) The major motivation for filing this bug was that users don't see their status changed (they are displayed as being logged in). When they see the warning and, at the same time, see that they  are still logged-in, what they are supposed to do?  Dismiss the warning and reload the page, then to click to log in  - these are quite non-trivial steps. Also, their editing efforts might be lost (I know that it's not the case, but users might not be so sure). 
+
+Btw, the options in the warning popup before publishing are different for for Suggested edits. A user is given an option to login (makes more sense to me): 
+
+{F41417596}
+
+(2) With temp users the issue described in the task won't be an issue, that's why I still think that this task might be closed. 
+{F41417587}
+
+(3) (out of scope of Editing context) The case when a user's status as being logged in is displayed, but, in fact, a user is logged out is present in different context. The most recent case with UploadWizard process - the warning there is barely noticeable and the logged-in status is still displayed.  
+{F41417610}
+
+",1698776965,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Oh, I see, I didn't read the task very carefully… I agree this is still a problem (although I also agree it's probably uncommon in production).
+
+More practical steps to reproduce (without waiting for login session to expire) are:
+# View a page as a logged-in user
+# In another browser tab, log out
+# In the original browser tab, click ""Edit"" to open VE
+
+{F41417244}
+
+If you continue and try to save your edit, you will get a warning about it when publishing changes, which I think decently explains what's going on: (I'm not sure if we had this back in 2014)
+
+{F41417246}
+
+Maybe VE could detect this situation and show this warning earlier.",1698767278,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,">>! In T75250#9279424, @matmarex wrote:
+> I can't reproduce this today.
+
+Thanks @matmarex for looking into it! The issue is still present in beta (at least) - to reproduce a user needs to be logged in and to wait for a user session expired. I recently ran into this issue on `commons beta`.  It might be that production handles sessions differently and, since there were no complaints, I agree that the issue may be closed for now. ",1698338451,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,I can't reproduce this today.,1698235646,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,Adding screenshots {F54279}{F54277},1425420254,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Re-checked after my user rights were changed to authorized. The captcha  does not appear anymore and the edits are saved. 
+However, the message ""You are not logged...""  still appears - although the page still displays me as logged in.",1423598026,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,"Since I do not have a way to manipulate session timeouts, we need to wait for timeout to occur naturally...
+
+1. Open VE and wait for an hour-and-half.
+2. Try to edit the page.
+3. In betalabs I receive a captcha in Save dialog box - entering the captcha(s) does not seem to be working.
+4. Switch to Read and then back to Edit - the message ""You are not logged...""  appears.
+
+ 
+Console shows:
+""[Edit] Missing property ""user.id"""" load.php:37
+<anonymous> load.php:37
+mw.trackSubscribe/<() load.php:154
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/self.fireWith() load.php:46
+jQuery.Callbacks/self.fire() load.php:46
+mw.track() load.php:153
+<anonymous> load.php:219
+ve.trackSubscribe/<() load.php:41
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/self.fireWith() load.php:46
+jQuery.Callbacks/self.fire() load.php:46
+ve.track() load.php:41
+ve.init.mw.TargetEvents.prototype.trackSaveError() load.php:215
+oo.EventEmitter.prototype.emit() load.php:58
+ve.init.mw.Target.prototype.onSaveError/<() load.php:197
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/self.fireWith() load.php:46
+.Deferred/</deferred[tuple[0]]() load.php:47
+mw.Api.prototype.ajax/xhr<() load.php:26
+jQuery.Callbacks/fire() load.php:45
+jQuery.Callbacks/self.fireWith() load.php:46
+done() load.php:135
+.send/callback()    ",1423529844,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in,Cannot reproduce issue.,1415672303,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-4aaydfvos3g3vz7sutt6,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Inconsistent behavior in Chrome compared to FF, on applying  a link or language annotation to a gallery.","Environment- test2, beta
+
+Just like media files , the gallery also does not take link or any annotations. But the behavior is inconsistent in Chrome when compared to FF.
+
+Tested in Chrome 38 and FF 33.1.
+
+1> In a blank page, insert a Gallery with some caption
+2> Click to highlight the gallery and while it is still highlighted, select to insert link.
+3> In FF, the link inspector opens above the Gallery.
+In Chrome, the link inspector opens and closes in a split second.
+
+The same thing happens when trying to language annotations to a Gallery.
+1> > insert a Gallery with a file name and caption
+2> Click to highlight the gallery and while it is still highlighted, select to apply language.
+3> In FF, the langauge inspector opens below  the Gallery.
+
+In Chrome, the language inspector opens and closes instantly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1415642340,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-rf55v7fmqwvlp6c7uvg6,task_description,open
+"VisualEditor:[Regression wmf7] Inconsistent behavior in Chrome compared to FF, on applying  a link or language annotation to a gallery.",Confirmed  - and as in bug 73226 - an inserted Gallery should be the first element on a page to display the described issue.,1415643472,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-rf55v7fmqwvlp6c7uvg6,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited.
+
+For example, create a page with the following wikitext:
+```
+<gallery>
+>>
+</gallery>
+```
+Example: https://en.wikipedia.org/w/index.php?title=User:Matma_Rex/sandbox&oldid=826934821
+
+This renders as an empty gallery (`<ul class=""gallery mw-gallery-traditional""></ul>`).
+
+In VE, it displays a placeholder, but it seems that it can't be clicked to focus it:
+{F13935446}
+When focussed using arrow keys, it displays a completely mispositioned context menu:
+{F13935448}
+Trying to use the ""Edit"" button causes a JS error in the console:
+```
+TypeError: Cannot read property 'toggleHighlighted' of undefined
+    at VeUiMWGalleryDialog.ve.ui.MWGalleryDialog.onHighlightItem (https://en.wikipedia.org/w/extensions/VisualEditor/modules/ve-mw/ui/dialogs/ve.ui.MWGalleryDialog.js?22058:591:7)
+    at https://en.wikipedia.org/w/extensions/VisualEditor/modules/ve-mw/ui/dialogs/ve.ui.MWGalleryDialog.js?22058:342:13
+    at fire (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3317:31)
+    at Object.add [as done] (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3376:7)
+    at VeUiMWGalleryDialog.<anonymous> (https://en.wikipedia.org/w/extensions/VisualEditor/modules/ve-mw/ui/dialogs/ve.ui.MWGalleryDialog.js?22058:341:9)
+    at https://en.wikipedia.org/w/resources/lib/oojs-ui/oojs-ui-windows.js?f9a29:748:28
+    at mightThrow (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3583:29)
+    at process (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3651:12)
+```",1415641200,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-5m22o74uyj2fr46ck3hv,task_description,resolved
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Change 413253 **merged** by Jforrester:
+[mediawiki/extensions/VisualEditor@master] ve.ce.MWGalleryNode: Ensure we always have a focusable element
+
+[[https://gerrit.wikimedia.org/r/413253]]",1519259604,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Change 413252 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.ui.MWGalleryDialog: Handle galleries with 0 items
+
+[[https://gerrit.wikimedia.org/r/413252]]",1519259491,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Change 413253 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.ce.MWGalleryNode: Ensure we always have a focusable element
+
+[[https://gerrit.wikimedia.org/r/413253]]",1519248599,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Change 413252 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.ui.MWGalleryDialog: Handle galleries with 0 items
+
+[[https://gerrit.wikimedia.org/r/413252]]",1519248598,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"This is not reproducible as originally written, due to changes in the gallery inspector, but a similar issue is still present. I updated the description.",1519245771,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,"Confirmed. 
+
+In addition to the scenario described abotve: 
+
+If "">>"" is entered  - the gallery will be saved as 
+
+<gallery>
+>>
+</gallery>  
+
+
+If, say, ""caption"", will be surrounded with << and >>, then the inserted Gallery becomes invisible, but in Edit source it will be: 
+
+<gallery>
+<<Caption>>
+</gallery>",1415642531,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited,Also found in FF 33.1.,1415641254,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-5m22o74uyj2fr46ck3hv,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Inserting media, while Gallery inspector is open, makes the cursor active in the main editor","Environment- test2, beta
+
+1> Select to insert a gallery.Type in  some caption in the resulting  dialog.
+2> Click done. 
+3> open the gallery inspector again and while it is open, select Insert -> Media.
+4> After the Media Search dialog opens notice the cursor instead of being active in the dialog's input field , is active in the main editor. See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1415637000,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-qe5zfxyv76gy6qgn6hwf,task_description,resolved
+"VisualEditor:[Regression wmf7] Inserting media, while Gallery inspector is open, makes the cursor active in the main editor",Checked in betalabs and production.,1423522560,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-qe5zfxyv76gy6qgn6hwf,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Inserting media, while Gallery inspector is open, makes the cursor active in the main editor",Confirmed  - an inserted Gallery should be the first element on a page to display tye described behavior with a cursor.,1415639173,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-qe5zfxyv76gy6qgn6hwf,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Inserting media, while Gallery inspector is open, makes the cursor active in the main editor",http://youtu.be/m6BeEEnrKtc . Also found in FF 33.1.,1415637301,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-qe5zfxyv76gy6qgn6hwf,task_subcomment,NA
+"VisualEditor:[Regression wmf7] Uncaught TypeError: Cannot read property 'nodeType' of undefined ,on deleting the content in the Gallery inspector and clicking done","screenshot of JS error
+
+Enviornment- test2, beta
+
+1> Select to insert a gallery. When the inspector opens just type in some text.
+2> Now highlight the gallery and click on the gallery context menu. The gallery inspector opens.
+3> delete the content in the dialog and then press done.Generates JS error Uncaught TypeError: Cannot read property 'nodeType' of undefined in the console.See screenshot.
+
+Same behavior found in FF 33.1. 
+JS error - TypeError: currentNode.children[(nao.offset - 1)] is undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP
+
+**Attached**: {F14822}",1415632380,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-w4wbehbgyvkgen7rk24r,task_description,resolved
+"VisualEditor:[Regression wmf7] Uncaught TypeError: Cannot read property 'nodeType' of undefined ,on deleting the content in the Gallery inspector and clicking done",Confirmed -  the error displayed in JS console is exactly as the attached screenshot presents.,1415636725,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-w4wbehbgyvkgen7rk24r,task_subcomment,NA
+VisualEditor: Support discontiguous table selections,"We currently sort of support this is that row/col deletion skips over merged cells, but the user should probably be able to create such a selection themselves. The current canonical form of a table selection is [fromCol,fromRow,toCol,toRow] so this would need to be changed/extended. There are also a lot of places where we assume the selection to be rectangular.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1415623800,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ffnapmr2ezee3boihytc,task_description,open
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,"I dug deeper after filing bug 73201.
+
+1. Type ""abcdef"".
+2. Make ""ab"" italic.
+3. Make ""ef"" italic.
+4. Make ""bcde"" a link.
+
+Result:   ''a[[bcde|b]]''[[bcde|cd''e'']]''f''
+Expected: ''a''[[bcde|''b''cd''e'']]''f''
+
+The result doesn't seem to depend on the order of operations here.
+
+VisualEditor should avoid splitting link annotations.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1415553420,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_description,duplicate
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,Do we need to file a task which requests that?,1436721864,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_subcomment,NA
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,Note that this remains the case even post {T105239} as Parsoid's `scrubWikitext` model doesn't aggressively merge links ahead of other styles.,1436552315,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_subcomment,NA
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,This is essentially also a duplicate of bug 50098; marking as a subsidiary though in case there are specific concerns.,1415618286,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_subcomment,NA
+VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap,"(In reply to Bartosz Dziewoński from comment #0)
+> 3. Make ""ef"" italic.
+
+Actually, you can skip this step, and still get the ""split link"" effect.",1415553626,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nftpjhkmvyq4ip3ojgai,task_subcomment,NA
+VisualEditor: Tables Caption - moving a cursor with keyboard forces a cursor to the begininng of the page,"1. Open a page in VE and insert a table with a caption. Make sure that you have some chunk of text above the inserted table or a block of some content, so the page needs to be scrolled down to the table.
+
+2. Place a cursor in the table caption and press the right arrow on a keyboard to navigate to the end of the caption. Press one more time - the page scrolls up and the cursor is placed at the beginning of the page. 
+
+Note: moving a cursor with the left arrow to the beginning of the caption and pressing it one more time will simply place it at the last character of a previous sentence.",1415228580,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-n4z3dix5blkhrgq34wbj,task_description,resolved
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","This task is about [VisualEditor](https://www.mediawiki.org/wiki/VisualEditor). See its [user guide](https://www.mediawiki.org/w/index.php?title=Help:VisualEditor/User_guide) for general information.
+
+In the VisualEditor, click the ≡ icon, click ""Options"", and choose ""Page Settings"".
+If someone puts an invalid page name / page title in the ""Target page for [redirection](https://www.mediawiki.org/wiki/Help:Redirects)"" field (like the page name ""Talk:"" or a page name with a pipe character `|` in it), and tries to apply the changes, an exception is caused and the editor is locked up. 
+
+The ""Apply Changes"" button should be disabled when the input is not valid (like in e.g. the ""Insert ➙ Media"" dialog when file dimensions are invalid). 
+
+You are expected to provide a patch in Wikimedia Gerrit. See https://www.mediawiki.org/wiki/Gerrit/Tutorial for how to set up Git and Gerrit.",1415132640,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_description,resolved
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","Change 470914 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Blocked apply if redirect address is invalid
+
+[[https://gerrit.wikimedia.org/r/470914]]",1541110624,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","Change 470914 had a related patch set uploaded (by Flutterish; owner: Flutterish):
+[mediawiki/extensions/VisualEditor@master] Blocked apply if redirect address is invalid
+
+[[https://gerrit.wikimedia.org/r/470914]]",1541021017,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",https://codein.withgoogle.com/tasks/5265052258009088/,1540301191,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",I would like to mentor this task in #Google-Code-in-2018.,1540269636,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","This is still a problem. Typing in an invalid page title (e.g. ""A<B"") and trying to apply the changes causes an exception and locks up the editor. The button should be disabled when the inputs are not valid (like in e.g. the media dialog when file dimensions are invalid).",1540269625,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",">>! In T74971#1486465, @Krenair wrote:
+> Right now it shows the red outline around the textbox when you try to do this. Do we want to block it from saving somehow? Show a warning and automatically set it back to the previous value?
+
+Sounds good.",1442345069,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",Right now it shows the red outline around the textbox when you try to do this. Do we want to block it from saving somehow? Show a warning and automatically set it back to the previous value?,1438035786,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","So I looked into the code - MWTitleInputWidget (used for redirects and templates) vs. MWLinkTargetInputWidget (links)
+I think a lot of the request/response handling code in MWLinkTargetInputWidget should probably be shared, it shows a lot of things in the result like title validity ('legality'), existence of the exact query, external links, exact matches, etc.",1421805281,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it","I was testing with characters like <>, pipes, etc.
+
+```#REDIRECT [[Talk:]]```
+
+comes up for ""Talk:"", but gets rendered as a numbered list element with a broken link by the MW parser.",1421804635,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it",```#REDIRECT [[MediaWiki:Badtitletext]]```,1421804505,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-aex5t4ko5dxm65ucfnyl,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again","Betalabs
+
+The down arrow to bring up the context menu for Categories is not center aligned.
+
+Compare the screenshots from Betalabs and test2
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14800}",1415128320,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_description,resolved
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again",Verified the fix in production,1415834628,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again",Verified the fix in test2,1415227775,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again",Verified the fix in Betalabs,1415218436,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again","Change 171165 merged by jenkins-bot:
+Fix indicator alignment in MWCategoryItemWidget
+
+https://gerrit.wikimedia.org/r/171165",1415149290,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again","Change 171165 had a related patch set uploaded by Catrope:
+Fix indicator alignment in MWCategoryItemWidget
+
+https://gerrit.wikimedia.org/r/171165",1415148810,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again","Created attachment 17015
+test2
+
+**Attached**: {F14802}",1415128414,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6fk5ybsls3a6cfm65ycp,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Environment- production, beta
+
+1> Cite -> Basic. Type a name in the “Use this Group”. Type some text in the sub-editor to make the insert button active and click to insert.
+2> Cite -> Re Use. Select the Reference from the list.
+3> Notice a label shows up with General References and the Group name momentarily, before the reference gets inserted to the main editor. See the screencast(pause it at 0.07).
+
+In beta, it appears on the top-left corner of the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1415027160,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_description,resolved
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","I can't reproduce this today, I think it has been genuinely fixed at some point in the past 8 years. The interface now looks completely different from the video.",1664897272,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Created attachment 17173
+screen recording
+
+**Attached**: {F15375}",1416431756,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","The bug exists in beta, test, and production. I've attached the screenrecording - it shows the issue somewhat slower than in the previous attachment.",1416430169,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","It turned out that Chrome displays the issue even better than FF. So, better see it there.",1416429768,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Elena, so it does not appear in Betalabs?",1416429502,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Re-tested it  - the bug still exists in test2 and production. The best way to reproduce it 
+
+- use FF
+- when inserting a Basic citation do not use General references- type some other name there",1416429381,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Yes, I saw it again in test2 - it's still not 100% reproducible. 
+
+Now for Re-use references in test2, I got
+Uncaught TypeError: Cannot read property 'length' of undefined VM1516:174ve.ui.MWReferenceDialog.useReference VM1516:174ve.ui.MWReferenceDialog.onSearchSelect VM1516:172oo.EventEmitter.emit VM1507:6ve.ui.MWReferenceSearchWidget.onResultsSelect VM1516:158oo.EventEmitter.emit VM1507:6OO.ui.SelectWidget.selectItem VM1507:147OO.ui.SelectWidget.chooseItem VM1507:148OO.ui.SelectWidget.onMouseUp",1415817517,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","Reopen this issue.Steps to reproduce are the same as above.
+
+See screencast at http://youtu.be/bhaPQLNC4ZU(pause it at 0.05).",1415724673,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",Verified in test2.,1415233257,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference","It looks as the issue is gone  - checked it in betalabs on Safari, FF, Chrome, and IE11.",1415127115,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",Provisionally marking as such.,1415054660,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",I think I might have fixed this in https://gerrit.wikimedia.org/r/170784 (which is the fix for bug 72783).,1415054360,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",Difficult to reproduce - I caught it once in betalabs Chrome. Maybe it related to network connectivity?,1415054312,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",Difficult to reproduce - I caught it once in betalabs Chrome. Maybe it related to network connectivity?,1415054284,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor: [Regression wmf6] A Label appears momentarily, showing all ""Use this Group"" options, when Re-Using a Reference",http://youtu.be/a8rgrcU7Bns,1415027383,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-27d4zngimys4mtw4fiz5,task_subcomment,NA
+"VisualEditor:  References inside galleries being displayed separately, inside the gallery, instead of in the correct <references /> block at the end of the page","Open a page containing some refs, and then a gallery that contains <ref> tags but no <references /> block inside the gallery.  (The references block can be elsewhere on the page.)  For example:
+```
+==Section==
+Hello world.<ref>First footnote</ref>
+
+==Gallery==
+<gallery>
+File:Example.jpg|An image<ref>A footnote for the image</ref>
+</gallery>
+
+==References==
+<references />
+```
+
+In read mode, everything looks right:
+
+> Section
+> Hello world.[1]
+> 
+> Gallery
+> An image[2]
+> 
+> References
+> 1. ^ First footnote
+> 2. ^ A footnote for the image
+
+In VisualEditor, you get this:
+
+> Section
+> Hello world.[1]
+> 
+> Gallery
+> An image[1]
+> 1. ^ A footnote for the image
+> 
+>References
+> 1. ^ First footnote
+
+{F15268}
+
+VisualEditor seems to be inserting a ref block into the gallery, even though none exists at that point on the page.  Also, it restarts the numbers for the gallery.",1414858200,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-afkiouif3sgwwazwgdpk,task_description,duplicate
+"VisualEditor:  References inside galleries being displayed separately, inside the gallery, instead of in the correct <references /> block at the end of the page","Reproducible in Parsoid:
+```
+$ echo -e ""<gallery>\nFile:foo.jpg|A <ref group=""n"">ref one</ref>\n</gallery>"" | node parse
+…
+<ul class=""gallery mw-gallery-traditional"" typeof=""mw:Extension/gallery"" data-mw='{""name"":""gallery"",""attrs"":{},""body"":{""extsrc"":""\nFile:foo.jpg|A &lt;ref group=n>ref one&lt;/ref>\n""}}' data-parsoid='{""dsr"":[0,62,2,2]}' about=""#mwt3"">
+<li class=""gallerybox"" style=""width: 155px"">
+<div style=""width: 155px"">
+<div class=""thumb"" style=""width: 150px;"">
+<div style=""margin:35.5px auto;""><a href=""/wiki/File:Foo.jpg"" class=""image""><img alt="""" src=""//upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/120px-Foo.jpg"" width=""120"" height=""79"" srcset=""//upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/180px-Foo.jpg 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/0/06/Foo.jpg/240px-Foo.jpg 2x"" data-file-width=""300"" data-file-height=""197""/></a></div>
+</div>
+<div class=""gallerytext"">
+<p>A <sup id=""cite_ref-1"" class=""reference""><a href=""#cite_note-1""><span>[</span>n 1<span>]</span></a></sup></p>
+</div>
+</div>
+</li>
+</ul><span about=""#mwt3"">
+</span><p about=""#mwt3""><br/>
+<strong class=""error mw-ext-cite-error"">Cite error: There are <code>&lt;ref group=n></code> tags on this page, but the references will not show without a <code>{{reflist|group=n}}</code> template (see the <a href=""/wiki/Help:Cite_errors/Cite_error_group_refs_without_references"" title=""Help:Cite errors/Cite error group refs without references"">help page</a>).</strong>
+<link rel=""mw:PageProp/Category"" href=""./Category:Pages_with_missing_references_list#Main%20Page""/></p>
+```
+
+Could this be caused by using the <gallery>'s contents as a whole page, thus confusing Cite.php?
+",1427117290,PHID-USER-56wtmb23orq4pu5liyj5,True,PHID-TASK-afkiouif3sgwwazwgdpk,task_subcomment,NA
+"VisualEditor:  References inside galleries being displayed separately, inside the gallery, instead of in the correct <references /> block at the end of the page",Blocked by T49344?,1421377783,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-afkiouif3sgwwazwgdpk,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,"Screenshot
+
+Steps to reproduce
+
+1.Insert a table
+2.Insert a caption ""text2""
+3.Make the caption a bullet point to create a slug above it
+4.Now add some other text in that slug ""text1""
+5.Save the page
+
+Observed Result:
+The order of ""text1"" and ""text2"" gets reversed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15176}",1414786140,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-64flnckmn275gswhshoe,task_description,resolved
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,This looks like it is fixed either in #visualeditor in some way or due to Remex. I followed the steps in the video as best as possible with the current VE design and the text appeared in the expected locations.,1534452609,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,"As mentioned in [[ https://phabricator.wikimedia.org/T76100 | T76100 ]], this was fixed in 2015, in tidy-html5.",1505777544,PHID-USER-vscvrah3yt5mw4fhroiz,False,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,Re-tested and confirmed that this still happens (unsurprisingly).,1469839886,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,Apparently this is a bug with HTMLTidy.,1415203267,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,"Still works on my local machine.
+
+The wikitext produced is:
+{|
+|+
+Foo
+* Bar
+!-
+|
+|}
+
+which looks problematic but locally renders fine as
+
+<table><caption>Foo<ul><li>bar...
+
+but on production and betalabs renders as
+
+<ul><li>bar</li></ul><table><caption>Foo...",1415202452,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,"Created attachment 17004
+video capture
+
+Still reproducible, see the video capture
+
+**Attached**: {F15177}",1415045853,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+MWTidy: Old versions of Tidy break flow content out of <caption> and <table>,Works for me in Chrome & FF.,1415024615,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-64flnckmn275gswhshoe,task_subcomment,NA
+Tables - adding formatted headings  to <visualeditor-table-caption> displays Uncaught TypeError,"1. In VE highlight any portion of an inserted table and add <visualeditor-table-caption>.  
+
+2. Without typing any text in the caption, select any format for headings format - Uncaught TypeError will be displayed.
+
+Uncaught TypeError: Cannot read property 'nodeType' of undefined VM8471:495ve.ce.Document.getNodeAndOffset VM8471:495ve.ce.Surface.focus VM8471:538ve.ui.FormatAction.convert VM8471:661ve.ui.Surface.execute VM8471:629ve.ui.Command.execute VM8471:645ve.ui.Tool.onSelect VM8471:638OO.ui.ToolGroup.onPointerUp VM8471:66OO.ui.PopupToolGroup.onPointerUp VM8471:91jQuery.event.dispatch load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141030T0…:65elemData.handle 
+
+3. Attempt to delete the added caption displays: 
+
+Uncaught Error: Unbalanced set of replace operations found (program):321ve.dm.TransactionProcessor.processors.replace (program):321ve.dm.TransactionProcessor.executeOperation (program):314ve.dm.TransactionProcessor.process (program):314ve.dm.Document.commit (program):390ve.dm.Surface.changeInternal (program):366ve.dm.Surface.change (program):365ve.dm.SurfaceFragment.change (program):370ve.dm.SurfaceFragment.delete (program):380ve.ce.Surface.handleLinearDelete (program):578ve.ce.Surface.onDocumentKeyDown (program):546ve.EventSequencer.callListener (program):257ve.EventSequencer.onEvent (program):254(anonymous function) (program):252jQuery.event.dispatch load.php:65elemData.handle
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1414771500,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-7jjbl4wy6ynwsfmld2oj,task_description,resolved
+Tables - adding formatted headings  to <visualeditor-table-caption> displays Uncaught TypeError,Verified the fix in production.,1416435285,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-7jjbl4wy6ynwsfmld2oj,task_subcomment,NA
+Tables - adding formatted headings  to <visualeditor-table-caption> displays Uncaught TypeError,Verified the fix in test2.,1415909982,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-7jjbl4wy6ynwsfmld2oj,task_subcomment,NA
+Tables - adding formatted headings  to <visualeditor-table-caption> displays Uncaught TypeError,Fixed in master.,1415883590,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7jjbl4wy6ynwsfmld2oj,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page woth VE
+2.Add a basic reference
+3.Re -use that reference
+4.Open the reference dialog for the re-used reference
+5.Open the dropdown for the Use this group comb box 
+
+Observed Result:
+Cannot see any groups names there as its getting cut off
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15043}",1414701900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nkev4xvcykpxkczstis2,task_description,resolved
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box",Verified the fix in production,1415835051,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nkev4xvcykpxkczstis2,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box",Verified the fix in Betalabs and test2,1415061470,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nkev4xvcykpxkczstis2,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box","**gerritadmin** wrote:
+
+Change 170176 merged by jenkins-bot:
+Add forgotten $overlay pass-through in MWReferenceDialog
+
+https://gerrit.wikimedia.org/r/170176",1414796058,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nkev4xvcykpxkczstis2,task_subcomment,NA
+"VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the ""Use this group"" combo box","**gerritadmin** wrote:
+
+Change 170176 had a related patch set uploaded by Catrope:
+Add forgotten $overlay pass-through in MWReferenceDialog
+
+https://gerrit.wikimedia.org/r/170176",1414705857,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nkev4xvcykpxkczstis2,task_subcomment,NA
+VisualEditor: No indication in the toolbar what text styles are active because they're in a menu,"screenshot
+
+Screenshot show my cursor within a string of bold text. However the toolbar menu button doesn't change to indicate that text-formatting is currently active. 
+
+This is particularly a problem if I place my cursor at the *end* of a string of bold/formatted text, as I cannot know at-a-glance, whether the text I'm about to type will come out formatted in some way.
+
+In many other programs/sites (eg. gmail, gdoc), there is always an onscreen indicator (usually the button appears ""pressed""), which helps me understand whether text-formatting is active or not.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14998}",1414695900,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-kcaluu7rsxygp57ew5gr,task_description,open
+VisualEditor: No indication in the toolbar what text styles are active because they're in a menu,"The button also appears pressed in VisualEditor, it's just that it's pushed down to a sub-menu so it's not obvious. This is the same as e.g. Google Mail's editing interface, but it can be a bit perplexing, yes.",1414773893,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kcaluu7rsxygp57ew5gr,task_subcomment,NA
+"VisualEditor: Switching out the image clears the ""link"" parameter","Steps to reproduce:
+* Went to my user page, mw:User:Adamw .
+* Clicked ""Edit"" to use the VisualEditor.
+* Clicked the thumbnail at the top, to edit.
+* Clicked the image title to open the editor dialog.
+* Clicked ""Choose a different image"".
+* Pasted the name of an image into the search field, and selected my image.
+* Apply changes.
+* Save chages to page.
+
+This all seemed to go swimmingly, until I looked at the diff:
+
+https://www.mediawiki.org/w/index.php?title=User%3AAdamw&diff=1246151&oldid=1041988
+
+The ""link"" parameter is missing.
+
+Client system: Linux, FF 32.0.3
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1414657080,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-bxani2nv3phs5oyyziql,task_description,open
+"VisualEditor: Switching out the image clears the ""link"" parameter","(In reply to Adam Wight from comment #1)
+> I gave it a second try, and went to add the missing parameter with VE.  It
+> was not supported anywhere...
+
+Indeed. This is an exceptionally rare piece of wikitext we don't support yet.",1414692926,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bxani2nv3phs5oyyziql,task_subcomment,NA
+"VisualEditor: Switching out the image clears the ""link"" parameter","I gave it a second try, and went to add the missing parameter with VE.  It was not supported anywhere...",1414657229,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-bxani2nv3phs5oyyziql,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations","Environment- test2, beta, production
+
+1> insert an external link to a blank page. Number generated for this link is “1”.
+2> hit enter a couple of times, to move the cursor down
+3> Click to insert media ,in the media settings dialog enter  the same external link in the caption sub-editor.Click to insert.
+4> notice the auto-numbers generated beside the external links.Number generated for the link in media is “2”.
+5> Save the page. And notice that the media file external link’s auto-number has now changed to #1 and the external link in the page is #2.
+
+See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1414507740,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-lecf6oguwzmplvfamo26,task_description,open
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations","This feels like we should fix this in MediaWiki rather than in VisualEditor. Alternatively, we could just wait for Parsoid HTML for read mode to come along, which fixes this that way instead. Meh.",1415055839,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations",Confirmed in betalabs - the steps to reproduce the bug are exactly as described by Ritu.,1414802758,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations","Created attachment 16928
+Numbers change after saving the document
+
+**Attached**: {F15282}",1414508298,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations","Created attachment 16927
+Auto numbers generated before saving the page.
+
+**Attached**: {F15281}",1414508236,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+"VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations",See screenshots.,1414508161,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-lecf6oguwzmplvfamo26,task_subcomment,NA
+Editing has become awfully slow,"Timing response editing at enwiki
+
+The save operation has become very slow lately, and it seems to have accelerated this month, possibly in the middle of this month (October).
+
+I did a test edit and the first POST request with submit action took 20562 ms, aka the ""save"". The later GET request on the page took 12627 ms. Some users report edit delays in the order of a minute or more.
+
+This is on a 75Mbps symmetric fiber line, using HTTPS, with Firefox browser on Ubuntu 14.10. Other users have experienced this problem on other platforms and browsers, and both when they are logged in and not logged in.
+
+Preferences for my part is pretty standard, I can make an export if necessary, but as this is reported from several users editing at several sites I don't think this has anything to do with preferences.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Whiteboard**: aklapper-moreinfo
+
+**Attached**: {F15172}",1414441560,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-p67up43jsphy5tblzmnk,task_description,declined
+Editing has become awfully slow,"No reply from @jeblad. :(
+
+Hence closing as declined.",1426776217,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,@jeblad: Still an issue?,1424082908,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,"This is very worrisome and I should not have let it slip my attention. @jeblad, what is the current status?",1422000181,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,Hmm. Would be good to know if that happened again.,1416222248,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,"This is about 1-2 weeks prior to the bug. It seems like the response time is back to normal now. A POST after an edit is 7.853 s and the following GET is 5.381 s. Slow but not awfully slow.
+
+I tested this (both now and the previous report) with classic editing, I don't know how the other users were editing.
+
+Last edit on [[w:no:Bagn]].[1] Previous edit on [[w:en:Norway]].[2]
+
+I suspect some heavy background processing slowed the system to a crawl, and it is now done.
+
+[1] https://no.wikipedia.org/w/index.php?title=Bagn&diff=13509266&oldid=13254424
+[2] https://en.wikipedia.org/w/index.php?title=Norway&diff=631363149&oldid=631261705",1415693274,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,"Sorry for the late response.
+
+(In reply to jeblad from comment #0)
+> reported from several users editing at several sites
+
+Any links? Which timeframe is this about?
+
+Does this only refer to ""classic"" editing or VisualEditor or both?",1415195320,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+Editing has become awfully slow,"For a discussion at nowiki, see https://no.wikipedia.org/w/index.php?title=Wikipedia:Tinget&oldid=13483198#Hva_er_det_som_skjer_her_.3F.3F.3F.3F",1414441827,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-p67up43jsphy5tblzmnk,task_subcomment,NA
+"VisualEditor:[Regression wmf5] Inserting a Link target after a text,instead gets added in between the typed text.","Environment- beta, test2,production
+
+1>In a blank page in VE,type in some text in paragraph format.
+2>Enter a space and select to insert a link. Type in some text in the link input box and keep the inspector open.
+3>Now while the inspector is open, click on to add a bullet/numbered list.
+4>Notice the list gets added and deleted quickly and the link target gets inserted in between the text(right before the last character of the previously typed text). See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: Windows XP",1414422900,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3ptsttym6kp4s3cf6ppu,task_description,resolved
+"VisualEditor:[Regression wmf5] Inserting a Link target after a text,instead gets added in between the typed text.",This seems to have been fixed.,1508929909,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-3ptsttym6kp4s3cf6ppu,task_subcomment,NA
+"VisualEditor:[Regression wmf5] Inserting a Link target after a text,instead gets added in between the typed text.","Confirmed in test2 - it happens for sure, but not quite noticeable. It's somewhat more noticeable in FF than in Chrome.",1415057606,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3ptsttym6kp4s3cf6ppu,task_subcomment,NA
+"VisualEditor:[Regression wmf5] Inserting a Link target after a text,instead gets added in between the typed text.",http://youtu.be/RwVvvlI9rcI,1414423053,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3ptsttym6kp4s3cf6ppu,task_subcomment,NA
+VisualEditor: Don't allow whitespace-only comments to be inserted,"screenshot of the comment popup
+
+Environment- test2,beta,production
+
+1> In VE, select to insert a comment.
+2> When the dialog opens just enter space in the text area and click Done.
+3> Notice the comment popup’s appearance (appears to be smaller, than the regular size).See screenshot.
+4> Click on the popup. Notice the Edit comment box's textarea is empty  with no space taken up for the whitespace characters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15118}",1414421400,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-nosrxhvqlznucmrj62x4,task_description,resolved
+VisualEditor: Don't allow whitespace-only comments to be inserted,"Change 205567 merged by jenkins-bot:
+ve.ui.WhitespacePreservingTextInputWidget: Trim whitespace in input
+
+[[https://gerrit.wikimedia.org/r/205567]]",1429663674,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nosrxhvqlznucmrj62x4,task_subcomment,NA
+VisualEditor: Don't allow whitespace-only comments to be inserted,"Change 205567 had a related patch set uploaded (by Bartosz Dziewoński):
+ve.ui.WhitespacePreservingTextInputWidget: Trim whitespace in input
+
+[[https://gerrit.wikimedia.org/r/205567]]
+",1429610641,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nosrxhvqlznucmrj62x4,task_subcomment,NA
+VisualEditor: Don't allow whitespace-only comments to be inserted,"Confirmed - a Comment with white spaces can be saved. Generally
+
+- it is not possible to create an empty comment
+- if all text is deleted from the comment - it cannot be saved
+- leading and trailing white spaces are not preserved upon saving 
+
+If you re-open the saved Comment with white spaces and click Done - the comment will be recognized as an empty comment and deleted.",1415058127,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-nosrxhvqlznucmrj62x4,task_subcomment,NA
+Escape brackets in URLs of new/changed links,"It would be nice if the VisualEditor dialogs were able to escape (percent-encode) URLs as this one in a way that makes them work in wikitext.
+
+Currently it fails to do so both when changing an existing URL https://it.wikipedia.org/w/index.php?title=PAGEPress_Publications&diff=68792069&oldid=68792024 and when adding it from scratch. I had to manually use urlencode: as usual in wikitext.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: http://doaj.org/search?source={%22query%22:{%22filtered%22:{%22query%22:{%22query_string%22:{%22query%22:%22Italy%22,%22default_operator%22:%22AND%22}},%22filter%22:{%22bool%22:{%22must%22:[{%22term%22:{%22_type%22:%22journal%22}},{%22term%22:{%22index.publisher.exact%22:%22PAGEPress%20Publications%22}}]}}}}}",1414071720,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-4z3rc5r4dabblz4yjn64,task_description,open
+Escape brackets in URLs of new/changed links,"> I am not sure what Parsoid should do here.
+
+Nor do I. :) The VisualEditor dialog should percent-encode URLs (feature request); whether such an operation involves Parsoid I don't know.",1425571434,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-4z3rc5r4dabblz4yjn64,task_subcomment,NA
+Escape brackets in URLs of new/changed links,"I am not sure what Parsoid should do here. When given a string that is a parameter to a transclusion, Parsoid doesn't know that the string happens to be a uri.
+
+Parsoid does handle escapable characters in links correctly where it is clear that the entire string is a url (as below).
+
+[subbu@earth lib] echo '<a rel=""mw:ExtLink"" href=""http://foo.bar?q=[foo]&s=[bar]"">baz</a>' | node parse --html2wt
+[http://foo.bar?q=&#x5B;foo&#x5D;&s=&#x5B;bar&#x5D; baz]
+
+Am I missing something?",1422988055,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-4z3rc5r4dabblz4yjn64,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Type a text
+3.Apply a link on the text
+4.Reopen the link inspector for it
+
+Observed Result:
+The link suggestions are appearing in a broken way .See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15372}",1414017480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fkh5and23bnoi3f25rdh,task_description,resolved
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,I cannot reproduce this on my mobile device.,1429569157,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,"In an actual mobile device,it appears broken for a split second, then again gets back to normal after that.",1415220722,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,"Created attachment 17044
+broken in FF
+
+It is still appearing broken in Firefox
+
+**Attached**: {F15373}",1415219884,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,Appears to now be fixed having tested with an iPad against Beta Labs.,1415147816,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile,Cannot reproduce.,1415068539,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-fkh5and23bnoi3f25rdh,task_subcomment,NA
+"VisualEditor: Banish the TOC and section edit link controls from the main page settings page, and show the display title one instead","Fram says that the ""Page settings"" item should be the three items most commonly wanted by encyclopedia article editors:
+
+* redirect
+* disambiguate
+* displaytitle
+
+and that all the other options should be ""Advanced settings"" (or not displayed at all as described in {T74396}).
+",1414016400,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-dggw3rzo3qdyf7wa5for,task_description,open
+"VisualEditor: Banish the TOC and section edit link controls from the main page settings page, and show the display title one instead","(In reply to WhatamIdoing from comment #0)
+> Fram says that the ""Page settings"" item should be the three items most
+> commonly wanted by encyclopedia article editors:
+> 
+> * redirect
+> * disambiguate
+> * displaytitle
+
+Where's the data to prove this prioritisation is accurate? (That's not to say the current list is good, but it's based on the MediaWiki manuals for ""simple"" controls.)
+
+(I've re-written the title to make it an actual ask.)",1414016788,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dggw3rzo3qdyf7wa5for,task_subcomment,NA
+VisualEditor: Provide a way to configure per-wiki which meta dialog items are available for each namespace,"Under ""Advanced settings"" in the Page options menu, there are two items:
+
+  ""Let this page be indexed by search engines""
+
+and
+
+  ""Show a tab on this page to add a new section"" 
+
+that should never be changed for Wikipedia articles.  (This will differ for other projects; both of these might be appropriate at Meta, for example.)
+
+Could these options be hidden at projects where they should not be used?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414016220,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-kt5s3xm5kkxkenmgo25a,task_description,open
+VisualEditor: Provide a way to configure per-wiki which meta dialog items are available for each namespace,"Do-able. Hard and messy, but do-able.",1414016548,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kt5s3xm5kkxkenmgo25a,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"Environment- beta.
+
+1> In VE, insert a comment. Click done.
+2> click to undo while the comment is still highlighted. Notice the label on the Comment  first changes to read “Comment” from the actual comment text, before removing it. See screencast.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1413903900,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_description,resolved
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,Verified the fix in test2.,1416440487,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,Verified the fix in beta.,1416348293,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"**gerritadmin** wrote:
+
+Change 173808 merged by jenkins-bot:
+Make changes to comment node before apply staging stack
+
+https://gerrit.wikimedia.org/r/173808",1416248155,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"**gerritadmin** wrote:
+
+Change 173808 had a related patch set uploaded by Esanders:
+Make changes to comment node before apply staging stack
+
+https://gerrit.wikimedia.org/r/173808",1416231589,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"(In reply to Alex Monk from comment #3)
+> This seems to be because the first undo you make only clears the comment
+> -text- change. The second undo actually removes the comment node itself.
+> This makes sense since you make the comment node and it goes in the document
+> first, then later insert some text into it.
+> ContextItemWidget#getDescription falls back to the tool's title if the text
+> was falsey (so, an empty string), which is why you see 'Comment' rather than
+> an empty box. This also seems reasonable.
+> 
+> We should probably be removing an empty comment node from the document if
+> it's left there due to undo... Currently this only appears to be done if you
+> have an open comment inspector with no text and then click outside it (see
+> CommentInspector#getTeardownProcess).
+
+This sounds like it was caused by Ed's ""staging empty comment node"" change. That code should ensure that the creation of the comment node and setting the value are one entry in the undo stack.",1414015326,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,"This seems to be because the first undo you make only clears the comment -text- change. The second undo actually removes the comment node itself. This makes sense since you make the comment node and it goes in the document first, then later insert some text into it.
+ContextItemWidget#getDescription falls back to the tool's title if the text was falsey (so, an empty string), which is why you see 'Comment' rather than an empty box. This also seems reasonable.
+
+We should probably be removing an empty comment node from the document if it's left there due to undo... Currently this only appears to be done if you have an open comment inspector with no text and then click outside it (see CommentInspector#getTeardownProcess).",1414014355,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,Confirmed in Beta(test2 and production do not have that issue).,1413915756,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation,http://youtu.be/ws3ObsyZijc,1413904190,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-56tbfvr6vp46m2ctcdjg,task_subcomment,NA
+VisualEditor: [Regression wmf4] Language context menu appears outside the Content Editor,"Language context menu appearing outside the editor
+
+Environment-test2, beta
+
+1> Insert some Language in RTL direction.
+2> insert a comment in the language text, right before the last word. Notice the word moves to the start of line.
+3> Now place the cursor at the end of the last char in the langauge text, notice the language context menu appears outside the editor on the top left of page.See screenshot.
+
+It happens only when the cursor is at the last character.
+
+Refer bug 71320 screencast, in case the above steps sound confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15040}",1413828000,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-33nc2htx3qd2h333vhm6,task_description,resolved
+VisualEditor: [Regression wmf4] Language context menu appears outside the Content Editor,Fixed by Ed.,1414003086,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-33nc2htx3qd2h333vhm6,task_subcomment,NA
+VisualEditor: [Regression wmf4] Language context menu appears outside the Content Editor,Confirmed test2 and Betalabs on Chrome.,1413835085,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-33nc2htx3qd2h333vhm6,task_subcomment,NA
+VisualEditor: Create a meta dialog panel for setting page status indicators,"Not quite sure how this will work (and how it will know which ones are available), but this would probably be rather useful.
+
+https://www.mediawiki.org/wiki/Help:Page_status_indicators is no longer blank. :-)
+",1413586320,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-u5halrjaknddtmd56on4,task_description,open
+VisualEditor: Create a meta dialog panel for setting page status indicators,"PSI's can contain arbitrary wikitext so ideally their contents would be editable in a SurfaceWidget, however I suspect in most situations they will be transcluded onto the page and therefore not editable at all.",1415402400,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-u5halrjaknddtmd56on4,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Advanced media dialog is shown with horizontal scrollbars because button labels don't fit.
+
+{F15974499}",1413560700,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_description,resolved
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,That'll do it.,1523287949,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Change 422138 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] ve.ui.MWMediaDialog: Use dropdown for image type selector
+
+[[https://gerrit.wikimedia.org/r/422138]]",1522926143,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Change 422138 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] ve.ui.MWMediaDialog: Use dropdown for image type selector
+
+[[https://gerrit.wikimedia.org/r/422138]]",1522154486,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Reciting myself from T190462:
+> No regression to my knowledge. We once discussed a compromise as solution in T112982 with Ed being against the proposal. We'd need a constructive idea…
+I was hoping for inputs by @Esanders – if spilling one button on next line seems insufficient, how about calculating the available horizontal size and putting all of them underneath each other when above?
+",1522112167,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Finally, this has also become a problem in English.",1522107799,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"This is still a problem with the new dialog and the new design, I updated the screenshot.",1422093725,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,"Well, given that we're replacing this dialog with a new design which will be wider (as we'll have now drawer), and it's only in the ""advanced"" section, it's maybe not worth worrying for now? Eh.",1413563517,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,Not really.,1413563107,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+Advanced media dialog is shown with horizontal scrollbars because button labels don't fit,Can we improve the translations?,1413562188,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-44vu7zrafitz5rmbpcac,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"Un-used function. Clean-up is good. Etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413498240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tp7hcgumrrewgducy7rw,task_description,resolved
+VisualEditor: Remove ve.bind(),"**gerritadmin** wrote:
+
+Change 171002 merged by jenkins-bot:
+[BREAKING CHANGE] Remove the ve.bind function
+
+https://gerrit.wikimedia.org/r/171002",1415909089,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"**gerritadmin** wrote:
+
+Change 171002 had a related patch set uploaded by Jforrester:
+[BREAKING CHANGE] Remove the ve.bind function
+
+https://gerrit.wikimedia.org/r/171002",1415128593,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"**gerritadmin** wrote:
+
+Change 169644 merged by jenkins-bot:
+Remove more references to ve.bind
+
+https://gerrit.wikimedia.org/r/169644",1414703073,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"**gerritadmin** wrote:
+
+Change 169644 had a related patch set uploaded by Alex Monk:
+Remove more references to ve.bind
+
+https://gerrit.wikimedia.org/r/169644",1414547161,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+VisualEditor: Remove ve.bind(),"<James_F> Krinkle: Thoughts on actually removing ve.bind rather than just removing its use?
+<Krinkle> James_F: Not just yet. Maybe in 1-2 weeks time?
+<James_F> Krinkle: For whom do you think we should wait?
+<Krinkle> James_F: documentation, community, etc.
+<James_F> Krinkle: Eh.
+<Krinkle> James_F: We may not have a public API yet, but that doesn't mean it's cool to break stuff without at least giving them the chance to fix is.
+<Krinkle> random google search: https://www.mediawiki.org/wiki/VisualEditor/Adding_instrumentation_how-to
+
+resolved later",1413500943,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-tp7hcgumrrewgducy7rw,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Screenshot
+
+Steps to reproduce:
+
+1.Open any page with VE in Betalabs using Firefox
+2.Go to Insert>Media
+3.Search for any image and select it to add it in the page
+
+
+Observed Result:
+The image gets added to the page but in the console there is an error:
+
+Image corrupt or truncated: http://upload.wikimedia.org/wikipedia/commons/1/1b/Ko_BuWe.jpg
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15306}",1413421680,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_description,resolved
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Deeming as resolved, then.",1418946432,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs",I haven't seen it recently.,1415644575,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs",Rummana/Elena: Have either of you seen this issue recently?,1415643712,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","(In reply to James Forrester from comment #15)
+> Did we decide to declare this a ""ghost in the machine"" and move on?
+
+If Roan didn't notice the cause in the above debug, I'm not sure who ask to look deeper. It seems the wrong request is being made, right?",1414511160,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Did we decide to declare this a ""ghost in the machine"" and move on?",1414448349,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","After additional investigation with Roan.
+
+Revised steps to reproduce:
+ 
+1. In test2 in FF - make sure that you just switched fro Read mode to Edit, or just refresh the browser window.
+
+2. Insert - Media, type 'artist'(without quotes) to display search results.
+
+3. In Console panel you'll see: 
+
+Image corrupt or truncated: https://upload.wikimedia.org/wikipedia/commons/d/db/Artist_drive.JPG
+
+
+In Network panel you'll see that instead of a thumbnail img - 112x149 and https://upload.wikimedia.org/wikipedia/commons/thumb/d/db/Artist_drive.JPG/112px-Artist_drive.JPG, 
+
+the request was made for for 1536x2048 img and
+GET  https://upload.wikimedia.org/wikipedia/commons/d/db/Artist_drive.JPG
+
+The Staus code: 206(not always).
+
+Request/Response headers:
+
+Request headers:
+Host: upload.wikimedia.org
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0
+Accept: image/png,image/*;q=0.8,*/*;q=0.5
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate
+Referer: https://test2.wikipedia.org/w/index.php?title=ET_page&redirect=no&veaction=edit
+Cookie: GeoIP=US:San_Francisco:37.7898:-122.3942:v4
+Connection: keep-alive
+
+Response headers: 
+Accept-Ranges:""bytes""
+Access-Control-Allow-Origin:""*""
+Access-Control-Expose-Headers:""Age, Date, Content-Length, X-Content-Duration, X-Cache, X-Varnish""
+Age:""1652""
+Connection:""keep-alive""
+Content-Length:""2115604""
+Content-Range:""bytes 32419-2148022/2148023""
+Content-Type:""image/jpeg""
+Date:""Thu, 23 Oct 2014 23:43:46 GMT""
+Etag:""6eaae0b7e042739bd4a04e686eab8dea""
+Last-Modified:""Mon, 07 Oct 2013 01:54:56 GMT""
+Server:""nginx/1.1.19""
+Via:""1.1 varnish, 1.1 varnish""
+X-Cache:""cp1048 hit (2), cp1048 frontend miss (0)""
+X-Object-Meta-Sha1base36:""8x65i07x23pfu6j7h8yl33asimaupwx""
+X-Object-Meta-Sha1base36:""8x65i07x23pfu6j7h8yl33asimaupwx""
+X-Timestamp:""1381110895.66655""
+X-Trans-Id:""txc9084137ff28405983d9c-0054498c3f""
+X-Varnish:""431922781 428031845, 3387585776""
+
+
+If you attempt to insert again the same image -  Request URL will be correct:
+https://upload.wikimedia.org/wikipedia/commons/thumb/d/db/Artist_drive.JPG/112px-Artist_drive.JPG",1414178459,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","As far I could see, there were no errors in header request/response. However, 
+
+there is one small thing(may be nothing): 
+
+Image corrupt or truncated: https://upload.wikimedia.org/wikipedia/commons/3/37/African_Bush_Elephant.jpg African_Bush_Elephant.jpg
+
+
+<img class=""ve-ce-focusableNode-highlight-relocatable-marker"" src=""data:image/gif;base64,R0lGODlh…EKAAEALAAAAAABAAEAAAICTAEAOw==""></img>
+
+And the issue still is not reproducible 100% of the time.",1413845423,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Can you look into the contents of the HTTP response (in the Firebug network tab, or a network analysis tool like Fiddler) and check if the content is damaged somehow?",1413833054,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","(In reply to etonkovidova from comment #10)
+> The issue was reproduced in test2.
+
+Which confirms this is not a ""Beta Cluster stability"" issue.",1413829866,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs",The issue was reproduced in test2.,1413829787,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs",I was able to reproduce the bug in FF 33. Look at the attached screenshot:  Screen Shot 2014-10-20 at 11.06.46 AM,1413829275,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Created attachment 16823
+error message for inserted picture
+
+**Attached**: {F15309}",1413828863,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","The two images mentioned in the FF console in the screenshots:
+https://commons.wikimedia.org/wiki/File:Ko_BuWe.jpg
+https://commons.wikimedia.org/wiki/File:Zwaardstootplaat-Rijksmuseum_AK-MAK-1056.jpeg
+
+The first file was loaded directly from Commons, the other from beta Commons.
+
+I don't see why this would be a MediaViewer issue. (Was its appearence somehow correlated with using MediaViewer? MV can cause some oddities on Beta because it sometimes tries to preload thumbnails before they exist, and the resulting 404 gets cached - but this error is not related to that in any way I can see.) Some ideas:
+
+- some sort of local issue? Happens deterministically, but no one else could reproduce...
+- could be an actual image loading error: Firefox seems to emit this error if it fetches the content for an image file and it turns out not to be a valid image. Maybe the file gets truncated somehow (there were a lot of HTTP errors on beta after the HHVM switch, see e.g. bug 72162 - based on Rummana's screenshot, the file is not necessarily served by beta though, so such an error seems unlikely)
+- https://bugzilla.mozilla.org/show_bug.cgi?id=941823 mentions FF errors with large files - the ones mentioned in the bug are in the 100MP range though, while the two files in the screenshots are 10MP
+- there are claims that FF throws this error if you change the src of an image before it is fully loaded (e.g. http://stackoverflow.com/questions/11928878/detect-image-corrupt-or-truncated-in-firefox )
+
+All in all, I would close this as worksforme if no one can reproduce and there are no reports of this happening in the wild.",1413824009,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","From Gergo: https://bugzilla.mozilla.org/show_bug.cgi?id=646090
+
+So, some image is corrupt (or just has had it's file extension changed, which is considered ""corrupt""). Neither Mark H nor Gergo can repro. Rummana is the only person who can right now, right?
+
+Rummana: can you repro with a clean Firefox profile?",1413822680,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","I also can't reproduce this problem (MediaViewer issue?) in Chrome, Safari or Firefox? The error as state would be from the MW media fetching/thumbnailing API it sounds like?",1413569866,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","See also: http://stackoverflow.com/questions/11727219/image-corrupt-or-truncated-in-firefox
+
+This probably isn't a Beta Cluster problem(?) so I'm moving to VE (feel free to move to where ever it really needs to be) on the assumption its a problem in the code (and I don't want it to not be addressed because it's 'hidden' in the Beta Cluster component).",1413501060,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Created attachment 16792
+Screenshot
+
+Hey Greg! I just added the following image in the same page you used, and got the error:
+
+http://en.wikipedia.beta.wmflabs.org/wiki/0.7358261884200304#mediaviewer/File:Zwaardstootplaat-Rijksmuseum_AK-MAK-1056.jpeg
+
+**Attached**: {F15308}",1413497307,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","Created attachment 16790
+Console log in Iceweasel 32.0.3
+
+I can't repro in Iceweasel 32.0.3. I've attached my console log with other warnings though :)
+
+Done on http://en.wikipedia.beta.wmflabs.org/wiki/0.7358261884200304
+
+**Attached**: {F15307}",1413494861,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+"In VE, while adding any image using Firefox getting the error ""Image corrupt or truncated"" in Betalabs","I don't see any such error in the Firefox 32 browser console when inserting the ""Ko_BuWe"" image in VisualEditor on http://en.wikipedia.beta.wmflabs.org.
+
+Also, why is this under ""MediaWiki General""?",1413459610,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-di2oqisjl4wdsto2nyxu,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Open any citation dialog like Cite>Website/book
+
+Observed Result:
+The fields inside Citations dialog are appearing at a much smaller size
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15293}",1413419940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6hvnj3pserezpnqsws3j,task_description,resolved
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,Verified the fix in production,1415835088,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"Created attachment 16987
+Screenshot
+
+Is it okay if the width appears this way in tablet?
+
+**Attached**: {F15295}",1414793420,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,It's not meant to. This is wide enough for tablets and phones.,1414793146,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"Created attachment 16986
+Screenshot
+
+Its still not taking full width .Reopening it.
+
+**Attached**: {F15294}",1414792710,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"confirmed in betalabs. 
+
+Previously it was: 
+oo-ui-textInputWidget {
+	.	
width: 20em;
+}
+
+
+After the fix: 
+.oo-ui-textInputWidget {
+
+	.	
width: 100%;
+	.	
max-width: 50em;
+
+}",1414713131,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"**gerritadmin** wrote:
+
+Change 169968 merged by jenkins-bot:
+Set input/menu widgets to have a max-width expanding to 100% rather than hard-coded
+
+https://gerrit.wikimedia.org/r/169968",1414627725,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"**gerritadmin** wrote:
+
+Change 169968 had a related patch set uploaded by Jforrester:
+Set input/menu widgets to have a max-width expanding to 100% rather than hard-coded
+
+https://gerrit.wikimedia.org/r/169968",1414627517,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE,"This is almost certainly because of the MediaWiki theme; maybe that now actually sets fields' default width, and the previous theme wasn't?",1413817229,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6hvnj3pserezpnqsws3j,task_subcomment,NA
+Collaborative spelling dictionary building tool,"* Originally proposed at at https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_9#Collaborative_spelling_dictionary_building_tool
+* Currently ongoing work: https://www.mediawiki.org/wiki/Collaborative_spelling_dictionary/Progress
+
+There are extensive spelling dictionaries for the major languages of the world: English, Italian, French and some others; at various degrees of coverage, Mozilla has over a hundred, LibreOffice dozens. They help make Wikipedia articles in these languages more readable and professional and provide an opportunity for participation in improving spelling. Many other languages, however, don’t have spelling dictionaries. One possible way to build good spelling dictionaries would be to employ crowdsourcing, and Wikipedia editors can be a good source for this, but this approach will also require a robust system in which language experts will be able to manage the submissions: accept, reject, filter and build new versions of the spelling dictionary upon them. This can be done as a MediaWiki extension integrated with VisualEditor, and possibly use Wikidata as a backend.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1413107460,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_description,open
+Collaborative spelling dictionary building tool,"(In reply to Quim Gil from comment #4)
+> There is a question that as far as I can see hasn't been answered:
+> 
+> > How would such a thing interact with the wiktionary community. Would it
+> > harvest data from them or be a sub project somehow, or is it planned to be
+> > entirely separate?
+> 
+> https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079022.html
+
+In the initial phase of development, the project will aim at making a spelling dictionary for VE. Once this has been achieved, it can then be integrated into Wiktionary later on. 
+This way, it won't remain totally independent of the Wiktionary community forever, rather, it shall aim at improving and increasing the span of the same.",1415377547,PHID-USER-vktcpyhhgydpo36f44uz,False,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+Collaborative spelling dictionary building tool,"There is a question that as far as I can see hasn't been answered:
+
+> How would such a thing interact with the wiktionary community. Would it
+> harvest data from them or be a sub project somehow, or is it planned to be
+> entirely separate?
+
+https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079022.html",1415292669,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+Collaborative spelling dictionary building tool,"(In reply to Daniel Naber from comment #2)
+> I'm not sure, but http://www.dicollecte.org/home.php?prj=fr might do
+> something similar. It should probably be evaluated before starting this
+> project.
+
+This is something very similar to what the project aims to accomplish, just that dicollecte is specific to French. The project takes this up as a challenge (that only the most popular languages have a solid base of spelling dictionaries) and aims to establish spelling dictionaries for lesser popular languages as well.",1414524987,PHID-USER-vktcpyhhgydpo36f44uz,False,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+Collaborative spelling dictionary building tool,"**misc2006** wrote:
+
+I'm not sure, but http://www.dicollecte.org/home.php?prj=fr might do something similar. It should probably be evaluated before starting this project.",1414334292,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+Collaborative spelling dictionary building tool,"Hello everyone!
+
+I read through this project idea and am interested in working on this. 
+Presently what I understand is that the project requires an admin panel to be built such that the suggestions that come through crowdsourcing can be verified by the administrator. This panel will be ready with rights like approving, rejecting, filtering to be given to the administrator so as to ensure only valid words/spellings to be accepted.
+
+Please correct me if I'm wrong.
+
+Also, it would be great if I could be redirected to some bugs that might help me better understand this project.
+
+Thanks!",1413110409,PHID-USER-vktcpyhhgydpo36f44uz,False,PHID-TASK-bcsluv26xq4a6l2nfhtt,task_subcomment,NA
+VisualEditor: Some file permissions are causing lintian warnings,"Dear Sir or Madam,
+
+0) Context
+
+DEB packages of `mediawiki' and many of its extensions, are prepared as part of the WP-MIRROR project (see <https://www.mediawiki.org/wiki/Wp-mirror>). 
+
+1) Lintian
+
+During the build process, `lintian' performs a great number of sanity checks, including seeing if each file has file permissions appropriate to its file type.
+
+When `lintian' sees a non-executable file with 755 permissions, rather than 644, `lintian' will throw a warning like:
+
+W: wp-mirror-mediawiki-extensions: executable-not-elf-or-script usr/share/wp-mirror-mediawiki/extensions/VisualEditor/modules/ve-mw/ui/styles/images/broken-image.png
+
+2) Files which should have permissions set to 644
+
+VisualEditor/modules/ve-mw/tests/browser/Gemfile
+VisualEditor/modules/ve-mw/ui/widgets/ve.ui.MWMediaResultWidget.js
+VisualEditor/modules/ve-mw/ui/widgets/ve.ui.MWMediaSearchWidget.js
+
+3) Technical details
+
+DEB standards version: 3.9.6
+GIT branch: wmf/1.24wmf22
+
+Sincerely Yours,
+Kent
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1413006660,PHID-USER-k3cyvvb2psrntxfcuyyr,False,PHID-TASK-ch2annsbdighe2sljgvb,task_description,resolved
+VisualEditor: Some file permissions are causing lintian warnings,"Change 166275 merged by jenkins-bot:
+Sort out some odd file permissions
+
+https://gerrit.wikimedia.org/r/166275",1413081041,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ch2annsbdighe2sljgvb,task_subcomment,NA
+VisualEditor: Some file permissions are causing lintian warnings,"Change 166275 had a related patch set uploaded by Alex Monk:
+Sort out some odd file permissions
+
+https://gerrit.wikimedia.org/r/166275",1413079320,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ch2annsbdighe2sljgvb,task_subcomment,NA
+VisualEditor: Some file permissions are causing lintian warnings,"https://bugzilla.wikimedia.org/show_bug.cgi?id=71928 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71930 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71931 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71932 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71933 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71934 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71935 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71936 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71937 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71938 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71939 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71940 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71941 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71942 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71943 
+https://bugzilla.wikimedia.org/show_bug.cgi?id=71944",1413070450,PHID-USER-nzp74jejkvrdzynpcb2o,False,PHID-TASK-ch2annsbdighe2sljgvb,task_subcomment,NA
+"VisualEditor: Add an ""open"" button for link nodes too","I'm editing, and I see a plain, unlabeled, auto-numbered link to an external website.  It says ""[2]"".  I can't open that link without exiting VisualEditor.  The link dialog has an option to ""Add label"" but not ""Open link"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412902140,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-7yvphvp4wfoejotflqgu,task_description,resolved
+"VisualEditor: Add an ""open"" button for link nodes too","**gerritadmin** wrote:
+
+Change 168007 merged by jenkins-bot:
+MWLinkNodeInspector: Provide an open button here too
+
+https://gerrit.wikimedia.org/r/168007",1413947057,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-7yvphvp4wfoejotflqgu,task_subcomment,NA
+"VisualEditor: Add an ""open"" button for link nodes too","**gerritadmin** wrote:
+
+Change 168007 had a related patch set uploaded by Jforrester:
+MWLinkNodeInspector: Provide an open button here too
+
+https://gerrit.wikimedia.org/r/168007",1413938165,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-7yvphvp4wfoejotflqgu,task_subcomment,NA
+Support PDF export on private wikis,"mwlib is able to fetch credentials to access content on private wikis, though with some issues.
+
+* http://web.archive.org/web/20110800000000/http://code.pediapress.com/wiki/ticket/747
+** Credentials not used to fetch license page 
+** new – ralf – normal – major – 23 months
+** Needs someone with a private wiki able to set $wgCollectionLicenseURL for testing; not relevant for OCG?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412805660,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-25wimjgt4tsdfufivzhc,task_description,declined
+Support PDF export on private wikis,The [Offline Content Generator](https://www.mediawiki.org/wiki/Offline_content_generator) (OCG) software is dead.,1611522574,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"As already announced in [[ https://meta.wikimedia.org/wiki/Tech/News/2017/37 | Tech News ]], OfflineContentGenerator (OCG) will not be used anymore after October 1st, 2017 on Wikimedia sites. OCG will be replaced by Electron. [[ https://www.mediawiki.org/wiki/Special:MyLanguage/Reading/Web/PDF_Functionality | You can read more on mediawiki.org. ]]",1505380686,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"(In reply to C. Scott Ananian from comment #3)
+> Is the concrete feature request here that we support HTTP authentication
+> (basic? digest?) when contacting the wiki's api.php endpoint?
+
+It depends on what we're asking from the API: are we asking anything that requires read privileges?",1414516085,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"Is the concrete feature request here that we support HTTP authentication (basic? digest?) when contacting the wiki's api.php endpoint?
+
+Have you tried using the 'http://username:password@host/...' format when configuring the API endpoint URL?",1414514286,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"(In reply to C. Scott Ananian from comment #1)
+> This should work, using the instructions for setting up Parsoid to point at
+> a private wiki: 
+
+Nice. But doesn't OCG also contact the web API?",1412831954,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+Support PDF export on private wikis,"This should work, using the instructions for setting up Parsoid to point at a private wiki: 
+https://www.mediawiki.org/wiki/Parsoid/Setup#Configuration
+https://www.mediawiki.org/wiki/Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis
+
+This could stand to be tested and documented better.",1412806048,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-25wimjgt4tsdfufivzhc,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"translate syntax in VE
+
+Translated text should probably not display with syntax in VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14987}",1412653560,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-ddqlzrwdgysvh766ik7s,task_description,resolved
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"As described, this doesn't happen any more. VE + Translate still sucks, but that isn't not this ticket.",1608232349,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"(In reply to James Forrester from comment #4)
+> No, it means the ghastly mess that is {{TNTNTNTNTTNT}} :-)
+
+The screnshot seems to be about this excerpt:
+
+<translate>
+<!--T:21-->
+More details at {{ll|Social media|Social media}}.
+</translate>
+
+{{ll}} only creates a link to Special:MyLanguage (which is not even in Translate now). (In the Translate docs we recommend to use Special:MyLanguage directly, but what can you do.)
+So the summary currently mentions the only thing which is not in the screenshot. :)",1414866828,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"No, it means the ghastly mess that is {{TNTNTNTNTTNT}} :-)",1412812126,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"I assume you mean translate tags as shown in the screenshot, because ""translate templates"" don't exist.",1412750511,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,"Yeah, the Translate extension fundamentally doesn't work with VisualEditor in its current form, as I understand it. Much sadness.",1412716773,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Content inside templates for translation of templates does not render in friendly ways,see https://www.mediawiki.org/wiki/Communication?veaction=edit,1412653611,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-ddqlzrwdgysvh766ik7s,task_subcomment,NA
+VisualEditor: Allow in-line editing/suggesting/flagging of TemplateData when labels are unclear,"unclear fields in an infobox template
+
+some labels are not clear, or have not been given ""human readable"" aliases, providing a way for end users to flag these, or even submit suggestions or edit them directly could help clean these up quickly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14733}",1412370540,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-frzymdkyeby2og65igsx,task_description,declined
+VisualEditor: Allow in-line editing/suggesting/flagging of TemplateData when labels are unclear,"Closing this to clean up our boards. Not to decline the idea. This is still a possibility. But this ticket is very old and probably not very helpful, even when someone attempts to implement this. The dialog looks very different now and usually displays an easy to follow link to the template where the documentation can be edited.",1654869001,PHID-USER-u6ycqhfpa3k4yvlpxjt2,True,PHID-TASK-frzymdkyeby2og65igsx,task_subcomment,NA
+VisualEditor: Allow in-line editing/suggesting/flagging of TemplateData when labels are unclear,"This could get very tricky, but could be useful.",1412376526,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-frzymdkyeby2og65igsx,task_subcomment,NA
+"VisualEditor Mobile: Does not load at all on IE 11 (unknown dependency ""ext.visualEditor.iehacks"")","VisualEditor Mobile does not load at all on IE 11 right now (unknown dependency ""ext.visualEditor.iehacks"", gets stuck displaying the loading spinner).
+
+Either the module needs mobile target, or we need to stop trying to load it on mobile.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1412367420,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-j7ic5u4qfl3yfcnkaw35,task_description,resolved
+"VisualEditor Mobile: Does not load at all on IE 11 (unknown dependency ""ext.visualEditor.iehacks"")","**gerritadmin** wrote:
+
+Change 164649 merged by jenkins-bot:
+Add mobile target to 'ext.visualEditor.iehacks' module
+
+https://gerrit.wikimedia.org/r/164649",1412380482,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-j7ic5u4qfl3yfcnkaw35,task_subcomment,NA
+"VisualEditor Mobile: Does not load at all on IE 11 (unknown dependency ""ext.visualEditor.iehacks"")","**gerritadmin** wrote:
+
+Change 164649 had a related patch set uploaded by Bartosz Dziewoński:
+Add mobile target to 'ext.visualEditor.iehacks' module
+
+https://gerrit.wikimedia.org/r/164649",1412367777,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-j7ic5u4qfl3yfcnkaw35,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"CommentInspector doesn't update its size when the textarea gets resized, only if it's closed and reopened. Split off from bug 71310.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1412021640,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_description,resolved
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"**gerritadmin** wrote:
+
+Change 163674 merged by jenkins-bot:
+ve.ui.CommentInspector: Update size when the textarea gets resized
+
+https://gerrit.wikimedia.org/r/163674",1412817094,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,Spoke too soon.,1412116117,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"**gerritadmin** wrote:
+
+Change 163738 merged by jenkins-bot:
+WindowManager: Emit 'resize' event when a window is resized
+
+https://gerrit.wikimedia.org/r/163738",1412115751,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"**gerritadmin** wrote:
+
+Change 163738 had a related patch set uploaded by Bartosz Dziewoński:
+WindowManager: Emit 'resize' event when a window is resized
+
+https://gerrit.wikimedia.org/r/163738",1412027038,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+VisualEditor: CommentInspector doesn't update its size when the textarea gets resized,"**gerritadmin** wrote:
+
+Change 163674 had a related patch set uploaded by Bartosz Dziewoński:
+[WIP] ve.ui.CommentInspector: Update size when the textarea gets resized
+
+https://gerrit.wikimedia.org/r/163674",1412023540,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xby2gkgrm5h5zubfd7l5,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","When one creates a redirect without filling an edit summary, MediaWiki automatically uses an edit summary to identify that the edit created a redirect. That's very useful. But the autosummary doesn't work if the user fills the edit summary. It also doesn't work when the user edits a redirected page to make it a normal page, by removing the #REDIRECT syntax.
+
+Redirections are very special edits that would be good to have them tagged for review on recent changes and watchlists.
+
+With AbuseFilter one could write some tricky filters to tag those edits, but that's far from ideal.
+
+My proposal is to have at least 2 new tags:
+* One to tag when a redirect is created
+* One when a redirect is removed (not by page deletion, but by removing the #REDIRECT)
+
+It would be nice to also have a tag for when a redirect target is changed (pointing the redirect to another article) and also when a redirect is edited without changing the redirect (like for example adding a category, a comment, or simply content that won't be viewed anyway).
+
+A slight limitation of tags (as I understand) is that they won't display the redirect target as the autosummary does, but that's not important, I think. The autosummary would do the job when present.",1411573320,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_description,resolved
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 194458 abandoned by Krinkle:
+Implement redirect-related and other tags in mediawiki core
+
+Reason:
+Closing for now due to inactivity and to clear review dashboards. The associated ticket appears to have been resolved without this commit.
+
+Feel free to re-open at any time.
+
+[[https://gerrit.wikimedia.org/r/194458]]",1535313488,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 390224 merged by jenkins-bot:
+[mediawiki/core@master] Add new core tags
+
+[[https://gerrit.wikimedia.org/r/390224]]
+",1512067410,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 390224 had a related patch set uploaded (by Catrope; owner: Petar.petkovic):
+[mediawiki/core@master] Add new core tags
+
+[[https://gerrit.wikimedia.org/r/390224]]
+",1511896667,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 311683 abandoned by Cenarium:
+Implement redirect-related and other tags in mediawiki core
+
+Reason:
+I ended up removing the dependencies directly in I2e48bd458fc8d7c289f04dc276f9287516e0b987 so I have only one commit to maintain.
+
+[[https://gerrit.wikimedia.org/r/311683]]",1474575790,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 211497 had a related patch set uploaded (by Cenarium):
+Implement redirect-related and other tags in mediawiki core
+
+[[https://gerrit.wikimedia.org/r/211497]]
+",1474574411,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 311683 had a related patch set uploaded (by Cenarium):
+Implement redirect-related and other tags in mediawiki core
+
+[[https://gerrit.wikimedia.org/r/311683]]
+",1474371254,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1640971, @daniel wrote:
+> what's the status of this? Can we get the patches merged?
+> Hm, seems to be a long chain...
+Lots of dependencies indeed...
+For automated tags, we need a user-friendly drop down menu instead of an input box (since internal tag names are in english and obtuse, e.g. core-move-crossnamespace). It's 211497.
+For the dropdown menu, we need to overhaul the caching so that a list of tags can be efficiently fetched. It's 218265.
+Before overhauling the caching, we need to make several related performance improvements. It's 201905.
+218777 is not essential to this (I might put it in another branch).
+
+>>! In T73236#1641141, @TTO wrote:
+> @daniel, if you have time, Cenarium and I would really appreciate a second opinion on some of these patches, particularly 201905. Anomie is too busy, and I personally have some doubts about `ChangeTagsContext` and would like someone's else's point of view.
+Yes, I would appreciate reviews.
+I've created `ChangeTagsContext` so that the `ChangeTag` class can't be provided with arbitrary hitcounts or tag definitions, in a way that doesn't require unnecessary duplications when multiple `ChangeTag` instances are involved.",1442338021,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@daniel, if you have time, Cenarium and I would really appreciate a second opinion on some of these patches, particularly 201905. Anomie is too busy, and I personally have some doubts about `ChangeTagsContext` and would like someone's else's point of view.",1442319875,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","*bump*
+what's the status of this? Can we get the patches merged?
+
+Hm, seems to be a long chain...
+* https://gerrit.wikimedia.org/r/#/c/194458/
+* https://gerrit.wikimedia.org/r/#/c/211497/7
+* https://gerrit.wikimedia.org/r/#/c/218265/4
+* https://gerrit.wikimedia.org/r/#/c/218777/3
+* https://gerrit.wikimedia.org/r/#/c/201905/28
+",1442312657,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","ArchCom approves: this seems pretty uncontroversial. We have added some reviewers to the patch. If the review doesn't go forward, let us know.",1434573574,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","[[ https://gerrit.wikimedia.org/r/#/c/194458/ | Change 194458 ]] pretty well does what's requested on this bug, so I'd say it could be closed once it's merged",1433445861,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@Cenarium, @Ciencia_Al_Poder: do you think it would be useful to have a discussion on IRC about this soon? Or would you say the patch sets you mentioned would be sufficient to close this? Is there anything more to discuss?",1433368988,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Did anyone work on this task at #wikimedia-hackathon-2015? If do, please share an update. If not, remove the label.",1433137363,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@daniel
+I dunno what you intend to discuss, but FYI the patch set in https://gerrit.wikimedia.org/r/194458 when combined with https://gerrit.wikimedia.org/r/#/c/190656/ allows to resolve T92621, and when also combined with https://gerrit.wikimedia.org/r/#/c/211656/, allows to resolve T14363 as well (from recent changes, not from new pages where performance issues make this impossible IMO).
+",1432521189,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",See {T92621},1432156301,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1283464, @daniel wrote:
+> @Cenarium, @Ciencia_Al_Poder: We (the ArchCom) thinks it may be nice to discuss this RFC at the hackathon in Lyon. Will you be attending?
+
+Me neither",1431629884,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1283464, @daniel wrote:
+> @Cenarium, @Ciencia_Al_Poder: We (the ArchCom) thinks it may be nice to discuss this RFC at the hackathon in Lyon. Will you be attending?
+
+No I won't be attending. What is it in particular that you want to discuss ?",1431624111,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@Cenarium, @Ciencia_Al_Poder: We (the ArchCom) thinks it may be nice to discuss this RFC at the hackathon in Lyon. Will you be attending?",1431550556,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",@Cenarium: We (the ArchCom) thinks it may be nice to discuss this RFC at the hackathon in Lyon. Will you be attending?,1431550512,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","> Should we deactivate the feature by default in mediawiki core ?
+
+Yes.
+
+> (And enable it on WMF wikis.)
+
+That requires a separate discussion IMHO.",1431409004,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1272896, @Nemo_bis wrote:
+> Do we have statistics on how many (non-Wikimedia) wikis consider cross-namespace redirects to be a problem?
+
+I don't think so.
+
+Should we deactivate the feature by default in mediawiki core ?
+(And enable it on WMF wikis.)",1431110020,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",Do we have statistics on how many (non-Wikimedia) wikis consider cross-namespace redirects to be a problem?,1431108703,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@daniel I haven't implemented any of the controversial aspects.
+
+The first one being the ability to activate / deactivate these tags directly from Special:Tags, which would require a database change. So we don't need a RFC on this at the moment, but we might revisit this issue if it turns out after implementation that there are requests from the wiki communities for such a feature.
+
+The second one is how to handle these tags for display in a drop down menu. I've given up the controversial idea of having a localizable tag name, instead having a separate message for it which can also be used to prevent the tag from appearing in the drop down menu. I haven't had feedback yet on this proposed solution so I can't say if a RFC might be needed, but I don't see which alternatives we have.",1431100816,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","@Cenarium do you think this should be an RFC? See https://www.mediawiki.org/wiki/Requests_for_comment/Process for the process. If not, feel free to remove the @MediaWiki-RfCs tag.",1430339538,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Assigning to RFC queue, since I think the ArchCom should have a look at this.",1430323269,PHID-USER-5dqihbanu3caaj7pigif,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Change 194458 had a related patch set uploaded (by Cenarium):
+Core-defined automatically added tags
+
+[[https://gerrit.wikimedia.org/r/194458]]
+",1428219966,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I've uploaded a patch set for T91535.
+
+Concerning this request, while I still think we should always endeavor to allow as much onwiki customization as possible, I plan on uploading a patch set that simply uses a config variable as originally suggested by TTO.",1428177574,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Okay, let's get back to what is being requested here and in many other places, and most importantly //why// it is requested. The //only// reason this feature is requested is, ultimately, the constraints imposed by the condition limit of the abuse filter. If no such restriction existed, every one of these tags would already exist as global or local filters. But since the restriction exist, and for good reason, this can't happen.
+
+Log-only and tag-only filters are always the ones that get sacrificed first; it has been like that since the introduction of AbuseFilter, see [[https://en.wikipedia.org/wiki/Wikipedia_talk:Edit_filter/Archive_3#Filter_Reduction|this June 2009 discussion]], and is [[https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Edit_filter&oldid=649616762#Condition_limit|just as true today as it was back then]] (the same holds on other wikis and even more for global filters). There's no change in sight, even if the condition limit can be legitimately criticized, some kind of limit must still exist.
+
+Pretty much all of the potential autotags were added by now deleted abuse filters : [[https://en.wikipedia.org/wiki/Special:AbuseFilter/8|self-redirects]], [[https://en.wikipedia.org/wiki/Special:AbuseFilter/27|making/changing redirects]], [[https://en.wikipedia.org/wiki/Special:AbuseFilter/27|replacing content]], and so on. These can be easily inserted from mediawiki core, most of these edits already create automatic edit summaries. I was even thinking we may want to merge autosummaries and autotags in a single function, since the special casing is very similar.
+
+What end users need is to have these easy autotags defined in core, so that abuse filters can focus instead on more complex tagging or other actions (warn, prevent edits). Therefore, this feature request amounts to a core-implemented tag-only AbuseFilter. The customization aspect is integral to AbuseFilter, and so it should be integral to this feature request. We should start from a level of customization that exactly matches the level of customization afforded by AbuseFilter, and narrow it down only when truly necessary for the implementation.
+
+Now with regard to extensions, I wasn't mentioning visual editor at random here, as I said we had to create filters to keep track of visual editor bugs, see [[https://en.wikipedia.org/wiki/Special:AbuseFilter/577|AF 577]], enabled for months, which, however silly that might look, checked for insertions of ♙, ☃ or ↵, so not exactly adding the letter ""A"" or ""B"", but close ! Same problems occurred with wikilove and other extensions. These filters aren't cheap, extensions should rather make these debugging tags on their end. Some wikis may also want more involved autotags than those defined in core. So I wanted to let this possibility open for future implementation (so we don't tie our hands).
+
+I was thinking of a hook that takes the same params as the autotags function and alters the autotags. If we had a config variable, the extension could add the extra tags to it and let end users do the activation/deactivation. Without it, the extension needs to provide a way for users to make the activation/deactivation. This means a user interface, so more work on the extension's side, when it can be done at Special:Tags. That being said, I'll keep this for later and only focus on core-defined tags for now. So basically the list of tags is hard-coded at ChangeTags.php instead of being provided as a config variable.",1425582205,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1089637, @Legoktm wrote:
+> I haven't followed all of the discussion here, but the patch seems drastically overcomplicated from what we need, which is a way for core to define tags (and then apply them). I would recommend just having a static function which returns core provided tags, similar to the one for extensions.
+That one is already implemented in ContentHandler (I'll need to update it).
+> I don't think there's a solid usecase for being able to disable core provided tags, so we can probably leave that out of the initial implementation.
+I agree it isn't essential to allow un-defining the autotags in the initial implementation, so I'll ditch the config variable, which is by far the most complicated aspect. Users and extensions will thus be unable to unset core tags, or only for the later though a hook that we might implement later on, if needed.
+
+>>! In T73236#1090941, @TTO wrote:
+> I like the idea of namespacing the tags. It's not currently done by most extensions, but it would be a good precedent to set. For example, `mw-redirected` or `mw-redirect-removed`. As I said, users should never have to interact with these names, except in the first column of Special:Tags and when using the API.
+I'm just pointing out here that the solution of parsing the tag description for display may be quite remote and more complex than it seems, we would need to rewrite tag filtering, abuse filter's handling of tags and many other things. What can we do in the mean time ? We shouldn't force users to use English text or arcane internal ids in order to filter recent changes. This effectively means that for many users in English language wikis and most users in other language wikis, those tags are completely useless everywhere except when accessed directly from Special:Tags. Note that localization wouldn't be a problem for external clients for those special purpose tags like it would be for visualeditor, and if needed they could retrieve the id by checking the wfmessage.
+>> In core, admins control the tags, not extensions, so they should also be able to rename them (in case of conflict, for example). 
+> 
+> Not really. What we're developing here is essentially another tag-applying extension (using automated logic to apply tags, just like OAuth, AbuseFilter, VisualEditor et al) but built into MW core. So this feature should behave like an extension, not like the newly-added manual tagging stuff in core. When extensions apply tags using automated logic, they have control over their tags' names etc. Likewise, when core uses automated logic to apply tags, core should control the tags. Extensions are free to provide a way to turn tags on and off; core can do the same (or, as Legoktm says, not).
+Except admins have complete control on extensions like AbuseFilter, and this autotagging feature is nothing but a core-implemented tag-only AbuseFilter (which makes it much more efficient), that's the request at any rate. If it isn't customizable enough, or end users can't understand the purpose, it won't get used.
+> What you are trying to create is a weird hybrid of extension-based tagging and manual tagging, which seems to be the main bone of contention here.
+I'll give up on the optionally defined part which can be addressed later on if needed. I still consider the i18n issue unresolved, but I'll ditch the localized messages for now.",1425523869,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I am in full agreement that localising tag names, which are purely meant as internal IDs, is wrong. The only place users should see these names in the UI is in the first column of Special:Tags. This is not currently the case - the tag filter input box and the AbuseFilter edit page being the most obvious places where the raw tag name is used - but the solution is to use the `tag-$tag` system message in those places, not to localise the internal ID. 
+
+Not only that, but it leads to difficulty for external consumers of the recentchanges API, as well as problems when trying to provide default tag description messages. 
+
+I like the idea of namespacing the tags. It's not currently done by most extensions, but it would be a good precedent to set. For example, `mw-redirected` or `mw-redirect-removed`. As I said, users should never have to interact with these names, except in the first column of Special:Tags and when using the API.
+
+> In core, admins control the tags, not extensions, so they should also be able to rename them (in case of conflict, for example). 
+
+Not really. What we're developing here is essentially another tag-applying extension (using automated logic to apply tags, just like OAuth, AbuseFilter, VisualEditor et al) but built into MW core. So this feature should behave like an extension, not like the newly-added manual tagging stuff in core. When extensions apply tags using automated logic, they have control over their tags' names etc. Likewise, when core uses automated logic to apply tags, core should control the tags. Extensions are free to provide a way to turn tags on and off; core can do the same (or, as Legoktm says, not).
+
+What you are trying to create is a weird hybrid of extension-based tagging and manual tagging, which seems to be the main bone of contention here.",1425517721,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I haven't followed all of the discussion here, but the patch seems drastically overcomplicated from what we need, which is a way for core to define tags (and then apply them). I would recommend just having a static function which returns core provided tags, similar to the one for extensions.
+
+I don't think there's a solid usecase for being able to disable core provided tags, so we can probably leave that out of the initial implementation.
+
+",1425497726,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1088558, @Anomie wrote:
+>> I'm indeed referring to the tag's name. IMO, it's a must have since it appears when filtering recent changes & co.
+> 
+> And yet no tag-using extension does this. Why should core?
+Extension-controlled tags are a different issue altogether, allowing admins to change the name for 'visualeditor' would cause issues, since we don't have a good rename mechanism yet. Localizing now would mean breaking the tags so it may no longer be worth it. But from now on, I think they should definitely use for new tags a localized name, that admins can't modify. In core, admins control the tags, not extensions, so they should also be able to rename them (in case of conflict, for example). Using a reserved prefix, as I suggested earlier, is not user friendly in light of the second point which I had overlooked initially.
+>> Especially when we'll have a user-friendly way of doing so with a drop-down menu and/or auto-completion or some hybrid of these (T27909 and T23383).
+> 
+> A dropdown menu should display the texts from the ""Appearance on change lists"" column on Special:Tags, making that a non-issue.
+> 
+> Auto-completion might take some more thought, but I still maintain that if i18n is needed then ""Appearance on change lists"" is the column to use rather than trying to have two layers of i18n.
+There would be only one layer of i18n in either case, since the tag appearance is the tag name by default. Using the tag appearance in a drop down would not be appropriate in many contexts : too verbose (some are quite long), parsing issues from wikitext (links, fonts, etc). A dropdown with 100+ entries isn't user friendly either so autocompletion is pretty much needed. The current filtering system, which relies on the tag name, should also be preserved, so switching to its parsed appearance would be quite an issue, not to mention consistency. Realistically, I think using the tag name is the only viable approach.
+>> The use case for VisualEditor is abundant, we could have at least a dozen of optional tags (for adding templates, images, categories, whatever) that could be activated or deactivated when needed as a debugging tool or to track certain types of edits.
+> 
+> I think you're going overboard with adding individual tags for adding and removing templates, images, categories, and so on. What next, ""Added the letter A"", ""Added the letter B""?
+Visual editor has the tendency of creating bugs when adding certain elements - a way of tracking them would be nice. I was not referring to a specific template, just adding a template (any template).
+>>>> - make it possible for admins to make the activation
+>>> 
+>>> Why is this a desired feature?
+>> The question is rather ""Why should we prevent use of this existing feature for those tags ?"" (see below).
+> 
+> Except it's not an existing feature. You're shoehorning it in.
+Tags activated by a config variable aren't an existing feature //at all//, whereas tags activated by admins already exist, although in a different context. This just extends this existing mechanism to the present context.
+>>>> - allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+>>> 
+>>> Where is this being stored? I see absolutely nothing about it in your WIP patch.
+>> It's not in this patch but the one for T89553, i.e. commit [[https://gerrit.wikimedia.org/r/#/c/190656/|980656]].
+> 
+> In which case that has nothing to do with this task: there's no requirement for using your overcomplicated proposal to accomplish this bullet point.
+It is a requirement. Not being able to patrol articles recently expanded from redirects, recently moved into mainspace and such makes those tags pretty much useless in the first place. (How could one know if each item has been dealt with ?) The initial request ([[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_117#Proposed_technical_change:_show_pages_expanded_from_redirects_on_Special:NewPages_and_Special:NewPagesFeed|link]]) was to have these appear at Special:NewPages so that it can be patrolled, but this can't be done so making them patrollable in recent changes is pretty much the only way of implementing this feature request. So we need to have these tags in valid_tag so we can store relevant data. Extension defined tags would store the data on their own end, but for core or user defined tags it's the only sensible way.
+Again it's not overcomplicated, using a second config variable would be just as complicated, and couldn't even match this requirement.
+>> True... I don't understand this objection, admins can activate tags not already defined by an extension or already activated, in the very current and live implementation of ChangeTags. The action and user interface both exist.
+> 
+> Yes, that exists. This whole new class of tags that can be activated by the same mechanism //doesn't// already exist.
+That whole new class of tags that can be activated with a config variable //doesn't// already exist, either. The difference is, the mechanism (config variable) doesn't even exist, whereas admin activation exists already so we might as well use it here too.
+
+Even if you object to the i18n issue, a config variable to define the tags still makes most sense since it can be modified as needed by extensions or wikis. And not adding these tags to the valid_tag table when activating them makes it impossible to customize the tag for the wiki. Admins can't make them patrollable or not as needed, so it's not even worth implementing, a bot-added tag would be better since tagged changes could be patrolled.",1425491671,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1085301, @Cenarium wrote:
+>>>! In T73236#1083545, @Anomie wrote:
+>> As far as I can tell from your non-functional WIP patch, you might be referring to trying to localize the internal tag names. That seems pointless when the tags are already localized for display where applicable.
+> I'm indeed referring to the tag's name. IMO, it's a must have since it appears when filtering recent changes & co.
+
+And yet no tag-using extension does this. Why should core?
+> Especially when we'll have a user-friendly way of doing so with a drop-down menu and/or auto-completion or some hybrid of these (T27909 and T23383).
+
+A dropdown menu should display the texts from the ""Appearance on change lists"" column on Special:Tags, making that a non-issue.
+
+Auto-completion might take some more thought, but I still maintain that if i18n is needed then ""Appearance on change lists"" is the column to use rather than trying to have two layers of i18n.
+
+> The use case for VisualEditor is abundant, we could have at least a dozen of optional tags (for adding templates, images, categories, whatever) that could be activated or deactivated when needed as a debugging tool or to track certain types of edits.
+
+I think you're going overboard with adding individual tags for adding and removing templates, images, categories, and so on. What next, ""Added the letter A"", ""Added the letter B""?
+
+>>> - make it possible for admins to make the activation
+>> 
+>> Why is this a desired feature?
+> The question is rather ""Why should we prevent use of this existing feature for those tags ?"" (see below).
+
+Except it's not an existing feature. You're shoehorning it in.
+
+>>> - allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+>> 
+>> Where is this being stored? I see absolutely nothing about it in your WIP patch.
+> It's not in this patch but the one for T89553, i.e. commit [[https://gerrit.wikimedia.org/r/#/c/190656/|980656]].
+
+In which case that has nothing to do with this task: there's no requirement for using your overcomplicated proposal to accomplish this bullet point.
+
+>>> Again, letting admins do the activation is much easier to implement,
+>> 
+>> False.
+> At least it's what I found out when actually trying to implement the thing (assuming a config variable is used to define tags, IMO a requirement).
+
+That's not very convincing, all things considered.
+
+>>> the current implementation of tags already allows it,
+>> 
+>> False.
+> True... I don't understand this objection, admins can activate tags not already defined by an extension or already activated, in the very current and live implementation of ChangeTags. The action and user interface both exist.
+
+Yes, that exists. This whole new class of tags that can be activated by the same mechanism //doesn't// already exist.",1425482408,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1083545, @Anomie wrote:
+>>>! In T73236#1083158, @Cenarium wrote:
+>> Ok, here's why we need a config variable to define optional tags IMO, it allows to:
+>> - have a neat and efficient 'isset' check instead of ugly 'in_array'
+> 
+> You've given no evidence that this is impossible with any solution other than yours. Or, for that matter, that this is an issue that should drive the implementation.
+I can't imagine and rebut every possible implementation, I would need more specifics, keeping in mind the constraints below.
+
+>> - easily define the wfmessage they should use
+> 
+> The messages used by tags are already clearly defined by how tags work.
+> 
+> As far as I can tell from your non-functional WIP patch, you might be referring to trying to localize the internal tag names. That seems pointless when the tags are already localized for display where applicable.
+I'm indeed referring to the tag's name. IMO, it's a must have since it appears when filtering recent changes & co. How could non-English speakers use these tags to filter recent changes if they can't even understand their purpose? Especially when we'll have a user-friendly way of doing so with a drop-down menu and/or auto-completion or some hybrid of these (T27909 and T23383). The appearance of tags when applied to specific edits is a different issue, it can be very different from the actual tag's name and contain wikitext or links. We have no need to make a default for it, since it's already the tag's name. We may want to make a default for the tag description to further describe its intent, but it would only be seen from Special:Tags directly, not from the tag input box.
+>> - easily unset the default autotags in case an extension wants to provide more specific ones (e.g. with more special casing, usergroups checks, etc, making many of the default ones redundant).
+> 
+> This seems like a requirement without a use case. And if some extension were to want to do this, it hurts nothing for the core tag to remain defined despite being deactivated in LocalSettings.php.
+It does. There are already dozens of defined tags on many wikis. Special:Tags takes quite a while to load on enwiki. If an extension like 'ImprovedBuiltInAutoTags' were to add a dozen or more of tags that would be more customizable than the default core autotags and therefore supersede them, and may also check for things like wikitext errors, the list of tags would become excessively long and confusing with all the redundancies. The use case for VisualEditor is abundant, we could have at least a dozen of optional tags (for adding templates, images, categories, whatever) that could be activated or deactivated when needed as a debugging tool or to track certain types of edits.
+>> Now for activation, doing this with the valid_tag table allows to:
+>> - avoid a second config variable
+> 
+> No need for this if you give up your idea of having the ability to not-even-define core tags.
+Not just this, also localization.
+>> - make it possible for admins to make the activation
+> 
+> Why is this a desired feature?
+The question is rather ""Why should we prevent use of this existing feature for those tags ?"" (see below). If an autotag can be activated by simply clicking on a button named 'activate'/'aktivigi'/'activar'/'rakendama'/'ενεργοποιώ'/ the appropriate translation for the wiki (or asking an admin to do it), isn't it going to be much easier to activate the tag than having to file a phabricator request for it, in English, specifying the config variables that should be set ? We would have to describe how to make the request at Special:Tags, and casual users would have to be motivated enough to find out about config variables and such complexities. I'm pretty sure requests would be sparse, not because of lack of interest but because of excessive complexity in making them. There's already eight autotags implemented just in this patch set, more will be added in core progressively, even more by extensions, so making requests to activate them every time doesn't look viable to me. And as I mentioned earlier, wikis may want to disable one if more specific abusefilter or bot tags are enabled, then reactivate it in case of issues.
+Or are you suggesting that we should make autotags active by default ? I wouldn't recommend it, as this would result in a flurry of users expressing their discontent at being unexpectedly tagged, complaints of redundant tags, wikis requesting opt out and such. This feature should be optional and opt-in, but very easily so. Plus, there wouldn't be much sense in activating by default a bunch of tags if nobody actually check them out at Special:Tags.
+>> , without a single line of code needed since everything already exists
+> 
+> False, unless you're counting LocalSettings.php as code.
+I didn't imply more code would be needed here, just pretty much the same, same complexity.
+>> - have more use for this vastly underused table
+> 
+> Why is this a requirement?
+Not a requirement per se.
+>> - allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+> 
+> Where is this being stored? I see absolutely nothing about it in your WIP patch.
+It's not in this patch but the one for T89553, i.e. commit [[https://gerrit.wikimedia.org/r/#/c/190656/|980656]]. It's in a new field vt_importance of the change_tag table. Tags marked as 'important' would make changes tagged by it patrollable. I'll update the patch in a couple of days, since there is support for this feature on enwiki. Take the autotag 'un-redirects' for example, it should be possible for admins to mark this tag as 'patrollable', this way users will be able to patrol ""articles expanded from redirects"", which can't be done from Special:NewPages. Same for the autotag 'cross namespace moves', which will allow to patrol ""pages moved into mainspace"". Both are frequently requested features. So admins should be able to mark these two autotags as patrollable (and others too), and to store this data the valid_tag table is a perfect fit. See also T91425 which concerns Special:ProblemChanges.
+>> Again, letting admins do the activation is much easier to implement,
+> 
+> False.
+At least it's what I found out when actually trying to implement the thing (assuming a config variable is used to define tags, IMO a requirement). Thinking about it, I forgot to update the canActivateTag function (which shouldn't count inactive optional tags), I'll upload a new patch set. But nothing more is needed, if a config variable were used instead, analog checks would have to be done. And we would have to find some way to store the above data, since we couldn't use the valid_tag table.
+>> the current implementation of tags already allows it,
+> 
+> False.
+True... I don't understand this objection, admins can activate tags not already defined by an extension or already activated, in the very current and live implementation of ChangeTags. The action and user interface both exist.
+>> on the other hand using a second config variable would be a hassle to implement and fuzzy to maintain.
+> 
+> Claim is based on a faulty premise, and probably also false.
+I still don't see how to store the data for patrolling / problem changes besides using the valid_tag table. And having to maintain a second config variable in parallel seems bothersome to me.",1425433184,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1083158, @Cenarium wrote:
+> Ok, here's why we need a config variable to define optional tags IMO, it allows to:
+> - have a neat and efficient 'isset' check instead of ugly 'in_array'
+
+You've given no evidence that this is impossible with any solution other than yours. Or, for that matter, that this is an issue that should drive the implementation.
+
+> - easily define the wfmessage they should use
+
+The messages used by tags are already clearly defined by how tags work.
+
+As far as I can tell from your non-functional WIP patch, you might be referring to trying to localize the internal tag names. That seems pointless when the tags are already localized for display where applicable.
+
+> - easily unset the default autotags in case an extension wants to provide more specific ones (e.g. with more special casing, usergroups checks, etc, making many of the default ones redundant).
+
+This seems like a requirement without a use case. And if some extension were to want to do this, it hurts nothing for the core tag to remain defined despite being deactivated in LocalSettings.php.
+
+> Now for activation, doing this with the valid_tag table allows to:
+> - avoid a second config variable
+
+No need for this if you give up your idea of having the ability to not-even-define core tags.
+
+> - make it possible for admins to make the activation
+
+Why is this a desired feature?
+
+> , without a single line of code needed since everything already exists
+
+False, unless you're counting LocalSettings.php as code.
+
+> - have more use for this vastly underused table
+
+Why is this a requirement?
+
+> - allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+
+Where is this being stored? I see absolutely nothing about it in your WIP patch.
+
+> Again, letting admins do the activation is much easier to implement,
+
+False.
+
+> the current implementation of tags already allows it,
+
+False.
+
+> on the other hand using a second config variable would be a hassle to implement and fuzzy to maintain.
+
+Claim is based on a faulty premise, and probably also false.",1425410962,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Ok, here's why we need a config variable to define optional tags IMO, it allows to:
+- have a neat and efficient 'isset' check instead of ugly 'in_array'
+- easily define the wfmessage they should use
+- easily unset the default autotags in case an extension wants to provide more specific ones (e.g. with more special casing, usergroups checks, etc, making many of the default ones redundant).
+I can't think of any other reasonable way of defining these tags.
+
+Now for activation, doing this with the valid_tag table allows to:
+- avoid a second config variable
+- make it possible for admins to make the activation, without a single line of code needed since everything already exists
+- have more use for this vastly underused table
+- allows to store tag-specific data such as whether they should be patrollable, and maybe other features like hidden and such.
+Again, letting admins do the activation is much easier to implement, the current implementation of tags already allows it, on the other hand using a second config variable would be a hassle to implement and fuzzy to maintain.",1425406520,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I've updated [[https://gerrit.wikimedia.org/r/#/c/193040/|commit 193040]] with various redirect-related tags including those suggested here.
+
+>>! In T73236#1076852, @Anomie wrote:
+> Extensions already have hooks to use.
+> 
+> I see no good reason to support wikis wanting to not-even-define built-in tags.
+
+If the ListDefineTags hook is used, we can't simply define the source as 'optional'. Yet extensions should also be able to define optional tags. In the implementation I made, I use the config variable to not only define the tags but also to provide the relevant message giving the name of the tag (for internationalization purposes). It also allows a simple 'isset' check. A config variable to define all optional tags actually makes implementation easier. Wikis with lots of extensions may have lots of default optional tags, some of them may be irrelevant to them, so they may want to unset some, although it's not essential, just a bonus. And activation by admins is very easy to implement. So I don't see the need to think of other solutions, unless there is a serious issue with this implementation.",1425279494,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Extensions already have hooks to use.
+
+I see no good reason to support wikis wanting to not-even-define built-in tags.",1425252648,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1076767, @Anomie wrote:
+>>> Why are you assuming that the tags couldn't show up as defined but not active when the config setting for applying them is turned off?
+>> 
+>> To do that we would need two distinct config variables
+> 
+> No we wouldn't. We'd need one config variable to activate the feature, and //non-config// logic somewhere to define the tags and conditionally activate them.
+
+Maybe, but if we did that, wouldn't it be more complicated, especially for extensions ? And how about wikis not wanting some built-in tags defined at all (whether from core or extensions) ?
+I don't see the issue since in this case, it's actually very easy to allow admins to activate or not - we've already got everything that we need.",1425248495,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1076763, @Cenarium wrote:
+>>>! In T73236#1069817, @Anomie wrote:
+>> Why are you assuming that the tags couldn't show up as defined but not active when the config setting for applying them is turned off?
+> 
+> To do that we would need two distinct config variables
+
+No we wouldn't. We'd need one config variable to activate the feature, and //non-config// logic somewhere to define the tags and conditionally activate them.",1425246730,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1069817, @Anomie wrote:
+> Why are you assuming that the tags couldn't show up as defined but not active when the config setting for applying them is turned off?
+
+To do that we would need two distinct config variables : one to list defined tags, one to make them active. This is just as complicated as letting admins activate them or not : it requires checking the config variable for active tags instead of checking the valid_tag table.
+
+>>! In T73236#1069290, @TTO wrote:
+> The fact is, configuration settings that affect the entire wiki belong in `$wg` variables. As far as I know, nowhere in MediaWiki or the WMF-installed extensions is there a way to modify global configuration state from the wiki (perhaps with the exception of Global Groups).
+I agree that //defining// the optional built-in tags is a config issue, but //activating// them is not. It should be just as easy for admins to activate or deactivate an optional tag as to make an abuse filter tag or not.
+
+I'll implement the redirect-related tags in a new patch set.",1425246544,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1068996, @Cenarium wrote:
+> Config only isn't satisfactory, since those tags should not be active by default, but if we don't define them in config, they don't appear at Special:Tags so how can users of the wiki be even aware of their existence ?
+
+Why are you assuming that the tags couldn't show up as defined but not active when the config setting for applying them is turned off?",1424962595,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","The fact is, configuration settings that affect the entire wiki belong in `$wg` variables. As far as I know, nowhere in MediaWiki or the WMF-installed extensions is there a way to modify global configuration state from the wiki (perhaps with the exception of Global Groups).
+
+The long-term plan is to actually get rid of the `$wg` scheme altogether, which would allow for the creation of an on-wiki configuration interface. This way, configuration settings would be stored in the DB (or CDB/similar file) rather than a PHP file, and stewards would be able to alter global wiki configuration settings from within the MediaWiki interface. See https://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database_2 and T28992.
+
+>>! In T73236#1068996, @Cenarium wrote:
+> but if we don't define them in config, they don't appear at Special:Tags so how can users of the wiki be even aware of their existence ? 
+
+That's a broader issue with configuration variables in general. People seem to manage to find them in general, see T65388 for a request to change a non-obvious setting.",1424940345,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1065778, @Anomie wrote:
+>>>! In T73236#1064690, @TTO wrote:
+>> Your point about reserving a ""mw-"" namespace for core tags is a good idea. However I don't think we need the added complexity of ""optional tags"". ""Built-in tags"" (just a temporary name I made up for tags added by MW core) could be turned on and off in the wiki's configuration settings
+> 
+> I agree with this, now that we have regular SWAT windows getting a configuration setting changed isn't very difficult, so the added complexity of having an on-wiki page for admins to directly do this seems unwarranted.
+
+Config only isn't satisfactory, since those tags should not be active by default, but if we don't define them in config, they don't appear at Special:Tags so how can users of the wiki be even aware of their existence ? I agree with the idea of using a config variable, rather than a hook, but it should only define the tag, not make it active. Users are thus informed of the availability of those tags, and admins can then make them active or not as needed.
+
+I've made a proof of concept implementation in [[https://gerrit.wikimedia.org/r/#/c/193040/|commit 193040]], which uses cross namespaces moves as an example (easier to implement). Since the user interface for activation already exists, it isn't complex to implement, they can be activated the same way as user-defined tags.",1424923494,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1064690, @TTO wrote:
+> Your point about reserving a ""mw-"" namespace for core tags is a good idea. However I don't think we need the added complexity of ""optional tags"". ""Built-in tags"" (just a temporary name I made up for tags added by MW core) could be turned on and off in the wiki's configuration settings
+
+I agree with this, now that we have regular SWAT windows getting a configuration setting changed isn't very difficult, so the added complexity of having an on-wiki page for admins to directly do this seems unwarranted.",1424876178,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","It wouldn't really be core/extension adding to valid_tag but the tag manager that activates it. Config variables may be slightly less complicated to implement but it also makes it much harder to activate / deactivate a built-in tag.
+I'd like this to be doable on wiki, since there's likely to be some interplay between these tags and those added by filters or bots, the later two offering more specific options (only certain users, namespaces, page size constraints, etc) that could supersede the built-in tag but since their reliability is limited (bot failure, condition limits...), and not all wikis would have the resources to implement these, or only intermittently, the built-in tags would be a handy default/fallback that should be readily available.
+
+Another reason for this is patrolling of tagged changes... As I'm planing it, extension-defined tags would use a hook to define patrollable tags. So the behavior would be configured by the extension (for example visual editor would only list 'visualeditor-needcheck' as patrollable). On the other hand, the 'patrollable' status of user-defined tags would be stored in a field vt_important of the valid_tag table that admins could modify from Special:Tags. So if active built-in tags are not stored in valid_tag, how do we store the patrollable status of these ? As you mentioned there, a config variable would be unsatisfactory... doing this from Special:Tags is much easier.
+
+If we add support for this class of 'optional' tags that can be defined and applied by core or extensions, but whose activation is up to tag managers, the built-in mediawiki tags would only be one aspect of it. Extensions could provide various optional tags without having to create a user interface for their activation/deactivation. It's kind of hybrid, but it allows much more control for end users, and valid_tag allows to store extra info for customization.",1424848563,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","Your point about reserving a ""mw-"" namespace for core tags is a good idea. However I don't think we need the added complexity of ""optional tags"". ""Built-in tags"" (just a temporary name I made up for tags added by MW core) could be turned on and off in the wiki's configuration settings using something like
+
+```
+$wgUseBuiltInTags = true; // have 'em all
+$wgUseBuiltInTags = array( 'mw-redirected', 'mw-redirect-removed' ); // list the ones that are wanted
+$wgUseBuiltInTags = false; // none
+```
+
+Extensions would be able to provide their own configuration variables, which could behave in a similar fashion, or differently, depending on the requirements of that extension.
+
+I should point out that only manually defined tags are present in the `valid_tag` table. Extensions do not add to this table, and neither should core.
+",1424831516,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I'd suggest to implement those in core, but with a hook so that they can be disabled and more of the same type can be added by extensions. IMO, these tags should be optional so I would make it their defining characteristic. They should probably not be enabled by default, it would be up to admins to enable them or not at Special:Tags (and they could subsequently disable them if they want).
+
+They would be listed at Special:Tags via a 'ListOptionalTags' hook (core tags included). It should be possible for tag managers to activate and deactivate those tags (implemented by adding or removing them from the valid_tag table), but not for users to apply them to edits. Before applying those tags, MediaWiki core or extensions would check that the tag is defined in the valid_tag table (i.e. activated).
+
+So basically three categories of tags :
+- User-defined tags : defined and activated by tag managers, directly applied by users
+- Extension-defined tags : defined, activated and applied by extensions
+- Optional tags : defined by core/extensions, activated by users, and applied by core/extensions
+We may also reserve a namespace for those defined in core, such as ""mw-"".",1424831163,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.",">>! In T73236#1056437, @TTO wrote:
+> I wonder if it would be best to do this as a core feature, an extension (perhaps something like `SimpleTags`), or a Wikimedia-specific hook?
+
+Core feature or extension, not a hook IMO.",1424708404,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","I wonder if it would be best to do this as a core feature, an extension (perhaps something like `SimpleTags`), or a Wikimedia-specific hook?",1424519841,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.","The un-redirect part would be helpful for [[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_117#Proposed_technical_change:_show_pages_expanded_from_redirects_on_Special:NewPages_and_Special:NewPagesFeed|this request]], particularly when combined with patrolling of tagged changes from T89553. This is a frequently requested feature, along with pages moved into mainspace.",1424477330,PHID-USER-znn4xfvlp7e7mr2g3tvl,False,PHID-TASK-sei7okmjt6zw6r54dwus,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""","Screenshot
+
+Steps to reproduce:
+
+1.Open a blank page with VE
+2.Insert an image as the first item of the document
+3.Save the page
+4.Reopen the page
+5.The image gets highlighted, now try to delete the image
+
+
+Observed Result:
+The following error appears in the console:
+Uncaught Error: offset was inside a handlesOwnChildren node
+
+See the screenshot attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F14961}",1411497900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_description,resolved
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""",Verified the fix in production,1412885663,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""",Verified the fix in test2,1412370570,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""",Verified the fix in Betalabs,1411688615,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""","Change 162884 merged by jenkins-bot:
+Be more cautious about placing the cursor
+
+https://gerrit.wikimedia.org/r/162884",1411676932,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""","Change 162884 had a related patch set uploaded by Esanders:
+Be more cautious about placing the cursor
+
+https://gerrit.wikimedia.org/r/162884",1411652949,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+"VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws ""Error: offset was inside a handlesOwnChildren node""",It happens for reflist too.Though thats not something common to encounter to have reflist at the beginning of a page,1411498048,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ss7bz24d7ztd7wl4af5k,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"The VisualEditor section of BetaFeatures appears before the introduction
+
+In my experimental setup, the VisualEditor section in the beta features appears as first item, just before the introductory text about beta features.
+
+It appears that in the LocalSettings.php I load the VisualEditor extension before the BetaFeatures extension, and exchange the order results in a good placement of the VE as BF (normal order).
+
+--------------------------
+**Version**: master
+**Severity**: minor
+
+**Attached**: {F14687}",1411229760,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_description,resolved
+BetaFeatures: the VisualEditor section appears before the introduction,Re-close. Thanks!,1411236943,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Change 161685 merged by jenkins-bot:
+Check the existence of BetaFeatures before adding the 'visualeditor-enable' preference
+
+https://gerrit.wikimedia.org/r/161685",1411236745,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Thanks for merging, Bartosz.
+
+I propose a patch for the second solution also, I find it better to check the existence of BetaFeatures.",1411235714,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Change 161685 had a related patch set uploaded by Seb35:
+Check the existence of BetaFeatures before adding the 'visualeditor-enable' preference
+
+https://gerrit.wikimedia.org/r/161685",1411235581,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Change 161677 merged by jenkins-bot:
+Unset the preference key before adding it
+
+https://gerrit.wikimedia.org/r/161677",1411234703,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Oh, I misread your solution 1. That also makes sense. Thanks for the patch!",1411234582,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Change 161677 had a related patch set uploaded by Seb35:
+Unset the preference key before adding it
+
+https://gerrit.wikimedia.org/r/161677",1411232797,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Yeah. VE should just check for the presence of 'BetaFeatures' class, instead of relying on the order. You can just use class_exists() for that. Want to submit a patch?",1411232436,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+BetaFeatures: the VisualEditor section appears before the introduction,"Since the VisualEditor registers its preference 'visualeditor-enable' in the standard GetPreferences and in the BF’s GetBetaFeaturePreferences, one is be cancelled.
+
+If BF is loaded before VE (and hence BF’s GetPreferences is before VE’s GetPreferences), VE takes care and don’t add again the 'visualeditor-enable'.
+
+But if VE is loaded before BF, VE’s GetPreferences first adds its 'visualeditor-enable' then VE’s GetBetaFeaturePreferences erases the previous value and remplaces it by the 'visualeditor-emable' in the BF syntax, but by *keeping* the same place in the $prefs array, so the PreferencesForm loads it in a ""wrong"" order.
+
+Two non-exclusive solutions:
+1. in BF, unset the $prefs[$key] before adding it, to restart the order (tested, it works)
+2. in VE in onGetPreferences function, add a second condition before adding the 'visualeditor-enable' preference ""!AutoLoader::loadClass( 'BetaFeatures' )"" (tested, it works)",1411231646,PHID-USER-2nopae2cxuamwcbndaih,False,PHID-TASK-nmmwisceyjh3lm2bamkh,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","See the 6 hidden comments I placed in https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/SandboxVE&action=edit .
+Only 2 of them are visible when VEditing, https://en.wikipedia.org/wiki/User:Elitre_(WMF)/SandboxVE?veaction=edit .
+Reported on fr.wp, see for example that they are missing from sections Personagges and Liens externes in https://fr.wikipedia.org/w/index.php?title=Détective_Conan&veaction=edit .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1411214460,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_description,resolved
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","@jdforrester-WMF, comments won't show up if placed among a list of external links (see https://de.wikipedia.org/w/index.php?title=Benutzerin:Elitre_(WMF)/sandbox&veaction=edit&vesection=1 ). Should this task be re-opened?",1432289295,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor",(Filed as T90517.),1424800252,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Ooh, thank you, that was helpful. I can reproduce only if the reference is at the end of paragraph, and you add the comment after it. Adding a comment before a reference, or adding it after and typing some more text, works correctly. I can also reproduce in production, so that must be a separate issue too.",1424738559,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Hmm, I am able to reproduce it consistently.Nope thats a different case, I am not adding anything into a slug.Attaching the screen capture if it helps
+{F45842}",1424737964,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","@Ryasmeen, can you elaborate? I can't reproduce that, neither in labs nor prod – I can open an existing article in VE, place the cursor after a citation (like ""[1]""), insert a comment there, and save the page with the comment appearing in the source code (I didn't actually save, but ""Review your changes"" shows it). There is currently a separate issue with inserting things into slugs (T89192) – are you sure you're not running into that?",1424737299,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not getting added after template,gallery,math node and table",1424728461,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not getting added after template,gallery and table",1424727818,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not getting added after template and table",1424726491,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not getting added after template",1424725977,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Also , comment is not gettiing added after template",1424725965,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Comment added after citation node is not getting added , nothing in review changes section after adding it.",1424725093,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Comment added after citation not is not getting added , nothing in review changes section after adding it.",1424725074,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Change 192051 merged by jenkins-bot:
+Generate CommentNodes more leniently
+
+[[https://gerrit.wikimedia.org/r/192051]]",1424523439,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","The patch above correctly displays all six comments in the example from task description.
+
+> (this could be blamed on Parsoid's funny output, though – the <!-- --> is outside the <p></p>) 
+
+Filed as T90321.",1424490492,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Change 192051 had a related patch set uploaded (by Bartosz Dziewoński):
+Generate CommentNodes more leniently
+
+[[https://gerrit.wikimedia.org/r/192051]]
+
+#patch-for-review",1424490119,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","Am I missing something obvious, or is this actually pretty simple?
+
+The logic for this behavior is in Converter and ve.dm.CommentNode.static.toDataElement, we only generate a content node if converter.isExpectingContent() (=we're inside one of BlockquoteNode, HeadingNode, ParagraphNode, PreformattedNode, and expecting text). Therefore no comment will appear in VE for comments placed between block-level elements – paragraphs, tables, floated images, box-like templates, headings – and more confusingly, for comments placed at the beginning of a line containing a paragraph, for example (this could be blamed on Parsoid's funny output, though – the <!-- --> is outside the <p></p>) or at the beginning of a table cells and list items (and this is all our fault).
+
+But! we already have logic to control which elements can be nested inside which (for example, table rows may only contain table cells; ordered list may only contain list items). And we already have logic to wrap things that are not block-level in paragraphs. Looks like we could easily use that.
+
+I implemented it, played with it, and encountered no problems. Patch incoming.",1424488847,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+"Comments in ""unsafe"" content locations are not displayed in VisualEditor","The reason for this is that we're currently very conservative about which comments we deem to be ""safe"" to display, because there are some ""unsafe"" ones, like comments placed between two table rows. We haven't yet refined the logic for this, so right now a lot of comments are erroneously identified as unsafe.",1411409916,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-mfpswg7xbkj64zruzhyd,task_subcomment,NA
+VisualEditor: Paste from Microsoft Word converting spaces to line breaks,"original Word source causing issues
+
+Some spaces in Word documented are being converted into line breaks when pasting into VE.
+
+Example: https://www.mediawiki.org/wiki/User:Rosencrantz/Paste
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F15305}",1411157280,PHID-USER-evwol34rsld7viokxokd,False,PHID-TASK-lsebojbccynjbxj4wazk,task_description,open
+VisualEditor: [Regression] The #contentSub should not be removed during loading phase,"1. View https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License
+2. Observe whitespace between heading, subtitle and first paragraph
+3. Click Edit beta
+
+Expected:
+* Table of contents slide up and content remains in the same position and dims.
+
+Actual:
+* The content shift upwards due to #contentSub being display-none'ed. This element is empty by default (also on English Wikipedia) but it does have a line height and thus affects flow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1410983640,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rd24i5biuj4r7i3jeier,task_description,resolved
+VisualEditor: [Regression] The #contentSub should not be removed during loading phase,"(In reply to Krinkle from comment #0)
+> 1. View https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License
+> 2. Observe whitespace between heading, subtitle and first paragraph
+> 3. Click Edit beta
+> 
+> 
+
+For comparison, here's a redirect page where the element is non-empty:
+
+https://en.wikipedia.org/wiki/GNU_Library_General_Public_License",1410983956,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rd24i5biuj4r7i3jeier,task_subcomment,NA
+VisualEditor: [Regression] The #contentSub should not be removed during loading phase,//**content hidden as private in Bugzilla**//,1410983936,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rd24i5biuj4r7i3jeier,task_subcomment,NA
+VisualEditor: [Regression] The #contentSub should not be removed during loading phase,"Caused by I2d6157708bd7b4c3a7c647 which fixed bug 52243 and bug 54325.
+
+Perhaps we should use ""visibility: hidden;"" instead of ""opacity: 0;"" ?",1410983876,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rd24i5biuj4r7i3jeier,task_subcomment,NA
+"VisualEditor: [Regression] In Transclusion (multi-template) dialog, moving a template past a content block then focuses the content block, not the selected template","Environment- Production, Test2, beta
+
+1> open the transclusion for any citation (book/news/journal).
+2> add a content and a template  below the citation in the modal.
+3> Now highlight the Citation and click to move the citation down.
+4> Notice that although the citation moves down and the Content moves up, but now the highlight moves to the content instead of staying at the Citation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1410797520,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ouvl42pvdoq34kfphg3u,task_description,open
+"VisualEditor: [Regression] In Transclusion (multi-template) dialog, moving a template past a content block then focuses the content block, not the selected template",Possibly caused by our changes to focussing in dialogs recently?,1410806753,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ouvl42pvdoq34kfphg3u,task_subcomment,NA
+"VisualEditor: [Regression] In Transclusion (multi-template) dialog, moving a template past a content block then focuses the content block, not the selected template","Created attachment 16472
+Highlight jumps to the next item following the Citation, that is content
+
+**Attached**: {F14730}",1410797644,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ouvl42pvdoq34kfphg3u,task_subcomment,NA
+"VisualEditor: [Regression] In Transclusion (multi-template) dialog, moving a template past a content block then focuses the content block, not the selected template","Created attachment 16471
+citation highlighted
+
+**Attached**: {F14729}",1410797579,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-ouvl42pvdoq34kfphg3u,task_subcomment,NA
+VisualEditor: Duplicate resize handles appear on unhighlighted image nodes after resize,"1. Select image node at <https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet#Media_files>
+2. Resize an image
+3. While a new thumb is generated and fetched from Commons, highlight a different image.
+
+## Unexpected behaviour
+
+Observe, after the thumbnail fetch has completed the dimmed pixelated thumbnail preview will be replaced with a sharp opaque rendering. Unexpected is that this new rendering results in the appearance of a new resize handle at its bottom right corner.
+
+This new highlight and resize handle aren't supposed to exist and aren't properly kept up to date either (when reflowing the document they mostly stay behind and only update during more general regenerations).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1410640380,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5l7l3b3s6yrlk2ddzysl,task_description,resolved
+VisualEditor: Duplicate resize handles appear on unhighlighted image nodes after resize,I can't reproduce this anymore. Looks like it was fixed.,1530904132,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5l7l3b3s6yrlk2ddzysl,task_subcomment,NA
+VisualEditor: Duplicate resize handles appear on unhighlighted image nodes after resize,"Still reproducible on latest master. On fast networks it's harder to reproduce but there's no doubt we're missing some state integrity in our handling for that callback.
+ 
+{F41807}",1424113319,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5l7l3b3s6yrlk2ddzysl,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"```
+review/jdlrobson/mantleview x ~/Sites/w/extensions/MobileFrontend $ vagrant provision
+==> default: Running provisioner: lsb_check...
+==> default: Running provisioner: puppet...
+Running Puppet with site.pp...
+Warning: Could not retrieve fact ipaddress
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+The following SSH command responded with a non-zero exit status.
+Vagrant assumes that this means the command failed!
+
+FACTER_fqdn='mediawiki-vagrant.dev' FACTER_forwarded_port='8080' FACTER_shared_apt_cache='/vagrant/cache/apt/' FACTER_environment='vagrant' FACTER_port_fragment=':8080' FACTER_share_owner='502' FACTER_share_group='20' FACTER_provider_name='virtualbox' puppet apply --templatedir /vagrant/puppet/templates --verbose --config_version /vagrant/puppet/extra/config-version --fileserverconfig /vagrant/puppet/extra/fileserver.conf --logdest /vagrant/logs/puppet/puppet.20f0fbdd9.log --logdest console --write-catalog-summary --modulepath '/tmp/vagrant-puppet-1/modules-0:/etc/puppet/modules' --hiera_config=/tmp/vagrant-puppet-1/hiera.yaml --manifestdir /tmp/vagrant-puppet-1/manifests --detailed-exitcodes /tmp/vagrant-puppet-1/manifests/site.pp || [ $? -eq 2 ]
+
+Stdout from the command:
+
+
+
+Stderr from the command:
+
+Warning: Could not retrieve fact ipaddress
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+```",1410541620,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_description,declined
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,We can safely decline this. The base VM memory has been bumped a couple of times since this was opened and roles can now define an increase to memory if necessary.,1478539905,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"Has anyone seen this problem in the last two years?
+Or should this task get declined?",1478167283,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"I know that some of the OOM issues during provisioning were happening during Ruby gem compilation (usually ffi). It probably wasn't the root cause—more likely the compounding effect of less base VM RAM and more memory required by the base MW dependencies (HHVM)—but it's worth noting that there have been far fewer reported cases since we switched to using system packages. [1][2]
+
+[1] https://gerrit.wikimedia.org/r/#/c/158564/
+[2] https://gerrit.wikimedia.org/r/#/c/156207/",1411754521,PHID-USER-7bifphmxtcqgvdofuzla,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,It hasn't happened to me in a while (maybe correlated to less Flow coding?)... soon as it does I'll be back here.,1411748673,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"I'll also add the easiest way to trigger the error is to try and load the hhvm debugger, 
+
+    hhvm -m debug --debug-host ::1
+
+always fails for me with not enough memory if it booted with 1G due to reading the wrong settings.yml",1411746321,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"I've had this happen several times, not because of applications eating ram but because of https://bugzilla.wikimedia.org/show_bug.cgi?id=70304
+
+I have to reload vagrant from the appropriate directory and it starts up with my configured 4G instead of 1G",1411746188,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"Jon, poke. Any progress in reproducing and determining which application is eating your instance RAM?",1411745597,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"(In reply to Jon from comment #2)
+> Nothing looked suspect. Is there any particular commands you would like me
+> to run?
+
+# Top 20 processes by resident memory size
+$ ps -e -orss=,args= | sort -b -k1,1nr | head -20
+
+# Free/used ram
+$ free -m
+
+# Job queue status
+$ mwscript showJobs.php --wiki=wiki --group",1410542901,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"I'm using Flow, MobileFrontend and VisualEditor. I notice this seems to correlate when I have a Flow page with over 20 posts and I continuously keep hitting.
+
+Nothing looked suspect. Is there any particular commands you would like me to run?",1410541944,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant,"(In reply to Jon from comment #0)
+> Warning: Could not retrieve fact ipaddress
+> Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+> Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant
+
+Any idea what's eating all the ram in your VM? Redis full of unprocessed jobs perhaps?",1410541844,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-y4soahtd3ne6ieogzdqn,task_subcomment,NA
+"VisualEditor: After removing the Template:Top,trying to place cursor on content throws TypeError: Cannot read property 'Left'/'right'/'start' of null","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a template Top, specify a bg color code so you can see the effect better on CE.I tried with #FFFFE0
+3.Now click on Insert and Save the page
+4.You will see the entire content after that template (until references list) gets added as a Content section for that template and inherits the styling specified in the template parameters.
+5.Reopen the page
+6.Reopen the transclusion dialog for that template
+7.Click on the Delete icon to remove the template ""Top"" to just retain the usual format of the text.
+8.Click on ""Apply Changes""
+9.Now when you are back to CE, try to place your cursor on the content which was part of that template
+
+Observed Result:
+It throws the following error on each click:
+
+
+Uncaught TypeError: Cannot read property 'right' of null
+Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 85 is out of bounds 
+
+Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14694}",1410203160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-krueh2a24bjyg7r3twut,task_description,open
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","The Sub-heading 4 font as shown in the Text Style drop-down does not match with the other Sub-headings in it.
+
+Screenshot:
+{F25185708}
+(old screenshot: F15333)
+
+Task: Update the styles for VisualEditor's ""Format"" dropdown when using the [MonoBook](https://www.mediawiki.org/wiki/Skin:MonoBook) [skin](https://www.mediawiki.org/wiki/Manual:Skins), so that the text size for headings inside the dropdown is the same as their size on the page.",1410188100,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-dx4wusevsujq7v5py7nu,task_description,resolved
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","Change 470992 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update the styles for VisualEditor's ""Format"" dropdown
+
+[[https://gerrit.wikimedia.org/r/470992]]",1541107212,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","Change 470992 had a related patch set uploaded (by Bjornskjald; owner: Bjornskjald):
+[mediawiki/extensions/VisualEditor@master] Update the styles for VisualEditor's ""Format"" dropdown
+
+[[https://gerrit.wikimedia.org/r/470992]]",1541070910,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)",https://codein.withgoogle.com/tasks/6745215428722688/,1540311144,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)",https://codein.withgoogle.com/dashboard/tasks/6745215428722688/,1540273504,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)",I would like to mentor this task in #Google-Code-in-2018.,1540253252,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","This is still a problem, the font size in the menu doesn't match the font size in the page content:
+{F25185698} {F25185708}
+Looks like VE's styles were never updated after the change to heading font sizes in MW: {237787cbadaadf31f5d71733ee8bac5b463ba292}.
+
+(this may look like my fault, but it's not, I was not on the VE team then yet ;) )",1534794823,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","Confirmed - Sub-headings(started with Sub-heading 1) are decreasing proportionally like this: 130, 115, 100(for Sub-heading 3). However, for Sub-heading 4 - it has font-size: 80% instead of 85%. 
+
+Look at the attached screenshot where Sub-heading 4 has font-size: 85% - it looks much more proportional relative to other Sub-headings.",1415403886,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+"The font size of headings in the ""Format"" dropdown doesn't match the font size in the page content (in MonoBook skin)","Created attachment 17076
+monobook Sub-heading 4 with font-size 85%
+
+**Attached**: {F15334}",1415403808,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-dx4wusevsujq7v5py7nu,task_subcomment,NA
+VisualEditor:  Please add a 'close' box to the wikitext warning,"It's not obvious to everyone that you can click the wikitext warning to make it go away.  Please add an 'X' or something that makes it look like you should click on it if you don't want it to be there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410155760,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-vussyglstlop2mytex2t,task_description,resolved
+VisualEditor:  Please add a 'close' box to the wikitext warning,"Adding close buttons / etc. to MediaWiki's notice system is bug 40307. Merging this into that rather than duplicating.
+
+*** This bug has been marked as a duplicate of bug 40307 ***",1410207810,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vussyglstlop2mytex2t,task_subcomment,NA
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,"A thing that happens to me frequently is that I paste the title of another article. When this happens, it's formatted as a heading. This is correct HTML-wise, but it's never what I mean - I usually mean to paste it as plain text or as a link.
+
+It would be nice if the VE vould guess it.
+
+A long shot, I know, but it happens to me a lot and I wanted to write it down :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410095760,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-347gkxmboadsdufxjprl,task_description,duplicate
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,"One could debate whether copying within a heading should write plain text to the clipboard, but then there is a common edge case where you select the whole heading, i.e. <h1>|word|</h1>. It's probably 50/50 what the user intends to happen when they paste. CTRL+SHIFT+V does what you need here, but maybe there could be a way to surface this after the fact (""this text was just pasted with formatting - click here to remove"").",1457948632,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-347gkxmboadsdufxjprl,task_subcomment,NA
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,"In the public weekly triage on 2015-04-29, we discussed this task. We decided that this task is not the right approach as stated, so we rejected it for the quarter's blocking list.",1430334671,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-347gkxmboadsdufxjprl,task_subcomment,NA
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,">>! In T72519#768508, @Jdforrester-WMF wrote:
+> So this is ""if paste is an <h1> with id of firstHeading, instead paste a <p>""? OK.
+
+Well, this is the most frequent DWIM-style thing I can think of. Happens to me almost every time I edit an article.
+
+I can imagine other DWIMmy things, but resolving just the <h1> issue would be a huge improvement for me.
+
+And it probably shouldn't be a <p>, but simply match the surrounding markup, whether it's <h2>, link, etc.",1416846337,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-347gkxmboadsdufxjprl,task_subcomment,NA
+VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>,"(In reply to Amir E. Aharoni from comment #0)
+> A thing that happens to me frequently is that I paste the title of another
+> article. When this happens, it's formatted as a heading. This is correct
+> HTML-wise, but it's never what I mean - I usually mean to paste it as plain
+> text or as a link.
+> 
+> It would be nice if the VE vould guess it.
+> 
+> A long shot, I know, but it happens to me a lot and I wanted to write it
+> down :)
+
+So this is ""if paste is an <h1> with id of firstHeading, instead paste a <p>""? OK.",1414011970,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-347gkxmboadsdufxjprl,task_subcomment,NA
+VisualEditor: Be able to make block-level edits (e.g. language of a <div> / <ol> not a <span>),"We'll need a way of editing these for the rare but useful block-level editing concepts that sometimes crop up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1410033900,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-repvwi7xaiozmntsb6ul,task_description,open
+VisualEditor/WikiEditor: Consistent terminology,"The terminology between WikiEditor (aka ""Advanced toolbar"") and VisualEditor MUST be consistent so people will not get confused.
+
+For example in VisualEditor there is ""Cite"" menu, while in WikiEditor it is called ""Reference"" (Cite options in enwiki is only a gadget). It is super important, so we can guide new editors with same terminology. If you don't like the old terminology in some cases - use new one, but fix the WikiEditor to use it too.
+
+
+[Longer story]
+Today I participated in a workshop for new editors. We told the new editors they should use either VE or classic wikitext, and gave them printed instructions what to do, and they got confused of it...
+[The first time ever for me to open terminology bug, yay :)]
+
+Suggested terminology
+| VE | classic edit (including WikiEditor) | Suggestion | Description
+| Review your changes | Show changes | Show changes 
+| Cite | Reference | Reference | Cite may have disambig with quote. Both buttons are actually for adding reference/source
+| Media | Embedded file (title), Insert file (dialog title) | Media | Media is more specific than file (e.g it doesn't mean you can upload article as txt file)
+| Heading, Sub-heading 1, Sub-heading 2... | Heading, Level 2, Level 3 | Heading, Sub-heading 1, Sub-heading 2... 
+| Search pages (in link dialog) | Target page (in link dialog) | Target page 
+| External link (link dialog) | URL (link dialog) | External link | Not sure what is better. URL seems to be more technical",1409923320,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-jseusuuyitcemiu5pnrs,task_description,open
+VisualEditor: Vector's styling for H2 headers (with a line underneath) does not expand to full width when the context of the surrounding changes,"Screen cast of the sequence
+
+When editing a page with an infobox on the side, header lines that ended on the infobox does not expand to full width if content added above them pushes them down below the infobox. 
+
+The opposite works thouhg, i.e. deleting content so a header lines move up shortens the header line so that they do not overlap the infobox.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14886}",1409835480,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-xissc7qsu7tkv7xx7nkr,task_description,resolved
+VisualEditor: Vector's styling for H2 headers (with a line underneath) does not expand to full width when the context of the surrounding changes,This appears to have been fixed some time ago.,1525335811,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-xissc7qsu7tkv7xx7nkr,task_subcomment,NA
+"VisualEditor: Cursor jumps to the start of the line, if link and Language style text present.","screenshot
+
+1> open a page in VE, insert a link. And after a space or two, insert some Language style text. 
+2> Now place the cursor at the end of the line and move along the line, the cursor jumps to the start of the line when it reaches the first character of the language style text .See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14760}",1409756940,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-xigwlc2e3gsxx4kbk5ix,task_description,open
+"VisualEditor: Cursor jumps to the start of the line, if link and Language style text present.","Confirmed. The structure of a line is like the following:
+*link* some text *lang text*
+
+A cursor that moves from left to right(placed at the beginning of *link*) will go through the inserted link, then the text, and then through language style text. 
+
+A cursor that is placed at the end of  *lang text* and then moved from right to left, will jump to the beginning of the line - which is a bug. 
+
+There is a workaround for editing the text between a link and lang style text  - just place a cursor inside it.",1415827729,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-xigwlc2e3gsxx4kbk5ix,task_subcomment,NA
+"VisualEditor: Cursor jumps to the start of the line, if link and Language style text present.",Environment- test2,1409757265,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-xigwlc2e3gsxx4kbk5ix,task_subcomment,NA
+"VisualEditor: Cursor jumps to the start of the line, if link and Language style text present.","so if i want to edit some text present in between a link and the language style text, i cannot do it.",1409757227,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-xigwlc2e3gsxx4kbk5ix,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors","{F14756}
+1> open a page in VE, insert a comment.
+2> Click to edit the comment and insert a link. Notice the link icon is selected in the toolbar, although no link gets inserted in the comment . Try the above steps, with Formula and text styles like Underline, Strikethrough. See screenshots.
+
+",1409755980,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_description,open
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors","I disagree. Disabling the surface (greyed out, like we do for dialogs) suggests the surface isn't active. Disabling individual tools (greyed out, like we do when the selection is a table range) suggests the tool can't work where the user believes the cursor is currently.",1447284297,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors"," Inspectors are non-modal so opening them keeps the selection in the surface, and so you can still use all the tools.
+
+Disabling the tools would suggest that the surface selection is no longer active which is not true.",1447284182,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors","Confirmed - as the attached screenshots indicate - link, and some style formats - e.g. Bold, Italic, Underline - make an impression that they can be applied to  Comments or Formulas. 
+
+IN fact, clicking Formatting options or insert link have no effect on inserted Comments or Formulas.",1415407832,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors",Environment-test2,1409757305,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+"VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors","Created attachment 16353
+screenshot2
+
+**Attached**: {F14757}",1409756023,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-gwdegmhrhwhz5sbml3r5,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"Screenshot of embeded video
+
+I think it would be better to distinguish better videos and pictures:
+a) in media selection
+b) in the text itself
+
+a) if Id like to add video, I am not able to determine, which previous in media selections are videos and which not. Thus I must go to Wikimedia Commons anyway and add it like a unique filename.
+
+b) attached screenshot shows, I add somethink and it still looks like an image - even its a video file.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F14720}",1409651580,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-4g6i4gjynjlxlyawm244,task_description,open
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"This is really two bugs, and should be split, but leaving for now…",1409670292,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"(In reply to Andre Klapper from comment #1)
+> Created attachment 16341 [details]
+> Screenshot from Firefox 31, no problems
+> 
+> Which browser and version is that (such information is always welcome)? No
+> problems here to get the ""Play"" button overlay with Firefox 31 on Linux, see
+> screenshot.
+
+But there is a small difference. Your screenshot is from ""read"" verstion, mine is from ""edit"".
+
+ 
+> Still, what's the usecase of knowing in VisualEditor if it's a video or
+> image? That you don't want to add another video if there is already one?
+
+Well, you want to know if you are adding video or image.
+
+**Attached**: {F14721}",1409662629,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"Sigh. VE! Confirming. I should get more coffee. 
+Sorry for all the noise. Ignore my last two comments please.
+
+Still, what's the usecase of knowing in VisualEditor if it's a video or image? That you don't want to add another video if there is already one?",1409658692,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,[Rephrasing bug summary; please insert browser & version there],1409658541,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: Distinguish better between media types in the search interface and in the editing surface,"Created attachment 16341
+Screenshot from Firefox 31, no problems
+
+Which browser and version is that (such information is always welcome)? No problems here to get the ""Play"" button overlay with Firefox 31 on Linux, see screenshot.
+
+**Attached**: {F14721}",1409658504,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-4g6i4gjynjlxlyawm244,task_subcomment,NA
+VisualEditor: There should be a link to the template page even if template description is available,"When a template doesn't have a description in TemplateData, a link is shown to the template's page in the Template namespace (using the visualeditor-dialog-transclusion-no-template-description message).
+
+This link is very useful.
+
+I don't see such a link when a template does have a description. Compare, for example, how adding {{Reflist}} is different from adding {{LGBT Welcome}}.
+
+For advanced users the description in TemplateData is not a replacement for the whole page, so there should always be a link to the template page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409644740,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-clgmrlcl24aptweuxikz,task_description,duplicate
+Make the CAPTCHA more visible when saving,"1. Sign up with a new username to a Wikimedia site.
+2. Edit an article and add an external link.
+3. Try saving.
+
+After entering an edit summary and pressing the button in the dialog, the dialog remains and the CAPTCHA is shown in its bottom. At least on my machine, I need to scroll down in the dialog to actually see the CAPTCHA. I saw new users puzzled over this - they thought that they already pressed the save button and couldn't understand why is the dialog still there.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409596440,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_description,resolved
+Make the CAPTCHA more visible when saving,"Change 479197 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Move save error messages above save footer
+
+[[https://gerrit.wikimedia.org/r/479197]]",1546534542,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"|Before |After
+| {F27784473}|{F27784482}",1546532815,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"Change 479197 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Move save error messages above save footer
+
+[[https://gerrit.wikimedia.org/r/479197]]",1544619390,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"The order was switched in https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VisualEditor/+/335223/ when adding a slide transition, putting the messages under the footer - we should switch them back.",1544619356,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"VisualEditor doesn't have any magic way to bypass it, are you sure it saved successfully and that nothing else changed?",1462550661,PHID-USER-mvx4x7ywk2flsaku2dbk,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,">>! In T72266#1384881, @jayvdb wrote:
+> So the steps as an anon (should be the same?) are:
+> 1. Edit using VE as an anon http://enwp.org/User:Elitre/Sandbox?veaction=edit
+> 2. Add an EL http://blah.com/foo
+> 3. step through the save process
+I received a captcha when using the source editor but not with the visual editor.",1462504877,PHID-USER-ibbxmosfonhbbhdgkv52,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,">>! In T72266#1384974, @Amire80 wrote:
+> Try it on a smaller screen. A lot of people still use 1024×768 or even smaller screens.
+> 
+
+I get exactly the same result in an 800x600 window
+
+{F181476}
+
+> How about putting it above the edit summary or instead of it?
+
+My suggestion, would be to highlight the text-input-box, which is currently hard to detect underneath the CAPTCHA. 
+Not that the current wikitext version is much better...
+{F181482}
+
+
+Sidenote: There's also {T54133} which if implemented will help reduce the size of that entire save window (and also fix T50274 - the missing autocomplete dropdown of previously used editsummaries (if someone let's their browser remember form-history. madness!))
+
+",1434820094,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"Try it on a smaller screen. A lot of people still use 1024×768 or even smaller screens.
+
+How about putting it above the edit summary or instead of it?",1434791299,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,">>! In T72266#1384881, @jayvdb wrote:
+
+Hey, thanks a lot for testing!
+
+> So the steps as an anon (should be the same?) are:
+
+I assume so, since the captcha is triggered then as well.
+
+> 1. Edit using VE as an anon http://enwp.org/User:Elitre/Sandbox?veaction=edit
+> 2. Add an EL http://blah.com/foo
+> 3. step through the save process
+> 
+> It should show
+> ""Warning:
+> CAPTCHA: To edit this page, please enter the words that appear below in the box (more info):""
+> 
+> And image appears below it.
+> 
+> Ive tried in twice on Chrome and once on Firefox. Two times it worked; once when I tried it on Chrome (Fedora 20; 43.0.2357.81), the warning appeared and the image didnt.
+> 
+> The warning should not be shown until the image is shown, and if the image doesnt arrive, it should display an error message.
+
+I think this is a different issue then? (and maybe one with javascript?) Amir says that he needs to scroll down to see the captcha. In all my tests, the captcha is always immediately visible (as in Nick's second screenshot).
+Which OS do you have? Mine is Win 7 (I'll test in my Macbook Air later). 
+
+> 
+> Also, it never shows the 'refresh' link to get another CAPTCHA, which is often necessary when the CAPTCHA is unreadable.  I checked and the 'source editor' has that.  Probably a separate bug.
+
+",1434790656,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"The CAPTCHA is appearing in the visible area, for me. Only the previously visible licensing info (which needs to have been read before clicking ""Save"" anyway!) gets scrolled out of view:
+
+{F181350}
+{F181349}
+
+So possibly this particular task needs to be retitled or refined?
+
+I've confirmed there's no refresh. Filed as {T103227}",1434788475,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"So the steps as an anon (should be the same?) are:
+1. Edit using VE as an anon http://enwp.org/User:Elitre/Sandbox?veaction=edit
+2. Add an EL http://blah.com/foo
+3. step through the save process
+
+It should show
+""Warning:
+CAPTCHA: To edit this page, please enter the words that appear below in the box (more info):""
+
+And image appears below it.
+
+Ive tried in twice on Chrome and once on Firefox. Two times it worked; once when I tried it on Chrome (Fedora 20; 43.0.2357.81), the warning appeared and the image didnt.
+
+The warning should not be shown until the image is shown, and if the image doesnt arrive, it should display an error message.
+
+Also, it never shows the 'refresh' link to get another CAPTCHA, which is often necessary when the CAPTCHA is unreadable.  I checked and the 'source editor' has that.  Probably a separate bug.",1434786518,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"I haven't been successful so far in finding a way to replicate (I tested several times in these months and couldn't replicate in IE, FF, Opera or Chrome. TBH, rather than creating a new account, I just use incognito window because I was testing a report from an IP user).
+I'm inclined to think that this may have been fixed by some design changes, but if it's still occurring for any of you and you can please post details of how you manage to reproduce it, I'd be happy to mark it as a ""blocker"". ",1434783341,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"I see closed tasks T52356 and T64766, but no other tasks relating to CAPTCHA, either open or closed.  Is this well covered by test scenarios?",1434768391,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Make the CAPTCHA more visible when saving,"If VE is going to be rolled out to new editors, surely this must be a high priority?
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29#Gradually_enabling_VisualEditor_for_new_accounts",1434767314,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-f7uhw2bgeh3f77k6lvjh,task_subcomment,NA
+Bugzilla: Create keyword for usability,"The design and accessibility keywords aren't sufficient to cover cases where usability is the main hurdle.
+
+Be it an existing implementation that is hard to use and needs input to improve it, or a new feature/bug that is blocked on having an intuitive interface.
+
+In cleaning up bugs I often see this word in the title but would be interested in giving it its own keyword for interested parties (especially the Wikimedia UX team) to look at.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1409582520,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cqzkozq3w62lx7y4ycf7,task_description,declined
+Bugzilla: Create keyword for usability,My main question was how/why the design keyword is not sufficient and what's the differentiation that users would need to understand to set those two keywords correctly.,1409601718,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-cqzkozq3w62lx7y4ycf7,task_subcomment,NA
+Bugzilla: Create keyword for usability,"(In reply to Andre Klapper from comment #1)
+> I'm against this.
+> I have not seen a single bugtracker where users understood the narrow frame
+> of ""usability"". Instead, everything was randomly tagged with that keyword.
+> ""The server was down so I couldn't use it, hence a usability issue"" style.
+> 
+> In my understanding, an intuitive interface needs proper design. 
+> If the ""design"" keyword is not sufficient, please elaborate why that is the
+> case.
+
+One could make the same argument about lots of components and keywords (accessibility, design, javascript, parser, i18n; VisualEditor; Page editing; Any of those will be affected by other factors). I don't see how it's relevant that users may use it incorrectly. That happens all the time. That's why we triage bugs.
+
+Anyway, not my problem.",1409588985,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cqzkozq3w62lx7y4ycf7,task_subcomment,NA
+Bugzilla: Create keyword for usability,"I'm against this.
+I have not seen a single bugtracker where users understood the narrow frame of ""usability"". Instead, everything was randomly tagged with that keyword. ""The server was down so I couldn't use it, hence a usability issue"" style.
+
+In my understanding, an intuitive interface needs proper design. 
+If the ""design"" keyword is not sufficient, please elaborate why that is the case.",1409588491,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-cqzkozq3w62lx7y4ycf7,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","**Author:** `bsitu`
+
+**Description:**
+It throws invalid workflow exception
+
+---
+See {T88908}.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1409272980,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_description,resolved
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","I think some assumptions may be wrong here: Flow doesn't need Parsoid because we integrate with VE.
+
+As you may know, Flow is (currently) able to store content in either wikitext or html.
+In production, we chose to store data in html, so that we need less resources to keep recompiling the wikitext to html when the page needs to be displayed.
+Parsoid is indeed resource-intensive, but less so than the alternative of converting all wikitext to html for every request.
+
+In this scenario (storing html), we need Parsoid to make it possible to edit things (in wikitext) that have been stored in html: plain old PHP parser can't convert html to wikitext.
+Since we recently added VE integration, Flow also needs Parsoid to convert from VE back to wikitext editor.
+The reason we *need* Parsoid (in production) is not VE, but wikitext-editing. Actually, we wouldn't need Parsoid if we *only* supported VE (we could just store VE's html output).
+
+If you don't want to use Parsoid, you (currently) can, but:
+* you have to store content in wikitext & convert to html for every request (will need lots more CPU, depending on amount of requests)
+* you can't use VE (since we can't convert the html back to wikitext)
+
+We currently still support wikitext storage/non-Parsoid (in part because we simply have to: jenkins isn't set up to let us connect to Parsoid yet) although it's suboptimal (see above).
+We must face that it's a burden to maintain & we just can't test everything all the time. Things may be broken from time to time.
+
+We don't need Parsoid because we have resources to burn, or because we want to push VE; those 2 would be easier without Parsoid & compromising on other things.
+We choose to use Parsoid because it is the best (only) solution to be more conservative on resources (store in html) & still support editing one's post in wikitext.
+
+AFAIK, there are no concrete plans to abandon wikitext storage/non-Parsoid support yet.
+I think we can put this discussion to rest at least until we can contact Parsoid on jenkins, which may or may not be awhile.
+I'm also going to close {T88908}",1429770288,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1230034, @Mattflaschen wrote:
+>>>! In T72148#1205755, @Arcane21 wrote:
+>> Parsoid is extremely resource intensive, even on small setups, and while the WMF may be able to easily ignore this, many smaller non WMF setups would not be able to do so, and I have to confess I'm greatly interested in introducing Flow to the Orain wiki farm (which I serve at as a staff member), but I'd rather we not have to have to acquire much more resources than we use currently to support Flow.
+> 
+> To determine whether it's overly resource-intensive, you would have to compare it to other software that does the same thing: Bidirectional conversion of editable HTML to wikitext.
+> 
+> The reason node.js was used for Parsoid is that investigation showed it was //far// more performant than the same thing would be in PHP.  There's no identical implementation of the current Parsoid in PHP (since no one chose to write one).  However, this has almost certainly not changed.
+> 
+>>>! In T72148#1211295, @FastLizard4 wrote:
+>> With a tool like VisualEditor, it's obvious why Parsoid needs to be required, but I don't see why Flow by itself //needs// to have access to the powerful parsing tools Parsoid provides, especially given that Parsoid is still experimental and is rapidly changing.
+> 
+> Though VisualEditor is not required (either for wiki operators installing Flow or for individual Flow end users), VE is a key part of the vision for Flow (that's why we use Parsoid to begin with).  That means, for example, we now use VE for previewing (so no preview without Parsoid). 
+
+As to the first issue, I understand that, but we don't WANT to have, need, or require VE at this time, just Flow, mostly because we don't want to be shackled to Parsoid, which we discovered would not scale well to our current resource infrastructure. The WMF can easily use it because frankly they've got resources to burn and them some, but Parsoid (the service backend) is costly to maintain in terms of memory and processor cycles, and while it may be a magical engine that solves a lot of the WMF's problems, it's a resource hog otherwise, and while it works great for VE and the WMF, and I don't dispute that, we and I'm certain almost every single smaller userbase with far less resources to burn does not want to be forced to use something that only the WMF is happy with.
+
+Forgive me if this sounds harsh, but I believe the WMF seems to be proceeding on the somewhat arrogant assumption that if they like something, the rest of the world should easily be able to adapt and emulate it if they want the same, even though the resources needed to maintain it aren't as plentiful on setups far smaller than the WMF's.
+
+Further, as you pointed out, Flow does not currently require it, and while Visual Editor needing Parsoid made sense from the get go (given its intended design and purpose), forcing Flow to conform to the same when it is not strictly required strikes me a little more than railroading non-WMF end users into using something they don't want simply because it make WMF users happy to do so.
+
+As to the second rebuttal, it merely proves my first point: VE is the WMF's baby, and the WMF is intent on forcing everything that hooks into it to use the same standards and nothing else, despite the inconvenience this places on those who do not wish the added expense of Parsoid when the optional hook in feature does not strictly require it.
+
+I understand the WMF wants to make their lives easier, and as a staff member on a wiki server setup myself, I'm sympathetic from an engineering standpoint. However, as an end user of MediaWiki and someone who has to help install, configure, and adjust settings on our setup to work nicely with anything we add, this would be expense in resources to add when as you pointed out it's not a strict requirement, and on a personal note, if adding Flow was merely adding the extension and running the update script without needing a backend that has no real reason to manacled to an extension that was not designed to strictly need it in the first place, I see no reason to make those like myself and others have to suffer Parsoid's presence at our expense when that could be avoided.
+
+I respectfully remind the WMF MediaWiki is global software, and that I feel the WMF should be mindful not all wiki farms and setups are as wealthy in processor and memory resources to burn to maintain the same configurations as the WMF, and since Parsoid is not needed for Flow (which has a negligible resource footprint without Parsoid in tests I have run so far), I see no reason to force others to use Parsoid only when they don't have to.
+
+I'm not opposed to a dual operation standard, in which Parsoid enabled setups can benefit if Parsoid is installed, but if it's not, then it should retain the non Parsoid mode for those who frankly have no desire or intention to ever use or enable Visual Editor.",1429761445,PHID-USER-iy4yqj4ftn74e3b5fy3e,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1205755, @Arcane21 wrote:
+> Parsoid is extremely resource intensive, even on small setups, and while the WMF may be able to easily ignore this, many smaller non WMF setups would not be able to do so, and I have to confess I'm greatly interested in introducing Flow to the Orain wiki farm (which I serve at as a staff member), but I'd rather we not have to have to acquire much more resources than we use currently to support Flow.
+
+To determine whether it's overly resource-intensive, you would have to compare it to other software that does the same thing: Bidirectional conversion of editable HTML to wikitext.
+
+The reason node.js was used for Parsoid is that investigation showed it was //far// more performant than the same thing would be in PHP.  There's no identical implementation of the current Parsoid in PHP (since no one chose to write one).  However, this has almost certainly not changed.
+
+>>! In T72148#1211295, @FastLizard4 wrote:
+> With a tool like VisualEditor, it's obvious why Parsoid needs to be required, but I don't see why Flow by itself //needs// to have access to the powerful parsing tools Parsoid provides, especially given that Parsoid is still experimental and is rapidly changing.
+
+Though VisualEditor is not required (either for wiki operators installing Flow or for individual Flow end users), VE is a key part of the vision for Flow (that's why we use Parsoid to begin with).  That means, for example, we now use VE for previewing (so no preview without Parsoid). ",1429757327,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",Changing my token to make clear my opinion is the same as @Arcane21's one.,1429284851,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","This issue has been fixed for awhile now. AFAIK, everything currently works in wikitext storage.",1429264967,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","I definitely see both sides of the argument here.  I agree that, in most cases, maintaining two versions of key parts of a single piece of software is quite costly.  However, as a small wiki operator myself, I feel that at this point, restricting Flow to Parsoid-only would only hurt wide adoption, because at this point, Parsoid is still rather experimental (definitely at least ""Beta"" software).
+
+With a tool like VisualEditor, it's obvious why Parsoid needs to be required, but I don't see why Flow by itself //needs// to have access to the powerful parsing tools Parsoid provides, especially given that Parsoid is still experimental and is rapidly changing.  At least until Parsoid becomes stable and ready for mass release, I would say that giving sysadmins the opportunity to be able to use Flow without needing Parsoid is important, even if it does increase the cost of Flow development.",1429150349,PHID-USER-q6nnw3r5axkpgj5uftsh,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1205608, @Mattflaschen wrote:
+>>>! In T72148#1179439, @Arcane21 wrote:
+>> I strongly disagree with dropping non Parsoid support. Parsoid is incredibly costly, and while I would love to switch my LQT enabled wiki to Flow, I have no desire to install costly backend software to do so, nor would many smaller non WMF wikis with more limited resources, and if it means it performs less optimally, I would consider that an acceptable compromise to retain non Parsoid functionality.
+> 
+> Costly in what way, exactly?
+> 
+> * Requires a lot of man-hours to install?
+> * Difficult to maintain?
+> * Requires high-end services or equipment to run?
+> 
+> Maybe there's a way Parsoid could be easier for you to use.
+> 
+> The main reason we want to remove support for non-Parsoid is that it is costly (mainly in software engineer time) to maintain two versions of key parts of the code.
+
+Parsoid is extremely resource intensive, even on small setups, and while the WMF may be able to easily ignore this, many smaller non WMF setups would not be able to do so, and I have to confess I'm greatly interested in introducing Flow to the Orain wiki farm (which I serve at as a staff member), but I'd rather we not have to have to acquire much more resources than we use currently to support Flow.
+
+I have also tested Parsoid on a localhost configuration, and I found Parsoid absorbed over half a gigabyte of resources just to function (on a Windows setup, have not fully evaluated this on a Linux at present), and I'm not sanguine on trying to use Parsoid on a wider scale given this resource drain on a small scale.
+
+Also, while I understand keeping around two sets of code is indeed costly to the WMF, I do not see the harm in maintaining such code if it means the extension can be used on non Parsoid enabled setups, as, to be blunt, the WMF provided MediaWiki to the world for everyone to use, and while I understand the WMF wants to tailor this software to fit it's current needs, it could be of great benefit to non-WMF users, and I see no good reason to throw those use cases under the bus just to make one organization happy.
+
+Also, since it is intended to succeed LiquidThreads, and many LQT users on non-WMF setups may wish to migrate to Flow like my organization, I don't see the point in making their task in doing so harder by forcing them to add backend software that consumes a ton of overhead just to use the successor to LQT.",1428984868,PHID-USER-iy4yqj4ftn74e3b5fy3e,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1179439, @Arcane21 wrote:
+> I strongly disagree with dropping non Parsoid support. Parsoid is incredibly costly, and while I would love to switch my LQT enabled wiki to Flow, I have no desire to install costly backend software to do so, nor would many smaller non WMF wikis with more limited resources, and if it means it performs less optimally, I would consider that an acceptable compromise to retain non Parsoid functionality.
+
+Costly in what way, exactly?
+
+* Requires a lot of man-hours to install?
+* Difficult to maintain?
+* Requires high-end services or equipment to run?
+
+Maybe there's a way Parsoid could be easier for you to use.
+
+The main reason we want to remove support for non-Parsoid is that it is costly (mainly in software engineer time) to maintain two versions of key parts of the code.",1428979580,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","I strongly disagree with dropping non Parsoid support. Parsoid is incredibly costly, and while I would love to switch my LQT enabled wiki to Flow, I have no desire to install costly backend software to do so, nor would many smaller non WMF wikis with more limited resources, and if it means it performs less optimally, I would consider that an acceptable compromise to retain non Parsoid functionality.
+
+LQT was thrown under the bus, more or less, because the WMF found Flow to be a better long term solution, and I would rather the WMF take more time to ensure non Parsoid fallback compatibility (which is advantageous to the WMF if Parsoid fails for some reason) than to eliminate any failsafes and disadvantage any other wikis wishing to use Flow.",1428100837,PHID-USER-iy4yqj4ftn74e3b5fy3e,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","I strongly disagree with dropping non Parsoid support. Parsoid is incredibly costly, and while I would love to switch my LQT enabled wiki to Flow, I have no desire to install costly backend software to do so, nor would many smaller non WMF wikis with more limited resources, and if it means it performs less optimally, I would consider that an acceptable compromise to retain non Parsoid functionality.",1428100573,PHID-USER-iy4yqj4ftn74e3b5fy3e,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1072830, @Ricordisamoa wrote:
+>>>! In T72148#730402, @coren wrote:
+>> In my specific usecase I was able to switch to html format at little cost or effort; but it would seem to me that a hard dependency on Parsoid is going to severely restict the number of non-WMF sites who can deploy that otherwise very valuable extension.
+>> 
+>> I don't get to set priorities on dev time, but I'm pretty sure that dropping wikitext markup would be a Bad Idea™
+> 
+> Sure. Medium and small-sized wikis may just want a better discussion system without being willing to install Parsoid or VisualEditor.
+
+The problem is, no one is testing the non-Parsoid configuration much.  As far as I know, there is no automated browser testing for that configuration.  And I don't even know of anyone regularly using wikis with the non-Parsoid configuration and reporting back (informally or formally).
+
+It's better to have one well-tested path, then two paths, one of which sorta works but has random breakage that doesn't immediately get caught.  This also requires maintaining extra code.
+
+That's why we are leaning towards eliminating it ({T88908}).",1425182896,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#1072844, @EBernhardson wrote:
+> MediaWiki is moving to soa, parsoid will likely be one of several services wikis require for various features.  The best solution is going to be working with the SOA team to ensure making services available works with your use case.
+
+The effort in librarization is valuable, but it seems that just running a simple MediaWiki is going to get harder and harder...",1425045094,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","MediaWiki is moving to soa, parsoid will likely be one of several services wikis require for various features.  The best solution is going to be working with the SOA team to ensure making services available works with your use case.",1425010728,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext",">>! In T72148#730402, @coren wrote:
+> In my specific usecase I was able to switch to html format at little cost or effort; but it would seem to me that a hard dependency on Parsoid is going to severely restict the number of non-WMF sites who can deploy that otherwise very valuable extension.
+> 
+> I don't get to set priorities on dev time, but I'm pretty sure that dropping wikitext markup would be a Bad Idea™
+
+Sure. Medium and small-sized wikis may just want a better discussion system without being willing to install Parsoid or VisualEditor.",1425008341,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","**gerritadmin** wrote:
+
+Change 169711 had a related patch set uploaded by Matthias Mullie:
+(bug 70148) Fix new topic creation with wikitext storage
+
+https://gerrit.wikimedia.org/r/169711",1414593342,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","In my specific usecase I was able to switch to html format at little cost or effort; but it would seem to me that a hard dependency on Parsoid is going to severely restict the number of non-WMF sites who can deploy that otherwise very valuable extension.
+
+I don't get to set priorities on dev time, but I'm pretty sure that dropping wikitext markup would be a Bad Idea™",1409285431,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+"""Create new topic"" does not work with $wgFlowContentFormat = wikitext","https://www.mediawiki.org/wiki/Extension:Flow#Dependencies mentions this bug, and emphasizes the html format with Parsoid is what WMF uses and tests.
+
+We could drop wgFlowCoptentFormat = wikitext if it makes life easier...",1409279767,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-mpn6fh3vjrwqonjyzkti,task_subcomment,NA
+data labels in imageinfo API don't make sense,"The data currently returned by the imageinfo API assigns the author to ""artist"" and the source to ""credit"". Both of these are incorrectly labeled. In particular these labels make it difficult to figure out the proper attribution for the image, as it sounds like you should use ""credit"", but you should actually use ""artist"".
+
+https://en.m.wikipedia.org/w/api.php?action=query&format=json&prop=imageinfo&titles=File%3ALiber_Eliensis%2EPNG&iiprop=url%7Cextmetadata
+
+--------------------------
+**Version**: master
+**Severity**: normal",1408730400,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_description,declined
+data labels in imageinfo API don't make sense,"I'll be bold and decline. With file metadata being migrated to WikibaseMediaInfo, I see little value on working on CommonsMetadata.",1603828394,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Change 231505 abandoned by Gergő Tisza:
+Rename extmetadata labels to be more intuitive
+
+Reason:
+Structured media info will obsolete this extension (or at least its current output data structure) soon.
+
+[[https://gerrit.wikimedia.org/r/231505]]",1531993101,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Tgr's patch has been sitting in Gerrit for four months without comments / review. 
+How to proceed / who to review?",1450267728,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Change 231505 had a related patch set uploaded (by Gergő Tisza):
+Rename extmetadata labels to be more intuitive
+
+[[https://gerrit.wikimedia.org/r/231505]]
+",1439545311,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"@Tgr: I would suggest changing:
+* Artist to Author
+* Credit to FileSource (https://gerrit.wikimedia.org/r/#/c/107368)
+* ImageDescription to FileDescription
+And possibly:
+* UsageTerms to LicenseLongName",1437767921,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"@Tgr: I would suggest changing:
+* Artist to Author
+* Credit to FileSource (https://gerrit.wikimedia.org/r/#/c/107368)
+* ImageDescription to FileDescription
+The rest look fine to me.",1437767838,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Still, the first step should be to come up with the names :)",1434557212,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"MedaViewer, OCG, MobileFrontend/mobile apps, VisualEditor are the big ones AFAIK. There are a bunch of gadgets, bots and other tools - [[ https://github.com/search?utf8=%E2%9C%93&q=extmetadata+imageinfo&type=Code&ref=searchresults | this search ]] should find the ones on GitHub. We could also just log useragents for a while.",1434557093,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"https://gerrit.wikimedia.org/r/#/c/107368/ mentions updaing ""all known clients"". Do we already have a list? A first step seems to make one.",1434543973,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Announce it on [[http://lists.wikimedia.org/pipermail/mediawiki-api-announce/|mediawiki-api-announce]], if you can't maintain BC for the old names.",1418056473,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Given how much the structured data project lags behind, I would be inclined to fix this now. @Anomie, is there any guidance on how such a breaking change to the API should be handled?",1417810294,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"See T59189#605222 for the rationale behind the field names. In hindsight, I agree it was the wrong decision, but I am not sure it is worth changing all the field names now - the API has other serious limitations and will be eventually superseded by the structured data API when wikibase will be introduced to Commons.",1508863651,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"See bug 57189 comment 1 for the rationale behind the field names. In hindsight, I agree it was the wrong decision, but I am not sure it is worth changing all the field names now - the API has other serious limitations and will be eventually superseded by the structured data API when wikibase will be introduced to Commons.",1408741667,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+data labels in imageinfo API don't make sense,"Not an API bug, it's just returning what deeper layers of MediaWiki give it. It sounds like you want the CommonsMetadata extension.",1408732994,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-5fxfxopay5yizt3sptbe,task_subcomment,NA
+MediaWiki should not expose any UI elements which require JavaScript when it is off (tracking),"**Author:** `gryllida`
+
+**Description:**
+from bug 54730#c3
+>The general design principle in MediaWiki is to only show functional user interface elements (for example, unprivileged users are not shown a delete tab or a protect tab)
+
+I would like MediaWiki to not expose any features which require JavaScript when it is off.
+
+This means, for instance, not showing visual editor's edit tab, bug 69779  (noting 'requires javascript' where necessary in the beta tab).
+
+I hope to succeed in making this a tracking bug for enforcing the above-quoted design for the ""no JS enabled"" case.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: enhancement",1408616100,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-srm34yak2agbaxyhgjji,task_description,resolved
+MediaWiki should not expose any UI elements which require JavaScript when it is off (tracking),"It certainly should not expose dead links (e.g. it would be bad if you saw a VE edit link, and clicking it did nothing).  We're fixing a similar issue in a non-deployed feature right now, in fact.
+
+My understanding is that with bug 69779, you are requesting that ""this feature requires js"" is shown especially when JS is disabled.  This makes sense, and the current intended behavior (as far as I can tell from reading the code) is that it shows only when JS is disabled.  As far as I can tell, it *does* show when JS is disabled.  You have not replied there to my latest comment and screenshot.
+
+There is a glitch where it *also* shows when JS is enabled (bug 69823) in some cases.
+
+Note, I don't think this preference behavior is clearly described by ""not expose any features"".  We want to make them aware (could be described as ""expose"") of JS-only features, but make it clear such feature can not be used without JS.
+
+Tweaking the title and adding a depends accordingly.",1408676859,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-srm34yak2agbaxyhgjji,task_subcomment,NA
+MediaWiki should not expose any UI elements which require JavaScript when it is off (tracking),[There are probably quite some open tickets already that could be marked as blocking this one],1408620867,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-srm34yak2agbaxyhgjji,task_subcomment,NA
+MediaWiki should not expose any UI elements which require JavaScript when it is off (tracking),"**gryllida** wrote:
+
+Which is probably stupid (visualeditor already does not show the edit tab when js is off; I misread earlier)",1408616344,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-srm34yak2agbaxyhgjji,task_subcomment,NA
+"VisualEditor:  Categories go at the bottom, so please place the cursor above the categories","Especially when there are only categories on the page, it does not appear to be possible to put text above the categories.  The result is things like this:
+
+http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=122314&oldid=51987
+
+which is not normally wanted.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1408562280,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-zk5ndm764k2ntbyz65kz,task_description,open
+"VisualEditor:  Categories go at the bottom, so please place the cursor above the categories","The saved page will display the text above categories. Only ""Difference between revisions"" misleadingly places the typed text under the categoreis.  ",1424825560,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-zk5ndm764k2ntbyz65kz,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Alternative: {T254277}
+
+If the ""View history"" tab changes size such that becomes too large where it before was not, an endless animation loop of collapse-expand-collapse-etc can be triggered. A resize could be caused by an ordinary zoom (frequently resizing the pixel width of the element by a few pixels), by a change in browser text size preferences (likely to significantly change the width), or by a user script modifying the text content of the element.
+
+This appears to be caused by expandCondition in Vector.js using a cached version of the element's width (collapsibleTabs.data's expandedWidth passed as the eleWidth argument), while collapseCondition is checking .width() each time.
+
+This happens when you enable `Editing mode: show both tabs is enabled in preferences` in VisualEditor and visit https://www.mediawiki.org/wiki/User:Martin_Urbanec?uselang=fr at certain screen resolutions. Demonstrated in image below:
+{F5061717}
+
+== Solutions
+
+#### Option 1 - Remove the animation and fix the collapsibletabs code:
+
+Rationale: The animation plays at times when it's not meaningful, eg. after page load. The tabs should be collapsed immediately, without animation.
+About half of the code is removed, including callbacks, resulting in a simple, less error-prone logic.
+Analysis of the bug, solution:  T71729#6183821 **Remove animation**
+
+#### Option 2 - Keep the animation, fix the collapsibletabs code:
+
+Rationale: Keeps the old functionality (animation) while safeguarding against the oscillation.
+Solution:  T71729#6183821 **Easy fix**
+
+#### Option 3 - Make the tabs responsive
+
+Rationale: No more collapsing, the tabs wrap into any number of rows.
+Mostly CSS solution with a one-liner resize event handler.
+Solution detailed: T71729#6183822 
+
+
+
+== Update 2020-05-30
+
+This bug resurfaced as a more prominent regression after the #mw1.35.0-wmf.34 deployment:
+{T253819}
+The difference is: the ""More"" (""Plus"" / ""Mehr"") menu is //not// visible:
+{F31848748}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1408416060,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_description,resolved
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",I can't replicate this any more. Please reopen with new replication steps if it's still occurring. I know there was lots of other related issues but they would likely benefit from a dedicated task at this point.,1633640757,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","(The previous patch fixes the latest issue where this problem occurred all the time; the older issue where this problem occurs rarely ""if a tab's width changes after initial page load"" still exists.)",1604911876,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",[Resetting assignee due to inactive user account],1604831127,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://sal.toolforge.org/log/fQ44ZnUBgTbpqNOm4WWZ} [2020-10-26T18:43:25Z] <catrope@deploy1001> Synchronized php-1.36.0-wmf.14/skins/Vector/: Fix logic in collapsibleTabs code (T71729) (duration: 00m 58s)",1603737805,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 636377 **merged** by jenkins-bot:
+[mediawiki/skins/Vector@wmf/1.36.0-wmf.14] Fix logic in collapsibleTabs code
+
+https://gerrit.wikimedia.org/r/636377",1603737506,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 636377 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
+[mediawiki/skins/Vector@wmf/1.36.0-wmf.14] Fix logic in collapsibleTabs code
+
+https://gerrit.wikimedia.org/r/636377",1603734524,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 636068 **merged** by jenkins-bot:
+[mediawiki/skins/Vector@master] Fix logic in collapsibleTabs code
+
+https://gerrit.wikimedia.org/r/636068",1603474357,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 636068 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
+[mediawiki/skins/Vector@master] Fix logic
+
+https://gerrit.wikimedia.org/r/636068",1603472347,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",oh.. whoops.,1603472288,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","`mw.util.showPortlet( 'p-cactions' )` reveals the portal. If it's not displaying  I suspect 6d967ed4a8c is more to blame here.
+",1603471990,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","`mw.util.showPortlet( '#p-cactions' )` doesn't seem to be revealing the more menu as it should do so I suspect 6d967ed4a8c is more to blame here.
+",1603471940,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","The current issue is distinct and maybe we should file a separate task. Whenever any tabs should be collapsed into the ""More"" menu, and the menu isn't already visible, it doesn't actually appear, and the tabs animate back and forth forever.
+
+I did a git-bisect and this bug seems to have been introduced in {711a41812aac6fe91432d3733805f3d96b7b90a0}, although I haven't tried to figure out what about that code causes it.",1603471691,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This is an extremely large number of duplicates, for a task that has been sitting here quietly for years with barely anyone ever noticing the problem.
+
+Could something have changed recently in Vector to make this scenario more common?",1603471088,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","To clarify the reading web team that I am tech lead for,  who are the maintainers of this skin (and legacy version) talked through this task yesterday in our team time meeting. It was agreed that we don't want to make any changes to legacy mode at this point so we will keep the code for now. In general we are not working on legacy bugs as part of the desktop improvements project - the project is considered frozen with the exceptions of changes that aid the new modern experience we are building. We decided to retain the collapsible tabs code and this bug. In future we'd like to rewrite and improve this code but right now we don't believe that fits into our current goals.
+
+I am thus punting this back to the backlog. This task about fixing the existing bug remains stalled on a decision in T254277 which we hope to revisit further into the project. If we decide not to review it, we may decide to rewrite it or simply continue to maintain it as we do now (in which case this task can be unstalled and worked on).
+",1591380797,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Thanks for the explanation, @matmarex. I believe the Readers-Web-Team is a developer team, at least in the context of DI, so calling it a maintenance team was very confusing to me.
+
+>>! In T71729#6194759, @Jdlrobson wrote:
+> The maintenance team has no interest in working or review patches for this task right now 
+@Jdlrobson  I was trying to understand this sentence. As you are the one reviewing the patches mostly (at least mine), referring to yourself wouldn't be confusing.
+I understand you prefer to axe the tab collapsing instead of fixing it. I've detailed why that's not feasible currently and for quite some time. 
+As I said if and **when** this patch is requested, I'll do it.
+
+> ... is likely to be wasted effort and I know you don't like to do that. 
+
+We should chat sometime so you can get to know me better. I've seen many times in the months we've been collaborating that my values and motivations are misunderstood or assumed to be something it is not.",1591374434,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","There is no ""maintenance team"", Jon was just referring to the Readers Web team (including himself), who maintain the Vector skin.",1591362627,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6195375, @Aklapper wrote:
+>>>! In T71729#6194862, @Demian wrote:
+>> Is that the release engineering team?
+> No it's not.
+Which one it is? Can I ask?
+",1591363925,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6195375, @Aklapper wrote:
+>>>! In T71729#6194862, @Demian wrote:
+>> Is that the release engineering team?
+> No it's not.
+Which one it is? Should I guess or can I ask?
+",1591350026,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6194862, @Demian wrote:
+> Is that the release engineering team?
+
+No it's not.
+
+> Spikes? Do you mean the 3 regressions in one week?
+
+No but [spikes](https://phabricator.wikimedia.org/maniphest/query/MlM0ymF.hVn7/#R).",1591344701,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6194759, @Jdlrobson wrote:
+> @demian please don't work on this task. Any effort expended here right now is likely to be wasted effort 
+Thanks for informing me. This is what I expected.
+
+> The maintenance team has no interest in working or review patches for this task right now 
+maintenance team? Never heard of them. Is that the release engineering team?
+
+> after our recent spikes.
+Spikes? Do you mean the 3 regressions in one week? (T249372)
+",1591316243,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",@demian please don't work on this task. Any effort expended here right now is likely to be wasted effort and I know you don't like to do that. The maintenance team has no interest in working or review patches for this task right now after our recent spikes.,1591313755,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","3 different solutions detailed above and in the description. I'll do the patch in a day, if it is decided to accept any of these fixes.",1591311231,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 601368 abandoned by Jdlrobson:
+[legacy] Drop the collapsibleTabs code
+
+Reason:
+To be reconsidered at a later date.
+
+[[https://gerrit.wikimedia.org/r/601368]]",1591291387,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",I've opened up T254277 to propose removing this code.,1591127145,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Solution
+
+> The code is definitely not going to be run in the new Vector and is pretty complex for what it does. 
+
+It's mostly essential complexity for the functionality that was intended. The code is actually good for practicing code reading skills: one aspect of mediawiki code that I appreciate is that a big percentage of the code is diligently written and formatted, resulting in very well readable code. Above the average of what I usually encounter.
+
+I see 3 solutions. 
+**1st solution** completely removes this code (collapsing tabs). In this case the tabs will wrap in narrow windows. With the SearchBox moved to the header this will affect windows narrower by about 320px than in legacy, but still not avoidable, it can still happen at above 900px width:
+{F31850806}
+Therefore the tabs row needs a proper responsive layout that can wrap properly. This means having `#left-navigation` and `#right-navigation` only in `#mw-head`. With the personal menu moved to the header this will be the case. I've submitted numerous patches in the past months to do this refactor and layout with flexbox.
+
+Further complication will be to move the content down when the tabs wrap. With the tabs being absolute positioned now, this would require JS. A compromise that I wouldn't do, but it's an acceptable compromise, imho.
+Alternatively, the tabs can be positioned above the content with flexbox (problem with some basic browsers that should be auto-updated), or the tabs can be before the content in the HTML.
+
+**2nd solution** only removes the animation, but does collapse the tabs: I've detailed this as ""Easy fix"" in the Analysis section, above.
+
+> The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.
+
+For legacy 2 solutions can be applied: **2nd solution** which only removes the animation (""Easy fix""), **3rd solution** that keeps the animation (""complicated fix""), both detailed in Analysis section, above.
+
+I'm happy to submit a patch for any of these solutions, if you wish.",1591163582,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Solution
+
+> The code is definitely not going to be run in the new Vector and is pretty complex for what it does. 
+
+It's mostly essential complexity for the functionality that was intended. The code is actually good for practicing code reading skills: one aspect of mediawiki code that I appreciate is that a big percentage of the code is diligently written and formatted, resulting in very well readable code. Above the average of what I usually encounter.
+
+I see 3 solutions. 
+**1st solution** completely removes this code (collapsing tabs). In this case the tabs will wrap in narrow windows. With the SearchBox moved to the header this will affect windows narrower by about 320px than in legacy, but still not avoidable, it can still happen at above 900px width:
+{F31850806}
+Therefore the tabs row needs a proper responsive layout that can wrap properly. This means having `#left-navigation` and `#right-navigation` only in `#mw-head`. With the personal menu moved to the header this will be the case. I've submitted numerous patches in the past months to do this refactor and layout with flexbox.
+
+Further complication will be to move the content down when the tabs wrap. With the tabs being absolute positioned now, this would require JS. A compromise that I wouldn't do, but it's an acceptable compromise, imho.
+Alternatively, the tabs can be positioned above the content with flexbox (problem with some basic browsers that should be auto-updated), or the tabs can be before the content in the HTML.
+
+**2nd solution** only removes the animation, but does collapse the tabs: I've detailed this as ""Easy fix"" in the Analysis section, above.
+
+> The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.
+
+For legacy 2 solutions can be applied: 2nd solution which only removes the animation (""Easy fix""), 3rd solution that keeps the animation (""complicated fix""), both detailed in Analysis section, above.
+
+I'm happy to submit a patch for any of these solutions, if you wish.",1591163563,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Solution
+
+> The code is definitely not going to be run in the new Vector and is pretty complex for what it does. 
+
+It's mostly essential complexity for the functionality that was intended. The code is actually good for practicing code reading skills: one aspect of mediawiki code that I appreciate is that a big percentage of the code is diligently written and formatted, resulting in very well readable code. Above the average of what I usually encounter.
+
+I see 3 solutions. 1st one completely removes this code (collapsing tabs). In this case the tabs will wrap in narrow windows. With the SearchBox moved to the header this will affect windows narrower by about 320px than in legacy, but still not avoidable, it can still happen at above 900px width:
+{F31850806}
+Therefore the tabs row needs a proper responsive layout that can wrap properly. This means having `#left-navigation` and `#right-navigation` only in `#mw-head`. With the personal menu moved to the header this will be the case. I've submitted numerous patches in the past months to do this refactor and layout with flexbox.
+
+Further complication will be to move the content down when the tabs wrap. With the tabs being absolute positioned now, this would require JS. A compromise that I wouldn't do, but it's an acceptable compromise, imho.
+Alternatively, the tabs can be positioned above the content with flexbox (problem with some basic browsers that should be auto-updated), or the tabs can be before the content in the HTML.
+
+2nd solution only removes the animation, but does collapse the tabs: I've detailed this as ""Easy fix"" in the Analysis section, above.
+
+> The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.
+
+For legacy 2 solutions can be applied: 2nd solution which only removes the animation (""Easy fix""), 3rd solution that keeps the animation (""complicated fix""), both detailed in Analysis section, above.
+
+I'm happy to submit a patch for any of these solutions, if you wish.",1591079087,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Solution
+
+> The code is definitely not going to be run in the new Vector and is pretty complex for what it does. 
+
+It's mostly essential complexity for the functionality that was intended. The code is actually good for practicing code reading skills: one aspect of mediawiki code that I appreciate is that a big percentage of the code is diligently written and formatted, resulting in very well readable code. Above the average of what I usually encounter.
+
+I see 3 solutions. 1st one completely removes this code (collapsing tabs). In this case the tabs will wrap in narrow windows. With the SearchBox moved to the header this will affect windows narrower by about 320px than in legacy, but still not avoidable, it can still happen at above 900px width:
+{F31850806}
+Therefore the tabs row needs a proper responsive layout that can wrap properly. This means having `#left-navigation` and `#right-navigation` only in `#mw-head`. With the personal menu moved to the header this will be the case. I've submitted numerous patches in the past months to do this refactor and layout with flexbox.
+
+Further complication will be to move the content down when the tabs wrap. With the tabs being absolute positioned now, this would require JS. A compromise that I wouldn't do, but it's an acceptable compromise, imho.
+Alternatively, the tabs can be positioned above the content with flexbox (problem with some basic browsers that should be auto-updated), or the tabs can be before the content in the HTML.
+
+2nd solution only removes the animation, but does collapse the tabs: I've detailed this as ""Easy fix"" in the Analysis section, above.
+
+> The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.
+
+For legacy 2 solutions can be applied: 2nd solution which only removes the animation (""Easy fix""), 3rd solution that keeps the animation (""complicated fix""), both detailed in Analysis section, above.
+",1591079035,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Analysis
+
+I think this requires a bit more thought. A quick look at the code reveals one design mistake that starts the infinite cycle: [[ https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/601368/5/resources/skins.vector.legacy.js/collapsibleTabs.js#b147 | line 147 ]] calling
+`rAF( $.collapsibleTabs.handleResize );`
+after the animation (hiding/showing ONE tab) finishes. I assume to hide another tab, if necessary.
+* The immediate issue: does not check if the direction changes (hide -> show -> hide). **Easy fix**: on resize event save direction, on animation end check the direction is the same for the next tab to be hidden/shown.
+** **Remove animation.** It's even easier to fix if the animation is removed: a loop can do (hide -> get size -> repeat if needed) in one cycle, the recalculation after the animation becomes unnecessary, which is the source of the design error.
+* The design issue: the number of hidden tabs should be decided **only once**, upon receiving the `resize` event. 
+** That's a more **complicated fix**, `collapseCondition` needs to be replaced by a logic that iterates the tabs and marks for hiding as many tabs as necessary to fit the available width.
+** Without animation it's unnecessary to be this elaborate.
+",1591163748,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Analysis
+
+I think this requires a bit more thought. A quick look at the code reveals one design mistake that starts the infinite cycle: [[ https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/601368/5/resources/skins.vector.legacy.js/collapsibleTabs.js#b147 | line 147 ]] calling
+`rAF( $.collapsibleTabs.handleResize );`
+after the animation (hiding/showing ONE tab) finishes. I assume to hide another tab, if necessary.
+* The immediate issue: does not check if the direction changes (hide -> show -> hide).
+** **Easy fix**. It's even easier to fix if the animation is removed: a loop can do (hide -> get size -> repeat if needed) in one cycle, the recalculation after the animation becomes unnecessary, which is the source of the design error.
+* The design issue: the number of hidden tabs should be decided **only once**, upon receiving the `resize` event. 
+** That's a more **complicated fix**, `collapseCondition` needs to be replaced by a logic that iterates the tabs and marks for hiding as many tabs as necessary to fit the available width.
+** Without animation it's unnecessary to be this elaborate.
+",1591163606,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","
+==== Analysis
+
+I think this requires a bit more thought. A quick look at the code reveals one design mistake that starts the infinite cycle: [[ https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/601368/5/resources/skins.vector.legacy.js/collapsibleTabs.js#b147 | line 147 ]] calling
+`rAF( $.collapsibleTabs.handleResize );`
+after the animation (hiding/showing ONE tab) finishes. I assume to hide another tab, if necessary.
+* The immediate issue: does not check if the direction changes (hide -> show -> hide).
+** Easy fix. It's even easier to fix if the animation is removed: a loop can do (hide -> get size -> repeat if needed) in one cycle, the recalculation after the animation becomes unnecessary, which is the source of the design error.
+* The design issue: the number of hidden tabs should be decided **only once**, upon receiving the `resize` event. 
+** That's more complicated, `collapseCondition` needs to be replaced by a logic that iterates the tabs and marks for hiding as many tabs as necessary to fit the available width.
+** Without animation it's unnecessary to be this elaborate.
+",1591079028,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6183507, @Jdlrobson wrote:
+> ""with a valid purpose."" 
+> Just because something has existed for a long time doesn't mean a good decision was made. :)
+That's a good summary of my opinion on many decisions in MediaWiki :-) Some of which I've already discussed previously, hoping you'd say the same there ;-)
+
+However, in this case I referred exactly to a functionality, not a decision. Tabs can get pretty long (see for ex. [[ https://commons.wikimedia.org/wiki/User:Aron_Manning?useskin=vector | user pages imported from meta ]] with a ""View on meta.wikimedia.org"" tab), just cutting this code will result in:
+{F31850773}
+At 1200px width!
+
+I don't think that can be released to the public. There is a gap to be filled after cutting this code that needs to be planned, designed and implemented. I estimate that will take weeks. In the situation where a recently introduced regression needed fixing, this approach was unfeasible, this is why I've downvoted the patch immediately.
+
+Other than that, I think this code was fickle, and the animation might have looked good when Vector was created, but it's unusual today, so I agree it needs to be revisited. TBH I wanted to get rid of the animation for a long time, I dislike it that much. However, whether cutting it entirely is a good decision, depends on what's the alternative and I sense an ""`rm -rf *` removes all bugs"" approach that will certainly result in another disappointment for the users (aka. community).
+",1591079018,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","""with a valid purpose."" 
+Just because something has existed for a long time doesn't mean a good decision was made. :)
+
+The code is definitely not going to be run in the new Vector and is pretty complex for what it does. The question becomes whether we want to maintain this as part of the legacy skin. I have various compromises in my head, and I'll be considering them during the course of this week and suggesting some options.",1591053536,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","@Jdlrobson the collapsibleTabs code existed for years with a valid purpose. I think removing it will raise some eyebrows at best, or cause further breakages at worst.
+Shouldn't we focus on fixing what's been broken by T249372 and T253912 and can be fixed easily, without any complications?",1591029296,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 601368 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
+[mediawiki/skins/Vector@master] Drop the collapsibleTabs code
+
+[[https://gerrit.wikimedia.org/r/601368]]",1591028881,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This code is clearly problematic and clearly hard to maintain it.
+
+Given Vector is not a responsive skin I honestly feel we should remove this code. Optimising the experience of Wikipedia at that resolution is not solving any problem except adding code complexity for a small gain.",1591025288,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","@Demian: ??? Leaving tickets open when tickets don't get completely fixed.
+
+(PS: I don't think that pinging after less than 24h on a weekend is constructive.)",1590998359,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",@Demian: ??? Leaving tickets open when tickets don't get completely fixed.,1590996544,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",@Aklapper Can you please answer the above //relevant// question?,1590959077,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6179380, @Aklapper wrote:
+> Again: This is definitely not Unbreak Now ([""Something is broken and needs to be fixed immediately, setting anything else aside.""](https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities)). Please stop setting that priority.
+Apparently there's no agreement on that: if the image of Wikimedia matters then it needs to be fixed immediately. That being said it does not matter until the next SWAT window, which is on Monday. If you don't agree, I'm happy to discuss this, but please do so off-ticket, it's off-topic here.
+
+@Aklapper the fix I've submitted is for a new regression introduced in wmf.34, which was reported in a wave of recent tickets that were closed as duplicates. //Those// look similar, but in fact aren't duplicates of //this// bug from 2014. This causes quite some confusion as people believe these are the same issue, furthermore the original bug won't be fixed by the patch, thus the ticket cannot be closed, leading to further confusion. What solution do you propose to untangle this?
+",1590896861,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#6179380, @Aklapper wrote:
+> Again: This is definitely not Unbreak Now ([""Something is broken and needs to be fixed immediately, setting anything else aside.""](https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities)). Please stop setting that priority.
+Apparently there's no agreement on that: if the image of Wikimedia matters then it needs to be fixed immediately. That being said it does not matter until the next SWAT window, which is on Monday. If you don't agree, I'm happy to discuss this, but please do so off-ticket, it's off-topic here.
+
+@Aklapper the fix I've submitted is for a new regression introduced in wmf.34, which was reported in a wave of recent tickets that were closed as duplicates. //Those// look the similar, but in fact aren't duplicates of //this// bug from 2014. This causes quite some confusion as people believe these are the same issue, furthermore the original bug won't be fixed by the patch, thus the ticket cannot be closed, leading to further confusion. What solution do you propose to untangle this?
+",1590896812,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Again: This is definitely not Unbreak Now ([""Something is broken and needs to be fixed immediately, setting anything else aside.""](https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities)). Please stop setting that priority.",1590879547,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","With a fix ready to be merged and considering the loss of prestige caused by this bug, I think it now matches the [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | ""Unbreak Now"" ]] criteria.
+CC the participants from the sister hotfix: @Niedzielski @Jdlrobson 
+
+This missed the wmf.34 train though...",1590878921,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","With a fix ready to be merged and considering the loss of prestige caused by this bug, I think it matches the [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | ""Unbroken Now"" ]] criteria.
+CC the participants from the sister hotfix: @Niedzielski @Jdlrobson 
+
+This missed the wmf.34 train though...",1590853408,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","With a fix ready to be merged and considering the loss of prestige caused by this bug, I think it matches the [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | ""Unbroken Now"" ]] criteria.
+CC the participants from the sister hotfix: @Niedzielski @Jdlrobson 
+",1590853190,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Hotfix:  https://gerrit.wikimedia.org/r/600358
+
+Related regression: {T253912}
+
+Broken by:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/589395/39/resources/skins.vector.legacy.js/vector.js#32
+Reverted in CSS but not JS:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/599468
+
+I think this can be ""Unbroken Now""
+Won't fix the elusive bug from 2014, though. This is a new regression.",1590851708,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Hotfix:  https://gerrit.wikimedia.org/r/600358
+
+Related regression: {T253912}
+
+Broken by:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/599468
+not reverting:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/589395/39/resources/skins.vector.legacy.js/vector.js#32
+
+I think this can be ""Unbroken Now""
+Won't fix the elusive bug from 2014, though. This is new.",1590851433,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Related regression: {T253912}
+
+Broken by:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/599468
+not reverting:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/589395/39/resources/skins.vector.legacy.js/vector.js#32
+
+I think this can be ""Unbroken Now""
+Won't fix the elusive bug from 2014, though. This is new.",1590850983,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Related regression: {T253912}
+
+Broken by:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/599468
+not reverting:
+https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/589395/39/resources/skins.vector.legacy.js/vector.js#32
+
+I think this can be ""Unbroken Now""",1590850855,PHID-USER-724ccjw2eq65o2te67qg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 600358 had a related patch set uploaded (by Aron Manning; owner: Aron Manning):
+[mediawiki/skins/Vector@master] Hotfix: Cannot rename `.emptyPortlet` to `.vector-menu-empty` yet. JS follow-up.
+
+[[https://gerrit.wikimedia.org/r/600358]]",1590850502,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","@dbarratt No. I did take a brief look at the code, but it's not something I feel I would be able to fix. 
+
+I was trying to be helpful and setting the priority as an ""experienced community member"" as described at  https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities since the task is unassigned, the situation has obviously changed since it was assessed as Low, and it looks bad to have such a highly visible task described as ""Low priority"". However I'll change it to Needs Triage so someone else can figure it out.",1590848865,PHID-USER-grgqimagqq3ankitlzm5,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","See: https://www.mediawiki.org/wiki/Phabricator/Project_management#Priority_levels
+
+@Pcoombe Are you (or your team) planning to work on this?",1590847212,PHID-USER-g5rqg2k7irztdonlursm,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","See: https://www.mediawiki.org/wiki/Phabricator/Project_management#Priority_levels
+
+@Pcoombe Are you planning to work on this?",1590847098,PHID-USER-g5rqg2k7irztdonlursm,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",This does not meet the criteria for an Unbreak Now!,1590846988,PHID-USER-g5rqg2k7irztdonlursm,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",Also happens on main page of dewiki at a zoom level of 133 percent when not logged in.,1590846618,PHID-USER-7sfnmvwpvh3etwtqk5pg,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",Boldly raising priority: given the number of duplicates this seems to have become much more common recently. Also seen a mention (with video) on Reddit https://www.reddit.com/r/softwaregore/comments/gtbdwu/cant_fit_all_the_buttons_in_the_frame_wikipedia/,1590843472,PHID-USER-grgqimagqq3ankitlzm5,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","That will be deployed next week, per the usual schedule. This task is not entirely fixed -- the tabs will still expand and collapse once on page load if you're using an unfortunate screen resolution. But correcting that is more difficult :/",1484268689,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 331919 merged by jenkins-bot:
+collapsibleTabs: Stop the tabs from collapsing back and forth forever
+
+[[https://gerrit.wikimedia.org/r/331919]]",1484268219,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This doesn't fix the issue entirely, but it should reduce it to mildly annoying. The tabs might still collapse back-and-forth once, but after that happens the code will update some internal calculations, and it should prevent the tabs from flapping forever.",1484260478,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Change 331919 had a related patch set uploaded (by Bartosz Dziewoński):
+collapsibleTabs: Stop the tabs from collapsing back and forth forever
+
+[[https://gerrit.wikimedia.org/r/331919]]
+",1484260214,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This has also been reported to us in OTRS, and I can easily reproduce it (at least in incognito mode) on local file description pages like https://de.wikipedia.org/wiki/Datei:Otzenrathpano2.jpg?uselang=de. So I'd also like to echo that this issue is easy to run into at the moment, which makes me wonder if this should really be treated as a low-priority issue.",1483643129,PHID-USER-x44asswe5g7265gs7ue4,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Grabbing some popcorn and selecting the `<li id=""ca-edit"">` element in Firefox' dev tools, things seem to happily jump around between three states: `display: list-item` with `right: 0px` not being applied, replaced by `display: block` with `left: 0px` not being applied and vice versa; plus only very occasionally also the 3rd screenshot with `div.vectorTabs` not being in the game at all:
+{F5228098}
+F5228098",1483536304,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I'm getting this on my non-existent user page (which is copied from Meta) at mediawiki.org in Firefox 50, with ""Show me both editor tabs"" enabled.  I can't trigger it without this setting.  With that setting, on a non-existent userpage, there are three long descriptions in tabs at the top of the page, and the last hides and un-hides repeatedly.  
+
+My browser window right now is about 1428 pixels wide.  To trigger it in English, I need to zoom in twice.  The default zoom triggers it in Russian.  Zooming in once or twice triggers it with the UI set to German.  So (the point of this message) if you aren't seeing it in your browser, then you might try enabling two tabs, switching to a couple of different languages with `?uselang=xx`, and/or zooming in and out a couple of steps.
+",1483466065,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I'm getting this on my non-existent user page (which is copied from Meta) at mediawiki.org in Firefox 50, with ""Show me both editor tabs"" enabled.  I can't trigger it without this setting.  With that setting, on a non-existent userpage, there are three long descriptions in tabs at the top of the page, and the last hides and un-hides repeatedly.  
+
+My browser window right now is about 1428 pixels wide.  To trigger it in English, I need to zoom in twice.  The default zoom triggers it in Russian.  Zooming in once or twice triggers it with the UI set to German.  So (the point of this message) if you aren't seeing it in your browser, then you might try enabling  switching to a couple of different languages with `?uselang=xx` or zooming in and out a couple of steps.
+",1483466015,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I noticed the problem today for the first time on my PC (Chromium), before I had experienced it only on the tablet. It happened with a user page on de.wiki that derived from meta, a similar case as the above mentioned.",1483199629,PHID-USER-zrh22rct2jo5hs6nu67r,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I've tried to reproduce locally without success
+
+`File:Opening Karte_Gemeinde_Gommiswald_2013.png?uselang=de` with private browsing, with latest master of MediaWiki and Vector, with InstantCommons enabled, and adding this to LocalSettings.php to mimick the addition of the third tab (to avoid installing VisualEditor):
+
+```
+function test_onSkinTemplateNavigation_Universal( &$sktemplate, &$links ) {
+        $links['views']['whatever'] = [
+                'class' => 'collapsible',
+                'text' => 'Lokalen Beschreibungsquelltext hinzufügen',
+                'href' => '#'
+        ];
+
+        if ( isset( $links['views']['edit'] ) ) {
+                $links['views']['edit']['primary'] = true;
+        }
+}
+
+$wgHooks['SkinTemplateNavigation::Universal'][] = 'test_onSkinTemplateNavigation_Universal';
+```
+
+In one tab, dewiki page, in other tab my local wiki. On dewiki the bug happens, on my local wiki it doesn't. Texts and dimensions of the tabs are the same. The generated HTML for both (before running JavaScript) is equivalent.
+
+So the only variable that is left here that might cause the problem is Visual Editor. But why?",1483199227,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","> Judging by the number of reports, this has started happening more frequently for some reason.
+Indeed.
+
+As I don't get the effect in the link of the initial description here is an other example: 
+https://de.wikipedia.org/wiki/Datei:Karte_Gemeinde_Gommiswald_2013.png.
+The animation-loop happens from the start (without changing window-width).
+
+Firefox v.50: `1173px` to `1428px`
+Chromium v.53: `1113px` to `1341px`  (witch are quite average widths)",1483154649,PHID-USER-xjpggc6wz3et2e52c3my,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",Might have been caused by https://phabricator.wikimedia.org/rSVEC1f26153a5d77584508f8bbd10478e8d8021ccb42,1482943473,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Judging by the number of reports, this has started happening more frequently for some reason.",1482938453,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","As far as I can tell (T108588#1640647) FlaggedRevs prevents VE from using the desired labels for editing tabs on server side, thus forcing VE to modify them on client side, triggering this bug.",1481966449,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","No, FlaggedRevs doesn't do that, and is not affected. To my knowledge, VisualEditor is the only tool that's causing this.",1481894379,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#2878053, @Jdforrester-WMF wrote:
+> This is not VE-specific, right? Anything that adjusts the tabs after the PHP layer is done with it, like FlaggedRevs and some gadgets, has this problem?
+
+True, the VE-specific bug (see T71729#1611561) is T108588",1481834873,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","This is not VE-specific, right? Anything that adjusts the tabs after the PHP layer is done with it, like FlaggedRevs and some gadgets, has this problem?",1481833225,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","I got this today when reviewing changes from article's history one by one and the FlaggedRevs' ""Pending edits"" tab probably interfered.",1444670842,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#1611561, @Ciencia_Al_Poder wrote:
+>If that's not supported, VisualEditor shouldn't be doing that, right?
+
+Indeed. That JavaScript is there in case the server failed to do it correctly (or in case of cached html). Looks like the ru.wikipedia.org configuration is not supported correctly by the server-side equivalent of that code.
+
+https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/667d8d9935/VisualEditor.hooks.php#L136-L175
+
+> ```lang=php
+>	$tabMessages = $config->get( 'VisualEditorTabMessages' );
+>	..
+>	if ( .. ) {
+>		$editTabMessage = $tabMessages[$action . 'localdescriptionsource'];
+>	} else {
+>		$editTabMessage = $tabMessages[$action . 'source'];
+>	}
+> ```",1441464903,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",,1441465277,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",,1441464832,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Well, that VE thing seems to be tracked on T108588 instead",1441460883,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#1027038, @Krinkle wrote:
+> Changing the value of existing tabs is not supported. Can you provide an example or use case where this happens?
+> 
+> Such customisations (if desired) should be done upstream as part of Vector, or at least done server-side (e.g. by changing the MediaWiki namespace message for it, or by creating a hook in your LocalSettings configuration).
+
+Reported again in T111601, Cokersed shows a nice video of it http://elric.ga/files/out-1.ogv
+
+I see that on initial page load, there are 2 ""edit"" tabs with the same text: `Править`. Then, once the page finishes loaded, the text of the ""not-ve edit"" is changed to `Править вики-текст`
+
+I've inspected a bit of JS and I see that it seems to be changed by #VisualEditor
+
+https://ru.wikipedia.org/static/1.26wmf21/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.DesktopArticleTarget.init.js
+
+```
+			// Alter the edit tab (#ca-edit)
+			if ( $( '#ca-view-foreign' ).length ) {
+				if ( tabMessages[ action + 'localdescriptionsource' ] !== null ) {
+					$caEditLink.text( mw.msg( tabMessages[ action + 'localdescriptionsource' ] ) );
+				}
+			} else {
+				if ( tabMessages[ action + 'source' ] !== null ) {
+					$caEditLink.text( mw.msg( tabMessages[ action + 'source' ] ) );
+				}
+			}
+```
+
+If that's not supported, Visual Editor shouldn't be doing that, right?",1441459500,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen",">>! In T71729#1027038, @Krinkle wrote:
+> Changing the value of existing tabs is not supported. Can you provide an example or use case where this happens?
+> 
+> Such customisations (if desired) should be done upstream as part of Vector, or at least done server-side (e.g. by changing the MediaWiki namespace message for it, or by creating a hook in your LocalSettings configuration).
+
+Given T108588, does VisualEditor change the tabs on client-side? If so, this definitely isn't ""Lowest"" priority.",1439222763,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen","Changing the value of existing tabs is not supported. Can you provide an example or use case where this happens?
+
+Such customisations (if desired) should be done upstream as part of Vector, or at least done server-side (e.g. by changing the MediaWiki namespace message for it, or by creating a hook in your LocalSettings configuration).",1423540184,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-gvjursv5fwpt4kgzz2v7,task_subcomment,NA
+"VisualEditor:  Please show the file name in the media dialog, and make it easy to copy it","Steps to reproduce:
+
+1.  Open a page that contains an image that has a really long or complicated name.
+
+2.  Think, ""Hey, I could use that image over at ______ article, too.""
+
+3.  Click on the image.  What's its name?  Well, it starts off as File:Foo bar baz bat... but who knows what the rest of it is.
+
+
+It would be nice to be able to see the entire name of the image and to copy that name as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408405260,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gfvkr44kb7p4gblp7hfj,task_description,resolved
+"VisualEditor:  Please show the file name in the media dialog, and make it easy to copy it","I added `[[File:Diederich Graminaeus (1550-1610). Beschreibung derer Fürstlicher Güligscher ec. Hochzeit (Johann Wilhelm von Jülich-Kleve-Berg ∞ Jakobe von Baden-Baden, Hochzeit in Düsseldorf im Jahre 1585), Köln 1587, Ringrennen am 18. Juni 1585 in Pempelfort.jpg]]` to my page, loaded it in VE and looked at the media dialog. I could see and copy the whole thing, so I assume this got resolved at some point.",1437955553,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-gfvkr44kb7p4gblp7hfj,task_subcomment,NA
+"VisualEditor:  Please show the file name in the media dialog, and make it easy to copy it","Being able to copy it from the tooltip would work for me, for example.",1409469981,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-gfvkr44kb7p4gblp7hfj,task_subcomment,NA
+"VisualEditor: ""New template"" is a confusing window title","When adding a template to a page, the window title is ""New template"". This is quite confusing. Some users complained that it sounds like creating a whole new template.
+
+Please consider retitling it to something like ""Add a template"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1408366140,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-kz7ltfye5vll22zw4wk3,task_description,resolved
+"VisualEditor: ""New template"" is a confusing window title","Change 155448 merged by jenkins-bot:
+Re-label inserting mode of transclusion dialog from ""New template"" to ""Add a template""
+
+https://gerrit.wikimedia.org/r/155448",1408586844,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kz7ltfye5vll22zw4wk3,task_subcomment,NA
+"VisualEditor: ""New template"" is a confusing window title","Change 155448 had a related patch set uploaded by Jforrester:
+Re-label inserting mode of transclusion dialog from ""New template"" to ""Add a template""
+
+https://gerrit.wikimedia.org/r/155448",1408571374,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kz7ltfye5vll22zw4wk3,task_subcomment,NA
+Investigate lenient handling of quotes in xml-tag attribute values,"https://en.wikipedia.org/wiki/Dachshund#Coat_and_color has a complex gallery tag:
+
+<gallery widths=""200px"" heights=""200px"" perrow=""5"" caption= ""There are three types of dachshund, which can  be classified by their coats: short-haired, called ""smooth""; long-haired; and wire-haired"">
+File:Wirehaired_Dachshund.jpg|A wire-haired dachshund
+File:Kurzhaardackel.jpg|A short-haired dachshund
+Std Dachshund 600.jpg|A long-haired standard dachshund
+File:Piebald.jpg|A piebald dachshund
+File:Red-merle smooth Dachshund.jpg|A dapple dachshund</gallery>
+
+
+It's being displayed as raw wikitext in VisualEditor on desktop.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66065",1408231860,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-tunsh3had56hubhfkhlt,task_description,duplicate
+Investigate lenient handling of quotes in xml-tag attribute values,"We now have a bunch of tasks that are all about how best to handle broken attribute strings. Parsoid will not always match the PHP parser on this, and this is no longer a high priority task for us. At this point, tt seems reasonable to have these be fixed up in wikitext.",1422920342,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-tunsh3had56hubhfkhlt,task_subcomment,NA
+Investigate lenient handling of quotes in xml-tag attribute values,*** Bug 66065 has been marked as a duplicate of this bug. ***,1408572797,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-tunsh3had56hubhfkhlt,task_subcomment,NA
+Investigate lenient handling of quotes in xml-tag attribute values,"I imagine this is probably not that uncommon since template args and template content may use the same quotes and thus break the html tags. We've seen a few different instances of this bug now. So, maybe worth investigating what it takes to handle this form of broken wikitext a bit more leniently.",1408568812,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-tunsh3had56hubhfkhlt,task_subcomment,NA
+Investigate lenient handling of quotes in xml-tag attribute values,"This is invalid wikitext – you can't use raw "" characters inside the caption of a gallery. Parsoid works just fine if you replace them with ' characters instead:
+
+<gallery widths=""200px"" heights=""200px"" perrow=""5"" caption= ""There are three
+types of dachshund, which can  be classified by their coats: short-haired,
+called 'smooth'; long-haired; and wire-haired"">
+File:Wirehaired_Dachshund.jpg|A wire-haired dachshund
+File:Kurzhaardackel.jpg|A short-haired dachshund
+Std Dachshund 600.jpg|A long-haired standard dachshund
+File:Piebald.jpg|A piebald dachshund
+File:Red-merle smooth Dachshund.jpg|A dapple dachshund</gallery>
+
+I've fixed this in the article, but am moving the bug to Parsoid in case they want to comment/merge into a wider bug about escaping bad wikitext?",1408272080,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tunsh3had56hubhfkhlt,task_subcomment,NA
+"VisualEditor: Keyboard shortcut dialog style differs between standalone and MW, ugly line wraps in MW","The keyboard shortcut styling is substantially different between the standalone demo and the MW integration in terms of font size. In MW, the font size is so much bigger that some shortcuts awkwardly break across lines. For instance, ""Ctrl+Shift+V"" is split with the ""V"" being on a line by itself. In SA, the font size is smaller (for the headings and the shortcuts, but not the descriptions) so this problem doesn't happen, but there the font feels a bit *too* small.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1408173420,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-y3iolseqcvefdxx6knc3,task_description,resolved
+"VisualEditor: Keyboard shortcut dialog style differs between standalone and MW, ugly line wraps in MW","Change 155539 merged by jenkins-bot:
+Define kbd font-family explicity in case environment overrides
+
+https://gerrit.wikimedia.org/r/155539",1408636142,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y3iolseqcvefdxx6knc3,task_subcomment,NA
+"VisualEditor: Keyboard shortcut dialog style differs between standalone and MW, ugly line wraps in MW","Change 155539 had a related patch set uploaded by Esanders:
+Define kbd font-family explicity in case environment overrides
+
+https://gerrit.wikimedia.org/r/155539",1408628545,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y3iolseqcvefdxx6knc3,task_subcomment,NA
+"VisualEditor: Keyboard shortcut dialog style differs between standalone and MW, ugly line wraps in MW","Ed likes fiddling with this dialog, so… :-)",1408272673,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y3iolseqcvefdxx6knc3,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","When I go to ""Enable Hovercards"" to change my settings, it always defaults to ""Read Quickly"", even when I explicitly change it to ""Monitor or Edit"", save, then re-open the dialog to check the setting.
+
+Tested in Firefox/Iceweasel 30.0
+
+--------------------------
+**See Also**: {T71576}",1408052580,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-csz2uil7ibkp5pr2bftr,task_description,invalid
+"When changing Hovercards settings, does not default to my current setting",Thanks @Mattflaschen-WMF. I've updated that page to indicate that Navigation Popups takes precedence when both are enabled.,1470747666,PHID-USER-srhlj2447vmpmrfhqnfa,True,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","No longer applicable.
+
+It's now just Disable/Enable.
+
+There is another issue now (but it may be by design so I'm not filing yet): If you have the Navigation popups enabled, it always takes precedence.  Before, I think there was a way to switch back to Hovercards without explicitly disabling NAVPOP.
+
+This is still documented at https://www.mediawiki.org/wiki/Beta_Features/Hovercards : ""The Hovercards settings panel enables logged-out users to disable it entirely, and enables logged-in users to choose between Hovercards, Navigation popups, or disabling both."", but that might just be a doc bug.",1470700163,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting",@Mattflaschen-WMF I believe the options have changed. Would you please update the task Description as appropriate?,1470341779,PHID-USER-srhlj2447vmpmrfhqnfa,True,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","(In reply to Prateek Saxena from comment #3)
+> I had forgotten why we had added the settings in the first place while we 
+> were having our conversation. After speaking with Nick I remembered that 
+> we'll be making it a default feature (for all logged in and logged out users) 
+> on a few wikis that have shown interest.
+
+It can still be a normal preference on those wikis, defaulted to true.  E.g. VisualEditor has multiple modes, including one where a regular preference is shown, and another where a beta feature is shown.
+
+> Which is why we'll have to keep it the way it is. This pattern is being used 
+> by ReferencePopups too which is a gadget that is enabled by default for all 
+> users.
+
+Gadgets have very different UX considerations, since they can not use normal preferences.
+
+Note, currently (in production) I see both popups (I think this is meant to be fixed by https://gerrit.wikimedia.org/r/#/c/141668/ , not yet deployed) and no ""Disable HoverCards"" link when in ""Read quickly mode"".  This is arguably inconsistent, although you still have another way of disabling it (the gear).",1408583920,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting",I apologize for the confusion. I've been causing too many of them lately.,1408531481,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","(In reply to Matthew in comment #2)
+
+> We also talked about possible parts of the solution, including dropping ""Turn Previews off"" and relying on the standard BetaFeatures UI for disabling beta features.
+
+I had forgotten why we had added the settings in the first place while we were having our conversation. After speaking with Nick I remembered that we'll be making it a default feature (for all logged in and logged out users) on a few wikis that have shown interest. 
+
+Which is why we'll have to keep it the way it is. This pattern is being used by ReferencePopups too which is a gadget that is enabled by default for all users.
+
+
+
+(In reply to Matthew in comment #0)
+
+> When I go to ""Enable Hovercards"" to change my settings, it always defaults to ""Read Quickly""
+
+I think this is justified. The link says ""/Enable/ hovecards"" and not ""Open settings"" so it is correct for it to select that option.",1408531435,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting","This may not make sense to fix in isolation.
+
+Prateek and I talked about some broader areas where the current UI may be confusing.
+
+We also talked about possible parts of the solution, including dropping ""Turn Previews off"" and relying on the standard BetaFeatures UI for disabling beta features.  That then simplifies the internal preferences needed, which opens up possibilities.",1408423647,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+"When changing Hovercards settings, does not default to my current setting",This is tested on English Wikipedia on 1.24wmf16.,1408052991,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-csz2uil7ibkp5pr2bftr,task_subcomment,NA
+VisualEditor: Provide ability to deal easily with dead links,"I met User:Zoony at Wikimania and he said that something which he'd love to see in VE is a way to deal easily with dead (rotten) links.
+He suggested that a right click could launch a menu which provides access to several options, from searching on a search engine in a different tab (to try to fix one) to pasting the {{dead link}} template.
+(More info about ways to deal with dead links at https://en.wikipedia.org/wiki/Wikipedia:Link_rot#Repairing_a_dead_link ).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1408030140,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mjskqwel42qqecgndgvg,task_description,open
+VisualEditor: Provide ability to deal easily with dead links,"We wouldn't use right click for touch compatibility, but links have a complex context area now which we can add too:
+{F2667021,size=full}",1444335666,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-mjskqwel42qqecgndgvg,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Ideas of things to scan for:
+
+* Any request resulting in an error response (404 Not Found, 500 Internal Error, etc.).
+* Uncaught JavaScript exceptions.
+* Network requests made to third-party domains (images, stylesheets, scripts, xhr, etc.)
+
+From comment 13 at {T71445} :
+> However it would be great to have automated tests running after changes in common.js and gadgets. Such general tests can at least validate no external resource is loaded, or no invalid syntax is added.
+> The simplest option is to run it outside MW (such as a script in labs that runs X times a day), but an extension to do it while editing would be even better...
+> 
+> BTW
+> I just runned a simple phantomjs script on all wikipedia languages to catch simple errors:
+> 
+> testing als
+> ERROR: ReferenceError: Can't find variable: ta
+> TRACE:
+> -> https://als.wikipedia.org/w/index.php?title=MediaWiki:If-pt-login.js&action=raw&ctype=text/javascript&dontcountme=s: 9
+> 
+> testing kk
+> ERROR: TypeError: 'null' is not an object (evaluating 'document.getElementById('mw-vector-current-variant').innerHTML=wgULS(""Кирил"",""Latın"",""توتە"")')
+> TRACE:
+> -> https://bits.wikimedia.org/kk.wikipedia.org/load.php?debug=false&lang=kk&modules=site&only=scripts&skin=vector&*: 9
+> 
+> 
+> anyone wants to fix them? :)
+> 
+
+From comment 14 at T71445:
+> Example for errors across wikis
+> Maybe it is a bit off-topic but here are some cases of errors across wikis in simple read/edit transaction using phantomJS
+
+See also:
+* {T71519}
+* {T106770}",1407983460,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_description,resolved
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,Obsoleted by {T226986}.,1691360468,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,:( unfortunately slimerjs is basically dead at this point. I should rewrite it on top of selenium.,1615221757,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"In the meanwhile I noticed that the current Jenkins job cited here is failing for all the wikis:
+
+> ```
+> name=aa.wikibooks.org.log
+> ERROR: aa.wikibooks.org: JSON errorGecko error: it seems /usr/bin/firefox is not compatible with SlimerJS.
+> See Gecko version compatibility. If version is correct, launch slimerjs
+> with --debug=true to see Firefox error message
+> from (https://aa.wikibooks.org/wiki/Main_Page)
+> ```
+>
+> ```
+>name=en.wikipedia.org.log
+>ERROR: en.wikipedia.org: JSON errorGecko error: it seems /usr/bin/firefox is not compatible with SlimerJS.
+>See Gecko version compatibility. If version is correct, launch slimerjs
+>with --debug=true to see Firefox error message
+> from (https://en.wikipedia.org/wiki/Main_Page)
+>```
+> ...
+> https://integration.wikimedia.org/ci/job/audit-resources/lastSuccessfulBuild/artifact/log/",1615214055,PHID-USER-hphk5jxfxfgl64tpfacw,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592584225,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"I think in terms of implementation that's probably good enough.
+
+Does its output go to something we can alert on? And/or does it tell someone/something when it fails?",1590104706,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,So https://integration.wikimedia.org/ci/job/audit-resources/ has been running for 2 years now. What else do we need/want?,1590104473,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,">>! In T71519#4002895, @eranroz wrote:
+> IMO this page is more targeted for extension developers with different skills (git/gerrit/php). I added documentation here: https://www.mediawiki.org/w/index.php?title=Gadget_kitchen&type=revision&diff=2725392&oldid=2718404  I
+> 
+> @Legoktm   - I couldn't find the relevant job in https://integration.wikimedia.org/ci - can you please add a link there (""where??"")
+
+It wasn't actually being run yet...the jenkins job is now https://integration.wikimedia.org/ci/job/audit-resources/ and I just kicked off a test run.",1526269823,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Change 413684 **merged** by jenkins-bot:
+[integration/config@master] Add docker image to run audit-resources
+
+[[https://gerrit.wikimedia.org/r/413684]]",1526267796,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,">>! In T71519#4000631, @Elitre wrote:
+>>>! In T71519#3982243, @eranroz wrote:
+>> Thanks @Legoktm well done and daily jenkins job is good idea to track it regularly. you can mark it as resolved.
+>> 
+>> (and some words to end this phab task from where it started T71445 : we should think how to use this utility as part of community ""code review"" process - so if we can trigger the job on wiki edit in .js files or document it somewhere as part of ""community code review"" process  )
+> 
+> Integrate with https://www.mediawiki.org/wiki/Review_queue? (not sure how official/followed that is.)
+IMO this page is more targeted for extension developers with different skills (git/gerrit/php). I added documentation here: https://www.mediawiki.org/w/index.php?title=Gadget_kitchen&type=revision&diff=2725392&oldid=2718404  I
+
+@Legoktm   - I couldn't find the relevant job in https://integration.wikimedia.org/ci - can you please add a link there (""where??"")
+",1519672148,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,">>! In T71519#3982243, @eranroz wrote:
+> Thanks @Legoktm well done and daily jenkins job is good idea to track it regularly. you can mark it as resolved.
+> 
+> (and some words to end this phab task from where it started T71445 : we should think how to use this utility as part of community ""code review"" process - so if we can trigger the job on wiki edit in .js files or document it somewhere as part of ""community code review"" process  )
+
+Integrate with https://www.mediawiki.org/wiki/Review_queue? (not sure how official/followed that is.)",1519640045,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Change 413684 had a related patch set uploaded (by Legoktm; owner: Legoktm):
+[integration/config@master] Add docker image to run audit-resources
+
+[[https://gerrit.wikimedia.org/r/413684]]",1519374344,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Thanks @Legoktm well done and daily jenkins job is good idea to track it regularly. you can mark it as resolved.
+
+(and some words to end this phab task from where it started T71445 : we should think how to use this utility as part of community ""code review"" process - so if we can trigger the job on wiki edit in .js files or document it somewhere as part of ""community code review"" process  )",1519021658,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"OK, so I opted for the initial solution that was proposed, using phantomjs to go over a bunch of URLs. Except instead of phantomjs, it's using slimerjs which has roughly the same API, but uses Firefox. It currently generates a per-wiki debug log, and then a single ""error"" log that contains any external resource loading violations plus JavaScript errors. I'd like to split those into two logs. We can have jenkins run this daily, and email to lists of people depending on what type of error it is (external resource or JS exception).
+
+Using 8 threads for each wiki's home page on the default skin took about 15 minutes total to run.",1519020999,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Change 412618 **merged** by Legoktm:
+[integration/audit-resources@master] Initial commit
+
+[[https://gerrit.wikimedia.org/r/412618]]",1519020089,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Change 412618 had a related patch set uploaded (by Legoktm; owner: Legoktm):
+[integration/audit-resources@master] Initial commit
+
+[[https://gerrit.wikimedia.org/r/412618]]",1519020038,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"...and mentioning {T106770} here.
+Not sure if that is a hard requirement and should be a dependency (subtask) here though",1500632004,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Replaced ""PhantomJS"" by ""automated browser tests"" in the task summary.
+
+Reading through the comments here and trying to summarize the perfect world:
+* run tests on all Wikimedia sites (gather from sitematrix)
+* run tests on mainpage, editing page etc (via predefined urls), with debug=true
+* allow test to be logged in
+* enable / cover all available gadgets on the site
+* cover MediaWiki:common.js on the site
+* cover skins on the site
+* maybe cover stuff like MediaWiki:Mobile.js or MediaWiki:Minerva.js or MediaWiki:Vector.js ?) on the site
+* cover detecting code that calls 3rd party domains
+I assume there is consensus to run such a test as a Jenkins job?
+
+Also wondering if this could potentially be a Hackathon project. If e.g. legoktm's script can be used as a base.
+
+For the records, aforementioned https://integration.wikimedia.org/ci/view/BrowserTests/view/Core/ and https://integration.wikimedia.org/ci/view/BrowserTests/view/-Dashboard/ are 404s nowadays. No idea if similar things are available on https://integration.wikimedia.org/ci/view/Default/ ...",1493642305,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,">>! In T71519#1567266, @hashar wrote:
+> @krinkle mentioned that PhantomJS is based on a completely outdated Webkit version
+
+Yeah, we're rewriting asset-check on top of Chromium for that reason. Similar to what I did with our QUnit infrastructure in Jenkins. The APIs are similar though, so it's not that much work. See T106770.",1440425911,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,See also {T101497},1440425176,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"@krinkle mentioned that PhantomJS is based on a completely outdated Webkit version that no more reflect the current browsers hitting the sites.  So I guess we can rephrase this task as being a smoke test for the production sites using modern browsers (chromium/firefox).
+
+We have a bunch of browser tests hitting production already ( https://integration.wikimedia.org/ci/view/BrowserTests/view/-Dashboard/ )  and even a test suite for MediaWiki core although it is only hitting beta https://integration.wikimedia.org/ci/view/BrowserTests/view/Core/
+
+
+Potentially we could come up with a set of tests defined somewhere (maybe integration/config) that are a shared responsibility, run continuously and spam everyone whenever something fails.  Will need to describe what kind of smoke tests we are interested to exercise though.
+
+",1440423674,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,Looks like this is more something for Jenkins to run than something that needs production server access...,1440016771,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"The webperf project has an asset-check deamon (see [""Webperf"" on Wikitech](https://wikitech.wikimedia.org/wiki/Webperf#asset-check)) that frequently (every 5 minutes) views a bunch of different endpoints in a PhantomJS browser and collects metrics. We can extend this to cover any metrics needed here.
+
+It currently publishes the metrics to Ganglia only which isn't very accessible. See T105354 for moving this to Graphite so we can build a dashboard for it and just in general to allow people to query the data more easily.
+
+See the [checkAssets() in webperf/asset-check.js](https://github.com/wikimedia/operations-puppet/blob/4ba5e62018ede8929025fb7a2a156c76527860e1/modules/webperf/files/asset-check.js#L61-L97) for an overview of the data currently collected.",1480981511,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"The webperf project has an asset-check deamon (see [""Webperf"" on Wikitech](https://wikitech.wikimedia.org/wiki/Webperf#asset-check)) that frequently (every 5 minutes) views a bunch of different endpoints in a PhantomJS browser and collects metrics. We can extend this to cover any metrics needed here.
+
+It currently publishes the metrics to Graphite only which isn't very accessible. See T105354 for moving this to Graphite so we can build a dashboard for it and just in general to allow people to query the data more easily.
+
+See the [checkAssets() in webperf/asset-check.js](https://github.com/wikimedia/operations-puppet/blob/4ba5e62018ede8929025fb7a2a156c76527860e1/modules/webperf/files/asset-check.js#L61-L97) for an overview of the data currently collected.",1436458429,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"There's also the VE production browser test that ensures that all wikis with VisualEditor installed actually let you get to VE successfully:
+
+https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-production-linux-firefox-sauce/
+
+(The fy.wikipedia.org one is just a regular test suite failure; the kk.wikipedia.org one looks like a local sysop has broken JS there.)",1408096409,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"Seems we have two versions :-]  If you guys could unify the effort and have the resulting code hosted in Gerrit, I would be more than happy to write a Jenkins job that runs the script  once per hour and spam some place (mail/IRC...).",1408018640,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"here is my version used for error checking:
+https://github.com/eranroz/wiki-js-error-log/blob/master/testwiki.js",1407988684,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"(In reply to MZMcBride from comment #0)
+> ...
+> testing als
+> ERROR: ReferenceError: Can't find variable: ta
+> TRACE:
+>  ->
+> https://als.wikipedia.org/w/index.php?title=MediaWiki:If-pt-login.
+> js&action=raw&ctype=text/javascript&dontcountme=s: 9
+> ...
+FIXED:
+https://als.wikipedia.org/wiki/MediaWiki:If-pt-login.js?diff=584752",1407984199,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"<http://tools.wmflabs.org/legobot/wmf_js_scanner.js> checks for any JS errors being thrown on the main page (as an anonymous user) as well as the inclusion of any external resources.
+
+Ideally such a tool would be able to login, visit a few pages (including ?action=edit), enable and disable individual gadgets and change skins.",1407983853,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript,"The idea here is to use a tool such as PhantomJS (a headless WebKit browser) to hit a bunch of pre-defined URLs and report JavaScript errors.
+
+In addition to strictly checking errors, checking fetches of content on domains outside of Wikimedia's control (e.g., Google Analytics) would also be nice.",1407983729,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-xk6dzyzmisj4aabwvaxm,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","Scan down these to find lots of garbage, including lines like:
+
+</xml><![endif]--><!--[if gte mso 9]><xml>
+
+or 
+
+<!--[if gte mso 9]><xml>
+
+https://fr.wikipedia.org/w/index.php?title=Catherine_Lemorton&curid=1711917&diff=105874955&oldid=105753648
+
+
+https://fr.wikipedia.org/w/index.php?title=Paul_C%C3%A8re&curid=8199909&diff=106116894&oldid=106116223
+
+https://fr.wikipedia.org/w/index.php?title=Paul_C%C3%A8re&curid=8199909&diff=106116209&oldid=106116068 
+
+https://fr.wikipedia.org/w/index.php?title=Andr%C3%A9_Grassi&curid=5857691&diff=106069630&oldid=105919440 
+
+https://fr.wikipedia.org/w/index.php?title=Capitulaire_de_Coulaines&curid=1578466&diff=106053129&oldid=90262123 
+
+https://fr.wikipedia.org/w/index.php?title=Charles_Ateba_Eyene&curid=7794227&diff=105959949&oldid=105470353
+
+
+This may be helpful in finding others:
+
+https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Modifications_r%C3%A9centes&days=30&from=&tagfilter=balise+HTML+interdite
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69821
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61371",1407974760,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ydyactq6zkhdtz4zvqql,task_description,resolved
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","This now looks to be fixed; I pasted the contents of a couple of the diffs show above into the HTML clipboard, and then back out into VisualEditor (simulating a copy from Microsoft Office), and the unwanted cruft was all magically removed.",1427402940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)",The comments were dealt with in T71821,1417005560,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)",Maybe Outlook is kind of part of Microsoft Office nowadays anyway. :),1408802811,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","Isn't mso Microsoft Office, rather than Outlook?",1408752973,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","(In reply to Alex Monk from comment #1)
+> People copying in things from MS Word, it seems:
+> http://www.equalserving.com/what-the-heck-is-msonormaltable-and-how-did-it-
+> get-in-my-post/
+
+Yes, probably, but this problem is new in VE: the first occurrence I've been able to find in frwiki is in August 1st. Nothing previously.",1408447733,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+"VisualEditor: Copying from Microsoft Word adds XML cruft like "" <w:WordDocument>
+"" (mso = Microsoft Office)","People copying in things from MS Word, it seems: http://www.equalserving.com/what-the-heck-is-msonormaltable-and-how-did-it-get-in-my-post/",1408046482,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ydyactq6zkhdtz4zvqql,task_subcomment,NA
+VisualEditor:  Page options icon is confusing,"From John Broughton:
+
+It would be easier to remember what this menu does, and to tell others about it (say, in the User Guide) if the icon for it were the text “Page” (with a down-arrow) rather than three horizontal lines. This menu icon approach is used for the “Insert” and “Cite” menus, which helps users immediately understand (and/or remember) what type of items are on the menu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407972420,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gho3zvnxqkwy4kgvoeo4,task_description,declined
+VisualEditor:  Page options icon is confusing,"Prateek, I don't remember seeing any complaints about this for a long while.  Maybe people are used to it now?",1515105150,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gho3zvnxqkwy4kgvoeo4,task_subcomment,NA
+VisualEditor:  Page options icon is confusing,With {T177432} progressing this should get resolved as we're using an article icon with settings cog.,1514960744,PHID-USER-caadsxn4xg5gmxrpn6kz,True,PHID-TASK-gho3zvnxqkwy4kgvoeo4,task_subcomment,NA
+VisualEditor:  Page options icon is confusing,"//Page options// is a vague thing and so gets a vague icon {icon frown-o}. We could use the typical {icon cog} or {icon cogs} but that might get confused as settings for the editor itself. The same might be true for {icon sliders} too, plus we're using both those icons for items within the menu.
+
+Other options might be {icon wrench}, {icon tachometer} or {icon file-o}.
+
+***
+
+@Whatamidoing-WMF, the {icon bars} icon while confusing has become quite popular as a //more options// icon, do you still find it difficult while communicating to users?",1504791222,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-gho3zvnxqkwy4kgvoeo4,task_subcomment,NA
+Enable Visual Editor for Math by default,"**Author:** `physik`
+
+**Description:**
+I'm using the vagrant role visual-editor for my wiki.
+After enabling the visual editor role I could not edit formulae... The message is available in source mode only.
+I see that the visual editor for math is not super fancy now, but it should be somehow stable?
+If not this can become a tracking bug to trace of the bugs that need to be resolved.
+
+--------------------------
+**Version**: master
+**Severity**: minor",1407933840,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5kt2ttqsqdttw35wyuft,task_description,invalid
+Enable Visual Editor for Math by default,"**physik** wrote:
+
+I think my version is not very old...
+/vagrant/mediawiki/extensions/VisualEditor$ git log -1
+commit f5681d490016a8c3213bbdceae859d784dbb5359
+Author: Translation updater bot <l10n-bot@translatewiki.net>
+Date:   Tue Aug 12 21:40:40 2014 +0200
+
+    Localisation updates from https://translatewiki.net.
+
+    Change-Id: I8e86d5dcaa3204893733734acf1439414656fc0f
+I'm not aware of any configuration option that disables VE-support in the Math extension.",1407944696,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5kt2ttqsqdttw35wyuft,task_subcomment,NA
+Enable Visual Editor for Math by default,"Umm. This was done in gerrit I0dd1c85a four months ago… are you running very very old code, or have you got the Maths extension configured in a way that breaks the VisualEditor plugin?",1407941455,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5kt2ttqsqdttw35wyuft,task_subcomment,NA
+Enable Visual Editor for Math by default,"**physik** wrote:
+
+Visual editor for math disabled
+
+**Attached**: {F14708}",1407934224,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5kt2ttqsqdttw35wyuft,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"**Author:** `ronnirubin`
+
+**Description:**
+Re bug 68101
+
+> Load VE. Say ""Foobar"" is the first word on the page.
+> If you click on the link tool, by mistake or not, without selecting anything before, Foobar will automatically become a link to the Foobar page (it doesn't help that pressing ESC doesn't abort the action, the link gets applied anyway, as we know).
+
+ESC _should not_ exit and save; it should either exit without saving, or revert the change (in this case, the link) without exiting.  I was going to set the Severity to ""blocker"", as it would block installation on en.Wikipedia, but that would be wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407776940,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ufpvladvj4hbtquskrvo,task_description,resolved
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,This was fixed a while ago.,1561738917,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"Yeah, that's {T52868}.",1454692497,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"Not sure if I'm adding further confusion :) 
+(and I think this task didn't keep T101176 into account?)
+but from what I'm reading at the German Wikipedia,
+some would find it desirable that ESC allowed to leave the ""blue"" link area after a link is added and placed the cursor just at the right so that people can quickly start typing again.
+
+Currently, hitting ESC right after choosing a link target doesn't close the link tool - it prompts the ""Are you sure?"" dialog to leave the page entirely.
+Also, to get out of the blue area just via the keyboard, you need to hit the right arrow twice (which doesn't seem much intuitive).",1454528383,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"Unfortunately I agree with BOTH of you. 
+I am often confused by the behaviour of the link dialogue and am often looking for the ""insert"" or ""confirm"" button. ""Done"" doesn't seem right to me somehow. 
+On the other hand, James is right too. The behaviour of all the formatting icons on the toolbar is that as soon you press them, the action takes place. So, highlighting a word and pressing ""bold"" will cause the text to go bold immediately, not after a second 'confirmation click'. 
+Nevertheless, despite intellectually understanding the link dialogue design, I keep stumbling on it - it gets in the way and I have to consciously think about it - which is not good behaviour for a labor-saving device.",1410168235,PHID-USER-b653jige5ek3oq53yron,False,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+VisualEditor: Consider whether exiting the link dialog in create mode should remove the link,"This is a mistaken understanding of what the button does, and what the window is for.
+
+* The link button *creates* a link if there is none there already.
+* Once the link is created, we then also pop up a link editing window 
+* This is to let you change the link to point to a different place, or remove it.
+* Pressing escape closes the editing window, leaving you with the link you created.
+
+This is intentional design. Escape isn't ""applying"" anything, but it's probably not very clear. Maybe design would like to comment?",1409670135,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ufpvladvj4hbtquskrvo,task_subcomment,NA
+Highlight that you can incrementally adjust the edit summary,"When editing in VisualEditor, you can click ""save"", add some text to the edit summary, click ""resume editing"", edit some more, and repeat. This kind of incremental summary is a fairly common request from editors who add to the summary field when they make each successive change in an edit. 
+
+So we actually have the capability they're requesting, but it's not well designed for this use case
+",1407758940,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-jy7hdkzqail6eg6yzt7t,task_description,open
+Highlight that you can incrementally adjust the edit summary,See also (merge one into other?) {T52961},1432250894,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-jy7hdkzqail6eg6yzt7t,task_subcomment,NA
+Highlight that you can incrementally adjust the edit summary,"Actually, I didn't realise you could do that which makes this much less of a problem that I thought it was.  Still, it's a bit clunky. I can't, for instance, start writing the edit summary first (I have to edit something first to make the save button go live).  There are many situations where one has ""dirty"" data on the clipboard carried from somewhere else and intended for the edit summary.  Have to remember not to copy-paste anything else before dumping it in the edit summary field.",1407786922,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-jy7hdkzqail6eg6yzt7t,task_subcomment,NA
+Highlight that you can incrementally adjust the edit summary,"I believe that what SpinningSpark is actually requesting is to have the edit summary visible and editable on the main screen.  Right now, you can fill out the edit summary incrementally, but you have to click on the Save button and then cancel saving each time.",1407781480,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-jy7hdkzqail6eg6yzt7t,task_subcomment,NA
+VisualEditor: Find a way to make the link button is more discoverable,"**Author:** `che`
+
+**Description:**
+Yesterday I tried VisualEditor for the first time, after nine years of editing wikitext. I took me several minutes to find out how to make a link. I have tried text styles drop-down (as it has an underlined letter, which I associated with hyperlinks), the the ""insert"" drop-down, which included several useful objects, but not the hyperlink option. I have tried typing ""[["", which has shown me a warning that wiki syntax does not work, but did not tell how to create a link in VisualEditor. Then I went through citation and list-formatting menus, before finally stumbling onto the link button, which is sort of grey, and the only button in the line that has no drop-down arrow. In retrospect, I guess I though it is some kind of separator.
+
+Some things that might have made my life easier:
+- a bit more obvious link button
+- having another link option in ""insert"" menu (with the same icon, so I could discover it on the toolbar afterwards)
+- having mr. Clippy's ""It looks like you're attempting to use wikitext"" message point me to the VisualEditor equivalent of what I'm trying to do (by showing the icon or highlighting the button on toolbar)
+
+Alternatively, interpreting wikitext in VisualEditor might make life easier for users experienced with it's syntax, but that might be a stupid idea.
+
+In any way, thank you for your work on VisualEditor. You're pushing as all forward towards a better future :-)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407676140,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7loco2tyuhwahwjzohkg,task_description,declined
+VisualEditor: Find a way to make the link button is more discoverable,"The link button is prominent enough. I do not agree that making it more prominent would be a good idea.
+
+Also, since this bug was filed, typing `[[` does now open the link dialogue.",1519404429,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-7loco2tyuhwahwjzohkg,task_subcomment,NA
+VisualEditor: Find a way to make the link button is more discoverable,"The current link button is very similar to what is used in Google Docs and Gmail. It also has the same keyboard shortcut - Ctrl-K.
+
+Adding a button to the insert menu is not bad, but may increase clutter unnecessarily.
+
+Interpreting wikitext such as identifying that the editor is typing [[ would be nice DWIM for a lot of people, but unnecessary for others. I wouldn't make it a priority.",1408350501,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-7loco2tyuhwahwjzohkg,task_subcomment,NA
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode","For example, if you open the link tool on a blank page, there is nothing to ""Remove"" and nothing to ""Open"", so those buttons should be grayed out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407652020,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ym3q5jy7edmc533tzdy5,task_description,resolved
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode","(In reply to Alex Monk from comment #3)
+> Maybe relabel it ""Cancel"" instead in this case?
+
+Maybe.",1416255867,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ym3q5jy7edmc533tzdy5,task_subcomment,NA
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode","Maybe relabel it ""Cancel"" instead in this case?",1416183190,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ym3q5jy7edmc533tzdy5,task_subcomment,NA
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode","(In reply to WhatamIdoing from comment #0)
+> For example, if you open the link tool on a blank page, there is nothing to
+> ""Remove"" and nothing to ""Open"", so those buttons should be grayed out.
+
+1. Click into a blank spot (e.g. the cursor is at '|' in ""Foo | Bar"")
+2. Enter a search term and select a link target
+
+At this point, the only way to not insert this link is to click ""Remove""; disabling it would mean that to not insert the link, you would have to empty the search box and then click ""Done"" (confusing) or outside the inspector (not possible in mobile).
+
+Maybe we could come up with a different label, or maybe we don't care about this edge case enough?",1414086706,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ym3q5jy7edmc533tzdy5,task_subcomment,NA
+"VisualEditor: Label the ""Remove"" button in link inspector as ""Cancel"" if in link creation mode",Open button was bug 70015,1414083209,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ym3q5jy7edmc533tzdy5,task_subcomment,NA
+"VisualEditor:Text style drop-down overridden by edit comment, in Monobook skin.","screenshot
+
+environment- test2
+
+1> open page in VE, insert a comment.
+2> Click to edit the comment.
+3> Now click on the Text Style Menu, notice the  text style drop-down opens with edit comment dialog overriding it . Please see screenshot.
+
+Only on Monobook skin, same issue found in FF.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14206}",1407445440,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-fvmxjg6y2457g7m277ut,task_description,resolved
+"VisualEditor:Text style drop-down overridden by edit comment, in Monobook skin.",Issue Resolved on test2.,1409668410,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-fvmxjg6y2457g7m277ut,task_subcomment,NA
+"VisualEditor:Text style drop-down overridden by edit comment, in Monobook skin.",Think that this may have been fixed by gerrit 156723.,1409247899,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fvmxjg6y2457g7m277ut,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"screenshot
+
+1> Open a page in VE, the skin is Monobook.
+2> Insert a link.
+3>While the link icon is visible, move the cursor to the beginning of the link. The link icon looks broken. See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows XP
+
+**Attached**: {F14152}",1407422460,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-cid7l2qphwhjkog4ga2f,task_description,resolved
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,Issue not fixed on test2.,1410182118,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"(In reply to Ritu Swain from comment #6)
+> Issue not fixed on test2.
+
+Yes, this code will be deployed to test2 on 2014-09-04 so for now it will still be broken, sorry.",1409669028,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,Issue not fixed on test2.,1409668630,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,Think that this may have been fixed by gerrit 156723.,1409247941,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,[editing bug summary],1407493009,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"(In reply to Andre Klapper from comment #2)
+> What does ""is broken"" or ""look broken"" mean exactly here?
+
+As the cursor moves on the link,the tip (""^"") of the link icon moves along.But when you move it to the first character of the link, the tip(""^""), it appears not to be part of the link icon anymore . Please see attached screenshot.",1407442326,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"What does ""is broken"" or ""look broken"" mean exactly here?",1407425757,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line,"Similar behavior found with the other icons as well, like - Comment,Language.",1407422917,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-cid7l2qphwhjkog4ga2f,task_subcomment,NA
+VE's beta help adds a question mark to 'Switch to source editing',"VE's help icon popup includes this ""visualeditor-beta-warning"" text:
+
+... To switch back to source editing at any time without losing your changes, open the dropdown next to ""Cancel"" and select ""Switch to source editing?"".""
+
+The last message is 'visualeditor-mweditmodesource-title'.  But the item in the dropdown is actually visualeditor-mweditmodesource-tool, which is ""Switch to source editing"" without a question mark. Trivial to fix.
+
+(Also ""Cancel"" is gone from the VE UI, I filed bug 69201.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1407357360,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-h725ojkqatxs3kupeh7s,task_description,resolved
+VE's beta help adds a question mark to 'Switch to source editing',"Change 152913 merged by jenkins-bot:
+Fix use of visualeditor-mweditmodesource-title instead of …-tool
+
+https://gerrit.wikimedia.org/r/152913",1407959178,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h725ojkqatxs3kupeh7s,task_subcomment,NA
+VE's beta help adds a question mark to 'Switch to source editing',"Change 152913 had a related patch set uploaded by Jforrester:
+Fix use of visualeditor-mweditmodesource-title instead of …-tool
+
+https://gerrit.wikimedia.org/r/152913",1407508641,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h725ojkqatxs3kupeh7s,task_subcomment,NA
+Add a proper way in MobileFrontend to load custom editors,"Currently the MobileFrontend provides two editors : one using wikitext and one based on the VisualEditor. It would be nice to have a proper editor loader in order to allow to the creation of customized editors by other extensions (an use case may be an editor for Wikisource Page: pages).
+
+**See Also**:
+* {T67165}",1407330780,PHID-USER-5paybpgtxjrhikdos3p5,False,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_description,stalled
+Add a proper way in MobileFrontend to load custom editors,"This already exists.
+
+You can use the hook 'SkinMinervaDefaultModules'
+
+Inside the hook you can replace the editing module with your own module.
+
+e.g.
+
+$modules['editor'] = array( 'mycustomeditor' )
+
+Can you try this and see if it works for you?",1410913173,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_subcomment,NA
+Add a proper way in MobileFrontend to load custom editors,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/1GD5dpRW",1408025121,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_subcomment,NA
+Add a proper way in MobileFrontend to load custom editors,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/pWbLQ2ga",1407417610,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_subcomment,NA
+Add a proper way in MobileFrontend to load custom editors,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/3iclM3PZ",1407330909,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fb2f5khj7vp3u2bzxxv6,task_subcomment,NA
+VisualEditor: ResourcesTest::testUnsatisfiableDependencies: The module 'mobile.editor.ve' must not have target 'desktop',"With attachment 16112:
+
+119) ResourcesTest::testUnsatisfiableDependencies
+The module 'mobile.editor.ve' must not have target 'desktop' because its dependency 'ext.visualEditor.mobileViewTarget' does not have it
+Failed asserting that an array contains 'desktop'.
+
+/srv/vagrant/mediawiki/tests/phpunit/structure/ResourcesTest.php:98
+/srv/vagrant/mediawiki/tests/phpunit/MediaWikiTestCase.php:133
+/srv/vagrant/mediawiki/tests/phpunit/MediaWikiPHPUnitCommand.php:42
+/srv/vagrant/mediawiki/tests/phpunit/phpunit.php:160
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406848200,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-d3rxpccf3znjcbyhsazz,task_description,resolved
+VisualEditor: ResourcesTest::testUnsatisfiableDependencies: The module 'mobile.editor.ve' must not have target 'desktop',Not re-encountered in over a year.,1438385391,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d3rxpccf3znjcbyhsazz,task_subcomment,NA
+VisualEditor: ResourcesTest::testUnsatisfiableDependencies: The module 'mobile.editor.ve' must not have target 'desktop',Hmm. mobile.editor.ve is defined in MobileFrontend but without a mobile target (!?)… How does mobile.editor.ve get used in mobile?,1406908192,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d3rxpccf3znjcbyhsazz,task_subcomment,NA
+VisualEditor: dm.Document seems to not get the right lang and dir settings inside the Media Dialog in insert mode,"… so instead it falls back to the built-in defaults (en and ltr), but really it shouldn't ever get to this position.",1406764980,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7upi3shakwholt2fwmgg,task_description,open
+VisualEditor: dm.Document seems to not get the right lang and dir settings inside the Media Dialog in insert mode,Is this now fixed?,1449024310,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7upi3shakwholt2fwmgg,task_subcomment,NA
+VisualEditor: Metas at the end of a link annotation's anchor cause it to be split; should instead change with it,"(Taken from bug 52127.)
+
+Previously, before comments were node-ified, editing
+
+  [[Foo|Bar<!--Foo!-->]]
+
+… to point to ""Baz"" would create the wikitext:
+
+  [[Baz|Bar]][[Foo|<!--Foo!-->]]
+
+… whereas it should have done
+
+  [[Baz|Bar<!--Foo!-->]]
+
+… (i.e., meta items inside annotations should get changed when the annotation changes, not keep their existing ones).
+
+
+As comments are (mostly) now nodes, this doesn't apply to them, but will apply to other meta items like {{DISPLAYTITLE:Foo}} or whatever broken items might exist.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406598120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lfafbeovak6pyjwejllz,task_description,resolved
+VisualEditor: Metas at the end of a link annotation's anchor cause it to be split; should instead change with it,"So, it turns out we fixed this at some point in the past ~3 years anyway – tested on 1.31.0-wmf.17:
+
+https://www.mediawiki.org/w/index.php?title=User:Jdforrester_(WMF)/T70779&diff=2703642&oldid=2703641
+
+However, it still works after the re-unification of data and meta-data, tested on 0c9fb65fbe:
+
+https://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Jdforrester_(WMF)/T70779&diff=375632&oldid=375631
+
+… hurrah?",1517251219,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lfafbeovak6pyjwejllz,task_subcomment,NA
+VisualEditor: Reconsider template tool tabbing behaviour to go to the next field (not the info or remove buttons),"This is possibly by design, but I found it unexpected:
+
+Use the Cite tool with any example having multiple fields to fill in, e.g. Website or Book.
+
+Enter a field. Hit TAB.
+
+I would expect the cursor to go to the next editable field, but instead the cursor highlights first the Field description icon, then the Remove field icon, and only after that moves to the next editable field.  The user must tab three times to put the cursor into the next editable field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406581620,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-63upowwh7qb6xl3mg3rx,task_description,declined
+VisualEditor: Reconsider template tool tabbing behaviour to go to the next field (not the info or remove buttons),">>! In T70768#720791, @Jdforrester-WMF wrote:
+> Yeah, this is intentional
+
+Specifically, we did it in response to T67474.
+",1431983918,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-63upowwh7qb6xl3mg3rx,task_subcomment,NA
+VisualEditor: Reconsider template tool tabbing behaviour to go to the next field (not the info or remove buttons),*** Bug 69512 has been marked as a duplicate of this bug. ***,1414084060,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-63upowwh7qb6xl3mg3rx,task_subcomment,NA
+VisualEditor: Reconsider template tool tabbing behaviour to go to the next field (not the info or remove buttons),"Yeah, this is intentional, but maybe we should look again in case there is a way to provide the accessibility we need without being unhelpful to keyboard users.",1406582743,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-63upowwh7qb6xl3mg3rx,task_subcomment,NA
+VisualEditor: Increase indentation is not working when the list is wrapped around a left aligned image,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+4.Add a numbered list or bullet list after that
+5.Make the image left aligned 
+6.When the list gets wrapped on the right side of the image,place the cursor on one item in the list
+7.Try increasing the indentation
+
+Observed Result:
+Nothing happens.No indentation is added to the listed item.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406243820,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6k4njahaswdgisg5ovok,task_description,duplicate
+"VisualEditor: Reconsider the ""Insert"" menu because it doesn't always insert","Use case:
+
+1. On a page with a heading and some text. Put cursor at start of the paragraph after the heading.
+2. Insert a template (ends up selecting it after finishing insertion)
+3. ""Insert"" another template.
+
+Expected:
+
+A dialog should appear with the ability to decide which template to insert etc.
+
+Actual:
+
+A dialog appears to edit the selected transclusion that is already on the page.
+
+
+After being genuinely confused for a minute I realised that the confusion came from the menu label being ""Insert"". A while back, the ""Template"" button was separate on the toolbar (or under ""More"" or ""Tools"" whatever it was). Back then, like still the case with Links and Text Style, it was more natural to assume it will edit and not create a template when a template is selected already because the button would be rendered in an ""active"" (pressed-down) state (like for links and text style). However, the menu was then relabelled to ""Insert"" and the items in the ""Insert"" menu do not have an ""active"" state to help correlate with the currently selected item on the page.
+
+Perhaps we should bring back the ""active"" state for the Insert menu items, for consistency with other buttons on the toolbar.
+
+Or make it actually insert a new one at/before the current cursor position, which would mean that to edit a transclusion users then need to use the context menu instead.",1406168400,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-53ehcwcdlxysbyk5zh6q,task_description,open
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor","Might be related to bug 68492.
+
+> Discontiguous selection is not supported. rangy-core-1.3.js:2842
+>> (anonymous function) rangy-core-1.3.js:2842
+>> (anonymous function) rangy-core-1.3.js:2852
+>> (anonymous function) rangy-core-1.3.js:327
+>> init rangy-core-1.3.js:249
+>> loadHandler rangy-core-1.3.js:365
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1406167740,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-el77qq7juolzlky357jd,task_description,resolved
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor",*** Bug 69616 has been marked as a duplicate of this bug. ***,1412803537,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-el77qq7juolzlky357jd,task_subcomment,NA
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor",Fixed now because we don't use Rangy any more.,1412591488,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-el77qq7juolzlky357jd,task_subcomment,NA
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor","**timdown** wrote:
+
+It's coming from a perfectly reasonable feature test in Rangy that is upsetting non-standard behaviour in Chrome. I've reluctantly put in a hideous browser sniff to work around it in the latest Rangy release.",1406934521,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-el77qq7juolzlky357jd,task_subcomment,NA
+"VisualEditor: Chrome 36 and higher throws ""Discontiguous selection is not supported"" on opening the editor",*** Bug 68771 has been marked as a duplicate of this bug. ***,1406584229,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-el77qq7juolzlky357jd,task_subcomment,NA
+VisualEditor: Don't use Range.detach (is now a no-op in Chrome per revised DOM spec),"Chrome emits this notice when using VisualEditor anywhere.
+
+> 'Range.detach' is now a no-op, as per DOM (http://dom.spec.whatwg.org/#dom-range-detach).
+
+
+Looks like more than the typical deprecation, because it's been replaced with a no-op. No idea if we/Rangy are relying on it doing something. Could cause all kinds of weird state inconsistencies.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1406167560,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cj3vl62yqcs5xpvo2hyk,task_description,resolved
+VisualEditor: Don't use Range.detach (is now a no-op in Chrome per revised DOM spec),"As we've now dumped Rangy, this is now FIXED.",1410404341,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cj3vl62yqcs5xpvo2hyk,task_subcomment,NA
+VisualEditor: Don't use Range.detach (is now a no-op in Chrome per revised DOM spec),"(In reply to Tim Down from comment #1)
+> Rangy has no reliance on Range.detach now. The latest release does not use
+> it at all.
+Unfortunately we still use the Rangy position plugin, which appears to have been unmaintained for a while. So we're stuck with our current version of rangy for now. Ideally I would like us to migrate away from the position plugin, then to a more recent version of Rangy. But I need to do a code audit to see is being used where.",1406935989,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cj3vl62yqcs5xpvo2hyk,task_subcomment,NA
+VisualEditor: Don't use Range.detach (is now a no-op in Chrome per revised DOM spec),"**timdown** wrote:
+
+Rangy has no reliance on Range.detach now. The latest release does not use it at all.",1406934562,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-cj3vl62yqcs5xpvo2hyk,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,"Environment- Betalabs
+
+Steps to Reproduce-
+
+For Chrome-
+1> Logged in and trying to switch to VE interface by clicking on ""Edit beta"" tab shows the spinner for a while and remains in the read mode.
+2> Now click on ""Edit Source"" tab opens the Wikieditor interface.
+3> Click on ""Edit beta"" tab again, takes you to the Read only mode instead.
+
+For FF-
+1>Logged in and trying to switch to VE interface by clicking on ""Edit beta"" tab shows the pop-up with message ""Error loading data from server: readonly: The wiki is currently in read-only mode. Would you like to retry?"", with the spinner in the background forever.
+
+For Safari-
+1>Logged in and trying to switch to VE interface by clicking on ""Edit beta"" tab shows the pop-up with message ""Error loading data from server: readonly: The wiki is currently in read-only mode. Would you like to retry?""
+
+This issue is related to Bug 59010 and Bug 60765.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1406041440,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-jaospgjrwtyxcof7isza,task_description,open
+VisualEditor: Consider changing behaviour on launch when the database is locked,See also T53547,1542651968,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,See also T111217,1542651858,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,"When trying to save wikitext during a DB lock, you can just copy-paste your wikitext, save it to a text file, and paste it back when the wiki comes up again later on. I guess with VE you can still do that by using ""switch to wikitext"", but it's not nearly as obvious.",1406118852,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,"By the way, bug 68349 is tracking the issue which has turned on read-only mode. This bug can be used to look into how VE is handling it poorly and/or inconsistently.",1406052764,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,I think they mean that they can't open VE on any *.beta.wmflabs.org wiki. Those are part of the deployment-prep project in labs. The database there are read-only at the moment: no edits can be made.,1406048177,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+VisualEditor: Consider changing behaviour on launch when the database is locked,"Where exactly is ""in betalabs""? All instances there or which one(s)?",1406047537,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jaospgjrwtyxcof7isza,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Without making any change , go to page options next to ""Save Page"" button
+3.Select the option ""Switch to source editing""
+
+Observed Result:
+The confirmation dialog to keep ot discard changes appears.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14213}",1405710600,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_description,resolved
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears",Verified the fix in production,1407188752,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears",Verified the fix in test2,1406324839,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears",Verified the fix in Betalabs,1406160327,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears","Change 147646 merged by jenkins-bot:
+Don't confirm if there's no changes when switching to edit source mode through the page options menu
+
+https://gerrit.wikimedia.org/r/147646",1406075190,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+"VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears","Change 147646 had a related patch set uploaded by Alex Monk:
+Don't confirm if there's no changes when switching to edit source mode through the page options menu
+
+https://gerrit.wikimedia.org/r/147646",1405715505,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-q4wvmsyfsol7m35pdvvw,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Open link inspector
+3.Type something in the text field to bring up the suggestions
+4.Select one suggestion from the drop down
+5.Place the cursor at the end of the link target name in the field
+6.Press backspace to delete it
+
+Observed Result:
+Instead of deleting the link target , it takes user to the CE closing the inspector.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1405635060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_description,resolved
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"Seems to work for me now. Tested on Beta Cluster using iOS Safari 8.0 on an iPad.
+",1434487702,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Needs re-testing.,1430336168,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Can't reproduce this issue. Is it Safari-only?,1429567863,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"(In reply to Alex Monk from comment #7)
+> Can't reproduce...
+
+Can reproduce here.",1415220540,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Can't reproduce...,1415067744,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"Yeah, I sat down with Maryana and showed her how to reproduce it.",1407967453,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"I am still getting it following the exact same steps on Betalabs ,test2 and en.wiki. Infact, Roan and I reproduced it several times last week on master.",1407967354,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,"I just tested this out, and I'm not seeing any issues with backspacing text in link inspector on test2 or mediawiki.org on an iPad 2 – did it get fixed somehow?",1407965137,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Double tapping on backspace takes to a blank page,1407183602,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,This is still happening in Betalabs,1406930911,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector,Fixed.,1406747579,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ykvk2t5okmz64pbkm7sn,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","This was mentioned on the ""[QA] Failing MobileFrontend browser tests"" thread in July. I have seen a few more  ""getaddrinfo: Name or service not known (SocketError)"" errors with Flow browser tests, and then today we got four of them. :-(
+
+See https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/65/
+
+All three tests failures in https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/65/ at Jul 16, 2014 6:26:46 PM (UTC?) were with this error.
+
+15 minutes earlier, https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/72/ also failed with ""getaddrinfo: Name or service not known (SocketError)"". The other test failure was an action that took longer than 5 seconds to complete.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1405546200,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-szhiff6d7luj5xmsrczv,task_description,invalid
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","As far as I can see, this is no longer a problem. The last Flow build has 17 failed scenarios, but all of them are `timed out after 5 seconds, waiting for ... to become present (Watir::Wait::TimeoutError)`
+
+https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/590/consoleFull
+
+Closing this as invalid. Please reopen if the problem is still reproducible.",1427725948,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","(In reply to Chris McMahon from comment #3)
+> This is very likely fixed with
+
+""fixed with what"" ? HHVM improvements?
+
+Anyway, this remains a problem. From e-mail to qa mailing list:
+>>>
+Echo and Flow tests were all green Saturday Sept 6 for the first time \o/
+
+But then 4 out of 6 Flow test runs today (
+  Sep 7, 2014 8:33:11 PM
+  Sep 7, 2014 6:51:45 PM    
+  Sep 7, 2014 6:13:05 PM
+  Sep 7, 2014 3:54:07 AM
+UTC times I think)
+<<<
+Tthere was another getaddrinfo failure Sep 8, 2014 3:45:56 AM, see 
+<https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/185/>",1410159268,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","
+This is very likely fixed with",1406300559,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""","Seems to be a 90 second timeout for a Flow job as well, but without the big red error message at the top of the Sauce page: https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/72/testReport/junit/(root)/Topic%20collapsing/Topics_only_view/",1405546521,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+"browser tests failing with ""getaddrinfo: Name or service not known (SocketError)""",In at least one case this was caused by SauceLabs not receiving any command for 90 seconds: https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/lastCompletedBuild/testReport/(root)/VisualEditor%20general%20text%20markup%20features/VisualEditor_general_markup__outline_example_____Superscript____sup_General_Markup_VisualEditor_Test__sup____/,1405546411,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-szhiff6d7luj5xmsrczv,task_subcomment,NA
+VisualEditor: there is no way to change the template name without re-filling all the params,"There are templates that have a different name, but the same parameters. For example, the many lang-XX templates. If I see that the parameter text is correct, but an incorrect template was used, and the template should be {{lang-ru}} and not {{lang-be}}, I can simply change the template name. In VE I need to delete the whole template and re-add it. This is silly, but tolerable, for a template with one parameter, but there are such templates with more parameters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1405488660,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-jbzu5w4c3nerq2feaawm,task_description,open
+VisualEditor: there is no way to change the template name without re-filling all the params,Somewhat similar to T97936? To be able to chnage template name easily.,1449875494,PHID-USER-4j7xntcqqwei7izzlfnd,False,PHID-TASK-jbzu5w4c3nerq2feaawm,task_subcomment,NA
+VisualEditor: there is no way to change the template name without re-filling all the params,"Ideally if the templates are identical but for one piece of information ('be' vs. 'ru') then the template should be used directly ({lang|ru|…}} vs {{lang-ru|…}}, not via accessor methods, which would make this moot. But yes.",1405533424,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jbzu5w4c3nerq2feaawm,task_subcomment,NA
+VisualEditor: Suppress being able to click on links in the error messages from mis-placed local wiki customisations,"window with message
+
+Calling message [[:en:Wikipedia:Edit filter]] 
+
+For example message ""redrect to itself"" (this filtermessage in ru-wiki; in en-wiki is no such call filter, but may work with other message)
+* Edit page in VE
+* Copy page title
+* [Ξ] → Page settings → check ""Redirect this page to"" → past page title (page name of this article)
+* Press Save page (in interface) → Save page (in floating window)
+
+* Start showing Edit filter message (1 image 1)
+* Clik on link in this message - new page open in this floating window and this window i can't close or go back to message (image 2)
+
+Link should open in a new window
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Windows 8.1
+**Platform**: PC
+
+**Attached**: {F14349}",1405438800,PHID-USER-5joeladhczukimiv4rwl,False,PHID-TASK-uav3b7isy6kd7g73ifwt,task_description,resolved
+VisualEditor: Suppress being able to click on links in the error messages from mis-placed local wiki customisations,"This is no longer a problem.
+
+* We no longer use iframes for dialogs, which caused the funny page-in-page effect.
+* Any links in customizable error messages are automatically changed to open in a new browser window/tab when clicked.",1562026815,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-uav3b7isy6kd7g73ifwt,task_subcomment,NA
+VisualEditor: Suppress being able to click on links in the error messages from mis-placed local wiki customisations,"This is caused by an unsuitable use of a template to provide links without a target=""_window"". Maybe we should prevent clicking on the links instead?",1405448152,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uav3b7isy6kd7g73ifwt,task_subcomment,NA
+VisualEditor: Suppress being able to click on links in the error messages from mis-placed local wiki customisations,"Created attachment 15941
+window after click on link
+
+**Attached**: {F14350}",1405438878,PHID-USER-5joeladhczukimiv4rwl,False,PHID-TASK-uav3b7isy6kd7g73ifwt,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","Invoke VE from iOS Safari on tablet,
+
+Make changes to page in VE 
+
+Open second tab, load another website, 
+
+Switch back to tab with VE instance, page is reloaded, and changes are lost",1405412400,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_description,resolved
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",The work done in T57370 is probably sufficient to solve this problem.,1520342734,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","Having poked about with this both locally and in production, I think we can declare this done alongside T57370. Assigning to Ed because he did a lot of the work, both recently and over the past few years.",1519854251,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","#Performance-Team is for any task worked on by the performance team. (Known issues in software we maintain, and improvements anywhere else if we're involved.)
+
+#Performance is a generic tag for other projects to track known problems causing bad performance. (Not usually improvements/enhancements.) In addition, projects with their own subproject or workboard column for performance, normally don't also tag with Performance (similar to Tech Debt). I've untagged this and others with #VisualEditor-Performance.",1494453011,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","#Performance-Team is for any task worked on by the performance team. (Known issues in software we maintain, and improvements anywhere when we assiset on the matter.)
+
+#Performance is a generic tag for all other projects to track known problems causing bad performance. (Not usually improvements/enhancements.) In addition, projects with their own subproject or workboard column for performance, normally don't also tag with Performance (similar to Tech Debt). I've untagged this and others with #VisualEditor-Performance.",1494452258,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","I don't know, what is the difference between //VisualEditor-Performance// and //Performance//, but //Performance// is used in similar VE issues and here is missing",1494450065,PHID-USER-dcexrhjioxqqsq4pdrfe,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",Auto-save issue is T57370,1439375732,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",Also the beahviour is the same on both devices: the tab is only expunged when the device runs out of memory.,1439125042,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","A long term solution would be to store editing state in localStorage. I think there's an existing bug for that.
+
+The best we can do at the moment is warn the user. The most likely time they'll switch is if they're using Citoid, and they go to get a URL to copy.
+",1439124589,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",">>! In T70017#782815, @Eloquence wrote:
+> What is the behavior in Chrome/Android?
+
+Similar, but not 100% reproducible, I think it depends on how much memory the tab is using, which probably corresponds to the size of the article you're editing. chrome might also just try to keep more than one tab alive concurrently ",1416871042,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",">>! In T70017#782815, @Eloquence wrote:
+> What is the behavior in Chrome/Android?
+
+From what I remember of our testing, it's the same, controlling for RAM size. Mostly this is a performance / resource use issue.",1416871006,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes",What is the behavior in Chrome/Android?,1416870939,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","""don't close me bro""",1408659536,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","(In reply to Jared Zimmerman (WMF) from comment #4)
+> This might not be able to resolved as the bug is written (stop safari from
+> reloading) but the current experience for the user in unacceptable. We need
+> a solution. possibly server side drafts or using localstorage on the device.
+> Feel free to rewrite the bug, but we can't ignore this issue.
+
+Well, this is what Apple wants to happen. We already say to the browser ""don't just close me"". Apple has decided in its wisdom to ignore that. We can try to take steps to make it less-terrible, but the underlying issue can't be fixed except upstream…",1408657375,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","This might not be able to resolved as the bug is written (stop safari from reloading) but the current experience for the user in unacceptable. We need a solution. possibly server side drafts or using localstorage on the device. Feel free to rewrite the bug, but we can't ignore this issue.",1408560637,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","Unfortunately, on investigation, this is something that we can't avoid; it's the built-in behaviour of Safari that we have no control over, sadly. Marking as ""WONTFIX"" but it's more ""CANTFIX"".",1408560322,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","Yep, I know this one might be difficult but it obviously makes doing references on mobile basically impossible. glad to see we're prioritizing this.",1408383575,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+"Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes","This is ""normal"" behaviour from Safari, but we need to investigate if we can prevent (or at least discourage) it somehow.",1406748019,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tkjl47hcghbp2eadvr32,task_subcomment,NA
+One-click system for setting user preferences,"This was an interesting comment from WhatamIdoing on T69826, so I thought I'd split it out for its own discussion.
+
+> Changing default user preferences means overriding the choices of 
+> registered editors who actually want the feature (including thousands of 
+> editors who voluntarily opted-in before MediaViewer was made avaialble 
+> by default).  
+> 
+> It's too bad that MediaWiki doesn't have a good one-click system for 
+> changing prefs, like a ""Click here to enable X"" button or pop-up.  It'd be 
+> so much easier than telling hundreds of users ""Go to Special:Preferences, 
+> click to this tab, scroll halfway down, find this item, tick the box, scroll 
+> all the way down, save the page.""
+
+--------------------------
+**See Also**:
+* {T34811}
+* {T69883}",1405075320,PHID-USER-uia2q3o33h5pb5lf7exz,False,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_description,open
+One-click system for setting user preferences,"As GET requests (navigating to a URL) now have to be read-only, this feature would at best be two clicks. The link would need to take you to a page that had a confirm button that triggered the POST request to update your preference.
+
+The only way to make this one click would be to use JavaScript, but then you aren't talking about a simple wiki link.",1668241823,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"(In reply to WhatamIdoing from comment #5)
+> I think I can:
+> 
+> Tell me the exact wikitext I need to type to tell an editor at the English
+> Wikipedia's Help Desk these things:
+> 
+> ""Click HERE to disable MediaViewer""
+
+Don't write ""click here"".
+
+http://www.w3.org/QA/Tips/noClickHere
+
+[…]
+
+> ""Click HERE to set your gender to female""
+
+whatever ajax appears should be clear on privacy implications (value is published) and what exactly it's used for. (software strings not stats, etc) also, remember a11y, aria, etc.",1407204968,PHID-USER-7ey733eainlhx5xqp4d3,False,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"I think I can:
+
+Tell me the exact wikitext I need to type to tell an editor at the English Wikipedia's Help Desk these things:
+
+""Click HERE to disable MediaViewer""
+
+""Click HERE to opt into the Beta Feature VisualEditor""
+
+""Click HERE to set your default image size to 300 px""
+
+""Click HERE to set your gender to female""
+
+""Click HERE to turn on Twinkle""
+
+""Click HERE to turn off Navpops""
+
+""Click HERE to set your default image size to 300 px""
+
+""Click HERE to set your gender to female""",1405140553,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"(In reply to James Forrester from comment #3)
+> I think you have mis-understood this request; it's asking for a consistent,
+> MW-provided system to do this that works the same way for all preferences
+
+The WebAPI works for all preferences. Can you clarify the requirements, as you're so sure about them?",1405125973,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"(In reply to Nemo from comment #2)
+> I don't understand this bug. We have plenty of one-click preference change
+> systems, which alter the preferences via WebAPI. As one prominent example,
+> see [[mw:ULS]].
+
+I think you have mis-understood this request; it's asking for a consistent, MW-provided system to do this that works the same way for all preferences, and which each feature can trivially provide, not specific ad-hoc hacks like ULS etc. use which mean users have to learn them each time.",1405125178,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"I don't understand this bug. We have plenty of one-click preference change systems, which alter the preferences via WebAPI. As one prominent example, see [[mw:ULS]].
+I recommend filing a separate bug for each preference you want one such control for, specifying if it can also supplant the Special:Preferences checkbox (cf. bug 32811; keep bug 31882 in mind).
+
+Unless requirements for this request to be considered fulfilled are clarified, I propose RESOLVED WORKSFORME.",1405125064,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+One-click system for setting user preferences,"Thanks for filing this.
+
+I should note that what would be most functional is a system that lets me post a link (meaning a wikilink or a URL) that represents the command.  I want anyone to be able to do this, not just the devs.  Something like:
+
+""Click [[Special:ChangePreferences/scary-code-name-for-pref |here]] to toggle the tickbox for that pref""
+
+(or whatever format is necessary) would be great.",1405094928,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-omlsw3dhgwnwrd5t5gd6,task_subcomment,NA
+"TemplateData: Deprecated param w/out description text ""no description"" isn't in italic grey","**Author:** `gabrasca2`
+
+**Description:**
+VisualEditor deprecated text
+
+When a param is indicated as ""deprecated"": true and it has no description, in the TemplateData parameters table the text ""no description"" isn't in italic grey.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14398}",1404988140,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-53i433yt4zo2nejhcsxm,task_description,resolved
+"TemplateData: Deprecated param w/out description text ""no description"" isn't in italic grey","Verified in beta with http://en.wikipedia.beta.wmflabs.org/wiki/Template:ET_test
+",1422561370,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-53i433yt4zo2nejhcsxm,task_subcomment,NA
+"TemplateData: Deprecated param w/out description text ""no description"" isn't in italic grey","Change 184440 merged by jenkins-bot:
+Show ""no description"" in italic grey also for deprecated parameters
+
+[[https://gerrit.wikimedia.org/r/184440]]",1421459215,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-53i433yt4zo2nejhcsxm,task_subcomment,NA
+"TemplateData: Deprecated param w/out description text ""no description"" isn't in italic grey","Change 184440 had a related patch set uploaded (by Ricordisamoa):
+Show ""no description"" in italic grey also for deprecated parameters
+
+[[https://gerrit.wikimedia.org/r/184440]]
+
+#patch-for-review",1421097785,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-53i433yt4zo2nejhcsxm,task_subcomment,NA
+VisualEditor: Making an image Frame-left/Frame-right redraws the highlight beyond CE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it frame-left or frame-right.
+
+Observed Result:
+
+The highlight for the image goes beyond the page
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14208}",1404864480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ysnk6kht23okwwdp5gp5,task_description,open
+[DO NOT USE] Support non-image media (tracking) [superseded by #VisualEditor-MediaWiki-Media],We currently don't. We should.,1404850380,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6hasow53qizwpe3vbpsp,task_description,resolved
+[DO NOT USE] Support non-image media (tracking) [superseded by #VisualEditor-MediaWiki-Media],Merged into #VisualEditor-MediaWiki-Media.,1422403165,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6hasow53qizwpe3vbpsp,task_subcomment,NA
+[DO NOT USE] Support non-image media (tracking) [superseded by #VisualEditor-MediaWiki-Media],*** Bug 67689 has been marked as a duplicate of this bug. ***,1404851265,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6hasow53qizwpe3vbpsp,task_subcomment,NA
+"VisualEditor: While inserting an image for the first time, the label for the button in Media Settings dialog should be ""Insert {image|animation|audio|video}"" instead of ""Apply Changes""","Right now while inserting an image, the button that shows up in the Media Settings dialog is ""Apply Changes"", it should be ""Insert"" instead , since there is no change here rather insertion.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1404849960,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-swo2rxiy6wgm2jbww3gv,task_description,resolved
+"VisualEditor: While inserting an image for the first time, the label for the button in Media Settings dialog should be ""Insert {image|animation|audio|video}"" instead of ""Apply Changes""","Checked in test2/production - for inserting a new media, the button will be always 'Insert'.  Marking as Resolved/Verified.",1422409223,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-swo2rxiy6wgm2jbww3gv,task_subcomment,NA
+"VisualEditor: While inserting an image for the first time, the label for the button in Media Settings dialog should be ""Insert {image|animation|audio|video}"" instead of ""Apply Changes""","Expanded, made dependent on bug 67690 for us to be able to tell media types apart.",1404850446,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-swo2rxiy6wgm2jbww3gv,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Copied from my Russian Wikipedia talk page: https://ru.wikipedia.org/wiki/%D0%9E%D0%B1%D1%81%D1%83%D0%B6%D0%B4%D0%B5%D0%BD%D0%B8%D0%B5_%D1%83%D1%87%D0%B0%D1%81%D1%82%D0%BD%D0%B8%D0%BA%D0%B0:Keegan_(WMF)#Bug_report_11
+
+I filled TemplateData for Шаблон:Малая планета
+
+early, template with comments inserted in articles
+{{Малая планета
+<!-- Основной блок -->
+ | param        = 
+<!-- Орбитальные характеристики -->
+ | param        = 
+<!-- Физические характеристики -->
+ | param        = 
+}}
+now if i deleted comments https://ru.wikipedia.org/w/index.php?title=(87)_Сильвия&diff=64040824&oldid=62184664 then i can see parameters in VE editor
+but if comments still in text then VE editor for template staying on ""Загрузка..."" (""Load..."") and don't show parameters. sample: (25143) Итокава
+Sunpriat 08:40, 6 июля 2014 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1404797580,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_description,resolved
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Change 169732 merged by jenkins-bot:
+Bug 67657: Add normalized parameter names to templates
+
+https://gerrit.wikimedia.org/r/169732",1414693263,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Marc, thanks for the clarification. I think the name 'paramWT' contributed to my confusion. It sounds more like the value to me. How about 'key.wt'? That could be extended with key.html etc in the future.
+
+We should definitely include the wikitext for the key, as there is no good way to properly handle editing otherwise. VE shouldn't just pretend that a parameter was not templated, when it was. Those comments also often contain information that the user might be interested in.",1414683407,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Gabriel, 'wt' still contains the original wikitext for the parameter value as it's always done, we're just adding a new paramWt attribute that only shows up if the original parameter name wikitext is different from the actual parameter name that would be used in expansion.
+
+I think the example was a little confusing because the comment in the param name is the same as the param value, sorry for that. Another example, this time with html in it too:
+
+> {{ec<!--tpl comment-->ho|unnamed param value|1<!--param name comment-->2=Param ''value''}}
+
+> {
+> 	'parts': [ {
+> 			'template': {
+> 				'target': {
+> 					'wt': 'ec<!--tpl comment-->ho',
+> 					'href': '../Template:Echo'
+> 				},
+> 			'params':
+> 			{
+> 				'1': {
+> 					'wt': ""unnamed param value"",
+>                                       'html': 'unnamed param value'
+> 				}
+> 			},
+> 			{
+> 				'12': {
+> 					'paramWt': '1<!--param name comment-->2',
+> 					'wt': ""Param ''value''"",
+>                                       'html': 'Param <i>value</i>'
+> 				}
+> 			},
+> 			'i': 0
+> 		}
+> 	} ]
+> }
+
+If paramWt isn't actually needed by VE, maybe we could even not output it at all in data-mw, as it's also kept in data-parsoid…",1414662288,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)",I'm not a fan of making 'wt' return something that's not the original wikitext. How will the need for a normalized name evolve with the 'html' parameter format? It's relatively straightforward to ask for .textContent.,1414624831,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","This looks fine to me. We don't really need paramWt in VE anyway, we don't really care that there was a comment in there, as long as Parsoid can preserve it when the template is edited. So with your proposed change, we wouldn't even have to change anything, because we'd just ignore (and preserve) paramWt.",1414622939,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","In the patch I've uploaded, the normalized parameter name is used as the entry for the parameter info and the original parameter wikitext only appears if different, in the 'paramWt' attribute. So James' example would output as
+
+> {
+> 	'parts': [ {
+> 			'template': {
+> 				'target': {
+> 					'wt': 'ec<!--Ho-->ho<!--Ha!-->',
+> 					'href': '../Template:Echo'
+> 				},
+> 			'params':
+> 			{
+> 				'12': {
+> 					'paramWt': '1<!--Foo!-->2',
+> 					'wt': 'Foo'
+> 				}
+> 			},
+> 			'i': 0
+> 		}
+> 	} ]
+> }
+
+Will that be enough, or should the paramWt be included for each parameter? Most of them will be the same anyway and that would increase page size a lot…",1414599796,PHID-USER-56wtmb23orq4pu5liyj5,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Change 169732 had a related patch set uploaded by Marcoil:
+Bug 67657: Add normalized param names to templates
+
+https://gerrit.wikimedia.org/r/169732",1414599557,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","So… this is asking if Parsoid would consider making the 'params' block of their API give a 'normalised' version of the parameter name, possibly with a 'target' version as well like they do with templates' names?
+
+E.g.:
+
+Wikitext
+
+> {{ec<!--Ho-->ho<!--Ha!-->|1<!--Foo!-->2=Foo}}
+
+
+Current Parsoid output:
+
+> {
+> 	'parts': [ {
+> 			'template': {
+> 				'target': {
+> 					'wt': 'ec<!--Ho-->ho<!--Ha!-->',
+> 					'href': '../Template:Echo'
+> 				},
+> 			'params':
+> 			{
+> 				'1<!--Foo!-->2': {
+> 					'wt': 'Foo'
+> 				}
+> 			},
+> 			'i': 0
+> 		}
+> 	} ]
+> }> 
+
+Requested Parsoid output:
+
+> {
+> 	'parts': [ {
+> 			'template': {
+> 				'target': {
+> 					'wt': 'ec<!--Ho-->ho<!--Ha!-->',
+> 					'href': '../Template:Echo'
+> 				},
+> 			'params':
+> 			{
+> 				'12': {
+> 					'target': '1<!--Foo!-->2',
+> 					'wt': 'Foo'
+> 				}
+> 			},
+> 			'i': 0
+> 		}
+> 	} ]
+> }
+
+… or similar?",1405108181,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","For comparison, Parsoid already strips out html comments from the template title. It should do so for parameter names as well (in addition to trimming whitespace).",1404936594,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Created attachment 15885
+Screenshot of bug.
+
+Screenshot for editing the following on on https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet?veaction=edit
+
+{{Wikimedia engineering project information
+| name        =VisualEditor<!-- This HTML comment should not get deleted or modified. -->
+| description <!-- ignored comment describing the parameter -->= Creating a visual editor for MediaWiki, other platforms and the Web at large
+| logo        =VisualEditor-logo.svg
+| ..
+}}
+
+**Attached**: {F14096}",1404935921,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)","Hm.. it sounds like the bug report says that html comments inside TemplateData conflict with VisualEditor.
+
+However I think this might've been a confusion in translation. I think the reported problem is that when the wikitext has html comments in the transclusion, that Parsoid/VE is including those as part of the template name.
+
+E.g. that when invoking:
+
+{{ Echo
+| 1 <!-- One -->  = Foo
+}}
+
+That the transclusion dialog and/or Parsoid is saying there is a parameter called ""! <!-- One -->"", and renders that as actual text in the label for the UI.
+
+Rephrasing bug accordingly. I think this is something that should be normalised by Parsoid as VisualEditor shouldn't need to know what html comments mean in wikitext.",1404935846,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zrsnll62nd3qae3uw3jx,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","The inspector for <syntaxhighlight /> node immediately closes after opening on Opera 12. I don't yet know why, but I am going to find out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404473940,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3vjexhza3sstfguvlk4h,task_description,declined
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","Seems to have been fixed at some point, I can no longer reproduce.",1416090593,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip",Also affects the comment inspector in standalone.,1410962848,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","Ooh. It only closes itself when opened by clicking the context tooltip. Opening it by double-clicking the node or by pressing Enter when it's selected keeps the inspector open.
+
+After editing it, when the context tooltip is displayed again, clicking it also will always work correctly. Fascinating.",1410962687,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","(In reply to Bartosz Dziewoński from comment #1)
+> * On Opera 12 `rangy.getSelection( this.getElementDocument() ).anchorNode` is
+>   null, but on other browsers it returns the .ve-ce-surface-paste element
+
+Oh, and I forgot the best part: not always. Sometimes the selection is the same as on other browsers. I've somehow caused that several times when debugging, but I have absolutely no idea how.",1404480728,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+"VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip","When you try opening the inspector:
+
+* The 'focusout' event is eventually fired on .ve-ce-surface-paste
+* ve.ce.Surface.prototype.onFocusChange is called
+* On Opera 12 `rangy.getSelection( this.getElementDocument() ).anchorNode` is
+  null, but on other browsers it returns the .ve-ce-surface-paste element
+* Therefore `hasFocus` is false instead of true
+* The document gets blurred, which triggers the inspector to hide some ten
+  levels of abstraction down.
+
+
+No idea why the selection gets lost. Perhaps the inspector should reselect?",1404480463,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3vjexhza3sstfguvlk4h,task_subcomment,NA
+VisualEditor: Changing language of a <syntaxhighlight /> node doesn't load styles for new language,"Changing language of a <syntaxhighlight /> node doesn't load styles for new language. 
+
+SyntaxHighlight_GeSHi defines a module for each supported language (in the format ""ext.geshi.language.$lang""), VE should ensure that the appropriate module is present. Not sure how the content is updated, but the information about required modules should be provided in the ParserOutput and by the action=parse API.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58388",1404435480,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-24czob2fjkxcqpu77r5w,task_description,resolved
+VisualEditor: Changing language of a <syntaxhighlight /> node doesn't load styles for new language,"* https://gerrit.wikimedia.org/r/214078 (branch master): #mw1.26wmf12
+",1435186822,PHID-USER-n4kveqwjjlpsb6ydn73h,False,PHID-TASK-24czob2fjkxcqpu77r5w,task_subcomment,NA
+VisualEditor: Changing language of a <syntaxhighlight /> node doesn't load styles for new language,"Change 214078 merged by jenkins-bot:
+Add VisualEditor support
+
+[[https://gerrit.wikimedia.org/r/214078]]",1435183387,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-24czob2fjkxcqpu77r5w,task_subcomment,NA
+VisualEditor: Changing language of a <syntaxhighlight /> node doesn't load styles for new language,"Change 214078 had a related patch set uploaded (by Jforrester):
+Add VE support for syntax highlighting
+
+[[https://gerrit.wikimedia.org/r/214078]]
+",1432909764,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-24czob2fjkxcqpu77r5w,task_subcomment,NA
+VisualEditor: [Regression wmf12] The highlight for centered images is taking 100% width,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it centre aligned
+4.Keep it selected
+
+Observed Result:
+The highlight for the centered image is taking 100% width
+
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14351}",1404427980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-57aftv3xzvmq2c2u7ztm,task_description,resolved
+VisualEditor: [Regression wmf12] The highlight for centered images is taking 100% width,"Ha. Yes, fixed by Ed as part of his FocusableNode fixes.",1410804238,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-57aftv3xzvmq2c2u7ztm,task_subcomment,NA
+VisualEditor: [Regression wmf12] The highlight for centered images is taking 100% width,Can't reproduce. Must have been fixed in the meantime.,1410804157,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-57aftv3xzvmq2c2u7ztm,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Go to Insert>Media
+
+Observed Result:
+""No results found"" message appearing even before entering a search term inside Media Settings dialog
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+
+**Attached**: {F14200}",1404338520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_description,resolved
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",Verified the fix in production,1411070175,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",Verified the fix in test2,1410554364,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",Verified the fix in Betalabs,1409960770,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 158584 merged by jenkins-bot:
+Abort promises before sending new ones in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/158584",1409957781,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 158584 had a related patch set uploaded by Mooeypoo:
+[wip] Abort promises before sending new ones in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/158584",1409894768,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Okay, it seems the problem is half fixed with the above commit. Now the ""No results"" message no longer appears on top of found results. However, it does seem to pop up and then disappear between searches. 
+
+I'm going to investigate the issue further.",1409886865,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 158530 merged by jenkins-bot:
+Hide ""no results"" messaage in media search widget
+
+https://gerrit.wikimedia.org/r/158530",1409872157,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 158530 had a related patch set uploaded by Mooeypoo:
+Hide ""no results"" messaage in media search widget
+
+https://gerrit.wikimedia.org/r/158530",1409871525,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",*** Bug 70273 has been marked as a duplicate of this bug. ***,1409669754,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","As I mentioned in the dup bug, it's seen in Firefox. In Chrome I see the 'no results' found flicker slightly, but the main issue is in Firefox.",1408660473,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","And I still can't see the issue there. I load ""Insert media"" and I see the search image page empty / processing and then ""No results found"".
+
+I don't see ""No results found"" before the search is done, I only see it after the page searched for a moment and found nothing (as intended)
+
+Tested on Chrome Version 36.0.1985.143 and Firefox 31.0
+
+What am I missing here?",1408660170,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","As in the duplicate bug, page is http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit 
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69877",1408659614,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","I can't replicate this. If you're still seeing this, can you give me the page this is still happening on?",1408659152,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",*** Bug 69877 has been marked as a duplicate of this bug. ***,1408657052,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","I just noticed this is again appearing in Betalabs, when you first open Media Settings dialog and the page name is in the search field,the ""No Result Found"" appears.Also, it appears when you click on ""Change Image"" button",1407353031,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","This is fixed in Betalabs but not on test2, moving it to the next sprint.",1407191690,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 150001 merged by jenkins-bot:
+Use $.when() in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/150001",1406787239,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Change 150001 had a related patch set uploaded by Mooeypoo:
+Use to $.when() in MediaSearchWidget
+
+https://gerrit.wikimedia.org/r/150001",1406575985,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog","Oops. 
+
+Wrong fix to the wrong bug (ignore the above comment)",1406389505,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+"VisualEditor: ""No results found"" message appearing even before entering a search term inside Media Settings dialog",This is fixed by this change: https://gerrit.wikimedia.org/r/#/c/149392/,1406389451,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-lyvz6pfbh5iamln4kped,task_subcomment,NA
+VisualEditor:  Parameter data doesn't always end up in the right parameter box in Firefox,"Report from Jay8g about a bug that may be very hard to reproduce:
+
+""After adding a parameter in the (advanced) template dialog, the focus briefly shifts to the previously added (edited) parameter before going to the one just added. This has led to me occasionally (about one in ten parameter additions) typing (generally just one character) in the wrong box""
+
+""I would type something *immediately* after clicking the parameter button and it would only happen occasionally""
+
+
+Jay's running Firefox 30 on Windows 7.  I've been unable to reproduce this, but I probably haven't tried enough times or been fast enough.  I've been wondering whether this might be easier to reproduce on an old, slow computer.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404324840,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-7qab3gnaeczpqu366xpc,task_description,open
+VisualEditor:  Parameter data doesn't always end up in the right parameter box in Firefox,"The issue is confirmed - it is most noticeable in FF35 on Windows. I've attached a screencast for FF35 on Mac - the problem is noticeable as ""jumpiness"" of parameters in Template dialog. 
+
+Important - to reproduce the bug, add parameter that will be placed **after** previously entered parameter, e.g. after parameter AA add parameter ZZ. Then you can see more clearly that the cursor will be placed momentarily into the previous field.
+
+{F56327}",1425599467,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-7qab3gnaeczpqu366xpc,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,"When we try to add this template:
+
+http://en.wikipedia.org/wiki/User:Jay8g/sandbox/Template:Airline fleet table/Start
+
+the TemplateData does not appear in the dialog.
+
+If we add the doc subpage directly:
+
+http://en.wikipedia.org/wiki/User:Jay8g/sandbox/Template:Airline fleet table/Start/doc 
+
+then TemplateData appears.
+
+We have already made at least three null edits to the template.  I assume that the problem is due to the namespace, but it's not bug 52609, because the template itself adds correctly to the page:  
+
+{{User:Jay8g/sandbox/Template:Airline fleet table/Start}}
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404322800,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-3shl4mcz2khwbu4uvoja,task_description,declined
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,AFAWCT this should work… marking as such.,1405559011,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,Possibly. I had to fiddle around with things like that to check that this was actually working on my machine.,1404762915,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,"(In reply to Alex Monk from comment #2)
+> I don't think this is valid... I can't reproduce it on my machine (with
+> different pages)
+
+Could it be a caching issue?",1404762864,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,I don't think this is valid... I can't reproduce it on my machine (with different pages),1404762624,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace,"(In reply to WhatamIdoing from comment #0)
+> We have already made at least three null edits to the template.  I assume
+> that the problem is due to the namespace, but it's not bug 52609, because
+> the template itself adds correctly to the page:  
+> 
+> {{User:Jay8g/sandbox/Template:Airline fleet table/Start}}
+
+I'm pretty sure it was still fine adding to the page in bug 52609.",1404322953,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-3shl4mcz2khwbu4uvoja,task_subcomment,NA
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,"This may be related to bug 42986:  VisualEditor and Parsoid autoconvert URLs in the external link format to local links, including for interlanguage and other interwiki links.
+
+This means that if you paste https://outreach.wikimedia.org/wiki/Example in as your link on one of the Wikipedias, it gets saved as [[outreach:Example]].  
+
+This is fabulous and should be kept. 
+
+However, if the local wiki doesn't recognize the converted prefix for the link, then the result is a redlink.  At the moment, office.wiki doesn't know about the existence of outreach.wiki, but links are converted anyway.  
+
+The result is that pasting https://outreach.wikimedia.org/wiki/Example as a link on office.wiki gets saved as [[outreach:Example]], and when you click on the resulting redlink, it takes you to the non-existent page https://office.wikimedia.org/wiki/Outreach:Example  
+
+This is not so fabulous.  
+
+The most flexible system is to find out which wikis are known locally, and only convert those.  The most immediate solution is probably to tell office.wiki where to find outreach.wiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404235020,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ibnihv52xnshteoxrd3r,task_description,open
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,"> It's because ""Outreach"" is a namespace name on officewiki. So this is not a MW bug, but a bug probably in Parsoid.
+
+I'd call that a bug in officewiki configuration. They shouldn't use a name reserved for an interwiki in their local namespaces...",1429713699,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-ibnihv52xnshteoxrd3r,task_subcomment,NA
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,"It's because ""Outreach"" is a namespace name on officewiki. So this is not a MW bug, but a bug probably in Parsoid. It shouldn't auto-convert external links to interwikis when the interwiki matches the name or alias of a local namespace.",1405408442,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-ibnihv52xnshteoxrd3r,task_subcomment,NA
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,"This is done in Parsoid, and should normally use the wiki-local interwiki table.
+
+It is listed in https://office.wikimedia.org/w/api.php?action=query&meta=siteinfo&siprop=interwikimap&format=json, so the Parsoid behavior looks correct. Interestingly it is listed twice though: once as 'outreach', and once at 'outreachwiki'. When I manually change the wikitext link to [[outreachwiki:Example]], it is rendered as expected.
+
+So to me this looks either like a configuration issue in officewiki. It could also be a bug in the PHP parser, which only recognizes one of two configured interwiki prefixes.",1404342253,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-ibnihv52xnshteoxrd3r,task_subcomment,NA
+Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name,Does this happen in VE or Parsoid? If the latter it should be moved.,1404339857,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-ibnihv52xnshteoxrd3r,task_subcomment,NA
+VisualEditor: Prompt for edit summary preference breaks the save dialog,"If a user has the preference ""Prompt me when entering a blank edit summary"" selected, VisualEditor's save dialog has to be closed and reopened to work. The ""Save"" button is greyed out even when an edit summary is entered.
+
+To reproduce:
+1. Enable Preferences>Editing>tick Prompt me when entering a blank edit summary
+2. Attempt to save a VE edit and the prompt for an edit summary comes up, with save not an option
+3. Enter an edit summary
+4. Save is still not an option
+5. Exit out of the dialog by clicking X and click save again
+6. You can now save your edit with an edit summary
+
+Firefox 30 on Mac OS X Mavericks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404185940,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_description,resolved
+VisualEditor: Prompt for edit summary preference breaks the save dialog,"Change 143326 merged by jenkins-bot:
+After showing missing edit summary error, mark the dialog as not pending anymore
+
+https://gerrit.wikimedia.org/r/143326",1404232141,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_subcomment,NA
+VisualEditor: Prompt for edit summary preference breaks the save dialog,This was probably an oversight on my part in Gerrit change 135945,1404226652,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_subcomment,NA
+VisualEditor: Prompt for edit summary preference breaks the save dialog,"Change 143326 had a related patch set uploaded by Alex Monk:
+After showing missing edit summary error, mark the dialog as not pending anymore
+
+https://gerrit.wikimedia.org/r/143326",1404226461,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_subcomment,NA
+VisualEditor: Prompt for edit summary preference breaks the save dialog,Sounds like we need to code in that the you-must-set-an-edit-summary message is a recoverable error.,1404187302,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yyzfeh3uodjnkeirw6ar,task_subcomment,NA
+MediaWiki:Visualeditor-wikitext-warning-link should link mediawiki.org,"On translatewiki.net I see a red link in messages and this page won't exist on most wikis, just link https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Formatting by default. See blocked bug for example and remember, Brion veto'ed the simple solution i.e. interwiki link [[mediawikiwiki:Special:MyLanguage/Help:Formatting]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1404044760,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-difb2qmugpstitptxrln,task_description,resolved
+MediaWiki:Visualeditor-wikitext-warning-link should link mediawiki.org,"Heh, WP:BEANS applies. Thanks.",1417038167,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-difb2qmugpstitptxrln,task_subcomment,NA
+MediaWiki:Visualeditor-wikitext-warning-link should link mediawiki.org,"Change 175886 merged by jenkins-bot:
+Point wikitext markup link in warning to MW.org
+
+[[https://gerrit.wikimedia.org/r/175886]]",1416966201,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-difb2qmugpstitptxrln,task_subcomment,NA
+MediaWiki:Visualeditor-wikitext-warning-link should link mediawiki.org,"Change 175886 had a related patch set uploaded (by Jforrester):
+Point wikitext markup link in warning to MW.org
+
+[[https://gerrit.wikimedia.org/r/175886]]
+
+#patch-for-review",1416956749,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-difb2qmugpstitptxrln,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"Key events fire without key codes (understandable as you can 'swipe' whole words) and backspace fires no key[up|down|press] event at all.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403994660,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_description,open
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"There is a still  bug where no events are fired if the cursor is in an empty span, and deleting across a paragraph.",1539445981,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,Looks like on latest Chrobile/iOSafari we get input+beforeinput events with an inputType of 'deleteContentBackward'. This should be enough to fix this (assuming we can preventDefault).,1539363966,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"Note that Android 4.4's WebView is based on the Chromium engine, and unlike the standalone Chrome app it only gets updated with the OS. Might want to check whether the  stock Android browser on non-Google-branded 4.4.x devices is also affected. (Nexus devices seem to leave out the AOSP default browser in favor of Chrome, but I see a customized version on Samsung Galaxy branded devices for instance.)",1404400580,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"OS update is not an issue, just app.",1404381778,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"(In reply to Ed Sanders from comment #6)
+> It looks like the above commit to Chrome for Mobile has been merged, which
+> solves the most serious case (no event fired at all).
+
+It doesn't ""solve"" it perfectly, as OS update lag for Android devices is notoriously slow (or non existent), and app update take-up is apparently poor. Is there a sane work-around we could do?
+
+> We are still left with the general problem of IME deletion.
+
+Yeah. :-(",1404353204,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"It looks like the above commit to Chrome for Mobile has been merged, which solves the most serious case (no event fired at all). We are still left with the general problem of IME deletion.",1404340111,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"""No key event is generated when the BACKSPACE key is pressed outside of composition, in other words, when AdapterInputConnection.deleteSurroundingText is called. In the reported bug, since the text field is empty, thus IME is not in the composition mode, thus pressing the BACKSPACE key triggers deleteSurroundingText and thus no key event is generated.
+
+A cl that generates key events in deleteSurroundingText with a dummy keycode is under review at https://codereview.chromium.org/348413003/.""",1403996659,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"Not quite true, see http://jsbin.com/alAKaNaZ/5
+
+Backspace fires a keydown with keyCode 0 (same as every other key event) but not when whitespace is deleted.
+
+See https://code.google.com/p/chromium/issues/detail?id=184812",1403996593,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"See https://code.google.com/p/chromium/issues/detail?id=118639 for pitchfork waving, including a complaint from the Microsoft Office Web Apps team who are having the same problem.",1403995499,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,"There is an 'input' event which fires, but this doesn't solve the problem of prevent the default backspace behaviour.",1403995446,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace,Oy.,1403994743,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fv7pgm7ma7rzqtzsf675,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"Setup- FF 30.0. 
+Steps to Reproduce-
+1>Launch the FF browser.  And go to your user page in Beta labs.
+2>Click on “Edit Source” tab.  Click anywhere on the Wikitext Editor pane.
+3>Now while the cursor is still blinking in the editor pane, press the keyboard shortcut for the VE editor tab which is “Alt+Shift+v”.  
+
+Actual Result-When the keyboard shortcut for the VE editor tab i,e. “Alt+Shift+v” is pressed, it just scrolls the window down, while the Wikitext Editor pane is still open and instead the “Show Changes” button gets highlighted(which apparently has the same keyboard shortcut combination).  The same behavior was observed in test2 environment for FF browser. But in Safari and Chrome no such similar behavior was found.
+
+Expected Result-When pressed the keyboard shortcut of “Alt+Shift+v” should access the Edit beta tab and open the VE pane.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**: {T54701}",1403905980,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3gt4ltdm5464h2so4dbt,task_description,duplicate
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"Just to on the safe side, this is not the same as T114793?",1459687141,PHID-USER-4j7xntcqqwei7izzlfnd,False,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"I'd like to see meta-V in read mode be VisualEditor, and meta-V in wikitext editor be the diff.",1445014779,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"We could have a different accesskey from action=edit (or just a new one in general), but that seems like it would confuse people.",1410125531,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"(In reply to Alex Monk from comment #2)
+> The 'Show changes' button has accesskey=v, so there's a conflict. Chrome
+> just goes for the first one on the page and breaks the 'Show changes'
+> shortcut, Firefox moves between the two. Not sure what we should do about
+> that.
+
+Oh, yeah, that thing. *sighs* I guess this would get fixed with a switch to a single edit tab, but I'm not sure what we could do in advance of that.",1405008025,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"The 'Show changes' button has accesskey=v, so there's a conflict. Chrome just goes for the first one on the page and breaks the 'Show changes' shortcut, Firefox moves between the two. Not sure what we should do about that.",1404943447,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser,"Yeah, Ctrl+Alt+v (on a Mac) works fine for me in read mode, but not in wikitext edit mode, where it just selects the tab… Something odd here.",1404773531,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3gt4ltdm5464h2so4dbt,task_subcomment,NA
+VisualEditor: Deleting a block item highlights the previous line,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE which contains a block item like reflist or image
+2.Delete the image
+
+Observed Result:
+A highlight appears from the end of the previous line covering up the rest of the line.
+
+Instead of highlighting, upon deleting the block item the cursor should just appear at the end of the previous line.
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14275}",1403901720,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_description,resolved
+VisualEditor: Deleting a block item highlights the previous line,Verified the fix in production,1405027416,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_subcomment,NA
+VisualEditor: Deleting a block item highlights the previous line,Verified the fix in betalabs and test2,1404771578,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_subcomment,NA
+VisualEditor: Deleting a block item highlights the previous line,"Change 142806 merged by jenkins-bot:
+Fix up selection after deletion if at non-content offset
+
+https://gerrit.wikimedia.org/r/142806",1403990939,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_subcomment,NA
+VisualEditor: Deleting a block item highlights the previous line,"Change 142806 had a related patch set uploaded by Esanders:
+Fix up selection after deletion if at non-content offset
+
+https://gerrit.wikimedia.org/r/142806",1403968234,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-si5gnqfnmh6gbx5l4jrp,task_subcomment,NA
+"VisualEditor: Block items converted to inline initially show a flash of highlight trying to select the previous line, and then the selection normalises to just the item","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Make it Frameless-Left or Basic-Left
+4.Now uncheck the wrapping option.
+
+
+Observed Result:
+The previous line gets highlighted for a split second then the highlight goes away.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403901180,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-pz2ixq5zf5t25xrb4rxy,task_description,resolved
+"VisualEditor: Block items converted to inline initially show a flash of highlight trying to select the previous line, and then the selection normalises to just the item",Can't reproduce. Very old bug so probably been fixed.,1701963876,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-pz2ixq5zf5t25xrb4rxy,task_subcomment,NA
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,"1. Create a page with {{echo|foo}} in the text somewhere
+2. Observe that the word ""foo"" is highlighted and clickable and all those good things
+3. Inspect ""foo"", and change the parameter to ""bar""
+4. Click the rerendering
+
+Note that there is no highlight, you're able to select parts of the word (!), it's not inspectable, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403824740,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_description,resolved
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,"Change 140439 merged by jenkins-bot:
+[BREAKING CHANGE] Remove generated content node wrappers
+
+https://gerrit.wikimedia.org/r/140439",1404170273,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_subcomment,NA
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,Confirmed fix,1403906711,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_subcomment,NA
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,"Change 140439 had a related patch set uploaded by Esanders:
+[BREAKING CHANGE] Remove generated content node wrappers
+
+https://gerrit.wikimedia.org/r/140439",1403906694,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_subcomment,NA
+VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly,What about after https://gerrit.wikimedia.org/r/140439 ?,1403827630,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-fynwqc5w5zeshpbxgfhb,task_subcomment,NA
+VisualEditor should support redirects to sections on a page,"Steps to reproduce:
+
+1.  Go to Page settings and tick the box to make a redirect.
+
+2.  Type in not just a page title, but also a section:  Example#Foo
+
+3.  Now what?  If I click ""Example"" in the list, it deletes the #Foo part.
+
+
+It turns out that if you click outside the page settings dialog, that it actually will accept this, but it looks impossible.
+
+Then when you ""apply changes"", the redirect isn't visible on the page (T63861) so you can't tell whether it worked or did anything at all.",1403805420,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-eegih6kooypkdgwbf43y,task_description,resolved
+VisualEditor should support redirects to sections on a page,"This seems to work the right way these days. If you input a title+section, the same is shown as the first element of the suggestions (but only if a page by that title exists). {F7052264}",1490714782,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-eegih6kooypkdgwbf43y,task_subcomment,NA
+VisualEditor should support redirects to sections on a page,"So, when you have a title+section link in the text box, and the suggestions show the page name that's currently in there, an extra suggestion should be added for the full title+current section? I think anything more than that would be T52881",1481110936,PHID-USER-mvx4x7ywk2flsaku2dbk,True,PHID-TASK-eegih6kooypkdgwbf43y,task_subcomment,NA
+VisualEditor should support redirects to sections on a page,This very likely would use some (magical) technology that would be needed to fix {T52881}.,1481055579,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eegih6kooypkdgwbf43y,task_subcomment,NA
+VisualEditor:  Broken Kloutify browser extension injects garbage into the page,"https://en.wikipedia.org/w/index.php?title=Lobstick&curid=43120379&diff=614082884&oldid=614013920
+
+The user edited the page twice, resulting in two copies of this:
+
+<div id=""kloutify""><div></div><div id=""kloutify-score"">10</div></div>
+
+at the top of the page.  The ""10"" is visible on the page.
+
+http://kloutify.com/ says that this can be installed on Firefox, Chrome, and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1403562600,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ruav2ogzbcqvzadctvdr,task_description,resolved
+VisualEditor:  Broken Kloutify browser extension injects garbage into the page,"Change 163968 merged by jenkins-bot:
+Blacklist div[id = kloutify] as well
+
+https://gerrit.wikimedia.org/r/163968",1412114701,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ruav2ogzbcqvzadctvdr,task_subcomment,NA
+VisualEditor:  Broken Kloutify browser extension injects garbage into the page,"Change 163968 had a related patch set uploaded by Alex Monk:
+Blacklist div[id = kloutify] as well
+
+https://gerrit.wikimedia.org/r/163968",1412114584,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ruav2ogzbcqvzadctvdr,task_subcomment,NA
+VisualEditor: Offer ability to save without exiting (for saving your work in the middle of an editing session),"Opening VisualEditor can be slow for some pages/some users.  Please offer the option of saving without exiting.
+
+(Original suggestion:  https://en.wikipedia.org/w/index.php?diff=613298543&oldid=613210959)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403195460,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jaeqm7s2wtu2hyzgjf62,task_description,open
+VisualEditor: Offer ability to save without exiting (for saving your work in the middle of an editing session),"There is now T57370, but that is only for the purpose of crash recovery, and only if the exact same tab is reopened, which does not satisfy this use case.",1525335642,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-jaeqm7s2wtu2hyzgjf62,task_subcomment,NA
+VisualEditor: Offer ability to save without exiting (for saving your work in the middle of an editing session),Interesting idea.,1403220029,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jaeqm7s2wtu2hyzgjf62,task_subcomment,NA
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)","Steps to reproduce:
+
+1.Open a page with Mobile VE
+2.Type a text 
+3.Tap on the ""Return"" key from the keyboard
+
+Observed Result:
+Instead of adding a newline and moving the cursor to it, it deletes the preceding text.
+
+Device:Nexus 7(Android 4.4.2)
+Environment:Production (en.wiki) and Betalabs",1403049840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_description,open
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)",The current Android version of Nexus 7 is 6.0.1 (Marshmallow). Shall the task description be updated to reflect that?,1604088026,PHID-USER-bf7nnwcm4i6wicvxtb77,False,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_subcomment,NA
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)","This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
+
+For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
+(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)",1592584225,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_subcomment,NA
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)","The previous comments don't explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status.
+
+//(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}. If this task is stalled on an upstream project, then the #upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task needs retesting, then the #testme tag should be added. If this task is either out of scope and nobody should ever work on this, or nobody else managed to reproduce the problem described in this task, then this task should have the ""Declined"" status.)//",1590761764,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_subcomment,NA
+"VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)",Needs re-testing.,1430336368,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jtmgedmpbpvmorw6vcq2,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),"Steps to reproduce:
+
+1.Open any page with Mobile VE in Nexus 7(Android 4.4.2)
+2.Type a text
+3.Save the page
+
+Observed Result:
+The edit does not get saved
+
+Device:Nexus 7(Android 4.4.2)
+Environment: Production (en.wiki) and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1403047800,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xttfxhpiryw6znoqo7lj,task_description,resolved
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),"Checked this issue , in en.wiki and test2 , not happening anymore. closing this one.",1430339892,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),"Was this specifically with that device, and not any others tested?",1429567642,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),Seems to be a mis-tag.,1405008111,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),"Change 145222 had a related patch set uploaded by BryanDavis:
+[WIP] Enable HHVM debugging REPL
+
+https://gerrit.wikimedia.org/r/145222",1404968989,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2),Try to recheck in case this was a deployment issue?,1404330034,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xttfxhpiryw6znoqo7lj,task_subcomment,NA
+"VisualEditor Mobile: Tapping at the end of each link, does copy-paste of preceding link text in Nexus 7(Android 4.4.2)","Steps to reproduce:
+
+1.Open a page with mobile VE
+2.Tap at the end of a link
+
+Observed Result:
+The link gets copied at the position your cursor was on and it will keep continue doing that everytime you place your cursor at the end of extended link.
+
+See the screenshot attached
+
+Device: Nexus 7(Android 4.4.2)
+Environment:Production (en.wiki) and Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1403047020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-lrdaa764ev2rnhtfh6c7,task_description,duplicate
+"VisualEditor Mobile: Tapping at the end of each link, does copy-paste of preceding link text in Nexus 7(Android 4.4.2)",Needs re-testing.,1430336075,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lrdaa764ev2rnhtfh6c7,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Right now the HTML created for
+- headings specified using Wikitext (e.g. ""=="")
+- headings created using HTML tags (e.g. ""<h2>"")
+look basically the same.
+
+- Both have a wrapping heading element (without class or id)
+- Both contain a <span> of class ""mw-headline""
+
+The only (but major) difference is that sections created by Wikitext are editable and therefore contain an additional <span> of class ""mw-editsection"".
+
+It would be nice if there was an easy possibility to directly differentiate those types of headers on a CSS level (e.g. by an additional class applied to the parent <h*> element)
+
+
+This would make it much easier to create custom CSS and JS since often one would only want to style ""true"" (that is editable) article headers created by Wikitext instead of custom created headers that are mostly used for design of e.g. project pages.
+Right now such CSS and JS often erroneously styles all headers the same, regardless of how the headers were created, often resulting in unintentional appearance.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: enhancement",1402834020,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_description,open
+Make it possible to distinguish Wikitext headings and HTML headings,"It does seem a bit strange though to simultaneously push for all media files to have a convoluted `typeof`-based syntax and for headings to not have `typeof`-based syntax. Though I do think that `<figure>` conversion as implemented was a massive mistake and we ended up with a lot of CSS bloat because of it that could’ve been avoided if classes were used, so I don’t have a problem with using them generally.",1735855955,PHID-USER-3ljmcrqixyljk2wy63jb,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"I forgot to note this here at the time, but I talked to some folks from the Content Transform team after I proposed these patches, who didn't like them very much because the semantic meaning of these attributes wasn't clear and it would also require changes to the Parsoid HTML spec with backwards-compat implications. Their counterproposal was adding some class name or some other attribute to only the ""raw"" HTML headings instead (internal Slack link: https://wikimedia.slack.com/archives/C024Z8K9CAU/p1705359054223579 – sorry, not publicly accessible). I'd be happy with that too, I just didn't get around to trying to implement it.
+
+Substantially the same idea was also proposed in T13555#9896561 by @Od1n.",1722710671,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990778 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/extensions/DiscussionTools@master] Detect HTML headings using 'typeof=""mw:Heading""'%%%
+Reason:
+%%%I'm not working on this at the moment.%%%
+https://gerrit.wikimedia.org/r/990778",1709839372,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990777 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/extensions/VisualEditor@master] Allow 'typeof=""mw:Heading""' on Parsoid headings%%%
+Reason:
+%%%I'm not working on this at the moment.%%%
+https://gerrit.wikimedia.org/r/990777",1709839365,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990776 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/services/parsoid@master] Add 'typeof=""mw:Heading""' to wikitext headings%%%
+Reason:
+%%%I'm not working on this at the moment.%%%
+https://gerrit.wikimedia.org/r/990776",1709839359,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990775 **abandoned** by Bartosz Dziewoński:
+%%%[mediawiki/core@master] Add 'typeof=""mw:Heading""' to wikitext headings%%%
+Reason:
+%%%I'm not working on this at the moment.%%%
+https://gerrit.wikimedia.org/r/990775",1709839354,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990778 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/DiscussionTools@master] Detect HTML headings using 'typeof=""mw:Heading""'%%%
+https://gerrit.wikimedia.org/r/990778",1705357839,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990777 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Allow 'typeof=""mw:Heading""' on Parsoid headings%%%
+https://gerrit.wikimedia.org/r/990777",1705357829,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990776 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/services/parsoid@master] Add 'typeof=""mw:Heading""' to wikitext headings%%%
+https://gerrit.wikimedia.org/r/990776",1705357823,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Make it possible to distinguish Wikitext headings and HTML headings,"Change 990775 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/core@master] Add 'typeof=""mw:Heading""' to wikitext headings%%%
+https://gerrit.wikimedia.org/r/990775",1705357816,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3ia4hoqkuy3so5q5dge4,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"It is possible (if inadvisable) to have whitespace at the start of a paragraph in HTML; to readers it is mostly invisible. In MediaWiki, because whitespace at the start of a paragraph has magic meaning, Parsoid `<nowiki />`s it. To avoid users doing this accidentally, it might be nice to design a way to flag to the user what they've done when they create these.",1402788000,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_description,resolved
+Spaces at the start of a paragraph aren't very obvious,"Thanks, Guillaume! I'll be watching.",1434448096,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,">>! In T68628#1366507, @Elitre wrote:
+> Even on Office wiki? If not, I have a diff from June 12th about that.
+
+I had the same question earlier today, and @Jdforrester-WMF said it might be related to JavaScript that was cached in the user's browser. It may take a few weeks for the issue to completely disappear.",1434390205,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"Even on Office wiki? If not, I have a diff from June 12th about that.",1434389638,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"VisualEditor now strips leading whitespace by design, so this task has become obsolete. Closing.",1434389028,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"It's still happening:  https://en.wikipedia.org/w/index.php?diff=660662487&oldid=657477479  The original had only one space between paragraphs, but I usually add two in wikitext (""English spacing""), so there may have been two spaces at the time that I hit return to split the paragraphs.",1430691888,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"This issue came up 4 times out of 100 reviewed diffs, and accounted for ⅔ of problematic diffs on the English Wikipedia this week ( T94767#1225878 ). I see this being a possible point of contention during a wider roll-out.
+
+Based on those numbers, I'm re-nominating this issue as a blocker for further discussion.",1429725232,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"{T78137} sounds like an interesting approach.
+
+I tested now and it seems like the leading spaces can still be created and displayed in the editor, but magically disappear when the MediaWiki page is saved.",1429614294,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"@Jdforrester-WMF by the way, was this officially rejected as blocker, or was the blocker tag removed for another reason?",1428429815,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,">>! In T68628#1150309, @Jdforrester-WMF wrote:
+> 
+> I have reverted the title change because it is **completely** wrong. ""Remove nowikied spaces at the beginning of a paragraph unless the user manually inserted them"" means ""please corrupt pages on load"", and is absolutely the wrong this to do. VisualEditor is not in the business of ""fixing"" pages. If you click edit, then click save without making changes, there should never ever be any difference, or we've failed.
+
+That's not at all what I meant. I didn't suggest we fix unrelated spaces; I thought the accompanying description (which you moved to T93935) made that clear. Sorry for the misunderstanding.",1428429657,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"I'm having second thoughts about my earlier all-clear.  It's possible that this problem only arises if the wikitext uses French spacing (two spaces after the full stop).  If that's the case—if it strips one space but leaves the second—then my test yesterday is inadequate, because I didn't check what the wikitext looks like.",1427410533,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"I've restored this task back to what it's about, which is a **design** issue about discouraging odd user behaviour, and has essentially nothing to do with `<nowiki />`s, which are already dealt with in multiple other tasks.
+",1427312907,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,">>! In T68628#1150358, @Whatamidoing-WMF wrote:
+> This appears to be fixed now (same browser/same article test).
+> 
+> I think that a title of ""Stop adding nowiki'd spaces at the start of newly
+> split paragraphs"" would capture the ask better.  I don't really want to see
+> the spaces (although that would be better than having them present but
+> invisible); I want the stray spaces to not be present in the first place.
+
+That's a different task, which I have created: {T93935}.",1427312590,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"This appears to be fixed now (same browser/same article test).
+
+I think that a title of ""Stop adding nowiki'd spaces at the start of newly
+split paragraphs"" would capture the ask better.  I don't really want to see
+the spaces (although that would be better than having them present but
+invisible); I want the stray spaces to not be present in the first place.",1427312389,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,">>! In T68628#1146900, @gpaumier wrote:
+> Are there any valid use cases for keeping those white spaces at the beginning of a paragraph? Otherwise I think we should just remove them. If we don't want to remove them automatically on save, then as @Whatamidoing-WMF suggested in T68628#967908 , we should at least remove the space when editing, so that the nowikied space is added //only if// the user explicitly inserts it.
+
+I have reverted the title change because it is **completely** wrong. ""Remove nowikied spaces at the beginning of a paragraph unless the user manually inserted them"" means ""please corrupt pages on load"", and is absolutely the wrong this to do. VisualEditor is not in the business of ""fixing"" pages. If you click edit, then click save without making changes, there should never ever be any difference, or we've failed.",1427312461,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"I have reverted the title change because it is **completely** wrong. ""Remove nowikied spaces at the beginning of a paragraph unless the user manually inserted them"" means ""please corrupt pages on load"", and is absolutely the wrong this to do. VisualEditor is not in the business of ""fixing"" pages. If you click edit, then click save without making changes, there should never ever be any difference, or we've failed.",1427312066,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,,1427236528,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,,1427236492,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"Are there any valid use cases for keeping those white spaces at the beginning of a paragraph? Otherwise I think we should just remove them. If we don't want to remove them automatically on save, then as @Whatamidoing-WMF suggested in T68628#967908 , we should at least remove the space when editing, so that the nowikied space is added //only if// the user explicitly inserts it.",1427236470,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"The nowikied space also persists if a user then removes the newline. See https://en.wikipedia.org/w/index.php?diff=653301980 for an example in which:
+* an existing nowikied space at the beginning of a paragraph now lives in the middle of a paragraph;
+* a new nowikied space was added at the beginning of a paragraph.",1427236275,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"I'm adding Parsoid to this, because Subbu thought that it might be solvable there.",1424153311,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"This is still happening.  I'm still not doing anything exceptional:  I put my cursor in between two sentences and press the Return key.  This still should not be happening. If I want to start a paragraph with a space, then I should have to actually press the space bar.
+
+https://en.wikipedia.org/w/index.php?diff=prev&oldid=641792115",1420862401,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"No, they actually are not shown.  
+
+Download the screenshot and pull it into Preview on your Mac. Zoom in six times, scroll way over to the red ovals, and use ""Tools:Annotate:Line"" to draw a vertical line down the leading edge of those paragraphs.  Hold down your shift key to keep the line straight.  Set the line to the thinnest option in the toolbar.  
+
+Now count the pixels between your line and the beginnings of each letter on those paragraphs.  The straight edge on the 'r' of 'raised', the 'E' of 'Experience', and the 'M' of 'Modern' are very convenient for this.  
+
+There is no visible difference.  Where I drew my line, I found exactly one pixel between my line and the start of each character.  Something that does not display as even a single pixel on a reasonably typical laptop is properly described as ""not shown"".",1410805643,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,They actually are shown – but it's very hard to see them. Re-wording.,1403742784,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+Spaces at the start of a paragraph aren't very obvious,"Created attachment 15656
+Nowiki tags enclose spaces, but no spaces are shown in VisualEditor
+
+**Attached**: {F13610}",1402788280,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-g2k2n2sjdlne5edkxabr,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"Highlighting entire paragraphs and applying or removing list formatting should consistently apply or remove formatting, currently some items are ignored.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42115",1402434120,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_description,declined
+VisualEditor: Reconsider list functions' application and clearing,"(In reply to Jared Zimmerman (WMF) from comment #4)
+> I'd love for us to do a set of user tests around this. Just because
+> word/gdocs/openoffice does something doesn't mean it is the correct thing to
+> do. Not saying we got it wrong, but I think hearing specific feedback on
+> this from users might be useful. 
+
+Absolutely. Just flagging that we've already spent many dozens of hours going back and forth about this with users and designers. It's not remotely a green field. :-)
+
+> I agree that a table or a link isn't ""formatting"" in this sense, but lists
+> don't fit as neatly into that category for me, I'd love to hear from users.
+
+Definitely.",1403745763,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"@abbey, can you create a card in the backlog to help the VE team validate some of the assumptions around formatting behavior best practices please.",1403745535,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"I'd love for us to do a set of user tests around this. Just because word/gdocs/openoffice does something doesn't mean it is the correct thing to do. Not saying we got it wrong, but I think hearing specific feedback on this from users might be useful. 
+
+I agree that a table or a link isn't ""formatting"" in this sense, but lists don't fit as neatly into that category for me, I'd love to hear from users.",1403745437,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"(In reply to Jared Zimmerman (WMF) from comment #2)
+> Nested list items…
+> 
+> Shouldn't clear formatting clear nested list items styles as well? That
+> would be my expectation.
+
+No. Lists, tables, blockquotes, headers, preformatted etc. are all considered ""structural"" changes rather than ""styles"".
+
+Right now the selection-action behaviour for links is modelled after a number of different editors with some insanely complex edge-cases (e.g. applying ""make numbered list"" to a selection covering some numbered list items, some paragraphs, some nested bullet list sub-items, and some partials of the above).",1403744085,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"Nested list items…
+
+Shouldn't clear formatting clear nested list items styles as well? That would be my expectation.",1403743131,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+VisualEditor: Reconsider list functions' application and clearing,"(In reply to Jared Zimmerman (WMF) from comment #0)
+> Highlighting entire paragraphs and applying or removing list formatting
+> should consistently apply or remove formatting, currently some items are
+> ignored.
+
+Which items?",1403742919,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-vtm3ino3v2y3b5ubwieo,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","For list of repositories see https://www.mediawiki.org/wiki/Repositories_with_Ruby_code
+
+For more information see https://www.mediawiki.org/wiki/Manual:Coding_conventions/Selenium#expect_or_should
+
+Still not implemented in:
+
+- mediawiki/extensions/ArticleFeedbackv5
+- mediawiki/extensions/CirrusSearch
+- mediawiki/extensions/ContentTranslation
+- mediawiki/extensions/Flow
+- mediawiki/extensions/Gather
+- mediawiki/extensions/MultimediaViewer
+- mediawiki/extensions/PdfHandler
+- mediawiki/extensions/Translate
+- mediawiki/extensions/TwnMainPage
+- mediawiki/extensions/UniversalLanguageSelector
+- mediawiki/extensions/UploadWizard
+
+```
+$ grep --include *.rb  -R -F '.should' .
+
+mediawiki/vagrant/mediawiki/extensions/ArticleFeedbackv5/tests/browser/features/step_definitions/aftv5_steps.rb:    page.yes_element.when_present.should be_visible
+...
+mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/page_steps.rb:    result.status.should eq 200
+...
+mediawiki/vagrant/mediawiki/extensions/ContentTranslation/tests/browser/features/step_definitions/basic_mt_steps.rb:  on(ContentTranslationPage).translation_editor_element.text.should == text
+...
+mediawiki/vagrant/mediawiki/extensions/Flow/tests/browser/features/step_definitions/description_steps.rb:    page.description.content.should eq(content)
+...
+mediawiki/vagrant/mediawiki/extensions/Gather/tests/browser/features/step_definitions/recent_collections_steps.rb:  on(GatherRecentPage).collection_one_hundred_element.should exist
+...
+mediawiki/vagrant/mediawiki/extensions/MultimediaViewer/tests/browser/features/step_definitions/mmv_options_steps.rb:  on(E2ETestPage).mmv_options_menu_disable_element.should be_visible
+...
+mediawiki/vagrant/mediawiki/extensions/PdfHandler/tests/browser/features/step_definitions/pdf_steps.rb:  on(PdfPage).download_as_pdf_element.should exist
+...
+mediawiki/vagrant/mediawiki/extensions/Translate/tests/browser/features/step_definitions/manage_translator_sandbox_steps.rb:	on(UserPage).babel_box_has_languages?(languages).should be_true
+...
+mediawiki/vagrant/mediawiki/extensions/TwnMainPage/tests/browser/features/step_definitions/signed_in_and_approved_user_steps.rb:		page.number_of_translators_element.should be_visible
+...
+mediawiki/vagrant/mediawiki/extensions/UniversalLanguageSelector/tests/browser/features/step_definitions/accept_language_steps.rb:  on(MainPage).main_page_element.text.should == text
+...
+mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/chunked_upload_steps.rb:  on(UploadPage).continue_element.when_present(300).should be_visible
+...
+```
+
+",1402321140,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_description,declined
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",Because of {T139740} this is unlikely to ever get done.,1495811105,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","A tool like these could automate the process:
+
+http://xinminlabs.github.io/synvert/rules/
+https://github.com/yujinakayama/transpec",1446720289,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Removed release-engineering, since it does not belong there.
+Removed patch-for-review, since all related patches (as far as I can see) are merged or abandoned.",1436283720,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",Removed,1427714305,PHID-USER-t4rpicnsgzxayalzj6k6,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","@jagori79 are you working on this? If not, please remove yourself from ""assigned to"". Thanks.",1427291727,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","@Physikerwelt: no problem. I think it would be a lot of noise if we created 20 or so subtasks, but it is something to consider for the future tasks.",1426863595,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Sorry for closing this bug. I thought it was only about the Math extension, because the project Math was specified. I think in the future it might be better to add subtasks for each extension.",1426862947,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186947 merged by jenkins-bot:
+Use rspec-expectations ""expect"" syntax instead of ""should"" syntax
+
+[[https://gerrit.wikimedia.org/r/186947]]",1426861426,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",,1443645049,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",,1426858450,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186949 merged by jenkins-bot:
+Change RSpec 2 should syntax to RSpec 3 expect syntax
+
+[[https://gerrit.wikimedia.org/r/186949]]",1424517099,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 187269 merged by jenkins-bot:
+RSpec 3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/187269]]",1424516577,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 179072 merged by jenkins-bot:
+Refactor code for RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/179072]]",1424115983,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","I was not able to test this for the Math Extension:
+See my comment in gerrit:
+""
+I could not test the effects of this change. I tried to run the tests on labs-vagrant instance following the guide at https://www.mediawiki.org/w/index.php?title=Quality_Assurance/Browser_testing/Running_tests#Running_VisualEditor_browser_tests_via_labs-vagrant However, even on master I get the following output https://gist.github.com/physikerwelt/5761056c077c02a8c636
+""",1422524733,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 187269 had a related patch set uploaded (by Jagori79):
+RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/187269]]
+
+#patch-for-review",1422486258,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186949 had a related patch set uploaded (by Jagori79):
+Changing should to expect syntax
+
+[[https://gerrit.wikimedia.org/r/186949]]
+
+#patch-for-review",1422362252,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186947 had a related patch set uploaded (by Jagori79):
+RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/186947]]
+
+#patch-for-review",1422360779,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 186947 had a related patch set uploaded (by Jagori79):
+RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/186947]]
+
+#patch-for-review",1422359801,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",@Cmcmahon can you do a code review for this change?,1422094796,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 179072 had a related patch set uploaded (by Physikerwelt):
+Refactor code for RSpec3 expect syntax incorporation
+
+[[https://gerrit.wikimedia.org/r/179072]]
+
+#patch-for-review",1418281843,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 146712 abandoned by Jagori79:
+WIP [BrowserTest] Use rspec-expectations expect syntax instead of should syntax
+
+Reason:
+I am abandoning this change as already been implemented for Visual Editor.I will make the expect syntax changes on other codebase as suggested by Chris on the QA mailing list.
+
+[[https://gerrit.wikimedia.org/r/146712]]",1417655722,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Thanks,Yes,will work on the other repositories.",1417091501,PHID-USER-t4rpicnsgzxayalzj6k6,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","If the change you were working on is already implemented, it probably makes sense to abandon your commit. We have plenty of other repositories where the change should be implemented. :)
+
+https://github.com/wikimedia/mediawiki-selenium#links",1416995330,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Zeljko:I see the changes already implemented for Visual editor code,should I abandon the part which I was working on :https://gerrit.wikimedia.org/r/#/c/146712/
+
+I had restored it .",1416908094,PHID-USER-t4rpicnsgzxayalzj6k6,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 146712 restored by Jagori79:
+WIP [BrowserTest] Use rspec-expectations expect syntax instead of should syntax
+
+Reason:
+Restoring
+
+[[https://gerrit.wikimedia.org/r/146712]]",1416907322,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 146712 abandoned by Zfilipin:
+WIP [BrowserTest] Use rspec-expectations expect syntax instead of should syntax
+
+Reason:
+No activity on the commit in months. Please restore if you plan to work on this.
+
+https://gerrit.wikimedia.org/r/146712",1415097965,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 147423 merged by jenkins-bot:
+Use rspec-expectations expect syntax instead of should syntax
+
+https://gerrit.wikimedia.org/r/147423",1405696369,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 147423 had a related patch set uploaded by Zfilipin:
+Use rspec-expectations expect syntax instead of should syntax
+
+https://gerrit.wikimedia.org/r/147423",1405685794,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","Change 146712 had a related patch set uploaded by Jagori79:
+WIP [BrowserTest] Use rspec-expectations expect syntax instead of should syntax
+
+https://gerrit.wikimedia.org/r/146712",1405498000,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","(In reply to Željko Filipin from comment #1)
+> Pick a repository:
+> 
+> https://github.com/wikimedia/mediawiki-selenium#links
+> 
+> Replace all expect syntax with should syntax.
+
+  Editing the above line to :
+   > Replace all should syntax with expect syntax.",1402752239,PHID-USER-t4rpicnsgzxayalzj6k6,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax","@Zeljko: I am not able to assign the bug to myself.Could you please look into it.
+I cannot see the ""Edit"" link.",1402562879,PHID-USER-t4rpicnsgzxayalzj6k6,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",,1443640356,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+"Use rspec-expectations ""expect"" syntax instead of ""should"" syntax",,1402321835,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-47y76ef6fmsctze6gbby,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"We should have a sane way of including screenshots with skins and displaying them in the UI. These would be useful on Special:Preferences, in the installer when it will ask you which skin to choose, on Special:Version…
+
+I coded up something that works but is probably not a good idea at https://gerrit.wikimedia.org/r/#/c/138110/ – this would just add support for a new key to $wgExtensionCredits.
+
+One interesting issue is, what resolution should we expect the screenshot to be?
+
+Another one is, how do we display it? Unless we want to push the whole thing through ResourceLoader CSS handling (which would be extremely silly), we need to know the URL path where the screenshot is available (relative to $wgStylePath?). This is not obvious :(
+
+**See Also**: {T70331}
+
+----
+
+**The new convention**:
+* Every skin can include screenshots in the screenshots/ directory, which will be shown in the installer (and possibly elsewhere in the future).
+* It should include at least one 1280x800px screenshot, plus any extra screenshots if your skin looks different at different screen resolutions or with different configuration options.
+* You should disable any extensions or uncommon configuration options when taking the screenshots.
+* Make sure not to include any copyrighted content in the screenshots – here's some public domain content you can use:
+** Page content: P5878
+** Site logo: the MediaWiki logo (`$wgLogo = ""/w/resources/assets/mediawiki.png"";`)
+** Images: [[https://commons.wikimedia.org/wiki/File:Turner,_J._M._W._-_The_Fighting_Téméraire_tugged_to_her_last_Berth_to_be_broken_(edit).jpg|1]] [[https://commons.wikimedia.org/wiki/File:Bierstadt_Albert_Indian_Summer_Hudson_River.jpg|2]] [[https://commons.wikimedia.org/wiki/File:Meisje_met_de_parel.jpg|3]]
+**Examples**:
+{F9028486,float} {F9028461,float} {F9028439,float}
+
+----",1402099020,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_description,resolved
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"No. I almost did it, but to upload them there, you'd have to find out the right license for every single one separately, and that was more effort than I was willing to put into it. The skins can each have different licenses, they're not all on GPL like MediaWiki.",1512230552,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"This task has been pointed from {T179709}, where we are trying to take screenshots of skins that doesn't have one yet in their mediawiki.org skin page. Have the pictures taken during the work done for this task been inserted on mw.org?",1512169724,PHID-USER-aswxykknolbbycawydkz,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"It would be good to write this up as a seleniumJS script (see VisualEditor/build/screenshots.js), because skins change.",1502651765,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,Also documented at https://www.mediawiki.org/wiki/Manual:Skinning_Part_2#Screenshots,1502485233,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"With these patches merged, 24 skins out of 42 in our version control have screenshots.
+
+The others ones are read-only repos, immediately fatal when enabled, don't seen to have any styles at all, or have other big problems.
+
+| Skin | Status |
+| -- | -- |
+| apex | {icon check, color=green}
+| Athena | 
+| Blueprint | 
+| BlueSky | {icon check, color=green}
+| BlueSpiceSkin | 
+| Bouquet | {icon check, color=green}
+| CologneBlue | {icon check, color=green}
+| CustomPage | 
+| Daddio | {icon check, color=green}
+| DeskMessMirrored | {icon check, color=green}
+| Dusk | {icon check, color=green}
+| DuskToDawn | 
+| Empty | 
+| erudite | {icon check, color=green}
+| Example | {icon check, color=green}
+| Gamepress | 
+| GreyStuff | {icon check, color=green}
+| HasSomeColours | 
+| Mask | {icon check, color=green}
+| Material | 
+| mediawiki-strapping | 
+| Metrolook | {icon check, color=green}
+| MinervaNeue | {icon check, color=green}
+| Modern | {icon check, color=green}
+| MonoBook | {icon check, color=green}
+| Nimbus | {icon check, color=green}
+| Nostalgia | {icon check, color=green}
+| p2wiki | 
+| Poncho | 
+| Refreshed | 
+| Schulenburg | 
+| Splash | {icon check, color=green}
+| Synagonism | 
+| Tempo | {icon check, color=green}
+| Timeless | {icon check, color=green}
+| Tomas | 
+| Truglass | {icon check, color=green}
+| Vector | {icon check, color=green}
+| VectorV2 | 
+| webplatform | {icon check, color=green}
+| WoOgLeShades | 
+| WPtouch | {icon check, color=green}
+",1502482673,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371548 merged by jenkins-bot:
+[mediawiki/skins/Timeless@master] Add skin screenshots for the installer
+
+[[https://gerrit.wikimedia.org/r/371548]]
+",1502482195,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371537 merged by jenkins-bot:
+[mediawiki/skins/MonoBook@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371537]]
+",1502481680,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371538 merged by jenkins-bot:
+[mediawiki/skins/Nimbus@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371538]]
+",1502481679,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371539 merged by jenkins-bot:
+[mediawiki/skins/Nostalgia@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371539]]
+",1502481678,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371540 merged by jenkins-bot:
+[mediawiki/skins/Splash@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371540]]
+",1502481561,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371541 merged by jenkins-bot:
+[mediawiki/skins/Tempo@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371541]]
+",1502481560,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371542 merged by jenkins-bot:
+[mediawiki/skins/Truglass@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371542]]
+",1502481557,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371544 merged by jenkins-bot:
+[mediawiki/skins/webplatform@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371544]]
+",1502481545,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371545 merged by jenkins-bot:
+[mediawiki/skins/WPtouch@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371545]]
+",1502481489,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371546 merged by jenkins-bot:
+[mediawiki/skins/GreyStuff@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371546]]
+",1502481384,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371536 merged by jenkins-bot:
+[mediawiki/skins/Modern@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371536]]
+",1502481383,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371534 merged by jenkins-bot:
+[mediawiki/skins/Metrolook@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371534]]
+",1502481297,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371530 merged by jenkins-bot:
+[mediawiki/skins/Dusk@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371530]]
+",1502481204,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371529 merged by jenkins-bot:
+[mediawiki/skins/DeskMessMirrored@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371529]]
+",1502481201,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371528 merged by jenkins-bot:
+[mediawiki/skins/Daddio@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371528]]
+",1502481173,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371527 merged by jenkins-bot:
+[mediawiki/skins/CologneBlue@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371527]]
+",1502481172,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371526 merged by jenkins-bot:
+[mediawiki/skins/Bouquet@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371526]]
+",1502481171,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371548 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Timeless@master] Add skin screenshots for the installer
+
+[[https://gerrit.wikimedia.org/r/371548]]
+",1502481037,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371533 merged by jenkins-bot:
+[mediawiki/skins/Mask@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371533]]
+",1502481012,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371532 merged by jenkins-bot:
+[mediawiki/skins/Example@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371532]]
+",1502480942,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371531 merged by jenkins-bot:
+[mediawiki/skins/erudite@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371531]]
+",1502480856,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371543 merged by jenkins-bot:
+[mediawiki/skins/Vector@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371543]]
+",1502480855,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371535 merged by jenkins-bot:
+[mediawiki/skins/MinervaNeue@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371535]]
+",1502480731,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371546 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/GreyStuff@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371546]]
+",1502480464,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371545 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/WPtouch@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371545]]
+",1502480286,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371544 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/webplatform@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371544]]
+",1502480273,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371543 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Vector@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371543]]
+",1502480260,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371542 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Truglass@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371542]]
+",1502480252,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371541 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Tempo@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371541]]
+",1502480240,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371540 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Splash@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371540]]
+",1502480228,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371539 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Nostalgia@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371539]]
+",1502480215,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371538 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Nimbus@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371538]]
+",1502480206,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371537 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/MonoBook@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371537]]
+",1502480188,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371536 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Modern@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371536]]
+",1502480179,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371535 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/MinervaNeue@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371535]]
+",1502480171,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371534 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Metrolook@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371534]]
+",1502480158,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371533 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Mask@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371533]]
+",1502480146,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371522 merged by jenkins-bot:
+[mediawiki/skins/BlueSky@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371522]]
+",1502480131,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371532 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Example@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371532]]
+",1502480127,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371531 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/erudite@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371531]]
+",1502480119,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371530 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Dusk@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371530]]
+",1502480106,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371529 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/DeskMessMirrored@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371529]]
+",1502480094,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371525 abandoned by Bartosz Dziewoński:
+Add skin screenshot for the installer
+
+Reason:
+Whoops, duplicate.
+
+[[https://gerrit.wikimedia.org/r/371525]]",1502480085,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371528 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Daddio@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371528]]
+",1502480083,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371524 abandoned by Bartosz Dziewoński:
+Add skin screenshot for the installer
+
+Reason:
+Whoops, duplicate.
+
+[[https://gerrit.wikimedia.org/r/371524]]",1502480079,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371527 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/CologneBlue@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371527]]
+",1502480074,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371521 merged by jenkins-bot:
+[mediawiki/skins/apex@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371521]]
+",1502480057,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371526 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/Bouquet@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371526]]
+",1502480056,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371525 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/BlueSky@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371525]]
+",1502480050,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371524 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/apex@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371524]]
+",1502480002,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371522 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/BlueSky@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371522]]
+",1502479669,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Change 371521 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/skins/apex@master] Add skin screenshot for the installer
+
+[[https://gerrit.wikimedia.org/r/371521]]
+",1502479593,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,<3,1502474625,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"| MinervaNeue | {F9036540} | {F9036540,layout=link}",1502474050,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,@matmarex probably needs MobileFrontend to be installed. It's still a bit weird in that way. :(,1502466933,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"I tried to include it, but it's shown me some error message so I skipped it. Maybe I'll look at it again later and try to actually read what the error says. I don't think it's a major problem if it's inconsistent; I won't be taking screenshots of all skins forever so they will soon enough become inconsistent anyway.",1502466327,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,Can #MinervaNeue get in on the screenshot  action? I cam generate one but it's  likely to be inconsistent..,1502461519,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,You're awesomeeeee <3,1502422602,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"Here are 24 screenshots for all the skins in our version control that I could effortlessly get to work and that did not have obvious huge rendering issues. They're at 1280x800px.
+
+All of the content on the screenshots is in the public domain:
+* The textual content is just a lot of copy-paste of Lorem ipsum: P5878
+* The site logo (where shown) is the MediaWiki logo (`$wgLogo = ""/w/resources/assets/mediawiki.png"";`)
+* The images are classic art ([[https://commons.wikimedia.org/wiki/File:Turner,_J._M._W._-_The_Fighting_Téméraire_tugged_to_her_last_Berth_to_be_broken_(edit).jpg|1]] [[https://commons.wikimedia.org/wiki/File:Bierstadt_Albert_Indian_Summer_Hudson_River.jpg|2]] [[https://commons.wikimedia.org/wiki/File:Meisje_met_de_parel.jpg|3]])
+
+I'm going to commit these to the repos, and upload them to Commons, later (or tomorrow).
+
+| apex | {F9028408} | {F9028408,layout=link} |
+| Blueprint | {F9028411} | {F9028411,layout=link} |
+| BlueSky | {F9028404} | {F9028404,layout=link} |
+| Bouquet | {F9028414} | {F9028414,layout=link} |
+| CologneBlue | {F9028412} | {F9028412,layout=link} |
+| Daddio | {F9028423} | {F9028423,layout=link} |
+| DeskMessMirrored | {F9028449} | {F9028449,layout=link} |
+| Dusk | {F9028426} | {F9028426,layout=link} |
+| erudite | {F9028422} | {F9028422,layout=link} |
+| Example | {F9028429} | {F9028429,layout=link} |
+| GreyStuff | {F9028433} | {F9028433,layout=link} |
+| Mask | {F9028436} | {F9028436,layout=link} |
+| Metrolook | {F9028435} | {F9028435,layout=link} |
+| Modern | {F9028439} | {F9028439,layout=link} |
+| MonoBook | {F9028462} | {F9028462,layout=link} |
+| Nimbus | {F9028468} | {F9028468,layout=link} |
+| Nostalgia | {F9028465} | {F9028465,layout=link} |
+| Splash | {F9028475} | {F9028475,layout=link} |
+| Tempo | {F9028466} | {F9028466,layout=link} |
+| Timeless | {F9028461} | {F9028461,layout=link} |
+| Truglass | {F9028482} | {F9028482,layout=link} |
+| Vector | {F9028486} | {F9028486,layout=link} |
+| webplatform | {F9028483} | {F9028483,layout=link} |
+| WPtouch | {F9028485} | {F9028485,layout=link} |
+",1502422314,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,Change https://gerrit.wikimedia.org/r/371080 (fd8d75c1fd26e9ca0976111f1b3861935a53f84b) makes this possible. I guess we should take a bunch of screenshots and include them now? :o,1502394934,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"A full preview sounds a bit sketchy on the site, but would it potentially be possible to do the full preview somewhere else? Have a screenshot available with the skin, also have an optional link to a testwiki preview (like maybe just set up an entire toollabs wiki or whatever you call it for that)... this wouldn't cover all skins, but for ones included with the tarball and even in gerrit and crap it would be pretty straight forward to set up.
+
+Would be a bit harder to maintain, though.",1443459705,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"We wouldn't want it to get too complicated, both on the admin and on the user end, but I dunno.
+
+If nothing else, having a small thumbnail just so there's something visual at all would certainly be useful, but we can't expect the thumbnail/screenshot to do much beyond that. So... er... there should be both. We should have both things - a more immediate preview mechanism, and a small thumbnail for initial eye-catching and later locating in the list.",1403463945,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"I actually agree with Isarra somewhat - a preview is better than a screenshot. That said the current experience is terrible. Previewing the preference page for one makes no sense - it would be far better to see something in the main namespace rendered via the chosen skin.
+
+Tumblr does a great job in its theme interface. You can select and search for skins and they instantly get applied so it's easy to flick between them and see the skin in the context of an ipsum lorem article.
+
+This could be a great opportunity to break skins out of Special:Preferences - maybe Special:Preferences/Skin and just provide a good simple interface for skin switching - maybe a drop down at the top and an Ipsum lorem article rendered below. When we have templating in core we could even do this rendering via JavaScript :-).",1403463675,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+Come up with a sane way of including screenshots with skins and displaying them in the UI,"What's wrong with ?useskin? 
+
+Except in the installer. That would need something fancier, or something. Unless there'd be some way to safely automatically include them temporarily for preview... er...
+
+I don't know where I was going with that.",1402125627,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-ro4iqgaoik67vus6rg36,task_subcomment,NA
+VisualEditor: Citation dialog changes title after opening,"1. Click Cite -> Newspaper
+2. A dialog opens; while it's opening, the title is ""Newspaper""
+3. Once it finishes opening, the title changes to ""Cite news""
+
+This is more visible on a slower system or with an artificially lengthened opening animation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1401752160,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mlrh4edb5aomh7cflcn2,task_description,open
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it","Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Click somewhere outside the page where the VE toolbar will get disabled
+4.Now click on the image.
+
+Observed Result:
+Clicking on the image tries to select the image first then cursor moves to the beginning of the document.
+
+Environment :Betalabs
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1401300060,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xbd775tm7a2kficmtwfv,task_description,resolved
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it",Verified the fix in en.wiki running wmf 8,1402684945,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it",Verified the fix in Betalabs and test2,1402344939,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it","Change 136013 merged by jenkins-bot:
+Don't fix selection on document focus if focusedNode is set
+
+https://gerrit.wikimedia.org/r/136013",1401391092,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it","Change 136013 had a related patch set uploaded by Esanders:
+Don't fix selection on document focus is focusedNode is set
+
+https://gerrit.wikimedia.org/r/136013",1401365615,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+"VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it","Created attachment 15500
+video capture of the bug
+
+**Attached**: {F13645}",1401300263,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-xbd775tm7a2kficmtwfv,task_subcomment,NA
+VisualEditor: Undo/redo should not (?) remain active when surface is blurred,"Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to the Media Settings dialog of the image
+4.Type something in the caption field
+5.Now place the cursor in the Alternative Test field
+6.Observe that, the ""Undo"" button in the toolbar is still active
+7.Click on the undo button
+
+Observed Result:
+It clears the text inside the caption field , this is a bit confusing , since the cursor was pointing to text inside Alternative Text and but it started clearing out the content inside caption field.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400887980,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3bxysrz3mthjheir6p4n,task_description,declined
+VisualEditor: Undo/redo should not (?) remain active when surface is blurred,"This is because the undo and redo buttons remain active when the surface is blurred. I know this is intentional, but maybe it should be revisited.",1401303039,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-3bxysrz3mthjheir6p4n,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"**Author:** `wiki.nihiltres`
+
+**Description:**
+I noticed today that dialogs are delayed or fail to work some of the time in VE, using Safari 5.1.10 on Mac OS 10.6.8. The first click on a button that produces a dialog, or first few clicks, don't seem to do anything, but clicking on the button a while later has the normal effect, suggesting something's taking a while to load.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**OS**: Mac OS X 10.6
+**Platform**: Macintosh",1400793900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gmtmxwco32y632mfebna,task_description,resolved
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Patch merged; assuming this is fixed / worked around by greylisting. If not, please reopen.",1583082370,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Change 135154 merged by jenkins-bot:
+Move Safari 5.x to greylist because dialogs aren't working well
+
+https://gerrit.wikimedia.org/r/135154",1400902028,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Change 135154 had a related patch set uploaded by Jforrester:
+Move Safari 5.x to greylist because dialogs aren't working well
+
+https://gerrit.wikimedia.org/r/135154",1400891973,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Yes, Confirmed on MAC OSX 10.6 and Safari 5.1. This is happening while opening any dialog for the first time , it does not open even if I try clicking on it multiple times, once I clicked on some other buttons from the toolbar both the dialogs open at the same time",1400890916,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?),"Odd. Rummana, can you test this and confirm behaviour?",1400794112,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gmtmxwco32y632mfebna,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Steps to reproduce:
+
+1.  Open any page that contains the {{coord}} template on en.wp  See, e.g., https://en.wikipedia.org/wiki/Harton,_North_Yorkshire 
+
+
+Results:
+
+The coordinates template, which should be in the top right corner, displays in the far left—so far to the left that only the last few characters are visible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400782860,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_description,open
+VisualEditor:  Coordinates template is displaying in the wrong place,"The previous comments don't explain who or what (task?) exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status, as tasks should not be stalled (and then potentially forgotten) for six years for unclear reasons.
+
+//(Smallprint, as general orientation for task management:
+If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead.
+If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}.
+If this task is stalled on an upstream project, then the #upstream tag should be added.
+If this task requires info from the task reporter, then there should be instructions which info is needed.
+If this task needs retesting, then the #testme tag should be added.
+If this task is out of scope and nobody should ever work on this, or nobody else managed to reproduce the situation described here, then it should have the ""Declined"" status.
+If the task is valid but should not appear on some team's workboard, then the team project tag should be removed while the task has another active project tag.)//
+",1604263405,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,Just FYI to Chris!,1522080495,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,">>! In T67648#4080803, @matmarex wrote:
+>>>! In T67648#4079369, @TheDJ wrote:
+>> %%% this will move the coordinates from below the H2 line to above it.. I expect resistance :)
+> 
+> You can still keep the `position: absolute; ...` for `<span id=""coordinates"">` if preserving the exact positioning is required, even when it's in an indicator.
+
+Good point, i'll see about experimenting with that somewhere this week.",1522075465,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,">>! In T67648#4079369, @TheDJ wrote:
+> %%% this will move the coordinates from below the H2 line to above it.. I expect resistance :)
+
+You can still keep the `position: absolute; ...` for `<span id=""coordinates"">` if preserving the exact positioning is required, even when it's in an indicator.",1522075391,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"For now https://en.wikipedia.org/w/index.php?title=MediaWiki:Monobook.css&diff=832362097&oldid=813457383 and https://en.wikipedia.org/w/index.php?title=MediaWiki:Vector.css&diff=832362332&oldid=813450031 less problematic, without the need to resort to moving it.
+
+@Jc86035 BTW. it can already use Kartographer (some wiki's do, and i think en.wp even has a sandbox version of it). But i'm not wasting my precious free time on weeks of discussion with the princesses to convince them to switch.",1521991082,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"If resistance would be an issue (and I think that's not unlikely), I think it would be better to wait for Community Tech to convert the module to use Kartographer, since GeoHack would then not be needed for coordinates on Earth. Then any visual change as a result of changing the GeoHack styling would affect far fewer pages.",1521989181,PHID-USER-zcjbttnvrligppi7hwnx,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"If resistance would be an issue (and I think that's not unlikely), I think it would be better to wait for Community Tech to convert the module to use Kartographer, since GeoHack would then not be needed for coordinates on Earth. Then any visual change would effect far fewer pages.",1521989156,PHID-USER-zcjbttnvrligppi7hwnx,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,this will move the coordinates from below the H2 line to above it.. I expect resistance :),1521988912,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"I don't know Lua, but I think something like [[https://en.wikipedia.org/w/index.php?diff=832258813&oldid=819658303|this]] might do it. See [[https://en.wikipedia.org/wiki/Module_talk:Coordinates#Convert_to_indicator|Module talk:Coordinates#Convert to indicator]].",1521926075,PHID-USER-32xfxqjy2iw66kf33xjy,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"More precisely, updating that scary template is something that I think a technically competent person, e.g., @Jc86035 @MaxSem @TheDJ or @JJMC89, should look into.  `:-)`",1521828281,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,@Whatamidoing-WMF is this something you'd like to look into?,1521819544,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Yes, the best solution here is for the English Wikipedia community to change {{Coord}} in that way. On its face this looks like a simple change, but this is a widely-used and complicated template, so some care will no doubt be needed. Any gadgets or tools depending on the output of this template may also need to be updated (e.g. the map popup). I don't think it is feasible to solve this on the VE side (and we won't need to do anything if the template is changed).",1521662847,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,">>! In T67648#4066986, @matmarex wrote:
+> Just for reference, since this task doesn't have a screenshot, here's how it currently looks: {F15921704}
+> 
+> VisualEditor does its best attempt to position the template where requested by the CSS (`position: absolute; top: 0; right: 0;`), but for boring technical reasons (""stacking contexts"") it can't escape the editing surface: {F15921712}
+> 
+> English Wikipedia should migrate the {{Coord}} template to use the `<indicator>` parser tag to position it in the top-right corner (see https://www.mediawiki.org/wiki/Help:Page_status_indicators). Many other templates there already use it, for example everything derived from [[ https://en.wikipedia.org/wiki/Template:Top_icon | {{Top icon}} ]]. VisualEditor will display such templates as if they were invisible (like e.g. [[ https://en.wikipedia.org/wiki/Template:Use_British_English | {{Use British English}} ]]), with a greyed-out puzzle icon and template name.
+> 
+> {F15921725}
+
+So, are we saying that the solution here is a simple recommendation to the community, or is there anything we technically would need to implement on our side? TY.",1521635636,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Just for reference, since this task doesn't have a screenshot, here's how it currently looks: {F15921704}
+
+VisualEditor does its best attempt to position the template where requested by the CSS (`position: absolute; top: 0; right: 0;`), but for boring technical reasons (""stacking contexts"") it can't escape the editing surface: {F15921712}
+
+English Wikipedia should migrate the {{Coord}} template to use the `<indicator>` parser tag to position it in the top-right corner (see https://www.mediawiki.org/wiki/Help:Page_status_indicators). Many other templates there already use it, for example everything derived from [[ https://en.wikipedia.org/wiki/Template:Top_icon | {{Top icon}} ]]. VisualEditor will display such templates as if they were invisible (like e.g. [[ https://en.wikipedia.org/wiki/Template:Use_British_English | {{Use British English}} ]]), with a greyed-out puzzle icon and template name.
+
+{F15921725}",1521585347,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Yes, this is because we give the document padding instead of margin to make the margins clickable.",1442587966,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Today in (try here: https://en.wikipedia.org/wiki/Burpengary_Creek?veaction=edit ) it is on the far right, so far right that there is no margin between the final character and the scrollbar, as Elitre described.  However, it's also one line too low, which means that it makes the last few words of the first paragraph very difficult to read.
+
+",1438972845,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"I tried as well, and what happens for me in FF and Chrome is that the template moves completely to the right and there is no margin between the E and the scrollbar.",1425652624,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"Cannot reproduce the problem anymore on https://en.wikipedia.org/wiki/Harton,_North_Yorkshire?veaction=edit even after hovering over the Coord template and clicking it. Same for Quiddity's other two links. Coord stays on the right where it belongs in Firefox 36 on Fedora 21.
+
+Should this task be closed as resolved / declined?",1425489265,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor:  Coordinates template is displaying in the wrong place,"The above example is still basically the same. Possibly different, is that the template only moves to the far-left *after* I mouseover the template. (Firefox and Chrome).
+
+However, at other articles, it moves to different places. 
+e.g. https://en.wikipedia.org/wiki/Happy_Valley,_Victoria after I mouseover the link, it moves downwards by ~1cm, so that it overlaps the infobox.
+e.g.2. https://en.wikipedia.org/wiki/Happy_Valley,_South_Australia after I mouseover the template, it moves to the far-left, but also far-down the page (underneath the ==References== section).",1403198616,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-lzzge4gnm7o6yqjh7rmy,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"This is related to T52855 about parser functions and magic words.
+
+When I have a sentence on a page like this:
+
+   Choose the ""{{int:visualeditor-dialogbutton-reference-tooltip}}"" item in the ""{{int:visualeditor-toolbar-insert}}"" menu. 
+
+I want to be able to:
+
+(1) copy and paste; 
+(2) edit; and
+(3) create
+
+the {{int:foo}} parts.  
+
+Right now, I can only copy them for re-use elsewhere on the page if I select a bigger block of text (so ""{{int:visualeditor-toolbar-insert}}"", but not just {{int:visualeditor-toolbar-insert}}).
+
+I can't edit them at all; it's an uneditable alienated text block.  Given the long strings of similar names for some of these items, it would be really handy to be able to copy and paste something like {{int:visualeditor-toolbar-insert}} and only need to change the ""insert"" bit to ""cite-label"", or to fix a typo in the name.
+
+It would also be nice to have a sensible system for creating these things.  At the moment, it can only be done through this sequence:  Insert > Template, ""Other options"", Content, type in the wikitext, and Insert transclusion. 
+
+However, my main concern is just being able to edit existing ones.",1400780640,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_description,resolved
+VisualEditor: Support editing {{int:name}} blocks,"@Whatamidoing-WMF, I'm sure it's //possible//, but generally we shouldn't introduce behavioral inconsistencies without a good reason. Whatever the decision on changing the name of a  transclusion is, it should probably apply to all types of transclusions. ",1438369981,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"I believe that has already been filed and declined for templates, although I can't find it.  Do you want to handle transcluded magic words and the like differently from transcluded templates?  (Is that even feasible?)",1438367554,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"@Whatamidoing-WMF, fair point. Do you want to file a separate task for changing the name of an existing transclusion?",1438203212,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"It is still not possible to edit them, e.g., to fix a typo.  You have to delete them and re-create them.  This is perhaps not surprising, since you can't fix a typo in a template name, either.",1438120805,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,">Update: I can insert parser functions by adding a ""template"" named (for example) ""int:vector-view-edit"". It says there's no TemplateData, but it adds it.
+
+Given that it's now possible to easily transclude and move interface messages, I'm closing this. I've opened T106755 for the low-priority challenge of making it more user-friendly.",1437690670,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+VisualEditor: Support editing {{int:name}} blocks,"Update:  I can insert parser functions by adding a ""template"" named (for example) ""int:vector-view-edit"".  It says there's no TemplateData, but it adds it.",1405532364,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-k5kojkbwzvqt4d36hrd3,task_subcomment,NA
+"Move the reference, reference list and citation systems into the Cite extension's repo","I spent a lot of time wondering why my citations were not rendering properly.
+
+VisualEditor shows a cite menu which behaves strangely if the Cite extension not enabled.
+
+Should this throw an error or not show the citation tool when the Cite extension is not installed?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400766240,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-njmo4dxth5kyk5lgw2it,task_description,duplicate
+"Move the reference, reference list and citation systems into the Cite extension's repo",Well technically we should move all the reference code to the Cite extension...,1416784874,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-njmo4dxth5kyk5lgw2it,task_subcomment,NA
+"Move the reference, reference list and citation systems into the Cite extension's repo","Yeah, this is a bit of a crummy situation. We should fix this.",1400775918,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-njmo4dxth5kyk5lgw2it,task_subcomment,NA
+Serializing images without data-parsoid normalizes image names incorrectly,"If you parse wikitext like `[[File:Ulmer M?nster-1024409.jpeg|frame]]` , Parsoid will produce a <figure> structure with href=""./File:Ulmer_M%3Fnster-1024409.jpeg"" (which is correct, the question mark is urlencoded) and resource=""./File:Ulmer_M%3Fnster-1024409.jpeg"" (not sure whether this is correct).
+
+When VisualEditor takes this information to build an inline image equivalent (taking the href and the resource, and dropping everything else including data-parsoid) we get [[File:Ulmer_M%3Fnster-1024409.jpeg|link=]] back. Note the space changed to an underscore and ? changed to %3F. There was information in data-parsoid to keep this from happening, but in this transformation VE discards it.
+
+```
+$ echo '[[File:Ulmer M?nster-1024409.jpeg|frame]]' | node tests/parse.js --apiURL=http://localhost/w/api.php
+<!DOCTYPE html>
+<html prefix=""dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/""><head prefix=""mwr: http://localhost/wiki/Special:Redirect/""><meta property=""mw:parsoidVersion"" content=""0""/><link rel=""dc:isVersionOf"" href=""//localhost/wiki/Main_Page""/><title></title><base href=""//localhost/wiki/Main_Page""/></head><body data-parsoid='{""dsr"":[0,42,0,0]}'><figure class=""mw-default-size"" typeof=""mw:Image/Frame"" data-parsoid='{""optList"":[{""ck"":""framed"",""ak"":""frame""}],""dsr"":[0,41,2,2]}'><a href=""./File:Ulmer_M%3Fnster-1024409.jpeg"" data-parsoid='{""a"":{""href"":""./File:Ulmer_M%3Fnster-1024409.jpeg""},""sa"":{},""dsr"":[2,39,null,null]}'><img resource=""./File:Ulmer_M%3Fnster-1024409.jpeg"" src=""//localhost/w/images/f/f1/Ulmer_M%3Fnster-1024409.jpeg"" height=""1024"" width=""764"" data-parsoid='{""a"":{""resource"":""./File:Ulmer_M%3Fnster-1024409.jpeg"",""height"":""1024"",""width"":""764""},""sa"":{""resource"":""File:Ulmer M?nster-1024409.jpeg""}}'/></a></figure>
+</body></html>
+
+$ echo '<p><span typeof=""mw:Image"" class=""mw-default-size""><span><img src=""//localhost/w/images/f/f1/Ulmer_M%3Fnster-1024409.jpeg"" resource=""./File:Ulmer_M%3Fnster-1024409.jpeg"" width=""764"" height=""1024""></span></span></p>' | node tests/parse.js --html2wt
+[[File:Ulmer_M%3Fnster-1024409.jpeg|link=]]
+```
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400706840,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-fscihqnuuufaxytwhfkf,task_description,open
+Serializing images without data-parsoid normalizes image names incorrectly,This is a low-priority issue since Parsoid has access to data-parsoid always via the old HTML (either explicitly reparsed or via RESTBase).,1583899287,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-fscihqnuuufaxytwhfkf,task_subcomment,NA
+Serializing images without data-parsoid normalizes image names incorrectly,It looks like we aren't percent-decoding & underscore-removing the resource properly in the serializer. This also seems to be the case for block images.,1401305509,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-fscihqnuuufaxytwhfkf,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,"1. go to article on en.m.wiki
+2. invoke WTE type characters
+3. shake phone, [undo/cancel] dialog is displayed
+4. choose undo
+
+expected : typed characters should be removed
+actual : typing is not undone
+
+5. once undo works, shaking phone again should trigger [redo/cancel] which should restore undone action.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400704140,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-o53zljq5pyonvqfryedx,task_description,resolved
+iOS: Shake to undo on mobile does not undo or redo typing,"Just testing on iphone, and ipad, in VE and WTE, issue is no longer present. closing. ",1418251044,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,@Jaredzimmerman-WMF Works for me. Tested in Mobile Safari on iPhone.,1418250424,PHID-USER-a5pveeqqwaddgfjiv2fq,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,@Jdforrester-WMF this behaviour should be supported by both editors on mobile devices which support this gesture. Its isn't actually WTE specific. ,1418163852,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,What about #VisualEditor is there to do on this task?,1418163380,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,"@Jdlrobson why is this non-actionable, can you please comment as to what is needed to unblock this?  ",1418160265,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,WikiTextEditor (e.g. not VE),1402524590,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,"**jgonera** wrote:
+
+What is WTE?",1402524550,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,If you didn't mean to shake the OS already shows a dialog with [undo/cancel] this is a standard part of the OS that you can't turn off.,1400707709,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,(Also what happens if I didn't mean to shake...? - happens to me all the time - had to disable it in Google Maps),1400705249,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,Please talk to Maryana about scheduling and prioritizing this feature request.,1400705221,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+iOS: Shake to undo on mobile does not undo or redo typing,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/pNCKv65l",1400704222,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-o53zljq5pyonvqfryedx,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,It's impossible to create a new page / new content without this. :-(,1400686140,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_description,open
+VisualEditor Mobile: Allow formatting editing,"Terminology. Bah.
+
+Well, yeah, those are missing. It's an open question whether we really want to support article creation in the short term over other use cases, but that's a different discussion...",1535400949,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,">>! In T67586#4535966, @Deskana wrote:
+> Formatting (e.g. bold, italics) can be added and edited in the mobile visual editor. Am I misunderstanding this task, or is it just so old that these features didn't exist back then?
+
+This is about formatting (headings), not styling (bold, italics). You can't make an article without being able to make sections (not least, a references section).",1535400395,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,"Formatting (e.g. bold, italics) can be added and edited in the mobile visual editor. Am I misunderstanding this task, or is it just so old that these features didn't exist back then?",1535400306,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,Just that - finding a place for it to go.,1439141540,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,What else do we need to do here other than add the formatting menu to MobileViewTarget?,1430597202,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor Mobile: Allow formatting editing,"**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/5i7pUTTK",1400692790,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-qunjidjpc6zmzxdvlfx7,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"Quora has a lovely feature in its visual editor: paste a URL and it's immediately and automatically converted in a smart way.
+
+* If it's a link to another answer on Quora, it is given an appropriate title.
+* If it's a link to YouTube, the video is embedded.
+* If it's a link to some other website, the page's HTML <title> is inserted and automatically linked. (There may be other special cases, but you get the idea.)
+
+After the link is thus inserted, the user can edit the text or click another button to make the actual URL appear or to make the URL just plain text.
+
+I'd love such a feature in VE. It's especially relevant for newbies who link to other Wikipedia articles with full http links as if they were external. For external links, getting the title automatically is usually better than having a plain URL (in fact, there are some bots that automatically insert such titles). And pasting a Commons URL can embed the media as such.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400608680,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-twvr5rqlyoly5q6lv355,task_description,resolved
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"Pasting URLs now does sensible things, even converting to internal links when appropriate. Mostly thanks to work by @cscott.",1444743744,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"(In reply to Amir E. Aharoni from comment #4)
+> I meant not only external links, but pages in the same wiki, too. It's
+> anecdotal, but I see newbies adding http urls to other Wikipedia article
+> instead of using square brackets, and this should be DWIMmier.
+
+Those already get converted to internal (well, interwiki) links, though…",1415799211,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"I meant not only external links, but pages in the same wiki, too. It's anecdotal, but I see newbies adding http urls to other Wikipedia article instead of using square brackets, and this should be DWIMmier.",1415798449,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"Hmm. Right now we're taking newly-created external links and displaying them as auto-numbered link nodes; having this as a secondary mode to fetching the <title> could work, but… I'm not sure.",1414693734,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"This could potentially inform the VE UI for citoid;
+
+I.e. we could have have one reference dialog, (i.e. the basic reference dialog) and then if a user pastes a link *into* the reference dialog, that inserts the citation guessed from the link. And then keep the drop down menu for individual templates in the ref dialog.
+
+This does take some user discovery; however, I see this commonly being done with references already- i.e. a ref tag containing only an unformatted url. So it seems people are already just pasting links into the ref field and this is a natural enhancement of that work flow. 
+
+This, by the way, is what both G+ and Facebook do for links as well, not just Quora. So there may be already some user comfort with a pasted link becoming formatted in some fashion.",1414580483,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Automatically convert inserted URLs to readable formatted links,"Interesting idea. We've got some work planned to do this kind of thing for citations (you feed it a URL, it inserts a nice <ref>{{cite web|…}}</ref> block), and links to internal or interwiki targets get auto-converted on save (so [[:en:Foo|Bar]] not [https://en.wikipedia.org/wiki/Foo Bar]), but we don't do this for pasting into the surface. Maybe something we could do in the future?",1400609128,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-twvr5rqlyoly5q6lv355,task_subcomment,NA
+VisualEditor: Font is too small in dialogs in standalone VE,"Compare the keyboard shortcut help dialog (Ctrl+/) in the standalone demo vs the MW integration. The one in standalone has a smaller font size.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1400109240,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6qrknx6d4rhbi2dfof45,task_description,resolved
+VisualEditor: Font is too small in dialogs in standalone VE,Fixed in gerrit 141089.,1405375966,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6qrknx6d4rhbi2dfof45,task_subcomment,NA
+BetaFeatures: Provide an anchor link for each beta feature,"Add anchor links to each feature so that a user could send someone directly to a feature. For example, https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures#VisualEditor
+",1400101980,PHID-USER-flenunkasbjk4topxvaj,False,PHID-TASK-i5g7enpuggt3etks6uiw,task_description,open
+BetaFeatures: Provide an anchor link for each beta feature,"(In reply to Kaity Hammerstein from comment #0)
+> Add anchor links to each feature so that a user could send someone directly
+> to a feature. For example,
+> https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-
+> betafeatures#VisualEditor
+
+I don't think double anchors like that even work?
+
+In my patch the links are created like https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures-betafeatures-vector-compact-personal-bar
+
+Where ""betafeatures-vector-compact-personal-bar"" is the preference key used for the CPB BF in VectorBeta. So for VE it would be ""visualeditor-enable"".",1400136694,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-i5g7enpuggt3etks6uiw,task_subcomment,NA
+BetaFeatures: Provide an anchor link for each beta feature,"Change 133419 had a related patch set uploaded by Legoktm:
+Add an anchor for individual features
+
+https://gerrit.wikimedia.org/r/133419",1400136515,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-i5g7enpuggt3etks6uiw,task_subcomment,NA
+VisualEditor Mobile: The Link inspector icon remains highlighted in the toolbar for mobile VE even if no new link has been added,"Screenshot
+
+Steps to reproduce:
+
+1.Open a blank page with mobile VE
+2.Click on the link inspector icon
+3.Without adding any text just close the inspector
+
+Observed Result:
+The link inspector icon in the toolbar remains highlighted where as there is no link added in the CE
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13539}",1400097300,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-uktdpzihh2lhvffqgb4d,task_description,resolved
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Edit something
+3.Switch to edit source mode
+4.Save the page from edit source mode
+
+Observed Result:
+The message  ""The page has been restored"" appearing on top of the page instead of 
+""your edit was saved""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F14068}",1400002440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6qhvami4rv442prsl2cd,task_description,resolved
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there",Verified the fix in production,1400794695,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there",Verified the fix on test2,1400268685,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there",Verified the fix on Betalabs,1400103762,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there",Should be fixed now.,1400103339,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there","Change 133363 merged by jenkins-bot:
+Only send useful oldid while switching to wikitext editor if it's specifically requested
+
+https://gerrit.wikimedia.org/r/133363",1400103223,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+"VisualEditor: ""The page has been restored"" appearing on top of the page instead of ""your edit was saved"" after switching to edit source mode and saving the page from there","Change 133363 had a related patch set uploaded by Alex Monk:
+Only send useful oldid while switching to wikitext editor if it's specifically requested
+
+https://gerrit.wikimedia.org/r/133363",1400102777,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6qhvami4rv442prsl2cd,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"A ""Request desktop site"" option exists in Chrome and Firefox on Android, and maybe in some other browsers too.
+
+I believe what that option affects is just a user-agent string, and does not change other behaviors of the browser. However (for example in Firefox), with ""Request desktop site"" on, VisualEditor works happily, while with that option off, VisualEditor refuses to load.
+
+We should check whether VE actually works in these browsers, and have it whitelisted or blacklisted, regardless of whether that option is on or off.
+
+--------------------------
+**Version**: 1.24rc
+**Severity**: normal",1399982340,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_description,resolved
+jquery.client should support detecting Firefox Mobile,I think this was fixed in T101483. Please reopen if this is incorrect.,1599505179,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"If I understand correctly:
+* When users of Firefox Mobile use ""Request desktop site"", it uses a user agent header jQuery Client recognises as desktop Firefox. And VE supports that. And that browser supports VE. All is good.
+* When users of Firefox Mobile use the default mode, it uses a user agent header jQuery Client doesn't yet recognise properly (version=mobile). VE doesn't whitelist that. But it seems otherwise that browser would support VE.
+
+I'm not sure that working around the intentionally faked user-agent header will be feasible. It would leave us in a hard to maintain state.
+
+I'd recommend, instead:
+* jQuery Client should detect the name and version of Firefox Mobile properly.
+* VisualEditor whitelists Firefox Mobile (from that version and up).
+
+",1426117677,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"If I understand correctly:
+* When users of Firefox Mobile use ""Request desktop site"", it uses a user agent header jQuery Client recognises as desktop Firefox. And VE supports that. And that browser supports VE. All is good.
+* When users of Firefox Mobile use the default mode, it uses a user agent header jQuery Client doesn't yet recognise properly (version=mobile). VE doesn't whitelist that. But it seems otherwise that browser would support VE.
+
+I'm not sure that working around the intentionally faked user-agent header will be feasible and would leave us with a to maintain scenario.
+
+I'd recommend, instead:
+* jQuery Client should detect the version of Firefox Mobile properly.
+* VisualEditor whitelists Firefox Mobile (from that version and up).
+
+",1426117624,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"If I understand correctly:
+* When users of Firefox Mobile use ""Request desktop site"", it uses a user agent header jQuery Client recognises as desktop Firefox. And VE supports that. And that browser supports VE. All is good.
+* When users of Firefox Mobile use the default mode, it uses a user agent header jQuery Client doesn't yet recognise properly (version=mobile). VE does not support that. But it seems otherwise that browser would support VE.
+
+I'm not sure that working around the intentionally faked user-agent header will be feasible and would leave us with a to maintain scenario.
+
+I'd recommend, instead:
+* jQuery Client should detect the version of Firefox Mobile properly.
+* VisualEditor whitelists Firefox Mobile (from that version and up).
+
+",1426117582,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"If I understand correctly:
+* When users of Firefox Mobile use ""Request desktop site"", it uses a user agent header jQuery Client recognises as desktop Firefox. And VE supports that. And that browser supports VE. All is good.
+* When users of Firefox Mobile use the default mode, it uses a user agent header jQuery Client doesn't yet recognise properly (version=mobile). VE does not support that. But it seems otherwise that browser would support VE.
+
+In that case, I'd recommend:
+* jQuery Client should detect the version of Firefox Mobile properly.
+* VisualEditor whitelists Firefox Mobile (from that version and up).
+
+I'm not sure that working around the intentionally faked user-agent header will be feasible and would leave us with a to maintain scenario.",1426117560,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"So it's a jquery.client issue: for Chrome and Firefox on Android, profile().name should always be ""firefox"" or ""chrome"" respectively, with .version set correctly, no matter how user configures the browser.
+
+Currently in Chrome, profile().platform is ""linux"". Maybe we can use ""android"" there to signify the browser is running on Android.",1399985804,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"It seems there're two places where UA matters, summarized below:
+
+Browser | Option | profile().name | profile().version | Tab shown | Warning shown
+---------------------------------------------------------------------------------
+Firefox |   On   |    android     |      mobile       |    No     |      N/A
+Firefox |  Off   |    firefox     |       29.0        |    Yes    |      No
+Chrome  |   On   |    android     |       4.4.2       |    Yes    |      Yes
+Chrome  |  Off   |    chrome      |   34.0.1847.114   |    Yes    |      No
+
+Firefox with the option on is being detected as browser ""android"" version ""mobile"" is the most problematic thing here, because it completely disables VE.",1399985467,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"By having Firefox hit my own webserver, I caught UA below. Not sure whether it can be different from the one returned by navigator.userAgent.
+
+""Request desktop site"" off:
+
+Mozilla/5.0 (Android; Mobile; rv:29.0) Gecko/29.0 Firefox/29.0
+
+JSON.stringify($.client.profile({userAgent:'Mozilla/5.0 (Android; Mobile; rv:29.0) Gecko/29.0 Firefox/29.0',platform:''}))
+""{""name"":""android"",""layout"":""gecko"",""layoutVersion"":29,""platform"":""unknown"",""version"":""mobile"",""versionBase"":""0"",""versionNumber"":0}""
+
+""Request desktop site"" on:
+
+Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0
+
+JSON.stringify($.client.profile({userAgent:'Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0',platform:''}))
+""{""name"":""firefox"",""layout"":""gecko"",""layoutVersion"":20100101,""platform"":""unknown"",""version"":""29.0"",""versionBase"":""29"",""versionNumber"":29}""",1399983335,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"(In reply to Liangent from comment #2)
+> (In reply to James Forrester from comment #1)
+> > Do you mean ""make jquery.client detect for Firefox mobile""? If so, that's a
+> > very different bug to how you've written this one. :-)
+> 
+> Hmm? so it's already special cased in jquery.client for Chrome mobile, so
+> there's no such issue in Chrome, without any change in VE side (I haven't
+> really tested)?
+
+I don't know. Your bug report seems to suggest that Firefox Mobile is getting detected as a failing browser, and telling Firefox Mobile to pretend to be Firefox makes it work fine. That's a sign that it's failing jquery.client's test cases.
+
+Do you have an example UA string? https://developer.mozilla.org/en-US/docs/Gecko_user_agent_string_reference suggests that it should be putting out ""Mozilla/5.0 (Android; Mobile; rv:13.0) Gecko/13.0 Firefox/13.0"".",1399982939,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"(In reply to James Forrester from comment #1)
+> Do you mean ""make jquery.client detect for Firefox mobile""? If so, that's a
+> very different bug to how you've written this one. :-)
+
+Hmm? so it's already special cased in jquery.client for Chrome mobile, so there's no such issue in Chrome, without any change in VE side (I haven't really tested)?",1399982719,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+jquery.client should support detecting Firefox Mobile,"Do you mean ""make jquery.client detect for Firefox mobile""? If so, that's a very different bug to how you've written this one. :-)",1399982480,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ixtz4sysk7h76zhcsyps,task_subcomment,NA
+VisualEditor: Clearing float from a template like {{-}} doesn't work,"In the linked article, the content is not cleared after floats of the tables when using the template {{-}} which transcludes as:
+<br style=""clear:both;"">
+
+This is caused by the inline-block behavior of .ve-ce-mwTransclusionInlineNode
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=List_of_top_100_Major_League_Baseball_strikeout_pitchers&oldid=608135239
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57372",1399971600,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-cfsuxmmxpeev6stnegu6,task_description,resolved
+VisualEditor: Clearing float from a template like {{-}} doesn't work,"Confirmed, now seems fixed (tested in Safari 8.0.4).",1427402228,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cfsuxmmxpeev6stnegu6,task_subcomment,NA
+VisualEditor: Clearing float from a template like {{-}} doesn't work,"This problem seems fixed, as far as I can assess...",1427402002,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-cfsuxmmxpeev6stnegu6,task_subcomment,NA
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,"The ""notices"" thing (exclamation mark in a triangle) disappears from VE toolbar if you open a page for editing, close VE, then open it again (on the same page).
+
+To reproduce:
+1. Click ""Edit"" (or ""Edit beta"") on any page to open VisualEditor
+2. Click ""Cancel"" to close it
+3. Click ""Edit"" again
+
+The toolbar will no longer have the ""notices"" item.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399921320,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-cbra3savyka36yjom4gn,task_description,resolved
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,"Gerritadmin seems to be missing, I uploaded Gerrit change 133537",1400184171,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cbra3savyka36yjom4gn,task_subcomment,NA
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,"Aha, yes, when the only warning is the browser warning I also get this. However, if e.g. you try to edit the Main Page of enwiki you get the other two notices (protected page and edit notice) each time.
+
+Renaming.",1399961766,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cbra3savyka36yjom4gn,task_subcomment,NA
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,"I tested on Opera Next 22 and Opera 12 with the same effect. Maybe this is related to the ""You're using an unsupported browser"" popup?",1399940658,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-cbra3savyka36yjom4gn,task_subcomment,NA
+VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session,What browser does this occur in? Opera? It works fine for me in Chrome and Firefox…,1399928299,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cbra3savyka36yjom4gn,task_subcomment,NA
+VisualEditor: References as part of a file description are misnumbered,"In https://en.wikipedia.org/w/index.php?title=Female_promiscuity&oldid=607751101 references [74], [75] and [76] show up as 1, 2 and 3 in VE in the references box, with the rest of the reference numbers ""pushed down"", but with their original numbering in the main VE editing interface.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1399921200,PHID-USER-n27daagbl3wqf3ghr4nk,False,PHID-TASK-3m3hkpshul72ld2jnj3z,task_description,resolved
+VisualEditor: References as part of a file description are misnumbered,This seems to work correctly these days.,1688060841,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3m3hkpshul72ld2jnj3z,task_subcomment,NA
+VisualEditor: References as part of a file description are misnumbered,"They now show as references [73], [74] and [75] (off-by-one error?)",1421784712,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3m3hkpshul72ld2jnj3z,task_subcomment,NA
+VisualEditor: References as part of a file description are misnumbered,"They now show as references [73], [74] and [75] (off-by-one error?0",1406594865,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3m3hkpshul72ld2jnj3z,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),"See link provided above.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Anaconda,_Montana&diff=prev&oldid=608235426",1399915320,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hhbsyblnnelojfdxms2h,task_description,declined
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),apparently worksforme is the correct resolution for this situation,1407403982,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),So is this unconfirmed then?,1406846549,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),"(In reply to Richard Morris from comment #1)
+> Not quite sure it was a plugin, it could have been user error, cut and
+> pasting the wrong thing. The user did correct them self in the next edit.
+
+If they'd pasted the HTML raw it would have refused (<iframe>s etc. are blocked on paste); maybe they tried to paste it as a link target?",1399916704,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),"Yeah, it could be. James had confirmed my theory and that's why I filed it anyway. But I noticed the revert and was really glad about it. Success, right? :)",1399916495,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?),"Not quite sure it was a plugin, it could have been user error, cut and pasting the wrong thing. The user did correct them self in the next edit.",1399915799,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-hhbsyblnnelojfdxms2h,task_subcomment,NA
+Support for Parsoid-based extracts,"This is important since the extracts are currently generated with the old API which doesn't guarantee valid xhtml5. That prevents third-party developers using less forgiving markup environments from fetching the extracts to build tools on top of them, e.g. https://github.com/waldyrious/primerpedia/issues/20
+
+I'd work on this myself but I really don't have the background to understand the code in ApiQueryExtracts.php on my own (even after taking a look at VisualEditor's ApiVisualEditor.php to check an example implementation of a request to Parsoid, as suggested by Mark Traceur).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399764120,PHID-USER-uazrhtptdqudzoqfefsc,False,PHID-TASK-egjhqqohru7fvy2225t5,task_description,duplicate
+Support for Parsoid-based extracts,Thanks for the feedback! We'll hopefully be prioritising this soon as part of the [[ https://www.mediawiki.org/wiki/Beta_Features/Hovercards | page previews/Hovercards ]] roll out... so watch this space!,1493660695,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"I need to be able to get the formatted extracts either via the old api.php or the new REST service. If a new endpoint is created providing such extracts with well-formed HTML, yes, that would work for me.",1493657792,PHID-USER-uazrhtptdqudzoqfefsc,False,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"TextExtracts could provide xml well formedness via php (we have a library in #MobileFrontend doing exactly that). Is there any other reason you specifically want this in REST?
+
+I suspect we will end up creating a rest endpoint to solve the epic. I've included well formed HTML as a requirement. Does this feel less broad now?",1493654331,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,">>! In T67169#3221431, @Jdlrobson wrote:
+> I think this task is exactly the same as what we are talking about in T113094 and its subtasks ?
+
+Yes, it looks like it, although the title/description of that issue is a little too broad for me to be comfortable calling this a dupe (particularly the line ""we either need to write a bunch of tests and fix up TextExtracts **//or//** build a new Parsoid based api specifically for the purpose of Hovercards"" -- this bug is specifically about the latter, due to the need for xml well-formedness).",1493551495,PHID-USER-uazrhtptdqudzoqfefsc,False,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"Thanks for clarifying @waldyrious .
+We are considering switching to HTML extracts for Page previews so watch this space.
+I think this task is exactly the same as what we are talking about in T113094 and its subtasks ?
+",1493396675,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"IIUC, that is not exactly what this request is about: [[ https://github.com/waldyrious/primerpedia/blob/gh-pages/primerpedia.js | currently I'm using ]] a request like https://en.wikipedia.org/w/api.php?action=query&prop=extracts&exintro&indexpageids=true&format=json&generator=random&grnnamespace=0&format=json, which returns a html-formatted extract. The problem is that the html is not guaranteed to be valid, hence it fails if embedded in a xhtml page (or any other context where well-formed xml is required).
+
+The REST API, in contrast, only returns plaintext extracts at the moment. I could use them, but that's a workaround (avoiding rich formatting altogether) rather than a fix.
+
+Is there any way to use the REST API to get an extract including the (rendered, not wikicode) basic formatting used in the actual article? For example bold, italics, and perhaps links as well.",1493372670,PHID-USER-uazrhtptdqudzoqfefsc,False,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"IIUC, that is not exactly what this request is about: [[ https://github.com/waldyrious/primerpedia/blob/gh-pages/primerpedia.js | currently I'm using ]] a request like https://en.wikipedia.org/w/api.php?action=query&prop=extracts&exintro&indexpageids=true&format=json&generator=random&grnnamespace=0&format=json, which returns a html-formatted extract. The problem is that the html is not guaranteed to be valid, hence it fails if embedded in a xhtml page (or any other context where well-formed xml is required).
+
+The REST API, in contrast, only returns plaintext extracts at the moment. I could use them, but that's a workaround (avoiding rich formatting altogether) rather than a fix.
+
+Is there any way to use the REST API to get an extract that preserves the basic formatting (bold, italics, and perhaps links as well) used in the actual article?",1493372609,PHID-USER-uazrhtptdqudzoqfefsc,False,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"IIUC, that is not exactly what this request is about: [[ https://github.com/waldyrious/primerpedia/blob/gh-pages/primerpedia.js | currently I'm using ]] a request like https://en.wikipedia.org/w/api.php?action=query&prop=extracts&exintro&indexpageids=true&format=json&generator=random&grnnamespace=0&format=json, which returns a html-formatted extract. The problem is that the html is not guaranteed to be valid, hence it fails if embedded in a xhtml page (or any other context where well-formed xml is required).
+
+The REST API, in contrast, only returns plaintext extracts at the moment. I could use them, but that's a workaround (avoiding rich formatting altogether) rather than a fix.
+
+Is there any way to use the REST API to get an html-formatted extract?",1493372514,PHID-USER-uazrhtptdqudzoqfefsc,False,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Support for Parsoid-based extracts,"I believe this is resolved?
+Is this what you were asking for: https://en.wikipedia.org/api/rest_v1/page/summary/Bavaria ?
+",1493322490,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-egjhqqohru7fvy2225t5,task_subcomment,NA
+Set up dev.wikimedia.org portal,"There's a few (not too many!) things that need a home, and I think this is a good time to start work on what will become the main entry point for developers to learn about Wikimedia (wiki) projects and Wikimedia (software) products.
+
+developer.wikimedia.org
+
+The initial portal wouldn't be unlike some of these:
+* https://developers.google.com/
+* https://developers.facebook.com/
+* https://dev.twitter.com/
+
+Here's are some very specific use cases that have come up during the Zurich Hackathon that I think would be best served with this:
+
+- Where do I find out about the existence of:
+  * gdash.wikimedia.org
+  * graphite.wikimedia.org
+  * noc.wikimedia.org
+  * doc.wikimedia.org
+  * git.wikimedia.org
+  * wikitech.wikimedia.org
+  * irc.wikimedia.org
+  ( * stream.wikimedia.org/rc )
+
+  Current solution: None
+
+  Current workaround for regulars:
+    https://wikitech.wikimedia.org/wiki/Category:Services
+
+- Where would I find out about xml dumps?
+
+  Current solution: None
+
+  Current workaround for regulars:
+    http://dumps.wikimedia.org/backup-index.html
+
+- Where would I find out about pageview count data?
+
+  Current solution: None
+
+  Current workaround for regulars:
+    http://dumps.wikimedia.org/
+      http://dumps.wikimedia.org/other/
+        http://dumps.wikimedia.org/other/pagecounts-raw/
+
+I'm sure the people from the ""Data API & Hub"" table from Zurich Hackathon 2014 have more specific stories and use cases. 
+
+This hub would act as delegate for the following cases (pointing to things on another domain or the same, some of which should probably move to it eventually):
+
+* Products
+  Such as:
+
+  - MediaWiki
+    -> Homepage
+    -> Source code (git repo)
+    -> Documentation (separate portal, on mediawiki.org for now, ultimately linking back to developer.wikimedia.org/mediawiki/{js,php,api} for documentation of individual classes and apis.
+        We already have JS and PHP docs autogenerated for MediaWiki.
+        Docs the API are still hardcoded on mediawiki.org and api.php/help
+        exclusively, we should get API and Hooks documentation onto
+        doc.wikimedia.org as well.
+        See https://www.mediawiki.org/wiki/Requests_for_comment/Documentation_overhaul
+
+  - VisualEditor
+    -> Source code
+    -> Demo(s)
+    -> Documentation
+
+* Data and APIs
+  (APIs that are not related to MediaWiki or individual user-facing products, but Wikimedia services in general, MediaWiki's API is one small part of that)
+
+  Such as:
+
+  * page view counts
+  * xml dumps
+  * OAuth?
+  * irc.wikimedia.org
+  ( * stream.wikimedia.org/rc )
+  * ""See also: Wikidata""
+
+* Communications
+  - (e.g. link to tech blog, as currently linked from noc.wikimedia.org)
+  - mailing lists
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=29936",1399646220,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_description,declined
+Set up dev.wikimedia.org portal,"This task has been lingering for five years. 
+The domain mentioned in the summary has existed for years (resolved).
+However, the content/workflow/thoughts in the task description do not (not resolved).
+
+I'm boldly decline this (very #epic broad) task in favor of the #Wikimedia-Developer-Portal project which allows a better breakdown of subtasks. 
+See https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal for more info (still going to take me 2-3 more weeks to sort out the very basics though - patience please!)",1597919448,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,please also see T246945 which might conflict with this effort and introduce yet another place for documentation rather than having a single place for developers to go to,1590062421,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Would this task be a good topic for the #wikidev17 ? If so, the deadline to submit new proposals is next Monday, October 31: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation",1477574862,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"I have detached this proposal from {T101441} and #web-APIs-Hub because the latter has defined its scope within web APIs only (which happens to be the scope of the Google, Facebook, Twitter examples given above).
+
+Being Wikimedia also the umbrella of hundreds of open source projects, we have a more complex picture. What should be the one and only home to find about all of them? In short, my opinion is to make http://mediawiki.org that home, linking wherever it is needed.",1439046147,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"#Engineering-Community with the help of @spage are committing to this goal for the next quarter: {T101441}.
+
+I think it is time to conciliate that goal with this task, and to find the best relationship with both that we can achieve by the end of September.",1434014667,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 197272 merged by BBlack:
+dev.wm.org - Increase HSTS max-age to 1 year
+
+[[https://gerrit.wikimedia.org/r/197272]]",1426599931,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 197272 had a related patch set uploaded (by Chmarkine):
+dev.wm.org - Increase HSTS max-age to 1 year
+
+[[https://gerrit.wikimedia.org/r/197272]]
+",1426564386,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 195338 merged by BBlack:
+Enable HSTS on dev.wm.org max-age=7 days
+
+[[https://gerrit.wikimedia.org/r/195338]]",1426025069,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 195338 had a related patch set uploaded (by Chmarkine):
+Enable HSTS on dev.wm.org max-age=7 days
+
+[[https://gerrit.wikimedia.org/r/195338]]
+",1425929398,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,">>! In T67074#1013909, @Qgil wrote:
+> We have decided to [[ https://phabricator.wikimedia.org/maniphest/query/zZr63xHvTU8d/#R | prioritize the creation of some actual content ]] under the existing API: namespace in mediawiki.org.
+
+Yes, content, then a portal page on mw.org featuring that content based on [[ https://www.mediawiki.org/wiki/dev.wikimedia.org#Structure |  wireframe ideas ]]. Once it's at ""better than draft"" status, dev.wikimedia.org can have a redirect to this, and doc.wikimedia.org can link to it.",1423521438,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,We have decided to [[ https://phabricator.wikimedia.org/maniphest/query/zZr63xHvTU8d/#R | prioritize the creation of some actual content ]] under the existing API: namespace in mediawiki.org.,1423039843,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"needs Apache config, then obviously some files to upload.. ",1421789349,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 181398 merged by Dzahn:
+add dev.wikimedia.org
+
+[[https://gerrit.wikimedia.org/r/181398]]",1420466525,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Change 181398 had a related patch set uploaded (by Qgil):
+add dev.wikimedia.org
+
+[[https://gerrit.wikimedia.org/r/181398]]
+
+#patch-for-review",1419253513,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,https://gerrit.wikimedia.org/r/#/c/181398/,1419250219,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"**sumanah** wrote:
+
+Removing myself from cc on this as I prepare to leave Wikimedia Foundation.",1411502025,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Let's merge this discussion with the work done at https://www.mediawiki.org/wiki/dev.wikimedia.org. Sorry for the duplicity of spaces, which will go away when we merge Bugzilla with Phabricator.
+
+We have settled on http://dev.wikimedia.org -- see 
+
+Name for the 'developer hub'
+http://fab.wmflabs.org/T488 
+
+and 
+
+URL of the Developer Hub
+http://fab.wmflabs.org/T490
+
+(In reply to Bawolff (Brian Wolff) from comment #6)
+> Why not just have dev.wikimedia.org redirect to a page on mediawiki.org.
+> That way people can update it as appropriate easily.
+
+Yes, this is the current plan that you can help fine tuning:
+
+Technology selection for the Developer Hub
+http://fab.wmflabs.org/T491
+
+How to redirect from dev.wikimedia.org
+http://fab.wmflabs.org/T558",1409036097,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"(In reply to Krinkle from comment #0)
+> 
+> developer.wikimedia.org
+> 
+> The initial portal wouldn't be unlike some of these:
+> * https://developers.google.com/
+> * https://developers.facebook.com/
+> * https://dev.twitter.com/
+
+* https://developer.github.com/
+* https://developer.yahoo.com/
+* http://dev.windows.com/
+* http://www.bing.com/dev
+
+
+https://developers.google.com/
+https://developers.google.com/maps/documentation/javascript/tutorial
+https://developers.google.com/maps/documentation/javascript/examples/map-simple",1408973486,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Why not just have dev.wikimedia.org redirect to a page on mediawiki.org. That way people can update it as appropriate easily.
+
+
+>- Where do I find out about the existence of:
+[..]
+>  * graphite.wikimedia.org
+
+Not much point telling people about the existence of a service they are not allowed access to.",1400968272,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"(In reply to Krinkle from comment #0)
+> * Data and APIs
+> 
+>   Such as:
+> 
+>   * page view counts
+>   * xml dumps
+>   * OAuth?
+
+Discovered today that there is such a thing as https://frdata.wikimedia.org
+ as well. To be documented at  https://wikitech.wikimedia.org/wiki/frdata.wikimedia.org.",1400967990,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Topic related with a session scheduled for tomorrow at 10:30 in the Wikimedia Hackathon:
+
+How does the data and developer hub fit into the current documentation
+https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Schedule#Saturday_May_10",1399653842,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"Initial implementation proposal:
+
+ - static html wrapped in a lightweight php router for header/footer and nice url handling (e.g. no need to repeat too much for each subdirectory, it can be handled automatically using data and available directories (js,php,api,demo) and versions (master,REL1_23,etc.)), using twitter bootstrap (like doc.wikimedia.org)
+ - all in git (wikimedia/dev-docroot.git?)
+ - deployed via git-deploy
+
+The server for it only needs to be behind misc-lb-eqiad and be a git-deploy target. The main changes would come in from people via gerrit/git and deployed periodically.
+
+Changes to the auto-generated docs would be build by gallium, and somehow pushed to the web server (they wouldn't be in dev-docroot.git).",1399647886,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"I'm in full support of this. 
+
+As someone working on this https://www.mediawiki.org/wiki/API_Documentation_&_Developer_Hub, I would like this very much.",1399646680,PHID-USER-xtudulsp3haty5uagokz,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+Set up dev.wikimedia.org portal,"I think all of doc.wikimedia.org can migrate to appropriate paths on this domain.
+
+Like:
+- dev.wikimedia.org/mediawiki/doc/js
+- dev.wikimedia.org/mediawiki/doc/php
+- dev.wikimedia.org/mediawiki/doc/api
+- dev.wikimedia.org/visualeditor/doc
+- dev.wikimedia.org/visualeditor/demo
+- dev.wikimedia.org/oojs-ui/doc
+- dev.wikimedia.org/oojs-ui/demo
+- dev.wikimedia.org/oojs/doc",1399646574,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-yrfd4dhbbio3uikl5u33,task_subcomment,NA
+"VisualEditor:  If you insert a gallery into a list, the list formatting remains visible but is removed in wikitext","Intention:
+Add an image gallery at the top of a section.
+
+Steps to Reproduce:
+1. Open a page that has a list at the top of the section.  
+
+2. Place your cursor at the top of the list, and Insert > Gallery.
+
+
+Actual Results:  
+The bullet remains visible.  The text of the list item is on the next line, but indented.
+
+However, when you save, the list formatting (the asterisk at the start of the line) has been removed.
+
+Expected Results:  
+The gallery would be inserted before the list.  That is,
+
+* List item
+
+would turn into 
+```
+<gallery>File:Example.jpg
+File:Example2.jpg</gallery>
+
+* List item
+```
+instead of into
+
+```
+ <gallery>File:Example.jpg
+File:Example2.jpg</gallery>List item
+```
+(Notice the stray space at the start of the line.)
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=92775&oldid=92716",1399497480,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ijh5ohctbismuiczyzo7,task_description,open
+"VisualEditor:  If you insert a gallery into a list, the list formatting remains visible but is removed in wikitext","Unlike legacy parser which breaks the list (T11996), Parsoid well supports `<gallery>` inside list item: wikitext-to-html [[https://meta.wikimedia.org/w/index.php?title=User:Pols12/Sandbox&oldid=26371690&useparsoid=1 | seems to work correctly]].
+However, this bug seems to indicate there is an issue with html-to-wiktext, since VisualEditor rendering is correct:
+
+```lang=html
+<li id=""mwBQ"" class=""ve-ce-branchNode"">
+  <div class=""ve-ce-branchNode-slug ve-ce-branchNode-blockSlug"">…</div>
+  <ul class=""ve-ce-branchNode gallery ve-ce-focusableNode"">
+    <li class=""ve-ce-branchNode gallerybox"">
+      <div class=""thumb"" style=""width: 150px; height: 150px;"">…</div>
+      <a href=""#"" class=""oo-ui-element-hidden"">…</a>
+      <div class=""ve-ce-branchNode ve-ce-activeNode gallerytext"">…</div>
+    </li>
+  </ul>
+  <p class=""ve-ce-branchNode ve-ce-contentBranchNode ve-ce-paragraphNode ve-ce-generated-wrapper"">List item</p>
+</li>
+```
+which should be parsed as 
+```lang=wikitext
+* <gallery>
+…
+</gallery> List item",1710098493,PHID-USER-unpoeiyj52rmcfqi5rbw,True,PHID-TASK-ijh5ohctbismuiczyzo7,task_subcomment,NA
+"VisualEditor:  If you insert a gallery into a list, the list formatting remains visible but is removed in wikitext",Update:  This is still happening.  https://en.wikipedia.org/w/index.php?diff=852318770&oldid=852318749&diffmode=source,1532748970,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ijh5ohctbismuiczyzo7,task_subcomment,NA
+"VisualEditor:  If you insert a gallery into a list, the list formatting remains visible but is removed in wikitext","This sort of happens if you insert a references list, which gives you this:
+
+* 
+<references />List item
+
+
+but not for images, math, templates, etc.",1399500501,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ijh5ohctbismuiczyzo7,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"From MediaWiki.org:
+
+> I would like to have an omnibar in VE. This is a single text field where
+> a user can search for things they want to do, instead of clicking a
+> button you can invoke omnibar with a keyboard shortcut and then search
+> for the task you want to do. This would be helpful to easier access those
+> buttons which don't have shortcuts now. Like managing category, inserting
+> reference, changing to source editor etc.
+
+Seems like it could be a lot of work to implement – for example, internationalisation of such controls might be hard – but it might be particularly useful for power users (or for controls that don't have a keyboard shortcut, as the proposer notes).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1399309080,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_description,resolved
+VisualEditor: Provide an omnibar for quick keyboard access to tools,">>! In T66905#8947788, @Sebastian_Berlin-WMSE wrote:
+> Ctrl+shift+p doesn't work for me (backslash does). This is on Ubuntu 22.04 and Firefox 114. What happens instead is that a private window is opened, which is the normal behaviour in Firefox.
+
+Filed as T341603",1689097619,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Ctrl+shift+p doesn't work for me (backslash does). This is on Ubuntu 22.04 and Firefox 114. What happens instead is that a private window is opened, which is the normal behaviour in Firefox.",1687241247,PHID-USER-fgieaqsdluipfhgequws,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"@John_Broughton yes, that’s expected. It should be removed if you chose something from the menu, and otherwise stick around (e.g. if you actually wanted to type a backslash). You can trigger it without entering a character by pressing {cmd/ctrl}-shift-p if you prefer to avoid that.",1687207492,PHID-USER-hdkktg27rkwebepkv6yw,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"When I'm in Visual Editor, and type a ""\"", I see this toolbar. However, the ""\"" is inserted into the text of the page being edited, as is illustrated at https://commons.wikimedia.org/wiki/File:Visual_editor_toolbar_search_feature.png  Is that the expected behavior? 
+",1687207174,PHID-USER-hirrhium5ibrtof34lwa,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,">>! In T66905#8935569, @DLynch wrote:
+> @Trizek-WMF It's already out, but your comment made me notice that it's broken this week, so https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/930637 will fix that.
+
+Now I get why I couldn't use it. :)
+
++1 to @Quiddity. Documentation is important, and much more efficient than a one-time announcement or serendipity. ",1686914696,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"It would be best if the image was part of the official documentation, and could be linked to as part of the text within Tech News, rather than just a footnote. Perhaps someone from the Editing team could add it to https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide wherever is appropriate? I'm not sure how your (great!) multilingual screenshot system works, nor where within that page to locate a new section mentioning the feature, hence haven't attempted to add it myself. Thanks!",1686858294,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"@Trizek-WMF It's already out, but your comment made me notice that it's broken this week, so https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/930637 will fix that.",1686844111,PHID-USER-hdkktg27rkwebepkv6yw,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,When this (cool) feature will be on wikis? ,1686824741,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"There isn't, but here's a screenshot: https://commons.wikimedia.org/wiki/File:Visual_editor_toolbar_search_feature.png",1685447252,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Thanks for the draft wording for Tech News!
+Is there a wiki-page the entry could link to, showing an image or text-description of the feature?",1685050127,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921682 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Register a HelpCompletionAction group alias for cite%%%
+https://gerrit.wikimedia.org/r/921682",1684950708,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 922577 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (12333c596)%%%
+https://gerrit.wikimedia.org/r/922577",1684936842,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 922577 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (12333c596)%%%
+https://gerrit.wikimedia.org/r/922577",1684859894,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921683 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] HelpCompletionAction: rename and clean up commandGroups to toolGroups%%%
+https://gerrit.wikimedia.org/r/921683",1684766260,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921677 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Add fuzzy bar to the help dialog%%%
+https://gerrit.wikimedia.org/r/921677",1684766235,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921683 had a related patch set uploaded (by DLynch; author: DLynch):
+%%%[VisualEditor/VisualEditor@master] Clean up the cite group alias since it's moving to the extension%%%
+https://gerrit.wikimedia.org/r/921683",1684664237,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921682 had a related patch set uploaded (by DLynch; author: DLynch):
+%%%[mediawiki/extensions/Cite@master] Register a HelpCompletionAction group alias for cite%%%
+https://gerrit.wikimedia.org/r/921682",1684664209,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Change 921677 had a related patch set uploaded (by DLynch; author: DLynch):
+%%%[VisualEditor/VisualEditor@master] Add fuzzy bar to the help dialog%%%
+https://gerrit.wikimedia.org/r/921677",1684661116,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Adding for tech news, suggested description: ""VisualEditor now includes a toolbar search popup that can be triggered by typing `\` or pressing `ctrl/cmd + shift + p`, which will let you quickly access most tools available inside the editor.""",1684665297,PHID-USER-hdkktg27rkwebepkv6yw,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Adding for tech news, suggested description: ""VisualEditor now includes a command search popup that can be triggered by typing `\` or pressing `ctrl/cmd + shift + p`, which will let you quickly access most tools available inside the editor.""",1684661044,PHID-USER-hdkktg27rkwebepkv6yw,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Provide an omnibar for quick keyboard access to tools,"Post-merge tagging these patches:
+* https://gerrit.wikimedia.org/r/#/c/744905
+* https://gerrit.wikimedia.org/r/#/c/921462
+* https://gerrit.wikimedia.org/r/#/c/921588
+* https://gerrit.wikimedia.org/r/#/c/745282",1684658065,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-myea7wfzzuri5j6zmpgx,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"I want to use the HTML code <mark> in the newsletter and still be able to edit the draft page in VisualEditor.  Right now, adding <mark> produces nowiki tags, and opening a page with <mark> already on it prevents editing the marked text (alienated content).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398362520,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-5ho3axzxyziic5a47eop,task_description,open
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"I had seen that, but given that it didn't mention the word ""text"" and that elsewhere you were so strongly against the idea, I had to assume it was actually about the page color.
+The ability to set a text background in whatever color we want (#FC0FC0, in my case) will IMHO make using <mark> unnecessary.",1415296452,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"(In reply to Elitre from comment #7)
+> No! Google Docs allows highlighting text in the color I want. Please make
+> that happen somehow?
+
+That's not highlighting with <mark>, that's setting text background colour which is bug 73041.",1415231587,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),No! Google Docs allows highlighting text in the color I want. Please make that happen somehow?,1415227751,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"(In reply to Elitre from comment #5)
+> I'm unhappy. I demand the ability to pick my favorite color when
+> highlighting.
+
+Talk to W3C. ;-)",1415227351,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),I'm unhappy. I demand the ability to pick my favorite color when highlighting.,1415227094,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"(In reply to Elitre from comment #3)
+> Will this only allow marking the text in yellow?
+
+It will mark the text with <mark>. It's up to users' browsers to decide how to show it as marked, but yes, all major browsers ape the neon-lemon-yellow highlighter colour to show this currently.",1415226752,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),Will this only allow marking the text in yellow?,1415221139,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"Change 141605 merged by jenkins-bot:
+Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
+
+https://gerrit.wikimedia.org/r/141605",1404154589,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+VisualEditor: Tool to set/unset text as highlighted (<mark>),"Change 141605 had a related patch set uploaded by Jforrester:
+Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
+
+https://gerrit.wikimedia.org/r/141605",1403568483,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-5ho3axzxyziic5a47eop,task_subcomment,NA
+"VisualEditor: Make MW toolbar integrate into the new ""floating toolbar"" beta feature when enabled","Right now it's a horrible mess. :-(
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1398113460,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-swkths2fnka7qjw7zpsv,task_description,invalid
+"VisualEditor: Make MW toolbar integrate into the new ""floating toolbar"" beta feature when enabled",Said feature was killed off.,1493662390,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-swkths2fnka7qjw7zpsv,task_subcomment,NA
+"VisualEditor: VE-core, OOjs and OOjs-UI update scripts share commonalities but don't share code","We should merge them together where appropriate.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1397873640,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-brrtew2a7sjhjj6dapyh,task_description,open
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Read mode
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add a bullet list
+3.Add an image as a bullet point 
+4.Save the page
+5.Reopen the page 
+
+
+Observed Result:
+The bullet point appears on the read mode but not inside VE, but when you type something in that position the bullet point appears again.
+
+See the screenshot attached
+
+Page:
+http://en.wikipedia.beta.wmflabs.org/wiki/After_switch
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13837}",1397863440,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_description,resolved
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,Verified the fix in production.,1398988023,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,Verified the fix on test2,1398906351,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Change 127387 merged by jenkins-bot:
+Remove unnecessary overflow:hidden from block slug style
+
+https://gerrit.wikimedia.org/r/127387",1398107347,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Change 127387 had a related patch set uploaded by Esanders:
+Remove unnecessary overflow:hidden from block slug style
+
+https://gerrit.wikimedia.org/r/127387",1397865770,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Caused by a bug in Chrome, reported upstream: https://code.google.com/p/chromium/issues/detail?id=365024",1397865735,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug,"Created attachment 15139
+Inside VE
+
+**Attached**: {F13838}",1397863503,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5s5qwgvvgi32pv6mawpw,task_subcomment,NA
+VisualEditor: Broken appearance when window is too small in Internet Explorer,"just ugh
+
+See attached screenshot.  Green Highlight is the cursor bar -- showing the cursor and the top of the page is somehow ending up under the heading instead of just below it.  Red hightlight is the outline of the (not showing) warning about using an unsupported browser.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13658}",1397146020,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-hrp2vnudp6cwigusycqf,task_description,declined
+VisualEditor: Broken appearance when window is too small in Internet Explorer,"This doesn't happen for me in IE10. The cursor does go under the toolbar, but that is a general issue (there's a lot of scrolling weirdness in IE still). I can't reproduce the invisible notice.",1409957935,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hrp2vnudp6cwigusycqf,task_subcomment,NA
+VisualEditor: Broken appearance when window is too small in Internet Explorer,"Fixed in IE11, at least.",1409099795,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hrp2vnudp6cwigusycqf,task_subcomment,NA
+VisualEditor: Keyboard shortcuts help page should use kbd elements,"This page should be using the html5 element <kbd> to represent the keyboard keys.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1397136240,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-qez6iozv44a6hxiwzacj,task_description,resolved
+VisualEditor: Keyboard shortcuts help page should use kbd elements,"Change 125212 merged by jenkins-bot:
+Put CommandHelpDialog keyboard shortcuts in kbd not div elements
+
+https://gerrit.wikimedia.org/r/125212",1397239055,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qez6iozv44a6hxiwzacj,task_subcomment,NA
+VisualEditor: Keyboard shortcuts help page should use kbd elements,"Change 125212 had a related patch set uploaded by Jforrester:
+Put CommandHelpDialog keyboard shortcuts in kbd not div elements
+
+https://gerrit.wikimedia.org/r/125212",1397145373,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qez6iozv44a6hxiwzacj,task_subcomment,NA
+"Provide easy, backend way for extensions to show PostEdit notifications with custom content","I've recently been working on an extension, and it would be nice for it to show a PostEdit success box when it successfully completes an operation. However, doing this at the moment would mean loading a Javascript file, the PHP setting a JS config var for whether to display the PostEdit box or not, JS checking this variable, JS getting a message for the text to display, etc.
+
+What would really be useful would be a way, just in PHP, for extensions to specify that a PostEdit box should be shown, with the text to display. The code would then ensure that JS to show the box is loaded on the page (which would possibly also save resources over the above method).
+
+I am not entirely sure how this would be best implemented, but possibly something like wfShowPostEdit( $text ), that could be easily called in an extension's code. Something like this would make it many more times easier for extensions to show PostEdit boxes.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1397069820,PHID-USER-xpto4uqv737bawfiy53m,False,PHID-TASK-tefwphwiw2bjgqazm5r5,task_description,declined
+"Provide easy, backend way for extensions to show PostEdit notifications with custom content","I think what you're looking for is `mw.notify()`.
+
+See also <https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.plugin.notify>. Be sure to load the `mediawiki.notify` module (or add it as dependency to your script).
+
+There are various examples in MediaWiki core that use this. Including the ajax modules for patrol and watch actions. E.g. click the watch star on a page when logged-in.",1457647347,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tefwphwiw2bjgqazm5r5,task_subcomment,NA
+"Provide easy, backend way for extensions to show PostEdit notifications with custom content","Yeah, it would be nice extensions to be able to show their own messages, depending on their function.
+
+(Sorry about the categorisation stuff, still pretty unexperienced here :) )",1397075634,PHID-USER-xpto4uqv737bawfiy53m,False,PHID-TASK-tefwphwiw2bjgqazm5r5,task_subcomment,NA
+"Provide easy, backend way for extensions to show PostEdit notifications with custom content","MediaWiki 1.21 provides a wgPostEdit variable (bug 43270) depending on mediawiki.action.view.postEdit. 
+Per bug 48276, the VisualEditor extension depends on it, but looks like you'd like to define your own strings to display here?",1397074968,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-tefwphwiw2bjgqazm5r5,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","On every page there is an icon of a pencil.
+
+It is linked to #editor/0.
+
+I.e. there is no way to edit any other section than section 0.
+
+Maybe it was assumed that /0 meant the whole page.
+
+Anyway one must manually change the url to /1, /2 etc.",1396838700,PHID-USER-awbqewknju4hbrnah6pm,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_description,duplicate
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","@Jdlrobson @Niedzielski, thoughts:
+
+It seems like there are possibly two confusing things going on here:
+
+**1) Articles with empty lead sections**
+-I find the fact that this page/article doesn't have a lead section to be slightly confusing. It took me a bit to understand how that was happening in the first place. Maybe this is just because I'm inexperienced with Wikis.
+-I wonder how common this situation is where the lead section is totally blank (I took a look around at some talk pages and other non-article namespace pages...it seems like often even when there is no text in the lead section there is still some stuff, e.g. a template, in there)
+-I wonder if people in this situation are intending to have empty lead sections, or if they don't realize that starting the article/page with a heading causes this slightly awkward situation
+-Do we have an opinion on whether or not it's ""okay"" to start an article/page with a heading? I suppose we could discourage it, or at least alert people so that there's a bit more awareness of what's going on here
+
+**2) The fact that on mobile you can only edit one section at a time**
+-agreed it's confusing that the edit pen for the lead section is located on top of the article, but then again the lead section doesn't have a heading like the other sections do so it'd be impossible to match the pattern used in subsequent sections
+-I wonder if this one section at a time editing is confusing to people in general, or only when they find themselves editing an empty lead section
+
+That being said, I wonder if there's something relatively cheap we can do with the empty state here? e.g.
+
+{F16725187}",1522970368,PHID-USER-cjbkqgaozso5gfp3xv2n,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button",This is being handled as part of the Fixed Header / Winter Beta feature https://www.mediawiki.org/wiki/Winter,1397843948,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","In the case of VE this does mean edit the entire page.
+On tablets/desktops we may make this mean the entire page.
+
+cc'ing Jared in case he can comment on the long term strategy.",1397843273,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","This is currently by design to make editing easier on a mobile screen by optimising for section editing.
+
+We are currently exploring full page edits in our work on VisualEditor. This may or may not get addressed as part of that.",1396981946,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","Maybe if there is nowhere else to put it, have that row be:
+Pencil (edit whole article), upload, watch, Pencil+0 (edit section 0)",1396934169,PHID-USER-awbqewknju4hbrnah6pm,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","The star watchlist icon applies to the entire article, so one assumes the same with the edit icon appearing in the same row. I didn't test the upload icon.",1396934041,PHID-USER-awbqewknju4hbrnah6pm,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","Ah... I get it!
+To edit section | use pencil at
+0 | top left
+1 | side right
+2 | side right
+3 | side right
+4 | side right
+
+Who would have ever guessed!
+
+One assumes instead:
+
+To edit section | use pencil at
+entire article | top left
+0 | side right
+1 | side right
+2 | side right
+3 | side right
+4 | side right",1396933316,PHID-USER-awbqewknju4hbrnah6pm,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","**jgonera** wrote:
+
+Are there no pencil icons in sections when you unfold them? If no, can you provide a URL?",1396891012,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button","**bingle-admin** wrote:
+
+Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1909",1396839008,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-lwpo5wymv4mwdrrzz7vg,task_subcomment,NA
+VisualEditor: Switch action=opensearch calls to list=prefixsearch where appropriate,"Gerrit af6d9ab introduced list=prefixsearch which can be used as a generator, which action=opensearch can't be. This would allows us to avoid taking the output of opensearch and turning around to make follow-up API requests for e.g. pageprops to see if they are redirects or whatever.
+
+We shouldn't do this switch until MW1.23 is released, at least, however.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1396659720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6zm5srh6har3jnrlfrt6,task_description,resolved
+VisualEditor: Switch action=opensearch calls to list=prefixsearch where appropriate,"Change 134632 merged by jenkins-bot:
+Switch action=opensearch call to list=prefixsearch where appropriate
+
+https://gerrit.wikimedia.org/r/134632",1401323903,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6zm5srh6har3jnrlfrt6,task_subcomment,NA
+VisualEditor: Switch action=opensearch calls to list=prefixsearch where appropriate,"Change 134632 had a related patch set uploaded by Alex Monk:
+Switch action=opensearch calls to list=prefixsearch where appropriate
+
+https://gerrit.wikimedia.org/r/134632",1400689052,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6zm5srh6har3jnrlfrt6,task_subcomment,NA
+Add Vietnamese (vi) input method,"(In reply to Minh Nguyễn from bug 5309 comment #45)
+> many Vietnamese Wikipedia users rely on an IME script embedded via
+> a gadget, but gadgets are disabled at [[Special:UserLogin/signup]]. We’d
+> need to port the (rather complex) IME to ULS to keep the signup form
+> accessible.
+
+We definitely should! It shouldn't be hard, jquery.ime only needs a comma separated list of input keys -> result character pairs.
+https://github.com/wikimedia/jquery.ime/wiki/Technical-Specification#input-method-definition
+If you can't prepare such a table, can you ask other vietnamese users?
+
+--------------------------
+**Version**: master
+**Severity**: enhancement
+**See Also**:
+https://github.com/wikimedia/jquery.ime/issues/342",1396517460,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_description,open
+Add Vietnamese (vi) input method,"As noted in T286863#7287345, @MikePlantilla has begun work on a jquery.ime-based reimplementation of Vietnamese IME.
+
+In case it helps, the AVIM Firefox extension’s repository has [a battery of automated tests](https://github.com/1ec5/avim/blob/master/tests/corpus.js) that ensures [the entire corpus](https://github.com/1ec5/hunspell-vi/blob/master/dictionaries/vi-DauCu.dic) of words in the Free Vietnamese Dictionary Project can be typed using a variety of tone mark placements. I put together this integration test because the core AVIM code is difficult to reason about and impossible to unit test, but it would be applicable to any IME implementation. Feel free to rig it to test your implementation.",1629178059,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"As noted in T286863#7287345, @MikePlantilla has begun work on a jquery.ime-based reimplementation of Vietnamese IME.
+
+In case it helps, the AVIM Firefox extension’s repository has [a battery of automated tests](https://github.com/1ec5/avim/blob/master/tests/corpus.js) that ensures [the entire corpus](https://github.com/1ec5/hunspell-vi/blob/master/dictionaries/vi-DauCu.dic) of words in the Free Vietnamese Dictionary Project can be typed using a variety of tone mark placements. Feel free to rig it to test your implementation.",1629177986,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"As noted in T286863#7287345, @MikePlantilla has begun work on a jquery.ime-based reimplementation of Vietnamese IME.
+
+In case it helps, the AVIM Firefox extension’s repository has [a battery of automated tests](https://github.com/1ec5/avim/blob/master/tests/corpus.js) that ensures [the entire corpus](https://github.com/1ec5/hunspell-vi/blob/master/dictionaries/vi-DauCu.dic) of words in the Free Vietnamese Dictionary Project can be typed using a variety of tone mark placements.",1629177880,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"(In reply to Nemo from comment #3)
+> (In reply to Minh Nguyễn from comment #2)
+> > I'd be happy to try and port AVIM to jquery.ime, but it may take awhile.
+> 
+> That would be wonderful! Please assign this bug to yourself when you start
+> working on it.
+
+Indeed, this would be wonderful. I'll gladly help with that. It shouldn't be very hard. jqeury.ime had pretty good docs for developers. Please contact me if you need any assistance.",1398158005,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"(In reply to Minh Nguyễn from comment #2)
+> I'd be happy to try and port AVIM to jquery.ime, but it may take awhile.
+
+That would be wonderful! Please assign this bug to yourself when you start working on it.
+
+> Fortunately, most of the complexity relates to text selection handling,
+> which should be handled by jquery.ime already.
+
+Nice. If other features are missing and block the port, please file them as soon as possible at https://github.com/wikimedia/jquery.ime/issues .",1396523951,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"Forgot to link [[vi:MediaWiki:Gadget-AVIM.js]] and [[vi:MediaWiki:Gadget-AVIM portlet.js]].
+
+I'd be happy to try and port AVIM to jquery.ime, but it may take awhile. Fortunately, most of the complexity relates to text selection handling, which should be handled by jquery.ime already.",1396521328,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+Add Vietnamese (vi) input method,"Unfortunately, it isn't quite that simple. Vietnamese users expect IME-like functionality, not just a keyboard layout. For instance, with the [[Telex (IME)]] input method, ""Vietje"" should become ""Việt"", ""truongwf"" should become ""trường"", and if you're indecisive enough, ""masfsfsfsfrxj"" should become ""mạ"". ""Wasshington"" should become ""Washington"" rather than ""Wáington"" or ""Wahíngton"".
+
+Much of this can be accomplished with regular expressions, but it might be easier to shoehorn an existing Vietnamese IME into jquery.ime. AVIM.js is very reliable and is available under an MIT license, but no one really understands the core code. bogo.js [1] is much cleaner but much more limited and only available under the MPL. Mudim [2] is a bit cleaner and is GPL2-licensed but has its own limitations, like an input buffer (not ideal for Vietnamese) and poor support for VIQR.
+
+We'll definitely need support for a few input method-specific preferences, particularly tone mark placement (xóa vs. xoá) and spelling rule enforcement (Wahíngton vs. Washington).
+
+AVIM works pretty well with VisualEditor and other features, so at the Wikimedia wikis, the only real benefit to ULS integration would be getting an IME on Special: pages. (The current workaround is to install a system IME or browser extension, or to use a bookmarklet.) I wouldn't recommend adopting a simplistic keyboard layout even as a stopgap measure, because then it'd be forced upon the Vietnamese wikis and literally no one would want to use it.
+
+Full disclosure: I maintain a Firefox extension based on AVIM.js [3], but these comments are more from the perspective of a Vietnamese Wikipedian.
+
+[1] https://github.com/lewtds/bogo.js
+[2] https://code.google.com/p/mudim/
+[3] http://avim.1ec5.org/en/",1396520914,PHID-USER-sxpswmchfwxkuo2wszeo,False,PHID-TASK-6b35ocfdr4zn6ivnpbgr,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"targetFn.super = originFn;
+
+triggers a JS error in IE 8, and presumably in older versions of IE as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1396274940,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-avlkvijmssa6on3rse52,task_description,resolved
+OOjs: Should be parseable by ES3 engines,"Change 124360 merged by jenkins-bot:
+core: Use bracket notation for 'super' for ES3 compatibility
+
+https://gerrit.wikimedia.org/r/124360",1403116763,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"(In reply to Tisza Gergő from comment #12)
+> (In reply to Krinkle from comment #10)
+> > I know for a fact that ""throws"" is perfectly safe (for I did extensive
+> > research to verify it's safety going back to IE6 before adopting it un
+> > QUnit).
+> 
+
+We don't use throws outside unit tests (it's a method name for QUnit) and as said,
+it's perfectly safe back to IE6.",1403114342,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"(In reply to Krinkle from comment #10)
+> I know for a fact that ""throws"" is perfectly safe (for I did extensive
+> research to verify it's safety going back to IE6 before adopting it un
+> QUnit).
+
+It would be easy to fix, though: it is only used by sinon.js which supplies aliases for all ES3-incompatible function names. For throws() it is throwsException(), I think.",1403113010,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"(In reply to Gilles Dubuc from comment #9)
+> That plan looks good to me. Since this bug is still marked as low priority,
+> I imagine that you guys won't get around to it for at least a few months.
+> 
+> Since we're starting to work on UploadWizard and using OOJS for it will
+> probably be on our todo list, would you be comfortable letting us implement
+> ES3 support for OOJS the way you've just described? With you guys providing
+> active review on it, so that we're not blocked waiting for too long?
+> 
+> That's assuming that we'll decide to keep UploadWizard ES3-compatible, but I
+> want to see what our options will be.
+
+Sorry for not seeing this comment earlier; this looks to now essentially be done. We'll need to merge the ES3-parsability (gerrit 124360), release a new version of OOjs, and pull it into MediaWiki, with the new ES5 shim (gerrit 139308).
+
+
+(In reply to Krinkle from comment #10)
+> Enabling 'es3: true' in jshintrc shows that we're supposed to avoid ""throws""
+> (qunit), ""super"" (oojs) and ""static"" (oojs).
+> 
+> I know for a fact that ""throws"" is perfectly safe (for I did extensive
+> research to verify it's safety going back to IE6 before adopting it un
+> QUnit).
+> 
+> Running a test shows that ""static"" is safe as well. It's only ""super"".
+
+Is there a way we can get jshint to add an ""es3-actual"" flag so we can ensure that ES5-syntax-isms don't accidentally creep back into the codebase automatically?",1403107696,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"Enabling 'es3: true' in jshintrc shows that we're supposed to avoid ""throws"" (qunit), ""super"" (oojs) and ""static"" (oojs).
+
+I know for a fact that ""throws"" is perfectly safe (for I did extensive research to verify it's safety going back to IE6 before adopting it un QUnit).
+
+Running a test shows that ""static"" is safe as well. It's only ""super"".
+
+Test suite:  http://fiddle.jshell.net/bsz74/show/light/
+
+(source: http://jsfiddle.net/bsz74/)
+
+Test results via browserstack.com:
+* Windows 7 / IE 9: all pass
+* Windows 7 / IE 8: 1 failure (super)
+* Windows XP / IE 8: 1 failure (super)
+* Windows XP / IE 7: 1 failure (super)
+* Windows XP / IE 6: 1 failure (super)
+* Windows XP / Opera 12.10: all pass
+* Windows XP / Firefox 3: all pass
+* Windows XP / Safari 4: 1 failure (super)
+* Windows XP / Safari 5.0: 1 failure (super)
+* Windows XP / Safari 5.1: all pass
+* OSX 10.6 Snow Leopard / Safari 4: 1 failure (super)
+* OSX 10.6 Snow Leopard / Safari 5.0: 1 failure (super)
+* OSX 10.6 Snow Leopard / Safari 5.1: all pass
+* OSX 10.6 Snow Leopard / Firefox 4: all pass
+* iPhone 3GS / iOS 3: 1 failure (super)
+* iPhone 4 / iOS 4.0: 1 failure (super)
+* iPhone 4S / iOS 5.0: all pass",1403076951,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"That plan looks good to me. Since this bug is still marked as low priority, I imagine that you guys won't get around to it for at least a few months.
+
+Since we're starting to work on UploadWizard and using OOJS for it will probably be on our todo list, would you be comfortable letting us implement ES3 support for OOJS the way you've just described? With you guys providing active review on it, so that we're not blocked waiting for too long?
+
+That's assuming that we'll decide to keep UploadWizard ES3-compatible, but I want to see what our options will be.",1399544882,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"If .super were the only issue, then that could work. However that isn't the case.
+
+For one, there are a few more properties that aren't allowed in old browsers.
+
+And two, it isn't so much the property name but the functionality it provides that is missing in those browsers. Just a few off the top of my head:
+
+- Object.create
+- Array.isArray
+- JSON.stringify
+- Reliable hasOwnProperty (as used by isPlainObject)
+- Reliable typeof for native functions (as used by clone)
+
+Fixing .super will make the parser die slightly later, that's all.
+
+Fixing .super and the other properties will make the parser never die in IE8, but it will fail upon execution. Though execution is fine as long as you have a proper feature test (like VE has) before initialising too much.
+
+The ES5 methods OOjs uses (Object.create, Array.isArray, etc.) are perfectly polyfillable. I've always been very careful in OOjs to not adopt ES5 features that are fundamentally new language constructs that are cannot polyfill.
+
+However, just to explain that there is a little more to it. The exception you saw is just the tip of a small floe of ice. A small floe, but it won't melt on its own.
+
+So here's what I'd propose (in no particular order) for the medium to long term:
+
+- Make OOjs parseable in ES3 engines.
+
+- Document that OOjs is ES3 parser compatible, but does require ES5 features to be present. Consumer is responsible for providing a polyfill of their choosing if they need to support older browsers (write for the future, not the past).
+
+- Ship an ES5 shim in MediaWiki core which can be used as a dependency of oojs. And is conditionally loaded based on a quick feature test in a ResourceLoader dependency function that adds the dependency conditionally (this conditional dependency creation is a new feature in ResourceLoader's client js, however is not yet exposed on the server-side).
+
+
+This all of course is for OOjs core. OOjs UI makes much stronger use of browser behaviour (because it renders visually, polyfilling is generally not an option, it requires rigorous testing and adding of quirks and workaround for old browsers).
+
+For the short term:
+
+- OOjs currently requires ES5. *Do not load* this module in older browsers. It is the responsibility of the consuming code to feature test the environment before loading everything. This is why VisualEditor doesn't throw up in IE8.",1398786356,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"Change 124360 had a related patch set uploaded by Jforrester:
+core: Avoid an IE8 bug causing a fatal error when loaded on that platform
+
+https://gerrit.wikimedia.org/r/124360",1396892502,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"In case super still needs to be read/written for backwards compatibility, the syntax obj['super'] might work. Described here:
+http://tiffanybbrown.com/2013/09/10/expected-identifier-bug-in-internet-explorer-8/
+but a cursory search of the ES3 spec also suggests that this is valid.
+
+(I note that UploadWizard is apparently being converted to OOjs UI. Doing this while declaring IE 6-8 is not supported seems like a pretty horrible idea to me.)",1396573962,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"That fact could be made clearer in OOjs's README.md or a similar prominent place. I'm not sure that Mark knew this caveat at the time he embarked our project on the OOjs train. I think it would be very easy for another project to miss that fact as well. Resources.php is a really odd place if it's the sole warning.
+
+Full support aside, the fix to this bug is simply renaming ""super"". Seems like a quick win for potentially making Media Viewer available to more than 1 in 20 visitors who currently can't use it. I would have submitted a patch, but since this is the name of an important feature in your framework, I'd rather let you pick the new name.
+
+I understand that advanced WYSIWIG VE stuff is hard to do in ES3 and older, so ruling those browsers out for VE makes sense considering the effort/reward ratio. But what OOjs provides doesn't seem to me like it justifies ignoring 5%+ of our visitors, particularly if you're pushing for foundation-wide use of that framework (seems to be the reason why we ended up using it, anyway), since most features developed by the foundation don't do things as advanced as VE where older browsers are hard to support.
+
+I'm pretty sure that this bug right here is the only thing preventing OOjs ES3 support, at least for the subset of OOjs features that Media Viewer is using. I recall using Media Viewer fine in IE 6, 7 and 8 in January/February, which seems consistent with the timeline, considering that the code triggering the bug seems to have been introduced in March.
+
+If you fix this, you'll be getting continuous free help from us as a consumer of these frameworks when it comes to older IE support, because we'll be keeping an eye on it and submitting bug reports and patches when issues arise.",1396504506,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"ES3 compatibility isn't yet supported for OOjs, as stated in Resources.php.",1396461118,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"http://jsfiddle.net/PKdPz/1/embedded/result/
+
+browserstack/IE9: Pass
+browserstack/IE8: Fail
+     > Expected identifier
+
+Error details:
+ User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
+Timestamp: Wed, 2 Apr 2014 01:04:33 UTC
+
+ Message: Expected identifier
+ URI: http://fiddle.jshell.net/PKdPz/1/show/light/
+ Line: 33
+ Char: 7
+ Code: 0",1396400735,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Reserved_Words,1396278224,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+OOjs: Should be parseable by ES3 engines,"I think it could be as simple as renaming ""super"" to something else. It's most likely erroring because it's considered a reserved name.",1396276331,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-avlkvijmssa6on3rse52,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),"The needcheck tag on it.wp recently detected half a dozen dirty diffs like this one: https://it.wikipedia.org/w/index.php?title=Respirazione_olotropica&curid=856162&diff=65014587&oldid=64980151 .
+
+This seems to be due to a broken browser plugin, NortonInternetSecurityBF .
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1396015020,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-g5funys7osn7lmrgyu2r,task_description,resolved
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),We believe that this is now worked around.,1427402671,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),https://no.wikipedia.org/w/index.php?title=Bruker:Bredekg%C3%A5rd&diff=13459686&oldid=13459676,1413390853,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114019,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113113,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?),*** Bug 70537 has been marked as a duplicate of this bug. ***,1410130325,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-g5funys7osn7lmrgyu2r,task_subcomment,NA
+Show VisualEditor button label conditionally for GettingStarted tours,"Show the VisualEditor appendix conditionally for GettingStarted tours.  This is the same as {T63321}, but for GettingStarted tours.
+
+--------------------------
+**Version**: master
+**Severity**: normal",1395868740,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-7o7uuh5g6ufbb6vnjvbo,task_description,declined
+Show VisualEditor button label conditionally for GettingStarted tours,"#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.",1703380311,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-7o7uuh5g6ufbb6vnjvbo,task_subcomment,NA
+VisualEditor: Automatically generate an edit summary for the user,"On stack overflow there is a nice feature that guess edit summary for user based on what they changed. So that when you edit something edit summary isn't empty, but contains things like:
+
+Replace ""foo"" with ""bar""
+
+OR
+
+Inserted 20 words, removed 2 lines in paragraph ""blah""
+
+OR
+
+Punctuation fixes
+
+User is still able to modify it afterwards but this already save so much time. It would be nice if Visual Editor would do the same, so that users who do minor edits wouldn't need to bother with writing the summary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52859",1395865740,PHID-USER-ppytiem7rcsbnstfsrvq,False,PHID-TASK-buuem2aad2voq2wmr3vg,task_description,duplicate
+VisualEditor: Automatically generate an edit summary for the user,*** Bug 70285 has been marked as a duplicate of this bug. ***,1409665309,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-buuem2aad2voq2wmr3vg,task_subcomment,NA
+VisualEditor:  Web Thunder Helper Plugin (download) leaves garbage in pages,"See https://en.wikipedia.org/w/index.php?title=User:MGMT90018_Turnover/sandbox&curid=42095125&diff=599418792&oldid=599219453
+The ""Web Thunder"" plugin script from xunlei.com leaves the following litter at the top and bottom of pages:
+
+<embed id=""xunlei_com_thunder_helper_plugin_d462f475-c18e-46be-bd10-327458d045bd"" type=""application/thunder_download_plugin"" height=""0"" width=""0"" />
+
+<embed id=""xunlei_com_thunder_helper_plugin_d462f475-c18e-46be-bd10-327458d045bd"" type=""application/thunder_download_plugin"" height=""0"" width=""0"" />
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395856260,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ncw7c5qs6xrgoatblkas,task_description,resolved
+VisualEditor:  Web Thunder Helper Plugin (download) leaves garbage in pages,"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114016,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ncw7c5qs6xrgoatblkas,task_subcomment,NA
+VisualEditor:  Web Thunder Helper Plugin (download) leaves garbage in pages,"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113148,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ncw7c5qs6xrgoatblkas,task_subcomment,NA
+"VisualEditor: Link can be applied on Cite Web/Book/Newspaper/Journal templates (but not reference nodes), which is confusing","Screenshot
+
+Steps to reproduce:
+
+
+1.Open a page with VE
+2.Add a text then a Cite>Website/Book/Newspaper/Journal just after that 
+3.Now select both the text and the cite
+4.Apply link on it
+
+Observed Result:
+The link also gets applied on the Cite
+
+See the screenshot attached
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Reference_numbering?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13245}",1395787260,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-4sxb362teoe7szw6jzp3,task_description,open
+"VisualEditor: Link can be applied on Cite Web/Book/Newspaper/Journal templates (but not reference nodes), which is confusing",For templates we may need to have some kind of function that dynamically determines whether the template is linkable :(,1401925015,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4sxb362teoe7szw6jzp3,task_subcomment,NA
+"VisualEditor: Link can be applied on Cite Web/Book/Newspaper/Journal templates (but not reference nodes), which is confusing","This is hard to fix. Blacklisted annotation types are done on a per-node-type basis. Normal references are of type 'mwReference', but citations are of type 'mwTransclusionInline', and I don't think it's a good idea to make all templates unlinkable.",1401924989,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4sxb362teoe7szw6jzp3,task_subcomment,NA
+VisualEditor: IE9 doesn't load new page when when re-editing a page modified in another browser,"To reproduce:
+
+1. Load a page in IE in the visual editor.
+2. Load the same page in another browser, make a change, and save it.
+3. Load the page view in IE, confirm you can see the edit.
+4. Click ""Edit"" to enable the visual editor.  Old content appears in the editor.
+5. Quit IE and restart.  Load page to edit in VE.  See new content in the editor.
+
+Initially I thought this was simply a server configuration issue (and maybe it still is), but I tested the same thing in FF and got the new page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395704460,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-gyj6luke5ayhahap6efm,task_description,invalid
+VisualEditor: IE9 doesn't load new page when when re-editing a page modified in another browser,"Sounds like it may have been resolved in another task, so resolving invalid. Please reopen if this is still an issue",1436996751,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-gyj6luke5ayhahap6efm,task_subcomment,NA
+VisualEditor: IE9 doesn't load new page when when re-editing a page modified in another browser,"Krenair writes:
+
+> Is this still a problem? Sounds like IE is caching wrongly?
+
+I doubt this is a problem now since {{T74480}} is resolved.",1436995874,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-gyj6luke5ayhahap6efm,task_subcomment,NA
+VisualEditor: IE9 doesn't load new page when when re-editing a page modified in another browser,Is this still a problem? Sounds like IE is caching wrongly?,1436994533,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-gyj6luke5ayhahap6efm,task_subcomment,NA
+VisualEditor: IE9 places cursor inside ce=false table cell,"With the following wikitext:
+
+  __NOTOC__ 
+
+  This is a test
+
+  {|
+  |-
+  | valign=""top"" | 
+  == Header  ==
+  * point one
+  * point two
+  ...
+
+VE starts up with the cursor on ""This"".  Pressing down once in FF ends up with the cursor on the ""Header"" line.  In IE, it ends up on the ""point one"" line.  Pressing up once in IE then puts the cursor on the ""Header"" line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1395703680,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-selst62j4vfcyd5gk5mu,task_description,declined
+VisualEditor: IE9 places cursor inside ce=false table cell,IE9 support has been dropped: T162277,1491506647,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-selst62j4vfcyd5gk5mu,task_subcomment,NA
+VisualEditor: IE9 places cursor inside ce=false table cell,Cursoring into a table cell in IE9 now takes you inside the cell and lets you edit it. This is still wrong: it should create a table selection highlighting the first cell.,1460637599,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-selst62j4vfcyd5gk5mu,task_subcomment,NA
+VisualEditor: IE9 places cursor inside ce=false table cell,"(In reply to Roan Kattouw from comment #1)
+> This is working as expected now. Pressing down once puts the cursor at the
+> beginning of ""Header"" on my Windows 7 machine in IE10.
+
+...but of course this bug was filed against IE9. I'm blind.",1409961316,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-selst62j4vfcyd5gk5mu,task_subcomment,NA
+VisualEditor: IE9 places cursor inside ce=false table cell,"This is working as expected now. Pressing down once puts the cursor at the beginning of ""Header"" on my Windows 7 machine in IE10.",1409961194,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-selst62j4vfcyd5gk5mu,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","From the console:
+
+ SCRIPT70: Permission denied 
+ Main_Page, line 1 character 1
+
+Filing to track this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1395701760,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_description,resolved
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","Change 283427 merged by jenkins-bot:
+Fix access of iframe-created document in IE9
+
+[[https://gerrit.wikimedia.org/r/283427]]",1461009288,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","Change 283427 had a related patch set uploaded (by Esanders):
+Fix access of iframe-created document in IE9
+
+[[https://gerrit.wikimedia.org/r/283427]]
+",1460636680,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","The iframe which is used to create the document is discarded and IE9 garbage collects it and wipes the document, even though we keep a pointer to the document.",1460636101,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","For the record, I haven't experienced this problem in weeks of messing around with VE in IE in either IE10 or IE11.",1409961388,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","Updated to latest VE (which shares MW's JQuery?) and saw the problem again.  Clicked IE's ""Start debugging"" in IE9 and wasn't able to reproduce it.
+
+Returned to page, clicked IE's ""Stop debugging"" and then clicked VE's ""Edit"".  Spinner went into infinite loop.
+
+Now, what are the dev tools setting up to cause this behavior?",1397145638,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","Created attachment 14910
+diff of changes to update jquery
+
+**Attached**: {F13122}",1395795363,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated",Got past part of the permission problem without messing with the registry (yay!) by looking at newer jQuery code and seeing how it avoided use of iframe.  It is now stopping in setUpSurface.,1395795311,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated",*** Bug 63043 has been marked as a duplicate of this bug. ***,1395784399,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+"VisualEditor: Console shows ""Permission denied"" on IE9 when VE is first initiated","So after poking around for a bit I was able to get past this error with the following registry key set to ""1"":
+
+  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN
+  \FeatureControl\FEATURE_PROTOCOL_LOCKDOWN\iexplore.exe
+
+Isn't IE support fun?
+
+Now the save button (bug #63043) changes color but clicking it results in ""SCRIPT70: Permission denied"" that IE's debugger says comes from the following line in jquery.js:
+
+    proxy=function(){
+        return fn.apply(context,args.concat(core_slice.call(arguments)));
+    };
+
+Hints on registry keys from http://stackoverflow.com/questions/5352057/script70-permission-denied-ie9
+
+Looks like there may be some help in the newer versions of jquery: http://bugs.jquery.com/ticket/13936",1395784324,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-rblj4bx5jecyxjn2maza,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),"Typing return to generate a new paragraph in FF works.  Filing this to ask for a pointer to figure out how I might track it down and fix it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1395701460,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_description,resolved
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),WFM in 9. 8 is not supported.,1460637023,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),"I was testing against IE8 or 9.  I've since upgraded that machine to 11, so it isn't available now.",1410029146,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),Works in IE10 too. Which version of IE did you observe this in?,1409961424,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),"Fixed in IE11, at least.",1409099678,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: Can't create new paragraph by hitting return in IE9(?),still needs some tracking down for a reproducible case.,1395770447,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-mrlzc7cbjms7mrkftzkz,task_subcomment,NA
+VisualEditor: User should be able to add gallery inside reference,"Right now, Users can add image inside reference dialog box, similarly they should be able to add gallery inside it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395687900,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-7jtvwd2g3x4hb6rhdnxy,task_description,open
+VisualEditor: User should be able to add gallery inside reference,I'm not sure that's something we want to encourage?,1445614649,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-7jtvwd2g3x4hb6rhdnxy,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395097920,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rsayshdqztdym7km5qd3,task_description,resolved
+"VisualEditor: Get rid of $.proxy, use native .bind()",Removal of this function is punted to bug 72156.,1413498289,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 167055 merged by jenkins-bot:
+Replace calls to ve.bind( fn, ... ) with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/167055",1413497045,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 167055 had a related patch set uploaded by Alex Monk:
+Replace calls to ve.bind( fn, ... ) with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/167055",1413488877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 166155 merged by jenkins-bot:
+Replace calls to OO.ui.bind( fn, ... ) with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/166155",1413483227,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 166155 had a related patch set uploaded by Alex Monk:
+Replace calls to OO.ui.bind( fn, ... ) with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/166155",1412984168,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Alex Monk from comment #15)
+> (In reply to Krinkle from comment #14)
+> > VisualEditor core, and OOjs UI.
+> 
+> Me and Krinkle spoke about this and think it would be a better idea to defer
+> this for now. PhantomJS is not implementing Function#bind (like we would
+> expect) and that's necessary for the tests to succeed. In other repos we get
+> around this by loading es5-shim but in these ones we should be able to rely
+> on ES5 properly.
+
+With I64a0bd96b in VE-core and If2da01a25 in OOUI this is no longer a blocker.",1412975453,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Krinkle from comment #14)
+> VisualEditor core, and OOjs UI.
+
+Me and Krinkle spoke about this and think it would be a better idea to defer this for now. PhantomJS is not implementing Function#bind (like we would expect) and that's necessary for the tests to succeed. In other repos we get around this by loading es5-shim but in these ones we should be able to rely on ES5 properly.",1405360443,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Alex Monk from comment #13)
+> (In reply to Krinkle from comment #7)
+> > We now have the polyfill for Function.prototype.bind provided by MediaWiki
+> > so this should be easier to do now.
+> 
+> Heh.
+> 
+> Anyway, is there anything else to do here?
+
+VisualEditor core, and OOjs UI.",1405001970,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Krinkle from comment #7)
+> We now have the polyfill for Function.prototype.bind provided by MediaWiki
+> so this should be easier to do now.
+
+Heh.
+
+Anyway, is there anything else to do here?",1405001884,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 144840 merged by jenkins-bot:
+Replace ve.bind( fn, ... ) calls with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/144840",1405001506,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to Krinkle from comment #10)
+> Why? How is this different from the other ES5 methods we've been using
+> already? VisualEditor nor OOjs UI support ES3 engines afaik.
+> 
+> MediaWiki itself does, and OOjs core does (for other consumers of OOjs). But
+> we don't (we user .super which breaks IE's ES3 parser, Array.isArray,
+> Object.keys etc.)
+> 
+> mw-ve, ve-core, oojs-ui, and oojs all share a requirement for ES5
+> environments beyond just the polyfillable methods.
+
+oojs-core supports ES3 engines but requires an ES5 shim. The same would apply to OOjs UI and/or VisualEditor core if and when we decide to support older browsers.",1404931697,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Why? How is this different from the other ES5 methods we've been using already? VisualEditor nor OOjs UI support ES3 engines afaik.
+
+MediaWiki itself does, and OOjs core does (for other consumers of OOjs). But we don't (we user .super which breaks IE's ES3 parser, Array.isArray, Object.keys etc.)
+
+mw-ve, ve-core, oojs-ui, and oojs all share a requirement for ES5 environments beyond just the polyfillable methods.",1404930429,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()",If we're going to replace ve.bind it should be done in ve core first so we'll need a polyfill there. In ve-mw we can omit that polyfill as mw loads it's own.,1404930088,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Change 144840 had a related patch set uploaded by Alex Monk:
+Replace ve.bind( fn, ... ) calls with fn.bind( ... )
+
+https://gerrit.wikimedia.org/r/144840",1404858922,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()",We now have the polyfill for Function.prototype.bind provided by MediaWiki so this should be easier to do now. Simply replace all uses of $.proxy(fn..) and ve.bind(fn) in the modules/ directory with calls to fn.bind(..).,1404774724,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Sorry, I got bit busy with my other project.",1403335083,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()",Ping on this bug again – do you need any support/advice/help?,1400888892,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","> (In reply to James Forrester from comment #1)
+> > Tony, are you planning to take on this bug?
+> 
+> I plan to. But is there anything like bind() is only present in modern
+> browsers ?
+
+Indeed, Function.prototype.bind is new in ECMAScript 5, which VisualEditor requires. Or rather, VE requires ECMAScript 3 syntax engine and an environment that somehow provides certain ES5 features, which can potentially be polyfilled. We don't yet (and that is by design), adopt any ES5 syntax or ES5 features that can't be polyfilled.
+
+This is already guarded against using the feature test in our mw integration init[1], so you can rely on this without having to worry about old browsers.
+
+(In reply to Roan Kattouw from comment #3)
+
+I'd recommend #2 for consistency (we do the same with other ES5 features we've adopted) and minor performance micro optimisation (extra global and property, extra callstack because it has to be a proxy calling bind, unlike Array.isArray is can't be assigned to ve.bind by reference because bind needs to be bound itself) and because we're already using '.bind' in a few places.
+
+But keeping ve.bind with a small wrapper to bind using bind seems fine for backwards compatibility with ve plugins in the wild. But I'd recommend we don't use this in core.
+
+[1] https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/7e52a1ab2ab514/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js#L74-L93",1395199898,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","We don't use $.proxy() directly in the VE code base, instead we set ve.bind = $.proxy; and use ve.bind().
+
+Yes, this.keyup.bind() exists in modern browsers. It doesn't exist in older browsers, but we don't really care because VE doesn't support browsers that old for lots of other reasons anyway.
+
+There are two ways we could approach this. I'll ask Krinkle which one he thinks is best before we proceed.
+
+#1 is to migrate uses of ve.bind( this.foo, this ); to this.foo.bind( this ); across the code base, then deprecate and later remove ve.bind(). This would be pretty laborious.
+
+#2 is to change ve.bind() to a wrapper that uses native .bind(). This will change every single function binding in the entire codebase to use native bind instantaneously.
+
+My guess it's probably best to do #2 first, then #1 later, but I'd like Krinkle to weigh in on this.",1395166498,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","(In reply to James Forrester from comment #1)
+> Tony, are you planning to take on this bug?
+
+I plan to. But is there anything like bind() is only present in modern browsers ? 
+will replacing, say 
+this.$element.on( 'keypress', $.proxy( this.keyup, this ) )
+with 
+this.$element.on( 'keypress', this.keyup.bind(this)) will do the trick ?",1395165708,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+"VisualEditor: Get rid of $.proxy, use native .bind()","Tony, are you planning to take on this bug?",1395164794,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rsayshdqztdym7km5qd3,task_subcomment,NA
+VisualEditor: Clean up SurfaceObserver usage,"ve.ce.Surface contains a bunch of calls to stopTimerLoop() and startTimerLoop() that are unnecessary and seem to have been added based on the false assumption that JavaScript can be multithreaded.
+
+There are also duplicate calls to pollOnce that seem unneeded, or only exist to update state post-modification. We should audit these.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1395097080,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2gy2ywwq2p5i63mtdvsz,task_description,open
+VisualEditor: Its possible to input a fraction value (with decimal point) in image size which results into showing wrong size in the review changes section,"Setting decimal value
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert a new image
+3.Set the image size to a long value which becomes a number with scientific notation 
+4.Now start deleting the value from right to left
+5.Once you have deleted the scientific notation (e) and the number becomes a value with decimal point , click on ""Apply Changes""
+
+Observed Issue 1: it accepts that decimal value
+
+6.Click on Save Page and go to ""Review your Changes""
+
+Observed Issue 2: The size value showing in the review changes section are completely different that what was set in step 5
+
+See the screenshots attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=17marchff&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F13038}",1395095100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5rr6tldo3g3davlgjzkz,task_description,resolved
+VisualEditor: Its possible to input a fraction value (with decimal point) in image size which results into showing wrong size in the review changes section,Verified the fix in production,1400012238,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5rr6tldo3g3davlgjzkz,task_subcomment,NA
+VisualEditor: Its possible to input a fraction value (with decimal point) in image size which results into showing wrong size in the review changes section,This doesn't happen anymore with the new MediaSizeWidget and the DimensionsWidget; they don't allow for decimal values at all.,1399571426,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-5rr6tldo3g3davlgjzkz,task_subcomment,NA
+VisualEditor: Its possible to input a fraction value (with decimal point) in image size which results into showing wrong size in the review changes section,"Created attachment 14843
+The discrepancy in review changes section
+
+**Attached**: {F13040}",1395095198,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5rr6tldo3g3davlgjzkz,task_subcomment,NA
+VisualEditor:  What you put into the template editor is not what it gives back (more Babel box bugs),"Intention:
+Edit a Babel box that I'd just created.
+
+Steps to Reproduce:
+1. Create a Babel box using the workaround described in bug 62740 {T64740}.
+
+2. Apply changes.
+
+3. Select the transclusion and click the puzzle icon to edit it again.
+
+4. It looks confusingly different.
+
+
+Expected Results:  
+If it can't add the function, then how is it able to edit it?  And if it can edit it, then why can't it add it normally?
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1395083820,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gpxl6tetek6gnjsolbm6,task_description,open
+VisualEditor:  What you put into the template editor is not what it gives back (more Babel box bugs),"Created attachment 14840
+Screenshot showing editing of Babel box
+
+**Attached**: {F13026}",1395083945,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gpxl6tetek6gnjsolbm6,task_subcomment,NA
+VisualEditor:  What you put into the template editor is not what it gives back (more Babel box bugs),"Created attachment 14839
+Screenshot showing creation of Babel box
+
+**Attached**: {F13025}",1395083916,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gpxl6tetek6gnjsolbm6,task_subcomment,NA
+VisualEditor:  Create a sensible system for adding Babel boxes (parser functions),"Intention:
+Add a Babel box
+
+Steps to Reproduce:
+1. Go to Insert > Template
+
+2. Type in #babel:en
+
+3. Click ""Add template"".
+
+4. Nothing happens.
+
+
+Expected Results:  
+Either it ought to Just Work™, or it ought to produce an error message about VisualEditor not supporting parser functions yet (see bug 50855).
+
+Reproducible: Always
+
+Workaround:  Go to complex transclusion mode; add ""Content""; paste in wikitext source code for the parser function.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49996",1395078720,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-d27naw46rmmwvpednony,task_description,open
+VisualEditor:  Create a sensible system for adding Babel boxes (parser functions),"Created attachment 14836
+Screenshot showing exactly what was in the template name field when it didn't work
+
+**Attached**: {F13013}",1395079025,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-d27naw46rmmwvpednony,task_subcomment,NA
+VisualEditor: Merge the media editing and gallery editing dialogs,Moved out of T40129's wishlist into its own bug.,1394835240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hkmxueiu32djdjwjf6qe,task_description,declined
+VisualEditor: Merge the media editing and gallery editing dialogs,">>! In T64677#2710576, @Tchanders wrote:
+> I suspect the real problem is that the media dialog is more mature, so a better solution in my opinion would be to work on improving the gallery dialog.
+
+Makes sense to me.",1519404558,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-hkmxueiu32djdjwjf6qe,task_subcomment,NA
+VisualEditor: Merge the media editing and gallery editing dialogs,"I'm not sure I agree with doing this, since media and galleries have such different functionalities. E.g. a media item is only chosen once, whereas galleries can be extended, pruned, rearranged, etc. The media display options are quite different from the gallery display options too, and a media item might not even be an image. I think a single dialog that incorporated all of this would lead to a confusing user experience, with too many alternative workflows and options being disabled according to whether whether media or gallery behaviour was required.
+
+I suspect the real problem is that the media dialog is more mature, so a better solution in my opinion would be to work on improving the gallery dialog.
+
+",1476304111,PHID-USER-abybinou47zwmsranndg,True,PHID-TASK-hkmxueiu32djdjwjf6qe,task_subcomment,NA
+VisualEditor: Be able to set a over-ride link target (link=…) in the media edit dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834760,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-co3ofwxr32imhzpdqgr6,task_description,open
+"VisualEditor: Centred images can appear in VE as overlapped by another image, then can't be selected","screenshot attached
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image 
+3.Insert another image just after it which is smaller than the previous one
+4.Now align the first one to the left
+5.Now align the second one to Centre 
+
+Observed Result:
+
+The smaller image overlaps with the previous bigger one in VE.If you save it and reopen the editor, you wont be able to see the image to select it.
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Widthnullagainalways
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62850
+
+**Attached**: {F13301}",1394666940,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-36q4opdcfxqgzrfpkocm,task_description,resolved
+"VisualEditor: Centred images can appear in VE as overlapped by another image, then can't be selected",I can't reproduce this issue anymore. We must have accidentally fixed it.,1521586640,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-36q4opdcfxqgzrfpkocm,task_subcomment,NA
+"VisualEditor: Centred images can appear in VE as overlapped by another image, then can't be selected",See also {T104540}.,1465387417,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-36q4opdcfxqgzrfpkocm,task_subcomment,NA
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE","Steps to reproduce:
+
+1.Open a page in VE
+2.Edit the page
+3.Switch to Edit Source mode
+
+Observed Result:
+In the console : an error is appearing :""Uncaught TypeError:Cannot read property cleardiff of null"".
+However, it does not hamper the functionality of switching/saving the page
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394564520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jyohwwldty3v4wbuw5lo,task_description,resolved
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE",Verified the fix in production:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit,1395350548,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jyohwwldty3v4wbuw5lo,task_subcomment,NA
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE",Verified the fix in test2:https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&veaction=edit,1394843693,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jyohwwldty3v4wbuw5lo,task_subcomment,NA
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE","Change 118331 merged by jenkins-bot:
+Fix JS error trying to access this.saveDialog from switch to source mode code path
+
+https://gerrit.wikimedia.org/r/118331",1394672171,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jyohwwldty3v4wbuw5lo,task_subcomment,NA
+"VisualEditor: ""Cannot read property cleardiff of null "" appearing while switching to Edit Source mode from VE","Change 118331 had a related patch set uploaded by Catrope:
+Fix JS error trying to access this.saveDialog from switch to source mode code path
+
+https://gerrit.wikimedia.org/r/118331",1394651238,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jyohwwldty3v4wbuw5lo,task_subcomment,NA
+Possibly unintended splitting of a table into two tables using VE,"Isn't VisualEditor supposed to be able to edit only the content of the table cells but not change the table structure? If so, I believe this should not happen:
+https://pt.wikipedia.org/w/index.php?diff=38365876&uselang=en
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394487120,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-jq2yekad4c4aywwp7b2x,task_description,resolved
+Possibly unintended splitting of a table into two tables using VE,"Table editing has changed dramatically since this bug was filed (for example, the visual editor //can// now change the table structure), so I'm closing. Reopen if you can still reproduce.",1437696255,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-jq2yekad4c4aywwp7b2x,task_subcomment,NA
+Possibly unintended splitting of a table into two tables using VE,I'm setting this task's status to stalled as long as clear steps to reproduce are not known (plus this issue is now a year old).,1425508205,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jq2yekad4c4aywwp7b2x,task_subcomment,NA
+Possibly unintended splitting of a table into two tables using VE,"I'm not sure how the anonymous user managed to do that.
+
+Since the edit was marked with ""Tag: VisualEditor"", I assume the user didn't change to the wikitext editor after he started his changes (in that case it would be marked as ""VisualEditor: Switched"", I think).",1421679090,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-jq2yekad4c4aywwp7b2x,task_subcomment,NA
+Possibly unintended splitting of a table into two tables using VE,"Any specific steps that resulted in a broken table? And the table was edited **only** in VE? 
+
+",1421451161,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-jq2yekad4c4aywwp7b2x,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","It seems to be possible to get the Parsoid HTML/RDF output through the standard Mediawiki API, but I can't figure out how.
+
+For example, this fails:
+https://en.wikipedia.org/w/api.php?action=visualeditor&paction=parse&page=Main_Page&oldid=598252063
+
+An example would be really helpful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61017",1394363280,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_description,resolved
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","Change 166519 merged by jenkins-bot:
+Mark action=visualeditor as an internal API
+
+https://gerrit.wikimedia.org/r/166519",1413246504,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","Change 166519 had a related patch set uploaded by Jforrester:
+Mark action=visualeditor as an internal API
+
+https://gerrit.wikimedia.org/r/166519",1413246389,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","I took the upstream bug in MW core, might as well take this as well.",1409874589,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use",Have filed bug 62905 in MW's API to make this possible.,1395361895,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","I see some kind of contradiction in proposing an API on one side  action=visualeditor @https://en.wikipedia.org/w/api.php and on the other side telling ""this is a private API"".
+
+I fully understand that this is a work in progress, and thank you very much for you explanation Gabriel. But, IMO the current VE related API status is really puzzling for someone which is not embeded in the Parsoid/VE project.
+
+Why not simply remove this documentation (action=visualeditor) as long as this is not really working for everybody?
+
+NB: Regarding the Parsoid/API integration work itself, I think there is an other bug open somewhere about that.",1394531723,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","(In reply to James Forrester from comment #2)
+> Should this be the Parsoid bug for that, then?
+
+My understanding is that this bug is about the VE API. http://parsoid-lb.eqiad.wikimedia.org/ links to the documentation at https://www.mediawiki.org/wiki/Parsoid#The_Parsoid_web_API, which has at least one example. This bug can probably be closed, but good to wait for Emmanuel's input.",1394473837,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","(In reply to Gabriel Wicke from comment #1)
+> The VE interface is private and not intended as a public / stable Parsoid
+> API. It just proxies to http://parsoid-lb.eqiad.wikimedia.org/ and adds some
+> more VE-specific information that is not needed if all you are interested in
+> is the content. As it spins up an extra PHP worker it is also slower than
+> accessing the Parsoid API directly.
+> 
+> The Parsoid API will be integrated in a new REST content API in the longer
+> term. The URL will change at some point later this year, but the principle
+> will remain the same.
+
+Should this be the Parsoid bug for that, then?",1394471745,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use","The VE interface is private and not intended as a public / stable Parsoid API. It just proxies to http://parsoid-lb.eqiad.wikimedia.org/ and adds some more VE-specific information that is not needed if all you are interested in is the content. As it spins up an extra PHP worker it is also slower than accessing the Parsoid API directly.
+
+The Parsoid API will be integrated in a new REST content API in the longer term. The URL will change at some point later this year, but the principle will remain the same.",1394465623,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-akuuuyc2bjx7xjtcjegr,task_subcomment,NA
+VisualEditor:  Advanced transclusion editor for complex templates eats parameters,"If you have a complex transclusion (e.g., a succession box), and you try to rearrange the order of the items, and if one or more of those items is a template that contains a parameter, then some or all of the parameter-containing templates will silently disappear.
+
+See https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_1#Add_content_and_other_transclusion_mysteries for complaints.
+
+
+Diffs of resulting problems:
+
+https://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=596891776&oldid=596891699
+
+https://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=597044161&oldid=596891923
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1394238840,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-foq2smoax4kgl2mj4anq,task_description,open
+VisualEditor:  Advanced transclusion editor for complex templates eats parameters,"Tested it in test2. 
+
+- By rearranging templates via moving them in Transclusion box, I was not able to separate template parameters - e.g. to make {{s-bef|before = [[Leonardo Domenici]]}}  --> {{s-bef|before = }}.
+ - Also tried the exact steps on https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_1#Add_content_and_other_transclusion_mysteries:
+""Example: here all I did was use the ""up"" button four times: ""up"" the lowest ""content"", ""up"" the lowest s-aft, ""up"" the lowest ""content"" again, try to ""up"" the lowest s-aft again. Result when you want to save it: the s-aft has simply vanished :-)""
+
+It was non-reproducible  - either the issue is resolved or I am not inventive enough :(  I'd like someone else to take a look at the issue - hence I've assigned some priority to it.",1426618431,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-foq2smoax4kgl2mj4anq,task_subcomment,NA
+VisualEditor: Empty references created in wikitext editor should be allowed to edit in VE,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with wikitext editor
+2.Insert an empty reference for example: empty reference<ref />
+3.Save the page
+4.Now open the page with VE
+
+Observed Result:
+It does not let you edit the empty reference you just added and shows an error ""This reference is defined in a template or other generated block and for now can only be edited in source mode""
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Newpagereference?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F12863}",1394220660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nhzlsr5aycf5vf4abhj6,task_description,open
+VisualEditor: Empty references created in wikitext editor should be allowed to edit in VE,"I just tried at http://en.wikipedia.beta.wmflabs.org/wiki/0.24595949980612886 and the reference can be edited now, but shows the ""disallowed"" cursor on hover.",1422564675,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nhzlsr5aycf5vf4abhj6,task_subcomment,NA
+"VisualEditor: Save dialog throws ""Uncaught TypeError: Cannot read get getModel of undefined"" (IE9)","Screenshot of bug.
+
+Encountered in IE9 using BrowserStack ""Windows 7/IE9"" using latest MediaWiki and VisualEditor master via a tunnel. Could either be a browser bug we have to work around, or something on our end applicable to other browsers as well.
+
+* Edit a simple document.
+* Add two characters at the start.
+* ""Save page"" enables itself.
+* Click it.
+
+Uncaught exception:
+
+> “Unable to get value of property ‘getModel’: object is null or undefined”.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13345}",1394128380,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vtqdjdocmtgvoothuoyh,task_description,resolved
+"VisualEditor: Save dialog throws ""Uncaught TypeError: Cannot read get getModel of undefined"" (IE9)",Works now.,1461148540,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vtqdjdocmtgvoothuoyh,task_subcomment,NA
+"VisualEditor: Save dialog throws ""Uncaught TypeError: Cannot read get getModel of undefined"" (IE9)","> I get bug 63039 first:
+Which is T65039 and has a patch for review.",1460637918,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vtqdjdocmtgvoothuoyh,task_subcomment,NA
+"VisualEditor: Save dialog throws ""Uncaught TypeError: Cannot read get getModel of undefined"" (IE9)","I'm unable to reproduce this bug because before it even gets anywhere, I get bug 63039 first:
+
+> ""SCRIPT70: Permission denied"", /Main_Page, line 1 character 1",1412209087,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vtqdjdocmtgvoothuoyh,task_subcomment,NA
+VisualEditor: Weird repetition when using the editor in IE9,"Screenshot of bug.
+
+Encountered in IE9 using BrowserStack ""Windows 7/IE9"" using latest MediaWiki and VisualEditor master via a tunnel. Could either be a browser bug we have to work around, or something on our end applicable to other browsers as well.
+
+
+* Load up the ""Worksheet"" page.
+* Trying to put the cursor in the first paragraph and add text.
+
+It repeats the first sentence many times and causes various weird scroll/focus events to occur all over the document.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13343}",1394128140,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n3l4te5qxvaeoc3fey5b,task_description,declined
+VisualEditor: Weird repetition when using the editor in IE9,IE9 support has been dropped: T162277,1491506596,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-n3l4te5qxvaeoc3fey5b,task_subcomment,NA
+VisualEditor: Weird repetition when using the editor in IE9,"Haven't yet narrowed down, vague subject for now.",1394128538,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n3l4te5qxvaeoc3fey5b,task_subcomment,NA
+VisualEditor:  Why doesn't the Insert menu in the main editor have the same order as the Insert menu in the Image caption editor?,"Open VisualEditor.  Click 'Insert'.  First item in the main Insert menu:  Reference.  
+
+Open (or insert) and image.  Under the Caption, click 'Insert'.  First item:  Language.
+
+Reference is still the most important item, and should be listed first.  (Should ""image"" even be listed at all?  It works, if you only go one deep, but...)
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1394058960,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-s24smc5kqzdyl5pvlpcz,task_description,resolved
+VisualEditor:  Why doesn't the Insert menu in the main editor have the same order as the Insert menu in the Image caption editor?,"Change 117101 merged by jenkins-bot:
+Make the order of insert tools consistent in dialogs
+
+https://gerrit.wikimedia.org/r/117101",1394060524,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-s24smc5kqzdyl5pvlpcz,task_subcomment,NA
+VisualEditor:  Why doesn't the Insert menu in the main editor have the same order as the Insert menu in the Image caption editor?,"Change 117101 had a related patch set uploaded by Catrope:
+Make the order of insert tools consistent in dialogs
+
+https://gerrit.wikimedia.org/r/117101",1394059854,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-s24smc5kqzdyl5pvlpcz,task_subcomment,NA
+VisualEditor:  Why doesn't the Insert menu in the main editor have the same order as the Insert menu in the Image caption editor?,"So in general, the menus are supposed to be different for exactly the reason you hinted at: there are things you can't do in an image caption or in a reference. That said, the order should probably be consistent. This is likely to just be an oversight (the lists are maintained completely separately, which is kind of horrible) rather than anything intentional, but I'll double-check with James to make sure.",1394059451,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-s24smc5kqzdyl5pvlpcz,task_subcomment,NA
+VisualEditor: Shortcut system should support shifted punctuation characters,"Right now there is no way to express Ctrl+? in the trigger system. Attempting to type that on my keyboard registers as Ctrl+Shift+/ , but that's only because my keyboard layout is such that ? is above /. There should be a way to express Ctrl+? independent of the keyboard layout.
+
+This may not be easy to do because Trevor tells me that charCode is less reliable than keyCode, so we may not be able to detect this correctly.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394056560,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-y76rhjbfn2sjvcyboyko,task_description,open
+"VisualEditor: Allow enablement of VE on pages whose titles are matched by regexps, editable through an interface message","Pages like:
+* documentation - [[Template:Terminal/doc]]
+* Wikipedia namespace = [[Wikipedia:Manual of Style]]
+
+Note that on many wikis there are custom subpages (like /doc) or namespaces which visual editing should be configurable.
+I suggest MediaWiki interface - [[MediaWiki:Visualeditor-editable-pages]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393669740,PHID-USER-b27lopawgf2h6utuuqyi,False,PHID-TASK-wx2s3qbnx44xiegmal63,task_description,open
+"VisualEditor: ""TypeError: $domNode.closest(...).data(...) is undefined"" appears while dragging an image inside Media Settings and Reference dialog box","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Open a reference dialog or Media Settings for an image
+3.Insert two images inside that dialog.
+4.Now drag one of them
+
+Observed Result:
+
+Observe that, the shadow of the image appears from the corner of CE instead of the dialog.Also an error appears after dragging the image shadow over itself:
+TypeError: $domNode.closest(...).data(...) is undefined
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=New_pageon%24&gettingStartedReturn=true&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13253}",1393553040,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-kg4z3siwsfs5p4zwouaz,task_description,open
+Slashes in titles should be escaped when generating links,"**Author:** `vigna`
+
+**Description:**
+Some Wikipedia pages contain slashes in their title, e.g., ""/b/"" or ""/dev/null"". Such slashes should be escaped to %2F when they are not meant to separate paths components, as per RFC 1738/3986. Instead, for instance,
+
+http://en.wikipedia.org/w/index.php?title=B/&redirect=no
+
+contains an A element
+
+<a href=""/wiki//b/"" title=""/b/"">/b/</a>
+
+that should written
+
+<a href=""/wiki/%2Fb%2F"" title=""/b/"">/b/</a>
+
+
+This causes 2 problems:
+
+1) The URL above does not conform to the RFCs. This is a minor issue but it might rise other problems in the future.
+
+2) If the slash is initial, the URI is not normalized as per RFC. E.g., in Java
+
+bsh % print(URI.create(""wiki//b/"").normalize());
+wiki/b/
+
+This might be a problem with crawlers, which usually normalize URLs to reduce the number of duplicates.
+
+
+
+Note that %2F-escaped slashes work perfectly, and 
+
+http://en.wikipedia.org/wiki/%2Fb%2F
+
+brings you exactly to /b/'s page. Bug 8254 seems to say the opposite, but it's a few years old.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1393411620,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-er23tg3bi4off4fieogn,task_description,open
+Slashes in titles should be escaped when generating links,"**vigna** wrote:
+
+What I mean is that the Wikipedia text contains links like [[/b/]]. That is, the user will input the title of a page. But then some code will turn this title into a link: it shouldn't be http://en.wikipedia.org/wiki//b/, but rather http://en.wikipedia.org/wiki/%2Fb%2F . 
+
+Maybe the page above wasn't a good example. Consider
+
+http://en.wikipedia.org/wiki/Cory_Doctorow
+
+The reference entry for /usr/bin/god in the ""Other"" section is
+
+* ''[[/usr/bin/god]]'' (novel; Tor Books)
+
+The link generated by the Wikimedia software (or whoever is in charge :) is
+
+<a href=""/wiki//usr/bin/god"" title=""/usr/bin/god"">/usr/bin/god</a>
+
+This should be
+
+<a href=""/wiki/%2Fusr%2Fbin%2Fgod"" title=""/usr/bin/god"">/usr/bin/god</a>",1393418640,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-er23tg3bi4off4fieogn,task_subcomment,NA
+Slashes in titles should be escaped when generating links,"Thanks for taking the time to report this!
+
+It's not entirely clear to me what ""should be escaped when generating links"" mean. The user (when using classic text wikipage editing) or VisualEditor (when using VE for wikipage editing) cannot knowwhich kind of slash is meant.
+
+Or did you mean ""when generating wiki page titles"" instead?",1393417411,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-er23tg3bi4off4fieogn,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"The button for the ""More settings"" menu has no tooltip.  Should it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1393309920,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-255bhdoqq2fqddmttfct,task_description,resolved
+VisualEditor: Add a tooltip to the page menu button,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755283,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,Verified the fix in production:https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit,1394755266,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,Verified the fix in test2,1394229751,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,Verified the fix in betalabs,1393889599,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"Change 116145 merged by jenkins-bot:
+Add tooltip to page options menu widget in the toolbar
+
+https://gerrit.wikimedia.org/r/116145",1393637749,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"Change 116145 had a related patch set uploaded by Jforrester:
+Add tooltip to page options menu widget in the toolbar
+
+https://gerrit.wikimedia.org/r/116145",1393615663,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"Yes:  the three-bars icon, which is currently called ""More settings"" at mw:Help:VisualEditor/User_guide.",1393610658,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+VisualEditor: Add a tooltip to the page menu button,"Do you mean the page menu (Options, Page settings, Advanced settings, …)?",1393537115,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-255bhdoqq2fqddmttfct,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","Intention:
+Blank a page (prior to setting a redirect).
+
+Steps to Reproduce:
+1. Select all (Command-a).
+2. Press the delete key.
+3. Save > Review changes.
+
+Actual Results:  
+Categories, defaultsort keys, and page protection templates are not removed.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)&diff=914307&oldid=904077",1393268400,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jd374nh4jydelfvamhck,task_description,open
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)",https://en.wikipedia.org/w/index.php?action=edit&oldid=665564885 is the most interesting version of this that I've seen for a while.  It kept parts of a subst'd template.,1434928717,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","(In reply to James Forrester from comment #3)
+> On this one I'm minded to WONTFIX, but I could be argued around. What are
+> the reasons for letting people remove content they can't see with select-all?
+
+As WhatamIdoing says, redirecting, for example for merging. This may be achieved using some special scenario. (And hey, blanking must point at something special in any case.)
+
+Copying here the description from bug 67200 which was closed as dupe:
+
+Deleting the text from the article and converting it to a redirect page still leaves all the categories in it, as well as Other Stuff such as magic words and invisible templates.
+
+This is a regression in comparison to the source editor, where the editor could just delete everything and be sure that categories, magic words, invisible templates and everything else is gone.
+
+Just redirecting an article shouldn't necessarily remove everything, because it's actually possible that the editor wants to leave the article in a category. Some projects, including enwiki, have categories, templates etc. in redirect pages. But probably some kind of a warning should be shown.",1403885859,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)",*** Bug 67200 has been marked as a duplicate of this bug. ***,1403885598,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","I'm not sure that select-all is the right way to remove them, but there should be some way to remove them, and a way to find out that they are present.",1393274944,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","(In reply to Bartosz Dziewoński from comment #1)
+> All kinds of other things too, see also bug 52036 and bug 60830. I think we
+> need a tracking bug for this or a large WONTFIX.
+
+I've merged bug 52036 and bug 60830 into their respective causes (both of those are things we will fix with those corrections), and narrowed this to just be about meta-data – things that don't display because they never create any content.
+
+On this one I'm minded to WONTFIX, but I could be argued around. What are the reasons for letting people remove content they can't see with select-all?",1393271801,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","Perhaps we should have a special process for redirects that handles 100% blanking, or at least inquires or warns about it.  (You might want cats for redirects, but probably not a default sort key).",1393271800,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+"VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)","All kinds of other things too, see also bug 52036 and bug 60830. I think we need a tracking bug for this or a large WONTFIX.",1393268518,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-jd374nh4jydelfvamhck,task_subcomment,NA
+VisualEditor: Adding gallery as Heading creates inconsistency between readmode and VE mode,"Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add a heading
+3.Select the text of the heading and insert a gallery
+4.The gallery gets added as part of the heading
+5.Save the page and observe the page content in the readmode
+
+Observed Result:
+
+In readmode , the heading text and caption of the gallery gets repeated immediately following the heading section.Also gallery is not showing up as part of the heading where as in wikitext editor it is inside ==heading== and also in VE
+
+See the screenshot attached
+
+Test Environment: https://test2.wikipedia.org/
+Browser:  FF 25
+OS: MAC OS X 10. 8. 5 
+https://test2.wikipedia.org/w/index.php?title=Totalnewheading
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13262}",1393026840,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-manrmfmqhbwpodlyqqk2,task_description,resolved
+VisualEditor:  Instapaper plug-in injects div tags into pages,"Instapaper is ""a simple tool for saving web pages to read later on your iPhone, iPad, Android, computer, or Kindle.""  It adds div tags to the top and bottom of pages edited in VisualEditor.  
+
+See https://en.wikipedia.org/w/index.php?title=Major_Arcana_%28album%29&diff=589184449&oldid=589116581 for an example.  It added this to the top and the bottom:
+
+<div id=""sendToInstapaperResults""></div>
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=Major_Arcana_%28album%29&diff=589184449&oldid=589116581",1393018260,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-y2vqmyz5nwnjkvcn4rft,task_description,resolved
+VisualEditor:  Instapaper plug-in injects div tags into pages,"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114022,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-y2vqmyz5nwnjkvcn4rft,task_subcomment,NA
+VisualEditor:  Instapaper plug-in injects div tags into pages,"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113140,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-y2vqmyz5nwnjkvcn4rft,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode","Pages in View mode contain a convenient link to the related ""Data item"" (in the sidebar, under Tools). However, in the classic edit mode such links disappears. It is a convenient link for editors, and there is no reason why it should disappear.
+
+PS: the link is kept in VisualEditor since the ""page"" actually doesn't change.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45687",1393014300,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_description,resolved
+"""Data item"" link in sidebar disappears in classic edit mode",Big Thank You!,1414582859,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode","Change 167233 merged by jenkins-bot:
+Always show link to wikibase item in toolbox
+
+https://gerrit.wikimedia.org/r/167233",1414582089,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode","Change 167233 had a related patch set uploaded by Hoo man:
+Always show link to wikibase item in toolbox
+
+https://gerrit.wikimedia.org/r/167233",1413566411,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode","(In reply to Lydia Pintscher from comment #1)
+> Hoo: Should this get the easy keyword?
+
+Don't think so... doesn't seem like the hook we currently use for this supports this :/",1395149218,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+"""Data item"" link in sidebar disappears in classic edit mode",Hoo: Should this get the easy keyword?,1395063814,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-5sljz2peyrsgbqkvdo5a,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"http://korma.wmflabs.org/browser/bugzilla_response_time.html should answer these questions:
+
+How long does it take to give a first response to reporters of Low-Immediate / trivial-blocker bugs? How long until acknowledged bugs are resolved? Are we using the importance parameters consistently? Are we improving?
+
+* Average time for an accepted bug report between bug creation date and PATCH_TO_REVIEW status being set
+* Average time for an accepted bug report between PATCH_TO_REVIEW status being set and RESOLVED FIXED status being set.
+* Average time for an accepted bug report between bug creation date and first comment by not the reporter her/himself.
+
+https://www.mediawiki.org/wiki/Community_metrics#Bugzilla_response_time
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1392848400,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_description,resolved
+Key performance indicator: Bugzilla response time,"I'm marking this task as Resolved because @acs and @sduenas worked hard on it, and the only piece left was better descriptions. Now there is no point in working on them...
+
+People interested in Maniphest metrics can watch and contribute to {T1003}. It's a modest start.",1417699948,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,">>! In T63561#807103, @Nemo_bis wrote:
+>>>! In T63561#802548, @Jdforrester-WMF wrote:
+>> Should this be changed into a Phabricator-focussed metric?
+> 
+> Yes, but AFAIK pretty much everything is impossible for korma given phabricator has no APIs, see T28. Perhaps mark all issue tracker-related tasks in this component as stalled?
+
+Can you not use https://phabricator.wikimedia.org/conduit/ for API access, or am I missing something?
+
+",1417626891,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,">>! In T63561#802548, @Jdforrester-WMF wrote:
+> Should this be changed into a Phabricator-focussed metric?
+
+Yes, but AFAIK pretty much everything is impossible for korma given phabricator has no APIs, see T28. Perhaps mark all issue tracker-related tasks in this component as stalled?",1417613803,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,Should this be changed into a Phabricator-focussed metric?,1417557831,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #29)
+> What if you try without me explaining you how, so we test how usable is this?
+
+I like!
+
+My first guess: Click on a canvas and use Ctrl key && mouse scroll wheel. But the standard zoom behavior of browser takes over. That idea probably came from using PDF viewers too much.
+
+Second guess: I mark a timeframe by clicking the left mouse button, dragging it horizontally while keeping it clicked, like in an audio editor.
+
+Bingo.
+
+I also highly appreciate that the y axis zoom is adjusted automatically!
+And clicking for a bit longer on the canvas seems to reset the zoom.
+
+Big kudos!",1400069447,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #9)
+> Is there a way to zoom the x and/or y axis (also see bug 61810)?
+
+Now you can zoom. What is you try without me explaining you how, so we test how usable is this?  :)",1400014165,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"The graphs are now considered ready:
+
+http://korma.wmflabs.org/browser/bugzilla_response_time.html
+
+We are still missing better strings, but this is a task for me. I'm taking the bug. Help / patches welcome.
+
+https://www.mediawiki.org/wiki/Community_metrics#Global_Pending_List still mentions ""Zoom feature for graphs"" a a nice-to-have improvement. If this item is still open when we close this bug, we will open a new bug report for it.",1395856237,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"This is our first approach to the zoom feature. There are some bugs to fix, though. 
+
+http://korma.wmflabs.org/browser/zoom_test.html",1395253199,PHID-USER-pgf5ibzmrl3xdc6hrj63,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Santi, only fyi: on the topic of removing tracking bugs, there is bug 2007, where all of them are identified.",1394572873,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Santi, thank you! The ""Total"" line is already useful now. I hope the fact of scanning only key Wikimedia projects will reduce the very high peaks, making the rest more readable.
+
+One option to make the Total line more visible could also be to make it thicker than the rest (just in case this is easier than changing the color).
+
+Andre, we agreed to Bitergia that they would focus on the graphs and we will focus on the content. Most of it can be ""edited"" indirectly via pull requests at https://github.com/Bitergia/mediawiki-dashboard/blob/master/browser/bugzilla_response_time.html",1394385156,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Looks good to me; thanks!
+
+(In reply to Santiago Dueñas from comment #21)
+> I've also include some help messages to clarify what the charts mean. Please
+> have a look to the message and let me know whether you understand them or
+> not, or if you want to change some terms, for instance, tickets to
+> bugs/reports, etc.
+
+* Typo: ""Unnatended Tickets""
+* Typo: ""had no actions by ohters than the reporter.""
+* Clicking on the explanation button (qm_15.png icon; ""?"" in a square) in the
+  four last of the six graphs scrolls up to the top of the page in FF27.
+* Unattended vs uncommented: I'd still love to see an explanation of the
+  difference to make sure that everybody understands, maybe in the header in 
+  brackets, like ""Unattended tickets (no activity by anybody else than 
+  reporter)"" and ""Uncommented tickets"" (no comments by anybody else than
+  reporter)"" or so?
+
+> I still have to add the number of bugs in the info boxes and filter those 
+> components that are not key projects.
+
+I think I'll reevaluate after we have this functionality in place (plus zooming, maybe).",1394369963,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #22)
+> Remaining tasks:
+> 
+> (In reply to Quim Gil from comment #19)
+> > * the number of bugs will be also displayed in the dialog with data.
+> > 
+> > Then the canonical list of products / reports that Andre just posted must be
+> > implemented.
+> 
+> We also agreed to add a black line t each graph showing the absolute median,
+> regardless of severity/priority, excluding ""Lowest"" as the graphs do now.
+
+Added but I still have to check how to change the colors of the charts.
+
+> 
+> We left this for later:
+> 
+> > Also, Andre was asking about the possibility to zoom graphs to visualize
+> > only a certain period. I *believe* I have seen this functionality in
+> > VizGrimoire but I'm not sure. In any case, it is something that we would
+> > consider only when we have the points above solve, if we still need it.",1394367598,PHID-USER-pgf5ibzmrl3xdc6hrj63,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Remaining tasks:
+
+(In reply to Quim Gil from comment #19)
+> * the number of bugs will be also displayed in the dialog with data.
+> 
+> Then the canonical list of products / reports that Andre just posted must be
+> implemented.
+
+We also agreed to add a black line t each graph showing the absolute median, regardless of severity/priority, excluding ""Lowest"" as the graphs do now.
+
+We left this for later:
+
+> Also, Andre was asking about the possibility to zoom graphs to visualize
+> only a certain period. I *believe* I have seen this functionality in
+> VizGrimoire but I'm not sure. In any case, it is something that we would
+> consider only when we have the points above solve, if we still need it.",1394063058,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #20)
+> Santi, yesterday Andre and me agreed that the information provided by the
+> ""Time to close"" graphs isn't very useful to us. Not only the very high peaks
+> make the rest impossible to analyze. The main problem is that those reports
+> don't tell us much about the trends, what should we do better, what is the
+> call to action.
+> 
+
+The other day Jesus and I were discussing about it and we find that these charts are not useful if we do not include bugs that are still opened, unattended or uncommented. Tomorrow we can talk about it during the confcall.
+
+> The graphs about the age of reports open without action do show trends and
+> where should we improve. In fact Andre is missing already the ones based on
+> priority. 
+> 
+> For all these reasons we propose to have these graphs, in this order:
+> 
+> Age of reports without any action by priority & severity
+> 
+> Age of reports without any comment by priority & severity
+> 
+> Age of reports unresolved by priority & severity
+> 
+> 
+
+Added.
+
+I've also include some help messages to clarify what the charts mean. Please have a look to the message and let me know whether you understand them or not, or if you want to change some terms, for instance, tickets to bugs/reports, etc.
+
+I still have to add the number of bugs in the info boxes and filter those components that are not key projects.
+
+> If you still think it makes sense to have graphs of the age of
+> closed/actioned/commented reports let's discuss, but after we leave this KPI
+> ready for this iteration. It's already March and there is still a lot to do.
+> Thank you!
+
+Ok!
+
+BTW, sorry with the delay with this. To get the ""age"" data from actions and comments was tricker than I thought.",1393990384,PHID-USER-pgf5ibzmrl3xdc6hrj63,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Santi, yesterday Andre and me agreed that the information provided by the ""Time to close"" graphs isn't very useful to us. Not only the very high peaks make the rest impossible to analyze. The main problem is that those reports don't tell us much about the trends, what should we do better, what is the call to action.
+
+The graphs about the age of reports open without action do show trends and where should we improve. In fact Andre is missing already the ones based on priority. 
+
+For all these reasons we propose to have these graphs, in this order:
+
+Age of reports without any action by priority & severity
+
+Age of reports without any comment by priority & severity
+
+Age of reports unresolved by priority & severity
+
+
+If you still think it makes sense to have graphs of the age of closed/actioned/commented reports let's discuss, but after we leave this KPI ready for this iteration. It's already March and there is still a lot to do. Thank you!",1393957111,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"After a conversation with Santi, we agreed on these changes:
+
+* focus on severity, removing all the graphs about priority and keeping the page sane; the former is more objective and stable, the latter is more subjective and changeable
+
+* Santi will try to draw the graphs calculating the severity of the reports at a given time; it seems to be easy but we'll see
+
+* the ""median age of open reports"" graphs will go at the beginning: reports without any action, reports without any comment, reports unresolved
+
+* the ""media age of reports acted upon"" will follow with a clear explanation: median age of reports when they get a first action, when they get a first comment, when they get a resolution
+
+* the number of bugs will be also displayed in the dialog with data.
+
+Then the canonical list of products / reports that Andre just posted must be implemented.
+
+Then we will see whether we still get those high peaks converting the rest in planes or not.
+
+Also, Andre was asking about the possibility to zoom graphs to visualize only a certain period. I *believe* I have seen this functionality in VizGrimoire but I'm not sure. In any case, it is something that we would consider only when we have the points above solve, if we still need it.",1393521221,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Santiago Dueñas from comment #14)
+> > > Should I make [[wikitech:Key_Wikimedia_software_projects]] a table and add
+> > > the corresponding Bugzilla product/component in the second column? 
+> 
+> A table sounds good. They're easy to parse and edit. But if I can suggest
+> something, I prefer to have product/component in separated columns
+
+Done: https://wikitech.wikimedia.org/w/index.php?title=Key_Wikimedia_software_projects&diff=101721&oldid=90993
+
+I hope I'll remember to update when I change Bugzilla's taxonomy. :)
+
+(And as a side-effect of (re-)investigating Bugzilla taxomony of Fundraising I found & filed bug 62002.)",1393521021,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Santiago Dueñas from comment #16)
+> I've added some new charts that try to show this.
+
+Thanks! They feel more helpful than the ""Time to close by..."" charts.
+
+> These charts have some problems:
+> 
+> - A peak that goes down doesn't implies you are closing the oldest bugs. It
+> can means that there are more bugs that were open recently, decreasing the
+> median. You can see this behaviour in Feb 2011. The median of Unprioritized
+> bugs is 530 days because there's only one bug that were opened 530 days ago.
+> The next month, the median goes down to 282 days because another bug was
+> opened in Mar 2011 and at the end of that month none of them were closed.
+
+Probably overhead and not a good idea, but could the overlay also display on how many items the calculated value is based on?
+
+> - Take into account that we are using the current priority of a bug. I think
+> that for these kind of charts, it makes more sense to take the priority of
+> the bug at that time, but it raises another problem: changes in lines might
+> be produced by changes in the priority. If you change the priority of a bug,
+> the old priority line will decrease while the new one will increase.
+
+Yeah, that's what I meant in comment 10 - but let's revisit the ""when to query the priority/severity value of a report"" aspect later.",1393515355,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"> (In reply to Santiago Dueñas from comment #4)
+> > In this case, the peak is from bug 27320.
+> 
+> > It was submitted on Feb 2011 (that's why it is shown at that point in the
+> > chart) but its first action was made two years later (April 2013). Its
+> > current priority is Immediate.
+> 
+> I think we have a problem of perspective. Your perspective seems to be
+> data-centric: ""how old were the bugs created at this point of time when they
+> received their first action?"" We actually care about our own perspective as
+> bugtriagers (yes, we are so self-centered people)  :) : ""how old are today
+> the open bugs that haven't received any action yet""? And last month? And a
+> year ago?
+> 
+> We want to see whether we are processing those bugs faster or slower than
+> before, whether we succeed addressing more important bugs faster or not. In
+> this sense, I wouldn't expect high peaks emerging, since the highest
+> increase from month to month can only be 31 days (unless you reopen hundreds
+> of very old bugs, an unlikely scenario that would reflect a legitimate
+> higher peak).
+> 
+> Let's agree on these points before tying to solve anything else, please.
+
+I've added some new charts that try to show this.
+
+These new ones are in top of the page and are ""Time opened by Priority (median)/(average)"". Former ""Time opened"" charts are now ""Time to close by Priodity (median)/(average). If you go down, you will see same charts but by Severity.
+
+Let's focus on ""Time opened by Priority (median)"". It shows how old your opened bugs were at a certain point in time, in median.
+
+If you select the first point with data, Aug 2004, it means that those bugs that remained open at the end of August were submitted (opened) in median around 15 days ago for most of the priorities. If you go to the next point, Sep 2004, it means the bugs that remain open (those from August that are not closed yet and those from September) were opened X days ago by priority, an so on.
+
+These charts have some problems:
+
+- A peak that goes down doesn't implies you are closing the oldest bugs. It can means that there are more bugs that were open recently, decreasing the median. You can see this behaviour in Feb 2011. The median of Unprioritized bugs is 530 days because there's only one bug that were opened 530 days ago. The next month, the median goes down to 282 days because another bug was opened in Mar 2011 and at the end of that month none of them were closed.
+
+- High lines can hide or shadow your work on new bugs. If you are closing new bugs very fast and you also have old opened bugs, you won't see any change in the lines.
+
+- Take into account that we are using the current priority of a bug. I think that for these kind of charts, it makes more sense to take the priority of the bug at that time, but it raises another problem: changes in lines might be produced by changes in the priority. If you change the priority of a bug, the old priority line will decrease while the new one will increase.
+
+One possible solution to these problems is combine these with historgrams or distribution charts.",1393428864,PHID-USER-pgf5ibzmrl3xdc6hrj63,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #12)
+> (In reply to Andre Klapper from comment #9)
+> > For my better understanding (and maybe others who might have the same
+> > problem):
+> > ""Time to first action by Priority"" - How is an ""action"" defined?
+> 
+> It means that someone (else, not the reporter) has changed priority,
+> severity, etc. That the bug has some history of changes, although afaik a
+> first comment is not counted (Santi must confirm). See Bug 13162, which tops
+> the list, it hasn't seen any change since it was submitted in 2008.
+> 
+> (It belongs to the MultiBoilerplate extension which afaik is not part of the
+> Key Wikimedia projects, a way to fine tune the list of products/components
+> we scan is to remove those that show up in the top results.)
+> 
+
+Action means changes + comments done by someone, but not by the reporter. In this context, ""Time to first action"" means how long it took that someone (not the submitter or reporter) for the first time, made a change on any the bug's parameters or posted a first comment. 
+
+This is the definition that Alvaro gime me but we can change it to ""Time to first change"", if you prefer.
+
+> > Is ""Time to
+> > first comment"" a subset, or disjunct?
+
+""Time to first comment"" is a subset of ""Time to first action"".
+
+> > So: Could the framework query changes to the ""Priority"" value of one report
+> > (via the ""bugs_activity"" database table in Bugzilla) and could one report be
+> > broken into/represented in several lines, each line showing for how long the
+> > report had that specific priority set?  I think this would make the lines
+> > more meaningful. (Same might apply to Severity).
+> 
+> Following on Comment 7, this would be translated as
+> 
+> ""How old are today the open bugs that haven't received any action yet,
+> organized by their priority/severity today""? And last month (based on the
+> priority/severity they had last month)? And a year ago (based on the
+> priority/severity they had last year)?
+> 
+> As said, if Santi sees a quick way to fix this let's do it. Otherwise let's
+> open an enhancement request for the next iteration.
+>
+
+Definitely. I can try something but I prefer to close the definition and meaning of the current charts before moving to new ones.",1393346880,PHID-USER-pgf5ibzmrl3xdc6hrj63,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #13)
+> (In reply to Andre Klapper from comment #11)
+> > Should I make [[wikitech:Key_Wikimedia_software_projects]] a table and add
+> > the corresponding Bugzilla product/component in the second column? 
+> > Or what's the prefered format to parse it in a machine-readable way? :-/
+> 
+> Santi: Could you answer this please?
+
+A table sounds good. They're easy to parse and edit. But if I can suggest something, I prefer to have product/component in separated columns, in order to pass them as parameters to our tool.",1393345013,PHID-USER-pgf5ibzmrl3xdc6hrj63,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #11)
+> Should I make [[wikitech:Key_Wikimedia_software_projects]] a table and add
+> the corresponding Bugzilla product/component in the second column? 
+> Or what's the prefered format to parse it in a machine-readable way? :-/
+
+Santi: Could you answer this please?",1393344862,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #9)
+> For my better understanding (and maybe others who might have the same
+> problem):
+> ""Time to first action by Priority"" - How is an ""action"" defined?
+
+It means that someone (else, not the reporter) has changed priority, severity, etc. That the bug has some history of changes, although afaik a first comment is not counted (Santi must confirm). See Bug 13162, which tops the list, it hasn't seen any change since it was submitted in 2008.
+
+(It belongs to the MultiBoilerplate extension which afaik is not part of the Key Wikimedia projects, a way to fine tune the list of products/components we scan is to remove those that show up in the top results.)
+
+> Is ""Time to
+> first comment"" a subset, or disjunct? Would changing the status from
+> REOPENED to NEW count as an action already?
+
+A bug REOPENED has been RESOLVED before, therefore it was acted upon already.
+
+(In reply to Andre Klapper from comment #10)
+> If I interpret comment 4 directly, one bug report remains in one line
+> (color) in the current model, based on gathering its *current* priority
+> value?
+
+Yes, this is not optimal but, unless it is easy to fix, I would leave it as such for the current iteration. We want to complete this KPI (well, the 5 KPIs) in this quarter, and Marc is already around the corner.
+ 
+> So: Could the framework query changes to the ""Priority"" value of one report
+> (via the ""bugs_activity"" database table in Bugzilla) and could one report be
+> broken into/represented in several lines, each line showing for how long the
+> report had that specific priority set?  I think this would make the lines
+> more meaningful. (Same might apply to Severity).
+
+Following on Comment 7, this would be translated as
+
+""How old are today the open bugs that haven't received any action yet, organized by their priority/severity today""? And last month (based on the priority/severity they had last month)? And a year ago (based on the priority/severity they had last year)?
+
+As said, if Santi sees a quick way to fix this let's do it. Otherwise let's open an enhancement request for the next iteration.
+
+I bet the current way of counting is still useful: for instance, if many urgent bugs were unnoticed for a long time, this will affect the time to address urgent issues, and it will show that we are slow addressing issues that were potentially urgent before we looked at them.
+
+I'm leaving the rest to Santi, but let's not deviate on the current focus es defined in Comment 7. We need to deliver a good iteration soon, and we have still many fonts open here.",1393256563,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #8)
+> > Last list I made was bug 54469 comment 6.
+> 
+> Interesting, but... you could have updated
+> [[wikitech:Key_Wikimedia_software_projects]] instead, which is the canonical
+> place to track changes to the key Wikimedia projects.
+
+Uhm. I cannot remember exactly, but I guess I was worried about the format I should use but did not ask explicitly. :(
+Should I make [[wikitech:Key_Wikimedia_software_projects]] a table and add the corresponding Bugzilla product/component in the second column? 
+Or what's the prefered format to parse it in a machine-readable way? :-/",1393194334,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Concentrating on ""Time to ... by Priority/Severity"" in this comment. Need to understand better, hence dropping some late night beer comments + thoughts.
+
+== Bug report priority changes vs. data gathering/representation in graph
+
+""Time to fix (TTF)""-related expectations per priority are covered in http://www.mediawiki.org/wiki/Bugzilla/Fields#Priority - an ""Immediate priority"" report should have a shorter TTF median than a ""Low prio"" report.
+
+In my opinion, TTF entirely depends to the moment a report receives priority triaging - either an initial triage or a retriage. Retriage means that Priority (and less often Severity, though from default ""Normal"" to ""Enhancement"" might be the one big exception here) of a report can change.
+
+If I interpret comment 4 directly, one bug report remains in one line (color) in the current model, based on gathering its *current* priority value?
+
+An open report that was low priority for three years and then suddenly became highest priority (e.g. due to other infrastructure changes creating the side effect that the bug is way more visible) and two weeks later closed as RESOLVED FIXED with priority still set to ""highest"" should probably not be shown as ""highest priority bug that took three years and two weeks to get closed"" as it's misleading.
+
+So: Could the framework query changes to the ""Priority"" value of one report (via the ""bugs_activity"" database table in Bugzilla) and could one report be broken into/represented in several lines, each line showing for how long the report had that specific priority set?  I think this would make the lines more meaningful. (Same might apply to Severity).
+
+
+== (Neglectable?) data artefacts on bug report metadata
+
+Can I assume that *all* bug reports are used as data source, hence also all resolutions (including WONTFIX, INVALID)?
+This might be a rather neglectable artefact, but correcting report metadata (priority, component, etc) after resolving a report (e.g. as WONTFIX, INVALID etc) often does not happen: 
+""Of course, the developer could change the issue category after resolution - but this happens rarely. In many cases there exists no real motivation to change the issue category once the cause for a problem is found and fixed."" (Herzig, Just, and Zeller: ""It's not a bug, it's a feature: how misclassification impacts bug prediction"", 2013, page 396, at http://www.st.cs.uni-saarland.de/softevo/bugclassify/paper/icse2013-bugclassify.pdf when the server is not down.)
+
+
+== Time to change ""Unprioritized"" to different priority (likely ignorable)
+
+As the default priority of a report is always ""Unprioritized"", I wonder whether median time between creation of a bug report and changing the priority from ""Unprioritized"" to a different value would be any helpful. 
+I am not convinced myself though: This is likely covered by ""Time to first action by Priority"" which might be enough for us.
+Anyway, just in case, two potentially problematic aspects for data gathering:
+* Not all teams use Priority in Bugzilla. Some use Mingle etc. instead.
+* Some tickets get closed so quickly that they remain ""Unprioritized"".",1393193797,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"For my better understanding (and maybe others who might have the same problem):
+""Time to first action by Priority"" - How is an ""action"" defined? Is ""Time to first comment"" a subset, or disjunct? Would changing the status from REOPENED to NEW count as an action already?
+
+Smaller issue in all graphs but only on this page:  After ""Feb 2013"", the month name header in the overlay popup becomes ""undefined"" (instead of ""Mar 2013"" etc).
+
+> The main problem here is with those big peaks in median charts. The 
+> useful data is lost at the bottom of the chart and you can only see
+> flat lines. We have to think about how to manage these cases.
+
+Does the rendering allow a cut-off parameter, e.g. ""only render lowest 40% of y axis""? Could images have double the height? Is there a way to zoom the x and/or y axis (also see bug 61810)?
+Not convinced by these ideas, but still some thoughts.",1393183040,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #2)
+> (In reply to Quim Gil from comment #1)
+> > * We need to scan only the Bugzilla products and components corresponding to
+> > https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects . Andre,
+> > did you have a list somewhere mapping these?
+> 
+> Last list I made was bug 54469 comment 6.
+
+Interesting, but... you could have updated [[wikitech:Key_Wikimedia_software_projects]] instead, which is the canonical place to track changes to the key Wikimedia projects.
+
+Maybe we can simplify things a bit? (but still document them in the wiki page)
+
+Entire products:
+
+Analytics
+Commons App
+Cortado (???)
+Datasets
+MediaWiki
+MediaWiki‑Vagrant
+MobileFrontend
+OOjs
+OOjs UI
+openZIM
+Parsoid
+Pywikibot
+QRpedia
+Security (can we extract anything from here anyway?)
+Tools (???)
+VisualEditor
+Wiki Loves Monuments
+Wikimedia
+Wikimedia Labs
+Wikipedia App 
+
+Then someone should map the components under ""MediaWiki extensions"" with [[wikitech:Key_Wikimedia_software_projects]]. Maybe it is easier to have the full list of components under ""MediaWiki extensions"" in Bugzilla and then remove those extensions not deployed here. It's not a big deal if there is a bit of mismatch. We can always fine tune.
+
+Andre, can you help Santi with this?",1393120176,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"Let's focus first on these graphs:
+
+(In reply to Santiago Dueñas from comment #5)
+> now we show ""Time opened"" by median and average.
+
+There is still something odd here. See for instance ""Time opened by Priority (average)""
+
+In August 2004, apparently one month after opening the Bugzilla instance, we have about Low and Lowest bugs with a median of 1000 days. How can this be? I expect a graph that says that after 30 days of Bugzilla a bug can be 30 days old at most.
+
+
+> The main problem here is with those big peaks in median charts.
+
+Before trying to address the visualization problems of those high peaks, I still must understand the algorithm that generates them. You say...  
+
+(In reply to Santiago Dueñas from comment #4)
+> In this case, the peak is from bug 27320.
+
+> It was submitted on Feb 2011 (that's why it is shown at that point in the
+> chart) but its first action was made two years later (April 2013). Its
+> current priority is Immediate.
+
+I think we have a problem of perspective. Your perspective seems to be data-centric: ""how old were the bugs created at this point of time when they received their first action?"" We actually care about our own perspective as bugtriagers (yes, we are so self-centered people)  :) : ""how old are today the open bugs that haven't received any action yet""? And last month? And a year ago?
+
+We want to see whether we are processing those bugs faster or slower than before, whether we succeed addressing more important bugs faster or not. In this sense, I wouldn't expect high peaks emerging, since the highest increase from month to month can only be 31 days (unless you reopen hundreds of very old bugs, an unlikely scenario that would reflect a legitimate higher peak).
+
+Let's agree on these points before tying to solve anything else, please.",1393019867,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Santiago Dueñas from comment #5)
+> The main problem here is with those big peaks in median charts. The useful
+> data is lost at the bottom of the chart and you can only see flat lines. We
+> have to think about how to manage these cases.
+
+Scale in log base 10?",1393009986,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #3)
+> The main problem I have with these graphs is that they show plenty of lines
+> going up and down, but no clear message. 
+> 
+> When answering ""Time to closed by Priority"", I think we should actually
+> answer ""Median time of open bugs"". This would provide more stable lines
+> without huge jumps between months, where we can see
+> 
+> * whether we are increasing or decreasing the median time for open bugs
+> * the differences of time response for higher and lower priority bugs
+> 
+> I think this change will make all the graphs a lot more useful.
+> 
+> Then we can organize better those six graphs:
+> 
+> Time to closed by Priority
+> Time to closed by Severity
+> 
+> Then time to first action, then time to first comment.
+> 
+
+I think you are right.
+
+Please have a look at the new charts that I've just uploaded. Instead of ""Time to close"" now we show ""Time opened"" by median and average. I've also included the median for first action and first comment.
+
+The main problem here is with those big peaks in median charts. The useful data is lost at the bottom of the chart and you can only see flat lines. We have to think about how to manage these cases.
+
+Average charts are still there for comparing with the median ones. We can remove them whenever you want.
+
+> It would be good to have also a line for the median of the total of bugs,
+> regardless of priority/severity, to see how good are we doing overall.
+> 
+
+Good point. I'm going to add it.
+
+> One more thing, since we are considering ""Lowest"" almost as an equivalent of
+> WONTFIX-for-maintainers (we assign Lowest priority when nobody is planning
+> to act on a report), we might need to consider them as resolved-wontfix if
+> they distort too much the results. We will see.
+
+I had it into account for top issues and ""Time opened"" so these data is already filtered.",1393009656,PHID-USER-pgf5ibzmrl3xdc6hrj63,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Andre Klapper from comment #2)
+> (In reply to Quim Gil from comment #1)
+> > * We need to scan only the Bugzilla products and components corresponding to
+> > https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects . Andre,
+> > did you have a list somewhere mapping these?
+> 
+> Last list I made was bug 54469 comment 6.
+> 
+> > Andre, you are the main stakeholder of this page.
+> 
+> Noted.
+> 
+> One data issue in the graphs:
+> http://korma.wmflabs.org/browser/bugzilla_response_time.html shows
+> ""avg_fa_Immediate:788.7567"" for Feb 2011. That is impossible as the
+> ""Immediate"" priority was only introduced on Nov 30, 2012:
+> http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064746.html
+> I have not investigated other peaks yet (also because I don't have data
+> handy when which priority and severity was introduced in this Bugzilla).
+
+It is shown that way because we take the current/final priority of a bug to classify them into group due to the priority can change during the life of bug.
+
+In this case, the peak is from bug 27320.
+
+https://bugzilla.wikimedia.org/show_bug.cgi?id=27320.
+
+It was submitted on Feb 2011 (that's why it is shown at that point in the chart) but its first action was made two years later (April 2013). Its current priority is Immediate.
+
+Another possibility is to select the initial state but most of the bugs (aroung 90%) fall in Unprioritize or Normal priorities. Selecting intermediate states doesn't make any sense because we would need infinite charts to show the data.",1393008607,PHID-USER-pgf5ibzmrl3xdc6hrj63,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"The main problem I have with these graphs is that they show plenty of lines going up and down, but no clear message. 
+
+When answering ""Time to closed by Priority"", I think we should actually answer ""Median time of open bugs"". This would provide more stable lines without huge jumps between months, where we can see
+
+* whether we are increasing or decreasing the median time for open bugs
+* the differences of time response for higher and lower priority bugs
+
+I think this change will make all the graphs a lot more useful.
+
+Then we can organize better those six graphs:
+
+Time to closed by Priority
+Time to closed by Severity
+
+Then time to first action, then time to first comment.
+
+It would be good to have also a line for the median of the total of bugs, regardless of priority/severity, to see how good are we doing overall.
+
+One more thing, since we are considering ""Lowest"" almost as an equivalent of WONTFIX-for-maintainers (we assign Lowest priority when nobody is planning to act on a report), we might need to consider them as resolved-wontfix if they distort too much the results. We will see.",1392924663,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"(In reply to Quim Gil from comment #1)
+> * We need to scan only the Bugzilla products and components corresponding to
+> https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects . Andre,
+> did you have a list somewhere mapping these?
+
+Last list I made was bug 54469 comment 6.
+
+> Andre, you are the main stakeholder of this page.
+
+Noted.
+
+One data issue in the graphs:
+http://korma.wmflabs.org/browser/bugzilla_response_time.html shows ""avg_fa_Immediate:788.7567"" for Feb 2011. That is impossible as the ""Immediate"" priority was only introduced on Nov 30, 2012: http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064746.html
+I have not investigated other peaks yet (also because I don't have data handy when which priority and severity was introduced in this Bugzilla).",1392905142,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+Key performance indicator: Bugzilla response time,"The main problems discussed so far:
+
+* We need to scan only the Bugzilla products and components corresponding to https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects . Andre, did you have a list somewhere mapping these?
+
+* The graphs miss a legend describing what is being calculated. Documentation in the wiki page linked above would be useful too.
+
+* The data calculated is the average, but the median is preferred.
+
+* The graphs start in Jan 2002 but there is no data until Jul 2004.
+
+* Proper labels.
+
+I still must put more time to dive into these graphs and see whether they provide the answers we are looking for, or they could be improved. Andre, you are the main stakeholder of this page.",1392849320,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-56srqkt3lcgu3p7kvj56,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Intention:
+Change an ISBN.
+
+Steps to Reproduce:
+1. Open a page with a pre-existing ISBN number (using the magic word).
+
+2. Click in the link and open the link inspector.
+
+3. Correct the numbers in the ISBN.
+
+4. Close the link inspector.
+
+
+
+Actual Results:  
+The link label does not change.  This is not surprising, given VisualEditor's approach to links, but it is sometimes unfortunate; see https://fr.wikipedia.org/w/index.php?title=Massimo_Introvigne&diff=100272017&oldid=94374615
+
+However, the link itself does not change, and if you have done nothing else, it is not possible to save the page, because you have supposedly made no changes.
+
+Expected Results:  
+Ideal behavior:
+
+Changing ""ISBN 1234567890"" to ""ISBN 1234567891"" simply updates the plain wikitext magic word.
+
+Possibly acceptable behavior:
+
+Changing ""ISBN 1234567890"" to ""ISBN 1234567891"" updates the link to [[Special:BookSources/1234567891|ISBN 1234567891]].
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52204",1392846900,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_description,resolved
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Change 233669 merged by jenkins-bot:
+Specialized inspector for ISBN magic links
+
+[[https://gerrit.wikimedia.org/r/233669]]",1441132464,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Change 233669 had a related patch set uploaded (by Cscott):
+Specialized inspector for ISBN magic links
+
+[[https://gerrit.wikimedia.org/r/233669]]
+",1440714140,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Change 233669 had a related patch set uploaded (by Cscott):
+WIP: Specialized inspector for ISBN magic links
+
+[[https://gerrit.wikimedia.org/r/233669]]
+",1440533743,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","@krenair it's mostly orthogonal to this bug, but we just changed the `rel` type of ISBN links to `mw:WikiLink`.  I agree that it is more consistent that way.
+
+The VE UX issue still exists: VE should detect edits to ISBN/RFC/PMID links and somehow keep the text and the link in sync.  I don't know the best way to do that within the VE codebase.",1440082534,PHID-USER-m2ezqyeb4uz67zq6bats,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links",">>! In T63558#1365108, @Elitre wrote:
+> @ssastry, are the problems described in [[ https://phabricator.wikimedia.org/T63558#677094 | this comment]] also possibly due to Parsoid? Thank you!
+
+Looking at [[Special:BookSources/9782981011206|ISBN 978-2-9810112-1-]]<nowiki/>3 .. that looks like VE issues to me. The ""3"" is not part of the link text so, Parsoid is forced to add a nowiki to preserve HTML semantics. As for editing link text not chaning the underlying link, that is also a VE UX issue.",1434380446,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","@ssastry, are the problems described in [[ https://phabricator.wikimedia.org/T63558#677094 | this comment]] also possibly due to Parsoid? Thank you!",1434365599,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","The Parsoid output does not look quite right to me:
+```<a href=""./Special:BookSources/0345318641"" rel=""mw:ExtLink"" data-parsoid='{""stx"":""magiclink"",""dsr"":[16,34,0,0]}'>ISBN 0-345-31864-1</a>```
+ExtLink? That href is for a WikiLink...",1429356029,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","The Parsoid output does not look quite right here:
+```<a href=""./Special:BookSources/0345318641"" rel=""mw:ExtLink"" data-parsoid='{""stx"":""magiclink"",""dsr"":[16,34,0,0]}'>ISBN 0-345-31864-1</a>```
+ExtLink? That href is for a WikiLink...",1429356018,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+"VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links","Other recent examples of ISBN problems caused by VE (awful syntax, link incoherent with displayed ISBN, nowiki added) :
+https://fr.wikipedia.org/w/index.php?title=Bassin_s%C3%A9dimentaire&diff=prev&oldid=104307942
+https://fr.wikipedia.org/w/index.php?title=Louis-Jos%C3%A9_Houde&diff=104782988&oldid=104262388
+
+This is a recurring problem on frwiki.",1403533505,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-mnf2geb333qld3ax5dkc,task_subcomment,NA
+GUI for VisualEditor Math plugin,"The original plan for the math plugin was to create a equation editor GUI, similar to that in Google Docs.
+https://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Application
+
+This would have ability to insert mathematical symbols and create structures like integrals, matrices etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392740220,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-grsmbxc6xcqg4so4enlg,task_description,resolved
+GUI for VisualEditor Math plugin,"
+
+*** This bug has been marked as a duplicate of bug 43058 ***",1392741898,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-grsmbxc6xcqg4so4enlg,task_subcomment,NA
+VisualEditor: Avoid mentioning wikitext on MediaWiki error messages (this confuses users who use VisualEditor instead of wikitext),"Consider VisualEditor as the default editing method, and suppose you are a new user arriving at one of the articles currently listed under
+[[Category:Pages with missing references list]]
+(or its equivalents in other languages).
+
+Somewhere in the page there will be messages such as these:
+* There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page).
+
+* There are <ref group=$1> tags on this page, but the references will not show without a {{reflist|group=$1}} template (see the help page).
+
+But since your few edits were made using VisuaEditor, you have no idea what are ""<ref>"", ""<ref group=$1>"" and ""{{reflist|group=$1}}"".
+
+There are many other messages like that which are exposed to (inexperienced) users (either by MediaWiki core or one of its extensions). They should try to describe the problem avoiding talking about the wiki syntax, which will not make sense if VisualEditor is the only way someone is able to edit.
+
+
+This bug report was inspired by the following feedback:
+https://pt.wikipedia.org/wiki/WP:Editor_Visual/Comentários?oldid=38180789#fonte.2C_pede_sempre.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1392546660,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-q6kl2cnzpurtdprt2z7l,task_description,open
+VisualEditor: Avoid mentioning wikitext on MediaWiki error messages (this confuses users who use VisualEditor instead of wikitext),"I'm not sure this is a VisualEditor-specific bug, but yes, MediaWiki and its extensions' messages make occasional assumptions of the use of wikitext. This is much more acute due to local communities' over-ridden messages, which much more frequently make this mistake.",1393537441,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q6kl2cnzpurtdprt2z7l,task_subcomment,NA
+VisualEditor: CSS to add numbers to reference list items it vertically misaligned (should be top not bottom?),"Screenshot
+
+Number of reflist vertically misaligned, see screenshot
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://de.wikipedia.org/w/index.php?title=Wolfgang-Hahn-Preis_K%C3%B6ln&veaction=edit
+
+**Attached**: {F13043}",1392490020,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-ojcdgofuxpjixghndf6z,task_description,resolved
+VisualEditor: CSS to add numbers to reference list items it vertically misaligned (should be top not bottom?),This appears to have been fixed some time ago.,1525335436,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-ojcdgofuxpjixghndf6z,task_subcomment,NA
+VisualEditor: CSS to add numbers to reference list items it vertically misaligned (should be top not bottom?),"**santosh.cool.reddy** wrote:
+
+Looks like german pages are not using current visual editor. In english which uses https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide doesn't show such errors.",1394889473,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ojcdgofuxpjixghndf6z,task_subcomment,NA
+VisualEditor: CSS to add numbers to reference list items it vertically misaligned (should be top not bottom?),"**santosh.cool.reddy** wrote:
+
+I had a look into this bug. I suggest style of ve-ce-mwTransclusionInlineNode must be ""inline"" not ""inline-block"" to clear this bug.",1394815686,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ojcdgofuxpjixghndf6z,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"This is with Translate 2014-02-04.
+
+I've created a testcase which you can see by visiting https://www.mediawiki.org/w/index.php?title=User:SamB/tvar_bug&oldid=907218&action=edit&section=1 and clicking the ""preview"" button.
+
+Notice how all of the Translate markup shows up in the Preview because the <translate> tag isn't in this section?  That's kind of annoying.
+
+{F31698682}",1392487980,PHID-USER-3bnjvlq3zbpzzxdh4g4g,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_description,resolved
+Section preview in new wikitext editor shows Translate markup,"As suggested by @Arlolra, I reverted  https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/808926/ (as well as https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/837636 to get parsedoc back) on my local wiki to re-test the preview with Parsoid. Things work as I expected - the tags are tranformed into <meta> tags and are not visible in the preview. The old <tvar> syntax doesn't break either. Consequently, I'm considering this issue resolved.",1675189578,PHID-USER-ut3yptb7r45gfpwp33qn,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"This issue is technically not triggering anymore, because section editing with the new wikitext editor are back on the legacy parser (see T154844 / https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/808926/). That said, we may want to keep an eye on it because we probably want to check that it indeed works for section preview when Parsoid becomes the default path for read views. My educated guess there is that it *should* work because of the work we've done on T261181, which transforms these translate/tvar tags into <meta> tags, that shouldn't be displayed, but there may be some corner cases on the detection of the annotation (in particular with the deprecated `<tvar|name>var</>` syntax) outside of a full context.",1675188824,PHID-USER-ut3yptb7r45gfpwp33qn,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,Just noting that there will be inconsistency with section preview in the old wikitext editor where Translate is hiding the tags using ParserBeforeInternalParse hook.,1616139116,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,">>! In T63422#660916, @Aklapper wrote:
+> I don't really see a bug here - unclosed tags are probably just displayed like that by the parser, plus this just applies to the preview. 
+> Not sure if that's something to fix in the Translate codebase.
+
+I'm going to agree with this",1616099628,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,Perhaps the Parsing team can have a look to provide an answer.,1586273756,PHID-USER-hqyy4wr7smuc4rzaoio5,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,Feedback whether this is fixable there would be appreciated.,1585553144,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"Sorry for the delay. That is the screenshot with legacy 2010 wikitext editor:
+{F31712035}
+
+I have just tried with 2017 NWE. Indeed, with this editor, <translate> tags are displayed:
+{F31712065}",1585505319,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"Can you post a screenshot?
+
+I believe this was fixed in {T168743}, but the new wikitext editor is probably still broken because it does previews differently.",1584973908,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"@Nikerabbit That’s strange, even with oldid, I can’t reproduce this bug at home: all <translate> tags, balanced or not, are removed from previewing, while editing a section.
+
+When I edit the full page, all translate tags are displayed if one closing tag is missing. But they are all removed (even successive closing tags) if I edit only a section.",1584973480,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"I can’t reproduce with the given testcase. I think this is fixed, isn’t it?
+
+EDIT: except if translate tags are unbalanced, but the same issue would produce with any unbalanced wikitext, I think",1584908152,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"I can’t reproduce with the given testcase. I think this is fixed, isn’t it?",1584908086,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+Section preview in new wikitext editor shows Translate markup,"I don't really see a bug here - unclosed tags are probably just displayed like that by the parser, plus this just applies to the preview. 
+Not sure if that's something to fix in the Translate codebase.",1396271561,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-td6bfetp5r2m3jb36nd3,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,"screenshot
+
+steps to reproduce:
+
+1.Open a page with VE
+2.Insert an image
+3.Go to the Media Settings of the image
+4.Set the image to frameless and none as position
+5.Now select the image
+
+Observed Result:
+ Image highlight box is appearing at the top left corner of the page
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=14thfebchrome&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+
+**Attached**: {F12967}",1392406080,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nbibeqvqnm42dfuywhy4,task_description,resolved
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,Verified the fix on:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox,1394758473,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,Verified the fix in test2,1394154128,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,Verified the fix in betalabs,1393636588,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,"Change 116116 merged by jenkins-bot:
+Don't show phantoms for hidden protected items
+
+https://gerrit.wikimedia.org/r/116116",1393615067,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,"Change 116116 had a related patch set uploaded by Esanders:
+Don't show phantoms for hidden protected items
+
+https://gerrit.wikimedia.org/r/116116",1393603609,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Phantoms showing in top left corner for no-longer visible objects,*** Bug 56608 has been marked as a duplicate of this bug. ***,1393541505,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nbibeqvqnm42dfuywhy4,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"See for instance
+https://fr.wikipedia.org/w/index.php?title=Philippe_Juvin&diff=101226971&oldid=101177693 .
+The edit added `<span style=""font-size:12.0pt;font-family:""Times New Roman"",""serif""; mso-fareast-font-family:Calibri;mso-ansi-language:EN-GB;mso-fareast-language: EN-US;mso-bidi-language:AR-SA"">` to a newly added reference.
+It was reported by NicoV at fr.wp, I haven't had a chance to see if it can be reproduced or how yet.
+
+**See Also**:
+* {T60689}
+* {T71821}
+* {T71513}
+* {T75292}",1392375360,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-r5hdqedtma6idm3jhqfo,task_description,resolved
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"Copy paste sanitisation has improved significantly since 2014, so closing. If this is still happening, please re-open.",1701962897,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"The previous comments don't explain what/who exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status.
+
+//(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}. If this task is stalled on an upstream project, then the #upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If this task needs retesting, then the #testme tag should be added. If this task is either out of scope and nobody should ever work on this, or nobody else managed to reproduce the problem described in this task, then this task should have the ""Declined"" status.)//",1590761765,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"Yeah, probably...",1410806073,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,My guess is that https://cs.wikipedia.org/w/index.php?title=%C4%8Cesk%C3%A1_akademie_v%C4%9Bd_a_um%C4%9Bn%C3%AD&diff=11859116&oldid=11475316 is copy/paste issue as well?,1410805955,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"<span style=""... mso-...""> It's a copy/paste from Microsoft Office => Word
+
+mso + wysiwyg on google => general trouble",1410469468,PHID-USER-hhw22zfd2xzrsyc22lp5,True,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"If you look at the history of the same article, you'll see several edits with the same kind of problems (references added with unwanted formatting: span
+I saw the same kind of problem on other articles, but can't find them right now.
+
+https://fr.wikipedia.org/w/index.php?title=Philippe_Juvin&action=history
+https://fr.wikipedia.org/w/index.php?title=Philippe_Juvin&diff=prev&oldid=101128645
+https://fr.wikipedia.org/w/index.php?title=Philippe_Juvin&diff=prev&oldid=100741981",1392381141,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"Anyway, I tested and couldn't reproduce it.",1392376103,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+VisualEditor: Span tags getting added to references when pasting from Microsoft Office,"(It reminds me of Bug 58689, but the tag is different.)",1392375763,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-r5hdqedtma6idm3jhqfo,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"Intention:
+Whenever a new VE feature is launched it seems as though existing translations are not included.
+
+Steps to Reproduce:
+1. Go to https://sv.wikipedia.org/wiki/Bonsai?uselang=de&veaction=edit
+2. Click on media settings for the first image
+3. Click advanced settings (Erweiterte Einstellungen)
+
+Actual Results:  
+2. Alt_text dialogue reads ""Alternative text""
+3. Position dialogues read ""Position: Left, right, center, none ""
+
+Expected Results:  
+2. Alt_text dialogue reads ""Alternativtext"" (per https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-alttext-section/de)
+3. Should also be all in german (per e.g. https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-position-left/de)
+
+Reproducible: Always
+
+This is not just an issue with the above features (or with uselang=de) but rather happens at every launched VE feature. Since the translations have normally been done before there is no reason why they should not be included as part of the pushing of any new feature.
+
+The VE translations also seem to take longer to go live then translations in other parts of the interface (seems to happen only when there are other VE updates).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=64230",1392370920,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_description,invalid
+New VisualEditor translations not appearing in production as quickly as for other features(?),Almost certainly obsolete.,1723522286,PHID-USER-escte3psz5yfd2nj3jzr,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),We'd need to check if the fix for bug 67805 fixed this as well.,1405948295,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"(In reply to Elitre from comment #7)
+> I wonder if bug 64230 is related?
+
+Seems possible; adding as a see-also.
+
+(In reply to Andre Klapper from comment #6)
+> James: As this is assigned to you, do you plan to investigate?
+
+No; unassigning.",1401726082,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),I wonder if bug 64230 is related?,1401725162,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"James: As this is assigned to you, do you plan to investigate?",1401709302,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"James: As this is assigned to you, do you plan to investigate?",1396871270,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"I am not sure if this counts as an example or not.
+A French Wikipedian reported he spotted a few untranslated messages in the interface. I checked, and the French equivalent for both of them did exist on TranslateWiki. While https://translatewiki.net/wiki/MediaWiki:Visualeditor-dialog-transclusion-multiple-mode/fr is quite recent, https://translatewiki.net/wiki/MediaWiki:Visualeditor-dialogbutton-template-tooltip/fr was created last year. The interface tells me these are the correct messages, but they still won't show up. So I just created the related MediaWiki message locally, but I don't think this should be the solution.",1395064954,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"Time difference between VE and non-VE items I've got no source for rather than a general impression (thus ""seems"" in my statement). In general though we are talking about weeks before the translations appear.
+
+The main issue for me would be why existing translations are not included with the launch of new features? For the above case both de and sv translations existed before the features went live, yet they were not included until 1+ week later. Surely the point of making the messages translatable before they go live is to avoid users having to encounter untranslated strings.",1394535978,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),Anybody having an idea how to investigate this?,1394534423,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+New VisualEditor translations not appearing in production as quickly as for other features(?),"(In reply to Lokal_Profil from comment #0)
+> Intention:
+> Whenever a new VE feature is launched it seems as though existing
+> translations are not included.
+> 
+> Steps to Reproduce:
+> 1. Go to https://sv.wikipedia.org/wiki/Bonsai?uselang=de&veaction=edit
+> 2. Click on media settings for the first image
+> 3. Click advanced settings (Erweiterte Einstellungen)
+> 
+> Actual Results:  
+> 2. Alt_text dialogue reads ""Alternative text""
+> 3. Position dialogues read ""Position: Left, right, center, none ""
+> 
+> Expected Results:  
+> 2. Alt_text dialogue reads ""Alternativtext"" (per
+> https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-
+> alttext-section/de)
+> 3. Should also be all in german (per e.g.
+> https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-
+> position-left/de)
+> 
+> Reproducible: Always
+> 
+> This is not just an issue with the above features (or with uselang=de) but
+> rather happens at every launched VE feature. Since the translations have
+> normally been done before there is no reason why they should not be included
+> as part of the pushing of any new feature.
+> 
+> The VE translations also seem to take longer to go live then translations in
+> other parts of the interface (seems to happen only when there are other VE
+> updates).
+
+Translations of VE items should go live at the same time as non-VE items (as they are done by the same process) – if not, this sounds like a localisation update bug. Moving there to see if anyone has any ideas.",1394477005,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2nfazteqrdf6h4dzw2tg,task_subcomment,NA
+VisualEditor:  Babel box not updated correctly upon editing,"Intention:
+Remove extraneous items from a Babel box
+
+Steps to Reproduce:
+1. Click on the Babel box to edit it. 
+2. Remove unwanted parameters (with trashcan icon).
+3. Apply changes.
+
+Actual Results:  
+Three items were correctly removed, but two that were kept were not displayed in VisualEditor.  (See screenshot to compare diff to VisualEditor's display.)
+
+Expected Results:  
+The transcluded {{#babel:en}} function would display correctly. 
+
+Reproducible: Yes
+",1392340440,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rzxhwx6c7jxhiti6ntu6,task_description,open
+VisualEditor:  Babel box not updated correctly upon editing,This is still a problem.,1532748248,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rzxhwx6c7jxhiti6ntu6,task_subcomment,NA
+VisualEditor:  Babel box not updated correctly upon editing,"Created attachment 14584
+Babel box bug:  ""Review changes"" does not match what's displayed in the lower right corner.
+
+**Attached**: {F12886}",1392340499,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-rzxhwx6c7jxhiti6ntu6,task_subcomment,NA
+VisualEditor: Clear formatting remains selected even after re-applying the styles from the menu,"Highlighted clear formatting option
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Select a text and apply some text styles from the toolbar like ""Bold"", ""Italic""
+3.Now select ""Clear Formatting:
+4.Again reapply these formats
+
+Observed Result:
+Observe that, the though the text formats are reapplied the ""Clear formatting"" option remains selected.
+
+
+See the screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/11thfeb?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13203}",1392147360,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ee2cihypua6u4gysreal,task_description,resolved
+VisualEditor: Clear formatting remains selected even after re-applying the styles from the menu,Verified the fix on production:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit,1397859484,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-ee2cihypua6u4gysreal,task_subcomment,NA
+VisualEditor: Clear formatting remains selected even after re-applying the styles from the menu,This was fixed last month.,1397787388,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ee2cihypua6u4gysreal,task_subcomment,NA
+Flow: default-thumbnail-size preferences are not being followed,"All thumbnails, eg [[File:example.jpg|thumb]], are displaying as 220px (which is the usual wikimedia/mediawiki default, per bug 21117). 
+
+If I change my ""Thumbnail size"" preferences (to 300px for example) at https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-rendering then the thumbnails in existing Flow posts do not change accordingly.
+
+The same applies to new posts that I make, or posts that I edit: all thumbnails are 220px regardless.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1391825160,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-b3kyg6embdoi5bsozap4,task_description,declined
+Flow: default-thumbnail-size preferences are not being followed,Original patch (in VE) is closed - shutting this one down as well,1409929682,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-b3kyg6embdoi5bsozap4,task_subcomment,NA
+Flow: default-thumbnail-size preferences are not being followed,"Possibly this is a WONTFIX, per bug 47804 (""VisualEditor: ""Thumb"" images should display in wiki default thumb size""). Which seems reasonable, but if so, it should be documented.",1393448397,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-b3kyg6embdoi5bsozap4,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,"broken link inspector UI
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add an image
+3.Go to some other tab/window
+4.After an idle time (~5 mins) come back to VE
+5.Open any inspector like galley/link/Math
+
+Observed Result:
+
+All the inspectors are appearing with broken UI
+
+See the screenshots attached.
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Sample Page:https://test2.wikipedia.org/wiki/Test2chromefeb7th?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70580
+
+**Attached**: {F12858}",1391822100,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2vwr5t63vss7tgocwalj,task_description,resolved
+VisualEditor: All inspectors get broken after VE tab is idle for a while,Bah.,1429482768,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,"I'm imagining so, too.",1429482758,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,Probably long fixed…,1429482620,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,Has anyone run into this issue recently?,1424831007,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,"Seems to be fixed. Formula/Gallery inspectors have a slight problem with displaying their border in full-screen view(test2 only), otherwise - betalabs/production display all inspectors correctly after various idle time intervals - 5-20 min.",1419380234,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: All inspectors get broken after VE tab is idle for a while,"Created attachment 14530
+Formula inspector UI
+
+**Attached**: {F12859}",1391822134,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-2vwr5t63vss7tgocwalj,task_subcomment,NA
+VisualEditor: Block format=xml from action=visualeditor API,"Given url:
+http://en.wikipedia.org/w/api.php?action=visualeditor&page=Berlin&paction=parse
+
+Return this:
+<?xml version=""1.0""?>
+<api servedby=""mw1193"">
+  <error code=""internal_api_error_MWException"" info=""Exception Caught: Internal error in ApiFormatXml::recXmlPrint: (notices, ...) has integer keys without _element value. Use ApiResult::setIndexedTagName()."" xml:space=""preserve"" />
+</api>
+
+I guess, I make something wrong, but the error message does not really help me to understand what goes wrong.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62452",1391769780,PHID-USER-nwa6c3hm5nmv7ixrih4p,False,PHID-TASK-6xksishkejfbmz5cphbk,task_description,resolved
+VisualEditor: Block format=xml from action=visualeditor API,"Change 119912 merged by jenkins-bot:
+Block non-JSON API access to VisualEditor, as it won't work
+
+https://gerrit.wikimedia.org/r/119912",1395870545,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6xksishkejfbmz5cphbk,task_subcomment,NA
+VisualEditor: Block format=xml from action=visualeditor API,"Change 119912 had a related patch set uploaded by Jforrester:
+Block non-JSON API access to VisualEditor, as it won't work
+
+https://gerrit.wikimedia.org/r/119912",1395362773,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6xksishkejfbmz5cphbk,task_subcomment,NA
+VisualEditor: Block format=xml from action=visualeditor API,The action=visualeditor API is purely designed for JSON access; we should inform the user that XML / etc. won't work instead of dying horribly.,1395362761,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6xksishkejfbmz5cphbk,task_subcomment,NA
+VisualEditor: Spin out UnicodeJS,"If nothing else, it should probably be in the /lib directory rather than /modules (which will save us a directory's depth of file paths).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391306880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kyycecb3ijdvy6pujf74,task_description,resolved
+VisualEditor: Spin out UnicodeJS,Done at Wikimania 2014.,1416343480,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kyycecb3ijdvy6pujf74,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,,1391281200,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-yjftwp5bygch5jgawu3q,task_description,open
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,This is a Parsoid/RESTBase issue. For caching purposes they don't serve different content based on user preferences.,1448666007,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,"At least this should be forward compatible and support the MathML rendering mode... maybe it's not optimal to classify this as ""Low"" priority.",1442510715,PHID-USER-4sfm3grxdo6hnogm4iqe,True,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,"Sure, but the non-MathJax rendering options are also ignored.",1442506944,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,MathJax is no longer supported. See T99369,1442497325,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,*** Bug 64572 has been marked as a duplicate of this bug. ***,1402295506,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+Parsoid doesn't have a mode to tailor rendered content based on user preferences,"The title change seems to have repurposed this bug. The original title 
+VisualEditor: Math formulas don't display correctly after save (until page is reloaded)  was a dupe of bug 36060 a dependant of bug 51565.
+
+The current title does not describe current behaviour:
+
+With VisualEditor formulae editing beta feature OFF. Formula are displayed as PNG's and can't be edited.
+
+With VisualEditor formulae editing beta feature ON. Formula are initially displayed as PNG's they can be edited. As soon as they are edited they switch to MathJax display but with very garbled output due to Bug 61497.",1398717771,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-yjftwp5bygch5jgawu3q,task_subcomment,NA
+VisualEditor: Providing clearer errors about invalid media item sizes on new Media Settings>Advanced Settings,"Right now, if I add an image for example:https://test2.wikipedia.org/wiki/File:Foo.jpg
+
+Initially in VE from Insert>Media it renders as 229x150.
+If a user attempts to resize it to 350x350 , it will show a message that ""Size Values are invalid""  as it has exceeded the original dimension values.But unless user knows those original dimensions , he or she might keep trying with different values not knowing what should be the input limit.
+
+I think it will be better if we can have more clearer indication in the message saying something like ""the size values are invalid since it has exceeded original dimension""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1391216220,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-m2mltnucijghdtio7lex,task_description,open
+VisualEditor: Providing clearer errors about invalid media item sizes on new Media Settings>Advanced Settings,"(In reply to comment #2)
+> Should those block the 'apply' button, or just give an indication that the
+> size itself won't be applied, giving the user the option to apply the rest
+> of the properties?
+
+The second – see bug 60602.",1391663516,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m2mltnucijghdtio7lex,task_subcomment,NA
+VisualEditor: Providing clearer errors about invalid media item sizes on new Media Settings>Advanced Settings,"Should those block the 'apply' button, or just give an indication that the size itself won't be applied, giving the user the option to apply the rest of the properties?",1391662714,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-m2mltnucijghdtio7lex,task_subcomment,NA
+VisualEditor: Providing clearer errors about invalid media item sizes on new Media Settings>Advanced Settings,"We should probably have several errors:
+
+* ""Size can be up to <width>x<height> pixels."" (if too big for media)
+* ""Size must be positive whole numbers."" (if not valid, e.g. negative or ""hello"")
+* ""Size is limited to <maxsize> pixels."" (if SVGMaxSize reached)",1391661265,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-m2mltnucijghdtio7lex,task_subcomment,NA
+"VisualEditor:  Character set in mathematical symbols is out of order (degree, seconds, minutes)","Reproducible: Always
+
+http://mediawiki.org/wiki/MediaWiki:Visualeditor-specialcharinspector-characterlist-insert should have the logical order of degrees, minutes, seconds, not with seconds in the middle.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1391106240,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-mcubwbacjd3vavyugrkq,task_description,resolved
+"VisualEditor:  Character set in mathematical symbols is out of order (degree, seconds, minutes)","Change 138304 merged by jenkins-bot:
+Re-order special character mathematical symbols to be degrees, minutes, seconds
+
+https://gerrit.wikimedia.org/r/138304",1402335952,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mcubwbacjd3vavyugrkq,task_subcomment,NA
+"VisualEditor:  Character set in mathematical symbols is out of order (degree, seconds, minutes)","Change 138304 had a related patch set uploaded by Jforrester:
+Re-order special character mathematical symbols to be degress, minutes, seconds
+
+https://gerrit.wikimedia.org/r/138304",1402296161,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mcubwbacjd3vavyugrkq,task_subcomment,NA
+OOjs UI: Constructive button has odd green border when disabled,"I'm not sure, but I think this is a regression (it didn't use to be this way).
+
+A button that is flagged as constructive and currently disabled has a green border around its otherwise grey button. When hovering the button the border becomes grey, so it doesn't seem intentional that the border is green (otherwise it should have a hover implementation as well).
+
+This is most visible when opening VisualEditor, the save button has emits this behaviour.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390859100,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4hlmsxmf5qswcobid4c5,task_description,resolved
+OOjs UI: Constructive button has odd green border when disabled,"Change 122879 merged by jenkins-bot:
+apex/button: Reset border-color of disabled button when not hovered
+
+https://gerrit.wikimedia.org/r/122879",1396400208,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4hlmsxmf5qswcobid4c5,task_subcomment,NA
+OOjs UI: Constructive button has odd green border when disabled,"Change 122879 had a related patch set uploaded by Krinkle:
+apex/button: Reset border-color of disabled button when not hovered
+
+https://gerrit.wikimedia.org/r/122879",1396380543,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4hlmsxmf5qswcobid4c5,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**Author:** `gryllida`
+
+**Description:**
+Script viewer software should support sections and section editing, using one-line comments (or special formatting therein) for heading syntax.
+
+---------------------------------------------
+
+/* Foo */
+
+Foo.prototype.bar = function(){
+...
+};
+Foo.prototype.baz = function(){
+...
+};
+
+^^^^^ everything above is in the Foo section
+
+/* Foo 2 */ <---------- this becomes a heading
+
+Foo2.prototype.bar = function(){
+...
+};
+
+Foo2.prototype.baz = function(){
+...
+};
+
+^^^^^ everything above is in the foo 2 section
+
+
+---------------------------------------------
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50962",1390727760,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_description,resolved
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"This seems effectively solved by the SyntaxHighlight extension and its integration for VisualEditor ({T49742}).
+
+{F35040371 height=200}
+
+Source code: [ve.ui.MWSyntaxHighlightDialog.js](https://github.com/wikimedia/mediawiki-extensions-SyntaxHighlight_GeSHi/blob/607afd5b4828af627447ed05ebc74829641706bf/modules/ve-syntaxhighlight/ve.ui.MWSyntaxHighlightDialog.js)",1649198234,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"We actually have a geshi module that does this in the CodeEditor codebase, but it's only the editor mockup, it's not actually able to make changes to the wikitext right now.
+
+Because you seem to be interested in similar functionality, I have fixed up the module in this patch: https://gerrit.wikimedia.org/r/#/c/127451/
+
+Making it fully work would be quite some additional work still, but it's not as far away as I initially figured. The biggest problem is that we need to make sure not to implement everything a dozen times (live preview, editpage, visual editor and inline code editor).",1398258317,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**gryllida** wrote:
+
+There are two reasons behind this.
+
+1) Usually people contain different objects in different files. On wiki, browsing (or simply creating) different files and subfiles of a JS file is far from intuitive. It could make sense to add support for sections.
+
+2) Inline (POD-like) documentation would benefit readability. See i.e. http://juerd.nl/site.plp/perlpodtut .
+
+In other words, CodeEditor should be capable of editing any <source> block on a page without entering edit mode for the entire page. I am renaming the bug title accordingly.",1395793964,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"Can I ask why ?
+
+I mean a section in Javascript is usually not a self-contained unit, it only has meaning icw all the other stuff. So I'm trying to understand why you would want to edit it in that way. Can you clarify how this helps you to edit code ?",1395784846,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**gryllida** wrote:
+
+https://test.wikipedia.org/wiki/User:Gryllida/common.js
+a stupid ugly workaround
+
+https://test.wikipedia.org/wiki/User:Gryllida/afch2/v2
+with sections
+
+syntax highlight ok, code-editor does not pick it up",1391082175,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"See also
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43008#c2",1391079604,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**gryllida** wrote:
+
+(Or Lua script.)",1390862418,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"**gryllida** wrote:
+
+Whatever I see when reading or editing [[Special:MyPage/common.js]]. (There is one extension which highlights the code when reading it, and another extension which is responsible for the code editor; I don't know which one this bug falls under, since both of them would have to support editing a section of a JS or CSS script.)",1390862387,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor should support editing <syntaxhighlight> blocks on a page,"Hi, what is ""Script viewer""? Is this [[mw:Extension:CodeEditor]]?",1390822843,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2vt7ams74ruy224ob3kr,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Dragging and dropping text (as an alternative to keyboard or context menu copy and paste commands) inside CodeEditor does not work.
+
+Since this is basic functionality in every other editor I know this should also be supported by CodeEditor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://github.com/ajaxorg/ace/issues/1879",1390684080,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_description,resolved
+CodeEditor's drag and drop only works after a small delay,I carnt set multiple assigned to by TheDj is also included.,1422657344,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,I cArnt set multiple assigned to by TheDj is also included.,1422657328,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 144780 merged by Brion VIBBER:
+Ace: Update to 2015-01-28
+
+[[https://gerrit.wikimedia.org/r/144780]]",1422657048,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 144780 had a related patch set uploaded (by Paladox):
+Ace: Update to 08-07-2014
+
+[[https://gerrit.wikimedia.org/r/144780]]
+
+#patch-for-review",1418639731,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 144780 had a related patch set uploaded by TheDJ:
+Ace: Update to 08-07-2014
+
+https://gerrit.wikimedia.org/r/144780",1404853195,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,Fixed upstream. I'll schedule an update of the code sometime next week.,1404475578,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 121044 abandoned by TheDJ:
+Remove CodeEditor delay in drag & drop of text
+
+Reason:
+Fix added upstream.
+
+https://gerrit.wikimedia.org/r/121044",1404475516,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Has been fixed upstream (thanks Derk-Jan):
+https://github.com/ajaxorg/ace/commit/63f43da96a1bd2b9894c371fb0feed7e38ef34d6
+
+Let's wait until this fix makes it into MediaWiki's CodeEditor extension...",1403901473,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,Very nice! Thank you for the submission.,1403363117,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,https://github.com/ajaxorg/ace/pull/2012,1403362973,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,i still need to wrap this in some platform dependent if constructs.,1403253798,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Change 121044 had a related patch set uploaded by TheDJ:
+Remove CodeEditor delay in drag & drop of text
+
+https://gerrit.wikimedia.org/r/121044",1395839162,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"So as answered in the linked upstream bug it seems this delay is actually configurable.
+
+Nighwing wrote:
+You can disable dragDelay by setting editor.setOption(""dragDelay"", 0)
+
+Can somebody familiar with CodeEditor implement this? I can't see a reason to keep the delay at this point.",1395836631,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,Thank you for clarifying Eduard !,1395793382,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"Upstream bug is https://github.com/ajaxorg/ace/issues/1879
+
+Let's hope it is easy fixable and not some sort of technical limitation.",1395791458,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"No this definitely is about CodeEditor!
+
+And while I just wanted to write that this is definitely not fixed I just realized during some additional testing that it actually is working... but only somehow.
+
+I don't know if I have a very special way of dragging/dropping but actually dragging only starts after a small delay (note that after clicking highlighted text the cursor only changes to the move cursor after approx. 100 ms). If you start moving the mouse before it will just create a new selection.
+However when normally dragging/dropping I start moving the mouse right away. Moving the mouse over the highlighted text, clicking, then *waiting* and only after waiting beginning to move the mouse is just counterintuitive and different from every other program I know.
+
+Since it therefore doesn't seem to be specific to MediaWiki's implementation (Ace's web demo ""works"" exactly the same) I'll report a bug for Ace directly however. I'll update this bug with the respective info then.",1395790507,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+CodeEditor's drag and drop only works after a small delay,"This works for me in the beta at least: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Module:HtmlBuilder&action=edit
+
+It might be that the reporter is actually talking about VisualEditor, which indeed does not seem to support drag and drop of text.",1395787108,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-35qnbteoopi7ow3gqvxx,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),This should especially useful as new images may not appear in the API search results due to caching.,1390585980,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_description,resolved
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 617434 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@REL1_35] Follow-up I0a1a889: Show user uploads in gallery dialog
+
+https://gerrit.wikimedia.org/r/617434",1596141663,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 617434 had a related patch set uploaded (by Bartosz Dziewoński; owner: Esanders):
+[mediawiki/extensions/VisualEditor@REL1_35] Follow-up I0a1a889: Show user uploads in gallery dialog
+
+https://gerrit.wikimedia.org/r/617434",1596141357,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 617490 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Follow-up I0a1a889: Show user uploads in gallery dialog
+
+https://gerrit.wikimedia.org/r/617490",1596129003,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 617490 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Follow-up I0a1a889: Show user uploads in gallery dialog
+
+https://gerrit.wikimedia.org/r/617490",1596123964,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 210831 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWMediaDialog: Show user uploads when no query provided
+
+https://gerrit.wikimedia.org/r/210831",1594647105,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 589343 **merged** by jenkins-bot:
+[mediawiki/core@master] mw.widgets.MediaSearchWidget: Show user uploads when query empty
+
+https://gerrit.wikimedia.org/r/589343",1594567921,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 210831 restored by Esanders:
+MWMediaSearchWidget: Show user uploads
+
+[[https://gerrit.wikimedia.org/r/210831]]",1587052040,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 589343 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/core@master] mw.widgets.MediaSearchWidget: Show user uploads when query empty
+
+[[https://gerrit.wikimedia.org/r/589343]]",1587051894,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 210831 abandoned by MarkAHershberger:
+MWMediaSearchWidget: Show user uploads
+
+[[https://gerrit.wikimedia.org/r/210831]]",1492468066,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"@Jdforrester-WMF I see the #Design tag was added but just wanted to make it explicit, I assume correctly from T154234#3072200 that this task is currently blocked on a design for showing user uploads in the Media insertion dialog so that <https://gerrit.wikimedia.org/r/210831> can be reworked to implement that?",1488594068,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 210831 had a related patch set uploaded (by Esanders):
+WIP Show recent uploads in MWMediaSearchWidget
+
+[[https://gerrit.wikimedia.org/r/210831]]
+",1450311354,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Jdforrester-WMF writes:
+
+> This is a functionality task. The search results caching task was
+> resolved by the switch to ElasticSearch months ago.
+
+Just to be clear, though, this is something I would see in any browser,
+right?  I've seen it in multiple browsers and across reboots so it isn't
+a local caching problem.",1424962321,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),">>! In T62398#1067311, @MarkAHershberger wrote:
+> This issue (can't see recent uploads in the selection) was pointed out to me by a client.  At first I thought this was an IE caching problem, but I'm glad  to see it has been spotted elsewhere.
+
+This is a functionality task. The search results caching task was resolved by the switch to ElasticSearch months ago.",1424895969,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"This issue (can't see recent uploads in the selection) was pointed out to me by a client.  At first I thought this was an IE caching problem, but I'm glad  to see it has been spotted elsewhere.",1424895867,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Change 109670 had a related patch set uploaded by Esanders:
+WIP Show recent uploads in MWMediaSearchWidget
+
+https://gerrit.wikimedia.org/r/109670",1391099540,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Re: search caching, 'File:Three_sided_football_pitch.svg' is still not showing up in search results, an hour after uploading.",1390595356,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Yes there will be edge cases where the username on commons is different, but that is an edge case.
+
+We can fill in the first row with recent uploads if found (which solves the case of ""most users don't upload"") and then fill with page title.",1390595056,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"Currently we show the name of the article. Lots of users have mentioned that this is helpful (albeit limited utility for non-English users until we implement Wikidata-based item searching instead of string searching).
+
+Walking away from this benefit from the somewhat-dubious benefit of your own uploads (most users don't upload, and we'd have no way to check for your ""own"" uploads on foreign repos) feels like a regression.",1390593864,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),We can just show recent uploads when no search term is entered.,1390593454,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget),"(In reply to comment #0)
+> This should be relatively simple compared to full UploadWizard integration,
+
+… but turns a simple search interface into a (multi-tabbed?) optional series of interfaces. :-(
+
+> new images may not appear in the API search results due to caching.
+
+{{cn}}
+
+The exceptional amount of work put into the new search system has this as its most significant user-facing improvement.",1390587311,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o4vsn4ihg5s72o4pgmhn,task_subcomment,NA
+VisualEditor:  Unclosed <dl> and <div> tags caused by absent {{refend}} template cannot be repaired,"Intention:
+Remove a line that appears in the last section of a page, underneath a section that has an unclosed/unpaired {{refbegin}} template.
+
+Steps to Reproduce:
+1. Open https://en.wikipedia.org/w/index.php?oldid=592187387 in VisualEditor.
+
+2. Try to select anything after the ==Bibliography== section, e.g., anything in the ==External links== section.
+
+Actual Results:  
+The cursor knows only two positions:  before the refbegin template, and in the slug at the bottom of the page.  You can't select or edit anything in between.
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1390579800,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-otqxqq3jfgirvkvr5ko2,task_description,resolved
+VisualEditor:  Unclosed <dl> and <div> tags caused by absent {{refend}} template cannot be repaired,"No reply. Assuming this is done. If not, then please reopen.",1617657078,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-otqxqq3jfgirvkvr5ko2,task_subcomment,NA
+VisualEditor:  Unclosed <dl> and <div> tags caused by absent {{refend}} template cannot be repaired,"Seven years later, on https://en.wikipedia.org/w/index.php?title=Chemotherapy&veaction=edit&oldid=592187387 , this shows some transclusion info on the right:
+{F32426376}
+
+Good enough? 
+Tasks shouldn't be stalled forever.",1604399234,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-otqxqq3jfgirvkvr5ko2,task_subcomment,NA
+VisualEditor:  Unclosed <dl> and <div> tags caused by absent {{refend}} template cannot be repaired,I'm not sure what else you could expect VE to do here.,1414812075,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-otqxqq3jfgirvkvr5ko2,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"Steps to reproduce:
+
+- create a simple page with just this text: <syntaxhighlight lang=""xml"">></syntaxhighlight>
+- example page: https://test2.wikipedia.org/wiki/Codez
+- when the page is saved, only this is displayed, as expected: >
+
+- edit the page with visual editor
+- edit the text using syntaxhighlight editor
+- for example, add just this: <
+- see attached screen shot #1
+
+- use ""back"" icon to see how the text will look like
+- I was expecting to see this as page text: ><
+- instead, the preview says page text is: &gt;&lt;
+- see attached screen shot #2
+
+- when the page is saved, the text is displayed correctly: ><
+- see attached screen shot #3
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1390390860,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-yagspunhz2cfycrqyzbn,task_description,resolved
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"This is actually the same issue as bug 57429, let's merge the bugs.
+
+*** This bug has been marked as a duplicate of bug 57429 ***",1404486826,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,*** Bug 66456 has been marked as a duplicate of this bug. ***,1404435630,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"Created attachment 14357
+screen shot #3
+
+**Attached**: {F12969}",1390390978,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"Created attachment 14356
+screen shot #2
+
+**Attached**: {F12968}",1390390950,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't,"Created attachment 14355
+screen shot #1
+
+**Attached**: {F12966}",1390390931,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-yagspunhz2cfycrqyzbn,task_subcomment,NA
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Steps to reproduce:
+
+1.Open a page which has a gallery inside it with VE
+2.Select the gallery and open the gallery inspector
+3.Close the gallery inspector 
+
+Observed Result:
+
+The ""Save page"" button of the page gets enabled although no change has been made in the gallery inspector
+
+Test Environment: https://test2.wikipedia.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:https://test2.wikipedia.org/wiki/Thedomtest
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1390348020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fpau7gga5ngffxkbjtka,task_description,resolved
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Change 342240 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor] Update gallery actions in response to changes
+
+[[https://gerrit.wikimedia.org/r/342240]]
+",1489520603,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fpau7gga5ngffxkbjtka,task_subcomment,NA
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Change 342240 had a related patch set uploaded (by Tchanders):
+[mediawiki/extensions/VisualEditor] Update gallery actions in response to changes
+
+[[https://gerrit.wikimedia.org/r/342240]]
+",1489518688,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fpau7gga5ngffxkbjtka,task_subcomment,NA
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Change 315449 abandoned by Tchanders:
+WIP Update gallery dialog actions to reflect presence of changes
+
+Reason:
+This was split into two patches
+
+[[https://gerrit.wikimedia.org/r/315449]]",1489164701,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fpau7gga5ngffxkbjtka,task_subcomment,NA
+VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction,"Change 315449 had a related patch set uploaded (by Tchanders):
+WIP Update gallery dialog actions to reflect presence of changes
+
+[[https://gerrit.wikimedia.org/r/315449]]
+",1476233341,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-fpau7gga5ngffxkbjtka,task_subcomment,NA
+Fully alphabetize Wikimedia configuration file visualeditor.dblist,"https://noc.wikimedia.org/conf/visualeditor.dblist
+
+This should be fully alphabetized, in my opinion. While people with intimate knowledge of Wikimedia's structure can likely discern and explain the current order, it seems like a lot more overhead than any value provided. A simple alphabetical index is easier to maintain (including insertion), it's more consistent with the other lists of databases (as far as I know), etc.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1390266360,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-wljhvk4gfcklidyyzcbh,task_description,declined
+Fully alphabetize Wikimedia configuration file visualeditor.dblist,"Why? It's a list of 300 dbnames; no-one sane is going to read it, just grep through it.
+
+The current structure is sorted {public/private,project,alphabetical}. This is to prevent accidental mis-configuration. Eventually VE will be on for all wikis, but then we'll just delete this dblist.
+
+If dblists supported comments it'd probably be easier to see, I agree, but that is not this bug.",1390321562,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wljhvk4gfcklidyyzcbh,task_subcomment,NA
+Client-side previewing,"I'm not sure how well these would work, but at least here in China, it is slow to wait for previews of musical scores for each modification. If you could add client-side support to Score, perhaps via:
+
+* http://code.google.com/p/abcjs/
+* https://github.com/incompleteopus/vexabc
+
+...I wonder whether client-side rendering support (ideally in SVG in case notes could be synchronized with the music play-back in the future) could be added, if not now, then maybe after the main Mediawiki WYSIWYG interface stabilizes?
+
+And support for the emerging Web Audio standard would be awesome for client-side audio play-back as well...
+
+Also, with ABC seeming (to my quick glance) more like an open standard than Lilypond, might it make sense to make ABC the default?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1390051560,PHID-USER-gljzp3uzec5ukggh6xdk,False,PHID-TASK-fpifldug4t73yao6kw5o,task_description,duplicate
+Client-side previewing,"#visualeditor implements similar support to your examples. Also, both ABC and Lilypond are open, but Lilypond is more flexible and has `abc2ly`. ABC doesn't have vice-versa :)",1502063966,PHID-USER-u66bgsaukythpwcdyjdu,False,PHID-TASK-fpifldug4t73yao6kw5o,task_subcomment,NA
+"Separate UploadWizard's data-handling, interface, and other controlling methods and put generally-applicable code into MediaWiki","In the past few years we've worked really hard to bring UploadWizard to a usable state, and now that we have a Multimedia team framework to actually do some good work on it, and we have the impetus to start making the upload pipeline way better, let's do it the right way: Let's make this project the organized, well-engineered machine it should have been in the first place.
+
+I would particularly emphasize code conventions being followed, jshint conformance, an eye towards an MVC-like structure (nothing strict, but as a general goal...), building toward libraries that can be used elsewhere, and a variety of different possible interfaces.
+
+Ideally none of the upload steps will be entangled unnecessarily with other steps, and we will be able to untangle them when necessary and put them in different pages or tools.
+
+Ideally we will use the brilliant work- and complexity-reducing technology (oojs, oojs-ui, jQuery promises, moment.js) that other projects have started using in recent times.
+
+It is an absolute *must* that we build tests for this system as we are building it, if we want this to be a generally useful set of tools for other projects. Same for documentation.
+
+The leaders in LOC for active frontend projects deployed on the cluster are* VisualEditor, UploadWizard, Flow, and MultimediaViewer (in no particular order). Let's start bringing the upload pipeline projects closer to the high standards that other projects are holding themselves to.
+
+* According to an unscientific survey based on guesswork
+
+See https://www.mediawiki.org/wiki/Requests_for_comment/More_general_frontend_uploading_tools for more.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62513",1389627360,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-gtvhfsoc4hivpuvxra7b,task_description,resolved
+"Separate UploadWizard's data-handling, interface, and other controlling methods and put generally-applicable code into MediaWiki",`<prtksxna> James_F: I think mw.Upload and mw.ForeignStructuredUpload resolved this.`,1442332652,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gtvhfsoc4hivpuvxra7b,task_subcomment,NA
+VisualEditor: Work correctly in Draft namespace (tracking),"This is a tracking bug for any problems in VisualEditor associated with the Draft: namespace at the English Wikipedia.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389304860,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-t7jppwsetf7fxoydv5qc,task_description,resolved
+VisualEditor: Work correctly in Draft namespace (tracking),Indeed. All known issues fixed. Marking as such.,1415031855,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-t7jppwsetf7fxoydv5qc,task_subcomment,NA
+VisualEditor: Work correctly in Draft namespace (tracking),It seems slightly silly to have a whole tracking bug lying around to track one single bug...,1414807490,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-t7jppwsetf7fxoydv5qc,task_subcomment,NA
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","It's not clear how the ""Tag the edit for further review"" option for AbuseFilter rules would work for Flow. Maybe it would add something to the Special:RecentChanges entry for FLow.
+
+This is mentioned in https://www.mediawiki.org/wiki/Flow/Administration_notes
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**: {T64750}",1389145320,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_description,open
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","See here for an example of where AF tags appear:
+https://en.wikipedia.org/w/index.php?title=User:Quiddity_%28WMF%29/sandbox&action=history
+https://en.wikipedia.org/w/index.php?title=Special:Contributions/Quiddity_%28WMF%29&dir=prev&offset=20140107194435&limit=2&target=Quiddity+%28WMF%29
+""(Tag: VisualEditor)""
+
+documentation at:
+https://en.wikipedia.org/wiki/Wikipedia:Tags
+(and more linked in the navbox at the top)",1389212921,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_subcomment,NA
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","We may be able to get this tag indication into the presentation of Flow changes in RecentChanges, Watchlist, Special:Log and history.",1389208749,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_subcomment,NA
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","FWIW, I took a very quick look at that code in AbuseFilter yesterday - this is pretty much what it does for article edits.
+
+AFAICT, when running a filter is matched and it needs to tag, something is added to array AbuseFilter::$tagsToSet, which is then read from a hook triggered when saving recentchanges for an article edit (RecentChange_save)",1389186155,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_subcomment,NA
+"Flow: AbuseFilter ""Tag the edit for further review"" doesn't work","**bingle-admin** wrote:
+
+The WMF core features team tracks this bug on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/flow/cards/701, but people from the community are welcome to contribute here and in Gerrit.",1389145528,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ppr5wcsdufpb6eyyasrg,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"On wiki's with Scribunto installed, when viewed in the mobile site, the exception ""Uncaught Error: Unknown dependency: ext.scribunto"" is thrown which prevents any further JavaScript from running.
+
+This is because the module is not registered on mobile.
+
+It also depends on jquery.ui.dialog code which pulls in the entire jquery.ui library - we certainly do not want on mobile where JavaScript load should be as tiny as possible.
+
+I doubt we'd want to run this code on mobile thus the use of addInlineScript needs to be avoided since the module doesn't exist in the mobile environment. At the very least it should be wrapped with a try catch so say it is acceptable to fail.
+
+Seems to have been introduced by https://gerrit.wikimedia.org/r/#/c/5617/1,publish
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389142380,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_description,resolved
+Scribunto pulls in jquery.ui.dialog for error reporting,"Change 109262 abandoned by TheDJ:
+Conditionally load jquery.ui.dialog for Scribunto errors
+
+Reason:
+Fixed with: https://gerrit.wikimedia.org/r/#/c/118944/
+
+https://gerrit.wikimedia.org/r/109262",1396790729,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,I'd still advise you to move away from jquery.ui but this is not effecting mobile now so I am happy.,1395858075,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Change 118944 merged by jenkins-bot:
+Don't try to inline load ext.scribunto on mobile
+
+https://gerrit.wikimedia.org/r/118944",1395857889,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Change 118944 had a related patch set uploaded by Hoo man:
+Don't try to (inline load) ext.scribunto if it isn't registered
+
+https://gerrit.wikimedia.org/r/118944",1394938224,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Change 109262 had a related patch set uploaded by TheDJ:
+Conditionally load jquery.ui.dialog for Scribuntu errors
+
+https://gerrit.wikimedia.org/r/109262",1390525326,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Updated summary since of course it doesn't pull in the whole of jQuery UI, it pulls in jquery.ui.dialog and (implicitly) its 7 dependencies, so 8 out of the 17 JavaScript files in resources/jquery.ui/",1390427962,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"let's just dynamically load it, it's simple and not too many 'normal' users are using it anyways. When OOjs is more mature, we can just switch it over.",1390427852,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"One problem with alert() is that it's not HTML, so you couldn't click on the source file links which appear in the Scribunto backtraces.
+
+(In reply to comment #1)
+> Okay this doesn't look so bad now as it seems to only become a problem when a
+> ScribuntoError occurs (I'm not sure how often this occurs on wiki's - I've
+> only managed to replicate this locally). 
+
+You can replicate it on the pages in this category:
+
+https://en.wikipedia.org/wiki/Category:Pages_with_script_errors
+
+It looks like there are currently no such pages in the main namespace, so the impact of this bug on readers of en.m.wikipedia.org is negligible.
+
+There's a bug in Scribunto which causes jquery.ui.dialog and the hidden category to be added even if no errors are emitted into the final HTML, say due to the error being sent to the condition of a {{#iferror:}}. At one point, there were tens of thousands of pages in [[Category:Pages with script errors]] for no obvious reason, possibly due to that bug. So, it would have affected mobile readers at that time. That could be reported separately if it's not already.
+
+> However it seems bizarre to me that the
+> entire jQuery UI library would be loaded simply for error reporting...
+
+I think error reporting is the most important feature in Scribunto, it's central to the usability of Lua scripting. So I don't think it's bizarre that it loads libraries. It's just somewhat inefficient. 
+
+I would be fine with a lightweight DIY thing, or with dynamic loading of jquery.ui.dialog on click of the error message, with a spinner.",1390427209,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"OOjs is in core, but if you want to make dialogs, you probably need OOjs UI as well, which is still only in VisualEditor.",1390427077,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"(In reply to comment #4)
+> * Remove the dialog code from Scribunto and just use a JS alert in the
+> meantime. Alerts are pretty unfriendly (since they take over the browser,
+> stop
+> JS execution, etc.), but since it's such a limited use, it might be OK for a
+> short-term fix.
+
+I believe some browsers are starting to block alters entirely.
+
+(In reply to comment #5)
+> As stated the correct thing to do would be to start using OO.js which is in
+> core.
+
+Patches welcome. Or even links to examples.",1390425282,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"In case I was clear please do not follow Ryan's suggestion of 
+""Make jquery.ui and jquery.ui.dialog loadable on mobile by giving them the
+'mobile' target in the module definition (and make sure they are only loaded
+when there is an error)""
+
+An alert would make more sense, using jQuery UI is overkill for this use case imo.",1390425155,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"jQuery UI != jQuery
+Use jQuery by all means of a jQuery plugin for this - you do not need a huge library the size of jQuery UI.
+
+jQuery UI is totally unsuitable for mobile. Please do not load it to simply use I'd guess about 2% of the library..
+
+As stated the correct thing to do would be to start using OO.js which is in core.",1390425066,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"For desktop, jQuery UI is fine (at least until OO.js is more widely adopted). The only problem is that mobile doesn't want to load jQuery UI unless absolutely necessary, and Scribunto is used on both desktop and mobile.
+
+There are two possible short-term solutions:
+* Make jquery.ui and jquery.ui.dialog loadable on mobile by giving them the 'mobile' target in the module definition (and make sure they are only loaded when there is an error)
+* Remove the dialog code from Scribunto and just use a JS alert in the meantime. Alerts are pretty unfriendly (since they take over the browser, stop JS execution, etc.), but since it's such a limited use, it might be OK for a short-term fix.",1390422361,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,What's the point of having jQuery if we're not supposed to use it?,1390420768,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,"Realistically, Scribunto does not require the full jQuery UI. I feel that it should roll its own ""script error"" popup, since jQuery UI Dialogs were not really designed for this use.",1390303199,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+Scribunto pulls in jquery.ui.dialog for error reporting,Okay this doesn't look so bad now as it seems to only become a problem when a ScribuntoError occurs (I'm not sure how often this occurs on wiki's - I've only managed to replicate this locally). However it seems bizarre to me that the entire jQuery UI library would be loaded simply for error reporting...,1389142792,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-4aq45pqxrqjz2qfggqde,task_subcomment,NA
+VisualEditor: Toolbar doesn't float properly in standalone demo,"It either snaps to the top left of the screen (instead of lining up with the surface), or it tries to render with 0 width (especially if you switch page)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1389017880,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-tb2ge6debarxu3vvlo2k,task_description,resolved
+VisualEditor: Toolbar doesn't float properly in standalone demo,*** Bug 60183 has been marked as a duplicate of this bug. ***,1390864797,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tb2ge6debarxu3vvlo2k,task_subcomment,NA
+VisualEditor: Toolbar doesn't float properly in standalone demo,"Change 109489 merged by jenkins-bot:
+Attach container to DOM before initialising target in demo
+
+https://gerrit.wikimedia.org/r/109489",1390863488,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tb2ge6debarxu3vvlo2k,task_subcomment,NA
+VisualEditor: Toolbar doesn't float properly in standalone demo,"Change 109489 had a related patch set uploaded by Esanders:
+Attach container to DOM before initialising target in demo
+
+https://gerrit.wikimedia.org/r/109489",1390692956,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tb2ge6debarxu3vvlo2k,task_subcomment,NA
+VisualEditor: Toolbar doesn't float properly in standalone demo,"I can't find a cause using git-bisect.
+
+VisualEditor.git goes back to 20 Dec 2013, which already exhibits the problem.
+
+Bisecting in mediawiki/extensions/VisualEditor.git also led to nothing as the problem was never present there to begin with.
+
+I suspect the problem may be caused by us having removed a stylesheet in the repo split that is now in the ve-mw only, but should be under ve/ve instead.",1389820688,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tb2ge6debarxu3vvlo2k,task_subcomment,NA
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,"Intention:
+Rearrange the sections on a page
+
+Steps to Reproduce:
+1. Select the entire last section
+2. Cut (Command-X) the section
+3. Paste it elsewhere
+
+Actual Results:  
+The formatting for the section heading (not the formatting for the last line) remains at the end of the page.
+
+
+Expected Results:  
+The last line should either disappear entirely (be replaced by a slug) or be set to default/Paragraph styling
+
+Reproducible: Always
+
+Removing the blank section heading produced its own problems; look for the next bug report.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/w/index.php?title=Celebrity_branding&diff=589156664&oldid=583130311
+**See Also**:
+{T52100}
+{T57769}",1388853360,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_description,resolved
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,Verified in beta.,1427238826,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_subcomment,NA
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,"Change 162310 merged by jenkins-bot:
+For empty / whitespace-only headings, output <p> instead of <h#>
+
+[[https://gerrit.wikimedia.org/r/162310]]",1426893387,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_subcomment,NA
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,"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",1424197332,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_subcomment,NA
+VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==,"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",1411496974,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-xfhhffifiyg3hfxvn6x3,task_subcomment,NA
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that","In edit mode
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Now add a reference to the page
+3,Add a bullet or numbered list
+4.Add references list from Insert>References list
+5.Save the page
+
+Observed Result:
+The references list appeared as a bulleted item or numbered item of the preceding list
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit
+
+See the screenshot attached
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12662}",1388433240,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dztchev2qtofstunypcs,task_description,open
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that",The MW behavior described here is reported as a bug in T27939.,1664896979,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-dztchev2qtofstunypcs,task_subcomment,NA
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that","I was able to reproduce this bug today and figured it was already reported earlier. My observation is pretty much the same as above.
+
+{F4452302}",1473459726,PHID-USER-vyft7xsn4ggkthnt52s2,False,PHID-TASK-dztchev2qtofstunypcs,task_subcomment,NA
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that","Eww, MW, why do we hate you so? This. This is why.",1394504318,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dztchev2qtofstunypcs,task_subcomment,NA
+"VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that","Created attachment 14193
+In read mode
+
+**Attached**: {F12663}",1388433340,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-dztchev2qtofstunypcs,task_subcomment,NA
+VisualEditor: Any changes made to an article by other users since switching into VE aren't reflected when switching back to read mode,"Steps to reproduce:
+
+1.Open an article in read mode in two different tabs of same browser or in two different browsers.
+
+2.Now edit the page using one browser or tab
+
+3.Save the change
+
+4.Now open the same article with VE using another browser or tab
+
+5.Click on ""cancel""
+
+Observed Result:
+After step 4 the change made in step 2 by another browser or tab are correctly reflected in the edit mode .
+
+But after pressing cancel on step 5 , it has been observed that the readmode is still not showing the change done in step 2 unless user refreshes it.
+
+It will be better if both Edit mode and Read mode shows consistent content even if the change is made by other user/browser session
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1388174160,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-wqxkbe4urxqrr546bvml,task_description,open
+VisualEditor: document.activeElement can change unexpectedly while typing in VE editor,"**Author:** `jhall`
+
+**Description:**
+After observing some strange results from an automated Ruby test for cursor movement in the Visual Editor CE surface, we did some digging, and it appears that while a user is typing away happily and making and edit, the document.activeElement flip-flop several times.  
+
+I'm assuming this is unintentional behavior, thus the bug ticket.
+
+Repro steps:
+
+1)  Visit this page: https://test2.wikipedia.org/wiki/User:Selenium_user/cursor_test_page_chromedriver_bug
+2)  Click into VE editing mode.
+3)  With cursor placed immediately in front of the letter ""a"" in the word ""after"", press the right arrow key several times in succession. 
+4)  When your right-arrow-clicking brings you to the reference, the document.activeElement switches from ""ve-ce-documentNode ve-ce-branchNode noime"" to ""ve-ce-surface-paste""
+
+I'm assuming that when the user is typing in the ""editing box"", the document.activeElement should not be changing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57552",1388165580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dsrtx3tiu5iommxo6ovz,task_description,declined
+VisualEditor: document.activeElement can change unexpectedly while typing in VE editor,This is intentional. We move the selection the paste target so we can intercept copy events. Users should not care what document.activeElement is set to.,1701962577,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dsrtx3tiu5iommxo6ovz,task_subcomment,NA
+VisualEditor: document.activeElement can change unexpectedly while typing in VE editor,"**jhall** wrote:
+
+Java program used to generate the blow-by-blow in the previous attachment
+
+**Attached**: {F12401}",1388165960,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dsrtx3tiu5iommxo6ovz,task_subcomment,NA
+VisualEditor: document.activeElement can change unexpectedly while typing in VE editor,"**jhall** wrote:
+
+Blow-by-blow of document.activeElement as right arrow key is pressed many times in succession
+
+**Attached**: {F12400}",1388165821,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dsrtx3tiu5iommxo6ovz,task_subcomment,NA
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,"Steps to reproduce:
+
+1.Open a page with VE in Chrome
+2.Copy a hiero
+3.Open another page in FF
+4.Paste the hiero into it
+
+Observed Result:
+An empty template table appears.The resulting wikitext is:
+{|
+
+|
+{|
+
+|
+
+|}
+
+|}
+
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=26th_paste_ff&veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388094480,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3e33c6y5allxgx2h75vj,task_description,resolved
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,WFM. Likely fixed at some point in the last two years.,1453424212,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-3e33c6y5allxgx2h75vj,task_subcomment,NA
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,Is this still occurring?,1439321293,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3e33c6y5allxgx2h75vj,task_subcomment,NA
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,"While doing hiero copy-paste from  a page opened in FF to another page in FF, the following wikitext appears:
+
+{| class=""mw-hiero-table mw-hiero-outer"" dir=""ltr""
+
+|
+{| class=""mw-hiero-table""
+
+|
+
+|}
+
+|}",1388094678,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3e33c6y5allxgx2h75vj,task_subcomment,NA
+VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF,"Created attachment 14174
+Screenshot in the edit mode
+
+**Attached**: {F12372}",1388094586,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-3e33c6y5allxgx2h75vj,task_subcomment,NA
+"VisualEditor:  Use colorful icons, or provide an option to use colorful icons / themes","Gryllida suggests that VisualEditor have colorful icons.  Alternatively, the existing monochrome icons could be kept, but editors could be given the option of choosing a Microsoft-style ""theme"" to change the appearance of the icons.  
+
+In addition to being fun, it is possible that other icon styles would improve accessibility for some users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1387824900,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-sk77bsakmg2v6bm4lawd,task_description,declined
+Left and right arrow keys jump to images if image has previously been viewed in Media Viewer,"I have enabled the experimental Media Viewer feature on Wikipedia, and when I click on an image, left and right scroll through the images on the page in full-window mode.
+
+However, when editing a page in Visual Editor, this keeps happening (that is, images from the article keep appearing in full-window mode) when I am trying to move around with the cursor keys.
+
+VisualEditor should disable this ""feature"", as it's obviously not wanted when editing a page!
+
+I use the Chromium browser.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: Linux
+**Platform**: PC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58266",1387747020,PHID-USER-bug3zrlooz3bdmi4fyl7,False,PHID-TASK-kz6xwcltn5xmr2ey75r7,task_description,resolved
+Left and right arrow keys jump to images if image has previously been viewed in Media Viewer,"Yeah, I don't see why this would still have been an issue on December 22, there should be no way to get this issue to happen anymore.
+
+If someone else sees this issue, speak up quick, but please be willing to discuss it with us relatively quickly, ideally on IRC, so we can nail it down.
+
+Thanks!",1389379350,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-kz6xwcltn5xmr2ey75r7,task_subcomment,NA
+Left and right arrow keys jump to images if image has previously been viewed in Media Viewer,"This should have been fixed in Media Viewer with bug 58266 being closed (the code was deployed to all wikis on 12 December), but if you're still encountering it that's not good.
+
+Does it still break in this manner? What happens if you refresh?",1388917874,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kz6xwcltn5xmr2ey75r7,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Intention:
+Move a section of a page by cutting it out of one place and pasting it into the right place.
+
+Steps to Reproduce:
+1.  Close an unwanted browser tab.
+2.  Select several paragraphs in VisualEditor.
+3.  Press Command-x to cut (not just copy) the material.
+4.  Notice that the just-closed browser window has reappeared.  (Command-z/Undo in Safari reopens a tab that you just closed.)
+
+
+
+Reproducible: Always
+
+I am unable to reproduce this in Firefox, presumably because selecting text within VisualEditor seems to clear (or otherwise make unavailable) the 'undo' buffer.  So even if VisualEditor is telling Firefox to undo something, Firefox believes that there there's nothing to undo.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57217",1387498860,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_description,resolved
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156776 merged by jenkins-bot:
+Remove unnecessary execCommand('undo') from onCut
+
+https://gerrit.wikimedia.org/r/156776",1409230172,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156776 had a related patch set uploaded by Esanders:
+Remove unnecessary execCommand('undo') from onCut
+
+https://gerrit.wikimedia.org/r/156776",1409227881,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156733 abandoned by Catrope:
+Avoid undo when processing a cut event.
+
+Reason:
+Duplicate of https://gerrit.wikimedia.org/r/156593
+
+https://gerrit.wikimedia.org/r/156733",1409183885,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156593 restored by Catrope:
+Avoid undo when processing a cut event.
+
+Reason:
+Whoops, obviously this isn't a duplicate of itself...
+
+https://gerrit.wikimedia.org/r/156593",1409183878,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156593 abandoned by Catrope:
+Avoid undo when processing a cut event.
+
+Reason:
+Duplicate of https://gerrit.wikimedia.org/r/156593
+
+https://gerrit.wikimedia.org/r/156593",1409183861,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156733 had a related patch set uploaded by Catrope:
+Avoid undo when processing a cut event.
+
+https://gerrit.wikimedia.org/r/156733",1409183761,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"Change 156593 had a related patch set uploaded by Catrope:
+Avoid undo when processing a cut event.
+
+https://gerrit.wikimedia.org/r/156593",1409165641,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"**aditya** wrote:
+
+Pushed a patch to gerrit. 
+
+https://gerrit.wikimedia.org/r/#/c/156593/",1409164825,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,"**aditya** wrote:
+
+Patch to prevent undo on cut
+
+Here's a patch that avoids the 'undo' execCommand and fixes the issue for me in Chromium 36.0.1985.125 (Linux).
+
+I'm assuming that the timeout was originally intended to let the code in that block be safely executed only after the browser manipulated (deleted) the selection. It appears that this no longer works and the code is processed before the text is actually deleted.
+
+Therefore this change uses preventDefault() to not let the browser do it's thing, and directly handles the entire removal with a transaction.
+
+This is my first patch to VE, sorry if I made any obvious mistakes. :)
+
+**Attached**: {F12701}",1409160577,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari,Ick. This feels like a pretty poor browser bug here…,1408642368,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hjqdq6dhlnlap44q7i5f,task_subcomment,NA
+"Disable ""Beta"" suffixes on tabs for VisualEditor opt-in wikis","On opt-in wikis, users already have to explicitly choose to be able to use VisualEditor, and they get a warning the first time they do so. Adding beta suffixes all over the UI is a leftover from opt-out status and only appropriate in wikis that are opt-out, and where communities explicitly request such notices to be present.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387305900,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-vfujufijqzs5z2vprlzj,task_description,resolved
+"Disable ""Beta"" suffixes on tabs for VisualEditor opt-in wikis","Change 112590 merged by jenkins-bot:
+Disable 'beta' label in tab for the VE opt-in wiki (enwiki)
+
+[[https://gerrit.wikimedia.org/r/112590]]",1426001948,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vfujufijqzs5z2vprlzj,task_subcomment,NA
+"Disable ""Beta"" suffixes on tabs for VisualEditor opt-in wikis","Change 112590 had a related patch set uploaded (by Jforrester):
+Disable 'beta' label in tab for the VE opt-in wiki (enwiki)
+
+[[https://gerrit.wikimedia.org/r/112590]]
+",1425512003,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vfujufijqzs5z2vprlzj,task_subcomment,NA
+"Disable ""Beta"" suffixes on tabs for VisualEditor opt-in wikis","Change 112590 had a related patch set uploaded by Jforrester:
+Disable 'beta' label in tab for the VE opt-in wiki (enwiki)
+
+https://gerrit.wikimedia.org/r/112590",1392069493,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vfujufijqzs5z2vprlzj,task_subcomment,NA
+VisualEditor: Outline widget in booklet layout responds to mouse up events even if they started elsewhere,"These should probably only respond to click events although it seems they currently support the click and drag functionality of a drop down box. If you are editing a textarea in the right hand panel and you click and drag from right to left to select all the text you will often end up with your mouse over the outline widget. Releasing your mouse here will cause you to jump to a random page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1387298340,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-it6zs5tx5bzoz3374bjq,task_description,resolved
+VisualEditor: Outline widget in booklet layout responds to mouse up events even if they started elsewhere,Fixed by https://gerrit.wikimedia.org/r/#/c/133284/,1416325755,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-it6zs5tx5bzoz3374bjq,task_subcomment,NA
+VisualEditor: Links should do pre-annotations in both directions (not just down-page but also up-page),"When editing Wikipedia, I have repeatedly run into the following issue: 
+
+The article contains a link and I want to change the beginning of the link text (not the link's target), usually because it is upper case and I want it lower case. So I use VisualEditor to delete the first letter of the link and replace it with its lower case version. The result is unexpected: the first letter is not marked up as part of the link, but this is very hard to see.
+
+The source code is transformed from [[Link]] to l[[Link|ink]]. Links like the latter are almost never contained in human-created wikitext.
+
+Suggestion: link text should be ""magnetic"", so that changes at either end will automatically inherit the link markup.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1387231020,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-atsl3fekbsgfq2jon2lc,task_description,resolved
+VisualEditor: Links should do pre-annotations in both directions (not just down-page but also up-page),"With the new style of link editing, the problem I described above has gone away. So this can task can be closed.",1517159814,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-atsl3fekbsgfq2jon2lc,task_subcomment,NA
+VisualEditor: Links should do pre-annotations in both directions (not just down-page but also up-page),"@AxelBoldt, the style of link editing has been changed so that the whole link is highlighted.  This makes it easier to tell when you're addding something to the link.  Do you still think that this would be desirable?",1517094679,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-atsl3fekbsgfq2jon2lc,task_subcomment,NA
+Flow: support VisualEditor VE editing of header & topics (tracking),"VisualEditor is currently disabled as an editor in Flow:
+  $wgFlowEditorList = array( 'none' );  // EXPERIMENTAL prepend 'visualeditor'
+
+when we re-enable it, the VE bugs we discovered will probably still apply.
+
+The WMF core features team plans the ""VisualEditor integration"" story in  Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/28
+
+--------------------------
+**Version**: master
+**Severity**: minor",1386884340,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-whjfcbb2dp7dyl7hx24q,task_description,resolved
+Flow: support VisualEditor VE editing of header & topics (tracking),"**bingle-admin** wrote:
+
+The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/619, but people from the community are welcome to contribute here and in Gerrit.",1386884545,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-whjfcbb2dp7dyl7hx24q,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"After pasting a block of <syntaxhighlight> in to a target surface, I had to save and then reload the page before the syntax highlighting styling was applied. 
+
+https://www.mediawiki.org/w/index.php?title=User:TheDJ/sandbox&oldid=841358
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67515",1386843900,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_description,resolved
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"Change 311839 merged by jenkins-bot:
+VE: Ensure ext.pygments module gets loaded when a user adds a syntax highlight node
+
+[[https://gerrit.wikimedia.org/r/311839]]",1474412031,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"Change 311839 had a related patch set uploaded (by Alex Monk):
+VE: Ensure ext.pygments module gets loaded when a user adds a syntax highlight node
+
+[[https://gerrit.wikimedia.org/r/311839]]
+",1474410284,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,Still an issue.,1435184824,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"Change 214078 merged by jenkins-bot:
+Add VisualEditor support
+
+[[https://gerrit.wikimedia.org/r/214078]]",1435183387,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"Change 214078 had a related patch set uploaded (by Jforrester):
+Add VE support for syntax highlighting
+
+[[https://gerrit.wikimedia.org/r/214078]]
+",1432909767,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,related: https://gerrit.wikimedia.org/r/#/c/162123/,1417604677,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,"With the dependency fixed, this just needs VisualEditor loading the appropriate modules defined by SyntaxHighlight (one for each language) at appropriate times.",1399233172,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling,Confirmed.,1393530933,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-afyzlqcbgonyyb4d3b7e,task_subcomment,NA
+VisualEditor: Templated tables seem to fail in copy paste,"https://www.mediawiki.org/wiki/Manual:Code?veaction=edit
+
+Copy one of the tables there. You get an error in fixupInsertion
+
+[Error] TypeError: 'undefined' is not an object (evaluating 'source.clone')
+	copy (load.php, line 94)
+	getClonedElement (load.php, line 39)
+	fixupInsertion (load.php, line 120)
+	fixupInsertion (load.php, line 119)
+	newFromDocumentInsertion (load.php, line 71)
+	afterPaste (load.php, line 299)
+	(anonymous function) (load.php, line 294)
+	proxy (load.php, line 10)
+
+This does not seem related to bug 58318. The table also doesn't render as it should in the original surface, with slugs above and below it inside the table. Possibly caused by the usage of templates for row construction.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386843540,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-wus5sgrv22omy4zu47lx,task_description,resolved
+VisualEditor: Templated tables seem to fail in copy paste,Fixed by gerrit 140439.,1404172527,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wus5sgrv22omy4zu47lx,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted","I'm not sure if this was done on purpose, but when selecting text containing some formatting in some or all of the selected text (e.g. part of a link and some text after it, or part of a bolded string) the toolbar shows the ""Clear formatting"" button highlighted (similarly to how the ""Bold"" icon is highlighted when selecting bolded text).
+
+The toolbar is supposed to reflect current state of selected text. Showing the ""Clear formatting"" button already activated seems like an impossible state (it would theoretically mean some hypothetical ""clear"" annotation is applied to the selected text, which is incorrect. The only case in which that would technically be correct is if you apply text that is already cleared of formatting).
+
+This highlighting for the ""Clear formatting"" button is confusing from a UX point of view. I would associate it with how ""bold"" is highlighted when bolding is applied.
+
+When encountering this strange UX behaviour earlier today, it took me a while to figure out what it is supposed to mean (longer than it should for an intuitive editor). I don't think this is because I'm familiar with VisualEditor's previous state, but more in general.
+
+I think the correct approach would be to never highlight the clear formatting button in the toolbar, and have it be an ""apply"" button, you select text, and then activate (not deactivate) ""clear formatting"".
+
+This concept also exists in other popular editors.
+
+Alternatively, though that would be a new concept for people to learn, perhaps change the icon to something that means the opposite of no formatting, so that it being turned on for selected text, and being able deactivate it, like it currently does, actually makes sense as an action take.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386821400,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_description,resolved
+"VisualEditor: ""Clear formatting"" should never be highlighted",That bit is now fixed too AFAICT.,1402332266,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted","This now happens again. If you:
+
+1. Select an image
+2. Click Bold. This bolds the caption (this is a separate bug)
+3. Select something else, then select the image again (otherwise the clear formatting button doesn't get enabled)
+3. Click Clear Formatting.
+4. Observe that Clear Formatting is now depressed.
+
+Obviously there are lots of other weird things going on, but it seems that the only way that Clear Formatting button manages to not be depressed is by assuming that it will always successfully clear all formatting and therefore be disabled next.",1395274339,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted",This was done in the changes to the toolbar.,1390025219,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted","Created attachment 14069
+When using the link inspector, ""Link"" and ""Clear formatting"" are active
+
+**Attached**: {F12008}",1386821596,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+"VisualEditor: ""Clear formatting"" should never be highlighted","Created attachment 14068
+Selecting text spanning across a link shows ""Clear formatting"" active
+
+**Attached**: {F12007}",1386821531,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-v2h22jpv5cv6bvq6wozz,task_subcomment,NA
+Flow: Create a separate preference for the Visual Editor (opt-in/out) for Flow pages,"VisualEditor is currently not usable or well-tested in Flow. (Per feedback at http://ee-flow.wmflabs.org/w/index.php?title=Talk:Flow_bugs&workflow=050a7c69647ff00fc8b1fa163e68c4ac&action=view)
+
+Please create a separate preference (opt-in/out) for the VisualEditor within Flow pages, so that editors who are happily using/testing VE, will still be able to use Flow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386101640,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-yzw2lh4x4ig5iyfc2jnv,task_description,invalid
+Flow: Create a separate preference for the Visual Editor (opt-in/out) for Flow pages,Experimental VE has been pulled from Flow for awhile - should be revisited once we properly reimplement VE,1409847331,PHID-USER-kms5nmb5gvqzcdep3cnl,False,PHID-TASK-yzw2lh4x4ig5iyfc2jnv,task_subcomment,NA
+Flow: Create a separate preference for the Visual Editor (opt-in/out) for Flow pages,"**bingle-admin** wrote:
+
+The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/573, but people from the community are welcome to contribute here and in Gerrit.",1386102270,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yzw2lh4x4ig5iyfc2jnv,task_subcomment,NA
+VisualEditor: Add ability to edit local language links (non-Wikidata ones),"Though bug 52105 covers Wikidata-bourne language link editing, there are cases where local language link editing is still needed:
+
+* for Wikimedia wikis not (yet) hooked into Wikidata;
+* for Wikimedia wikis which cannot (yet) be hooked into Wikidata (e.g. [[en:Maggie Simpson]] vs. [[de:Die Simpsons (Familie)#Maggie Simpson]]); and 
+* for MediaWiki installs without a Wikibase server (almost all third party users).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52105",1386087840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l5om5dvvhar7j76c2fnz,task_description,open
+"Global, better URL to citation conversion functionality","**Author:** `vladjohn2013`
+
+**Description:**
+Global, better URL to citation conversion functionality
+
+Suppose, in Wikipedia, all that needed to be done to generate a perfect citation was to provide a URL? That would be a tremendous step toward getting a much higher percentage of text in Wikipedia articles to be supported by inline citations.
+
+There are already expanders (for the English Wikipedia, at least) that will convert an ISBN, DOI, or PMID, supplied by an editor, into a full, correct citation (footnote). These are in the process of being incorporated into the reference dialog of the VisualEditor extension, making it almost trivial (two clicks, paste, two clicks) to insert a reference.
+
+For web pages, however, the existing functionality seems to be limited to a Firefox add-on. Its limits, besides the obvious requirement to use that browser (and to install the add-on), include an inability to extract the author and date from even the most standard pages (e.g., New York Times), and the lack of integration with MediaWiki.
+
+For a similar approach, using a different plug-in/program, see this Wikipedia page about Zotero.
+
+A full URL-to-citation engine would use the existing Cite4Wiki (Firefox add-on) code, perhaps, plus (unless these exist elsewhere) source-specific parameter specifications. For example, the NYT uses ""<meta name=""author"" content=""NICK BILTON"" />"" for its author information; that format would be known by the engine (via a specifications database). Each Wikipedia community would be responsible for coding these (except for a small starter set, as examples), in the way that communities are responsible for TemplateData for the new VisualEditor extension.
+
+(Project idea suggested by John Broughton.)
+
+URL:https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Global.2C_better_URL_to_citation_conversion_functionality
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385913900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_description,resolved
+"Global, better URL to citation conversion functionality","Resolving, then. Check #Citoid for details.",1423649593,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality",This is being addressed by [[ https://www.mediawiki.org/wiki/Citoid | Citoid ]] ,1423614294,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","John- thank you for the links, they were very helpful!
+
+The project for an engine to provide citations to VE was approved for the May 2014 round for OPW. Extension is tentatively called https://www.mediawiki.org/wiki/Extension:CiteURLEngine although I'm not set on the name. 
+
+Since you mention NYTimes, they're proving to be quite problematic because they treat scrapers as logged out users (so scrapers get redirected to a log-in page), and they've also disallowed caching by Google so you can't use the cached page as a back-up solution. If anyone has any ideas let me know!",1398180001,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","Marielle - I'd be happy to work with you on nailing down the specs, and I'd also be happy to assist with QA (testing). If you do decide to create a bot to clean up naked urls in references/citations, I can also assist you with getting permission to run the bot at en.wikipedia.org (per [[WP:BOTREQ]]). 
+
+However, I can't offer technical assistance - it's been far too many years since I did programming, in languages that aren't particularly useful today.
+
+Finally, I note that the list of existing tools, at https://www.mediawiki.org/wiki/Improving_URL_citations_on_WikiMedia_(OPW_Project) , omits a significant number of things.  
+
+See https://en.wikipedia.org/wiki/Help:Citation_tools for a more comprehensive list, and also see https://en.wikipedia.org/wiki/Wikipedia:EIW#Citetools .",1394664371,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","Hi,
+
+This project was listed as a possible project for the FOSS Outreach Program for Women and I'd very much like to work on it.
+
+I've written a very rough proposal here: https://www.mediawiki.org/wiki/Improving_URL_citations_on_WikiMedia_(OPW_Project)
+
+However, I would need a mentor to help nail down the specs of the project and then oversee it. I don't to step on anyone's toes regarding the project Erik mentioned (a WMF web service to provide citations to both the visual editor and the wikitext editor)- it sounds like some of what I proposed might replicate that. I'd be happy to work on this from that angle as well but I'm not sure what other people have done already.
+
+Is there anyone on this thread that could mentor such a project? Thanks!
+
+-Marielle",1394553539,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","We are, in fact, investigating this in the context of VisualEditor, specifically the possibility of setting up a WMF web service for this that can be used by VisualEditor and wikitext editors alike to quickly generate citations. It'd be ideal to be able to share code with Zotero which has a comprehensive suite of URL-to-citation translators already.",1387360625,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"Global, better URL to citation conversion functionality","**vladjohn2013** wrote:
+
+This proposal has been listed at https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects and we are filing a report to gather community feedback and share updates.",1385913933,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-i47lj2e2ftd5tvqh5r7r,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","Intention:
+Add a category to a page
+
+Steps to Reproduce:
+1. Open the page in VisualEditor and choose the categories tool.
+2. Type the full name of the category, including the namespace:  Category:Example
+
+
+Actual Results:  
+VisualEditor adds a non-existent, malformed category named [[Category:Category:Example]].
+
+Expected Results:  
+That VisualEditor would recognize that ""Category:Example"" already contained the namespace, and thus omit the duplication.  Ideally, at non-English wikis, it would recognize and remove both the local name for the namespace and the English name, since both are typically valid (e.g., strip out both ""Kategorie"" and ""Category"" at the German Wikipedia).
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385856300,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-f7abfvzj2vf4lqry7phg,task_description,open
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","Also there's the problem of either (a) only doing this hack for English, or (b) having to hold in VE a copy of all of the translations of Category:, and know which one to remove when (removing Catégorie: on French, but not on English, and so on).",1386361041,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","(In reply to comment #4)
+> Do any [[Category:Category:Foo]] pages exist?  I haven't seen one.
+
+On all ten million MediaWiki wikis out there? Quite probably…
+
+J.",1386360951,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in",Do any [[Category:Category:Foo]] pages exist?  I haven't seen one.,1386359880,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","There is [[Category:Category theory]], it might be worth checking as a corner case.",1386285245,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","What to do when there's a category called ""Category:Foo"" and another called ""Foo"". Do we strip or not?",1386041139,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+"VisualEditor:  The category tool should automatically strip the namespace ""Category:"" out of the cat name, if the editor types it in","[new feature or ""nice-to-have"" => severity=enhancement]",1385979158,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-f7abfvzj2vf4lqry7phg,task_subcomment,NA
+VisualEditor:  Wikitext warning needs to be updated to refer to switching to wikitext editor without losing unsaved changes,"Intention:
+The wikitext warning says:
+
+""Click ""Edit source"" to edit the page in wikitext mode – unsaved changes will be lost.""
+
+This need to be changed to reference the new ability to switch to the source editor without losing unsaved changes, at least (currently) for non-Firefox users.
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57699",1385604180,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-3pikq7qftwx2jwebgh76,task_description,resolved
+VisualEditor:  Wikitext warning needs to be updated to refer to switching to wikitext editor without losing unsaved changes,"Change 133637 merged by jenkins-bot:
+Update wikitext-warning to refer to 'Switch to source editing'
+
+https://gerrit.wikimedia.org/r/133637",1400523894,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3pikq7qftwx2jwebgh76,task_subcomment,NA
+VisualEditor:  Wikitext warning needs to be updated to refer to switching to wikitext editor without losing unsaved changes,I uploaded Gerrit change 133637 for this,1400200917,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-3pikq7qftwx2jwebgh76,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"Intention:
+When you open VisualEditor for the first time, you get a message that says you can switch to wikitext, but that unsaved changes will be lost:
+
+""You can keep using the wikitext editor by clicking the ""Edit source"" tab instead – unsaved changes will be lost.""
+
+This is not always true, since (currently for non-Firefox users) it is possible to switch to wikitext using the new menu item without losing any changes.
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57462
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57700",1385604120,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ookmj2wjll2ptshhb67g,task_description,resolved
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"Change 133639 merged by jenkins-bot:
+Update beta warning to refer to 'Switch to source editing'
+
+https://gerrit.wikimedia.org/r/133639",1400523863,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,I uploaded Gerrit change 133639 for this,1400200902,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,The switch option appears to be currently working for IPs as well.,1399462468,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"(Actually, it's still broken for IPs.)",1393936033,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"(BTW the switch option is now working with any browser AFAIK, or at least it is with FF.)",1389085568,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost,"Any message of the interface can be changed locally in the MediaWiki namespace, so anybody can fix that. But the message only refers to the Edit source main tab, so it is always true that if you click that your changes will be lost.",1389085230,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-ookmj2wjll2ptshhb67g,task_subcomment,NA
+VisualEditor: Features not yet available in a certain browser (but working in others) should be grayed out/unselectable,"Pretty much what the title says.
+James thinks this might eventually be done at some point, so this is a reminder.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385499300,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-25ulackf33wigk7bvnyg,task_description,invalid
+VisualEditor: Make jquery.byteLimit more user friendly and cleaner in usage,"Currently:
+
+* byteLimit() will internally do all kinds of event binding to get notice of changes.
+* We have our own 'change' callback for InputWidget elements.
+* in mw.ViewPageTarget we use our 'change' event, our own getValue, manually run it through byteLength (not byteLimit), in order to get the current length that we assume byteLimit got to as well.
+* When the length is exceeded by user input, byteLImit internally will start chopping off characters (or rather, cancel user events after it hit the limit, and falls back to chopping off characters until it fits again).
+
+Problems:
+* Mimics the change event.
+* Duplicates logic for byteLength outside byteLimit, this will fail if the logic changes, and already fails if the byteLimit has a filter callback.
+
+Ideally: byteLimit (standalone)
+* Its own on('change') - so we don't have to mimic it
+* Ability to retrieve byte length as perceived by byteLimit - so we don't have to reverse engineer it
+* Option to disable the chopping off (instead, more like Twitter where the underlying user interface element will allow new characters, but it will have an event like 'length-exceeded' and 'length-satisfied' or 'length-recovered' so we dan display a nicer user interface (e.g. make the number negative and red)
+
+
+or:
+
+Ideally: byteLimit (utility mixin)
+* Option to feed it change events instead of having it listen on its own.
+* Get back from each event – the current state (length exceeded or not, and what the length is, having taken the filter in account).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385472600,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cptw6scnn4zompkjhwyq,task_description,declined
+VisualEditor: Make jquery.byteLimit more user friendly and cleaner in usage,"Code has improved since then and is now more abstract and re-usable, which VE already makes use of in ve.ui.MWSaveDialog.
+
+Re-use of the additional abstraction layer ""byteLimit""  on top of ""byteLength"" no longer makes sense as it seems undesirable from a UX perspective to artificially limit how much one can type. Rather, VE allows the user to type more while drafting the edit summary and then shows visually when the limit is exceeded and disallows submission until fixed.
+
+This is much better than hard limiting the size of the input field which makes editing of the edit summary much harder due to not having any wiggle room to move things around or copy/pasting etc to tune it.",1554174106,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cptw6scnn4zompkjhwyq,task_subcomment,NA
+VisualEditor: Fire a hook before the page is saved,"Some Wikipedias have hooks for the source editor that process the wikitext before it is saved. The only thing to currently do this for the Visual Editor seems to be to hook in the 'wikipage.content' event and do an API edit that processes the text as intended.
+
+Instead, the visual editor should offer a different event, such as visualeditor.beforesave, that would allow such processing to take place when saving the content.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385385360,PHID-USER-2trxtywh5ma4onasf4kq,False,PHID-TASK-dakuttxcpl6bkvpemnmx,task_description,declined
+VisualEditor: Fire a hook before the page is saved,"Re-evaluating – if you want a client-side hook, this is a WONTFIX (both for specific reasons to this bug to do with catastrophic performance hits, and also because events are not a sane way to go).
+
+If you want a VE-specific server-side (PHP) hook on wikitext save, we could do that more reasonably (as MediaWiki's too far down that road to pull back).",1397675923,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dakuttxcpl6bkvpemnmx,task_subcomment,NA
+VisualEditor: Fire a hook before the page is saved,"Ideally, there would be an event for each of these stages :) 
+
+Realistically, in order to reuse existing code, the best time would probably be when the Wikitext is ready to be saved (since that would be the equivalent for pressing the ""Save"" button). Of course, the callback needs to be able to give the modified wikitext back to VE.",1385395263,PHID-USER-2trxtywh5ma4onasf4kq,False,PHID-TASK-dakuttxcpl6bkvpemnmx,task_subcomment,NA
+VisualEditor: Fire a hook before the page is saved,"What stage of the save do you want? 
+
+* HTML is ready to be saved
+* HTML is converted to wikitext
+* Wikitext is back from Parsoid and is ready to be saved
+* VE just sent the wikitext to MW API
+* VE just got the confirmation token back from MW API
+* …",1385394655,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dakuttxcpl6bkvpemnmx,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","When a user clicks on Switch to source editing option from the settings drop down it tells user that switching to source editing will keep the changes made in the document.But if a user attempts to switch from the tab it does not retain those changes.This seemed confusing to me because when user uses the ""switch to source editing"" , the ""Edit Source"" tab is selected ,indicating the same destination for both action.
+
+If a user can switch to source editing in multiple ways, i think it is better both ways have similar mechanism of handling the changes to have uniform experience.
+Specially when switching from tab is one click away compared to the ""[]switch to source editing"" option.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57699
+https://bugzilla.wikimedia.org/show_bug.cgi?id=42141",1385165520,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_description,resolved
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab",Verified the fix in production,1405028027,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab",Verified the fix in test2,1404769383,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab",Verified the fix in Betalabs,1404243442,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Change 143203 merged by jenkins-bot:
+Don't offer to retain changes when switching to wikitext editor by tab if no changes have been made
+
+https://gerrit.wikimedia.org/r/143203",1404176682,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Change 143203 had a related patch set uploaded by Alex Monk:
+Don't offer to retain changes when switching to wikitext editor by tab if no changes have been made.
+
+https://gerrit.wikimedia.org/r/143203",1404172800,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Change 142064 merged by jenkins-bot:
+Offer to retain changes when switching to the wikitext editor
+
+https://gerrit.wikimedia.org/r/142064",1404171633,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Change 142064 had a related patch set uploaded by Alex Monk:
+Offer to retain changes when switching to the wikitext editor
+
+https://gerrit.wikimedia.org/r/142064",1403727961,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab",I personally think that this bug report is a duplicate of bug 42141.,1391403189,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","This is possible, but would be ugly, because we'd need to replace the existing two-choice option (switch or don't switch) with a custom three-choice one (switch and keep changes, switch without changes, don't switch)… Maybe.",1385394909,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","[Removing ""[Suggestion]"" from summary; setting severity field to ""enhancement"" instead]",1385226568,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: Offer to retain changes when switching to the ""Edit Source"" tab","Created attachment 13890
+Inside Edit Source tab
+
+**Attached**: {F12699}",1385165849,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-rwqvw5qcvrnogk334awp,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Repro:
+
+1. Create a page with text below:
+
+<math>
+\begin{matrix}
+x & y \\
+z & v
+\end{matrix}
+</math>
+
+2. Default rendering, in PHP parser and Parsoid (VE initial state):
+
+x y
+z v
+
+3. VE edit this matrix, change v to uv.
+
+4. Edited block becomes:
+
+x amp; y
+z amp; uv
+
+(After saving it works fine)
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54577",1385141220,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_description,resolved
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)",Thanks Bartosz!,1405470041,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Should be fixed.
+
+Like in wikitext, it will now be impossible to input '</tag>' in the inspector in VisualEditor: it will be converted to '&lt;/tag>' when the inspector is closed.",1405463766,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Change 144158 merged by jenkins-bot:
+ve.ce.MWExtensionNode: Don't escape content of wikitext tags on preview
+
+https://gerrit.wikimedia.org/r/144158",1405462152,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Change 144157 merged by jenkins-bot:
+ve.ui.MWExtensionInspector: Prevent from setting impossible content
+
+https://gerrit.wikimedia.org/r/144157",1405462148,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Change 144158 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ce.MWExtensionNode: Don't escape content of wikitext tags on preview
+
+https://gerrit.wikimedia.org/r/144158",1404490445,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Change 144157 had a related patch set uploaded by Bartosz Dziewoński:
+ve.ui.MWExtensionInspector: Prevent from setting impossible content
+
+https://gerrit.wikimedia.org/r/144157",1404490440,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Just for ""fun"", some informative examples that show what happens when you try too hard with {{#tag:}}. Two of these actually cause UNIQ markers to appear in output, which is rather bad in general. The behavior may differ depending on the tag used.
+
+
+<syntaxhighlight lang=php>$a;</syntaxhighlight>
+
+<syntaxhighlight lang=php></syntaxhighlight></syntaxhighlight>
+
+<syntaxhighlight lang=php>&lt;/syntaxhighlight></syntaxhighlight>
+
+{{#tag:syntaxhighlight|</syntaxhighlight>|lang=php}}
+
+<syntaxhighlight lang=php><syntaxhighlight lang=php>$a;</syntaxhighlight></syntaxhighlight>
+
+{{#tag:syntaxhighlight|<syntaxhighlight lang=php>$a;</syntaxhighlight>|lang=php}}
+
+{{#tag:syntaxhighlight|&lt;syntaxhighlight lang=php>$a;</syntaxhighlight>|lang=php}}
+
+{{#tag:syntaxhighlight|<nowiki><syntaxhighlight lang=php>$a;</syntaxhighlight></nowiki>|lang=php}}",1404487657,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","Basically, ve.ce.MWExtensionNode.prototype.generateContents builds an XML element object for given tag name (for example 'math'), given attributes (none in this case) and given contents (for example 'a < b'), and then serializes it to a string to ensure that everything is correctly escaped.
+
+The problem is that MediaWiki XML-like tags don't expect their contents to be escaped. Serializing such a node generates ""<math>a &lt; b</math>"", while wikitext expects ""<math>a < b</math>"".
+
+(An interesting corollary is that a MediaWiki XML-like tag 'foo' may not contain the string '</foo>' in any form nor encoded in any way, unless the code of the extension handling the tag specifically parses nested <nowiki/> tags or something. You can cheat – {{#tag:foo|</foo>}} – but then you still can't include the string '<foo></foo>' because it gets double-parsed.)
+
+(Fun fact: the above behavior is the reason why <source/> was renamed to <syntaxhighlight/> some years ago.)
+
+We should not escape the contents at all and instead do something clever if the input text contains '</foo>'. VE and wikitext are both designed to never disallow the user from doing stupid things, so I'm not sure what can be done if we don't just prevent the user from saving that. Maybe selectively HTML-escape /<\/\s*foo\s*>/ when closing the inspector?",1404487482,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)",*** Bug 60332 has been marked as a duplicate of this bug. ***,1404486826,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)","This problem is actually common for everything that uses MWExtensionNode. The problem is that ve.ce.MWExtensionNode.prototype.generateContents makes some bold assumptions about wikitext syntax that are not true.
+
+The fix from bug 54577 didn't actually fix much, it just changed what the problem is.",1404486795,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+"VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)",*** Bug 60113 has been marked as a duplicate of this bug. ***,1404431099,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pvooclgjtrwgebkle3fj,task_subcomment,NA
+VisualEditor: <visualeditor-dialog-beta-welcome-content> does not mention new switch to wikicode feature,"**Author:** `raincity471`
+
+**Description:**
+Reproducible: Didn't try
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1385125920,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ccqdyfu36me32igrajec,task_description,declined
+VisualEditor: <visualeditor-dialog-beta-welcome-content> does not mention new switch to wikicode feature,"I'm not sure it's worth trying to explain this minor and not-hugely-useful feature. I think it would just add to the confusion.
+
+Remember that this is the first ever interface users will see when using VisualEditor – it's important that we don't over-load them with too much information, or that we drown out the important information for them to learn by hiding it amongst a sea of less-important and un-important information.
+
+WONTFIXing.",1385136050,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ccqdyfu36me32igrajec,task_subcomment,NA
+VisualEditor: <visualeditor-dialog-beta-welcome-content> does not mention new switch to wikicode feature,"**raincity471** wrote:
+
+Screenshot of the intro screen with affected sentence highlighted
+
+Outdated sentence circled in red.
+Screenshot saved ‎22 ‎November ‎2013, ‏‎13:37:15 (UTC) after a bit of editing in the GIMP. VE beta 0.1.0 running MediaWiki 1.23wmf4 (c066033), Firefox 25.0 in private mode (so no copyright problems with addons).
+Firefox 25 is licensed under the Mozilla Public License 2.0. VisualEditor is licensed under the Massachusetts Institute of Technology license. MediaWiki is licensed under the GNU GPL version 2 or later.
+
+**Attached**: {F12597}",1385128202,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ccqdyfu36me32igrajec,task_subcomment,NA
+VisualEditor: <visualeditor-dialog-beta-welcome-content> does not mention new switch to wikicode feature,"**raincity471** wrote:
+
+A new feature has been added to VisualEditor which allows editors to switch from VE to wikitext editing without losing their changes (see Bug 50687). The VE intro dialogue (shown to users the first time they open VE) still says you may switch from VE to ""edit source"" using the tab at the top and that changes will be lost. The new feature should be mentioned, maybe something like:
+
+""You can keep using the wikitext editor by clicking the options button (three horizontal lines next to the cancel button) in the top-right corner and then ""switch to source editing"". Unsaved changes will not be lost.""",1385126471,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ccqdyfu36me32igrajec,task_subcomment,NA
+VisualEditor: Adjacent floating tables are offset by vertical space because of intervening <span>,"Reproducible: Always
+
+Fram reports that when you try to VEdit pages like
+https://en.wikipedia.org/wiki/List_of_top_100_Major_League_Baseball_strikeout_pitchers
+https://en.wikipedia.org/wiki/List_of_Major_League_Baseball_players_with_2,500_games_played
+or https://en.wikipedia.org/wiki/List_of_top_300_Major_League_Baseball_home_run_hitters ,
+what you get is not exactly what you saw :) (see the tables and the following sections.)
+
+Ssastry furtherly diagnosticated: ""Looks like some VE-clientside rendering issues with empty spans between multiple floating tables.""
+Doesn't look specific to a browser or skin.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65249",1385068980,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-upqk35oo5h6sa55ff7w5,task_description,duplicate
+Enable VisualEditor on svwiktionary,"We would like to have VisualEditor enabled on some part of svwiktionary.
+
+Suggested namespace: User namespace.
+
+Rationale:
+
+We're doing a proof-reading project[1] where we'll need to do lots of style edits (mainly update italics and bold).
+
+The idea is to extract useful information from the dictionary/thesaurus ""Ord för ord""[2] and create new entries and improve existing ones using the information.
+
+
+[1] https://sv.wiktionary.org/wiki/Wiktionary:Projekt/Ord_f%C3%B6r_ord
+[2] http://runeberg.org/ordforord/
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1385045940,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_description,resolved
+Enable VisualEditor on svwiktionary,This should now be fixed; sorry for the mis-configuration.,1386126509,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Change 98871 merged by jenkins-bot:
+Disable VisualEditor in content namespaces on svwiktionary
+
+https://gerrit.wikimedia.org/r/98871",1386116304,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Change 98871 had a related patch set uploaded by Jforrester:
+Disable VisualEditor in content namespaces on svwiktionary
+
+https://gerrit.wikimedia.org/r/98871",1386102272,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"(In reply to comment #9)
+> I noticed that it's enabled in the main namespace too, but that doesn't make
+> sense. We use lots of templates and very well-defined lists that just don't
+> work well with VisualEditor.
+> 
+> Can you please disable it for the main namespace?
+
+Hmm, that's odd; it's configured for just the User namespace, per this bug – will investigate why it's working elsewhere too.
+
+> If possible, you could enable it for the project namespace instead (but not
+> on pages with __NEWSECTIONLINK__).
+
+Not sanely possible - we don't enable VisualEditor on pages which are signed, as that's what Flow is for, and too much of the project namespace is randomly signed (even with an expensive check for __NEWSECTIONLINK__), sorry. :-(",1386087168,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"I noticed that it's enabled in the main namespace too, but that doesn't make sense. We use lots of templates and very well-defined lists that just don't work well with VisualEditor.
+
+Can you please disable it for the main namespace?
+
+If possible, you could enable it for the project namespace instead (but not on pages with __NEWSECTIONLINK__).",1386081623,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"This is now live - you can opt in to test VisualEditor using the Beta Features link in your personal tools at the top of the page, or through the Preferences link in the ""Beta Features"" tab.
+
+If there are any issues, please shout!",1386022164,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Change 97711 merged by jenkins-bot:
+Enable VisualEditor as opt-in on svwiktionary
+
+https://gerrit.wikimedia.org/r/97711",1386021544,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Change 97711 had a related patch set uploaded by Jforrester:
+Enable VisualEditor as opt-in on svwikitionary
+
+https://gerrit.wikimedia.org/r/97711",1385463709,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Sorry for the slow reply – we can do this if wanted.
+
+Just user namespace is entirely possible if that's what you want.
+
+Will do a patch now.",1385463048,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,I was just providing info about what's written in public; James and the VE development team has the final word and is free to change plans. :),1385462658,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"I was thinking that it might be possible to enable it on svwiktionary earlier, since I thought it would be low-risk to enable it for the user namespace only, not adding any new requirements.
+
+Anyway, I take that as a ""no"" in the short-term (this year).",1385402559,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"https://www.mediawiki.org/wiki/VisualEditor#Timeline says ""VisualEditor may be offered to users at non-Wikipedia projects, such as Commons or Wiktionary, after deployment to the Wikipedias has completed. No timeline has been set for this.""",1385396895,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+Enable VisualEditor on svwiktionary,"Thank you for your interest in Visual Editor.
+
+[ Adding James Forrester and Trevor Pascal as CC to get feedback on this matter. ]",1385062535,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-xiyv4jixkvbxe2phirwu,task_subcomment,NA
+VisualEditor: Long links are not shown in full in the link searcher,"When a long string (24 characters or more) gets added in the link tool (a typical long URL, or a just a long article title), the external and internal link options get shortened with ""..."" in the middle. This can make it hard to know whether you put in the right string or not, and there doesn't seem to be much downside to displaying the full link targets for at least moderately longer strings.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69574",1384795860,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-7fbhbqnohmq5xaiuz462,task_description,open
+VisualEditor: Long links are not shown in full in the link searcher,"(In reply to comment #0)
+> When a long string (24 characters or more) gets added in the link tool (a
+> typical long URL, or a just a long article title), the external and internal
+> link options get shortened with ""..."" in the middle. This can make it hard to
+> know whether you put in the right string or not, and there doesn't seem to be
+> much downside to displaying the full link targets for at least moderately
+> longer strings.
+
+The downside is that the link needs to fit on the screen for the user to read it. :-)
+
+I'm not happy with the idea of a hugely-wide search results pane masking much of the screen unnecessarily, but I also think that expanding and contracting as needed could be a bit of an eyesore…",1384844593,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7fbhbqnohmq5xaiuz462,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"On this page [1], the ""Open questions"" section ends with a line that has starts with <s> but later has another <s> instead of </s>. The strikethrough ends with the second tag anyway, when the page is being viewed normally. With VisualEditor, however, the strikethrough formatting continues to the end of the page.
+
+[1] = https://www.mediawiki.org/w/index.php?title=Wikipedia_Education_Program&oldid=821826
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1384790520,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-rg7ifjxavegjy63g4nhz,task_description,declined
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"Tidy is going away and RemexHTML will be used on all wikis sometime mid next year. In that context, all these pages will look broken in RemexHTML as well and the relevant broken markup on these pages has to be fixed. We have added [[https://www.mediawiki.org/wiki/Help:Extension:Linter/multiple-unclosed-formatting-tags|a special linter category to aid that effort. ]]",1513635570,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"(Tracking bug for Tidy being a piece of junk is bug 2542, by the way.)",1396786527,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"This comment is basically a +1/me too. The same issue exhibits on https://en.wikipedia.org/w/index.php?title=Actor_model&oldid=602988700 but with a <tt> rather than a <s>. After some discussion with thedj on IRC he suggested I'd file here anyway, if only to indicate it might be somewhat prevalent in the wild.
+
+Personally, I think this is a bug in tidy rather than in VE, and the most reasonable behaviour would be for tidy to conform to prevalent browser behaviour/the HTML spec, and to emit a warning about the likely location of the breakage (where tidy now closes the element)",1396785653,PHID-USER-n27daagbl3wqf3ghr4nk,False,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"This is a difference between tidy used by MediaWiki in production and the HTML5 spec. Tidy closes unclosed formatting elements eagerly, while the HTML5 spec demands that formatting elements are restored in most cases.
+
+We are considering to prevent formatting elements from bleeding out of transclusions (see bug 50536) for reasons of correctness and performance, but so far we don't have plans to generally move away from HTML5-compliant (and MediaWiki without tidy) behavior for this.
+
+We can detect unclosed tags and provide information for fix-ups in the wikitext though. That is partly tracked in bug 50547. I thought that we had another bug for this, but don't currently find it. Will add a link to bug 50547 when I find it.",1386120327,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+Unclosed strikethrough tag makes strikethrough formatting continue throughout page,"Also, when I removed the entire section that included the offending strikethrough tags, the VE still showed strikethrough on the remainder of the page.
+
+When I open it again in VE after the edit [1], it appears as expected.
+
+[1] = https://www.mediawiki.org/w/index.php?title=Wikipedia_Education_Program&diff=821838&oldid=821826",1384790892,PHID-USER-nyv6rqxnzdy3oe323a3d,False,PHID-TASK-rg7ifjxavegjy63g4nhz,task_subcomment,NA
+VisualEditor: Allow users to set/edit __STATICREDIRECT__ status in the page metadata panel,"Checkbox flag, redirect pages only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7cbywnlba7fvo6mhudvs,task_description,resolved
+VisualEditor: Allow users to set/edit __STATICREDIRECT__ status in the page metadata panel,Verified the fix in test2,1393021669,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-7cbywnlba7fvo6mhudvs,task_subcomment,NA
+VisualEditor: Allow users to set/edit __STATICREDIRECT__ status in the page metadata panel,"Change 95213 merged by jenkins-bot:
+Let users set #REDIRECT and __STATICREDIRECT__ status
+
+https://gerrit.wikimedia.org/r/95213",1392349581,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7cbywnlba7fvo6mhudvs,task_subcomment,NA
+VisualEditor: Allow users to set/edit __STATICREDIRECT__ status in the page metadata panel,"Change 95213 had a related patch set uploaded by Jforrester:
+Let users set #REDIRECT and __STATICREDIRECT__ status
+
+https://gerrit.wikimedia.org/r/95213",1384754847,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7cbywnlba7fvo6mhudvs,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTITLECONVERT__ (and __NOTC__) status in the page metadata panel,"Checkbox flag, pages on variant wikis only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754580,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qu2aqxrmqddq2le4yre5,task_description,resolved
+VisualEditor: Allow users to set/edit __NOTITLECONVERT__ (and __NOTC__) status in the page metadata panel,"Change 126015 merged by jenkins-bot:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1398123277,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qu2aqxrmqddq2le4yre5,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTITLECONVERT__ (and __NOTC__) status in the page metadata panel,"Change 126015 had a related patch set uploaded by Alex Monk:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1397579976,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qu2aqxrmqddq2le4yre5,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOTITLECONVERT__ (and __NOTC__) status in the page metadata panel,"Change 95726 had a related patch set uploaded by Jforrester:
+[WIP] Create remaining meta items in DM
+
+https://gerrit.wikimedia.org/r/95726",1384754699,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qu2aqxrmqddq2le4yre5,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOCONTENTCONVERT__ (and __NOCC__) status in the page metadata panel,"Checkbox flag, pages on variant wikis only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754580,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ckkuvwdfjtbnqb4u7jpk,task_description,resolved
+VisualEditor: Allow users to set/edit __NOCONTENTCONVERT__ (and __NOCC__) status in the page metadata panel,"Change 126015 merged by jenkins-bot:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1398123274,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ckkuvwdfjtbnqb4u7jpk,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOCONTENTCONVERT__ (and __NOCC__) status in the page metadata panel,"Change 126015 had a related patch set uploaded by Alex Monk:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1397579981,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ckkuvwdfjtbnqb4u7jpk,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOCONTENTCONVERT__ (and __NOCC__) status in the page metadata panel,"Change 95726 had a related patch set uploaded by Jforrester:
+[WIP] Create remaining meta items in DM
+
+https://gerrit.wikimedia.org/r/95726",1384754703,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ckkuvwdfjtbnqb4u7jpk,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOGALLERY__ status in the page metadata panel,"Checkbox flag, category namespace only.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754520,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zwu3t35ebtuycwppeq65,task_description,resolved
+VisualEditor: Allow users to set/edit __NOGALLERY__ status in the page metadata panel,"Change 126015 merged by jenkins-bot:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1398123269,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zwu3t35ebtuycwppeq65,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOGALLERY__ status in the page metadata panel,"Change 126015 had a related patch set uploaded by Alex Monk:
+Add checkboxes to set some metadata on page metadata panel
+
+https://gerrit.wikimedia.org/r/126015",1397579990,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zwu3t35ebtuycwppeq65,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOGALLERY__ status in the page metadata panel,"Change 95726 had a related patch set uploaded by Jforrester:
+[WIP] Create remaining meta items in DM
+
+https://gerrit.wikimedia.org/r/95726",1384754694,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-zwu3t35ebtuycwppeq65,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,"Trinary state (default, NEWEDITSECTION, NONEWEDITSECTION), all pages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2jvygydrgf5vwtxvhwak,task_description,resolved
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,Verified the fix in test2,1393021067,PHID-USER-24djtv3gj5gua2y6u2g5,True,PHID-TASK-2jvygydrgf5vwtxvhwak,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,"Change 95725 merged by jenkins-bot:
+Let users set __NEWEDITSECTION__ & __NONEWEDITSECTION__ status
+
+https://gerrit.wikimedia.org/r/95725",1392866615,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2jvygydrgf5vwtxvhwak,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,"Change 95725 had a related patch set uploaded by Jforrester:
+Let users set __NEWEDITSECTION__ & __NONEWEDITSECTION__ status
+
+https://gerrit.wikimedia.org/r/95725",1392350212,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2jvygydrgf5vwtxvhwak,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel,"Change 95725 had a related patch set uploaded by Jforrester:
+Let users set __NEWEDITSECTION__ & __NONEWEDITSECTION__ status
+
+https://gerrit.wikimedia.org/r/95725",1384754373,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2jvygydrgf5vwtxvhwak,task_subcomment,NA
+VisualEditor: Allow users to set/edit __INDEX__ and __NOINDEX__ status in the page metadata panel,"Trinary state (default, INDEX, NOINDEX), all pages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-knrygben5z6uuprlfcd4,task_description,resolved
+VisualEditor: Allow users to set/edit __INDEX__ and __NOINDEX__ status in the page metadata panel,"Change 95724 merged by jenkins-bot:
+Let users set __NOINDEX__ & __INDEX__ status
+
+https://gerrit.wikimedia.org/r/95724",1392861031,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-knrygben5z6uuprlfcd4,task_subcomment,NA
+VisualEditor: Allow users to set/edit __INDEX__ and __NOINDEX__ status in the page metadata panel,"Change 95724 had a related patch set uploaded by Jforrester:
+Let users set __NOINDEX__ & __INDEX__ status
+
+https://gerrit.wikimedia.org/r/95724",1392350168,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-knrygben5z6uuprlfcd4,task_subcomment,NA
+VisualEditor: Allow users to set/edit __INDEX__ and __NOINDEX__ status in the page metadata panel,"Change 95724 had a related patch set uploaded by Jforrester:
+Let users set __NOINDEX__ & __INDEX__ status
+
+https://gerrit.wikimedia.org/r/95724",1384754285,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-knrygben5z6uuprlfcd4,task_subcomment,NA
+VisualEditor: Allow users to set/edit __NOEDITSECTION__ status in the page metadata panel,"Checkbox flag on/off, all pages.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384754160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cvzyzrek2t2cvehwvzle,task_description,resolved
+VisualEditor: Allow users to set/edit __NOEDITSECTION__ status in the page metadata panel,"Change 95723 had a related patch set uploaded by Jforrester:
+Let users set __NOEDITSECTION__ status
+
+https://gerrit.wikimedia.org/r/95723",1384754197,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-cvzyzrek2t2cvehwvzle,task_subcomment,NA
+Image searched for does not come back in results but does exist on server,"**Author:** `anjana1`
+
+**Description:**
+OS: Win 8
+Browser: Fire Fox 24 and Chrome 31.0
+
+Not able to insert an image in VE mode on Beta. The image (A nice pic.jpg) which is on commons is not seen in the list while trying to upload it using the ""Media"" in the toolbar (found in ""More"" pulldown menu)in ""Edit Beta mode"".
+
+The same image is uploadable using wikitext syntax [[File:A Nice pic.jpg]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**Whiteboard**: cirrus-fixed",1384575840,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k62fxro4rxguo7ka2mon,task_description,declined
+Image searched for does not come back in results but does exist on server,This is fixed in Cirrus as far as I know. Inclined to WONTFIX for lsearchd as a result.,1398881638,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-k62fxro4rxguo7ka2mon,task_subcomment,NA
+Image searched for does not come back in results but does exist on server,"Re-titling this and putting back into the Wikimedia / Search area, as that's where the issue lies; I believe that the new search system fixes this issue, but will leave it for the experts to opine.",1393039167,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k62fxro4rxguo7ka2mon,task_subcomment,NA
+Image searched for does not come back in results but does exist on server,"**anjana1** wrote:
+
+Steps to reproduce:
+
+Pre-requisites: Create an account in http://en.wikipedia.beta.wmflabs.org
+
+1. Login with username and password into http://en.wikipedia.beta.wmflabs.org/wiki/User:<username>
+2. On the topmost right-hand side of the page, click on ""preferences""
+3. Click on the ""Beta Features"" tab and select ""VisualEditor""
+4. Click on ""Save"" at the end of the page. You must see a message saying ""Your preferences have been changed"".
+5. Click on <your username>. Your username will be found on the topmost right-hand side of the page.
+6. Click on ""Edit beta"" , found on the top right-hand side next to ""Edit Source"".
+7. On the toolbar, click on ""More"" pull-down menu and click on ""Media""
+8. Search for ""A nice picture.jpg"". [Here, we are looking for an image of ""cave 26,ajanta caves""]
+9. The intended image is not found.
+
+
+But, this can be found with wikitext i.e, without VisualEditor.
+1. Click on ""Edit Source""
+2. Type [[File:A nice picture.jpg]] on the page.
+3. Click on ""Save Page"" tab at the bottom of the page.
+4. Result: You will be able to see the intended image.",1384793674,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-k62fxro4rxguo7ka2mon,task_subcomment,NA
+Image searched for does not come back in results but does exist on server,"Thanks for taking the time to report this!
+
+Could you please provide exact steps, click by click, to reproduce the problem, so anybody else could follow these steps and get the same results?",1384692376,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-k62fxro4rxguo7ka2mon,task_subcomment,NA
+"VisualEditor: External links that point to the local wiki should be changed into internal links, not interwikis","Reported by Mattho69 on frwiki [1].
+
+If I try to add a link to a Wikipedia article using its full form (http://fr.wikipedia/org/wiki/…), it is saved as an interwiki (see [2]) instead of a local wikilink. 
+
+I notice that it only happens with HTTP links, not with HTTPS ones (see [3]), which are not converted (maybe separate bug ?).
+
+[1] https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis#:fr:
+[2] https://fr.wikipedia.org/w/index.php?title=Utilisateur:Ltrlg/tests&diff=98243431&oldid=98197987
+[3] https://fr.wikipedia.org/w/index.php?title=Utilisateur:Ltrlg/tests&diff=98243523&oldid=98243431
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45209
+https://bugzilla.wikimedia.org/show_bug.cgi?id=61672",1384363680,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-jb2rslshvyhiqokerp5m,task_description,resolved
+"VisualEditor: External links that point to the local wiki should be changed into internal links, not interwikis","
+
+*** This bug has been marked as a duplicate of bug 42986 ***",1397764105,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jb2rslshvyhiqokerp5m,task_subcomment,NA
+"VisualEditor: Improve message for parameters that have no TemplateData (say ""undocumented"" instead of ""unknown"")","When adding parameters of some templates like this:
+https://cs.wikipedia.org/wiki/%C5%A0ablona:Citace_elektronick%C3%A9_monografie
+ it sais ""unknown parametr"" even the parametr is valid and works afterwords. 
+
+This information is confusing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1384164360,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-he2d3umv5r6rhdzphakm,task_description,open
+"VisualEditor: Improve message for parameters that have no TemplateData (say ""undocumented"" instead of ""unknown"")","There are very many templates where the TemplateData description is incomplete and some parameters are just not documented. Some better description than unknown would be good - perhaphs ""undocumented"".",1519683820,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-he2d3umv5r6rhdzphakm,task_subcomment,NA
+"VisualEditor: Improve message for parameters that have no TemplateData (say ""undocumented"" instead of ""unknown"")","Right now, manually adding a parameter that's not described by TemplateData shows a message saying that the parameter is ""unknown"", which is a little odd if it then seems to work.",1384842902,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-he2d3umv5r6rhdzphakm,task_subcomment,NA
+"VisualEditor: Improve message for parameters that have no TemplateData (say ""undocumented"" instead of ""unknown"")",What would be the exact steps to follow in order to reproduce this problem?,1384181553,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-he2d3umv5r6rhdzphakm,task_subcomment,NA
+VisualEditor: Appending to a line shows additions before end of line in diff,"Steps to reproduce:
+1. Find a page that already has a category
+2. Edit in VE, and add a category
+3. Review changes
+
+Expected results:
+The diff is
+```
++**[[Category:New cat]]**
+```
+
+Actual results:
+The diff is
+```
+-[[Category:Old cat]]
++[[Category:Old cat**]][[Category:New cat**]]
+```
+With the chunk between the stars viewed as added.
+
+This also happens in the source editor, but it is less common that people will append a category to an existing category as that is against all style guidelines.  However the Visual Editor is doing just that.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: normal",1384146180,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-p4ulxppdivzqqe2umxe7,task_description,resolved
+VisualEditor: Appending to a line shows additions before end of line in diff,"I cannot reproduce this anymore with VE visual mode; the category gets added in a separate new line. Maybe this got fixed in T135667.
+Please reopen if you can still reproduce.",1565560030,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-p4ulxppdivzqqe2umxe7,task_subcomment,NA
+VisualEditor: Allow users to set/edit other behavioural flags in the page metadata panel,"Checkboxes (disabled for some/most namespaces), setting:
+
+__NEWSECTIONLINK__
+  <meta property=""mw:PageProp/newsectionlink"">
+
+__NONEWSECTIONLINK__
+  <meta property=""mw:PageProp/nonewsectionlink"">
+
+__NOGALLERY__
+  <meta property=""mw:PageProp/nogallery"">
+
+__HIDDENCAT__
+  <meta property=""mw:PageProp/hiddencat"">
+
+__NOCONTENTCONVERT__
+  <meta property=""mw:PageProp/nocontentconvert"">
+
+__NOCC__
+  <meta property=""mw:PageProp/nocc"">
+
+__NOTITLECONVERT__
+  <meta property=""mw:PageProp/notitleconvert"">
+
+__NOTC__
+  <meta property=""mw:PageProp/notitleconvert"">
+
+__NOEDITSECTION__
+  <meta property=""mw:PageProp/noeditsection"">
+
+__NOINDEX__
+  <meta property=""mw:PageProp/noindex"">
+
+__INDEX__
+  <meta property=""mw:PageProp/index"">
+
+__STATICREDIRECT__
+  <meta property=""mw:PageProp/staticredirect"">
+
+… and possibly others.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384101720,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3p46j5ufygre5dauey6h,task_description,invalid
+VisualEditor: Allow users to set/edit other behavioural flags in the page metadata panel,Split out as bug 57166 ++,1384755174,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3p46j5ufygre5dauey6h,task_subcomment,NA
+VisualEditor: Allow users to set/edit other behavioural flags in the page metadata panel,"Similar to bug 56867 comment 1 I think these would be better handled as pairs of radio buttons, e.g.
+
+Show this category on member pages: * Yes * No
+Show a gallery of images in this category: * Yes * No
+Show a new section link in the tab par for this page: * Yes * No
+Allow search engines to index this page: * Yes * No
+
+Defaults would be set per namespace as at present.",1384186519,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-3p46j5ufygre5dauey6h,task_subcomment,NA
+VisualEditor: Allow users to set/edit __FORCETOC__ status in the page metadata panel,"A checkbox, greyed out when there are more than 2 headings(?), setting:
+
+  <meta property=""mw:PageProp/forcetoc"">
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384101180,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3gsbzhqvjcq7g3i67lcq,task_description,resolved
+VisualEditor: Allow users to set/edit __FORCETOC__ status in the page metadata panel,"Change 95103 merged by jenkins-bot:
+Let users set __NOTOC__ & __FORCETOC__ status
+
+https://gerrit.wikimedia.org/r/95103",1388919569,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3gsbzhqvjcq7g3i67lcq,task_subcomment,NA
+VisualEditor: Allow users to set/edit __FORCETOC__ status in the page metadata panel,"Change 95103 had a related patch set uploaded by Jforrester:
+[WIP] Let users set #REDIRECT, __NOTOC__, & __FORCETOC__
+
+https://gerrit.wikimedia.org/r/95103",1384313414,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3gsbzhqvjcq7g3i67lcq,task_subcomment,NA
+VisualEditor: Allow users to set/edit __FORCETOC__ status in the page metadata panel,"Perhaps better than this and bug 56866 would be a radio button/dropdown with three options for TOC:
+Include an automatic table of contents on this page:
+* Never
+* When there are three or more headings (default)
+* Always
+
+If different wikis (can) have different settings for the number of headings before a TOC then the middle option will need to read that setting.
+
+I say ""automatic"" above as manual TOC templates such as [[template:Compact ToC]] should always override this setting.",1384185420,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-3gsbzhqvjcq7g3i67lcq,task_subcomment,NA
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"PageTriage UI editing User page
+
+seen on beta enwiki:
+
+* log in as a user with PageTriage privileges e.g. Selenium_user
+* visit http://en.wikipedia.beta.wmflabs.org/wiki/Special:NewPagesFeed
+* visit your user page
+
+PageTriage UI appears
+
+PageTriage UI should not appear on User pages
+PageTriage UI should not appear in the editor
+
+see screen shot
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F12047}",1383850080,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-evnlmsxi5llkdqpags37,task_description,resolved
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"Change 133379 merged by jenkins-bot:
+Hide PageTriage curation toolbar while VE is open
+
+https://gerrit.wikimedia.org/r/133379",1400108645,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-evnlmsxi5llkdqpags37,task_subcomment,NA
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"Change 133379 had a related patch set uploaded by Alex Monk:
+Hide PageTriage curation toolbar while VE is open
+
+https://gerrit.wikimedia.org/r/133379",1400106032,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-evnlmsxi5llkdqpags37,task_subcomment,NA
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"
+I don't believe I logged a bug against PageTriage at the time.",1400105734,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-evnlmsxi5llkdqpags37,task_subcomment,NA
+VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page,"(In reply to Chris McMahon from comment #0)
+> PageTriage UI should not appear on User pages
+
+Was a bug logged against PageTriage for that?",1400104778,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-evnlmsxi5llkdqpags37,task_subcomment,NA
+Flow: Agora CSS issues in IE8,"I visited a Flow page in IE8, which is 8% of WMF audience according to https://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix (and more elsewhere I think).
+
+Screenshot https://saucelabs.com/jobs/2a2680aeb681420381a5652ddf5fdca2/0001screenshot.png?auth=fc4f7362b9615cfceee0744b0f4bc93a
+
+There are issues with Flow's local Agora CSS override in IE8:
+* Gray backgrounds on secondary buttons (they should appear without any button border).
+* Buttons aren't rounded.
+* Thank icon goes away on mouseover.
+* ""Start a new topic"" text field and textarea both have no blue bar on focus.
+* Textarea has no placeholder (see http://www.jacklmoore.com/notes/form-placeholder-text/ ,also there's a jquery.placeholder in core, and Matt Flaschen had a placeholder patch for Login forms).
+* Green [Add topic] button text looks poor.
+
+For now this is a Flow bug, but at some point a version of this CSS will migrate to core (bug 54360).  https://gerrit.wikimedia.org/r/#/c/93584 may already have relevant LESS workarounds.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**URL**: http://ee-flow.wmflabs.org/wiki/User_talk:Spage",1383785580,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-akhhxseet47blrfcikb5,task_description,declined
+Flow: Agora CSS issues in IE8,5 years later and IE8 is not longer a supported client.,1523277647,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-akhhxseet47blrfcikb5,task_subcomment,NA
+Flow: Agora CSS issues in IE8,status ?,1409576638,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-akhhxseet47blrfcikb5,task_subcomment,NA
+Flow: Agora CSS issues in IE8,"Possibly relevant, a current discussion on WP:VPT, describing odd problems with IE8 that supposedly only started on Nov 2nd.
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Unable_to_do_anything_through_IE8",1383850053,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-akhhxseet47blrfcikb5,task_subcomment,NA
+Flow: Agora CSS issues in IE8,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/413, but people from the community are welcome to contribute here and in Gerrit.",1383805211,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-akhhxseet47blrfcikb5,task_subcomment,NA
+Flow must respect the per-wiki VE opt-in/out configuration,"VE on beta labs and on prod is opt-in, but VE on test2wiki/mw.o is enabled by default for everyone, including anons. Flow must appropriatly offer VE as configured by the wiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383758160,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-hzlysdp33ce6zpzmy3wm,task_description,invalid
+Flow must respect the per-wiki VE opt-in/out configuration,"We're not using VE anymore; if/when we do, we can reopen.",1390958975,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-hzlysdp33ce6zpzmy3wm,task_subcomment,NA
+Flow must respect the per-wiki VE opt-in/out configuration,Less pressing now that editing in Flow with VisualEditor is disabled by default (gerrit 99721).,1386620084,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-hzlysdp33ce6zpzmy3wm,task_subcomment,NA
+Flow must respect the per-wiki VE opt-in/out configuration,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/411, but people from the community are welcome to contribute here and in Gerrit.",1383805197,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-hzlysdp33ce6zpzmy3wm,task_subcomment,NA
+VisualEditor: Hover effect inconsistent for Help icon,"Noticed on mediawiki.org, currently at 1.23wmf2 (88c7b3f)
+
+On hover, the Help icon in the VisualEditor toolbar gets both the light gray border with all corners rounded, and the darker gray border that, if I look at the Menu icon for reference, should probably only appear when the button is pressed, not just hovered.
+
+Furthermore, the dark gray border only has the left corners rounded.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1383656340,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-6rvja2kia3oue26e5a2q,task_description,declined
+VisualEditor: Hover effect inconsistent for Help icon,"This doesn't appear to be a problem anymore (not even on MonoBook, which still uses the original toolbar design), or I'm misunderstanding your description. In the future, please file bugs with screenshots. :(",1487210805,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6rvja2kia3oue26e5a2q,task_subcomment,NA
+VisualEditor: Hover effect inconsistent for Help icon,"The behaviour is correct because the help icon is actually in a group with the notification icon, however the notification icon is hidden when there are no notifications. This is also the cause of the rounded corners problem, as the CSS renderer doesn't match the last-child rule if the next child is hidden.
+
+Solutions:
+* Group help and notifications with the hamburger menu. This avoids the rounded corners problem, and the issue of the colours looking wrong because it is a set of one, but is hacky.
+* Destroy the notifications icon when not in use. This would involve a bit of a rewrite as in theory it's possible to push notifications after load and the button should appear when this happens.
+* Ungroup help and notifications. This avoids all the problems here.",1383669904,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6rvja2kia3oue26e5a2q,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"As the preferred way to access the `wg*` variables in JavaScript is to use mw.config.get()/.set(), accessing them as globals (i.e. as members of window) should show deprecation notices in debug mode, just like it is done for the functions from wikibits.js.",1383558360,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-f2wyattehq3ovuellsm6,task_description,resolved
+Show deprecation notices when accessing wg* JavaScript globals,"Change 133162 merged by jenkins-bot:
+mw.config: Show deprecation notices when accessing globals
+
+[[https://gerrit.wikimedia.org/r/133162]]",1420428513,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"Change 133162 had a related patch set uploaded (by Krinkle):
+mw.config: Show deprecation notices when accessing globals
+
+[[https://gerrit.wikimedia.org/r/133162]]
+
+#patch-for-review",1417496573,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"Change 133162 had a related patch set uploaded by Gerrit Patch Uploader:
+Show deprecation notices when accessing wg* JavaScript globals
+
+https://gerrit.wikimedia.org/r/133162",1400013433,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,mw.log.deprecate warnings are now visible when not in debug mode too.,1394235254,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"I just tried, and found that mw.log.deprecate can be called multiple times for the same variable without any problems. So mw.config.set could just call it, and whenever a wg* variable is changed via mw.config.set the global value would be updated, too. Only the other way round wouldn't work (or require some extra code instead of mw.log.deprecate).",1383817024,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"(In reply to comment #3)
+> (In reply to comment #1)
+> > mw.config.get('wg*') is currently basically a wrapper for window.wg*. To make
+> > such deprecation notices possible we'd have to duplicate the values, which
+> > could cause them to get out-of-sync if something modified them after page
+> > load.
+> 
+> Is this an actual issue? Once they are set, they shouldn't be changed anyway.
+> So using a new object for mw.config.values instead of window and copying the
+> variables over when they are set the first time using mw.log.deprecate
+> shouldn't break more than replacing some of the wikibits.js functions with
+> $.noop will break.
+
+Apparently VisualEditor sets one, see bug 56532.",1383677840,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"(In reply to comment #1)
+> mw.config.get('wg*') is currently basically a wrapper for window.wg*. To make
+> such deprecation notices possible we'd have to duplicate the values, which
+> could cause them to get out-of-sync if something modified them after page
+> load.
+
+Is this an actual issue? Once they are set, they shouldn't be changed anyway. So using a new object for mw.config.values instead of window and copying the variables over when they are set the first time using mw.log.deprecate shouldn't break more than replacing some of the wikibits.js functions with $.noop will break.
+
+(In reply to comment #2)
+> Hm, how would deprecation actually work? Can we add getters on the window
+> object?
+
+Yes, if you don't believe it, have a look at wikibits.js.",1383641734,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"Hm, how would deprecation actually work? Can we add getters on the window object?",1383588507,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+Show deprecation notices when accessing wg* JavaScript globals,"mw.config.get('wg*') is currently basically a wrapper for window.wg*. To make such deprecation notices possible we'd have to duplicate the values, which could cause them to get out-of-sync if something modified them after page load.",1383560942,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-f2wyattehq3ovuellsm6,task_subcomment,NA
+VisualEditor: unintended ref change resulting in a dirty diff,"https://en.wikipedia.org/w/index.php?title=Guilt_(emotion)&diff=579908396&oldid=576819947
+
+I only intended to edit the ""See also"" section. VisualEditor edited a <ref> without my knowledge or consent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383422400,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-tfngbl2qu7djqip3dbd3,task_description,resolved
+VisualEditor: unintended ref change resulting in a dirty diff,"I [[ https://en.wikipedia.org/w/index.php?title=User%3ANeil_P._Quinn-WMF%2Fsandbox&diff=656821548&oldid=656821441 | repeated ]] @MZMcBride's testcase, and I didn't see any dirt. Closing. ",1429226399,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-tfngbl2qu7djqip3dbd3,task_subcomment,NA
+VisualEditor: Faked keys don't trigger triggers,"If you're not pressing a ""\"" key, OO's trigger doesn't see a ""\"" key being pressed. This includes if you magically simulate a ""\"" key with another key combination, like ""AltGr + 8"" on French keyboards. Should we support that?
+
+Split from bug 53682.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1383283800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zx4tbcdiu47yjmwyniwx,task_description,open
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,"I want to be able to test and give feedback for VisualEditor, so I've opted in on the English Wikipedia.
+
+VisualEditor has bugs, but identifying bugs caused in your own edits can be annoying.
+
+When I make an edit using VisualEditor, I want to be able to verify the edit (double-check VisualEditor's behavior) by viewing a diff of the changes. (Unlike when I'm editing wikitext, where I'll only preview and not use ""show changes"" to view a diff.) Clicking ""Review your edits"" in VisualEditor's user interface is tedious and interrupts my workflow.
+
+It might be nice to implement showing the diff post-save for advanced users who simply want to be able to report an issue with VisualEditor. Or perhaps we could restore the previous behavior where a diff was automatically shown. This is an advanced user option, so it could be JavaScript config or similar. It should not be a user preference or anything that's user-facing. This feature would hopefully make reporting issues easier: rather than needing to request a diff from VisualEditor or navigate to the page history to check a diff link there, you would simply be presented with a diff.
+
+In addition, if we're implementing an advanced user auto-diff option, perhaps we can also add a ""report an issue"" link to more easily file a bug? (Or search for relevant bugs.)
+
+Filing as a Sunday afternoon thought.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382894520,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_description,declined
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,This is probably no longer needed now that most VisualEditor bugs messing up your edits have been fixed (and the few that haven't are known).,1696087493,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_subcomment,NA
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,"Triaging (but doing this as a gadget might make more sense, given this need is going to be short-term and our aversion to preference bloat).",1387221515,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_subcomment,NA
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,"Hey guys. The ""report an issue"" link has been there for a while: click on the question mark, then ""Leave feedback"". You can even choose if you want to file a bug here or add your request to the feedback page. HTH.",1385420445,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_subcomment,NA
+VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue,"(In reply to comment #0)
+> Or perhaps we
+> could restore the previous behavior where a diff was automatically shown.
+
+I don't recall an core mediawiki option for post-save diffs; have I forgotten?
+I would love an pref 'Show diff after page save' in core, which when combined with 'Do not show page content below diffs' would mean my browser doesn't automatically fetch a new version of the page, which could be quite large.
+
+Or, do you mean a pre-launch VisualEditor behaviour where a diff was automatically shown?  Was it pre-save or post-save?",1384145015,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ty7ads3lpdrt4ghudt2s,task_subcomment,NA
+"VisualEditor: Wikitext warning not triggered when editing image captions, references","Wikitext added to image captions is nowikied in the same way that markup added to the page body is. e.g. https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=578947711&oldid=574091986 however the wikitext warning is not generated.
+
+To reproduce:
+1. Load any page with an image in VE
+2. Edit the image caption
+3. Add any wiki markup in the caption (tested with bold, italic and links)
+
+Expected behaviour: The wikitext warning pops up.
+Action behaviour: Nothing happens
+
+If popping up the warning while in the image caption dialog is not possible, then it should do so immediately the dialog is closed. Displaying it at the same time would be preferable though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53839",1382877060,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-esodzvlhnrqwgbidaff4,task_description,resolved
+"VisualEditor: Wikitext warning not triggered when editing image captions, references","Change 138761 merged by jenkins-bot:
+Show wikitext warnings in the reference and media caption dialogs
+
+https://gerrit.wikimedia.org/r/138761",1403125231,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-esodzvlhnrqwgbidaff4,task_subcomment,NA
+"VisualEditor: Wikitext warning not triggered when editing image captions, references","Change 138761 had a related patch set uploaded by Alex Monk:
+Show wikitext warnings in the reference dialog
+
+https://gerrit.wikimedia.org/r/138761",1402445473,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-esodzvlhnrqwgbidaff4,task_subcomment,NA
+"VisualEditor: Wikitext warning not triggered when editing image captions, references","I started looking at this. It's annoying because the code to do the wikitext detection is already there and working for the main surface. It would be trivial to do the absolutely wrong way (i.e. copy the existing code to the reference surface or image caption surface and just change the reference to the Surface object), but it's a pain to fix the proper way.
+
+One of the problems lies in the differences between normal surfaces (i.e. the main one) and surface widgets. It was suggested that we could implement MWSurfaceWidget which does the wikitext warning, but the main surface is not a widget and would still need it's own version of the code.
+
+Also, we can't just shove the wikitext detection code in the ve.ui.Surface class and guard it with some config, because the Surface code lives in VE core which does not deal with MediaWiki features (wikitext) - the VE MediaWiki extension deals with that.
+
+Roan suggested we could make the main surface be a surface widget and then create an MWSurfaceWidget, but that apparently has issues involving toolbar floating (I'm not familiar with this, perhaps it could be fixed in some way).
+
+I think that for now, we can probably change the wikitext detection function to accept a surface parameter, then make it static somewhere and have each wikitext-free surface to set up an event handler for it.",1402442853,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-esodzvlhnrqwgbidaff4,task_subcomment,NA
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.","Please rephrase the message ""Visualeditor-preference-enable"". Currently it says: ""Enable VisualEditor (only in the main and user namespaces)""
+
+With https://gerrit.wikimedia.org/r/#/c/90923/ the VE was enabled in NS_FILE, NS_HELP, NS_CATEGORY namespaces too.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1382807280,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-iun6kcufna6ud4g23brk,task_description,resolved
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.",*** Bug 52188 has been marked as a duplicate of this bug. ***,1385396577,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iun6kcufna6ud4g23brk,task_subcomment,NA
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.","Change 92340 merged by jenkins-bot:
+Re-word visualeditor-preference-enable to not specify NSes
+
+https://gerrit.wikimedia.org/r/92340",1382982294,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iun6kcufna6ud4g23brk,task_subcomment,NA
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.","Change 92340 had a related patch set uploaded by Jforrester:
+Re-word visualeditor-preference-enable to not specify NSes
+
+https://gerrit.wikimedia.org/r/92340",1382981666,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-iun6kcufna6ud4g23brk,task_subcomment,NA
+"VisualEditor: Re-phrase message ""Visualeditor-preference-enable"" to not specify namespaces.",Good catch!,1382807414,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-iun6kcufna6ud4g23brk,task_subcomment,NA
+VisualEditor: Remove unused CSS classes,"For instance, there's a rule for .oo-ui-toolbar-bottom but no code adding that class to anything.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1382592120,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dwai2fmvvprbgn2msyx6,task_description,open
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"see page 
+
+https://test2.wikipedia.org/wiki/User:Selenium_user/cursor_test_page2?veaction=edit
+
+In Chrome, hit down-arrow 3 times to get to the line that begins with text 'Invisible'
+
+In Firefox, it takes 4 times hitting down-arrow to get to that line.  The first time hitting down-arrow does nothing
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382561640,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_description,resolved
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,There are no slugs after lists anymore either.,1423751013,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"Well, this now doesn't happen because Firefox doesn't get the surface selected on open.",1421282698,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"Change 92331 merged by jenkins-bot:
+[browser test] don't run cursor test pending Bug 56068 and review
+
+https://gerrit.wikimedia.org/r/92331",1382979490,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"Change 92331 had a related patch set uploaded by Cmcmahon:
+[browser test] don't run cursor test pending Bug 56068 and review
+
+https://gerrit.wikimedia.org/r/92331",1382978699,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"as of Oct 28, the first right-arrow keyed also does nothing, and the first down-arrow keyed continues to do nothing.   Keying right-arrow had worked before.",1382970830,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"Not occurring in FF18, but is in FF24; divergent behaviour from Chrome, where this works as expected.",1382632069,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox,"
+this is causing browser test failures",1382562148,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ify3mxiz6gcnqdo2h2sx,task_subcomment,NA
+VisualEditor: Remove dual-type support for categories and language links,"Per https://gerrit.wikimedia.org/r/#/c/90339/ we should remove the dual-type support once it's been long enough since Parsoid has renamed the types.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1382468760,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ly3c2pbora5rvknhb3sm,task_description,resolved
+VisualEditor: Remove dual-type support for categories and language links,Re-opened as this will need to be co-ordinated with Parsoid to do a cache purge.,1386302494,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ly3c2pbora5rvknhb3sm,task_subcomment,NA
+VisualEditor: Remove dual-type support for categories and language links,"Change 99310 merged by jenkins-bot:
+Remove dual-type support for Languages and Categories
+
+https://gerrit.wikimedia.org/r/99310",1386284494,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ly3c2pbora5rvknhb3sm,task_subcomment,NA
+VisualEditor: Remove dual-type support for categories and language links,"Change 99310 had a related patch set uploaded by Jforrester:
+Remove dual-type support for Languages and Categories
+
+https://gerrit.wikimedia.org/r/99310",1386211170,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ly3c2pbora5rvknhb3sm,task_subcomment,NA
+"VisualEditor: VE blanks syntax-highlight extension block after editing contents with ""<>"" popup","screenshot
+
+VE blanks syntax-highlight extension block after editing contents with ""<>"" popup. :(
+
+If you open the popup back up the source is there, but the preview in the editor is empty.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Manual:CORS?veaction=edit
+
+**Attached**: {F12120}",1382271180,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-2ns4vqzbqzflsbtpszu5,task_description,resolved
+"VisualEditor: VE blanks syntax-highlight extension block after editing contents with ""<>"" popup","Ha, yeah, we fixed this ages ago, I believe.",1411404775,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2ns4vqzbqzflsbtpszu5,task_subcomment,NA
+"VisualEditor: VE blanks syntax-highlight extension block after editing contents with ""<>"" popup","Does this still happen? I cleaned up various issues with extension blocks some months ago, and I never ran into this.",1411399735,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2ns4vqzbqzflsbtpszu5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"On English Wikipedia, the VE is now not offered for anons & people who have not enabled a user pref.
+
+However if the user loads a URL that invokes VE (i.e. includes ?veaction=edit), it would be nice if VE loaded irrespective of user preferences.  If ?veaction=edit in the URL isnt explicit enough to bypass some checks, ?veaction=edit&debug=true should just do it.
+
+That would streamline testing in many browsers, as we wouldnt need to log in on each browser - which is a bugger because logging into a second browser causes the first browser to be logged out.(bug 49890)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51765
+https://bugzilla.wikimedia.org/show_bug.cgi?id=19415",1382133000,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_description,resolved
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"Change 97701 merged by jenkins-bot:
+Make veaction=edit work regardless of user preference
+
+https://gerrit.wikimedia.org/r/97701",1386027834,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"Change 97701 had a related patch set uploaded by Jforrester:
+Make veaction=edit work regardless of user preference
+
+https://gerrit.wikimedia.org/r/97701",1385459614,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"(In reply to comment #2)
+> It is not a regression. Fixing.
+Removing the code-update-regression keyword; it sounds like you intended to do that.",1382136351,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,"(In reply to comment #0)
+> On English Wikipedia, the VE is now not offered for anons & people who have
+> not enabled a user pref.
+
+Indeed.
+
+> However if the user loads a URL that invokes VE (i.e. includes
+> ?veaction=edit), it would be nice if VE loaded irrespective of user
+> preferences. If ?veaction=edit in the URL isnt explicit enough to bypass some
+> checks, ?veaction=edit&debug=true should just do it.
+
+Possibly, but I feel that this conflicts with the expressed will of the community (to prevent anonymous users from being able to use VisualEditor).
+
+> That would streamline testing in many browsers, as we wouldnt need to log in
+> on each browser - which is a bugger because logging into a second browser
+> causes the first browser to be logged out.(bug 49890)
+
+Understood the use-case (I have the issue too).
+
+(In reply to comment #1)
+> p.s. anon VE testing via URL params used to work.
+
+Because it was enabled for all anons; when the configuration was changed, this feature was disabled. It is not a regression. Fixing.",1382135173,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+VisualEditor: veaction=edit should invoke VE irrespective of user prefs,p.s. anon VE testing via URL params used to work.,1382133712,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-hob5f3o6eqkkls7qd6k5,task_subcomment,NA
+"VisualEditor: When indenting a list as a block, instead of putting it inside its own type, use <dl><dd>s","example of a number list attempting to be indented
+
+This may be similar to https://bugzilla.wikimedia.org/show_bug.cgi?id=48010
+
+In the VisualEditor, entire lists cannot be indented. For example, to get an entire list to appear slightly indented, a user would type in wikitext:
+
+:* First
+:** First sub one
+:** First sub two
+:** First sub three
+:* Second
+:** Second sub one...
+
+Whereas the VisualEditor is attempting to enter this wikitext:
+
+** First
+*** First sub one
+*** First sub two
+*** First sub three
+** Second
+*** Second sub one...
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12745}",1381942020,PHID-USER-2mvmxqtefj5cyyzm7jks,False,PHID-TASK-vmns7e2rmymfweongzav,task_description,open
+VisualEditor: Adding an image at the top of a list puts the image inside the list,"=Steps to reproduce=
+Start with a section whose contents are: 
+```
+ ==Heading==
+ * Alice
+ * Bob
+ * Chris
+```
+Place the cursor just before the 'A' in 'Alice' and insert an image.
+
+The image will be placed inside the first list item:
+```
+==Heading==
+* [[File:Example.jpg]]Alice
+* Bob
+* Chris
+```
+
+Editors almost never place images inside list items so they are likely to expect this to produce the following wikitext instead:
+```
+==Heading==
+[[File:Example.jpg]]
+* Alice
+* Bob
+* Chris
+```
+
+See https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=577354576&oldid=577352415 for an example (look for the image of the apple).",1381880400,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-lv7k67pbkstmigdp3rd7,task_description,open
+VisualEditor: Adding an image at the top of a list puts the image inside the list,"This isn't about the VisualEditor, it is about the PHP Parser?",1488543425,PHID-USER-vlni4mhyozor7ghqnfkl,True,PHID-TASK-lv7k67pbkstmigdp3rd7,task_subcomment,NA
+VisualEditor: Adding an image at the top of a list puts the image inside the list,"Same thing happen at the bottom of the list.
+Example at [[ https://no.wikipedia.org/w/index.php?title=%C3%98vre_Vang_kirke&oldid=17205263 | w:no:Øvre Vang kirke ]].
+
+Note that preview in VisualEditor/WikitextEditor seems to do it right. Or at least different.
+
+It is not enough to add a newline to break out of the list.",1488543289,PHID-USER-vlni4mhyozor7ghqnfkl,True,PHID-TASK-lv7k67pbkstmigdp3rd7,task_subcomment,NA
+VisualEditor: Adding an image at the top of a list puts the image inside the list,"Same thing happen at the bottom of the list.
+Example at [[ https://no.wikipedia.org/w/index.php?title=%C3%98vre_Vang_kirke&oldid=17205263 | w:no:Øvre Vang kirke ]].",1488543193,PHID-USER-vlni4mhyozor7ghqnfkl,True,PHID-TASK-lv7k67pbkstmigdp3rd7,task_subcomment,NA
+VisualEditor: Don't encourage users to set a group for reference lists (as that's only rarely used),"Maybe I havent understood, but I think it is not necessary to push user to add group to Reference list. Most of the references are used as a references. Other groups may be insert as an option. If you force it, it blocks to add references.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381816620,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-lcf23f43lwbo3lfwkrca,task_description,resolved
+VisualEditor: Don't encourage users to set a group for reference lists (as that's only rarely used),"In the fix for bug 59180 we made the group have a placeholder (default text) that says ""General references"" (in English), which should discourage this enough – marking as FIXED, though happy to discuss better ways to improve this if you want to re-open (or create a new bug).",1392860457,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lcf23f43lwbo3lfwkrca,task_subcomment,NA
+VisualEditor: Don't encourage users to set a group for reference lists (as that's only rarely used),"Well,
+
+I think this may cause also the following problem:
+
+At this page:
+https://cs.wikipedia.org/wiki/Angus_MacLise
+There is one reference in group ""p"", but the VE engine sais here:
+https://cs.wikipedia.org/wiki/Angus_MacLise#Pozn.C3.A1mky
+
+there is no group p!",1383465560,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-lcf23f43lwbo3lfwkrca,task_subcomment,NA
+VisualEditor: Don't encourage users to set a group for reference lists (as that's only rarely used),"The ""group"" parameter is necessary if you have multiple reference lists, which is uncommon but is used some times. Re-wording to make clearer.",1381874206,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lcf23f43lwbo3lfwkrca,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"In the software at Wikisource it not possible to have paragraphs (by inserting empty lines) in references similar to the normal text. See: https://en.wikisource.org/wiki/User:Aschroet/test. In the normal HTML view the empty lines are just ignored and only one text block is shown. Even more interesting is the behavior in case when the text is exported by ""Download as PDF"". There, the paragraphs are created but not in a correct way.
+
+The usage of <nowiki><p></nowiki> helps for the HTML view but not for PDF. The usage if <nowiki><br /></nowiki> works but does not generate real paragraphs but only newline in HTML and PDF.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: minor",1381677300,PHID-USER-nrfhx7zwxqc7nau5uyyz,False,PHID-TASK-uysfedps55fdczhfrfys,task_description,open
+No paragraphs/linebreaks in references by inserting empty lines,"Change 574116 **abandoned** by Thiemo Kreuz (WMDE):
+[mediawiki/services/parsoid@master] Replace new lines with <br> tag in references
+
+Reason:
+Please create a new Phabricator ticket to let the Parsoid and VisualEditor teams know what's going on. I'm closing this proposal for now because it is almost certainly not a valid way forward, and to free up our review queues. You can link it from the ticket, and it can be reopened later if it turns out it's a valid way forward.
+
+https://gerrit.wikimedia.org/r/574116",1593768715,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"IMO the editor should add <br> tags when the VE user press Enter inside <ref>. Because presently the behavior is not ""WYSIWYG"" (loss of new lines after saving the page), and, personally, I have an intensive use of references with different paragraphs.",1588259976,PHID-USER-rfidgdbrpqooabqr372x,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"I'm afraid this is not a bug, but an intentional feature of both the #mediawiki-parser and the #Cite extension.
+
+First, references are meant to be text (technically: inline elements). When <ref> tags are rendered, the text is enclosed in <span class=""reference-text"">. However, we are not limiting the features that can be used in <ref>. This is mostly for historical reasons. Cite is old. Users are free to use all wikitext features in <ref>, but we do not and can not guarantee they are all rendered exactly the same as in other contexts.
+
+The fact an empty line in a <ref> does not create a paragraph is, strictly speaking, unrelated to <ref>. The same happens outside of references. Example wikitext:
+```lang=html
+* <span>This does
+
+not render as two paragraphs.</span>
+```
+
+This creates a single list item without any line breaks. As said above, I believe this is intentional and not a bug. If this behavior is going to change, we certainly can't just add a hack to some arbitrary <ref> code, but would need to fix this in all existing Parsers.
+
+Note we can't use <p> elements in a list.",1582385531,PHID-USER-u6ycqhfpa3k4yvlpxjt2,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Change 574116 had a related patch set uploaded (by Pastakhov; owner: Pastakhov):
+[mediawiki/services/parsoid@master] Replace new lines with <br> tag in references
+
+[[https://gerrit.wikimedia.org/r/574116]]",1582325512,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Change 572301 abandoned by Pastakhov:
+Replace new lines with <br> tag in <ref> (patch for v0.11.0) Do Not Merge!
+
+[[https://gerrit.wikimedia.org/r/572301]]",1581706113,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Change 572301 had a related patch set uploaded (by Pastakhov; owner: Pastakhov):
+[mediawiki/services/parsoid@master] Replace new lines with <br> tag in <ref> (patch for v0.11.0) Do Not Merge!
+
+[[https://gerrit.wikimedia.org/r/572301]]",1581705808,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Background:
+
+This issue manifests itself most often when using ""bundled references"" - https://en.wikipedia.org/wiki/Wikipedia:Citing_sources#Bundling_citations - where a single citation calls up multiple sources. Semantically references are a list and what we really ought to be doing is for the bundled references to be a nested list within one item of the overall list. However, the visual presentation of references is often the dominant factor among editors and they try to make each reference in the bundle display on a new line. This is sometimes implemented by inserting a raw <p> tag into the wikitext to create a paragraph and that is (i) semantically incorrect; and (ii) an annoyance for users of screen readers. Using <br> is similarly problematical.
+
+In any case, inserting a blank line does not cause bundled references to display on separate lines as would be expected, hence this bug.",1431350026,PHID-USER-cctxaafy3x73lcil6bsc,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"This bug causes an accessibility issue for screen reader users like myself, allbeit a minor one, because it makes it difficult to create HTML paragraphs that are semantically correct, as discussed at:
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Manual_of_Style/Accessibility&oldid=661776586#.7B.7Bparagraph_break.7D.7D",1431307598,PHID-USER-sufjfnou23bahju6b5me,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"> In the software at Wikisource it not possible to have paragraphs (by inserting empty lines) in references similar to the normal text....
+
+The same type of DIV-ish [[https://en.wikisource.org/w/index.php?title=User:Aschroet/test&diff=5172643&oldid=4604940 | hack]] folks used for BLOCKQUOTE works for one or more newlines wrapped within REF tags as well.
+
+I'm under the impression the ''paragraphStack'' approach in the parser was always at fault when it came to this (or at least plays a role in one reported instance or another). Seems like it should lead off with a closing P tag instead of a BR to me (resulting in an empty P tag at worst).
+
+... but I don't know enough about this stuff to be sure about much truth be told.",1419191897,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"My mind doesn't always understand itself either.
+
+Currently, newlines inside <ref> tags or Image/File brackets are ignored.  This was also the case for <blockquote> and various quote templates.  
+
+Due to Visual Editor's logic, VE was *not* ignoring newlines in <blockquote> or the quote templates.  The solution to fix whether newlines should or shouldn't be ignored was bug 6200.  6200 fixed the parser code so newlines are *not* ignored by anyone.
+
+The question is, does VE respects newline characters in <ref> and Image/File brackets?  I ask the question because:
+1) Bug 6200 languished for eight years until the problem showed up in VE
+2) If VE is not ignoring the newlines, this too becomes a VE vs parser issue.
+3) To show a past precedent of newlines being ignored and the bug being fixed.",1381957895,PHID-USER-xw5m756eevennryab5gb,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,bgwhite: Not sure if the VisualEditor codebase itself thinks or will answer your questions here. Maybe you want to rephrase for humans.,1381922477,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"This problem has been going on for awhile for ref tags.  
+
+Until today, newlines did not work correctly in blockquotes and various blockquote type templates (bug 6200).  The bug was finally fixed today on enwiki after 8 1/2 years and 2 years after a patch was submitted.  The reason for finally fixing it was because Virtual Editor thought newlines should actually work like newlines.  Silly VE.
+
+Does VE think newlines should actually work in ref tags?
+https://en.wikipedia.org/wiki/Mormons, ref 110 uses a newline. 
+
+Newlines also don't work in Image/File brackets.  Does VE think newlines should actually work there too?
+https://en.wikipedia.org/wiki/Angular_momentum, second to last image is an example.",1381902538,PHID-USER-xw5m756eevennryab5gb,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"For the example, in Wikisource we convert orignial sources to digital texts. Footnotes as e.g. in https://de.wikisource.org/wiki/Seite:Die_Gartenlaube_%281865%29_703.jpg (sorry, i usually work in German wikisource) are mapped to <ref> blocks. Since they are from time to time a little bit longer there are paragraphs inside the footnodes. 
+
+Yes, <br /> enforces a line break but not indent of the following sentence.
+
+I am just wondering why there is a different treatment in references than in the normal text for ""normal"" paragraphs.",1381701183,PHID-USER-nrfhx7zwxqc7nau5uyyz,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+No paragraphs/linebreaks in references by inserting empty lines,"Thanks for taking the time to report this!
+
+What is an example/real usecase to use paragraphs in references?
+
+As you wrote, a workaround is to insert a <br> to enforce a linebreak.
+
+[Resetting component, as ""Export/Import"" refers to ""Special:Export and Special:Import"" only.]",1381683169,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-uysfedps55fdczhfrfys,task_subcomment,NA
+VisualEditor: Broken link creation workflow,"I'm not sure exactly how I cause this bug but I've seen it twice now.
+
+Works somewhat like this:
+Click anywhere in the textarea and ensure there is whitespace before the cursor and nothing highlighted.
+
+Click the link button
+enter text, save it.
+
+The link doesn't get added anywhere and now clicking the link button to create a new link has no effect.
+
+I get JavaScript exception:
+Uncaught Error: Offset could not be translated to a DOM element and offset: 6306
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381361640,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-epe55jgajl2jerw3siyg,task_description,declined
+VisualEditor: Broken link creation workflow,Can't replicate. Closing for now.,1396470649,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-epe55jgajl2jerw3siyg,task_subcomment,NA
+VisualEditor: Broken link creation workflow,"Yes, that exception only throws from one place, and the high number looks like it's trying to find a position beyond the end of the document, but I can't reproduce.",1382530303,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-epe55jgajl2jerw3siyg,task_subcomment,NA
+VisualEditor: Broken link creation workflow,Yeh I know.. I was hoping the Javascript exception would help debug somewhat. I managed to make it happen twice but haven't done so recently. Any clues from that exception to when it might occur?,1382468176,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-epe55jgajl2jerw3siyg,task_subcomment,NA
+VisualEditor: Broken link creation workflow,"This is difficult to look into without steps to reproduce. Let us know if you see it again, and how.",1382453865,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-epe55jgajl2jerw3siyg,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","On editing a page on mediawiki.org
+
+Navigated to
+https://www.mediawiki.org/wiki/Manual:Coding_conventions/CSS?veaction=edit#Less
+
+Looking in the console I see:
+Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist. 
+
+The save button is disabled.
+I only noticed this after doing a long edit :(
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**URL**: https://www.mediawiki.org/wiki/Manual:Coding_conventions/CSS?veaction=edit",1381190760,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_description,open
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Patch to disable SyntaxHighlight is now merged, so this problem will be suppressed with the production push tomorrow morning; restoring to ""ASSIGNED"".",1381370904,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Change 88901 merged by jenkins-bot:
+Remove SyntaxHighlight from the experimental set
+
+https://gerrit.wikimedia.org/r/88901",1381361800,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Change 88901 had a related patch set uploaded by Catrope:
+Remove SyntaxHighlight from the experimental set
+
+https://gerrit.wikimedia.org/r/88901",1381361398,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","This was because of breakage in MWSyntaxHighlightNode, and that page 1) contains such a node and 2) is on mw.org where MWSyntaxHighlightNode is actually enabled. This is experimental code that's only enabled on mw.org and nowhere else (although it will be available everywhere else as an opt-in once we get BetaFeatures going).",1381358788,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Oh, sorry, it's something about that page in particular - confirmed on Chromium 28, Ubuntu GNU/Linux 12.04",1381355681,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","WFM, Chromium 28 on Ubuntu GNU/Linux 12.04",1381355602,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""","Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist. load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%2Cs…:155
+ve.dm.Converter.getDomSubtreeFromData load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%2Cs…:155
+ve.dm.Converter.getDomFromData load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%2Cs…:148
+(anonymous function) load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.by…:94",1381190952,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""",Google Chrome Version 30.0.1599.69 and https://www.mediawiki.org/w/index.php?title=Manual:Coding_conventions/CSS&oldid=797048,1381190885,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+"VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws ""Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.""",ve.dm.Converter.js:1401,1381190833,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-ghws2ohsdojmmph4ub27,task_subcomment,NA
+VisualEditor: Clean up phantom mouse event code in ve.ce.ProtectedNode,"Currently, the mouse event handling in phantoms is:
+```lang=js
+// mouseenter on the protectednode
+ve.ce.ProtectedNode.prototype.onProtectedMouseEnter = function () {
+	if ( !this.root.getSurface().dragging ) {
+		this.createPhantoms();
+	}
+};
+
+// mousemove on the surface, bound by createPhantoms and unbound by clearPhantoms
+ve.ce.ProtectedNode.prototype.onSurfaceMouseMove = function ( e ) {
+	var $target = $( e.target );
+	if (
+		!$target.hasClass( 've-ce-protectedNode-phantom' ) &&
+		$target.closest( '.ve-ce-protectedNode' ).length === 0
+	) {
+		this.clearPhantoms();
+	}
+};
+
+// mouseout on the surface, bound by createPhantoms and unbound by clearPhantoms
+ve.ce.ProtectedNode.prototype.onSurfaceMouseOut = function ( e ) {
+	if ( e.toElement === null ) {
+		this.clearPhantoms();
+	}
+};
+```
+Issues:
+* the mousemove handler seems to permit moving the mouse directly to a different ProtectedNode without causing the phantoms to be cleared
+* the mouseout handler uses e.toElement, which is a poorly documented property that's allegedly IE-only
+* it's generally very difficult to reason about what this code does or convince oneself that it does something reasonable
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381185960,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mf6ollxu3yqurw4viu55,task_description,resolved
+VisualEditor: Clean up phantom mouse event code in ve.ce.ProtectedNode,"ProtectedNode became FocusableNode, and phantoms became highlights.
+
+
+> the mousemove handler seems to permit moving the mouse directly to a different ProtectedNode without causing the phantoms to be cleared
+
+This seems to be fixed in {138a7f862f24f66452ec2fd805ac43c53fbb583b}.
+
+> the mouseout handler uses e.toElement, which is a poorly documented property that's allegedly IE-only
+
+Big rewrite in {e1b0e33df7796ed41028aa04355b302e6559445b} changed that to use e.relatedTarget, which is legit, and basically the same (according to <http://help.dottoro.com/ljltrsom.php>).
+
+> it's generally very difficult to reason about what this code does or convince oneself that it does something reasonable
+
+This is still true, but I'm not sure if it's fixable :)
+
+
+>>! In T57448#597087, @Catrope wrote:
+> What's even worse is that if somehow another ProtectedNode does manage to show other phantoms, they will replace the first node's phantoms (because of the way ce.Surface manages phantoms), but if for some reason clearPhantoms() isn't called, the first node will continue to track the now-detached phantoms and reposition them when a transaction occurs.
+
+This might still be a problem.",1579119330,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mf6ollxu3yqurw4viu55,task_subcomment,NA
+VisualEditor: Clean up phantom mouse event code in ve.ce.ProtectedNode,"What's even worse is that if somehow another ProtectedNode does manage to show other phantoms, they will replace the first node's phantoms (because of the way ce.Surface manages phantoms), but if for some reason clearPhantoms() isn't called, the first node will continue to track the now-detached phantoms and reposition them when a transaction occurs.",1381186300,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mf6ollxu3yqurw4viu55,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Right now the way that you add a template through the VisualEditor is by choosing the Transclusion option from the toolbar.
+
+'Transclusion' is programmer jargon. Regular people have no idea what that means. 'Template' is a somewhat ambiguous term, but at least it matches all of our documentation and the name of the namespace. It is also less scary sounding.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381170240,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-t7swuomd63q7e3mou7kp,task_description,resolved
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","> 'Transclusion' is programmer jargon. Regular people have no idea what that means.
+
+ =/",1420450176,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","> 'Transclusion' is programmer jargon. Regular people have no idea what that means.
+
+=/",1398701048,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","(In reply to Helder from comment #5)
+> Created attachment 15228 [details]
+> Transclusion vs. Template
+> 
+> I'm still seeing a few ""transclusion"" in the dialogs, on English Wikipedia.
+
+Transclusion dialog != template dialog; transclusion = multiple template dialog.
+
+**Attached**: {F11988}",1398700163,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Created attachment 15228
+Transclusion vs. Template
+
+I'm still seeing a few ""transclusion"" in the dialogs, on English Wikipedia.
+
+**Attached**: {F11988}",1398683755,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Change 117151 merged by jenkins-bot:
+Re-label ""Transclusion"" button to ""Template"", as that's now the default
+
+https://gerrit.wikimedia.org/r/117151",1394075228,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Change 117151 had a related patch set uploaded by Jforrester:
+Re-label ""Transclusion"" button to ""Template"", as that's now the default
+
+https://gerrit.wikimedia.org/r/117151",1394073856,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions",*** Bug 58163 has been marked as a duplicate of this bug. ***,1393525848,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+"VisualEditor: Call the ""transclusion"" dialog a ""template"" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions","Eh. Maybe. We've been talking about this for months and months (surprised that there's not an extant bug for this). The problem is that though ""transclusion"" is indeed confusing and a surprising word, it has the advantage of being correct, and  ""template"" is even more confusing (and just jargon from a different well).",1381171497,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t7swuomd63q7e3mou7kp,task_subcomment,NA
+VisualEditor: Wikitext diff is not regenerated if VE content is the same but the page has subsequently changed,"+++ This bug was initially created as a clone of Bug #55392 +++
+
+VE caches the diff, which means if no content is changed, the user is shown
+a) a stale diff and is allowed to proceed with saving the page, which means they are then
+b) the page with their saved changes only
+The user is unaware that they have overwritten another persons changes.
+
+Steps to reproduce:
+1. Create a page with some two lines
+   https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=573748285
+2. Open the page in two VE windows
+3. In the second window, alter the first line and save
+   https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=576079696
+5. In the first window, alter the first line and review changes
+   (the diff only shows the first line being modified
+    against the page contents from step 3)
+6. In the second window, add some lines and save
+   https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=576079807
+7. In the first window, review changes, and cancel the save
+   (the diff is the same as in step 5; the VE page content doesnt change)
+8. In the first window, save
+
+Expected results:
+In step 7, the diff should be refreshed even though the page content has not been modified.
+
+Actual results:
+The diff from step 5 is displayed in step 7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=55392",1381115640,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-kfr2fhuhxwwkvqg5jwuw,task_description,open
+VisualEditor: Wikitext diff is not regenerated if VE content is the same but the page has subsequently changed,"At bug 55392 comment 3 James says that in core mediawiki functionality ""you can't edit conflict with yourself, and new edits silently over-write"", which could mean this bug is also the correct behaviour.  Need to retest with two different users.",1399697381,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-kfr2fhuhxwwkvqg5jwuw,task_subcomment,NA
+VisualEditor: Wikitext diff is not regenerated if VE content is the same but the page has subsequently changed,This might be a Parsoid issue?,1381118185,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-kfr2fhuhxwwkvqg5jwuw,task_subcomment,NA
+VisualEditor: The link suggestor should suggest links from the current namespace ahead of named links,"If the user is editing a content namespace, the link dialog should search the current namespace first, then all other content namespaces, when looking for link targets.
+
+Steps to reproduce
+1. https://www.mediawiki.org/wiki/Manual:Page_table?veaction=edit
+2. Write and select 'archive table'
+3. Open link dialog
+
+Expected results:
+Link target 'manual:archive table' automatically found
+
+Actual results:
+Link target 'archive table' (new page) is automatically provided
+
+The same is needed for Wikisource which has, e.g. an Author: content namespace.
+
+Wikipedias with a content namespace listed in InitialiseSettings.php:
+Arabic Wikipedia : T22623
+  https://ar.wikipedia.org/wiki/%D8%AE%D8%A7%D8%B5:%D9%81%D9%87%D8%B1%D8%B3_%D8%A8%D8%A7%D8%AF%D8%A6%D8%A9/%D9%85%D9%84%D8%AD%D9%82:
+Spanish Wikipedia : T41866
+  https://es.wikipedia.org/wiki/Especial:P%C3%A1ginasPorPrefijo/Anexo:
+North Frisian Wikipedia: T40023
+  (Wikisource inside Wikipedia)
+Croatian Wikipedia: T42732
+  https://hr.wikipedia.org/wiki/Posebno:Prefiks_indeks/Dodatak:
+Portuguese Wikipedia:
+  https://pt.wikipedia.org/wiki/Especial:%C3%8Dndice_por_prefixo/Anexo:
+
+(and more potential ones listed at T41866)
+
+As an aside, in 'Help' namespace, which isnt set as a content namespace, it would be nice to search within that namespace when linking, but that is a more blurry line.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T71780}
+{T57390}
+{T64917}
+{T71716}",1381111920,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cfrutsorovcrc76vfomh,task_description,open
+"VisualEditor: Inserted objects (references, templates, images) should not be selected after insertion","**Author:** `Wikifram`
+
+**Description:**
+When you add a reference, it is automatically selected (blue), instead of having the cursor positioned directly after it (or better still, with a space after the ref and the cursor after that). The effec is that if you enter a ref and then start typing (which is rather normal editing behaviour), your ref immediately gets removed (overwritten) again, which makes it rather pointless. 
+
+I think that it is much more often the intention to continue typing after adding a ref, than to have it highlighted, so please change the default behaviour.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1380869940,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4yohlm5rptv4jnlli5mk,task_description,resolved
+"VisualEditor: Inserted objects (references, templates, images) should not be selected after insertion","Change 100522 merged by jenkins-bot:
+Don't select nodes inserted by a dialog, but drop cursor after
+
+https://gerrit.wikimedia.org/r/100522",1386793552,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4yohlm5rptv4jnlli5mk,task_subcomment,NA
+"VisualEditor: Inserted objects (references, templates, images) should not be selected after insertion","Change 100522 had a related patch set uploaded by Catrope:
+Don't select nodes inserted by a dialog, but drop cursor after
+
+https://gerrit.wikimedia.org/r/100522",1386641138,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4yohlm5rptv4jnlli5mk,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","When the text of a link is changed in VisualEditor, the link target does not change. This results in many, many edits which are entirely well-intentioned but for a patroller look like vandalism. E.g. a user tries to fix the wrong date `[[2000]]` and ends up with `[[2000|2001]]` - an erroneous link that is basically impossible to catch in visual view. (Some examples: [[https://de.wikipedia.org/w/index.php?title=Osmium(IV)-oxid&diff=prev&oldid=122526489|diff]], [[https://hu.wikipedia.org/w/index.php?title=Lengyelorsz%C3%A1g_f%C3%B6ldrajza&diff=19527995&oldid=18755093|diff]]) This is a major problem; even highly experienced users fall prey to this, and new editors all the more (and then they get treated as vandals by the patrollers who are not familiar with VE and have no idea what's going on).
+
+Maybe there could be some sort of notice asking whether the editor also wants to correct the actual target in case they change the displayed part of a wikilink (T55973#2792012 has a nice mockup).
+
+On-wiki reports:
+[[https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=123123378#Wikilink-Korrektur|Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07#Wikilink-Korrektur]]
+[[https://hu.wikipedia.org/wiki/Wikipédia:Kocsmafal_(egyéb)/Archív250#VisualEditor-hiba%3A_megtévesztő_belső_hivatkozások_létrehozása|Wikipédia:Kocsmafal_(egyéb)#VisualEditor-hiba: megtévesztő belső hivatkozások létrehozása]]
+
+See Also:
+* {T59506}
+* {T55973}",1380841680,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-muxtuy47vttbiujlra5y,task_description,open
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#6657213, @Tgr wrote:
+>>>! In T56947#6654187, @Esanders wrote:
+>> The volume in the above mentioned edit filter (T56947#2098243) would be a good metric for success. It might be useful to have it on more high volume wikis.
+> 
+> Note that the filter only catches changes to dates (which is a good way to avoid false positives, but it avoids the vast majority of true positives too). So it's a good way of measuring whether problematic edits become less frequent, but not a good way of measuring how frequent they are, in an absolute sense.
+
+In addition to the abuse filter, I also generate twice a month a dump analysis which gets a bit more than the filter (same as in my post above) :
+
+
+  - On [[ https://en.wikipedia.org/wiki/Wikipedia:CHECKWIKI/WPC_526_dump | enWP ]]
+  - On [[ https://fr.wikipedia.org/wiki/Projet:Correction_syntaxique/Analyse_526 | frWP ]]
+
+",1606769955,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#6657213, @Tgr wrote:
+>>>! In T56947#6654187, @Esanders wrote:
+>> The volume in the above mentioned edit filter (T56947#2098243) would be a good metric for success. It might be useful to have it on more high volume wikis.
+> 
+> Note that the filter only catches changes to dates (which is a good way to avoid false positives, but it avoids the vast majority of true positives too). So it's a good way of measuring whether problematic edits become less frequent, but not a good way of measuring how frequent they are, in an absolute sense.
+
+In addition to the abuse filter, I also generate dump twice a month a dump analysis which gets a bit more than the filter (same as in my post above) :
+
+
+  - On [[ https://en.wikipedia.org/wiki/Wikipedia:CHECKWIKI/WPC_526_dump | enWP ]]
+  - On [[ https://fr.wikipedia.org/wiki/Projet:Correction_syntaxique/Analyse_526 | frWP ]]
+
+",1606769924,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#6654173, @Esanders wrote:
+> Since this was last discussed we added the label editing field to mobile VE.
+> 
+> I think bringing that interface over to desktop would make these mistakes much less common as whenever you edit the link target, the link label is shown in an editable field right next to it.
+> 
+> By removing the existing edit label button that just puts the cursor into the surface, we would also push label editors to the same interface. Complex annotated labels could still be edited in the surface.
+
+I think that would be an improvement for experienced users as well, the current desktop approach for changing the label doesn't work that well. (This is worse for external links, where you end up with an uneditable `[1]` that you cannot change at all without involving the mouse, but normal links have some annoying mechanics as well.)
+
+>>! In T56947#6654187, @Esanders wrote:
+> The volume in the above mentioned edit filter (T56947#2098243) would be a good metric for success. It might be useful to have it on more high volume wikis.
+
+Note that the filter only catches changes to dates (which is a good way to avoid false positives, but it avoids the vast majority of true positives too). So it's a good way of measuring whether problematic edits become less frequent, but not a good way of measuring how frequent they are, in an absolute sense.",1606769045,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",The volume in the above mentioned edit filter (T56947#2098243) would be a good metric for success. It might be useful to have it on more high volume wikis.,1606653159,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Since this was last discussed we added the label editing field to mobile VE.
+
+I think bringing that interface over to desktop would make these mistakes much less common as whenever you edit the link target, the link label is shown in an editable field right next to it.
+
+By removing the existing edit label button that just puts the cursor into the surface, we would also push label editors to the same interface. Complex annotated labels could still be edited in the surface.",1606652304,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",And 2021: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Editing/Unintentional_false_links_in_VE,1606651924,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",Relevant Community Wishlist entry: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Editing/Avoid_VisualEditor_edits_changing_only_the_link_text_or_only_the_link_target,1543306882,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",T55973#2792012 may interest some of the followers of that task.,1479143554,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","On frwiki, the problem appeared in the following pages between the February and March dump, I haven't checked what is the proportion of VE edits.
+Problems with only [[1990|2000]] are not listed here but can be found with the abuse filter
+https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Journal_du_filtre_antiabus&wpSearchFilter=241
+
+* [[3 Mustaphas 3]]: <nowiki>[[1990 en musique|1986]]</nowiki>
+* [[Alexandra Lacrabère]]: <nowiki>[[2016 en handball|2014]]</nowiki>
+* [[Alexondra Lee]]: <nowiki>[[2012 au cinéma|1998]]</nowiki>
+* [[Anaïs Delva]]: <nowiki>[[2014 à la télévision|2015]]</nowiki>
+* [[Andra Akers]]: <nowiki>[[1978 à la télévision|1979]]</nowiki>
+* [[Andy Samberg]]: <nowiki>[[2016 au cinéma|2013]]</nowiki>
+* [[Annapolis]]: <nowiki>[[2010 aux États-Unis|2000]]</nowiki>
+* [[Anne-Violaine Brisou]]: <nowiki>[[2010 en sports équestres|2009]]</nowiki>
+* [[Arthur Brown (musicien)]]: <nowiki>[[1992 en musique|1993]]</nowiki>
+* [[Baudouin Taslé d'Héliand]]: <nowiki>[[2011|2016]]</nowiki>, <nowiki>[[2011|2015]]</nowiki>, <nowiki>[[2011|2013]]</nowiki>, <nowiki>[[2011|2012]]</nowiki>
+* [[Billy Talent]]: <nowiki>[[2001 en musique|1999]]</nowiki>
+* [[Boris Tokarev (acteur)]]: <nowiki>[[1967 au cinéma|1976]]</nowiki>
+* [[Bruno Léandri]]: <nowiki>[[2014|2015]]</nowiki>
+* [[Carlos Edwards]]: <nowiki>[[2008 en football|2011]]</nowiki>, <nowiki>[[2014 en football|2011]]</nowiki>
+* [[Cesare Danova]]: <nowiki>[[1980 à la télévision|1981]]</nowiki>
+* [[Chair de poule (film)]]: <nowiki>[[2015 au cinéma|2016]]</nowiki>
+* [[Charles Chaynes]]: <nowiki>[[1995 en musique|1958]]</nowiki>
+* [[Charlie Rowe]]: <nowiki>[[2006 à la télévision|200]]</nowiki>
+* [[Claude Mann]]: <nowiki>[[2014 au théâtre|2015]]</nowiki>
+* [[Claude Scasso]]: <nowiki>[[2015 à la télévision|2016]]</nowiki>
+* [[Claudio Lemmi]]: <nowiki>[[2007 au théâtre|2008]]</nowiki>, <nowiki>[[2006 au théâtre|2007]]</nowiki>, <nowiki>[[2011 au théâtre|2012]]</nowiki>
+* [[Club Atlético San Lorenzo de Almagro]]: <nowiki>[[2016 en football|2015]]</nowiki>
+* [[Construction navale]]: <nowiki>[[1631|1931]]</nowiki>
+* [[Coupe de Tunisie de football (FFF)]]: <nowiki>[[1921 en sport|1922]]</nowiki>
+* [[Courrier international]]: <nowiki>[[2014|2015]]</nowiki>
+* [[Croc-Blanc]]: <nowiki>[[1992 au cinéma|1991]]</nowiki>
+* [[David Zucker]]: <nowiki>[[1993 au cinéma|1983]]</nowiki>
+* [[Dominika Minicz]]: <nowiki>[[2001 en sport|2003]]</nowiki>
+* [[Drowning Pool]]: <nowiki>[[2013 en musique|2016]]</nowiki>
+* [[Du Caurroy]]: <nowiki>[[1750|1850]]</nowiki>
+* [[Dunkerque Handball Grand Littoral]]: <nowiki>[[1992 en handball|1978]]</nowiki>
+* [[Déborah Heissler]]: <nowiki>[[2005 en littérature|2004]]</nowiki>
+* [[En dépit des étoiles]]: <nowiki>[[2016 en littérature|2013]]</nowiki>
+* [[Ermin Šiljak]]: <nowiki>[[1999 en football|1998]]</nowiki>, <nowiki>[[2000 en football|2001]]</nowiki>
+* [[François Guérin (réalisateur)]]: <nowiki>[[2011 au cinéma|2000]]</nowiki>
+* [[Frédéric Gaillard]]: <nowiki>[[2006 en football|2008]]</nowiki>
+* [[Fury Records]]: <nowiki>[[1957 en musique|1987]]</nowiki>, <nowiki>[[1957 en musique|1987]]</nowiki>
+* [[Fédération camerounaise de football]]: <nowiki>[[2012|2013]]</nowiki>
+* [[Gaëtan Vassart]]: <nowiki>[[2015 au théâtre|2016]]</nowiki>
+* [[Georges Beuret]]: <nowiki>[[1800|1803]]</nowiki>
+* [[Gianluigi Buffon]]: <nowiki>[[1987 en football|1997]]</nowiki>
+* [[Grand Corps Malade]]: <nowiki>[[2014 en littérature|2012]]</nowiki>
+* [[Guerre FISA-FOCA]]: <nowiki>[[1978 en sport automobile|1979]]</nowiki>
+* [[Heidi]]: <nowiki>[[1937 au cinéma|1973]]</nowiki>
+* [[Hervé Jolly]]: <nowiki>[[1990 au cinéma|1991]]</nowiki>, <nowiki>[[1991 au cinéma|1990]]</nowiki>
+* [[Hot Rod (rappeur)]]: <nowiki>[[2010 en musique|2011]]</nowiki>
+* [[Houari Ferhani]]: <nowiki>[[2013 en football|2014]]</nowiki>
+* [[Hugo Moulinier]]: <nowiki>[[2008 en sport|2013]]</nowiki>
+* [[Ion Ansotegui]]: <nowiki>[[2003 en football|2016]]</nowiki>
+* [[Ismaël Bangoura]]: <nowiki>[[2013 en football|2016]]</nowiki>
+* [[Jaime Penedo]]: <nowiki>[[2005 en football|2006]]</nowiki>
+* [[James LeGros]]: <nowiki>[[2015 au cinéma|2016]]</nowiki>
+* [[Jamie Lee Curtis]]: <nowiki>[[1983 au cinéma|1984]]</nowiki>
+* [[Jardin botanique de Liège]]: <nowiki>[[2010|2016]]</nowiki>
+* [[Jason Bard]]: <nowiki>[[1939 en bande dessinée|1969]]</nowiki>
+* [[Jean Arp]]: <nowiki>[[2005|2014]]</nowiki>
+* [[Jean Sagols]]: <nowiki>[[1988 à la télévision|1989]]</nowiki>
+* [[Jean-Paul Daoust]]: <nowiki>[[2015 en littérature|2016]]</nowiki>
+* [[Joe Stone]]: <nowiki>[[2015 en musique|2013]]</nowiki>
+* [[John Kenneth Galbraith]]: <nowiki>[[1979 en littérature|1980]]</nowiki>
+* [[Jon Abrahams]]: <nowiki>[[2004 au cinéma|2005]]</nowiki>, <nowiki>[[2007 au cinéma|2009]]</nowiki>, <nowiki>[[2008 au cinéma|2009]]</nowiki>, <nowiki>[[2013 au cinéma|2014]]</nowiki>
+* [[Jovan Ćurčić]]: <nowiki>[[1995 en football|1976]]</nowiki>, <nowiki>[[1996 en football|1977]]</nowiki>
+* [[Jérôme L'Hotsky]]: <nowiki>[[2013 au cinéma|2012]]</nowiki>
+* [[Kaamelott]]: <nowiki>[[2015 en bande dessinée|2017]]</nowiki>
+* [[Kaisa Alanko]]: <nowiki>[[2013 en sport|2016]]</nowiki>
+* [[Katé-Mé]]: <nowiki>[[1995 en musique|1996]]</nowiki>
+* [[Khalid Karami]]: <nowiki>[[2002 en football|2004]]</nowiki>, <nowiki>[[2011 en football|2005]]</nowiki>, <nowiki>[[2001 en football|2005]]</nowiki>, <nowiki>[[2012 en football|2011]]</nowiki>
+* [[Kora Jazz Band]]: <nowiki>[[2015 en musique|2014]]</nowiki>
+* [[Krawatencross]]: <nowiki>[[2004 en cyclisme|2016]]</nowiki>, <nowiki>[[2004 en cyclisme|2016]]</nowiki>
+* [[L'Amour des trois oranges (opéra)]]: <nowiki>[[1950 en musique classique|1961]]</nowiki>
+* [[La Garçonnière (film, 1960)]]: <nowiki>[[1995 en littérature|1996]]</nowiki>
+* [[La Guerre de Caliban]]: <nowiki>[[2015 en littérature|2016]]</nowiki>
+* [[Lamine Ndao]]: <nowiki>[[2011 en football|2013]]</nowiki>, <nowiki>[[2011 en football|2013]]</nowiki>
+* [[Laurent Bouhnik]]: <nowiki>[[1999 au cinéma|1998]]</nowiki>
+* [[Laurent Courtiaud]]: <nowiki>[[2010 au cinéma|2011]]</nowiki>
+* [[Liste des présidents de la République d'Angola]]: <nowiki>[[1992|1979]]</nowiki>
+* [[Lorie Pester]]: <nowiki>[[2005 au cinéma|2004]]</nowiki>
+* [[Luke Grimes]]: <nowiki>[[2018 au cinéma|2017]]</nowiki>
+* [[Léon Cordes]]: <nowiki>[[1969|1974]]</nowiki>, <nowiki>[[1977|1974]]</nowiki>
+* [[M. Chapoutier]]: <nowiki>[[1879|1808]]</nowiki>
+* [[Malika Wagner]]: <nowiki>[[2010 en littérature|2016]]</nowiki>
+* [[Marc Renard]]: <nowiki>[[2008 en littérature|2016]]</nowiki>
+* [[Marcilio]]: <nowiki>[[2014 en sport|2042]]</nowiki>
+* [[Marco Motta]]: <nowiki>[[2016 en football|2015]]</nowiki>
+* [[Marilyne Canto]]: <nowiki>[[1977 au cinéma|1978]]</nowiki>
+* [[Meaghan Rath]]: <nowiki>[[2015 à la télévision|2016]]</nowiki>
+* [[Mickey 3D]]: <nowiki>[[1999 en musique|1998]]</nowiki>, <nowiki>[[2015 en musique|2006]]</nowiki>, <nowiki>[[2015 en musique|2009]]</nowiki>, <nowiki>[[2015 en musique|2010]]</nowiki>, <nowiki>[[2015 en musique|2010]]</nowiki>, <nowiki>[[2015 en musique|2016]]</nowiki>
+* [[Mini-Star]]: <nowiki>[[1982 en musique|1983]]</nowiki>
+* [[NGC 271]]: <nowiki>[[1798|1785]]</nowiki>
+* [[Nicky Jam]]: <nowiki>[[2015|2014]]</nowiki>, <nowiki>[[2015|2014]]</nowiki>
+* [[Néstor Ortigoza]]: <nowiki>[[2011 en football|2010]]</nowiki>, <nowiki>[[2011 en football|2012]]</nowiki>
+* [[Pascal Brissy]]: <nowiki>[[2003 en littérature|2001]]</nowiki>
+* [[Patrick Béthune]]: <nowiki>[[2002 au cinéma|2009]]</nowiki>
+* [[Patrick Timsit]]: <nowiki>[[2016|2017]]</nowiki>
+* [[Paul Barge (1941- )]]: <nowiki>[[1970 à la télévision|1980]]</nowiki>
+* [[Petr Zelenka]]: <nowiki>[[2005 au cinéma|2015]]</nowiki>
+* [[Peugeot 305]]: <nowiki>[[1989|1990]]</nowiki>
+* [[Pierre Douglas]]: <nowiki>[[1979 au cinéma|1975]]</nowiki>
+* [[Princes et Princesses]]: <nowiki>[[1999 au cinéma|2000]]</nowiki>
+* [[Raouf Benguit]]: <nowiki>[[2008 en football|2013]]</nowiki>, <nowiki>[[2015 en football|2014]]</nowiki>
+* [[Raphaël Didjaman]]: <nowiki>[[2012|2015]]</nowiki>, <nowiki>[[2012|2016]]</nowiki>
+* [[Raymond Ochoa]]: <nowiki>[[2013 au cinéma|2015]]</nowiki>
+* [[Reem Kherici]]: <nowiki>[[2014 au cinéma|2016]]</nowiki>
+* [[Rencontres d'Arles]]: <nowiki>[[1985 en photographie|1982]]</nowiki>
+* [[Rick Hoffman]]: <nowiki>[[2010 à la télévision|2000]]</nowiki>
+* [[Rihanna]]: <nowiki>[[2005 en musique|2004]]</nowiki>
+* [[Robert Walser (écrivain)]]: <nowiki>[[1916 en littérature|1917]]</nowiki>
+* [[Rocky Balboa (film)]]: <nowiki>[[2014 au cinéma|2015]]</nowiki>
+* [[Romain Dumas]]: <nowiki>[[2014 en sport|2015]]</nowiki>
+* [[Santigold]]: <nowiki>[[2015 en musique|2016]]</nowiki>
+* [[Slobodan Rajković]]: <nowiki>[[2005 en football|2006]]</nowiki>
+* [[Srđan Ristić]]: <nowiki>[[2001 en sport|2006]]</nowiki>, <nowiki>[[2008 en sport|2009]]</nowiki>, <nowiki>[[2010 en sport|2014]]</nowiki>
+* [[Swamp Thing]]: <nowiki>[[2013 en bande dessinée|2014]]</nowiki>, <nowiki>[[2013 en bande dessinée|2015]]</nowiki>
+* [[Sylvain Marchal]]: <nowiki>[[2015 en football|2016]]</nowiki>
+* [[Taken (série télévisée)]]: <nowiki>[[2007 au cinéma|2015]]</nowiki>
+* [[Tallac Records]]: <nowiki>[[2012 en musique|2135]]</nowiki>
+* [[Thierry Westermeyer]]: <nowiki>[[2004 en musique|2001]]</nowiki>
+* [[Umberto Eco]]: <nowiki>[[2000 en littérature|1988]]</nowiki>, <nowiki>[[2004 en littérature|2009]]</nowiki>
+* [[Under Two Flags]]: <nowiki>[[1867 en littérature|1897]]</nowiki>
+* [[Université de La Rochelle]]: <nowiki>[[2008|2016]]</nowiki>
+* [[VfL Wolfsbourg]]: <nowiki>[[2005 en football|2015]]</nowiki>
+* [[Villa La Reine Jeanne]]: <nowiki>[[1928|1933]]</nowiki>
+* [[Villiers-Saint-Georges]]: <nowiki>[[2001 en France|2008]]</nowiki>, <nowiki>[[2008 en France|2014]]</nowiki>
+* [[Vladimir Venguerov]]: <nowiki>[[1954 au cinéma|1945]]</nowiki>
+* [[William Séry]]: <nowiki>[[2013 en football|2014]]</nowiki>
+* [[Yann Arthus-Bertrand]]: <nowiki>[[2012 en littérature|2015]]</nowiki>, <nowiki>[[2012 en littérature|2015]]</nowiki>
+* [[Yuma (Arizona)]]: <nowiki>[[2008|2010]]</nowiki>
+* [[Yusef Lateef]]: <nowiki>[[2005|1989]]</nowiki>
+* [[Zakaria Haddouche]]: <nowiki>[[2011 en football|2013]]</nowiki>
+* [[Álvaro Magalhães]]: <nowiki>[[1980 en football|1981]]</nowiki>
+* [[Éditions À la carte]]: <nowiki>[[2012 en Suisse|2016]]</nowiki>
+",1457426012,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Elitre 
+Yes.
+
+For the 1st and 3rd, I know, but there are only a few articles in these cases (5 of them exactly in total). And they appear at the beginning of the list, because they are recognized as special and my bot didn't flag them with {{Lien à corriger}}... So none of them appear in the dedicated category ""Article avec un lien à corriger"", and are not counted in the ""more than 6.000 articles""
+
+For the 2nd, I never said that all errors were due to VE, but most of them are. We are still talking about thousands of VE mistakes
+",1457350363,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Elitre 
+Yes.
+
+For the 1st and 3rd, I know, but there are only a dozen of articles in these cases. And they appear at the beginning of the list, because they are recognized as special and my bot didn't flag them with {{Lien à corriger}}... So none of them appear in the dedicated category ""Article avec un lien à corriger"", and are not counted in the ""more than 6.000 articles""
+
+For the 2nd, I never said that all errors were due to VE, but most of them are. We are still talking about thousands of VE mistakes
+",1457349845,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","(Just a quick comment about the query linked above:
+it includes links to pages [[ https://fr.wikipedia.org/w/index.php?title=Accident_ferroviaire_de_Zoufftgen&type=revision&diff=104207507&oldid=104207037 | which are not years and not added by mistake]];
+it includes pages where [[ https://fr.wikipedia.org/w/index.php?title=1._FC_Neubrandenburg_04&action=edit&oldid=62013397 | the visual editor was never used, and the mistake is almost certainly a typo]];
+it includes pages where [[ https://fr.wikipedia.org/w/index.php?title=Nombre_de_Markov&action=edit&oldid=12476390 | the visual editor was never used, and the editor seems to have made a deliberate choice about the link target]].
+There may be more, I'm not going to dig deeper though.)",1457349108,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF
+In addition to the abuse filter that was put in place last year, I've also recently run a bot on a dump from frwiki to find the incorrect links to pages related to years like [[2000|2015]] or [[2000 en musique|2015]].
+Result is at https://fr.wikipedia.org/wiki/Projet:Correction_syntaxique/Analyse_526
+
+Analysis on February dump found more than 6.000 articles with this kind of problem (and it's only for years related links, we are probably missing the majority of incorrect links)
+
+I've then run a bot to add a warning after each problematic link with a template
+https://fr.wikipedia.org/wiki/Mod%C3%A8le:Lien_%C3%A0_corriger
+It displays a warning message and puts the article in a tracking category
+https://fr.wikipedia.org/wiki/Cat%C3%A9gorie:Article_avec_un_lien_%C3%A0_corriger
+
+It helped reduce the number of articles with this problem to about 5.400 articles
+
+This shows that this problem is far from being anedoctic (and I don't know how to evaluate how many articles have the same problem, but not for links related to years)",1457221150,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Maybe whenever someone changes the link text which initially was the same as the link target, and the new link text is the name of an existing article, show a small warning in some easy-to-notice color in the link widget saying ""[click here] to update the link target as well""?",1457220558,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","+1 to //that ""better"" method is live, and we still have this problem//.
+",1457220364,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF
+Only for links to years which are easy to detect by a filter and (almost ?) always an error
+https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Filtre_antiabus/241",1432644594,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",@NicoV:  Isn't there an edit filter on the French Wikipedia that would show every time this happens?,1432576409,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#1294934, @Neil_P._Quinn_WMF wrote:
+>>>! In T56947#1294891, @Amire80 wrote:
+>> I may be missing something, but to me it's pretty obvious that changing the blue text ""2010"", which happens to point to [[2010]], to ""2015"" must change the link target to [[2015]].
+> 
+> @Amire80, are you suggesting that when a link has the same text and target (e.g. [[2010]]), changing the text should automatically change the target? Consider that this would make it //impossible// to change, for example, [[Impressionism]] to [[Impressionism|Impressionist]].
+
+It won't be impossible if the inspector is shown, as it already is. An editor who really wants to change the text, but leave the target, can use the inspector to change it.
+
+What I'm saying is that common sense tells me that when when the text and the target are the same and the text is changed, the target should be changed by default automatically. It makes little sense to alert the user that the target should be changed, because it's likely that that's what the user wants anyway, and double work should be avoided. It there's any alert, then it should be about the opposite: that maybe the user wants to //keep// the target.",1432121178,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Another pretty common mistake I find is people modifying [[Wikipedia]] to [[Wikipedia|Wiki]]pedia (probably a drag and drop problem).
+Sometimes I see also [[Wikipedia|wikipedia]] or [[wikipedia|Wikipedia]] (VE seems to ignore first letter is case insensitive).
+Finally I seldom (let's say less than 20 occurrences per month) find [[Wikipedia|Wikipedia]], still wrong but easy to fix via bot.",1432052602,PHID-USER-irgoyfmq4qktx4ueexfk,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#1294891, @Amire80 wrote:
+> I may be missing something, but to me it's pretty obvious that changing the blue text ""2010"", which happens to point to [[2010]], to ""2015"" must change the link target to [[2015]].
+
+@Amire80, are you suggesting that when a link has the same text and target (e.g. [[2010]]), changing the text should automatically change the target? Consider that this would make it //impossible// to change, for example, [[Impressionism]] to [[Impressionism|Impressionist]].",1431984454,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","I may be missing something, but to me it's pretty obvious that changing the blue text ""2010"", which happens to point to [[2010]], to ""2015"" must change the link target to [[2015]].",1431982566,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF, to what //extent// do we still have this problem? Now, anytime your cursor is within a link range, you get a big popup showing the target, along with a helpful picture in many cases; I'm not sure how much more visible it's possible to make the target without making it severely distracting.
+
+At any rate, if it still is a major problem and we decide it needs to be addressed, I feel strongly that a more fundamental design change, not a reminder popup, would be the right solution. When a user type `<ref>`, for example, we don't bring up a comment saying: ""Did you mean to add a reference?"". We just pop up the citation dialog.",1431981263,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF, to what //extent// do we still have this problem? Now, anytime your cursor is within a link range, you get a big popup showing the target, along with a helpful picture in many cases; I'm not sure how much more visible it's possible to make the target without making it severely distracting.",1431981065,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","@Whatamidoing-WMF, to what extent do we still have this problem? Now, anytime your cursor is within a link range, you get a big popup showing the target, along with a helpful picture in many cases; I'm not sure how much more visible it's possible to make the target without making it severely distracting.",1431981051,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",">>! In T56947#1266454, @Whatamidoing-WMF wrote:
+> Okay, that ""better"" method is live, and we still have this problem.  
+> 
+> We need people (especially experienced editors) to be warned that this is happening.  When they see [[2010]], and they change the visible ""2010"" part to say ""2015"", they expect the result to be [[2015]], not [[2010|2015]].
+> 
+> Solutions could be a soft warning, like asking ""Do you want to change the destination link to match?"", but sirens and flashing lights and a blinking banner that says something like ""DANGER, WILL ROBINSON!  IT LOOKS ALL RIGHT ON YOUR SCREEN, BUT THE ACTUAL LINK IS STILL SECRETLY GOING TO THE ORIGINAL PAGE!!"" would be good, too.
+
+imo, solution should not be ""soft warning"". solution should be something like
+""internal links are not directly editable on page. when editor tries to edit an internal link, popup the ""link"" tool instead"".
+
+peace.",1431449887,PHID-USER-akv4ingxkspiiam6r2n4,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Okay, that ""better"" method is live, and we still have this problem.  
+
+We need people (especially experienced editors) to be warned that this is happening.  When they see [[2010]], and they change the visible ""2010"" part to say ""2015"", they expect the result to be [[2015]], not [[2010|2015]].
+
+Solutions could be a soft warning, like asking ""Do you want to change the destination link to match?"", but sirens and flashing lights and a blinking banner that says something like ""DANGER, WILL ROBINSON!  IT LOOKS ALL RIGHT ON YOUR SCREEN, BUT THE ACTUAL LINK IS STILL SECRETLY GOING TO THE ORIGINAL PAGE!!"" would be good, too.",1430942372,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",This will be done better via {T88337}.,1424911487,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Merged in a bunch of duplicates. T63558 might be another one (not sure).
+Proposing for potential VE Q3 Blocker due to the numerous duplicates (but feel free to punt).",1424371535,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","I am a bit of a VE ambassador in the Hebrew Wikipedia and an experienced user asked me about this today. I know there are over a thousand other bugs and I don't mean to nudge, but this keeps coming up and I am curious whether this is considered as a needed feature on a product design level.",1409122552,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too",*** Bug 57506 has been marked as a duplicate of this bug. ***,1400106756,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too","Changing links is unintuitive -- user changes link text, but that dosen't change link target --see also this diff https://et.wikipedia.org/w/index.php?title=Joel_Luhamets&diff=3899205&oldid=3861224",1398576932,PHID-USER-hxt4ak6xrngllg2dof3u,True,PHID-TASK-muxtuy47vttbiujlra5y,task_subcomment,NA
+"VisualEditor: Make the isRedirect disable check look at the revision being considered, not current revision","When a page is currently a redirect, but has none-redirect versions in its history those versions should be editable in VE but are not. e.g. https://en.wikipedia.org/w/index.php?title=Equality_Acts&oldid=570457856
+
+To reproduce:
+1. Load any page that is not a redirect in the source editor
+2. Change the page into a redirect and save
+3. View any revision prior to the redirect
+
+Expected behaviour: Old version is editable in VE
+Action behaviour: No option is given to edit in VE
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50878",1380813300,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-yuoxq5n2ii32plugotg4,task_description,invalid
+"VisualEditor: Make the isRedirect disable check look at the revision being considered, not current revision","We no longer stop editing of isRedirect pages, so marking as INVALID now.",1398706803,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yuoxq5n2ii32plugotg4,task_subcomment,NA
+"VisualEditor: Make the isRedirect disable check look at the revision being considered, not current revision","I'm not sure how easy this would be to do... It appears to be based on MediaWiki core's wgIsRedirect, which would need fixing to work out whether the current revision is a redirect (instead of the latest revision of the current page). I'm not sure core even has a function to work that out at the moment. Even in the database, the field to determine if something is a redirect is in the page table instead of the revision table.",1390956621,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-yuoxq5n2ii32plugotg4,task_subcomment,NA
+"VisualEditor: Make the isRedirect disable check look at the revision being considered, not current revision","Will be superseded by bug 50878 once bug 47328 is implemented, but could be done sooner if someone is keen.",1380834030,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yuoxq5n2ii32plugotg4,task_subcomment,NA
+Ability to change preferences without leaving current page,"When a user goes to change a preference, they are usually in one of the following states:
+1. On a page that the preference would affect, and they wish to change the preference and have the change be effective asap.
+2. About to go to a page, and know they need to change a preference in order that it is rendered the way they want.
+
+An example of both of those scenarios is bug 52355, where a user wants to enable the VisualEditor on the current page, or enable it on the next page they visit (especially if it is a redlink).
+
+Currently the typical workflow is
+0. The user on a mediawiki page
+1. Load special:preferences
+2. Change the preference and Save (which loads preferences panel again)
+3. Press 'Back' button twice
+4. Reload or click a link
+
+Desired workflow:
+1. Open a pref panel in the current page
+2. Change the pref and close the panel
+3. The changes become effective immediately, if that can be achieved without reloading the page and/or loosing any user data, or a small notice displayed near the preferences panel button to inform the users their changes will be effective by reloading.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52355",1380686940,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-is3n3dhxo4ti5nzgooot,task_description,open
+New keywords for dataloss and corruption,"All products occasionally cause the user to have their work disappear.  It could be the browser crashes, or the UI in a window becomes locked up.  The VisualEditor is having more than its fair share of these at the moment, and it would be good to track them with a keyword.
+
+There are quite a few Parsoid/VisualEditor bugs that are behind 'corruption' of the wiki database.  'corruption' probably isnt the best name for the keyword.  It would include all the nowiki and pawn bugs, but also some parsoid round-trip issues.  These are not always high priority/severity, if they are rare or impossible in a 'normal configuration'.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1380675360,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_description,declined
+New keywords for dataloss and corruption,Closing for the time being as per comment 6. Feel free to reopen if there are more requestees / more arguments.,1384462331,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"In case that you are so far the only person interested in this, I recommend to use the Whiteboard field instead of introducing keywords - only difference to keywords is that anybody can use it for tagging (so using a ""personal namespace"" might be considered, e.g. I use the whiteboard for ""aklapper-moreinfo"" entries), and that it is not limited to entries globally defined on the server (like for keywords).
+I'm saying this because I prefer to keep the list of keywords small (as otherwise nobody can remember them anymore and does not set them, seen that problem in many other Bugzillas) and cross-product.",1382106411,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"Yes I am intetested in building lists. I could use tracking bugs, but we have this funky keywords feature in bugzilla where dataloss and corruption typically go.
+
+Precisely because dataloss and corruption are orthogonal to severity and priority, these keywords would allow periodic review of these bugs that havent been resolved due to prioritisation and open adhoc system.
+
+My intentions are to help the mediawiki product and extensions and users.",1381793776,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"(In reply to comment #1)
+> Refering to a potential database corruption keyword, what are your
+> intentions?
+> Are you just interesting to find a list of all such issues more quickly?
+> Would this keyword somehow help developers to keep track?",1381767050,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"(In reply to comment #2)
+> IMO severity and dataloss are orthogonal.  Not all critical are dataloss
+> cases,
+> and some dataloss are not critical.  The definition of critical includes a
+> reasonable caveat 'in a widely used and important component'.
+
+I agree, it does not always fit, but in most cases.
+Question is: How exact and specific do we need to tag information in Bugzilla, and for the sake of who? :)",1380708699,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"A discussion is happening over at https://www.mediawiki.org/wiki/Talk:Bugzilla/Fields
+
+IMO severity and dataloss are orthogonal.  Not all critical are dataloss cases, and some dataloss are not critical.  The definition of critical includes a reasonable caveat 'in a widely used and important component'.
+
+I would consider bug 52187 to be a dataloss problem, and that its severity of normal is a reasonable assessment.  But that doesnt change the fact that real users are loosing their data.
+
+IMO bug 54591 would be corruption, but unlikely to be critical as it isnt a standard operation to add a math element and put nothing in it, and it is easily fixable.",1380704888,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+New keywords for dataloss and corruption,"Loss of data is severity=critical by definition ( https://www.mediawiki.org/wiki/Bugzilla/Fields#importance ) hence I don't see a need for a keyword.
+
+Refering to a potential database corruption keyword, what are your intentions? Are you just interesting to find a list of all such issues more quickly? Would this keyword somehow help developers to keep track?",1380701068,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vcq6z4aphzzlu3bsrflv,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"this is like bug 46893.
+
+ $ cd extensions/VisualEditor/modules/ve-mw/test/browser
+ $ bundle exec cucumber features/visual_editor_bullets.feature
+
+If the tests progress, eventually they print out a lot of
+
+*** DEPRECATION WARNING
+*** You are calling a method named class_name at /home/spage/projects/core/extensions/VisualEditor/modules/ve-mw/test/browser/features/step_definitions/visual_editor_bullets_steps.rb:81:in `block in <top (required)>'.
+*** This method does not exist in page-object so it is being passed to the driver.
+*** This feature will be removed in the near future.
+*** Please change your code to call the correct page-object method.
+*** If you are using functionality that does not exist in page-object please request it be added.
+
+*** DEPRECATION WARNING
+*** You are calling a method named select_text at /home/spage/projects/core/extensions/VisualEditor/modules/ve-mw/test/browser/features/step_definitions/visual_editor_bullets_steps.rb:14:in `block in <top (required)>'.
+*** [same last 4 lines]
+
+The lines deprecated by the former are all of the form
+  SOME_element.class_name.{should, should_not} match /disabled/
+where the HTML has CSS class=""ve-ui-widget ve-ui-tool ve-ui-tool-outdent ve-ui-widget-disabled"".  I don't know the page-object equivalent to retrieving the CSS class (attribute( 'class' ), but maybe instead the code could use page-object's disabled? and enabled? methods.
+
+The latter deprecation is odd since the test specifically requires ""watir-webdriver/extensions/select_text""
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal
+**Whiteboard**: gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks",1380084600,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-al543vpnemdlnqyld3n4,task_description,resolved
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"After a quick look at VisualEditor Jenkins jobs[0], looks like this is fixed. Please reopen if you see the problem again.
+
+0: https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/",1414406388,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"(In reply to Chris McMahon from comment #4)
+> Cheezy actually fixed this but hasn't updated the page-object gem yet
+> https://github.com/cheezy/page-object/issues/192
+
+Željko / Chris: Is this still a valid ticket one year after? Has Cheezy updated it in the meantime or is this still a task suitable for new contributors?",1414345430,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"If you need more information (and you probably do), feel free to ask questions
+here, at #wikimedia-qa freenode IRC channel or at QA mailing list:
+
+https://lists.wikimedia.org/mailman/listinfo/qa",1386004101,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,Cheezy actually fixed this but hasn't updated the page-object gem yet https://github.com/cheezy/page-object/issues/192,1382721432,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,See also bug 46893,1382712015,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"And here:
+
+https://wmf.ci.cloudbees.com/job/VisualEditor-test2.wikipedia.org-linux-firefox/119/console",1382711956,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+page-object Ruby gem deprecation warnings in VisualEditor browser tests,"Still not fixed:
+
+https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-test2.wikipedia.org-linux-chrome/96/console",1382711467,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-al543vpnemdlnqyld3n4,task_subcomment,NA
+VisualEditor: Allow inspectors to be left-aligned?,"Non-embedded inspectors are generally positioned to the bottom right of the node they're inspecting. In cases where we're dynamically altering the node, however (like the live preview feature for math), it probably makes more sense to position that kind of inspector at the bottom left. Then if the dimensions of the node change, the inspector will move around a bit less.
+
+Thoughts? Other ideas to tackle this issue?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1380073020,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vnxcxik6c5qmqlw52xaj,task_description,resolved
+VisualEditor: Allow inspectors to be left-aligned?,Fixed a while ago,1442494980,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vnxcxik6c5qmqlw52xaj,task_subcomment,NA
+Flow: misleading exception is thrown if the parsoid service is down,"If the parsoid service is down (`sudo service parsoid stop`, or update extension/Parsoid and forget/fail `npm install`), then viewing flow pages fails with exception
+
+   Parser only supports wikitext to HTML conversion
+
+   Backtrace:
+
+   #0 /srv/mediawiki/extensions/Flow/includes/ParsoidUtils.php(24): Flow\ParsoidUtils::parser('html', 'wikitext', '<p>It's a long ...')
+
+This is true, but it masks the real problem that parsoid has to work, and didn't.  ParsoidUtils::convert has a try-catch block around using parsoid, and if that fails it will fall back to using parser. It would be helpful for wiki operators if the exception message included the parsoid failure, e.g.
+   Parser only supports wikitext to HTML conversion (and parsoid earlier failed with exception ""VisualEditor is unavailable"")
+
+Now that I've figured out what's going on, this has become a low-priority bug :-)
+
+--------------------------
+**Version**: master
+**Severity**: minor",1380001740,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-vpzdercihud4opsstlu6,task_description,resolved
+Flow: misleading exception is thrown if the parsoid service is down,https://gerrit.wikimedia.org/r/#/c/92633/,1386220039,PHID-USER-r5pzlcquei6f4hb53rfg,False,PHID-TASK-vpzdercihud4opsstlu6,task_subcomment,NA
+Flow: misleading exception is thrown if the parsoid service is down,Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/264,1380310267,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-vpzdercihud4opsstlu6,task_subcomment,NA
+VisualEditor: Allow re-positioning of selected media items using arrow keys,"When an image is selected it should be possible to position it using the cursor keys.
+
+up/down should move it one line up/down. Whether left/right should move it one character or one word at a time I'm not sure about. Possibly shift/ctrl should modify this?
+
+This would be useful for fine control and for systems with laggy mouse behaviour (not uncommon on slow connections in my experience).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51665",1379954340,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-b2btpgodq22ee3ay6bt2,task_description,open
+VisualEditor: Allow re-positioning of selected media items using arrow keys,We probably can't use arrow keys (because that's over-riding expected behaviour of moving the cursor) but we could use Ctrl+→ etc. potentially.,1380072535,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-b2btpgodq22ee3ay6bt2,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"When a pre-formatted paragraph with long lines is displayed in VE it word wraps. However it doesn't word-wrap in display mode (T2260), meaning that you have no idea that you need to add manual line breaks until after you have saved.
+
+See https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&oldid=573792519#Section_number_three (rendered) and https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&oldid=573792519&veaction=edit&section=2 (in VE)
+
+The word wrapping in VE is actually better than what happens in read mode, but the two should not be different. Fixing T2260 would be better, but as it's been open since 2004 adjusting VE to match the current behaviour seems more realistic :/
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=260",1379694420,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_description,resolved
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"Change 205177 merged by jenkins-bot:
+Do not wrap <pre> nodes
+
+[[https://gerrit.wikimedia.org/r/205177]]",1429559989,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"Change 205177 had a related patch set uploaded (by Bartosz Dziewoński):
+Do not wrap <pre> nodes
+
+[[https://gerrit.wikimedia.org/r/205177]]
+",1429476381,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"We have `pre.ve-ce-branchNode { white-space: pre-wrap; }` added per T40043, because Chrome/Safari will otherwise //also// wrap the text, not just between words, but anywhere (this affects any `<pre>` inside a  `contenteditable=""true""` node). I did some searching and found https://bugs.webkit.org/show_bug.cgi?id=35935; it appears that we can set `word-wrap: normal;` to override this behavior.
+
+We also need to remove `overflow: hidden` from the surface to get regular sane horizontal scrolling behavior. It doesn't //seem// to be necessary…",1429476284,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,,1429475491,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,,1429475153,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"Created attachment 17130
+Read - no word wrapping
+
+**Attached**: {F11732}",1415999787,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,"Created attachment 17129
+Preformatted text in Edit- word wrapping is present
+
+**Attached**: {F11731}",1415999734,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Long lines in preformatted paragraphs should not wrap in VE,Alternatively we could fix this bug in MediaWiki…,1415881181,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mnx5c5z533vu7ca4ybtp,task_subcomment,NA
+VisualEditor: Provide a dialog with a list of all keyboard short-cuts (on Ctrl+? or similar?),"See e.g. http://www.impressivewebs.com/demo-files/question-mark-js/ - similarly used in Reddit etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379661360,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5xysqxijiml4iixxb7sd,task_description,resolved
+VisualEditor: Provide a dialog with a list of all keyboard short-cuts (on Ctrl+? or similar?),https://gerrit.wikimedia.org/r/#/c/107153/,1390677098,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-5xysqxijiml4iixxb7sd,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for searching for pages (some don't come up),"Screenshot of link inspector not listing a matching page
+
+When opening the link inspector on a link to dab page [[Department of Foreign Affairs and Trade]], the link inspector shows two items: the dab page, and the page [[Department of Foreign Affairs and Trade (Ireland)]].  It does not list [[Department of Foreign Affairs and Trade (Australia)]].  The unlisted page is not a new page.
+
+Steps to reproduce:
+1. https://en.wikipedia.org/w/index.php?title=Heidi_Bootle&oldid=573475141
+2. Open Visual Editor
+3. Click on Department of Foreign Affairs and Trade
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51013
+
+**Attached**: {F11697}",1379640720,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cqgpkdfnpdapeshycn57,task_description,duplicate
+VisualEditor: OpenSearch results aren't perfect for searching for pages (some don't come up),"Actually, merging this into bug 51013 for actioning.
+
+*** This bug has been marked as a duplicate of bug 51013 ***",1410985568,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cqgpkdfnpdapeshycn57,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for searching for pages (some don't come up),*** Bug 67150 has been marked as a duplicate of this bug. ***,1406753647,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cqgpkdfnpdapeshycn57,task_subcomment,NA
+VisualEditor: OpenSearch results aren't perfect for searching for pages (some don't come up),*** Bug 62804 has been marked as a duplicate of this bug. ***,1395185089,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cqgpkdfnpdapeshycn57,task_subcomment,NA
+VisualEditor: Enwiki's {{divstyleamber}} (used in a parameter) turns into mw:ExpandedAttrs in Parsoid which VE doesn't handle yet.,"Although it can't be used in articles, it is widely used elsewhere, including userpages.
+If you try and VEdit https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=573626556 you'll notice that this reflects in reference numbering being incorrect, since the ones in the divbox will be ignored.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54803",1379590260,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-dxrqwnd4epgrwlipk5o2,task_description,open
+VisualEditor: Enwiki's {{divstyleamber}} (used in a parameter) turns into mw:ExpandedAttrs in Parsoid which VE doesn't handle yet.,"Another issue:
+<<Open a page with {{divbox|amber|test|Test content.}} Click on the divbox, open the template dialogue. Click on ""apply changes"". Divbox disappears.>>
+
+If you want to test this, VEdit https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=573628652 .",1379591181,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-dxrqwnd4epgrwlipk5o2,task_subcomment,NA
+VisualEditor: Enwiki's {{divstyleamber}} (used in a parameter) turns into mw:ExpandedAttrs in Parsoid which VE doesn't handle yet.,"My previous comment was related to a page containing <div style=""{{divstyleamber}}"">Content.</div>, which can not be edited.",1379591096,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-dxrqwnd4epgrwlipk5o2,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Incorrect reversed display of non Latin characters
+
+Please see the attached image and Bugs #54308 & #54309.
+
+By this time I resigned to utilize the advanced toolbar and after making an attempt, I feel very cynical because this effort is totally useless. There is a lot to be said for programmers and developers learning to proofread a chapter or so of text, to see how their ideas are working in the real world.
+
+In the first place, It takes several steps to hide the header to gain additional viewing space or access various features. 
+
+Finally, The non-Latin characters, like Hebrew and Arabic were inserted from left to right. For those who don't understand, that's the equivalent of displaying Latin characters from right to left, as in: . . . . L K J I H G F E D C B A
+
+In view of my previous posts, please consider correcting this ASAP.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11606}",1379579460,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_description,resolved
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 414961 **merged** by jenkins-bot:
+[mediawiki/extensions/WikiEditor@master] Use display:inline-block for special character buttons
+
+[[https://gerrit.wikimedia.org/r/414961]]",1520269897,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415286 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] fetchSpecialCharList: Set directionality
+
+[[https://gerrit.wikimedia.org/r/415286]]",1519948593,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415374 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (f5c88eb30)
+
+[[https://gerrit.wikimedia.org/r/415374]]",1519932738,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415374 had a related patch set uploaded (by Jforrester; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (bdb1a680a)
+
+[[https://gerrit.wikimedia.org/r/415374]]",1519848137,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415281 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] SpecialCharacterPage: Allow setting lang/dir via special attributes property
+
+[[https://gerrit.wikimedia.org/r/415281]]",1519846076,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415286 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] fetchSpecialCharList: Set directionality
+
+[[https://gerrit.wikimedia.org/r/415286]]",1519825824,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 415281 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] SpecialCharacterPage: Allow setting lang/dir via special attributes property
+
+[[https://gerrit.wikimedia.org/r/415281]]",1519825655,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"I set the CSS float to right for RTL languages.
+
+If this is done for WikiEditor, then it must also be updated in the VE special character editor. There is will be easier: the lang and dir attributes must simply set on the `<div>` that wraps all the characters `<span>` tags.",1519718525,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Change 414961 had a related patch set uploaded (by Amire80; owner: Amire80):
+[mediawiki/extensions/WikiEditor@master] Order right-to-left alphabets from right-to-left in the special character selector
+
+[[https://gerrit.wikimedia.org/r/414961]]",1519718250,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"**yesod22** wrote:
+
+Hi. The only input I can give is that as a bi-lingual english hebrew speaker being forced with the option of having english displayed RTL or hebrew displayed LTR is CERTAINLY not desired. I'd much prefer having each language displayed in it's natural order - as it's supposed to be.
+
+The idea of displaying Hebrew or Arabic from LTR because that's the expectation of an english speaker reminds me of a joke by Louis CK on how the pilgrims named the natives ""Indians"" despite the fact that they had nothing to do with India :-) (see youtube). A language should be displayed in it's order - not in the order of what a non-native speaker would like it to be :-)
+
+blessings, Daniel",1380213955,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Michael M., Please point me to the page on en.Wikipedia where RTL characters show up correctly. I just implemented the WikiEditor on en. Wikipedia and RTL characters were displayed in LTR order. Then, I am curious as to how do you know what is the expectation of the users???",1379680638,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Reopening: I looked at en.wikipedia and de.wikipedia. Both have a set of special characters *below* the editbox, which isn't part of MediaWiki, but developed by the communities. In both cases the characters of RTL languages are shown from right to left, so even if this behavior of WikiEditor is intended (which I doubt), it is wrong based on the expectation of its users.",1379664481,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Andre, the user's language settings should not affect the character sets. They should be displayed in their natural order regardless of the user's language preferences.",1379623385,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+RTL language characters are displayed in LTR order in LTR languages (and vice versa),"Confirming what you see. Hebrew letters Alef and Bet are on the left. 
+
+I am pretty sure that this is intended and that it depends on your personal language settings in https://en.wikisource.org/wiki/Special:Preferences#mw-prefsection-personal-i18n because depending on your ""primary"" language you are used to either expect the first letter on the left (LTR) or on the right (RTL).
+
+It's the same the other way round: 
+Looking at the Cyrillic character section with the interface language set to Hebrew (by simply adding &uselang=he to the URL), I also get the Russian alphabet from right to left, while Russian is a left to right language.",1379586269,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yj6unjc6sotp4kv2mflx,task_subcomment,NA
+VisualEditor: ResizableNode should show numeric dimensions when resizing.,"In a status bar/next to the cursor/on the image
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379549160,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-db7owolkladsvbupsv7m,task_description,resolved
+VisualEditor: ResizableNode should show numeric dimensions when resizing.,"Change 85970 merged by jenkins-bot:
+Show a label with the current dimensions while resizing
+
+https://gerrit.wikimedia.org/r/85970",1382007456,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-db7owolkladsvbupsv7m,task_subcomment,NA
+VisualEditor: ResizableNode should show numeric dimensions when resizing.,"Change 85970 had a related patch set uploaded by Esanders:
+Show a label with the current dimensions while resizing
+
+https://gerrit.wikimedia.org/r/85970",1380109182,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-db7owolkladsvbupsv7m,task_subcomment,NA
+VisualEditor: ResizableNode should show numeric dimensions when resizing.,"Created attachment 13376
+Screenshot of implementation
+
+**Attached**: {F11558}",1380109052,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-db7owolkladsvbupsv7m,task_subcomment,NA
+"VisualEditor: VE ""edit"" link in section edit links of a remote file tries to create a new page on local wiki, not remote section","Example image: https://www.mediawiki.org/wiki/File:MassMessage_submitted.png
+
+Clicking on ""edit"" takes you to <https://www.mediawiki.org/wiki/File:MassMessage_submitted.png?veaction=edit&vesection=1>
+
+Clicking on ""edit source"" tags you to <https://commons.wikimedia.org/w/index.php?title=File:MassMessage_submitted.png&action=edit&section=1>
+
+The 'edit' link should take you to commons and somehow gracefully fallback on the wikitext editor since VE is not enabled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://www.mediawiki.org/wiki/File:MassMessage_submitted.png
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62071",1379486100,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-wwi2e2vktmnorzseurla,task_description,resolved
+"VisualEditor: VE ""edit"" link in section edit links of a remote file tries to create a new page on local wiki, not remote section","Change 130082 merged by jenkins-bot:
+Don't change section edit links on foreign file description pages
+
+https://gerrit.wikimedia.org/r/130082",1398711188,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wwi2e2vktmnorzseurla,task_subcomment,NA
+"VisualEditor: VE ""edit"" link in section edit links of a remote file tries to create a new page on local wiki, not remote section","Change 130082 had a related patch set uploaded by Alex Monk:
+Don't change section edit links on foreign file description pages
+
+https://gerrit.wikimedia.org/r/130082",1398697756,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wwi2e2vktmnorzseurla,task_subcomment,NA
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"**Author:** `swalling`
+
+**Description:**
+Screenshot
+
+If you start ?tour=firstedit and then click veaction=edit, you get the wikitext-related Preview step unattached (see screenshot).
+
+This is a low priority issue, because users should only be getting the wikitext 'firstedit' tour if VE is not available. I am filing just in case the opposite situation might happen, i.e. users start a ?tour=vefirstedit, click Edit source, then get the VE tour step. If that's impossible, then this can be ignored for now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11439}",1379459220,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-7sgyl2imvttq6da7zqhg,task_description,open
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"If you look at firstedit tour definition, you'll see that shouldSkip is set to call isEditing() Calling gt.isEditing() checks to see if you are either editing with wikitext or if the VisualEditor is loaded.  However the tour step loads before ve is actually loaded.
+
+IMO: isEditing needs to return true if VisualEditor is loading or loaded.  
+Locally this fixes the bug for me.  I probably will make a patch for this.",1399496465,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-7sgyl2imvttq6da7zqhg,task_subcomment,NA
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"Change 84735 had a related patch set uploaded by Mattflaschen:
+Declare tour as requiring wikitext, but it doesn't work yet.
+
+https://gerrit.wikimedia.org/r/84735",1379495165,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7sgyl2imvttq6da7zqhg,task_subcomment,NA
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"I was wrong about it being an easy fix.  As far as I can tell, this never worked (wikitext tours not being loaded for VisualEditor).  There are two different scenarios, which don't work for different reasons.
+
+However, it will work in the other direction (which is probably why I didn't catch this bug earlier): If it's a VE tour it will not show in the wikitext editor.
+
+I will fix this properly, but it looks like it may require some refactoring to do right.",1379495139,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-7sgyl2imvttq6da7zqhg,task_subcomment,NA
+Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step,"Oh, I forgot the showConditionally.  This is a trivial fix, and I'll do it tonight.",1379459453,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-7sgyl2imvttq6da7zqhg,task_subcomment,NA
+Tech metrics missing IRC channels,"Currently there are only 4 IRC channels being scanned at 
+
+http://korma.wmflabs.org/browser/irc-repos.html
+
+https://meta.wikimedia.org/wiki/IRC/Channels#MediaWiki_and_technical contains the list of tech channels
+
+#pywikipediabot should be added as well in order to keep consistency with https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1379440500,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_description,resolved
+Tech metrics missing IRC channels,Thanks! Closing.,1445360976,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Ok, channels are updated.
+
+Having a JSON file with the list of channels and log place would be awesome :).
+
+@Aklapper, from my side feel free to close the task if you prefer to have further discussion about automation in another ticket.",1445360460,PHID-USER-kiwupwbdc2fe6dzsojnq,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Also note my last comment at https://github.com/benapetr/wikimedia-bot/pull/49#issuecomment-149596883
+It would be trivial for this to all be in json format too but I would leave that for @petrb to implement!",1445354068,PHID-USER-u7w6n5ecde66oujx33pe,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1735259, @Aklapper wrote:
+>>>! In T56230#1734947, @Dicortazar wrote:
+>> is there a way to automatically retrieve the list of available channels?.
+> 
+> for ""automatically retrieve the list of channels **which are logged by wm-bot**"" I have asked its maintainer and will update this task once I've received an answer.
+
+<addshore> the list is not on github! You manage the setting per channel through the bot!
+<addshore> http://bots.wmflabs.org/~wm-bot/dump/systemdata.htm
+<addshore> that has all of the info on it, updated every 20 mins
+<addshore> there isn't a structured form currently though",1445353892,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1737513, @Qgil wrote:
+> Do we need to remove deprecated channels?
+
+No, so I've canceled https://github.com/Bitergia/mediawiki-repositories/pull/8
+
+>>! In T56230#1736157, @Dicortazar wrote:
+> we just need to add the listed channels in that irc_channels.conf file and we would be done here :).
+
+Awesome! Feel free to close this longstanding task after merging https://github.com/Bitergia/mediawiki-repositories/pull/9
+
+We (I?) can create separate tasks to discuss whether to get certain channels logged by wm-bot (""mediawiki-i18n"", ""mediawiki-parsoid"", ""mediawiki-scripts"", ""wikimedia-cep"", ""wikimedia-design"", ""wikimedia-ect"", ""wikimedia-perf"", ""wikimedia-qa"", ""wikimedia-search"", ""pywikibot"") and after deciding, getting them added to korma later.",1445331981,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"This depends on your needs. I mean, as we're not automatically retrieving IRC channels information, we can keep as many channels as you want.
+
+The irc_channels.conf file is more a place to centralize requirements from Korma than an automated place to retrieve IRC info. On the other hand, as we successfully automated Gerrit projects, the Gerrit .conf file is a place where automatically info is updated, added and removed.",1445329859,PHID-USER-kiwupwbdc2fe6dzsojnq,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Do we need to remove deprecated channels? Isn't their information useful to
+count contributions of related users in those channels?",1445329360,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"@Aklapper, what I've done so far is to manually add them to the infrastructure (this is indeed a script deleting, removing, adding URLs, tar.gz, etc) and I wanted to add that list of TRACKED channels once the process if finished and correct (still running).
+
+And yes, as you comment, we just need to add the listed channels in that irc_channels.conf file and we would be done here :).",1445286147,PHID-USER-kiwupwbdc2fe6dzsojnq,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1735971, @Dicortazar wrote:
+> Based on info provided by @Aklapper, I've added all of them
+
+Thank you. 
+I think we're cool with this list for now; adding any further potential channels would first require making them logged on the Wikimedia side of things.
+
+@Dicortazar: For my understanding of the infrastructure: where did you ""add"" them? Any URL to some public diff? I guess the next and last step for one of us is to provide a pull request to `mediawiki-repositories/irc_channels.conf` adding those TRACKED channels and after merging that pull request we are done here?",1445284658,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Based on info provided by @Aklapper, I've added all of them, but mediawiki that was already in the list.
+
+So, the list is as follows:
+
+* ""mediawiki"": TRACKED
+* ""mediawiki-i18n"": 
+* ""semantic-mediawiki"": TRACKED
+* ""mediawiki-parsoid"":
+* ""mediawiki-visualeditor"": TRACKED
+* ""mediawiki-scripts"":
+* ""wikimedia-tech"": TRACKED
+* ""wikimedia-dev"": TRACKED
+* ""wikimedia-toolserver"": TRACKED
+* ""wikimedia-labs"": TRACKED
+* ""wikimedia-labs-nagios"":
+* ""wikimedia-ai"": TRACKED
+* ""wikimedia-analytics"": TRACKED
+* ""wikimedia-cep"":
+* ""mediawiki-core"": TRACKED
+* ""wikimedia-collaboration"": TRACKED
+* ""wikimedia-databases"": TRACKED
+* ""wikimedia-design"":
+* ""wikimedia-ect"":
+* ""wikimedia-fundraising"": TRACKED
+* ""wikimedia-mobile"": TRACKED
+* ""wikimedia-multimedia"": TRACKED
+* ""wikimedia-operations"": TRACKED
+* ""wikimedia-perf"":
+* ""wikimedia-qa"":
+* ""wikimedia-releng"": TRACKED
+* ""wikimedia-research"": TRACKED
+* ""wikimedia-search"":
+* ""wikimedia-teampractices"": TRACKED
+* ""huggle"": TRACKED
+* ""pywikibot"":
+* ""wikidata"" TRACKED",1445281870,PHID-USER-kiwupwbdc2fe6dzsojnq,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1734947, @Dicortazar wrote:
+> I'll close that pull request since the place to add/remove repositories takes place at https://github.com/Bitergia/mediawiki-repositories
+
+Thanks! Good to know.
+
+> On the other hand, is there a way to automatically retrieve the list of available channels?.
+
+I'm afraid that technically speaking the answer is no. However for ""automatically retrieve the list of channels **which are logged by wm-bot**"" I have asked its maintainer and will update this task once I've received an answer.
+
+> Finally, the list of updated repos analyzed by Korma are found at http://korma.wmflabs.org/browser/data/json/irc-repos.json
+
+""wikimedia-toolserver"" is irrelevant nowadays, I've created https://github.com/Bitergia/mediawiki-repositories/pull/8 to remove it.
+
+> For the rest of the non TRACKED IRC channels, there's missing information in some cases at https://meta.wikimedia.org/wiki/IRC/Channels about where the logs are stored.
+
+Taking the list of channels which are not listed in our configuration yet, and which I'd be interested in, and which I could find public logs for in folders which saw recent updates:
+* ""mediawiki"" - https://bots.wmflabs.org/~wm-bot/logs/%23mediawiki/
+* ""mediawiki-visualeditor"" - https://bots.wmflabs.org/~wm-bot/logs/%23mediawiki-visualeditor/
+* ""wikimedia-ai"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-ai/
+* ""mediawiki-core"" - https://bots.wmflabs.org/~wm-bot/logs/%23mediawiki-core/
+* ""wikimedia-collaboration"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-collaboration/
+* ""wikimedia-databases"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-databases/
+* ""wikimedia-multimedia"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-multimedia/
+* ""wikimedia-releng"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-releng/
+* ""wikimedia-research"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-research/
+* ""wikimedia-teampractices"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-teampractices/
+* ""wikidata"" - https://bots.wmflabs.org/~wm-bot/logs/%23wikidata/
+
+Removing myself as assignee here as I don't know how the ""grab those logs"" infrastructure works exactly.",1445272505,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"And regarding to the rest of IRC channels. Do we have logs for all of them?
+
+The following ones were the ones added in the GitHub change:
+
+* ""mediawiki"": TRACKED
+* ""mediawiki-i18n"": 
+* ""semantic-mediawiki"": TRACKED
+* ""mediawiki-parsoid"":
+* ""mediawiki-visualeditor"":
+* ""mediawiki-scripts"":
+* ""wikimedia-tech"": TRACKED
+* ""wikimedia-dev"": TRACKED
+* ""wikimedia-toolserver"": TRACKED
+* ""wikimedia-labs"": TRACKED
+* ""wikimedia-labs-nagios"":
+* ""wikimedia-ai"":
+* ""wikimedia-analytics"": TRACKED
+* ""wikimedia-cep"":
+* ""mediawiki-core"":
+* ""wikimedia-collaboration"":
+* ""wikimedia-databases"":
+* ""wikimedia-design"":
+* ""wikimedia-ect"":
+* ""wikimedia-fundraising"": TRACKED
+* ""wikimedia-mobile"": TRACKED
+* ""wikimedia-multimedia"":
+* ""wikimedia-operations"": TRACKED
+* ""wikimedia-perf"":
+* ""wikimedia-qa"":
+* ""wikimedia-releng"":
+* ""wikimedia-research"":
+* ""wikimedia-search"":
+* ""wikimedia-teampractices"":
+* ""huggle"": TRACKED
+* ""pywikibot"":
+* ""wikidata""
+
+For the rest of the non TRACKED IRC channels, there's missing information in some cases at https://meta.wikimedia.org/wiki/IRC/Channels about where the logs are stored.",1445267841,PHID-USER-kiwupwbdc2fe6dzsojnq,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"I've commented on the GitHub repo.
+
+As a summary: I'll close that pull request since the place to add/remove repositories takes place at https://github.com/Bitergia/mediawiki-repositories
+
+On the other hand, is there a way to automatically retrieve the list of available channels?.
+
+Finally, the list of updated repos analyzed by Korma are found at http://korma.wmflabs.org/browser/data/json/irc-repos.json, but there are some more than the initial four: ""wikimedia-operations"", ""mediawiki"", ""wikimedia-dev"", ""wikimedia-labs"", ""wikimedia-mobile"", ""wikimedia-toolserver"", ""wikimedia-tech"", ""wikimedia-analytics"", ""wikimedia-fundraising"", ""semantic-mediawiki"", ""huggle""
+",1445265939,PHID-USER-kiwupwbdc2fe6dzsojnq,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1557951, @Dicortazar wrote:
+> I'll check that list and update those channels in Korma.
+
+@Dicortazar: Clean pull request now in https://github.com/Bitergia/mediawiki-dashboard/pull/62",1443943426,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"(let's keep the discussion of this task focused on IRC channels, not mixing it with code repositories)",1440097412,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Thanks for this update!
+
+I'll check that list and update those channels in Korma.
+
+@Dzahn and @Aklapper, I'm still working on the feature to automate the list of repositories to be tracked by Korma at {T104845}. In summary this will provide a list of repositories per data source and a black list for each of them.
+
+Thus, anyone interested in tracing new repositories or in adding some of them to the black list, should modify such lists and pull request a change.
+
+A first version of the files are available at GitHub in https://github.com/Bitergia/mediawiki-repositories. Those are old versions, so we shouldn't change those a lot.
+
+So, if we keep that workflow, @Aklapper, my suggestion is to add a new config file to the GitHub repo (irc_channels.conf) with the correct list of repositories (sorted). I can do this in any case with the new list you provided. This will help to centralized those lists of repos.
+
+Comments are welcome in any case :). It's a bit complex task to automate and trace repositories, but this could be an interesting feature for all of us :).",1440091921,PHID-USER-kiwupwbdc2fe6dzsojnq,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"So that updated list would be https://github.com/Bitergia/mediawiki-dashboard/pull/59/files (and obviously my GitHub workflow skills are still improvable, sigh)",1440085780,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,">>! In T56230#1443372, @Dzahn wrote:
+> How do you add channels to korma?
+
+Editing `/browser/data/json/irc-repos.json` in https://github.com/Bitergia/mediawiki-dashboard",1436531313,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,How do you add channels to korma?,1436481722,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Once {T96371} is closed, we may want to work on this task again.
+
+We can discuss this during this Friday conf call and leave it as June task.",1432652217,PHID-USER-kiwupwbdc2fe6dzsojnq,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,%%%*** Bug 60079 has been marked as a duplicate of this bug. ***%%%,1395751080,PHID-USER-lepsd737p6wqwsowcou2,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,IRC channels are not that critical. Normal priority.,1380233157,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Ooops, actually Nemo is (again) right:
+
+https://meta.wikimedia.org/wiki/IRC/Channels#MediaWiki_and_technical
+https://meta.wikimedia.org/wiki/IRC/Channels#Tools",1379541015,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"Check the URL above. I'm proposing only the ""MediaWiki and technical"" section plus #pywikipediabot",1379513170,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+Tech metrics missing IRC channels,"There are 261 Wikimedia IRC channels. We want to gather all those channels?
+
+I think it is not a big issue to configure and implement it, but it could be an important delay and resource consuming in the update process because logs are included in one big file per channel and the incremental support can not be implemented.
+
+http://bots.wmflabs.org/~wm-bot/logs/
+
+Is there any other place with logs for IRC channels?",1379498684,PHID-USER-lepsd737p6wqwsowcou2,False,PHID-TASK-ylv5ntuga7adnifnjbdx,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"InstantCommons does not work on Vagrant if you enable the 404 handler for images (the `thumb_on_404` role does that and most multimedia roles include it). The problem is related to thumbnail caching; similar to T101565, but the default wiki (`127.0.0.1`) is also affected.
+
+As a workaround, caching can be disabled by creating `/vagrant/settings.d/10-DisableThumbnailCaching.php` with
+```
+<?php
+$wgUseInstantCommons = false;
+$wgForeignFileRepos[] = array(
+	'class' => 'ForeignAPIRepo',
+	'name' => 'wikimediacommons',
+	'apibase' => 'http://commons.wikimedia.org/w/api.php',
+	'fetchDescription' => true,
+	'descriptionCacheExpiry' => 0,
+	'apiThumbCacheExpiry' => 0,
+);
+```
+",1379384100,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_description,resolved
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Please reopen or file a new bug if you can reproduce.,1468099239,PHID-USER-ll6tmaogat2b5q7tnqas,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,IIRC yes but much harder to trigger than it used to be. But I'm may be wrong - I only vaguely remember what this was about.,1457652757,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,@Tgr is this still an ongoing problem?,1457644136,PHID-USER-ll6tmaogat2b5q7tnqas,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223480 abandoned by Gergő Tisza:
+Use 404 handler for all wikis when the role is enabled
+
+Reason:
+There doesn't seem to be a way to do this correctly.
+
+[[https://gerrit.wikimedia.org/r/223480]]",1436559679,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223493 merged by jenkins-bot:
+Fix thumb on 404 role for multiwiki reality
+
+[[https://gerrit.wikimedia.org/r/223493]]",1436391322,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223477 merged by jenkins-bot:
+Fix thumb rewrite rules
+
+[[https://gerrit.wikimedia.org/r/223477]]",1436327387,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223493 had a related patch set uploaded (by BryanDavis):
+Fix thumb on 404 role for multiwiki reality
+
+[[https://gerrit.wikimedia.org/r/223493]]
+",1436327281,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223480 had a related patch set uploaded (by Gergő Tisza):
+Use 404 handler for all wikis when the role is enabled
+
+[[https://gerrit.wikimedia.org/r/223480]]
+",1436318919,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Change 223477 had a related patch set uploaded (by Gergő Tisza):
+Fix thumb rewrite rules
+
+[[https://gerrit.wikimedia.org/r/223477]]
+",1436317320,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"From the Apache docs:
+> REQUEST_FILENAME
+> The full local filesystem path to the file or script matching the request, if this has already been determined by the server at the time REQUEST_FILENAME is referenced. Otherwise, such as when used in virtual host context, the same value as REQUEST_URI. Depending on the value of AcceptPathInfo, the server may have only used some leading components of the REQUEST_URI to map the request to a file.
+
+So apparently the problem is that Apache does not map the URI to the filesystem path before checking whether the file exists. If I disable the rewrite rule, the thumbnail appears correctly.",1436316316,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Probably even more broken on other wikis since the 404 handler config rule seems to only be applied to the default wiki (and the one created by the `commonswiki` role which has its own apache rules).,1436313920,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Contents of `/etc/apache2/site-confs/devwiki/50-thumb-php-on-404.conf`:
+```
+RewriteEngine On
+
+# call thumb.php for thumb images not on disk
+RewriteCond %{REQUEST_FILENAME} !-f
+RewriteCond %{REQUEST_FILENAME} !-d
+RewriteRule ^/images/thumb/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/[^/]*([0-9]+)px-.*$ /w/thumb_handler.php [PT,QSA,B]
+
+
+# call thumb.php for thumb archive images not on disk
+RewriteCond %{REQUEST_FILENAME} !-f
+RewriteCond %{REQUEST_FILENAME} !-d
+RewriteRule ^/images/thumb/archive/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/[^/]*([0-9]+)px-.*$ /w/thumb_handler.php [PT,QSA,B]
+```
+
+Contents of `/etc/apache2/site-confs/devwiki/50-devwiki-images.conf`:
+```
+# vim: filetype=apache sts=4 sw=4 autoindent
+#
+# This file is managed by Puppet.
+#
+<Directory /srv/images>
+    Require all granted
+    Header set Access-Control-Allow-Origin ""*""
+</Directory>
+
+Alias /images /srv/images
+```
+
+Apache log with `LogLevel alert rewrite:trace6`:
+```
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace2] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] init rewrite engine with requested uri /images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg, referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace3] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] applying pattern '^/$' to uri '/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg', referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace3] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] applying pattern '^/images/thumb/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/[^/]*([0-9]+)px-.*$' to uri '/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg', referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace4] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] RewriteCond: input='/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg' pattern='!-f' => matched, referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace4] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] RewriteCond: input='/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg' pattern='!-d' => matched, referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace2] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] rewrite '/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg' -> '/w/thumb_handler.php', referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+Jul  7 23:56:57 mediawiki-vagrant apache2[6545]: [rewrite:trace2] [pid 6545] mod_rewrite.c(468): [client 10.0.2.2:56986] 10.0.2.2 - - [127.0.0.1/sid#7f720dfb0bb8][rid#7f720decc0a0/initial] forcing '/w/thumb_handler.php' to get passed through to next API URI-to-filename handler, referer: http://127.0.0.1:10000/wiki/File:Sunrise_over_fishing_boats_in_Kerala.jpg
+```
+
+The thumbnail is at `/srv/images/thumb/b/b0/Sunrise_over_fishing_boats_in_Kerala.jpg/800px-Sunrise_over_fishing_boats_in_Kerala.jpg`. I don't get why the `!-f` rule matches, somehow the alias does not get applied?",1436313779,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Still (or again) broken. Commons API is used without a problem, the image is thumbnailed, but Apache redirects the request to `thumb.php` even though the thumbnail exists and seems to be in the right place. (`thumb.php` cannot handle remote images, that's T27958.)",1436313023,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Can't reproduce this anymore. https://gerrit.wikimedia.org/r/217769 might have fixed it.,1435366189,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Same for me. This is actually impacting my ability to code review certain changes... :-/,1435087748,PHID-USER-5dwuaigmkz2vzg65lape,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Enabling the multimedia role on a fresh MW-Vagrant box still produces broken thumbnails for me. (""//Error generating thumbnail: The source file 'XXX' does not exist.//"")",1419909145,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"@Eloquence, @tgr Is this still a problem?",1419899284,PHID-USER-ll6tmaogat2b5q7tnqas,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,Bulk unassigning bugs from Ori.,1416260174,PHID-USER-ll6tmaogat2b5q7tnqas,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"In the latest MediaWiki Vagrant with the multimedia role enabled, InstantCommons does not successfully generate thumbnails for me. The issue goes away if I comment out the thumb-php-on-404 handler, so I suspect it's an issue with the rewrite rule. CCing Bryan since he wrote that template.",1401153590,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"I can confirm that Gergo's workaround does the trick, even for a Vagrant newbie like me.
+
+So even if we can't fix this in code right away, at least we have a solution for making this work temporarily.
+
+Thanks for this!",1394693207,PHID-USER-dbudsaorcqut7sg3vvbi,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Bawolff: I could reproduce this with the multimedia vagrant role enabled, which in theory should enable 404-based image handling.",1394665838,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Workaround:
+
+<?php
+$wgUseInstantCommons = false;
+$wgForeignFileRepos[] = array(
+    'class' => 'ForeignAPIRepo',
+    'name' => 'wikimediacommons',
+    'apibase' => 'http://commons.wikimedia.org/w/api.php',
+    'fetchDescription' => true,
+    'descriptionCacheExpiry' => 0,
+    'apiThumbCacheExpiry' => 0,
+);
+
+I started to track this down some weeks ago but ran out of time and had to give up. The issue was MediaWiki getting confused about which local directory to use for the thumb cache IIRC.",1394665237,PHID-USER-a6p24cvyblhfzc7we7nc,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"This is a known issue of using thumb.php directly instead of from a 404 handler. (Not sure how ""known"" in any case, not new)",1380304952,PHID-USER-dpu5hmqvprhycqlkdzrk,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+InstantCommons no longer working in MediaWiki-Vagrant multimedia role,"Oddly, if I insert an image from Commons through VisualEditor it appears to work ok inline.
+
+If I insert one in source, I get ""Error creating thumbnail: Invalid thumbnail parameters"".
+
+whaaaaaat?",1380304811,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-ujchhacr3p2gtsdgmxlg,task_subcomment,NA
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter","(Hopefully other reporters will improve the title and description if necessary!)
+The French Wikipedia has a number of templates which usually ask for some kind of clarification about a whole passage of text (see https://fr.wikipedia.org/wiki/Mod%C3%A8le:Refnec#Exemples ).
+So users are asking that, when they select that text and launch the template inspector, the text is already recognized as a ""parameter"" for that template.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379367180,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_description,open
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter",I think a better way to solve this would be to somehow allow templates to be treated as 'annotations' in VE (like bold style or links).,1403885820,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_subcomment,NA
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter","This feature would be very helpful for other common templates in articles. For example, the {{Colonnes}} template on French wiki, or its equivalent {{columns-list}} template on English wiki to put text/lists on several columns.
+
+https://en.wikipedia.org/wiki/Template:Columns-list",1379522740,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_subcomment,NA
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter","I think it's not only the French wiki that may use this... On English wiki, the equivalent of {{Refnec}} and its ""1"" parameter is {{Citation needed span}} and its ""text"" parameter.
+
+Maybe a way of implementing this would be the following :
+* Add an information in TemplateData to be able to tell which parameter should be initialized with the selected text
+* When you insert a template with VE, if the TemplateData as such configuration, use the selected text to initialize the parameter",1379367849,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_subcomment,NA
+"VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter",And I think that such a functionality would need to be able to remove the template by replacing it with its first parameter.,1379367567,PHID-USER-5pyvkdz65d5h5vxebodc,True,PHID-TASK-a5fu3pyzxhbjzmz25n7i,task_subcomment,NA
+VisualEditor: Duplicating categories (and possibly also something else),"NicoV reports this diff,
+https://fr.wikipedia.org/w/index.php?title=Blood_Lad&diff=96657484&oldid=96506947 .
+Assuming the user deleted the infobox without realizing it, I did not manage to reproduce the duplication of categories inside a reference tag (line 38); if I just copy/paste them they get nowikied, so it shouldn't be a vandalism.  
+
+CCing subbu and gwicke here. T52120 and T54238 come to mind, but I'm not sure if it's really a dupe.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+T54238
+T52120
+T76715
+T89618",1379347920,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_description,resolved
+VisualEditor: Duplicating categories (and possibly also something else),Think this was all fixed,1415881087,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_subcomment,NA
+VisualEditor: Duplicating categories (and possibly also something else),"https://fr.wikipedia.org/w/index.php?title=Bello_de_Carcassonne&diff=107097528&oldid=107091155 duplicated two categories and added others, but not within a ref tag.  It also added a blank (== ==) section heading after the misplaced cats.",1409788705,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_subcomment,NA
+VisualEditor: Duplicating categories (and possibly also something else),"Yes Gabriel, I tried to behave like a vandal :) and wanted to paste templates and categories into the reference, to understand if this was what the user had actually done.
+But as you can see here https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve&diff=96710198&oldid=96710142 my result is different, in that the pasted content generated nowiki tags, so the duplication in the article is not a result of copy/pasting that content into the reference editor.",1379350998,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_subcomment,NA
+VisualEditor: Duplicating categories (and possibly also something else),"(In reply to comment #0)
+> NicoV reports this diff,
+> https://fr.wikipedia.org/w/index.
+> php?title=Blood_Lad&diff=96657484&oldid=96506947
+> .
+> Assuming the user deleted the infobox without realizing it, I did not manage
+> to
+> reproduce the duplication of categories inside a reference tag (line 38); if
+> I
+> just copy/paste them they get nowikied, so it shouldn't be a vandalism.
+
+Can you clarify what you mean with 'just copy/paste them'? Do you mean copy/pasting wikitext into VE?",1379350615,PHID-USER-hbtlbu4zftxnz4i6f7yf,True,PHID-TASK-fn2b4izsi4dcu5lgaxmp,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","Change in MediaWiki:Editing notice to a links does not  parse
+
+Hi,
+
+
+When I tried to add a internal link (related to [[Special:Preferences#mw-prefsection-editing]])  to MediaWiki:Editing, it did not parse as shown in attachment.  
+
+
+*Exact edit  difference which I tried https://mr.wikipedia.org/w/index.php?title=मिडियाविकी%3AEditing&diff=1200554&oldid=44085 the result is shown in the attachment.
+
+
+*The purpose of edit was to request users to give a try to VisualEditor and report input issues . (Issues related to usability of Marathi Devnagari script are very crucial to us )
+
+
+I am not sure whether this a normal limitation of MediaWiki messages  and so not sure whether this will be accepted as a bug.
+
+But still prefered to report this bug since it is simmiller problem of parsing which I observed in Bug no 45195 also and just prefered to keep developers informed.
+
+Thanks and regards
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal
+**Whiteboard**: aklapper-moreinfo
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=45195
+
+**Attached**: {F11186}",1379172900,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-43yopxeqsvyzzvqfuavz,task_description,invalid
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","The issue in comment 0 was about a link not being parsed and instead [[]] is literally shown. My confusion probably arised from the fact that you had changed https://mr.wikipedia.org/w/index.php?title=मिडियाविकी:Editing already, so I asked how to see this problem myself and to provide steps.
+
+MediaWiki:Editing neither exists on en.wp or fr.wp and was removed in 2007.
+
+As the issue was originally about https://mr.wikipedia.org/w/index.php?title=%E0%A4%AE%E0%A4%BF%E0%A4%A1%E0%A4%BF%E0%A4%AF%E0%A4%BE%E0%A4%B5%E0%A4%BF%E0%A4%95%E0%A5%80%3AEditing&diff=1200554&oldid=44085 which is totally wrong HTML I don't see any valid bug reported here.
+
+If the problem still happens with *valid* HTML, please reopen this bug report and link to the revision of MediaWiki:Editing that shows the problem. Thanks.",1379943675,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","Created attachment 13341
+additional example of message MediaWiki:Editing
+
+(In reply to comment #3)
+
+Additional example of how MediaWiki message MediaWiki:Editing works.
+
+**Attached**: {F11189}",1379766935,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","Created attachment 13340
+MediaWiki:Editing example en wikipedia
+
+(In reply to comment #3)
+
+Which language you used for The Tokyo article ? Here is an example from eglish wikipedia
+
+**Attached**: {F11188}",1379766277,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","Created attachment 13332
+Editing The Tokyo article
+
+(In reply to comment #2)
+> *[[MediaWiki:Editing]] message (Current text:Editing $1) is visible at the
+> top of every wiki page when you  are editing any wiki page.
+
+No, not for me.
+
+**Attached**: {F11187}",1379686080,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","(In reply to comment #1)
+> How to see what's on the screenshot? This is missing steps... 
+
+*[[MediaWiki:Editing]] message (Current text:Editing $1) is visible at the top of every wiki page when you  are editing any wiki page.
+
+* So the given screen shot will be visible on all wiki pages while editing if you save the given edit diff https://mr.wikipedia.org/w/index.php?title=मिडियाविकी%3AEditing&diff=1200554&oldid=44085 on any test wiki
+
+
+** (My impression is MediaWiki messages work simmiller to Templates. If template:ABC is having internal link [[PQR]] and template:ABC is included in Template:XYZ usually internal link [[PQR]] of template:ABC will parse through Template:XYZ , What I suppose/doubt is,  If MediaWiki:ABC has internal link  [[PQR]] and MediaWiki:ABC is getting included in MediaWiki:XYZ unlike templates MediaWiki messages are not parsing internal link of another MediaWiki message.That is my pure guess you(Developers) are the right people to inform what is supposed to be expected behaviour for MediaWiki messages,and the reported behaviour is matching with expected behaviour or not)
+
+
+Also, 
+>    <small><small><small /><small /> 
+> does not look like valid HTML to me.
+
+*https://mr.wikipedia.org/w/index.php?title=%E0%A4%AE%E0%A4%BF%E0%A4%A1%E0%A4%BF%E0%A4%AF%E0%A4%BE%E0%A4%B5%E0%A4%BF%E0%A4%95%E0%A5%80:Sitenotice&diff=prev&oldid=1201270 It is the same text parsing through the internal links in different MediaWiki message.
+
+HTML may be having minor issue on layout side but parsing of internal link is different issue I suppose.
+
+Rgds",1379606319,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"""MediaWiki:Editing"" notice did not parse  a link when tried so","How to see what's on the screenshot? This is missing steps... Also, 
+   <small><small><small /><small /> 
+does not look like valid HTML to me.",1379340953,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-43yopxeqsvyzzvqfuavz,task_subcomment,NA
+"Transclusion dialog: ""unknown parameter"" is confusing if TemplateData doesnt exist","If adding w:cs:template:commonscat, it might be confusing for newbies even for older wikipadians to set parameters. As in this case parameters or numbers, but VE sais that such parameters are unknown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50735",1379064360,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-qyjx6fdbrrh3weriir7z,task_description,resolved
+"Transclusion dialog: ""unknown parameter"" is confusing if TemplateData doesnt exist","Merging with bug 50735.
+
+*** This bug has been marked as a duplicate of bug 50735 ***",1381342230,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qyjx6fdbrrh3weriir7z,task_subcomment,NA
+"Transclusion dialog: ""unknown parameter"" is confusing if TemplateData doesnt exist","If I can paraphrase Juan's bug report, ..
+
+In the transclusion dialog, template 'add parameter' screen, for a template without templatedata (such as cs:wp template commonscat),...
+
+Dont say 'Unknown parameter'.
+
+If there is no templatedata, VE doesnt know about any parameters, so it should not offer warnings that are essentially bogus when it is given a parameter name.  The user cant use this 'Unknown parameter' information, so it is scary.  Further to that, VE _does_ know that numeric parameters names (like '1', '2', etc) are valid parameter name, so warning 'Unknown parameter' is false in that case.
+
+Juan, if you want to add templatedata to that template, see https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/TemplateData  and
+https://en.wikipedia.org/w/index.php?title=Template:Commons_category/doc&action=edit
+
+The VE UI for templates without templatedata needs a usability overhaul. Some simple suggestions to improve usability while keeping the current UI structure:
+1. say 'This template does not have VE compatible parameter data', and link to the relevant template:blah page
+2. dont say 'No unused parameters' because that message is also misleading
+3. Instead of 'Unknown parameter' for '1', say 'parameter number 1' or 'first parameter'
+4. pre-populate the template form with a parameter '1', place the user in the parameter value field, but allow the user to rename the parameter name in the left hand list.
+
+A more difficult suggestion is to rethink the way the numbered parameter UI works.  Putting numbers in a UI, without any explanation, is not intuitive or discoverable.  How does a newbie know to enter '1'?  The template documentation pages usually say to put in {{foo|blah}} ; they dont say {{foo|1=blah}} so the typical user doesnt know about '1'.",1380616208,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-qyjx6fdbrrh3weriir7z,task_subcomment,NA
+"Transclusion dialog: ""unknown parameter"" is confusing if TemplateData doesnt exist",The steps to reproduce are unclear to me. Also see https://www.mediawiki.org/wiki/How_to_report_a_bug,1379323419,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-qyjx6fdbrrh3weriir7z,task_subcomment,NA
+VisualEditor: Zero width no-break space is added to the end of the article (in a slug) in the editing element (but not the document),"I am trying to run the test at https://gerrit.wikimedia.org/r/#/c/83966/
+
+In the end it is trying to compare the text that was typed with the text that actually appears on the screen. The test fails, because the Zero width no-break space (U+FEFF) character is added to the string that appears on the screen.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378949100,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-mgmwirwldz45agzrgg3n,task_description,open
+VisualEditor: Zero width no-break space is added to the end of the article (in a slug) in the editing element (but not the document),Presumably this is ve.ce.BranchNode.$blockSlugTemplate.,1406595885,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mgmwirwldz45agzrgg3n,task_subcomment,NA
+Autocomplete for (local) image names,"It'd be nice if WikiLove had a javascripty autocomplete for image names (at least local ones)
+
+--------------------------
+**Version**: master
+**Severity**: enhancement",1378778340,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-ta7jealrbrncqvj3zzez,task_description,open
+Autocomplete for (local) image names,"(In reply to comment #1)
+> Any possibility of sharing a UI module with VisualEditor here, rather than
+> having two implementations of a media selection browser?
+
+Works for me. Though, ideally would go into core. WikiLove (optionally) depending on VisualEditor could be a potential problem
+
+MassMessage has a simple similar implementation of this, with based on resources/mediawiki/mediawiki.searchSuggest.js in core",1378840970,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-ta7jealrbrncqvj3zzez,task_subcomment,NA
+Autocomplete for (local) image names,"Any possibility of sharing a UI module with VisualEditor here, rather than having two implementations of a media selection browser?",1378839938,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-ta7jealrbrncqvj3zzez,task_subcomment,NA
+Reduce VisualEditor's memory usage,"Editing of large pages can use a significant amount of memory; a spotcheck that Max did on [[United States]] showed an increase of 121MB usage in Chrome while editing the page.
+
+This is a concern for us for mobile in particular, as today's mobile devices have the amount of memory of computers from several years ago -- most have 1GB or 512MB (or even less), which has to house the operating system, background apps, the web browser, and the *entire* article with a richly annotated DOM.
+
+Possible techniques for reducing memory usage were proposed at the VE mobile meeting yesterday:
+
+* Section editing -- if we only have to load up a single section at a time, large pages won't use up nearly as much memory. Note that on mobile we already divide the page up into sections surrounded by <div>s that can be replaced with the editable surface; the other sections on page might not even be open.
+
+* Limit full annotation processing to areas under active editing -- apparently it should be possible to delay some of the HTML processing on sections or even paragraphs that have not yet been edited. This might also save memory, but needs to be looked into.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378411260,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-aag3cwflmkojbhxxal5q,task_description,open
+Reduce VisualEditor's memory usage,"This is a high-level tracker bug rather than a blocker; it needs child bugs with more specifics to be nominated as blockers. Consequently, we decided to remove it from the Q3 blockers list at the triage on 2015-02-11.",1423879177,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,"More specific criteria and numbers are welcome / required here.
+Also, should the ""Epic"" tag be added here?",1423743458,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,">>! In T55825#558826, @brion wrote:
+> Feel free to move this to 'general' and we'll hang some mobile-specific bugs off it that are more directly actionable.
+
+Have any mobile-specific bugs been identified since 09/2013? Adding task numbers is welcome.",1423686484,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,"(In reply to comment #2)
+> Feel free to move this to 'general' and we'll hang some mobile-specific bugs
+> off it that are more directly actionable.
+
+{{Done}}",1378416264,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,Feel free to move this to 'general' and we'll hang some mobile-specific bugs off it that are more directly actionable.,1378415457,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+Reduce VisualEditor's memory usage,"Not sure this is a Mobile-specific bug, but yes, very important to make progress here. I think there's likely to be some produce trade-offs that are more appropriate for the Mobile than Desktop experience, though, so certainly some of it will be…",1378414642,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-aag3cwflmkojbhxxal5q,task_subcomment,NA
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),"Users seem to expect that the feedback link will automatically supply information, especially the title of the article they're working on.  I'd also like to have the version number they were actually using (cacheing issues) and a link to the user's contibutions.
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: enhancement",1378397100,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-dyxvwjhctefty5l6omxi,task_description,open
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),"The core feedback tool is (I think intentionally) very generic. If VE needs additional functionality, it should probably extend it.",1383301933,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-dyxvwjhctefty5l6omxi,task_subcomment,NA
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),The feedback tool isn't specific to VisualEditor - moving to the general group for others to see and comment.,1383281154,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dyxvwjhctefty5l6omxi,task_subcomment,NA
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),"(In reply to comment #1)
+> Google has a feedback tool for Google+ which lets you ""screenshot"" the page
+> you
+> are on and highlight what you think is wrong. Something like that would be
+> really cool.
+
+That would be good, but possibly a bit more complicated for us. I wrote [[Wikipedia:Screenshots of Wikipedia]] to help people include screenshots in on-wiki bug reports, so linking prominently to that would be a very easy first step.",1380546133,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-dyxvwjhctefty5l6omxi,task_subcomment,NA
+[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions),"Google has a feedback tool for Google+ which lets you ""screenshot"" the page you are on and highlight what you think is wrong. Something like that would be really cool.",1378408265,PHID-USER-bug3zrlooz3bdmi4fyl7,True,PHID-TASK-dyxvwjhctefty5l6omxi,task_subcomment,NA
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","Right now external paste always writes the clipboard as formatted; in some cases, users will want to ""Paste Unformatted"".
+
+On Mac, there's a standard shortcut for this of Cmd+Shift+V - I'm assuming that Ctrl+Shift+V would be sensible as well.
+
+Would we also need a button? What about for the other standard 3 (Cut/Copy/Paste)?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378335600,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2uz6thdqdeegj4cxnbup,task_description,resolved
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","Change 88224 merged by jenkins-bot:
+Plain text paste with paste special
+
+https://gerrit.wikimedia.org/r/88224",1385500068,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2uz6thdqdeegj4cxnbup,task_subcomment,NA
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","Change 88224 had a related patch set uploaded by Esanders:
+Plain text paste with paste special
+
+https://gerrit.wikimedia.org/r/88224",1381178929,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-2uz6thdqdeegj4cxnbup,task_subcomment,NA
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","(In reply to comment #1)
+> ctrl+shift+v in Open Office is ""paste special"", which gives lots of
+> non-default
+> options so it doesn't seem out of line. Not sure a separate button is needed
+> but if button=shortcut then shift+button should = shift+shortcut
+
+We don't need a button to have a shortcut (but we do for users without a keyboard, or with a limited keyboard that can't do shortcuts, like tablet users).
+
+> In general I think its best to cut/copy richly to the clipboard and let the
+> target deal with the formatting. I don't know whether this view is common or
+> uncommon though,
+
+I agree personally, but people have asked for it a few times and it's a not-hard change for us to make when pasting from the clipboard.",1378337286,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2uz6thdqdeegj4cxnbup,task_subcomment,NA
+"VisualEditor: Insert external pasted content as ""unformatted"" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger","ctrl+shift+v in Open Office is ""paste special"", which gives lots of non-default options so it doesn't seem out of line. Not sure a separate button is needed but if button=shortcut then shift+button should = shift+shortcut
+
+In general I think its best to cut/copy richly to the clipboard and let the target deal with the formatting. I don't know whether this view is common or uncommon though,",1378336500,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-2uz6thdqdeegj4cxnbup,task_subcomment,NA
+"VisualEditor: On opening a reference which includes a single template and nothing else, also open that template's dialog","When you open an existing reference in VE that only consists of one template the main use case should be that you want to edit that template. But now you need to first select it and then klick on the puzzle piece.
+
+Instead I suggest that in that case, you get forwarded to the template editor directly after choosing to open the reference editor without having to do it manually.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1378220100,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-jldo3wo4jenhs2iglbfo,task_description,resolved
+"VisualEditor: On opening a reference which includes a single template and nothing else, also open that template's dialog",This was done (for citation templates) in the new citation system.,1401472643,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jldo3wo4jenhs2iglbfo,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"The VisualEditor and ULS MediaWiki extensions have recently been blessed with QA browser tests.  We would need them to be in the Contint Jenkins and triggered by Zuul whenever a patchset is submitted as well as in the gate-and-submit pipeline.
+
+That needs several step:
+
+- describe the jobs in Jenkins
+- add the triggers in Zuul configuration
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1378194900,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_description,resolved
+[EPIC] trigger browser tests from Gerrit (tracking),As far as I know this is resolved a long time ago. Please reopen if there is anything left to be done.,1496054383,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Have to make the following extension to trigger the job on patchset proposal:
+
+CentralAuth
+CentralNotice
+Math
+PageTriage
+WikiLove
+",1488879529,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Change 341506 merged by jenkins-bot:
+[integration/config] Add experimental mwext-mw-selenium-jessie
+
+[[https://gerrit.wikimedia.org/r/341506]]
+",1488877980,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Change 341506 had a related patch set uploaded (by hashar):
+[integration/config] Add experimental mwext-mw-selenium-jessie
+
+[[https://gerrit.wikimedia.org/r/341506]]
+",1488877553,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"@dduvall made it possible to trigger selenium tests when a new patchset is triggered which unblocked a few tasks.
+
+Originally we had this blocked on T47499 which comes from Bugzilla and was the parent tracking task / epic for the #continuous-integration-scaling project.  It has progressed and we are not so far from having the jobs run on Nodepool.  That is {T137112} which is more specific than the legacy epic task and better reflect the intention.",1465249476,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"For mediawiki/extensions/VisualEditor no browser tests are run for patch upload nor merge, so it probably still needs to be done, possibly also for a few other closed blockers.",1450969250,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),">>! In T55697#1646493, @Jdlrobson wrote:
+> The description is a little confusing. Does VisualEditor do this already? I can't see the selenium job on a per commit basis....
+
+Still interested in the answer to this.
+",1450907160,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),The description is a little confusing. Does VisualEditor do this already? I can't see the selenium job on a per commit basis....,1442430477,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),I have closed a few tasks that were requesting browser tests to be triggered on patch proposal. There is no point in keeping them open until we are actually ready to trigger such jobs.,1427208701,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Per a discussion we had in the Releng weekly checkin, triggering browser tests from Gerrit would need the disposable VMs. We would also need to setup MediaWiki and the required backend services such as Parsoid (and more as needed).",1424944811,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"(In reply to Matthew Flaschen from comment #7)
+<snip>
+> What's the status of this?  Are there any projects that have browser tests
+> triggering on each change (even if non-voting)?
+> 
+> If not, can you outline the blockers?
+
+It is not hold, mostly because we lack resources to do the integration / make them faster.  On top of my head:
+
+* make them faster
+* runnable in parallel and aggregate the results
+* rethink the way we setup the environment to run the browser tests, it is currently a huge shell snippet which is copy pasted in different place
+
+
+Feel free to take the leadership. Zeljkof and Nik Everett would be able to assist.  I can offer reviews / guidances as well.",1415887484,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"(In reply to Antoine ""hashar"" Musso from comment #6)
+> This is no more a top priority.  We have most browsertests run twice per day
+> instead.
+> 
+> We will eventually managed to get them added in Gerrit, but there is a bit
+> more work that needs to be done first.
+
+What's the status of this?  Are there any projects that have browser tests triggering on each change (even if non-voting)?
+
+If not, can you outline the blockers?",1412275069,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"This is no more a top priority.  We have most browsertests run twice per day instead.
+
+We will eventually managed to get them added in Gerrit, but there is a bit more work that needs to be done first.",1405076783,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"Quick status update:
+
+- ULS has browser tests being triggered albeit lot of tests ends up being
+- MobileFrontend has a patch that has browser tests passing locally against a freshly installed wiki. Pending review / merge then I will add the browser tests.
+- VisualEditor browser tests depends on some work to be done to safely start and stop a Parsoid daemon for each test.
+
+I am focusing this week on integrating Parsoid daemon in Jenkins",1386705460,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),The Jenkins jobo template in https://gerrit.wikimedia.org/r/#/c/86868/ would let us trigger tests.,1385379924,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),See also the Wiki page https://www.mediawiki.org/wiki/Continuous_integration/Browser_tests,1379694650,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),We will go with ULS first since we have a good experience interacting with the i18n team and they are in European timezone just like Zeljko and I.,1378225513,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+[EPIC] trigger browser tests from Gerrit (tracking),"raise priority, add 'tracking' in summary.",1378225359,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-jzpbyio6ibhoo7ft5azi,task_subcomment,NA
+VIsualEditor: Allowing editing of attributes in MWAlienExtensionNode,"Need some UI to add/remove/edit the key value pairs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377906360,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-342y4tkwn6enbyuyqjn3,task_description,open
+VIsualEditor: Allowing editing of attributes in MWAlienExtensionNode,"As an update, this is done for editing, but not adding/removing.",1394479039,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-342y4tkwn6enbyuyqjn3,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, use ""Root#sets"" data to allow addition and/or completion of parameter > sets","
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377905220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bjxf522olmedsdx6rpbc,task_description,open
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Adam Cuerden says,  ""I believe the VE team intends to have a some one click solutions in the near future, including adding templates of your choice to a bar? Although I'd hope there'd also be a few automatic lists you could choose to pull up - cleanup templates, etc.""
+
+So, it would be really comfy for users if the template editor, beyond being able to let them select what they need by typing the name, asked ""Which kind of template do you want to add?"" and provided lists of the most used/popular ones, divided per set (cleanup templates, citation templates and so on).
+Or just a way to store one's most used choices.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T52458}",1377873180,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_description,open
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"T209797 requests a specific subset of this, in a specific format, as part of semi-automated tool interfaces, for wikisource as well as VE.",1732669010,PHID-USER-t5o36keuho36mcmrau5j,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,CommTech is planning to address some of this with [[ https://phabricator.wikimedia.org/T367428  | Favorite Templates ]] ,1729696706,PHID-USER-gijtkzcktagsduwnkeo6,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The infobox could be suggested based on some categories of the article, specifically or generally, for example writer or just biography.",1715092406,PHID-USER-ygejgcs65h5nr3ssbueb,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Editing/Quickly_add_favorite_and_related_templates,1676201310,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/98c44ac3c7/wiki/Main_Page?veaction=edit",1675175353,PHID-USER-jab5bp3ivtzmobfdxoa7,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Editing/Quickly_add_infobox,1675173851,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Editing/Select_templates_by_categories,1606394588,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"CCing WMDE Technical Wishes team (https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Templates)
+
+@ecohen @Lena_WMDE @thiemowmde ",1585845044,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,Any clue on this?,1574156168,PHID-USER-g73uduhwmggntmexighn,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"> Um... A lot of it actually is defined locally on the wiki and won't work without non-trivial JSON configuration that maps it to local templates.
+
+Yes, I'm comparing them to templates that are 100% defined on wiki.
+
+> Infoboxes are very common, but unlike citations they are usually inserted only once when the article is created
+
+Yes, so as an editing tool, no particular template comes close to cite in terms of frequency of use (although I'm sure there are wiki-by-wiki examples where this is the case).
+
+> and VE is for some reason perceived more as a page editing tool than a page creation tool
+
+I don't see it this way either, but edits >> creations.
+
+I think this conversation belongs on T96710.",1558269856,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5192906, @Esanders wrote:
+>>>! In T55590#5192101, @Amire80 wrote:
+>> There is no good reason for this differentiation. Many templates could be first-class features like ""Cite"", although global templates should probably implemented first.
+> 
+> I think the distinction at the moment is that the Cite tools relate to extension functionality defined in the code, specifically templates wrapped in a <ref>, and the Citoid tool allows automatic population of those templates.
+
+Um... A lot of it actually //is// defined locally on the wiki and won't work without non-trivial JSON configuration that maps it to local templates.
+
+My theory is that Cite got its own button because the English Wikipedia community, unlike most others, enforces citations very strongly, and new citations are needed in new edits all the time. Infoboxes are very common, but unlike citations they are usually inserted only once when the article is created, and VE is for some reason perceived more as a page editing tool than a page creation tool. (//I// don't perceive it as such, and I use VE for creating pages whenever I can, but my impression is that a lot of people don't think of VE as a page creation tool.)
+
+> ""Suggested templates"" on the other hand are 100% defined on-wiki: the names of the templates to use, the implementation of the templates, and the metadata, so I think it's appropriate to think about these differently.
+
+Sure, but please do keep in mind that some day, better earlier than later, at least some templates should become global. When this finally happens, we can probably also have global JSON configuration for popular templates.",1558190892,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5192101, @Amire80 wrote:
+> There is no good reason for this differentiation. Many templates could be first-class features like ""Cite"", although global templates should probably implemented first.
+
+I think the distinction at the moment is that the Cite tools relate to extension functionality defined in the code, specifically templates wrapped in a <ref>, and the Citoid tool allows automatic population of those templates.
+
+""Suggested templates"" on the other hand are 100% defined on-wiki: the names of the templates to use, the implementation of the templates, and the metadata, so I think it's appropriate to think about these differently.
+
+That said there are certainly cases on a wiki by wiki basis where it would make sense to promote certain templates to the toolbar, and that is covered by T96710.
+
+",1558172962,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"I think curating locally is a good step, as different Wikipedias have different customs on this. Basque Wikipedia, for example, has 6 main templates that would cover around 80% of articles (statistics invented now)",1558126751,PHID-USER-g73uduhwmggntmexighn,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"This development looks good as a step forward. It's certainly better to have a cross-wiki uniform way for listing community curated things, than having local hacks on wikis.
+
+It shouldn't be a permanent solution, however. Some problems with it that need a deeper solution. For example, ""Cite"" has its own whole first-class button, and all the other templates will be hidden in this new list behind Insert -> Template, even though many templates are as useful and common as Cite is. There is no good reason for this differentiation. Many templates could be first-class features like ""Cite"", although global templates should probably implemented first.
+
+But still, it's a step in the right direction.",1558126633,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5191516, @Trizek-WMF wrote:
+> That's the list of most popular (aka most used templates), right?
+
+No, it will be a community-curated list, defined on-wiki in a JSON message file. Otherwise you'd probably end up with useless crap like `{{!}}`.",1558114037,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5191516, @Trizek-WMF wrote:
+> That's the list of most popular (aka most used templates), right?
+
+No, it will be a fixed list, defined on-wiki in a JSON message file. Otherwise you'd probably end up with useless crap like `{{!}}`.",1558113546,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#5191516, @Trizek-WMF wrote:
+> That's the list of most popular (aka most used templates), right?
+
+No, it will be a fixed list, defined on-wiki in a JSON message file.",1558113274,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"That's the list of most popular (aka most used templates), right?",1558112406,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Here's how it looks on my local install:
+{F29090517,size=full}",1558112173,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"@Whatamidoing-WMF tells me that English Wikivoyage would be a good candidate for a potential test: ""they have 6 templates they use all the time"". I think French Wikipedia would be a good candidate too. ",1558112074,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T223534#5189267, @Theklan wrote:
+> I think the first one would work.
+
+
+
+>>! In T223534#5189303, @Esanders wrote:
+> For anyone interested working  on this, the code would go in `ve.ui.MWTemplatePlaceholderPage`, and would need to do the following:
+> # Fetch the JSON data for the local wiki using mw.message, see `ve.ui.Citoid.init.js` for an example of this.
+> # Get the template descriptions for the listed templates using the API, see the request that the search box uses
+> # Append a list of mw.widgets.TitleOptionWidgets to the page
+
+
+
+>>! In T223534#5190232, @Trizek wrote:
+> I'll give my eternal reconnaissance as a community member to whoever achieves that task. This is something we miss since a while on French Wikipedia. 
+> 
+> Also, that task is probably a duplicate of {T96710}.
+
+
+
+>>! In T223534#5190242, @Theklan wrote:
+> @Trizek-WMF it is similar, but this would be adding the most usual ones, as we are working with 6 automated templates that are highly used.
+
+
+
+>>! In T223534#5191300, @Esanders wrote:
+> I think T96710 is asking for a similar feature, but adding buttons to the toolbar, not the template dialog.
+
+",1558109768,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T223534#5189252, @Esanders wrote:
+> I think for a first pass on this we can allow wikis to define a list of most common templates on wiki, e.g.
+> ```lang=json,name=MediaWiki:Template-directory.json
+> [
+>   ""Biografia infotaula automatikoa"",
+>   ...
+> ]
+> ```
+> 
+> This could then be fetched by the template dialog and show in the space below the search input:
+> 
+> {F29083664,width=350}
+> 
+> 
+> In the future we would probably want to make this more flexible, such as by grouping templates together, e.g.
+> ```lang=json,name=MediaWiki:Template-directory.json
+> [
+>   {
+>     ""group"": ""Infoboxes"",
+>     ""templates"": [
+>       ""Biografia infotaula automatikoa"",
+>       ...
+>     ]
+>   }
+> ]
+> ```
+> 
+> which would necessitate a slightly more complex UI.
+
+",1558109701,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T223534#5189228, @Theklan wrote:
+> When we click in the insert template button we get a white pop-up where we must figure out what the correct template is. In Basque wikipedia we are using a reduced automatic templates system, so it would be very useful to have them listed just below, so you can click them and choose.
+> 
+> Most useful infoboxes:
+> 
+> * {{biografia infotaula automatikoa}}
+> * {{artelan infotaula automatikoa}} < for artworks
+> * {{Eraikin infotaula automatikoa}} < buildings
+> * {{Hiri orokor infotaula}} < cities
+> * {{Probintzia orokor infotaula}} < administrative units up from cities
+> * {{taxotaula automatikoa}} < taxobox
+
+",1558109622,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Change 510943 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Allow popular templates to be listed in the template dialog
+
+[[https://gerrit.wikimedia.org/r/510943]]",1558109586,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,{T109253} looks like a similar request.,1510330562,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,">>! In T55590#1673809, @Elitre wrote:
+> @James_F, is this something a gadget could easily achieve?
+
+It could, but I'd rather avoid people adding new things to the toolbar //ad hoc//. We really need a design for this that can scale.",1443172692,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"@James_F, is this something a gadget could easily achieve?",1443171649,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Mmm... I don't know if it's a //blocker//, but it is quite desirable.",1434708828,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"I suggest that per Amire80, cross-wiki templates be made a blocker bug for this feature.
+
+It's just too much widely duplicated work to do otherwise.",1434682068,PHID-USER-rtxvf2yd2qd3qmsps3bk,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,It would really be appreciated in wikipedia's sister projects to have a costumizable common templates dropdown as there is with the citation tool.,1429796328,PHID-USER-igg6dsz3ijszcxvvirgp,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The more I use VE, the more I miss such a feature.
+
+The challenge with it is that it's badly project-specific, so community editors will need an easy way to customize this list, but something like this already done for citation templates, so it should be possible for other templates as well.
+
+This is one issue for which it's REALLY worth poking around Wikimedia projects in different languages to ask them what would they like in such a feature, and what current features they currently have that are similar to this. For example, the Hebrew Wikipedia has the Templateslist script ( https://he.wikipedia.org/wiki/MediaWiki:Templateslist.js ), which adds a dropdown with common templates to the Vector editing toolbar, and users there complain that they don't want to use VE because VE doesn't have such a list.
+
+I'm not rushing - this requires proper research, understanding and design, but it should be somewhere in the roadmap.",1434455793,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The more I use VE, the more I miss such a feature.
+
+The challenge with it is that it's badly project-specific, so community editors will need an easy way to customize this list, but something like is already done for citation templates, so it should be possible for other templates as well.
+
+This is one issue for which it's REALLY worth poking around Wikimedia projects in different languages to ask them what would they like in such a feature, and what current features they currently have that are similar to this. For example, the Hebrew Wikipedia has the Templateslist script ( https://he.wikipedia.org/wiki/MediaWiki:Templateslist.js ), which adds a dropdown with common templates to the Vector editing toolbar, and users there complain that they don't want to use VE because VE doesn't have such a list.
+
+I'm not rushing - this requires proper research, understanding and design, but it should be somewhere in the roadmap.",1420149875,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The more I use VE, the more I miss such feature.
+
+The challenge with it is that it's badly project-specific, so community editors will need an easy way to customize this list, but something like is already done for citation templates, so it should be possible for other templates as well.
+
+This is one issue for which it's REALLY worth poking around Wikimedia projects in different languages to ask them what would they like in such a feature, and what current features they currently have that are similar to this. For example, the Hebrew Wikipedia has the Templateslist script ( https://he.wikipedia.org/wiki/MediaWiki:Templateslist.js ), which adds a dropdown with common templates to the Vector editing toolbar, and users there complain that they don't want to use VE because VE doesn't have such a list.
+
+I'm not rushing - this requires proper research, understanding and design, but it should be somewhere in the roadmap.",1416866083,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,*** Bug 69787 has been marked as a duplicate of this bug. ***,1408571387,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"The main priority is a (very limited) suggestion of quick-inserting templates when in a reference, which is bug 50458.
+
+This is certainly a possibility, but would probably want to be context-specific (so it only suggests clean-up templates when your cursors is at the top of the page; only suggests stubs when at the bottom; etc.).",1377908590,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+VisualEditor: Provide some kind of template suggestion in the transclusion editor,"Created attachment 13203
+A very quick mockup for quick access buttons
+
+One idea I've had is to use some of the empty vertical space on the right of the dialog for some quick access buttons. See attachment for a 2 minute mockup of how this might look. The labels I've used in the mockup are not necessarily the right ones, they're just ones I quickly thought of.
+
+Either the buttons could be set to allow one-click access to certain templates, or to be drop-down lists of similar related ones. Possibly the two could be combined - click to get the top item in the list, or click and hold for a moment to open the drop down for short list (almost certainly no more than 10, probably less than that) of similar ones.
+
+Selecting any of these would have the same effect as typing the name into the search field, selecting it, and clicking to add the template.
+
+A second idea would be to change the transclusion editor button from a simple button to a combined button/drop down as I described above. Here you could only have a single list but it could be longer. Selecting a template from this list would load the transclusion editor with that template preloaded into it.
+
+Some way of customising either/both lists (beyond recently used) would be useful too.
+
+**Attached**: {F11786}",1377900016,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-6ivr3ri6bvcbt55jfp2f,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","As discussed at bug 50452 comment 9 it would be very useful for a page to have associated metadata about its title.
+
+For most pages and by default* this would be identical to the all-lowercase rendering of its stored title, but where pages correctly start with a lowercase letter (on wikis where the first character is case insensitive), contain special characters or conflict with interwikis/namespaces, etc. the metadata would record the correct page title. It could also be used for titles that should be italicised.
+e.g. on en.wp:
+Page Title         - Correct Title
+[[IPad]]           - iPad
+[[Benzo(a)pyrene]] - Benzo[a]pyrene
+[[Pilot No. 5]]    - Pilot #5
+[[D Ream]]         - D:Ream
+[[Computer]]       - computer [indicating a common noun]
+[[Amy Studt]]      - Amy Studt [indicating the title is proper noun]
+[[Animal Farm]]    - <i>Animal Farm</i> [italicised proper noun, the tags are not literal]
+
+The displayed title would be taken from this metadata and as such would effectively supercede the DISPLAYTITLE magic word and the [[template:correct title]] family of templates (and the equivalents on other wikis).
+
+VisualEditor and any other tools that aid linking would be able to read the metadata and use it to determine what the default displayed name should be when linking to that article.
+
+*Actually the default should be configurable as I guess languages like German that capitalise common nouns may want the default to be capitalised and the upper/lower case distinction probably doesn't make sense in all scripts.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50452
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56868
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49076",1377811860,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_description,open
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)",">The advantage of storing this metadata is that it allows for a large amount of
+>semantic information about the title which can be used not only for linking but
+>potentially for customised display options and doubtless more that I haven't
+>thought of.
+
+That's certainly true. 
+-----
+
+My initial reaction is that the user is probably in a better position to decide how to capitalize/italicize the title in a given context than software would be, but if such formatting of titles is consistent, I suppose it could make sense to automatically do it.
+
+>I'm told that it needs to be moved out of templates for VE to support.
+
+It should not need that to *use* the data. To effectively edit the displaytitle data, it may need that.
+
+>I don't
+>know why.
+>More philosophical, but I was under the impression that the long term goal was
+>to separate metadata from content?
+
+Some folks have that goal. Personally I think that doing so would reduce the power of mediawiki significantly, although my opinion may be a minority one. (And probably offtopic for this bug report)",1378773876,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","(In reply to comment #4)
+> > 
+> > The idea is not just to store what the title should be displayed as when it
+> > doesn't match the default, but to record what the title actually is in all
+> > cases. Presently there is afaik no way to tell that for example [[Parish
+> > ale]]
+> > is a common noun, [[Parish Walk]] is a proper noun and [[Parish Bar]] is a
+> > proper noun that should be italicised.
+> 
+> *Does it really make sense to store what type of word the title is, instead
+> of just how to display it. 
+
+Sorry that was my poor explanation. For tools (such as VisualEditor) to offer a sensible default for the display of a link the tool needs to know how the title should be displayed. In mid sentence:
+*The vicar drank some [[parish ale]] and declared it ""rather good""
+*The vicar competed in the 2013 [[Parish Walk]], raising money for the church roof.
+*The vicar enjoyed listening to the ''[[Parish Bar]]'' album while driving.
+
+At present only the last of these has need of a {{DISPLAYTITLE}} because the unitalicised format with an initial capital letter is correct when it appears as a page title. This tells us nothing about how it should be used in other contexts, and the DISPLAYTITLE for the third example tells us nothing about capitalisation mid-sentence. In other words we want to store the information about how the title should be used in all cases, not just when it doesn't match the default.
+
+It seems to me that there are three options for how to structure this metadata. 
+The first is to simply store the format, e.g. ""title: ''Parish Bar''"" or ""title: parish ale"".
+The second is to define classes of titles and how they are displayed and assign each article title to one such class. e.g. for Parish Walk ""title class: proper noun"" and for Parish Bar: ""title class: musical album title""
+The third option is to store a class (without that defining the display) and the display: ""title: ''Parish Bar''; class: musical album title"".
+
+The classes and (associated) displays would need to be configurable per wiki for either of those options to work.
+
+I've also realised that separate fields would be good for ""title"" and ""disambiguator"", e.g. for the article at [[Mercury (element)]]: ""title: mercury""; ""disambiguator: element""; class: ""common noun"" or for [[Wellington, Somerset]]: ""title: Wellington""; ""disambiguator: Somerset""; ""class: place name""
+
+The advantage of storing this metadata is that it allows for a large amount of semantic information about the title which can be used not only for linking but potentially for customised display options and doubtless more that I haven't thought of.
+
+> *What problem (Other than perhaps ideological) does moving the data out of
+> templates actually solve?
+I'm told that it needs to be moved out of templates for VE to support. I don't know why.
+More philosophical, but I was under the impression that the long term goal was to separate metadata from content?",1378772376,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","
+> 
+> The idea is not just to store what the title should be displayed as when it
+> doesn't match the default, but to record what the title actually is in all
+> cases. Presently there is afaik no way to tell that for example [[Parish
+> ale]]
+> is a common noun, [[Parish Walk]] is a proper noun and [[Parish Bar]] is a
+> proper noun that should be italicised.
+
+I don't think I properly understand the problem this is trying to solve. To be honest it sounds like a solution looking for a problem.
+
+Basically what I'm asking:
+*Does it really make sense to store what type of word the title is, instead of just how to display it. Mapping types of words -> how to display them sounds like something that would vary a lot by culture (Or even in english wikis that have different traditions)
+*What problem (Other than perhaps ideological) does moving the data out of templates actually solve?",1378768930,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","(In reply to comment #1)
+> I'm confused. Is this asking to move {{DISPLAYTITLE:...}} out of wikitext?
+> 
+> Displaytitle is a form of metadata, and it gets stored in the db separately,
+> and can be queried separately, etc.
+
+Chris has it right - it's effectively asking to implement DISPLAYTITLE properly, rather than DISPLAYTITLEIFNEEDEDTOBEANOVERRIDE.",1378766620,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","According to James F at  bug 50452 comment 9 ""for this to be used in VisualEditor it would need to be a proper feature and not one hacked into a template""
+
+The idea is not just to store what the title should be displayed as when it doesn't match the default, but to record what the title actually is in all cases. Presently there is afaik no way to tell that for example [[Parish ale]] is a common noun, [[Parish Walk]] is a proper noun and [[Parish Bar]] is a proper noun that should be italicised.",1378283614,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"Pages should have metadata about their correct title (capitalisation, special characters, etc)","I'm confused. Is this asking to move {{DISPLAYTITLE:...}} out of wikitext?
+
+Displaytitle is a form of metadata, and it gets stored in the db separately, and can be queried separately, etc.",1377892939,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-lmosmab7pjd2m5cnmo2t,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","If you start to add a link, and change your mind (e.g., you realized that you have the wrong word selected), there is no way to simply cancel adding a link.  You have to remove the link with the trashcan icon.
+
+Steps to reproduce:
+
+1. Select any word.
+2. Press ctrl-K to enter link tool.
+3. Attempt to cancel the link by closing the unwanted link tool dialog box using Esc key or the < button.
+4. Discover that VisualEditor linked the word anyway.
+
+If the Escape key and ""Cancel"" button are worthless for escaping/going back/cancelling, then they shouldn't be present or have any effect.
+
+({T93749} altered this to re-add the cancel/close button.)",1377799620,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-reeypst4562edb7eoqfi,task_description,resolved
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","Change 209695 merged by jenkins-bot:
+Only apply annotations if 'done' is clicked
+
+[[https://gerrit.wikimedia.org/r/209695]]",1433183692,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","Change 209695 had a related patch set uploaded (by Jforrester):
+Only apply annotations if 'done' is clicked
+
+[[https://gerrit.wikimedia.org/r/209695]]
+",1432909435,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","We now have a ""Remove"" button, which is nice, but since the link is automatically created when you open the inspector, most people don't know that if you did nothing and want nothing to make the link, then you still need to ""Remove"" the link that you didn't know you already made.",1430939284,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","Maybe we should label the ""cancel"" button ""remove"" or somesuch? I don't know…",1429559622,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing",*** Bug 56431 has been marked as a duplicate of this bug. ***,1395197399,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","I'm not sure that the < button is going to be interpreted as ""close and apply"".  It looks to me a lot more like a ""get me out of here"" or ""go back (to how things were)"" button.  I think that it ought to be treated the same as an Escape key.",1378763198,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","I'm getting very frustrated with the current behaviour of the link tool in this regard.
+
+When I am in the link dialog and I press escape I want the dialog to exit and leave the page in the state it was in before I loaded the dialog, ignoring any changes I have made and whether I was adding or modifying a link.
+
+The current behaviour of the < button (close and apply the current state) and the rubbish bin (close and remove link) are correct. 
+
+There also though needs to be a button/icon though that closes and cancels all changes made (this is bug 52462).",1378124944,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+"VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing","This is due to fixing bug 51065; we can either have one or the other, but not both. I'm minded to stick with the behaviour as it now is, as it's less confusing that the previous form was.
+
+Consequently, marking as WONTFIX. Very happy to be argued around to the opposite behaviour, however.",1377834959,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-reeypst4562edb7eoqfi,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"The Parsoid team is considering a simplification of the different mw:ExtLink/* variants to just a single mw:ExtLink type. 
+
+For most types this should not make much of a difference to VE, but for auto-numbered external links ([http://example.com]) it might, so I am looking for your input. I did some testing on https://www.mediawiki.org/wiki/User:GWicke/TestNumberedLinks. Changes to the text lead to corruption as in this diff:
+
+https://www.mediawiki.org/w/index.php?title=User%3AGWicke%2FTestNumberedLinks&diff=772988&oldid=772987
+
+There also does not seem to be any automatic re-numbering when a numbered link is changed into a plain external link.
+
+What are you plans for the handling of numbered links?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377728940,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_description,resolved
+VisualEditor: Provide a way for users to edit auto-numbered external links,*** Bug 57755 has been marked as a duplicate of this bug. ***,1386000770,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Change 98114 merged by jenkins-bot:
+Make autonumbered external links inspectable
+
+https://gerrit.wikimedia.org/r/98114",1385801891,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Change 98114 had a related patch set uploaded by Catrope:
+Make autonumbered external links inspectable
+
+https://gerrit.wikimedia.org/r/98114",1385662180,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,*** Bug 57419 has been marked as a duplicate of this bug. ***,1385489060,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Though the code in gerrit 90432 is merged, that just adjusts how VisualEditor works with auto-numbered links to support Parsoid's changed behaviour - this bug remains undone. Resetting to ASSIGNED.",1382368642,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Change 90432 merged by jenkins-bot:
+Add a node type for numbered external links
+
+https://gerrit.wikimedia.org/r/90432",1382353256,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Change 90432 had a related patch set uploaded by Catrope:
+Add a node type for numbered external links
+
+https://gerrit.wikimedia.org/r/90432",1382043276,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"I guess that means that we can go ahead and drop the explicit numbering in Parsoid in favor of pure CSS. We will also drop the /Numbered typeof suffix along with the other mw:ExtLink suffixes.
+
+You will then get empty links with typeof=""mw:ExtLink"" as in this example.",1377816806,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"
+* Supports:
+  - http://caniuse.com/#feat=css-sel3 (CSS3 :empty)
+  - http://caniuse.com/#feat=css-counters (counter-increment)
+  - http://caniuse.com/#feat=css-gencontent (:before)
+
+* Test case: http://jsfiddle.net/wTNc4/
+  - Works fine in IE9: http://cl.ly/image/2r2L1F3U2X0r
+
+I wonder why it didn't work for James?",1377816701,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"(In reply to comment #5)
+> Please test this test with IE as well. I am hopeful that it works with IE >=
+> 8.
+
+In IE9 you get ""not empty"" but none of the other four links.
+
+In IE10 and IE11 you get all five links as expected.",1377816286,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Yeah, you need the UI for the creation of empty links. But there is no need to deal with renumbering etc in VE, which simplifies things a lot.
+
+Please test this test with IE as well. I am hopeful that it works with IE >= 8.",1377814874,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"(In reply to comment #3)
+> With a href set this actually works as expected in FF and Chrome:
+
+[…]
+
+> So it seems that we can actually implement auto-numbered links in pure CSS.
+
+That's great. :-)
+
+We will still need a way of creating an auto-numbered external link (rather than just being able to copy and alter them), but that's our problem. :-)",1377814131,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"With a href set this actually works as expected in FF and Chrome:
+
+<html><head>
+<style>
+body {
+    counter-reset: numberedlink;
+}
+a[typeof~=""mw:ExtLink""]:empty:after {
+    content: ""["" counter(numberedlink) ""]"";
+    counter-increment: numberedlink;
+}
+</style>
+</head>
+<body>
+<a href=""test"" typeof=""mw:ExtLink""></a>
+<a href=""test"" typeof=""mw:ExtLink"">not empty</a>
+<a href=""test"" typeof=""mw:ExtLink""></a>
+<a href=""test"" typeof=""mw:ExtLink""></a>
+<a href=""test"" typeof=""mw:ExtLink""></a>
+</body>
+</html>
+
+So it seems that we can actually implement auto-numbered links in pure CSS.",1377813350,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,See http://www.w3.org/TR/css3-content/ for the relevant spec.,1377811927,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: Provide a way for users to edit auto-numbered external links,"Maybe this could even be handled in CSS, somewhat like this example:
+
+<html><head>
+<style>
+body {
+    color: red;
+    counter-reset: numberedlink;
+}
+a[typeof~=""mw:ExtLink""]:empty:before {
+    content: ""["" counter(numberedlink) ""]"";
+    counter-increment: numberedlink;
+}
+</style>
+</head>
+<body>
+<a typeof=""mw:ExtLink""></a>
+<a typeof=""mw:ExtLink""></a>
+<a typeof=""mw:ExtLink""></a>
+<a typeof=""mw:ExtLink""></a>
+</body>
+</html>
+
+Problems in this simple experiment:
+
+* Links are not clickable, and (maybe related)
+* the content can only be generated :before and :after, but not inside the empty link.",1377811764,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-pu5wfoxxn6nblwrmsxy7,task_subcomment,NA
+VisualEditor: trouble with Template:Hlist,"Reporting user comment, some formatting is mine:
+<<I made this http://en.wikipedia.org/wiki/User:Atethnekos/sandbox4 as a demonstration. 
+1) If the hlist template is used in an infobox or a table like on the page, when I go to VE, the list will end up be extended far into the page. 
+2) If it's used with [[File:Image]] as on the page, the list will end up being cut off, and then some weird things will happen if I try to click on the hlist template (e.g., the page will be extended to right and my browser will give a horizontal scroll bar). FF 23.0.1 Win7--Atethnekos 19:33, 25 August 2013 (UTC) >>
+
+I edited his sandbox a couple of times. In this version http://en.wikipedia.org/w/index.php?title=User:Atethnekos/sandbox4&oldid=570256245&veaction=edit the pics of the masks are moved to the left: the caption of the first one is not cut out, but you can't edit the pics at all since VE will consider them as a non editable block.
+I can't reproduce the horizontal bar and I can correctly edit the hlist template inside the mask pic caption with both FF and Chrome.
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1377521880,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-l6w6nyonc7ci3mnehffx,task_description,resolved
+VisualEditor: trouble with Template:Hlist,"The previous comments don't explain what/who exactly this task is //stalled// on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)).
+
+> the list will end up be extended far into the page.
+Does not seem to happen anymore:
+
+{F31846960}
+
+> If it's used with [[File:Image]] as on the page, the list will end up being cut off, and then some weird things will happen if I try to click on the hlist template (e.g., the page will be extended to right and my browser will give a horizontal scroll bar).
+
+Cannot reproduce in Firefox 76.
+
+>  but you can't edit the pics at all since VE will consider them as a non editable block.
+
+If I understand correctly then I cannot reproduce:
+
+{F31846963}
+
+{F31846962}
+
+If this still happens then please follow https://www.mediawiki.org/wiki/How_to_report_a_bug (clear steps to reproduce; what's expected; what happens instead; in separate sections) and reopen this ticket.
+
+For the records, wiki text test case here is
+```
+{{Infobox philosopher
+|image = File:NAMA Masque esclave.jpg
+|caption = Geloius: copy of portrait bust by [[Silanion]]
+|name = Geloius
+|birth_place = [[Athens]]
+|main_interests  = {{hlist |nullus |primus |secundus |tertius |quartus |quintus |sextus |septus |octavus |nonus |decimus |et ceterus }}
+}}
+```
+
+",1590760929,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-l6w6nyonc7ci3mnehffx,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"Same as #51959, but it keeps hapenning on frwiki: some texts that look like telephone numbers are changed in <a href=""tel:..."">...</a>.
+
+http://fr.wikipedia.org/w/index.php?title=Les_Visiteurs_(film,_1993)&diff=95954243&oldid=95559259
+
+http://fr.wikipedia.org/w/index.php?title=Transformers_3_:_La_Face_cach%C3%A9e_de_la_Lune&diff=96093057&oldid=95089445
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**OS**: other
+**Platform**: Other
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51959",1377428640,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-26knsdpm5excrpowc3dw,task_description,resolved
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,On re-testing this is now fixed.,1430334450,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"(In reply to Elitre from comment #10)
+> So, James, is this what we are going to do, adding this line? Thanks.
+
+Yes, experimentation as to what triggers Safari to break things, and what changes cause it to stop breaking, is needed.",1398787080,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"So, James, is this what we are going to do, adding this line? Thanks.",1396944069,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"The answer appears to be to have:
+
+  <meta name = ""format-detection"" content = ""telephone=no"">
+
+… in the <head> of the page. Unfortunately, we probably don't want to switch this off for all MediaWiki pages, so instead we will need to experiment to see if JS inserting it into there makes the behaviour go away.",1395762161,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"(In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #5)
+> Hmmm, it seems I was close enough ;)
+> 
+> ""In Safari on iOS, telephone number detection is on by default"" according to
+> [1]. There it says that adding <meta name=""format-detection""
+> content=""telephone=no""/> would prevent that autolink feature, that may
+> interfere with the content editable component of the editor.
+> 
+> ----
+> 
+> [1]
+> https://developer.apple.com/library/safari/featuredarticles/
+> iPhoneURLScheme_Reference/Articles/PhoneLinks.html
+
+That URL is no longer valid. This is the new one:
+
+https://developer.apple.com/library/ios/featuredarticles/iPhoneURLScheme_Reference/PhoneLinks/PhoneLinks.html",1393672711,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"And, yes, I really think that VE/Parsoid should find a way to detect changes from browser extensions and neutralize them, otherwise it will be an endless battle to have every extension modified, updated, ...",1377442673,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"(In reply to comment #4)
+> This might be a bug in Safari rather than VE, but even if it is it would be
+> useful for VE (or Parsoid?) to detect the changes and neutralise them. It is
+> unlikely that Wikipedia would need href=tel: links but I can see they might
+> be
+> useful in environments like the contact pages on the Foundation wiki, so
+> stripping such links completely mightn't be the optimal solution?
+
+Isn't the <a> tag deactivated on the Foundation wiki also, as it is on Wikipedia ?
+On Wikipedia, the <a href=""tel:..."">...</a> doesn't produce a link because MediaWiki renders the <a> tag as text.
+
+Even if ""tel:"" was needed on any wiki, it would be better handled as an external link [tel:... ...] than as a <a> tag.",1377442583,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"Hmmm, it seems I was close enough ;)
+
+""In Safari on iOS, telephone number detection is on by default"" according to [1]. There it says that adding <meta name=""format-detection"" content=""telephone=no""/> would prevent that autolink feature, that may interfere with the content editable component of the editor.
+
+----
+
+[1] https://developer.apple.com/library/safari/featuredarticles/iPhoneURLScheme_Reference/Articles/PhoneLinks.html",1377441939,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"Bug 51959 was also iPad/Safari and I've not seen any reports of it being reproducible on any other system so I've adjusted the bug summary accordingly.
+
+This might be a bug in Safari rather than VE, but even if it is it would be useful for VE (or Parsoid?) to detect the changes and neutralise them. It is unlikely that Wikipedia would need href=tel: links but I can see they might be useful in environments like the contact pages on the Foundation wiki, so stripping such links completely mightn't be the optimal solution?",1377441370,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"For the first one, iPad with Safari.
+No answer for the seconde one.",1377440082,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"May it be caused by a Skype plugin for the browser, that usually make those telephone-looking numbers into a clickable link to make a call through Skype?
+
+http://stackoverflow.com/questions/3032427/how-to-prevent-phone-numbers-to-be-converted-into-skype-links",1377431900,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links,"I can't reproduce it on either page using Firefox 23 / Linux.
+
+Do you know what OS/browser those editors were using?",1377431452,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-26knsdpm5excrpowc3dw,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"EverNote Web Clipper has a problem with the editable area and inserts:
+
+<style id=""_clearly_component__css"" type=""text/css"">#next_pages_container { width: 5px; hight: 5px; position: absolute; top: -100px; left: -100px; z-index: 2147483647 !important; } </style><div id=""_clearly_component__next_pages_container""></div>
+
+Triggering: https://en.wikipedia.org/wiki/Special:AbuseFilter/345
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1377255600,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-pxgyjw5isiqywctk5c7e,task_description,resolved
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114013,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113100,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"Derk-Jan, did you hear back from Evernote?",1406844430,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,Evernote support ticket #253866,1385645050,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Evernote Web Clipper inserts _clearly_component__css,"I submitted a report with Evernote trough their API developers platform.
+
+http://dev.evernote.com/support/faq.php#filebug
+
+Not totally the right forum, but I suspect that was the easiest way to get developer level support.",1377256101,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-pxgyjw5isiqywctk5c7e,task_subcomment,NA
+VisualEditor: Hieroglyphics tool inserts a new line at the cursor whether or not you actually insert a hieroglyphics block,"Screeshot of post hiero editor
+
+Safari 6
+
+I opened the editor inline, didn't do anything, pressed the back arrow, the editor closed and inserted a newline.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11956}",1377250800,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ur6ykzlvrepzlje7qdsa,task_description,open
+Support Clipboard Based Image Upload,"**Author:** `lucashokanson`
+
+**Description:**
+It would be extraordinarily useful to mimic Imgur.com's clipboard based uploader.  Upon visiting the upload page, you would simply Paste - command/control v or click a button to use your clipboard's contents.  This would then upload the file and return to you the standard file:____ page.  
+
+In addition to this, if this functionality is built it, it would even more useful to streamline this into the page editor as well. A simple button click could pop up a prompt and upon upload return the proper image reference in your article.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=37932
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65670",1377203100,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-jbmwpl35zyrkzdw4hfwx,task_description,duplicate
+Support Clipboard Based Image Upload,I'm going to move this to upload wizard I suppose.,1377203439,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-jbmwpl35zyrkzdw4hfwx,task_subcomment,NA
+Support Clipboard Based Image Upload,"There's an ambition to add this to VisualEditor in time - see bug 37932, which I've added as a see also - but not sure on plans for doing this for the regular wikitext editor.",1377203318,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jbmwpl35zyrkzdw4hfwx,task_subcomment,NA
+VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users),"In Chrome, edit any page in https://test2.wikipedia.org
+
+Click Transclusion, type 's' into input box.
+Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""
+
+In Firefox, edit any page in https://test2.wikipedia.org
+
+Click Transclusion, type 's' into input box.
+Result is a list of suggestions that begin with ""Succession box"" and ""South America""
+
+This suggests that at least one list of Template suggestions is absolutely incorrect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-gi6xthiyrxw7c2mnmgvl,task_description,declined
+VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users),*** Bug 70219 has been marked as a duplicate of this bug. ***,1416339245,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gi6xthiyrxw7c2mnmgvl,task_subcomment,NA
+VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users),"This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit). Not sure if this is a ""bug"" per se…",1387245600,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gi6xthiyrxw7c2mnmgvl,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned <div>s used to create pie charts(!) to break,"https://he.wikipedia.org/wiki/%D7%A8%D7%90%D7%A9%D7%95%D7%9F_%D7%9C%D7%A6%D7%99%D7%95%D7%9F?veaction=edit
+
+The template on the left has a pie chart (see in view mode in the extendable green section) -- but in edit mode it's all jumbled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+{T53932}
+{T53166}",1377192840,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-s55lzef3gmpfhhdexj66,task_description,resolved
+VisualEditor: CSS munging causing absolutely-positioned <div>s used to create pie charts(!) to break,"The issue as filed was resolved long time ago (see parent bug T52577), I filed T96667 to track the issue of oversized highlights.",1429615765,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-s55lzef3gmpfhhdexj66,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned <div>s used to create pie charts(!) to break,"There are no screenshots here to show how it used to be broken, but it seems almost correct now. Only the highlight is displayed incorrectly.
+
+(The infobox also looks a bit borked, which is a Parsoid issue I filed as T96529.)
+
+{F117709}",1429478036,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-s55lzef3gmpfhhdexj66,task_subcomment,NA
+"VisualEditor: Hieroglyphics tool operating on a selection replaces the content, rather than appending the hieroglyphics block","Testing the hieroglyphics feature on MW.org just now:
+
+1. Open VE and select some text
+2. Click ""Hieroglyphics"" button
+
+Why can I ""apply"" hieroglyphics to a run of text, as if it was a kind of formatting? Doesn't make any sense.
+
+3. Type some hiero codes (e.g. G26-t:Z4-A40) in the box
+4. Leave the popup (by clicking away/clicking the < button)
+
+The popup goes blank and can't be dismissed (Firefox 23).
+Also notice that no hieroglyphics are seen.
+
+5. Review changes.
+
+The hiero tag successfully appears in the wikitext, even though it is invisible in VE.
+
+Sorry for three issues in one bug, but I guess you guys can figure this out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1376996400,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cq2sis2akuochldidpvr,task_description,declined
+"VisualEditor: Hieroglyphics tool operating on a selection replaces the content, rather than appending the hieroglyphics block",I can't reproduce any of these issues in Chrome or Firefox. Please re-open with details if you can.,1386337120,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cq2sis2akuochldidpvr,task_subcomment,NA
+"VisualEditor: Hieroglyphics tool operating on a selection replaces the content, rather than appending the hieroglyphics block","The second and third issues are now fixed. However, you can still ""apply"" hieroglyphics (and LaTeX) to a run of text: this behavior is confusing and nonsensical.",1379825433,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cq2sis2akuochldidpvr,task_subcomment,NA
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page","Some users on en.wp consider it a bug that VE shows the top of the page after you edit a ""section"", and demand instead that, as VE auto-scrolls to the relevant section when you click Edit, it does the same after you save. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376995620,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-unso5k7lgj5lojo4gz7w,task_description,resolved
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page","Yes, it does seem to. There could still be some polishing done to make it smoother, but it does work, so this task is resolved.",1541160256,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-unso5k7lgj5lojo4gz7w,task_subcomment,NA
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page","It seems to work in recent versions of VisualEditor, isn’t it?",1541159845,PHID-USER-2nopae2cxuamwcbndaih,True,PHID-TASK-unso5k7lgj5lojo4gz7w,task_subcomment,NA
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page",*** Bug 54645 has been marked as a duplicate of this bug. ***,1392058252,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-unso5k7lgj5lojo4gz7w,task_subcomment,NA
+"VisualEditor: When ""section editing"", re-focus on that section after saving the page","Not sure, is https://bugzilla.wikimedia.org/show_bug.cgi?id=52566 a dupe?",1384269494,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-unso5k7lgj5lojo4gz7w,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","If you have the preference set to ""Edit pages on double click"", then double-clicking on a word while you're already in VisualEditor tries to re-open the page so you can edit it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Double-click_asks_if_you_want_to_leave_page",1376935080,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_description,resolved
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","Change 162968 merged by jenkins-bot:
+Stop ""Edit pages on double click"" from affecting VE
+
+https://gerrit.wikimedia.org/r/162968",1411685541,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","Change 162968 had a related patch set uploaded by Alex Monk:
+Stop ""Edit pages on double click"" from affecting VE
+
+https://gerrit.wikimedia.org/r/162968",1411676447,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""",Is this now fixed given the above being merged?,1411664311,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","Change 150391 merged by Bartosz Dziewoński:
+Make mediawiki.action.view.dblClickEdit recheck preference
+
+https://gerrit.wikimedia.org/r/150391",1411663651,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","Change 150391 had a related patch set uploaded by Alex Monk:
+Add JS hook to allow extensions to prevent double click from changing to action=edit
+
+https://gerrit.wikimedia.org/r/150391",1406667468,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""",fwiw 'Enable section editing by right clicking on section titles' is active within VE,1380693722,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","For variety, I confirmed on Chrome/Linux ;-)",1380693472,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, ""Edit pages on double click (requires JavaScript)""","This was reported in Mozilla 23 on Windows 8, and I reproduced it in Safari 6 on Mac OS 10.7.5, so it's probably universal.",1376935250,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-upzv2zqhai5rvy7wc6sm,task_subcomment,NA
+"VisualEditor: Show ""Review changes"" link in the toolbar all the time, or available somehow (on hover?) rather than just through save dialog","I am editing a page and something untoward happens.  To review changes, I now have to click ""Save page"", which is sort of like a sign above a circular saw saying, ""To unplug, please saw through wall.  Thank you for your cooperation.""
+
+:p
+
+Perhaps hovering over the ""save page"" button could drop down alternative actions, such as ""save draft of changes"", ""review..."" etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376812680,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-jacp3aj4vm5u6h6b4chc,task_description,open
+"VisualEditor: Show ""Review changes"" link in the toolbar all the time, or available somehow (on hover?) rather than just through save dialog","Firstly, hover is something we avoid using in VisualEditor as it means the functionality isn't available for those using a touch interface. I don't think this is ""major"" - closer to ""minor"" - but either way it's an enhancement.
+
+Also, there's an existing bug to show what changes you've made as you enter them (e.g. by highlighting the background of the new text, like Microsoft Word's ""tracked changes"" view): bug 37931.",1376952013,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jacp3aj4vm5u6h6b4chc,task_subcomment,NA
+VisualEditor: Broken Foxlingo Firefox extension injects javascript into page,"See reported diff on fr.wp
+https://fr.wikipedia.org/w/index.php?title=Debra_Winger&action=historysubmit&diff=95823433&oldid=94552186
+
+The js is from Foxlingo but the liberal sprinkling of nowikis is from VE or Parsoid.
+
+PrimeHunter at en.wp reports that a Google search for FoxlingoJS reveals several other internet forums are suffering the same problems.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1376582220,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-nfvv4eym3zcif2i7nb4d,task_description,resolved
+VisualEditor: Broken Foxlingo Firefox extension injects javascript into page,"Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114004,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nfvv4eym3zcif2i7nb4d,task_subcomment,NA
+VisualEditor: Broken Foxlingo Firefox extension injects javascript into page,"Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113130,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nfvv4eym3zcif2i7nb4d,task_subcomment,NA
+VisualEditor: Populate the edit summary for simple changes,"At T53903,  Elitre said:
+
+> A user at it.wp wonders: if VE could pre-populate the summary box, could it
+> also auto-add the text that was added, in case of very short additions? i.e.,
+> if someone added a parameter to a template, could it automatically detect
+> what was added and write it in the edit summary? Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**: T53903, T50274",1376506380,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-dy2dbpcxtagget43fzoa,task_description,open
+VisualEditor: Populate the edit summary for simple changes,See also T3307 & T14411,1606235062,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-dy2dbpcxtagget43fzoa,task_subcomment,NA
+VisualEditor: Add help page for all keyboard shortcuts,"GMail's keyboard shortcuts help page
+
+Similar to GMail's modal when '?' is pressed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F11100}",1376487180,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_description,resolved
+VisualEditor: Add help page for all keyboard shortcuts,"Change 98517 merged by jenkins-bot:
+Keyboard shortcuts MW integration
+
+https://gerrit.wikimedia.org/r/98517",1389823722,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_subcomment,NA
+VisualEditor: Add help page for all keyboard shortcuts,"Change 107153 merged by jenkins-bot:
+Keyboard shortcuts dialog
+
+https://gerrit.wikimedia.org/r/107153",1389821946,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_subcomment,NA
+VisualEditor: Add help page for all keyboard shortcuts,"Change 107153 had a related patch set uploaded by Esanders:
+WIP Keyboard shortcuts dialog
+
+https://gerrit.wikimedia.org/r/107153",1389625063,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_subcomment,NA
+VisualEditor: Add help page for all keyboard shortcuts,"Change 98517 had a related patch set uploaded by Esanders:
+WIP Keyboard shortcuts dialog
+
+https://gerrit.wikimedia.org/r/98517",1385994018,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sjrtlm4n5ikwytrhpwex,task_subcomment,NA
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page","At https://en.wikipedia.org/w/index.php?title=Judi_Dench&curid=85432&diff=568314406&oldid=568147939 the article was top and tailed with
+<embed type=""application/x-datavault"" width=""0"" height=""0"" />
+
+Searching seems to suggest the most likely cause is the ""DataVault"" password manager browser plugin
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1376392740,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_description,resolved
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page","Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114025,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_subcomment,NA
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page","Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113124,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_subcomment,NA
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page","Did you get anything back, Derk-Jan?",1397835827,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_subcomment,NA
+"VisualEditor: Broken DataVault browser plugin causes ""application/x-datavault"" to be injected into the page",I've send an email to their support department. Let's hope it helps.,1376470329,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ffqjhxzn42bsoktzv7bm,task_subcomment,NA
+"VisualEditor: Add support for making some templates directly ""visually editable"", as if they were tables (e.g. infoboxes)","A user at it.wp asks if, in the long term, it will be possible to edit templates directly (i.e., infoboxes), without the transclusion dialog, as if one was changing something in a table. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376386200,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-fnziglwvvwpmlxekyjvk,task_description,resolved
+"VisualEditor: Add support for making some templates directly ""visually editable"", as if they were tables (e.g. infoboxes)","
+
+*** This bug has been marked as a duplicate of bug 50182 ***",1394074105,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fnziglwvvwpmlxekyjvk,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,"<< http://en.wikipedia.org/wiki/File:GreatNurse.jpeg is a headshot of Virginia Henderson that was uploaded to Commons yesterday. VisualEditor's image feature can't find it, and won't accept file names that it doesn't believe exist. WhatamIdoing (talk) 00:17, 13 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=37578",1376382300,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-zckv7xwfgl4cxjix23f5,task_description,declined
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,*** Bug 52218 has been marked as a duplicate of this bug. ***,1383282089,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,Marking WONTFIX as this is inherently fixed by CirrusSearch and lsearchd has been end of life'd and won't be improved further.,1383013054,PHID-USER-oetk6bbl6omm354ejz3b,True,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,*** Bug 54777 has been marked as a duplicate of this bug. ***,1382572188,PHID-USER-oetk6bbl6omm354ejz3b,True,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,"The good news: CirrusSearch is updated a few seconds after a page is added, changed, or deleted.
+The bad news: it isn't ready yet!",1377001750,PHID-USER-2rnfxoezl66afpa7w7in,True,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+Newly-uploaded image doesn't immediately appear in image search results in VisualEditor,The image now comes up in the search result - this is probably a delay in the speed with which the search index is updated.,1376952277,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zckv7xwfgl4cxjix23f5,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"At https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=568194420#I_can.27t_edit_the_references it has been proposed that it would be helpful to editors if they could edit references in the reference list, as well as where they appear inline.
+
+""As just about every object you see on a page is directly editable with the VE, of course having the reflist not editable is counter-intuitive. ""
+
+This proposal would make T54736 either unnecessary or just a ""workaround""/interim measure, depending on the timescale to implement.
+
+--------------------------
+
+#2 in the 2023 wishlist: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Citations/Allow_citations_to_be_edited_in_the_references_section_with_VisualEditor
+",1376315340,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_description,resolved
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by Novem Linguae using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/d94eddd976/w/ ]]~~",1713878505,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 950231 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Don't warn that reference list is uneditable%%%
+https://gerrit.wikimedia.org/r/950231",1692430973,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by Novem Linguae using patch(es) linked to this task:
+[[ https://patchdemo.wmflabs.org/wikis/d94eddd976/w ]]",1692417223,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 950231 had a related patch set uploaded (by Novem Linguae; author: Novem Linguae):
+%%%[mediawiki/extensions/Cite@master] Don't warn that reference list is uneditable%%%
+https://gerrit.wikimedia.org/r/950231",1692416810,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by ESanders (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/e045f72283/w/ ]]~~",1686069577,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> Citations and footnotes can now be edited directly in the references section using VisualEditor.
+
+I wouldn't describe it like this (which I think is how the wish was described). You can't edit the citations in-place, like you can a image caption, but you can launch the editing dialog for each reference from the list. Maybe:
+
+> Citation and footnote editing can now be started from the reference list when using the visual editor.
+
+The changes are in wmf10 which is on mediawiki.org (e.g. https://www.mediawiki.org/w/index.php?title=Composer&veaction=edit&section=10) and would already be on Wikipedias but for the train being blocked at the moment (T330216).
+
+There is no documentation at the moment, just the text description.",1685118600,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"For Tech News, please confirm if this is an accurate summary, below? 
+> Citations and footnotes can now be edited directly in the references section using VisualEditor. This feature request was voted #2 in the 2023 Community Wishlist Survey.
+And confirm the timing: Will it be on the deployment train next week, or live on Monday, or other/later?
+And is there a documentation page that it should link to, or just plaintext? 
+Thanks.",1685048120,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 922153 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Fix ref list click-to-edit on mobile%%%
+https://gerrit.wikimedia.org/r/922153",1684782321,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 922153 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/Cite@master] Fix ref list click-to-edit on mobile%%%
+https://gerrit.wikimedia.org/r/922153",1684776138,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 903311 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Launch reference editors from ve.ce.MWReferencesListNode%%%
+https://gerrit.wikimedia.org/r/903311",1684340605,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,This will also supersede T54736 and T183170.,1684327960,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/e045f72283/wiki/Douglas_Adams?veaction=edit",1683044836,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by ESanders (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/6247694800/w/ ]]~~",1683044705,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/6247694800/wiki/Douglas_Adams?veaction=edit",1683043472,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by ESanders (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/0f949bd767/w/ ]]~~",1683043303,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/0f949bd767/wiki/Douglas Adams?veaction=edit",1682683909,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Currently it works like that (both in Chrome and FF):
+
+| 1. before click | 2. first click | 3. second click |
+| {F36934541} | {F36934544} | {F36934546} |
+
+So first click could just change highlighted ref. That would work similar to tables and templates I guess.
+
+> but there is nothing to show after a single click (or any other interaction to be had, e.g. drag/drop).
+
+You could always show an edit button like with templates.",1680201324,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> Looks quite promising :-). One note: at the moment in the demo, after saving the changes, the script jumps to the link in the article. If it's not obvious, I think it would be good to stay where you started...
+
+Yes - this will require some more upstream changes to fix.
+
+> I assume 1st click should only select as with other templates
+
+These aren't real focusable templates, it's just a CSS hover and JS click handler. It could be changed to double click, but there is nothing to show after a single click (or any other interaction to be had, e.g. drag/drop).
+
+We have previously implemented this single click -> dialog interaction with the categories list.",1680189296,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> Looks quite promising :-). One note: at the moment in the demo, after saving the changes, the script jumps to the link in the article. If it's not obvious, I think it would be good to stay where you started...
+
+Yes - this will require some more upstream changes to fix.
+
+> I assume 1st click should only select as with other templates
+
+These aren't real focusable templates, it's just a CSS hover and JS click handler. It could be changed to double click, but there is nothing to show after a single click (or any other interaction to be had, e.g. drag/drop).",1680187061,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> WIP UI: https://patchdemo.wmflabs.org/wikis/6689bcdde2/wiki/Douglas_Adams?veaction=edit&section=26
+
+Looks quite promising :-). One note: at the moment in the demo, after saving the changes, the script jumps to the link in the article. If it's not obvious, I think it would be good to stay where you started...
+
+Hm... And I think double click is not working correctly. When I click [64] and then click [66] the edit window opens. I assume 1st click should only select as with other templates. I assume that is part of the WIP, but reporting just to be sure :)",1679967370,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,Esanders is a god,1679953834,PHID-USER-2xdbwtk2vlfbk2k6hhbh,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,WIP UI: https://patchdemo.wmflabs.org/wikis/6689bcdde2/wiki/Douglas_Adams?veaction=edit&section=26,1679937874,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Change 903311 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/Cite@master] Launch reference editors from ve.ce.MWReferencesListNode%%%
+https://gerrit.wikimedia.org/r/903311",1679937793,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,">>! In T54750#8727283, @Whatamidoing-WMF wrote:
+> Once it becomes possible to edit `<references />`, will editing through `{{reflist}}` require rich editing of templates?
+
+Probably not – we already have a special-case support for templates that generate a reflist. Since we already treat it like a ""real"" references list, any new features should work here as well. For example, note how in https://en.wikipedia.org/wiki/Holcocera_immaculella?veaction=edit (random article) the references are labelled like this: {F36929304} …and not like this: {F36929306} …despite being generated from a `{{Reflist}}` markup.
+
+----
+
+However, supporting references defined using `{{reflist|refs= ... }}` would require rich editing of templates. For example <https://en.wikipedia.org/wiki/Bali#cite_ref-Foley_128-0>. We already detect those and disable editing in visual mode, and presumably something similar woul happen inside this new feature: {F36929314}",1679923162,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Once it becomes possible to edit `<references />`, will editing through `{{reflist}}` require rich editing of templates?",1679850024,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,">>! In T54750#8641368, @DLynch wrote:
+>> Even if we switch to just using (2) this will mean that references are re-numbered when switching from read mode to edit mode.
+> 
+> I think we're stuck with the references renumbering in the reflist if the user edits any of them anyway, so it might be better to do it up-front and have them stay consistent throughout the entire session.
+
+It takes ~800ms to render the list on [[Barack Obama]], hence not doing it up-front. Also on he.wiki, the initial rendering is the only rendering with content.",1677604414,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,">>! In T54750#8641368, @DLynch wrote:
+>> Even if we switch to just using (2) this will mean that references are re-numbered when switching from read mode to edit mode.
+> 
+> I think we're stuck with the references renumbering in the reflist if the user edits any of them anyway, so it might be better to do it up-front and have them stay consistent throughout the entire session.
+
+It takes ~800ms to render the list on [[Barack Obama]], hence not doing it up-front.",1677604047,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"> Even if we switch to just using (2) this will mean that references are re-numbered when switching from read mode to edit mode.
+
+I think we're stuck with the references renumbering in the reflist if the user edits any of them anyway, so it might be better to do it up-front and have them stay consistent throughout the entire session.",1677168505,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"I was thinking that a quick path forward would be for the reference list to offer a button that opened up a variant on the reuse dialog. In its context item would be the easiest place.
+
+{F36866803}",1677168143,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Following on from David's point, there are two ways the the reference list is rendered in the VisualEditor surface:
+1. **Using the HTML of the ref list supplied by Parsoid**: This will include all references, included those defined inside templates (e.g. infoboxes), but the numbers will not necessarily map to those in VE's data model, so mapping from these references to editable references will be hard.
+2. **Generating a reference list by iterating over references in the document model**: This will //exclude// references defined inside templates, but can easily be mapped back to the reference data in VE's data model. This list could be edited directly, or be used to launch a reference editor relatively easily.
+
+(1) is used on the first load mostly for performance reasons (implemented in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Cite/+/411101) as it's a lot quicker to use the pre-generated HTML; rebuilding the reference list can be pretty slow on large pages. It also helps on wikis where most references are defined in templates, such as he.wiki.
+
+Even if we switch to just using (2) this will mean that references are re-numbered when switching from read mode to edit mode.
+
+From a UI perspective, we will need a way of showing the reference list context, probably by not embedding it but also thinking about where a user can click to show it (as clicking the reference list contents would now let you edit the list in some way)
+
+{F36865507}
+{F36865505}",1677088390,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Copying my comment in from the other ticket, since I think it remains relevant here:
+> The major hangup on this is that it's going to expose the challenges with VE seeing references that're defined within templates. (Because of the current lack of a centralized way to edit references, this is only really visible to users from the ""reuse citation"" part of the cite dialog, where such references don't appear.) I suspect that if we accept having those ones greyed out in the list with a ""this can't be edited here"" tooltip, the rest of this should be fairly simple to do -- unless I'm not thinking of something, it's ""just"" hooking up a few bits of already-existing functionality and doing some UI work to expose them.",1676585194,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,[[https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Questions_techniques/semaine_28_2016#Impossibilt.C3.A9_d.27apporter_des_corrections_dans_les_sections_Notes_et_r.C3.A9f.C3.A9rences|New feedback from a user]] (a beginner) who wants to change a reference rom the reflist while editing with VE. ,1468426292,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,The alphabetising problem could perhaps be reduced by making the references only limitedly editable. i.e. Only individually editable in a dialog that allows for the editing of the template/parameters only.,1376323496,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface,"Adam Cuerdon comments:
+    I'd suggest popping up a note telling the user what he or she is doing at least the first time, though. Something like ""This reference is used to document the source of text in the article. You can also edit it by clicking on the number after the text. Please make sure that you don't accidentally break documentation with your edit. Thanks for your work!""
+    We don't want to have a situation where newbies, for example, try to alphabetise the list, say.
+
+Personally, I'm not sure ""documentation"" is the right word, but otherwise it seems like a good suggestion.",1376321914,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-wvw2grcusq5k2ipkgxi4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","en.wp user JmCor reports that in Firefox on Windows 7 the shortcut ""<shift><alt>V (show the changes), which stopped working when the Visual Editor was introduced: currently, <shift><alt>V simply positions the cursor on the ""Show the changes"" button.""
+
+I can confirm this also occurs in Firefox 23 on Linux.",1376130000,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-txrorpbrj6b5ssangri4,task_description,open
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",">>! In T54701#6404011, @Sunpriat2 wrote:
+> Additionally https://www.mediawiki.org/wiki/Extension:FlaggedRevs add one more tab ""Pending changes"" which is also assigned ""v"" key. Any but unique replacement for short keys will be more convenient to activate instantly.
+
+See {T335652}
+
+>>! In T54701#8587857, @Pols12 wrote:
+> What about using`E` as accesskey for visual__**E**__ditor? From Read view, it opens wikitext editor. Pressing once again, it would switch to VisualEditor.
+
+I’d rather not change a conflicting access key to another conflicting one. The idea of @jhsoby seems better to me, although it doesn’t fix all conflicts either: filtering out `edit` and `submit` would fix this task, filtering out `history` would help fixing T26977, but there’s no way to fix T335652 with this approach, as both access keys should be available in read view.",1682937197,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","What about using`E` as accesskey for visual__**E**__ditor? From Read view, it opens wikitext editor. Pressing once again, it would switch to VisualEditor.",1675606822,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",Would it be possible to just disable the VE accesskey if the `wgAction` is `edit` or `submit`?,1649588052,PHID-USER-jqjb54lbf7psat6shbcc,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Additionally https://www.mediawiki.org/wiki/Extension:FlaggedRevs add one more tab ""Pending changes"" which is also assigned ""v"" key. Any but unique replacement for short keys will be more convenient to activate instantly.",1598121058,PHID-USER-fhwkrjgsdwt5sqn3xaq7,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Additionally ruWP has one more tab ""Pending changes"" which is also assigned ""v"" key in https://www.mediawiki.org/wiki/Extension:FlaggedRevs . Any but unique replacement for short keys will be more convenient to activate instantly.",1598120799,PHID-USER-fhwkrjgsdwt5sqn3xaq7,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Additionally ruWP has one more tab ""Pending changes"" which is also assigned ""v"" key in https://www.mediawiki.org/wiki/Extension:FlaggedRevs",1598120539,PHID-USER-fhwkrjgsdwt5sqn3xaq7,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","@AhmadF.Cheema reports problems with this in detail at https://www.mediawiki.org/wiki/Topic:Veyo7xqvss4jz8d8
+
+Also, {T156141} seems similar.",1582684702,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Yes Ed, but only when you're on the content page.",1464613495,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",alt+shift+v appears to launch VE now we have editor switching (from duplicate T130899),1459265003,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","(In reply to Lejonel from comment #4)
+> In other namespaces focus is always on ""show changes""
+> button, but the shortcut does not actually click the button. That is because
+> the HTML still contains a hidden ""visual edit"" tab with the same shortcut.
+
+This is changing (bug 64142)",1400371890,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","**dng032** wrote:
+
+Results of testing in Wikipedias about a week ago:
+
+(""Positions"" means that focus changes to the ""Show changes"" button, but does not actually show the changes)
+
+Catalan : positions
+German : shows dif
+French : positions
+Greek : positions
+English : shows dif
+Spanish : shows dif
+Hungarian : positions
+Italian : warns about not saving
+Japanese : shows dif
+Portuguese : positions
+Russian : positions
+Simple English : positions
+Chinese : shows dif
+
+Sorry for being late to react and for not retesting recently. ~~~~",1398663027,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Maybe Visual editor does not need an access key while the normal editor is used? Then one possible solution is to just remove 'v' as access key for visual editor when using the normal wiki editor.
+
+I think removing the access key there should not cause any problems for most users, for two reasons:
+
+1. Since currently ""show changes"" in wiki editor has the same acces key, neither of the access keys work as they should.
+2. In most use cases for Visual editor a user starts visual editting when they are seeing an actual page, not when they are looking at the page in the wiki editor.",1397937991,PHID-USER-axibsactcdotqkfh3mfe,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",*** Bug 52969 has been marked as a duplicate of this bug. ***,1397676026,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox",Suggestions for a different shortcut for VisualEditor (or show changes) welcome.,1397675426,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","This is because the same shortcut is used for multiple actions in the same page. 
+
+For me in Firefox in namespaces with visual editor enabled pressing alt+shift+v once focuses on the ""show changes"" button, pressing again focus on ""visual edit"" tab"" and further key pressing just changes the focus between the two. In other namespaces focus is always on ""show changes"" button, but the shortcut does not actually click the button. That is because the HTML still contains a hidden ""visual edit"" tab with the same shortcut.",1377281265,PHID-USER-axibsactcdotqkfh3mfe,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","**dng032** wrote:
+
+(In reply to comment #2)
+> This is definitely related to VisualEditor - the shortcut works when
+> VisualEditor is disabled (Safari on Mac 6, Firefox 23 on Linux) and in
+> Konqueror on Linux which VE is not enabled for.
+> 
+> Changing component to VisualEditor accordingly
+
+jmCor: still Windows 7, Firefox 22.0. The component change did not fix the bug on my machine.",1376531065,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","This is definitely related to VisualEditor - the shortcut works when VisualEditor is disabled (Safari on Mac 6, Firefox 23 on Linux) and in Konqueror on Linux which VE is not enabled for.
+
+Changing component to VisualEditor accordingly",1376338921,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox","Adding James to the CC as this might be an artefact of VE, even though it affects the source editor.",1376130189,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-txrorpbrj6b5ssangri4,task_subcomment,NA
+VisualEditor: Tool to set/unset text as a variable (<var>),"The <var> tag is used in many articles for variables, and there are css styling rules for it. An example article is Shading
+http://en.wikipedia.org/w/index.php?title=Shading
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1376027640,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-rafmsmstj5wsl5tvqzu5,task_description,open
+VisualEditor: Tool to set/unset text as a variable (<var>),"Change 141605 merged by jenkins-bot:
+Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
+
+https://gerrit.wikimedia.org/r/141605",1404154586,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rafmsmstj5wsl5tvqzu5,task_subcomment,NA
+VisualEditor: Tool to set/unset text as a variable (<var>),"Change 141605 had a related patch set uploaded by Jforrester:
+Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
+
+https://gerrit.wikimedia.org/r/141605",1403568489,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rafmsmstj5wsl5tvqzu5,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"VisualEditor needs a tool to set/unset font colour.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375956720,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_description,open
+VisualEditor: Tool to set/unset text color,{F57733391},1732295481,PHID-USER-zij24c7higfq2voiyf5y,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"Just an idea on how it may look like (a bit inspired by BlueSpice)
+
+{F41702256}
+
+""Custom color"" click will open a browser tool to select a custom color (browser tool allows to enter html code so no need to have a separate control for that)
+
+End by analogy -- for colorizing table cells:
+
+{F41702286}
+
+This one would change color for the whole cell (not just for background) -- it might be helpful when people create tables and use color as an additional layer of information. For example like in Ubuntu versions table:
+
+{F41702296}
+",1705756442,PHID-USER-37di5uhqpe6nihfhk2xf,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"Just an idea on how it may look like (a bit inspired by BlueSpice)
+
+{F41702256}
+
+""Custom color"" click will open a browser tool to select a custom color (browser tool allows to enter html code so no need to have a separate control for that)",1705755713,PHID-USER-37di5uhqpe6nihfhk2xf,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,[[ https://www.mediawiki.org/wiki/Topic:U1chcv4o6odr18kt | Here's a new request for this. ]],1509959939,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"(In reply to Elitre from comment #8)
+> Would we need to file a separate bug for background text color?
+
+Background colour isn't really a thing we want to encourage. :-) That would be a distinct piece of work; created as bug 73041.
+
+If you meant surface colouring for objects like table cells or <div>s, that's another piece of work again - bug 52180	for table cells, possibly that bug will need to be split for the wider work.
+
+If you mean the ""highlight"" / ""mark"" tool, that's yet another one - bug 64376.",1415217870,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,Would we need to file a separate bug for background text color?,1415188300,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"(Copied from
+https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Textcolor)
+
+Hi there :-)
+Just wondering, why there is no feature for ""coloring Text"". In know, there is a way, to use 'span', but im looking for a feature, with a WYSIWYG-Editor. Any advices, ideas?
+
+Thanks :-)",1400881060,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"(In reply to comment #5)
+> I think this will be difficult to implement well. I see two concerns:
+> 
+> * extraneous (noöp) <span>s being left behind in the wikimarkup; and
+
+This is the same as bug 37835 and is trivial for us to trim out.
+
+> * <span>s that specify the color black (bad for accessibility, etc.).
+
+Yes, though we already give people loads of tools that they can (and frequently do) abuse. Technology should serve the community and we should make tools that let them do their job, rather than dictate that they can't do something (or, in this case, that they can but it's hard).
+
+> There may be some generic ""clear formatting"" button/apparatus to be used to
+> mitigate the second point, but I'm still wary.
+
+There's already a ""clear formatting"" button provided - it would apply its magic to this too.",1383008984,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"I think this will be difficult to implement well. I see two concerns:
+
+* extraneous (noöp) <span>s being left behind in the wikimarkup; and
+* <span>s that specify the color black (bad for accessibility, etc.).
+
+There may be some generic ""clear formatting"" button/apparatus to be used to mitigate the second point, but I'm still wary.",1383008076,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"(In reply to comment #2)
+> Any pros/cons of handling this by wrapping colored text in span with
+> appropriate value of style tag?
+
+Yeah, that's what we'll want to do.
+
+We'll want to supply a generic <span> editor (which lets you edit the style=""…"" tag as raw CSS) at some point, but we'd want to do something about colour sooner (and nicer), I think.",1376123060,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,*** Bug 51409 has been marked as a duplicate of this bug. ***,1376120681,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,Any pros/cons of handling this by wrapping colored text in span with appropriate value of style tag?,1376115461,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Tool to set/unset text color,"Do we want to do this as a general colour-picker widget, possibly?",1376115172,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-iwu723btthb7y2jwtq7u,task_subcomment,NA
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,"**Author:** `sandrobt.wiki`
+
+**Description:**
+Here is how to reproduce it, when trying to add a link to the page ""Maria"" on en.wiki.
+
+1) Select the add link icon and type ""maria""
+2) Select ""Maria"", which is at the end of the suggested list
+3) Press Enter or the ""<"" button
+4) Save
+
+The link is added to Mariah Carey (which was on the top of the suggested list).
+Cf. https://en.wikipedia.org/w/index.php?title=User:Sandrobt/prova&diff=prev&oldid=567641122
+
+Note that this doesn't happen if in 2) you had typed ""Maria"" (which is the exact title of the page you want to link to).
+Cf. https://en.wikipedia.org/w/index.php?title=User:Sandrobt/prova&diff=next&oldid=567641169
+
+The same problem appears in similar situations in it.wiki (for example when adding a link to ""Sega"" you need to type it exactly like that, since the first option is always SEGA) 
+
+I'm using Firefox 22.0 on Mac OS X 10.6.8.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1375943460,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ga36aloq6psrxy7t2mlx,task_description,resolved
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,In fixing bug 50452 we have changed the behaviour slightly regarding this - not sure if it's still necessary to keep this open?,1378766470,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ga36aloq6psrxy7t2mlx,task_subcomment,NA
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,"This happens in every case where:
+* the input text case INsensitively matches an entry >= 2nd in the list, AND
+* the input text case sensitively does NOT match the title of any in the list, AND
+* the user selects the case insensitive match
+
+It doesn't matter whether the text was entered in the link dialog or selected on the editing surface.",1378424550,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ga36aloq6psrxy7t2mlx,task_subcomment,NA
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,"**sandrobt.wiki** wrote:
+
+Ok, note taken. Though, a bug that inserts the wrong link in a pretty large variety of situation, despite selecting the correct one and without giving any clue of having done so, is a pretty seriuos problem and has probably alredy produced quite a lot of wrong wikilinks.",1375945790,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ga36aloq6psrxy7t2mlx,task_subcomment,NA
+VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list,"[resetting severity, see http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity ]",1375945480,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ga36aloq6psrxy7t2mlx,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"if the template does not contain explicit ""templatedata"", the API call should return auto-generated ""templatedata"" structure, distilled from the template itself.
+
+
+it's trivial to do - basically parse the template, extract parameter names (including order based, aka 1,2,3), and return ""default"" templatedata where every param is of type string, without any special attributes (default, required, etc.)
+
+this 15-line enhancement will make VE suddenly useful for templates, without detracting anything from current functionality.
+
+we did this in hewiki with ""template param wizard"" (the equivalent of VE template editor, for the old wikitext editor), and it enhanced the wizard's functionality tenfold.
+
+regretfully i can't submit a patch - hopefully someone else will be able to do so.
+
+peace.
+
+--------------------------
+
+**See Also**:
+{T54135} / https://bugzilla.wikimedia.org/show_bug.cgi?id=52135",1375804800,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_description,duplicate
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"Change 257684 abandoned by Eranroz:
+Guess parameters when templatedata is missing
+
+[[https://gerrit.wikimedia.org/r/257684]]",1483655816,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"Change 257684 had a related patch set uploaded (by Eranroz):
+Guess parameters when templatedata is missing
+
+[[https://gerrit.wikimedia.org/r/257684]]
+",1449605074,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,">>! In T54581#1271501, @Krinkle wrote:
+> .... Possibly with a warning outputted alongside the object. Similar to how MediaWiki's query api communicates things like ""warnings"", ""normalized"", and ""badrevids"".
+
+maybe so, but maybe it should not be ""warning"". 
+a new field can be added to the record returned by the API, e.g. ""synthetic"" or somesuch, to indicate tempaltedata was generated synthetically, and the template itself does not contain ""templatedata"" tag.
+
+peace.
+
+",1431449493,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"The TemplateData editor now supports scanning the template source code and inferring a list of parameter names to bootstrap the documentation editor.
+
+We can use the same logic server-side to provide a basic TemplateData object for templates lacking it. Possibly with a warning outputted alongside the object. Similar to how MediaWiki's query api communicates things like ""warnings"", ""normalized"", and ""badrevids"".",1431058046,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"for many many simple templates, just getting the list of parameter names is enough for even moderately experienced editors. 
+the editor may even be well familiar with the template, but she does not necessarily remembers the exact name (case sensitive) of every parameters.
+
+
+regarding your 2nd use case: are you aware that this tool (prepopulate templatedata editor) is already written and working?
+
+written by wmf volunteer (intern? gsoc student? not sure), [[mw:. User:Mooeypoo]], and works on hewiki for quite some time. 
+this tool already includes ""import parameters from template"" button - last time i checked, it was working quite well. 
+
+see [[mw:MediaWiki:Gadget-templatedata-core.js]], function ""importtemplateparams()""
+
+if your comment meant to describe it rather than suggesting to build it, i apologize for the confusion.
+
+bottom line: having templatedata is good, but when it does not exist, just seeing the list of parameters (including unpopulated) is hugely perferrable to not seeing them.
+
+peace.",1400794505,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"So this ""guess template data"" parser would be useful in two cases:
+
+* Consumers of TemplateData (e.g. VisualEditor)
+
+They could pass a parameter to the API of TemplateData to trigger this parser as fallback. The generated data would presumably be flagged in some way to allow consumers to identify them as such.
+
+* TemplateDate editor
+
+A button to prefill the template data (e.g. use the default data as a start and edit from there). This should not be misused to populate <templatedata> tags on a bunch of pages, this is only useful if users provide data beyond what is inferred (the inferred data is unlikely to ever be satisfactory as at best it can provide which parameters exist and maybe which are optional).",1400616454,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"(In reply to comment #4)
+> i did it long ago, and published it on
+> [[en:Wikipedia:WikiProject_User_scripts/Scripts#Scripts]]. the script page on
+> enwiki is [[en:User:קיפודנחש/TemplateParamWizard]].
+
+See also
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_103#Template_Parameter_Wizard
+(mentioned on bug 39598 comment 1)
+
+> -- ""Choices"": this allows the designer to declare that a certain parameter
+> has
+> a fixed set of ""legal"" values. very useful when the template uses a parameter
+> as an input for {{#switch:
+
+Bug 51375.
+
+> -- ""Depends on"": only expose this field if some other field is not empty.
+
+Bug 50407.",1383413267,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"The status was recently changed to ""Assigned"", but the ""Assigned to"" field was left as ""Nobody"". 
+is Mr. (or Ms.) ""Nobody"" a new developer on the team?
+
+peace.",1377790501,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"Thanks so much for the nice words, but... 
+This entry is about templatedata, not templatewizard.
+
+the information i brought above relating to TW was meant as ""what templatedata can learn from TW"" - if you'd like to discuss TW and its use on enwiki, it should be discussed on enwiki, not here.
+
+peace.",1375977047,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"Thank you so much. It works beautifully. I couldn't test it in Hebrew WP because it is situated in the edit toolbar which was disabled by me because I feel more comfortable to type everything with my keyboard. But anyway, the gadget's performance is smooth even while editing large article like ""United States"" in English WP. The only few issues I can think of right now after tried it a bit are, I don't feel the toolbar is the proper place for the gadget icon. It deserves a more visible location in the edit page. The other thing I hope to improve is that I need to select the whole markups of existing template from ""{{"" to ""}}"" in order to edit it in the Wizard. For large infobox template which has lot of parameters filled, it could be little bit inefficient to trigger. I suggest the end of the selection of the markup extends to the first vertical bar near the template name, so only selecting like this ""{{templatename|"", works the same way as ""{{templatename|foo|bar}}"".",1375976428,PHID-USER-xnvlg7y5phtzugavv6wj,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"i did it long ago, and published it on [[en:Wikipedia:WikiProject_User_scripts/Scripts#Scripts]]. the script page on enwiki is [[en:User:קיפודנחש/TemplateParamWizard]]. the script source itself is practically identical to the hewiki one, except maybe some recent enhancement(s) to the hewiki script (for instance, by default, the wizard does not leave empty parameters on the page, but some users asked for this as an option, so now the hewiki script learned to support on more option).
+
+
+the wizard uses a similar construct to ""templatedata"", but instead of having this information on the template page, it uses a subpage with a fixed name (in enwiki, this fixed name is ""Parameters"", so for Template:Foo, the templatedata equivalent will be in Template:Foo/Parameters).
+
+when the subpage does not exist, the wizard extracts the list of parameter names from the template itself, with some fixed attributes (for instance, in this case it assumes that each parameter is ""multiline"")
+
+i believe there are several people on enwiki who actually use this (at least there were) - you probably want to ask them about their experience (something like
+
+https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=TemplateParamWizard+intitle%3Ajs&fulltext=Search&ns2=1&redirs=1&profile=advanced
+
+
+
+the wizard supports some attributes that, to the best of my knowledge, ""templatedata""/VE do not support yet, which i think would be good ideas:
+
+-- ""Extended"": this allows the designer to designate some fields as ""secondary"", which means they are not visible when the form opens. if there is at least one ""Extended"" parameter, the form will grow a new checkbox ""Show all fields"", which allows the user to show/hide the ""Extended"" fields.
+
+-- ""Choices"": this allows the designer to declare that a certain parameter has a fixed set of ""legal"" values. very useful when the template uses a parameter as an input for {{#switch:
+
+-- ""Depends on"": only expose this field if some other field is not empty. very useful for templates with many repetitions (e.g., [[en:Template:Track listing]]: you make ""title4"" depend on ""title3"", and then ""note4"", ""writer4"", ""lyrics4"", ""music4"", ""extra4"", ""length4"", and finally ""title5"" all depend on ""title4""). without this feature, the wizard is much less useful for templates of this type.
+
+
+peace.",1375969237,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,Hi kipod. I can't understand Hebrew language and I have some trouble to test it in Hebrew Wikipedia. Can you translate the gadget to English Wikipedia under your own userspace? Thank you.,1375948802,PHID-USER-xnvlg7y5phtzugavv6wj,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"https://he.wikipedia.org/wiki/Mediawiki:Gadget-TemplateParamWizard.js
+
+the function is called buildParamsRaw() (""data"" is the raw template page).
+
+i cannot guarantee that it always works flawlessly, but the wizard works on hewiki  for a while now (more than a year), and i did not get any bug reports (i did have some bug reports for previous versions).
+
+i think it is possible to intentionally create a legal template that will give bad results there: specifically, this function does not take ""nowiki"" and ""noinclude"" tags into account.
+
+OTOH, it uses only 9 out of the budget of 15, so you have 6 lines to augment those shortcomings...
+
+more seriously: i assumed the codebase already have non-negligible amount of logic that can be used to distill the parameter list of a template. 
+
+(full disclosure: i too did not believe it can be done without tons of code - Eran Roz showed me the light)",1375942161,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+TemplateData: Implement inferred templatedata as fallback based on the contents of the template,"I very much look forward to a link to the part of the hewiki wizard that implements this logic. I very much doubt it can be done (or done well) in 15 lines of code, and I very much doubt it's trivial or even easy to do it well.",1375931029,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-x7gbeomejfcfsu7jr2ib,task_subcomment,NA
+VisualEditor: Allow replacing file by changing the file name,"To replace a file it is currently neccessary to delete the file from the page and insert the new one.
+
+It would be easier to replace the filename only. This avoids to add caption and file options again.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375804620,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-atfd2medq2qoyjgabdcf,task_description,resolved
+VisualEditor: Allow replacing file by changing the file name,"
+
+*** This bug has been marked as a duplicate of bug 51033 ***",1402608867,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-atfd2medq2qoyjgabdcf,task_subcomment,NA
+VisualEditor: Allow replacing file by changing the file name,"I'm not sure there's a great way to merge the experience of adding a media item and the one for editing one, but this seems a reasonable extension.",1383281015,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-atfd2medq2qoyjgabdcf,task_subcomment,NA
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","When VisEd is activated from a section edit link, the focus of the display normally stays on that section.  However, if the user activates from a section edit link while on a diff link (has to be diff of current version), the focus shifts to the top of the page as if the whole page edit link had been pressed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375747320,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-cvljbzolxfeydqmcoo2c,task_description,resolved
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","Change 131415 merged by jenkins-bot:
+Generate PHP VE edit section with correct parameter, vesection
+
+https://gerrit.wikimedia.org/r/131415",1399312738,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cvljbzolxfeydqmcoo2c,task_subcomment,NA
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","Thanks, Matt!",1399312671,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cvljbzolxfeydqmcoo2c,task_subcomment,NA
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","Change 131415 had a related patch set uploaded by Mattflaschen:
+Generate PHP VE edit section with correct parameter, vesection
+
+https://gerrit.wikimedia.org/r/131415",1399259020,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cvljbzolxfeydqmcoo2c,task_subcomment,NA
+"VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section","This is just a special case.  The general issue is that VE does not navigate to the section when a section edit is initiated with a fresh page load (it does when it uses the AJAX switch to editing without a page load).  For example, https://en.wikipedia.org/w/index.php?title=Earth&veaction=edit&section=6 .  It appears in this case because VE (there is a comment to this effect) uses a new page load to start section editing when it's showing the latest diff (to deal with another issue).
+
+This applies any time the user is sent directly to edit a section via VE.  For the Growth team's current project, we will allow the user to click ""Sign up and edit"" (including for sections).  This works using the normal signup page, with the returnto and returntoquery parameters.  That means we can not do an AJAX switch.
+
+Besides login/signup, there are other (albeit less common) reasons you might want to link directly to a section edit URL.",1399258028,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-cvljbzolxfeydqmcoo2c,task_subcomment,NA
+"When a link goes to a redirect, show the final destination as a tooltip (title attribute)","Wikis use lots of shortcuts on the talk pages, and it can be quite frustrating for the uninitiated to figure out what WP:MOS, WP:N etc. mean, especially when several are used at once.
+
+Having to click on the link to see that its about the 'Manual of Style' or 'Notability' would be unnecessary, if the same information was available in the tooltip when hovering the link.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1375731240,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-btbym6mlgax3tzzbkzr4,task_description,open
+"When a link goes to a redirect, show the final destination as a tooltip (title attribute)","I was thinking when reading.
+
+Now that you mention it, it would probably be useful for VisualEditor as well, but I think that can be its own bug.
+
+(updating the summary to clarify)",1375791803,PHID-USER-pwsgofaoir7tnszvfzqi,False,PHID-TASK-btbym6mlgax3tzzbkzr4,task_subcomment,NA
+"When a link goes to a redirect, show the final destination as a tooltip (title attribute)","In which exact situation should the tooltip be shown? 
+Is this about reading? Editing?",1375790948,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-btbym6mlgax3tzzbkzr4,task_subcomment,NA
+VisualEditor: Copying of styles to dialog frame is dirty,"Screenshot where it works (VE copied it from <style>)
+
+When VE copies styles into the frame, in the case of copying from a friendly <link> tag (e.g. one that is readable, we inspect it and copy the contents over, as opposed to a foreign one we have to fetch again from the iframe).
+
+In that case, the css we manage to extract from the remote <link> appears to be dirty and neither strictly or effectively roundtrips. Both the actual css it copied and the effective values are different.
+
+For example, in the case of ""background: none;""  it gets dirtied to ""background-image: none; background-position: initial initial; background-repeat: initial initial;"". Which means it no longer overrides background-color.
+
+Now, in some browsers background: none (old IE iirc) is indeed interpreted as the above, and it would be reasonable behaviour of it expands it to what it interprets it as.
+
+However in the case of Chrome, it does't just normalise but actually gives us values that don't match. See attached screenshots.
+
+The side effects (e.g. broken styles) are currently (e.g. MediaWiki context) most visible in debug mode because then almost everything is loaded through <link> and as such subject to this bug. In production mode most things are loaded by ResourceLoader and thus evaluated inline. However it is a bug both in production as well, it is just a matter of time before we find random broken styles.
+
+
+- Figure out if we can get the contents without normalisation
+
+- Perhaps fallback indefinitely to always using <link href> for remote stylesheets, thus costing a few extra http requests inside the dialog, but that might be the only way we can for now.
+
+- Figure out how many things are affected and in which browsers. Maybe we can get it fixed upstream reasonably fast (these seem to be genuine bugs in the browser).
+
+- If there's only a few properties subject to dirty normalisation, we could consider changing our stylesheets to avoid those properties. E.g. instead of background: none; use background-color: none; (something less ambiguous, and probably correct in this case, though it is a bug still because it works in Chrome normally, but not after roundtripping to an iframe).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F11259}",1375487160,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f3cdxehcze5c6igk2koe,task_description,resolved
+VisualEditor: Copying of styles to dialog frame is dirty,Effectively fixed for dialogs by expedient of not doing this any more…,1415062594,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f3cdxehcze5c6igk2koe,task_subcomment,NA
+VisualEditor: Copying of styles to dialog frame is dirty,"Has the bug:
+- Chrome 29 beta
+- Chrome 30 canary
+- Safari 6.0.5
+
+Does not have the bug:
+- Firefox 22 stable
+- Firefox Aurora 24.0a2",1375487416,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f3cdxehcze5c6igk2koe,task_subcomment,NA
+VisualEditor: Copying of styles to dialog frame is dirty,"Created attachment 13055
+Screenshot where it is dirty and broken (VE copied it from <link>)
+
+**Attached**: {F11260}",1375487204,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-f3cdxehcze5c6igk2koe,task_subcomment,NA
+VisualEditor: Media selector should suggest media used on other language versions of the page,"en.wp user Wouterstomp suggests that the media selector should also suggest images that are used on other language versions of the article, not just based on the page title.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T53031}",1375461120,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dv44kcirtbdcglt6wfni,task_description,open
+VisualEditor: Media selector should suggest media used on other language versions of the page,"This could be very useful, but would need us to move more of the media item usage data out of local wikis and into a central repository (probably Wikidata), which has been discussed a few times but I don't know how soon it might get done, sorry.",1375487609,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dv44kcirtbdcglt6wfni,task_subcomment,NA
+VisualEditor: Media settings dialog should show a preview of the media item,"Wouterstomp at en.wp has requested that the media settings dialog shows a tumbnail/preview of the image so you can refer to it while writing the caption.
+
+I would add to this that ctrl+click on this preview image should load the media description page in another tab/window.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375459860,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-zpdzyjmznhwuqu7y5wnu,task_description,open
+VisualEditor: Media settings dialog should show a preview of the media item,"(In reply to comment #2)
+> I don't think the original commenter had particularly thought of that, as the
+> only thing you can currently do is write a caption. The idea being that you
+> can refer back to the image when writing it. This will be even more useful
+> I guess when you can used this dialog to write alt text.
+> 
+> My gut feeling is that a live preview would be nice but not essential.
+> Possibly implement a static preview and then see if anybody asks for it to be
+> made into a live preview. Assuming a live view is more than trivially harder
+> to implement than a static one.
+
+I believe that the hard stuff here will be in showing anything at all (and, particularly, anything that looks like how it will render in the page). Will check about live-updating, though.",1375783156,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zpdzyjmznhwuqu7y5wnu,task_subcomment,NA
+VisualEditor: Media settings dialog should show a preview of the media item,"I don't think the original commenter had particularly thought of that, as the only thing you can currently do is write a caption. The idea being that you can refer back to the image when writing it. This will be even more useful I guess when you can used this dialog to write alt text.
+
+My gut feeling is that a live preview would be nice but not essential. Possibly implement a static preview and then see if anybody asks for it to be made into a live preview. Assuming a live view is more than trivially harder to implement than a static one.",1375486837,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-zpdzyjmznhwuqu7y5wnu,task_subcomment,NA
+VisualEditor: Media settings dialog should show a preview of the media item,"Is this meant to be a preview of the media item as it will render in the page (i.e., a live-updated view of the configuration options from the dialog)?",1375482852,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zpdzyjmznhwuqu7y5wnu,task_subcomment,NA
+VisualEditor: Disallow (discourage?) placing references inside section headers,"<<This is not really a VE bug (it is possible in the standard editing mode as well), but it is something that happens more often in VE, and that perhaps can be automatically disabled in VE as well; inserting references inside section headers. This is never needed or wanted (it is ugly, and the thing that needs to be referenced should be in the text of the section, not only in the title anyway). Example (spam, but the principle applies): http://en.wikipedia.org/w/index.php?title=Miniature_pig&diff=prev&oldid=566703074 . Fram (talk) 07:31, 2 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375436160,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-beeof7d2r6t7gnezbj7a,task_description,open
+"VisualEditor: Always show dialog icons for nodes (transclusion, media, reference, etc.)","A user at en.wp asks:
+""Why hide the puzzle and content icons until mouse-over? In general, if a function is active, it should be always shown - no idea, what hiding tries to achieve here.""
+
+Personally I think this could be very confusing for links, but it should be ok for templates and media.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375434180,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-nbkquo5siurqmbtxqe3i,task_description,declined
+"VisualEditor: Always show dialog icons for nodes (transclusion, media, reference, etc.)","On reflexion, I'm going to mark this as WONTFIX per my reasoning in comment 1 - this would massively dominate the interface on most real-world pages and make it unusable.",1393632819,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nbkquo5siurqmbtxqe3i,task_subcomment,NA
+"VisualEditor: Always show dialog icons for nodes (transclusion, media, reference, etc.)","yeah, the only way round that I can think of at the moment would be to have some sort of toggle between the current behaviour (default) and a display all mode. That would be useful for identifying at a glance where things are on a page, particularly with locating any invisible templates. It's not something I personally see as being of huge value, but I'm not everybody.",1375510577,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-nbkquo5siurqmbtxqe3i,task_subcomment,NA
+"VisualEditor: Always show dialog icons for nodes (transclusion, media, reference, etc.)","Templates and images aren't necessarily very big (think for example about the 20px-wide images that decorate some lists, either directly or as tables).
+
+When a node is smaller than a threshold, it displays the node icon as a pop-out (like an inspector menu); if we showed them all the time it could massively crowd-out the text of the page.
+
+Also, I worry that it would obstruct part of the template so you wouldn't know whilst editing exactly what was going to appear for users (if the menu icon was unhelpfully placed).",1375490038,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nbkquo5siurqmbtxqe3i,task_subcomment,NA
+"VisualEditor: If an added category is a redirect to another, suggest adding the target instead","If category:A is redirected to category:B 
+when user adds category:A it should switch it automatically to category:B like mediawiki:gadget-Hotcat.js
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375383960,PHID-USER-dswbdv7ibhsefllcqarz,False,PHID-TASK-ykcis27ybwjtiim3musu,task_description,resolved
+"VisualEditor: If an added category is a redirect to another, suggest adding the target instead","Change 118218 merged by jenkins-bot:
+Follow redirects in the category widgets
+
+https://gerrit.wikimedia.org/r/118218",1397702683,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ykcis27ybwjtiim3musu,task_subcomment,NA
+"VisualEditor: If an added category is a redirect to another, suggest adding the target instead","Change 118218 had a related patch set uploaded by Alex Monk:
+Follow redirects in the category widgets
+
+https://gerrit.wikimedia.org/r/118218",1394582184,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ykcis27ybwjtiim3musu,task_subcomment,NA
+"VisualEditor: If an added category is a redirect to another, suggest adding the target instead","So the redirect comes up as a suggestion, but when we add it, the redirect is resolved and the target added?",1394563520,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ykcis27ybwjtiim3musu,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","The sentence ""This page was last modified on … "" (message lastmodifiedat) is not updated after an edit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48560",1375374540,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_description,resolved
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved",Verified in production.,1416427771,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Verified in test2 and betalabs. The timestamp for ""This page was last modified on 5 November 2014, at 23:54."" seems to reflect accurately editing&saving events.",1415231839,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Change 170264 merged by jenkins-bot:
+Update ""page was last modified on date, at time"" footer line when saving
+
+https://gerrit.wikimedia.org/r/170264",1414733101,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Change 170264 had a related patch set uploaded by Alex Monk:
+Update ""page was last modified on date, at time"" footer line when saving
+
+https://gerrit.wikimedia.org/r/170264",1414715367,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved",(... I had assumed this was for the LastModified extension without checking the message name.),1414707773,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Change 170184 abandoned by Alex Monk:
+Expose getLastModifiedText function
+
+Reason:
+oops
+
+https://gerrit.wikimedia.org/r/170184",1414707699,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Change 170184 had a related patch set uploaded by Alex Monk:
+Expose getLastModifiedText function
+
+https://gerrit.wikimedia.org/r/170184",1414707232,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"VisualEditor: Invocation of ""lastmodifiedat"" message is not updated when page is saved","Same problem as bug 48560 (the page isn't re-painted when the edit is saved, just the contents <div>, and this sits outside that).",1375473428,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lreoxwdcbus6wy6gbdcn,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","The cog to the side of the ""Languages"" sidebar section does, in fact, not let you change anything about that section.
+
+### Concerns
+
+* The ULS ""cog"" is visually associated with the ""Languages"" sidebar section, despite being unrelated, other than (confusingly) relating to the word ""Language"" in some way. The placement of this cog should be reconsidered.
+
+* The ""Language"" sidebar does not currently have a way to quickly edit its contents. (Unlike HotCat for categories). It can be changed by performing a full page edit (via the main ""Edit"" button on top). Alternatively, the links can (sometimes) be edited using the ""Edit links"" placed at the end of the link, which relates to Wikidata.
+
+### Background
+
+There are three things related here:
+
+1. Edit language links on current page: This is part of the content for the current page, and can be edited by clicking ""Edit"" and changing them in VisualEditor (under ""Page Settings  > Languages""), or by using the source editor.
+
+2. Edit language links associated with current page's Wikidata item: These are stored on Wikidata and can be edited by using the ""Edit links"" button at the bottom of ""Languages"" sidebar section.
+
+{F11931}
+
+3. User interface language: This is the language used for the interface of the software, names of input fields, sections, buttons, etc. This can be changed in three ways currently:
+
+| Preferences | ""Preferences"" among the personal tools. Available on all pages, all wikis. leading to Special:Preferences.  {F14222596} {F14222603}
+|--
+| ULS (personal)| The ULS link (language name) among the person tools. Available on all pages, but only certain wikis have it enabled. Leading to a ULS dialog dedicated to language selection.  {F14222782} {F14222792}
+|--
+| ULS (cog)| The ULS cog, aside the ""Languages"" section in the sidebar. Available only on content pages, all wikis. Leads to a different ULS dialog, one that also has other features, but among them language selection. {F11929} {F14223046}
+|--
+
+
+### Original task description
+
+>>! this-does-not-edit-languages wrote:
+>
+> languages should be editable out of a link besides languages. see attachment for a wheel which opens something else, on top of languages. clicking below drops you into wikidata. to really edit the languages one has to go to page settings! very confusing.
+>
+>
+> **Attached**: {F11929}",1375354680,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-zatiesduw4yvsu33o45q,task_description,open
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Little comment 1: Since the task was filed in 2013, another element was added to most pages near the languages in the sidebar: ""//X// more"", opening the compact language links panel. I am adding the #uls-compactlinks tag here, because even though this project didn't exist when the bug was filed, it is totally relevant in the context. I am also adding the #wikidata tag, because it has a lot to do with it.
+
+Little comment 2: The following two tasks at least partially overlap with this one:
+# {T53355}
+# {T53431}
+
+----
+
+So, we now have two or three elements near the languages list:
+# The cog, near the ""Languages"" title:
+-- Coming from the ULS extension. Used for choosing UI language, and configuring webfonts and keyboards. It was put there back in 2012 when the first version of ULS was developed. Of course, the association between the ""Languages"" title, familiar to most wiki editors (and possibly to many readers) was a factor in choosing this location.
+# The Wikidata link at the bottom:
+-- It has the text ""Add links"" when the page is not linked to versions in other languages. Clicking it opens a dialog for adding the links without leaving the page.
+-- It has the text ""Edit links"" when the page is linked to versions in other languages. Clicking it goes to the item page in Wikidata.
+# The Compact Language Links ""''X'' more"" button:
+-- Appears only on pages with 9 links or more, and only if the Compact Language Links preference is enabled. (It was in beta for a long time, but now it is default in Wikipedia in all languages, and in most other Wikimedia projects.)
+-- Clicking it opens a ULS panel with all the languages in which the page is available.
+
+----
+
+This is not ideal.
+
+This is not ideal for a lot of reasons:
+# Generally, three elements near the language the list //feel// like a bit too much.
+# The cog is at the top, but the things that it includes are //probably// needed by fewer people. I'm saying ""probably"", because I don't have the numbers, but we can try to obtain them. Fonts and keyboards configuration is important in some languages, but completely unnecessary in a lot of others (at least in the current implementation; I have a lot of ideas for redoing webfonts support, but they are far from being implemented, and they are way beyond the scope of this task). One thing I'm sure of is the the other two elements are needed by users in wikis in all languages, and the cog—only in some.
+# The language selector in ""Display settings"" under the cog includes all the languages, but it only selects the UI language. Even though the panel explicitly says what does it do, I suspect that some people—possibly a lot—select the UI language instead of the article language. I've seen it happening to a lot of people in workshops for new editors.
+# As a follow up to the previous point: Changing the UI language is not currently available to logged-out users. The panel says so, and some people may even think that they can only read an article in another language if they log in. It may sound crazy, but it may be true.
+# The title is not always actually ""Languages"". It is ""Languages"" in some wikis, but in others it is ""In other languages"", ""This page in other languages"", or something else.
+# ""Add links"" and ""Edit links"" have the same location, but different text, and completely different behavior. I suspect that a lot of editors will appreciate //editing// wikidata sitelinks (i.e. languages) in a dialog similar to the one that is used for initial linking, thus making the functionalities similar. I've been hearing comments like this from a lot of users in a lot of languages for years.
+# This is more of a guess than the previous point, but I further suspect that a lot of editors will appreciate a link to the Wikidata item page in a convenient location, possibly near the language list. ""Edit links"" is such a link already, but that's not what its title says. There is also a ""Wikidata item"" link buried elsewhere in the sidebar, which does largely the same thing. As an editor, it's one of the very few sidebar links that I actually use, although I might be very different from a lot of other people. This requires proper research.
+# The ""''X'' more"" button appears in some cases, but not always.
+# The language selector (ULS) and the language editor (WikidataClient's dialog) are related in their functionality, but they have a completely different interface design. It would be nice to bring their appearance closer to each other.
+
+----
+
+That's a lot of different issues. There's material here for a lot of different tasks and subtasks. Fixing them is desirable. It won't happen overnight, and it will require //proper// design work, and not just editors' or developers' intuition. It will probably require collaboration between Wikidata developers and WMF's Language team developers.
+
+But yes, it's about time to start resolving it.
+
+To @Krinkle's question—no, there's no proper roadmap at the moment. This very long comment is, hopefully, the first attempt to think of such a roadmap.",1521568306,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Little comment 1: Since the task was filed in 2013, another element was added to most pages near the languages in the sidebar: ""//X// more"", opening the compact language links panel. I am adding the #uls-compactlinks tag here, because even though this project didn't exist when the bug was filed, it is totally relevant in the context. I am also adding the #wikidata tag, because it has a lot to do with it.
+
+Little comment 2: The following two tasks at least partially overlap with this one:
+# {T53355}
+# {T53431}
+
+----
+
+So, we now have two or three elements near the languages list:
+# The cog, near the ""Languages"" title:
+-- Coming from the ULS extension. Used for choosing UI language, and configuring webfonts and keyboards. It was put there back in 2012 when the first version of ULS was developed. Of course, the association between the ""Languages"" title, familiar to most wiki editors (and possibly to many readers) was a factor in choosing this location.
+# The Wikidata link at the bottom:
+-- It has the text ""Add links"" when the page is not linked to versions in other languages. Clicking it opens a dialog for adding the links without leaving the page.
+-- It has the text ""Edit links"" when the page is linked to versions in other languages. Clicking it goes to the item page in Wikidata.
+# The Compact Language Links ""''X'' more"" button:
+-- Appears only on pages with 9 links or more, and only if the Compact Language Links preference is enabled. (It was in beta for a long time, but now it is default in Wikipedia in all languages, and in most other Wikimedia projects.)
+-- Clicking it opens a ULS panel with all the languages in which the page is available.
+
+----
+
+This is not ideal.
+
+This is not ideal for a lot of reasons:
+# Generally, three elements near the language the list //feel// like a bit too much.
+# The cog is at the top, but the things that it includes are //probably// needed by fewer people. I'm saying ""probably"", because I don't have the numbers, but we can try to obtain them. Fonts and keyboards configuration is important in some languages, but completely unnecessary in a lot of others (at least in the current implementation; I have a lot of ideas for redoing webfonts support, but they are far from being implemented, and they are way beyond the scope of this task). One thing I'm sure of is the the other two elements are needed by users in wikis in all languages, and the cog—only in some.
+# The language selector in ""Display settings"" under the cog includes all the languages, but it only selects the UI language. Even though the panel explicitly says what does it do, I suspect that some people—possibly a lot—select the UI language instead of the article language. I've seen it happening to a lot of people in workshops for new editors.
+# As a follow up to the previous point: Changing the UI language is not currently available to logged-out users. The panel says so, and some people may even think that they can only read an article in another language if they log in. It may sound crazy, but it may be true.
+# The title is not always actually ""Languages"". It is ""Languages"" in some wikis, but in others it is ""In other languages"", ""This page in other languages"", or something else.
+# ""Add links"" and ""Edit links"" have the same location, but different text, and completely different behavior. I suspect that a lot of editors will appreciate //editing// wikidata sitelinks (i.e. languages) in a dialog similar to the one that is used for initial linking, thus making the functionalities similar. I've been hearing comments like this from a lot of users in a lot of languages for years.
+# This is more of a guess than the previous point, but I further suspect that a lot of editors will appreciate a link to the Wikidata item page in a convenient location, possibly near the language list. ""Edit links"" is such a link already, but that's not what its title says. There is also a ""Wikidata item"" link buried elsewhere in the sidebar, which does largely the same thing. As an editor, it's one of the very few sidebar links that I actually use, although I might be very different from a lot of other people. This requires proper research.
+# The ""''X'' more"" button appears in some cases, but not always.
+# The language selector (ULS) and the language editor (WikidataClient's dialog) are related in their functionality, but they have a completely different interface design. It would be nice to bring their appearance closer to each other.
+
+----
+
+That's a lot of different issues. There's material here for a lot of different tasks and subtasks. Fixing them is desirable. It won't happen overnight, and it will require //proper// design work, and not just editors' or developers' intuition.
+
+But yes, it's about time to start resolving it.
+
+To @Krinkle's question—no, there's no proper roadmap at the moment. This very long comment is, hopefully, the first attempt to think of such a roadmap.",1521567896,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links",">>! In T54383#4015867, @Krinkle wrote:
+> The main thing I'm unsure about is why the cog is placed near the ""Languages"" sidebar section. Especially given we already have two other interfaces for editing the user language. Do I understand correctly that the intention is to (eventually) migrate all wikis away from the ""cog"" icon in favour of the ULS dialog trigger from the personal tools? The dialogs have different designs, but seem similar in purpose. And I can't actually find a wiki/page combination that shows both, which leads me to believe it is a configuration option, of which the personal-tools placement seems preferable as it avoids confusion with the purpose of the ""Language links"" sidebar section.
+> 
+> Can someone confirm this? And/or point to a roadmap of some sort related to this?
+
+The different ways in which language selection is provided are the result of trying to keep a single area related to language where the default selection is about content (plus backwards compatibility). I'll try to elaborate and add some context:
+
+**Our goal and what we learned about the user needs**
+
+We want to provide the ability to select both, the content language and the UI language. During our user research we identified that many users don't have a very clear distinction of both concepts (or don't make a careful evaluation on which part a language selector they find is going to change). The most common expectation was to change the content (or both, content + UI). That is, if a user finds a selector with a list of languages and selects Italian, the user expects the content of the page to become in Italian, and it would be unexpected to see that only a few menus (the UI) change to Italian instead.
+
+Based on the above, we tried to follow the guideline of presenting the option to change the UI language in a less prominent way than the content language selection. That is providing a default selector for changing the content language, and less prominent advanced options in case you wanted to specifically change the UI only.
+
+**Why there are two different solutions**
+
+We had two different kinds of wikis. Some wikis are multilingual, like Commons. Other wikis are a group of individual monolingual wikis linking to one another, like Wikipedia in each language. For multilingual wikis we presented a language selector on the personal toolbar on top. The selector let's you pick the content language and provides advanced options at the bottom to change other aspects such as the UI language. This was working well, and having the language selection on top was easy to discover.
+
+However, monolingual wikis had already an established way to change the content language (technically, to jump to the equivalent page in a wiki of a different language) using the interlanguage links. At that time, we decided to keep the interlanguage links to avoid pushing for too much change at once (although we may want to revisit that in the future). With the constraint of keeping the interlanguage links where they were, placing the UI selector on top was problematic because (a) it created two separate areas for language selection, and (b) the most prominent one (on top) was not about content but UI. So we decided to have a single area dedicated to languages, keeping interlanguage links where they were as the most prominent language selection, and provide advanced options in a less prominent way as advanced settings.
+",1521215850,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","I've updated the task description with some background information.
+
+The main thing I'm unsure about is why the cog is placed near the ""Languages"" sidebar section. Especially given we already have two other interfaces for editing the user language. Do I understand correctly that the intention is to (eventually) migrate all wikis away from the ""cog"" icon in favour of the ULS dialog trigger from the personal tools? The dialogs have different designs, but seem similar in purpose. And I can't actually find a wiki/page combination that shows both, which leads me to believe it is a configuration option, of which the personal-tools placement seems preferable as it avoids confusion with the purpose of the ""Language links"" sidebar section.
+
+Can someone confirm this? And/or point to a roadmap of some sort related to this?",1519942423,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","This is generally a valid feature request, and this is something that ULS and VE developers should consider some time in the not-so-far future.",1395398464,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Sorry, I meant to move this to ULS (as it's mostly a ULS design question) when it was filed some weeks ago.",1377534431,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","(In reply to comment #11)
+> my english is not good enough to understand the ""incidentally, ...""
+> paragraph. what does that mean in terms of coding?
+
+We may write more code to let you use bits of VisualEditor (like the dialogs) outside of the editor.",1375485860,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","my english is not good enough to understand the ""incidentally, ..."" paragraph. what does that mean in terms of coding?",1375482575,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","(In reply to comment #8)
+> oh, you are right, it is just code to parse and display it in page settings
+> *blush*, sorry for confusion. coming back to the original suggestion: why not
+> improve the hacky gadget in the frame of the VE project, instead of including
+> it in the VE?
+
+The hacky gadget, as I recall:
+
+* Doesn't let you set non-Wikidata language links (as needed on non-Wikipedia wikis)
+* Doesn't let you set local language links to over-ride the ones from Wikidata (as needed on Wikipedia sometimes e.g. for [[Maggie Simpson]])
+* Doesn't let you change/remove other languages' links without making you leave the site and going to Wikidata to use the tools there
+* Doesn't let you create new Wikidata entities for the page
+* Is based on local code that may differ between wikis (making VisualEditor work differently in different places)
+
+We agreed with the Wikidata team a few months ago that replacing this was a worthwhile thing to do.
+
+Incidentally, on the wider point, we're very keen to start moving away from editing being a monolithic block of actions that have to take place together, and instead letting users ""curate"" quickly - whether that's changing categories, language links, workflow action items (like ""needs wikifying"" or ""nominate for deletion"") or other tasks - without having to enter the editor.
+
+HOWEVER, that's not really the point of this bug, is it?",1375480011,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","""about the cog not letting you change settings of other languages"" refers to the small wheel symbol in the side bar close to ""Languages"". 
+It is created by the MediaWiki extension ""UniversalLanguageSelector"" (ULS) so that would be the codebase to change for that aspect, not VE's code.",1375466130,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","oh, you are right, it is just code to parse and display it in page settings *blush*, sorry for confusion. coming back to the original suggestion: why not improve the hacky gadget in the frame of the VE project, instead of including it in the VE?
+
+the ""about the cog not letting you change settings of other languages"" and ""ULS"" i did not understand. what would you mean by this?",1375446015,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","(In reply to comment #6)
+> _remove_ the code to edit language links from the already complicated VE.
+
+There is no code to edit language links in VisualEditor. What are you talking about?",1375401899,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","james, bug 52105 is the exact opposite of the suggestion here. the visual editor team should, imo, leave the hacky gadget, or improve the hacky gadget with something which is not called hacky any more.
+
+and, _remove_ the code to edit language links from the already complicated VE.",1375397942,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Being able to edit language links is bug 52105 (specifically, for Wikidata ones). This would replace the current hacky gadget.
+
+The other part of this bug (about the cog not letting you change settings of other languages) would be an issue with ULS, not VisualEditor, I think?",1375384179,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","> i see, you do not know this beast as well
+
+I admit I don't know every single option of software running on Wikimedia servers by heart, plus sometimes bug reporters paraphrase things. That's why I appreciate good steps to reproduce to understand the problems that you're facing.
+
+Now that I can reproduce I agree that it's slightly confusing. 
+However the bug summary does not describe the problem but one potential solution, hence changing the bug summary to: 
+""VE > Page Settings > Languages"" functionality expected where ULS' ""Language Settings"" cog is
+
+> and all people are happier.
+
+On a general note: If you have not run a survey in your neighborhood and beyond (as other neighborhoods might have different needs and expectations), generalizations feel like http://en.wikipedia.org/wiki/Wikipedia:WEASEL and might diminish the impact & interest in your suggestions how to improve Wikimedia, which would be a pity.",1375383652,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","wikidata at the bottom
+
+attached page settings at the right, with languages. and wikidata at the bottom. and i see, you do not know this beast as well and do _not_ expect the language code there. just remove this language link code and all people are happier.
+
+**Attached**: {F11931}",1375364945,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","page settings at the right
+
+**Attached**: {F11930}",1375364802,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+"ULS' ""Language Settings"" cog is confused with a way to edit language links","Why would you want to edit languages, in order to understand the problem that you report here? To add links to articles with the same topic in other languages? That is exactly what Wikidata is for.
+
+With regard to the wheel ""which opens something else"", this is part of your language and input text settings. 
+See http://www.mediawiki.org/wiki/File:ULS_Usability_testing_summary.pdf for the Usability tests that led to this design.
+
+> to really edit the languages one has to go to page settings!
+
+I cannot find anything called ""Page Settings"" on for example http://en.wikipedia.org/wiki/Berlin . Please provide exact steps to reproduce.",1375355187,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zatiesduw4yvsu33o45q,task_subcomment,NA
+VisualEditor: pasting with middle-click in X-Windows doesn't work when automatic scrolling is enabled,"On Unix systems with an X-Windows desktop middle-clicking usually pastes text that was last selected with the mouse.
+
+It doesn't work in the VisualEditor in Firefox if automatic scrolling is enabled in the preferences.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1375295280,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-lusbxefwae6sj2xokbvm,task_description,open
+VisualEditor: pasting with middle-click in X-Windows doesn't work when automatic scrolling is enabled,How on Earth does Firefox's automatic scrolling feature interact with its pasting feature? Gah. :-),1375299597,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lusbxefwae6sj2xokbvm,task_subcomment,NA
+VisualEditor: Selecting with Shift-arrow selects the heading after a list item,"Go to https://www.mediawiki.org/wiki/User:Amire80/be-bullet-heading?veaction=edit, which contains the wikitext:
+```
+* list item 1
+* list item 2
+* list item 3
+
+==Heading==
+paragraph text
+```
+Press Shift-↓ (down arrow) three times.
+
+The first time, the first list item is selected.
+The second time, the second list item is selected.
+The third time, the third list item AND the heading are selected.
+
+Selecting the heading should require a forth press of Shift-↓.",1375294800,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-tddypvggbabpq3kxu4cc,task_description,declined
+VisualEditor: Selecting with Shift-arrow selects the heading after a list item,"Pressing shift+down moves your cursor down visually in the browser. This is just how native selection works in the browser (for example, in read mode, select the first 'l' in 'list item 1', then press shift down, and the same thing happens).
+
+Without completing re-implenting our own version of cursor movement, we couldn't fix this even if we wanted to.",1701961099,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-tddypvggbabpq3kxu4cc,task_subcomment,NA
+VisualEditor: Selecting with Shift-arrow selects the heading after a list item,Verified in Firefox 41.0a2 on OS X.,1437770551,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-tddypvggbabpq3kxu4cc,task_subcomment,NA
+VisualEditor: Display of several float:left-ed tables side-by-side inserts slugs that break them up,"Screenshot of the bug as provided by user
+
+Depending on the display format, VE fails to get the display of several tables properly in line. See also attachment; test page here:
+
+http://de.wikipedia.org/wiki/Benutzer:Stefan_Knauf/Dateidurchsuchungsprogramm.cpp
+
+Report:
+
+http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121040382#VisualEditor_ist_nicht_WYSIWYG
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11761}",1375227780,PHID-USER-wswkm7jrcwes3tc7o34k,True,PHID-TASK-wgyduwg7w4wdsktqalds,task_description,open
+VisualEditor: Display of several float:left-ed tables side-by-side inserts slugs that break them up,"Ugh, this is because we put block slugs between these tables, and the tables are floated left.",1375228215,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-wgyduwg7w4wdsktqalds,task_subcomment,NA
+VisualEditor: Reject (or at least loudly warn about) edits that contain pawns or other obvious placeholders,"Rather than simply quietly inserting pawns and other placeholder characters into the page text, VisualEditor should do a sanity-check pre-save and either outright reject or loudly warn about edits that will insert such characters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1375118160,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-sfwbwm73nkcseqpbk5if,task_description,declined
+VisualEditor: Reject (or at least loudly warn about) edits that contain pawns or other obvious placeholders,"The problem of inserting pawns and such is ancient history now, so building a system to detect them is not a good use of time.",1508930263,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-sfwbwm73nkcseqpbk5if,task_subcomment,NA
+VisualEditor: Reject (or at least loudly warn about) edits that contain pawns or other obvious placeholders,"I suggest piggybacking on the existing sanity check code: display the ""your edit may be corrupted"" warning in the save dialog and tag the edit with visualeditor-check.",1375118282,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-sfwbwm73nkcseqpbk5if,task_subcomment,NA
+Allow users to customise keyboard shortcuts,"What it says on the in. Like in most desktop applications, it should be possible for users to customise the keyboard shortcuts to their liking. Including in VisualEditor and source editor.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1374931980,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-hsvzb36avth2iqas7oad,task_description,open
+Allow users to customise keyboard shortcuts,Removed VE reference from the title because it's simply not part of MediaWiki core.,1374938852,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-hsvzb36avth2iqas7oad,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**Author:** `KilliondudeWP`
+
+**Description:**
+The edit summary box currently uses a textarea input box. Current functionality has the return key starting a new line in the textarea, but upon save the edit summary is truncated into one line in the page history (line breaks are turned into spaces). Thus, the textarea box is misleading.
+
+A more sane option would be to use a single line text input box, where the enter key processes the edit rather than starts a new line.
+
+See T40042 and T42034, and specifically T42034#467450.
+",1374899820,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_description,declined
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1465077, @matmarex wrote:
+> even worse in VE than in wikitext editor because the input field is narrower.
+
+Putting a (wider) summary box in the main editor UI would solve {T52961} as well.",1437402576,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Such input box will still not wrap the typed text, which is terrible enough by itself for users, and even worse in VE than in wikitext editor because the input field is narrower.",1437401367,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,How about making it an input box and just set `padding-bottom` to make it //feel// like a textarea?,1437399200,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"As discussed on the patch, assuming that we want the text to wrap, this is **not actually possible to do** for most languages, and an English-only half-solution would be inappropriate. Browsers are really letting us down here.
+
+As I understand, there are two reasons why we would want this, which have separate tasks:
+* {T106325}
+* {T50274}
+
+We should focus on resolving these, which should be possible regardless of the underlying text field used.",1437391823,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Change 212795 abandoned by Bartosz Dziewoński:
+[WIP] TextInputWidget: Allow wrapped singleline inputs
+
+Reason:
+This is not going to be compatible with different text input methods.
+
+[[https://gerrit.wikimedia.org/r/212795]]",1437391169,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"The idea may or may not actually be a good one. It's definitely interesting. The gist is that we dynamically swap the <input type=text> for a <textarea>. It has some funny behavior but sort of works.
+
+The patch above makes it impossible to type a newline into the field, and should let it display the automatic browser's autocompletion when it is single-line. Ed mentioned that it can break with IMEs if you're typing a word and it changes from input to textarea in the middle of it.",1432313088,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Change 212795 had a related patch set uploaded (by Bartosz Dziewoński):
+Allow wrapped singleline inputs
+
+[[https://gerrit.wikimedia.org/r/212795]]
+",1432312920,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"I think I have a pretty good idea on how to implement this, I'll try to do some pre-hackathon hacking on it today.",1432288471,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1302510, @Whatamidoing-WMF wrote:
+> I care whether it **behaves like** the wikitext edit summary in terms of interacting with my web browser.  I want to type a complex edit summary once, and have that edit summary automagically re-appear whenever I start typing it on my next edit.  If you can give me that useful function while making the box a perfect square, then I'm satisfied.  I need the function, not the appearance. 
+
+Yup. IIUC, changing the textarea to a text input line, will solve {T50274} (possibly that should be listed as blocked by this?)
+
+Re: keeping it visually highlighted - do note that the textarea has the bright blue border now, when the field is active, which it is automatically when opened, (but not shown in matmarex's screenshot above), and I think that could be sufficient. 
+
+
+",1432250744,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"I've said this in several places, but I repeat it here:  I don't care what size or shape the edit summary box is on my computer screen.  
+
+I care whether it **behaves like** the wikitext edit summary in terms of interacting with my web browser.  I want to type a complex edit summary once, and have that edit summary automagically re-appear whenever I start typing it on my next edit.  If you can give me that useful function while making the box a perfect square, then I'm satisfied.  I need the function, not the appearance. ",1432241088,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"The last thing I heard is that making the edit summaries any bigger required redesigning //the database// (yes, //that// database), not merely the user interface.",1432240831,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1302437, @awight wrote:
+> Okay, I understand where that's coming from.  On the other hand, sometimes it's really helpful to have a brief summary sentence, then a few more paragraphs of relevant things which fall into the ""why"" category and are therefore more appropriate in a summary or the Talk page than in the main article.
+
+Well, edit summaries are limited to around 200 characters. Changing that limit would involve redesigning the UI, which is doable, but is a fairly big undertaking that should only be done if there's some specific need to change this. I don't think there's a need for that.
+
+> How would you suggest we broaden this discussion?  I'm not sure this is the right place, and donno if wikitech-l is the best mailing list, cos we should involve editors.
+
+I expect that the product folks in the VisualEditor Team will take our input then make an appropriate decision. :-)",1432238326,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Okay, I understand where that's coming from.  On the other hand, sometimes it's really helpful to have a brief summary sentence, then a few more paragraphs of relevant things which fall into the ""why"" category and are therefore more appropriate in a summary or the Talk page than in the main article.
+
+How would you suggest we broaden this discussion?  I'm not sure this is the right place, and donno if wikitech-l is the best mailing list, cos we should involve editors.",1432237819,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1302396, @awight wrote:
+> @Deskana, I'm curious why you say that,
+>> We want users to be fairly brief with their edit summaries
+
+Edit summaries are intended to be quite brief summaries of the edits. I don't think encouraging users to write a lot of text in there is a good idea.",1432236841,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"@Deskana, I'm curious why you say that,
+> We want users to be fairly brief with their edit summaries",1432236748,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,">>! In T54133#1296269, @matmarex wrote:
+> For comparison. The last one looks positively //tiny//.  We'd need to come up with something smart if we were to make it single-line.
+
+That's not necessarily a bad thing. We want users to be fairly brief with their edit summaries, and bigger boxes are more likely to encourage them to write more. Smaller boxes encourage the opposite.
+
+That said, we'd have to be sure that the user's attention isn't drawn to the wrong place; in the last screenshot, the box is so small that the user's attention may not immediately be drawn to that text box. You could try try making the font in the box slightly larger, and slightly increasing the width of the dialogue to compensate.
+
+",1432068967,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"For comparison. The last one looks positively //tiny//.  We'd need to come up with something smart if we were to make it single-line.
+
+| Current edit summary field | {F166629,size=full} |
+| -- |
+| Wikitext editor edit summary field | {F166627,size=full} |
+| -- |
+| Proposed edit summary field (single-line) | {F166624,size=full} |
+| -- |
+",1432045895,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Just merged in very similar task arguing that enter should submit the summary field. (On a similar note, I've proposed using meta + enter as a general shortcut for submitting dialogs in T98105.)
+
+Good points in the comments:
+
+@matmarex:
+>This could be confusing since the summary text field looks like a multiline text input, possibly causing users to accidentally submit with incomplete summaries (which can't be corrected afterwards).
+>
+>It could be interesting to try something else – maybe pressing Enter twice to submit the form, maybe Ctrl+Enter? We should probably do some research.
+>
+>...
+>
+>* Facebook: comments to posts on the timeline are normally single-line (pressing Enter in the text field submits a comment), but you can make them multi-line by pressing Ctrl+Enter or Shift+Enter (or by copy-pasting text with newlines). Pressing Enter submits the comment even if it is multi-line.
+>* My bank has these ""wrapped single-line"" inputs in some fields and pressing Enter always does nothing in them. Accidentally submitting a form could potentially have dire consequences there.
+
+@Deskana:
+>For the advanced user, the current approach where enter adds new lines is counterintuitive. The advanced user not only knows that edit summaries cannot be multi-line, but it also feels wrong because they're also used to enter submitting their edit.
+>
+>For the new user, the current approach feels misleading, as you're giving the user an expectation that edit summaries can be multi-lined when in fact they cannot. This user has no expectations about enter submitting the edit, so probably doesn't care too much about that.
+>
+>I think the best approach would be to make the edit summary box single-line, and make enter submit the edit.",1431978382,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"(In reply to Spinningspark from comment #10)
+
+However, the input box should be large enough to accomodate the maximum permitted length of edit summary, even if that means using two lines.",1411393509,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"(In reply to Amir E. Aharoni from comment #9)
+> Is it possible to meet in the middle: To show it as a textarea, but to allow
+> saving using Enter/Return? And maybe provide autocomplete?
+
+That will lead to another problem: newbies will accidentally save before they have finished entering the summary.
+
+The fact is, the edit summary *is not* a text area and should not be displayed as such.  It can only ever be a single line of text.  That is what should be shown.  Enter should initiate a save.",1411391908,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Is it possible to meet in the middle: To show it as a textarea, but to allow saving using Enter/Return? And maybe provide autocomplete?",1409247587,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"Bug 48274 seems to cover the same ground, and was one of the first things I found problematic with VE: those of us who do a lot of regular work on many different articles usually have a set of standardised edit summaries which can convey a lot of useful information, with links, to help other editors. The autocomplete facility provided by browsers for a one-line input box worked well.",1375521561,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**JohnCD67** wrote:
+
+Killiondude's comment 1 is an significant usability point - for repetitive tasks it is very helpful that the browser pops up a list of suggestions to click on, which is context-sensitive and based on previous usage. I did not realise how helpful that was until with VE I found myself having to type the full edit summary each time.",1375440006,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"(In reply to comment #5)
+> > Sure, but collapsing the box down to a single line would de-emphasise the
+> > edit summary, however, and turn it back into ""a mysterious text box"" that
+> > uses ""feel free to skip"".
+> 
+> Why would it?
+> 
+> It's still hidden behind a modal dialog. I will wager that editors still feel
+> forced to fill it in simply because it is there.
+
+The numbers went up when we switched from inputbox to textarea. Expecting them not to fall when we reverse that change seems unlikely to me.",1375423283,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**sk8er_97456** wrote:
+
+> Sure, but collapsing the box down to a single line would de-emphasise the
+> edit
+> summary, however, and turn it back into ""a mysterious text box"" that uses
+> ""feel
+> free to skip"".
+
+Why would it?
+
+It's still hidden behind a modal dialog. I will wager that editors still feel forced to fill it in simply because it is there.",1375418475,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"(In reply to comment #3)
+> I seriously doubt that that is the reason you have a higher incidence of edit
+> summaries. What you did in parallel to making it a textarea was that you hid
+> the ""Save page"" final submit button behind a dialog that prominently presents
+> the box for an edit summary. Users no longer feel free to skip a mysterious
+> text box and click ""Save page"" right away, the look and feel of the modal
+> dialog forces them to consider filling it out in full before proceeding.
+> That's why you're getting more edit summaries.
+
+Sure, but collapsing the box down to a single line would de-emphasise the edit summary, however, and turn it back into ""a mysterious text box"" that uses ""feel free to skip"".",1375415740,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**sk8er_97456** wrote:
+
+I seriously doubt that that is the reason you have a higher incidence of edit summaries. What you did in parallel to making it a textarea was that you hid the ""Save page"" final submit button behind a dialog that prominently presents the box for an edit summary. Users no longer feel free to skip a mysterious text box and click ""Save page"" right away, the look and feel of the modal dialog forces them to consider filling it out in full before proceeding. That's why you're getting more edit summaries.",1375414773,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"By making the summary a textarea rather than an inputbox we've seen a radically-greater number of editors (especially, anonymous and new editors) entering edit summaries for their edits. I think we should think very seriously about the impact of such a change before just making it.",1375388426,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+VisualEditor: Edit summary box should be a text input box and not textarea,"**KilliondudeWP** wrote:
+
+Another issue brought up with having a text area box is that previously entered summaries are not suggested. Most browsers suggest prior terms entered into text input boxes, this allowing editors to choose from their (frequently) used summaries.
+
+https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Improvements&oldid=566754323#Autofill_edit_summary",1375384096,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-y2wr4truqmwwemxh72yk,task_subcomment,NA
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","Steps to reproduce
+1. Create a page with a linefeed
+2. Edit it in VE
+3. Copy the block containing the ↵
+4. In a new VE window, paste
+
+Expected results:
+VE smartly removes the ↵
+
+Actual results:
+The ↵ is pasted into the second VE as a literal character
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=53828",1374849360,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-bmgl5fdektu6pj27wpm4,task_description,resolved
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","Just want to capture that in many cases the user could want the ↵ to mean ""break this line and create a new line""
+
+I don't think this is 100% of the time, but enough that we should think about it.",1378923579,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-bmgl5fdektu6pj27wpm4,task_subcomment,NA
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","Change 83222 merged by jenkins-bot:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",1378923311,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bmgl5fdektu6pj27wpm4,task_subcomment,NA
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","Change 83222 had a related patch set uploaded by Esanders:
+The Great [...] Rewrite of 2013: Clipboard edition
+
+https://gerrit.wikimedia.org/r/83222",1378548144,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bmgl5fdektu6pj27wpm4,task_subcomment,NA
+"VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder","References are also pasted as [1], etc",1374849508,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-bmgl5fdektu6pj27wpm4,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"As perhaps a simpler case of copy and paste from 'external sources', pasting richtext that copied from the same wiki should work seamlessly.
+
+In many cases, the 'html' already has the metadata needed. e.g. the image, or text-with-wikilinks, even the categories, should be paste-able
+
+https://en.wikipedia.org/wiki/Pelham_Parkway
+
+With a tiny bit of additional html attributes, the navbox templates ({{Parkways in New York City}} & {{Bronx streets}}) could be copied as they are self-contained units - no parameter were used to invoke them.
+
+Again with a bit of markup, the Infobox pasted into a VE session, but only the shell transclusion could set up - the parameters would need to be entered by the user in the VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51547",1374842820,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jg5w64dq46rdbpyabqp7,task_description,open
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,This should be largely addressed as we transition to #parsoid-read-views.,1700062714,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"NB Firefox throws away RDFa properties when copying, so this won't be possible without JavaScript intercepting copy events, as it stands:
+
+https://jsfiddle.net/L9q81y02/2/",1535732717,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"NB Firefox throws away RDFa properties when copying, so this won't be possible without JavaScript intercepting copy events, as it stands.",1390316714,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,*** Bug 52787 has been marked as a duplicate of this bug. ***,1383280378,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"(In reply to comment #2)
+> This is a separate problem James.  This is about copying from a non-VE wiki
+> page on the same wiki.  That is very different from copying from another VE,
+> or another website.  As I eluded to in my initial enhancement request,
+> additional HTML needs to be emitted into the read version of the wiki page in
+> order that a VE could pick up the name of the template to use when pasting it
+> into a VE.
+
+Oh, sorry, I missed your comment about adding RDFa/etc. hinting to highlight what DOM elements are what.
+
+""Tiny"" is not remotely the correct word - this will require us to replace the entire read DOM with the same output as Parsoid provides VisualEditor, which is vaguely scheduled to be considered for research/analysis in about a year's time (this is so far off in the distance there isn't even a bug for it yet). Recasting.",1374881208,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"This is a separate problem James.  This is about copying from a non-VE wiki page on the same wiki.  That is very different from copying from another VE, or another website.  As I eluded to in my initial enhancement request, additional HTML needs to be emitted into the read version of the wiki page in order that a VE could pick up the name of the template to use when pasting it into a VE.",1374880786,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces,"This is not simpler. This is the same. The problem is not taking in rich text (from any source), it's inserting it sanely into VisualEditor's ContentEditable surface, sadly. Merging.
+
+*** This bug has been marked as a duplicate of bug 33105 ***",1374880349,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jg5w64dq46rdbpyabqp7,task_subcomment,NA
+"VisualEditor: Paste in Firefox with privacy option enabled behaves strangely: rich text appears, but in reality paste has failed","The paste operation on Firefox behaves strangely when dom.event.clipboardevents.enabled = false
+(which is exposed in the UI of several extensions)
+
+When disabled, rich text appears to have been pasted into VE, with links in blue (but the link isnt editable), but in reality the paste has failed to change the underlying data in VE.
+
+If the user starts typing, the pasted richtext disappears.
+
+If the user saves immediately after the paste, the richtext remains visible in the VE, but the save only adds blank lines instead.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374841620,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-yluaahg4ge2upl35udiq,task_description,open
+"VisualEditor: Paste in Firefox with privacy option enabled behaves strangely: rich text appears, but in reality paste has failed",[[ https://pl.wikipedia.org/w/index.php?title=Wikipedia:Kawiarenka/Kwestie_techniczne&diff=prev&oldid=74782151 | September 2024 report from pl.wikipedia ]] - need to confirm about:config settings of the reporter,1727568654,PHID-USER-qduasitr62ffvc5eiivd,False,PHID-TASK-yluaahg4ge2upl35udiq,task_subcomment,NA
+VisualEditor: Transclusion dialog should also display the actual parameter name as well as the display name,"When you start a new transclusion dialog for a template which has the templatedata specified it shows a list of the parameters with the label on the left and the actual parameters in grey on the right. This is good for power users who know the parameters. 
+
+When you choose a parameter which has a value specified you can see the label, but you can't see what the actual parameter is. This would be quite handy and could use the same grey style as in the list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374838980,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-i65x4dklyvkvelmyu7om,task_description,open
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"Wikipedias in some languages, among them Polish, Russian, Ukrainian and Hebrew, have a gadget that shows a list of frequent edit summaries near the edit summary field in source editing mode.
+
+Here are the source samples:
+
+Polish: https://pl.wikipedia.org/wiki/MediaWiki:Gadget-edit-summaries.js
+Hebrew: https://he.wikipedia.org/wiki/MediaWiki:Gadget-Summarieslist.js
+
+Many users in the Hebrew Wikipedia complained about the lack of this gadget in the VisualEditor. This could be an enhancement request, but given that for several languages it's an integral part of the editing interface for these languages, it's a regression for them.
+
+Adding this as a feature should be very easy, given that it's quite simple and the existing gadgets' code can be reused. Localization and customization for every project can be done on a MediaWiki page with a list of summaries for that project.
+
+--------------------------
+**See Also**:
+{T50274}",1374828360,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-odseemabxyqbdz2dgloa,task_description,resolved
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,Task was to update gadgets which is done. Please re-file if you think this functionality needs to be upstreamed.,1561117513,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"The relevant gadgets currently seem to support VE (And so does the english wikipedia version of this gadget). Do we keep this open as a core VE improvement ? 
+
+I'd think that considering the experiences with iOS mobile App canned edit summaries some thorough UX analysis and creative thinking would have to go into this to make such a thing useful for both inexperienced and seasoned editors honestly.",1496828368,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"Yes, and FWIW, the he.wikipedia veteran editors welcomed this change, done by @eranroz (thanks, Eran).
+
+It's available in the mobile apps in all languages, and I wonder - can @deskana provide any info about whether the mobile editors use it and like it? And what do the recent changes patrolers in different languages think about it?",1420985690,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"Both of the gadgets linked have been extended to also work with VisualEditor, by the way.",1420984413,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,"(In reply to comment #1)
+> I'm reminded of bug 48274.
+
+It's somewhat related, but definitely not the same. What I'm talking about are very frequent summaries in a project. Every project community decides what it needs, but usually it's common generic stuff like ""spelling"", ""adding links"", ""wikification"", ""removing unreferenced content"", ""copyediting"" etc.",1374829478,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+VisualEditor: Provide buttons for locally-configured frequent edit summary contents,I'm reminded of bug 48274.,1374828543,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-odseemabxyqbdz2dgloa,task_subcomment,NA
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","Steps to reproduce:
+1. Open VE on a sandbox
+2. In a different window, delete the sandbox
+3. In the VE window, change the text in the sandbox and save the page
+
+Expected results:
+Something similar to the SE, which asks ""
+User xxx (talk) deleted this article after you started editing it, with a reason of:
+
+    blah 
+
+Please confirm that you really want to recreate this article."" with a checkbox
+
+Actual results:
+Backend error message is displayed, and there is no option to ignore this error.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374805260,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-pyseattqnc7yj362nndp,task_description,resolved
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","Change 169976 merged by jenkins-bot:
+Catch pagedeleted errors and give the ability to re-create the page
+
+[[https://gerrit.wikimedia.org/r/169976]]",1416944580,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pyseattqnc7yj362nndp,task_subcomment,NA
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","Change 169976 had a related patch set uploaded by Alex Monk:
+Catch pagedeleted errors and give the ability to re-create the page
+
+https://gerrit.wikimedia.org/r/169976",1414630160,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pyseattqnc7yj362nndp,task_subcomment,NA
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","I currently get this error in Parsoid:
+
+TypeError: Cannot read property 'length' of null
+    at Object.result.parse (eval at <anonymous> (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.tokenizer.peg.js:97:44), <anonymous>:18347:34)
+    at PegTokenizer.tokenizeAsync (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.tokenizer.peg.js:135:25)
+    at PegTokenizer._processText (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.tokenizer.peg.js:124:8)
+    at PegTokenizer.process (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.tokenizer.peg.js:38:7)
+    at ParserPipeline.process (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.parser.js:439:21)
+    at ParserPipeline.processToplevelDoc (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.parser.js:455:21)
+    at SSP.parseOriginalSource (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.SelectiveSerializer.js:143:17)
+    at TemplateRequest.<anonymous> (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.Util.js:1266:3)
+    at TemplateRequest.g (events.js:180:16)
+    at Object.processSome [as _onImmediate] (/var/www/MediaWiki/Git/extensions/VisualEditor/parsoid/lib/mediawiki.ApiRequest.js:123:17)
+worker 11363 died (1), restarting.",1397917595,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-pyseattqnc7yj362nndp,task_subcomment,NA
+"When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate‎>","The response is now:
+
+| Error: The page has been deleted since you fetched its timestamp
+
+I guess we should inherit this message, however. Changing to an enhancement.",1385395630,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pyseattqnc7yj362nndp,task_subcomment,NA
+VisualEditor: Make ve.ce.MWBlockImageNode.prototype.getCssClass nicer,"It should look at the attributes directly rather than take them as parameters. We should move the folding of all sorts of types into 'default' or 'none' in there. We should set the CSS class in one place rather than two different ones.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374792420,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-onafhjfu75ziw55sv6d6,task_description,open
+Merge Poem extension into MediaWiki core,"The Poem extension has almost as much extension setup as it has functionality. Bundling it with MediaWiki is silly, it should simply be merged into core.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement
+**Whiteboard**: migrate Poem extension bugs to core post-resolution",1374788640,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_description,open
+Merge Poem extension into MediaWiki core,"For clarity I have split the work plan in my previous comment to a new task, {T194651}.",1526299289,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"We had an IRC discussion in #mediawiki-parsoid about this. 
+
+* We'll get rid of the special handling of `:`, but preserve the existing appearance by using CSS. So end users won't notice a change, unless they have custom CSS rules with selectors like `div.poem > span` or `.mw-poem-indented`, which will not work anymore. This will address T123216.
+* The compact attribute is going to be killed. (We didn't actually discuss this, but everyone appears to agree that it is useless.) This will address T16910.
+* We'll try to solve the T124144 <hr> issue as well. Existing patches for that task will be insufficient to deal with the problem when <pre> is used. 
+* Once those things are done, @ssastry suggested to follow this plan:
+** get feedback from Wikisource
+** do visual diffs if required as part of that
+** merge the patch https://gerrit.wikimedia.org/r/#/c/328887/
+** evaluate if there is anything we want to deprecate via linter (e.g. intra-line whitespace)
+** reevaluate whether we want to merge this into core as <lines> as the original proposal stood
+
+This is arguably the wrong task for this work, since we are not actually merging the extension (yet) - the current flurry of work is a precursor to that.",1522959725,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"So, looking at https://gerrit.wikimedia.org/r/328887 it seems that, if that patch is merged, the primary difference between `<poem>` and `<pre>` handling in core is:
+* `<poem>` generates an empty span with `margin-left:1em` for wikitext like `: foo`.  But I think we could probably tweak the CSS so that the rendering of the standard parser output for `:foo` (aka, `<dl><dd>foo</dd></dl>` is the same.
+* `<poem>` respects leading whitespace, but compresses intraline whitespace.  This is currently being done by a combination of CSS and manually substituting leading whitespace with `&nbsp;`.  In order to clean this up, the easiest thing would be to stop compressing intraline whitespace.  We'd either do that for a new `<lines>` tag (and merge the `<lines>` semantics into core) or else do a wikilint type project to simply removing inadvertent intraline whitespace.  Depending on how prevalent it is, the latter might not be too hard.
+
+What else am I missing?",1522871580,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Also, it would be nice if we could have some more attention on https://gerrit.wikimedia.org/r/330896/. This is an obscure bug in the PHP parser that is only triggered by certain wikitext content generated by a tag extension (it can't be triggered by user-entered wikitext), and it blocks the re-implementation of `<poem>` using the `<pre>` tag.",1521288301,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I think https://gerrit.wikimedia.org/r/106861 is probably still relevant today (or if there is no appetite for merging into core, then the changes can be rebased on top of the extension, as seen in https://gerrit.wikimedia.org/r/#/c/328887/). I seem to recall that it fixes a number of bugs in the Poem implementation, not all of which are tracked in Phabricator. Although this was 4 years ago, so I might be wrong.",1521293089,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I think https://gerrit.wikimedia.org/r/106861 is probably still relevant today (or if there is no appetite for merging into core, then the changes can be rebased on top of the extension). I seem to recall that it fixes a number of bugs in the Poem implementation, not all of which are tracked in Phabricator. Although this was 4 years ago, so I might be wrong.",1521288123,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"This zombie bug has lurched to life again because of {T188478}.
+
+Any chance we can come up with a sane semantics for `<poem>`/`<lines>` so that we aren't plunged into eternal darkness by trying to make a Parsoid extension bug-for-bug compatible with `<poem>`?  We have fancy new linting tools that (in theory) could help auto-migrate uses of `<poem>` if we can agree on a better replacement.",1521232200,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 abandoned by TTO:
+Merge Poem extension into core
+
+Reason:
+I don't intend to pursue this anymore. However, reviewers here might be interested in https://gerrit.wikimedia.org/r/328887 and https://gerrit.wikimedia.org/r/328888 .
+
+[[https://gerrit.wikimedia.org/r/106861]]",1482494427,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I'm not really interested in this anymore. Instead, I might try getting the automatic line numbering functionality requested in T15644 into the Poem extension, which would make the Poem extension a bit bigger and more worthwhile.",1482474275,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,">>! In T54061#1672245, @cscott wrote:
+> In particular, I'm interested in hearing more from @GOIII about:
+>> . . .
+> Lets get a spec for `<lines>` written down in such a way that we can discuss issues like this:
+
+> * Should the tags be forced to be on their own lines?  (The current implementation doesn't force this.)
+Depends. Will the new tag mimic the standard behavior of a <DIV> attribute's //display:block// or the behavior of a <P> attribute's //display:block// under the wiki mark-up/parser/parsoid? 
+
+The whole damnblasted issue comes back first and formost to the auto insertion of an opening <P> tag at every seemingly first detected line start. That's the current quirk; whether or not content placement starts after //or// under the poem tag. In other terms using the basic underlying html when it comes to the <poem> tag, it's ....
+
+<poem>First line
+<p>second line</br>
+third line</br>
+last line</p></poem>
+
+... versus ...
+
+<poem>
+<p>First line</br>
+second line</br>
+third line</br>
+last line</p>
+</poem>
+
+The 2nd version is //closer// to reflecting normal/expected behavior based on the ""substitution"" of <poem> for <div> but its still not quite right because of the attributes <p> automatically follows as defined elsewhere by some number of .css files 'handed down' by mediawiki by default. The optimal ""underlying"" html should behave as a true DIV tag (//display:block//) should and there should be no <P> element or behavior anywhere in play here.
+
+Taking the same two possible placements of content start (immediately after or immediately under) as above but substituting <div> for <poem>, the ""underlying"" html should go something like this ... 
+
+<div class=poem>First line</br>
+second line</br>
+third line</br>
+last line</br></div>
+
+... versus ...
+
+<div class=poem>
+First line</br>
+second line</br>
+third line</br>
+last line</br>
+</div>
+
+Obviously, consensus still needs to be reached whether or not there should be a </br> at the end of the 'last line' found immediately before the closing tag, but regardless of //after// or //under// placement by the contributor, both render the same. The takeaway here should be __killing the presence and/or behavior of that mark-up induced opening <p> tag for any of this to truly be worthwhile imho__.
+ 
+> * Can you write `<lines class=""foo"">`?  Does this override the default ""poem"" and ""mw-lines"" classes, or add to them?  Is this sufficient for the different styling @GOIII describes?  (The current implementation doesn't allow extra classes.)
+Imho, manually adding a class= statement should add or enhance the default. 
+
+> * What should the Parsoid representation be?
+Not sure what exactly you're looking for here
+
+> * What if somebody writes `<pre class=""poem mw-lines"">` in wikitext?  That's valid wikitext.  Should Parsoid try to re-serialize this as a `<lines>` tag?
+Probably not as the <pre> tag introduces background-color and borders which is not likely to be in high demand as far as Wikisource goes. I can't speak for other projects however.
+
+I'm not even sure the current <pre> scheme follows the ""new"" css3 properties of //white-space: pre-wrap// or //white-space: pre-line// for that matter. 
+
+> * Generally styles hard-coded by mediawiki core are prefixed.  The `poem` class is not.
+I would hope the accepted practices and/or appropriate procedures would dictate this.
+
+> * If `<poem>` is aliased to `<lines>`, are we going to break all of wikisource overnight?
+Building an all encompassing testbed on //test2.wikipedia.org// to experiment against prior to roll out seems like the logical way to address such concerns in my view. 
+
+> * Is a recursive parse strategy really appropriate?  It means that `<lines>` and `<pre>` are going to grow additional inconsistencies on the edge cases.  For example, `'''foo<lines>bar'''bat` could get rather confused about its `<b>`s. 
+I'd need more clarity re: the direction ultimately taken regarding the earlier points to reply here 
+
+",1443489871,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"In particular, I'm interested in hearing more from @GOIII about:
+> force the opening and closing poem tags to always reside on their own lines
+and
+> ways to use empty inline-blocks to ''handle'' not only stanza spacing; but indentation and eol padding as well. Making attribute manipulation easier through the opening (margin-top) or closing (margin-bottom) tags of Line itself could dramatically cut down on stuff like that.
+Lets get a spec for `<lines>` written down in such a way that we can discuss issues like this:
+* Should the tags be forced to be on their own lines?  (The current implementation doesn't force this.)
+* Can you write `<lines class=""foo"">`?  Does this override the default ""poem"" and ""mw-lines"" classes, or add to them?  Is this sufficient for the different styling @GOIII describes?  (The current implementation doesn't allow extra classes.)
+* What should the Parsoid representation be?
+* What if somebody writes `<pre class=""poem mw-lines"">` in wikitext?  That's valid wikitext.  Should Parsoid try to re-serialize this as a `<lines>` tag?
+* Generally styles hard-coded by mediawiki core are prefixed.  The `poem` class is not.
+* If `<poem>` is aliased to `<lines>`, are we going to break all of wikisource overnight?
+* Is a recursive parse strategy really appropriate?  It means that `<lines>` and `<pre>` are going to grow additional inconsistencies on the edge cases.  For example, `'''foo<lines>bar'''bat` could get rather confused about its `<b>`s. ",1443122831,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"From Parsoid's perspective, the biggest problem with `<lines>` is unclear semantics.
+
+I suggest that this patch go through the RFC process first.  Let's write up a document which describes exactly how we want `<lines>` to behave.  We should also discuss deployment strategy in the RFC -- should we turn off support in core until Parsoid and VE also support it?  Or implement stopgap support which doesn't allow editing sections which contain `<lines>` (treating it an an ""unknown extension""), or what?
+
+And what is our strategy for migrating existing `<poem>` content to `<lines>`?  Is there an automatic translation?  Or are some details of the semantics going to trip us up when we try to convert existing content?
+
+As @GOIII states, our paragraph handling in the wikitext parser is already extremely complex, and there are a lot of existing workarounds which depend on details of `<poem>` in order to obtain specific effects in poetry.  If we're going to create a new feature, let's make sure it can actually handle all the things that folks want it to do, without crazy hacks.",1443121493,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"> **Merge Poem extension into MediaWiki core**
+Well now.... I've found the most interesting patch to watch for 2015.  If //$paragraphStack// is going to have a [greater] role when it comes to Poem's application - I'm sure no harm can ever come of it.
+</sarcasm off>
+
+Seriously - I hope whenever this move goes through, its given a week of vetting on test/test2 before its deployed to the usual suspects in a formal build. And, while I'm of like mind in the assessment it should have never existed in the manner that it has to date & the //Line//s alternative would be the best route to follow - there are sooo many people that depend on it on an almost daily basis just on Wikisource alone that I would not have the nuts to screw around with it like this.
+
+Truthfully, the issues with the tag to date have mostly been over the User:s response on occasion to the parser's `<p><br /></p>` effect compounded by the esoteric formatting typically done via template are both really where the ''blame'' should go than anything found in the extension itself. Admittedly, the choice //not// to force the opening and closing poem tags to always reside on their __own lines__ upon save & rendering starting on day-one with it's introduction sure hasn't helped matters either.
+
+I implore you to mirror `.mw-body`s definition of `P` rather than the one(s) found in `Elements.css` -- those values are all long usurped by the time the page finishes loading its 1st click-in of the session. You'll find that `0.1`//em// less between the two definitions in //margin-top// is hard to catch initially... until the `1.5`em `line-height` setting is replaced [again?]  -- setting it  [back?] to //inherit// that is.
+
+The last thing that comes mind would be more of an enhancement (like in T15644) than a bug . //Had// Poem been crafted to force it's tags to their own line/line-starts, the closing tag of the previous stanza would ''land'' right above the opening tag of the stanza that followed more often than not. This would be desirable because the ''gap'' between verses or stanzas are rarely as small as the predefined paragraph's are. Contributor's frequently came up with all sorts of ways to use empty inline-blocks to ''handle'' not only stanza spacing; but indentation and eol padding as well. Making attribute manipulation easier through the opening (//margin-top//) or closing (//margin-bottom//) tags of //Line// itself could dramatically cut down on stuff like that.",1420497073,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"> **Merge Poem extension into MediaWiki core**
+Well now.... I've found the most interesting patch to watch for 2015.  If //$paragraphStack// is going to have a [greater] role when it comes to Poem's application - I'm sure no harm can ever come of it.
+</sarcasm off>
+
+Seriously - I hope whenever this move goes through, its given a week of vetting on test/test2 before its deployed to the usual suspects in a formal build. And, while I'm of like mind in the assessment it should have never existed in the manner that it has to date & the //lines// alternative would be the best route to follow - there are sooo many people that depend on it on an almost daily basis just on Wikisource alone that I would not have the nuts to screw around with it like this.
+
+Truthfully, the issues with the tag to date have mostly been over the User:s response on occasion to the parser's `<p><br /></p>` effect compounded by the esoteric formatting typically done via template are both really where the ''blame'' should go than anything found in the extension itself. Admittedly, the choice //not// to force the opening and closing poem tags to always reside on their __own lines__ upon save & rendering starting on day-one with it's introduction sure hasn't helped matters either.
+
+I implore you to mirror `.mw-body`s definition of `P` rather than the one(s) found in `Elements.css` -- those values are all long usurped by the time the page finishes loading its 1st click-in of the session. You'll find that `0.1`//em// less between the two definitions in //margin-top// is hard to catch initially... until the `1.5`em `line-height` setting is replaced [again?]  -- setting it  [back?] to //inherit// that is.
+
+The last thing that comes mind would be more of an enhancement (like in T15644) than a bug . //Had// Poem been crafted to force it's tags to their own line/line-starts, the closing tag of the previous stanza would ''land'' right above the opening tag of the stanza that followed more often than not. This would be desirable because the ''gap'' between verses or stanzas are rarely as small as the predefined paragraph's are. Contributor's frequently came up with all sorts of ways to use empty inline-blocks to ''handle'' not only stanza spacing; but indentation and eol padding as well. Making attribute manipulation easier through the opening (//margin-top//) or closing (//margin-bottom) tags of //Line// itself could dramatically cut down on stuff like that.",1420453788,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"> **Merge Poem extension into MediaWiki core**
+Well now.... I've found the most interesting patch to watch for 2015.  If //$paragraphStack// is going to have a [greater] role when it comes to Poem's application - I'm sure no harm can ever come of it.
+</sarcasm off>
+
+Seriously - I hope whenever this move goes through, its given a week of vetting on test/test2 before its deployed to the usual suspects in a formal build. And, while I'm of like mind in the assessment it should have never existed in the manner that it has to date & the //lines// alternative would be the best route to follow - there are sooo many people that depend on it on an almost daily basis just on Wikisource alone that I would not have the nuts to screw around with it like this.
+
+Truthfully, the issues with the tag to date have mostly been over the User:s response on occasion to the parser's `<p><br /></p>` effect compounded by the esoteric formatting typically done via template are both really where the ''blame'' should go than anything found in the extension itself. Admittedly, the choice //not// to force the opening and closing poem tags to always reside on their __own lines__ upon save & rendering day-one sure hasn't helped matters.
+
+I implore you to mirror `.mw-body`s definition of `P` rather than the one(s) found in `Elements.css` -- those values are all long usurped by the time the page finishes loading its 1st click-in of the session. You'll find that `0.1`//em// less between the two definitions in //margin-top// is hard to catch initially... until the `1.5`em `line-height` setting is replaced [again?]  -- setting it  [back?] to //inherit// that is.
+
+The last thing that comes mind would be more of an enhancement (like in T15644) than a bug . //Had// Poem been crafted to force it's tags to their own line/line-starts, the closing tag of the previous stanza would ''land'' right above the opening tag of the stanza that followed more often than not. This would be desirable because the ''gap'' between verses or stanzas are rarely as small as the predefined paragraph's are. Contributor's frequently came up with all sorts of ways to use empty inline-blocks to ''handle'' not only stanza spacing; but indentation and eol padding as well. Making attribute manipulation easier through //line// itself could dramatically cut down on stuff like that.",1420453542,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 had a related patch set uploaded (by TTO):
+Merge Poem extension into core
+
+[[https://gerrit.wikimedia.org/r/106861]]
+
+#patch-for-review",1419905484,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #42)
+> (In reply to comment #38)
+>> A Global Message Delivery to all Wikisource Scriptoriums/Village pump is
+>> higly recommended
+> 
+> MZMcBride, could you advise how feasible this would be?
+
+I think a mention in [[m:Tech/News]] is sufficient here. Nothing is breaking, as I understand it, so this news is purely informational: ""In addition to <poem>, you can also now use <some other tag name>.""
+
+If you really want to send a global message, you can use [[m:MassMessage]].",1406091878,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to James Forrester from comment #49)
+> I don't particularly mind it being merged into core from an ""editing"" POV,
+> but it is ""yet another feature"" in MediaWiki core which we're meant to be
+> making leaner, faster and more flexible, which this roughly feels like it
+> goes against.
+> 
+> The Parsoid-land changes aren't too hard to handle, I believe, so that
+> shouldn't block this.
+
+It's also another one of those features that will come in at least slightly handy on almost every wiki, though. It's deployed on a significant percentage of wikis, and on those on which it isn't deployed, the users probably wish it were deployed when they run into situations that call for its use. https://wikiapiary.com/wiki/Extension:Poem
+
+Admittedly, it's not as important as, say, ParserFunctions or Cite (both of which should probably be merged to the core, by the way). But it's not very harmful, either.",1406061505,PHID-USER-h3izjiozzysppsokit7l,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to Kunal Mehta (Legoktm) from comment #48)
+> (In reply to Tpt from comment #45)
+> > Yes, you have right with ""mw-lines"".
+> > 
+> > I understand your concern with differing functionality that would require
+> > two buttons in the editing interface (it's the major concern I see). I think
+> > we should have feedback from the VisualEditor team.
+> 
+> James, do you/your team have an opinion?
+
+I don't particularly mind it being merged into core from an ""editing"" POV, but it is ""yet another feature"" in MediaWiki core which we're meant to be making leaner, faster and more flexible, which this roughly feels like it goes against.
+
+The Parsoid-land changes aren't too hard to handle, I believe, so that shouldn't block this.",1406060775,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to Tpt from comment #45)
+> Yes, you have right with ""mw-lines"".
+> 
+> I understand your concern with differing functionality that would require
+> two buttons in the editing interface (it's the major concern I see). I think
+> we should have feedback from the VisualEditor team.
+
+James, do you/your team have an opinion?",1406017589,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 restored by Legoktm:
+Merge Poem extension into core
+
+Reason:
+I think this is a valuable changeset that should be pursued.
+
+https://gerrit.wikimedia.org/r/106861",1406016597,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 abandoned by Krinkle:
+Merge Poem extension into core
+
+Reason:
+Closing for now to clear pending review dashboard. Feel free to re-open when you can work on it.
+
+https://gerrit.wikimedia.org/r/106861",1405886331,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Yes, you have right with ""mw-lines"".
+
+I understand your concern with differing functionality that would require two buttons in the editing interface (it's the major concern I see). I think we should have feedback from the VisualEditor team.",1392368977,PHID-USER-5paybpgtxjrhikdos3p5,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"That's a very good suggestion, Tpt. I would be inclined to call the CSS class something more like ""mw-lines"" or similar, to comply with modern class naming standards.
+
+However I wonder if it is really a good idea to provide differing functionality, however minor, between <poem> and <lines>?",1392368471,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"As I believe that <poem> tag will be kept as an alias forever, it may be interesting to make <poem> and <lines> semantic a little bit different:
+- <lines> would be presentational only and the output will have the ""lines"" class as in <pre class=""lines"">
+- <poem> has the same presentational effect as <lines> but use the ""poem"" class to specify that the content is a poem as in <pre class=""lines poem"">
+
+It won't break sites CSS because the current pages only use the poem tags. If wikis wants to use their custom CSS for <poem> tag with all <lines> tags, they will only have to change ""poem"" by ""lines"" in their rules.",1392367071,PHID-USER-5paybpgtxjrhikdos3p5,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #37)
+> (In reply to comment #31)
+> > 1) In comment 29, Jesús Martínez Novo made a good suggestion to more widely
+> > publicize the new <lines> name before it gets committed.  
+> > A mailing list thread might be a good way to
+> > kick off this discussion.
+> 
+> I'll post one.
+
+http://lists.wikimedia.org/pipermail/wikitech-l/2014-February/074337.html
+
+No replies, so I assume no-one is concerned.
+
+(In reply to comment #38)
+> A Global Message Delivery to all Wikisource Scriptoriums/Village pump is
+> higly recommended
+
+MZMcBride, could you advise how feasible this would be?",1392363249,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #40)
+> The <poem/> tag usage on texts that does not contains poems, only the need to
+> parse line breaks in a different behaviour, isn't the feature itself provided
+> by the extension, only a very interesting side effect.
+
+Please read the preceding comments in this bug report. The reason why this tag is going to be made available under the name <lines> is to emphasise that is not only used for poems, but for other texts that require the preservation of line breaks. This is not merely a ""side effect"", but the key feature of this tag.
+
+> IMHO before merging Extension:Poem into core it firstly needs to addresses
+> all
+> expected behaviours in their original expected feature,
+
+A merge of an extension into core, means taking the extension's existing functionality, and placing it in MediaWiki core. It does not mean we add extra features at the same time.
+
+The Poem extension only provides poem-related (line break preservation) functionality, so that is all that core is getting in this merge. This is not the place to discuss other ""original expected features"".",1392079227,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"The <poem/> tag usage on texts that does not contains poems, only the need to parse line breaks in a different behaviour, isn't the feature itself provided by the extension, only a very interesting side effect.
+
+It looks to me like in very old MediaWiki versions without file undeletion support: media deletion at that time resulted in less disk space being used. But that aren't the feature, only a side effect.
+
+IMHO before merging Extension:Poem into core it firstly needs to addresses all expected behaviours in their original expected feature, ie to provide quickly and in easy ways alternatives to format text portions based in a given form of language.",1392077997,PHID-USER-gu24fgh5wu7isjb4g5b7,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #38)
+> In the time that <poem/> tag arised on Wikisources, we have also asked for a
+> <prose/> tag (See bug 6810).
+
+That is an entirely separate issue. The presence or absence of a <prose> tag is not going to affect the resolution of this bug.
+
+> As you can see on [3] and [4], the formatting isn't the same currently
+> adopted
+> in <poem/> tag, so the current consensus to set <poem/> as an alias for a new
+> tag name isn't viable.
+
+I don't understand your point here. What has this got to do with the <poem> tag?",1392076482,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"A Global Message Delivery to all Wikisource Scriptoriums/Village pump is higly recommended, since this extension was firtly developed to Wikisource wikis and latter enabled on all Wikimedia wikis [1] [2].
+
+In the time that <poem/> tag arised on Wikisources, we have also asked for a <prose/> tag (See bug 6810).
+
+Unfortunately at that time the developers picked what was most easy to then instead of what is more user intuitive (sorry, but <poem>foo</poem> and {{prose start}}foo{{prose end}} don't makes sense to newcomers (#c6).
+
+As you can see on [3] and [4], the formatting isn't the same currently adopted in <poem/> tag, so the current consensus to set <poem/> as an alias for a new tag name isn't viable.
+
+[1] - https://wikitech.wikimedia.org/wiki/Server_admin_log/Archive_7#June_23
+
+[2] - https://wikitech.wikimedia.org/wiki/Server_admin_log/Archive_10#February_7
+
+[3] - https://en.wikisource.org/wiki/Template:Prose
+
+[4] - https://fr.wikisource.org/w/index.php?title=MediaWiki:Common.css (classe prose : PERIMÉE, utiliser text )
+
+[[:m:User:555]]",1392048878,PHID-USER-gu24fgh5wu7isjb4g5b7,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #31)
+> 1) In comment 29, Jesús Martínez Novo made a good suggestion to more widely
+> publicize the new <lines> name before it gets committed.  
+> A mailing list thread might be a good way to
+> kick off this discussion.
+
+I'll post one.
+
+> 2) In the comments on the patch, '----' was brought up as the last remaining
+> way that the current <lines> implementation differs from 'indent-pre'
+> handling.
+>  I'd like to resolve this discrepancy: I really really *really* don't want to
+> complicate the parser more with Yet Another Slightly Different Way to handle
+> preformatted content.
+
+Let me expand a bit here: <poem> is designed for the treatment of poetry. I don't know what indent-pre was designed for, but one assumes it was intended for general-purpose, preformatted text, such as command line outputs and plain-text tables. The two use-cases are somewhat different.
+
+I went through and found the following differences. There are probably many others.
+
+* For some reason, indent-pre doesn't handle ----. Presumably this is so
+  preformatted tables, etc (e.g. those copied out of the MySQL monitor)
+  still appear correctly. This consideration is not relevant for <poem> and
+  so ---- is parsed inside these tags. Indeed, ---- within <poem> is quite
+  common at Wikisource.
+
+* Indents using : are ignored within indent-pre (presumably because they
+  don't make a whole lot of sense in a preformatted context). In <poem>,
+  indents are handled specially (using a fixed-width <span> to give 1em
+  indentation per : character), and line-initial spaces are transformed
+  to &nbsp;, to cope with the special formatting of some poetry.
+
+* Wikitext {| |} tables are available within <poem>, whereas indent-pre is
+  aborted as soon as a table is found.
+
+* Indent-pre formatting is aborted whenever a block-level tag is
+  encountered on the line. Block-level formatting is, however, available
+  inside <poem> (although this is only useful for stuff like <table>, since
+  the appearance of tags like <p> is affected quite badly by the <pre>
+  environment).
+
+* Indent-pre is not available inside <blockquote>, for unclear reasons.
+  <poem> works fine inside <blockquote>, just as anywhere else.
+
+* <poem> allows the application of a custom class/ID/style. The use of a
+  tag also allows extra attributes to be used - I have a patch in the works
+  that adds line numbering support to <poem>, which makes use of several
+  additional tag attributes (see bug 13644).
+
+I don't think it is correct to speak of ""resolving"" these discrepancies. As you can see, most of them seem to exist for a reason, and most involve idiosyncrasies in the existing indent-pre behaviour, any changes to which would disrupt existing wikitext.
+
+(Note, when I talk about <poem> above, I'm talking about the new implementation in Gerrit. The old extension sometimes does things differently.)
+
+> 3) I'd also like to review the code coverage issues a little more, to ensure
+> that we're sharing code (and CSS rules) to the maximum extent possible.
+
+I think this is up to you, Scott, and others in the know.",1391835029,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #31)
+> 1) In comment 29, Jesús Martínez Novo made a good suggestion to more widely
+> publicize the new <lines> name before it gets committed.  We almost
+> inadvertently introduced a conflict with <verbatim>, I'd like some greater
+> certainty that the new <lines> name proposal has been seen by a larger number
+> of editors/extension authors.  A mailing list thread might be a good way to
+> kick off this discussion.
+
+Will a post to wikitech-l suffice? Or is more needed in your opinion? I can probably handle the communication portion of this, just please be explicit with what you would consider sufficient.
+
+> 2) In the comments on the patch, '----' was brought up as the last remaining
+> way that the current <lines> implementation differs from 'indent-pre'
+> handling.
+
+Okay, I figured out what you mean here. At [[testwiki:Bug 52061#Indent-Pre (""Preceding space"")]] a ""----"", the wikitext equivalent of a horizontal rule (<hr>), is not current expanded when there's a leading space.
+
+In my opinion, this behavior (preceding space + unexpanded horizontal rule) is a separate issue that should be filed as a separate bug report (if one doesn't exist already) and is not a blocker to merging Gerrit change 106861. If you feel differently, can you please elaborate? (Also, can you please search for a relevant bug report and/or file one?)
+
+> 3) I'd also like to review the code coverage issues a little more, to ensure
+> that we're sharing code (and CSS rules) to the maximum extent possible.  This
+> is to ensure that point #2 continues to hold in the future, and we don't
+> accidentally introduce subtle incompatibilities by changing only one side of
+> a code path.
+
+Sure, code review is ongoing at Gerrit change 106861. If you have additional suggestions for technical changes, feel free to leave them on Gerrit. :-)",1391830615,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Instead of finding similarities between poem and indent-pre, which is moot since the indentation already breaks all markup that depends on being on the first column of the line, we may look at similarities between poem and normal wikitext.
+
+It's practically the same. The only difference is that poem treats newlines as <br/>, while normal text simply ignore newlines or convert them into paragraphs when there's a combination of newlines.",1390939202,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #31)
+> I'd like to resolve this discrepancy: I really really *really* don't want to
+> complicate the parser more with Yet Another Slightly Different Way to handle
+> preformatted content.
+
+There's nothing really new here :) We're just sending a <pre> tag to the parser, after all. The change to the parser itself is minuscule, and arguably it is a fix for a long-standing bug that was never exposed until now.
+
+(In reply to comment #33)
+> (07:34:41 PM) subbu: so, we were wrong .. <poem> is not indent-pre with
+> classes then.
+
+I'm glad you're aware of this! As I said in Gerrit, the similarities are purely coincidental.",1390875527,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"From chat:
+
+(07:32:52 PM) subbu: i just checked the updated wiki page .. and  <hr> and colon-indents seem different in <poem> vs. indent-pre .. probably all wikitext elements that occur in SOL position but are strict about not having any leading ws.
+(07:33:16 PM) cscott-free: how many of those are there?
+(07:33:36 PM) subbu: i suppose <poem> just calls regular parse on embedded content and then wraps it in wrapper with the right css classes
+(07:33:43 PM) subbu: tables are fine with leading space.
+(07:34:05 PM) subbu: headings, lists, hr dont work if there is leading WS, iirc.
+(07:34:41 PM) subbu: so, we were wrong .. <poem> is not indent-pre with classes then.
+(07:35:10 PM) cscott-free: but should it be?  i don't like the idea of adding a bunch of new special cases to the parser.
+(07:35:48 PM) subbu: cscott, it cannot be without breaking <poem> behavior OR breaking existing pages that have leading space before :*;#=- chars
+(07:35:59 PM) cscott-free: if we can at least parameterize it, such that indent-pre has SOL markers turned off, and <poem> has SOL markers turned on, that would make me happier.
+(07:36:14 PM) cscott-free: rather than poem just being gratuitously different in random ways.
+(07:36:24 PM) subbu: ya, you are talking of refactoring code in the parser.
+(07:36:30 PM) subbu: and reusing it.
+(07:36:56 PM) cscott-free: subbu: i'm certainly talking about reusing more parser code, rather than implementing <poem> as a brand new crazy thing.
+(07:37:25 PM) cscott-free: i'm tired of having weird corner cases everywhere.
+(07:37:50 PM) cscott-free: there should be some principled way we can describe how indent-pre and <poem> are similar.
+(07:37:57 PM) subbu: maybe spend some time, how <poem>/<lines> would fit in parsoid land and that can inform the discussion of how the core code can be restructured .. but refactoring/restructure that seems like a lot of work as well.
+(07:38:33 PM) cscott-free: in a nutshell that's why i don't want <poem> merged too quickly.  i'd like to understand better how it all fits in.
+(07:38:53 PM) cscott-free: and probably to do some dumpGrepping to figure out how much we can change indent-pre and/or <poem> without breaking too much stuff.",1390869777,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,I added a few more test cases to [[testwiki:bug 52061]] -- leading colons are also parsed differently inside <poem>.,1390847758,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I think I just saved this patch from a premature +2.
+
+I'd like to summarize what still needs to be done here:
+
+1) In comment 29, Jesús Martínez Novo made a good suggestion to more widely publicize the new <lines> name before it gets committed.  We almost inadvertently introduced a conflict with <verbatim>, I'd like some greater certainty that the new <lines> name proposal has been seen by a larger number of editors/extension authors.  A mailing list thread might be a good way to kick off this discussion.
+
+2) In the comments on the patch, '----' was brought up as the last remaining way that the current <lines> implementation differs from 'indent-pre' handling.  I'd like to resolve this discrepancy: I really really *really* don't want to complicate the parser more with Yet Another Slightly Different Way to handle preformatted content.
+
+3) I'd also like to review the code coverage issues a little more, to ensure that we're sharing code (and CSS rules) to the maximum extent possible.  This is to ensure that point #2 continues to hold in the future, and we don't accidentally introduce subtle incompatibilities by changing only one side of a code path.
+
+Does anyone else have any remaining issues they'd like to see resolved before this is merged?",1390846375,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Regarding my use of ""indent-pre"" above -- I'm looking at this mostly from the perspective of parser maintenance.  As [[testwiki:bug 52061]] demonstrates, the desired behavior of <poem>/<lines> is the same as the existing behavior of 'indent-pre', although the implementation in the original patch was very different.  I would like to try to avoid adding a bunch of new hair (and crazy interactions) with the new feature, and instead try to reuse the existing indent-pre handling code so that all the corner cases were consistent.
+
+In fact, assuming this gets merged, it might be cleaner in the future to document the ""indent pre"" behavior as ""an implicit <lines> surrounding the indented region"".  This would reduce confusion because ""indent pre"" and ""<pre>"" are actually quite different in their handling of embedded wikitext, etc.
+
+I like the name <lines>, btw.",1390666581,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"lines sounds good, or <preservelines>
+
+That said, maybe it would be more user friendly to use a mediawiki.org page to discuss the tag name, so ideas can be better exposed and have more opinions (remember one have to explicitly register an account here to post a comment).
+
+About <poem> itself, I don't know why is a different name really needed. What are other use cases for this? I've just only used it for poem and lyrics (which is basically the same).",1390653738,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I like <lines>, the name puts the focus on the individual ""lines"" of the content, which is also what the tag is doing. Nice lateral thinking, Michael :)",1390648436,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #22)
+> (In reply to comment #16)
+> > <verbatim> is a misleading name since it still parses wikitext in its
+> > content.
+> > It is only verbatim for text-content. 
+> 
+> I do see what you mean here. The problem is, we have so far been unable to
+> come
+> up with a better name! <poem> is inappropriate as too specific/narrow.
+> 
+
+What about <lines>? The tag just just preserves the lines in its content, and it seems generic enough for what is used.",1390646698,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #25)
+> Since this is going to be merged into core/php-parser, presumably, you
+> control
+> this behavior and where in the parser pipeline the outer wrapping <pre> tag
+> is
+> generated? I haven't looked at the parser changes to answer that or how easy
+> this is since I haven't really hacked the php parser. Maybe Scott can answer
+> that more readily. 
+
+I think I've got this part sorted.",1390611047,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"That is right reg. CSS.
+
+Since this is going to be merged into core/php-parser, presumably, you control this behavior and where in the parser pipeline the outer wrapping <pre> tag is generated? I haven't looked at the parser changes to answer that or how easy this is since I haven't really hacked the php parser. Maybe Scott can answer that more readily. 
+
+At least with Parsoid, that is what we will consider outputting for this new tag unless VE folks find a <div> tag simpler than a marked up <pre> tag (seems unlikely).",1390609860,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"What you are saying makes sense. Presumably the CSS for .poem would have to ""neutralise"" the monospace/gray formatting normally applied to pre tags.
+
+My main question is, if we output a <pre> tag from the tag hook, will wikitext inside that tag still get parsed, as it should be?",1390609332,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #22)
+
+> (In reply to comment #20)
+> > IMO the <poem> tag should be rendered as <pre
+> > class=""poem""> and it has exactly the behavior of indent-pre (with an extra
+> > HTML
+> > class and without the necessity to write the leading indentation).
+> 
+> A few questions about this statement:
+> 
+> * The gray box/monospaced font of <pre>/indent-pre would have to be removed
+> for
+>   <poem> blocks.
+> * What are the existing differences between <poem> and indent-pre?
+> * <pre> does not render identically to indent-pre, so could you explain how
+>   rendering poems using <pre class=""poem""> would help?
+
+We weren't very clear about what we were discussing there. 
+
+What Scott meant is that the patch should generate <pre class=""poem""> .. </pre> for the HTML of the <verbatim>..</verbatim> (or <pre-text> or whatever tag name is picked) instead of generating <div class=""poem"">..</div>. It is cleaner and the ouput is semantically closer to the intention of the <verbatim> tag.",1390608896,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #16)
+> <verbatim> is a misleading name since it still parses wikitext in its
+> content.
+> It is only verbatim for text-content. 
+
+I do see what you mean here. The problem is, we have so far been unable to come up with a better name! <poem> is inappropriate as too specific/narrow.
+
+> Is there another way of achieving this
+> without adding a new tag?
+
+The <poem> tag is already in wide use. I don't see the problem with adding a tag for this functionality.
+
+(In reply to comment #20)
+> IMO the <poem> tag should be rendered as <pre
+> class=""poem""> and it has exactly the behavior of indent-pre (with an extra
+> HTML
+> class and without the necessity to write the leading indentation).
+
+A few questions about this statement:
+
+* The gray box/monospaced font of <pre>/indent-pre would have to be removed for
+  <poem> blocks.
+* What are the existing differences between <poem> and indent-pre?
+* <pre> does not render identically to indent-pre, so could you explain how
+  rendering poems using <pre class=""poem""> would help?",1390608255,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I agree reg. output being <pre class='poem'> .. </pre>
+
+However, maybe make it possible for the editor to provide a css-class rather than hardcode class=""poem"" into the tag?
+
+For standard <poem> content,
+<pre-text>
+... 
+</pre-text>
+
+And for other uses,
+<pre-text class=""fancy-css"">
+...
+</pre-text>",1390589947,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I further updated [[testwiki:bug 52061]] to show the difference between <poem> and <pre class=""poem"">.  IMO the <poem> tag should be rendered as <pre class=""poem""> and it has exactly the behavior of indent-pre (with an extra HTML class and without the necessity to write the leading indentation).",1390588717,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #17)
+> I don't know what you mean by indent-pre.
+
+Subbu clarified that this means the preceding space trick. I updated [[testwiki:bug 52061]].",1390587244,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Please, don't use <verbatim>!!. It's already been in use by a Wikia extension [1]
+
+----
+
+[1] http://community.wikia.com/wiki/Help:Verbatim_tags",1390587154,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #16)
+> From what I can tell, looking at output, this is ""indent-pre"" - ""indent"" +
+> CSS-class. Given that indent-pre provides all the formatting functionality, I
+> presume the missing ability of adding CSS-classes onto indent-pre is the
+> primary reason for this new tag? Is there another way of achieving this
+> without adding a new tag?
+
+I don't know what you mean by indent-pre.
+
+I created a test page at [[testwiki:bug 52061]] to demonstrate the poem tag's functionality.",1390586895,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"<verbatim> is a misleading name since it still parses wikitext in its content. It is only verbatim for text-content. 
+
+From what I can tell, looking at output, this is ""indent-pre"" - ""indent"" + CSS-class. Given that indent-pre provides all the formatting functionality, I presume the missing ability of adding CSS-classes onto indent-pre is the primary reason for this new tag? Is there another way of achieving this without adding a new tag?",1390586336,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #10)
+> Regarding the tag name, is <poem> ever actually used for things besides
+> poems?
+
+I looked at some examples in de.wikipedia. Apart from poems and poem-like texts (prayers etc.) there are things like inscriptions and dialogs, which use <poem>. And of course, as it is a wiki, some stupid things like quotes even without any line break in them.",1389605473,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Sure, let's go with verbatim.
+
+Siebrand also noted on Gerrit change 106861 that if/when this gets merged, we'll need to migrate the Poem extension bugs to core.",1389459951,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,I'd also prefer <verbatim> as the name.,1389446044,PHID-USER-3qsavo6roa5h32xcsgng,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,I'm wondering if people would prefer <verbatim> as the name of this tag?,1389432065,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Change 106861 had a related patch set uploaded by TTO:
+Merge Poem extension into core
+
+https://gerrit.wikimedia.org/r/106861",1389413873,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"The compact feature has always seemed quite buggy (or at least bizarrely unintuitive) and I wonder if we would really hurt much by killing it altogether.
+
+Regarding the tag name, is <poem> ever actually used for things besides poems? I usually use <pre> for other cases.",1389061208,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #8)
+> I am thinking something like <verbatim>, <asis> (""as is""), <nocollapse>,
+> <pretext>/<pre-text> (as in <pre> but for text, not code), <keepbreaks>
+> [...]
+
+Okay, I'll paint this bikeshed. I like verbatim or pretext. How about one of those?
+
+> 2. The attribute ""compact"" seems to actually make the display less compact.
+> See the testcase at [[mw:Extension:Poem]]. I think we need a new name/alias for
+> this too. However, I have no idea what it is actually meant to be used for...
+
+I'm not sure ""compact"" is needed... do people use it? If so, are there examples of it in the wild?",1389057399,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"OK, I'm taking a look at this. The merge looks easy enough, but I need advice.
+
+Poem has two major nomenclature issues:
+
+1. The tag should have another name besides <poem>. In comment 6 <nobreak> was suggested, but Poem does the reverse - it preserves line breaks. I am thinking something like <verbatim>, <asis> (""as is""), <nocollapse>, <pretext>/<pre-text> (as in <pre> but for text, not code), <keepbreaks> ......... ?? Any better ideas?
+
+2. The attribute ""compact"" seems to actually make the display less compact. See the testcase at [[mw:Extension:Poem]]. I think we need a new name/alias for this too. However, I have no idea what it is actually meant to be used for...",1388220804,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #6)
+> (In reply to comment #5)
+> > If you merge it to core, please call it something other than <poem>. Other
+> > than that I couldn't care less :D
+> 
+> I think we must keep the name ""<poem>"" for backward-compatibility, but it
+> should definitely have a saner alias (""<nobreak>"" or something).
+
+The main name of the feature should be something else, <poem> can be an alias for backwards-compatibility.",1374862476,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #5)
+> If you merge it to core, please call it something other than <poem>. Other
+> than that I couldn't care less :D
+
+I think we must keep the name ""<poem>"" for backward-compatibility, but it should definitely have a saner alias (""<nobreak>"" or something).",1374855121,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"If you merge it to core, please call it something other than <poem>. Other than that I couldn't care less :D",1374849740,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Poem was merged into core back in 2008, but subsequently reverted; see http://www.mediawiki.org/wiki/Special:Code/MediaWiki/43520.
+I must say, however, that I totally agree with the original report and Poem (along with some obvious stuff like CheckUser, RenameUser, etc.) should be in core; maybe it should've been there from day one, even.",1374843237,PHID-USER-mlp7cjyksjzemkdr5ued,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"Steps to deprecate an extension (apart from actual code changes):
+
+* Turn off extension for testwiki in InitialiseSettings.php and make sure nothing breaks (1 deployment cycle)
+* Turn off extension for all wikis in InitialiseSettings.php and make sure nothing breaks (1 deployment cycle)
+* Remove extension from CommonSettings.php, wmf-config/extension-list, and make-wmf-branch/default.conf (1 deployment cycle)
+* Move/deprecate MediaWiki documentation
+* Get component removed from Bugzilla, migrate any existing bugs
+* Have project removed from Gerrit (not immediately of course)",1374792408,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"(In reply to comment #1)
+> Anytime an extension is created or deprecated it's a logistical pain in the
+> ass.
+
+Can you elaborate on this? It seems pretty easy to me.",1374789622,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+Merge Poem extension into MediaWiki core,"I'm cool with merging it into core, although I probably wouldn't call it 'easy'. Anytime an extension is created or deprecated it's a logistical pain in the ass. Also, I would prefer to have this idea vetted on Wikitech-l before someone actually goes through the trouble of doing it.",1374789414,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-bdnotllyeea37ihjkmr3,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"VE should work as expected without clipboard access.  Currently it only half initalises.
+
+1. Install Kill Evil in Chrome or similar
+2. Edit any page
+
+(https://chrome.google.com/webstore/detail/kill-evil/epieehnpcepgfiildhdklacomihpoldk)
+
+Result:
+https://en.wikipedia.org/wiki/File:Missing-ui-ve.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374713100,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_description,declined
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),The extension in question doesn't exist anymore. I still don't think we need to support any future extension that kills essential web APIs.,1718626265,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"People disable these features for good reason; a nice error message, or even an ugly error message, would be helpful to let them know why VE wont load.",1462884959,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"@Esanders I agree, but perhaps we should also be better about error handling in general when an app such as VE fails to launch. There is no problem with not supporting Kill Evil, but I think there is a problem of ending up in a half initiated state with no user feedback right ?
+
+I think that is an area that we could be better at (be it VE, UploadWizard or what not).",1462883974,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),This little used extension kills APIs that are essential for VE to work.,1462883110,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),Sorry for very slow triage.,1390417139,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"When 'Kill Evil' addon exists, there are two failures to load modules, and then an exception which halts the VE initialisation half way.
+
+Module 'WrappedSelection' failed to load: Module 'WrappedSelection' failed to load: No means of selecting a Range or TextRange was found rangy-core-1.3.js:105
+
+Module 'Position' failed to load: required module 'WrappedSelection' not supported rangy-core-1.3.js:105
+
+Uncaught TypeError: Object #<WrappedSelection> has no method 'refresh' rangy-core-1.3.js:3035
+
+WrappedSelection rangy-core-1.3.js:3035
+getSelection rangy-core-1.3.js:3084
+ve.ce.Surface.showSelection ve.ce.Surface.js:1325
+ve.ce.Surface.onChange ve.ce.Surface.js:747
+oo.EventEmitter.emit oo.js:421
+ve.dm.Surface.change ve.dm.Surface.js:402
+ve.dm.SurfaceFragment.select ve.dm.SurfaceFragment.js:448
+ve.ui.Surface.initialize ve.ui.Surface.js:81
+(anonymous function) ve.init.mw.ViewPageTarget.js:1098
+proxy load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.t…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130725T023359Z:775
+
+in ve.ui.Surface method initialize, the following invocation should probably be skipped if those rangy modules have failed to load.
+
+   // By re-asserting the current selection and forcing a poll we force selection to be something
+   // reasonable - otherwise in Firefox, the initial selection is (0,0), causing bug 42277
+   this.model.getFragment().select();",1374728047,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),This isn't a fancy thing. You can't do things like bold the selection if you can't access information about what is actually selected.,1374714907,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),That too ;-)  Making the bug more general.  Hopefully VE is able to be at least partially functional without all those fancy things.,1374714190,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load),"That's more likely caused by the ""getSelection and onselectstart/onmousedown"" part of that extension.",1374713556,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-cn7rkjg6saedlg6no5bg,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"A very common chess template on many Wikipedias recommends using '|=' , and most instances of chess boards use this syntax
+https://en.wikipedia.org/wiki/Template:Chess_diagram#Standard_diagram
+https://de.wikipedia.org/wiki/Vorlage:Schachbrett#Standarddiagramm
+
+On German Wikipedia, editing the template strips the '=' signs.  This article is on the parsoid topfails
+https://de.wikipedia.org/wiki/Edward_Lasker?veaction=edit
+http://parsoid.wmflabs.org:8001/topfails/1
+
+There are 900 uses of these chess templates on German Wikipedia.
+https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/Vorlage:Schachbrett&limit=750
+https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/Vorlage:Schachbrett-klein&limit=115
+A few more of
+https://de.wikipedia.org/wiki/Vorlage:Schachbrett-10x10
+https://de.wikipedia.org/wiki/Vorlage:Schachbrett-8x10
+https://de.wikipedia.org/wiki/Vorlage:Schachbrett-Chaturanga
+
+The syntax is used on many other WPs, incl. eswp, frwp, plwp and ruwp
+https://es.wikipedia.org/wiki/Plantilla:Diagrama_de_ajedrez#Diagrama_est.C3.A1ndar
+https://fr.wikipedia.org/wiki/Mod%C3%A8le:Diagramme_d%27%C3%A9checs
+https://fr.wikipedia.org/wiki/Alexandre_Alekhine
+https://pl.wikipedia.org/wiki/Szablon:SzachyDiagram
+https://ru.wikipedia.org/wiki/%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:%D0%A8%D0%B0%D1%85%D0%BC%D0%B0%D1%82%D0%BD%D0%B0%D1%8F_%D0%B4%D0%B8%D0%B0%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B0
+
+On English, the VE UI can go into massive layout problems, but the UI issues may all be due to the Parsoid issue.
+https://en.wikipedia.org/wiki/French_Defence?veaction=edit
+The number of uses on enwp appears to be in the same ballpark as dewp
+https://en.wikipedia.org/w/index.php?title=Special:WhatLinksHere/Template:Chess_diagram&limit=900
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+{T55226}
+{T53166}
+{T73404}",1374655260,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-73q6sosb7r2syig35llq,task_description,resolved
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"There are no screenshots here to show how it used to be broken, but it seems to behave correctly now.",1429477499,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,Also at https://fr.wikipedia.org/w/index.php?title=Tour_(%C3%A9checs)&diff=96381943&oldid=95391142 .,1378286809,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"Moving to visual editor in case there is something about the Parsoid output that is causing broken layout in the ""|="" form of chess-board syntax.  Please assign to Parsoid if there is a bug here in our output.",1375205944,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"Hmm .. strange.  When I copied both forms of the syntax into a file and parse it with Parsoid, the html renders just fine.  Curious why it breaks in VE however.
+
+Verifiable here: http://parsoid.wmflabs.org/_wikitext/
+
+Paste this there and scroll down past the literal html and you'll see this rendered correctly there.
+
+------------------------------------------------
+{{Infobox chess opening
+|openingname = French Defence
+|image = {{Chess diagram|=
+|
+|
+|=
+  |rd|nd|bd|qd|kd|bd|nd|rd|=
+  |pd|pd|pd|pd|  |pd|pd|pd|=
+  |  |  |  |  |pd|__|__|__|=
+  |  |  |__|  |__|__|__|__|=
+  |  |  |__|  |pl|__|__|__|=
+  |  |  |__|__|__|__|__|__|=
+  |pl|pl|pl|pl|__|pl|pl|pl|=
+  |rl|nl|bl|ql|kl|bl|nl|rl|=
+|
+}}
+|moves=1.e4 e6
+|ECO=C00–C19
+|birth =
+|nameorigin = London vs. Paris correspondence match (1834–36)
+|parentopening = [[King's Pawn Game]]
+|AKA =
+|chessgid=39913&move=2&moves=e4.e6&nodes=21720.39913
+}}
+------------------------------------------------",1375137900,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break,"An alternative 'pretty' syntax that doesnt cause breakages is:
+
+https://de.wikipedia.org/w/index.php?title=Edward_Lasker&diff=120835751&oldid=120194113
+
+The html comments are visible in the parameters of the template dialog, but it stops the dirty diffs if this |= syntax is not desirable.",1374655563,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-73q6sosb7r2syig35llq,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"Several users on the English Wikipedia, most recently Salix, have requested that the parameters for templates should be in the recommended order not alphabetical order. 
+
+For example in {{tracklist}} it lists ""Track10"" before ""Track2"", and in the various citation templates, ""First"" and ""Last"" should be adjacent.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374654480,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_description,resolved
+VisualEditor: Template parameters should be in TemplateData recommended order,"Change 107428 merged by jenkins-bot:
+Use paramOrder data for ordering template parameters
+
+https://gerrit.wikimedia.org/r/107428",1389754734,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"Change 107428 had a related patch set uploaded by Trevor Parscal:
+Use paramOrder data for ordering template parameters
+
+https://gerrit.wikimedia.org/r/107428",1389730796,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,Resolved in Ic3eb665389380c8e3dd6562b059c2f6655a22588,1389730752,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"After filling/testing a couple of templates in ca.wikipedia.org, it looks like the current behavior is the following:
+
+* Required fields are sorted by the order they are listed in the template data.
+* Optional files are sorted alphabetically.
+
+Please sort everything following the same sequence used in the template data. Usually this is the same order used in the ""old"" documentation, which in turn tends to follow the order in which the information is presented.",1386640799,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"The dependency has been fixed.
+
+Is the importance of this still ""Low enhancement""?",1384434926,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,*** Bug 53891 has been marked as a duplicate of this bug. ***,1380655447,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"(In reply to comment #4)
+> There is a good case for imposing some ordering on the template parameters.
+> Often you find some parameters naturally group together. Take for example
+> http://en.wikipedia.org/wiki/Template:Infobox_single/doc There are various
+> parameters which group together:
+> *Ones relating to the image (Cover, Alt, Caption and Border)
+> *Ones to do with the single chronology (Last single, This single, Next
+> single)
+> for infoboxes a prefered order would generally be the order they appear in
+> the
+> template.
+
+Yeah, that sounds a totally reasonable thing to add. Making a bug now…",1377903725,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"There is a good case for imposing some ordering on the template parameters. Often you find some parameters naturally group together. Take for example http://en.wikipedia.org/wiki/Template:Infobox_single/doc There are various parameters which group together:
+*Ones relating to the image (Cover, Alt, Caption and Border)
+*Ones to do with the single chronology (Last single, This single, Next single)
+for infoboxes a prefered order would generally be the order they appear in the template.",1377903377,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"There is no such thing as ""TemplateData recommended order""; the JSON block is unordered and can't be relied upon. Does this imply that we should have a ""parameter order"" value for TemplateData?",1377900547,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"Another example is [[pl:Template:Związek chemiczny infobox]] on pl.wp (infobox for chemical compounds) which has a lot of parameters which should be shown together, but which are not always alphabetically one after another. These groups are for example:
+
+* gęstość + gęstość źródło + stan skupienia w podanej g + g warunki niestandardowe (density, source for density, state of matter for this density, non-standard environment conditions for the density)
+* rozpuszczalność w wodzie + rww źródło + rww warunki niestandardowe (solubility in water, source, non-standard environment conditions)",1375226159,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Template parameters should be in TemplateData recommended order,"An example of this is {{Taxobox}} which has 100+ parameters. There are about 10 recommended parameters which go at the top the list and the rest of the parameters have a strict ordering depending on taxonomic hierarchy. Kingdom, Phylum, Class,	Order, Family, Subfamily, Genus, Species. An example of use is http://en.wikipedia.org/wiki/Formica which gives the fields in a confusing alphabetial order (latin names are used for the fields).
+
+A second problem is the order when no templatedata is specified. In the article http://en.wikipedia.org/wiki/Where_Does_This_Door_Go?veaction=edit
+if you open up the dialog for the {{tracklist}} the parameters are listed in the order track1, track10, track11 ... track15 track2 track3 ... track9. Ideally they would be in strict numerical ordering. This would require a smarter sorting algorithm than just alphabetical. 
+
+Another note is that case insensitive sort is better than case sensitive sort as templates often have the same parameter with different capitalization, 'Image' and 'image'.",1374674837,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-3r7ax46g5ehieydsuuvm,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"Removing the last reference on a page, with <references/> present, causes the waring:
+
+There are no references with the group """" on this page.
+
+That should be 
+
+There are no references on this page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374580740,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_description,resolved
+VisualEditor: Warning for blank reference list is confusing,"Change 86656 merged by jenkins-bot:
+Add specific message for empty ref group list
+
+https://gerrit.wikimedia.org/r/86656",1380747909,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"Change 86656 had a related patch set uploaded by Esanders:
+Add specific message for empty ref group list
+
+https://gerrit.wikimedia.org/r/86656",1380577840,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"I agree with John: Most pages dont used grouped references. It would be much more intuitive to say that there are no references at all. Several users in the Hebrew Wikipedia complained about it, and I imagine that it's the same in all languages.",1374823191,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"In the use-case for this bug, there are no references of any group, so why mention groups at all.  IMO the UI shouldnt talk about groups unless it is necessary.  Most pages dont used grouped references.",1374612826,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Warning for blank reference list is confusing,"(In reply to comment #0)
+> Removing the last reference on a page, with <references/> present, causes the
+> waring:
+> 
+> There are no references with the group """" on this page.
+> 
+> That should be 
+> 
+> There are no references on this page.
+
+No. You can have dozens of <ref group=""foo"">s and no <ref>s and get that message.
+
+Perhaps a special-case of ""There are no references without a group on this page."" for the null-group instance?",1374591288,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sl6ozzm6vdvlvv4lpkc6,task_subcomment,NA
+VisualEditor: Allow per-wiki/-namespace disabling of formatting styles e.g. page title,"On the English Wikipedia the page title formatting level is never used in article space, although I understand it is used on some other wikis. It might be that other wikis do not use a dfferent page style.
+
+Accordingly it would be nice to be able to remove/suppress/disable this item from the list on a per namespace (or, less ideally, per wiki) to avoid confusion to new editors. 
+
+Unless this is absolutely trivial to implement, please regard it as a low priority enhancement request.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374576000,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-7abqyeltz5gnkmdn4t4n,task_description,open
+VisualEditor: Allow per-wiki/-namespace disabling of formatting styles e.g. page title,"Sadly not trivial, but yes, this level of flexible configuration would be nice.",1374591912,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7abqyeltz5gnkmdn4t4n,task_subcomment,NA
+VisualEditor: Display name of transclusions as a tool-tip when selected,"At en.wp a user comments:
+""The tooltip with a ""puzzle"" icon that appears when clicking on a template should contain the name of the template used. This would allow readers to be aware of which template they're about to change and would make the Templates interface [[self-documenting]], teaching by example the existence of the most common templates.
+
+For example, the next screenshot would contain the word ""Chembox"" besides the puzzle icon:""
+
+Screenshot: [[File:VisualEditor - Template editing 1.png]]
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51827",1374512400,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-25n5vcma7cdemv6yuhj7,task_description,resolved
+VisualEditor: Display name of transclusions as a tool-tip when selected,"(In reply to Alex Monk from comment #3)
+> Don't we have this now? What to do about this bug?
+
+Yes, fixed by Trevor's new context menus as of 6 months or so ago.",1416249978,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-25n5vcma7cdemv6yuhj7,task_subcomment,NA
+VisualEditor: Display name of transclusions as a tool-tip when selected,Don't we have this now? What to do about this bug?,1416190833,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-25n5vcma7cdemv6yuhj7,task_subcomment,NA
+VisualEditor: Display name of transclusions as a tool-tip when selected,"(In reply to comment #1)
+> What would this do when multiple templates (or other transclusions) are used
+> in
+> the scope of one transclusion block, like the succession boxes?
+
+I can think of three logical options:
+
+1. The name of the first template and some indication (perhaps an asterisk?) that there are multiple translcusions in the block, e.g. ""s-start *""
+
+2. a list of all the items in the transclusion, e.g. for [[Alan Williams]]:
+
+s-start
+s-par
+s-bef
+s-ttl
+s-aft
+s-end
+
+Note that above, each template is listed only once, even for multiple occurrences, showing repeats is possible also.
+
+3. The names of the first and last templates with an indication (probably an ellipsis) that there are omitted elements, e.g. ""s-start ... s-end"" or
+s-start
+...
+s-end
+
+The horizontal format I'd guess might be easiest to program but would only work for templates with short names.
+
+In either 1 or 3 there could be a way to click to see the templates that are omitted. However I'm not sure how useful that would be, so my suggestion would be to just leave passive provision for it to be added later without difficulty should it be requested.",1383349090,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-25n5vcma7cdemv6yuhj7,task_subcomment,NA
+VisualEditor: Display name of transclusions as a tool-tip when selected,"What would this do when multiple templates (or other transclusions) are used in the scope of one transclusion block, like the succession boxes?",1383282851,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-25n5vcma7cdemv6yuhj7,task_subcomment,NA
+VisualEditor: Double-clicking on an image in the image finder inserts it twice,"If you open up the image finder, identify an image you want and /double/ click on it, the image finder closes and the selected image is inserted twice.
+
+Debian/Iceweasel 17.0.7.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374511980,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-hkdfdeny5avjlyz74jqn,task_description,resolved
+VisualEditor: Double-clicking on an image in the image finder inserts it twice,I believe we fixed this yonks ago; sorry for slow response.,1395355791,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hkdfdeny5avjlyz74jqn,task_subcomment,NA
+VisualEditor: Double-clicking on an image in the image finder inserts it twice,Also in Chrome 28/Windows 7.,1374681230,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-hkdfdeny5avjlyz74jqn,task_subcomment,NA
+VisualEditor: Double-clicking on an image in the image finder inserts it twice,"Screenshot
+
+**Attached**: {F11569}",1374512097,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-hkdfdeny5avjlyz74jqn,task_subcomment,NA
+VisualEditor: Note that Wikidata exists in the description text above the read-only language links section in the meta dialog,"In the site settings dialog you can see a list of language/interwiki links for the current article. There is a explanation text saying those can only be edited in the wikitext editor. Because of Wikidata this is now no longer true for most articles. The text should be adapted and maybe link to the corresponding Wikidata item?
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1374504240,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-mztpccwdq5aifemh7iim,task_description,resolved
+VisualEditor: Note that Wikidata exists in the description text above the read-only language links section in the meta dialog,"\o/
+thanks!",1385506631,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-mztpccwdq5aifemh7iim,task_subcomment,NA
+VisualEditor: Note that Wikidata exists in the description text above the read-only language links section in the meta dialog,"Change 97516 merged by jenkins-bot:
+Note language links need to be edited on Wikidata
+
+https://gerrit.wikimedia.org/r/97516",1385506442,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mztpccwdq5aifemh7iim,task_subcomment,NA
+VisualEditor: Note that Wikidata exists in the description text above the read-only language links section in the meta dialog,"Change 97516 had a related patch set uploaded by Jforrester:
+Note language links need to be edited on Wikidata
+
+https://gerrit.wikimedia.org/r/97516",1385392603,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mztpccwdq5aifemh7iim,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","I could only find one major button that leads to the help pages - the one at the top toolbar. Ideally, there should be help buttons in every context - dialog boxes, inspector, plugins, etc.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T53237}",1374488460,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_description,open
+"There should be help links in every context - dialog boxes, inspectors, etc.","We disagree with the premise; instead, there should only be help links where they are useful to explain the complexity of a control to the user. Most of this is already done, and the focus areas for this release don't have this level of complexity required. Consequently, we decided to remove this from the Q3 blockers list at the triage meeting on 2015-02-11.",1423879363,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","They are definitely in the i18n system, for example https://meta.wikimedia.org/wiki/MediaWiki:Visualeditor-dialog-meta-categories-defaultsort-help/en",1423690069,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","The relevant documentation about messages (i18n system) appears to include 
+* https://www.mediawiki.org/wiki/Help:System_message
+* https://www.mediawiki.org/wiki/Localisation#Adding_new_messages
+* https://www.mediawiki.org/wiki/Localisation_file_format
+* https://www.mediawiki.org/wiki/Help:System_message#Finding_messages_and_documentation
+
+The last of these says ""How each message is used by MediaWiki, variables available, parameters used, limitations, et cetera is explained with the complete documentation in the qqq pseudo-language files"", with a link to here:
+
+* https://translatewiki.net/w/i.php?title=Special%3ATranslate&task=reviewall&group=core&language=qqq&limit=5000&tux=0
+
+On that page, if I change the Group field to any of the four VisualEditor groups, and then look for the messages that James added to all items related to one VE menu, I can't find those messages. Should I be looking somewhere else, or are the messages not in the i18n system?",1423689769,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",">>! In T53798#1029938, @John_Broughton wrote:
+> * The content of contextual help should be similar to templates: visible to everyone, each on separate page, with a related talk pages, but not necessarily editable by anyone but an admin. What //isn't// needed is some programmer-added contextual help; what is needed is a //system// so that creating and modifying contextual help is done by members of Wikipedia communities. [For example, pages could be named something like this: Help:VisualEditor/ContextHelp///label//, where ""label"" is a unique name for where the contextual help will appear.
+
+MediaWiki already solved this problem long ago with the i18n system and the MediaWiki: system namespace. Either look at the changes made to the i18n/en.json file, or search for the text you want changed, to find out which page in the MediaWiki namespace an admin needs to change. These MediaWiki pages can also have related talk pages.
+
+
+>>! In T53798#1029938, @John_Broughton wrote:
+> * Contextual help should be able to include links - because linking to the relevant section (or anchor point - see WP:EIW, for example) is important when the (relatively short) contextual help isn't sufficient.
+
+I think we could allow that, but we'd need to change OO.ui.FieldLayout to accept HTML for the 'help' configuration, and then make VE-MW parse the help messages.
+",1423651331,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",">>! In T53798#1029938, @John_Broughton wrote:
+> * The content of contextual help should be similar to templates: visible to everyone, each on separate page, with a related talk pages, but not necessarily editable by anyone but an admin. What //isn't// needed is some programmer-added contextual help; what is needed is a //system// so that creating and modifying contextual help is done by members of Wikipedia communities. [For example, pages could be named something like this: Help:VisualEditor/ContextHelp///label//, where ""label"" is a unique name for where the contextual help will appear.
+
+MediaWiki already solved this problem long ago with the i18n system and the MediaWiki: system namespace. Either look at the changes made to the i18n/en.json file, or search for the text you want changed, to find out which page in the MediaWiki namespace an admin needs to change. These MediaWiki pages can also have related talk pages.
+
+
+>>! In T53798#1029938, @John_Broughton wrote:
+> * Contextual help should be able to include links - because linking to the relevant section (or anchor point - see WP:EIW, for example) is important when the (relatively short) contextual help isn't sufficient.
+
+I think we could allow that, but we'd need to change OO.ui.FieldLayout to accept HTML for the 'help' configuration.
+",1423651288,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Those who noticed the contextual help on the meta (page settings) menu - I'm not one of them - apparently didn't think it was worth commenting at WP:VE/F, or its equivalent at mediawiki.org. That may because contextual help was added to the VE menu //least used.// Or because no one was overwhelmed by the wording in the contextual help popups. Or because there was no obvious way to suggest improvements in wording. Regardless of the reasons, the lack of a response should absolutely not be taken to be a polling of the user community.
+
+More generally:
+
+* Contextual help absolutely is needed. The lack of this is one of the major weaknesses of wikitext editing. I don't think user feedback is needed to confirm this need. But if there is any doubt, then I suggest posting this the question (""Should VE menu items have contextual help?) at one or both Feedback pages. 
+* The content of contextual help should be similar to templates: visible to everyone, each on separate page, with a related talk pages, but not necessarily editable by anyone but an admin. What //isn't// needed is some programmer-added contextual help; what is needed is a //system// so that creating and modifying contextual help is done by members of Wikipedia communities. [For example, pages could be named something like this: Help:VisualEditor/ContextHelp///label//, where ""label"" is a unique name for where the contextual help will appear.
+* Contextual help should be able to include links - because linking to the relevant section (or anchor point - see WP:EIW, for example) is important when the (relatively short) contextual help isn't sufficient.",1423633543,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 186108 merged by jenkins-bot:
+MWMediaDialog: Add contextual help for controls
+
+[[https://gerrit.wikimedia.org/r/186108]]",1422488523,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 186108 had a related patch set uploaded (by Jforrester):
+MWMediaDialog: Add contextual help for controls
+
+[[https://gerrit.wikimedia.org/r/186108]]
+
+#patch-for-review",1421798146,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",Did we get any feedback?,1416183267,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","The page settings (""meta"") dialog now has a complete set of contextual help. Will wait for further user feedback before doing the rest of the dialogs.",1410831140,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 160371 merged by jenkins-bot:
+Add contextual help to all remaining meta dialog controls
+
+https://gerrit.wikimedia.org/r/160371",1410831074,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 160371 had a related patch set uploaded by Jforrester:
+Add contextual help to all remaining meta dialog controls
+
+https://gerrit.wikimedia.org/r/160371",1410744289,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 159104 merged by jenkins-bot:
+Provide contextual help for the page settings dialog's controls
+
+https://gerrit.wikimedia.org/r/159104",1410208908,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",First one done. We'll seek feedback on this approach and then roll out for the rest of the dialogs.,1410208838,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 159104 had a related patch set uploaded by Alex Monk:
+Provide contextual help for the page settings dialog's controls
+
+https://gerrit.wikimedia.org/r/159104",1410200618,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 159095 merged by jenkins-bot:
+Make help button for FieldLayout frameless again
+
+https://gerrit.wikimedia.org/r/159095",1410199152,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 159095 had a related patch set uploaded by Alex Monk:
+Make help button for FieldLayout frameless again
+
+https://gerrit.wikimedia.org/r/159095",1410199015,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",It looks like some work was done in Gerrit change 147751 and then reverted,1407980699,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","So for adding these to the page settings controls, it should now just be a case of adding the new messages and using them as the config.help for each setting's FieldLayout. James, are you planning to do this?",1405636684,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.",So I suppose now the job is to start writing copy…,1405452080,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 142468 merged by jenkins-bot:
+Allow FieldLayouts to have help text
+
+https://gerrit.wikimedia.org/r/142468",1405449958,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","Change 142468 had a related patch set uploaded by Alex Monk:
+Allow FieldLayouts to have help text
+
+https://gerrit.wikimedia.org/r/142468",1403828245,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","As a start, maybe add the (?) icon next to each of the page settings controls so we can give some blurb for users? I'm happy to write the copy on the commits. :-)",1402608232,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","**turingt** wrote:
+
+Maybe, the way to make the target page configurable can be creating a fixed redirect page for each link, so that we can change the redirect target.",1378729186,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+"There should be help links in every context - dialog boxes, inspectors, etc.","At https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=572181319#Inserting_reference there are comments that the instruction manual is too difficult to find, and requests that contextual help be added to the various dialogs. 
+
+These help links should obviously open in a new window/tab, and the target needs to be configurable on wiki as help pages are not static and get split/merged/reorganised over time.",1378729025,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-qeadal5vtjyli2cuuxzk,task_subcomment,NA
+VisualEditor: TemplateData-provided parameters in list should show description in tooltip,"The description of a parameter in the list of parameters does not always fit in the width of the editing add-parameter box, particularly in firefox (where the font size is apparently larger in than chrome) and when users are using large fonts for accessibility reasons. Where this is the case (or always) the description should be shown in a tooltip on hover or when selected by up/down keyboard prior to insertion.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50354
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51436
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62142",1374419280,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-rggykpwnizk34bvpsjp6,task_description,open
+"Broken table, repeated section in diff after VisualEditor edit","I recently ran across [https://en.wikipedia.org/w/index.php?title=Polycarbonate&diff=prev&oldid=564618311 this edit].  It seems as though they were trying to fix a spelling correction and inadvertently destroyed a table and had an entire section get repeated.
+
+There was a little [https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Strange_Diff discussion about the diff on the Visual Editor feedback page], where it was mentioned that the diff ""is very strange and [the commenter didn't] recall seeing anything similar"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374416280,PHID-USER-2qzpsivaeuezrxqtzhwn,False,PHID-TASK-ing4zbhpdsfypnokceeg,task_description,resolved
+"Broken table, repeated section in diff after VisualEditor edit","This was fixed a very long time ago (around August last year), but I didn't spot this report until just now; my apologies.",1412977739,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ing4zbhpdsfypnokceeg,task_subcomment,NA
+"Broken table, repeated section in diff after VisualEditor edit","The problem is that the table wikitext is buggy there.  It is missing a closing tag (in reality, it is missing a newline break.  |-|} .. See https://en.wikipedia.org/w/index.php?title=Polycarbonate&action=edit&oldid=563700122)
+
+The PHP parser output for this is also broken (see https://en.wikipedia.org/w/index.php?title=Polycarbonate&oldid=563700122#Manufacturers_and_brands and where the table has ended up).
+
+We could improve Parsoid to detect some scenarios like this, but it is currently lower priority.  Fixing the table by adding a line break between ""|-"" and ""|}"" should fix the issue for now.
+
+Sample wikitext snippet for our use later:
+
+{|
+|foo
+|-|}
+abc",1374506456,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-ing4zbhpdsfypnokceeg,task_subcomment,NA
+"VisualEditor: Have a ""remove from page"" button in media settings dialog","An English Wikipedia user familiar with the transclusion dialog expected thatthe way to remove an  image from the article was using a remove option in the media dialog. Such an option does not exist, and they couldn't work out another way of removing the image other than selecting and deleting the characters around and including the slug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374362700,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-apnlro5ql64fbmr7qoty,task_description,declined
+"VisualEditor: Have a ""remove from page"" button in media settings dialog",It's (now?) very simple to delete an image by clicking on it and pressing delete. Pushback welcome.,1437787301,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-apnlro5ql64fbmr7qoty,task_subcomment,NA
+sees unreviewed pages despite their ns isn't reviewable,"After https://pl.wikipedia.org/w/index.php?title=Pomoc:VisualEditor/Skr%C3%B3ty_klawiszowe&oldid=37098556&diff=cur this edit it sees unreviewed pages and distinguishes between stable and unreviewed versions despite a) on this page, both versions are autoreviewed b) even if points [[Wikipedia:VisualEditor/Nawigacja]] (transcluded) out as pending rewiev - the project namespace is not reviewable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374328320,PHID-USER-gf5juv3z3p75bykrcrhf,False,PHID-TASK-npzavnntwnz6xylar7kw,task_description,open
+VisualEditor: Set correct text annotation buttons for ka (მ/კ),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4uk2cqp2bkhf3so3ifse,task_description,resolved
+VisualEditor: Set correct text annotation buttons for ka (მ/კ),Done and will be deployed tomorrow.,1374633775,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4uk2cqp2bkhf3so3ifse,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ka (მ/კ),"Change 74979 merged by jenkins-bot:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374632702,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4uk2cqp2bkhf3so3ifse,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ka (მ/კ),"Change 74979 had a related patch set uploaded by Esanders:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374428015,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4uk2cqp2bkhf3so3ifse,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for os (Б/???),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jfjnga5p64vzxczhpota,task_description,resolved
+VisualEditor: Set correct text annotation buttons for os (Б/???),Done and will be deployed tomorrow.,1374633751,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jfjnga5p64vzxczhpota,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for os (Б/???),"Change 74979 merged by jenkins-bot:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374632700,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jfjnga5p64vzxczhpota,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for os (Б/???),"Change 74979 had a related patch set uploaded by Esanders:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374428013,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jfjnga5p64vzxczhpota,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ru/ky (Ж/K),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ateveyfcbqb3i4wfvvxx,task_description,resolved
+VisualEditor: Set correct text annotation buttons for ru/ky (Ж/K),Done and will be deployed tomorrow.,1374633741,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ateveyfcbqb3i4wfvvxx,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ru/ky (Ж/K),"Change 74979 merged by jenkins-bot:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374632698,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ateveyfcbqb3i4wfvvxx,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for ru/ky (Ж/K),"Change 74979 had a related patch set uploaded by Esanders:
+Add bold/italic for cyrillic/georgian languages
+
+https://gerrit.wikimedia.org/r/74979",1374428011,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ateveyfcbqb3i4wfvvxx,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for nl (V/C),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266280,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hlwmurrr6a42vwsh4edb,task_description,resolved
+VisualEditor: Set correct text annotation buttons for nl (V/C),Done and will be deployed tomorrow.,1374634218,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hlwmurrr6a42vwsh4edb,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for nl (V/C),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632635,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hlwmurrr6a42vwsh4edb,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for nl (V/C),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412448,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-hlwmurrr6a42vwsh4edb,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for eu (L/E),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266280,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-52xvekcadppljx7wxtjw,task_description,resolved
+VisualEditor: Set correct text annotation buttons for eu (L/E),Done and will be deployed tomorrow.,1374633960,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-52xvekcadppljx7wxtjw,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for eu (L/E),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632633,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-52xvekcadppljx7wxtjw,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for eu (L/E),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412437,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-52xvekcadppljx7wxtjw,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for es (N/C),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ztoidsuy5fwdvtm6hoxa,task_description,resolved
+VisualEditor: Set correct text annotation buttons for es (N/C),Done and will be deployed tomorrow.,1374633947,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ztoidsuy5fwdvtm6hoxa,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for es (N/C),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632626,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ztoidsuy5fwdvtm6hoxa,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for es (N/C),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412439,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ztoidsuy5fwdvtm6hoxa,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for pt (N/I),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-evgaeiyun2bs3jdkzmuq,task_description,resolved
+VisualEditor: Set correct text annotation buttons for pt (N/I),Done and will be deployed tomorrow.,1374633901,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-evgaeiyun2bs3jdkzmuq,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for pt (N/I),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632624,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-evgaeiyun2bs3jdkzmuq,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for pt (N/I),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412443,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-evgaeiyun2bs3jdkzmuq,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for gl (N/C),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-64zcrx2xmqdtz5ns3ivt,task_description,resolved
+VisualEditor: Set correct text annotation buttons for gl (N/C),Done and will be deployed tomorrow.,1374633878,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-64zcrx2xmqdtz5ns3ivt,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for gl (N/C),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632631,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-64zcrx2xmqdtz5ns3ivt,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for gl (N/C),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412445,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-64zcrx2xmqdtz5ns3ivt,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for it (G/C),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ganyn24uk5sn6pp36vou,task_description,resolved
+VisualEditor: Set correct text annotation buttons for it (G/C),Done and will be deployed tomorrow.,1374633829,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ganyn24uk5sn6pp36vou,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for it (G/C),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632629,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ganyn24uk5sn6pp36vou,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for it (G/C),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412452,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ganyn24uk5sn6pp36vou,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for fr (G/I),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-buz4r3nu6zcrowjeto7w,task_description,resolved
+VisualEditor: Set correct text annotation buttons for fr (G/I),Done and will be deployed tomorrow.,1374633813,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-buz4r3nu6zcrowjeto7w,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for fr (G/I),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632620,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-buz4r3nu6zcrowjeto7w,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for fr (G/I),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412454,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-buz4r3nu6zcrowjeto7w,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for hu (B/D),"This is how it is configured in WikiEditor; will require icon creation.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374266220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4e4lr7gjx3fhin7zieit,task_description,resolved
+VisualEditor: Set correct text annotation buttons for hu (B/D),Done and will be deployed tomorrow.,1374633800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4e4lr7gjx3fhin7zieit,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for hu (B/D),"Change 74972 merged by jenkins-bot:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374632622,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4e4lr7gjx3fhin7zieit,task_subcomment,NA
+VisualEditor: Set correct text annotation buttons for hu (B/D),"Change 74972 had a related patch set uploaded by Esanders:
+Add bold/italic for more latin langages
+
+https://gerrit.wikimedia.org/r/74972",1374412441,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-4e4lr7gjx3fhin7zieit,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","At the moment wikimarkup being entered into the VE triggers a notice warning the user that it won't work - this notice then has to be actively dismissed. It'd be nice if, should the user remove the problematic markup, the notice would vanish.
+
+I'm popping this in as a low-priority enhancement: I appreciate the VE team has active breakage to focus on.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52386
+https://bugzilla.wikimedia.org/show_bug.cgi?id=70168",1374265800,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_description,resolved
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","That area of code could do with some rethinking, but this is basically done.",1391815339,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","Change 110295 merged by jenkins-bot:
+Hide wikitext warning notification when the user removes the markup
+
+https://gerrit.wikimedia.org/r/110295",1391813698,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","Change 110295 had a related patch set uploaded by Alex Monk:
+Hide wikitext warning notification when the user removes the markup
+
+https://gerrit.wikimedia.org/r/110295",1391045818,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","(In reply to comment #3)
+> There's an issue with this though, in that the popup hovers over the 'Save
+> page' button so I couldn't actually click 'Save page' very easily. It wasn't
+> at
+> all clear to me that clicking anywhere on the popup would close it.
+
+You aren't the first person to say that - see bug 52386",1380727372,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","(In reply to comment #2)
+> The popup should also be closed automatically after the ""save page"" button
+> has
+> been pressed. At that point it's clear that the user is not going to remove
+> any
+> markup that still remains (for whatever reason) so the notice serves no other
+> purpose and just gets in the way of the edit summary dialog.
+
+There's an issue with this though, in that the popup hovers over the 'Save page' button so I couldn't actually click 'Save page' very easily. It wasn't at all clear to me that clicking anywhere on the popup would close it.",1380724444,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup","The popup should also be closed automatically after the ""save page"" button has been pressed. At that point it's clear that the user is not going to remove any markup that still remains (for whatever reason) so the notice serves no other purpose and just gets in the way of the edit summary dialog.",1375812069,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+"VisualEditor: Auto-hide ""You've entered wikimarkup"" warning when the user has removed the markup",%%%*** Bug 52155 has been marked as a duplicate of this bug. ***%%%,1375381691,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-cb45x4k3rxys6v2cqzcc,task_subcomment,NA
+VisualEditor: Move-dragging a media item shows the copy cursor on Mac/Safari,"If I move an image around, I see the ""copy"" cursor, even though I'm just moving.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374262740,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ujehggdfeqiirechz6c2,task_description,resolved
+VisualEditor: Move-dragging a media item shows the copy cursor on Mac/Safari,"Created attachment 13903
+cursor image
+
+Oh, the screenshot doesn't show the cursor, but I added an example image of the cursor type instead.
+
+Safari Mac Version 7.0 (9537.71) just dragging around a thumbnailed image throughout the text shows this problem for me. It changes from the move cursor to the copy cursor.
+
+**Attached**: {F11318}",1385421258,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ujehggdfeqiirechz6c2,task_subcomment,NA
+VisualEditor: Move-dragging a media item shows the copy cursor on Mac/Safari,"Nope, I still see this problem. Initially it's the move cursor, but as soon as i move the cursor somewhere between the lines, i get the copy cursor.
+
+Screenshot attached.",1385420891,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ujehggdfeqiirechz6c2,task_subcomment,NA
+VisualEditor: Move-dragging a media item shows the copy cursor on Mac/Safari,The cursor I get in Safari (the same as in Firefox and Chrome) is the move cursor (a four-pointed cross). Marking as WORKSFORME. Possibly a config issue with your system?,1385387607,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ujehggdfeqiirechz6c2,task_subcomment,NA
+VisualEditor: Section edit links don't work like wikitext where the section is transcluded from elsewhere,"http://it.wikipedia.org/wiki/Template:Cassetto is AFAIK the Italian version of Hidden (it shouldn't be used in articles).
+
+http://it.wikipedia.org/wiki/Utente:Superchilum features a cassetto named Tudù which transcludes the subpage Utente:Superchilum/do.
+
+If you try and edit the first section in that cassetto, Varie, with the classic editor, you correctly manage to edit the /do subpage; VE instead only allows editing the main userpage.
+
+Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374231000,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-wcreo2gxsoyscsxloyxc,task_description,resolved
+VisualEditor: Section edit links don't work like wikitext where the section is transcluded from elsewhere,"The example page linked here no longer has any section edit links on it, so I can't test this exact case, but I believe we fixed this issue in 2017 with {b7dd6077b8cab3740cb84b5c003ad272ff09ab8f} (related to T153176).",1663955476,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-wcreo2gxsoyscsxloyxc,task_subcomment,NA
+Editing window does not scroll when dragging,"When dragging an item in the visual editor (tested with image and text), the editing window does not scroll up or down when you reach the top or bottom of the window. This means you have to make several consecutive drag and drop actions to move an item within a long article/section. Per Bug 51665 the image must be separately selected before you are able to drag it (i.e. each movement requires two mouse clicks).
+
+**See Also**:
+{T36307}
+{T75240}",1374226320,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_description,open
+Editing window does not scroll when dragging,"I tested moving an image again today, and this is the result on my Air Os X in https://en.wikipedia.org/wiki/Victor_Diaz_Lamich?veaction=edit, using the trackpad.
+In Chrome, maximized window, using Lamich’s plane pic:
+*I click on it and drag it down to put it at the bottom of the article, a green “+"" icon appears to guide me (good!). Nothing happens if I hover my pointer around the bottom of the page; down arrow does nothing; the side scrollbar doesn’t appear.
+*The two-fingers scroll gesture does work when the pointer is on the side scrollbar, so I manage to put the pic at the bottom of the article.
+*Now trying to put it back where it was, so I click and drag it again. Nothing happens if I hover around the top of the page or hit the up arrow, but the page does scroll if instead I move the pointer /on/ the toolbar (scroll gesture while on the side scrollbar also works). There may be a problem with the focus though, but at least the pic is where I want it to be.
+
+In Safari, maximized window, using the same pic:
+*Dragging the pic doesn’t show the green + icon, but a line instead. Dragging it toward the bottom of the screen achieves nothing. 
+*The two-fingers scroll gesture works on the entire surface of the page, and it’s the only way to get to the bottom of the page, and then on the top again. Hovering on the toolbar while dragging accomplishes nothing in Safari; it shows the green + icon though, in the area of the tab name.
+*Dragging and pressing the up and down arrows doesn’t seem to work. In the rare cases when it does, both the up and the down keys will actually move the pic toward the top of the page, one line at the time (holding the key never works in my experience).
+ ",1430228132,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"Yes, OS X 10.9.5 Chrome and Windows 7 with IE 11- objects cannot be dragged beyond the bottom or the top of the page - the page does not scroll up. In IE 11, sometimes it's possible to drag beyond the bottom of a page but never beyond the top of editing area. ",1419959778,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,I'm on OS X 10.10.1 (14B25) with Chrome 40.0.2214.45 beta (64-bit) and the issue is present. ,1419920556,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,This appears to be OS-specific.  I do not have this problem (either scrolling up or down) on Mac OS 10.8.5; I know that at least two editors have this problem on Windows 8.,1419882579,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"So I'm not sure I'm adding to the right bug, but I don't seem to be able to drag templates or images beyond the bottom of the window (and even beyond the top when I tested this the other way around) with the mouse.
+I tried this in https://de.wikipedia.org/wiki/Benutzer:Elitre_%28WMF%29/sandbox with Chrome and Firefox.",1416241422,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"Just tested this, I can scroll up, with some difficulty ( by positioning the cursor on the top toolbar), but scrolling down does not seem possible. 
+
+Additionally, in most drag and drop interfaces I can be dragging and use a two finger, gesture based scroll while dragging, this does not work on VE (Chrome Version 39.0.2171.52 beta (64-bit) / OS X 10.10 )",1415828928,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,This was fixed over the Summer.,1415807780,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"I found this a problem to. When additing using just a touchpad or not having a scroll option on the mouse, you have a difficulties to move and object.",1407176990,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,*** Bug 63170 has been marked as a duplicate of this bug. ***,1404761224,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"Problem encounter at FF 24.0 Windows Vista. As I cant add a template, per this bug:
+http://imgbin.org/index.php?page=image&id=15296
+
+I have to use the method of placing the template on the top and scroll down. Thus this behaviour is blocking me in activity in VE.",1381053810,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"(In reply to comment #4)
+> the ""challenge"" was to get
+> the ""language"" template back at the bottom of the page. You can't do this by
+> dragging, even if you stay in the same window.
+
+I think I know what you mean and I have filed a report about it at Bug 54756. Good catch! Thank you.
+
+Also, setting the priority back to Normal since this is usually decided by the developer or team working on a specific report. Thank you for your understanding.",1380428104,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"**Wikifram** wrote:
+
+While the above is correct insofar that dragging beyond the page boundaries doesn't work (apparently not an urgent problem?), the ""challenge"" was to get the ""language"" template back at the bottom of the page. You can't do this by dragging, even if you stay in the same window. You can use some unintuitive workarounds (which you can find for yourselves), but the basic functionality doesn't work, just like most of the basic functionality of MW 1.22wmf19. has anyone tested ''anything'' in this release related to VE? Anything at all? Since it was ""very"" easy to find many problems with it in half an hour of testing. Back to the drawing boards please.",1380382559,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,"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 
+
+The users poses ""a challenge"" consisting in dragging the <languages /> bar at [[mw:Groups]] from the bottom of the page to the top, which implies dragging.
+
+A more probable use case it to move pictures from one section to another.",1380324332,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,Confirmed that this also occurs on Firefox 22 and Chrome 28 on Windows 7,1374228554,PHID-USER-ohetl546bwt5ac2szu5w,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+Editing window does not scroll when dragging,Forgot to note this is on Firefox 22 on Xubuntu Linux,1374226368,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-xnlwaxwz6vxmxx7sxwlh,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near","If you want to move an image to the start of a section in Visual Editor the logical course of action is to drag it to before the first character of the first word of the section.
+
+A user of Firefox 21 reports this does not work at all, in my testing in Firefox 22 it appears to work only occasionally.
+
+The counter-intuitive dragging the image to after the last character of the section title does work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54756
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65883",1374225180,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-32x2jdddgorx6i4qqszg,task_description,resolved
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near","Change 139674 merged by jenkins-bot:
+Block item drag and drop
+
+https://gerrit.wikimedia.org/r/139674",1403049871,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near",*** Bug 51292 has been marked as a duplicate of this bug. ***,1403005130,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near","Change 139674 had a related patch set uploaded by Esanders:
+Block item drag and drop
+
+https://gerrit.wikimedia.org/r/139674",1402926269,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near",*** Bug 54756 has been marked as a duplicate of this bug. ***,1381246558,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near","I'm a little confused as to what the request is here - do you feel that VisualEditor should, when dragging, magically create (and destroy) places to put the cursor, so you can drag content there? Assuming this, I've re-titled, but please correct if I've misunderstood.
+
+We've deliberately decided against that in the past as a confusing behaviour, hence why there are all the extra blank lines (""slugs"") for the ""possible place you could put the cursor which aren't actually there"" concept.
+
+We could do this, but I'm not sure. Also, it adds behaviour that is possible using a mouse but not the keyboard (dragging is not done in the keyboard, instead cut/paste is), which is a little uncomfortable given the intent of VisualEditor.
+
+We've considered adding an ""outline mode"" which would have all the slugs shown, possibly including these ones, and an ""editor mode"" where no slugs at all would show, which could be one alternative to this request.",1381246309,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+"VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near",There is a similar problem when you try to drag elements to the end of the editable content area - see Bug 54756.,1380428336,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-32x2jdddgorx6i4qqszg,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"A user on English Wikipedia requests that templates such as navigation boxes that display as collapsed by default when viewing should display as collapsed by default when editing.
+
+""Currently, navigation boxes are always uncollapsed when editing. This can be quite annoying when having to deal with big ones like {{The Beatles}}, e.g. on ""I'm a Loser"", also it might be confusing editors into believing that this part of a page can easily be edited.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1374223320,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_description,open
+VisualEditor: Surface should respect the default state of collapseable templates,"And worse, they are often 'autocollapse' which means they won't benefit from this. I am going to propose a change on en.wp soon, to limit the usage of autocollapse to ONLY navboxes, so at least other parts of the pages will not have this problem. But i'm not sure how to get social buy-in for completely removing autocollapse behaviour of navboxes.",1526025290,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"Navboxes and probably almost everything else still use `class=""collapsible""`…",1525985062,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,">>! In T53664#4198427, @matmarex wrote:
+> This should now magically work for elements made collapsible using `class=""mw-collapsible""`, as a result of 8cdfcc5fd4b, which refactored that code to hide them using only CSS. 
+
+Does that make this fixed, or are there elements we'd want to support which use a different class/mechanism?",1525983346,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"This should now magically work for elements made collapsible using `class=""mw-collapsible""`, as a result of 8cdfcc5fd4b, which refactored that code to hide them using only CSS. ",1525981957,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"Created attachment 13417
+Related render problems
+
+This is a related problem, which would not be noticable if it was not for this bug.
+
+https://en.wikipedia.org/w/index.php?title=Anarchism&veaction=edit
+
+When in normal view mode (not VE), expand all of those sidebars
+A large area of whitespace opens up above ""Internal issues and debates"", and the images appear there.
+
+In the VE, that whitespace is filled with text, which causes the images to be pushed further down in the content, eventually slipping into the References section, and on Firefox the images even overlaps the References section.
+
+I haven't investigated what is causing the VE vs non-VE rendering differences, but collapse is clearly the reason this rendering difference is a significant problem that all VE users face, rather than a minor glitch that only appears when the user is silly enough to alter all sidebars to be expanded.
+
+**Attached**: {F11253}",1380600089,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"(In reply to comment #1)
+> First of all, this requires fixes for bug 51565 to be deployed, and then we
+> need to fix the NavFrame and CollapsibleTable scripts in
+> en:wp:MediaWiki:Common.js to use the same hooks.
+
+That change has been made on enwp by TheDJ/hartman (cc'd)
+
+https://en.wikipedia.org/w/index.php?title=MediaWiki:Common.js&diff=570114240&oldid=569893356
+
+The templates are yet not collapsing; is there more development needed in VE product or in Common.js ?
+
+I think 'collapse' need more special handling in VE (possibly even in parsoid); in order to be WYSIWYG.
+1. The user can change the collapse state of templates in the VE dialog editor, and that change should be reflected in the VE after the changes are applied.
+2. The user should be able to collapse and uncollapse a collapse-able template in order 
+2.1 to visualise how the page will look in each mode
+2.2 hide/unhide collapse-able templates that are consuming precious screen real estate (this should be a separate enhancement)
+
+Perhaps this feature should be dependent on bug 30352.",1380598815,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Surface should respect the default state of collapseable templates,"First of all, this requires fixes for bug 51565 to be deployed, and then we need to fix the NavFrame and CollapsibleTable scripts in en:wp:MediaWiki:Common.js to use the same hooks.",1374261760,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-i6t6lpxllw2dz6rjfyz5,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,,1374158760,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tv63msunrr34jh3gj3an,task_description,resolved
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529488, @Danny_B wrote:
+>>>! In T53613#2529467, @Jdforrester-WMF wrote:
+>> Actually, VE will have one until it's banned in wikitext, not just ""not easily accessible"".
+> 
+> So ban it then. The request for it has been around for ages.
+
+At the bare minimum you'll need to run a three-month-long community RfC on meta with convincing arguments that explain as to why they all need to replace `<big>` with `<span style=""font-size: bigger;"">` and so on. There are, from a quick search, over 70k pages with at least one of these on the English Wikipedia alone; the transition will be quite a lot of work.
+
+It's not remotely worth it to spend that much in terms of WMF resources. If you want to try, you're welcome, but I seriously doubt you'll get sufficient consensus (and even then it'd probably need to be a configuration option so that third party wikis can address the breaking change in slower time).
+
+Not of this is germane to this ticket, however.",1470435796,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529467, @Jdforrester-WMF wrote:
+> Actually, VE will have one until it's banned in wikitext, not just ""not easily accessible"".
+
+So ban it then. The request for it has been around for ages. Not even speaking that it has been deprecated ages ago even in XHTML we used before, and it is obsolete in HTML5.",1470435420,PHID-USER-xqqqgn2dels45flxw5kb,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529467, @Jdforrester-WMF wrote:
+> Actually, VE will have one until it's banned in wikitext, not just ""not easily accessible"".
+
+So ban it then. The request for it has been around for ages.",1470435319,PHID-USER-xqqqgn2dels45flxw5kb,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529443, @matmarex wrote:
+> ""WT"" is VisualEditor team's jargon for ""wikitext"". Wikitext editor's toolbar has buttons for this: {F4339790}
+> 
+> I'll note that there's a task to remove them: T40487. You could probably file a similar one for VisualEditor. But as long as one has them, the other should too.
+
+Thanks for explanation.
+
+So why instead of adding it to Visual Editor not removing it from WikiEditor then (which should be obviously easier)?",1470435100,PHID-USER-xqqqgn2dels45flxw5kb,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2529443, @matmarex wrote:
+> ""WT"" is VisualEditor team's jargon for ""wikitext"".
+
+Correct (though we didn't invent it).
+
+> Wikitext editor's toolbar has buttons for this: {F4339790}
+> 
+> I'll note that there's a task to remove them: T40487. You could probably file a similar one for VisualEditor. But as long as one has them, the other should too.
+
+Actually, VE will have one until it's banned in wikitext, not just ""not easily accessible"".",1470434945,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"""WT"" is VisualEditor team's jargon for ""wikitext"". Wikitext editor's toolbar has buttons for this: {F4339790}
+
+I'll note that there's a task to remove them: T40487. You could probably file a similar one for VisualEditor. But as long as one has them, the other should too.",1470434546,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"What does WT stand for?
+
+What do you call feature-parity in this case?",1470432701,PHID-USER-xqqqgn2dels45flxw5kb,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,">>! In T53613#2528664, @Danny_B wrote:
+> We have headers and table captions providing semantically correct way how to emphasize headlining text. What is the use case of using big text elsewhere?
+
+Off-topic. VE and WT are designed to have feature-parity. If you think we should ban users from using these, file a task.",1470432011,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,We have headers and table captions providing semantically correct way how to emphasize headlining text. What is the use case of using big text elsewhere?,1470426148,PHID-USER-xqqqgn2dels45flxw5kb,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"Change 141617 merged by jenkins-bot:
+Provide tools to make text bigger or smaller
+
+[[https://gerrit.wikimedia.org/r/141617]]",1470421624,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"Change 141617 had a related patch set uploaded (by Jforrester):
+Provide tools to make text bigger or smaller
+
+[[https://gerrit.wikimedia.org/r/141617]]
+",1469233591,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as big/small,"Change 141617 had a related patch set uploaded by Jforrester:
+Provide tools to make text bigger or smaller
+
+https://gerrit.wikimedia.org/r/141617",1403574866,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-tv63msunrr34jh3gj3an,task_subcomment,NA
+VisualEditor: Tool to set/unset text as subscript,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374158700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f6ao6kmtchv7v27bft42,task_description,resolved
+VisualEditor: Tool to set/unset text as subscript,Now merged into master; will be deployed (as experimental) in the next push (so will be available on MediaWiki.org) - we will make this available to production wikis next week when we re-work the toolbar.,1376619792,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-f6ao6kmtchv7v27bft42,task_subcomment,NA
+VisualEditor: Tool to set/unset text as subscript,"Change 78495 merged by jenkins-bot:
+Create a subscript tool
+
+https://gerrit.wikimedia.org/r/78495",1376619387,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-f6ao6kmtchv7v27bft42,task_subcomment,NA
+VisualEditor: Tool to set/unset text as subscript,"Change 78495 had a related patch set uploaded by Steven Zhang:
+Add subscript tool
+
+https://gerrit.wikimedia.org/r/78495",1376120249,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-f6ao6kmtchv7v27bft42,task_subcomment,NA
+VisualEditor: Tool to set/unset text as subscript,"An editor at en.wp has noted that subscript is requried to be able to correctly edit some articles, ""ECG leads, e.g. V4"" was the example given.",1374927410,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-f6ao6kmtchv7v27bft42,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374158700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rdzse5grzzixnnifzj2z,task_description,resolved
+VisualEditor: Tool to set/unset text as superscript,Now merged into master; will be deployed (as experimental) in the next push (so will be available on MediaWiki.org) - we will make this available to production wikis next week when we re-work the toolbar.,1376619787,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"Change 78490 merged by jenkins-bot:
+Create a superscript tool
+
+https://gerrit.wikimedia.org/r/78490",1376619344,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"Change 78490 had a related patch set uploaded by Steven Zhang:
+Add a superscript tool
+
+https://gerrit.wikimedia.org/r/78490",1376116614,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"As explained elsewhere, this is trivial to do but would make the toolbar (even more) unwieldy for all users, and so I de-prioritised it whilst waiting for a way to have lots of these icons available without filling everyone's screens with buttons most of them don't want to touch.
+
+We're working right now on a first draft which we think will help with the clutter, at which point making these tools is a work of minutes.",1375304078,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as superscript,"A user at en.wp has noted the lack of a tool to set superscript means that the article [[Spiral Dynamics]] cannot be completely edited in VE.
+
+The ability to set superscript and subscript are essential features for writing about many articles in the science, maths and technology fields, so it should be a core competence of the VisualEditor rather than a low-priority enhancement.",1375263490,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-rdzse5grzzixnnifzj2z,task_subcomment,NA
+VisualEditor: Tool to set/unset text as strikethrough,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374158700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ascdutdvqb4aq6opfuse,task_description,resolved
+VisualEditor: Tool to set/unset text as strikethrough,Done by Peter C. at Wikimania 2013 Hacking Days. Yay.,1375865291,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ascdutdvqb4aq6opfuse,task_subcomment,NA
+VisualEditor: Tool to set/unset text as strikethrough,"Change 78019 merged by jenkins-bot:
+Create strikethrough text style button
+
+https://gerrit.wikimedia.org/r/78019",1375865057,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ascdutdvqb4aq6opfuse,task_subcomment,NA
+VisualEditor: Tool to set/unset text as strikethrough,"Change 78019 had a related patch set uploaded by Peter.C:
+Create strikethrough text style button
+
+https://gerrit.wikimedia.org/r/78019",1375863283,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ascdutdvqb4aq6opfuse,task_subcomment,NA
+VisualEditor: Tool to set/unset text as underlined,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374158700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dwpuhdlnvzi2y7re3asf,task_description,resolved
+VisualEditor: Tool to set/unset text as underlined,Now merged into master; will be deployed (as experimental) in the next push (so will be available on MediaWiki.org) - we will make this available to production wikis next week when we re-work the toolbar.,1376619782,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dwpuhdlnvzi2y7re3asf,task_subcomment,NA
+VisualEditor: Tool to set/unset text as underlined,"Change 78488 merged by jenkins-bot:
+Create an underline tool
+
+https://gerrit.wikimedia.org/r/78488",1376619184,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dwpuhdlnvzi2y7re3asf,task_subcomment,NA
+VisualEditor: Tool to set/unset text as underlined,"Change 78488 had a related patch set uploaded by Steven Zhang:
+Create an underline tool
+
+https://gerrit.wikimedia.org/r/78488",1376114307,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dwpuhdlnvzi2y7re3asf,task_subcomment,NA
+"VisualEditor: Show two editing/view source tabs at all times, even if you can't edit page because it's protected","When viewing an article you have permission to edit, you see two tabs at the top - ""Edit"" and ""Edit source"". When viewing an article you don't have permission to edit, you see only one - ""view source"".
+
+This is not good UI design There needs to always be the same number of tabs displayed. Ideally there should be tabs to ""view source"" and ""view visual source"" (with better wording though!), see Bug 51547.
+
+If a read-only editor is not possible or not available then that tab needs to pop up a message saying that editing is restricted currently/until xx:xx for <log entry> and that they can view the wikitext source if they want (linked to an explanation what that means).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374077880,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-qh3lrsa2vheyfhks3klm,task_description,declined
+"VisualEditor: Show two editing/view source tabs at all times, even if you can't edit page because it's protected","Comment... I think it might be useful to have the suggested ""view visual source"" tab, primarily to enable copying content such as references between protected and non-protected articles. However, I do grok the additional layers of complexity this would entail...",1427495377,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-qh3lrsa2vheyfhks3klm,task_subcomment,NA
+"VisualEditor: Show two editing/view source tabs at all times, even if you can't edit page because it's protected","A ""read-only editor"" is the view mode… I'm not really sure there's much value in going down the route, but instead we'd want to combine the two edit tabs together (except for users with VisualEditor disabled).",1385386552,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qh3lrsa2vheyfhks3klm,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","There should be a view-source equivalent for the visual editor so that people can see the page in VE as if the could edit it. It should allow them to interrogate things like template, so they can find out which template is producing what they see and how it does that. ~~When VE can cope with copy+paste, then~~ this will also allow them to copy and paste the relevant image/template/whatever to whatever article they are working on.
+
+**See Also**:
+* T54004
+* T54091",1374077700,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_description,resolved
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages",">>! In T53547#4983051, @matmarex wrote:
+>>>! In T53547#4977960, @Schnark wrote:
+>>> Additionally, if the user has NWE enabled, the old wikitext editor is still used for protected pages (but NWE loads after switching to visual and back).
+>> And if the user doesn't have NWE enabled, switching back to wikitext gives an error: ""Error loading data from server: readonly.""
+> This doesn't happen for me locally, only on Beta, which has been stuck in readonly mode for two weeks now.
+
+My comment was wrong anyway, as I actually did have NWE enabled. But whatever, switching now works on Beta as expected, both with NWE and without.",1551172044,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages",">>! In T53547#4977960, @Schnark wrote:
+>> Additionally, if the user has NWE enabled, the old wikitext editor is still used for protected pages (but NWE loads after switching to visual and back).
+> And if the user doesn't have NWE enabled, switching back to wikitext gives an error: ""Error loading data from server: readonly.""
+This doesn't happen for me locally, only on Beta, which has been stuck in readonly mode for two weeks now.",1551137528,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages",">>! In T53547#4977107, @matmarex wrote:
+> You can only access it by switching from old wikitext editor
+Or  by using `veaction=edit`.
+
+> Additionally, if the user has NWE enabled, the old wikitext editor is still used for protected pages (but NWE loads after switching to visual and back).
+And if the user doesn't have NWE enabled, switching back to wikitext gives an error: ""Error loading data from server: readonly.""",1550913707,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","Read-only VE is now available, but rather sneaky. You can only access it by switching from old wikitext editor:
+
+{F28266181}
+
+I think we should consider some more obvious ways to access it. Should we have another tab for it, called ""View in editor"" or something?
+
+Additionally, if the user has NWE enabled, the old wikitext editor is still used for protected pages (but NWE loads after switching to visual and back).
+
+----
+
+After we settle on this, we should probably brag about this in Tech News (#user-notice). Something like ""You can now open the visual editor in read-only mode on protected pages to see how they are made or copy citations to other pages"".",1550868857,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","Change 489416 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Load VE in read-only mode on protected pages
+
+[[https://gerrit.wikimedia.org/r/489416]]",1550868092,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","Change 489416 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Load VE in read-only mode on protected pages
+
+[[https://gerrit.wikimedia.org/r/489416]]",1549749958,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","The ability to load VE at all on protected pages was removed in https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VisualEditor/+/350471/. As a result you can only open the wikitext view source page.
+
+Ideally you would be able to open VE in read-only mode as this bug describes.",1542299795,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Provide a ""view VE"" mode / disable editing for protected pages","(In reply to comment #0)
+> There should be a view-source equivalent for the visual editor so that people
+> can see the page in VE as if the could edit it.
+
+This could get quite complex, but do-able if it's worth it.
+
+> It should allow them to interrogate things like template, so they can find out
+> which template is producing what they see and how it does that.
+
+I can sort-of see the value here, but it's not great.
+
+> When VE can cope with copy+paste, then this will also allow them to copy and
+> paste the relevant image/template/whatever to whatever article they are working
+> on.
+
+We're probably going to want to do this with ""read mode"" HTML rather than build something like that (so, you copy something from the action=read and paste into veaction=edit and you get the template/etc. magically working).
+
+Marking as ""low"" priority given difficulty and relatively low value for users; happy to be convinced otherwise.",1375300513,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k3k3gj4cbyainkrjcrt7,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","I had OpenODBC's iODBC plugin installed in Safari (latest release, always). After any edit, EMBED tags would be inserted at the top and bottom of the article. This did not occur with the source editor, or any other editable widget, like this one I'm typing in now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51423",1374057480,PHID-USER-5tluooawvjfhtqywnxag,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_description,resolved
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114000,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113106,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page",Can't see a link to a bug filed upstream -> rm upstream keyword,1400336197,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","(In reply to PiRSquared17 from comment #10)
+> This is now assigned to James Forrester.
+
+No it isn't. Above line clearly says:
+
+Assigned To: 	 VE team bugs – take if you're interested!",1395876859,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page",This is now assigned to James Forrester. Will a special test for this specific text be added? What can be done to fix this bug? Seems more like an upstream issue IMHO.,1395865021,PHID-USER-omdcggvudfkuawipp23i,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","PiRSquared17 is right. This is not VE's fault. It only occurs in VE because of the way it sets up the editing area, which your plugin doesn't recognise as not to touch.
+
+No and no.",1375284998,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","""This is not VE's fault.""
+
+I am not at all certain of this. This problem ONLY occurs in VE. It does not occur in the source editor, or any other text editor across the whole wide web.
+
+Something in VE is triggering this plugin to insert code. The plugin and the code it's inserting, is perfectly valid.",1375274462,PHID-USER-5tluooawvjfhtqywnxag,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page",You could write an AbuseFilter to prevent edits like this. This is not VE's fault. There is a problem with the extension. Has anyone notified the author of said extension?,1375240617,PHID-USER-omdcggvudfkuawipp23i,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","(In reply to comment #5)
+> From my understanding, using this bug targetedly it is possible for Browser
+> Add-Ons to insert malicious code in Wikipedia pages. The Wikipedia user will
+> not even notice. I put importance to ""immediate"", in case I'm wrong please
+> undo
+> my change.
+
+embed is not one of the allowed html tags when $wgRawHtml is disabled, so the embed tag is escaped as a security measure.  No malicious injection is possible via this bug.
+
+The now archived discussion is
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29/Archive_114#Is_this_me_or_the_editor.3F
+
+Examples:
+https://en.wikipedia.org/w/index.php?title=The_Road_%282009_film%29&diff=prev&oldid=563739949
+https://en.wikipedia.org/w/index.php?title=The_Road_%282009_film%29&diff=prev&oldid=564586766
+https://en.wikipedia.org/w/index.php?title=Informix_Wingz&diff=prev&oldid=564587579",1375131440,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","**wikipedia** wrote:
+
+From my understanding, using this bug targetedly it is possible for Browser Add-Ons to insert malicious code in Wikipedia pages. The Wikipedia user will not even notice. I put importance to ""immediate"", in case I'm wrong please undo my change.",1375128154,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","It is adding
+<embed type=""application/iodbc"" width=""0"" height=""0"" />",1374448472,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page",Have you reported it to the author yet?,1374165651,PHID-USER-omdcggvudfkuawipp23i,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","Actually my post over on the Village Pump *appears* to have turned up several other examples of plugins having the same problem. Not much more I can add though...
+
+http://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)
+
+Look for ""Is this me or the editor?"" (I can't get the section link to work)",1374086422,PHID-USER-5tluooawvjfhtqywnxag,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+"VisualEditor: Broken OpenODBC browser plugin causes ""application/iodbc"" to be injected into the page","Have you reported this upstream (i.e., to the author of the extension)? I don't this it's VE's fault, although I've seen similar stuff with another extension (FoxLingo):
+[[m:en:Wikipedia:VisualEditor/Feedback/Archive_2013_07#Inserting_weird_script_tag_stuff]].
+
+Actually, might be a more general bug, as these diffs have many similarities. I wonder if any other browser extensions do this.",1374078408,PHID-USER-omdcggvudfkuawipp23i,False,PHID-TASK-h64w6lawxsfffv5qe4yw,task_subcomment,NA
+Rewrite VisualEditor's converter to be bottom-up,"The data->DOM converter should construct its DOM bottom-up, the way https://gerrit.wikimedia.org/r/74058 already does for annotations. This would enable us to do some cool things like:
+
+* Pass childDomElements to nodes and meta items (already done for annotations)
+* Pass data content in addition to DOM content?
+* Allow nodes and meta items to unwrap themselves by returning an empty array (already done for annotations)
+** We could implement unwrapping of generated wrapper paragraphs using this feature
+* Possibly change the API so that instead of returning an array of DOM elements, the toDomElements function is responsible for appending its children.
+** This could replace handlesOwnChildren, and enable model types with complex output
+
+For DOM->data it's not as straightforward. We could experiment with bottom-up (outside-in, really) building there too, but it would be a bit less clear how things would work, and whether the copying involved would affect performance (although I believe we may already do a fair bit of copying around as it is).
+
+
+This may be my pet project for my flight to Wikimania, or I may end up doing this sooner if there's time.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374029040,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bevtevpkvtmwwlk2gved,task_description,open
+Rewrite VisualEditor's converter to be bottom-up,Ping on this bug.,1402554326,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bevtevpkvtmwwlk2gved,task_subcomment,NA
+Rewrite VisualEditor's converter to be bottom-up,"(In reply to comment #0)
+> * Possibly change the API so that instead of returning an array of DOM
+> elements, the toDomElements function is responsible for appending its
+> children.
+> ** This could replace handlesOwnChildren, and enable model types with complex
+> output
+> 
+This would also enable partial unwrapping of annotations, e.g. <p><a> Foo </a></p> -> <p> <a>Foo</a> </p>",1374029309,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-bevtevpkvtmwwlk2gved,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"Right now, ce.MWInternalLinkAnnotation obtains a DM rendering to get the computed href. We should factor out href computation so that this isn't needed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1374014700,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_description,resolved
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"Change 90953 merged by jenkins-bot:
+Get rid of dmRendering hack in ve.ce.MWInternalLinkAnnotation
+
+https://gerrit.wikimedia.org/r/90953",1382986514,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"Change 90953 had a related patch set uploaded by Catrope:
+Get rid of dmRendering hack in ve.ce.MWInternalLinkAnnotation
+
+https://gerrit.wikimedia.org/r/90953",1382383432,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"(In reply to comment #2)
+> (In reply to comment #1)
+> > Change 86065 had a related patch set uploaded by Catrope:
+> > Resolve rendered URLs according to the provided <base>
+> > 
+> > https://gerrit.wikimedia.org/r/86065
+> This change tried to just get rid of href computation, but that's not good
+> enough. It does need to actually be computed.
+
+The most recent version of this change actually makes the hack worse, in order to partly fix bug 48915. Once that bug is fixed properly, this hack can be removed.",1380241008,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"(In reply to comment #1)
+> Change 86065 had a related patch set uploaded by Catrope:
+> Resolve rendered URLs according to the provided <base>
+> 
+> https://gerrit.wikimedia.org/r/86065
+This change tried to just get rid of href computation, but that's not good enough. It does need to actually be computed.",1380240303,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation,"Change 86065 had a related patch set uploaded by Catrope:
+Resolve rendered URLs according to the provided <base>
+
+https://gerrit.wikimedia.org/r/86065",1380161666,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-izrcwmsj2eh7uaufp4mk,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"If someone is clicking on ""Mobile View"" and then back to ""Desktop"", a stopMobileRedirect cookie is left behind. This cookie will disable central notices on all wikimedia sites perpetually
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374004080,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_description,declined
+Switching to mobile view and back leaves cookie behind,"I'm marking this as wontfix.
+
+While I see your point about not setting the stopMobileRedirect cookie for devices that wouldn't normally get automatically redirected (eg a desktop browser), we don't have a reliable way to detect that, so without rearchitecting, we can't really achieve this. Ultimately, we've been attempting to simplify how MobileFrontend works - partly for performance/caching reasons and partly for codebase sanity, and I do not think this usecase is compelling enough to warrant additional complexity.
+
+I suspect Jon is right that with some CSS magic you may be able to resolve the specific issues you're running into with the banners. Otherwise, we should have a bigger discussion about how best for you guys to achieve what you need from within CentralNotice.",1376950515,PHID-USER-jh2oguhshocanixqvlfk,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"Is that zoomed in?
+Does it disappear when you scroll?
+Is it fixed position or absolute?
+
+How can one access that banner on a phone - is there a url? Looks like with a few tweaks to the css that should be easy render correctly on a desktop view on a mobile screen...",1374866409,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"**mwalker** wrote:
+
+Illustration of why desktop banners should not be served to mobile users
+
+Adam got this whilst browsing on the desktop site on his phone whilst logged out.
+
+**Attached**: {F11712}",1374861806,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"""With CentralNotice not filtering; true mobile users who choose to use the
+desktop site may be presented with a banner that doesn't work on small screens
+- e.g. the buttons are too small to hit with a finger.""
+
+This is a non-issue
+The banner will be exactly the same size for users viewing the desktop site on a mobile device.",1374098687,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"**mwalker** wrote:
+
+(In reply to comment #4)
+> You want to show a banner on the desktop site (en.wikipedia.org and friends)
+> when viewed in a mobile phone?
+
+Nope -- we want to show a banner on the desktop site to a desktop user who has previously used the mobile interface.
+
+> Could you clarify ""Removing the filtering comes at the expense of potentially
+> exposing users to banners that don't work particularly well on small
+> screens.""
+
+With CentralNotice not filtering; true mobile users who choose to use the desktop site may be presented with a banner that doesn't work on small screens - e.g. the buttons are too small to hit with a finger.
+
+> Does this effect the mobile site (en.m.wikipedia.org and friends) in anyway?
+
+No. Only the desktop site (and the transition of a desktop user between that and the mobile site and back.)
+
+> I'm also unclear how this effects the VisualEditor roll out... (you mention
+> this in the CentralNotice fix).
+
+VE is only involved because we spotted it with a VE banner (they want to show to everyone so we're getting lots of interesting CN bugs.)
+
+> The stopMobileRedirect cookie exists for a reason - if a user of the mobile
+> site wants to see the desktop site this stops them from being redirected on
+> every visit.
+
+Yep, understood. The feature request is more to not return 'desktop' devices to the desktop site after having viewed the mobile site with a stopMobileRedirect cookie.
+
+> We could only set the stopMobileRedirect cookie if the user is on a mobile
+> phone but this is messy and I don't see what value the work put in to achieve
+> this would gain. Does anything really need to change in MobileFrontend now?
+
+Meh; don't know. This is an edge case... It's more related to if we have more things that are device dependent using the cookie to determine if someone is on a big device or not.",1374091987,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"Just to check I understand the problem correctly:
+You want to show a banner on the desktop site (en.wikipedia.org and friends) when viewed in a mobile phone?
+Was there any reason you didn't do this before? I don't really understand the logic... ResourceLoader disables JavaScript on older phones so these banners should work perfectly fine.
+
+Could you clarify ""Removing the filtering comes at the expense of potentially exposing users to banners that don't work particularly well on small screens."" - if a mobile views the desktop site on their phone they will either use a modified viewport [1] and the banner will look exactly the same as desktop, or if there is no viewport the entire website will be unreadable so I'd be surprised they'd even be in desktop mode.
+
+Does this effect the mobile site (en.m.wikipedia.org and friends) in anyway?
+
+I'm also unclear how this effects the VisualEditor roll out... (you mention this in the CentralNotice fix).
+
+The stopMobileRedirect cookie exists for a reason - if a user of the mobile site wants to see the desktop site this stops them from being redirected on every visit.
+
+We could only set the stopMobileRedirect cookie if the user is on a mobile phone but this is messy and I don't see what value the work put in to achieve this would gain. Does anything really need to change in MobileFrontend now?
+
+[1] http://www.quirksmode.org/mobile/viewports2.html",1374082443,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"Change 73999 merged by jenkins-bot:
+(Bug 51465) No Longer Filtering Mobile Devices
+
+https://gerrit.wikimedia.org/r/73999",1374005801,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"Change 73999 had a related patch set uploaded by Mwalker:
+(Bug 51465) No Longer Filtering Mobile Devices
+
+https://gerrit.wikimedia.org/r/73999",1374004590,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+Switching to mobile view and back leaves cookie behind,"**mwalker** wrote:
+
+Fundraising's initial response is going to be just to just remove the filtering -- however, it would be a good feature for mobile frontend if that cookie was somewhat smarter (enough to remove itself when not needed / or track where it came from originally: varnish vs url click.)
+
+Removing the filtering comes at the expense of potentially exposing users to banners that don't work particularly well on small screens.",1374004272,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pl2ghnqidzao7i2kjzgp,task_subcomment,NA
+"VisualEditor: Use a ""broken link"" icon as the ""remove"" button in the link inspector, instead of a rubbish bin","There is consensus for a change to this element here: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Dustbin_icon_not_intuitive_for_.22unlink.22
+
+To summarize - the garbage can icon to remove a link is not intuitive.  Users may be unsure of its function, or believe it will remove the highlighted text, rather than just the link.  Most other editing UI's employ a broken link for this function, so it will be more familiar.
+
+Suggested improvement:
+
+*Replace ""Garbage Can/Dustbin"" with a ""broken link"" icon (example:http://us.fotolia.com/id/49483380)
+
+*Replace current rollover text ""Remove"" with ""Unlink""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374002400,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-ygze3evr6iu2qv2rw7yu,task_description,invalid
+"VisualEditor: Use a ""broken link"" icon as the ""remove"" button in the link inspector, instead of a rubbish bin","We've decided instead to remove the use of icons here as it's too confusing, and instead will use just the label.",1403977522,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ygze3evr6iu2qv2rw7yu,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"See:
+http://en.wikipedia.org/w/index.php?title=User%3ACananian&diff=564446937&oldid=564446873
+
+I was adding a heading (after a <!-- ... --> comment) and the diff stuck a <br> inside the ==heading==.
+
+I'm assigning this bug to VE for the moment, but it could be a parsoid bug.  I need to see the intermediate parsoid HTML generated for the change to tell one way or the other.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1373986620,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gqdob64njr6frqrzr75a,task_description,resolved
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Parsoid now normalizes this HTML to strip <br> from headings - the code is now in production.,1447795442,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Change 253050 merged by jenkins-bot:
+T53444: Strip <br>s from headings via new HTML normalization routine
+
+[[https://gerrit.wikimedia.org/r/253050]]",1447461206,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Change 253050 had a related patch set uploaded (by Subramanya Sastry):
+T53444: Strip <br>s from headings via new HTML normalization routine
+
+[[https://gerrit.wikimedia.org/r/253050]]
+",1447455845,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"If you want an example of how that happens on a private wiki, see above line 114 [[ https://office.wikimedia.org/w/index.php?title=Community_Engagement_(Product)/Editing&diff=prev&oldid=158096 | here ]]. It doesn't involve hidden comments.",1444058682,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Unless it advances the consistency of parsing, I am not convinced this is worth a lot of effort beyond normalization during serialization. The WYSIWYG behavior is clearly an edge-case since wikitext does not support multi-line headings. So, if VE folks are with it, I am fine with it.",1443736308,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"WYSIWYG is tricky here.  In this case, the user clearly saw the entire paragraph, including the newline, being styled as part of the heading.  If we handle this during normalization, then the result after saving will not be consistent with what the user saw during editing.
+
+@Jdforrester-WMF It's //possible// that existing-tidy wouldn't remove `<p><!--comment--></p>` because of the embedded comment.  Currently PHP elides all the comments, so it hands tidy the string `<p></p>` which tidy happily removes.  So it's possible we could finesse this somehow, for example by emitting a stub comment from the PHP parser.  Investigation needed.",1443735812,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Maybe worth handling this in the normalization routines.,1443735363,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Would fixing the PHP Parser require us to have replaced Tidy first, then?",1443714586,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"The original document was serialized with the `<br/>`:
+```
+$ (echo 'foo' ; echo; echo '<!--comment-->'; echo; echo 'bar') | tests/parse.js  --normalize=parsoid
+
+<p>foo</p>
+<!--comment-->
+<p><br/> bar</p>
+```
+I wonder if we should be generating `<p><!--comment--></p>` for that case, instead of the `<br/>` embedded inside the next paragraph.  Our current behavior is consistent with PHP:
+```
+$ (echo 'foo' ; echo; echo '<!--comment-->'; echo; echo 'bar') | php maintenance/parse.php --quiet
+<p>foo
+</p><p><br />
+bar
+</p>
+```
+...but it's certainly not ideal from an editing perspective.  Maybe PHP should change here as well, although I'm guessing the reason it is putting the `<br/>` inside the `<p>` is because otherwise `tidy` would strip the ""empty"" `<p>` tag.
+
+In any case, given this input DOM, VE's behavior is strange but understandable -- when you put your cursor between the exclamation mark and the last written line, VE is placing its internal insertion point between the `<p>` and the `<br/>`, so any heading conversion applies to the entire `<p>` contents, including the embedded `<br/>`.  The result that VE passes back to parsoid is then unsurprising:
+```
+<p id=""mwAQ"">some text</p> <!-- hidden comments FTW --><h2>Foo<br id=""mwAw""> moar text here</h2>
+```
+and Parsoid gives a faithful serialization of this as wikitext.",1443713401,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"The page is nominated for deletion, but [[https://en.wikipedia.org/w/index.php?title=Sabaragamuwa_Province_(Sri_Lanka)_bus_routes&diff=next&oldid=654323182| here's another example]].",1427805964,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Providing steps.
+1) Start with [[ https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=223541 | a new or a blank page ]].
+2) In wikitext mode, [[ https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=223541 | write something on the first line, leave a blank line, write a hidden comment, leave a blank line, write something else ]], then Save.
+3) Now enter VE mode. Notice the hidden comment is correctly displayed as an exclamation mark; there is now a carriage return sign at the beginning of the last line. 
+4) Put the cursor in the blank line between the comment and the last written line. You can now write any word, select it and turn it into a heading or a subheading; notice the entire line below, including the carriage return sign, also becomes part of said heading/subheading.
+5) Save. [[ https://test.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=223543&oldid=223542 | You now have wikitext for the heading/subheading you just made, showing up in plain sight ]]. You can also notice that the carriage return character was turned into a br tag.
+
+Reproducible: Always.
+Tested in Win 8 with the latest versions of Chrome, Firefox, IE, Opera (the last two while logged out). ",1425651893,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"Providing steps.
+1) Start with [[ https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=223541 | a new or a blank page ]].
+2) In wikitext mode, [[ https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=223541 | write something on the first line, leave a blank line, write a hidden comment, leave a blank line, write something else ]], then Save.
+3) Now enter VE mode. Notice the hidden comment is correctly displayed as an exclamation mark; there is now a carriage return sign at the beginning of the last line. 
+4) Put the cursor in the blank line between the comment and the last written line. You can now write any word, select it and turn it into a heading or a subheading; notice the entire line below, including the carriage return sign, also becomes part of said heading/subheading.
+5) Save. [[ https://test.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=223543&oldid=223542 | You now have wikitext for the heading/subheading you just made in plain sight ]]. You can also notice that the carriage return character was turned into a br tag.
+
+Reproducible: Always.
+Tested in Win 8 with the latest versions of Chrome, Firefox, IE, Opera (the last two while logged out). ",1425651818,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"No reproduction steps in > 18 months. If you can give some more details, please re-open.",1425599536,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"(BTW, I really couldn't play that vid on YouTube.)",1380121710,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"The steps are clear in AzaToth's video, but I can't reproduce that either: have you fixed something about ↵ being displayed, this week?",1380121219,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Does anyone have any steps to reproduce? I can't reproduce in Firefox or Chrome whilst playing around…,1380069203,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Also reported at https://fr.wikipedia.org/w/index.php?title=Cabinet_des_estampes_et_des_dessins_de_Strasbourg&curid=1591028&diff=96701784&oldid=96701717,1379352540,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,Also reported at http://mr.wikipedia.org/w/index.php?title=%E0%A4%9F%E0%A4%BE%E0%A4%95%E0%A4%A3%E0%A4%95%E0%A4%BE%E0%A4%B0_(%E0%A4%B8%E0%A4%AE%E0%A4%BE%E0%A4%9C)&curid=66935&diff=1193242&oldid=1193112 .,1375704033,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,*** Bug 52021 has been marked as a duplicate of this bug. ***,1374767614,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"AzaToth made a screencast at http://youtu.be/G_xXETTVgO0 showing the issue.
+
+Gwicke filed bug 50683 on the parsoid side -- we shouldn't allow newlines in a heading when we serialize to wikitext.
+
+But there's still a VE issue -- where is the ↵ coming from (visible in AzaToth's screencast).  VE shouldn't be putting the newline inside the heading.",1373987836,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading,"See also https://www.mediawiki.org/w/index.php?title=User%3AGWicke&diff=723931&oldid=655405
+
+So the <!-- ... --> comment doesn't seem to have anything to do with it.",1373987078,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-gqdob64njr6frqrzr75a,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"```
+[subbu@earth:~/work/wmf/parsoid] echo '<a rel=""mw:WikiLink"" href=""./Foobar"">:foobar</a>' | php bin/parse.php --html2wt
+[[:foobar]]
+
+[subbu@earth:~/work/wmf/parsoid] echo '<a rel=""mw:WikiLink"" href=""./Foobar"">:foobar</a>' | php bin/parse.php --html2html --body_only
+<p data-parsoid='{""dsr"":[0,11,0,0]}'><a rel=""mw:WikiLink"" href=""./Foobar"" title=""Foobar"" data-parsoid='{""stx"":""simple"",""a"":{""href"":""./Foobar""},""sa"":{""href"":"":foobar""},""dsr"":[0,11,2,2]}'>foobar</a></p>
+```",1373984340,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_description,open
+Leading colon in link label is wrongly removed from wikitext,"(In reply to comment #11)
+> My point is mainly that VE could easily understand when the punctuation is
+> added by mistake, because the label and the target link will be different. So
+> if the target does not feature a punctuation mark, but the label does, that
+> was probably not wanted. 
+
+Unfortunately we have to handle the case when it was intentional, so we can't just blindly auto-correct it. Also the definition of what is punctuation becomes much more complex when you are dealing with thousands of languages.",1379678052,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"This is a Parsoid bug (the colon part, at least):
+
+<a rel=""mw:WikiLink"" href=""./Foobar"">:foobar</a>
+
+serialises to:
+
+[[:foobar]]
+
+which converts back to
+
+<a rel=""mw:WikiLink"" href=""./Foobar"">foobar</a>",1379677931,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"I am leaving aside the semicolon issue, covered elsewhere.
+About what I reported in Comment 5:
+
+1) Type "":foobar""
+2) select all of this, from the colon (included) to the final r
+3) click on the linking tool, and make this a link to the article ""foobar""
+4) save.
+*outcome: the colon is included in the link; the link is working but the colon is invisible (and I think this is certainly not desirable).
+
+Please note that this also happens to "": foobar"", that is, if the colon and the typed word are separated by a space.
+
+
+1) Type ""foobar:""
+2) select all of this, from the f to the colon, including it
+3) click on the linking tool, and make this a link to ""foobar""
+4) save.
+*outcome: the colon is included in the link, it is visible, the link works fine (and I think this is not good code).
+
+Please note that when a piped link is created instead (for example if foobar is a link to Foobar2000), the colons will be part of the link in every case and they will all be visible.
+
+My point is mainly that VE could easily understand when the punctuation is added by mistake, because the label and the target link will be different. So if the target does not feature a punctuation mark, but the label does, that was probably not wanted. 
+
+HTH.",1379619273,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"This is indeed reproducable, and not just with semi-colons, but it is not this bug. I've reported it separately as bug 54332 including how to reproduce it.",1379606034,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,Can you leave some step-by-step instructions to reproduce the bug for clarification?,1379604129,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"About semicolons, we got another feedback that I managed to reproduce, see https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=573644513&oldid=573644268 .
+I wrote French; and turned that into a wikilink, including the semicolon.
+Then I added some text between the end of the word and the semicolon. The result is that we now have two wikilinks to the same word, and a nowiki tag in the middle.",1379599394,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"Yes Ed, in both cases I selected the colon and the word and then used the link tool. I know that you can get the first result also in the source editor, but the second one definitely does not produce a working link with the source editor, and anyway I was not really sure if it makes sense having a wikilink which includes a colon and then makes it invisible. If you think none of these behaviours should be prevented or worked on anyway, please just re-close this. Thanks.",1379512496,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"Can you explain how those cases were created. From what I can see colons don't extend link annotations, but if you select over a colon and use the link tool you're going to end up with weird stuff like that anyway.",1379507908,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"I am reopening this since I noticed that colons at least still get included in the links: here https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=573483719&oldid=573483114 the line beginning with ""Performance problems: VisualEditor"" has the colon included in the wikilink of the lattest word; the link works fine but you don't get to see the colon at all.
+https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=573483774 Here instead it is included in the wikilink to Issues, and I am not sure it's desirable either. Thanks.",1379507107,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"(In reply to comment #3)
+> Links are no longer getting extended automatically when any text is added at
+> the end, including commas, semicolons, etc. Possibly a result of the fix for
+> bug 51463
+
+Indeed, this was fixed in that.",1377830517,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"Links are no longer getting extended automatically when any text is added at the end, including commas, semicolons, etc. Possibly a result of the fix for bug 51463",1377448214,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"(In reply to comment #1)
+> instead of just the former (perhaps some kind of inline block wrapper around
+> the link, e.g. like Apple does in Mail and Calendar when text contains a
+> reference to a contact. It looks like ""Foo { bar } quux."" Where bar has a
+> rounded bubble around it when hovered and the cursor can be placed inside or
+> outside the bubble.
+
+)
+
+http://xkcd.com/859/",1373984998,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"I don't think we should explicitly disallow such symbol to be used in the label (might lead to other strange side-effects and inconsistencies).
+
+However it does give another use case for bug 51438 (T55973). Having a better way to edit the label might reduce the cases where this happens. Perhaps we could make it possible to put the cursor inside the link (after the last character) and outside the link.
+
+So that one can be in either of these positions:
+
+ * Foo <a>bar|</a>
+ * Foo <a>bar</a>|
+
+instead of just the former (perhaps some kind of inline block wrapper around the link, e.g. like Apple does in Mail and Calendar when text contains a reference to a contact. It looks like ""Foo { bar } quux."" Where bar has a rounded bubble around it when hovered and the cursor can be placed inside or outside the bubble.",1589732305,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+Leading colon in link label is wrongly removed from wikitext,"I don't think we should explicitly disallow such symbol to be used in the label (might lead to other strange side-effects and inconsistencies).
+
+However it does give another use case for bug 51438. Having a better way to edit the label might reduce the cases where this happens. Perhaps we could make it possible to put the cursor inside the link (after the last character) and outside the link.
+
+So that one can be in either of these positions:
+
+ * Foo <a>bar|</a>
+ * Foo <a>bar</a>|
+
+instead of just the former (perhaps some kind of inline block wrapper around the link, e.g. like Apple does in Mail and Calendar when text contains a reference to a contact. It looks like ""Foo { bar } quux."" Where bar has a rounded bubble around it when hovered and the cursor can be placed inside or outside the bubble.",1373984857,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-aeyfn2tjv55fvu4s3qp4,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"Currently, if you use TemplateData for a template without any parameters, you still have to create an empty ""params"" in the JSON (not really important), but you also end up with a ""Template parameters"" table with just the title line (Parameter	Description	Type	Default	Status).
+
+Rather than displaying an empty table, I think it would be better to display no table at all, or a simple message saying that no parameters are defined for this template.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1373960160,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_description,resolved
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"The fix in beta:
+ {F45817}
+
+vs test2:  
+{F45819}",1424732585,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"Change 191518 merged by jenkins-bot:
+Display a message when no parameters are defined
+
+[[https://gerrit.wikimedia.org/r/191518]]",1424310514,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"Change 191518 had a related patch set uploaded (by Mooeypoo):
+Display a message when no parameters are defined
+
+[[https://gerrit.wikimedia.org/r/191518]]
+
+#patch-for-review",1424308343,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,"It would also be useful if you could set ""no parameters"" in the TemplateData so that VisualEditor does not suggest adding a parameter for these templates.",1421330757,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+TemplateData: Display a useful message instead of an empty table for templates that take no parameters,*** Bug 62417 has been marked as a duplicate of this bug. ***,1398711170,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-t4cpdxjr67bsgbbjfn5v,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Seeing this more often now with VE and think it may be a couple different issues (not all on our side) but want to see what we can do to stop it and or lessen impact. This is currently being added to the security queue because I'm a bit concerned about some of the symptoms and worry it could be an injection vulnerability (see below). If we rule out a security concern I'm obviously happy with it being moved.
+
+Editors are making a normal edit and div's are being inserted like 
+
+<div id=""myEventWatcherDiv"" style=""display:none;""></div>
+
+often at the start and end of the page. 
+
+Googling around it seems they may be inserted by a common 3rd party plugin (divX?) but it is in no way clear. It also seems to be interacting weirdly with VE because it isn't only being inserted it's inserting WITHOUT <nowiki> tags which is what you'd expect if someone put a div in (see https://en.wikipedia.org/w/index.php?title=User:Jalexander/sandbox&diff=564465081&oldid=553572859 ). Could it be being injected somehow around VE and/or parser? 
+
+Examples:
+https://en.wikipedia.org/w/index.php?title=Spank!_The_Fifty_Shades_Parody&diff=prev&oldid=564448990
+http://en.wikipedia.org/w/index.php?title=Kendra_Morris&diff=prev&oldid=564426900
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51521",1373954100,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_description,resolved
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",">>! In T53423#1031831, @Aklapper wrote:
+> This task has #VE-deploy-2014-10-02 but is still open. Should this be retargetted?
+
+No.",1427402641,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",This task has #VE-deploy-2014-10-02 but is still open. Should this be retargetted?,1423677807,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Still seems to be happening, e.g. https://fr.wikipedia.org/?diff=108255165",1413485794,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Change 163961 merged by jenkins-bot:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412114007,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Change 163961 had a related patch set uploaded by Alex Monk:
+Remove certain blacklisted elements when getting HTML from document
+
+https://gerrit.wikimedia.org/r/163961",1412113155,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Has anyone here managed to actually get this to happen in their browser yet? James tried the DivX plugin in Safari on his Mac and couldn't get it to insert the bad content.,1407403424,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #16)
+> Sorry meant http://en.wikipedia.org/wiki/Special:AbuseFilter/345
+
+Thanks - though we should probably silently remove on save inside VisualEditor, like Inez suggests.",1380214635,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Sorry meant http://en.wikipedia.org/wiki/Special:AbuseFilter/345,1380184705,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Detected and warning issued by the abuse filter http://en.wikipedia.org/wiki/Special:AbuseFilter/485,1380184623,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",for the record it happened in fr.wp : https://fr.wikipedia.org/w/index.php?title=Les_Fourmis_%28Werber%29&diff=96415737&oldid=89791930,1378394111,PHID-USER-h66anukl4e5enszrrt3t,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",@James: Should we go for silent remove on safe? Also we can start tracking it with information about logged in vs. logged out user.,1377119871,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","I am also curious to know why it only happens to anonymous editors - at least, all the occurrences I have seen so far.",1377119586,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",On it.wp as well: http://it.wikipedia.org/w/index.php?title=Tank_Palamara&diff=60582899&oldid=60582688,1375696065,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Silently remove on save. Hacking blacklist will prevent people from saving and many of them are not technical enough to understand why - bad bad user experience.,1375286948,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #8)
+> As a workaround for now we could make VE remove those divs from the HTMLDOM
+> that it is sending to MW API for serializing. @James: Should we do it?
+
+You mean, have a blacklist of items to just silently remove on save? Could work as a quick hack.",1375286359,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",As a workaround for now we could make VE remove those divs from the HTMLDOM that it is sending to MW API for serializing. @James: Should we do it?,1374964307,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #6)
+> Making this public since I don't see this having any security impact. Then
+> the
+> community can also give input into how they want to see it handled.
+
+Thanks Chris",1374014416,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page",Making this public since I don't see this having any security impact. Then the community can also give input into how they want to see it handled.,1374014345,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #2)
+> It's certainly a type of edit we really don't
+> want but more importantly I'm confused about how it's getting inserted and
+> avoiding the normal VE/parser work flow which should <nowiki> it (instead of
+> actually inserting it in as a div like it is now).
+It's possible that the plugin inserts it in all <iframe>s. We use <iframe>s internally for encapsulating HTML documents.",1374013982,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #2)
+> I'm confused about how it's getting inserted and
+> avoiding the normal VE/parser work flow which should <nowiki> it (instead of
+> actually inserting it in as a div like it is now).
+
+It looks like it's bypassing the browser's events model and just inserting into the DOM, hence the issue. JS like VE isn't able to notice things outside the JS events model, sadly.",1374013882,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","(In reply to comment #1)
+> Hi James, the google consensus seems to be that a DivX plugin is inserting
+> that. 
+> 
+> http://padawan.info/en/2011/03/wtf-is-this-myeventwatcherdiv-doing-in-my-web.
+> html
+> 
+> I'm guessing that VE's interface suddenly looks like something the plugin was
+> expecting to use in the browser, and so it silently adds the div.
+> 
+> We could add an abusefilter rule to block those edits, but that seems a
+> little drastic.
+
+Ideally we'd want a global AbuseFilter rule that just silently dropped the content from the edit, but that's not a feature AF currently does. :-)
+
+Blocking is a bit strong, though possibly likely to happen from the community if we just warn users and they ignore. The only fix (other than getting the upstream plugin crap fixed, which seems unlikely) is to do the auto-drop in VE, which is icky too.",1374013806,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","yeah, that seems to be the consensus I could find too (which is very very weird... because I can't for the life of me find a 'legitimate' reason it should insert that into any page it can edit.. oh well certainly not the weirdest plugin BS I've seen). 
+
+Actually I don't think that's very drastic to do, the community almost certainly would agree and I'd pass it off to them (though they'll likely blame us for it which is never fun). It's certainly a type of edit we really don't want but more importantly I'm confused about how it's getting inserted and avoiding the normal VE/parser work flow which should <nowiki> it (instead of actually inserting it in as a div like it is now).",1374013674,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Broken DivX browser plugin causes ""myEventWatcherDiv"" to be injected into the page","Hi James, the google consensus seems to be that a DivX plugin is inserting that. 
+
+http://padawan.info/en/2011/03/wtf-is-this-myeventwatcherdiv-doing-in-my-web.html
+
+I'm guessing that VE's interface suddenly looks like something the plugin was expecting to use in the browser, and so it silently adds the div.
+
+We could add an abusefilter rule to block those edits, but that seems a little drastic.",1374013374,PHID-USER-doeppszazlm3r7xah4il,False,PHID-TASK-cdpx3zolbm5hnu4e76jg,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","In view mode, [[Template:Top icon]] places the featured star or good article at the top right hand corner.
+
+After loading a FA or GA or English Wikipedia, the featured star or good article icon appears where the template is, which is often down the bottom.  This is perfectly acceptable except for the 'where did it go?' feeling, but maybe a plugin could come up with a better UI design for topicons, geocoords, etc.
+
+Also templates without any real estate (like {{Use dmy dates}} and {{Use Australian English}}) 'disappear' entirely.
+
+https://en.wikipedia.org/wiki/Angels_Brought_Me_Here?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51322",1373941680,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ee572n6mn4yah76xipnp,task_description,open
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","Now that bug 23796 is fixed, we ""just"" need to work out a way to let the user set/unset these (bug 72199) and then trap clicks on this area to open the meta dialog, I think?",1414441807,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","This is a rather more general problem with the Vector skin (there's desire to have flag icons from the content, but no ability other than a hack that's unsupportable in VisualEditor).",1380753138,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","Bug 51322 fixed issues that were 'solely metadata', but these actually do produce elements, the problems that remain for these elements are:
+1: incorrectly positioned
+2: their template edit button, when selected is visually placed far from the content, making it difficult to find. bug 50854
+3: if they were correctly positioned, they are 'decoupled' from their anchor point  which is a problem with templates producing floating content as well. bug 50907",1375717076,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","The meta-templates bug 51322 has been marked as fixed, but the issue of top icons is still ongoing.",1375710059,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable",'templates without any real estate' has been raised already as bug 51322 (meta templates).,1374037304,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","It is easy to delete these hidden templates without noticing.
+
+e.g. delete the '↵' on Angels Brought Me Here.",1374035331,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+"VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they ""should"" and be editable","The 'templates without any real estate' problem is raised here:
+
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Time_for_an_essay
+
+I'm not sure if a separate bug has been raised, or even should be.  The top icons and templates without any real estate all need a special UI, probably under 'page settings'.",1374034932,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-ee572n6mn4yah76xipnp,task_subcomment,NA
+VisualEditor: Automatically build the option description for visualeditor-enable,"Forked from the original request at bug 48666 which was solved by making the preference hidden, as intended.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373933760,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fe5263dfospwtagdlyvz,task_description,resolved
+VisualEditor: Automatically build the option description for visualeditor-enable,"Change 130075 merged by jenkins-bot:
+Add dynamically generated list of namespaces to visualeditor-enable preference
+
+https://gerrit.wikimedia.org/r/130075",1398712510,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fe5263dfospwtagdlyvz,task_subcomment,NA
+VisualEditor: Automatically build the option description for visualeditor-enable,"Change 130075 had a related patch set uploaded by Alex Monk:
+Add dynamically generated list of namespaces to visualeditor-enable preference
+
+https://gerrit.wikimedia.org/r/130075",1398694222,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-fe5263dfospwtagdlyvz,task_subcomment,NA
+"VisualEditor: Create i18n toolbar icon for bold for Portuguese, Spanish and Galician","As in Bug T53330, I would like to request the icon for ""Bold"" to be an ""N"" (from ""Negrito"") in Portuguese (""pt"" and ""pt-br"").
+",1373919300,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-gguvte4hcswafvyrrjsm,task_description,resolved
+"VisualEditor: Create i18n toolbar icon for bold for Portuguese, Spanish and Galician",This was fixed and deployed yesterday.,1374771717,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gguvte4hcswafvyrrjsm,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"Use case:
+* The user opens VisualEditor
+* The user types something that looks like wikitext
+* VE notices and displays an mw.notify bubble with autoHide:false
+* The user leaves VE by clicking on the Read tab
+* The editor is torn down and we go back to view mode, but the bubble persists
+
+I would like to be able to remove this bubble when the editor is torn down, but mw.notification doesn't expose an API for this. There is a .close() method on Notification, but there's no way to get the Notification object created by mw.notify().
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1373853480,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mjeduabrtvm33uiu3e4a,task_description,resolved
+mw.notify notifications can't be removed/hidden programmatically,"Change 74407 merged by jenkins-bot:
+mediawiki.notification: Expose close method to hide a Notification
+
+https://gerrit.wikimedia.org/r/74407",1382187742,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"Change 74407 had a related patch set uploaded by Alex Monk:
+Return Notification object from mw.notification.notify
+
+https://gerrit.wikimedia.org/r/74407",1374170832,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"(In reply to comment #2)
+> I'd say that this is expected behavior and a ""feature"" of the shorthand. Just
+> like you can't have a message parsed by just doing mw.msg(), you have to use
+> mw.message().whatever() instead.
+> 
+> Alex's solution makes sense at a glance.
+Returning the Notification object would fix this, yes. Unfortunately, that change is still pending review.",1374170547,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"I'd say that this is expected behavior and a ""feature"" of the shorthand. Just like you can't have a message parsed by just doing mw.msg(), you have to use mw.message().whatever() instead.
+
+Alex's solution makes sense at a glance.",1373910457,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+mw.notify notifications can't be removed/hidden programmatically,"I had this problem in Gerrit change 5130. Had to depend on mediawiki.notification, add a 'return notif' to the mw.notification.notify function and use that instead of mw.notify.",1373855119,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-mjeduabrtvm33uiu3e4a,task_subcomment,NA
+"VisualEditor: Deleting new line icon (""↵"") between two links has no effect (?)","If an article has 
+
+[external link]
+[external link]
+
+It is rendered in VE as:
+
+[external link]↵[external link]
+
+Selecting the ↵ and pressing delete causes the ↵ to be removed, however the link break is not removed, and saving says that there are no changes.
+
+Example:
+https://en.wikipedia.org/wiki/Otis_%28album%29?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373850900,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-pkpe26l4yvkcclna5vl6,task_description,resolved
+"VisualEditor: Deleting new line icon (""↵"") between two links has no effect (?)","This appears to work correctly now.
+
+(The article no longer has this wikitext now, but I tried on an older version: https://en.wikipedia.org/w/index.php?title=Otis_(album)&oldid=512105119&veaction=edit – be sure to only preview changes and do not accidentally save the article.)",1429478513,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-pkpe26l4yvkcclna5vl6,task_subcomment,NA
+"VisualEditor: Deleting new line icon (""↵"") between two links has no effect (?)",Possibly a Parsoid bug?,1385384555,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pkpe26l4yvkcclna5vl6,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"The way VisualEditor handles links with square brackets, but no explicit anchor, can be confusing.  These links are generally discouraged on English Wikipedia, but still occasionally used.
+
+An example is https://en.wikipedia.org/w/index.php?title=User:Superm401/Sandbox&veaction=edit&oldid=564175896 .  The wikitext for this is just [http://example.com], which renders as a linked [1] (or whatever number it is in the page)
+
+However, you should edit the latest version of a page for testing this.  When you edit an oldid page, you won't be able to reproduce the ""Save page"" disable behavior I mention below.
+
+VisualEditor lets you backspace to remove the characters one by one, which does not really reflect the model of how the link works.  After one or more is removed, ""Save page"" un-greys.  However, when you go to review the changes, it says, ""Could not start the review because your revision matches the latest version of this page.""
+
+It does let you remove the link entirely, but to do so you need to explicitly remove each character (not just backspace once to delete the whole thing).
+
+Do a fresh load of the edit page (separate test).  Then, click the chain icon next to the link.  Then, press enter twice to exit the link dialog.  This time, review changes works.  The wikitext becomes:
+
+[http://example.com <nowiki>[1]</nowiki>]
+
+It probably should not change the link if you simply enter the link dialog and press enter without changing anything.  Also, forcing it to text like this is inconsistent with what happens if you delete the right bracket (see above).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373772420,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_description,resolved
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to Matthew Flaschen from comment #9)
+> Is it possible to convert an auto-numbered link to one with arbitrary text
+> (that's what the second part of the bug title refers to)?
+
+Yes, that's been possible for a while. In https://meta.wikimedia.org/wiki/Tech/News/2014/27?veaction=edit for example, click on one of the auto-numbered links to edit it, then click ""add label"" to convert it to a ""normal"" link.",1410238428,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,Is it possible to convert an auto-numbered link to one with arbitrary text (that's what the second part of the bug title refers to)?,1410235672,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"Change 143346 merged by jenkins-bot:
+Make it possible to create autonumbered external links from link inspector
+
+https://gerrit.wikimedia.org/r/143346",1409962256,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to Bartosz Dziewoński from comment #6)
+> (In reply to James Forrester from comment #2)
+> > You cannot …
+
+[…]
+
+> > * … convert an auto-numbered external link to a real external link; or
+> 
+> You can do that from ve.ui.MWLinkNodeInspector now, I don't know when it was
+> implemented.
+
+Yes, that was fixed a month or so ago with the creation of MWLinkNodeInspector.",1404237321,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to James Forrester from comment #2)
+> You cannot …
+> 
+> * … create an auto-numbered external link; 
+
+My patch https://gerrit.wikimedia.org/r/143346 implements this.
+
+> * … convert an auto-numbered external link to a real external link; or
+
+You can do that from ve.ui.MWLinkNodeInspector now, I don't know when it was implemented.
+
+> * … ""clear formatting"" on an auto-numbered external link.
+> 
+> I think the first two are valuable, but the third isn't, because we're
+> planning to remove the function of removing links and other rich styling
+> from the ""clear formatting"" function button.
+
+I don't think treating it as ""formatting"" makes sense anyway.",1404233558,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"Change 143346 had a related patch set uploaded by Bartosz Dziewoński:
+Make it possible to create autonumbered external links from link inspector
+
+https://gerrit.wikimedia.org/r/143346",1404233443,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to Matthew Flaschen from comment #3)
+> (In reply to Matthew Flaschen from comment #0)
+> > VisualEditor lets you backspace to remove the characters one by one, which
+> > does not really reflect the model of how the link works.
+> 
+> This is fixed.  It now highlights on first backspace, and erases on second,
+> which I think is handled the same as similar things.
+
+Yeah, sorry, forgot to say ""we've done a bunch of work on auto-numbered external links since this bug was filed, so most of this is fixed, however…"" at the top. :-)",1394498598,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"(In reply to Matthew Flaschen from comment #0)
+> VisualEditor lets you backspace to remove the characters one by one, which
+> does not really reflect the model of how the link works.
+
+This is fixed.  It now highlights on first backspace, and erases on second, which I think is handled the same as similar things.",1394490729,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"Current status:
+
+You can …
+
+* … edit the target of an auto-numbered external link to a different external link; and 
+* … edit the target of an auto-numbered external link to an internal link, and the anchor will automatically be set as the internal link value.
+
+
+You cannot …
+
+* … create an auto-numbered external link; 
+* … convert an auto-numbered external link to a real external link; or
+* … ""clear formatting"" on an auto-numbered external link.
+
+I think the first two are valuable, but the third isn't, because we're planning to remove the function of removing links and other rich styling from the ""clear formatting"" function button. Re-titling, setting priority.",1394479965,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones,"Also, if you highlight it, then use ""Clear formatting"", it does nothing.  I'm not sure what it should do (nowiki the URL?), but if it does nothing it should be greyed out.",1373772660,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-67wpkhw2f4styiyn7rfv,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"From English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):
+
+It's not a high priority, but still, a suggestion: the default search text, for an image search, is the complete page name. So, for example, if someone is editing a draft article, at User:WhateverEditorName/Article name, the default search text is ""WhateverEditorName/Article name"". It would be better if the default ignored the final slash and all text to the left of it; in this case, it would mean the default search would be ""Article name"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373722680,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-dokktb23gmzzq6sf5ts5,task_description,resolved
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"Change 137151 merged by jenkins-bot:
+Use subpage only for media search string
+
+https://gerrit.wikimedia.org/r/137151",1401919831,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"Change 137151 had a related patch set uploaded by Mooeypoo:
+Use subpage only for media search string
+
+https://gerrit.wikimedia.org/r/137151",1401825558,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"(In reply to comment #5)
+> No, not everyone has the editbugs permission.
+
+See bug 40497 for the editbugs problem.",1374841877,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"No, not everyone has the editbugs permission. Andre can give you it, CCing him.",1374840313,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"Ah, I see. :) I don't actually know if everyone has the rights to do so - bugzilla is a strange and wondrous land to me.",1373808017,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"You missed my main point in the title : it's text ""before"" the / that should be ignored, not the text ""after"" ;-)
+
+I don't see how I can change bug titles. Are you sure everyone has the rights to do so ?
+The only things I can do is add a comment, add an attachment, ...",1373807242,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"I've changed it. Titles are editable in bugzilla, much like wikitext. :)",1373806617,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages,"Bug title is incorrect, it would rather be something like ""Default search text for images should ignore text before /""",1373793904,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-dokktb23gmzzq6sf5ts5,task_subcomment,NA
+VisualEditor: Maxthon mobile browser click on link opens the link,"When using the Maxthon browser, clicking on a link (wiki or external) opens the link instead of allow ther to alter the link object.
+
+After the linked page is opened, returning to the VE shows the link object icon which alllows the link to be altered.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373671080,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-d2aeownijzkra4jifb23,task_description,declined
+VisualEditor: Maxthon mobile browser click on link opens the link,"Unfortunately closing this Phabricator task as no further information has been provided.
+
+After you have provided the information asked for and if this still happens, please set the status of this task back to ""Open"" via the {nav name=Add Action... > Change Status} dropdown. Thanks!
+",1598732594,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d2aeownijzkra4jifb23,task_subcomment,NA
+VisualEditor: Maxthon mobile browser click on link opens the link,"5.5 years later, is this still an issue? If it is, please provide Maxthon browser version information and a URL to reproduce. Thanks!",1590943358,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d2aeownijzkra4jifb23,task_subcomment,NA
+VisualEditor: Maxthon mobile browser click on link opens the link,It works better than Google Chrome. :P  See bug 51270.,1373672761,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-d2aeownijzkra4jifb23,task_subcomment,NA
+VisualEditor: Maxthon mobile browser click on link opens the link,Sounds like we may need to blacklist the Maxthon browser. :-(,1373671579,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d2aeownijzkra4jifb23,task_subcomment,NA
+VisualEditor: Initial (PHP-rendered) template display misaligned in Firefox,"Copied from English Wikipedia:
+
+Editing Gol Transportes Aéreos Flight 1907#Criminal proceedings I added two cleanup templates, {{update}} and {{prose}}. In the visual editor the two templates were differently left-aligned and different lengths, despite saving and displaying correctly. Reopening the page in the visual editor, the templates appear at their correct size and alignment, but do appear with an apparent blank line between them. Thryduulf (talk) 14:04, 12 July 2013 (UTC)
+
+See screenshot: 
+http://en.wikipedia.org/wiki/File:Visual_Editor_screenshot_-_templates_not_aligned.png
+
+****
+I could replicate this on Firefox (Windows 7) but not Chrome.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1373654340,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-sazwqzfkazbagnggd2du,task_description,resolved
+VisualEditor: Initial (PHP-rendered) template display misaligned in Firefox,Looks fine to me now?,1421778486,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sazwqzfkazbagnggd2du,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","I was following Sherry's kind advices in my sandbox at enwp http://en.wikipedia.org/wiki/User:Elitre_(WMF)/Sandbox:
+<<you can create an {{Infobox person}}, with parameters like ""name"" and ""occupation"".  Within those parameters, you can type the wikicode for any templates you want.  For example, you can give it a name parameter of ""Alice Expert((citation needed|date=July 2013}}"", which later gets processed properly as a template. >>
+An infobox appeared (well, a box with my sandbox title, actually), I saved, ""your edit was saved"" message appeared, the box isn't in the page anymore.
+Tried again, same thing. No trace of my activity in the history. Win 7, Vector, both Chrome and FF.
+
+Thanks,
+E.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=52640",1373644020,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_description,resolved
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","Change 150419 merged by jenkins-bot:
+Don't show PostEdit message if we made a null edit
+
+https://gerrit.wikimedia.org/r/150419",1406681112,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","Change 150419 had a related patch set uploaded by Alex Monk:
+Don't show PostEdit message if we made a null edit.
+
+https://gerrit.wikimedia.org/r/150419",1406673673,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't",Confirmed that this is still broken for VisualEditor (and not for wikitext editing).,1401997911,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","**swalling** wrote:
+
+(In reply to comment #3)
+> This is the same behaviour as the wikitext editor. We really should fix this
+> there first if we're changing behaviour for VisualEditor, so that they match.
+> 
+> CC'ed Steven - is there interest in changing for this case in core?
+
+As far as I know, this problem is solved for the wikitext editor. We should not be showing the post-edit confirmation on null edits. I just re-tested this to confirm with a null edit to an article. Is there something special about Elitre's case that I should try to replicate?",1385406579,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","This is the same behaviour as the wikitext editor. We really should fix this there first if we're changing behaviour for VisualEditor, so that they match.
+
+CC'ed Steven - is there interest in changing for this case in core?",1385399707,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","It might be worth adding that this actually works for Sherry:
+http://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&action=history .",1373648223,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+"VisualEditor: If making a null change, the ""Your edit was saved"" message appears, even if there were no changes and so it wasn't","It must be the ""template within a template"" thing, because it will save without that part. 
+Thanks,
+E.",1373644172,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-iwpzwdpnv56ft4z3qyze,task_subcomment,NA
+VisualEditor: Suppression of Cite error in templates still paints a phantom,"Screenshot
+
+Previously we had an issue that the cite extension would throw an error if you had a reference inside a template. That message is now suppressed, but only suppressed - it generates a substantial visual artefact on mouseover that previously contained the error message. See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11227}",1373635140,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-v6t7ev5julnky6rafmtd,task_description,resolved
+VisualEditor: Suppression of Cite error in templates still paints a phantom,I believe that this has been fixed for some time; I cannot replicate now.,1392426157,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v6t7ev5julnky6rafmtd,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"A few users at itwp requested that the list of articles you can choose as a wikilink target supports right-click on each title to view the page in another tab; and that disambiguation pages in the same list appear differently (maybe italicized as it currently happens in MediaWiki special pages?) Thanks!
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373580540,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_description,resolved
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,Verified the fix in test2 and production.,1416433806,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,The fix is verified in betalabs(beware of a difference between Link and Simple link!). The fix applies to the Link.,1415399485,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"Change 171488 merged by jenkins-bot:
+Matching pages from suggestions in link dialog now actually work as links
+
+https://gerrit.wikimedia.org/r/171488",1415310550,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"Change 171488 had a related patch set uploaded by SuchetaG:
+Matching pages from suggestions in link dialog now actually work as links
+
+https://gerrit.wikimedia.org/r/171488",1415237098,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"(In reply to Roan Kattouw from comment #3)
+> Both this and bug 50646
+Forget about bug 50646, my mistake, that one was about links in a different context. Comment #3 is still valid for this bug though.",1415226493,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"Both this and bug 50646 should be fixed by making the link suggestions real links, i.e. real <a> tags whose hrefs point to the pages they're suggesting.
+
+To do that, you'd need MWLinkTargetInputWidget to use a specialized subclass of MenuItemWidget; right now it creates plain MenuItemWidgets. Eventually that specialized subclass could be enriched to contain an image and a description etc., per the new designs for the link inspector. We could also use this new widget in MWTitleInputWidget.",1415054253,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"Bug 50240 asks for disambiguation pages to be distinguished in the list, so I'm retitling this one to focus on being able to open the targets with ctrl+click/right click. A user at en.wp has requested this functionality as well.",1378728231,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab,"You can use right click or ctrl+click on the links once inserted into the page, but per Bug 48915 this currently leads to the wrong namespace for links other than those to and from the article namespace.",1375706305,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-mwemxfe2uqw3orx4x7j5,task_subcomment,NA
+"VisualEditor: Context menu should appear in floated element, not in float origin","Screenshot of problem
+
+When a page contains multiple floated blocks after one another that each have a context menu (e.g. both transclusion) the ones after the first get the context menu in the wrong place. Namely on the second ""line"" of the article instead of where the element actually is (much further down).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11059}",1373540820,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-xtmuxxa5rnveu7aqbphi,task_description,resolved
+"VisualEditor: Context menu should appear in floated element, not in float origin","This works correctly these days:
+
+https://en.wikipedia.org/wiki/Wangbangsan?veaction=edit
+
+{F18142544}
+{F18142546}",1525988938,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-xtmuxxa5rnveu7aqbphi,task_subcomment,NA
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"Go to https://en.wikipedia.org/wiki/Mohammad_Azharuddin - look at the infobox image. Then hit ""edit"". I have no idea what's happening, but it shouldn't be.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+{T53932}
+{T55226}",1373539980,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_description,resolved
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"The issue as filed was resolved long time ago (see parent bug T52577), I filed T96667 to track the issue of oversized highlights.",1429615750,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_subcomment,NA
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"There are no screenshots here to show how it used to be broken, but it seems almost correct now. Only the highlight is displayed incorrectly.
+
+https://en.wikipedia.org/w/index.php?title=Mohammad_Azharuddin&oldid=564025381&veaction=edit
+
+{F117707}",1429477738,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_subcomment,NA
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"There are no screenshots here to show how it used to be broken, but it seems almost correct now. Only the highlight is displayed incorrectly.
+
+{F117707}",1429477722,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_subcomment,NA
+VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image,"The image displayed is the same, https://en.wikipedia.org/wiki/File:Mohammad_Azharuddin_Sangeeta_Bijlani.jpg. But it is cropped by CSS (using https://en.wikipedia.org/wiki/Template:Css_Image_Crop) and VE don’t let the image be cropped correctly…",1373541156,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-vjl47zkqiz6gdd6vv7bq,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","If would be nice for power users to have an option to disable the popup warning that occurs when you are trying to leave the edit mode while you have done some editing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373395140,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-7oml5hricm47p3yxxcje,task_description,resolved
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","Change 126994 merged by jenkins-bot:
+Check useeditwarning preference before showing warning when browsing away from editor
+
+https://gerrit.wikimedia.org/r/126994",1397849065,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","Change 126994 had a related patch set uploaded by Alex Monk:
+Check useeditwarning preference before showing warning when browsing away from editor
+
+https://gerrit.wikimedia.org/r/126994",1397746746,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","Change 126977 abandoned by Alex Monk:
+Add preference to disable leaving warning while editing
+
+Reason:
+gah, missed that one.
+
+https://gerrit.wikimedia.org/r/126977",1397745885,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","The preference 'useeditwarning' already exists, but this bug is about VisualEditor, maybe the VisualEditor does not respect the core preference or implement it's own edit warning.",1397744974,PHID-USER-qaoxfiqu6bxhd5ehlwhc,False,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning",Note that such a preference existed before and was removed when this functionality was merged into core from the Vector extension (bug 46514).,1397743302,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","I'd argue this is unwanted feature mania. If the warning doesn't make sense, remove it. If it does, leave it.",1397743017,PHID-USER-w5a723w3wes6jd5wskgg,False,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","Change 126977 had a related patch set uploaded by Alex Monk:
+Add preference to disable leaving warning while editing
+
+https://gerrit.wikimedia.org/r/126977",1397742780,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning","As mentioned in IRC, we should make this a core feature for MW and just re-use that preference rather than have a VE-specific one.",1373395795,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+"VisualEditor: Respect MediaWiki's ""useeditwarning"" user preference to disable leaving while editing warning",See http://youtu.be/gqqswqLd5Yw for what I mean,1373395370,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-7oml5hricm47p3yxxcje,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Editor requests support for adding non-breaking spaces (&nbsp;), keyboard shortcut?
+
+From MediaWiki Feedback:
+
+How do I enter a no-break space (& nbsp;) into the source text via the keyboard? Something like Ctrl+Space would be nice … And, BTW, can I see the difference between a regular space and a no-break space?
+
+Troubled @sset Work • Talk • Mail‎18:03, 8 July 2013
+
+--------------------------
+Alternative: {T70429}",1373383320,PHID-USER-ttyyrgsrkyonct7hizgv,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_description,resolved
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Test wiki on [[ http://localhost/patchdemo | Patch demo ]]  by Ed using patch(es) linked to this task was **deleted**:
+
+~~[[ http://localhost/patchdemo/wikis/bca3f56df9aa1ff71991cf889062e980/w/ ]]~~",1689773252,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"This should be fixed now, and the change will be deployed to Wikimedia wikis next week.
+
+Here's how the final version works:
+* On every operating system and keyboard layout, VisualEditor should support the built-in shortcut to insert a non-breaking space – e.g. Opt+Space on macOS, or various Linux keyboard layouts like those mentioned in T53045#5133074. (We'd appreciate if you could test with your favorite operating system / browser / language / keyboard layout / input method, as it's impossible for us to verify all combinations.)
+* In addition to that, on PC, we also support the Ctrl+Shift+Space shortcut to insert a non-breaking space.
+* These shortcuts insert the `&nbsp;` entity, in new wikitext editor as well as in the visual editor.",1618344115,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 255937 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Add command to insert non-breaking space%%%
+https://gerrit.wikimedia.org/r/255937",1618340744,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 676162 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (5d0701ea3)%%%
+https://gerrit.wikimedia.org/r/676162",1617229406,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 676162 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (5d0701ea3)%%%
+https://gerrit.wikimedia.org/r/676162",1617227930,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 665132 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Detect NBSPs being inserted deliberately by IMEs%%%
+https://gerrit.wikimedia.org/r/665132",1617227748,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Test wiki on [[ http://localhost/patchdemo | Patch Demo ]]  by Ed using patch(es) linked to this task was **deleted**:
+
+~~[[ http://localhost/patchdemo/wikis/ccf0f0ed62e0183bcd8312eb45d1ce97/w/ ]]~~",1615050934,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Test wiki **created** on [[ http://localhost/patchdemo | Patch Demo ]] by Ed using patch(es) linked to this task:
+
+http://localhost/patchdemo/wikis/bca3f56df9aa1ff71991cf889062e980/w/",1615049225,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Test wiki **created** on [[ http://localhost/patchdemo | Patch Demo ]] by Ed using patch(es) linked to this task:
+
+http://localhost/patchdemo/wikis/ccf0f0ed62e0183bcd8312eb45d1ce97/w/",1615047467,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 665132 had a related patch set uploaded (by Esanders; owner: Esanders):
+[VisualEditor/VisualEditor@master] Detect NBSPs being inserted deliberately by IMEs
+
+https://gerrit.wikimedia.org/r/665132",1613669036,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 255937 **restored** by Bartosz Dziewoński:
+[mediawiki/extensions/VisualEditor@master] Add command to insert non-breaking space, triggered by Ctrl+Space (PC) / Opt+Space (Mac)
+
+https://gerrit.wikimedia.org/r/255937",1613074784,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"I have a related remark. Even though the editor does not provide itself a keyboard shortcut to insert no-break spaces, your keyboard layout might allow you to write no-break spaces. If you’re in this case, an editor-provided keyboard shortcut to insert no-break spaces is completely unneeded.
+
+The ‘French (alternative)’ keyboard layout (it’s its name on Linux) allows to insert no-break spaces with AltGr-Shift-Space. Personally I use the ‘Bépo’ keyboard layout (a Dvorak-like for French) which allows to type no-break spaces with Shift-Space. But it doesn’t work in the VisualEditor (both in visual and wikitext modes): it inserts a normal space. However it works with the classic (2013?) wikitext editor. It is very weird, because I can type no-break spaces everywhere else on my system, except in some rich-text web editors (I have the same problem with WordPress). I’m very curious about the source of that bug. It might be something else though, that would need its own bug report.
+
+You can test the ‘French (alternative)’ keyboard layout easily on Linux by typing `setxkbmap fr oss` in a terminal. (Under Windows you must install it: use [[ http://mjulier.free.fr/clavier/clavier_fr-ossc.zip | this archive ]] linked from [[ https://fr.wikipedia.org/wiki/Aide:Lettres_accentu%C3%A9es#Avec_des_dispositions_de_clavier_am%C3%A9lior%C3%A9es | this Wikipedia page ]].)
+
+Actually… OK, I just figured out it’s a Firefox bug with the `contenteditable=""true""`. Typing no-break spaces does work in Chromium.",1556057434,PHID-USER-2fha2mym5lty6djs2qfl,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"I have a related remark. Even though the editor does not provide itself a keyboard shortcut to insert no-break spaces, your keyboard layout might allow you to write no-break spaces. If you’re in this case, an editor-provided keyboard shortcut to insert no-break spaces is completely unneeded.
+
+The ‘French (alternative)’ keyboard layout (it’s its name on Linux) allows to insert no-break spaces with AltGr-Shift-Space. Personally I use the ‘Bépo’ keyboard layout (a Dvorak-like for French) which allows to type no-break spaces with Shift-Space. But it doesn’t work in the VisualEditor (both in visual and wikitext modes): it inserts a normal space. However it works with the classic (2013?) wikitext editor. It is very weird, because I can type no-break spaces everywhere else on my system, except in some rich-text web editors (I have the same problem with WordPress). I’m very curious about the source of that bug. It might be something else though, that would need its own bug report.
+
+You can test the ‘French (alternative)’ keyboard layout easily on Linux by typing `setxkbmap fr oss` in a terminal. (Under Windows you must install it: use [[ http://mjulier.free.fr/clavier/clavier_fr-ossc.zip | this archive ]] linked from [[ https://fr.wikipedia.org/wiki/Aide:Lettres_accentu%C3%A9es#Avec_des_dispositions_de_clavier_am%C3%A9lior%C3%A9es | this Wikipedia page ]].)",1556057144,PHID-USER-2fha2mym5lty6djs2qfl,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"@Nnemo: +1 for Ctrl-Shift-Space which also works on LibreOffice.
+
+>>! In T53045#1244827, @Nnemo wrote:
+> # « The safe places for french quotes » do not work in the visual editor — this is a bug, by the way. 
+
+//All// the safe places fail in the visual editor. I sometimes have line breaks before colons, semicolons, etc.
+
+>>! In T53045#1757181, @Esanders wrote:
+> Or you could somehow annotate the whole word as nowrap. Arguably <nowrap>100 °C</nowrap> would be clearer than 100&nbsp;°C
+
+Forget `<nowrap>`. There’s an already existing HTML4 `<nobr>` tag. To me it would be relevant that MediaWiki supports it; MDN says it’s non-standard (while it’s supported by all browser engines), that may be the reason. The behavior you were looking for can still be obtained with code like what [[ https://en.wikipedia.org/wiki/Template:Nowrap | this template ]] uses.",1556056383,PHID-USER-2fha2mym5lty6djs2qfl,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),">>! In T53045#1953183, @Nnemo wrote:
+> Regarding Ctrl Space on PC, would Ctrl Shift Space work as well? It would be good.
+
+Yes, that patch actually used both of these combinations, but space in the commit summary is limited ;)",1453407360,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),">>! In T53045#1837188, @gerritbot wrote:
+> Change 255937 had a related patch set uploaded (by Bartosz Dziewoński):
+> Add command to insert non-breaking space, triggered by Ctrl Space (PC) / Opt Space (Mac)
+> 
+> [[https://gerrit.wikimedia.org/r/255937]]
+
+Option Space on Mac is a good combination. Regarding Ctrl Space on PC, would Ctrl Shift Space work as well? It would be good.
+",1453407233,PHID-USER-fjve3gq5wsmaaccti7pb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"If those are blockers, can they be listed as such?",1453297794,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 255937 abandoned by Bartosz Dziewoński:
+Add command to insert non-breaking space, triggered by Ctrl Space (PC) / Opt Space (Mac)
+
+Reason:
+This doesn't seem to be moving forward. And last time I checked, non-breaking spaces in VE-MW (implemented as MWEntity) had a bunch of problems like T119838, T119839, T119840; so we wouldn't really want to point users towards them without fixing that first.
+
+[[https://gerrit.wikimedia.org/r/255937]]",1453297689,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),I also think CTRL+space is quite a high profile shortcut to assign to a relatively uncommon feature.,1448822067,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Change 255937 had a related patch set uploaded (by Bartosz Dziewoński):
+Add command to insert non-breaking space, triggered by Ctrl Space (PC) / Opt Space (Mac)
+
+[[https://gerrit.wikimedia.org/r/255937]]
+",1448820160,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),">>! In T70429#1224015, @Esanders wrote:
+> Or you could somehow annotate the whole word as nowrap. Arguably <nowrap>100 °C</nowrap> would be clearer than 100&nbsp;°C
+",1445953865,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),">>! In T53045#1232726, @Ltrlg wrote:
+> Inserting only the character is not persistent: there is at least one browser which replaces non-breaking spaces with normal spaces in `<textearea>`s (may be Firefox? don’t remember). See [[https://fr.wikipedia.org/w/index.php?diff=114391750&oldid=114391708|this diff]] for an example of such a replacement (I read unfortunately more talk pages than articles and don’t remember an recent example in ns-0).
+
+//Sometimes//, a replacement of non-breaking spaces with normal spaces in the text area occurs (occurred). This is (was) caused by a bug of Firefox, that was fixed years ago. Now, this happens rarely, because people having a fossil Firefox are rare. Over time, such replacements will be rarer and rarer.
+
+>>! In T53045#1232726, @Ltrlg wrote:
+> Of course there are safe places (before colons, inside French quotations marks) where MediaWiki does not require a special space to render a non-breaking one and where it would make no difference.
+
+These safe places exist. //But ://
+
+# I think that these safe places are a setup specific to the site fr.wikipedia.org, and do not apply in the general case of a MediaWiki. I may be wrong here. 
+# These safe places do not work in links. 
+# These safe places do not work in wikicode. 
+# « The safe places for french quotes » do not work in the visual editor — this is a bug, by the way. 
+",1430308930,PHID-USER-fjve3gq5wsmaaccti7pb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Inserting only the character is not persistent: there is at least one browser which replaces non-breaking spaces with normal spaces in `<textearea>`s (may be Firefox? don’t remember). See [[https://fr.wikipedia.org/w/index.php?diff=114391750&oldid=114391708|this diff]] for an example of such a replacement (I read unfortunately more talk pages than articles and don’t remember an recent example in ns-0).
+
+Of course there are safe places (before colons, inside French quotations marks) where MediaWiki does not require a special space to render a non-breaking one and where it would make no difference.",1429827478,PHID-USER-5pyvkdz65d5h5vxebodc,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"Inserting only the character is not persistent: there is at least one browser which replaces non-breaking spaces with normal spaces in `<textearea>`s (may be Firefox? don’t remember). See [[https://fr.wikipedia.org/w/index.php?diff=114391750&oldid=114391708|this diff]] for an example of such a replacement (I read unfortunately more talk pages than articles and don’t remember an recent example in ns-0).
+
+Of course there are safe places (before colons, inside French quotations marks) where MediaWiki does not require the a special space to render a non-braking one and where it would make no difference.",1429827443,PHID-USER-5pyvkdz65d5h5vxebodc,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"For this feature, something would need to be clarified :
+
+What would the keyboard combination insert in the wikicode ?
+
+# The character non-breaking space 
+# The HTML entity ##&nbsp;## 
+
+These are two different things.
+
+For this feature, I would recommend inserting the character non-breaking space. Inserting the non-breaking space character leaves the wikicode natural and readable. Well, as readable as the wikicode already is. ;-) 
+
+",1429807031,PHID-USER-fjve3gq5wsmaaccti7pb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),"For this feature, I suggest Ctrl Shift Space rather than Ctrl Space.
+
+Reasons :
+
+# Ctrl Space is already taken for Spotlight on Mac. 
+# The Word feature for entering a non-breaking space is pressing Ctrl Shift Space. 
+
+The Word feature is quite well known. Having an inconsistency here would confuse users.
+",1429806239,PHID-USER-fjve3gq5wsmaaccti7pb,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP),Related: https://phabricator.wikimedia.org/T70429,1425904145,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-33ykzddzyqsfzj3qavxw,task_subcomment,NA
+VisualEditor: Ability to switch image used whilst maintaining the caption and other settings,"You should be able not only to change image caption, but select another image.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54285",1373372220,PHID-USER-s2t4lzis4swnj7hbvkgn,False,PHID-TASK-cq56uabry7nuedxb56e6,task_description,resolved
+VisualEditor: Ability to switch image used whilst maintaining the caption and other settings,*** Bug 52580 has been marked as a duplicate of this bug. ***,1402608867,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cq56uabry7nuedxb56e6,task_subcomment,NA
+VisualEditor: Ability to switch image used whilst maintaining the caption and other settings,*** Bug 53409 has been marked as a duplicate of this bug. ***,1377621974,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-cq56uabry7nuedxb56e6,task_subcomment,NA
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title","Try to add image to http://uk.wikipedia.org/wiki/29er_(%D0%B2%D0%B5%D0%BB%D0%BE%D1%81%D0%B8%D0%BF%D0%B5%D0%B4) 
+
+It suggests no images for article ""29er (велосипед)"", but it will if you search by Commonscat template parameter or english interwiki
+
+--------------------------
+**See Also**:
+{T54464}",1373372040,PHID-USER-s2t4lzis4swnj7hbvkgn,False,PHID-TASK-faz57akdhnnsrbbitdmo,task_description,open
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title","It probably should be tagged with it. Sorry, VE tasks are often not consistently tagged (other than with the #visualeditor tag).",1551212560,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-faz57akdhnnsrbbitdmo,task_subcomment,NA
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title","@matmarex thanks for finding this, I did look before filing but this task wasn't tagged with #visualeditor-media, is that the right tag? ",1551207441,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-faz57akdhnnsrbbitdmo,task_subcomment,NA
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title","I don't think this would require T68108. It seems possible to implement today (although maybe inefficient…)
+* Given a page e.g. https://en.wikipedia.org/wiki/The_Fighting_Temeraire, look up its Wikidata entry e.g. https://www.wikidata.org/wiki/Q257580
+* Given the Wikidata entry, look up the Commons gallery/category using the 'commons' sitelink, or the category using the ""Commons category"" (`P373`) property
+* Given the Commons category, show search results from it (maybe using [[https://www.mediawiki.org/wiki/Help:CirrusSearch#Intitle_and_incategory|incategory:]] search)",1551206616,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-faz57akdhnnsrbbitdmo,task_subcomment,NA
+"VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title",I think doing this via Wikidata identity would be a better way forward.,1385398709,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-faz57akdhnnsrbbitdmo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,"Two editors have commented independent in different place over the weekend on English Wikipedia about how they wish they could access the edit summary while using the VE instead of on save, because they track their changes as they go.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373304120,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_description,open
+VisualEditor: Provide simultaneous access to editor and edit summary,@Sadads has suggested that the Tab key be used to switch between the article and the edit summary window.,1482427198,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,(Aaand there's an exception for that. See T114857.),1444222841,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,"(Although they won't be able to do so if they enabled the warning that doesn't allow to save without providing an edit summary, as noted at de.wiki. )",1444153431,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,"On a related note: There's also no edit summary in the diff view (""review you changes""), just a save button. This tempts users to save without leaving an edit summary.",1443996374,PHID-USER-ctff2aq5r64yvikejdwo,True,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,"Think this is also happening on PL.WP. 
+
+""Jeśli w okienku z polem służącym do opisu dokonanej zmiany klikniemy w link dotyczący sposobu opisywania zmian zostaniemy przekeierowani do strony Wikipedii z opisem tychże skrótów, jednak strona ta wyświetla się w tym samym małym okienku. Uniemożliwia to powrócenie to opisu modyfikacji a jednocześnie uniemożliwia zapisanie dokonanej zmiany w danym artykule. Michał (dyskusja) 11:36, 5 lis 2013 (CET)""
+
+https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#B.C5.82.C4.85d_w_okienku_opisu_zmian.",1383663034,PHID-USER-brn4v5ta45bnw4f5as3h,True,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Provide simultaneous access to editor and edit summary,+1. This is a particularly useful feature of the old editor.,1374780006,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-oyxqdt66z23wvh7pe5mo,task_subcomment,NA
+VisualEditor: Reduce padding in editnotice popup because some existing edit notices already have some margin,"An editor from pt.wikipedia writes:
+
+[E]ditnotices seems strange inside the flyout because there's a weird padding inside the popup, without the padding the templates would look nicer (there´s already padding in most edinotices templates by default). Dianakc (talk) 23:56, 6 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373302800,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-yxjf5ed7ojxtui2z6sss,task_description,open
+VisualEditor: Reduce padding in editnotice popup because some existing edit notices already have some margin,"(In reply to comment #2)
+> Hi James,
+> 
+> I don't know what mean you by normal edit notices :) A simple 100% div, with
+> background color but without padding would look weird inside the flyout.
+> We are rethinking the editnotices design/content and right now they look
+> somewhat awkward within this asymmetrical padding. If someone ever need a
+> margin it can be done within the editnotices itself, but this mandatory
+> padding
+> limits the design a lot.
+
+Normal edit notices are text only (or bold/italics/links). Adding any further styling, including <span>s, <div>s, images, etc. is likely to break in a variety of situations and isn't really intended behaviour for the tool.",1379846011,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yxjf5ed7ojxtui2z6sss,task_subcomment,NA
+VisualEditor: Reduce padding in editnotice popup because some existing edit notices already have some margin,"Hi James,
+
+I don't know what mean you by normal edit notices :) A simple 100% div, with background color but without padding would look weird inside the flyout.
+We are rethinking the editnotices design/content and right now they look somewhat awkward within this asymmetrical padding. If someone ever need a margin it can be done within the editnotices itself, but this mandatory padding limits the design a lot.",1375490603,PHID-USER-2u4zc7zmyw5qldxupou6,True,PHID-TASK-yxjf5ed7ojxtui2z6sss,task_subcomment,NA
+VisualEditor: Reduce padding in editnotice popup because some existing edit notices already have some margin,"(In reply to comment #0)
+> An editor from pt.wikipedia writes:
+> 
+> [E]ditnotices seems strange inside the flyout because there's a weird padding
+> inside the popup, without the padding the templates would look nicer (there´s
+> already padding in most edinotices templates by default). Dianakc (talk)
+> 23:56,
+> 6 July 2013 (UTC)
+
+I'm not sure that it's a better solution to get editors to make edit notices in uneditable HTML boxes, rather than the padding be system-level. The padding is designed to take normal edit notices; if you make fancy ones that break, the onus is generally on you. :-)
+
+Note that we're planning on having setting/editing/removing page-level edit notices built into VisualEditor in the next few months, which will make enwiki's solution available to all wikis.",1373303074,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yxjf5ed7ojxtui2z6sss,task_subcomment,NA
+Messing up Math formulas,"Several concerns noted about VisualEditor messing with math formulas when (evidently) the user was not attempting to edit the formula at all.
+
+https://en.wikipedia.org/w/index.php?title=Raising_and_lowering_indices&curid=11325244&diff=563062676&oldid=560490441
+
+https://en.wikipedia.org/w/index.php?title=Regression_analysis&curid=826997&diff=563265603&oldid=561802206
+
+https://en.wikipedia.org/w/index.php?title=Bipartite_double_cover&curid=21241712&diff=563327691&oldid=554035797
+
+I'm not sure if this is related to an existing bug or a different kind of thing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373289300,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-tlllnzr2q3k5zu3yv6nh,task_description,resolved
+Messing up Math formulas,"**cbm.wikipedia** wrote:
+
+This is a duplicate of bug 50291. It is a round tripping error in VisualEditor.
+
+%%%*** This bug has been marked as a duplicate of bug 50291 ***%%%",1373592757,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-tlllnzr2q3k5zu3yv6nh,task_subcomment,NA
+Messing up Math formulas,"The changes don't actually change the visual output. Just the way italics (used to mark variables) and superscript and subscript tags interact. So it might change ''e''<sup>''x''</sup> to ''e<sup>x</sup>'' you could say the former is better semantically. Other cases will split a complex superscript into two separate subscripts  ''K''<sub>''n'',''n''</sub> into ''K<sub>n</sub>''<sub>,''n''</sub>, visually the same but worse semantically.
+
+Marking as low priority as no visible change.",1373290493,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-tlllnzr2q3k5zu3yv6nh,task_subcomment,NA
+"VisualEditor: License text in save dialog is light gray, giving it a 'disabled' appearance","The save dialog uses a gray color on a very small text. This isn't good for contrast, and gives it rather 'light' color which might communicate a 'disabled' state to some users, which you don't want with a license text.
+
+Just as with Special:UserLogin, I think we should switch to a slightly darker gray on small text.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373232780,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-3ydcw352v55xv74m7jhi,task_description,resolved
+"VisualEditor: License text in save dialog is light gray, giving it a 'disabled' appearance",This has been [[ https://phabricator.wikimedia.org/rEVED48db1c16f81091f62d82539b2a41fede49ba7915 | changed to `#54595d` in wmf/1.29.0-wmf.7 ]] and fulfills WCAG 2.0 level AAA conformance.,1483659684,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-3ydcw352v55xv74m7jhi,task_subcomment,NA
+"VisualEditor: License text in save dialog is light gray, giving it a 'disabled' appearance",The meta-design of the save process for wikitext and for VisualEditor are being reviewed by Design and by Legal right now; hopefully there'll be an update soon enough.,1385380440,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3ydcw352v55xv74m7jhi,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"Perhaps when the [[WP:Tutorial]] on enwiki is updated for VE, we will want to enable VE on the tutorial sandboxes.
+
+Also, when VE is enabled for anonymous editors, we might want to turn on VE in the enwiki [[WP:Sandbox]], because otherwise anons won't have anywhere to play with VE (they cannot create user pages).
+
+Perhaps a category (similar to the way AFTv5 does it) or MediaWiki page (like Echo blacklist) would be the way to do it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373193180,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-cudr7dbtubp7jj3ldgha,task_description,open
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"It’s great that enabling VE in Wikipedia namespace is less risky now, but I think the current feature request (enabling it more granularly than on the namespace level) is still valid, exactly because of the limitations (risks) you’ve mentioned.",1722169176,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"Turning VE on at Wikipedia: namespace was a problem as some pages at this namespace are used for discussions. The visual editor is not designed to handle discussions, but Discussion tools are. Now that DT is available everywhere,[[ https://www.mediawiki.org/wiki/Help:VisualEditor/FAQ#WPNS |  it is possible to enable VE at namespaces that are used for discussions, with limitations ]]. ",1721988681,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"This is a huge pain point, newbies cannot try out the tool in the sandbox that was created specifically for them…
+
+>>! In T52883#5193760, @matmarex wrote:
+> You can put a big blue button or something with such a link on sandbox pages, see e.g. <https://de.wikipedia.org/wiki/Wikipedia:Spielwiese>.
+This has three issues:
+* The link is not where it is on other pages. On the one side, it’s more prominent, which is good, but on the other side, it’s inconsistent, which is bad.
+* It uses an external link, which means that
+** the domain name is fixed, it’s `de.wikipedia.org` even if the user browses through `de.m.wikipedia.org` (i.e. mobile view); if they’re not redirected back to the mobile site automatically, they find themselves in a totally different interface than where they were;
+** a new page load is initiated upon clicking, in contrast to the usual VE loading, where the page isn’t entirely reloaded.",1624489831,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"Also, note that the &veaction=edit URL parameter can now also be used to open VE on pages where it's normally not available (T221892). You can put a big blue button or something with such a link on sandbox pages, see e.g. <https://de.wikipedia.org/wiki/Wikipedia:Spielwiese>.",1558194860,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"If we ever do it, I think it should be done using a double-underscore keyword placed on the page (or in a transcluded template), e.g. `__VISUALEDITOR__`. This would be analogous to e.g. the `__NEWSECTIONLINK__` keyword.",1558194738,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"While bug 55900 now allows logged-out users to invoke VE in the namespaces where it is already available, in the meantime I hope communities created temporary sandboxes in one of said namespaces :) (The Italian one did, it's basically a subpage of mine).",1388962544,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes),"For the record: on ptwiki we also have a few sandboxes on Project namespace:
+[[pt:Special:PrefixIndex/WP:Página_de_testes/]]",1373856039,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-cudr7dbtubp7jj3ldgha,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"**Author:** `KilliondudeWP`
+
+**Description:**
+1) Have categories on a page with a stub tag underneath - https://en.wikipedia.org/w/index.php?title=Rosebud_Ranch&oldid=563208475 (note that this is SOP on enwiki per https://en.wikipedia.org/wiki/Wikipedia:ORDER#ORDER )
+
+2) Edit the categories using VE to deleted one and modify another - https://en.wikipedia.org/w/index.php?title=Rosebud_Ranch&diff=563208669&oldid=563208475
+
+3) End up with newly formed category underneath the stub template as well as some line breaks taken out. 
+
+I reported this in #mediawiki-visualeditor while everyone was sleeping. This is something that might just need an enwiki fix since we like to put stub tags under categories.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+* {T51143}
+* {T55508}
+* {T74048}",1373181360,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zg7dy72bmhpynpamskgq,task_description,open
+VisualEditor: Place page meta-data in expected order,"There's also an inconsistency in how VE inserts `{{DEFAULTSORT}}` and categories.
+
+If you edit the page's properties to add a `{{DEFAULTSORT}}`, apply, then edit the properties again to add a category, then the `{{DEFAULTSORT}}` is added before the category, as is usually expected based on community guidelines.
+
+However, if you do the sequence in the other order (add a category first, apply, then edit the properties again to add a `{{DEFAULTSORT}}`), then the `{{DEFAULTSORT}}` is added //after// the categories.
+
+Since the user doesn' t have a way to specify or change that order, VE should be consistent in how it outputs them in the wikitext.
+",1428688398,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,*** Bug 51714 has been marked as a duplicate of this bug. ***,1377833797,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"The reasons behind [[WP:ORDER]] are:
+1) We want ""stub categories"" to appear Last in the list of categories.
+2) We want 2 blank lines preceding stub-templates, for whitespace. (Other ways of achieving this are more complex, or don't work for articles with multiple stub-templates.)
+See example of both factors, at http://en.wikipedia.org/w/index.php?title=Milo_McCarger&oldid=532917627
+
+
+(To quote the [[WP:ORDER]] reference here, for ease of access: ""While categories are entered on the editing page ahead of stub templates, they appear on the visual page in a separate box after the stub templates. One of the reasons this happens is that every stub template generates a stub category, and those stub categories appear after the ""main"" categories. Another is that certain bots and scripts are set up to expect the cats, stubs and ILLs to appear in that order, and will reposition them if they don't. Therefore, any manual attempt to change the order is doomed unless the bots and scripts are also altered."")",1373650166,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"(In reply to comment #2)
+> The problem here is not specifically ""stub templates"", but the general idea
+> that some items of content - in this case, on one wiki, a sub-type of
+> template that is trivially-identifiable to humans but not necessarily so for
+> software - should have its own special ordering when the page is
+> re-serialised. The explanation for why this (relatively new?) policy change
+> for enwiki seems to be absent [...]
+
+This practice has been documented at [[WP:LAYOUT]] for at least a few years. It's been standard practice since before then. There's a note in the current version of that document that explains that it's due to a battle with bots (notable AutoWikiBrowser, as I recall). Because most people add stub categories with AWB or similar scripts, the conventions those tools use become (or rather, became) wiki conventions.
+
+I agree with the general point that we should move this type of information (whether a page is a stub and if so, what kind of stub) to a metadata area.",1373422161,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,Moving back to VE as this is handled in VE until we move metadata out of the body.,1373400958,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"In the medium term I'd like to move metadata like categories out of the page and into a header section (see bug 49143).
+
+In the meantime, we serialize metadata wherever the VE places it in the DOM.",1373400711,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"I've re-titled this bug to ""Provide a way for Parsoid to know that some types of some content on some wikis go after the meta-data, not in the body of the document"", which I think captures the 'ask' here most generally. I believe that currently, Parsoid puts all content first, followed by meta-data in the order ""Magic words (e.g. DEFAULTSORT) > Categories > Language links"", which is MediaWiki standard style.
+
+The problem here is not specifically ""stub templates"", but the general idea that some items of content - in this case, on one wiki, a sub-type of template that is trivially-identifiable to humans but not necessarily so for software - should have its own special ordering when the page is re-serialised. The explanation for why this (relatively new?) policy change for enwiki seems to be absent, unlike for the other elements; it adds complexity without justifying why, as far as I can see.
+
+I think it is unlikely that we will change things so that Parsoid has an understanding of what kinds of content it is dealing with, much less a concept of per-wiki settings for where the content should be positioned. Just because the English Wikipedia likes things one way doesn't mean we should impose those standards on everyone else - for example, another wiki might like their categories at the top, or their semi-structured data template (like PERSONDATA) at the very bottom, or… any one of countless other possible orderings that don't effect readers. Remember that VisualEditor is currently available on 300 wikis, and is being developed for all ~900 Wikimedia wikis, the ~300,000 Wikia wikis, and numerous other wikis as well.
+
+This is not saying that this request is impossible, that the barriers are insurmountable, that it will never be done, or that our mind is set for ever on this matter. However, coming up with a system for specifying this on a per-wiki basis, and justifying us spending (significant) developer time adding complexity and confusion to the code and the user interfaces is going to be challenging. This is time that would otherwise be spent on fixing bugs, on editing tables, on a better reference dialog, on supporting language variants as used in (e.g.) Chinese. I don't think that we can prioritise this above these other issues; sorry.",1373395467,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Place page meta-data in expected order,"This is not minor, unless enwiki has agreed to abandon the long-established rules set out in http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Layout#Order_of_sections . I have just added a category to [[Permyak Salty Ears]] (it's a sculpture I was stub-sorting), and it has been put below the stub tag and interwiki link, and not adjacent to two existing categories. 
+
+There are also rules for the top of the article: navigational hatnotes go before anything else. Not in VE. WP:AWB sorts these out misplaced elements as part of ""General fixes""; Twinkle can put a newly-added maintenance tag within the {{tl|multiple issues}} tag. It is very disappointing that VE seems incapable of offering the same level of helpfulness as these existing systems have offered for years.",1373371153,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-zg7dy72bmhpynpamskgq,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"When I edited an internal link and pasted in Work_breakdown_structure#Terminal_element as the new link target, the link editor widget thought that it was a new page, because it didn't understand that the # referenced an anchor within that page.
+
+However, that was just a harmless warning - it did work. So I am classifying this as minor severity, because it is merely an incorrect warning message that could confuse editors.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373173500,PHID-USER-bug3zrlooz3bdmi4fyl7,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_description,resolved
+VisualEditor: Link input widget should suggest section links,Filed remaining work as T367739,1718627142,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by ESanders (WMF) using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/dacb60851e/w/ ]]~~",1713878088,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 975293 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Link inspector: Use searchFragments feature in TitleWidget%%%
+https://gerrit.wikimedia.org/r/975293",1701967466,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 975292 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] TitleWidget: Allow searching for section fragments%%%
+https://gerrit.wikimedia.org/r/975292",1701967461,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"3 & 4 are fixed. 1 is more complicated as it requires more interaction between VE and this core component (VE needs to override the list of available sections, rather than use an API call). I think that should probably be fixed later.",1701100973,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,">>! In T52881#9352286, @gerritbot wrote:
+> Change 976691 had a related patch set uploaded (by Sophivorus; author: Sophivorus):
+> %%%[mediawiki/extensions/ParserFunctions@REL1_39] Backport fix of implicit conversion to int%%%
+> https://gerrit.wikimedia.org/r/976691
+
+Tagged the wrong bug, sorry.",1700655480,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 976691 had a related patch set uploaded (by Sophivorus; author: Sophivorus):
+%%%[mediawiki/extensions/ParserFunctions@REL1_39] Backport fix of implicit conversion to int%%%
+https://gerrit.wikimedia.org/r/976691",1700655252,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Thanks for the feedback.
+1 sounds useful and should be fixable.
+I think points 2-3 can be addressed later in follow ups.
+4 should be fixed, we should replace underscores when normalising.
+5: if you start typing # immediately you get no page name. Removing the page name could arguably be a Parsoid job, or something we should leave in if the user types it explicitly, but we could remove it locally.",1700639837,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Really nice UX! 🙂
+Some minor limitations I noted:
+- Added/edited headings in the current editing session are not reachable.
+- Since selecting the target page with directional keys does not fill the text input (what a browser URL bar usually does), in order to link an external section without fully typing the target page name, you have to first add a link to the page name, then edit it to add the fragment.
+- For local page section suggestions, a middle click opens the page in visual editing mode rather than reading mode like for external sections.
+- It does not recognize underscore as space equivalent; so copying the fragment from a URL looks like it is not an existing section.
+- For local sections, the resulting wikitext uselessly adds page name before fragment. (T239847)",1700257312,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by ESanders (WMF) using patch(es) linked to this task:
+[[ https://patchdemo.wmflabs.org/wikis/dacb60851e/wiki/Douglas Adams?veaction=edit ]]",1700234169,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 975293 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Link inspector: Use searchFragments feature in TitleWidget%%%
+https://gerrit.wikimedia.org/r/975293",1700233938,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"Change 975292 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/core@master] TitleWidget: Allow searching for section fragments%%%
+https://gerrit.wikimedia.org/r/975292",1700233858,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"When adding links to sections in the current page, the UI may be a third tab in the Link popup (after the ""Search pages"" and ""External link"" tabs) called ""Section link"" (or similar). In this tab, the existing section titles would be listed (possibly in a hierarchical TOC fashion) and clicking on a section would add a link to that section.",1529619847,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"{T112898} has been fixed but `[[#section|text]]` just inserted is still red (all the same, it displays correctly for links which were already present before loading VisualEditor).",1470731559,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,*** Bug 61428 has been marked as a duplicate of this bug. ***,1401417280,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"(In reply to comment #11)
+> John reports today that ""It used to be possible, in VE, to link to another
+> section of a page (say, Bank#History). Now, when section information is
+> added,
+> in the Link/Hyperlink dialog box, VE just deletes it when the user presses
+> [return] or exits (in any way) that dialog box.""
+
+Noting for posterity that that was bug 53219, which has now been fixed.",1377527665,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"John reports today that ""It used to be possible, in VE, to link to another section of a page (say, Bank#History). Now, when section information is added, in the Link/Hyperlink dialog box, VE just deletes it when the user presses [return] or exits (in any way) that dialog box.""",1377170602,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"The VE software has changed (at least a week ago, maybe longer) for this issue. Now pressing [Return] does not remove the ""#Whatever"" text that the user typed, for the section link. So this bug is now primarily a display issue.
+
+(In reply to comment #7)
+> This isn't just a display problem, and it is NOT an enhancement - it's a real
+> defect because editors are unlikely to take the time - as I did - to figure
+> out
+> how to make section links work.
+> 
+> Here's what happens now: The editor finds an article to link to (good UI;
+> much
+> better than the wikitext editor); then he/she starts typing the section link
+> (#whatever). The link name turns red (that's the display issue), and it
+> doesn't
+> suggest section names (that would be a really slick enhancement; if you do
+> this
+> well, people are going to love you). Instead, when the editor is done typing
+> the section information, one of four things can happen:
+> 
+> * The editor presses Enter/Return (per the user guide), and the section
+> information is REMOVED by VE. That is clearly a defect in the software.
+> 
+> * The editor presses the close icon (<) (per the user guide), and the section
+> information is REMOVED by VE. That is clearly a defect in the software.
+> 
+> * The editor clicks somewhere else on the page, and the section information
+> is
+> REMOVED by VE. That is clearly a defect in the software.
+> 
+> * The editor clicks on the area ABOVE the input box, the area containing the
+> word ""Hyperlink"", and VE is happy, and saves the section information. (I'm
+> going to add that to the user guide, but that wouldn't do nearly as much good
+> as changing, in the software, what happens in the first three situations,
+> above.",1375822006,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,The suggestion of the sections that can be linked are also requested at it.wp.,1375739703,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,*** Bug 51445 has been marked as a duplicate of this bug. ***,1374029473,PHID-USER-fwlidikyeorzj35hufwu,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"This isn't just a display problem, and it is NOT an enhancement - it's a real defect because editors are unlikely to take the time - as I did - to figure out how to make section links work.
+
+Here's what happens now: The editor finds an article to link to (good UI; much better than the wikitext editor); then he/she starts typing the section link (#whatever). The link name turns red (that's the display issue), and it doesn't suggest section names (that would be a really slick enhancement; if you do this well, people are going to love you). Instead, when the editor is done typing the section information, one of four things can happen:
+
+* The editor presses Enter/Return (per the user guide), and the section information is REMOVED by VE. That is clearly a defect in the software.
+
+* The editor presses the close icon (<) (per the user guide), and the section information is REMOVED by VE. That is clearly a defect in the software.
+
+* The editor clicks somewhere else on the page, and the section information is REMOVED by VE. That is clearly a defect in the software.
+
+* The editor clicks on the area ABOVE the input box, the area containing the word ""Hyperlink"", and VE is happy, and saves the section information. (I'm going to add that to the user guide, but that wouldn't do nearly as much good as changing, in the software, what happens in the first three situations, above.",1373991618,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,Worth noting here the comments on bug 50945 about cases where display text != link text (piped links),1373526525,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,*** Bug 51121 has been marked as a duplicate of this bug. ***,1373520194,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"(In reply to comment #3)
+> When reporting the duplicate bug (sorry, this one didn't come up in my
+> search)
+
+Don't worry, it's my fault for not triaging earlier. :-)
+
+> I wondered whether this was related to Bug 33094
+
+I don't believe so (though we should get that fixed soon too, of course).",1373518375,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"When reporting the duplicate bug (sorry, this one didn't come up in my search) I wondered whether this was related to Bug 33094",1373476336,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,*** Bug 51118 has been marked as a duplicate of this bug. ***,1373475138,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+VisualEditor: Link input widget should suggest section links,"* The link inspector needs to understand that if Foo exists, linking to Foo#Bar isn't a red link
+* Ideally the link inspector should have introspection of articles' sections so that it can suggest which headings to link to
+* This should also work for naked (local) section links - i.e., linking to just #Bar on the local page.",1373475114,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dfaq53vqbeqqxygg7gqr,task_subcomment,NA
+Difficult for users to know what exact version of each extension is running on the cluster,"This bug was cloned from bug 50120.
+
+(In reply to bug 50120 comment #5)
+> We believe that this is now fixed (due to fixes in Parsoid). Please re-open
+> if it recurs.
+
+How do you know what version of VisualEditor or Parsoid is running? Looking at Erik's comment (bug 50120 comment 6), I try to go to [[Special:Version]] to figure out what exact versions of Parsoid and VisualEditor are running (for debugging purposes and to figure out if this problem is still present in the latest bleeding edge code) and I find that Parsoid and VisualEditor are both marked as version 0.1.0. Not quite helpful for debugging. Splitting this issue out.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373161140,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-grvae3imieydt4li7k7h,task_description,resolved
+Difficult for users to know what exact version of each extension is running on the cluster,"With bug 53972 now fixed, this is now fixed in Beta Labs (see http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version for git hashes against each extension), and for VisualEditor specifically (which was the original locus of this suggestion) it's also available at the bottom of the ""help"" menu.",1404841447,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-grvae3imieydt4li7k7h,task_subcomment,NA
+Difficult for users to know what exact version of each extension is running on the cluster,"(In reply to comment #1)
+> Could we switch on the configuration we have on beta labs for Special:Version
+> for other wikis? (Perhaps as a page option - ?showversions=true or whatever,
+> so as to avoid confusing users.)
+
+I'm not sure of the history here, but perhaps it could show the extra info only for logged-in users?",1373217143,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-grvae3imieydt4li7k7h,task_subcomment,NA
+Difficult for users to know what exact version of each extension is running on the cluster,"(In reply to comment #0)
+> This bug was cloned from bug 50120.
+> 
+> (In reply to bug 50120 comment #5)
+> > We believe that this is now fixed (due to fixes in Parsoid). Please re-open
+> > if it recurs.
+> 
+> How do you know what version of VisualEditor or Parsoid is running? Looking
+> at
+> Erik's comment (bug 50120 comment 6), I try to go to [[Special:Version]] to
+> figure out what exact versions of Parsoid and VisualEditor are running (for
+> debugging purposes and to figure out if this problem is still present in the
+> latest bleeding edge code) and I find that Parsoid and VisualEditor are both
+> marked as version 0.1.0. Not quite helpful for debugging. Splitting this
+> issue
+> out.
+
+This is a cluster configuration issue; it's trivial to find out which version of VisualEditor is running in Beta Labs, as each MW extension is shown in http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version with the date and a link to the git.wikimedia.org page of the currently-running commit. I don't think bumping version numbers on extensions with every deployment is a great idea, however.
+
+(Note that this doesn't help for Parsoid, however, as it's not actually an MW extension, despite the confusing repo name.)
+
+For ultra-power-users like me, I ""just"":
+
+* Find from Special:Version which branch the site I'm interested in is on
+* Look up in gerrit any changes to that branch since it was cut https://gerrit.wikimedia.org/r/#/q/status:merged+project:mediawiki/core+branch:wmf/1.22wmf8,n,z
+* Find the latest time the extension was updated in there based on commit title (hopefully helpful), or if never, from the original cut commit
+* Take that commit ID (in this case, ""11453371c637b50cd3f37e80893d9a80b0c044a5"") and sling it into gerrit (in this case, https://gerrit.wikimedia.org/r/#/q/11453371c637b50cd3f37e80893d9a80b0c044a5,n,z gives the result).
+* Success! Umm.
+
+However, this isn't remotely a great solution for even quite serious developers on staff or in the community, let alone regular users who might want to file bugs.
+
+Could we switch on the configuration we have on beta labs for Special:Version for other wikis? (Perhaps as a page option - ?showversions=true or whatever, so as to avoid confusing users.)",1373162213,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-grvae3imieydt4li7k7h,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"**Author:** `gigs`
+
+**Description:**
+I see that a cancel button has been added, which is an improvement, but the escape key should also cancel edit mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373132460,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-biusmqvxgixprlg4xp34,task_description,resolved
+Escape key inside the main editor should cancel VE mode and return to action=view,"@Alex42 Thanks for reporting this. I filed a separate task about it: {T302096}. This task is from almost 9 years ago, and the cause of the new problem is almost certainly not related.",1645206828,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"This feature worked as expected until now. The last time i remember it working correctly is a few month ago.
+
+But now it is broken and **no dialog** ""Are you sure?"" is shown any more, when pressing Esc key once. Yesterday i lost a [[ https://de.wikipedia.org/w/index.php?title=Kreditkarte&curid=18081&diff=220309975&oldid=217344355 | hour of work ]].
+
+Tested in main view of VisualEditor on fr-, de- and en-wiki with Firefox 97.0 (64-Bit) on Win10.
+
+See also this disussion: [[ https://en.wikipedia.org/wiki/User_talk:Nick_Moyes#ESC_key_in_VisualEditor | en-wiki:User_talk:Nick_Moyes#ESC_key_in_VisualEditor ]]",1645197042,PHID-USER-iaar5nh25gcynskxgwrr,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"This feature worked as expected until now. The last time i remember it working correctly is a few month ago.
+
+But now it is broken and **no dialog** ""Are you sure?"" is shown any more, when pressing Esc key once. Yesterday i lost a [[ https://de.wikipedia.org/w/index.php?title=Kreditkarte&curid=18081&diff=220309975&oldid=217344355 | hour of work ]].
+
+Tested in main view of VisualEditor on fr-, de- and en-wiki with Firefox 97.0 (64-Bit) on Win10.",1645177521,PHID-USER-iaar5nh25gcynskxgwrr,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"It is a somewhat traumatic experience when you press Esc too hard in a dialog (or try to use Esc to cancel text selection etc) and VE shows a helpful ""would you like me to irrecoverably throw away the result of your last three hours of work? Y/N"" dialog. It's probably not easy to confirm by accident but it's still a pretty bad feeling. Has this been through any user testing at all?",1545717996,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"The discussion above makes sense and I think the <escape> key feature as currently implemented is probably helpful to some people.  But as a user who heavily uses <esc> to get out of ""insert ..."" dialogs and so on, it's alternately scary and annoying that a hitting (any) key too many times threatens to cancel my changes without saving.
+
+I'm not sure what improvements to suggest.  On second thought...  There doesn't seem to be a Cancel button, which makes it arch-surprising that a keyboard shortcut would do so.  What about changing the behavior of <esc> to ""Save Changes"" instead?  This seems consistent and friendly.",1481102923,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"The discussion above makes sense and I think the <escape> key feature as currently implemented is probably helpful to some people.  But as a user who heavily uses <esc> to get out of ""insert ..."" dialogs and so on, it's alternately scary and annoying that a hitting the key too many times will threaten to cancel my changes without saving.
+
+I'm not sure what improvements to suggest.  On second thought...  There doesn't seem to be a Cancel button, which makes it arch-surprising that a keyboard shortcut would do so.  What about changing the behavior of <esc> to ""Save Changes"" instead?  This seems consistent and friendly.",1481102889,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,Verified in betalabs.  Escape key will bring a warning message  box 'Are you sure?',1417633671,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,">>! In T52868#805066, @Jdforrester-WMF wrote:
+> Resolution is determined by QA for features and bugs.
+
+Huh?",1417575813,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,Resolution is determined by QA for features and bugs.,1417573056,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Change 175869 merged by jenkins-bot:
+Cancel VE when escape key pressed
+
+[[https://gerrit.wikimedia.org/r/175869]]",1417566802,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Change 175868 merged by jenkins-bot:
+Dialog: Only handle escape events when open
+
+[[https://gerrit.wikimedia.org/r/175868]]",1416953583,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Change 175869 had a related patch set uploaded (by Alex Monk):
+Cancel VE when escape key pressed
+
+[[https://gerrit.wikimedia.org/r/175869]]
+
+#patch-for-review",1416953386,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Change 175868 had a related patch set uploaded (by Alex Monk):
+Dialog: Only handle escape events when open
+
+[[https://gerrit.wikimedia.org/r/175868]]
+
+#patch-for-review",1416953163,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"(In reply to WhatamIdoing from comment #11)
+> I'm a bit worried about this.  What if I'm in a template dialog and
+> accidentally press Esc twice/too long?  If this triggered the ""Do you really
+> wnt to exit?"" confirmation, it might be okay.  However, I suspect that this
+> might not have the ultimate effect that was intended.
+
+Comment 10 asks for the unsaved changes warning to be shown. If we do that, I think it'll be fine. Pressing escape while a dialog is open will dismiss that dialog with a safe action (the cancel/never mind action). So if you press escape again when the unsaved changes warning is visible, that'll dismiss the warning with the safe action, which is ""never mind, I want to continue editing"". So if you press Esc a bunch of times or hold it too long, you'll end up in a loop of the unsaved changes warning appearing and being dismissed.",1407973255,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"I'm a bit worried about this.  What if I'm in a template dialog and accidentally press Esc twice/too long?  If this triggered the ""Do you really wnt to exit?"" confirmation, it might be okay.  However, I suspect that this might not have the ultimate effect that was intended.",1407972909,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Yes, pressing escape when in a dialog should close that level of the dialog (if more than one) or the dialog if it's at the top level of the dialog. If a change was confirmed then it should remain when closed, if a change was unconfirmed it should be cancelled. 
+
+With no dialogs open, escape should exit VE but should ask for confirmation before doing so if there are unsaved changes. That dialog should have keyboard actions such that enter confirms you want to leave and escape indicates that you don't want to leave and take you back to the VE. This will stop people losing work if they hit esc accidentally or too many times.",1374027650,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,Clarify title so it's clear we all agree.,1373394497,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"**gigs** wrote:
+
+Agreed, that's how I envisioned it.",1373382255,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"I'd like to note that really this should only happen iff someone is exclusively in edit mode. IOW, if someone has opened the template inspector, close that. Link inspector, close that - so on and so forth.",1373361187,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"On macs, cancel is usually cmd-.
+
+Wouldn't mind having that in VE.",1373228712,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"I think this isn't a bad idea, though I'm a little troubled if this causes unexpected behaviour for users of some browsers.",1373145156,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"**gigs** wrote:
+
+OK, but my next question is: What form fields are people going to be interacting with when in the main Visualeditor?  The only form field I see is the search box.",1373143309,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"Opera does that; it's useful enough that I expected other browsers to behave similarly. IE8 resets the value to the default (for both inputs and textareas). And Firefox apparently doesn't do anything, like you said.",1373139445,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,"**gigs** wrote:
+
+What browsers?  Not Chrome or Firefox.  I don't have IE here to test with, but I doubt it does it either.
+
+http://www.w3schools.com/jquery/tryit.asp?filename=tryjquery_event_blur_alert",1373136114,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+Escape key inside the main editor should cancel VE mode and return to action=view,The escape key is used by browsers to defocus (blur) currently focused form element. Reusing it for this would be really annoying.,1373132960,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-biusmqvxgixprlg4xp34,task_subcomment,NA
+VisualEditor: Transclusions editor should support parser functions and variables,"Parser function syntax is generally {{#function_name : expr1 | expr2 | expr3 | ...}}
+
+Currently VE sees this as a template with name ""#function_name : expr1"" and arguments ""1 = expr2"", ""2 = expr3"", etc. This makes it impossible to edit expr1 in VE.
+
+Same for parserfunctions like urlencode and template messages. The transclusions editor should be able to handle them, preferably by invisibly detecting them and failing that with a special, user-selected mode. Until we can, we should show an explanatory message when the user attempts to add one. 
+
+**See also:**
+{T54607}",1373104140,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-5tthiu6szwn225okbzla,task_description,open
+VisualEditor: Transclusions editor should support parser functions and variables,"So yeah. Matma Rex has merged T249860 with this task. Also, I will add details about this task on [[ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor | Wikipedia:VisualEditor ]].",1587917120,PHID-USER-wmk4bsljm5c77zhckwcj,False,PHID-TASK-5tthiu6szwn225okbzla,task_subcomment,NA
+VisualEditor: Transclusions editor should support parser functions and variables,"If Parsoid doesn't automatically tell VE whether something is a template or not, could it not be done by looking at the format of the string (e.g. {{# is never a template) or comparing it to a list of parser functions?",1435260148,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-5tthiu6szwn225okbzla,task_subcomment,NA
+VisualEditor: Transclusions editor should support parser functions and variables,"Many of the parser functions are rarely used in the main namespace (#if, ...), but some of them are really important even in the main namespace. For example {{formatnum:...}} is probably used a lot there.",1373465761,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-5tthiu6szwn225okbzla,task_subcomment,NA
+VisualEditor: Transclusions editor should support parser functions and variables,"Yes, we need a special form of editing transclusions which aren't templates; I can't recall whether Parsoid gives us sufficient information to recognise these as different except for introspection.",1373160763,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5tthiu6szwn225okbzla,task_subcomment,NA
+VisualEditor: Provide integration as an API service,"Original Bug title: 
+Provide an API to activate VE on arbitrary textareas for Gadgets and user scripts and document it at [[:mw:VisualEditor/API]]
+
+Please also create a mailing-list for those API updates.
+
+Issue:
+Since users will not be able to understand Wiki-Markup, please provide and API for turning-on VisualEditor on <textarea>s. Example use case would be the Translate Extension where translators still have to enter wiki-markup or LiquidThreads or whatever is adding Wiki-Markup to a page.
+
+Providing an API to Gadget authors and other tools is an important matter; nearly all edits are made through gadgets at certain pages; thus it is not just an ""enhancement"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373053800,PHID-USER-fgjrqsoj4hk6ezzjdea4,False,PHID-TASK-x25765urrimfm7ul6ci4,task_description,open
+VisualEditor: Provide integration as an API service,"This is a quite considerable piece of work; marking as ""low"" absent a huge push for this.",1373058098,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-x25765urrimfm7ul6ci4,task_subcomment,NA
+VisualEditor: Transclusion display garbled after removing parameter (CSS caching issue),"narrow display
+
+Seen in Chrome at least
+
+* click Transclusion
+* add a Template; add-parameter display is fine
+* add a parameter to the template
+* click Remove parameter
+
+resulting display is too narrow and does not display fully
+
+* add a new parameter in the garbled display
+
+display of parameter value show echoed/ghost characters as user types into parameter input
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11254}",1373044920,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-7fduwzpt3wlf2h5imzyr,task_description,resolved
+VisualEditor: Transclusion display garbled after removing parameter (CSS caching issue),confirmed,1373062937,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-7fduwzpt3wlf2h5imzyr,task_subcomment,NA
+VisualEditor: Transclusion display garbled after removing parameter (CSS caching issue),"I believe that this was due to a CSS caching issue (which we will more generally fix with bug 49420), and should now be gone - can you confirm?",1373062869,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7fduwzpt3wlf2h5imzyr,task_subcomment,NA
+VisualEditor: Transclusion display garbled after removing parameter (CSS caching issue),"Created attachment 12763
+ghost characters while typing
+
+**Attached**: {F11255}",1373044974,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-7fduwzpt3wlf2h5imzyr,task_subcomment,NA
+"VisualEditor: Add class name to protected pages, to allow for specific CSS styling of edit area","The wikitext editor <textarea> element has a CSS class ""mw-textarea-protected"" when a protected page is being edited. This can be used to provide custom styling for this textarea, mainly in order to alert sysops that they are editing a fully protected page.
+
+A similar CSS class name should somehow be provided for VE.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372998120,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-u5vpeaoeulxl7k3l2bmg,task_description,resolved
+"VisualEditor: Add class name to protected pages, to allow for specific CSS styling of edit area","Change 130665 merged by jenkins-bot:
+Add class name to protected pages, to allow for specific CSS styling of edit area
+
+https://gerrit.wikimedia.org/r/130665",1398891701,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u5vpeaoeulxl7k3l2bmg,task_subcomment,NA
+"VisualEditor: Add class name to protected pages, to allow for specific CSS styling of edit area","Change 130665 had a related patch set uploaded by Alex Monk:
+Add class name to protected pages, to allow for specific CSS styling of edit area
+
+https://gerrit.wikimedia.org/r/130665",1398887540,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u5vpeaoeulxl7k3l2bmg,task_subcomment,NA
+"VisualEditor: Show a different cursor when Ctrl (Cmd on Mac) is held down, as the interaction will be different","If you Ctrl+Click a link in the VE, it'll open (discovered through trial and error). Presumably the cursor when hovering over links while Ctrl is depressed should be the hand icon, rather than the typing icon.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372938780,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-wvxangmpnag4krm3mcnl,task_description,resolved
+"VisualEditor: Show a different cursor when Ctrl (Cmd on Mac) is held down, as the interaction will be different",Browsers do this automatically now (tested Chrome + FF).,1701797038,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-wvxangmpnag4krm3mcnl,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Screenshot
+
+See screenshot; not sure this is how it's meant to look, but it's how it looks. If there are no unused parameters it seems like the box notifying you of such should overwrite, rather than sit under, the search box - that's unnecessary functionality if all available parameters exist.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54094
+
+**Attached**: {F11039}",1372936920,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_description,resolved
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?",This interface has been replaced as a part of <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/VisualEditor_template_dialog_improvements>.,1724097630,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","This is still an issue, although now the message reads ""No unused fields"".
+{F34066618}",1611947721,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Just noting that bug 54094 (which was marked as a duplicate) is about the ""Unknown parameter"" message which appears (briefly) after the user has typed in '1'/'2' but not pressed enter yet.
+
+(In reply to comment #5)
+> Yes, ""No more known parameters"" would work. 
+> 
+> Not essential, but if it's not too much work, including a link to an
+> explanation (that there may be unknown parameters and that these can be used)
+> and/or the template documentation (if there isn't one provided elsewhere on
+> that view) would be good. Obviously both should open in a new window/tab.
+
+That is essentially bug 49772.",1382338192,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?",*** Bug 54094 has been marked as a duplicate of this bug. ***,1381342230,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Yes, ""No more known parameters"" would work. 
+
+Not essential, but if it's not too much work, including a link to an explanation (that there may be unknown parameters and that these can be used) and/or the template documentation (if there isn't one provided elsewhere on that view) would be good. Obviously both should open in a new window/tab.",1377907592,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Urk. Tis true. In particular, I'm thinking of scenarios where you have an infinite number of parameters (templates that merely order and format a set of inputted data, for example). ""No more known parameters"" would work.",1377906608,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","(In reply to comment #2)
+> Possibly? Offering people the ability to do something when the system knows
+> it won't end in what they want probably isn't the direction we want to be
+> going in, however.
+
+But the system doesn't 'know' that. TemplateData is hinting, not a binding-contract-of-doom. It's (intentionally) possible to add parameters that aren't in the hinting, because the hinting is out-of-date or doesn't cover this ""secret"" parameter, or because the name of your parameter is generated (e.g. {{CURRENTDAY}}=Easter Egg! or something more useful). Remember that there's almost no end to the level of flexibility that WT allows users…",1377905124,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Possibly? Offering people the ability to do something when the system knows it won't end in what they want probably isn't the direction we want to be going in, however.",1377904852,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+"VisualEditor: Transclusion dialog informing you that there are ""no unused fields"" looks odd; improve message?","Possibly we could say ""No known parameters"" and ""No more known parameters"" to make it clearer?",1377904599,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-d6zgk46zgybexfzzc4pr,task_subcomment,NA
+VisualEditor: Drop mw:ExtLink/URL,"Since Parsoid has dropped it in bug 46027
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372936500,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6lutt2i5yzl6odq5e46s,task_description,resolved
+VisualEditor: Drop mw:ExtLink/URL,"Change 71974 merged by jenkins-bot:
+Drop mw:ExtLink/URL support
+
+https://gerrit.wikimedia.org/r/71974",1373310810,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6lutt2i5yzl6odq5e46s,task_subcomment,NA
+VisualEditor: Drop mw:ExtLink/URL,"Change 71974 had a related patch set uploaded by Esanders:
+Drop mw:ExtLink/URL support
+
+https://gerrit.wikimedia.org/r/71974",1372936758,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-6lutt2i5yzl6odq5e46s,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**Author:** `lunarjam.mcgahan`
+
+**Description:**
+MS Word document describing and illustrating the bug
+
+See attached document. O/S is iOS 6.1.3
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**OS**: other
+
+**Attached**: {F11914}",1372904400,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_description,resolved
+VisualEditor: Location map template does not display correctly,"I checked the links that were given as examples to illustrate the problem - it does not seem that the issue is present anymore in wmf.2. 
+
+Also, I checked how the specific example (given in the ticket description) renders in iPad  - both in Chrome emulator and on real device - the issue is not present anymore. 
+(btw, there is a typo in the template code - should be `E` not `N` - I pasted the sample without correcting it to document the issue in its original form) 
+```
+{{Location map|South Australia|label=Macumba Station
+  |position=left
+  |lat_deg=27.25082|lat_dir=S
+  |lon_deg=135.6533|lon_dir=N
+  |caption=Location in South Australia}}
+```
+I am closing the ticket - if there are still some problems it'd be a good idea to create a new specific task.  ",1525739028,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,">>! In T52714#589573, @TheDJ wrote:
+> the technology of absolute positioning that is use by these templates and replace them with something more sustainable.
+
+Split to T120809",1449570666,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Link to a few other templates that run into trouble due to this problem.
+
+https://en.wikipedia.org/wiki/Template:Chess_diagram
+https://en.wikipedia.org/wiki/Template:Quote_box (with curly quotes option on)",1385032387,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Yes, exactly, the elements themselves. The HTML DOM elements. Not the pretty picture that translates into, nor the ugly wikicode language that generates them.",1384946588,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**Wikifram** wrote:
+
+(In reply to comment #14)
+> And i'm slightly offended by your attack on me as a person. A volunteer who
+> probably spends more time on en.wp than doing development.
+
+I haven't attacked you as a person, for all I know you may be a wonderful person. I have attacked your comment as a developer here, and what I see as the mindset of many developers here when working as a developer. 
+
+(In reply to comment #14)
+> > are so wrong that I feel it may be hard to explain to you what is the problem with it.
+> 
+> I think you assumed that I meant the elements/templates themselves. You
+> assumed
+> incorrect.
+
+I didn't ""assume"" anything, I read what you wrote: ""Ideally, we would
+just get rid of absolute positioned elements"". Usually, when people write ""get rid of elements"", they mean ""the elements themselves"", not ""keep the elements but get rid of the technology used"". Don't blame your errors on others please. I have no problem with someone correcting his position or retracting earlier statements, and I'm not the type to claim for all eternity that you want to get rid of these elements if you clarify that that was not what you intended; but then just state that what you said was not what you meant, not that the problem lies with the reader who ""assumed"" something incorrectly.",1384945064,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"> are so wrong that I feel it may be hard to explain to you what is the problem with it.
+
+I think you assumed that I meant the elements/templates themselves. You assumed incorrect. I meant the technology of absolute positioning that is use by these templates and replace them with something more sustainable. They currently also break in mobile and are very sensitive to skin changes for instance. The technique used to place them is problematic (and has been known to be problematic for many years, it's part of why I consolidated those hacks into https://en.wikipedia.org/wiki/Template%3ATop_icon, so that we could replace them at some point). The same technique has also been used for several spam attacks on the wiki.
+
+And i'm slightly offended by your attack on me as a person. A volunteer who probably spends more time on en.wp than doing development.",1384941212,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**Wikifram** wrote:
+
+The DJ, thanks for your response, but I fear that it is again symptomatic of the incorrect view you and other devs seem to have. VisualEditor is ''not'' the goal, it is a means to make editing easier. Comments like ""Ideally, we would just get rid of absolute positioned elements (.topicon, coordinates, FA/GA etc icons), but that's probably going to be near impossible."" are so wrong that I feel it may be hard to explain to you what is the problem with it. There is absolutely ''nothing'' ideal about getting rid of these elements, they are a very useful aspect of maps and other position-defined elements. If VE can't handle these, then VE has to change or an alternative method that can be used in view mode and VE mode needs to be found. But ""VE can't handle this, so we should get rid of these elements""? No, that's the opposite mindset of what we actually need. 
+
+As for ""nor is it extremely visible to the uninitiated."", have you looked at pages like [[:en:FC Barcelona]] or [[:en:ant]]? I think most of the ""uninitiated"" would notice some differences in the display between [[:fr:Azincourt]] and [https://fr.wikipedia.org/wiki/Azincourt?veaction=edit this] (cause this bug happens on all wikis, not just here...) 
+
+This bug happens on about 1 in 5 pages. I don't see how this can be both ""low"" and ""minor"" in importance, either one should be a lot higher (a minor aspect that affects an awful lot of pages on all wiki versions is a lot more important than a minor aspect that only affects a few hundred pages, obviously). On a fair number of pages (e.g. the football kit ones, 25000 on enwiki alone, but also e.g. [https://fi.wikipedia.org/wiki/Paris_Saint-Germain?veaction=edit here]), this bug (assuming it is the same one) is very pronounced, so not so minor anyway.",1384938669,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"By investigating the railway template problem, I think I identified 3 Parsoid bugs that were contributing to those problems on those pages. Most important is bug 57258. The others were bug 57251 and bug 57252.
+
+These are very distinct issues from the location map issue.",1384880301,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"For Location map, this is caused solely by:
+
+.ve-ce-protectedNode, .ve-ce-protectedNode * {
+position: relative !important;
+top: 0 !important;
+left: 0 !important;
+bottom: 0 !important;
+right: 0 !important;
+}
+
+Disabling it returns both the markers and the coordinates back to their original position. However, that also makes all content outside of the main box (you can click title coordinates that are generated by an info box).
+
+Conclusion, this was probably done to counter the effects of absolute positioned elements and causes 'fallout' for relative positioned elements. One way to fix this is with a bit of JS.
+
+var elements = $("".ve-ce-protectedNode"").filter(function() {
+      if( $(this).css(""position"") === ""absolute"" ) {
+            $(this).addClass(""evilabsoluteitems"");
+      }
+});
+
+And then assign the above css only to those elements. This is probably a rather 'expensive' operation. Ideally, we would just get rid of absolute positioned elements (.topicon, coordinates, FA/GA etc icons), but that's probably going to be near impossible. A third option might be to add a classname to all these elements that VE can recognize and then apply this styling to it.
+
+The question of the railway template seems more complex. I have a suspicion that there is actually a coding error in those templates, since I see problems with columns/rows counts on those pages. That would also explain why they take long to render in parsoid, it likely makes it complex to render the pages.",1384872097,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Probably a separate problem, which may already be filed in buzila, but here are a few railway templates that have extreme layout issues.
+https://en.wikipedia.org/w/index.php?title=Ontario_Northland_Railway&veaction=edit
+https://en.wikipedia.org/w/index.php?title=Brunswick%E2%80%93Magdeburg_railway&veaction=edit
+https://en.wikipedia.org/w/index.php?title=East_Lancashire_Railway&veaction=edit
+https://en.wikipedia.org/w/index.php?title=Channel_Tunnel&veaction=edit
+https://en.wikipedia.org/w/index.php?title=Ravenglass_and_Eskdale_Railway&veaction=edit",1380613476,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+Map of Loyalsock State Forest in VE on Chrome 22 Win7
+
+**Attached**: {F11916}",1374667210,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+VE display of a railway line in Chrome 22 on Win7
+
+**Attached**: {F11915}",1374667025,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+Also does nasty things to railway line diagrams - see [[South Maitland Railway]].",1374666736,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+For an example of a similar but not identical problem see the map in [[Loyalsock State Forest]]",1374665426,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Another fairly large set of 'CE-munging-absolutely-positioned-CSS bug'.  Is there an open bug for that?
+
+https://en.wikipedia.org/wiki/Template:Football_kit",1374665092,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"It also appears in other cases, such as this circle which should be over right-most persons face.
+https://de.wikipedia.org/wiki/Selbstbildnis_%28Leonardo_da_Vinci%29?veaction=edit",1374662867,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"Problem confirmed on Firefox and Chrome, and can be seen at
+
+https://en.wikipedia.org/wiki/Macumba_Station?veaction=edit
+
+And most other pages (lots and lots) that use
+
+https://en.wikipedia.org/wiki/Template:Location_map
+
+also confirmed for uses of the German template, so I am guessing most other wikis will have the same problem
+
+https://de.wikipedia.org/wiki/Vorlage:Positionskarte
+
+https://en.wikipedia.org/wiki/Azincourt?veaction=edit
+https://de.wikipedia.org/wiki/Albany_%28New_York%29?veaction=edit
+
+I cant find another bug that mentions location maps.",1374538983,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,"**lunarjam.mcgahan** wrote:
+
+This bug also occurs in Chrome Version 27.0.1453.116 m on Windows 7.",1372992263,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+VisualEditor: Location map template does not display correctly,This looks like a CE-munging-absolutely-positioned-CSS bug.,1372904578,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-uejijc4imv5i4n5hfjzf,task_subcomment,NA
+Compatiblity between the two editors,"Very often I find that there are some tools that both these editors (VE and the old editor) that I would want to use on the same article. But there is no way to do so.
+
+It would be a very useful feature of the VE if there was some way (direct, or indirect; like through the show preview button) for editors opening an article in VE to be able to edit the same article in the old editor without having to save it or discard the changes made.
+
+Such a feature could also come in handy for other editors who have started editing through VE but couldn't understand the interface/needed to switch because they realised VE could not do an action they wanted
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372890000,PHID-USER-65pjzcmoby2fsgzdrfjq,False,PHID-TASK-xucom3pjxavt6vbh6mcr,task_description,resolved
+Compatiblity between the two editors,"This is the same as bug 47779
+
+*** This bug has been marked as a duplicate of bug 47779 ***",1373855340,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+Compatiblity between the two editors,"Oops - just realized there was an external link in his comments.
+
+The picture he mentions in his last sentence can be found here:
+http://en.support.files.wordpress.com/2009/07/visual_editor2.png?w=688",1373301423,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+Compatiblity between the two editors,"Another editor adds:
+If you want to switch (say you started in Visual, but you want to switch to source to get something fancy working), you have to either discard your changes or save a partial edit in visual and create a second edit in source. What I want to see is a means of switching between the two at will within the same edit. Wordpress does something similar where you can type up a blog post to switch between visual rendering and HTML source using tabs surrounding the edit window. You can switch between visual and HTML at will and each will be updated. I want to see the same thing with the Wikipedia VisualEditor. -Thunderforge (talk) 21:32, 6 July 2013 (UTC)
+
+AND
+
+They don't necessarily have to both be visible at the same time (in fact, that might be somewhat confusing and perhaps wouldn't work well on mobile devices and tablets if the VisualEditor is going to be used there). But I would like some way to switch between the two without having to discard an edit. Again, the tabs on the edit window that Wordpress uses are one excellent way to do this: they allow the edit space to be swapped out, providing a compact way to easily switch. A picture of it can be found here. -Thunderforge (talk) 21:40, 6 July 2013 (UTC)",1373301385,PHID-USER-joqqkabmjmvxeucx4ni2,False,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+Compatiblity between the two editors,"Examples of articles where I need to use both? That would be any article where I'm trying to manipulate citations (move/add/append/improve) or with templates; as well as doing some general editing.
+
+
+Example of what I want? A button saying ""View this in the old editor"", and clicking on that gets you the same article, including any changes you made, in the old editor. Alternately, you could display the same button in the preview mode when you're viewing the article",1372935534,PHID-USER-65pjzcmoby2fsgzdrfjq,False,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+Compatiblity between the two editors,Can you provide some more specific examples?,1372931394,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-xucom3pjxavt6vbh6mcr,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"Copied:
+For logged in user, can there be a formatting preference to display [edit | edit source] as [edit source | edit]? --J. D. Redding 18:47, 3 July 2013 (UTC)
+
+The user finds it frustrating that he keeps inadvertently selecting ""edit""
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=56337",1372879860,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-kpw2y2iowrttt6zxpjia,task_description,invalid
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"(In reply to comment #5)
+> I don't think a user preference is appropriate here.
+> 
+> Given the resolution of bug 50540, I'm not sure there's anything actionable
+> here.
+
+Concurred; closing as INVALID.",1380214284,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"I don't think a user preference is appropriate here.
+
+Given the resolution of bug 50540, I'm not sure there's anything actionable here.",1380209341,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,A better solution would be the one suggested at bug 50540.,1373324983,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"I agree that we need to resolve this somehow, since the current hover interface has also been pointed out as a problem on touch devices (e.g. tablets).",1373324915,PHID-USER-766idcqt4jkngnnuhnrj,True,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"I think it is a fairly high priority. It would keep a lot of users (such as me) from turning off the visual editor altogether. Many people are turning off the VE due to this problem. More and more people are saying this here:
+[[Wikipedia:VisualEditor/Feedback]]
+
+I want instant direct access to the ""edit source"" link. I want the ""edit"" link to be the one that is hidden. 
+
+Better yet would be an option to display both links directly without any hover effects. When I want to click either link I do not want to waste one millisecond finding the link, or thinking I may screw up again, and hit the wrong link. 
+
+Think gaming, ping, lag time, and even slightly experienced Wikipedia editors wanting to get things done faster.",1372897059,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+VisualEditor: User preference for reversing the order of [edit | edit source] section links,"We can do this, but I don't think it's as high priority as a number if others. Marking as such.",1372886254,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kpw2y2iowrttt6zxpjia,task_subcomment,NA
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.","what it says on the tin; if you remove the first character from [[foo]] to change it to [[moo]], what you actually end up with is m[[oo]].
+
+See also:
+* T52745
+* T52945
+* T55495
+* T52452",1372872240,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-oqqiylk3iqavc5qnj32p,task_description,resolved
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.","This was fixed by the work on link cartouches (the blue highlights that appear when you place the cursor or select text inside a link) in T91285.
+{F32358209}",1600713579,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-oqqiylk3iqavc5qnj32p,task_subcomment,NA
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.","In the weekly triage meeting on 2015-05-06, we discussed this task. We acknowledge that this industry standard manner of operation for editors can lead to some poor outcomes, but as written this isn't actionable and we feel that the issue is not as high priority as the other user-facing work that we need to get done this quarter, so we rejected it as a piece of work for Q4.",1430945493,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oqqiylk3iqavc5qnj32p,task_subcomment,NA
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.","comment from Elitre on bug 53210:
+Seems I had written about it in an unrelated bug, sorry. This happens on itwp:
+in order to do this
+http://it.wikipedia.org/w/index.php?title=DNasi_attivata_da_caspasi&diff=60101664&oldid=60089990
+I had to delete the word and link it back again. Our guidelines about style
+require pages in that section to appear with the capital letter, so we need to
+be able to fix that easily.
+
+It is also reported on en.wp, the user states <<When trying to correct a
+lower-case letter to a capital letter at the beginning of a link, I deleted the
+lower-case letter and found I couldn't type a capital letter and have it become
+part of the link, nor could I seem to extend the link over the capital.
+Eventually, I typed the capital after the lower-case letter and then deleted
+the lower-case letter. It might be good to have some way to extend a link over
+adjoining letters/words/text. Mount Flatten (talk) 05:31, 22 August 2013 (UTC)
+>>
+Thanks.
+
+ps. Might be related to https://bugzilla.wikimedia.org/show_bug.cgi?id=50745",1377445735,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-oqqiylk3iqavc5qnj32p,task_subcomment,NA
+"VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.",*** Bug 53210 has been marked as a duplicate of this bug. ***,1377445650,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-oqqiylk3iqavc5qnj32p,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","ve.init.mw.Platform.js currently hard-codes searching from Commons, even if the wiki doesn't actually load images from Commons. We should do this based on wiki config instead.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372865220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_description,resolved
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","Change 102377 merged by jenkins-bot:
+Use image sources from the fileRepo API
+
+https://gerrit.wikimedia.org/r/102377",1388900839,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","Change 102377 had a related patch set uploaded by Mooeypoo:
+Use image sources from API's fileRepo
+
+https://gerrit.wikimedia.org/r/102377",1387334234,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","This can now be done by using the new meta=filerepoinfo API query, which was introduced into core in gerrit 85344.",1380757856,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","**humpface** wrote:
+
+This was very frustrating for my work's internal wiki.  First, I didn't want any Instant Common images (and thanks to James, I was able to remove the line of code).  However, since I disabled the use of Instant Commons ($wgUseInstantCommons = false;), I was still able to search through the Instant Commons but after saving, everything showed up as a broken link.
+
+Suggestion:
+- Tie the JSON mediaSources object in ve.init.ms.Platform.js to the $wgUseInstantCommons (i.e., if Commons is turned off in LocalSettings.php, then a user can't search through the images).",1380067695,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","(In reply to comment #1)
+> Ideally we'd avoid hardcoding Commons entirely and instead of exporting
+> isInstantCommons, we'd export fileRepos.
+
+Indeed; that was what I was thinking when I wrote this bug. Title modified to be clearer.",1374157001,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+"VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons","Ideally we'd avoid hardcoding Commons entirely and instead of exporting isInstantCommons, we'd export fileRepos. That should be almost as easy to do and would fix other things as well:
+
+* Wikis where their repo is Commons but through their own wgForeignFileRepos setting (e.g. like on WMF where we use more fine-tuned configuration that does essentially the same, or wikis that configure it but don't use wgUseInstantCommons because they want to set different parameters (e.g. disable repo[fetchDescription] or use a non-default repo[cacheExpiry]).
+
+* Wikis with more than 2 repositories.
+
+* Wikis working with other repos (e.g. a wiki farm might have their own commons-like thing).
+
+Especially reason #1 since we do use InstantCommons in production but not the default settings through the UseInstantCommons toggle. We could hardcode some detection and export ""isUsingCommonsAsARepoSomehow"", but might as well take a few more minutes and figure out how to just export an array of api urls.
+
+
+[] https://www.mediawiki.org/wiki/Manual:$wgUseInstantCommons#Details",1374150733,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-n6pkynrqsgqpbnp7oitd,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"Not sure the technical term, but: if I hover over, for example, the bugzilla ""search bugs"" link, it shows as a URL in the bottom left of firefox, allowing me to identify the destination. The same is true in articles in read mode. It'd be good to have this functionality in the VisualEditor, or some other way of more prominently identifying where links are going to: hovering over every. single. one. doesn't really work.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372840860,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_description,declined
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,Re-marking as WORKSFORME.,1415226643,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"As for the issue of browsers not displaying the link target in the status bar when you hover them: that's a browser problem. Neither Firefox nor Chrome appears to do this for links in a contentEditable.
+
+However, since the filing of this bug we do have a better way than tooltips links to show their targets: when you put your cursor in a link, the context menu now shows the target of the link rather than just a link icon.
+
+So, WONTFIX?",1415226397,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"Removing See Also and unassigning; I thought this was about link suggestions in the dropdown in the link inspector, but it doesn't appear to be.",1415226144,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"(In reply to comment #1)
+> Links are now displaying page URL.Checked in FireFox 20
+
+They are not in Firefox 25.0 on Fedora 19 in VE edit mode for me on https://en.wikipedia.org/w/index.php?title=Wikimedia_Foundation&veaction=edit",1384254853,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that,"Links are now displaying page URL.Checked in FireFox 20 and Chrome Version 26.0.1410.65 using MAC OS X 10.8.5.
+Therefore changing the status to resolved-worksforme for now.
+If you experience this problem again,please reopen the bug.",1384220252,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-vqlk4nl6b5bryutwjnk3,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"I imagine this is mostly due to Firefox's JS engine, but I commonly run across articles that take an extremely long time to load the new VisualEditor interface. For example, ""Domestic violence"" and ""Feminism"" take about 30 seconds. Really long articles like ""World War II"" take over a minute. The interface loads in about half that time in Safari. I'm using Firefox 21.
+
+Comparative loading figures:
+
+| Article | FF 32, 2014-09 | Cr 37, 2014-09
+|--|--|--|--|--
+| Barack Obama | 17.6s | 17.2s
+|--
+| Cat | 16.4s | 16.0s
+|--
+| Beyoncé Knowles | 25.4s | 7.5s
+|--
+| India | 26.8s | 5.6s
+|--
+| Richard Nixon | 9.9s | 5.6s
+|--
+| Europe | 28.3s | 7.1s
+|--
+| English language | 18.2 | 8.0s
+|--
+
+
+| Article | FF 34.05 2014-12 |Cr 39 2014-12
+|--|--|--|--|--
+| Barack Obama | 13.23s | 10.61s
+|--
+| Cat | 11.59s |5.82s
+|--
+| Beyoncé Knowles | 8.01s|5.13s
+|--
+| India | 8.90s |5.64s
+|--
+| Richard Nixon | 8.85s|6.36s
+|--
+| Europe | 10.31s|6.52s
+|--
+| English language |6.98s|5.45s
+|--
+",1372802220,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_description,resolved
+Improve VisualEditor's loading performance in Firefox,"Yeah; let's claim this as Resolved, in as much as it can be.",1595844165,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! From the **task description**:
+> | Article | FF 32, 2014-09 | Cr 37, 2014-09
+> |--|--|--|--|--
+> | Barack Obama | 17.6s | 17.2s
+> |--
+> | Cat | 16.4s | 16.0s
+> |--
+> | Beyoncé Knowles | 25.4s | 7.5s
+> |--
+> | India | 26.8s | 5.6s
+> |--
+> | Richard Nixon | 9.9s | 5.6s
+> |--
+> | Europe | 28.3s | 7.1s
+> |--
+> | English language | 18.2 | 8.0s
+> |--
+> 
+> 
+> | Article | FF 34.05 2014-12 |Cr 39 2014-12
+> |--|--|--|--|--
+> | Barack Obama | 13.23s | 10.61s
+> |--
+> | Cat | 11.59s |5.82s
+> |--
+> | Beyoncé Knowles | 8.01s|5.13s
+> |--
+> | India | 8.90s |5.64s
+> |--
+> | Richard Nixon | 8.85s|6.36s
+> |--
+> | Europe | 10.31s|6.52s
+> |--
+> | English language |6.98s|5.45s
+> |--
+> 
+
+Six years later – some updated numbers. I couldn't find any  record of how the above was measured. I'm measuring the below based on the `timing.ve.mwTarget.performance.system.activation` metric. Method: open article while logged-in, click Edit, wait for loading to complete, and only then open the console and run `mw.trackSubscribe('timing', console.log)`. I then close the console, close the editor, hard refresh, and measure it once more. Numbers were trimmed to 1 decimal without rounding.
+
+Setup: MacBook Pro with macOS 10.15 Catalina. Using unthrottled latest stable Firefox, Chrome, and Safari.
+
+| Article | FF 78 2020-07 | Cr 83 2020-07 | Saf 13 2020-07
+|--|--|--|--|--
+| Barack Obama | 8.0s, 7.9s | 4.9s, 4.6s | 9.4s, 8.9s
+|--
+| Cat | 4.2s, 4.1s | 2.8s, 2.4s | 3.8s, 3.7s
+|--
+| Beyoncé Knowles|5.6s, 5.2s| 4.2s, 4.0s | 5.7s, 5.2s
+|--
+| India | 6.2s, 6.1s| 4.3s, 4.1s | 8.0s, 7.7s
+|--
+| Richard Nixon | 4.2s, 4.2s | 3.5s, 3.2s | 4.9s, 4.5s
+|--
+| Europe|6.0s, 5.9s | 5.6s, 4.7s| 5.8s,  5.0s
+|--
+| English language | 4.9s, 4.6s | 3.8s, 3.6s | 4.3s, 4.3s
+|--
+
+The load times have shrunk a lot across the board. It's also interesting to see that while Safari generally feels faster than either Chrome or Firefox when browsing day-to-day, with the specific payload of initialising VisualEditor it's more or less on part with Firefox, with Chrome still being notably faster.
+
+Having said that, I would say overall that the differences are now small enough to not need a ticket specifically about Firefox. And that generally speaking we are still consistently taking more than one second to load popular articles which would be great to bring down, but that's outside the scope of this task and it's certainly much much better than it was six years ago.",1595631881,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! In T52616#3769993, @Elitre wrote:
+> T171093 ?
+
+That's for a performance review, which isn't technically the same as making performance improvements. I don't particularly object to merging this into that, but I don't think it's quite right.",1510937642,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! In T52616#3769774, @Deskana wrote:
+> I actually don't see a more general task for improving performance of the visual editor anywhere, so I guess I'll just leave this as it is for now.
+
+T171093 ?",1510933858,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! In T52616#3769774, @Deskana wrote:
+> I actually don't see a more general task for improving performance of the visual editor anywhere, so I guess I'll just leave this as it is for now.
+
+Good idea actually: I was telling myself that there is plenty of computers which will not receive the update son (or will never receive an update), and we still have to improve performances for them.",1510930415,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"I actually don't see a more general task for improving performance of the visual editor anywhere, so I guess I'll just leave this as it is for now.",1510930305,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,">>! In T52616#3769691, @Trizek-WMF wrote:
+> Firefox 57 really improves that issue (I can notice it even with my good computer which had a fast enough Firefox). Maybe reconsider that task?
+
+Yeah, I doubt we'll work specifically on improving Firefox 57 performance directly, and instead choose to work on performance more generally. I can merge this into a more general task. In the unlikely event we do decide to work directly on Firefox 57 in the future, this can be reopened.",1510930006,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,Firefox 57 really improves that issue (I can notice it even with my good computer which had a fast enough Firefox). Maybe reconsider that task?,1510929558,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"This is really a tracker bug more than a specific call-to-action, so we decided in the meeting to remove it from the Q3 blockers list at the triage on 2015-02-11.",1423878817,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"Those are pretty major performance improvements, much more than I was expecting. Odd.",1418255283,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"Added the new data, one thing to note is if you check chrome before firefox, or check only firefox, the results are almost the same for firefox. but if you check chrome after firefox, it is faster, i guess due to caching. So, more food for thought.",1418243212,PHID-USER-u7udgblfyop6qd5wxot6,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"Could you compare loading times for these articles now, three months later?",1418241832,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"(In reply to matanya from comment #1)
+> I'm using firefox 32 and did some tests on this on en,wikipedia, and beta
+> en, which runs HHVM, but is on a virt cluster.
+
+Comparing the time to execute of anything between beta and prod is comparing nothing of value. Different hardware, different cluster sizes (for cache, execute and db) and different code.",1410306789,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"Adding timings in chromium 37 for comparison:
+
+
+Article name:Barack Obama
+beta en: 8.1s
+en : 17.2s
+
+Article name: Cat
+beta en: 7.7s
+en: 16.0s
+
+Article name:Beyoncé Knowles
+beta en: 5.1s
+en: 7.5s
+
+Article name: India
+beta en: 4.8s
+en : 5.6s
+
+Article name: Richard Nixon
+beta en:3.6s
+en: 5.6s
+
+Article name:Europe
+beta en: 5.7s
+en: 7.1s
+
+Article name: English language
+beta en:3.5s
+en: 8.0s",1410306686,PHID-USER-u7udgblfyop6qd5wxot6,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,adding Ori for possible HHVM implications,1410305231,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+Improve VisualEditor's loading performance in Firefox,"I'm using firefox 32 and did some tests on this on en,wikipedia, and beta en, which runs HHVM, but is on a virt cluster.
+
+Article name:Barack Obama
+beta en: 41.7s
+en : 17.6s
+
+Article name: Cat
+beta en: 31.7s
+en: 16.4s
+
+Article name:Beyoncé Knowles
+beta en: 16.9s
+en: 25.4s
+
+Article name: India
+beta en: 36.4s
+en : 26.8s
+
+Article name: Richard Nixon
+beta en:16.2s
+en: 9.9s
+
+Article name:Europe
+beta en: 26.8s
+en: 28.3s
+
+Article name: English language
+beta en:23.7s
+en: 18.2
+
+I think although it is a small test it does show the trend. 
+
+The computer running this test is an i7 quad core from the 3rd gen with 8G of ram, so shouldn't be any issue on this front. 
+
+Would be glad to provide any other info needed.",1410305084,PHID-USER-u7udgblfyop6qd5wxot6,False,PHID-TASK-ysfxvsvtwjpipqsulyul,task_subcomment,NA
+VisualEditor: Reduce whitespace in transclusion dialog,"A contributor requests the following:
+
+I'm sure this is far down the list of problems, but I think the transclusion editor (and other bits with similar display) have way too much white space. For each parameter one gets two blank lines for every one line with parameter name. That is annoying and when templates have dozens of parameters, as many infoboxes and citation templates do, it creates a lot of extra scrolling to find what one is looking for. I'd suggest reducing the whitespace between parameter names by half. Dragons flight (talk) 18:18, 2 July 2013 (UTC)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372791060,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-rhordq7y2ulyxaighkvm,task_description,resolved
+VisualEditor: Reduce whitespace in transclusion dialog,We did this as part of the transclusion dialog tweaks in August; sorry for the slowness to update.,1385375733,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rhordq7y2ulyxaighkvm,task_subcomment,NA
+VisualEditor: Link inspector should preview the linked page (à la Navigation Popups),"Disambiguations and other oddities can mean that the first link you select in a typeahead search may not actually be right. You then have to follow the link (which is hard in edit mode) and go looking again.
+
+Being able to get a short preview of the selected link target, similar to what Navigation Popups gadget does when hovering over links, would go miles (kilometers) towards making link selection *awesomer*.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=59208",1372786320,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-wzei4tpax7kpf3oq25mp,task_description,resolved
+VisualEditor: Link inspector should preview the linked page (à la Navigation Popups),This is effectively now solved with the link image/data preview,1431047236,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wzei4tpax7kpf3oq25mp,task_subcomment,NA
+VisualEditor: Link inspector should preview the linked page (à la Navigation Popups),"It probably shouldn't be the highest priority, but as an editor, I would like something like this. In fact, I'd find it far more useful than Hovercards: When I'm reading an article and want to know more about a topic to which there is a link, I usually middle-click it to open it in a new tab and read it a bit later, so I don't really need Hovercards. As I am editing, however, it would be useful for me to add a link and  be more sure as to where is the link leading. Is [[Washing Machine]] leading to the article about the appliance or about the Sonic Youth album? Is [[AC/DC]] leading to an article about electrical engineering or about a band? These are real situation in which I found myself recently, and in both of them I had to open a new tab to make sure.
+
+So I would love to see something more than just the title when I'm linking. It doesn't even have to be a full-blown Hovercard - just the first few words are likely to be enough. (Although reusing the Hovercards code makes sense, too.)",1401698735,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-wzei4tpax7kpf3oq25mp,task_subcomment,NA
+VisualEditor: Link inspector should preview the linked page (à la Navigation Popups),"I'm not sure this is needed once bug 50240 is fixed, but we should re-consider it then. Also, some form of interaction that doesn't need hover would be needed for touch-screen devices, like mobile.",1377023920,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wzei4tpax7kpf3oq25mp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"The template inspector's parameters contain the contents of each parameter, and also a line break, which represents, well, the break between two parameters. When modifying a param, it's all too easy to remove the line break, which results in user-unfriendly things like https://en.wikipedia.org/w/index.php?title=Kidz_Bop_20&diff=prev&oldid=562494239
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=69682",1372775700,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-drqb66ingqes5mea47vp,task_description,resolved
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"Agreed, looks fixed.  I can no longer reproduce the problem I had before on $wgEnableCanonicalServerLink (I tried to test with the same exact changes on my sandbox).",1421036273,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"…and in fact, this appears to have been fixed already? The leading and trailing newlines from wikitext source are not displayed in the fields in the template dialog, and can not be removed. However, newly inserted template parameters (and newly inserted templates) do not have ""smart whitespace"" added (this overlaps with T71682 a bit).",1420986164,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"The whitespace around the value of parameters should just be preserved (and not shown in the text field at all). This can't be difficult to do, can it?",1420984596,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,"The bug is open for more than a year, and we get ugly diffs and ugly wikitext. Please increase its severity.
+
+If it isn't possible or it is hard to know whether a template is ""inline template"" or ""multiline template"", at least allow manual indication for it (using TemplateData?)",1408794928,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,(inspector->dialog; inspector is the context menu with buttons to open a dialog),1373539573,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters,Confirmed (https://www.mediawiki.org/w/index.php?title=Manual:$wgEnableCanonicalServerLink&diff=728104&oldid=667291).,1373408374,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-drqb66ingqes5mea47vp,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"If you create a new reference, you can specify a name - great! If you try to modify an existing reference to add a name... https://en.wikipedia.org/wiki/File:VEReferenceEdit.jpg oops.",1372760160,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_description,open
+VisualEditor: Be able to name references manually in the reference dialog,"Just noting that there's lots of libraries out there that do this kind of thing.  Google for ""slugify"".",1723306099,PHID-USER-vipegwlyd4ievw2wqspk,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 891513 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Cite@master] Make auto-generated reference names like name="":0"" visible in VE%%%
+https://gerrit.wikimedia.org/r/891513",1677179166,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 891513 had a related patch set uploaded (by Thiemo Kreuz (WMDE); author: Thiemo Kreuz (WMDE)):
+%%%[mediawiki/extensions/Cite@master] Make auto-generated reference names like name="":0"" visible in VE%%%
+https://gerrit.wikimedia.org/r/891513",1677151684,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 743057 **abandoned** by Chlod Alejandro:
+%%%[mediawiki/extensions/Cite@master] [WIP] Add field for changing reference name%%%
+Reason:
+%%%Abandoning this, since as of the way VisualEditor is written right now, it is immensely difficult to switch from counter-based reference names to name-based reference names, or perhaps I simply lack the required prior knowledge of how to make it possible in VisualEditor. Leaving this for someone else to do, hopefully some of the code here might still be useful.%%%
+https://gerrit.wikimedia.org/r/743057",1670504338,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 740171 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Verify key before removing node from InternalList%%%
+https://gerrit.wikimedia.org/r/740171",1666189710,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Test wiki on [[ https://patchdemo.wmflabs.org | Patch demo ]]  by Chlod using patch(es) linked to this task was **deleted**:
+
+~~[[ https://patchdemo.wmflabs.org/wikis/2274ae27f1/w/ ]]~~",1665052298,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by Chlod using patch(es) linked to this task:
+https://patchdemo.wmflabs.org/wikis/2274ae27f1/w",1665051508,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 740171 had a related patch set uploaded (by Samtar; author: Chlod Alejandro):
+%%%[VisualEditor/VisualEditor@master] Verify key before removing node from InternalList%%%
+https://gerrit.wikimedia.org/r/740171",1665051130,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Is there any progress on this? I note (now, having not seen it before) the proposal for an alternative at https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Status_report_1#Named_References_in_VE which really doesn't look very helpful: if several of the refs in an article are to sources found on google books, or to a collection of articles written over time in one newspaper, or to journals from a particular online publisher, the editor will still have to struggle among a large set of semi-meaningless references (which of the umpteen ncbi refs in https://en.wikipedia.org/wiki/Oxford%E2%80%93AstraZeneca_COVID-19_vaccine would be ncbi-12?)  It surely cannot be that difficult for an algorithm, faced with a reference in a citation template, to do something like: ""Is there a ""last"" or ""last1"" field? If so, use it as ref name, adding number if needed for disambiguation (or, better, adding year if present, then number if needed); if no ""last1"", then use first word (or 2 words, or 10 chars) of  ""title"" field, similarly. If all else fails, use the domain name as proposed.""",1656964617,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Change 743057 had a related patch set uploaded (by Chlod Alejandro; author: Chlod Alejandro):
+%%%[mediawiki/extensions/Cite@master] Add field for changing reference name%%%
+https://gerrit.wikimedia.org/r/743057",1638420663,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"This has been proposed as part of the 2019 Community Wishlist:   https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Citations/VisualEditor:_Allow_references_to_be_named  It's too early to know whether it will make the top 10 (voting will be open until the 30 November 2018), but it's currently among the more popular items, which suggests that solving this problem has widespread community support. ",1543192104,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"My first thought is that this wont remain opaque to VE forever and so what is required is a workaround that exposes to VE some aspects about the contents of templates like `{{columns-list}}` even if cannot be edited yet. 
+For example, the template could expose metadata like: 
+```
+References included:  'Smith' 'Jones' 'Patel'
+```
+where each of those is the `name=` parameter of a reference used inside it. 
+
+This would allow VE to display and error along the lines of ""Cannot rename reference ""Jones"" - used in uneditable block. It would also prevent the naming of a new reference with a conflicting name.
+
+It may also be useful for T52474 and similar tasks.
+
+How significant this would be to program I haven't the foggiest though.",1542746748,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"My first thought is that this wont remain opaque to VE forever and so what is required is a workaround that exposes to VE some aspects about the contents of templates like `{{columns-list}}` even if cannot be edited yet. 
+For example, the template could expose metadata like: 
+```
+References included:  'Smith' 'Jones' 'Patel'
+```
+where each of those is the `name=` parameter of a reference used inside it. 
+
+This would allow VE to display and error along the lines of ""Cannot rename reference ""Jones"" - used in uneditable block. It would also prevent the naming of a new reference with a conflicting name.
+
+How significant this would be to program I haven't the foggiest though.",1542746648,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,">>! In T52568#4743919, @Thryduulf wrote:
+> When this is implemented it needs to take account of reused references: 
+> i.e. if `<ref name=""Smith"">...</ref>` is renamed to `<ref name=""Jones"">...</ref>`
+> then all instances of `<ref name=""Smith"" />` need to be automatically changed to `<ref name=""Jones"" />`
+
+This is actually a very good point, and I think this actually makes changing the name impossible in some cases. (But it should be possible to allow setting the name for newly created references.)
+
+Consider a page like this:
+```
+Lorem ipsum dolor sit amet, consectetur adipisicing elit.<ref name=""example"">http://example.com/</ref>
+
+{{columns-list|
+* [[George Washington]]
+* [[John Adams]]<ref name=""example"" />
+}}
+
+<references />
+```
+
+If you were to use VE to change the `name` of this reference, we would not be able to update the reuse inside the `{{columns-list}}` template, because the entire template is ""opaque"" – VE doesn't know about anything inside of it, it just displays the content.",1542650803,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,">>! In T52568#4743919, @Thryduulf wrote:
+> When this is implemented it needs to take account of reused references: 
+> i.e. if `<ref name=""Smith"">...</ref>` is renamed to `<ref name=""Jones"">...</ref>`
+> then all instances of `<ref name=""Smith"" />` need to be automatically changed to `<ref name=""Jones"" />`
+
+This is actually a very good point, and I think this actually makes changing the name impossible in some cases. (But it should be possible to set the name for newly created references.)
+
+Consider a page like this:
+```
+Lorem ipsum dolor sit amet, consectetur adipisicing elit.<ref name=""example"">http://example.com/</ref>
+
+{{columns-list|
+* [[George Washington]]
+* [[John Adams]]<ref name=""example"" />
+}}
+
+<references />
+```
+
+If you were to use VE to change the `name` of this reference, we would not be able to update the reuse inside the `{{columns-list}}` template, because the entire template is ""opaque"" – VE doesn't know about anything inside of it, it just displays the content.",1542650702,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"When this is implemented it needs to take account of reused references: 
+i.e. if `<ref name=""Smith"">...</ref>` is renamed to `<ref name=""Jones"">...</ref>`
+then all instances of `<ref name=""Smith"" />` need to be automatically changed to `<ref name=""Jones"" />`
+
+Thought will need to be given to the interaction of this and section editing. ",1542139214,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"If we try to name a reference by only using a numeral, the system rejects it and says that numeral only reference names are not permitted.
+I feel it is bogus that Visual Editor gets around this by adding a colon: e.g. - :17
+That kind of reference name is wrong and unhelpful.
+I hope that the ability to manually name references, or at least the ability to manually approve the generated name is restored.",1511145285,PHID-USER-wwyujao3kjfasgvrx6nk,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"> If you create a new reference, you can specify a name - great! 
+
+It's no longer possible to specify a name even when creating a new reference.",1484857993,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"At the triage meeting on 11 March it was agreed that this is too complex and imprecise to keep as a Q3 objective, but that a much more on-point task, {T92432}, could be done instead.",1426548049,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Here's another idea for an automatically suggested (but still editable) ref name that would work with manually formatted citations:  
+
+Use the longest text string is in the citation, appending numbers as necessary to keep the names unique.  You might end up with a lot of refs named ""September"", but it in many cases it will pick up the most significant keyword in the source's title.",1425493648,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"The citoid extension could definitely come up with an automated reference name, but that should be filed as a separate issue as a feature request :). For editing citations, the extension uses the same reference dialog as the rest of VE. ",1424976215,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,Perhaps Citoid could suggest a ref name.,1424975287,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,*** Bug 57459 has been marked as a duplicate of this bug. ***,1414104088,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Useful for default would be to read from the parameters of the cite template if provided. The following would be a useful preference order I think 
+1. Lastname and Year (e.g. Smith2013)
+2. Author and year (e.g. Bob Smith2013)
+3. Lastname and serial number (e.g. Smith001)
+4. Title (first 3 words) and year (e.g. FreddieStarrAte1986)
+5. domain, underscore, page name (If only a bare url is given) (e.g. bbc_magazine-23969607)
+6. fist alphabetic string in reference (when neither a template or a url) and a string of four digits from the reference (e.g. Jones1999)
+7. fist alphabetic string in reference and a serial number (when neither a template or a url and no sequence of four digits is present) (e.g. Brown001)",1378935773,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"It would even be convenient if VisualEditor suggested a unique label for the ref, perhaps using the first alphabetic string of characters in the ref (usually the first author's last name).",1378918158,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Editor APerson at en.wp, is asking for this and suggests that the name of a reference could be set in the ""Options"" section along with the group name.",1375511477,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: Be able to name references manually in the reference dialog,"Actually, it even looks like the ability to name a reference has been removed from the reference creation interface. Expanding the scope of this request accordingly.
+
+Being able name references is an important step to allow compatibility with the classic wikitext editor: human-readable names are much easier to use than names like "":5"".",1374250436,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-k6ov7zzpw2ljayjxrczz,task_subcomment,NA
+VisualEditor: {{clear}} template phantom generated too large,"See http://en.wikipedia.org/wiki/United_States_v._Windsor right above the 'Dissents' heading. Clear template covers most of quote box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50395",1372738560,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-32cvx6zgypptrjsr7sri,task_description,resolved
+VisualEditor: {{clear}} template phantom generated too large,"I can no longer reproduce this, nor the issue in either of the duped bugs (T53872, T54431). (Note that you need to look at older versions of the articles, as the problematic markup was changed since the bugs were filed.)
+
+For future reference, here's a copy Jalexander's screenshot above: {F117777}",1429479438,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-32cvx6zgypptrjsr7sri,task_subcomment,NA
+VisualEditor: {{clear}} template phantom generated too large,*** Bug 52431 has been marked as a duplicate of this bug. ***,1395360523,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-32cvx6zgypptrjsr7sri,task_subcomment,NA
+VisualEditor: {{clear}} template phantom generated too large,*** Bug 51872 has been marked as a duplicate of this bug. ***,1377830855,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-32cvx6zgypptrjsr7sri,task_subcomment,NA
+VisualEditor: {{clear}} template phantom generated too large,"Covers most of the box appears to be for latest chrome (what I have). Other report below from FF:
+
+http://i.imgur.com/rAJqIsa.png from FF23 (huge, on top of whole quote box and appears to be pushing other content away too)",1372739147,PHID-USER-f6l3bchko2ogbi4poj24,False,PHID-TASK-32cvx6zgypptrjsr7sri,task_subcomment,NA
+Direct link in revision history to report VisualEditor errors for specific change,"https://en.wikipedia.org/w/index.php?title=Colorado_River&diff=562465192&oldid=562442392
+
+When I go here, I have several options for what I can do with the edit:
+
+> Revision as of 19:24, 1 July 2013 (edit) (undo) (thank)
+
+I'd like another option that says ""(this edit was made with VisualEditor and introduced a problem; report it here)"" or something like that. A JavaScript gadget would be dandy, but I'm not picky about the implementation details.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1372734540,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-clyi3kkewgt6by3dskxa,task_description,declined
+Direct link in revision history to report VisualEditor errors for specific change,"This is probably not needed these days. VisualEditor no longer introduces errors in articles, certainly not at a rate that would demand a prominent action to report them.",1729515165,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-clyi3kkewgt6by3dskxa,task_subcomment,NA
+Direct link in revision history to report VisualEditor errors for specific change,"Rephrasing summary to reflect what the report is about (""Make it easier"" is vague and impossible to define when it's fixed).",1372760577,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-clyi3kkewgt6by3dskxa,task_subcomment,NA
+"VisualEditor: ""Drag to move image"" is buggy in Safari 6","Screenshot of oddly collapsed resizable area
+
+Not sure whether it is specific to Safari 6 but it seems a bit buggy.
+
+Sometimes when holding down the mouse button the cursor won't change from a  ""move"" cursor to a ""drag/add"" cursor (as if it is a regular hover, ""move"" until it hits the edge of the image and then becomes a regular pointer).
+
+Also when dragging and dropping sometimes it seems to separate the image itself and the thumb container is left behind (!).
+
+When resizing it seems to sometimes (sorry, can't be move specific yet) collapse into a single dot (see screenshot).
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11549}",1372721760,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7b3ttjryq7h2dwfsiked,task_description,resolved
+"VisualEditor: ""Drag to move image"" is buggy in Safari 6",Seems to now be fixed.,1385379064,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-7b3ttjryq7h2dwfsiked,task_subcomment,NA
+"VisualEditor: ""Drag to move image"" is buggy in Safari 6","Created attachment 12723
+Screenshot of misplaced image inspector
+
+It also seems to take about a second for it to apply when releasing the mouse, so the user can continue to drag it else where and then after about 2 seconds into the second drag the image moves back and actually moves to where the first drag put it. It is at this point that the inspector stays behind when dropping near another image (see screenshot).
+
+**Attached**: {F11550}",1372721910,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7b3ttjryq7h2dwfsiked,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"http://parsoid.wmflabs.org/en/User:Adjwilley/sandbox10?oldid=562331693
+
+Relevant wikitext:
+
+*{{Cite book| last=Fádil-i-Mázindarání | first= Asadu'lláh | authorlink = Mírzá Asadu’llah Fádil Mázandarání | year=1967 | title=Asráu'l-Á<u>th<u>ár, Vol.I| pages= 453 | publisher=Bahá'í Publishing Trust, Tehran | url = http://www.h-net.org/~bahai/areprint/authors/mazandarani/asrar.htm | ref=harv}}
+
+(note the <u> isn't opened then closed, but double-opened)
+
+Output HTML (with data-*, about and a few others stripped):
+
+<li><span typeof=""mw:Transclusion""><a rel=""mw:WikiLink"" href=""..."">Fádil-i-Mázindarání, Asadu'lláh</a> (1967). <a rel=""mw:ExtLink"" href=""...""><i>Asráu'l-Á<u>th<u>ár, Vol.I</u></u></i></a><u><u>. Bahá'í Publishing Trust, Tehran. p.<span typeof=""mw:Entity"">&nbsp;</span>453.</u></u></span><u><u><span class=""Z3988""><span style=""display:none;""><span typeof=""mw:Entity"">&nbsp;</span></span></span></u></u></li><u><u>
+
+<li>(next item here, note how we're still inside of <u><u>)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372721640,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_description,resolved
+Unclosed formatting elements leaking out of transclusions,"Parsoid output and core output matches on this at this point since we are all in a HTML5 post-Tidy world. 
+
+```
+[subbu@earth:~/work/wmf/parsoid] echo '<ul><li>{{1x|<u>}}</li><li>foo</li></ul>' | php bin/parse.php --normalize
+<ul>
+<li><u></u></li>
+<li><u>foo</u></li>
+</ul>
+
+[subbu@earth:~/work/wmf/parsoid] echo '<ul><li><u></li><li>foo</li></ul>' | php ../mediawiki/maintenance/parse.php
+<ul><li><u></u></li><li><u>foo</u></li></ul><p><u>
+</u></p>
+```
+
+Here is Parsoid's unnormalized output and wt2wt resluts:
+```
+[subbu@earth:~/work/wmf/parsoid] echo '<ul><li>{{1x|<u>}}</li><li>foo</li></ul>' | php bin/parse.php --body_only
+<ul data-parsoid='{""stx"":""html"",""dsr"":[0,40,4,5]}'><li data-parsoid='{""stx"":""html"",""dsr"":[4,23,4,5]}'><u about=""#mwt1"" typeof=""mw:Transclusion"" data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""dsr"":[8,18,null,null],""pi"":[[{""k"":""1""}]]}' data-mw='{""parts"":[{""template"":{""target"":{""wt"":""1x"",""href"":""./Template:1x""},""params"":{""1"":{""wt"":""&lt;u>""}},""i"":0}}]}'></u></li><li data-parsoid='{""stx"":""html"",""dsr"":[23,35,4,5]}'><u data-parsoid='{""stx"":""html"",""autoInsertedEnd"":true,""autoInsertedStart"":true,""dsr"":[27,30,0,0]}'>foo</u></li></ul>
+
+[subbu@earth:~/work/wmf/parsoid] echo '<ul><li>{{1x|<u>}}</li><li>foo</li></ul>' | php bin/parse.php --wt2wt
+<ul><li>{{1x|<u>}}</li><li>foo</li></ul>
+```
+As for the formatting leaking out of transclusions, the tree builder doesn't care about transclusion boundaries and it is unclear how much we ought to worry about it. Selser will still prevent that leakage from serializing back in most cases, but yes, if some of that content is edited, it will cause some minor dirty diffs.
+
+We aren't going to add extra complexity to identify these leaked formatting elements and then expand the scope of the template (likely by migrating the meta-end tag to a different place in the DOM tree).
+
+Since we have the Linter flagging ""syntax  errors"" like this ( https://www.mediawiki.org/wiki/Help:Lint_errors/multiple-unclosed-formatting-tags ), I am inclined to call this resolved since the best strategy here is to fix the wikitext lint errors.",1590072108,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,Is this still an issue? Last activity was 12 months ago…,1416945130,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"Re-titling to reflect our plan [1] to avoid the leaking and match PHP parser semantics instead.,
+
+[1]: https://www.mediawiki.org/wiki/Parsoid/DOM_notes",1386112099,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"https://www.mediawiki.org/w/index.php?title=VisualEditor/Basic_example_worksheet&oldid=751458&veaction=edit
+
+""Foo <tt>bar<tt>\n == Heading == * Lists""",1375204287,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"Change 73369 had a related patch set uploaded by Subramanya Sastry:
+WIP: (Bug 50536) Improved handling of tree-builder fixup
+
+https://gerrit.wikimedia.org/r/73369",1373586328,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"The template encapsulation does not catch all template-affected content, so is not correct really. Alternatively we should be able to undo the leak to match the PHP parser's semantics. That would remove the need for extending the encapsulation in this case.",1373576627,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"No, the tpl encapsulation looks correct to me.  The tree builder correction in this case is quite broad and it would be hard to detect auto-correction as well.  On this last example, there are no autoInserted* flags except on the innermost <u> tag.  As long as we are using a html5 compliant tree builder, our options are a little limited on this kind of html without doing more complicated tracking/analyses.  I am not convinced those are worth the trouble and headaches.",1373053934,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,"Since this is a plain transclusion this is pretty much the behavior I would expect. The formatting is processed in accordance with the HTML spec.
+
+I suspect tidy has a heuristic that closes the <u> at some point in contrast with the HTML spec.
+
+Something that looks broken on the Parsoid side is the missing encapsulation for formatting that spans list items:
+
+echo '<ul><li>{{echo|<u>}}</li><li>foo</li></ul>' | node parse
+<body><ul>
+  <li><u about=""#mwt1"" typeof=""mw:Transclusion"" data-mw='{""target"":{""wt"":""echo"",""href"":""./Template:Echo""},""params"":{""1"":{""wt"":""<u>""}},""i"":0}'></u></li>
+  <li><u>foo</u></li>
+</ul>
+<u>
+</u></body>
+
+(reformatted the above a bit and removed data-parsoid for clarity)
+
+We should in theory be able to detect that the leaked <u>s were completely auto-inserted by the treebuilder. Maybe we can use that information to extend the encapsulation for cases like this one.",1372727019,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Unclosed formatting elements leaking out of transclusions,Diff showing resulting VE breakage: https://en.wikipedia.org/w/index.php?title=User:Adjwilley/sandbox10&curid=38366631&diff=562462441&oldid=562331693 . I'm not sure if the categories being dropped is on the VE or Parsoid side yet.,1372721716,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tl2v542il5zhvqmae5zl,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"There should be an edit notice whenever someone tries to use VE which says something like ""Slower computers or users trying to use older markup should try editing in the older Editor."" and link to the older editor. Otherwise we're directly cutting off plenty of editors who can't figure it out, and would have relatively slow internet.
+
+P.S. My internet is slow enough to not give a satisfactory VE experience, and I consider myself to have decent Indian speed internets
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372710300,PHID-USER-65pjzcmoby2fsgzdrfjq,False,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_description,open
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"Change 135046 abandoned by Alex Monk:
+Attempt to detect slow machines and show an edit notice
+
+Reason:
+This is seemingly impossible for me to get right, and just not worth the effort
+
+https://gerrit.wikimedia.org/r/135046",1401411908,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"Change 135046 had a related patch set uploaded by Alex Monk:
+Attempt to detect slow machines and show an edit notice
+
+https://gerrit.wikimedia.org/r/135046",1400859196,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"We discussed how to do this in #mediawiki-visualeditor a bit. Some quotes:
+
+<Krinkle> when a certain amount of time has passed (potentially taking the document complexity in account as well, avoid measuring network by accident), set a boolean flag, which in getEditnotices() will make it include/exclude that notice accordingly
+<Krenair> I'm wondering what operation we should measure and what timing shows a reasonable speed
+<Krinkle> Krenair: one or more of the actions in the setup of the surface (parsing of html into data DOM, conversion to linenar data model, building of CE etc.)
+
+<Krenair> but those operations will all take different times depending on document length/complexity :/
+<Krinkle> Krenair: Yes, but avoiding I mean, taking into account
+<Krinkle> e.g. not `timespend > maxtime`, but something like `timespent/doc-size > maxratio`
+<Krinkle> RoanKattouw might have some math ideas that are more useful
+<Krinkle> However, we should probably do some research and see how slow the 'too slow' browsers really are.
+<Krinkle> We might be able to measure it with a very simple operation at a small scale (e.g. create an iframe and attach it, just a random unused iframe), that that one operation is measurable enough, we can do it that way.
+<Krenair> Hm. This is getting increasingly out of the 'MediaWiki integration' part
+<Krinkle> The function calls are all in viewpagetarget in setupSurface
+<Krinkle> though ideally this would probably be in ve-core, seems a useful statistis
+
+Roan, could you comment on this when you have time please?",1399321807,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,Timo thinks we can measure performance and display an edit notice if it's slow.,1398879851,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"The plan is to get rid of the beta welcome dialog relatively soon (in the next few months), however…",1398792650,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor,"So we already have the beta welcome dialog, I think we should add something like ""Users of slow computers should consider doing this."" after the ""You can keep using the wikitext editor by clicking the ""Edit source"" tab instead – unsaved changes will be lost.""",1398792405,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-wyt43e5vzv4rp23bx4s7,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"When I add a link to the title of the page, it is displayed as a normal link instead of a <strong class=""selflink"">.
+
+Same problem while editing a page with a 'selflink' already present.
+
+The contributor doesn’t see the article as it will be after saving.",1372684440,PHID-USER-5pyvkdz65d5h5vxebodc,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_description,resolved
+VisualEditor: Links to current page should show as bold,"Change 345526 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Follow-up I88d45aad2: Fix selflink detection
+
+[[https://gerrit.wikimedia.org/r/345526]]
+",1490882209,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 345526 had a related patch set uploaded (by Esanders):
+[mediawiki/extensions/VisualEditor@master] Follow-up I88d45aad2: Fix selflink detection
+
+[[https://gerrit.wikimedia.org/r/345526]]
+",1490871596,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 342084 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Render self-links as if they were <strong>s
+
+[[https://gerrit.wikimedia.org/r/342084]]
+",1490865420,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 341775 abandoned by Esanders:
+Render self-links as <strong class=""selflink"">, not <a ...>
+
+Reason:
+See I88d45aad2aaa45e71b433350986b19764603a1f2
+
+[[https://gerrit.wikimedia.org/r/341775]]",1490864792,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 341774 abandoned by Esanders:
+Allow links to be constructed with custom elements
+
+Reason:
+See I88d45aad2aaa45e71b433350986b19764603a1f2
+
+[[https://gerrit.wikimedia.org/r/341774]]",1490864784,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 342084 had a related patch set uploaded (by Jforrester):
+[mediawiki/extensions/VisualEditor] Render self-links as if they were <strong>s
+
+[[https://gerrit.wikimedia.org/r/342084]]
+",1489091254,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 341775 had a related patch set uploaded (by Esanders):
+[mediawiki/extensions/VisualEditor] Render self-links as <strong class=""selflink"">, not <a ...>
+
+[[https://gerrit.wikimedia.org/r/341775]]
+",1488968700,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"Change 341774 had a related patch set uploaded (by Esanders):
+[VisualEditor/VisualEditor] Allow links to be constructed with custom elements
+
+[[https://gerrit.wikimedia.org/r/341774]]
+",1488968529,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,">>! In T52497#561368, @Jdforrester-WMF wrote:
+> bug 37901
+
+aka T39901 in Phabricator numbering
+
+",1488968489,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"This will need bug 37901 (a general CSS hinting system for links) to be implemented, which is planned for later this quarter. Hinting that links should be red (non-existent), bold (current), purple (stubs), orange (redirects) etc. will need to be supported in that service.",1375235157,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+VisualEditor: Links to current page should show as bold,"**crypticc62** wrote:
+
+For those who might be wondering why selflinks would ever appear in an article: Many pages make use of navigation boxes, such as Template:Extreme Sports. Each navbox usually links to all of the articles that it will be transcluded to. So, with several hundred navboxes, each appearing on at least a dozen pages, we can expect selflinks to appear on several thousand articles.",1375234921,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-75qcblrq4xxtwfp5s76f,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Suppose an article contains two lines in Paragraph formatting, and we want to turn the first one into Heading formatting. Select the entire first line (Cursor at beginning of line, Shift-CursorDown) then choose Heading formatting from the selection box at the top. Result: both lines are turned into Headings, not just the first. (Bold and italics formatting changes work correctly and affect only the current line.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372508580,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-jktlvnskifhm2sbbalki,task_description,resolved
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Line with cursor gets heading(or other) formatting applied
+
+{F41659137}",1704734922,PHID-USER-sbs2thr232mk3iv6jwal,False,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Change 981374 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (402570007)%%%
+https://gerrit.wikimedia.org/r/981374",1701976844,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Change 981374 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[mediawiki/extensions/VisualEditor@master] Update VE core submodule to master (402570007)%%%
+https://gerrit.wikimedia.org/r/981374",1701971212,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Change 980439 **merged** by jenkins-bot:
+%%%[VisualEditor/VisualEditor@master] Don't convert empty-selected paragraphs%%%
+https://gerrit.wikimedia.org/r/980439",1701968690,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","Change 980439 had a related patch set uploaded (by Esanders; author: Esanders):
+%%%[VisualEditor/VisualEditor@master] Don't convert empty-selected paragraphs%%%
+https://gerrit.wikimedia.org/r/980439",1701796908,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","In Microsoft Word, both character-level styling and paragraph-level formatting are only applied to the one line that was selected either with Cursor-at-beginning-plus-Shift-Cursor-down or with a triple-click. In three of these four scenarios, VE behaves as Word.
+
+As far as I can see, applying character-level styling to a line selected with Cursor-at-beginning-plus-Shift-Cursor-down does not become a pre-annotation on the following line (neither in Word nor in VE): the styling is not applied if I insert text at the beginning of that line.",1455301413,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)","This is the same behaviour as in other rich editors.
+
+By selecting in the manner you've stated (""Cursor at beginning of line, Shift-CursorDown"") you've selected the current text, the current line, AND the newline into the place before the first character.
+
+If you mark the text as bold (which is character-level) the boldness becomes a ""pre-annotation"" on the second line before the first character (so typing anything at that point will become bold).
+
+However, changing the format (rather than styling) of some text applies to the entire paragraph (because that's how HTML works) – i.e., the entire second line gets this applied.
+
+We could theoretically apply different behaviour for styling and formatting, so we apply over a newline for the first but not the second, but that might be more unexpected?",1385471045,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+"VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)",This issue exists for all kind of formatting from the Headings pull-down menu.,1383081754,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-jktlvnskifhm2sbbalki,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Add a way to mark a parameter to be dependent on an other paramter. For example :
+We have following parameters:
+""foo1_bar"", ""foo1_baz"", ""foo1_quux"" 
+...
+ ""fooN_bar"", ""fooN_baz"", ""fooN_quux""
+
+fooX_bar required fooX_baz to be used as well, it doesn't require fooX_quux to be used, but if fooX_quux is used, then fooX_bar must have been defined as well
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372464000,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_description,open
+TemplateData: Add a way to express dependencies between parameters,"The previous comments don't explain who or what (task?) exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status, as tasks should not be stalled (and then potentially forgotten) for years for unclear reasons.
+
+//(Smallprint, as general orientation for task management:
+If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead.
+If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}.
+If this task is stalled on an upstream project, then the #upstream tag should be added.
+If this task requires info from the task reporter, then there should be instructions which info is needed.
+If this task needs retesting, then the #testme tag should be added.
+If this task is out of scope and nobody should ever work on this, or nobody else managed to reproduce the situation described here, then it should have the ""Declined"" status.
+If the task is valid but should not appear on some team's workboard, then the team project tag should be removed while the task has another active project tag.)//",1604270588,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,,1453561129,PHID-USER-25bxvdt2svnidzfzjpk7,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,,1453561068,PHID-USER-25bxvdt2svnidzfzjpk7,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Well, I have another case: In German Wikipedia we have Template:Charteintrag, where not only such dependencies are required (eg if “POS_xy” then also “WO_xy”), but even the parameter names depend heavily on earlier added parameters. If I enter 1=x and 2=y, the possible parameters following are POS_x (with WO_x) and POS_y (with WO_y), but of course not eg POS_z! At the moment TemplateData is totally useless with this template, I fear.",1441831007,PHID-USER-zrh22rct2jo5hs6nu67r,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"[Moved from bug 60358 discussion.]
+
+(In reply to Helder from bug 60358 comment #10)
+> (In reply to James Forrester from bug 60358 comment #9)
+> > (In reply to Helder from bug 60358 comment #8)
+> > > (In reply to James Forrester from bug 60358 comment #6)
+> > > > (In reply to Ricordisamoa from bug 60358 comment #5)
+> > > > > or a set of fields may be mutually exclusive (and yet one of them would
+> > > > > be required).
+> > > > 
+> > > > That doesn't make sense. ""Required"" means ""the template will die horribly if
+> > > > you don't include this"". It is *not* a ""we'd like you to fill this in"" –
+> > > > that's what ""suggested"" is for. Most templates will have no 'required'
+> > > > fields.
+> > > 
+> > > It seems perfectly valid for a template to require that ""either A or B be
+> > > provided"" and the user should be able to delete one of them if it is not
+> > > needed.
+> > 
+> > This feels like a pretty edge case (and suggests that we should consider
+> > whether the template should be re-written to be less anti-human); maybe file
+> > a TemplateData bug to ask for a way to express this relationship?
+> 
+> This kind of relationship between parameters was requested on bug 50407.
+
+Well, as I see it, this bug only asks for param-level relationships – if A also B; if C not D; etc.
+
+Should we extend it for shared-param relationships (exactly one of A, B and C are required; D is an alias for E if F is set but is an alias for G if F is not set; …), or should we create a new bug? (BTW, this feels like a potentially ever-expanding system could be created, and we'd probably say this adds too much complexity for the value.)",1409778173,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Change 73708 abandoned by Krinkle:
+Add depends and conflicts parameters
+
+Reason:
+Closing for now to clear review backlog. Can be re-activated when the feature request is accepted.
+
+https://gerrit.wikimedia.org/r/73708",1404942538,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"at en.wp a user has given the example of [[template:for]] where parameter 3 is optional unless parameter 4 is specified, when it becomes mandatory.
+
+They expected that VisualEditor would give them a warning about using parameter 4 without parameter 3. Obviously this is not possible until TemplateData can define such relationships.",1377689591,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"(In reply to comment #3)
+> Note that as for a parameter ""going together with"" other parameters, this is
+> what a ""Set"" is for.
+> 
+> Though Sets are merely suggestive and allow for overlap, it us a lot easier
+> to
+> work with from a user interface perspective.
+Set doesn't make any sense for parameters like ""author1, author2, ..., authorN""
+> 
+> Though TemplateData is generic and should not be tailored specific for
+> VisualEditor, right now I'd recommend we hold off on this change until we
+> find
+""depends"" and ""conflicts"" are pretty much not tailored for VE at all (Though I could agree, sets are).
+> out and/or verify that this can be properly represented in a user interface
+> without making it too complex.
+The most important thing is that common templates can be modeled correctly without ending up with too many false choices, or hiding true choices because they couldn't be modeled correctly.",1373912959,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Note that as for a parameter ""going together with"" other parameters, this is what a ""Set"" is for.
+
+Though Sets are merely suggestive and allow for overlap, it us a lot easier to work with from a user interface perspective.
+
+Though TemplateData is generic and should not be tailored specific for VisualEditor, right now I'd recommend we hold off on this change until we find out and/or verify that this can be properly represented in a user interface without making it too complex.",1373912431,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,"Change 73708 had a related patch set uploaded by AzaToth:
+Add depends and conflicts parameters
+
+https://gerrit.wikimedia.org/r/73708",1373830886,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+TemplateData: Add a way to express dependencies between parameters,See also [[User:קיפודנחש/TemplateParamWizard#Depends on]].,1372589692,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-2xs7662hh3qdt5fonxnb,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"https://en.wikipedia.org/w/index.php?title=Stand-your-ground_law&diff=562005779&oldid=561464750 is a good example (hat-tip to MatMaRex)
+
+--------------------------
+**Version**: unspecified
+**Severity**: major
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50120",1372445760,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_description,resolved
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),Done and will be deployed tomorrow.,1374634250,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),This should be fixed now. Rejoice!,1374519751,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Change 72233 merged by jenkins-bot:
+Array.prototype.splice polyfill for Opera
+
+https://gerrit.wikimedia.org/r/72233",1374518403,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Change 72233 had a related patch set uploaded by Matmarex:
+Array.prototype.splice polyfill for Opera
+
+https://gerrit.wikimedia.org/r/72233",1373066976,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"function testSpliceBroken() {
+	var n = 256;
+	var a = [];
+	a[n] = 'a';
+	
+	a.splice( n+1, 0, 'b' );
+	
+	return a[n] != 'a';
+};
+
+This yields 'true' on Opera.
+
+That's probably the bizarrest browser bug I've ever seen, and it seems to be the root cause of this.",1373052337,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Funnily, my testing shows that the categories are only moved inside the reference if it contains a template. Inserting an empty or text-only reference results in the cateogires eing killed entirely.",1373035435,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Eh, it seems to be Opera-specific after all, I can't reproduce on Firefox (but it reproduces reliably in Opera).",1372504054,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"(In reply to comment #1)
+> Another is
+> https://pl.wikipedia.org/w/index.
+> php?title=Waldemar_Kasta&diff=36944980&oldid=36944831
+
+Bartosz,
+
+Both these corruptions were by you - were both of them made using Opera? If so, I'm happy to mark this bug out to you (but please clean up after yourself when editing using a blacklisted browser).",1372472137,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),"Very strange, looks like metadata is being moved somehow. Do we have any information about what the editors did to provoke this?",1372468169,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Categories deleted or misplaced when a reference is added (in Opera),Another is https://pl.wikipedia.org/w/index.php?title=Waldemar_Kasta&diff=36944980&oldid=36944831 .,1372445852,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-poawg73ix2eh7lpylhyd,task_subcomment,NA
+VisualEditor: Template:Listen (and similar sound files) doesn't render the TMH aspects correctly,"Screenshot
+
+Firefox 21.0, Windows 7 - see screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49896
+
+**Attached**: {F11161}",1372417620,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-6fjqaicfdcw65wigvygy,task_description,resolved
+VisualEditor: Template:Listen (and similar sound files) doesn't render the TMH aspects correctly,"Looks perfect now.
+{F26621568}",1539835123,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6fjqaicfdcw65wigvygy,task_subcomment,NA
+VisualEditor: Template:Listen (and similar sound files) doesn't render the TMH aspects correctly,"It looks better today than in that screenshot, but still a bit funny:
+https://en.wikipedia.org/wiki/Rage_Against_the_Machine?veaction=edit&section=3#1992–2000%3A_Mainstream_success
+{F26280267}
+…But I am 99% sure it will be fixed completely by T201081 (which will swap from using a `<video>` with a fake thumbnail to using `<audio>`). We should test this after that is deployed.
+
+Note that it will display using the HTML5 `<audio>` player in your browser, rather than actual TMH interface. I think attempting to load TMH here is unnecessary, since you can't interact with the element to play it, anyway.",1538513327,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-6fjqaicfdcw65wigvygy,task_subcomment,NA
+VisualEditor: Template:Listen (and similar sound files) doesn't render the TMH aspects correctly,This looks like it is caused by bug 49896.,1375050061,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-6fjqaicfdcw65wigvygy,task_subcomment,NA
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol","This is a legacy of wiki-syntax, where all external links have to begin with the protocol. It would be nice to make the VE link inspector smarter than this.
+
+""www.google.com"" is almost certainly meant to be an external link - if there is an article by this name, then it could be shown in the link inspector dropdown as well, but the option for ""External link"" definitely needs to be there. Even something like ""royal.gov.uk"" should be recognised as a URL.
+
+Requiring ""http://"" or some other protocol at the start is confusing for the newbie, as the protocol component of URLs is generally ignored nowadays.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372414560,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-qdoykgze5mrfb2vlwluc,task_description,open
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol","So we now have a separate external link input, but it shows URLs without a protocol as invalid :/",1439170185,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qdoykgze5mrfb2vlwluc,task_subcomment,NA
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol",">>! In T52360#542816, @Krinkle wrote:
+> We solved this to some degree in WikiEditor with the link dialog in that extension. We can probably re-use some of that logic.
+
+https://github.com/wikimedia/mediawiki-extensions-WikiEditor/blob/master/modules/jquery.wikiEditor.dialogs.config.js#L131
+
+By looking for www.? Yeah, that doesn't work. phabricator.wikimedia.org should be recognised, as well as the bug creator's suggestion of royal.gov.uk.
+
+Sounds like {T76398} would fix this by having the user deal with it instead.",1417555457,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-qdoykgze5mrfb2vlwluc,task_subcomment,NA
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol",*** Bug 56490 has been marked as a duplicate of this bug. ***,1402609062,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qdoykgze5mrfb2vlwluc,task_subcomment,NA
+"VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. ""www.example.org/foo"") and then guess the right protocol",We solved this to some degree in WikiEditor with the link dialog in that extension. We can probably re-use some of that logic.,1373369726,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qdoykgze5mrfb2vlwluc,task_subcomment,NA
+VisualEditor: FlaggedRevs status box causes blank space down the right side of CE content div,"Screenshot of bug
+
+1. Go to [[de:Special:PendingChanges]]
+2. Visit one of the linked articles and edit it in VE
+
+Notice the wide right margin, caused by the floating FlaggedRevs status box.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11085}",1372388280,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-q7kvrcess52gstbba6tv,task_description,resolved
+VisualEditor: FlaggedRevs status box causes blank space down the right side of CE content div,"Indeed, probably fixed a while ago…",1405449142,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-q7kvrcess52gstbba6tv,task_subcomment,NA
+VisualEditor: FlaggedRevs status box causes blank space down the right side of CE content div,Seems fixed?,1405410026,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-q7kvrcess52gstbba6tv,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","At the moment adding categories (through ""page settings"") involves turning away from the actual content. This is a problem because a lot of categories are dependent on the actual content, which needs to be referred back to - birth or death years, college, etc, etc.
+
+Suggestion is:
+* Show the existing categories in the standard skin location (at the bottom of the page, in Vector)
+* Make the categories editable there, in some way.
+
+----
+Original onwiki comments were [[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_6#Categories_-_display_them.2C_please |archive 6]] 
+> I can see categories when I read an article. I can see them below the editing paraphernalia when I'm in Edit Source. But in VE I can only see them by clicking ""Page Settings"", which (a) takes a click and (b) means I can't see any of the article content (eg the hard-to-remember-the-spelling district name, the birth date, etc which I might want to use in creating categories, having seen that they aren't already there). Please display the categories in or around the article, not just as ""Page settings"".
+and [[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_7#Categories:_please_display_them_in_VE_-_not_the_right_bug |archive 7]]:
+> I want to be able to see the categories when I've got an article open in VE: just as I can see them when reading the article, or when editing it in Edit Source. I don't want to have to click on ""Page Data"" to find out whether or not it's already got categories.
+
+--------------------------
+See also: {T67518}
+
+merged duplicates: {T53153} and {T71506}
+",1372262760,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_description,open
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat",">>! In T52239#1562999, @John_Broughton wrote:
+> It would be a definite improvement if the user could reach categories either via a top menu, or by scrolling to the bottom of the page. As several people have pointed out, there are disadvantages of the user being able to do only one of these, and - of course - there is no reason, from a programming viewpoint, why there can't be two paths to the same dialog.
+> 
+> So yes, I support (a) making existing categories visible at the bottom of a page, when in editing mode, (b) having something at the bottom of the page that, when clicked, will open the dialog where categories can be added or deleted, and (c) leaving that dialog accessible via the Pages options menu.
+
+This sounds like a good path forward. It gives two paths to one dialog rather than two different dialogs. Hopefully, we can also extend the bottom-of-the-page experience to the read mode at some point.",1440439943,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","It would be a definite improvement if the user could reach categories either via a top menu, or by scrolling to the bottom of the page. As several people have pointed out, there are disadvantages of the user being able to do only one of these, and - of course - there is no reason, from a programming viewpoint, why there can't be two paths to the same dialog.
+
+So yes, I support (a) making existing categories visible at the bottom of a page, when in editing mode, (b) having something at the bottom of the page that, when clicked, will open the dialog where categories can be added or deleted, and (c) leaving that dialog accessible via the Pages options menu.",1440205952,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","I was pointed to this bug because of a feedback comment. I mostly see discussion about category editing on the page itself. Another feature hotcat offers is to navigate the category-tree, so it is quite simple to put an article in a subcat, or to bring it to a category above it. Can that feature be considered as well?",1438716633,PHID-USER-roxczeg7vc6hdylglkpt,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","How about extracting the categories editor and making it a beta feature as ""HotCatoid""?",1438159829,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","Just reinforcing @whatamidoing-wmf's point. This is one of those features where some user feedback would be welcome indeed, to see whether we are planning to put the right effort in the right feature. My totally subjective impression is that editors seem to be happy with HotCat, where you don't need to deal with wikitext at all. IMHO HotCat's UI could welcome some enhancements, but editing categories at the bottom of the page (where categories are found) seems to be unproblematic.",1438123638,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","Just reinforcing @whatamidoing-wmf's point. This is one of those features where some user feedback would be welcome indeed, to see whether we are planning to put the right effort in the right feature. My totally subjective impression is that editors seem to be happy with HotCat, where you don't need to deal with wikitext at all. IMHO UI could welcome some enhancements, but editing categories at the bottom of the page (where categories are found) seems to be unproblematic.",1438122984,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","This has been discussed several times on wiki, and none of the experienced editors have mentioned concerns about having to scroll all the way to the end of the page.  However, if you're worried about that, then you could leave an item in the toolbar that either jumps to the end of the page, or that does exactly what it does now.",1438120605,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat",">>! In T52239#1477765, @Jdforrester-WMF wrote:
+> Certainly I think this should only happen at the bottom of the page, not the window, yes.
+
+In that case, we'd either be duplicating controls (if we leave the current category interface in) or removing the ability to edit categories without a bunch of scrolling (if we take the current interface out).  ",1437699559,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","Certainly I think this should only happen at the bottom of the page, not the window, yes.",1437699244,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","I'm not sure this would actually be easier for the user. Currently, you can edit categories whenever you want without losing your place in the article; if we just stuck a category widget at the end of the document, you'd have to scroll all the way to the bottom every time you wanted to use it.
+
+We could prevent that by putting the widget in a static flyout at the bottom of the window (as opposed to at the bottom of the //document//). But that means taking more screen space with the interface and splitting the editing tools between two different locations. ",1437698404,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat",*** Bug 69506 has been marked as a duplicate of this bug. ***,1414806319,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","pamdavies7: It is not ""such a big ask"" and the problem is well understood. This is an enhancement request with low priority because there are currently more important things to do, but this will be handled at some point.
+In case you have a tech background, patches are welcome: http://www.mediawiki.org/wiki/Developer_access",1373886151,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","To expand on my point of 07-07: if I'm stub-sorting an article which already has categories, a common technique is to look at a key existing category, see if it has a stub category, if not then go to its parent category, and onwards up the tree (particularly useful in biological taxa etc which are so hierarchic); another technique is to assign a broad stub category and then look at the sub-categories of the stub-category, as being much quicker than going to the full stub listings. Neither of these approaches is possible with VE - I have to either open the article a second time in another tab, or quit VE and do it in Edit Source. 
+
+Please just display clickable links for the categories while I'm editing the article in VE. Is it such a big ask?",1373883409,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","I've been told that [Wikipedia:VisualEditor/Feedback#Categories:_please_display_them_in_VE_-_not_the_right_bug my request] is covered by this bug, so I'll restate it here: please make the categories visible when I'm editing in VE. I can see them when I read an article, or while I'm editing in Edit Source, and I shouldn't have to click on ""Page Data"" to find out whether the article has been categorised or not.",1373238366,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat","We've discussed (but there's no bug for it - until now) duplicating the editing of categories in a box at the bottom of the article that would look similar to/the same as the category box in Vector (but with hidden categories shown, and inherited categories not shown). We'd have to properly design this, of course, so it may take a little time.
+
+There's also a proposal to make the dialogs themselves smaller - bug 49549 - and draggable - bug 49969.",1372270719,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ofqsbhnx4zke4uzfi4r7,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","See the screenshot. I get that it's sort of a one-sided diff in a <poem> box, but it isn't particularly useful to review since no tweaks made by the VE that are problematic could be picked out; one would have to review the entire article, in markup.
+
+I'm not sure if there's a better way to work it or if the answer is just to kill it for new page creations, but.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372171920,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-h6w322yrax25ai4skgpq,task_description,declined
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","Closing since (1) we don't have a clear suggestion here, (2) some power editors clearly find the tool useful, and (3) it would be needlessly confusing to normally have a ""review your changes"" button, but take it away when you're creating a page. I've opened T106926 for the main design inconsistency between the two flavors of the dialog. ",1437786780,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","(Oliver Keyes, where's the screenshot?)
+
+Currently on enwiki and mediawiki.org [Review your changes] on a new page displays the wiki text in a <pre> tag, so the wiki markup continues way off to the right side and is almost unusable.
+
+If VE just gave it a style ""ve-review-newpage"" and give it something like
+   white-space: pre-wrap;
+it would be somewhat usable. Or you could use a poem-like div, from comment #0 it sounds like VE used that in June.
+
+Cheers,
+
+(In reply to comment #0)
+> See the screenshot.
+Where? I see no attachments.",1373922321,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","I disagree; albeit as a power-user, I check the resultant wikitext quite often when I'm doing complex things with templates and parser functions (especially the kind that are subst:'ed).
+
+This will be somewhat moot when we have an HTML-based ""review your changes"" available as well, but that's some months off at this point. :-( Rewording.",1372172512,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour","I guess the ask is ""can we come up with a better way of handling things, or alternately not load the option to review on new page creations?"" The wikitext editor handles it this way, yes. The wikitext editor sucks at it, and shouldn't be providing that button in that scenario ;p.",1372172349,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+"VisualEditor: Wikitext ""review your changes"" is relatively unhelpful for page creations; consider behaviour",This is the exact same behaviour as the wikitext editor; I'm not sure what the 'ask' is?,1372172147,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-h6w322yrax25ai4skgpq,task_subcomment,NA
+VisualEditor: sizing of footnote tags (e.g. [12]) inconsistent.,"See https://en.wikipedia.org/wiki/Joe_Flacco?veaction=edit - for example, references 24 and 25 under the section ""2012 season: Super Bowl MVP"". It looks like one of them is using Template:R, which may explain the problem, but I'm not sure if the icon not rendering properly is a template problem or a VE problem.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1372081320,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yifg3bkbmsq2tzfrga4q,task_description,resolved
+VisualEditor: sizing of footnote tags (e.g. [12]) inconsistent.,"Also in https://en.wikipedia.org/wiki/Michelle_%28song%29 sourced to the sfn template, it looks like.",1372125037,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-yifg3bkbmsq2tzfrga4q,task_subcomment,NA
+VisualEditor: sizing of footnote tags (e.g. [12]) inconsistent.,"From that article, references 25 and 26 (from {{r}} and <ref> respectively) generate:
+
+{{r}} ->
+
+<span about=""#mwt97"" class=""reference"" data-mw=""…"" rel=""dc:references"" typeof=""mw:Transclusion  mw:Extension/ref"" data-parsoid=""…"">[25]</a></span>
+
+<ref> ->
+
+<span about=""#mwt99"" class=""reference"" data-mw=""…"" id=""…"" rel=""dc:references"" typeof=""mw:Extension/ref"" data-parsoid=""…""><a href=""…"">[26]</a></span>
+
+Is this just because the CSS isn't being applied when it's ""mw:Transclusion  mw:Extension/ref"" as opposed to just ""mw:Extension/ref""?",1372084163,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-yifg3bkbmsq2tzfrga4q,task_subcomment,NA
+VisualEditor: Editing of headings is broken in IE10,"Edit [[User:This, that and the other/sandbox/VE6]] in VE using IE10:
+
+1. Try modifying the heading text. You have to double-click on the heading to be able to modify it. Hopefully this stupid IE behavior can be worked around.
+
+2. Double-click, and modify the heading text. ""Save page"" button is still disabled.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372059540,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-rstmsueangena7h4cdaj,task_description,resolved
+VisualEditor: Editing of headings is broken in IE10,This was fixed by undoing MW's overflow:hidden style on headings in https://gerrit.wikimedia.org/r/#/c/144104,1409961747,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-rstmsueangena7h4cdaj,task_subcomment,NA
+"VisualEditor: Broken layout of inspector menu, link inspector (others?) in Monobook","link icon not square
+
+See attachments. Reproduced in Chrome and Firefox by the original reporter, and me.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11416}",1372005420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p5tj36n2mckefr5apd2o,task_description,resolved
+"VisualEditor: Broken layout of inspector menu, link inspector (others?) in Monobook","This has been fixed, AFAICT.",1404168883,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p5tj36n2mckefr5apd2o,task_subcomment,NA
+"VisualEditor: Broken layout of inspector menu, link inspector (others?) in Monobook","Created attachment 12611
+overlapping recycle bin
+
+**Attached**: {F11417}",1372005461,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p5tj36n2mckefr5apd2o,task_subcomment,NA
+"OutputPage: Don't output mw.loader.state ""loading"" and mw.loader.state ""ready"" for the same module","It looks like we currently output both for some modules.
+
+Current output on a wiki with user and site css/js enabled[1] but empty:
+
+<script>if(window.mw){
+mw.loader.state({""site"":""loading"",""user"":""loading"",""user.groups"":""loading""});
+}</script>
+<script>if(window.mw){
+mw.loader.load([""mediawiki.action.view.postEdit"",""mediawiki.user"",""mediawiki.hidpi"",""mediawiki.page.ready"",""mediawiki.searchSuggest"",""mediawiki.page.watch.ajax"",""ext.vector.collapsibleNav"",""ext.visualEditor.viewPageTarget"",""skins.vector.js""],null,true);
+}</script>
+<script>if(window.mw){
+mw.loader.state({""site"":""ready""});
+}</script>
+<script>if(window.mw){
+mw.loader.state({""user"":""ready""});
+}</script>
+<script>if(window.mw){
+mw.loader.state({""user.groups"":""ready""});
+}</script>
+
+The first one with ""loading"" is always output. The last 3 with ""ready"" are output by OutputPage::makeResourceLoaderLink if $module->isKnownEmpty is true.
+
+We should probably optimise this to just output ""ready"" in the first place.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371976440,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-r3jcy4x4njr5hh24ytpk,task_description,resolved
+"OutputPage: Don't output mw.loader.state ""loading"" and mw.loader.state ""ready"" for the same module","> resourceloader: Refactor module links output 
+>
+> Change-Id: I91754ce5fae3d05b4bfa7372372eba81ee2fc579",1412588792,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-r3jcy4x4njr5hh24ytpk,task_subcomment,NA
+"OutputPage: Don't output mw.loader.state ""loading"" and mw.loader.state ""ready"" for the same module","This looks fixed for me, because at the moment I will get directly
+mw.loader.state({""site"":""ready"",""user"":""ready"",""user.groups"":""ready""});
+when there is no site or user js page (bug 46857?).",1408907579,PHID-USER-qaoxfiqu6bxhd5ehlwhc,False,PHID-TASK-r3jcy4x4njr5hh24ytpk,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"https://www.mediawiki.org/wiki/Help:Magic_words#Variables
+
+{{CURRENTYEAR}}, {{CURRENTMONTH}], etc. - possibly a pop-up inserter with a brief description of what each do (and their current value?)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62740",1371860100,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_description,open
+VisualEditor: Provide a way for users to insert variable magic words,"Change 278429 abandoned by Alex Monk:
+[WIP] Add MagicWord::getDocs and i18n messages for documentation of magic words
+
+[[https://gerrit.wikimedia.org/r/278429]]",1484005244,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Change 140445 abandoned by Alex Monk:
+[WIP] Allow TemplateData to output information about magic words
+
+[[https://gerrit.wikimedia.org/r/140445]]",1483653103,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Change 278429 had a related patch set uploaded (by Alex Monk):
+[WIP] Add MagicWord::getDocs and i18n messages for documentation of magic words
+
+[[https://gerrit.wikimedia.org/r/278429]]
+",1458351113,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Change 140445 had a related patch set uploaded (by Jforrester):
+[WIP] Allow TemplateData to output information about magic words
+
+[[https://gerrit.wikimedia.org/r/140445]]
+",1456023513,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Change 140445 had a related patch set uploaded by Alex Monk:
+[WIP] Allow TemplateData to output information about magic words
+
+https://gerrit.wikimedia.org/r/140445",1403119862,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,2014-06-16 22:00:29	<Krinkle>	but we'll need to implemetn support for the colon argument in Parsoid and VisualEditor DM first.,1403110567,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"(In reply to Alex Monk from comment #5)
+> Apparently some of the magic words involving 'colon arguments' will need
+> Parsoid/VE DM support.
+
+Does Parsoid not split out the zeroth argument or something? If so, is there a bug that this can be made semi-dependent on?",1403060528,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,Apparently some of the magic words involving 'colon arguments' will need Parsoid/VE DM support.,1402958830,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"(In reply to Alex Monk from comment #3)
+> Actually, maybe we should just have VE query
+> api.php?action=query&meta=siteinfo&siprop=magicwords, then load a
+> documentation message for it in the given language.
+
+no, ignore this",1402945015,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"Actually, maybe we should just have VE query api.php?action=query&meta=siteinfo&siprop=magicwords, then load a documentation message for it in the given language.",1402761433,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,"So we need to:
+
+* Alter TemplateData to provide documentation for magic words
+* Add extra field to template insert dialog for the addition of magic words.",1402696798,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Provide a way for users to insert variable magic words,Feel like taking this on? It'd be a step towards fixing bug 50855 in general… Big fun challenge. :-),1402608512,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dljoa7k34bkwqsbvudos,task_subcomment,NA
+VisualEditor: Table of Contents should be a draggableNode and insert __TOC__ as needed,"It should be possible for users to modify the location of the TOC (see bug 49224 for getting it shown and updated as they edit), and the system should insert a __TOC__ identifier (that should be silently dropped by Parsoid when not needed?).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371859800,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-zgftkji5nk4n25cdqxjy,task_description,open
+"VisualEditor: No way to identify destination, rather than link text, of links","Because the VE splits up the destination of a link and the text displayed for it (quite rightly) it's impossible, in VE mode, to identify where links point to without source editing. This is kind of a problem for disambiguation issues, for example. Is there any way that this could somehow be hunt-down-able?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371790440,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-e3ncbibtfnsjabzzzce6,task_description,resolved
+"VisualEditor: No way to identify destination, rather than link text, of links","It's nice, but doesn't really address the workflow in comment 3.
+
+(In reply to James Forrester from comment #3)
+> However, this doesn't work well if you know there's one link to [[foo|xxx]]
+> somewhere on the page and you want to change it to [[bar|xxx]], I agree.",1402566355,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links",This is now done with the new context widget system.,1402550246,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links","No, hovering over each link is not the answer: if I'm looking at a large article and want to find and amend the link which is pointing to some particular other page (perhaps in connection with cleaning up dab pages etc), I want to be able to use something like ctrl-F ""Find"" as I can at present: once the article is open in Edit Source, the hidden text is searchable.
+
+As an example, look at [[User:PamD/sandbox for VE]] and find the link to [[Dunmallet]]. Now imagine if that page was the length of [[London]] and you needed to find a similar piped link.
+
+Might also be an issue if people want to find (and check parameters of, or amend, etc) one particular template which is used on a page, but doesn't ""show up"" in the visible article. And probably various other scenarios. ~~~~",1373190367,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links","(In reply to comment #0)
+> Because the VE splits up the destination of a link and the text displayed for
+> it (quite rightly) it's impossible, in VE mode, to identify where links point
+> to without source editing. This is kind of a problem for disambiguation
+> issues, for example. Is there any way that this could somehow be
+> hunt-down-able?
+
+Hover over the link; that's the target, not the anchor, that comes up in the pop-up tooltip. 
+
+However, this doesn't work well if you know there's one link to [[foo|xxx]] somewhere on the page and you want to change it to [[bar|xxx]], I agree.",1372015806,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links","The workflow of ""this article has DAB issues, it's pointing to [disambiguation page], I should point it to [proper page], now to find the link that's pointing to the disambig- shit.""",1371791889,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"VisualEditor: No way to identify destination, rather than link text, of links","You can just click the floating ""chain"" icon to see the name of the destination article. 
+
+What does this bug relate to in particular? Was there some use case where this isn't working/isn't possible?",1371791727,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-e3ncbibtfnsjabzzzce6,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","User:JohnCD at English Wikipedia writes the following:
+""If you enter, for instance, ""Welcome"" in the new template box, on clicking ""Apply changes"" you see the result; but if you enter ""subst:welcome"" you see only {{subst:welcome}}, though after clicking ""Save page"" the result is correct. Should there be a check-box for ""subst"" in the New template dialogue, (a) to save typing it out, (b) to arrange the correct display?""
+
+James F. suggested this would be good to enter as an enhancement request, since template substitution should be supported.
+
+Maggie
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66281",1371756600,PHID-USER-joqqkabmjmvxeucx4ni2,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_description,open
+"Support ""substituting"" templates in transclusion dialog","@matmarex , the [[ https://en.wikipedia.org/wiki/Module:Unsubst | unsubst module ]] can be used in most cases to prevent inexperienced editors from accidentally using substitution erroneously. Beyond that, a better version of TemplateData would allow for instruction about substitution for each template.
+
+For now, I think allowing substitution in VE is still a worthwhile goal, even if it has to remain a somewhat advanced/hidden feature to avoid improper use.",1668563742,PHID-USER-tl3o6dlackm57f3qrt4b,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 855565 **merged** by jenkins-bot:
+%%%[mediawiki/core@master] ParsoidHandler: remove subst feature from wt2html%%%
+https://gerrit.wikimedia.org/r/855565",1668101234,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","For context about this patch: @daniel discovered that feature in Parsoid while doing some refactoring, and we discovered that we were not using it. All it does is to add `subst:` to template invocations, before calling existing APIs for pre-save transform and for parsing. That doesn't seem useful even if we wanted to add substing templates to VE (we could easily add this prefix and call the APIs ourselves).
+
+We're not planning to work on this task apart from this at the moment. The main obstacle is designing the interface so that people wouldn't damage articles by using it without understanding what it does.",1668093586,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 855565 had a related patch set uploaded (by Daniel Kinzler; author: Daniel Kinzler):
+%%%[mediawiki/core@master] ParsoidHandler: remove subst feature from wt2html%%%
+https://gerrit.wikimedia.org/r/855565",1668086122,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Yes, that's the goal.  There is no timeline for when the work might be done.",1623088652,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Am I right in understanding that this ticket seeks to make it possible to use subst when adding a template to a page in VisualEditor, or is that another task?",1622827126,PHID-USER-tl3o6dlackm57f3qrt4b,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Parsoid's API supports substing. But, VE folks need to figure out what they exactly need to support user feature requests. I'm going to untag Parsoid here. @Esanders @matmarex @JTannerWMF: please take a look and retag Parsoid with an updated description if you need anything from us.",1590034383,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Another request for this, this time from @Hoefsldyla :  https://www.mediawiki.org/wiki/Topic:Uq6vtaf8wk0z30zh
+",1548380239,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","[[ https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:%C3%89diteurVisuel/Avis&diff=0&oldid=123998059#Subst_dans_le_mod.C3.A8le_ouvrage | New feedback ]] concerning that task (here, need to subst: a date on a template included with VE).",1457356882,PHID-USER-uciss2jl2e4ifxqqk7wk,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",">>! In T51904#1406296, @Krenair wrote:
+> I'm not sure the parsoid API from T73161 is quite what we were looking for. The idea had been to allow the user to mark a template to be substituted upon save, but with this we'd have to substitute an entire transclusion (immediately?)
+
+If you look at this task's description, it asks for being able to do a subst when inserting a template from the template dialog box. Also, according to the description, susbt already works when saving.",1435560829,PHID-USER-56wtmb23orq4pu5liyj5,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","If I have misunderstood this feature and how it would work inside VE, then we should talk more on IRC sometime to get clarity about how this would / should work and update it here, and we can make appropriate updates to the API.",1435360448,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",">>! In T51904#1406342, @Krenair wrote:
+> Substituting things directly on the client? That sounds like we'd run into more issues involving unbalanced html fragments?
+
+Yes, subst directly on the client. In VE, as far as I understand, you cannot add transclusions that generate unbalanced HTML since you have to ask Parsoid for an expansion and you get balanced DOMs always.
+
+So, as far as I can imagine, this subst feature in VE will have to be in-edit substitution of DOMs rather than on-save substitution of arbitrary wikitext.",1435360176,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",">>! In T51904#1406342, @Krenair wrote:
+> Substituting things directly on the client? That sounds like we'd run into more issues involving unbalanced html fragments?
+
+Yes, subst directly on the client. In VE, as far as I understand, you cannot add transclusions that generate unbalanced HTML since you have to ask Parsoid for an expansion and you get balanced DOMs always.
+
+So, as far as I can imagine, this subst feature in VE, it will have to be in-edit substitution of DOMs rather than on-save substitution of arbitrary wikitext.",1435360150,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",Substituting things directly on the client? That sounds like we'd run into more issues involving unbalanced html fragments?,1435359746,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","But yes, you would have to substitute transclusions immediately, rather than ""on-save"" as with the wikitext PST mode of operation.",1435359430,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",">>! In T51904#1406296, @Krenair wrote:
+> I'm not sure the parsoid API from T73161 is quite what we were looking for. The idea had been to allow the user to mark a template to be substituted upon save, but with this we'd have to substitute an entire transclusion (immediately?)
+
+But, whenever a user edits a transclusion, you are querying the API to fetch the expansion. So, you would enable the subst parameter alongwith the query instead of marking up individual transclusions for 'at-save' substitution. Once substed, the transclusion itself goes away and the editor can further tweak that output if required.",1435359220,PHID-USER-slccyo5rqasgpljxny7g,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","I'm not sure the parsoid API from T73161 is quite what we were looking for. The idea had been to allow the user to mark a template to be substituted upon save, but with this we'd have to substitute an entire transclusion (immediately?)",1435358724,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 153895 abandoned by Alex Monk:
+Add a subst property to template data which adds ""subst:"" to the target
+
+Reason:
+I'm not actually planning to work on this commit. The associated VE commit will continue to depend on this however.
+
+https://gerrit.wikimedia.org/r/153895",1412721735,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 153934 had a related patch set uploaded by Alex Monk:
+Provide a checkbox on template page of transclusion dialog to substitute when saving
+
+https://gerrit.wikimedia.org/r/153934",1407964061,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Change 153895 had a related patch set uploaded by Alex Monk:
+Add a subst property to template data which adds ""subst:"" to the target
+
+https://gerrit.wikimedia.org/r/153895",1407963687,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Subst:ing isn't working (again?  still?).  
+
+If you follow the (soon-to-be-blanked) directions in the user guide, you get the text typed in, with no display, no expansion, and no processing.  The result is that the exact wikitext of your template displays on the page, exactly as if it had been nowiki'd, but without the nowiki tags.
+
+https://en.wikipedia.org/w/index.php?diff=620566012&oldid=618729009",1407626540,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","Not only in insert dialogue. Template text should be inserted and rerendered page immediately.
+for example:
+-[[:en:Template:Accent]]
+-[[:ru:Шаблон:Ударение]]
+
+i do
+-te|xt
+-insert/template - subst:Ударение
+
+i see in VE
+-te{{subst:Ударение}}xt
+(after saving the page text in read mode looks normally: téxt)
+
+
+I want to see in VE
+-téxt
+
+if possible it should be a new method ""template (with parameters) to text ()"" with no return to template
+for example:
+-""insert/subst"" or ""insert/template"" and in dialogue check-box for ""subst""
+-open TemplateData for ""template"" (now for ""subst:template"" TemplateData not shown)
+-press Add template
+-template is executed and generate new text which is inserted same as ctrl+v
+-the new text (or all page) rendered (may consist any other template inside it)",1406716486,PHID-USER-5joeladhczukimiv4rwl,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",*** Bug 59182 has been marked as a duplicate of this bug. ***,1389931233,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","(In reply to comment #4)
+> (In reply to comment #3)
+> > (In reply to comment #2)
+> > > This is effectively a subset of bug 49833 which seems to be part tracking,
+> > > part bugs, part enhancement requests
+> > 
+> > … part mess. :-(
+> > 
+> > Not sure why you turned it into a tracker after Krinkle mis-named it; I don't
+> > think it helps at all. I might undo that.
+> 
+> Sorry, that would be my misunderstanding of Krinke's intentions and then
+> trying to be helpful. :(
+
+Not your fault at all. :-) All fixed now, anyway.",1378227406,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","(In reply to comment #3)
+> (In reply to comment #2)
+> > This is effectively a subset of bug 49833 which seems to be part tracking,
+> > part bugs, part enhancement requests
+> 
+> … part mess. :-(
+> 
+> Not sure why you turned it into a tracker after Krinkle mis-named it; I don't
+> think it helps at all. I might undo that.
+
+Sorry, that would be my misunderstanding of Krinke's intentions and then trying to be helpful. :(",1377908456,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","(In reply to comment #2)
+> This is effectively a subset of bug 49833 which seems to be part tracking,
+> part bugs, part enhancement requests
+
+… part mess. :-(
+
+Not sure why you turned it into a tracker after Krinkle mis-named it; I don't think it helps at all. I might undo that.",1377899956,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog","This is effectively a subset of bug 49833 which seems to be part tracking, part bugs, part enhancement requests",1377897429,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+"Support ""substituting"" templates in transclusion dialog",Lots of important templates need subst. On en {{prod}} and {{afd}} both need to be subst.,1377871154,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-ztq7heekc4zpnp4mj6uf,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"It seems that the server part of this is already correct.  The client just needs to add printable=1 to requests for JS-wrapped CSS should include printable=1, when the page is in print mode (printabable=yes).
+
+This is necessary to make sure that screen CSS is omitted and print CSS is not wrapped in @media print for this use case.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: normal",1371510780,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-uou7qnzilekcbteofdw4,task_description,declined
+ResourceLoader does not process media queries for printable view with JS-added CSS,"Given {T24256} was resolved, that means the printable mode is essentially no longer discoverable/advertised to users. I'm closing this task in favour of T167956.",1507244402,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"I think {T24256} is definitely better than simply dropping the link entirely (although we'd have to hide it for no-JS).  A feature is only useful if users know about it, and I think having the link exposes the fact that our pages look reasonably good when printed.",1433302393,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"I do know that the ""printable"" link, in the past had surprising amount of traffic for other websites. As in: without it, people don't know how to print (yes, i know, i know...)
+
+So if we do remove the printable mode, then having the JS enabled print mode link is probably quite desirable I suspect.",1433165098,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"> Given that we should support printing the view page directly, perhaps it makes sense to remove the ""Printable"" mode from MediaWiki? 
+
+{T24256}",1433112549,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,">>! In T51722#569487, @Mattflaschen wrote:
+> [..]
+> That illustrates that the print styles apply to the current DOM, not the original HTML source.  So even if the JS doesn't run in printable=yes, all the print styles still need to be correct in case they just print directly (without using printable view).
+
+I agree. In fact, I suspect users that print pages would just print directly. It seems counterintuitive to first open a ""Printable version"".
+
+Given that we should support printing the view page directly, perhaps it makes sense to remove the ""Printable"" mode from MediaWiki? The interface to print pages is part of the web browser. Having a control for it seems redundant.
+
+If we want to keep it, we could collect analytics on popularity of printable=yes views in relation to [print events](http://tjvantoll.com/2012/06/15/detecting-print-requests-with-javascript/) (from both printable, and regular mode).",1433110472,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"Not actively working on this, so putting it back in the pool, but I think the original issue holds.  It seems we should either:
+
+1. Pass printable to load.php on printable=yes pages.
+2. Not run JS on printable=yes pages (as Krinkle says was the case earlier).",1393371920,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"Change 69276 abandoned by Krinkle:
+ResourceLoader: Pass printable parameter to load.php.
+
+Reason:
+Closing for now.
+
+https://gerrit.wikimedia.org/r/69276",1393321150,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"(In reply to comment #2)
+> Which is wrong, those things are not supposed to be loaded on a print page
+> (to avoid e.g. collapsible buttons, ""[show]"", etc.). Though some of those are
+> hidden by CSS, it'd be better for them to not initialise in the first place.
+
+Well, if we do that, we need to find an equally simple way to debug the print CSS.  There are extensions that are supposed to do it (e.g. https://addons.mozilla.org/en-US/firefox/addon/web-developer/), but it shows the screen *and* print styles.  There's probably a good way to do it, just need to find it.
+
+More importantly to the average user, we may want to run some JS on the printable=yes view.  People sometimes read in that view, and there's some stuff that works in that bare-bones mode.
+
+For instance, the reference popups on enwiki (https://en.wikipedia.org/wiki/MediaWiki:Gadget-ReferenceTooltips.js) currently work there, and it seems useful.  You can even get the popup to print with some finagling.
+
+That illustrates that the print styles apply to the current DOM, not the original HTML source.  So even if the JS doesn't run in printable=yes, all the print styles still need to be correct in case they just print directly (without using printable view).",1371531290,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,"We didn't pass this to the client and on to load.php because printable pages shouldn't run run any load queue.
+
+http://mediawiki.dev/?printable=yes gives me:
+> #top:
+> mw.loader.load([""mediawiki.page.startup"",""mediawiki.legacy.wikibits"",""mediawiki.legacy.ajax""]);
+> #bottom:
+> mw.loader.load([""mediawiki.action.view.postEdit"",""mediawiki.user"",""mediawiki.hidpi"",""mediawiki.page.ready"",""mediawiki.searchSuggest"",""mediawiki.page.watch.ajax"",""ext.vector.collapsibleNav"",""ext.vector.collapsibleTabs"",""ext.visualEditor.viewPageTarget"",""skins.vector.js""],null,true);
+
+
+Which is wrong, those things are not supposed to be loaded on a print page (to avoid e.g. collapsible buttons, ""[show]"", etc.). Though some of those are hidden by CSS, it'd be better for them to not initialise in the first place.
+
+I think this is a regression. If memory serves, not so long ago there were no mw.loader calls on the printable view. Perhaps a change in Skin caused them to be inserted unconditionally?
+
+Either way, if there is no other way around it, then the proposed change is good, but I'd prefer to prevent the client-side loader from being set up in the first place (so only the <link only=styles> will run).",1371523555,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+ResourceLoader does not process media queries for printable view with JS-added CSS,Related URL: https://gerrit.wikimedia.org/r/69276 (Gerrit Change I691588c39da7fadeac1ca2ace2c1b769fc4e1bd6),1371519777,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-uou7qnzilekcbteofdw4,task_subcomment,NA
+VisualEditor: Diff is done with current revision instead of old revision when editing an old revision,"When I am editing an old revision of a page and then view the diff before saving it is the diff between the current version of the page and my edited version it seems. I was expecting to see the diff between the old revision and my edited version.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1371475440,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-xnegl5h6ucwhzlod3aip,task_description,declined
+VisualEditor: Diff is done with current revision instead of old revision when editing an old revision,"Oh I wasn't aware the wikitext-editor is doing the same. Then I guess you can close it. It should probably be consistent.
+
+And yes the message could probably be improved.",1371542654,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-xnegl5h6ucwhzlod3aip,task_subcomment,NA
+VisualEditor: Diff is done with current revision instead of old revision when editing an old revision,"This is the same behaviour as the wikitext editor. :-)
+
+Theoretically we could have diff-against-current and diff-against-starting-point, but that could be a bit messy.
+
+Do you think the message (""review your changes"" in VE against ""review changes"" in wikitext) is confusing and should be changed?",1371488556,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xnegl5h6ucwhzlod3aip,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly","Screenshot
+
+See on https://en.wikipedia.org/wiki/Brainbuster for example, at the bottom - screenshot attached. Reproduced in Chrome, Firefox and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F11473}",1371464940,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-msldrstq5fb4d2d5owxm,task_description,resolved
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly",Seems to be fixed - confirmed in test2/production.,1422408680,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly",I believe that this was fixed by Ed's work on this last week.,1402549729,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly","(In reply to comment #2)
+> I had wondered whether the fix for bug 54446 would solve this too, but at
+> least in Firefox 24.0 on Linux it is still evident.
+
+Yeah, this is actually a rather more fundamental issue (the ""next"" item from the data model's point of view, if not the user's, is indeed a link). Sorry.",1380324768,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly","I had wondered whether the fix for bug 54446 would solve this too, but at least in Firefox 24.0 on Linux it is still evident.",1380323919,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+"VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly","This only seems to happen with an image at the start of the lead section and seems unaffected by the presence of a template,
+
+Test case: 
+https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=567508072&veaction=edit
+
+Real-world example:
+https://en.wikipedia.org/w/index.php?title=Boden_Professor_of_Sanskrit_election%2C_1860&oldid=567473898&veaction=edit",1375863022,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-msldrstq5fb4d2d5owxm,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,"See also: T51633, T52341",1371431700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-oipcbzqxlofc3iyaefws,task_description,open
+<title> of editing page doesn't respect DISPLAYTITLE,See also {T88117},1427239342,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,Moving to MW core.,1416183397,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,"If I'm right that it's consistent with core, this bug should be moved there.",1398979991,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,"I think this is about VE changing the <title> to ""Editing IPod"", which doesn't respect displaytitle? If so, this is consistent with core's behaviour...",1398776732,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+<title> of editing page doesn't respect DISPLAYTITLE,"Current bug summary: ""VisualEditor: Title doesn't respect DISPLAYTITLE"".
+
+I'm not sure what this means. Looking at the links below, I see various issues, but none related to the <h1>. The <title> is a bit weird, but it's weird without VisualEditor as well.
+
+* https://en.wikipedia.org/wiki/IPod?veaction=edit
+* https://test.wikipedia.org/wiki/IPod?veaction=edit
+
+Further clarification (including links) would be helpful here.",1371441334,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-oipcbzqxlofc3iyaefws,task_subcomment,NA
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,"Some suggestions of improvements to the media insertion dialog; this is mostly a brain-dump which we might turn into a tracker later:
+
+- a way of accessing the file page, on Commons or elsewhere
+- a more clear highlighting
+- maybe slightly enlarging the image
+- double-click to insert
+- filter by: …
+-* media type
+-* language (mostly specific to audio/video but also maps/diagrams)
+-* length (audio/video)
+-* resolution (image/video)
+-* video bit-depth (image/video)
+-* audio bit-depth (video/audio)
+-* sample rate (audio)
+-* format
+-* licence
+-* local vs. Commons
+
+Notes:
+
+The image size is based on the largest default thumbnail (the dialog asks for the 300x300px image and then shows it at 150x*px size). Changing this would need to have discussions with Ops about load on the image renderers and possibly changing the default sizes globally.
+
+The filtering will have to wait for Solr faceted search, if that's indeed coing.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51032",1371425280,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_description,resolved
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,"The first part of this is now done by the wonderful Structured Data team's work on #sdaw-mediasearch, which they've now integrated into VisualEditor. The initial work has address the most pressing problem of language; I expect that the faceted search ideas might come later. Thank you!",1613688042,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_subcomment,NA
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,"It makes more sense to combine all the media-related bugs into bug 37870 as a tracker, and use this for its original intent, to be about structured data about files and using that for inserting.",1394082888,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_subcomment,NA
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,I'm marking a few other improvement suggestions filed as bugs as blockers so they don't get lost.,1377625064,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_subcomment,NA
+VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog,"It'd be nice to be able to search only by file name, if you know the title or know that that the file you want has a particular word in its name.  ""Intitle:apple"" cuts the number of images by 70%, which is a big help when there are ~12K files returned on that search.",1377191107,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-gk2uxvqxmdwjks3o6oar,task_subcomment,NA
+VisualEditor: Empty annotations which display are hidden as alienMetas,"Per Ed's comment on T50605:
+
+> Above change fixes issue with annotations being dropped, but we still need to fix empty annotations not rendering (e.g. `<span style=""display: block; background: red; width: 100px; height: 100px;""></span>`), either here or in a new bug.
+
+This is the new bug. :-)
+",1371065040,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cka2ffmhei6ufmfdjpyi,task_description,open
+VisualEditor: VE crash mid-edit in IE9,"**Author:** `and.radiate`
+
+**Description:**
+Using alpha version as of 11JUN13. Did a small edit on Wikipedia English article ""Nagato-class battleship"" (deleting 3 letters from [Japanese] to form [Japan] in second sentence under section 5.1 World War II. Then scrolled down; after originally displayed area scrolled off screen, the screen went black in the TAB.  Other TABs in IE remained operative.  Back arrow did not produce any results on black screen or URL showing for the Wikipedia TAB.  Reloaded http://en.wikipedia.org in TAB with black screen; successfull load and correct operation thereafter.  Could not reproduce the error.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370999220,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-e6ljc4wlzprcqdkdk7fk,task_description,resolved
+VisualEditor: VE crash mid-edit in IE9,"No reproduction steps in three years, over which time it's been significantly changed. I'm marking this as Resolved for now.",1465404791,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e6ljc4wlzprcqdkdk7fk,task_subcomment,NA
+VisualEditor: VE crash mid-edit in IE9,and.radiate: Have you seen this problem again with a more recent VE version?,1408109540,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-e6ljc4wlzprcqdkdk7fk,task_subcomment,NA
+"VisualEditor: Font weight is removed from ""article"" tab in Monobook","VisualEditor is removing the font weight from the ""article"" tab when using Monobook on the English Wikipedia.
+
+Steps to reproduce:
+
+* Go to <https://en.wikipedia.org/wiki/Canada_Goose_(clothing)>
+
+* Click ""edit this page"".
+
+* The ""article"" tab loses its boldness.
+
+* Clicking the ""cancel"" button does not restore the boldness.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370896140,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-qf4dixqxm23hinqfnhhq,task_description,resolved
+"VisualEditor: Font weight is removed from ""article"" tab in Monobook","Change 130085 merged by jenkins-bot:
+Fix tab selection on monobook
+
+https://gerrit.wikimedia.org/r/130085",1398881455,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qf4dixqxm23hinqfnhhq,task_subcomment,NA
+"VisualEditor: Font weight is removed from ""article"" tab in Monobook","Change 130085 had a related patch set uploaded by Alex Monk:
+Fix tab selection on monobook
+
+https://gerrit.wikimedia.org/r/130085",1398699745,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qf4dixqxm23hinqfnhhq,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"E.g. [[:fr:Foo]] or [[m:Foo]].
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1370631180,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-u7fscppwehap7w2btqmk,task_description,resolved
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"As Roan says, external links are now silently converted to interwikis when appropriate by Parsoid, so this is totally possible, and has been since we fixed it in November.",1396028566,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"This is kind of possible now, by creating external links.",1385136692,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"I just tried adding a link with [[:w:eo]] and got this:
+http://www.mediawiki.org/w/index.php?title=Language_portal%2FWikimania2013%2FEvent_Report&diff=768410&oldid=768371
+
+[Changed the title to avoid confusion with interlanguage links.]",1377094621,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,*** Bug 50889 has been marked as a duplicate of this bug. ***,1374331394,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,"It's actually already possible to create interwiki links by including the interwiki prefix in the link editor; example with wikitech: https://www.mediawiki.org/w/index.php?diff=729932 .
+
+Interwiki links that have been created this way with VisualEditor can still be edited the same way as long as the page isn't saved.
+
+Since this works for new and newly-added interwiki links, I'm not sure why they're blacklisted / green-striped in subsequent edits.",1373532188,PHID-USER-z6nzrwuaij3spgyg23jt,True,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: It should be possible to create interwiki links and edit them subsequently,*** Bug 49545 has been marked as a duplicate of this bug. ***,1371150585,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-u7fscppwehap7w2btqmk,task_subcomment,NA
+VisualEditor: Toolbar button text doesn't line up vertically,"See http://imgur.com/wmAeHRD
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370522640,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-262uhvu3ikqle2l6ewsw,task_description,invalid
+VisualEditor: Toolbar button text doesn't line up vertically,No longer applicable,1392388033,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-262uhvu3ikqle2l6ewsw,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"This is bad, though in a relatively edge case of lanklinks outside the main namespace.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1370489100,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kpzuaoygi6lx5pro226s,task_description,resolved
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"Change 127419 merged by jenkins-bot:
+Use wgPageName instead of wgTitle when fetching language links
+
+https://gerrit.wikimedia.org/r/127419",1398108169,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"Change 127419 had a related patch set uploaded by Catrope:
+Use wgPageName instead of wgTitle when fetching language links
+
+https://gerrit.wikimedia.org/r/127419",1397886324,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),*** Bug 50565 has been marked as a duplicate of this bug. ***,1381266333,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"(In reply to comment #1)
+> This description is a bit cryptic, so .. is bug 50565 a dup of this bug?
+
+It is, yes; sorry for crypticness. Hope it's a little better now.",1381266327,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main),"This description is a bit cryptic, so .. is bug 50565 a dup of this bug?",1381108150,PHID-USER-oxd6f6xemkuyttw7z7wl,True,PHID-TASK-kpzuaoygi6lx5pro226s,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"Users and categories should not be auto-completed based on page names (API action=opensearch) but instead based on their own respective query modules (list=allusers, list=allcategories) because the existence of a description page is optional and neither a subset nor superset of the database tables.
+
+* Pages can exist for inexistent objects.
+* Objects often don't have an associated page.
+
+718db58f introduced category editing with autocompletion from opensearch (with hardcoded 'Category:' prefix). This should be switched to using list=allcategories instead.
+
+That way the input field will no longer include results for inexistent categories, and no longer omit results for existing categories lacking a description page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=65517",1370113020,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qh6gg46z66xqohu77fjn,task_description,resolved
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,*** Bug 65956 has been marked as a duplicate of this bug. ***,1401483580,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"Change 135782 merged by jenkins-bot:
+Suggest categories that exist but don't necessarily have pages
+
+https://gerrit.wikimedia.org/r/135782",1401321989,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"Change 135782 had a related patch set uploaded by Alex Monk:
+Suggest categories that exist but don't necessarily have pages
+
+https://gerrit.wikimedia.org/r/135782",1401295064,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"(In reply to comment #1)
+> Though I commend the effort for correctness, I don't think that this has ever
+> even been brought up in the HotCat feedback. It would be nice though.
+> 
+> However, an empty category (page only), is still a valid category in most
+> workflows (you have to start somewhere), so I think that excluding them is no
+> more correct than including categories without pages...
+
+(Whilst not defending the current MediaWiki behaviour) the way you start a new category is either:
+* Create the description page
+* Add pages to it from wikitext with [[Category: <name> ]]
+or:
+* Implicitly create it by adding pages to it from wikitext with [[Category: <name> ]]
+
+The same is true for HotCat, afaik you can use a category that doesn't exist yet. The page is optional and the 'Category' table row will be created once there are items in it (though it doesn't delete the row if there are no more children in it, so you can still have category pages for categories that don't ""exist"" but do exist in the database).
+
+Either way I think it is more likely for a user to want to add a page to a category that is used on another page (which may or may not have a description page yet) then for a user to first create a category page and then add a page to it. Especially on established wikis.
+
+I agree it doesn't really make sense but this is how MediaWiki works. We could change MediaWiki core to also create category rows immediately when the page is created.
+
+We could do 2 ajax requests for every autocomplete action but that seems a bit too much, and given the choice between the two I think completing based on existing categories instead of category description pages, the former is more likely and also has larger volume (there are more categories than there are description pages, there are relatively few category pages for categories that don't exist, ideally a wiki would have none of them).",1372102674,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page,"Though I commend the effort for correctness, I don't think that this has ever even been brought up in the HotCat feedback. It would be nice though.
+
+However, an empty category (page only), is still a valid category in most workflows (you have to start somewhere), so I think that excluding them is no more correct than including categories without pages...",1370372523,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-qh6gg46z66xqohu77fjn,task_subcomment,NA
+"VisualEditor: On save, warn the user about inconsistent header indexes","It would be very nice if the Ve would warn you about inconsistencies in header levels (when you are skipping a level for instance)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1370005980,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-i4fozwumgivhnul7k3yd,task_description,open
+"VisualEditor: On save, warn the user about inconsistent header indexes","Nice idea.
+
+Possible rules:
+
+* Use of H1 in the main namespace
+* Use of Hn+1 not inside an Hn
+* Others?",1370633090,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-i4fozwumgivhnul7k3yd,task_subcomment,NA
+VisualEditor: Whitespace characters should not take a pre-annotation unless they have non-whitespace after them in the annotation,"In https://de.wikipedia.org/w/index.php?title=Anna_Zaja&curid=7691608&diff=118985342&oldid=118754158 a missing space was added after the name, but it should not be inside the bold part.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://de.wikipedia.org/w/index.php?title=Anna_Zaja&curid=7691608&diff=118985342&oldid=118754158",1369820460,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-6lw5ypbid2gpphswv2j6,task_description,open
+VisualEditor: Whitespace characters should not take a pre-annotation unless they have non-whitespace after them in the annotation,"Rephrased to ""Whitespace characters should not take a pre-annotation unless they have non-whitespace after them in the annotation"". This means that we have to evaluate whether pre-annotation should take place on insertion against both the content and the context, but then re-evaluate on the first non-WS character in a potential pre-annotation. This could get messy.",1372026701,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-6lw5ypbid2gpphswv2j6,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Situation:
+* ResourceLoader wraps modules in closures
+* MediaWiki developers put a closure in each file
+* As a result loading 1 module with 2 files will have 3 closures
+
+```
+mw.loader.implement( 'foo', function ( $ ) {
+  --- foo.a.js
+  ( function ( $, mw ) { 
+    ...
+  }( jQuery, mediaWiki ) )
+
+  --- foo.b.js
+  ( function ( $, mw ) { 
+    ...
+  }( jQuery, mediaWiki ) )
+} );
+
+inside mw.loader#execute:
+
+  script( jQuery );
+```
+
+It has been suggested we add ""mw"" to ResourceLoader's closure and get rid of the per-file closure.
+
+The downside of doing that would be that they are less safe to use ""standalone"". e.g. a jquery plugin would be using $ directly, which, outside MediaWiki ResourceLoader context is bad.
+
+There is also the pending refactoring of ResourceLoader debug mode to not be completely different and near useless by executing in the global scope.
+",1369733580,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_description,resolved
+ResourceLoader: Remove obsolete closures from files,"Change 534762 **merged** by jenkins-bot:
+[mediawiki/core@master] mediawiki.util: Remove redundant file closures
+
+[[https://gerrit.wikimedia.org/r/534762]]",1567876799,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 534762 had a related patch set uploaded (by Fomafix; owner: Fomafix):
+[mediawiki/core@master] Remove redundant closure for module 'mediawiki.util'
+
+[[https://gerrit.wikimedia.org/r/534762]]",1567756299,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 518951 had a related patch set uploaded (by Fomafix; owner: Fomafix):
+[mediawiki/extensions/CentralNotice@master] Remove redundant closure for all packageFiles with own directory
+
+[[https://gerrit.wikimedia.org/r/518951]]",1561457574,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 512519 had a related patch set uploaded (by Fomafix; owner: Fomafix):
+[mediawiki/core@master] Remove redundant closure for all modules with packageFiles
+
+[[https://gerrit.wikimedia.org/r/512519]]",1558862601,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 501993 **merged** by jenkins-bot:
+[mediawiki/core@master] Remove redundant closure for all packageFiles with own directory
+
+[[https://gerrit.wikimedia.org/r/501993]]",1554861690,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 501993 had a related patch set uploaded (by Fomafix; owner: Fomafix):
+[mediawiki/core@master] Remove redundant closure for all packageFiles with own directory
+
+[[https://gerrit.wikimedia.org/r/501993]]",1554628343,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 501960 **merged** by jenkins-bot:
+[mediawiki/core@master] mediawiki.Title: Remove redundant closure
+
+[[https://gerrit.wikimedia.org/r/501960]]",1554594846,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Effectively fixed by T133462, which makes this a possibility regardless of debug mode.
+
+I'm closing this as resolved as it is now possible with T133462 to lint a file as a ""module"" (similar to Node.js) without needing a closure. The only reason our files had closures is for compatibility with debug mode. And for modules using packageFiles, debug mode has been fixed to not change the execution scope.
+
+This does mean we can remove them from files not loaded as part of a module bundle that uses packageFiles, but it seems good enough for me.
+
+Maybe as part of  T85805, we will make it possible for legacy modules, but that's TBD, and separate from this task.",1554583100,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Change 501960 had a related patch set uploaded (by Krinkle; owner: Krinkle):
+[mediawiki/core@master] mediawiki.Title: Remove redundant closure
+
+[[https://gerrit.wikimedia.org/r/501960]]",1554582926,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Note that this bug isn't blocked on implementing global variable mappings.
+
+This bug basically says:
+
+* Closures added by ResourceLoader are not merely a by-product of the deferred loading. They are part of the eco system and to be relied on.
+* Drop the tradition that each .js file should be loadable raw and standalone and instead embrace the dynamic build system.
+
+The main thing blocking this is debug mode. We need to refactor debug mode to not load raw files (bug 62605). Instead it should merely keep them deminified. Ideally with support for source maps (bug 45514).",1404778084,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"
+-- 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
+} );",1404777088,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+ResourceLoader: Remove obsolete closures from files,"Also:
+
+
+modules['bar'] = {
+  scripts: ['bar.a.js', 'bar.b.js'],
+  globals: {
+    ba: Bar
+  }
+};
+
+mw.loader.implement( 'foo', function ( $, mw, ba ) {
+  --- bar.a.js
+    ...
+
+  --- bar.b.js
+  ...
+} );",1369733723,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-knvyif3q5u66km5ufvcb,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","Go to some long article (so long that it won't fit on one screen in your browser), start the visual editor, scroll down, then use up-arrow to walk all the way back up to the top of the article. It's not possible: the first lines of the article remain obscured by the visual editor's menu bar; the only way to make them visible is using the scroll bar or with PageUp.
+
+
+This is Windows 7, Firefox 16.0.2, Chrome 26.0.1410.64 m, Mediawiki 1.22wmf4 (646544a), VisualEditor 0.1.0
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1369410540,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_description,declined
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","IE9, Firefox 16.0.2, Chrome 26.0.1410.64 not supported anymore.",1680797355,PHID-USER-tuy2dac6pfhknbtqmqgh,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","IE9, Firefox 16.0.2, Chrome 26.0.1410.64 now supported anymore.",1680797345,PHID-USER-tuy2dac6pfhknbtqmqgh,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer",Apparently IE is affected too (see bug 63778).,1404175752,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","Go to some long article, scroll all the way down, click to make the blinking cursor visible. Now press and hold the cursor-up key to go all the way back to the top. Upon release of the cursor-up key, the cursor will be invisibly placed behind the toolbar. Another press/release of the cursor-up key is necessary to make it visible again.",1394913857,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer",I believe that this was fixed some time ago as part of the toolbar fixes - please re-open if not.,1386037710,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","I am now seeing the following behavior on mediawiki.org, using both Firefox and Chrome:
+
+Editing a long article with the VisualEditor, scrolling down, and then pressing and holding CursorUp will scroll back to the top, but not quite: the very first line of the article remains obscured by the toolbar. I have to release and repress CursorUp to see that line.",1373636974,PHID-USER-zzvqlvm6i6kml4tfnqvq,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer",This is now merged and will go out later today.,1373491493,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","Change 73015 merged by jenkins-bot:
+Bind listener to keyup to capture arrows & better math for scrolling.
+
+https://gerrit.wikimedia.org/r/73015",1373491380,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","Change 73015 had a related patch set uploaded by Robmoen:
+Bind listener to keyup to capture arrows & better math for scrolling.
+
+https://gerrit.wikimedia.org/r/73015",1373484943,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+"VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer","(In reply to comment #0)
+> Go to some long article (so long that it won't fit on one screen in your
+> browser), start the visual editor, scroll down, then use up-arrow to walk all
+> the way back up to the top of the article. It's not possible: the first lines
+> of the article remain obscured by the visual editor's menu bar; the only way
+> to make them visible is using the scroll bar or with PageUp.
+
+I can't reproduce this as written (for wmf6 or wmf7 on Mac or Linux, don't have Windows to test on). We did change the behaviour of the toolbar a little in wmf5, which may explain.
+
+However, it /is/ possible using the cursor keys to put the cursor underneath the toolbar when scrolled down so that the user can't see where it is. Will change this bug to reflect that, but feel free to revert if you can reproduce.",1371167210,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4bokg6oohi7iw7rzhciv,task_subcomment,NA
+VisualEditor: Cursor position does not match point of insertion (when inline annotation has padding),"Steps to reproduce bug:
+
+* Edit a page and add the following content: `Hello ""<code>world</code>"".`
+* Place cursor before the first quote, then use the arrow keys to move right (after the quote, before W for world).
+* Insert a character.
+
+Expected:
+
+The place where the character appears, and the position of the blinking cursor should be the same. In actually, this is not the case.
+
+The cursor is blinking **inside** the code annotation (close to the W, within the padded area of the code block).
+
+The added character appeared **outside** the code annotation (close to the quote, outside the padded area of the code block).
+
+Screenshot of problem (from May 2013):
+{F10475}
+
+Video capture (July 2018):
+{F23391729}",1369144560,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4iulhoim62acub7cms4q,task_description,open
+VisualEditor: Cursor position does not match point of insertion (when inline annotation has padding),"Back in 2013, a similar issue exited with links and their labels. Both issues were cause due to a limitation that exists in browsers by default (there is only 1 logical position, and where it happens to be is browser-dependent).
+
+However, the link annotation issue has since been fixed by the introduction of virtual positions within the VisualEditor surface to decide whether the user is inside or outside a node. Perhaps the same could be applied to the code annotation?",1530906618,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4iulhoim62acub7cms4q,task_subcomment,NA
+VisualEditor: Cursor position does not match point of insertion (when inline annotation has padding),"Back in 2013, a similar issue exited with links and their labels. Both issues were cause due to a limitation that exists in browsers by default (there is only 1 logical position, and where it happens to be is browser-dependent).
+
+However, the link annotation issue has since been fixed by the introduction of virtual positions within the VisualEditor surface to decide whether the user is inside or outside a node. Perhaps the same could be applied to other annotations?",1530906360,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-4iulhoim62acub7cms4q,task_subcomment,NA
+VisualEditor: Cursor position does not match point of insertion (when inline annotation has padding),"**orbit** wrote:
+
+Yeah, this is reproducible. No adjustment to margin or padding of the alien (the code element) is able to fix this issue though. We're using native browser selection rendering, and this is a side-effect.
+
+One possible future fix would be to allow the cursor to be placed at the first and last offset of protected nodes (contenteditable would have to be set to true) to give the desired cursor rendering. Any keypress would have to first fixup the selection.
+
+I think this is likely a minor occurrence and making such a dramatic change to protectedNodes is out-of-scope for now.",1369267184,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4iulhoim62acub7cms4q,task_subcomment,NA
+VisualEditor: Check for and warn user on unexpected badtoken event says they're now logged out,"When ever the user does a load, save, diff (, other?) action with the server, we should check for whether the new edit token is an anonymous one when we're expecting the user to be logged in, so we can warn the user that they're now logged out (to prevent them asking for their IP to be over-sighted, etc.).
+
+There's potentially utility in doing this in core (for the wikitext editor) as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1369077780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-owjlus7kvzpryeunybdk,task_description,resolved
+VisualEditor: Check for and warn user on unexpected badtoken event says they're now logged out,"This feature has been implemented soon after this task was filed, in July 2013, in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/73446, and still exists today with minor changes.
+
+{F37480899}
+
+(I found this task because we're revisiting the messages for IP Masking: T343848.)",1692047069,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-owjlus7kvzpryeunybdk,task_subcomment,NA
+VisualEditor: Check for and warn user on unexpected badtoken event says they're now logged out,Bug 48657 is the request for the same functionality in core's wikitext editor.,1369078265,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-owjlus7kvzpryeunybdk,task_subcomment,NA
+"VisualEditor: Category sort key setting not done on click out, only on return","In the Category inspector, start setting an over-ride for a category's sort key, but instead of pressing return, click out; no sort key is set. If you change and click ""apply"", it seems like it should apply but doesn't, confusingly.
+
+Thoughts?
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1368745320,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lunpphbvjkp5qsin6ywz,task_description,resolved
+"VisualEditor: Category sort key setting not done on click out, only on return",Now merged.,1370985956,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lunpphbvjkp5qsin6ywz,task_subcomment,NA
+"VisualEditor: Category sort key setting not done on click out, only on return",Related URL: https://gerrit.wikimedia.org/r/67920 (Gerrit Change I256d2b21bc2306959f6d6a0373386054b21dadfe),1370904596,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lunpphbvjkp5qsin6ywz,task_subcomment,NA
+VisualEditor: Auto-selection covers adjacent text over punctuation,"This seems weird to me, but it still might be intentional.
+
+If you put the caret immediately after a sentence ending in a period (e.g. the last sentence of the lede from https://en.wikipedia.org/w/index.php?title=Kono_Statement_of_1993&oldid=546398254&veaction=edit), then click the Link button, it tries to link the last word, including the punctuation.
+
+I would expect it to let you create an new link, without assuming any existing anchor.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368583260,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-3tivkrvvx7tiwvalguwy,task_description,resolved
+VisualEditor: Auto-selection covers adjacent text over punctuation,Merged in master; will go out as part of wmf5.,1368978683,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3tivkrvvx7tiwvalguwy,task_subcomment,NA
+VisualEditor: Auto-selection covers adjacent text over punctuation,Related URL: https://gerrit.wikimedia.org/r/64481 (Gerrit Change I2408229cddd876ff8fe55a9eddf9bac87a61457e),1368888486,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-3tivkrvvx7tiwvalguwy,task_subcomment,NA
+VisualEditor: Auto-selection covers adjacent text over punctuation,"Bug.
+
+Because null (the value we get for the end of the sentence) is silently converted to the string 'null' by RegExp#test (!?) and so we think it's an 'ALetter' which triggers the ALetter-MidNumLet-ALetter rule for mid-word punctuation, and so no break is returned.",1368888212,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-3tivkrvvx7tiwvalguwy,task_subcomment,NA
+VisualEditor: Auto-selection covers adjacent text over punctuation,"This is indeed intentional (and took some time to get right). If the cursor is in, or directly adjacent to, a word, so that you can link a word quickly as a keyboard user without having to use a mouse or do keyboard-based shift-selection.
+
+However, this is meant to not trigger when you're not in the ""context"" of a word, so it does some fancy language-dependent Unicode whitespace detection; it should be doing this for punctuation but apparently isn't, so referring to Ed to investigate.",1368727707,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-3tivkrvvx7tiwvalguwy,task_subcomment,NA
+VisualEditor: Image in template gets cut off,"When editing http://de.wikipedia.org/wiki/Wikidata the top of the Wikimedia logo in the template at the bottom of the page is cut off. (It might also be hidden behind the grey bar or something.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368550980,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-qglalluk4kbrg2flbvzv,task_description,resolved
+VisualEditor: Image in template gets cut off,"Not happening for me in Chrome or FF. Assuming this was a browser bug that has since been fixed, but please re-open if it is still happening.",1701795362,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+VisualEditor: Image in template gets cut off,"This happens in any article that uses the following template with an image, which is lots and lots and lots
+https://de.wikipedia.org/wiki/Vorlage:Navigationsleiste
+
+https://de.wikipedia.org/wiki/Bezirk_Altona?veaction=edit
+
+And the German template appears on many other languages as well.
+https://bar.wikipedia.org/wiki/Wikibooks?veaction=edit",1374479589,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+VisualEditor: Image in template gets cut off,"We aim to render templates as similarly as possible, but there are some exceptions at this time. One such exception is that protected elements and their child elements positioned as 'absolute' or 'fixed' will be changed to relative. Protected elements are usually non-text or generated elements like images or templates.
+
+Specifically in this case the CSS rule for elements that match '.ve-ce-alienNode, .ve-ce-alienNode *' is being used to set all elements relative. In a more recent version of the code this rule is now renamed to '.ve-ce-protectedNode, .ve-ce-protectedNode *' but it's effect is the same.
+
+We should probably be only applying relative positioning to elements that are actually positioned 'absolute' or 'fixed', because it's currently being applied to an element that's positioned 'static'.",1368729636,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+VisualEditor: Image in template gets cut off,"Created attachment 12328
+screenshot of the issue in chromium in kubuntu
+
+**Attached**: {F10816}",1368728163,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+VisualEditor: Image in template gets cut off,I cannot reproduce this using either Firefox or Chrome - which browser(s) does this appear in? Do you have a screenshot I could see? Does it still appear?,1368727833,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qglalluk4kbrg2flbvzv,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"It should be possible to edit a part of a MediaWiki page such as a section or paragraph via VisualEditor without loading the entire article into the editor. This would be especially useful on mobile devices. This ticket is designated to serve as the parent task for all work related to such a goal.
+
+The parsing-related work can be seen at [[https://phabricator.wikimedia.org/project/view/3331/|Parsoid: Section-Editing-Support board]].",1368497160,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_description,open
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Not sure how related these are, but task watchers may be interested in {T209955} and children. (My uneducated observation is that the one doesn't necessarily sort the ""performance"" aspect of this one.)",1605882637,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I am just tyring to get the gnarly dependency graph look a bit more sane .. and AFAIK, this task isn't dependent on read views since you've all embarked on this work in previous years already. If my edit is in error, feel free to add the dependency back.",1595628476,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#6218951, @valerio.bozzolan wrote:
+> Is this task also about supporting `action=edit&section=new` in VisualEditor?
+
+I don't think we have plans to add that, sorry.",1592252834,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,Is this task also about supporting `action=edit&section=new` in VisualEditor? Thank you.,1591964176,PHID-USER-hphk5jxfxfgl64tpfacw,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Thanks. I take your word for it that editing a section on the same page
+will be *faster* than loading the section editor on a fresh screen. The
+design intent is to reduce client load by putting as little of the page as
+practical in edit mode.",1552558162,PHID-USER-axuerq3wmxtfm6tav6bu,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Just as a comment, this task is for ""section editing inline with read mode"", a cooler/faster system than T76541 (which is section editing on its own page). Not sure if that's clear here.",1552409670,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,We need to further explore the approach. ,1537375112,PHID-USER-hqyy4wr7smuc4rzaoio5,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#4559824, @Jdforrester-WMF wrote:
+>>>! In T50429#4559065, @deryckchan wrote:
+>>>>! In T50429#4558267, @kaldari wrote:
+>>> Currently the main blocker (although it may not be a hard blocker) is parsing support for managing state that is page-level (mainly for reference management). @dchan  is [[ https://gerrit.wikimedia.org/r/#/c/VisualEditor/VisualEditor/+/433753/ | exploring doing some of the subtree editing business on the client side ]] as something of a stop-gap solution. The Parsing team's [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ | work on server-side ref management ]] will probably be a better long-term solution (see T146072). They are hoping to have that work wrapped before the end of 2018. Anything to add @ssastry, @dchan, @DLynch, @Esanders?
+>> 
+>> What's the worst that can happen if we let VE load a section of a page, ignoring page-wide state variables? We have made do with section edit page previews, which ignore the effects of other parts of the page on the section you're editing, without too many issues for over a decade.
+> 
+> From a product feature perspective, the citation functionality that people most like about VE wouldn't work (it's entirely page-level content). With the stop-gap work Ryan mentions, it will, mostly, but //e.g.// citations from this section but also used elsewhere won't be editable, which will be very confusing.
+> 
+> From a product reliability perspective, there's the risk of catastrophic page corruption from section-spanning structures (people putting headings in a table, using headings via a template, or using templates that open a div but don't close it, or…), and even if that is somehow(?!) avoided, it'll be at best confusing when some section edit buttons refuse to load.
+
+
+Parsoid currently provides <section> wrappers around HTML and these section wrappers also have editable / uneditable markers on them based on the well-formedness of the wikitect that generated them. So, a section edit scenario, if the section is opened for editing, Parsoid guarantees that the content in there does not contain HTML tags that had an incorrect overlap elsewhere. So, if you open such a section for editing (and just that section), and since VE doesn't introduce bad markup, you are unlikely to cause page corruption.
+
+As for dealing with global state, we have two separate work-in-progress patches
+* https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ frees clients from having to worry about global state, i.e. what happens if you delete a named ref that is used elsewhere. That patch requires clients to mark deleted references with a 'deleted' marker in the data-mw property instead of actually deleting the refences. Parsoid then handles updating state appropriately.
+* https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/441151/ adds support for subtree editing. It effectively takes the desired subtree and computes a ""closure"" of that subtree wrt global state so that the subtree now behaves like a self-contained high-level document. This depends on the previous patch for handling named references.
+
+As part of the patches above, we are adding extension API endpoints to make this support generic, since for example, there is also templatestyles, which has page-level global state when templatestyle uses are deduplicated.
+
+It will take a little while to work through all the details to completion, test, etc. but that is the generic direction we are going towards on the Parsoid end.",1536249606,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Thanks James, that sounds reasonable. I think Ryan's proposal is a fine
+solution - we can allow sections to be edited while freezing references
+that are reused elsewhere on the page, preventing them from being deleted.
+
+If a section cannot be edited, I think users will find it reasonable when
+they see an error like ""This section cannot be edited on its own because it
+depends on [another section of the page / name of transcluded page]. Please
+try editing [the whole page / link to transcluded page] instead.""",1536166546,PHID-USER-axuerq3wmxtfm6tav6bu,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#4559065, @deryckchan wrote:
+>>>! In T50429#4558267, @kaldari wrote:
+>> Currently the main blocker (although it may not be a hard blocker) is parsing support for managing state that is page-level (mainly for reference management). @dchan  is [[ https://gerrit.wikimedia.org/r/#/c/VisualEditor/VisualEditor/+/433753/ | exploring doing some of the subtree editing business on the client side ]] as something of a stop-gap solution. The Parsing team's [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ | work on server-side ref management ]] will probably be a better long-term solution (see T146072). They are hoping to have that work wrapped before the end of 2018. Anything to add @ssastry, @dchan, @DLynch, @Esanders?
+> 
+> What's the worst that can happen if we let VE load a section of a page, ignoring page-wide state variables? We have made do with section edit page previews, which ignore the effects of other parts of the page on the section you're editing, without too many issues for over a decade.
+
+From a product feature perspective, the citation functionality that people most like about VE wouldn't work (it's entirely page-level content). With the stop-gap work Ryan mentions, it will, mostly, but //e.g.// citations from this section but also used elsewhere won't be editable, which will be very confusing.
+
+From a product reliability perspective, there's the risk of catastrophic page corruption from section-spanning structures (people putting headings in a table, using headings via a template, or using templates that open a div but don't close it, or…), and even if that is somehow(?!) avoided, it'll be at best confusing when some section edit buttons refuse to load.",1536161053,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#4558267, @kaldari wrote:
+> Currently the main blocker (although it may not be a hard blocker) is parsing support for managing state that is page-level (mainly for reference management). @dchan  is [[ https://gerrit.wikimedia.org/r/#/c/VisualEditor/VisualEditor/+/433753/ | exploring doing some of the subtree editing business on the client side ]] as something of a stop-gap solution. The Parsing team's [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ | work on server-side ref management ]] will probably be a better long-term solution (see T146072). They are hoping to have that work wrapped before the end of 2018. Anything to add @ssastry, @dchan, @DLynch, @Esanders?
+
+What's the worst that can happen if we let VE load a section of a page, ignoring page-wide state variables? We have made do with section edit page previews, which ignore the effects of other parts of the page on the section you're editing, without too many issues for over a decade.",1536140954,PHID-USER-axuerq3wmxtfm6tav6bu,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Thanks @kaldari! As I understand it the fundamental differences between T76541 and T146072 are:
+
+- With T76541 , the browser has all the document-level data (meta / internal list items, in VE parlance) at its disposal, but at a cost of the whole document being received and parsed (though not rendered, which greatly improves speed and memory usage).
+
+- With T146072 , the browser only has to receive and render a single section that effectively behaves like a small, simple document, but at a cost of not having all the document-level data at its disposal.
+
+It seems there's substantial overlap where either may be adequate to achieve certain functionality, but that the tasks are actually complementary – there are use cases that would need one or the other. For instance, T76541 would be needed to suggest existing citations when adding a new reference, or to keep reference numbering accurate while editing; but you would clearly want T146072 for certain microedit-style approaches that step rapidly between documents.",1536114562,PHID-USER-lliyevigiycjbybglftk,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,Are you aware of the VEForAll extension? https://www.mediawiki.org/wiki/Extension:VEForAll,1536110041,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Currently the main blocker (although it may not be a hard blocker) is parsing support for managing state that is page-level (mainly for reference management). @dchan  is [[ https://gerrit.wikimedia.org/r/#/c/VisualEditor/VisualEditor/+/433753/ | exploring doing some of the subtree editing business on the client side ]] as something of a stop-gap solution. The Parsing team's [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/services/parsoid/+/456520/ | work on server-side ref management ]] will probably be a better long-term solution (see T146072). They are hoping to have that work wrapped before the end of 2018. Anything to add @ssastry, @dchan, @DLynch, @Esanders?",1536108865,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,">>! In T50429#979728, @Jdforrester-WMF wrote:
+> It's entirely do-able for the developers of SemanticMediaWiki to create a VisualEditor integration for each of the fields in a form. Indeed, it's one of the use-cases we built VisualEditor around.
+
+I have been poking around the VE and (recently) Semantic Forms looking for a place where I can dig in.  This may be it.  I can't promise anything, but knowing this is a place that needs work and that some of my users could use it helps.
+
+Knowing other people want it doesn't hurt, either.",1421355867,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"It's entirely do-able for the developers of SemanticMediaWiki to create a VisualEditor integration for each of the fields in a form. Indeed, it's one of the use-cases we built VisualEditor around. However, it'd be a bunch of work and it's nothing we're planning to do at the Wikimedia Foundation (we don't support Semantic MediaWiki either). So effectively this is a ""no"" for your question.
+
+This task is talking about using VisualEditor to edit parts of a single-content-block page, not a page made up via collections of different pieces of information.",1421340191,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I've been using Semantic Forms for more than 4 years now. It used to support the FCKEditor extension (and branch SMW+ supported the WYSIWYG extension).
+But the decision to stop using FCKEditor going forward was at least related to the promise of a cleaner integration with VisualEditor (Yaron Koren would be able to
+comment more accurately on that).  I believe that was decided around 2012.
+
+I'm now with a new company, and I've been tasked with evaluating Atlassian Confluence.  It supports bare pages, but also form-based pages.  The only significant feature it has over
+Semantic Mediawiki / Forms installation is WYSIWYG editing.  I can't stick with MW 1.16 / FCKEditor as I did at my previous company, so it looks like we'll to go with 
+Confluence... which is a shame to me, since I know how versatile the mediawiki environment is.
+
+It doesn't seem like the work-arounds being considered would support being about do do WYSIWYG editing in a text field or the free text area of a Semantic Form.  
+//If that's the case//, it would be nice if this could be marked WONTFIX, and a new issue created that discusses compensating for the lack of an edit section as we
+know it in Mediawiki.
+
+Or, it's 2015, the solution is about to be released any day now, and I'll shut up (I can do that last one anyway).",1421340016,PHID-USER-v7p53gf64fwttu5ylooz,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I've been using Semantic Forms for more than 4 years now. It used to support the FCKEditor extension (and branch SMW+ supported the WYSIWYG extension).
+But the decision to stop using FCKEditor going forward was at least related to the promise of a cleaner integration with VisualEditor (Yaron Koren would be able to
+comment more accurately on that).  I believe that was decided around 2012.
+
+I'm now with a new company, and I've been tasked with evaluating Atlassian Confluence.  It supports bare pages, but also form-based pages.  The only significant feature it has over
+Semantic Mediawiki / Forms installation is WYSIWYG editing.  I can't stick with MW 1.16 / FCKEditor as I did at my previous company, so it looks like we'll to go with 
+Confluence... which is a shame to me, since I know how versatile the mediawiki environment is.
+
+It doesn't seem like the work-arounds being considered would support being about do do WYSIWYG editing in a text field or the free text area of a Semantic Form.  
+''If that's the case'', it would be nice if this could be marked WONTFIX, and a new issue created that discusses compensating for the lack of an edit section as we
+know it in Mediawiki.
+
+Or, it's 2015, the solution is about to be released any day now, and I'll shut up (I can do that last one anyway).",1421339932,PHID-USER-v7p53gf64fwttu5ylooz,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to Tim Starling from comment #49)
+> > * Editing by section blocks users from editing other areas at the same time
+> > that the notice flaws in after they've entered editing, for very limited
+> > added-value.
+> 
+> For large articles, I think the added value would be very large indeed.
+> People don't want to wait tens of seconds to make a small correction, and
+> it's likely that VE performance causes many edits to be abandoned.
+> 
+> Perhaps there are other solutions for the performance issue, but it seems to
+> me that this is a fairly obvious approach, especially for bandwidth
+> reduction.
+
+For what it's worth...
+
+I did a non-scientific poll and asked the Hebrew Wikipedia community what are the people's reasons to avoid VE. Precisely this suggestion came up several times.",1408623631,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"No, it definitely shouldn't be a preference – instead, it should be possible for everyone to ""expand"" the editing area from the one section to the entire article.",1404067177,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Another thought on the preference: currently clicking on a section edit gives a pre-filled edit summary including the section.  Whether this happens should depend on the same preference.  If I have ""section-editing"" set to yes, I would get the pre-filled edit summary and other sections hidden; if I have it set to no, I would get no pre-filled edit summary, and I would see the whole article, as happens now.  This would help avoid the (common) situation where the edit summary is misleading when a section edit is clicked.",1403957632,PHID-USER-ufjbf3qatjamiwoal5fp,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Re comment 52: I agree that show/hide would be nice for the uneditable sections.
+
+More importantly, if this behaviour is implemented, please make it a preference option.  I often use ""edit beta"" on one section in order to fix a problem I see in the section just above it; I'd hate to lose that capability.",1403956163,PHID-USER-ufjbf3qatjamiwoal5fp,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Mike Christie has a suggestion:  Edit the whole page, but only display the chosen section.  
+
+By this I don't think he means ""discard"" everything except the section, but instead just to cover up the other parts.  We're already scrolling to the chosen section, so this would add maybe a gray or white block over everything above that (or perhaps collapse it), and ideally everything below it, too.  
+
+This would help people who are using section editing to keep them focused on their chosen tasks, rather than because of beliefs about performance or edit conflicts.",1403929593,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Comment 46 ignored comment 44, hence making the priority value reflect reality again. If there are further good arguments to give this higher priority, feel free to convince the *developers* to set a higher priority again.",1394027896,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #49)
+> 
+> Yes, the existing feature prevents users from editing other sections on the
+> page, which sucks. That could presumably be addressed in VE: a separate
+> content-editable region could be created by each section edit click, to be
+> saved in bulk.
+
+
+i agree with Tim's comment wholeheartedly, except the last paragraph: preventing the user from editing outside the section doesn't ""suck"". it's a great feature.
+
+when editing a section, we have automatically generated edit summary with the section name. for users that use wikitext editor, you pretty much know, when you see the very common ""/* section name */ optional comment"" edit summary, that the edit is indeed confined to the section whose name appears in the comment.
+
+but with VE, because of the wrong (IMHO) way bug 50872 was handled, a user can press the ""sectionedit"" link of some section, then edit anywhere on the page, and the summary will still show the section name of the click. this makes the summary practically useless: when looking at the history, seeing a section name in the summary tells me nothing - i don't care which button Joe pressed, i care which content was changed, and the summary does not tell me that anymore.[1]
+
+
+since the most urgent issue ATM for VE is unacceptable performance on longer articles with slower machines, true section edit would be (as Tim notes) a very very desirable feature. 
+
+how about this: i think that the cases where a section is not balanced, in terms of html tags (the case described in comment 2) is very rare. how about falling back to full article edit in those rare cases? [2]
+true, it means that those cases would be even slower, but i believe that those are a negligible minority. the vast majority of the sections *are* balanced, and will gain greatly (performance wise) from the ability to edit a single section.
+
+
+peace.
+
+---------------------------------------------
+
+[1] this can be handled by undoing the solution for bug 50872, and solving bug 51903 instead (i.e., create the summary by analyzing the diff instead of the button the user clicked), but the best thing, IMO, would be to support true ""section edit"" for VE.
+
+
+[2] this means: get the section content from the server, and if it ""does not make sense"", like the example in comment #2, get and edit the whole page.",1375911862,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #2)
+> {|
+> ! Foo !! Bar
+> |-
+> === Section 1 ===
+> |-
+> | Foo || bar
+> === Section 2 ===
+> |-
+> | Foo || bar
+> |}
+> 
+> Coming up with a solution to this is would be a significant piece of
+> engineering effort for marginal utility.
+
+The section editing feature in the old parser works by excluding all sections headings where the heading is not a child of the document root. The previous section thus runs on past the excluded heading. This means that a section can always be represented as a set of adjacent DOM subtrees. It seems to me that the same solution could be implemented in VE. 
+
+The definition of ""children of the document root"" would change somewhat, since it is a different kind of DOM, so the number of excluded sections would be larger, but it would still be a better solution than what we have now.
+
+> * The reasons we brought in section-editing originally were two-fold - to
+> skip
+> past confusing wikitext in other areas to find the item you actually wanted
+> to
+> edit (not an issue in the context of VisualEditor), and to avoid edit
+> conflicts
+> using the page-based diffs at the time (not an issue for ~ 7 years since Tim
+> re-wrote the diff tool).
+
+Section editing has never had any special case to help with edit conflicts -- it was always dealt with using the generic three-way merge feature, which, for the record, I did not write.
+
+I think the main two reasons for implementing section editing were bandwidth and avoiding the need to scroll. Erik's original post on the subject suggests as much:
+
+http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/3433
+
+Note that it was implemented at a time when 56k modems were still common -- I had one at the time, and I was certainly glad of the performance improvement.
+
+> * Editing by section blocks users from editing other areas at the same time
+> that the notice flaws in after they've entered editing, for very limited
+> added-value.
+
+For large articles, I think the added value would be very large indeed. People don't want to wait tens of seconds to make a small correction, and it's likely that VE performance causes many edits to be abandoned.
+
+Perhaps there are other solutions for the performance issue, but it seems to me that this is a fairly obvious approach, especially for bandwidth reduction.
+
+Yes, the existing feature prevents users from editing other sections on the page, which sucks. That could presumably be addressed in VE: a separate content-editable region could be created by each section edit click, to be saved in bulk.",1375745889,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"james, we tried your sections within a table example from above here:
+https://en.wikipedia.org/wiki/Wikipedia_talk:VisualEditor/Known_problems#section_in_a_table
+and we could not create something useful.",1375590809,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"note blocks section edit
+
+**Attached**: {F10744}",1375517586,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"upgrading this to ""highest"" as this is the main reason for item 1 (slow loading), item 2 (slow scrolling) and item 6 (no section editing) of https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Known_problems. personally i think this should be _the only_ ""immediate"". why?
+
+i tried it at https://en.wikipedia.org/wiki/Jos%C3%A9_Mourinho.
+* 1 click and 15 secs to edit
+* 1 click to make go a away a note (see attachment)
+* 1 click to edit summary
+* 1 click and 20 secs to review changes
+* 1 click to return to save form
+* 1 click and 40 secs to save
+* 5* pg down to go to the section just edited
+
+section edit with the text editor takes:
+* 1 click and 2 secs to open
+* 1 click and 2 secs to preview
+* 1 pg-down to find the save button
+* 1 click and 10 secs to save",1375516381,PHID-USER-2ccnbnjo2s2q3diidydr,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"This:
+""but I cannot justify spending donor funds to that extent""
+just turned into:
+""we're hoping to be able to undertake it some time towards the start/middle of next calendar year""
+
+Which sure sounds like a priority change, so I'm not sure if my flag change was psychic-magic or precipitative-magic, but either way, it now seems like the correct priority status.  I've tried communicating other ways:
+https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Section_editing_will_never_be_implemented
+(""Any update from the dev discussion?"") but got no answer, and the known problems page still says ""not planned"".
+
+Anyway, it's good to hear that you are now planning to do this.  I'm sure it will be worth it for low-bandwidth editors.",1375369864,PHID-USER-und42bbibe2hhp4rbyu3,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #43)
+> I'm upgrading this to ""normal"" since it's listed at #4 on
+> https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Known_problems and I'm
+> not
+> seeing any good case for low/lowest made here.
+
+The ""priority"" field doesn't mean ""how much do people want it"", it's ""how soon are the developers likely to get to do it"".
+
+As I explained above, this will require a series of major changes in Parsoid and a huge re-write of MediaWiki's skins system as we switch over to use Parsoid's generated HTML for read pages, and is many (many) months away - we're hoping to be able to undertake it some time towards the start/middle of next calendar year.
+
+Magically changing the status of the priority doesn't make this complex work happen any quicker. There is no value in edit-warring over Bugzilla statuses, so I'm going to leave this as is, but please don't make changes like this.",1375301261,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I'm upgrading this to ""normal"" since it's listed at #4 on https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Known_problems and I'm not seeing any good case for low/lowest made here.",1375243706,PHID-USER-und42bbibe2hhp4rbyu3,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"**joedecker** wrote:
+
+This is quite serious for slow connections.",1372953307,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Ah, the disappearing double-links are Bug 50731.",1372952558,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Ah, I see the ""edit|edit source"" links on sections have turned back into just ""edit"" links, which edit the wikitext. Thank you :-)",1372936067,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I appreciate the VE is a hard problem  - but now you have an interface that *lies* to the user. It claims visual section editing is possible, but the PM for the VE has stated this functionality will not be funded.
+
+So, is the interface lying to the user this bug, or should it be a separate bug?
+
+If lying to the user is considered a feature, what is it for?",1372922447,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Oh, and sorry to be pedantic, but in the original context, ""marginal utility"" was not referring to a specific semi-solution as far as I can see:
+
+>> I don't seem to be able to section edit with VisualEditor.
+> To edit a section, we would need to get its HTML from Parsoid - but a section
+isn't guaranteed to be balanced HTML ...
+> Coming up with a solution to this is would be a significant piece of
+engineering effort for marginal utility.
+
+Thank you for confirming now that you *do* see utility in stopping the waste of bandwidth and slowing of load time.  Even if you think it is too difficult.",1372852730,PHID-USER-und42bbibe2hhp4rbyu3,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"> the core developers of this are not intending to work on this issue any time soon
+That's exactly what befuddles me, and seems like a poor judgement.  If it's anywhere near as big a task as you envisage, then I can't expect a volunteer to take it up.  So I conclude that realistically it will never be done.
+
+> having the entire document available, but just not editable
+Ok, I agree that would be useless, possibly of negative value. You're right that this is not what I'm asking for.
+
+>Parsoid that loaded and edited only one section at a time would be a mammoth piece of work
+Obviously I'm not a mediawiki programmer, so I speak from ignorance here.  But I don't understand why Parsoid can't just be given a shorter piece of wikitext to parse, along with the section number it is starting at.  Since the old editor is quite capable of serving up a correct section of the wikicode to the user, I don't see why the same wikicode can't be given to Parsoid.  Please can you get a third and fourth opinion on the feasibility of this.  Someone in your team may be able to think of a way around the problems you envisage.
+
+> I've edited Wikipedia (and other wikis) since 2001, including over heroically-terrible connexions
+So have you now also tried VisualEditor on those heroically-terrible connections?  I'm willing to bet that you will feel the weight of this problem.
+
+>I cannot justify spending donor funds
+The whole goal of VisualEditor is to improve accessibility and the editing experience for lower-tech editors right?  Well, the sad truth is that low-tech and globally underrepresented editor communities are strongly correlated with low bandwidth access.  Section editing in a long article gives an order of magnitude speed gain to those editors.  If you cannot do this for the target audience, I fear that VisualEditor will not serve those who need it the most.
+
+I really hope you will discuss this with more people before confining it to the dustbin.",1372839855,PHID-USER-und42bbibe2hhp4rbyu3,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"
+> Solving what you're actually asking for (a form of VisualEditor/Parsoid that
+> loaded and edited only one section at a time) would be a mammoth piece of
+> work,
+> albeit with some usefuless as you describe.
+> 
+> > James, please try regular editing on a slow connection if you haven't done
+> > this before, I'm pretty sure you'll end up editing the section source.
+> 
+> I've edited Wikipedia (and other wikis) since 2001, including over
+> heroically-terrible connexions through the years; I am very aware of the
+> impact
+> that our current site has on low-bandwidth users, even without VisualEditor,
+> but I cannot justify spending donor funds to that extent when there are more
+> pressing demands on the resources of the VisualEditor team.
+
+My first thought is what were people thinking when they thought that using a visual editor to edit a whole page at a time would not slow things down a lot for many users? I am not a developer though, and hindsight is 20/20. 
+
+Whatever it costs to make a visual editor that edits a section at at time would be worth it. The WMF spends money on far less important things. I have been saying this for years. 
+
+I think millions of dollars more a year should be spent on developer salaries just for the visual editor, and the coordination of vast armies of volunteer developers to work on the visual editor. Another spending priority would be developer money for cross-wiki watchlists.",1372837803,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #34)
+> I can't believe that section editing is marked as a ""lowest priority""
+> ""enhancement""!
+
+""Enhancement"" means ""the software doesn't do this, and isn't as-written meant to do this""; it's not a judgement on whether it should.
+
+""Lowest priority"" means ""the core developers of this are not intending to work on this issue any time soon""; bugs are always open to other developers coming and working on them, which frequently happens.
+
+""Lowest"" is a very clear way of me marking the bug as something that can be taken up without fear of duplication of work by a developer new to the code. (This is known as avoiding ""cookie licking"".)
+
+> This is incredibly important to me.
+
+I appreciate that it is important to some editors, but I have to balance all requested features, changes and bugs with VisualEditor against one another, and in my judgement this is, relatively, an edge case.
+
+> The way it's currently set up wastes bandwidth and slows load time relative
+> to the old editor. Both of these are important when making a quick-fix edit.
+
+I agree with that; I recommend using the wikitext editor for exactly these use cases by power users if they prefer.
+
+> Hardly ""marginal utility"". 
+
+That specifically refers to finding a solution which you don't want.
+
+A simpler solution - involving having the entire document available, but just not editable except for the section the user asked for - is do-able, but in that case, the benefits you're looking for (low bandwidth, fast loading time, low load on local computers) would not be present; hence, marginal utility.
+
+Solving what you're actually asking for (a form of VisualEditor/Parsoid that loaded and edited only one section at a time) would be a mammoth piece of work, albeit with some usefuless as you describe.
+
+> James, please try regular editing on a slow connection if you haven't done
+> this before, I'm pretty sure you'll end up editing the section source.
+
+I've edited Wikipedia (and other wikis) since 2001, including over heroically-terrible connexions through the years; I am very aware of the impact that our current site has on low-bandwidth users, even without VisualEditor, but I cannot justify spending donor funds to that extent when there are more pressing demands on the resources of the VisualEditor team.
+
+> I'm quite supportive of visual editor in general, but if this is not going
+> to be fixed, I may have to turn back.
+
+I'm sorry that that is the case, and hope that it does not come to that. Sorry if my explanation here is insufficient.",1372812826,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I can't believe that section editing is marked as a ""lowest priority"" ""enhancement""!  This is incredibly important to me.  The way it's currently set up wastes bandwidth and slows load time relative to the old editor.  Both of these are important when making a quick-fix edit.  Hardly ""marginal utility"".  James, please try regular editing on a slow connection if you haven't done this before, I'm pretty sure you'll end up editing the section source.  I'm quite supportive of visual editor in general, but if this is not going to be fixed, I may have to turn back.",1372805196,PHID-USER-und42bbibe2hhp4rbyu3,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,%%%*** Bug 50592 has been marked as a duplicate of this bug. ***%%%,1372793232,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Just a note (for users not following the other bugs) that we have just merged a change along the lines of bug 49666 - there will be both an ""edit"" and an ""edit source"" link on every section, with the edit link taking the user into VisualEditor, scrolled down to that section.
+
+This enhancement request (to have VE appear just for a section within a wider page) is not impossible, and we're keen to explore what impact it has, but very hard, and blocked on Parsoid's HTML being used as the basis for MW's read pages, so may take some time.",1372281418,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,Related URL: https://gerrit.wikimedia.org/r/69984 (Gerrit Change I4b9c47fd65a700a81c880144247fec524edff7e5),1371931754,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #18)
+> I commented at
+> http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/
+> Feedback#Now_unable_to_edit_sections_by_old_method
+> that it would be ideal to have section-edit links for [edit] and [edit
+> source].
+> 
+>  ie.
+> Sandbox [edit]
+>  replaced with:
+> Sandbox [edit] [edit source]
+> 
+> I believe this would prevent a LOT of complaints in the short term, and it
+> would permit a lot of us to continue being active beta testers
+> (section-editing
+> is my most frequent type of edit), that it should be High priority, if at all
+> possible. Thanks.
+
+I have created this as bug 49666.",1371430370,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #25)
+> It would be wonderful if the ""edit source"" links or icons for sections also
+> showed up inside the Visual Editor. The Visual Editor could treat ""edit
+> source"" links or icons as uneditable links. But the link would still work. So
+> people could click ""edit source"" links or icons to open source editing of a
+> section.
+
+I have created this as bug 49665.",1371430207,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #20)
+> I read the discussion, and it seems nobody mentioned what i think is the
+> ""real""
+> bug here: we have the ""edit source"" link, that drops you back to wikitext
+> editor. The correct behavior for ve should obviously be to drop you to a
+> section edit if the hser entered edit state through an edit section link. 
+> 
+> Peace.
+
+I have created this as bug 49664.",1371429995,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Bartosz (comment 26). If I am reading bug 43133 right it sounds way too complicated. What I am suggesting is a simple ""edit source"" link to source mode editing of a section. Nothing fancy like floating windows, etc. tied in any way to the Visual Editor. 
+
+One clicks out of the Visual Editor altogether. This means that edits to the source wikitext in a section are treated the same no matter how one got to that wikitext edit window. This avoids integration conflicts, additional edit conflicts, or anything complicated. 
+
+Same for clicking on stuff Visual Editor can't edit. One is sent to source mode for the section where that stuff is found. Nothing more. 
+
+For transcluded templates one still has to go to the bottom of the source-mode edit window for the whole page. That is where the list of transcluded templates is found. It would be nice if one could see such a list at the bottom of source-mode edit windows for sections too.",1371347020,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Timeshifter, this sounds very much like what is described at bug 43133.",1371343969,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I like kipod's ideas (comment 22). I think to more fully support section editing means to make it easy to choose either editor at any time. 
+
+Let me explain. If the Bartosz patch is implemented (comment 24), or some variation of it, there will be ""edit"" and ""edit source"" links or icons on every section. 
+
+It would be wonderful if the ""edit source"" links or icons for sections also showed up inside the Visual Editor. The Visual Editor could treat ""edit source"" links or icons as uneditable links. But the link would still work. So people could click ""edit source"" links or icons to open source editing of a section. 
+
+People could go to source mode editing at anytime, even from inside the Visual Editor. That would be so convenient and so useful. 
+
+Later on, this functionality could be extended to anything the Visual Editor can't edit. People could click on templates, tables, etc. inside the Visual Editor and go directly to source mode editing of that section. Or they could right-click templates, tables, etc. to go to a new tab in source mode for that section.",1371341581,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I submitted the patch above to show two links side-by-side, in the form of ""[edit] [edit source]"", similarly to how the article tabs are done.",1371319506,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,Related URL: https://gerrit.wikimedia.org/r/68868 (Gerrit Change I13bbb9549c999bb7301bbcf530706a813184425d),1371319421,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #21)
+> (In reply to comment #20)
+> > I read the discussion, and it seems nobody mentioned what i think is the
+> > ""real""
+> > bug here: we have the ""edit source"" link, that drops you back to wikitext
+> > editor. The correct behavior for ve should obviously be to drop you to a
+> > section edit if the hser entered edit state through an edit section link. 
+> > 
+> 
+> It does do so (in its own way). If you click a section-edit link, it
+> currently
+> enters VE edit-mode, and scrolls down to the section you clicked on, and
+> places
+> the cursor at the beginning of the section-header.
+
+
+no it doesn't. what i meant is that if you click on the ""edit"" section link, and then see something that requires wikitext editing and click ""edit source"", you are dropped into ""old"" editor _for the whole page_. this means that there is no way to execute the old ""section edit"" in the wikitext editor. removing this existing functionality is a regression, and fixing it should be easy.
+
+""fixing it"" meas that if you open the editor through a ""section edit"" link and then press ""edit source"", you will be in the exact same state as someone who has VE disabled and pressed the edit section link.
+
+failing to fix this causes editors to disable VE (i know for a fact that i am not the only one who disabled VE because of this very reason).
+
+peace.",1371315010,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #20)
+> I read the discussion, and it seems nobody mentioned what i think is the
+> ""real""
+> bug here: we have the ""edit source"" link, that drops you back to wikitext
+> editor. The correct behavior for ve should obviously be to drop you to a
+> section edit if the hser entered edit state through an edit section link. 
+> 
+
+It does do so (in its own way). If you click a section-edit link, it currently enters VE edit-mode, and scrolls down to the section you clicked on, and places the cursor at the beginning of the section-header.",1371313187,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I read the discussion, and it seems nobody mentioned what i think is the ""real"" bug here: we have the ""edit source"" link, that drops you back to wikitext editor. The correct behavior for ve should obviously be to drop you to a section edit if the hser entered edit state through an edit section link. 
+
+Peace.",1371301719,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #17)
+> (In reply to comment #16)
+> > Matthew. You are incorrect. There has been a recent change. 
+> 
+> You're right that the section editing default has changed for people who
+> opted
+> in to VE.
+> 
+> However, if you've never changed any editing preferences (most registered
+> users), you are still using the old editor by default.  That will change,
+> assuming the random test works well and VE continues to improve.
+
+I think Timeshifter means the ""which will soon be all users"" part, and I agree that it would be very unfortunate. Quiddity's solution seems like the best one, and IMO should be implemented before the A/B test on en.wp.",1371288142,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"I commented at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Now_unable_to_edit_sections_by_old_method
+that it would be ideal to have section-edit links for [edit] and [edit source].
+
+ ie.
+Sandbox [edit]
+ replaced with:
+Sandbox [edit] [edit source]
+
+I believe this would prevent a LOT of complaints in the short term, and it would permit a lot of us to continue being active beta testers (section-editing is my most frequent type of edit), that it should be High priority, if at all possible. Thanks.",1371264453,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #16)
+> Matthew. You are incorrect. There has been a recent change. 
+
+You're right that the section editing default has changed for people who opted in to VE.
+
+However, if you've never changed any editing preferences (most registered users), you are still using the old editor by default.  That will change, assuming the random test works well and VE continues to improve.",1371259513,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Matthew. You are incorrect. There has been a recent change. 
+Please read comment 13 by James Forrester above. Here is the relevant part: 
+
+""as of today, we have switched over to the 'beta' behaviour for VisualEditor in a number of regards, including section edit links - i.e., default behaviour for users with VisualEditor (which will soon be all users) is that section edit links will take you into VisualEditor, scrolled to that section, with the cursor at the start of it.""",1371257851,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #14)
+> Many registered editors don't edit enough to know much about preferences. 
+> ...
+
+Editors who haven't changed their preferences are still using the wikitext editor.
+
+> Worst of all, what was once an interesting option has now become an imposed
+> encumbrance. There is no way to edit in source mode now without effort.
+> Registered editors are forced to use VE. They can only opt-out of VE section
+> editing. They must go here: 
+> [[Special:Preferences#mw-prefsection-editing]]
+> 
+> Please return section editing of source wikitext as the default. Make this VE
+> section editing gimmick the option in preferences. Make it opt-in, not
+> opt-out. 
+
+It is opt-in.  So far, the defaults have not changed in any way.  You can sign up for a temporary test account and see for yourself.
+
+If you don't change any preferences, editing remains wikitext only.  And you can change back (and forth) at any time.  That means the defaults are not being imposed on anyone.
+
+I understand your point.  VisualEditor is a work in progress.  However, it's a work in progress that's currently 100% opt-in, and James has already said he will consider two section edit links.",1371256729,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Many registered editors don't edit enough to know much about preferences. This is a bad idea. There are already many complaints here: 
+[[Wikipedia:VisualEditor/Feedback]]
+
+This could cause many editors, who already do not edit much, to edit less because their edits get reverted soon after using Visual Editor. VE messes up many things. I have seen it myself, and so I do not use VE. I have to check a WHOLE-PAGE preview diff for errors it inserts before I save some other minor thing I edited. Minor typos and other things that used to take me a few seconds to fix now take a long time with the Visual Editor. 
+
+Visual Editor needs to edit SECTIONS, too. Not the whole page. So this fix is not a fix. Visual Editor still does not support section editing. It still only edits the whole page. 
+
+Worst of all, what was once an interesting option has now become an imposed encumbrance. There is no way to edit in source mode now without effort. Registered editors are forced to use VE. They can only opt-out of VE section editing. They must go here: 
+[[Special:Preferences#mw-prefsection-editing]]
+
+Please return section editing of source wikitext as the default. Make this VE section editing gimmick the option in preferences. Make it opt-in, not opt-out. 
+
+The WMF does not have anywhere near a consensus or approval or any other type of community process sanction that justifies imposing beta VE. Especially when it is as buggy and beta as it is now. VE was actually an interesting option until this latest forced imposition of beta VE.",1371255945,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #12)
+> OK. Now that I finally get it, and see that everyone (logged in or not)
+> currently gets source editing of sections, let us not remove section editing
+> of source wikitext when VisualEditor is fully implemented! That would make many
+> editors very unhappy.
+
+Just to update on this point: as of today, we have switched over to the 'beta' behaviour for VisualEditor in a number of regards, including section edit links - i.e., default behaviour for users with VisualEditor (which will soon be all users) is that section edit links will take you into VisualEditor, scrolled to that section, with the cursor at the start of it.
+
+For the mean time (until VisualEditor is out of beta, when it will be much less likely that users will want to use wikitext editor often), there's a user preference (defaulted to off) that will redirect these section edit links back to the wikitext editor; this is in Special:Preferences > Editing > Beta features.
+
+I'm open to seeing if there's a way of giving people two section edit links without being confusing in the medium/long term, but that's a discussion for later. :-)",1371180404,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"OK. Now that I finally get it, and see that everyone (logged in or not) currently gets source editing of sections, let us not remove section editing of source wikitext when VisualEditor is fully implemented! That would make many editors  very unhappy. 
+
+I sometimes like to open up a section in a new tab for editing. So I can switch between tabs to alternate between how the section currently looks, and how my preview looks. This also helps me in finding stuff in the wikitext. I can use browser find in both tabs to help me find where I need to edit. 
+
+This can be very necessary when editing references, tables, navigation boxes, image captions, and other such wikitext. Images that are right-floating, for example, can be difficult to find in the wikitext otherwise.",1371076044,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #10)
+> OK. I see that section editing is currently enabled for anonymous users too
+> on Wikipedia. I am almost always logged in, and so I must have been confused by
+> the preference ""Enable section editing via [edit] links"".
+
+That is in fact the preference, but it's checked by default (as well as always on for anons).",1371073574,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"OK. I see that section editing is currently enabled for anonymous users too on Wikipedia. I am almost always logged in, and so I must have been confused by the preference ""Enable section editing via [edit] links"". I see now that it is about the URLs. See 
+[[Help:Section#Section_editing]].
+
+I would hate to lose section editing of source wikitext if VisualEditor is enabled for section editing. That would be a serious step backwards for the reasons I and others have discussed.",1371073277,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #8)A section
+> preview is much faster. I have been editing Wikipedia since 2005, and at one
+> point I had forgotten that section editing is not a given for all editors. We
+> are wasting a lot of editors time by not enabling it by default.
+
+Wikitext section editing is enabled by default.",1371073015,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"See discussion here:
+[[Wikipedia:VisualEditor/Feedback]] and go to the section titled ""VisualEditor not enabled for section editing"". That talk section will end up in the archives eventually. Do an archive search then. 
+
+Load time will still be an important factor with VisualEditor. That reason alone justifies continuing with section editing. 
+
+If VisualEditor is enabled for section editing, then it will also be necessary to enable ""edit source"" somehow for sections too. So people can choose between the two. Just like at the top of page. If the developers are worried about cluttering up each section with both ""edit"" and ""edit source"" links, then there needs to be some icon next to ""edit"" that will be the link for ""edit source"". The clickable icon will have a popup tooltip saying ""edit source"".
+
+I use section editing for almost all my editing, whether in short or long articles. Do you have section editing enabled? If not, you might try it. It speeds up editing immensely for me, and many others. See: 
+[[Special:Preferences#mw-prefsection-editing]] and ""Enable section editing via [edit] links"". It would be better if it were enabled by default for all editors, whether logged in, or not. 
+
+Many people will still use wikitext source editing. There will long be a need until every single bug is fixed in VisualEditor. I can tell you this from years of experience with the Wikia visual editor. Many, if not most, regular editors on Wikia avoid it due to its continuing bugginess. 
+
+When using source editing I don't know why anybody would want to wade through paragraphs of irrelevant stuff to get to the paragraph and section one is interested in editing. Especially if you make multiple edits, and use multiple previews. Why wait long periods of time for full-page previews? A section preview is much faster. I have been editing Wikipedia since 2005, and at one point I had forgotten that section editing is not a given for all editors. We are wasting a lot of editors time by not enabling it by default. Since there are fewer and fewer editors we need to make their editing more and more efficient.
+
+Anonymous editors do much of the editing on Wikipedia, and many will prefer to edit the source wikitext for all the reasons previously discussed. Many anonymous editors are experienced Wikipedia editors, and will not tolerate having to only use VisualEditor. So never get rid of the option for source editing. Let me repeat: WIKIA, WIKIA, WIKIA. Bugs are seemingly never-ending and ever-growing with visual editors.",1371065466,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #6)
+> One of the things I'm pondering is if we should relabel the edit section
+> links to have two links, one to VE and the other to wikitext. Possibly ""[_edit_
+> _*_]"" or somesuch.
+
+I think that might be too much clutter when VE rolls out to everyone.  But while it's opt-in, it will definitely encourage me to test it, since I use the edit section link a lot.",1369114201,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #5)
+> Err, whoops. Sorry, yeah, completely missed that paragraph.
+
+:-)
+
+> If the default editor behavior is a switch that controls parts of the
+> interface like this (I didn't realize that), is this testable now anywhere?
+> A Labs wiki or something?
+
+No; we should do that.
+
+One of the things I'm pondering is if we should relabel the edit section links to have two links, one to VE and the other to wikitext. Possibly ""[_edit_ _*_]"" or somesuch.",1368980861,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #4)
+> I mentioned it too, you know :-) - see:
+> 
+> (In reply to comment #2)
+> | The behaviour in VisualEditor when running as the default editor is for the
+> | edit section links to take you into VE for the entire page, with the view
+> | moved down to the anchor of that section (note, this is not how it appears
+> | right now on the various Wikipedias, but will be once they have the 'beta'
+> | enabled).
+
+Err, whoops. Sorry, yeah, completely missed that paragraph.
+
+If the default editor behavior is a switch that controls parts of the interface like this (I didn't realize that), is this testable now anywhere? A Labs wiki or something?",1368848488,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #3)
+> Krinkle briefly mentioned an idea where section edit links might load the
+> full VisualEditor form and then jump down to the specific section. This might
+> be an approach to consider.
+
+I mentioned it too, you know :-) - see:
+
+(In reply to comment #2)
+| The behaviour in VisualEditor when running as the default editor is for the
+| edit section links to take you into VE for the entire page, with the view
+| moved down to the anchor of that section (note, this is not how it appears
+| right now on the various Wikipedias, but will be once they have the 'beta'
+| enabled).",1368825534,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"There must be a recognition that editing large articles is burdensome and that section editing has (had) _enormous_ value.
+
+Even with JavaScript disabled, the parser continues to take a significant amount of time to parse a large article. And while modern browsers on modern hardware don't have as many issues, rendering large articles can also be taxing.
+
+VisualEditor adds to this burden by piling on a lot of JavaScript. The idea that wanting to edit only a section of [[GE]] or [[Iraq War]] stems from wanting to skip past confusing wikitext or avoid edit conflicts misses the point, I think. Though I realize that VisualEditor uproots many principles of the current editing workflow/paradigm.
+
+Krinkle briefly mentioned an idea where section edit links might load the full VisualEditor form and then jump down to the specific section. This might be an approach to consider.",1368825331,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"(In reply to comment #0)
+> I don't seem to be able to section edit with VisualEditor.
+
+There are three issues here:
+* To edit a section, we would need to get its HTML from Parsoid - but a section isn't guaranteed to be balanced HTML, for example (commonly-used):
+
+{|
+! Foo !! Bar
+|-
+=== Section 1 ===
+|-
+| Foo || bar
+=== Section 2 ===
+|-
+| Foo || bar
+|}
+
+Coming up with a solution to this is would be a significant piece of engineering effort for marginal utility.
+
+* The reasons we brought in section-editing originally were two-fold - to skip past confusing wikitext in other areas to find the item you actually wanted to edit (not an issue in the context of VisualEditor), and to avoid edit conflicts using the page-based diffs at the time (not an issue for ~ 7 years since Tim re-wrote the diff tool).
+
+* Editing by section blocks users from editing other areas at the same time that the notice flaws in after they've entered editing, for very limited added-value.
+
+
+The behaviour in VisualEditor when running as the default editor is for the edit section links to take you into VE for the entire page, with the view moved down to the anchor of that section (note, this is not how it appears right now on the various Wikipedias, but will be once they have the 'beta' enabled).
+
+I'm not convinced that this is a WONTFIX, but I'm similarly not convinced that we should spend our time fixing this rather than, say, making VisualEditor and Parsoid work on Wikisource, or other things we could be doing with our limited resources.",1368814282,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+[Epic] Support editing parts of a page in VisualEditor-MediaWiki,"Thoughts:
+
+It strikes me that this might not be overly difficult - if VE is just using H<n> elements to represent sections anyway, then it should be relatively simple to change the edit URL to ""javascript:"", and add some JavaScript events to them that call the VE setup and, once it's done, brings the specified section to the top of the user's screen.
+
+I won't mark this as easy, because I don't think it is. I wish we had an ""intermediate"" keyword.",1368812060,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-wdo3c45xgv7mte4en6az,task_subcomment,NA
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on","How to reproduce:
+
+1. Enable the ""Mark all edits minor by default"" option in the preferences.
+2. Edit a page in the VisualEditor.
+3. Press ""Review and save"", then ""Looks good to me"".
+4. The edit summary entering bubble appears.
+
+Observed:
+
+* The ""This is a minor edit"" box is not checked.
+
+Expected:
+
+* The ""This is a minor edit"" box is checked.
+
+Comment: The saved revision IS correctly marked as minor. It's just the check box that appears incorrectly.
+
+GWT scenario for Cucumber:
+Given that I am editing an article while the minordefault preference is on
+When I am saving the article
+Then the ""This is a minor edit"" box is checked
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1368250560,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-lxnhaohtjgjw5zamlish,task_description,resolved
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on",Merged into master; will go out with wmf5.,1368638598,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lxnhaohtjgjw5zamlish,task_subcomment,NA
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on",Related URL: https://gerrit.wikimedia.org/r/63844 (Gerrit Change Ib5cdcb9433be5ff7b9179d3833f42e5c3453285a),1368621284,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lxnhaohtjgjw5zamlish,task_subcomment,NA
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on","(In reply to comment #1)
+> You know, if minoredit preference was killed, this wouldn't be an issue...
+
+I couldn't agree more :)",1368250904,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-lxnhaohtjgjw5zamlish,task_subcomment,NA
+"VisualEditor: ""This is a minor edit"" is not auto checked in save dialog if the ""minordefault"" preference is on","You know, if minoredit preference was killed, this wouldn't be an issue...",1368250852,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-lxnhaohtjgjw5zamlish,task_subcomment,NA
+Allow extensions to automatically generate jsduck documentation on doc.wikimedia.org,"Core now has jsduck documentation on https://doc.wikimedia.org/mediawiki-core/master/js/ .  It would be useful to provide a standardized mechanism for extensions to have their jsduck documentation automatically added under doc.wikimedia.org as well.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48244",1368220260,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-cci6rbbarnfeumyquutn,task_description,resolved
+Allow extensions to automatically generate jsduck documentation on doc.wikimedia.org,"Marking this fixed.  The general functionality is there.  For GuidedTour specifically, https://gerrit.wikimedia.org/r/#/c/118428/ and https://gerrit.wikimedia.org/r/#/c/118426/ are in progress.",1394685438,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-cci6rbbarnfeumyquutn,task_subcomment,NA
+Allow extensions to automatically generate jsduck documentation on doc.wikimedia.org,"It looks like VisualEditor and MultimediaViewer are both doing so now.  i don't know if they're one-offs or there's a general process.
+
+However, I would like to do the same for GuidedTour.  Currently, we have it at http://growthdoc.wmflabs.org/GuidedTour/ .",1393639541,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-cci6rbbarnfeumyquutn,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,"Wikitext edit has page title ""Editing Foobar"", as opposed to reading-mode's ""Foobar"". For people with a number of tabs open, it'd be great for them to get a handle on where they are by updating the window title to prepend ""Editing "" to it (and remove it on save).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1368044160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jhka5utrurrafo6ytxhv,task_description,resolved
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,"Yes, re-using 'editing' & 'creating' messages.
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > And 'Creating'.
+> 
+> Ah, yes. Presumably they're existing MW messages to steal, avoiding
+> duplication
+> of i18n efforts?.",1368885209,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,Merged; will go out with wmf5.,1368885131,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,Related URL: https://gerrit.wikimedia.org/r/64325 (Gerrit Change I9dcc8ec2c37a7ff9cff6cedb7bdb1fed1bdc4deb),1368807251,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,"(In reply to comment #1)
+> And 'Creating'.
+
+Ah, yes. Presumably they're existing MW messages to steal, avoiding duplication of i18n efforts?.",1368804528,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+VisualEditor: Over-ride browser window/tab title to show you're in editing mode,And 'Creating'.,1368804345,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-jhka5utrurrafo6ytxhv,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"It would be helpful to have a built-in method in Scribunto/Lua that allows retrieving a list of the categories used on a page.
+
+For example, <https://en.wikipedia.org/wiki/Einar_Schleef> would return a list that includes:
+
+* German dramatists and playwrights
+* 1944 births
+* 2001 deaths
+
+As these categories are included on this page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**: {T20596}",1367867880,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_description,resolved
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@SD0001 Thank you! One more hesitant suggestion: I was looking for something to link the term ""edit notices"" to, and found the page https://www.mediawiki.org/wiki/Manual:Interface/Edit_notice - I wonder if it would be worth adding an example there for this new capability? (~~Or perhaps the Scribunto requirement makes this unfeasible?~~ EDIT: (I'm probably wrong here, I see it's default with 1.34+))",1723770787,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@SD0001 Thank you! One more hesitant suggestion: I was looking for something to link the term ""edit notices"" to, and found the page https://www.mediawiki.org/wiki/Manual:Interface/Edit_notice - I wonder if it would be worth adding an example there for this new capability? (Or perhaps the Scribunto requirement makes this unfeasible?)",1723768444,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@Quiddity I have documented the new property in the [[https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Title_objects|Lua reference manual]]. Suggested blurb for tech news:
+
+> Page categories are now accessible in Lua modules via `categories` property of [[https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Title_objects|mw.title objects]]. This enables use cases like category-specific editnotices.",1723746686,PHID-USER-52k2lmr37woy42l6kdmv,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@SD0001 Hi, I'm wondering if you're able to help answer any of the requests in my comment above? (Or anyone familiar, who sees this!) But I also guess you may still be traveling/recovering/catching-up from Wikimania, so no rush if it needs to wait a week or two! Thanks.",1723675356,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Hi, this sounds great, and thank you Pppery for adding the user-notice tag. Two requests, and a note:
+1. Please could someone **suggest some wording for a Tech News entry**? -- I've read the comments above, and the linked gerrit patch, but I'm still uncertain how to clearly describe the new function(s?) that will be available to editors. 
+  * Here's a rough-guess attempt (and structure example): 
+  * ""Editors can now use Lua code to get a listing of categories used in a page. This enables [example use-case?]. The [link]documentation has details and examples[/link] of how this new function can be used.
+2. Please could someone write (or link us to any existing) **permanent documentation for the new function(s)**? -- I.e. It seems like it would be good to have a page-section on MediaWiki-wiki for any details and examples. That will also make it possible to have a shorter Tech News entry that simply links to those details/examples!
+* Note: I see the gerrit commit-msg says ""//This enables category-specific editnotices (T85372) and other use-cases.//"" -- Maybe that task needs an update (of some sort)? Or to be highlighted in the docs/TN entry if it's already available due to this task's resolution?
+Thanks!",1723058925,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Change #919459 **merged** by jenkins-bot:
+%%%[mediawiki/extensions/Scribunto@master] Expose page categories to Lua%%%
+https://gerrit.wikimedia.org/r/919459",1723049408,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I struggled to get proxying to work on the second test wiki I created, but I was able to still test the specific use case of category editnotices on the first test wiki and that functions correctly. We probably need more use cases tested before the change can be implemented.",1714666635,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I struggled to get proxying to work on the second test wiki I created, but I was able to still test the specific use case of category editnotices and that functions correctly. We probably need more use cases tested before the change can be implemented.",1714666610,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by Awesome Aasim using patch(es) linked to this task:
+[[ https://patchdemo.wmflabs.org/wikis/29fac70752/w ]]",1714661371,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,Okay I will just initialize a new wiki with proxying from EN Wikipedia.,1714661181,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9746242, @Awesome_Aasim wrote:
+> One can you enable proxying articles from en.wiki?
+
+No, I don’t think it’s possible to enable proxying after creating the patch demo. If important, you can create a new patch demo with proxying enabled; otherwise, just copy the necessary pages with an edit summary linking to the enwiki page.
+
+> And second, can you give the test account admin and interface-admin so I can test a specific use case (category based editnotices) with the Lua categories?
+
+You can log in with the user name `Patch Demo` and the password `patchdemo1` and give yourself admin rights (or just use that account directly). This is a standard account that works on any Patch Demo wiki.",1714139068,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@Novem_Linguae I created a test account called ""Test"" on the test wiki you created on patch demo. I want to know if you can do a couple of things: One can you enable proxying articles from en.wiki? And second, can you give the test account admin and interface-admin so I can test a specific use case (category based editnotices) with the Lua categories?",1714074781,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"There is very much an error with this. Page is not in A so gets put in A, but now that the page is in A the parser function says that we are now in A and does not category link. This is a less obvious self reference loop. The page should detect that it is getting categorization information about itself, do a parse, and after recursing one down say ""template loop detected: A"" and throw the page into ""pages with template loops"". Something similar to what happens when you construct an actual template loop like this:{F47620082}",1713574509,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9730478, @Awesome_Aasim wrote:
+> https://patchdemo.wmflabs.org/wikis/878c4bb105/wiki/A says that the page is in A, even though it clearly is not from the category bar. This might be the ""unstable parses"" that matmarex was alluding to.
+
+I don't see an issue. By the logic you have, page should be categorised to Category:A if it wasn't already in it. Once this is done, the page is //now// in Category:A and is indicated as such. 
+
+I think we have established already that there are no ""unstable parses"". Purging the page any number of times doesn't change its categorisation. ",1713559024,PHID-USER-52k2lmr37woy42l6kdmv,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Thank you. I just tested out the categories and specifically the undefined behavior which would result in a template loop for any other parser function.
+
+https://patchdemo.wmflabs.org/wikis/878c4bb105/wiki/A says that the page is in A, even though it clearly is not from the category bar. This might be the ""unstable parses"" that matmarex was alluding to.
+
+Can we maybe find a way to detect these template loops and throw an error in the Lua code if one occurs?",1713550469,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,@Awesome_Aasim You can do so: https://toolhub.wikimedia.org/tools/patchdemo,1712727381,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Test wiki **created** on [[ https://patchdemo.wmflabs.org | Patch demo ]] by Novem Linguae using patch(es) linked to this task:
+[[ https://patchdemo.wmflabs.org/wikis/878c4bb105/w ]]",1712709797,PHID-USER-jab5bp3ivtzmobfdxoa7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,Might we be able to get this on a test wiki so we can ensure that there aren't any problems with the patch?,1712694065,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9595853, @SD0001 wrote:
+> The proposed patch reads the categories from the db, sidesteping any ""cross-communication"" concerns. The tradeoff is that the categories reflect the ones produced by the last parsed version of the page, so if someone adds some categories and invokes this function on the current page in the same edit, the page is temporarily saved with lua returning outdated result, which gets fixed on the next purge or edit[0]. 
+
+I view this as a feature, not a bug -- it breaks a possible cycle and avoids doing a full parse of the page just to extract categories.",1711390959,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,I am also going to backtrack from what I was saying about the template loop issue. Instead of forbidding categorization... why not just add the page to the Category:Pages with template loops category?,1710298174,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"@SD0001 IMHO I think any effort to expose categories to Lua is better than nothing at all.
+
+A more robust editnotice load module I worked on testwiki https://test.wikipedia.org/wiki/Module:Editnotice_load uses some hackery to get the categories from the (preprocessed) wikitext, it takes forever to load on large pages, like on this fork of Taylor Swift from enwiki: https://test.wikipedia.org/w/index.php?title=Taylor_Swift&action=edit
+
+I don't think the result is even cached when used in interface messages, is it...",1710298027,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"The proposed patch reads the categories from the db, sidesteping any ""cross-communication"" concerns. The tradeoff is that the categories reflect the ones produced by the last parsed version of the page, so if someone adds some categories and invokes this function on the current page in the same edit, the page is temporarily saved with lua returning outdated result, which gets fixed on the next purge or edit[0]. 
+
+However, per @aaron on gerrit:
+> It's strange for this to use the categories of the previous parsed revision. It's also not well defined to use the currently-being-parsed revision either.
+>
+> It's one thing to depend on page existence, current revision text, or current revision metadata, but depending on the parsed current revision of another page (let alone the same page) to generate the parsed output feels overly ""higher-order"".
+
+This is something which does seem unprecedented in MediaWiki, although I'm not certain if it's a bad thing. As it stands, there are a lot of Scribunto feature requests where the only straightforward implementation is to use db data generated by the last parsed revision. 
+
+| **Feature** | **Ticket** | **Workaround** |
+| Reading categories (this ticket) | T50175 | [[https://en.wikipedia.org/wiki/Module:Mainspace_editnotice|Module:Mainspace_editnotice]], function blp_notice |
+| Reading local short description | T216356 | [[https://en.wikipedia.org/wiki/Module:GetShortDescription|Module:GetShortDescription]] |
+| Checking if page is a disambiguation page | T71441 | [[https://en.wikipedia.org/wiki/Module:Disambiguation|Module:Disambiguation]] |
+ 
+Current workarounds generally try processing the raw getContent(), which is worse.
+
+----
+[0]: Even this minor annoyance is not unfixable. I earlier tried fixing it by using VARY_REVISION output flag. This doesn't quite work as it causes a re-purge before the link tables are updated. Instead, we could use a custom parser output flag which triggers the LinksUpdateComplete hook to re-purge once the link table is up to date.
+",1709558536,PHID-USER-52k2lmr37woy42l6kdmv,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I like the idea of forbidding Scribunto output from adding new categories once categories have been read, but the implementation of that could be fraught.  Parsoid will parse the scribunto code as a separate ""top level document"" so in theory we could zero-out ParserOutput::$mCategories() after the Scribunto code has returned. This still works even if the categories were placed in ParserOutput by parsing `[[Category:Foo]]` as wikitext.  Seems like a pretty big hammer, though, for a problem we'd hope wouldn't arise in practice.
+",1702407148,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9164846, @Awesome_Aasim wrote:
+> Here is a solution: only fill getCategories() for the page all the way up to the point of execution.
+
+The problem is that the page may not be parsed in the same order each time, so this “all the way up to the point of execution” may change from parse to parse, without any edits.
+
+> then we can also get that in the following scenario. Suppose we have the page ""Foo"" check to see if ""Foobar"" is in the page ""Bar"" and if so does nothing, and if not writes ""Foobar"". Now say ""Bar"" does the same for ""Foo"". Now the order of execution determines which page has ""Foobar"" and which one does not.
+
+Actually, not:
+* `mw.title:getContent()` returns the raw wikitext, without any parsing. This either contains or doesn’t contain `Foobar`; this fact can be changed only through an edit.
+* `frame:expandTemplate()` uses the parser to get the preprocessed content, and the parser errors out, adding the page to [[https://en.wikipedia.org/wiki/Category:Pages_with_template_loops|Category:Pages with template loops]], when it notices this kind of recursion.",1697358959,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9164846, @Awesome_Aasim wrote:
+> There might actually be a better solution than this. If a module accesses category information, just prohibit population of categories by that module period. That is, if the module is like the first two scenarios, it would just do nothing and maybe add the module to a special page. This is something that can be checked after the module is done executing. For now, this might be a good solution until some way to detect these two scenarios is reliably determined. It would allow for category editnotices to work while preventing the two scenarios above from arising.
+
+Categories are added by literal category links in the wikitext emitted by a module, unfortunately. Disabling categories might be fairly easy to do for any invoked module function that generates a complete category link that goes straight into the wikitext of the article, because it could be as easy as a search and replace in the parser code that receives the output of the module function, but a module can be used to generate only part of a category link, like `[[Category:{{#invoke:example|emit_category_that_page_is_not_in}}]]`. But there are often be multiple layers of expansion past the module invocation, for instance when a template contains `{{#invoke:module name|function name|...}}`. Text generated by a module invocation could also be put into a template that then puts the text in a category link.
+
+I'm not familiar with the parsing infrastructure, but I imagine to solve some of these problems, the parser would have to track which 'contaminated"" text ultimately had something to do with invocations of modules that looked up category information for the current page, and in the final expanded text disable any category links that contain any of this contaminated text. That could be quite an invasive change to the parser because of all the levels of expansion that wikitext goes through. There would also be false positives, because a template or module can take in contaminated text but totally ignore it and just generate the same thing whether the contaminated text is there or not. This change could lead to annoying results: suppose a module that is widely used suddenly starts looking up categories when it doesn't need to; then any templates or modules that depend on the module would stop generating category links even though they didn't do anything wrong with the category information. Then editors would have to look through the dependency tree and figure out which module was the culprit for the suddenly disappearing category links.",1694639124,PHID-USER-ckzurwd36svqc4arsqvb,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9164846, @Awesome_Aasim wrote:
+> There might actually be a better solution than this. If a module accesses category information, just prohibit population of categories by that module period. That is, if the module is like the first two scenarios, it would just do nothing and maybe add the module to a special page. This is something that can be checked after the module is done executing. For now, this might be a good solution until some way to detect these two scenarios is reliably determined. It would allow for category editnotices to work while preventing the two scenarios above from arising.
+
+Categories are added by literal category links in the wikitext emitted by a module, unfortunately. Disabling categories might be fairly easy to do for any invoked module function that generates a complete category link that goes straight into the wikitext of the article, because it could be as easy as a search and replace, but a module can be used to generate only part of a category link, like `[[Category:{{#invoke:example|emit_category_that_page_is_not_in}}]]`. But there are often be multiple layers of expansion past the module invocation, for instance when a template contains `{{#invoke:module name|function name|...}}`. Text generated by a module invocation could also be put into a template that then puts the text in a category link.
+
+I'm not familiar with the parsing infrastructure, but I imagine to solve some of these problems, the parser would have to track which 'contaminated"" text ultimately had something to do with invocations of modules that looked up category information for the current page, and in the final expanded text disable any category links that contain any of this contaminated text. That could be quite an invasive change to the parser because of all the levels of expansion that wikitext goes through. There would also be false positives, because a template or module can take in contaminated text but totally ignore it and just generate the same thing whether the contaminated text is there or not. This change could lead to annoying results: suppose a module that is widely used suddenly starts looking up categories when it doesn't need to; then any templates or modules that depend on the module would stop generating category links even though they didn't do anything wrong with the category information. Then editors would have to look through the dependency tree and figure out which module was the culprit for the suddenly disappearing category links.",1694639064,PHID-USER-ckzurwd36svqc4arsqvb,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#9164846, @Awesome_Aasim wrote:
+> There might actually be a better solution than this. If a module accesses category information, just prohibit population of categories by that module period. That is, if the module is like the first two scenarios, it would just do nothing and maybe add the module to a special page. This is something that can be checked after the module is done executing. For now, this might be a good solution until some way to detect these two scenarios is reliably determined. It would allow for category editnotices to work while preventing the two scenarios above from arising.
+
+Categories are added by literal category links in the wikitext emitted by a module, unfortunately. Disabling categories might be fairly easy to do for any invoked module function that generates a complete category link that goes straight into the wikitext of the article, because it could be as easy as a search and replace, but a module can be used to generate only part of a category link, like `[[Category:{{#invoke:example|emit_category_that_page_is_not_in}}]]`. But there are often be multiple layers of expansion past the module invocation, for instance when a template contains `{{#invoke:module name|function name|...}}`. Text generated by a module invocation could also be put into a template that then puts the text in a category link.
+
+I'm not familiar with the parsing infrastructure, but I imagine to solve some of these problems, the parser would have to track which 'contaminated"" text ultimately had something to do with invocations of modules that looked up category information for the current page, and in the final expanded text disable any category links that contain any of this contaminated text. That could be quite an invasive change to the parser because of all the levels of expansion that wikitext goes through. There would also be false positives, because a template or module can take in contaminated text but totally ignore it and just generate the same thing whether the contaminated text is there or not. That could be a bit obnoxious if a module that is widely used suddenly starts looking up categories when it doesn't need to, any templates or modules that depend on the module could stop generating category links even though they didn't do anything wrong with the category information.",1694638874,PHID-USER-ckzurwd36svqc4arsqvb,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I kind of see the issue as well a little that Matmarex has put forth. It is the classical paradox of self reference. If the page populates Category:Foo when it is not in Category:Bar, and the page populates Category:Bar when it is in Category:Foo, then which category would be populated? It would require us to know the final execution state in order to further populate. Here is a solution: only fill getCategories() for the page all the way up to the point of execution.
+
+But then for two pages, we have the problem of timing. The order in which categories are populated would then depend on when the page was parsed. I can see how it can lead to ""unstable parses"" regarding categories, but then we can also get that in the following scenario. Suppose we have the page ""Foo"" check to see if ""Foobar"" is in the page ""Bar"" and if so does nothing, and if not writes ""Foobar"". Now say ""Bar"" does the same for ""Foo"". Now the order of execution determines which page has ""Foobar"" and which one does not.
+
+There might actually be a better solution than this. If a module accesses category information, just prohibit population of categories by that module period. That is, if the module is like the first two scenarios, it would just do nothing and maybe add the module to a special page. This is something that can be checked after the module is done executing. For now, this might be a good solution until some way to detect these two scenarios is reliably determined. It would allow for category editnotices to work while preventing the two scenarios above from arising.",1694632731,PHID-USER-bzspc5im4mzxblgdl3e7,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Although @Izno only mentions “cross-communication between templates”, I’m pretty sure he meant specifically templates transcluded on a page accessing output of templates transcluded at other parts of the same page – otherwise, it’s just a simple template transclusion, which was, is, and going to be, supported, of course. Templates transcluded on a page accessing output of templates transcluded at other parts of the same page is where issues come up: previews of parts of the page (e.g. sections or – in case of VisualEditor and other Parsoid-based things – individual templates) may be different from what a full-page parse produces, and parallel parsing of different parts of the page may cause race conditions.",1684739405,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Yes, I tested it. It works in editnotices; it did cause a template loop on the page itself yeah. But the main complaint from Izno seems to be about cross-template communication, not about accessing info about the current page; and this definitely works if the page given is not the current page.",1684731135,PHID-USER-3ffkgjb7rllliblvxdy2,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Did you test these? Unless you have countermeasures (is it possible at all?), or unless `{{FULLPAGENAME}}` isn’t actually the title of the current page (which is the case e.g. in edit notices), both `frame:expandTemplate` and `{{:{{FULLPAGENAME}}}}` would definitely cause infinite template recursion, not only potentially cause unstable parses.",1684656255,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#8865219, @Izno wrote:
+> `getContent` does not expand templates. I'm pretty sure the PHP implementation of `getCategories`
+
+`frame:expandTemplate` allows this though. In fact, just using e.g. `{{#invoke:string|find|{{:{{FULLPAGENAME}}}}|Category:X1}}`, you can check if the categories of the current (or any) page include X1 without even using Lua to get the page content. So this actually adds zero additional functionality (it just makes things faster, since transcluding the page is very slow to parse) and I don't think it actually needs any restrictions. The infinite loops mentioned should already be possible through this method.",1684626769,PHID-USER-3ffkgjb7rllliblvxdy2,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"There are also opportunistic limk updates of the page is ""dynamic"", but yes it is limited.",1684558154,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#8865315, @matmarex wrote:
+> Every time one of these pages are parsed, the state of its category will flip. This seems bad. As one side effect of this, I think everyone watching the pages will see a message about category changes on their watchlist. 
+
+... which should motivate one of those users to fix up the ungodly mess! This should only happen when the parse is a result of an edit though, as LinksUpdate isn't run otherwise.",1684557228,PHID-USER-52k2lmr37woy42l6kdmv,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,You can definitely already do this - e.g. make the category used depend on the current time or something. It does seem like this might make the problem worse though.,1684526427,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I see a slightly different problem – this feature may produce ""unstable"" parses. Consider the scenario:
+* Page A has a template that adds category X if another page B has a category Y
+* Page B has a template that adds category Y if page A does not have the category X
+Every time one of these pages are parsed, the state of its category will flip. This seems bad. As one side effect of this, I think everyone watching the pages will see a message about category changes on their watchlist. There may be other bad side effects.
+
+Even when it doesn't produce an infinite loop like this, you may end up with pages that may need to be parsed multiple times until they reach a stable state. This actually seems even worse. Imagine a vandalism that requires multiple pages to be purged in exactly correct order to be reverted.
+
+I don't know if that's necessarily a deal breaker, but I know that I wouldn't want to be responsible for this :)",1684512883,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"I dont think it falls afoul of that as long as it is reflecting DB state (current contents of categorylinks) and not currently parsed page.
+
+Although maybe shouldnt work for current page as that would be confusing",1684512620,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,">>! In T50175#8858120, @SD0001 wrote:
+> It doesn't enable communication between templates any more than getContent() already allows.
+
+`getContent` does not expand templates. I'm pretty sure the PHP implementation of `getCategories`
+
+```lang=php
+$page = MediaWikiServices::getInstance()->getWikiPageFactory()->newFromTitle( $title );
+...
+$categoryTitles = $page->getCategories();
+```
+
+gets all categories, which may be in templates. So I am pretty sure your statement is not a true statement.
+
+>  Besides, it's often useful - such as for citation modules to decide if dates should be formatted as dmy or mdy. 
+I am not concerned about its utility though -- I think the utility is pretty clear, enabling one path of cross-communication between templates, exactly as you say. I am instead raising a point that previous maintainers of Scribunto have drawn a line in the sand about, and which may have particular implications regarding this extension's support of Parsoid. The maintainers (whoever that may be since Anomie stopped participating in MediaWiki development) should decide whether it's a legitimate objection or not and whether I've identified the issue correctly or not, though if you don't think that's what those two lines are doing, I'm happy to be informed otherwise.",1684509817,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"It doesn't enable communication between templates any more than getContent() already allows. Besides, it's often useful - such as for citation modules to decide if dates should be formatted as dmy or mdy. ",1684311499,PHID-USER-52k2lmr37woy42l6kdmv,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"This change strikes me as enabling communication between separate templates, something which has been a no-no in this extension.",1684256661,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,"Change 919459 had a related patch set uploaded (by SD0001; author: SD0001):
+%%%[mediawiki/extensions/Scribunto@master] Expose page categories to Lua%%%
+https://gerrit.wikimedia.org/r/919459",1684006243,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,There's https://www.mediawiki.org/wiki/Extension:CategoryToolbox but I don't how suitable the code is.,1682931513,PHID-USER-3ffkgjb7rllliblvxdy2,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,%%%*** Bug 59111 has been marked as a duplicate of this bug. ***%%%,1397790380,PHID-USER-gljzp3uzec5ukggh6xdk,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+Scribunto/Lua should have a built-in method for retrieving categories used on a page,I'd just like to make the explicit suggestion that the categories be exposed be on title objects (see http://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Title_objects ) as they contain other information about a given page.,1397790345,PHID-USER-gljzp3uzec5ukggh6xdk,False,PHID-TASK-drv4cgq5tb5q7a75rjxp,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"many + signs
+
+Tested: 
+
+In OpenOffice, create a small table with text in cells a1, a2, b1, b2, c2. 
+
+Copy only the rows of the table. 
+
+Paste into VE. 
+
+* the view immediately in VE is of unusable information and some ""+"" characters apparently indicating cell boundaries. 
+
+Version:1.0StartHTML:0000000155EndHTML:0000000881StartFragment:0000000475EndFragment:0000000864➞➞➞➞➞➞➞➞➞➞➞➞➞a1➞➞➞b1➞➞➞➞➞➞➞➞➞➞a2➞➞➞b2➞➞➞c2➞➞➞
+
+* the view in the ""Review your changes"" panel is of a swath of white space with the contents of the table interspersed.
+
+* User tendency is to copy entire contents of rows, yielding many empty cells.  VE dutifully tracks these empty cells and displays an enormous number of ""+"" symbols in the immediate view and mostly empty space in the ""Review your changes"" view.
+
+* Upon save, no table is in the page when pasting from OpenOffice.
+
+Other anomalous results are reported when pasting from the Apple Pages application.  From another user: 
+
+""...number of cells didn't match the number of columns. Since they don't match, tried to delete the cells in order to recover the blank page, but they won't delete.""
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F11079}",1367866200,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-4fybw5go6fyidok4tmp7,task_description,resolved
+VisualEditor: Support pasting of HTML from external sources,"Change 86664 merged by jenkins-bot:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1385500075,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"Change 86664 had a related patch set uploaded by Esanders:
+Rich paste
+
+https://gerrit.wikimedia.org/r/86664",1381157527,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"(In reply to comment #2)
+> I think users will expect that pasting things like tables from other editors
+> and sources into VE to more or less Just Work.
+
+That is bug 41193 (and yes, getting that to work would be lovely). This is about corruption of the clipboard from OpenOffice, which is a distinct problem whether or not we get the pasted-formatting working in time for the 'beta'.",1367874654,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"
+I think users will expect that pasting things like tables from other editors and sources into VE to more or less Just Work.",1367867550,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+VisualEditor: Support pasting of HTML from external sources,"* Editing of table structure isn't exactly supported right now
+
+* I'm curious what OpenOffice puts on the clipboard. It may well be that the root cause is ""OpenOffice puts unreasonable things on the clipboard when copying a table""",1367866569,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-4fybw5go6fyidok4tmp7,task_subcomment,NA
+Sync source and editor like TeXShop,"**Author:** `mstankus`
+
+**Description:**
+In TeXShop, you can click on a piece of content (for example,
+a word) and choose sync and you are sent directly to the 
+part of the source corresponding to that word. It would be great
+if that could happen for wikis.
+
+--------------------------
+**Version**: 1.22.0
+**Severity**: enhancement",1367686680,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zolq2daof5tqslp44gue,task_description,declined
+Sync source and editor like TeXShop,"(In reply to comment #2)
+> Write now, you decide what is wrong, click on edit and then
+> search through markup for the word was misspelled or phrase
+> which needs to be checked. 
+
+This will mostly get fixed by VisualEditor which you can already try out:
+http://blog.wikimedia.org/2013/04/25/visualeditor-alpha-in-15-languages/
+
+Closing as WORKSFORME.",1368010283,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zolq2daof5tqslp44gue,task_subcomment,NA
+Sync source and editor like TeXShop,"**mstankus** wrote:
+
+Write now, you decide what is wrong, click on edit and then
+search through markup for the word was misspelled or phrase
+which needs to be checked. 
+
+  An alternate approach would be to allow someone to mark 
+a word with a mouse, right click, choose ""edit wiki page""
+and then have the computer open the editor AND move
+the cursor to the part of the markup relevant to that 
+word in the text. It looks through the mark up for you
+and saves everyone time.",1367964649,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zolq2daof5tqslp44gue,task_subcomment,NA
+Sync source and editor like TeXShop,"I don't know what TeXShop is, so ""like in TeXShop"" is not helpful.
+Still I don't understand what is requested here. I click a word in the content of a wiki page (preferably in ""Edit"" mode), and I am send to which source, and why?
+Could you come up with a specific example and exact steps to reproduce, plus the current outcome and the expected outcome? Thanks.",1367833876,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-zolq2daof5tqslp44gue,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","The close icon as defined by the [[ https://wikimedia.github.io/WikimediaUI-Style-Guide/visual-style_icons.html | WikimediaUI icon principles ]]. OOUI is already featuring the correct icon.
+
+| | Product | Description | Code | Screenshot | Screenshot after
+| | -- | -- | -- | -- | --
+| {icon check color=green} | OOUI | [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=icons&theme=wikimediaui&direction=ltr&platform=desktop#widgets-mediawiki-vector-ltr | Uses the correct icon ]] |  | {F9379666} | 
+| {icon check color=green} | Post-Edit Feedback popup | Uses the Unicode × glyph with hover behavior | Extension:PostEdit outputs CSS generated content `×` with style rules. | {F7451633} | {F26525706} 
+| {icon check color=green} | Recent CentralNotice banners | ""x in a circle"" icon, no `:hover` behavior | Extension:CentralNotice outputs an img tag showing :$wgNoticeCloseButton which defaults to [[https://upload.wikimedia.org/wikipedia/foundation/2/20/CloseWindow19x19.png|CloseWindow19x19.png]] | {F26525761} | 
+| - | ~~Visual Editor Feedback dialog~~ | As of 2017-09 not an issue any more => converted to OOUI | | {F9404470} | 
+| {icon check color=green} | ULS | ~~Thicker stroke “x” SVG, no :hover behavior~~ | Extension:UniversalLanguageSelector custom `.uls-icon-close` class | {F9362244} | {F9404483}
+| {icon check color=green} | Extension:GuidedTour | different icon with different size |  `.guider_close` |  | 
+| {icon exclamation-triangle color=red} | Extension:MultimediaViewer | bolder, less contrast; Exempt from amending is the main close icon as it would need a full icon redesign. Will be revisited after T177432 |  | {F10595012} | 
+| {icon check color=green} | Extension:GettingStarted | different icon with different size and lighter grey |  `.mw-gettingstarted-cta-close` | {F10172642} | {F10188673}
+| {icon check color=green} | Extension:PagePreviews | different icon, bolder and bigger | | {F10318266} | {F10319955}
+| {icon check color=green} | Extension:Translate | ~~Similar to ULS, different icon though, as it's minimally smaller in layout~~ | `.grid .tux-message-editor .close` | {F9405760} | 
+
+
+The differences make WMF wikis feel unpolished.
+
+--------------------------
+Original report: 
+**Version**: 1.22.0",1367638620,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_description,resolved
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 389542 **merged** by jenkins-bot:
+[mediawiki/extensions/MultimediaViewer@master] Remove special color treatment of close icon on confirmation
+
+[[https://gerrit.wikimedia.org/r/389542]]",1517946899,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",OH from @RHo: “We can finally close the close icon”,1517337678,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376851 **merged** by jenkins-bot:
+[mediawiki/extensions/CentralNotice@master] Use consistent close icon
+
+[[https://gerrit.wikimedia.org/r/376851]]
+",1517271747,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 394076 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/core@master] mw.postEdit: Use mw.notify to display message
+
+[[https://gerrit.wikimedia.org/r/394076]]
+",1512061260,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 389542 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/MultimediaViewer@master] Remove special color treatment of close icon on confirmation
+
+[[https://gerrit.wikimedia.org/r/389542]]
+",1509995888,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 385250 merged by jenkins-bot:
+[mediawiki/extensions/Popups@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/385250]]
+",1509555770,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 385250 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/Popups@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/385250]]
+",1508444481,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 384094 merged by jenkins-bot:
+[mediawiki/extensions/GettingStarted@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/384094]]
+",1507942239,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 384191 merged by jenkins-bot:
+[mediawiki/extensions/GuidedTour@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/384191]]
+",1507941006,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 384191 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/GuidedTour@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/384191]]
+",1507939773,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 384094 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/GettingStarted@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/384094]]
+",1507923417,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",Possible regression: {T178111},1507846952,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376873 merged by jenkins-bot:
+[mediawiki/core@master] postEdit: Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/376873]]
+",1505254455,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376869 merged by jenkins-bot:
+[mediawiki/extensions/Translate@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/376869]]
+",1504966688,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376873 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/core@master] postEdit: Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/376873]]
+",1504936447,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376869 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/Translate@master] Use standard close icon
+
+[[https://gerrit.wikimedia.org/r/376869]]
+",1504923664,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376851 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/CentralNotice@master] Use consistent close icon
+
+[[https://gerrit.wikimedia.org/r/376851]]
+",1504911061,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376648 merged by jenkins-bot:
+[mediawiki/extensions/UniversalLanguageSelector@master] Use consistent close icon
+
+[[https://gerrit.wikimedia.org/r/376648]]
+",1504857338,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Change 376648 had a related patch set uploaded (by VolkerE; owner: VolkerE):
+[mediawiki/extensions/UniversalLanguageSelector@master] Use consistent close icon
+
+[[https://gerrit.wikimedia.org/r/376648]]
+",1504828559,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","Just to give an update
+
+https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_icon_set gives a list of places the old icon is used, probably based off of this report, but the page has not been updated for 2 years, so it is likely out of date. 
+
+https://doc.wikimedia.org/oojs-ui/master/demos/#icons-apex-ltr gives what I believe to be the most recent icons (using apex). Based on the attached screenshot, that is indeed what Wikipedia uses in the edit feedback
+
+{F4913849}
+
+If someone could investigate other places and help to figure out to what extent this is still an issue, that'd be great",1480546272,PHID-USER-4h2udy357ze7pb3oqlp3,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","{F187901}
+
+This icon is used for all of these instances mentioned above:
+
+https://upload.wikimedia.org/wikipedia/commons/5/56/PEF-1-Cropped.png
+https://upload.wikimedia.org/wikipedia/commons/3/37/CentralNotice_banner_2013-05-03.png
+https://upload.wikimedia.org/wikipedia/commons/3/37/CentralNotice_banner_2013-05-03.png
+
+---
+
+{F187902}
+{F187903}
+
+This icon is used specifically to clear input fields. 
+
+---
+
+I hope this helps. Let me know if I'm not answering any other questions mentioned. I'll provide info around specs soon.",1435682114,PHID-USER-tjeabpzbwsqw3xciydvb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",@Galorefitz: Sorry that nobody has replied yet. I've also brought up your question on the mailing list now: https://lists.wikimedia.org/pipermail/design/2015-June/002325.html,1435674260,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","I am new here and was wondering if I could contribute to resolving this ticket.
+
+I went through the conversation and had a few doubts:
+1. Are we to switch from icons to glyphs, everywhere? Or just make the icons consistent, for now?
+2. Already pointed out, but not answered,
+
+>>! In T50067#526717, @Aklapper wrote:
+> As Jared added the ""easy"" keyword to this ticket: What is the prefered approach and expected implementation for a potential new code contributor? 
+> Which specific 'close' icon to use everywhere?
+> What is the complete list of codebases which are affected?
+",1431636628,PHID-USER-v3ap2mbgahzlhkciw4ai,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","James, there are still many many interfaces especially with smaller dialogs (language switching, fundraising banners, etc) which use icons for dismiss, this is true on mobile as well due to space constraints, I'd prefer to get consistency in these places then we can investigate in which interfaces we should expand beyond just an icon. But for places we're CURRENTLY using an icon, that icon should be consistent.",1414441471,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","(In reply to Andre Klapper from comment #9)
+> As Jared added the ""easy"" keyword to this ticket: What is the prefered
+> approach and expected implementation for a potential new code contributor? 
+> Which specific 'close' icon to use everywhere?
+> What is the complete list of codebases which are affected?
+> 
+> This ticket got a bit messy so I got lost. Summarizing is highly welcome.
+
+From what I understand, the current guidance is ""never ever ever use an icon for workflow functionality"", per user testing outcomes. This is why VE switched over to simple words instead (""Done""/""Cancel""/etc.)",1414441300,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","As Jared added the ""easy"" keyword to this ticket: What is the prefered approach and expected implementation for a potential new code contributor? 
+Which specific 'close' icon to use everywhere?
+What is the complete list of codebases which are affected?
+
+This ticket got a bit messy so I got lost. Summarizing is highly welcome.",1414344333,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","8. Besides #2 (an 'X' in a circle), other fund-raising banners use the plain 7px 'x' image donate/Small-black-close.png for their close iocn, e.g. http://meta.wikimedia.org/w/index.php?title=Main_Page&banner=B13_0725_trn_Cntrl_nd_yyYY&force=1",1376346995,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","(In reply to comment #4)
+> 1. Located in core (probably /skins/common/images/)
+
+In the past I've tried to use core image resources in CSS files together with @embed without success. I think that desperately needs fixing to go onward with the unification.
+
+> 3. Available in a large size and a small size
+
+I would consider having SVG version too a must.",1372850261,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","7. Extension:GuidedTour uses a square [X] icon, no hover, for its .x_button style. <https://bits.wikimedia.org/static-1.22wmf3/extensions/GuidedTour/modules/externals/mediawiki.libs.guiders/mediawiki.libs.guiders.submodule/x_close_button.jpg>",1368227877,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",I checked in a smaller version of the closewindow19x19.png image in change I0e170305.,1367693472,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","There are also currently 2 close window images in core (besides jQuery UI):
+
+1. https://bits.wikimedia.org/static-1.22wmf3/skins/common/images/closewindow.png
+
+2. https://bits.wikimedia.org/static-1.22wmf3/skins/common/images/closewindow19x19.png
+
+I don't think #1 is used anywhere any more (but would be worth checking).
+
+I believe #2 is the same image as the one used in CentralNotice and similar to the Agora design.
+
+If we want developers to standardize on one close icon it needs to have the following properties:
+
+1. Located in core (probably /skins/common/images/)
+2. Works for any background (light, dark, grey, etc.)
+3. Available in a large size and a small size
+4. Conforms to design guidelines
+
+closewindow19x19.png is probably the best bet since it meets 3 of the 4 criteria. All we need to do is create a smaller version for use in small UI elements. Then we can start standardizing everything on that. We can override the jQuery UI close box in resources/jquery.ui/themes/default/.",1367693407,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces",Related URL: https://gerrit.wikimedia.org/r/62237 (Gerrit Change I0e1703057e45297d6728cb635c58183aa37103da),1367693310,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","4. The Universal Language Selector extension uses its own chunky X icon with no hover behavior. jquery.uls styles icon-close with background of https://bits.wikimedia.org/static-1.22wmf3/extensions/UniversalLanguageSelector/lib/jquery.uls/images/close.svg
+
+5, 6. The Translate and VisualEditor extensions also have close.svg icons for CSS backgrounds, each slightly different.",1367641625,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"Inconsistent close icon ""x""  in Wikimedia product interfaces","1. is a design from late 2012.
+
+2. matches https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_Icon_Set#General edits in 2012 which says ""Dismiss - an 'X' in a circle.""
+
+3. came from jquery.ui work in 2010.",1367639602,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-ox6rq6ltvn2e7lv2xj47,task_subcomment,NA
+"""Leave feedback"" link has confusing scope","Component: UI
+
+The speech bubble icon and ""Leave feedback"" link in Visual Editor look like they apply to the page being edited.  I was expecting a Talk: tool.
+
+It would be more clear if the text were ""Report bug in Visual Editor"", but that's annoyingly verbose.  Which is sort of the intention here, I assume ;)  Normally, this link would get buried in a dropdown menu or something, IMO.
+
+The problem is exacerbated if you are sort of blind and zoom in your browser a lot, because the VE feedback link becomes very prominent once the toolbar is wrapped.
+",1367214840,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-necjrhau4bastnyumud5,task_description,resolved
+"""Leave feedback"" link has confusing scope","Yep, from what I recall of the past and my understanding of the report, the issue looks solved.",1419610136,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-necjrhau4bastnyumud5,task_subcomment,NA
+"""Leave feedback"" link has confusing scope","The link is now neatly tucked inside a dropdown menu. There's no screenshot on this bug, so I can only guess that it wasn't like this before. This probably resolves the issue sufficiently.
+
+{F23347}",1419186729,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-necjrhau4bastnyumud5,task_subcomment,NA
+"""Leave feedback"" link has confusing scope","Adding many blockers of bug 38638 to the list of ""easy"" bugs, to mark them as candidates for [[mw:Google Code-in]] tasks (gci2013). If you think this bug is not suitable, remove the keyword.",1384864550,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-necjrhau4bastnyumud5,task_subcomment,NA
+"""Leave feedback"" link has confusing scope",The feedback link isn't a VisualEditor item but part of MediaWiki core. Moving bug appropriately.,1367275669,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-necjrhau4bastnyumud5,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","Screenshot of page in view mode
+
+Show thumbnail in user preference size in edit mode.
+
+1. Set user preference to 300 pixel: ""Thumbnail size:"" of https://de.wikipedia.org/wiki/Spezial:Einstellungen?uselang=en#mw-prefsection-rendering
+
+2. Edit page with image included as standard thumb.
+
+Thumbnail is shown in a smaller size instead of the user preference size.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/thumb
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50379
+
+**Attached**: {F10384}",1367185680,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-pwct3nalejruvwpszxyi,task_description,resolved
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","We have now implemented displaying default images in local wiki default size, and explicitly *not* user-preference size.
+
+This is because the editing surface should encourage users to make the right kind of edits for all users, not just themselves. If a page has an image at default and a second at 300px, and a user with a default of 400px resizes one of the images to fit in with the other, a user with a default of 200px (e.g. an anonymous user) will get a different experience and may try to revert (or the change will have a different effect to what was intended).
+
+I'm therefore re-titling this bug to just refer to local wiki size, and marking as FIXED. Happy to discuss further.",1393447280,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","Change 114420 merged by jenkins-bot:
+Set up wiki-default image size
+
+https://gerrit.wikimedia.org/r/114420",1393446711,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","Change 114420 had a related patch set uploaded by Mooeypoo:
+[wip] Set up wiki-default image size
+
+https://gerrit.wikimedia.org/r/114420",1392873520,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","French Wikipedians would like VE to follow the local convention that thumbnails are only displayed with the ""upright"" option (https://en.wikipedia.org/wiki/Wikipedia:Extended_image_syntax#Size).",1389017980,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","User preference and wiki-default sizes specify the maximum width of an image, regardless of dimensions or aspect ratio, but VE scales the images to fit in a 190px by 212px box.
+
+This means that some images, particularly tall thin ones such as full-length portraits, get rendered at very different sizes in VE edit mode to view mode, with consequential impact on the layout of surrounding content.",1380667642,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size",*** Bug 52487 has been marked as a duplicate of this bug. ***,1380666480,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size",Confirmed with Gabriel (Parsoid team) that this [should|is going to be] solved in VE.,1368216779,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Thumb"" images should display in wiki default thumb size","Created attachment 12197
+Screenshot in edit mode with smaller thumbnail
+
+**Attached**: {F10385}",1367185755,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-pwct3nalejruvwpszxyi,task_subcomment,NA
+"VisualEditor: ""Review your changes"" pop-over overlaps sidebar in monobook skin","Review your changes
+
+See screenshot.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+
+**Attached**: {F10352}",1367136660,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-fs4ayby7t52qjcroab4t,task_description,declined
+"VisualEditor: ""Review your changes"" pop-over overlaps sidebar in monobook skin",Meh. I guess I'll never use VE.,1370328889,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-fs4ayby7t52qjcroab4t,task_subcomment,NA
+"VisualEditor: ""Review your changes"" pop-over overlaps sidebar in monobook skin","Exactly what is the problem? The fact that the VisualEditor dialog overlaps the Monobook sidebar, or that the searchbox/logo in the Monobook sidebar overlap the VisualEditor dialog?
+
+The VisualEditor dialog overlapping is pretty much inevitable since it has a minimum width. If your screen is too narrow it has no where to go (short of a scrollbar, which I think give a worse user experience).
+
+If it were always overlapping it would be a more pressing problem, but right now it only overlaps if you activate the review dialog, in which case your focus is more likely to be on the dialog than on the sidebar (e.g. if we need to choose, it is the obvious choice).",1370298705,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fs4ayby7t52qjcroab4t,task_subcomment,NA
+VisualEditor: Tools to set/unset text with annotations (tracker),"Given that these all exist in DM, it's ""just"" a question of making a set of icons for each function and adding it to the tool bar (and then working out what to do with a toolbar with eight such icons when we wanted two.
+
+Have left off from the existing list in ve.dm.TextStyleAnnotation.js:
+
+* span - as that'll need to be a distinct bug given the complexity (it'll need at least an inspector, possibly a dialog)
+* strong/em - should we just silently use these instead of b/i (or vice versa)? Either way, it feels confusing to give the user both options.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367087820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nkytk4yj27kjhhclg73g,task_description,declined
+VisualEditor: Tools to set/unset text with annotations (tracker),All now in #VisualEditor-EditingTools.,1422405518,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nkytk4yj27kjhhclg73g,task_subcomment,NA
+VisualEditor: Tools to set/unset text with annotations (tracker),Related URL: https://gerrit.wikimedia.org/r/64801 (Gerrit Change I51f2605e7d8e2bab1d641f02244d5cd24f505676),1369136660,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nkytk4yj27kjhhclg73g,task_subcomment,NA
+VisualEditor: Tools to set/unset text with annotations (tracker),"Icons for these are now merged into master; the outstanding work here is relatively light, except for the overall design issue about the toolbar having too many buttons.",1369094298,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nkytk4yj27kjhhclg73g,task_subcomment,NA
+VisualEditor: Tools to set/unset text with annotations (tracker),Related URL: https://gerrit.wikimedia.org/r/64475 (Gerrit Change I2f317e1dda2c2e2fceac401768c732dae02e83ce),1368875872,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nkytk4yj27kjhhclg73g,task_subcomment,NA
+VisualEditor: Report that the save dialog omits the save description entry box on hewiki/Windows/Firefox,"Cannot reproduce in Firefox/Mac or Chrome/Mac; asking user to reconfirm.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**Platform**: PC",1366931820,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xc3udo6fxmbjckxyjow3,task_description,invalid
+VisualEditor: Report that the save dialog omits the save description entry box on hewiki/Windows/Firefox,I asked the user. he meant to a local script which isn't supported by VE.,1367254280,PHID-USER-u7udgblfyop6qd5wxot6,True,PHID-TASK-xc3udo6fxmbjckxyjow3,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,"As suggested by Timo - currently we have 'wmgUseVisualEditor' and 'wmgVisualEditorParsoidPrefix' which both need to be defined for each wiki we're putting VE on, which is a bit annoying (and prone to mistakes) - when we have all 295 Wikipedias with it switched on, it will be even worse. We should probably clean this up a bit.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1366731840,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-em5ivp4uf7qvneztv3ep,task_description,resolved
+VisualEditor: Clean up the way that VE must be configured per wiki,This is now done and live in production.,1369920023,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,"(In reply to comment #1)
+> We could replace wgUseVisualEditor with a visualeditor.dblist file, and
+> change the Parsoid prefixes to be equal to $wgDBname.
+
+$wgUseVisualEditor (or wmgUseVisualEditor) seems fine to me, not sure if a dblist would make things easier.
+
+Getting rid of having to configure wmgVisualEditorParsoidPrefix for each wiki would be great (or at least setting it dynamically/automatically from CommonSettings.php).",1369145278,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,Related URL: https://gerrit.wikimedia.org/r/64493 (Gerrit Change I621e98da3be4f787e294d97b350b92d217f43a00),1368896205,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,"(In reply to comment #1)
+> We could replace wgUseVisualEditor with a visualeditor.dblist file, and
+> change the Parsoid prefixes to be equal to $wgDBname.
+
+That sounds like a start, but we're going to want to run some wikis in nothing (no preference to switch on - just not in the .dblist file?), some in alpha (opt-in, limited namespaces) and some in beta (default, all ""content"" even-numbered namespaces that won't break - e.g. MediaWiki:, Template:, Schema:, ? others). Would we want two .dblist files? And some magic juice to decide what namespaces were safe?",1368770741,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Clean up the way that VE must be configured per wiki,"We could replace wgUseVisualEditor with a visualeditor.dblist file, and change the Parsoid prefixes to be equal to $wgDBname.",1368770161,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-em5ivp4uf7qvneztv3ep,task_subcomment,NA
+VisualEditor: Always submit Parsoid bugs over https,"Please write your bugs report to http://parsoid.wmflabs.org/_bugs/ only with https to avoid a secure hole.
+
+Please see this as a blocker for the coming roll out. Thanks.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1366641360,PHID-USER-a6jwrurphpx6yl4coupk,False,PHID-TASK-zdwyyiwstl6uz4rcbn5g,task_description,invalid
+VisualEditor: Always submit Parsoid bugs over https,"We're scrapping this feedback system, so marking as INVALID.",1370629791,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zdwyyiwstl6uz4rcbn5g,task_subcomment,NA
+VisualEditor: Always submit Parsoid bugs over https,"Comment from bug 47507 comment 1:
+
+| No data goes over the wire that is personally-identifying, so I would
+| disagree that this is a blocker; however, yes, this is good practice and we
+| should try to do thi[s] (especially, to avoid unexpected mix-mode for users).",1366668178,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zdwyyiwstl6uz4rcbn5g,task_subcomment,NA
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,"It seems <syntaxhighlight is working just fine, but it's old deprecated 'redirect' <source is not recognized by VE, as can be seen in the link.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://en.wikipedia.org/wiki/User:TheDJ/Sandbox",1366465260,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-2izho3en3c7veqknv2wr,task_description,resolved
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934095,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2izho3en3c7veqknv2wr,task_subcomment,NA
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,"
+
+*** This bug has been marked as a duplicate of bug 47579 ***",1366790189,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-2izho3en3c7veqknv2wr,task_subcomment,NA
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,"This is probably something Parsoid needs to handle (or, rather, SyntaxHighlight with the Parsoid functionality to cope with 'redirects' between extension tags). Gabriel, does this sound right to you?
+
+@Raimond - bug 43126 is about editing these blocks; this is just about displaying them correctly.",1366471273,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2izho3en3c7veqknv2wr,task_subcomment,NA
+VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported,Dupe of bug 43126?,1366465834,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-2izho3en3c7veqknv2wr,task_subcomment,NA
+VisualEditor: VE tab missing oldid when using edit source on an oldid,"https://en.wikipedia.org/w/index.php?title=Phil_Thompson&action=edit&oldid=535300833
+
+Note that in this mode, the VE tab is missing the oldid
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://en.wikipedia.org/w/index.php?title=Phil_Thompson&action=edit&oldid=535300833",1366464180,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-v3h2ouiwohdu44mwy2g6,task_description,declined
+VisualEditor: VE tab missing oldid when using edit source on an oldid,"All of the tabs in this mode go to current, not oldid, so I think this is something that either should be fixed upstream in MW core (in which case, VE should just magically work), or be left as is, given that users will expect the current behaviour.",1368809793,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v3h2ouiwohdu44mwy2g6,task_subcomment,NA
+VisualEditor: VE tab missing oldid when using edit source on an oldid,"In this mode without the VE, the wikitext edit tab doesn't go to the oldid, it goes to the curid page; I think we're going to have to think about how to let users get the VE from here.
+
+Timo, any thoughts?",1366471108,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v3h2ouiwohdu44mwy2g6,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab text should be ""Create source"" or similar when page is non-existent","Currently the ""Edit source"" button's label is the same whether the page is extant or not. This should change.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1366394700,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lr6aehasmla6m24l7lfy,task_description,resolved
+"VisualEditor: ""Edit source"" tab text should be ""Create source"" or similar when page is non-existent",Merged; will go out with wmf5.,1368885140,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-lr6aehasmla6m24l7lfy,task_subcomment,NA
+"VisualEditor: ""Edit source"" tab text should be ""Create source"" or similar when page is non-existent",Related URL: https://gerrit.wikimedia.org/r/64276 (Gerrit Change Iafba040cb8eb53017f38f2099a473e0e43e2ec46),1368791290,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-lr6aehasmla6m24l7lfy,task_subcomment,NA
+Use JSDuck syntax for inline examples in code documentation,"That is https://github.com/senchalabs/jsduck/wiki/Inline-examples
+
+For instance:
+
+resources/js/ext.translate.editor.js
+9:       * Example usage:
+
+resources/js/ext.translate.proofread.js
+107:     * Example usage:
+
+resources/js/ext.translate.pagemode.js
+10:      * Example usage:",1365665640,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-nqzemfntve3l7ortesoj,task_description,declined
+Use JSDuck syntax for inline examples in code documentation,"JSDuck's `@example` syntax is for a live demo of running code. For OOjs UI and VisualEditor this can be useful in places for classes and methods that are largely about their visual and interactive rendering (not about the shape return value itself). However I'm not sure that's useful in the case of the Translate extension.
+
+To render code examples with syntax highlighting, just use three backticks (or indentation) to create a code section in JSDuck's markdown rendering. Closing this task as it doesn't seem actionable right now.
+
+Right now Translate documentation isn't rendered/published anywhere, so in its current form the code examples are readable as-is. If they are published, one of the three examples will need to be indented for it to be preformatted correctly.",1487992074,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nqzemfntve3l7ortesoj,task_subcomment,NA
+Use JSDuck syntax for inline examples in code documentation,"Example of how usage example is used:
+
+https://doc.wikimedia.org/VisualEditor/master/#!/api/ve.init.sa.Target
+
+(especially notice the live preview)
+
+https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.html",1379593886,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-nqzemfntve3l7ortesoj,task_subcomment,NA
+"VisualEditor: ""Report problem"" button should give some feedback","- Edit an article on the English Wikipedia in the VE
+
+- Click ""Review and save""
+
+- Click ""Something is wrong""
+
+- Enter text into the field and click ""report problem""
+
+Nothing happens - either the error report is not sent, or the fact that it was sent is not conveyed to the user.
+
+Reproduced three times in a current Chromium version (Chromium/25.0.1364.160) on Ubuntu.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1365661620,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-tz5is7r52hxlpbizafzp,task_description,resolved
+"VisualEditor: ""Report problem"" button should give some feedback","The HTTPS element of this is now seemingly fixed in production. On submission, the user gets a ""Your problem has been reported. Thank you."" message. Marking as closed.",1366397733,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tz5is7r52hxlpbizafzp,task_subcomment,NA
+"VisualEditor: ""Report problem"" button should give some feedback","To clarify, Gabriel checked the log and the reports I sent indeed do not seem to have made it through.
+
+And I agree that a ""thank you"" alert would be nice, but I would already have been happy if the ""Report a problem"" dialog box would just have closed after clicking the ""Report problem"" button. Instead, nothing happened at all...",1365716252,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-tz5is7r52hxlpbizafzp,task_subcomment,NA
+"VisualEditor: ""Report problem"" button should give some feedback",IIRC posting from Wikipedia pages accessed via https has always been broken because of client-side security restrictions for subrequests. I think this is an instance of that problem.,1365715063,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-tz5is7r52hxlpbizafzp,task_subcomment,NA
+"VisualEditor: ""Report problem"" button should give some feedback","The reports go to a private log that Gabriel monitors. :-)
+
+We're likely to kill the feature in the medium-term anyway, but a ""Thank you for your report"" JS alert wouldn't go amiss.
+
+Timo, thoughts?",1365714340,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tz5is7r52hxlpbizafzp,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"An automatic tracking category for pages with errors in <math> (when parsed by texvc) would help finding these pages and fixing the errors.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1365503760,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_description,resolved
+Add tracking category to pages with errors in <math>,"I see nobody answers. I am closing the task by myself. If there is a problem, reopen it.
+
+Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].",1467323599,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"The discussion was moved to [[https://en.wikipedia.org/wiki/MediaWiki_talk:Math-tracking-category-error|here]].
+",1467219463,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"No problem.
+",1467218718,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,Thank you. I have posted an edit request at that page on en.wiki.,1467210767,PHID-USER-7cpk77uy2iq7bxf6hac6,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.
+Second of all, there is no link for this case help, because it's too obvious.
+1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.
+2. Put there for example a code:
+{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]
+3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.
+4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment).
+5. Save the page.
+6. Open one page with a math error in good namespace for editing. Make sure the category is there.
+7. Open one page with a math error in bad namespace for editing. Make sure the category is not there.
+8. If there is a problem, replace "":"" with ""-"" in the code and try again.
+9. When you are sure it works, run a nulledit bot on the current category content.
+10. Done.
+ ",1467195164,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.
+Second of all, there is no link for this case help, because it's too obvious.
+1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.
+2. Put there for example a code:
+{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]
+3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.
+4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment).
+5. Save the page.
+6. Open one page with a math error in good namespace. Make sure the category is there.
+7. Open one page with a math error in bad namespace. Make sure the category is not there.
+8. If there is a problem, replace "":"" with ""-"" in the code and try again.
+9. When you are sure it works, run a nulledit bot on the current category content.
+10. Done.
+ ",1467194961,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"I would love to do it myself (for everyone, not just in my own vector.js). @IKhitron, do you have a link to instructions on how to take care of it on en.wiki? Thanks.",1467177192,PHID-USER-7cpk77uy2iq7bxf6hac6,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"I meant one line in wiki code, @SalixAlba and @Jonesey95, not jawascript.
+",1467148543,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors  will remain.
+
+If its really a problem this bit of javascript in your vector.js will hide most of the talk pages.
+
+  jQuery( document ).ready( function( $ ) {	
+    	if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") {
+		$("".mw-category-group a"").each(function(ind,ele) {
+			var title = ele.innerHTML;
+			if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") 
+			 || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) {
+				root = ele.parentElement;
+				$(root).css({""display"":""none""});
+				console.log(ele.innerHTML);
+			}
+		})
+	   }
+     }",1467141776,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"But @Jonesey95, you can do it in a minute by yourself.
+",1467135776,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"":
+
+""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories.""
+
+The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",1467130992,PHID-USER-7cpk77uy2iq7bxf6hac6,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"@Aklapper? Or maybe @Quiddity? Thanks.
+",1466776616,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,It looks like this is fixed in T134872 by https://gerrit.wikimedia.org/r/292576 We can probably close this as a duplicate. ,1466691225,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,So we now seem to have [[Category:Pages with math errors]] on en wiki at least. ,1466630074,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"Hello, @Aklapper. It works. I think you need close this task as resolved.
+",1466629083,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,I think we would need comunity consensus for enabling the MathSearch extension in production... and a lot of cleanup work... sinc it's currently more desinged as demo/proof of concept.,1437662084,PHID-USER-4sfm3grxdo6hnogm4iqe,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"**physik** wrote:
+
+(In reply to Richard Morris from comment #2)
+> This error is made worse by the difference between the syntax used in
+> MathJax and texvc. In
+> http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/
+> Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE
+> a unicode character was used in a formula, the editor was probably using
+> MathJax so the error did not show up. There seem to be a few such errors. A
+> google search
+> https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.
+> org+-Talk%3A
+> can be used to find some.
+
+Bug 72240 will make it better again. I'll try to migrate this feature from MathSearch to the Math extension.",1413745226,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"This error is made worse by the difference between the syntax used in MathJax and texvc. In
+http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE
+a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A
+can be used to find some.",1376979625,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+Add tracking category to pages with errors in <math>,"**physik** wrote:
+
+This is already a feature of the MathSearch extension.",1365506334,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-fr22j5swh5wt5gmpgdnh,task_subcomment,NA
+VisualEditor: Part of MetaList should be moved into Document,"Per IRC discussion between me and Trevor:
+
+* Move list of MetaItems to dm.Document
+* Keep MetaList (possibly rename it) with current API, wraps around list of items in Document
+* MetaList takes a surface, and can make changes using that surface
+* MetaItem.remove method will have to be removed, because it can't call back into the surface
+
+(This is for post-July)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1365460200,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-r3vxaorhac46omf45tpw,task_description,open
+VisualEditor: Any transaction which results in metadata being merged won't rollback cleanly,"Take the document:
+
+<!-- meta -->content<!-- data -->
+
+If you remove all of ""content"", the two comments now have to share an offset in the metadata array but this process is not recorded in the transaction. As a result, when the commit is rolled-back the comments aren't re-split so the resulting doc is:
+
+content<!-- meta --><!-- data -->
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1365265140,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-vebapwqy2gnmj6e46row,task_description,resolved
+VisualEditor: Any transaction which results in metadata being merged won't rollback cleanly,Related URL: https://gerrit.wikimedia.org/r/57850 (Gerrit Change I4edad1c2dd37c723bff2792bab7d694ef17a86dc),1365266744,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-vebapwqy2gnmj6e46row,task_subcomment,NA
+"Remove ""sleep"" from tests","We are using `sleep` in several places. Sleep is evil. The code should be refactored so the sleep is removed.
+
+There are more robust ways to wait for something to happen than using sleep:
+
+http://watirwebdriver.com/waiting/
+https://github.com/cheezy/page-object/wiki/Ajax-Calls
+
+```
+$ grep --include *.rb  -R -F 'sleep' .
+
+./wmde/WikidataBrowserTests/tests/browser/features/support/env.rb:  sleep env_no * 4 # sleep time to give webdriver time to setup
+./wmde/WikidataBrowserTests/tests/browser/features/support/modules/entity_module.rb:    sleep(1.0 / 3) while execute_script('return jQuery.active') != 0
+./wmde/WikidataBrowserTests/tests/browser/features/support/modules/entity_module.rb:    sleep 1
+
+./mediawiki/selenium/features/step_definitions/environment_steps.rb:    sleep 0.3
+
+./mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/general_steps.rb:  sleep(Integer(seconds))
+./mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/search_steps.rb:    sleep(5)
+./mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/search_steps.rb:    sleep 1
+
+./mediawiki/vagrant/mediawiki/extensions/Gather/tests/browser/features/step_definitions/common_steps.rb:  sleep 5
+./mediawiki/vagrant/mediawiki/extensions/Gather/tests/browser/features/step_definitions/edit_collection_steps.rb:  sleep 5
+
+./mediawiki/vagrant/mediawiki/extensions/MobileFrontend/tests/browser/features/step_definitions/editor_ve_steps.rb:    sleep 2 # this gets around a race condition bug in ChromeDriver where both the confirm and the toast are in the page at once, and Chrome reports either ""stale element reference: element is not attached to the page document"" or ""Element does not exist in cache""
+./mediawiki/vagrant/mediawiki/extensions/MobileFrontend/tests/browser/features/step_definitions/notification_steps.rb:  sleep 1
+./mediawiki/vagrant/mediawiki/extensions/MobileFrontend/tests/browser/features/step_definitions/notification_steps.rb:  sleep seconds.to_i
+
+./mediawiki/vagrant/mediawiki/extensions/MultimediaViewer/tests/browser/features/step_definitions/mmv_download_steps.rb:  sleep 1
+
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu
+./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:  sleep 0.5 # Sleep because of annoying JS animation happening in the date picker
+
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1
+./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/media_interface_steps.rb:    sleep 1
+```
+
+
+
+
+
+
+
+",1365078180,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_description,declined
+"Remove ""sleep"" from tests",Unlikely to ever be resolved because of {T139740}.,1495812867,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","We can keep this open.  I actually just added a sleep to a test because I needed to get on with other things, and I should return to fix it at some point.",1405701499,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","(In reply to Andre Klapper from comment #18)
+> Are there more tests containing sleep or is this fixed?
+> 
+> Tony: Are you still working on this or should the assignee be reset to
+> default?
+I think there are a few more sleep keywords to be removed. Sorry, but I dont think I will be able to continue on this right now. Resetting to default assignee for the time being.",1405688273,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Are there more tests containing sleep or is this fixed?
+
+Tony: Are you still working on this or should the assignee be reset to default?",1405687592,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",All patches merged => resetting status from PATCH_TO_REVIEW to NEW,1394711816,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 109471 merged by jenkins-bot:
+Removed sleep variable from TwnMainPage tests
+
+https://gerrit.wikimedia.org/r/109471",1390904723,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Cirrus has two sleeps:
+1.  It waits for some suggestions not to appear.  Without reworking the error handling in the javascript I can't remove this.  I don't feel up to reworking that right now.
+2.  It sleeps between the creation of two pages that it uses to test searches that prefer pages with recent edits.  If I could backdate edit times then I wouldn't need it but I can't at this point.
+
+In total Cirrus sleeps 35 seconds because each of the above is executed once.  It could be better but it could be worse.",1390833772,PHID-USER-2rnfxoezl66afpa7w7in,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 109471 had a related patch set uploaded by 01tonythomas:
+Removed sleep variable from TwnMainPage tests
+
+https://gerrit.wikimedia.org/r/109471",1390656466,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 108916 merged by Cmcmahon:
+Replaced sleep with page-object gem waiting API
+
+https://gerrit.wikimedia.org/r/108916",1390407465,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 108918 merged by jenkins-bot:
+Removed sleep with waiting API in browsertests
+
+https://gerrit.wikimedia.org/r/108918",1390403834,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 108918 had a related patch set uploaded by 01tonythomas:
+Removed sleep with waiting API in browsertests
+
+https://gerrit.wikimedia.org/r/108918",1390402787,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Change 108916 had a related patch set uploaded by Zfilipin:
+Replaced sleep with page-object gem waiting API
+
+https://gerrit.wikimedia.org/r/108916",1390401099,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","(In reply to comment #8)
+> Tony and I have paired on getting his environment set up to work on this.
+I will put my status in [QA] once I have made my environment ready.",1389959040,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Tony and I have paired on getting his environment set up to work on this. Tony, if you still are interested in working on this, feel free to assign the bug to yourself. Let me know if you need help.",1389957541,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443702073,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1389430912,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","Tony Thomas:  just removing the code is not enough.  The tests have to be made to wait properly for whatever it is they are waiting for.  
+
+Using sleep() is either an interim step that never got completed, or else the person writing the test could not think of a better way to wait for whatever the test needs.  
+
+So the tests need to be updated in a thoughtful way so that they wait correctly without using sleep() but also without failing mistakenly.",1389377877,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests","(In reply to comment #3)
+> Sleep statements found:
+> 
+Removing the code from the following places will do ?",1389377680,PHID-USER-b3xlpjqyzhcppjoumu63,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443702056,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1386004108,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443701949,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1384961357,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443702034,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1384960949,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1443701981,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+"Remove ""sleep"" from tests",,1381410981,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-tux6tzschtwynlmfypkk,task_subcomment,NA
+VisualEditor: mw.ViewPageTarget tabLayout should be configurable as part of mw-config,"mw.ViewPageTarget tabLayout is currently hard-coded, which means that we can't have VE work in replace mode on one wiki and add mode on another.
+
+[No doubt other aspects of the integration configuration should not be hard-coded.]
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1365032760,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-iciq5e24fktvreyuptk3,task_description,resolved
+VisualEditor: mw.ViewPageTarget tabLayout should be configurable as part of mw-config,Related URL: https://gerrit.wikimedia.org/r/66881 (Gerrit Change I3fcb0c2903ae62d61ff789b5504e0ea23932121b),1370298230,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-iciq5e24fktvreyuptk3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Page: pages are not plain wikitext pages but are split into three textareas: header, footer and body and a proofreading level tag (note 1).
+So, an adaptation of the VisualEditor to these pages is needed in order to make edition of the pages work.
+
+The UI need to be tweaked in order to allow the splitting of the main textarea into three and the edition of the Proofreading level at the save of page as it works currently for wikitext editing (example: https://en.wikisource.org/w/index.php?title=Page:La_Fontaine_-_The_Original_Fables_Of,_1913.djvu/20&action=edit ).
+
+An other useful (but less important thing) things is to add modules to the Visual Editor to support specific tags used by Wikisource like <pages>, <section> and <poem>.
+
+note 1: structure of the page as save in the database:
+<noinclude><pagequality level=""LEVEL"" user=""LAST PROOFREADER"" />HEADER<div class=""pagetext"">BODY<noinclude>FOOTER</noinclude>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey
+
+This proposal received 41 support votes, and was ranked #23 out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Wikisource#Visual_Editor_adapted_for_Wikisource",1364329860,PHID-USER-5paybpgtxjrhikdos3p5,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_description,resolved
+Create a VisualEditor plugin to integrate with ProofreadPage,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVgmueGyHQCSeVEJeq-D} [2016-11-02T20:27:45Z] <arlolra> updated Parsoid to version 173d7e32 (T149241, T119228, T141723, T141905, T147742, T48580, T133320)",1478118471,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Change 295707 merged by jenkins-bot:
+Allow extensions to handle specific contentmodels.
+
+[[https://gerrit.wikimedia.org/r/295707]]",1476648660,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Change 295707 had a related patch set uploaded (by Cscott):
+Allow extensions to handle specific contentmodels.
+
+[[https://gerrit.wikimedia.org/r/295707]]
+",1466695881,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,Parsoid support for extensions implementing their own contentmodels at https://gerrit.wikimedia.org/r/295707 ,1466695854,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2398307, @Osnard wrote:
+> Is there already a place/time made out to work on this during the Hackathon?
+
+Table in Room 12 if you're not there!",1466599379,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Change 284681 merged by jenkins-bot:
+Sectioned edit target for page namespace
+
+[[https://gerrit.wikimedia.org/r/284681]]",1466598809,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,Is there already a place/time made out to work on this during the Hackathon?,1466584161,PHID-USER-khiuzivvgcimpgvedbzf,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"when trying to insert > pages get a 404 error ;' trying to switch to code hangs.
+when refresshing and repeating it saves properly. on chrome browser 
+{F4145216}",1465443442,PHID-USER-uclm66q7d2hquzahxskz,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"when trying to insert > pages get a 404 error
+{F4145216}",1465443336,PHID-USER-uclm66q7d2hquzahxskz,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"@DannyH, you should subscribe to this :-)",1461661097,PHID-USER-jhzyhftzsmppvszocqg2,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2232258, @coren wrote:
+>>>! In T48580#2228508, @jayvdb wrote:
+>> Is it safe to assume this feature will not suddenly become active and in use in production once code from this task is merged?
+> 
+> It will certainly remain as a beta feature for quite some time, requiring explicit activation.
+
+Well why not activate it on https://test2.wikipedia.org at the very least? The ProofreadPage extension is already 'enabled' there and nobody really uses it for proofreading; just for testing &/or illustrative purposes.
+
+If not, please remember to make the beta ""option"" available there as well.",1461460533,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2228508, @jayvdb wrote:
+> Is it safe to assume this feature will not suddenly become active and in use in production once code from this task is merged?
+
+It will certainly remain as a beta feature for quite some time, requiring explicit activation.",1461417141,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Is it safe to assume this feature will not suddenly become active and in use in production once code from this task is merged?  Sorry that I need to ask ... but I have been unpleasantly surprised in the past (definitely not referring to the developers active on this or related task), and I hope to avoid that occurring in this case.
+
+I think WS folk would like to play with it a little in a test bed before it becomes active somehow, and will need longer than a few days as the deploy process moves from beta/test/prod.
+
+I certainly would be happy to do some QA work on it, if given a decent window to work with.  i.e. I cant make any promises to help if the approach is: it is merged, and will be deployed in three days, happy hunting.",1461270188,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Change 284681 had a related patch set uploaded (by Esanders):
+WIP Sectioned edit target for page namespace
+
+[[https://gerrit.wikimedia.org/r/284681]]
+",1461240057,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2214028, @Ankry wrote:
+> We are still waitng for Page namespace support which is the main editing namespace for most wikisources. Moreover, many new wikisourcians edit **only** in the Page namespace. The general trend is to have articles in main namespace automatically or semi-automatically generated basing on data from Index and Page namespaces. So having VE support in main namespace may be a nice feature, but mostly useless.
+
+Indeed.  Having VE there at all was a preliminary requirement, not the end result.  :-)",1461168206,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"i noted some buggy interaction for the insert > pages, initially rather than subsequenly editing pages template https://www.mediawiki.org/wiki/VisualEditor/Feedback",1461083185,PHID-USER-uclm66q7d2hquzahxskz,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,i noted some buggy interaction for the insert > pages initially rather than subsequenty editing pages template https://www.mediawiki.org/wiki/VisualEditor/Feedback,1461083004,PHID-USER-uclm66q7d2hquzahxskz,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,i noted some buggy interaction for the insert > pages initially rather than editing pages https://www.mediawiki.org/wiki/VisualEditor/Feedback,1461082519,PHID-USER-uclm66q7d2hquzahxskz,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2213983, @Qgil wrote:
+> What is missing to consider this task Resolved?
+
+We are still waitng for Page namespace support which is the main editing namespace for most wikisources. Moreover, many new wikisourcians edit **only** in the Page namespace. The general trend is to have articles in main namespace automatically or semi-automatically generated basing on data from Index and Page namespaces. So having VE support in main namespace may be a nice feature, but mostly useless.
+",1460986863,PHID-USER-2ji2k3idgmipacu4ftck,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"What is missing to consider this task Resolved?
+
+I am trying to summarize the progress on this task at https://meta.wikimedia.org/wiki/Wikimedia_Blog/Drafts/WIP_Wikimedia_Hackathon_2016_post#The_connection_with_the_Community_Wishlist. Is there any beautiful screenshot in Commons that we can reuse?",1460985360,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,This was deployed in the new Single Edit Tab mode.  The basic explanation is at https://www.mediawiki.org/wiki/VisualEditor/Single_edit_tab if anyone is looking for information.,1460150503,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Insert -> Pages -> there is no ""onlysection"" attribute
+
+Z.",1460051560,PHID-USER-zg5ljrw5inhmynt7vcfd,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,works well in chrome and firefox. saved first new article.,1460048163,PHID-USER-uclm66q7d2hquzahxskz,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2173976, @Jdforrester-WMF wrote:
+> Clarification: This will be for all Wikisources, not just frws. :-)
+
+Oh, yeah.  Good point.  It will be available (selectable from the beta features selector) on all Wikisources.
+",1459688948,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,">>! In T48580#2172585, @coren wrote:
+> @Jdforrester-WMF is planning to turn the configuration switch on April 7.
+> 
+> At that point, Visual Editor will become available as a beta feature on fr.wikisource.org for all content namespaces except Page (that's the next part being worked on now).
+
+Clarification: This will be for all Wikisources, not just frws. :-)
+",1459667947,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"Current status: we now have a proper design for Page namespace that is in progress but - as a first step - we now have usable mainspace editing with Visual Editor (including the transclusion tag).  This is currently working on a test server, and is scheduled for the deployment train Tueseday, Apr 5 (and deployed on group 1 that inlcludes the Wikisources on Apr 6).
+
+@Jdforrester-WMF is planning to turn the configuration switch on April 7.
+
+At that point, Visual Editor will become available as a beta feature on fr.wikisource.org for all content namespaces except Page (that's the next part being worked on now).
+",1459604047,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"> I will be in Jerusalem, and will concentrate on coordinating work on this task while there (as well as hack on it myself).
+Great! I'll be in Jerusalem too and willing to work on it.",1456517911,PHID-USER-5paybpgtxjrhikdos3p5,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"I will be in Jerusalem, and will concentrate on coordinating work on this task while there (as well as hack on it myself).",1456515851,PHID-USER-h75guknmwivm6x37iute,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"IMPORTANT:  **If you are a community developer interested in working on this task:** The [[ https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2016 | Wikimedia Hackathon 2016 ]] (Jerusalem, March 31 - April 3) focuses on #Community-Wishlist-Survey projects. There is some budget for sponsoring volunteer developers. THE DEADLINE TO REQUEST TRAVEL SPONSORSHIP IS TODAY, JANUARY 21. Exceptions can be made for developers focusing on Community Wishlist projects until the end of Sunday 24, but not beyond. If you or someone you know is interested, please [[ https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2016 | REGISTER NOW ]].",1453388008,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,@Jdforrester-WMF are you able to add some guidance here?,1426811015,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"What can we do, as community members, to raise the priority of this? It is **really** important for Wikisource to have the VE active within the Page namespace. It is probably the most needed feature of Wikisource projects, and it would be an important testbed for the VE itself: Wikisource books are heavily formatted, much more than Wikipedia articles. ",1426782168,PHID-USER-jhzyhftzsmppvszocqg2,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"(In reply to comment #2)
+> This data should be in a queryable format. The current format sucks and should
+> be abandoned. If there's not already a bug filed about this, please file one.
+Done (bug 46724). But before doing anything on this direction, a refactoring of the wikitext edition interface is needed because the current system is closely based on this storage format (bug 46578).",1364657586,PHID-USER-5paybpgtxjrhikdos3p5,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"(In reply to comment #0)
+> note 1: structure of the page as save in the database:
+> <noinclude><pagequality level=""LEVEL"" user=""LAST PROOFREADER"" />HEADER<div
+> class=""pagetext"">BODY<noinclude>FOOTER</noinclude>
+
+This data should be in a queryable format. The current format sucks and should be abandoned. If there's not already a bug filed about this, please file one.
+
+(In reply to comment #1)
+> How would we go with looking to put the user into the API?  That information
+> would be useful to present through the 'page information' so it is
+> presentable via 'action=info'.  At the moment one has to pull the page data to
+> get the user info, while the proofread status is already captured. Well that
+> is my limited understanding of the data.
+
+action=info is part of index.php, not api.php. That is, the info action is part of the (graphical) user interface, not part of the MediaWiki API. This bug should just be about a single issue. Adding this type of information to the info action can be a dependent bug of this bug. There may be such a page filed already, maybe.
+
+Basically, once the data is queryable, both the info action and the MediaWiki API modules can pull the data out easily. But that's at least three separate bugs (and probably many more).",1364449830,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Create a VisualEditor plugin to integrate with ProofreadPage,"How would we go with looking to put the user into the API?  That information would be useful to present through the 'page information' so it is presentable via 'action=info'.  At the moment one has to pull the page data to get the user info, while the proofread status is already captured. Well that is my limited understanding of the data.",1364377774,PHID-USER-bmenasgfntvftznu6wxs,False,PHID-TASK-v7kj4prknc3sujshfgg3,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Inline comments would be powerful addition to AFT.  It would be something like
+https://en.wikipedia.org/wiki/Stet_%28software%29 integrated into MediaWiki.
+
+I think it would help people make useful comments that could more
+quickly be acted on/resolved.
+
+I realize this would be a large enhancement, but I think it's worth considering at some point in the future.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: http://annotator.wmflabs.org/
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49603",1363903320,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_description,resolved
+Implement inline comment support using OKFN annotator,No reply. Hence closing.,1511275456,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,">>! In T48440#529613, @Parent5446 wrote:
+> https://gerrit.wikimedia.org/r/79839
+> https://gerrit.wikimedia.org/r/78251
+> 
+> Once they are merged, the extension has most of the features implemented. The only thing not implemented is threading, which would be too difficult because OKFN does not natively support it.
+
+>>! In T48440#529622, @Mattflaschen-WMF wrote:
+> Yeah, I consider this complete.
+
+So should this task be closed as resolved? (The item is mentioned on https://www.mediawiki.org/wiki/Outreach_programs/Possible_mentors - that's how I got here)",1504334003,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"If you have open tasks or bugs left, one possibility is to list them at https://www.mediawiki.org/wiki/Google_Code-In and volunteer yourself as mentor.
+
+We have heard from Google and free software projects participating in Code-in that students participating in this programs have done a great work finishing and polishing GSoC projects, many times mentores by the former GSoC student. The key is to be able to split the pending work in little tasks.
+
+More information in the wiki page. If you have questions you can ask there or you can contact me directly.",1382470782,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**tilgovi** wrote:
+
+Nice to see this worked out well!
+
+As for replies, I've got a threading plugin that handles most of this. I'm looking to upstream it for Annotator 2.0.
+
+I'll also take the feedback about not showing annotations immediately into mind. Nothing stops the integrator from overriding the .annotator-hl styles, but something more direct and programmatic might make sense.
+
+Once again, reach out any time in #annotator on freenode or the annotator-dev list and I'll keep watching this bug.",1379459763,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"The GSoC project has the ""Prototyping"" word very visible. Wikimedia requirements for deployment are out of scope. The fact that they are being discussed already now indicates that this prototyping phase seems to be a success. :)
+
+Let's get through the GSoC evaluation and let's talk about further steps after that.",1379455722,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Bug 52156 (history) is also a blocker (to be clear, this is an extra, not part of the required prototype deliverables) to WMF (and probably most third parties) deployment.  It's not strictly UI, but it's definitely user-visible (to experienced users who understand history).",1379454874,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**swalling** wrote:
+
+(In reply to comment #54)
+> Yeah, I consider this complete.  I think we will be able to get those two
+> merged, but I don't think either are hard requirements (though the annotation
+> tab is pretty useful, because otherwise you get annotations everywhere all
+> the
+> time).
+
+I think bug 52064 is the only big UI/UX blocker for actually deploying this to a Wikimedia wiki. Showing annotations by default on every view is likely to annoy folks. 
+
+Otherwise, I think even things like bonafide threading support can be put on hold for later release. Overall, agreed with Matt that this product is nearly done. Very good work for a GSoC project. :)",1379450646,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Yeah, I consider this complete.  I think we will be able to get those two merged, but I don't think either are hard requirements (though the annotation tab is pretty useful, because otherwise you get annotations everywhere all the time).
+
+As Tyler noted, there's not really reply support.  However, if you comment on the same text, it puts the annotation underneath.
+
+The other item that is not implemented (mainly since we did not prioritize it) is including the date.
+
+However, there have been other items implemented that were not listed under Required Deliverables, so I think it balances out.  E.g.
+
+* Update and delete
+* Proper DB setup (including AnnotationRepository for testability), including SQLite support and updates.
+* Logged out user support (under review; Required Deliverables mentions usernames, but not IPs)
+* PHP unit tests (this is the third change under review, which I would like to get merged).",1379449034,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"There are two open patches right now:
+
+https://gerrit.wikimedia.org/r/79839
+https://gerrit.wikimedia.org/r/78251
+
+Once they are merged, the extension has most of the features implemented. The only thing not implemented is threading, which would be too difficult because OKFN does not natively support it.",1379447594,PHID-USER-ea6gwat27oulytc5tvsy,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"GSoC ""soft pencils down"" date was yesterday and all coding must stop on 23 September. Has this project been completed?",1379434950,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #49)
+> Just tried the demo and it works well. Great work Richa and mentors! Just a
+> couple of comments:
+
+Thanks. :)
+
+> - When I edited the page all annotations were gone, I reverted to the
+> previous edition but the annotations didn't reappear.
+
+Yes, handling page changes is one of the trickier things that there may or may not be time for this summer.
+
+However, we do want to fix the issue where the wrong annotations appear when you look at an old version of the page from the history (bug 51728).
+
+> - I assume that these annotations will be displayed in the newly deployed
+> Visual Editor. Would it be possible to update the text anchor as the text is
+> being changed? Annotations in Google Docs have this behaviour, however I am
+> not sure if it would be too complex to mimic that feature.
+
+There is no VE support so far.
+
+> - In the ""recent changes"" page I didn't see any notification of my actions, I
+> understand that it could be meant this way?
+
+We may have time to add logging, but you're right there is no history or logging yet.
+ 
+> And I also loved that you can select several sections of text and create one
+> annotation for all those sections. If the annotation link could be displayed
+> (maybe with a 3rd icon, an anchor displaying the link), that would be a great
+> addition for external websites linking to/highlighting particular fragments,
+> or conversations in the talk page pointing to fragments.
+
+That's a possibility at some point.",1374381107,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #49)
+> Just tried the demo and it works well. Great work Richa and mentors! Just a
+> couple of comments:
+> - When I edited the page all annotations were gone, I reverted to the
+> previous
+> edition but the annotations didn't reappear.
+It looks for annotations for the latest revision since i am using the latest revision id. There is already a bug filed for this https://bugzilla.wikimedia.org/show_bug.cgi?id=51728 .
+> - I assume that these annotations will be displayed in the newly deployed
+> Visual Editor. Would it be possible to update the text anchor as the text is
+> being changed? Annotations in Google Docs have this behaviour, however I am
+> not
+> sure if it would be too complex to mimic that feature.
+> - A minor glitch: when I delete an annotation I get the message ""sorry we
+> could
+> not destroy this annotation"", however the annotation is indeed deleted.
+
+The destroying of annotations is still under review. https://gerrit.wikimedia.org/r/74150 so the annotations are not actually deleted currently.
+> - In the ""recent changes"" page I didn't see any notification of my actions, I
+> understand that it could be meant this way?
+> 
+> And I also loved that you can select several sections of text and create one
+> annotation for all those sections. If the annotation link could be displayed
+> (maybe with a 3rd icon, an anchor displaying the link), that would be a great
+> addition for external websites linking to/highlighting particular fragments,
+> or
+> conversations in the talk page pointing to fragments.
+> 
+> Micru",1374337939,PHID-USER-y3lag4tcfivaet2fsuln,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Just tried the demo and it works well. Great work Richa and mentors! Just a couple of comments:
+- When I edited the page all annotations were gone, I reverted to the previous edition but the annotations didn't reappear.
+- I assume that these annotations will be displayed in the newly deployed Visual Editor. Would it be possible to update the text anchor as the text is being changed? Annotations in Google Docs have this behaviour, however I am not sure if it would be too complex to mimic that feature.
+- A minor glitch: when I delete an annotation I get the message ""sorry we could not destroy this annotation"", however the annotation is indeed deleted.
+- In the ""recent changes"" page I didn't see any notification of my actions, I understand that it could be meant this way?
+
+And I also loved that you can select several sections of text and create one annotation for all those sections. If the annotation link could be displayed (maybe with a 3rd icon, an anchor displaying the link), that would be a great addition for external websites linking to/highlighting particular fragments, or conversations in the talk page pointing to fragments.
+
+Micru",1374323153,PHID-USER-my5s6nat437le6q5fq7d,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"You can now also use the simpler URL, http://annotator.wmflabs.org",1374301337,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"There is now a test wiki for this, http://annotator.instance-proxy.wmflabs.org/ .  If you're interested in testing it, create an account, then try annotating http://annotator.instance-proxy.wmflabs.org/wiki/Lorem_ipsum .
+
+Currently, you must be logged in, both to see annotations and to make them (bug 51722).",1374299983,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"We've made a Bugzilla component.  This will still be the main bug, tracking the initial key functionality.",1374286335,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**nick** wrote:
+
+That GitHub compare url has the sense of the comparison the wrong way round: http://github.com/okfn/annotator/compare/master...wip",1374046255,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**nick** wrote:
+
+(In reply to comment #43)
+
+Hi all,
+
+Sorry not to have weighed in earlier. I'm really glad to see you're using Annotator, and hope I can help out with any problems you might have.
+
+> I'm a little unclear about the relationship of 'read' and 'index', and how
+> the URLs work.
+
+Yes, this is a bit messy. Read and index are implicitly the same endpoint at the moment, and index is just ""read"" with a null ID. Obviously this is horrible, but it turns out that it doesn't matter that much as an index endpoint that returns all annotations is almost never useful anyway, so...
+
+> It seems like this may be a moot point if we use loadFromSearch.  However, I
+> would expect there to be an 'index' url for consistency.
+
+...the vast majority of real implementations use loadFromSearch. If you're interested, current work in progress on Annotator 1.3/2.0 (http://github.com/okfn/annotator/compare/wip...master) is revisiting some of this stuff, and the four endpoints that need implementing by a store are now create/update/delete/query, and the index endpoint is gone.
+
+But, to answer your concrete question: use loadFromSearch and ignore the existence of the ""index"" endpoint.",1374046180,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"I was wondering if someone from the OKFN team could answer a couple quick questions.
+
+I'm a little unclear about the relationship of 'read' and 'index', and how the URLs work.
+
+https://github.com/okfn/annotator/wiki/Storage#index says index returns ""a list of all annotation objects"".  First, I'm wondering if that is supposed to be limited to the current page's annotations.  Maybe that's up to us.
+
+However, the plugin docs (https://github.com/okfn/annotator/wiki/Store-Plugin) have no mention of index, nor do I see a way to override the URL.
+
+https://github.com/okfn/annotator/wiki/Storage#read says it's a straight-forward method that takes an ID and returns a single annotation.
+
+But the plugin docs (Store-Plugin) say, ""read: GETs all annotations. Called when plugin loads or .loadAnnotations() is called. Server should return an array of annotations serialised as JSON.""
+
+Looking at the Coffee code, it seems read is called to get a list, but never explicitly called for a single annotation (although there is a commented out line doing that).  However, since we're using the recommended 303 redirect, it's implicitly used for creations.
+
+The list part is confirmed by testing.  It loads http://127.0.0.1:9090/w/api.php?action=annotator-read&id=:id, which is a bit weird.  I think this is related to https://github.com/okfn/annotator/issues/186
+
+It seems like this may be a moot point if we use loadFromSearch.  However, I would expect there to be an 'index' url for consistency.",1373666058,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"See also:
+* [[Wikipedia:Village_pump_(idea_lab)/Archive_3#Sticky_Notes_for_Easier_Editing]]
+* [[Wikipedia:Sticky notes]]",1372611691,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**tilgovi** wrote:
+
+We're right here watching, Rob :)
+
+I would recommend just focusing on upstream okfn/annotator. We're cranking hard to get everything relevant pushed upstream.
+
+Richa, don't hesitate to reach out if you want help testing or have any questions about the annotator code.",1372372816,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**azaroth42** wrote:
+
+
+Just to recommend the hypothes.is version of annotator, and to point to the Open Annotation specification for the implementation:
+
+http://www.openannotation.org/spec/core/
+
+and 
+
+http://www.w3.org/community/openannotation/
+
+Hope that helps, and looking forwards to seeing the outcomes. Happy to answer any Open Annotation questions that may come up!",1372368533,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Gerrit is ready and all my github changes are imported. 
+https://git.wikimedia.org/log/mediawiki%2Fextensions%2FAnnotator.git
+The basic skeleton of where to call the annotations is ready. Now i am starting with the storage of comments. Here are some of my points:
+1. Going through the idea of custom table implementation and storing comments in a separate table which takes account of the revision id, user and the range.
+2. Creating classes 'create', 'update', 'read', 'delete' for annotations. https://github.com/okfn/annotator/wiki/store-plugin#urls
+3. Modify the above urls of OKFN as:
+prefix: 'api.php'
+create: '?action=create', etc.",1371452038,PHID-USER-y3lag4tcfivaet2fsuln,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,Just a note that i have made a repo on github https://github.com/richajain/Prototyping-inline-comments and have done some initial commits. I will be updating this with the progress done at regular time.,1370539929,PHID-USER-y3lag4tcfivaet2fsuln,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**tilgovi** wrote:
+
+Just popping in to subscribe to CC on this. I'm actively maintaining and improving Annotator for Hypothes.is and am happy to answer any questions or work with you all to close any gaps we need to in order to store annotations in mediawiki.",1369945974,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #35)
+> I saw they allow overriding the URL syntax
+> (https://github.com/okfn/annotator/wiki/Store-Plugin#urls), so the main
+> concern
+> is probably less used methods like PUT and DELETE, which needs investigation
+> on
+> both sides (OKFN and MW).
+
+AFAIK, if you submit a PUT/DELETE request to the API, it will probably just treat it as a GET request, although I could be wrong and have not tested this.",1369942866,PHID-USER-ea6gwat27oulytc5tvsy,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #33)
+> (In reply to comment #32)
+> > Someone may have made a RESTful wrapper of a MW API, or have advice on doing
+> > so.
+> 
+> I sure hope this exists. The API interface is terrible right now.
+
+I saw they allow overriding the URL syntax (https://github.com/okfn/annotator/wiki/Store-Plugin#urls), so the main concern is probably less used methods like PUT and DELETE, which needs investigation on both sides (OKFN and MW).",1369942576,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"From Matt's email:
+> The high-level concept of RevisionDelete applies, but I don't think
+> directly using it is a good fit.  What happens if one comment on a page
+> is a violation, but the next consecutive 999 are fine?  With RevDel, I
+> think you'd have to remove the bad one, then suppress all 1000 (correct
+> me if I'm wrong) containing the bad one, leaving no history of how the
+> good 999 developed.
+
+I was thinking one page per comment.
+
+> True, but there's existing code (the main one I'm thinking of is AFTv5)
+> to learn from.  Another reason not to use a page is that it constrains
+> changes.  Once we publish the JSON page, there could be bots that rely
+> on it, rather than the API.  If we just use JSON internally, that gives
+> us flexibility.
+
+If we use pages, we could still use JSON only internally. We'd implement a new Content type for annotations and still provide an API module for accessing comments.
+
+All that said, I understand the concern with using articles as a storage medium, so I would be fine with either way. I just wanted to make sure we weren't ditching the idea without due consideration.",1369942104,PHID-USER-ea6gwat27oulytc5tvsy,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #32)
+> Someone may have made a RESTful wrapper of a MW API, or have advice on doing
+> so.
+
+I sure hope this exists. The API interface is terrible right now.",1369936634,PHID-USER-ea6gwat27oulytc5tvsy,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Richa Jain has been accepted for Google Summer of Code for this project.  She is currently investigating OKFN and the store plugin.  The below are some thoughts as a starting point:
+
+OKFN provides documentation on writing a plugin for storing annotations (https://github.com/okfn/annotator/wiki/Store-Plugin)?  The most straightforward approach seems to be implementing that as a MW extension.
+
+https://github.com/okfn/annotator-store is an example of how one store works, though of course the MW extension example will be different.
+
+One issue is that the API is RESTful.  It lets you set a custom prefix, but the syntax is a little different than MW normally uses.  
+
+One way to do this is to make a normal MW-style API subclass (like https://www.mediawiki.org/wiki/API:Extensions#Creating_API_modules_in_extensions), then hook into the URL routing code to translate the OKFN-style RESTful URLs to calls to the API.
+
+Someone may have made a RESTful wrapper of a MW API, or have advice on doing so.  It's probably also worth looking at the hooks (https://www.mediawiki.org/wiki/Manual:Hooks)",1369893630,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+(In reply to comment #30)
+going by the description, it perfectly fits the bill! I mean it has all the methods of firefox available in IE. But the documentation is really very poor man. Its going to take me a while to make heads and tails of this :(",1369104663,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #29)
+> going a little off topic here, I think internet explorer cannot be supported
+> in any efficient way, cause of the way text ranges are implemented in it. 
+> 
+> Both ofkn and pundit are not supported in IE. I ve been going through the
+> code of OFKN for a while now and this dawned upon me just now.
+
+In the VisualEditor project we have similar needs for cross-browser range selection and manipulation, and we have used the Rangy library - https://code.google.com/p/rangy/ - which has worked out well for us. Not sure if this is helpful for you?",1369060957,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+going a little off topic here, I think internet explorer cannot be supported in any efficient way, cause of the way text ranges are implemented in it. 
+
+Both ofkn and pundit are not supported in IE. I ve been going through the code of OFKN for a while now and this dawned upon me just now.",1369002502,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Another tool for inspiration? http://www.thepund.it/
+
+Java backend but ""The Pundit client is a Javascript application based on the Dojo Toolkit http://dojotoolkit.org/ . It works closely with the Pundit server API, allowing the end-user to annotate any kind of web contents.""
+
+Apparently related with Europeana and funded by the EU. Sounds like open source but after a very few clicks couldn't find sources (busy day etc).",1367946207,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,Just a note to say that Anthony Chen has submitted a GSoC proposal related to this project: https://www.mediawiki.org/wiki/User:N3c/GSoC_Proposal,1367618047,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+I seem to have butt into the conversation .. I didn't read the comments yet. 
+Apologizes .. 
+
+Anyways keeping with the conversation, since you guys are discussing interfaces, please checkout my prototype
+
+http://adityasastry.in.cp-2.webhostbox.net/index.php?title=Special:BlankPage
+
+Instead of the in-page along with article display, I would propose a movable popout as the readability might suffer when you try to squeeze in the comments interface into the article.",1367180341,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #23)
+> Hey,
+> My name is Aditya and am interested in pursuing this as my GSOC project.
+
+Thank you for your interest.
+
+> Implementing this for some other theme is very easy. We just need to add a
+> DIV in the theme's php file.
+
+Note that this is being proposed as an extension.  Thus, you should not need to modify the core skin definition.",1367162727,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+
+2)Databases
+Allow me to make a very bold statement here that  json/xml are ill suited for a project of this nature.
+Justification:
+1) There are many helper classes already written for MediaWiki like sanitizer class(which depends on the databases) load balancer class(Incase one wants to distribute the comments data) and few other classes which implement functionality which is critically needed. Incase one wants to go the XML/JSON way one needs to implement them as well.
+
+2) Maintenance will become an issue.
+
+3)When migrating between hosts one needs to manually select the xml/json files and move them around. MYSQL supports one click export and import functionality for all the tables.
+
+I will be making a prototype for databases as well in a couple of days.
+And here's my idea. Each article is stored as a WikiText string, so as illustrated by my UI the selected text's starting and ending indexes are caught and the article page name is also caught. These three attributes will be used as indexes into a table ""Comments"" 
+
+When parsing this wikitext, based on the starting and ending indexes the text will be marked and a link will be provided next to it to access the comments as I have shown.
+
+I will be implementing this functionality by tuesday. But for the sake of proposal I will be not using any of the MediaWiki classes for now so you people could test drive it once and based on your feedback I will be making ammendments to my proposal, so please review my work so far :)",1367141303,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"**ganeshaditya1** wrote:
+
+Hey,
+My name is Aditya and am interested in pursuing this as my GSOC project.
+
+After going through the requirements, leaving apart any additional features required. I have outlined two major aspects of this project.
+
+1) Designing the UI.
+2) Designing the database.
+
+I just want to present my perspective on these two things before I start drafting my proposal. I want to hear your opinion on this.
+
+1)UI
+When it comes to designing the UI. I think it will be better if we go with a custom build rather than using a ready-made component, cause MediaWiki uses themes and each component should match the theme and a ready made component leaves very little margin for customization ( in-case its a opensource component, then it might as well be modified, but the person designing the theme need to be not only versed with the code of the MediaWiki but as well as the source code of the component, hence I believe a ready made component would constrain the customizability of MediaWiki.
+
+http://adityasastry.in.cp-2.webhostbox.net/index.php?title=Special:BlankPage
+This is a UI mockup I came up with. Its a prototype for a prototype :P I have made an implementation of this for VECTOR theme, but I have placed the CSS and JS for this in the common skins shared.css and the JS in vector.js as of for now.
+Implementing this for some other theme is very easy. We just need to add a DIV in the theme's php file.",1367140627,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Just a note to say that Richa Jain has submitted a GSoC / OPW proposal related to this report:
+
+https://www.mediawiki.org/wiki/User:Rjain/Proposal-Prototyping-inline-comments
+
+There is another student that has submitted a proposal. I will announce it here as soon as there is a public URL.",1366901402,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Slightly related: http://homes.cs.washington.edu/~travis/reflect/
+
+With old MediaWiki extension code available: http://www.mediawiki.org/wiki/Extension:Reflect
+
+Depends on LiquidThreads, so I don't expect many possibilities of reuse as-is but perhaps you want to have a look.",1366507980,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #19)
+> http://okfnlabs.org/annotator/ is maybe (with some adaptations) a relevant
+> option.
+
+Also http://hypothes.is (they seem to build on top of okf's annotator: https://github.com/hypothesis/h#development)",1365784493,PHID-USER-uazrhtptdqudzoqfefsc,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,http://okfnlabs.org/annotator/ is maybe (with some adaptations) a relevant option.,1365528421,PHID-USER-5paybpgtxjrhikdos3p5,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"This is the end result we are after:
+
+Wikipages optionally looking like this (famous examples picked for reference only):
+
+http://gplv3.fsf.org/comments/lgpl-draft-1.html (few comments)
+
+http://gplv3.fsf.org/comments/gplv3-draft-2.html (really busy)
+
+
+That view would include the possibility to add comments. There is a sandbox to play without registration at
+
+http://www.co-ment.com/see/
+
+And a lite version at https://lite.co-ment.com/
+
+
+PS: group permissions to be taken into account? Maybe not in a prototype for a GSOC student but I can imagine that the same levels of protection (open, registered users, autoconfirmed...) would be desired. For Wikimedia wikis I would require login, a nice reason to register. But this is going too far...  :)
+
+Also, spam check? Posting external URLs possible or not? Well, this can be endless and again we should define the scope for a GSOC prototype.",1364319150,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"From where I'm coming from, it has nothing to do with the first option (HTML comments/warnings to editors).
+
+It is meant as a collaboration tool, essentially your second option.  I don't see it as a replacement for long free-form discussion (""this article needs more reliable sources...""/""it has an undue weight is the following areas""...), but a targeted form of collaboration around small areas of the article, like co-ment.
+
+I agree a first pass (on MediaWiki.org, etc.) would be useful regardless, even if not all the code could necessarily be integrated into the permanent solution.  It would allow trying out implementations and UI ideas.
+
+I agree it would probably have to be one interface at first (and maybe ever), and VisualEditor/Parsoid probably makes more sense.
+
+There would probably have to be limited threading, but flat (these people commented on this excerpt in this chronological order) would probably be sufficient.  If it gets too elaborate, talk it to the talk page/Flow.
+
+To keep it concise, I would suggest just the username and date (perhaps auto-formatted to e.g. ""3 hours ago"" for recent comments), rather than a signature.  I suggest it should show IPs for anons.
+
+I'm not envisioning using LQT, since it seems like if we want to integrate at some point, Flow would be a better candidate.
+
+It would be most useful attached to pages, automatically invalidating a comment when an excerpt is altered.  But ""attached to revision"" is probably more realistic for the first implementation.",1364318830,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"So, to my mind there are two options here, and I can't quite understand which is being discussed (it appears both):
+
+* Is this about surfacing to the editors in some nice way post-VisualEditor roll-out the existing comments for editors - I.e. ""<!-- PLEASE DO NOT CHANGE OBAMA'S NAME -->"" at the top of the Barack Obama article on enwiki? If so, great, and this should probably be moved to the VisualEditor product space. This is definitely needed for VE, but I worry that the scope for functionality is not huge, and it might be limiting.
+
+* Is this about building an additional persistent/semi-persistent un-threaded/semi-threaded discussion space on top of pages/revisions(?) like Co-ment and Google Docs? If so, that sounds fun, and something that we're also looking at building for VisualEditor (as part of the real-time collaboration system, potentially), but I wouldn't want us to get in the way of someone building a first pass for GSoC. Doing this for both VE and wikitext at the same would be a really hard UI challenge (they're very different interface concepts), so perhaps limiting it to just one of them for now? Also, there needs to be a really serious discussion about how this would work from a product perspective (threading? how much? how signed? using LQT? why not? where stored? attached to revisions? To pages? to sections of said revision/page? how? etc.) lest it become mammoth. OTOH, this would be very cool as well.
+
+Apologies for the confusion on my part. :-)",1364317551,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"I've linked this bug from https://www.mediawiki.org/w/index.php?title=Feature_map&diff=663816&oldid=566850 where the FSF feature was reported.
+
+(In reply to comment #11)
+> Are all annotations willing the be seen publicly by default? We won't go for
+> private annotations, but maybe people want to have notes-to-self? Like ToDo
+> post-its for editors, or notes for students preparing their school work.
+
+Looks outside the scope of the request. It's indeed the sort of thing the word ""annotation"" is usually used for, so let's not call this proposal ""annotations"" maybe?",1364283676,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"More context:
+
+Commons has annotations in images:
+http://commons.wikimedia.org/wiki/Commons:Image_annotations
+
+Munaf mentioned annotations at
+http://www.mediawiki.org/wiki/Micro_Design_Improvements#Annotations",1364279754,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"James Forrester has indicated that this may be within the scope of VisualEditor, and that he would be receptive to the feature being implemented as part of GSOC.  I've CCed him.",1364277673,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"To follow up, I have decided to act as mentor should the project be selected.
+
+I think annotation is a valid term, although comment is also commonly used (e.g. LibreOffice, Google Docs).  co-ment seems to use both terms.
+
+There should probably be some kind of permalink that shows the comment, but initially that might just be a link to the revision (especially if comments aren't preserved on edit in the first implementation).
+
+I don't think they should be shown to readers by default.  It would have to be a toggle of some kind.  It would be nice to make this available in VisualEditor mode (either just that, or both).
+
+The notes to self idea needs further thought.  I see the primary use of the extension as collaborative work, but then again people do use userpage for drafts too.
+
+If this project moves forward, we may want to continue speccing it out on mediawiki.org.",1364276995,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"A bit of context and braindumping:
+
+http://openannotation.org/
+http://www.openannotation.org/wiki/index.php/Web_Page_Clients_List
+
+Maybe ""annotations"" is the label we are looking for? Wikipedia articles are not scholarship texts, and inline comments won't be scholrship annotations. Then again... aren't they structurally the same? Point to a specific portion of text and connect a comment, a signature, a timestamp, maybe a link.
+
+Another aspect is My Annotations, as part of My Contributions.
+
+I guess annotations will need a unique deeplink? 
+
+And do we get those annotations by default, or should users activate an ""Annotated view""? Maybe the latter, it looks like too much extra bytes and clutter for the majority of people interested in the first paragraph and some factoids.
+
+Bonus:
+Are all annotations willing the be seen publicly by default? We won't go for private annotations, but maybe people want to have notes-to-self? Like ToDo post-its for editors, or notes for students preparing their school work. Those would be as public as our User pages: public for those knowing where to look but out of default searches / views.",1364271952,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"This feature request is being considered for 
+
+https://www.mediawiki.org/wiki/Summer_of_Code_2013#Project_ideas
+
+Question: is there a potential mentor willing to help potential students interested in this project?",1364081939,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,This sounds much more like a separate extension than an enhancement to ArticleFeedback.,1363987812,PHID-USER-a5pveeqqwaddgfjiv2fq,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Such articles tend to be protected on some level, though, and the same reasons would probably have to apply to this as well.",1363911693,PHID-USER-nv2bu7uh3huvidyjo4lk,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #4)
+> But why would that many people be commenting on the same thing?
+
+Think of a controversial article that asserted a true, verifiable, but controversial fact.  It would probably perennially attract comments to the sentence stating the fact.  So at the very least there would have to be easy filtering/mark as resolved/mark as rejected.
+
+I agree it doesn't *have* to be Wikipedia-scalable, but it's certainly far more useful if it is.
+
+Note, implementers should also consider looking at the co-ment code.",1363911476,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Right, I guess my point was just that wikipedia is not as extreme as folks often make out, sorry. If the thing is well-engineered and scales properly it should work for everyone, which would be perfect.",1363910784,PHID-USER-nv2bu7uh3huvidyjo4lk,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"If it's not the problem, all the better. I'm just saying that we shouldn't hamper this potential GSOC project with Wikipedia-centric issues if they are not issues for the 98% of MediaWikis out there.",1363910387,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"(In reply to comment #3)
+> Then again it is not a trivial project at all. If we propose this we should
+> put
+> apart key aspects of Wikipedia like 5.000 editors commented on the same
+> sentence, performance issues, scalability... Perhaps the project could
+> consist
+> in recycling as much stet code as possible and plug it to a MediaWiki
+> backend.
+
+But why would that many people be commenting on the same thing? There are only so many parts of an article worth commenting on, and only so many points to be made, and a flat out discussion would belong on a talkpage (or equivalent), not in the comments themselves.
+
+As it is people tend to distribute what they work on and edit. Yes, many, many people edit wikipedia and such, and a lot of people may edit the same article, but it doesn't happen all at once. Comments, even if they do span multiple revisions, will only span so many before they cease to apply.
+
+Just look at gerrit as a tiny example - plenty of folks comment on plenty of things, but I've rarely seen more than one or two people comment inline on any one patchset. It's only useful for so many things, and once someone made a point there's no use making it again.",1363909988,PHID-USER-nv2bu7uh3huvidyjo4lk,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"Regadless of Wikipedia & Wikimedia plans, this looks like an extension that would be useful and welcomed in other MediaWikis out there. Well, I know that in the GPLv3 drafting times I really wanted to have that in the MediaWiki based project we were running...
+
+Then again it is not a trivial project at all. If we propose this we should put apart key aspects of Wikipedia like 5.000 editors commented on the same sentence, performance issues, scalability... Perhaps the project could consist in recycling as much stet code as possible and plug it to a MediaWiki backend.",1363909447,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,"See http://lists.wikimedia.org/pipermail/ee/2013-March/000263.html (beginning of thread), in particular http://lists.wikimedia.org/pipermail/ee/2013-March/000276.html (about some of the UI/UX challenges).
+
+The AFT team is not planning on implementing this, at least for the time being.
+
+It is a candidate for a Google Summer of Code Project (mentioned at https://www.mediawiki.org/wiki/Talk:Summer_of_Code_2013#List_of_project_ideas_25327), among other possibilities.",1363906883,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Implement inline comment support using OKFN annotator,This could also potentially be done as a separate extension.,1363903597,PHID-USER-dw53c5cb2qfhyemej57o,True,PHID-TASK-eyovzj2nicd45d4mqp3j,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"Various users find them inappropriate in #mediawiki because it is a support channel, not as much a developer discussion channel (#wikimedia-dev).
+
+Whether to move them there or to a dedicated channel isn't clear yet.
+
+See discussions on bug 46282 and bug 46144.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1363699500,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_description,resolved
+Move wikibugs and gerrit-wm out of #mediawiki,https://github.com/valhallasw/pywikibugs is the source for people who want to make modifications.,1398601535,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"Wikibugs is dead, pywikibugs reports to #wikimedia-dev.",1398197924,PHID-USER-muirnivxp5hzppn2a3z7,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"(In reply to Krinkle from comment #11)
+> Re-opened since bug 46144 is still unresolved.
+
+You didn't re-open this bug. It's now a tracking bug that's marked resolved/fixed with an open dependency. Hrm.",1393636938,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,Re-opened since bug 46144 is still unresolved.,1366375213,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"06.45 -!- Nemo_bis changed the topic of #wikimedia-dev to: MediaWiki and Wikimedia software development | Support: #mediawiki | Technical help for Wikimedia wikis: #wikimedia-tech | Wikimedia operations: #wikimedia-operations
+
+It used to be ""Developers' talk about WMF's #mediawiki projects"" or very similar ones (the key being WMF) since the beginning of time (creation as -usability).",1366174392,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"https://gerrit.wikimedia.org/r/#/c/57752/ , https://gerrit.wikimedia.org/r/#/c/57753/ merged.
+
+00.31 -!- gerrit-wm [~gerrit-wm@manganese.wikimedia.org] has quit [Remote host closed the connection]
+00.32 < mutante> bot is moving per merged changes
+00.32 < James_F> Yup. :-)
+00.32 < James_F> (Yay.)
+
+(CEST)",1366172907,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,Related URL: https://gerrit.wikimedia.org/r/58661 (Gerrit Change I588f2eba8fba9603f33386e54e90c03e2bb5f5f0),1365657530,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"(In reply to comment #6)
+> Ori submitted I10a02bfe to get this done when there is approval.
+
+I'd say, why can't we do both? Lets first move it out of #mediawiki. That is something we all agree upon.
+
+We'll keep it in regular talk channels for now (#wikimedia-dev).
+
+If we believe that it is disturbing even in a developer-oriented channel (which I'm sure it won't) then we can choose to create a separate channel, but going all the way at once is unnecessary and only creates more chaos.",1365475852,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,Ori submitted I10a02bfe to get this done when there is approval.,1365203853,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"I wrote this before: Could we move this debate to its target audience somehow, as I'm afraid that it won't be seen in this Bugzilla report?
+I understand that's hard for IRC, but maybe a generic mailing list or RFC? 
+I don't see much sense battling here.",1363769474,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"(In reply to comment #3)
+> #wikimedia-dev is not Wikimedia deployment specific development. It is
+> development of software used by Wikimedia, which all of MediaWiki is
+> obviously part of at least as long as either MediaWiki is a Wikimedia
+> Foundation project and Wikipedia.org runs on MediaWiki. Regardless of
+> whether our staff maintains it or not.
+
+This is insane. Are you hearing yourself?
+
+>> I'd much prefer #mediawiki-feeds.
+> 
+> For what reason? Because you don't want to see it in channels that you're in?
+
+Because it's the least bad option (other than keeping the bots in #mediawiki).
+
+> In that case we move it out of channels not meant for developers only
+> (#mediawiki) and into #wikimedia-dev where it is reasonable to ask you to use
+> /ignore if you don't like it.
+
+This doesn't make any sense. What's accomplished here?
+
+> If you do find them useful, then how are they useful in a separate channel?
+> You'd have to manually check up there to see for anything. I don't think that
+> works well in practice. The whole idea of being exposed to other people's
+> activities casually (without actively looking for it) wouldn't exist anymore
+> then I believe.
+
+That's a reason to either keep the bots in #mediawiki or not. Moving them to a separate discussion channel solves nothing.
+
+> Besides, what about the channels for operations, visualeditor, parsoid,
+> mobile.
+> They all have bots related to their activities, because it makes sense to
+> have it in the same channel so you're exposed to each others activities and
+> can jump into things when they come by. Separating it out is
+> counter-intuitive.
+
+What about them? You're the one conflating gerrit-wm and wikibugs and then complaining about the two being conflated. wikibugs is only in #mediawiki and was the subject of its own discussion before you created this bug. gerrit-wm is in multiple channels already and serves a different purpose from wikibugs.",1363752509,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"(In reply to comment #2)
+> I don't think #wikimedia-dev should exist.
+> Moving MediaWiki development bots to a Wikimedia channel is pretty wrong.
+> 
+
+#wikimedia-dev is not Wikimedia deployment specific development. It is development of software used by Wikimedia, which all of MediaWiki is obviously part of at least as long as either MediaWiki is a Wikimedia Foundation project and Wikipedia.org runs on MediaWiki. Regardless of whether our staff maintains it or not.
+
+#wikimedia-dev should exist by all means, it isn't specific but broad. Perhaps too broad, but that's why we have specific channels for teams that prefer their own area:
+- operations, visualeditor, parsoid, mobile, i18n.
+
+A #mediawiki-dev could exist leaving #wikimedia-dev with only non-MediaWiki related dev stuff, but that would be rather narrow. There is no justification to split it up right now I think. It isn't too crowded and splitting it up would go at the cost of more decentralisation and less integrated communication.
+
+> I'd much prefer #mediawiki-feeds.
+
+For what reason? Because you don't want to see it in channels that you're in?
+
+In that case we move it out of channels not meant for developers only (#mediawiki) and into #wikimedia-dev where it is reasonable to ask you to use /ignore if you don't like it.
+
+If you do find them useful, then how are they useful in a separate channel? You'd have to manually check up there to see for anything. I don't think that works well in practice. The whole idea of being exposed to other people's activities casually (without actively looking for it) wouldn't exist anymore then I believe.
+
+Besides, what about the channels for operations, visualeditor, parsoid, mobile. They all have bots related to their activities, because it makes sense to have it in the same channel so you're exposed to each others activities and can jump into things when they come by. Separating it out is counter-intuitive.",1363709152,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"I don't think #wikimedia-dev should exist.
+
+Moving MediaWiki development bots to a Wikimedia channel is pretty wrong. I'd much prefer #mediawiki-feeds.",1363707120,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs and gerrit-wm out of #mediawiki,"Aggregating various arguments that apply generally to moving them out (as opposed to moving any specific bot):
+
+(Quote bug 46282 comment #0)
+> The only times I've found it useful is when I was live reviewing and wanted
+> to point someone to a change/comment I made.
+
+(Quote bug 46282 comment #1)
+> Use /ignore in your favorite IRC client. Works well.
+
+(Quote bug 46282 comment #2)
+> I disagree with ""it's completely useless"", but in this case, when someone
+> knows he is going to spam the channel and has op on #mediawiki, he should
+> have quieted [the bot] before sending all those changes.
+
+(Quote bug 46282 comment #6)
+> We're going to move both. Need puppet changes.
+
+
+(Quote bug 46144 comment 5)
+> We actively had a user saying ""This channel obviously isn't for support...two
+> pages of scrollback and I've spotted 2 real people."" This is a bad thing,
+> contrary to what you may think.
+> 
+> We've had *contributors* complaining about the bot(s) for the past couple of
+> months/years.
+> 
+> I really don't think two/three people saying ""I LIKE THE BOT IN #MEDIAWIKI SO
+> LEAVE IT THE HELL ALONE"" trumps the wider problems here...that the bot
+> *needs*
+> to go.
+
+(Quote bug 46144 comment 8)
+> Lets take this the mailing list again...
+> 
+> (But my two cents)
+> If we kick any single bot, Gerrit produces a-lot more cruft lately than
+> wikibugs... I, as having pointed out would prefer them all in a separate
+> channel that is moderated and only the bots are voiced.
+
+(Quote bug 46144 comment 19)
+> (Quote bug 46144 comment 18)
+> > That's not a valid reason, imho. We need a way to tone down what it reports,
+> > if
+> > it's going to stay...the rate of bug reporting & commenting is many times
+> > greater than it once was. It's definitely gotten noisier over the years,
+> > which
+> > has reduced its utility.
+> 
+> Reduced it's utility -> in the main support channel. The bot *is* useful, I
+> just think it drowns out conversation these days.
+
+(Quote bug 46144 comment 26)
+> What about moving them to #wikimedia-dev instead of #mediawiki?
+> 
+> I think most (actively involved) developers that are on IRC aren't disturbed
+> by
+> the feed. If they really must they're experienced enough to not be afraid of
+> a
+> simple /ignore.
+> 
+> Though I speak only for myself, I believe those that do want the feed, would
+> prefer it to be in context of regular conversation, not in a separate
+> channel.
+> 
+> It's where random bits of interesting things come by from (e.g. discussing a
+> change, proposing and and then someone does it or files a bug about it).
+> 
+> It doesn't work when in a separate channel.
+> 
+> See also #mediawiki-parsoid, #mediawiki-visualeditor, #wikimedia-operations,
+> #wikimedia-mobile etc. (and same for third parties such as #jquery-dev and
+> webkit).
+> 
+> The problem is mainly with #mediawiki being a support channel instead of dev
+> channel, not with having notifications in a human-occupied irc channel in
+> general.",1363699938,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-b7iac2xw43i4wyam3nwq,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"wikibugs has gone missing from #mediawiki.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://www.mediawiki.org/wiki/Git/IRC
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=28402",1363319760,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_description,resolved
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #31)
+> @Nemo, this bug is about wikibugs. Though some related change has been
+> merged,
+> wikibugs is not yet run from puppet so that change is irrelevant until that
+> is
+> activated.
+
+Current status is also discussed in https://gerrit.wikimedia.org/r/#/c/54984",1381952272,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"As this came up in the IRC office hour today, wondering whether to go via an RFC for this.",1373991340,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #39)
+> Whose blood do I sacrifice to have this happen?
+
+How about this, instead:
+
+(In reply to comment #21)
+> We could schedule an IRC meeting, announce it ia wikitech-l mailing list, and
+> tally votes/opinions on a wiki page.",1371792126,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #40)
+> Chad's?
+
+No, not me. I tried to move it out of #mediawiki, but people yelled at me. I don't care about this bot anymore.
+
+Removing myself from CC.",1371783597,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Chad's?,1371778738,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Whose blood do I sacrifice to have this happen?,1371739659,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,(Updating summary to make it easier to search this bug),1367252699,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Sooo... it's still in #mediawiki, and not in #wikimedia-dev. Does it need additional poking?
+
+[Personally I prefer the bots in #mediawiki, but it sounds like I've lost this fight. :)]",1367252671,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"sorry, one last time",1366673117,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,..,1366671790,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"test - wikibugs bot, please report in new channel, after having to kill concurrent bot instances started by old script",1366670542,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,moved to #wikimedia-dev,1366670045,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #31)
+> @Nemo, this bug is about wikibugs. Though some related change has been
+> merged, wikibugs is not yet run from puppet so that change is irrelevant
+> until that is activated. wikibugs is still in #mediawiki. Reopening.
+
+At the time the bug was closed, #mediawiki was blessèdly-free of bots. :-)",1366381582,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"@Nemo, this bug is about wikibugs. Though some related change has been merged, wikibugs is not yet run from puppet so that change is irrelevant until that is activated. wikibugs is still in #mediawiki. Reopening.",1366375128,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"https://gerrit.wikimedia.org/r/#/c/57752/ , https://gerrit.wikimedia.org/r/#/c/57753/ merged.
+
+00.31 -!- gerrit-wm [~gerrit-wm@manganese.wikimedia.org] has quit [Remote host closed the connection]
+00.32 < mutante> bot is moving per merged changes
+00.32 < James_F> Yup. :-)
+00.32 < James_F> (Yay.)
+
+(CEST)",1366172918,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Note that wikibugs is now 30 % less chatty, as bug 28402 was fixed (bug 28402 comment 8). It would maybe deserve a second chance. :)",1365658133,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Related URL: https://gerrit.wikimedia.org/r/58661 (Gerrit Change I588f2eba8fba9603f33386e54e90c03e2bb5f5f0),1365657518,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Ori submitted I10a02bfe to get this done when there is approval.,1365203841,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"What about moving them to #wikimedia-dev instead of #mediawiki?
+
+I think most (actively involved) developers that are on IRC aren't disturbed by the feed. If they really must they're experienced enough to not be afraid of a simple /ignore.
+
+Though I speak only for myself, I believe those that do want the feed, would prefer it to be in context of regular conversation, not in a separate channel.
+
+It's where random bits of interesting things come by from (e.g. discussing a change, proposing and and then someone does it or files a bug about it).
+
+It doesn't work when in a separate channel.
+
+See also #mediawiki-parsoid, #mediawiki-visualeditor, #wikimedia-operations, #wikimedia-mobile etc. (and same for third parties such as #jquery-dev and webkit).
+
+The problem is mainly with #mediawiki being a support channel instead of dev channel, not with having notifications in a human-occupied irc channel in general.",1363699186,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"de duping title, These are two issues that really should be discussed separately.",1363699112,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,*** Bug 46282 has been marked as a duplicate of this bug. ***,1363698855,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #22)
+> Right
+> now, wikibugs is reporting CC changes, when it used to not report those.
+
+This is what I just linked: bug 28402 aka bug 43130, which has a patch that someone needs to commit/review.",1363626815,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #18)
+> That's not a valid reason, imho. We need a way to tone down what it reports,
+> if it's going to stay...the rate of bug reporting & commenting is many times
+> greater than it once was. It's definitely gotten noisier over the years,
+> which has reduced its utility.
+
+I believe I already said as much somewhere around here, but wikibugs _is_ producing more noise lately, as it was broken by the recent Bugzilla upgrade and nobody has fixed it (or deployed the fixes to it, I can't remember). Right now, wikibugs is reporting CC changes, when it used to not report those.",1363626526,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"We could schedule an IRC meeting, announce it ia wikitech-l mailing list, and tally votes/opinions on a wiki page.",1363618310,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Could we move this debate to its target audience somehow, as I'm afraid that it won't be seen in this Bugzilla report? 
+I understand that's hard for IRC, but maybe a generic mailing list or RFC?",1363618174,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #18)
+> That's not a valid reason, imho. We need a way to tone down what it reports,
+> if
+> it's going to stay...the rate of bug reporting & commenting is many times
+> greater than it once was. It's definitely gotten noisier over the years,
+> which
+> has reduced its utility.
+
+Reduced it's utility -> in the main support channel. The bot *is* useful, I just think it drowns out conversation these days.",1363617531,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"That's not a valid reason, imho. We need a way to tone down what it reports, if it's going to stay...the rate of bug reporting & commenting is many times greater than it once was. It's definitely gotten noisier over the years, which has reduced its utility.",1363617489,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Bumping importance back down; wikibugs belongs on #mediawiki as it's always been. Recommend WONTFIX.,1363617399,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Upping priority, adjusting summary, reopening.",1363617125,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"I've created bug 46282 about kicking gerrit-wm instead, per myself & p858snake.",1363616978,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #13)
+> wikibugs appears to be in #mediawiki right now and is happily reporting bug
+> updates...
+
+This required me unquieting and unbanning the bot and Tim re-adding the bot to the channel.
+
+(In reply to comment #9)
+> Moving it's easier said than done, since it's not puppetized properly, but
+> that can be worked around.
+
+It's pretty easy. You change ""mediawiki"" to something else (e.g., ""mediawiki-feeds"").
+
+> Long term--wouldn't improvements to wm-bot be a good idea too?
+
+Absolutely. In the short-to-medium term, STOP KICKING THE BOT ON A WHIM.",1363375114,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,wikibugs appears to be in #mediawiki right now and is happily reporting bug updates...,1363368845,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #11)
+> (In reply to comment #7)
+> > Hashar kicked it yesterday... Adding hashar to CC.
+> 
+> I have not kicked wikibugs out of any IRC channel. Additionally, I have ZERO
+> interest in wikibugs nowadays nor am I able to do anything about it. Sorry.
+
+Ah it was ^demon. Sorry for my bad memory.",1363358615,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #7)
+> Hashar kicked it yesterday... Adding hashar to CC.
+
+I have not kicked wikibugs out of any IRC channel. Additionally, I have ZERO interest in wikibugs nowadays nor am I able to do anything about it. Sorry.",1363353592,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #8)
+> If we kick any single bot, Gerrit produces a-lot more cruft lately than
+> wikibugs... I, as having pointed out would prefer them all in a separate
+> channel that is moderated and only the bots are voiced.
+
+This. wikibugs is useful, it tends to notify about semi-interesting things that are happening (unless it notifies that someone CC'd himself on something, but that's another bug).
+
+gerrit-wm tends to spam about changes being merged to wmf branches.",1363347600,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #6)
+> (In reply to comment #5)
+> Lets move it into #mediawiki-feed or another channel then. It provides a
+> better
+> service than wm-bot does (comment 1), and people find it useful. If the
+> specific channel that it's in is a problem, move the bot, don't just kill it.
+
+Moving it's easier said than done, since it's not puppetized properly, but that can be worked around.
+
+Long term--wouldn't improvements to wm-bot be a good idea too?",1363346924,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"Lets take this the mailing list again...
+
+(But my two cents)
+If we kick any single bot, Gerrit produces a-lot more cruft lately than wikibugs... I, as having pointed out would prefer them all in a separate channel that is moderated and only the bots are voiced.",1363346843,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,Hashar kicked it yesterday... Adding hashar to CC.,1363346799,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"(In reply to comment #5)
+ 
+> We've had *contributors* complaining about the bot(s) for the past couple of
+> months/years.
+
+So then lets fix the problem, not just shut off a service people find useful.
+> 
+> I really don't think two/three people saying ""I LIKE THE BOT IN #MEDIAWIKI SO
+> LEAVE IT THE HELL ALONE"" trumps the wider problems here...that the bot
+> *needs*
+> to go.
+
+Lets move it into #mediawiki-feed or another channel then. It provides a better service than wm-bot does (comment 1), and people find it useful. If the specific channel that it's in is a problem, move the bot, don't just kill it.",1363346711,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"We actively had a user saying ""This channel obviously isn't for support...two pages of scrollback and I've spotted 2 real people."" This is a bad thing, contrary to what you may think.
+
+We've had *contributors* complaining about the bot(s) for the past couple of months/years.
+
+I really don't think two/three people saying ""I LIKE THE BOT IN #MEDIAWIKI SO LEAVE IT THE HELL ALONE"" trumps the wider problems here...that the bot *needs* to go.",1363346397,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,*** Bug 46139 has been marked as a duplicate of this bug. ***,1363338334,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,15 04:19:44 -!- wikibugs [~wikibugs@mchenry.wikimedia.org] has joined #mediawiki,1363321422,PHID-USER-7ey733eainlhx5xqp4d3,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"15 04:03:39 < Susan> Can someone please take a look at <https://bugzilla.wikimedia.org/show_bug.cgi?id=46144>?
+15 04:16:04 < jeremyb_> Susan: i did
+15 04:16:18 < Susan> Helpful.
+15 04:16:19 < jeremyb_> (a while ago)
+15 04:16:29 < jeremyb_> Susan: it was kicked. people didn't like the spamming
+15 04:16:37 < Susan> I don't like people.
+15 04:16:39 < Susan> I think we're even.
+15 04:16:41 < jeremyb_> there was a user trying to get help and had trouble because of the flood
+15 04:16:52 < jeremyb_> (wasn't my decision i only saw the scrollback)
+15 04:17:03 < jeremyb_> Susan: anyway, there's #mediawiki-feed for now
+15 04:17:10 < Susan> It's a terrible replacement.
+15 04:17:15 < Susan> As it's missing wikibugs.
+15 04:17:28 < jeremyb_> it has wm-bot providing a similar service
+15 04:17:31 < jeremyb_> i witnessed it
+15 04:17:50 < jeremyb_> and you've been there too
+15 04:18:34 < jeremyb_> Susan: at some point we should either let it back into #mediawiki or configure it to not join (and remove the ban). also we could maybe get wikibugs to join #mediawiki-feed if you really care
+15 04:18:48 < Susan> I do really care.",1363321307,PHID-USER-7ey733eainlhx5xqp4d3,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+Move wikibugs out of #mediawiki to #wikimedia-dev,"wm-bot in #mediawiki-feed is not an acceptable replacement for wikibugs.
+
+For example, Quim added a comment here: bug 35508 comment 14.
+
+wm-bot reported this:
+
+<wm-bot> [bugzilla] (--- - created by: Sumana Harihareswara | priority: enhancement - Normal assignee Chad H.) [Bug 35508] List of Gerrit users - https://bugzilla.wikimedia.org/show_bug.cgi?id=35508
+
+I realize that this is a limitation of Bugzilla's RSS feed, but the output is still almost useless.",1363321220,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hd4snxw47ckt4oowe3xb,task_subcomment,NA
+VisualEditor: Transaction with replaceMetadata then replace at the same offset doesn't rollback cleanly,"This is kind of a ridiculous case, but it cost me an hour of debugging time, so documenting it here for posterity. It won't be a practical issue until we start composing transactions together.
+
+Consider:
+
+var data = ve.dm.example.withMeta,
+    oldDoc = new ve.dm.Document( ve.copyArray( data ) ),
+    newDoc = new ve.dm.Document( ve.copyArray( data ) ),
+    tx = new ve.dm.Transaction();
+tx.pushRetain( 11 );
+tx.pushReplaceMetadata( [], [ { metadata element here } ] );
+tx.pushReplace( [] , [ 'a', 'b', 'c' ] );
+ve.dm.TransactionProcessor.commit( newDoc, tx );
+ve.dm.TransactionProcessor.rollback( newDoc, tx );
+
+After running this, you'd expect oldDoc.metadata and newDoc.metadata to be equal, but they're not:
+
+> oldDoc.metadata[11].length;
+4
+> newDoc.metadata[11].length;
+5
+
+When the transaction is rolled back, the metadata element that was added was never removed. I think this is because the content insertion pushes the metadata back, and then when the rollback tries to remove the metadata again, it can't find it. When the metadata replacement and content replacement are swapped, it works fine, so that's my workaround for now.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1363300500,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2imau6pf732mnvgzug5k,task_description,invalid
+VisualEditor: Transaction with replaceMetadata then replace at the same offset doesn't rollback cleanly,There are no more metadata ops since T56299.,1682006049,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2imau6pf732mnvgzug5k,task_subcomment,NA
+"VisualEditor: Redesign naming of canHaveChildren, ContentBranchNode, etc.","Trevor complained the naming of these things doesn't make sense, so let's sit down and come up with a strategy for renaming this stuff at some point.",1363284960,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-o7nh4k5ffcmrnlrox5vs,task_description,open
+VisualEditor: Allow testing dom<->data conversion with and without MW-specific nodes registered,"TODO comment in ve.dm.Converter.test.js:
+
+// TODO: this is a hack to make normal heading/preformatted
+// nodes the most recently registered, instead of the MW versions
+
+It's not entirely clear to me how we should fix this. Maybe once we hard-split the VE and MWVE code bases and each of these has its own test suite, then we won't have to worry about this as much.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1363131420,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-2jnxk3ykpceaf3icyoim,task_description,resolved
+VisualEditor: Allow testing dom<->data conversion with and without MW-specific nodes registered,This was fixed in gerrit 70753.,1372874201,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2jnxk3ykpceaf3icyoim,task_subcomment,NA
+"VisualEditor: When Parsoid is down, error message is parsoidserver-http-200","When the Parsoid server is down completely (e.g. because you forgot to start it), the error message VE gives you is ""parsoidserver-http-200"". It's kind of ridiculous that it's presenting an error with 200, but it's also a lie: 200 wasn't the response code we got from Parsoid, we got no response whatsoever.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362783660,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6g7xrokkwj7xvlcpixpd,task_description,resolved
+"VisualEditor: When Parsoid is down, error message is parsoidserver-http-200",https://gerrit.wikimedia.org/r/#/c/53165/,1363011611,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6g7xrokkwj7xvlcpixpd,task_subcomment,NA
+VisualEditor: Add static name property to CE nodes,"DM nodes have a static name property which is used by the nodeRegistry. CE nodes currently have their names written out at least twice. It also creates unnecessary complexity when inheriting CE nodes as the parent constructor cannot be used (as it contains the parent's name hard coded).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1362405720,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qrmj2zvtj5xzsxn37rp3,task_description,resolved
+VisualEditor: Add static name property to CE nodes,Related URL: https://gerrit.wikimedia.org/r/52545 (Gerrit Patch-Set: Ibf31de16ab28ad58209c1443cd74f93dda278998/7),1362697441,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-qrmj2zvtj5xzsxn37rp3,task_subcomment,NA
+VisualEditor: Add static name property to CE nodes,Fixed with https://gerrit.wikimedia.org/r/#/c/52545/,1362610508,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qrmj2zvtj5xzsxn37rp3,task_subcomment,NA
+VisualEditor: Kill global functions in test suites,"Functions like runConverterTests() and what not are often global functions in the test file. These should be un-global-ified somehow.
+",1361566080,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ynic2zitioz5lqrrxvlq,task_description,open
+VisualEditor: Kill global functions in test suites,"Found a few:
+
+- ve.dm.ModelRegistry.test
+* function checkForPickMe
+
+- ve.dm.Transaction.test
+* function runBuilderTests
+* function runConstructorTests",1369152667,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ynic2zitioz5lqrrxvlq,task_subcomment,NA
+VisualEditor: Kill global functions in test suites,I can't find these any more. Resolved?,1369145400,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ynic2zitioz5lqrrxvlq,task_subcomment,NA
+VisualEditor: SurfaceFragment methods don't document their chainability properly,"The hallmark of chainability in VE, dm.SurfaceFragment, doesn't actually use @chainable to document the chainability of most of its methods.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1361494680,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lshlhzbjuwcfnblbdwsc,task_description,resolved
+VisualEditor: SurfaceFragment methods don't document their chainability properly,Change-Id: Ib950422ddb78d7b91545399a6053e82ae2dbd932,1361614307,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-lshlhzbjuwcfnblbdwsc,task_subcomment,NA
+VisualEditor: newFromWrap() should perform validation,"ve.dm.Transaction.newFromWrap() currently doesn't check that the transaction it generates will be valid. That is, it will ensure that things are unwrapped correctly, but it doesn't check that the result doesn't end up violating parent/child restrictions.
+
+It's not entirely clear to me whether we should try to rectify that or throw an exception, but either of those is better than generating a transaction that, when applied, will make the document nonconformant.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1361325660,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-dxxwsml3j6lvywpngjgf,task_description,open
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"When a user saves a page, VE should check for references (<ref>s) created without the de-referencing block (<references /> or {{reflist}} or...) and intervene:
+
+* prompt them to fix before saving (out of the notices area?);
+* refuse to save before fixed (grey out the save button?); or
+* auto-fix for them (insert a ""== References ==\n<references />"" section just above the categories), though this (a) sucks, (b) enforces a particular wiki's style on other wikis in code, and (c) would be difficult to internationalise
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=54906
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51260",1361220060,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bw6slpyeq2u23y3ltra6,task_description,invalid
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"This probably doesn't really matter any more, since the absence of a references template will simply cause the references to display at the end of the page.",1508927932,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"The last thing I want us to be doing is adding more error messages. I really think that we can get away with actually fixing the error for people. 
+
+I'd rather see us put it in the wrong place and someone have to fix it than us give the user an error they probably don't know how to fix. 
+
+Can we do a quick audit of major sites and where they put the reference list? I worry we're worrying a bit too much about about negative feedback that might not be as big a deal as we might think.",1383182051,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"(In reply to comment #4)
+> The auto-fix option in comment 0 has been requested today by en.wp user
+> Mahitgar. If the issues noted can be overcome, then it would be the most
+> user-friendly way forward.
+> 
+> Regarding those issues, it is not obvious why this ""sucks"" - please could you
+> elucidate?
+> 
+> Internationalisation of the section title could (I guess easily) be achieved
+> by
+> inserting the contents of a MediaWiki page instead of something defined in
+> code. e.g. the equivalent of
+> 
+> ==={{subst:MediaWiki:Refsection title}}===
+> <{{subst:MediaWiki:Reflist function name}} />
+> 
+> 
+> This doesn't solve the option of imposing en.wp style on other wikis though.
+
+Blindly putting the references section at the end of the article seems to not be great (it'd be after the ""external links"" and ""see also"" sections, and after any stub or thematic templates).",1376520004,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"The auto-fix option in comment 0 has been requested today by en.wp user Mahitgar. If the issues noted can be overcome, then it would be the most user-friendly way forward.
+
+Regarding those issues, it is not obvious why this ""sucks"" - please could you elucidate?
+
+Internationalisation of the section title could (I guess easily) be achieved by inserting the contents of a MediaWiki page instead of something defined in code. e.g. the equivalent of
+
+==={{subst:MediaWiki:Refsection title}}===
+<{{subst:MediaWiki:Reflist function name}} />
+
+
+This doesn't solve the option of imposing en.wp style on other wikis though.",1376323198,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,*** Bug 51910 has been marked as a duplicate of this bug. ***,1375192364,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"Bug 50779 makes it easy to accidentally delete the references list, so this should check for its presence every save not just when references have been added.",1375180866,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+VisualEditor: Warn user when saving page with <ref>s but not <references />,"Currently this would require scanning for the exact html it outputs as the <span style=""color:red;"">...</a> tag. Which can be tricky to do reliably.
+
+Though the Cite extension could perhaps be the first to give their elements some kind of standard attribute for parse errors, it should probably do more like the TemplateData extension: Refuse to save without it and show a warning there instead. Then the API will return to VE with a nice { error: .. } block containing a error code which we can use to fetch a localised message.",1371776892,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-bw6slpyeq2u23y3ltra6,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"Using a more extensive default $linkTrail regex was tried in 416c84480 (although I don't know why it used `\p{L&}` rather than `[[:alpha:]]` or `\p{L}`), but this was reverted in 5b97a5bb due to {T17035}. We could probably try that again (without the apostrophe, see T16655) now that we require a more modern version of PHP with a more modern version of PCRE. It may not work correctly for alphabets other than Latin.
+
+----
+
+Please have a look at 
+https://www.wikidata.org/wiki/MediaWiki:Gadget-rightsfilter/hu
+where the link has the form [[:hu:Reguláris kifejezés|regex]]alapú
+and ""ú"" is not linked.
+This is a multilingual project, so all letters should be included into links, or at least all Hungarian letters. :-)",1361209560,PHID-USER-4c6srusxkc3xljf73qq6,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_description,open
+The default (English) link trail ($linkTrail) only matches [a-z],">>! In T47126#2509560, @Verdy_p wrote:
+> link trails are just a minor facility for **lazy** English contributors using the Wiki code editor.
+
+Those links can be used in many languages. In German Wikipedia they are used exceedingly!
+",1471883260,PHID-USER-co4khfkxwku2c5tgvhnc,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"\p{Latin} would not be sufficient to avoid breaking words. There are languages needing other characters within Latin, notably with combining sequences. See for example Vietnamese that could use letters with two diacritics ! See also Chinese pinyin text, and some African languages.
+
+In fact the minimum would require adding all combining characters (really needed to avoid breaking default grapheme clusters), all joiner controls, digits (including their wide versions used in CJK contexts because p{Latin} also includes wide letters), and a few punctuations (and the soft hyphen, but probably not the minus-hyphen).
+
+Handling the ASCII apostrophe is complex (even more complex in MediaWiki due to its use to markup bold and italic styles: an initial parsing of these wiki syntax would be needed to know if these are apostrophes or markup...).
+
+Note also that the apostrophe mays also be used as a quote (this is covered in more details in Unicode word breakers), and that this concerns not only the the ASCII apostrophe but also the rounded apostrophe.
+
+Again, it is really needed to look at the Unicode standard :
+
+# a MUST-HAVE in all cases, for all languages first requires not breaking any combining sequences before any characters with a non-zero combinining class and not even before CGJ), and to ensure that canonically equivalent strings will always break identically (needed for strict process conformance as required by the standard in all algorithms).
+#  the rules for default grapheme clusters breakers (this adds some unbreakable sequences for Latin text), these rules are language-neutral (there are a few rules to take for Latin text, notably ""spacing diacritics"", and joiners; we could exclude here some ""letterlike"" symbols that are not really Latin).
+#  the rules for word breakers (even if we consider only Latin-written languages): these rules however are language-sensitive (English is simple at this step but not all Latin-written languages, here there's the case for apostrophes, hyphens...)
+
+In summary, it will be much more complex than just a regular expression: it requires a specific parser code (look at ICU implementation).",1470057925,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],Hungarian was cited because the current conservative linktrail rules break Hungarian words. `\p{L}` or `\p{L&}` would work well for Hungarian (I imagine the latter was used to avoid affecting CJK languages; no idea how well that works). Even `\p{Latin}` would be fine.,1470035748,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],For years it was corrected in the other direction. It would be mad to change this now.,1470008927,PHID-USER-4z6eerx3m7iocsrcpku5,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"I don't think that ""cleanup"" operations such as automated replacement of [[Dog|dogs]] to [[dog]]s are useful. In fact they are counterproductive (and in fact unnecessary for the Visual Editor that should completely avoid using these link trails).
+
+My opinion is we **should deprecate** these old link trails and in fact correct the other ways (link trails are just a minor facility for **lazy** English contributors using the Wiki code editor.
+
+In fact, even the Wiki editor should better automatically convert these trails (only [a-z]) to regular links without them. It would also simplify the parsers for bots and analysers. Contributors should always use regular links, that are in fact more readable, and more explicit about the effective range of text covered by links.",1469974285,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"I don't think that ""cleanup"" operations such as automated replacement of [[Dog|dogs]] to [[dog]]s are useful. In fact they are counterproductive (and in fact unnecessary for the Visual Editor that should completely avoid using these link trails).
+
+My opinion is we **should deprecate** these old link trails and in fact correct the other ways (link trails are just a minor facility for **lazy** editors using the Wiki code editor.
+
+In fact, even the Wiki editor should better automatically convert these trails (only [a-z]) to regular links without them. It would also simplify the parsers for bots and analysers. Contributors should always use regular links, that are in fact more readable, and more explicit about the effective range of text covered by links.",1469974218,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"I can say that link trails work well in Polish, which has fairly complex conjugation and declension rules. I'd make a wild guess that it works in around 50% of cases (in English it's more like 99%, as you say). There is a very popular gadget on Polish Wikimedia projects that applies wikitext code cleanup, and one of the cleanups it does is converting things like `[[Dog|dogs]]` to `[[dog]]s`. I would be very sad if we wanted to get rid of them.",1469663792,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"I can say that link trails work well in Polish, which has fairly complex conjugation and declension rules. I'd make a wild guess that it works in around 50% of cases (in English it's more like 99%, as you say). There is a very popular gadget that applies wikitext code cleanup, and one of the cleanups it does is converting things like `[[Dog|dogs]]` to `[[dog]]s`. I would be very sad if we wanted to get rid of them.",1469663654,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"Note als othat a few languages written in the Latin script also use ""agglutination"" for creating very long custom ""words"" by using many prefixes/inffixes/suffixes (and often some internal mutations). Such extension may break for example in Finnish or Hungarian (Hungarian was cited at top of this bug).
+
+Any way I don't think that link trails are a very good idea: users can't control it easily (and should not have to include some arbitrarty separation toklen such as ""nowiki/>"" to limit these trails. Link trails were added only for lazy English writers that want to create links to a singural noun, by placing the final ""s"" of the displayed plural in the trail, or for placing some common suffixes (""ed"", ""s"") of conjugated verbs (but it does not work when there are more complex mutations such as ""*y -> *ies"").
+
+This concept of link trails does not even exist in HTML. And anyway with the Visual Editor, we much less need it now as it is simpler to edit links separately of their visible text content.
+",1469663399,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"> Such link trails should contain only letters or digits in the same script as the last string script used within the inner text of the link and only if that script is alphabetic or an abjad, but probably not Indic abugidas and not any sinographic script (a good question is: can we extend some kanas after a kanji in the inner text of the link (I don't think so), but we can probably extend runs of kanas.
+
+There are some rules for semi-sensible word breaking in CJK languages. VisualEditor implements some of them to be able to e.g. extend selection to the word around cursor when inserting an internal link. I'm not sure if they're simple enough to implement as a regexp; @dchan can probably advise.",1469663161,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"In my opinion [[:alpha:]] or \p{L} would be wrong for Chinese and Thai at least ! they would produice overlong links sticked side by side everywhere and covering most contents in all paragraphs. In Wikipedia, almost all the text of paragraphs would be blue except the start of paragraphs without significant words.
+
+Such link trails should contain only letters or digits in the same script as the last string script used within the inner text of the link and only if that script is alphabetic or an abjad, but probably not Indic abugidas and not any sinographic script (a good question is: can we extend some kanas after a kanji in the inner text of the link (I don't think so), but we can probably extend runs of kanas.
+
+The Unicode rule of matching identifiers is not usable for this (we are not in the context of a programminc language but within a context of use by a natural language, so the punctuation/spacing rules are very different).
+
+If we want a regexp, for now let's focus only in Latin, Greek, Cyrillic, Arabic, Hebrew, and possibly Hangul, breaking the run if there's any change of script (but not if these are ""weak"" digits belonging to all scripts). Extending the regexp for other scripts should be tested first (the hint here is to look at existing rules existing in CLDR for *word breakers* and look at the Unicode standard covering this complex aspect. And may be include also the line breakers to restrict more the link trails to get shorter runs.
+
+However this should not be very language specific: it should better be script-specific.
+
+",1469662578,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"Historical note: Using a more extensive regex was tried in 416c84480 (although I don't know why it used `\p{L&}` rather than `[[:alpha:]]` or `\p{L}`), but this was reverted in 5b97a5bb due to {T17035}. We could probably try that again (without the apostrophe, see T16655) now that we require a more modern version of PHP with a more modern version of PCRE.",1469628163,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"""Is this strange behaviour something we want to preserve, or is it just a historical quirk?""
+Or just survived tests, as a rare case.",1469625591,PHID-USER-4c6srusxkc3xljf73qq6,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"Essentially I think the linktrail for `en` should include all Latin-alphabet characters in the regex. Would `/^(\p{Latin}+)(.*)$/` work?
+
+Although, oddly enough, most uppercase letters are left out of the linktrails. For the Hungarian example above, only accented uppercase letters are matched, not regular ones. Most languages don't include any uppercase letters in their linktrail  string. Is this strange behaviour something we want to preserve, or is it just a historical quirk?",1469625378,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"No, this is a perfectly valid bug. Unfortunately ""link trails"" are currently specified per-language, and the link trail for English doesn't include any accented characters. For example it's defined like this for Hungarian: `$linkTrail = '/^([a-záéíóúöüőűÁÉÍÓÚÖÜŐŰ]+)(.*)$/sDu';`, but these characters will only work on a Hungarian-language wiki.",1469624271,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],OK. Thanks for the detailed explanation.,1469598638,PHID-USER-4c6srusxkc3xljf73qq6,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Link|Links]]"") is just an **old (deprecated) trick** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583675,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Target|Links]]"") is just an **old (deprecated) trick** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583643,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Target|Links]]"") is just an ***old (deprecated) trick*** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583625,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Target|Links]]"") is just an ***old (deprecated) trick*** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583610,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"For now the workaround is to place the text content of the link within the brackets and not expect that it will expand outside on touching letters (this only works on ASCII letters, not on non-ASCII letters that are UTF-8 encoded).
+
+There's some regexp that controls how many characters to add to the link, but it just accepts ASCII digits [0-9], ASCII letters [A-Za-z] and a few ""continuing punctuations"" such as [_].
+
+To cover non-ASCII only contents (including for English!) we should still not include all non-ASCII characters but only characters that are in some simple class. The problem is that regexps to match characters with UTF-8 can be fairly complex to write (but it's still possible to write it) and it is not a closed subset of the Unicode repertoire (because it is extensible: Unicode adds regularly letters, digits and some other useful symbols which could or could not be included such as emojis, we should however exclude whitespaces, but include all combining characters, plus a few controls such as CGJ/ZWJ/ZWNJ/WJ joiners needed in the standard orthography of some languages)
+At each revision of Unicode, we would need to regenerate this matching regexp.
+
+Unicode provides data for character subsets useful for identifiers (idstart, idcontinue) that we could use for matching these textual extensions of wikilinks (after the two closing brackets). It is easily recompilable into a UTF-8 matching regexp. Such regexp is already used internally by Javascript and HTML5 for recognizing their valid identifiers
+
+However this could cause problems with languages that usually don't use whitespaces to separate words in their scripts (notably Chinese, Japanese, or Korean with their sinographic scripts, and a few other Asian scripts such as Thai): we should not extend links to all touching sinograms which would include a full sentence (not fully relevant: it would obscure the page with overlong links everywhere).
+
+We could also break the link if there's a strong script change (e.g. any switch from CJK sinograms to Latin, including ""wide"" Latin characters used in CJK, or the reverse), but not for characters that are using weak scripts (e.g. ASCII digits, shared across many scripts): using regexps in this case would be more complex as we would need to use distinct regexp depending on the last strong script of the last character of the link text within the bracket)
+
+So I think that writing ""[[Link]]s"" (or ""[[Target|Link]]s"") instead of  ""[[Target|Links]]"" (or ""[[Target|Links]]"") is just an old **trick*** of MediaWiki used by (lazy) wiki redactors, we cannot recommand using it:
+
+The longer form will be preferred (where all characters to include in the link should be within the brackets), even if there's still some support for (ASCII-only) text link extensions (after closing brackets) to /[0-9A-Z_a-z]+/.
+
+And I see no reason to handle this case to only to cover all extensions of the Basic Latin script (or even just for Hungarian), or even with other alphabetic scripts (Cyrillic, Greek) or abjads (Hebrew, Arabic) and some Indic abugidas (but not all of them use whitespace for word separation!), or simple syllabaries (such as Ethiopic, or Canadian Syllabics: should we include Hangul, Bopomofo and Katakana/Hiragana when they are mixed with signograms and now necessarily whitespace separated?).
+",1469583362,PHID-USER-haxgydpauf444oiywhg2,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],This seems to be problem on all multilingual projects...,1450788845,PHID-USER-l6fch4yy6jwf3du42zrz,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],"It could also be that the content language is still English in some cases, but it doesn't seems so form the content source.",1361275352,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+The default (English) link trail ($linkTrail) only matches [a-z],This is link trails and it is part of the localization that would be very difficult to get right for everyone. In this case I would say put what you want to use for the page part into the link and do not depend on the link trails.,1361274313,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-n4lw5kls7dkiwbydrbtn,task_subcomment,NA
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,"This test works in Chrome, but in Firefox it fails with:
+
+Expected: 	
+
+""a<b>b<span typeof=\""mw:Entity\"" class=\""ve-ce-leafNode ve-ce-MWEntityNode\"" contenteditable=\""false\"">c</span>d<div class=\""ve-ce-leafNode ve-ce-alienNode ve-ce-alienInlineNode\"" contenteditable=\""false\""><tt>e</tt></div></b>""
+
+Result: 	
+
+""a<b>b<span class=\""ve-ce-leafNode ve-ce-MWEntityNode\"" typeof=\""mw:Entity\"" contenteditable=\""false\"">c</span>d<div class=\""ve-ce-leafNode ve-ce-alienNode ve-ce-alienInlineNode\"" contenteditable=\""false\""><tt>e</tt></div></b>""
+
+(the difference is in the order of the class and typeof attributes)
+
+We should probably implement DOM comparison instead of string comparison in the ce.ContentBranchNode test suite.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1360374780,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_description,resolved
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,"Related: https://gerrit.wikimedia.org/r/#/c/240722/ in MW, where we need to decode data-mw and parse body.html, sometimes recursively :/",1443111671,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_subcomment,NA
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,https://gerrit.wikimedia.org/r/#/c/240693/,1443111590,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_subcomment,NA
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,"This specific case is fixed in https://gerrit.wikimedia.org/r/#/c/57240 by using equalDomElement. However, another case has appeared: recent code introduced full HTML preservation in mw:Image and the attribute order in the HTML serialization matters there too, so now that test passes in Chrome but fails in Firefox (getDataFromDom test 4).",1365033745,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_subcomment,NA
+VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order,"Not sure if it is caused by the javasript object keys. May be related to how WebKit/Geck order the element attributes when serialising the html.
+
+If the former:
+ ve.getHash or assert.deepEqual
+
+If the latter:
+ assert.equalDomElement",1361569492,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-6hp73xqwptdzkhjkx2ki,task_subcomment,NA
+VisualEditor: Clean up duplication of Mac/PC command/ctrl in all command registrars,"Should perhaps have some kind of magic alias ""trigger"" that maps to meta/ctrl respectively.
+
+The flexibility of being able to bind something to ctrl on mac, and to meta on pc is useful but in the most common case we don't to do that.
+
+And we're currently duplicating this internal logic at the cost of decentralisation. So plugin authors providing Tools need to duplicate this logic also, meaning more maintenance when we change this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1359158880,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-fbrnpd67ntdl7dxrvivk,task_description,open
+Only tag edits via GettingStarted if the user is actually new,"The GettingStarted extension is tagging edits of new users (bug 43191). These tags should be temporary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1359154380,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-o2degjsneil7pojmpiav,task_description,resolved
+Only tag edits via GettingStarted if the user is actually new,"**swalling** wrote:
+
+https://gerrit.wikimedia.org/r/#/c/65337/ was merged, and henceforth only users who aren't autoconfirmed will get their GettingStarted edits tagged.",1369959989,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,Related URL: https://gerrit.wikimedia.org/r/65337 (Gerrit Change I3bc2235ac9d5ae1060c86df03663dcb8a6966a38),1369431985,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,"(In reply to comment #4)
+> It sounds like you have a general problem with permanent tags. 
+
+It sounds like you didn't read comment 3.",1368574939,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,"**swalling** wrote:
+
+(In reply to comment #3)
+> The general trend of permanently tagging edits should be examined. Other
+> sites
+> engage in similar practices (such as Facebook marking mobile posts), but
+> whether this is a good thing or whether it should be encouraged is up for
+> debate.
+> 
+> In this case, I don't think permanently marking someone's first edits after
+> you've secretly tagged them as part of an experiment that they didn't opt in
+> to
+> is a good idea. Do other bad tags exist? Yes, but those aren't really
+> relevant
+> here.
+
+It sounds like you have a general problem with permanent tags. 
+
+I think our actual enhancement is to not tag edits of users who aren't new anymore if they make further edits via Special:GettingStarted, e.g. if you're autoconfirmed don't tag their edit, even if if comes via GettingStarted. That's an enhacement we should make, but it's not the same thing as altering MediaWiki tags so they're there one minute and gone the next. That's unexpected and broken behavior according to how tags currently work in all other cases. 
+
+I've changed the bug title to reflect what we're actually going to do around tagging in GettingStarted, to ensure that the tag is accurate.",1368565460,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,"The general trend of permanently tagging edits should be examined. Other sites engage in similar practices (such as Facebook marking mobile posts), but whether this is a good thing or whether it should be encouraged is up for debate.
+
+In this case, I don't think permanently marking someone's first edits after you've secretly tagged them as part of an experiment that they didn't opt in to is a good idea. Do other bad tags exist? Yes, but those aren't really relevant here.",1359156311,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,This proposal is a specific case of https://bugzilla.wikimedia.org/show_bug.cgi?id=18670 .,1359155975,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+Only tag edits via GettingStarted if the user is actually new,"I'm not yet convinced this is a problem.  There are a variety of permanent tags (edit filter, VisualEditor, etc.).  In all cases, it's a good-faith tag of the edit.
+
+Edit filter tags are permanent, even though they sometimes wrongly flag an edit as harmful.  It's just understood that the situation will be cleared up, and editors will move on.
+
+Similarly, the fact that a user made a Special:GettingStarted edit doesn't even mean they're necessarily new.  It's understood and accepted that established users can also have this tag on their edits if they use the page.
+
+It indicates how they made it.  It certainly is not a marker of whether the edit is productive.  And it doesn't really say anything about the user, let alone the user's future work.",1359155274,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-o2degjsneil7pojmpiav,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I encountered many times now on wikis (usually the small wikis) that there are 100s of local MediaWiki pages with translations from before translatewiki.net covered that language.
+
+And even after twn covered it, there may have been local improvements that over time make it into twn, but then the local page stales.
+
+To avoid translations from going out of sync (the longer we wait with this, the harder it is to clean them up as the difference between an override and an outdated translation becomes harder to tell), and also to avoid migration issues when messages change.
+
+Lets run this asap.
+
+--------------------------
+//EDIT//: deleteEqualMessages.php has been completed on the following wikis:
+{P1988}",1358039640,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_description,resolved
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSrzRPvwY2u4JUTPlju} [2018-07-18T05:11:41Z] <Krinkle> mwscript deleteEqualMessages.php --wiki dewiki (1 page) - T45917",1531890702,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSrzN-hwY2u4JUTPljt} [2018-07-18T05:11:27Z] <Krinkle> mwscript deleteEqualMessages.php --wiki ruwiki (4 pages) - T45917",1531890688,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSrzKYowY2u4JUTPljs} [2018-07-18T05:11:13Z] <Krinkle> mwscript deleteEqualMessages.php --wiki frwiki (5 pages) - T45917",1531890673,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSryx3NoDEJc1hAykSQ} [2018-07-18T05:09:32Z] <Krinkle> mwscript deleteEqualMessages.php --wiki metawiki (deleted 1 page) - T45917",1531890573,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWSrywV9oDEJc1hAykSP} [2018-07-18T05:09:26Z] <Krinkle> mwscript deleteEqualMessages.php --wiki test2wiki (deleted 2 pages) - T45917",1531890567,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVsHFYbVlCyyDMEPvX-7} [2017-03-25T20:08:22Z] <Krinkle> Ran mwscript deleteEqualMessages.php on public wikis (T45917) - deleted 5 pages across 5 wikis",1490472503,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVruLkTylCyyDMEPvWIy} [2017-03-21T00:04:54Z] <Krinkle> mwscript deleteEqualMessages.php on public wikis (T45917)",1490054696,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> if dry run, where to publish it. (https://people.wikimedia.org/~krinkle/ maybe?)
+
+That would be ok. On the other hand, this list already proves that LocalisationUpdate is needed and must be faster, to avoid accumulating translator frustration and unnecessary technical debt (see ruwiki example: https://ru.wikipedia.org/w/index.php?title=MediaWiki%3ACreate-local&type=revision&diff=84144899&oldid=84144800 https://translatewiki.net/w/i.php?title=MediaWiki%3ACreate-local%2Fru&type=revision&diff=7293894&oldid=5453967 ).",1489915878,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#3083680, @Amire80 wrote:
+>>>! In T45917#3083285, @Nemo_bis wrote:
+>> So if anything we should have a cronjob with a dry run, which triggers an alert somewhere when messages get translated locally. [..]
+> 
+> I regularly check Special:AllMessages //in languages that I know//. I wish it was done in all languages, but I alone don't have the capacity to do it manually. [..]
+
+If I understand correctly, you're looking for instances of where the translation is overridden and not equal - e.g. to find potential improvements that could be upstreamed. I'm not sure how to automate that since many of those will be semi-permanent local modifications that are specific to the wiki.
+
+However if we want to find out about translations that were once local overrides but are now redundant (presumably due to it being upstreamed), I could run the maintenance script that this task is about, from a cron on terbium.
+
+It's only been 10 days, but there are already plenty of translations detected again that are now equal:
+```
+foreachwikiindblist 'all - private' deleteEqualMessages.php | tee out-deleteEqualMessages-allwikis-dry.log
+-----------------------------------------------------------------
+aawiki
+-----------------------------------------------------------------
+aawiki:  Checking for pages with default message...
+aawiki:  ... fetching message info for content language
+aawiki:  done.
+-----------------------------------------------------------------
+```
+Filtered output:
+```lines=5
+$ grep '*' out-deleteEqualMessages-allwikis-dry.log 
+bnwiki:  * [[মিডিয়াউইকি:Cite references link many format backlink labels]]
+cebwiki:  * [[MediaWiki:Loginreqlink]]
+commonswiki:  * [[MediaWiki:Kartographer.js]]
+donatewiki:  * [[MediaWiki:Donate interface-problemsdonating]]
+donatewiki:  * [[MediaWiki:Fundraiserlandingpage-wmch-landing-page]]
+elwiki:  * [[MediaWiki:Ep-addstudents-btn]]
+elwiki:  * [[MediaWiki:Ep-user-roles-message-additional]]
+guwikisource:  * [[મીડિયાવિકિ:Common.js]]
+guwikisource:  * [[મીડિયાવિકિ ચર્ચા:Common.js]]
+guwikisource:  * [[મીડિયાવિકિ:Proofreadpage quality3 category]]
+hrwiktionary:  * [[MediaWiki:Prefs-personal]]
+mkwiki:  * [[МедијаВики:Searchresults-title]]
+plwiki:  * [[MediaWiki:Wm-license-cc-wiki-link]]
+plwiki:  * [[MediaWiki:Wikieditor-toolbar-tool-link-int-target]]
+plwiki:  * [[MediaWiki:Wikieditor-toolbar-tool-link-int-text]]
+plwiki:  * [[MediaWiki:Geodata-broken-tags-category]]
+ruwiki:  * [[MediaWiki:Create-local]]
+trwiki:  * [[MediaWiki:Autosumm-blank]]
+trwiki:  * [[MediaWiki:Group-interface-editor]]
+trwiki:  * [[MediaWiki:Grouppage-interface-editor]]
+trwikibooks:  * [[MediaWiki:Autosumm-blank]]
+trwikiquote:  * [[MediaWiki:Autosumm-blank]]
+trwikisource:  * [[MediaWiki:Autosumm-blank]]
+trwiktionary:  * [[MediaWiki:Autosumm-blank]]
+trwiktionary:  * [[MediaWiki tartışma:Autosumm-blank]]
+ukwikivoyage:  * [[MediaWiki:Group-uploader]]
+ukwikivoyage:  * [[MediaWiki:Group-uploader-member]]
+ukwikivoyage:  * [[MediaWiki:Wikibase-otherprojects-wikipedia]]
+ukwikivoyage:  * [[MediaWiki:Interlanguage-link-wikipedia]]
+ukwikivoyage:  * [[MediaWiki:Interlanguage-link-commons]]
+```
+
+I'm open for ideas on whether to schedule this periodically, as dry run or not, and if dry run, where to publish it. (<https://people.wikimedia.org/~krinkle/> maybe?)",1489809250,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#3083285, @Nemo_bis wrote:
+> So if anything we should have a cronjob with a dry run, which triggers an alert somewhere when messages get translated locally. It could be one useful signal of an insufficient frequency of localisation updates, due to broken LocalisationUpdate or other reasons. (In general, we already know that the updates must be daily; but contingent data points are still useful.)
+
+This.
+
+I regularly check Special:AllMessages //in languages that I know//. I wish it was done in all languages, but I alone don't have the capacity to do it manually. I very frequently find not only translation mistakes, but also reasons to fix the original English message, and of course this happens not only when the local customization is the same as the original message, but also when it's different.
+
+It's good to have local translation in the MediaWiki space as a quick fix for particularly bad translation mistakes, or for actually-needed local customizations, but it must not be relied upon as a an actual way to translate the interface, even temporarily. (And even though I'm saying ""actually-needed local customization"", these should actually always raise the question of whether this thing should be done through a message at all, but that's a separate topic.)",1488969396,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","So if anything we should have a cronjob with a dry run, which triggers an alert somewhere when messages get translated locally. It could be one useful signal of an insufficient frequency of localisation updates, due to broken LocalisationUpdate or other reasons. (In general, we already know that the updates must be daily; but contingent data points are still useful.)",1488962701,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","That's what I'm saying. The usual reason people were editing the messages was because LU was broken, or there was a long time between deploys.
+
+I'm not even suggesting we encourage people to edit the MW namespace like that",1488923437,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I agree with @nemo_bis why force people to do something they dont want to, especially if we have the ability to do it ourselves. ",1488922841,PHID-USER-ct4qymje4lpxby255tze,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> People that don't want to wait for train deploys and/or LocalisationUpdate?
+
+Forcing such people to edit the MediaWiki namespace would be a broken system.",1488922637,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#3081939, @Nemo_bis wrote:
+>> Any reason we can't cronjob it, say monthly?
+> 
+> This is supposed not to be a recurring task on each wiki: if it's needed regularly, then something is wrong.
+
+People that don't want to wait for train deploys and/or LocalisationUpdate?",1488922530,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> Any reason we can't cronjob it, say monthly?
+
+This is supposed not to be a recurring task on each wiki: if it's needed regularly, then something is wrong.",1488922193,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","It'd be interesting to see the scale of this in relation to T158360...
+
+Any reason we can't cronjob it, say monthly?",1488917248,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","@MarcoAurelio Thanks. Yeah, my thoughts exactly. This should be re-run from time to time as upstreaming happens all the time.
+
+Meanwhile, as always, feel free to ask here or on IRC for a run on a specific wiki (or set of wikis).",1488916953,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","@MarcoAurelio Thanks. Yeah, my thoughts exactly. This should be re-run from time to time as upstreaming happens all the time.
+
+Meanwhile, as always, feel free to ask here on IRC for a run on a specific wiki (or set of wikis).",1488916940,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","@MarcoAurelio Thanks. Yeah, my thoughts exactly. This should be re-run from time to time as upstreaming happens all the time.",1488916895,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","We should do this once or twice a year. Nice job, thanks.",1488893219,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVqnN6AAHQCSeVEJfRZs} [2017-03-07T05:22:04Z] <Krinkle> foreachwikiindblist 'all - closed - private' deleteEqualMessages.php (T45917) - purge upstreamed translations from remaining wikis",1488864127,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVqm0BIAlCyyDMEPvRe-} [2017-03-07T03:28:58Z] <Krinkle> foreachwikiindblist closed deleteEqualMessages.php (T45917) - purge upstreamed translations from closed wikis",1488857338,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVpoVYifQMK9DA-FKjFz} [2017-02-23T00:18:40Z] <Krinkle> mwscript deleteEqualMessages.php --wiki simplewikibooks (T45917)",1487809120,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVnODfVMHQCSeVEJfEH0} [2017-01-24T01:18:58Z] <Krinkle> mwscript deleteEqualMessages.php --wiki gotwiki (T45917)",1485220738,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",@Krinkle: Maybe https://meta.wikimedia.org/wiki/Steward_requests/Miscellaneous#All_local_mediawiki_messages_on_got.wikipedia.org_should_be_deleted is of interest here. Thanks.,1485096966,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVlreqFoHQCSeVEJe_Xe} [2017-01-04T21:55:15Z] <Krinkle> mwscript deleteEqualMessages.php --wiki nowikinews (T45917)",1483566916,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVlreoZdHQCSeVEJe_Xd} [2017-01-04T21:55:08Z] <Krinkle> mwscript deleteEqualMessages.php --wiki nowiki (T45917)",1483566909,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2822892, @MarcoAurelio wrote:
+> Can angwiki be run next? Thanks.
+
+:white_check_mark: Done!",1480114888,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2822892, @MarcoAurelio wrote:
+> Can angwiki be run next? Thanks.
+
+Done :)",1480104613,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVidG31FHQCSeVEJeyWR} [2016-11-25T20:09:34Z] <Krinkle> mwscript deleteEqualMessages.php --wiki angwiki (T45917)",1480104574,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Can angwiki be run next? Thanks.,1480071561,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhFB-pNQMK9DA-FJhuN} [2016-11-08T17:41:36Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki ptwikinews (T45917)",1478626896,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhEvj7xQMK9DA-FJhrT} [2016-11-08T16:21:08Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki kkwiki (T45917)",1478622068,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhBM2zgHQCSeVEJesuz} [2016-11-07T23:50:39Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki jawikinews (T45917)",1478562639,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhBIxJ3HQCSeVEJesuW} [2016-11-07T23:32:47Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki jawikibooks (T45917)",1478561567,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVhBEtxkHQCSeVEJestw} [2016-11-07T23:15:04Z] <Krinkle> mwscript --deleteEqualMessages.php --wiki gawiktionary (T45917)",1478560505,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AVd9IhIcfIH_7EDsrdXG} [2016-09-30T22:06:07Z] <Krinkle> Re-run mwscript deleteEqualMessages.php on all wikis it was previously run on (T45917) ",1475273167,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570454, @MuhammadShuaib wrote:
+> @Dereckson, Will you export for me urwiki mediawiki messeges which do not exist on translatewiki? I can help which messeges to be imported to translatewiki. 
+
+Thanks, this is important work. :)",1471807228,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Here the list of messages to export:
+
+{P3863}
+
+You need to clean it: remove any Wikipedia or Wikimedia message.
+
+The goal is to:
+  - translate on wiki Wikimedia/Wikipedia messages
+  - translate on TranslateWiki universal messages
+
+",1471799443,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","@Dereckson, Will you export for me urwiki mediawiki messeges which do not exist on translatewiki? I can help which messeges to be imported to translatewiki. ",1471792632,PHID-USER-xfrkgxsnlepm7r3bx43d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVatnr1JpirJUPGy-ySY} [2016-08-21T15:01:16Z] <Dereckson> Run deleteEqualMessages maintenance script on urwiki (T45917)",1471791677,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570412, @Dereckson wrote:
+> We can sorry :)
+
+Thanks, Okay, I wish to delete those messeges which have same value on both wiki. ",1471791515,PHID-USER-xfrkgxsnlepm7r3bx43d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",We can sorry :),1471791402,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570408, @Dereckson wrote:
+> We can't start to delete messages with the same values on ur. and TranslateWiki if you wish.
+> 
+> That would delete 297 messages with the (identical) translation already on TranslateWiki.
+
+You can't? :)",1471791369,PHID-USER-xfrkgxsnlepm7r3bx43d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","We can't start to delete messages with the same values on ur. and TranslateWiki if you wish.
+
+That would delete 297 messages with the (identical) translation already on TranslateWiki.",1471791248,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","We can't start to delete messages with the same values on ur. and TranslateWiki if you wish.
+
+That would delete 297 messages.",1471791220,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",We can't start to delete messages with the same values on ur. and TranslateWiki.,1471791155,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570406, @Dereckson wrote:
+> Yes but that's exactly the problem.
+> 
+> TranslateWiki manages the translation for EVERY wiki un Urdu (and you can set every installation of MediaWiki in Urdu just adding ?uselang=ur).
+> 
+> Wikimedia and Wikipedia specific translations should be done on wiki.
+> 
+> Universal translations should be done on TranslateWiki.
+> 
+> So yes, we can export translations from ur.wikipedia to import them to TranslateWiki, but there is a need to know what messages to import, what not.
+
+In that case, Will you delete mediawiki: messeges on ur.wiki? Because now we are translating on translatewiki. ",1471790490,PHID-USER-xfrkgxsnlepm7r3bx43d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Yes but that's exactly the problem.
+
+TranslateWiki manages the translation for EVERY wiki un Urdu (and you can set every installation of MediaWiki in Urdu just adding ?uselang=ur).
+
+Wikimedia and Wikipedia specific translations should be done on wiki.
+
+Universal translations should be done on TranslateWiki.
+
+So yes, we can export translations from ur.wikipedia to import them to TranslateWiki, but there is a need to know what messages to import, what not.",1471790303,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#2570356, @Dereckson wrote:
+> The issue is how to sort them between Wikimedia-specific messages and universal messages for every wikis?
+
+I want it for specific wiki, ur.wiki",1471787975,PHID-USER-xfrkgxsnlepm7r3bx43d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",The issue is how to sort them between Wikimedia-specific messages and universal messages for every wikis?,1471784540,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Is this possible to move mediawiki: namespace translations to translatewiki.net? Previously we had translated huge amount of mediawiki software strings locally. Some have been outdated but many of them are useful. And now we would like to continue translate on translatewiki. ,1471752189,PHID-USER-xfrkgxsnlepm7r3bx43d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVafiUcdX4d8bmU7pfbN} [2016-08-18T21:23:09Z] <Dereckson> Run deleteEqualMessages maintenance script on eswikibooks, eswikiquote, eswikisource, eswiktionary and eswikiversity (T45917)",1471555389,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Done.
+
+{P3852}",1471555245,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I'm handling the es part, then I'll reassign the task to Krinkle for review and closure.",1471554376,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Doing a quick check, I've encountered the same problems at the rest of Spanish language projects, as such I propose to run the script on:
+
+* eswikibooks
+* eswikiquote
+* eswikisource
+* eswiktionary
+* eswikiversity
+
+Thank you.",1471552138,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Requesting the script to be run on es.wikisource as per https://es.wikisource.org/w/index.php?title=Especial%3ATodosLosMensajes&prefix=&filter=modified&lang=es&limit=5000
+
+Lots of local messages equal to the source in TWN.
+
+Thank you!",1471551990,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVUIBSXNgCrwkbTdmSYI} [2016-05-31T18:13:23Z] <Krinkle> mwscript deleteEqualMessages.php --wiki hrwikibooks (T45917)",1464718403,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVUDAGmt1EdYBLP_75C3} [2016-05-30T18:50:06Z] <Krinkle> mwscript deleteEqualMessages.php --wiki nvwiki (T45917)",1464634207,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTknVjG1EdYBLP_72u_} [2016-05-24T21:13:17Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki mrwiki (T45917)",1464124398,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTkYTJ_gCrwkbTdmPef} [2016-05-24T20:07:35Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki diqwiki (T45917)",1464120456,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTkVf57sSQjJM_mrtuk} [2016-05-24T19:55:21Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki cywiktionary (T45917)",1464119721,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTkTHRTgCrwkbTdmPdj} [2016-05-24T19:44:56Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki warwiki (T45917)",1464119096,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVTjg8HA1EdYBLP_72ig} [2016-05-24T16:05:43Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki fiwikinews (T45917)",1464105943,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQM0ZS2D0x0K5Df_Smj} [2016-04-12T23:32:22Z] <Krinkle>  mwscript deleteEqualMessages.php --wiki elwiki (T45917)",1460503942,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHoFN2gCrwkbTdl-Hq} [2016-04-11T23:20:28Z] <Krinkle> mwscript deleteEqualMessages.php --wiki idwiki (T45917)",1460416828,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHmQ5I1EdYBLP_7mNA} [2016-04-11T23:12:31Z] <Krinkle> mwscript deleteEqualMessages.php --wiki zh_classicalwiki (T45917)",1460416352,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHOvKAD0x0K5Df_R_k} [2016-04-11T21:29:44Z] <Krinkle> mwscript deleteEqualMessages.php --wiki bgwikiquote (T45917)",1460410184,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHOuy9gCrwkbTdl-ET} [2016-04-11T21:29:42Z] <Krinkle> mwscript deleteEqualMessages.php --wiki frwikibooks (T45917)",1460410183,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQHDv3n1EdYBLP_7mIC} [2016-04-11T20:41:43Z] <Krinkle> mwscript deleteEqualMessages.php --wiki plwiki (T45917)",1460407304,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQDoTWOD0x0K5Df_RpN} [2016-04-11T04:42:57Z] <Krinkle> mwscript deleteEqualMessages.php --wiki shwiki (T45917)",1460349777,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQCZCaKD0x0K5Df_RoZ} [2016-04-10T22:56:38Z] <Krinkle> mwscript deleteEqualMessages.php --wiki srwiki (T45917)",1460328999,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQCP56LgCrwkbTdl9qq} [2016-04-10T22:16:44Z] <Krinkle> mwscript deleteEqualMessages.php --wiki yowiki (T45917)",1460326604,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVQCLBWxgCrwkbTdl9qj} [2016-04-10T21:55:24Z] <Krinkle> mwscript deleteEqualMessages.php --wiki trwikimedia (T45917)",1460325324,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVPepXiHD0x0K5Df_P7O} [2016-04-04T00:21:39Z] <Krinkle> mwscript deleteEqualMessages.php --wiki ruwiki (T45917)",1459729299,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVPeRhqty3uubrspqdd0} [2016-04-03T22:37:29Z] <Krinkle> mwscript deleteEqualMessages.php --wiki eswiki --lang-code ca (T45917)",1459723049,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVPeRglHy3uubrspqddz} [2016-04-03T22:37:25Z] <Krinkle> mwscript deleteEqualMessages.php --wiki eswiki (T45917)",1459723046,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVPLTHP8y3uubrspqcNy} [2016-03-31T06:11:38Z] <Krinkle> mwscript deleteEqualMessages.php --wiki zh_min_nanwiki (T45917)",1459404699,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","{nav icon=file, name=Mentioned in SAL, href=https://tools.wmflabs.org/sal/log/AVOnA0SngCrwkbTdl4Pi} [2016-03-24T05:05:22Z] <Krinkle> mwscript deleteEqualMessages.php --wiki zhwikiquote (T45917 , P1988)",1458795922,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> Has this now all been done and resolved?
+
+Not that I know.",1452678979,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Has this now all been done and resolved?,1452622160,PHID-USER-lumvg23bxmfbvekr2fbo,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#1841781, @Jdforrester-WMF wrote:
+> What is left to do here?
+
+Running on all wikis.",1449002935,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",What is left to do here?,1448988458,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+rowiki: 432 pages
+zhwiktionary: 143 pages
+fywiktionary: 65 pages
+pmswiki: 391 pages
+```",1441593011,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+rowiki: 432 pages
+zhwiktionary: 143 pages
+fywiktionary: 65 pages
+```",1441556987,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+rowiki: 432 pages
+zhwiktionary: 143 pages
+```",1440638349,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+rowiki: 432 pages
+```",1440638311,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+ocwiki: 862 pages
+```",1440615416,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for a few more wikis:
+
+```
+eowiki: 129 pages
+euwiki: 740 pages
+frpwiki: 2 pages
+frwiki: 48 pages
+huwiki: 7 pages
+kawiki: 777 pages
+```",1440521878,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Maybe it can be used to clean old translations such as [[https://meta.wikimedia.org/w/index.php?title=Special%3AAllMessages&prefix=&filter=modified&lang=eu&limit=5000|these ones]] at Meta? (included other langs). Thread opened at Babel.,1439156148,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran it for a two more wikis after inspecting the dry-run:
+
+```
+cewiki: 243 pages
+sawiki: 58 pages
+```",1434167492,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran it for these wikis:
+```
+mediawikiwiki
+* [[MediaWiki:Wikilove-barnstar-resilient-desc]]
+* [[MediaWiki:Wikilove-barnstar-tireless-desc]]
+* [[MediaWiki:Code-referenced]]
+* [[MediaWiki:Rss-item]]
+
+nlwiki
+* [[MediaWiki:Logentry-block-block]]
+* [[MediaWiki:Logentry-block-unblock]]
+* [[MediaWiki:Centralauth-uwbr-name]]
+* [[MediaWiki:Centralauth-uwbr-registration]]
+* [[MediaWiki:Centralauth-uwbr-editcount]]
+* [[MediaWiki:Centralauth-uwbr-intro]]
+* [[MediaWiki:Sandboxlink-subpage-name]]
+* [[MediaWiki:Sandboxlink-portlet-label]]
+
+commonswiki: 0
+metawiki: 0
+```",1431010787,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",">>! In T45917#1152012, @Krenair wrote:
+> Is there a reason we haven't done this on all wikis now?
+
+No good one. It's fine to proceed.",1427358499,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Is there a reason we haven't done this on all wikis now?
+
+{P436}",1427334122,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran for commonswiki per my own request there as sysop (could've deleted them by hand):
+
+
+> 279 pages in the MediaWiki namespace override messages.
+> 1 pages are equal to the default message (+ 0 talk pages).
+> 
+> List:
+> * [[MediaWiki:Visualeditor-ca-editsource]]",1409147479,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Spread over the past two weeks, mwscript deleteEqualMessages.php was ran[1] on the following wikis while performing other routine maintenance and interface fixes:
+
+abwiki
+afwiki
+afwikiquote
+alswiki
+bat-smgwiki
+bpywiki
+cswiki
+cswikiversity
+cswiktionary
+cvwiki
+lnwiki
+nahwiktionary
+newwiki
+nlwiki
+rowiktionary
+simplewiki
+sqwiki
+suwiki
+tlwiki
+
+[1] https://wikitech.wikimedia.org/wiki/Server_admin_log",1399337202,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to Nemo from comment #26)
+> Thanks! I'd suggest to avoid touching talk pages, so that the operation is
+> truly no-op. Those talk pages are unlikely to exist but wikis have different
+> policies on the matter.
+
+Good point. We have orphan tools to detect those and are indeed not always trivial/uncontroversial. Will keep them from now on.",1398283925,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Thanks! I'd suggest to avoid touching talk pages, so that the operation is truly no-op. Those talk pages are unlikely to exist but wikis have different policies on the matter.",1398282173,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Ran mwscript deleteEqualMessages.php --delete --delete-talk on the following wikis:
+
+* afwiki
+* amwiki
+* brwiki
+* euwiktionary
+* gvwiki
+* hrwiki
+* hrwiktionary
+* iawiki
+* miwiki
+* mlwiki",1398281729,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Done!
+
+$ mwscript deleteEqualMessages.php --wiki wuuwiki --delete
+
+Checking for pages with default message...
+... fetching message info for content language
+352 pages in the MediaWiki namespace override messages.
+110 pages are equal to the default message (+ 0 talk pages).
+
+...deleting equal messages (this may take a long time!)...
+* [[MediaWiki:Sitematrix]]
+* [[MediaWiki:Cite]]
+* [[MediaWiki:Searchfulltext]]
+* [[MediaWiki:Createarticle]]
+* [[MediaWiki:Categorytree-mode-categories]]
+* [[MediaWiki:Categorytree-expand]]
+* [[MediaWiki:Categorytree-no-pages]]
+* [[MediaWiki:Sitesupport]]
+* [[MediaWiki:Fri]]
+* [[MediaWiki:January-gen]]
+* [[MediaWiki:March-gen]]
+* [[MediaWiki:May-gen]]
+* [[MediaWiki:September-gen]]
+* [[MediaWiki:October-gen]]
+* [[MediaWiki:November-gen]]
+* [[MediaWiki:Mypage]]
+* [[MediaWiki:History short]]
+* [[MediaWiki:Print]]
+* [[MediaWiki:Mainpage]]
+* [[MediaWiki:Nstab-template]]
+* [[MediaWiki:Logout]]
+* [[MediaWiki:Userlogout]]
+* [[MediaWiki:Notloggedin]]
+* [[MediaWiki:Loginerror]]
+* [[MediaWiki:Loginsuccesstitle]]
+* [[MediaWiki:Wrongpassword]]
+* [[MediaWiki:Bold sample]]
+* [[MediaWiki:Bold tip]]
+* [[MediaWiki:Savearticle]]
+* [[MediaWiki:Loginreqtitle]]
+* [[MediaWiki:Loginreqlink]]
+* [[MediaWiki:Yourdiff]]
+* [[MediaWiki:Nohistory]]
+* [[MediaWiki:Nextrevision]]
+* [[MediaWiki:Rev-delundel]]
+* [[MediaWiki:Prevn]]
+* [[MediaWiki:Prefs-personal]]
+* [[MediaWiki:Prefs-rc]]
+* [[MediaWiki:Prefs-watchlist]]
+* [[MediaWiki:Prefs-watchlist-days]]
+* [[MediaWiki:Prefs-watchlist-edits]]
+* [[MediaWiki:Saveprefs]]
+* [[MediaWiki:Searchresultshead]]
+* [[MediaWiki:Savedprefs]]
+* [[MediaWiki:Yourlanguage]]
+* [[MediaWiki:Badsig]]
+* [[MediaWiki:Userrights-user-editname]]
+* [[MediaWiki:Rclistfrom]]
+* [[MediaWiki:Diff]]
+* [[MediaWiki:Hist]]
+* [[MediaWiki:Show]]
+* [[MediaWiki:Minoreditletter]]
+* [[MediaWiki:Newpageletter]]
+* [[MediaWiki:Uploadbtn]]
+* [[MediaWiki:Uploadnologin]]
+* [[MediaWiki:Uploaderror]]
+* [[MediaWiki:Uploadlog]]
+* [[MediaWiki:Uploadlogpagetext]]
+* [[MediaWiki:Filedesc]]
+* [[MediaWiki:Uploadedfiles]]
+* [[MediaWiki:Uploadwarning]]
+* [[MediaWiki:Savefile]]
+* [[MediaWiki:Destfilename]]
+* [[MediaWiki:Uploadnewversion-linktext]]
+* [[MediaWiki:Download]]
+* [[MediaWiki:Listredirects]]
+* [[MediaWiki:Randompage]]
+* [[MediaWiki:Statistics]]
+* [[MediaWiki:Brokenredirects]]
+* [[MediaWiki:Popularpages]]
+* [[MediaWiki:Mostlinked]]
+* [[MediaWiki:Mostlinkedcategories]]
+* [[MediaWiki:Mostimages]]
+* [[MediaWiki:Shortpages]]
+* [[MediaWiki:Longpages]]
+* [[MediaWiki:Listusers]]
+* [[MediaWiki:Newpages-username]]
+* [[MediaWiki:Log]]
+* [[MediaWiki:Emailsend]]
+* [[MediaWiki:Emailsent]]
+* [[MediaWiki:Emailsenttext]]
+* [[MediaWiki:Watchthispage]]
+* [[MediaWiki:Unwatchthispage]]
+* [[MediaWiki:Created]]
+* [[MediaWiki:Confirm]]
+* [[MediaWiki:Deletionlog]]
+* [[MediaWiki:Rollback]]
+* [[MediaWiki:Rollback short]]
+* [[MediaWiki:Rollbackfailed]]
+* [[MediaWiki:Protectlogpage]]
+* [[MediaWiki:Restriction-edit]]
+* [[MediaWiki:Restriction-move]]
+* [[MediaWiki:Undeletepage]]
+* [[MediaWiki:Mycontris]]
+* [[MediaWiki:Blocklink]]
+* [[MediaWiki:Blocklogpage]]
+* [[MediaWiki:Movepagebtn]]
+* [[MediaWiki:Cantmove-titleprotected]]
+* [[MediaWiki:Thumbnail-more]]
+* [[MediaWiki:Newimages]]
+* [[MediaWiki:Variantname-zh-tw]]
+* [[MediaWiki:Watchlistall2]]
+* [[MediaWiki:Namespacesall]]
+* [[MediaWiki:Descending abbrev]]
+* [[MediaWiki:Table pager next]]
+* [[MediaWiki:Table pager prev]]
+* [[MediaWiki:Table pager first]]
+* [[MediaWiki:Table pager limit]]
+* [[MediaWiki:Autoredircomment]]
+* [[MediaWiki:Version]]
+
+done!",1395422702,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",This was requested to be run on wuuwiki: https://meta.wikimedia.org/w/index.php?title=Steward_requests/Miscellaneous&oldid=7913568#Remove_useless_system_messages_on_wuu_wikipedia,1395422161,PHID-USER-omdcggvudfkuawipp23i,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Krinkle, are you still planning to work on this?",1395223025,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","The short version of the long story (that is partially outlined in previous comments by all of you) is that it:
+
+* Was never consistent to be begin with.
+* It has changed over time.
+  So we can't reliably know now what to do with a message. You'd have to account
+  for deployment dates for different wikis and assume a community member
+  intentionally left a message override untouched knowing the new behaviour.
+  More likely it was forgotten about and is actually still assuming the old logic. 
+* It can vary by message whether it is blankable or disableable.
+
+If the code calls isBlank first (like Sitenotice) then it can be blanked with '' without leaving a gap in the interface because the feature checks it first.
+
+If the code calls isDisabled first, and then falls back or something, then it can be blanked with '' or '-' and it will use the default.
+
+However by far the default behaviour for the majority of messages is that if you create a local page, it replaces the message with that page. And if you put '' or '-' in it, it will appear as a gap in the interface.
+
+Either way, those pages are there with empty content for a reason, so it doesn't make sense to delete them en mass as part of this maintenance script.",1381358925,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Blanking a message no longer disables it (bug 14176), so all pre-12.06.2013 blankings should be transformed in deletions.",1381349348,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I'm confused by comment #12 and #13 then, I understood from them that '' no longer meant default.",1381346722,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #16)
+> > Even the ""redundant"" messages getting deleted makes me a little sad, given
+> > how useful some of that page history can be (including being linked from active
+> > bug reports). But I understand that it's better future-proofing. Alas.
+> 
+> I remember blanking some MediaWiki messages precisely to use the default but
+> keep the history.
+> Maybe the script should edit the messages to whatever is used now to mean
+> ""use
+> the default"" (""-"" ?) when there are several edits to the page.
+
+Sometimes '', sometimes '-' (handled by Message:isBlank and Message::isDisabled) however those are not generic APIs. The message system does not use these methods. They are available for local code to use if they want to.
+
+So there's no way of knowing whether an individual message ""supports"" that behaviour, and even then we currently have some use '' and some use '-' ('' is a safe bet for both).",1381345858,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #15)
+> I've run this on a single wiki where I'm also a local sysop (nlwiki) and
+> noticed the script has a minor flaw.
+> 
+> It incorrectly deleted MediaWiki:Sitenotice.
+
+Fixed in I5b416cda25a3641862df9919c46ae59ad5d5d6e0.",1381345737,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","> Even the ""redundant"" messages getting deleted makes me a little sad, given
+> how useful some of that page history can be (including being linked from active
+> bug reports). But I understand that it's better future-proofing. Alas.
+
+I remember blanking some MediaWiki messages precisely to use the default but keep the history.
+Maybe the script should edit the messages to whatever is used now to mean ""use the default"" (""-"" ?) when there are several edits to the page.",1381345333,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I've run this on a single wiki where I'm also a local sysop (nlwiki) and noticed the script has a minor flaw.
+
+It incorrectly deleted MediaWiki:Sitenotice (if it is empty), which is undesirable. So we should probably change the script to make an exception for empty messages.
+
+Those are most unlikely to change anyway because there is no message content to update or change, it is empty.",1381345054,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #13)
+> (In reply to comment #12)
+>> If a script to delete empty messages existed in the past, we could've run it
+>> once globally after we reverted the feature to have blank messages mean
+>> default. But it has been to long to do this now.
+> 
+> What do you mean too long? It's been today for Wikipedias (1.22wmf7). Blank
+> message has always meant ""equal to default"", so it doesn't seem out of scope
+> for the script, which should be run by third parties before upgrading to
+> MediaWiki 1.22.
+
+Not always. The behavior has switched a few times now.
+
+There's no good answer here. It's impossible to determine intent simply by page_len being equal to 0. I tend to agree with Krinkle that it's better to be cautious here.
+
+Even the ""redundant"" messages getting deleted makes me a little sad, given how useful some of that page history can be (including being linked from active bug reports). But I understand that it's better future-proofing. Alas.
+
+> [...] [[MediaWiki 1.22]] [...]
+
+You mean [[mw:MediaWiki 1.22]], of course.",1371778016,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #12)
+> If a script to delete empty messages existed in the past, we could've run it
+> once globally after we reverted the feature to have blank messages mean
+> default. But it has been to long to do this now.
+
+What do you mean too long? It's been today for Wikipedias (1.22wmf7). Blank message has always meant ""equal to default"", so it doesn't seem out of scope for the script, which should be run by third parties before upgrading to MediaWiki 1.22.
+If you consider it out of scope I'd file a bug for another script to be created, but nobody would be working on it so it would become too late so I'll just add a warning on [[MediaWiki 1.22]] and let sysops sort it out manually.",1371761038,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #11)
+> (In reply to comment #10)
+> > Related URL: https://gerrit.wikimedia.org/r/64991 (Gerrit Change
+> > I2680413c276365a44c935a6f6fdd740daa86341e)
+> 
+> Merged a month ago.
+> 
+> Given bug 14176 (bug 49793), the script should also delete blank messages and
+> be run as soon as possible; unless a separate script is prepared and run for
+> that only.
+
+Since blank messages no longer mean showing the default, deleting them seems inappropriate.
+
+Yes, there are likely some pages out there that are blank and currently causing bugs due the message being empty instead of the default. However it would be a mistake to unconditionally delete all blank pages in the MediaWiki namespace.
+
+For maintenance scripts like deleteEqualMessages it is important that they do not affect the interface. It should only delete things that are non-controversial.
+
+If a script to delete empty messages existed in the past, we could've run it once globally after we reverted the feature to have blank messages mean default. But it has been to long to do this now. And one could also argue that it was dangerous even then because there might be existing pages that are blank for other reasons.",1371758984,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #10)
+> Related URL: https://gerrit.wikimedia.org/r/64991 (Gerrit Change
+> I2680413c276365a44c935a6f6fdd740daa86341e)
+
+Merged a month ago.
+
+Given bug 14176 (bug 49793), the script should also delete blank messages and be run as soon as possible; unless a separate script is prepared and run for that only.",1371757399,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Related URL: https://gerrit.wikimedia.org/r/64991 (Gerrit Change I2680413c276365a44c935a6f6fdd740daa86341e),1369264493,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",Related URL: https://gerrit.wikimedia.org/r/62159 (Gerrit Change I2680413c276365a44c935a6f6fdd740daa86341e),1367596599,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #7)
+> (In reply to comment #6)
+> > I could run it, but I'd like to not execute my own request without a little
+> > more consensus from people.
+> > 
+> > They aren't permanent or hidden actions in any way (regular wiki deletions,
+> > it's a bot basically), but they would be a horror to undo.
+> > 
+> 
+> Can you dry run it and make a list of the pages that will be deleted so they
+> can be reviewed before deletion?
+
+I'm not sure what there is to review regarding individual pages. They all follow the same description, whatever reasoning one would use about them doesn't specify for any particular page:
+
+ Pages in the MediaWiki namespace that exist and override a system message
+ of which the wiki page contents are equal to the system message of the site
+ language (in other words, there is no longer a reason fo the override page
+ to exist).
+
+Deleting these pages has no visible effect as the effective value of the interface message will still be the same.
+
+The advantage is saving maintenance work later on by not having to update these messages when the software upgrades, and for consistency across wikis.
+
+A common scenario is the following:
+* 3 wikis in language x
+* 1 of the wikis overrides a message (making an improvement)
+* the message is fixed in translatewiki
+* the message update is deployed
+* users of all 800 wikis using language x now see the new version of the message
+* another update is made to the message and deployed
+* all wikis use it, except the wiki where the first change came from which is now out of sync without it being intentionally so.
+
+
+Alright, I'm biased as it was my own idea. But that doesn't mean the script itself has to be controversial. I'll run this next week if no objections are raised before then.",1365712467,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","**Thehelpfulonewiki** wrote:
+
+(In reply to comment #6)
+> I could run it, but I'd like to not execute my own request without a little
+> more consensus from people.
+> 
+> They aren't permanent or hidden actions in any way (regular wiki deletions,
+> it's a bot basically), but they would be a horror to undo.
+> 
+
+Can you dry run it and make a list of the pages that will be deleted so they can be reviewed before deletion?",1362516836,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","I could run it, but I'd like to not execute my own request without a little more consensus from people.
+
+They aren't permanent or hidden actions in any way (regular wiki deletions, it's a bot basically), but they would be a horror to undo.
+
+I wouldn't know why someone would disagree, but then again, there've only been a few people involved so far that all agreed.",1362512294,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","**Thehelpfulonewiki** wrote:
+
+Any progress on running this?",1362038010,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages",See bug 43915.,1358895498,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","(In reply to comment #2)
+> Can the old [[User:MediaWiki default]] be used for this task?
+
+The script I wrote uses that user and ensures it is in the bot group  (that is, add if not present) before it runs.
+
+(In reply to comment #2)
+> I understand this is going to affect messages pre-betawiki.
+
+No, it is not.
+
+(In reply to comment #2)
+> However I  what would happen with messages that we decided to customize
+
+Nothing.",1358895477,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","Can the old [[User:MediaWiki default]] be used for this task? (Please note that since it does not run since 2006 it has been deflagged from the bot group from some projects).
+
+I understand this is going to affect messages pre-betawiki. However I wonder what would happen with messages that we decided to customize localy. Those should not be deleted as they're likely going to be recreated later... Only a minor issue, though.",1358729054,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+"Delete all redundant ""MediaWiki"" pages for system messages","This is a subset of the general task ""clean-up local messages"".
+What we have now:
+[[mw:Localisation#Old_local_translation_system]]
+https://toolserver.org/~robin/?tool=cleanuplocalmsgs",1358041581,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-odpakiqqpzglf5pzvu3o,task_subcomment,NA
+Batch Parsoid's API requests,"We should amortize per-request overheads by batching API requests.
+
+AFAIK there is no generic batching support in the API currently, and adding it would probably be a bit too time-consuming for now. Instead we can add a unique string as a separator, for example something like 
+
+<nowiki>d41d8cd98f00b204e9800998ecf8427e</nowiki>
+
+This would work for for action=expandtemplates and action=parse which are the main workarounds we currently use. In the longer term we should switch to explicit methods that don't involve parsing wikitext, which is probably also a good moment to add real batching support.
+
+Decisions about batch sizes could be based on wikitext source size initially (based on the assumption that templates with a bazillion parameters also take longer to expand). A fixed number of templates per batch would be another simple alternative. Really fancy batching could use stats of previous processing times (returned by the PHP preprocessor per transclusion and stored in HTML).
+
+Ideally we would also enforce separation between batched requests to avoid non-deterministic behavior for stateful extensions.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1357943520,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_description,resolved
+Batch Parsoid's API requests,"@ssastry, good point re load. Added the parse request rate for completeness. Also agreed re needing more data.",1443744632,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"@ssastry, good point re load. Added the parse request rate for completeness.",1443744450,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"@subbu, good point re load. Added the parse request rate for completeness.",1443744437,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"You need to account for the spikiness in the load too. see http://grafana.wikimedia.org/#/dashboard/db/parsoid-timing-wt2html (zoom out to a 7-day window and look how the request rate was much closer to 200 reqs / sec last few days compared to < 150 reqs / sec earlier in the week (before batching was enabled). I am fairly confident that parsing latencies haven't been affected adversely based on monitoring this last couple days. But, I think we have to wait and watch this over the next couple weeks before we have a truer picture. 
+
+On the other hand, if you look at ganglia graphs for the API cluster, you do see a reduction in network traffic in/out of it (despite the higher parse load on the Parsoid end) + a downward trend in the load there.",1443743973,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th, around 16:14 UTC. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}
+
+Smoothed parse request rate:
+{F2652092}",1443744961,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th, around 16:14 UTC. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}
+
+Smoothed parse request rate:
+{F2652078}",1443744831,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th, around 16:14 UTC. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}
+
+Parse request rate:
+{F2652035}",1443744407,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th, around 16:14 UTC. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443744243,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen)):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443743533,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Batching was fully enabled on Sept 29th. 12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443743341,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"12-hour median latencies as seen by RESTBase in the last days (smoothed version of [this graph](http://grafana.wikimedia.org/#/dashboard/db/restbase?panelId=9&fullscreen):
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443743180,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"12-hour median latencies as seen by RESTBase in the last days:
+
+P99:
+{F2651940}
+
+Mean:
+{F2651943}",1443743150,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Change 227208 merged by jenkins-bot:
+Batch MW parser and imageinfo API requests
+
+[[https://gerrit.wikimedia.org/r/227208]]",1439607321,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Change 227208 had a related patch set uploaded (by Tim Starling):
+Batch MW parser and imageinfo API requests
+
+[[https://gerrit.wikimedia.org/r/227208]]
+",1438000591,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Sounds good to me since it looks like it keeps complexity down implementing this since the code can be customized to Parsoid's needs. But, once this is all ironed out and live, we should update docs for 3rd party Parsoid installs about requirement (unless batching can be made optional on the Parsoid end).",1437963707,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"@tstarling +1 from me. Your rationale covers all the things I would have brought up (and more). Sorry for being slow, @ssastry is vacationing and I'm not sure if @cscott's been following this thread.",1437781827,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,@tstarling +1 from me. Your rationale covers all the things I would have brought up (and more). Sorry for being @ssastry is vacationing and I'm not sure if @cscott's been following this thread.,1437781808,PHID-USER-gxcjmjpejlhfnrquksm2,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"No response, so I committed the MW extension to https://gerrit.wikimedia.org/r/#/c/226670/
+
+Still ironing out a couple of issues on the client side. A changeset will appear soon.",1437781171,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Please comment on the idea of doing batch parsing in an extension instead of in a core API module. I'd like to know if it sounds like a good idea before I create the Gerrit repository.
+
+The reasons for doing this were:
+* Simpler design, due to the smaller number of clients/stakeholders. Code size is only 135 physical lines, with no internal API calls, compared to 800 for action=parse and 218 for action=expandtemplates.
+* Allows the action=parse and action=expandtemplates modules to be easily combined. No need to break my head trying to think about generic Lua frontend batch processing APIs which allow arbitrary actions to be combined.
+* An API for parsoid use only can easily be policed for misuse or DoS, e.g. with IP-based access control. No need for restrictive server-side batch size limits which may interfere with optimal performance.
+* Expedient output format, based on b/c with action=parse and action=expandtemplates, which allows the client to share code with the fallback case.
+* Forking the API provides an easy path towards more aggressive integration with the MW parser, for example output annotation hooks.
+
+The proposed extension name is ParsoidBatchAPI.",1437369948,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"I've written a client-side ""batcher"" class hierarchy, and a MediaWiki extension which does server-side batches of mixed parse and preprocess operations. The impact on both client and server CPU time is substantial, as expected from the discussion on T88915. For [[List of 20th-century classical composers]] with a batch size of 50, node CPU time went from 54s to 29s, and HHVM CPU time went from 216s to 70s.
+
+The impact on latency can't easily be measured in my current test setup.
+
+Unfortunately, it was necessary to treat each item in the batch as a distinct parse operation, with clearState(), since Parsoid wishes to know which categories are generated by which templates. This causes a number of useful caches to be discarded at the start of each batch item. This may be the reason why the HHVM CPU time is still 70s, even though running the text through expandtemplates as a whole takes only 10s. Increasing the batch size from 50 to 500 only reduced the HHVM CPU time to 65s.
+
+If clearState() was not done, it would not be easy to determine which template caused the addition of a given category. Consider the case of a template which is invoked with no arguments, which causes a tracking category to be added. If this template is invoked more than once in a parse operation, the expansion cache will prevent ParserOutput::addCategory() from being called on the second and subsequent invocations. This implies that the expansion cache would need to be disabled or rewritten to support this Parsoid use case.",1437368829,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"We should also keep in mind the effect of batching on overall system reliability. In {T97204} I advocate for tight timeouts in backend services, combined with no client retries when encountering a server timeout. In general, batching makes it harder to establish tight timeouts on end points. We should thus limit it to end points where each batch action has a very predictable processing time, and the overall batch will always complete within a reasonable timeout (< 60s).",1429996047,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"We should also keep in mind the effect of batching on overall system reliability. In {T97204} I advocate for tight timeouts in backend services, combined with no client retries when encountering a server timeout. In general, batching makes it harder to establish tight timeouts on end points. We should thus limit it to end points where each batch action has a very limited processing time, and the overall batch will always complete within a reasonable timeout (< 60s).",1429995562,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,I concur.,1424214020,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"It is good thing to reduce the load on the API cluster, but I don't think this task should be a VE Q3 blocker. 
+
+Right now,
+(a) Parsoid tracks all edits -- so there is going to be no change in Parsoid parsing load (and hence API load) even if VE is enabled everywhere (assuming edit rate stays the same).
+(b) The current load on the API cluster is not problematic that forces us to work on this for VE deployment.
+
+So, I suggest that this task be removed from the VisualEditor Q3 Blockers workboard since there are other more higher priority issues to fix in Parsoid land.",1424212155,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,">>! In T45888#978615, @tstarling wrote:
+> The main reason I am leaning towards the internal batcher is because some of the queues will have very little traffic on them, e.g. queues for small wikis. This makes for some uncomfortable tradeoffs when you try to set the dispatch timeout. Consider that parse operations are observed to take ~10s and issue ~100 API requests -- this implies a mean interval between requests on the order of 100ms, and a timeout of at least that much if there is to be any throughput benefit from batching at all. That is quite a long time to wait. From a throughput perspective, the optimal dispatch timeout may be more than 1s.
+
+The amount of batching we can achieve on the long tail is bounded by the maximum latency penalty we are willing to introduce. A global batcher can combine requests from different API clients (not just parsoid), and should thus result in lower average latencies by filling up batches quickly (or reaching a given batching ratio with a lower maximum latency penalty).
+
+Also keep in mind that with selective re-expansion of templates those requests will become less common, which will make the single-client batch even less effective, as there are just less requests to combine within the time window.
+
+> Also, note that Parsoid currently performs API requests with keep-alive disabled. With default socket options, this implies a limit of 470 API requests per second per client server before local port exhaustion occurs, as in T75949. Batching internally, without the involvement of TCP, avoids this limit.
+
+The number of connections has not been an issue in practice & would not change. On the proxy we could also enable [SPDY support](https://github.com/indutny/node-spdy), which reduces the number of connections to one per client & removes some per-request overhead. That said, I think the `Connection: close` bit can be removed. It was a work-around from an early node version IIRC, and is no longer needed.",1421339610,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,">>! In T45888#978615, @tstarling wrote:
+> The main reason I am leaning towards the internal batcher is because some of the queues will have very little traffic on them, e.g. queues for small wikis. This makes for some uncomfortable tradeoffs when you try to set the dispatch timeout. Consider that parse operations are observed to take ~10s and issue ~100 API requests -- this implies a mean interval between requests on the order of 100ms, and a timeout of at least that much if there is to be any throughput benefit from batching at all. That is quite a long time to wait. From a throughput perspective, the optimal dispatch timeout may be more than 1s.
+
+The amount of batching is bounded by the maximum latency penalty we are willing to introduce. A global batcher can combine requests from different API clients (not just parsoid), and should thus result in lower average latencies by filling up batches quickly (or reaching a given batching ratio with a lower maximum latency penalty).
+
+Also keep in mind that with selective re-expansion of templates those requests will become less common, which will make the single-client batch even less effective, as there are just less requests to combine within the time window.
+
+> Also, note that Parsoid currently performs API requests with keep-alive disabled. With default socket options, this implies a limit of 470 API requests per second per client server before local port exhaustion occurs, as in T75949. Batching internally, without the involvement of TCP, avoids this limit.
+
+The number of connections has not been an issue in practice & would not change. On the proxy we could also enable [SPDY support](https://github.com/indutny/node-spdy), which reduces the number of connections to one per client & removes some per-request overhead. That said, I think the `Connection: close` bit can be removed. It was a work-around from an early node version IIRC, and is no longer needed.",1421339535,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"The two main implementation options are: a batcher internal to parsoid, and a shared node.js batcher service. The internal batcher would operate roughly as follows:
+
+* Instead of having the token handlers directly dispatch HTTP requests, they would send their requests to a batcher service, which would be local to the current parse operation. The batcher API would be slightly different to the HTTP API, since it needs to be able to easily aggregate titles, and the batcher will take over responsibility for HTTP protocol details such as timeouts.
+* If the batch is full, the request can be dispatched on the next attempted queue insertion.
+* If Parsoid returns to the event loop with requests queued in the batch but not sent, the request could permanently hang. So in relevant code paths prior to returning to the event loop, Parsoid needs notify the batcher, giving it a last chance to check if there are any batch requests queued so that it can dispatch them.
+* Additionally, a timeout would be prudent, allowing Parsoid to recover from accidental return to the event loop without notification.
+
+Gabriel suggested an external batcher which, if I understand his proposal correctly, would operate as follows:
+
+* One cluster-wide batch queue per (wiki, action) tuple. 
+* Requests to the proxy would be held in the batch queue until either it fills, or some specified timeout (e.g. 10ms) is reached. Then the batch query would be sent to the MW backend.
+* While a request is waiting in the batch queue, and while it is waiting for the backend response, the client connections, one per item, would be held open. Responses would be sent to these clients after the batch query returns from the backend.
+* This architecture avoids the need for significant changes inside Parsoid.
+
+The main reason I am leaning towards the internal batcher is because some of the queues will have very little traffic on them, e.g. queues for small wikis. This makes for some uncomfortable tradeoffs when you try to set the dispatch timeout. Consider that parse operations are observed to take ~10s and issue ~100 API requests -- this implies a mean interval between requests on the order of 100ms, and a timeout of at least that much if there is to be any throughput benefit from batching at all. That is quite a long time to wait. From a throughput perspective, the optimal dispatch timeout may be more than 1s.
+
+Explicit notification of the idle event avoids severe tradeoffs between batch size and latency. It can be implemented in either the internal or external design. But the need for idle event notification would reduce the attractiveness of the external batcher -- it would make the service stateful and its advantages in simplicity on the Parsoid side would be reduced. There is a risk that idle events could be lost anyway, and a timeout incurred, due to exhaustion of the client connection limit (globalAgent.maxSockets).
+
+Also, note that Parsoid currently performs API requests with keep-alive disabled. With default socket options, this implies a limit of 470 API requests per second per client server before local port exhaustion occurs, as in T75949. Batching internally, without the involvement of TCP, avoids this limit.",1421295841,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"The two main implementations are: a batcher internal to parsoid, and a shared node.js batcher service. The internal batcher would operate roughly as follows:
+
+* Instead of having the token handlers directly dispatch HTTP requests, they would send their requests to a batcher service, which would be local to the current parse operation. The batcher API would be slightly different to the HTTP API, since it needs to be able to easily aggregate titles, and the batcher will take over responsibility for HTTP protocol details such as timeouts.
+* If the batch is full, the request can be dispatched on the next attempted queue insertion.
+* If Parsoid returns to the event loop with requests queued in the batch but not sent, the request could permanently hang. So in relevant code paths prior to returning to the event loop, Parsoid needs notify the batcher, giving it a last chance to check if there are any batch requests queued so that it can dispatch them.
+* Additionally, a timeout would be prudent, allowing Parsoid to recover from accidental return to the event loop without notification.
+
+Gabriel suggested an external batcher which, if I understand his proposal correctly, would operate as follows:
+
+* One cluster-wide batch queue per (wiki, action) tuple. 
+* Requests to the proxy would be held in the batch queue until either it fills, or some specified timeout (e.g. 10ms) is reached. Then the batch query would be sent to the MW backend.
+* While a request is waiting in the batch queue, and while it is waiting for the backend response, the client connections, one per item, would be held open. Responses would be sent to these clients after the batch query returns from the backend.
+* This architecture avoids the need for significant changes inside Parsoid.
+
+The main reason I am leaning towards the internal batcher is because some of the queues will have very little traffic on them, e.g. queues for small wikis. This makes for some uncomfortable tradeoffs when you try to set the dispatch timeout. Consider that parse operations are observed to take ~10s and issue ~100 API requests -- this implies a mean interval between requests on the order of 100ms, and a timeout of at least that much if there is to be any throughput benefit from batching at all. That is quite a long time to wait. From a throughput perspective, the optimal dispatch timeout may be more than 1s.
+
+Explicit notification of the idle event avoids severe tradeoffs between batch size and latency. It can be implemented in either the internal or external design. But the need for idle event notification would reduce the attractiveness of the external batcher -- it would make the service stateful and its advantages in simplicity on the Parsoid side would be reduced. There is a risk that idle events could be lost anyway, and a timeout incurred, due to exhaustion of the client connection limit (globalAgent.maxSockets).
+
+Also, note that Parsoid currently performs API requests with keep-alive disabled. With default socket options, this implies a limit of 470 API requests per second per client server before local port exhaustion occurs, as in T75949. Batching internally, without the involvement of TCP, avoids this limit.",1421295823,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Request batching appears to be simple to implement (~100 lines according to @gwicke) and would cause a substantial decrease in API cluster CPU load. By switching it on only for requests initiated by the job queue, there would be no effect on user latency.
+
+> The problem with general batching is that state in MediaWiki is not very well defined. Several extensions for example keep internal state between calls to tag hooks, and resetting that state between individual requests in a batch would probably produce a similar overhead as the regular per-request setup (30+ms).
+
+No, parser state in MediaWiki is very well-defined, it is defined as the data which is cleared by Parser::clearState(). Extensions which keep internal state hook this function in order to clear their state. MediaWiki is reasonably well-optimised for clearing the parser state, since message parsing does so, often tens of times per request. The overhead is orders of magnitude smaller than the request setup time.
+
+> The current performance numbers combined with several optimizations aimed at avoiding API requests lessened the need for API request batching on our end.
+
+Parsoid is still by far the largest API consumer by CPU time.
+
+> Speeding up individual API requests is a general architectural goal, and should be addressed in that context. Closing this bug as WONTFIX on our end.
+
+I am familiar with MW setup time optimisation, and compared to that large, ongoing effort, Parsoid request batching looks like low-hanging fruit.",1421212316,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"The current performance numbers combined with several optimizations aimed at avoiding API requests lessened the need for API request batching on our end.
+
+Speeding up individual API requests is a general architectural goal, and should be addressed in that context. Closing this bug as WONTFIX on our end.",1370996729,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"Adding custom batching support just for template expansion and extension tag calls would really be a workaround, and would add complexity to both clients and the server. If the performance of API requests could be improved in general, we could and should probably avoid that complex workaround in favor of the general solution.
+
+In the longer term, our HTML storage and incremental re-parsing / expansion plans should reduce the number of template expansions and extension calls to a fraction of the level we'll produce initially. The round-trip testing we are currently performing is already close to the edit rate of the English Wikipedia and did not create any issues on the API cluster. A Parsoid installation tracking all edits on all wikis would probably create 2-3 times the number of API requests, which are probably still doable for the current API cluster.
+
+Overall it seems to be a good idea to hold off on a custom batching solution until it is clear that it is really needed and general API performance improvements are not possible.",1361472978,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"For us, the main use cases are template expansion using the PHP preprocessor and the expansion of extension tags. Currently, both of these are only available with a detour through the PHP parser (action=expandtemplates and action=parse respectively), so we'd like to add direct API end points to perform these actions.
+
+A general batching mechanism would probably accept a posted JSON array with each member being an object containing the API arguments for one action (action etc). The return value would be a JSON array with results corresponding to the request array. Instead of relying on positions in an array the client could also supply UIDs for requests which are then mirrored in the result. This could be achieved with an reqid member in each request object.
+
+The problem with general batching is that state in MediaWiki is not very well defined. Several extensions for example keep internal state between calls to tag hooks, and resetting that state between individual requests in a batch would probably produce a similar overhead as the regular per-request setup (30+ms).
+
+In Parsoid, we can work around this issue for our specific use cases by maintaining a whitelist of stateless extensions which can be mixed in a batch without producing non-deterministic output. Non-whitelisted extensions would need to be expanded in a single action=parse request containing all extension tags for that particular extension in page order.",1359928307,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+Batch Parsoid's API requests,"action=query was built specifically to support batching, but other actions might choose not to implement it. Could you give a very specific example of
+* How the final api request should look like?
+* What do you expect in return.",1359927005,PHID-USER-esrrkc2rlizdlae443wg,False,PHID-TASK-rtnmynqsvowvjvcit3ww,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","From user suggestion:
+
+| Heading 1 is very rare on enwiki, and indeed on most other installations.
+| Where it is used (mostly on project discussion pages), it does not usually
+| need to be edited. VisualEditor should not offer it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1356129180,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_description,resolved
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",This is now merged and will go out later today.,1372274701,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",Related URL: https://gerrit.wikimedia.org/r/69801 (Gerrit Change I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9),1371765581,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",Related URL: https://gerrit.wikimedia.org/r/69801 (Gerrit Change I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9),1371765577,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","I believe that the current list of titles  will quickly be a problem if VE is rolled out to unexperienced users on wikipedia: they will probably use Heading 1 because they don't know it shouldn't be used in 99.9...% of edits.
+When I tried to add a section, I used Heading 1 by default and only changed back to Heading 2 when I saw that the new title was bigger than what I'm used to.
+
+If you think <h1> titles should be kept in VE, it should be separated from the other titles (after other ones). Eventually, would it be possible to make that configurable on a per wiki basis if some wiki really use <h1> as a normal title ?",1371736146,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","> Lots of wikis (e.g.meta) use H1s quite liberally.
+
+I didn't know that, and it seems bad practice. Could you point to some examples? Maybe there is a use case I'm completely overlooking.
+
+
+> | H1: Title
+> | H2: Heading
+> | H3: Sub-heading
+> | H4: Sub-heading
+> | H5: Sub-heading
+> | H6: Sub-heading
+
+I'm not so happy about the name ""Title"", and it being at the top of that list. I would much rather see it buried somewhere at the bottom, maybe as the very last option, and something like ""Duplicate page title"", or at least something that makes it abundantly clear that it is not something that is meant to be used.",1371622689,PHID-USER-n27daagbl3wqf3ghr4nk,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","AzaToth's suggestion is to label as follows:
+
+| H1: Title
+| H2: Heading
+| H3: Sub-heading
+| H4: Sub-heading
+| H5: Sub-heading
+| H6: Sub-heading
+
+The differentiation between H3 - H6 would be only styling. Not sure how I feel about this, but it's certainly ""correct"".",1371598971,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","(In reply to comment #12)
+> Kill the H1s from the editor please. They should really be considered
+> deprecated in the wiki syntax, and aren't something that people should be
+> able to create by accident.
+
+VE is meant to be able to edit all content that's valid. Lots of wikis (e.g. meta) use H1s quite liberally. Discouraging use is fine, but preventing use feels wrong. (Also, what the hell should VE do when it encounters an H1 in the wild, if they were 'disabled'?)",1371598575,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","Kill the H1s from the editor please. They should really be considered deprecated in the wiki syntax, and aren't something that people should be able to create by accident.",1371598260,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","(In reply to comment #10)
+> Instead of messing around with the numbers and having [heading 3 = <h4>], why
+> not rename them ""Heading"", ""Subheading"", and ""Sub-subheading"".
+
+So:
+
+| H1: Title
+| H2: Heading
+| H3: Sub-heading
+| H4: Sub-sub-heading
+| H5: Sub-sub-sub-heading
+| H6: Sub-sub-sub-sub-heading
+
+It might get a bit ridiculous, but I like the idea.",1371160524,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","**ypnypn9** wrote:
+
+(In reply to comment #9)
+> It is unfortunate that wikitext currently allows h1 elements. It shouldn't.
+> It should be the end aim for the visual editor to have feature parity with
+> wikitext, but at the current point it makes it natural to select a heading 1
+> when you really never want to do that. I would prefer to see it not available
+> in the visual editor at all, but as a compromise, I could live with renaming
+> Header 1 to Pageheader, and move it all the way to the bottom of markup
+> elements, and rename header 2 to header 1, etc. That way we don't lose an
+> option in the visual editor that is available in wikitext, and at the same
+> time reduce the chance of people thinking it is an option they may want to
+> choose for a header, which it is not.
+
+Instead of messing around with the numbers and having [heading 3 = <h4>], why not rename them ""Heading"", ""Subheading"", and ""Sub-subheading"".",1371160398,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","It is unfortunate that wikitext currently allows h1 elements. It shouldn't. It should be the end aim for the visual editor to have feature parity with wikitext, but at the current point it makes it natural to select a heading 1 when you really never want to do that. I would prefer to see it not available in the visual editor at all, but as a compromise, I could live with renaming Header 1 to Pageheader, and move it all the way to the bottom of markup elements, and rename header 2 to header 1, etc. That way we don't lose an option in the visual editor that is available in wikitext, and at the same time reduce the chance of people thinking it is an option they may want to choose for a header, which it is not.
+
+At the same time, we may want to think about abandoning the option to make h1 headers in wikitext too, but that makes for a different discussion which should take place in a different place than this bug.",1370004773,PHID-USER-n27daagbl3wqf3ghr4nk,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","Does this really have much to do with the VE to begin with ? It's already allowed. I agree that such is a bad thing but that's a separate story. I guess at most, we could make the H1 option 'non visisble' unless the current element already is exactly of that type.
+
+What would be nice, was if the VE would have more 'guided' heading building. It could warn you about inconsistencies in header levels for instance.",1370000141,PHID-USER-wrimmmr5w2zt7nk2t753,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",*** Bug 48955 has been marked as a duplicate of this bug. ***,1369927169,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","**rogerchrisman** wrote:
+
+(In reply to comment #5)
+> (In reply to comment #4)
+> > Agree--Visual Editor should not use <h1> HTML tags for headings at all
+> > because
+> > MediaWiki uses <h1> HTML for page name and headings are subordinate to page
+> > name. Heading-1 should create <h2> HTML tags, Heading-2 <h3> HTML tags,
+> > Heading-3 <h4> HTML tags, etc. Newcomers don't know this. Visual Editor
+> > should
+> > simply do this correctly without editors needing to know or think about it at
+> > all. Offering <h1> HTML in Visual Editor will cause confusion and misuse
+> > among
+> > the very people Visual Editor is designed to empower. They just want it to
+> > work
+> > right.
+> 
+> Except ""Heading 1"" is actually create-able on any wiki page (""= Foo =""), it's
+> just discouraged. This is a tension between what the software /lets/ users do
+> and what they /should/ do. I'm not convince that hard and fast global rules
+> are
+> always appropriate.
+
+This is not about convincing anyone ""that hard and fast global rules are
+always appropriate."" This is about getting it right for MediaWiki and MediaWiki users. Having ""Heading-1"" create wrong first level headings is wrong because orrect first level headings are <h2> in MediaWiki, subordinate to the page name <h1> that _is_ 'hard and fast' coded into the wiki page generator because that works well, always has, and is correct HTML. Users should not need to think about HTML at all. VisualEditor should just work right, not wrong. I know = Foo = gives <h1>Foo</h1>. That is an unfortunate wiki markup parser bug. If the VisualEditor team is too week to fix this bug by removing <h1> from the editor, they may implement ""Header-0 _deprecated_"" as <h1> (and link ""_deprecated_"" to a mediawiki.org page explaining why it is deprecated and why nevertheless included in VisualEditor). That is the obvious easy way out. However, VisualEditor has no need nor obligation to implement the deprecated and seldom used = Foo =. So remove it now and save everyone the mind drain of ""Header-0 _deprecated_"". VisualEditor is NOT an HTML editor. It is a MediaWiki page editor.",1366174196,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","(In reply to comment #4)
+> Agree--Visual Editor should not use <h1> HTML tags for headings at all
+> because
+> MediaWiki uses <h1> HTML for page name and headings are subordinate to page
+> name. Heading-1 should create <h2> HTML tags, Heading-2 <h3> HTML tags,
+> Heading-3 <h4> HTML tags, etc. Newcomers don't know this. Visual Editor
+> should
+> simply do this correctly without editors needing to know or think about it at
+> all. Offering <h1> HTML in Visual Editor will cause confusion and misuse
+> among
+> the very people Visual Editor is designed to empower. They just want it to
+> work
+> right.
+
+Except ""Heading 1"" is actually create-able on any wiki page (""= Foo =""), it's just discouraged. This is a tension between what the software /lets/ users do and what they /should/ do. I'm not convince that hard and fast global rules are always appropriate.",1366153968,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","**rogerchrisman** wrote:
+
+Agree--Visual Editor should not use <h1> HTML tags for headings at all because MediaWiki uses <h1> HTML for page name and headings are subordinate to page name. Heading-1 should create <h2> HTML tags, Heading-2 <h3> HTML tags, Heading-3 <h4> HTML tags, etc. Newcomers don't know this. Visual Editor should simply do this correctly without editors needing to know or think about it at all. Offering <h1> HTML in Visual Editor will cause confusion and misuse among the very people Visual Editor is designed to empower. They just want it to work right.",1366006598,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?","**rogerchrisman** wrote:
+
+Agree--Visual Editor should not use <h1> HTML tags for headings at all because MediaWiki uses <h1> HTML for page name and headings are subordinate to page name. Heading-1 should create <h2> HTML tags, Heading-2 <h3> HTML tags, Heading-3 <h4> HTML tags, etc. Newcomers don't know this. Visual Editor should simply do this correctly without editors needing to know or think about it at all. Offering <h1> HTML in Visual Editor will cause confusion and misuse among the very people Visual Editor is designed to empower. They just wont it to work right.",1366006439,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",May want to cover content namespaces in general (but provide some way of getting them). Also to consider preventing H6s (and H5s?).,1360376924,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+"VisualEditor: For article namespace, disable Heading-1s (<h1>), others?",*** Bug 44780 has been marked as a duplicate of this bug. ***,1360376842,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-whtfrzztibmjwea3vy7l,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**Author:** `turb`
+
+**Description:**
+When cookies are disabled, VisualEditor loads indef. It would better to either 1) be able to use it without cookies (I suppose that's not possible) or 2) display an adequate error message.
+
+Tested on Firefox 17.0.1 with Cookie Monster 1.1.0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1355742780,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zborcq5aeddm5rc2upgl,task_description,resolved
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**turb** wrote:
+
+(In reply to comment #7)
+> Afaik the bad token handling has been solved for the save process. The load
+> process no longer requires a token.
+> 
+> Can you confirm this now works fine?
+
+Yes, it does work fine now, even with Cookie Monster preventing cookies to be set.",1380306403,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"Afaik the bad token handling has been solved for the save process. The load process no longer requires a token.
+
+Can you confirm this now works fine?",1380304934,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**turb** wrote:
+
+(In reply to comment #5)
+> Does normal editing (through the old, non-visual editor) work for you on
+> mediawiki.org when not whitelisted?
+
+Yes, it works.",1357831603,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"(In reply to comment #3)
+> (In reply to comment #2)
+> > (In reply to comment #1)
+> > > Can you confirm whether VE always fails to load with Cookie Monster and
+> > > always
+> > > loads successfully without Cookie Monster?
+> > And could you also confirm that you're able to edit *as a logged-in user*
+> > using
+> > the regular non-visual editor?
+> 
+> I forgot to mention I was testing on VisualEditor:Test in mediawiki.org, that
+> was not whitelisted in Cookie Monster. When I did whitelisted it, the page
+> reloaded and VE was now working.
+> 
+> I just removed again mediawiki.org from whitelist, and VE now loads without
+> end.
+> 
+Does normal editing (through the old, non-visual editor) work for you on mediawiki.org when not whitelisted?",1357671274,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**turb** wrote:
+
+Note: after some tests, VE does work with Chrome and IE9, with totally disabled cookies.",1355821721,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"**turb** wrote:
+
+(In reply to comment #2)
+> (In reply to comment #1)
+> > Can you confirm whether VE always fails to load with Cookie Monster and
+> > always
+> > loads successfully without Cookie Monster?
+> And could you also confirm that you're able to edit *as a logged-in user*
+> using
+> the regular non-visual editor?
+
+I forgot to mention I was testing on VisualEditor:Test in mediawiki.org, that was not whitelisted in Cookie Monster. When I did whitelisted it, the page reloaded and VE was now working.
+
+I just removed again mediawiki.org from whitelist, and VE now loads without end.
+
+VE do work for me in en.wikipedia.org (that is of course whitelisted). I don't know if anonymous users can contribute with cookies disabled (for the day it will be activated for them).",1355821184,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"(In reply to comment #1)
+> Can you confirm whether VE always fails to load with Cookie Monster and
+> always
+> loads successfully without Cookie Monster?
+And could you also confirm that you're able to edit *as a logged-in user* using the regular non-visual editor?",1355819420,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+VisualEditor: Firefox has issues using VE when cookies are disabled,"You can't have *all* cookies disabled, otherwise you wouldn't be able to log in and enable the VE preference. I'm guessing this might be a badtoken error (in which case I'm pretty sure we do actually show an error message, rather than load forever; and in which case you're probably also unable to edit through the regular UI), or it might be something entirely unrelated to cookies.
+
+Can you confirm whether VE always fails to load with Cookie Monster and always loads successfully without Cookie Monster?",1355819348,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zborcq5aeddm5rc2upgl,task_subcomment,NA
+Undo/Redo doesn't work in Chrome/Chromium/Firefox for WikiEditor 0.3.1 in MW 1.19.2,"**Author:** `kartiksinghal`
+
+**Description:**
+I am using WikiEditor 0.3.1 in my mediawiki (1.19.2) installation and found that for some weird reason, undo/redo (Ctrl+Z and Ctrl+Shift+Z) doesn't work in the editor with Chrome, Chromium and Firefox browsers; while it works for Rekonq and default KDE webbrowser.
+
+I found T33780 - a slightly different but probably relevant bug report.
+
+Also, undo works just fine in default VisualEditor in Chrome.
+
+Interesting point to notice is that Undo/Redo work fine even on WikiEditor used on Wikipedia, but not in my mediawiki instance, looks like some good changes not pushed to upstream yet.
+
+I also tried test2.wikipedia.org, it works fine there as well.
+
+--------------------------
+**Version**: REL1_19-branch
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=31780",1355717820,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-5sshjiczpsr7gablgejn,task_description,invalid
+Undo/Redo doesn't work in Chrome/Chromium/Firefox for WikiEditor 0.3.1 in MW 1.19.2,This has probably already been fixed. I have no issues with undo/redo in Firefox on my local wiki running MW 1.23 and WikiEditor from master.,1417536426,PHID-USER-2uu3axihtun5w4v24nqz,False,PHID-TASK-5sshjiczpsr7gablgejn,task_subcomment,NA
+VisualEditor: Parsoid diff failure errors are not very descriptive,"Parsoid diff failure errors are not very descriptive - ""error loading data from server: unsuccessful request: diff failed."" but not why (in this case, it was because the target oldid had been deleted subsequent to the user pressing save, but a more graceful message would be good.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=44354
+https://bugzilla.wikimedia.org/show_bug.cgi?id=39057
+https://bugzilla.wikimedia.org/show_bug.cgi?id=63149",1355530860,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rmktbubqqol74vvmg4zn,task_description,resolved
+VisualEditor: Parsoid diff failure errors are not very descriptive,"With the above patch, the former message:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500. Would you like to retry?
+
+… turns into:
+
+    Error loading data from server: parsoidserver-http-bad-status:
+    500: Page Fetch failure for ""BADURL"": Error: getaddrinfo
+    ENOTFOUND. Would you like to retry?
+
+Which is not ideal, but at least describes things a bit. Marking this as FIXED.",1409684401,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-rmktbubqqol74vvmg4zn,task_subcomment,NA
+VisualEditor: Parsoid diff failure errors are not very descriptive,"Change 157775 merged by jenkins-bot:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409681803,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rmktbubqqol74vvmg4zn,task_subcomment,NA
+VisualEditor: Parsoid diff failure errors are not very descriptive,"Change 157775 had a related patch set uploaded by Jforrester:
+Add debugging help to VisualEditor
+
+https://gerrit.wikimedia.org/r/157775",1409669834,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-rmktbubqqol74vvmg4zn,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","For content which is alienated, provide a way for users to get a wikitext editing window for just the wikitext for that item. This allows users to modify content that does not have an inspector yet, and for ""power users"", make tweaks in an environment that is familiar to them, without overwhelming other users. Ideally, this would be syntax-highlighted and pretty and helpful, but anything at all would be a start. :-)
+
+This will require some serious magic in Parsoid to identify the causal wikitext and allow partial document retrieval, and so this is very much in the ""enhancement"" pile for now; putting in UI as it's an inspector, but it will have impacts all the way down through DM.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355508900,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_description,resolved
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")",Fixed by Ed last year in https://gerrit.wikimedia.org/r/#/c/78035/,1414135494,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","**suitongbowgn** wrote:
+
+(In reply to comment #9)
+> (In reply to comment #8)
+> > There are quite a lot of extensions where the content should probably be
+> > treated as a simple block of text. <math>, <source>, <pre>, <poem> basically
+> > just have plain text ending with the appropriate closing tag.
+> 
+> Sort of. Ideally there will one day be a visual math editor, a visual music
+> editor, and we already have [[mw:Extension:CodeEditor]] (which is even
+> deployed
+> to certain wikis) for JavaScript and CSS, which will likely cover <pre> and
+> <source>/<syntaxhighlight> blocks.
+> 
+> I suppose <poem> and <nowiki> blocks can use a simple editor. :-)
+
+For <math> please see bug 43058. I believe it is already available via VisualEditor experimental code.
+For <syntaxhighlight> please see bug 47742. The code is currently under code review and will be available via VE experimental code in the future.",1375162399,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","(In reply to comment #8)
+> There are quite a lot of extensions where the content should probably be
+> treated as a simple block of text. <math>, <source>, <pre>, <poem> basically
+> just have plain text ending with the appropriate closing tag.
+
+Sort of. Ideally there will one day be a visual math editor, a visual music editor, and we already have [[mw:Extension:CodeEditor]] (which is even deployed to certain wikis) for JavaScript and CSS, which will likely cover <pre> and <source>/<syntaxhighlight> blocks.
+
+I suppose <poem> and <nowiki> blocks can use a simple editor. :-)",1375159143,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","There are quite a lot of extensions where the content should probably be treated as a simple block of text. <math>, <source>, <pre>, <poem> basically just have plain text ending with the appropriate closing tag.
+
+Some partial fix of this would be a great step in allowing VE to be used on some large classes of article.",1375133975,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")",*** Bug 51131 has been marked as a duplicate of this bug. ***,1373482421,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")",*** Bug 47742 has been marked as a duplicate of this bug. ***,1366998592,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")",Moved to Lowest as this has a huge dependency on Parsoid which they are unlikely to implement; depending on their reconsideration in a while.,1360206963,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","(In reply to comment #3)
+> +1, I imagine this feature as a toggle button, which switches the main view
+> between its current rendering containing uneditable blocks, to a hybrid
+> rendered + wikitext view in which the VE-opaque stuff is displayed as raw
+> source.
+
+Actually, we'll probably have inspector buttons on alienated nodes that trigger a float-over IFRAME quasi-window (in the same way that we do for the link inspector) for the individual item, rather than have a different editing mode (disrupting the entire editing flow feels wrong), but these decisions have yet to be taken.",1357696093,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","+1, I imagine this feature as a toggle button, which switches the main view between its current rendering containing uneditable blocks, to a hybrid rendered + wikitext view in which the VE-opaque stuff is displayed as raw source.
+
+The VE is great, but I have not found it to be usable for anything beyond the most trivial copy-editing, because of this issue.",1357694232,PHID-USER-p6hvqn5njgnxuagekh4b,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","(In reply to comment #1)
+> It should be noted that a lot of this is already supported. I don't think
+> it's
+> perfect, and VE would have to perform some acrobatics to get it working, but
+> you could essentially make it work if you set the wikitext source on the
+> element, then serialized the DOM and re-parsed it to get the visual
+> representation back.
+> 
+The wikitext is currently exposed in the data-parsoid attribute, but the contents of that attribute are supposed to be private and VE isn't supposed to look at them, just preserve them. There were earlier hacks in VE that extracted information from data-parsoid to work around Parsoid issues (specifically, we had to look at sHref for links and stx==html for list items), but Gabriel has been glaring at me every time I did that.
+
+So to make the wikitext editable, it would have to be moved to a more public place, or data-parsoid would have to be declared semi-public. Either way, we need to spec how Parsoid is going to present the wikitext to VE and what VE is allowed to do with it.
+
+> James_F and I chatted about this for some time, and I'm pretty sure that's
+> one
+> of the saner ways to do it (unless you wanted to simply ignore the visual
+> portion of ""VisualEditor"" and submit the alien's changes only when the user
+> is
+> done editing.
+Yeah, you probably don't want to continuously rerender as the user types, that would get crazy. But as you say, you'd want to reparse the entered wikitext so you can rerender it and give the user visual feedback. That should be interesting to implement.",1355819784,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+"VisualEditor: Fly-out wikitext editor for unsupported extensions' source blocks (""alienated content"")","It should be noted that a lot of this is already supported. I don't think it's perfect, and VE would have to perform some acrobatics to get it working, but you could essentially make it work if you set the wikitext source on the element, then serialized the DOM and re-parsed it to get the visual representation back.
+
+James_F and I chatted about this for some time, and I'm pretty sure that's one of the saner ways to do it (unless you wanted to simply ignore the visual portion of ""VisualEditor"" and submit the alien's changes only when the user is done editing.",1355522188,PHID-USER-nvavrb7ko66hv3xap6sb,True,PHID-TASK-64pve3q3gx7xk5rm2nk4,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Poem blocks,"<poem>....</poem> is unparsed but shown as plain wikitext:
+https://en.wikipedia.org/wiki/User:Raymond/poem
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/poem",1355479800,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-j5lt672qs5xqtdfzq6de,task_description,open
+Create a VisualEditor plugin tool to add/edit Poem blocks,"(In reply to comment #3)
+> (a) and (b), I guess. See bug 52061. I was going through a list of bugs in
+> the Poem component, since they will all need to be moved once the change
+> is merged (hoping it *is* merged, of course). Sorry if I'm getting too far
+> ahead of myself, but this bug did seem like an odd one out, so I moved it
+> out here.
+
+Moving back to Poem, then. The bug can be moved the MediaWiki/editing or whatever later, when bug 52061 is closed-fixed.
+
+> (In reply to comment #2)
+> > > so I'm punting back to VisualEditor.
+> > 
+> > Why? It's not VisualEditor's problem that an extension hasn't been updated
+> > yet…
+> 
+> Well, if Poem is to become a MediaWiki core feature, then it will turn into
+> something for the VE team to worry about.
+
+No, not really. It'll remain the responsibility of some code's maintainer, whoever that is (you?). In the absence of an obvious maintainer, that's the ""Platform team"", which sucks, but is rather outwith this bug report.
+
+The VE team build VE and some of the MW-specific VE tools. We're not going to make an editor for EasyTimeline, and we're not going to make one for Poem, for the same reason. :-)
+
+> Also, if I may point it out, the WikiHiero extension is seemingly supported
+> in VisualEditor core. The extension itself knows nothing about VE. is that
+> an anomaly?
+
+Yes; the code's yet to be moved into that repo. Give me a spare 10 minutes. :-)",1389573042,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j5lt672qs5xqtdfzq6de,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Poem blocks,"(a) and (b), I guess. See bug 52061. I was going through a list of bugs in the Poem component, since they will all need to be moved once the change is merged (hoping it *is* merged, of course). Sorry if I'm getting too far ahead of myself, but this bug did seem like an odd one out, so I moved it out here.
+
+(In reply to comment #2)
+> > so I'm punting back to VisualEditor.
+> 
+> Why? It's not VisualEditor's problem that an extension hasn't been updated
+> yet…
+
+Well, if Poem is to become a MediaWiki core feature, then it will turn into something for the VE team to worry about.
+
+Also, if I may point it out, the WikiHiero extension is seemingly supported in VisualEditor core. The extension itself knows nothing about VE. is that an anomaly?",1389572502,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-j5lt672qs5xqtdfzq6de,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Poem blocks,"(In reply to comment #1)
+> This is not a bug/enhancement in the Poem extension itself,
+
+False. The Poem extension fails to register a VisualEditor enhanced editor for itself. This is a problem with that extension. See also bug 43115, bug 43118, bug 43127, etc.
+
+> so I'm punting back to VisualEditor.
+
+Why? It's not VisualEditor's problem that an extension hasn't been updated yet…
+
+> If I've got this wrong, please don't move the bug back to Poem, as this
+> component is hopefully going to be removed soon.
+
+Please justify this.
+
+All MW extensions that are deployed on the WMF cluster (and many that aren't) have a Bugzilla component, by policy. Are you saying that:
+
+ (a) you want us to remove this extension from the cluster,
+ (b) you want us to merge this extension into MW core, or
+ (c) you want us to break our existing policy for this extension?",1389567907,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-j5lt672qs5xqtdfzq6de,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Poem blocks,"This is not a bug/enhancement in the Poem extension itself, so I'm punting back to VisualEditor.
+
+If I've got this wrong, please don't move the bug back to Poem, as this component is hopefully going to be removed soon.",1389521779,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-j5lt672qs5xqtdfzq6de,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Timelines,"<timeline>....</timeline> is unparsed but shown as plain wikitext:
+https://en.wikipedia.org/wiki/User:Raymond/timeline
+
+**See Also**:
+{T29157}",1355477160,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-xk6tqgbthziuxrrlpn37,task_description,declined
+Create a VisualEditor plugin tool to add/edit Timelines,"Same as {T29157}, EasyTimeline is legacy and will eventually be replaced in favor of the Graph extension (T137291). As such it does not make sense to invest in a VisualEditor plugin that will eventually be made obsolete when timelines are migrated to Graph.",1479204677,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-xk6tqgbthziuxrrlpn37,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Timelines,I'd advise against work on this task; see {T137291} for the likely disposition of the extension.,1465386511,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xk6tqgbthziuxrrlpn37,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Timelines,"Not a duplicate; bug 27157 is about making a stand-alone interactive visual tool to create and edit EasyTimelines, whereas this is specifically about doing it inside VisualEditor (and so not for wikitext users).",1403569577,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xk6tqgbthziuxrrlpn37,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Timelines,"I think this is a duplicate of bug 27157. Please revert if I'm wrong.
+
+*** This bug has been marked as a duplicate of bug 27157 ***",1403559016,PHID-USER-omdcggvudfkuawipp23i,False,PHID-TASK-xk6tqgbthziuxrrlpn37,task_subcomment,NA
+VisualEditor: Switch over edit-success notice to use the deployed one,"On successful save, VE informs the user with a notification; however, this is not the same as the one deployed to the English Wikipedia (and elsewhere?). We should just inherit that, if possible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1355431920,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tnwafiqbhbl7tln47v6a,task_description,resolved
+VisualEditor: Switch over edit-success notice to use the deployed one,"
+
+*** This bug has been marked as a duplicate of bug 39632 ***",1368638967,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-tnwafiqbhbl7tln47v6a,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"//This task is about PHP errors, for fatals, see T89169.//
+
+-------
+
+Although we get PHP warnings in the apache syslogs, we don't really get much information about it:
+
+Dec 13 18:30:43 10.0.11.48 apache2[9987]: PHP Warning:  preg_match() expects parameter 2 to be string, array given in /usr/local/apache/common-local/php-1.21wmf6/extensions/FundraiserLandingPage/FundraiserLandingPage.php on line 96
+Dec 13 18:30:43 10.0.2.198 apache2[24462]: PHP Warning:  preg_match() expects parameter 2 to be string, array given in /usr/local/apache/common-local/php-1.21wmf6/extensions/FundraiserLandingPage/FundraiserLandingPage.php on line 96
+
+We could do with recording more information (to a different log file on fluorine), like we do for both the fatal log and the exception logs
+
+-------
+
+Patches: <https://gerrit.wikimedia.org/r/#/q/message:T45086>
+
+Checklist:
+
+* [x] Improve de-duplication and message counting by ensuring `normalized_message` does not include the exception_id. – Pending review: https://gerrit.wikimedia.org/r/374895
+* [x] Introduce $wgPropagateErrors to avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [x] Enable $wgPropagateErrors in Beta Cluster. https://gerrit.wikimedia.org/r/c/409171/
+* [x] Enable $wgPropagateErrors in production Cluster.
+* [x] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+",1355424060,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_description,resolved
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Nice! That concludes a multiple years project :-],1551739179,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Thanks for pushing this through the finish line @Krinkle!,1551733519,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 494042 **merged** by Herron:
+[operations/puppet@production] logstash: Remove filter for unused 'exception-json' channel
+
+[[https://gerrit.wikimedia.org/r/494042]]",1551729558,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 494042 had a related patch set uploaded (by Krinkle; owner: Krinkle):
+[operations/puppet@production] logstash: Remove filter for unused 'exception-json' channel
+
+[[https://gerrit.wikimedia.org/r/494042]]",1551628735,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Pushing back. But would be nice to finish up at some point, but not now. To anyone else that happens to run into it: feel free to take it.",1539744093,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Last remaining check box:
+
+> [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`.",1539743995,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"I wasn't aware of `$wgPropagateErrors`, indeed we no more need errors to be spurts to HHVM stdout (which is `type:hhvm`).  That is a nice improvement to the logging and tracking errors :]",1539675476,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWZvyp40zCcrHSwq9kpb} [2018-10-13T23:37:21Z] <krinkle@deploy1001> Synchronized wmf-config/InitialiseSettings.php: T45086 - I4857e8ac (duration: 00m 51s)",1539473842,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 423338 **merged** by jenkins-bot:
+[operations/mediawiki-config@master] Set $wgPropagateErrors to false in production
+
+[[https://gerrit.wikimedia.org/r/423338]]",1539473248,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"@Tgr Yeah, take of small chunk of say 2 hours and then correlate as you describe. Keep in mind that T200960 was/is causing serious loss of data all over the place, including between these two channels. It's close to being fixed, so best to look at [Grafana](https://grafana.wikimedia.org/dashboard/db/logstash?orgId=1) and find a comfortable period of time range where there was 0 packet loss (which until last week, was never).",1533749486,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Hm, not sure why I didn't find it. Thanks Krinkle.
+
+What would be the next step here? Get a full list of all `type:hhvm` errors, filter out the ones which are also found in `type:mediawiki channel:error`, make sure that the rest are not propagated PHP errors, then enable `$wgPropagateError` in production?",1525164989,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#4166452, @Tgr wrote:
+> Seems like some PHP errors are only logged in the HHVM channel (T193339). Not sure whether they end up there with a mechanism that $wgPropagateError would affect.
+
+At T193339, the following sample is referenced from `type:hhvm`:
+
+```
+2018-04-29T09:25:59
+t  _type	hhvm
+t  host	mw1315
+t  level	NOTICE
+t  message	Notice: Undefined index: 0 in /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php on line 1498
+```
+
+Looking in `type:mediawiki` (dashboard ""mediawiki-errors"" with INFO and DEBUG un-disabled) I do find the same error trending
+
+```name=Trending
+Count: 16,672
+Message:
+[{exception_id}] {exception_url} ErrorException from line 1498 of /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php: PHP Notice: Undefined index: 0  	
+```
+
+And the exact duplicate (based on timestamp, host and message):
+<https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-2018.04.29/mediawiki?id=AWMQuSfhpesmgM3l0MzT&_g=h@b6494f7>
+
+```name=Sample,lines=10
+@timestamp	2018-04-29T09:25:59
+t  _type	mediawiki
+t  host		mw1315
+t  level	INFO
+t  server	ar.wikipedia.org
+t  url		/w/api.php
+[..]
+t  exception.message	PHP Notice: Undefined index: 0
+t  exception.trace	#0 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php(1498): MWExceptionHandler::handleError(integer, string, string, integer, array, array)
+#1 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php(955): AbuseFilter::takeConsequenceAction(string, array, Title, AbuseFilterVariableHolder, string, integer)
+#2 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilter.php(1105): AbuseFilter::executeFilterActions(array, Title, AbuseFilterVariableHolder)
+#3 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilterHooks.php(119): AbuseFilter::filterAction(AbuseFilterVariableHolder, Title)
+#4 /srv/mediawiki/php-1.32.0-wmf.1/extensions/AbuseFilter/includes/AbuseFilterHooks.php(52): AbuseFilterHooks::filterEdit(RequestContext, WikitextContent, string, Status, string, boolean)
+#5 /srv/mediawiki/php-1.32.0-wmf.1/includes/Hooks.php(177): AbuseFilterHooks::onEditFilterMergedContent(RequestContext, WikitextContent, Status, string, User, boolean)
+#6 /srv/mediawiki/php-1.32.0-wmf.1/includes/Hooks.php(205): Hooks::callHook(string, array, array, NULL)
+#7 /srv/mediawiki/php-1.32.0-wmf.1/includes/EditPage.php(1679): Hooks::run(string, array)
+#8 /srv/mediawiki/php-1.32.0-wmf.1/includes/EditPage.php(1998): EditPage->runPostMergeFilters(WikitextContent, Status, User)
+#9 /srv/mediawiki/php-1.32.0-wmf.1/includes/EditPage.php(1506): EditPage->internalAttemptSave(NULL, boolean)
+#10 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiEditPage.php(392): EditPage->attemptSave(NULL)
+#11 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(1579): ApiEditPage->execute()
+#12 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(504): ApiMain->executeAction()
+#13 /srv/mediawiki/php-1.32.0-wmf.1/extensions/VisualEditor/includes/ApiVisualEditorEdit.php(69): ApiMain->execute()
+#14 /srv/mediawiki/php-1.32.0-wmf.1/extensions/VisualEditor/includes/ApiVisualEditorEdit.php(382): ApiVisualEditorEdit->saveWikitext(Title, string, array)
+#15 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(1579): ApiVisualEditorEdit->execute()
+#16 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(535): ApiMain->executeAction()
+#17 /srv/mediawiki/php-1.32.0-wmf.1/includes/api/ApiMain.php(506): ApiMain->executeActionWithErrorHandling()
+#18 /srv/mediawiki/php-1.32.0-wmf.1/api.php(83): ApiMain->execute()
+#19 /srv/mediawiki/w/api.php(3): include(string)
+#20 {main}
+```",1525143540,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Seems like some PHP errors are only logged in the HHVM channel (T193339). Not sure whether they end up there with a mechanism that $wgPropagateError would affect.,1524994832,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 423338 had a related patch set uploaded (by Gergő Tisza; owner: Gergő Tisza):
+[operations/mediawiki-config@master] Set $wgPropagateErrors to false in production
+
+[[https://gerrit.wikimedia.org/r/423338]]",1522576116,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"{nav icon=file, name=Mentioned in SAL (#wikimedia-operations), href=https://tools.wmflabs.org/sal/log/AWGLan1EL7tQ11ghvNrW} [2018-02-12T19:07:47Z] <niharika29@tin> Synchronized wmf-config/InitialiseSettings-labs.php: Stop PHP errors from going to the hhvm channel T45086 (duration: 00m 56s)",1518462467,PHID-USER-j4uyesgqhubl2dywl4xd,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 409171 **merged** by jenkins-bot:
+[operations/mediawiki-config@master] Stop PHP errors from going to the hhvm channel
+
+[[https://gerrit.wikimedia.org/r/409171]]",1518462280,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338911 **merged** by jenkins-bot:
+[mediawiki/core@master] Make it possible to not propagate errors to PHP
+
+[[https://gerrit.wikimedia.org/r/338911]]",1518130976,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 409171 had a related patch set uploaded (by Gergő Tisza; owner: Gergő Tisza):
+[operations/mediawiki-config@master] Stop PHP errors from going to the hhvm channel
+
+[[https://gerrit.wikimedia.org/r/409171]]",1518126418,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 374895 merged by jenkins-bot:
+[mediawiki/core@master] exception: Support message normalisation for structured logging
+
+[[https://gerrit.wikimedia.org/r/374895]]
+",1504804114,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 374895 had a related patch set uploaded (by Krinkle; owner: Krinkle):
+[mediawiki/core@master] exception: Support message normalisation for structured logging
+
+[[https://gerrit.wikimedia.org/r/374895]]
+",1504129234,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Checklist (//EDIT: Moved to task description.//)
+",1518121066,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+* [x] Fix de-duplication and message counting by ensuring `normalized_message` does not include the exception_id. – Pending review: https://gerrit.wikimedia.org/r/374895",1505203383,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+* [ ] Fix de-duplication and message counting by ensuring `normalized_message` does not include the exception_id. – Pending review: https://gerrit.wikimedia.org/r/374895",1504129256,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+* [ ] Fix de-duplication and message counting possible by ensuring `normalized_message` does not include the exception_id. – Pending review: https://gerrit.wikimedia.org/r/374895",1504129247,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`
+* [ ] Fix de-duplication and message counting possible by ensuring `normalized_message` does not include the exception_id.",1504128813,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"It's been several months, let's look at the current state of affairs:
+
+* MediaWiki core - <https://github.com/wikimedia/mediawiki/blob/61696a0bd/includes/exception/MWExceptionHandler.php>
+ * `exception`: PSR-3 structured message with exception context via `MWExceptionHandler::getLogContext` (includes trace)
+ * `exception-json`: JSON-formatted structured data with exception context via `getStructuredExceptionData()`  (includes trace)
+ * `error`: (Non-suppressed only) PSR-3 structured message with exception context (includes trace)
+ * `error-json` (Includes suppressed errors) JSON-formatted structured data with exception context (includes trace)
+* wikimedia/operations-mediawiki-config - <https://github.com/wikimedia/operations-mediawiki-config/tree/f750c8930f/wmf-config>
+ * `exception`: Enabled (to mwlog and to logstash)
+ * `exception-json`: Disabled (to mwlog only)
+ * `error`: Enabled (to mwlog and to logstash)
+ * `error-json`: Disabled
+* Logstash config - <https://github.com/wikimedia/puppet/blob/87740eaedc/modules/role/files/logstash/filter-mediawiki.conf>
+ * Augments `channel=exception`
+ * Converts any `channel=exception-json` to `channel=exception` (Unused, todo: remove)
+* logstash.wikimedia.org receives:
+ * `type:hhvm` - All non-suppressed error messages and fatal errors (no trace)
+ * `type:mediawiki channel:exception` - Fatals and caught exceptions logged by MediaWiki, structured and includes trace.
+ * `type:mediawiki channel:error` - Non-suppressed error messages, structured and includes trace.
+
+Known issues or remaining tasks:
+* **Nothing?** {icon check color=green} **Resolved**?
+
+Clean up or optimisation:
+* [ ] Avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911
+* [ ] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`",1504128659,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Since 9eafbebdd882a562171fd0e46dcd5a9ec1e55cf8 has been deployed, some new error logs are surfacing \O/  An example is {T158770}  :-}
+",1487774255,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"The `error` channel (with severity=ERROR or maybe WARNING) should be added added to fatalmonitor on logstash, I suppose?",1487734726,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,[[https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-2017.02.22/mediawiki/?id=AVpjaHVDlL3ktRIGM6p7|Example error]]. See T136849#3045285 for comments on the format. (Except `exception.trace` seems different here. Or just has random errors in different ways than for other exceptions.),1487726805,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338820 merged by jenkins-bot:
+Route PHP warnings from the handler into udp2log
+
+[[https://gerrit.wikimedia.org/r/338820]]",1487639339,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338911 had a related patch set uploaded (by Gergő Tisza):
+Make it possible to not propagate errors to PHP
+
+[[https://gerrit.wikimedia.org/r/338911]]
+",1487638133,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338901 had a related patch set uploaded (by Gergő Tisza):
+Do not mix suppressed errors with non-suppressed ones
+
+[[https://gerrit.wikimedia.org/r/338901]]
+",1487633673,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338821 merged by jenkins-bot:
+MWExceptionHandler::handleError: Set log severity based on error level
+
+[[https://gerrit.wikimedia.org/r/338821]]",1487632148,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041561, @Tgr wrote:
+> The point is that the handler should not return false on errors which PHP would only log but not abort on, so that warnings don't get duplicated.
+
+Ok, I'm finally getting what you are working towards. Thanks for sticking with me. :) It would need some config flag as you mentioned in T45086#3041550 since the default behavior of the logging system is discard everything.",1487620029,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041550, @Tgr wrote:
+>>>! In T45086#3041541, @bd808 wrote:
+>> By not returning false and instead handling everything internally in the custom handler, the handler itself becomes responsible for deciding when to abort the request.
+> 
+> Yes, and it's a trivial decision (assuming we want to replicate the existing behavior): just abort on `*_ERROR`, unless PHP error reporting is turned off. So would there be any disadvantage to doing that? We could abort via exceptions which is more useful (HHVM can log the trace when the script aborts with an error but normal PHP can't), plus generally have better logging, at the cost of higher log volume / manual setup needed. It should probably be configurable and off by default but for WMF servers (and anyone else who cares enough about error logging to fine-tune it) it seems like a win.
+
+If the handler returns false then $php_errormsg is not set (based on code inspection). Grep shows it being used by PEAR Net/Socket, it calls @ini_set('track_errors', 1).",1487619640,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041557, @bd808 wrote:
+> How is raising an unhandled exception functionally different than passing control back to the default error handler? Is this an attempt to get more data into the PHP runtime's error log or less? I'm confused about the goal here.
+
+The point is that the handler should not return false on errors which PHP would only log but not abort on, so that warnings don't get duplicated. For errors which need the script to abort, IMO just push them to the exception channel (ie. don't log in the error handler but throw an exception) because that behaves nicer with non-log-based debugging (e.g. the developer would see a stack trace instead of just an error message, the user would see an exception hash that they can report). But logging and returning false, or just `die`ing, are also viable alternatives, the primary issue is log duplication for non-fatals.",1487619367,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041550, @Tgr wrote:
+>>>! In T45086#3041541, @bd808 wrote:
+>> By not returning false and instead handling everything internally in the custom handler, the handler itself becomes responsible for deciding when to abort the request.
+> 
+> Yes, and it's a trivial decision (assuming we want to replicate the existing behavior): just abort on `*_ERROR`, unless PHP error reporting is turned off. So would there be any disadvantage to doing that? We could abort via exceptions which is more useful (HHVM can log the trace when the script aborts with an error but normal PHP can't), plus generally have better logging, at the cost of higher log volume / manual setup needed. It should probably be configurable and off by default but for WMF servers (and anyone else who cares enough about error logging to fine-tune it) it seems like a win.
+
+How is raising an unhandled exception functionally different than passing control back to the default error handler? Is this an attempt to get more data into the PHP runtime's error log or less? I'm confused about the goal here.",1487618837,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041541, @bd808 wrote:
+> By not returning false and instead handling everything internally in the custom handler, the handler itself becomes responsible for deciding when to abort the request.
+
+Yes, and it's a trivial decision (assuming we want to replicate the existing behavior): just abort on `*_ERROR`, unless PHP error reporting is turned off. So would there be any disadvantage to doing that? We could abort via exceptions which is more useful (HHVM can log the trace when the script aborts with an error but normal PHP can't), plus generally have better logging, at the cost of higher log volume / manual setup needed. It should probably be configurable and off by default but for WMF servers (and anyone else who cares enough about error logging to fine-tune it) it seems like a win.",1487618437,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338821 had a related patch set uploaded (by BryanDavis):
+MWExceptionHandler::handleError: Set log severity based on error level
+
+[[https://gerrit.wikimedia.org/r/338821]]
+",1487618087,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041483, @bd808 wrote:
+> One way to provide granularity without creating N log channels would be to actually use the PSR3 log level in the generated log events:
+
+I would still put suppressed logs into their own channel because the way we seem to be using suppression is usually to prevent the program from being stopped and not so much to suppress logging, so having severity information for suppressed events seems useful. I agree about the rest (I actually wrote the patch yesterday but apparently forgot to submit it).",1487617990,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Is someone actually saying the log volume is too high? It looks to me like it's blocked on nobody giving a crap since 2015. Suppressed errors were removed from the stream in https://gerrit.wikimedia.org/r/#/c/177096/,1487617790,PHID-USER-k6tmz5ylx4rzfl3bitse,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041502, @Tgr wrote:
+>>>! In T158270#3041160, @bd808 wrote:
+>> We [return false from the error handler] that because it's the correct way for a default `set_error_handler()` to function. If we swallowed the errors there without returning false then `$php_errormsg` would not be populated and all errors would be handled as though the `@` suppression operator was applied to every line in the codebase.
+> 
+> We don't seem to use `$php_errormsg` anymore, so as far as I can see all that would do is to switch error logginrg to Monolog instead of the PHP/HHVM log files. (Assuming we die / throw an exception for errors which would interrupt program execution when unhandled.) Isn't that a good thing? It seems counterproductive to have the same error in logstash both as a Monolog event with traces etc. and a mostly useless HHVM record. Or are we worried about Monolog being more fragile / less reliable than logfiles/syslog?
+
+I think you are confusing the log data that we collect in WMF production and how PHP/HHVM work. The error handler must either abort the execution of the request or not. By not returning false and instead handling everything internally in the custom handler, the handler itself becomes responsible for deciding when to abort the request. If the handler returns (i.e. doesn't abort the request somehow) then it is functionally the same as applying `@` suppression to all lines in all scripts.",1487617740,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 338820 had a related patch set uploaded (by Tim Starling):
+Route PHP warnings from the handler into logstash
+
+[[https://gerrit.wikimedia.org/r/338820]]
+",1487617563,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T158270#3041160, @bd808 wrote:
+> We [return false from the error handler] that because it's the correct way for a default `set_error_handler()` to function. If we swallowed the errors there without returning false then `$php_errormsg` would not be populated and all errors would be handled as though the `@` suppression operator was applied to every line in the codebase.
+
+We don't seem to use `$php_errormsg` anymore, so as far as I can see all that would do is to switch error logginrg to Monolog instead of the PHP/HHVM log files. (Assuming we die / throw an exception for errors which would interrupt program execution when unhandled.) Isn't that a good thing? It seems counterproductive to have the same error in logstash both as a Monolog event with traces etc. and a mostly useless HHVM record. Or are we worried about Monolog being more fragile / less reliable than logfiles/syslog?",1487617325,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,">>! In T45086#3041403, @Tgr wrote:
+> What's the current state of this task? Is it blocked in the log volume being too high? There are a few things we could do about that:
+> * only log warnings (at least initially), not notices
+> * sample
+> * send suppressed errors to a separate channel which can be blackholed
+> * cut down the number of warnings/notices in production (a lot of that has been happening recently, so maybe it's worth doing another experiment and reassess the situation?)
+
+One way to provide granularity without creating N log channels would be to actually use the PSR3 log level in the generated log events:
+* suppressed -> debug
+* E_STRICT -> debug
+* E_NOTICE, E_USERNOTICE, E_DEPRECATED, E_USER_DEPRECATED -> info
+* E_WARNING, E_CORE_WARNING, E_COMPILE_WARNING, E_USER_WARNING -> warning
+* E_RECOVERABLE_ERROR -> error
+
+It would be a pretty simple patch to MWExceptionHandler to allow the caller of `MWExceptionHandler::logError()` to specify a severity level and then to adjust `MWExceptionHandler::handleError()` to set an appropriate level. The current implementation in `MWExceptionHandler::logError()` emits all events as severity `error`.",1487616845,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"What's the current state of this task? Is it blocked in the log volume being too high? There are a few things we could do about that:
+* only log warnings (at least initially), not notices
+* sample
+* send suppressed errors to a separate channel which can be blackholed
+* cut down the number of warnings/notices in production (a lot of that has been happening recently, so maybe it's worth doing another experiment and reassess the situation?)",1487615460,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"@bd808 Thanks!
+
+Looks like we're not using `error-json` in Logstash yet. For PHP Notice and Warning events, Logstash uses the apache2/hvvm source still (which doesn't have stack traces). Currently blocked on T88732.",1429806541,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"@bd808 Thanks!
+
+Looks like we're not using `error-json` in Logstash yet. For PHP Notice and Warning events, Logstash uses the apache2/hvvm source still (which doesn't have stack traces).",1425357563,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"@bd808 Thanks!
+
+Looks like we're not using `error-json` in Logstash yet. For PHP Notice and Warning events, Logstash uses the apache2 error_log source still (which doesn't have stack traces).",1424825151,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 177096 merged by jenkins-bot:
+exception: Hide suppressed errors in 'error' log, flag in 'error-json'
+
+[[https://gerrit.wikimedia.org/r/177096]]",1421111660,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 177095 merged by jenkins-bot:
+exception: Implement error-json log
+
+[[https://gerrit.wikimedia.org/r/177095]]",1420489388,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 177096 had a related patch set uploaded (by Krinkle):
+exception: Hide suppressed errors in 'error' log, flag in 'error-json'
+
+[[https://gerrit.wikimedia.org/r/177096]]
+
+#patch-for-review",1418054876,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"Change 177095 had a related patch set uploaded (by Krinkle):
+exception: Implement error-json log
+
+[[https://gerrit.wikimedia.org/r/177095]]
+
+#patch-for-review",1418054865,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"As of 399ba2fecf, MediaWiki has a new debug log group called ""error"" (similar to ""exception"" log we've had for years).
+
+Its entries are PHP Notices, PHP Warnings etc.. These always went (and still go) to PHP stderr (and apache's error log), but are historically lacking stack traces. 399ba2fecf hooks into PHP's error handler and produces a stack traces and forwards it to the new log.
+
+@Reedy and I enabled ([[ https://gerrit.wikimedia.org/r/#/c/173649/ | b4ace9661a ]]) this in production at Amsterdam Hackathon 2014 but it was disabled ([[ https://gerrit.wikimedia.org/r/#/c/173655/ | 82139373383c ]]) as it generated too much data on `fluorine` (1.5G in under 15 minutes).",1416970686,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"As of 399ba2fecf, MediaWiki has an new debug log group called ""error"" (similar to ""exception"" log we've had for years).
+
+Its entries are PHP Notices, PHP Warnings etc.. These always went (and still go) to PHP stderr (and apache's error log), but are historically lacking stack traces. 399ba2fecf hooks into PHP's error handler and produces a stack traces and forwards it to the new log.
+
+@Reedy and I enabled ([[ https://gerrit.wikimedia.org/r/#/c/173649/ | b4ace9661a ]]) this in production at Amsterdam Hackathon 2014 but it was disabled ([[ https://gerrit.wikimedia.org/r/#/c/173655/ | 82139373383c ]]) as it generated too much data on `fluorine` (1.5G in under 15 minutes).",1416970656,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"I wonder if we should close this. There's going to need to be some work to port this log into logstash, but that should be a different task. Also, knowing how much disk space it's going to use over a 24 hour period would be useful. The logs should certainly be very compressible...",1416933804,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"The ability to log backtraces in php errors was added in https://gerrit.wikimedia.org/r/#/c/173642/ .
+It was enabled in production in https://gerrit.wikimedia.org/r/#/c/173649/ and disabled again in https://gerrit.wikimedia.org/r/#/c/173655/ , because it was using ""up 680M in under a minute"".
+
+Having backtraces enabled is a huge help. So they should be enabled permanently and also sent into logstash.",1416852549,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,Grabbing stack traces for warnings should be possible with a custom error handler and debug_backtrace() or ErrorException. It should probably be put behind a feature flag of some sort so that deployments that don't care about tracking warnings don't incur the performance penalty of generating the backtrace.,1404420413,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,The above might be from xdebug..,1384192111,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Capture PHP warnings with stacktraces in MediaWiki and save to logstash,"PHPUnit dumps warnings to the console...
+
+Warning: Invalid argument supplied for foreach() in /var/www/wiki/mediawiki/core/includes/objectcache/SqlBagOStuff.php on line 232
+
+Call Stack:
+    0.0009     245936   1. {main}() /var/www/wiki/mediawiki/core/tests/phpunit/phpunit.php:0
+    2.0765   14629624   2. MediaWikiPHPUnitCommand::main() /var/www/wiki/mediawiki/core/tests/phpunit/phpunit.php:119
+    2.0767   14641960   3. MediaWikiPHPUnitCommand->run() /var/www/wiki/mediawiki/core/tests/phpunit/MediaWikiPHPUnitCommand.php:64
+    2.0767   14642440   4. PHPUnit_TextUI_Command->run() /var/www/wiki/mediawiki/core/tests/phpunit/MediaWikiPHPUnitCommand.php:80
+    7.3004   87363544   5. PHPUnit_TextUI_TestRunner->doRun() /usr/share/php/PHPUnit/TextUI/Command.php:176
+    7.3094   87684904   6. PHPUnit_Framework_TestSuite->run() /usr/share/php/PHPUnit/TextUI/TestRunner.php:349
+    7.4141   87686664   7. PHPUnit_Framework_TestSuite->run() /usr/share/php/PHPUnit/Framework/TestSuite.php:705
+   22.3535  178137936   8. PHPUnit_Framework_TestSuite->run() /usr/share/php/PHPUnit/Framework/TestSuite.php:705
+   22.3537  178139472   9. PHPUnit_Framework_TestSuite->runTest() /usr/share/php/PHPUnit/Framework/TestSuite.php:745
+   22.3537  178139952  10. MediaWikiTestCase->run() /usr/share/php/PHPUnit/Framework/TestSuite.php:775
+   22.3586  178141408  11. ApiQueryContinueTest->addDBData() /var/www/wiki/mediawiki/core/tests/phpunit/MediaWikiTestCase.php:109
+   23.4059  178284240  12. ApiTestCase->editPage() /var/www/wiki/mediawiki/core/tests/phpunit/includes/api/query/ApiQueryContinueTest.php:47
+   23.4063  178285904  13. WikiPage->doEditContent() /var/www/wiki/mediawiki/core/tests/phpunit/includes/api/ApiTestCase.php:56
+   23.5032  178306552  14. Title->getUserPermissionsErrors() /var/www/wiki/mediawiki/core/includes/WikiPage.php:1904
+   23.5032  178306736  15. Title->getUserPermissionsErrorsInternal() /var/www/wiki/mediawiki/core/includes/Title.php:1820
+   23.5140  178309936  16. Title->checkPermissionHooks() /var/www/wiki/mediawiki/core/includes/Title.php:2338
+   23.5142  178310696  17. wfRunHooks() /var/www/wiki/mediawiki/core/includes/Title.php:1946
+   23.5142  178310696  18. Hooks::run() /var/www/wiki/mediawiki/core/includes/GlobalFunctions.php:4032
+   23.5167  178312136  19. call_user_func_array() /var/www/wiki/mediawiki/core/includes/Hooks.php:199
+   23.5167  178312848  20. PageTranslationHooks::lockedPagesCheck() /var/www/wiki/mediawiki/core/includes/Hooks.php:199
+   23.5168  178312984  21. SqlBagOStuff->get() /var/www/wiki/mediawiki/extensions/Translate/tag/PageTranslationHooks.php:777
+   23.5168  178313336  22. SqlBagOStuff->getMulti() /var/www/wiki/mediawiki/core/includes/objectcache/SqlBagOStuff.php:200",1384189180,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-ywjb7uxxy5pimzykpwh2,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"Visual Editor sometimes creates nowiki markup around simple square text brackets. Interestingly, it does that only in some cases, and not in others. For the same structure, it can also handle the text with nowiki, but does it in others. Text case:
+
+ The example below shows that in some cases this is done, in others not:
+
+# Remains unchanged: Test text for the VisualEditor: [[Link target|These are ['''just''' normal brackets]]].
+# Superflous nowiki-tags added on editing: Test text for the VisualEditor: [[Link target|These are '''just''' [normal brackets]]].
+
+
+Edit with Visual Editor to see the effect.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**See Also**:
+{T54268}",1355402040,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_description,resolved
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,[Parsoid component reorg by merging JS/General and General. See bug 50685 for more information. Filter bugmail on this comment. parsoidreorg20130704],1372934108,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"Much of this is now resolved. [foo] is no longer nowiki-escaped, but [''foo''] is due to the apostrophes.
+
+There is still some room for (minor) improvement by moving the nowiki inside the brackets, although in some cases it is actually easier to read to wrap an entire line in nowiki instead of several nested nowikis.",1362174611,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"Note about the lost ""'''"" in the example above: that is a different bug unrelated to nowiki-escaping -- it should be fixed after the ongoing serializer refactor is complete.",1362171505,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"https://gerrit.wikimedia.org/r/49190 added URL validation in the tokenizer
+based on the wiki's configured URL protocols. This now makes the nowiki escaping more precise and fixes the snippet in this bug report.
+
+[subbu@earth lib] echo '[[Link target|These are '''just''' [normal brackets]]]' | node parse --wt2wt
+[[Link target|These are just [normal brackets]]]
+
+However, this wont be visible in the VE yet till a new deploy of Parsoid (another couple weeks, I expect).",1362171374,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"The problem is that till templates are expanded, it is hard to know whether the content of a ""[..]"" is going to a link or not.  That is the reason the tokenizer defers decisions for all [..] content till all templates are expanded so it can all be handled in a single place.
+
+But, there is another ticket for addressing this a bit more selectively which should address nowiki situations like this: https://bugzilla.wikimedia.org/show_bug.cgi?id=44449 --",1359472114,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"I believe adding illogical nowiki markup is somewhat irritating to existing editors.
+
+Perhaps a simple solution: Is there any justification for the tokenizer to consider an opening [ as a token? I believe only [http://, [https://, [irc://, [ircs://, [ftp://, [news://, [mailto: and [gopher:// should be external link tokens.",1359448382,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"One underlying issue is that our tokenizer is relatively liberal in what it accepts as an external link target, while a stricter validation is applied after templates etc are expanded. Our wikitext escaper also makes use of the tokenizer (plus some regexps), but does not (yet) consider external links that turn out to have invalid targets.
+
+Current output:
+
+echo ""[[Link target|These are '''just''' [normal brackets]]]"" | nodejs parse --wt2wt
+[[Link target|These are '''just'''<nowiki> [normal brackets]</nowiki>]]",1359415346,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"(In reply to comment #2)
+> and the fact that the last
+> ""]"" is outside the link.  
+
+The first ] is inside the link and the last 2 are the closing link.
+
+I agree that there may be more pressing matters, but compare that in one case:
+
+[[Link target|These are ['''just''' normal brackets]]
+
+the parser already works correct (does not add superfluous nowiki). Only if there is no formatting inside single square brackets it adds nowiki. I suspect this is not very logical.
+
+(... and annyoing on the live testing on en.wikipedia.)",1355510254,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"The nowiki-escaping is related to how Parsoid parses the text: [[Link target|These are ['''just''' normal brackets]]] and the fact that the last ""]"" is outside the link.  The nowiki escaping strategy is safe (but conservative) and tries not to accidentally create a wikilink when a ""]"" precedes a regular link bracket.  We (Parsoid team) should fix the parse first, add new tests, and then update the nowiki escaping.",1355508117,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't,"This appears to be a Parsoid bug; adjusting to reflect that.
+
+If you use the RT form - http://parsoid.wmflabs.org/_rtform/ - on the above string:
+
+[[Link target|These are '''just''' [normal brackets]]]
+->
+[[Link target|These are '''just'''<nowiki> [normal brackets]</nowiki>]]
+
+However, it generates correct HTML; for the other string:
+
+[[Link target|These are ['''just''' normal brackets]]]
+->
+<p data-parsoid=""{&quot;dsr&quot;:[0,54]}""><a rel=""mw:WikiLink"" href=""./Link_target"" data-parsoid=""{&quot;tsr&quot;:[0,53],&quot;a&quot;:{&quot;href&quot;:&quot;./Link_target&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;Link target&quot;},&quot;stx&quot;:&quot;piped&quot;,&quot;dsr&quot;:[0,53]}"">These are [<b data-parsoid=""{&quot;tsr&quot;:[25,28],&quot;dsr&quot;:[25,35]}"">just</b> normal brackets</a>]</p>
+
+Whereas canonical HTML from the PHP parser is:
+
+<p><a href=""/wiki/Link_target"" title=""Link target"">These are [<b>just</b> normal brackets]</a></p>
+
+[i.e., the closing not-used-for-a-link square bracket is inside the link, not outside it - however, this is probably a separate bug; happy to re-file.]",1355507224,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-sdeqwu5trbiv6f7fqfg7,task_subcomment,NA
+"VisualEditor: Suppress ""Web link"" section in link inspector suggestion list if a wiki page link already exists","Present situation: the Visual Editor, when clicking on an existing Wiki-Link, provides the chain-link icon which in turn opens a dialogue which contains a pick list. In the pick list two sections exist: ""Existing page"" (value e.g. ""Pretoria"") and ""Web link"" (e.g. ""http://Pretoria""). 
+
+The present dialogue is good enough for creating new links. However, for existing links it is somewhat confusing to offer a nonsense http:// link as an equally valid alternative to an existing or previously confirmed wiki page.
+
+I suggest to keep the present behaviour for new links, but for existing wiki-page-links suppress the ""web link"" part of the pick list. It will still be possible to enter URLs directly in the dialogue box, the enhancement is only about suppressing it in the pick list.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=43841",1355397960,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-3cu7p6qfbrrfjek7shaw,task_description,invalid
+"VisualEditor: Suppress ""Web link"" section in link inspector suggestion list if a wiki page link already exists","This refers to behaviour that has now changed such that this is no longer actionable, so marking as INVALID.",1367544076,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3cu7p6qfbrrfjek7shaw,task_subcomment,NA
+"VisualEditor: Suppress ""Web link"" section in link inspector suggestion list if a wiki page link already exists","I am not proposing ANY changes to creating a new link. So when you mark the text wikipedia.org, yes you should be provided with page and the url in the picklist.
+
+My suggestion is about the confusion that occurs when the link already exists and already points to an internal page. I believe that then the chance that users want to validly change it to an external http URL are very small and not worth the confusion. The enhancement is about avoiding visual clutter and avoiding accidental mis-selections. And in those cases where you do want to change an external link to an internal one: you can still do it, only not with the pick list.
+
+I am not sure I understand the timing issues you mention, since the web page suggestions are always non-sense suggestions, just prefixing the text with http, so it seems easily suppressible. The ajax responsible for possible pages is a different story, but the visibility of that is not under discussion.",1355435857,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-3cu7p6qfbrrfjek7shaw,task_subcomment,NA
+"VisualEditor: Suppress ""Web link"" section in link inspector suggestion list if a wiki page link already exists","Not convinced that this is correct; yes, you /can/ have a valid page at a web site, but still want to link to the external one. For the most trivial example, ""amazon.com"" is both an article (on enwiki) and a valid external link. Therefore I'm minded to WONTFIX this.
+
+Also, I'd note that there are timing issues (as the list is created before the suggestions are returned), but those are minor.",1355434976,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3cu7p6qfbrrfjek7shaw,task_subcomment,NA
+mediawiki.action.view.dblClickEdit.dblClickEdit should trigger ca-edit click instead opening URL directly,"To account for editors that don't open a new page, simulate a click instead of using window.location directly.
+
+That way editors such as VisualEditor will get the edit event and initiate the editor.
+
+VisualEditor works without this as it updates the ca-edit url with ?veaction=edit, so it'll work. But still, going through a useless reload is... useless.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355360100,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5tc7u6hpj3ir3jtg2fhh,task_description,resolved
+mediawiki.action.view.dblClickEdit.dblClickEdit should trigger ca-edit click instead opening URL directly,Code has been merged.,1358469835,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5tc7u6hpj3ir3jtg2fhh,task_subcomment,NA
+mediawiki.action.view.dblClickEdit.dblClickEdit should trigger ca-edit click instead opening URL directly,"mediawiki.action.view.dblClickEdit and mediawiki.action.view.rightClickEdit modules respectively.
+
+Change-Id: Ie8a35700bc9e74b24f234ea682ad25375e18bda4",1355379612,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-5tc7u6hpj3ir3jtg2fhh,task_subcomment,NA
+VisualEditor: Strange duplication of content after multiple save attempts,"Reported at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Error_saving_data_to_server:_error: the parsoid appears to time out(?) and reports that there's an error, while actually saving the page. Meanwhile, a second attempt at saving has the same problem, /also/ saves...but adds random duplication of sentence fragments. See 
+https://en.wikipedia.org/w/index.php?title=Cologne&diff=next&oldid=527666838
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355347080,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-vus23yeu76aembddoyxe,task_description,resolved
+VisualEditor: Strange duplication of content after multiple save attempts,I believe that this is now fixed given the changes in Parsoid and in how VE talks to it; marking as such.,1366665489,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-vus23yeu76aembddoyxe,task_subcomment,NA
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active","When using the VisualEditor and having the Preference ""Edit pages on double click (requires JavaScript)"" on, the Editor is stopped as soon as one tries to select a word  (= double click)or paragraph (= triple click). The javascript for ""Edit pages on double click (requires JavaScript)"" needs to be modified to check whether in VisualEditor mode or not (all works ok when in normal editing mode.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1355333220,PHID-USER-grpjkpfolt5gz4ljlbfg,False,PHID-TASK-3hi7my5pvgnqne4eigdb,task_description,resolved
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active","This has been fixed by Ie8a35700bc9e in mediawiki core.
+
+In the current configuration however out tabLayout is in ""add"" more (when this bug was reported, we were still in ""replace"" mode).
+
+In ""add"" mode we add an extra tab for ""VisualEditor"", so the original ""Edit"" is still there, which is the default. And double-clicking in the content area will (as it should) trigger the original editor.
+
+If/when we enable the ""replace"" mode again, since this bug is fixed, double-clicking will trigger VisualEditor as expected.
+
+So, although it can't be seen right now, as the feature is not activated right now, this bug as been fixed.
+
+To verify, edit ve.init.mw.ViewPageTarget.js and set `this.tabLayout = ""replace"";`.",1361748640,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3hi7my5pvgnqne4eigdb,task_subcomment,NA
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active",Bumping; didn't make it to 2013-01-16.,1358461249,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3hi7my5pvgnqne4eigdb,task_subcomment,NA
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active",The surface should just bind a click handler and prevent the event from bubbling up to the handler that mediawiki.action.view.dblClickEdit attaches to $content.,1355375630,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-3hi7my5pvgnqne4eigdb,task_subcomment,NA
+"VisualEditor: Handling of double click when preference ""Edit pages on double click"" is active","Immediate solution is to suppress the JS when VE is active, but not when in read mode.
+
+Longer-term, this should be refactored so that users have a ""default"" editor, and this kind of thing triggers whichever one you've chosen.",1355344807,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3hi7my5pvgnqne4eigdb,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: this.registry[name].static is undefined""","When trying to use VisualEditor on the English Wikipedia at <https://en.wikipedia.org/wiki/James_Mackay,_Baron_Mackay_of_Clashfern>, I get the following error in my browser's console:
+
+---
+[11:35:31.120] TypeError: this.registry[name].static is undefined @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Cjquery.multiSuggest%7Crangy&skin=monobook&version=20121212T032708Z&*:207
+---
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355330220,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-zivm3qjikccdl4xebglv,task_description,declined
+"VisualEditor: Fix ""Uncaught TypeError: this.registry[name].static is undefined""","Cannot reproduce this without a deep stack trace; also, this is from three months ago, and we're unlikely to still have the same issue.",1364318088,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zivm3qjikccdl4xebglv,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: this.registry[name].static is undefined""",Max - any update on this? Can you reproduce when using debug=true (so we might have a hope of finding the underlying cause)?,1360206346,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zivm3qjikccdl4xebglv,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: this.registry[name].static is undefined""","I can't reproduce this, can you still? Did you do anything special to make this happen?",1355341942,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zivm3qjikccdl4xebglv,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'typePattern' of undefined""","When I try to use VisualEditor with <https://en.wikipedia.org/wiki/User:Trevor_Parscal>, I get the following error in my browser console: Uncaught TypeError: Cannot read property 'typePattern' of undefined.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355327040,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-lin2kfpz66zdn3l3uhx2,task_description,declined
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'typePattern' of undefined""","Cannot reproduce this without a deep stack trace; also, this is from three months ago, and we're unlikely to still have the same issue.",1364318060,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lin2kfpz66zdn3l3uhx2,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'typePattern' of undefined""","Also, which browser, etc.? :-)",1355343913,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lin2kfpz66zdn3l3uhx2,task_subcomment,NA
+"VisualEditor: Fix ""Uncaught TypeError: Cannot read property 'typePattern' of undefined""","Works for me; can you still reproduce this? Did you just load the editor, or did you do something to make this happen?",1355341841,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-lin2kfpz66zdn3l3uhx2,task_subcomment,NA
+Enable Visual editor on test client,"Enable VisualEditor on test client and check if the two extensions do not interfere with each other.
+
+They should not interfere with each other except for the additional parser function(s) introduced by Wikibase client.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355287440,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-ewbthsndzjv2jnkqp2ly,task_description,declined
+Enable Visual editor on test repo,"Enable VisualEditor on test repo and check if the two extensions do not interfere with each other.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1355285580,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-dc5kyuqpkf3s6kddlzao,task_description,declined
+Enable Visual editor on test repo,"Note that VisualEditor will attempt to add edit links in the caction for pages in main namespace, but with Wikibase using main namespace for items this will be conflicting.
+
+It is possible to enable VisualEditor for specific namespaces so a work around should be pretty simple.",1355285813,PHID-USER-vlni4mhyozor7ghqnfkl,False,PHID-TASK-dc5kyuqpkf3s6kddlzao,task_subcomment,NA
+"VisualEditor: Avoid triggering ""XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.""","Feedback is one-way, we don't need to read the reponse (and we can't, due to origin policy). So we should convert this into a regular POST without XHR so that it doesn't error.
+
+Apparently though the current method does work for one-way (the request isn't blocked in Chrome).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1355277780,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-tq6ygkwi32qnc2l6vv5h,task_description,invalid
+"VisualEditor: Avoid triggering ""XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.""","We're scrapping this feedback system, so marking as INVALID.",1370629685,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tq6ygkwi32qnc2l6vv5h,task_subcomment,NA
+"VisualEditor: Avoid triggering ""XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.""","I'm watching this bug.  Parsoid does support CORS headers via a configuration in localsettings.js (although maybe not yet on this particular response), so if you do decide to fix this on the parsoid end let me know.",1366316690,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-tq6ygkwi32qnc2l6vv5h,task_subcomment,NA
+"VisualEditor: Avoid triggering ""XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.""",De-prioritising and pulling from target milestone.,1361816423,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tq6ygkwi32qnc2l6vv5h,task_subcomment,NA
+VisualEditor: Integration in production should not ignoreHidden on user preference,"In VisualEditor.hooks.php the function to evaluate whether or not to show the VisualEditor has ignoreHidden set true on the user preference check; this should be false in production.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1355190000,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ffowylul32ecwhb6soji,task_description,resolved
+VisualEditor: Integration in production should not ignoreHidden on user preference,Related URL: https://gerrit.wikimedia.org/r/61035 (Gerrit Change Idebb147ee03ad956cd0f3826c304db65eed1e34e),1366995915,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ffowylul32ecwhb6soji,task_subcomment,NA
+VisualEditor: Integration in production should not ignoreHidden on user preference,Fixed and being deployed today.,1366929861,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ffowylul32ecwhb6soji,task_subcomment,NA
+VisualEditor: Integration in production should not ignoreHidden on user preference,Related URL: https://gerrit.wikimedia.org/r/60911 (Gerrit Change Iec91b30422017ce9d71bc71b2cbeb71688e0d18f),1366920806,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ffowylul32ecwhb6soji,task_subcomment,NA
+VisualEditor: Integration in production should not ignoreHidden on user preference,Related URL: https://gerrit.wikimedia.org/r/60899 (Gerrit Change I0e55faca4eabe910d9b4d8ca8c6b4b0bd42e8539),1366916775,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ffowylul32ecwhb6soji,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"On a site such as the English Wikipedia, editors often create redirects for misspelled versions of page titles so that readers can have an easier time accessing the content they're after. For example, if a reader enters ""Barrack Obama"" or ""Dave Chapelle"" or ""Steve Carrell"" into the search bar, they'll be redirected automatically to ""Barack Obama"" or ""Dave Chappelle"" or ""Steve Carell"" (respectively) automatically. This is a good thing.
+
+However, these redirects can be problematic when editors insert this text into a page in the form of a link and don't get any feedback that the text they've entered is a misspelling (that it's likely wrong and not the text they intended to insert). In fact, the user gets the opposite feedback: they get feedback (a blue link) indicating that they've inserted an appropriate, working link.
+
+These misspelled redirects can be tagged with templates such as ""{{R from misspelling}}"" which generally automatically categorize them.
+
+I'm not sure what the appropriate behavior here is. I believe that continuing to allow users to insert links to misspelled words or phrases unknowingly is a bug and should be addressed somehow.
+
+There are a few options here, but I'm curious to read what others think about this. The goal here is to reduce the number of misspelled links that are added to a page by giving the user warning or notice that they've tried to insert a misspelled link (e.g., [[Hilary Clinton]] or [[Stephen Spielberg]]).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Linked_misspellings
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=13595",1355001180,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-nnoorqwvduraaxjx3s3c,task_description,open
+Redirects mask incorrect spellings (misspellings) in articles,"(In reply to John Broughton from comment #5)
+> (In reply to John Mark Vandenberg from comment #4)
+> 
+> I think we've wandered off topic, for which I'll take some responsibility.
+> The issue is NOT links to redirect pages, which (typically as hatnotes) can
+> be absolutely correct. Rather, the problem is wikilinks to redirect pages
+> **that are marked as being for misspellings**.
+
+Thanks for clarifying your solutions are for misspelling redirects only.
+
+What I was focusing on was the underlying problem that the software does not have a good way to determine which redirects are marked as misspellings?  And the concept of misspelling is IMO too complex to be built into the mediawiki layer.
+
+Surely not by looking for [[Template:R from misspelling]] or [[Category:Redirects from misspellings]] (as was done for disambiguation pages)
+
+__MISSPELLING__ ?  That would be equally odd.
+
+Bug 13595 is an interesting idea that records per-redirect custom messages to be used in one context (above target article), but the same approach may be used to provide custom messages to other contexts (such as in VE).
+
+Another approach may be to add misspellings to Wikidata, preferably as a misspellings attribute on the target Qs (similar to labels), rather than have redirects as distinct items in Wikidata (as was done for dab pages).",1399700412,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"(In reply to John Mark Vandenberg from comment #4)
+
+I think we've wandered off topic, for which I'll take some responsibility. The issue is NOT links to redirect pages, which (typically as hatnotes) can be absolutely correct. Rather, the problem is wikilinks to redirect pages **that are marked as being for misspellings**. So, let me reword the four alternatives I gave, above, to (hopefully) make this clearer.
+
+In articlespace (only):
+
+1. The software adds an administrative category, ""Articles with wikilinks to redirect pages for misspellings"", when an article is saved that has one or more of these problematical links.
+
+2. Links to redirect pages for misspellings are shown in yellow, both when previewing an edit and after saving the page. (With VisualEditor, the yellow coloring would appear immediately after typing the wikilink, which is ideal.) However, the editor can save the page with the (problematical) wikilink still on it.
+
+3. The software issues a warning when an editor tries to save a page with a link to a redirect page used to fix a misspelling, but allows the editor to override this. (Misspelled wikilinks need to be highlighted, of course; the software could also make it easy to accept a spelling change, since the redirect page points to the correct spelling of the article being linked to)
+
+4. The software issues a warning when an editor tries to save a page with a link to a redirect page for a misspelling, and prevents the editor from overriding this. (Misspelled wikilinks need to be highlighted, of course.)
+
+** Addendum:** 
+
+I'll also note that since we're concerned with *what the reader sees*, we should ignore wikilinks where a pipe is used, since the software can't (easily) determine if what the reader sees is correct:  [[wikilink to redirect|possibly correctly spelled text]].",1399698286,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"(In reply to John Broughton from comment #3)
+> Google translate didn't turn Comment 2 into anything meaningful for me, so
+> here are four alternative solutions, which could be implemented in the
+> software, one or more of which may already have been suggested above (in
+> Polish).
+> 
+> ...
+> 
+> Alternatives #1, #2, and #3 are compatible; all could be implemented
+> together. Alternative #4 is problematical in that an editor who is doing a
+> minor change might be blocked from saving that change even though he/she had
+> nothing to do with creating the wikilinks that go to redirects, and he/she
+> may not understand how to correct this. (Think of a relatively new editor,
+> or an IP editor.)
+> 
+> Implementing #1 would be invisible to the reader; #2 might cause a bit of
+> confusion.
+
+These solutions all presume that *every* link to a redirect is problematic.  If that is what the software presumes, it will cause more problems than it solves.  There are many instances where a link to a redirect page is appropriate.  If they are categorised into a maintenance category, some idiot will try to 'fix' them.  If it is more difficult to link to redirects using the VE UI, competent editors will complain bitterly.
+
+> *** Or someone could just create a bot that notifies editors that they've
+> made a mistake with their wikilink - as does DPL bot, for links to
+> disambiguation pages. ***
+
+This would be helpful, and the bot author could adapt the logic to understand when links to redirects are desirable.  For redirects categorised as spelling mistakes, a bot could also fix them automatically.",1399683919,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"Google translate didn't turn Comment 2 into anything meaningful for me, so here are four alternative solutions, which could be implemented in the software, one or more of which may already have been suggested above (in Polish).
+
+In articlespace (only):
+
+1. The software adds an administrative category, ""Articles with wikilinks to redirect pages"", when an article is saved that has one or more problematical links.
+
+2. Links to redirect pages are shown in yellow, both when previewing an edit and after saving the page. (With VisualEditor, the yellow coloring would appear immediately after typing the wikilink, which is ideal.) However, the editor can save the page with the (problematical) wikilink still on it.
+
+3. The software issues a warning when an editor tries to save a page with a link to a redirect page, but allows the editor to override this. (Problem wikilinks need to be highlighted, of course.)
+
+4. The software issues a warning when an editor tries to save a page with a link to a redirect page, and prevents the editor from overriding this. (Problem wikilinks need to be highlighted, of course.)
+
+Alternatives #1, #2, and #3 are compatible; all could be implemented together. Alternative #4 is problematical in that an editor who is doing a minor change might be blocked from saving that change even though he/she had nothing to do with creating the wikilinks that go to redirects, and he/she may not understand how to correct this. (Think of a relatively new editor, or an IP editor.)
+
+Implementing #1 would be invisible to the reader; #2 might cause a bit of confusion.
+
+*** Or someone could just create a bot that notifies editors that they've made a mistake with their wikilink - as does DPL bot, for links to disambiguation pages. ***",1371419572,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,"The solution on pl.wiki is not to create redirects from misspelings. The ""Did you mean"" feature catches these well enough, and educates the reader on his mistake.
+
+(Policy: https://pl.wikipedia.org/wiki/Wikipedia:Przekierowanie#Stosowanie_przekierowa.C5.84 , last paragraph)",1355001897,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+Redirects mask incorrect spellings (misspellings) in articles,This is a serious problem on some wikis (thousands of misspelled links): <https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Linked_misspellings>.,1355001544,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-nnoorqwvduraaxjx3s3c,task_subcomment,NA
+VisualEditor: Links should not be allowed to be created spanning only whitespace,"Select some whitespace and open the link inspector and create the link.
+The SurfaceFragment.trimRange method is not trimming the space if the range only contains space.
+
+The correct behavior should be to trim the space then insert the location text into the document.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354917180,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-2mqmky2wjztbg6g74ags,task_description,resolved
+VisualEditor: Links should not be allowed to be created spanning only whitespace,"Patch in https://gerrit.wikimedia.org/r/37541
+This is DM stuff so Trevor or Roan will need to review.",1354917532,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-2mqmky2wjztbg6g74ags,task_subcomment,NA
+VisualEditor: Page creation should have a customized save button,"Similar to bug 41865
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1354749120,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-mzqqlikp4a7wrk4foid4,task_description,resolved
+VisualEditor: Page creation should have a customized save button,Merged,1354758526,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-mzqqlikp4a7wrk4foid4,task_subcomment,NA
+VisualEditor: Page creation should have a customized save button,Fixed in gerrit 37144.,1354750343,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mzqqlikp4a7wrk4foid4,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**Author:** `bugzilla.wikimedia.org.76374`
+
+**Description:**
+curl -I 'http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.wikimediaShopLink.core%7Cjquery.client%2Ccookie%2CmwExtension%7Cmediawiki.cldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cutil%7Cmediawiki.language.data%2Cinit%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup&skin=vector&version=20121203T183954Z&*'
+curl: (52) Empty reply from server
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1354560840,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_description,resolved
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out",">>! In T44653#480329, @Nemo_bis wrote:
+> Every time I look (e.g. on webpagetest.org), I always find one or two ""failing"" load.php calls however I test it. Usually it's the CentralNotice taking too much
+
+From looking at the original description I tend to think it was a CentralNotice issue indeed. On the other hand, bannercontroller stuff was refactored in the meanwhile.",1490687031,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Closing for now as most likely the original cause can no longer cause a page to take 12 seconds to load given the following major changes that have happened since then.
+
+* Switch to HTTPS and HTTP/2 made bits re-use the same connection instead of establishing a new connection, thus speeding things up and reducing the changes that a connection gets cut off.
+ * {T96848}
+ * {T94896}
+ * {T95448}
+ * ..
+* Since then, bits itself has been folded into the main domains entirely, further optimising this re-use: 
+ * {T107430}
+* Since then, we've also reduced the number of requests that block rendering and page-ready
+ * {T107399}",1490658160,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","@Nemo_bis: I'm asking anybody in the CC list as someone might have faced the same problem in that IP range. 
+If I had asked anybody specifically, I would have prefixed a name. :)",1435685379,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","> Does this problem still happen nowadays?
+
+Who are you asking? The reporter is one of those made into ghosts by the bugzilla murder.",1435684764,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","
+Does this problem still happen nowadays?",1435675753,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","> We no longer use bits to serve this content. So this can probably be closed now ?
+
+What makes you think the issue was caused by the fact of being served from that domain?",1435039204,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out",We no longer use bits to serve this content. So this can probably be closed now ?,1435011660,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Here is a Chrome plugin that provides a workaround:
+
+https://chrome.google.com/webstore/detail/wikipedia-speedup/ppmagkdpdaaabpmdppckemgkngkpchdl?hl=en",1415214025,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","(In reply to Macavity from comment #19)
+> This happens reliably on the IP range my ISP uses (looks like
+> 86.141.0.0/16), when jqueryMsg is in the query string:
+> 
+> This times out:
+
+Works for me as I get a cached response /* cache key: enwiki:resourceloader:filter:minify-js:7:519abda9a1640250a7c561ccfd0f22f8 */
+I don't see ongoing CentralNotice campaigns for UK.",1414919322,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","This happens reliably on the IP range my ISP uses (looks like 86.141.0.0/16), when jqueryMsg is in the query string:
+
+This times out:
+
+http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin%7Cext.uls.init%2Cinterface%2Cpreferences%2Cwebfonts%7Cext.visualEditor.viewPageTarget.init%7Cjquery.accessKeyLabel%2CbyteLength%2Cclient%2Ccookie%2CmwExtension%2CtabIndex%2Cthrottle-debounce%2Ctipsy%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.language.init%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cmmv.base%2Chead%7Cskins.vector.js&skin=vector&version=20141031T180422Z&*
+
+This returns:
+
+http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin%7Cext.uls.init%2Cinterface%2Cpreferences%2Cwebfonts%7Cext.visualEditor.viewPageTarget.init%7Cjquery.accessKeyLabel%2CbyteLength%2Cclient%2Ccookie%2CmwExtension%2CtabIndex%2Cthrottle-debounce%2Ctipsy%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.language.init%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cmmv.base%2Chead%7Cskins.vector.js&skin=vector&version=20141031T180422Z&*",1414918068,PHID-USER-klksrqr4iars7szz53kl,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Every time I look (e.g. on webpagetest.org), I always find one or two ""failing"" load.php calls however I test it. Usually it's the CentralNotice taking too much, I don't see what can be done in this component.",1404555792,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Correct, comment 14 - comment 17 are a different issue.",1368105953,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Yeah, bits was having issues earlier today. https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&oldid=69483 and http://status.wikimedia.org/8777/156486/Static-assets-(CSS/JS) seem to confirm this. I think separate issues are getting mixed in to a single bug, though.",1368059296,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","And little bit more. In my case it is maybe just only DNS updating problem. In my home ip bits.wikimedia.org resolves to  91.198.174.233, 2620:0:862:ed1a::a,  bits.esams.wikimedia.org.
+
+In .kapsi.fi where everything is working fine bits.wikimedia.org resolves to  2620:0:861:ed1a::a, 208.80.154.234, bits-lb.eqiad.wikimedia.org",1367994507,PHID-USER-pmmyhpxkzmo6lbo5bcqo,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","This seems to something like my ongoing Wikipedia/Wikimedia problem. In last 12 hours most of queries to http://bits.wikimedia.org from my home IP are failed, but not all. However https://bits.wikimedia.org seems to work normally. I also asked in community portal of fiwiki if wikipedia has been slow and answer was  it has been worked normally.
+
+Commands asked:
+
+--- CLIP ----
+curl -i http://bits.wikimedia.org/
+curl: (7) Failed to connect to 2620:0:862:ed1a::a: Network is unreachable
+
+--- CLIP ----
+curl -i https://bits.wikimedia.org/
+HTTP/1.1 200 OK
+Server: nginx/1.1.19
+Date: Wed, 08 May 2013 05:45:54 GMT
+Content-Type: text/html
+Content-Length: 178
+Connection: keep-alive
+Last-Modified: Thu, 12 Aug 2010 16:12:20 GMT
+ETag: ""b2-48da2a1772100""
+X-Varnish: 693529009
+Via: 1.1 varnish
+Accept-Ranges: bytes
+X-Varnish: 1488468153
+Age: 0
+Via: 1.1 varnish
+X-Cache: strontium miss (0), cp3021 miss (0)
+
+<html>
+	<head><title>bits and pieces</title>
+		<meta http-equiv=""refresh"" content=""1;url=http://www.wikimedia.org/"" />
+	</head>
+<body>
+bits and pieces live here!
+</body>
+</html>
+
+--- CLIP ----
+curl -i http://bits.wikimedia.org/geoiplookup
+HTTP/1.1 200 geoiplookup
+Server: Varnish
+Content-Type: text/javascript
+Content-Length: 111
+Last-Modified: Wed, 08 May 2013 05:58:57 GMT
+Cache-Control: private, max-age=86400, s-maxage=0
+Accept-Ranges: bytes
+Date: Wed, 08 May 2013 05:58:57 GMT
+X-Varnish: 2987799549
+Age: 0
+Via: 1.1 varnish
+Connection: close
+X-Cache: cp3022 miss (0)
+
+Geo = {""city"":""REMOVED"",""country"":""FI"",""lat"":""REMOVED"",""lon"":""REMOVED"",""IP"":""91.153.84.229"",""netmask"":""24""}
+
+--- CLIP ----
+traceroute bits.wikimedia.org
+traceroute to bits.wikimedia.org (91.198.174.233), 30 hops max, 60 byte packets
+ 1  kotiboksi.Elisa (192.168.100.1)  0.662 ms  0.861 ms  1.079 ms
+ 2  tkueur1.fi.elisa.net (91.153.48.1)  14.876 ms  15.553 ms  15.781 ms
+ 3  ge1-0-0.tkubra-p1.fi.elisa.net (139.97.9.13)  13.879 ms  15.328 ms  16.106 ms
+ 4  so7-2-0.esptnl-p1.fi.elisa.net (139.97.6.1)  19.842 ms  21.924 ms  22.199 ms
+ 5  ip-rr.hkika234.fi.elisa.net (139.97.0.162)  22.454 ms  23.130 ms  23.885 ms
+ 6  213.192.184.109 (213.192.184.109)  25.150 ms  17.379 ms  18.065 ms
+ 7  as0-0.bbr1.ams1.nl.eunetip.net (213.192.191.226)  54.601 ms  50.913 ms  47.484 ms
+ 8  * * *
+ 9  * * *
+10  * * *
+....
+
+Discussion in community portal:
+http://fi.wikipedia.org/wiki/Wikipedia:Kahvihuone_%28tekniikka%29#Wikipedian_hidastelu",1367992987,PHID-USER-pmmyhpxkzmo6lbo5bcqo,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Bug 39322 came to my mind, so I'd still appreciate the output of the following commands
+
+traceroute bits.wikimedia.org
+
+curl -i http://bits.wikimedia.org/",1366803080,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Andre: we have already determined that it is a problem related to the source ip range.",1363057173,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Look at the screenshot. Just one out of multiple calls to the same script fails. So the routing is definitely ok.",1363057106,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Just realizing that this question still stands:
+
+> Is the routing to the bits servers ok from both ip address ranges?",1363000685,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","For me in Firebug that specific call is 51ms and 14.9kb (being logged in), for you 11440ms and 0.0kb.
+
+And in my case the URL is
+http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.wikimediaShopLink.core%7Cjquery.client%2Ccookie%2CmwExtension%7Cmediawiki.cldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cutil%7Cmediawiki.language.data%2Cinit%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cwikibase.client.init&skin=vector&version=20130311T110922Z&*",1363000652,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+screenshot of timeout in firebug
+
+**Attached**: {F10260}",1362773214,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Yes, it is still a problem. See the screenshot.",1362773152,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","As we've changed data centers in late January and the related setup, could you please test if this is still a problem?",1362732889,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+This appears to be a *script bug* in http://bits.wikimedia.org/en.wikipedia.org/load.php because the server itself shows no problems at all.",1356131835,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out",I'm wondering if this is a dup of bug 41130?,1356116359,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","(In reply to comment #2)
+> Works from 81.169.0.0/16, but *NOT* from 78.52.0.0/16 (Europe/Berlin/dynamic
+> IP
+> for DSL endpoint)
+
+Is the routing to the bits servers ok from both ip address ranges?",1355671621,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","**bugzilla.wikimedia.org.76374** wrote:
+
+Works from 81.169.0.0/16, but *NOT* from 78.52.0.0/16 (Europe/Berlin/dynamic IP for DSL endpoint)",1355671137,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+"en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out","Works for me - is this still an issue, and on which continent are you based? There were some load issues but they are mostly fixed now.",1355665523,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d6ih3cdrbybmct3lwinv,task_subcomment,NA
+VisualEditor: Only replace url on veaction=edit if there is no other query,"Go to a VE wiki page directly in edit mode:
+
+http://mediawiki.org/wiki/VisualEditor:Test?uselang=he&veaction=edit
+
+The integration changes the URL to:
+
+https://www.mediawiki.org/wiki/VisualEditor:Test
+
+... instead of:
+
+https://www.mediawiki.org/wiki/VisualEditor:Test?uselang=he
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1354218360,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-er2j2jzi7wxs7w6xckns,task_description,resolved
+VisualEditor: Only replace url on veaction=edit if there is no other query,Code now live in master; will get deployed in the next cycle.,1354565570,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-er2j2jzi7wxs7w6xckns,task_subcomment,NA
+VisualEditor: Only replace url on veaction=edit if there is no other query,Change-Id: Ia63c937d3a0a68acaa178486ab439bc1ea9db8af,1354423024,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-er2j2jzi7wxs7w6xckns,task_subcomment,NA
+VisualEditor: Integration fails if an article has an '@' character in its title,"VE/MW integration fails (does not trigger but instead throws two errors, below) if an article has an '@' character in its title, though these are valid
+
+Uncaught Error: Bad constructor arguments    mediawiki.Uri.js:165
+Uri                     mediawiki.Uri.js:165
+mw.UriRelative          mediawiki.Uri.js:318
+(anonymous function)    mediawiki.Uri.js:325
+(anonymous function)    mediawiki.Uri.js:328
+
+Uncaught TypeError: undefined is not a function    ve.init.mw.ViewPageTarget.js:18
+VeInitMwViewPageTarget    ve.init.mw.ViewPageTarget.js:18
+(anonymous function)      ve.init.mw.ViewPageTarget.js:1121
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**URL**: https://www.mediawiki.org/wiki/VisualEditor:Test@4",1353449520,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pjkjsbfhouqskvpvg6ev,task_description,resolved
+VisualEditor: Integration fails if an article has an '@' character in its title,"Fixed upstream, will be in 1.21wmf9.",1358878792,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pjkjsbfhouqskvpvg6ev,task_subcomment,NA
+VisualEditor: Integration fails if an article has an '@' character in its title,Upstream issue in the mediawiki.Uri module of mediawiki/core.,1354127118,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-pjkjsbfhouqskvpvg6ev,task_subcomment,NA
+VisualEditor: Putting cursor immediately before link should display inspector icon,"Currently, putting the cursor inside a link displays the inspector icon (except for bug 42276). Putting the cursor immediately after a link (i.e. between the last linked character and the first non-linked character) also displays the icon, but putting it immediately before the icon (between the last non-linked character and the first linked character) does not. I think it should.
+
+Of course, the interesting question here is what should happen when you have two directly adjacent links and you put the cursor between them.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353379740,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nm5db6sizlej6gdhkkqp,task_description,declined
+VisualEditor: Putting cursor immediately before link should display inspector icon,"Per IRL discussion, this is wontfix.",1353539731,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-nm5db6sizlej6gdhkkqp,task_subcomment,NA
+VisualEditor: Pre-annotations code annotates characters with the empty set,"1. Open any document
+2. Blank it
+3. Type some text
+4. Dump the model into the console (ve.instances[0].documentModel.data)
+
+Expected output: [ 'F', 'o', 'o', 'b', 'a', 'r' ]
+Actual output: [ 'F', ['o', ve.AnnotationSet([])], ['b', ve.AnnotationSet([])] ...
+
+The pre-annotations code is applying the empty set as a pre-annotation to every character except the first. This shouldn't happen, it should just not annotate if it's got nothing to annotate with.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1353378840,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vedbqhk6swjrkcfcznus,task_description,resolved
+VisualEditor: Pre-annotations code annotates characters with the empty set,Actually fixed in gerrit 34684,1353546438,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vedbqhk6swjrkcfcznus,task_subcomment,NA
+VisualEditor: Pre-annotations code annotates characters with the empty set,"...doesn't actually fix it, will investigate.",1353543663,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vedbqhk6swjrkcfcznus,task_subcomment,NA
+VisualEditor: Pre-annotations code annotates characters with the empty set,https://gerrit.wikimedia.org/r/#/c/34598/,1353541416,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vedbqhk6swjrkcfcznus,task_subcomment,NA
+VisualEditor: Pre-annotations code annotates characters with the empty set,Trevor has a commit queued up that fixes this.,1353530421,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-vedbqhk6swjrkcfcznus,task_subcomment,NA
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page","Currently to view the underlying wikitext of a page that's in a namespace where VisualEditor is active, one clicks an ""edit source"" tab. However, when editing, if you want to see the underlying wikitext but not lose your changes or really just not have to reload the page, that isn't possible. It'd be awfully nice if you could toggle between wikitext and the VisualEditor interface without needing to reload the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57462",1352958180,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-o2rqx7ng2feqhiottjsd,task_description,open
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page",It seems like this task is sort of obsoleted by {T102398} and its blockers+dependencies.,1437012494,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-o2rqx7ng2feqhiottjsd,task_subcomment,NA
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page","When a user presses ""Save page"" (for the second time, as you point out):
+* the HTML DOM gets converted to Parsoid-format HTML+RDFa,
+* this HTML+RDFa is squirted at Parsoid, 
+* Parsoid converts it to wikitext, and
+* Parsoid saves it to the DB (using the user permissions/etc. as provided by VE from the user session).",1353022256,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o2rqx7ng2feqhiottjsd,task_subcomment,NA
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page","(In reply to comment #1)
+> This would be nice, but goes far beyond current functionality of MW core, so
+> marking as low priority.
+
+It's unclear to me at which stage the visual document that a user is editing is converted to wikitext.",1353019498,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-o2rqx7ng2feqhiottjsd,task_subcomment,NA
+"VisualEditor: Make MW's core ""edit source"" functionality load in-page","This would be nice, but goes far beyond current functionality of MW core, so marking as low priority.",1353018184,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-o2rqx7ng2feqhiottjsd,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Currently when using the VisualEditor extension, there's a big green button that reads ""Save page"" in the top-right corner of the browsing window.
+
+When a user clicks this button labeled ""Save page"", the page is not saved. Instead, a dialog box appears in which the user is prompted to enter an edit summary. If the user then clicks the ""Save page"" button again (a second time), the page will be saved (maybe).
+
+I believe this is behavior is a little wrong. Historically the behavior of the ""Save page"" button has been to actually attempt to save the page to the database. This new workflow changes that behavior.
+
+Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+
+There's also no warning within the ""Save page"" dialog box that says that the page has not yet been saved to the database. There's no ""this is only a preview!"" text. Perhaps that's a separate bug, though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1352957520,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_description,resolved
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3957958, @Pinnerup wrote:
+> This issue has been open for 5+ years now. Please take action to differentiate the text on the two buttons so it's possible to distinguish whether pressing them will publish something immediately or not.
+
+If had a pound for every time someone said that, I'd be a rich man.
+
+Tasks come in faster than they can be worked on. The Editing team has only three full time engineers, and we have the responsibility of an entire ecosystem of editing tools across over 800 Wikimedia wikis, and thousands more third-party websites. The consequence is that many, many tasks sit around for years with no action, even though every task is very important to the person that filed it; this is an unfortunate reality of software development.",1524050312,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3957958, @Pinnerup wrote:
+> This issue has been open for 5+ years now. Please take action to differentiate the text on the two buttons so it's possible to distinguish whether pressing them will publish something immediately or not.
+
+I had a pound for every time someone said that, I'd be a rich man.
+
+Tasks come in faster than they can be worked on. The Editing team has only three full time engineers, and we have the responsibility of an entire ecosystem of editing tools across over 800 Wikimedia wikis, and thousands more third-party websites. The consequence is that many, many tasks sit around for years with no action, even though every task is very important to the person that filed it; this is an unfortunate reality of software development.",1524050081,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","With the completion of T189803, there is now more clarity about what clicking the first ""Publish changes"" button does, so this task is now resolved.",1524049612,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","I came here just for this after too often accidentally publishing an incomplete or undescribed edit. It's really frustrating to me as a user that it's not easily possible to see if pressing the ""Publish changes"" button will take me to an intermediate step allowing review and description or if it will publish the changes immediately. 
+
+This issue has been open for 5+ years now. Please take action to differentiate the text on the two buttons so it's possible to distinguish whether pressing them will publish something immediately or not.",1518175350,PHID-USER-vvb5cpvcki2rgdles7sq,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","> for example, we can provide an access to preview as an additional mode in the menu we provide access to ""Visual editing"" and ""Source editing"".
+
+I provided mockups demonstrating something like this in [[#3274084|a previous message]].",1504785682,PHID-USER-2fha2mym5lty6djs2qfl,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3579770, @Jan_Dittrich wrote:
+> From observing the users and further corroborated by the comments on Kurier 
+
+Some notes on the different observations:
+
+> 1. Users, particular experienced ones, seem to rely a lot on previewing before they save, so they want to preview //before// they save and create an entry in the history.
+
+This probably means that some users don't see preview as part of the publishing process, but as part of their edit process: edit-> preview -> continue editing...
+
+> 2. In the current UI, the only way to preview is clicking a button that indicates it does something they want to avoid: Saving directly.
+
+Having the option to preview as you publish is fine, but it does not have to be the only entry point we provide for it. Especially if we want to support users that don't see ""preview"" as part of the publishing process. for example, we can provide an access to preview as an additional mode in the menu we provide access to ""Visual editing"" and ""Source editing"". That seems to align better with the idea of supporting preview as another perspective to switch while editing. 
+
+> Thus there is a problem. Adding … does not solve all the problems. But it alleviates point 2: It indicates that clicking ""publish changes"" does //not// do immediately what they want to avoid. 
+
+I don't think that adding ellipsis is going to alleviate the issue of point 2 since the publishing button (with ellipses or other indications) has the main job of announcing the path to publishing, and being it in one or two steps, these users are not interested to go into it yet. Making the ""publish"" action (even slightly) to be less about publishing does not seem the most promising option.
+
+Let's assume that ellipses make more users access the summary panel. Is that solving the issue? I don't think the problem is that those users are not reaching the summary panel, these users probably have already done so (since they are experienced editors), the problem is they don't seem to find it natural to go through the publishing path while their editing process is not over.
+
+I'm ok with experimenting with this if people think it may have potential, but let's make sure it does not impact the regular use of publishing when people actually want to publish.
+",1504699168,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","I feel like unfortunately we already have enough tasks open about how long translations look ugly and make the interface potentially difficult to use. ""..."" is a good compromise that I really endorse.",1504695764,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","@dialmove's suggestion above to rename the button to ""Review and publish"" would also be a simple way to improve things.
+
+The downside is that the space for the button is limited, and the text can already be fairly long in some languages. E.g. in Hungarian ""Publish changes"" is ""Változtatások közzététele""; ""Review and publish"" would be something like ""Változtatások áttekintése és közzététele"".
+
+Maybe just change to ""Review"" and rely on the constructive colors to tell the user that's the next step?",1504627839,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","> I'd like to understand better the specific issues that the uncertainty about ""whether 
+> the save button saves immediately"" generates. 
+
+From observing the users and further corroborated by the comments on Kurier 
+
+1. Users, particular experienced ones, seem to rely a lot on previewing before they save, so they want to preview //before// they save and create an entry in the history.
+2. In the current UI, the only way to preview is clicking a button that indicates it does something they want to avoid: Saving directly.
+
+Thus there is a problem. Adding … does not solve all the problems. But it alleviates point 2: It indicates that clicking ""publish changes"" does //not// do immediately what they want to avoid. ",1504615255,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3578131, @Jan_Dittrich wrote:
+> Who is the one to decide about this?
+
+Me. I'm watching this task. :-)
+
+This is far from the most pressing item on the agenda, but I do agree with the statement of the problem. I like the ellipsis idea; it's not perfect, but it's easy to implement, is at least step in the right direction, and can easily be iterated on. I think more discussion about other solutions would be good.",1504606283,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3578131, @Jan_Dittrich wrote: 
+> @Pginer-WMF – what do you think? And: Who is the one to decide about this?
+
+I'm not convinced this would improve much. I'm ok with experimenting, but given the importance of the publishing workflow I'd like to have a clear hypothesis of what we expect and how to observe the impact of the change. More details below:
+
+**On the need to communicate additional steps**
+
+Ellipses may help to emphasise that the publishing process have multiple steps. The key question is whether we need to anticipate such information. There are many processes that require some kind of confirmation/follow-up step that users see as a logical progress to completion, and do not cause any kind of confusion or surprise despite those extra steps not being anticipated. For example, I don't think that adding ellipses to all actions that open any kind of panel such as ""add link"" or ""insert image"" would improve things much.
+
+I'd like to understand better the specific issues that the uncertainty about ""whether the save button saves immediately"" generates. What do we expect users to do differently if they know there are more step behind the button?
+
+The ellipses make also the call to action less strong. In addition, ellipses in buttons have been also used to communicate an action being performed (e.g., a ""Save"" button turning into ""Saving..."" after being pressed), so there is a risk of confusion for users thinking some publishing action may be going on that we may want to check.
+
+**Connection with ""preview"" issue**
+If the proposal is intended to improve the issue with preview (T155732), which some comments in this ticket still refer to, I don't think it will help much.
+
+My understanding of the preview issue is that some users don't see ""preview"" necessarily as an intermediary step in their way to publishing. That is, some users understand preview as away to check that their recent editing actions produce the expected result before continue their editing session. Since they are not completing their editing session, it is not obvious that preview will be behind the ""publish"" path. We are supporting well the scenario of ""preview in your way to publish"" but we may not be doing so well with the ""preview as you edit"". 
+
+Ellipsis help to emphasise that the publishing process has multiple steps. However, is surfacing that the publishing process has multiple steps going to solve the above issue? I don't think so. Since users in that context are not interested yet to go into the publishing path, they are unlikely to explore that way to check if they find functionality that they don't consider connected to it, being it ""preview"" or ""print"".
+",1504603185,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","You may consider my feedback withdrawn. I didn't make the connection with the operating system conventions. I have indeed used many applications that use ellipsis in context menus or top menus for items to indicate they won't be performed immediately but will require an additional interaction first (e.g. new dialog, or next panel if already in a dialog).
+
+Before I realised this connection, my main concern was that adding ellipsis would not solve the original problem, which is that users may be uncomfortable clicking this button because they may want to do a comparison first or enter an edit summary, and the current appearance of the button suggests it will be immediate. Adding ellipsis does make sense for this and might a good first step toward solving this problem.",1504553449,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","It seems that 
+* An ellipsis is standard in many UI guidelines, including Mac and Windows (as @Tgr wrote). It is an UI standard at least since the 90s and basically the icon for ""a window will open"".
+* The only feedback I remember that was contra ellipsis itself came from @Krinkle (""It doesn't clarify or improve the user experience, it only makes it more mysterious.""). 
+* The  character could be either included via CSS or in the translation messages.  
+* The ""does the save button save immediately?!"" is an actual problem (at least according to German Kurier and feedback on enwiki according to @TTO )
+
+With ellipsis, it would look like 
+
+{F7336409}
+
+@Pginer-WMF – what do you think? And: Who is the one to decide about this?",1504543438,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Yep, I’ve put the word ‘Done’ in my mockups.",1502922724,PHID-USER-2fha2mym5lty6djs2qfl,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","What about ""Complete..."", ""Final review"" or similar term to indicate the button will lead to the publication, but not being a ""Publish"" button?",1502921848,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Related to this, there is an [[ https://de.wikipedia.org/w/index.php?title=Wikipedia:Kurier&oldid=166132048 | article on the German signpost equivalent ""Kurier"" ]], in which as user talk about having trouble finding the save button and difficulties on clicking on ""save"", assuming it might save directly. 
+
+> »Zunächst einmal sucht man vergeblich einen Knopf für die Vorschau.  Wie heißt es doch: „Sei mutig!“ Wir drücken also einfach ohne Vorschau auf „Änderungen speichern“ «
+
+> Roughly translated: »We search unsuccessfully of the ""preview"" Button … They say ""Be brave"" and we press without preview on ""Save Changes""«",1496766716,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","@Frigory, @Jan_Dittrich: There is a task for this, where all this stuff should probably go, please see T155732",1495620185,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Hi @Frigory, Hi @Dvorapa,
+
+I like these ideas! I suppose they should have their own ticket. The current ticket was just meant to make the button actions clearer. Your suggestion extends the scope a lot. 
+Can you copy it in a separate tasks and mention this one (T44138)? Thus they would be kept connected and allows each one to focus on the button, two column view or both. 
+If you need help doing it, please write me or tell here. ",1495617839,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","So I could imagine something like this.
+
+- Possibility to have frames in the same dropdown, and an additional option for separate scrollbars: {F8119433}
+- A dropdown in the top right-hand corner of each frame to choose its content: {F8119439}
+- The splitted view: {F8119442} (the bar at the middle can be moved)
+- In the content selection, a ‘Switch panels’ option (I don’t know if the correct word should be ‘frame’ or ‘panel’), and the content of the other panel is grayed; also, a ‘Refresh’ button for the preview: {F8119451}
+
+Of course there should be other icons (‘Refresh’ should be an icon).
+
+This way the toolbar is even shorter than before, because ‘Done’ is shorter than ‘Publish changes’ — :).",1495137268,PHID-USER-2fha2mym5lty6djs2qfl,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","No, if I add just a button with ""Preview"" and dropdown arrow, the symbol button is moved to the second line. The problem of a space in a toolbar or why text labels should be avoided was discussed in detail in T116417 or T153306 or above I guess.",1494958136,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","No, if I add just a button with ""Preview"" and dropdown arrow, the symbol button is moved to the second line. The problem of why text labels should be avoided due was discussed in detail in T116417 or T153306 or above I guess.",1494958069,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","- Separate scrollbars could be a preference.
+- Indeed separate toolbars and dialogs are probably a bad idea.
+- I don’t understand why the Preview dropdown wouldn’t be convenient? You don’t have enough space for it?",1494957310,PHID-USER-2fha2mym5lty6djs2qfl,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","@Frigory I'm not a dev, but I like your proposals (I've already suggested some of them in a different task). Just be aware of those people with more narrow screens (like me - 1280x768), where those features like separate scrollbars, separate toolbars/dialogs and text ""Preview"" as a dropdown label are not very convenient.",1494956623,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Hello,
+
+I’m 21, and I have a bit of experience and interest in web ergonomics. I’ve contributed to the design of a few websites (notably [[http://www.france-ioi.org/|this one]], which was really worse before). I’d like to share my opinion on this task as a Wikimedia contributor. I hope I’m not too late.
+
+I’m not sure all my ideas are appropriate here but let’s spread. I’ve realized screenshots on a random article with the DOM manually modified.
+
+For the preview, I’m dreaming about something like this:
+{F8094031}
+
+I.e. two (possibly resizable) frames, one containing the code and the other one for preview or reviewing changes.
+On my desktop computer, I have two monitors with a resolution of 1920×1080. With this configuration, I could extend my browser window on the two monitors, and have the code on the first one, the preview on the second one.
+
+The initial setup would be:
+{F8094055}
+
+Then you would click on ‘Preview’ in the dropdown:
+{F8094059}
+
+It would make the preview appear on the right, half width, just like in the first screenshot but a bit larger, till the bottom:
+{F8094074}
+
+You could have full preview by sliding:
+{F8094102}
+
+You could reload the preview by clicking on the button ‘Preview’. To get the dropdown, you should click on the arrow. If you select ‘Review changes’, then the button’s label would change to ‘Review changes’.
+
+Then for writing the summary, the popup annoys me because it takes more than 1 second to appear. I contribute mainly for minor edits (orthotypo, article structure, etc.) and I sometimes do a bunch of them so I’d like efficient tools.
+I would imagine something similar to the Find & Replace panel when you click on ‘Done’:
+{F8094203}
+(I would also prefer it for template editing because the current dialog lags…)
+
+Other ideas:
+
+- Two different scrollbars: {F8094424}
+- With these separate scrollbars, a button to show the section containing the cursor in the preview, and another for the opposite (would be very useful when I’m reviewing long articles). This button could be on the vertical splitting bar.
+- For monitors having different sizes: vertically resizable frames (or two different windows?): {F8094520}
+- In the ‘Preview’/‘Review changes’ dropdown, a second subsection with 3 choices: Hidden/Splitted/Full to set the frames’ width automatically (or another button which would toggle between these 3 choices when clicked): {F8094595} I’m also suggesting new labels there. ‘Reviewing the changes’ is actually like viewing a preview of the changes.
+- Maybe having separate toolbars/dialogs in the two frames (e.g. Find & Replace with the wikitext, Publish with the preview)…
+
+Note that, currently, I’m often using two different windows for editing: the first with the wikitext editor and the second with the published article (to explore it and make the fixes at the same time; but it is quite a pity not to view the changes I’m realizing).
+
+I’m not sure I’m the ‘common’ editor but to me it would really be simpler to improve the quality of articles with such an interface, and newbies might appreciate it too.
+
+What do you think about all this? I can give more details if you feel there’s a gap somewhere.",1494907566,PHID-USER-2fha2mym5lty6djs2qfl,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",@Liuxinyu970226 That should be possible with CSS or HTML/CSS without big issues if requested and agreed upon.,1492070083,PHID-USER-caadsxn4xg5gmxrpn6kz,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3171667, @Tgr wrote:
+>>>! In T44138#3171527, @Elitre wrote:
+>> Do we know if there's an equivalent for the ellipsis for every language we support?
+> 
+> Looking at the translations for the [[https://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki%3AEllipsis|ellipsis]] and some messages containing it ([[https://translatewiki.net/w/i.php?title=Special%3ATranslations&message=Watching&namespace=8|1]], [[https://translatewiki.net/w/i.php?title=Special%3ATranslations&message=Moredotdotdot&namespace=8|2]]) it would seem so.
+
+Would it be possible to migrate all ellipsis of MediaWiki core and extensions in all languages to use ""…"" (by default, i.e. if we don't provide translations), which can help extract a lot?",1492008872,PHID-USER-chrmcih5qjpx5buo7vx6,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",On desktop it's very widely used. See e.g. [[https://msdn.microsoft.com/en-us/library/windows/desktop/bb226792(v=vs.85).aspx|Microsoft]] and [[https://developer.apple.com/library/content/documentation/UserExperience/Conceptual/OSXHIGuidelines/TerminologyWording.html#//apple_ref/doc/uid/20000957-CH15-SW3|Apple]] button design guidelines.,1492006934,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">I'm not sure the standard is used in this way. It is used in dropdown menus, but I don't think it is common in push buttons. I certainly don't recall seeing it in web ""call to action-style"" buttons, ever.
+
+Yes, it is not very widely used on buttons. Checking some applications (Libreoffice and Ubuntu System  Settings), I found that: 
+* Few of the buttons I checked open new windows/popups anyway (makes sense, I assume, a button usually triggers an action)
+* For the buttons which open a new window, several had ""…""  (In Setting: ""Network""/""use as hotspot…"" ; ""Language Support""/""install / remove Languages…""; ""Security and Privacy""/ ""Files & Applications""/ ""Clear Usage Data…"")
+
+So, not //widely// used, but used, if it opens new windows. 
+
+ I think it would be an improvement.",1491926565,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","
+>>! In T44138#3162853, @Jan_Dittrich wrote:
+>> Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+> 
+> I think this would make sense – it is an established UI standard and can be found in many desktop applications. 
+> I would love to see an improved wording on the button itself, but util then, I’d go with …
+
+I'm not sure the standard is used in this way. It is used in dropdown menus, but I don't think it is common in push buttons. I certainly don't recall seeing it in web ""call to action-style"" buttons, ever.
+
+>>! In T44138#2087472, @Tgr wrote:
+> The whole save/preview/edit summary interface feels clunky and getting the way. I don't have a constructive suggestion, it's a rather straightforward way of handling saving in a WYSIWYG editor - but it does not feel right, and I hear others complaining about it as well.
+
+I think a large part of the weird feeling is having the button at the top of the screen. ""Submit"" buttons are typically at the bottom of the page, below the form they complete, to go with the reading flow (see this very interface as an example).",1491925559,PHID-USER-uqnvjf4m5wpzmkaddswb,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","
+>>! In T44138#3162853, @Jan_Dittrich wrote:
+>> Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+> 
+> I think this would make sense – it is an established UI standard and can be found in many desktop applications. 
+> I would love to see an improved wording on the button itself, but util then, I’d go with …
+
+I'm not sure the standard is used in this way. It is used in dropdown menus, but I don't think it is common in push buttons. I certainly don't recall seeing it in web ""call to action-style"" buttons, ever.",1491925344,PHID-USER-uqnvjf4m5wpzmkaddswb,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",">>! In T44138#3171527, @Elitre wrote:
+> Do we know if there's an equivalent for the ellipsis for every language we support?
+
+Looking at the translations for the [[https://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki%3AEllipsis|ellipsis]] and some messages containing it ([[https://translatewiki.net/w/i.php?title=Special%3ATranslations&message=Watching&namespace=8|1]], [[https://translatewiki.net/w/i.php?title=Special%3ATranslations&message=Moredotdotdot&namespace=8|2]]) it would seem so.
+",1491923160,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","@Elitre: To better understand the concern – is this about the problem that users may see a rectangle because their fonts don't support ""…"" or about the users not understanding what ""…"" means in that context?",1491923012,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",Do we know if there's an equivalent for the ellipsis for every language we support?,1491921951,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","> Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+
+I think this would make sense – it is an established UI standard and can be found in many desktop applications. 
+I would love to see an improved wording on the button itself, but util then, I’d go with …
+
+Would look like: 
+{F7336409}",1491557467,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","> Roan suggested perhaps changing ""Save page"" to read ""Save page..."", which would give the user a clue that it's going to be a process, not an immediate action.
+
+I think this would make sense – it is an established UI standard and can be found in many desktop applications. 
+
+Would look like: 
+{F7336409}",1491557372,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",,1491557269,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",,1491557250,PHID-USER-3qggseejscb6dtiy4uyx,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","A very typical wording would be ""Review and save"" (or ""Review and publish""). It shouldn't be merely ""Save"" or ""Publish"", since the page is not immediately saved when pressing it.",1491301428,PHID-USER-uqnvjf4m5wpzmkaddswb,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","""Ready to save""?",1488280705,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Maybe there should be something like ""Proceed to save"" instead...",1487742745,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","I like the save process for the most part.  I agree this (initial label that opens the dialog) could potentially be changed, but in practice it's not really a problem as is.",1458845746,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","The whole save/preview/edit summary interface feels clunky and getting the way. I don't have a constructive suggestion, it's a rather straightforward way of handling saving in a WYSIWYG editor - but it does not feel right, and I hear others complaining about it as well.",1457067955,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","**swalling** wrote:
+
+This is being discussed on enwiki as well, at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VE_.22save.22_vs_.22finish_edit.22_button",1373412857,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","There have been a lot of complaints about this on the enwiki feedback page. One especially interesting point was raised by the ever-wise John Broughton:
+
+> [""Save page""] is the same label as on the button, in the old editing interface, that completed the edit session. Lots of effort has been made, over the years, to encourage editors to write an edit summary before they click ""Save page"", and now VE is designed exactly the opposite. The button ought to be labeled ""Finish edit"" or ""Continue"" or ""Final steps"" or just about anything other than ""Save page"".
+> The current problem is even worse than just one poorly labeled button. In VE, after clicking ""Save page"", a dialog box appears that also has a ""Save page"" button. So now an editor has to understand that the two ""Save page"" buttons do not do the same thing. And documentation (when it's written) is going to have to clarify which ""Save page"" button is being referred to - unless the label on the first occurrence of ""Save page"" is changed, as it should be.
+
+The button label on enwiki was modified to ""Finish edit"" per [[MediaWiki:Visualeditor-toolbar-savedialog]].",1433810308,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","There have been a lot of complaints about this on the enwiki feedback page. One especially interesting point was raised by the ever-wise John Broughton:
+
+> [""Save page""] is the same label as on the button, in the old editing interface, that completed the edit session. Lots of effort has been made, over the years, to encourage editors to write an edit summary before they click ""Save page"", and now VE is designed exactly the opposite. The button ought to be labeled ""Finish edit"" or ""Continue"" or ""Final steps"" or just about anything other than ""Save page"".
+
+> The current problem is even worse than just one poorly labeled button. In VE, after clicking ""Save page"", a dialog box appears that also has a ""Save page"" button. So now an editor has to understand that the two ""Save page"" buttons do not do the same thing. And documentation (when it's written) is going to have to clarify which ""Save page"" button is being referred to - unless the label on the first occurrence of ""Save page"" is changed, as it should be.
+
+The button label on enwiki was modified to ""Finish edit"" per [[MediaWiki:Visualeditor-toolbar-savedialog]].",1433810295,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","There have been a lot of complaints about this on the enwiki feedback page. One especially interesting point was raised by the ever-wise John Broughton:
+
+---
+[""Save page""] is the same label as on the button, in the old editing interface, that completed the edit session. Lots of effort has been made, over the years, to encourage editors to write an edit summary before they click ""Save page"", and now VE is designed exactly the opposite. The button ought to be labeled ""Finish edit"" or ""Continue"" or ""Final steps"" or just about anything other than ""Save page"".
+
+The current problem is even worse than just one poorly labeled button. In VE, after clicking ""Save page"", a dialog box appears that also has a ""Save page"" button. So now an editor has to understand that the two ""Save page"" buttons do not do the same thing. And documentation (when it's written) is going to have to clarify which ""Save page"" button is being referred to - unless the label on the first occurrence of ""Save page"" is changed, as it should be.
+---
+
+The button label on enwiki was modified to ""Finish edit"" per [[MediaWiki:Visualeditor-toolbar-savedialog]].",1373365011,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","I agree the toolbar button needs improvement, but imho changing the label from ""Save page"" to ""Save page..."" is not an improvement.
+
+It doesn't clarify or improve the user experience, it only makes it more mysterious.
+
+I'd prefer we look for another solution, but I think the current situation is better than having ""..."" tacked on to the label.",1370637776,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page","Setting milestone to 2013-06-27 since it is marked as blocker for ""Beta"" (2013-07). It may be moved to an earlier milestone as we see fit. But no later than 06-27. Setting it since I use milestone to sort ""My bugs"".",1370298498,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: Toolbar ""Save page"" button is confusing as it merely opens the dialog to save the page",Filing without prejudice as to whether we should implement.,1360206161,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-abb2jsunmv7mixlbbgye,task_subcomment,NA
+"VisualEditor: ""Watch this"" checkbox in Save dialog should use same logic as core EditPage","When using VisualEditor currently when creating a page, the ""Save page"" dialog box has two checkboxes below the edit summary input: ""This is a minor edit"" and ""Watch this page"".
+
+The ""Watch this page"" checkbox is not auto-checked, even though it is (for my account) via the non-VisualEditor editor. There's a user preference (""Add pages I create and files I upload to my watchlist"") that controls whether this checkbox is checked by default when creating a page. VisualEditor currently ignores the value of this user preference. It should respect it.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1352957160,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-u4tbayn5u7dwwaa4yhrw,task_description,resolved
+"VisualEditor: ""Watch this"" checkbox in Save dialog should use same logic as core EditPage",Change-Id: Ic3daf32505a745b3cccd0663a03bbf7f3885be84,1354773511,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u4tbayn5u7dwwaa4yhrw,task_subcomment,NA
+"VisualEditor: ""Watch this"" checkbox in Save dialog should use same logic as core EditPage","If
+- option ""Watch pages I edit (watchdefault)
+- option ""Watch pages I create (watchcreations)"" (and this is a page creation)
+- the page is already watched by the user for whatever reason",1354773101,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u4tbayn5u7dwwaa4yhrw,task_subcomment,NA
+VisualEditor: Merging behaviour of lists should be looked at,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=66452",1352935080,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-53f6o63dslfan6juoyu2,task_description,open
+VisualEditor: Merging behaviour of lists should be looked at,I'm assuming that this is a high level tracking purpose ticket.,1362183560,PHID-USER-s7sn3zjthnxvep34c5ho,True,PHID-TASK-53f6o63dslfan6juoyu2,task_subcomment,NA
+VisualEditor: Merging behaviour of lists should be looked at,"**orbit** wrote:
+
+Any details?",1362181189,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-53f6o63dslfan6juoyu2,task_subcomment,NA
+"VisualEditor: When editing a non-current revision of a page, alter the ""Save page"" button behaviour","Current behaviour on oldid pages is the same as for current ones - that is, the ""Save page"" button is greyed out and won't activate until the content changes.
+
+However, for oldid pages the content is already ""changed"" compared to the current revision, so it should be active right from the start. Also, ideally it should say ""Restore page"" at first, changing to ""Save page"" when/if the page's contents have been altered.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1352324940,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-y3mmi3dje57c7pi3w742,task_description,resolved
+"VisualEditor: When editing a non-current revision of a page, alter the ""Save page"" button behaviour",Merged into master.,1354737639,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-y3mmi3dje57c7pi3w742,task_subcomment,NA
+"VisualEditor: When editing a non-current revision of a page, alter the ""Save page"" button behaviour",I8b30c2a153911f44643e369b7c6a9b89c0fb2c5b should resolve the rest of this.,1354655326,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-y3mmi3dje57c7pi3w742,task_subcomment,NA
+"VisualEditor: When editing a non-current revision of a page, alter the ""Save page"" button behaviour","Partially resolved in I9e5ce76520e091612afe4fbc0300cff8ca645335
+
+No changes to labels yet.",1352325656,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-y3mmi3dje57c7pi3w742,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"**Author:** `orbit`
+
+**Description:**
+Internet Explorer 10, the most cutting-edge browser on the planet, is displaying the context menu far away from the end of the selection. It looks to be about 300 pixels to the right and 150 pixels down - similar to the size of the inspector. Maybe it's related?
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1350690900,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_description,resolved
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"Change 283443 merged by jenkins-bot:
+Update RangeFix to 0.2.0
+
+[[https://gerrit.wikimedia.org/r/283443]]",1460746418,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"Change 283443 had a related patch set uploaded (by Esanders):
+Update RangeFix to 0.2.0
+
+[[https://gerrit.wikimedia.org/r/283443]]
+",1460643139,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,Fixed in RangeFix: https://github.com/edg2s/rangefix/pull/4,1460642589,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"getClientRects (native function) is messed up in IE10 and below when the zoom level is not 100%, it looks like it's applying the zoom factor twice. It may be able to fix it using screen.deviceXDPI / screen.logicalXDPI to calculate the zoom level - maybe this can be done upstream in RangeFix...",1460638469,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"You would think our code would have changed a lot in the past two years, but this bug is still reproducible. It doesn't happen in IE11 though.",1409962684,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"Dhaval: There was a recent fix to the client test module here:
+https://gerrit.wikimedia.org/r/#/c/45183/ Which was deployed on Tuesday.
+
+This fixed a problem with VisualEditor being enabled in IE despite it being configured to be disabled for all versions of Internet Explorer during this deployment.
+
+However, there is a recent patch to enable VisualEditor in IE9 and above.
+https://gerrit.wikimedia.org/r/#/c/45233/
+Which should be rolled out in the next VisualEditor deployment.",1359072321,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,I couldn't see the visual editor option at all in IE10. I am using Windows 7 and IE10.0.9200,1359065509,PHID-USER-wi7txqp5ld5ze33dx7am,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"Yes, sorry; Rangy is a library on which VisualEditor depends heavily, and this appears to be a bug with Rangy that we'd want to get fixed upstream rather than hack around. We've got a reasonable relationship with Rangy's author, so this shouldn't be impossible. :-)",1351101004,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"(In reply to comment #2)
+> Rangy bug. To file/fix upstream?
+
+Means https://code.google.com/p/rangy/issues/list ?
+Curious how to isolate if it is an upstream issue?",1351039040,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,Rangy bug. To file/fix upstream?,1350929614,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in,"**orbit** wrote:
+
+This only happens when zoomed in.",1350691603,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-gwjsvonglc5wqb5w3xah,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"Wikitext:
+
+[[汉]]字
+
+Parsoid:
+
+<p data-parsoid=""{&quot;dsr&quot;:[0,6]}""><a rel=""mw:WikiLink"" href=""./汉"" data-parsoid=""{&quot;tsr&quot;:[0,6],&quot;bsp&quot;:[0,6],&quot;a&quot;:{&quot;href&quot;:&quot;./汉&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;汉&quot;},&quot;stx&quot;:&quot;simple&quot;,&quot;tail&quot;:&quot;字&quot;,&quot;dsr&quot;:[0,6]}"">汉字</a></p>
+
+PHP Parser <https://www.mediawiki.org/w/index.php?title=Project:Sandbox&oldid=594926>:
+
+<p><a href=""/w/index.php?title=%E6%B1%89&amp;action=edit&amp;redlink=1"" class=""new"" title=""汉 (page does not exist)"">汉</a>字</p>
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350544680,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_description,resolved
+Linktrail&prefix is wrongly applied to CJK characters,"This seems fixed, but I found bug 54891 when testing it. Not sure whether this should be considered a bug on VisualEditor side or in Parsoid serializer.",1380741319,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"This should be fixed now.  The core patch has been merged for some time.  Liangent, can you retest?",1380739640,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"There's still a patch in that depends on a core patch. It's not testable on zhwiki until the core patch is deployed. I guess that will happen at wmf11, which is (at most) four weeks away from zhwiki. But it may have fixed this.
+
+If someone could test it locally, it's at https://gerrit.wikimedia.org/r/50814 and the core patch is in the latest mediawiki (from git).",1361989473,PHID-USER-nvavrb7ko66hv3xap6sb,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"(In reply to comment #7)
+> We could do so, but it is pretty low priority for us. Note that you can also
+> point the web service to a page in the user namespace like this:
+> 
+> http://parsoid.wmflabs.org/zh/User:Liangent/Test
+
+Now linkprefix is applied incorrectly. Still the same use case: [[中]]cjk[[文]]
+
+Expected: [[中]]cjk[[文]]
+
+Actual: [[中]][[文|cjk文]]",1361878825,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"We could do so, but it is pretty low priority for us. Note that you can also point the web service to a page in the user namespace like this:
+
+http://parsoid.wmflabs.org/zh/User:Liangent/Test",1361840613,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"(In reply to comment #5)
+> We have switched to use per-language link trail (and prefix) regexps now with
+> https://gerrit.wikimedia.org/r/#/c/48589/. Our HTML form defaults to English
+> settings, but testing on a test page from the Chinese Wikipedia has a good
+> chance of working. Can you verify that the test cases above are now fixed?
+
+Can you make that HTML form accept an extra ""language"" option?",1361708371,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"We have switched to use per-language link trail (and prefix) regexps now with https://gerrit.wikimedia.org/r/#/c/48589/. Our HTML form defaults to English settings, but testing on a test page from the Chinese Wikipedia has a good chance of working. Can you verify that the test cases above are now fixed?",1361300873,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"(In reply to comment #3)
+> Liangent, how well does the new regexp work for Chinese?
+
+[[中]]cjk[[文]]
+
+This gets linktrailed which are usually not wanted. I believe there're some real world use cases on zhwiki as we usually don't put a space between Chinese and embedded English words.",1359424006,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"This specific example is working now as we have extended our negative char class to include something very close to the union of the complements of per-language character classes. This is a bit of a departure from default MediaWiki behavior, but might not be noticeable in practice. 
+
+We'd get consistent link trail behavior across languages if this works ok. If it does not, we'd have to revert to traditional per-language regexps.
+
+Liangent, how well does the new regexp work for Chinese?",1359413776,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"[09:19] <liangent> $linkTrail = '/^([a-z]+)(.*)$/sD'; is in MessagesEn.php
+[09:20] <liangent> this shouldn't include CJK characters, right?
+[09:20] <gwicke> I would think so
+[09:20] <liangent> but parsoid includes CJK chars in linktrail..
+[09:21] <gwicke> interesting- I guess we approximate the regexp to something more liberal right now
+[09:22] <gwicke> there is no i18n support yet, so we don't use the localized regexps
+[09:23] <gwicke> we currently have tail:( ![A-Z \t(),.:\n\r-] tc:text_char { return tc } )* 
+[09:24] <gwicke> I think the idea was to be very liberal about tails in the tokenizer, and to convert/validate based on language in token stream transforms
+[09:24] <gwicke> invalid tails can then be converted back to a text token
+[09:25] <gwicke> the A-Z might be a bit fishy in that context though..",1350664104,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+Linktrail&prefix is wrongly applied to CJK characters,"We don't support the localized link trail regexp yet and default to the English one, so in this case the trail is not matched as such.
+
+Currently our focus is to make Parsoid safe for the English Wikipedia first, so that we can release it as a demo in December. After that release the plan is to shift the focus to C++, which will also enable us to call back into PHP. That should allow us to reuse the existing localizations and message systems, so we don't spend too much time reinventing the wheel in a JavaScript prototype.",1350661579,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-3h2cevtlx5g2a6ncai2m,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"See gerrit 21142
+
+The latest Firefox (Iceweasel) version shipped with the latest ""working""[1] Debian is 10.x[2], so unless they install a newer Firefox manually, Debian desktop users can't use VisualEditor in Firefox.
+
+[1] http://en.wikipedia.org/wiki/Debian#Additional_repositories
+[2] http://packages.debian.org/search?keywords=iceweasel
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1350539940,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-zdr6lujpo7t7bcteewl4,task_description,resolved
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"(In reply to comment #7)
+> Looks done in Gerrit change #46668?
+
+Whoops, sorry, yes, we didn't mark this bug as fixed then. Resolved since the 4 February roll-out.",1367002642,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,Looks done in gerrit 46668?,1366999513,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"I assume you have some kind of tests for the different functionalities. Exposing them would allow:
+a) Users to beta test the functionality on the UA of their choice.
+b) Vendors to actually test what fails and needs fixing (eg. Iceweasel maintainers)
+c) It's much more clear what is not working for each browser (or if it just hasn't been tested).",1352066955,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"Abstract layers can be done in another way. For example in your case, keypress is different, so we make our own keypress_ve, and for normal browsers, just use a wrapper function to map keypress_ve to keypress, but for Firefox, filter special keys out before mapping.
+
+So now for a new browser, use a simplest wrapper and ask people to press keys to test it. Once we find its behavior strange, make a special wrapper for that browser.",1350630563,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"I agree that it's difficult.
+
+For example, most of the point of the approach we've taken is to re-use browsers' native capability - this means that we can support IME, spell-checking and other things important to users of our wikis that would be (even more) hugely complex or impossible to implement in VE itself. However, this means that abstracting behaviour would go in completely the wrong direction - for more on this, see our (abandoned) EditableSurface attempt, before we switched over to ContentEditable for the core surface earlier this year.
+
+A simple example of the difficulties is that Firefox triggers a keypress event on special keys that other browsers don't, such as the cursor keys; this means we need to catch these but only on Firefox to avoid hugely unexpected behaviour (such as removing text when you make a selection with the keyboard). This, and dozens of issues like this example, is why we don't have the resources to support browsers further down the chain.",1350586012,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,Iceweasel seems to contain some backports from newer Firefox.,1350582384,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"but it's difficult for people to dig into code and find out the behavior that doesn't meet VE's requirement.
+
+maybe create some abstract layers over browsers?",1350582207,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist,"Though I understand the wish here, I'm afraid we in the core team have got our work cut out for us just supporting the latest, core versions of Firefox, Chrome, Safari and IE.
+
+We've already spent a good deal of time looking at compatibility with older versions of these four, with Opera, and other browsers or forks of these browsers (like Iceweasel, which from our testing is not just a re-badge of Firefox, but works differently in unexpected ways). It's not a case of just adding browses to the whitelist and assuming all will be fine.
+
+Our current browser support policy [0] is still in draft, but given the huge variance we're finding between browsers on their JavaScript models, how they react to key-press events, and similar issues that are key to making VisualEditor work. That's quite apart from the browsers that claim to support key technologies but don't (like Android native browser before 3.0) and those that don't even reach that far (like Opera Mini).
+
+It's very important to us that we don't give people false expectations of the VisualEditor working for them only to break somewhere down the line because their browser can't or won't follow what limited standards there are, or that appear to work only to break wiki content terribly when people save their changes.
+
+We would of course be delighted to accept git pushes that would fix the compatibility issues with Iceweasel and other more minor browsers, though that will be quite a lot of work in some cases. Sorry that we can't give the support you want here.
+
+[0] - https://www.mediawiki.org/wiki/VisualEditor/2012-13_Q1_forward-look#Browser_matrix",1350580222,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zdr6lujpo7t7bcteewl4,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"With longer tables it can be very difficult to identify the columns. It might be nice if table headers stayed in view when scrolling trough a long table.
+
+This could be done with JS, but would need to be compatible with tablesorter of course.
+
+Thinking about 'fixed' position headers once the header moves out of the screen viewport. Can possibly do similar stuff with footers.
+
+--------------------------
+**Version**: 1.21.x
+**Severity**: enhancement
+**See Also**: {T12013}",1349347020,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_description,open
+Implement repeated/fixed/floating/sticky table headers,"Ah, yes it worked ----aaaaaah .. just not:
+
+as explained in
+https://en.wikipedia.org/wiki/Template:Sticky_header
+I copy/pasted: {{sticky header}}
+above the code generating this very long and wide table, but the data from the 150 lines scrolls and reappears above the sticky header : 
+
+ https://en.wikipedia.org/wiki/Template_talk:Sticky_header#sticky_header_template_works_just_about_-_just_makes_the_data_in_the_lines_scroll_under_it_and_reappear_above_the_sticky_header_:)
+",1711634392,PHID-USER-p5mohmucn4hzkcdmumnq,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Change 791014 **abandoned** by D3r1ck01:
+%%%[mediawiki/skins/Vector@master] [WIP] resources: Make sortable wikitable stick underneath sticky title%%%
+Reason:
+%%%%%%
+https://gerrit.wikimedia.org/r/791014",1706274672,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1711668368,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696548392,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696548279,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696506991,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696506917,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,,1696506726,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#9102043, @matmarex wrote:
+> Timeless has a script that makes wide tables horizontally scrollable that might be conflicting.
+
+Correct. This is one of the problems that are hard to tackle. Sticky is relative to the first parent scrollcontext. But the skin offset (for the header) for sticky is relative to the top scroll context. This means that as we don’t really know all the situations where extra scrollers exist, it is hard to have universal CSS rules for timeless and vector 2022. The only reliable way around this, might be with JavaScript looking for scroll contexts, to set a specific class which opts out of the offset. I haven’t fully dived into that yet.",1692433044,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#9102043, @matmarex wrote:
+> Timeless has a script that makes wide tables horizontally scrollable that might be conflicting.
+
+Correct. This is one of the problems that are hard to tackle. Sticky is relative to the first parent scrollcontext. But the skin offset (for the header) for sticky is relative to the top scroll context. This means that as we don’t really know all the situations where extra scrollers exist, it is hard to have universal CSS rules for timeless and vector 2022. The only reliable way around this, might be with JavaScript looking for scroll contexts. I haven’t fully dived into that yet.",1692432972,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#9102043, @matmarex wrote:
+> Timeless has a script that makes wide tables horizontally scrollable that might be conflicting.
+
+Correct. This is one of the problems that are hard to tackle. Sticky is relative to the first parent scrollcontext. But the skin offset (for the header) for sticky is relative to the top scroll context. This means that as we don’t really know all the situations where extra scrollers exist, it is hard to have universal rules. The only reliable way around this, might be with JavaScript looking for scroll contexts. I haven’t fully dived into that yet.",1692432919,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,Timeless has a script that makes wide tables horizontally scrollable that might be conflicting.,1692375586,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#3139713, @TheDJ wrote:
+> I've created a gadget for this:
+> https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets
+> Currently inside the Testing and development section
+> 
+> It should work for all versions of Safari, most recent versions of Chrome (though less optimal), some versions of Firefox (support is a bit sketchy there).
+
+It seems to be.. buggy on #timeless when the table is wider than the article view area... Fine after editing (using VE) as it overflows, but on refresh it's broken again...",1692374274,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,It might be worthwhile to only make headers sticky for tables of a certain size and above.,1679089338,PHID-USER-wfmjbbgdraluvoigu3lo,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,It might be worthwhile to only make headers sticky for tables of a certain size.,1679089325,PHID-USER-wfmjbbgdraluvoigu3lo,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"With the sticky header in Vector2022 and sticky header in a sortable wikitable and a new patch applied, we now get.
+
+{F35130089}",1652270181,PHID-USER-7tsz7e5krfc7ng6ihkjr,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Change 791014 had a related patch set uploaded (by D3r1ck01; author: Derick Alangi):
+%%%[mediawiki/skins/Vector@master] resources: Make sortable wikitable stick underneath sticky title%%%
+https://gerrit.wikimedia.org/r/791014",1652269468,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"With @daniel's patch applied to Vector2010, here's a sample output
+
+{F35130045}
+
+{F35130044}
+
+But on Vector 2022, the sticky header hides the sticky table header.
+
+{F35130048}",1652268761,PHID-USER-7tsz7e5krfc7ng6ihkjr,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Change 791000 had a related patch set uploaded (by Daniel Kinzler; author: Daniel Kinzler):
+%%%[mediawiki/core@master] WIP: add sticky header support.%%%
+https://gerrit.wikimedia.org/r/791000",1652265418,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Change 790697 had a related patch set uploaded (by Daniel Kinzler; author: Daniel Kinzler):
+%%%[mediawiki/core@master] Extract table normalization out of tablesorter%%%
+https://gerrit.wikimedia.org/r/790697",1652192877,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Indeed, sorry: I incorrectly tested this.
+
+Still in Timeless, though.",1649709584,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#7844758, @Pols12 wrote:
+> Note `style=""position:sticky; top:0""` workaround meets an issue with new Vector sticky header (the site header displays over the table header).
+
+That has been addressed in T289817.
+",1649684393,PHID-USER-zrh22rct2jo5hs6nu67r,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Note `style=""position:sticky; top:0""` workaround meets an issue with new Vector sticky header (the site header displays over the table header).",1649682592,PHID-USER-unpoeiyj52rmcfqi5rbw,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,@TheDJ Thanks for implementing a fix for iPhones.,1643589151,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I redid the styles for the large COVID-19 tables and added some additional features like a column of left-sticky row headers. Below are the styles and a few tables.
+* [[https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_data/styles2.css | Template:COVID-19 pandemic data/styles2.css]]
+* [[https://en.wikipedia.org/wiki/Template:2020_monthly_cumulative_COVID-19_death_totals_by_country | Template:2020 monthly cumulative COVID-19 death totals by country]]
+* [[https://en.wikipedia.org/wiki/Template:2021_monthly_cumulative_COVID-19_death_totals_by_country | Template:2021 monthly cumulative COVID-19 death totals by country]]
+* [[https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates_by_country | Template:COVID-19 pandemic death rates by country]]
+
+We found (**[[https://en.wikipedia.org/wiki/Template_talk:COVID-19_pandemic_data#New_styles_feedback|see talk]]**) that the new styles work on all tested browsers except iPhone (WebKit) browsers. The ""position: sticky;"" style works on iPhone if not on the Wikipedia site, but not on the Wikipedia site, so the mobile site's styles might be interfering. Unfortunately, I don't have any Apple products to test with. The same may be true with help from **[[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Sticky_table_headers_not_working_on_iPhone | Wikipedia:Village pump (technical)#Sticky table headers not working on iPhone]]**. Any iPhone help appreciated.
+
+With some adjustments and fine tuning, these styles could be moved to a ""Big table"" template so the styles can be included above the table's div wrapper, similar to how ""**{{Import-blanktable}}**"" and ""**{{Static row numbers}}**"" work. The ""big-table"" class would be added to the div that wraps the table.
+
+For tables with two rows of top-sticky column headers, I kept it simple with pure CSS and height/nowrap restrictions. Ideally, JavaScript would instead be used to set ""top"" for the second based on the first's ""height"", which would remove the need for height/nowrap restrictions. I didn't provide any links to tables with two top-sticky rows since the tables I updated didn't need them. Because of the JavaScript potential, it might be better to implement in Wikipedia's core instead of a template.",1643589318,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I redid the styles for the large COVID-19 tables and added some additional features like a column of left-sticky row headers. Below are the styles and a few tables.
+* [[https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_data/styles2.css | Template:COVID-19 pandemic data/styles2.css]]
+* [[https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country | Template:Monthly cumulative COVID-19 death totals by country]]
+* [[https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 | Template:Monthly cumulative COVID-19 death totals by country 2021]]
+* [[https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates_by_country | Template:COVID-19 pandemic death rates by country]]
+
+We found (**[[https://en.wikipedia.org/wiki/Template_talk:COVID-19_pandemic_data#New_styles_feedback|see talk]]**) that the new styles work on all tested browsers except iPhone (WebKit) browsers. The ""position: sticky;"" style works on iPhone if not on the Wikipedia site, but not on the Wikipedia site, so the mobile site's styles might be interfering. Unfortunately, I don't have any Apple products to test with. The same may be true with help from **[[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Sticky_table_headers_not_working_on_iPhone | Wikipedia:Village pump (technical)#Sticky table headers not working on iPhone]]**. Any iPhone help appreciated.
+
+With some adjustments and fine tuning, these styles could be moved to a ""Big table"" template so the styles can be included above the table's div wrapper, similar to how ""**{{Import-blanktable}}**"" and ""**{{Static row numbers}}**"" work. The ""big-table"" class would be added to the div that wraps the table.
+
+For tables with two rows of top-sticky column headers, I kept it simple with pure CSS and height/nowrap restrictions. Ideally, JavaScript would instead be used to set ""top"" for the second based on the first's ""height"", which would remove the need for height/nowrap restrictions. I didn't provide any links to tables with two top-sticky rows since the tables I updated didn't need them. Because of the JavaScript potential, it might be better to implement in Wikipedia's core instead of a template.",1643508964,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"@Jroberson108 
+There must be somewhere you can post this so that others can see it. I am afraid to point to other wikis such as Shoutwiki, etc.. They are often not using the latest version of Wikimedia. What about Toolforge:
+*https://wikitech.wikimedia.org/wiki/Help:Toolforge 
+
+
+",1638490929,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"@Timeshifter
+The page you linked to says ""This page is obsolete. It is being retained for archival purposes."" I'm not really sure where I can set it up.
+
+As for the code, although the majority of the use cases are covered, it's still a work-in-progress in regards to the more complex use cases like only making certain headers sticky versus all.",1638478027,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"@Jroberson108 
+Is there someplace you can set this up so we can see it in action as you make changes? Wikimedia Labs?: 
+*https://www.mediawiki.org/wiki/Wikimedia_Labs 
+
+",1638476190,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Just an update on the issues I mentioned above in regards to the work I did. I figured out a fix for the desktop browser issue, which has been implemented.
+
+The only issue left is on mobile browsers when there are multi-tiered column or row headers. The headers are sticky, but they become stacked when scrolling away. As far as I can tell, JavaScript isn't able to get the row height or column width on mobile browsers so I can assign it to the respective ""top"" and ""left"" values to prevent stacking. I've got a note on this in the JS file. The table may need to render first before they are set? Otherwise, the sticky column and/or row headers appear to work fine in mobile browsers.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox",1638424450,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Just an update on the issues I mentioned above in regards to the work I did. I figured out a fix for the desktop browser issue, which has been implemented.
+
+The only issue left is on mobile browsers when there are multi-tiered column or row headers. The headers are sticky, but they become stacked when scrolling away. As far as I can tell, JavaScript isn't able to get the row height or column width on mobile devices so I can assign it to the respective ""top"" and ""left"" values to prevent stacking. I've got a note on this in the JS file. The table may need to render first before they are set? Otherwise, the sticky column and/or row headers appear to work fine in mobile browsers.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox",1638424300,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#7539855, @Timeshifter wrote:
+> There are 4 scrolling tables that have long had sticky headers in this section:
+> *https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics 
+> 
+> Single header rows:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_vaccination_data 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 
+> 
+> Taller header row:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates 
+> 
+> Template with 2 header rows: 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country 
+
+I tested those tables. For desktop browsers (Windows 10: Chrome & Firefox), the sticky column headers work, but the row headers (country cells) weren't sticky. For mobile browsers (Android: Chrome & Firefox), there were no sticky headers. Mobile browsers are where it is needed the most because of the small screen size.",1638379200,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#7539855, @Timeshifter wrote:
+> There are 4 scrolling tables that have long had sticky headers in this section:
+> *https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics 
+> 
+> Single header rows:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_vaccination_data 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 
+> 
+> Taller header row:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates 
+> 
+> Template with 2 header rows: 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country 
+
+I tested those tables. For desktop browsers (Windows 10: Chrome & Firefox), the sticky column headers work, but the row headers (each country) weren't sticky. For mobile browsers (Android: Chrome & Firefox), there were no sticky headers. Mobile browsers are where it is needed the most because of the small screen size.",1638379157,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#7539855, @Timeshifter wrote:
+> There are 4 scrolling tables that have long had sticky headers in this section:
+> *https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics 
+> 
+> Single header rows:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_vaccination_data 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 
+> 
+> Taller header row:
+> *https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates 
+> 
+> Template with 2 header rows: 
+> *https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country 
+
+I tested those tables. For desktop browsers (Windows 10: Chrome & Firefox), the sticky column headers work, but the row headers weren't sticky. For mobile browsers (Android: Chrome & Firefox), there were no sticky headers. Mobile browsers are where it is needed the most because of the small screen size.",1638376988,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"There are 4 scrolling tables that have long had sticky headers in this section:
+*https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics 
+
+Single header rows:
+*https://en.wikipedia.org/wiki/Template:COVID-19_vaccination_data 
+*https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country_2021 
+
+Taller header row:
+*https://en.wikipedia.org/wiki/Template:COVID-19_pandemic_death_rates 
+
+Template with 2 header rows: 
+*https://en.wikipedia.org/wiki/Template:Monthly_cumulative_COVID-19_death_totals_by_country ",1638344262,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"There are 3 scrolling tables that have long had sticky headers in this section:
+https://en.wikipedia.org/wiki/COVID-19_pandemic_by_country_and_territory#Statistics ",1638343478,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I'm not sure if this helps any, but I've done some work on making table headers sticky while scrolling both on desktop and mobile browsers since Dec 4, 2020. This work is on my sandbox since I'm not familiar with the Wikipedia project/task workflow. Since this is my sandbox, the CSS/JS won't be included for you unless you are logged in as me. The only workaround I can think of is for you to reproduce the CSS and JS files in your sandbox.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox
+https://en.wikipedia.org/wiki/User:Jroberson108/common.css
+https://en.wikipedia.org/wiki/User:Jroberson108/common.js
+
+This code works fine for the majority of the tables, which have one row of column headers and/or one column of row headers, and works with ""sortable"".
+
+For multi-tiered headers, there are some issues where the second-tier header stacks above its first-tier header instead of sticking to its side. For desktop browsers, it works fine unless the first-tier row header is grouped and its second-tier isn't grouped (no column header issues). For mobile browsers, everything stacks. (e.g. https://en.wikipedia.org/wiki/User:Jroberson108/sandbox#Dual-tier_columns_and_rows)",1638329896,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I'm not sure if this helps any, but I've done some work on making table headers sticky while scrolling both on desktop and mobile browsers since Dec 4, 2020. This work is on my sandbox since I'm not familiar with the Wikipedia project/task workflow. Since this is my sandbox, the CSS/JS won't be included for you unless you are logged in as me. The only workaround I can think of is for you to reproduce the CSS and JS files in your sandbox.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox
+https://en.wikipedia.org/wiki/User:Jroberson108/common.css
+https://en.wikipedia.org/wiki/User:Jroberson108/common.js
+
+This code works fine for the majority of the tables, which have one row of column headers and/or one column of row headers, and works with ""sortable"". In the cases where there is a second row of column headers and/or a second column of row headers, the second header stacks against its first-tier counterpart.
+
+For multi-tiered headers, a stacking issue can occur in certain circumstances when the first-tier row header is grouped causing an overlap of the second row header, as indicated in the CSS file comments. (e.g. https://en.wikipedia.org/wiki/User:Jroberson108/sandbox#Dual-tier_columns_and_rows)",1638327549,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I'm not sure if this helps any, but I've done some work on making table headers sticky while scrolling both on desktop and mobile browsers since Dec 4, 2020. This work is on my sandbox since I'm not familiar with the Wikipedia project/task workflow. Since this is my sandbox, the CSS/JS won't be included for you unless you are logged in as me. The only workaround I can think of is for you to reproduce the CSS and JS files in your sandbox.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox
+https://en.wikipedia.org/wiki/User:Jroberson108/common.css
+https://en.wikipedia.org/wiki/User:Jroberson108/common.js
+
+This code works fine for the majority of the tables, which have one row of column headers and/or one column of row headers, and works with ""sortable"". In the cases where there is a second row of column headers and/or a second column of row headers, the second header stacks against its first-tier counterpart.
+
+For multi-tiered headers, a stacking issue can occur in certain circumstances when the first-tier row header is grouped causing an overlap of the second row header, as indicated in the CSS file comments. (e.g. https://en.wikipedia.org/wiki/User:Jroberson108/sandbox#Dual-tier_columns_and_rows)
+- Stacked multi-tier row headers wider than the first one are visible.",1638327223,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I'm not sure if this helps any, but I've done some work on making table headers sticky while scrolling both on desktop and mobile browsers since Dec 4, 2020. This work is on my sandbox since I'm not familiar with the Wikipedia project/task workflow. Since this is my sandbox, the CSS/JS won't be included for you unless you are logged in as me. The only workaround I can think of is for you to reproduce the CSS and JS files in your sandbox.
+
+https://en.wikipedia.org/wiki/User:Jroberson108/sandbox
+https://en.wikipedia.org/wiki/User:Jroberson108/common.css
+https://en.wikipedia.org/wiki/User:Jroberson108/common.js
+
+This code works fine for the majority of the tables, which have one row of column headers and/or one column of row headers, and works with ""sortable"". In the cases where there is a second row of column headers and/or a second column of row headers, the second header stacks against its first-tier counterpart.
+
+For multi-tiered headers, a stacking issue can occur in certain circumstances when the first-tier header is grouped causing an overlap, as indicated in the CSS file comments. (e.g. https://en.wikipedia.org/wiki/User:Jroberson108/sandbox#Dual-tier_columns_and_rows)
+- Stacked multi-tier column headers taller than the top one are visible. Use the ""nowrap"" class for equal heights.
+- Stacked multi-tier row headers wider than the top one are visible.",1638324710,PHID-USER-srxdqhmx4zl3u4celq4u,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,I'm going to be deploying an update to my gadget on en.wp soon. This includes the fix for the collapsed borders + sticky. Unfortunately it seems that in Safari 14 there are now several problems with sticky table elements. The most noticeable is that the space that a table caption takes up is added above the sticky element. All these problems should be fixed in Safari 15 pretty soon however (according to the upstream tickets),1630505636,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,">>! In T42763#6654192, @XanonymusX wrote:
+> I just noticed that apparently the tables with sticky headers I created on dewiki don’t work anymore if I activate the new Vector skin! How can the skin interfere with this effect? Noticed this on Chrome.
+
+>>! In T42763#6654237, @XanonymusX wrote:
+> My question was whether there was a known interference of the new vector with position:fixed in table headers, not about a specific case.
+> 
+> Anyway, random example (taken from the Community Wishlist): [[ https://de.wikipedia.org/wiki/Red_Hot_Chili_Peppers/Diskografie | most tables here ]] have sticky headers. Works fine in old Vector and in all up-to-date browsers. With new vector position:fixed apparently is completely ignored (at least in Chrome).
+
+It was related to scrollable containers used for the skin's layout, similar to what @TheDJ mentioned above. This also caused problems with VisualEditor and other tools (e.g. T270146, T264679), and in the end the skin was changed to avoid breaking things. Looks like the fixed headers also work again now.",1622130356,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Update: [[ https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c60 | Chrome 91 will ship ]] with working position:fixed for <thead> and <tr> elements (I tested and it works), so this is much closer to reality now and all main browsers will support it soon.
+
+That means it is only details on 'when'/'how' to enable this functionality that remain to be determined.
+
+Note that position fixed for thead gets disabled inside scroll containers (like used by us on mobile), this is a technical limitation of the CSS specification: https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c59",1622129551,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Update: [[ https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c60 | Chrome 91 will ship ]] with working position:fixed for <thead> and <tr> elements, so this is much closer to reality now and all main browsers will support it soon.
+
+That means it is only details on 'when'/'how' to enable this functionality that remain to be determined.
+
+Note that position fixed for thead gets disabled inside scroll containers (like used by us on mobile), this is a technical limitation of the CSS specification: https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c59",1622129399,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Update: [[ https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c60 | Chrome 91 will ship ]] with working position:fixed for <thead> and <tr> elements, so this is much closer to reality now and all main browsers will support it soon.
+
+That means it is only details on 'when'/'how' to enable this functionality that remain to be determined.
+
+Note that position fixed for thead gets disabled inside scroll containers (like used by us on mobile), this is a technical limitation of the specification: https://bugs.chromium.org/p/chromium/issues/detail?id=702927#c59",1622129340,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"My question was whether there was a known interference of the new vector with position:fixed in table headers, not about a specific case.
+
+Anyway, random example (taken from the Community Wishlist): [[ https://de.wikipedia.org/wiki/Red_Hot_Chili_Peppers/Diskografie | most tables here ]] have sticky headers. Works fine in old Vector and in all up-to-date browsers. With new vector position:fixed apparently is completely ignored (at least in Chrome).",1606661794,PHID-USER-zrh22rct2jo5hs6nu67r,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,@XanonymusX: Please always provide links to test cases so other people could try to reproduce without having to somehow search for pages first. Thanks.,1606660747,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,I just noticed that apparently the tables with sticky headers I created on dewiki don’t work anymore if I activate the new Vector skin! How can the skin interfere with this effect? Noticed this on Chrome.,1606657775,PHID-USER-zrh22rct2jo5hs6nu67r,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021/Reading/Enable_sticky_table_headers,1606654513,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Anyone interested feel free to work on a patch, please: https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker - thanks in advance!",1605562875,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"FYI, this task recently came up at [[ https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)/Archive_172#Always_Show_Column_Headers_in_Tables | the Village Pump ]], showing continuing interest.",1605562175,PHID-USER-tl3o6dlackm57f3qrt4b,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,This is possible in pure CSS these days with minimal dodginess; see for example the `.floatable-header` CSS at https://yugipedia.com/wiki/MediaWiki:Common.css and an example usage at https://yugipedia.com/wiki/Historic_Forbidden/Limited_Chart.,1596487144,PHID-USER-2wibf62nhsbcjs6773je,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Today I found the class //mw-sticky-header// being automatically applied to some tables on enwiki. As far as I can see, it only works in Safari and only on desktop. Does somebody know more about this?
+
+EDIT: Oh, I could have just read the thread again, my bad. So it's [[ https://en.wikipedia.org/wiki/MediaWiki:Gadget-StickyTableHeaders.js | TheDJ's gadget from 2017]]. But how come i only see this now? I have not changed my preferences recently.",1596403028,PHID-USER-zrh22rct2jo5hs6nu67r,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Today I found the class //mw-sticky-header// being automatically applied to some tables on enwiki. As far as I can see, it only works in Safari and only on desktop. Does somebody know more about this?
+
+EDIT: Oh, I could have just read the thread again, my bad. So it's [[ https://en.wikipedia.org/wiki/MediaWiki:Gadget-StickyTableHeaders.js | TheDJ]]'s gadget from 2017. But how come i only see this now? I have not changed my preferences recently.",1596403009,PHID-USER-zrh22rct2jo5hs6nu67r,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Today I found the class //mw-sticky-header// being automatically applied to some tables on enwiki. As far as I can see, it only works in Safari and only on desktop. Does somebody know more about this?",1596402546,PHID-USER-zrh22rct2jo5hs6nu67r,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"@Sdkb: No updates, otherwise they would be in this task. :) Do you [plan to work on fixing this task](https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities), as you [increased the priority](https://www.mediawiki.org/wiki/Bug_management/Phabricator_etiquette) of this task? If so, please set yourself as assignee - thanks!",1587545384,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Any updates on this? It would be hugely useful for pages like https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources/Perennial_sources#Sources, and it's come up again at https://en.wikipedia.org/wiki/Help_talk:Table#Sticky_table_headers?.",1587515503,PHID-USER-tl3o6dlackm57f3qrt4b,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,Any updates on this? It would be hugely useful for pages like https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources/Perennial_sources#Sources.,1587515413,PHID-USER-tl3o6dlackm57f3qrt4b,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I've created a gadget for this:
+https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets
+Currently inside the Testing and development section
+
+It should work for all versions of Safari, most recent versions of Chrome (though less optimal), some versions of Firefox (support is a bit sketchy there).
+
+https://developer.microsoft.com/en-us/microsoft-edge/platform/status/positionsticky/
+https://bugzilla.mozilla.org/show_bug.cgi?id=886646
+https://bugzilla.mozilla.org/show_bug.cgi?id=975644
+https://bugs.chromium.org/p/chromium/issues/detail?id=231752
+https://developers.google.com/web/updates/2016/12/position-sticky
+https://bugs.chromium.org/p/chromium/issues/detail?id=702927",1490783329,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"I've created a gadget for this:
+https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets
+Currently inside the Testing and development section
+
+It should work for all versions of Safari, most recent versions of Chrome (though less optimal), some versions of Firefox (support is a bit sketchy there).
+
+https://developer.microsoft.com/en-us/microsoft-edge/platform/status/positionsticky/
+https://bugzilla.mozilla.org/show_bug.cgi?id=886646
+https://bugs.chromium.org/p/chromium/issues/detail?id=231752
+https://developers.google.com/web/updates/2016/12/position-sticky
+https://bugs.chromium.org/p/chromium/issues/detail?id=702927",1490782070,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,*** Bug 53358 has been marked as a duplicate of this bug. ***,1377602419,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"http://datatables.net/extras/fixedheader/
+
+and 
+
+http://css-tricks.com/persistent-headers/
+
+are some of the nicest implementations i have seen so far. both require cloning the headers, which is currently not possible with sortable tables.
+
+I think that if we would want to do this, we should split of the thead and tableheader normalization of tablesorter into it's own module and reuse that for fixed headers.",1373152890,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,Moving to the right component. You need javascript to dynamically switch the styling of a table header like this.,1373123387,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,"Moving to the Parser component. I hope this is the right place.
+
+PS: part of https://www.mediawiki.org/wiki/Bug_management/Triage/20130307",1362674199,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+Implement repeated/fixed/floating/sticky table headers,Adding 'floating' and 'fixed' to summary to clarify how we'd probably want to implement such things by dynamically switching them to position:fixed rather than actually repeating.,1349374141,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-lkomsrc6uy5sho4rnfh7,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**Author:** `winne2i`
+
+**Description:**
+Column of fixed row numbers. 
+
+In tables where we enumerate something we usually add a first column with row numbers. Of course we set it as unsortable (class=unsortable) – BUT it doesn't prevent the column from being sorted while we sort another column. Then the row numbers get all messed up.
+
+There should be an additional parameter (class or something) for setting which column should not be sorted in any circumstance.
+(I cannot think of anything more in that column than row numbers…)
+
+Template:Static_row_numbers creates tables with fixed row numbers:
+https://en.wikipedia.org/wiki/Template:Static_row_numbers 
+https://en.wikipedia.org/wiki/Special:WhatLinksHere/Template:Static_row_numbers 
+
+A deprecated method is used for tables in this category: 
+*https://en.wikipedia.org/wiki/Category:Articles_with_tables_with_fixed_row_numbers
+Some of the tables in that category have row number columns that do not sort under any circumstance. Some only sort if that particular row number column header is clicked. For example; if ascending or descending ranking is desired. But none of the row number columns sort when other column heads are clicked.
+
+Wikitext of fixed row numbers in a table on Polish Wikipedia below, and in use here: 
+https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne_dyskusja/Archiwum/2012-grudzie%C5%84#Sortowanie_tabeli 
+The row number column does not sort under any circumstance.
+
+```
+{| class=""wikitable sortable"" style=""text-align:center;"" align=""left""
+!class=""unsortable""|№
+!color
+!name
+!city
+|-
+|1||white||John||New York
+|-
+|2||green||Alice||Warsaw
+|-
+|3||black||Mark||Rennes
+|}
+```
+
+Th attached chart images show what happens if the row number column is not fixed. For example; if the above table wikitext is used on English Wikipedia.
+**Attached**: {F9709}
+
+The best patch would add a column of fixed row numbers to any chart. Without having to manually enter the row numbers. Or reenter the numbers after every addition of more rows in the middle of the table. ",1348933560,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_description,open
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","> Can you create a user sandbox page on that wiki with some simple example tables?
+
+Sure, see [[https://pl.wiktionary.org/wiki/Wikis%C5%82ownikarz:Peter_Bowman/autonumber|wikt:pl:Wikisłownikarz:Peter Bowman/autonumber]] ([[https://pl.wiktionary.org/w/index.php?title=Wikis%C5%82ownikarz:Peter_Bowman/autonumber&oldid=7809320|permalink]]). It looks like desktop Minerva has a different set of rules which I have not considered yet.",1635506371,PHID-USER-zzlez5ppzytn7ghyo6sc,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#7461512, @PeterBowman wrote:
+>  Example: [[https://pl.wiktionary.org/wiki/Wikis%C5%82ownik:Statystyka#J%C4%99zyki | wikt:pl:WS:STAT]].
+
+
+Thanks PeterBowman. I want to see the wikitext for a simple table. Not this:
+https://pl.wiktionary.org/w/index.php?title=Wikis%C5%82ownik:STAT/j%C4%99zyki&action=edit 
+
+Can you create a user sandbox page on that wiki with some simple example tables? 
+
+",1635361845,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Expanding on T42618#434018, [[ https://pl.wiktionary.org/w/index.php?title=MediaWiki:Gadget-autonumber.css&oldid=7808333 | wikt:pl:MediaWiki:Gadget-autonumber.css ]] works with both regular and sorted (`class=""sortable""`) tables, either HTML or wiki-syntax (`{| |}`), all basic skins (including mobile Minerva). No extra column needed, just add class `autonumber`. Example: [[https://pl.wiktionary.org/wiki/Wikis%C5%82ownik:Statystyka#J%C4%99zyki | wikt:pl:WS:STAT]].",1635344698,PHID-USER-zzlez5ppzytn7ghyo6sc,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","The new template **//{{Static row numbers}}//** is a lot better: 
+*https://en.wikipedia.org/wiki/Template:Static_row_numbers 
+
+**Works great** in both **desktop** and **mobile. **For multiple examples see: 
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox144 
+
+Unlike //{{rank}}// it **works with** the **Visual Editor. **
+
+For tables with a single header row all that is needed is to add **//{{static row numbers}}//** just above the top of the table wikitext.
+And **//class=static-row-numbers//** to the top line of the table wikitext. 
+
+For other options see the template documentation. 
+
+Is there any reason this could not be added to the Mediawiki software? That way people could just add the class to get the result. 
+
+And maybe something could be added so that multiple header rows don't need //class=static-row-header// in order for the row numbering to be correct. ",1621469845,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (whyyy)
+- edit previews (again, whyyy)
+- https://en.wikipedia.org/wiki/United_States_drug_overdose_death_rates_and_totals_over_time (what did they do right where the others failed?)
+- perhaps more pages
+
+Yeah... it's gonna suck to fix this bug if you can only see it in 'production'.
+
+(incomplete) list of pages using this template: https://en.wikipedia.org/w/index.php?title=Special%3AWhatLinksHere&target=Template%3ARank&namespace=
+
+Sorry for accidentally closing the task. I'm a noob.",1619598565,PHID-USER-5agpayhvmxww3lkrbrkw,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (whyyy)
+- edit previews (again, whyyy)
+- https://en.wikipedia.org/wiki/United_States_drug_overdose_death_rates_and_totals_over_time (what did they do right where the others failed?)
+- perhaps more pages
+
+Yeah... it's gonna suck to fix this bug if you can only see it in 'production'.
+
+(incomplete) list of pages using this template: https://en.wikipedia.org/w/index.php?title=Special%3AWhatLinksHere&target=Template%3ARank&namespace=",1619598541,PHID-USER-5agpayhvmxww3lkrbrkw,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (whyyy)
+- edit previews (again, whyyy)
+
+Yeah... it's gonna suck to fix this bug if you can only see it in 'production'.",1619597688,PHID-USER-5agpayhvmxww3lkrbrkw,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (which shouldn't use different CSS but alas they do)
+- edit previews
+
+Yeah... it's gonna suck to fix this bug if you can only see it in 'production'.",1619597661,PHID-USER-5agpayhvmxww3lkrbrkw,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Unfortunately the {rank}-template does not seem to work for regular Wikipedia articles. I have tested the results from multiple pages on multiple browsers and multiple platforms and it consistently fails. Screenshots here:
+
+https://imgur.com/a/TsaZoFp
+
+The {rank}-template does seem to work on:
+- en.m.wikipedia.org (which of course uses different CSS)
+- user sandboxes (which shouldn't use different CSS but alas they do)",1619597529,PHID-USER-5agpayhvmxww3lkrbrkw,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","It has been pointed out to me that **row alignment is off when viewed in mobile browsers.** This is when using the previously mentioned **{{Rank} template.**
+
+See discussion here: 
+https://en.wikipedia.org/wiki/Talk:List_of_countries_by_population_(United_Nations)#Alignment_problem
+
+**This is another reason for an integrated, fixed row number column. **",1576042567,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A much easier and better method for creating a static row number column exists. Sandbox 89 linked below uses the new method, and is updated as needed. The table in Sandbox 89 is taken from a version of ""List of countries by incarceration rate"".
+*https://en.wikipedia.org/wiki/List_of_countries_by_incarceration_rate
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox89 
+
+It uses:
+*https://en.wikipedia.org/wiki/Template:Static_column_begin - see its documentation.
+*https://en.wikipedia.org/wiki/Template:End 
+
+{{Static column begin}} redirects to {{Rank}}
+
+Can any of that template code be used here for this phabricator task?
+
+I added class=""wikitable **nowrap** sortable"" to simplify things further.
+
+The nowrap class means the **table rows do not ladder** as the **screen is narrowed.** So the **rows always align.**
+
+**Header-lines=4** allows text alone to be zoomed to very high levels without causing row alignment problems. 
+
+Here is the wikitext at the top that adds the fixed row-number column: 
+
+```
+{{Rank | rows={{TRC|ignore=1|id=nations}} | header-lines=4 | caption=Incarceration populations and rates. From [[World Prison Brief]].}}
+{|class=""wikitable nowrap sortable mw-datatable"" border=1 style=""text-align:right;"" id=""nations""
+|-valign=bottom
+```
+
+And this goes at the end of the table:
+
+
+```
+{{End}}
+```
+",1575966318,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A much easier and better method for creating a static row number column exists. Sandbox 89 linked below uses the new method, and is updated as needed. The table in Sandbox 89 is taken from ""List of countries by incarceration rate"".
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox89 
+
+It uses:
+*https://en.wikipedia.org/wiki/Template:Static_column_begin 
+*https://en.wikipedia.org/wiki/Template:End 
+
+Can any of that template code be used here for this phabricator task?
+
+I added class=""wikitable **nowrap** sortable"" to simplify things further.
+
+The nowrap class means the **table rows do not ladder** as the **screen is narrowed.** So the **rows always align.**
+
+I set the header height to 140px so that people can increase the text size all the way to around 150% in their browsers without causing row alignment problems. 
+
+Basically, this is all that is needed at the top of the table to add the static row number column:
+
+```
+{{Static column begin
+| rows=223
+| header-text=Row
+| header-height=140px
+| text-align=right
+| caption='''Incarceration populations and rates.''' From '''[[World Prison Brief]].'''<ref name=WorldPrisonBrief/>
+}}
+{|class=""wikitable nowrap sortable"" border=1 style=text-align:right;
+|-
+! height=140px | [[Country]] (or [[dependent territory]],<br>[[Subnational administrative division|subnational]] area, etc.)
+```
+
+And this goes at the end of the table:
+
+
+```
+{{End}}
+```
+",1574313089,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A much easier and better method for creating a static row number column exists. See: List of countries by incarceration rate:
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox89 
+https://en.wikipedia.org/w/index.php?title=List_of_countries_by_incarceration_rate&oldid=927094380 
+https://en.wikipedia.org/wiki/Talk:List_of_countries_by_incarceration_rate#Much_easier_and_better_method_for_creating_static_row_number_column 
+
+It uses:
+*https://en.wikipedia.org/wiki/Template:Static_column_begin 
+*https://en.wikipedia.org/wiki/Template:End 
+
+Can any of that be used here for this phabricator task?
+
+I added class=""wikitable **nowrap **sortable"" to simplify things further.
+
+The nowrap class means the **table rows do not ladder ** as the **screen is narrowed.** So the **rows always align.**
+
+I set the header height to 140px so that people can increase the text size all the way to around 150% in their browsers without causing row alignment problems. ",1574243756,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A much easier and better method for creating a static row number column exists. See: List of countries by incarceration rate:
+*https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox89 
+https://en.wikipedia.org/w/index.php?title=List_of_countries_by_incarceration_rate&oldid=927094380 
+https://en.wikipedia.org/wiki/Talk:List_of_countries_by_incarceration_rate#Much_easier_and_better_method_for_creating_static_row_number_column 
+
+It uses:
+*https://en.wikipedia.org/wiki/Template:Static_column_begin 
+*https://en.wikipedia.org/wiki/Template:End 
+
+Can any of that be used here for this phabricator task?
+
+I added class=""wikitable **nowrap **sortable"" to simplify things further.
+
+The nowrap class means the **table rows do not ladder ** as the **screen is narrowed.** So the** rows always align.
+**
+I set the header height to 140px so that people can increase the text size all the way to around 150% in their browsers without causing row alignment problems. ",1574243690,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","
+**[[ https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_and_correctional_supervision_rate | List of U.S. states by incarceration and correctional supervision rate ]] **is an example of a table that needs a fixed row number column. Because there are **3 separate columns that are important enough** that people want **to see them in rank order**. That can't be done with an integrated rank order column. It can only be done with a fixed row number column. 
+
+**[[ https://en.wikipedia.org/wiki/List_of_countries_by_incarceration_rate | List of countries by incarceration rate ]]** may or may not need a fixed row number column. It depends on whether one believes there is more than one column that people want to see in rank order. ",1555388540,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**List of countries by intentional homicide rate:**
+https://en.wikipedia.org/wiki/List_of_countries_by_intentional_homicide_rate
+
+The **[[https://en.wikipedia.org/w/index.php?title=List_of_countries_by_intentional_homicide_rate&oldid=876122887 | current version]]** is very usefully **sorted initially by region and subregion. ** See my comment on the talk page: 
+
+I noticed that the **current version of the table is wider than the last time I checked months ago:**
+https://en.wikipedia.org/w/index.php?title=List_of_countries_by_intentional_homicide_rate&oldid=858063940
+
+**A separate column of row numbers **(something I added to a few charts) **does not work correctly with wider tables and narrow screens. The rows do not align.**
+
+I suggest adding an integrated rank order column instead. There is new info in **[[ https://en.wikipedia.org/wiki/Help:Table | Help:Table ]]** in the Visual Editor section at the end.
+
+It makes editing of tables much easier and faster. It makes adding an integrated rank order column very easy too. Just copy and paste from another table.
+
+**Of course when the table is put in rank order, it is not sorted by region or subregion.**
+
+**That is why there is a Phabricator thread asking for an integrated row number column that remains static when the rest of the table is sorted. Then we could have wide tables that are initially sorted in any way we please.**
+
+See **[[ https://en.wikipedia.org/wiki/Help:Sorting | Help:Sorting ]]** and the section called something like: ""Auto-ranking or adding a row numbering column (1,2,3) next to a table"". See phab:T42618.
+",1546267416,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","@The_Equalizer: Welcome to Phabricator! I'm resetting the priority as you don't seem to [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | plan to work on fixing this ]] (correct me if I'm wrong!) and as the [[ https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities | Priority field summarizes and reflects reality and does not cause it ]]. If you're interested in contributing code to fix this, please refer to https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker . Or you could propose this task for the [[ https://meta.wikimedia.org/wiki/2018_Community_Wishlist_Survey | next Community Wishlist survey ]]. Thanks!",1536271320,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Team Phabricator, will there be any traction on this? This is such a core function of any table that I am surprised this has stalled for so long.
+As a builder of a few advanced tables this has been quite literally a bug-bear to me, even more so that we have a working solution on Polish Wiki.
+I appreciate the English Wiki will need some testing, but really this needs to be actively worked with a higher priority.
+Even if we implement this initially and then going forward, add functionality to make any column fixed.
+If need be I can supply coffee and biscuits to help get this going.",1536266299,PHID-USER-sdoyz3kq5f2hwi7epy2b,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Thanks for the links. I would like some links to long tables where the matmarex JS method of row numbering is being used. Of the links you provided this is the only one with such a table: 
+*https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne_dyskusja/Archiwum/2012-grudzie%C5%84#Sortowanie_tabeli 
+
+This is the class needed in the column header to fix the row numbers:
+
+!class=""unsortable ordinal""
+
+Here is the wikitext for that table below. I don't like the fact that one has to add the numbers. That is problematic. For example; with a long alphabetical list one would have to manually renumber the row numbers after each new row added in the middle of the table. Especially tedious the farther up the table one adds the row. Since all row numbers after the new row entry would have to be changed. 
+
+Can this JS solution be changed so that it also creates the row numbers? That way we can leave the row number column blank, and let the JS fill it in. Or maybe a combination of JS and CSS. Since table sorting depends on jquery.tablesorter.js, then I don't see why this JS can not be part of the solution. I like that the column header is default blank for the row number column. It is obvious it is a row of numbers, and that it is not sorting. Yet one could manually add a column header name, symbol, or icon. 
+
+```
+{| class=""wikitable sortable"" style=""text-align:center;"" align=""left""
+!class=""unsortable ordinal"" width=""25px""|
+!width=""60px""|kolor
+!width=""60px""|mebel
+!width=""60px""|miasto
+|-
+|1||biały||stół||Kraków
+|-
+|2||zielony||taboret||Iława
+|-
+|3||czarny||szafa||Puck
+|}
+```
+Is the previous CSS solution fixable? It does not require manually entering the row numbers. Could it be combined with the matmarex JS solution?",1523482294,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#4121570, @Timeshifter wrote:
+> matmarex. Could you edit that old comment of yours and add in full URLs so that we can check it out?
+
+Here you go:
+
+>>! In T42618#433972, @matmarex wrote:
+> The solution was discussed on pl.wikipedia's technical village pump[1][2] and is currently live in its common.js[3]. It's used on a few pages already, including the aforementioned [[pl:Miasta w Polsce (statystyki)]] and our help page with a list of interwiki codes, https://pl.wikipedia.org/wiki/Pomoc:Interwiki .
+> 
+> [1] https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne_dyskusja/Archiwum/2012-grudzie%C5%84#Poprawa_tabeli_w_Miasta_w_Polsce_%28statystyki%29
+> [2] https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne_dyskusja/Archiwum/2012-grudzie%C5%84#Sortowanie_tabeli
+> [3] https://pl.wikipedia.org/wiki/MediaWiki:Common.js , at the very bottom
+
+>>! In T42618#4121570, @Timeshifter wrote:
+> And could you start a new comment listing some more info and links since then. 
+Which ""more info and links"" are needed? What's missing in the current information provided? (It's hard to provide more info if you don't get told which info.)",1523443415,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","matmarex. Could you edit that old comment of yours and add in full URLs so that we can check it out? I have had to do that on old comments after we changed over to phabricator. Is the JS the same? You might update that also on that post. 
+
+And could you start a new comment listing some more info and links since then. Links to working tables, etc.. Also, any how-to pages concerning its use. I can use Google translation to figure it out somewhat. 
+
+Are people using this function of tables? Is it easy to use? Does it require a blank column to be set up? Or does it create the column too? 
+",1523392568,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","You could convince an English Wikipedia administrator to copy the solution from Polish Wikipedia that I implemented there five years ago, see comment above: T42618#433972. ",1523379257,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Could someone explain to me in simple English why there is no simple way to add a column of fixed row numbers to tables. What is blocking this? Many tables are out of date due to their use of rank order columns that are completely out of whack. Due to any change in data in the table. 
+
+There are thousands, if not tens of thousands, of tables that would benefit from this. Currently, the only method of adding a column of fixed row numbers is so tedious, timeconsuming, and problematic that only 5 tables has a column of fixed row numbers. See them here:
+*https://en.wikipedia.org/wiki/Category:Article_with_table_with_fixed_row_numbers 
+
+I bring this up now due to this template deletion discussion:
+*https://en.wikipedia.org/wiki/Wikipedia:Templates_for_discussion/Log/2018_April_10#Template:Rank_order 
+
+Removing the rank numbers might be too bold. People don't realize that there is an alternative that works better, and does the same thing (row numbers). They get pissed when the rank numbers are removed, and not replaced with the alternative (row numbers). And that takes some work. The template serves a purpose in remembering some tables to go back to someday, and hopefully someone will work on them. It also helps developers see the need for their patch that they sometimes work on, but haven't finished due to problems. There are thousands of tables that this template could be placed on.
+
+A patch would be so much simpler. ",1523374156,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Change 234473 abandoned by Krinkle:
+Add class rownumbers for tables
+
+Reason:
+Closing to reduce review noise. Feel free to re-open once task has settled on a solution.
+
+[[https://gerrit.wikimedia.org/r/234473]]",1511812174,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","This may be a starting point to pass on to others interested in this topic:
+Articles containing tables with fixed row numbers are in this hidden category: 
+*https://en.wikipedia.org/wiki/Category:Article_with_table_with_fixed_row_numbers 
+
+Please add the category to any article I have missed. 
+
+I noticed that the 800 row table with fixed row numbers is now sorting fast for me: 
+*http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 
+
+Later edit: I checked sorting using an 11-year old PC, and I see that sorting took 2 seconds for that very long table of 779 rows. 
+
+On that same 11-year-old PC sorting is fast on lists of around 200 rows. Such as this one that has fixed row numbers: 
+*http://cannabis.shoutwiki.com/wiki/Basic_2013_Global_Marijuana_March_city_list
+
+So since country lists on Wikipedia are a little over 200 rows, then this type of CSS will not be a problem, even on old PCs. Country lists are about the longest lists on Wikipedia. ",1500133061,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","This may be a starting point to pass on to others interested in this topic:
+Articles containing tables with fixed row numbers are in this hidden category: 
+*https://en.wikipedia.org/wiki/Category:Article_with_table_with_fixed_row_numbers 
+
+Please add the category to any article I have missed. 
+
+I noticed that the 800 row table with fixed row numbers is now sorting fast for me: 
+*http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 ",1500126292,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Any system of row numbering is fine by me. I saw another list today I would like to add row numbers to: 
+*https://en.wikipedia.org/wiki/List_of_minimum_wages_by_country 
+
+Click the header of the hourly PPP minimum wage column to get a list covering the highest to lowest minimum wages by country. USA is around 15th on the list. Not sure since there is no row numbering.
+
+That list though is too wide to use the method I have used in other lists. Such as in this one: 
+**https://en.wikipedia.org/wiki/List_of_countries_by_intentional_homicide_rate ",1498620295,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","It seems there are two feature requests being mixed here:
+
+1. Having a ""fixed"" column that won't change when the rows are sorted. Typically a column that numbers the rows, which we want to treat separately and not related to the other fields in each row.
+2. Not needing to manually maintain the numbers in these rows when editing pages so that you don't have to change all other rows when inserting or re-ordering entries.
+
+The current patch essentially implements a solution for issue 2 (automatically number the rows and render the row's number). It also kind of solves issue 1. It doesn't really preserve the authored cell contents, but rather it reproduces them dynamically in CSS. This still requires manual work and seems fairly limited.
+
+I'd recommend solving these problems separately. Two ideas:
+
+* Allow for automatic numbering of rows. Perhaps by providing syntax in wikitext that would allow a cell in each row to be set as the placeholder for an incrementing number within the current table. Or perhaps by generating the tables with a Lua module? Or by keeping them maintained manually, with perhaps a client-side feature in VisualEditor/WikiEditor to automatically encourage re-indexing the ""index number"" cell based on a particular marking on the class (e.g. a class on the table, similar to ""wikitable"" and ""sortable"").
+* Add a feature in tablesorter that allows one of the columns to be marked as ""static"" (similar to ""unsortable"") which will preserve that table column as-is regardless of the sorting of the rest of other columns for each row.",1495548608,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Here are some lists with row numbering: 
+*https://en.wikipedia.org/wiki/List_of_countries_by_incarceration_rate 
+*https://en.wikipedia.org/wiki/List_of_countries_by_intentional_homicide_rate 
+*https://en.wikipedia.org/wiki/List_of_countries_by_total_health_expenditure_per_capita 
+*https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_rate 
+
+Discovered another problem with the current method of row numbering. Italics used for some of the country names causes the rows to not align the farther down the list one goes. See this list revision: 
+https://en.wikipedia.org/w/index.php?title=List_of_countries_by_intentional_homicide_rate&oldid=727879356 
+Had to remove the italics to fix it. 
+
+These lists are popular and are maintained since they are in alphabetical order. The row numbering allows rank order to be seen easily with a click of the mouse on the sorting button. 
+
+The problem is that the initial setup of such lists is tedious, and subject to many rules such as no italics, no flag icons, and no references within the chart itself. All break the row alignment. Along with wide tables. So the number of columns has to be limited to allow the charts to be seen correctly on narrower screens. 
+",1467498935,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I put some tables in a sandbox of mine to see if the patch has been implemented in the test release of MediaWiki 1.27.0-wmf.7. 
+*https://test2.wikipedia.org/wiki/User:Timeshifter/Sandbox 
+
+The patch has not been implemented in the test release of MediaWiki 1.27.0-wmf.7. 
+*https://www.mediawiki.org/wiki/MediaWiki_1.27/wmf.7 ",1449321463,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I put some tables in a sandbox of mine to see if the patch has been implemented in the test release of MediaWiki 1.27.0-wmf.7. 
+*https://test2.wikipedia.org/wiki/User:Timeshifter/Sandbox 
+
+The patch has not been implemented in the test release of MediaWiki 1.27.0-wmf.7. ",1449321295,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I put some tables in a sandbox of mine to see if the patch has been implemented in the test release of MediaWiki 1.27.0-wmf.7 (dfe838b). 
+*https://test2.wikipedia.org/wiki/User:Timeshifter/Sandbox 
+
+The patch has not been implemented in the test release of MediaWiki 1.27.0-wmf.7 (dfe838b). ",1449320828,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I updated the tables in this Wikipedia article: 
+*[[https://en.wikipedia.org/wiki/List_of_countries_by_total_health_expenditure_per_capita|List of countries by total health expenditure per capita]]. 
+
+I noticed on the talk page that I had left a message over 3 years ago suggesting adding row numbering. No one had updated the list since then even though this is a topic frequently in the media. 
+
+The reason is that people had the list in rank order instead of in alphabetical order. I put it in alphabetical order which makes it much easier to update. See some of my method here: 
+*https://commons.wikimedia.org/wiki/Commons:Convert_tables_and_charts_to_wiki_code_or_image_files#Web_to_LibreOffice_Calc_to_tab2wiki
+
+Unfortunately, the current primitive method of row numbering I am using over the last few years breaks many functions of tables:
+*Flags can not be used because they break the alignment of the row-number column with the rest of the table. This adds up at the bottom of the table where the rows will be completely misaligned, especially at smaller text sizes. 
+
+*A note column can not be used due to narrow screens breaking alignment due to laddering. 
+*References can not be added within the table due to the superscript increasing the height of that one line, and thus breaking alignment. 
+*The tables can not be put side by side or laddering will occur, and alignment is broken. 
+
+This health expenditure table has to do without more than a few years of data or the table is too wide. This is a problem on many such lists of nations inside tables. For example; many more years of data could be added to these popular articles: 
+*[[https://en.wikipedia.org/wiki/List_of_countries_by_intentional_homicide_rate|List of countries by intentional homicide rate]]
+*[[https://en.wikipedia.org/wiki/List_of_countries_by_incarceration_rate|List of countries by incarceration rate]]
+
+There are many more years for homicide rates for example. See: 
+*[[https://en.wikipedia.org/wiki/User:Timeshifter/Sandbox62|User:Timeshifter/Sandbox62]]
+
+
+
+",1448870831,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Is T113340 (Allow to request modules by CSS classes in content) holding this up? 
+
+I was looking at the proposed patch: 
+https://gerrit.wikimedia.org/r/#/c/234473 
+
+Trying to decipher the holdup from the notes there. There are so many tables not being updated because they are in rank order initially. ",1447348326,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I checked the Internet Explorer 7 page on Wikipedia: 
+https://en.wikipedia.org/wiki/Internet_Explorer_7 
+
+A reference from that article said that IE7's desktop browser share in August 2015 was 0.31%. 
+http://marketshare.hitslink.com/browser-market-share.aspx?qprid=2&qpcustomd=0",1442874731,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I was looking at: 
+https://gerrit.wikimedia.org/r/#/c/234473 
+
+and a note from Sept 3, 2015 3:31 AM says ""Added code to make the rank column always unsortable""
+
+I assume this is added to the column header?:
+```class=""unsortable"" |```
+
+That is necessary to remove the sorting icon from the header. So people will not be confused. ",1441943536,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1604298, @Timeshifter wrote:
+> How does this fail in Internet Explorer 7? Is it just a blank column? If so, that is not important in my opinion. 
+
+Yes, in IE7 and other unsupported browsers (if any), just a blank column will be shown. Or, if you add the numbers as fallback with the `rownumbers-fallback` class, these will be shown, but will be sorted along with the rest of the table, instead of being fixed.",1441352371,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1601171, @Schnark wrote:
+> Adding a blank column is easy. That's two clicks in Visual Editor, 
+
+It is not immediately intuitive, but it is easy after I figured it out! So it takes exactly 3 steps to add a row-number column to an existing table. See history: 
+https://test.wikipedia.org/w/index.php?title=User:Timeshifter/Sandbox4&action=history 
+https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox4 
+
+Now that I see how easy it is to add a blank column this is definitely easier than my previous suggestion. I could explain it all in fewer paragraphs than is currently used in [[https://en.wikipedia.org/wiki/Help:Sorting|Help:Sorting]]. See the section currently titled ""Auto-ranking or adding a row numbering column (1,2,3) next to a table"". 
+
+How does this fail in Internet Explorer 7? Is it just a blank column? If so, that is not important in my opinion. 
+
+",1441315081,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I'm of the opinion that functions like this should 'just work' and so far none of the proposals I have seen qualify as 'just work'. That means that people will use it incorrectly and there will be confusion. That's not a good experience. I'm also pondering: What would the dialog window look like for this in VE.
+
+As an 'overall picture' kind of guy, i'm just not enthusiastic and I think that we should be careful of 'feature creep' and long term maintenance burden. Sometimes it's better to NOT have a feature, then to add extra complexity.",1441275714,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","How about something like `header=Lp` in the top of the table wikitext? So to get Polish numbers and header:
+```
+{|  lang=""pl"" header=""Lp"" class=""wikitable sortable rownumbers""
+```
+
+>>! In T42618#1601171, @Schnark wrote:
+> Adding a blank column is easy. That's two clicks in Visual Editor, or replacing `/^\| /` with `| || ` with the search-and-replace-tool in the WikiEditor toolbar. Given that users are currently willing to add code like on https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_rate#Incarceration_rate_by_state adding a blank column won't scare them away.
+
+I am the one that added the fixed row numbering to that article. It had previously been in rank order, and so it was impossible to update it easily.  I added much more recent numbers that I copied from the data table of a Commons map of US incarceration rates that someone else did. It was in alphabetical order, and not rank order. The Wikipedia article had been using 2009 numbers until I updated it this summer. 
+
+This patch will not be used much if it depends on skilled editors. I don't use Wikieditor. I rarely use the Visual Editor. I barely understand some CSS, and I occasionally have figured out (and soon forgotten) some regex methods in Notepad++ to do complicated replacements within the Unicode wikitext of long lists or SVG images. Very frustrating. I am not a developer like you. I am skilled in other areas. 
+
+Currently, people are adding rank columns that are not fixed. Many of these table lists are way out of date because even a single change messes up the rank order, and the list is soon completely out of order. People stop updating it at all. A fixed row-number column fixes this because then the list can be put in alphabetical order. Alphabetical order is far easier to maintain. Sorting a column instantly produces a list in rank order. If this patch is dead simple to use then hundreds of tables will then be easy to set up and maintain. ",1441268597,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","How something like `header=Lp` in the top of the table wikitext? So to get Polish numbers and header:
+```
+{|  lang=""pl"" header=""Lp"" class=""wikitable sortable rownumbers""
+```
+
+>>! In T42618#1601171, @Schnark wrote:
+> Adding a blank column is easy. That's two clicks in Visual Editor, or replacing `/^\| /` with `| || ` with the search-and-replace-tool in the WikiEditor toolbar. Given that users are currently willing to add code like on https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_rate#Incarceration_rate_by_state adding a blank column won't scare them away.
+
+I am the one that added the fixed row numbering to that article. It had previously been in rank order, and so it was impossible to update it easily.  I added much more recent numbers that I copied from the data table of a Commons map of US incarceration rates that someone else did. It was in alphabetical order, and not rank order. The Wikipedia article had been using 2009 numbers until I updated it this summer. 
+
+This patch will not be used much if it depends on skilled editors. I don't use Wikieditor. I rarely use the Visual Editor. I barely understand some CSS, and I occasionally have figured out (and soon forgotten) some regex methods in Notepad++ to do complicated replacements within the Unicode wikitext of long lists or SVG images. Very frustrating. I am not a developer like you. I am skilled in other areas. 
+
+Currently, people are adding rank columns that are not fixed. Many of these table lists are way out of date because even a single change messes up the rank order, and the list is soon completely out of order. People stop updating it at all. A fixed row-number column fixes this because then the list can be put in alphabetical order. Alphabetical order is far easier to maintain. Sorting a column instantly produces a list in rank order. If this patch is dead simple to use then hundreds of tables will then be easy to set up and maintain. ",1441268474,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1598099, @Timeshifter wrote:
+
+> And a blank header is fine for the number column.
+
+I would consider a blank header just because the user was to lazy to add a row for it as bad practice. It's not clear whether that blank header is acceptable for everyone, see matmarex's comment:
+>>! In T42618#434067, @matmarex wrote:
+>    * In the heading neither ""№"" nor ""#"" would be acceptable in, say,
+>      Polish (we use ""Lp."" which is an abbreviation of ""ordinal
+>      number""), although this might be worked around by just leaving
+>      the space empty as tm112 suggests above; I'm not sure if that'd
+>      be acceptable for all languages we support in MediaWiki, though.
+
+
+> If editors are required to add a blank column first this will be used a lot less than it could be. Country lists have over 200 rows. 
+
+Adding a blank column is easy. That's two clicks in Visual Editor, or replacing `/^\| /` with `| || ` with the search-and-replace-tool in the WikiEditor toolbar. Given that users are currently willing to add code like on https://en.wikipedia.org/wiki/List_of_U.S._states_by_incarceration_rate#Incarceration_rate_by_state adding a blank column won't scare them away.
+",1441265148,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","OK, I see that currently it requires an existing blank column. See: 
+https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox3
+
+How about ""rownumbers"" class for adding numbers to an existing blank column? And ""autorownumbers"" class for adding both the numbers and the column. See:
+
+>>! In T42618#434018, @Yair_rand wrote:
+> To just get the fixed numbering column without manually adding cells to each row or using JS, one could use CSS generated-content cells with counters:
+
+But why require an existing column at all? And a blank header is fine for the number column. I used Yair_rand's method without problems on Shoutwiki. I removed the border coloring from his CSS. Maybe some other changes in the CSS too. I don't remember, since it was done a couple years ago. Here is what I did: 
+*http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+*http://cannabis.shoutwiki.com/wiki/2013list - see section called ""Alphabetical city list"".
+
+If editors are required to add a blank column first this will be used a lot less than it could be. Country lists have over 200 rows. 
+",1441229841,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","OK, I see that currently it requires an existing blank column. See: 
+https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox3
+
+How about ""rownumber"" class for adding numbers to an existing blank column? And ""autorownumber"" class for adding both the numbers and the column. See:
+
+>>! In T42618#434018, @Yair_rand wrote:
+> To just get the fixed numbering column without manually adding cells to each row or using JS, one could use CSS generated-content cells with counters:
+
+But why require an existing column at all? And a blank header is fine for the number column. I used Yair_rand's method without problems on Shoutwiki. I removed the border coloring from his CSS. Maybe some other changes in the CSS too. I don't remember, since it was done a couple years ago. Here is what I did: 
+*http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+*http://cannabis.shoutwiki.com/wiki/2013list - see section called ""Alphabetical city list"".
+
+If editors are required to add a blank column first this will be used a lot less than it could be. Country lists have over 200 rows. 
+
+",1441212943,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1594012, @Timeshifter wrote:
+> What about using ""rownumber""? Is that in use on Wikipedia, or other wikis?
+
+`rownumber` in singular or `rownumbers` in plural? But yes, that's probably the best idea.
+
+>>! In T42618#1594246, @TheDJ wrote:
+> Hmm, i still find the whole feature somewhat confusing:
+> 
+> Deployed here:
+> https://test.wikipedia.org/wiki/User:TheDJ/T42618
+
+I just added a second example, to both show how it works with an unsortable first column and how it looks like in a different language.
+
+> And it's still purely a stylistic effect, that will rely on people still fixing the fallback values, which of course they won't...
+
+Well, in most cases the fallback values won't be added at all, so users of IE6 and IE7 will see an empty row instead of the rank, which isn't perfect (that's why I think it should be possible to add a fallback), but doesn't hurt much.
+
+> And the whole initial premise of it being 'confusing' that the numbers follow the sort state, is rather an arbitrary valuation as well. I find it confusing if they don't follow the sorting actions personally. I don't know. I'm still not enthusiastic.
+
+In my example of course it doesn't make sense to have a column for the rank in the current order, but for example the table in https://de.wikipedia.org/wiki/Liste_der_Gro%C3%9Fst%C3%A4dte_in_Deutschland uses a hack to add such a fixed rank column, and it does make sense there.
+
+>>! In T42618#1594736, @Timeshifter wrote:
+> It seems that the patch does not create a column for the row numbers? Why not? 
+
+Because it doesn't know what to use as heading.",1441179713,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","It seems that the patch does not create a column for the row numbers? Why not? 
+*https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox2 ",1441142317,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","It seems that the patch does not create a column for the row numbers? Why not? 
+https://test.wikipedia.org/wiki/User:Timeshifter/Sandbox2 ",1441141827,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","https://test.wikipedia.org/wiki/User:TheDJ/T42618
+
+> And the whole initial premise of it being 'confusing' that the numbers follow the sort state, is rather an arbitrary valuation as well. I find it confusing if they don't follow the sorting actions personally. I don't know. I'm still not enthusiastic.
+
+I suggest that the patch remove the sorting icon from the rank column. Then people are more likely to figure out that the rank column is not supposed to sort, nor change at all. The patch needs to add the ""unsortable"" class to the rank column header. See how here:
+*https://en.wikipedia.org/wiki/Help:Sorting#Making_a_column_unsortable 
+
+",1441139984,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Hmm, i still find the whole feature somewhat confusing:
+
+Deployed here:
+https://test.wikipedia.org/wiki/User:TheDJ/T42618
+
+And it's still purely a stylistic effect, that will rely on people still fixing the fallback values, which of course they won't...
+
+And the whole initial premise of it being 'confusing' that the numbers follow the sort state, is rather an arbitrary valuation as well. I find it confusing if they don't follow the sorting actions personally. I don't know. I'm still not enthusiastic.",1441135166,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","What about using ""rownumber""? Is that in use on Wikipedia, or other wikis?
+
+""mw-"" is used for mw-collapsible and mw-collapsed on Wikia:
+*http://community.wikia.com/wiki/Help:Collapsing 
+
+But not on Wikipedia: 
+*https://en.wikipedia.org/wiki/Help:Collapsing
+
+A side note. I noticed that the numbeo.com site uses fixed row numbering on most of their many sortable tables:
+*http://www.numbeo.com - for example: 
+*http://www.numbeo.com/crime/rankings_by_country.jsp - the rank column. ",1441139545,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","What about using ""rownumber""? Is that in use on Wikipedia, or other wikis?
+
+""mw-"" is used for mw-collapsible and mw-collapsed on Wikia:
+http://community.wikia.com/wiki/Help:Collapsing 
+
+But not on Wikipedia: 
+https://en.wikipedia.org/wiki/Help:Collapsing
+
+A side note. I noticed that the numbeo.com site uses fixed row numbering on most of their many sortable tables:
+*http://www.numbeo.com - for example: 
+*http://www.numbeo.com/crime/rankings_by_country.jsp - the rank column. ",1441132993,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","You almost convinced me to drop the ""mw-"" prefix, but then I noticed, that `autonumber` is already in use for autonumbered external links. This shouldn't be a problem if everything is done right, as in one case the class is on an `<a>`, in the other case on a `<table>` element, but you never know with what expectations users added rules for `.autonumber` to their personal CSS. Also note that there is a class `mw-datatable` which is used on tables in wiki content, too, so the ""mw-"" prefix isn't my invention.
+
+Of course I'm open to arguments against my concerns and other suggestions, the currently proposed patch won't be the last one.",1441092554,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I prefer simplicity. There is no great need for ""mw"" in front of the class name. I have no problem with ""autonumber"", ""rownumber"", or just ""rows"". Or anything else without ""mw"" in front of it. 
+
+I doubt too many people other than me used the old class=autonumber CSS provided by Yair_rand higher up in this thread.
+
+See: 
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+It has the Yair_rand CSS for easy autonumbering used on these pages: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_10 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 
+http://cannabis.shoutwiki.com/wiki/2013list 
+
+By changing to the latest Mediawiki class name those pages will still work when the mediawiki software used on Shoutwiki incorporates the new automatic row numbering class. I can then delete the old Yair_rand CSS for autonumbering from MediaWiki:Common.css on that Shoutwiki wiki. 
+
+",1441066023,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I prefer simplicity. There is no great need for ""mw"" in front of the class name. I have no problem with ""autonumber"", ""rownumber"", or just ""rows"". Or anything else without ""mw"" in front of it. 
+
+I doubt too many people other than me used the old class=autonumber CSS provided by Yair_rand higher up in this thread.
+
+See: 
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+It has the Yair_rand CSS for easy autonumbering used on these pages: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_10 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 
+http://cannabis.shoutwiki.com/wiki/2013list 
+
+By changing to the latest Mediawiki class name those pages will still work when the mediawiki software used on Wikia incorporates the new automatic row numbering class. I can then delete the old Yair_rand CSS for autonumbering from MediaWiki:Common.css on that Shoutwiki wiki. 
+
+",1441065859,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I prefer simplicity. There is no great need for ""mw"" in front of the class name. I have no problem with ""autonumber"", ""rownumber"", or just ""rows"". Or anything else without ""mw"" in front of it. 
+
+I doubt too many people other than me used the old class=autonumber CSS provided by Yair_rand higher up in this thread.
+
+See: 
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+It has the Yair_rand CSS for easy autonumbering used on these pages: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_10 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4 
+http://cannabis.shoutwiki.com/wiki/2013list 
+
+By changing to the latest Mediawiki class name those pages will still work when the mediawiki software used on Wikia incorporates the new automatic row numbering class. I can then delete the old Yair_rand CSS for autonumbering from MediaWiki:Common.css on that Wikia wiki. 
+
+",1441065793,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Hmm, ""autonumber"" might be better in this case for consistency with existing classes from this script (like ""sortable"") and since the script aspires not to be MediaWiki-dependent.",1441044558,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",">>! In T42618#1588087, @MatthiasDD wrote:
+> But why starts the classname with mw- ? I suggesst use of ""autonumber"" instesd ""mw-autonumber"".
+
+To avoid clashes with classes added to MediaWiki:Common.css, e.g. T42618#434098.
+",1441008907,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","A good patch, it works good for ltr- and rtl-direction. But why starts the classname with mw- ? I suggesst use of ""autonumber"" instesd ""mw-autonumber"". Every user read this HTML-code in the wiki-editor. It should be simple and short. For the counter i suggest use of ""row"":
+  table.autonumber tr td:first-child:before {
+	counter-increment: row;
+	content: counter(row);
+}",1440971369,PHID-USER-tyoxb7kenw57z2mztwe2,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Change 234473 had a related patch set uploaded (by Gerrit Patch Uploader):
+Add class mw-autonumber for tables
+
+[[https://gerrit.wikimedia.org/r/234473]]
+",1440748008,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Is there any reason this can not be implemented right now? I will be adding row numbering to dozens of tables right away when this is implemented. Once I do so, I am sure it will be immediately added to hundreds more tables as others see how easy it is to add something like 
+class=""wikitable sortable rownumbers"" 
+
+See Help:Sorting to see how convoluted it is to add row numbers now without a class for it: 
+https://en.wikipedia.org/wiki/Help:Sorting 
+https://en.wikipedia.org/wiki/Help:Sorting#Auto-ranking_or_adding_a_row_numbering_column_.281.2C2.2C3.29_next_to_a_table 
+See also the talk page and this current thread (before it goes to the talk archive):
+https://en.wikipedia.org/wiki/Help_talk:Sorting#Accessibility_issues_when_implementing_.22rank.22_in_a_separate_table ",1439915370,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Is there any reason this can not be implemented right now? I will be adding row numbering to dozens of tables right away when this is implemented. Once I do so, I am sure it will be immediately added to hundreds more tables as others see how easy it is to add something like 
+class=""wikitable sortable rownumbers"" 
+
+See Help:Sorting to see how convoluted it is to add row numbers now without a class for it: 
+https://en.wikipedia.org/wiki/Help:Sorting 
+See also the talk page and this current thread (before it goes to the talk archive):
+https://en.wikipedia.org/wiki/Help:Sorting#Auto-ranking_or_adding_a_row_numbering_column_.281.2C2.2C3.29_next_to_a_table ",1439915268,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Bartosz Dziewoński from comment #20)
+> 1. Obviously, no support for old browsers. I understand that this is a
+>    trade-off that we're willing to make.
+
+According to http://caniuse.com/#feat=css-counters the CSS solution even works in IE8, and because IE7 and below are now grade C, a JS solution can't reach a greater level of support anyway.
+
+I doubt that there is great support for CSS Counter Styles Level 3 yet, but at least most of the stuff from Predefined Counter Styles should be supported, so localization up to the level it is done for ordered lists ([1]) should be possible.
+
+[1] https://git.wikimedia.org/blob/mediawiki%2Fcore.git/902f90a123bef85cfaf2b206c51a89ffdd416674/resources%2Fsrc%2Fmediawiki.legacy%2Fshared.css#L935",1411545124,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","In comment 18 I linked to a row-numbered sortable table in a page that no longer has that table. I copied the table from an old revision of the page to this sandbox: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_10 
+This table has 168 rows. Sorting is not slowed down by the auto numbering. 
+
+The auto numbering CSS used is found here: 
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+CSS is in the section titled ""Easy method of auto numbering of table rows"".
+
+As I said previously (comment 23) sorting a table with 779 rows is slowed down by the addition of auto numbering: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4",1400167451,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",*** Bug 10433 has been marked as a duplicate of this bug. ***,1398794576,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","On long lists autonumbering table rows means sorting any column takes longer. Around a couple seconds to sort a column 800 rows long. This is true whether using the easy CSS method or the hard CSS method (with every cell manually added in).
+
+I link to an example below of a table with around 800 rows. 
+
+With autonumbering:
+http://cannabis.shoutwiki.com/w/index.php?title=GMMcities&oldid=6398 
+Table from above-linked old revision has been copied to this sandbox after converting to the easy CSS method: 
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_4
+
+Same table without autonumbering sorts faster:
+http://cannabis.shoutwiki.com/wiki/User:Timeshifter/Sandbox_5 
+
+The initial click takes a couple seconds in all cases. Click again. 
+
+I haven't been able to find a working JS method of autonumbering. Can someone link to a table with JS doing the autonumbering. I want to see how fast it is. 
+
+I have not seen any JS tables linked from previous comments that work for me. Please point me to working JS I can copy to Shoutwiki, or to my personal user JS on a wiki. So I can test it on some tables.",1396482842,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+They also say (on w3) that you can add suffix which solves the problem with number formatting that you mentioned. In such way those numbering issues are solved but every wiki would have to set its own @counter-style and heading cell content.
+(Or – can it be preset?)",1396467047,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Bartosz Dziewoński from comment #20)
+>    * No support for digit conversion (some languages use other numerals
+>      than 0 1 2 3 4 5 6 7 8 9, e.g. Arabic uses ٠‎ ١‎ ٢‎ ٣‎ ٤‎ ٥‎ ٦‎ ٧‎ ٨‎
+> ٩‎).
+>      I don't think this is possible with CSS (although I might be wrong).
+
+I underestimated the CSS designers, it does support this :) (in the spec at least). See <http://www.w3.org/TR/css-counter-styles-3/> and <http://www.w3.org/TR/predefined-counter-styles/>.",1396464926,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Yair Rand from comment #17)
+> To just get the fixed numbering column without manually adding cells to each
+> row or using JS, one could use CSS generated-content cells with counters:
+>   <snip>
+
+I was thinking about doing this with just CSS, and this solution is
+very neat, but is has two problems:
+
+1. Obviously, no support for old browsers. I understand that this is a
+   trade-off that we're willing to make.
+
+2. Less obviously, no support for internationalization!
+   * No support for digit conversion (some languages use other numerals
+     than 0 1 2 3 4 5 6 7 8 9, e.g. Arabic uses ٠‎ ١‎ ٢‎ ٣‎ ٤‎ ٥‎ ٦‎ ٧‎ ٨‎ ٩‎).
+     I don't think this is possible with CSS (although I might be wrong).
+   * No support for various typographic conventions on the number
+     formatting; again, proper Polish would require a dot to be placed
+     after the ordinal number (as in 1., 2., 3. etc. for first,
+     second, third), some might want 1st, 2nd, 3rd etc. in English as
+     well, and who knows what other languages might require.
+   * In the heading neither ""№"" nor ""#"" would be acceptable in, say,
+     Polish (we use ""Lp."" which is an abbreviation of ""ordinal
+     number""), although this might be worked around by just leaving
+     the space empty as tm112 suggests above; I'm not sure if that'd
+     be acceptable for all languages we support in MediaWiki, though.
+
+It's probably a good solution on a per-wiki basis (for at least some
+languages), but I'm afraid we won't be able to use it in core unless we
+manage to solve the above problems (might be doable with some deep LESS
+magic, at least for the latter two).",1396464716,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+This solution is great, I hope this one will be implemented soon.
+
+As for '#' or '№' – I think there could be also an empty cell or even a cell without borders and background (as if there was no cell). It could also be up to local admins choice.",1396437056,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Yair Rand from comment #17)
+> To just get the fixed numbering column without manually adding cells to each
+> row or using JS, one could use CSS generated-content cells with counters: ...
+
+It works great, and is a lot easier to use than the row-numbering method I was using before. 
+
+I am using Yair Rand's method on a ShoutWiki wiki. Currently using this easy method on the table on this page: 
+*http://cannabis.shoutwiki.com/wiki/2013list 
+
+Before I would have to manually create a cell at the beginning of each row in the table. Here is the table with the old method:
+* [Removed incorrect link]
+
+Now all I have to do is add this to the top line of any table: 
+
+class=""sortable autonumber""
+
+I adapted the CSS a little. Here it is:
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+I removed the border coloring, and I used # for the header. See: 
+https://en.wikipedia.org/wiki/Number_sign 
+- # is more common in American English. 
+
+I hope this easy method can be implemented soon on Wikipedia and the Commons. It is by far the easiest auto-row-numbering method I have seen. It would make things a lot easier than the hacks currently listed at Help:Sorting: 
+*https://en.wikipedia.org/wiki/Help:Sorting - see ""Static column"" and following sections.",1441210643,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Yair Rand from comment #17)
+> To just get the fixed numbering column without manually adding cells to each
+> row or using JS, one could use CSS generated-content cells with counters: ...
+
+It works great, and is a lot easier to use than the row-numbering method I was using before. 
+
+I am using Yair Rand's method on a ShoutWiki wiki. Currently using this easy method on the table on this page: 
+*http://cannabis.shoutwiki.com/wiki/2013list 
+
+Before I would have to manually create a cell at the beginning of each row in the table. Here is the table with the old method:
+* [Removed incorrect link]
+
+Now all I have to do is add this to the top line of any table: 
+
+class=""sortable autonumber""
+
+I adapted the CSS a little. Here it is:
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+I removed the border coloring, and I used # for the header. See: 
+https://en.wikipedia.org/wiki/Number_sign 
+# is more common in American English. 
+
+I hope this easy method can be implemented soon on Wikipedia and the Commons. It is by far the easiest auto-row-numbering method I have seen. It would make things a lot easier than the hacks currently listed at Help:Sorting: 
+*https://en.wikipedia.org/wiki/Help:Sorting - see ""Static column"" and following sections.",1439907173,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to Yair Rand from comment #17)
+> To just get the fixed numbering column without manually adding cells to each
+> row or using JS, one could use CSS generated-content cells with counters: ...
+
+It works great, and is a lot easier to use than the row-numbering method I was using before. 
+
+I am using Yair Rand's method on a ShoutWiki wiki. Currently using this easy method on the tables on these pages: 
+*http://cannabis.shoutwiki.com/wiki/2014list 
+*http://cannabis.shoutwiki.com/wiki/2013list 
+
+Before I would have to manually create a cell at the beginning of each row in the table. Here is the table with the old method:
+*http://cannabis.shoutwiki.com/w/index.php?title=2014list&oldid=21668
+
+Now all I have to do is add this to the top line of any table: 
+
+class=""sortable autonumber""
+
+I adapted the CSS a little. Here it is:
+http://cannabis.shoutwiki.com/wiki/MediaWiki:Common.css 
+
+I removed the border coloring, and I used # for the header. See: 
+https://en.wikipedia.org/wiki/Number_sign 
+# is more common in American English. 
+
+I hope this easy method can be implemented soon on Wikipedia and the Commons. It is by far the easiest auto-row-numbering method I have seen. It would make things a lot easier than the hacks currently listed at Help:Sorting: 
+*https://en.wikipedia.org/wiki/Help:Sorting - see ""Static column"" and following sections.",1396366807,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","To just get the fixed numbering column without manually adding cells to each row or using JS, one could use CSS generated-content cells with counters:
+  table.autonumber > tbody {
+    counter-reset: autonumbering;
+  }
+  table.autonumber > tbody > tr::before {
+    counter-increment: autonumbering;
+    content: counter(autonumbering);
+  }
+  table.autonumber > thead > tr::before {
+    content: ""№"";
+  }
+  table.autonumber > thead > tr::before, table.autonumber > tbody > tr::before {
+    display: table-cell;
+    padding: 0.2em;
+    border: 1px solid #AAA;
+    vertical-align: middle;
+    text-align: center;
+  }",1396243834,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I am not sure if T4315 and T12433 are resolved duplicates of this. I marked T4315 as a resolved duplicate of this, but now I am not sure. Maybe we can fix that problem too. 
+
+It would be nice if the fixed number column was automatically numbered (row numbering) without having to fill in anything in the column cells at all. 
+
+T12433 offers some automatic numbering JS that does this:
+https://en.wikipedia.org/wiki/User:Mike_Dillon/Scripts/autonumber.js 
+
+via class=""wikitable autonumber""
+
+The example given at T12433 is this: ""Example: say an author creates a chart that alphabetically lists all of the 535 members of the US Congress.  It would be laborious to list the numbers 1, 2, 3, … 533, 534, 535 near each of the 535 entries on the list.  And next time the list changes (at the next election, when names  are added to or subtracted from the list of Congress members), the author would have to repeat the laborious process of numbering the 535 entries on the  list all over again.""
+
+For T12433 the original poster's user page has moved to here:
+https://en.wikipedia.org/wiki/User:Joseph_A._Spadaro 
+
+The table wikitext he provided in T12433 produces this: 
+http://en.wikipedia.org/wiki/User:Timeshifter/Sandbox29 ",1439906511,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I am not sure if bug 2315 and bug 10433 are resolved duplicates of this. I marked bug 2315 as a resolved duplicate of this, but now I am not sure. Maybe we can fix that problem too. 
+
+It would be nice if the fixed number column was automatically numbered (row numbering) without having to fill in anything in the column cells at all. 
+
+Bug 10433 offers some automatic numbering JS that does this:
+[[User:Mike Dillon/Scripts/autonumber.js]]
+
+via class=""wikitable autonumber""
+
+The example given at bug 10433 is this: ""Example: say an author creates a chart that alphabetically lists all of the 535 members of the US Congress.  It would be laborious to list the numbers 1, 2, 3, … 533, 534, 535 near each of the 535 entries on the list.  And next time the list changes (at the next election, when names  are added to or subtracted from the list of Congress members), the author would have to repeat the laborious process of numbering the 535 entries on the  list all over again.""
+
+For bug 10433 the original poster's user page has moved to here:
+[[User:Joseph A. Spadaro]]
+
+The table wikitext he provided in bug 10433 produces this: 
+[[User:Timeshifter/Sandbox29]]",1357035993,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",%%%*** T4315 has been marked as a duplicate of this bug. ***%%%,1439906633,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",%%%*** Bug 2315 has been marked as a duplicate of this bug. ***%%%,1357034232,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.",*** Bug 40634 has been marked as a duplicate of this bug. ***,1356967180,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+And I'd say it works very well…! Thanks, Bartosz!
+I really hope it will be implemented widely soon, as it's ready to work!",1356561239,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I've created a proof-of-concept implementation using the sortEnd.tablesorter event $.tablesorter fires upon finishing sorting.
+
+The code is essentially five lines:
+```
+$('table.sortable th.unsortable.ordinal').each(function(i, th) {
+	var $th = $(th), $table = $th.closest('table');
+	$table.on('sortEnd.tablesorter', function() {
+		$table.find('tr td:nth-child('+ (th.cellIndex+1) +')').each(function(j, td) {
+			$(td).text( (j+1) );
+		});
+	})
+});
+```
+This means that for every column with class=""unsortable ordinal"" on the header cell inside a table with class=""sortable"", the code will re-fill it with consecutive numbers, starting at 1, when the table is sorted. This allows for columns which contain ordinal numbers (the original use case).
+
+The solution was discussed on pl.wikipedia's technical village pump[1][2] and is currently live in its common.js[3]. It's used on a few pages already, including the aforementioned [[pl:Miasta w Polsce (statystyki)]] and our help page with a list of interwiki codes, [[pl:Pomoc:Interwiki]].
+
+[1] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Poprawa tabeli w Miasta w Polsce (statystyki)]]
+[2] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Sortowanie tabeli]]
+[3] [[pl:MediaWiki:Common.js]], at the very bottom",1523379117,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I've created a proof-of-concept implementation using the sortEnd.tablesorter event $.tablesorter fires upon finishing sorting.
+
+The code is essentially five lines:
+```
+$('table.sortable th.unsortable.ordinal').each(function(i, th) {
+  var $th = $(th), $table = $th.closest('table');
+  $table.on('sortEnd.tablesorter', function() {
+    $table.find('tr td:nth-child('+ (th.column+1) +')').each(function(j, td) {
+      $(td).text( (j+1) );
+    });
+  })
+});
+```
+This means that for every column with class=""unsortable ordinal"" on the header cell inside a table with class=""sortable"", the code will re-fill it with consecutive numbers, starting at 1, when the table is sorted. This allows for columns which contain ordinal numbers (the original use case).
+
+The solution was discussed on pl.wikipedia's technical village pump[1][2] and is currently live in its common.js[3]. It's used on a few pages already, including the aforementioned [[pl:Miasta w Polsce (statystyki)]] and our help page with a list of interwiki codes, [[pl:Pomoc:Interwiki]].
+
+[1] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Poprawa tabeli w Miasta w Polsce (statystyki)]]
+[2] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Sortowanie tabeli]]
+[3] [[pl:MediaWiki:Common.js]], at the very bottom",1439922832,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","I've created a proof-of-concept implementation using the sortEnd.tablesorter event $.tablesorter fires upon finishing sorting.
+
+The code is essentially five lines:
+
+$('table.sortable th.unsortable.ordinal').each(function(i, th) {
+  var $th = $(th), $table = $th.closest('table');
+  $table.on('sortEnd.tablesorter', function() {
+    $table.find('tr td:nth-child('+ (th.column+1) +')').each(function(j, td) {
+      $(td).text( (j+1) );
+    });
+  })
+});
+
+This means that for every column with class=""unsortable ordinal"" on the header cell inside a table with class=""sortable"", the code will re-fill it with consecutive numbers, starting at 1, when the table is sorted. This allows for columns which contain ordinal numbers (the original use case).
+
+The solution was discussed on pl.wikipedia's technical village pump[1][2] and is currently live in its common.js[3]. It's used on a few pages already, including the aforementioned [[pl:Miasta w Polsce (statystyki)]] and our help page with a list of interwiki codes, [[pl:Pomoc:Interwiki]].
+
+[1] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Poprawa tabeli w Miasta w Polsce (statystyki)]]
+[2] [[pl:Wikipedia:Kawiarenka/Kwestie techniczne#Sortowanie tabeli]]
+[3] [[pl:MediaWiki:Common.js]], at the very bottom",1356540538,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+(In reply to comment #10)
+> Sure. If we're going to add this, it'll be part of the jquery.tablesorter
+> module.
+
+Thanks.
+
+I just looked into the code with hope that I could help a bit but I understand too little to see what's going on there ;) But I thought I'd ask if it could be like:
+1) search for a colmun with class ""fixed"",
+2) store it's order,
+3) sort the table as usually,
+4) recover the ""fixed"" column.
+
+Or simplified version, only for ordering numbers:
+1) sort table as usually
+2) search for a column with class ""ordering-numbers""
+3) fill the cells of the column with ordering numbers.",1348967706,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to comment #9)
+> Yes, let's say it's a ""new feature"" but I feel it's inseparable part of
+> ""wikitable sortable"" feature.
+> 
+
+Sure. If we're going to add this, it'll be part of the jquery.tablesorter module.",1348965938,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+Yes, let's say it's a ""new feature"" but I feel it's inseparable part of ""wikitable sortable"" feature.
+
+And yes, you're totally right with ""fixed"", thanks for clarification.",1348965787,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Rephrasing ticket summary.
+
+If I understand correctly you're looking for a way to let a column be fixed, unaffected by row re-ordering.
+
+That is not a bug with ""unsorted"", ""unsorted"" works as it should, many people rely on the way it works. I believe you're looking for a new feature, I'll call it ""fixed"" for now.",1348964712,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+The ""every row"" issue can be avoided using:
+ table.autonumber td:first-child
+…which still doesn't change the fact that IE6/7 don't deal with it.",1348952714,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","Also, this solution requires the class to be added in every row, instead of just to the header. I don't think this can be circumvented using CSS magic.",1348950369,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+Yes, that could be not only a workaround but a solution. Thanks, I didn't know about it!
+
+The counter property is supported in all major browsers (IE, FF, Opera, Chrome, Safari, maybe more). IE8 supports it only if a !DOCTYPE is specified.
+//source: http://www.w3schools.com/cssref/pr_gen_counter-increment.asp",1348950236,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","(In reply to comment #3)
+> It works for me on Mozilla Firefox 15.0.1. Not sure if other browsers support
+> it.
+
+CSS counters are supported by all modern (and even slightly old) browsers except for IE <= 7. http://caniuse.com/#feat=css-counters
+
+Unfortunately I think MW still supports IE 7?",1348948811,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","See this example: http://www.mediawiki.org/w/index.php?title=User:Ciencia_Al_Poder/Test&oldid=588713
+
+Use the provided CSS code on that page to display the static numbers on the first column, that remain untouched when the table gets sorted. You can add that CSS to your personal css page.
+
+It works for me on Mozilla Firefox 15.0.1. Not sure if other browsers support it.",1348948350,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","**winne2i** wrote:
+
+Well, that was only just an immediate conclusion.
+
+Speaking precisely, rows of one (or more) specified column(s) should not be sorted. Most commonly it will be the 1st column as usually there are ordering numbers – e.g. list of cities in Poland* http://pl.wikipedia.org/wiki/Miasta_w_Polsce_(statystyki) – while sorting by inhabitants, area, voivodeship, (…) the cells in 1st column with ordering numbers also get sorted while they shouldn't. The 1st column with ordering numbers informs quickly e.g. ""Gdańsk is 6th in a row in terms of number of inhabitants"" or ""there are 125 cities with area <5 km²"".
+
+Ordering numbers just should be in order all the time regardless of sorting rows – otherwise they just become nonsense.
+
+*) It's big article, may load long. In this article I tried to make separate table with ordering numbers that would not be sorted but that looks like… nothing good. The feature is craved.",1348945144,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"jquery.tablesorter: Add support for a ""fixed"" column of row numbers.","When you sort, it's not a column what gets sorted, but the rows of the table, using the selected column as the sort key. The ""unsortable"" stands for ""do not sort using this column as a sort key"".
+
+Could you please provide a use case for this (one real example where it will be used)?
+
+[ changing from bug to enhancement]",1348934030,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-forssl3t3nzyfxttmbjs,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","For consistency, when editing, the 'Cancel' link should really be a button along with the other buttons on the line, since it is an action like the rest of them even if it isn't directly tied to the form itself.
+
+The help link should also probably be removed entirely from at least the default installation, as no help pages actually come with said installation and thus the link doesn't go anywhere. Expecting wikis at this point to write their own editing help pages is also pretty silly, as there tend to already be much more thorough such pages on other wikis such as enwp, meta, and similar, and new projects can merely refer to those instead if needed. For any projects using the WikiEditor extension, though, having a link at all is redundant anyway as the toolbar the extension provides includes a navigable help menu directly in it.
+
+Ignore the other stuff, but the line of buttons would look something like on this: http://commons.wikimedia.org/wiki/File:Enwp_edit_20120917_with_even_less_stuff.png
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1348853520,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-msazj7jjbjrha34imxrt,task_description,declined
+"""Cancel"" link when editing a page should either be a button or not be there at all.","Okay, so I'm inclined to say this ain't worth doing. Closing.",1391019141,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","(In reply to comment #12)
+> If we need to be messing with the buttons, I'd say we need to be putting
+> additional emphasis on the ""Save page"" button rather than further emphasizing
+> ""Cancel"".
+
+There are some bold plans about doing just that, Steven and Jon (CC'd) know more about them than me. I think you can play with a reasonably current demo at http://ee-flow-extra.instance-proxy.wmflabs.org/wiki/Main_Page (use the ""Agora styling"" menu on the left).",1391014026,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","**skizzerz** wrote:
+
+Having Cancel be a link instead of a button is not unprecedented in designs, and in fact would be preferred for a couple of reasons:
+
+1. Making them both buttons would put extra emphasis on the Cancel action, making it more likely that users will accidentally click it and wipe their edit.
+2. If a user does not wish to actually edit, and the Cancel link is removed entirely, they may not know that they can also cancel the edit by clicking another link elsewhere (does anybody have info on how many times the cancel link is clicked vs how many edits are cancelled via other means?)
+
+If we need to be messing with the buttons, I'd say we need to be putting additional emphasis on the ""Save page"" button rather than further emphasizing ""Cancel"".
+
+Interesting further reading on the topic: http://www.lukew.com/ff/entry.asp?571=",1390929238,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","**andnlnbn18** wrote:
+
+Can I work on it?",1390925233,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.",Minor update!,1363750179,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","(In reply to comment #8)
+> The other consideration that should be made here is that MediaWiki core may end
+> up using different styling/button positions than VisualEditor (which currently
+> has one large, green ""Save page"" button _above_ the textarea).
+
+Having a button above the text area is not unprecedented - there was a labs feature that added a 'Publish' and a 'Cancel' button at the top right above the textarea. I've used it to cancel before, since it's in a convenient and expected place; dunno that I've ever used the link by the usual buttons.
+
+It really stands out with the VE sandbox, but that's the model both VE and the current editor should be following, regardless of positioning - a cancel button is intuitive. Having to click on the 'page' tab is not, and yet that is still more so than a text link that gets lost amidst the other text.",1349025940,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","The other consideration that should be made here is that MediaWiki core may end up using different styling/button positions than VisualEditor (which currently has one large, green ""Save page"" button _above_ the textarea).",1348933546,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","On the contrary, the save is the one that needs to be distinct, not the cancel, or that will really confuse people. Yes, different systems use different orientations, but it generally still works just fine - partly just because people are used to it at this point, but also because one button is consistently distinct: the one people care about. The save.
+
+The english wikipedia was right to bold that one. It should be bolded on all of them.
+
+And the cancel link should really be a button if it is going to be there at all.",1348908193,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","If there were only two actions (""save"" and ""cancel""), even then.  The positioning of the actions is important: (in LtR languages) left actions are ""backwards"" and right side actions are ""forwards"".  We are not talking about the ""word as written"" but rather the ""word as perceived"".  
+
+There have been about 4234523452345234532 studies done where human beings ignore the text ""cancel"" and simply click the button because they think it means something totally different.",1348903833,PHID-USER-ua75tm4u7cmt4mdof6vb,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","(In reply to comment #4)
+> I disagree that the ""cancel"" link *must* be a button.  If there were different
+> visual treatments to the various buttons, then it could work as a button with
+> an alternate treatment.
+> 
+> However, since all buttons have the same visual treatment, then the ""destroy""
+> action must have different treatment.  
+
+Why does it need to be different? The meaning of 'cancel' is pretty unambiguous.",1348903354,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","I disagree that the ""cancel"" link *must* be a button.  If there were different visual treatments to the various buttons, then it could work as a button with an alternate treatment.
+
+However, since all buttons have the same visual treatment, then the ""destroy"" action must have different treatment.  Ergo, it shouldn't be a button.
+
+This should be closed unless the buttons get different visual treatments.",1348888455,PHID-USER-ua75tm4u7cmt4mdof6vb,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","The following html should work for this:
+
+<a href=""/wiki/pagename"" title=""Pagename"" id=""mw-editform-cancel""><input type=""button"" name=""Cancel"" value=""Cancel""/></a>",1348886873,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.",Okay.,1348867653,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"""Cancel"" link when editing a page should either be a button or not be there at all.","You're conflating issues here. This bug should _only_ be about the ""Cancel"" link. Anything else (such as the ""Editing help"" link and its interaction with the WikiEditor toolbar) should be filed as separate bugs.
+
+I'm changing this bug's summary from ""'Cancel' link when editing should be a button, and 'Editing help' link is silly"" to """"Cancel"" link when editing a page should be a button"".",1348867597,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-msazj7jjbjrha34imxrt,task_subcomment,NA
+"VisualEditor: In link inspector, when you hover over a dropdown list item it should highlight (blue background), not only when using keyboard navigation","Suggested by a user.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1346774100,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-t3ipmvj7oq3ez2aqp4mq,task_description,resolved
+"VisualEditor: In link inspector, when you hover over a dropdown list item it should highlight (blue background), not only when using keyboard navigation",Now in master.,1354322608,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-t3ipmvj7oq3ez2aqp4mq,task_subcomment,NA
+"VisualEditor: In link inspector, when you hover over a dropdown list item it should highlight (blue background), not only when using keyboard navigation",Hover state added in https://gerrit.wikimedia.org/r/36247,1354309419,PHID-USER-pun3sjvg3cemjzbgyo2t,True,PHID-TASK-t3ipmvj7oq3ez2aqp4mq,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,"The current wikitext escape algorithm adds excessive nowiki tags around quote marks.  While these are semantically correct and useful, for existing code, it introduces dirty diffs with the source wikitext.
+
+This is not a problem if unmodified DOM subtrees are serialized using original wikitext source.  But, we dont this right now.
+
+Till such time, the code needs fixing to use heuristics to eliminate nowikis where the parser can figure out the right parse without nowikis.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1344977760,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-zgw6ir3d7s2sg2njimma,task_description,resolved
+Minimize unnecessary nowiki tags around quote marks,"We are using selective serialization by default, so this is no longer a major issue in practice.",1370993167,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,"(In reply to comment #3)
+> Note also that through continuous edits more cruft might be added around the
+> same source text, and at some point ugly visual changes do occur.
+
+This is VisualEditor bug 47434, which is fixed in VE master, but not yet deployed.",1366605485,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,"Note also that through continuous edits more cruft might be added around the same source text, and at some point ugly visual changes do occur.
+
+See the bold text at http://en.wikipedia.org/w/index.php?title=Yolanda_Ordaz_de_la_Cruz&oldid=551330208#Impact . It appeard through several edits, each one adding a bit.
+
+See the diff of the fix:
+
+http://en.wikipedia.org/w/index.php?title=Yolanda_Ordaz_de_la_Cruz&diff=551330391&oldid=551330208",1366483604,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,*** Bug 47442 has been marked as a duplicate of this bug. ***,1366470553,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+Minimize unnecessary nowiki tags around quote marks,"Since quote heuristics are relatively complex, I guess the simplest and most reliable solution to figure out if escaping for quotes in a line is really needed would be to round-trip test the output for that line.",1344978834,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-zgw6ir3d7s2sg2njimma,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work","The VisualEditor extension currently requires a Parsoid instance to handle wikitext (cf. $wgVisualEditorParsoidURL in VisualEditor.php). This makes installing and using the extension very difficult (or impossible) for third-party users wishing to use the extension with their MediaWiki installations.
+
+Ideally, calling out to an external Parsoid instance should not be necessary.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1342672800,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-cxha3l6ahwyau5brwb5g,task_description,resolved
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work",Closing in favour of #parsoid-php.,1555119418,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work","Since modern web-applications are become ""stacks"" (i.e. microservices) I don't think this should be done....",1522382744,PHID-USER-g5rqg2k7irztdonlursm,False,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work",See https://www.mediawiki.org/wiki/Parsoid/Roadmap for our latest plans on this. Our plan is to support HTML-only wikis with VisualEditor without any dependency on Parsoid.,1359411901,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work",Mass-moving bugs into the new 'Parsoid' product.,1344281154,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work","Our plan is to port Parsoid to a C library and interface it to PHP as an extension and (for shared hosting) as a near-static binary following Tim's strategy for Lua. We have some issues to address in the JS implementation before we embark on that, so don't expect that to happen before October.
+
+We could later also port Parsoid to pure PHP, but PHP's less-than-stellar performance for memory-heavy workloads would make this only useful for very small wikis. See http://shootout.alioth.debian.org/u32/performance.php?test=binarytrees for a fun memory-heavy benchmark.",1342721922,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work",Re-wording to be specific. I know Gabriel (and Tim Starling) are already looking at solutions to this issue.,1342719453,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cxha3l6ahwyau5brwb5g,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)","Currently just goes to latest revision, which is irritating.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1341265200,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jzhc7bilulnwxwe466rc,task_description,resolved
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)","It appears I didn't git-add the fix for this bug (I fixed several small issues at once).
+
+Since  I5bc24e0cbdf01b3704d4ccb0 is already merged, pushed for review separately:
+
+I7d702a3eb1f9ce23a5e3c9e846b00da5cead386e.",1344314009,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)",eh.. I5bc24e0cbdf01b3704d4ccb0.,1344312053,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)",Fixed in a better way in  I82e051b6f25f7e71bc7fbfcbd8e9b14ecc8870af (which fixed any and all edit-link related issues instead of hard-coding exceptions for oldid).,1344311999,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)","Fixed in I4b8e2e77ddeb3d38144a3c96790660e86d57a82d
+
+https://gerrit.wikimedia.org/r/#/c/17920/",1344295522,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+"VisualEditor: ""Edit Source"" link should preserve original query parameters (such as oldid)",*** Bug 38769 has been marked as a duplicate of this bug. ***,1343674164,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jzhc7bilulnwxwe466rc,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340654640,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_description,resolved
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"Not WORKSFORME; we actively did something that made this work (just, we didn't notice at the time). :-)",1362436146,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"(In reply to comment #4)
+> Behaviour
+> 
+> 1. Enter ""RFC 1234"" & save; it doesn't auto-nowiki, so you get a page with
+> ""RFC
+> 1234"" as wikitext which automatically links.
+> 2. Edit again in VE; you get a link which you could edit.
+This is no longer true. The behavior on master is that the link gets alienated.
+
+> 3. Saving this without changing causes the link to be unchanged (as
+> expected).
+> 4. Saving this with a different link doesn't convert 
+You can't do that, because it's an alien. You can remove it as a unit. Bolding it seems to work too, although there's a different bug that causes text to be cut off there, will investigate.
+
+> 5. Enter ""<nowiki>RFC 1234</nowiki>"" in wikitext editor, save.
+> 6. Edit in VE; you get some text link in an alien node.
+> 7. Saving this causes the link to be unchanged (as expected).
+> 
+Also alienated.
+
+Entering ""RFC 2822"" into an existing paragraph causes Parsoid to <nowiki> the entire paragraph.
+
+> Fixes for unexpected behaviours above:
+> 
+> 1. This feels a little odd; should magic links be allowed, or should Parsoid
+> (un?)magically wrap them in <nowiki>s?
+It does this now, although the entire paragraph is wrapped.
+
+> 2. This probably should be alienated in DM.
+It is now.
+
+> 4. If the link won't be alienated (i.e., option 2 is not followed), we'll
+> need
+> to special-case this kind of link and re-generate [[]]s around it (? in DM).
+Moot, because we have alienation working.
+
+Closing this bug as WORKSFORME. I saw a few weird issues while testing this, but they seem to be Parsoid serialization bugs not directly related to this bug, and I may have an out-of-date library again.",1362092338,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,Pulling from release; we won't get to this.,1355168491,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,Think there are still issues to resolve in DM (either options 1. or 2.) - Roan?,1354927639,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,https://gerrit.wikimedia.org/r/37496 has a fix for this -- but there is more to be tested and done.  Work-in-progress.  Feel free to report additional failure test cases here.,1354915694,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"Parsoid HTML+RDFa output for ""RFC 1234"" as wikitext input is:
+
+<a typeof=""mw:ExtLink/RFC"" href=""//tools.ietfs.org/html/rfc1234"" rel=""mw:ExtLink/RFC"" data-parsoid=""{&quot;tsr&quot;:[0,8],&quot;dsr&quot;:[0,8]}"">RFC 1234</a>",1354899393,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"Behaviour
+
+1. Enter ""RFC 1234"" & save; it doesn't auto-nowiki, so you get a page with ""RFC 1234"" as wikitext which automatically links.
+2. Edit again in VE; you get a link which you could edit.
+3. Saving this without changing causes the link to be unchanged (as expected).
+4. Saving this with a different link doesn't convert 
+5. Enter ""<nowiki>RFC 1234</nowiki>"" in wikitext editor, save.
+6. Edit in VE; you get some text link in an alien node.
+7. Saving this causes the link to be unchanged (as expected).
+
+Fixes for unexpected behaviours above:
+
+1. This feels a little odd; should magic links be allowed, or should Parsoid (un?)magically wrap them in <nowiki>s?
+2. This probably should be alienated in DM.
+4. If the link won't be alienated (i.e., option 2 is not followed), we'll need to special-case this kind of link and re-generate [[]]s around it (? in DM).",1354852310,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,"<nowiki>RFC 12234</nowiki> round-trips just fine in Parsoid (try it at http://parsoid.wmflabs.org/_rtform/), so I think this is a VE bug. Guessing the module, please change as needed.",1343177484,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,Think this issue is going to be fixed by Parsoid as and when this is done. :-),1343175758,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip,Magic links: RFC xxx stuff,1340654663,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-tyw6vxwg2iqhnxtqi2eo,task_subcomment,NA
+Support for creating and editing definition-lists in VisualEditor,"As discussed.
+
+See also:
+* {T62411}
+* {T54399}
+* {T57797}",1340654220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2yyksazxkjyor5p6mer4,task_description,open
+Support for creating and editing definition-lists in VisualEditor,"Note that VE supports ""bulletizing"" lines inside a definition list and they end up properly indented.
+
+For example, using VE to highlight 1, 2, and 3 on a page with the following wikitext
+  : 1
+  : 2
+  : 3
+and clicking ""Bullet list"" results in
+  :* 1
+  :* 2
+  :* 3
+
+Seems like this is a good start on some sort of broader support for arbitrary indention.",1415816927,PHID-USER-ogbcrxm45oo3n3xe5q25,True,PHID-TASK-2yyksazxkjyor5p6mer4,task_subcomment,NA
+Support for creating and editing definition-lists in VisualEditor,*** Bug 67751 has been marked as a duplicate of this bug. ***,1404964562,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-2yyksazxkjyor5p6mer4,task_subcomment,NA
+Support for creating and editing definition-lists in VisualEditor,"I had a problem caused by the broken definition lists. If you have a maths equation aligned as a block using a dl ie
+
+:<math>e^{i \pi}</math>
+
+then you can't add a non indented paragraph after it. https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_2#Trying_to_add_a_line_after_an_equation
+
+This has some impact on Bug 61051 about how MathJax equations are aligned.",1396821462,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-2yyksazxkjyor5p6mer4,task_subcomment,NA
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,"From a VE test page:
+
+Perhaps a different colour font as you are editing...so you could keep track of what you're doing (TG)
+
+Not sure if we'd want to do this.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=60535",1340643120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ovut64wzzg2st7xdxqrv,task_description,open
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,*** Bug 65247 has been marked as a duplicate of this bug. ***,1402329075,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ovut64wzzg2st7xdxqrv,task_subcomment,NA
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,"(In reply to comment #2)
+> Perhaps the way to do this is to use the same visual clues that are used when
+> using revision tracking in OOo Writer, MS Word etc. Particularly if they use
+> the same markings as each other.
+
+Word does a thin line (1px wide, maybe) down the outer column of a page to indicate changed lines, in both the desktop and print versions, I believe, by default.",1376959499,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-ovut64wzzg2st7xdxqrv,task_subcomment,NA
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,"Perhaps the way to do this is to use the same visual clues that are used when using revision tracking in OOo Writer, MS Word etc. Particularly if they use the same markings as each other.",1375716176,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-ovut64wzzg2st7xdxqrv,task_subcomment,NA
+VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding,*** Bug 37903 has been marked as a duplicate of this bug. ***,1345669770,PHID-USER-mpfqwllylfkzpcgkdkvc,True,PHID-TASK-ovut64wzzg2st7xdxqrv,task_subcomment,NA
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,"Screenshot of iPad simulator
+
+iOS 5.1 simulator on Mac OS X. Screenshot attached.
+
+iOS's selection handles overlap the arrow button we add, so it can't be clicked on.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9311}",1340472240,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-byqi7qvbtypqe3qpqvys,task_description,invalid
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,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.,1399324094,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-byqi7qvbtypqe3qpqvys,task_subcomment,NA
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,"Regarding Android, I've raised a similar issue at Bug 51270.",1373682808,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-byqi7qvbtypqe3qpqvys,task_subcomment,NA
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,"Something very similar happens on my Android phone. However, if I blur the editor and refocus it, the first cursor I get upon focusing doesn't have a selection handle, but if I then move the cursor, a selection handle appears.",1363054703,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-byqi7qvbtypqe3qpqvys,task_subcomment,NA
+VisualEditor: Selection popup arrow is overlapped by selection controls on iPad,"Moving to ""Mobile"" component.",1354811640,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-byqi7qvbtypqe3qpqvys,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","Take a two-word link (e.g. [[Example link]]). Use the VE inspector to select ""Example"" and press the remove-formatting button. Repeat with ""link"". Now the text is ""Example <a href='...'> </a> link"", which is illegal wikitext, and renders as if there's no link there.",1340388420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_description,open
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",">>! In T39835#1170062, @NicoV wrote:
+> There's also the situation with nowiki surrounded by bold or italic formatting: [[2008|''<nowiki/>'']] in [[ https://fr.wikipedia.org/w/index.php?title=Saint-Florent-des-Bois&diff=prev&oldid=113366483 | this edit ]].
+
+{T95730}.",1429617085,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",There's also the situation with nowiki surrounded by bold or italic formatting: [[2008|''<nowiki/>'']] in [[ https://fr.wikipedia.org/w/index.php?title=Saint-Florent-des-Bois&diff=prev&oldid=113366483 | this edit ]].,1427888424,PHID-USER-o34e5i3eq4nstbvcf26w,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",*** Bug 54266 has been marked as a duplicate of this bug. ***,1380072033,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","Just FYI, we have a user at en.wp stating <<I was going to give examples of what turns out to be bug 37835. As the bug is a year old, looks like this won't be fixed and therefore no use in giving the examples.>> :/",1377770349,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",*** Bug 51877 has been marked as a duplicate of this bug. ***,1374879481,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","I don't know if it is related to this bug, but it is no longer possible to select only part of a link. Previously you could unlink the second word separately for example. See also bug 51531 and bug 50945",1374066259,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","Change 74084 had a related patch set uploaded by Catrope:
+[WIP] Unwrap whitespace-only links
+
+https://gerrit.wikimedia.org/r/74084",1374014852,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",Pulling from this milestone as it's a lot of work for a small feature.,1366141216,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","(In reply to comment #4)
+> We probably shouldn't allow users to create whitespace-only links, because
+> they
+> don't render correctly in HTML let alone wikitext. I'm going to work on a
+> change that strips whitespace-only links in the converter.
+This part depends on bug 46464.",1364433622,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","<a> </a> doesn't actually render as a clickable link in Firefox. Even if you set text-decoration:underline; on it, it still doesn't render and can't be clicked. However, <a>&nbsp;</a> does behave ""correctly"".
+
+We probably shouldn't allow users to create whitespace-only links, because they don't render correctly in HTML let alone wikitext. I'm going to work on a change that strips whitespace-only links in the converter.",1363987143,PHID-USER-fovtl67ew4l4cc3oeypc,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","(In reply to comment #2)
+> (In reply to comment #0)
+> >  ""Example <a href='...'> </a> link"", which is illegal wikitext.
+> 
+> ... because [[Foo| ]] will trigger the pipe-trick and turn it into [[Foo|Foo]].
+
+Actually, it doesn't (current master, not using Tidy).
+
+<pre>
+* [[Foo]]
+* [[Foo|]]
+* [[Foo| ]]
+* [[Foo|<nowiki></nowiki>]]
+* [[Foo|<nowiki> </nowiki>]]
+</pre>
+
+Expands to:
+
+* [[Foo]]
+* [[Foo|Foo]]
+* [[Foo| ]]
+* [[Foo|<nowiki></nowiki>]]
+* [[Foo|<nowiki> </nowiki>]]
+
+Renders as:
+
+<ul><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo"">Foo</a>
+</li><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo"">Foo</a>
+</li><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo""> </a>
+</li><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo""></a>
+</li><li> <a href=""/wm-git/mediawiki/alpha/index.php/Foo"" title=""Foo""> </a>
+</li></ul>
+
+Which means a loose space works, and with <nowiki> it even works when empty. Good news :)",1349132566,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed","(In reply to comment #0)
+>  ""Example <a href='...'> </a> link"", which is illegal wikitext.
+
+... because [[Foo| ]] will trigger the pipe-trick and turn it into [[Foo|Foo]].",1349132335,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+"A link can span whitespace but won't be displayed, so cannot be edited or noticed",Mass-moving items into VisualEditor product,1340402731,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-w22wdpvzx7smcv2ec6cy,task_subcomment,NA
+migrate MedaWiki from using BiDirectional characters by properly embedding any item using directionality syntax,"**Author:** `gangleri`
+
+**Description:**
+Hi! It is long time ago since Nikerabbit installed Goylem a RTL testwiki. At that time I suggested the usage of BiDirectional characters to stabilize the common look and feel of pages as recent changes, etc.
+
+It should be possible to obtain the same result by properly embed all objects and the delimiters (spaces or whatsoever) with directionality syntax.
+
+An example is available at bug 36803#0
+and http://en.wikipedia.org/?oldid=492307285#bugzilla ,
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1336886760,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-eype2avbpoowyttmdlqv,task_description,resolved
+migrate MedaWiki from using BiDirectional characters by properly embedding any item using directionality syntax,"I'll allow myself to close it.
+
+In essence, VisualEditor now allows to edit template parameters comfortably separately from the rest of the text, and also includes a lang/dir setting (both made mostly by @mooeypoo; thanks!)
+
+Some articles might still be using bidirectional control characters (probably not much in the English Wikipedia, but quite a lot in the Hebrew Wikipedia), but that's a matter for editors and not developers.",1440920059,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-eype2avbpoowyttmdlqv,task_subcomment,NA
+migrate MedaWiki from using BiDirectional characters by properly embedding any item using directionality syntax,"I definitely have plans to introduce fine-grained control of directionality, maybe in the Visual Editor age and maybe even earlier (see https://www.mediawiki.org/wiki/Visual_editor/Bidirectional_text_requirements ). But I'm not sure that I understand what are you referring to.
+
+<span dir=""rtl/ltr""> doesn't solve everything in a heavily mixed-directionality environment. For example, a title in an RTL wiki can be LTR. <bdi> would be more comprehensive than span, but the support for it is not yet completely stable, neither in the browsers nor in MediaWiki (see bug 31817).",1336888426,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-eype2avbpoowyttmdlqv,task_subcomment,NA
+VisualEditor: Ctrl + K should trigger link inspector,"Pressing Ctrl + K doesn't work in chrome16/win7. It just produces a ? in the url bar instead with a dropdown option saying
+
+<Enter query> - Google search
+
+Repeated pressing does not solve the issue either.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1335243600,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_description,resolved
+VisualEditor: Ctrl + K should trigger link inspector,"**orbit** wrote:
+
+Fixed in:
+https://gerrit.wikimedia.org/r/12977
+Will release soon.",1340671640,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_subcomment,NA
+VisualEditor: Ctrl + K should trigger link inspector,Mass-moving items into VisualEditor product,1340402766,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_subcomment,NA
+VisualEditor: Ctrl + K should trigger link inspector,"I can confirm this issue on Ubuntu 12.04, Chrome 19.0.1084.56.",1340396406,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_subcomment,NA
+VisualEditor: Ctrl + K should trigger link inspector,"WORKSFORME on Ubuntu 12.04, Google Chrome 19.0.1084.56.
+
+Could you check if it is still happening on Windows 7?",1340332908,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-bq2wcgmbdrspfxuefmjq,task_subcomment,NA
+VisualEditor: Sticky selection popup,"Playing around with text selection a bit I was able to find a ""sticky"" popup.
+
+Environment: Win7, Chrome 16
+
+What I did:
+1. Select some text
+2. Click on the small arrow that appears above the selected text
+3. Select the ""create link"" icon
+4. Neither input title for the link, nor close the popup
+5. Instead take the caret somewhere else and select some other word
+6. Repeat 4 and 5 a few times
+
+Soon, the following js error was generated:
+
+Uncaught Invalid annotation error. Can not find non-annotation data in character.
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:54
+ve.dm.DocumentNode.getIndexOfAnnotation
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:54
+ve.ce.Surface.removeInsertionAnnotation
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:103
+ve.ce.Surface.annotate
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:102
+ve.ui.LinkInspector.onClose
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:133
+ve.ui.Inspector.close
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:123
+ve.ui.Context.closeInspector
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:129
+(anonymous function)
+bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:122
+jQuery.event.dispatch
+load.php:49
+jQuery.event.add.elemData.handle.eventHandle
+load.php:42
+
+Plus, after a reload; I did the following:
+1. Select text
+2. Click on the arrow above it
+3. Not click any icon but instead take the caret elsewhere. This should (as I see it) have ideally closed the popup, but it didn't.
+4. I clicked on bold and italics but that does nothing (since because the caret has moved there is currently no text selected).
+5. Since the popup is still open, clicking on the link icon opens the link window, and closing it finally closes the popup.
+
+If the first 4 steps are reproduced and step 5 is replaced by clicking on the tickmark instead of the close, nothing happens since no text is selected. The click neither inserts a link into the page, nor closes the popup. After this, even clicking on the close doesn't close the popup. The caret can be moved and other text selected, but that just brings up the arrow and popup again. The previous popup still sticks. The popup finally went away on selecting an existing link in the text and clicking on the link icon in the toolbar. This made the link title appear in the popup and the close button finally worked.
+
+After another reload, I tried the following:
+1. Select text
+2. Click on the arrow
+3. Select some other word. Now, selecting some other word automatically moves the popup to be near the new selection, i.e the popup is already open for the new selection if the popup for the original selection isn't closed before making a new selection. Also, after step 2, since the popup is open, nothing below the popup can be selected without closing the popup first.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1335241260,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xiaw7dpykpv6pphvabfq,task_description,resolved
+VisualEditor: Sticky selection popup,"This was partly fixed a few commits ago. 
+Though, context icon was not being properly cleared when the editor loses focus.
+Steps to reproduce: 
+
+Make a selection (Icon appears)
+
+Click anywhere outside of the editor. ( lose selection, icon is stuck )
+
+Fixed in https://gerrit.wikimedia.org/r/16794",1343345020,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-xiaw7dpykpv6pphvabfq,task_subcomment,NA
+VisualEditor: Sticky selection popup,Mass-moving items into VisualEditor product,1340402736,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xiaw7dpykpv6pphvabfq,task_subcomment,NA
+VisualEditor: Sticky selection popup,"Btw, the second, third and fourth tests also produced some js-errors; but I forgot to note them down.",1335241495,PHID-USER-4bjsher5mqcoikeqnnec,False,PHID-TASK-xiaw7dpykpv6pphvabfq,task_subcomment,NA
+VisualEditor: All annotations are broken,"Editing annotations is broken in VisualEditor. Selecting some text and then clicking either Bold, Italics, Link, or Clear formatting has no effect. Tested in Chrome, Firefox 11, IE9, and Safari.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1334532660,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-klisuk3f7xmyrpypvmbw,task_description,resolved
+VisualEditor: All annotations are broken,Fixed in new version.,1340403982,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-klisuk3f7xmyrpypvmbw,task_subcomment,NA
+VisualEditor: All annotations are broken,Mass-moving items into VisualEditor product,1340402751,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-klisuk3f7xmyrpypvmbw,task_subcomment,NA
+VisualEditor: All annotations are broken,"(In reply to comment #0)
+> Editing annotations is broken in VisualEditor. Selecting some text and then
+> clicking either Bold, Italics, Link, or Clear formatting has no effect. Tested
+> in Chrome, Firefox 11, IE9, and Safari.
+
+What do you mean by annotations? I'm confused.",1340396215,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-klisuk3f7xmyrpypvmbw,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","Accessing http://www.mediawiki.org/ as a logged-in user with Konqueror 4.8.1, every page pops up a JavaScript alert: ""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1334440320,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_description,resolved
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""",777preethi: Please see https://www.mediawiki.org/wiki/How_to_report_a_bug and create a new ticket with sufficient information to reproduce your setup. Thank you in advance!,1391610944,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","**777preethi** wrote:
+
+This error is coming on some clicks.
+
+**Attached**: {F9202}",1391598197,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","This seems to have been fixed at least on mediawiki.org as messages appear no more.
+
+> [...]
+>   I understand that the purpose of the ResourceLoader effort was to minimize
+> JavaScript loading and execution; the running of the Visual Editor's code on a
+> normal page view would suggest that something's amiss here.
+
+I assume this has either been dealt with or is not important.",1353558325,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","(In reply to comment #13)
+> The problem is that KHTML's Range implementation is missing some constants
+> (required by DOM Level 2 Range spec) that Rangy expects. I've relaxed the
+> relevant tests in Rangy for the upcoming version 1.3 to work around this. [...]
+
+I've read and appreciate it; I just wanted to answer Roan's questions.
+
+  I understand that the purpose of the ResourceLoader effort was to minimize JavaScript loading and execution; the running of the Visual Editor's code on a normal page view would suggest that something's amiss here.",1347628110,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","**timdown** wrote:
+
+Tim,
+
+The problem is that KHTML's Range implementation is missing some constants (required by DOM Level 2 Range spec) that Rangy expects. I've relaxed the relevant tests in Rangy for the upcoming version 1.3 to work around this. See 
+
+https://code.google.com/p/rangy/issues/detail?id=113
+
+I created a bug on the KHTML bug tracker (https://bugs.kde.org/show_bug.cgi?id=301871) but since it has been so far ignored, the best solution is for MediaWiki to use a newer version of Rangy. I would be happy to do a new 1.2 release with this fix while 1.3 is still in alpha.",1347528439,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","(In reply to comment #10)
+> The only code I see adding Rangy to the page is in
+> SpecialVisualEditorSandbox.php, and that code is only run on, you guessed it,
+> Special:VisualEditorSandbox.
+
+> Given that this only happens when logged in, do you have a user script or
+> gadget enabled that uses rangy maybe?
+
+I don't have any user scripts on mediawiki.org; the gadgets section of the preferences list as enabled:
+
+- Edittools
+- WMF Project Status Helper
+- <gadget-enwp-boxes>
+
+Disabling all of them doesn't get rid of the Rangy message.",1347483158,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","**timdown** wrote:
+
+Roan: There are a couple of Chrome plugins I've heard of that use Rangy, so it's possible.
+
+Regardless of the specifics of this bug for MediaWiki, it's a general problem for Rangy. A minor oversight in KHTML's Range implementation is responsible for the error message, so I will be fixing Rangy to be less pedantic. The bug is here:
+
+https://code.google.com/p/rangy/issues/detail?id=113",1339631061,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","The only code I see adding Rangy to the page is in SpecialVisualEditorSandbox.php, and that code is only run on, you guessed it, Special:VisualEditorSandbox.
+
+Given that this only happens when logged in, do you have a user script or gadget enabled that uses rangy maybe?",1339609166,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","**timdown** wrote:
+
+Rangy's author here.
+
+This could be a Rangy bug, or at least something Rangy can address. Rangy checks for the existence of all of the standard DOM Level 2 Range methods to determine whether Range is properly supported by the browser so it's possible KHTML is missing one or more of those.
+
+I'll look into it.",1339607862,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""",Did you quit and start a new instance of Konqueror after changing the setting?,1334456407,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","It's set at ""WebKit"" by default for me.
+
+No visible error messages if I switch to ""KHTML"", either on http://www.mediawiki.org (logged in) or http://translatewiki.net (logged out).",1334452311,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","What's your engine set to?  With ""WebKit"" I see no problems as well, they occur with ""KHTML"" (the default setting).",1334451827,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","Konqueror 4.8.2 ""release 491"" on same VM .... also no problems visible at http://www.mediawiki.org/ when logged in.",1334449628,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","Tested Konqueror 4.7.2 ""release 5"" (openSUSE 12.1), no problems on home page (or even on Special:VisualEditorSandbox). Trying an update to KDE 4.8...",1334446321,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","(In reply to comment #1)
+> Does it also happen on test2 (Also 1.20wmf1) or any other projects?
+
+Not on test2.wikipedia.org, but on translatewiki.net (as an anonymous user).
+
+(In reply to comment #2)
+> Only extension I can find using the 'rangy' library is VisualEditor, which
+> shouldn't be loading anything on the home page...
+
+It occurs already on the Special:UserLogin ""Login successful"" page (""Anmeldung erfolgreich"").",1334445982,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""","Only extension I can find using the 'rangy' library is VisualEditor, which shouldn't be loading anything on the home page...",1334442862,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"""Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented""",Does it also happen on test2 (Also 1.20wmf1) or any other projects?,1334440806,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-d5x4qtlwe24swelvcnf7,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","In pages such as Special:LonelyPages I would love to have an easy to access form which allowed filtering by namespace (à la Special:Allpages). Since MW 1.18, all $wgContentNamespaces are included in the default listing, but I think it would be nice to have some extra filtering.
+
+I've played a bit, by adding a $namespace parameter extracted from $wgRequest->getInt( 'namespace' ), but I would need some guiding about reusing it in more Special pages (for instance, also in WantedPages) and prepare a patch if this enhancement is considered interesting enough.
+
+= Additional context
+Spun out of T170687:
+
+It would be useful on many of the pages listed above in T170687#3439746
+
+E.g. 
+Special:ShortPages and Special:DeadendPages could then be used with the Help: and Project: namespace to find things to cleanup or merge
+Special:LongPages could then be used with the usertalk namespace to find people to nag to archive their overwhelming talkpages.
+Special:AncientPages could then be used with the Help: and Mediawiki: namespace to find things to update or reconsider the defaults.
+
+Note: Special:Random already has this functionality, similar to solution (f) but using full namespace names, per mw:Help:Random_page e.g. full list at https://en.wikipedia.org/wiki/Wikipedia:Random
+
+= Unknowns
+[] Some design for how the filters should look. Tabs? A search form? A drop down? Is this covered in the UI standards spec?
+[] More input
+
+",1333731000,PHID-USER-af2fdb5prucep2ihmjqc,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_description,open
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","> Some design for how the filters should look. Tabs? A search form? A drop down? Is this covered in the UI standards spec?
+
+
+I've seen two different kinds of namespace filters on special pages:
+1. In `Special:Contributions` and some other pages there's a dropdown that allows you to choose just one:
+{F58011403}
+2. In `Special:Search` there's a dropdown that allows you to choose more namespaces:
+{F58011430}
+
+So the second have more options but I'm not sure are they needed here. And most other special pages have the first dropdown.",1734098960,PHID-USER-eqjbrvz42r7foicyocxh,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)",Is this supposed to be tagged Code-Stewardship-Review? Seems more like a feature request to me. If you disagree feel free to re-tag.,1685990607,PHID-USER-qydb7ytmqqctg7dn7fqa,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","For everyone's info, currently no #code-stewardship-reviews are taking place as there is no clear path forward and as this is not prioritized work.
+(Entirely personal opinion: I also assume lack of decision authority due to WMF not having a CTO currently. However, //discussing// this is off-topic for this task.)",1651563672,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","Removing task assignee due to inactivity, as this open task has been assigned for more than two years. See the email sent to the task assignee on February 06th 2022 (and `T295729`).
+
+Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome.
+
+If this task has been resolved in the meantime, or should not be worked on (""declined""), please update its task status via ""Add Action… 🡒 Change Status"".
+
+Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator.",1647201313,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","Another page where this will be very useful is MostTranscludedPages. The templates that are used on articles, user pages, talk pages, and category pages are quite different, and it would be useful to know what are the most used templates in each namespace.",1567917425,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","Change 522602 had a related patch set uploaded (by DannyS712; owner: DannyS712):
+[mediawiki/core@master] Add namespace filter to Special:WantedPages
+
+[[https://gerrit.wikimedia.org/r/522602]]",1563034515,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","There is similar code in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/SpecialNewpages.php | SpecialNewpages.php ]] that allows filtering that by namespace (see `parseParams`, `formDescriptor`, and the logic in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/pagers/NewPagesPager.php | the pager ]]. I think the use of a drop-down menu to select the namespace would be best, given that it is already in use elsewhere. I'll try to add a filter for Special:WantedPages, and if that works add it to the others.",1563034482,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","There is similar code in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/SpecialNewpages.php | SpecialNewpages.php ]] that allows filtering that by namespace (see `parseParams`, `formDescriptor`, and the logic in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/pagers/NewPagesPager.php | the pager ]]. I think the use of a drop-down menu to select the namespace would be best, given that it is already in use elsewhere.",1563025900,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","There is similar code in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/SpecialNewpages.php | SpecialNewpages.php ]] that allows filtering that by namespace (see `parseParams`, `formDescriptor`, and the logic in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/pagers/NewPagesPager.php | the pager ]]",1563025804,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)",There is similar code in [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/includes/specials/SpecialNewpages.php | SpecialNewpages.php ]] that allows filtering that.,1563025495,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","Support for this feature request. It came up in the Dutch Wikipedia Village Pump as request a few days ago. A big help would already be to differentiate between Content namespaces (Main, List, etc) and All namespaces. ",1531157783,PHID-USER-bdyms27sdtgdvjm7zfz4,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)",This doesn't seem to be related to VisualEditor.,1503062038,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+"Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)","(In reply to comment #0)
+> I've played a bit, by adding a $namespace parameter extracted from
+> $wgRequest->getInt( 'namespace' ), but I would need some guiding about
+> reusing
+> it in more Special pages (for instance, also in WantedPages) and prepare a
+> patch if this enhancement is considered interesting enough.
+
+I'd recommend to write a basic initial patch and iterate from there on.
+You are very welcome to use Developer access
+  https://www.mediawiki.org/wiki/Developer_access
+to submit a patch as a Git branch directly into Gerrit:
+  https://www.mediawiki.org/wiki/Git/Tutorial",1363962077,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3yeacms7h4ndqwnaljiw,task_subcomment,NA
+VisualEditor: behavior switches are saved in parser environment,"parser patch to stub signature wikitext
+
+Just learning about the parser--these patches will match the __NOTOC__ etc. layout behavior switch keywords, and signature and timestamp strings.
+
+I'm not so confident about my decisions where to put these grammars.
+
+The behavior switch keywords should probably turn into tokens which send control commands to set state in the sync23 stage.
+
+The signature doesn't have access to the current username.  The timestamp has no locale or user timezone functionality.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F8819}",1332357960,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_description,declined
+VisualEditor: behavior switches are saved in parser environment,Seems to be a NOTDONE given Adam's comment. :-),1340403756,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_subcomment,NA
+VisualEditor: behavior switches are saved in parser environment,Mass-moving items into VisualEditor product,1340402741,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_subcomment,NA
+VisualEditor: behavior switches are saved in parser environment,"Patches have been deprecated in favor of https://gerrit.wikimedia.org/r/4050
+
+I've abandoned the signature/timestamp patch, agreeing with Brion that,
+> These sorts of things really should be happening *in* the editor, rather
+> than in the parser. We only have to put ~~~~ in because the original editor
+> was too primitive to have a nice ""insert signature"" live function. So I
+> think it's worth really rethinking how these things get done for the new
+> paradigm. :)",1333247667,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_subcomment,NA
+VisualEditor: behavior switches are saved in parser environment,"Created attachment 10309
+parser grammar stub for behavior switch magic words
+
+**Attached**: {F8820}",1332358043,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-f2cowtgtc2wzg3hsmtjy,task_subcomment,NA
+VisualEditor: wrap parser output callback,"patch
+
+Totally trivial static function to abstract out __parseArgs[2] and explain.  It's possible that we want the flush() functionality to work differently in the future.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F9217}",1332324900,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-nww4b27vuz6kurpzyhrl,task_description,resolved
+VisualEditor: wrap parser output callback,Mass-moving bugs into the new 'Parsoid' product.,1344281137,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,"Fixed in commit 1736e52bfb6c6b459b571cd8a8f26c7ee6d84da7. Thanks for your patch, Adam!",1341045649,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,"Just noticed that this was assigned to my old (now reactivated with wikimedia address) bugzilla account.
+
+It is still current, and still relates to VE since Parsoid is currently treated as a submodule of VE in Bugzilla. We should perhaps create a separate product for it so that we can set up our own set of default assignees etc.",1340476773,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,Gabriel - this still current?,1340403701,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,Mass-moving items into VisualEditor product,1340402719,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,What's the status of this bug? And does it actually relate to the VisualEditor extension?,1340395142,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,"**sumanah** wrote:
+
+By the way, Adam, you can get a Gerrit account if you want and suggest changes to be merged directly into our Git repository: https://www.mediawiki.org/wiki/Project:Labsconsole_account & https://www.mediawiki.org/wiki/Git/Workflow#Easier_submission_of_code have more information.",1332385352,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+VisualEditor: wrap parser output callback,"**sumanah** wrote:
+
+Thanks for the patch! Added keywords to ask for code review.",1332355998,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nww4b27vuz6kurpzyhrl,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"WikiEditor toolbar icons are low-resolution raster images, and appear visibly pixelated on a high-resolution display such as iPad third-gen or when zoomed in.
+
+Recommend using SVG images with PNG fallbacks.
+
+Note that currently many of these images are sprited and may need to be re-separated and re-drawn.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1332199740,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_description,resolved
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 220344 abandoned by Jforrester:
+WikiEditor: Add svg images
+
+Reason:
+No reason to back-port.
+
+[[https://gerrit.wikimedia.org/r/220344]]",1435171591,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 220344 had a related patch set uploaded (by Paladox):
+WikiEditor: Add svg images
+
+[[https://gerrit.wikimedia.org/r/220344]]
+",1435099603,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"* https://gerrit.wikimedia.org/r/181786 (branch master): #mw1.26wmf12
+* https://gerrit.wikimedia.org/r/195529 (branch master): #mw1.26wmf12
+",1435093227,PHID-USER-n4kveqwjjlpsb6ydn73h,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 195529 merged by jenkins-bot:
+Add svg to LESS file
+
+[[https://gerrit.wikimedia.org/r/195529]]",1435092277,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181786 merged by jenkins-bot:
+WikiEditor: Add svg images
+
+[[https://gerrit.wikimedia.org/r/181786]]",1435092121,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,i have uploaded patch that moves the signature button down slightly please could you check it. and if you want the italic i changed a bit could i have some help to do that please.,1435067254,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I think the italic I was done like that on purpose.,1435066791,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Maybe I could do something with css for the signature since that is a new updated version of previous with details of who created in the patch at gerrit.
+
+But not sure about italic might need help on that one please.",1435012063,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi how can I fix it. I am using the original version but removed the shadow.,1435011419,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"I can be OK with this version.
+I have a slight concern about the outline of the italic I, and the signature button seems to be aligned a bit 'high'.
+
+{F182267}",1435009644,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Ok so I should disable enhanced dialogs to test to see if it still works.,1434913288,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"I just visited  http://en.random-wikisaur.tk/index.php?title=Main_Page&action=edit  with Win8.1/IE 11 and saw no ill-effects when zooming either. Some of the plain-text based icons still seem a little ""dull"" to me but so are the .png variants; not a reason to disqualify merging imho though.
+{F181822}
+'Enhanced dialogs' are enabled for guests it seems so it might be best to verify everything is OK without the dialogs enabled and just straight WikiEditor as well.
+
+Remember: A picture is worth a thousand words; especially if as many icons are displayed as possible (i.e. tick the 'Advanced' menu open like I did in my screen-grab)",1434911560,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Here is a screenshot showing it works now.
+
+Zoomed in at 110%.
+
+{F181806}",1434909052,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Yes it is fixed. I inserted the code to fix chrome issue I also tested it in ie to check if it affected the way it shows but doesent.,1434908363,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#399524, @TheDJ wrote:
+> Created attachment 16901
+> Alignment trouble
+> 
+> Well I should be able to see that it works in all situation, not just in yours, and as this screenshot of a zoomed Chrome shows, it simply still doesn't work... unfortunately.
+> 
+> **Attached**: {F9095}
+
+@TheDJ - assuming the modifications mentioned in...
+
+>>! In T37342#1228421, @Paladox wrote:
+> Hi I fonund a fix to chrome zooming out problem. we should use preserveAspectRatio=""none"" and xml:space=""preserve"" in button-sprite.svg file.
+
+>>! In T37342#1228470, @Paladox wrote:
+> Found the fix at http://yootheme.com/support/question/6801?order=modified
+
+... have been applied to the latest rebase, could you please see if the Chrome~Zoom issue has been resolved?
+Getting these .svg images up & working is the first step on the path to mirroring VE's scheme (FontAwesome-ish). Thanks
+",1434906902,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Found the fix at http://yootheme.com/support/question/6801?order=modified,1429726756,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Hi I fonund a fix to chrome zooming out problem. we should use preserveAspectRatio=""none"" and xml:space=""preserve"" in button-sprite.svg file.",1429726484,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,,1429301559,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,,1429301541,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,https://code.google.com/p/chromium/issues/detail?can=8&start=0&num=100&q=&colspec=ID%20Pri%20M%20Week%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=&id=458307,1427631594,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181788 abandoned by Paladox:
+Adds svg to css file
+
+Reason:
+Moved to https://gerrit.wikimedia.org/r/#/c/195529/8 since less has been merged.
+
+[[https://gerrit.wikimedia.org/r/181788]]",1425984241,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 195529 had a related patch set uploaded (by Paladox):
+Add svg to LESS file
+
+[[https://gerrit.wikimedia.org/r/195529]]
+",1425982208,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Thankyou. your really good at it.,1424895262,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1056482, @Paladox wrote:
+> Hi could you please do what you did with the image...
+Here is the icon without mask but same effect (+ some minor improvements).
+{F44927}",1424559619,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1056482, @Paladox wrote:
+> Hi could you please do what you did with the image...
+Here is the icon without mask but same effect.
+{F44922}
+",1424559306,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Thanks.,1424522731,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi could you please do what you did with the image your uploaded and do it to this one https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FWikiEditor/1eaf5e8463ae5a95c7a7939d8f3f894b1283742f/modules%2Fimages%2Ftoolbar%2Finsert-ilink.svg this is an old link and this is the current link https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FWikiEditor/c12f248eaa673b1419bd20c77a59ddc0c5bba07f/modules%2Fimages%2Ftoolbar%2Finsert-ilink.svg the old one uses mask the current link doesent please could you get the new link to look like old link without having to use mask.,1424522723,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Thank you for doing that. It is that another image had to have mask removed because it was not showing in internet explorer. but thanks for upload an updated image without mask.,1424484649,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+>> Hi internet explorer does not support mask. please could you do the image without having to do mask thanks.
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask, and bit other improvements). Thanks for promptly take.",1424481747,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask, and bit other improvements). Thanks for promptly take.",1424481721,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask). Thanks for promptly take.",1424481633,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask). Thanks for take.",1424481585,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#1053269, @Paladox wrote:
+
+I have uploaded a new version (the ""s"" more away from pencil and without mask)",1424481557,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I have added the new image to the patch I have also updated the png version.,1424451742,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi internet explorer does not support mask. please could you do the image without having to do mask thanks.,1424442765,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Thanks will add it soon to the patch.,1424370183,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"On request I've created an new signature icon:
+* [[ http://commons.wikimedia.org/wiki/File:Insert-signature2.svg | File:Insert-signature2.svg ]]
+
+Because the current icon shows something like ""**f**alse"" or in German ""**f**alsch""/""fehlerhaft""",1424365201,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,The patch is ready to be merged with the svg and then we can merge the file that includes the svg line in css later.,1423781775,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have reported the bug at webkit for svg not being able to zoom out correctly on chrome. The bug is at https://bugs.webkit.org/show_bug.cgi?id=141535,1423779296,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181786 had a related patch set uploaded (by Paladox):
+Re add svg images
+
+[[https://gerrit.wikimedia.org/r/181786]]
+
+#patch-for-review",1422229973,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have uploaded the new image.,1422229917,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I am using my laptop screen on tv so I can upload the image now which I will be doing.,1422227559,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Ok should I use this one. Sorry I missed this reply. I will upload when I can. Laptop broke last week so have to wait for it be repaired before using git to upload.,1422205535,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Paladox
+
+I don't know what the big deal was. I commented out the `<mask>` section using a text editor and the basic icon reappeared when I opened it again. Now I don't know if that means it still needs a //mask// or not  -- can't say I didn't corrupt the file further either. 
+
+{F26805}
+
+The only thing I'm sure is that I can see it now in IE... and I bet that's better than knowing there is a button on your toolbar but the lack of even a crippled button-icon means you have no clue what it does until you tick on it. (NOT optimal).
+
+So use it if we can, fix it if we must... but at least swap out the one rendering ''blank'' for something that everybody can at least see. ",1420619890,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Paladox
+
+I don't know what the big deal was. I commented out the Mark section using a text editor and the basic icon reappeared when I opened it again. Now I don't know if that means it still needs a //mask// or not  -- can't say I didn't corrupt the file further either. 
+
+{F26805}
+
+The only thing I'm sure is that I can see it now in IE... and I bet that's better than knowing there is a button on your toolbar but the lack of even a crippled button-icon means you have no clue what it does until you tick on it. (NOT optimal).
+
+So use it if we can, fix it if we must... but at least swap out the one rendering ''blank'' for something that everybody can at least see. ",1420619856,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Paladox
+
+I don't know what the big deal was. I commented out the Mark section using a text editor and the basic icon reappeared when I opened it again. Now I don't know if that means it still needs a //mask// or not  -- can't say I didn't corrupt the file further either. 
+
+{F26805}
+
+The only thing I'm sure is that I can see it now in IE... and I bet that's better than knowing there is a button on your toolbar but the lack of even a crippled button-icon means you have no clue what it does until you tick on it. (NOT optimal).
+
+So use it if we can, fix it if we must... but at least swap out the one rendering ''blank'' for something that everybody at see. ",1420619808,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Jdforrester-WMF said:
+>At the request of Design I'm (very slowly) working on replacing all the assets with copies of the OOjs UI ones (in advance of actually switch WikiEditor over to using that, which is lower priority). Maybe we should merge these efforts?
+
+If it gets mobile, tablet and similar device user's the same intended results //A//nd within a reasonable amount of time, then I'm all for it. The current ''bundle'' of .png-matching .svg files are just not making the cut. I suspect the amount of turnover week in, week out has jaded many beyond the point of no return by now as well.
+
+Still, I'd hate to wait another 3 or 4 months for something that could be applied today in full & in the interim; where individual, problematic .svg based icons are disabled by pointing them either to the equivalent .svg stand alone image file or the alleged fallback, stand alone png  as the issues at hand should dictate.",1420567662,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi the image insert-ilink.svg and the same image but in button-sprite.svg seems to not show in certain browsers the problem is with using mask. It works in chrome but in Internet explorer it does not show this I doint know how to fix this problem.,1420554603,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#945952, @Paladox wrote:
+> I can confirm that problem is because of multiple images inside one image file. I tested it.
+
+Are you saying its because WikiEditor first looks to use ''Spirited'' button icons from //button-sprite.svg// using offset coordinates instead of individual icons?
+
+If so, I wonder why it does not happen using //button-sprite.png// (or does it but nobody bothered to try?)",1419888506,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I can confirm that problem is because of multiple images inside one image file. I tested it.,1419776339,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi here is the bug filed https://bugs.webkit.org/show_bug.cgi?id=125118 and https://code.google.com/p/chromium/issues/detail?id=260319 it seems the bug is when the image has multiple images in it.,1419774614,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi if you zoom out to 50% it lines up again. seems to either been a problem with the css or it is webkit or chrome.,1419774170,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"I think it is to do with this file jquery.wikiEditor.toolbar.config.js
+
+and how do you add something like 2px -142px center to background-position because it seems if I add 2px center the icon goes back to the position you want it to be but it is a different icon.",1419772581,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Oh ok.,1419767078,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#945594, @Paladox wrote:
+> probably the file button-sprite.png and .svg need to be separated into different images to fix the issue on google chrome (guessing)
+
+It could just be an overlooked css attribute and setting like the one that fixes T78354 for example. We won't know until folks have something to test against.",1419727208,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,probably the file button-sprite.png and .svg need to be sepereted into different images to fix the issue on google chrome (guessing),1419726053,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi but there is an error with chrome where if you zoom out pass 90% or lower it will make the icons go out of position. how will that get fixed but any ways chrome default zoom is 100% and not a lot of people use 90% zoom (guess) so this svg images that are being added could get merged and the problem fixed letter including the .css or .less file.,1419723973,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943845, @Paladox wrote:
+> There is also a bug with having svg images because if your on chrome and 90% zoomed in the icons go everywhere.
+
+Every example screenshot that I've seen is not the default WikiEditor toolbar but always with additional buttons, etc. added afterwards. I'd like to see an unmodified WikiEditor toolbar behave that way just to be sure.
+
+Scratch that I just saw https://phabricator.wikimedia.org/T37342#399524
+
+seems like problem with the spirited coordinates not re-sizing on such actions as a zoom. ",1419518358,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943845, @Paladox wrote:
+> There is also a bug with having svg images because if your on chrome and 90% zoomed in the icons go everywhere.
+
+Every example screenshot that I've seen is not the default WikiEditor toolbar but always with additional buttons, etc. added afterwards. I'd like to see an unmodified WikiEditor toolbar behave that way just to be sure.",1419517812,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi the problem started when someone created the images earlier this year. The problem was the reported.,1419517258,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943844, @Paladox wrote:
+> Do you have the link for svg version of format-olist.svg 
+
+It was part of one your patchsets - https://gerrit.wikimedia.org/r/151203",1419517097,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,There is also a bug with having svg images because if your on chrome and 90% zoomed in the icons go everywhere.,1419517000,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Do you have the link for svg version of format-olist.svg ,1419516963,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943824, @GOIII wrote:
+> ...but if the svg file variants for all the existing png files are missing some, I doubt anybody would want to merge that so there's the first roadblock
+> 
+Then again, the whole point of keeping/having the png files is for a fallback if svg somehow fails so I take it back -- no reason not to vote merge
+",1419515856,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"r151203 had at least `format-olist.svg` listed in it
+
+...but if the svg file variants for all the existing png files are missing some, I doubt anybody would want to merge that so there's the first roadblock
+
+I wish we could slow down some and address one thing at a time - we're already 9 patch-sets deep for example and the css could have taken some cleaning/amending first too.",1419514974,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi they doint currently have svg images but can be added later.,1419514374,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 abandoned by Paladox:
+WikiEditor: Convert .css to .less and also fixes SVG issues.
+
+Reason:
+Split this into two patches first patch is svg images https://gerrit.wikimedia.org/r/#/c/181786/ second patch is convert .css to .less https://gerrit.wikimedia.org/r/#/c/181790/
+
+[[https://gerrit.wikimedia.org/r/151203]]",1419514192,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have this patch now https://gerrit.wikimedia.org/r/#/c/181790/ that converts .css to .less,1419514115,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"See, this is partly why the previous patches were so hard to follow. With the revised 1st patch just being the addition of the svg variants, the following .png files have no corresponding .svg file in the new patch
+
+* format-bold-L.png
+* format-bold-hy.png
+* format-bold-ka.png
+* format-bold-os.png
+* format-bold-ru.png
+
+* format-italic-D.png
+* format-italic-E.png
+* format-italic-hy.png
+* format-italic-ka.png
+
+* format-olist-rtl.png
+* format-olist.png
+* format-ulist-rtl.png
+
+* insert-redirect-rtl.png
+
+* magnify-clip.png
+",1419514417,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"See, this is partly why the previous patches were so hard to follow. With the revised 1st patch just being the addition of the svg variants, the following .png files have no corresponding .svg file in the new patch
+
+* format-bold-L.png
+* format-bold-hy.png
+* format-bold-ka.png
+* format-bold-os.png
+* format-bold-ru.png
+
+* format-italic-D.png
+* format-italic-E.png
+* <s>format-italic-I.png (see previous comment above)</s>
+* format-italic-hy.png
+* format-italic-ka.png
+
+* format-olist-rtl.png
+* format-olist.png
+* format-ulist-rtl.png
+
+* insert-redirect-rtl.png
+
+* magnify-clip.png
+",1419514384,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"See, this is partly why the previous patches were so hard to follow. With the revised 1st patch just being the addition of the svg variants, the following .png files have no corresponding .svg file in the new patch
+
+* format-bold-L.png
+* format-bold-hy.png
+* format-bold-ka.png
+* format-bold-os.png
+* format-bold-ru.png
+
+* format-italic-D.png
+* format-italic-E.png
+* format-italic-I.png (see previous comment above)
+* format-italic-hy.png
+* format-italic-ka.png
+
+* format-olist-rtl.png
+* format-olist.png
+* format-ulist-rtl.png
+
+* insert-redirect-rtl.png
+
+* magnify-clip.png
+",1419513951,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have managed to do it.,1419513641,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Please could I have some help to rename it because I try it but it stays at lower case I instead of being uppercase i.,1419513287,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181788 had a related patch set uploaded (by Paladox):
+Adds svg to css file
+
+[[https://gerrit.wikimedia.org/r/181788]]
+
+#patch-for-review",1419512878,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 181786 had a related patch set uploaded (by Paladox):
+Re add svg images
+
+[[https://gerrit.wikimedia.org/r/181786]]
+
+#patch-for-review",1419512868,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 abandoned by Paladox:
+WikiEditor: Re add SVG
+
+Reason:
+I have added split some of this in to two patches which are at https://gerrit.wikimedia.org/r/#/c/181786/ and https://gerrit.wikimedia.org/r/#/c/181788/
+
+[[https://gerrit.wikimedia.org/r/151611]]",1419512850,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"shouldn't `format-italic-i.svg` be `format-italic-I.svg` ? (capital i =I [eye] )
+
+the existing png I think its suppose to replace is `format-italic-I.png`",1419512845,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Css file containing svg.
+
+https://gerrit.wikimedia.org/r/#/c/181788/",1419511603,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Always abandon AFTER you have replacements up no?
+
+
+>>! In T37342#943714, @Paladox wrote:
+> So I should add svg images and if I have any png files I should add them and I should not edit the css files on first patch but add the svg image to css on the second patch and then last patch change css to less.
+
+
+Right, the first step should just be to add the final desired svg variants and/or any final desired png - be they replacements or previously missing",1419510935,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi this is the first patch https://gerrit.wikimedia.org/r/#/c/181786/ is this what you ment for first patch.,1419510842,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I will abandon them patches in a min. I will upload the new patches to make sure they are what your saying to do. thanks for helping.,1419510301,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,So I should add svg images and if I have any png files I should add them and I should not edit the css files on first patch but add the svg image to css on the second patch and then last patch change css to less.,1419509992,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Ok.,1419509863,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943701, @Paladox wrote:
+> So I should do the svg images first. and then css to less last.
+Patch No.
+# add all the final svg variants and any additional final png files to the ...images/toolbar directory
+     * nothing should change the current rendering by only adding image files here
+# edit the current css to use the svg variants and have the png variants as the fall backs
+     * we can stop here to see if anybody has svg rendering issues or not. If not...
+# convert the svg rich css files to use the less format
+     * we then see if anything has changed from the rendering seen in #2
+
+Well that's what I //think// is the best way for folks to pay attention to this again while addressing previously voiced concerns/issues. I could very well be 100% wrong mind you.",1419510822,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943701, @Paladox wrote:
+> So I should do the svg images first. and then css to less last.
+Patch No.
+# add the svg variants and any additional png files to the ...images/toolbar directory
+     * nothing should change the current rendering here
+# edit the current css to use the svg variants and have the png variants as the fall backs
+     * we can stop here to see if anybody has svg rendering issues or not. If not...
+# convert the svg rich css files to use the less format
+     * we then see if anything has changed from the rendering seen in #2
+
+Well that's what I //think// is the best way for folks to pay attention to this again while addressing previously voiced concerns/issues. I could very well be 100% wrong mind you.",1419509898,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,">>! In T37342#943701, @Paladox wrote:
+> So I should do the svg images first. and then css to less last.
+Patch No.
+# add the svg variants and and any additional png files to the ...images/toolbar directory
+     * nothing should change the current rendering here
+# edit the current css to use the svg variants and have the png variants as the fall backs
+     * we can stop here to see if anybody has svg rendering issues or not. If not...
+# convert the svg rich css files to use the less format
+     * we then see if anything has changed from the rendering seen in #2
+
+Well that's what I //think// is the best way for folks to pay attention to this again while addressing previously voiced concerns/issues. I could very well be 100% wrong mind you.",1419509828,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Patch No.
+# add the svg variants and and any additional png files to the ...images/toolbar directory
+     * nothing should change the current rendering here
+# edit the current css to use the svg variants and have the png variants as the fall backs
+     * we can stop here to see if anybody has svg rendering issues or not. If not...
+# convert the svg rich css files to use the less format
+     * we then see if anything has changed from the rendering seen in #2
+
+Well that's what I //think// is the best way for folks to pay attention to this again while addressing previously voiced concerns/issues. I could very well be 100% wrong mind you.",1419509785,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I will create the first patch with the new svg images excluding the arrow image. and second will include css to less arrow svg images and the new svg images from first reason because if first patch gets merged then this patch could get rebased without needing to add anything else.,1419509681,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,So I should do the svg images first. and then css to less last.,1419509304,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi the reason I created three patches is because someone asked me to create separate patches and then someone asked me to put the patch into one. so I created three patches. should I create two one with the convert to .less and with the svg images of arrow and then the other svg images in different patch with the fix for the background.,1419509255,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,On second thought - maybe css to less conversion should be the last patch merged after all the other pieces are in place rather than the first patch.,1419509127,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"basically yes -- although I suspect you would do better by taking the existing three and separating the changes even further into even more specific patches. Again, this is just from an observational standpoint rather a technical one. Nevertheless, these enhancements seem to be pretty much ignored no matter how one looks at them.
+
+Maybe the first step should be a conversion of the existing .css into less format prior to the svg icons addition/modifications for example. Then add the svg variants in another patch - the changes needed to make them live in the now existing less files in still another patch. And so on....",1419508909,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi so should I abandon them and then re upload them.,1419504455,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"> [[https://gerrit.wikimedia.org/r/151611]]
+> 
+> [[https://gerrit.wikimedia.org/r/151616]]
+> 
+> [[https://gerrit.wikimedia.org/r/151203]]
+> 
+These 3 patches have been re-committed for weeks and weeks now to no avail. Nobody, including myself, seems to be comfortable with supporting a merge for revisions that have three-dozen or more Patch-sets in place to date -- not to mention each patch is trying to accomplish more than it should or overlaps into another's all at once.
+
+It seems to me the best way to get the underlying changes merged is to abandon these three and create new ones that accomplishes the same end results but with smaller steps to reach that aim instead.",1419474773,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded (by Paladox):
+WikiEditor: Re add SVG
+
+[[https://gerrit.wikimedia.org/r/151611]]
+
+#patch-for-review",1417643642,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded (by Paladox):
+WikiEditor: Convert .css to .less and also fixes SVG issues.
+
+[[https://gerrit.wikimedia.org/r/151203]]
+
+#patch-for-review",1417122920,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded (by Paladox):
+WikiEditor: Re add SVG
+
+[[https://gerrit.wikimedia.org/r/151611]]
+
+#patch-for-review",1417122843,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded by Paladox:
+WikiEditor: Re add SVG
+
+https://gerrit.wikimedia.org/r/151611",1416224701,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded by Paladox:
+WikiEditor: Fix issue with SVG
+
+https://gerrit.wikimedia.org/r/151611",1415219504,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Based on talking to James and Trevor, we can provide the icons that will improve consistency dramatically, we're targeting end of day tomorrow Nov 5 to have all the assets ready to integrate. Thanks for a moment of patience.",1415149663,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to Jared Zimmerman (WMF) from comment #66)
+> No, i just mean the same SVG assets. for bold, italic, image, link, etc. Not
+> the code behind an OOUI control
+
+That's fundamentally incompatible with how MediaWiki is built. Reaching in to the code base to pull out assets will immediately fail basic code review.",1415146038,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"No, i just mean the same SVG assets. for bold, italic, image, link, etc. Not the code behind an OOUI control",1415145973,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Using the OOUI icons means using OOUI. Porting the wikitext editor to OOUI is a big piece of work.,1415145859,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"part of me is still wondering why we aren't using the icons that are in use in VisualEditor currently, any rational?",1415145803,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 168821 merged by jenkins-bot:
+Revert ""Add SVG versions of toolbar icons""
+
+https://gerrit.wikimedia.org/r/168821",1415139693,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have one of the images that were fixed by a user here and fixed the other ones to. the patch is at https://gerrit.wikimedia.org/r/#/c/151611/,1415119144,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Okay, this is getting ridiculous. M4tx made a commit that added SVG files (a low priority enhancement). The commit accidentally mutilated the ""B"" icon (visible regression) and was merged by TheDJ.
+
+See
+https://gerrit.wikimedia.org/r/#/c/97454/
+http://i.imgur.com/mBZm28W.png
+
+
+I don't know what everyone is doing, but please just fix the icon. All this other stuff is unrelated to this bug. If there's no simple commit that fixes the icon soon I'll recommend reverting the SVGs for the time being and re-submitting that change as a draft blocked on restoring the B icon.",1415118989,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,This one only includes the fixes for svg http://simple-random-wikisaur.tk/index.php?title=Main_Page&action=edit,1414326828,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,That site also includes .less.,1414326445,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to Derk-Jan Hartman from comment #55)
+> ""is the way I thought this was all going to play out too."" There are no
+> dependencies on the tickets, there are no comments on the commit message
+> that indicate this.
+> 
+Granted - and you are absolutely correct to take that position imo as well. I merely had the small benefit of following this exercise 20+ revisions ago is all. Don't read into it any further than that.
+
+(In reply to Derk-Jan Hartman from comment #53)
+> 4: It turned out that there were problems with the SVGs in production. This
+> should have been cause for reverting the change.
+
+Bingo. Regression seems to be a dirty word around here however.",1414326005,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 16901
+Alignment trouble
+
+Well I should be able to see that it works in all situation, not just in yours, and as this screenshot of a zoomed Chrome shows, it simply still doesn't work... unfortunately.
+
+**Attached**: {F9095}",1414325710,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I have created 3 commits one has all of it in it and 2nd patch has .less in it and third patch has the fixes for svg.,1414325541,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"""is the way I thought this was all going to play out too."" There are no dependencies on the tickets, there are no comments on the commit message that indicate this.
+
+That first link already mixes three issues in a way that I'm not confident anymore that something unexpected is mixed into it as well.
+
+Separation of concerns (in bugzilla tickets, commit messages etc), be explicit about what depends on what, proof that stuff works (as intended) and you will convince a core reviewer to merge the code. That has not happened so far.",1414325442,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Ok I have tested all the patches on my site. here is link to show how it is working. http://en.random-wikisaur.tk,1414325196,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Paladox, I'm not sure how I need to explain this to you and it hope it doesn't come across as rude, because it's not intended to be that way, but this whole stuff is simply not reviewable right now.
+
+If I go trough a patchset, read the commit message and the diff, test it in my browsers and NOT have all my questions answered. It cannot be merged.
+
+Things I should not have to do are:
+1: Go trough 50 patchset rebases
+2: Go trough 15 comments interspersed with these rebases, for finding answers that should be in the commit message, if they affect the review.
+3: Pick and choose between 3 patchsets, for one change.
+
+
+This Bug ticket is about converting the Original PNGs to SVG.
+1: M4tx did some nice work
+2: This work was not pixel perfect with the original PNGs, but that was fine
+3: I approved the SVG change on that basis
+4: It turned out that there were problems with the SVGs in production. This should have been cause for reverting the change.
+5: Instead of reverting I gave people a chance to fix it, Pro, you etc.
+6: You currently are the one making those proposals for changes.
+7: You can't answer the questions in a way that gives enough people confidence to approve the changes. (either by lack of experience, by lack of your mastery of the language, of not actually being able to prove it all works as expected etc.)
+8: This means the patches cannot be merged, and that means that it's about time to bite the bullet, and I need to admit that I should have reversed the original commit back then when it became clear there were some problems with the original change to SVG.",1414325003,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to paladox2015 from comment #50)
+> Hi i have got it right i have added the images that were here to the patch
+> and also added a note on who created the image i also followed fomafix
+> instructions and so the patch should be correct now.
+
+https://gerrit.wikimedia.org/r/151203
+
+... followed by ...
+
+https://gerrit.wikimedia.org/r/151611
+
+... followed by ...
+
+https://gerrit.wikimedia.org/r/151616
+
+... is the way I thought this was all going to play out too.",1414324893,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 168821 had a related patch set uploaded by TheDJ:
+Revert ""Add SVG versions of toolbar icons""
+
+https://gerrit.wikimedia.org/r/168821",1414323690,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi i have got it right i have added the images that were here to the patch and also added a note on who created the image i also followed fomafix instructions and so the patch should be correct now.,1414323543,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"I can't seem to get a clear, concise and accurate description from the patch submitters on these problems. Problems also remain in the latest versions of the submitted patches with strange offset problems in the sprite when the user zooms in or out.
+
+Since there are clearly problems in the original patch that was converting the toolbar resources to SVG, and since it seems that the patch submitters cannot get them corrected, I think that there is only one solution left. Revert the original SVG patch and wait till someone with SVG skills AND gerrit experience pays attention to this problem.",1414323342,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have now fix it.,1412625240,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have fixed it.,1410782072,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to paladox2015 from comment #42)
+> Merge Failed.
+> This change was unable to be automatically merged with the current state of
+> the repository. Please rebase your change and upload a new patchset.
+
+So please fix that? :)",1410781002,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/151203",1410778589,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 160421 abandoned by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/160421",1410778225,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 160421 had a related patch set uploaded by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/160421",1410778182,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Hi I have now re opended the patch but it says 
+
+Merge Failed.
+
+This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset.",1410730049,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/151203",1410729808,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded by Paladox:
+WikiEditor: Convert .css to .less and also fixes svg issues.
+
+https://gerrit.wikimedia.org/r/151203",1410728915,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 restored by Paladox:
+Update WikiEditor
+
+https://gerrit.wikimedia.org/r/151203",1410728608,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have already done a patch that does that. https://gerrit.wikimedia.org/r/#/c/151203/ Someone commit and said to split them into two patches.,1410727035,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"(In reply to Bartosz Dziewoński from comment #36)
+> 
+> Can anybody summarize what is going on and what's up with all the various
+> patches and attachments? . . .
+> 
+
+I'll second that!
+
+When it comes to such matters involving images/icons on a toolbar, it seems [to me] the best way to whittle down the issues is to actually have them render in semi-real world instances and have folks report back their findings.
+
+Can't we merge ....
+
+https://gerrit.wikimedia.org/r/151611
+
+and 
+
+https://gerrit.wikimedia.org/r/151616
+
+... so that they at least come up live & working on test2.wikipedia.org in the immediate near future (i.e. today)?
+
+That should get us a decent pool of user responses before next week's scheduled core update to see if those patches resolve anything (or not) bug-wise and still give us enough of a buffer to further refine or revert as needed before that scheduled update rolls-out as well.
+
+The way things stand now, with half a dozen patch sets awaiting attention or implementation for weeks if not months already, we sure don't seem to be resolving much.",1410666732,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"This bug seems to be tracking at least two or maybe three completely distinct issues, one of which has just been reported as bug 70679.
+
+Can anybody summarize what is going on and what's up with all the various patches and attachments? Derk, you're marked as assignee – are you still working on it?",1410455845,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Hi I have fixed the problem I also removed the shadow from the rest of the svg icons.,1409906966,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on attachment 15497
+button-sprite.svg fixed
+
+Hi there is a problem with this image I uploaded to gerrit and this is what user krinkle said.
+
+
+format-B is now missing a doctype. And the sprite completely changed. It should probably only have the bold part replaced.
+
+I mean xml header, not doctype.",1409311484,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded by Paladox:
+WikiEditor: Fix issue with SVG
+
+https://gerrit.wikimedia.org/r/151611",1407426536,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 abandoned by Paladox:
+Update WikiEditor
+
+Reason:
+Ok.
+
+Please see Ic0c261f66ee882efeb07ab77ee2a3a5533093c4f for the fix for svg images. and I2a223e202aa488f0e83e663e490ee009da686687 for converting .css to .less.
+
+https://gerrit.wikimedia.org/r/151203",1407168713,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151611 had a related patch set uploaded by Paladox:
+WikiEditor: Fix issue with SVG
+
+https://gerrit.wikimedia.org/r/151611",1407150680,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 151203 had a related patch set uploaded by Paladox:
+Update WikiEditor
+
+https://gerrit.wikimedia.org/r/151203",1406927368,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"But for sure, I would upload tomorrow another fixed version, with all group transform attributes removed (W3C valid uncompressed and xml well formed).",1405204063,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@Derk-Jan Hartman, yes me too, it is the browser zoom level, but only in Chrome and only sporadically. (If I reset the zoom level, the effect is gone immediately.)
+
+I can't say it is an SVG bug, instead of a Chrome bug with CSS sprite sheets (maybe only with SVG).",1405199463,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@PRO, i'm also seeing what you see in your: ""Screenshot - vector-bar completely disordered""
+
+I'm mostly seeing it if I zoom the page out a bit. Probably has to do with scaling and rounding... ?",1405112728,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Is anyone working on merging PRO's corrected button sprite into code?
+
+I'm also seeing what Krinkle reported before (positioning issues of the shadow of all letters) which is fixed with attachment 15497.
+
+This should be a high priority since it looks pretty broken right now!",1405070793,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@PRO, btw we don't need it to be SVGZ compressed, because that already happens on the fly.
+
+I concur that the gaussian blur is somewhat unusual, and I'm not a big fan of it myself.",1401360541,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Thank you PRO, i'll get on this in the next week.",1401277666,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on attachment 15497
+button-sprite.svg fixed
+
+All GaussianBlur filter are still present although this is very unusual for small icons. I would make a version without GaussianBlur. (File size before 152.841 Bytes after my optimation = 34.961, SVGZ compression = 10.918 Bytes)",1401259506,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"button-sprite.svg fixed
+
+I've optimized the button-sprite and also converted all text to path. Check it out.
+
+**Attached**: {F9094}",1401259124,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on attachment 15466
+Screenshot - vector-bar completely disordered
+
+Now everything is ok again, I've nothing changed.",1400877805,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on attachment 15465
+Letter B fixed
+
+font type to path",1400863912,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Screenshot - vector-bar completely disordered
+
+It appears also if I logged out. Win 7 Chrome 34. Firefox is normal.
+
+**Attached**: {F9093}",1400863853,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Letter B fixed
+
+Font to pfad converted , remove all transform attributes.
+
+**Attached**: {F9092}",1400863295,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 15431
+Zip of icon files
+
+**Attached**: {F9091}",1400417677,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"@DJ, the proposed SVG icons were significantly different (bevels, embossing, gradients) which definitely diverge from what we had, I was just saying, if we're diverging from what we had, I'd like to diverge in the right direction, not in the direction of greater ornamentation.",1400172622,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Eh, this is just about the old style icons, we are not talking about replacing them...",1400159859,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I thought there is an Wikimedia icon initiative? I'm interesting to do this like simple in the Tango/GNOME style!? [[File:Gnome-format-text-bold.svg]],1400154692,PHID-USER-qrrijb4p5yfluwirt7lw,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Anything that is already part of wikifont doens't need to be redrawn https://github.com/munmay/WikiFont/blob/master/Screenshot-current.png,1400093115,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Good point, i'll upload them on commons.wm.org",1400075265,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"**anonmoos** wrote:
+
+Re: request for assistance in the Commons Graphics village pump:
+
+It might help if the SVG code in question were available somewhere as an ordinary SVG file, and not only as embedded in some kind of generalized source code patch management database system that not everybody may feel like trying to come to terms with...",1400074767,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,I also left a request for assistence in the commons graphics lab. https://commons.wikimedia.org/wiki/Commons:Graphics_village_pump#SVG_improvements_for_MediaWiki_toolbar,1400056565,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Comment on https://gerrit.wikimedia.org/r/97454:
+
+FIXME: The ""B"" button looks broken.
+
+> This change changed the B button to have 3D depth
+> whereas all the others remain flat (the book icon
+> also some depth to it, but not beyond a simple surface,
+> which looks fine). The depth is sufficiently odd that
+> I suspect this was not done on purpose. 
+>
+> Screenshot: http://i.imgur.com/mBZm28W.png
+> (bottom row shows the new SVG versions)
+>
+> It looks like the outline that is making it look
+> 3D is actually just the regular outline, and the
+> black filling for some reason only covers half
+> of the width.",1400005331,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 97454 merged by jenkins-bot:
+Add SVG versions of toolbar icons
+
+https://gerrit.wikimedia.org/r/97454",1399377216,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"DJ, looks ""good enough for now"" I'd like for us to clean this up, and switch to a smaller set of icons that use the new wikifont icons when we can https://www.mediawiki.org/wiki/Design/Wikicons",1398974317,PHID-USER-z3kqk2bjnqneldcznht6,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 15051
+screenshot safari 7
+
+I notice a few small problems the shadow of the chars seems a tad excessive, the red traffic sign around the W is a bit shifted for me (likely Mac Safari specific issues).
+
+**Attached**: {F9090}",1396961743,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,Done and commented.,1386183122,PHID-USER-ua75tm4u7cmt4mdof6vb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Pau / Brandon: Could you review the patch (8 lines of CSS and a bunch of new SVG files), or do you have an idea who could?",1386182674,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 13895
+Screenshot of WikiEditor after the patch
+
+**Attached**: {F9089}",1385329916,PHID-USER-myqwv53kwudj34c4zwgl,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Change 97454 had a related patch set uploaded by M4tx:
+Add SVG versions of toolbar icons
+
+https://gerrit.wikimedia.org/r/97454",1385329638,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+WikiEditor: Add SVG versions of editing toolbar icons,"Created attachment 10281
+screenshot of editing on en.wikipedia.org on iPad 3
+
+**Attached**: {F9088}",1332199815,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-km5nj6ibsdxpfztnkkyo,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","* If debug=true, remember in session
+* the ""set debugmode"" code should check session in addition to GET query param
+* going to debug=false will also unset it in the session
+
+Allows to navigate the wiki, submit forms (T37061), and stuff.
+
+To prevent users from unknowingly staying in debug mode, JS should but up an informational notification on the page informing something short like: ""You've enabled debug mode of client resources delivery, click here to disable this""
+",1331206980,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlvuxsstbitv7gqtjze,task_description,open
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode",I propose to resolve this by documenting a one-line snippet that sets the cookie-based debug mode flag for a period of time (e.g. 1 hour).,1701992404,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode",I propose to resolve this by documenting a one-line snippet that sets the cookie-based debug mode flag for a period of time (e.g. 1 hour) and leave it at that.,1664909739,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","Deprioritising until after {T85805}.
+
+Right now debug mode changes execution behaviour in a significant way, and can be very slow for modules with 1000s of class files (such MediaViewer, Wikibase and VisualEditor). I expect T85805 will make debug mode more performant and less intrusive.
+
+After that, I think it would be worth considering to allow developers, WMF staff and other interested tech-savvy users to browse our sites with ""debug mode"" enabled by default. Whether through a beta feature, regular preference, via WikimediaDebug extension, or some other way.",1554174487,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","See also:
+https://github.com/he7d3r/mw-gadget-DebugModeToggle",1416917131,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","(In reply to comment #1)
+> Since setting a cookie ""resourceLoaderDebug"" enables debug mode, this probably
+> can be done easily on client side.
+
+Ah, this is already implemented. I didn't know that. (bug 25610 slipped by silently, and it never made it into documentation).
+
+Repurposing this bug for the GUI module.",1340243946,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","(In reply to comment #1)
+> Since setting a cookie ""resourceLoaderDebug"" enables debug mode, this probably
+> can be done easily on client side.
+
+The cookie can be set on the client side, however the initial server request needs to know this before any client code is processed because it influences how the page is rendered very early on. (one could implement a redirect/refresh, but that gives the same problem with form submissions).
+
+This needs (at least some) server development. But that's OK, it's not a hard thing to do :), just other priorities right now (although patches are welcome at any time :)",1331295470,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+"Provide a way to ""sticky"" enable ResourceLoader's debug mode","Since setting a cookie ""resourceLoaderDebug"" enables debug mode, this probably can be done easily on client side.",1331283521,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-avlvuxsstbitv7gqtjze,task_subcomment,NA
+mergeMessageFileList.php spews undefined notices of some extensions,"mergeMessageFileList.php spews undefined notices of some extensions for usages of DefaultSettings variables in their inclusion script
+
+
+Updating ExtensionMessages-1.19.php...
+Loading data from /home/wikipedia/common/php-1.19/extensions/AbuseFilter/AbuseFilter.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/AntiBot/AntiBot.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/AntiSpoof/AntiSpoof.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ApiSandbox/ApiSandbox.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ArticleFeedback/ArticleFeedback.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/AssertEdit/AssertEdit.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Babel/Babel.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CategoryTree/CategoryTree.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CentralAuth/CentralAuth.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CentralNotice/CentralNotice.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CharInsert/CharInsert.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CheckUser/CheckUser.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Cite/Cite.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Cite/SpecialCite.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/cldr/cldr.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ClientSide/ClientSide.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ClickTracking/ClickTracking.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CodeReview/CodeReview.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Collection/Collection.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CongressLookup/CongressLookup.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Contest/Contest.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CommunityApplications/CommunityApplications.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CommunityHiring/CommunityHiring.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CommunityVoice/CommunityVoice.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ConfirmEdit/ConfirmEdit.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ConfirmEdit/FancyCaptcha.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ContactPage/ContactPage.php
+PHP Notice:  Undefined variable: wgSitename in /home/wikipedia/common/php-1.19/extensions/ContactPage/ContactPage.php on line 44
+
+Notice: Undefined variable: wgSitename in /home/wikipedia/common/php-1.19/extensions/ContactPage/ContactPage.php on line 44
+Loading data from /home/wikipedia/common/php-1.19/extensions/ContactPageFundraiser/ContactPage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ContributionReporting/ContributionReporting.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ContributionTracking/ContributionTracking.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/CustomUserSignup/CustomUserSignup.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/DisableAccount/DisableAccount.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/DismissableSiteNotice/DismissableSiteNotice.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/DonationInterface/donationinterface_langonly.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/DoubleWiki/DoubleWiki.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/EditPageTracking/EditPageTracking.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/EmailCapture/EmailCapture.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ExpandTemplates/ExpandTemplates.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ExtensionDistributor/ExtensionDistributor.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/FeaturedFeeds/FeaturedFeeds.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/FlaggedRevs/FlaggedRevs.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/FormPreloadPostCache/FormPreloadPostCache.php
+PHP Notice:  Undefined variable: wgUseFileCache in /home/wikipedia/common/php-1.19/extensions/FormPreloadPostCache/FormPreloadPostCache.php on line 11
+
+Notice: Undefined variable: wgUseFileCache in /home/wikipedia/common/php-1.19/extensions/FormPreloadPostCache/FormPreloadPostCache.php on line 11
+Loading data from /home/wikipedia/common/php-1.19/extensions/FundraiserLandingPage/FundraiserLandingPage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Gadgets/Gadgets.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/GlobalBlocking/GlobalBlocking.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/GlobalUsage/GlobalUsage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ImageMap/ImageMap.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/InputBox/InputBox.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/intersection/DynamicPageList.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/LabeledSectionTransclusion/lst.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/LandingCheck/LandingCheck.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/LiquidThreads/LiquidThreads.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/LocalisationUpdate/LocalisationUpdate.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/MarkAsHelpful/MarkAsHelpful.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/MoodBar/MoodBar.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/MobileFrontend/MobileFrontend.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/MWSearch/MWSearch.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Narayam/Narayam.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/NewUserMessage/NewUserMessage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Nuke/SpecialNuke.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/OAI/OAIRepo.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/OggHandler/OggHandler.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/OpenSearchXml/OpenSearchXml.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Oversight/HideRevision.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PagedTiffHandler/PagedTiffHandler.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ParserFunctions/ParserFunctions.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PdfHandler/PdfHandler.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Poem/Poem.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PoolCounter/PoolCounterClient.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PrefStats/PrefStats.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/PrefSwitch/PrefSwitch.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ProofreadPage/ProofreadPage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Quiz/Quiz.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ReaderFeedback/ReaderFeedback.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Renameuser/SpecialRenameuser.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/RSS/RSS.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ScanSet/ScanSet.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SecurePoll/SecurePoll.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ShortUrl/ShortUrl.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SimpleAntiSpam/SimpleAntiSpam.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SimpleSurvey/SimpleSurvey.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SiteMatrix/SiteMatrix.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SkinPerPage/SkinPerPage.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/skins/Schulenburg/Schulenburg.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/skins/Tomas/Tomas.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SpamBlacklist/SpamBlacklist.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SubPageList3/SubPageList3.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SwiftCloudFiles/SwiftCloudFiles.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/UserThrottle/UserThrottle.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/timeline/Timeline.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/TitleBlacklist/TitleBlacklist.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/TitleKey/TitleKey.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/TorBlock/TorBlock.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Translate/Translate.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/TrustedXFF/TrustedXFF.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/UnicodeConverter/UnicodeConverter.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/UploadBlacklist/UploadBlacklist.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/UploadWizard/UploadWizard.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/Vector/Vector.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikiEditor/WikiEditor.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/VipsScaler/VipsScaler.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/VipsScaler/VipsTest.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/VisualEditor/VisualEditor.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WebFonts/WebFonts.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/wikihiero/wikihiero.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikiLove/WikiLove.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php
+PHP Notice:  Undefined variable: wgExtensionAssetsPath in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 27
+
+Notice: Undefined variable: wgExtensionAssetsPath in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 27
+PHP Notice:  Undefined variable: wgLocalDatabases in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 115
+
+Notice: Undefined variable: wgLocalDatabases in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 115
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikimediaMessages/WikimediaLicenseTexts.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/WikimediaMessages/WikimediaMessages.php
+Loading data from /home/wikipedia/common/php-1.19/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php
+
+--------------------------
+**Version**: 1.19
+**Severity**: trivial",1329340740,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-lsoz6uynuyo3es6wev2y,task_description,declined
+mergeMessageFileList.php spews undefined notices of some extensions,Seems fine now,1343423081,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-lsoz6uynuyo3es6wev2y,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"**Author:** `van.de.bugger`
+
+**Description:**
+I have a form with nested templates:
+
+> {{{info}}}
+> {{{for template|Cache}}}
+> ...Cache fields...
+> {{{field|Locations|holds template}}}
+> {{{end template}}}
+> {{{for template|Cache/Location|multiple|embed in field=Cache[Locations]}}}
+> ...Location fields...
+> {{{end template}}}
+
+Everything works good. Page code looks as expected:
+
+> {{Cache
+> |...Cache fields...
+> |Locations={{Cache/Location|...}}{{Cache/Location|...}}...
+> }}
+
+I have an additional *partial* form:
+
+> {{{info|partial form}}}
+> {{{for template|Cache}}}
+> <!-- No Cache fields, just next one. -->
+> {{{field|Locations|holds template}}}
+> {{{end template}}}
+> {{{for template|Cache/Location}}}
+> ...Location fields...
+> {{{end template}}}
+
+After editing a page with this partial form, all the Location templates *moved* *out* of Cache, while Locations field receives strange value:
+
+> {{Cache
+> |...Cache fields...
+> |Locations=@replace_Cache___Locations@
+> }}
+> {{Cache/Location|...}}{{Cache/Location|...}}...
+
+That's obviously a big. Partial form should not move nested templates out of main template.
+
+However, there is a workaround: removing ""partial form"" specifier from partial form definition. Such a ""non-partial"" form produces correct result, but I am a bit afraid -- formally it is declared as partial form, so it does not have to save non-used fields of main template, does it?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1328917020,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_description,declined
+SemanticForms: Partial forms and nested templates.,"Changing status to ""Declined"", since partial forms were removed entirely from Page Forms in version 5.3. Unfortunately, there's no ideal way to edit template calls that are not at the top of the page. Your best bet, if you want to preserve that layout of template calls halfway down the page, might be to use VisualEditor for those instead, with the TemplateData extension.",1682374235,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"I have the exact same problem, nested templates work perfectly well, until I add {{{info|partial form}}} to my form (tested on the latest version of page forms, 5.0.1)
+
+And I don't see any alternative solution to using partial form, when the form should apply to only part of the page content, that can be anywhere inside the page, as Sophivorus mentioned.
+
+Is there any alternative solution to provide the same result?",1609845290,PHID-USER-mot76bxt3c5mvqmzegwu,False,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"Problem with using pseudo-partial forms is that PageForms moves the template to the top of the page.
+
+I'm using partial forms to provide a user-friendly interface to add metadata to videos embedded through a {{Video}} template. This template has a ""comments"" parameter that should be filled with multiple {{Video comment}} subtemplates, each specifying a video time and corresponding comment. The natural solution would be a partial form with a multiple-instance subtemplate, but this bug prevents it. Pseudo-partial forms will not do because videos are often in the middle of the page and saving pseudo-partial forms moves them to the top of the page. :-(",1606317041,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,Problem with using pseudo-partial forms is that PageForms moves the template to the top of the page.,1606315365,PHID-USER-lucj4cqevg3ebah7vybd,False,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"Hi - partial forms have never really worked well, and they certainly don't work with embedded templates. My long-term plan is to get rid of them - as soon as there's support for editing sections in SF (as opposed to just templates), I think partial forms can be gotten rid of. Until then (and afterwards as well), you can definitely use ""pseudo-partial"" forms - regular forms that only have a small subset of the fields.",1329248569,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+SemanticForms: Partial forms and nested templates.,"**van.de.bugger** wrote:
+
+> formally it is declared as partial form, so it does not have to
+save non-used fields of main template, does it?
+
+Oops, of course it should be:
+
+formally it is NOT declared as partial form, so it does not have to
+save non-used fields of main template, does it?",1328917343,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-yjmyhigfoa4mxqt7ha7t,task_subcomment,NA
+Hitting enter on an empty list item should end the list,"Or at least Aryeh thinks so; I guess this is disputable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1328023740,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ewjtzp76256uwhrcagor,task_description,resolved
+Hitting enter on an empty list item should end the list,Related: https://bugzilla.wikimedia.org/show_bug.cgi?id=48287,1368090037,PHID-USER-qmcrs2npimuywblubznv,False,PHID-TASK-ewjtzp76256uwhrcagor,task_subcomment,NA
+Hitting enter on an empty list item should end the list,Noting bugs closed in the 2012-10-15 release.,1351534185,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ewjtzp76256uwhrcagor,task_subcomment,NA
+Hitting enter on an empty list item should end the list,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341828,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ewjtzp76256uwhrcagor,task_subcomment,NA
+Hitting enter on an empty list item should end the list,Fixed with new version of VE.,1340401239,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ewjtzp76256uwhrcagor,task_subcomment,NA
+VisualEditor: Ctrl+Home / Ctrl+End don't navigate the cursor to the beginning/end of the document,"Pressing Ctrl+Home should send the cursor to the start of the document, but instead it sends it to the start of the line (same behavior as home). Similarly for Ctrl+End.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1328023500,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-ct4l6w4mrliejtnz6hwi,task_description,resolved
+VisualEditor: Ctrl+Home / Ctrl+End don't navigate the cursor to the beginning/end of the document,"**orbit** wrote:
+
+This works now.",1349999703,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ct4l6w4mrliejtnz6hwi,task_subcomment,NA
+VisualEditor: Ctrl+Home / Ctrl+End don't navigate the cursor to the beginning/end of the document,"Mass-move out of ""General"" to ""ContentEditable"".",1340415381,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ct4l6w4mrliejtnz6hwi,task_subcomment,NA
+VisualEditor: Ctrl+Home / Ctrl+End don't navigate the cursor to the beginning/end of the document,Mass-moving items into VisualEditor product,1340402777,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ct4l6w4mrliejtnz6hwi,task_subcomment,NA
+ApiQueryParseTree doesn't work when XML format is requested,"**Author:** `neilk`
+
+**Description:**
+Something like this query:
+
+    http://wiki.ivy.local/w/api.php?action=query&prop=parsetree&titles=Main%20Page&format=json
+
+Returns a sensible data structure. However, when formatted as XML, an error is returned:
+
+    Warning: htmlspecialchars() expects parameter 1 to be string, object given in /Users/neilk/Sites/trunk/includes/Sanitizer.php on line 978
+
+I've tried other variants and sometimes I do get reasonable XML back but with empty contents. Is it not possible for the API to return arbitrary PHP data structures? Is there something to be done with 'indexed tags'?
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1327970460,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rgsze6qyeosq3v4u4bgt,task_description,invalid
+ApiQueryParseTree doesn't work when XML format is requested,Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.,1350341879,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rgsze6qyeosq3v4u4bgt,task_subcomment,NA
+ApiQueryParseTree doesn't work when XML format is requested,Fixed with new version of VE (code replaced).,1340400724,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-rgsze6qyeosq3v4u4bgt,task_subcomment,NA
+ApiQueryParseTree doesn't work when XML format is requested,"**neilk** wrote:
+
+The code in question was added r110344.",1328025602,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-rgsze6qyeosq3v4u4bgt,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"**Author:** `utsavsabharwal`
+
+**Description:**
+It would be great if could add following shortcuts:
+
+ctrl + { <-- For decreasing font size upto Heading 6
+ctrl + } <-- For increasing font size upto Heading 1
+
+Lemme know if I can help you out :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1325686440,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_description,resolved
+VisualEditor: Add keyboard shortcut for heading level,"Some feedback on the choice of shortcuts:
+http://lists.wikimedia.org/pipermail/wikitech-l/2013-September/071684.html
+(http://www.gossamer-threads.com/lists/wiki/wikitech/388134)",1378657723,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Change 81605 merged by jenkins-bot:
+Add keyboard shortcuts for formatting tools
+
+https://gerrit.wikimedia.org/r/81605",1378254410,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Change 81605 had a related patch set uploaded by Jforrester:
+[WIP] Add keyboard shortcuts for formatting tools
+
+https://gerrit.wikimedia.org/r/81605",1377736667,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Unfortunately the ⌘ + 1 -> ⌘ + 8 are taken by the browser in Chrome for ""switch to tab 1…8"", and ⌘ + 9 is for ""switch to final tab"".
+
+I'm going to go our own way (whee) with:
+
+* ⌘ + Alt + 0 -> Paragraph
+* ⌘ + Alt + 1 -> Heading 1 (Page title)
+* ⌘ + Alt + 2 -> Heading 2 (Heading)
+* ⌘ + Alt + 3 -> Heading 3 (Sub-heading 1)
+* ⌘ + Alt + 4 -> Heading 4 (Sub-heading 2)
+* ⌘ + Alt + 5 -> Heading 5 (Sub-heading 3)
+* ⌘ + Alt + 6 -> Heading 6 (Sub-heading 4)
+* ⌘ + Alt + 7 -> Preformatted
+
+And potentially:
+
+* ⌘ + Alt + 8 -> Blockquote (when that is working)
+
+This isn't great, but it's the least-bad option that I can see.",1377716311,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Confluence seems preferable, mainly because it has one less key.  I'm not sure how many people are familiar with either, and people who know the Word shortcuts will have to disregard Ctrl + Alt + 4 either way.",1374037058,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"(In reply to comment #5)
+> This is typically done with ctrl+alt+# in Microsoft Word on Windows, where #
+> is a number between 1 and 3. 
+> 
+> I'm not sure if this is the right way to go, but at least there's some
+> precedence.
+
+Microsoft Word:
+* Ctrl + Shift + N -> Paragraph (⌘ + Shift + N on Mac)
+* Ctrl + Alt + 1 -> H1 (⌘ + Alt + 1 on Mac)
+* Ctrl + Alt + 2 -> H2 (⌘ + Alt + 2 on Mac)
+* Ctrl + Alt + 3 -> H3 (⌘ + Alt + 3 on Mac)
+* Ctrl + Alt + 4 -> € (hello, Europe!)
+
+Confluence:
+* Ctrl + 0 -> Paragraph (⌘ + 0 on Mac)
+* Ctrl + 1 -> H1 (⌘ + 1 on Mac)
+* Ctrl + 2 -> H2 (⌘ + 2 on Mac)
+* Ctrl + 3 -> H3 (⌘ + 3 on Mac)
+* Ctrl + 4 -> H4 (⌘ + 4 on Mac)
+* Ctrl + 5 -> H5 (⌘ + 5 on Mac)
+* Ctrl + 6 -> H6 (⌘ + 6 on Mac)
+* Ctrl + 7 -> Preformatted (⌘ + 7 on Mac)
+
+Should we adopt the Word ones (which are more common but less relevant) or the Confluence ones (which are a perfect fit for our needs, but less commonly-known)?",1371056324,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"This is typically done with ctrl+alt+# in Microsoft Word on Windows, where # is a number between 1 and 3. 
+
+I'm not sure if this is the right way to go, but at least there's some precedence.",1345668861,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,Standardise title.,1341257162,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Mass-move out of ""General"" to ""ContentEditable"".",1340415517,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,Mass-moving items into VisualEditor product,1340402770,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+VisualEditor: Add keyboard shortcut for heading level,"Not sure if we want key bindings for toggling formatting type? Also, not sure if we want to use these particular ones. :-)",1340398744,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-4vao55kg5dno6lnw3rh7,task_subcomment,NA
+"When translating a string at translatewiki.net, there should be a screenshot of the page where the string is used","- document the idea at [[ https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects | Mentorship programs/Possible projects ]]
+- this project would use a lot of code from existing VisualEditor screenshots project",1416494621,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-nx6rwv65d53u3tb74upy,task_description,declined
+"When translating a string at translatewiki.net, there should be a screenshot of the page where the string is used","Move to MediaWiki, because Translate and TWN already support this. It's ""just"" about producing the screenshots and adding them to qqq.
+
+I'm not sure how many components are using https://commons.wikimedia.org/wiki/Special:Contributions/LanguageScreenshotBot but perhaps that feature can be promoted more. There are some devs who love screenshots for documentation but are probably unaware of the feature.",1427879127,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-nx6rwv65d53u3tb74upy,task_subcomment,NA
+"When translating a string at translatewiki.net, there should be a screenshot of the page where the string is used",I do not plan to work on this any time soon. Please reopen if you care about this.,1427800770,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-nx6rwv65d53u3tb74upy,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","All the items in https://bugzillapreview.wmflabs.org/tag/visualeditor-data_model/ should also be in the main VisualEditor project, which is currently called https://bugzillapreview.wmflabs.org/tag/visualeditor-general/ (and per {T856} won't be re-named until after the import).
+
+I support the ~8000 bugs //could// all just be mass-added(?) after the import, but this feels like a perfect opportunity to get it done right from the start.",1414167177,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_description,declined
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","Cf. T100, T72, T101 on subprojects and parent projects.",1416843686,PHID-USER-v7bwpq3rs3zdxegibdbh,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#15852, @Jdforrester-WMF wrote:
+> Because the saved searches for Phabricator work the way they do, this means that every month or so we'd need to ping out an e-mail to everyone who might care about VisualEditor telling them to forget the old search URL and use a new one.
+
+According to your previous post, this query was meant to be used basically by the development team leadership. Even if not, I personally think that a query URL posted and updated at the parent project description would be more useful than flooding the parent project with >1000 tasks. HOWEVER,  none of this really matters. You are the product owner and you decide how you want to organize your projects.   :)
+
+Back to the initial request, it looks clear at this point that //tagging tasks also against a super-project// is more a particular approach than a solution for everybody. Therefore, we will not touch the migration script, and we will leave this decision to project owners, who can do this manually pretty easily with batch edits.
+
+Resolving as Declined.",1414491978,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#15771, @Qgil wrote:
+> I still don't see why you cannot do what you explain with the search query I'm proposing. 
+
+[Snip]
+
+The number of sub-projects inside VisualEditor changes quite frequently. Right now they are tracked by a combination of Bugzilla tracking bugs (mostly for features) and Bugzilla components (for code areas and types of problem). On average I'd say a new project comes along every month or so.
+
+Because the saved searches for Phabricator work the way they do, this means that every month or so we'd need to ping out an e-mail to everyone who might care about VisualEditor telling them to forget the old search URL and use a new one. The only way to work around this, AFAIAA, is to cheat with a mega-project that is added to everything anyway.
+
+I'm sure you've considered this and decided that for Phabricator you don't need it, which is awesome, but some of us do. :-)
+
+> PS: ACL has nothing to do with this discussion, and I suspect it doesn't work as you think it works. See https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Policy
+
+Well, no. The **team** ""VisualEditor"" will have special status in the ACL of the ""VisualEditor"" **repos** but probably not needed in the ACL of the ""VisualEditor"" project's **tasks**. Probably.",1414436055,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","I still don't see why you cannot do what you explain with the search query I'm proposing. 
+
+Let me explain you the situation of the Wikimedia Phabricator team, which is very similar to your case. We don't have a mega-project. In most cases, tasks that can go to a specialized project are not listed under ""Phabricator"". If we want to triage tasks tasks regardless of the subproject they are in, we only need to query https://phabricator.wikimedia.org/maniphest/query/q47HlqJVpTSy/
+
+One list, all tasks, grouped by priority. And still someone can go to ""Phabricator"" and get a sane list of tasks, because we are not duplicating by default. We did that at the beginning, and it didn't take long before we moved away. If we want to aggregate, we can use saved queries, leaving the default/general projects genuinely for tasks that don't fit anywhere else (just like you have in Bugzilla, btw).
+
+PS: ACL has nothing to do with this discussion, and I suspect it doesn't work as you think it works. See https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Policy",1414429979,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14800, @Qgil wrote:
+>>>! In T859#14527, @Jdforrester-WMF wrote:
+>> the ""general"" bucket is just a ""triage me"" one, and a general-overview list of top-end priorities.
+> 
+> I'm not sure a list with ~8000 bugs is useful to ""triage me"" anything. Besides, you can just get that list with a saved search query whenever you need it.
+
+No.
+
+All new VE bugs go into the VE mega-project (with a status of ""Needs triage""). As part of the triage, it will be given a priority and added to one or more projects of which it's a part – //e.g.// ""VisualEditor MediaWiki integration"" or ""VisualEditor table editing"" or ""VisualEditor ContentEditable"" or ""VisualEditor performance"" or whatever.
+
+Most people will care about a particular feature or aspect of functionality, and so will only follow those particular projects. A few people, like the development team leadership, will want to see the overall priorities across the whole of the VisualEditor mega-project to decide whether to pull resources from one area and put it into another. The ACL for merge/etc. access will also belong to members of the VisualEditor mega-project (probably), as more fine-grained control is not needed and locking-down controls is against our general ethos at Wikimedia.
+
+Does this make sense?",1414426067,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14527, @Jdforrester-WMF wrote:
+> the ""general"" bucket is just a ""triage me"" one, and a general-overview list of top-end priorities.
+
+I'm not sure a list with ~8000 bugs is useful to ""triage me"" anything. Besides, you can just get that list with a saved search query whenever you need it.
+",1414191829,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14527, @Jdforrester-WMF wrote:
+> the ""general"" bucket is just a ""triage me"" one, and a general-overview list of top-end priorities.
+
+I'm not sure a list with ~8000 bugs is useful to ""triage me"" anything. Besides, you can just get that list with a search query.
+",1414191799,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14564, @Qgil wrote:
+> Also, wouldn't the right solution be to move the ""General"" tasks to the main project and then archive the ""General"" project?
+
+Yes, that's what T856 said. Except that there is no ""main project""; ""General"" is the principal project.",1414179922,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","Also, wouldn't the right solution be to move the ""General"" tasks to the main project and then archive the ""General"" project?",1414173470,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14534, @Aklapper wrote:
+> Umbrella projects: If you don't want to spend time manually adding super-projects to task in projects there needs to be some rule or even code to automatically do that... 
+
+Sure, that's what Herald is for. :-)
+
+> In general we prefer to keep the Bugzilla-to-Phab import code simple and not handle project rename requests in there.
+
+Yeah, fine for {T856} to be fixed manually by me after the migration. If necessary, I can fix this request manually too after the migration, but….",1414168616,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","Umbrella projects: If you don't want to spend time manually adding super-projects to task in projects there needs to be some rule or even code to automatically do that... 
+
+In general we prefer to keep the Bugzilla-to-Phab import code simple and not handle project rename requests in there.",1414168506,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too",">>! In T859#14519, @Qgil wrote:
+> Different teams might want to deal with this situation in different ways. You are saying: all tasks in a subproject must be added to the parent project as well. Others might prefer the current situation, where tasks in a subproject are not ""duplicated"" in a parent project.
+> 
+> For instance, this is what we are doing in the Phabricator project. As soon as a task is defined as ""Code-Review"" or ""Project-Management"", we usually place them in these subprojects only, removing them from ""Phabricator"" unless for some reason we want to keep it as a reminder. This keeps the parent project backlog still usable, allowing us to put some attention to the tasks that are not placed in some other subproject.
+
+Sure, but for the projects I listed the ""general"" bucket is just a ""triage me"" one, and a general-overview list of top-end priorities.",1414167914,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+"Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too","Different teams might want to deal with this situation in different ways. You are saying: all tasks in a subproject must be added to the parent project as well. Others might prefer the current situation, where tasks in a subproject are not ""duplicated"" in a parent project.
+
+For instance, this is what we are doing in the Phabricator project. As soon as a task is defined as ""Code-Review"" or ""Project-Management"", we usually place them in these subprojects only, removing them from ""Phabricator"" unless for some reason we want to keep it as a reminder. This keeps the parent project backlog still usable, allowing us to put some attention to the tasks that are not placed in some other subproject.
+",1414167756,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-kjrhrj6aczzaskvfkmpl,task_subcomment,NA
+High level overview of Phabricator projects,"Is this something that we want to have before the launch, right after the launch, or whenever it is ready?
+
+> [[ https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079117.html | On Wed, Oct 22, 2014 at 8:02 AM, David Cuenca  wrote ]]:
+> 
+> Tagging is just a poor man's
+> version of classing, since it doesn't let you define the relationship
+> between tags. True that you can put any task in several projects/tags, the
+> problem is that the project structure is nevertheless flat:
+> https://phabricator.wikimedia.org/project/query/all/
+> Which will become cumbersome to navigate for occasional visitors as the
+> number of projects goes up.
+
+Sure, but after years of Bugzilla we have also seen that the rigid tree structure of https://bugzilla.wikimedia.org/describecomponents.cgi causes many problems too, and occasional visitors probably find it cumbersome anyway.
+
+If we want a high level overview of the projects, we can always have a wiki page identifying the main teams/projects, the starting points to understand the hundreds of projects that we will have soon. Now there is a task to discuss this.  :)",1414075117,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_description,declined
+High level overview of Phabricator projects,"1. Regarding Bugzilla's product-component tree structure vs. Phab's flat namespace, soon the way to go in Phabricator will be using subprojects (see T123078) instead of some external wiki page listing connections or hierarchy between Phab projects.
+2. I consider http://www.mediawiki.org/wiki/Phabricator/Projects sufficient, and if $someone considers it not sufficient, $someone please write a wikipage for what is wanted here (and/or reopen this task and assign it to themselves), or enhance the code that creates http://www.mediawiki.org/wiki/Phabricator/Projects to fulfil their needs.
+1.+2. together: Hence I'm declining this task.",1453296382,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"We do have http://www.mediawiki.org/wiki/Phabricator/Projects nowadays (which is created automatically). That's probably where to continue here.
+
+That current script misses certain contextual knowledge, e.g. that a project named ""Flow"" is technically a ""MediaWiki extension"", or that ""FR"" is the same as ""Fundraising"". Not sure how that could be implemented.",1433945046,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,I'm going to remove ECT 01/2015 from this. It's a nice to have but I don't think I'll have time to work on this in January,1420635098,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"We have scheduled this task for #ECT-January-2015 but it has no owner. Based on lessons learned, we should either get an owner for it or remove it from the sprint.",1420616338,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Maybe you don't have the permissions. No problem, it's here now: https://www.mediawiki.org/wiki/Phabricator/Projects",1418381155,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"@Qgil I have added the draft template to the wiki. However, I cannot find the ""Move"" link. All I see is (From left to right): User Page, Discussion, Read, Edit, Edit Source, View History and Watchlist (The star). Some help is appreciated!",1418373981,PHID-USER-tezy4s5q5b72t2dhoo23,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"@Toolboxx8, you have done a tone of work! Thank you very much. I will close this task as completed now. Just one thing, can you please add a ""{{draft}}"" template at the top of the page (just paste that string using ""edit source"", and then move the page to Phabricator/Projects, please? To move the page just click the ""More"" link in the toolbar.
+
+We will probably massage that page a bit and then create another task to add the descriptions and polish it. As said, I believe you have put enough effort to consider your GCi task closed, even if we will keep this task here open until the page is ready. Thank you again.",1418369289,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"So, I have added links to the list and add a few more projects that were present in Phabricator but not in Bugzilla.
+
+It is still incomplete, mainly the MediaWiki extensions part (there are a lot under it) and the Wikimedia section at the bottom. I have included archived projects while adding a (Archived) note beside the projects, it can be removed if it is not wanted. I also have not include a lot of projects that are in Phabricator but was not in Bugzilla e.g. JavaScript, Jenkins, Human Resource etc.
+
+You can check out the list at : https://www.mediawiki.org/w/index.php?title=User:Toolboxx8/Sandbox
+
+Another problem is at the Common Apps part where all the projects are archived. Should it just be removed? I added a link to the Android project page on Phabricator by the side.
+
+Finally, just out of curiosity as I was going through the list of projects. Under 'Unofficial Apps' the projects listed there use ""or"" instead of ""on"", for example: Wikipedia or Windows 8. Shouldn't it be ""on"" instead of ""or""? Just a minor question.",1418357647,PHID-USER-tezy4s5q5b72t2dhoo23,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"@Aklapper Oh, I see.
+
+Yeah, that makes a lot of sense. As I was browsing through the active projects I couldn't find any that was closely related to those in Bugzilla. Yes, it only states if the projects is new, unconfirmed or patched.
+
+Okay, thanks a lot! I'll see what I can do to improve it further.
+
+@Qgil I will continue to work on it for a while and upload the URL to the GCi page. Is that ok?
+
+I feel that I could still improve the page a little more.",1418351217,PHID-USER-tezy4s5q5b72t2dhoo23,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"I think the current list would be good enough for a GCi task in terms of entries. We can polish these type of details that are quite time consuming for a newcomer but someone like Andre can decide in a whim. I would put my time on linking each entry to its Phabricator project and adding the soft description, if available.",1418326729,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"@Toolboxx8: Thanks for your work on this!
+Referring to your example, Bugzilla product ""Common Apps"" and component ""Android"" became Phabricator project ""Commons-App-Android"" - you can see that listed in the list of all projects under https://phabricator.wikimedia.org/project/query/all/?after=Commoa .
+Note that the project is closed as archived so no new tasks can be filed under it anymore (I guess you looked at the list of //active// projects in Phabricator, which makes sense - we're not interested in listing archived/inactive projects).
+Unfortunately, Bugzilla's describecomponents.cgi does not tell you whether a project is archived or not so that is indeed confusing. :-/
+
+If you have further specific cases where you aren't sure what has happened, don't hesitate to list them here and ask - but in general, don't worry too much if you cannot find some stuff, it does not have to be //totally// perfect. :)",1418320281,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"I have created a clone (quite literally) of the old Bugzilla page: https://old-bugzilla.wikimedia.org/describecomponents.cgi at https://www.mediawiki.org/w/index.php?title=User:Toolboxx8/Sandbox which is almost an exact copy of the old web page.
+
+I have not linked the items to any projects yet as I know the difference between Bugzilla and Phabricator. However, I am unsure of how to link the two together. Some projects that are in Bugzilla are not present in Phabricator. Whereas some projects in Phabricator are not listed in Bugzilla. Any advice on tackling this problem?
+
+Should I edit the project page? For example:
+
+  - Common Apps
+       - Android
+
+becomes
+
+  - Android
+(as in Phabricator) and then add subprojects under this title?
+
+
+
+
+
+
+",1418316119,PHID-USER-tezy4s5q5b72t2dhoo23,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"# Create an account in https://www.mediawiki.org/
+# Then you can go with your browser to a page like www.mediawiki.org/wiki/User:YOUR-USERNAME/Sandbox (changing ""YOUR-USERNAME"" for your actual username)
+# Click ""Create""
+# Type some text. Save. 
+
+There you have your page. Then you can share the URL here while you keep editing by clicking ""Edit"".
+",1418219396,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Hi @Qgil
+
+Thanks for the guidelines! I now understand what is my aim.
+
+However, I have a few questions. Where should the wiki page be? And how do I go about creating one?
+
+I'm sorry but I'm sort of new to creating wiki pages, but I'm willing to learn!
+
+I have search about and read a few articles and watch a few videos but I'm not sure which one to follow. Any suggestions?",1418218630,PHID-USER-tezy4s5q5b72t2dhoo23,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Hi @Toolboxx8, to keep this task simple, 
+
+# please create a wiki page cloning the list of projects shown in this page: https://old-bugzilla.wikimedia.org/describecomponents.cgi, but linking to their current Phabricator projects, which an be found under https://secure.phabricator.com/project/.
+# then, under each project list the subprojects that look more relevant to you, for instance checking the amount of tasks they have listed.
+
+I started a rough example of how this would look like at [[ https://phabricator.wikimedia.org/T833#19869 | at a previous comment ]] in this task.
+
+No need to aim for perfection. If you have a wiki page that looks complete enough for a v0.8, we can continue polishing it.",1418216129,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Hi!
+
+I'm excited in taking part in GCi and taking this task. However, I'm not very sure about my task at hand. I have a rough idea from the description given, but I would like to have a more detailed explanation? 
+
+It says that my proposal should help a newcomer to Phabricator to understand how we use Phabricator for managing projects. Does that mean I'm writing like a tutorial guide? 
+
+Some help is much appreciated! Thanks!",1418183434,PHID-USER-tezy4s5q5b72t2dhoo23,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Heads up! A student has taken this #Google-Code-in-2014 task.
+
+http://www.google-melange.com/gci/task/view/google/gci2014/5777066188341248
+
+Hi toolboxx8! If you have questions, you can ask them here. In addition to the GCi mentors there are other community members that may help you. Thank you for your interest in contributing to Wikimedia!",1417869252,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,Task added to GCI at https://www.mediawiki.org/wiki/Google_Code-in_2014#Category:_Documentation.2FTraining,1415646859,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"I don't think we need a 1:1 mapping of all the projects. After the Bugzilla migration we will have hundreds. The word ""overview"" in the subject of this task is important.
+
+Also, we don't need to perpetuate a Bugzilla tree structure that never made us happy.
+
+We just need a sane list of main areas, identifying the most popular / relevant projects underneath.",1415402096,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"If I understand correctly, we want to start with a 2-column table on mediawiki, that lists:
+1. The existing components in bugzilla, as the structured 2-level tree that they are currently in. (https://bugzilla.wikimedia.org/describecomponents.cgi)
+2. The current list of phabricator projects. (https://phabricator.wikimedia.org/project/query/all/)
+
+----
+Once that exists:
+* A) We'd add a section for anyone to Propose obvious/immediate additions, for column 2. 
+** These proposals would be related to things discussed in T802 and T705. 
+* B) We'd discuss/decide on a logical hierarchy for sorting the items in column 2, for an at-a-glance overview, to help people find the likely project name(s) they want to use in a Task.
+** B1) This might incorporate/adapt the listing/structure given in https://www.mediawiki.org/wiki/Wikimedia_Engineering#Features_engineering , plus other sections from https://wikimediafoundation.org/wiki/Template:Staff_and_contractors 
+** B2) Plus potentially some of the structure from https://meta.wikimedia.org/wiki/Wikimedia_movement
+* C) And we'd also take 1 or 2 key examples of each ""Type"" to add to the docs in https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Type_of_project (only ""Tag"" currently has an example: ""Accessibility"").
+
+----
+
+Q1. Is that fairly accurate?
+
+Q2. What other existing mappings, are missing?
+
+Q3. Are **all** the existing components in bugzilla going to be replicated in phabricator 1-to-1? (""No"" would mean we are also taking this opportunity to remove/merge some of the unused/un-useful components. Either now, or later.)
+
+Q4. Is there a static list of all bugzilla's current ""Product->Component"" options?  (Ideally, I want a copy&pastable 2-level bulletpoint list, of just the names. Otherwise I have to manually copy&paste a few hundred lines...)
+
+(I have zero spare time to guarantee mentoring. But I'd happily contribute thoughts/edits, occasionally. :-)",1415397006,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"...and I am very happy to (co-)mentor this task! 
+Anybody willing to add this to https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks ? (I might do so if nobody is faster)
+
+@Micru and/or @Quiddity: Are you in?",1415385417,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"(Sorry, apparently my brain cannot have all ideas at once)
+
+... and with https://bugzilla.wikimedia.org/describecomponents.cgi as starting point, a student cannot go too too wrong, with just a bit of guidance.",1415365199,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Also, this is a task that @Micru and/or @Quiddity could mentor. You just need to know about Wikimedia, editing wiki pages, and searching projects in Phabricator.",1415365104,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"Also, this is a task that @Micru and/or @Quiddity could mentor. You just need to know about Wikimedia, editing wiki pages, and searching projects in Phabricator to mentor this one.",1415365070,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"We are talking about a wiki page that serves as a list of the main projects (the ones that are important on its own and the ones that act as umbrella of many others). Something like (if only our Bugzilla tree structure would be same). This page shouldn't aim to contain all the projects, probably 2 levels only i.e.
+
+* MediaWiki
+** API
+** Configuration
+** ((some more core components))
+* MediaWiki Extensions
+** VisualEditor
+** MobileFrontend
+** ((a few more selected))
+** See all extensions ((a query to all projects containing the word ""extension"" in the title)
+* (etc etc)
+
+While having a perfect two-level tree isn't trivial, having a first version up to a level that invites experienced contributors to fine tune it is not that difficult.",1415364901,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,"I'm not entirely sure which problem we want to solve. Make people understand what types of ""projects"" we have is already reflected by https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Type_of_project I'd say? 
+Or what else is thought of?
+
+For the records, https://phabricator.wikimedia.org/project/query/all/ lists all archived and active projects.",1415364147,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+High level overview of Phabricator projects,A GCi task?,1415354993,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-bigy3voacwmstnxfox2p,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"This would be useful to identify who is currently working on a card. Helps with visual scanning and clearly shows when certain people are ""hogging"" cards.",1419872102,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_description,resolved
+show avatar of assigned to field on cards displayed in workboard,"As Shaggy once said ""it wasn't me"", but do appreciate the heads up.",1425506265,PHID-USER-izqileijt5niumtehazh,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"CCing @JKatzWMF just to ma sure he is aware of he comment above. No worries, it happens the first time.  :)",1425465421,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,">>! In T85455#1083879, @Jdlrobson wrote:
+> Got it! FYI to newbies like myself there is a barely visible checkbox when you edit project details for Sprint - tick that and boom - magic :)
+
+@jdlrobson: Please do read https://www.mediawiki.org/wiki/Phabricator/Project_management#Sprints and spread the word that there is documentation. I just corrected the wrong icon, the wrong color, and the missing start and end dates of ""Gather Sprint C_"" (the name still violates the [[ https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects | project guidelines ]]).",1425464618,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Got it! FYI to newbies like myself there is a barely visible checkbox when you edit project details for Sprint - tick that and boom - magic :)
+",1425412962,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,That is not a Sprint project.... As in using the Sprint extension (no burndown chart).,1425412866,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,This is so far my biggest pain point about using Phabricator for sprint boards. I can see username but not avatar - how do I get the avatars on https://phabricator.wikimedia.org/tag/gather_sprint_c/board/,1425412673,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Proof: https://phabricator.wikimedia.org/tag/%C2%A7_visualeditor_q3_blockers/
+
+Thank you!",1424351788,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Good! It looks like the cards wuld benefit from some vertical-align: top.
+
+Anyway, @Jdlrobson is the one wanting this feature, and he is a web coder ninja himself... (hint, hint)",1421406939,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"In order to make the cards look better (like Trello), we would have to recreate several upstream UI classes.  
+
+For this image, I opted to use the basic icon class PHUIIconView() which has constants that control the css and celerity resource implementation.  The icon size is set by the constant HEAD_SMALL which makes it 35px square.  This was overridden in a recent update in the phabricator-side-menu-view.css (phabricator-icon-nav .phui-icon-view.phuihead-small) that sets it as 24px square.  This can be seen here: https://phab08.wmflabs.org/project/sprint/board/27/
+
+I do not think that this card style is very nice and it could be improved.  But, the small image is there for now.
+
+",1421910702,PHID-USER-lltif2drabccdkwhet7x,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"In order to make the cards look better (like Trello), we would have to recreate several upstream UI classes.  
+
+For this image, I opted to use the basic icon class PHUIIconView() which has constants that control the css and celerity resource implementation.  The icon size is set by the constant HEAD_SMALL which makes it 35px square.  This was overridden in a recent update in the phabricator-side-menu-view.css (phabricator-icon-nav .phui-icon-view.phuihead-small) that sets it as 24px square.  This can be seen here: https://phab08.wmflabs.org/project/sboard/27/
+
+I do not think that this card style is very nice and it could be improved.  But, the small image is there for now.
+
+",1421405535,PHID-USER-lltif2drabccdkwhet7x,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Thank you! Not bad at all for sprints, where there are less tasks and all of them are supposed to be assigned to someone. I can also see its usefulness in non-sprint projects, but that depends on https://secure.phabricator.com/T4863, which is a longer term game.
+
+I think it would be better to use the smallest version of the avatar, like the one used in the log of tasks (i.e. see above ""Aklapper triaged this task as ""Needs Volunteer"" priority."").
+
+Also, the boxes might need to be arranged differently. Currently the height of the avatar pulls ""Points:"" down, which looks bad and makes the size of the card bigger.",1421052913,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,Check https://phab08.wmflabs.org/project/sprint/board/27/ for demo and test of this feature.  ,1421910747,PHID-USER-lltif2drabccdkwhet7x,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,Check https://phab08.wmflabs.org/sprint/board/27/ for demo and test of this feature.  ,1420215031,PHID-USER-lltif2drabccdkwhet7x,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Change 182463 merged by Christopher Johnson (WMDE):
+adds User image icon to Sprint Board Task Cards
+
+[[https://gerrit.wikimedia.org/r/182463]]",1420214260,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+show avatar of assigned to field on cards displayed in workboard,"Change 182463 had a related patch set uploaded (by Christopher Johnson (WMDE)):
+adds Owner Image Icon to Sprint Card
+
+[[https://gerrit.wikimedia.org/r/182463]]
+
+#patch-for-review",1420213938,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-j5yw5s756nhxpysj3ya6,task_subcomment,NA
+Use URL from foreign file repositories to search for images within VisualEditor,"What I want:
+
+1)  Open page.
+2)  Insert > Image
+3)  Paste in URL (from Commons)
+4)  Insert image
+
+
+What I got:
+
+1)  Open page.
+2)  Insert > Image
+3)  Paste in URL (from Commons)
+4)  No image found.
+5)  Remove most of the URL
+6)  Insert image.
+
+",1418779487,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-v25fzfcgl7xz24bzsekb,task_description,open
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"As a user looking for a report about a MediaWiki core bug, I want to quickly look for it without bothering about non-core reports or specific components/projects, so that I find what I'm looking for before I give up out of desperation.
+
+----
+
+Currently, I must type N MediaWiki core projects manually in the ""Projects"" field. (Cf. https://secure.phabricator.com/T3670#65849, first bullet.)",1417872973,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_description,open
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#5405654, @Aklapper wrote:
+>>>! In T76942#2503522, @mmodell wrote:
+>> I think this discussion deserves to be resurrected now that we have real subproject support in phabricator.
+> 
+> Indeed. I think nowadays the way to go would be converting all current separate `#MediaWiki-*` parent projects which are about the MediaWiki Core codebase (note that not all are!) to [subprojects](https://www.mediawiki.org/wiki/Phabricator/Project_management#Parent_Projects,_Subprojects_and_Milestones) of a **new** `#MediaWiki` or `#MediaWiki-Core` parent project. 
+
+Premising I don't have a 100% big picture of the Wikidata stuff in Wikimedia Phabricator, implementing Sub-Projects makes really sense from me from a Phorge/Phabricator perspective. Everything in the Sub-Projects automatically ends up in the root Project, making any wide search definitively easier, without the need to list all Sub-projects manually.",1684857400,PHID-USER-hphk5jxfxfgl64tpfacw,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#2503522, @mmodell wrote:
+> I think this discussion deserves to be resurrected now that we have real subproject support in phabricator.
+
+Indeed. I think nowadays the way to go would be converting all current separate `#MediaWiki-*` parent projects which are about the MediaWiki Core codebase (note that not all are!) to [subprojects](https://www.mediawiki.org/wiki/Phabricator/Project_management#Parent_Projects,_Subprojects_and_Milestones) of a **new** `#MediaWiki` or `#MediaWiki-Core` parent project. 
+Why a new parent project?
+* A task cannot have both the parent project and a subproject of that parent project associated. So if the already existing project called `#MediaWiki-General` became the parent project and a task is both associated with the `#MediaWiki-General` project and another now-to-become subproject, we'd have data inconsistency in the database due to T224421.
+* Furthermore, when a first subproject is added to a parent project, all of the parent project members shift to the first subproject. Parent projects do not support adding members.
+That's why it would probably make more sense to keep the `#MediaWiki-General` project and **not** make it a parent project, but instead create a new parent project and make the existing `#MediaWiki-General` (or `#MediaWiki-Misc` or whatever to call it) a subproject of that new parent project.
+
+For completeness: A task can have more than one subproject of the same parent project associated (at least when I tested this locally). So there should not be issues having more than one `#MediaWiki-*` now-to-become subproject associated to a task. (Not the case for milestones but we don't talk about milestones here.)
+
+I hope I did not forget any relevant aspects when I wrote this comment.",1565372416,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#5214363, @Aklapper wrote:
+> Also note that nowadays, a lot of MediaWiki core tasks are under `#Core Platform Team` and `#Core Platform Team Backlog` tags. See for example https://phabricator.wikimedia.org/T219524#5070460
+
+That seems like an antipattern (if at all intentional).",1558960835,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Also note that nowadays, a lot of MediaWiki core tasks are under `#Core Platform Team` and `#Core Platform Team Backlog` tags. See for example https://phabricator.wikimedia.org/T219524#5070460",1558955029,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Also note that nowadays, a lot of MediaWiki core tasks are under `#Core Platform Team` and `#Core Platform Tean Backlog` tags. See for example https://phabricator.wikimedia.org/T219524#5070460",1558955015,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"This project is selected for the #developer-wishlist voting round and will be added to a MediaWiki page very soon. To the subscribers, or proposer of this task: please help modify the task description: add a brief summary (10-12 lines) of the problem that this proposal raises, topics discussed in the comments, and a proposed solution (if there is any yet). Remember to add a header with a title ""Description,"" to your content. Please do so before February 5th, 12:00 pm UTC. ",1486164929,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"A question @Nikerabbit asked reminded me of this bug, specifically of the use case: list the #i18n tasks filed against a MediaWiki core/MediaWiki extensions component, to have an overview similar to what was provided by SMW on https://translatewiki.net/wiki/Support/Open_requests#MediaWiki .",1478428446,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"The problem it was blocked on was disabling notifications, right? Having an umbrella project would make sense, with or without subproject support, but Andre has a point about spam.",1469742709,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),I think this discussion deserves to be resurrected now that we have real subproject support in phabricator.,1469742239,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#1287991, @Krinkle wrote:
+> We now have the generic ""Untriaged"" status
+
+There is no such task status but a ""Needs Triage"" priority but the task priority field is [[ https://www.mediawiki.org/w/index.php?title=Topic:Sh94hyx5vqslwf8n&topic_showPostId=shljfgkm296r8vk3#flow-post-shljfgkm296r8vk3 | not used by every team ]] so that does not entirely sound like the same.
+
+> However, considering not all components in MediaWiki core have an appropiate place in Phabricator yet (some are simply too niche or don't fit anywhere) a ""MediaWiki-Core-Misc"" or ""MediaWiki-Other"" component may be useful.
+
+""Misc"" to me is pretty much the same as ""General"" which already is part of the current name... but interpretation of words might be different.
+
+> I've tried to make a complete list of all MediaWiki core components, saved in the profile description of #MediaWiki-General-or-Unknown: https://phabricator.wikimedia.org/project/profile/135/
+
+Uh, thanks! I hope we will remember to update that when needed...",1432130685,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Indeed. ""Unknown"" should not be its own component anymore. We now have the generic ""Untriaged"" status and/or workboard column for that (depending on the project in question).
+
+However, considering not all components in MediaWiki core have an appropiate place in Phabricator yet (some are simply too niche or don't fit anywhere) a ""MediaWiki-Core-Misc"" or ""MediaWiki-Other"" component may be useful. Or perhaps having just ""MediaWiki"" for those suffices, though I do see a use case for being able to query those at ease (and even have a workboard for it). Doing an exclusion search is imho unacceptable. Also because the list of MediaWiki subcomponents will inevitably change over time, and will keep changing a lot in the short term as we identify more components in MediaWiki and move other things out into libraries.
+
+I've tried to make a complete list of all MediaWiki core components, saved in the profile description of #MediaWiki-General-or-Unknown: https://phabricator.wikimedia.org/project/profile/135/",1431701531,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#946690, @Nemo_bis wrote:
+>> rename MediaWiki-General-or-Unknown to #MediaWiki 
+> 
+> Absolutely not. We MUST be able to search stuff in the MediaWiki-General-or-Unknown component. If you rename it #MediaWiki, it will immediately get filled with stuff which is not General-or-Unknown, and phabricator doesn't practically offer search features to counter this. Deleting the project is about as useful.
+
+I disagree with Nemo; renaming sounds like a good idea to me. It won't get filed if the bugs are triaged, and bugs are being triaged.
+
+More important use-case are people filing bugs, who keep accidentally adding them in `#MediaWiki-Core-Team` (perhaps since that's what pops up when searching for ""mediawiki core"" project).",1423514102,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"So I'd propose creating a MediaWiki umbrella project (like VisualEditor or Multimedia) and creating a Herald rule to automatically add that umbrella project to any of the (newly created) tasks in one of MediaWiki Core's ""subprojects"". 
+
+(Big) **But:**
+* Adding that umbrella project to all existing tasks will create a huge number of notifications. We are talking about roughly already 4800 //open// tasks here, and for proper search results I'd prefer including also closed ones which means updating approx. 26000 tasks. I am not sure if we could (ab)use a maintenance window (like T86772) and //somehow// disable mail notifications for that time (@chasemp: Can we do that somehow?), but that's nothing I want to do in ""normal mode"".
+* Adding that umbrella project to all existing tasks via batch-editing will be cumbersome and time-consuming as long as T76152 is not fixed. I could survive that but it'll take some time (26000 / ~100 = 260 actions). Or I need to first play more with / learn Conduit and bots. Meh.
+
+So until these one and a half items are sorted out, we are unfortunately stuck here.",1421603212,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#946690, @Nemo_bis wrote:
+>> rename MediaWiki-General-or-Unknown to #MediaWiki 
+> 
+> Absolutely not. We MUST be able to search stuff in the MediaWiki-General-or-Unknown component. If you rename it #MediaWiki, it will immediately get filled with stuff which is not General-or-Unknown, and phabricator doesn't practically offer search features to counter this.
+
+It is unclear why ""we must"" and who we is. 
+You could search for ""In All Projects: MediaWiki"" && ""Not In Projects: ..."" and save that query. Setting that query up is pretty cumbersome though.",1419858507,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> rename MediaWiki-General-or-Unknown to #MediaWiki 
+
+Absolutely not. We MUST be able to search stuff in the MediaWiki-General-or-Unknown component. If you rename it #MediaWiki, it will immediately get filled with stuff which is not General-or-Unknown, and phabricator doesn't practically offer search features to counter this. Deleting the project is about as useful.",1419841708,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"==== Creating an MW Core umbrella project ====
+
+1) So the proposal is to rename #MediaWiki-General-or-Unknown to #MediaWiki ? If MW Core team is fine with that I am happy to go ahead.
+
+2) Note that for VisualEditor I set up a Herald rule (H10, but T630):
+
+ If ""Projects"" include any of: {VisualEditor-ContentEditable, VisualEditor-ContentLanguage, ...}, then: Add (umbrella) project ""VisualEditor"", every time this rule matches. (""every time"" means even if someone tries to manually remove the Umbrella project that it would be readded again to a task).
+  Is the same wanted here too?
+
+==== Renaming MW Core subprojects ====
+
+Renaming all those MediaWiki-* core subprojects is a separate topic (this task is about searching core tasks). See the list at https://phabricator.wikimedia.org/project/query/all/?after=MediaWiki-a (and ignore some stuff like extensions, ""MediaWiki-Developer-Summit-2015"" project etc.) for those projects.
+If we renamed ""MediaWiki-Database"" to ""Database"" this would collide with the Herald rule that I proposed above - any task with projects ""MediaWiki-extensions-Foo"" and ""Database"" (named ""MediaWiki-Database"" beforehand) would get an automatic ""MediaWiki"" project associated with that rule. I don't think this would be helpful, and if we didn't set up a Herald rule then manually adding the ""MediaWiki"" umbrella project is not a great use of triage time either.
+So with the current situation I'm slightly against using more generic names for those MW core subprojects.",1419806954,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#848212, @Chad wrote:
+>>>! In T76942#848206, @Nemo_bis wrote:
+>>> You'd search for [Database] and not [MediaWiki]
+>> 
+>> Is ""and not"" allowed in the search, filters and workboard definitions consistently? 
+> 
+> I see fields to exclude projects in all these places. Let me clarify:
+> # Go to [[ /maniphest/query/advanced/ | advanced search ]]
+> # Add ""MediaWiki"" to ""Not in Projects""
+
+That's one place, not ""all these places"". For instance the main search has no ""Not in projects"". https://phabricator.wikimedia.org/search/query/advanced/ 
+
+Did you check the search forms of all applications which have knowledge of projects? (I don't even know which those are.)",1419805268,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#848206, @Nemo_bis wrote:
+>> You'd search for [Database] and not [MediaWiki]
+> 
+> Is ""and not"" allowed in the search, filters and workboard definitions consistently? 
+
+I see fields to exclude projects in all these places. Let me clarify:
+# Go to [[ /maniphest/query/advanced/ | advanced search ]]
+# Add ""MediaWiki"" to ""Not in Projects""",1418661734,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> You'd search for [Database] and not [MediaWiki]
+
+Is ""and not"" allowed in the search, filters and workboard definitions consistently? ",1418661493,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#848047, @Nemo_bis wrote:
+>> So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database]
+> 
+> And how to distinguish that from, say, bugs in some extensions with the usage of the database?
+> 
+
+You'd search for [Database] and not [MediaWiki]
+
+> Plus, did we really surrender to the idea that to do a mere search here we'll need to edit tens of thousands bugs to update their tags?
+
+It's more than just search imho. I think the current tags are an awful way to organize bugs and my plan gives us a whole lot more flexibility in this area :)",1418655989,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database]
+
+And how to distinguish that from, say, bugs in some extensions with the usage of the database?
+
+Plus, did we really surrender to the idea that to do a mere search here we'll need to edit tens of thousands bugs to update their tags?",1418654659,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database]
+
+And how to distinguish that from, say, bugs in some extensions with the usage of the database?
+
+Plus, did we realy surrender to the idea that to do a mere search here we'll need to edit tens of thousands bugs to update their tags?",1418654644,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database]
+
+And how to distinguish that from, say, bugs in some extensions with the usage of the database?",1418654510,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"I think this is how it should be done, and I'm personally happy that no less than the MediaWiki team is willing to move in this direction. 
+
+In addition to solving the search fragmentation problem, this also will mean that there will be better piles of untriaged tasks: a very big one (but only one) for all MediaWiki related tasks, and then one for each ""discipline"" (tag), where contributors specialized in that area can help with a first triage regardless of whether they are directly involved in MediaWiki core or not.
+
+One problem to take into account are the mentions to `#mediawiki` the IRC channel. But well, chances that those mentions are written in #mediawiki related tasks are high, and if not, removing the project is easy.",1418376575,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#842969, @bd808 wrote:
+> Can we just rename #mediawiki-general-or-unknown to #MediaWiki?
+
+In my plan that's how I'd do it, then additionally add that tag to all MediaWiki-* tagged tasks and then rename their projects to drop the MW-* prefix.",1418337002,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),Once upon a time in Bugzilla we had a catch all component for Mediawiki:  MediaWiki -> General-or-Unknown.  #MediaWiki sounds good to me.,1418336918,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Here's what I've been saying to do (in a couple of places on IRC already). The current MediaWiki-* tags are awful. Instead, we should have a [MediaWiki] project in which bugs about MediaWiki go. We'd then have things like [Database], [Localization], [Editing], [Parsing] that would get applied alongside.
+
+So then a database bug for MediaWiki core would be tagged [MediaWiki], [Database] instead of [MediaWiki-Database] (or even worse, adding a [MediaWiki-Core]).
+
+The added benefit is that all extensions and other projects will get to use core's general tags like database or javascript for tagging their bugs too.",1418336894,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),Can we just rename #mediawiki-general-or-unknown to #MediaWiki?,1418336760,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),[Project organization needs to primarily work for the project owners and Quim explained above the difference. Feel free to search for items under both the Phabricator and Phabricator.org if you are looking for Phab specific tasks.],1418302543,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> ""Phabricator.org"" project is for upstream requests, and this is clearly not one.
+
+Debatable, but that debate is happening on other reports. Feel free to create another Phabricator subproject for issues with the phabricator.wikimedia.org instance that don't fit your definition of ""specific features and configuration in our instance"".",1418288279,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"> ""Phabricator.org"" project is for upstream requests, and this is clearly not one.
+
+Debatable, but that debate is happening on other reports. Feel free to create another Phabricator subprojects for issues with the phabricator.wikimedia.org instance that don't fit your definition of ""specific features and configuration in our instance"".",1418288265,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"For what is worth...
+
+""Phabricator.org"" project is for upstream requests, and this is clearly not one.
+
+""Phabricator"" project is for specific features and configuration in our instance. I personally think this is not one of these.
+
+""Project-Creators"" is a Phabricator related project to work on tasks related with the creation of projects, and I personally think that this is one of these.",1418287284,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),Please stop removing phabricator-related projects from phabricator-related reports. Searching tickets on this site is hard enough.,1418280960,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"I think a ""MediaWiki Core"" project distinct from the ""MediaWiki Core Team"" project is fine.  It might be a little confusing, but survivable.",1418260891,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"PS: ah, now I understand the confusion. I typed `#MediaWiki-Core` which is an additional hashtag of MediaWiki-General-or-Unknown. Sorry for the confusion. I'll edit my original comment.",1417946902,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),">>! In T76942#823768, @Nemo_bis wrote:
+> Why did you remove the Phabricator project?
+
+Because I don't think the legit problem you are reporting should be solved with a new Phabricator feature, but with the topols we have. 
+
+> This has nothing to do with MediaWiki code.
+
+This is a problem that the #MediaWiki-Core-Team should be aware of, and the solution agreed should work for them in the first place. 
+
+
+> Creating a new project for all MediaWiki core tasks is definitely overkill. 
+
+In my opinion, developing a local Phabricator application to solve this probles is an overkill.
+
+> Also, reusing the MediaWiki-General-or-Unknown name for such a new project is out of question, because we would then be unable to tell ""General/Unknown"" tasks from the others.
+
+Indeed. This is why in my proposal I didn't touch it.
+
+> Lower cost alternatives:
+> 1) a local phabricator application allowing us to do regex search against projects;
+> 2) a local phabricator application which, in the search form, expands a literal ""MediaWiki-*"" to a list of all MediaWiki core projects;
+
+I don't see the lower cost in these proposals. They are far more expensive to develop and maintain.
+
+> 3) a saved search across all MediaWiki core projects, maintained by the bugwrangler and prominently linked by all phabricator search forms.
+
+That would be low cost indeed. If this is a good solution, then this is all we need.",1417946769,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Why did you remove the Phabricator project? This has nothing to do with MediaWiki code.
+
+Creating a new project for all MediaWiki core tasks is definitely overkill. Also, reusing the MediaWiki-General-or-Unknown name for such a new project is out of question, because we would then be unable to tell ""General/Unknown"" tasks from the others. Lower cost alternatives:
+1) a local phabricator application allowing us to do regex search against projects;
+2) a local phabricator application which, in the search form, expands a literal ""MediaWiki-*"" to a list of all MediaWiki core projects;
+3) a saved search across all MediaWiki core projects, maintained by the bugwrangler and prominently linked by all phabricator search forms.",1417941666,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"Why did you remove the Phabricator project? This has nothing to do with MediaWiki code.
+
+Creating another project for all MediaWiki core tasks is definitely overkill. Also, reusing MediaWiki-General-or-Unknown is out of question, because we would then be unable to tell ""General/Unknown"" tasks from the others. Lower cost alternatives:
+1) a local phabricator application allowing us to do regex search against projects;
+2) a local phabricator application which, in the search form, expands a literal ""MediaWiki-*"" to a list of all MediaWiki core projects;
+3) a saved search across all MediaWiki core projects, maintained by the bugwrangler and prominently linked by all phabricator search forms.",1417941627,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"A possible solution:
+
+* Create `#MediaWiki-Core` as a project umbrella (we could even consider the use of the 'umbrella' icon, still with violet background)
+* Batch edit all the tasks in all the MediaWiki Core subprojects and associate `#Media-Core` to them.
+* Create a Herald rule consisting in adding `#MediaWiki-Core` automatically to any task associated with any of the subprojects.
+
+I'm not sure whether this is an overkill or not, but it is very likely that @Nemo_bis is not the only person willing to perform queries across MediaWiki Core components.",1417946933,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?),"A possible solution:
+
+* Create #MediaWiki-Core as a project umbrella (we could even consider the use of the 'umbrella' icon, still with violet background)
+* Batch edit all the tasks in all the MediaWiki Core subprojects and associate #Media-Core to them.
+* Create a Herald rule consisting in adding #MediaWiki-Core automatically to any task associated with any of the subprojects.
+
+I'm not sure whether this is an overkill or not, but it is very likely that @Nemo_bis is not the only person willing to perform queries across MediaWiki Core components.",1417875650,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-vnsbzpm2rpsys35in4is,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"Please split off a #Browser-Support-Opera-12 project from #Browser-Support-Opera. The Presto-based ""classic"" Opera 12.xx (and previous versions) is a completely different browser from the Chromium-based ""new"" Opera 15.xx (and later versions, currently at 26), having completely different and completely unrelated bugs. (There was no desktop Opera 13 or 14.)
+
+Most of the existing bugs under this project seem to be about Opera 12, but new reports are mostly about Opera 15+. I'll be happy to re-triage them (getting the bulk task change permission would probably help).",1417373028,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kozwn3k45tsayt7lttoe,task_description,declined
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,Meh.,1421877681,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"@matmarex: See my questions in T76302#796189 (first part before I unfortunately answered the braoder part).
+We talk about 15 open tickets in total for Opera, and currently I don't want specific projects for versions of one browser (like MSIE-10, MSIE-11 etc). I think 15 tickets is small enough (and in theory, priority could be decreased for ancient Opera codebases), and I don't think that adding more projects to differentiate makes more people use the browser-support tags that we already have. I'm afraid of tagging for the sake of tagging.",1421779333,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"@Aklapper, @Krinkle, After reading your comments, I have no strong argument myself to keep/archive these browser tags.",1417514135,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,">>! In T76302#795544, @Qgil wrote:
+> I guess at least the #Mobile-Web team will find these browser specific tags useful, and I have also seen many VisualEditor bugs being specific to i.e. Firefox.
+
+I'm not questioning the usefulness of a bug report detailing its relation to a specific browser. I'm questioning the use in maintaining tags for them. What would be the added value over simply stating it in the title or description (like we do for the other aspects of a bug, e.g. the page, class, country, user group etc.). Sure it matters, but every other aspect of a task name/description matters too. Is it useful to add tags? Have we used these for queries in the past?
+
+>>! In T76302#796188, @Aklapper wrote:
+> 
+>>>! In T76302#795501, @Krinkle wrote:
+>> We should've dropped this
+> 
+> (..) no information should ever be lost when migrating. (..)
+
+They could've been converted the same way we did ""Severity"", ""Version"" and ""See also"". Simply appended to the bug report (which probably mentions it already in the description and/or title).
+",1417503821,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"There are 15 open tasks with the Opera project tag set so should not be too hard to (re)triage. 
+Do you really also care about closed ones, or about Opera 12 bugs? (Basically: Is this information of any real value or are we just categorizing for the sake of categorizing.)
+
+>>! In T76302#795501, @Krinkle wrote:
+> We should've dropped this
+
+Your ""we"" is not the ""we"" of those folks who had and have a strong opinion that no information should ever be lost when migrating. In any case we could still always archive projects in Phab if we wanted.
+
+
+
+>>! In T76302#795544, @Qgil wrote:
+> I guess at least the #Mobile-Web team will find these browser specific tags useful
+
+At least when it came to the ""Mobile Platform"" field in Bugzilla, it was set zero times in the last 12 months by a mobile team. I can imagine that the absolute number isn't too different for the ""Web browser"" field though I haven't checked.
+
+> A rename might help using them for the purpose they were created. For instance, what about #Opera-Specific, #Firefox-Specific...
+
+That would have been a really good idea for Bugzilla where the ""Web browser"" field had a bug exposure. Now it's rather hidden as yet another project but I think I'd still go for #Opera-Browser-Specific etc.",1417435160,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,"I guess at least the #Mobile-Web team will find these browser specific tags useful, and I have also seen many VisualEditor bugs being specific to i.e. Firefox.
+
+A rename might help using them for the purpose they were created. For instance, what about #Opera-Specific, #Firefox-Specific...
+",1417376275,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ,I think tagging tasks with Browser-Support at all is a wasted effort. We should've dropped this like we dropped the other fields from BugZilla (and imported as plain text in the description).,1417373914,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kozwn3k45tsayt7lttoe,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"This is a huge problem for test automation.
+
+- open any page in VisualEditor
+- toolbar tools are located in `<div class=""oo-ui-toolbar-tools"">`
+- as far as I can see, there is no unique way to access a tool in the toolbar (example: click Insert tool)
+- all of them share the same classes, and none of them have unique attributes, like `id`
+- the only thing that is different is the string (Cite, Insert...), but since it changes when the UI language changes, it is not usable for us
+- our test automation breaks all the time because elements in the toolbar move around, and the workarounds that we have at the moment are all fragile
+- the best solution for us would be if every tool in the toolbar (undo, redo, paragraph...) had an unique id
+- unique classes (or any other attribute, as long as it is unique) would work for us
+- if there is an attribute used for translations, it would work for us, as long as each tool has and unique attribute
+- this is not just a problem in toolbar, but let's start somewhere",1417094720,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_description,resolved
+Tools in the toolbar do not have unique attributes,"Change 174666 merged by jenkins-bot:
+Add classes to toolbar UI elements
+
+[[https://gerrit.wikimedia.org/r/174666]]",1420574566,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#932189, @Esanders wrote:
+> Thanks Amir. On a separate issue - would you be able to work with a JS API in this case, so we know if it's worth implementing?
+
+This is probably a question for @zeljkofilipin. For the sake of language screenshots and testing in general it must be something that will work with Ruby and Selenium, and Zeljko is a far bigger expert in this than I am.",1418937647,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"Thanks Amir. On a separate issue - would you be able to work with a JS API in this case, so we know if it's worth implementing?",1418900427,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"I updated the patch. Now it adds classes only to elements that cannot be found in the DOM by Selenium in any other way. Incidentally, all of these are elements that are identified by a text label, rather than an icon. Where as icons have classes that are the same in all languages, the labels are different everywhere.
+
+I think that the current version of https://gerrit.wikimedia.org/r/#/c/174666/ (Patch set 15) addresses all the comments above.",1418898708,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"A 'better API' in this case would probably be giving groups unique symbolic names, then they could be accessed via 
+```
+ve.init.target.getToolbar().getGroup( 'structure' )
+```
+for example.",1418056141,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"The problem with letting people use these classes for gadgets is they then become an undocumented API. Trevor's point about greppability is that I should be able to see a class in the code and search for it to find out who uses it and what for, this is why we add comments when classes are built dynamically. API's for gadgets should be provided directly via JavaScript, not classnames/ID. ve-test-* obviously smells - but it is clear what it does and obvious what needs to be replaced when we come up with a better API for this particular task.",1418056038,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"I expected that the names that I gave may have to be changed. I'm generally fine with any naming scheme. If everybody is sure that these things are useful for nothing but testing then it can be ve-test-*. I can imagine that these classes can also be useful for community-developed gadgets that do Stuff with the toolbar; there were similar gadgets for WikiEditor. Also, it's kinda odd to have a class with ""test"" in it in usual production version, but that isn't a disaster either.",1417794562,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"I think there is no risk in adding a couple of strings causing any noticeable performance problem. However, if this is how we are going to target things, than I can see this becoming a very common thing, and it won't be a couple of strings, it will be a ton of them.
+
+My worry isn't even that it's ""bloat"" as much as cruft. If the classes are for testing only, then ideally we can namespace them as such. not only is ""ve-ui-TargetToolbar-insert"" not following the lowerCamelCase naming convention, but it's misleading that it's a class used for styling the ve.ui.TargetToolbar's insert object, rather than targeting it for testing.
+
+I recommend we better quarantine such added classes, such that they are easy to grep for later on, should we come up with a less ""duct tape"" approach. Perhaps you could namespace testing classes as ""ve-test"" and describe the actual thing being tested with the class name, such as ""ve-test-insertToolGroup""?",1417726988,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#794364, @Jdforrester-WMF wrote:
+> If you want robust tests, agree to my request to have the browser tests block merge. :-) Right now the tests are a basket case because they don't need to pass in master, which means they often don't. The responsibility for testing software should be with the team building it, and when they break a test they should also fix it. By having browser tests not block merge, they're just out-of-band chaff.
+
+Amen. It would mean some serious work on the tests, but I think this is the only way to go forward. I am not sure I have ever voted -1 when we were talking about making browser tests voting, but my memory could be failing me.
+
+> And I find it hard to believe that I still have to argue that we should have more rigorous testing, rather than a series of hacks. :-(
+
+I am not sure what you mean here.",1417293517,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#793969, @Jdforrester-WMF wrote:
+> Also, if this is a requirement, it should be made in OOUI which ships the toolbar code, not hacked in by one of its clients. Adding the request to the OOUI project.
+
+As far as I am concerned, this is a requirement. Amir and I did the best we could be we were pretty sure we did it wrong. Thanks for letting us know where this belongs to.",1417293154,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#794185, @zeljkofilipin wrote:
+>>>! In T76143#793969, @Jdforrester-WMF wrote:
+>> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+> 
+> This is not about testing //more easily//, this is about having robust test automation. At the moment, our test automation is made up of cardboard and duct tape.
+
+If you want robust tests, agree to my request to have the browser tests block merge. :-) Right now the tests are a basket case because they don't need to pass in master, which means they often don't. The responsibility for testing software should be with the team building it, and when they break a test they should also fix it. By having browser tests not block merge, they're just out-of-band chaff.
+
+>>! In T76143#794289, @zeljkofilipin wrote:
+>>>! In T76143#793969, @Jdforrester-WMF wrote:
+>> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+> 
+> I find it hard to believe that we still have to fight for testability in 2014. If VisualEditor team does not care about it, I give up on test automation of VisualEditor.
+
+And I find it hard to believe that I still have to argue that we should have more rigorous testing, rather than a series of hacks. :-(",1417282502,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#793969, @Jdforrester-WMF wrote:
+> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+
+Do you have any data on how much memory/etc. would be taken by adding a few strings to the page?
+",1417274523,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#793969, @Jdforrester-WMF wrote:
+> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+
+I find it hard to believe that we still have to fight for testability in 2014. If VisualEditor team does not care about it, I give up on test automation of VisualEditor.
+",1417274041,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,">>! In T76143#793969, @Jdforrester-WMF wrote:
+> I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily…
+
+This is not about testing //more easily//, this is about having robust test automation. At the moment, our test automation is made up of cardboard and duct tape.
+
+",1417254153,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"I'm not sure I agree with the premise here, that bloating the DOM model and so taking up more memory/etc. is a worthwhile objective just so we can test more easily… Also, if this is a requirement, it should be made in OOUI which ships the toolbar code, not hacked in by one of its clients. Adding the request to the OOUI project.",1417228637,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"The above patch adds class `ve-ui-TargetToolbar-insert` to the Insert element. Something like this is all we need so far, if VisualEditor team thinks this is the way to go.
+
+Before:
+
+```
+<div class=""oo-ui-widget oo-ui-widget-enabled oo-ui-toolGroup oo-ui-indicatorElement oo-ui-labelElement oo-ui-popupToolGroup oo-ui-listToolGroup"">
+```
+
+After:
+
+```
+<div class=""ve-ui-TargetToolbar-insert oo-ui-widget oo-ui-widget-enabled oo-ui-toolGroup oo-ui-indicatorElement oo-ui-labelElement oo-ui-popupToolGroup oo-ui-listToolGroup"">
+```
+
+Tested in MediaWiki-Vagrant virtual machine with VisualEditor role enabled.",1417096989,PHID-USER-fz7hkyvt4jypl76ieyol,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+Tools in the toolbar do not have unique attributes,"Change 174666 had a related patch set uploaded (by Zfilipin):
+WIP: Add a class to the toolbar button
+
+[[https://gerrit.wikimedia.org/r/174666]]
+
+#patch-for-review",1417094774,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2rcyzuif3kfiujpetxoz,task_subcomment,NA
+VisualEditor: Insert media dialog appears to immediately abort request,"In test2 and production(betalabs does not display the error).
+
+In VE, open any page for Edit and insert Media - ""Uncaught TypeError: undefined is not a function"" is immediately displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1415381700,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_description,resolved
+VisualEditor: Insert media dialog appears to immediately abort request,"The original issue was never reproduced, and the follow-up discussion about immediately aborted requests was apparently addressed in 2015, in {5d8108f229b8a284fc02b29e509bba39bd2142a0}.",1644536360,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_subcomment,NA
+VisualEditor: Insert media dialog appears to immediately abort request,"(In reply to Roan Kattouw from comment #2)
+> Elena showed me that if you open the media dialog on a new page after typing
+> some text and going to a new paragraph, the usual jQuery JSONP abort error
+> thing happens, and it consistently happens every time you open the dialog.
+> This probably means we are sending a request and then immediately aborting
+> it.
+
+We are immediately sending a request every time the search input is changed. In the case of opening the insert dialog, the search input should get the page title, so a request is immediately sent with that. If the request is sent and is immediately aborted even if no other detail was changed (so, if you didn't change the search input at all) then maybe there's an issue with the way the input is updated. But then, the search appears, so the request doesn't seem to be cancelled immediately.
+
+I'm not entirely sure what goes on there with the JSONP failures, but if this is about cancelling requests before they're done, I'm not entirely sure we can do anything about it -- requests are sent when the input is changed, which means that when the user types, we send each request on keystroke. If you're writing a whole word of 5 letters, then you'll get 4 cancelled requests and 1 completed one.
+
+Changing this behavior would mean adding some ""search"" button to do the search on click rather than instantaneously on keystroke, and that's not the behavior we want.",1415390018,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_subcomment,NA
+VisualEditor: Insert media dialog appears to immediately abort request,"Elena showed me that if you open the media dialog on a new page after typing some text and going to a new paragraph, the usual jQuery JSONP abort error thing happens, and it consistently happens every time you open the dialog. This probably means we are sending a request and then immediately aborting it.",1415389734,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_subcomment,NA
+VisualEditor: Insert media dialog appears to immediately abort request,"Works fine for me in production (enwiki), test2 and beta labs.",1415383213,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-h6gl5kl5rbsafwe4bbxb,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Change https://gerrit.wikimedia.org/r/#/c/171326/ shouldn't have to trigger bundle-rubocop.
+
+Affects at least mediawiki-extensions-VisualEditor and oojs-ui repos, probably more. ",1415276340,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-wcav44bst4bw55h5vacr,task_description,resolved
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,Confirmed that Rubocop still runs on //e.g.// https://gerrit.wikimedia.org/r/187166 which has a Ruby file.,1422672991,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Change 187805 merged by jenkins-bot:
+rubocop: Run *-bundle-rubocop only if relevant files were modified
+
+[[https://gerrit.wikimedia.org/r/187805]]",1422672389,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Change 187805 had a related patch set uploaded (by Krinkle):
+rubocop: Run *-bundle-rubocop only if relevant files were modified
+
+[[https://gerrit.wikimedia.org/r/187805]]
+
+#patch-for-review",1422652099,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Unassigning myself, I am not working on it.",1415803868,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+Don't trigger rubocop Jenkins job for changes that only modify php or js files,"Seems we should only trigger it when .rubocop.* or .rb files are changed.
+
+In Zuul something like:
+
+jobs:
+ - name: '^.*-rubocop$'
+   files: '(^\.rubocop\..*|.*\.rb$)'
+
+The same files: statement would have to be added to any other rubocop jobs defined as non voting in the jobs section. Ie:
+
+  - name: mediawiki-core-bundle-rubocop
+    voting: false
++   files: '(^\.rubocop\..*|.*\.rb$)'",1415614370,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-wcav44bst4bw55h5vacr,task_subcomment,NA
+VisualEditor: Tool to set/unset background colour,"For completion.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1415217780,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-kv3qzdtcovilhit5wojg,task_description,open
+"VisualEditor: In the transclusion dialog, show the non-normalised parameter name if available?","Per bug 67657, there's now key.wt going to be available in the Parsoid output; if so, we should show that, not the key name, so that ""foo<!--OMG!-->bar"" is shown as ""foobar"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1414694340,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jx334o6lve2gveakyge4,task_description,open
+"VisualEditor: In the transclusion dialog, show the non-normalised parameter name if available?","Aha, yes.
+
+Still, the comment might be important in some rare cases…",1414694625,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-jx334o6lve2gveakyge4,task_subcomment,NA
+"VisualEditor: In the transclusion dialog, show the non-normalised parameter name if available?","I think it's the other way around: Now the same code would show ""foobar"", and if you want to display ""foo<!--OMG!-->bar"" you'd need to use key.wt.",1414694500,PHID-USER-56wtmb23orq4pu5liyj5,True,PHID-TASK-jx334o6lve2gveakyge4,task_subcomment,NA
+VisualEditor: Provide a way to move pages through interacting with the displayed title,"An often encountered hurdle for new editors is that they can't find out how to move a page. Generally they ask how to ""change the title"". Apparently - and understandably - in their mental model, the title of a page is part of the page. It would be nice if VE could accommodate that model. For that I suggest
+* Make the page title editable
+* If the new page title is a valid title, move the page to that location
+** If the move fails, notify of the failure to automatically change the title, and link to the documentation of the move functionality, suggesting to do it manually.
+* If the new page title isn't a valid title, insert a {{DISPLAYTITLE}} element to the page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1414573980,PHID-USER-n27daagbl3wqf3ghr4nk,False,PHID-TASK-2wlcma4q7b3q3yusckvl,task_description,open
+VisualEditor: Provide a way to move pages through interacting with the displayed title,"This is a perennial request from inexperienced editors.  See, e.g., https://www.mediawiki.org/wiki/Topic:Uuooxecko4mfmnia ",1550858386,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-2wlcma4q7b3q3yusckvl,task_subcomment,NA
+VisualEditor: Provide a way to move pages through interacting with the displayed title,"Hmm. I like this idea. Could get a bit complicated where ""sometimes"" it is moving the page, and ""sometimes"" it's setting the {{DISPLAYTITLE}}, and it's not clear which is which.
+
+Also, moving mid-edit might be complicated on the back-end? MW relies on the title of a page /way/ too much. Something to watch for when we implement.",1414600396,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2wlcma4q7b3q3yusckvl,task_subcomment,NA
+VisualEditor: Inserted images overlap preformatted text box,"images overlap preformatted text box
+
+Betalabs - desktop and mobile
+
+Steps to reproduce: 
+
+1. In VE insert preformatted text 
+2. Insert an image  - observe that the image will be overlapping the preformatted text. 
+
+The two screenshots are attached.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F14713}",1414024200,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3wq7rvzz7yhgz4hc5nya,task_description,declined
+VisualEditor: Inserted images overlap preformatted text box,"At the moment, <pre> blocks and images overlap in the read version of pages too, so we're correct to show the same thing in VisualEditor. I'm declining this; we can file a broader bug if we want to change how the read version looks.",1437696770,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-3wq7rvzz7yhgz4hc5nya,task_subcomment,NA
+VisualEditor: Inserted images overlap preformatted text box,"Created attachment 16892
+desktop - image overlap preformatted area
+
+Added attachment - VE_desktop_images overlapping preformatted text- that displays the issue clearer.
+
+**Attached**: {F14714}",1414186852,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-3wq7rvzz7yhgz4hc5nya,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,"For the very few GCNs that generate wiki-link links (class=new etc.).
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1412891220,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-m2eygkjsu6uashwjrsks,task_description,resolved
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,"Change 345607 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWSaveDialog: Run links through a render function for preview & visual diff
+
+[[https://gerrit.wikimedia.org/r/345607]]
+",1491060129,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,">>! In T73900#3146112, @Esanders wrote:
+> What did you mean by non-template GCN? Extension nodes?
+
+Yes.",1491059495,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,"Change 345607 had a related patch set uploaded (by Esanders; owner: Jforrester):
+[mediawiki/extensions/VisualEditor@master] MWSaveDialog: Run links through a render function for preview & visual diff
+
+[[https://gerrit.wikimedia.org/r/345607]]
+",1490954038,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,What did you mean by non-template GCN? Extension nodes?,1490952931,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,(Uploaded Gerrit change 167249 for that),1413571914,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,Yeah. More with bug 65353 really,1413570393,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes,"In the top template at https://it.wikipedia.org/wiki/Korova_Milk_Bar?veaction=edit ""migliorare questa voce"", which leads to https://it.wikipedia.org/w/index.php?title=Korova_Milk_Bar&action=edit , shows up as red. This is related to this bug, I guess?",1413566926,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-m2eygkjsu6uashwjrsks,task_subcomment,NA
+VisualEditor: Proposed external links should be validated before being created,"Open the link inspector and just type in double slash(forward), click done.It gets inserted in the CE as an external link.
+The external links should be validated for correct format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412776440,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3ojjmktdxwslnqst6zf3,task_description,open
+VisualEditor: Proposed external links should be validated before being created,"I raised this  ticket, because i thought there should be some sort of client-side validation for external link entries.What I mean is, when i type in a ""//"" or ""//foo"" then even the  external link icon should not get inserted to the page. Right now it is only after saving the page,you would see that ""//"" is saved as a text and not a link.",1412960452,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3ojjmktdxwslnqst6zf3,task_subcomment,NA
+VisualEditor: Proposed external links should be validated before being created,"(In reply to Ritu Swain from comment #2)
+> it could follow the HTTP URL syntax.
+
+What is that syntax? What about other protocols? How to define what's ""valid"" without excluding other valid URLs?",1412808976,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3ojjmktdxwslnqst6zf3,task_subcomment,NA
+VisualEditor: Proposed external links should be validated before being created,"(In reply to Andre Klapper from comment #1)
+> [Problem is unrelated to specific browsers hence removing 'Web browser'
+> field entry. ""should be"" -> new feature, hence setting 'Severity' to
+> 'enhancement'.]
+> 
+> (In reply to Ritu Swain from comment #0)
+> > The external links should be validated for correct format.
+> 
+> Do you have any definition (or even regular expression) in mind for ""correct
+> format""?
+> it could follow the HTTP URL syntax.But right now anything that has a double slash(""//"" or ""//foo"") is taken as an external link.",1412793003,PHID-USER-ndwodmhxnp2vypdesdns,False,PHID-TASK-3ojjmktdxwslnqst6zf3,task_subcomment,NA
+VisualEditor: Proposed external links should be validated before being created,"[Problem is unrelated to specific browsers hence removing 'Web browser' field entry. ""should be"" -> new feature, hence setting 'Severity' to 'enhancement'.]
+
+(In reply to Ritu Swain from comment #0)
+> The external links should be validated for correct format.
+
+Do you have any definition (or even regular expression) in mind for ""correct format""?
+*If* the scope of the link inspector is supposed to support URIs as per http://www.ietf.org/rfc/rfc3986.txt this could become complex...",1412785907,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-3ojjmktdxwslnqst6zf3,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"This suggestion comes from Gebruiker:Stratoprutser at nl.wp.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1412346900,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_description,open
+VisualEditor: Make it easier to see that there is an option to paste as plain text,">>! In T73612#3588103, @Prtksxna wrote:
+> Has this come up as a problem again?
+
+There was some confusion about a similar problem (see T174898), but this specific problem hasn't come up. I'm changing priority to reflect the state of things here.",1505130706,PHID-USER-kve2ug5yc3dp6ighnmqk,True,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,">>! In T73612#775328, @Jdforrester-WMF wrote:
+> …so although we could add a ""paste unformatted"" button it would feel very odd…
+
+Where do you think this would make sense? Within the //Insert// menu? One option could be to add it in the right click context menu, but I am sure hijacking that will come with problems of its own.
+
+
+
+
+>>! In T73612#775330, @Jdforrester-WMF wrote:
+> If you couldn't find it then probably others couldn't either; we should keep this open until we come up with a good way to expose this.
+
+
+Has this come up as a problem again?
+",1504790189,PHID-USER-gc5hdyw5p4np7atqjynz,True,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"(In reply to Stratoprutser from comment #4)
+> ok my bad, thanks for the follow-up, closing
+
+If you couldn't find it then probably others couldn't either; we should keep this open until we come up with a good way to expose this.",1412365144,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"**m8r-0p6s0d** wrote:
+
+ok my bad, thanks for the follow-up, closing",1412363214,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"(In reply to Stratoprutser from comment #2)
+> Ah! In Firefox ctrl shift v opens Ad blocks' blockable items dialog, but
+> disabling adblocker indeed pastes unformated.
+> 
+> Not sure if it needs a button or an entry under ""Insert"", but its always
+> nice to have such a hidden feature somewhere exposed?
+
+If you click on the help icon, then ""keyboard shortcuts"" (""Tastaturkürzel"" in German), it is listed there along with the other standard shortcut commands. Unfortunately browsers will not let us provide cut/copy/paste buttons, so although we could add a ""paste unformatted"" button it would feel very odd…",1412362633,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"**m8r-0p6s0d** wrote:
+
+Ah! In Firefox ctrl shift v opens Ad blocks' blockable items dialog, but disabling adblocker indeed pastes unformated.
+
+Not sure if it needs a button or an entry under ""Insert"", but its always nice to have such a hidden feature somewhere exposed?",1412358966,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Make it easier to see that there is an option to paste as plain text,"This is already available via the standard shortcut (Ctrl/Cmd+Shift+V), and it's listed in the dialog of all keyboard shortcuts.
+
+Is this asking for a button to do this as well?",1412354396,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sz5p6z5c3eaapd6a7hxt,task_subcomment,NA
+VisualEditor: Be able to make block-level items centred (and other styles),"A fr.wp editor uses centered lists in his sandbox, https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Brouillon#Le_spectacle  (diff:  https://fr.wikipedia.org/w/index.php?diff=107080711&oldid=107080641 ).
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1409997000,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-bg7mho6ovlk6kuy4oasm,task_description,open
+VisualEditor: Be able to make block-level items centred (and other styles),"I don’t know what was the original issue, but currently, bullets points are kept left because of unexpected list item wrapping in paragraphs (T92441).",1643596968,PHID-USER-unpoeiyj52rmcfqi5rbw,True,PHID-TASK-bg7mho6ovlk6kuy4oasm,task_subcomment,NA
+VisualEditor:  Be able to search for an existing image by name,"Sometimes you know the name of an image, but need to be able to find it on a large page.  It would be convenient if searching (with Command-F or Control-F) could find the image this way.",1409542680,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-aanfzw3dbp4of5eqkf3w,task_description,open
+VisualEditor:  Be able to search for an existing image by name,"If we did this, we would need to highlight the matching text. We could do that by popping open the inspector which contains the matching file name and highlighting inside it. We'd still have to handle the common case of words which don't appear in an inspector because the title is too long, though.
+
+Somewhat similar to T103286.",1437699411,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-aanfzw3dbp4of5eqkf3w,task_subcomment,NA
+VisualEditor:  Be able to search for an existing image by name,"If we did this, we would need to highlight the matching text. We could do that by popping open the inspector which contains the matching file name and highlighting inside it.
+
+Somewhat similar to T103286.",1437699249,PHID-USER-vixhpqcaqfpdj6impfwy,True,PHID-TASK-aanfzw3dbp4of5eqkf3w,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","Hello. As discussed in [[https://it.wikipedia.org/wiki/Discussioni_MediaWiki:Visualeditor-ca-editsource | :it:Discussioni_MediaWiki:Visualeditor-ca-editsource ]] we'd need a way to get the same editing labels of en.wiki (in italian, obviously), that are ""Edit"", ""Edit source"" and ""Edit beta"":
+
+* When VE is disabled by user, show these labels: ""EDIT"" (for wikitext)
+* When VE is enabled, show these labels: ""EDIT SOURCE"" (for wikitext), ""EDIT BETA"" (for VE)
+
+Now on it.wiki there are ""Modifica sorgente"" (edit source) for the classic edit when VE is off and ""Modifica"" (edit) both for the VE edit and for the classic edit when VE is enabled. There's a way to have three different labels to change according to the consensus that emerged?
+
+Thanks,
+Horcrux92
+
+P.S. Sorry for the probably erroneous categorization.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1409484180,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_description,open
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034842, @Aklapper wrote:
+> It was difficult to understand because I assumed you want to potentially display three labels. Initial description wasn't entirely clear. Alright then, thanks for clarifying and your patience :)
+
+Thank to you.
+My probable guilt is I haven't got a very wide english lexicon, so the repetitions in the sentences may be confusing.",1423770458,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","It was difficult to understand because I assumed you want to potentially display three labels. Initial description wasn't entirely clear. Alright then, thanks for clarifying and your patience :)",1423768352,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034779, @Aklapper wrote:
+> Sorry but I'm getting lost here (plus I don't know implementation details as I'm not a developer). 
+> 
+> Could you please edit the task description here and finish these two sentences:
+> * When VE is off: Show these labels in this order: ...
+> * When VE is on, show these labels in this order: ...
+> plus for the case of just displaying ""Edit"", please also explain what ""Edit"" would do (either wikitext or VE).
+> That might things less confusing here. Sorry. :-/
+
+Maybe I should give up...
+
+* When VE is disabled by user, show these labels: EDIT
+* When VE is enabled, show these labels: EDIT SOURCE, EDIT BETA
+EDIT would open the classic edit mode, that is the wikitext editing (ovviously, since VE is disabled).
+
+The labels' names are indicative (they would be editable in the MediaWiki namespace) and I don't care about the order.
+
+Why it is so difficult to understand? It would be the <u>same</u> setting of en.wiki.",1423767505,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034779, @Aklapper wrote:
+> Sorry but I'm getting lost here (plus I don't know implementation details as I'm not a developer). 
+> 
+> Could you please edit the task description here and finish these two sentences:
+> * When VE is off: Show these labels in this order: ...
+> * When VE is on, show these labels in this order: ...
+> plus for the case of just displaying ""Edit"", please also explain what ""Edit"" would do (either wikitext or VE).
+> That might things less confusing here. Sorry. :-/
+
+Maybe I should give up...
+
+* When VE is disabled by user, show these labels: EDIT
+* When VE is enabled, show these labels: EDIT SOURCE, EDIT BETA
+EDIT would open the classic edit mode (wikitext editing).
+
+The labels' names are indicative (they would be editable in the MediaWiki namespace) and I don't care about the order (ovviously, since VE is disabled).
+
+Why it is so difficult to understand? It would be the <u>same</u> setting of en.wiki.",1423767455,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034779, @Aklapper wrote:
+> Sorry but I'm getting lost here (plus I don't know implementation details as I'm not a developer). 
+> 
+> Could you please edit the task description here and finish these two sentences:
+> * When VE is off: Show these labels in this order: ...
+> * When VE is on, show these labels in this order: ...
+> plus for the case of just displaying ""Edit"", please also explain what ""Edit"" would do (either wikitext or VE).
+> That might things less confusing here. Sorry. :-/
+
+Maybe I should give up...
+
+* When VE is disabled by user, show these labels: EDIT
+* When VE is enabled, show these labels: EDIT SOURCE, EDIT BETA
+EDIT would open the classic edit mode (wikitext editing).
+
+The labels' names are indicative (they would be editable in the MediaWiki namespace) and I don't care about the order.
+
+Why it is so difficult to understand? It would be the <u>same</u> setting of en.wiki.",1423767371,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","Sorry but I'm getting lost here (plus I don't know implementation details as I'm not a developer). 
+
+Could you please edit the task description here and finish these two sentences:
+* When VE is off: Show these labels in this order: ...
+* When VE is on, show these labels in this order: ...
+plus for the case of just displaying ""Edit"", please also explain what ""Edit"" would do (either wikitext or VE).
+That might things less confusing here. Sorry. :-/",1423766823,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034429, @Aklapper wrote:
+>>>! In T72230#1034061, @Horcrux92 wrote:
+>> Because ""edit"" is ambiguous.
+> 
+> If that's ambiguous then why request three labels, instead of two that are not ambiguous (classic wikitext editing, VE editing)?
+
+The third one would appear when VE is off and must be independent from the other two (like on en.wiki).
+
+Instead of quote only four words, I please you to try to answer to my two questions.",1423758786,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034429, @Aklapper wrote:
+>>>! In T72230#1034061, @Horcrux92 wrote:
+>> Because ""edit"" is ambiguous.
+> 
+> If that's ambiguous then why request three labels, instead of two that are not ambiguous (classic wikitext editing, VE editing)?
+
+The third one would appear when VE is off and must be independent from the other two (like on en.wiki).
+
+Instead of quote only four words, try to answer to my two questions.",1423758745,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1034061, @Horcrux92 wrote:
+> Because ""edit"" is ambiguous.
+
+If that's ambiguous then why request three labels, instead of two that are not ambiguous (classic wikitext editing, VE editing)?",1423757892,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","Because ""edit"" is ambiguous. Why the basic ""edit"" should be the VE-mode?
+
+We discussed it a lot (as can you see in the page that I linked in the first post) and we'd like to be able to put into practice our decisions.
+
+The real question I'd like to make is: why on en.wiki it's possible to have three distinct labels (two for VE-mode on and one for VE-mode off) and on it.wiki it is not?",1423747546,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp",">>! In T72230#1033724, @Horcrux92 wrote:
+> The problem is that we cannot turn the label ""Edit"" in ""Vidual edit"" without changing the same label for who has got VE off.
+
+I understand that part, but why do you want to turn ""Edit"" into ""Visual edit""? The intention behind this would be welcome and why you think that it's not more confusing.",1423744234,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","The problem is that we cannot turn the label ""Edit"" in ""Vidual edit"" without changing the same label for who has got VE off.
+
+For us this is a problem, maybe not to big but I thought you would have been able to solve it.",1423735683,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","My question ""Which problem do you try to solve?"" is still unanswered though...",1423702519,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","(In reply to Andre Klapper from comment #1)
+> Hi,
+> what would ""Edit Beta"" do if you already have the two other buttons? 
+> Which problem do you try to solve? What's the URL to the discussion?
+
+https://it.wikipedia.org/wiki/Discussioni_MediaWiki:Visualeditor-ca-editsource
+
+We would like to:
+1) edit the label ""Modifica"" (edit) in ""Modifica visuale"" (visual edit) for the edit made with VE;
+2) edit the label ""Modifica sorgente"" (edit source) in ""Modifica"" (edit) for the classic edit (when VE is enabled);
+3) mantain the label ""Modifica"" for the classic edit (when VE is disabled);
+
+And, if I have correctly understood, the 1 and the 3 are impossible to do together, because both of them refer to MediaWiki:Visualeditor-ca-editsource.
+
+The same goes for the label [edit] near the section titles.
+
+If it can be useful, I forget to say that on en.wiki (as you may know) VE is disabled by default, while on it.wiki it's enabled by default.",1409493741,PHID-USER-vzowt52hw2qfnu2w3eim,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+"Provide three editing labels (""Edit"", ""Edit source"" and ""Edit beta"") on it.wp","Hi,
+what would ""Edit Beta"" do if you already have the two other buttons? 
+Which problem do you try to solve? What's the URL to the discussion?",1409490283,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-yueggycui2i6sogbyidl,task_subcomment,NA
+Allow setting all template parameters at once without having to pick which ones to enter,"A Wikipedia editor raised the following problem: When experienced Wikipedians want to add a template in the source editor, they can copy the template code without parameter values, which usually appears on template documentation pages, and then fill all the parameters one by one, and eventually delete the unneeded empty lines.
+
+In VE, parameters must be added one-by-one, and this feels less efficient. As the default behavior this may be OK, but there can be a button that shows all the available parameters.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=72083",1408434360,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-wia5kvwoexms6u3azcgb,task_description,open
+Allow setting all template parameters at once without having to pick which ones to enter,"How would this work? How does VisualEditor know that you wanted a field specified and left blank, vs. haven't set it?",1423675337,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wia5kvwoexms6u3azcgb,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","Lines starting with ; are not recognized as wikitext and just saved, only afterwards revealing their wikitext meaning:
+
+https://wikimania2014.wikimedia.org/w/index.php?title=User%3ADeryck_Chan%2FWMUK_report&diff=49488&oldid=49487
+
+Reported: https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/;caption
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1408359480,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_description,resolved
+"Entering "";"" does not trip the wikitext warning that it won't work","The current behavior in production: 
+;(semi-colon) triggers a warning ""Wikitext markup detected...""
+: (colon) adds <blockquote></blockquote>",1418257749,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","Indeed. This is intentional. Use of a "":"" to ""indent a paragraph"" (as multiple people who are wikitext experts have complained) is a sign that they're doing it wrong. :-) This is a much better outcome for editors – doing what they ""meant"" to do – and for readers.",1417542113,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","I don't think that's exactly correct:  the ; semi-colon and the : regular
+colon are supposed to create association lists (aka definition lists,
+because they're used for glossaries a lot).  I believe that a <blockquote>
+is a different thing.
+
+Whatamidoing (WMF)/Sherry Snyder
+Community Liaison
+Wikimedia Foundation, Inc.",1417539970,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work",Verified in beta and test2 - a semi-colon will trigger a wikitext warning; a colon(:)  - indicates a <blockquote> text.,1417467671,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","Change 175909 merged by jenkins-bot:
+Warn users who write ';' or ':' on a new line that it won't work
+
+[[https://gerrit.wikimedia.org/r/175909]]",1416966214,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+"Entering "";"" does not trip the wikitext warning that it won't work","Change 175909 had a related patch set uploaded (by Jforrester):
+Warn users who write ';' or ':' on a new line that it won't work
+
+[[https://gerrit.wikimedia.org/r/175909]]
+
+#patch-for-review",1416964644,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ysyptgmfd7iy7rypjjx3,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"Goal:   
+
+* Add something to an existing citation that the template shouldn't include, like a {{verify credibility}} tag.
+* Assign a citation to a references group.
+
+
+Steps to reproduce:
+
+1.  Open a page containing a {{cite book}} template.
+2.  Click on the citation to edit it.
+3.  Think, ""Um, I don't actually want this ''in'' the template; I want this ''after'' the template.""
+4.  Give up.
+
+
+~~This can be done, if you happen to know that the thing to do is to select the ref, ignore the tag that pops up, go to the Cite menu, and choose Basic~~ (after Citoid replaced the old Cite menu, this is no longer possible).  But the ability to edit these refs would be more discoverable if the Cite Book dialog had a button at the bottom for ""Use reference editor"".
+",1407967980,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-j43eul4onpngbxmfr2sa,task_description,resolved
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"I'm going to call this resolved, per the previous comment:
+
+>>! In T71498#4868396, @matmarex wrote:
+> It is not exactly easy, but with that patch, it is at least possible again – you can open the ""basic"" reference dialog for citations using Edit → Replace reference → Manual → Basic form. See screenshots in T208981#4868393.
+
+Note that ""Replace reference"" has been renamed to ""Change reference type"" in the final version, but the behavior is otherwise the same.",1601427334,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"Change 483337 **merged** by jenkins-bot:
+[mediawiki/extensions/Citoid@master] Allow any reference to be replaced using Citoid
+
+https://gerrit.wikimedia.org/r/483337",1601391848,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"Change 483337 had a related patch set uploaded (by Esanders; owner: Bartosz Dziewoński):
+[mediawiki/extensions/Citoid@master] Allow any reference to be replaced using Citoid
+
+https://gerrit.wikimedia.org/r/483337",1600944169,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"It is not exactly easy, but with that patch, it is at least possible again – you can open the ""basic"" reference dialog for citations using Edit → Replace reference → Manual → Basic form. See screenshots in T208981#4868393.",1547095979,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,"Change 483337 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/Citoid@master] Allow any reference to be replaced using Citoid
+
+[[https://gerrit.wikimedia.org/r/483337]]",1547095357,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog,{T180104} looks related.,1510253140,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-j43eul4onpngbxmfr2sa,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"MediaWiki: CSS/JS pages on any non-large wiki are usually a mess. Occasionally, we'll discover that wikis have been loading external resources for months and no one noticed. In addition, the local sysops maintaining those pages usually don't know JavaScript and are copy-pasting what someone else told them to do. Even when that's not the case, mistakes can result in code with [[https://szl.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.js&diff=prev&oldid=208782|obvious syntax errors]] being sent to readers for long periods of time.
+
+Various proposals have floated around over the years. The wikitech-l threads have some good discussion on some of the reasons why this is difficult for smaller wikis.
+* Wikitech-l:
+  * [[http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/74283|No longer allow gadgets to be turned on by default for all users on Wikimedia sites]] (specifically about Gadgets though)
+  * [[http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/79080/|Deployment targets and preferences (was: Superprotect user right, Comming to a wiki near you)]]
+* Wikimedia-l: 
+** [[http://thread.gmane.org/gmane.org.wikimedia.foundation/74166|Next steps regarding WMF<->community disputes about deployments]]
+** [[http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/79055/|Superprotect user right, Comming to a wiki near you]]
+
+**See Also**:
+* {T39230} (bug 37230)
+* {T53651} (bug 51651)
+* {T71550}
+* {T121470}
+* {T165981}
+* {T120886}
+* {T171563}",1407872640,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_description,open
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@DannyS712 @Xover
+It would seem that this proposed extension should just perform the functionality. This will likely require installation of Extension:FlaggedRevs or implementing a similar lightweight functionality for the new special page.
+As for handing merging, I propose using Special:MergeHistory to combine the specific revision approved for merge into the original page in MediaWiki namespace. Since this would lockout editing the mediawiki namespace pages, there would be less conflicts. This would retain the historical revision and edit summary in page history as attribution.  As for what happens to the forked page to user subpage, that's for the wiki community to handle as their policy.
+When forking, there should be some coordination to avoid edit conflicts or loss of code functionality. 
+ - Forking user is responsible for maintaining up to date with original page to avoid overwrite. if it does overwrite, previous revision should remain in page history.
+As for the rights based access issue 
+  - Handled by restricting access to the special page with a new user permission. 
+  - When a user who is allowed access to the special page, submits a fork or merge request, extension will check if the user has all these permissions: editinterface, editsitecss, editsitejs, editsitejson. Instead of relying on default usergroups [Interface Administrator], this would allow anyone to use the extension.
+
+ The big question for merging is do we want just the final version of the updated working code or all the subsequent trial & error historical revisions/edit summary?
+
+",1660423743,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#6496321, @DannyS712 wrote:
+> Quick idea version 2 for an extension + workflow
+
+Some quick ""diff"" proposals for your idea (below), with the caveat that I am not convinced this is the way to go.
+
+With the existence of a WMF Gitlab instance in this equation, I'm inclined to think the vast majority of this task's scope should be implemented there, and then it is how to connect the wiki side to the off-wiki (i.e. Gitlab) process that is the main problem. For example, being able to have decision artefacts //on wiki//, holding discussions //on wiki//, and seeing changes in the //on wiki// watchlist. We need some way to gain the other stuff without losing those bits (because they are critical to the long tail of contributors who will never visit Gitlab and have no clue what it is).
+
+>  # User wants to fork a script or gadget to propose a change
+>  #* !!User visits Special:ForkCode, says what the source page is and what the target page is!!
+
+""User selects the //Fork// option in the page actions menu, right next to the //Move// option. The page contents is copied to the same base page name as a subpage of that user's user page. If there is an existing page it is overwritten and there is no option to choose a different name (but the forking can always be done manually as before). A //page property/special MCR slot/ad hoc edit summary syntax// gives the source page for both attribution and subsequent merging reasons.""
+
+It could still be implemented as a special page (that can be used manually), but for the main use case it should be hidden behind some suitable UI and manual user inputs automated.
+
+>  # User submits edit request by requesting on the script/gadget talk page something like ""Please replace with the code currently at User:Me/code.js, which will implement the new feature ABC. This has been tested and consensus supports including the new feature.""
+
+""User requests merge using the //Merge// command in the page actions menu. The page to be merged to is extracted from //page property/special MCR slot/ad hoc edit summary syntax//. The code to be merged is saved as a flagged revision in the target page (NB: clashes with permissions-based access control, may be hard to solve) with a edit summary identifying the source of the merge request for both attribution and review purposes. Location of relevant discussion and consensus etc. is left as a social construct on the local wiki (the sandbox talk page, a central technical or general village pump, etc.).""
+
+>  # Interface administrator uses Special:ComparePages to see what the changes are, and, if they agree to make the edit, continues
+
+""Interface administrator sees //there are flagged revisions// notice on their watchlist, and uses ordinary diff tools to see what the changes are. Presumably a link in the edit summary will lead them to any relevant discussions.""
+
+>  # !!Interface administrator visits Special:MergeCode!!
+
+""Interface admin uses the flaggedrev tools to accept or reject the change, possibly including a manual review comment (possibly identifying the ""main author"" of the code being merged, but source page link and rev history attribution makes that unnecessary).
+
+> This would all be possible within the special pages.
+
+Yes, but with some lightweight UI / process sugar to make it a lot less tedious and prone to human mistakes.
+
+> * Not require database tables, special user rights, integration with external tools, etc.
+
+Modulo the clash between flaggedrevs and rights-based access control that I am uncertain would be reconcilable without major surgery.",1660389890,PHID-USER-3ay4ryrsytga5xa3rqak,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Quick idea version 2 for an extension + workflow (extension part highlighted)
+
+ # User wants to fork a script or gadget to propose a change
+ #* !!User visits Special:ForkCode, says what the source page is and what the target page is!!
+ #* !!Current content of source page is copied to target page, with a summary giving the needed attribution!!
+ # User makes desired modifications
+ # Others test, comment, etc. with normal talk pages
+ # User submits edit request by requesting on the script/gadget talk page something like ""Please replace with the code currently at User:Me/code.js, which will implement the new feature ABC. This has been tested and consensus supports including the new feature.""
+ # Interface administrator uses Special:ComparePages to see what the changes are, and, if they agree to make the edit, continues
+ # !!Interface administrator visits Special:MergeCode!!
+ #* !!provides the page title to be modified!!
+ #* !!provides and the permanent link to the revision of the fork that was approved (in case the page is modified in the middle)!!
+ #* !!provides a comment to be added to the automatic summary!!
+ #* !!provides the name of the user who wrote the new code being merged in!!
+ #* !!Clicks merge!!:
+ #* !!New revision is saved for the target page, implementing the edit request by copying the content from the approved revision. Edit is attributed to approving interface admin (in terms of whose contributions it shown up in, page history, etc.) but automatic summary notes the original author. Something like ""Updating with code written by User:FooBar. (rest of edit summary with explanation)!!
+
+This would all be possible within the special pages. It would:
+* Ensure that only users that can edit the actual gadget/mediawiki ns page/script can edit it using the special page
+* Provide attribution to the original author of the code (user who forked)
+* **Not** handle ""merging"" due to changes made in the script since the fork was created, but the user can just update their fork code; also doesn't deal with official branching, rebasing, etc.
+* Not require database tables, special user rights, integration with external tools, etc.",1601184019,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(completely forgot about this task)
+
+
+>>! In T71445#6265776, @Nux wrote:
+>> User forks a script or gadget in own user space
+> 
+> That would require a special page too. There should be some automatic information about forked version (at least as a oid link in the version history).
+> 
+> The fork information should then be available when merging/comparing.
+
+Sure, the automatic information at the start would be easy, though not sure about using that when merging/comparing since merging/rebasing may be an issue",1601183324,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"> User forks a script or gadget in own user space
+
+That would require a special page too. There should be some automatic information about forked version (at least as a oid link in the version history).
+
+The fork information should then be available when merging/comparing.",1593464204,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#6262201, @Dinoguy1000 wrote:
+> I'm not keen on the amount of work left in the hands of the merging interface admin in your proposal, @DannyS712. In particular, for an extension it should be possible to mark the forked pages as forks and indicate what page they're forked from, and have some mechanism to mark a particular revision as approved, at which point the special page could pull most of the required info automatically from the fork when an iadmin merges it back in. If it's a concern, the special page could allow certain fields to be modified pre-merge (e.g. tweaking the summary), but in general I feel much more comfortable not requiring the iadmin to manually copy so much (less chance for errors to creep in, etc).
+
+Interface admin only copies the approved revision id and the target page, plus its registered as a normal edit and so can easily be reverted.",1593327296,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I'm not keen on the amount of work left in the hands of the merging interface admin in your proposal, @DannyS712. In particular, for an extension it should be possible to mark the forked pages as forks and indicate what page they're forked from, and have some mechanism to mark a particular revision as approved, at which point the special page could pull most of the required info automatically from the fork when an iadmin merges it back in. If it's a concern, the special page could allow certain fields to be modified pre-merge (e.g. tweaking the summary), but in general I feel much more comfortable not requiring the iadmin to manually copy so much (less chance for errors to creep in, etc).",1593326552,PHID-USER-2wibf62nhsbcjs6773je,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"This is an N-of-one experience but I thought I should still share it:
+
+Recently, we decided that the version(s) of Twinkle that we had on fawiki were very old and not worth maintaining and patching; therefore, we decided to pull the latest version of Twinkle and localize it. We put the original code (which is in English, and has some enwiki-only features that we needed to modify or turn off) in the MediaWiki namespace, and made a gadget out of it. Then we also copied the code for each module in Draft namespace (and changed content model to JS) and a group of around 6-7 people started localizing the code. Those who know JS well helped with all aspects of localization, but those who don't only focused on translating Twinkle interface messages from English to Persian.
+
+In your scenario, this is akin to a single fork, in which multiple users are contributing. So regarding your point 5.F above, note that more than one user may need to be attributed.
+
+Each time the forked (Draft) version was merged into the MediaWiki version (by yours truly, and using manual code review + Preview feature of MediaWiki), we synced the Draft version too; that is, if I found an error in the Draft, I fixed it both in the Draft and in the MediaWiki version. If the Draft was further revised from then on, we had to merge again, and we would not want to attribute every contributor again (only those who contributed since the sync). You could argue the forked version in Draft should have been deleted and recreated to have clean history, but I think that is extra work.
+
+I can think of other ways your proposal may not be ideal, but for now, I will only focus on the issue of ""multiple contributors in the 'forked' version"". I like where you are going with this, but I think your model is too simple right now.",1593264047,PHID-USER-p2ebbrj45wupyi25othr,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Quick idea that just came to me for an extension + workflow (extension part highlighted)
+
+ # User forks a script or gadget in own user space
+ # User makes desired modifications
+ # Others test, comment, etc. with normal talk pages
+ # Interface administrator ""approves"" the edit (changes can be seen via Special:ComparePages)
+ # !!Interface administrator visits Special:MergeCode!!
+ #* !!provides the page title to be modified!!
+ #* !!provides and the permanent link to the revision of the fork that was approved (in case the page is modified in the middle)!!
+ #* !!provides a comment to be added to the automatic summary!!
+ #* !!provides the name of the user who wrote the new code being merged in!!
+ #* !!Clicks merge!!:
+ #* !!New revision is saved for the target page, implementing the edit request by copying the content from the approved revision. Edit is attributed to approving interface admin (in terms of whose contributions it shown up in, page history, etc.) but automatic summary notes the original author!!
+
+This would all be possible within a special page. It would:
+* Ensure that only users that can edit the actual gadget/mediawiki ns page/script can edit it using the special page
+* Provide attribution to the original author of the code (user who forked)
+* **Not** handle ""merging"" due to changes made in the script since the fork was created, but the user can just update their fork code; also doesn't deal with official branching, rebasing, etc.
+
+Thoughts? If this had support, I might apply for a rapid grant to write such an extension - shouldn't take too long for a working version to be created",1593251653,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Quick idea that just came to me for an extension + workflow (extension part highlighted)
+
+ # User forks a script or gadget in own user space
+ # User makes desired modifications
+ # Others test, comment, etc. with normal talk pages
+ # Interface administrator ""approves"" the edit (changes can be seen via Special:ComparePages)
+ # !!Interface administrator visits Special:MergeCode!!
+ #* !!provides the page title to be modified!!
+ #* !!provides and the permanent link to the revision of the fork that was approved (in case the page is modified in the middle)!!
+ #* !!provides a comment to be added to the automatic summary!!
+ #* !!provides the name of the user who wrote the new code being merged in!!
+ #* !!Clicks merge!!:
+ #* !!New revision is saved for the target page, implementing the edit request by copying the content from the approved revision. Edit is attributed to approving interface admin (in terms of whose contributions it shown up in, page history, etc.) but automatic summary notes the original author!!
+
+This would all be possible within a special page. It would:
+* Ensure that only users that can edit the actual gadget/mediawiki ns page/script can edit it using the special page
+* Provide attribution to the original author of the code (user who forked)
+* **Not** handle ""merging"" due to changes made in the script since the fork was created, but the user can just update their fork code; also doesn't deal with official branching, rebasing, etc.
+
+Thoughts?",1593251573,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,@Nux Wouldn't a simply way to utilize another namespace where the script or gadget is copied too and anyone that is authorized to make changes only touch that copied version? This way there wouldn't be any merge conflicts when merging back upon reviewer approval and the scripts/gadgets in MediaWiki namespace would be locked as production - live for viewers/users.,1574211681,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"> If we allow forking these to user css/json/js pages, when merging back there could be edit conflicts considering another edit could have been merged and the user didn't pull. How would you suggest keeping a fork to user namespace be kept up to date, might need to keep track of diff changes - this gets complicated?
+
+The problems are the same if users copy the page text. The difference you don't even know which version user copied. You also don't know if user copied text and saved and then did his/her changes or changed something while copying (and saved with the changes).
+
+So if you are merging you don't worry about that. You are reviewing changes as you see them. You either reject or accept them.
+
+Optionally the system can warn you (as a reviewer) that changes were forked before other changes were added. You can then reject and inform user about problems. The user then need to re-fork and re-apply changes. This is also similar to how you can resolve problems on Github.",1574200391,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"> If we allow forking these to user css/json/js pages, when merging back there could be edit conflicts considering another edit could have been merged and the user didn't pull. How would you suggest keeping a fork to user namespace be kept up to date, might need to keep track of diff changes - this gets complicated?
+
+The problems are the same if users copy the page text. The difference you don't even know which version user copied. You also don't know if user copied text and saved and then did his/her changes or did it change something while copying.
+
+So if you are merging you don't worry about that. You are reviewing changes as you see them. You either reject or accept them.
+
+Optionally the system can warn you (as a reviewer) that changes were forked before other changes were added. You can then reject and inform user about problems. The user then need to re-fork and re-apply changes. This is also similar to how you can resolve problems on Github.",1574196756,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"For general issues with forking/merging pages, see T113004. ",1574014937,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"If we allow forking these to user css/json/js pages, when merging back there could be edit conflicts considering another edit could have been merged and the user didn't pull. How would you suggest keeping a fork to user namespace be kept up to date, might need to keep track of diff changes - this gets complicated? Sending the fork to another namespace and keeping it in one location is much better. I am suggesting a simpler system due to these projects not being finished ie partial blocks was meant to become multi-blocks.",1573957857,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think what is needed is forking, not branching.
+
+  # Copy pages (make a fork).  This is not available AFAIK. Sure you can copy text but that doesn't preserve history.
+  # Merge pages (pull request). Kind of available but tricky. You can do some tricks with delete and restore IIRC, but that requires admin rights and is complicated anyway.
+
+Copying would have to be made available to standard users (e.g. user copies Mediawiki:common.css to User:Example/common.css). Then an admin could merge ""User:Example/common.css"" back to ""Mediawiki:common.css"" (visually e.g. by reviewing it as an edit).
+
+Note that both operations would actually be useful for articles as well. You sometimes need to merge articles and there is no nice way to do that.",1573952031,PHID-USER-awklupbdn3wr6glu7nyx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@JEumerus clarified my side note, yeah it was confusing. I was meaning to refer to how js, json, css pages under MediaWiki were split out, did not mean to suggest that EditInterface was a new permission.",1573889449,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Actually, editinterface has been around for a long time. It allows editing of all MediaWiki: namespace pages as they are not all super sensitive, the css and js extra permissions were created because js and css pages in the MediaWiki: namespace and elsewhere are more sensitive than the average MediaWiki namespace page.",1573812811,PHID-USER-cr5rnyhox7s3fl5at22e,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@DannyS712 isn't that the current system that Wikipedia already uses?
+
+Your branching/pull request concept is great! While using existing namespace could work, the need to delete and move seems messy. I think instead of having all of this within the MediaWiki namespace, a second namespace could be utilized. Keeps it much cleaner, though this would require new development resources...
+
+MediaWiki namespace scripts/gadgets would be the version that is activated for users/visitors. 
+Creation of a new namespace such as ""MediaWiki_Staging"" would be where changes are made to the scripts/gadgets as a sort of ""staging"" area, not served to users/visitors. 
+
+any scripts/gadgets from MediaWiki that need changes could then be cloned/pulled into MediaWiki_Staging by click of a button. When ready to submit changes, user clicks a ""submit"" button to send to reviewers (new user permission) and a status message is set to ""Pending Review"". Page would be locked from editing or if an edit is made, status is reset to nothing and review request is canceled.
+
+A special page to list all the pending changes to scripts/gadgets would provide reviewers option to approve or reject with reason.
+  - Approve would set status to ""Accepted"", latest revision is copied to script/gadget in MediaWiki namespace
+  - Reject would reset status back to ""Failed"", no changes occur
+
+side note: based on recent changes to edit access to js, json, css in MediaWiki namespace, It would make more logical sense and add additional protections to add in a configurable variable that acts as a whitelist regarding which of the system messages can be modified, on average only like 10% are ever modified.",1573889381,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@DannyS712 isn't that the current system that Wikipedia already uses?
+
+Your branching/pull request concept is great! While using existing namespace could work, the need to delete and move seems messy. I think instead of having all of this within the MediaWiki namespace, a second namespace could be utilized. Keeps it much cleaner, though this would require new development resources...
+
+MediaWiki namespace scripts/gadgets would be the version that is activated for users/visitors. 
+Creation of a new namespace such as ""MediaWiki_Staging"" would be where changes are made to the scripts/gadgets as a sort of ""staging"" area, not served to users/visitors. 
+
+any scripts/gadgets from MediaWiki that need changes could then be cloned/pulled into MediaWiki_Staging by click of a button. When ready to submit changes, user clicks a ""submit"" button to send to reviewers (new user permission) and a status message is set to ""Pending Review"". Page would be locked from editing or if an edit is made, status is reset to nothing and review request is canceled.
+
+A special page to list all the pending changes to scripts/gadgets would provide reviewers option to approve or reject with reason.
+  - Approve would set status to ""Accepted"", latest revision is copied to script/gadget in MediaWiki namespace
+  - Reject would reset status back to ""Failed"", no changes occur
+
+side note: I know that the editinterface permission plus the new restricted permissions for js, json, css were recently created. There should still be a configurable variable that acts as a whitelist regarding which of the system messages can be modified, on average only like 10% are ever modified.",1573792970,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Implementation with current technical options:
+
+# Have a script or gadgets at `Foo`
+# Copy the (then-current) version to `Bar` (Equivalent of branching)
+# Apply any suggested edits
+# Request that the edits be merged in (Equivalent of opening a pull request)
+# Move `Bar` to `Foo`, deleting `Foo` in the process (Equivalent of merging a pull request)
+# Restore old revisions of `Foo` (to provide continuity of history)
+
+This would
+* Provide attribution to users who suggest the edits (since they are still credited with the revision)
+* Not require new development (perhaps some user scripts to simplify things, but not strictly speaking needed)
+Thoughts?",1573703541,PHID-USER-ilk3nopl66nufkd26tee,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"thanks for letting me know about T205482. Given that Flagged Revs gave me an internal error (VM1844:1 Uncaught TypeError: Cannot read property 'addPortletLink' of undefined) for trying to add in MediaWiki namespace, I do not think that placing effort and time into solving T205482 is worth it.
+
+probably better off creating a new extension either from scratch or reusing elements from Extension Flagged Revs and Moderation. Simple Extension that has Approve/Reject buttons with a special page listing unreviewed .js, .css, Gadgets and preventing unreviewed from going live would be enough for basic usage. Also would allow any wiki to use it, not just WMF.
+
+Last I checked, this task stalled out on deciding a solution.",1538576793,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#4637342, @SpookyGhost8 wrote:
+> I know that a while ago it was mentioned that Extensions Flagged Revs + Code Review could be a potential solution.
+For the records, CodeReview is unmaintained so you'd have to solve T205482 first.",1538564697,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I know that a while ago it was mentioned that Extensions Flagged Revs + Code Review could be a potential solution. I tested yesterday on a small wikifarm and Flagged Revs does not work on the MediaWiki namespace at all, pretty sure I configured correctly. I did not grant myself the autoreview permission and did not use any of the default user groups. Any valid or invalid javascript added to MediaWiki:common.js went live immediately. Trying to hardcode ""NS_MEDIAWIKI"" into extension array resulted in an internal error at Special:UnreviewedPages. Extension:Approved Revs explicitly says that it doesn't work on MediaWiki namespace.
+
+Edit: ""addportlet"" error was my own script, not Flagged Revs",1538619107,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I know that a while ago it was mentioned that Extensions Flagged Revs + Code Review could be a potential solution. I tested yesterday on a small wikifarm and Flagged Revs does not work on the MediaWiki namespace at all, pretty sure I configured correctly. I did not grant myself the autoreview permission and did not use any of the default user groups. Any valid or invalid javascript added to MediaWiki:common.js went live immediately or gave a ""addportlet"" error in my browser console. Trying to hardcode ""NS_MEDIAWIKI"" into extension array resulted in an internal error at Special:UnreviewedPages. Extension:Approved Revs explicitly says that it doesn't work on MediaWiki namespace.",1538531515,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#3613657, @Tgr wrote:
+> the most promising approach is to make MediaWiki sync with the master branch of some remote repo, after which there is no point in rebuilding the code review interface in MediaWiki, since there are plenty decent ones out there.
+
+Now filed as {T187749}.",1519075015,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"another possibility outside of Gadget 2 is a test wiki where any JS, CSS or Lua is tested and then moved over to the main WMF wikis after having a +2 code reviewer approve merging it over. The MediaWiki namespace is mostly interface messages, restricting JS & CSS editing to new permissions might make this safer as well; editusercssJS was split into separate permissions though seems to be limited use cases (someone breaking personal js/css).",1505785630,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think relying on Git is a good idea, but I think you underestimate that by moving contributing to these files to a git, you remove it from direct access from the wiki. I think it will feel like we're taking away control form the community, even if this isn't the intention, as we in some way remove the direct editing possiblity from the wiki and make it more difficult to contribute there for normal user.
+
+We have to find a compromise to minimize this problem, because this wouldn't ever be accepted otherwise. (Many users still remember the js wheel-war between WMF and community at German Wikipedia to well, even if it's been a long time ago and many things have changed.)",1505771008,PHID-USER-4z6eerx3m7iocsrcpku5,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"CodeReview + FlaggedRevs is a possible way to handle this task, although not a good one. SVN-style ""linear"" history sucks for code review (which is why pretty much every single projetc abandoned it when DVCS-s became mainstream), and implementing non-linear history in MediaWiki does not sound like fun, so the most promising approach is to make MediaWiki sync with the master branch of some remote repo, after which there is no point in rebuilding the code review interface in MediaWiki, since there are plenty decent ones out there.",1505709294,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#3612257, @SpookyGhost8 wrote:
+> There also is [[ https://www.mediawiki.org/wiki/Extension:CodeReview | Extension:CodeReview  ]] but status is historical reference, perhaps reopening that for development would be a potential solution?
+
+CodeReview is perfectly stable and usable and (mostly) feature-complete. The `{{Historical}}` template was added to that page by someone who doesn't appear to be familiar with the extension. There is absolutely nothing preventing you from installing and using CodeReview -- or if there is, that's a bug and I'd love to hear about it so that we can get it fixed! Just because something isn't used on Wikimedia's wikis anymore doesn't mean it's flat-out obsolete and/or unusable.
+
+All that being said, CodeReview is mostly a web UI for a Subversion (SVN) repository. The workflow is essentially different when it comes to a SVN repository as opposed to editing on-wiki .css and .js pages: changes to the latter are live immediately, whereas code changes committed to a SVN repo need to be manually deployed by someone.
+It is my firm belief that creating a largely new system for ""code reviewing"" on-wiki .css and .js pages would be the easiest and cleanest solution instead of trying to repurpose CodeReview. In any case, please feel free to add me as a reviewer to CodeReview patches and I'll be happy to review 'em (unless someone else beats me to it, that is).",1505648536,PHID-USER-mlp7cjyksjzemkdr5ued,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"There also is [[ https://www.mediawiki.org/wiki/Extension:CodeReview | Extension:CodeReview  ]] but status is historical reference, perhaps reopening that for development would be a potential solution?",1505587846,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,,1505583022,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,,1505582353,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,From what I remember that was already done in #Gadgets-2.0.,1505580179,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Would it be more secure to possibly add in a few more custom user permissions such as splitting editinterface into editJS and editCSS with also adding in restrictions for template namespace and editLua for Lua? I know that edituserjs&css was split into edituserjs and editusercss. This way the mediawiki namespace would contain the interface messages; all javascript is restricted to .js and users with editJS, all css is restricted to .css and users with editCSS; all lua modules restricted by editLua; possibly restrict templates to editTemplate. Just a suggestion...",1505579931,PHID-USER-sypsy74suppfrytdu4vx,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"In relation to {T158149}, I dare to ask: what is the current status? :)",1505205187,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"See also {T171563}, which I just created for the rest of the problem (pages outside MediaWiki: namespace, still a very large set with some potential vulnerabilities).",1500954964,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Based on my work around T165981 during the 2017 Hackathon - which essentially involved creating a prototype implementation of Wikia's ContentReview extension compatible with core MediaWiki - I would like to note the following:
+
+Creating an extension that just requires site JS to pass certain requirements (manual review, automated tests) before it is served to other users is relatively easy to develop. As discussed above and elsewhere, such a system has been in operation at Wikia since 2015 - its main benefits are that it has a clear workflow, and is tightly integrated into MediaWiki.
+
+I'm on the opinion that if extra code review features are required from this product, such as branching or line comments, implementing them within MediaWiki would be a bad idea. It would have to reconcile MediaWiki's concept of singular multi-revision pages with the paradigm of a branching VCS - an extension implementing this could easily become a highly complex behemoth that is a nightmare to develop, maintain and sustain.
+
+If the decision is to extract the code review functionality from MediaWiki, it is possible to leverage the power of existing VCS and code review tools, such as Gerrit. In this scenario, the setup can be further simplified by completely eliminating JS pages handling from inside MediaWiki. The versatility of ResourceLoader makes it possible to define configurable custom modules that pull their source content from an external data source instead of MediaWiki pages.",1495415465,PHID-USER-c4xszutxtrvtj73h3rns,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Just an idea: what about committing to have an initial plan agreed by the end of Wikimania -- latest? Just an arbitrary date, but a firm one. A driver would be required to stir the discussion and draft plan, though.",1488387037,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Note that, for templates and modules, a branch-like system is already used manually on English Wikipedia (and probably other wikis) via template/module sandbox pages, though there's no hard requirement for their use to propose changes.",1487597449,PHID-USER-2wibf62nhsbcjs6773je,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#3039577, @Samwilson wrote:
+> […]
+> The tricky part of it I think is whether or not it's going to be possible to set up a development environment (or e.g. use an existing test wiki) in which to work on scripts etc. and then easily move them from there to code review and then to the live wiki.
+
+That's why I'd prefer a more universal approach: If you think of a wiki as a whole as a Git (or similar) repository, you could test in a particular ""branch"" (even if for example a change in a template system requires edits to multiple templates pages) and, after testing, merge it to ""master"".  Proposed changes to protected pages could be submitted as branches and, if approved, merged.  Changes to (subelements of) the main page or other portals could be mocked up without having to fiddle with all the dependent links.  Flagged revisions would be a special case where there is a social contract to merge changes to a particular branch regularly.  Users could save their incomplete rewrites of a page in a branch without having to copy & paste it to their computer.  Etc.
+
+That wouldn't make the solution to this task easier, but if the solution to this task already is complex, it would be nice if it solves other use cases as well.",1487591492,PHID-USER-vk6mlmacfhx77egryy5i,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"@MZMcBride: the difference between on-wiki JS and CSS and pretty much any other wiki page (although templates and modules sometimes also fall into this category) is that edits to them can break the whole site for other users. So it's not about trying to limit editing of these to ""professionals"", but just to make it less likely to introduce errors.
+
+Which is why these pages are often protected and left to admins to edit. But even people who know what they're doing (which is all I would take ""engineers"" in the above sense to mean) can make mistakes and would benefit from a process of being able to propose changes and have those changes be easily reviewed by other people before they go live and suddenly make everyone's search autocomplete stop working. :-)
+
+I'd also say that no one seems to be suggesting Gerrit as a solution. I'm not super familiar with Differential, but I guess it's better (or does it just have more whitespace and better-looking buttons?) On the other side of the fence, there's Github and seemingly a lot of people find that relatively easy to use. So surely we can have figure out something that works.
+
+The tricky part of it I think is whether or not it's going to be possible to set up a development environment (or e.g. use an existing test wiki) in which to work on scripts etc. and then easily move them from there to code review and then to the live wiki.
+
+",1487549651,PHID-USER-hlhhe6qw6qfkl7wyfhxk,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1459477, @Krinkle wrote:
+> Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source.
+
+I agree with most of what you write in this comment. I'll note that there's a view that engineer should be treated similar to a term like doctor, and should require at least a degree in engineering. Developers, coders, or programmers might be more apt.
+
+I also don't really love the notion that engineers need to do the engineering (even when broadening the terms to be almost meaningless). Wikipedia is not exclusively written by professional encyclopedists, Wiktionary is not exclusively written by professional lexicographers, Wikinews is not exclusively written by professional reporters, etc.
+
+>>! In T71445#3028613, @Tgr wrote:
+> This was the second (slash third, in a tie) most popular item in the [[https://www.mediawiki.org/wiki/User:Community_Tech_bot/WishlistSurvey/Votes|Developer Wishlist results]]. Any thoughts about the next step?
+
+I would recommend re-reading this task. It's quite long, but contains a lot of good and useful thoughts.
+
+Speaking of engineers and engineering, it strikes me as odd and interesting that the Gerrit code review process isn't really well-liked (cf. {T114419}, etc.), and yet we're expecting the same people to build a ""sane code-review process"" that integrates perhaps Git, perhaps wiki pages, and definitely an even larger and more diverse group of Wikimedians?",1487445102,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"If this could be done as an extension that talks to //any// git repository (as configured by site admins), then it would work with whatever Git code review system people want (i.e. Wikimedia sites could use Gerrit or Differential), and third-party wikis could do it with Github.
+
+An extension could easily update a given set of gadget's pages based on the content of files in a public Git repository somewhere. It'd be really cool if changes made locally could also be pushed out to that repository as review-requests — although perhaps it's more likely that the set up would be that some wikis are configured to //only pull// from the repo (because that's the point of requiring code review after all), and it'd be possible to configure development wikis to send new code to the repo (and to receive updates when the user asks for them).
+
+Is there a possibility that such an extension could be a sort of global gadget system? The code is still duplicated, but it's controlled centrally. Would work for templates and modules too.",1487212377,PHID-USER-hlhhe6qw6qfkl7wyfhxk,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#3028613, @Tgr wrote:
+> I guess first we should determine if this needs to be done inside MediaWiki
+Yes please.
+
+> or the community would accept something based on gerrit/github/whatever (which would be much less work and would provide much better tooling integrartion).
+Gerrit is awful [no citations needed] and GitHub is proprietary, and plenty of people -- developers and users alike -- care about the solution being as FOSS as possible.
+
+Anyway, I don't think doing this as a MediaWiki extension is impossible; there are probably a few tricky questions to solve and whatnot, but considering that [[https://github.com/Wikia/app/tree/dev/extensions/wikia/ContentReview|Wikia managed to implement a similar system]], it should be doable. I'd be interested in helping out where possible to get this thing built.
+",1487165515,PHID-USER-mlp7cjyksjzemkdr5ued,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"This was the second (slash third, in a tie) most popular item in the [[https://www.mediawiki.org/wiki/User:Community_Tech_bot/WishlistSurvey/Votes|Developer Wishlist results]]. Any thoughts about the next step? I guess first we should determine if this needs to be done inside MediaWiki or the community would accept something based on gerrit/github/whatever (which would be much less work and would provide much better tooling integrartion).",1487151515,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"This proposal is selected for the developer wishlist voting round and will be added to a MediaWiki page very soon. To the subscribers, or proposer of this task: please help modify the task description: add a brief summary (10-12 lines) summarizing the problem that this proposal raises, topics discussed in the comments, and a proposed solution (if there is any yet). Remember to add a header with a title ""Description,"" to your content. Please do so before February 5th, 12:00 pm UTC. ",1486164465,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A couple possibilities:
+* write a bot that syncs page content to files on Github (or some other DVCS site to be bikeshedded later), push out the whole code review system there
+* write a proper extension that does that and can load alternative branches / pull requests on demand, a bit like TemplateSandbox
+* repurpose [[https://www.mediawiki.org/wiki/Extension:CodeReview|CodeReview]] to work with page revisions instead of an SVN repo, and pair it with something like FlagRev.
+
+The second option is probably the sane one.",1486114095,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I've been thinking about this task a bit more with {T151408} recently filed. I wonder whether we could implement some kind of social +2 process for on-wiki JavaScript and CSS as a medium-term solution. If we needed to, we could also investigate a technical +2 process, but that's probably overkill for now.
+
+What would a social +2 process look like? We'd try to convince the various wikis to adopt a process of proposing edits on the talk page and having more than one person review the code for sanity before editing the live JavaScript or CSS pages. This type of approach has both the same benefits and detriments as Gerrit's +2 process, of course. Gerrit implements this at a technical level and wikis could as well if needed, but a social process would be more organic and perhaps a better starting point.
+
+A lot of the discussion surrounding security issues related to on-wiki JavaScript editing boils down to this task, I think. A true increase in security would likely only come from some kind of sane and workable code review situation. The other issues (such as bot flags) are peripheral and marginal in comparison.",1480271160,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Would this task be a good topic for the #wikidev17 ? If so, the deadline to submit new proposals is next Monday, October 31: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation",1477575565,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,@Dinoguy1000 thanks for sharing that information !,1446066743,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"As a bit of a case study, Wikia recently experienced [[ http://community.wikia.com/wiki/Thread:890734 | two ]] [[ http://community.wikia.com/wiki/Thread:922459 | attacks ]] which resulted in revoking the ability for admins to edit pages in the MediaWiki namespace (except for a [[ http://community.wikia.com/wiki/Help:System_messages/whitelist | handful of whitelisted pages ]]), user JS being [[ http://community.wikia.com/wiki/Help:Personal_CSS_and_JS#JavaScript | made opt-in]] (and admins not being able to edit other users' CSS/JS any more either), and a [[ http://community.wikia.com/wiki/Help:JavaScript_review_process | review process ]] for sitewide JS instituted (though it's more of a [[ http://community.wikia.com/wiki/Help:JavaScript_review_process#What_are_the_criteria_for_approval.3F | lightweight sanity check ]] than a proper code review).",1446065037,PHID-USER-2wibf62nhsbcjs6773je,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1469730, @demon wrote:
+>>>! In T71445#1459477, @Krinkle wrote:
+>> Or we can enter the realm of Git. [..] I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.
+> 
+> I think it's very important to differentiate between ""using Git"" and ""using Git in the same way we develop MW.""
+
+Completely agree.
+>>! @demon wrote:
+> I can see the argument for Git, but under no circumstances should we subject any more people to Gerrit than we already do [..]
+
+Agreed. The repo shouldn't use Gerrit, and it shouldn't require WMF staff to add users to its access group. I'm pushing for a repo that is first and foremost maintained independently by the community and deployed often (at least weekly; with the option to ride WMF-SWAT deployment schedule for individual changes so they can even push changes twice a day when needed). Phabricator makes sense, but if the community has other suggestions we should consider those as well.",1438022631,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"The idea of Git but not Gerrit for gadget developers is sensible. It fits with T1238 and the idea of bringing gadget developers together and closer to our wider developer community.
+
+I agree that a code review extension for MediaWiki would put us in a costly spin-off. Differential is already enabled [[ https://phabricator.wikimedia.org/differential/query/all/ | here ]] (and in [[ https://phab-01.wmflabs.org/differential/query/all/ | phab-01 ]] if someone wants to play with it). Barriers are obstacles but also defenses. If there are barriers for gadget developers they will be barriers also for other developers. Better work on minimizing common barriers than creating different workflows to achieve the same goals.
+
+The process for deploying patches for gadgets from Differential to Wikimedia projects would need a plan. Would this be the same process as for MediaWiki core and extension patches (meaning that this plan is also blocked on {T18}) or can some shortcuts be taken?
+
+>>! In T71445#1459477, @Krinkle wrote:
+> this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+Nothing that Differential cannot handle, right?",1438006121,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1459477, @Krinkle wrote:
+> Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+> 
+
+Heh, ""tightly controlled."" Yes, you couldn't just sign up...but all you had to do was ask and not be an idiot. Versus now where anyone can sign up, but it's impossible to get trusted access to anything :p
+
+I disagree that there was lack of manpower to maintain ACLs for SVN...we already did...
+
+And...deployment cycles had nothing to do with whether we hosted Gadgets in SVN.
+
+I actually don't even remember a discussion about putting them in SVN, but I am gladly willing to be proven wrong.
+
+> Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.
+
+I think it's very important to differentiate between ""using Git"" and ""using Git in the same way we develop MW."" Right now I think the two are a little conflated (possibly because we've had discussions about doing the latter before).
+
+I can see the argument for Git, but under no circumstances should we subject any more people to Gerrit than we already do; the CR process it enforces is absurd, terrible, and actively scares people away. Also, I don't like the idea of building more infra in/around Gerrit when we're trying to kill the dang thing ;-)
+
+Now, if we want to build something on Phabricator. Or just plain old Git...that could be useful or cool. But let's not ruin all the Gadget maintainers' lives by making them use Gerrit :p",1437534518,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little staffing to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review problem and not all the other problems (being able to use an IDE, having testing, having localisation bot commits, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1605809299,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review problem and not all the other problems (being able to use an IDE, having testing, having localisation bot commits, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1605809262,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations. Of course I'd screw up if you let them drive a plane.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review problem and not all the other problems (being able to use an IDE, having testing, having localisation bot commits, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1437173532,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations. Of course I'd screw up if you let them drive a plane.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review problem and not all the other problems (being able to use an IDE, having testing, having localisation, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1437173381,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"A brief summary of my intent with this ticket:
+
+Users not experienced enough in software development have no business writing code to be executed on all our user's devices.
+
+Everybody is welcome to contribute ideas, create tasks, start polls, etc. but you need an engineer to do the engineering. When I say ""engineers"" I'm not referring to Wikimedia Foundation staff. Instead, it should fully embrace open source. With the added difference that this ""gadget repository"" should be viral. Similar to how wikis hand out access for bureaucrats and sysops. In the common case, all granting and revoking of access in this context should be handled by the community, not staff.
+
+The way and the place in which Gadgets are developed should change. But we should not change the the essential purpose and use case of Gadgets.
+
+I don't believe the purpose of Gadgets was to allow people with no engineering experience to react to user requests, hunt the internet for some scrap pieces of code (without having the faintest idea how the code works), and upload the programs onto the wiki. It's the equivalent of having me pilot an airplane. It's irresponsible and sets unfair expectations. Of course I'd screw up if you let them drive a plane.
+
+If that's not the essence of Gadgets, then what is? The essence of Gadgets is the ability for the community to decide together what and how they want to build features. They can propose ideas and when they agree on an idea, they find other users with the knowledge to make that idea a reality.
+
+Back in 2006, Wikimedia had a tightly controlled repository (SVN). There was little manpower to maintain separate access controls. Deployments were scarce (every 3-6 months). For those reasons, it was not feasible and not reasonable to maintain gadgets in SVN.
+
+Instead we utilised the storage engine behind MediaWiki and appointed users to maintain gadgets that way. This had obvious drawbacks. No way to validate code, no testing, syntax errors, no regression testing or staging. Relying solely on users to catch issues after deployment (e.g. ""saving the page""). It was also hard to maintain the code itself with no support for indentation and other IDE features (due to the HTML textarea semantics). This is why many gadget authors choose to keep their code elsewhere (e.g. on their own computer, or in Git); and merely copying it to the wiki when ""deploying"" the changes.
+
+When adding a code review system of sorts in front of Gadgets, it is inevitable that that system will be a barrier of sorts. We'll do our best to make it easy to use, but there will be an inevitable barrier. The question is, will we choose a barrier in the form of a MediaWiki extension? An extension that nobody will be familiar with, that will not benefit from existing manuals, tutorials, user-friendly desktop interfaces etc. An extension that would only solve the code-review aspects and not all the other aspects (being able to use an IDE, having testing, having localisation, etc.)
+
+Or we can enter the realm of Git. A small barrier that is actually quire //relevant// to software developers. I've encountered plenty of competent hobby programmers with years of experience that hadn't used Git before. It's something new, and yeah, that can be scary. But I doubt it's too complex for someone we expect to be writing code. Especially with all the existing GUI applications for Git.",1437100088,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1018186, @DaBPunkt wrote:
+> This ticket exists to prevent users at Wikipedia of disabling stuff they don’t want.
+Not really.",1423162299,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,No it does not.,1423155874,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1017081, @Krenair wrote:
+> Yes, and it's bad. It's why this ticket exists.
+
+This ticket exists to prevent users at Wikipedia of disabling stuff they don’t want. That’s the hole purpose; not security, not helping, but control. Be at least so frank and say the truth.
+
+Yes, there is the possibility that an admin could do evil stuff with JS; but at Wikipedia we have something called »Assume good faith« and until now it worked great. The users implemented so much stuff in JS and CSS that Mediawiki lacks until today – if you are underused try to fix the software (there are a few thousand bugs in here) and not implement a new kind of force-control. 
+",1423154098,PHID-USER-4nukugv22wnc3p6k557t,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016949, @jayvdb wrote:
+>>>! In T71445#1016916, @Krenair wrote:
+>>>>! In T71445#1016860, @jayvdb wrote:
+>>> And whenever it happens, we can improve the static analysis tools (and desysop the fool who wrote it).
+>> 
+>> I don't think you understand. It's not okay for us to get to this stage.
+> 
+> You're already in this stage.  That is reality.
+
+Yes, and it's bad. It's why this ticket exists.",1423111689,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016916, @Krenair wrote:
+>>>! In T71445#1016860, @jayvdb wrote:
+>> And whenever it happens, we can improve the static analysis tools (and desysop the fool who wrote it).
+> 
+> I don't think you understand. It's not okay for us to get to this stage.
+
+You're already in this stage.  That is reality.",1423103019,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016860, @jayvdb wrote:
+> And whenever it happens, we can improve the static analysis tools (and desysop the fool who wrote it).
+
+I don't think you understand. It's not okay for us to get to this stage.",1423101886,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016685, @Krenair wrote:
+> 
+>>>! In T71445#1016653, @jayvdb wrote:
+>>>>! In T71445#1011829, @Krenair wrote:
+>>> I don't think we can just sandbox JS running on the wiki, @jayvdb
+>> 
+>> Firstly, that isnt what I recommended.  We can perform static analysis of the JS / CSS before it is saved.  Tools exist for this.  It doesnt need to be perfect; the JS is either written by an admin, or enabled by an admin, or a user is enabling a script in their own JS page only.  
+>> More broadly, the scary area is small wikis with few admins, potentially adding code that they dont understand written by someone else, possibly malicious.  Static analysis and ops monitoring suspicious JS page saves can gradually improve static analysis to make it increasingly difficult for malicious code to come via this vector through a sysop to the wiki's Common.js.
+> That's not good enough. It doesn't matter how big/small a wiki is or how many admins it has, that would only affect catching the fact that malicious JS ***has already been added*** by an admin user who is either malicious themselves (e.g. the account was taken over by someone unauthorised, or the actual authorised user was untrustworthy themselves even) or didn't know what they were doing. By then it's too late - we must catch this stuff *before* it can be run on random people's clients, e.g. with a full external code review system.
+
+Did you look at any of the static analysis tools before writing this?  My point is that wikis have a saner environment than many of the other projects who rely on static analysis, as we have less people able to edit the JS.  And whenever it happens, we can improve the static analysis tools (and desysop the fool who wrote it).  We can also run the static analysis tools in over-protective mode, and use {{edit protected}} to engage an JS expert (with a special right) whenever the tool incorrectly detects proposed code as unsafe, due to potential security implications.",1423100125,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016730, @Ricordisamoa wrote:
+>>>! In T71445#1016653, @jayvdb wrote:
+>> Another approach regarding JS is to migrate it to a language which is safer, and compile it into JS.  https://github.com/mherkender/lua.js
+> 
+> Is this a joke? Putting together two bad languages cannot result in a good one.
+> And by the way, MediaWiki embeds lots of 'custom' JS libraries we must be able to use.
+
+A bridge to 'approved' JS libraries would be needed.",1423099544,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1016653, @jayvdb wrote:
+> Another approach regarding JS is to migrate it to a language which is safer, and compile it into JS.  https://github.com/mherkender/lua.js
+
+Is this a joke? Putting together two bad languages cannot result in a good one.
+And by the way, MediaWiki embeds lots of 'custom' JS libraries we must be able to use.",1423098198,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"
+>>! In T71445#1016653, @jayvdb wrote:
+>>>! In T71445#1011829, @Krenair wrote:
+>> I don't think we can just sandbox JS running on the wiki, @jayvdb
+> 
+> Firstly, that isnt what I recommended.  We can perform static analysis of the JS / CSS before it is saved.  Tools exist for this.  It doesnt need to be perfect; the JS is either written by an admin, or enabled by an admin, or a user is enabling a script in their own JS page only.  
+> More broadly, the scary area is small wikis with few admins, potentially adding code that they dont understand written by someone else, possibly malicious.  Static analysis and ops monitoring suspicious JS page saves can gradually improve static analysis to make it increasingly difficult for malicious code to come via this vector through a sysop to the wiki's Common.js.
+That's not good enough. It doesn't matter how big/small a wiki is or how many admins it has, that would only affect catching the fact that malicious JS ***has already been added*** by an admin user who is either malicious themselves (e.g. the account was taken over by someone unauthorised, or the actual authorised user was untrustworthy themselves even) or didn't know what they were doing. By then it's too late - we must catch this stuff *before* it can be run on random people's clients, e.g. with a full external code review system.",1423097598,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1011829, @Krenair wrote:
+> I don't think we can just sandbox JS running on the wiki, @jayvdb
+
+Firstly, that isnt what I recommended.  We can perform static analysis of the JS / CSS before it is saved.  Tools exist for this.  It doesnt need to be perfect; the JS is either written by an admin, or enabled by an admin, or a user is enabling a script in their own JS page only.  
+More broadly, the scary area is small wikis with few admins, potentially adding code that they dont understand written by someone else, possibly malicious.  Static analysis and ops monitoring suspicious JS page saves can gradually improve static analysis to make it increasingly difficult for malicious code to come via this vector through a sysop to the wiki's Common.js.
+
+However there are ways to sandbox JS. Again, tools exist and are in production. https://en.wikipedia.org/wiki/Caja_project 
+
+Another approach regarding JS is to migrate it to a language which is safer, and compile it into JS.  https://github.com/mherkender/lua.js  Then the only 'real' JS is libraries provided by extensions managed by code review processes.",1423097035,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I don't think we can just sandbox JS running on the wiki, @jayvdb",1422983276,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Maybe a tool like https://www.mediawiki.org/wiki/Gerrit_patch_uploader can be created to supplement Phab/etc.
+
+Not that I agree with this idea ; IMO we'd be far better off identifying the problematic uses of .css and .js and requiring a new right to save changes which appear to have security implications. That allows gradual improvement, and is not too dissimilar to security checks used on uploads.  And 'safe' functions added to properly managed JS modules whenever Common.js editors hit their head too regularly on the security inspector.",1422962357,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Ref web-based editor in Phabricator, as commented in T71445#742556, we checked upstream, but generally speaking they are not enthusiastic with the idea. See their reasoning at https://secure.phabricator.com/T6008#7
+",1422960004,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1005858, @Krinkle wrote:
+> Using Git does raise the barrier for contribution a little.
+
+This is a concern, though. While Phabricator uses SUL and so doesn't have the issues that earlier proposals of using Gerrit did, until WMF has moved from Gerrit to Phabricator for code review it's hard to really guess how this might work in practice for people who maintain gadgets on-wiki and aren't used to other workflows.
+
+Ideally one workflow would be loading the gadget files in a web-based editor of some sort, making the changes, and submitting that as a patch without having to use any locally-installed software other than a web browser and without any complicated key setup. But does Phabricator support that (and will it be enabled here)?",1422890696,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1005858, @Krinkle wrote:
+> We'd have a clear distinction between the ""wiki-content administrator"" role (sysop) and ""developer"" role. One person can still have both roles, but sysop would no longer imply ""developer"". We currently have a situation where users can become sysop (to block users, delete pages, etc.) – but at the same time able to change gadgets. (Through the MediaWiki-namespace that got unfortunately re-used for Gadgets). This isn't a matter of personal trust or malicious intent. These users have clearly gained the respect and trust of their respective communities. It's about technical competence and experience to make decisions about software modifications. This is a sensitive area. It's not fair to demand from most sysops that they have to make these decisions. They shouldn't have to deal with requests for edits on Common.js without knowing what the impact of such program would be.
+
+Conversely, more experienced JavaScripters should be able to merge improvements without having to request advanced user rights on each wiki.
+And what about Lua modules then? A Git repository would probably speed T52329 up.
+
+However, I'm afraid that many users could think of Git being another way to limit their independence.",1422706176,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#1006055, @Steinsplitter wrote:
+>>>>! In T71445#968479, @Ricordisamoa wrote:
+>> I often find privacy violations in Common.js in the form of well-intended scripts  (...)
+> 
+> Then the software should log or prevent such actions (like a abusefilter). 
+
+There's no way to automate code review, especially not of obfuscated code. Same goes for security review, which is as important (and a lot of scripts are lacking here... only yesterday I had to kill a user script because of a CSRF vulnerability that would allow page deletions).",1422700941,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>>! In T71445#968479, @Ricordisamoa wrote:
+> I often find privacy violations in Common.js in the form of well-intended scripts  (...)
+
+Then the software should log or prevent such actions (like a abusefilter). 
+
+And please remember that a lot of script dev's don't like to work with git...",1422695806,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968479, @Ricordisamoa wrote:
+> I know this has probably been discussed before, but... what about hosting gadgets via Git/Phabricator?
+> At least the largest ones will benefit from more thorough review.
+
+Thanks for bringing this up @Ricordisamoa!
+
+I support the idea of using Git for gadgets in the future. There are other options, but Git is nice.
+
+Using Git/Phabricator for gadgets provides many benefits:
+
+* Code review
+ * Review by another person before merging (more stable code).
+ * Ability for anyone to submit a patch that others can easily merge (instead of copy-pasting from a talk page, or a user sub page).
+ * Inline discussion about the code and making small improvements.
+* Continuous integration
+ * Ability to write and run unit tests (less breakage for users).
+ * Option to enforce coding style and code quality via JSHint (opt-in of course).
+* Git
+ * ""git-blame"" to find authors of a particular pieces of code.
+ * The option to distinguish between stable and beta versions.
+ * Easily backport (apply) individual bugfixes to older versions.
+ * Streamlined process for deploying weekly to all wikis (for ""global"" gadgets).
+ * Ability for non-Wikimedia wikis to ""install"" gadgets on their wikis (and update it). Instead of copying all relevant pages and trying to keep them up-to-date. (Or hotlinking via extra HTTP requests and risking breakage with incompatible versions.)
+ * Ability for MediaWiki site-admins to install the right version of gadgets on their wikis. (Thanks to Git branches associated with a MediaWiki  release version.) – No more need to maintain compatibility with old MediaWiki versions or hotlinking code.
+* Issue tracker
+ * Central place to create and resolve tasks, bugs and feature requests.
+
+We could create an extension like ""WikimediaGadgets"". Or separate Git repositories with git-submodules or Composer-based. Everything is possible.
+
+Using Git does raise the barrier for contribution a little. But in full perspective of where we are coming from and what we all want, I think that's worth raising the barrier for. With gadgets, the community creates their own modules without involving Wikimedia Foundation. They can create and deploy anything they want. It's very enabling and flexible for the community.
+
+In the last few years, Wikimedia has changed a lot in how it manages code. We no longer have a single repository managed by a handful of people that only deploy updates once or twice a year. Quite the contrary. We now have a plethora of different repositories maintained by different people (including lots of volunteers!). This ""Wikimedia Gadgets"" repo can have its own access control in Git – separate from MediaWiki and Wikimedia user groups.
+
+Some gadgets have already done this by using GitHub (except for the deployment part, these still copy-paste to wiki pages):
+* https://github.com/azatoth/twinkle
+* https://github.com/Krinkle/mw-gadget-rtrc
+* https://github.com/Krinkle/mw-gadget-whatleaveshere
+* https://github.com/countervandalism/mw-gadget-cvnoverlay
+
+Aside from the benefits for authors and users of gadgets, there are a few extra gains.
+
+We'd have a clear distinction between the ""wiki-content administrator"" role (sysop) and ""developer"" role. One person can still have both roles, but sysop would no longer imply ""developer"". We currently have a situation where users can become sysop (to block users, delete pages, etc.) – but at the same time able to change gadgets. (Through the MediaWiki-namespace that got unfortunately re-used for Gadgets). This isn't a matter of personal trust or malicious intent. These users have clearly gained the respect and trust of their respective communities. It's about technical competence and experience to make decisions about software modifications. This is a sensitive area. It's not fair to demand from most sysops that they have to make these decisions. They shouldn't have to deal with requests for edits on Common.js without knowing what the impact of such program would be.
+
+I often find privacy violations in Common.js in the form of well-intended scripts that load files from third-parties. (E.g. fonts, images or scripts.) This is against the Foundations' privacy policy, and probably not what the sysop intended. There's a good chance the sysop and user who suggested such edit, actually believe in our privacy policy. But they simply lack knowledge of how web browsers work. They didn't realise that such edit would result in all readers of the wiki now loading a file from a Google server. (And send their IP address and other details about their computer and geolocation to that Google server – without consent.)
+
+The wikis can use their own policies for deciding what gadget to create, support and enable. The code would be reviewed by members of the community interested in development, instead of sysops. Sysops can still control which gadgets they enable by default etc.
+",1422672168,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968958, @Steinsplitter wrote:
+>>>! In T71445#968625, @Krenair wrote:
+>> All currently-on-wiki gadgets/scripts need to go through some form of pre-deployment code review. Not just popular ones.
+> 
+> Can we please establish community consensus before implanting such a code review. This sounds like a huge change.
+
+Huge yes, but if done it'd basically be a CONEXCEPT type of thing as this would be for technical code security and quality reasons.
+
+(Just in case it's not clear, this is with my technical volunteer hat on. My opinion only, etc.)",1421792603,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968479, @Ricordisamoa wrote:
+> I know this has probably been discussed before
+
+Yes, about a thousand times. Could you volunteer to read the past discussions (linked in task description) and summarise them in the task description, please?",1420973512,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968625, @Krenair wrote:
+> All currently-on-wiki gadgets/scripts need to go through some form of pre-deployment code review. Not just popular ones.
+
+Can we please establish community consensus before implanting such a code review. This sounds like a huge change.",1420964445,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968625, @Krenair wrote:
+> All currently-on-wiki gadgets/scripts need to go through some form of pre-deployment code review. Not just popular ones.
+
+Can we please establish community consensus before implanting such a code review. This is a HUGE change.",1420964424,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,All currently-on-wiki gadgets/scripts need to go through some form of pre-deployment code review. Not just popular ones.,1420921204,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,All currently-on-wiki gadgets/scripts need to go through some fprm of pre-deployment code review. Not just popular ones.,1420921187,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968494, @Steinsplitter wrote:
+>>>! In T71445#968479, @Ricordisamoa wrote:
+>> I know this has probably been discussed before, but... what about hosting gadgets via Git/Phabricator?
+>> At least the largest ones will benefit from more thorough review.
+> 
+> This is something else. Hosting highly popular gadgets like HotCat makes sense imho, :)
+
+But then we wouldn't need any on-wiki ""code-review process"".",1420913210,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968479, @Ricordisamoa wrote:
+> I know this has probably been discussed before, but... what about hosting gadgets via Git/Phabricator?
+> At least the largest ones will benefit from more thorough review.
+
+This is something else. Hosting highly popular gadgets like HotCat makes sense imho, :)",1420909334,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I know this has probably been discussed before, but... what about hosting gadgets via Git/Phabricator?
+At least the largest ones will benefit from more thorough review.",1420908816,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#968415, @Nemo_bis wrote:
+>>>! In T71445#958792, @MZMcBride wrote:
+>> the list is in T71445#742344.
+> 
+> Anything that begins with «To take English wikipedia as an example» is IMHO irrelevant for a bug whose summary is ""on Wikimedia sites"".
+
+Exactly. For example, on commons are only a few coders who are keeping up scripts (fixing bugs, deprecated code etc.)  Implanting a code review in such a case makes coder unhappy.",1420907837,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#958792, @MZMcBride wrote:
+> the list is in T71445#742344.
+
+Anything that begins with «To take English wikipedia as an example» is IMHO irrelevant for a bug whose summary is ""on Wikimedia sites"".",1420905083,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#956103, @Nemo_bis wrote:
+> I feel this report is //un cane che si morde la coda//. Unless someone summarises the (relevant parts of the) discussion above and in the linked threads, I propose to close this invalid.
+
+Closing this issue as invalid would probably be the wrong choice as I think the issue is both real and unresolved.
+
+I can't quote Jon's list of action items above (the quote button is disabled for some godforsaken reason), but the list is in T71445#742344.",1420605953,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#957894, @Aklapper wrote:
+> [Please do not add otherwise contentless ""+1"" comments as they create notifications for everybody. Use tokens or flags instead. Thanks.]
+
+-1",1420577858,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"[Please do not add otherwise contentless ""+1"" comments as they create notifications for everybody. Use tokens or flags instead. Thanks.]",1420571578,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#956103, @Nemo_bis wrote:
+> I feel this report is //un cane che si morde la coda//. Unless someone summarises the (relevant parts of the) discussion above and in the linked threads, I propose to close this invalid.
+> 
+> We already have separate, actionable reports (and sometimes RfC) for things like JavaScript validation and granularity of sysop permissions.
+
++1",1420535434,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I feel this report is //un cane che si morde la coda//. Unless someone summarises the (relevant parts of the) discussion above and in the linked threads, I propose to close this invalid.
+
+We already have separate, actionable reports (and sometimes RfC) for things like JavaScript validation and granularity of sysop permissions.",1420491129,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,">>! In T71445#742556, @Qgil wrote:
+> @eloquence proposed to investigate the idea of Phabricator with a web based interface for editing files, as a possibility to bring easy-as-in-editing-text development closer to proper code review and continuous integration with automated QA.
+> 
+> We checked upstream, but generally speaking they are not enthusiastic with the idea. See their reasoning at https://secure.phabricator.com/T6008#7
+> 
+> For different reasons, @Legoktm proposed to go back to the idea of a MediaWiki-based code review...
+
+Now that this task is here, let me add #Code-Review just to make sure that people interested in code review in Phabricator know about this discussion.
+",1417697095,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think the effort of bringing all developers under the same roof is worth, and mediawiki.org is the right roof. 
+
+But going back to the definition of the sane code-review process, some ideas came up from a casual email chat. Summary in sequential order:
+
+Erik proposed to investigate the idea of Phabricator with a web based interface for editing files, as a possibility to bring easy-as-in-editing-text development closer to proper code review and continuous integration with automated QA.
+
+We checked upstream, but generally speaking they are not enthusiastic with the idea. See their reasoning at https://secure.phabricator.com/T6008#7
+
+For different reasons, Legoktm proposed to go back to the idea of a MediaWiki-based code review. Let me paste:
+
+""(...) we could just put a revision id in the gadget definition:
+
+""scripts"": {""foo.js"": 123, ""bar.js"": 456},
+""styles"": {""baz.css"": 789},
+
+Or something like that. So anyone can edit (maybe still restricted by
+a userright or maybe not) the JS/CSS pages, but their changes don't
+actually take effect until the gadget definition is updated by someone
+with those rights (+2). This allows us to take advantage of wiki
+process like be bold, revert, discuss, but still impose a review
+requirement by someone with ""+2"" rights. In some ways it's like SVN.""
+
+As Legoktm explain, there is a precedent of this type of process in the workflow for approving EventLogging schemas, where many can edit the schemas but only a few can point to a new version (the +2 equivalent).
+
+https://www.mediawiki.org/wiki/Extension:EventLogging/Guide#Peer_review",1409846486,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Quim Gil from comment #30)
+> mediawiki.org please. I'm happy to discuss the reasoning wherever
+> corresponds.
+Ideally both global user scripts and global gadgets should be in the same wiki (but Meta is already in use for the first, so going to another wiki will require migration - which is easy enough: 1. inform users; 2. import any /global.js/css from Meta, with history; 3. delete the old ones from Meta).
+
+Anyway, both Meta and mw.org have Translation extension installed, which will help creating multilingual documentation in a consistent way for popular gadgets.",1409246367,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Helder from comment #29)
+> using a single common wiki would be the best - whatever wiki is choosen -
+
+mediawiki.org please. I'm happy to discuss the reasoning wherever corresponds.",1409245878,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"What about creating the ""Gadget developer"" user group on WMF wikis, with the user rights which are currently given to sysops (edituserjs, editusercss and editinterface - which gerrit change 154452 splits into 'editsitejs' and 'editsitecss') and, later, also the user rights introduced by Gadgets 2.0 (see the links mentioned on comment 17).
+
+Then, send an announcement recommending communities to evaluate whose of their sysops should indeed have the permissions to edit JavaScript and CSS and add them to the new user group, and after a reasonable amount of time, remove the user rights from sysops on WMF wikis.
+
+Also, since it is recommended to keep gadgets central[1], and since now Meta-wiki is the central wiki used by extension GlobalCssJs, maybe apply any code-review process first to the editing of global gadgets hosted on Meta (some are currently hosted on mw.org or enwiki, or wikidata, but using a single common wiki would be the best - whatever wiki is choosen - and would help in the implementation of the Gadgets 2.0 when that is ready for deployment in the future).
+
+[1] https://www.mediawiki.org/wiki/ResourceLoader/Migration_guide_%28users%29#Keep_gadgets_central",1409245587,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Yann Forget from comment #27)
+> Why not do it as page correction and validation in Wikisource? It is a light
+> process, and there is no need to learn a new tool.
+> 
+> With the Proofreading page extension, 2 non-anonymous users are needed to
+> validate a page. Additionally, more right could be needed (either sysop or
+> autopatrolled).
+
+This sounds good to me. +1",1409239662,PHID-USER-nuf2sujf7qrx4v5ixbs3,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Why not do it as page correction and validation in Wikisource? It is a light process, and there is no need to learn a new tool.
+
+With the Proofreading page extension, 2 non-anonymous users are needed to validate a page. Additionally, more right could be needed (either sysop or autopatrolled).",1409235503,PHID-USER-dy7vqdheslnndi5s6r4g,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,Depends on bug 20153?,1408085526,PHID-USER-je4a7kqdfgacwkyhtg4c,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Stefan2 from comment #16)
+> I think that the problem is that the MediaWiki namespace can be edited by
+> any administrator. Many administrators do not understand what the code does,
+> as demonstrated for example by the ""~~~~"" in
+> [[szl:Special:PermanentLink/207947]], which Legoktm mentioned above. A
+> simple solution would be to remove the right to edit pages in the MediaWiki
+> namespace from administrators and instead assign it to a new group,
+> ""scripteditors"", consisting of editors who understand how the code works.
+> 
+
+> Broadly, administrators are trusted users and should be treated as such.
+
+Yes but whereas I might trust a fellow developer, I still wouldn't at all me comfortable if they +2ed their own code and this is why we have code review processes. Also I might trust an administrator in wiki things but if they are unable to use a code review tool then I wouldn't trust them to edit JavaScript. I worry that a lot of this is due to an outdated idea that JavaScript is not a real language. Ask yourself what if MediaWiki:Common.php existed and how allowing editing of code on a wiki that would make you feel...
+
+I can imagine Common.js being useful for a hobby wiki to make a few tweaks, but it really has no place on a Wikimedia wiki and we should certainly not be building code review systems to support it. Instead we should be focusing energy on making code review in mediawiki core quicker and more enticing and more regularly deploying our code.",1408039865,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to MZMcBride from comment #19)
+> In other words, if you all want to deprecate the use of MediaWiki:Common.js
+> and similar pages, you should work toward that goal. If/when the day comes
+> that they're no longer needed, then we can consider getting rid of them. But
+> this bug seems to be a bit ""cart before the horse.""
+
+Agreed, and if anyone wants to write patches that make our software more useful I will happily help merge them. Have raised bug 69550 so as not to derail this bug anymore. :)",1408032618,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to MZMcBride from comment #19)
+> Err, most of the MediaWiki namespace isn't JavaScript and CSS, it's
+> interface messages. The fact that JS and CSS pages are included in the
+> MediaWiki namespace has always been a design quirk that should probably be
+> corrected as their inclusion in the namespace is a(n) (ab|mis)use of the
+> namespace's purpose.
+
+Well yes, but there are some messages that are also a big issue. See also bug 43646",1407987309,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to C. Scott Ananian from comment #8)
+> I think that extensions and gadgets are probably the ""right"" way to make
+> sitewide changes.  Extensions already have a code review/deployment process,
+> although we can certainly work to make that smoother/easier.  Perhaps enwiki
+> could have an 'Extension:enwiki', for example, which could contain any code
+> which would otherwise live in common.js.
+
+I was thinking a bit more generic, but yeah, this might be a good idea to pursue. My thought was that you might have Extension:WikimediaScripts, which follows the pattern of E:WikimediaMaintenance and E:WikimediaMessages and E:WikimediaEvents. Inside the WikimediaScripts extension, you'd have modules that could then be loaded on a per-wiki basis.
+
+> common.js is just a weird special case that doesn't need to exist.
+
+I addressed this line of reasoning in comment 19, last paragraph. For now, there's a definite need for these pages to exist. That may not be true in the future, but it is true today.",1407985719,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Brad Jorsch from comment #9)
+> (In reply to MZMcBride from comment #6)
+>> Code is the enemy; less code is better. Rather than looking at ways to
+>> impose code review on wiki communities, we should first look for ways to
+>> centralize code (global gadgets) and we should look for ways to make the
+>> current site-wide JavaScript hacks no longer necessary.
+> 
+> While having more code in gadgets rather than in common.js is good, it's
+> orthogonal to the need for a good code review process that's actually usable
+> by wiki users. The global gadgets will still need a code review process.
+
+It would be helpful if you could explicitly specify what needs you see that you feel MediaWiki could handle well and/or that you think Phabricator could not handle well.
+
+> Wiki users might accept having to go to a Commons-like site instead of doing
+> it on their local wiki (and in the long run they'll probably have to), but
+> they're unlikely to accept something that requires they install software
+> locally, sign up for a non-SUL account, figure out ssh keys, publish an
+> email address publicly, and so on.
+
+GitHub and GitLab both allow in-browser editing now, I believe. I imagine Phabricator, which will allegedly be part of Wikimedia unified login, will also have equivalent functionality. The e-mail address is trivially solvable in Git by simply making up an e-mail address (User:Anomie@git-en.wikipedia.org), I think? And if you're using a Web browser and single unified login for authentication, you probably don't need to worry about SSH keys or installing software such as Git locally.
+
+You may be correct that there's a need here for global gadgets, but I think we need to do more to be much clearer about what that need is and how we propose to address it, assuming additional development—outside of the ongoing Phabricator work and I suppose the work to deprecate Common.js and similar pages—is needed.",1407985428,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Gilles Dubuc from comment #7)
+> The fact that people who aren't developers and/or who don't understand what
+> custom JS they're deploying to millions of users is the problem.
+
+You're basically hitting [[hard cases make bad law]] here. Most Wikimedia wikis (probably over 800 of them) do not have millions of users.
+
+> If you're not willing to learn git, you're not the right person to be
+> pushing custom JS to a top-5 website.
+
+Can we please collectively stop with the ""top-5"" bullshit? :-)  Obviously the English Wikipedia and other wikis are a consideration, but over 99% of MediaWiki wikis are not top-5 anything.",1407985318,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Stefan2 from comment #16)
+> I think that the problem is that the MediaWiki namespace can be edited by
+> any administrator. Many administrators do not understand what the code does,
+> as demonstrated for example by the ""~~~~"" in
+> [[szl:Special:PermanentLink/207947]], which Legoktm mentioned above. A
+> simple solution would be to remove the right to edit pages in the MediaWiki
+> namespace from administrators and instead assign it to a new group,
+> ""scripteditors"", consisting of editors who understand how the code works.
+
+Err, most of the MediaWiki namespace isn't JavaScript and CSS, it's interface messages. The fact that JS and CSS pages are included in the MediaWiki namespace has always been a design quirk that should probably be corrected as their inclusion in the namespace is a(n) (ab|mis)use of the namespace's purpose.
+
+Broadly, administrators are trusted users and should be treated as such.
+
+Whether the rest of the MediaWiki namespace is needed is also debatable nowadays, but probably also outside the scope of this ticket.
+
+> I think that some code should be removed from Common.js files and moved to
+> MediaWiki core instead. For example, [[sv:MediaWiki:Common.js]] contains
+> code fixing incorrect sorting of text in tables (search for
+> ""tableSorterCollation""). Every user of MediaWiki would want text to be
+> sorted correctly, so I don't see why this couldn't be in MediaWiki core
+> instead.
+
+Yes, for sure. I made a similar comment above (comment 6). We should figure out why these pages are still needed and work to address that by putting the functionality in MediaWiki core or in an extension. I think this is a better use of time than proposing trashing the functionality.
+
+In other words, if you all want to deprecate the use of MediaWiki:Common.js and similar pages, you should work toward that goal. If/when the day comes that they're no longer needed, then we can consider getting rid of them. But this bug seems to be a bit ""cart before the horse.""",1407984367,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Eran Roz from comment #13 and comment #14)
+> I just runned a simple phantomjs script on all wikipedia languages to catch
+> simple errors:
+> 
+> [...]
+
+Thanks for this. I split this out to bug 69519.",1407983890,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Gadgets 2.0 (T31272) introduces new user rights specific for edit/management of gadgets:
+https://www.mediawiki.org/wiki/ResourceLoader/Version_2_Design_Specification#User_rights
+See also this discussion about which users (user groups) should have each permission:
+https://www.mediawiki.org/wiki/Thread:Talk:ResourceLoader/V2_testing/Questions_about_permission_model_and_developer_workflow",1430821452,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Gadgets 2.0 introduces new user rights specific for edit/management of gadgets:
+https://www.mediawiki.org/wiki/ResourceLoader/Version_2_Design_Specification#User_rights
+See also this discussion about which users (user groups) should have each permission:
+https://www.mediawiki.org/wiki/Thread:Talk:ResourceLoader/V2_testing/Questions_about_permission_model_and_developer_workflow",1407966302,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think that the problem is that the MediaWiki namespace can be edited by any administrator. Many administrators do not understand what the code does, as demonstrated for example by the ""~~~~"" in [[szl:Special:PermanentLink/207947]], which Legoktm mentioned above. A simple solution would be to remove the right to edit pages in the MediaWiki namespace from administrators and instead assign it to a new group, ""scripteditors"", consisting of editors who understand how the code works.
+
+I think that some code should be removed from Common.js files and moved to MediaWiki core instead. For example, [[sv:MediaWiki:Common.js]] contains code fixing incorrect sorting of text in tables (search for ""tableSorterCollation""). Every user of MediaWiki would want text to be sorted correctly, so I don't see why this couldn't be in MediaWiki core instead.",1407964090,PHID-USER-zcvchmenkrawdr5233in,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,Eran Roz: please fill bug report for all such issues. This way they can be triaged / assigned to the proper persons and will be easier to track than this bug which is merely for discussion.,1407956393,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Created attachment 16185
+Example for errors across wikis
+
+Maybe it is a bit off-topic but here are some cases of errors across wikis in simple read/edit transaction using phantomJS
+
+**Attached**: {F14648}",1407955361,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think code review isn't the solution, as it is probable that no one will review the code for small wikis. 
+However it would be great to have automated tests running after changes in common.js and gadgets. Such general tests can at least validate no external resource is loaded, or no invalid syntax is added.
+The simplest option is to run it outside MW (such as a script in labs that runs X times a day), but an extension to do it while editing would be even better...
+
+BTW
+I just runned a simple phantomjs script on all wikipedia languages to catch simple errors:
+
+testing als
+ERROR: ReferenceError: Can't find variable: ta
+TRACE:
+ -> https://als.wikipedia.org/w/index.php?title=MediaWiki:If-pt-login.js&action=raw&ctype=text/javascript&dontcountme=s: 9
+
+testing kk
+ERROR: TypeError: 'null' is not an object (evaluating 'document.getElementById('mw-vector-current-variant').innerHTML=wgULS(""Кирил"",""Latın"",""توتە"")')
+TRACE:
+ -> https://bits.wikimedia.org/kk.wikipedia.org/load.php?debug=false&lang=kk&modules=site&only=scripts&skin=vector&*: 9
+
+
+anyone wants to fix them? :)",1407951117,PHID-USER-cfsvvgbtlqnbt2yokfjf,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I don't think MediaWiki should invent its own code review software. I completely agree with every Gilles Dubuc and C. Scott said above.
+
+Code review software is /hard/ to build and for us to build it would 1) be a waste of resources and 2) be suboptimal.
+
+
+That aside, The existing MediaWiki:Common.js is a serious hack and huge security hole that I can't believe has not been exploited yet and we really should be thinking about better ways to replace it with something else.
+
+I too think Gadgets and extensions are the place for these things. Anything site wide should be in an extension, anything goes in a gadget as long as user has the choice to opt into it.
+
+MZMcBride is spot on and makes a good suggestion that we should be starting at the source.
+To take English wikipedia as an example [1]
+When I look through the code I see:
+
+* Main page layout fixes - why is this code running across the entire site?
+* A redirect script that sends User:Name/skin.js to User:Name/skin.js to vector.js or monobook.js - again why is this running across the entire site and not a feature of the software?
+* Some deprecation notices... shouldn't deprecation happen in the software?
+* Then a bunch of imported scripts:
+** if you are on an edit page 'MediaWiki:Common.js/edit.js'
+** on the watchlist MediaWiki:Common.js/watchlist.js
+** on the file page MediaWiki:Common.js/file.js
+
+At this point I gave up reading. All these indicate to me is that there are holes in the software that need fixing for all users and are being neglected to be fixed in the software because ""code review is too cumbersome"". This is completely irresponsible and upsets me. We should be striving to make MediaWiki as customisable and flexible as possible without having hacky compromises like this.
+
+""sysops are going to download and learn to use git."" if a person is not able to learn git then personally I worry about them tinkering with software that hits site wide. Tinkering with gadgets that are available for opt in is a great thing and I believe important for community innovation but site wide just scares me.
+
+My suggested way forward would be:
+* Audit all uses of Common.js
+* Open bugs for all the problems they are solving (I think we'll be surprised at how much overlap there is between projects)
+* Work with the community to fix the issues in the software they have identified in Common.js and remove the code from Common.js. In doing so build up a trust that through code review we can fix things just as quickly and better without resorting to needing a wikipage.
+* With a cleaner Common.js wikipage and better process see the wood through the trees and reevaluate what we need this page for.
+
+[1] https://en.wikipedia.org/wiki/MediaWiki:Common.js",1407944364,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Brad Jorsch from comment #9)
+> ...
+> they're unlikely to accept something that requires they install software
+> locally, sign up for a non-SUL account, figure out ssh keys, publish an
+> ...
+FYI: we might have SUL for Phabricator:
+http://fab.wmflabs.org/T314",1407942287,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Notice that many wikis have migrated code from Common.js to default gadgets (e.g. for modularization, to allow users to disable functionality, to make debugging easier, to allow importing specific parts from other wikis, etc), and others also load subpages like Common.js/edit.js, Common.js/watchlist.js, Common.js/IEFixes.js, etc..
+
+Wikimedia Commons for example has 17 gadgets enabled for everyone by default. See more stats on
+https://meta.wikimedia.org/wiki/Gadgets",1407942078,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"(In reply to Gilles Dubuc from comment #7)
+> The fact that people who aren't developers and/or who don't understand what
+> custom JS they're deploying to millions of users is the problem. It's not a
+> situation that needs to be perpetuated through dumbed-down on-wiki code
+> review.
+
+I've heard that same argument as to why wikitext is better than VisualEditor. I didn't agree then, and I don't agree now: making the process technically difficult to try to discourage ""unqualified"" contributors isn't a very well-targeted heuristic. Even if the people affected are smart enough to be able to figure out the process, they may well decide the effort isn't worth it.
+
+
+(In reply to MZMcBride from comment #6)
+> Code is the enemy; less code is better. Rather than looking at ways to
+> impose code review on wiki communities, we should first look for ways to
+> centralize code (global gadgets) and we should look for ways to make the
+> current site-wide JavaScript hacks no longer necessary.
+
+While having more code in gadgets rather than in common.js is good, it's orthogonal to the need for a good code review process that's actually usable by wiki users. The global gadgets will still need a code review process.
+
+Wiki users might accept having to go to a Commons-like site instead of doing it on their local wiki (and in the long run they'll probably have to), but they're unlikely to accept something that requires they install software locally, sign up for a non-SUL account, figure out ssh keys, publish an email address publicly, and so on.
+
+FlaggedRevs isn't a good model, because we need merging of proposed changes rather than a linear history. I don't know whether CodeReview will do pre-commit review, which is probably a necessity.",1407941889,PHID-USER-uqcn2l4ng4murmyfnvyp,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think that extensions and gadgets are probably the ""right"" way to make sitewide changes.  Extensions already have a code review/deployment process, although we can certainly work to make that smoother/easier.  Perhaps enwiki could have an 'Extension:enwiki', for example, which could contain any code which would otherwise live in common.js.  On github, at least, proposing a new change would be as easy as going to the 'common.js' file inside the Extension:enwiki respository and clicking 'edit', which takes care of forking, branching, commiting, and submitting a pull-request.
+
+Gadgets don't really have a good review mechanism at the moment.  I think this bug could concentrate on reviews for gadgets;  common.js is just a weird special case that doesn't need to exist.",1407941069,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"The fact that people who aren't developers and/or who don't understand what custom JS they're deploying to millions of users is the problem. It's not a situation that needs to be perpetuated through dumbed-down on-wiki code review. Like MZ just described, if there's a way to remove the bulk of the need for these users to deploy custom JS, it should be explored first.
+
+And for whatever JS is left that can't be standardized into a global gadget repository (I haven't looked at the code, but I imagine there will always be ""that specific thing that can't be done differently""), community members with appropriate skills should be doing it. If you're not willing to learn git, you're not the right person to be pushing custom JS to a top-5 website. Even if you don't want to learn or don't have time to, it just means that you need to enlist the help of someone who knows about this stuff. Right now that step doesn't exist and irresponsible actions are being taken by people who are just unaware of what they're doing.
+
+I think that a ""simple mode"" review tool is also likely to make the uneducated people sending JS they don't understand less likely to learn to master what they're doing. As such it wouldn't be code review, it would be ""please make this thing I don't understand work and deploy it"", which puts all the workload burden on the reviewer, instead of being the 2-way street code review should be.",1407939353,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I'm not sure this problem is being approached in the best way. I think it would be helpful to look at use-cases and work backward from there. Why are administrators adding custom site-wide JavaScript?
+
+Looking through [[MediaWiki:Common.js]], for example, it seems as though a lot of code is deprecated and could be removed once de-referenced. The non-deprecated code should probably exist in MediaWiki core or in a MediaWiki extension, if it's generally useful functionality.
+
+Code is the enemy; less code is better. Rather than looking at ways to impose code review on wiki communities, we should first look for ways to centralize code (global gadgets) and we should look for ways to make the current site-wide JavaScript hacks no longer necessary.
+
+(In reply to Zell Faze from comment #4)
+> I think the community would likely reject attempts to use git or gerrit. 
+> Whatever this system is, it will need to be implemented within Mediawiki. 
+> People have a hard enough time leaving their home wiki, I seriously doubt
+> that most sysops are going to download and learn to use git.
+
+A smart front-end could mask that the user is using Git. I'm thinking about an interface similar to in-browser editing in the GitHub front-end. But again, I'd like us to more closely look at the underlying use-cases first.",1407934687,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Indeed. This definitely must be implemented ""inside"" MediaWiki (whatever the backend we use, the UI must be displayed within regular MediaWiki pages) if it is supposed to be used by MediaWiki users and not MediaWiki developers.",1407931671,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"I think the community would likely reject attempts to use git or gerrit.  Whatever this system is, it will need to be implemented within Mediawiki.  People have a hard enough time leaving their home wiki, I seriously doubt that most sysops are going to download and learn to use git.
+
+Though Flaggedrevs is weird, I personally think that it, or something like it, is the way to go.  The learning curve of it is less than that of git and gerrit, and I'm sure some sort of bridge could be made that would allow running of tests on code submitted there.
+
+I feel like any system outside of Mediawiki would stifle each communities autonomy, something that in recent weeks we've seen they care an awful lot about.",1407930580,PHID-USER-2qzpsivaeuezrxqtzhwn,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Why can't we just do this the same way as our current status quo (gerrit) or the soon-to-be status quo (phabricator)? Less systems that do the same thing to maintain...
+
+Some volunteers have +2 on our projects, this is the same situation except that we need to find more volunteer reviewers than usual, because we don't have the bandwidth to review this at the moment.
+
+IMHO if the code review process we normally undergo feels heavy to impose on this audience, it just needs that we need to improve the process. If it becomes easier to outsiders, it benefits all projects.",1407927917,PHID-USER-papbtlagfolot4dzerne,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"Would it make sense to use git / phabricator ?   We will have to convince the community that a pre commit review workflow is a good thing, but that would let us run validation tests and deploy on some staging area before rolling changes to production.
+
+I am very skeptical at our ability to code and maintain a review system in MediaWiki, we have past experiences:
+
+- CodeReview extension for svn could have been nice if we had the ability to devote time to it, it turned out to be simpler to delegate the software to third party (Gerrit, soon Phabricator). 
+
+- FlaggedRevs which would let one validate revisions before they were made public. I don't think anyone regret it. I found the workflow / UI etc terrible and never understood how it worked.
+
+
+Also, we could use such a review system for Gadgets and LUA modules.  When writing, versionning and collaborating on code, ones need a version control system. git comes to mind.",1407876357,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites,"This would need to be done differently from how FlaggedRevisions currently is implemented (as in FR you still submit a new version which is directly being used by eg. ResourceLoader).
+
+I would suggest to have a new extension in which edits can basically be suggested like github pull requests and then get merged/ commented on/ rejected by a reviewer.
+
+Mid to long term this process should be centralized and managing JS/CSS should move away from the Wikis into a central place (that can be a MediaWiki, but IMO doesn't necessarily have to be one).",1407873356,PHID-USER-2mey32xhshfnf7rz7jjn,False,PHID-TASK-x6kwfnzot4hyoo5g6hzg,task_subcomment,NA
+VisualEditor: Reconsider whether you should be able to replace a selected node by typing / insertion tools,"Intention:
+Attempting to replace a formula with text by selecting the formula does not work.  Simply nothing happens.  Either typing or pasting has the same null effect.  Attempting to replace a formula by inserting a template results in the template being inserted after the formula, not instead of it.
+
+
+
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1407805620,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-cjqylbv337cm23t2r2z6,task_description,open
+VisualEditor: Reconsider whether you should be able to replace a selected node by typing / insertion tools,"(In reply to Spinningspark from comment #0)
+> Intention:
+> Attempting to replace a formula with text by selecting the formula does not
+> work.  Simply nothing happens.  Either typing or pasting has the same null
+> effect.  Attempting to replace a formula by inserting a template results in
+> the template being inserted after the formula, not instead of it.
+
+Yes, this is intentional. We could reconsider it but I worry that the additional slowness to support certain broken browsers in this respect (I believe the main issue here is Firefox) is not worth the minor user experience improvement.
+
+Note that the ""delete"" and ""backspace"" keys still work to delete the selection.",1415882261,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-cjqylbv337cm23t2r2z6,task_subcomment,NA
+"VisualEditor: in the image advanced settings dialog, ""Wrap text around this item"" looks like a label of the alignment buttons","The ""Wrap text around this item"" checkbox appears above the the alignment buttons and looks like a label for these buttons. The button group doesn't have a label of itself. It should be moved around somehow so the separation between them will be clear.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1407316440,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-bbylgmiwgkujcoiek33q,task_description,open
+"VisualEditor: in the image advanced settings dialog, ""Wrap text around this item"" looks like a label of the alignment buttons","Change 152054 abandoned by Amire80:
+Move the wrapping checkbox under the alignment buttons
+
+https://gerrit.wikimedia.org/r/152054",1415713370,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bbylgmiwgkujcoiek33q,task_subcomment,NA
+"VisualEditor: in the image advanced settings dialog, ""Wrap text around this item"" looks like a label of the alignment buttons","Change 152054 had a related patch set uploaded by Amire80:
+Move the wrapping checkbox under the alignment buttons
+
+https://gerrit.wikimedia.org/r/152054",1407329770,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bbylgmiwgkujcoiek33q,task_subcomment,NA
+"VisualEditor: in the image advanced settings dialog, ""Wrap text around this item"" looks like a label of the alignment buttons","... Also, it's on by default, so that's another reason not to put it on the top.",1407316562,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-bbylgmiwgkujcoiek33q,task_subcomment,NA
+VisualEditor: Main application namespace should be capitalised and not 2 characters short (ve -> VisualEditor),"Let's rename our global namespace to something longer than 2 characters and not identified by lowercase characters.
+
+Proposing VisualEditor instead of 've'.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1404778500,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jslvrd4uihevdc3j7qsn,task_description,declined
+VisualEditor: Main application namespace should be capitalised and not 2 characters short (ve -> VisualEditor),"Lowercase globals aren't ideal, but I think the ship has sailed on this for both `ve` and `mw`. Not worth messing with.",1530906840,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-jslvrd4uihevdc3j7qsn,task_subcomment,NA
+VisualEditor: Only display the wikitext warning once per session,"1. '[[' to a paragraph and dismiss the wikitext warning
+2. type in another paragraph then re-focus the [[ paragraph and type
+3. the wikitext warning returns
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403710500,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-xgn6yi4nvtbkl7ouzmwj,task_description,declined
+VisualEditor: Only display the wikitext warning once per session,"Displaying it once per session...? Per James, this is a wontfix I think.",1403811741,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-xgn6yi4nvtbkl7ouzmwj,task_subcomment,NA
+VisualEditor: Only display the wikitext warning once per session,Not sure that this is not a WONTFIX. We don't really want it to be lost on users that they're Doing It Wrong™. :-),1403741735,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-xgn6yi4nvtbkl7ouzmwj,task_subcomment,NA
+VisualEditor: Provide a way to make images default sized without invoking a dialog,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403637300,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-ysksgctttx7kwjm25imt,task_description,open
+VisualEditor: Provide a way to make images default sized without invoking a dialog,"or it could be a spot in the resize steps which replaces the ""XXX x XXX"" with ""Default size"" There are any number of options.",1403748049,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-ysksgctttx7kwjm25imt,task_subcomment,NA
+VisualEditor: Provide a way to make images default sized without invoking a dialog,"(In reply to Jared Zimmerman (WMF) from comment #1)
+> updated the title to not jump to the conclusion of how this should be done,
+> not sure if a button is the right answer,
+
+An ""action button"" is the ""set … without invoking image settings dialog"" UX concept in VE…",1403746116,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ysksgctttx7kwjm25imt,task_subcomment,NA
+VisualEditor: Provide a way to make images default sized without invoking a dialog,"updated the title to not jump to the conclusion of how this should be done, not sure if a button is the right answer,",1403745680,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-ysksgctttx7kwjm25imt,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"When editing, ""default size"" in mw prefs is not honored.",1403637120,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-qbjbd5yessxi474lujxf,task_description,resolved
+VisualEditor: Image should not change size when going from read to edit,"Change 499330 **merged** by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] Respect user preference for default thumbnail size while editing
+
+[[https://gerrit.wikimedia.org/r/499330]]",1553645145,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"Change 499330 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
+[mediawiki/extensions/VisualEditor@master] Respect user preference for default thumbnail size while editing
+
+[[https://gerrit.wikimedia.org/r/499330]]",1553635131,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,http://en.wikipedia.beta.wmflabs.org/wiki/Thumbnail_size2 / http://en.wikipedia.beta.wmflabs.org/api/rest_v1/page/html/Thumbnail_size2,1455138940,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"This really looks like it would be a simple fix. Parsoid sets `class=""mw-default-size""` on the `<figure>` elements if no explicit size was given, and VE already knows user's preferred thumbnail size.",1455138918,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"This issue has been pointed on fr.wp too.
+With the given example I see the image 1.66 bigger while reading than while editing.",1444936861,PHID-USER-unpoeiyj52rmcfqi5rbw,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"I'd like to revisit this, the current behavior is actively against the WYSIWYG model established in VE. I'm still not understanding the argument against this. If images are the same size both in read and edit mode, how will this contribute to editors wanted to resize them to ""look right for them"" if they already look correct? if anything this seems like it would lessen the desire to fiddle with image sizes.",1411066314,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"I think I might be being unclear with the request…
+
+
+As a user who sets my thumbnail preference to (120/180/220/250/300/etc)px while in visual editor I see ""default sized"" thumbnails display as (120/180/220/250/300/etc)px depending on my preference. 
+
+I'm not sure I understand your point ""we actively don't want people resizing images to look ""right"" for them, which this would encourage."" which is the exact opposite of what this would do, if the images LOOK right when i get to VE then I'm much less likely to go on a resizing spree.",1405968043,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"(In reply to Jared Zimmerman (WMF) from comment #2)
+> I think i might have been unclear on this one. 
+> 
+> The gist is ""Image should not change size when going from read to edit""
+> 
+> there are many possible fixes, but the one that seemed simplest was, for
+> images which are at ""default"" size, look at users preference for what size
+> ""default"" is and display them at that size when in edit mode.
+
+And as I said, we have intentionally chosen not to do this.
+
+> there might be other options, but the bug is that they change, size at all.
+
+The simplest ""fix"" to this issue is to remove the user preference. But you probably don't want that.",1403746069,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"I think i might have been unclear on this one. 
+
+The gist is ""Image should not change size when going from read to edit""
+
+there are many possible fixes, but the one that seemed simplest was, for images which are at ""default"" size, look at users preference for what size ""default"" is and display them at that size when in edit mode.
+
+there might be other options, but the bug is that they change, size at all.",1403745950,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor: Image should not change size when going from read to edit,"This is verging on a WONTFIX; we actively don't want people resizing images to look ""right"" for them, which this would encourage.",1403741652,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qbjbd5yessxi474lujxf,task_subcomment,NA
+VisualEditor:  Please strip trailing spaces and returns from media or image captions,"The solution for this may be related to Bug 61049:
+
+If you add a caption to an image, and you press return in the text area box at the end (perhaps several times), then the caption includes those pointless blank lines, which makes for ugly wikitext when the page is saved.
+
+See https://en.wikipedia.org/w/index.php?title=Sugar_candy&diff=613063549&oldid=611921250
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1403032080,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-etg24hhx2qupzouy5rnw,task_description,open
+VisualEditor:  Please strip trailing spaces and returns from media or image captions,"I got bit by this bug again:  https://ca.wikipedia.org/w/index.php?title=Cloïssa_gegant&diff=prev&oldid=17846863 
+
+Ed, does this really need a general solution?  I'd be happy to limit it to just text that's entered into a dialog.",1481143532,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-etg24hhx2qupzouy5rnw,task_subcomment,NA
+VisualEditor:  Please strip trailing spaces and returns from media or image captions,"The same is true for the main document, but I'd rather issue warnings than do automatic document modification (cf. typing wikitext into VE)",1403033540,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-etg24hhx2qupzouy5rnw,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Go to this page:
+
+https://test2.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&oldid=87309
+
+Change the first image from Thumbnail to Basic and click on ""Apply Changes""
+The following error appears in the console and cannot save page or cancel editing the page with VE.
+ 
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 55
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1402704660,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5cganofaldk4meetlmoe,task_description,resolved
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,Me neither.,1530051678,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,This seems to work correctly now. I can't reproduce any of the issues described here.,1530046412,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Now if I follow the minimal wikitext or the steps to reproduce in a page and try to change the first image from thumbnail to Basic, it moves the image inside the caption of the second image.
+
+Is that how we want it now?",1405546742,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Change 144136 merged by jenkins-bot:
+Fixes to getRelativeOffset and getRelativeRange
+
+https://gerrit.wikimedia.org/r/144136",1405445154,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Change 144136 had a related patch set uploaded by Esanders:
+Fixes to getRelativeOffset and getRelativeRange
+
+https://gerrit.wikimedia.org/r/144136",1405019099,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Change 144004 merged by jenkins-bot:
+Skip over nested handlesOwnChildren nodes in getRelativeOffset
+
+https://gerrit.wikimedia.org/r/144004",1404418515,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Change 144004 had a related patch set uploaded by Esanders:
+Skip over nested handlesOwnChildren nodes in getRelativeOffset
+
+https://gerrit.wikimedia.org/r/144004",1404415212,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"first case works perfectly in master
+second case still results in the image being deleted",1404408749,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"On test 2 wiki:
+the first case still throws an exception
+the second 'minimal' case results in the image being deleted",1404408560,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Marking as theoretically fixed, then. :-)",1404330575,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"I... can no longer reproduce this. I tried the steps in comment 3 as well as the wiki page in comment 2. Maybe this got fixed by Ed's selection-after-deletion fix? Because when we change an image from block to inline, we delete the old image and insert a new one.",1404329684,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"Found the steps to reproduce it from VE :D
+
+1.Open a page with VE
+2.Insert an image, keep it thumbnail-right
+3.Go to next line of the added image by pressing enter
+4.Add another image on the next line, make it frameless right
+5.Now in the caption of the second image : Add another image and go to the next line of this image by pressing enter
+6.Add anything on the next line of the caption
+7.Apply changes
+8.Save Page
+7.Reopen the page
+8.Try to make the first image Thumbnail to Basic
+
+Observed Result:
+
+Uncaught Error: Offset could not be translated to a DOM element and offset: 55
+appears in the console and cannot cancel the edit or save the page in VE",1403120797,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"This is the minimum wikitext required to reproduce this issue:
+[[File:MO-supp-K.svg|thumb]]
+[[File:IMA-johnson1.jpg|right|frameless|
+
+[[File:S.M.R.JPG|thumb]]
+{{Cite web|url = http://yahoo.com|title = }}
+
+]]
+
+You can try on this page:
+https://test2.wikipedia.org/wiki/Test66604?veaction=edit",1403119407,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions,"The problem seems to be in ve.ce.Document.prototype.getNodeAndOffset() where the stack ends up empty but the element is not a slug.
+
+I am pretty certain this happens due to the image with the complex caption that includes {{Cite}} <math> <ref> and another image inside it. My attempts to sanitize the wikitext and try everything one-by-one failed when I added that piece: 
+
+
+[[File:MO-supp-K.svg|thumb]]
+[[File:MO-supp-K.svg|thumb]]
+[[File:IMA-johnson1.jpg|right|frameless|caption
+<ref>{{Cite web|url = http://yahoo.com|title = }}</ref>
+
+<ref>reference</ref>{{Citation needed}}
+
+<math>\pi</math>
+[[File:S.M.R.JPG|thumb]]
+
+{{Cite web|url = http://yahoo.com|title = }}
+
+]]",1402939454,PHID-USER-zq6nzfwxwkyliljd4lfy,False,PHID-TASK-5cganofaldk4meetlmoe,task_subcomment,NA
+[DO NOT USE] Additional keyboard shortcuts (tracking) [superseded by #VisualEditor-EditingTools],"(Now tracked as part of #VisualEditor-EditingTools.)
+
+More keyboard shortcuts help users.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1401473640,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-qhfyvgtoq7dd2wahxu7j,task_description,invalid
+[DO NOT USE] Additional keyboard shortcuts (tracking) [superseded by #VisualEditor-EditingTools],[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343615,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-qhfyvgtoq7dd2wahxu7j,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400886180,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_description,duplicate
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"A <br /> could be inserted when the user uses Shift + Enter (line break instead of change of paragraph).
+This would be consistent with word processor software.",1487757747,PHID-USER-mapumhlp3gw5qefhvafn,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Where do we draw the line about being paternalistic and disallowing users to do things they want to do but we don't think are ""good code"" or ""stylistically wrong"" it seems like in many cases we go to great lengths to make things possible or easy even if we think the outcome may be that users misuse or use in unexpected ways and other times we block on them by saying we don't want to be enablers of bad behavior. Curious in this case how that logic is applied to do, or not do this?",1403742826,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"(In reply to Jared Zimmerman (WMF) from comment #7)
+> Two possible proposals that we could use one, both, or some variations
+> 
+> When consecutive breaks are found we could use
+> 
+> <br>
+> <br>
+> 
+> which is what you'll commonly see on wikipages when people are trying to do
+> some advanced formatting
+
+… and is horrendous and explicitly deprecated.
+
+> if the <br> is followed by a [[template]] or == Section == we could strip
+> out any <br> and replace with {{Clear}}
+
+This is verging on a WONTFIX, but leaving as a possible thing for later consideration.",1403742521,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Two possible proposals that we could use one, both, or some variations
+
+When consecutive breaks are found we could use
+
+<br>
+<br>
+
+which is what you'll commonly see on wikipages when people are trying to do some advanced formatting
+
+if the <br> is followed by a [[template]] or == Section == we could strip out any <br> and replace with {{Clear}}",1402335045,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,Closing temporarily as there's no proposed action. Please feel free to re-open.,1402328468,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Unfortunately MediaWiki has no representation of a blank paragraph, so they get destroyed when you save.
+
+We could theoretically not let you insert a second new line (so ""enter"" in a blank paragraph does nothing), and though this is an extant UX in the wild – LyX does this because LaTeX has the same limitation – I think it's pretty crummy, and probably worse than the current behaviour.
+
+What would you expect to happen?",1402015126,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Created attachment 15503
+post-save
+
+**Attached**: {F13877}",1401302297,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Created attachment 15502
+pre-save
+
+**Attached**: {F13876}",1401302265,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"go to https://en.wikipedia.org/wiki/User:Jaredzimmerman_%28WMF%29/VEtest
+
+1. place cursor after ""line 1""
+2. press enter/return on keyboard twice
+3. save page
+
+expected : there will be two blank lines after ""line 1""
+actual: there are no blank lines after ""line 1""
+
+see attached images for pre and post save appearance.",1401302215,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link,"Please provide steps to reproduce - no idea at which stage/keyboard focus I press some key on my keyboard, and which browsers this was tested with
+
+Please see https://www.mediawiki.org/wiki/How_to_report_a_bug",1401102456,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-xiestiqvpxbtrw7ppizw,task_subcomment,NA
+VisualEditor: Allow editing of a category link (not just add/remove),"In the page options menu, you can add a category by typing its name in the ""add a category"" box and delete a category by clicking the the trash icon in the category inspector. However it's not currently possible to **edit** the name of the category.
+
+For example, if the page is currently in [[Category:Admirals of World War I]] and I want to put it in [[Category:Admirals of World War II]], I can do that easily in the wikitext editor by simply typing an extra ""I"".  In VisualEditor, I have to completely delete the first category and then add the second from scratch.",1400565600,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-miv67zvinnq5ma6mdz7k,task_description,open
+VisualEditor: Allow editing of a category link (not just add/remove),"This was just mentioned to me by an experienced editor as the #1 reason why he doesn't use the VE much. I was about to report it, and found that not only it's already reported, but that it's reported by myself :)",1548593910,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-miv67zvinnq5ma6mdz7k,task_subcomment,NA
+VisualEditor: Allow editing of a category link (not just add/remove),"{F4221948}
+
+Being able to edit this would make a big difference for UX. Right now it's border-line inaccessible to make the intended change.
+
+Additionally, the label is not selectable by cursor. The category object is shielded from text selection for some reason, requiring the user to retype it from scratch. This gets worse with T139189.",1467394682,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-miv67zvinnq5ma6mdz7k,task_subcomment,NA
+VisualEditor: Allow editing of a category link (not just add/remove),"(In reply to Amir E. Aharoni from comment #1)
+> Just noticed that the User guide[1] says: ""On the Page options menu there
+> are options [...] to add, edit, or delete categories.""
+> 
+> I'd say that actual ""editing"" must involve the resolution of this bug, and
+> otherwise it is just adding and deleting.
+> 
+> [1] https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide
+
+You can edit each category to add, change or remove the sort key for the page for that category.",1411847706,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-miv67zvinnq5ma6mdz7k,task_subcomment,NA
+VisualEditor: Allow editing of a category link (not just add/remove),"Just noticed that the User guide[1] says: ""On the Page options menu there are options [...] to add, edit, or delete categories.""
+
+I'd say that actual ""editing"" must involve the resolution of this bug, and otherwise it is just adding and deleting.
+
+[1] https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide",1411822235,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-miv67zvinnq5ma6mdz7k,task_subcomment,NA
+"If a reference is defined in a template, and re-used outside of it, and you delete the template, then the reference contents get lost; similarly, copying citations defined inside a template doesn't work","Steps to Reproduce:
+1. Start with a page that contains:
+
+(a) a template with a named ref inside it:  {{quote|Text.<ref name=Foo>Example citation</ref>}}
+
+(b) Some text outside the template that re-uses that citation:  Text.<ref name=Foo />
+
+2. Open the page in VisualEditor and remove the template.
+
+
+
+Actual Results:  
+The named ref becomes undefined.  VisualEditor doesn't ""see"" the citation inside the template, so it can't rescue the re-used template-based citation content when the template is deleted.
+
+Expected Results:  
+That the citation content would be preserved, just like it is preseved when the first instance of a re-used citation in regular page text (outside of templates) is removed.
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1400094060,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ja5zqpx3lc7f2cjcms4a,task_description,open
+"If a reference is defined in a template, and re-used outside of it, and you delete the template, then the reference contents get lost; similarly, copying citations defined inside a template doesn't work","Also, if the only refs are hidden in templates, then when you add a <references /> block, you get the error mesage that ""There are no references on this page to include in this list.""",1406314582,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-ja5zqpx3lc7f2cjcms4a,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"**Author:** `admin`
+
+**Description:**
+Greetings,
+Please enable the Translate and any related extensions to the affcom wiki (chapcom.wikimedia.org) to help us with drafting English based text that will later be utilized on Meta-Wiki. I recognize that actually marking the pages for translation could be problematic - the goal is primarily to utilize tags without making the wikipages difficult to proofread and edit.
+
+Thank you!
+-greg aka varnent
+AffCom Member
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1397876460,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_description,declined
+Translate and related extensions on AffCom wiki,"> we can guess it was just a personal request
+
+If so I'd consider it invalid rather than declined. There's never a good reason to decline enabling Translate if people want to use it.",1467240667,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"I'm going to be bold here and close this task as declined. The requestor is no longer with AffCom, and we don't really know if the people there still wants this or not. No further tickets were filled asking for this feature, so we can guess it was just a personal request from Greg based on a need there back in the days. I've abandoned the gerrit change for this. Please reopen if you disagree. Thank you.",1467150621,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Change 275289 abandoned by MarcoAurelio:
+Enable Translate extension on AffCom (chapcomwiki)
+
+Reason:
+Per task. Requestor is no longer with AffCom and no apparent renewed interest in this feature.
+
+[[https://gerrit.wikimedia.org/r/275289]]",1467150307,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"You can help being present at one of our SWAT windows, for example this night at 23:00 UTC.",1460562206,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"You can help being present at one of our SWAT windows, for example this night at 00:00 UTC",1460562175,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"@Dereckson - I am no longer connected to AffCom having joined WMF as a contractor. However, I still have access to their wiki, and am still in touch with their members and staff liaison (Jaime Anstee). As such, I am happy to help with this ticket in whatever ways would be helpful and logical.",1460468301,PHID-USER-tbsqok4i4d2fpoef36s2,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"@Varnent I discussed again last week the issue with Marco Aurelio, whom isn't really comfortable to process this change.
+
+Would you be available during a SWAT window to help to test this change?",1460422980,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Well in such case, there is not a lot we can do for fishbowls.
+
+So, you can see it deployed during a SWAT window with two strategies.
+
+The first would be to ensure you have someone with access to test that at the moment the change is merged.
+
+The second is a minimal check, then an async broader check:
+
+# check the wiki homepage it's not broken with a fatal exception and all looks good as far as you can tell
+# state during deployment it's not further testable as fishbowl
+# leave the task open, move it in the Done column
+# report here the change is deployed, and ask original task author (here @Varnent) to ensure all is fine
+# You or @varnent can close it as resolved if it's actually fine. If not, you submit a fix or a revert change",1458398634,PHID-USER-4opnqejtv7adgswtxy67,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Please do not assign this to me as I don't have access to the chapcom wiki, thus I won't be able to test if the change works when deployed. Thank you.",1458393536,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"I missed the config rights mentioned above by @Nemo_bis, will try to do in PS2.",1457281006,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,@Varnent @Nikerabbit Will https://gerrit.wikimedia.org/r/275289 achieve what's desired here?,1457280970,PHID-USER-xvs3y6hf6yrfn6sxrk5d,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Change 275289 had a related patch set uploaded (by MarcoAurelio):
+Enabling Translation extension on AffCom (chapcomwiki)
+
+[[https://gerrit.wikimedia.org/r/275289]]
+",1457280835,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,Not stalled AFAICT.,1446737362,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Any progress, or has this stalled?",1443085199,PHID-USER-lumvg23bxmfbvekr2fbo,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Well in that case it's pretty straightforward, just need to explicitly disable all Translate features when enabling.",1433346685,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Responses:
+
+  - We just want to be able to setup <translate> tags while docs are being prepared to help make transitioning to Meta easier.
+  - Most translations would not be happening on the wiki, so we are not concerned about export/import. If translate is used, it will be for things like email messages that are template and housed on AffCom wiki permanently.
+  - Given that there are only a dozen active users, I am not too concerned about accidental markings.
+  - The members who code our pages are familiar with translate extension - I do not anticipate needing additional support.
+  - We do not use VisualEditor much, if at all, although a few members do - we do not anticipate that being a problem given the small percentage of draft pages we are talking about.
+
+If this is too much of a hassle, that's fine, we'll continue to work without. However, it was something we felt would make prep work for draft wikipages going to Meta easier.
+",1433100324,PHID-USER-tbsqok4i4d2fpoef36s2,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"In addition to above:
+* translation memory and other web services should be disabled
+* <translate> tags do not currently work well with visual editor (in case you use it)
+* related database tables must be created when Translate is enabled on a new wiki",1433097590,PHID-USER-732lqsmz4v6bss3kln2v,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"So you want Translate without actually marking pages for translation? If so, what checks are you interested in?
+* If you only want to check balanced translate tags and so on, the solution would be to enable Translate while revoking the pagetranslation right from all groups.
+* If you need Special:PageTranslation for your checks/preparations, how do you plan to avoid accidental marking?
+* If you want to actually mark the pages for translation and have them translated in private before publishing, do you already have a plan for export-import of translations?
+* In any case, do you have users on the wiki who are comfortable using the Translate extension and have enough time to train and assist all the other users, so that you are self-sufficient?",1433082996,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+Translate and related extensions on AffCom wiki,"Niklas, can this be done? I know almost nothing about that extension.",1433072245,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-nz63pogjll27mlyr4bfz,task_subcomment,NA
+VisualEditor: Provide a way (other than selection) to extend link (and other) annotations to more of the content,"When you add text on the left side of a link (external, internal) in article core the content is not merge with the link. T55210 asks to change this.
+
+When you add text on the left side of a link (external, internal) in the reference assistant the content is merge with the link. Someone asks to change this on https://fr.wikipedia.org/w/index.php?title=Wikipédia:ÉditeurVisuel/Avis&oldid=102556548#Gestion_des_liens
+
+A solution might be : On clicking a link, show 2 sliders (left/right of the current link) to handle easily  what is In what is Out of the link
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1396823280,PHID-USER-hhw22zfd2xzrsyc22lp5,False,PHID-TASK-kfwclljbfb2twseyrniu,task_description,open
+VisualEditor: Provide a way (other than selection) to extend link (and other) annotations to more of the content,"These feels very confusing as a use paradigm; boxes suddenly flying out for links (just links? not bold/italics?) seems like it will get in the way of seeing what the existing content has. Marking as ""lowest"" priority and re-wording to be more general.",1398726027,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kfwclljbfb2twseyrniu,task_subcomment,NA
+VisualEditor: Warn/stop users from inserting wikitext/bad inputs in the Gallery inspector,"Right now if , a user inserts wikitext inside gallery inspector such as <gallery></gallery> or <ref> inside gallery inserter, it adds an empty gallery inside the page and if you switch to edit source you will see something like:
+<gallery><gallery><ref></ref></gallery></gallery>
+
+
+One possible solution to this issue could be let user know not to add any such wikitext/bad inputs inside gallery inspector
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: Chrome Version 26.0.1410.65 & FF 25
+OS: MAC OS X 10. 8. 5
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1395169020,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fwu3dpls26ckqdml4hft,task_description,resolved
+VisualEditor: Warn/stop users from inserting wikitext/bad inputs in the Gallery inspector,"Not exactly ""current"". :-)",1519255838,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-fwu3dpls26ckqdml4hft,task_subcomment,NA
+VisualEditor: Warn/stop users from inserting wikitext/bad inputs in the Gallery inspector,"This has been resolved by the new gallery dialog, which doesn't allow users to input weird wikitext into the <gallery> tag (T45037).",1519255714,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-fwu3dpls26ckqdml4hft,task_subcomment,NA
+VisualEditor: Warn/stop users from inserting wikitext/bad inputs in the Gallery inspector,"Created attachment 14853
+Screenshot
+
+**Attached**: {F13152}",1395169083,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-fwu3dpls26ckqdml4hft,task_subcomment,NA
+VisualEditor: Be able to set a multimedia item's thumb position (thumbtime=) in the media dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394835120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-shlqtr6tjud3djafldgi,task_description,open
+VisualEditor: Be able to set a multimedia item's start position (start=) and end position (end=) in the media dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394835000,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-5lq7dixzl5nvcmty4r7v,task_description,open
+VisualEditor: Be able to set a multimedia item's start position (start=) and end position (end=) in the media dialog,"I'd like to try to find someone to help make this happen, how difficult would this be to do and what skills would the person need? ",1543864604,PHID-USER-bmbtggsblh3aipffyl4i,True,PHID-TASK-5lq7dixzl5nvcmty4r7v,task_subcomment,NA
+VisualEditor: Be able to set a multimedia item to not show an icon (noicon) in the media dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834880,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-fzczz22mbckxwxyidfg7,task_description,open
+VisualEditor: Be able to set an item's alignment (baseline/middle/…) in the media edit dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834640,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-pfqaskw64eurbsarzh27,task_description,open
+VisualEditor: Be able to set a over-ride thumbnail (thumb=…) in the media edit dialog,"Moved out of bug 38129's wishlist into its own bug.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1394834520,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-p75r2s6odgzvudzsebc2,task_description,open
+Jenkins: Set up perceptual diffs (visual regression testing),"This is something I've been experimenting with in spare time for a while.
+
+The idea is: Render a visual diff for one or more pages and states thereof (comparing the result of the current change to the result of the latest master, or whatever target branch the commit has).
+
+The screenshots would be created using PhantomJS' render() API. Or, while we don't need cross-browser per se, having a browser more representative than PhantomJS would be nice. Perhaps using Chromium under Xvfb with a large enough window (we don't need it to be very tall). And capture output from Xvfb using ImageMagic display `import`.
+
+Rough idea for the Jenkins job:
+
+* Run project setup (e.g. build script for projects like OOjs UI and VisualEditor; installing MediaWiki for core/extensions). Then expose workspace to the local web server (We've got re-usable macros for this already).
+
+* Run the scenarios or urls for the current project and capture the screen after each scenario.
+
+* Compare them against the ones from the last run (e.g. for a commit to master, compare them to the latest master build). TODO: Will need to be stored somewhere. Shared NFS maybe? `store/{project}/{branch}`.
+
+* In test pipeline:
+ * If different, make sure the latest.png/change-after.png/change-diff.png for that url is kept and stored as build artefacts in Jenkins. Otherwise delete the image.
+* In the post-merge pipeline:
+ * Replace the images in the store with those of this build.
+
+Scenarios:
+
+I imagine we'll need to support two kinds of scenarios:
+
+* Plain url.
+* Web driver steps (for large interfaces not accessible by url). This should *not* be used to trigger every possible dialog and component, that slows the test matrix and only tests for no reason. More useful would be to capture individual components via e.g. the OOjs UI demo page. Use these two assert the composition rather.
+
+A few urls we might want:
+* mediawiki-core:
+ - /index.php?title=Main_Page
+ - /index.php?title=Main_Page&useskin=monobook
+ - /index.php?title=Main_Page&action=edit
+ - /index.php?title=Main_Page&action=history
+ - /index.php?title=Special:UserLogin
+ - /index.php?title=Special:UserLogin/signup
+ - /index.php?title=Special:Search&search=wiki
+* VisualEditor:
+ - /demos/ve/#!/src/pages/empty.html
+ - /demos/ve/#!/src/pages/simple.html
+ - /demos/ve/#!/src/pages/complex.html
+* oojs-ui:
+ - /demos/icons.html
+ - /demos/widgets.html
+
+A few implementations that exist:
+* https://github.com/uber/image-diff/
+* https://github.com/bslatkin/dpxdt/
+* Talk (Velocity 2013): https://www.youtube.com/watch?v=1wHr-O6gEfc
+* Talk (Google Developers): https://www.youtube.com/watch?v=UMnZiTL0tUc
+
+Behind these is basically just a ImageMagick compare command between two PNGs.
+* https://github.com/bslatkin/dpxdt/blob/8e76f62e5/dpxdt/client/pdiff_worker.py#L115-L127
+* https://github.com/uber/image-diff/blob/1.0.1/lib/image-diff.js#L53-L65
+* http://www.imagemagick.org/Usage/compare/
+````
+compare
+      -verbose
+      -metric RMSE
+      -highlight-color RED
+      -compose Src
+      mytest-latest.png
+      mytest-build.png
+      mytest-diff.png
+```
+
+See also:
+* {T64511}",1394769900,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_description,stalled
+Jenkins: Set up perceptual diffs (visual regression testing),"Web team has built out a solution here without jenkins that is working well so far. I am curious Timo if this could solve what you had in mi d.
+
+Reports can be found at https://pixel.wmcloud.org
+
+More information at T302246: [GOAL] Leverage Automated Visual Regression Testing",1652228622,PHID-USER-5dwuaigmkz2vzg65lape,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),Until we have a data store to expose the generated files ( {T101545} ). There is not much we can do on this task.,1444134912,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),Lowering priority from high to normal since nobody is apparently actively pushing for this change.  Whenever the feature teams figure out a good utility / way to do such visual differences we can work on integrating it on Jenkins/Zuul.,1408458358,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),"See https://github.com/subbuss/parsoid_visual_diffs for a version that is being used to compare Parsoid and PHP parser HTML output. That works quite well and has already exposed a few css issues and other non-css rendering/html diffs.
+
+Something similar could perhaps be adapted for this purpose as well?",1404789309,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),Mentionned by Subbu on IRC: an example of what visual diffs can bring to us http://diplograph.net/posts/visual_diffs,1403558710,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),"**jgonera** wrote:
+
+See also: https://gerrit.wikimedia.org/r/#/c/126878/",1397862936,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),See also: https://github.com/facebook/huxley,1395961811,PHID-USER-z3l4i7dl52qicxtephy5,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),"I assume that it's easier to roll our own than to re-use wraith or something similar, due to trying to integrate it into jenkins? Multi-platform screenshot regression testing is probably a secondary-level target, but…",1394812559,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+Jenkins: Set up perceptual diffs (visual regression testing),"The job would be non-voting of course, and we'd change the jenkins-bot comment to Gerrit to CHANGED/UNCHANGED instead of SUCCESS/FAILURE.",1394770023,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-kvgadhnokjawoz2a3myt,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"Some MediaWiki installations have images hosted on a different domain than the wiki, and in some cases do not have an 'Access-Control-Allow-Origin' header on the image server domain. This causes the XMLHttpRequest for MultimediaViewer to fail, and nothing but a black screen appears. So that the usability isn't completely broken in these (and similar) situations, if the XMLHttpRequest to get the image fails for any reason, MultimediaViewer should fall back to simply displaying the image using an <img> tag.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1394426460,PHID-USER-qze3uk4zsetjvgf7liey,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_description,open
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,One of the problems is that the request is sending `withCredentials` marked true in the actual XHR. Is there a way to disable it?,1619556311,PHID-USER-bb2gcrpsvrrae4vbf4da,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,This issue still hasn't been resolved. The fallback to img tag is a very reasonable request.,1619554987,PHID-USER-bb2gcrpsvrrae4vbf4da,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"Mass-removing the Multimedia tag from MediaViewer tasks, as this is now being worked on by the Reading department, not Editing's Multimedia team.",1442850249,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"**bryanhunt** wrote:
+
+I can't comment on the rational other than to say that the behavior is common enough to indicate it would be condition worth considering. Due to the fact that the CORS header is requesting a browser to relax its security level it does sort of make sense that peripheral security would flag that as dangerous in that regard.
+
+The being said switching over to https does resolve the problem so offering that as an option to the user when the error screen shows up could be the easiest way to handle condition.",1405114675,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"We do fail more gracefully now (there is an error message, not just a black screen of deatch which is what the OP was complaining about). Could look nicer (we have some design notes in https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/299 ) but that's very low priority.
+
+I'll think about adding a fallover, but we have too many of them already (the image loading can fail in other ways) and the logic is getting way too complex for its own good. Also, while the image could be loaded without CORS, some of the metadata API requests could not (we could probably recover from those requests failing, though).
+
+All that said, stripping CORS headers is horribly broken behavior and makes zero sense from a security point of view. You should probably complain to the manufacturer / whitelist Wikipedia domains.",1405112327,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"**bryanhunt** wrote:
+
+Yes, while that is true (watchguard), it is far from an extraordinary configuration ( http://www.garysieling.com/blog/dont-use-access-control-allow-origin ) and the OP's comment was that the application should fail a bit more gracefully the headers don't exist. Web tech is far from my area of expertise but as a developer I would have to concur with the OP that it does make sense for Media Viewer to fail over to another mechanism to ensure a functional application in these situations.
+
+An interesting note is that while Firefox & Chrome both exhibit the same failure mode, IE (11.0.9) does not appear to - making me assume that it either lacks similar security checks or is already using a different mechanism.",1405096530,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"Wikipedia images are served with correct CORS headers:
+
+
+$ curl -vo/dev/null 'http://upload.wikimedia.org/wikipedia/commons/thumb/8/8a/Media_Viewer_-_View_Original_File_-_Mockup_1024px.jpg/1024px-Media_Viewer_-_View_Original_File_-_Mockup_1024px.jpg' 2>&1 | grep Access-Control
+
+< Access-Control-Allow-Origin: *
+< Access-Control-Expose-Headers: Age, Content-Length, Date, X-Cache, X-Varnish
+
+$ curl -vo/dev/null 'https://upload.wikimedia.org/wikipedia/commons/thumb/8/8a/Media_Viewer_-_View_Original_File_-_Mockup_1024px.jpg/1024px-Media_Viewer_-_View_Original_File_-_Mockup_1024px.jpg' 2>&1 | grep Access-Control
+
+< Access-Control-Allow-Origin: *
+< Access-Control-Expose-Headers: Age, Content-Length, Date, X-Cache, X-Varnish
+
+
+Maybe you are you behind some sort of proxy which messes with the headers?",1405040062,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"**bryanhunt** wrote:
+
+Media Viewer handling of lack of CORS headers in Chrome
+
+This seems to be the root cause of the chrome rendering problem of wikipedia images since media viewer is now enabled by default. I am quite surprised I couldn't find any other reference for media viewer simply not working for Chrome.
+
+I have confirmed this behavior in Chrome Version 35.0.1916.153 m on windows XP, 7, & 8
+
+**Attached**: {F12997}",1405033109,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"There could be a flag (off by default) to enable AJAX image loading; when off, we could show a static (positionless) loading bar.",1403822668,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"(In reply to Tisza Gergő from comment #5)
+> George: the MultimediaViewer version you use is outdated, the current
+> version loads images differently. Do you want to give a shot at updating to
+> the current version? (The tip of the 1.23wmf17 branch should be a safe
+> choice.)
+> 
+> I expect it will still fail, but for an entirely different reason, and that
+> will be easy to fix.
+
+Alright, I updated the extension. It works and does have the fallback, but the fallback also blurs the image a lot. I know why it's doing that, but maybe should it not upscale the img tag bigger than the image's thumbnail was?",1394489121,PHID-USER-qze3uk4zsetjvgf7liey,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"For now I am setting this back to unconfirmed, most of the image loading code has been replaced since then.",1394486794,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"George: the MultimediaViewer version you use is outdated, the current version loads images differently. Do you want to give a shot at updating to the current version? (The tip of the 1.23wmf17 branch should be a safe choice.)
+
+I expect it will still fail, but for an entirely different reason, and that will be easy to fix.",1394486512,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"Contents of the console:
+
+XMLHttpRequest cannot load http://images.brickimedia.org/7/7d/Goodship1.jpg. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://dev.brickimedia.org' is therefore not allowed access. 
+
+Uncaught TypeError: Cannot read property 'length' of null mmv.provider.Image.js:93
+Image.binaryToDataURI mmv.provider.Image.js:93
+(anonymous function) mmv.provider.Image.js:73
+(...)
+request.onreadystatechange mmv.performance.js:71",1394482240,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,Tracked in Mingle as https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/295,1394477799,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"(In reply to Tisza Gergő from comment #1)
+> We do have an <img> fallback, but it sets img.crossOrigin = true on certain
+> browsers where the fallback would otherwise result in downloading the image
+> twice. Just to be sure that is really the cause of the problem, is there a
+> public wiki where this bug can be reproduced?
+
+Yes, here is an example: http://dev.brickimedia.org/wiki/VisualEditor You'll have to make an account so you can enable it in Beta Features (I think) but that only takes a minute or so.",1394471169,PHID-USER-qze3uk4zsetjvgf7liey,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers,"We do have an <img> fallback, but it sets img.crossOrigin = true on certain browsers where the fallback would otherwise result in downloading the image twice. Just to be sure that is really the cause of the problem, is there a public wiki where this bug can be reproduced?",1394471074,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-ma2djbmaav4mlnfs25tp,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"We apply red link styles to nonexistent titles in the link suggestions, so for redirects and disambig pages the corresponding styles/classes should be applied as well.
+
+I don't actually know what these are, ask James :)
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial",1391818500,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-zddhewpobyqo3lkurdqv,task_description,resolved
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"Change 345883 merged by jenkins-bot:
+[mediawiki/core@master] mw.widgets.TitleOptionWidget: Apply styles for redirects/disambiguation links
+
+[[https://gerrit.wikimedia.org/r/345883]]
+",1491061072,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,">>! In T63072#3147540, @matmarex wrote:
+> I don't think so – that one did it for links in the editing surface, but not in the link inspector suggestions dropdown. Looks like this code lives in mw.widgets.TitleOptionWidget now.
+> 
+> …and we actually handle redirects and disambigs there with custom icons. So this should be trivial.
+
+Oh, hah, I thought we'd done it when the code was in VE but clearly I was wrong. :-)",1491060513,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"Change 345883 had a related patch set uploaded (by Bartosz Dziewoński):
+[mediawiki/core@master] mw.widgets.TitleOptionWidget: Apply styles for redirects/disambiguation links
+
+[[https://gerrit.wikimedia.org/r/345883]]
+",1490992438,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"I don't think so – that one did it for links in the editing surface, but not in the link inspector suggestions dropdown. Looks like this code lives in mw.widgets.TitleOptionWidget now.
+
+…and we actually handle redirects and disambigs there with custom icons. So this should be trivial.",1490992221,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,This was done by @matmarex way back in August 2014 (two weeks after my comment above) – 066283dde745fcc372ffab8d753962858813d032.,1490898090,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"(In reply to Bartosz Dziewoński from comment #2)
+> We actually don't apply any classes, ve.ui.MWLinkTargetInputWidget.css just
+> has some styles defining a close-enough reddish color. (This is kind of bad
+> since the color can differ per-skin.)
+> 
+> .ve-ui-mwLinkTargetInputWidget-menu .oo-ui-menuItemWidget[rel=newPage] {
+> 	color: #BA0000;
+> }
+> 
+> There are no styles by default for redirect and disambiguation links, some
+> users choose to style them in various ways (usually green for redirects and
+> maroon for disambigs). 
+
+Presumably the styles will be ported over to Parsoid content, at which point we can just apply them directly?
+
+
+> I'm not sure if we should do this for the link in the inspector; they are
+> already visually distinct by being placed in separate sections. We might
+> want to remove the reddish styles too...
+
+I'm not sure. Consistency of hinting is important.",1406821549,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,"We actually don't apply any classes, ve.ui.MWLinkTargetInputWidget.css just has some styles defining a close-enough reddish color. (This is kind of bad since the color can differ per-skin.)
+
+.ve-ui-mwLinkTargetInputWidget-menu .oo-ui-menuItemWidget[rel=newPage] {
+	color: #BA0000;
+}
+
+There are no styles by default for redirect and disambiguation links, some users choose to style them in various ways (usually green for redirects and maroon for disambigs). 
+
+I'm not sure if we should do this for the link in the inspector; they are already visually distinct by being placed in separate sections. We might want to remove the reddish styles too...",1406813705,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector,*** Bug 64584 has been marked as a duplicate of this bug. ***,1401417534,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zddhewpobyqo3lkurdqv,task_subcomment,NA
+"VisualEditor:  Add a Preview feature to show actual version of page (minus slugs, etc.)","VisualEditor has some deliberate/non-buggy differences in its display, compared to what readers will see on a saved page, such as the addition of blank lines/slugs to make adding new items at the top of a page.  These differences sometimes confuse users.
+
+Add a preview button so that users can see the final version, rather than the slightly different VisualEditor version.
+
+**See Also**:
+*{T49790}
+*{T44139}
+*{T39931}",1390928460,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qi6wc6gcqjrnpifmlnvz,task_description,open
+"VisualEditor:  Add a Preview feature to show actual version of page (minus slugs, etc.)",Suggestion from SarahTehCat:  Use the 'Live Preview' system (if it's stable).,1425493251,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-qi6wc6gcqjrnpifmlnvz,task_subcomment,NA
+VisualEditor does not format hatnotes correctly,"comparison of screenshots
+
+Currently, VisualEditor inserts blockSlugs around rellinks and dablinks (collectively known as hatnotes). This adds a lot of extra whitespace around them compared to how they are formatted normally. See attachment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+
+**Attached**: {F13459}",1390875300,PHID-USER-a5pveeqqwaddgfjiv2fq,False,PHID-TASK-3eutuphwveuy6tgpm2lo,task_description,open
+VisualEditor does not format hatnotes correctly,"Still exists (see testcase at https://en.wikipedia.org/wiki/User:Neil_P._Quinn-WMF/T62516). We now explain this inconsistency somewhat better by showing a ""insert paragraph"" message when you hover over one of the slugs (see screenshot), but this still falls short of our ideal of having the VisualEditor surface appear identical to the read surface.
+
+{F160551}",1430783645,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-3eutuphwveuy6tgpm2lo,task_subcomment,NA
+VisualEditor: Provide option in media insertion dialog to only show local media,"**Author:** `gabriel.birke`
+
+**Description:**
+There is no way to make the VisualEditor Media selection to look only for local media (send iilocalonly when querying imageinfo). While this is ok for Wikipedia, it's not suitable for other wikis.
+
+There should be a checkbox in the search dialog to switch to local only search.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1389260880,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-eudgmmbmz7t3therwbwh,task_description,open
+"VisualEditor:  Unable to select empty section heading (e.g., to remove it) at the end of a page","Intention:
+Remove a blank section heading (==<nowiki/>==) at the end of a page.
+
+Steps to Reproduce:
+1. Place cursor on blank section heading at the end of the page.
+2. Try to select it.
+
+
+Actual Results:  
+Nothing.  Also, it's not possible to select the whole line (e.g., to cut and paste it, leaving nothing behind) even after you type something on the section heading.  If you type ""abc"", then you can select and cut ""abc"" (Note:  what it cuts is *not* ""==abc==""), but the ==<nowiki/>== will remain.
+
+
+Reproducible: Always
+
+You can test this at https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox2&oldid=589158823
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1388854560,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-j2mehk62spszuq5kxa3y,task_description,resolved
+"VisualEditor:  Unable to select empty section heading (e.g., to remove it) at the end of a page","This seems to no longer to be a problem. I can remove the heading in the example page in two ways:
+* By putting the cursor inside it and pressing Backspace
+* By changing the format from ""Heading"" to ""Paragraph""",1542996092,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-j2mehk62spszuq5kxa3y,task_subcomment,NA
+"VisualEditor:  Unable to select empty section heading (e.g., to remove it) at the end of a page",The bug confirmed  - <nowiki/> cannot be deleted from VE.,1421789796,PHID-USER-4alekd35in5tg53zpsl4,True,PHID-TASK-j2mehk62spszuq5kxa3y,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Screenshot
+
+Steps to reproduce:
+
+1.Open a page with VE
+2.Add any image
+3.Open the dialog box to add image again
+4.Type a different string in the textbox to search for matching images.
+
+Observed Result:
+An error appears TypeError: jQuery1830683983782510787_1388777743220 is not a function
+
+See the screenshot attached 
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/New_pageimage?veaction=edit
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+
+**Attached**: {F12791}",1388778000,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_description,declined
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",*** Bug 58364 has been marked as a duplicate of this bug. ***,1406740632,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",*** Bug 68059 has been marked as a duplicate of this bug. ***,1405543712,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Also:
+* Upstream jQuery: http://bugs.jquery.com/ticket/8744 (status: cantfix)
+* Closely related upstream Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=707154 (status: NEW)",1403055668,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","As such, please don't waste any more time on this. This is harmless errors that we can't do anything about and are side-effects of behaviour that is very much intended and wanted by us. Just another one the category of browsers being ugly and/or minor issues upstream.",1403055051,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","That patch, as far as I can see, did nothing. And if it did, it would actually have caused a regression.
+
+The TypeError thrown is caused by the JSONP <script> tag request finishing and trying to invoke a temporary global function that jQuery exposed, but has revoked since because the consumer of $.ajax, VisualEditor in this case, has aborted the request.
+
+All jqXHR objects have an abort method. Duck-typing it is useless because it is always there.
+
+And while JSON-P doesn't have a native abort mechanism, jQuery does a good job of emulating it (it will do a best effort approach to cancel the http request for efficiency reasons, and in case it still makes it, it will make sure it reaches a dead end and not cause our application code to process its data[1]).
+
+As I mentioned before, the dead end results in a Uncaught TypeError which sounds bad, but isn't, because it's in an asynchronous and independent call stack that has no influence on either our or jQuery's cod execution.
+
+[1] Even if there was a way to not half-abort these requests, we wouldn't want that. We actually want these requests to reach a dead end. Otherwise we'd get race conditions where you type ""a"", ""ab"", ""abc"" and after ""ab"" is intended to be aborted, it might still arrive *after* ""abc"" and mess up our search results.",1403054973,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Change 140044 merged by jenkins-bot:
+Media search dialog: Only try to abort request if possible
+
+https://gerrit.wikimedia.org/r/140044",1403026198,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Change 140044 had a related patch set uploaded by Alex Monk:
+Media search dialog: Only try to abort request if possible.
+
+https://gerrit.wikimedia.org/r/140044",1402960839,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","I already had InstantCommons enabled, but couldn't reproduce it before. Looks like I can now.",1402960294,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","This can be reproduced when using the input field for the Media insertion dialog.
+
+E.g. on https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet?veaction=edit
+
+It might not throw the error on your local wiki if your wiki is not configured to use a separate wiki, e.g. Wikimedia Commons, as extra file repository. Enable wgUseInstantCommons if you haven't already.
+
+https://www.mediawiki.org/wiki/Manual:$wgUseInstantCommons",1402830324,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",Looks like we fixed this – possibly by resetting the search on open?,1402694967,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",Although I can't actually reproduce this error.,1402690209,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","(In reply to Krinkle from comment #5)
+> This doesn't affect our callstack in any way, and from our perspective it
+> works as expected (after the request is aborted, our callback must not fire).
+> 
+> This last part is a jQuery internal implementation detail that might change
+> in the future, but either way, it is out of our hands, doesn't affect
+> anything, and nothing we can do anything about.
+
+I'm tempted to wontfix this, but apparently people are complaining that VE is broken because of it. I guess we'll just have to suppress the error.",1402689014,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Lowering priority as this is merely a console notice. It doesn't affect anything in any way, it is in fact ""expected"" behaviour by jQuery due to there not being another way to do what it does.
+
+What it does is cancel a cross-domain ajax request. Short of CORS/XHR, there isn't actually such thing as a cross-domain ajax request. What it really does (and we rely on this) is JSON-P, which is a <script> tag to the api.php entry point with a temporary function as callback (this is a sort-of standard method called ""JSON-P"" which MediaWiki actively supports, it's not a VE intention or a hack beyond what it is).
+
+As with many ajax-based content population requests (e.g. search suggestions, auto completion etc.) we abort pending requests when we fire off the next. When interacting with the local API, we use regular XHR which has an abort method.
+
+When interacting with a foreign API, jQuery gives us an XHR-like interface but really underneath it is JSON-P, which means there isn't a way to actually abort the request. Instead, jQuery deletes the callback and does a best-effort approach to cancel the request. When the request does come back, it will try to invoke a callback that has already been revoked, which results in a TypeError in the asynchronous callstack of the ajax request.
+
+This doesn't affect our callstack in any way, and from our perspective it works as expected (after the request is aborted, our callback must not fire).
+
+This last part is a jQuery internal implementation detail that might change in the future, but either way, it is out of our hands, doesn't affect anything, and nothing we can do anything about.",1389376025,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted",This issue is happening on mw.org too,1389375010,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","This issue is still occurring while inserting image inside Media Settings and Reference Dialog.
+
+Steps to reproduce:
+
+1.Click on a image inside VE
+2.Go to Media Settings 
+3.Type something as caption and add another image inside it
+
+Second way to reproduce:
+
+1.Click on a reference inside VE
+2.Type something and add a image in this dialog box
+
+Screenshot attached
+
+Test Environment: http://en.wikipedia.beta.wmflabs.org/
+Browser: FF 25
+OS: MAC OS X 10. 8. 5 
+Page:http://en.wikipedia.beta.wmflabs.org/wiki/Jan8th?veaction=edit",1389210897,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Created attachment 14258
+Reproduced on 8th January
+
+**Attached**: {F12793}",1389210883,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: Console shows ""TypeError: jQuery1xxxxx is not a function"" when cross-domain ajax request is aborted","Not happening anymore.Possible fix for the bug might be: https://gerrit.wikimedia.org/r/#/c/102377/
+as discussed with Moriel.",1389055776,PHID-USER-24djtv3gj5gua2y6u2g5,False,PHID-TASK-u6zd7ambsyqiu2ueio6t,task_subcomment,NA
+"VisualEditor: If more than one section was changed, no section title should be shown in the edit summary","To reproduce:
+
+0. Go to a page with two sections.
+1. Click the ""Edit"" link on the second section.
+2. Make some changes in the first section.
+3. Press the save button.
+
+Observed: The second section's name is shown in the summary.
+Expected:
+1. If only one section was changed, then that section's title should be shown in the summary.
+2. If more than section was changed, no section title should be shown.
+
+--------------------------
+**Version**: unspecified
+**Severity**: trivial
+**See Also**: T53903",1387043280,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-gdczdi6me4o4ykhiyif2,task_description,open
+"VisualEditor: If more than one section was changed, no section title should be shown in the edit summary","The current behavior 
+- clicking on Edit in a section makes all page(sections) available for editing in VE. 
+- if there are two sections  - 'Review your changes' in save box will display both section titles - no matter which section was opened or edited
+- with three or four - only the section title to which changes were applied will be displayed
+",1419969643,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-gdczdi6me4o4ykhiyif2,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","**Author:** `Wikifram`
+
+**Description:**
+When I edit a page, and add a reference to the text and a different reference to an image caption, all in one edit, then the reference text for the image caption is not saved but gets changed to the reference text from the text (this already happens in the preview). You now get two references with the same text, even though you gave them a different text. 
+
+Example: [https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=840234&oldid=840227] (the image caption ref had a different text on typing)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1386760560,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-nnnclbqpn5cgksi3kujo,task_description,invalid
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","Can **not** reproduce the issue (anymore). See the following test:
+
+- Edit/Create a page in VE
+- In one edit:
+  - Add a plain reference using the VE reference dialog with e.g. content `A`
+  - Add an image using the VE image dialog and in that process adding a plain reference to the caption with e.g. content `B`
+  - Save
+
+I then get two references with the two texts as exprected. Feel free to re-open the issue if there's something new to it.
+",1726499520,PHID-USER-k5wpqok2x66oei3wguaf,False,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","Can **not** reproduce the issue (anymore). See the following test:
+
+- Edit/Create a page in VE
+- In one edit:
+  - Add a plain reference using the VE reference dialog with e.g. content `A`
+  - Add an image using the VE image dialog and in that process adding a plain reference to the caption with e.g. content `B`
+  - Save
+
+I then get two references with the two texts as exprected. Feel free to re-open the issue is there's something new to it.
+",1726499498,PHID-USER-k5wpqok2x66oei3wguaf,False,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","{T87106} isn't quite a duplicate of the outcome, but it's the same issue.",1423675748,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","The key bug here is bug 47344, about using sub-documents instead of the current hack. This would affect media captions and references, and possibly other things.",1415054373,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text",See also bug 60919?,1414883373,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text",I can reproduce this issue.,1414812757,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text","Change 102386 had a related patch set uploaded by Aquifacae:
+Changed wiktionary/en.ico favicon to proper image and resolutions
+
+https://gerrit.wikimedia.org/r/102386",1387344005,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-nnnclbqpn5cgksi3kujo,task_subcomment,NA
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","**Author:** `Wikifram`
+
+**Description:**
+This version of my sandbox at enwiki, [https://en.wikipedia.org/w/index.php?title=User:Fram/sandbox&oldid=585258547], is no longer editable in VE by me (FF25, W7). It opens, and I can make whatever changes I want, but the ""save"" button stays disabled, and when I open the reference interface, I can no longer close that one either. The category and media interface work allright though.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57573",1386683160,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oycdhxzb7vj25wmx37yl,task_description,invalid
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","Sorry for randomly stumbling over that ticket. I can not reproduce the issue anymore. What I did:
+
+I open the sandbox with the revision linked and edit that revision in VE:
+- I can make changes in the editor and the `Save` button becomes enabled.
+- I can open, use & close the references interface without issues.
+
+Feel free to re-open the task if anything remains or I missed a point here.
+",1726500810,PHID-USER-k5wpqok2x66oei3wguaf,False,PHID-TASK-oycdhxzb7vj25wmx37yl,task_subcomment,NA
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","Yuck.
+
+So the problem is that you've got a reference in an image's caption, which is inside a reference; this is not allowed in wikitext (as you can see from the ""Cite error: A <ref> tag is missing the closing </ref> (see the help page)."" error), and is because the restriction on media items' captions doesn't inherit the restriction of the reference block.
+
+We'll need to build a way for restrictions to be explicit and inheritable.",1386697008,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-oycdhxzb7vj25wmx37yl,task_subcomment,NA
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","**Wikifram** wrote:
+
+[16:24:59.875] TypeError: itemNode is undefined @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20131210T024153Z:298",1386689836,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-oycdhxzb7vj25wmx37yl,task_subcomment,NA
+"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load","Could you please open the Error Console (or whatever it is called in your browser) and reload the page that you see the problem on? If there is a problem or an error with JavaScript it should be printed in that console.
+For more information please see:
+* Firefox ≥24: https://developer.mozilla.org/en-US/docs/Tools/Web_Console
+* Internet Explorer: http://msdn.microsoft.com/en-us/library/ie/dn255006
+* Google Chrome: https://developers.google.com/chrome-developer-tools/
+* Apple Safari: https://developer.apple.com/library/safari/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/PrototypingYourWebsite/PrototypingYourWebsite.html
+* Opera: http://help.opera.com/Linux/12.10/en/errorconsole.html",1386687050,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-oycdhxzb7vj25wmx37yl,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu","Steps to reproduce:
+
+1. Go to https://en.wikipedia.org/wiki/Wax_foundation
+2. Click on ""Edit"".
+
+The first image is automatically selected, and its four corners are replaced with image resizing icons, but ""Media"" image editing icon is not shown. I expected that the image would not be selected, or if selected that image editing icon is shown.
+
+3. Click on the second image.
+4. Click again on the first image. Now the image editing icon should be shown.
+5. Click on the image editing icon.
+6. Click on the word ""frame"". Link editing icon should be shown.
+7. Click on the link editing icon.
+8. Enter ""Beehive frame"" (without quotes) in the text box.
+9. Click on ""Apply changes"".
+10. Click on ""Save page"". ""Save your changes"" dialogue appears.
+11. Click on ""Save page"" in the new dialogue.
+
+The VisualEditor displays ""Your changes to Wax foundation have been saved."", but nothing has actually been saved.
+
+Now, I see three bugs here:
+
+1) The first image should not be selected automatically.
+2) Possibly I have to do something after entering the link target in order for the target to be ""applied"" to the image caption? But I don't see what it is that I should do.
+3) The editor shouldn't display ""changes have been saved"" message when there are no changes to be saved; doing so prevents the people from knowing that what they did was not saved, regardless of whether there was an error on their part or on the VisualEditor part.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=58248
+https://bugzilla.wikimedia.org/show_bug.cgi?id=62542",1385195700,PHID-USER-asiusr6cw73okn35tobw,False,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_description,open
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu",(Confirmed still an issue.),1429559780,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu",*** Bug 62650 has been marked as a duplicate of this bug. ***,1394818952,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu","We now try to select the nearest content branch, so this bug is only reproduceable if the document consists of just an image.",1392388656,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu","1.1) I believe the image should not be selected, but I understand people might have different opinion about it.
+
+1.2) But if the image is selected, then the icon must be shown as well. I see this as an obvious bug.
+
+2)
+
+OK, it appears that in order for the link to be applied, I have to click on < icon in the top left corner of the link editing box; or, I have to press Enter twice; or, click in the text editing box and then in the space below it(?).
+
+To me, and I believe other editors, this is very unintuitive. Perhaps < icon could be changed to ✓ - I see < as signifying 'Undo' rather than 'Apply'. Perhaps ""Apply changes"" should be ghosted when there are no chages to apply. But even with these changes I don't see how I could intuitively know what I should do.
+
+The ""Review your changes"" button shows correctly whether I have any changes.",1385452878,PHID-USER-asiusr6cw73okn35tobw,False,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu","I'll leave the first question to others, for the other ones:
+2) You need to make sure that you select the word you want (then you click on it, press Enter, whatever). Try and review your changes before you save: is it there now? If it is, you should be able to save and your edit should stay in the page history. If it isn't, please let us know the browser (and its version) and Wikipedia skin you use.
+3) I experienced something similar back in July: https://bugzilla.wikimedia.org/show_bug.cgi?id=51243 .",1385398701,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-qhhgdhl7wtfejwnw6kuy,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","Intention:
+Re-use a reference.
+
+
+Actual Results:  
+The ref naming scheme needs improvements so that humans can remember which ref name they want to re-use, especially if they are using the wikitext editor, where they will not have any of the possible hints that VisualEditor may provide.
+
+Expected Results:  
+A system that is ""xxx:0"", where ""xxx"" is text simply copied out from the beginning of the named ref would be an improvement.  We can assume that anything inside the ref is in a language that the editor is capable of coping with.  We can exclude the names of templates and their parameters, as well as ""http"" (otherwise, bare URLs in refs will produce a lot of equally unfriendly <ref name=htt:n> names).
+
+Reproducible: Always
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1385163660,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_description,duplicate
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","
+
+*** This bug has been marked as a duplicate of bug 50568 ***",1414104088,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","Speaking as an extensive editor, I just find the exist reference I want to re-use and manually copy the name; this is no extra work in VE. Clearly some people try to remember the name between uses, but given that random people write random names for references already…",1385399054,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","I realize that any automagic system will have serious limitations, compared to prompting users for a human-created name (which VisualEditor ought to be doing).  But a semi-random string of letters is actually easier for most people to remember than a purely incremental number.  <ref name=""sgd1""> and <ref name=""iuo2""> are easier to keep straight than <ref name="":1""> and <ref name="":2"">—and <ref name=""usc1""> and <ref name=""lee2"">, when the ref's contents actually meantion USC and Lee, are even easier.
+
+I don't understand how including some letters (taken from the ref's contents) in the ref name would fail to work anywhere, or at least would fail to work at any language that uses left-to-right typing (unless Arabic numbers are also typed right to left; I can imagine that combining RTL for letters with LTR for numbers would be irritating) and a non-IME/non-variant character set (which might also work just fine, but I don't know enough to have an opinion).",1385397795,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","Why humans need to be able to remember the ref names:
+
+Because actual humans actually have to be able to remember the ref name if they're going to re-use it.  They cannot re-use the ref any other way.
+
+This is true for everyone now, because VisualEditor is only showing (at most) the ref names when you try to re-use a ref, which means that anyone trying to re-use a ref currently needs to know whether the ref they want to re-use ref name :0, :1, :2, :3, :4, :5, etc.—sometimes through a dozen or more meaningless numbers.
+
+This is true permanently for anyone not using VisualEditor, because there is no other way to re-use a ref in the wikitext editor except to manually type (or copy) the name of the ref.",1385397298,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+"VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name="":0"">","(In reply to comment #0)
+> The ref naming scheme needs improvements so that humans can remember which
+> ref name they want to re-use
+
+Why?
+
+This is an insane amount of work to do, won't work on wikis that do things in a different way (e.g. this might work for enwiki and frwiki but not dewiki or others), and will likely not actually result in what you want.
+
+I'm hovering on WONTFIX, but will leave this as ""Lowest"" instead for now.",1385394470,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-j3rfh4pmjx4pel7dk2tn,task_subcomment,NA
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"In the linked diff I added an external link within single brackets.
+It didn't trigger the markup warning - I wouldn't know how to add such links in VE.
+The markup guide for en.wp says these links are ""Only used within article body for footnotes"", but of course they might be used also outside ns0.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2Fsandbox&diff=582808389&oldid=582806629
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=57419",1385123700,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hryitnavu3rbrhqscuk7,task_description,declined
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"On reflection, I'm WONTFIXing this as it'd be too disruptive for a temporary notice.",1398713139,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hryitnavu3rbrhqscuk7,task_subcomment,NA
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"I worry that this would interfere with languages which use []s rather than ()s in text – remember that the wikitext warning is for rare, occasional chiding comments for users who've temporarily forgotten that they're using a rich editor rather than wikitext.
+
+If you want to write ""using sites like Amazon [http://amazon.com and its local country variants] or eBay [http://ebay.com etc.]"" you're going to be rather annoyed by this…",1385488985,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-hryitnavu3rbrhqscuk7,task_subcomment,NA
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"(As far as I tested, it can't edit them, that's why I filed bug 57419.)",1385488658,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-hryitnavu3rbrhqscuk7,task_subcomment,NA
+VisualEditor: Adding external link (wikitext style) should trigger wikitext warning,"Steps:
+1. Edit page
+2. Add [http://example.org]
+
+
+Yep, we should change our wikitext detection to account for external links. Widening scope of this bug for external links in general, not just unnamed ones.
+
+Steps:
+1. Edit page
+2. Add [http://example.org Foo] (unnamed external link)
+3. Add [http://example.org] (named external link)
+
+(In reply to comment #0)
+> [..] I wouldn't know how to add such links in VE.
+
+VisualEditor currently doesn't allow (external) links to be created without names. It can edit them (afaik), but not create new ones. This is a separate issue from the wikitext warning not being triggered though.",1385488417,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-hryitnavu3rbrhqscuk7,task_subcomment,NA
+Lots of CSS related noise in FF Web Console on enwiki,"Not urgent, but should probably be investigated and cleaned up were appropriate..
+
+[04:51:59.127] Unknown property '-moz-box-shadow'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.127] Expected 'none' or URL but found 'alpha('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.127] Unknown property 'zoom'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.127] Expected declaration but found '*'.  Skipped to next declaration. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.127] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.128] Error in parsing value for 'background'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.128] Error in parsing value for 'display'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.129] Error in parsing value for 'list-style-type'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.129] Unknown property 'user-select'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.130] Unknown property 'box-sizing'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.130] Error in parsing value for 'background-image'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.131] Unknown pseudo-class or pseudo-element '-webkit-input-placeholder'.  Ruleset ignored due to bad selector. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.131] Unknown pseudo-class or pseudo-element '-ms-input-placeholder'.  Ruleset ignored due to bad selector. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1
+[04:51:59.168] Unknown property 'break-inside'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.169] Unknown property 'speak'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.169] Expected 'none' or URL but found 'chroma('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.170] Unknown property 'zoom'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.170] Expected media feature name but found '-webkit-min-device-pixel-ratio'. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1
+[04:51:59.716] Unknown property 'box-sizing'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page
+[04:51:59.812] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:4
+[04:51:59.812] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:4
+[04:51:59.812] Error in parsing value for 'unicode-bidi'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:6
+[04:51:59.812] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Unknown property '-moz-box-shadow'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Unknown property '-moz-background-clip'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Expected 'none' or URL but found 'progid'.  Error in parsing value for 'filter'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Error in parsing value for 'background'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10
+[04:51:59.812] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.812] Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.813] Unknown pseudo-class or pseudo-element '-o-prefocus'.  Ruleset ignored due to bad selector. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.813] Error in parsing value for 'background'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.813] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:51:59.813] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:16
+[04:52:00.137] Unknown property '-moz-box-shadow'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:2
+[04:52:00.138] Expected 'none' or URL but found 'alpha('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:2
+[04:52:00.138] Expected 'none' or URL but found 'alpha('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12
+[04:52:00.138] Unknown property '-moz-background-clip'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Unknown property '-moz-background-origin'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Expected color but found 'bottom'.  Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Unknown property '-moz-border-radius-topleft'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+[04:52:00.138] Unknown property '-moz-border-radius-topright'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14
+
+--------------------------
+**Version**: 1.23.0
+**Severity**: minor",1385009520,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-wjmyqwnbfehyswxiilbk,task_description,declined
+Lots of CSS related noise in FF Web Console on enwiki,"Unless you have a good reason to kill any of these, this is expected and okay.
+
+The noise refers either to:
+* horrible hacks we need to support older browsers (""Expected
+  'important' but found 'ie'.  Expected ';' or '}' to terminate
+  declaration but found 'ie'."", ""Expected declaration but found '*'.
+  Skipped to next declaration."" – both of these are for IE 6 and 7)
+* browser-specific rules that other browsers do not understand (-ms-*,
+  -webkit-*, …)
+* or things your browser just does not support (""Unknown property
+  'user-select'."").",1385065447,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wjmyqwnbfehyswxiilbk,task_subcomment,NA
+Lots of CSS related noise in FF Web Console on enwiki,"Really depends on our browser version support.  
+For example, ""border-radius"" property is supported since Firefox 4; deprecated ""-moz-border-radius"" is required for Firefox 3.x and older, and unsupported since Firefox 13.",1385065111,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-wjmyqwnbfehyswxiilbk,task_subcomment,NA
+Lots of CSS related noise in FF Web Console on enwiki,"So... those are just the CSS parser saying it doesn't recognize various things that are there for other browsers or older browsers.
+
+Not sure how actionable this is?",1385051464,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-wjmyqwnbfehyswxiilbk,task_subcomment,NA
+Provide dialog to enter and edit templates,"It would be very nice if WikiEditor had a dialog to work with templates the way VisualEditor has. There is also a user script: [[User:קיפודנחש/TemplateParamWizard]], but IIRC this script doesn't use the informations provided by TemplateData, but uses its own format.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1384851900,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-d4viyvnin3zjuou7itc4,task_description,resolved
+Provide dialog to enter and edit templates,"With the beta of #mediawiki-extensions-templatewizard having been deployed {T202545}, I'm calling this resolved. Any related issues should be filed against that component.",1542127013,PHID-USER-wrimmmr5w2zt7nk2t753,False,PHID-TASK-d4viyvnin3zjuou7itc4,task_subcomment,NA
+Provide dialog to enter and edit templates,">>! In T59232#610546, @Aklapper wrote:
+> Michael: How is/was this request different from the (unmaintained) template editor which was just removed from WikiEditor recently? https://gerrit.wikimedia.org/r/#/c/123647/
+
+The difference is, that it actually should work ;-) This wasn't removed because nobody wants such a feature, but because that module didn't do anything sensible.",1425984217,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-d4viyvnin3zjuou7itc4,task_subcomment,NA
+Provide dialog to enter and edit templates,Michael: How is/was this request different from the (unmaintained) template editor which was just removed from WikiEditor recently? https://gerrit.wikimedia.org/r/#/c/123647/,1396879957,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-d4viyvnin3zjuou7itc4,task_subcomment,NA
+VisualEditor: do not remove line break before first category when a user deletes {{DEFAULTSORT}},"There should be a line break (ENTER) between ""{{Álgebra}}"" and ""[[Categoria:Estruturas algébricas]]"" on these edits:
+https://pt.wikipedia.org/wiki/Anel_%28matem%C3%A1tica%29?diff=37240720
+https://pt.wikipedia.org/wiki/Corpo_%28matem%C3%A1tica%29?diff=37240730
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1383471540,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-6bdm7pcljc4dgt4wt7gc,task_description,open
+VisualEditor: do not remove line break before first category when a user deletes {{DEFAULTSORT}},"I just [[https://pt.wikipedia.org/w/index.php?title=Usu%C3%A1rio%28a%29%3ANeil_P._Quinn-WMF%2FTestcase%2FT58530&diff=41959157&oldid=41959144|tested it]], and this issue still exists.",1429548535,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-6bdm7pcljc4dgt4wt7gc,task_subcomment,NA
+VisualEditor: do not remove line break before first category when a user deletes {{DEFAULTSORT}},This issue [[https://pt.wikipedia.org/w/index.php?title=Usu%C3%A1rio%28a%29%3ANeil_P._Quinn-WMF%2FTestcase%2FT58530&diff=41959157&oldid=41959144|still exists]].,1429548497,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-6bdm7pcljc4dgt4wt7gc,task_subcomment,NA
+VisualEditor inspector for SyntaxHighlight is too tiny with no resize option,"screenshot
+
+While we can't yet just click into a <source> SyntaxHighlight extension chunk and edit it, I notice we can now click a ""<>"" button that opens a plaintext editor for the contents. Awesome!
+
+Unfortunately the popup box for this seems really small, and there doesn't appear to be any way to resize it (no resize handles or zoom button that I can find).
+
+Especially for editing source code blocks, being able to bump the size waaay up would be very helpful.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal
+**URL**: https://www.mediawiki.org/wiki/Manual:CORS?veaction=edit
+
+**Attached**: {F12119}",1382271000,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-7kzo6bgqrlkpwpxqbvsn,task_description,resolved
+VisualEditor inspector for SyntaxHighlight is too tiny with no resize option,"Change 247567 merged by jenkins-bot:
+Use dialog for editing block level syntax highlights
+
+[[https://gerrit.wikimedia.org/r/247567]]",1445528831,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7kzo6bgqrlkpwpxqbvsn,task_subcomment,NA
+VisualEditor inspector for SyntaxHighlight is too tiny with no resize option,"Change 247567 had a related patch set uploaded (by Esanders):
+Use dialog for editing block level syntax highlights
+
+[[https://gerrit.wikimedia.org/r/247567]]
+",1445350935,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-7kzo6bgqrlkpwpxqbvsn,task_subcomment,NA
+VisualEditor inspector for SyntaxHighlight is too tiny with no resize option,"That inspector shown in that screenshot is not one from the SyntaxHighlight extension. Rather, it's the default dialog VisualEditor provides to allow editing of unknown MediaWiki tags (e.g. ones not registered elsewhere with a dedicated interface for known attributes and validating of values).
+
+The SyntaxHighlight dialog or VisualEditor was merged only a few days ago:
+{T45126}
+
+It'll be deployed in wmf12 next week. Here's a screenshot from beta:
+
+{F183659}
+http://en.wikipedia.beta.wmflabs.org/wiki/Python?veaction=edit
+
+Which.. is also not very big.  Keeping this task unresolved for now.
+
+A few ideas:
+* Button to turn dialog into ""full page"" size.
+* By default, inner height unrestricted (however large the textarea is, autogrowing when changing it). With outer height providing scroll overflow based on browser window size.
+* Or; default to OOjs UI ""large"" or ""larger"" size at least.",1435307612,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-7kzo6bgqrlkpwpxqbvsn,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"On the English Wikipedia, I'd like to be able to use the VisualEditor on any namespace, but especially the project namespace.
+
+Given that VisualEditor is opt-in and already regularly breaks pages anyway, I don't think lifting the arbitrary namespace restriction on wikis where VisualEditor is opt-in (such as the English Wikipedia) will be problematic.
+
+Submitted for consideration. CC'ing James and Roan.
+
+--------------------------
+
+See also: {T57968}",1381937700,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hmwjwgzjxsoee75bqkok,task_description,duplicate
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"(In reply to comment #3)
+> (In reply to comment #1)
+> > If VE is OK to edit a namespace (and, in general, it's probably fine for
+> > any that aren't signed, Template: or MediaWiki:) then we should just make
+> > that config change and not vary it per wiki. Make a distinct bug for that?
+> 
+> I vaguely understand what you're saying here, but I think it would be best if
+> you filed the bug.
+
+Sure - bug 55968 filed.",1382372495,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"This is not a site request but a VisualEditor enhancement.
+
+The check in [1] needs to be moved somewhere else (one of the hooks in VisualEditor.hooks.php?).
+
+[1] https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor.git/a531b396981042da09280df2ea5dceb6be3fa106/ApiVisualEditor.php#L218",1382168909,PHID-USER-sx63fwaih5kjt7bz4u6z,False,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"(In reply to comment #1)
+> If VE is OK to edit a namespace (and, in general, it's probably fine for
+> any that aren't signed, Template: or MediaWiki:) then we should just make
+> that config change and not vary it per wiki. Make a distinct bug for that?
+
+I vaguely understand what you're saying here, but I think it would be best if you filed the bug.",1381982024,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"Let's take a step back here. Here's my use-case: I don't edit articles very much, but I still want to be able to test VisualEditor when I do occasionally edit non-articles. Today I came across [[Wikipedia:Meetup/DC]] and wanted to use VisualEditor to edit it. I wasn't able to. :-(
+
+You bring up a good point about user signatures, but many project-space pages are informational in nature, not discussion-oriented.
+
+Perhaps there's some way to programmatically detect whether a page is a discussion page?
+
+Or perhaps we can remove the hard restriction on VisualEditor editing? For example, if I try to navigate to <https://en.wikipedia.org/w/index.php?title=Wikipedia:Meetup/DC&veaction=edit> directly, VisualEditor won't load. We could remove the hard restriction and leave in place the soft restriction (not exposing the user interface tab). This would allow people like me to just hack in an extra tab. Dirty, but probably fine for now.",1381981978,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions,"Three things:
+
+1 - If VE is OK to edit a namespace (and, in general, it's probably fine for any
+    that aren't signed, Template: or MediaWiki:) then we should just make that
+    config change and not vary it per wiki. Make a distinct bug for that?
+
+2 - Project: is frequently signed, especially on enwiki, so I think giving a VE
+    editor in this context would be confusing and actively wrong. There is no VE
+    tool for signing comments, nor for creating the definition lists which are
+    (ab)used so very widely for MediaWiki discussions right now. The intent has
+    always been that signed content would be covered by Flow, and I think trying
+    to build tools now for a few months' usage would be a diversion from the main
+    task of improving VisualEditor.
+
+3 - I think that this would end up being a rather broken user experience when a
+    wiki switched from opt-in to opt-out, and all the pages that you used to be
+    able to edit with VE suddenly vanish in a cloud of WT-only smoke, without any
+    explanation or obvious cause.
+
+Consequently, minded to WONTFIX, but am open to suggestions",1381939682,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-hmwjwgzjxsoee75bqkok,task_subcomment,NA
+Flow: VE takes significant time to manifest,"We have been encountering a number of performance issues and race conditions with VE and Chrome in recent times, this is probably one more of those. 
+
+* In a fresh instance of Chrome 30 or Chrome 29, as a logged in user, visit https://en.wikipedia.beta.wmflabs.org/wiki/Special:Flow/Flow_QA
+
+* Enter a Message topic
+
+The VE controls and CE field take significant time to appear while the user sees a spinner.  For an example causing a failure in a browser test, see https://wmf.ci.cloudbees.com/job/Flow-en.wikipedia.beta.wmflabs.org-linux-chrome/12/testReport/(root)/Create%20new%20topic%20logged%20in/Add_new_Flow_topic/ .  Note the test times out with the spinner still visible after 5 seconds. 
+
+This is not seen in Firefox
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1381877940,PHID-USER-kqibbfgfpgocyzwe32lv,False,PHID-TASK-mef22t3vme6fkzexu6mp,task_description,invalid
+Flow: VE takes significant time to manifest,"We removed the VE option in Flow long, long ago :) 
+
+People should feel free to reopen this when we actually have the VE in Flow option up and running again.",1390958494,PHID-USER-yu5wnmvkjecufsjgh2fa,False,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,"I've tested it on my own box. It's this call that takes the long time:
+
+'http://localhost/mw-dev/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cdata%2Cicons-vector%2Cstandalone%7Cext.visualEditor.viewPageTarget.icons-vector%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20131106T030133Z&*'
+
+This typically returns in ~6 seconds. However, I've found that sometimes it works in ~200ms. When that happens, VE loads quickly on my local box.
+
+So it does indeed seem to be caching, of a particular ResourceLoader resource.",1383707587,PHID-USER-cgfiqjzsqzd7ulp7eyr7,False,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,Aha; thanks for letting me know :).,1382990815,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,"(""RESOLVED LATER"" was replaced with the ""lowest"" priority. Might want to use that instead.)",1382990684,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,This is likely a problem with the Labs instance; no varnish == no caching of VE elements :/. Unfortunately that means it's something we're probably not going to be able to track or test properly until we go into deployment on production. Closing as WONTFIX since LATER is no longer available.,1382990575,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+Flow: VE takes significant time to manifest,"The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/324, but people from the community are welcome to contribute here and in Gerrit.",1382030051,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-mef22t3vme6fkzexu6mp,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"**Author:** `swalling`
+
+**Description:**
+The introductory dialog for VE is supposed to be seen only once per person. However, it seems that the way it is hidden for users is dependent on session information, probably a cookie? 
+
+This means that every time I clear my cookies, open an incognito browser window, use a new browser, or use a new device, I get the intro again. Even if I'm using the same account. This stinks. 
+
+In GuidedTours we solve this problem (not showing users repeated intro tours across devices/sessions) by setting a hidden preference when someone completes a tour. I'd like to suggest we do that for the VE intro, unless someone can think of a more elegant way to avoid this annoying behavior.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1381393200,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-un4pzbob5j2l45f2pfnt,task_description,resolved
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"(In reply to Tom Hart from comment #5)
+> Where is this preference to turn of the Welcome overlay located? I am always
+> getting the ""Welcome..."" dialog when I click Edit, while logged in on the
+> same machine, same session... I'm using Chrome Version 35.0.1916.114 on
+> Mavericks 10.9.2.
+
+It's hidden, only the server interacts with it. This is bug 65821",1401217681,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"**tahart** wrote:
+
+Where is this preference to turn of the Welcome overlay located? I am always getting the ""Welcome..."" dialog when I click Edit, while logged in on the same machine, same session... I'm using Chrome Version 35.0.1916.114 on Mavericks 10.9.2.",1400877136,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"Change 125914 merged by jenkins-bot:
+mw.ViewPageTarget: Hide the welcome dialog via a preference if possible
+
+https://gerrit.wikimedia.org/r/125914",1399723586,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"Change 125914 had a related patch set uploaded by Jforrester:
+Hide the beta welcome via a preference, not a cookie, for logged in users
+
+https://gerrit.wikimedia.org/r/125914",1397518857,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"**swalling** wrote:
+
+(In reply to comment #1)
+> Yay more preferences bloat (and a slower page load). :-(
+> 
+> Given that the welcome dialog is temporary, I was tempted to WONTFIX this,
+> but
+> if someone wants to code it up we might consider accepting it.
+
+In this case, the preference is hidden so while it might be bloat, it's not the kind that clogs up Special:Preferences. I'm not sure what's worse: presenting an unnecessary modal repeatedly or slowing page load time. Have we actually quantified how much each preference slows page load?",1390848538,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome,"Yay more preferences bloat (and a slower page load). :-(
+
+Given that the welcome dialog is temporary, I was tempted to WONTFIX this, but if someone wants to code it up we might consider accepting it.",1390818198,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-un4pzbob5j2l45f2pfnt,task_subcomment,NA
+"""Publish and submit"" button shouldn't be available because it shouldn't be used","Per discussion with Krinkle on IRC, the ""publish and submit"" button in Gerrit should not be used.
+
+If this is the case, it should not be present.
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: normal",1380910920,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-gys4tf753s77f4zdjpsb,task_description,resolved
+"""Publish and submit"" button shouldn't be available because it shouldn't be used","Interesting, ""Publish and Submit"" is gone via upgrading. You can't submit from the review box anymore.",1469470370,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-gys4tf753s77f4zdjpsb,task_subcomment,NA
+"""Publish and submit"" button shouldn't be available because it shouldn't be used",Actually sometimes you are required to force merged.,1468340685,PHID-USER-bxp7xrbobtrp5o3q3swv,False,PHID-TASK-gys4tf753s77f4zdjpsb,task_subcomment,NA
+"""Publish and submit"" button shouldn't be available because it shouldn't be used","* Our Gerrit config requires V+2 to be present. We can change Jenkins to do V+1 on the patch test so that it doens't clash with the V+2 vote for the submit test, that resolves the ambiguity and will make the submit button not appear before it should.
+
+* Alternatively, like for various repositories already (including VisualEditor) we could remove the ""Submit"" right from regular users (e.g. only for JenkinsBot and l10nbot, and some ops maybe).",1380911098,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-gys4tf753s77f4zdjpsb,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","(Where the word is the actual working part of the element).
+Probably not a real bug, since it is triggered by a user mistake (who should remove the brackets), but since it's easily reproduceable, here are the steps:
+take any <nowiki>[[link]]</nowiki> created like this (by ignoring the markup warning).
+VEdit the page and use the linking tool on the word inside the brackets.
+Save, you now have [[[[link]]]], and of course the nowiki tags are gone.
+
+https://www.mediawiki.org/w/index.php?title=User:Elitre_(WMF)/SandboxVE&diff=prev&oldid=794483
+
+https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=794473&oldid=794472
+
+Just interested in understanding whether VE wants or can do something about it.
+
+(Note that it is absolutely possible to get the same result with the traditional editor as well, https://sl.wikipedia.org/w/index.php?title=Klerofa%C5%A1izem&diff=next&oldid=4101482 ).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1380727020,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_description,resolved
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","Change 104695 merged by jenkins-bot:
+(Bug 54877) Tokenize [[[[Foo]]]] correctly
+
+https://gerrit.wikimedia.org/r/104695",1388700351,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","Change 104695 had a related patch set uploaded by Subramanya Sastry:
+WIP (Bug 54877) Tokenize [[[[Foo]]]] correctly
+
+https://gerrit.wikimedia.org/r/104695",1388448649,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","Re-re-phrasing the title (and yes, this appears to be a Parsoid bug, but a very low priority one).",1380845739,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","Rephrasing bug. A user would not have a goal to generate 4 brackets in wikitext, but the use case of typing (or editing existing pages that do have) [[ around a link, that is genuine content that VisualEditor should be able to create and edit.",1380728622,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+"Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=""Foo"">Foo</a>]]","This is probably a bug in Parsoid, not VisualEditor.
+
+Given a page containing:
+
+[[[[Sandbox]]]]
+
+Which contains no <nowiki>, this is parsed as [[<a href=Sandbox>Sandbox</a>]] by the PHP parser and renders accordingly.
+
+When editing that page in VisualEditor, the initial rendering is wrong (it renders as a text node ""[[[[Sandbox]]]]"", no anchor link).
+
+If I add text to that line or change the word to something else, the serialisation from Parsoid is still the same (no <nowiki> is inserted, so Parsoid is unaware of it being a link both in parsing and serialising).
+
+
+Given a page containing:
+
+<nowiki>[[[[Sandbox]]]]</nowiki>
+
+When editing that in VisualEditor, the initial rendering is correct (1 text node containing ""[[[[Sandbox]]]]"").
+
+If I add text to that line or change the word to something else, the serialisation from Parsoid is no longer the same. It dropped the <nowiki>, thus effectively (according to the PHP parser) turning it into a link after saving.",1380728435,PHID-USER-sai77mtxmpqnm6pycyvz,True,PHID-TASK-7ylkp2sxhpczkkcpbdi6,task_subcomment,NA
+[DO NOT USE] VisualEditor: Tracking bugs for VisualEditor (tracking) [superseded by #VisualEditor],"[Unused; we don't do tracking bugs, post-Phabricator transition.]
+
+A central place for people to keep track of tracking bugs for VisualEditor. (Yay for bug meta-ness.)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1379656500,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ncpmmwig7janid6ikysj,task_description,invalid
+[DO NOT USE] VisualEditor: Tracking bugs for VisualEditor (tracking) [superseded by #VisualEditor],[adding the #tracking project to tasks blocking (now deprecated) T4007 as part of T93366],1440343622,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-ncpmmwig7janid6ikysj,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Missing scan and edit toolbar
+
+I am posting three separate bugs and mentioning this in this first report because they are somewhat related.
+
+The user defined edit toolbar, defined in my very simple
+https://en.wikisource.org/wiki/User:Ineuw/common.js stopped functioning in this latest version of the mw software. In versions previous, it worked reliably and always, permitting me greatly increased productivity. The toolbar does show up intermittently and occasionally. 
+
+Regardless of the toolbutton definition syntax used, the same intermittent functioning is the result. The syntax is either the current definition one, or an older one:
+
+mw.toolbar.addButton(
+        '',
+        ' Æ ',
+        'Æ',
+        '',
+        '',
+        ''
+);
+
+I also used the definitions without image buttons, thinking that this may be the cause, but it doesn't make a difference.
+
+The problem is also not browser related. I tried other browsers and OS's as well:
+
+Firefox in Windows, Xubuntu, and Apple OSX.
+Safari in Windows and Apple OSX.
+Google Chrome in Windows and Linux (Xubuntu).
+but the intermittent behaviour is the same. . . . . 
+
+Finally, this is also true on the Commons and Wikipedia, where it's less critical because I am not so active on those wikis.
+
+Please see attached image.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+
+**Attached**: {F11589}",1379578860,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_description,declined
+Customized legacy edit toolbar does not always load correctly,"I ask that this bug be closed, since I accepted the demise of the old wiki toolbar.",1379736095,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"(In reply to comment #8)
+> I also got the same Firefox (23.0.1) error as Andre Klapper. If this seems to
+> be the cause, can't it be corrected?
+
+It might either be an issue in your code in common.js, or some changes in MediaWiki. Apart from Alex' cleanup which got merged at the beginning of September I cannot see any changes in
+https://git.wikimedia.org/history/mediawiki%2Fcore.git/HEAD/resources%2Fmediawiki.action%2Fmediawiki.action.edit.js
+
+> Finally, this is a very big disappointment because the replacement option is
+> very awkward. Among other things, it takes up (and unnecessarily) a lot of
+> screen real estate and I work on a 22"" screen.
+
+I don't see that big difference in size. Not sure if we refer to the same things?
+The legacy toolbar had enough issues (e.g. it was never meant to be expanded so inserting required exposing and dealing with implementation details) so it got replaced by the current toolbar.",1379680607,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"I am not the only one who is using the toolbar at Wikisource. While other users have occasional issues, theirs seem to work on most cases. 
+
+I also got the same Firefox (23.0.1) error as Andre Klapper. If this seems to be the cause, can't it be corrected?
+
+Finally, this is a very big disappointment because the replacement option is very awkward. Among other things, it takes up (and unnecessarily) a lot of screen real estate and I work on a 22"" screen. Krinkle's opinion is akin to taking away a mechanic's trusted tools because he doesn't personally favor them. He should try his hand at some proofreading for a day or two.",1379623232,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"To quote Krinkle: 
+""The classic edit toolbar has long been deprecated. The default was replaced
+with WikiEditor on Wikimedia in a 2010 deployment"", plus VisualEditor is also around the corner.
+Setting lowest priority, might be even a WONTFIX.",1379601766,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Created attachment 13327
+Character selection moved too low in new mw software version
+
+To the attention of Andre Klapper
+
+This is the missing image of the drop down character set selector
+
+**Attached**: {F11593}",1379590215,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Created attachment 13325
+old style toolbar coding
+
+This text contains the legacy toolbar layout, without captions by the elements, no images, and notice the function syntax difference. It doesn't matter which I use, the behaviour is identical.
+
+mw.toolbar.addButton(
+
+and NOT 
+
+mw.toolbar.addButtons(
+
+**Attached**: {F11592}",1379589793,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Created attachment 13324
+Legacy edit toolbar displayed.
+
+**Attached**: {F11591}",1379589573,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Hi. I am sorry to confuse you. The new edit toolbar was activated so that I could take a proper snapshot and I forgot to turn it off. Otherwise, it's not usable for me at the moment.
+
+Wikisource users, who use edit toolbar buttons, use the ""legacy"" old style because it's more versatile. For my main project work of Popular Science Monthly, I only need the 12-14 extended ANSI to accommodate French and German and occasionally Greek. 
+
+I am also working on Hebrew/Arabic texts, and not being able to access the dropdown box of character selections, this forced me to try using the ""advanced"" WikiEditor toolbar in which my language setting places things in reverse order.
+
+I am attaching what should be the correct display of the legacy toolbar when it works.",1379589495,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Hi ineuw,
+
+your screenshot looks like the old toolbar to me, instead of the WikiEditor toolbar. Is that intended or part of the problem?
+
+The WikiEditor toolbar should look like your screenshot in https://bugzilla.wikimedia.org/attachment.cgi?id=13323
+
+I went to 
+https://en.wikisource.org/w/index.php?title=Page:Popular_Science_Monthly_Volume_63.djvu/155&action=edit
+to reproduce the problem (Firefox 23.0.1) and switched to horizontal layout.
+
+I also copied your ""common.js"" file to my user account (the file basically just has a number of ""mw.toolbar.addButtons"" calls).
+
+The scanned image still loads for me, and I get the correct WikiEditor toolbar, but in Firefox' Error Console I get:
+
+Timestamp: 09/19/2013 11:52:12 AM
+Error: TypeError: mw.toolbar is undefined
+Source File: https://bits.wikimedia.org/en.wikisource.org/load.php?debug=false&lang=en&modules=user&only=scripts&skin=vector&user=AKlapper+%28WMF%29&version=20130919T095201Z&*
+Line: 1
+
+I have bug 47872 in mind.",1379585655,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+Customized legacy edit toolbar does not always load correctly,"Created attachment 13321
+edit toolbar is showing occasionally
+
+**Attached**: {F11590}",1379578978,PHID-USER-kdpydfvhr2l2qcrbvvz7,False,PHID-TASK-r3avdlac5as6usqbtpvz,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"The link input widget should have separate fields for the link target and the displayed text.
+
+From various comments at T50789
+
+> There are essentially two ways to create a link:
+> 
+> […]
+> 
+> #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.
+> 
+> […]
+> 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 [T54462]
+> 
+> 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.
+
+---
+>>! In T50789#510194, @Thryduulf wrote:
+> An 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. 
+>
+> See also T53438
+
+---
+>>! In T50789#510207, @Thryduulf wrote:
+> 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]].
+
+--------------------------
+**See Also**: T52945",1378772640,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_description,resolved
+VisualEditor: Link input widget should have separate inputs for target and display text,"Change 303956 **merged** by jenkins-bot:
+[VisualEditor/VisualEditor@master] LinkAnnotationInspector: add a ""label"" field on mobile
+
+[[https://gerrit.wikimedia.org/r/303956]]",1566512170,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Change 303956 restored by Esanders:
+LinkAnnotationInspector: add a ""label"" field
+
+[[https://gerrit.wikimedia.org/r/303956]]",1561206667,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"The solution in T124305#4321883, which is implemented and will be live in two weeks, should effectively resolve this task.",1530193718,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Change 303956 abandoned by Jforrester:
+LinkAnnotationInspector: add a ""label"" field
+
+Reason:
+It was decided to go with Iad48fb55 instead.
+
+[[https://gerrit.wikimedia.org/r/303956]]",1530047719,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,Looks like we're going with the solution Pau proposed above – please see T124305 for details.,1529601576,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,FYI: Issues which are caused by the lack of a clear separate visualization of both link destination and link title on the German-language Wikipedia can be seen [[ https://tools.wmflabs.org/persondata/ve.php | with this tool]].,1522158502,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"@Pginer-WMF That looks like it would resolve at least most of the issues I have with the current set-up, and as long as it is obvious that truncation has happened when it has then there are no immediate problems with it I can see. ",1518921766,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"One possible approach to explore would be to expose a shortcut for editing the label that results in selecting the link label in place. In this way, there is no duplication of the places used to edit the label (avoiding the issues described above) while making the entry point for editing the label more explicit. We need to be cautious for the later not to cause issues, and test with users accordingly if we decide to explore this direction anytime.
+
+The idea is illustrated below:
+
+{F13736398, size=full}
+- A separate section of the inspector is added about the label. The current label can be cropped if too long, it is there just for reference.
+- Clicking on the section hides the inspector and selects the text label inside the link for the user to type the new one.  Temporary time-based tooltip can appear to indicate to ""type the new label"" if needed.",1518605752,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'm really not at all sure that the actual benefits of this task to the people who are at the sharp end are actually understood by the developers. There is a reason that this has been resurrected at least twice, has at least four duplicate tasks, and the requests for it continue more than 5 years after it was first requested. Indeed this is one of just two tasks (T51969 is the other, and this is far more important than that) that are standing between where we are now and VE being intuitively easy for both new and power editors to use simply and reliably for non-specialist editing in almost all reasonable circumstances without making unforced errors.
+
+Links are utterly fundamental to the way wikis work and VE is intended to be used by inexperienced users, so it is completely and utterly mind boggling to be told that something that forces unintuitive workarounds to achieve something that should be absolutely basic skill level 0.2 (at most) will not be fixed. ",1502273460,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"There is an insane amount of complexity with links in wikis due to the nature of how much they're used. Any change in this area would divert a lot of product and design time away from other projects, thus making changes here incredibly costly. Given the limited benefit of doing work here compared to other projects, this task is not going to be worked on any time soon. That is, after all, why James declined it twice. The debate here is interesting, but it is mostly academic at this point.",1502126282,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"There is an insane amount of complexity with links in wikis due to the nature of how much they're used. Any change in this area divert a lot of product and design time away from other projects, thus making changes here incredibly costly. Given the limited benefit of assigning work here compared to other projects, this task is not going to be worked on any time soon. That is, after all, why James declined it twice. The debate here is interesting, but it is mostly academic at this point.",1502126250,PHID-USER-kve2ug5yc3dp6ighnmqk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3505027, @Whatamidoing-WMF wrote:
+>> if a link targets a page that matches exactly the link label, and a user changes that label to the name of a different page, the software can suggest the target also to be updated.
+> 
+> That would be very annoying every time someone needs to change the ending of a link.  `[[Example]]s` is a good link.  `[[Example|Examples]]` is bearable.  Having Clippy ask you if you want to change the link from ``[[Example]]` to `[[Examples]]` every time you try to fix the grammar in a sentence is not bearable.
+
+I think that whether the approach is annoying or not would depend on its execution, and how prominently the suggestion is presented. Clippy represents the annoying extreme of suggestion mechanisms: causing distraction as an animated character, and providing unreasonable suggestions (""what made Clippy think this could be a letter?""). In this case, the approach should be much more subtle (no animated characters) and the connection on why a suggestion is provided is quite clear (so even if it is not what you want, there is not a big surprise that the suggestion was provided). More like [[ https://www.youtube.com/watch?v=qcm0rG8EKXI | Google instant ]] than Clippy.
+
+In that particular example, given that ""Examples"" is a redirect to ""Example"", we can probably show no suggestion at all.",1502096404,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> if a link targets a page that matches exactly the link label, and a user changes that label to the name of a different page, the software can suggest the target also to be updated.
+
+That would be very annoying every time someone needs to change the ending of a link.  `[[Example]]s` is a good link.  `[[Example|Examples]]` is bearable.  Having Clippy ask you if you want to change the link from `[[Example]]` to `[[Examples]]` every time you try to fix the grammar in a sentence is not bearable.",1502123192,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> if a link targets a page that matches exactly the link label, and a user changes that label to the name of a different page, the software can suggest the target also to be updated.
+
+That would be very annoying every time someone needs to change the ending of a link.  `[[Example]]s` is a good link.  `[[Example|Examples]]` is bearable.  Having Clippy ask you if you want to change the link from ``[[Example]]` to `[[Examples]]` every time you try to fix the grammar in a sentence is not bearable.",1502077881,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3500032, @Thryduulf wrote:
+>>>! In T55973#3491393, @ssastry wrote:
+>> When you want to change the label, can't you just change the label text without opening the link editor? 
+> There is no way for the software to know which you intend, and no way for the naive user to know which has actually happened without actively opening the link editor, but it is likely that the assumption will be that both were changed (per @Whatamidoing-WMF).
+
+There is no way for the software to know, but the software could pay attention to some clues. As I mentioned in T55973#2792012, if a link targets a page that matches exactly the link label, and a user changes that label to the name of a different page, the software can suggest the target also to be updated. That would give visibility to the user on the mismatch between label and target, and let the user to update the target in one click if needed as some word processors do with spellcheckers.",1501835793,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3491393, @ssastry wrote:
+> When you want to change the label, can't you just change the label text without opening the link editor? 
+The problem is that when you do that you could be intending to change the label without the link or you could be intending to change both label and link. There is no way for the software to know which you intend, and no way for the naive user to know which has actually happened without actively opening the link editor, but it is likely that the assumption will be that both were changed (per @Whatamidoing-WMF). Remember that VE is focused towards inexperienced and less-computer-literate users rather than power users, so there will be a very high proportion of users who do not know that you need to actively check what VE is doing. 
+
+Related to this, some way of identifying in the VE editing surface whether a link is piped or not would be useful in many different scenarios. I've only just thought of this but I've run out of time to investigate whether there is an existing task for this or not, so I'll pop it on VE/F and return to it this evening.
+",1501835075,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3491393, @ssastry wrote:
+> ... that hack is probably unpleasant, but at last for simple label text edit scenarios, it should work just fine?
+
+It works okay, assuming that you actually know that you have to follow all of those steps.  However, I think that we've proven that this is an invalid assumption in at least a substantial fraction of cases.  We have thousands of editors who are accustomed to changing a link such as `[[2016]]` to `[[2017]]` by only changing the visible number.  When you do that in VisualEditor, you end up with `[[2016|2017]]`.
+",1501630681,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#3224611, @Thryduulf wrote:
+> Well that news is a big disaapointment as the inability to quickly, easily, reliably and unambiguously change the destination the destination and/or description of a link is the biggest single impediment to Visual Editor.
+> 
+> When changing a link you could want to do one of three things:
+> 1. Change the label
+> 2. Change the target
+> 3. Chang both.
+> 
+> The only way to be sure that the change you want to make is the one being made is to:
+> 1. delete the current link, making sure to note the exact title and capitalisation of any section links
+> 2. type the label
+> 3. select the label
+> 4. open the link dialog
+> 5. enter the link, appending section links if necessary
+> 6. close the link dialog.
+
+When you want to change the label, can't you just change the label text without opening the link editor? But yes, in certain label-edit scenarios, one hack you have to rely on is to make sure there is at least one character left behind with the link and delete that character last ... that hack is probably unpleasant, but at last for simple label text edit scenarios, it should work just fine?",1501628448,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Well that news is a big disaapointment as the inability to quickly, easily, reliably and unambiguously change the destination the destination and/or description of a link is the biggest single impediment to Visual Editor.
+
+When changing a link you could want to do one of three things:
+1. Change the label
+2. Change the target
+3. Chang both.
+
+The only way to be sure that the change you want to make is the one being made is to:
+1. delete the current link, making sure to note the exact title and capitalisation of any section links
+2. type the label
+3. select the label
+4. open the link dialog
+5. enter the link, appending section links if necessary
+6. close the link dialog.
+
+In Google Docs you need to.
+1. select the link
+2. open the link dialog
+3. change what needs to  be changed
+4. close the link dialog
+
+Google Docs users, to my knowledge, don't find this unnecessarily heavyweight but rather simple and reliable.",1493599292,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"For clarity, this task isn't likely to have work on it soon.
+
+In general, this goes strongly against the design philosophy of the tools, making the process of adding links much ""heavier"" and context-switching. Re-validating the research results would take a lot of time and effort. In practice users don't have as many problems with this area as with others that are higher importance.",1490394770,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Another problem to take into consideration are disambiguation pages. Example:
+1. I add a link to https://en.wikipedia.org/wiki/John_Quested_(producer)
+2. I then change the label (which has automatically been set to ""John Quested (producer)"") to just ""John Quested"".
+In this case I do not want any automatism to change the link, and actually not even a suggestion to do so.
+
+In this case this can easily be detected, as https://en.wikipedia.org/wiki/John_Quested is marked as disambiguation page. But doing the same steps with https://en.wikipedia.org/wiki/Albert_Einstein_(album) should work, too, without changing the link accidentally to https://en.wikipedia.org/wiki/Albert_Einstein, even though that page isn't a disambiguation.",1479205506,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2792226, @matmarex wrote:
+> Another idea (strawman): If a wikilink's target is identical to label, we could just synchronize the target with the label when the label is changed. In both the link context and the link inspector, there would be a ""lock/unlock"" button to toggle this behaviour for the currently focused link.
+
+Thanks for the proposal, @matmarex. As pointed out above, the difference is about how much automatic we need the process to be.
+
+Changing the target automatically solves the problem without requiring the users to notice what is going on, which works rally well when it does the right thing. However it creates a stronger inconsistency of expectations when editing a link and has a higher cost for false positives:
+- Inconsistency of expectations. Some links will change their target and others won't. Changing ""lemon"" to ""orange"" will change the target, but changing ""lemons"" to ""oranges"" won't. Conversely, with the proposed approach editing the document will change always the label for all kinds of links, but it will provide a suggestion to change the target too for some of them.
+- Cost for false positives. The Tokyo article indicates that it is the ""capital"" (linking to [[ https://en.wikipedia.org/wiki/Capital_of_Japan | ""Capital of Japan"" ]], not to [[ https://en.wikipedia.org/wiki/Capital | ""Capital"" ]]. The user can add a link to ""Capital of Japan"", change it to just say ""capital"" and either miss that it now points to a different article or get annoyed by having to recreate the link again on an autocorrect-like situation.
+
+
+>>! In T55973#2792689, @DLynch wrote:
+> * It's hard to change the link text completely. Selecting the entire thing by dragging is prone to accidentally selecting outside the link annotation and thus un-linking it when you start typing. Common case: people who paste in a URL letting it auto-link, and then want to add a descriptive label.
+
+This is an interesting case too, thanks for pointing to this, @DLynch. I wonder if we could facilitate things by selecting the whole label when the link is selected/added (similar to what ""add label"" does for quick links). This can be applied to either to (a) links with a URL as label, or (b) links that got their label automatically and have not been edited before.
+It is hard to anticipate how that may interfere with all the other editing processes, but it may be worth prototyping an example to check how it feels in practice.",1479145858,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> This issue seems to happen when editing a link that uses the page title as label. This may bring expectations of such information to remain in sync when changing the link (or even not being aware of the target potentially being different from the textual representation).
+
+I do think that's only half of the issue, mind you. There's:
+
+* It's easy to let the link text and URL get out of sync, if they were initially the same. This will show up with internal wikilinks, and URLs which are shown in full.
+* It's hard to change the link text completely. Selecting the entire thing by dragging is prone to accidentally selecting outside the link annotation and thus un-linking it when you start typing. Common case: people who paste in a URL letting it auto-link, and then want to add a descriptive label.
+
+Your suggestion helps with the former, but not the latter. I grant that this is entirely anecdotal, but I started working on this task because the latter issue was bugging me in-practice while I used VE (whereas the former hadn't actually come up for me) so it's the one I have more personal connection to. :D
+
+> Is that like T56947?
+Sort of. T56947 proposes basically exactly what @Pginer-WMF suggested -- a ""you might want to update this"" popup -- whereas @matmarex's suggestion is a more-aggressive version of that which forces the update unless you explicitly opt out.
+
+I think it's basically the system proposed there, yeah. We don't currently have a convenient ""suggest a change"" system in context popups like this, but it's certainly addable if we want it. Making it keyboard-accessible as suggested would break the current paradigm, but it's not like context popups are //currently// keyboard-accessible anyway, so...",1479141371,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2792226, @matmarex wrote:
+> Another idea (strawman): If a wikilink's target is identical to label, we could just synchronize the target with the label when the label is changed. In both the link context and the link inspector, there would be a ""lock/unlock"" button to toggle this behavior for the currently focused link.
+> 
+> I think this would eliminate the user errors of the kind we see now. On the other hand, it would make it somewhat annoying when you actually wanted to change the label (especially when writing in languages with rich inflexion).
+
+Is that like T56947?",1479126440,PHID-USER-xfe43w2lb5gpvglf4coa,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Another idea (strawman): If a wikilink's target is identical to label, we could just synchronize the target with the label when the label is changed. In both the link context and the link inspector, there would be a ""lock/unlock"" button to toggle this behavior for the currently focused link.
+
+I think this would eliminate the user errors of the kind we see now. On the other hand, it would make it somewhat annoying when you actually wanted to change the label (especially when writing in languages with rich inflexion).",1479125778,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2789271, @matmarex wrote:
+>> As I understand it, the main problem occurs when adding a link without any previous text selection.
+> 
+> I think the biggest problem here is in editing links.
+
+Thanks for the illustrative examples, @matmarex.
+This issue seems to happen when editing a link that uses the page title as label. This may bring expectations of such information to remain in sync when changing the link (or even not being aware of the target potentially being different from the textual representation).
+
+I think those cases (where the label and page name matches) could be detected by VE and provide some support to quickly solve the out-of-sync status. For example, I illustrated below how we can surface that once the user changed the label, the link is pointing to the old page but that can be changed to point to a page that matches the new label. Clicking on the suggestion (or using keyboard down arrow to select it + enter) will update the link target without writing it twice.
+
+{F4723857, size=full}
+
+
+In the example above, having separate fields for editing label and target won't be very useful since we are not accessing the editing mode where those would be shown. It can be argued that making the edit label non-editable on the editing surface could force users to access the link editing panel, but that makes other scenarios more complex (e.g., quick label corrections, or using more complex content as link labels).",1479120130,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,What matma said.,1478931953,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> As I understand it, the main problem occurs when adding a link without any previous text selection.
+
+I think the biggest problem here is in editing links.
+
+For example, a user is editing a sentence like `[[Tim Berners-Lee]] was born in [[1965]].` and wishes to correct the typo (he was actually born in 1955). Editing the visible text in VisualEditor without correcting the link target will result in `[[1965|1955]]`; editing the link target without correcting the text will result in `[[1955|1965]]`; both of these mistakes are easy to make in the current interface and difficult to spot when reviewing, if you're not looking at the wikitext source code.",1478892137,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I think it is important to separate the problem from possible solutions. As I understand it, the main problem occurs when adding a link without any previous text selection. In that context, the way to add a label has not much visibility. This generates confusion about where is the label supposed to be edited and makes it difficult workflows based on a different order than the one supported by default.
+
+Provide a separate field for the link label as suggested above, makes label editing more explicit, but it is duplicating content that is already in the document which causes some different problems.
+
+I was trying to explore a way to make the label editing more inviting right where it is going to be, without any duplication:
+
+{F4716647}
+
+When adding a link with no selection, instead of showing no content in the text, a placeholder element can be added in-place (styled similar to the link that it will become later) for the user to indicate the label, while a selector can be also available to pick the link target.
+
+The content provided by the user in one field can inform the other (e.g., if I write ""rice"" as label, the Rice article should be among the suggestions when I click on the page search).
+
+This is just a rough idea, but I'm curious to hear whether a solution along these lines is considered to help with the issue identified, or use it to identify which parts of the problem that I may be missing.",1478889614,PHID-USER-c47vnc2yxmwfvvc4367q,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> How do you deal with something like `[[Parrot|{{lang|fr|perroquet}}]]`, where the label is built on a template?
+
+Most likely we will just not support cases where the link contains non-text through this particular interface, but they aren't that common.",1478705462,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2777160, @Quiddity wrote:
+>>>! In T55973#2775922, @Trizek-WMF wrote:
+>> How do you deal with something like `[[Parrot|{{lang|fr|perroquet}}]]`, where the label is built on a template?
+> 
+> Is that a regular pattern somewhere? I don't think I've seen it used before, and am interested to see examples.
+
+I've quick-searched on articles I've written and found that exemple [[https://fr.wikipedia.org/w/index.php?title=Mod%C3%A9lisme_ferroviaire&action=edit&section=33|here]]:  `''[[Gorre & Daphetid Railroad|{{lang|en|Gorre & Daphetid Railroad}}]]''` 
+
+I've also searched (ctrl+F) on [[https://fr.wikipedia.org/w/index.php?title=Histoire%20du%20communisme&action=edit|Histoire du communisme]], the biggest article on fr.wp, where I've found:
+* `[[groupe Barta|{{citation|groupe Barta}}]] ` or `[[De chacun selon ses moyens, à chacun selon ses besoins|{{citation|De chacun selon ses facultés, à chacun selon ses besoins}}]]`
+* `[[Kang Kek Ieu|{{citation|Douch}}]]`
+
+There is also cases like `[[1er octobre|{{1er}} octobre]]` or `[[18e congrès national du Parti communiste chinois|{{18e|congrès}} national]]`.
+
+Some cases can be rewritten for sure, but not always.",1478601347,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2775922, @Trizek-WMF wrote:
+> How do you deal with something like `[[Parrot|{{lang|fr|perroquet}}]]`, where the label is built on a template?
+
+Is that a regular pattern somewhere? I don't think I've seen it used before, and am interested to see examples.
+",1478541625,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"One reason to consider keeping the internal-labels is that they're easier to slip into the existing MW extension version of the link inspector, since that has to accommodate the wiki search results alongside the fields.",1478540932,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2769070, @Quiddity wrote:
+
+> Losing occasional text-formatting is an acceptable compromise.
+
+I've slept on that and now I agree.
+
+>>! In T55973#2773796, @Esanders wrote:
+> Inline labels:
+> 
+> {F4698802}
+> 
+> Google docs for comparison:
+> 
+> {F4698804}
+> 
+> I think focusing the link field first, and labelling it ""link"" instead of ""target"" (which is a bit technical) will help. We could also live-update the link as the text field is changed, which would avoid surprises when 'done' is clicked.
+
+I think that's the best for a link made on a raw text.
+How do you deal with something like `[[Parrot|{{lang|fr|perroquet}}]]`, where the label is built on a template?",1478518303,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Inline labels:
+
+{F4698802}
+
+Google docs for comparison:
+
+{F4698804}
+
+I think focusing the link field first, and labelling it ""link"" instead of ""target"" (which is a bit technical) will help. We could also live-update the link as the text field is changed, which would avoid surprises when 'done' is clicked.",1478360692,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"> Use a 'placeholder' and insert an invisible label somewhere for accessibility.
+Worth considering that the common-case here is (probably) editing an already-existing internal-wiki link. With a placeholder as the only distinction, that's going to look like this:
+
+{F4693560}
+
+...which is perhaps initially confusing.
+
+Then the secondary case is editing an external link, where keeping the URL field as wide as possible is preferred, because URLs can get pretty long. The advantage of the internal label there is that it really is pretty space-efficient -- no added vertical size, and it's a compact horizontal representation.",1478203630,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2763929, @matmarex wrote:
+> * Just use a FieldLayout :)
+> * Use a 'placeholder' and insert an invisible label somewhere for accessibility.
+
+
+* This would make the inspector much taller, which may or may not be acceptable.
+* When editing the link both fields will be non-empty so the placeholder will never be seen.
+
+Google Docs uses an inline label, which may severely reduce the width if we need to make room for all languages, but this should be considered too.",1478203101,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2768853, @Trizek-WMF wrote:
+> And what if we only display a read-only text for the label?
+> 
+> Label: //2013//
+> Target: 2014
+> 
+> That way, people will notice there is something wrong and will be able to correct the text afterwards, using the full potential of VE.
+
+That would leave a primary use-case as very difficult - pasting or writing a complete replacement for the link label.
+
+I.e. As an experienced wikitext editor, I'm accustomed to writing/pasting the link first, and then writing/pasting the label after a space or pipe. -- With VE, it is hard to select the entire label, in order to paste my clipboard on top, or in order to write it from scratch.
+
+I really like the design given in T55973#2761021 above.
+Losing occasional text-formatting is an acceptable compromise.",1478194854,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2768853, @Trizek-WMF wrote:
+> And what if we only display a read-only text for the label?
+> 
+> Label: //2013//
+> Target: 2014
+> 
+> That way, people will notice there is something wrong and will be able to correct the text afterwards, using the full potential of VE.
+
+That would leave a primary use-case as very difficult - pasting or writing a complete replacement for the link label.
+
+I.e. As an experienced wikitext editor, I'm accustomed to pasting the link first, and then writing the label after a space or pipe. -- With VE, it is hard to select the entire label, in order to paste my clipboard on top, or in order to write it from scratch.
+
+I really like the design given in T55973#2761021 above.
+Losing occasional text-formatting is an acceptable compromise.",1478194804,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2768853, @Trizek-WMF wrote:
+> And what if we only display a read-only text for the label?
+> 
+> Label: //2013//
+> Target: 2014
+> 
+> That way, people will notice there is something wrong and will be able to correct the text afterwards, using the full potential of VE.
+
+This is another good option (I may have suggested it in the past).
+
+ps Note that we will be able to handle the example you gave just fine because the annotation (italic) spans the whole link. A better example would be:
+
+Label: Season //2014//
+Target: Season 2014",1478193377,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"And what if we only display a read-only text for the label?
+
+Label: //2013//
+Target: 2014
+
+That way, people will notice there is something wrong and will be able to correct the text afterwards, using the full potential of VE.",1478192130,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I do agree that showing wikitext is the wrong way to go. This is a prime user-facing tool, which a majority of users are going to be interacting with regularly, not something far more power-usery like templates.
+
+If we want to preserve the rare cases of internal formatting, we should go all out and have a VE surface inside the inspector... which I think makes it far too heavy for what's normally an incredibly quick action.
+
+Technically, I suppose there's alternatives like diffing/merging the change to the label so that we keep the annotations if the section they cover wasn't touched. But that's a bunch more work on our end, and moves towards being too magic for the user to understand why the formatting sometimes stays and sometimes goes.",1478191646,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Also, as a volunteer, I don't want to hear ""quotes on the text are making italics, that's a bug"" from a newbie. That's a request for my personal comfort, Sherry ;)
+
+>>! In T55973#2768788, @Esanders wrote:
+> Showing wikitext is not the right thing to do. Links with *partial* formatting are very rare, and editing their text rarer. Even in those cases the user can just edit the text directly. If the user edits the label in this very rare case they will get immediate visual feedback of the change. Let's not make perfect the enemy of the good.
+
+Wise words!
+
+",1478190964,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Showing wikitext is not the right thing to do. Links with *partial* formatting are very rare, and editing their text rarer. Even in those cases the user can just edit the text directly. If the user edits the label in this very rare case they will get immediate visual feedback of the change. Let's not make perfect the enemy of the good.",1478190826,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Rich display would be nicer (but take up a lot of space).  OTOH, given a link such as `[[Example|the ''blue'' picture]]`, I'd rather see 
+
+```
+the ''blue'' picture
+Example
+```
+
+rather than 
+
+```
+the blue picture
+Example
+``` 
+
+– especially when the second item will silently remove the italics if I touch it.
+",1478189876,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"No wikitext displayed, please! ",1478166975,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"@DLynch, would it be easy enough to make it show wikitext rather than ""plain text"" (i.e., like the template dialog does for parameters)?  Having the internal annotations silently disappear might be annoying (for the very small percentage of links that contain internal annotations).",1478136737,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"The patch currently behaves as:
+
+* If there's any block-level content in the link (e.g. an image), it disables the label field. (Cue taken from Google Docs, which completely hides the field in this case.)
+* If there's annotations on the content (bold, italic, etc), the field is enabled, and contains the plain text version. Making a change to its contents will remove all internal annotations from the link. (i.e. if it's in a block of bold text, it'll stay bold, but if part of the inside was bold, that'll be lost)",1478105014,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'm glad this is being worked on.
+
+>>! In T55973#2761021, @DLynch wrote:
+> {F4685690}
+> 
+> (Prior to any Design feedback.)
+
+Please don't use these weird right-side labels. TextInputWidget's 'label' option should never have been created. :/
+
+Unless design folks invent something new, there are two options that would be consistent with existing interfaces:
+* Just use a FieldLayout :)
+* Use a 'placeholder' and insert an invisible label somewhere for accessibility.",1478104836,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2763892, @DLynch wrote:
+> The other options I came up with are context item:
+> {F4688837}
+> (With attendant ""we need to think up an icon that intuitively symbolizes 'select all'"" dilemma, which nobody else seems to have really cracked. My favorite, after a bunch of searching, was [Blackberry's](https://help.blackberry.com/en/blackberry-leap/10.3.1/help/hjo1405445343190_hiresdevice_en-us.png))
+> 
+> Or inspector:
+> {F4688838}
+
+I'm pretty sure that people will not edit the label with that version. Edit label is not as obvious as it is on your first proposal with two separate fields.
+
+Speaking of which, how do you deal with a label which includes some wikitext formatting, like bold or, worse, an in-line template?",1478104532,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"The other options I came up with are context item:
+{F4688837}
+(With attendant ""we need to think up an icon that intuitively symbolizes 'select all'"" dilemma, which nobody else seems to have really cracked. My favorite, after a bunch of searching, was [Blackberry's](https://help.blackberry.com/en/blackberry-leap/10.3.1/help/hjo1405445343190_hiresdevice_en-us.png))
+
+Or inspector:
+{F4688838}",1478102871,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"{F4685690}
+
+(Prior to any Design feedback.)",1478028816,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Regular users have a really understand creating a mental model of how links work, especially when the label (nearly) matches the target. Having both side by side in the edit area makes it a lot clearer what is going on. More experienced users will be able to use the edit surface as designed.",1470870679,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"To elaborate slightly, 303956,2 adds some protection in to make sure it won't replace the current label text if it hasn't been changed from its initial value, so even internal annotations will be preserved if you're only editing the target.",1470870456,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Moving from gerrit:
+
+**James F:**
+This creates a TextInputWidget which is just wrong; the contents covered by the link annotation could be anything up to and including <span>s, <img>s and so on; this would need to be a complete SurfaceWidget, which would totally dominate this inspector and destroy the whole design of it being a lightweight, simple control. I'm pretty strongly against this change for exactly this reason.
+
+**David L:**
+James: This is totally cribbing from Google Docs' design for link labels. It shows the field... if the label is simple. If it's not simple, it hides it. That lets us give people a field that works in most cases, and won't break anything otherwise.
+Admittedly, I just have it *disabled* if it's not-simple, on the theory that might be less confusing, but I could go full-hidden.
+
+**Ed S:**
+That is technically true, however in almost all cases additional annotations to the link are covering, and can be preserved. This is the same behaviour as Google Docs. Links containing content (e.g. img) are many times rarer still. For these cases we can block/and or warn (or not).",1470870390,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"To clarify the issue about ""display text"", both Google Docs and the patch above will maintain all covering annotations, but will remove any partial annotations if the text is edited (e.g. <a><b><i>He</i>llo</b></a> -> <a><b>Bye</b></a>). Also if the label contains any non-text (e.g. an inline image) it will be uneditable, but this is a very rare edge case.
+
+This should also make the editing of external links and numbered external links a bit cleaner, getting rid of the 'add label' button for numbered external links.",1470850953,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Change 303956 had a related patch set uploaded (by DLynch):
+LinkAnnotationInspector: add a ""label"" field
+
+[[https://gerrit.wikimedia.org/r/303956]]
+",1470789051,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Off in T124305 there's a patch to make it easier to select the link-contents, which avoids many of the issues a ""display text"" field has (most notably: it's not just text). It's held up on general ""what design do we want?"" concerns.",1460559037,PHID-USER-hdkktg27rkwebepkv6yw,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"It's now approaching two months since this was declined without adequate explanation and reopened pending that explanation. Please can we now have the reasoning (or a pointer to it) that led to the decline - this remains the biggest single hindrance to simple, intuitive use in my experience.",1460556396,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Sorry Jdforrester, I re-opened this task. I don't doubt that a lot of thinking went into this idea - but could you please provide a concise summary of the reasons you don't want to see this implemented? Again, I don't doubt that there are good reasons, I just don't see any and haven't seen a discussion anywhere. Thank you!",1456522432,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Thinking more about it, that you have had to have discussions about it in ""dozens of places"" (none of which are linked so we can verify this) suggests that actually there is a very strong desire for a two-box solution. 
+
+WONTFIXing something that is so strongly desired by the editing community needs justification, particularly why two boxes would ""mak[e] the user experience too heavy"" - the only explanation actually given, and that was a musing two years ago. 
+
+The only current way to be sure that both link target and link title are correct when editing is to delete what is currently there, write the title, select it, and then create a link. I am unable to correlate this with the goal of creating an editing interface that makes editing easy. ",1456418517,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'd like to third this question. 
+In informal discussions of VE this is one of the most frequent issues brought up. Indeed I'm astounded that anyone could be ""happy"" at this decision. ",1456417495,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'd like to second this question. You could at the very least state the reason why you decline this, as from this feature request it's not clear at all why one would not add this little, extremely helpful textbox in the link widget.",1456257863,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I'd like to second this question. You could at the very least state the reason why you decline this, as from this feature request it's not clear at all why one would not add this little, extremely helpful textbox in the link menu.",1456257811,PHID-USER-n5zbtah6t77lz2asxkmm,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,">>! In T55973#2052851, @Jdforrester-WMF wrote:
+> With the benefit of four years' discussion in dozens of places, I'm now happy to conclude that this is indeed Declined.
+
+Because of...?",1456226144,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"With the benefit of four years' discussion in dozens of places, I'm now happy to conclude that this is indeed Declined.",1456174729,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,[[ https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis#Am.C3.A9lioration_de_l.27insertion_de_lien | New feedback concerning the separate input fields ]]. I also strongly support this idea.,1444311377,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Changing a wikilink to an external link is not so smart, because text in the External links tab is not automatically selected, and therefore needs to be selected before being replaced by typing or pasting.",1434625821,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"@Whatamidoing-WMF Works with Chromium, but not on Firefox (38.0 canonical 1.0 for Ubuntu).",1434616721,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"@Trizek-WMF:  It's supposed to automagically switch to the External links tab if you type ""http://"" at the start.  Is the automatic detection not working for you?",1434563472,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"I've made some edits yesterday evening with VE in order to add an external link. Here is what I did: 
+
+  # select the text
+  # click on the link icon
+  # type my URL in the field
+  # click on ""Done"" button
+  # See a red link
+  # Realize there is a special tab for external links
+  # Start again...
+
+The same happens to me quite all the time. :/",1434530659,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"Copy Google Docs solution?
+
+To elaborate, I don't think that labelling this solution as ""ugly"" is a strong rationale to why it shouldn't actually work for us. I'm fairly sure there must be a fair amount of research behind something that Google came up with for millions of people, and editors are constantly confused by our current interface instead.",1437581407,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,Copy Google Docs solution?,1409658400,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,*** Bug 51438 has been marked as a duplicate of this bug. ***,1395196870,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Link input widget should have separate inputs for target and display text,"This is not a WONTFIX, but it comes close in terms of making the user experience too heavy (for detailed reasoning, see endless bugs passim).",1395196770,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g66fda6j3q2ga6eul3do,task_subcomment,NA
+VisualEditor: Let template's navboxes (VTE links) be used in VE edit move,"<< Currently when you click on a template with the ""VTE"" (view, talk page, edit) links, Visual Editor gives you the option of adding parameters to the transclusion of the template. Most of the templates with the ""VTE"" links are navigational boxes or other transcluded items without parameters, but as the VTE links suggest, we want people to easily view the template page itself. Maybe if someone clicks on a template with VTE links in Visual Editor, rather than being given the regular option to add parameters they should instead be given a dialogue box saying something along the lines of ""This is a template that appears on many pages. Would you like to open this template's page in a new tab?"". —[[User:Arctic.gnome|Arctic Gnome]] <small>([[User talk:Arctic.gnome|talk]] • [[Special:Contributions/Arctic.gnome|contribs]])</small> 13:45, 20 August 2013 (UTC) >>
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1377012600,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-jtv2xb4ipsbwnbem7fka,task_description,open
+VisualEditor: Let template's navboxes (VTE links) be used in VE edit move,"Bug 49772 - VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation) 
+looks relevant. 
+
+The V.T.E links are a specific of the way things are organised on en.wikipedia See for example the nav box template at the bottom of 
+http://en.wikipedia.org/wiki/When_an_Old_Cricketer_Leaves_the_Crease
+
+I suspect bug 49772 will be a more general solution.",1377021493,PHID-USER-7hrs7wwclcldf7mm6a7o,True,PHID-TASK-jtv2xb4ipsbwnbem7fka,task_subcomment,NA
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51527",1375013100,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-zsmkxbjmo6bthiyirco6,task_description,resolved
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"This was re-filed as bug 56205 and fixed in October.
+
+*** This bug has been marked as a duplicate of bug 56205 ***",1385396577,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zsmkxbjmo6bthiyirco6,task_subcomment,NA
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"With the VE being enabled in Help, File & Category pages, this message is now incorrect on en.wp (and others?) too.",1383118394,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-zsmkxbjmo6bthiyirco6,task_subcomment,NA
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"(In reply to comment #1)
+> Do you mean 
+> https://www.mediawiki.org/wiki/Manual:$wgContentNamespaces
+
+Presumably.
+
+> Is VE enabled in other content namespaces?
+
+Only on MediaWiki.org and the test wikis (where the alpha opt-in preference is not shown). Everywhere else, it's just NS0 (articles) and NS2 (user pages).",1375136842,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-zsmkxbjmo6bthiyirco6,task_subcomment,NA
+VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces,"Do you mean 
+https://www.mediawiki.org/wiki/Manual:$wgContentNamespaces
+Is VE enabled in other content namespaces?",1375135683,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-zsmkxbjmo6bthiyirco6,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"**Author:** `jonathan_haas`
+
+**Description:**
+It's currently impossible to change table cell background VE
+
+See for example http://de.wikipedia.org/wiki/Suriyakati-Kalender
+
+**See also**
+* Open subtasks of {T49780} ",1375007580,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_description,open
+Be able to set table cell background (and other formatting options),,1634434555,PHID-USER-6q5jenpm75klo2spmch3,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),,1624208185,PHID-USER-6q5jenpm75klo2spmch3,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),This was requested again at https://www.mediawiki.org/wiki/Topic:Vcflv3wnvk90yycr by @Guarapiranga.  I think that this or similar requests appear a couple of times each year.,1576212562,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#2169644, @Whatamidoing-WMF wrote:
+> If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+
+Please re-read my comment, where I accepted highlighting, as in a table, as a valid use case. But I'm also going to point out that the same information can and should be conveyed by a class, so that we can better enforce accessibility, if no other reason.
+
+See also {T37704} and {T89134}.",1459597392,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#2169644, @Whatamidoing-WMF wrote:
+> If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+
+Please re-read my comment, where I accepted highlighting, as in a table, as a valid use case. But I'm also going to point out that the same information can and should be conveyed by a class.
+
+See also {T37704} and {T89134}.",1459597259,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#2169644, @Whatamidoing-WMF wrote:
+> If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+
+Please re-read my comment, where I accepted highlighting, as in a table, as a valid use case. But I'm also going to point out that the same information can and should be conveyed by a class.
+
+See also T37704.",1459596974,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#2169644, @Whatamidoing-WMF wrote:
+> If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+
+Please re-read my comment, where I accepted highlighting, as in a table, as a valid use case. But I'm also going to point out that the same information can and should be conveyed by a class. See also T37704.",1459596951,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"If random color should not be ""doable"" on the grounds that there's no reasonable use case for it, then James F wouldn't have recommended using ""random color"" in this edit:  https://www.mediawiki.org/w/index.php?diff=1647707&oldid=1647704  But he did, and therefore there is a reasonable use case to be made for having that ability.
+",1459530568,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#969564, @Juandev wrote:
+>>>! In T54180#966351, @Jdforrester-WMF wrote:
+>> There's a strong use case to //not// let this be something people do. The colour in your example adds almost no value but massively distracts from the readability, accessibility and utility of the information being conveyed.
+> 
+> Probably strong case not to use it in Wikipedia, but what about Wikiversity. You may need to highlight cells just to be more atractive for the students or to be able to count someting better. I thing advanced MS Excell of Google Tabs already allow to search by table cell bg color.
+
+This looks like a (really) strong use case for a class to be applied to a row/cell, //not// random style, if in fact ""highlighting"" is being used in multiple places.
+
+I would tend to agree that random color should not be ""doable"" in VE, while permitting the addition of classes may be valuable (especially .wikitable if no others).",1458404950,PHID-USER-yawytiq5q7eduxmvnkid,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#966571, @Krinkle wrote:
+> Note that standardised styles (by the software or by local wikis) for tables can be developed and provided through program code (instead of through article content) by declaring them in CSS stylesheets (such as `MediaWiki:Common.css`).
+> 
+> I'd say it'd be an improvement if VisualEditor has an interface that can apply certain css classes to a table. Especially ones provided by MediaWiki core, such as `wikitable`, `sortable`, and `mw-collapsible`. (Though ideally through an intuitive interface, and not a free-form text field; which requires users to know internal software class names.)
+> 
+> ...
+
+Agreed. One of the most common ""deviations"" made to table element defaults is changing the `vertical-align` of all (or nearly all) of the table cells in a table to render //top// rather than default //middle//.
+
+Most folks assume this requires changing the default `vertical-align` value per every TR or per each TD within a table but the default is actually ''inherit'' for these elements - set by tbody, thead or tfoot which actually has the `vertical-align:middle` setting.
+
+Understanding the tbody element is not 'shown but always present' we can still simplify the table rendering of cell content throughout an entire table by making a simple .css addition to the default stylesheets such as...
+
+``` lang=""css""
+.valign-td-top > tbody {
+	vertical-align: top;
+}
+```
+... in turn, setting `table class=""valign-td-top""` is all the user needs to add (either manually or by design in a VE table option) to accomplish top rendering of content.
+
+Worst case scenario is the user needs to [re]adjust the TH header row's vertical-alignment back to middle - far less work than applying inline styling to each TR or every TD as is the case now.",1454639052,PHID-USER-fflcyhesfpbopooupqa3,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#971085, @Whatamidoing-WMF wrote:
+> I wonder if it could be a feature that is configurable per-wiki, or ideally per-namespace at each wiki.  Then you could get (for example) teaching materials at WIkiversity that use it, but keep it out of the article namespace at the English Wikipedia.  (It would still need to accept copied/pasted tables, and maybe have a 'remove this background color' button—which we need anyway, because of tables copied from other websites.)
+
+So should I understand your statment like we need community consensus for that?",1433206467,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),So the option per wiki is the best choise I guess. Namespaces are not standardized yet on some wv projcects.,1424002582,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"I wonder if it could be a feature that is configurable per-wiki, or ideally per-namespace at each wiki.  Then you could get (for example) teaching materials at WIkiversity that use it, but keep it out of the article namespace at the English Wikipedia.  (It would still need to accept copied/pasted tables, and maybe have a 'remove this background color' button—which we need anyway, because of tables copied from other websites.)",1421081161,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),">>! In T54180#966351, @Jdforrester-WMF wrote:
+> There's a strong use case to //not// let this be something people do. The colour in your example adds almost no value but massively distracts from the readability, accessibility and utility of the information being conveyed.
+
+Probably strong case not to use it in Wikipedia, but what about Wikiversity. You may need to highlight cells just to be more atractive for the students or to be able to count someting better. I thing advanced MS Excell of Google Tabs already allow to search by table cell bg color.",1421024302,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"> The colour...distracts from the readability, accessibility and utility of the information being conveyed.
+
+Making it possible and even moderately easy to render this image in a table instead of in an image would IMO be a significant improvement in the readability, accessibility and utility of the information.  For example, someone with a screen reader could actually read it, and anyone could edit the contents.
+
+I'm not looking for fruit salad in encyclopedia articles, but when someone wants to create a table like this, I want them to think ""Oooh, I can do that in VisualEditor"", not ""I'll draw this in Adobe Illustrator, export it as a jpeg, upload it to Commons, insert it on a page in mediawiki.org, and every time someone needs to have a simple typo fixed, I'll repeat that process.""
+
+",1420843846,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"> The colour...distracts from the readability, accessibility and utility of
+the information being conveyed.
+
+Making it possible and even moderately easy to render this image in a table
+instead of in an image would IMO be a significant improvement in the
+readability, accessibility and utility of the information.  For example,
+someone with a screen reader could actually read it, and anyone could edit
+the contents.
+
+I'm not looking for fruit salad in encyclopedia articles, but when someone
+wants to create a table like this, I want them to think ""Oooh, I can do
+that in VisualEditor"", not ""I'll draw this in Adobe Illustrator, export it
+as a jpeg, upload it to Commons, insert it on a page in mediawiki.org, and
+every time someone needs to have a simple typo fixed, I'll repeat that
+process.""
+
+
+
+
+
+Whatamidoing (WMF)/Sherry Snyder
+Community Liaison
+Wikimedia Foundation, Inc.",1420843792,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"Note that standardised styles (by the software or by local wikis) for tables can be developed and provided through program code (instead of through article content) by declaring them in CSS stylesheets (such as `MediaWiki:Common.css`).
+
+I'd say it'd be an improvement if VisualEditor has an interface that can apply certain css classes to a table. Especially ones provided by MediaWiki core, such as `wikitable`, `sortable`, and `mw-collapsible`. (Though ideally through an intuitive interface, and not a free-form text field; which requires users to know internal software class names.)
+
+And potentially a few other class-name / label combinations provided by the local wiki. There's definitely a use case for having more than one type of table for all of Wikipedia.",1420833804,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"Note that standardised styles (by the software or by local wikis) for tables can be developed and provided through program code (instead of through article content) by declaring them in CSS stylesheets (such as `MediaWiki:Common.css`).
+
+I'd say it'd be an improvement if VisualEditor has an interface that can apply certain css classes to a table. Especially ones provided by MediaWiki core, such as `wikitable`, `sortable` and `mw-collapsible` (though ideally through an intuitive interface, and not a free-form text field (which requires users to know internal software class names).
+
+And potentially a few other class-name / label combinations provided by the local wiki. There's definitely a use case for having more than one type of table for all of Wikipedia.",1420833751,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"There's a strong use case to //not// let this be something people do. The colour in your example adds almost no value but massively distracts from the readability, accessibility and utility of the information being conveyed.",1420829910,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"In terms of the scope for this item:  I'd like (Howie) to be able to create this table in VisualEditor:  https://www.mediawiki.org/wiki/File:Product_stages_and_players.jpg
+
+I'm not entirely sure how to do it in wikitext, but that's what I want to be able to do.
+",1420829373,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),This issue of table cell paragraph formatting is now Bug 65416.,1400273034,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"(In reply to WhatamIdoing from comment #1)
+> ""Other formatting"" should include support for font size and line height, so
+> that tables like the ones seen at
+> https://en.wikipedia.org/w/index.php?oldid=608813235#Early_years will
+> display with the correct row height.
+
+No, that's a bug caused by VE assuming that table cells' paragraphs should be styled like other paragraphs. That's a fix to styling rules, nothing to do with editing them to have custom styles. Could you file a new bug?",1400270237,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+Be able to set table cell background (and other formatting options),"""Other formatting"" should include support for font size and line height, so that tables like the ones seen at https://en.wikipedia.org/w/index.php?oldid=608813235#Early_years will display with the correct row height.",1400265859,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-ppmnn62nd4u24sclez4h,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"Links are frequently placed in edit summaries but the user is currently perversely required to revert to wikicode to insert them.  The VisEd menu should be available for the edit summary and the text should be displayed as it will be seen.  Wysiwyg should apply to all elements of the edit summary (eg, the recently added section title is displayed as code rather than the grey italics as it will be seen).
+
+=== Potential use cases/impacts/hypotheses 
+- **[potential impact]**: if people publishing edits write more expressive edit summaries, these edit summaries will be compelling/interesting to people whose primarily relationship to Wikipedia is as as a reader
+-- //See more in {T379405}
+- **[potential use case]**: enable people to relate edits to the events/campaigns that inspired them to make them (T373232)
+-- //Inspired @AlexHollender-WMF and @ifried...//
+- **[hypothesis]** If people have an easier time doing things like mentioning other people, inserting links, and formatting text within the edit summary input, they will invest more effort into writing edit summaries.
+- **[potential impact]** If people write more descriptive edit summaries, then machine learning models will become more effecting at learning from the actions volunteers are taking because these models will have to make fewer inferences/assumptions about the semantic meaning of a change/changes someone is making. //This thought is inspired by the conversation we (the Editing Team) had with @diego on 27 July 2022.//
+- **[potential impact]** If people write more descriptive edit summaries, then people visiting an article's ""page history""  will have an easier time: A) understanding how the article they are interested in evolved over time and B) identifying changes they are curious to learn more about
+-- this could also open up the potential for edits/diffs being presented as small, standalone pieces of information people could ""consume"" 
+
+=== Related
+- T123529
+- T323875
+- https://hashtags.wmcloud.org/",1374996120,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-imjhsazltcwrba7knjzi,task_description,open
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,">>! In T54174#6178473, @MMiller_WMF wrote:
+> @ppelberg -- thanks for thinking about this.  We have the idea for ""notify your mentor"" as part of the longer term of suggested edits.  [[https://commons.wikimedia.org/wiki/File:Prototype_of_confirmation_desktop_guidance_for_suggested_edits_2020-01-16.png | Here's a mockup ]], and shown below.
+Assuming people are ""feeling good"" after having successfully completed an edit, it seems like a good idea to provide them with an opportunity to ""shop"" for more edits to make so they can keep that flow going.
+
+> But maybe it would make sense to combine that into one step, which would reduce how many ""posts"" happen after an edit is completed, and streamline the workflow for the user.
+This is what I had in mind. Additionally, I wonder if guiding the mentee to notify their mentor by way of edit summaries could have the following effects:
+- Other experienced editors will act more conscientiously towards newcomers, and their edits, if newcomers' intentions are more legible them.
+-- //Here, I'm assuming the interaction the ""Notify mentor"" workflow would facilitate would be less visible to experienced contributors than if the communication happened through edit summaries.//
+- Mentors will appreciate newcomers interacting with them via the tools/workflows they're used to
+- Newcomers will learn a skill that is likely to benefit outside the context of Newcomer tasks.
+
+I also wonder whether it's more consistent with how other, more experienced editors behave, to introduce this piece of communication (read: Edit summaries) as being //a part of the edit process// as opposed to something that happens after the fact. //This is a thought I'd like to develop more.// 
+
+>It sounds like you're saying that it would be better if they could use the `@` symbol and autocomplete with usernames.  Perhaps that would be useful beyond just newcomers.
+Exactly (to both points).
+
+> But all this said, I think that if we're going to encourage newcomers to ping their mentors in the edit summary (or elsewhere), we wouldn't have them type out their mentor's name, even with autocomplete.  The system would know their mentors name and take care of that part for them.  Although, the argument I see for having the newcomer type their mentor's name is that they would learn how to ping in edit summaries.  What do you think?
+I think it would be fine to automatically insert the mentor's handle into the newcomers' edit summary //so long as// newcomers can see the ping and have it appears as such: [@Marshall](https://meta.wikimedia.org/wiki/User:MMiller_(WMF)).
+
+Reason:
+- I think newcomers will intuitively understand/recognize the presence of  [@USERNAME](https://meta.wikimedia.org/wiki/User:MMiller_(WMF)) to mean: [i]
+-- A) @USERNAME is going to get a notification
+-- B) To notify someone next time, I bet I can just type {key @} and the rest will work like it does on other platforms. 
+
+
+---
+i. The above is informed, in part, by the latest round of user tests we ran where we found most test participants intuitively understood typing {key @} to tag/ping/mention someone else. //See ""@-mentioning a user not in the conversation"" in T246190#6186156 //",1591841391,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,">>! In T54174#6178473, @MMiller_WMF wrote:
+> @ppelberg -- thanks for thinking about this.  We have the idea for ""notify your mentor"" as part of the longer term of suggested edits.  [[https://commons.wikimedia.org/wiki/File:Prototype_of_confirmation_desktop_guidance_for_suggested_edits_2020-01-16.png | Here's a mockup ]], and shown below.
+Assuming people are ""feeling good"" after having successfully completed an edit, it seems like a good idea to provide them with an opportunity to ""shop"" for more edits to make so they can keep that flow going.
+
+> But maybe it would make sense to combine that into one step, which would reduce how many ""posts"" happen after an edit is completed, and streamline the workflow for the user.
+This is what I had in mind. Additionally, I wonder if guiding the mentee to notify their mentor by way of edit summaries could have the following effects:
+- Other experienced editors will act more conscientiously towards newcomers, and their edits, if newcomers' intentions are more legible them.
+-- //Here, I'm assuming the interaction the ""Notify mentor"" workflow would facilitate would be less visible to experienced contributors than if the communication happened through edit summaries.//
+- Mentors will appreciate newcomers interacting with them via the tools/workflows they're used to
+- Newcomers will learn a skill that is likely to benefit outside the context of Newcomer tasks.
+
+I also wonder whether it's more consistent with how other, more experienced editors behave, to introduce this piece of communication (read: Edit summaries) as being //a part of the edit process// as opposed to something that happens after the fact. //This is a thought I'd like to develop more.// 
+
+>It sounds like you're saying that it would be better if they could use the `@` symbol and autocomplete with usernames.  Perhaps that would be useful beyond just newcomers.
+Exactly (to both points).
+
+> But all this said, I think that if we're going to encourage newcomers to ping their mentors in the edit summary (or elsewhere), we wouldn't have them type out their mentor's name, even with autocomplete.  The system would know their mentors name and take care of that part for them.  Although, the argument I see for having the newcomer type their mentor's name is that they would learn how to ping in edit summaries.  What do you think?
+I think it would be fine to automatically insert the mentor's handle into the newcomers' edit summary //so long as// newcomers can see the ping and have it appears as such: [@Marshall](https://meta.wikimedia.org/wiki/User:MMiller_(WMF)).
+
+Reasons:
+- I think newcomers will intuitively understand/recognize the presence of  [@USERNAME](https://meta.wikimedia.org/wiki/User:MMiller_(WMF)) to mean: [i]
+-- A) @USERNAME is going to get a notification
+-- B) To notify someone next time, I bet I can just type {key @} and the rest will work like it does on other platforms. 
+
+
+---
+i. The above is informed, in part, by the latest round of user tests we ran where we found most test participants intuitively understood typing {key @} to tag/ping/mention someone else. //See ""@-mentioning a user not in the conversation"" in T246190#6186156 //",1591841123,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@ppelberg -- thanks for thinking about this.  We have the idea for ""notify your mentor"" as part of the longer term of suggested edits.  [[ https://commons.wikimedia.org/wiki/File:Prototype_of_confirmation_desktop_guidance_for_suggested_edits_2020-01-16.png | Here's a mockup ]], and shown below.
+
+{F31847417}
+
+Our thinking here was that the user would not be pinging the mentor in an actual edit summary, but rather writing them a separate notification via a dedicated workflow that would automatically ping the mentor, after having already posted a normal edit summary.
+
+But maybe it would make sense to combine that into one step, which would reduce how many ""posts"" happen after an edit is completed, and streamline the workflow for the user.
+
+It is currently possible to ping users in edit summaries, but only by using the traditional user page link syntax, e.g. `[[User:Cloud atlas]]`.  It sounds like you're saying that it would be better if they could use the `@` symbol and autocomplete with usernames.  Perhaps that would be useful beyond just newcomers.
+
+But all this said, I think that if we're going to ecourage newcomers to ping their mentors in the edit summary (or elsewhere), we wouldn't have them type out their mentor's name, even with autocomplete.  The system would know their mentors name and take care of that part for them.  Although, the argument I see for having the newcomer type their mentor's name is that they would learn how to ping in edit summaries.  What do you think?
+
+FYI @RHo ",1590799405,PHID-USER-krko4robkho2pjor6klf,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@ppelberg -- thanks for thinking about this.  We have the idea for ""notify your mentor"" as part of the longer term of suggested edits.  [[ https://commons.wikimedia.org/wiki/File:Prototype_of_confirmation_desktop_guidance_for_suggested_edits_2020-01-16.png | Here's a mockup ]].  Our thinking here was that the user would not be pinging the mentor in an actual edit summary, but rather writing them a separate notification via a dedicated workflow that would automatically ping the mentor, after having already posted a normal edit summary.
+
+But maybe it would make sense to combine that into one step, which would reduce how many ""posts"" happen after an edit is completed, and streamline the workflow for the user.
+
+It is currently possible to ping users in edit summaries, but only by using the traditional user page link syntax, e.g. `[[User:Cloud atlas]]`.  It sounds like you're saying that it would be better if they could use the `@` symbol and autocomplete with usernames.  Perhaps that would be useful beyond just newcomers.
+
+But all this said, I think that if we're going to ecourage newcomers to ping their mentors in the edit summary (or elsewhere), we wouldn't have them type out their mentor's name, even with autocomplete.  The system would know their mentors name and take care of that part for them.  Although, the argument I see for having the newcomer type their mentor's name is that they would learn how to ping in edit summaries.  What do you think?
+
+FYI @RHo ",1590799352,PHID-USER-krko4robkho2pjor6klf,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@Esanders would resolving this task enable us to extend T232601 to edit summaries? 
+
+I'm not suggesting we prioritize this, but the use case below occurred to me today and thought I'd ask.
+
+---
+=== Context
+**Use case: newcomer seeking review from mentor**
+1. Newcomer receives guidance from an experienced editor, be it via the Growth team's mentorship module or some other means [i]
+2. Newcomer makes an edit per mentor's instructions
+3. Newcomer wants to get the attention of their mentor, to ensure they made their edit correctly //before// someone comes along and reverts said edit
+4. Newcomer types their edit summary and @-mentions their mentor in said summary
+
+**😀 Benefits**
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Newcomer avoids their edit being reverted by someone else 
+- Mentor and newcomer now have a more contextual way of communicating about the process of editing through the edits themselves.
+
+**😬 Risks**
+- Easier to notify people = more noise
+- People writing edit summaries could begin to tailor their summaries to individuals rather than ""other editors as a whole"" leading them to become more difficult to understand.
+
+---
+
+i. https://nl.wikipedia.org/wiki/Overleg_gebruiker:Jessevermeulen18
+
+---
+@MMiller_WMF cc'ing you for your awareness.",1590711675,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@Esanders would resolving this task enable us to extend T232601 to edit summaries? 
+
+I'm not suggesting we prioritize this, but the use case below occurred to me today and thought I'd ask.
+
+---
+=== Context
+**Use case: newcomer seeking review from mentor**
+1. Newcomer receives guidance from an experienced editor, be it via the Growth team's mentorship module or some other means [i]
+2. Newcomer makes an edit per mentor's instructions
+3. Newcomer wants to get the attention of their mentor, to ensure they made their edit correctly //before// someone comes along and reverts said edit
+4. Newcomer types their edit summary and @-mentions their mentor in said summary
+
+**😀 Benefits**
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Newcomer avoids their edit being reverted by someone else 
+- Mentor and newcomer now have a more contextual way of communicating about the process of editing through the edits themselves.
+
+**😬 Risks**
+- Easier to notify people = more noise
+- People writing edit summaries could begin to tailor their summaries to individuals rather than ""edits as a whole"" leading them to become more difficult to understand.
+
+---
+
+i. https://nl.wikipedia.org/wiki/Overleg_gebruiker:Jessevermeulen18
+
+---
+@MMiller_WMF cc'ing you for your awareness.",1590708629,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@Esanders would resolving this task enable us to extend T232601 to edit summaries? 
+
+I'm not suggesting we prioritize this, but the use case below occurred to me today and thought I'd ask.
+
+---
+=== Context
+**Use case: newcomer seeking review from mentor**
+1. Newcomer receives guidance from an experienced editor, be it via the Growth team's mentorship module or some other means [i]
+2. Newcomer makes an edit per mentor's instructions
+3. Newcomer wants to get the attention of their mentor, to ensure they made their edit correctly //before// someone comes along and reverts said edit
+4. Newcomer types their edit summary and @-mentions their mentor in said summary
+
+**😀 Benefits**
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Newcomer avoids their edit being reverted by someone else 
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Mentor and newcomer now have a more contextual way of communicating about the process of editing through the edits themselves.
+
+**😬 Risks**
+- Easier to notify people = more noise
+- People writing edit summaries could begin to tailor their summaries to individuals rather than ""edits as a whole"" leading them to become more difficult to understand.
+
+---
+
+i. https://nl.wikipedia.org/wiki/Overleg_gebruiker:Jessevermeulen18
+
+---
+@MMiller_WMF cc'ing you for your awareness.",1590708577,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,"@Esanders would resolving this task enable us to extend T232601 to edit summaries? 
+
+I'm not suggesting we prioritize this, but the use case below occurred to me today and thought I'd ask.
+
+---
+=== Context
+**Use case: newcomer seeking review from mentor**
+1. Newcomer receives guidance from an experienced editor, be it via the Growth team's mentorship module or some other means [i]
+2. Newcomer makes an edit per mentor's instructions
+3. Newcomer wants to get the attention of their mentor, to ensure they made their edit correctly //before// someone comes along and reverts said edit
+4. Newcomer types their edit summary and @-mentions their mentor in said summary
+
+**😀 Benefits**
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Newcomer avoids their edit being reverted by someone else 
+- Mentor gets a notification linking them to the precise edit they are being asked to review
+- Mentor and newcomer now have a more contextual way of communicating about the process of editing through the edits themselves.
+
+---
+
+i. https://nl.wikipedia.org/wiki/Overleg_gebruiker:Jessevermeulen18
+
+---
+@MMiller_WMF cc'ing you for your awareness.",1590708453,PHID-USER-7x5ai23ne5qampjf3g7r,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,Re-purposing this to flesh out bug 42139 comment 1.,1390417719,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.,Dupe of bug 42139 (specifically bug 42139 comment 1)?,1374996450,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-imjhsazltcwrba7knjzi,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"There are many pages for which VisualEditor is broken.  In some cases, the page syntax can be changed to avoid the problem.  In other cases (such as nlwp's largethumb, dewp dab pages, enwp episode lists), the design affects many pages, and the only feasible solution is to fix the parser.  While we wait for fixes, the VE should be disabled on those pages known to be affected.
+
+The set of pages to be VE-disabled could be a category, if you trust the villagers..:-)
+Or a page title blacklist in MediaWiki: namespace so it is admin only
+Or a page content regex blacklist in MediaWiki: namespace so it is easier to blacklist all pages which include a certain element.
+
+**See Also**: {T55767} (also declined)",1374931800,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_description,declined
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),">>! In T54141#1568572, @Neil_P._Quinn_WMF wrote:
+> @Kipod, whether it's easy or hard it not really the main issue. The main issue is whether the benefits outweigh the downsides—and unfortunately there //are// downsides. These magic words would increase complexity, sometimes stay on pages long after the need is gone, and risk confusing users when no visual editor tab appears on a page where they expect to see it.
+> 
+> Today, the visual editor corrupts pages //far// less often than it did when this bug was filed two years ago, which makes me think that the benefits of these magic words would be small. Are there other reasons for having them?
+
+Has Paroid been round-trip tested against Wikisource pages in the main & Page: namespace?
+I am guessing there will be a new batch of page corruptions on Wikisource when it is deployed for the Page: namespace, if there has not been specific testing for the Page: namespace. Wikisource has some very odd hacks. Many thanks if this testing has already been done and there are no serious problems when it is deployed.
+
+An alternative would be for wikisource to add an editnotice, which is only shown for VE editors, for pages which have problems with VE. Then it can be more advisory:
+
+""this page may have problems with VE; please check the diff after saving changes. Report bugs at <x> ; if there are no bugs, remove this editnotice by <do y>.""",1461565625,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),">>! In T54141#1568572, @Neil_P._Quinn_WMF wrote:
+> Today, the visual editor corrupts pages //far// less often than it did when this bug was filed two years ago, which makes me think that the benefits of these magic words would be small. Are there other reasons for having them?
+
+The primary benefit I see is that I'd like to enable VE on pages where it will not be enabled globally. ",1461516395,PHID-USER-fgzcdbj3je3ksnhufo47,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"@Kipod, whether it's easy or hard it not really the main issue. The main issue is whether the benefits outweigh the downsides—and unfortunately there //are// downsides. These magic words would increase complexity, sometimes stay on pages long after the need is gone, and risk confusing users when no visual editor tab appears on a page where they expect to see it.
+
+Today, the visual editor corrupts pages //far// less often than it did when this bug was filed two years ago, which makes me think that the benefits of these magic words would be small. Are there other reasons for having them?
+
+>this should override the namespace default, but _not_ the user personal choice (i.e., if the user elects to disable VE. 
+That only works for people who turn off the visual editor completely. If you disable the visual editor on a given page, I can no longer choose to use it. 
+
+Peace to you as well :)",1440440676,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"i see this is ""closed, declined"".
+since another ticket, opened by me, was ""closed, duplicate"" pointing here, i would like to request to reconsider.
+implementing my request should be very easy, controllable, requres no changes outside VE, and very simple change inside VE, and, oh, by the way, will also close/solve this one. so i paraphrase my previous request here:
+
+
+there are good reasons (i guess) not to enable VE on some namespaces, and specifically ""project"" namespace, but it would be desirable to be able to override it for specific pages.
+ 
+i was thinking something like adding two new magic words:
+
+
+```
+__ENABLE_VISUAL_EDITOR__
+__DISABLE_VISUAL_EDITOR__
+```
+this should override the namespace default, but _not_ the user personal choice (i.e., if the user elects to disable VE.
+
+implementing these two switches is 100% risk-free (currently there are no pages that use these magic words), and should be easy enough to implement, such that the switch that decides wheter or not to enable VE will test for these magic words, and make the correct decisiosn.
+
+so, implementing it would be risk-free, easy, and will soleve at least two legitimate requests that came from the community (with some 19 members subscribing to this ticket).
+
+maybe you should consider reopening. unfortunately i can't offer a patch to prove my claim that it's  ""easy""...
+
+
+peace.",1440372132,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"i see this is ""closed, declined"".
+since another ticket, opened by me, was ""closed, duplicate"" pointing here, i would like to request to reconsider.
+implementing my request should be very easy, controllable, requres no changes outside VE, and very simple change inside VE, and, oh, by the way, will also close/solve this one. so i paraphrase my previous request here:
+
+
+there are good reasons (i guess) not to enable VE on some namespaces, and specifically ""project"" namespace, but it would be desirable to be able to override it for specific pages.
+ 
+i was thinking something like
+
+
+```
+__ENABLE_VISUAL_EDITOR__
+__DISABLE_VISUAL_EDITOR__
+```
+this should override the namespace default, but _not_ the user personal choice (i.e., if the user elects to disable VE.
+
+implementing these two switches is 100% risk-free (currently there are no pages that use these magic words), and should be easy enough to implement, such that the switch that decides wheter or not to enable VE will test for these magic words, and make the correct decisiosn.
+
+so, implementing it would be risk-free, easy, and will soleve at least two legitimate requests that came from the community (with some 19 members subscribing to this ticket).
+
+maybe you should consider reopening. unfortunately i can't offer a patch to prove my claim that it's  ""easy""...
+
+
+peace.",1440372042,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"i see this is ""closed, declined"".
+since another ticket, opened by me, was ""closed, duplicate"" pointing here, i would like to request to reconsider.
+implementing my request should be very easy, controllable, requres no changes outside VE, and very simple change inside VE, and, oh, by the way, will also close/solve this one. so i paraphrase my previous request here:
+
+
+there are good reasons (i guess) not to enable VE on some namespaces, and specifically ""project"" namespace, but it would be desirable to be able to override it for specific pages.
+ 
+i was thinking something like
+
+__ENABLE_VISUAL_EDITOR__
+__DISABLE_VISUAL_EDITOR__
+this should override the namespace default, but _not_ the user personal choice (i.e., if the user elects to disable VE.
+
+implementing these two switches is 100% risk-free (currently there are no pages that use these magic words), and should be easy enough to implement, such that the switch that decides wheter or not to enable VE will test for these magic words, and make the correct decisiosn.
+
+so, implementing it would be risk-free, easy, and will soleve at least two legitimate requests that came from the community (with some 19 members subscribing to this ticket).
+
+maybe you should consider reopening. unfortunately i can't offer a patch to prove my claim that it's  ""easy""...
+
+
+peace.",1440351968,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"Hello, @Jdforrester-WMF. You merged T107426 here, but it is not the same problem. The main part over there was an ability to ENABLE the VisualEditor on a page in VE-disabled namespace. Thank you.
+",1438769968,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),Agreed.,1437697879,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),">>! In T54141#1312318, @ssastry wrote:
+> Yes, the largethumb template issue has been fixed since early 2014.
+> 
+> The only large-scale corruptions that have been reported have been due to transient bugs on deploys (which tend to be fixed quickly or deploys reverted). There are some pages on which Parsoid could potentially cause corruptions, but those one-off bugs tend to get fixed promptly. There are no large sets of pages that I am aware of that aren't handled properly on the Parsoid end. So, as far as I know, from the Parsoid perspective, this workaround shouldn't be needed.
+
+@Jdforrester-WMF, what do you think about declining this bug?
+
+",1437697817,PHID-USER-vixhpqcaqfpdj6impfwy,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"Yes, the largethumb template issue has been fixed since early 2014.
+
+The only large-scale corruptions that have been reported have been due to transient bugs on deploys (which tend to be fixed quickly or deploys reverted). There are some pages on which Parsoid could potentially cause corruptions, but those one-off bugs tend to get fixed promptly. There are no large sets of pages that I am aware of that aren't handled properly on the Parsoid end. So, as far as I know, from the Parsoid perspective, this workaround shouldn't be needed.",1432641854,PHID-USER-slccyo5rqasgpljxny7g,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"I'm pretty certain that the largethumb template issue has been fixed, and based on the lack of activity and concrete reports of ongoing large-scale corruptions it seems possible that the work-around described in this task might no longer be needed. @ssastry and @jdforrester-wmf: Could you chime in?",1432629212,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"This is an old task, so it would be good to get some specificity around whether this is still an issue and under which circumstances. Can someone please re-validate this issue?",1432563831,PHID-USER-v7pv6vw32wp56vc4wyt7,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"An interesting solution is to add a wikitext magic word `__NOVISUALEDITOR__` to disable it in contexts it might otherwise be enabled.
+
+https://www.mediawiki.org/wiki/Thread:Extension_talk:VisualEditor/Behavior_switch_NOVISUALEDITOR",1432543493,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"An interesting solution is to add a wikitext magic word __NOVISUALEDITOR__ to disable it in contexts it might otherwise be enabled.
+
+https://www.mediawiki.org/wiki/Thread:Extension_talk:VisualEditor/Behavior_switch_NOVISUALEDITOR",1392433326,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"(In reply to comment #6)
+> Obviously VE/Parsoid shouldn't cause breakage - the goal would be to keep
+> membership of that category close to zero at any given time. But if and when
+> things do break, it'd be good to have an official mechanism to deal with it,
+> rather than just template hacks.
+
+Bugzilla is the official mechanism for dealing with breakages.
+
+While it's easy to say that the goal would be to keep the category membership near zero, it sounds like (from reading comment 0) that this category would quickly include tens of thousands of pages.",1375488872,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"Obviously VE/Parsoid shouldn't cause breakage - the goal would be to keep membership of that category close to zero at any given time. But if and when things do break, it'd be good to have an official mechanism to deal with it, rather than just template hacks.",1375488524,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),I don't like the idea presented in bug 52489 (a blacklist category). VisualEditor simply shouldn't break pages ever. Users shouldn't be required to shield articles from it; that's a bit insane.,1375488293,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"It would indeed be helpful to be able to selectively disable VisualEditor (we should indicate to a user who'd otherwise see VisualEditor that it is disabled, to reduce confusion).
+
+A hidden blacklist category could be included in a page or template to achieve
+the desired effect, and could be used by developers to prioritize roundtripping
+issues.",1375488230,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),*** Bug 52489 has been marked as a duplicate of this bug. ***,1375488138,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"If WMF has spare compute power, Parsoid could flag which pages it _may_ break, and tell the VE extension to not enable itself on those pages.",1375047287,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page),"A temporary solution is being developed: {{Disable VE top}} and {{Disable VE bottom}}
+
+https://en.wikipedia.org/wiki/Template:Disable_VE_top",1374991704,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-qrsg7i26ioq3iroi5j3v,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"The Visual Mode editor of Wikia is able to check all the available parameters automatically without the need for editors to edit the TemplateData for each template manually which is unrealistic to be done for over 505k templates on English Wikipedia.
+However, Wikia's template editor has a severe flaw that it cannot handle a template to be included inside another template. The visual editor will deem the coding to be too complex and forcibly switch back to source mode editor.
+
+--------------------------
+**See Also**:
+T54581 / {T191756}",1374901500,PHID-USER-xnvlg7y5phtzugavv6wj,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_description,open
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,">>! In T54135#2501906, @Whatamidoing-WMF wrote:
+> The GUI for TemplateData can detect (or attempt to detect) parameters now.  I wonder whether that could be 'borrowed' by the template tool?
+
+It's not perfect, and in the GUI there is manual review involved before publication. However, from a user perspective, the only side-effect of the detection is suggestion of parameter names. Not anything beyond that. That's fairly harmless.
+
+If we're ready to try and make this kind of detection available to users without review, then I propose to do this in the TemplateData API instead of in VisualEditor.
+
+That way it will benefit all users of the data, not just VE. And it will keep the logic in the same repository. When VisualEditor fetches it from the API will automatically respond with either the authored data, or fallback to auto-detection for parameter keys.",1469726549,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,">>! In T54135#2501906, @Whatamidoing-WMF wrote:
+> The GUI for TemplateData can detect (or attempt to detect) parameters now.  I wonder whether that could be 'borrowed' by the template tool?
+
+It's not perfect, and in the GUI there is manual review involved before publication. However, from a user perspective, the only side-effect of the detection is suggestion of parameter names. Not anything beyond that. That's fairly harmless.
+
+If we're ready to try and make this kind of detection available to users without review, then I propose to do this in the TemplateData API instead of in VisualEditor.
+
+That way it will benefit all users of the data, not just VE. And it will keep the logic in the same repository. When VisualEditor fetches it from the API which will automatically respond with either the authored data, or fallback to auto-detection for parameter keys.",1469726512,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,The GUI for TemplateData can detect (or attempt to detect) parameters now.  I wonder whether that could be 'borrowed' by the template tool?,1469716429,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,*** Bug 70228 has been marked as a duplicate of this bug. ***,1409694736,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"(In reply to comment #2)
+> This is something we're unlikely to get to do soon, as it would require a
+> vast
+> amount of work (and, indeed, Strong AI to do properly). However, it would be
+> a
+> great improvement, yes.
+
+Indeed. It would help the newbies - not to push them to look for template page and/or template documentation and fill it slow, piece by piece. It is than much faster to add it copy&paste in wiki code, than use VE.",1388572741,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"(In reply to comment #6)
+> (In reply to comment #5)
+> > Kipod do you have a direct link to templatewizard as I've like to link to it?
+> 
+> See bug 52581 comment 4
+
+Or even
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_103#Template_Parameter_Wizard
+mentioned on bug 39598 comment 1.",1383413531,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"(In reply to comment #5)
+> Kipod do you have a direct link to templatewizard as I've like to link to it?
+
+See bug 52581 comment 4
+
+The transclusion UI currently requires thousands of hours to implement on each and every wiki.  This is an enormous design problem that especially impacts small wikis without thousands of minions who have nothing better to do but create templatedata, so I've added this as a blocker for non-English Wikipedia (bug 51792).",1381022591,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"It is dead easy all you need to do is scan for {{{1}}}, {{{name}}}, {{{1| {{{name| etc. I've implemented this at
+http://en.wikipedia.org/wiki/User:Salix_alba/TDSkell
+and there are a few other implementations about. 
+
+Kipod do you have a direct link to templatewizard as I've like to link to it?
+
+There are 300,000 templates on the English wikipedia so many will never have their TemplateData written making this an important enhancement. 
+
+A slightly enhanced version of this request was asked at 
+
+http://en.wikipedia.org/w/index.php?title=Wikipedia_talk%3AVisualEditor&diff=574762591&oldid=573484823
+
+in addition to just getting the names it wanted to find the ""mandatory"" parameters, a much harder job.",1380869650,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,Kipod's Template Parameter Wizard is exactly the thing I'm looking for. At least it works in Wikitext mode nicely.,1375976785,PHID-USER-xnvlg7y5phtzugavv6wj,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"templatewizard on hewiki implements this logic using 9 lines on JS, (so PHP  should probably be able to accomplish that with no more than 50 lines). might not be perfect, but it works for a long time now, and i did not get any bug report yet.
+
+peace.",1375943106,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"This is something we're unlikely to get to do soon, as it would require a vast amount of work (and, indeed, Strong AI to do properly). However, it would be a great improvement, yes.",1375937039,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it,"i added a ""see also"" to bug 52581.
+
+the idea is not to change anything with VE itself, but rather to teach teh TemplateData extension to return a ""cookie cutter"" templatedata through the API if it does not find ""templatedata"" tag on the template page.
+
+this way, all existing functionality, with all the neat thing one can do with templatedata will still work, and still, VE will be usable for template editing even without it.
+
+also, i think that programmatically, the right place to handle the issue is in the templatedata extension and not in VE itself (in addition to being cleaner and shorter code, there might be other scripts and tools that want to use the templatedata API. even if these were not a consideration, the templatedata extension is the right place to deal with templatedata shortcomings).
+
+
+peace.",1375882556,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-dpwiikhbs2gw5p5foc5a,task_subcomment,NA
+VisualEditor: Allow preference to move toolbar to over navigation sidebar,"The editor an en.wp who signs as ""Josh, linguist"" has left the following suggestion about toolbar placement in the Visual Editor:
+
+""I've encountered a sort of inconvenience which is the following: while editing, the toolbar occupies a significant area in the upper third visually and otherwise blocking the text, when we, at the same time, usually have an unoccupied area to the left (where the navigation column is which is often empty much below the existing items); the question is why not to devise a possibility, an option to change its place — I mean the toolbar could be opted to place it either where it's offered to be now – or, otherwise, on the left side of the pane – where it should not be blocking an essential area of the text to edit, in this case the text available without scrolling will be by, approximately (depending on your zoom), a half more than it is now.""
+
+For RTL wikis read ""right"" instead of ""left"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374662220,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-ks4nmmzc4p4mogffuzxg,task_description,open
+VisualEditor: Allow preference to move toolbar to over navigation sidebar,"In that case, though, we'd only really have room for six toolbar options and then ""…"", which I'm not sure is much better. :-(",1425591680,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ks4nmmzc4p4mogffuzxg,task_subcomment,NA
+VisualEditor: Allow preference to move toolbar to over navigation sidebar,"Hmm, interesting idea. Lack of vertical space is especially a problem when using an on-screen keyboard, like on a tablet.
+
+{F56237}",1425591542,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ks4nmmzc4p4mogffuzxg,task_subcomment,NA
+VisualEditor: Allow preference to move toolbar to over navigation sidebar,"This is an interesting idea, and one worth exploring; right now, the team are focussed on squashing bugs, performance fixes, and core usability experience improvements, so I'm marking this as ""Lowest"" priority for now to avoid cookie-licking.",1379657567,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ks4nmmzc4p4mogffuzxg,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","one thing that makes life better with existing editor is the fact that when editing a specific section, the section name is automatically added to the edit summary. often, this ends up being the entire edit summary.
+
+REQUESTED ACTION
+1) when hitting ""save"", test to see if all the diffs are contained in a single section, and if so, add the section name to the edit summary automatically.
+2) just like with existing editor, allow the user to modify or remove this part. i.e., the request is to pre-populate the summary box, not to add section name outside of summary box such that the user can't touch it.
+
+peace.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**: T54859, T50274, T52872, T60488",1374605160,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_description,open
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary",">>! In T53903#959238, @matmarex wrote:
+>> The scope of the bug is bigger than that?
+>  
+> Yes:
+>  
+> - When the user edits text in other sections too, this hint shouldn't appear.
+> - When the user opens VE using the ""Edit"" tab at the top and only edits one section, the appropriate hint should appear.
+
+what he said.
+with VE, the ""edit"" links to the right (or left, in rtl wikis) of the section title are misleading: unlike wikieditor, where clicking one of those will limit the changes to this section, with VE there no such limitation. 
+
+IMO, the current VE behavior is wrong and misleading (T60488 agrees with this view). when looking at page history, i don't care which thingy the editor clicked to start the editor - i want to know which changes this edit contains.
+if you do not _know_ that the changes are limited to some section, please don't tell me they are. (and, on the other hand, if you _do_ know such a thing, it would be nice if you told me).
+
+peace.",1420824665,PHID-USER-akv4ingxkspiiam6r2n4,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","> The scope of the bug is bigger than that?
+ 
+Yes:
+ 
+- When the user edits text in other sections too, this hint shouldn't appear.
+- When the user opens VE using the ""Edit"" tab at the top and only edits one section, the appropriate hint should appear.",1420635773,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","Curret behavior in production:
+
+- click on Edit on a section on a page
+- make changes to that section - click Save
+- Save dialog box - 'Edit summary' box will pre-populated with the title of a section that was edited: 
+/* Section 3 */ 
+- 'Review your changes' will have an additional pointer to the section that was edited:
+Preview of edit summary:
+(→‎Section 3: )
+
+The scope of the bug is bigger than that?
+",1419970531,PHID-USER-4alekd35in5tg53zpsl4,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","(In reply to Elitre from comment #8)
+> Isn't this the current behavior (for various meanings of ""section editing"")?
+
+No. This is asking for VE-MW to insert the name of the section edited if only one section was edited, even if the editor was launched from a page-level link. Doing it when the user clicks a section edit link was bug 50872 and is indeed done. Not doing it when the user clicks a section edit link and then edits outside the link is bug 58488.",1412985721,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","Isn't this the current behavior (for various meanings of ""section editing"")?",1412929540,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary",*** Bug 56891 has been marked as a duplicate of this bug. ***,1384842568,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary",(Thanks Matthew!),1376512668,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","(In reply to comment #4)
+> A user at it.wp wonders: if VE could pre-populate the summary box, could it
+> also auto-add the text that was added, in case of very short additions? i.e.,
+> if someone added a parameter to a template, could it automatically detect
+> what was added and write it in the edit summary? Thanks.
+
+Yes, in theory, but in my opinion, that's a separate bug.  Filed as bug 52859.",1376506478,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","A user at it.wp wonders: if VE could pre-populate the summary box, could it also auto-add the text that was added, in case of very short additions? i.e., if someone added a parameter to a template, could it automatically detect what was added and write it in the edit summary? Thanks.",1376403025,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","You're right, this isn't a duplicate; I'm re-opening and titling it to be clearer.",1375199919,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","**ignatzmice.wiki** wrote:
+
+I agree with kipod's comments at bug 50872, this bug is not a duplicate if that one. This would be a very useful feature (if rather resource-intensive).",1375138221,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+"If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary","
+
+*** This bug has been marked as a duplicate of bug 50872 ***",1374605494,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-z3skamqtqkfqxyfwcbsx,task_subcomment,NA
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,"The basic idea is to have a clear and pleasant-to-use web-based interface for generating a MediaWiki instance manifest. The interface should allow you to tick off the extensions you want, for example, and it would automate the configuration of supporting software like Apache and memcached. There's an attractive example of such an interface at <https://puphpet.com/>.
+
+MediaWiki-Vagrant already implements the bulk of the work in that it provides a set of parametrized, MediaWiki-oriented Puppet modules and resource types. In plain English: MediaWiki-Vagrant can take a configuration file that says ""give me a MediaWiki instance with Scribunto and VisualEditor that is set up for development work"" and configure a machine to match these specifications.
+
+A number of cloud computing platforms provide hooks for uploading Puppet code to automate the creation and customization of servers. Some are event implemented as Vagrant 'providers', which means that you can run 'vagrant up' and Vagrant will create a cloud instance rather than a VirtualBox VM. Examples include vagrant-rackspace for Rackspace Cloud (<https://github.com/mitchellh/vagrant-rackspace>) and vagrant-aws (<https://github.com/mitchellh/vagrant-aws>) for Amazon AWS. A vagrant-openstack provider (<https://github.com/aodn/vagrant-openstack>) also exists; I don't know how much work it would take to make it work with Labs.
+
+The major work-item would be to build the web interface (or adapting the source code of <https://puphpet.com/> or some other project -- there are several), ideally as a MediaWiki extension so that we can offer the ability to provision a virtual server (either local or cloud-based) right on MediaWiki.org.
+
+I think that this could considerably broaden the appeal of MediaWiki to a new generation of internet users. The success of Wikia shows that there exists considerable demand for point-and-click wiki creation. It could also help drive third-party usage of VisualEditor / parsoid, if it is true that adoption is held back by anxiety over having to configure and maintain an additional software component.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374439020,PHID-USER-r7wrkcx7j2vutqs6hr3g,False,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_description,open
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,Bulk unassigning bugs from Ori.,1416260155,PHID-USER-ll6tmaogat2b5q7tnqas,False,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_subcomment,NA
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.],1378939555,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_subcomment,NA
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,"See also https://www.heroku.com/
+
+Juan,  I'll like what you're doing.  Emailing you.",1375133344,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_subcomment,NA
+Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally,"**jtreminio** wrote:
+
+Hi there, creator of PuPHPet here.
+
+We're actually actively working on providing ready-made quick-start configurations for some popular projects.
+
+Right now we have it done for Symfony2 (https://puphpet.com/quickstart/symfony) and for PuPHPet itself (https://puphpet.com/quickstart/puphpet).
+
+If I could be given your exact requirements I could easily whip something up for you :)",1374452121,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-mivgnyfxfz6yjozsfgrs,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"The ""clear formatting"" button returns bold and italic text to its plain state, as expected. However it also removes any links in the selection, which is not expected, rather there should be a separate ""unlink"" button to do this job - conceptually I regard a link as an attribute not as formatting.
+
+For example selecting a bolded sentence with an italicised title and a linked word in it. I clicked the clear formatting intending to clear the bold and italic, which it did but it also removed the link. Similarly if using it to remove a link it also removes bold/italic which is unlikely to be the intention.",1374344100,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3geuv3zh7grvfypwtx6m,task_description,declined
+VisualEditor: Clear formatting button should not remove links,*** Bug 70739 has been marked as a duplicate of this bug. ***,1410482044,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,*** Bug 59191 has been marked as a duplicate of this bug. ***,1390025103,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"(In reply to comment #4)
+> (In reply to comment #3)
+> > Also, removing a link takes three clicks if you don't use 'clear
+> > formatting'.
+>
+> Which is why I said there should be a separate button to remove
+> links with a single click.
+
+We're meant to be in the business of removing user confusion, not
+adding to it. More buttons make things harder to understand, in
+general. In this specific case I'm not sure.
+
+> > 'Clear markup' would be more descriptive, but probably less user-
+> > friendly.
+>
+> ""Clear markup"" doesn't describe what it does either, because it
+> doesn't remove paragraph style, text size, templates, colour, etc.
+> It only removes text formatting and links.
+
+Actually, this is wrong. Specifically, ""clear formatting"" removes
+everything that's an annotation (things that take text and fiddle with
+it in some way), and not objects or structure - in VisualEditor
+language, ""styles"".
+
+I.e., things that are removed:
+
+* Bold, italics, underlines, strikethrough, superscript, subscript,
+  code style
+* Text size (big/small and font-size attributes)
+* Rich text annotations - links, language (lang=""fr""), direction
+  (dir=""rtl""), …
+* Colours (foreground and background highlight) on text
+* Arbitrary paragraph settings (<span>s with style tags, etc.)
+
+… and things that remain:
+
+* Formats (paragraph/heading/preformatted/blockquote/…)
+* Structure (numbered list/bulleted list/definition list/table/…)
+* Objects (media items/galleries/transclusions/equations/…)
+
+> My point is that bold and italic, etc. are a subset of formatting,
+> but links aren't.
+
+In your meaning of the term ""formatting"". I don't use it that way, and
+neither do similar functions in other rich editors like Word or Google
+Docs, I believe.
+
+> I want the ability to remove formatting without removing links, and
+> the ability to remove links without removing formatting.
+
+I understand the request. :-) I just don't think that it's a need that
+is sufficiently widely-held that we should burden all users with an
+extra button and a confusing ""everything except not that one sorry""
+cognitive step.",1383006366,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"(In reply to comment #3)
+Also, removing a link takes three clicks if you don't use 'clear
+> formatting'.
+Which is why I said there should be a separate button to remove links with a single click.
+ 
+> 'Clear markup' would be more descriptive, but probably less user-friendly.
+""Clear markup"" doesn't describe what it does either, because it doesn't remove paragraph style, text size, templates, colour, etc. It only removes text formatting and links.
+
+My point is that bold and italic, etc. are a subset of formatting, but links aren't. I want the ability to remove formatting without removing links, and the ability to remove links without removing formatting.",1375800747,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"I agree that links are fundamental to Wikipedia (and other wikis).  However, I think it is quite reasonable that 'clear formatting' removes links.  If you want to remove something in particular, you can use the individual buttons (click bold to unbold, etc.) in most cases.
+
+Part of this is that I've already become used to using 'clear formatting' for links in VE.  But I don't think this seemed unintutive even when I started using VE.  Also, removing a link takes three clicks if you don't use 'clear formatting'.
+
+'Clear markup' would be more descriptive, but probably less user-friendly.",1375599397,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"Well ""superscript/subscript/underline/strikethrough/big/small/code
+formatting and <span>s setting arbitrary formatting annotations (like ""color:
+red;"" or ""font-family: serif;"" are all just different sorts of text decoration formatting like bold and italic so the clear formatting button is appropriate for all of them.
+
+""language settings (lang=fr and dir=rtl)"" are not in my mind the same thing as bold, strikethrough, etc, but equally they're not the same thing as links. I haven't thought about them before now and I at this point I just don't know what my opinion is and I don't really know what the arguments for an against are, so more thinking needed before I can you a proper answer for those, sorry.
+
+I think possibly the difference in our opinions about links is that you are approaching this from a ""make it like a popular word processor that can edit Wikipedia"" whereas I'm thinking of it from ""make it an editor for Wikipedia that works like word processors"". There might not sound much different in those philosophies, and in most cases I don't think there is. However from a word processing POV links are useful-to-have additional metadata, whereas from a Wikipeida editor POV links are fundamental to the structure and essence they don't conceptually fit with decoration.",1374821514,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Clear formatting button should not remove links,"This is exactly as designed. It also removes language settings (lang=fr and dir=rtl), superscript/subscript/underline/strikethrough/big/small/code formatting, and <span>s setting arbitrary formatting annotations (like ""color: red;"" or ""font-family: serif;"" or …). It's modelled against the same function in other editors, rendering the text down to completely plain text (except for objects like references or templates).
+
+Do you think each of these formatting options should have a ""remove"" function? Only some of them? Only those that trigger an inspector rather than just a boolean state (like links, language and arbitrary settings)? Only links? Why/why not? Happy to change direction but it would need to be a pretty strong reason to change (amongst other things, we'd need to give users ways to break out of the other kinds of pre-annotations as well as removing the selected annotation).",1374798885,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-3geuv3zh7grvfypwtx6m,task_subcomment,NA
+VisualEditor: Support for SFN and similar references,"One of the major advances in wiki editing in the last few years has been support for the short template-based referencing systems like SFN. I've made it a basic rule to use SFN if a reference is used more than twice within the article, and an inline only in the rare case where it is used once or twice. I realize my editing patterns are not normal, but I think support for these templated refs would improve the editor greatly. 
+
+Perhaps a ""toolbar-like"" editor to one side of the main editor could list of global references created so far, and allow the user to drag a handle from them into the article to place the ref in the body.
+
+Even better, perhaps the use could drag URLs or text into the bar to create semi-filled out master refs.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1374057780,PHID-USER-5tluooawvjfhtqywnxag,False,PHID-TASK-ksoksajvjcd37y5wvvq2,task_description,declined
+VisualEditor: Support for SFN and similar references,"JD, can you point to the ""as discussed previously""? I am not familiar with the problem, so do I understand why this would be a ""horrible hack"".",1442227600,PHID-USER-5tluooawvjfhtqywnxag,False,PHID-TASK-ksoksajvjcd37y5wvvq2,task_subcomment,NA
+VisualEditor: Support for SFN and similar references,"I guess I agree that it may not be worthwhile to support creating new footnotes with the [[https://en.wikipedia.org/wiki/Template:Sfn| shortened footnotes (SFN) template]]. 
+
+However, for the time being this system is still around on enwiki. And since this bug was filed, the citation reuse features was introduced in VE, and there it's an awkward and confusing user experience that one is not able to reuse already existing sfn footnotes. 
+
+Compare the list of footnotes offered for reuse in
+https://en.wikipedia.org/w/index.php?title=AI_winter&oldid=680877170&veaction=edit  (via ""Cite"" -> ""Re-use"")  with the actual [[https://en.wikipedia.org/w/index.php?title=AI_winter&oldid=680877170#Notes |list of footnotes in that article revision]]. The numbering is inconsistent, e.g. #7 (John Hutchins) in the article becomes #3 in VE, with the original footnots #3, #4, #5 and #6 mission. I had to search and think for a while to realize that I wasn't simply overlooking things and that the reason for the discrepancy is this template.",1442195570,PHID-USER-wlku5ja6envbi4cz2etp,False,PHID-TASK-ksoksajvjcd37y5wvvq2,task_subcomment,NA
+VisualEditor: Support for SFN and similar references,"Cite.php is designed a certain (bad) way. It has issues, and we will replace it at some point, but the way to fix its issues is not to make horrible hacks in wikitext using loopholes over-looked when the code was written to try to re-design in.
+
+This is one of those cases, and is not sanely supportable in VisualEditor, so I'm going to mark this as WONTFIX. I know I previously said ""lowest"", but I don't think that that's a justifiable direction for the product to go in.",1393541245,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ksoksajvjcd37y5wvvq2,task_subcomment,NA
+VisualEditor: Support for SFN and similar references,"As discussed previously, supporting this wikitext hack is exceptionally difficult to do, and it would be much more sensible to spend the effort on a proper cross-page, cross-wiki citations system instead which would solve the same problem (and lots more). However, it's not impossible, so keeping open as a lowest-priority enhancements.",1383281654,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ksoksajvjcd37y5wvvq2,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"Hi,
+
+a: Currently language list displayed below MediaWiki:Visualeditor-dialog-meta-languages-readonlynote/mr does not open the respective language wiki but when that is possible along with that respective language item ULS should offer option to open up the respective language wiki with related display and/or input .May be this shall need to mingle three extensions VE,wikidata,ULS and also
+
+b When in menubar languages displayed by wikidata if curser hover over any wiki language name options as requested in 4a should display and available. (Whether this needs to split as a separate 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_28864
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51431",1373886360,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-jfzrmnmoj3qahau2ohse,task_description,open
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"1(In reply to comment #6)
+> (In reply to comment #5)
+> However, is this a duplicate of bug 52383 maybe?
+
+::No not at all,if I have read bug 52383 correctly,it is asking to scrap certain feature made avaialable by VE by some frustrated user.Unless you are ready to scrap parts of VE design in that sense it is not an enhancement bug at all and most likely bug 52383 need to be wont fix
+
+
+* This bug 51355 assumes that any way you will be completeing the bug 52105. This bug is an enhancement over bug 52105 (So parsing job is happening at bug 52105)  and also expects bug 51431 enhancement also too take place.
+::In other words this bug 51355 wants to mount bug 51431 enhancement over bug 52105 enhancement.",1376726474,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"(In reply to comment #5)
+> *In VisualEditor - Toolbar -Page settings - language Section shows languages
+> heading with following message  
+> http://www.mediawiki.org/wiki/MediaWiki:Visualeditor-dialog-meta-languages-
+> section 
+> *Below this message  VisualEditor - Toolbar -Page settings - language Section
+> reproduces the same list of interwiki languages that I provided by Wiki data.
+> *Currently these language links are not parsed. 
+
+Not sure what you want to ""parse"" here, plus parsed by who?
+However, is this a duplicate of bug 52383 maybe?
+
+Please also update the bug summary to be descriptive. Thanks!",1376565627,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"I have split point b in a separate bug 51431.  
+
+
+*In VisualEditor - Toolbar -Page settings - language Section shows languages heading with following message  
+http://www.mediawiki.org/wiki/MediaWiki:Visualeditor-dialog-meta-languages-section 
+
+*Below this message  VisualEditor - Toolbar -Page settings - language Section reproduces the same list of interwiki languages that I provided by Wiki data.
+
+*Currently these language links are not parsed. 
+
+*This bug expects the same feature that is expected in bug 51431 but in context of Visual Editor toolbar -page settings languages",1374080554,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,...and please provide a bug summary that describes the actual feature request.,1374075864,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"Please provide exact and clear steps (click by click, as a numbered list) so anybody else could reproduce the problem, plus the expected and the actual outcome. I still don't know which page you are on, etc.
+See https://www.mediawiki.org/wiki/How_to_report_a_bug for general info.",1374075169,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"Created attachment 12860
+Request for Wikidata interwiki wikis to open with respective language ULS display and input
+
+**Attached**: {F11455}",1373971802,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+Feature request for VisualEditor language setting  +ULS +Wikidata interwikis,"Please provide a screenshot of the current problem that you would like to
+solve, plus a link to a wikipage where the problem can be seen. 
+Furthermore, please only file one problem per report. 
+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.",1373893720,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jfzrmnmoj3qahau2ohse,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"The ability to sign posts is useful outside of talk name spaces. For instance http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback is in project space. While that might one day be in flow there are many other project space items where  its useful to be able to sign. For instance lists of project members. Some uses have guest books in the User: space which can be signed. 
+
+You can't even enter them manually due to T51820.
+
+A button to insert this would be good, possibly done at the same time as bug 38029 which would insert symbols.
+ 
+This was discussed at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Let_me_sign.21
+
+----
+
+VisualEditor now allows you to insert signatures on pages that are in `$wgExtraSignatureNamespaces` (and any talk pages).
+
+This was previously implemented as a user script / gadget is available at https://meta.wikimedia.org/wiki/User:Matma_Rex/visualeditor-signature.js.",1373511180,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-kttslfnxq434mabydy2v,task_description,resolved
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"@Trizek-WMF Sure, I know, @Urbanecm told us the same on cswiki on community forum. I think we also have got on cswiki some bugs subpage under WP:Flow page, where all the bugs found are listed. I'll take a look into tasks I sent here, if there is another one I forgot to mention on that subpage.",1467125739,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"@Trizek-WMF Sure, I know, @Urbanecm told us the same on cswiki on community forum. I think we also have got on cswiki some bugs subpage under WP:Flow page, where all the bugs are listed. I'll take a look into tasks I sent here, if there is another one I forgot to mention on that subpage.",1467125678,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"@Dvorapa, please contact me if you have any suggestions about Flow bugs which need to be fixed.",1467110390,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,,1466612046,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,,1466604894,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,">>! In T53154#2399021, @Dvorapa wrote:
+> @Jdforrester-WMF I see, thank you. Still looking for a good talk solution - Flow is too buggy, VisualEditor is not really designed for discussions and wikitext is not easy to learn for novice users.
+
+I think getting the bugs in Flow fixed is the best option at this point, but I appreciate that there's a few things people would like to see added there.",1466602713,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"@Jdforrester-WMF I see, thank you. Still looking for a good talk solution - Flow is too buggy, VisualEditor is not really designed for discussions and wikitext is not easy to learn for novice users.",1466602589,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,">>! In T53154#2398111, @Dvorapa wrote:
+> Is there any option how to add a signature button to the main VE bar (e.g. instead of the special symbol button or next to?) (discussed on cswiki; just asking if possible)
+
+This is not possible. We intentionally do not allow the toolbar to vary in the position of buttons on the same wiki.",1466602060,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,Is there any option how to add a signature button to the main VE bar (e.g. instead of the special symbol button or next to?) (discussed on cswiki; just asking if possible),1466559576,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Is there any option how to add a signature button to the main VE bar (e.g. instead of the special symbol button or next to?) (cswiki; in discussion, just asking if possible)",1466559547,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,Is there any option how to add a signature button to the main VE bar (e.g. instead of the special symbol button or next to?),1466559506,PHID-USER-dcexrhjioxqqsq4pdrfe,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Change 251834 merged by jenkins-bot:
+Provide a tool to insert a signature in namespaces that need it
+
+[[https://gerrit.wikimedia.org/r/251834]]",1447719403,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Change 251834 had a related patch set uploaded (by Bartosz Dziewoński):
+Provide a tool to insert a signature in namespaces that need it
+
+[[https://gerrit.wikimedia.org/r/251834]]
+",1447004908,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Hmm, and so it seems that the $wgExtraSignatureNamespaces functionality provided by https://gerrit.wikimedia.org/r/87649 (T7645) was actually merged, even thought it looked hopeless a year ago. I think we can go ahead with migrating my gadget to VisualEditor proper, and enabling the signature inserting tool only in those namespaces.",1441556932,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,">>! In T53154#1138179, @Juandev wrote:
+> Thank you for the code. Could the user also add a special button to VE or is it a difficult cooding? 
+
+Per the task description and per my previous comment, there is a gadget that implements this that you can easily enable for yourself, or on your wiki.",1426958719,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,,1426958667,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,,1426958656,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,">>! In T53154#537004, @AdHuikeshoven wrote:
+> Adding a signature with VisualEditor can be simulated using a template:
+> 
+> ---template code:---
+> {{{Sign}}}
+> <noinclude>
+> This template allows to sign using Visual Editor by adding this template as you can't enter four tildes <nowiki>~~~~</nowiki> in VE. Enter the template in VE. Hit Add template. Enter <nowiki>~~~~</nowiki> in the field. Hit Insert template. Hit Save page. Enter edit summary. Hit Save. Doone.</br>
+> <templatedata>
+> {
+> 	""description"": ""A template to sign using Visual Editor. "",
+> 	""params"": {
+> 		""Sign"": {
+> 			""aliases"": [
+> 				""Signature""
+> 			],
+> 			""label"": ""Sign by entering ~~~~ in the field below"",
+> 			""description"": ""Field to enter signature, that is four tildes"",
+> 			""default"": ""Please enter four tildes here"",
+> 			""required"": true
+> 		}
+> 	}
+> }
+> </templatedata>
+> </noinclude>
+> ---end of template code---
+> 
+> Usage:
+> Enter the template in VE. Hit Add template. Enter ~~~~ in the field. Hit Insert template. Hit Save page. Enter edit summary. Hit Save.
+> 
+> Example:
+> See https://www.mediawiki.org/wiki/Template:VESign. Application of template tested on https://www.mediawiki.org/wiki/User:Ad_Huikeshoven/test. 
+> 
+> Evaluation:
+> There might be nicer methods to accomplish the same, maybe using JS (I have no experiene writing JS). When there is a switch over to Parsoid rendering the templates mid-edit rather than relying on PHP parser the above solution will probably break, as will probably do any solution to bug 51146.
+
+Thank you for the code. Could the user also add a special button to VE or is it a difficult cooding? ",1426954578,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,I updated the description with information about the gadget implementing this feature.,1425561628,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,@Pine: Yes I'd object. :) Please see T53154#536989,1425558453,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,Would anyone object to bumping up the priority of this to normal?,1425544467,PHID-USER-l7v72q5tq6vg6zclrld6,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Like @AdHuikeshoven, I just ran into the use case where I can't sign myself to a list of Wikimania talk attendees.",1425083820,PHID-USER-p6hvqn5njgnxuagekh4b,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Yes, I've moved it to talk space. Sorry I didn't catch that earlier.",1412362166,PHID-USER-l7v72q5tq6vg6zclrld6,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to Pine from comment #22)
+> Perhaps someone enabled VE on talk pages when they shouldn't have?
+> 
+> It's enabled on https://meta.wikimedia.org/wiki/Grants:APG/Comments
+
+Argh. That's not a talk page. You can tell because the talk page would be https://meta.wikimedia.org/wiki/Grants talk:APG – this is really unhelpful of people to use the wrong namespace. I'm sorry about that. :-(",1412362031,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Ah, I see. That's not really labeled as a talk page on Meta, but it probably should be. I'll try to take care of that.",1412362011,PHID-USER-l7v72q5tq6vg6zclrld6,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Perhaps someone enabled VE on talk pages when they shouldn't have?
+
+It's enabled on https://meta.wikimedia.org/wiki/Grants:APG/Comments",1412361949,PHID-USER-l7v72q5tq6vg6zclrld6,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to Pine from comment #20)
+> I am raising the priority of this bug. VisualEditor is now enabled for talk
+> pages on Meta, yet I can't insert my signature using VisualEditor, which is
+> a major shortcoming. Please fix!
+
+What talk pages is it enabled for? Can you give an example? It doesn't appear on the talk pages I just looked at. This feels like a distinct bug.
+
+Please read the history of this bug for why this is explicitly outside of the plans for VisualEditor; it's fundamentally the wrong approach. Resetting priority.",1412361791,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"I am raising the priority of this bug. VisualEditor is now enabled for talk pages on Meta, yet I can't insert my signature using VisualEditor, which is a major shortcoming. Please fix!",1412361008,PHID-USER-l7v72q5tq6vg6zclrld6,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"It seems that bug 5645 which I thought to be a dependency is not going to be fixed in a useful way. The only way to proceed would be reimplementing the namespace selection logic in VE, which I'm wary of. I don't know how to proceed with this, I guess we'll be stuck with the gadget for the time being.",1406412781,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Actually, a $wg config variable for this is not a very good idea. We should just be smart and display the signature button in the namespaces that need it (and no others).
+
+Core MediaWiki currently has no way to do this (other than the implied assumption that all talk namespaces need signatures), but there happens to be a patch pending that would introduce one (https://gerrit.wikimedia.org/r/87649). We should just wait for that to be implemented, and then use the same logic as wikitext editor when deciding whether to enable signatures or not.",1405887415,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to Bartosz Dziewoński from comment #16)
+> That sounds fine by me. So it would be enabled with a $wg config variable?
+
+That was my thought, yes.
+
+> I wonder if it would make sense to let users enable it for themselves (by
+> loading a RL module in common.js, for example).
+
+It doesn't; either VE namespaces are signable or they're not. A per-user setting doesn't make sense.
+
+""Assigning"" to Bartosz given he's done all the work here. :-)",1405787749,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"That sounds fine by me. So it would be enabled with a $wg config variable?
+
+I wonder if it would make sense to let users enable it for themselves (by loading a RL module in common.js, for example).",1405775648,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to Lokal_Profil from comment #14)
+> Being a basic building block of a wiki which is currently missing from VE I
+> would not mark this as Resolved until there is a solution integrated in VE.
+> Better then to leave it open and hope that some volunteer takes it on if it
+> is deemed to be outside of the scope for Wikimedia to implement.
+
+There is never going to be a ""sign post"" feature integrated into VisualEditor as deployed on WMF servers. That's the whole point of Flow. From a perspective of ""VisualEditor for WMF users"", this is WONTFIXed.
+
+This bug is not marked as ""WONTFIX"" though, because it's entirely plausible that someone might want to run VisualEditor on a wiki without Flow (or LQT or Message Wall or whatever).
+
+Maybe we should bundle up Bartosz's code into a VE plug-in that's available for users (but not on by default)?",1405474400,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Being a basic building block of a wiki which is currently missing from VE I would not mark this as Resolved until there is a solution integrated in VE. Better then to leave it open and hope that some volunteer takes it on if it is deemed to be outside of the scope for Wikimedia to implement.
+
+Adding a signature should be as easy or easier (for the user) as adding an image or template. Also since there is nothing preventing signatures from being added to any namespace in the wikitext editor there should be no hard-coded exceptions in the VE-solution (although there could of course be site-wide setting disallowing them.",1405344964,PHID-USER-uu7wg6g3b37dcktbje3a,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"I wonder what should we do with this bug? I think it should be marked either RESOLVED WONTFIX or RESOLVED FIXED, but I'm not sure which is more appropriate.",1405339051,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,I replied at [[meta:User talk:Matma Rex/visualeditor-signature.js]].,1405338928,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to SJ from comment #3)
+> I think it is important to enable signatures in VE.  I have found it useful
+> in a few circumstances; and regretted having to drop out of VE just for that
+> one addition.
+
+The use case I would like mention is adding your name to the list of interested attendees at the program pages of https://wikimania2014.wikimedia.org/. Bartosz tools works wonderfully outside content name space. However, it explicitly doesn't work on content name space in which the program pages at the Wikimania site reside.",1405327655,PHID-USER-mcyovqjor52nj3se4lq7,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Whoa, that's scary. Please don't do that.
+
+I wrote a script to implement signatures properly. This definitely isn't what the editor was designed to do, but, as it was noted in earlier comments, this has its use cases.
+
+https://meta.wikimedia.org/wiki/User:Matma_Rex/visualeditor-signature.js
+
+Please comment about it on the script's talk page, not here :) I'd be happy to include more translations (there are just two words to translate).
+
+I think the only thing missing is an icon that would match the look-and-feel of existing ones. I'd be happy to add it, too, if only someone drew one (SVG).",1405303431,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Adding a signature with VisualEditor can be simulated using a template:
+
+---template code:---
+{{{Sign}}}
+<noinclude>
+This template allows to sign using Visual Editor by adding this template as you can't enter four tildes <nowiki>~~~~</nowiki> in VE. Enter the template in VE. Hit Add template. Enter <nowiki>~~~~</nowiki> in the field. Hit Insert template. Hit Save page. Enter edit summary. Hit Save. Doone.</br>
+<templatedata>
+{
+	""description"": ""A template to sign using Visual Editor. "",
+	""params"": {
+		""Sign"": {
+			""aliases"": [
+				""Signature""
+			],
+			""label"": ""Sign by entering ~~~~ in the field below"",
+			""description"": ""Field to enter signature, that is four tildes"",
+			""default"": ""Please enter four tildes here"",
+			""required"": true
+		}
+	}
+}
+</templatedata>
+</noinclude>
+---end of template code---
+
+Usage:
+Enter the template in VE. Hit Add template. Enter ~~~~ in the field. Hit Insert template. Hit Save page. Enter edit summary. Hit Save.
+
+Example:
+See https://www.mediawiki.org/wiki/Template:VESign. Application of template tested on https://www.mediawiki.org/wiki/User:Ad_Huikeshoven/test. 
+
+Evaluation:
+There might be nicer methods to accomplish the same, maybe using JS (I have no experiene writing JS). When there is a switch over to Parsoid rendering the templates mid-edit rather than relying on PHP parser the above solution will probably break, as will probably do any solution to bug 51146.",1405282624,PHID-USER-mcyovqjor52nj3se4lq7,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"To clarify, this is a ""WONTFIX"" for VE as it is (and will be) enabled on WMF projects, but if someone wants to write a plugin for VE for other wiki hosts using it that want to try to make VE work in discussion namespaces (and don't want to use Flow).
+
+There are a number of meanings of ""Lowest"" priority, and this is one of the confusing ones. Sorry. :-(",1390430037,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"(In reply to comment #6)
+> Will Flow be applicable to all namespaces? There are lots of article-style
+> pages that temporarily or permanently would benefit from inline comments in
+> the
+> middle of what is otherwise a full-text long-form page.  In those cases* I
+> don't see how the Flow design will help.
+
+Like what? Some examples, please?
+
+> 
+> Signatures are useful in most namespaces, whereas ""idiosyncratic protocols
+> and
+> templates and formats"", with unknown amounts of associated work, seem like
+> higher-hanging tasty fleshy vegetalia.
+> 
+Sure, and work on those namespaces is best done when we actually discuss _deploying_ in those namespaces - and when it is fully working for the primary target of the VE (i.e., the mainspace).
+
+> * Examples: wikis that don't separate talk from content; wikis that have two
+> layers of talk: limited inline v. permanent talk-threads; articles or main
+> pages that tabulate membership or participation or otherwise include tables
+> that include user signatures.
+
+Actual examples for each example...?",1390426187,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"Will Flow be applicable to all namespaces? There are lots of article-style pages that temporarily or permanently would benefit from inline comments in the middle of what is otherwise a full-text long-form page.  In those cases* I don't see how the Flow design will help.  
+
+Signatures are useful in most namespaces, whereas ""idiosyncratic protocols and templates and formats"", with unknown amounts of associated work, seem like higher-hanging tasty fleshy vegetalia.
+
+* Examples: wikis that don't separate talk from content; wikis that have two layers of talk: limited inline v. permanent talk-threads; articles or main pages that tabulate membership or participation or otherwise include tables that include user signatures.",1390423793,PHID-USER-fgzcdbj3je3ksnhufo47,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"That's probably something to do with the fact that the VE isn't really being used in discussion namespaces.
+
+This is not, by far, the only feature blocking VE from being useful in many other contexts. A lot of the discussion namespaces have their own idiosyncratic protocols and templates and formats that parsoid and the VE will then have to directly support, which is likely to be some (unknown) additional amount of work, and that'll all be done just in time for us to start releasing Flow, which does auto-signing.
+
+I can understand the low prioritisation ;).",1390420131,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,I just noticed this is flagged as lowest-priority enhancement... again surprising considering the importance and prevalence of signing in wiki culture and other MW docs.,1390419820,PHID-USER-fgzcdbj3je3ksnhufo47,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"I think it is important to enable signatures in VE.  I have found it useful in a few circumstances; and regretted having to drop out of VE just for that one addition.
+
+This is the only feature blocking VE from being useful in a much wider variety of contexts, in my opinion.  (And it's odd for all sig options to be missing when reminders about how to sign and where to sign are some of the most prominent in the MediaWiki interface otherwise.)",1390419772,PHID-USER-fgzcdbj3je3ksnhufo47,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Let_me_sign.21
+
+^Updated link",1373787620,PHID-USER-kmbrbjm7jackp4nrang3,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+VisualEditor: Provide a tool to insert a talk signature in namespaces that need it,"The VisualEditor isn't going to be in project space at any point in the near future, however.",1373571593,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-kttslfnxq434mabydy2v,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","**Author:** `mcdevitd`
+
+**Description:**
+""Preformatted"" is HTML jargon which most of VisualEditor's target users will not understand, and it actually produces an effect (text with less formatting) which is unexpected if you don't know what it means beforehand. It should either be given a plain-language name so that people will expect the behavior, or removed.
+
+I actually don't understand why this style effect is in the header-level pull-down when it is not a header-level. My preference is to remove it, since it is uncommon and mostly adding noise, but it should be renamed if kept.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373247780,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_description,open
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","Also, a dictionary cite for usage of ""pre-formatted"": http://www.oed.com/view/Entry/149454?rskey=n6kMKv&result=2&isAdvanced=false#eid51449481 (not that it gives a definition or synonym we could use).",1394476377,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","(In reply to Dominic from comment #7)
+> (In reply to James Forrester from comment #6)
+> > (In reply to MZMcBride from comment #5)
+> > 
+> > I'm inclined to WONTFIX at this point…
+> 
+> I was under the impression that VisualEditor was about removing jargon
+
+Sort-of.
+
+Actually, it's about making it easy to edit content.
+
+
+> and unneeded advanced features that clutter the user experience.
+
+No.
+
+In meeting the ""making it easy to edit content"" objective, we can't rope off some content that is considered ""too difficult"" to explain nicely.
+
+
+> All three of the other commenters here agreed that ""Preformatted"" is jargon
+> that should at least be renamed using plain language.
+
+Sure, but no-one has actually suggested something they think is better yet (Chris suggested ""monospace"", but said he didn't like it, and I somewhat agree). Until such time as someone suggests a better term, this is unfixable.
+
+
+> And it's not really even clear why we expect ""preformatted"" to be a common
+> enough formatting choice among VisualEditor users that it even merits the
+> inclusion in that menu.
+
+That's a more interesting question, yes, as I said in comment 6. But that's not what other people's comments on this bug have been about.
+
+
+> Your comment on WONTFIXing the report doesn't address the actual problem
+> being raised.
+
+Pick one. Either this bug is about removing ""preformatted"" as an option, in which case WONTFIX stands, or it's about something else (""come up with a different name""? ""have a secondary system for less-common formats""? something else?) and make it about that?
+
+
+
+(In reply to MZMcBride from comment #8)
+> Eh, this is a bad wontfix. My dictionary doesn't contain ""preformatted""; we
+> can probably come up with a better term.
+
+See above.
+
+
+> Regarding the user interface, it's a bit confusing why there's a text
+> formatting menu (paragraph text and headings) next to another text
+> formatting menu (bold, underline, computer code, etc.). It might make sense
+> to move the artist currently known as preformatted to the bottom of the
+> latter menu as it's not very commonly needed (about as commonly needed as
+> needing to write ""computer code"" using VisualEditor, surely).
+
+It's formatting vs. styling; one operates on paragraphs, the other on selections (which can be smaller than a paragraph). I agree that it's confusing (yay HTML and MediaWiki), but I think it would be more confusing to have things in the same menu that do radically different things without distinction.",1394475244,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","Eh, this is a bad wontfix. My dictionary doesn't contain ""preformatted""; we can probably come up with a better term.
+
+Regarding the user interface, it's a bit confusing why there's a text formatting menu (paragraph text and headings) next to another text formatting menu (bold, underline, computer code, etc.). It might make sense to move the artist currently known as preformatted to the bottom of the latter menu as it's not very commonly needed (about as commonly needed as needing to write ""computer code"" using VisualEditor, surely).",1393989052,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","**mcdevitd** wrote:
+
+(In reply to James Forrester from comment #6)
+> (In reply to MZMcBride from comment #5)
+> 
+> I'm inclined to WONTFIX at this point…
+
+I was under the impression that VisualEditor was about removing jargon and unneeded advanced features that clutter the user experience. All three of the other commenters here agreed that ""Preformatted"" is jargon that should at least be renamed using plain language. And it's not really even clear why we expect ""preformatted"" to be a common enough formatting choice among VisualEditor users that it even merits the inclusion in that menu.
+
+Your comment on WONTFIXing the report doesn't address the actual problem being raised.",1393987799,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","(In reply to MZMcBride from comment #5)
+> Should this bug report continue to be assigned?
+> 
+> I think a mock would help here.
+
+A mock of what? Moving some (but not all) paragraph-level formats somewhere else seems like a really bad design. We'd be talking about pre-formatted, blockquote, and maybe other like poem and so-on being in one menu, and other tools that operate in the exact same way (e.g. don't apply to a selection). I'm inclined to WONTFIX at this point…",1393527782,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","Should this bug report continue to be assigned?
+
+I think a mock would help here.",1392360410,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","Now that we have the ""more"" menu I don't think the button issue exists (to the same degree at least) as it did.
+
+As the ""preformatted"" name I agree it doesn't make sense, as this isn't really what it does. I was going to suggest ""monospaced"" but it's more than that - it's monospaced and indented with a shaded background. However, <code> also produces monospace and a shaded background but that is different.",1379693519,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","**mcdevitd** wrote:
+
+My confusion came from the fact that the user guide refers to it as the ""Headings pull-down menu"" (http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/User_guide#Getting_started:_the_VisualEditor_toolbar), and every other option in the menu is a heading level (or no level), not a style.
+
+If there is somewhere else where styles like pre are going to go, or you intend to add other styles to this same menu, that's fine with me, but my original point about it being jargon still stands. (Though if you add more style options to the same menu, I think that is even more reason to remove pre as noise.)",1373524183,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","This isn't a ""header pull-down menu"", it's a text style menu. Also, having yet another control in the toolbar (for blockquote, pre and whatever else) doesn't feel great. :-(",1373504408,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+"VisualEditor: Come up with a different name for ""Preformatted"" in the text formatting menu","I agree.
+
+It's strange that it's currently in the header menu. A separate menu for <blockquote> and <pre> may make sense.",1373282762,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-pdpuwrbqccg6nncfnxuk,task_subcomment,NA
+VisualEditor: Remove Opera from blacklist,"I think we can (almost) remove Opera from the blacklist now, see blocking bug 36000. Opera < 12 should still probably be blacklisted, though, and < 10 should be blacklisted for sure (there's a bunch of people who insist that 9.64 was the ultimate version ever and stick to it).
+
+It'd be cool if it could be added to the whitelist as well, but I guess that would be a promise to support it and you guys probably don't want to promise that ;)
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1373044680,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g36wsrlii3gd62hxtn2u,task_description,resolved
+VisualEditor: Remove Opera from blacklist,It was unblacklisted in the now-merged Ia80a6f53.,1375135090,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g36wsrlii3gd62hxtn2u,task_subcomment,NA
+VisualEditor: Remove Opera from blacklist,"(In reply to comment #2)
+> Note that the Presto engine-based Opera 12.x is being end-of-lined; the new
+> Opera 15 is Chromium-based.
+
+There is no release date or anything apart from a very early alpha of Opera 15 (which basically does nothing apart from showing pages). I'd say Opera 12 still has a bit of time before it.
+
+
+> Is it worth worrying about Opera 12.x compatibility?
+
+Still, objectively, maybe it's not. But I care personally. :)",1373052515,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g36wsrlii3gd62hxtn2u,task_subcomment,NA
+VisualEditor: Remove Opera from blacklist,"Note that the Presto engine-based Opera 12.x is being end-of-lined; the new Opera 15 is Chromium-based.
+
+Is it worth worrying about Opera 12.x compatibility?",1373046513,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-g36wsrlii3gd62hxtn2u,task_subcomment,NA
+VisualEditor: Remove Opera from blacklist,"(In reply to comment #0)
+> I think we can (almost) remove Opera from the blacklist now, see blocking bug
+> 36000. Opera < 12 should still probably be blacklisted, though, and < 10
+> should
+> be blacklisted for sure (there's a bunch of people who insist that 9.64 was
+> the
+> ultimate version ever and stick to it).
+> 
+> It'd be cool if it could be added to the whitelist as well, but I guess that
+> would be a promise to support it and you guys probably don't want to promise
+> that ;)
+
+Very happy to add to the whitelist if you're sure that everything works perfectly. It's not a state a browser can only reach if supported by WMF, if you want to commit to doing that. The comprehensive testing is quite a high bar, however - does Opera now cope with everything at mediawiki.org/wiki/VisualEditor/Basic_example_worksheet ?",1373046107,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g36wsrlii3gd62hxtn2u,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,"Because.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1373035320,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-eulhe75w7cy7if64iutj,task_description,declined
+VisualEditor: VisualEditor needs easter eggs,"Call me boring, but… :-)",1393642162,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,"(In reply to comment #4)
+> Articles mysteriously being littered with ♙ and ☃ doesn't count? :-)
+
+No :P",1383332239,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,Articles mysteriously being littered with ♙ and ☃ doesn't count? :-),1383324321,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,,1373035563,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,"Maybe it already has them, and we're just not cool enough to know...",1373035520,PHID-USER-2nnm76h4ykalvvref2ye,False,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+VisualEditor: VisualEditor needs easter eggs,Maybe you're just not looking hard enough,1373035486,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-eulhe75w7cy7if64iutj,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"When you add a new citation in VE, templates which wrap the `<references />` tag do not update to display it until the page is saved. Examples include [[https://en.wikipedia.org/wiki/Template:Reflist|`{{reflist}}`]] on the English Wikipedia and [[https://es.wikipedia.org/wiki/Plantilla:Listaref|`{{listaref}}`]] on the Spanish Wikipedia. This bug doesn't block any of the core citation workflows (creating, editing, and reusing) since those are accessed from the toolbar and the in-text reference numbers, but it's still very annoying. 
+
+However, it remains unfixed because it's an //extraordinarily// hard technical challenge, verging on impossible given the current architecture of Mediawiki. No one has any idea what a workable solution would look like. Just to give one facet of the problem, you could implement this in VE right now //if// you completely re-parsed the entire page every time the user touched a template or a reference—which would be a //horrible// user experience and place //insane// loads on the servers. It's possible that in the future, someone will think up a brilliant solution that avoids all these huge issues, so this task remains open.
+
+In the meantime, the planned solution is to update the `<references />` tag, which does update properly during editing, to support multiple columns and alternative list styles so they have all the functionality of these templates (T53260). When that task has been completed, communities will be able to replace the templates with references tags at whatever pace and with whatever tools they prefer (if there's demand for it, it would probably be possible to do a more immediate, bot-driven changeover).
+",1372969200,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_description,resolved
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Thank you.
+",1518731537,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Thanks, I've filed T187495.",1518726539,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,">>! In T52769#3975407, @Esanders wrote:
+> Can you link to an example?
+Sure:
+https://he.wikipedia.org/wiki/%D7%90%D7%93%D7%99_%D7%A7%D7%91%D7%98%D7%A0%D7%A8?veaction=edit&uselang=en",1518706913,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,Can you link to an example?,1518702862,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Hi. Our wiki does not show any references in reflists at all in VE now, the list is empty. All of them are created by reference template, rather than by tag. I was not sure it's new indeed, because I do not use VE, but people say it wasn't like this before.
+",1518653027,PHID-USER-t7ue4j3fnqznjjs4z5ef,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Change 408604 **merged** by jenkins-bot:
+[mediawiki/extensions/Cite@master] Treat template-generated reference lists as real ones
+
+[[https://gerrit.wikimedia.org/r/408604]]",1518112687,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"Change 408604 had a related patch set uploaded (by Esanders; owner: Esanders):
+[mediawiki/extensions/Cite@master] Treat template-generated reference lists as real ones
+
+[[https://gerrit.wikimedia.org/r/408604]]",1517948195,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,">>! In T52769#541738, @Jdforrester-WMF wrote:
+> Note that we can't currently see a way to do this without round-tripping the entire page, which would be a sub-optimal solution, to put it mildly.
+
+So, if <references/> directly on the page are supposed to work (they're updated on edit) but when they're inside a template not, it should be possible to make parsoid tag the template with a special property so only that template region gets updated (or the references list) and not the entire page. Note that I'm speaking without knowledge about how the entire thing works.",1467209234,PHID-USER-jnta3z3spxto3vbxdngm,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"So to clarify, it is a known bug that adding references will display the updated reference list when the <references /> tag is used in the article, but not when the {{reflist}} template is used?",1405248457,PHID-USER-evd3wnvnlb66lrwulch4,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,*** Bug 51607 has been marked as a duplicate of this bug. ***,1374167787,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+Adding or updating a reference in VisualEditor does not update fake references blocks inside templates,"(In reply to comment #0)
+> What it says on the tin; the addition of a reference is not reflected in an
+> update to {{reflist}} or <references/> or whathaveyou.
+
+I can't replicate the bug as described, but re-purposing to be about our desire to update fake reference lists inside templates on edit, rather than the current unhelpful not-updated-'til-page-save issue.
+
+Note that we can't currently see a way to do this without round-tripping the entire page, which would be a sub-optimal solution, to put it mildly.",1373163815,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-kloqgpjwhtcokmj7eica,task_subcomment,NA
+VisualEditor: Editing tool to changing case,"A user has requested a tool to alter the case of text that has been typed. Marking as lowest priority, since we've made clear it's not something anyone is likely to work on any time soon.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T55210}
+{T52678}
+{T55495}
+{T52452}",1372943460,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-w4y2nb4727kwbhfjqdup,task_description,open
+VisualEditor: Editing tool to changing case,https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Editing/Case_conversion,1651251693,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-w4y2nb4727kwbhfjqdup,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Occasionally wiki links are being mangled adding ./ to the start and replacing spaces with underscores. For example replacing [[specific name (zoology)|specific epithet]] with [[./Specific_name_(zoology)|specific epithet]]. I've only noticed it with piped links.
+
+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)
+
+possibly related to bug 50428
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=50539
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48769",1372919760,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-tyu752voayr4g6elcmgx,task_description,resolved
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Can no longer reproduce the test case given by Erik in FF13/14. Edited the link directly to avoid SelSer.
+
+https://en.wikipedia.org/wiki/HELLP_syndrome?veaction=edit&vewhitelist=1
+
+{F4089820}",1464692505,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them",">>! In T52720#2164275, @Schnark wrote:
+> Should this task just be closed? I don't think anyone is going to put work into supporting  these really old Firefox versions.
+
+I've been keeping this open as we //would// accept any patch doing this. Yes, there are relatively very few users, but it's not great to leave these users without an editor over something that's effectively trivial.",1459413492,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them",Should this task just be closed? I don't think anyone is going to put work into supporting  these really old Firefox versions.,1459413067,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Just wondering, has anybody tested VE on those old Firefoxes somewhat recently? The codebase is changing so fast this might as well be magically fixed now.",1379263769,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","(In reply to comment #11)
+> I think you viewed this bug solely as a blocker to bug 50848. I agree that it
+> no longer is, but I don't believe this bug is now resolved/fixed. The issue
+> hasn't been fixed, as I understand it, just worked around. I'm re-opening the
+> bug, but removing bug 50848 as a blocker, lowering the importance fields, and
+> clarifying the bug summary.
+
+Well, had you given me more than 30 seconds I was in the middle of creating a new bug, but never mind. :-) Repurposing this one.",1373502359,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","I think you viewed this bug solely as a blocker to bug 50848. I agree that it no longer is, but I don't believe this bug is now resolved/fixed. The issue hasn't been fixed, as I understand it, just worked around. I'm re-opening the bug, but removing bug 50848 as a blocker, lowering the importance fields, and clarifying the bug summary.",1373502220,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","We believe that this should not recur due to the (hopefully-temporary) blacklisting of Firefox 13 and 14, which is now live in production. Consequently, I'm marking this bug as fixed. Please re-open if you find it happening again.",1373501510,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Change 72675 merged by jenkins-bot:
+Blacklist Firefox 13 and 14 too
+
+https://gerrit.wikimedia.org/r/72675",1373334336,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Change 72675 had a related patch set uploaded by Jforrester:
+Blacklist Firefox 13 and 14 too
+
+https://gerrit.wikimedia.org/r/72675",1373332958,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them",Can reproduce in Firefox 13 and 14; cannot reproduce in 15 or 17 or 20. Interestingly in Firefox 13 I get a little bit more normalization in the diff as well. Looks like we get more progressively more broken the further down we go. :P,1373135486,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Confirmed in Firefox 14. Steps to reproduce:
+
+1) Open https://en.wikipedia.org/wiki/HELLP_syndrome?veaction=edit as a logged in user
+
+2) Make an unrelated edit
+
+3) Press ""Save"" and ""Review your changes"".
+
+The link [[Right upper quadrant (abdomen)|right upper quadrant]] is transformed to [[./Right_upper_quadrant_(abdomen)|right upper quadrant]].",1373134893,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","According to https://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07#VE_zerschie.C3.9Ft_Kats_und_Wikilinks this seems to be an issue in old Firefox: FF14 inserted the ./, while FF22 didn't.",1373097754,PHID-USER-tyjmn7xcw6s2b6rqagj7,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","I think it might be to do with having punctuation in the links in this edit
+https://en.wikipedia.org/w/index.php?title=Soccer_in_the_United_States&diff=prev&oldid=563041224
+this the links which have ' or ( in them which get mangled other links are ok so
+[[United States men's national soccer team|men's national team]] gets changed to 
+ [[./United_States_men's_national_soccer_team|men's national team]] but [[FIFA World Cup|World Cup]] is unchanged. And [[National Professional Soccer League (1967)|National Professional Soccer League]] is changed to [[./National_Professional_Soccer_League_(1967)|National Professional Soccer League]].",1373089586,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","(In reply to comment #1)
+> Escalating priority. Additional example:
+> 
+> https://en.wikipedia.org/w/index.
+> php?title=OMICS_Publishing_Group&curid=35277259&diff=562944992&oldid=56157968
+> 0
+I can't reproduce this, and can in fact edit the page just fine: https://en.wikipedia.org/w/index.php?title=OMICS_Publishing_Group&diff=563024944&oldid=562947045
+
+This bug must have some particularly nasty cache persistence properties; we've purged the Parsoid caches but that doesn't seem to have made it go away.",1373059132,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them",*** Bug 50539 has been marked as a duplicate of this bug. ***,1373020641,PHID-USER-7hrs7wwclcldf7mm6a7o,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+"VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them","Escalating priority. Additional example:
+
+https://en.wikipedia.org/w/index.php?title=OMICS_Publishing_Group&curid=35277259&diff=562944992&oldid=561579680",1373011178,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-tyu752voayr4g6elcmgx,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"Enhancement request for more informative error messages - as simple as ""Syntax error in JSON on line foo."" would be better than the current message, which is just ""Syntax error in JSON.""
+
+| {F34099979} | {F34099994}",1372704060,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_description,open
+TemplateData: Get better error messages for JSON syntax errors,"While I agree this is a valid feature request, I'm afraid there isn't much we can do at this point. I tried to annotate the generic error message with what `json_last_error_msg()` reports. All it says is ""Syntax error"". 😞 We would need to use another JSON parser to fulfill this feature request. That's unlikely to happen.",1638173623,PHID-USER-u6ycqhfpa3k4yvlpxjt2,False,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"This is not the same issue as T256574.
+
+
+T256574 is about the error message when clicking the ""Manage TemplateData"" button to open the ""Template documentation editor"" dialog:
+| {F34099977} | {F34099996}
+
+This is about the error message when clicking ""Publish changes"": (currently this error doesn't appear at all, that's yet another separate issue filed as T258790)
+| {F34099979} | {F34099994}",1612991707,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"(In reply to comment #2)
+> Presumably this could be done if bug 50169 was implemented, though. :-)
+
+Well, in case of bug 50169 (VisualEditor plugin for TemplateData) there would never be a syntax error in the JSON because the user wouldn't be editing it directly. They'd be using a form-like interface to interact with it (VE would generate the JSON which is always valid).
+
+However if the VE plugin would have a raw mode to edit the JSON (e.g. using an Ace surface like Extension:CodeEditor does), we could use its JSHint integration to get inline errors by line/char highlighting (e.g. like in Sublime).",1381079222,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"For the moment, you can use TemplateDataEditor to be able to create the <templatedata/> without editing any real JSON.
+
+http://en.wikipedia.org/wiki/User:NicoV/TemplateDataEditor",1374506154,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"**weskaggs** wrote:
+
+Displaying the contents of the line at which an error is detected, with a few lines around it for context, would be almost as useful as a line number.  Of course the actual error can be a long way off from the point at which a syntax error is detected, but the information would still be helpful.  Adding information about the type of error would make it even better.  Really any information at all about the nature of the error would be an improvement.",1372774985,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"Presumably this could be done if bug 50169 was implemented, though. :-)",1372734893,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+TemplateData: Get better error messages for JSON syntax errors,"It is in my opinion not feasible to get line numbers because we use a native PHP extension to parse the JSON.
+
+If the JSON syntax itself is invalid, there is nothing we can do. Best case scenario the parser gives the type of error (""Unexpected comma"", ""Expected closing curly brace"" etc.) but a line number is unlikely.
+
+Once the JSON is parsed, the TemplateData validation itself (e.g. sets referring to existing parameters) we have full control over and gives pretty informative errors with the full path to the property.
+
+> Unexpected property ""params.user.blabla"".
+> Property ""params.timestamp.description"" is expected to be of type ""string|object"".
+
+etc.",1372711992,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-n2g6v2vrtf3k3hkqsoi3,task_subcomment,NA
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"Until a recent MediaWiki change the default behavior of edit section links was to float to the far side of the heading (right on LTR Wikis, assume this case in the following).
+
+This was changed recently but almost all Wikis provide Gadgets to restore the old behavior (see http://en.wikipedia.org/wiki/MediaWiki:Gadget-righteditlinks.css or http://de.wikipedia.org/wiki/MediaWiki:Gadget-editsection-align-end.css for examples)
+
+The problem is, that the VisualEditor's fly-out-links reserve space to the right for the ""edit source"" link. Therefore when aligning the links right they actually appear with a large distance to the page-margin. The fly-outs should therefore be modified to not reserve any space so the ""edit"" link is correctly aligned right.
+
+To prevent the fly-outs to shift the whole ""edit"" link left as soon as they become visible they could be changed to fly-out to the left in this case or to the bottom.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1372460880,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-wxztsvwizvyvhpvx2lty,task_description,resolved
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"This task refers to a short-lived VE feature, where instead of the dual ""edit"" and ""edit source"" section edit links we all know and love today, it only displayed one of the links, and the second one would appear (""fly-out"") when the links were hovered with the mouse. It was so short-lived that I can't even find any screenshots of it; it was implemented in [[https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/69984|change 69984]] (Jun 26, 2013) and then removed in [[https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/77165|change 77165]] (Aug 02, 2013). This task was filed on Jun 29.
+
+No solution is needed any more since we started showing both links, and this probably should have been closed in 2013!",1663958347,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-wxztsvwizvyvhpvx2lty,task_subcomment,NA
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"Trivial patch idea
+
+To add some content: Wouldn't a trivial patch along the lines of the attachment be sufficient to fix this problem?
+
+I'm sure something like this could be implemented with minimal effort for somebody with a little experience!
+
+**Attached**: {F11273}",1372621960,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-wxztsvwizvyvhpvx2lty,task_subcomment,NA
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"I see your point but you have to admit that without changing the style of the edisection-links these Gadgets wouldn't have been necessary in the first place. They are basically ""fixing"" what WMF ""broke"" so it would be nice if you at least tried to supply a solution.",1372620403,PHID-USER-v3yn5qf233ggnnnmvejc,False,PHID-TASK-wxztsvwizvyvhpvx2lty,task_subcomment,NA
+VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget),"(In reply to comment #0)
+> Until a recent MediaWiki change the default behavior of edit section links
+> was
+> to float to the far side of the heading (right on LTR Wikis, assume this case
+> in the following).
+> 
+> This was changed recently but almost all Wikis provide Gadgets to restore the
+> old behavior (see
+> http://en.wikipedia.org/wiki/MediaWiki:Gadget-righteditlinks.css or
+> http://de.wikipedia.org/wiki/MediaWiki:Gadget-editsection-align-end.css for
+> examples)
+> 
+> The problem is, that the VisualEditor's fly-out-links reserve space to the
+> right for the ""edit source"" link. Therefore when aligning the links right
+> they
+> actually appear with a large distance to the page-margin. The fly-outs should
+> therefore be modified to not reserve any space so the ""edit"" link is
+> correctly
+> aligned right.
+> 
+> To prevent the fly-outs to shift the whole ""edit"" link left as soon as they
+> become visible they could be changed to fly-out to the left in this case or
+> to the bottom.
+
+Note that in general WMF does not support gadgets and does not encourage their use; they are highly likely to break like this when the code they depend on changes, and this is a good example of that breakage. :-(
+
+I've re-written this a bit to be clearer. As ""lowest"" priority, reflecting that we don't support gadgets. of course anyone who is interested in patching is welcome to suggest ideas/code that could address this.",1372620013,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-wxztsvwizvyvhpvx2lty,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"It has been mentioned in some places[1][2] that the JSON syntax might be a problem for typical (non-technical) users, so I suggest creating a plugin for editing the content of the <templatedata> tags.
+
+[1] https://commons.wikimedia.org/wiki/Template_talk:Information#Adding_TemplateData_information
+[2] https://pt.wikipedia.org/wiki/WP:Café_dos_programadores#Mais_uma_novidade:_TemplateData
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=51734",1372160580,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-blsibbjjroitozskiyjq,task_description,resolved
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"This was done as part of {T152230}.
+
+{F5229438}",1483554630,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"No, this is for editing TemplateData blocks nicely once we enable Template: namespace editing in VE (and the 2017 wikitext editor).",1476984711,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,We created a template data editor a few years ago.,1476640713,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"I've translated the script to enwiki : http://en.wikipedia.org/wiki/User:NicoV/TemplateDataEditor
+
+and made a screenshot in Commons : http://commons.wikimedia.org/wiki/File:TemplateDataEditor.png",1374308029,PHID-USER-o34e5i3eq4nstbvcf26w,False,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"Created attachment 12786
+Screenshot of the form provided by the user script from frwiki
+
+(In reply to comment #2)
+> A user on fr.wikipedia seems to have developed a user script to easily add
+> TemplateData to a template:
+> https://fr.wikipedia.org/wiki/Utilisateur:Ltrlg/scripts/TemplateDataEditor.js
+> 
+> This might be of interest while developing a similar VE module.
+
+For convenience, I've attached a screenshot of the form generated by that script.
+
+**Attached**: {F11686}",1373295643,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,"A user on fr.wikipedia seems to have developed a user script to easily add TemplateData to a template:
+https://fr.wikipedia.org/wiki/Utilisateur:Ltrlg/scripts/TemplateDataEditor.js
+
+This might be of interest while developing a similar VE module.",1373293342,PHID-USER-z6nzrwuaij3spgyg23jt,False,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+VisualEditor: Extend the rich TemplateData editor to be used inside VE,See also bug 50370 comment 1.,1372535975,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-blsibbjjroitozskiyjq,task_subcomment,NA
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],"A retread of bug 42847 for issues in the run-up to wider deployment.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1372053120,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nsv64fqtru36njpwa54p,task_description,invalid
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],Now replaced by https://phabricator.wikimedia.org/maniphest/query/V25BI8.HgRPz/#R instead.,1423674480,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nsv64fqtru36njpwa54p,task_subcomment,NA
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],"Change 155841 merged by jenkins-bot:
+Greylist IE11
+
+https://gerrit.wikimedia.org/r/155841",1409263118,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nsv64fqtru36njpwa54p,task_subcomment,NA
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],"Change 155841 had a related patch set uploaded by Jforrester:
+[WIP] Greylist IE11
+
+https://gerrit.wikimedia.org/r/155841",1409099824,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-nsv64fqtru36njpwa54p,task_subcomment,NA
+[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer],*** Bug 65688 has been marked as a duplicate of this bug. ***,1400868288,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-nsv64fqtru36njpwa54p,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikimedia wikis,"One of our long-term objectives is for VisualEditor to be enabled by default on all (public) Wikimedia wikis; this is a tracker for that ambition.
+
+As of August 2016, it isn't likely to be completed anytime soon, because some projects differ substantially from the Wikipedia use case for which VE has been primarily designed. For example, Wiktionary pages tend to be composed almost entirely of templates.",1371860160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-r5vx4pebxayyrkdqlagy,task_description,open
+Enable VisualEditor by default for all users of all Wikimedia wikis,"@Jdforrester-wmf, you are proposing to work on this task during the Wikimedia Hackathon in Lyon. Please consider associating this task or the specific related task(s) with #Wikimedia-Hackathon-2015.",1424384875,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-r5vx4pebxayyrkdqlagy,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikimedia wikis,"Change 71259 merged by jenkins-bot:
+Add ability to disable for anonymous users
+
+https://gerrit.wikimedia.org/r/71259",1372564644,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-r5vx4pebxayyrkdqlagy,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikimedia wikis,"Change 71259 had a related patch set uploaded by Jforrester:
+Add ability to disable for anonymous users
+
+https://gerrit.wikimedia.org/r/71259",1372560612,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-r5vx4pebxayyrkdqlagy,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikimedia wikis,OMG. It's bug number 50000.,1371861883,PHID-USER-r7wrkcx7j2vutqs6hr3g,True,PHID-TASK-r5vx4pebxayyrkdqlagy,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,Current deployments listed at [[https://www.mediawiki.org/wiki/VisualEditor/Rollouts|mw:VisualEditor/Rollouts]].,1371860160,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-io6eogshz2s3ntb5ae7u,task_description,open
+Enable VisualEditor by default for all users of all Wikipedias,"Volunteers, across experience levels, benefiting from the positive impact [Reference Edit Check](https://www.mediawiki.org/wiki/Edit_check) has been [proven to cause ](https://phabricator.wikimedia.org/T342930#9753996) relates to how easily newcomers can access VE. Thus, why I'm relating this ticket to T331946.",1715626643,PHID-USER-7x5ai23ne5qampjf3g7r,True,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,">>! In T51999#2735651, @Liuxinyu970226 wrote:
+> What about Dutch, that's the only Phase 1 wiki that still haven't done?
+
+Will create a task.",1490411970,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"What about Dutch, that's the only Phase 1 wiki that still haven't done?",1477095772,PHID-USER-chrmcih5qjpx5buo7vx6,True,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"Change 102208 merged by jenkins-bot:
+Enable VisualEditor by default on ""phase 4"" Wikipedias
+
+https://gerrit.wikimedia.org/r/102208",1389635422,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"Change 102208 had a related patch set uploaded by Jforrester:
+Enable VisualEditor by default on ""phase 4"" Wikipedias
+
+https://gerrit.wikimedia.org/r/102208",1387306106,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"Change 96473 merged by jenkins-bot:
+Enable VisualEditor as default to ""phase 3"" Wikipedias
+
+https://gerrit.wikimedia.org/r/96473",1386021517,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,"Change 96473 had a related patch set uploaded by Catrope:
+Deploy VisualEditor as default to ""phase 3"" Wikipedias
+
+https://gerrit.wikimedia.org/r/96473",1384948485,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+Enable VisualEditor by default for all users of all Wikipedias,*** Bug 54866 has been marked as a duplicate of this bug. ***,1380835091,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-io6eogshz2s3ntb5ae7u,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"###Problem
+There are various workflows where a user wants to both interact with (or at least see) a page's content, and also interact with a potentially complicated form/process, which may have many controls/inputs.
+
+Some VisualEditor examples:
+ - Adding/editing categories (T51969#548266)
+ - Adding/editing a template with many parameters
+Some non-VE examples:
+ - Rater dialog (T51969#2847958)
+ - [[https://en.wikipedia.org/wiki/Wikipedia:Twinkle|Twinkle]] dialogs ([[https://github.com/azatoth/twinkle/issues/414]])
+
+###Feature request
+Dialogs that have no need to be modal (intended to interrupt the primary workflow, and requiring some action before you can get back to the primary workflow) should be draggable.
+Gadget/script/other developers using OOUI should have a simple way to enable this feature, e.g. a config setting that can be set to `true` to allow dragging.
+
+Some specific workflows may have viable alternatives to dialogs, e.g. {T52239}, but that doesn't solve the general problem for more complicated dialog-based workflows.
+
+###Initial task description
+Quoth requester: If I can't read the article, because the ""page settings"" box is large and un-draggable and hides all the article, how can I see what defaultsort or categories I want to add (especially as for defaultsort I probably want to copy and paste all or part of the article title).
+",1371833520,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_description,open
+OOUI: Dialogs should be repositionable/draggable,"The previous comments don't explain who or what (task?) exactly this task is stalled on ([""If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on""](https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle)). Hence resetting task status, as tasks should not be stalled (and then potentially forgotten) for six years for unclear reasons.
+
+//(Smallprint, as general orientation for task management:
+If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead.
+If work on this task is blocked by another task, then that other task should be added via {nav name=Edit Related Tasks... > Edit Subtasks}.
+If this task is stalled on an upstream project, then the #upstream tag should be added.
+If this task requires info from the task reporter, then there should be instructions which info is needed.
+If this task needs retesting, then the #testme tag should be added.
+If this task is out of scope and nobody should ever work on this, or nobody else managed to reproduce the situation described here, then it should have the ""Declined"" status.
+If the task is valid but should not appear on some team's workboard, then the team project tag should be removed while the task has another active project tag.)//
+",1604263339,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#5669037, @John_Broughton wrote:
+> (b) let's find specific solutions to specific user problems that don't require that approach.
+
+Sure, but shouldn't they be discussed in more specific tasks? This task is for OOUI in general, which is used for more than just VisualEditor.",1573957456,PHID-USER-sesl3h225nhd3px7w7bu,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Regarding ""Your idea also doesn't seem to relate to dialogs where information is being input from multiple different places in the article"", I'm not proposing this for all situations. In fact, I'm primarily interested in getting some action on the problem of more easily adding categories to articles.
+
+And yes, it's true that some categories won't be have related text in the article. For that, one option is to leave the current menu-driven process as is (there isn't anything wrong with having two ways to do the same thing). Another option, of course, is for the user to select some (irrelevant) text, then when the dialog box occurs, change that text to whatever he/she wants as a category. (The selected text wouldn't be locked in any way, just as text selected to create a link can be changed by the user, in the dialog box.)
+
+Again, my larger points are (a) if a moveable dialog box is either difficult to implement or undesirable from a UI/UX viewpoint, then (b) let's find specific solutions to specific user problems that don't require that approach.",1573924342,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I'm now totally unfamiliar with VE because I abandoned it years ago because I found it unusable. I simply wanted to be able to move the category input box away from being on top of the info I needed to categorise, which might have been a county name for a locality, or a footballer's birth decade and field position, etc. It seems, to a naive editor, a simple request.
+Sent from Yahoo Mail on Android",1573919054,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"@John_Broughton that seems to be assuming that the category name will appear as text somewhere in the article, but that will not always be the case. For example [[ https://en.wikipedia.org/wiki/List_of_pear_cultivars | List of pear cultivars ]] is in Category:Lists of foods. The words ""Lists"" and ""foods"" appear nowhere on the page other than the category names, even ""food"" appears only in the link to a portal and in the title of one reference and neither are in close proximity to any instance of the word ""list"". I imagine this will be even worse in languages where plurals are formed differently than in English.
+
+Your idea also doesn't seem to relate to dialogs where information is being input from multiple different places in the article. 
+
+Back in May 2017 I commented:
+> I wouldn't object to dockable diaglogs appearing like that at the bottom of the screen as an option, but simply being able to move a reasonably sized box around the screen to a convenient point for the task at hand would be vastly superior imo.
+@Spinningspark replied
+>Yes, that exactly sums up the issues.  A moveable window is the best solution. The issue is being clouded with these alternative solutions and we have ended up with no solution at all.
+We don't seem to have moved on at all in the last 2½ years. ",1573913438,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I haven't thought this through, but, for example, to add a category to Wikipedia page, one could (1) select some text, and (2) tell VE that you want that text to be a category.  The process would be similar to linking, where one selects text and then clicks on the link icon. 
+
+The linking process works really well in VE because the link icon is one click away from the text being edited, while categories are a menu choice, so two clicks away. But I doubt that anyone would complain about the extra click if setting up a category was almost as easy a process as creating a link.
+
+Still, if one wants to dream about an even easier interface, it would be this:
+
+(a) select some text
+(b) a palette window automatically appears (relatively small, perhaps, since the editor might be selecting text to copy, move, or delete)
+(c) click on an icon in the palette window to select a relevant action from the palette window (which might be expanded with a click, maybe showing the selected text in an attached window). The relevant options could include create a link, create a category, format the text as a heading, format a paragraph (block quote), format some text within a paragraph (bold, italic, etc)
+
+In other words, in VE, when you select some text, VE would automatically say ""Okay, here are your options for that text."" [I have no idea how difficult this would be to program.]
+
+",1573840441,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"@John_Broughton, the StackExchange link makes me wonder whether we should be thinking of these as modal dialogs (something intended to interrupt the primary workflow [which is probably ""typing text into the body of an article""] and requiring some action before you can get back to the primary workflow).  Maybe editors would find it better to have a https://en.wikipedia.org/wiki/Palette_window instead.",1573838216,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Given that a user wants to both interact with (or at least see) a page's content, and also interact with a somewhat complicated form/process (i.e. many controls/inputs, e.g. Rater, or in VE adding/editing a template with many parameters), what alternatives are there?
+ - Unmovable dialog: Forces the user to swicth back-and-forth to another tab/window; or exit the dialog, find what they wanted to find, and go back in
+ - Docking: Only works if your screen is big enough
+ - Prepending to (or placing just above) the content area: Causes content to re-position, can't necessarily see both things at once (if scrolling is required), not really suitable if the form/process applies to only one section of the page
+ - Appending to (or placing just below) the content area: Similar to prepending, but instead content re-positioning existing content, the form/process won't initially be visible on longer pages, unless you force the page to scroll there
+I don't think those alternatives are actually better than letting the user move the dialog out of the way.",1573803105,PHID-USER-sesl3h225nhd3px7w7bu,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"https://ux.stackexchange.com/questions/81134/should-modal-dialogs-be-movable seems to show a (rough) consensus that when a proposed solution to a dialog is to make it moveable, the dialog itself is poorly designed. That implies looking for a different solution that addresses the underlying user problem. 
+
+For example, when in VE, and wanting to create a category, the dialog could include the text of the section where the pointer was located when the dialog was invoked (scrollable on the left side of the dialog). That way, the user could selected text from the left side of the dialog and paste it into the right side. [I'm not arguing that this is optimal, just that it's another way to solve the underlying user problem.]",1573599401,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"FYI, I found I could do the draggability easily enough without the library, just using mouse/pointer events directly - [[https://github.com/evad37/rater/commit/a510709e8eb61389e0d83faca7750215affb1f9c|diff]].",1573580066,PHID-USER-sesl3h225nhd3px7w7bu,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I've implemented draggability for an OOUI process dialog for the latest version of my [[ https://github.com/evad37/rater | Rater script]], by [[ https://github.com/evad37/rater/commit/0ef3d7eca0a2417550030ceac9219265dbcbdf5b | using a drag-and-drop library ]] and [[ https://github.com/evad37/rater/blob/f0ca4cdbbfca6529bbe235e2f8d8b3f626bcc18d/rater-src/css.js#L31 | some CSS overrides]]. It would be nicer if this functionality was directly supported, rather than relying on a library with a bunch of functionality that isn't actually used -- at least for reusers of OOUI, even if WMF devs choose not to use it.
+
+(Coincidentally, this is the exact use-case @Gryllida was describing above three years ago.)",1573488532,PHID-USER-sesl3h225nhd3px7w7bu,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#3224607, @Thryduulf wrote:
+> When editing in VE I sometimes have to load a duplicate copy of the page in a new tab so that I can see what I'm doing.
+> 
+> I dislike the split-screen approach as that uses more screen estate than required and divorces the dialog from its context. I wouldn't object to dockable diaglogs appearing like that at the bottom of the screen as an option, but simply being able to move a reasonably sized box around the screen to a convenient point for the task at hand would be vastly superior imo.
+
+Yes, that exactly sums up the issues.  A moveable window is the best solution.  The issue is being clouded with these alternative solutions and we have ended up with no solution at all.",1493641919,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"When editing in VE I sometimes have to load a duplicate copy of the page in a new tab so that I can see what I'm doing.
+
+I dislike the split-screen approach as that uses more screen estate than required and divorces the dialog from its context. I wouldn't object to dockable diaglogs appearing like that at the bottom of the screen as an option, but simply being able to move a reasonably sized box around the screen to a convenient point for the task at hand would be vastly superior imo.",1493598817,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Three and a half years on from my initial complaint, and as far as I know the Visual Editor is still useless to me, so I don't use it. Let me know when it becomes a useful editing system for people who need to see the original article while adding categories or doing other tasks.",1493224533,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,I still think something like a split-screen mode would be a better solution for these cases than movable dialogs (see mockup above in T51969#821409).,1493220892,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Yes - when someone tells me that VE is usable, I'll have another look at it. If the dialog box still obscures the content, then for my prolific WikiGnoming it's useless. Two years since I raised this, and no progress. Nice to feel appreciated. ",1481018430,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Astonishing this is still open.  I stopped using VE a year or two back because this and other problems made for an inefficient worklow.  Still not time to give it another try I see.,1481016428,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I appreciate this discussion happening. It is strange that we are thinking that draggable dialogs create problems, so I will attempt to illustrate it with a use-case. I am trying to write a user script in oojs-ui, and the script work should be similar to the old gadget whose dialog is draggable to expose different parts of the article text in order to perform its assessment.
+
+Here is the gadget documentation and source code: https://en.wikipedia.org/wiki/User:Kephir/gadgets/rater
+
+Here is a screenshot attached, which I also uploaded to Commons and which is found at the gadget documentation page:
+
+{F4983945}
+
+I would like to be able to perform article rating on the new pages queue continuously one after another, and having draggable dialog reduces the working memory (and increases efficiency) of the process about tenfold, as I don't have to hold the article contents in my memory.",1480961860,PHID-USER-aklqcs2xae5ghg6icqmd,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I agree that the dockable model is trying to modify something where we might better look for alternatives. For example, one way to create a new category might be to highlight some text, then select (say) Insert > Category. That could open a dialog (for example, to  allow a different sort key than the default, and to offer the opportunity to create a category if one being created didn't already exist.
+
+This isn't perfect, of course - if a particular category didn't exist (as text) on the page, the user would have to add it, create the category, then delete the unneeded text. Still, maybe it's better, and at least it's something to think about.",1418179696,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#821409, @matmarex wrote:
+> I'm increasingly convinced that draggable dialogs in general are a solution in search of a problem. (It could be interesting to do, but shouldn't be applied to all dialogs.)
+> 
+>> You're saying that I've got a problem with my workflow: how else do you suggest that I add a category, a stub template, or a DEFAULTSORT to an article, if I can't read the text of the article? I could copy and paste the entire article content into a notepad, so that I could refer to it ... hardly seems reasonable.
+> 
+> I was thinking, perhaps the dialogs should be ""dockable"" at the bottom of the screen? Clicking an icon on dialog's title bar would hide the white overlay and dock it, revealing article content. We should think what to do with dialogs that were modal in this case, but I think this approach could work, and could work a lot better than clunky dragging of dialogs (which are often way too large for dragging to make sense, as they would cover most of the content anyway even when dragged aside).
+> 
+> Here's a rough mockup – note the docking icon on the right. Thoughts?
+
+Eurgh. I really don't like the dockable model of modals. It feels like failure. I'd prefer instead that we provide secondary non-modal ways to do things people want to do that isn't modal. As @Whatamidoing-WMF says, this isn't going to work for anyone that doesn't have a huge desktop screen to use.",1418176632,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#835122, @TrevorParscal wrote:
+> In my view, editing categories should not be a modal experience.
+
+Not **necessarily** modal. The HotCat gadget that this partially replaces is already effectively-modal too, for instance.
+
+> The category editor should simply be embedded at the bottom of the page in place of the category listing.
+
+That's {T52239}.
+
+",1418176524,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#548465, @PamD wrote:
+> (In reply to Trevor Parscal from comment #22)
+>> I would like to avoid adding moving and resizing to dialogs, because I
+>> believe it solving the problem in the wrong way. At it's root, this is a
+>> workflow problem. Making the dialog resizable and movable does not
+>> adequately address it.
+>> 
+>>....
+> 
+> You're saying that I've got a problem with my workflow: how else do you suggest that I add a category, a stub template, or a DEFAULTSORT to an article, if I can't read the text of the article? I could copy and paste the entire article content into a notepad, so that I could refer to it ... hardly seems reasonable.
+
+I am not saying it's a problem with YOUR workflow, I'm saying it's a problem with the workflow we are providing you. I'm admitting we have failed you, and because we didn't understand how you actually use the software we modeled the workflow around our imagined way you might use the software.
+
+In my view, editing categories should not be a modal experience. The category editor should simply be embedded at the bottom of the page in place of the category listing. If we do anything to try and get the dialog out of the way temporarily, we will still not be able to let you select text behind the dialog without breaking the entire concept of a modal dialog. By placing the category editor at the bottom, you are free to scroll around and select whatever you like. This is the experience you have with the Wikitext editor, and there's no reason we can't continue to provide it.",1418163779,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Making the dialog one-third the width of the screen is only going to make sense on a desktop system.  One third the width of a smartphone screen is not going to be functional (the entire dialog box would be a couple of centimeters wide).,1418010994,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"The discussion is complicated by the unnecessary ""Options"" menu on the left side of the dialog box. (I believe this is the **only** place in VE where selecting a choice from a top menu results in a dialog box that shows all the other choices on that menu; that would make sense if an editor were likely to want to do two or three page-related things at once, but in fact he/she almost certainly does *not*.) While redoing the entire approach to how the three-line (should be ""Page"") menu choices work is probably outside the scope of this topic, I will note that what the requester needs (access to all the text on the page, *while* the dialog is open) is applicable only to **two choices** - categories and default sort. 
+
+For those two menu choices, categories and default sort, I suggest that the dialog attach itself to the **right side** of the window, taking up 1/3 of the width of the window, and that the left side - the text on the page - be scrollable. (If it's easier to program, then perhaps the dialog should be attached on the left, with the scrolling done on the right.) For the other menu choices, a normal modal dialog box is fine.",1417811550,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#821594, @PamD wrote:
+>I don't know the term ""dock""  but I think you mean what I'd call ""minimise""? 
+
+No, dock does not mean the same as minimise.  Docking is fixing the dialogue to one edge of the window, rather than plonking a popup in the middle of the window.  In the mockup example the dialogue is docked to the bottom of the window.  Applications often give the user a choice of which edge they want to dock to, but I don't know if that is what is propsoed here.
+
+For me, this would work if the window could still be scrolled while the dialogue was open, thus uncovering any content hidden by the dialogue (or even off the boundary of the window at the time the dialogue was invoked).
+",1417802087,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Looks as if it might work: I don't know the term ""dock""  but I think you mean what I'd call ""minimise""? So click on that icon, the dialog box shrinks to an icon, I read what's behind it: I hope I can copy text from it, eg to fix a DEFAULTSORT? Then click on the icon to restore the dialogue box and carry on. Yes, could be a great solution. Probably better than my original suggestion, many moons ago, of dragging or resizing.  Thanks.",1417799263,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Indeed, but in this use case you then have to drag it back on-screen to input the category name or whatever.",1417793086,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,">>! In T51969#821409, @matmarex wrote:
+> ...and could work a lot better than clunky dragging of dialogs (which are often way too large for dragging to make sense, as they would cover most of the content anyway even when dragged aside).
+
+Even if the dialog window is very large, it can still be pushed out of the way by dragging it until it is nearly completely off screen.
+",1417793032,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I'm increasingly convinced that draggable dialogs in general are a solution in search of a problem. (It could be interesting to do, but shouldn't be applied to all dialogs.)
+
+> You're saying that I've got a problem with my workflow: how else do you suggest that I add a category, a stub template, or a DEFAULTSORT to an article, if I can't read the text of the article? I could copy and paste the entire article content into a notepad, so that I could refer to it ... hardly seems reasonable.
+
+I was thinking, perhaps the dialogs should be ""dockable"" at the bottom of the screen? Clicking an icon on dialog's title bar would hide the white overlay and dock it, revealing article content. We should think what to do with dialogs that were modal in this case, but I think this approach could work, and could work a lot better than clunky dragging of dialogs (which are often way too large for dragging to make sense, as they would cover most of the content anyway even when dragged aside).
+
+Here's a rough mockup – note the docking icon on the right. Thoughts?
+
+{F19025,size=full}",1417792226,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to Trevor Parscal from comment #22)
+> I would like to avoid adding moving and resizing to dialogs, because I
+> believe it solving the problem in the wrong way. At it's root, this is a
+> workflow problem. Making the dialog resizable and movable does not
+> adequately address it.
+> 
+>....
+
+You're saying that I've got a problem with my workflow: how else do you suggest that I add a category, a stub template, or a DEFAULTSORT to an article, if I can't read the text of the article? I could copy and paste the entire article content into a notepad, so that I could refer to it ... hardly seems reasonable.
+
+If I want to add a stub template for a Russian footballer, and then discover that not only do I need {{Russia-footy-defender-stub}} but that it's subdivided by date of birth, I need to be able to look at the article and find his date of birth to use {{Russia-footy-defender-1960s-stub}}.  If I want to add a defaultsort, I need to be able to copy the surname, and then the forename, from the text of the article. How should I adjust my workflow?
+
+For the foreseeable future, I've adjusted my workflow by abandoning any attempt to use VE as it makes my editing too difficult.",1414347353,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to Trevor Parscal from comment #22)
+> I would like to avoid adding moving and resizing to dialogs, because I
+> believe it solving the problem in the wrong way. At it's root, this is a
+> workflow problem. Making the dialog resizable and movable does not
+> adequately address it.
+> 
+> More of these processes should be non-modal, especially authoring edit
+> summaries. This would allow users to contribute to edit summaries as they
+> work, rather than having to write them at the very end, when the changes
+> they've made are so temporally distant.
+> 
+> Even if the dialog is movable an resizable and movable, the contents below
+> are only visible through a semi-opaque mask and the contents cannot be
+> scrolled because the modal dialog is capturing events (on purpose, it's
+> modal).
+
+This is a good point, but I dont think, its related to this enhencment. You are right, that if I am doing a lot of different changes and/or editing the article several minutes, I forgot, what I was doing. But how this problem is related to the fact, I cannost drag the DW avay to see what is behind?",1414336477,PHID-USER-vm462i2ffbawnuo4mh3n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"I would like to avoid adding moving and resizing to dialogs, because I believe it solving the problem in the wrong way. At it's root, this is a workflow problem. Making the dialog resizable and movable does not adequately address it.
+
+More of these processes should be non-modal, especially authoring edit summaries. This would allow users to contribute to edit summaries as they work, rather than having to write them at the very end, when the changes they've made are so temporally distant.
+
+Even if the dialog is movable an resizable and movable, the contents below are only visible through a semi-opaque mask and the contents cannot be scrolled because the modal dialog is capturing events (on purpose, it's modal).",1413922302,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"> You can't edit anything, tables, Chinese or galleries, 
+> if there is big immovable box in the way.
+
+This isn't really true:  you can close the box.  With the box open (and movable), you can *see* the content on the page, but you still can't edit it.  When you've got a dialog box open, but all your typing ends up on the page underneath the box, then we call that a bug.
+
+The problem here is that (depending on the size of the box and the exact location of your cursor when you open it), what you need to *see* on the page might be covered up by the box.  ""Open box, realize that you've forgotten how to spell something, realize that the box is covering up that word, close box, check spelling, open box again, finally type"" is not as efficient as ""Open box, drag it out of the way, start typing"".",1407787535,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to James Forrester from comment #18)
+> (In reply to Spinningspark from comment #17)
+> > Why is this languishing at low priority? Fixing something that is preventing
+> > the editor from reading the thing he is editing is HIGH priority.
+> 
+> ""High"" priority would mean that it's more important than editing tables,
+> editing in Chinese, or editing galleries. ""High"" priority is not appropriate
+> for this relatively minor and very complex enhancement request.
+
+You can't edit anything, tables, Chinese or galleries, if there is big immovable box in the way.",1407777158,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Just to be clear, this is a DESIGN TEAM problem, because it's a problem with the OOjs UI, which VE uses, but which is under the control of the Design team. The issue is that the OOjs UI WindowManager lacks a resizing event. That issue affects every use of windows in the OOjs UI, not just VE's use of windows.
+
+Why isn't this bug showing on the list of problems that the Design Team is considering (https://bugzilla.wikimedia.org/buglist.cgi?keywords=design&keywords_type=allwords&list_id=335932&order=changeddate%20DESC%2Cvotes%20DESC%2Cpriority%2Cbug_status%20DESC%2Cassigned_to%2Cbug_id&query_format=advanced&resolution=--- )? (I got that list via https://www.mediawiki.org/wiki/Design ) 
+
+Relatedly, why is the priority for fixing this bug being set by the VE team, rather than by the Design team?",1407776333,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to Spinningspark from comment #17)
+> Why is this languishing at low priority? Fixing something that is preventing
+> the editor from reading the thing he is editing is HIGH priority.
+
+""High"" priority would mean that it's more important than editing tables, editing in Chinese, or editing galleries. ""High"" priority is not appropriate for this relatively minor and very complex enhancement request.",1407771922,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Why is this languishing at low priority? Fixing something that is preventing the editor from reading the thing he is editing is HIGH priority.,1407759592,PHID-USER-imut7wxehhy35ukuzaks,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,*** Bug 67952 has been marked as a duplicate of this bug. ***,1405474879,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Moving to the OOjs UI product as that code is now shared.,1387222480,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Please see https://upload.wikimedia.org/wikipedia/commons/d/d9/Wide_edit_window_%28Proposal_for_Wikimedia_VisualEditor%29.png for an example of what a wide window might look like for reviewing changes.,1387216858,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"The change review window is also too small to be useful for some editors, especially if a lot of changes have been made.",1385605063,PHID-USER-uf3buojo4ceizjywvyn5,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Understandable. You will receive a bugmail notification once this bug report is fixed.,1382574004,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Let me know when this is fixed, because I'm not going to stress myself by using VE until then - it just makes my everyday editing too much like hard work. When it's fixed (and perhaps a few more of my long-standing complaints - hidden comments, red links appearing as red, etc), I might carry on with debugging your system. Till then, why should I bother?",1382566037,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to comment #9)
+> Two months since there's been any comment on this ... I admit I've pretty
+> much
+> given up using VE (too tedious because of this and other problems, plus some
+> stuff going on in Real Life which makes me want to reduce Wikistress). Any
+> chance of it getting fixed some time? I'm sure I'm not the only person
+> affected.
+
+Some time? Yes. Soon? No. In my view, it's not as important as fixing things like copy-and-paste or adding citation template quick-add support or editing tables.",1380756245,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Two months since there's been any comment on this ... I admit I've pretty much given up using VE (too tedious because of this and other problems, plus some stuff going on in Real Life which makes me want to reduce Wikistress). Any chance of it getting fixed some time? I'm sure I'm not the only person affected.",1380755973,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Prioritisation of work is done on how much it interferes with people using the software, not how long ago it was first mentioned as an issue. For example, bug 4 (!) is from 2004.
+
+I'm sorry that this is getting in the way of your use of VisualEditor, but I think that adding copy and paste support (for example) should happen first. I could ""upgrade"" the importance of this to ""high"" but it wouldn't get the code written any faster. :-(",1375472653,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Six weeks on from first request it's depressing to see this is still ""low enhancement"". Example: stub-sorting a Russian icehockey player, I open the dialog box to remove the existing stub tag and then go to the dropdown menu to add ""Russia-icehockey-bio-stub"", only to discover that there are separate stubs for wingers, goalies, etc. I didn't notice what he was.  I have to quit the dialog box, find he's a winger, re-open it, re-delete the old stub, return to the dropdown menu to add the new stub template.  The inability to move or shrink the dialogue box makes ordinary routine wikignoming harder work. But I suppose the target market of newbies don't do things like that, and we established editors can be trusted to struggle on regardless (some of us, perhaps a diminishing number), however ignored our needs may be?  
+
+Yes, I could abandon VE and this wouldn't trouble me any more, but I'm trying to help by persevering in using it to help you debug it. In return, how about a little attention to one of the first issues I raised?",1375470897,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"How hard is it to make the dialog box moveable? Really? There is what, one parameter that needs to be changed? If this were a really hard problem, it would be understandable that the VE team was deferring this for more important things. But it's not that hard (I hope; if so, that bodes poorly for VE), and it impacts LOTS of editors. Yes, it affects the dialog box for page settings, when doing categories. But there is the identical problem when adding a caption for an image (Media settings dialog; might want to know how something in the article is spelled) and possibly for the other dialog boxes (for example, in the Media dialog, searching for an image where the search term has an unusual spelling).
+
+Even better would be the ability to copy/paste from the main editing window to a field in the dialog box. I realize that has potential ramifications for loss of focus - it would be undesirable for the dialog box to disappear *behind* the main editing window. Still, in Mac OS X, the ""Force Quit Applications"" dialog box is moveable, and the user is able to copy text from other windows, but the dialog box remains on top of every window until it is closed. (Excessive, actually: the ideal is to have the VE dialog box float on top of the main editing window, ONLY.)
+
+But we (as in, Wikipedia editors) would settle for a really minimal solution, initially - just make the dialog boxes moveable. Please?",1374967939,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"Any movement on this? Low-priority according to the development team, I accept, but it's a pretty important chunk of the editing workflow for a lot of tasks.",1373882058,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"If I want to add ""Category:1917 births"" and ""Category 1987 deaths"" to an article, is it undesirable multitasking to expect to be able to see the lead sentence which says ""'''Joe Bloggs (1917-1987)..."", rather than having to remember the two dates? Or if I want to assign ""Category:Villages in ..."" for some area whose placenames are unfamiliar and have difficult spellings? Please let me see the article while adding categories: a simple way would be to let me drag, or shrink, the dialogue box which at present totally obscures the article text. (I was the original reporter of this bug on 21 June, and the response above seems to misunderstand its importance.)",1372628541,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"(In reply to comment #1)
+> The idea of the dialog being modal is that you aren't multi-tasking with it
+> at all.
+
+This isn't asking for multi-tasking, it's asking for the ability to drag the dialog out of the way so that you can get context for the single-tasking, err, task. :-)",1371835847,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,Makes sense.,1371835810,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+OOUI: Dialogs should be repositionable/draggable,"The idea of the dialog being modal is that you aren't multi-tasking with it at all.
+
+As far as adding a category or changing the default sort of a category directly from some other mode (such as reading, or editing paragraph text) we should look at those workflows rather than dissolve the intentional model-ness of the dialog.
+
+For example:
+
+- Perhaps categories could be edited at the bottom of the page, rather than inside a dialog.
+- Maybe the category editor could use some other kind of UI container that isn't modal.
+
+etc.",1371835724,PHID-USER-mpfqwllylfkzpcgkdkvc,False,PHID-TASK-g55t2yyhma4clcxdjjey,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","When in the template editing dialog, a link going to the [template:name] page, would be really helpful for:
+* Reading detailed documentation
+* Easy access to (edit or examine) template source code
+
+**See Also**:
+* {T52354}
+* {T52656}
+* {T53311}",1371589200,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-axbu733atg4fftym2lek,task_description,resolved
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","Change 257443 merged by jenkins-bot:
+MWTemplatePage: Show a link to the template even when there's a description
+
+[[https://gerrit.wikimedia.org/r/257443]]",1482231864,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","Change 257443 had a related patch set uploaded (by Jforrester):
+MWTemplatePage: Show a link to the template even when there's a description
+
+[[https://gerrit.wikimedia.org/r/257443]]
+",1449525412,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","Exists templates with variable parameter names. If you create a tTD for a part of the parameters, then it just do not describe the other part of parameters and disappear link to the documentation. eg https://ru.wikipedia.org/wiki/Ш:Familytree",1441449224,PHID-USER-5joeladhczukimiv4rwl,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","MediaWiki doesn't enforce any particular page being a documentation page, it's a thing made up by users.",1414817959,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","If this wasn't clear enough, the user asks for a link to the template /documentation/ page.
+Here's another example of the need to access documentation page:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=67986#c1
+If the user doesn't read the template's manual, he currently has no way to guess that there may be several required parameters and which ones he needs to fill for the template to work correctly.",1405348985,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","This is being asked at ru.wp even for templates which have TemplateData info;
+quoting the reasoning, the user wants to be able to access:
+-full template documentation 
+-see more examples of which are difficult to describe in words 
+-read about other similar templates 
+-edit template data.",1405346626,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","This was done two months ago for templates which lack documentation; I'm closing this as a ""WORKSFORME"" at this point, as if the user has to go read the template's page to understand what the documentation is telling them, the creator of the documentation has utterly failed.",1399324925,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","This bug seems to have strayed/widened far from the original simple request (which I remember also making on the feedback page at some point many days ago): when one is adding a template (""transclusion""), a button to link to the template page would be very useful - to be able to read all the detailed description there. Look at [[Template:Genukiwry]] as an example - it couldn't all be coded up into TemplateData, but it could be made accessible by providing a simple link which would open in a new tab / new window / popup (ie anything which wouldn't spoil the ongoing editing operation). This facility would be an area where VE could provide a better editing experience than Edit Source, and surely wouldn't need a huge programming effort.",1373999921,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","I googled ""mediawiki glossary"" and found this: 
+*[[mw:Manual:Glossary]] - now bookmarked. :)
+
+I am not using ""parameter"" correctly in the context of MediaWiki. I couldn't find ""parser"" listed in the glossary. :)
+
+My point with both bugs is to get links to the template pages so that people can edit them in wikitext source mode there on the template page. Nothing more. I am not interested in being able to edit templates within VE at all. 
+
+In fact, With the exception of reference templates I think editing of templates within VE should be disabled since it is not WYSIWYG, and only adds a new layer of abstraction. I think the only thing that should be provided by VE is a link to the template page. 
+
+If an editor of Wikipedia like me with 26,000 edits does not understand the terms (parameter) used in VE template editing, then imagine the difficulty new editors have when they see those terms listed in VE template editing. 
+
+I would like VE mainly to do text editing and references. Nothing more for now. I think people would be ecstatic with that. Since there are so many reference templates, I think that alone may require an increase in the number of paid full-time developers assigned to VE. 
+
+I actually understand a lot about table editing and template editing, but only at the wikitext editing level. I can do it, but not always explain it, since my knowledge mostly comes from hacking at it over the years. :) I help edit this page:
+*[[Help:Sorting]]",1371717599,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","(In reply to comment #1)
+> Here is a page that has a table and a couple transcluded navigation-box
+> templates at the bottom:
+> [[List of countries by incarceration rate]]
+> 
+> With VisualEditor (VE) the table is editable and WYSIWYG.
+
+(Yay. :-))
+
+> But with VE the existing text in the 2 navigation boxes can not be edited as
+> far as I can tell. At least not within VE from that page. I am talking about
+> after clicking the edit icons for the navigation boxes.
+
+Yes, VisualEditor is disabled for the Template namespace, and likely will be for a very long time (or forever). It's mostly used for very complicated transclusion wikicode which often can't be edited visually, because it doesn't form a complete document, only part of one.
+
+> New parameters can be added to one of the templates, but not to the other. I
+> don't see a way to edit the text for existing parameters in either navigation
+> box. 
+
+I'm a bit lost here - you mean parameters on [[List of countries by incarceration rate]]'s invocations of [[Template:Incarceration]] and [[Template:Law country lists]]? Those templates take no parameters, though it's possible to add new parameters to template invocations that don't currently have one - see my edit (actually two edits) with VisualEditor here: https://en.wikipedia.org/w/index.php?title=List_of_countries_by_incarceration_rate&diff=560637005&oldid=559696805
+
+> So to be able to edit one of those templates in source mode or otherwise it
+> would be helpful to have a direct link to the transcluded template page, and
+> not to the many templates that make up such a navigation box at the core
+> level. 
+
+You can definitely edit those templates in source mode still - do you mean, edit the invocation of those templates? You should be able to replicate anything you can do with a template invocation in source mode using VisualEditor at this point. On the other hand, trying to offer ""edit the source of this template invocation"" is extremely technically hard (as well as being a very complicated user interface issue for users).
+
+> See related bug 878.
+
+I'm afraid I don't see how that bug, about the wikitext editor's additional listing of templates used on section editing, is related. Could you explain the link?
+
+I also don't see how this relates to this bug, which is a minor enhancement request to add a link to the used template on the template's pane (which I think is fine, but we'll have to work out if we can do this in all situations - what do we do when the ""template"" you're using is in fact a parser function? - etc.).",1371665278,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it","Here is a page that has a table and a couple transcluded navigation-box templates at the bottom:
+[[List of countries by incarceration rate]]
+
+With VisualEditor (VE) the table is editable and WYSIWYG.
+
+But with VE the existing text in the 2 navigation boxes can not be edited as far as I can tell. At least not within VE from that page. I am talking about after clicking the edit icons for the navigation boxes. 
+
+New parameters can be added to one of the templates, but not to the other. I don't see a way to edit the text for existing parameters in either navigation box. 
+
+So to be able to edit one of those templates in source mode or otherwise it would be helpful to have a direct link to the transcluded template page, and not to the many templates that make up such a navigation box at the core level. 
+
+See related bug 878.",1371619899,PHID-USER-ebwxbdwkoxprr4cvvjvy,False,PHID-TASK-axbu733atg4fftym2lek,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"This is more of a tracking bug than anything else, but it should be something people are aware of and something that's formally logged; the VisualEditor is very slow on large articles, to the point where it causes confusing output.
+
+Using the example of https://en.wikipedia.org/wiki/OpenOffice - I edited this and it took a good 20 seconds just to render 'review changes', and another 20 to save. David Gerard did the same and the server popped up  ""Error saving data to server: timeout."" with both 'review' and 'save'. Despite this, it saved anyway.
+
+Obviously as a long-term thing: we shouldn't have an editor so slow that someone in an industrialised, Western nation (i.e. the UK) can't make things work.[1] As a short-term thing, we shouldn't be informing users ""something has gone terribly, terribly wrong, abort!"" when it has actually saved.
+
+[1] It's David Gerard, he's not going to be using dial-up.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1371467880,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_description,invalid
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],Let's use #VisualEditor-Performance instead.,1417556322,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Update on the test Oliver mentions at the top: on the same PC and the same Internet connection (though a current version of Firefox), it just now took:
+
+* 10 seconds to open [[OpenOffice.org]]
+* 176 seconds (nearly three minutes!) to render the ""Review your changes"" diff
+* two minutes attempting to save, then ""Error: Unknown error"". The edit did, however, save: https://en.wikipedia.org/w/index.php?title=OpenOffice.org&diff=597641893&oldid=593809275
+
+It's a ... test subject ... of a page.",1393664271,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"another stopped sript warning
+
+**Attached**: {F11497}",1372621880,PHID-USER-2mkpm2voxepwvz7abjug,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Firefox chokes
+
+This happens /before/ script-stop warnings.
+
+**Attached**: {F11496}",1372621308,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Stopped script warning
+
+**Attached**: {F11495}",1372621284,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"It was previously doing a very dirty diff; I just tried again on this article and it did a clean diff, but timed out when I hit ""save"", three times in a row, and didn't actually save any of them.",1371560422,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"(In reply to comment #3)
+> It may also be worth noting that this page takes ~30 seconds in my use to
+> save when using the ordinary source wikitext editor - it's a complex page!
+
+Yes, one of the problems is that VE being slow is rather more noticeable than MW being slow (because ""it's a website"" and so triggers different time response expectations in users). :-(",1371496866,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],It may also be worth noting that this page takes ~30 seconds in my use to save when using the ordinary source wikitext editor - it's a complex page!,1371495878,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Listing the issues so it's clear what we mean by ""performance issues"" and their different causes and artefacts:
+
+* [network] VE slow to load own JS - mostly provided by ResourceLoader and local cacheing so this would only be a slowness once per user's browser (assuming they don't clear their local cache); we could pre-load VE JS for all users on read, which would reduce load times when people press edit slightly, but that is evil
+
+* [network] VE slow to fetch HTML from Parsoid - mostly fixed due to highly-aggressive caching at our cluster (the payload is slightly smaller in byte size than the read page fetch, i.e. not significant)
+
+* [client] VE slow to render Parsoid HTML into an editable document - we're working on this (profiling etc.), but there's a tension between editability and simplicity of data structure. :-)
+
+* [client] VE slow to respond to user action - same as above; this is the core ""performance"" area for VE itself, of course
+
+* [server] VE slow to get a wikitext diff - this relies on two operations; a Parsoid serialise and an MW wikitext diff: we can work with Parsoid on that being faster, but there's a limit; theoretically we could pre-serialise as we go (but eww network traffic and load on the servers)
+
+* [server] VE slow to save edit - this is essentially the same performance issue as getting the wikitext diff, above; theoretically we could optimise by saving the output of the serialise from a wikitext diff, but this won't be triggered for most users, so it's of marginal utility",1371495451,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance],"Specifically, 8Mbit ADSL through Zen. Most of the slowness appears to be thinking - I could hear my laptop's CPU fan speed up.",1371470989,PHID-USER-gfaq55vdypjmzz6nl2kn,False,PHID-TASK-bzxuqebvczsa3yqj6fmu,task_subcomment,NA
+VisualEditor: Provide a get-me-into-the-wikitext-editor link on every header inside the VisualEditor,"From [[https://phabricator.wikimedia.org/T50429#518092|a comment]] on T50429.
+
+>It would be wonderful if the ""edit source"" links or icons for sections also showed up inside the Visual Editor. The Visual Editor could treat ""edit source"" links or icons as uneditable links. But the link would still work. So people could click ""edit source"" links or icons to open source editing of a section. 
+>
+> People could go to source mode editing at anytime, even from inside the VisualEditor. That would be so convenient and so useful. Later on, this functionality could be extended to anything the VisualEditor can't edit. People could click on templates, tables, etc. inside the VisualEditor and go directly to source mode editing of that section. Or they could right-click templates, tables, etc. to go to a new tab in source mode for that section.
+
+**See also:**
+T50429
+T51664
+T49779",1371430140,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-cafdsbi6thmpaj3iik3u,task_description,open
+VisualEditor: Provide a get-me-into-the-wikitext-editor link on every header inside the VisualEditor,Is this still relevant now that {T49779} is resolved?,1446661434,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-cafdsbi6thmpaj3iik3u,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","[From bug 48429 comment 20.]
+
+Switching to ""edit source"" tab when VE was triggered via a section-edit link should enter the wikitext editor for that section, rather than the entire page.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=48429
+https://bugzilla.wikimedia.org/show_bug.cgi?id=49665",1371429960,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4qp7cge7h2tflfmzkmov,task_description,invalid
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","In the end we went with bug 49666, which is now done (code to be deployed this afternoon). As discussed above (and I agree), changing behaviour between wikitext section edit behaviour as currently is and the way it works post-VE roll-out - but only on VE-enable-able pages (i.e., not talk pages/etc.) would be complicated and not add value to users.
+
+Consequently, closing this as INVALID.",1372279963,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","Bug 49665 may be another solution: ""VisualEditor: Provide a get-me-into-the-wikitext-editor link on every header"". 
+
+It looks like there will be an ""edit"" link and ""edit source"" link (or icon) on every header.See bug 49666.
+
+If the header ""edit source"" links (or icons) remain clickable (and/or right-clickable) from within VE, then that would be a solution for getting into the source editor for sections.",1371649103,PHID-USER-ebwxbdwkoxprr4cvvjvy,True,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","(In reply to comment #3)
+> (In reply to comment #2)
+> > ""Edit Source"" never even existed before Visual Editor
+> 
+> Not even remotely true. The ""Edit Source"" tab is the relabelling of the
+> regular
+> ""Edit"" tab.
+> 
+> I'm minded to agree with This, that and the other, but willing to be
+> convinced.
+
+I see now what you mean, but my point still stands: ""edit source"" is not something that warrants use of the word ""always"", as it's completely new, introduced with visual editor... there was no ""edit source"" anywhere before VE.
+for all i care, we do not even need ""edit source"" on the page when reading it, ""Edit"" is enough, as long as there *is* ""edit source"" once VE fires up. as to what should be the action of this ""edit source"", i believe it should put you in the same spot you would have been if VE was not enabled. in the case you entered edit state through an editsection linkette, this means edit section.
+
+however, it is possible in this case to eat the cake and have it too, by rephrasing the original ticket, so let me try to do this:
+
+====== ORIGINAL TICKET REPHRASING ===========
+When the user press the editsection linkette and VE is enabled, a new top menu item should be generated: ""Edit section source"", next to ""Edit source"". pressing this menu item is equivalent to pressing the editsection link when VE is disabled.
+
+Not allowing this functionality basically means that there is no way to execute section edit of wikitext if VE is enabled, which, IMO, is a serious regression.
+(alternatively, pressing the ""edit source"" linkette should open a dialog asking if the user wants to edit the whole article or just the section).
+============== END REPHRASING ===============
+
+peace.",1371594513,PHID-USER-akv4ingxkspiiam6r2n4,True,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","(In reply to comment #2)
+> ""Edit Source"" never even existed before Visual Editor
+
+Not even remotely true. The ""Edit Source"" tab is the relabelling of the regular ""Edit"" tab.
+
+I'm minded to agree with This, that and the other, but willing to be convinced.",1371582534,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","(In reply to comment #1)
+> This behavior would be confusing and would break the consistency of the ""edit
+> source"" tab always going to the whole-page editor. 
+
+forgive my bluntness, but this is plain silly.
+what do you mean ""source tab always going to the whole page""? we are not discussing ""View Source"" tab, we are discussing ""Edit Source"" tab, which is something completely different.
+""Edit Source"" never even existed before Visual Editor and the reference to ""always"" does not make any sense: this project is slowly making its way from alpha to beta, and there is no ""backward compatibility"" or past behavior this thing should feel obliged to.
+
+peace.",1371581100,PHID-USER-akv4ingxkspiiam6r2n4,True,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+"VisualEditor: Switching to ""edit source"" tab within VE triggered via section-edit should be a wikitext section edit","This behavior would be confusing and would break the consistency of the ""edit source"" tab always going to the whole-page editor. 
+
+Perhaps displaying the UI of bug 49666 while in VE edit mode would be a better solution to this. I'd be interested to see the resolution of bug 47779 first though.",1371521502,PHID-USER-sx63fwaih5kjt7bz4u6z,True,PHID-TASK-4qp7cge7h2tflfmzkmov,task_subcomment,NA
+VisualEditor: Links to new pages inside templates are coloured red in the content but not a dialog iframe,"These links being red at all come about because content of templates is rendered by the PHP parser, which sets class=""new"" (Parsoid itself doesn't hint about target colour yet). However, because dialogs are implemented as <iframe>s, we can't inherit MW's CSS for the body element, so they appear differently.
+
+--------------------------
+**Version**: unspecified
+**Severity**: minor",1369932240,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yevsvpn7ps2wcpzwmbie,task_description,resolved
+VisualEditor: Links to new pages inside templates are coloured red in the content but not a dialog iframe,Now fixed as of last month.,1399324316,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-yevsvpn7ps2wcpzwmbie,task_subcomment,NA
+Implement a find/search and replace tool,"There's a search-and-replace tool in the wikiEditor which some users might miss and would like in VisualEditor somehow.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1368321420,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_description,resolved
+Implement a find/search and replace tool,"Change 174491 merged by jenkins-bot:
+Find and replace
+
+[[https://gerrit.wikimedia.org/r/174491]]",1417631052,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,Same. See the commit above.,1416824888,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,">>! In T50368#776888, @Esanders wrote:
+> For now I think the tool can go in the hamburger menu on the right.
+
+What about in non-MW integrations?",1416794975,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,For now I think the tool can go in the hamburger menu on the right.,1416791907,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,https://gerrit.wikimedia.org/r/#/c/174491/,1416791428,PHID-USER-it53o2f2kyryqyj33uzt,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"(In reply to Eran Roz from comment #12)
+> I can only think of ""Language"" and ""Replace"", so I guess we don't have
+> enougth tools right now for a new menu.
+> (or maybe the ""advanced"" options (page settings, categories etc...) is
+> actually ""tools"" menu?)
+
+We've been struggling with what to do with categories (which are pretty vital) compared to ""don't show TOC"" (which is pretty rare). Suggestions for improvements to the toolbar are always welcome. :-)",1400888389,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"I can only think of ""Language"" and ""Replace"", so I guess we don't have enougth tools right now for a new menu.
+(or maybe the ""advanced"" options (page settings, categories etc...) is actually ""tools"" menu?)",1400881097,PHID-USER-cfsvvgbtlqnbt2yokfjf,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"(In reply to Eran Roz from comment #10)
+> Yes, I would like if it would be possible to create an extra different menu,
+> instead of adding all the tools to mislabelled ""Insert"". I think the new
+> ""Language"" option will also fit here.
+
+Hmm. Possibly. I was thinking of putting it in the ""text styling"" menu, but it could live here.
+
+Is there anything else that would live in the ""Tools"" menu? (Note that the obvious items to go in a ""tools"" menu – copy, cut, paste, paste formatting – can't be done in Javascript at all, sadly.)",1400880157,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"Yes, I would like if it would be possible to create an extra different menu, instead of adding all the tools to mislabelled ""Insert"". I think the new ""Language"" option will also fit here.",1400879623,PHID-USER-cfsvvgbtlqnbt2yokfjf,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"(In reply to Eran Roz from comment #8)
+> We have a first working draft for replace tool for VE:
+> https://en.wikipedia.org/wiki/User:%D7%A2%D7%A8%D7%9F/veReplace.js
+
+This ends up in the (mis-labelled) ""Insert"" menu, right? Would it be helpful it we created a category of tool to manipulate the contents (a spelling or grammar tool might also fit here, though again it's something you'd generally expect your browser to provide)?",1398975277,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"We have a first working draft for replace tool for VE:
+https://en.wikipedia.org/wiki/User:%D7%A2%D7%A8%D7%9F/veReplace.js
+
+It works and replace the specified text, and undo&redo are properly supported (the last is just a claim that we didn't hack the VE too much :) ). 
+Currently it does only ""replace all"" but it can be easily extended with simple replace function, regexs and more... 
+We didn't ""publish"" it yet in village pumps since we want to do add at least some of this features before.",1398963768,PHID-USER-cfsvvgbtlqnbt2yokfjf,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"(In reply to Eran Roz from comment #6)
+> As part of the work on
+> [[meta:Grants:IEG/Visual_editor-_gadgets_compatibility]], I plan to work on
+> [[meta:User:Pathoschild/Scripts/Regex menu framework]], that should give a
+> quick&dirty workaround to this issue.
+
+Consider using the new version of that script instead:
+[[m:User:Pathoschild/Scripts/TemplateScript]]",1396716497,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"I agree with Amir. This is regression as this option is already available in WikiEditor and it is very basic functionality (available even in simple notepad), so it isn't an enhancement but at least normal (or major?) bug.
+
+As part of the work on [[meta:Grants:IEG/Visual_editor-_gadgets_compatibility]], I plan to work on [[meta:User:Pathoschild/Scripts/Regex menu framework]], that should give a quick&dirty workaround to this issue.",1396687246,PHID-USER-cfsvvgbtlqnbt2yokfjf,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"Somebody told me that my comment was unclear: when I say that it's a regression and not an enhancement, I mean that the *lack* of search and replace functionality is a regression, and the request to have it should be treated as a bug report and not as an enhancement request.",1396685853,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,I'd say that it's a regression and not an enhancement.,1395925189,PHID-USER-xfe43w2lb5gpvglf4coa,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,This still seems to be a popular request from users at multiple Wikipedias.,1386468820,PHID-USER-uf3buojo4ceizjywvyn5,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,*** Bug 53326 has been marked as a duplicate of this bug. ***,1377460909,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+Implement a find/search and replace tool,"As long as it doesn't have the same performance issues which makes it unusable (bug 23510), I support this. :-)",1375968089,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-l5y2bm67zzyyrk4uvrke,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"The difference between editing and reading mode isn't obvious enough for the user.
+
+(reported at http://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Alpha2013-04#Unterschied_Bearbeitungsfenster_und_gespeicherter_Artikel)
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367512020,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-e53nvp2e24hk4kjigmbx,task_description,open
+VisualEditor: There is not enough UI difference between reading and editing mode,"This seems, well, almost trivial to implement. Here's what I have in my common.css to do this when I edit:
+
+.ve-ce-surface { background: #FFFDD0; }
+
+That's a personal color choice, of course. I'd be happy to defer to the consensus of a larger group of VE users about a better color. But other than choosing a color, this seems like an enhancement that can relatively easily be put in the ""done"" category.  ",1417807160,PHID-USER-hirrhium5ibrtof34lwa,False,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"I'm with Pam on this one. Editing and reading are not two halves of the same participation at all - they are distinct activities. There should be no (or at least minimal) barriers to people participating in both but there is a fundamental difference between them.
+
+Reading Wikipedia and other Wikimedia projects is an act of consuming content. With varying degrees of interactivity you can choose which content you want to consume, and in limited ways how you want to consume it. It is possible to read Wikipedia etc in many different environments, for example using a desktop computer, handheld tablet, e-ink reader, dead-tree books even projected onto the side of buildings iirc. The reader has no responsibility to or for the content and enters into no legal agreement with anyone (although they may do so with others in order to access Wikipedia in some modes).
+
+Editing Wikipedia is an inherently interactive process of collaborative production. It entails the responsibility to abide be the legal agreement they enter into, and the requirement to not insert copyright violations, to agree to community norms, and display at least basic competence, etc. Editors must agree to be responsible for the content they enter, and so must be old enough according to one or more legal jurisdictions to assume that responsibility. It is not possible to edit Wikipedia in all modes it is possible to read it in.
+
+Look at attachment 12954 (the second attachment on bug 52004 in case that link doesn't work) for perhaps the clearest evidence about how reading and editing are fundamentally different concepts.
+
+In addition to the above there a practical difference with the way one has to behave with a reading window and editing window. When reading, I can paste a new link anywhere on the page to view a different article, or an can follow a link from anywhere in the page with no need to think about anything else; I can page down using the space bar (often convenient on this laptop), and I can simply type a few characters or words to quickly jump to a different part of the page. When editing I cannot do any of those and I need to be able to tell at a glance whether pressing tab a couple of times followed by enter will take me to the third link or will alter the formatting of the page.",1374876541,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"What's the virtue of having no difference between reading and edit mode? I see none. If I'm in editing mode, I want to be reminded that I still need to close off the edit properly (give edit summary, save page), rather than accidentally just close down all tabs, or leave the computer and let it close itself messily after x hours). I may be juggling several open windows, in connection with the one edit or with other jobs (and because the page dialog obscures the article, I'm often opening a second copy of the page while I'm in VE so that I can actually see it while adding a category or stub template, as being quicker than closing the dialog box to see the information I need). Editing and reading are two different activities: someone editing has responsibilities - not to accidentally lean on keys and produce garbage, not to leave the page without a helpful edit summary. Someone reading... is just someone reading.",1373882835,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,*** Bug 50456 has been marked as a duplicate of this bug. ***,1373852659,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"Bug 48272 should help a little, changing the browser tab and title when editing. The reporter wanted a change within the content area, such as a red border while editing.",1369192036,PHID-USER-gbl4hfak3cfurt3c7skd,False,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: There is not enough UI difference between reading and editing mode,"This is somewhat of a deliberate choice - indeed, a long term goal is to be able to have no distinction at all between 'read' and 'edit' modes (except that in one you'll have a cursor) - though we may not do this for Wikimedia's servers, and certainly not soon.
+
+I'm willing to consider suggestions about making it a little more obvious without breaking the fundamental concept that editing and reading are two halves of the same participation, but marking this as Lowest/Enhancement to reflect this.",1367547755,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-e53nvp2e24hk4kjigmbx,task_subcomment,NA
+VisualEditor: Link inspector doesn't open in Opera,"The link inspector doesn't open. Clicking the little button causes it to animate as if it was opening, then disappear completely.
+
+I'm investigating.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1367169780,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_description,resolved
+VisualEditor: Link inspector doesn't open in Opera,"Sweet, link editing is now possible. Now we just need bug 47793 fixed and Opera will be basically on par with other browsers in temrs of VE support.",1372894482,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_subcomment,NA
+VisualEditor: Link inspector doesn't open in Opera,"Change 61365 merged by jenkins-bot:
+Revert ""Address error caused by changing focus from context menu to window.""
+
+https://gerrit.wikimedia.org/r/61365",1372889290,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_subcomment,NA
+VisualEditor: Link inspector doesn't open in Opera,"Ie4f1334e is just a proof-of-concept, not really a patch yet.",1367238767,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_subcomment,NA
+VisualEditor: Link inspector doesn't open in Opera,Related URL: https://gerrit.wikimedia.org/r/61365 (Gerrit Change Ie4f1334e0beb7ba7d4f4aa3b42464fa219c4778c),1367238634,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-tsmqnxcmfpxq6jai5pux,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Something causes ve.ce.SurfaceObserver.prototype.stop() to be called without a subsequent call to ve.ce.SurfaceObserver.prototype.start().
+
+Apparently happens after clicking on a link. I'm investigating.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367169660,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_description,resolved
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),I'm hacking around mutation observers.. maybe we will get rid of SurfaceObserver soon (and get rid of those kind of problems).,1375851816,PHID-USER-s7sn3zjthnxvep34c5ho,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),Fixed a second time. Maybe. :-),1375845262,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 77639 merged by jenkins-bot:
+Actually fix bug 47793 for Opera for real this time
+
+https://gerrit.wikimedia.org/r/77639",1375845178,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 77639 had a related patch set uploaded by Matmarex:
+Actually fix bug 47793 for Opera for real this time
+
+https://gerrit.wikimedia.org/r/77639",1375650620,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),Hooray! This shouldn't be causing issues anymore now.,1375118463,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 71249 merged by jenkins-bot:
+ve.ce.Surface: Prevent focus loss on the document node in Opera
+
+https://gerrit.wikimedia.org/r/71249",1375118269,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 61358 abandoned by Matmarex:
+Don't bind 'blur' and 'focus' on the document node in Opera
+
+Reason:
+A different approach in I7962f59bd02e0.
+
+https://gerrit.wikimedia.org/r/61358",1372541828,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),"Change 71249 had a related patch set uploaded by Matmarex:
+ve.ce.Surface: Prevent focus loss on the document node in Opera
+
+https://gerrit.wikimedia.org/r/71249",1372541790,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),Gotcha. Why does Opera have to be weird...,1367235895,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start(),Related URL: https://gerrit.wikimedia.org/r/61358 (Gerrit Change Iaaa2a7993f3561dc663a064468c396ebfe951ce7),1367235847,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-bplfh6ygtxtpnfjjomyl,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,"ve.ce.Surface.getSelectionRect() throws errors in Opera. I think this is the root cause of bug 37861 and likely various other issues.
+
+It seems that rangySel.get{Start,End}DocumentPos consistently fails in Opera, because nativeRange.getClientRects() inside of the private createClientBoundaryPosGetter() function returns an empty collection. This causes the ""Cannot get position for range ..."" error to be thrown.
+
+I'm still investigating the why, I'm just putting this here. Changing getSelectionRect() to just always return some static value seems to work (or at least not fail miserably anymore).
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1367065980,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_description,resolved
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,The fix is merged now. Marking as fixed.,1367595441,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,(Done is PS2.),1367168550,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,"Hmm, apparently this also happens for non-empty selections in some cases. We're gonna need a larger workaround...",1367165002,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,Related URL: https://gerrit.wikimedia.org/r/61190 (Gerrit Change I4bad882d1d6fb83bcdcfd0de3bfc9af52960c2ff),1367082013,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,"This seems to work:
+
+>>> range = document.getSelection().getRangeAt(0)
+Range 
+>>> span = document.createElement('span')
+<span/>
+>>> range.getClientRects()
+ClientRectList []
+>>> range.surroundContents(span)
+undefined
+>>> $(span).offset()
+{ left: 352, top: 1025 }
+
+Now we just have to substract window.scrollY from the 'top' value and remove the <span> from the DOM again. (And don't call .getClientRects() on that Range again, as it returns a completely bonkers huge list of values.)",1367069662,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera,"So, what happens is that in Opera, for zero-length ranges (ie, just a caret, no selection):
+
+* .getSelection().getRangeAt(0) returns a Range
+* but then .getClientRects() returns an empty ClientRectList
+* and .getBoundingClientRect() returns a rectangle with all values being 0",1367067995,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-h4j7vw6gh3bn7a3uis4l,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**Author:** `suitongbowgn`
+
+**Description:**
+Feature request:
+
+A feature that supports insertion and simple editing of source code snippets in a general article. It may include a simple grammar checking mechanism which checks some fundamental grammatical errors such as having a { without closing it, having a () with a trailing period and nothing else, having solely a pair of brackets, etc.; an indentation correction tool which will perform indentation formatting on the codes; a beautify code tool which will reorganize code formatting, including indentation to make the code more reader-friendly in format.
+
+
+Features:
+* Insert or edit a code block.
+* Basic IDE features (perhaps re-use WikiEditor/CodeEditor)
+ * Syntax validation (matching quotes/parenthesis/braces etc.)
+ * Follow indentation level when breaking lines.
+ * Live grammar highlighting.",1366998060,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_description,resolved
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 247474 merged by jenkins-bot:
+Use Ace editor widget for code input
+
+[[https://gerrit.wikimedia.org/r/247474]]",1445528834,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 247851 merged by jenkins-bot:
+Introduce Ace editor widget
+
+[[https://gerrit.wikimedia.org/r/247851]]",1445528829,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 247851 had a related patch set uploaded (by Esanders):
+Introduce Ace editor widget
+
+[[https://gerrit.wikimedia.org/r/247851]]
+",1445443909,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 247474 had a related patch set uploaded (by Esanders):
+WIP Use Ace editor when available
+
+[[https://gerrit.wikimedia.org/r/247474]]
+",1445350934,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"A first step would be putting making an RL module for Ace in core. Each language is a separate JS file so we'd want submodules for each, like we used to do with GeSHi.",1442426303,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,">>! In T49742#1645908, @Esanders wrote:
+> I think the best approach would be to convert the editor to a dialog and drop in CodeEditor's existing code editor (Ace), or some equivalent (CodeMirror).
+
+That could work.",1442424825,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"I think the best approach would be to convert the editor to a dialog and drop in CodeEditor's existing code editor (Ace), or some equivalent (CodeMirror).",1442424794,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 114529 had a related patch set uploaded by Jforrester:
+[WIP] Add VisualEditor support
+
+https://gerrit.wikimedia.org/r/114529",1404758232,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,Re-opening as this is now unmerged.,1404758215,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,Marking this also as fixed by gerrit 68615 - congratulations again!,1380739898,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+Yes.
+
+(In reply to comment #19)
+> GSoC ""soft pencils down"" date was yesterday and all coding must stop on 23
+> September. Has this project been completed?",1379521061,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"GSoC ""soft pencils down"" date was yesterday and all coding must stop on 23 September. Has this project been completed?",1379435009,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+For now no codes from GeSHi are directly reused. I just used them as reference for regex patterns. I said 'port' due to this fact.
+
+(In reply to comment #17)
+> (In reply to comment #15)
+> > Have you considered using an existing highlighter
+> > library, or at least basing your implementation on a existing language spec
+> > format (e.g. implementing GeSHi language specs in JS?)
+> 
+> GeSHi is GPLv2+, whereas VisualEditor is MIT.  So if any GeSHi code is
+> reused,
+> the authorship and licensing should be made clear.",1378765646,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"(In reply to comment #15)
+> Have you considered using an existing highlighter
+> library, or at least basing your implementation on a existing language spec
+> format (e.g. implementing GeSHi language specs in JS?)
+
+GeSHi is GPLv2+, whereas VisualEditor is MIT.  So if any GeSHi code is reused, the authorship and licensing should be made clear.",1378765153,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+The highlighter spec is ported from GeSHi's php into js. I didn't find spec for validator so I came up with myself.
+
+(In reply to comment #15)
+> Tongbo: Re: your implmementation so far: Is the language spec something
+> you've
+> come up with yourself? Have you considered using an existing highlighter
+> library, or at least basing your implementation on a existing language spec
+> format (e.g. implementing GeSHi language specs in JS?)",1378509824,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Tongbo: Re: your implmementation so far: Is the language spec something you've come up with yourself? Have you considered using an existing highlighter library, or at least basing your implementation on a existing language spec format (e.g. implementing GeSHi language specs in JS?)",1378509073,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,CCing Andre who can give you editbugs.,1375196802,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"If you don't have permission to do it yourself, it's probably because you don't have the 'editbugs' right.  Hopefully, someone on this bug can give it you.  If not, ask on IRC.",1375163246,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Change 68615 had a related patch set uploaded by Jforrester:
+Source code editing
+
+https://gerrit.wikimedia.org/r/68615",1375162980,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+Somebody with the power could you change the bug status to assigned, and it was assigned to me.
+Also anyone who is interested please feel free to give code review at the following patch.
+
+> Related URL: https://gerrit.wikimedia.org/r/68615 (Gerrit Change
+> I4adede9e05fd2236cee50ce03f597e8ff6b1914d)",1375162735,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,Related URL: https://gerrit.wikimedia.org/r/68615 (Gerrit Change I4adede9e05fd2236cee50ce03f597e8ff6b1914d),1371190144,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Just a note to say that Tongbo Sui has submitted a GSoC proposal related to this report: https://www.mediawiki.org/wiki/User:Beanixster
+
+Good luck!",1367534348,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+In a nutshell it would be a major front-end JS work and will leave backend as-is as much as possible. I'm pretty sure that it will only utilize tags currently available and won't affect backend at all.(In reply to comment #6)",1367169151,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,Given that this is about desired enhancements to a VisualEditor plugin for the SyntaxHighlight extension - bug 43126 - moving this there and marking as a dependency.,1367002940,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+I understand that the rich text is just a presentation and I can see in article source that the formats are defined using a set of markups. What I'm proposing is a plugin/feature which will take care of write the markup(plaintext) for the user when editing code snippets, just like what VisualEditor is intended to do (in my opinion). In addition source code needs special formatting that is different from natural written human language, so that's why I think the feature should include automatic indentation and such.
+For editing just a part of the text, I'm thinking of an interface similar to a pop-up window, obscuring parts of the editing window. Just like when you insert an image the editor will have a new window pop up asking image url, alt text, target, etc. When you click insert the editor will convert your choice in that pop-up window to the plaintext with tags and other markups, which will be visually reflected in the main WYSIWYG editor.
+
+(In reply to comment #5)
+> Ah, it seems I misunderstood, sorry. I though you are talking about the
+> source
+> code *of the article itself*, and it appears like you meant source code in
+> different languages, such as what's included in a <syntaxhighlight> tag.
+> 
+> Sorry and please disregard my comments :)
+
+(In reply to comment #4)
+> Making sure that arbitrary wikitext does not interact with other parts of the
+> page is difficult. It is possible to enforce this for extension content, but
+> generally not for arbitrary parts of a page.",1367000971,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Ah, it seems I misunderstood, sorry. I though you are talking about the source code *of the article itself*, and it appears like you meant source code in different languages, such as what's included in a <syntaxhighlight> tag.
+
+Sorry and please disregard my comments :)",1367000177,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"Making sure that arbitrary wikitext does not interact with other parts of the page is difficult. It is possible to enforce this for extension content, but generally not for arbitrary parts of a page.",1367000151,PHID-USER-hbtlbu4zftxnz4i6f7yf,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"If anything, it seems like this request would build on top of that one. It's currently just not possible to edit almost anything else than plaintext in VisualEditor (and it's not just an interface issue, but a backend one as well).
+
+I'm reopening and marking as dependent on that one, then. Feel free to adjust this :)",1367000062,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"**suitongbowgn** wrote:
+
+I believe that request is too broad and this one is more specific. (In reply to comment #1)
+> 
+%%%> *** This bug has been marked as a duplicate of bug 43133 ***%%%",1366998862,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Provide basic source code editor features in VisualEditor SyntaxHighlight plugin,"
+
+*** This bug has been marked as a duplicate of bug 43133 ***",1366998592,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-ss5sivrosviwhazfuu4q,task_subcomment,NA
+Automatically propose/suggest a category for images,"Let's crush the [categorisation backlog](https://commons.wikimedia.org/wiki/User:Multichill/Categorization_stats) once and for all!
+
+some categorization could be automated already.
+
+Searching for pictures based on meta-data is called ""Concept Based Image Retrieval"", searching based on the machine vision recognized content of the image is called ""Content Based Image Retrieval"".
+
+What I understood of Lars' request, is an automated way of finding the ""superfluous"" concepts or meta-data for pictures based on their content. Of course recognizing an images content is very hard (and subjective), but I think it would be possible for many of these ""superfluous"" categories, such as ""winter landscape"", ""summer beach"" and perhaps also ""red flowers"" and ""bicycle"".
+
+There exist today many open source ""Content Based Image Retrieval"" systems, that I understand basically works in the way that you give them a picture, and they find you the ""matching"" pictures accompanied with a score. Now suppose we show a picture with known content (pictures from Commons with good meta-data), then we could to a degree of trust find pictures with overlapping categories. I am not sure whether this kind of automated reverse meta-data labelling should be done for only one category per time, or if some kind of ""category bundles"" work better. Probably adjectives and items should be compounded (eg ""red flowers"").
+
+Relevant articles and links from Wikipedia:
+
+  # [w:Image_retrieval](https://en.wikipedia.org/wiki/Image_retrieval)
+  # [w:Content-based_image_retrieval](https://en.wikipedia.org/wiki/Content-based_image_retrieval)
+  # [w:List_of_CBIR_engines#CBIR_research_projects.2Fdemos.2Fopen_source_projects](https://en.wikipedia.org/wiki/List_of_CBIR_engines#CBIR_research_projects.2Fdemos.2Fopen_source_projects)
+
+ Some demo links bawolff found:
+
+
+  # [http://demo-itec.uni-klu.ac.at/liredemo/](http://demo-itec.uni-klu.ac.at/liredemo/ ) (Lire might even be integrated with CirrusSearch because it's based on Lucene)
+  # [http://image.mdx.ac.uk/time/demo.php](http://image.mdx.ac.uk/time/demo.php)
+  # [http://mi-file.isti.cnr.it:8765/CophirSearch/](http://mi-file.isti.cnr.it:8765/CophirSearch/)
+  # [http://orpheus.ee.duth.gr/anaktisi/](http://orpheus.ee.duth.gr/anaktisi/) (not free)
+  # [https://youtube.com/2eaGwk4Xhks](https://youtube.com/2eaGwk4Xhks)
+
+
+  - Skills: image recognition/analysis, possibly Natural language processing; language depending on implementation, e.g. python for a [PWB tool](https://www.mediawiki.org/wiki/Manual:Pywikibot), JavaScript and PHP for a MediaWiki extension, JavaScript for a [tool](https://www.mediawiki.org/wiki/Tool_Labs) similar to the [Wikidata Game](http://magnusmanske.de/wordpress/?p=203).
+  - Possible mentors: Kristian Kankainen (Keeleleek); WereSpielChequers?
+  - Additional info: ""I like the idea of automating categorisation, but I think we are a long way from being able to do much of it. So this would be a big longterm project. One of my concerns is that we are a global site, and we are trying to collect the most diverse set of images that anyone has ever assembled. Image recognition is a good way of saying that we now have another twenty images of this person, but it could be confused when we get our first images of one of the fox subspecies that we don't yet have a picture of. Or rather it would struggle to differentiate the rare and the unique from their more common cousins. There are also some spooky implications for privacy re image recognition and our pictures of people, aside from the obvious things like identifying demonstrators in a crowd or linking a series of shots of one person in such a way as to identify that this photograph of a face belongs to the same person as this photo of pubic hair because the hand is identical; We have had some dodgy things happening on Wikipedia with people wanting to categorise people ethnically and I worry that someone might use a tool such as this to try and semi accurately categorise people as say Jewish. Another major route for improved categorisation is geodata, and I think this could be a less contentious route. Not that everything has geodata, but if things have it could be a neat way to categorise a lot of images, especially if we can get boundary data so we can categorise images as being shot from within a set of boundaries rather than centroid data with all its problems that the parts of one place maybe closer to the centre of an adjacent place than the centre of the area they belong to. WereSpielChequers (talk) 09:58, 20 June 2014 (UTC)""
+
+----
+Proposed in #community-wishlist-survey-2016. Received 33 support votes, and ranked #45 out of 265 proposals. [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Commons#CW2016-R045 | View complete proposal with discussion and votes here. ]]",1366602900,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_description,open
+Automatically propose/suggest a category for images,"Hi there. I did work on a proof of concept for this during the hackathon. Backend code is at https://github.com/Niharika29/imagery as Framawiki pointed out. The user script is at https://commons.wikimedia.org/wiki/User:NKohli_(WMF)/imagery.js (It needs a lot of improvements but works okay as a proof of concept). To use it, add `importScript( 'User:NKohli_(WMF)/imagery.js' );` to your common.js page and then you will see a 'Detect labels' button underneath each image on the File page for the image. Clicking that button will activate it and after a few seconds it will be replaced by features it found in the image and suggested categories.
+
+This could use a lot of feature and design improvements. I haven't heard any actual feedback on the script yet so I was waiting on that a bit. I would be more than happy to work on improving this script and eventually proposing it be a gadget, if people think that's a good idea.
+
+As for integration into MediaWiki - that would be a challenge. This script works by querying Google's image recognition service. Anything that can do feature labelling for images needs to have a huge, good, trained dataset like Google does. We'd first have to build that in order to build the extension because we do not deploy extensions which rely on external services. That's a monumental task and it will probably be years before we can get that in place. 
+",1531771716,PHID-USER-qztkawkvfnwvkspdr46l,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,@Framawiki: Is there a reason why this should preferably be implemented via a MediaWiki extension (instead of any kind of implementation)?,1531749181,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,">>! In T49492#4427133, @Aklapper wrote:
+> Someone correct me if I'm wrong: I think that @Niharika worked on this in {T155538} as can be seen in https://commons.wikimedia.org/wiki/File:Wikimedia_Hackathon_2018_showcase_-_Image_labelling_and_category_suggester.jpg ? 
+> Wondering if there is a link to a codebase to share?
+
+True, but as I remember @Niharika says during the presentation that she worked on a proof-of-concept. Backend is at https://github.com/Niharika29/imagery.
+
+Why removing #MediaWiki-extension-requests ? It would be great to have this feature integrated in mediawiki, no ? For example directly integrated into the #UploadWizard.",1531745771,PHID-USER-aswxykknolbbycawydkz,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Someone correct me if I'm wrong: I think that @Niharika worked on this in {T155538} as can be seen in https://commons.wikimedia.org/wiki/File:Wikimedia_Hackathon_2018_showcase_-_Image_labelling_and_category_suggester.jpg ? 
+Wondering if there is a link to a codebase to share?",1531745242,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Removing the  #possible-tech-projects tag as we are planning to kill it soon! This project does not seem to fit in the #outreach-programs-projects category in its current state, so I am not adding that tag right now! ",1531374696,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,I'm interested in thinking along/working on image recognition (and classification) on Commons. See also T155538.,1492719064,PHID-USER-dl5hhyukw7ernefjsgrd,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"@WereSpielChequers That sounds great! Thanks for willing to mentor :) I'm going to link your Phabricator username in the hackathon task, and if someone wants to reach out to you for questions, they can comment here or msg you on Phabricator? ",1492713320,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"I'm happy to mentor, though my availability is limited at present. Email me if a Skype chat would be useful.",1492679788,PHID-USER-a4aiqpertfr5ceq6qg2d,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"I'm adding this task here T154988. Let me know if it is not a good idea to do so :) Also, if it's fine as it is in the linked task, would someone be willing to be a point of contact/ mentor/ available to answer questions for this task during the hackathon?  ",1492645954,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,I'm adding this task here T154988. Let me know if it is not a good idea to do so :) ,1492645575,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"I'm not sure I'd call it ""standard"".  Image processing is a notoriously difficult problem.  See https://xkcd.com/1425/ for relevant discussion.  ",1488416741,PHID-USER-u64h73gx226teqcym3r5,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"@Halfak this looks like an interesting and standard ML thing. Can this be structured as a research project to do a feasibility study of methods for image category suggestions for current round of GSoC, Outreachy, RGSoC internships?",1488342572,PHID-USER-ll7x5qhzru4lqz3xfdbm,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"(NOTE) This task was proposed in the #community-wishlist-survey-2016 and in its current state needs owner. Wikimedia is participating in [[ https://www.mediawiki.org/wiki/Google_Summer_of_Code_2017 | Google Summer of Code 2017 ]] and [[ https://www.mediawiki.org/wiki/Outreachy/Round_14 | Outreachy Round 14 ]].  To the subscribers -- would this task or a portion of it be a good fit for either of these programs? If so, would you be willing to help mentor this project? Remember, each outreach project requires a minimum of one primary mentor, and co-mentor.",1488248718,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"IMPORTANT: This is a message posted to all tasks under ""Need Discussion"" at Possible-Tech-Projects. Wikimedia has been accepted as a mentor organization for GSoC '16. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.",1456853860,PHID-USER-ll7x5qhzru4lqz3xfdbm,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Hi. I am new to image recognition, so I think this could be a great learning opportunity for me. I would really appreciate it if I could get some help understanding the scope of this project and also help me find mentors, or suggest how I could get in touch with possible mentors. I am interested in applying for this project in Outreachy 11, but if that doesn't work out, I think this would still be a really great learning opportunity for me and I would like to contribute to it nonetheless. Thanks. ",1443721833,PHID-USER-stsyzohkfwbw7rep2wxj,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"The description says ""Possible mentors: Kristian Kankainen (Keeleleek); WereSpielChequers?"" CCing @werespielchequers, couldn't find Kristian.
+
+I'm also adding #Community-Tech, since this feature looks like within their scope of tools helping experienced editors. Please remove it if this is not correct.
+
+It looks like this task needs a bit of discussion to confirm that it is a good fit for #Possible-Tech-Projects. Is it a feature that is needed and the community would welcome? Is the estimated project time for a senior contributor around 2-3 weeks?",1443519573,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,Hi. I think this project is very interesting. I want to work on this in the upcoming round of Outreachy and I want to know what is expected out of me in terms of the skills and background knowledge required. Please let me know how I can contribute. Thanks. ,1443514187,PHID-USER-stsyzohkfwbw7rep2wxj,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"This is a message sent to all #Possible-Tech-Projects. The new round of [[ https://meta.wikimedia.org/wiki/Grants:IEG | Wikimedia Individual Engagement Grants ]] is open until 29 Sep. For the first time, technical projects are within scope, thanks to the feedback received at Wikimania 2015, before, and after ([[ https://phabricator.wikimedia.org/T105414 | T105414 ]]). If someone is interested in obtaining funds to push this task, this might be a good way.",1443000963,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"This is a message posted to all tasks under ""Re-check in September 2015"" at #Possible-Tech-Projects. #Outreachy-Round-11 is around the corner. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.",1442999420,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Yeah, this idea is interesting but pretty much out of scope for Bugzilla as long as it's entirely unclear how to code it.",1405685443,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,So we discuss a number of options here and it is not clear at all how to proceed. Wondering if an https://www.mediawiki.org/wiki/Requests_for_comment would be better.,1373888179,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,Is this bug also apropriate for mw extension VisualEditor ?,1373629378,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Gather display and add few more options
+
+option 6)At advance search give an option to compare and suggest a category. If selected Compare the categories also when advance search is being carried out.
+
+Have a differentlly coloured column on right hand side of search results of uncatgorised pages 
+
+
+Option 7)In special pages there is one tool called  Special:ComparePages .The tool is currently under utilised if enhanced with feature button assking to show uncategorised pages one after another. and suggesting pages for comparison . Utilisation of this good tool will improve and also rest of the data also will get improved.",1367070822,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"I came across one edit filter Filter no1(http://ja.wikipedia.org/wiki/特別:不正利用フィルター/1)  on Japanese Wikipedia it has tagged more than 80000 new uncategorised pages , the data what is already available in special pages.But here purpose of using edit filter may be to be behind page creators to add a category.This is how an avarage wikipedian looks towards imporatance of categorisation it seems.",1367069812,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Where to display options and How to insert
+
+1)Vis a Vis above first option: If a page is new or uncategorised , A button can be shown before save pages to add category.
+
+:Horizontal category option display can be provided just above save button line ,and if clicked same as in edit tools it will get added to edit window
+
+2)For option two same as First's option
+
+
+3) For third option HotCat option display as some one clicks + button 
+
+4) For fourth option to display and  add category from exmine page please also see bug no. 47497 also.
+
+5)For fifth option either like first option or a pop-up after firt few sentences are typed on a new or uncategorised page.",1367069015,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Thanks for being prompt from your side and sorry for delay from my side.
+
+
+*>>how this woould be gathered<< 
+
+1)Some part of info is already being gathered for  ""Special:Categories"" ,'Special:UncategorizedPages' and other related pages.Analyse first copule of line of categorised pages and suggest categories to un categorised pages.
+
+2)Second option is to gather information from (interwiki) Wikidata . 
+Example: Say page 'abc' and its category page 'xyz' both are common for  language 'o' and language 'p'  wikipedia + may be more other languages; say page 'efg' also is connected on more than two wikis but category 'xyz' is mentioned on some wikis and not mentioned on some wiki's 
+
+3)Third option enhancement on HotCat gadget side, when, a category is being added collect first two or three sentences of the article for statisticle comparison,or give a key line option and request editors to provide keyline  
+
+4)fourth option, having few say 5 edit filters with upto 10 keywords each and allowing edit filter manager to add category from exmine page
+
+5) Fifth option As and when Wikipedia goes for realtime editing analyse first couple of lines statistically.",1367067890,PHID-USER-azy72hrp3tpetr52aob6,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,Mahitgar: Please elaborate how this woould be gathered and displayed.,1366734764,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"Note people have done things like this before. See CommonSense on toolserver. I have no idea how that tool works or if it could be feasible to use the same method in mw.
+
+I agree with andre that how to display such information is very unclear.
+
+P.s. I don't think the original poster was referring to the CategoryTree extension when s/he said category tree.",1366617778,PHID-USER-dpu5hmqvprhycqlkdzrk,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+Automatically propose/suggest a category for images,"It's not clear to me how ""automatic suggestion"" would work - the only sentence you provide about your *expected* outcome is ""The way bugzilla suggests automated summary"".
+
+What would proposals be based on? Only checking for strings that were previously used, or do you also have other heuristics in mind?
+
+When would this be displayed, and where? Only when using CategoryTree?",1366613694,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-giw7fw2ejpup3mkxp5z7,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","The job will vote -1. But only in gate-and-submit, when working on it the tests should pass (or have this one be non-voting).
+
+--------------------------
+**Version**: wmf-deployment
+**Severity**: enhancement",1365022920,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-idlocbtqlilq2tqfojzu,task_description,declined
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","After all those years, it is not going to happen. Guess it is better handled directly in Gerrit eg via T135245.  Gerrit is replacing the draft system with private changes which would suit the WIP convention. ",1490610800,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits",T135245 propose to add a new label in Gerrit `Workflow` to let users vote -1 and prevent it from being merged.,1465209913,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","There is a patch proposed upstream:
+
+* https://review.openstack.org/#/c/251373/
+** Filter events by commit message,  Allow events to be filtered by commit messages
+
+That might  let us prevent a change from entering gate-and-submit.
+",1455277524,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","(In reply to Antoine ""hashar"" Musso (WMF) from comment #4)
+> Revisiting after a while: Zuul does not have support to prevent merge based
+> on a the content of the commit message.
+
+Really?  The Jenkins jobs have a full git checkout, so presumably you could write a jenkins job for gate-and-submit that runs:
+
+git log --oneline | head -1 | fgrep -q WIP
+
+The actual test would be a little more complicated, since you'd want to be sure you were looking at the right side of a merge commit, but either HEAD^1 or HEAD^2 would name the actual patch you're committing in that case.",1416436916,PHID-USER-m2ezqyeb4uz67zq6bats,False,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","Revisiting after a while: Zuul does not have support to prevent merge based on a the content of the commit message.
+
+A possibility is to use Code-Review: -2 which will effectively prevent Gerrit from submitting the patch.
+
+Another way would be to add a new label in Gerrit that would be used to flag a change has being in progress which would trigger the gate-and-submit when voted +1. Something like:
+
+ Approval:
+  +1 Approved
+   0 Pending review
+  -1 Work in progress
+
+Timo thoughts? Or should we just abandon this idea?",1400511546,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits",*** Bug 53405 has been marked as a duplicate of this bug. ***,1377672091,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","Looking at the dashboard of VisualEditor extension that makes a lot of sense :)
+
+https://gerrit.wikimedia.org/r/#/projects/mediawiki/extensions/VisualEditor,dashboards/default
+
+$ git-review -l|egrep '(WIP|MERGE)'
+70560  master  [WIP] Language Inspector Prototype                          
+71641  master  [DON'T MERGE] Remove 'mw-editsection-bracket' hack    
+71285  master  [WIP] Do not allow to resize thumb image to be bigger than original file
+70346  master  [DON'T MERGE] Rich Copy and Paste from External Source
+69796  master  [DON'T MERGE] Rich paste from external sources         
+71661  master  [WIP] ve.dm.Transaction: Implement newFromDocumentInsertion, take 2
+70981  master  [WIP] Math Node UI
+68615  master  [WIP] Source code editing
+70171  master  [WIP] Math Node Matcher
+69281  master  [WIP] Link surface fix for RTL
+$",1372883700,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+"Jenkins: Set up job in gate-and-submit to avoid submitting ""DRAFT"" or ""WIP"" commits","I would prefer we do not rely on the commit summary having WIP or DRAFT in it, though we might warn about it.
+
+OpenStack has a patch for Gerrit (might have been upstreamed), that let you flag a change has being a work in progress (see original feature request https://bugs.launchpad.net/openstack-ci/+bug/902953 ).
+
+
+From Gerrit 2.5 release-notes, the drafts do not send patchset-created events so they should not trigger any job.  When they are published we have a new `draft-published`  event which is essentially the same as patchset-created.
+
+
+I guess voting CodeReview +2 on a draft will thus send no event at all and the change will obviously never enter any pipeline.",1365577705,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-idlocbtqlilq2tqfojzu,task_subcomment,NA
+VisualEditor: Plugin editors to be created (tracking),"This is a tracking bug for the creation of VisualEditor plugin editors, for each of which the primary bug should live in that product/component instead (where they're about an existing Extension etc.).
+
+This task has been replaced by #VisualEditor-MediaWiki-Plugins
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1364926560,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_description,resolved
+VisualEditor: Plugin editors to be created (tracking),Replaced by the #VisualEditor-MediaWiki-Plugins project.,1422424777,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_subcomment,NA
+VisualEditor: Plugin editors to be created (tracking),"(In reply to Elitre from comment #2)
+> For documentation, see https://www.mediawiki.org/wiki/VisualEditor_gadgets.
+
+No, that doesn't document how to create a proper VisualEditor plugin; the gadgets system uses a different way to work.",1415898284,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_subcomment,NA
+VisualEditor: Plugin editors to be created (tracking),"For documentation, see https://www.mediawiki.org/wiki/VisualEditor_gadgets.",1415894243,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_subcomment,NA
+VisualEditor: Plugin editors to be created (tracking),"Setting to ""Lowest"" priority as in general the WMF VisualEditor team won't itself be creating these, but instead helping others do so.",1364926707,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-sqaxwrwatnj3ric4i2qs,task_subcomment,NA
+no language links shown in edit mode,"When you are editing an article the language links from Wikidata are not shown in the sidebar. Local links are shown.
+
+(Reported at https://en.wikipedia.org/wiki/Wikipedia_talk:Wikidata/Archive_1#No_interwiki_links_when_you_are_in_edit_mode%3F)
+
+**See Also**:
+{T48488}
+{T63768}",1362396060,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-xb522jegn4symvyf4f4u,task_description,resolved
+no language links shown in edit mode,Thanks for checking! It might have been fixed in the meantime then. Let's close it.,1644158450,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,"If I open https://en.wikipedia.org/wiki/Zdravets,_Varna_Province for editing and hit {nav Show preview} using the 2010 wikitext editor and legacy Vector, I see language links in the sidebar, even though none are specified in wikitext, only through Wikidata. @Lydia_Pintscher, could you please provide specific steps to reproduce, or close this ticket if you can’t reproduce it anymore either?",1644154172,PHID-USER-ocqnoktaualicuvge2tu,False,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,Should this still be fixed? see {T160931},1503080071,PHID-USER-3wfzrv2a2ggwauxc52is,False,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,Still an issue in wikitext editor.,1492960800,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,*** Bug 58518 has been marked as a duplicate of this bug. ***,1387190061,PHID-USER-7n5fvppwj4ueprv2iuys,False,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+no language links shown in edit mode,"Tested on fiwiki: Language links are shown when you click ""Show preview"". In VisualEditor, they are shown immediately. Is this enough?",1383629823,PHID-USER-pxpu4muyuyvybjioj2la,False,PHID-TASK-xb522jegn4symvyf4f4u,task_subcomment,NA
+"Create a ""zen mode""/""Distraction free mode"" MediaWiki extension","Perhaps might be nice in MediaWiki core, but would definitely be nice as at least a MediaWiki extension, we should implement a ""zen mode"" capability from ?action=edit.
+
+GitHub and it seems like the Cloud9 IDE both have this mode. It's demonstrated here: <https://docs.c9.io/zen_mode.html>.
+
+In short, in the case of GitHub, it appears to be a bit of JavaScript that adds a ""zen mode"" button to the UI. When the user clicks this button, the non-essential page elements are hidden from the page, allowing the user to focus on the textarea (or other central input area) alone. Basically it reduces the amount of noise on the page in order to increase the signal.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+https://bugzilla.wikimedia.org/show_bug.cgi?id=14501",1361595420,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-edwajw6htxppl743yg5e,task_description,open
+"Create a ""zen mode""/""Distraction free mode"" MediaWiki extension",So... I like the way that Phabricator does full screen. It's probably more accurately called full browser window. I think we should steal the (idea of) their code and put it in MediaWiki core. It can't be that much JavaScript... and then the wikitext edit toolbar (WikiEditor?) and the VisualEditor toolbar can be modified to expose this full browser window functionality. Does that seem reasonable?,1427761367,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-edwajw6htxppl743yg5e,task_subcomment,NA
+"Create a ""zen mode""/""Distraction free mode"" MediaWiki extension","Could easily be done as a gadget, rather than a extension.",1361616078,PHID-USER-dw53c5cb2qfhyemej57o,False,PHID-TASK-edwajw6htxppl743yg5e,task_subcomment,NA
+"Create a ""zen mode""/""Distraction free mode"" MediaWiki extension","Also knows as ""Distraction free mode"", e.g. in Sublime Text 2:
+
+http://www.sublimetext.com/docs/2/distraction_free.html",1361613794,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-edwajw6htxppl743yg5e,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","**Author:** `Coiby.Xu`
+
+**Description:**
+I try a clean install of MW 1.20.2 and also install VE and Parsoid extension. When click ""VisualEditor"" button, the VE doesn't appear and there's a js error: ""Uncaught TypeError: Cannot read property 'error' of null"".
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1357988100,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_description,declined
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them",Now that 1.23.x is released I suppose this is unnecessary.,1404436245,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","(In reply to comment #8)
+> I would suggest creating a backport and then ask for a review of it.  If a
+> person can be found to implement and support the backport, I don't have a
+> problem with shipping a 1.19 with it.
+
+Thanks Mark; marking as lowest priority as (as said above) WMF won't be working on this, but if a third party would like to we'd be happy to help them out.",1366906626,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","(In reply to comment #6)
+> Copying Mark - Mark, what's policy for backporting functionality changes in
+> core so that people can use extensions?
+
+Andre is right -- depends on the complexity.  We did have some discussion of this on Wikitech-l, but I don't think a final decision was made.
+
+I would suggest creating a backport and then ask for a review of it.  If a person can be found to implement and support the backport, I don't have a problem with shipping a 1.19 with it.",1366902873,PHID-USER-ogbcrxm45oo3n3xe5q25,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","(In reply to comment #6)
+> Copying Mark - Mark, what's policy for backporting functionality changes in
+> core so that people can use extensions?
+
+James: Have specific commits been identified? 
+I guess it highly depends on the complexity of the task...",1366892475,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","Copying Mark - Mark, what's policy for backporting functionality changes in core so that people can use extensions?",1366665631,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","**Coiby.Xu** wrote:
+
+Suddenly VE gave such error:""Uncaught TypeError: Cannot call method 'enable' of null"" while it was normal a few days. I'm not sure if that error is related to this bug.",1359041505,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","**Coiby.Xu** wrote:
+
+Not really, I find it works on 1.20.0 :)
+> This is correct - minimum current version of MW for the VE code is 1.21/wmf5
+> (and this may go up as we add more functionality to MW core so that VE can
+> work; it is possible that these changes will get back-ported to 1.19 and 1.20
+> by some volunteers, but we at WMF won't be looking at this whilst the
+> extension
+> is still in an experimental stage.
+> 
+> Will change this to an enhancement for that to be done, with low priority
+> (reflecting that if a volunteer wants to do it, that'd be great).
+> 
+> See my comment on the wikitech-l mailing list thread:
+> http://lists.wikimedia.org/pipermail/wikitech-l/2013-January/065532.html
+> 
+> Have added this to the Extension page on MediaWiki.org - 
+> https://www.mediawiki.org/w/index.php?title=Extension:
+> VisualEditor&diff=628258&oldid=610234",1358149634,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","**Coiby.Xu** wrote:
+
+Hi Andre,
+The skin I use is Vector. This Mediawiki is in the local network thus can't be accessed from outside:(
+The version of VE is 72c121684c6edb6ab580258676759f62e3efd471 and Parsoid's is aa34a80a6e43fe4fe6c5a95b465bf10dee3ed922.
+> Hi Coiby,
+> which user interface skin do you use?
+> Is this MediaWiki installation publicly accessible somewhere?
+> Which versions of VE and Parsoid versions do you use?",1358149479,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","This is correct - minimum current version of MW for the VE code is 1.21/wmf5 (and this may go up as we add more functionality to MW core so that VE can work; it is possible that these changes will get back-ported to 1.19 and 1.20 by some volunteers, but we at WMF won't be looking at this whilst the extension is still in an experimental stage.
+
+Will change this to an enhancement for that to be done, with low priority (reflecting that if a volunteer wants to do it, that'd be great).
+
+See my comment on the wikitech-l mailing list thread: http://lists.wikimedia.org/pipermail/wikitech-l/2013-January/065532.html
+
+Have added this to the Extension page on MediaWiki.org - 
+https://www.mediawiki.org/w/index.php?title=Extension:VisualEditor&diff=628258&oldid=610234",1358117818,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+"VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them","Hi Coiby,
+which user interface skin do you use?
+Is this MediaWiki installation publicly accessible somewhere?
+Which versions of VE and Parsoid versions do you use?",1358100484,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-utiy7prmp4a62qvvpo6d,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Hieroglyphics blocks,"<hiero>....</hiero> is unparsed but shown as plain wikitext:
+https://en.wikipedia.org/wiki/User:Raymond/hiero
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**URL**: https://en.wikipedia.org/wiki/User:Raymond/hiero",1355479200,PHID-USER-3uecblbxq24ycewm2cog,False,PHID-TASK-flnjgejb5tcqxovz54rt,task_description,open
+Create a VisualEditor plugin tool to add/edit Hieroglyphics blocks,"Moving this back to WikiHiero for writing the VisualEditor rich editor, if someone ever wants to do this (the basic source one is now done).",1376115313,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-flnjgejb5tcqxovz54rt,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Hieroglyphics blocks,"The above tag lets you edit the hiero syntax and preview it.
+
+This could be further extended to provide a hiero IME, but that's not going to be on our priority list any time soon.",1375554659,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-flnjgejb5tcqxovz54rt,task_subcomment,NA
+Create a VisualEditor plugin tool to add/edit Hieroglyphics blocks,"Hieroglyphics support.
+
+https://gerrit.wikimedia.org/r/77508",1375554460,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-flnjgejb5tcqxovz54rt,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,"Puppet config for wikibugs:
+
+https://gerrit.wikimedia.org/r/gitweb?p=operations/puppet.git;a=blob;f=manifests/misc/wikibugs.pp
+
+Puppet config for gerrit-wm:
+
+https://gerrit.wikimedia.org/r/gitweb?p=operations/puppet.git;a=blob;f=manifests/gerrit.pp
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1354738560,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ciosa56mnibqn4lx27ub,task_description,resolved
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,"Change 37570 abandoned by Jforrester:
+wikibugs: Set up #mediawiki-visualeditor
+
+Reason:
+We gave up and moved to using pywikibugs instead.
+
+https://gerrit.wikimedia.org/r/37570",1398113588,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,"Change 54984 abandoned by Jforrester:
+Filter VisualEditor product to new mediawiki-visualeditor.log
+
+Reason:
+We gave up and moved to using pywikibugs instead.
+
+https://gerrit.wikimedia.org/r/54984",1398113560,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,The bugs are now being reported in #mediawiki-visualeditor by pywikibugs.,1398113038,PHID-USER-muirnivxp5hzppn2a3z7,True,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,Related URL: https://gerrit.wikimedia.org/r/54984 (Gerrit Patch-Set: I04e82cb392f1ad680db6c469f76fb717d435c20d/1),1363816716,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,Related URL: https://gerrit.wikimedia.org/r/37570 (Gerrit Patch-Set: Id7405c8ee9a8658ed7afae844a870e0253a73806/4),1363816181,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,"gerrit-wm is done, but wikibugs is ""an almighty pile of crap"" and would need major work; moving to Lowest.",1360206228,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+Setup wikibugs and gerrit-wm for #mediawiki-visualeditor,Attempted fixes in Gerrit 37566 and Gerrit 37570.,1354926921,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ciosa56mnibqn4lx27ub,task_subcomment,NA
+VisualEditor: Two replacements within the same transaction and the same paragraph cause change markers to be off,"Test case:
+
++                       'removing then inserting a character': {
++                               'calls': [
++                                       ['pushRetain', 41],
++                                       ['pushReplace', ['i'], []],
++                                       ['pushReplace', [], ['j']]
++                               ],
++                               'expected': function ( data ) {
++                                       data[41] = 'j';
++                                       ve.setProp( data[37], 'internal', 'changed', 'content', 2 );
++                               }
+                        }
+
+This sets the second change marker on data[36]. This happens because the start offsets handled in TransactionProcessor.replace are translated using this.adjustment , but that glosses over the fact that not all adjustments captured in this.adjustment actually apply if the offset is before the cursor. Instead, we need some sort of offset translation. I tried using ve.dm.Transaction.translateOffset() but that doesn't seem to work out of the box very well.
+
+I guess theoretically this might also be an issue with other uses of .start attributes in the replacement processor, but it hasn't led to issues so far.
+
+Low prio because we currently don't generate transactions that trigger this case.
+
+--------------------------
+**Version**: unspecified
+**Severity**: major",1353134520,PHID-USER-fovtl67ew4l4cc3oeypc,False,PHID-TASK-guukovmsjsnlpphgujcv,task_description,invalid
+VisualEditor: Two replacements within the same transaction and the same paragraph cause change markers to be off,With bug 45061 all change marker code has been removed.,1360975473,PHID-USER-it53o2f2kyryqyj33uzt,False,PHID-TASK-guukovmsjsnlpphgujcv,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface","To quote Roan:
+
+| LQT hijacks section=new via the PerformAction hook, but it doesn't make
+| any attempt to hijack section=new in the API. Instead, LQT has its own
+| API for posting things
+
+This leads to tools that use the edit API (such as the Feedback tool) being incompatible with LQT.
+
+--------------------------
+**Version**: master
+**Severity**: normal
+**See Also**:
+* {T54729}
+* {T35260}
+* {T59989}",1350927300,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uztlkap77g3rnibwjzla,task_description,open
+"LQT should intercept ""section=new"" edits through API as well as skin interface","LiquidThreads has been replaced by #Flow on all Wikimedia production wikis (except one, which will be done soon). It is no longer under active development or maintenance, so I'm re-classifying all open LQT tasks as ""Lowest"" priority.",1470353658,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface",">>! In T43276#838397, @He7d3r wrote:
+> Is this solved by Flow?
+
+No. Flow's version of this same problem is {T59989}.",1418237342,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface",Is this solved by Flow?,1418237275,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface",See also [[mw:Thread:VisualEditor/Feedback/Eror on Feedback?]],1378924102,PHID-USER-sryrz6tgcfnnsiddx32p,True,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+"LQT should intercept ""section=new"" edits through API as well as skin interface","I guess LQT extension must be a good citizen and get along with other extensions? Under the exclusivity is there by design, this looks more like a bug (and a major one) rather than an enhancement request.
+
+Setting to ""Normal"" because I lack the background. Feel free changing to Major if you agree that blocking other extensions deserves that.",1363708216,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-uztlkap77g3rnibwjzla,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"More or less related to bug 41147 (T43147). Iceweasel team may consider Mozilla's ESR version in their forking work. However that bug was turned into talk about Firefox forks, so I start a new bug here.
+
+Firefox is said to have an ""Extended Support Release""[1] which is recommended to be used ""by enterprises, public institutions, universities and other organizations that centrally manage their Firefox deployments""[2] by Mozilla. We may want to support that version too (just an older Firefox with security bugs fixed AFAIS).
+
+[1] http://en.wikipedia.org/wiki/History_of_Firefox#Extended_Support_Release
+[2] http://blog.mozilla.org/blog/2012/01/10/delivering-a-mozilla-firefox-extended-support-release/
+",1350761460,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_description,declined
+VisualEditor: Support Firefox 10-14,"Per T266866, the support for Firefox 10-14 has been dropped. Declining this task is long overdue.",1644737571,PHID-USER-bf7nnwcm4i6wicvxtb77,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"Per {T266866}, the support for Firefox 10-14 has been dropped. Declining this task is long overdue.",1616112511,PHID-USER-bf7nnwcm4i6wicvxtb77,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"> Maybe that bug can be reconsidered as ""Support Firefox ESR version"". That is currently version 52 released in March 2017.
+
+No. That milestone was reached in mid-2013. This is specifically about very old Firefox versions. It's possible someone might want to do this in the future.",1513027210,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"Firefox 10-14 are from the past.
+
+From https://analytics.wikimedia.org/dashboards/browsers/#all-sites-by-browser/browser-family-and-major-hierarchical-view
+
+In percent of Firefox traffic:
+
+
+| v10 | 0.29%
+| v52 | 8.9%
+| v56 | 17%
+| v57 | 65%
+
+Maybe that bug can be reconsidered as ""Support Firefox ESR version"". That is currently version 52 released in March 2017.
+",1513022862,PHID-USER-orzyp3dswemhdgdznro5,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,">>! In T43245#1161468, @Krenair wrote:
+> Do we know how many people are still using our sites with 10-14?
+
+In Dec 2014, [[ https://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm | 305.8 M total requests ]].",1427706781,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"Are we still interested in supporting these versions? FF ESR 24.8.0 is EOL now, based on the chart at https://www.mozilla.org/en-US/firefox/organizations/faq/
+Do we know how many people are still using our sites with 10-14?",1427703276,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,Re-labelling this to be about supporting Firefox versions 10-14; 15+ (inc. ESR 17 and ESR 24) should work fine.,1386182693,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"(In reply to comment #5)
+> The new warning about VE being in beta stage is not fully readable with this
+> browser. This said, it might be interesting to know whether support is coming
+> at some point or this is going to be closed as ""won't fix"". Thanks.
+
+Note that the current ESR version of Firefox is 17 now instead of 10. What does your ""this browser"" refer to?",1375475479,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"The new warning about VE being in beta stage is not fully readable with this browser. This said, it might be interesting to know whether support is coming at some point or this is going to be closed as ""won't fix"". Thanks.",1375475270,PHID-USER-wil4b5lylrvf3krixlkl,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"(In reply to comment #3)
+> VE deployment is planned for up to the end of June 2013.
+> 
+> According to
+> https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal#Proposal
+> the end of life for Firefox 10.0.x is planned for February 12, 2013. That's 13
+> weeks from now.
+
+Considering this timeframe issue, it looks fine to me not to support 10.0.x ESR currently. But in
+
+http://www.mediawiki.org/wiki/VisualEditor/2012-13_Q1_forward-look#cite_note-FirefoxLater-3
+
+I see ""VE team roughly intend to support the current, soon-to-be-current, and immediately previous versions only."" and this bug is asking VE team not to treat ESR versions as ""outdated versions"" but ""current version"" in another ""branch"".",1352072123,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"The last comment is a general ""Do we allow unsupported browsers to use VE"" question. It's not specific to supporting Firefox ESR versions.
+
+To put this into context:
+
+https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals#Visual_Editor states: ""Q2 (October-December 2012):
+First English Wikipedia deployments and iteration (New Page creation is not an ideal candidate here because of required support for things like a VE citations to ensure page survivability)"".
+VE deployment is planned for up to the end of June 2013.
+
+http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm shows a 0.52% rate for Firefox 10.0 (which will likely decrease in the future).
+
+According to https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal#Proposal the end of life for Firefox 10.0.x is planned for February 12, 2013. That's 13 weeks from now.
+
+Though there are enough internet users who run unsupported vulnerable old software versions I'd say it's arguable if it makes sense to allow FF 10.0.x as it will be rather dead soon anyway.
+
+For the time being, feedback from testing VE on FF 10.0.x would be useless and not interesting for VE developers. If VE in 10.0.x turns out buggy, Wikimedia would get blamed for a non-functional VisualEditor and would receive feedback to ""fix it please!"", instead of the browser vendor for its old version.
+
+So at the current state I don't consider adding &vewhitelist helpful for anybody. Proposing WONTFIX again.
+
+Comments?",1352066239,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"(In reply to comment #1)
+> Mozilla's internal LTS-like arrangements do not mean that the rest of the Web
+> must dance to their tune. Quite the reverse; it means that they have committed
+> to keeping a particular primary version of their browser ""up-to-date"" by
+> back-porting security and other fixes.
+> 
+> If we target VE working for modern versions of Firefox, then Firefox ESR should
+> happen to work; if it does not, that is a flaw that the Firefox development
+> team are responsible for back-porting, and there would be nothing for us to do.
+
+Yes ESR versions may work but even if it always work with all required features, the whitelist keeps blocking it from working unless &vewhitelist is added.",1351973975,PHID-USER-zjzhrhmn36icnzbckqy4,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+VisualEditor: Support Firefox 10-14,"As listed on bug 41147, our browser matrix is https://www.mediawiki.org/wiki/VisualEditor/2012-13_Q2_forward-look#Browser_matrix - right now, we are not likely to expand this list, though as previously stated, we'd look at including pushes from others. Browsers that are not ""supported"" are still likely to work, but we will not stand behind them as working before code is released.
+
+Mozilla's internal LTS-like arrangements do not mean that the rest of the Web must dance to their tune. Quite the reverse; it means that they have committed to keeping a particular primary version of their browser ""up-to-date"" by back-porting security and other fixes.
+
+If we target VE working for modern versions of Firefox, then Firefox ESR should happen to work; if it does not, that is a flaw that the Firefox development team are responsible for back-porting, and there would be nothing for us to do.
+
+Clearly there are levels of reasonableness about this, and we won't attempt to stop things working or make changes that cause it for no good reason.",1350939146,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2u5uxjiqhth3znfq26qw,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","I am after removing a bit of clutter from show_bug.cgi.
+
+Mobile team prefers to keep Mobile Platform separate from Platform:
+""we don't want *any* desktop os in the platform, they're useless to us. it'll be pure noise to have the desktop os list.""
+
+Hence we should show the ""Mobile Platform"" custom field only for products ""Wikipedia App""/""Wiktionary App""/""WikiLoves Monuments Mobile"" and for component ""MobileFrontend"".
+This requires Bugzilla 4.2 as per https://bugzilla.mozilla.org/show_bug.cgi?id=479400 .
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350610560,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_description,declined
+"Display ""Mobile Platform"" custom field only for relevant products/components","Wikimedia has migrated from Bugzilla to Phabricator. Learn more about it here: https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla - This task does not make sense anymore in the concept of Phabricator, hence closing as declined.",1416786013,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","Based on data how rarely this field has been set in the last 12 months (except for by the reporter and the bugwrangler), I am very tempted to just hide 
+* field_label_cf_platform
+* field_container_cf_platform
+via ""display:none"" in CSS for the time being, wait if anybody will actually complain, and if nobody complains disable it entirely.",1398152893,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","...by the way, Bugzilla query to see which reports use the ""Mobile Platform"" field is https://bugzilla.wikimedia.org/query.cgi?format=advanced and setting ""Custom Search"" to ""Mobile Platform | is not equal to | ---"".",1357924202,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","Looking at this again, I wondered if there are cases apart from aforelisted components when the field is set. 
+There are, especially when ""Hardware"" is set to ""Tablet PC"":
+https://bugzilla.wikimedia.org/buglist.cgi?bug_id=43748,43414,43101,41984,38420,37875,38393,37160
+
+Hence this is maybe not a good idea, and I currently think I shouldn't pursue this idea.",1357924024,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","Now that we have upgraded Bugzilla to 4.2 we can define more than one product XOR product/component when a custom field (like ""Mobile platform"") should be shown.
+
+Proposing to show ""Mobile platform"" only for:
+
+* Commons App / General
+* MediaWiki extensions / MobileFrontend
+* MediaWiki extensions / MobileFrontend (Beta)
+* MediaWiki extensions / ZeroRatedMobileAccess
+* Tools / WikiSnaps
+* WikiLoves Monuments Mobile / Browse
+* WikiLoves Monuments Mobile / General
+* WikiLoves Monuments Mobile / Login
+* WikiLoves Monuments Mobile / Maps
+* WikiLoves Monuments Mobile / Upload
+* Wikimedia / WAP mobile gateway
+* Wikimedia Mobile / Content
+* Wikimedia Mobile / devices
+* Wikimedia Mobile / Generic
+* Wikimedia Mobile / Retired (Ruby) Gateway (DO NOT USE)
+* Wikipedia App / Automated Builds
+* Wikipedia App / Generic
+* Wikipedia App / History
+* Wikipedia App / Localization/Translation/Language
+* Wikipedia App / Media Uploads
+* Wikipedia App / Near by
+* Wikipedia App / Save Article
+* Wikipedia App / Search
+* Wikipedia App / Settings
+* Wikipedia App / Share
+* Wikisource App / General
+* Wiktionary App / Wiktionary",1354729486,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+"Display ""Mobile Platform"" custom field only for relevant products/components","Current situation and diffusion:
+
+* ""Wikimedia Mobile"" is closed for new bug entries. Good.
+* Several mobile apps exist, such as
+  WikiLoves Monuments Mobile
+  Wikipedia App
+  Wiktionary App
+  Commons Mobile App
+* Tools/WikiSnaps exists, which is a mobile app.
+* VisualEditor/Mobile should likely should also show this field.",1351280229,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-yo4pzdo2eh7soywdrv2r,task_subcomment,NA
+Add unsubscribe links to email notifications,"Please add ""unsubscribe"" links to these:
+
+
+>>>>> ""MM"" == MediaWiki Mail <wiki@wikimedia.org> writes:
+MM> Hi Jidanni,
+
+MM> this is a notification from MediaWiki that a new thread on Talk:Download from Git, 'Update error',
+MM> was created on 14 October 2012 at 03:30 by Lukas9950
+
+MM> You can see it at <http://www.mediawiki.org/w/index.php?title=Talk:Download_from_Git&offset=20121013193053&lqt_mustshow=19695#Update_error_19695>
+
+MM> The text is:
+MM> When I want to update all extensions, I get an error.
+
+MM> sh-4.1$ git submodule update --init
+MM> fatal: reference is not a tree: 655d019b84689e37b3fb1018600f629c657fb575
+MM> Unable to checkout '655d019b84689e37b3fb1018600f629c657fb575' in submodule path 'Persona'
+MM> sh-4.1$
+
+MM> Anyone can help me with this?
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1350158820,PHID-USER-awbqewknju4hbrnah6pm,False,PHID-TASK-hs2662uteqpf2jylzi43,task_description,declined
+Add unsubscribe links to email notifications,"This is already provided:
+
+Your friendly translatewiki.net notification system
+
+--
+To change your email notification settings, visit
+https://translatewiki.net/wiki/Special:Preferences
+
+To change your watchlist settings, visit
+https://translatewiki.net/wiki/Special:EditWatchlist
+
+To delete the page from your watchlist, visit
+https://translatewiki.net/w/i.php?title=Summary:Support/About_Wikia:Wikia-visualeditor-dialog-wikiamediainsert-upload-label/en_(3)&action=unwatch
+
+Feedback and further assistance:
+https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents",1402005852,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+Add unsubscribe links to email notifications,"Yes, but consider a user who has left a project for several years.
+He would be looking for 'to unsubscribe' links, and nothing more technical...
+However 'Configure bugmail' I suppose is better than nothing, agreed.",1350163279,PHID-USER-awbqewknju4hbrnah6pm,False,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+Add unsubscribe links to email notifications,"I was trying to be helpful. I disagree from your last statement. Copying the notification I got for your last comment:
+
+Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
+------- You are receiving this mail because: -------
+You are on the CC list for the bug.",1350162916,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+Add unsubscribe links to email notifications,"Yes, all that needs to be added *within* the email.
+More importantly, a ""standard"" explanation ""of how to unsubscribe"" needs
+to me added to such emails.
+
+Indeed, even this bugzilla needs it.",1350159872,PHID-USER-awbqewknju4hbrnah6pm,False,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+Add unsubscribe links to email notifications,You can unwatch that thread to stop receiving email notifications. Or disable on your preferences «E-mail me on replies to a thread I am watching»,1350159071,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-hs2662uteqpf2jylzi43,task_subcomment,NA
+[DO NOT USE] Support tables (tracking) [superseded by #VisualEditor-Tables],This was a tracking bug when tasks were managed in Bugzilla. It has been replaced by the #VisualEditor-Tables project.,1345761660,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-ov5tmb6ogxr2kfhnpik4,task_description,invalid
+[DO NOT USE] Support tables (tracking) [superseded by #VisualEditor-Tables],"**tomte** wrote:
+
+By teaching groups for Wiki editing I found WYSIWYG support for tables most important. 
+
+Even elder people I can get accoustomed to markups like bold, links, headers / TOC, bullets, categories etc without WYSIWYG, but not for tables.
+
+Editing Wiki tables in Libre Office makes them huge and no longer editable manually.
+
+So table support is not just an option but a minimum feature  - the ""condition sine qua non"" -  for WYSIWYG support. 
+tomte , Member 542126 in WikiMedia Deutschland",1374741668,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-ov5tmb6ogxr2kfhnpik4,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","From user suggestion, along the lines of how Microsoft Word works.
+
+This would involve a number of language-specific substitutions (and probably some shared ones); for English, I believe it would at least involve:
+
+* If a user types the character string 'foo ""bar', on the pressing of the 'b' it would convert the '""' character to a an &ldquo;.
+* If a user types the '""' character whilst in a string that has an &ldquo; in it earlier, convert the character to an &rdquo;.
+* If a user types in ' - ', on the pressing of the space character after the hyphen, covert the hyphen to an &endash;.
+* If a user types in ' -- ', on the pressing of the space character after the second hyphen, covert the two hyphens into one &emdash;.
+
+Worth considering as a nice to have; this would probably want to be both site-configurable (is it available at all; if yes, is it default-on), and user-configurable.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1343329080,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_description,open
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","Hm, fair enough. Sounds a bit English-centered, but I get that the number of potentially supported/affected languages is a fact that should not be overlooked. I am indeed using Schnark’s tool and it works fine overall (except for single quotation marks, but even MS Word still can’t deal with those, so I guess there is no proper solution), also for other languages than German. As always with such tools, I just do believe that they would be most useful for new editors, and like this there is a only a small chance that they would find out about and start using it by themselves. That leaves us once again with lots of unnecessary corrections all over the articles. Furthermore, with every year that passes, the chance that some wikis might want to start “enforcing” proper typography is diminishing; I had a long discussion on itWP years ago about the issue and it was clear that without a generally available autocorrect function nobody would be willing to change the typography rules. I guess with autocorrect available from the beginning, even the (to say the least: debatable) MoS rule on enWP would not exist in this form.
+
+Anyway, I get why we are at this point, but it’s very unsatisfying.",1578572545,PHID-USER-zrh22rct2jo5hs6nu67r,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","VisualEditor now has a framework for implementing autocorrection (and more generally, doing things in response to specific text being typed). In VE we mostly use it to add wikitext-inspired shortcuts for certain features, e.g. opening the link dialog when typing `[[`, inserting a bullet list when typing `* `.
+
+I know of one script that used it to implement autocorrection rules for German: https://de.wikipedia.org/wiki/Benutzer:Schnark/js/veAutocorrect.js
+
+However, doing it for the 100+ supported MediaWiki languages would be a lot more work, and personally I'd be afraid that it would be //really annoying// if it was done wrong. Or even if it was correct, but against the style accepted by a given wiki's community: for example, English Wikipedia prefers to use straight quotation marks: https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style#Quotation_marks
+
+I don't think we want to take responsibility for writing and maintaining that at this time.",1578534992,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)",We have several user scripts that do exactly what is requested here. Maybe take some ideas from them? The feature should be available for everyone and would prevent a lot of unnecessary typographical corrections.,1578223639,PHID-USER-zrh22rct2jo5hs6nu67r,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)",Anything going on? It's high time that typography is corrected automatically; I don't get how you can classify this as lowest priority!,1476643032,PHID-USER-zrh22rct2jo5hs6nu67r,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","I actually can't promise that I'll implement this soon, so I'm unassigning myself; sorry. I'm still interested in this, and proper typography on the wikis in general :)",1430348486,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","For German, that would mean changing """" in „“, like it is being suggested at de.wp.",1404019929,PHID-USER-wil4b5lylrvf3krixlkl,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","en.wp user Ruud Koot requests ""--"" be converted to endash and ""---"" to emdash, which is slightly different to comment 0.",1375956377,PHID-USER-ysftv67jxeaxdwcakvwo,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","**wmf.amgine3691** wrote:
+
+And use bom. It's the right thing to do.",1343358797,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+"VisualEditor: Automatically use ""smart quotes"" and convert other typing to more advance characters (as an option)","Also ellipses (... -> …) and other auto-conversions, if this is done.",1343348715,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-dnx6tmydfht55cpjp4ur,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"Inserting symbols, accented characters, and characters from other writing systems is a common task in encyclopedia-building.
+
+VisualEditor needs to provide this as much as WikiEditor does; preferably they should use the same configuration and avoid duplicating code or config if possible.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340903580,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-svlkli7eygnwnscchzm6,task_description,declined
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"Re-visiting this, I'm not sure I agree with the premise any more.
+
+Lots of the per-language localisations (and the per-wiki customisations) of the ""edit tools"" message have added useful characters for editors without the ability to insert them using their keyboard, but they all mix the semantic concepts of wikitext syntax fragments (e.g. ""<nowiki>"" or even ""{{RLM}}"") and accented characters; asking communities to de-merge these just so VisualEditor can re-use some of them seems impractical.
+
+Consequently I'm going to mark this as a WONTFIX, but if you can think of a sane way to do this, please re-open. :-(",1387220701,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,*** Bug 58323 has been marked as a duplicate of this bug. ***,1387220238,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"Re-wording this and making it depend on bug 50296 - I have doubts about this, however. Many choices about availability of characters, or about their prominence, aren't appropriate in both contexts (""~~~~"" isn't something needed in VisualEditor, for example). Not sure whether this should instead be a WONTFIX in lieu of 50296, but leaving open for now.",1383282568,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,Another request for this today. It's regarded as one of the few key missing features by a significant content editor.,1375716584,PHID-USER-ysftv67jxeaxdwcakvwo,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"This seems coincidentally to have been the subject of two separate requests today in the VE feedback pages: many editors need access to accented characters, greek letters, em-dashes and other specialised symbols, etc. See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Quick_insert_panel and the section below it.",1374066955,PHID-USER-7zhn2ep5wvjhxetsbb6n,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"**weskaggs** wrote:
+
+I have a few comments; apologies if I misunderstand the issues or am commenting in the wrong place.
+
+First, the ability to enter special characters should have higher priority.  They are very frequently used -- long dashes the most frequently of all, but many others too.
+
+Second, the WikiEditor toolbar is probably overkill.  A better model may be the CharInsert gadget that can be enabled in the English Wikipedia preferences.  The JS code for the gadget can be found at
+
+http://en.wikipedia.org/wiki/MediaWiki:Gadget-charinsert.js
+
+The gadget depends on a very simple extension called CharInsert, whose php code can be viewed at
+
+https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FCharInsert/8fa1602e22324b73491004957f02d5309302505b/CharInsert.php
+
+Of course none of this can be used without modification, but it may provide a model for a character insert interface that has been optimized for usability.",1373638737,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"Forking existing code feels icky, but depending on an otherwise-unrelated extension isn't a good way to go.
+
+Possibly some of this could be core-ified?",1354835514,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,the character config can be found: WikiEditor/modules/jquery.wikiEditor.toolbar.config.js,1354832598,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,"This may be obvious but to use the existing character code would make this feature dependent on WikiEditor.  Otherwise, reproduce the character configuration in a  VisualEditor module.  Another idea is to to pull the character configuration out of WikiEditor and place it in a more centralized place.  Thoughts?",1354832512,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow,Agree with stealing existing code if possible. :-),1340922361,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-svlkli7eygnwnscchzm6,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"There is an eminently and patently useful extension called ""Drafts"" that was written a few years ago: <https://www.mediawiki.org/wiki/Extension:Drafts>.
+
+This project kind of stagnated and/or died, I believe. I'd like to see it revived. This bug is about doing whatever is necessary to have this extension deployed to Wikimedia wikis.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement
+**See Also**:
+{T57370}
+{T75241}",1340821500,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_description,open
+Review and deploy Drafts extension to Wikimedia wikis,Is this still relevant now that #edit_recovery is a thing?,1728102632,PHID-USER-escte3psz5yfd2nj3jzr,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I'd generally prefer client-side drafts, but as discussed offline with @Jdforrester-WMF there is no blanket prohibition from the legal team on server-side draft storage.",1419864569,PHID-USER-kqwh3rvfxxh3wfsft7mu,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"About ability to recover from crashes, I wonder how complex would it be enable this ""cache"" that Phabricator offers in this very Comments textarea I'm typing it. Type something, reboot your laptop, come back to this URL, and your text is still here, in the textarea, where you left it.",1416815782,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Legal issues put aside, using client-side storage for drafts does have a lot of advantages: better performance, support for anonymous edits, ability to recover from crashes that happen while there is no network connection. The main disadvantage that I can see is that it is not privacy-friendly - using good privacy practices like incognito mode of the browser would cripple a client-side draft feature as it could not recover the text after a browser crash.",1416814165,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,">>! In T39992#424332, @Jdforrester-WMF wrote:
+> If we create a server-side private drafts facility, we invite malefactors to (ab)use the facility to store and (using accounts with a shared password) distribute:
+> 
+> * Terrorism-related materials;
+> * Child pornography (even if the Drafts are 'just' text, e.g. base64 encoding of images);
+> * Foreign intelligence service / espionage channels (let's please not make the Wikileaks comparisons true);
+> * Other criminal information; and
+> * Civil illicit information (e.g. breaking NDAs, corporate espionage, …)
+>
+>All this kind of stuff is potentially uploaded to the public fora of Wikimedia's wikis (talk pages, etc.), but (because people are aware that it's public) it is much less frequently put there, and so is at a level where it can generally be dealt with by the existing community processes. A private cache of drafts that isn't visible to any other user means that the community couldn't police it, or flag for suppression/other admin action.
+> 
+> Because of this, *even if no terrorist/pædophile/spy/criminal/mole ever did this*, WMF would get many, many subpœnæ, warrants, clandestine requests (National Security Letters, etc.) and other legal instruments which would have the effect of hugely increasing the cost to comply with these matters. I appreciate that lots of the other top-10 websites have server-side drafts facilities, but they have lots more money to throw away like this, and (allegedly) direct NSA/FBI/… access to their servers anyway, reducing the legal compliance cost (but something to which we would never agree, of course). People running less-visible services run into this problem from time to time, and in some cases end up shutting down their services; we can't take the risk that we'd need to do this at Wikimedia.
+
+This is the classic argument from infocalypse [1] which is bad form in general, but makes even less sense in Wikimedia's case given that storing arbitrary private data is already possible via the options API [2]. In fact, any user with some Javascript skills could implement the Drafts extension right now as a user script. Even if arbitrary-key, arbitrary-length options got disabled, there would be ways to make Wikipedia store private information (e.g. split it into 255-byte chunks and store it as signatures over a set of autogenerated user accounts).
+
+Not that there is any need of that, given that Wikipedia can be edited by anyone and edits are practically never deleted, so a terrorist/pedophile/etc. who is particularly set on using Wikipedia to distribute illegal content could easily do that with some industry-grade cryptography tool and a bot that hides secret messages in vandalism. Or encode messages via steganography in penis selfies, etc.
+
+Not that there is any need of *that*, given that other WMF-operated services give you easier ways of sharing secret messages, such as etherpad which is essentially private if you choose a pad name that's hard enough to guess.
+
+Not that there is any need of that either, of course, since the net is full of services which, unlike Wikipedia, can be used easily and conveniently using pre-existing software to share information in secret. Dropbox, Google Drive etc, and we didn't even get to tools which were designed explicitly for that purpose like Freenet. So I find the notion that anyone would choose to use Wikipedia's draft feature as their underground distribution channel somewhat absurd.
+
+I appreciate the argument that such activities don't actually need to happen for law enforcement to decide that they need to police them, but as I said, they are already possible, so Drafts would not change the status quo at all.
+
+
+[1] https://en.wikipedia.org/wiki/Four_Horsemen_of_the_Infocalypse
+[2] https://www.mediawiki.org/wiki/API:Options",1416814019,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Thanks for the explanation of the legal issues relating to private drafts.  I've created bug  T57670 as a result.(In reply to comment #47)
+
+Regarding the client-side hit of a VE->Drafts interface vs VE->Local storage, I suppose I was expecting that VE would be putting HTML+RDFa into local storage, in which case the client side hit is the same for both.  But that should be discussed on bug T57370. (I've raised a few other points to consider there)",1469753942,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Thanks for the explanation of the legal issues relating to private drafts.  I've created bug 55670 as a result.(In reply to comment #47)
+
+Regarding the client-side hit of a VE->Drafts interface vs VE->Local storage, I suppose I was expecting that VE would be putting HTML+RDFa into local storage, in which case the client side hit is the same for both.  But that should be discussed on bug 55370. (I've raised a few other points to consider there)",1381649758,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"James' answer above is very authoritative and the concerns about server-side private drafts apply whether we're talking about wikitext or about VE.
+
+I like the general principle of using client-side storage for data recovery purposes (maximum privacy, avoids legal issues), and working towards better support for public drafts (inviting collaborators etc.) in future. That approach is more consistent with wiki-style collaboration in public while also safeguarding user actions.",1381348765,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"[Please note that I am not a lawyer and not currently working in a criminal prosecution or national security context; this is not legal advice, just based on my professional experience.]
+
+(In reply to comment #46)
+> (In reply to comment #44)
+> > Just a quick note, in case people are pushing hard on getting this done so it
+> > can be used for VisualEditor, it's not the direction we're looking at taking
+> > for VE.
+> > 
+> > * We would need something that is client-side, not server-side (this makes
+> > things faster and avoids the really icky legal issues).
+> 
+> Are these 'icky legal issues' explained somewhere? Are you referring to the
+> need for explicit copyright signoff before *distribution*?  Why cant that be
+> delayed until the real save button is pressed?
+
+Sorry - when I quickly wrote that yesterday, I assumed they were obvious, but that probably says more about me and my priors than anything else (I have a background in criminal prosecution and central government/security) - my apologies. :-)
+
+If we create a server-side private drafts facility, we invite malefactors to (ab)use the facility to store and (using accounts with a shared password) distribute:
+
+* Terrorism-related materials;
+* Child pornography (even if the Drafts are 'just' text, e.g. base64 encoding of images);
+* Foreign intelligence service / espionage channels (let's please not make the Wikileaks comparisons true);
+* Other criminal information; and
+* Civil illicit information (e.g. breaking NDAs, corporate espionage, …)
+
+All this kind of stuff is potentially uploaded to the public fora of Wikimedia's wikis (talk pages, etc.), but (because people are aware that it's public) it is much less frequently put there, and so is at a level where it can generally be dealt with by the existing community processes. A private cache of drafts that isn't visible to any other user means that the community couldn't police it, or flag for suppression/other admin action.
+
+Because of this, *even if no terrorist/pædophile/spy/criminal/mole ever did this*, WMF would get many, many subpœnæ, warrants, clandestine requests (National Security Letters, etc.) and other legal instruments which would have the effect of hugely increasing the cost to comply with these matters. I appreciate that lots of the other top-10 websites have server-side drafts facilities, but they have lots more money to throw away like this, and (allegedly) direct NSA/FBI/… access to their servers anyway, reducing the legal compliance cost (but something to which we would never agree, of course). People running less-visible services run into this problem from time to time, and in some cases end up shutting down their services; we can't take the risk that we'd need to do this at Wikimedia.
+
+> A client-side solution is not going to go down well.  People switch between
+> computers and browsers, use internet cafes, etc.  Wikipedia and VE are a
+> web-app; ordinary users will expect auto-save to persist across their
+> user-agents. A client side solution isnt auto-save; it is a data-recovery
+> mechanism only, which is still useful in its own right, but each client will
+> have its own quirks, etc.
+
+I appreciate that this is a pain, but the drafts would probably need to only last for a few hours anyway (it's intentionally a DR solution, as you say) - Wikimedia is in the business of providing wikis, and long-term drafting is completely anti-thetical to the concept of a wiki, where ""the page is the draft"". If you have a change which is an improvement, even if it's not all it could possibly be, save it so others can collaborate with you. I would be very troubled if we were to move in a direction of encouraging such anti-wiki behaviours.
+
+> > * We would need something that lets us persist VE linear-models, or at least
+> > Parsoid HTML+RDFa (otherwise each save will take dozens of seconds of
+> > computation, slowing clients down and adding to burdens on the cluster; until
+> > server-side storage of Parsoid HTML+RDFa is undertaken, there's nowhere
+> > really appropriate for this to be saved for the Drafts extension to implement,
+> > which is currently wikitext-based)
+> 
+> There is no client-side hit required to persist VE as wikitext. VE already
+> has an API call that accepts HTML+RDFa and produces wikitext; VE can add an API
+> call that accepts HTML+RDFa and persists it as wikitext into the Drafts
+> tables.
+
+I'm sorry, this is not correct. The API call in VE that you mention is a server-side request. The process to save (or get a wikitext diff) works roughly as follows:
+
+* VE client converts data model's linear model into Parsoid HTML+RDFa (this can take a noticeable amount of processing time for complex pages)
+* VE client establishes a connexion with the (very thin) server-side VisualEditor code, and transmits the HTML+RDFa to it (noticeable network time for long pages)
+* VE server establishes a connexion with the Parsoid service, and transmits the HTML+RDFa to it (server-side IO load)
+* Parsoid pulls from storage or the MW API the previous version of the page and other data so that it can as-cleanly-as-possible serialise (server-side IO load)
+* Parsoid serialises the HTML+RDFa from the client into wikitext based on this information (server-side CPU load)
+* Parsoid responds down the connexion with VE server and transmits the wikitext to it (server-side IO load)
+* VE server establishes a connexion with the MW cluster, and transmits the wikitext to it (server-side IO load)
+* MW saves the wikitext, or fails and returns an error code with why (server-side CPU load)
+
+This whole process can take multiple seconds (as you will see every time you press ""save"" in VE), and the first step is a significant CPU drain locally; I think this would be a really not-great thing to make happen every minute in the background, given the burden that VE already exhibits on some users' machines.
+
+> Not sure that there is going to be an overall additional burden to the
+> servers either.  Converting HTML+RDFa to wikitext will be a memory&processor
+> hit to the app servers, whereas persisting HTML+RDFa into the database is an
+> IO hit as compared to wikitext.
+
+Sure. But I'm not talking about persisting to the servers, as explained.
+
+> Besides, what percentage of overall server load is spent on processing page
+> saves to content pages (excluding rendering as autosave in VE doesnt need a
+> render hit)?  I'm guessing that isn't where the WMF resources are being
+> pinched.
+
+By definition, 100% of the Parsoid cluster's load is spent on processing page saves to re-render them now they have changed, either caused by a Parsoid client (like VE) or inside MW from another source (like the wikitext editor). The split is currently weighted towards MW changes, but that's an artefact of the current proportion of edits done with VisualEditor; we expect that figure to rise over time towards 100%.
+
+> > * We would want (but not strictly /need/) something very flexible, so we
+> > could persist undo stacks, etc. which could add a huge amount of
+> > complexity to the Drafts extension for just one use case/client.
+> 
+> I agree with Legoktm; it would be great if the source editor also had some
+> features added to it. undo stacks is a major part of the problems holding up
+> the deployment of Drafts; Drafts needs to handle multiple revisions of the
+> same page being saved as a draft.   I hear the majority of the editor base
+> tend to use the source editor most of the time ;-)
+
+Sure. But who's going to do that? Building expectations for features on the never-never isn't great for editors. :-(",1381332760,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #44)
+> Just a quick note, in case people are pushing hard on getting this done so it
+> can be used for VisualEditor, it's not the direction we're looking at taking
+> for VE.
+> 
+> * We would need something that is client-side, not server-side (this makes
+> things faster and avoids the really icky legal issues).
+
+Are these 'icky legal issues' explained somewhere? Are you referring to the need for explicit copyright signoff before *distribution*?  Why cant that be delayed until the real save button is pressed?
+
+A client-side solution is not going to go down well.  People switch between computers and browsers, use internet cafes, etc.  Wikipedia and VE are a web-app; ordinary users will expect auto-save to persist across their user-agents.  A client side solution isnt auto-save; it is a data-recovery mechanism only, which is still useful in its own right, but each client will have its own quirks, etc.
+
+> * We would need something that lets us persist VE linear-models, or at least
+> Parsoid HTML+RDFa (otherwise each save will take dozens of seconds of
+> computation, slowing clients down and adding to burdens on the cluster; until
+> server-side storage of Parsoid HTML+RDFa is undertaken, there's nowhere
+> really
+> appropriate for this to be saved for the Drafts extension to implement, which
+> is currently wikitext-based)
+
+There is no client-side hit required to persist VE as wikitext.  VE already has an API call that accepts HTML+RDFa and produces wikitext; VE can add an API call that accepts HTML+RDFa and persists it as wikitext into the Drafts tables.
+
+Not sure that there is going to be an overall additional burden to the servers either.  Converting HTML+RDFa to wikitext will be a memory&processor hit to the app servers, whereas persisting HTML+RDFa into the database is an IO hit as compared to wikitext.
+
+Besides, what percentage of overall server load is spent on processing page saves to content pages (excluding rendering as autosave in VE doesnt need a render hit)?  I'm guessing that isn't where the WMF resources are being pinched.
+
+> * We would want (but not strictly /need/) something very flexible, so we
+> could
+> persist undo stacks, etc. which could add a huge amount of complexity to the
+> Drafts extension for just one use case/client.
+
+I agree with Legoktm; it would be great if the source editor also had some features added to it.  undo stacks is a major part of the problems holding up the deployment of Drafts; Drafts needs to handle multiple revisions of the same page being saved as a draft.   I hear the majority of the editor base tend to use the source editor most of the time ;-)",1381282093,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I'm not sure this is should be discussed on this bug but...
+(In reply to comment #44)
+> Just a quick note, in case people are pushing hard on getting this done so it
+> can be used for VisualEditor, it's not the direction we're looking at taking
+> for VE.
+
+Thanks for the comment. Really I'm just trying to get this extension to not suck ;-)
+
+> * We would need something that lets us persist VE linear-models, or at least
+> Parsoid HTML+RDFa (otherwise each save will take dozens of seconds of
+> computation, slowing clients down and adding to burdens on the cluster; until
+> server-side storage of Parsoid HTML+RDFa is undertaken, there's nowhere
+> really
+> appropriate for this to be saved for the Drafts extension to implement, which
+> is currently wikitext-based)
+
+Technically Drafts is set up to store anything that is text based, and I think HTML+RDFa can be serialized into text (or is already text)? We might need to add a column for contentmodel in the drafts db schema though...
+
+> * We would want (but not strictly /need/) something very flexible, so we
+> could
+> persist undo stacks, etc. which could add a huge amount of complexity to the
+> Drafts extension for just one use case/client.
+
+Ideally the Drafts extension would also have some kind of history/undo, but this is kind of a slippery slope and at some point you end up with essentially private user sandboxes.
+
+> 
+> Though I think that the Drafts extension could be useful for wikitext users,
+> I
+> don't think it's right for VisualEditor; see bug 55370 for VisualEditor's
+> take.",1381270044,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Just a quick note, in case people are pushing hard on getting this done so it can be used for VisualEditor, it's not the direction we're looking at taking for VE.
+
+* We would need something that is client-side, not server-side (this makes things faster and avoids the really icky legal issues).
+* We would need something that lets us persist VE linear-models, or at least Parsoid HTML+RDFa (otherwise each save will take dozens of seconds of computation, slowing clients down and adding to burdens on the cluster; until server-side storage of Parsoid HTML+RDFa is undertaken, there's nowhere really appropriate for this to be saved for the Drafts extension to implement, which is currently wikitext-based)
+* We would want (but not strictly /need/) something very flexible, so we could persist undo stacks, etc. which could add a huge amount of complexity to the Drafts extension for just one use case/client.
+
+Though I think that the Drafts extension could be useful for wikitext users, I don't think it's right for VisualEditor; see bug 55370 for VisualEditor's take.",1381267322,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #42)
+> It would also be helpful if there are people willing to do code review, it
+> seems that's whats stalled the development of this extension in the past.
+
+It seems Yuvi is willing. You can also e-mail wikitech-l if you can't find anyone. :-)",1381196143,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #37)
+> 
+> Is it enabled on a WMF test wiki with VE?  Could it be enabled on
+> mediawiki.org
+> in order to encourage dev's playing with it?
+> 
+
+So I set up an instance at http://drafts.instance-proxy.wmflabs.org/wiki/Main_Page and attempted to install VE, except setting up parsoid failed with some cryptic error I didn't spent time debugging.
+
+Digging through the code, there's a lot of cleanup (deprecated stuff, (ab)use of globals, etc) that needs to be done and a start has been made at https://gerrit.wikimedia.org/r/#/c/29749/
+
+It would also be helpful if there are people willing to do code review, it seems that's whats stalled the development of this extension in the past.",1381161937,PHID-USER-v7vgzvvcw7v2umf737ri,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #39)
+> Shouldn't be deployed on cluster until code has had relevant code review
+> actioned against it, and any necessary remedial action completed.
+
+Hmm, right, I forgot that this bug has a bunch of outstanding dependencies.
+
+John V.: we'll need to find someone to work on the extension in order to eventually get it deployed on any Wikimedia wikis.",1381113030,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Well, and until Features and Product have confirmed it's something they're interested in supporting (unless Platform devs are comfortable explicitly saying 'yes, we will make sure it works forevermore')",1381112441,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Depends by what you mean as a wmf test wiki. Its not on the cluster, as its not branched. I don't think it is on beta either, but you van confirm it yourselves via NOC or mediawiki-config
+
+Shouldn't be deployed on cluster until code has had relevant code review actioned against it, and any necessary remedial action completed.",1381107508,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #37)
+> Is it enabled on a WMF test wiki with VE?  Could it be enabled on
+> mediawiki.org in order to encourage devs playing with it?
+
+Greg: do you know?",1381106680,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"The demo of this extension (http://kubo.wmflabs.org/wiki/Main_Page) now returns 404.  There are some non-WMF wikis using this extension: http://wikiapiary.com/wiki/Extension:Drafts
+
+Is it enabled on a WMF test wiki with VE?  Could it be enabled on mediawiki.org in order to encourage dev's playing with it?
+
+From a quick look at the code, a prototype of VE-support of Drafts can be done easily with only user: space custom JavaScript.
+
+Proper VE-support would need a new API call to minimise data being sent back and forth.",1381106334,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Visual editor brings new dataloss scenarios due to its beta status. If VE could autosave the article as a draft, and could open the draft in VE, this would allow switching editor.",1381102490,PHID-USER-oxd6f6xemkuyttw7z7wl,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,....by six people ;p.,1352200079,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**armbrust** wrote:
+
+There was a discussion on the Proposal Village Pump on the English Wikipedia (http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_94#Allowing_users_to_keep_private_drafts_of_their_work), where this feature was cleary supported.",1352199927,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I agree that browser auto-save isn't a sufficient alternative to this feature. We still need this, and help whipping the extension into shape is very much appreciated.",1351104490,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #31)
+> (In reply to comment #19)
+> > ... modern Web browsers have auto-save.
+> 
+> That's a good point. A couple of years ago this extension would have been
+> really appreciated by me, but nowadays it has become almost superfluous, thanks
+> to the improvement of the browsers' auto-save capabilities (Firefox, for one,
+> can recover what you have typed even in the case of a power failure).
+
+I'm not aware of other browsers having the same capabilities, which I anyway still see myself failing, not seldom. There are also many other chances to lose an edit with actions that the browser can consider intentional. In short, it's not a valid assumption that the wiki editor is using a human-like smart browser.
+
+> Another thing to consider is that, after such feature is deployed, users will
+> generally feel safer about starting an edit and postponing the save for hours
+> later, posing a higher risk of edit conflicts (especially in larger wikis as
+> Wikipedia).
+
+I doubt so, and anyway it's easily configurable as far as I can see.",1351094795,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**capmo700** wrote:
+
+(In reply to comment #19)
+> ... modern Web browsers have auto-save.
+
+That's a good point. A couple of years ago this extension would have been really appreciated by me, but nowadays it has become almost superfluous, thanks to the improvement of the browsers' auto-save capabilities (Firefox, for one, can recover what you have typed even in the case of a power failure).
+
+Another thing to consider is that, after such feature is deployed, users will generally feel safer about starting an edit and postponing the save for hours later, posing a higher risk of edit conflicts (especially in larger wikis as Wikipedia).",1351094482,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #29)
+> I agree that this is a useful extension, but this goes beyond code review. The
+> extension is not deployable in its current state and needs significant work.
+> I've added some dependencies.
+
+Yes, completely agreed. I hadn't realized this reality when I filed this bug.
+
+I actually considered marking this bug as ""resolved later"" over the weekend, but now that it has some dependencies and lacks the ""shell"" keyword, I think leaving this bug open as a tracking bug should work well. Thanks for looking into this, Erik!",1348521626,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I agree that this is a useful extension, but this goes beyond code review. The extension is not deployable in its current state and needs significant work. I've added some dependencies. 
+
+I don't think this is doable as a 20% time project for Trevor, so unless there are more folks who want to chip in improvements, I'd put this on hold for now from a WMF standpoint.",1348516213,PHID-USER-766idcqt4jkngnnuhnrj,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**stillwaterising** wrote:
+
+(In reply to comment #25)
+ 
+> For the record, I'd strongly urge that the first response to any Bugzilla that
+> will result in a change to the UI should be ""Please point me to the community
+> discussion that recommends this change.""   I'm not sure why the WMF would be
+> investing 20% of an engineer's time without any evidence that [multiple]
+> communities are interested in activating an extension.  There are plenty of
+> extensions around that, simply put, aren't used because they're unwanted or
+> have a negative impact on a project.  Unexpected and undiscussed UI changes
+> have repeatedly caused significant discord between communities and Engineering.
+
+The percentage of editors reading message boards like Village pump (idea lab) has to be a very small fraction. The ratio of developers to normal users reading and responding will be disproportionate. Village Pump does not represent what the average user wants.
+
+Successful companies looking to invest in new services or products will perform studies, focus groups, and surveys.  What I propose is a survey consisting of 250+ randomly-selected recently active auto-confirmed users.
+
+Users could be shown images or videos as well having written descriptions of proposed changes to the UI and ask for how interested, how useful, how effective, etc. they think it will be for them.
+
+Smaller focus groups can be organized where users are asked to go to a test wiki and perform certain tasks and answer questions about their experience.",1347853611,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #26)
+> I'm sorry; this problem is at least partially my fault. [...]
+
+And just to clarify, I take that portion of fault for myself because I'm the one who added the extension to the queue page, perhaps misleading someone. I did so because I well remember this coming from real usability issues found at the time, being tested and receiving unanimously positive comments which can in part still be found at https://usability.wikimedia.org (I agree that the lack of a live prototype is confusing those who can't remember the 2009 one). I think the documentation already explains everything that was requested, but maybe I'm reading too much into it. 
+Anyway, as Sumana notes, design is now being re-reviewed by the wider design team.",1347852451,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**sumanah** wrote:
+
+(In reply to comment #25 by Risker)
+
+> For the record, I'd strongly urge that the first response to any Bugzilla that
+> will result in a change to the UI should be ""Please point me to the community
+> discussion that recommends this change.""   I'm not sure why the WMF would be
+> investing 20% of an engineer's time without any evidence that [multiple]
+> communities are interested in activating an extension.  There are plenty of
+> extensions around that, simply put, aren't used because they're unwanted or
+> have a negative impact on a project.  Unexpected and undiscussed UI changes
+> have repeatedly caused significant discord between communities and Engineering.
+
+Thanks for the comment, Risker, and thanks to everyone in this thread for all your comments.
+
+I'm sorry; this problem is at least partially my fault.  Just before my vacation this summer, I asked for some help maintaining the review queue (for new extensions to potentially be deployed on WMF sites: https://www.mediawiki.org/wiki/Review_queue ).  The Drafts extension got added to this list, and in late August I accidentally went straight into requesting code review/improvements from Trevor, using his ""20%"" time ( https://www.mediawiki.org/wiki/Wikimedia_engineering_20%25_policy ) . Per our procedures at https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment#Design_review , I should have instead gotten Drafts a design review first, from our product management or design team.  As the ""design review"" procedure says, ""This will start a conversation about the design of your feature, which should include community consensus on the wiki where the extension would be deployed.""
+
+The design team is currently discussing Drafts on the design mailing list:
+
+http://lists.wikimedia.org/pipermail/design/2012-September/thread.html#130
+
+and I will update that list, Trevor, and the review queue to ask for that design review.
+
+Thanks, and my apologies again.",1347849681,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #24)
+> The drafts saved by a user are not publicly visible and as such do not show up
+> on 
+> recent changes. The author can delete them at any time by clicking on ""Discard""
+> either while editing a page for which he saved a draft or while accessing all
+> his personal drafts by Special:Drafts.
+
+
+Thanks, mybugs, for answering #2 and #3.  So the response to #1 should be no because the draft is not publicly visible, and #4 & #8 would be moot if it is seen only by the user.    
+
+So this leaves:
+
+5) How long between creation and ""automatic expiry""?  Is this configurable by
+user or only within the code?
+6) Will the edits made in a ""draft"" count as edits statistically?
+7) When drafts are ""saved"" into the page, is the edit history of the draft
+incorporated into the page history?  If so, is there a way to indicate that it
+was made on a ""different"" page and not directly into the article?  [Note that
+one of the biggest issues in merging page histories is that it is pretty much
+impossible to correctly identify what past versions of the page looked like.]
+
+9) Will drafts be included in dumps?
+10) What evidence is there that *users* want this feature?  
+
+I learned long ago not to assume too much here.  
+
+For the record, I'd strongly urge that the first response to any Bugzilla that will result in a change to the UI should be ""Please point me to the community discussion that recommends this change.""   I'm not sure why the WMF would be investing 20% of an engineer's time without any evidence that [multiple] communities are interested in activating an extension.  There are plenty of extensions around that, simply put, aren't used because they're unwanted or have a negative impact on a project.  Unexpected and undiscussed UI changes have repeatedly caused significant discord between communities and Engineering.",1347847001,PHID-USER-yif6nz5uhka5cnltixpc,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"The drafts saved by a user are not publicly visible and as such do not show up on 
+recent changes. The author can delete them at any time by clicking on ""Discard"" either while editing a page for which he saved a draft or while accessing all his personal drafts by Special:Drafts.",1347825120,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #8)
+> Trevor is looking at this extension for review & improvement.  See
+> https://gerrit.wikimedia.org/r/#/q/project:mediawiki/extensions/Drafts+-owner:L10n-bot,n,z
+> .
+
+Couple of questions:
+
+1) Will these be indexed? 
+2) Can they be deleted?
+3) Do they show up in Recent Changes?
+4) Is suppression enabled? 
+5) How long between creation and ""automatic expiry""?  Is this configurable by user or only within the code?
+6) Will the edits made in a ""draft"" count as edits statistically?
+7) When drafts are ""saved"" into the page, is the edit history of the draft incorporated into the page history?  If so, is there a way to indicate that it was made on a ""different"" page and not directly into the article?  [Note that one of the biggest issues in merging page histories is that it is pretty much impossible to correctly identify what past versions of the page looked like.]
+8) When drafts expire, is that information completely inaccessible, or accessible only under specific circumstances?  [It's important to be able to re-access any material that was *ever* publicly viewable because we never know which bits will wind up requiring some sort of response in the future.]
+9) Will drafts be included in dumps?
+10) What evidence is there that *users* want this feature?  
+
+
+I think there is a faulty assumption behind some of the discussion here, that users are saving frequently because of fear of losing their work.  This isn't true; users save frequently because (a) they want to see their work in the context of the page being edited, (b) there is a systemic problem with saving work because of time-outs or the system logging them out/otherwise not accepting edits, that will not be rectified by this and (c) they are beefing up their edit counts without using scripts.",1347822673,PHID-USER-yif6nz5uhka5cnltixpc,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"As a user, this seems useful.
+
+What to do about edit conflicts might be an issue, but even a short warning not to leave it too long (and why) upon saving a draft could be enough for that, and if a page is too highly edited, maybe just removing the draft option entirely on those would be in order? Could confuse people a little at first, but they'd probably catch on eventually since a draft on, say, enwp's WP:ANI would make NO BLOODY SENSE in the first place.
+
+Just suddenly turning on automatic drafts could also pose problems due to current habits of starting edits and then thinking better of them and leaving, as opposed to using the cancel button, but editors can be retrained. On the other hand, since editing and then previewing is not only the only way to test things without saving them, but also a really convenient one, that might actually be an issue... but if all else fails, a user option to turn the automatic drafts off should fix that pretty effectively. 
+
+And the only part of this that seems like it might go out of general enhancement territory and into OUTRAGE WHY YOU CHANGE THIS?! territory is the automatic drafts. But while a decision on the parts of the projects themselves whether or not enable that part at all might make them a little happier, why should be necessary, especially if users have the option to just turn it off themselves if they don't like it?",1347769391,PHID-USER-nv2bu7uh3huvidyjo4lk,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #20)
+> It'd be nice if this extension could be enabled on https://test.wikipedia.org
+> or similar. A lack of a working demonstration is hurting the conversation, I
+> fear.
+
+Okeyes said at
+[[WP:Village_pump_(proposals)#Allowing_users_to_save_drafts_of_their_work]]
+that (the version 0.1.1) of the extension is enabled on this wiki:
+http://kubo.wmflabs.org/wiki/Main_Page
+I don't know if this is the most up to date version.",1347751319,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #17)
+> I have to say, I'm with Oliver here.  I have concerns about deployment on a
+> wide scale without some further feature development and (more importantly)
+> community input and buy-in.  It seems to me that there are policy and
+> governance changes that also need to be introduced at the same time, and it
+> would be courteous to let the community work on those with some warning.
+
+Can you elaborate on the policy and governance changes you envision?
+
+> I also have UI challenges with this.  It's not immediately transparent how it
+> works to a new user (where is the integration to contribution history or recent
+> changes?), and (while I haven't seen the documentation) I suspect that the
+> documentation is also not user-ready.
+
+They're private (per-user) drafts. I'm not sure if this was apparent when you wrote this comment.
+
+It'd be nice if this extension could be enabled on https://test.wikipedia.org or similar. A lack of a working demonstration is hurting the conversation, I fear.",1347750972,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #12)
+> TL;DR, I really oppose turning this on with the way it's formatted now and
+> using the process that's being discussed.
+
+Most of your comment reads as ""I'm bored and looking for a fight"" with a hint of ""why wasn't I consulted?"" If you want to start petty disputes on Bugzilla with me, you really ought to do better research into the battles you pick. This isn't my brainchild or my code. It's a missing MediaWiki feature that would be particularly helpful to have on Wikimedia wikis.
+
+> *For more detail on each point; this is not, as MzMcBride claims, ""a general
+> MediaWiki enhancement"" unless you want to expand the definition to cover pretty
+> much anything.
+
+It seems like a fairly standard enhancement to me.
+
+> It introduces a completely new workflow, alters existing ones
+> and sticks a big button on the (already overfilled) page that we know all
+> editors are going to see. There is no way this can be turned on without a
+> community discussion unless you want a raging storm of anger hurled in the
+> direction of whoever hits the big red button.
+
+I'm not sure I understand what you're saying here. Microsoft Word has auto-save; WordPress has auto-save; modern Web browsers have auto-save. Who do you think will be shouting about this being enabled? Is there any evidence of this being a controversial feature?
+
+> *The UI elements clash with current thinking about the direction that we're
+> going in. The Micro Designs Improvement project is currently working on the
+> edit window as we speak, and plans to do a couple more iterations given the
+> opportunity. I'd rather not throw two competing philosophies of design into the
+> mix - that works if they're from the same team, but I worry we'd end up with
+> (at best) an inconsistent UI and (at worst) an active clash.
+
+I'm not sure how this is relevant. Other parts of the edit view need work, yes.
+
+> *This really doesn't seem an efficient way to do things. What's the use case
+> here, exactly? If it's ""people would like to save a draft in case they lose
+> their work"", save the draft automatically after [number] of minutes or seconds
+> rather than requiring them to actually make a decision, and then just void any
+> drafts after [other number] of minutes or seconds.
+
+This extension pretty much does exactly that, doesn't it? I don't think the current version of this extension is as heavy-handed about auto-discarding drafts as you suggest it could be, but that seems like a feature to me, not a bug.
+
+> If it's ""we want to sort how
+> confusing the existing setup is by offering functions found on other sites"",
+> integrate that into the existing workflows to avoid button bloat. At
+> https://www.mediawiki.org/wiki/Extension:Drafts I'm seeing edge cases discussed
+> and the workflow discussed...but not how this in any way can be integrated into
+> how Wikipedia currently works, or how we'd like it to work, or what exactly the
+> use case is for this software. If there is a use case, it needs to be
+> communicated. If there isn't, we shouldn't be turning it on.
+
+I didn't follow most of this section, so I'm not quite sure how to respond.
+
+> *Can someone point me to, if not a use case, the user demand for this feature?
+> One power user requesting it on bugzilla is not a case for change.
+
+You can't formulate a use-case for a drafts feature in your head? Interesting. You've been editing Wikipedia for how many years now? You've never wanted to create a draft of something? :-)
+
+As for the ""one power user"" comment, when you look at the history of the development of the extension (which you apparently didn't) and you look at related bugs (such as bug 19909), you can see that your comment doesn't make much sense. I'm not sure what you gain by trying to act as though there's only person pushing for auto-save functionality on Wikimedia wikis.
+
+> This is not to say that it isn't useful, or that this type of feature isn't the
+> sort of thing we should be looking at - as mentioned above, reforming the
+> editing workflows is something that is being discussed and worked on. I'm just
+> skeptical that this particular information, particularly deployed in this
+> fashion, is going to benefit more than it costs.
+
+""The extension needs a bit of work before deployment. Water is also wet. You can safely ignore the last few paragraphs I wrote.""",1347750601,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #15)
+> Really? Who makes these saves? And if this is a common use case, could we have
+> an on-wiki demonstration that people need or want it? :)
+Ok. I just created a topic on enwiki for this:
+https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)#Allowing_users_to_save_drafts_of_their_work
+
+(and there was the other one on ptwiki, mentioned on comment 13).",1347747627,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I have to say, I'm with Oliver here.  I have concerns about deployment on a wide scale without some further feature development and (more importantly) community input and buy-in.  It seems to me that there are policy and governance changes that also need to be introduced at the same time, and it would be courteous to let the community work on those with some warning.
+
+I also have UI challenges with this.  It's not immediately transparent how it works to a new user (where is the integration to contribution history or recent changes?), and (while I haven't seen the documentation) I suspect that the documentation is also not user-ready.  I would hope that the UI takes advantage of some of the knowledge gained through the past year's experimentation rigor, rather than charting a course that may or may not make sense.  
+
+With all that said, I agree with MZMcBride's intent in moving this forward - limbo is a terrible place, and when promising tools are stuck there, it's frustrating.  We SHOULD improve the pipeline; but let's do it intelligently.
+
+Philippe",1347746393,PHID-USER-gk4enxd23ebojohiq7rf,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #15)
+> Really? Who makes these saves? And if this is a common use case, could we have
+> an on-wiki demonstration that people need or want it? :)
+
+A DB query will give you plenty of examples. ;)
+
+> I'm not a developer either. However, I consider needlessly complicating the UI
+> interface or introducing new workflows without consulting people in advance or
+> having a firm use case that we actually know occurs to be a core problem with
+> what's being discussed - regardless of what's being discussed.
+
+As I already said, I don't think this introduces new workflows, except when the workflow is ""rewrite everything from scratch because you've lost all you wrote"" or ""save every 30 s to avoid losing everything"". And no, I can't imagine anyone who could dislike this feature intervening in such cases.",1347745859,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Really? Who makes these saves? And if this is a common use case, could we have an on-wiki demonstration that people need or want it? :)
+
+I'm not a developer either. However, I consider needlessly complicating the UI interface or introducing new workflows without consulting people in advance or having a firm use case that we actually know occurs to be a core problem with what's being discussed - regardless of what's being discussed.",1347745340,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #12)
+> *Can someone point me to, if not a use case, the user demand for this feature?
+
+The use case and user demand is the hundreds or thousands of users saving their edits every couple of minutes and so for fear of losing everything.
+I'm not a developer but the points you raise, although very important, don't seem to be blockers, rather marginal ones. 
+For instance, removing the button by default seems a reasonable solution, as long as the user understands what's going on (just a small notice every time the draft is saved?). A configuration variable could be used to enable the button for wikis which desire it.",1347744717,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"I've asked on Portuguese Wikipedia a few days ago:
+http://pt.wikipedia.org/wiki/Project:Esplanada/propostas/Instalar_extens%C3%A3o_para_salvar_rascunhos_(1set2012)?uselang=en
+
+So far, no one opposed it, but one of the users asked if we could test it somewhere. According to
+http://www.gossamer-threads.com/lists/wiki/wikitech/278043
+the extension was installed by [[User:Petrb]] on
+http://en.wikipedia.beta.wmflabs.org/wiki/Special:Drafts
+but the link is not working right now.",1347744546,PHID-USER-sryrz6tgcfnnsiddx32p,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"TL;DR, I really oppose turning this on with the way it's formatted now and using the process that's being discussed.
+
+*For more detail on each point; this is not, as MzMcBride claims, ""a general MediaWiki enhancement"" unless you want to expand the definition to cover pretty much anything. It introduces a completely new workflow, alters existing ones and sticks a big button on the (already overfilled) page that we know all editors are going to see. There is no way this can be turned on without a community discussion unless you want a raging storm of anger hurled in the direction of whoever hits the big red button.
+
+*The UI elements clash with current thinking about the direction that we're going in. The Micro Designs Improvement project is currently working on the edit window as we speak, and plans to do a couple more iterations given the opportunity. I'd rather not throw two competing philosophies of design into the mix - that works if they're from the same team, but I worry we'd end up with (at best) an inconsistent UI and (at worst) an active clash.
+
+*This really doesn't seem an efficient way to do things. What's the use case here, exactly? If it's ""people would like to save a draft in case they lose their work"", save the draft automatically after [number] of minutes or seconds rather than requiring them to actually make a decision, and then just void any drafts after [other number] of minutes or seconds. If it's ""we want to sort how confusing the existing setup is by offering functions found on other sites"", integrate that into the existing workflows to avoid button bloat. At https://www.mediawiki.org/wiki/Extension:Drafts I'm seeing edge cases discussed and the workflow discussed...but not how this in any way can be integrated into how Wikipedia currently works, or how we'd like it to work, or what exactly the use case is for this software. If there is a use case, it needs to be communicated. If there isn't, we shouldn't be turning it on.
+
+*Can someone point me to, if not a use case, the user demand for this feature? One power user requesting it on bugzilla is not a case for change.
+
+This is not to say that it isn't useful, or that this type of feature isn't the sort of thing we should be looking at - as mentioned above, reforming the editing workflows is something that is being discussed and worked on. I'm just skeptical that this particular information, particularly deployed in this fashion, is going to benefit more than it costs.",1347743734,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"Could we see this put up on a labs instance somewhere? I have several concerns, but I'm not sure how valid they are because I can't actually see an example of the software in use - which is an issue.",1347742158,PHID-USER-j5ma2nageni56xp567v5,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**sumanah** wrote:
+
+Trevor is continuing to work on Drafts for about one day a week, fixing bugs, improving database handling, adding ResourceLoader and jQuery integration, and so on.",1347485723,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**swalling** wrote:
+
+(In reply to comment #4)
+> Consensus?
+
+This is also a feature that someday would have been tested anyway for new page creation. See also: https://www.mediawiki.org/wiki/Article_Creation_Workflow/Design",1346369067,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"**sumanah** wrote:
+
+Trevor is looking at this extension for review & improvement.  See https://gerrit.wikimedia.org/r/#/q/project:mediawiki/extensions/Drafts+-owner:L10n-bot,n,z .",1346342384,PHID-USER-ynivjflmc2dcl6w5ut5v,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,-shell; nothing for ops to do yet. Extension needs review and improvements first.,1343434370,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #5)
+> (In reply to comment #4)
+> > Consensus?
+> 
+> I believe this extension falls under general MediaWiki enhancements and doesn't
+> require local community consensus to enable.
+> 
+> Do you feel otherwise? If so, how would you recommend moving forward?
+
+I'd agree with you. It should be an unobtrusive benefit for anyone with a browser that works with it.
+
+And even then, it's got a preference to turn it on/off",1343422972,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #4)
+> Consensus?
+
+I believe this extension falls under general MediaWiki enhancements and doesn't require local community consensus to enable.
+
+Do you feel otherwise? If so, how would you recommend moving forward?",1343419866,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,Consensus?,1343377587,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #2)
+> (In reply to comment #1)
+> > I guess step one is to get the code into Git/Gerrit. CC'ing Sam and Chad about
+> > that.
+> 
+> On it, will be done shortly.
+
+Done, https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Drafts",1340828567,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,"(In reply to comment #1)
+> I guess step one is to get the code into Git/Gerrit. CC'ing Sam and Chad about
+> that.
+
+On it, will be done shortly.",1340826848,PHID-USER-oetk6bbl6omm354ejz3b,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+Review and deploy Drafts extension to Wikimedia wikis,I guess step one is to get the code into Git/Gerrit. CC'ing Sam and Chad about that.,1340822766,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-dvfnj4v6d6wmzjocacpy,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"[Suggestion from community.]
+
+Copy-pasting in an image to the editor should automatically upload it to the wiki and insert it into the article.
+
+After/on insertion (but before saving) the editor should be prompted to add meta-data (e.g. name, licence, source, ...).
+
+I'd imagine we'd be less likely to accept this for Wikimedia wikis, but others (Wikia?) might be interested.
+
+**See Also**: {T23557}",1340644620,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-usebfh653647q2fmkkwk,task_description,resolved
+VisualEditor: Upload-by-insertion of images via copy-paste,@matmarex Will do. Thank you for the response :),1541192975,PHID-USER-cb53pyjz3ccu7fvgd7m2,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"> See recording here: https://cloud.jackalope.tech/s/example
+
+(Here's the same, for future reference in case that URL becomes unavailable, and in smaller size to save folks a 200 MB download.)
+
+{F26990564}",1540950373,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,">>! In T39932#4708065, @Thedonquixotic wrote:
+> Hi @matmarex It does appear to work with copy pasting from paint but it doesn't work when copying pasting an image from another browser tab. 
+
+Interesting. Turns out that when you copy an image in the browser, it is stored in the clipboard in two formats: as the actual image, and as HTML like this:
+```
+<html>
+<body>
+<!--StartFragment--><img src=""https://apod.nasa.gov/apod/image/1705/Arp273Main_HubblePestana_3079.jpg"" alt=""Image result for galaxy""/><!--EndFragment-->
+</body>
+</html>
+```
+
+When this is pasted into VisualEditor, we use the HTML instead of the image (ve.ce.Surface.prototype.handleDataTransfer), because:
+```
+	// Only look for files if HTML is not available:
+	//  - If a file is pasted/dropped it is unlikely it will have HTML fallback (it will have plain text fallback though)
+	//  - HTML generated from some clients has an image fallback(!) that is a screenshot of the HTML snippet (e.g. LibreOffice Calc)
+```
+
+Then our paste sanitization strips that HTML down to nothing (since `<img>` tags using external resources are not possible in wikitext), and then nothing is pasted.
+
+@Thedonquixotic Can you file a separate task about this?
+
+(As a workaround, I guess you can paste into Paint, then copy from Paint.)",1540950367,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Hi @matmarex It does appear to work with copy pasting from paint but it doesn't work when copying pasting an image from another browser tab. 
+
+See recording here: https://cloud.jackalope.tech/s/example
+
+",1540942186,PHID-USER-cb53pyjz3ccu7fvgd7m2,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Hi @matmarex It does appear to work with copy pasting from paint but it doesn't work when copying pasting an image from another browser tab. 
+
+See recording here: https://cloud.jackalope.tech/s/example-copypaste  
+
+",1540942130,PHID-USER-cb53pyjz3ccu7fvgd7m2,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"(Also, we forgot to close this task in April 2017 when it was fixed, whoops.)",1540863713,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"File upload by copy-paste definitely still exists and works, I just tested it. However, it seems like there is a bug and the media dialog opens on the wrong tab when a file is pasted (or dragged and dropped). You can still complete the upload if you switch to the other tab. See demonstration:
+{F26972710}
+I filed T208286 about this issue.",1540863690,PHID-USER-wkpnidxoctuhawexig5p,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,@Florian Sorry to bother on this old ticket but I don't see how to do this in my current (1.31) installation of Mediawiki with Visual Editor enabled. Is this feature still in mediawiki or has it been taken out?,1540769905,PHID-USER-cb53pyjz3ccu7fvgd7m2,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 339400 merged by jenkins-bot:
+[mediawiki/extensions/VisualEditor@master] MWMediaTransferHandler: Allow uploading of dropped Blobs
+
+[[https://gerrit.wikimedia.org/r/339400]]
+",1493321563,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 288773 abandoned by Bartosz Dziewoński:
+WIP: Add possibility to paste a file to the document
+
+Reason:
+Apparently no longer needed? https://gerrit.wikimedia.org/r/339400 also works. It's not clear to me why we couldn't do that before.
+
+[[https://gerrit.wikimedia.org/r/288773]]",1493321068,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 339400 had a related patch set uploaded (by Jforrester; owner: Esanders):
+[mediawiki/extensions/VisualEditor@master] Allow uploading of dropped Blobs
+
+[[https://gerrit.wikimedia.org/r/339400]]
+",1493245940,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Quick video of the change above:
+https://youtu.be/IuWaxS7mOBA",1463330808,PHID-USER-c5xwrfdyp3dckkh2nkoj,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 288773 had a related patch set uploaded (by Florianschmidtwelzow):
+WIP: Add possibility to paste a file to the document
+
+[[https://gerrit.wikimedia.org/r/288773]]
+",1463330633,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Change 288773 had a related patch set uploaded (by Florianschmidtwelzow):
+WIP: Add possibility to paste a file to the document
+
+[[https://gerrit.wikimedia.org/r/288773]]
+",1463247437,PHID-USER-idceizaw6elwiwm5xshb,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Interesting idea, I'll try to upload a first change for it :)",1463240041,PHID-USER-c5xwrfdyp3dckkh2nkoj,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,Bumping down priority.,1367089009,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"**orbit** wrote:
+
+I've been taking copy-paste related tickets.",1349897395,PHID-USER-ynivjflmc2dcl6w5ut5v,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+VisualEditor: Upload-by-insertion of images via copy-paste,"Tweaking summary to clarify this is for HTML copy-paste -- if we get a full URL to the web then this should be doable. If we get a relative URL or something on the local filesystem, there's less we can do. :)
+
+Drag-and-drop of files or similar would be a separate concern.",1340651137,PHID-USER-yek7ymogrv4qc67oilhf,True,PHID-TASK-usebfh653647q2fmkkwk,task_subcomment,NA
+"VisualEditor on Opera 12: editing existing link doesn't work, breaks selection logic","Testing in Opera 12 on Mac
+
+Steps:
+* open https://www.mediawiki.org/wiki/VisualEditor:Welcome
+* hit 'edit'
+* select a link
+* hit link button
+
+Expected behavior:
+* link dialog pops up, lets you change the link
+
+Actual behavior:
+* nothing... usually
+* sometimes - nothing, followed by the next attempt opening a link dialog at your first selection
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1340419620,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-mdlouwe6duqgfyx233gy,task_description,resolved
+"VisualEditor on Opera 12: editing existing link doesn't work, breaks selection logic",This shouldn't be happening anymore now that all dependencies are fixed. Rejoice!,1375118502,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-mdlouwe6duqgfyx233gy,task_subcomment,NA
+"VisualEditor on Opera 12: editing existing link doesn't work, breaks selection logic","Opera is not currently a target browser, so marking this as ""Lowest"" priority.",1354811733,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-mdlouwe6duqgfyx233gy,task_subcomment,NA
+"VisualEditor on Opera 12: clicking selection arrow shows, then hides popup bar","Testing in Opera 12 on Mac
+
+After making a selection, the little arrow shows up which you can click for a popup formatting bar. In Opera, the bar pops up then immediately hides itself, so can't be used.
+
+This also kills the selection.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340418600,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-qz33ogip6xbczaatjhcs,task_description,invalid
+"VisualEditor on Opera 12: clicking selection arrow shows, then hides popup bar",This refers to the inspector menu trigger icon that was removed in late-2012. Marking as INVALID as it doesn't matter any more.,1367028832,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qz33ogip6xbczaatjhcs,task_subcomment,NA
+"VisualEditor on Opera 12: clicking selection arrow shows, then hides popup bar",What arrow? I don't see one in neither Opera not Firefox.,1367017176,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-qz33ogip6xbczaatjhcs,task_subcomment,NA
+"VisualEditor on Opera 12: clicking selection arrow shows, then hides popup bar","Opera is not currently a target browser, so marking this as ""Lowest"" priority.",1354811747,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-qz33ogip6xbczaatjhcs,task_subcomment,NA
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"Selecting text from end to beginning with the mouse in Opera 12 doesn't work properly; the selection keeps resetting itself, so you end up with no selection.
+
+Selecting end to start via keyboard (shift+arrow keys) works as expected.
+
+Selecting from start to end works as expected.
+
+--------------------------
+**Version**: unspecified
+**Severity**: normal",1340418480,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_description,resolved
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"I poked around. This appears to have been fixed by I0873d906 together with bug 42925.
+
+Lesson for today: Opera bugs often highlight hidden non-Opera bugs ;)
+
+*** This bug has been marked as a duplicate of bug 42925 ***",1355350453,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_subcomment,NA
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"This currently appears fixed on en.wiki. What happened, and is it going to break itself again? :)",1355349532,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_subcomment,NA
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"I've determined the issue to happen within ve.ce.Surface.prototype.showSelection, which, every time a selection is made, removes it and adds it back (after the code path goes through two events called via the .emit() system). 
+
+I have also determined that the bug only happens when you're not debugging; setting apparently any breakpoint prevents it. Gotta be something timing-sensitive, but I don't know the codebase well enough to investigate (or, in fact, at all).",1354817818,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_subcomment,NA
+VisualEditor on Opera 12: selecting text with mouse 'backwards' fails,"Opera is not currently a target browser, so marking this as ""Lowest"" priority.",1354811757,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-lksk7iecqxpzkmtpqlr5,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"The VisualEditor does not display when using Opera. The header ""Visual editor sandbox"" is the only thing displayed.
+
+--------------------------
+**Version**: unspecified
+**Severity**: enhancement",1334532780,PHID-USER-um3fhlwaza6ecwf67t77,False,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_description,resolved
+VisualEditor: Does not work in Opera (tracking),No outstanding bugs against this tracker; closing.,1375126546,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"Change 72738 merged by jenkins-bot:
+Unblacklist Opera >= 12
+
+https://gerrit.wikimedia.org/r/72738",1375126428,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"Change 72738 had a related patch set uploaded by Matmarex:
+Unblacklist Opera >= 12
+
+https://gerrit.wikimedia.org/r/72738",1373385725,PHID-USER-idceizaw6elwiwm5xshb,False,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"[Reopening as a tracking bug and assigning to myself.]
+
+The current dependencies are the things that IMO are blockers to enabling VE for Opera users again.",1367169919,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),"Yair Rand: Since the time of your posting, The Visual Editor surface has been completely rewritten and is based on Content Editable.
+
+Content Editable is supported in Opera 12 and above.
+
+Browsers that support contentEditable here:
+http://caniuse.com/#search=contentEditable
+
+Closing bug.",1343344311,PHID-USER-pun3sjvg3cemjzbgyo2t,False,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),Seems to work in Opera 12 on a quick spot-check.... but there's a few problems. I'll file bugs and stack them on this one.,1340417922,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),To check if this is still current.,1340404043,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+VisualEditor: Does not work in Opera (tracking),Mass-moving items into VisualEditor product,1340402746,PHID-USER-ydswvwhh5pm4lshahjje,False,PHID-TASK-2teo2k6a5oyvyz7ddfv7,task_subcomment,NA
+Implement minification for SVG files in ResourceLoader,"This task is about implementing a high performance minifier for SVG content. It will also track the use of that minifier when embedding SVG files in file modules through CSSMin. 
+
+**See Also**:
+* {T175318}
+* {T61086}
+
+Task T61086 tracks the use of this minifier (once implemented) by ResourceLoaderImage for SVGs served from that endpoint.
+
+--------------------------
+
+>>! **Original report**:
+> 
+> 
+> This comes from bug 34810 (T36810)... Which could use this feature to dynamically do it (or the simpler older method of creating .min files)
+> 
+> SVG are used as non page content files, they contain a lot of whitespace. Minify and serve!
+> 
+
+",1330547040,PHID-USER-6vzzsmi22zem6yttr6vp,False,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_description,open
+Implement minification for SVG files in ResourceLoader,Raising priority per T59777. We're using more SVGs nowadays.,1430242878,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_subcomment,NA
+Implement minification for SVG files in ResourceLoader,*** Bug 63491 has been marked as a duplicate of this bug. ***,1410989371,PHID-USER-wkpnidxoctuhawexig5p,False,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_subcomment,NA
+Implement minification for SVG files in ResourceLoader,"I think we can apply the same as PNG files.
+
+I don't know of any SVG files we have in our repository that we manually edit to the level that can't aren't already be minified (they might have some indentation, but that's about it, and we could actually minify those in the repository, like we optimise PNG files).
+
+I know SVG is text where PNG is not, but unless we actually edit them, it should be fine.
+
+As for solving this bug, if we want to minify SVGs in separate requests (e.g. fonts), that would get quite tricky. They'd need a url to be served from.
+
+As for SVGs we embed in CSS (SVGs for icons like we do in VisualEditor), those could be easily minified before being base64 encoded (that is, once we have an xml minifier).",1362551377,PHID-USER-sai77mtxmpqnm6pycyvz,False,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_subcomment,NA
+Implement minification for SVG files in ResourceLoader,"There's several possible things to do here:
+
+* transparent HTTP gzip compression (can be enabled at webserver-level)
+* stripping comments and whitespace (traditional 'minification', could be done as a pre-processing step)
+* intelligent collapsing of redundant attributes and styles (harder!)
+* rounding coordinates to fewer digits
+* decimating points in overly-detailed polygons/curves
+
+Depending on just what you're trying to do, you could do some or all of those...
+
+For SVG fonts I'd recommend that they be relatively sane to begin with (if they're full of whitespace and comments as output assets, that's kinda lame -- they should be small/clean to begin with), and use transparent gzip compression on the web server configuration.",1330557265,PHID-USER-yek7ymogrv4qc67oilhf,False,PHID-TASK-s5at4xy2rbu4kz3beaqh,task_subcomment,NA
+Polish : Editing tools (VisualEditor and WTE) should display to user when server connection has been lost,"This will reduce instances where user submits changes and receives an error, possibly resulting in data loss. 
+see — http://github.hubspot.com/offline/",1415513322,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-bzskyradcmgpuo2efgwc,task_description,open
+Polish : Editing tools (VisualEditor and WTE) should display to user when server connection has been lost,"Tagging with VE-ME and WikiEditor as this is the first time I've stumbled over this, and we might want to come back to it.
+
+Dropping ""easy"" because it isn't. Anyone tempted to try to work on this needs to have a serious long conversation with me and Operations about how we could do this in a way that doesn't over-load the servers and take down Wikipedia.",1465833995,PHID-USER-ydswvwhh5pm4lshahjje,True,PHID-TASK-bzskyradcmgpuo2efgwc,task_subcomment,NA
+Polish : Editing tools (VisualEditor and WTE) should display to user when server connection has been lost,"Then we might want to only alert at critical times, like when edit summary is open or when save is pressed prior to actually submitting, e.g. disable save if connection can't be restored. ",1415566359,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-bzskyradcmgpuo2efgwc,task_subcomment,NA
+Polish : Editing tools (VisualEditor and WTE) should display to user when server connection has been lost,The editors do not keep a constant connection open to the server.,1415552047,PHID-USER-x7ti5ksby4ubsabntlxa,True,PHID-TASK-bzskyradcmgpuo2efgwc,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"We have three problems related to calendars that need to be resolved, which are related but perhaps may be fixed separately, even at different points in time:
+
+* **Introducing calendar data**. Now we are doing this in 1001 places. Ideally it would be just one place. The assumption of this task is that the one place would be Phabricator's calendar ([[ https://secure.phabricator.com/T7924 | today a prototype ]]), but other candidates should be considered.
+* **Pulling calendar data in other supports, mainly wiki pages**. While we could start linking from wiki pages to Phabricator calendar queries, the desired scenario would be a way for editors to embed calendars based on queries in wiki pages. This probably implies a Calendar API to query data ([[ https://secure.phabricator.com/T7944 | which is missing ]]) and a MediaWiki extension allowing to embed those queried calendars in wiki pages (which we don't have). Maybe this is just too much, and at least the tech-inclined Wikimedians would be fine clicking a Phabricator link.
+* **Integrating calendar data with other systems (mainly Google Calendar)**. ""[[ https://secure.phabricator.com/T7929 | Future work ]]"" upstream, no plans today.
+
+As we can see, deciding on Phabricator Calendar as the one place to introduce data would not provide a quick path to use that data out of Phabricator. However, what would be the alternatives? Other than defaulting to Google Calendar (which I think would be wrong as a matter of Wikimedia principles), I don't see a shortcut but others may have better ideas.
+
+== Phabricator Calendar in a nutshell ==
+
+After playing a bit with https://phabricator.wikimedia.org/calendar/, I think the most practical option is to focus on having that calendar up to date, and then link to it from the right places in mediawiki.org.
+
+* Entering events is simpler. The usual you can expect in a calendar application. There is no need to archive past events, since this is done automatically.
+* Users can RSVP, getting notifications about the event and letting others know that they are attending.
+* The calendars shown are the result of queries allowing for multiple parameters, including month view vs list, show only upcoming events, etc. These queries have static URLs.
+* Events can be assigned to projects, which means that
+** We could have projects for i.e. Tech Talks, Technical Office Hours, etc, people could subscribe to these projects and receive notifications when a new event is filed.
+** By adding an event to existing related projects (i.e. #Web-APIs-hub, #Google-Summer-of-Code-2015), users following that project would receive notifications as well.
+** Queries can be fine tuned to show a specific set of events.
+
+If we agree on this, the implementation would be relatively simple, since (at least in Wikimedia tech) a few people create most of the events. Redirecting from the current calendar pages to their equivalent Phabricator calendar queries should be enough to tell current users about these calendars about the new way to create new events.
+
+=== Basic review of existing MediaWiki extensions ===
+
+I went through https://www.mediawiki.org/wiki/Extension:Calendar (a linkhub for the ~12 different extensions or methods of integrating calendars with MediaWiki). There was no extension surviving a basic check against our needs. In fact, most of them are more than abandoned, and in general they focus on presentation, not on easy input, even less on semantic data (except the SemanticMediaWiki one, perhaps). [[ https://www.mediawiki.org/wiki/Extension:SimpleCalendar | SimpleCalendar ]] looks like the only candidate if we would ever want to start from this point.
+
+The reason for a lack of a proper MediaWiki Calendar extension may well be that MediaWiki was not designed to input calendar data, subscribe to events, etc.
+
+After this short investigation, I still think that it is better to start from something other than MediaWiki, and the main candidate keeps being Phabricator. Then work separately in a way to import Phabricator Calendar data and present it in MediaWiki pages.
+
+=== Background / previous description ===
+
+https://www.mediawiki.org/wiki/Project:Calendar has a lot of room for improvement. Creating tasks is not trivial, and although the calendar can be watched and the entries appear in the mediawiki.org homepage, it doesn't have any of the features expected nowadays in an online calendar, i.e. integration with the calendar apps people use to organize their lives.
+
+Also, for some low hanging fruit, a reporter explains in an email:
+> the whole project:calendar page hierarchy is confusing - I would avoid subpages at more than one level deep
+> It's not clear to me why this page is in the Project: namespace to begin with
+> https://www.mediawiki.org/wiki/Project:Namespaces seems to suggest the Project: namespace is for ""organization of mediawiki.org"", which does not describe this page
+> see https://meta.wikimedia.org/wiki/Tech for a better way to provide consistent navigation/page structure across a set of dispersed pages without use of subpages you asked :)",1415025314,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_description,declined
+Consolidate the many tech events calendars in Phabricator's calendar,"I would not reopen but keep this declined. Phabricator Calendar is a rudimentary ""Prototype"" application which currently lacks a few things.",1611614207,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Should this be reopened since Space has been abandoned?,1611613347,PHID-USER-bvi77f4zkvm3mrkrqvwp,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Yes, agreed.",1563807275,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Boldly declining this in favor of https://discuss-space.wmflabs.org/c/events/l/calendar,1563466400,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Also note that https://discourse.wmflabs.org/c/12-local-events exists now.,1531658546,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I'd propose to revert 2015's T1035#1579199 and go back to the original task scope.
+
+> We can use Developer-Wishlist (2017) to check how much interest there is for this idea.
+#66 out of 76, for the records.",1528549290,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Meanwhile, Meta seems to be moving to a wiki-based calendar: https://meta.wikimedia.org/wiki/Template:Events_calendar",1528195216,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"[See Also] Similar task for (non-technical) Education events, wondering where they should put such a potential calendar: {T111968}",1523261235,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,WMFR also worked on something on-wiki: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=831389270#Events_calendar,1521541032,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I keep not having time to even start thinking seriously on this task, and I believe it is better to reflect reality.",1519735180,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,This task is now a #goal. I need to update the description.,1507103115,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I realize this is well-underway but I recently came across [[ https://hackshackers.github.io/misinfocon-event-calendar/ | this public events calendar ]] and really liked the format and the code is [[ https://github.com/hackshackers/misinfocon-event-calendar | up on GitHub ]] so I thought I would share as a stickie in case there are future revisions planned down the road.
+
+(I also realize this could be a totally annoying update given the status of the project so if it's irrelevant, please ignore and forget this message ever existed. :))",1496150582,PHID-USER-w5dqcsw7esxdqy3say2e,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#3104260, @Aklapper wrote:
+> * DONE: [[ https://secure.phabricator.com/T10747 | Import and export ICS from Calendar ]]
+
+Pretty useless though in its current form as there is no stable export URL (the ""export"" link just takes you to a web page that initiates download of the actual file via JS) so you cannot plug an URL into your calendar client and get changes to the event automatically synced.
+
+> * DONE: [[ https://secure.phabricator.com/T7929 | Integrate Calendar with external systems ]]
+
+Declined, actually (upstream uses task statuses in weird ways), except for Google Calendar integration, which has not been done yet.",1496148909,PHID-USER-a6p24cvyblhfzc7we7nc,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Removed parent task T136213 as the technical side seems to be done.,1494331203,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Agreed.,1489757391,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Status update of related upstream tasks:
+* DONE: [[ https://secure.phabricator.com/T10747 | Import and export ICS from Calendar ]]
+* DONE: [[ https://secure.phabricator.com/T7944 | Add Conduit support to Calendar ]]
+* DONE: [[ https://secure.phabricator.com/T7929 | Integrate Calendar with external systems ]]
+* [[ https://secure.phabricator.com/T7924 | Unprototyping the calendar application ]] in upstream has not happened. It only depends on 
+** [[ https://secure.phabricator.com/T7930 | Let Calendar provide date services to other applications ]] 
+** and potentially [[ https://secure.phabricator.com/T8022 | Implement a meeting autoscheduler ]] (listed in task deps but not in task desc).
+The first item is likely still a blocker (Google Calendar being popular) for this very downstream task T1035, while I think the second might not be that crucial for us?",1489616971,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"This project is selected for the #developer-wishlist voting round and will be added to a MediaWiki page very soon. To the subscribers, or proposer of this task: please help modify the task description: add a brief summary (10-12 lines) of the problem that this proposal raises, topics discussed in the comments, and a proposed solution (if there is any yet). Remember to add a header with a title ""Description,"" to your content. Please do so before February 5th, 12:00 pm UTC. ",1486164935,PHID-USER-dho6cgabdzx4ehinmzcd,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,We can use #devwish17 to check how much interest there is for this idea.,1484641614,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Re DevSummit: Hmm, I'm not convinced. ""Dealing with calendar data in the Wikimedia movement""?",1477587409,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Would this task be a good topic for the #wikidev17 ? If so, the deadline to submit new proposals is next Monday, October 31: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation",1477576972,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2698874, @Qgil wrote:
+> I just 
+> 
+> # created {E329}
+> # clicked ""Export as .ics"", and an .ics file was downloaded to my laptop
+> # imported the .ics file to my Google Calendar
+> 
+> The event is now visible in my calendar. Progress!
+
+So as in mine. I don't know if it was the expected result. ;)",1475848243,PHID-USER-uciss2jl2e4ifxqqk7wk,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"There is more coming (just landing in Phabricator HEAD, not stable yet):
+
+https://secure.phabricator.com/book/phabricator/article/calendar_exports/",1475847624,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I just 
+
+# created {E329}
+# clicked ""Export as .ics"", and an .ics file was downloaded to my laptop
+# imported the .ics file to my Google Calendar
+
+The event is now visible in my calendar. Progress!",1475829026,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I just 
+
+# created {E329}
+# clicked ""Export as .ics"", and an .ics file was downloaded to my laptop
+# imported the .ics file to my Google Calendar
+
+It's there. Progress!",1475828997,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I just created {E329}, then clicked ""Export as .ics"", then import to my Google Calendar. It's there. Progress!",1475828903,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,(Aforementioned deployment postponed due to Ops offsite),1475177370,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,@qgil: That will land in our phabricator tomorrow night (midnight UTC) when I deploy #phab-2016-09-28 ,1475015490,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Initial support for ICS export is available in Phabricator HEAD, and the work is continuing as we speak -- see https://secure.phabricator.com/T10747
+
+I am counting on this ICS support for this proposal: {T146749}",1474981509,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Punting to Oct-Dec for Dev-Rel. 
+Not to happen this quarter as long as T136213 isn't resolved which is external.",1474644859,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@CKoerner_WMF - as I noted earlier, Semantic MediaWiki was declined for use on Wikipedia, in favor of Wikidata. (Which was the right choice.) I don't believe it has ever been reviewed for use on, say, mediawiki.org.
+
+And - though I'm repeating myself - Cargo is, in my opinion, the better option. But either one would work.",1466023933,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Just to chip in my $.02, I would encourage us to look for a solution that can be used on-wiki. There's something about investing time/money/energy in on-wiki solutions that sits better with me. Maybe it has to do with an on-wiki solution being more inviting. People without or only entry level development skills will find the information easier than here in phabricator, where super dev skills are the norm. :)
+
+I understand that SMW was declined many years ago. What were the reasons for the declination? It's not clear to me if those still stand today. Could those be addressed?
+
+@Yaron_Koren You're far more savvy with this than I, but does SMW meet these requirements? https://wikitech.wikimedia.org/wiki/Writing_an_extension_for_deployment
+
+My personal bias aside, SMW seems like a present solution that is free, on-wiki, adaptable, and within our own MediaWiki community. Much different than spending money on a one-time development of a feature from an outside vendor. Ok, that was totally biased. ",1466022679,PHID-USER-iwx53fdq7w3yv4h7wffx,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Just a reminder that if, say, Cargo and Semantic Forms were installed on mediawiki.org today, there would be functioning event-entry forms and event calendars on the site, probably by the end of the day. (And at no cost.)",1466010033,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wikimedia groups like WMES don't need to install their own Phabricator instance. They can use Wikimedia Phabricator instead.
+
+Only the users willing to introduce and manage calendar data would need to create an account here (which they can do with their Wikimedia accounts). Users only needing to access that data can visit the URLs of the calendars they are interested about, and according to this proposal they will be able to import Wikimedia Phabricator calendar data to their own calendars importing the iCalendar files (.ics)
+
+Users with a Phabricator account are able to RSVP, comment, and associate events to other projects (promoting activities to the users following those projects).
+
+@BrillLyle, we are not trying to compete with Google Calendar, but I think we can aim to provide the basic functionality that most people may need for Wikimedia activities. From your list:
+
+* Time zone support. Events are created with the timezone of the event creator, and that [[ https://phabricator.wikimedia.org/settings/panel/datetime/ | timezone can be defined ]] in the user profile. As of today, events cannot be created in a different timezone, but this is a problem with a simple workaround (find out the time in your own timezone). Not a blocker.
+
+* Color coding. Missing indeed. Icons can be defined for events, and if this is considered important then perhaps colors could be defined as well, just like it is possible to define icons and color for projects. This looks like an improvement simple to implement that would provide basic color cues in calendars.
+
+* Ability to select and maintain different calendars. This is possible, by associating events to projects (i.e. ArchCom meetings, Tech Talks, Wikimania Hackathon 2016...) and by [[ https://phabricator.wikimedia.org/calendar/query/advanced/ | querying events ]] in a pretty advanced way (i.e. IRC Office Hours about VisualEditor during 2015, displayed in month view). These queries provide static URLs that can be shared with users.
+
+* Ability to copy to events to personal calendar. Phabricator users can RSVP already now, and this will make events appear in their personal Phabricator calendar. According to this proposal, they will be able to import the .ics data as well, which will integrate such data in their calendar apps.",1463465173,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wikimedia groups like WMES don't need to install their own Phabricator instance. They can use Wikimedia Phabricator instead.
+
+Only the users willing to introduce and manage calendar data would need to create an account here (which they can do with their Wikimedia accounts). Users only needing to access that data can visit the URLs of the calendars they are interested about, and according to this proposal they will be able to import Wikimedia Phabricator calendar data to their own calendars importing the iCalendar files (.ics)
+
+Users with a Phabricator account will be able to RSVP, comment, and associate events to other projects (promoting activities to the users following those projects).
+
+@BrillLyle, we are not trying to compete with Google Calendar, but I think we can aim to provide the basic functionality that most people may need for Wikimedia activities. From your list:
+
+* Time zone support. Events are created with the timezone of the event creator, and that [[ https://phabricator.wikimedia.org/settings/panel/datetime/ | timezone can be defined ]] in the user profile. As of today, events cannot be created in a different timezone, but this is a problem with a simple workaround (find out the time in your own timezone). Not a blocker.
+
+* Color coding. Missing indeed. Icons can be defined for events, and if this is considered important then perhaps colors could be defined as well, just like it is possible to define icons and color for projects. This looks like an improvement simple to implement that would provide basic color cues in calendars.
+
+* Ability to select and maintain different calendars. This is possible, by associating events to projects (i.e. ArchCom meetings, Tech Talks, Wikimania Hackathon 2016...) and by [[ https://phabricator.wikimedia.org/calendar/query/advanced/ | querying events ]] in a pretty advanced way (i.e. IRC Office Hours about VisualEditor during 2015, displayed in month view). These queries provide static URLs that can be shared with users.
+
+* Ability to copy to events to personal calendar. Phabricator users can RSVP already now, and this will make events appear in their personal Phabricator calendar. According to this proposal, they will be able to import the .ics data as well, which will integrate such data in their calendar apps.",1463464977,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@Qgil  Wouldn't that require that each of our members created an account here? (Not that this was available until recently, so it's no wonder it hadn't been brought up as anoption). It may be worth trying, though.
+
+And installing a local phabricator instance… no, thanks.",1463447343,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@Qgil -- Hi Yes I have looked at the **[[ https://phabricator.wikimedia.org/calendar/query/month/ | Phabricator Calendar ]].** It seems fine but there are some significant things missing that would mean loss of functionality. (i.e., time zone support, color coding, ability to select and maintain different calendars, ability to copy to events to personal calendar, etc.). It also requires end users sign in using OAuth and have a Phabricator account, correct? We have problems getting participants onboarded to the en-Wiki so this is another thing that I'm just thinking of. Unless this solution was fully integrated with Wikipedia where it would not require logging in to another system to easily copy/export events, I am concerned this is a big issue.
+
+The fact of the matter is that the current reliance on Google and Facebook is a reality for most end users and organizers. So I think that while the focus of this solution is on Phabricator and MediaWiki options, it would be a bit ""head in the sand"" to ignore the reality of what is going on. These popular external calendars need to be able to be integrated -- either in export or import -- somehow with existing systems. They are sort of the only game in town calendar-wise, and it's not just because of market share, but because of functionality and the integratedness of the two options.
+
+Sorry, I don't mean to be demanding (but I am) or discouraging (yeah that too).
+
+– Erika
+User:BrillLyle
+
+
+>>! In T1035#2295877, @Qgil wrote:
+> 
+> @BrillLyle, have you tried Phabricator Calendar? I think it is quite low barrier as soon as users don't make the mental connection ""Phabricator == technical, not for me"", but I would be very interested in discussing the details.
+> 
+> I am not proposing to rely on Google, Facebook on anything at Wikimedia, so we can take this topic out of this discussion.
+> 
+> Anyone can request funding to develop a MediaWiki extension that allows  native input of calendar data. It's just that such funding request will need to come from [[ https://meta.wikimedia.org/wiki/Grants | grants ]], because (for the bureaucratic-sounding but very real reasons I have explained) the budget that our team has right now will not be available on July 1.",1463406303,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"By the way, I just rewrote this page, to be clearer and more up-to-date:
+
+https://www.mediawiki.org/wiki/Extension:Calendar",1463351662,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"A solution that would work for the Wikimedia Tech community is not a suboptimal solution, is a valid solution for a specific problem (which doesn't conflict with potential solutions for the non-tech Wikimedia communities).
+
+As for the general problem...
+
+@Platonides, can you show the use of calendar by Wikimedia Spain? Installing OwnCloud on your own server looks like a much more technical and involved task than just using Phabricator Calendar for your org/project. For what is worth, every time there are more chapters and non-tech groups that are using Phabricator as a project management tool.
+
+@BrillLyle, have you tried Phabricator Calendar? I think it is quite low barrier as soon as users don't make the mental connection ""Phabricator == technical, not for me"", but I would be very interested in discussing the details.
+
+I am not proposing to rely on Google, Facebook on anything at Wikimedia, so we can take this topic out of this discussion.
+
+Anyone can request funding to develop a MediaWiki extension that allows  native input of calendar data. It's just that such funding request will need to come from [[ https://meta.wikimedia.org/wiki/Grants | grants ]], because (for the bureaucratic-sounding but very real reasons I have explained) the budget that our team has right now will not be available on July 1.",1463330999,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"A solution that would work for the Wikimedia Tech community is not a suboptimal solution, is a valid solution for a specific problem (which doesn't conflict with potential solutions for the non-tech Wikimedia communities).
+
+As for the general problem...
+
+@Platonides, can you show the use of calendar by Wikimedia Spain? Installing OwnCloud on your own server looks like a much more technical and involved task than just using Phabricator Calendar for your org/project. For what is worth, every time there are more chapters and non-tech groups that are using Phabricator as a project management tool.
+
+@BrillLyle, have you tried Phabricator Calendar? I think it is quite low barrier as soon as users don't make the mental connection ""Phabricator == technical, not for me"", but I would be very interested in discussing the details.
+
+I am not proposing to rely on Google, Facebook on anything at Wikimedia, so we can take this topic out of this discussion.
+
+Anyone can request funding to develop a MediaWiki extension that allows  native input of calendar data. It's just that such funding request will need to come from [[ https://meta.wikimedia.org/wiki/Grants | grants ]], because (for the bureaucratic-sunding but very real reasons I have explained) the budget that our team has right now will not be available on July 1.",1463330943,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"A solution that would work for the Wikimedia Tech community is not a suboptimal solution, is a valid solution for a specific problem, that is not in direct competition with other potential solutions.
+
+As for the general problem...
+
+@Platonides, can you show the use of calendar by Wikimedia Spain? Installing OwnCloud on your own server looks like a much more technical and involved task than just using Phabricator Calendar for your org/project. For what is worth, every time there are more chapters and non-tech groups that are using Phabricator as a project management tool.
+
+@BrillLyle, have you tried Phabricator Calendar? I think it is quite low barrier as soon as users don't make the mental connection ""Phabricator == technical, not for me"", but I would be very interested in discussing the details.
+
+I am not proposing to rely on Google, Facebook on anything at Wikimedia, so we can take this topic out of this discussion.
+
+Anyone can request funding to develop a MediaWiki extension that allows  native input of calendar data. It's just that such funding request will need to come from [[ https://meta.wikimedia.org/wiki/Grants | grants ]], because (for the bureaucratic-sunding but very real reasons I have explained) the budget that our team has right now will not be available on July 1.",1463330861,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I agree that just because there is a budget and a time constraint doesn't mean that's the best approach -- especially because a bandaid and/or short-term solution may not provide what is needed in the long-term. 
+
+The google calendar and folks using Facebook event pages seems to be working right now. Is it ideal? No. 
+
+The lowest technical barrier on the end users and organizers is my biggest concern. Not sure any of these options is an improvement -- or needs to be a focus of this discussion. But wanted to mention it just in case. 
+
+Erika
+User:BrillLyle
+
+>>! In T1035#2295720, @Platonides wrote:
+> 
+> Should we spend budget in a suboptimal solution because of time constraints for expenditure in the TC team?
+> It may be worth it for the interim benefit. And while I prefer to spend money that way than developer hours, it's still a tough decision.
+
+
+",1463323693,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"One important reason for WM-ES to install Owncloud was precisely so we could use its calendar features.
+Storing calendars in external platforms like Google of Facebook is far from ideal. Even if people really had it in one of those unfree platforms{{citation needed}}, the problem is not just //showing// the ics calendar, but also //editing// it.
+If it's stored in the wiki, that would be relatively straightforward, compare that to finding out it is included from a Facebook calendar, which requires  you to create a Facebook account, then ask for permission to someone else (which may not even be too active now) for changing the calendar, just to enter your local event.
+And all of these duplicating the existing organization at a parallel site.
+
+Storing the calendars in phabricator may work for the Wikimedia technical community, but doesn't solve the problem for the second group.
+
+
+>>! In T1035#2295517, @Qgil wrote:
+> Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+
+Should we spend budget in a suboptimal solution because of time constraints for expenditure in the TC team?
+It may be worth it for the interim benefit. And while I prefer to spend money that way than developer hours, it's still a tough decision.",1463320979,PHID-USER-izojihzr4ja3jsgzn5wv,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Qgil wrote:
+
+> SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+
+If anyone's wondering, I assume he's referring to this ticket: T53642. To summarize that discussion: three of the DevOps people want to replace SMW on their system with dedicated DevOps tools. How relevant that is to this discussion is a matter of personal opinion.
+
+I hate to sound like a broken record here, but SMW is already in successful use on hundreds of wikis, including probably dozens where it's used specifically to manage calendar and event data. It provides all the functionality that people are talking about here, as far as I can tell: data entry, standard calendars, customized views/queries, data export. Cargo is a newer extension (first released in 2015), so it hasn't gotten as much use so far, but it does essentially all the same stuff as SMW.",1463316950,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thank you for the quick and diverse feedback provided so far. Some thoughts:
+
+Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+* The Technical Collaboration team has some budget available for FY2015-16, to be used by the end of June. What can be achieved within this timeline? Certainly not anything in the form of a new extension in the Wikimedia cluster. In comparison, the Phabricator Calendar improvements could be developed and deployed in Wikimedia within that timeframe.
+* Who is going to develop that extension? After agreeing on a plan for a MediaWiki extension, we need to define who will work on it as paid work, which also takes time. In comparison, funding Phacility Inc for Phabricator upstream improvements is a straightforward and quick decision.
+* Who is going to maintain that extension? The Technical Collaboration team doesn't have the skills to maintain it, and the Community Engagement department has a known problem of mid term sustainability plans of the software we commission and own. While other CE teams are trying to reduce and resolve this problem, TC cannot just start the development of a new extension without a maintenance plan. In comparison, the Phabricator improvements funded would be maintained by the Phabricator maintainers.
+
+When it comes to the technical plan, things are anything but clear:
+The first requirement is **Introducing calendar data**, something that plain MediaWiki was not designed for. 
+* SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+* Recent efforts on developing extensions focusing on input of structured data via forms (limiting wiki editing in its purest sense) are being met by a small but perseverant current of criticism. Would this project conflict with that view? (I don't agree with such view, and I wouldn't want to be a participant in such discussion)
+* In previous discussions about something new, Wikidata was mentioned as part of the solution, and then the Wikidata team disagreed for reasons that I found convincing. Is this another of these cases? In any case, that would not solve the input problem immediately either.
+* In comparison, Phabricator Calendar provides a way to input data designed for events, it is based on free software, and it is already deployed in Wikimedia servers.
+
+I think that starting this effort by requiring native calendar input data in MediaWiki is not the best tactic. Once the calendar data is introduced and available somewhere via .ics, a MediaWiki extension could focus on its presentation in MediaWiki pages. That would probably solve better the 3rd use case, since I can imagine many MediaWiki users needing calendar data in their wikis to have that data already in Google Calendar, Facebook Events, or elsewhere able to export data via .ics.
+
+I also want to note that output in MediaWiki pages is not the only destination of calendar data, and I would even contest the idea that it is the most important. I believe that most of our users would use this data integrated in their own calendars, importing Wikimedia events/calendars and following their updates from their calendar apps. That is also a reason why I am not obsessed with having MediaWiki output first, or as a requirement for any first step.
+
+For all these reasons, I still think that improving Phabricator Calendar is the best first step solving our problems with calendars. A step that would solve most of the Wikimedia tech problems, and a step that would be in a direction compatible with solving the problem for the rest of Wikimedia, and other MediaWiki users.
+
+The MediaWiki extension able to read .ics data and embed it in MediaWiki pages could be a good candidate for an Individual Engagement Grant. That program is well suited to evaluate movement priorities, feasibility of plans, and funding specific contributors, all done under a community review process. 
+
+If we solve the Phabricator Calendar piece in the next 2-3 months, and the MediaWiki extension piece in the next IEG round, we could have a good enough solution for everybody by the end of the year or so.",1463308865,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thank you for the quick and diverse feedback provided so far. Some thoughts:
+
+Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+* The Technical Collaboration team has some budget available for FY2015-16, to be used by the end of June. What can be achieved within this timeline? Certainly not anything in the form of a new extension in the Wikimedia cluster. In comparison, the Phabricator Calendar improvements could be developed and deployed in Wikimedia within that timeframe.
+* Who is going to develop that extension? After agreeing on a plan for a MediaWiki extension, we need to define who will work on it as paid work, which also takes time. In comparison, funding Phacility Inc for Phabricator upstream improvements is a straightforward and quick decision.
+* Who is going to maintain that extension? The Technical Collaboration team doesn't have the skills to maintain it, and the Community Engagement department has a known problem of mid term sustainability plans of the software we commission and own. While other CE teams are trying to reduce and resolve this problem, TC cannot just start the development of a new extension without a maintenance plan. In comparison, the Phabricator improvements funded would be maintained by the Phabricator maintainers.
+
+When it comes to the technical plan, things are anything but clear:
+The first requirement is **Introducing calendar data**, something that plain MediaWiki was not designed for. 
+* SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+* Recent efforts on developing extensions focusing on input of structured data via forms (limiting wiki editing in its purest sense) are being met by a small but perseverant current of criticism. Would this project conflict with that view? (I don't agree with such view, and I wouldn't want to be a participant in such discussion)
+* In previous discussions about something new, Wikidata was mentioned as part of the solution, and then the Wikidata team disagreed for reasons that I found convincing. Is this another of these cases? In any case, that would not solve the input problem immediately either.
+* In comparison, Phabricator Calendar provides a way to input data designed for events, it is based on free software, and it is already deployed in Wikimedia servers.
+
+I think that starting this effort by requiring native calendar input data in MediaWiki is not the best tactic. Once the calendar data is introduced and available somewhere via .ics, a MediaWiki extension could focus on its presentation in MediaWiki pages. That would probably solve better the 3rd use case, since I can imagine many orgs using MediaWiki that already have their calendars in Google, Facebook, or elsewhere able to export data via .ics.
+
+I also want to note that output in MediaWiki pages is not the only destination of calendar data, and I would even contest that idea that it is the most important. I believe that most of our users would use this data integrated in their own calendars, importing Wikimedia calendars and following their updates from their calendar apps. That is also a reason why I am not obsessed with having MediaWiki output first, or as a requirement for any first step.
+
+For all these reasons, I still think that improving Phabricator Calendar is the best first step solving our problems with calendars. A step that would solve most of the Wikimedia tech problems, and a step that would be in a direction compatible with solving the problem for the rest of Wikimedia, and other MediaWiki users.
+
+The MediaWiki extension able to read .ics data and embed it in MediaWiki pages could be a good candidate for an Individual Engagement Grant. That program is well suited to evaluate movement priorities, feasibility of plans, and funding specific contributors, all done under a community review process. 
+
+If we solve the Phabricator Calendar piece in the next 2-3 months, and the MediaWiki extension piece in the next IEG round, we could have a good enough solution for everybody by the end of the year or so.",1463308605,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thank you for the quick and diverse feedback provided so far. Some thoughts:
+
+Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+* The Technical Collaboration team has some budget available for FY2015-16, to be used by the end of June. What can be achieved within this timeline? Certainly not anything in the form of a new extension in the Wikimedia cluster. In comparison, the Phabricator Calendar improvements could be developed and deployed in Wikimedia within that timeframe.
+* Who is going to develop that extension? After agreeing on a plan for a MediaWiki extension, we need to define who will work on it as paid work, which also takes time. In comparison, funding Phacility Inc for Phabricator upstream improvements is a straightforward and quick decision.
+* Who is going to maintain that extension? The Technical Collaboration team doesn't have the skills to maintain it, and the Community Engagement department has a known problem of mid term sustainability plans of the software we commission and own. While other CE teams are trying to reduce and resolve this problem, TC cannot just start the development of a new extension without a maintenance plan. In comparison, the Phabricator improvements funded would be maintained by the Phabricator maintainers.
+
+When it comes to the technical plan, things are anything but clear:
+The first requirement is **Introducing calendar data**, something that plain MediaWiki was not designed for. 
+* SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+* Recent efforts on developing extensions focusing on input of structured data via forms (limiting wiki editing in its purest sense) are being met by a small but perseverant current of criticism. Would this project conflict with that view (I don't agree with such view, and I wouldn't want to be a participant in such discussion).
+* In previous discussions about something new, Wikidata was mentioned as part of the solution, and then the Wikidata team disagreed for reasons that I found convincing. Is this another of these cases? In any case, that would not solve the input problem immediately either.
+* In comparison, Phabricator Calendar provides a way to input data designed for events, it is based on free software, and it is already deployed in Wikimedia servers.
+
+I think that starting this effort by requiring native calendar input data in MediaWiki is not the best tactic. Once the calendar data is introduced and available somewhere via .ics, a MediaWiki extension could focus on its presentation in MediaWiki pages. That would probably solve better the 3rd use case, since I can imagine many orgs using MediaWiki that already have their calendars in Google, Facebook, or elsewhere able to export data via .ics.
+
+I also want to note that output in MediaWiki pages is not the only destination of calendar data, and I would even contest that idea that it is the most important. I believe that most of our users would use this data integrated in their own calendars, importing Wikimedia calendars and following their updates from their calendar apps. That is also a reason why I am not obsessed with having MediaWiki output first, or as a requirement for any first step.
+
+For all these reasons, I still think that improving Phabricator Calendar is the best first step solving our problems with calendars. A step that would solve most of the Wikimedia tech problems, and a step that would be in a direction compatible with solving the problem for the rest of Wikimedia, and other MediaWiki users.
+
+The MediaWiki extension able to read .ics data and embed it in MediaWiki pages could be a good candidate for an Individual Engagement Grant. That program is well suited to evaluate movement priorities, feasibility of plans, and funding specific contributors, all done under a community review process. 
+
+If we solve the Phabricator Calendar piece in the next 2-3 months, and the MediaWiki extension piece in the next IEG round, we could have a good enough solution for everybody by the end of the year or so.",1463308541,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thank you for the quick and diverse feedback provided so far. Some thoughts:
+
+Sure, the perfect solution would be a MediaWiki extension deployed in Wikimedia and available for 3rd parties, but let me share why I think this is not possible within the scope of this exercise:
+* The Technical Collaboration team has some budget available for FY2015-16, to be used by the end of June. What can be achieved within this timeline? Certainly not anything in the form of a new extension in the Wikimedia cluster. In comparison, the Phabricator Calendar improvements could be developed and deployed in Wikimedia within that timeframe.
+* Who is going to develop that extension? After agreeing on a plan for a MediaWiki extension, we need to define who will work on it as paid work, which also takes time. In comparison, funding Phacility Inc for Phabricator upstream improvements is a straightforward and quick decision.
+* Who is going to maintain that extension? The Technical Collaboration team doesn't have the skills to maintain it, and the Community Engagement department has a known problem of mid term sustainability plans of the software we commission and own. While other CE teams are trying to reduce and resolve this problem, TC cannot just start the development of a new extension without a maintenance plan.
+
+When it comes to the technical plan, things are anything but clear:
+The first requirement is **Introducing calendar data**, something that plain MediaWiki was not designed for. 
+* SemanticMediaWiki is designed for semantic input, but I think it is safe to assume that Wikimedia is not going to increase its dependency on SMW when the trend on wikitech.wikimedia.org / Labs is the opposite.
+* Recent efforts on developing extensions focusing on input of structured data via forms (limiting wiki editing in its purest sense) are being met by a small but perseverant current of criticism. Would this project conflict with that view (I don't agree with such view, and I wouldn't want to be a participant in such discussion).
+* In previous discussions about something new, Wikidata was mentioned as part of the solution, and then the Wikidata team disagreed for reasons that I found convincing. Is this another of these cases? In any case, that would not solve the input problem immediately either.
+* In comparison, Phabricator Calendar provides a way to input data designed for events, it is based on free software, and it is already deployed in Wikimedia servers.
+
+I think that starting this effort by requiring native calendar input data in MediaWiki is not the best tactic. Once the calendar data is introduced and available somewhere via .ics, a MediaWiki extension could focus on its presentation in MediaWiki pages. That would probably solve better the 3rd use case, since I can imagine many orgs using MediaWiki that already have their calendars in Google, Facebook, or elsewhere able to export data via .ics.
+
+I also want to note that output in MediaWiki pages is not the only destination of calendar data, and I would even contest that idea that it is the most important. I believe that most of our users would use this data integrated in their own calendars, importing Wikimedia calendars and following their updates from their calendar apps. That is also a reason why I am not obsessed with having MediaWiki output first, or as a requirement for any first step.
+
+For all these reasons, I still think that improving Phabricator Calendar is the best first step solving our problems with calendars. A step that would solve most of the Wikimedia tech problems, and a step that would be in a direction compatible with solving the problem for the rest of Wikimedia, and other MediaWiki users.
+
+The MediaWiki extension able to read .ics data and embed it in MediaWiki pages could be a good candidate for an Individual Engagement Grant. That program is well suited to evaluate movement priorities, feasibility of plans, and funding specific contributors, all done under a community review process. 
+
+If we solve the Phabricator Calendar piece in the next 2-3 months, and the MediaWiki extension piece in the next IEG round, we could have a good enough solution for everybody by the end of the year or so.",1463307550,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"After a first wave of feedback it is clear that we have two different discussions that need solving:
+
+# If we use WMF Technical Collaboration budget for Phabricator improvements, should we invest it the Calendar application? This is a well framed discussion with a clear deadline for decisions (very soon, or our FY2015-16 budget will be gone). I have created a task to discuss this specifically: {T135327}
+# If we want to improve the announcement and promotion of Wikimedia tech events, is the best first step to improve Phabricator Calendar? This is a complex discussion with many ramifications that we can keep discussing here.",1463304220,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@JanZerebecki - actually, both Semantic MediaWiki and Cargo can have their data displayed on other wikis. They both can export their data via the API, in formats including JSON and iCalendar (well, Cargo doesn't currently support iCalendar, but it would be easy to add it in). To be able to get and display the JSON data, any other wiki would just need to have the External Data extension installed:
+
+https://www.mediawiki.org/wiki/Extension:External_Data
+
+As for getting iCalendar data and actually being able to display a calendar with that information, the Widgets extension, and specifically the Google Calendar widget, could probably be used for that:
+
+http://www.mediawikiwidgets.org/Google_Calendar",1463275196,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wikibase (thus Wikidata) is able to store the required information. The time portion of dates might need some love first, though. It is able to provide that information to multiple clients (all Wikimedia wikis). And to external consumers in various formats. (Perhaps query.wikidata.org needs support to output ics! Sometime after exposing results to Lua.) Maybe conference occurrences can be entered in Wikidata (like was done for Wikimania 2016 https://www.wikidata.org/wiki/Q19291990 ) and maybe that could then link to their ics URL of the schedule...
+
+SMW is as the links above show able to store the required information. AFAIK as is, it is not able to provide that information to other wikis than the wiki where it is stored, though it can probably provide it to external consumers in various formats. Would be useful if SMW and Wikibase supported a common query result format. So that they could share many extensions. We didn't update the version of SMW that is running on one of the Wikimedia wikis. See e.g. https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/1479 (could need some love independent of this task).
+
+The Phabricator calendar doesn't automatically subscribe me to materialized instances of recurring events. (That reminds me that we have tasks that we manually repeat where I sometimes also need to subscribe to the next one manually depending on if the subscribers were copied.)
+> I oppose spending money on this unless we first spend money on the Phabricator upstream bugs which Wikimedia users suffer from.
+Yes #Phabricator-Upstream has some that are more important than those related to Calendar.
+
+Anything that doesn't export caldav/ical doesn't help me personally (all people I know use devices and software that can consume CaldDav or ics files from the Internet).
+Special Google Calendar support is probably not needed as google supports ics.
+Ext:Cargo sounds interesting. Other back ends (than SMW) could be supported in the same way.
+I personally use https://en.wikipedia.org/wiki/DAViCal as a back end.
+Still need to find something to sync ics files to a CalDav server. And something to filter and aggregate calendar events ( like query.wikidata.org ? ), e.g. to get an ics file with all events related to open educational resources (Q116781) that are at most 10km from the center of Berlin (Q64).
+
+Does FullCalendar support CalDav?
+http://agendav.org/ looks interesting as a front end.",1463241475,PHID-USER-mdihg2tyzmlvyhn3h32y,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I think we should be looking at the possibility of different solutions to serve the different purposes:
+
+* Firstly (as the basis of this task) we want a solution for the Tech crowd, where we can use tags, cross reference teams, tasks, subscribe/cc to follow, ACLs and the likes, and since Phabricator is already our central point it may be the best contender or it may not be once we start looking at extended features (example: displaying inside MediaWiki, exporting via standard formats etc, syncing to personal devices).
+
+* Secondary (probably best discussed in a separate task) appears to be where we want a calendaring solution for those that are primarily in the wiki-sphere and don't use Pharicator as a central discussion location and want to manage wholelly on a wiki based level (eg: WikiCons, meetups, EditThons).
+
+",1463223449,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,I oppose spending money on this unless we first spend money on the Phabricator upstream bugs which Wikimedia users suffer from.,1463218135,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,I would also like to see a calendar solution that is usable for 3rd party Mediawiki users.,1463198128,PHID-USER-fo56wm4wxiwpoofn2xdu,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@Qgil posted on wikitech-l asking for feedback about this. He writes:
+
+> The Technical Collaboration team has some budget that we could use to fund the Phabricator maintainers to prioritize some improvements in their Calendar. If you think this is a bad idea and/or you have a better one, please discuss in the task (preferred) or here.
+
+I'd personally prefer to see a calendar solution that integrates with MediaWiki. Many of the use-cases mentioned in this task relate to our wikis.
+
+There are times when investing in another organization's platform makes sense, but in this case, I think investing in our own platform is probably more prudent. As demonstrated by the dozen MediaWiki extensions in this space, there's demand among ""third-party"" (i.e., non-Wikimedia) MediaWiki installations—including wikis that I administer—to have a usable calendar system.",1463190845,PHID-USER-hyfm4swq76s4j642w46x,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"The thing that us folks doing Wikipedia:Meetup editathons need is **something that can be maintained on the Wikipedia namespace **-- and probably for those still using Meta for use on that namespace as well.
+
+For the WM NYC chapter, we have been putting our event pages on Wikipedia via Wikipedia:Meetup as it is a semi-passive way to onboard people onto the main Wiki. Plus a lot of templates don't play well with Meta -- blargh. So that functionality / integration especially would be super helpful for the chapter.
+
+I think other chapters and probably more global meetups use Meta -- WM NYC doesn't really use our Meta that much, especially not for calendar-related activities. Again we are trying to point people to one main URI if possible. We have over 20 events (not including outliers) so far this year and it's only May, so this would be something used in a very robust way.
+
+If MediaWiki is not implementable onto the main Wiki, and assume Wikidata obviously (?) isn't an option for calendaring (?), then would Phabricator Calendar be able to be embedded onto Wikipedia:Meetup namespaces? We would really really like that. A lot.
+
+I'm probably using the term namespace incorrectly but it makes sense to my pea brain. Apologies for the lack of precision. I'm more of an end user experience person.
+
+Also, is the afore-mentioned Calagator just completely not an option? It doesn't have the bells and whistles of Google calendar but it seems sort of cool.
+
+– Erika 
+User:BrillLyle
+
+",1463184609,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I would appreciate an improvement to the calendar situation, not just for tech events but also for finance, fundraising, community, and everything else. I haven't looked into Cargo or SMW calendars in any detail, but I'd like to see *some* kind of progress on an open source calendar that can be used widely including outside of WMF by affiliates. Thanks!",1463178969,PHID-USER-l7v72q5tq6vg6zclrld6,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"@Krenair - that was a discussion about including SMW on Wikipedia and the like; SMW was rejected in favor of Wikidata. It's unrelated to its use on ""internal"" sites like mediawiki.org and meta.wikimedia.org. Again, though, I personally think Cargo is the superior solution.",1463177991,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,SMW was already declined years ago: {T10390},1463175018,PHID-USER-x7ti5ksby4ubsabntlxa,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"There are already two MediaWiki extensions that handle the display of calendars very well: Semantic MediaWiki and Cargo. Both let you query events in any number of ways, displaying subsets of events and allowing for color-coding and so forth. When used in conjunction with the Semantic Forms extension for entering event data (which can be used with either SMW or Cargo), the whole system becomes fairly simple to use.
+
+https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki
+https://www.mediawiki.org/wiki/Extension:Cargo
+https://www.mediawiki.org/wiki/Extension:Semantic_Forms
+
+Personally, I think Cargo is a little nicer to use, but you can see here a nice demonstration of how SMW and SF were used together to enter the data for, and display, a conference schedule:
+
+https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2015/Calendar
+
+This is using the FullCalendar JS library:
+
+http://fullcalendar.io/",1463174574,PHID-USER-7jqnferdzzzwelhzchyo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I have updated the description adding the relevant information in the thread. If you are missing important bits, please add them.
+
+I have sent an informal call for feedback to wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085613.html
+
+The goal is to make a decision soon-ish, and if that decision is to fund the Phabricator maintainers, sign the agreement by the end of the month, and get the work done during June-July:
+
+# Unprototyping Calendar (mainly updating backend stuff?)
+# A Good API (tm)
+# .ics support
+# Basic Google Calendar support
+
+I wonder what would be the best way to proceed with the MediaWiki extension. If we get the Phabricator side done, it would be a decent candidate for the next Outreachy or Individual Engagement Grants rounds.",1463168681,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I have updated the description adding the relevant information in the thread. If you are missing important bits, please add them.
+
+I have sent an informal call for feedback to wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085613.html
+
+The goal is to make a decision soon-ish, and if that decision is to fund the Phabricator maintainers, sign the agreement by the end of the month, and get the work done during June-July:
+
+# Unprototyping Calendar (mainly updating backend stuff?)
+# A Good API (tm)
+# .ics support
+# Basic Google Calendar support
+
+I wonder what would be the best way to proceed with the MediaWiki extension. If we get the Phabricator side done, it would be decent candidate for the next Outreachy or Individual Engagement Grants rounds.",1463168661,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I have updated the description adding the relevant information in the thread. If you are missing important bits, please add them.
+
+I have sent an informal call for feedback to wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085613.html
+
+The goal is to make a decision soon-ish, and if that decision is to fund the Phabricator maintainers, sign the agreement by the end of the month, and get the work done during June-July:
+
+# Unprototyping Calendar (mainly updating backend stuff?)
+# A Good API (tm)
+# .ics support
+# Basic Google Calendar support
+",1463168574,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2191801, @Quiddity wrote:
+> 1. There's also https://www.mediawiki.org/wiki/Extension:Calendar (a linkhub for the ~12 different extensions or methods of integrating calendars with MediaWiki). If further work was done on one of those, to make it usable by us, many other MediaWiki users would also benefit. 
+
+I went through the list and there was none surviving a basic check against our needs. In fact most of them are more than abandoned, and in general they focus on presentation, not on easy input, even less on semantic data (except the SemanticMediaWiki one, perhaps). [[ https://www.mediawiki.org/wiki/Extension:SimpleCalendar | SimpleCalendar ]] looks like the only candidaste if we would ever want to start from this point.
+
+> There have been 12 attempts at this, for a reason!
+
+Sure, and the reason may well be that MediaWiki was not designed to input calendar data, subscribe to events, etc.
+
+After this short investigation, I still think that it is better to start from something other than MediaWiki, and the main candidate keeps being Phabricator. Then work separately in a way to import Phabricator Calendar data and present it in MediaWiki pages.",1463060811,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"High priority because I need to decide whether we are investing some FY2015-16 budget on a Phabricator Calendar improvement or not, and that decision needs to be made soon.",1462437116,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,,1462389147,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,,1462389023,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I posted this to the main mailing list, just sharing for 100% transparency. WM NYC had one massive calendar but the consensus was it needed to be carved down, so here they are.... :-)
+
+– –
+
+Hello --
+
+In an effort to de-clutter the Wikimedia NYC calendar -- and to support the various initiatives and enhance event calendaring within Wikimedia -- after some active discussion, Wikimedia NYC (well that would be me) has set up the following calendars. 
+
+Many events were pulled from these source:
+- https://meta.wikimedia.org/wiki/Events
+- https://www.mediawiki.org/wiki/Events
+
+Ideally a calendar solution would be open source and Wiki-friendly (see https://phabricator.wikimedia.org/T1035 Consolidate the many tech events calendars in Phabricator's calendar), but Google calendars seem to provide the most functionality right now so this is seen as an interim solution. For reference: https://phabricator.wikimedia.org/calendar/
+
+Please feel free to add events and share widely.
+
+G L O B A L
+
+Wikimedia Global Events
+Calendar ID: 7naa8gc5mjqhgjn1g2pbb4829s@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/7naa8gc5mjqhgjn1g2pbb4829s%40group.calendar.google.com/public/basic.ics
+
+Global Tech Events
+Calendar ID: 8bkj15efk0qgu4jut3oe5kd5eg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/8bkj15efk0qgu4jut3oe5kd5eg%40group.calendar.google.com/public/basic.ics
+
+.–.
+
+I N I T I A T I V E S
+
+AfroCROWD
+Calendar ID: djfkq9sql4h956b8vo6e35h484@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/djfkq9sql4h956b8vo6e35h484%40group.calendar.google.com/public/basic.ics
+
+Art+Feminism -- 3/4 complete, will go back and add missing & updated 2016 events
+Calendar ID: vpjc23to157rgtvgnkces05oq4@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/vpjc23to157rgtvgnkces05oq4%40group.calendar.google.com/public/basic.ics
+
+Black Lunch Table -- will double-check complete
+Calendar ID: speen8r33k1oh2e99u608g7moc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/speen8r33k1oh2e99u608g7moc%40group.calendar.google.com/public/basic.ics
+
+Black WikiHistory Month
+Calendar ID: 40pgnrv1hbagcd40ukv6c15o0c@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/40pgnrv1hbagcd40ukv6c15o0c%40group.calendar.google.com/public/basic.ics
+
+GLAM
+Calendar ID: ljmqctd112nju1fsngd1mvbelc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ljmqctd112nju1fsngd1mvbelc%40group.calendar.google.com/public/basic.ics
+
+Women in Red -- just started, in progress
+Calendar ID: qnadatlib4j65u1cn4ifo17o4k@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/qnadatlib4j65u1cn4ifo17o4k%40group.calendar.google.com/public/basic.ics
+
+
+WikimediaNYC
+Calendar ID: nnvhsl9su019vngvb58qb68u6o@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com/public/basic.ics
+
+WM NYC Planning -- Board and Event Planning so not public
+Calendar ID: ed471n0r5vkgg99dn3tau1i9vg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ed471n0r5vkgg99dn3tau1i9vg%40group.calendar.google.com/public/basic.ics
+
+
+Please forgive typos, errors and works in progress. :-)
+
+– Erika
+
+Erika Herzog
+Wikipedia User:BrillLyle
+Secretary, Wikimedia NYC",1461938043,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I posted this to the main mailing list, just sharing for 100% transparency. WM NYC had one massive calendar but the consensus was it needed to be carved down, so here they are.... :-)
+
+– –
+
+Hello --
+
+In an effort to de-clutter the Wikimedia NYC calendar -- and to support the various initiatives and enhance event calendaring within Wikimedia -- after some active discussion, Wikimedia NYC (well that would be me) has set up the following calendars. 
+
+Many events were pulled from these source:
+- https://meta.wikimedia.org/wiki/Events
+- https://www.mediawiki.org/wiki/Events
+
+Ideally a calendar solution would be open source and Wiki-friendly (see https://phabricator.wikimedia.org/T1035 Consolidate the many tech events calendars in Phabricator's calendar), but Google calendars seem to provide the most functionality right now so this is seen as an interim solution. For reference: https://phabricator.wikimedia.org/calendar/
+
+Please feel free to add events and share widely.
+
+G L O B A L
+
+Wikimedia Global Events
+Calendar ID: 7naa8gc5mjqhgjn1g2pbb4829s@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/7naa8gc5mjqhgjn1g2pbb4829s%40group.calendar.google.com/public/basic.ics
+
+Global Tech Events
+Calendar ID: 8bkj15efk0qgu4jut3oe5kd5eg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/8bkj15efk0qgu4jut3oe5kd5eg%40group.calendar.google.com/public/basic.ics
+
+--
+
+I N I T I A T I V E S
+
+AfroCROWD
+Calendar ID: djfkq9sql4h956b8vo6e35h484@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/djfkq9sql4h956b8vo6e35h484%40group.calendar.google.com/public/basic.ics
+
+Art+Feminism -- 3/4 complete, will go back and add missing & updated 2016 events
+Calendar ID: vpjc23to157rgtvgnkces05oq4@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/vpjc23to157rgtvgnkces05oq4%40group.calendar.google.com/public/basic.ics
+
+Black Lunch Table -- will double-check complete
+Calendar ID: speen8r33k1oh2e99u608g7moc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/speen8r33k1oh2e99u608g7moc%40group.calendar.google.com/public/basic.ics
+
+Black WikiHistory Month
+Calendar ID: 40pgnrv1hbagcd40ukv6c15o0c@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/40pgnrv1hbagcd40ukv6c15o0c%40group.calendar.google.com/public/basic.ics
+
+GLAM
+Calendar ID: ljmqctd112nju1fsngd1mvbelc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ljmqctd112nju1fsngd1mvbelc%40group.calendar.google.com/public/basic.ics
+
+Women in Red -- just started, in progress
+Calendar ID: qnadatlib4j65u1cn4ifo17o4k@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/qnadatlib4j65u1cn4ifo17o4k%40group.calendar.google.com/public/basic.ics
+
+
+WikimediaNYC
+Calendar ID: nnvhsl9su019vngvb58qb68u6o@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com/public/basic.ics
+
+WM NYC Planning -- Board and Event Planning so not public
+Calendar ID: ed471n0r5vkgg99dn3tau1i9vg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ed471n0r5vkgg99dn3tau1i9vg%40group.calendar.google.com/public/basic.ics
+
+
+Please forgive typos, errors and works in progress. :-)
+
+– Erika
+
+Erika Herzog
+Wikipedia User:BrillLyle
+Secretary, Wikimedia NYC",1461938024,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I posted this to the main mailing list, just sharing for 100% transparency. WM NYC had one massive calendar but the consensus was it needed to be carved down, so here they are.... :-)
+
+– –
+
+Hello --
+
+In an effort to de-clutter the Wikimedia NYC calendar -- and to support the various initiatives and enhance event calendaring within Wikimedia -- after some active discussion, Wikimedia NYC (well that would be me) has set up the following calendars. 
+
+Many events were pulled from these source:
+- https://meta.wikimedia.org/wiki/Events
+- https://www.mediawiki.org/wiki/Events
+
+Ideally a calendar solution would be open source and Wiki-friendly (see https://phabricator.wikimedia.org/T1035 Consolidate the many tech events calendars in Phabricator's calendar), but Google calendars seem to provide the most functionality right now so this is seen as an interim solution. For reference: https://phabricator.wikimedia.org/calendar/
+
+Please feel free to add events and share widely.
+
+G L O B A L
+
+Wikimedia Global Events
+Calendar ID: 7naa8gc5mjqhgjn1g2pbb4829s@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/7naa8gc5mjqhgjn1g2pbb4829s%40group.calendar.google.com/public/basic.ics
+
+Global Tech Events
+Calendar ID: 8bkj15efk0qgu4jut3oe5kd5eg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/8bkj15efk0qgu4jut3oe5kd5eg%40group.calendar.google.com/public/basic.ics
+
+--
+
+I N I T I A T I V E S
+
+AfroCROWD
+Calendar ID: djfkq9sql4h956b8vo6e35h484@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/djfkq9sql4h956b8vo6e35h484%40group.calendar.google.com/public/basic.ics
+
+Art+Feminism -- 3/4 complete, will go back and add missing & updated 2016 events
+Calendar ID: vpjc23to157rgtvgnkces05oq4@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/vpjc23to157rgtvgnkces05oq4%40group.calendar.google.com/public/basic.ics
+
+Black Lunch Table -- will double-check complete
+Calendar ID: speen8r33k1oh2e99u608g7moc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/speen8r33k1oh2e99u608g7moc%40group.calendar.google.com/public/basic.ics
+
+Black WikiHistory Month
+Calendar ID: 40pgnrv1hbagcd40ukv6c15o0c@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/40pgnrv1hbagcd40ukv6c15o0c%40group.calendar.google.com/public/basic.ics
+
+GLAM
+Calendar ID: ljmqctd112nju1fsngd1mvbelc@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ljmqctd112nju1fsngd1mvbelc%40group.calendar.google.com/public/basic.ics
+
+Women in Red -- just started, in progress
+Calendar ID: qnadatlib4j65u1cn4ifo17o4k@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/qnadatlib4j65u1cn4ifo17o4k%40group.calendar.google.com/public/basic.ics
+
+
+WikimediaNYC
+Calendar ID: nnvhsl9su019vngvb58qb68u6o@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com/public/basic.ics
+
+WM NYC Planning -- Board and Event Planning so not public
+Calendar ID: ed471n0r5vkgg99dn3tau1i9vg@group.calendar.google.com
+ics: https://calendar.google.com/calendar/ical/ed471n0r5vkgg99dn3tau1i9vg%40group.calendar.google.com/public/basic.ics
+
+
+Please forgive typos, errors and works in progress. :-)
+
+- Erika
+
+Erika Herzog
+Wikipedia User:BrillLyle
+Secretary, Wikimedia NYC",1461938003,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2214477, @BrillLyle wrote:
+> Wanted to mention that someone on one of the Wiki mailing lists recommended looking into the Calagator interface, Portland's Tech Calendar:
+
+Calagator is really interesting. Thanks for sharing.
+
+",1460999031,PHID-USER-fn7qnpccfbitivgtw2rt,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wanted to mention that someone on one of the Wiki mailing lists recommended looking into the Calagator interface, Portland's Tech Calendar:
+
+https://github.com/calagator
+
+http://calagator.org/about
+
+As far as I can tell there's no typical calendar grid format, which is non-ideal, and I'm not a code person so I don't know how Wiki-friendly this is. They do seem to be open source FWIW....
+
+http://www.bizjournals.com/portland/blog/techflash/2016/01/after-8-years-of-connecting-portland-tech.html
+
+– Erika aka BrillLyle, Secretary Wikimedia NYC",1460997542,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"1. There's also https://www.mediawiki.org/wiki/Extension:Calendar (a linkhub for the ~12 different extensions or methods of integrating calendars with MediaWiki). If further work was done on one of those, to make it usable by us, many other MediaWiki users would also benefit. There have been 12 attempts at this, for a reason!
+
+2. I've made an incomplete linkhub, for easier listing of all relevant and tangential pages, at https://meta.wikimedia.org/wiki/Calendars_events_and_meetings (I grok that this task is just about tech events/meetings, but it's a perennial issue throughout the movement.)",1460151705,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Quim started a discussion on this task on the teampractices mailing list ([""Who doesn't love calendars?""](https://lists.wikimedia.org/pipermail/teampractices/2016-April/thread.html#1078)).  This comment is partly my response on that thread
+
+The Phab calendaring tool is really good for a lot of things, and seems to hold promise as the core of an information hub about events.  The things I like about it for recurring [ArchCom RFC meetings](https://www.mediawiki.org/wiki/Architecture_meetings):
+*  Automatically weekly event instances (e.g. [Phab query: list of all RFC meetings](https://phabricator.wikimedia.org/calendar/query/XJjy54s3PEFf/))
+*  Each instance has a comment section
+*  Comments are really well integrated with Phabricator.  We can refer to RFCs by Phab number, and get automatic linking ( #ArchCom-RFC process)
+
+The upsides of using Phab made it really easy to drop useful comments about scheduling E159 //while we were having// meeting E158.  I find these features fit the #ArchCom workflow way better than the current MediaWiki-based template process on meta.
+
+As @BrillLyle says in T1035#2191149, other non-MediaWiki tools are better for different forms of outreach.  Interoperability with a broad range of tools is going to be essential.  Phab upstream is very thoughtful about synchronization with other tools (see [Upstream:T7924](https://secure.phabricator.com/T7924)). Given that our instance of Phab is something Wikimedia has operational control over, it seems like a good repository as a ""source of truth"" about events that we can build on.
+
+That's my longwinded way of saying that I'm excited about following through on this work, and more deeply integrating Phab events into our general workflows.",1460139288,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2189693, @Peachey88 wrote:
+> My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+> 
+> But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. 
+> 
+> But its more a side thing compared to the main goal of this bug (example: thinking of the tech events list on the main page of mw wiki).
+
+I agree with @Peachey88's comments. I created a semi-complete calendar of the 2016 Art+Feminism events that happened globally and one of the noticeable realities was that it was often easier for folks to add a Facebook event page than an actual on-Wikipedia event page -- especially as a first organizational step. Also, most of the larger events had both Facebook event pages as well as Eventbrite registration. Additionally, WM NYC uses Meetup.com as a registration tool (see: http://www.meetup.com/WikimediaNYC/}
+
+I think there needs to be the ability to subscribe to calendars that reflects these different realities. Not a huge fan of the whole Facebook thing, but it did seem to be the most user-friendly approach that would be easiest for event organizers.
+
+see this link for the events, as well as the links to the Google calendar (which I should probably go back and update for posterity's sake, as well as to include some of the newer events).
+https://en.wikipedia.org/wiki/Wikipedia:Meetup/ArtAndFeminism#2016_Art.2BFeminism_Wikipedia_Edit-a-thon
+
+Long winded way of saying, yes, RSS. But also consider iCal, Facebook, etc.
+
+– Erika aka BrillLyle, Secretary Wikimedia NYC",1460136002,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2189693, @Peachey88 wrote:
+> My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+> 
+> But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. 
+> 
+> But its more a side thing compared to the main goal of this bug (example: thinking of the tech events list on the main page of mw wiki).
+
+I agree with @Peachey88's comments. I created a semi-complete calendar of the 2016 Art+Feminism events that happened globally and one of the noticeable realities was that it was often easier for folks to add a Facebook event page than an actual on-Wikipedia event page -- especially as a first organizational step. Also, most of the larger events had both Facebook event pages as well as Eventbrite registration. Additionally, WM NYC uses Meetup as a registration tool.
+
+I think there needs to be the ability to subscribe to calendars that reflects these different realities. Not a huge fan of the whole Facebook thing, but it did seem to be the most user-friendly approach that would be easiest for event organizers.
+
+see this link for the events, as well as the links to the Google calendar (which I should probably go back and update for posterity's sake, as well as to include some of the newer events).
+https://en.wikipedia.org/wiki/Wikipedia:Meetup/ArtAndFeminism#2016_Art.2BFeminism_Wikipedia_Edit-a-thon
+
+Long winded way of saying, yes, RSS. But also consider iCal, Facebook, etc.
+
+– Erika aka BrillLyle, Secretary Wikimedia NYC",1460135948,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2189693, @Peachey88 wrote:
+> My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+> 
+> But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. 
+> 
+> But its more a side thing compared to the main goal of this bug (example: thinking of the tech events list on the main page of mw wiki).
+
+I agree with @Peachey88's comments. I created a semi-complete calendar of the 2016 Art+Feminism events that happened globally and one of the noticeable realities was that it was often easier for folks to add a Facebook event page than an actual on-Wikipedia event page, and most of the larger events had both Facebook event pages as well as Eventbrite registration. Additionally, WM NYC uses Meetup as a registration tool.
+
+I think there needs to be the ability to subscribe to calendars that reflects these different realities. Not a huge fan of the whole Facebook thing, but it did seem to be the most user-friendly approach that would be easiest for event organizers.
+
+see this link for the events, as well as the links to the Google calendar (which I should probably go back and update for posterity's sake, as well as to include some of the newer events).
+https://en.wikipedia.org/wiki/Wikipedia:Meetup/ArtAndFeminism#2016_Art.2BFeminism_Wikipedia_Edit-a-thon
+
+Long winded way of saying, yes, RSS. But also consider iCal, Facebook, etc.
+
+– Erika aka BrillLyle, Secretary Wikimedia NYC",1460135903,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+
+But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. 
+
+But its more a side thing compared to the main goal of this bug (example: thinking of the tech events list on the main page of mw wiki).",1460116755,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"My suggestion of RSS was more of just thinking the quickest way to get it into MediaWiki wikis on the WMF cluster.
+
+But if we want to put time into a extension that can pull a calendar widget (etc) into a page would be fantastic and would be more versatile. ",1460116683,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"The fact is that RSS support is not in Phabricator plans, neither (I believe) RSS is a technology that comes to mind when handling calendar data. Yes, if that bridge would exist maybe we could use it but since it doesn't... should we invest on it?
+
+What is the difference of embedding a calendar in a wiki page and offering that calendar with a link? At the end the most important feature is not viewing a list of events but being able to subscribe, RSVP, and add it to your own calendar application.",1460110737,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2026019, @Peachey88 wrote:
+> RSS output would probably the most useful starter for us, For integration onto the wikis via E:RSS
+
+RSS support doesn't seem to be on the official upstream roadmap https://secure.phabricator.com/T1928 so would need to be built by us or someone else (https://secure.phabricator.com/w/community_resources/), or to be funded (https://secure.phabricator.com/w/prioritization/).",1460059598,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"We have three problems that need to be resolved, which are related but perhaps may be fixed separately, even at different points in time:
+
+* **Introducing calendar data**. Now we are doing this in 1001 places. Ideally it would be just one. The assumption of this task is that the one place would be Phabricator's calendar ([[ https://secure.phabricator.com/T7924 | today a prototype ]]), but other candidates should be considered.
+* **Pulling calendar data in other supports, mainly wiki pages**. While we could start linking from wiki pages to Phabricator calendar queries, the desired scenario would be a way for editors to embed calendars based on queries in wiki pages. This probably implies a Calendar API to query data ([[ https://secure.phabricator.com/T7944 | which is missing ]]) and a MediaWiki extension allowing to embed those queried calendars in wiki pages (which we don't have). Maybe this is just too much, and at least the tech-inclined Wikimedians would be fine clicking a Phabricator link.
+* **Integrating calendar data with other systems (mainly Google Calendar)**. ""[[ https://secure.phabricator.com/T7929 | Future work ]]"" upstream, no plans today.
+
+As we can see, deciding on Phabricator Calendar as the one place to introduce data would not provide a quick path to use that data out of Phabricator. However, what would be the alternatives? Other than defaulting to Google Calendar (which I think would be wrong as a matter of Wikimedia principles), I don't see a shortcut but others may have better ideas.",1460051551,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"We have three problems that need to be resolved, which are related but perhaps may be fixed separately, even at different points in time:
+
+* **Introducing calendar data**. Now we are doing this in 1001 places. Ideal it would be just one. The assumption of this task is that the one place would be Phabricator's calendar ([[ https://secure.phabricator.com/T7924 | today a prototype ]]), but other candidates should be considered.
+* **Pulling calendar data in other supports, mainly wiki pages**. While we could start linking from wiki pages to Phabricator calendar queries, the desired scenario would be a way for editors to embed calendars based on queries in wiki pages. This probably implies a Calendar API to query data ([[ https://secure.phabricator.com/T7944 | which is missing ]]) and a MediaWiki extension allowing to embed those queried calendars in wiki pages (which we don't have). Maybe this is just too much, and at least the tech-inclined Wikimedians would be fine clicking a Phabricator link.
+* **Integrating calendar data with other systems (mainly Google Calendar)**. ""[[ https://secure.phabricator.com/T7929 | Future work ]]"" upstream, no plans today.
+
+As we can see, deciding on Phabricator Calendar as the one place to introduce data would not provide a quick path to use that data out of Phabricator. However, what would be the alternatives? Other than defaulting to Google Calendar (which I think would be wrong as a matter of Wikimedia principles), I don't see a shortcut but others may have better ideas.",1459938293,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#19336, @Quiddity wrote:
+> * https://www.mediawiki.org/wiki/Meetings
+> * https://www.mediawiki.org/wiki/Architecture_meetings
+> * https://www.mediawiki.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Meetup
+
+* https://meta.wikimedia.org/wiki/IRC_office_hours and related tag #IRC-Meetings
+* https://meta.wikimedia.org/wiki/Community_Engagement/Calendar
+* https://www.mediawiki.org/wiki/Category:MediaWiki_developer_meetings",1459587043,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#19336, @Quiddity wrote:
+> * https://www.mediawiki.org/wiki/Meetings
+> * https://www.mediawiki.org/wiki/Architecture_meetings
+> * https://www.mediawiki.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Meetup
+
+* https://meta.wikimedia.org/wiki/IRC_office_hours and related tag #IRC-Meetings
+* https://meta.wikimedia.org/wiki/Community_Engagement/Calendar",1457464258,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#2026016, @RobLa-WMF wrote:
+> Of course, [Upstream:T7929 (Integrate Calendar with external systems)](https://secure.phabricator.com/T7929) may be a blocker for us seriously moving over to this, but it adds enough value for repeating meetings and Phab integration that it's worth it for me (ymmv)
+
+RSS output would probably the most useful starter for us, For integration onto the wikis via E:RSS
+",1455406524,PHID-USER-hwuumsjqciw7ji5qhpc7,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"There's a new #IRC-Meetings tag, per T114322.  This tag is for all [Phabricator events](https://phabricator.wikimedia.org/calendar/query/upcoming/) that have an anticipated IRC component (e.g. office hours on #wikimedia-office).  A couple of queries:
+
+* **[All upcoming IRC meetings](https://phabricator.wikimedia.org/calendar/query/wiuSD6vCKuhA/)**
+* [All IRC meetings](https://phabricator.wikimedia.org/calendar/query/q0gEvg_5.lM_/)
+
+As of this writing, only #ArchCom-RFC meetings are in there, but hopefully that will expand as education grows.
+
+Of course, [Upstream:T7929 (Integrate Calendar with external systems)](https://secure.phabricator.com/T7929) may be a blocker for us seriously moving over to this, but it adds enough value for repeating meetings and Phab integration that it's worth it for me (ymmv)",1455406015,PHID-USER-edlps6xg553cjlnvd4ao,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Qgil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+-- Meetup calendar actually seems the most sharable and used within Wikipedia
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+**Wikimedia Phabricator calendar**
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it has more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+Erika, User:BrillLyle",1453746279,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Qgil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+**Wikimedia Phabricator calendar**
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it is more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+Erika, User:BrillLyle",1453746018,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+**Wikimedia Phabricator calendar**
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it is more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+Erika, User:BrillLyle",1453745970,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+**Wikimedia Phabricator calendar**
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it is more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+- Erika
+User:BrillLyle",1453745946,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- **Administrative burden** on one or more people can be heavy
+- **Duplication of effort **
+- **Usability past 2 months** Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- **Embedability** Google calendars can't be embedded on Wikipedia
+- **Low sharability / visibility** -- Google calendars are not super easy to add, make public, share
+
+re: Wikimedia Phabricator existing calendar
+- **Too many events:** I think if there's too many events it will become unusable.
+- **Color coding:** Also the calendar needs to be color coded so it is more usability
+- **Administrative burden:** It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- **Embeddability?** Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+- Erika
+User:BrillLyle",1453745922,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- Administrative burden on one or more people can be heavy
+- Duplication of effort 
+- Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- Google calendars can't be embedded on Wikipedia
+- Low sharability / visibility -- Google calendars are not super easy to add
+
+re: Wikimedia Phabricator existing calendar
+- Too many events: I think if there's too many events it will become unusable.
+- Color coding: Also the calendar needs to be color coded so it is more usability
+- Administrative burden: It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+- Embeddability? Can the Wikimedia Phabricator calendar be updated? That would be ideal....
+
+- Erika
+User:BrillLyle",1453745830,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"to: @Ogil
+cc: @Aklapper
+
+Calendars are a big issue for Meetups, especially for active chapters
+https://en.wikipedia.org/wiki/Wikipedia:Meetup
+
+re: Active chapters, to understand scope, see: **Event Archive:**  https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Event_archive
+
+For Wikimedia NYC (the local New York City chapter), as Secretary, I created the following Google calendars:
+
+  - **WikimediaNYC** - public, all events as well as some larger events like hackathons and national conferences: https://calendar.google.com/calendar/embed?src=nnvhsl9su019vngvb58qb68u6o%40group.calendar.google.com&ctz=America/New_York
+
+  - **WM NYC Planning** - visible only to the WM NYC Board, used for planning and adding placeholder events to help schedule and de-cluster events
+
+For EVERY event, the following gets updated:
+- **WikimediaNYC Google calendar(s)** (see above)
+- **Header box** (cream box on top of most pages {{Wikipedia:Meetup/NYC/Main|short=1}} ): https://en.wikipedia.org/wiki/Wikipedia:Meetup/NYC/Header
+- **Meetup box** (pink box on right of most meetup pages {{meetup}})
+- **Event Archive** on our namespace (see above)
+
+**Issues:**
+- Administrative burden on one or more people can be heavy
+- Duplication of effort 
+- Meetup calendar is not easy to update for forward events beyond 2 months (those that are visible in the pink Meetup box)
+- Google calendars can't be embedded on Wikipedia
+- Low sharability / visibility -- Google calendars are not super easy to add
+
+re: Wikimedia Phabricator existing calendar
+- Too many events: I think if there's too many events it will become unusable.
+- Color coding: Also the calendar needs to be color coded so it is more usability
+- Administrative burden: It doesn't seem fair to have only one person in charge of maintaining the calendar. Not sure if Community-Liaison is a person?
+
+- Erika
+User:BrillLyle",1453745772,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"I wonder whether #Community-Liaisons have any opinion about this proposal, considering that they Help organizing many of these activities (i.e. office hours).",1453726138,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#1960445, @Aklapper wrote:
+>>>! In T1035#1958506, @BrillLyle wrote:
+>> Is this still an active project?
+> 
+> @BrillLyle: Yes, people can [[ https://phabricator.wikimedia.org/calendar/event/create/ | create calendar events ]] in Wikimedia Phabricator. :)
+
+@Aklapper: Thanks for letting me know. Public calendars are a huge issue for Meetups -- not sure if it would be helpful to add such specific to locale events to this calendar but the interface looks great. Thanks!",1453666655,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,">>! In T1035#1958506, @BrillLyle wrote:
+> Is this still an active project?
+
+@BrillLyle: Yes, people can [[ https://phabricator.wikimedia.org/calendar/event/create/ | create calendar events ]] in Wikimedia Phabricator. :)",1453659554,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Is this still an active project? I stumbled upon this calendar when combing for national Wikimedia events. If this is active and is being used for local chapter meetup events, I would love to add the Wikimedia NYC events to this calendar so we can use this calendar in addition to the Google Calendar we are currently keeping. (Calendar ID: nnvhsl9su019vngvb58qb68u6o@group.calendar.google.com) -- Please let me know -- Erika aka BrillLyle",1453510534,PHID-USER-5orqjaw2whyidcs3hejo,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,fwiw #archcom is using Phabricator' calendar to organize their weekly meetings i.e. {E61} ,1441735624,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Email preferences have entries for calendar events that you could set to Ignore if you are not interested.
+
+Watching https://www.mediawiki.org/wiki/Project:Calendar and/or other calendar pages is not superior to subscribing only to the projects for the types of events you are interested about (i.e. Tech Talks yes but not Wikimedia Tech San Francisco Meetup) or defining whatever specific queries you are interested about.
+
+There is no iCal support in Phabricator (https://secure.phabricator.com/T7929). iCal for Wikimedia office hours is done via http://h2vx.com/, which doesn't seem to be able to digest our Phabricator URLs. Now idea when will upstream work on this, and how complex it is.
+
+But... an important factor is how simple it is to create events and announce them to those who probably care. Doing this on-wiki is a pain, and ultimately not very effective. I know well because I have done it multiple times. And another evidence is that there is only a few people creating events, and probably only a few people watching the relevant pages. An email to wikitech-l and a couple of mailing lists more keeps being our main way to reach our potential audience.
+
+When creating events is a pain, the rest of the process is broken. This is where Phabricator is clearly superior in the context of the Wikimedia tech community, because most potential users are already here, with the possibility to subscribe to the projects they care about.",1440672160,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Personally I don't see a benefit in this proposal. https://phabricator.wikimedia.org/settings/panel/emailpreferences/ doesn't have any useful notification setting for ""calendar"" things and I'm certainly not going to watch a project just for the sake of getting notifications of events which might be attached to it.
+
+MediaWiki transclusion, watchlist and enotifwatchlist are vastly superior features and integration with iCal applications is not particularly difficult: as far as I know, it's provided successfully for https://meta.wikimedia.org/wiki/IRC_office_hours (see there).",1440669277,PHID-USER-v7bwpq3rs3zdxegibdbh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Thanks for this list of pages, @quiddity. I have announced this proposal at
+
+> * https://www.mediawiki.org/wiki/Meetings
+> * https://www.mediawiki.org/wiki/Architecture_meetings
+> * https://www.mediawiki.org/wiki/Events
+> * https://meta.wikimedia.org/wiki/Events
+> * https://www.mediawiki.org/wiki/Bug_management/Triage
+> * https://meta.wikimedia.org/wiki/Meetup
+
+Not at this one because it felt too off-topic:
+> * https://en.wikipedia.org/wiki/Wikipedia:Meetup",1440668646,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,Proposal completely revamped. Feedback welcome.,1440668113,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Furthermore, [[ https://www.mediawiki.org/wiki/Hackathon | mw:Hackathon]] redirects to [[ https://www.mediawiki.org/wiki/Events | mw:Events]] but [[ https://www.mediawiki.org/wiki/Hackathons | mw:Hackathons]] does not and that plural page includes stuff that should be merged as part of T85598.",1422314971,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Wasn't aware of this task and Quiddity's great list above (thanks!) when I wrote the following lines yesterday night in an email:
+
+ Trying to get an overview as an outsider: https://www.mediawiki.org/wiki/Events seems to be about physical events that last longer than two hours and https://www.mediawiki.org/wiki/Meetings seems to be even deader though some recent tech talks are listed there too. Hmm. There's also office hours on https://meta.wikimedia.org/wiki/IRC_office_hours
+
+ So currently there seems to be a division by either medium or format of activity, expressed via different pages. I can't easily get an overview of what's cooking or might be somehow ""joinable"" for me.
+
+If I had too much time I might try to merge all into one table on one page, and have 
+* 'medium' (IRC Office Hour? Physical Happening? Video hangout?) and 
+* 'content/format' (TechTalk presentation? WMFMetrics presentation? ECT TeamMeeting? Techy Hackathon? Non-techy Edithon? Booth/stand at some conference? Q&A on Phabricator? Other?) columns/pre-defined classifications that allow filtering (does MediaWiki support that?).",1418815978,PHID-USER-hgn5uw2jafgjgfvxibhh,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Note that there is an additional risk (positive or not, I still don't know) of having yet another calendar: {T466}",1415260538,PHID-USER-lluzkul4z7us4sxkayss,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+Consolidate the many tech events calendars in Phabricator's calendar,"Agreed. I'm often confused as to why ""X"" isn't mentioned, and then I realize it's at the //other// page...  ([[https://meta.wikimedia.org/wiki/Mergism|Mergism]] is often good, when a few short pages are involved. :)
+
+Here are some more ""scheduled/re-occurring"" meetings, some or all of which should be considered for merging. (Or for upgrading, once there's a better system that we can recommend.)
+* https://www.mediawiki.org/wiki/Meetings
+* https://www.mediawiki.org/wiki/Architecture_meetings
+* https://www.mediawiki.org/wiki/Events
+* https://meta.wikimedia.org/wiki/Events
+* https://www.mediawiki.org/wiki/Bug_management/Triage
+* https://meta.wikimedia.org/wiki/Meetup
+* https://en.wikipedia.org/wiki/Wikipedia:Meetup
+",1415234931,PHID-USER-hphmqcx66p6d6gvmjzp7,False,PHID-TASK-jwtr42v56pyz6l6jnzpx,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"actions such as adding projects or tags, adding cc's or assigning owner, changing security should be more easily added, removed or modified. ",1414186408,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_description,resolved
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"This is now implemented for status, priority, assignee, points, project tags subscribers and even workboard column.
+
+The only fields that can't be edited in-line with the comment form are title, description and advanced things like visibility policy.",1463618910,PHID-USER-fn7qnpccfbitivgtw2rt,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"Tangentially, if you click ""2 others"" on this task, you get an in-browser pop-up window and even that window has no write capability. :-(
+
+>>! In T870#933937, @Jaredzimmerman-WMF wrote:
+> On your flickr photo pages, and on your facebook ""about"" section almost all fields are editable this way, If I remember correctly this is how Jira tasks were as well. I feel like some aspects of bugzilla were like this as well, but not that its locked I can't point to specific ones. 
+
+Yep, JIRA has this functionality (using a standard pencil icon on hover) and Bugzilla had similar functionality.
+
+Broadly the ""Add Comment"" box is probably mislabeled. But this task appropriately focuses on making the fields at the top of every task easier to modify. I think this is medium-ish priority, but definitely worth pursuing.",1420007762,PHID-USER-hyfm4swq76s4j642w46x,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"On your flickr photo pages, and on your facebook ""about"" section almost all fields are editable this way, If I remember correctly this is how Jira tasks were as well. I feel like some aspects of bugzilla were like this as well, but not that its locked I can't point to specific ones. ",1418937041,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"As I understand this request, users could click on the title of any field in a task page, and then such field would become editable, seamlessly.
+
+Not like VisualEditor ""all page is yours now"", field by field. I have seen this behavior before somewhere, I just don't remember where. Giving real examples might help this task moving forward upstream.",1418914734,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"@chasemp still 3, just a different 3",1418856171,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,you can do all 3 in the action drop down with 2-ish?,1418854492,PHID-USER-3neel27i7dyu62jbbx2l,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"@Aklapper I'm more referring to status, assigned, cc, currently these are all 3 actions, when they could just as easily be 1 or two ",1418854426,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"Might have been a fundamental design decision of upstream (though I cannot find any past discussions) to ""hide"" some not too common actions under a separate ""edit"" page. 
+It also makes the task view less cluttered (""Visible To"", ""Editable By"", ""Security"" checkbox not exposed, in my case at least).",1418840397,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+attributes in a task should be modifiable in-line rather than having to go to an edit mode,"Nice feature, but I have no idea about the complexity.",1418825004,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-bm7u2vdbvfhrl7phrzgv,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Allow shortcut keys for text formatting and action in description fields like CMD+B, CMD+K, CMD+I, etc. ",1414018531,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_description,declined
+Shortcut keys for description fields text formatting are needed. ,Declining as per T816#5224212 and as several other ways to achieve similar functionality were provided.,1562205607,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,Another possibility would be something like https://addons.mozilla.org/en-US/firefox/addon/shortkeys/,1559769252,PHID-USER-fn7qnpccfbitivgtw2rt,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"This looks like a couple of different requests:
+
+  - Add text formatting shortcuts like {key command B} (or whatever) to make selected text bold when editing text in a Remarkup text area.
+  - Add navigation shortcuts for a lot of other stuff.
+
+I don't currently plan to add either feature to the upstream.
+
+In both cases, we've seen relatively little interest in these features and they're somewhat complex to implement, test, and maintain. One issue in all cases here is conflicts with existing browser and OS shortcuts: for example, {key command B}, {key command K}, {key Control K}, {key Command U} and {key Command I} all do something in at least one of Safari, Firefox, or Chrome on macOS.
+
+For global navigation (like ""View Notifications""), you can probably bookmark the URL and use browser shortcut features, or use OS-level shortcut features with `open <url>`.
+
+For quicker access to on-page actions, you might be able to use accessibility features of your OS. For example, with VoiceOver you can {key Control Option I} to pull up a list of all links on a page, then type ""sub"" to select the ""subscribe"" link. This may or may not be a great fit, but is a general-purpose solution to providing keyboard access to the page if you need accessibility affordances because of poor vision, limited dexterity, RSI injury, etc.
+
+You can also use ""Bulk Edit"" to bulk-edit multiple tasks in a single action, or the API to automate a larger number of more complex edits.",1559233887,PHID-USER-ic77k5i4bubodmfnpbui,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,@aklapper: [[ https://en.wikipedia.org/wiki/Repetitive_strain_injury | Repetitive strain injury ]],1505493435,PHID-USER-fn7qnpccfbitivgtw2rt,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"What is ""RSI""?",1505490799,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Task specific shortcuts:
+
+* Edit task
+* Subscribe / unsubscribe
+* Assign to self
+* Remove assignment
+* Close task
+
+Navigation shortcuts:
+
+* Go to notifications
+* Go to RSI help page",1505473120,PHID-USER-mye6umixnhfo7lhpgzmj,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Task specific shortcuts:
+
+* Edit task
+* Subscribe / unsubscribe
+* Assign to self
+* Remove assignment
+* Close task
+
+Navigation shortcuts:
+
+* Go to notifications",1505473005,PHID-USER-mye6umixnhfo7lhpgzmj,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,">>! In T816#3296416, @Aklapper wrote:
+> See wontfix'ed https://secure.phabricator.com/T1931#144486 asking for use cases.
+
+You're probably the most active phab user here, so maybe you could add a list of use-cases? (If you're generally a user of keyboard shortcuts, of course!) - I do my triage via email, so cannot really help.",1496450839,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,See wontfix'ed https://secure.phabricator.com/T1931#144486 asking for use cases.,1495916660,PHID-USER-hgn5uw2jafgjgfvxibhh,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,I'd love some navigational shortcuts. Go to notifications is an obvious one (ctrl + n).,1461864852,PHID-USER-mye6umixnhfo7lhpgzmj,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"""Shortcut keys for description fields"" is too vague. I think we will have a better chance if specific shortcuts are requested, like in https://secure.phabricator.com/T704",1420809229,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"2 Closed Phab bugs:
+* Suggestion of going towards Github's standard of shortcuts, for Differential at least. (j/k for prev/next), done in https://secure.phabricator.com/T184
+* Feature request for ctrl-Enter to submit a comment, https://secure.phabricator.com/T704
+But nothing about bold/italic/link/code/etc.
+
+----
+Here are Mediawiki's shortcut standards: 
+* Mediawiki (navigational): https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts#Modifier_keys
+* VE (text formatting): https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts
+
+Here are Github's and Gerrit's:
+* https://help.github.com/articles/using-keyboard-shortcuts/
+* https://git.eclipse.org/r/Documentation/images/intro-quick-hot-key-help.jpg",1414564414,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"2 Closed Phab bugs:
+* Suggestion of going towards Github's standard of shortcuts, for Differential at least. (j/k for prev/next), done in https://secure.phabricator.com/T184
+* Feature request for ctrl-Enter to submit a comment, https://secure.phabricator.com/T704
+But nothing about bold/italic/link/code/etc.
+
+----
+Here are Mediawiki's shortcut standards: 
+* Mediawiki (navigational): https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+* VE (text formatting): https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts
+
+Here are Github's and Gerrit's:
+* https://help.github.com/articles/using-keyboard-shortcuts/
+* https://git.eclipse.org/r/Documentation/images/intro-quick-hot-key-help.jpg",1414564371,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"2 Closed Phab bugs:
+* Suggestion of going towards Github's standard of shortcuts, for Differential at least. (j/k for prev/next), done in https://secure.phabricator.com/T184
+* Feature request for ctrl-Enter to submit a comment, https://secure.phabricator.com/T704
+But nothing about bold/italic/link/code/etc.
+
+----
+Here are Mediawiki's shortcut standards: 
+* Mediawiki (navigational): https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts
+* VE (text formatting): https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts
+
+Here's Github's and Gerrit's:
+* https://help.github.com/articles/using-keyboard-shortcuts/
+* https://git.eclipse.org/r/Documentation/images/intro-quick-hot-key-help.jpg",1414564354,PHID-USER-hphmqcx66p6d6gvmjzp7,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Phabricator saves the text you are typing with some persistence (which is very useful if your connection drops, your browser crashes, etc). My bet is that you had typed ""test"" at some point while creating a task, and then you created this task here without any description (tsk tsk)  :) , and you didn't notice that your ""test"" was still there.",1414021678,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"I didn't type test… I see it there, but I didn't add it. Is there default description that is being added?",1414020873,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Sorry, for some reason reading ""test"" as sole description made me think this was a test.  :)",1414020799,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Wasn't an experiment, where do we log bugs against phabricator? bugzilla?",1414019041,PHID-USER-z3kqk2bjnqneldcznht6,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Shortcut keys for description fields text formatting are needed. ,"Hi, this is a production instance. Please file only legitimate tasks.
+
+We have https://phab-01.wmflabs.org/ for experimenting and learning.",1414018835,PHID-USER-lluzkul4z7us4sxkayss,True,PHID-TASK-qku5ds4p6huc4ehidnf2,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,The [[https://secure.phabricator.com/book/phabricator/article/remarkup/|ReMarkup]] system is not wikitext and not Markdown. Sad.,1397576333,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_description,declined
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,//importing issue status//,1410485105,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-09-04 11:06:07 (UTC)`
+
+I do not see a reason to switch off markup (and I don't think it's possible). I don't see much ""confusion"" because **there is a preview of your comment**. Plus functionality like @aklapper is nothing I want to switch off.",1410485105,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Svetlana** wrote on `2014-09-03 23:46:32 (UTC)`
+
+Can we force it to go plaintext? That could be nice, to avoid confusion of people who see an 'italic' button which adds //.",1410485105,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-09-03 14:23:49 (UTC)`
+
+>>! In T100#48, @Nemo_bis wrote:
+> Then just disable the phabricator-specific markup, no? Is there any reason we need a markup?
+
+Same reasons phab-specific markup exists as any other markup: It's convenient.",1410485104,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Nemo_bis** wrote on `2014-09-03 14:15:50 (UTC)`
+
+> In fact, it takes less work to copy a Wikimedia URL from your browser and paste it here than typing the mw:etc custom strings manually.
+
+Then just disable the phabricator-specific markup, no? Is there any reason we need a markup?",1410485104,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**qgil** wrote on `2014-09-01 07:26:21 (UTC)`
+
+In fact, it takes less work to copy a Wikimedia URL from your browser and paste it here than typing the mw:etc custom strings manually.
+
+After months of daily Phabricator use and after reading this discussion again, I think we can Decline this request.",1410485104,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**scfc** wrote on `2014-08-31 19:26:56 (UTC)`
+
+FWIW, as @aklapper said, the preview function (dearly missed in Bugzilla) makes this a not-so-big problem.
+
+Personally, I strongly favour full-fledged URLs over [[wikilinks]] because:
+
+  # They prevent users from messing with ""evidence"" relevant to a bug; if they just have to copy & paste something, the chances are much higher that what they report is what they actually experienced.
+  # They work //everywhere//, i. e. if you read a bug report in your mailbox, you don't have to set up a local filter and keep that in sync with the tracker, but you can just click on a link.",1410485103,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-08-26 09:59:47 (UTC)`
+
+For comparison, Bugzilla's [[https://bugzilla.wikimedia.org/buglist.cgi?bug_id=29506,41851,51720 | half-working]] ability to turn [[:mw:Extension:Flow]] into a link is a [[ https://git.wikimedia.org/blob/wikimedia%2Fbugzilla%2Fmodifications.git/HEAD/extensions%2FWikimedia%2FExtension.pm#L31 | custom patch on our side]]. Whether something similar is doable and feasible in Phabricator remains to be investigated by anybody willing to dive into the codebase (and upstream is very responsive in helping).
+
+If you are strongly interested in performance differences I recommend to contact upstream development for more information.",1410485103,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Svetlana** wrote on `2014-08-26 09:14:29 (UTC)`
+
+There is the routine work of having to click through or type through many times to link to common things like [[:mw:Extension:Flow]]. There is another task of having to ""learn a new markup"". The latter appears to be discussed extensively in this task and a visual editor could indeed help (or we could kick and scream a little and have Parsoid service break into this site).
+
+The former (routinely linking to mw and other sites) needs more attention. Implementing this would indeed be a repetition of the parser that Wiki uses which could probably be inefficient - some more insight is needed here; I wouldn't like to //assume// anything. If it is slower then //how// slower is it? Such feature would probably not be needed for other companies using Phabricator: they typically don't have a wiki farm, and may as-well do everything right in Phabricator itself. Phabricator is free software. Surely it's within its philosophy to be extensible and script-able to suit such specific needs?
+
+I'd suggest to split this task and move over some interwiki-related comments over to a new task.",1410485102,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-06-16 11:07:45 (UTC)`
+
+>>! In T100#40, @Nemo_bis wrote:
+> Ok, but at least not double brackets for external links, as Guillaume says in T100#14... And yes, I think such a decision must be before day 1.
+
+The comment preview would tell that markup parsing expectations from MediaWiki do not work out in Phabricator. 
+I expect a frustration level similar to Bugzilla and our custom regexes over there. Neither better nor worse. Which makes this not block day 1 for me currently.
+ --~~~~ (Y signature no work on tis Phabicreator wiki?!?!)",1410485102,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Nemo_bis** wrote on `2014-06-15 10:15:27 (UTC)`
+
+>>! In T100#39, @aklapper wrote:
+> I was missing a rationale for ""we'd really like to switch it to something else if possible"" in the task summary but I guess it translates to ""I'm used to wikitext markup and don't see good enough reasons to learn something else"".
+
+Given it was set by James, it probably rather means ""what's wrong with HTML after all"". :P
+
+Performance, really? Ok, but at least not double brackets for external links, as Guillaume says in T100#14... And yes, I think such a decision must be before day 1.",1410485102,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-05-23 03:40:42 (UTC)`
+
+I was missing a rationale for ""we'd really like to switch it to something else if possible"" in the task summary but I guess it translates to ""I'm used to wikitext markup and don't see good enough reasons to learn something else"".
+
+In any case I don't think that this should //block// Day 1 of Phabricator in production so I've changed the project of this task and added Maintenance (after day 1) instead.
+
+Reasons:
+You can actually see in the preview how your text will look like (compared to Bugzilla commenting) so you can realize beforehand that wikitext parsing might not work as expected. In the worst case people will realize that they need to paste full URLs - slightly more inconvenient, but not a dealbreaker IMHO. Furthermore, see RobLa's comment 33 above.
+
+> We definitely don't need to patch the parser to set links between bugs, with Gerrit, RT, or with Wikimedia wiki pages. The existing Bugzilla links can be converted during the migration.
+
+Good point; Added a comment to T39.",1410485101,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**qgil** wrote on `2014-05-15 18:13:55 (UTC)`
+
+We shouldn't maintain a local patch just because. If there is a very good reason to add some functionality, then it could be proposed upstream. 
+
+We definitely don't need to patch the parser to set links between bugs, with Gerrit, RT, or with Wikimedia wiki pages. The existing Bugzilla links can be converted during the migration.",1410485101,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**robla** wrote on `2014-05-14 19:10:18 (UTC)`
+
+The Phabricator folks explain their rationale for yet another markup language in https://secure.phabricator.com/T2849
+
+In a nutshell, they've packed a bunch of functionality into a syntax that is very efficient to parse.  One of the things that makes Phabricator a pleasure to use is the performance, so I would be hesitant to implement a (likely) less efficient, feature poor parser in the name of making something that we hope is vaguely headspace compatible with Mediawiki markup.  If we're concerned about usability, I would rather we push the Phabricator folks to implement visual editing like we ourselves are doing.",1410485101,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**jdforrester** wrote on `2014-05-10 20:35:20 (UTC)`
+
+◀ Merged tasks: T165.",1410485100,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Krenair** wrote on `2014-04-20 16:06:21 (UTC)`
+
+@Rillke If we implemented it again the default wiki obviously wouldn't be enwiki (probably mediawiki.org or maybe wikitech), so it wouldn't change much for them.",1410485100,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**qgil** wrote on `2014-04-20 15:24:50 (UTC)`
+
+In general, I would be reluctant to any local patches, except when they provide functionality that we would not get with the stock software.
+
+In any case, I don't think lack of wikitext parsing would stop us from migrating. Setting priority as Wishlist for now. My opinion is Wontfix.
+
+No guideline would be needed. Plain MediaWiki and VisualEditor also have a chain icon to define external links. When users click this icon, the rest is also obvious.",1410485099,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Rillke** wrote on `2014-04-20 11:57:05 (UTC)`
+
+> Can we please not implement wikitext again?
+
+@Krenair Yeah but then we should have some guide how to achieve the same, although phabricator has some nice toolbars and instant preview. I will not miss this feature very much because I mostly linked to `:commons:` and `:de:` (thus not a lot shorter or faster) but the `:en:`-guys may complain.",1410485099,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Krenair** wrote on `2014-04-20 11:40:29 (UTC)`
+
+Can we please not implement wikitext again?",1410485099,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**gpaumier** wrote on `2014-04-18 10:47:45 (UTC)`
+
+@aklapper The problem is that Remarkup uses the same syntax for external links as well, e.g.:
+  [[https://fr.wikipedia.org | Wikipédia]]
+
+There is an alternate Markdown-like syntax for external links:
+  [Wikipédia](https://fr.wikipedia.org)
+but the one with double brackets is the one inserted by default by the toolbar. 
+
+I don't know how customizable / fixable this is, but I just wanted to raise the issue for completeness :)",1410485098,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-04-18 10:31:46 (UTC)`
+
+...and that page says:
+
+[[wiki page]]             # Link to Phriction
+[[wiki page | name]]      # Named link to Phriction
+
+so with a small (?) code change we could hopefully link to mediawiki.org or whatever instead. Maybe.",1410485098,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-04-18 10:15:09 (UTC)`
+
+For the records, https://secure.phabricator.com/book/phabricator/article/remarkup/ covers the auto-linking stuff.",1410485098,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-04-17 12:45:09 (UTC)`
+
+Also see T88",1410485097,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**aklapper** wrote on `2014-04-17 12:40:57 (UTC)`
+
+Haven't checked Phab's code, but as it autolinks numbers followed by a certain letter I'd assume somebody could patch the code and reuse the regexes we have in https://git.wikimedia.org/blob/wikimedia%2Fbugzilla%2Fmodifications.git/HEAD/extensions%2FWikimedia%2FExtension.pm",1410485097,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
+Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible,"**Rillke** wrote on `2014-04-15 15:39:46 (UTC)`
+
+[[ :de:Test | Testcase ]]",1410485097,PHID-USER-nyhmztvvw4luz5mlcuvg,False,PHID-TASK-l2wcdsvwatewpompucdp,task_subcomment,NA
diff --git a/src/helper_scripts/cleaning_scripts/cleaning_phabricator.ipynb b/src/helper_scripts/cleaning_scripts/cleaning_phabricator.ipynb
index 935efba..4b0dba3 100644
--- a/src/helper_scripts/cleaning_scripts/cleaning_phabricator.ipynb
+++ b/src/helper_scripts/cleaning_scripts/cleaning_phabricator.ipynb
@@ -16,7 +16,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "fp =\"/data/users/mgaughan/mw-repo-lifecycles/phab_data/visualeditor/2012_1_1_to_2014_12_31.json\"\n",
+    "fp =\"/data/users/mgaughan/mw-repo-lifecycles/case1/visualeditor/2012_1_1_to_2014_12_31.json\"\n",
     "with open(fp, 'r') as file:\n",
     "        data = json.load(file)"
    ]
@@ -43,4602 +43,4602 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 6,
+   "execution_count": 4,
    "metadata": {},
    "outputs": [
     {
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "PHID-TASK-vrk66ztqr5wv6qiwliyc\n",
-      "PHID-TASK-ufoo62yyz25ibqfvz7ez\n",
-      "PHID-TASK-j7cnykjnzlc5nu27zqtt\n",
-      "PHID-TASK-hlczvkjyex42kxtfvcdr\n",
-      "PHID-TASK-6stmkadongdngovinrsy\n",
-      "PHID-TASK-2oau4k2rwhb4lnhnwgl5\n",
-      "PHID-TASK-nohpzqcpzjmuxbicpotc\n",
-      "PHID-TASK-k34jgliglfher6oyvsj3\n",
-      "PHID-TASK-s4icej2snebqglex3pcn\n",
-      "PHID-TASK-bfjwz5ljcpfpztnowj4p\n",
-      "PHID-TASK-dnykg7zlhhhsxuhitddq\n",
-      "PHID-TASK-kghawjstykvx6zxoqfju\n",
-      "PHID-TASK-h5qveiikflwo46ebtb77\n",
-      "PHID-TASK-fjl7kogsfw35mh64piys\n",
-      "PHID-TASK-htn6d4t4wffqwtpyga74\n",
-      "PHID-TASK-pcjfp7itxwp6ka5s4r5q\n",
-      "PHID-TASK-rh6lcdzaiwcz3kmrclju\n",
-      "PHID-TASK-r4bsfhr5vzw7cgtwuw7z\n",
-      "PHID-TASK-3t7mpi32hxkzdcilczeh\n",
-      "PHID-TASK-b56uk34hrwocyqm77dht\n",
-      "PHID-TASK-ndseob64bszecd4p2h7o\n",
-      "PHID-TASK-h2p2ez3bfy7n73tt2adc\n",
-      "PHID-TASK-sbk42chhxkin6ieg2dfm\n",
-      "PHID-TASK-6bxeocfqy65faxfgqvze\n",
-      "PHID-TASK-633guswlzr7odpcbch5o\n",
-      "PHID-TASK-qnqc42uqv5b4sr7b2rpz\n",
-      "PHID-TASK-zy4ezl7vztln3ygf33xm\n",
-      "PHID-TASK-fwehkkee2lr5fjpovjuq\n",
-      "PHID-TASK-ln7jbu2x6wlzofbjcy4a\n",
-      "PHID-TASK-b3df6m2mchn3utytvuaf\n",
-      "PHID-TASK-6qxa43n2e2cuawkmsjkj\n",
-      "PHID-TASK-i5anxr3c7tfz3nnupv2g\n",
-      "PHID-TASK-eav5fcndl4mja6vawvjn\n",
-      "PHID-TASK-2idu63bmownfe3nmo7uw\n",
-      "PHID-TASK-7htliylswhsoxwr2ubyy\n",
-      "PHID-TASK-jgbkfgky2myuop7wzuxk\n",
-      "PHID-TASK-q27xrsziqqu2gvfpstjp\n",
-      "PHID-TASK-5iwkyaqeklkuqfwuota4\n",
-      "PHID-TASK-lcme72ntc4q7f7osmdcq\n",
-      "PHID-TASK-uhyblvwcfbpgyw4wtwxt\n",
-      "PHID-TASK-rnyntxlpgpkvucc3e4ik\n",
-      "PHID-TASK-2vmwo4ulefvzsaoj7eql\n",
-      "PHID-TASK-tqwxzdskyfhflxbbieky\n",
-      "PHID-TASK-okkoyig77ax6awinvswk\n",
-      "PHID-TASK-mker322rzvciw5p7awgr\n",
-      "PHID-TASK-kzdbresrul4febvg7lyl\n",
-      "PHID-TASK-gudx655lxaye4zq5b6ff\n",
-      "PHID-TASK-e4ksvaww5iuvjwbtsxcb\n",
-      "PHID-TASK-s5rvm6dwfjaakdvzgibq\n",
-      "PHID-TASK-r7qy3zpmgywloionffwx\n",
-      "PHID-TASK-7tigxc4wvpbca2apofph\n",
-      "PHID-TASK-bcgfqlvc5q7seezob47j\n",
-      "PHID-TASK-owiuxjd7oca7orel6ps4\n",
-      "PHID-TASK-rfstox6mxs6jh237skev\n",
-      "PHID-TASK-vlfpk6ajyvlxh6hgotnl\n",
-      "PHID-TASK-buwthuzxtqpnnddxy6dq\n",
-      "PHID-TASK-lntjwslyqekt7yy463bc\n",
-      "PHID-TASK-dwqhppzvqivqkml7bog4\n",
-      "PHID-TASK-hkzhgk7ageafae2dzf72\n",
-      "PHID-TASK-2nuk4asg3igwqhymztcn\n",
-      "PHID-TASK-rgzdxwwd2r7aewnb3lwu\n",
-      "PHID-TASK-txpk2gqbin5ejaia7ygi\n",
-      "PHID-TASK-gfuv2xwswyf4byfslddo\n",
-      "PHID-TASK-vcsituk4chxvmxz2c4wl\n",
-      "PHID-TASK-uuqogx3zmcprkfif7yn7\n",
-      "PHID-TASK-euzbw3vi7isnaf55vkqs\n",
-      "PHID-TASK-ej7jssp2ujl54r7e4pzw\n",
-      "PHID-TASK-3twnkxlpgxzvfbcyqhgy\n",
-      "PHID-TASK-rurycjmbtcjhdokp3fmq\n",
-      "PHID-TASK-expmgbsecy7tgvchmyll\n",
-      "PHID-TASK-aunwbewxqem2omz7rmcs\n",
-      "PHID-TASK-owz56g6evszntatdaa2y\n",
-      "PHID-TASK-5smx3vzr2s6nuq4uvikr\n",
-      "PHID-TASK-ytsxsndot74amowyp5vy\n",
-      "PHID-TASK-3bskmko72vtqvqb4i7uh\n",
-      "PHID-TASK-mlk3wsew3wcl527ku3ln\n",
-      "PHID-TASK-fndgxh4r76y6bofc4pwd\n",
-      "PHID-TASK-ejqmybntf4qgjjx56ees\n",
-      "PHID-TASK-xnks7a25xfso6juiiyae\n",
-      "PHID-TASK-64s56xzrc22ustp2z7wx\n",
-      "PHID-TASK-yznolfyf24iw64vdzaqk\n",
-      "PHID-TASK-3ez4hz7oidp3mnpniacp\n",
-      "PHID-TASK-mvlnrj6updlhvfhvduhk\n",
-      "PHID-TASK-gwdd3z7hkhviwmwe5a2j\n",
-      "PHID-TASK-qzxqmy2qhwcdfwstvjhk\n",
-      "PHID-TASK-m5xhygyqlxkvxhsdd6xe\n",
-      "PHID-TASK-kfb3zo4zemxl5qzh25hm\n",
-      "PHID-TASK-mb4drpsu5auacyiu42kp\n",
-      "PHID-TASK-pkce7psg2t4g6fb5wfiy\n",
-      "PHID-TASK-fbhx4wfxlfcwk7mwpqtl\n",
-      "PHID-TASK-5bbhrorxovykfuz52i3u\n",
-      "PHID-TASK-2o36gh7lztukgi2lajdg\n",
-      "PHID-TASK-xtlw6alcryg5gfvrdeqj\n",
-      "PHID-TASK-2czs2gshamoxbwaweocz\n",
-      "PHID-TASK-q6smnzvqe6vc4eby67me\n",
-      "PHID-TASK-x7tgs2fyboki473gy3pu\n",
-      "PHID-TASK-btjddhvc23db2mven5vt\n",
-      "PHID-TASK-hdwzoxwzxwme4zwudykf\n",
-      "PHID-TASK-sa6s63ajvv65ik2b7344\n",
-      "PHID-TASK-kql7loyrzdkr4rwpdcm6\n",
-      "PHID-TASK-shna2ollivhvhx6ukpk5\n",
-      "PHID-TASK-j5pmqk7nfjpk76iccyaa\n",
-      "PHID-TASK-ixmexwlx4wiq23ctxvjy\n",
-      "PHID-TASK-ldrbm7zdbq6hmivijiqq\n",
-      "PHID-TASK-jjb4vcjpt27hv7dg5p5g\n",
-      "PHID-TASK-b5zzf7lh657agk5cdqkw\n",
-      "PHID-TASK-r4klwzo7lxdsgw53zery\n",
-      "PHID-TASK-i4cg3cr5ipw5q2y7rdrv\n",
-      "PHID-TASK-6uhmvpxh7rikbtdr2wns\n",
-      "PHID-TASK-mtdexeiuriq5cdelhc5o\n",
-      "PHID-TASK-4rutvvnh7fiqox2z3go4\n",
-      "PHID-TASK-pcg77ljjtbxyojrgt6ue\n",
-      "PHID-TASK-vek6torvduvoml55paap\n",
-      "PHID-TASK-77axhndq3mqnxx2kqcjc\n",
-      "PHID-TASK-y6bkvqygqya2opqdmv3c\n",
-      "PHID-TASK-d2rlcey47hxosbomhyfo\n",
-      "PHID-TASK-4qadhatjuo4mjlpfaic7\n",
-      "PHID-TASK-yb6ulq67lztw2wvyk4lu\n",
-      "PHID-TASK-k6rdk2swblj7w4zhblsz\n",
-      "PHID-TASK-ih6vrsjge6cjapq5orey\n",
-      "PHID-TASK-2hl7ewtzlnhd3pk5gn7t\n",
-      "PHID-TASK-cl3n6ut5q64yapdxwsov\n",
-      "PHID-TASK-fftdwlrkyjt5yc2hamtk\n",
-      "PHID-TASK-qsgca2wst2byl7ix2pwv\n",
-      "PHID-TASK-awj25x4zsacz62adi3j5\n",
-      "PHID-TASK-e3u3nzdde2xltny25tvr\n",
-      "PHID-TASK-ibds6gk456ofg6szjteu\n",
-      "PHID-TASK-yc4hfzr5ombibggchvok\n",
-      "PHID-TASK-7sjurdxqyilrckxefznc\n",
-      "PHID-TASK-uuaax5ooenq6lyv32r7j\n",
-      "PHID-TASK-7sbdbkrfcvaejzeycoty\n",
-      "PHID-TASK-j6slyvhfp3d6ozltvruk\n",
-      "PHID-TASK-ivktalncu225io76zzys\n",
-      "PHID-TASK-vm7v6vojqzplbnspgwqk\n",
-      "PHID-TASK-cheeem2iuszopjmd3axj\n",
-      "PHID-TASK-b7q472kz3l2dnhbtziiw\n",
-      "PHID-TASK-2z2izcavd5te3dkswczw\n",
-      "PHID-TASK-myow2awxzmx4c4ssz6ta\n",
-      "PHID-TASK-znkh7fhdepbxk6h3va36\n",
-      "PHID-TASK-m3novk5xasw5lqvg62ye\n",
-      "PHID-TASK-g43ik5bj4ejp7p75b5p4\n",
-      "PHID-TASK-v44oexl4vlksqgaeptjm\n",
-      "PHID-TASK-r7nekr4d3omjjmecwwq6\n",
-      "PHID-TASK-5refjnnnoyqumq4ge53g\n",
-      "PHID-TASK-glwrzzfq4ph2os2n2f6r\n",
-      "PHID-TASK-52eneev7kw444gspkrww\n",
-      "PHID-TASK-r45sjfea3cr6rhagxvom\n",
-      "PHID-TASK-iowbxqgcysomfeaijbgp\n",
-      "PHID-TASK-vv7dhxcel5yesltb4ctu\n",
-      "PHID-TASK-icuv2sbiyqbhbfbwtar6\n",
-      "PHID-TASK-bxvvumd26q44ufzm7ua5\n",
-      "PHID-TASK-beabkw6yw7remnijbvdm\n",
-      "PHID-TASK-32fs65piddaapoc5z4hg\n",
-      "PHID-TASK-cilebqon5xuldg2g3esr\n",
-      "PHID-TASK-kcoehi5bluofxq2bsd4i\n",
-      "PHID-TASK-5wvor46u2dd3dffehhqn\n",
-      "PHID-TASK-dt7csod4a2evm53mkmur\n",
-      "PHID-TASK-5bkkyo5d2dquufftw2sz\n",
-      "PHID-TASK-dciqnjw7tyxyl2dkeuls\n",
-      "PHID-TASK-5bwy7gci6gdsa3r3m24i\n",
-      "PHID-TASK-b7yvvcuza7umneartpgv\n",
-      "PHID-TASK-67bjy5it2mluh5artfn6\n",
-      "PHID-TASK-uw2enw4anj5qqfz3lyei\n",
-      "PHID-TASK-2kjxh5erw27qfzcnj2zn\n",
-      "PHID-TASK-exzifkfq2psfgq3kiwzv\n",
-      "PHID-TASK-gngjvjs5g5d7kc4osh37\n",
-      "PHID-TASK-tud4ia4bietz5pnf4dyz\n",
-      "PHID-TASK-rl3v4wnjsqhxlyzhy4r4\n",
-      "PHID-TASK-oua6msncukecknrhwrdf\n",
-      "PHID-TASK-z34hczzuvb2kxj4wvl4l\n",
-      "PHID-TASK-ukt7mx53j5m7gaxam7vy\n",
-      "PHID-TASK-jye77ivrdahrtvdtxmyb\n",
-      "PHID-TASK-v466mnsvk3gmqhazwrti\n",
-      "PHID-TASK-wh5lwbsbwcapw3b5fkjp\n",
-      "PHID-TASK-6tkrmk42gm6l4ttp56da\n",
-      "PHID-TASK-7hihps7ry67el6iq5omz\n",
-      "PHID-TASK-vfbpfzavk4xiw4bzbauh\n",
-      "PHID-TASK-euqyxfrrhmfrgg76hheq\n",
-      "PHID-TASK-ffv55y77ier7bslrsyco\n",
-      "PHID-TASK-bjs5pwsw6c4ji7r65fru\n",
-      "PHID-TASK-6whfmphns7qcm6tbt5j3\n",
-      "PHID-TASK-d53w6sbodbcpx4rkzth3\n",
-      "PHID-TASK-yvetu3dh7pwz6hn5x7ii\n",
-      "PHID-TASK-ldu3pqks4ww5ptxdm5nq\n",
-      "PHID-TASK-zzor3of7nndkvfeeo4kt\n",
-      "PHID-TASK-bnfj7ezq3zkwfxcrblkm\n",
-      "PHID-TASK-4xi6ukfplmi5m5nx7n2s\n",
-      "PHID-TASK-gmkobaxn2aw3klv7tvlc\n",
-      "PHID-TASK-lv7kzqodvetkfp53usel\n",
-      "PHID-TASK-zf3equ3kmfihdlt4bfvt\n",
-      "PHID-TASK-v7rf6nwt2u72ghyq4kad\n",
-      "PHID-TASK-sj4lh4ptvu2lzgg743rk\n",
-      "PHID-TASK-bifywkolpcqrbipm7zgp\n",
-      "PHID-TASK-mt3dwshqj2hvmp73flaa\n",
-      "PHID-TASK-gfulce44jv65rvyd7kt2\n",
-      "PHID-TASK-hys6f6g7uxyhvocshtwi\n",
-      "PHID-TASK-q4c2ad3gdnidfwio3wwp\n",
-      "PHID-TASK-hy7qluemr2knghxwplss\n",
-      "PHID-TASK-vz22yajno24klsq4wdsy\n",
-      "PHID-TASK-5qhy3k4ikqcg7djrpejr\n",
-      "PHID-TASK-35mqsk5kwrqhdyst3iki\n",
-      "PHID-TASK-d2wd3ojejdgstj6g3h2c\n",
-      "PHID-TASK-cxmbeijkrc3gdlqivbjg\n",
-      "PHID-TASK-dtnazl6m376lv35fjrzu\n",
-      "PHID-TASK-k26xtxmrbja4nhavgk5s\n",
-      "PHID-TASK-ff2rzzz5sv5pwbreaohw\n",
-      "PHID-TASK-g5mewjy3ybwuscrobyvx\n",
-      "PHID-TASK-sx57fjn2ccu5x2lvqnvi\n",
-      "PHID-TASK-wh6hb2yzthpqgw4xqhff\n",
-      "PHID-TASK-nscjwo6mgqab76opx5wt\n",
-      "PHID-TASK-l54ayivuqbmpreuplbak\n",
-      "PHID-TASK-2zl7jj2byve5amcxz4nc\n",
-      "PHID-TASK-a27c6scsdqjxaingm45j\n",
-      "PHID-TASK-khh4rz3t6eqnbtz47oby\n",
-      "PHID-TASK-sk5dddkhjvxvi76fjcya\n",
-      "PHID-TASK-2wk7ydj7z2mxwtrff6by\n",
-      "PHID-TASK-eohxemedb6jupuzhjihr\n",
-      "PHID-TASK-hiemxvbjccwrbpce5noi\n",
-      "PHID-TASK-wwj7ivjxi3mj6jsc3tc6\n",
-      "PHID-TASK-ksiwshyonkquzpb6aoz4\n",
-      "PHID-TASK-3jzj5p7wyiyt5e2ugrkb\n",
-      "PHID-TASK-5bbju6mqrb4hytvcocfv\n",
-      "PHID-TASK-kkuldyxop75uyhtvgofe\n",
-      "PHID-TASK-zk2f2rtykxd7etnlrmtb\n",
-      "PHID-TASK-7h5p3whd42ak5tbojlbc\n",
-      "PHID-TASK-vkpbe46usd5elh6546nv\n",
-      "PHID-TASK-yrjidyow5pz4cmjn4or3\n",
-      "PHID-TASK-ju3dj4ysqtrezth635p2\n",
-      "PHID-TASK-3x3n5ljioxs67z2z7nhc\n",
-      "PHID-TASK-6l5wjfkbykj3jdrufonn\n",
-      "PHID-TASK-vgdeswcro65dp4sojtrt\n",
-      "PHID-TASK-sz7lovyjgkskrmxay2d6\n",
-      "PHID-TASK-t4mn4nb76mzz3ahxoggz\n",
-      "PHID-TASK-altlbz4ow72qgwhpfdya\n",
-      "PHID-TASK-h3ux7jbm3qrdgpuszex2\n",
-      "PHID-TASK-5jsfxjyzrxm3or6trnvk\n",
-      "PHID-TASK-kvh4xexeziejdfpxnqcl\n",
-      "PHID-TASK-rff3kdscndxezxto7luz\n",
-      "PHID-TASK-alwvf22pdixzdjmak4za\n",
-      "PHID-TASK-dikhm6z5abefq6sfybiz\n",
-      "PHID-TASK-pquqanuuilo2pfgkwyps\n",
-      "PHID-TASK-pt3ytqx2aq2gdplmppgg\n",
-      "PHID-TASK-z6jywipl5zqujo3htvlq\n",
-      "PHID-TASK-u34r5p3uaxlfwzfdw4om\n",
-      "PHID-TASK-srlf3r7iawflrql5il7l\n",
-      "PHID-TASK-o6yfcomtzmhncilri75a\n",
-      "PHID-TASK-2tym47dhhlsomwrn7ywj\n",
-      "PHID-TASK-ytvabqehjgq7vzt7rym4\n",
-      "PHID-TASK-gbdas2p32dgcym35jznx\n",
-      "PHID-TASK-cr523vgbmfq3b5zfi7gt\n",
-      "PHID-TASK-xzgjkfv633ag6fmt7rky\n",
-      "PHID-TASK-3elt5ys3qqz7nivrswhi\n",
-      "PHID-TASK-apuow26xcvt52fvqwwvs\n",
-      "PHID-TASK-6k2emu2psnugqtpitixd\n",
-      "PHID-TASK-ajcga6hkx4kdoeksqocl\n",
-      "PHID-TASK-amkdzmp26p5hbs2ljuus\n",
-      "PHID-TASK-nnnzye23nj6ys3ykaygo\n",
-      "PHID-TASK-gcgx64v3je25kov2xxdy\n",
-      "PHID-TASK-zuvvxfljo3m4uvk2s3ea\n",
-      "PHID-TASK-ohb2gmeqf4uqlyoctr2o\n",
-      "PHID-TASK-g4ont2tuuoxetvha3ayd\n",
-      "PHID-TASK-nw2zz6yzstf57zmtkbz5\n",
-      "PHID-TASK-upwgk7teb5ogr6ig3z4r\n",
-      "PHID-TASK-5yf5dygkkj6zbjbu5pbs\n",
-      "PHID-TASK-gqixviakwxjhwko6a5nu\n",
-      "PHID-TASK-4tcm2evcvzrqvo5xtchr\n",
-      "PHID-TASK-d4545cy7z4y2r2mrze77\n",
-      "PHID-TASK-v72oxbgvsl4t35xhcxhi\n",
-      "PHID-TASK-fgqx6dqjpzobxffe3bcw\n",
-      "PHID-TASK-mlkcxdg52un5am2qjmf2\n",
-      "PHID-TASK-yaxez2im35xxygh33vod\n",
-      "PHID-TASK-63hk7m7naae6ypxuy7z5\n",
-      "PHID-TASK-xcx7l75kyfn73sjmenqd\n",
-      "PHID-TASK-jtmdegkv2zterww5ielc\n",
-      "PHID-TASK-kn7dujwu6ne4iw4jweqi\n",
-      "PHID-TASK-mgurrwf77bjbyrtqm46n\n",
-      "PHID-TASK-vqfyeha7beo3b4cn7bu7\n",
-      "PHID-TASK-miymejtyr774ogj6oozg\n",
-      "PHID-TASK-un6exrb6nu4tk4ohkbsk\n",
-      "PHID-TASK-kecyjmzzfanyavgzh5ry\n",
-      "PHID-TASK-5vpeo4fnxwtoxb7qsyxu\n",
-      "PHID-TASK-oaaxxaeryjuj676qlgup\n",
-      "PHID-TASK-yb4podernpcrt5eyrrqt\n",
-      "PHID-TASK-4irstsowbqex2mh6wzgk\n",
-      "PHID-TASK-mwpy2efniouotho4t26d\n",
-      "PHID-TASK-c4uueulkx7xekhb35rdo\n",
-      "PHID-TASK-ack5uaxekj6oz3tbot5c\n",
-      "PHID-TASK-i3da234yo25qxkfj7b4k\n",
-      "PHID-TASK-n3nv2432ws3qayvnnhn2\n",
-      "PHID-TASK-pidkwinuimfpigrlcpjx\n",
-      "PHID-TASK-c5xlvoaq4xlahtprsd7f\n",
-      "PHID-TASK-buxz75urt74gcutli3bm\n",
-      "PHID-TASK-a3kbjn7bnws47ljk6ywa\n",
-      "PHID-TASK-2clz3t46qatency62ael\n",
-      "PHID-TASK-ve3s5gkwypzy4otg3e5f\n",
-      "PHID-TASK-ukh27frjetxrfd5snx42\n",
-      "PHID-TASK-kgomrdkqhh5iwoae4w4d\n",
-      "PHID-TASK-nu7ca5igwfzpwjjvumze\n",
-      "PHID-TASK-auvoatapd5phg6h74xvs\n",
-      "PHID-TASK-xez3lpoguhhnw27ay3na\n",
-      "PHID-TASK-5hcwojrrrykznqwemq5q\n",
-      "PHID-TASK-ppa4557zfmdweuq2ycvp\n",
-      "PHID-TASK-p5prxsfn6jdj43jb5hhk\n",
-      "PHID-TASK-giznvs23bxpaswgircgp\n",
-      "PHID-TASK-iboqexwepmrgmkfwmdpm\n",
-      "PHID-TASK-kmwl4sqnbhfoukhb367a\n",
-      "PHID-TASK-5iagtk7ef7sicdms3ksc\n",
-      "PHID-TASK-jr2a2h6e2iclnvx4wa2e\n",
-      "PHID-TASK-2o5afywhjm53xfqkmeux\n",
-      "PHID-TASK-o3mocvfmdnarvi5x2cyl\n",
-      "PHID-TASK-a3yfrijahd6twdq67xo2\n",
-      "PHID-TASK-v3n4j4kb2ell4h52eujf\n",
-      "PHID-TASK-p5kjnipb4qiha2arheu4\n",
-      "PHID-TASK-brolhdih457kpowhgvqe\n",
-      "PHID-TASK-nsm5ksrnyvwuqbyf6qjb\n",
-      "PHID-TASK-wvmydl4bbkdtqm7osvyj\n",
-      "PHID-TASK-uz4ebiomuh52dqhalxqd\n",
-      "PHID-TASK-rlvjrs3munfatsc5rqfz\n",
-      "PHID-TASK-mkaptpov6nx3eewv7jvc\n",
-      "PHID-TASK-btruvlfdq3qyqvht2rk7\n",
-      "PHID-TASK-yata753fflzx3ifjicto\n",
-      "PHID-TASK-6myt7vl23u4acnyzoq5w\n",
-      "PHID-TASK-gyjrpnwlzlseuj5ay2wq\n",
-      "PHID-TASK-6zqiurw6oqkkhhopo7w5\n",
-      "PHID-TASK-tjl4vryiojzktgcw53ge\n",
-      "PHID-TASK-pamojafdtnhybmzjhew6\n",
-      "PHID-TASK-mkqig7y2abufhee3e6a4\n",
-      "PHID-TASK-vqi7xz3ct5esenmosj2r\n",
-      "PHID-TASK-x4x3miva4uelxlwoeyn2\n",
-      "PHID-TASK-otkdojq77s5a7dnwv5td\n",
-      "PHID-TASK-rl2y2ishipdsqzcikuvr\n",
-      "PHID-TASK-dko2nwcat2a5enwq6736\n",
-      "PHID-TASK-ndrboycjw5r2mnma3qfj\n",
-      "PHID-TASK-p274rceja3pbo4jwirun\n",
-      "PHID-TASK-vvn3l4s5izeg73ehqg63\n",
-      "PHID-TASK-dm6dyr2mel4tbhvuduxe\n",
-      "PHID-TASK-xl7tc3cnzjbugrn4flu6\n",
-      "PHID-TASK-3m42xm4a2po4jrwv4dcy\n",
-      "PHID-TASK-wkzeswtrlltjtokvlumh\n",
-      "PHID-TASK-zdzo44mp6rva2lnt47x2\n",
-      "PHID-TASK-ojclybdvdmwc7icip62q\n",
-      "PHID-TASK-rci6ybeykugoc2ofg22w\n",
-      "PHID-TASK-mxtw6d3rc6477dklsvnc\n",
-      "PHID-TASK-j7533hletfeocs3ygieq\n",
-      "PHID-TASK-5usl4n5awcjbcbomw5bs\n",
-      "PHID-TASK-geqryn2sngosctjjau7u\n",
-      "PHID-TASK-wbqcdudfren5nxeb76rg\n",
-      "PHID-TASK-7eeeai67evjmijctkql6\n",
-      "PHID-TASK-svm6hns77rkpqj4hta5x\n",
-      "PHID-TASK-nhp4v32xljmakc2dxomi\n",
-      "PHID-TASK-27c6qwr5exrk2ddgkl7k\n",
-      "PHID-TASK-qxncvpizrrogrxizezsv\n",
-      "PHID-TASK-gns6o7tbrfc7vxzburbb\n",
-      "PHID-TASK-kpls4bc5j2jlc3ln667n\n",
-      "PHID-TASK-cz65rk35yeaxpnwx5nca\n",
-      "PHID-TASK-2bpmj5q3ahfokc4zz46h\n",
-      "PHID-TASK-e7pblfgszxhcuzstcumk\n",
-      "PHID-TASK-dqhh6futiytkca6um27i\n",
-      "PHID-TASK-73pt5ehjfcwtumxwpuww\n",
-      "PHID-TASK-hnf7dr4pfcowjzfzszvb\n",
-      "PHID-TASK-fsbewl22leh75q5wxi4m\n",
-      "PHID-TASK-bnj7f5cnhoxzikonjjvj\n",
-      "PHID-TASK-4gkkbuwk3jlg27h57c3x\n",
-      "PHID-TASK-huk6uolixsrw4vl5idv3\n",
-      "PHID-TASK-hfno6mirclxxp4wamoqs\n",
-      "PHID-TASK-c57y4fdc3ukcmw6umira\n",
-      "PHID-TASK-vfapjnaswl6rsvgrurvh\n",
-      "PHID-TASK-r6jtpcdwjxmbzke3wazy\n",
-      "PHID-TASK-65is3y3rbqummqu5reci\n",
-      "PHID-TASK-qcsqvh62dwh2bjvi4jg5\n",
-      "PHID-TASK-7qcly6qjxshoqdfuzt3e\n",
-      "PHID-TASK-pk3xxotbd2cygxbic2dv\n",
-      "PHID-TASK-unakgbnnnqhghsth6f2x\n",
-      "PHID-TASK-oxgjzrxg7p6u7stnpafd\n",
-      "PHID-TASK-y32jhfrfnhzhio3fteie\n",
-      "PHID-TASK-aanmrkvizmwbalha5bbk\n",
-      "PHID-TASK-cwbxz7kcqiotdqiikk2n\n",
-      "PHID-TASK-fz7qljplu3bbp45jxtbz\n",
-      "PHID-TASK-42zqimydtpfzutihf66c\n",
-      "PHID-TASK-jmmp4zdhs654ea55j6sa\n",
-      "PHID-TASK-tdor3tpvb3ykeaupjgx6\n",
-      "PHID-TASK-zmkykyh2tvcwalgnx52u\n",
-      "PHID-TASK-lahzm5zackfjcqjtlntj\n",
-      "PHID-TASK-m24wzue25r3tbqzzunue\n",
-      "PHID-TASK-ucqemxjwxsynri4inhdj\n",
-      "PHID-TASK-dpxhyjkbi3yny76mtezq\n",
-      "PHID-TASK-pqxet5vnqn3mirgkweo6\n",
-      "PHID-TASK-mpoga25glxtbttk73ydj\n",
-      "PHID-TASK-gekbe2bs7wupt3isplty\n",
-      "PHID-TASK-mpvfengewtqthcpazlj5\n",
-      "PHID-TASK-2pzeuibn247qiu4bfkvi\n",
-      "PHID-TASK-nuccdntq5xq6sbg2nsxr\n",
-      "PHID-TASK-ort3kaznvsgusca4dojy\n",
-      "PHID-TASK-aevdvuut3fcigynuksnq\n",
-      "PHID-TASK-okhxrptvop7zaitv5gj5\n",
-      "PHID-TASK-wno2xwrbywvfr44kwnto\n",
-      "PHID-TASK-vjbacwfxxizwddsg34zm\n",
-      "PHID-TASK-zom2liucvmkdzjzairgy\n",
-      "PHID-TASK-5udu3lh4gaeui3owoea2\n",
-      "PHID-TASK-nt5xhkrvd2i4xkg5ro26\n",
-      "PHID-TASK-ughpsi3kiwodix5i5iuq\n",
-      "PHID-TASK-fp5nv7xkzn6llpv5rdfl\n",
-      "PHID-TASK-xtf36l2ciogrg6tcnf6x\n",
-      "PHID-TASK-yohnyaa6rhyxwjflhy7p\n",
-      "PHID-TASK-iueuapim3yguer55bovm\n",
-      "PHID-TASK-jozgz5cpm6v67hgjs2el\n",
-      "PHID-TASK-2hkltmsnr5h4bebiuu3r\n",
-      "PHID-TASK-cmxp5glim7b3bnu36xg4\n",
-      "PHID-TASK-772o537nc7bdn7wry7rh\n",
-      "PHID-TASK-og532unr32aprpg62cxq\n",
-      "PHID-TASK-pbprcixeydceic4lndax\n",
-      "PHID-TASK-vdyxqxqymleikvtbkkbj\n",
-      "PHID-TASK-pcp54qhvwgbbzskvrcsq\n",
-      "PHID-TASK-r7mvsfuq3amffbdzvceu\n",
-      "PHID-TASK-37lwji5jwrqcsuanpdky\n",
-      "PHID-TASK-ofzs6modf4yxz63ugmdy\n",
-      "PHID-TASK-otxks6mxubirbwsvqvfv\n",
-      "PHID-TASK-u7g6dtcwyoyjlymqpi37\n",
-      "PHID-TASK-wurlwpdl3llexy7jqxw5\n",
-      "PHID-TASK-hf7auwexf5hzfjlto5wz\n",
-      "PHID-TASK-ltqykuq33aln74viml6d\n",
-      "PHID-TASK-jfbnqce7vgau7v3adje4\n",
-      "PHID-TASK-azn3jqm7c4zgqmbqnk6m\n",
-      "PHID-TASK-eibrrqabz54in23ld6jv\n",
-      "PHID-TASK-c6w4q2qazxtjqqz52eh5\n",
-      "PHID-TASK-lryy7gpyx4cjl47ybghb\n",
-      "PHID-TASK-krpdp7rpaekkdslv6m5f\n",
-      "PHID-TASK-gcadzjjnt6fiqkhy623y\n",
-      "PHID-TASK-vy4qb3tkuvo3pp2bvalh\n",
-      "PHID-TASK-hebmh46ynxb5xtfcynmn\n",
-      "PHID-TASK-ndk7b6dff6ow5oi3ifru\n",
-      "PHID-TASK-np4k3bluhrwdx3t7fl4r\n",
-      "PHID-TASK-m6ahh3o7wiecdy5522i5\n",
-      "PHID-TASK-cqabqcw62xkqwgp5vzag\n",
-      "PHID-TASK-7qyivx7mukqztl4bew6d\n",
-      "PHID-TASK-bxloupudebssszvcsfyv\n",
-      "PHID-TASK-6xcbbe4kcyhfokfy2ccf\n",
-      "PHID-TASK-qkmncwgadvm2zyw4ptz7\n",
-      "PHID-TASK-lfivv2gwageaek5qpppw\n",
-      "PHID-TASK-b5mzjxluwzhdjnamwvwg\n",
-      "PHID-TASK-6cgiws4wsgspk77z65mb\n",
-      "PHID-TASK-qjbo7xdeq7skmyh72eli\n",
-      "PHID-TASK-jx5wa6pf2qanvuyvggpu\n",
-      "PHID-TASK-rwiwk6z77szqe2xi53tu\n",
-      "PHID-TASK-aaldjasjdqcsgs4dgei6\n",
-      "PHID-TASK-rtprhlspp44bc3deup2j\n",
-      "PHID-TASK-r5dtguf5lpskmwirqnjk\n",
-      "PHID-TASK-i2hkjs3uujagjhxf5ecx\n",
-      "PHID-TASK-j2ivwzlbwna3s5gipwur\n",
-      "PHID-TASK-nxkrip2qpu45o4qn32qd\n",
-      "PHID-TASK-qc5trqqgz5vloi4oqng6\n",
-      "PHID-TASK-v4yeqp4ktfp26rooyyb4\n",
-      "PHID-TASK-iro4l3sspq3bi2nblqmz\n",
-      "PHID-TASK-227untois7bfweaz7mct\n",
-      "PHID-TASK-vbe43kp33h3r5mdxnudc\n",
-      "PHID-TASK-u6jklhcw662pkjycjvtd\n",
-      "PHID-TASK-2vhxquft7zgsd3wwscky\n",
-      "PHID-TASK-ycn3ic72wlfp37rtzxzr\n",
-      "PHID-TASK-6nnrbmhm34zvreojlgpl\n",
-      "PHID-TASK-wqkvsiwaq4pnd2lugivq\n",
-      "PHID-TASK-ocb7ebf4v6bjoboovjt4\n",
-      "PHID-TASK-qcrmoxueaa23emzyho3c\n",
-      "PHID-TASK-6ronffn6fe4mqkisco3e\n",
-      "PHID-TASK-ogvz5uh6cxjgnxeelh7e\n",
-      "PHID-TASK-d2r6gtoaqlgf6litoxhf\n",
-      "PHID-TASK-xctt6gf3mq7aojdrpzna\n",
-      "PHID-TASK-lq26x5df5b2uayf5w4sb\n",
-      "PHID-TASK-sizovmscvvm6rifym437\n",
-      "PHID-TASK-7n4a7riwzybvgg2yg5oj\n",
-      "PHID-TASK-225bp5yp7locuogtr3qd\n",
-      "PHID-TASK-ioynhxkaq6fkwspf5nvl\n",
-      "PHID-TASK-zdasmwk6nzlmwf5wx5ui\n",
-      "PHID-TASK-gkhfh2wlphtsgti7jxch\n",
-      "PHID-TASK-vz3x2eqhdts2i7ebivnh\n",
-      "PHID-TASK-gxyil7alpbre5j7mytzf\n",
-      "PHID-TASK-vgqjfn2lbwd73gkgod6a\n",
-      "PHID-TASK-xrfq4g5uc44xmpqmjyis\n",
-      "PHID-TASK-5g5bsfyli427a7al2nvk\n",
-      "PHID-TASK-zegr7o2fy2tmw2zqjzmu\n",
-      "PHID-TASK-k2eejhz2gxdoin7eo4qz\n",
-      "PHID-TASK-zf5c7zmnxbn4etopqpde\n",
-      "PHID-TASK-kxhi7vtkl2n4fcawl2u5\n",
-      "PHID-TASK-4lsnvnfnca247mubrvhc\n",
-      "PHID-TASK-nzp73hbths7mtxjcxvm4\n",
-      "PHID-TASK-y5chdora657t2p3e7tbs\n",
-      "PHID-TASK-5ulqzr566hicsrhuontf\n",
-      "PHID-TASK-gf4us2lajwz7mnxt2hru\n",
-      "PHID-TASK-zwurzmbrgsoaldr6hnqg\n",
-      "PHID-TASK-ki5b25is43aulcidvmv4\n",
-      "PHID-TASK-phnj44ch6mszxq6qpohn\n",
-      "PHID-TASK-3x6kkofcned4qcjjk6dl\n",
-      "PHID-TASK-ixgrpcodnk3skm7y2hlt\n",
-      "PHID-TASK-nx2jsmtulfpacm6ytqq2\n",
-      "PHID-TASK-pau2osi4bgxm7omr62y5\n",
-      "PHID-TASK-d7f46ss2k5gqniu6endn\n",
-      "PHID-TASK-cqmy2yutnupgu7hrfwej\n",
-      "PHID-TASK-hlddr6phtisadyt4ixuj\n",
-      "PHID-TASK-csoldbfxlq5rsqqvnrq6\n",
-      "PHID-TASK-2rc2hldv5lyl6kgrhcon\n",
-      "PHID-TASK-v5ulk7ng472f6cnu46nx\n",
-      "PHID-TASK-vcoxn3g74svzqfbhj3kr\n",
-      "PHID-TASK-r3yfhoreb7uextmhj5cl\n",
-      "PHID-TASK-ezhyct2qlpeljnoxkbyi\n",
-      "PHID-TASK-goupncgsrq626ilxi7gq\n",
-      "PHID-TASK-sffadm7jcu5zx5bxq7pj\n",
-      "PHID-TASK-rmjs32q5moc3ksh5b4i6\n",
-      "PHID-TASK-kvfwa2nd6meb57icljm7\n",
-      "PHID-TASK-u3drbnyix6yjkcu5oyqk\n",
-      "PHID-TASK-ip33qxtt2biyhu6zcsou\n",
-      "PHID-TASK-ly47mruxj7vi65vxkzoe\n",
-      "PHID-TASK-ynfnvjveqi44j7uneaz3\n",
-      "PHID-TASK-7xrtsoeeizfsiz3k6g62\n",
-      "PHID-TASK-67pmnsh7dhho75ccfvye\n",
-      "PHID-TASK-26ap2rg73qekvvcczshf\n",
-      "PHID-TASK-d3gqxoje5kzf5dkzzc7n\n",
-      "PHID-TASK-7knsheja5rlwn5x4ough\n",
-      "PHID-TASK-psa6ws3eur6fpdx4wxx6\n",
-      "PHID-TASK-y2qrrzk3vroo6d7obsoq\n",
-      "PHID-TASK-nmx2oitfu5c5j3jvk2xb\n",
-      "PHID-TASK-rowxfowcw2djnxscevba\n",
-      "PHID-TASK-33whpxom3nwt6xusuiuy\n",
-      "PHID-TASK-bw6f5yfozkwjmdh33dvf\n",
-      "PHID-TASK-dwxkxakygop4b2h6bkwj\n",
-      "PHID-TASK-4fzagmogxghtgnyhorob\n",
-      "PHID-TASK-lcdwdqoqbndlmqibkajx\n",
-      "PHID-TASK-k2jmjawnw4bqcn7k66fw\n",
-      "PHID-TASK-6si76vcvgzigcakihtz4\n",
-      "PHID-TASK-sdhut7ee3wusfacg3uhp\n",
-      "PHID-TASK-355w7hlobmllbrlusrps\n",
-      "PHID-TASK-2gcwk5t4olp3qx43ljc7\n",
-      "PHID-TASK-mw46y7ei5hcau3e3zb6y\n",
-      "PHID-TASK-3jt32w56utgsiwksttva\n",
-      "PHID-TASK-yifu433xtyd2cz6f7zjy\n",
-      "PHID-TASK-hfgaosahvwicr3n3m3lj\n",
-      "PHID-TASK-g6ao2orn4uf6igum3xuw\n",
-      "PHID-TASK-n5bah7oda2vyaqmkor4k\n",
-      "PHID-TASK-ilhxonhqlmyxfkhaqn34\n",
-      "PHID-TASK-mbgornmacv5hvpihufw2\n",
-      "PHID-TASK-u54zpp3nlpyzgygilqys\n",
-      "PHID-TASK-iij5s3q5lqjww4xxudga\n",
-      "PHID-TASK-se5cgamgbkdgfzjnta6l\n",
-      "PHID-TASK-qe7ct72pnrg4lcr747kr\n",
-      "PHID-TASK-xbwpkppvqworctg5ub5j\n",
-      "PHID-TASK-j4pdqjq2wnzhgv26mfh6\n",
-      "PHID-TASK-7ho2brlduxnhg2gejymz\n",
-      "PHID-TASK-piljwz7ejgbgmrwmptju\n",
-      "PHID-TASK-ciemclcqodgd6pk6mejb\n",
-      "PHID-TASK-6hvjba3tuflbtzmptodb\n",
-      "PHID-TASK-ljbacnsrtxmpcftewdk3\n",
-      "PHID-TASK-olyocmpjb6k7cvxtzx7a\n",
-      "PHID-TASK-nbxtzfyyzyj53uup2gmf\n",
-      "PHID-TASK-dd4n7egyr75tqjapspdy\n",
-      "PHID-TASK-irielkewu77v4z4a3hlm\n",
-      "PHID-TASK-6754fqjnk5hw4q6cz6zc\n",
-      "PHID-TASK-ximodnbmrouyqq5tnhwi\n",
-      "PHID-TASK-zmktchjngp5bwq3bloha\n",
-      "PHID-TASK-lutd3sk7dfkqcmljv7ob\n",
-      "PHID-TASK-3z36ic6aws767el6smak\n",
-      "PHID-TASK-gokdl4kwqlwt6cmm66eh\n",
-      "PHID-TASK-5qn7fz4uqtu624ogpnuh\n",
-      "PHID-TASK-l56rigwmq6kptg33obmi\n",
-      "PHID-TASK-gxelvauhc4ymdd6gw2ss\n",
-      "PHID-TASK-yt7hoiqatg2twcdmiujq\n",
-      "PHID-TASK-zs5e5bzcmcr4rtwmlnui\n",
-      "PHID-TASK-62gwo3nopvq6bsrwmth7\n",
-      "PHID-TASK-usrosfs2iqiakawkjchy\n",
-      "PHID-TASK-cp3g7luvxfst4ptkx7me\n",
-      "PHID-TASK-25boqjke4cijtwjgyjbt\n",
-      "PHID-TASK-b2icu3jhk57jo4lbtgez\n",
-      "PHID-TASK-6krx2nyb5rqgwoao3nrw\n",
-      "PHID-TASK-323aluzrs2vl2d7v27bc\n",
-      "PHID-TASK-m2mjxjfupqonuuet4g5a\n",
-      "PHID-TASK-lac4g5g62zrekkfygvxx\n",
-      "PHID-TASK-yurtnajxpg7fxltytwpi\n",
-      "PHID-TASK-btmvpbqnfpj57y5y72ua\n",
-      "PHID-TASK-zhochcqzfoj4bimpgiqx\n",
-      "PHID-TASK-gtujhqzrxk5hd6l7lxu3\n",
-      "PHID-TASK-timuxvvj3wafz5qt6zh2\n",
-      "PHID-TASK-vod4bp3xvmjarqf6dtmz\n",
-      "PHID-TASK-bxocvjff7v4vgwjuctgr\n",
-      "PHID-TASK-gwypfbeszglyxfdqtuls\n",
-      "PHID-TASK-r236onqi4kxnnfykppxk\n",
-      "PHID-TASK-lb4esyvemyxlbz7scvjj\n",
-      "PHID-TASK-xdef52u2xoutalmxvqxq\n",
-      "PHID-TASK-2hjerlp3jrpdifpv6ca6\n",
-      "PHID-TASK-covwdyeu7km7zagn5wbs\n",
-      "PHID-TASK-ey2t66avbr7lh2xruo6p\n",
-      "PHID-TASK-riotbykdtow5sbh7ljef\n",
-      "PHID-TASK-mcp3tejcciwpxx3d2tbm\n",
-      "PHID-TASK-f2ifd6fdj6pchv36q7fq\n",
-      "PHID-TASK-f3t5ledkhevthmf76bbm\n",
-      "PHID-TASK-5qndpoaoah52uflwalmh\n",
-      "PHID-TASK-4yqfpq6tylsvui2kalk4\n",
-      "PHID-TASK-eee27mysfumux3ogerbm\n",
-      "PHID-TASK-6yggapp3gflkqr5tutc5\n",
-      "PHID-TASK-mhhjk5pjhzhxuptufuod\n",
-      "PHID-TASK-iu3irtpbwblnycah2bvt\n",
-      "PHID-TASK-vtsg5xob5vkahyr6gi7o\n",
-      "PHID-TASK-l4vjyqc363bdzzivdhbk\n",
-      "PHID-TASK-xcqwgfkr43r7ohstvh74\n",
-      "PHID-TASK-oap3pcoqr67a3nxmzly7\n",
-      "PHID-TASK-kpwswnv3ba5na6dn3pbp\n",
-      "PHID-TASK-v3oimjdnujt4xxuujgme\n",
-      "PHID-TASK-3tsgq57muuprxfvxj5ar\n",
-      "PHID-TASK-kts426m6tijfml3ngiqw\n",
-      "PHID-TASK-zjzk5xt7l23o75cnuaf2\n",
-      "PHID-TASK-dgtxn3qlqf7gdy53gvep\n",
-      "PHID-TASK-rdqowzyta6j737yhntsg\n",
-      "PHID-TASK-42yujcjufaw4amwkd6cx\n",
-      "PHID-TASK-l4uq3cbllrcxoqio4v45\n",
-      "PHID-TASK-ni5qpiyvtnjgi6dt3iyo\n",
-      "PHID-TASK-kbipswhiezygmb4rkkls\n",
-      "PHID-TASK-utvzk3vp6pazzmc524i4\n",
-      "PHID-TASK-atmvlu42kr6udcjperus\n",
-      "PHID-TASK-r2uo7jsfp6tf7hhh7pgx\n",
-      "PHID-TASK-gjdaipusi2pbcwygi4nx\n",
-      "PHID-TASK-dahdfluva5saanqyyruw\n",
-      "PHID-TASK-ufqs3dhnocvsaimspsxt\n",
-      "PHID-TASK-jf4ozwjh3vlshz4bzqkm\n",
-      "PHID-TASK-e3i52jzvuvgyt4mfbiae\n",
-      "PHID-TASK-sb5pc5upei6lbqlstsbe\n",
-      "PHID-TASK-5i5trthg3bfis3yeyeyg\n",
-      "PHID-TASK-dqr5vyv74wju5geh4nth\n",
-      "PHID-TASK-vvjswcot4n4j42ahvoek\n",
-      "PHID-TASK-uh22mktin45cgziwuwry\n",
-      "PHID-TASK-zwykrgbpiln6fvzmfzeo\n",
-      "PHID-TASK-dvyukuw5fsuzum36qlzx\n",
-      "PHID-TASK-gvtbr3mwdnel75bfmsye\n",
-      "PHID-TASK-wsp5xk3lssgxslzaamko\n",
-      "PHID-TASK-ok75mzddmda57d6nn6kk\n",
-      "PHID-TASK-bexcdxbi3u4bthv7sscm\n",
-      "PHID-TASK-vgvl47jspv2pkkjrsfci\n",
-      "PHID-TASK-lowf6tecq6p7hjj3ouia\n",
-      "PHID-TASK-upb3ctljk2bwd7r3gsy3\n",
-      "PHID-TASK-rafw5v7fpv6llvfw3itz\n",
-      "PHID-TASK-36ttyeifxhhwq5q4jnq3\n",
-      "PHID-TASK-7qcobbntfbebu2v6aryi\n",
-      "PHID-TASK-rfypkehjlixpt65ao4mm\n",
-      "PHID-TASK-slqzyalxfqafkznbvky4\n",
-      "PHID-TASK-nhlyafdpxr6icar37fw4\n",
-      "PHID-TASK-2yxmskm3croyyjfnp4wh\n",
-      "PHID-TASK-jsdvuoacpjes6iw6v4vx\n",
-      "PHID-TASK-patmtmusp6dirpvlwuru\n",
-      "PHID-TASK-744uhoqz2qaraesrqoyi\n",
-      "PHID-TASK-eumorghlixcu2bg3vnve\n",
-      "PHID-TASK-p7dsmh4gtfhvebckg5yk\n",
-      "PHID-TASK-cnlgzxw2fzybmpp3j5xx\n",
-      "PHID-TASK-oypbzk3jpzff5cgsiva7\n",
-      "PHID-TASK-p2fgtkqsv3nbsvtion3a\n",
-      "PHID-TASK-s6y4w7kahlei5ddylfmn\n",
-      "PHID-TASK-y5w7khnzvllsehcslsmd\n",
-      "PHID-TASK-c3ineb5mdwoziw4jeqdo\n",
-      "PHID-TASK-tm5h6mdh2hlegrznd7pk\n",
-      "PHID-TASK-h5arfbwysxbybm7hujkv\n",
-      "PHID-TASK-ki5ndhcsugxw2thwlhd4\n",
-      "PHID-TASK-crf7s6bmhldwret6sy4u\n",
-      "PHID-TASK-lcm5zsufp2kobbnnphbv\n",
-      "PHID-TASK-yht56d7rk34lqhlubcge\n",
-      "PHID-TASK-eo43z5xddf6sg3om7sem\n",
-      "PHID-TASK-zdphbo6gq23bo6llwwdp\n",
-      "PHID-TASK-omucxcdp6ujh4xt2zaue\n",
-      "PHID-TASK-4otjzc7vuobs4xcw5kx2\n",
-      "PHID-TASK-hqe3vfy7ixkkhkavdrmm\n",
-      "PHID-TASK-kfrktikcnijejv2ssua3\n",
-      "PHID-TASK-37pnzuvt2mm7zi2opamc\n",
-      "PHID-TASK-n7jievcoinoyg7mcltce\n",
-      "PHID-TASK-dujs2kys4ubjpcmrausf\n",
-      "PHID-TASK-z5fquxt3pmfidowhr5a7\n",
-      "PHID-TASK-l6tkqmvanqkkeexo642z\n",
-      "PHID-TASK-eq2ksi6d2va2c2ejstl2\n",
-      "PHID-TASK-ecndqfmm5tbhzjqkbox5\n",
-      "PHID-TASK-72io3l35lrubzg5lhtmy\n",
-      "PHID-TASK-fsd7k5bgeeg76dzbdwqt\n",
-      "PHID-TASK-4oyxxjh4jqregv7p7irk\n",
-      "PHID-TASK-sb4u7diaqxhpd6losrrl\n",
-      "PHID-TASK-qd7qmbfus3ten7z3kj22\n",
-      "PHID-TASK-6kcc6zwg5etjn2shtwsu\n",
-      "PHID-TASK-wh2szim422wwxdw436uf\n",
-      "PHID-TASK-i2lmjhrkpsur4lev23mc\n",
-      "PHID-TASK-6hhndn43mfdn55mwrsk5\n",
-      "PHID-TASK-ulu6mdlz3xg6p4np7egn\n",
-      "PHID-TASK-qpfa44mctjexoxkqo5hy\n",
-      "PHID-TASK-c5hksu6p5uhmhvzh64ht\n",
-      "PHID-TASK-qxsrbiw7op5y6y6inavq\n",
-      "PHID-TASK-mbub4crzlrqq6sng5lzq\n",
-      "PHID-TASK-nng5pyk5o4ztbazvqymy\n",
-      "PHID-TASK-2mttdczw7itqtq7orbyc\n",
-      "PHID-TASK-2smfwsfpsgu5q6m6ladw\n",
-      "PHID-TASK-6oalc7d7kvavaxvkwlfd\n",
-      "PHID-TASK-gqb7b73hwnhh6qxsaoee\n",
-      "PHID-TASK-poin5yyszgpyi25gk3je\n",
-      "PHID-TASK-34urcguvs6tsm3wpvxu2\n",
-      "PHID-TASK-wodgydx2ln55w6eo4p32\n",
-      "PHID-TASK-ibwc5pqjlv3hmwafkxsy\n",
-      "PHID-TASK-mrrmkqrflbgdrpb2xbtx\n",
-      "PHID-TASK-awob47g62om2eeegot3r\n",
-      "PHID-TASK-6t2ellqdwuvd5rouaqmf\n",
-      "PHID-TASK-euq7ddmd6rhlinex2kpe\n",
-      "PHID-TASK-3rb6x5qzoi77sgsqzncr\n",
-      "PHID-TASK-xoirrjdhitvqz5v3riwf\n",
-      "PHID-TASK-pgc3jemya3dsi32iivp4\n",
-      "PHID-TASK-kwxuse4ccvh4vqlns2jq\n",
-      "PHID-TASK-dmyb42alfmzpnf6hhtbk\n",
-      "PHID-TASK-uhuzwsa5ueu5efipt6sv\n",
-      "PHID-TASK-sbvwivlalvusgjwp5ire\n",
-      "PHID-TASK-ggvevjnwwlcst5xdmmsn\n",
-      "PHID-TASK-q2lm2rmvtrop4xotxxnt\n",
-      "PHID-TASK-22g4ckg3k3byisqvwxiy\n",
-      "PHID-TASK-m7leu4xitl3lklt5rrdg\n",
-      "PHID-TASK-hxm7dylzsr7cb36xgt4j\n",
-      "PHID-TASK-b2the5znff3yi5iqewab\n",
-      "PHID-TASK-tjb4bkjfszkwoz7qktjo\n",
-      "PHID-TASK-kgksabqabkax4kkg7izy\n",
-      "PHID-TASK-twgftigrpz6uckwjelnt\n",
-      "PHID-TASK-lhb7q2iod46plkygoni4\n",
-      "PHID-TASK-rutprbjwmdkgbr5b3uoo\n",
-      "PHID-TASK-nbvnewtd4mrfr4a4ytce\n",
-      "PHID-TASK-32bj4xsfxzl66kfabfpq\n",
-      "PHID-TASK-prrrskdzk7yoo3hn4dt2\n",
-      "PHID-TASK-ooqyq4axuutnv7pchwcb\n",
-      "PHID-TASK-ufkgro7khm6qaqk6mboe\n",
-      "PHID-TASK-32vbq6qkhx3wngjcnodn\n",
-      "PHID-TASK-6hbiyaynilweesovh3xs\n",
-      "PHID-TASK-plwpcaqphz3xxe7n4naa\n",
-      "PHID-TASK-5wto4e4bokkzs7zmbjod\n",
-      "PHID-TASK-d3idqafxjg2fp5yxwuqt\n",
-      "PHID-TASK-xs35ywfjwn7iygqwhlqh\n",
-      "PHID-TASK-htmipabmc3qfaiznrebo\n",
-      "PHID-TASK-eja43n7xny5lbdanmj4p\n",
-      "PHID-TASK-lpdahuwz6su3aljkvwaf\n",
-      "PHID-TASK-qgpnwx66d3gjnes6vhh6\n",
-      "PHID-TASK-iuv45mcdfmqdyf3lof4l\n",
-      "PHID-TASK-uftjcaqg7wftryrkpsp5\n",
-      "PHID-TASK-c6grklf7gpa6ipg5o6y3\n",
-      "PHID-TASK-tzaqvebpmuva7a34ejvl\n",
-      "PHID-TASK-6jr33finz32lgguug7oy\n",
-      "PHID-TASK-t4dsq6rpgyk5vhbxgywu\n",
-      "PHID-TASK-uhsm2u4fy2r57ifl5now\n",
-      "PHID-TASK-drnulywmv5gyytjha22k\n",
-      "PHID-TASK-6t3k4ac3wbqeudiatuwg\n",
-      "PHID-TASK-jruyips3fse6ym3bsadi\n",
-      "PHID-TASK-5cydsdjiqddokog4ej2b\n",
-      "PHID-TASK-z4ctrxtxswdyl3z2vpsi\n",
-      "PHID-TASK-cgtmnxzfbtaknv2y77sf\n",
-      "PHID-TASK-dbzugsxj63hxmjo7guoe\n",
-      "PHID-TASK-djxrtouulbirtmeqhyvj\n",
-      "PHID-TASK-zkjur77n4a4fhw75q46a\n",
-      "PHID-TASK-ztcqreqfln2w4zvztfod\n",
-      "PHID-TASK-nw7eq5nisvhi4vmqmjnf\n",
-      "PHID-TASK-66xp2mmqcy647pdvgm4x\n",
-      "PHID-TASK-7ogjkc6ddhzycfrd4aut\n",
-      "PHID-TASK-bawhmiorm2ucu6th36wp\n",
-      "PHID-TASK-72rziu6fsgfsmc5bjdnx\n",
-      "PHID-TASK-hec6fvmphtw5a6pgaa64\n",
-      "PHID-TASK-2a2cr676hxaynicchkxu\n",
-      "PHID-TASK-xdv6gb57qioudhzewlqo\n",
-      "PHID-TASK-rzowuuc23degrhsrsjvb\n",
-      "PHID-TASK-sgia5xvzrqql7odhc5nl\n",
-      "PHID-TASK-5hxk5ete5tb4osa6g3ma\n",
-      "PHID-TASK-qgb5fgt6vmjtfvknn43z\n",
-      "PHID-TASK-kimy5ztgryvb4j5fhi5i\n",
-      "PHID-TASK-ccs2prus5tuvbhududhj\n",
-      "PHID-TASK-zvbelbjtso7n2rf7unpl\n",
-      "PHID-TASK-445qwg6xrym7xzuyvyec\n",
-      "PHID-TASK-dgtigim34wqholkwxjpw\n",
-      "PHID-TASK-y4pcs6u7xh3tw5y7ea4f\n",
-      "PHID-TASK-hl7fehn5dewfavdk36so\n",
-      "PHID-TASK-gsqvj57elluda2nmu55f\n",
-      "PHID-TASK-43dibnfvzllm4nbj6ga3\n",
-      "PHID-TASK-imfh6gg55vyil5deeyj5\n",
-      "PHID-TASK-xjqjhle7et4eysgadisw\n",
-      "PHID-TASK-m5ly62fnpxkni7on4d5x\n",
-      "PHID-TASK-ya3ww47fwcb2aqeuzqly\n",
-      "PHID-TASK-waufzrnebrjzcfjas3t4\n",
-      "PHID-TASK-m2ogvfsvhbevnrvvzb4q\n",
-      "PHID-TASK-2by3cfwyw4mn3t7yyzoq\n",
-      "PHID-TASK-xbuo4fcnx4oupw7ol2me\n",
-      "PHID-TASK-ytppcpdbs2adftajp5tt\n",
-      "PHID-TASK-5zskngbxk4z3y36fzvyt\n",
-      "PHID-TASK-x2bemat6dbvj4qacn3ja\n",
-      "PHID-TASK-bytfsofa3wltd64urfvv\n",
-      "PHID-TASK-hibjkpd4gxjy4lfkuxhu\n",
-      "PHID-TASK-k23jbc4tij5lhe6eeo73\n",
-      "PHID-TASK-4tqy4h2htavrdjo2k36n\n",
-      "PHID-TASK-w7zawrtzky3vftelryka\n",
-      "PHID-TASK-u6bt2ddckctrby5sscwl\n",
-      "PHID-TASK-eq6kmmhfj5sxk522ij2u\n",
-      "PHID-TASK-xkeqdnpvwm2mnuk2p4kq\n",
-      "PHID-TASK-bnfed45fsdr7ijiu7iy4\n",
-      "PHID-TASK-jyvhhwmshuq26opbmerd\n",
-      "PHID-TASK-huguj37vwbp5tlmsngzb\n",
-      "PHID-TASK-4iunqtmz3u4jccn23ct7\n",
-      "PHID-TASK-ar7o222adkj6yo6s5o5w\n",
-      "PHID-TASK-qdobmgita3aclomioanb\n",
-      "PHID-TASK-z5y5vu36oczd2xqoi5r7\n",
-      "PHID-TASK-hy35new7rxofajvvqivl\n",
-      "PHID-TASK-owimzdmbcsatfp52eoa7\n",
-      "PHID-TASK-gjqblxpe4th4o7zcpret\n",
-      "PHID-TASK-xrx5soggiup6jgpqpzkt\n",
-      "PHID-TASK-kvr63y5we4pdqpvagdka\n",
-      "PHID-TASK-pv364hftdbapyxednn7m\n",
-      "PHID-TASK-tchh23qe4nddxeojdetp\n",
-      "PHID-TASK-xaefdkhei34lxghlfb26\n",
-      "PHID-TASK-bj5auvkiqa4ukpb3i76l\n",
-      "PHID-TASK-dxtpzjislp3ykzi64aen\n",
-      "PHID-TASK-6las75m7yq6t6y42jony\n",
-      "PHID-TASK-um6o7aq2fxsloslxu5y5\n",
-      "PHID-TASK-yofovlast3zou4zon7j5\n",
-      "PHID-TASK-n4ayvtd5iz5jguzeqtvl\n",
-      "PHID-TASK-ql37zwei7lw6idcpnjvx\n",
-      "PHID-TASK-mlek6l25jsi4523n6c4x\n",
-      "PHID-TASK-dfnjvi4ebxg4qf7ygljp\n",
-      "PHID-TASK-qjg3q7wq3q3awr64hcmy\n",
-      "PHID-TASK-bd72y7iiei67kbxti76b\n",
-      "PHID-TASK-sj7ezonvgeb3be62737a\n",
-      "PHID-TASK-pdpn7hvlculri4ccy42t\n",
-      "PHID-TASK-lxnv4tg7oifuczocddhi\n",
-      "PHID-TASK-zomjkczfpnrvxzpe4yzr\n",
-      "PHID-TASK-hesseird5ugq7qigg32p\n",
-      "PHID-TASK-djpv4d2tw7he7bcaiwgo\n",
-      "PHID-TASK-ktfyzhjkb3urubsydtou\n",
-      "PHID-TASK-53pjjq3mogcsnoshnrpu\n",
-      "PHID-TASK-5usozn6lenkcoenzeuyk\n",
-      "PHID-TASK-gcsogk6cy5vhnwnvhuql\n",
-      "PHID-TASK-wf4d3yulifq7pdamnvpv\n",
-      "PHID-TASK-uro44a5vqso2sy7u2arn\n",
-      "PHID-TASK-ez3lf5ze2ra5vwgm2kwo\n",
-      "PHID-TASK-dusvcxcsy7gqikdevzgn\n",
-      "PHID-TASK-brld2i7xjlh2vp4m2jxn\n",
-      "PHID-TASK-keti3xueyglzi4p4spht\n",
-      "PHID-TASK-dfdz2k3zlkzv6jpt4n44\n",
-      "PHID-TASK-pqtihvfc7f4d73rdtnjq\n",
-      "PHID-TASK-ma7ogjs2kvk66wshe44k\n",
-      "PHID-TASK-dhqbmbptdf76io4mrpls\n",
-      "PHID-TASK-uvse6kpckod47zira6mk\n",
-      "PHID-TASK-skm7yk65ve7ofcodlrqs\n",
-      "PHID-TASK-jjwaxnsw7nonpkj5w5ug\n",
-      "PHID-TASK-m5whhh35h7fkdpaca77l\n",
-      "PHID-TASK-cbkpykct3waf2q7jincj\n",
-      "PHID-TASK-hvan6ykhuzyhtye5e56x\n",
-      "PHID-TASK-lz4m6zadc7gusnegkxep\n",
-      "PHID-TASK-5xzxzrfm4dqssl7w5dix\n",
-      "PHID-TASK-q6pz6kygm2rnc3zs7geb\n",
-      "PHID-TASK-dhmvhapysnb7mmzkzrmc\n",
-      "PHID-TASK-5k5rt6qbkoyx3ta4vs6h\n",
-      "PHID-TASK-lfg46f7cy7mmetnq3hpg\n",
-      "PHID-TASK-inp4lb4bxjfhduddc4ri\n",
-      "PHID-TASK-z2y2nxnb7rd7vpntvfza\n",
-      "PHID-TASK-5gtyq6ebthpfjdmqjbyu\n",
-      "PHID-TASK-6fqslp7awofcsqlxxg2u\n",
-      "PHID-TASK-rnr44j25me5v5afzc5we\n",
-      "PHID-TASK-z4gyf5rhh3zawzwg3vor\n",
-      "PHID-TASK-kecuajpgt5rzhwm6db3u\n",
-      "PHID-TASK-lpapd5tkeo4vhxavi7m5\n",
-      "PHID-TASK-in5fzrgdn5o7nk5vzdej\n",
-      "PHID-TASK-wnlasenua7iwnzhgajgz\n",
-      "PHID-TASK-6fktzxq6di35ahdf6gf4\n",
-      "PHID-TASK-oeqdjrsyoun6qoc3mib4\n",
-      "PHID-TASK-dit32vs3thukzudalngg\n",
-      "PHID-TASK-bid73jyquzumwcuffblp\n",
-      "PHID-TASK-aphzv5yajhoubslqbzir\n",
-      "PHID-TASK-z73kr2qs67okpafmzjog\n",
-      "PHID-TASK-es2flh3nsdngj3dxtuxi\n",
-      "PHID-TASK-ia2t3u7dnvzwa74mm3vr\n",
-      "PHID-TASK-svug2yxishcvki3vxn4q\n",
-      "PHID-TASK-xsaz6kvx37q5kaxfiw5l\n",
-      "PHID-TASK-wwlsmm4fnvqjdssb7g4d\n",
-      "PHID-TASK-vis7xnmoa7ngc2i4ds2i\n",
-      "PHID-TASK-avc3fsxulmn56uqgbsy6\n",
-      "PHID-TASK-vemzxauwwwilvulip65t\n",
-      "PHID-TASK-ssrgubmui6ycz46f7lkd\n",
-      "PHID-TASK-4hux64flsouxqgjibleh\n",
-      "PHID-TASK-xyg7preywhwlpczuaps6\n",
-      "PHID-TASK-gwksqe4mofbzkamj67mf\n",
-      "PHID-TASK-i6f5p5xjfmxdo6ubzpmu\n",
-      "PHID-TASK-ud6rksuxulevqjsfqs6h\n",
-      "PHID-TASK-rvrst7lvd6twcpeipdkt\n",
-      "PHID-TASK-sjjvxqyu5lvsgdnholi7\n",
-      "PHID-TASK-brb5wektguex52kczga7\n",
-      "PHID-TASK-4xuz3vb5yze6xii6usyj\n",
-      "PHID-TASK-kvdgcfvnalphobirayqv\n",
-      "PHID-TASK-33n5y7ewqlbefwxwacox\n",
-      "PHID-TASK-qpvwyqg5nibzkozzdov5\n",
-      "PHID-TASK-7bui5nacoyzpq7m5e4vx\n",
-      "PHID-TASK-ocna2wajo3o5voxuppid\n",
-      "PHID-TASK-tvsxq36upc6ipnvhxpyk\n",
-      "PHID-TASK-wedvkdl2s27csm5sxz7t\n",
-      "PHID-TASK-klrivpj5pu4qmrhtcgbi\n",
-      "PHID-TASK-dpkxtqdack6wacscxvhg\n",
-      "PHID-TASK-gbm6kyiyozz73ztd6xzq\n",
-      "PHID-TASK-idjdigelfjcuvhcx24zy\n",
-      "PHID-TASK-xylt7ym6cdzsnco3r3ty\n",
-      "PHID-TASK-vs6adtg7gilhg5r2g74x\n",
-      "PHID-TASK-qwinndvqnthzbul47nb3\n",
-      "PHID-TASK-ifh6gryuu6hee6pcadvb\n",
-      "PHID-TASK-aowfgq4eh3wcjsqyftty\n",
-      "PHID-TASK-wi6gwfwlbpwko4ows4b5\n",
-      "PHID-TASK-juxrg4k7aci5xpwlvsaq\n",
-      "PHID-TASK-vbh2rbaxi3v4g2vosvk6\n",
-      "PHID-TASK-poqv6admiczpvguuyu43\n",
-      "PHID-TASK-2i2pvcby76cfowf624hh\n",
-      "PHID-TASK-xvbh6q43vypy6tjr3wjo\n",
-      "PHID-TASK-zg6asep6oadhz6pkrf4o\n",
-      "PHID-TASK-yokifd7zmqwcieiz3iiy\n",
-      "PHID-TASK-ahjlajk3zasbqo4br4bs\n",
-      "PHID-TASK-d4phvcwb6pak5wn2vbdh\n",
-      "PHID-TASK-etdxsdkmhg4aoyrvdmmw\n",
-      "PHID-TASK-wgr5qefyrk6vxixqgywz\n",
-      "PHID-TASK-3h7v3emjhhqinh5o5aqf\n",
-      "PHID-TASK-nuh252st2e54ff56mbpe\n",
-      "PHID-TASK-t6h3rucl4ojovdzxkq66\n",
-      "PHID-TASK-3ew3gilga74djx2te24b\n",
-      "PHID-TASK-oqjy24dqtbqambra54dm\n",
-      "PHID-TASK-jwf46mqjltex4ny7fpad\n",
-      "PHID-TASK-mx57agjpr44kackrkfz2\n",
-      "PHID-TASK-pxbsw644f45j6giahmh5\n",
-      "PHID-TASK-inyop7q4zxzxlulleamf\n",
-      "PHID-TASK-olrhjl5ydsytkfv6yzoo\n",
-      "PHID-TASK-3d44p7lu3ycz3cvuwxqd\n",
-      "PHID-TASK-yvfkvibbvk27rfmuao7p\n",
-      "PHID-TASK-ijjtl5hsv4igmy4k6sej\n",
-      "PHID-TASK-tghru467viza4owq4m3v\n",
-      "PHID-TASK-fcytooow3nd5c6cwcwl6\n",
-      "PHID-TASK-mcleu5c4oborex7k7xit\n",
-      "PHID-TASK-s2gl74yfgu2t3qm3jv3q\n",
-      "PHID-TASK-fyok2cjpctqiorpfldvp\n",
-      "PHID-TASK-krz3dz5vyj2jo6pufnnb\n",
-      "PHID-TASK-hekxaxmddcora46opa6e\n",
-      "PHID-TASK-wg4if5a5jfs6ciuoa7x3\n",
-      "PHID-TASK-dbgv7dfw47acis2f72rd\n",
-      "PHID-TASK-53dxg6rsj6uqcm45wss5\n",
-      "PHID-TASK-horg3ds56xoznfv445i2\n",
-      "PHID-TASK-fl755yo3ekdckavdhb4b\n",
-      "PHID-TASK-4r4lbhkxqhogotfzas57\n",
-      "PHID-TASK-fz3rgh4ljjpvwe3terlp\n",
-      "PHID-TASK-w26cnf2uzn6whhzpd4p5\n",
-      "PHID-TASK-fgo5ntod4pt7hex3reuf\n",
-      "PHID-TASK-ibvdz6zkyuw2mud34vwr\n",
-      "PHID-TASK-o6hvv37kdmfpbrbf7mjf\n",
-      "PHID-TASK-veppenlnczvh4hbbxwsw\n",
-      "PHID-TASK-bsoljznx4zww5csa3zth\n",
-      "PHID-TASK-tvk7p5y33xg5evlkkbgh\n",
-      "PHID-TASK-4pnt5quh7n4hpe7ffu3t\n",
-      "PHID-TASK-2ub5t2oupkp4z4qo32ce\n",
-      "PHID-TASK-4itryfnmayohwwozkuws\n",
-      "PHID-TASK-calntit5bgsnncojx237\n",
-      "PHID-TASK-kuzyc5hs4c2r4b2fex4f\n",
-      "PHID-TASK-ayjpiyllgpwjsso4fzvt\n",
-      "PHID-TASK-m2dyfyycv5j7jnwg3sup\n",
-      "PHID-TASK-ydxhivupzag4qu4llhwx\n",
-      "PHID-TASK-gkasmmcbpikhl6gq6kg5\n",
-      "PHID-TASK-z7k6ld4qvfzn2ify7im6\n",
-      "PHID-TASK-ltt3irfuuufns7tetoc3\n",
-      "PHID-TASK-ebhdb6qns6ottyytmzfa\n",
-      "PHID-TASK-s4chuo432xmbozeyirll\n",
-      "PHID-TASK-ydbji5fefbbeiocpl24u\n",
-      "PHID-TASK-z2agxnwfy52lvo6yjxrd\n",
-      "PHID-TASK-3qhhrxr2wofxfssyycod\n",
-      "PHID-TASK-2maqvichtgrs77o35tls\n",
-      "PHID-TASK-pbxss6r2sg7qfrxykect\n",
-      "PHID-TASK-tgo7euxf3cnwhcvmwsfs\n",
-      "PHID-TASK-rorj54kzrfz5yajplzy6\n",
-      "PHID-TASK-lc76yoxati6qqmlqel6x\n",
-      "PHID-TASK-jo6lx3im2dnf4fgrh2cy\n",
-      "PHID-TASK-nuhotkfh44rday75ra54\n",
-      "PHID-TASK-tpc6ler6znj3xz2beohn\n",
-      "PHID-TASK-eril5tvgiad53f3rcpft\n",
-      "PHID-TASK-tlf237apfkoioeofs5ec\n",
-      "PHID-TASK-djoqnd37pa6rtsa7b2iv\n",
-      "PHID-TASK-w2eu52oilk4spsdpzeoa\n",
-      "PHID-TASK-d36xqpcmqmrkpqcgucpb\n",
-      "PHID-TASK-pskrxedevzwi6wzlhh27\n",
-      "PHID-TASK-hqvxg56nlg2toykqmhmk\n",
-      "PHID-TASK-rl6e4brnawmfpf74jcdj\n",
-      "PHID-TASK-nkmn6tlxg6fzvqjixjiw\n",
-      "PHID-TASK-euerogqwtdmzt7fjkkmb\n",
-      "PHID-TASK-h3r2wuw2m4pdrb5ixf7h\n",
-      "PHID-TASK-a465jbds23gplxffpkqu\n",
-      "PHID-TASK-nanbji3vohfklohczwir\n",
-      "PHID-TASK-ipxn4a5xggbelogecqff\n",
-      "PHID-TASK-pi2tzunhpx5y7ayoea2g\n",
-      "PHID-TASK-6syee5vbnlo6bygtishg\n",
-      "PHID-TASK-avk6xwxd7jsix4gwqxoe\n",
-      "PHID-TASK-6vh7i45cbz7znphxlsf6\n",
-      "PHID-TASK-vlaiyo2akniolmqe5tq6\n",
-      "PHID-TASK-aljzsqmks2kf5dymrk45\n",
-      "PHID-TASK-favvfitkxvyu4vmy3ump\n",
-      "PHID-TASK-fldsdjwnv5jvqc2iam55\n",
-      "PHID-TASK-ykvbtj26wyleuw4bnbjh\n",
-      "PHID-TASK-de6dmorszoddddclnd4y\n",
-      "PHID-TASK-yz6cpenppcreusg72zvt\n",
-      "PHID-TASK-hrdmmz7wdsz3xmnhvpp2\n",
-      "PHID-TASK-jakyw4q5ktlmqgd4sv3v\n",
-      "PHID-TASK-mruibaiz5kt46pzezn7l\n",
-      "PHID-TASK-mgnru2nwxtufpuc6lqyx\n",
-      "PHID-TASK-hn23baiwxuaicjnc3ue4\n",
-      "PHID-TASK-umxktvxo76lzoeghwqxz\n",
-      "PHID-TASK-htn2o6dmt6ze2hhaf537\n",
-      "PHID-TASK-ikbuupkdg7jny4q2ih3u\n",
-      "PHID-TASK-gonbe6svndpp6xg5nn7w\n",
-      "PHID-TASK-maorft5oyfrh3mtkgplv\n",
-      "PHID-TASK-zt2vp3ws2fthuoczhtcs\n",
-      "PHID-TASK-zvpdqkuywxev3x3oy6sk\n",
-      "PHID-TASK-fc6sg7pcqin3kmtv4x57\n",
-      "PHID-TASK-bypr3rbgyguddodinker\n",
-      "PHID-TASK-ax4pkg2fcq3uwnfjn5h5\n",
-      "PHID-TASK-rzacfnoggbzshwb2qnc6\n",
-      "PHID-TASK-cj43kd2u4kzkuq6rlhnu\n",
-      "PHID-TASK-j4lztgmjyrotthez4ft5\n",
-      "PHID-TASK-eedu2jxaz76eztsst6ep\n",
-      "PHID-TASK-dhjt3sejejdufp3ya2co\n",
-      "PHID-TASK-weyb3zctidhjrppnilwj\n",
-      "PHID-TASK-2j6ctllml6qqxhzmqlmr\n",
-      "PHID-TASK-6uqz7k3i6hhy6r5mf4qh\n",
-      "PHID-TASK-6d6mtcjbaxy3ev26rxls\n",
-      "PHID-TASK-karzxpqg6fmjzovu77r7\n",
-      "PHID-TASK-3ngsdaq55c6cqyub75es\n",
-      "PHID-TASK-yvxmfw4svpxfoy2mq3xe\n",
-      "PHID-TASK-atyu2v5fwwehteymmmkf\n",
-      "PHID-TASK-xbi4z4qhqpsbwxzbb7j2\n",
-      "PHID-TASK-ovg5r2xmn4fehf7ofjhg\n",
-      "PHID-TASK-bhshtaaxwx36iiznlkm2\n",
-      "PHID-TASK-b3kpqkztod52q3bqpgcc\n",
-      "PHID-TASK-754mi2navz4pvonnspxh\n",
-      "PHID-TASK-njvhn6axgtv4xkldtkx2\n",
-      "PHID-TASK-ovfsitu3qtht2esmfi2s\n",
-      "PHID-TASK-qrgadp2mt3qhvw2auoa4\n",
-      "PHID-TASK-lb7abq7fkyxs3qzwp4ty\n",
-      "PHID-TASK-wob6rhplaqtaaqqwjmgd\n",
-      "PHID-TASK-gqozvzrj5ka3lgyouwvn\n",
-      "PHID-TASK-vjvfdsbkvnnffz3rb6r3\n",
-      "PHID-TASK-6yatmdhnokanuospfimc\n",
-      "PHID-TASK-rlgq63dcwusayyjqcpor\n",
-      "PHID-TASK-5oldmu57nfk4gdllhb7z\n",
-      "PHID-TASK-qrcwbd4n7nqvsvfbykcb\n",
-      "PHID-TASK-ltzaf5hgb6yn3qi7gdwt\n",
-      "PHID-TASK-w3w62aq46ybywp76vzom\n",
-      "PHID-TASK-xjgn5e55ct4mrwoaox2n\n",
-      "PHID-TASK-q6dmhbtud5dlan7xkm5f\n",
-      "PHID-TASK-ygke3aatutel76h64y5d\n",
-      "PHID-TASK-6tpy6ex557ljdilowdac\n",
-      "PHID-TASK-gpv7ztvo3m727pmopcq7\n",
-      "PHID-TASK-zr2hewhivqrgrbnvcapd\n",
-      "PHID-TASK-odieilz34gnzoz67vumw\n",
-      "PHID-TASK-u7bebesywdz3nbtymuyr\n",
-      "PHID-TASK-3nmcqmdcnvrslmvnpgyx\n",
-      "PHID-TASK-nptn4dym6znmjhge2meh\n",
-      "PHID-TASK-3mzdvk7doccla2cgipwj\n",
-      "PHID-TASK-k3ijb4t7vtqm2fvl7dqa\n",
-      "PHID-TASK-u4b7k3vc55d23eoi7lfv\n",
-      "PHID-TASK-ppoinlj2eyh5xj7jyhin\n",
-      "PHID-TASK-zu3q7ugqbcdtlalzbdir\n",
-      "PHID-TASK-c67owxdoizewmtq2qqq2\n",
-      "PHID-TASK-xzt7v3b2ore2q4iogeui\n",
-      "PHID-TASK-i5l4tj3jbqlfjjgj2xtx\n",
-      "PHID-TASK-5jyjadx572ehzjtstm2i\n",
-      "PHID-TASK-gm7mlj7ylnonhtpcmhmc\n",
-      "PHID-TASK-tndk34qrdqsecj3chsun\n",
-      "PHID-TASK-i6cv3vliogwuderqbjnw\n",
-      "PHID-TASK-y2smkmxkc74umzi22ziq\n",
-      "PHID-TASK-devcsvnwd5brcea5luka\n",
-      "PHID-TASK-p2n3tks426uods6v37cf\n",
-      "PHID-TASK-wf4a2uikjvfox37upsq3\n",
-      "PHID-TASK-yaappft5pc7quebc2sf7\n",
-      "PHID-TASK-4i77geu65qzvj7wexwob\n",
-      "PHID-TASK-my7qaki5z5rpjdhjrelx\n",
-      "PHID-TASK-tb4dfoj5ivzds3d5vjbf\n",
-      "PHID-TASK-adbbasada34enlaaq6ns\n",
-      "PHID-TASK-qzi73sz5voocgvogf6kk\n",
-      "PHID-TASK-q22fxzgily436ad4iq5g\n",
-      "PHID-TASK-mystbxhb36nxyv6pxcfr\n",
-      "PHID-TASK-dwm6neygnm5atdz5p2ls\n",
-      "PHID-TASK-am2tq4ttmt7ojewwkmyp\n",
-      "PHID-TASK-jp6ugl4t75zwxp4yb5dw\n",
-      "PHID-TASK-fxdptzpzjvmxdqfbxpig\n",
-      "PHID-TASK-rlct7v5aitn3wet7l6e6\n",
-      "PHID-TASK-cbgrzxh5jpcsxgl5p5xy\n",
-      "PHID-TASK-smzjavkfcebgjqkdtqrx\n",
-      "PHID-TASK-trv3cartgmv24xouxumz\n",
-      "PHID-TASK-lorkde4zqpoazowbiim6\n",
-      "PHID-TASK-ymkat6i32jrdnouhpmiw\n",
-      "PHID-TASK-vthqyhkr4mcwanonthu2\n",
-      "PHID-TASK-mfexrt4v3gjwo4jczoeu\n",
-      "PHID-TASK-bklb3mjjhzmtwofxaf4c\n",
-      "PHID-TASK-3b3ojih2e7wkq7l3upwi\n",
-      "PHID-TASK-o7g3xrsatafdlookojvh\n",
-      "PHID-TASK-6a4gkdcnicitblhp6cug\n",
-      "PHID-TASK-mgc6io5oxbkpzoctvybg\n",
-      "PHID-TASK-ytqjgzoe2nidan525q6p\n",
-      "PHID-TASK-44radwd6pkgnkplpyiul\n",
-      "PHID-TASK-th6xciyktmum2yvdvsqy\n",
-      "PHID-TASK-alyz2tg2s4hlxhbv3yqa\n",
-      "PHID-TASK-bcsg2progke55h2rhst6\n",
-      "PHID-TASK-7ma6pcpqiiyq3gvijprg\n",
-      "PHID-TASK-sgceljbbtlgbbpr3bdfh\n",
-      "PHID-TASK-z2wr7yxi5vylreuzml56\n",
-      "PHID-TASK-6xivramwe724jwphgukh\n",
-      "PHID-TASK-q3v5q4q6bifjgxghffaq\n",
-      "PHID-TASK-txtftm3ohgrpjqzazgnp\n",
-      "PHID-TASK-yllnjqjrkuliux5dxtws\n",
-      "PHID-TASK-bfsjo6ol2jmfu3gdf4ch\n",
-      "PHID-TASK-tn6apoz6stp2eozgwscp\n",
-      "PHID-TASK-dyhspvuz6dvlmjei7r7v\n",
-      "PHID-TASK-dgi4ucdvhwjzbauoa7td\n",
-      "PHID-TASK-k43bzyrhgig4srkamrde\n",
-      "PHID-TASK-jvpgelxqydhjqfkhkgas\n",
-      "PHID-TASK-dmz6g3cracqeyd3hxrar\n",
-      "PHID-TASK-4c7jfgdvdgsa7tz3aom4\n",
-      "PHID-TASK-efd5wnljemqy75ubgwoi\n",
-      "PHID-TASK-jazdgxdcnzvf2vvkoqay\n",
-      "PHID-TASK-ndrderb5cpy5obe7r7so\n",
-      "PHID-TASK-2nhg6abdnwgx5uutzfus\n",
-      "PHID-TASK-k4lzd6fndz3snhg24las\n",
-      "PHID-TASK-fa3dg2ag3ccgjplogzop\n",
-      "PHID-TASK-ljxem5cmodalpwa72kg4\n",
-      "PHID-TASK-wvgg7vhdge7chox3fyjo\n",
-      "PHID-TASK-c3wbsdob4ioii2vvg62w\n",
-      "PHID-TASK-7ahnfikr3ud3nwuglytr\n",
-      "PHID-TASK-wzimuyoyzpmwzhvmicic\n",
-      "PHID-TASK-btez3p46ypsfjdbg3yny\n",
-      "PHID-TASK-gd5v26ccraeduoxxlbju\n",
-      "PHID-TASK-pfavb4dwppjl5cul5xfr\n",
-      "PHID-TASK-dgmfpphgdhqlrv3bwalq\n",
-      "PHID-TASK-gt3d3w3roul5snkreii4\n",
-      "PHID-TASK-cttjkncimnkmzpg2rgta\n",
-      "PHID-TASK-u5v4rso2epl4jpiezw4u\n",
-      "PHID-TASK-b7f2axjx5q6kogc6seqp\n",
-      "PHID-TASK-2mi7knu2wbwwklhttype\n",
-      "PHID-TASK-54g2ow3ld3vtvnaijiwz\n",
-      "PHID-TASK-kybodyavmyonstmof6sr\n",
-      "PHID-TASK-w6vvfriu2l3mqu3xrisn\n",
-      "PHID-TASK-xfgiug37am4goz3ewbs4\n",
-      "PHID-TASK-gpu6rhupzadk44q3zvmd\n",
-      "PHID-TASK-fz5qvkff7hb32uaxnpl7\n",
-      "PHID-TASK-uubavjgv7r236ouenxi3\n",
-      "PHID-TASK-c2pwlmpgr24oxvj7ruka\n",
-      "PHID-TASK-amav3irppf34v275xo4q\n",
-      "PHID-TASK-xbihpnurfxbt3vghqoxr\n",
-      "PHID-TASK-ss2itizzzz4vdy6z2bwv\n",
-      "PHID-TASK-k4uqhsrhnkkuz3d2z6l6\n",
-      "PHID-TASK-jzepbqpzu7s7bfg4k2ua\n",
-      "PHID-TASK-6tdi4t2hiwd4kw4wdp3k\n",
-      "PHID-TASK-5ezr4schgjcznl2chb3p\n",
-      "PHID-TASK-oz4sidkwsjedlisknc5h\n",
-      "PHID-TASK-tmvxleqap5uqab7s5tju\n",
-      "PHID-TASK-c4vkf2igh4ozkrhmdcdd\n",
-      "PHID-TASK-ruct6x62hxyefsmpylp6\n",
-      "PHID-TASK-aujnfu5wgjys4i7m3tqa\n",
-      "PHID-TASK-7xdz6csv454jmjt43l3k\n",
-      "PHID-TASK-ku4zjzbgxbemhv6sicxc\n",
-      "PHID-TASK-j57p7ueywyekpmhxkqes\n",
-      "PHID-TASK-ajsfntti2ybnqjqeqxfs\n",
-      "PHID-TASK-bumkxu7r6tdc2iyjok4e\n",
-      "PHID-TASK-wdm6ddtjkbpjvqclln2i\n",
-      "PHID-TASK-n7737xkjqezrnwwaava3\n",
-      "PHID-TASK-f22y5n2hutfcuixay276\n",
-      "PHID-TASK-2xyzi2meu5y5iozdxh3z\n",
-      "PHID-TASK-6nrh4cee4ez6cwykweo5\n",
-      "PHID-TASK-4ottk5yqyncneqh7goju\n",
-      "PHID-TASK-q6etjfxib3te52jrdbqh\n",
-      "PHID-TASK-f54j3i3yobgyvswaikfo\n",
-      "PHID-TASK-a6xscw7mjvhcbwgufh5y\n",
-      "PHID-TASK-zfww4nd7axazvbfkd7qj\n",
-      "PHID-TASK-a6lxhzu2xrx5tgje6umc\n",
-      "PHID-TASK-h57f3cph7qycjnbwjvnw\n",
-      "PHID-TASK-apdnw6jklub4mtqzckmn\n",
-      "PHID-TASK-zpvndgxny4i6jsgnxaga\n",
-      "PHID-TASK-uuriwo6q3mdhjyt6egwi\n",
-      "PHID-TASK-tstjv3noyoaah6bfdmns\n",
-      "PHID-TASK-7u7csbjslb6fdxkpcs6y\n",
-      "PHID-TASK-hc26warwwz5ylqujc3td\n",
-      "PHID-TASK-slnchzhtiw4uoxg47vla\n",
-      "PHID-TASK-r75ffyh3qiqooawo44eb\n",
-      "PHID-TASK-2gqmb4cvp2njgfweg4mi\n",
-      "PHID-TASK-ul25dgz4nyeridoqmsqg\n",
-      "PHID-TASK-a56uzvltsvz2gw6egtar\n",
-      "PHID-TASK-exyn4bfiq2igip2xy6r4\n",
-      "PHID-TASK-ajr6uvwq3l2hdzyqjden\n",
-      "PHID-TASK-ob7cxxrhd6d3aeazrujm\n",
-      "PHID-TASK-vav3ssxyt7puz6mth7ck\n",
-      "PHID-TASK-ryyonehlcnqdc46zjg2w\n",
-      "PHID-TASK-4q75ixwk7yvcayzud2qd\n",
-      "PHID-TASK-sk3uspo3yfsnwm2o672b\n",
-      "PHID-TASK-jhlniwxu2ykuroltxk3l\n",
-      "PHID-TASK-6vicxrcuqmyqgizvbnop\n",
-      "PHID-TASK-l2eaq3bdozrt2dgpbncq\n",
-      "PHID-TASK-e7xy2ghygeqe5vvk7vir\n",
-      "PHID-TASK-2gmwjvi3zn6cswyfyegi\n",
-      "PHID-TASK-mq355eomr24cmluqc7dh\n",
-      "PHID-TASK-2lufxleaemvynes2b2da\n",
-      "PHID-TASK-xtyrp3i5752jen7uoe6m\n",
-      "PHID-TASK-2aj3mfax5n7tlrsztfhy\n",
-      "PHID-TASK-aqea5euyvi5ekuwq3kig\n",
-      "PHID-TASK-hiumuha3tc6xqypqt2lz\n",
-      "PHID-TASK-nsc6gcp3vvg4tvl6tyfb\n",
-      "PHID-TASK-xpyddbk7oe25b7f7bpp3\n",
-      "PHID-TASK-cke5acua2kmqpq2rtiv4\n",
-      "PHID-TASK-gf44zknlabktvyuiobnc\n",
-      "PHID-TASK-fmsq2a44unt5qvw7fvjz\n",
-      "PHID-TASK-cek4b33i7kzn3d5tir7d\n",
-      "PHID-TASK-v5mejtdved3hadzpnblg\n",
-      "PHID-TASK-bbwwebnria5w3khcdb2z\n",
-      "PHID-TASK-d3f2ddd27saapnkqzblp\n",
-      "PHID-TASK-6tdn24gf46lji7yqfvl2\n",
-      "PHID-TASK-jtaql5mrtvhb43vajwv3\n",
-      "PHID-TASK-ttm23g3exfsgbjvupqdx\n",
-      "PHID-TASK-i3kcektvabsqugyb5tzv\n",
-      "PHID-TASK-ux4izidb7xrrwhvej2xp\n",
-      "PHID-TASK-ly2xm7tz73tvksvhmtyz\n",
-      "PHID-TASK-kvsbzknbe6m5oydwjk6y\n",
-      "PHID-TASK-ton3dd6uf2z3sfe3n2k3\n",
-      "PHID-TASK-gax37c3j4qvaskyhk55t\n",
-      "PHID-TASK-uqidpcw3y4xgb5ynjwev\n",
-      "PHID-TASK-3ytipv46bzm44jpqmwoq\n",
-      "PHID-TASK-ivhyp5yplrphnwughsqu\n",
-      "PHID-TASK-hydd4sggtsrxlgqhafqc\n",
-      "PHID-TASK-6k6omehrnjj3d64g3xkp\n",
-      "PHID-TASK-qsgzi7766f5xj7zdn6hb\n",
-      "PHID-TASK-2qype6jzcuqvgj55crv3\n",
-      "PHID-TASK-mu7m2pj54l427crmnupd\n",
-      "PHID-TASK-jvbmuzupmyildaswp3ax\n",
-      "PHID-TASK-75c273bypsftlyrbr3cc\n",
-      "PHID-TASK-vr2jeooanda24ls5knww\n",
-      "PHID-TASK-yjkqv35zcxvtirgx56ds\n",
-      "PHID-TASK-drb6zxeswawnaqold54q\n",
-      "PHID-TASK-qyxlhx72vvvsjxiz5mxk\n",
-      "PHID-TASK-gcvicv5c5il3dfwvq4z6\n",
-      "PHID-TASK-btqaquo52pvsfg5ytjrc\n",
-      "PHID-TASK-54zoeovhyceutq4h2rxj\n",
-      "PHID-TASK-bxfy5lj3p2kmooagyw4k\n",
-      "PHID-TASK-bzfy62f6eeawy7qsikz2\n",
-      "PHID-TASK-r3cecfzae44mq2jgxqtv\n",
-      "PHID-TASK-j4syqnzwdunhoucwx6o6\n",
-      "PHID-TASK-vsa4dipmuhxhvfjv3ueq\n",
-      "PHID-TASK-rq2tsnu6ypd4j65ev7c2\n",
-      "PHID-TASK-ot6puhxaw7ez7zuaeuyr\n",
-      "PHID-TASK-e52bbyzcqb4xr73axz3g\n",
-      "PHID-TASK-jqy4wf5ol4o3dp66hs7r\n",
-      "PHID-TASK-cchu7wayqp2w3m4ikxkf\n",
-      "PHID-TASK-zkqsllah4f32kfkyu6pq\n",
-      "PHID-TASK-raetvmzuudiefybcm2if\n",
-      "PHID-TASK-fqt5fy3rkv2cyagloqrl\n",
-      "PHID-TASK-cvrmtrl6akf6grx2t2dt\n",
-      "PHID-TASK-7oxigo4kmioch62jccio\n",
-      "PHID-TASK-rw22m4geg4i4wedyx35p\n",
-      "PHID-TASK-cv2eddejijgeuiyzx5iv\n",
-      "PHID-TASK-4ygvi66vjgjggrrbm2gv\n",
-      "PHID-TASK-esphifhyt57uf6xcfxuh\n",
-      "PHID-TASK-bwuzjaia5wetefisy2ta\n",
-      "PHID-TASK-2z4m5xpg5gzvx6kbldfe\n",
-      "PHID-TASK-47tdq27eh5j4qgr4lw5p\n",
-      "PHID-TASK-lldcsju4qcxyd4jmidkt\n",
-      "PHID-TASK-n7gptyps7udhncfic5rt\n",
-      "PHID-TASK-gxlesrzwrsipkfsxba4o\n",
-      "PHID-TASK-jykflci4lybdcwkdegx7\n",
-      "PHID-TASK-zlrtgjuxyb4v4l2qepry\n",
-      "PHID-TASK-dzuii7n6goxb7ffjhlad\n",
-      "PHID-TASK-rwdzpvdya3fyeweyik45\n",
-      "PHID-TASK-qwmhk54ep4zitmtvbaik\n",
-      "PHID-TASK-7vr2tsadkbk7lzyzolas\n",
-      "PHID-TASK-khmajutgdejtygs4iuzr\n",
-      "PHID-TASK-wkopxt22hpjopb4jwgk3\n",
-      "PHID-TASK-g5vhskgl4jngc5bjv6k7\n",
-      "PHID-TASK-z2cdsxjpkxttsbnu4d2x\n",
-      "PHID-TASK-h6kkxvcriuqwp7klykw2\n",
-      "PHID-TASK-nepuoz3eghdbacybz47v\n",
-      "PHID-TASK-g6mdoxrevyqbrazocz2q\n",
-      "PHID-TASK-kpx6sqi7fes7jlx6flt4\n",
-      "PHID-TASK-nhi52laxjrwxyxxoh46r\n",
-      "PHID-TASK-r2i2uzlqlwknth3ox5rg\n",
-      "PHID-TASK-nnvtoxoopp6h7zbzqq7s\n",
-      "PHID-TASK-rh7iz42inbmpgpuz2l7u\n",
-      "PHID-TASK-bodj4j2hdcdjgi2sbtmy\n",
-      "PHID-TASK-4tmd7nww2cyfj5sek6yq\n",
-      "PHID-TASK-3vh3dwgpiyxwl4qobayn\n",
-      "PHID-TASK-jzxawxvcg5luenehopjn\n",
-      "PHID-TASK-hlm32lc3bwvjx3khjhox\n",
-      "PHID-TASK-ybjzemdynryfg4brsgpi\n",
-      "PHID-TASK-od4vkgjhilutsh6eoi2o\n",
-      "PHID-TASK-sofl3tiyrxpjkqmu6grn\n",
-      "PHID-TASK-lrcob3z2uqlumi23wzcg\n",
-      "PHID-TASK-okkhp45bypa46o6v5bzh\n",
-      "PHID-TASK-hpovu36fcfgevlvacc57\n",
-      "PHID-TASK-4dujg5dey76ud6rkyyfy\n",
-      "PHID-TASK-cxydx5rlo2r5gmbuelnf\n",
-      "PHID-TASK-4q4qvm4gto65caiusmb3\n",
-      "PHID-TASK-lj5fifjrup6bhxud572h\n",
-      "PHID-TASK-ss7w322z7ikgu5wkin5c\n",
-      "PHID-TASK-dbjwk2354ghy4uqtyvgu\n",
-      "PHID-TASK-eftf2krwbij53usp7qbq\n",
-      "PHID-TASK-ar46xe5css6dnxzqbtde\n",
-      "PHID-TASK-jka67woodw5fn6qicshn\n",
-      "PHID-TASK-3rsluniow7ulmwxctugw\n",
-      "PHID-TASK-etughy4urwl7bhwydk2t\n",
-      "PHID-TASK-3edkedybbeebfer2rcap\n",
-      "PHID-TASK-etsrlkklzald7ybkqh3u\n",
-      "PHID-TASK-h7ssc4ozwop6qczla4rr\n",
-      "PHID-TASK-rataorpnc6452rqcpgfh\n",
-      "PHID-TASK-d66zsm26kiowezoool57\n",
-      "PHID-TASK-l7c73muvr5qk2q5p42wr\n",
-      "PHID-TASK-urg73yoypnuiks7zst4o\n",
-      "PHID-TASK-53mqogsdiodyzah24cx5\n",
-      "PHID-TASK-obhstlqgs73vks43hy74\n",
-      "PHID-TASK-zlt7qdys5zthrlly644p\n",
-      "PHID-TASK-byaxrg34aq533rbmohda\n",
-      "PHID-TASK-aypymh3waspkktjfjzyq\n",
-      "PHID-TASK-pz4hu5kupf3cy6rgi2hl\n",
-      "PHID-TASK-k2ubvggwznutod3v37na\n",
-      "PHID-TASK-mu5hvfs3z4bnfcwufhcz\n",
-      "PHID-TASK-7hymyhokel2tmuz42xo3\n",
-      "PHID-TASK-utdxlw7pghyukf2ujhmo\n",
-      "PHID-TASK-hcc3ucc2gxwo6jb557m7\n",
-      "PHID-TASK-q6pn4p5ppytwmrilrwfc\n",
-      "PHID-TASK-dutiulezx3dwzyt4n3jd\n",
-      "PHID-TASK-k3ogdcpxt3y5m7tvnsj2\n",
-      "PHID-TASK-qc2hzb2zgpy4pqax7p6j\n",
-      "PHID-TASK-vnz2yl4fdnpwhagmzdlo\n",
-      "PHID-TASK-jnj6pwbdr63nh5prebtr\n",
-      "PHID-TASK-yl7i3kirybrkgyab56tk\n",
-      "PHID-TASK-ilakhjhigyp4sxfadq5q\n",
-      "PHID-TASK-a2g47wnz3wqen23fp6b7\n",
-      "PHID-TASK-oh5g652d7wxhvdg5yg3r\n",
-      "PHID-TASK-4hfyvqkoxqfkrsf53qio\n",
-      "PHID-TASK-2kfniuyxuldpuiatpfod\n",
-      "PHID-TASK-ksttu36zsaoc7fxnzt2x\n",
-      "PHID-TASK-clc63qvmswgkzbw33tkq\n",
-      "PHID-TASK-mxb522dezlpdexpuwpqh\n",
-      "PHID-TASK-anbufyvs4yecgr5utuge\n",
-      "PHID-TASK-uccw7yqukr3actwcyct3\n",
-      "PHID-TASK-yfp5mfkl2pgmbsvfh5vf\n",
-      "PHID-TASK-7piycxpmx56ohmyj2zuk\n",
-      "PHID-TASK-ryivokqumebwl4y5m3ua\n",
-      "PHID-TASK-kpq3munittovusy35opj\n",
-      "PHID-TASK-jvcrri6ivphdq3gs6cdy\n",
-      "PHID-TASK-ysuesdqax3nucpqxzzrl\n",
-      "PHID-TASK-gztnciutz4zkajephs5s\n",
-      "PHID-TASK-nfo3xiyndruo5aeqves4\n",
-      "PHID-TASK-rjxemhifa3x2566jx3he\n",
-      "PHID-TASK-tdi5kkh4rg6wvf7cam7m\n",
-      "PHID-TASK-6qteafzaet5hssww25zp\n",
-      "PHID-TASK-kil3chqyjneigkvf34lu\n",
-      "PHID-TASK-6goh2k74apor363cgxbh\n",
-      "PHID-TASK-j3ofm67egbuxxvm3t7el\n",
-      "PHID-TASK-sunqzkbtk2xufhfoaa2r\n",
-      "PHID-TASK-m7dvl6wigpdkychmqdou\n",
-      "PHID-TASK-mi6bk4kxywbgiufipreu\n",
-      "PHID-TASK-u6ckhkexjtiftpwrkmpc\n",
-      "PHID-TASK-5asnk76tj5m575vlprx3\n",
-      "PHID-TASK-3bmha7jwdg75jxh75rnj\n",
-      "PHID-TASK-lerurhal64ijhdssrwjz\n",
-      "PHID-TASK-umbcx7pdcw56w7fx2jhf\n",
-      "PHID-TASK-zooes6fkunmcss2rmnar\n",
-      "PHID-TASK-6welbf6ni6cfb2mlnvar\n",
-      "PHID-TASK-monj46bisauzpolgauzi\n",
-      "PHID-TASK-5mt4qblkmzcmmaz4z7cw\n",
-      "PHID-TASK-baxx2wdr226fyxswg265\n",
-      "PHID-TASK-ktvckajg62tqaio3n4gv\n",
-      "PHID-TASK-675e74bf6yv4vzpihvax\n",
-      "PHID-TASK-cm26etfhdyviprbpebfm\n",
-      "PHID-TASK-ywadwhslnfchsbahscag\n",
-      "PHID-TASK-63zjaemkihhdn67rqs2l\n",
-      "PHID-TASK-426ekcmockyid64cqfva\n",
-      "PHID-TASK-qsx26ngxjl4avpi2ln2b\n",
-      "PHID-TASK-cidep33c4c5o3tej2ipd\n",
-      "PHID-TASK-6hephrfe43g3sajiaspv\n",
-      "PHID-TASK-v2ol64y3mialrzwjykor\n",
-      "PHID-TASK-ie5f4kyk73zuc2topaj7\n",
-      "PHID-TASK-snvwps4elfr6ehb3bg2z\n",
-      "PHID-TASK-tnxcsv7yi4nvi2fk6b6r\n",
-      "PHID-TASK-4res6cs3y6litn77e77o\n",
-      "PHID-TASK-kok6e7cmusz47p2lyu46\n",
-      "PHID-TASK-ijwoo3bfloiiovk2zi4r\n",
-      "PHID-TASK-g4umm5xifvnyjhvuzvzx\n",
-      "PHID-TASK-5ufggm4c7s4fufhtimjv\n",
-      "PHID-TASK-mgagqv36esykujdeqdd6\n",
-      "PHID-TASK-hc57wasluvhgws762zjc\n",
-      "PHID-TASK-kcbyh6alaid3ganxbdh7\n",
-      "PHID-TASK-ztbhkhlbjf2yhr7pllu2\n",
-      "PHID-TASK-mi4dx3mxevunni7ssqg3\n",
-      "PHID-TASK-mvlq3qqfqqmazl5ytcnb\n",
-      "PHID-TASK-xliej5372d5wtuol7oum\n",
-      "PHID-TASK-vdncadf63tpumxtunpkp\n",
-      "PHID-TASK-l2puvf36mj2rean2tzju\n",
-      "PHID-TASK-3skoc3yrmrphd6vlwwdo\n",
-      "PHID-TASK-jc73aooy3axdug4ckbsa\n",
-      "PHID-TASK-5oa3p2m62q7vlwtaworj\n",
-      "PHID-TASK-c6rxgzyci66c7ffcr5dz\n",
-      "PHID-TASK-kyyxvxidfguxqxef3flo\n",
-      "PHID-TASK-4tywejgljpprmmm7tbbh\n",
-      "PHID-TASK-iyyzwzlyhrbyhzbudijv\n",
-      "PHID-TASK-iezltl5j2pc2evrnk2x6\n",
-      "PHID-TASK-hsyburiakp2zdvz34qoh\n",
-      "PHID-TASK-2iqe4d6ln6247lyafirs\n",
-      "PHID-TASK-5sccvnyuy43bzxbyv7n4\n",
-      "PHID-TASK-pgkoq2ygryfod5gjbheg\n",
-      "PHID-TASK-7c7nuth53wqtbnm6qaa2\n",
-      "PHID-TASK-upmb4s4arsl5sfm2zcbh\n",
-      "PHID-TASK-zsenbwls7ebypri26j7n\n",
-      "PHID-TASK-qmfoshrg3djlltdfiuev\n",
-      "PHID-TASK-frawcbm336hvwpzabjlz\n",
-      "PHID-TASK-dokvmwmoyy5xh2fmdf7t\n",
-      "PHID-TASK-qvglmtpnlcnxuc34bwtp\n",
-      "PHID-TASK-dqkqlyz5zbhrlqk3ihv6\n",
-      "PHID-TASK-xkj5bkkwqzmcktj6whgq\n",
-      "PHID-TASK-ue6vedmhhpltifawbjjw\n",
-      "PHID-TASK-6suiiraatmj5yc6h6pe5\n",
-      "PHID-TASK-h5r6intumxzasr64ard3\n",
-      "PHID-TASK-cq5xz34jat667ipldw3m\n",
-      "PHID-TASK-hhyxloh7waxmrcuezybh\n",
-      "PHID-TASK-mzsciyic2wqa2bvm4hc7\n",
-      "PHID-TASK-iykzkw3bnfenwugca5ap\n",
-      "PHID-TASK-5xquomxdtu6ifmyxtnyo\n",
-      "PHID-TASK-ywep5k7o4fxifohcgdas\n",
-      "PHID-TASK-upmf46g433ncdqqvf7jl\n",
-      "PHID-TASK-a2ijxws7hzmbqlcz7s2f\n",
-      "PHID-TASK-nrc66pgj7y6cxhboa2o2\n",
-      "PHID-TASK-4o73zjiapudkgirgztfc\n",
-      "PHID-TASK-vi6faapr4iunjpanknxn\n",
-      "PHID-TASK-c62cwehj54km2p5gebox\n",
-      "PHID-TASK-fielr75hawu6al7yvwgb\n",
-      "PHID-TASK-hnw54lb3tce7w3w2y7dx\n",
-      "PHID-TASK-bonyuszkfft3v3iimug2\n",
-      "PHID-TASK-fv2akybq3ywgtzliagz5\n",
-      "PHID-TASK-ttqllxkghaqgjfflgrdp\n",
-      "PHID-TASK-fvdvxsgxt5hfh5g5e7b6\n",
-      "PHID-TASK-qwganlrulofurpdkcbyf\n",
-      "PHID-TASK-62x4lmlf5c4o37ouorno\n",
-      "PHID-TASK-zxwfb74rzwpzfsgbjyzv\n",
-      "PHID-TASK-mypudm3323akv2drcpva\n",
-      "PHID-TASK-wfdurzh7jsda4trl4dsh\n",
-      "PHID-TASK-7cay56sblrqfurqj5hno\n",
-      "PHID-TASK-szea6r75prmyfpghqu7p\n",
-      "PHID-TASK-4sadouseu6almebfar54\n",
-      "PHID-TASK-wicmfrektsx4wuuuhcwq\n",
-      "PHID-TASK-qhmfjyurm2j53vu5lrbp\n",
-      "PHID-TASK-d4t2kxc6dwgul6wss43q\n",
-      "PHID-TASK-ppbj4smgqgqx5ararami\n",
-      "PHID-TASK-hqizdzws5eagirsav5rw\n",
-      "PHID-TASK-poy4sfkajyxaov7ad2nl\n",
-      "PHID-TASK-gvnhzkjgz3cv6frzglkt\n",
-      "PHID-TASK-fhkhxz7oi6kric5dekys\n",
-      "PHID-TASK-hsklb2fted77hcl6jkir\n",
-      "PHID-TASK-kinrik6hswrtg2xxwohw\n",
-      "PHID-TASK-ovmfajyzbve3uus6gktf\n",
-      "PHID-TASK-ii2vmdvj7u6fxg2vyxax\n",
-      "PHID-TASK-5nl2agli3yogyhbgab57\n",
-      "PHID-TASK-a6d7zyzurpoea557wxot\n",
-      "PHID-TASK-7fusp4t2k553x5ynkjxt\n",
-      "PHID-TASK-gc45eius7aytam2rlpth\n",
-      "PHID-TASK-x72zymsnartka42zou7j\n",
-      "PHID-TASK-lwdlllmgxfie4lfk6ywk\n",
-      "PHID-TASK-goezj3fhvn2phuamifjy\n",
-      "PHID-TASK-htx2um5fnyusay6ynwua\n",
-      "PHID-TASK-t2avilcwnjfjpdywdken\n",
-      "PHID-TASK-7336trfcokkmlnznz5wa\n",
-      "PHID-TASK-awpfthjrjritxkhujr46\n",
-      "PHID-TASK-omkq3ws5wkkdmzuc3v34\n",
-      "PHID-TASK-k7nxqqgjeodo2osblgev\n",
-      "PHID-TASK-gynefzcsmqruipthvy7i\n",
-      "PHID-TASK-mkys274ty5zb7zz3ixqh\n",
-      "PHID-TASK-i7jndqttvnweqczobiov\n",
-      "PHID-TASK-2didnifgbvsq7sszd23i\n",
-      "PHID-TASK-wawq2es6xnwknziib6yf\n",
-      "PHID-TASK-k7yzoaid7tne2jeioxrh\n",
-      "PHID-TASK-ggojb6ctli2epykmy6k6\n",
-      "PHID-TASK-j4fwj3nkikf5qqbm775b\n",
-      "PHID-TASK-5frqhlvurysfjreie4jc\n",
-      "PHID-TASK-btr4z4bv5sp7jrbg3tc7\n",
-      "PHID-TASK-ihbbvcuqsgulvmjyinx7\n",
-      "PHID-TASK-lhmoss6srr2f2jmg2mip\n",
-      "PHID-TASK-aimwlbodlnjas75xvos2\n",
-      "PHID-TASK-x6dj767aouujxepwm3oj\n",
-      "PHID-TASK-aezkk3hojhat5t2zwuar\n",
-      "PHID-TASK-bnbg6xhq6kx3wi7mwirb\n",
-      "PHID-TASK-sz5lbvh7j7kau3kukcw2\n",
-      "PHID-TASK-y5us6kajeyeryt5odbuu\n",
-      "PHID-TASK-ijstbrdms7lza5yyddte\n",
-      "PHID-TASK-zwrntrbhezfc6nqksazy\n",
-      "PHID-TASK-xlnqf77fujlvuvwewshn\n",
-      "PHID-TASK-yz4c2eic4amw552h2kwd\n",
-      "PHID-TASK-hixyotclnt74wvydoglc\n",
-      "PHID-TASK-kf2l66kfrhge5pukl6ms\n",
-      "PHID-TASK-jt6qre2zwuzp7bltugkt\n",
-      "PHID-TASK-xg7pbllkf35fo5qpa5uo\n",
-      "PHID-TASK-6qda63lpaymzom6tbttz\n",
-      "PHID-TASK-yjzj5bv5ffrnllxzssak\n",
-      "PHID-TASK-ygqki32oghxhcc37oyhf\n",
-      "PHID-TASK-yx3vtjrhpk7db6rdy7sr\n",
-      "PHID-TASK-xbka5x6ezizjtfccyclk\n",
-      "PHID-TASK-izo3tiafzfdz4gvztvz5\n",
-      "PHID-TASK-j2fbmrbwc2pv3om246qs\n",
-      "PHID-TASK-dexoxhnm6p7r5tl42o5j\n",
-      "PHID-TASK-htrpa3kqlb6jcmk4geh7\n",
-      "PHID-TASK-5vqpyeuqy5abgcxggp5x\n",
-      "PHID-TASK-grrxbpfjnax5tx6mcpya\n",
-      "PHID-TASK-7y5kuddivdzl45gvwj6r\n",
-      "PHID-TASK-gyvrffyluoyvwurby4pu\n",
-      "PHID-TASK-5u7yrk6gecrewqxqwwkc\n",
-      "PHID-TASK-cjhmjbqvl2impaei6gum\n",
-      "PHID-TASK-fj2r7bnjbarkjkyc42pf\n",
-      "PHID-TASK-vebbfxury34xj3qnszdg\n",
-      "PHID-TASK-dbp5fnytgn27ydme3c6e\n",
-      "PHID-TASK-iu3lzoun25ro22ahnfsl\n",
-      "PHID-TASK-7mhhjati7jq7vehinugh\n",
-      "PHID-TASK-ffazj5r46gg74oi7gacd\n",
-      "PHID-TASK-vggdj3oaoiimjl76co4b\n",
-      "PHID-TASK-erh6pdj44sgbbysd6pck\n",
-      "PHID-TASK-cwv4uf7sks54skkmccyq\n",
-      "PHID-TASK-hzeisownarrcldmlrur4\n",
-      "PHID-TASK-dxzb43i42p6jkhs4k3pq\n",
-      "PHID-TASK-2fo2vepgfvoop6cua3yb\n",
-      "PHID-TASK-povdwehsnsp3g7l76hmb\n",
-      "PHID-TASK-hiqmkuftu6tynmzgz27e\n",
-      "PHID-TASK-ulr4ihyno7bftkrdq7gf\n",
-      "PHID-TASK-ewm6busofenduqisc4ug\n",
-      "PHID-TASK-zjrtgmgipdtxr4pdqjch\n",
-      "PHID-TASK-utovzemiq3m7agsxe4zz\n",
-      "PHID-TASK-kaupnnwmc22zgqdjwdqc\n",
-      "PHID-TASK-zvw4nqatdijriyfaposh\n",
-      "PHID-TASK-fxbpehdnotnzwpki3qwo\n",
-      "PHID-TASK-dzlegd43ozkumznabj4b\n",
-      "PHID-TASK-o6vqpx64l4l5tkaovklh\n",
-      "PHID-TASK-6ftf7qwnyyvl5eqcv524\n",
-      "PHID-TASK-2o3jcx26svgc5z7twzye\n",
-      "PHID-TASK-rsuk24lv6ttcz4hpew66\n",
-      "PHID-TASK-rpfc6ad3ojppedslirip\n",
-      "PHID-TASK-tth52wedfhhza5omlooc\n",
-      "PHID-TASK-o6lz6v2kc4f7zqt46qrr\n",
-      "PHID-TASK-cn7ribouyrqugmfcsow6\n",
-      "PHID-TASK-ftsn3l6t3sodv3lfszbw\n",
-      "PHID-TASK-ssdjpviwo7nog652sz63\n",
-      "PHID-TASK-l57zuo7fpi4s3unocju2\n",
-      "PHID-TASK-n3cn64gzbt6oqm2bmb34\n",
-      "PHID-TASK-5uojpr32nnknnwpwsv2v\n",
-      "PHID-TASK-54wl37knbm4fkiq6mgrc\n",
-      "PHID-TASK-citqfhmyoebglw4grn67\n",
-      "PHID-TASK-4odvxcpwxrfuqnmkdos7\n",
-      "PHID-TASK-d72tlf3bm27wp2zhe5ko\n",
-      "PHID-TASK-jv3ln2ejw5h3wcq3tixs\n",
-      "PHID-TASK-ryz7t2wtrhqbokqt3o6s\n",
-      "PHID-TASK-5z56coxja6r5rbey633o\n",
-      "PHID-TASK-fyybkik3jnrz25mdbjea\n",
-      "PHID-TASK-upajxn6r42b5mvgdvg4u\n",
-      "PHID-TASK-3xmwgu22clys4qnwhvfj\n",
-      "PHID-TASK-g6ern4m4ctxikpozgnha\n",
-      "PHID-TASK-e754krtqrkmtvi55a5wr\n",
-      "PHID-TASK-bmc4xfzmfvvqjrrocbcd\n",
-      "PHID-TASK-rwxrle7xnhmz63ujcqjc\n",
-      "PHID-TASK-fk7j2az3j3ks52n4wvg5\n",
-      "PHID-TASK-qwu6tsfyuvic4ungwofd\n",
-      "PHID-TASK-riqtlu6jga2olfkc3ozl\n",
-      "PHID-TASK-w7nid5fuef63kkolvi3n\n",
-      "PHID-TASK-fzzyk5pyf5z3b4bz7k2n\n",
-      "PHID-TASK-2kxlh36d7ae4apn7vxff\n",
-      "PHID-TASK-bkunv6kbite7pb74lhap\n",
-      "PHID-TASK-jwcd6eadytsw2au77emm\n",
-      "PHID-TASK-qs2qv3kzzffml4p5gons\n",
-      "PHID-TASK-g4sg72aye2nbqzjdh3gd\n",
-      "PHID-TASK-ytqk243gnjxzenhu2jo7\n",
-      "PHID-TASK-chatnkffcac2ryz34vhn\n",
-      "PHID-TASK-lekklfuupduztoemlst2\n",
-      "PHID-TASK-ldqdnoxy2auvexjbdlp2\n",
-      "PHID-TASK-67wxtc4ozjdd24rgjf7t\n",
-      "PHID-TASK-wiosc4sy22tsxnhzhxot\n",
-      "PHID-TASK-ae5pdnywbce3fdaiy6ww\n",
-      "PHID-TASK-adgbuexuqgrstkyhiwax\n",
-      "PHID-TASK-7qzoqhzy6hdwgnxmlkfw\n",
-      "PHID-TASK-sbabim6xkbzbfmpzbhw2\n",
-      "PHID-TASK-g37btpr3pykwbk3ho5jh\n",
-      "PHID-TASK-m3mxko4zbo6nl2kgz2by\n",
-      "PHID-TASK-dtf7e3athicgtegt5jra\n",
-      "PHID-TASK-7xd4p7fhhty3seeornpc\n",
-      "PHID-TASK-f45ircs47t3ihtnmxal3\n",
-      "PHID-TASK-34u5syhh5mqyo7rcvvfm\n",
-      "PHID-TASK-hzfx6auxygw63xeggrj6\n",
-      "PHID-TASK-ypgoy4zxc5bctzwefulz\n",
-      "PHID-TASK-zvmwksybywvrfm2uti2u\n",
-      "PHID-TASK-u3bc5ilahqhu67jkbxxw\n",
-      "PHID-TASK-emgwmnazcg2mnjqwuy34\n",
-      "PHID-TASK-cgd7gfh5limbmfzyuqbj\n",
-      "PHID-TASK-wnt7rzmhqp7spos2ra3v\n",
-      "PHID-TASK-gcxpqprlky5p3csmakeu\n",
-      "PHID-TASK-goldr7i773st4wqcjxev\n",
-      "PHID-TASK-cuzlz53jl73xd5rwzfwe\n",
-      "PHID-TASK-zjnwbcq6vujt355a3rpo\n",
-      "PHID-TASK-d77ihdd6l74pyicsh6os\n",
-      "PHID-TASK-scuorfdmgzjdphugjbmh\n",
-      "PHID-TASK-c6jr2jdyjmcydtgy4pr7\n",
-      "PHID-TASK-x74esizqbmiiw7nhiogh\n",
-      "PHID-TASK-42zzbjl2eh4mv5xecel6\n",
-      "PHID-TASK-lgy5g6voka2ep73yf275\n",
-      "PHID-TASK-vdj2elhgawonhfvz6sns\n",
-      "PHID-TASK-h2riepmcawlf54gdgu2o\n",
-      "PHID-TASK-dnopciwdieirbov75q2y\n",
-      "PHID-TASK-ftg6xmbgjlpqhszufc2t\n",
-      "PHID-TASK-pemezhinhwcmsjmxrgcv\n",
-      "PHID-TASK-lpehn2gbooedlcmnbnt4\n",
-      "PHID-TASK-cxvk42p4teyvew3duhd3\n",
-      "PHID-TASK-zfbsov36z6srqhbwgabt\n",
-      "PHID-TASK-4sbnoqmt6akkxouhu25v\n",
-      "PHID-TASK-fclmxs3oedf5jio2gq6g\n",
-      "PHID-TASK-j7kkjkivstfcbdtgopcv\n",
-      "PHID-TASK-dpdpa5liabymg7w2g4yy\n",
-      "PHID-TASK-b73qbgwpj2jg4avkkdnb\n",
-      "PHID-TASK-x4lxm7vnk37zcqajzk5r\n",
-      "PHID-TASK-zz6pjwdovfpej7nnkvlg\n",
-      "PHID-TASK-xph2545wogpg3ilxwqvv\n",
-      "PHID-TASK-kvdc2sbtbd6agc4wdbbt\n",
-      "PHID-TASK-oz5jjuc4evheyckkxa75\n",
-      "PHID-TASK-cxvaopbhevdikka45q3y\n",
-      "PHID-TASK-dobpoqvld4np3b5yv3hj\n",
-      "PHID-TASK-rj2zoft2yh74cpk6h2y7\n",
-      "PHID-TASK-zwqtfztcfyrexovbyarr\n",
-      "PHID-TASK-reknxycmtl2gxva75ktp\n",
-      "PHID-TASK-2caghp6wplr54d3wekly\n",
-      "PHID-TASK-parbfhdkrfhhceyjfyzf\n",
-      "PHID-TASK-twukwcdq55v7wby6qwvx\n",
-      "PHID-TASK-2glncnsws774p5ae225r\n",
-      "PHID-TASK-ena4hp3pzrqznsrbns76\n",
-      "PHID-TASK-em74gqq6yx5on4mj77dz\n",
-      "PHID-TASK-psuzyfjtumeoqqoapj7r\n",
-      "PHID-TASK-izisrqmjp3trkjaifdin\n",
-      "PHID-TASK-ftzt37epboyseb3ggnxl\n",
-      "PHID-TASK-tp3if73tgdh5us2okcnt\n",
-      "PHID-TASK-pwym3hscyxiqlzuo6ffh\n",
-      "PHID-TASK-jx5rpwyz5z3myik43die\n",
-      "PHID-TASK-vugz2ayag65wyaecr7ve\n",
-      "PHID-TASK-jvicijhnnvmkmtkj4r5b\n",
-      "PHID-TASK-n2qnl3eqyqev6tdkohxz\n",
-      "PHID-TASK-j4en6ingifxpa67vre45\n",
-      "PHID-TASK-vfdslw5rczsnlnpgu752\n",
-      "PHID-TASK-qamxjhmoqqas27inzryu\n",
-      "PHID-TASK-ousahplumt5sf7vusapd\n",
-      "PHID-TASK-upntlx7j3bdz3r52gesp\n",
-      "PHID-TASK-pgl7oiy2l6bvk7hzunv7\n",
-      "PHID-TASK-7xyquvj6hhetuc547oo3\n",
-      "PHID-TASK-ntqqbxxddzdo7yltukgf\n",
-      "PHID-TASK-crppoo23swkvxppmtyyo\n",
-      "PHID-TASK-wbcmbobk54vghobxtvq5\n",
-      "PHID-TASK-5yohjyriweszqbp34vz6\n",
-      "PHID-TASK-yarhuzhed4wqvpw62gpb\n",
-      "PHID-TASK-atiq5mebijzmzfpmqye2\n",
-      "PHID-TASK-h2scyo6a2vi7fzgxwmg2\n",
-      "PHID-TASK-u7s5e2g4bwlbc7qkpfjc\n",
-      "PHID-TASK-dkzwbg45silmhmsouxdk\n",
-      "PHID-TASK-oucacwo66k2ybwrotr5f\n",
-      "PHID-TASK-msf2quw2wlciqweodnnt\n",
-      "PHID-TASK-qvq2zj4itka6fwjddhwh\n",
-      "PHID-TASK-6vymomlg7udbwzf75icd\n",
-      "PHID-TASK-bd4dgg3belnvzk5644rb\n",
-      "PHID-TASK-sfzqgeaol3scscbd2imq\n",
-      "PHID-TASK-hl2jx7woen5yuyiqirv4\n",
-      "PHID-TASK-2falvdljg7ldqp2rj3l5\n",
-      "PHID-TASK-cpq7rrq57bxr73nzx4zb\n",
-      "PHID-TASK-axqdhgfcw2rceb3xxkdn\n",
-      "PHID-TASK-ovk5omihhahdt4qfvph7\n",
-      "PHID-TASK-f627kqg22t3exoned4d4\n",
-      "PHID-TASK-44p2piogq6pows7eriqb\n",
-      "PHID-TASK-hrckm6oxmmkaoroohbia\n",
-      "PHID-TASK-m5xgrnjz6bps3ib55cr7\n",
-      "PHID-TASK-xl64eqcb6ygsvtl5jnqv\n",
-      "PHID-TASK-6ylcfxjs56sonur5wvhg\n",
-      "PHID-TASK-5fgokfjvvl5idcf7wq5q\n",
-      "PHID-TASK-mdr37i6dfciuquwfrsiu\n",
-      "PHID-TASK-pquph4y6rgkckbyn7rza\n",
-      "PHID-TASK-ih4n4564yrxr2ygatq7s\n",
-      "PHID-TASK-xskmm57u4y7kf62syw5f\n",
-      "PHID-TASK-4yo52lx6x7wj5lym5xlc\n",
-      "PHID-TASK-7gxc6q7whoodm3jmk5bv\n",
-      "PHID-TASK-7uw3xey4tqnzlnmyclap\n",
-      "PHID-TASK-un4nilv22yoifhx5muc5\n",
-      "PHID-TASK-pe2hcgpuqebuelkuegcp\n",
-      "PHID-TASK-xdi4r7ceks7mdjg5jvbl\n",
-      "PHID-TASK-z6u74sout6eqjchhlbja\n",
-      "PHID-TASK-7vghnyvf4zsfnamrgi5g\n",
-      "PHID-TASK-dwllxtwbn3l46wpsweqk\n",
-      "PHID-TASK-sg62navkedep4loydypt\n",
-      "PHID-TASK-p6ts7vep3e6p2gds2ktg\n",
-      "PHID-TASK-nazqhnyfc7ftcgefkuwk\n",
-      "PHID-TASK-ccf5hssmynovsc2eeyi7\n",
-      "PHID-TASK-mjjjlepmev2tbtsh3jxb\n",
-      "PHID-TASK-b4n4vtsivb5tsumyakxy\n",
-      "PHID-TASK-54nochcknohar22gmhks\n",
-      "PHID-TASK-um7czp26rhb3rg5y7ylt\n",
-      "PHID-TASK-27yzqmhzbjs5rne5s34q\n",
-      "PHID-TASK-vi756jr6zyy2qwagomlc\n",
-      "PHID-TASK-rtrlbvsemfk66nq4yjrk\n",
-      "PHID-TASK-xudydyain6z66hfd3b4j\n",
-      "PHID-TASK-nnept6fzie6soxprbn5c\n",
-      "PHID-TASK-ptgqr6zojc4enjvswwud\n",
-      "PHID-TASK-evpea5eipr52hejululr\n",
-      "PHID-TASK-vytwuphk2slvp4di2jdx\n",
-      "PHID-TASK-qbcdetoo7qm4jdonkcjz\n",
-      "PHID-TASK-inzxqv53pmck5ixn7m3p\n",
-      "PHID-TASK-kxnh5pjmlmwxifaxh7ms\n",
-      "PHID-TASK-ykbhhmjodoocwvhdre4y\n",
-      "PHID-TASK-uxy2xvq5jbknz67fn7wg\n",
-      "PHID-TASK-w7pprk65bliocrygvf6x\n",
-      "PHID-TASK-27nmtsor6eimhr5y7et3\n",
-      "PHID-TASK-surzsdxcrbzuyzqvftoa\n",
-      "PHID-TASK-zhrtjoratrgaaikgkpse\n",
-      "PHID-TASK-jluksfszdh7gv4yindcl\n",
-      "PHID-TASK-eadbguwqy532rvgz6odb\n",
-      "PHID-TASK-4gefxwl7us64nltukoon\n",
-      "PHID-TASK-cqwbgfkvpqda37mpw4ej\n",
-      "PHID-TASK-ax47g3ki5ssd7peuji3p\n",
-      "PHID-TASK-jwmmvp23t2xd4yvcgzu4\n",
-      "PHID-TASK-p4neoppdlgxnyyv67555\n",
-      "PHID-TASK-h653ah4yfpixu3lyftgq\n",
-      "PHID-TASK-dr3mdcdnc5tips2mh57g\n",
-      "PHID-TASK-feyxsootc5yehsnjglpn\n",
-      "PHID-TASK-d7no6zkv7cafcmlb4pgb\n",
-      "PHID-TASK-nfrfujiczibmostmogl4\n",
-      "PHID-TASK-fxa5h2jzelmnjbfjhslc\n",
-      "PHID-TASK-pgrl2ozbdinedqyu3zhp\n",
-      "PHID-TASK-jwug2jk4wwdhybwdo5mt\n",
-      "PHID-TASK-7oof4yk2z7twkxa4m44m\n",
-      "PHID-TASK-na3kvjeuvjvrfmdfp33y\n",
-      "PHID-TASK-hixhmoom5yqrm66bfq43\n",
-      "PHID-TASK-gw4kqg7hxd3uiuwopwmw\n",
-      "PHID-TASK-gjdoj3a3jrnvxz3zslyj\n",
-      "PHID-TASK-6m7f64h6b4dqidv7aoqk\n",
-      "PHID-TASK-nn2dv56qvs3mjvm533mq\n",
-      "PHID-TASK-q4ectqywx354prbxw6g6\n",
-      "PHID-TASK-kc7quhrwey6274zbvvpw\n",
-      "PHID-TASK-2mwqn6vwc6bznvjfn3vg\n",
-      "PHID-TASK-vsxmfaftb5u77hxjzrlr\n",
-      "PHID-TASK-2lbvzwvr2rcpaahfrzu7\n",
-      "PHID-TASK-6xlmfh5z7qar45y5xdva\n",
-      "PHID-TASK-p4knbm6poo246efefsph\n",
-      "PHID-TASK-rfnk22psp766igbje5es\n",
-      "PHID-TASK-gczwgyrlggneqddarcum\n",
-      "PHID-TASK-7l43lybihonkgrfu2q5d\n",
-      "PHID-TASK-thvvordl2hv7kcsai3bw\n",
-      "PHID-TASK-evpxmbfxyief5l7gsbk6\n",
-      "PHID-TASK-kuwpox6ibgr56bpzslcr\n",
-      "PHID-TASK-5mgdsk4ykjr4lc4rfm3a\n",
-      "PHID-TASK-mppl4c4v4ljpt2byhnxf\n",
-      "PHID-TASK-32vq2w6nrmkqhr2ecptb\n",
-      "PHID-TASK-boiihq6lvygsgus2qbrt\n",
-      "PHID-TASK-yk5ghixsbt7pcjv7wois\n",
-      "PHID-TASK-p6nh7m7ljbshvwyj2lmd\n",
-      "PHID-TASK-ypnibbwkhkctaw6xxskl\n",
-      "PHID-TASK-f6765ahcloqg4k3lhy2n\n",
-      "PHID-TASK-ark2omnqbkzm4rckjjjm\n",
-      "PHID-TASK-d6fvkqxdzbk3emadetgp\n",
-      "PHID-TASK-dstdh5ubda4mfhlddsus\n",
-      "PHID-TASK-wkw5zbjzhfqvkpwqq4dz\n",
-      "PHID-TASK-yko76gbkbhubxt5cplo5\n",
-      "PHID-TASK-nxdykwxwefwrkkwa2sxc\n",
-      "PHID-TASK-ddwzsz5d7gwehcqqwr6x\n",
-      "PHID-TASK-lmv6en7m2i2nthp4bbad\n",
-      "PHID-TASK-3dkpw6uttju4ehjxawfk\n",
-      "PHID-TASK-h52lnxgvppaohab4kg6x\n",
-      "PHID-TASK-xe24oejtt6ji24d5t62v\n",
-      "PHID-TASK-i7csvcnyrxx5gr5lwuwd\n",
-      "PHID-TASK-xwtmpv2x7s3ve2444eyi\n",
-      "PHID-TASK-qs4hjzccsgzpxttdtdrd\n",
-      "PHID-TASK-gfsol6rwzvgp2bqtxhxa\n",
-      "PHID-TASK-43nrc2oe3kjbjeoi5weu\n",
-      "PHID-TASK-j7arlw5peomdv3rolltm\n",
-      "PHID-TASK-hjchikg52kgk75rl7yaa\n",
-      "PHID-TASK-rafcafjslpgvnetrixxn\n",
-      "PHID-TASK-yw4hrlw6tweytjl62h36\n",
-      "PHID-TASK-6ghlb6bfzg6jhbosmoq2\n",
-      "PHID-TASK-mipnpagv42ujw7okwcjf\n",
-      "PHID-TASK-23mm54valrpkfsjce3lj\n",
-      "PHID-TASK-uctbq2qfw5ogzgknys3a\n",
-      "PHID-TASK-eri6nma5at4veawakgy2\n",
-      "PHID-TASK-4hd4cmhduncacfpdevsv\n",
-      "PHID-TASK-sfrluwneg7unava7ogpl\n",
-      "PHID-TASK-vlthdxz6gr6ej4yayl53\n",
-      "PHID-TASK-vyopkwx7tzzhwu3uxyi3\n",
-      "PHID-TASK-j4o6hezr3wnjxd57w5a5\n",
-      "PHID-TASK-d6mwrlxedpo24myhvpw5\n",
-      "PHID-TASK-wuqpc2pu5uodgmseauhd\n",
-      "PHID-TASK-oupzvbwduxmp5jze2owb\n",
-      "PHID-TASK-ye5mwgkyf24rzjhatyv4\n",
-      "PHID-TASK-udmrgnust5cyxf2ghvzk\n",
-      "PHID-TASK-24fbkjihpzafrhlh33na\n",
-      "PHID-TASK-edd62atl2rczsx2d656j\n",
-      "PHID-TASK-jqbci4yiint3kpdehjhn\n",
-      "PHID-TASK-nbwk4dgm4c4qnjzg6thr\n",
-      "PHID-TASK-tudylk7ksc5zbhsewjyu\n",
-      "PHID-TASK-sxmma4s54vfesb7w6uwo\n",
-      "PHID-TASK-c3pmu5hmgxjgedm5kw7e\n",
-      "PHID-TASK-i73bqleta3mxkalcjer2\n",
-      "PHID-TASK-npjjopn76exjm4ew3cxf\n",
-      "PHID-TASK-yw4lbpse7jkf77ng3ueg\n",
-      "PHID-TASK-kq6jtegqhbf7n3nonedr\n",
-      "PHID-TASK-6rfydyjylk7nntzf43tk\n",
-      "PHID-TASK-3vfkchuyvemtkqdiybsv\n",
-      "PHID-TASK-fbvcimq5q66ajybncb7c\n",
-      "PHID-TASK-yavg34kffrrjkowzgnkc\n",
-      "PHID-TASK-eoqysm7gglrd73chhak6\n",
-      "PHID-TASK-yd7ochttyhijjxl6b2jj\n",
-      "PHID-TASK-f4tvdtjt3vze2yti62aa\n",
-      "PHID-TASK-y4bnpd7zbos4ftiaptko\n",
-      "PHID-TASK-nesgwricmarnjfu5yju5\n",
-      "PHID-TASK-unomzqtpqw6kv6noyrev\n",
-      "PHID-TASK-nm5utpa7p43ribr4hikq\n",
-      "PHID-TASK-in4rh3odis5atqwtca5u\n",
-      "PHID-TASK-4qiopkau6hjwndo32zi6\n",
-      "PHID-TASK-hratsjfcabvp22ykev47\n",
-      "PHID-TASK-aqkrg4zofhwpyfihiwdi\n",
-      "PHID-TASK-uzu755zs7nfkcf7hr26i\n",
-      "PHID-TASK-zhbaybf77c2fnawhs7mp\n",
-      "PHID-TASK-nqplnxbxs7jfzg4fzdna\n",
-      "PHID-TASK-h43bnjrvp2e4ey2244ee\n",
-      "PHID-TASK-atznnv7miiw6xcbyzewl\n",
-      "PHID-TASK-7xlzuxk3ore4kep2xn5u\n",
-      "PHID-TASK-izzgctdjakrtomfnsa2n\n",
-      "PHID-TASK-o2njh75t3ulqqtpvzcjc\n",
-      "PHID-TASK-s6jclbzflvjqvzupxbrv\n",
-      "PHID-TASK-yoiz5bs5xl4hztc6azyb\n",
-      "PHID-TASK-vxauebeaoyvfqdythyzt\n",
-      "PHID-TASK-ralatlcjdkp2pb5sjaiy\n",
-      "PHID-TASK-22dxmk6w5i2gv5vgbjoj\n",
-      "PHID-TASK-aljnlx2ibmppm5ov7vo7\n",
-      "PHID-TASK-j3t4kswoyrigddha43ep\n",
-      "PHID-TASK-t37b6rskig2gygqauzqe\n",
-      "PHID-TASK-q5yeocuc7uzle4efdhw5\n",
-      "PHID-TASK-pdqwezif4yyehpz3pomy\n",
-      "PHID-TASK-vcjosxhcqmpzxbjafscg\n",
-      "PHID-TASK-b5q6raassymzwkebamu6\n",
-      "PHID-TASK-56jj32rdepjfe2dxapzo\n",
-      "PHID-TASK-zcneabl26r5jk4uera2i\n",
-      "PHID-TASK-q6gvl4xwdjjg6spcmgi7\n",
-      "PHID-TASK-u7nbiznggvbdhjsuerpt\n",
-      "PHID-TASK-qt6vdckmcwpnahubzp3f\n",
-      "PHID-TASK-7pt5q2e2t3vecx3vztw2\n",
-      "PHID-TASK-fwj24igsgg2aqdhxz7wz\n",
-      "PHID-TASK-733eiwtp5o2tjyz7twh7\n",
-      "PHID-TASK-gays66miu6qia6yucqn2\n",
-      "PHID-TASK-dncrsb6dk5scs5lfx2nt\n",
-      "PHID-TASK-kuprsa4m7ibn5pvxkone\n",
-      "PHID-TASK-ok33eixi5ajoi2xq4y5b\n",
-      "PHID-TASK-zjh7rxbyat4v4fiw75ul\n",
-      "PHID-TASK-yyi4jvalwcv5dpoi7ztd\n",
-      "PHID-TASK-hic2xcoiiq7ialvw5olf\n",
-      "PHID-TASK-2yz76pkci3v3zvjx2tiq\n",
-      "PHID-TASK-sffy2i74xcwn56xygl5s\n",
-      "PHID-TASK-ux7txrspzgavrsg33265\n",
-      "PHID-TASK-vyjwvfkazlz4xdouhxqh\n",
-      "PHID-TASK-aiigjvy5vmwd6y2u2ole\n",
-      "PHID-TASK-htxalzptwgauyfiuzj3f\n",
-      "PHID-TASK-5qityf526pfz6qwd7svp\n",
-      "PHID-TASK-catfculfgyiwykiyu7uj\n",
-      "PHID-TASK-3et3rxfdnnlv6panz53k\n",
-      "PHID-TASK-iu6hbgjioqo5cvt23aal\n",
-      "PHID-TASK-y4a7ol3ogwhv6t7beaox\n",
-      "PHID-TASK-4e57g4ptze3lbabyzrzu\n",
-      "PHID-TASK-hha36vju233upi7kw3se\n",
-      "PHID-TASK-jjqfhcfkk7z7pj4lsi37\n",
-      "PHID-TASK-r3eqg73n7uhflvgw7eg3\n",
-      "PHID-TASK-aiuoktdbszkgqdmpuqlq\n",
-      "PHID-TASK-omdhcpi6if5gftpy7523\n",
-      "PHID-TASK-ebmnnccanbjpovnhy3nw\n",
-      "PHID-TASK-nlovvj3dmzpq3qzvi5qq\n",
-      "PHID-TASK-pbmmp535m2nwlycrbccu\n",
-      "PHID-TASK-7hmdcwhevnhvtjp6kuea\n",
-      "PHID-TASK-rrhxw3o7tylkgfuhgckm\n",
-      "PHID-TASK-trd3quxv62oo47pm6dey\n",
-      "PHID-TASK-pkufios4crste37qzbra\n",
-      "PHID-TASK-vtu44ya7j43gvaddcjhx\n",
-      "PHID-TASK-nhj52cwstgebwydn6v4r\n",
-      "PHID-TASK-h7awbzyfjip5gjfxifz2\n",
-      "PHID-TASK-xooewvbyzadgfzwpxeqt\n",
-      "PHID-TASK-6sni25mbjuiipuy7iv24\n",
-      "PHID-TASK-j7lyujcbs6zaatnh7kya\n",
-      "PHID-TASK-c4mfirb7unow74hkyrys\n",
-      "PHID-TASK-tjmyy26tm4c7ectpe3s2\n",
-      "PHID-TASK-rf2ed4nqjcimz43cz4tr\n",
-      "PHID-TASK-i27oymi2g7hoildczlee\n",
-      "PHID-TASK-l6lohkvjqdbjrls5sdjz\n",
-      "PHID-TASK-w6mmcf4y43jmqe4tziga\n",
-      "PHID-TASK-lj6h46r7rjyl6me5nb7h\n",
-      "PHID-TASK-22klbikg4fmxw7aotqvi\n",
-      "PHID-TASK-ipv73kunpojcr76x2cb7\n",
-      "PHID-TASK-k77k35tkwkjkzeravyd3\n",
-      "PHID-TASK-v44q2sk65tk423gk2wgc\n",
-      "PHID-TASK-trziv3xjwkvokcwfszqm\n",
-      "PHID-TASK-zoji45q564z2zd5mmomf\n",
-      "PHID-TASK-dzv6eikbb3qjtwxvccno\n",
-      "PHID-TASK-fl7p4f543bjhpoylmcxl\n",
-      "PHID-TASK-rjymkq6lc7hubjand5ea\n",
-      "PHID-TASK-zlvsszagknsbory2w3zc\n",
-      "PHID-TASK-aaouxso4nhg5xgscmdmm\n",
-      "PHID-TASK-wxxlsxtwpum7ayno6uo4\n",
-      "PHID-TASK-equ6rehqzaorfkk3nuw5\n",
-      "PHID-TASK-agsyhe563ga6xlci4yds\n",
-      "PHID-TASK-u4lgntwhbwxxlocbfh5j\n",
-      "PHID-TASK-n7t7uv2o256io5ck73dn\n",
-      "PHID-TASK-5ts3ggpcjypmoohi32ft\n",
-      "PHID-TASK-itdw5f4y5avsmhjnkmu3\n",
-      "PHID-TASK-uycqr5h5vgduf55buvs4\n",
-      "PHID-TASK-o4nfasrtm3o6yo3ndwdo\n",
-      "PHID-TASK-gendcsutkyq5czjdhhzy\n",
-      "PHID-TASK-djr6oferphbxqbgynsnj\n",
-      "PHID-TASK-bq2ty22xrf3ppn7g6cdz\n",
-      "PHID-TASK-sudk6gs3gu276aszhg6w\n",
-      "PHID-TASK-r65cbq4ixbupvjwfesjt\n",
-      "PHID-TASK-bl2j543fwlnzihaohpzu\n",
-      "PHID-TASK-kxfoifw5vn4mx32v4nnk\n",
-      "PHID-TASK-wn3s7fg7p7dky4txupqd\n",
-      "PHID-TASK-l4bd6ekvg2ifcspk72da\n",
-      "PHID-TASK-dvolbemwppvolpsqeen5\n",
-      "PHID-TASK-tes2snxxrdfko3p2bzft\n",
-      "PHID-TASK-ikc6bitfegyn4srxsl45\n",
-      "PHID-TASK-qgxcekjgfnhxpyipqdms\n",
-      "PHID-TASK-4lk6qpiuan7kbk6fch54\n",
-      "PHID-TASK-5jzwlml42c5fglrwtkfi\n",
-      "PHID-TASK-bcaoiws3nuti2nsjkjz3\n",
-      "PHID-TASK-w64szlorn34djdoon7kx\n",
-      "PHID-TASK-ibe45dq6vmicfsr4xdu7\n",
-      "PHID-TASK-cp6otuehw4hsidnwe5aw\n",
-      "PHID-TASK-uypsqiix32ng3uny23mo\n",
-      "PHID-TASK-epab3bnrysrclgspz74p\n",
-      "PHID-TASK-bzqqgbtatyk37hok3eeg\n",
-      "PHID-TASK-7n32t2g7qmarlr4ehelo\n",
-      "PHID-TASK-dtn35n72ll6dpl3csge6\n",
-      "PHID-TASK-si6erwgobtecdd3semnx\n",
-      "PHID-TASK-2537ayvqomhm6aw6be77\n",
-      "PHID-TASK-tht33qexrstttffqqdac\n",
-      "PHID-TASK-5rnk4jk4usyomimnhvgw\n",
-      "PHID-TASK-q5vutkamr63367rd7zxs\n",
-      "PHID-TASK-jr5ycdlwcecuxieizpcv\n",
-      "PHID-TASK-l56nfzkytddrozusk6lo\n",
-      "PHID-TASK-oupbsd5554xmfpbxxxyj\n",
-      "PHID-TASK-gnj6uia6j4dqknm3pggn\n",
-      "PHID-TASK-ii6rhmjn7erj375xgev6\n",
-      "PHID-TASK-4oj2ukzhgtypk3cunb5o\n",
-      "PHID-TASK-oplpiaxofrtlrt3axphq\n",
-      "PHID-TASK-p4b2w3x4lqa7c5xyypgv\n",
-      "PHID-TASK-qsixjppbefsch6bho32b\n",
-      "PHID-TASK-uwxs5htjvrwhn73aykjk\n",
-      "PHID-TASK-j5vjfdev7u6pvuctl7bs\n",
-      "PHID-TASK-4rr6da3rjeo7zsqa7vfz\n",
-      "PHID-TASK-cxh6tjsfd6x3hseyrbib\n",
-      "PHID-TASK-bdoqslcxagfk2qftlhdb\n",
-      "PHID-TASK-4hkjv2ath5m5txk2nfy2\n",
-      "PHID-TASK-5nevglmngclvgx6tccw2\n",
-      "PHID-TASK-66ginvgnolmwprgt3cuj\n",
-      "PHID-TASK-cclb4wsdr7iky3sqhmhw\n",
-      "PHID-TASK-o5baaacr6iodckukah5p\n",
-      "PHID-TASK-cmua6cyyxv7g5lccv5gd\n",
-      "PHID-TASK-l2ev3r2fbwgu3qyqlxqi\n",
-      "PHID-TASK-7ldpzjc4tuyxvsjssopj\n",
-      "PHID-TASK-fbqhcge4qrnba67okcqc\n",
-      "PHID-TASK-hf3lpbfwtlmq4fqfsw75\n",
-      "PHID-TASK-s4knko26mc6rjznucnmu\n",
-      "PHID-TASK-kpx3x3zovypfoultwmwq\n",
-      "PHID-TASK-puu746mglczm4q4dlq2x\n",
-      "PHID-TASK-zoxqzhcrz3axmm25xk3m\n",
-      "PHID-TASK-qi4sreqcffmkf7rnalbq\n",
-      "PHID-TASK-bygn32hj7tnm3bhqdwpl\n",
-      "PHID-TASK-qmrrjmfnasuu75b532kc\n",
-      "PHID-TASK-ov7pqqy7izua2omo6knh\n",
-      "PHID-TASK-sveofxpb25owm56vn52q\n",
-      "PHID-TASK-acmmw5etc6s3hnjsoagh\n",
-      "PHID-TASK-dixea6aehlzjvgpfccvz\n",
-      "PHID-TASK-vzoa67je6467j364n6nw\n",
-      "PHID-TASK-v2iurekb2mj5nlfaied2\n",
-      "PHID-TASK-bpmyhnrfcuvcbkkh3dqm\n",
-      "PHID-TASK-5butgjmyg5i25tvyzxlh\n",
-      "PHID-TASK-7i5ifep2qqvrl24ie5dq\n",
-      "PHID-TASK-svgbuubly7i37677eqfj\n",
-      "PHID-TASK-ycfuexv2jknnm72vmgj2\n",
-      "PHID-TASK-rk7rg7s3j76gm4lymrcv\n",
-      "PHID-TASK-27y3ao6udiwcetvc5juo\n",
-      "PHID-TASK-7gsk7m3csraunlup7tpi\n",
-      "PHID-TASK-nirzuutzqnx7m4wim5ej\n",
-      "PHID-TASK-jtms4kp7m57ptk6ccdpu\n",
-      "PHID-TASK-alab5hdzxtgqi3cu2eqm\n",
-      "PHID-TASK-rqtkbfxffdpbdagffzia\n",
-      "PHID-TASK-uxrs32aphojxiommp53x\n",
-      "PHID-TASK-dp34rjmxuoe4ud2hxyic\n",
-      "PHID-TASK-4vm6pqlg5hib6dju3lvl\n",
-      "PHID-TASK-2klcawe4zbxemkcjvd56\n",
-      "PHID-TASK-q3emmq6fhgusggcncftz\n",
-      "PHID-TASK-r5kajbzeeq4xhzra4a5e\n",
-      "PHID-TASK-3gmemcjr7w4kdsoeiv6t\n",
-      "PHID-TASK-ehj46yftpulklnhzc5nl\n",
-      "PHID-TASK-jhcapgyaxz3ow5vafpun\n",
-      "PHID-TASK-vzhy73evvtw5m5ueeyz3\n",
-      "PHID-TASK-sqeh7jyki3euhm6uvc2p\n",
-      "PHID-TASK-7cagldmd3jobcif24ufn\n",
-      "PHID-TASK-oq4h4k5rxxh5mzsezcrf\n",
-      "PHID-TASK-kcmkos4wcsglqvinne4e\n",
-      "PHID-TASK-v4wsjl2yostcro6yfl5m\n",
-      "PHID-TASK-rlrxpsau6vww7ypqckon\n",
-      "PHID-TASK-y7lnjkpbhgxsbrsuxizc\n",
-      "PHID-TASK-bd27gm56r2au6k3ieg34\n",
-      "PHID-TASK-6wbe37ccwgagtoa3kdhv\n",
-      "PHID-TASK-qsnt7zdtnfm5xnawmteg\n",
-      "PHID-TASK-a2p56mvfah4kifyqy327\n",
-      "PHID-TASK-xnmn6i6yc73dhywaqm2m\n",
-      "PHID-TASK-ph24e22ltq2s3oztatem\n",
-      "PHID-TASK-nlgy7km52ntxkqvlqnu2\n",
-      "PHID-TASK-wm36m5xxm3u54pgeyz4a\n",
-      "PHID-TASK-wfbovalkwufxdqplhata\n",
-      "PHID-TASK-zc6v32lm5ytpux3undwt\n",
-      "PHID-TASK-2siqskyqqgqcynauvs72\n",
-      "PHID-TASK-rrnwu2dnzhxx4ckh2cdj\n",
-      "PHID-TASK-zrcmecxwpnqso5zyiauu\n",
-      "PHID-TASK-jxtza5wxkt3lvc2yga75\n",
-      "PHID-TASK-sqexirvlnm7n526sp3a3\n",
-      "PHID-TASK-6pam6yoqknf5n2r6w5qx\n",
-      "PHID-TASK-lui5vpla74335t6r63nr\n",
-      "PHID-TASK-kjhdlfcx4jhz24dn5jl5\n",
-      "PHID-TASK-jvkszokywziqndkikfj4\n",
-      "PHID-TASK-jd5jq4oxcix7nauaawh2\n",
-      "PHID-TASK-hbtmtpgjefyo637ujihd\n",
-      "PHID-TASK-lskwjin7vud63rd4ruhi\n",
-      "PHID-TASK-y2l4ooxqksxji4wptopd\n",
-      "PHID-TASK-7rwifffi3m7nv3vjbxms\n",
-      "PHID-TASK-p5bbvutzsk36zk6seh2n\n",
-      "PHID-TASK-nqg4k7suwubkfsf5dkfa\n",
-      "PHID-TASK-usa4c4in3z4ffsufnkoi\n",
-      "PHID-TASK-u4mzdxdhi5v6xlyw7zkb\n",
-      "PHID-TASK-rygkkourrlt3am2ziugg\n",
-      "PHID-TASK-qnbuhg3o2v7eth5y6stx\n",
-      "PHID-TASK-qpzhi34lem7nwd6nbsu5\n",
-      "PHID-TASK-hju3hugjlttehugtvu7d\n",
-      "PHID-TASK-vbuyxcfsri4ye35bdcvl\n",
-      "PHID-TASK-vs2q4kkygajmjexkudzc\n",
-      "PHID-TASK-cfoc7zk5vj22ygiycyil\n",
-      "PHID-TASK-fqzbhpnqgjp4qad6vrii\n",
-      "PHID-TASK-mu2vgsj5i4mlfiswzx4o\n",
-      "PHID-TASK-q5qzozhueiwufmgr5jwq\n",
-      "PHID-TASK-eto6zg3t57jsyeutf64w\n",
-      "PHID-TASK-xodrhcpq6wj3seyvlmoc\n",
-      "PHID-TASK-5pkp6kncu5pzdahrd6qn\n",
-      "PHID-TASK-dke6zkvtno2ooulod6bw\n",
-      "PHID-TASK-6s22kiygdurpmwpk3lqs\n",
-      "PHID-TASK-eddbh3tcvexylixr6tiy\n",
-      "PHID-TASK-67oipsmostyhug2737rz\n",
-      "PHID-TASK-faltfztxkqc5daxcntnx\n",
-      "PHID-TASK-sm4xza7t5teplcefqzij\n",
-      "PHID-TASK-lufoybqaultvloukxdjz\n",
-      "PHID-TASK-4hclm7qlzk6wj2x4xb2q\n",
-      "PHID-TASK-5am5k4waw47kga4kfuau\n",
-      "PHID-TASK-3hxhzuqbp3dgpcaubftg\n",
-      "PHID-TASK-sojoibzwruxvdv55tvoj\n",
-      "PHID-TASK-vq64xxj3d54xo3daemjh\n",
-      "PHID-TASK-toxebubahyyw4rmtx4vj\n",
-      "PHID-TASK-m4tvj6xkn7aqhr4yajip\n",
-      "PHID-TASK-re6qm3cualjp5dczcmlc\n",
-      "PHID-TASK-6ey7x6n5abzoqr3wo43j\n",
-      "PHID-TASK-ft4ssckvycvjlzjy3fax\n",
-      "PHID-TASK-nilflssh5x72tinfk7a6\n",
-      "PHID-TASK-qjailuyl4kenb2ytqa5a\n",
-      "PHID-TASK-sby6wjdxcouq3g5mq67p\n",
-      "PHID-TASK-l2askobdymn34t55t5lm\n",
-      "PHID-TASK-u4ds5rkvr4rcsxwqaoaz\n",
-      "PHID-TASK-it7sgrllp5k6su66uukw\n",
-      "PHID-TASK-mip6kupgxcxydyy26dwa\n",
-      "PHID-TASK-uxowmsznm5ykbiez7tm2\n",
-      "PHID-TASK-7rcg5rkjl6kyyl4elbfa\n",
-      "PHID-TASK-ur6l6l2ezqzug2nab347\n",
-      "PHID-TASK-z5vtizhnd7zq6vobiqci\n",
-      "PHID-TASK-kt3assypvj632tuitmf6\n",
-      "PHID-TASK-vgr63prhj7eik7b2qkwd\n",
-      "PHID-TASK-he62ku3noedhtzp55bhf\n",
-      "PHID-TASK-ofaluihol767l3yg5fjw\n",
-      "PHID-TASK-4v36rjb5p4c3fhjflpoq\n",
-      "PHID-TASK-qf4vt6acq5wtvvlwympv\n",
-      "PHID-TASK-j7v3ex7edi7dypukus5m\n",
-      "PHID-TASK-redwc5kkxwdmnoyvkj7r\n",
-      "PHID-TASK-2cs7ruqdiqeaisw3iea4\n",
-      "PHID-TASK-js6dahlv3jujgj6b2lzv\n",
-      "PHID-TASK-6tlgztl4hagkm2r7xhiz\n",
-      "PHID-TASK-p53a3hhm2h3bhitmo2np\n",
-      "PHID-TASK-tgytmlqjykzpjs6zkq4g\n",
-      "PHID-TASK-mlttagm5jcb3oqt5j734\n",
-      "PHID-TASK-3x6yvjlb5kfqndi3ivao\n",
-      "PHID-TASK-2avh7ag4txo4yazyqwg3\n",
-      "PHID-TASK-44thcl26amo7hsho63fi\n",
-      "PHID-TASK-6255kvv4aihzvptanmel\n",
-      "PHID-TASK-ob2d5ffvdmtamrwpb4u7\n",
-      "PHID-TASK-k2f6cmw4o3bualf2yl72\n",
-      "PHID-TASK-pb7leo6kictiruq53qyh\n",
-      "PHID-TASK-hz3zx2etea2vvyzkz3b6\n",
-      "PHID-TASK-uxrck24is2ussi4ctgr2\n",
-      "PHID-TASK-a2cttzysu3oh2p7i6yls\n",
-      "PHID-TASK-xwzbnkc2eempknw62ukj\n",
-      "PHID-TASK-j2nulhpv4byjb3fgfm3a\n",
-      "PHID-TASK-x7aj5blwrrol3b4wt6un\n",
-      "PHID-TASK-vpsb5oulcmbkksi2sshi\n",
-      "PHID-TASK-u7msjuo24hkzquuc5w2p\n",
-      "PHID-TASK-n27a25omdfur3socqod5\n",
-      "PHID-TASK-l36v7qffhro3qiv5v3ya\n",
-      "PHID-TASK-iqdlibipj4aozqzz2www\n",
-      "PHID-TASK-rwwvww3qvgi4ff4ivkf7\n",
-      "PHID-TASK-pt2yvsftiewkmjm3j2nx\n",
-      "PHID-TASK-l5hcose5p2erl7wolwnd\n",
-      "PHID-TASK-geudhodnzjlx4dkfmnsc\n",
-      "PHID-TASK-2q5s3rnh3ragcm43w2pm\n",
-      "PHID-TASK-l5ckh63ssiggmz3slrqg\n",
-      "PHID-TASK-em7qpd4h4h3xgy2ceara\n",
-      "PHID-TASK-otwsyh65xhzuochbdcrh\n",
-      "PHID-TASK-5mroix5k2facuxaaopyg\n",
-      "PHID-TASK-4vsqha4nxg6sirme3ghc\n",
-      "PHID-TASK-fn66at2vne5i62qo6jnn\n",
-      "PHID-TASK-pcueszubfgitqkx3f2bv\n",
-      "PHID-TASK-xz7of2bozktz6cktgsun\n",
-      "PHID-TASK-3yckz2spdz6vwpvvlsja\n",
-      "PHID-TASK-xid2rg44chmbsuqujmzr\n",
-      "PHID-TASK-wwlsd2ozt42kgfcsmka4\n",
-      "PHID-TASK-b74srkob65ougmewgpvd\n",
-      "PHID-TASK-3tkt5wwlr2pp4a6ayi3s\n",
-      "PHID-TASK-rxqaxhgvcsfou4tzboet\n",
-      "PHID-TASK-2ttmyole76xyfw5lxpgw\n",
-      "PHID-TASK-ey46lj4dpzgt5ypwdhi4\n",
-      "PHID-TASK-uydrcj3p2rhxycgc65tn\n",
-      "PHID-TASK-ndmy33qu6brquwrr27nw\n",
-      "PHID-TASK-fmgdk7zrdnkog3djzdrc\n",
-      "PHID-TASK-lsxohsnqwom7fu46vsrm\n",
-      "PHID-TASK-yhjioiu5qdrnau76umcl\n",
-      "PHID-TASK-2qe7sdslfntthznnkcbt\n",
-      "PHID-TASK-jidkdocy777f7fa4pk3t\n",
-      "PHID-TASK-cc4653x6b7o5qyh3ddoy\n",
-      "PHID-TASK-q4tev2wggvrevxlx57l3\n",
-      "PHID-TASK-dawylrxmkjvn5rn6pdtf\n",
-      "PHID-TASK-kum7spdwx5xdoe73t4u5\n",
-      "PHID-TASK-7u4x4gvkmazindkefefh\n",
-      "PHID-TASK-orgyqstlg3e7bpbpnpc5\n",
-      "PHID-TASK-oqhko7t4wfln3rpauqc5\n",
-      "PHID-TASK-erpehiwtm4uj5znmo2et\n",
-      "PHID-TASK-d6skq2oyzzqzdxdbdskt\n",
-      "PHID-TASK-hjnunyjomlrvhkq4oiqo\n",
-      "PHID-TASK-vvu5ucedidqohifits2s\n",
-      "PHID-TASK-u2ls26f436dp4ls4xqnj\n",
-      "PHID-TASK-x646ub2izdkijgiiwrz2\n",
-      "PHID-TASK-lfvhcf2i2gcieggk662j\n",
-      "PHID-TASK-j223oppi3t252tmumwbg\n",
-      "PHID-TASK-cohcqit7cjc474qs3bul\n",
-      "PHID-TASK-jgkllstpxv33sn72mt5f\n",
-      "PHID-TASK-43bme3ubhjcp6xf3kyaw\n",
-      "PHID-TASK-z4n2utsm2obyfevr5eud\n",
-      "PHID-TASK-h7bfc7jy5zuiok7zj7zv\n",
-      "PHID-TASK-tbvrdwvxvbqqobem3szn\n",
-      "PHID-TASK-sdadbdxs63vkmq4vqjom\n",
-      "PHID-TASK-isqwpxpplzad6mrvzuhz\n",
-      "PHID-TASK-edvyo63z4kmo5a2d7dvy\n",
-      "PHID-TASK-ay5qiidktmoux2bli72a\n",
-      "PHID-TASK-pg6duwir2q65ub4iepr6\n",
-      "PHID-TASK-gqjhk4wjp2xx3zlksb5g\n",
-      "PHID-TASK-zhyimecjptsrsi7gj65o\n",
-      "PHID-TASK-gww3sadaua5hd4aa5mxy\n",
-      "PHID-TASK-3f6rzvtal3vp7j7ok4ve\n",
-      "PHID-TASK-4gxgm32h47ktjmsohfhi\n",
-      "PHID-TASK-wnsljgens4avgolp5rah\n",
-      "PHID-TASK-2jhlgapomh7x5pp3mfeq\n",
-      "PHID-TASK-k3jo2lfnt7epz4x6sikv\n",
-      "PHID-TASK-67esakdk26er4uxasrc3\n",
-      "PHID-TASK-5cf6g72rzkft37gbritr\n",
-      "PHID-TASK-spoxch2h3fjmkmu6pdme\n",
-      "PHID-TASK-rghqg5jcqisid4tfv5hr\n",
-      "PHID-TASK-o6x7c2kbmm5le5grlxkj\n",
-      "PHID-TASK-jxas3inmlw4l4tcg6zyx\n",
-      "PHID-TASK-batdg3q5jwk7z4eeddgg\n",
-      "PHID-TASK-2go6ew7f46vsl6ngyy7w\n",
-      "PHID-TASK-6doqtsezbhohs5na7asr\n",
-      "PHID-TASK-p2hyhzwp54l6ohsbe4j4\n",
-      "PHID-TASK-3nquleh2aykawirbt4st\n",
-      "PHID-TASK-isttvrxbjpvgt5itwu5n\n",
-      "PHID-TASK-mnsdqy6zrnvlm2uqkhcw\n",
-      "PHID-TASK-ffl4fedejvxwcxttjfil\n",
-      "PHID-TASK-o3inw6vkpkuhjrfly4eb\n",
-      "PHID-TASK-algalgsjyyisq2anwhms\n",
-      "PHID-TASK-kd62lmqw7ntjvcrqwhvx\n",
-      "PHID-TASK-5dgywim5ydcwu6b7g2zz\n",
-      "PHID-TASK-hk4qv3of7jiwnhul5ayb\n",
-      "PHID-TASK-4g3nhqcki5ifz5oczcu7\n",
-      "PHID-TASK-h5i7cqn2z7j4vdb2bioo\n",
-      "PHID-TASK-5pskpoilrrm4nns4zugy\n",
-      "PHID-TASK-dvy6cixcc2nxje733xv6\n",
-      "PHID-TASK-jm7w3nmu4dvvbq4cevqz\n",
-      "PHID-TASK-fhtlyq5kho6tpsip3niy\n",
-      "PHID-TASK-crkiryzxavcthffyf5za\n",
-      "PHID-TASK-w3m2d62g427w2i6vbyd4\n",
-      "PHID-TASK-eepem2ziuzvmflw5gpqj\n",
-      "PHID-TASK-ipvexqb24ep4dnkhsnif\n",
-      "PHID-TASK-epwwpgqwza3gwnpfjm7f\n",
-      "PHID-TASK-xszasferpgmq6tda243w\n",
-      "PHID-TASK-d6c7qzgfg4jsrlzfag4r\n",
-      "PHID-TASK-k7f4ru5f6yx35p5jkdx7\n",
-      "PHID-TASK-sidkh5inlhdkyygqassz\n",
-      "PHID-TASK-n7i2eetsofstfrmijiw5\n",
-      "PHID-TASK-ovbuk7vqve57dhhhvnh7\n",
-      "PHID-TASK-rjfwlifxsqzej72hvwal\n",
-      "PHID-TASK-ic77u5udy3nvxbsnznrc\n",
-      "PHID-TASK-xu4scnfjjp674hs6ehjl\n",
-      "PHID-TASK-eiikdpgxia5svismvu44\n",
-      "PHID-TASK-fox5cuz5lkwl5eb3gxrd\n",
-      "PHID-TASK-2hbzqzof3t5thiyrb3yz\n",
-      "PHID-TASK-v4v3wychksw2n5sabckt\n",
-      "PHID-TASK-ukps7g4li7inap7lxq46\n",
-      "PHID-TASK-563eb2ikcrhdth26zmqs\n",
-      "PHID-TASK-3dm4nj4f3hmvkgyfm7k2\n",
-      "PHID-TASK-tyh6rgmh65nrcg5ssati\n",
-      "PHID-TASK-nbmggedatdejjopgumhd\n",
-      "PHID-TASK-d53fjwjfjlwbqoq4e52t\n",
-      "PHID-TASK-gmfhmaeyushutcy45y6x\n",
-      "PHID-TASK-zgrdvieu55b7ilh6yt3l\n",
-      "PHID-TASK-tqom52xzffar63gwv2th\n",
-      "PHID-TASK-osst63lnijz6dlmc57xi\n",
-      "PHID-TASK-acs2ekfum76g27vb7duj\n",
-      "PHID-TASK-uoptaiss5vhdq32dkswe\n",
-      "PHID-TASK-zuh52jc2toouqelcucf4\n",
-      "PHID-TASK-oe6mridn2bnwc6ynf3en\n",
-      "PHID-TASK-nvkr7m44ao53f5uftwjr\n",
-      "PHID-TASK-r3xcog5g6murfqlx2fpo\n",
-      "PHID-TASK-s72q22vgyujmcogxkisx\n",
-      "PHID-TASK-zptqvqstkrfianknvktj\n",
-      "PHID-TASK-o4e72bpfvnzueqs77k5k\n",
-      "PHID-TASK-comswpptjs3uwf7ztbnb\n",
-      "PHID-TASK-mu7u3eco45xxsfwg4vhq\n",
-      "PHID-TASK-cdmjeut7byvwilwzjfyv\n",
-      "PHID-TASK-clapsacnmffdpmc6uic3\n",
-      "PHID-TASK-qb2vdcmk4mrkuu43ivqi\n",
-      "PHID-TASK-mgaib3olu55b5fa25dcw\n",
-      "PHID-TASK-nqjwrvv7obmoxabd6boz\n",
-      "PHID-TASK-4g3tuqan3yhuka5pdfba\n",
-      "PHID-TASK-uk5g2utei5kls5xo2fer\n",
-      "PHID-TASK-d25o2mdf4mdptqcqy2de\n",
-      "PHID-TASK-ws46dvvtpsd7zfz4gkae\n",
-      "PHID-TASK-ze4pocno64vkraksutzp\n",
-      "PHID-TASK-6dfe6wmnmfcjqgh27brf\n",
-      "PHID-TASK-m2xsnbv7vbfet2rfctjx\n",
-      "PHID-TASK-465skcravcf5ewxwsyd2\n",
-      "PHID-TASK-dbpbmbo7zjpy256zvcs6\n",
-      "PHID-TASK-sxoh4wnqppbjcq4eftvq\n",
-      "PHID-TASK-ypcnrwup72gw33jiae5x\n",
-      "PHID-TASK-hljkwvij7ri6zsnlv4ny\n",
-      "PHID-TASK-io3sncftadpkbmrqampw\n",
-      "PHID-TASK-a7khjsiws3kuhgw3dtj5\n",
-      "PHID-TASK-vtupkd2hzxpp7w3fyltw\n",
-      "PHID-TASK-3tfgena4tsev5hzwqh7g\n",
-      "PHID-TASK-wgabwxsulvcboqwjus4t\n",
-      "PHID-TASK-b63g5k3ztoignbyr5s5w\n",
-      "PHID-TASK-wynzwypqafg7laiqaomg\n",
-      "PHID-TASK-vocovg5zyvqjxex3mwtr\n",
-      "PHID-TASK-aqxcn24qtgiw3ubxzs6h\n",
-      "PHID-TASK-xrh4kcflnord5zllknj6\n",
-      "PHID-TASK-leu57abgm2tb4hkx7knq\n",
-      "PHID-TASK-s4cphi53nj54xruaarhy\n",
-      "PHID-TASK-7stkkrpd65tx5rjkp4fg\n",
-      "PHID-TASK-bs4iwunmzd4mvfoqwfmx\n",
-      "PHID-TASK-vhlmolnzsp5kd7qoa2nn\n",
-      "PHID-TASK-lyuwrgvbcgimricw6omw\n",
-      "PHID-TASK-dlmzlny66znupvw7flge\n",
-      "PHID-TASK-7mo2ly5r5mqfuju3u5ar\n",
-      "PHID-TASK-pj4cd4p4ynmavre5zsn7\n",
-      "PHID-TASK-koardc3to3cjpsgjsemv\n",
-      "PHID-TASK-2astjxmuxt2yyso6g3kb\n",
-      "PHID-TASK-7d3wwwbypeipgqn42o5c\n",
-      "PHID-TASK-2nyantno3ds7ohrifauv\n",
-      "PHID-TASK-nu3747gtrfgcnn6ifzlx\n",
-      "PHID-TASK-f3bksoxide4n4n2plcfg\n",
-      "PHID-TASK-ukhmjz446wmy32ws4rzz\n",
-      "PHID-TASK-frnef4dwspf2gymmanpq\n",
-      "PHID-TASK-dl4wjvv5i2ofxqjlq7lh\n",
-      "PHID-TASK-tzlbyq77mfgatrefsaj3\n",
-      "PHID-TASK-4k5gqkncjczqm4ffrhqk\n",
-      "PHID-TASK-miessklckuwapsejbpw4\n",
-      "PHID-TASK-lyjnjxdzskobjhrp4tgf\n",
-      "PHID-TASK-6w7ima76rbpczpaozizw\n",
-      "PHID-TASK-xwv2yy4yt35rtaqt27uj\n",
-      "PHID-TASK-7v5fwi2od2mzskuipoyb\n",
-      "PHID-TASK-vqvckkamqnznu7z5ud6j\n",
-      "PHID-TASK-zzjrcgydauwz7h5g6ufd\n",
-      "PHID-TASK-zoij2t4he6jsr6wfqjde\n",
-      "PHID-TASK-wiwrmd5v2ykgptbszxoc\n",
-      "PHID-TASK-hwpwpa3athddhod7xlp4\n",
-      "PHID-TASK-uhuq2co3arbcvjn3js5m\n",
-      "PHID-TASK-fkhtpgjkzrvqucqxny7q\n",
-      "PHID-TASK-sw2uw4ekzaqwybdqmbq6\n",
-      "PHID-TASK-l6veaqa2gygvcgf2ywhf\n",
-      "PHID-TASK-ht3d5xeklsjuq5qulguj\n",
-      "PHID-TASK-rf6xvihdg3l2eowhdgrm\n",
-      "PHID-TASK-erliezrdqnohfykefn5r\n",
-      "PHID-TASK-o6h5thx2nxd7xpm2ferq\n",
-      "PHID-TASK-njwlhw4yezfqfiviad2b\n",
-      "PHID-TASK-s7xxo6pqgoai7qxiqran\n",
-      "PHID-TASK-4rlrewbrchltpzty4e37\n",
-      "PHID-TASK-rrfiavqqnofzrlok2ea7\n",
-      "PHID-TASK-zcmfiyirjhsjlqbiehnf\n",
-      "PHID-TASK-yygcicr6m5mpgdgpjccs\n",
-      "PHID-TASK-hk3rab5lb2jvryjrgppj\n",
-      "PHID-TASK-czooq62xjeisscbrllhg\n",
-      "PHID-TASK-3whynfwz7dddsiybr7nr\n",
-      "PHID-TASK-fa5biiyjbod7exipkpqs\n",
-      "PHID-TASK-p24deoao7z7cqo3jfmi7\n",
-      "PHID-TASK-hmeryxjc5h5ucj6zkjj7\n",
-      "PHID-TASK-25426wyep677h7baqpvx\n",
-      "PHID-TASK-mw76lciqtgo7k33dnexw\n",
-      "PHID-TASK-zn4qygjgu7jjo6j7f6is\n",
-      "PHID-TASK-coiafysv5fwnb2coli72\n",
-      "PHID-TASK-na7hdsgn5rcikyp6dgpv\n",
-      "PHID-TASK-l3samzhuiftku6aijqqt\n",
-      "PHID-TASK-sipzssmp2cg3ixlpwvsi\n",
-      "PHID-TASK-4ifg7mkk6tb64fjj6xsp\n",
-      "PHID-TASK-app5etuemqiwaqysxa3i\n",
-      "PHID-TASK-qwln7sdc2jjjjhdroshx\n",
-      "PHID-TASK-akpipntp36njlfgkew56\n",
-      "PHID-TASK-g5zcpdywgfveewvgyndn\n",
-      "PHID-TASK-yop2zgg7fofkoppm6y4x\n",
-      "PHID-TASK-66lb2jf7kuruqajpygry\n",
-      "PHID-TASK-u4ghwr7nh5cniopiuid3\n",
-      "PHID-TASK-p6hdrbkwl7jmyhc7wdyj\n",
-      "PHID-TASK-foy2pwxdiqiuemtnxzak\n",
-      "PHID-TASK-kdifvxztyisvsjamslc7\n",
-      "PHID-TASK-yqzsqc62wfjcfr3spvjk\n",
-      "PHID-TASK-oohwmpwpyrfuvog4u4ox\n",
-      "PHID-TASK-pxkrw7ecjvb7q433anxa\n",
-      "PHID-TASK-4o3l42xhur3szmao22jr\n",
-      "PHID-TASK-xbcm5bbrtpu22jkr7ofg\n",
-      "PHID-TASK-p6aosiypctjfd3m7mled\n",
-      "PHID-TASK-3dsaxavgxklzocfpg2pl\n",
-      "PHID-TASK-dh3tjq2uz3nbefcu74t6\n",
-      "PHID-TASK-iadcnxx6h6rf3uwphvzc\n",
-      "PHID-TASK-3jc7jvjjcdtgrshlnq7r\n",
-      "PHID-TASK-lemidsivs6ktavbh7gts\n",
-      "PHID-TASK-zbiughyq34hw6tacnlnj\n",
-      "PHID-TASK-njupimbksvxhw4nnmsfy\n",
-      "PHID-TASK-266a7gondg6gygyomb2r\n",
-      "PHID-TASK-tqdmz6elwsrngx5orrvl\n",
-      "PHID-TASK-jnxq7ir4c6munsrkbn2f\n",
-      "PHID-TASK-tzp63nj3bg2h6gjxrpwx\n",
-      "PHID-TASK-jer6pedsydbmctp5xlhb\n",
-      "PHID-TASK-ok3b6bw3cne4xry4dq2k\n",
-      "PHID-TASK-fvybwsx2pzn3o2pbtxx6\n",
-      "PHID-TASK-nwfeyfjfrxwame6u7ux5\n",
-      "PHID-TASK-piflhuji3l6moqmh3nbj\n",
-      "PHID-TASK-ocokyzlkygrkgdcs4rdx\n",
-      "PHID-TASK-eskw2sna4jhs2lvvjvcw\n",
-      "PHID-TASK-iw27jj4bhfweo22d2lg4\n",
-      "PHID-TASK-6nqkzsnqx67qeicoilm6\n",
-      "PHID-TASK-obbqrn6j222whjin4fm6\n",
-      "PHID-TASK-xzuyfy5phfxcgoae52f6\n",
-      "PHID-TASK-b2euwwfrbpmnfl2aq75y\n",
-      "PHID-TASK-tbgpmmiggp5mn7bvnvbe\n",
-      "PHID-TASK-jrdnntjfzxsr3v7pxbff\n",
-      "PHID-TASK-i3m3gsgv7zrvvcskhdat\n",
-      "PHID-TASK-sqgxilqkeecvprvfh7ro\n",
-      "PHID-TASK-xtwsiyvycjjuwkmu2mcm\n",
-      "PHID-TASK-czuwyblk43urnavypsbt\n",
-      "PHID-TASK-2hzsnhrqn3e44r3w5wpx\n",
-      "PHID-TASK-xsynpfa72ixj4q44cgdk\n",
-      "PHID-TASK-zi2tai4mmhmdntkaup52\n",
-      "PHID-TASK-zvx6cpsh2puavdxxft2q\n",
-      "PHID-TASK-i4afw6okkvtcnnnerpcr\n",
-      "PHID-TASK-bhfeaa4hp3iuxtp7inrp\n",
-      "PHID-TASK-alx56wytsjcuj4hvxv6h\n",
-      "PHID-TASK-qr4la5fjep3uvnewafhr\n",
-      "PHID-TASK-3qimgh7ycaviacztiyae\n",
-      "PHID-TASK-2fap3nvdrgza3a4h2sj6\n",
-      "PHID-TASK-vhisdvekk4sgvgkkuben\n",
-      "PHID-TASK-rifozrrb2mk5wki2qrw4\n",
-      "PHID-TASK-upsvylaxm2favfgmiub4\n",
-      "PHID-TASK-3mbtnybtpij42l625lvd\n",
-      "PHID-TASK-bsg3qk2puigbios7b56m\n",
-      "PHID-TASK-mutotkwptjvzfn2nuk4y\n",
-      "PHID-TASK-bp5lorruinm7xnzv76mb\n",
-      "PHID-TASK-2iww52jmzvuwmwgsjy5e\n",
-      "PHID-TASK-vrsv454ata26ui2zocei\n",
-      "PHID-TASK-vagtkpb7zm3ecw5cnsap\n",
-      "PHID-TASK-j3shvug7fft7t4wshe6d\n",
-      "PHID-TASK-hgicqduvx6exq6mle75r\n",
-      "PHID-TASK-76qxn5mqf3hcvdkgf2kt\n",
-      "PHID-TASK-o3u5ojlmiw3bdf7dgyiu\n",
-      "PHID-TASK-75uqqg6zbs3w4jxdyn43\n",
-      "PHID-TASK-smsvykwx7lxu2tyag7ye\n",
-      "PHID-TASK-jml4yae3q65u4srebbyl\n",
-      "PHID-TASK-jazf6d7oefzddss6mv36\n",
-      "PHID-TASK-idkrdic2vphpfwclosyo\n",
-      "PHID-TASK-uxbnfma4ejiksnkp2e7x\n",
-      "PHID-TASK-vsfkgcc5kyalos6vc4gl\n",
-      "PHID-TASK-p6hldnmgl7xtnj7zwjyv\n",
-      "PHID-TASK-murhom53ypttvsazncwz\n",
-      "PHID-TASK-cougiswjchh3cn6khldz\n",
-      "PHID-TASK-oxmalsbaodappytqtaoo\n",
-      "PHID-TASK-kk4vhnmofck2qdxtjn2o\n",
-      "PHID-TASK-lag2eyarvgkricqxqmeh\n",
-      "PHID-TASK-hfb6u2us7tcoc2xke4cf\n",
-      "PHID-TASK-5jn5rxhygbvz6pzdt2uo\n",
-      "PHID-TASK-jh7jzzemygqrgcfg25dq\n",
-      "PHID-TASK-az3twbgyfogcznpnnndd\n",
-      "PHID-TASK-qacmwzmv3ujwgmodf5y7\n",
-      "PHID-TASK-f2x5ytlsmyx24xetmj5s\n",
-      "PHID-TASK-hrsow4jckaq52vpprzud\n",
-      "PHID-TASK-y3luskovb4jkrwp3ep3w\n",
-      "PHID-TASK-rjnvooe4gramc7frhovi\n",
-      "PHID-TASK-c65rdnrtnbgfg3a46ubp\n",
-      "PHID-TASK-5pbz4o5r22cqczijgvqj\n",
-      "PHID-TASK-7erbrnp4x3oao3bdre67\n",
-      "PHID-TASK-peotted4ituorcv5mtdk\n",
-      "PHID-TASK-fgmvecleq7bixt5aoemb\n",
-      "PHID-TASK-7cd6puxwf2ufvh73gnet\n",
-      "PHID-TASK-hbxpldwjo7edx75sbrgd\n",
-      "PHID-TASK-vezbsxzq3qktiqaner6o\n",
-      "PHID-TASK-peieofedvf7rbivy6oia\n",
-      "PHID-TASK-yiyhc6t4upjvxr35iuyv\n",
-      "PHID-TASK-73dsmojov4fu5z4edh64\n",
-      "PHID-TASK-tlecjwjjkrzbeglszhlp\n",
-      "PHID-TASK-jqxpftgvocz6dbwkyo26\n",
-      "PHID-TASK-wfbwa6r6kerlfz6umih6\n",
-      "PHID-TASK-43hyj7572ppndylnp2wq\n",
-      "PHID-TASK-gpw7j3jiv4sk67tvdv7b\n",
-      "PHID-TASK-wg7j7pyuulwf75hox73z\n",
-      "PHID-TASK-innmgpodu5aq5mgfve6a\n",
-      "PHID-TASK-fsq7dtwwt7ruqbvnri5t\n",
-      "PHID-TASK-txytmd2sbsfb7usyegll\n",
-      "PHID-TASK-yhyqhzgc2jfbifybi6up\n",
-      "PHID-TASK-mvbvbyjoydgdze5uwazb\n",
-      "PHID-TASK-6xoak4ts4kf6g44ewytz\n",
-      "PHID-TASK-7fkwhekj4glhqvjvdax3\n",
-      "PHID-TASK-eru2tiwghisa2sl7pdsv\n",
-      "PHID-TASK-bw4tf22xsrw2meuuvmyr\n",
-      "PHID-TASK-6xsc6lb6uvcf633e32tb\n",
-      "PHID-TASK-kxjmckaitcfmwxa44pgn\n",
-      "PHID-TASK-mxnglgs5g63joubkufdc\n",
-      "PHID-TASK-cmzxtthtzpwj4eczkcbn\n",
-      "PHID-TASK-2egq3hlgvj5ljxkovvce\n",
-      "PHID-TASK-qttnmog5m4ro2nv4m5sn\n",
-      "PHID-TASK-duiplk7fkjkz4nppzcgi\n",
-      "PHID-TASK-vyxifsvid5dvxvr4vi6e\n",
-      "PHID-TASK-nicumpfbj5y55eeu3oq3\n",
-      "PHID-TASK-yny6sbrvi7mgfvctnaj2\n",
-      "PHID-TASK-7km7sjcw27m7salmhqyx\n",
-      "PHID-TASK-hlh4ejepruxcb5g2rrjr\n",
-      "PHID-TASK-jb33pbb73nuyy4d6ar52\n",
-      "PHID-TASK-pax76pmwwhkfmzx3qyu2\n",
-      "PHID-TASK-evnmq44e74m2oihqgr55\n",
-      "PHID-TASK-yuwu5opgb5rp2g46lbs3\n",
-      "PHID-TASK-lowef3zhz3so2jcgpngl\n",
-      "PHID-TASK-arynstjhbybir4k6knmy\n",
-      "PHID-TASK-x54eh7ootvdxv4yravzz\n",
-      "PHID-TASK-faneqy7veketsdzp7dgx\n",
-      "PHID-TASK-q3ldi6tymbhxe2lm6rjl\n",
-      "PHID-TASK-urypd4qwlje662u65qd3\n",
-      "PHID-TASK-x3hpjdsv6mi5u6x6aket\n",
-      "PHID-TASK-prw46t5ok4y7p3lhivye\n",
-      "PHID-TASK-yrvvt5gp7rnhtwez34gc\n",
-      "PHID-TASK-6tvdmfknnn6daqnwcthv\n",
-      "PHID-TASK-gm3iscenilyd5pim7stg\n",
-      "PHID-TASK-eo27t627sh27uj66uxst\n",
-      "PHID-TASK-2fasjdalcvfhpa6dgghm\n",
-      "PHID-TASK-xtbmxjggz7gkbjodpajo\n",
-      "PHID-TASK-o2wsm7xh6lrm5c2z6lwk\n",
-      "PHID-TASK-uwqdkdxx5tmkmhzfjwvz\n",
-      "PHID-TASK-s7lpkaw3xu6zlj3jjwqm\n",
-      "PHID-TASK-chdbjfofb5zihbj3xecj\n",
-      "PHID-TASK-aekjxzlbg6hbymq5ylwp\n",
-      "PHID-TASK-2qguei6bgca37llfakum\n",
-      "PHID-TASK-supxiuf2snjkiztaupce\n",
-      "PHID-TASK-woqxqv6iluugikztqpwo\n",
-      "PHID-TASK-5yndg4e2xdepto2tr2wh\n",
-      "PHID-TASK-p76q3pkvm3ujbswasdmd\n",
-      "PHID-TASK-soqe2cuy2qnpxktzzeed\n",
-      "PHID-TASK-j5vmxwhgpdua5wcyruej\n",
-      "PHID-TASK-dgumy74z3zd6vmd4zme2\n",
-      "PHID-TASK-c2lpx2p2cpizjy235cz3\n",
-      "PHID-TASK-fxifnazewrqgvu4gcnog\n",
-      "PHID-TASK-sqhibubgcam4rw6zg2im\n",
-      "PHID-TASK-fpwsjr2z43gzastjf6ak\n",
-      "PHID-TASK-qhw2xsmje3nm75l6hyqw\n",
-      "PHID-TASK-gpbnxuzghyxgmcl5cika\n",
-      "PHID-TASK-yfvk4vo7aqne3mus4xte\n",
-      "PHID-TASK-hmqwa7xe2lrqdvsrno4s\n",
-      "PHID-TASK-xfimimrnkl7a4samm5xn\n",
-      "PHID-TASK-wegjd34ahvbrxxjftgql\n",
-      "PHID-TASK-tobiwpavuldjyxvbgv2n\n",
-      "PHID-TASK-t6gmkam4z4t2upv65tdm\n",
-      "PHID-TASK-hlzqzpsz6w4c5bzdi4i5\n",
-      "PHID-TASK-wxrtx43jaw7tpwg7bd7l\n",
-      "PHID-TASK-tjkkepz2glxx6dypkoab\n",
-      "PHID-TASK-3o2r6t4wgzcrj2zuvlkx\n",
-      "PHID-TASK-rtdocuudreaisizzfzfc\n",
-      "PHID-TASK-yja5lvncvpyih4flmthe\n",
-      "PHID-TASK-5dur2e4zsk6uu6tgyilj\n",
-      "PHID-TASK-np6rbo55hknbpzfqqpzh\n",
-      "PHID-TASK-6gtwxeyvjyc66bmigmaz\n",
-      "PHID-TASK-llwgzv3tlimidw6znewt\n",
-      "PHID-TASK-2krxsenupth53kalib2f\n",
-      "PHID-TASK-2c6nxv3lw3wwpzottiyw\n",
-      "PHID-TASK-6gmrv6d3roeydcelmnyh\n",
-      "PHID-TASK-sgoczofqmqi4d2v3nizb\n",
-      "PHID-TASK-ymyyonb4npnvudsmny5o\n",
-      "PHID-TASK-tuxjn2c5glhsmp3uc4wx\n",
-      "PHID-TASK-zmcluk2i4zmrgthivhmp\n",
-      "PHID-TASK-ncbhpeaekx466zjaq6at\n",
-      "PHID-TASK-twc6oxttivmbeivgzrtf\n",
-      "PHID-TASK-h4m4lscojm4qbgfbthk7\n",
-      "PHID-TASK-rqmz2t77d5756bkn77xp\n",
-      "PHID-TASK-flyugauog5dd6v4unsi7\n",
-      "PHID-TASK-uonptigegjibdzpnxm6t\n",
-      "PHID-TASK-e3w6zshniruifvkfks6d\n",
-      "PHID-TASK-x62ljudld7jl6ovaojqy\n",
-      "PHID-TASK-2aag2u6vtt53677npv2w\n",
-      "PHID-TASK-a44mepuutxluyfml3j5g\n",
-      "PHID-TASK-77gxvnl3q3ubn5mtomzv\n",
-      "PHID-TASK-devcuj6oy6zi6ehpdryq\n",
-      "PHID-TASK-wejuqtqqsktmkabwdqxr\n",
-      "PHID-TASK-evrokwipdbub7qma7gbx\n",
-      "PHID-TASK-hjiff2rve77sfx43cqpe\n",
-      "PHID-TASK-23kytwe342kbpmgthgmt\n",
-      "PHID-TASK-luvruzm46k3dlau5z6wg\n",
-      "PHID-TASK-isjhm5lhynj6lgf5pve2\n",
-      "PHID-TASK-sojeywgrcg6knl7y5dzy\n",
-      "PHID-TASK-utpcvnudjvnmrf5n2mpi\n",
-      "PHID-TASK-k7ndkr4spt2bt7mgctja\n",
-      "PHID-TASK-xmwils3vchvzzdbgegip\n",
-      "PHID-TASK-paw5zcxophppwlal7wbs\n",
-      "PHID-TASK-d3c74irtdh5bydamc36k\n",
-      "PHID-TASK-urgeoycg3qunrfzhjulb\n",
-      "PHID-TASK-osvgc2rrhwadyji7x6hl\n",
-      "PHID-TASK-cz3rtgfxbykofx4kvsia\n",
-      "PHID-TASK-wt57zr2htyhkzzgovt4f\n",
-      "PHID-TASK-5vjdcr5yqcamhgt2wymw\n",
-      "PHID-TASK-vcg3kzlidjqghgcegqdp\n",
-      "PHID-TASK-4kpfmliccubzixbhguff\n",
-      "PHID-TASK-bvr7nre4pjr3pofdoq6o\n",
-      "PHID-TASK-kjvvoq653qna4dsuzabo\n",
-      "PHID-TASK-xmktwdgi2pttbrlspf73\n",
-      "PHID-TASK-v6lbymq7s3dov27etrxo\n",
-      "PHID-TASK-hwrlm3m5llfqtt2m3frc\n",
-      "PHID-TASK-re6vwytcthwmzpbqbfoy\n",
-      "PHID-TASK-xnyble5ko7cj77odceh5\n",
-      "PHID-TASK-dunm4q3cjegrnqlbrlnx\n",
-      "PHID-TASK-7fjtjpvxdar4zf4p2zn5\n",
-      "PHID-TASK-a2u5v6wtvnxub3uml7uz\n",
-      "PHID-TASK-cf7sodft5apnwjetm2ek\n",
-      "PHID-TASK-67cctylbfobidrbv3hfd\n",
-      "PHID-TASK-tihohw65um5nqiof2m35\n",
-      "PHID-TASK-scoh4xqxum72mhxquk27\n",
-      "PHID-TASK-qsgnrw34off5kbfx52lz\n",
-      "PHID-TASK-ssmxrwedkkwjcdz3pkfv\n",
-      "PHID-TASK-z7lqudiqsx3toqxfmyrh\n",
-      "PHID-TASK-setrj27w67t7gktol4z3\n",
-      "PHID-TASK-au5g35tuuylapsk7eubl\n",
-      "PHID-TASK-qetvgvrqjisxdxa4u7np\n",
-      "PHID-TASK-32waecquxrqyav4wai64\n",
-      "PHID-TASK-2ik4qr5eikvbxsyx7ihu\n",
-      "PHID-TASK-oxbr6v2mpytzioyqp4ma\n",
-      "PHID-TASK-jrcdwxsp3bh53xuhlofi\n",
-      "PHID-TASK-nhmtatolxkhjgn54hngt\n",
-      "PHID-TASK-uzavsh7jiyrspclcykx3\n",
-      "PHID-TASK-vexowcgnl3zfx2wx744e\n",
-      "PHID-TASK-j6fh2cs3wbb53aewhrnh\n",
-      "PHID-TASK-irwbawwd34nibsp6cr6n\n",
-      "PHID-TASK-iybf6jspgbrl4k2sojui\n",
-      "PHID-TASK-urbyde4ziyfvfk6kwccx\n",
-      "PHID-TASK-wljrwrl4avglyuy7j5wi\n",
-      "PHID-TASK-n73esked2uknidkk6dcc\n",
-      "PHID-TASK-gsdjjehs7duzg6p7efj3\n",
-      "PHID-TASK-nngads3asyp22g2mfznd\n",
-      "PHID-TASK-pwgzlrz42g3jw6le42cr\n",
-      "PHID-TASK-gglnxexerzlpc27dmjou\n",
-      "PHID-TASK-3l67fot6jvz627mticzv\n",
-      "PHID-TASK-xm2mk6rfi3neidlarp5g\n",
-      "PHID-TASK-g4sqyb3luctzxk2bog3r\n",
-      "PHID-TASK-sxtng5ghv2nfoij5k4cf\n",
-      "PHID-TASK-zetzc2ngsimcakpv3og3\n",
-      "PHID-TASK-lgqyw65pbs63v6sqiv4j\n",
-      "PHID-TASK-y2ze4622w2dwciygcnjb\n",
-      "PHID-TASK-lfzhnijm7hbfk3gvny5g\n",
-      "PHID-TASK-2ixdh6dr2flnvqm77pxq\n",
-      "PHID-TASK-3ukvlx3ldefokpkbnka7\n",
-      "PHID-TASK-aj6cx3ygftk3motxe7xa\n",
-      "PHID-TASK-peyhafaf5o5etsa2l5gh\n",
-      "PHID-TASK-22uqtxwdglxq7a27zivv\n",
-      "PHID-TASK-r4igd57u7iobs63xxnge\n",
-      "PHID-TASK-hlivvhccoogrytjztz4v\n",
-      "PHID-TASK-gx6gtxwaujgia6xrg3cb\n",
-      "PHID-TASK-dr7acvvfxto6plbboi4q\n",
-      "PHID-TASK-b2w334geyn6xehtamxqg\n",
-      "PHID-TASK-wfyoixdybjp6v6matvrj\n",
-      "PHID-TASK-rdtadfeyhzed33gkdvtq\n",
-      "PHID-TASK-x35ncnimbtqjngphowun\n",
-      "PHID-TASK-ptvgwefznutknxfidbsh\n",
-      "PHID-TASK-x2js3cwk25pg7q5wraqv\n",
-      "PHID-TASK-hrzcgmgl37xcbzoguhtx\n",
-      "PHID-TASK-4zyamq2uzqay4psf2mpk\n",
-      "PHID-TASK-3unnspcgavr6xhail2er\n",
-      "PHID-TASK-remttdefwzofqhhvwg2h\n",
-      "PHID-TASK-bh5fnqsfor56ucbo6du7\n",
-      "PHID-TASK-2xatbyajrpglcczqz7gu\n",
-      "PHID-TASK-btvs2s2ihxdsixm3lt3a\n",
-      "PHID-TASK-br5a45fin6czazh3islo\n",
-      "PHID-TASK-k2h6lp7jsa6s76ca2dx4\n",
-      "PHID-TASK-a3rsqh3622rlfp4zpwul\n",
-      "PHID-TASK-ivp5hiloykrq3ijnlcsd\n",
-      "PHID-TASK-ovf2mbalohzcr6eav5wb\n",
-      "PHID-TASK-sdgsqmliomodrzl3kegc\n",
-      "PHID-TASK-x4n4ij754asqbc6h7jmx\n",
-      "PHID-TASK-ckia45kqd4ianv3wg3rp\n",
-      "PHID-TASK-rezh53p2xm2bwsgbhpo6\n",
-      "PHID-TASK-jetfcrjzmljadekjnwqj\n",
-      "PHID-TASK-3itlwc5mvcohetlwjnl4\n",
-      "PHID-TASK-ljyxu64angwfdp5jfokm\n",
-      "PHID-TASK-3jv4morfdfduiqmadob2\n",
-      "PHID-TASK-6pa7blfmoh6dhhydjpvh\n",
-      "PHID-TASK-6x3yrgo5cawaeou4wbls\n",
-      "PHID-TASK-hb3ednf4d3ajqz4ggzlz\n",
-      "PHID-TASK-yd4kojpa26xd52r2dadr\n",
-      "PHID-TASK-5ngxnua7ghoiwyqztxbu\n",
-      "PHID-TASK-o2nuawja3gd5ensyabpx\n",
-      "PHID-TASK-ne77k6a4n7agmzuuryr2\n",
-      "PHID-TASK-2jzgntengke75ccufbeh\n",
-      "PHID-TASK-qwgyzixmq7444faqzt2k\n",
-      "PHID-TASK-u3fli75nyhvezrtxd2vp\n",
-      "PHID-TASK-wfaki2636ucppxoiacm4\n",
-      "PHID-TASK-rurgi2fk663rrehd4j3x\n",
-      "PHID-TASK-rcih7yd7sainywzff7di\n",
-      "PHID-TASK-blqrlqqm7xzdi5yg7pna\n",
-      "PHID-TASK-rqg7uqc7ixojj2plkvbr\n",
-      "PHID-TASK-uk3slh6vbmq3xu4fvsu3\n",
-      "PHID-TASK-f6bgxahe6w7alqbxqvv6\n",
-      "PHID-TASK-hrnl7scbkqiphhkzetoj\n",
-      "PHID-TASK-edczq7heipb4q3v2tcxp\n",
-      "PHID-TASK-abnrntzw5wtc5wukwim2\n",
-      "PHID-TASK-ix3up4zzzosiimtj4nop\n",
-      "PHID-TASK-6u4gabtaq5rfue7qj2wa\n",
-      "PHID-TASK-w7b6jdh4p5xzbufd7owv\n",
-      "PHID-TASK-eng4eygt5qljaa7eds7p\n",
-      "PHID-TASK-k3frejgdyxsgnsdn5zqw\n",
-      "PHID-TASK-wkcjdg26ppvadj2qcmne\n",
-      "PHID-TASK-u7wmfggaowz3nwqsib4h\n",
-      "PHID-TASK-aa6mqfnkyrurwc3qf3hi\n",
-      "PHID-TASK-kqf3ft6lr75jkeflzwo7\n",
-      "PHID-TASK-3gsxa566npjtwodxt42a\n",
-      "PHID-TASK-uhvgmgrdscjhwyvdb474\n",
-      "PHID-TASK-3jtahafvmd46fufkeey7\n",
-      "PHID-TASK-utd4dwndfqs2xvimd262\n",
-      "PHID-TASK-5zoyxx73z2lluiw4akkr\n",
-      "PHID-TASK-d2yxda424o7uk6liddmf\n",
-      "PHID-TASK-xzvyjiqogzwcgi53p5vo\n",
-      "PHID-TASK-ku4qzbqeu24wzpgt76qw\n",
-      "PHID-TASK-jleaptwiihwbszn24ore\n",
-      "PHID-TASK-dx53p7272wo7nmcymv63\n",
-      "PHID-TASK-hzqhjjti55dwecogv2dm\n",
-      "PHID-TASK-zznxlmtpisyv35ph3vdy\n",
-      "PHID-TASK-444jjina7afgsdohllry\n",
-      "PHID-TASK-kfwpka7h3inptj65moc2\n",
-      "PHID-TASK-szhrrt6yhyfzihjpjade\n",
-      "PHID-TASK-5azsp7uzzucqdg6yukh3\n",
-      "PHID-TASK-z2d3f6p2ejg2badg7nph\n",
-      "PHID-TASK-fypqepsh6l776gwf6e2h\n",
-      "PHID-TASK-e532vezhqz47vwem7t6o\n",
-      "PHID-TASK-advminout52vzy4o576h\n",
-      "PHID-TASK-ic44hmdblr4rvvctpw5r\n",
-      "PHID-TASK-6fjxmlk42cz5vwd46onb\n",
-      "PHID-TASK-bdmcqwt76vyccvojptxl\n",
-      "PHID-TASK-nk4g5ukj6fdtvpowneko\n",
-      "PHID-TASK-utuehsjkuc2a6rnd6nid\n",
-      "PHID-TASK-djmwv2eookrt5vpvsei5\n",
-      "PHID-TASK-5xlpbmlhjpmu5hgvb6ks\n",
-      "PHID-TASK-2lh4x2ggoyfra3mal2dj\n",
-      "PHID-TASK-5djpuvo4wkwj32snxeof\n",
-      "PHID-TASK-6rg4t2epelfvjth52scv\n",
-      "PHID-TASK-kl7wuwhazni6b4o7mq2g\n",
-      "PHID-TASK-2a4evartaeoqgwykf6un\n",
-      "PHID-TASK-e5hoozp2bm6dugby2g2l\n",
-      "PHID-TASK-l5v5vrwex3hz2ct4owi2\n",
-      "PHID-TASK-ld45zmxdo6zli7e3kkzm\n",
-      "PHID-TASK-hahseqx35ztkj6fz5cfs\n",
-      "PHID-TASK-faekguqj2f5hrdp6337k\n",
-      "PHID-TASK-5soltwr3wdlryrbxkfmr\n",
-      "PHID-TASK-5jyi6gfrdcofdg2qdtbv\n",
-      "PHID-TASK-orpzganqdg7lbcpdb7jk\n",
-      "PHID-TASK-lp6gjih6erk6yxlyvwlx\n",
-      "PHID-TASK-jbatrq3ogdwn3vlvgukn\n",
-      "PHID-TASK-mmjlnjyrfskgvyw6dlte\n",
-      "PHID-TASK-qfttw2uqh62xx2xebpyu\n",
-      "PHID-TASK-pyvddazcokg6hnj3x73g\n",
-      "PHID-TASK-nfrlo5myv3v4eprweid5\n",
-      "PHID-TASK-tsdm6dyf3irbaneuouwo\n",
-      "PHID-TASK-iuk3q3w2mokdzao6ks7s\n",
-      "PHID-TASK-gomohetkd7ro7h36m2z2\n",
-      "PHID-TASK-ht57jl47eqhrn5mu6y4k\n",
-      "PHID-TASK-floz7aecowu5ipopiscf\n",
-      "PHID-TASK-k65a4qbdt2vssa5txndo\n",
-      "PHID-TASK-yyipeqjrkozgykvwcduy\n",
-      "PHID-TASK-puc2xw4bd2b2xsnoq5zd\n",
-      "PHID-TASK-fvgll6ju7di7hlztbvdl\n",
-      "PHID-TASK-4ptlg2ito6vzer5kk57s\n",
-      "PHID-TASK-e33lumruqobfcwjjasrw\n",
-      "PHID-TASK-5bjxxerf7yoz2uejrrao\n",
-      "PHID-TASK-zhhx6gkxdzizm66cix7v\n",
-      "PHID-TASK-psfncojk42sp2n4fkx6z\n",
-      "PHID-TASK-qkdhag2mz377tvfw5d6p\n",
-      "PHID-TASK-p57423cc4ujmx5lgadoy\n",
-      "PHID-TASK-2kwqewofv75ewmmj7vjy\n",
-      "PHID-TASK-waltxxgf7klwuydmvsrb\n",
-      "PHID-TASK-v5onbdu6jehxicnrwhag\n",
-      "PHID-TASK-4qeseygjikdfuaqbrolu\n",
-      "PHID-TASK-zvn2wduyu4ldd2i4hote\n",
-      "PHID-TASK-lwcxwsesbmhskncgd577\n",
-      "PHID-TASK-u54ktpl5srhndkfxtln2\n",
-      "PHID-TASK-77b6hmihb7n4klffjkkg\n",
-      "PHID-TASK-442235joepfyed6ueex4\n",
-      "PHID-TASK-bmlzjgktkdmjeslkstm4\n",
-      "PHID-TASK-ohfy6lgpehsflydjpak3\n",
-      "PHID-TASK-nu5xspbn76mwgtd5gyqq\n",
-      "PHID-TASK-7od6d3icidxgdzhb3ji2\n",
-      "PHID-TASK-jnmodmpu2b6kl3sbrqya\n",
-      "PHID-TASK-jkzbviyi473qzvp6r5kd\n",
-      "PHID-TASK-enbovi37zxerllyc24yd\n",
-      "PHID-TASK-xaopuar5atia63pv7slc\n",
-      "PHID-TASK-xtaz4xuglw6bqqvscwvu\n",
-      "PHID-TASK-6hnqd5mtozjfcpv3i3hp\n",
-      "PHID-TASK-4itcjtumhnjkxw77si2v\n",
-      "PHID-TASK-st45mendifimrc7daviy\n",
-      "PHID-TASK-dobhhdqzp556tigyqgiz\n",
-      "PHID-TASK-k7zaj564v4tdljuzqups\n",
-      "PHID-TASK-rltauqohawt55lchrl4d\n",
-      "PHID-TASK-n4wu3wvhi3ff7lpioygq\n",
-      "PHID-TASK-u5svmf673m5i5zmpc5ng\n",
-      "PHID-TASK-dqhaia75vamsl3rmnltp\n",
-      "PHID-TASK-caaaahazbcu7qa5ilv5p\n",
-      "PHID-TASK-e6jsiulpiw5hjbfetpvc\n",
-      "PHID-TASK-x2p7hqn3esqtuse7scxc\n",
-      "PHID-TASK-3q2oh7zhspz3z3iusr7s\n",
-      "PHID-TASK-nu7ycsxlgziqvsqjceef\n",
-      "PHID-TASK-ekrm36buebgsetzut4ox\n",
-      "PHID-TASK-czceip6xh6hv5epzval5\n",
-      "PHID-TASK-zlsf4q2llhdhofvqvfe6\n",
-      "PHID-TASK-cvdip7jn2gnnatmluyma\n",
-      "PHID-TASK-aay645uqkadlmx7yyijx\n",
-      "PHID-TASK-rihr5cwlyy5m2utltcfx\n",
-      "PHID-TASK-74pysrayjf4h6tgvqp3q\n",
-      "PHID-TASK-ftd3677o2fooxu3axvei\n",
-      "PHID-TASK-ek6i77jrst3xdd4rkvxd\n",
-      "PHID-TASK-bszbfrxj2jltj2nwse7z\n",
-      "PHID-TASK-wlzgvsmjnsumbns2rmzg\n",
-      "PHID-TASK-gnfxkxgge6jy5yegpul5\n",
-      "PHID-TASK-a532f3kpz7dqjttdx5l3\n",
-      "PHID-TASK-fyzrdfvjxxuw2ddhhqeq\n",
-      "PHID-TASK-wdsm7d6qbu5bt75ivacj\n",
-      "PHID-TASK-kckucons2r46xrc5a3xw\n",
-      "PHID-TASK-6tl7tgozycm2vk3qmwxb\n",
-      "PHID-TASK-ts644nvpin7nzxjkmyqi\n",
-      "PHID-TASK-woa5qgdd2kuacxa4kj4z\n",
-      "PHID-TASK-amg4rcgoazznjnphzquh\n",
-      "PHID-TASK-uv7harsaw6uegtz3aesy\n",
-      "PHID-TASK-iedxgxzmnkj5w6tca2tu\n",
-      "PHID-TASK-bcsjdeldob7pksf2jsjk\n",
-      "PHID-TASK-2ccuu4qtfxpytbz5rhoh\n",
-      "PHID-TASK-kpjfjaghlnt74hhgi5cv\n",
-      "PHID-TASK-nu4jynpne3safxk75oss\n",
-      "PHID-TASK-oe5ms72gy2uu6mjaaqe6\n",
-      "PHID-TASK-jggh6lkqz7csocnbz4oo\n",
-      "PHID-TASK-c27kk34icz4bpyrlvjpf\n",
-      "PHID-TASK-zlieutzkthf2674wairs\n",
-      "PHID-TASK-g7bdag3ouhcedtw4w7px\n",
-      "PHID-TASK-lfmhdqf2fp3fy5b24chh\n",
-      "PHID-TASK-bd7sldgzh3ssrxvsie4v\n",
-      "PHID-TASK-mawqu55vtwhutyac6fl2\n",
-      "PHID-TASK-juabtt3jtkdtozbvwjyi\n",
-      "PHID-TASK-jjbnp6qzxgfufzean2ux\n",
-      "PHID-TASK-ad7ys6ayrhumzmd7s5np\n",
-      "PHID-TASK-6svejr4dlr5a76d65y4o\n",
-      "PHID-TASK-zq64ne5etzq4kohyhblm\n",
-      "PHID-TASK-axpv35jfsr4hb5ftvtac\n",
-      "PHID-TASK-rw3z2ncxhjiapf53g2dj\n",
-      "PHID-TASK-tx3tnhbz5553iuofuywl\n",
-      "PHID-TASK-2rmkxa2is7nps4mba7xt\n",
-      "PHID-TASK-rvudp57rsxh5tyqambv6\n",
-      "PHID-TASK-ffq5hsenml5yhfful4jm\n",
-      "PHID-TASK-rwcczd2xhqirmziyxmyi\n",
-      "PHID-TASK-2jqvp6o5rukgut7ypeps\n",
-      "PHID-TASK-5xjx5bhytilus36xtsqu\n",
-      "PHID-TASK-oamnqxetj6ams3volnvi\n",
-      "PHID-TASK-s4yzmexfuvbf2g7dwcux\n",
-      "PHID-TASK-zvu24wr6gapdwg6aoskt\n",
-      "PHID-TASK-gbmahf2nvdgcfrdtetva\n",
-      "PHID-TASK-2c2kd5h5swrnoe5i4rnh\n",
-      "PHID-TASK-rchunvbnr26iqkmvxxy5\n",
-      "PHID-TASK-flp4acupxj7fjvq4mgfw\n",
-      "PHID-TASK-iqulbj2ddfudaregj3jn\n",
-      "PHID-TASK-3gju4wuwcydtmtdjrzrr\n",
-      "PHID-TASK-yw4b4pmbrw2obgk33kph\n",
-      "PHID-TASK-ac2zsjomwjgmhkoayiuf\n",
-      "PHID-TASK-otgwycebw25ej3on4cg6\n",
-      "PHID-TASK-yhsvhbgjvy4nwgcogikw\n",
-      "PHID-TASK-3y4bzefvz74zyiylvmg7\n",
-      "PHID-TASK-kcdt6evoxb7dyclasvhr\n",
-      "PHID-TASK-nq5cnmniruskng2atihr\n",
-      "PHID-TASK-3c2zptsonkrp7vi7nbpx\n",
-      "PHID-TASK-5pgxr7pnqmtyrolp2ztp\n",
-      "PHID-TASK-6xolie2zefzogwp7ndhu\n",
-      "PHID-TASK-v376iz64hfsix2c3s4lh\n",
-      "PHID-TASK-p7uyyr5xswg5yrofkqdd\n",
-      "PHID-TASK-qoj6ymfjm5pgvzklinrg\n",
-      "PHID-TASK-bi34wimyectesmdx6jar\n",
-      "PHID-TASK-w6vt4utuqyldv2cmmund\n",
-      "PHID-TASK-iqrozz7c5dzdomgukors\n",
-      "PHID-TASK-alhxfplatrwdgk43xfb3\n",
-      "PHID-TASK-s4vdrbpgig26i4hixati\n",
-      "PHID-TASK-7qh467vyga6czchrrd2p\n",
-      "PHID-TASK-i33x4h5mjnat262gctqt\n",
-      "PHID-TASK-5tsqijmuo4ilr7nqgjnq\n",
-      "PHID-TASK-2dy4aao545tjoscghlgd\n",
-      "PHID-TASK-dlmffyeaeajaau5cpsge\n",
-      "PHID-TASK-futqy7nlsvxuqr4dx2cu\n",
-      "PHID-TASK-64xilll6eo5zib7plcyu\n",
-      "PHID-TASK-667pdzsnat3vywzbk5ru\n",
-      "PHID-TASK-kh62mq4lhvjr4fgfwe22\n",
-      "PHID-TASK-cmqoovhbvvqbxuay3bwi\n",
-      "PHID-TASK-jc3gqyo3pxpfmohz2253\n",
-      "PHID-TASK-fkv4g3aqxijtbgft56ij\n",
-      "PHID-TASK-gs7sqst6umknljvlszmu\n",
-      "PHID-TASK-nwx24kr2omo3papjy3ml\n",
-      "PHID-TASK-ekjvtpnzqj4imqhj22ob\n",
-      "PHID-TASK-nfr2zvfwe5lwozeia6mm\n",
-      "PHID-TASK-6bfwstz2ygurnkr45nkj\n",
-      "PHID-TASK-edh3xjjr7fz32wcyfzho\n",
-      "PHID-TASK-ddcfyypc3d3cbv33i3u4\n",
-      "PHID-TASK-gxjcazoxkhshpy57yk43\n",
-      "PHID-TASK-cq5fibwchbc6tbp3nqih\n",
-      "PHID-TASK-qj4gnvod7alfvonyqkys\n",
-      "PHID-TASK-czjybdfyzr6v25qeuy65\n",
-      "PHID-TASK-42m5jdfxp7jxtni7uvzn\n",
-      "PHID-TASK-6mc64lhux5u37tjrwhgt\n",
-      "PHID-TASK-lir3hgqiu4i4u7zzavcu\n",
-      "PHID-TASK-v3zkwy3tg4leghjf72lu\n",
-      "PHID-TASK-s4ok5yjksrgckoh7pb4g\n",
-      "PHID-TASK-xb4vn67r37nss6carg4t\n",
-      "PHID-TASK-iiy3kce22e4pguynjf55\n",
-      "PHID-TASK-pxmtpggakccpl77xndne\n",
-      "PHID-TASK-joglrkxpvi7xbxra2nb4\n",
-      "PHID-TASK-4wl4oxtvtviyvxfc5oan\n",
-      "PHID-TASK-235ze5es2nor6ps5ebbv\n",
-      "PHID-TASK-qy3qgp5iqhli5t3ezwmr\n",
-      "PHID-TASK-c4o3u3guy4bzz3drfvag\n",
-      "PHID-TASK-iplno7nvlo3lydwjjepq\n",
-      "PHID-TASK-7kyxrtyxcyoydu6uyyz6\n",
-      "PHID-TASK-a3rrdosrq4m3cjifkopd\n",
-      "PHID-TASK-kawtquvxo6egab2fazwx\n",
-      "PHID-TASK-uccadm75mlxcgmk4xnec\n",
-      "PHID-TASK-eyop3dml22vuj2xt5thb\n",
-      "PHID-TASK-epbhwclyvevd6ywuakhx\n",
-      "PHID-TASK-hhaov2ntlzzdbxxlqyat\n",
-      "PHID-TASK-ycmbmogx7itnsveopvs4\n",
-      "PHID-TASK-vtl6oy2eryypamslyqf3\n",
-      "PHID-TASK-p6ujqrof7r3kr32ikdjk\n",
-      "PHID-TASK-l5466yh2wfhphliediki\n",
-      "PHID-TASK-4cw53y6ozxxq4jifc5pd\n",
-      "PHID-TASK-wio2msjxwwllpptk2lsk\n",
-      "PHID-TASK-6w5hbvxithekehcvu66c\n",
-      "PHID-TASK-63ow7n2ozd4m65ls2xnq\n",
-      "PHID-TASK-7dclqnnm72xwnpvu2eq7\n",
-      "PHID-TASK-ebuzshnkdnhhawwjczws\n",
-      "PHID-TASK-studawgsnaudqrhmhjyt\n",
-      "PHID-TASK-qnn2vzzsqhnziozjaxbu\n",
-      "PHID-TASK-cnqs3vwq6pny7mken344\n",
-      "PHID-TASK-6imkll3gv77iihieqgvg\n",
-      "PHID-TASK-sfyrbpff7z277arpuv5d\n",
-      "PHID-TASK-j62lqv2pnnbnbgw7ja53\n",
-      "PHID-TASK-5juvbbzvkfwawhcrnc5e\n",
-      "PHID-TASK-fsxmbv5x3nocq46ayz64\n",
-      "PHID-TASK-zxmvdaa5bbdoniada2kf\n",
-      "PHID-TASK-cvfoo26a6vgdda4p5l74\n",
-      "PHID-TASK-6jndi54ckbh2pmkgvgw2\n",
-      "PHID-TASK-a4rtuxfqfzt4t5rmm2ac\n",
-      "PHID-TASK-cdonwzrog6i3xfchvyc6\n",
-      "PHID-TASK-cfl3njg4dbpxcmrct57o\n",
-      "PHID-TASK-5gjtponbzcvgfibouvua\n",
-      "PHID-TASK-llsmiww6l77wds4q4ajz\n",
-      "PHID-TASK-fe5hswi3ghhljkcsvvmj\n",
-      "PHID-TASK-ff5dovr2nj7hbi4mfk6d\n",
-      "PHID-TASK-rvzy7u46557pyglomvpy\n",
-      "PHID-TASK-r2gtjg6dw22voeqzade6\n",
-      "PHID-TASK-4tie5um47m54nxlowc4v\n",
-      "PHID-TASK-deyxxgilo6bu43xrinwb\n",
-      "PHID-TASK-2scgn55flrrhzwl72ldr\n",
-      "PHID-TASK-elatzf7sipmoeh7h3gfm\n",
-      "PHID-TASK-okbzzhxdfdpwr6xdxdko\n",
-      "PHID-TASK-lyauywwlebuzz4wjazr5\n",
-      "PHID-TASK-cmm2l4x3yrjzyxs5v4rl\n",
-      "PHID-TASK-aulut6cxxmdw4srpyjpu\n",
-      "PHID-TASK-adfbbfgylcnmev6236w2\n",
-      "PHID-TASK-4wvfrqahqjzbkpjnaxd4\n",
-      "PHID-TASK-sg2l7bjtavldgjqjhg4m\n",
-      "PHID-TASK-h3rnvqmaajhu7cd26sul\n",
-      "PHID-TASK-b2kjds44fcmdnsoqczzm\n",
-      "PHID-TASK-vkbfyitznumudqoxqfgs\n",
-      "PHID-TASK-pxydfaaecdb2drrqo3x6\n",
-      "PHID-TASK-cgka64ivffbox23apkiw\n",
-      "PHID-TASK-gyyhelxas56x6xvw7n7w\n",
-      "PHID-TASK-qlnckdanskw255gs5et4\n",
-      "PHID-TASK-twqcomuca3vkpbi4cgb7\n",
-      "PHID-TASK-2io5oqagajkj54tjjrwx\n",
-      "PHID-TASK-gxhvf2p6374tnbqf755k\n",
-      "PHID-TASK-ahuroh4hw3ltw7jphxcw\n",
-      "PHID-TASK-3nqxc32ajmzpi3hsotvq\n",
-      "PHID-TASK-nuycumir3hop5ekks7h2\n",
-      "PHID-TASK-3zamatwiubewzrfjcxeq\n",
-      "PHID-TASK-p565vznerestdkazvkox\n",
-      "PHID-TASK-yigtzgsn2qahxek7rusl\n",
-      "PHID-TASK-tjsegrcnpxgmtmoqmaq2\n",
-      "PHID-TASK-qp5fiwrkazudpv3vzwkc\n",
-      "PHID-TASK-3egehmh4zidndvgzwfvm\n",
-      "PHID-TASK-o7phiemau5qvzpjncsca\n",
-      "PHID-TASK-orropflowqhqpd4oiqpd\n",
-      "PHID-TASK-k5farhnvyfzzpgjvizgv\n",
-      "PHID-TASK-xkubjhuxj6ibkrx7jfgp\n",
-      "PHID-TASK-gchq7jmbvglbydxeihay\n",
-      "PHID-TASK-dsoezmplcqkvtg5il36e\n",
-      "PHID-TASK-2zikzspgdiyrdhq43hy6\n",
-      "PHID-TASK-nxxo6xoo5y7bzqx6ntg5\n",
-      "PHID-TASK-hzbsw24557jvqnw3xxby\n",
-      "PHID-TASK-25trlvhkq536lvbbruzl\n",
-      "PHID-TASK-vggdfu44niwggkew2ust\n",
-      "PHID-TASK-5sy4lbhaku6tjpejlwmy\n",
-      "PHID-TASK-py5gbrzeyuwgfnhmvab3\n",
-      "PHID-TASK-25agkmu2ndsyxxwmvqos\n",
-      "PHID-TASK-4cyyyuqcl5m5zuvtdeym\n",
-      "PHID-TASK-l2jl4edzrpyacaksfsyv\n",
-      "PHID-TASK-jvt3xyvqjt3cysi2vihe\n",
-      "PHID-TASK-bsy6cd23dxzzu4de3gqm\n",
-      "PHID-TASK-xgahiq6goif4ltykeqno\n",
-      "PHID-TASK-p4piwpm2qv7ndud2jr4x\n",
-      "PHID-TASK-5s7zqldna73gv3hkyshd\n",
-      "PHID-TASK-rmisq2mh4lmql7yzicx6\n",
-      "PHID-TASK-p6lbsrsy4c6xtsnzfnbc\n",
-      "PHID-TASK-47vdxcoqpdotzl5weohn\n",
-      "PHID-TASK-7z4tlyfijoeek5deckps\n",
-      "PHID-TASK-n3jah3fg23mapojunl7u\n",
-      "PHID-TASK-gy7d2blzfo6x6blcrzsj\n",
-      "PHID-TASK-6ixpggv4pjhmvx5zdw23\n",
-      "PHID-TASK-dbb75rdjycfheqcgaqvh\n",
-      "PHID-TASK-dirtzibr6cqkhuru3pvp\n",
-      "PHID-TASK-lvbwtwmxsjk452ye6dto\n",
-      "PHID-TASK-uj2x5dn6fe36q7kyulaj\n",
-      "PHID-TASK-zmuntlo4o5mkodhqeydo\n",
-      "PHID-TASK-kd7fv3uer3q4cxedaaca\n",
-      "PHID-TASK-4cf26q6ltrha64fqtdx3\n",
-      "PHID-TASK-q2usgov5bljwewguaiq4\n",
-      "PHID-TASK-l3o54qij3sav6s6cs6gu\n",
-      "PHID-TASK-seke4lquqzuxgalldvtb\n",
-      "PHID-TASK-3a75i4egmmyligpq2dlv\n",
-      "PHID-TASK-zbfvbqwtbhi2xzot3pbs\n",
-      "PHID-TASK-tp5fj2ilr35mvlgznvlo\n",
-      "PHID-TASK-7l5b3wunws2md2o6jk66\n",
-      "PHID-TASK-fyptj4pjp5zcqzsqxqnr\n",
-      "PHID-TASK-3ntrwhhennryl3bteiii\n",
-      "PHID-TASK-b3t54p4czyuwn2zt3mj7\n",
-      "PHID-TASK-qlstyqepo7ltrgysuslj\n",
-      "PHID-TASK-2nnhfwqpohjtpzziaj7g\n",
-      "PHID-TASK-tulkkn7hqx5jvhx43ruj\n",
-      "PHID-TASK-yewo3tdl2luoyru63ra4\n",
-      "PHID-TASK-2avmt4q62mzizp4k2qoh\n",
-      "PHID-TASK-6onfy2t6xjcwwmj3od5r\n",
-      "PHID-TASK-3ttlflt7d3qnjlwwyi2n\n",
-      "PHID-TASK-tufvyhfqrhacbhpyytqx\n",
-      "PHID-TASK-ypg6arsu3fplwmwytrtn\n",
-      "PHID-TASK-o4kh74skefuz5dgfcvx5\n",
-      "PHID-TASK-742b3uk4lvclm4lzhhp4\n",
-      "PHID-TASK-evkkc4zlooiizhrujg2e\n",
-      "PHID-TASK-hmpbfsja6fcgdvssmu4u\n",
-      "PHID-TASK-at437ap3jp2nwtfjwgi6\n",
-      "PHID-TASK-gqge6ob2qbmzizzddum7\n",
-      "PHID-TASK-z2cr4me55wbuu3qesrhc\n",
-      "PHID-TASK-ilx4l4y6zoryzl6763pk\n",
-      "PHID-TASK-p44y73skf774qafrhxfm\n",
-      "PHID-TASK-jyfxkeisbvohmunciamd\n",
-      "PHID-TASK-hlvwrmmv76naf6jfq4rg\n",
-      "PHID-TASK-sdsa2kuvbtigpgaepsc2\n",
-      "PHID-TASK-bmlhfoq57oujs4ajpe2q\n",
-      "PHID-TASK-bthorzb222zjqyyqflqv\n",
-      "PHID-TASK-k52nhgcjimjne3g6enih\n",
-      "PHID-TASK-hwxwkjrd5ypn4cohgwlt\n",
-      "PHID-TASK-caf2jml522yw7s4hrz7i\n",
-      "PHID-TASK-ziermjjci3oyywhcltgx\n",
-      "PHID-TASK-zltiznjn5tevkdkrgrvo\n",
-      "PHID-TASK-ioicrlnneujuclmsdn76\n",
-      "PHID-TASK-xle733tl52tx5qckejj2\n",
-      "PHID-TASK-q5awmwers7vnmtk3yywm\n",
-      "PHID-TASK-tpdzsfwsce2gxm3hlxzp\n",
-      "PHID-TASK-fuicnfjgm4dh24qhshha\n",
-      "PHID-TASK-e22m3ew36smar7n5obdf\n",
-      "PHID-TASK-adi2ks5r3obfupmjeuws\n",
-      "PHID-TASK-n7aygelprycptenbqxi4\n",
-      "PHID-TASK-2f5c5qfnz7mu3qheybrb\n",
-      "PHID-TASK-ceazwtjwm6a7jnascqca\n",
-      "PHID-TASK-tv45m2ck4vwdr4ovivkr\n",
-      "PHID-TASK-pikh7ix5hnqd4nnyiadm\n",
-      "PHID-TASK-ps7lp2luxy7m2thoc7zr\n",
-      "PHID-TASK-lfp625smnes4vmcpcaey\n",
-      "PHID-TASK-fde4qftmev4t5neslgqj\n",
-      "PHID-TASK-gwz2iw7f66yzzxl37lvc\n",
-      "PHID-TASK-cpftde25rzzyhyrt3v2b\n",
-      "PHID-TASK-3i3uyys5czodi4h5dtpg\n",
-      "PHID-TASK-dpqe4m25ofueoo7qs7ie\n",
-      "PHID-TASK-fm5h62v32kkok5qvd6go\n",
-      "PHID-TASK-db4a2ffve3au67ttwvrv\n",
-      "PHID-TASK-zvvrmcmz4eig3vs37trj\n",
-      "PHID-TASK-ozvmsbsv7fj3xaensg4b\n",
-      "PHID-TASK-aaoipsgz7oyqufzeblee\n",
-      "PHID-TASK-yuhi6ibmivh2wft5t4tf\n",
-      "PHID-TASK-wvcdfkoucmmc4frpdguw\n",
-      "PHID-TASK-bothhqbjosqeckagzghn\n",
-      "PHID-TASK-qkmndwu7hujefvxd4fpz\n",
-      "PHID-TASK-pkc5qf2xz72ywhnd6t26\n",
-      "PHID-TASK-52g62pbs7jogl5cwjmrs\n",
-      "PHID-TASK-hg2cfd2lpoag3lfyqcii\n",
-      "PHID-TASK-5dustpsver5abqahxsbc\n",
-      "PHID-TASK-o64myfteta7sv33kwhio\n",
-      "PHID-TASK-ongcgoxsyk4s52fr7dbg\n",
-      "PHID-TASK-a2hfohfk5j5mwllqwzu6\n",
-      "PHID-TASK-sa4ylwldmmhrky72otw3\n",
-      "PHID-TASK-6zaw3in4igorb3k4bavq\n",
-      "PHID-TASK-mtoupxdcw637uabefm23\n",
-      "PHID-TASK-fl6ckzrwls3bv7wziv27\n",
-      "PHID-TASK-atlm4jbmrywbsofx5zts\n",
-      "PHID-TASK-cgjlomsf2qva26bhkh5o\n",
-      "PHID-TASK-tgchpzb2re5dhfc6dype\n",
-      "PHID-TASK-nlvlcsu6onawdloowc5x\n",
-      "PHID-TASK-wicgwgtwpynij2ce4n4w\n",
-      "PHID-TASK-6fwnwpvm5g7pybmx2eaw\n",
-      "PHID-TASK-b4is7j2fhz7cdny4tfr2\n",
-      "PHID-TASK-e27vu3d74mxw2xwf3ahr\n",
-      "PHID-TASK-3lzxk25gwjfyhhw6s2ps\n",
-      "PHID-TASK-ep2xq5qhopjkqsqft6tl\n",
-      "PHID-TASK-nvbt37dfbyf2ilz2wcwc\n",
-      "PHID-TASK-j4fy326x5cwxfcmowqlo\n",
-      "PHID-TASK-qqtn53sr5xr6josxp5cm\n",
-      "PHID-TASK-qoe2ftyvquvdpbv4iapa\n",
-      "PHID-TASK-xkdnjrereisoecj453z5\n",
-      "PHID-TASK-cfrv36eokvo6qttirzvb\n",
-      "PHID-TASK-2pul64ax3wl2rgoic6ap\n",
-      "PHID-TASK-6i3c2xat3qhxsq5ee23u\n",
-      "PHID-TASK-46ixfpirqh7liqxoja7t\n",
-      "PHID-TASK-3recwohppy6wk6kediy2\n",
-      "PHID-TASK-ckbwvojthagfr3sxjhi7\n",
-      "PHID-TASK-buhdykqbpmicqrkqd7ao\n",
-      "PHID-TASK-rmjvwpvg64vxchilw4se\n",
-      "PHID-TASK-25jxvzvuaojvd6jgwcvc\n",
-      "PHID-TASK-42a5ngyvptb5lztis6k3\n",
-      "PHID-TASK-b6gfeng3ezs2u5pyporj\n",
-      "PHID-TASK-fz6jo77atbl2ydzv46s4\n",
-      "PHID-TASK-asfp6tebtqdcuww7w2ty\n",
-      "PHID-TASK-a3gencpajun7iccgc53o\n",
-      "PHID-TASK-pmwa76p7ooaxhmfvsbmw\n",
-      "PHID-TASK-el7cvjkat7q3jypwgavh\n",
-      "PHID-TASK-ikkzdnx32gvzflyd7h5m\n",
-      "PHID-TASK-bcrdaw3njczs7zhzj3to\n",
-      "PHID-TASK-2j26u6grwn6r7iymvg75\n",
-      "PHID-TASK-cu3bvvy2inqyghkz63xu\n",
-      "PHID-TASK-ew5qrcq2dqqfmtj4zhhi\n",
-      "PHID-TASK-irztrimblav2ughjnygh\n",
-      "PHID-TASK-yqdyvohgcbxzehgnpq4g\n",
-      "PHID-TASK-d7gosdnm6wposiphhgbw\n",
-      "PHID-TASK-7g7uyqfy56h27dadb2t4\n",
-      "PHID-TASK-3ysx7zhkex33mtvcwvjv\n",
-      "PHID-TASK-yj26bqg27rohxa63lh2v\n",
-      "PHID-TASK-kvwonhqh7mk3tnuapkuo\n",
-      "PHID-TASK-abahz4qyzn3wpoxxwffa\n",
-      "PHID-TASK-op7hsmyyqri3qvye5pcj\n",
-      "PHID-TASK-o26zcq73b7wls4nly65z\n",
-      "PHID-TASK-ey2zjvufzkixpyfo3wvk\n",
-      "PHID-TASK-nms5tkiqwi23vyk5dc7p\n",
-      "PHID-TASK-fk5w6cwyl6t7fo226qow\n",
-      "PHID-TASK-du3trqyxzlr7pus3ud55\n",
-      "PHID-TASK-2lksrv5vv6rqnzdrzgxv\n",
-      "PHID-TASK-bgaxa5whdy4rwfmma5hm\n",
-      "PHID-TASK-zzarel5lh2xkfhzr752t\n",
-      "PHID-TASK-3x6ghzfmxd6n4cvw7pxm\n",
-      "PHID-TASK-sjbb3upxz7oa72molxbx\n",
-      "PHID-TASK-lfuu4csnnqoanjnouo7z\n",
-      "PHID-TASK-zgtluxsdmxcciykkdi5g\n",
-      "PHID-TASK-jskdpgwlerlkftfmfqxh\n",
-      "PHID-TASK-3iie7vgp5rstgp2jfvqp\n",
-      "PHID-TASK-r6noyqq7rq63j346ezyr\n",
-      "PHID-TASK-fs5utskfc7v7hpp4u6fl\n",
-      "PHID-TASK-orj2erahi5zpz3pkgwc6\n",
-      "PHID-TASK-lbfh6wptvtd5xpjhoeon\n",
-      "PHID-TASK-fc5nfpvuhrxs4qd4v73j\n",
-      "PHID-TASK-m25vw4w7d3ob5tvtvkwx\n",
-      "PHID-TASK-brz6dzyxm67j6sqaxjdh\n",
-      "PHID-TASK-ucrlmd4fhqqckto7xviu\n",
-      "PHID-TASK-kjvmewrqq2l7f4hcprhb\n",
-      "PHID-TASK-yzpiypk2d2inixzpoytj\n",
-      "PHID-TASK-5vxcaydqorsjojhwsdme\n",
-      "PHID-TASK-g3vdqa5vzvi25aw23qzs\n",
-      "PHID-TASK-uontdax7p5isoaavstyc\n",
-      "PHID-TASK-ogfzjtubgzf6pn6yfvz3\n",
-      "PHID-TASK-atmvpvsegseglymt64gn\n",
-      "PHID-TASK-bphj5ytqpxc666bbt2xo\n",
-      "PHID-TASK-fxi2rdyqsib2css4ztr4\n",
-      "PHID-TASK-jxecea6ezbybvmmufndn\n",
-      "PHID-TASK-wsfvt6m45cmlqsrx2ft3\n",
-      "PHID-TASK-22g4j3j7uwe6d4goqunf\n",
-      "PHID-TASK-sgdd3ezfcgiwqqplkpsn\n",
-      "PHID-TASK-psruyhkjwka6oelbiqmt\n",
-      "PHID-TASK-qjeerptbgnssiimoy3ki\n",
-      "PHID-TASK-qf5vsjv66k5lg7t737hz\n",
-      "PHID-TASK-wgfiyucmntqggrzaytku\n",
-      "PHID-TASK-fdmergs3gf3rbdk5e44x\n",
-      "PHID-TASK-u7imfvtjqvaumjzh3knn\n",
-      "PHID-TASK-irtxbpca23zxuomdrg5i\n",
-      "PHID-TASK-3tvzg52f222bnnwlfsai\n",
-      "PHID-TASK-qooshzhaumbtp7cw7ahy\n",
-      "PHID-TASK-vqb2npuzjlgfxcuruzpi\n",
-      "PHID-TASK-dlrnznpa3flmvxcmva4s\n",
-      "PHID-TASK-cvyf4p3q6gk7j36ju3mz\n",
-      "PHID-TASK-i4u3xd3ofse5i6zio6uu\n",
-      "PHID-TASK-rierearzanexovgzmq5m\n",
-      "PHID-TASK-ccm3vufixpqdiieyj7mc\n",
-      "PHID-TASK-664j7lcmpr3idv6utx47\n",
-      "PHID-TASK-hu5muegrlrswr533nsfw\n",
-      "PHID-TASK-ybs7n5eiujqyko2jnore\n",
-      "PHID-TASK-fmxzdu423cuvq3v2z6tl\n",
-      "PHID-TASK-5oobwv46vr3i7ha7vl3i\n",
-      "PHID-TASK-lh72hjfjcfl6ttsyvwlr\n",
-      "PHID-TASK-pdnnreco64cgppyjvp4j\n",
-      "PHID-TASK-lgpuuxaum6kkmmaplhbc\n",
-      "PHID-TASK-sbvrcvwdbi27giwzj5gb\n",
-      "PHID-TASK-bggjq452trm2zbnm5rkp\n",
-      "PHID-TASK-bl52d56tzpumlzzhbr7q\n",
-      "PHID-TASK-akovpzpidyf5rwspkfmg\n",
-      "PHID-TASK-2c2keu6qpdpobf5algrr\n",
-      "PHID-TASK-yyxfhtfwvvpwlkr3s2rr\n",
-      "PHID-TASK-al3lhhw2b2pdp5sbs2i4\n",
-      "PHID-TASK-mmalwnjfjku6bqhnzsw6\n",
-      "PHID-TASK-cn5fpeogq2gpk4m4ftlz\n",
-      "PHID-TASK-zlmgxm2zkcke3qpckzhj\n",
-      "PHID-TASK-acfakt67yvd2rrao52i6\n",
-      "PHID-TASK-ainrxat373d2ajxvqix6\n",
-      "PHID-TASK-o3kocsqzjyadygy3bp6m\n",
-      "PHID-TASK-zwu66cvpdyxa3rt4yxqv\n",
-      "PHID-TASK-lbjifl56xpkfw4ti3gs6\n",
-      "PHID-TASK-reos2ubqqepoytoaxumu\n",
-      "PHID-TASK-dknub327yjfltf5egogv\n",
-      "PHID-TASK-5jz7sjvvr5dsv6ewj3sj\n",
-      "PHID-TASK-nlj7q7vdqadglucet365\n",
-      "PHID-TASK-bfggoy34bkzy45f7kcpd\n",
-      "PHID-TASK-eusx3radyuz75qavwdhm\n",
-      "PHID-TASK-iptvwjtzvbnrwojokpim\n",
-      "PHID-TASK-du3phlfbnb3yvb3jrnn5\n",
-      "PHID-TASK-7y5mvenxogghsfr7glsa\n",
-      "PHID-TASK-yf4ddfqwtxz3ayykgrqd\n",
-      "PHID-TASK-tqu2xxzwj77ml37wgx66\n",
-      "PHID-TASK-ezapkfj5jvedysawagen\n",
-      "PHID-TASK-xdltfrkzgw4ix3sbkszo\n",
-      "PHID-TASK-tswnyxkeiir5xgyyjogc\n",
-      "PHID-TASK-5e3qnrqbc3plh3qb6zjr\n",
-      "PHID-TASK-owm5ukn67i2uhxyue7qi\n",
-      "PHID-TASK-2thfovp27y2lm7rjxegt\n",
-      "PHID-TASK-2jrwjzhk56qqi6hbuy6z\n",
-      "PHID-TASK-fhofyq422q3wz75cdddw\n",
-      "PHID-TASK-mb365ltelmuwscrj3lep\n",
-      "PHID-TASK-k4x357kadd74krhi4jsl\n",
-      "PHID-TASK-du4fblehtatuv452azlx\n",
-      "PHID-TASK-ooymibfombnrpq5ugplm\n",
-      "PHID-TASK-4m3elcu2mghgs5wp7t2j\n",
-      "PHID-TASK-dpieimh3wxp5zjcp2w6f\n",
-      "PHID-TASK-2iussc7hskb3wyvivj3j\n",
-      "PHID-TASK-yhklbztfy4qioy5s3nw3\n",
-      "PHID-TASK-dgyqtyk3mbic5zgwmitl\n",
-      "PHID-TASK-ft4llcu4k2rwkptmn6t6\n",
-      "PHID-TASK-oelrynugtph5rjeyq7u4\n",
-      "PHID-TASK-igmisx4akeh5yixglyfo\n",
-      "PHID-TASK-4x34z4rnugcat2zdme3x\n",
-      "PHID-TASK-gc3mafjeizbrumfuxqil\n",
-      "PHID-TASK-wqlj6yxiyvemo7hpj3z4\n",
-      "PHID-TASK-xya74ryevlevdpyqmth6\n",
-      "PHID-TASK-cefkpaw5jsqxys54667r\n",
-      "PHID-TASK-mpgdokvlglkvrsqagxhx\n",
-      "PHID-TASK-d75ni2yenyhhlzg2tn2q\n",
-      "PHID-TASK-sy5wjdxwr4pa75h3r2tc\n",
-      "PHID-TASK-xkup4dal7lu2v5on7iek\n",
-      "PHID-TASK-g37szxauflfw6qlavwpb\n",
-      "PHID-TASK-6g5do6pkec5ll56oa4cb\n",
-      "PHID-TASK-2pa34yqzcieje3dwrtub\n",
-      "PHID-TASK-iesy7n57vtjmvbveuqa4\n",
-      "PHID-TASK-ge3lxw5vifprlb3diogc\n",
-      "PHID-TASK-g2els4untqmatfgmtodr\n",
-      "PHID-TASK-5udersenidwseo6m5grs\n",
-      "PHID-TASK-4y6au3cwi5b6pobrhrz5\n",
-      "PHID-TASK-w3ca2knqurlwdolz6rth\n",
-      "PHID-TASK-gmswkf7wwjtivxzlq3hb\n",
-      "PHID-TASK-s52vfnr5655l5mcn3ccw\n",
-      "PHID-TASK-a4ziafykxquhrim4wrm3\n",
-      "PHID-TASK-dlrbz5yirqhdlb5ixx32\n",
-      "PHID-TASK-y3zmidmzskha5h7ldgcc\n",
-      "PHID-TASK-d2izuitwfayrxbyhcjil\n",
-      "PHID-TASK-pvtq3ysdgbspx2ubicva\n",
-      "PHID-TASK-rmkl7hs2ktj4cx7nvrl4\n",
-      "PHID-TASK-geakkjwdr2b6k3vobqx7\n",
-      "PHID-TASK-uw2trpgzgq47w4uqfske\n",
-      "PHID-TASK-nql2oht74xidzmey66vl\n",
-      "PHID-TASK-qb2engnawhn3el2wqyzm\n",
-      "PHID-TASK-3qnp2v5yec7kxc653kc7\n",
-      "PHID-TASK-g5cwud3usjdr2bplpq6x\n",
-      "PHID-TASK-fkizlik3mtnbtsqbgnqs\n",
-      "PHID-TASK-f3qthugptx3szx2kr56o\n",
-      "PHID-TASK-5eekrsnuh3slhfvi2vl5\n",
-      "PHID-TASK-ufskmzg3xlrkksp26qtv\n",
-      "PHID-TASK-vstc34ukjrx4agdul6rw\n",
-      "PHID-TASK-nqqibdaciuaeyw2lnzmy\n",
-      "PHID-TASK-hu7ibauxmtlo3ljy4pvq\n",
-      "PHID-TASK-blsktvyvk2zcdw2o4yue\n",
-      "PHID-TASK-c45wkid72cnbk33nmpdr\n",
-      "PHID-TASK-bxknfjhi57rb6pgzrqm7\n",
-      "PHID-TASK-boxjw4hklzqeriwzj6zc\n",
-      "PHID-TASK-khbn3xwnzxzqjmsvryrq\n",
-      "PHID-TASK-2mkgo6douokimv6febmw\n",
-      "PHID-TASK-w7k7v4pcanwqeehqmoyp\n",
-      "PHID-TASK-six3hr3num5ryuty64kf\n",
-      "PHID-TASK-4a5risai7mr4y6na4dug\n",
-      "PHID-TASK-wh766os42bllzvmszxya\n",
-      "PHID-TASK-oxphbzmhqbxzbsixhfq4\n",
-      "PHID-TASK-sc56jdm4lxt6le2zxeuz\n",
-      "PHID-TASK-7wslc7ru3hkj3phtleql\n",
-      "PHID-TASK-m6zybnoobh3hwy2qmm6n\n",
-      "PHID-TASK-da2sdjr5nuneldb7hbcy\n",
-      "PHID-TASK-3yhieue5lg5ipuzhildn\n",
-      "PHID-TASK-nydh4gpoq4wxodchwgi3\n",
-      "PHID-TASK-rzsc7tmlupqbuaedolkl\n",
-      "PHID-TASK-s47345xgplfmgixnp726\n",
-      "PHID-TASK-ejnmmkuva4ygwqwckki3\n",
-      "PHID-TASK-psky7k3cs2jglhz37xhh\n",
-      "PHID-TASK-6g646hsi3p3j73jyxxaz\n",
-      "PHID-TASK-ngyf6tjjlwso4rlid7ni\n",
-      "PHID-TASK-y44xrgvhzk7uy25krg2j\n",
-      "PHID-TASK-nj4fiiksolcbit4ngngp\n",
-      "PHID-TASK-bqgfek7rspw6d5gukppc\n",
-      "PHID-TASK-ibmxa5xzrcmu5u7fcttq\n",
-      "PHID-TASK-jvygvcsdp3dse45vpayw\n",
-      "PHID-TASK-ejote3xjqqm7riq7xqwf\n",
-      "PHID-TASK-ycbizrojj6ti4ywzojyo\n",
-      "PHID-TASK-fzc2bascptcvyjvfz6iv\n",
-      "PHID-TASK-3e25u2t2rvump3xhzmpi\n",
-      "PHID-TASK-kxbkw2kfnhnvqihjlumu\n",
-      "PHID-TASK-c6mjvz42mmi6bswdw56d\n",
-      "PHID-TASK-4ua7w7m7aik6txmrerbe\n",
-      "PHID-TASK-346l3sxkrxirwfv4rf4g\n",
-      "PHID-TASK-3g3rbtewmym2ch553j4x\n",
-      "PHID-TASK-3niuhnlezs7jfmugbwdy\n",
-      "PHID-TASK-anwdvhxvorgu42thq5we\n",
-      "PHID-TASK-sqkvabmnd7cfcbr6tkhz\n",
-      "PHID-TASK-5u2adzhalmhqywlvbhji\n",
-      "PHID-TASK-n4sh4scopfxwny7l26we\n",
-      "PHID-TASK-5dek6g5wc736qamv43s5\n",
-      "PHID-TASK-nkghehcsjvmpig3dnbgm\n",
-      "PHID-TASK-qoahpa6ud2jrgv76kigv\n",
-      "PHID-TASK-77lwknbtryzjh4peqeh4\n",
-      "PHID-TASK-ozeftogat7b2642er6vn\n",
-      "PHID-TASK-4zstjmvxiakrfapfim3n\n",
-      "PHID-TASK-f6pggcvz6dsrki4glrbf\n",
-      "PHID-TASK-r7e6j3kldhsiy2cc57wd\n",
-      "PHID-TASK-oveveoihmpyqrm3ltjzu\n",
-      "PHID-TASK-wnl2ydoz2ca2h7xcsvtk\n",
-      "PHID-TASK-pdsk3nihjnd2lxdtnwus\n",
-      "PHID-TASK-j32rmxvcdit6df4qvtqi\n",
-      "PHID-TASK-oml53qiv2ffx7tuvmx47\n",
-      "PHID-TASK-ye62pxccv2jh5w3o2yl7\n",
-      "PHID-TASK-ezxtdsztbaq4wuvaxjmv\n",
-      "PHID-TASK-chjb2m7r6pmqmr457wgg\n",
-      "PHID-TASK-va4nmthl5rer6qeyil6y\n",
-      "PHID-TASK-evkujyihqmirmqqeozmk\n",
-      "PHID-TASK-5cuwqt62enm5hymwly75\n",
-      "PHID-TASK-tyb65vkuz46fcurmj72h\n",
-      "PHID-TASK-hia733wv6lu2vvjmm2xv\n",
-      "PHID-TASK-iwz7tbppv2hen4mzt3ny\n",
-      "PHID-TASK-7uqnmenedinwiui6wz4s\n",
-      "PHID-TASK-mx73qk7qlj7jty4xm3o5\n",
-      "PHID-TASK-r3aliipwenpyb4simxc3\n",
-      "PHID-TASK-h7psvvdxqq5nurzgtxts\n",
-      "PHID-TASK-tn3a37o3zgibya4bkm32\n",
-      "PHID-TASK-osskcs5pzqf76ce4lpyj\n",
-      "PHID-TASK-zls4w4oon3y5sp6y4rot\n",
-      "PHID-TASK-3fcobyguspmbsv62uzbp\n",
-      "PHID-TASK-clul26iiuspnnu6ubobc\n",
-      "PHID-TASK-ueuakppu4zprla5jwywo\n",
-      "PHID-TASK-cttzml5ohhludlqqeslk\n",
-      "PHID-TASK-bgfttfnluju4mvokk3ud\n",
-      "PHID-TASK-pdifcdlqnopvfjzdvczw\n",
-      "PHID-TASK-m6mab3qibjjsonpriu5r\n",
-      "PHID-TASK-ejfpqmqzgmehdhmxzmty\n",
-      "PHID-TASK-xffvpozuzkjhhlysn3cs\n",
-      "PHID-TASK-ltfnf6nk2htfdban76pc\n",
-      "PHID-TASK-ymnidmb2ap2g4se52stx\n",
-      "PHID-TASK-sflxt54msumq4ifieh2r\n",
-      "PHID-TASK-gysdgpu4licxwvxxosg3\n",
-      "PHID-TASK-7ix4hqmkcelueduz7hux\n",
-      "PHID-TASK-cwptueorc4rxrgvc5shh\n",
-      "PHID-TASK-blwhpbgbhchhdkulxgr2\n",
-      "PHID-TASK-c65b3wdhn2onui4dnvcj\n",
-      "PHID-TASK-oqp2lj4ng622u7fiwxp2\n",
-      "PHID-TASK-gx6k3eekkero53hloidz\n",
-      "PHID-TASK-gf6k4fuodiscgbllfhpa\n",
-      "PHID-TASK-7agzn6t2zkyppgtkt4zy\n",
-      "PHID-TASK-pe6m5b3pbhmfcnu7uep4\n",
-      "PHID-TASK-tb2wtwoarrokjafpdi3e\n",
-      "PHID-TASK-u3h65rxvz452mowrmajb\n",
-      "PHID-TASK-vrzpbb2v2s74ml5e53ww\n",
-      "PHID-TASK-nog34g36rvrxth34pzwz\n",
-      "PHID-TASK-wvcrw2fz7zto4p5xyqav\n",
-      "PHID-TASK-bm4l7dozmqtublm7xcao\n",
-      "PHID-TASK-g7kzupvlt4lakd72su4u\n",
-      "PHID-TASK-yfjwr3je2btidmhmuccx\n",
-      "PHID-TASK-escar4ypn3o4hbygakj4\n",
-      "PHID-TASK-yr55vawmutvv7jim7igv\n",
-      "PHID-TASK-lusyegvtclbce7nfsesb\n",
-      "PHID-TASK-ktdxstz7i62g4zy5m5ov\n",
-      "PHID-TASK-erdij6gvcjcryxt3xqjp\n",
-      "PHID-TASK-qjdwtbzzs25aurzlowwr\n",
-      "PHID-TASK-f6h4xzkjkkq4qb5rbp2j\n",
-      "PHID-TASK-m6kobht7lswcgwklm5ra\n",
-      "PHID-TASK-k3hxvwskpoy3zkxaliwa\n",
-      "PHID-TASK-d3wa2dbg66dt5t24advb\n",
-      "PHID-TASK-pzog36r24v5pdzjqcxdr\n",
-      "PHID-TASK-jgayasapvffxzhq5zq6a\n",
-      "PHID-TASK-6ytamqsj45kuhfs22bx4\n",
-      "PHID-TASK-cjrfpthlsv4urm5hyivq\n",
-      "PHID-TASK-vpvtoerhlbprn6ollnkr\n",
-      "PHID-TASK-sug5dsmkfrgqkbno76mo\n",
-      "PHID-TASK-l6tecg3euv7s6vvgap3i\n",
-      "PHID-TASK-bcphrwlve5fbhq4ltxr3\n",
-      "PHID-TASK-y754cxtupebi6bfunc3e\n",
-      "PHID-TASK-xoiz3tzy2fgdd4xhxob7\n",
-      "PHID-TASK-ydvvzyrpkompusxbw5gr\n",
-      "PHID-TASK-7te6uik6zxfmwlua2dgh\n",
-      "PHID-TASK-rkr7k7s24b2ie267wdh5\n",
-      "PHID-TASK-x4ddesfyx6gxnu6ahuf6\n",
-      "PHID-TASK-pey4kjm5sey6cllpuym2\n",
-      "PHID-TASK-jjtln7nquqmd5je6fmy3\n",
-      "PHID-TASK-7wx6pzrxilelrduf5qci\n",
-      "PHID-TASK-df6digqa5tkg4x3pko26\n",
-      "PHID-TASK-pw24nueljk2i343joyw2\n",
-      "PHID-TASK-3wvoqjxuqinfi7bgkax4\n",
-      "PHID-TASK-tgtxd532icx4mnfll75r\n",
-      "PHID-TASK-ra3d7l6sbywnzslhiccu\n",
-      "PHID-TASK-yocptvdek2u4pm4ssk5d\n",
-      "PHID-TASK-y2db4ahscixrwviebqhf\n",
-      "PHID-TASK-7ljydmhlfgrzwegrjhpj\n",
-      "PHID-TASK-czxsast2el34thkj2xkj\n",
-      "PHID-TASK-s536bhjhjcxh5wim4rzu\n",
-      "PHID-TASK-jksvrmf6seb3lzwf6tsr\n",
-      "PHID-TASK-27h7itsrfluxqubhrje3\n",
-      "PHID-TASK-egsozcckjwhatubn2cu7\n",
-      "PHID-TASK-csda6oirljibl6xuzg3w\n",
-      "PHID-TASK-tl42tulmp4okf7khych6\n",
-      "PHID-TASK-vb4syhceqgegacimzles\n",
-      "PHID-TASK-3wggiaj4uckt3tln426a\n",
-      "PHID-TASK-gru24gdbzlh5sitams7s\n",
-      "PHID-TASK-d3oejnwggmk2whlojm2x\n",
-      "PHID-TASK-ah63325mhbgtfpeazbnl\n",
-      "PHID-TASK-jx64nu32n5cymzvwwjp5\n",
-      "PHID-TASK-6nas4q7uc475euchng3b\n",
-      "PHID-TASK-xckf32rcb2yx56eieafj\n",
-      "PHID-TASK-2ms2vngz2briyomwp2bg\n",
-      "PHID-TASK-bcumpuzgy3avff6z7fio\n",
-      "PHID-TASK-likhdovodmty4qer7rsq\n",
-      "PHID-TASK-oytsgsispcryv5y4kv3t\n",
-      "PHID-TASK-j46p5in7q2s26odkx5az\n",
-      "PHID-TASK-kvei76aer6u2clu7k444\n",
-      "PHID-TASK-m7yoxj62gdjohzchm7zw\n",
-      "PHID-TASK-iycnxhmj2yiay4bvfsic\n",
-      "PHID-TASK-4imcgove7xglvcqm25ym\n",
-      "PHID-TASK-6gr7275ayzz2al57mitp\n",
-      "PHID-TASK-eebs7mwekgwvhg5ap6qk\n",
-      "PHID-TASK-3ree5vwpvfff7nqhn3qg\n",
-      "PHID-TASK-m5725ohwtikdne7f72hd\n",
-      "PHID-TASK-mdqhw3wzqwlxbr4xogeu\n",
-      "PHID-TASK-boasjpxas32sxaoibmuy\n",
-      "PHID-TASK-q5ayyohzxfrkbwwrho46\n",
-      "PHID-TASK-5rpxkdg4clk2xzkgyeci\n",
-      "PHID-TASK-nkihkps7zwe2jnpuv2vo\n",
-      "PHID-TASK-4iqn2br77eamftwdpwfs\n",
-      "PHID-TASK-udzfkpaotefzeteimh7e\n",
-      "PHID-TASK-7uebrq6s5hgkckkrqkv5\n",
-      "PHID-TASK-ufv5laxxz2gup5mbsoae\n",
-      "PHID-TASK-mc4ekk7vrriv5kycc2u2\n",
-      "PHID-TASK-63tv3lkov2okxud2zyxo\n",
-      "PHID-TASK-gdwu5ick5nfagic7txm6\n",
-      "PHID-TASK-ktldutlvil3ngaxt2l2k\n",
-      "PHID-TASK-kg6wsbien7yipr4dzrul\n",
-      "PHID-TASK-a3yp2evtjuq3hjqdrvhc\n",
-      "PHID-TASK-ca6crnotrmabx3jkz5wk\n",
-      "PHID-TASK-brtl2hvq3mpywf2r3lkp\n",
-      "PHID-TASK-iudy2zuexclkhlwqjbkn\n",
-      "PHID-TASK-ss6harhqovaxcprykzge\n",
-      "PHID-TASK-7auhm5son76ryeyfeyid\n",
-      "PHID-TASK-573oqdvpm2jqlbzsvzdg\n",
-      "PHID-TASK-unahzezsufzzdb4k4beo\n",
-      "PHID-TASK-g24bxdialbz5a5bcp4qb\n",
-      "PHID-TASK-kg4p7wmv7m2n5tdejrm4\n",
-      "PHID-TASK-3es7m4cbr63gg2w4l5or\n",
-      "PHID-TASK-t4nrv75pjo2r4cxn47di\n",
-      "PHID-TASK-gou4ejmnkpg5lgq6cdfx\n",
-      "PHID-TASK-erfxy2a7265vjb4b2dj3\n",
-      "PHID-TASK-mo5dvj5do74gbwyx6vrs\n",
-      "PHID-TASK-643scf5lq5v72slluprm\n",
-      "PHID-TASK-npqg6q6ozudz2pqkgmjm\n",
-      "PHID-TASK-6ana44vgeezadw6ore4y\n",
-      "PHID-TASK-yv3kce72452r37igamnp\n",
-      "PHID-TASK-a6e5anlp2g7eyftsen6n\n",
-      "PHID-TASK-6vanypiuvvogqhl2yqvj\n",
-      "PHID-TASK-c2zo7myzzju4zjk7el5z\n",
-      "PHID-TASK-deqihdmtktthecojw62o\n",
-      "PHID-TASK-cc7gmrf5ioc7lfjjvyzo\n",
-      "PHID-TASK-p6rccw5cwglxrbbkmq2b\n",
-      "PHID-TASK-glljlygxsse6ts5nyo5g\n",
-      "PHID-TASK-qxyoycuq2mw55c2oy7mm\n",
-      "PHID-TASK-znebtf73mavsnt4zkjtb\n",
-      "PHID-TASK-fu4mfwq7s4u3wu5u6yny\n",
-      "PHID-TASK-jdnwbc5e2g3tlpeis2hc\n",
-      "PHID-TASK-f6islnvgxyd3d63sxooo\n",
-      "PHID-TASK-l5pjiw32hngnewgrmmmy\n",
-      "PHID-TASK-ki7bzkbyld2qdm75nyap\n",
-      "PHID-TASK-nphxjkvvi4eszdxix7bq\n",
-      "PHID-TASK-ny6m4ujfqwfjm6dzcxsg\n",
-      "PHID-TASK-7brx7poui3lgaqmgzlvg\n",
-      "PHID-TASK-xxykpaxkkgrcn363ntny\n",
-      "PHID-TASK-l4k7rc3z5agm24u46fhj\n",
-      "PHID-TASK-oh3fg6fot6uziw3ctbqu\n",
-      "PHID-TASK-4phtoxaof6zm4vyraue4\n",
-      "PHID-TASK-dhlp7wsucyat5r5hizgn\n",
-      "PHID-TASK-hqedrd262jmefrbeu2zs\n",
-      "PHID-TASK-jbywhdnkgf572tjejemv\n",
-      "PHID-TASK-4thzrxadngq5mhfphtu2\n",
-      "PHID-TASK-tqk4thl22c326oiwdmgc\n",
-      "PHID-TASK-etzwcnqtxa6glyvdpt5e\n",
-      "PHID-TASK-zy6o6x7vkuly2bz7grnv\n",
-      "PHID-TASK-vqebaloi6mz6p43fpars\n",
-      "PHID-TASK-cc3yxgxiksoojspiwoxm\n",
-      "PHID-TASK-vwwslgbmh4ftbegrc3zg\n",
-      "PHID-TASK-h7tfqm7vbzcm7dpmeabg\n",
-      "PHID-TASK-bmll3l66rbyvzumaunet\n",
-      "PHID-TASK-2lqrwar67hw6qvy4f5kh\n",
-      "PHID-TASK-4qpkfgh5ks6gaaj22qxs\n",
-      "PHID-TASK-77heb24pfspzzrzifyb6\n",
-      "PHID-TASK-e3ikdtgrrubm3iohiewm\n",
-      "PHID-TASK-opmsqzsgromr47nfku4r\n",
-      "PHID-TASK-delfcnij7a43xvmu5qyt\n",
-      "PHID-TASK-aq6bcd3lx5mpkayh6jkq\n",
-      "PHID-TASK-yhjup2iu6lr4ysgs743l\n",
-      "PHID-TASK-fgcx6r4cq4f3sp3crtxx\n",
-      "PHID-TASK-e5rh26mnuyokpvoo2c2t\n",
-      "PHID-TASK-hkpifvkdgtnwuojek3uj\n",
-      "PHID-TASK-wcnnt6ci2eb4mcaggjrl\n",
-      "PHID-TASK-35rbgnr7z5e2nahfmsjs\n",
-      "PHID-TASK-5kevizlj2r7opk2fmypx\n",
-      "PHID-TASK-ct4cgxz4gl6hs4fuvcpo\n",
-      "PHID-TASK-jza5e4mrwocbbyclpgux\n",
-      "PHID-TASK-qx22rnw4roeugdfib5hc\n",
-      "PHID-TASK-x7y27baxwalxutuxi24u\n",
-      "PHID-TASK-rdmlp3onaqmsq2rdmrnq\n",
-      "PHID-TASK-2liv3ois3nnjarqe73d5\n",
-      "PHID-TASK-zzmgok2p56thwvxkpnrv\n",
-      "PHID-TASK-snnn2o47ucaywt5ufim7\n",
-      "PHID-TASK-smutmksr4slgk2o54suc\n",
-      "PHID-TASK-ubeo6o33vz5bavixyf3q\n",
-      "PHID-TASK-joexgd3r5nmcwbofqrlr\n",
-      "PHID-TASK-ftkzim4nufm7ey6vnaq5\n",
-      "PHID-TASK-2p76xxlh44jpmzqza6ge\n",
-      "PHID-TASK-ibes2uplyibrsadgodld\n",
-      "PHID-TASK-3jrxscvn6apol6nbrw66\n",
-      "PHID-TASK-72xdyaasptqyeuovlab3\n",
-      "PHID-TASK-itj4sdz77n2m7ganhvyr\n",
-      "PHID-TASK-ce2w6vrcycpoidffw23e\n",
-      "PHID-TASK-v3iakko3iymlxqo43aix\n",
-      "PHID-TASK-du5yifaebt3zb2zhinvr\n",
-      "PHID-TASK-5ftakv5wuzkf73akgiop\n",
-      "PHID-TASK-d3wyk4xxdf6fguq3hvoj\n",
-      "PHID-TASK-65s4zvg7e6km2enogisy\n",
-      "PHID-TASK-spssyaufehg6a576inro\n",
-      "PHID-TASK-kazpxbs6hxscszn2mj4j\n",
-      "PHID-TASK-xduyhafmy6kenmdf7cuh\n",
-      "PHID-TASK-focb5kxme3jxk4n6xklr\n",
-      "PHID-TASK-eqiuslxuu3t7bxl7vmwb\n",
-      "PHID-TASK-potyqd62zizy6tkvf2ak\n",
-      "PHID-TASK-ag2p4jtrgjagpo2qegcu\n",
-      "PHID-TASK-rou7bduh6enhafdxh2lv\n",
-      "PHID-TASK-7n67l5aimznnhmya4iwf\n",
-      "PHID-TASK-ttp4fmqdy7axj4tku4zm\n",
-      "PHID-TASK-n26jfot72gcfg6mgq6wx\n",
-      "PHID-TASK-xnsrcsuce62r2yfruwso\n",
-      "PHID-TASK-op3amukih656hqtejh6j\n",
-      "PHID-TASK-nopdefkge3ym2od7ufrd\n",
-      "PHID-TASK-ttobixbmawcbongmnatf\n",
-      "PHID-TASK-itqhk6koq7bmakcn2wvo\n",
-      "PHID-TASK-hoazjhp6o63s5rrky5qa\n",
-      "PHID-TASK-5wuwyofe6l5k2cmqjzad\n",
-      "PHID-TASK-dwxii5uaohcgrtbsiwxl\n",
-      "PHID-TASK-2r6x4q4bt3fqtg3es4ps\n",
-      "PHID-TASK-a6pw6i4cfeu2jzsduppd\n",
-      "PHID-TASK-ssksx6n4c7yondhu6cpg\n",
-      "PHID-TASK-ogwe6d555gi7xn3bq357\n",
-      "PHID-TASK-bcblwti2swge5nlt24om\n",
-      "PHID-TASK-hadccnndpx3xlfcdq5x6\n",
-      "PHID-TASK-bygkpi2cds2ycjzl4xyf\n",
-      "PHID-TASK-o63tibhphh5vfhjwesdx\n",
-      "PHID-TASK-bdj7ew4y7qhxm7z7ixap\n",
-      "PHID-TASK-vipia63usd432ltaseq6\n",
-      "PHID-TASK-hhff6uyjp6fqhsgfm4vx\n",
-      "PHID-TASK-kmp5cza2rwu3qkvnz3gy\n",
-      "PHID-TASK-yelwyuxn7ull4zzjha5n\n",
-      "PHID-TASK-pquc72fdsgxf4k4jbbrl\n",
-      "PHID-TASK-xcrom5qozpxh2fsjz7v7\n",
-      "PHID-TASK-s6tr75wkga6yoxhfytgb\n",
-      "PHID-TASK-g7bv7yb2notx65burp7i\n",
-      "PHID-TASK-hnjrb6dsvhgt7tgjsyyd\n",
-      "PHID-TASK-yv5u43sg36sflqbgt5oh\n",
-      "PHID-TASK-4pmiosnpdta6wvmtogmm\n",
-      "PHID-TASK-cc3wbqmetbmasfz6nkj6\n",
-      "PHID-TASK-rl6rjnnqsrrmwprvwrmk\n",
-      "PHID-TASK-cypsptchtj5tr3ktdvxq\n",
-      "PHID-TASK-flrq364icuczabc3nb2z\n",
-      "PHID-TASK-nctiyee24idgcp7llspj\n",
-      "PHID-TASK-nu54imdjney5p47v7jx7\n",
-      "PHID-TASK-f2jkrvqamprej6vbtifd\n",
-      "PHID-TASK-eirxrxhok3puf5mpvsgj\n",
-      "PHID-TASK-coeco2n4cfz4d24eek2p\n",
-      "PHID-TASK-gvpsurapr2wpn6mmysso\n",
-      "PHID-TASK-xd4kljcgqcwzmsvbid4p\n",
-      "PHID-TASK-ui3plx4slven33rbf4id\n",
-      "PHID-TASK-zkfo43fncbploqynkreq\n",
-      "PHID-TASK-xeya3bpycvyi4743gzho\n",
-      "PHID-TASK-jxgfjh6zrpct7dssxnsk\n",
-      "PHID-TASK-vrnyctiie6ntzdrqt77a\n",
-      "PHID-TASK-d42ybmk2s2iavorgwpdd\n",
-      "PHID-TASK-fcxjzl7orc3z55j4k4z4\n",
-      "PHID-TASK-457x6imtkd7rswr4kl6x\n",
-      "PHID-TASK-busqmj37jbvye6nty5bt\n",
-      "PHID-TASK-sl5n5bwvzliz5t3rwkrs\n",
-      "PHID-TASK-pcf2yvjdcefbppv4nmdv\n",
-      "PHID-TASK-4tagph3in7nb7kiwdldq\n",
-      "PHID-TASK-ynxqancujipoqcvx5723\n",
-      "PHID-TASK-z4fhfn54bwmdzbvrehbm\n",
-      "PHID-TASK-uebopddiz3ehqfkg326y\n",
-      "PHID-TASK-gk2mpik33dhlthfx6ji5\n",
-      "PHID-TASK-6j7kkh226srwx4yd3xob\n",
-      "PHID-TASK-pg2baotfmhrts6ap3fmf\n",
-      "PHID-TASK-io6oush42k3uezzajdmy\n",
-      "PHID-TASK-js3thiqf6n5putzp4qaq\n",
-      "PHID-TASK-fzpzl3u4tnchcdvuauzd\n",
-      "PHID-TASK-pvs5mqz2lxwkwyv7enfq\n",
-      "PHID-TASK-q46agi2mree3c3qnk2y4\n",
-      "PHID-TASK-ju3g2oypj6sg3qneywp4\n",
-      "PHID-TASK-fismtah5nhz3jechnxci\n",
-      "PHID-TASK-pyjlzzqqrcxthunhdjxd\n",
-      "PHID-TASK-4ea4xsfwmbsq76ri4xgj\n",
-      "PHID-TASK-sbmvrc3jz243m2e4aqmd\n",
-      "PHID-TASK-2nqdcy26wu7c3ct3pti6\n",
-      "PHID-TASK-vaw5sbbofozchqbqlxfo\n",
-      "PHID-TASK-jdjfrc2gvkcmr2dyxdhz\n",
-      "PHID-TASK-isdw3zrrbc3uvww3ghe4\n",
-      "PHID-TASK-e2zkvddmlxs36w5rmyck\n",
-      "PHID-TASK-3z252ihuxf33ir4how73\n",
-      "PHID-TASK-6welutlbuxohheakxhlf\n",
-      "PHID-TASK-ccjs4p2cgeia2i67aibl\n",
-      "PHID-TASK-fbmrhc7yiidum6n27xww\n",
-      "PHID-TASK-esg6d3iurlxoqoaozlgc\n",
-      "PHID-TASK-hmd3ybxvx2oovxcgcs5b\n",
-      "PHID-TASK-okxdqrb2z7y2e2t7su5q\n",
-      "PHID-TASK-txjmg5opo7xccxwery5r\n",
-      "PHID-TASK-mmsz5huxzdhmzpx6zlmd\n",
-      "PHID-TASK-fruuvllzbsjlpilalc3q\n",
-      "PHID-TASK-k2rw3gv6tegtzx4fqydd\n",
-      "PHID-TASK-dlisjakdxxdx6ulkcllp\n",
-      "PHID-TASK-pq2jmdduyi27pmzdn6fs\n",
-      "PHID-TASK-cdvhznmmt4p6jcin6skh\n",
-      "PHID-TASK-sit6vtslr7r2fqfrzugp\n",
-      "PHID-TASK-2qasjtis6bukznlqh6fa\n",
-      "PHID-TASK-4rqn2y6kag5uml6nligz\n",
-      "PHID-TASK-yt5y3btrqqtcxanvipk4\n",
-      "PHID-TASK-rkmnvdgo6nof3bkunyfu\n",
-      "PHID-TASK-oqao2yl4prg5uecpylkw\n",
-      "PHID-TASK-bhc7xmtcptcglmeqxvai\n",
-      "PHID-TASK-trlh3c7s2ff2x2avhgoo\n",
-      "PHID-TASK-ticw62p4dy4nr4dhvsrq\n",
-      "PHID-TASK-7ci67c3uih3tuev7ghu3\n",
-      "PHID-TASK-3qm4izjirylpzskf6mlm\n",
-      "PHID-TASK-inqexk3a4klng6im6ld7\n",
-      "PHID-TASK-jjld4d5wjqxkuihohuzl\n",
-      "PHID-TASK-ebn2j76ougc2mnfqb4fp\n",
-      "PHID-TASK-nlxbzrcehkp3h36untox\n",
-      "PHID-TASK-rhsntkwc7ofl6qzz7kt4\n",
-      "PHID-TASK-2h7j3etzcjrazlrx7t2k\n",
-      "PHID-TASK-n3tckyz3ypiasbv7mmov\n",
-      "PHID-TASK-3ovbcuxkngbjxrroevib\n",
-      "PHID-TASK-caprohhe57u5cvvih5r4\n",
-      "PHID-TASK-2qamjq3crlikvr3nahtr\n",
-      "PHID-TASK-lsb2vshfs5s363qn5xmf\n",
-      "PHID-TASK-mmm6poefxi4xoohquyi4\n",
-      "PHID-TASK-jpmjmzcf4crsjhqwquzp\n",
-      "PHID-TASK-4vzkkpi6vnpbfv2eknxj\n",
-      "PHID-TASK-cxhnj4waa436ovh4o7lz\n",
-      "PHID-TASK-c3wc4a6vunygqboimdkx\n",
-      "PHID-TASK-7lzwyjbh5q62jpz2njvq\n",
-      "PHID-TASK-ftjpfhlr3dsluwcrrpaa\n",
-      "PHID-TASK-jzom4aa22nn3mtwtm74t\n",
-      "PHID-TASK-e53ehyegovylp4gigsvo\n",
-      "PHID-TASK-pds66u5f24d37usiicgj\n",
-      "PHID-TASK-nmn7dlmg7l34754u4bwb\n",
-      "PHID-TASK-ezht24x5cf4eytaekvqk\n",
-      "PHID-TASK-7jfh3i424pezp3um3zzy\n",
-      "PHID-TASK-q322vvsm62gyx2idxtx2\n",
-      "PHID-TASK-kjq6yunjdamvcihfi3va\n",
-      "PHID-TASK-djl2633o2ndbnj77h5l2\n",
-      "PHID-TASK-g4wwasypneek2xwppnuc\n",
-      "PHID-TASK-vqj7c3uh5ndu4ic45odq\n",
-      "PHID-TASK-6qqicftxiu35fghejuwg\n",
-      "PHID-TASK-xka4cwtxxzprt6337pfw\n",
-      "PHID-TASK-njbgmmjxybp3rk2azuui\n",
-      "PHID-TASK-wggr7br64lqzvnsbmef2\n",
-      "PHID-TASK-jslagmridhbcpdvjclho\n",
-      "PHID-TASK-kayythzbd2m7qbeafhrw\n",
-      "PHID-TASK-namz3nhksthhosxp6pjt\n",
-      "PHID-TASK-ppxeze2biaiay2bq2ned\n",
-      "PHID-TASK-isog5p3qki3pp25ezf63\n",
-      "PHID-TASK-xj7stom4ugsmlhxmz6az\n",
-      "PHID-TASK-p25kct7eiowcmvkmyncx\n",
-      "PHID-TASK-lpywcmlyfhgff4artepd\n",
-      "PHID-TASK-arvnl4rgkbslvicqgsmj\n",
-      "PHID-TASK-vgio4d23zmdnqxwyja3n\n",
-      "PHID-TASK-azvy6g4nbj2z6hw5ydsm\n",
-      "PHID-TASK-6r6iwczgdw2x3g22idm6\n",
-      "PHID-TASK-dga3eyvqthuwtl6xayui\n",
-      "PHID-TASK-irkp2njalgjutggxseff\n",
-      "PHID-TASK-o45i4q2kievixjidhsk7\n",
-      "PHID-TASK-2f2dgqt54eqesg4exgwo\n",
-      "PHID-TASK-ju6nd3s77iuekvlfhra5\n",
-      "PHID-TASK-rc4yhxp2tlzilezhonck\n",
-      "PHID-TASK-x7lpmfetdbteus26qx4l\n",
-      "PHID-TASK-altic2tebpor7cfydf6y\n",
-      "PHID-TASK-ix6ll4i6ezero6wug475\n",
-      "PHID-TASK-bdvf6u5xglbisa5hqfhd\n",
-      "PHID-TASK-o742mr6hjh6wsdblaanj\n",
-      "PHID-TASK-pgpcd7rvhd6x44lw4xo5\n",
-      "PHID-TASK-6kpwltejynowd5ns5iud\n",
-      "PHID-TASK-hg7swbc4ekjgxojfr5bz\n",
-      "PHID-TASK-yr7732vg2ebd5ndyalb6\n",
-      "PHID-TASK-hvvrpcxmtlfovm73otnw\n",
-      "PHID-TASK-maehbrz5znwar2qitk5b\n",
-      "PHID-TASK-nvh5ejbvixlonbrch4jd\n",
-      "PHID-TASK-fsl2ocvagc2ct7mjj527\n",
-      "PHID-TASK-v7tsixpel4mikkpah73h\n",
-      "PHID-TASK-lfunc2bgbzuuwhfvjpdv\n",
-      "PHID-TASK-vdic7routqydx75tmmbb\n",
-      "PHID-TASK-dv6pxr32mobwf3arakop\n",
-      "PHID-TASK-pzrh6lxoqsxowrm5mt6k\n",
-      "PHID-TASK-bltbr6dun3s6724ee3wt\n",
-      "PHID-TASK-qpmnlciz3b3w3vskmgmu\n",
-      "PHID-TASK-gfh3zyqmntwzuisuy7o2\n",
-      "PHID-TASK-xdguppbr4wppxkti274y\n",
-      "PHID-TASK-xjswbfq6vvdy4oyl6qub\n",
-      "PHID-TASK-pruvovx7b4nd6obededc\n",
-      "PHID-TASK-bwileoq2fxrn6ez262yc\n",
-      "PHID-TASK-k5ivcykbmehlps6rrqj3\n",
-      "PHID-TASK-vhod5j4lmpp5giw7zjlk\n",
-      "PHID-TASK-h6knxqbqokuwzylojsm7\n",
-      "PHID-TASK-cv5eyk43xupkutrvi7fo\n",
-      "PHID-TASK-eaknwofmb4d2xflpnx7d\n",
-      "PHID-TASK-7rd7dea5gzp4xsh4amok\n",
-      "PHID-TASK-jrrnahwoyus5omqe5ox7\n",
-      "PHID-TASK-ndh2cqs25x7mmcs6xaye\n",
-      "PHID-TASK-inty44ufbm7rwhc55mom\n",
-      "PHID-TASK-fqccocu2hyrbuqx5yi6l\n",
-      "PHID-TASK-ctzq3dsxntnt7zcuqb4y\n",
-      "PHID-TASK-bflgm4moy2wypdjtiaao\n",
-      "PHID-TASK-pp5tg5rybcmy6c6xwggf\n",
-      "PHID-TASK-t6pdz2y6vcq57sem2c5t\n",
-      "PHID-TASK-pi36geznysiuvpgm2xg5\n",
-      "PHID-TASK-wlq23wlr4vjsce4a5eom\n",
-      "PHID-TASK-ywpcq2rcuhvgvzt5k6zj\n",
-      "PHID-TASK-qe3ooothxjpeykl2xzld\n",
-      "PHID-TASK-2a3roys3zrsyau3jssx7\n",
-      "PHID-TASK-tqro35vsrplftuemdxbd\n",
-      "PHID-TASK-ynwo2pb45ypgaglir47z\n",
-      "PHID-TASK-jps6ok65jqx3whi4rc2h\n",
-      "PHID-TASK-u7qyhofavuvw7qvhg5w6\n",
-      "PHID-TASK-yvmhgidy7jqjbjbp5sta\n",
-      "PHID-TASK-fsxicsfwrmjxla4crdyz\n",
-      "PHID-TASK-jbdbttk2lguhy7gmvjn2\n",
-      "PHID-TASK-ys5ubt2jukiwmzznrvjg\n",
-      "PHID-TASK-q2sq3hniv3ip4n5l2tv4\n",
-      "PHID-TASK-lfnwgg3zbq7kwd5zrvyd\n",
-      "PHID-TASK-zcg333mt7cdvw4jrhfyr\n",
-      "PHID-TASK-wgf3mrrwn3ymravx5tvh\n",
-      "PHID-TASK-sgmrkdjbdkbtrt6o6mwh\n",
-      "PHID-TASK-zkyntw7nvnjqikzefrbn\n",
-      "PHID-TASK-m4d5tcwgzxjphwooyz2c\n",
-      "PHID-TASK-yycd32q4sp6a3jbmgdq4\n",
-      "PHID-TASK-zjrdtyysctdr2ogcnult\n",
-      "PHID-TASK-3otirho2qtinxa5jdm5c\n",
-      "PHID-TASK-suuligy6idoz5fgoqmha\n",
-      "PHID-TASK-34q3bn6uqje2mlmgmqhq\n",
-      "PHID-TASK-5medlyzpqf3k4z7hksir\n",
-      "PHID-TASK-chtpmgo2h5aq6i6j4niv\n",
-      "PHID-TASK-tgulnwlt3ym3t3u4alzn\n",
-      "PHID-TASK-iwk4mxubemdjw56l5wqu\n",
-      "PHID-TASK-ojc6pzmsefmlfjvvupqg\n",
-      "PHID-TASK-pxuflqdxigvalopfqw3z\n",
-      "PHID-TASK-3d7wihxirj5lu7swsg43\n",
-      "PHID-TASK-7aedtfvbjcpnujzhsbiy\n",
-      "PHID-TASK-7akqsunetgzvscos7y7g\n",
-      "PHID-TASK-q2kd7nc4teibu2d6yujb\n",
-      "PHID-TASK-woqw5jwyjb5eshocsjdw\n",
-      "PHID-TASK-e2rzlzqqfl2v7m5ms4g6\n",
-      "PHID-TASK-nspbk6goaacnxvuhl4ff\n",
-      "PHID-TASK-63cm7igyhb5qdw236lct\n",
-      "PHID-TASK-dmuriij6wzg4f6nemlx3\n",
-      "PHID-TASK-hjoe3umj3mbaqn4fu5f7\n",
-      "PHID-TASK-bbycowhblqb7wl5ri2sh\n",
-      "PHID-TASK-kgk6kmve6lavlyhdrvmv\n",
-      "PHID-TASK-m3nqsseg45psoqx36exc\n",
-      "PHID-TASK-log2ro3sq5p5acp2puga\n",
-      "PHID-TASK-7cmqtr6tlqrqawji66zc\n",
-      "PHID-TASK-sqz4vnvgzmxmvjkrplhx\n",
-      "PHID-TASK-jprjjnlynxuoul2du4w2\n",
-      "PHID-TASK-nhhyjbko2xftjs44uuqt\n",
-      "PHID-TASK-ca4ckkjl6hs65faqueyf\n",
-      "PHID-TASK-uv4cfp2ue45fk333wtws\n",
-      "PHID-TASK-3ij7dtc5vwzmge2qmliq\n",
-      "PHID-TASK-wydq63k4j2l2fgeenwfb\n",
-      "PHID-TASK-f4bx3pmct7c24xmmqmka\n",
-      "PHID-TASK-hh227cldfkbylq2gwxw3\n",
-      "PHID-TASK-ugjwuslvzh6eo2ldgto4\n",
-      "PHID-TASK-ys2g6r2fl6x4a5jhjj5w\n",
-      "PHID-TASK-s6nknz73d36vzlhe7o7x\n",
-      "PHID-TASK-6vw3aq5up3oho4pbayyr\n",
-      "PHID-TASK-rdvinxanauxpvzlynziw\n",
-      "PHID-TASK-ncyndehe2estt3jwmggo\n",
-      "PHID-TASK-stsksyo6vo24yafdejoq\n",
-      "PHID-TASK-y6wx3bzrwdh7htuo432k\n",
-      "PHID-TASK-qfmwammnoff7cszevjw6\n",
-      "PHID-TASK-o7xyvob3g2jy33fpbism\n",
-      "PHID-TASK-hyy5m6djppnbb3qc32pu\n",
-      "PHID-TASK-evrtetuy2zbr3a7t4zhq\n",
-      "PHID-TASK-yssbwa6yqsenmbrxptpp\n",
-      "PHID-TASK-a3lcwcpnaonnbhuser76\n",
-      "PHID-TASK-e6xtogl4rredgvs524aw\n",
-      "PHID-TASK-mwak57g5crp4aezvpr7x\n",
-      "PHID-TASK-q7nnm3osibolbwwipfib\n",
-      "PHID-TASK-xwuorocthdcw4tqbqq2f\n",
-      "PHID-TASK-scyl7lhkpp7vgev5i5sy\n",
-      "PHID-TASK-ciiqin6dnqycnrlibykn\n",
-      "PHID-TASK-fwiz7o6xh4rtopisteba\n",
-      "PHID-TASK-dox25wyrywoe37jydxge\n",
-      "PHID-TASK-wvifmqwchjuqimprw5ls\n",
-      "PHID-TASK-rdz73xd47uv2yacm4zi7\n",
-      "PHID-TASK-ca53s4wb5hmrmn3k5jlh\n",
-      "PHID-TASK-yzml3nhjxlsx67vmqf5g\n",
-      "PHID-TASK-m2qyu4hp5hrjchjkpr5h\n",
-      "PHID-TASK-vpi6cxw7fpw4iujs76of\n",
-      "PHID-TASK-bbdpglmzwrfptpvjc4qf\n",
-      "PHID-TASK-usdc5jwsnmb44rymudwh\n",
-      "PHID-TASK-4h4phdyks6plprfkjwnh\n",
-      "PHID-TASK-w23sfro3gylh7zauvhcz\n",
-      "PHID-TASK-5os74s4qlwnokutpo36w\n",
-      "PHID-TASK-e5n7wa77tt6s4carpjsv\n",
-      "PHID-TASK-fg4qhxpyc7qgbgtrnnjy\n",
-      "PHID-TASK-mo2gxuiaaf5jb54y7zdh\n",
-      "PHID-TASK-xad4cjfvysvak3tdxloe\n",
-      "PHID-TASK-oeyka3jairvoviqejllv\n",
-      "PHID-TASK-voh6lpuq6qwl3jpaliry\n",
-      "PHID-TASK-47m3opkl4tk6r424d6ee\n",
-      "PHID-TASK-gzce6zqlyqcwjilrw6bf\n",
-      "PHID-TASK-arr3l5eisybqnti6pj5e\n",
-      "PHID-TASK-sx2ogxi3akejlbpibw6h\n",
-      "PHID-TASK-a7wc4l7yt5s7l3dos7zx\n",
-      "PHID-TASK-tig5qf53lxx7q22k3ipg\n",
-      "PHID-TASK-zf6z6dd2eewg4w66u3vr\n",
-      "PHID-TASK-f7bxhifsd4lp32e2eisz\n",
-      "PHID-TASK-ok2zr74rwqedp7qc3cko\n",
-      "PHID-TASK-ey56a2rp3p2o7wkxvsg6\n",
-      "PHID-TASK-54hi6wjvnjjmrztmmiki\n",
-      "PHID-TASK-wfsi7vtkgqxje73iid73\n",
-      "PHID-TASK-ufnfo3vpfoqevod6gugb\n",
-      "PHID-TASK-dyo7e4yq3hpypzt6oaid\n",
-      "PHID-TASK-u474tffzkippspfbkwn7\n",
-      "PHID-TASK-zfix24cb4ecmeq3x62k4\n",
-      "PHID-TASK-4kmfp6xox5jr7cpq77bb\n",
-      "PHID-TASK-eka3irpvy3o5kqmxjf5b\n",
-      "PHID-TASK-oymg4uxerfmmmfg76vbm\n",
-      "PHID-TASK-zmu5pfwidjokjny4bfvu\n",
-      "PHID-TASK-oh6abcadhuy4bmoaictt\n",
-      "PHID-TASK-xs7dd22v62cbr3tksryr\n",
-      "PHID-TASK-epgl7mls74tyc7pzzpv7\n",
-      "PHID-TASK-iltgxch7wxmytcatl3vo\n",
-      "PHID-TASK-pf7labc5tuafvfstlptu\n",
-      "PHID-TASK-uoqsiopafkhtpu2r5hem\n",
-      "PHID-TASK-fddzs2tnied2swcs624k\n",
-      "PHID-TASK-juwxek3lh7qnt55hfhfo\n",
-      "PHID-TASK-hvyzq7c5neh3uqybtctf\n",
-      "PHID-TASK-5m5zlkgduk4k4cvtcijk\n",
-      "PHID-TASK-4rdwdflxn4nfr6u6rtjg\n",
-      "PHID-TASK-msm6dhxj4earcc46fnei\n",
-      "PHID-TASK-5uacgwuqg3wsvpphjet4\n",
-      "PHID-TASK-p72kac32ipfr5e6rjj23\n",
-      "PHID-TASK-xgh4sxdhab2hhybxk42k\n",
-      "PHID-TASK-55xswnakobrdktp5xg5z\n",
-      "PHID-TASK-lrc5z5oojaqr6d5oluvr\n",
-      "PHID-TASK-gbf4krxvukazedeyc7t6\n",
-      "PHID-TASK-h64673nwftdciwancqe4\n",
-      "PHID-TASK-mto5lbev7aopkjbicd5f\n",
-      "PHID-TASK-lddwevjhaszbxshxxywi\n",
-      "PHID-TASK-7wkbsbpxb6wsld7vrucn\n",
-      "PHID-TASK-xtnd6wdqgp6cwmj72d3c\n",
-      "PHID-TASK-7blxbh53cp3cws3rmqek\n",
-      "PHID-TASK-3iyil63ecpynuu65ebug\n",
-      "PHID-TASK-v5jcyw7wftxsu6hvvjts\n",
-      "PHID-TASK-bzsupfbaq25gtun2byod\n",
-      "PHID-TASK-aiczpu2ygn72rpiek6xz\n",
-      "PHID-TASK-jugonrend4wlvekztr4d\n",
-      "PHID-TASK-zivj5224uzhg27lsf7rt\n",
-      "PHID-TASK-3p6vhaawgb7sqodrhouz\n",
-      "PHID-TASK-3gb5fng3mdx3cf25e4jj\n",
-      "PHID-TASK-ezoyokghacndpxr47zrb\n",
-      "PHID-TASK-gygrr56itpwtjglimrdq\n",
-      "PHID-TASK-72pzweoqmhairfkznqk6\n",
-      "PHID-TASK-4aaydfvos3g3vz7sutt6\n",
-      "PHID-TASK-rf55v7fmqwvlp6c7uvg6\n",
-      "PHID-TASK-5m22o74uyj2fr46ck3hv\n",
-      "PHID-TASK-qe5zfxyv76gy6qgn6hwf\n",
-      "PHID-TASK-w4wbehbgyvkgen7rk24r\n",
-      "PHID-TASK-ffnapmr2ezee3boihytc\n",
-      "PHID-TASK-nftpjhkmvyq4ip3ojgai\n",
-      "PHID-TASK-n4z3dix5blkhrgq34wbj\n",
-      "PHID-TASK-aex5t4ko5dxm65ucfnyl\n",
-      "PHID-TASK-6fk5ybsls3a6cfm65ycp\n",
-      "PHID-TASK-27d4zngimys4mtw4fiz5\n",
-      "PHID-TASK-afkiouif3sgwwazwgdpk\n",
-      "PHID-TASK-64flnckmn275gswhshoe\n",
-      "PHID-TASK-7jjbl4wy6ynwsfmld2oj\n",
-      "PHID-TASK-nkev4xvcykpxkczstis2\n",
-      "PHID-TASK-kcaluu7rsxygp57ew5gr\n",
-      "PHID-TASK-bxani2nv3phs5oyyziql\n",
-      "PHID-TASK-lecf6oguwzmplvfamo26\n",
-      "PHID-TASK-p67up43jsphy5tblzmnk\n",
-      "PHID-TASK-3ptsttym6kp4s3cf6ppu\n",
-      "PHID-TASK-nosrxhvqlznucmrj62x4\n",
-      "PHID-TASK-4z3rc5r4dabblz4yjn64\n",
-      "PHID-TASK-fkh5and23bnoi3f25rdh\n",
-      "PHID-TASK-dggw3rzo3qdyf7wa5for\n",
-      "PHID-TASK-kt5s3xm5kkxkenmgo25a\n",
-      "PHID-TASK-56tbfvr6vp46m2ctcdjg\n",
-      "PHID-TASK-33nc2htx3qd2h333vhm6\n",
-      "PHID-TASK-u5halrjaknddtmd56on4\n",
-      "PHID-TASK-44vu7zrafitz5rmbpcac\n",
-      "PHID-TASK-tp7hcgumrrewgducy7rw\n",
-      "PHID-TASK-di2oqisjl4wdsto2nyxu\n",
-      "PHID-TASK-6hvnj3pserezpnqsws3j\n",
-      "PHID-TASK-bcsluv26xq4a6l2nfhtt\n",
-      "PHID-TASK-ch2annsbdighe2sljgvb\n",
-      "PHID-TASK-7yvphvp4wfoejotflqgu\n",
-      "PHID-TASK-25wimjgt4tsdfufivzhc\n",
-      "PHID-TASK-ddqlzrwdgysvh766ik7s\n",
-      "PHID-TASK-frzymdkyeby2og65igsx\n",
-      "PHID-TASK-j7ic5u4qfl3yfcnkaw35\n",
-      "PHID-TASK-xby2gkgrm5h5zubfd7l5\n",
-      "PHID-TASK-sei7okmjt6zw6r54dwus\n",
-      "PHID-TASK-ss7bz24d7ztd7wl4af5k\n",
-      "PHID-TASK-nmmwisceyjh3lm2bamkh\n",
-      "PHID-TASK-mfpswg7xbkj64zruzhyd\n",
-      "PHID-TASK-lsebojbccynjbxj4wazk\n",
-      "PHID-TASK-rd24i5biuj4r7i3jeier\n",
-      "PHID-TASK-ouvl42pvdoq34kfphg3u\n",
-      "PHID-TASK-5l7l3b3s6yrlk2ddzysl\n",
-      "PHID-TASK-y4soahtd3ne6ieogzdqn\n",
-      "PHID-TASK-krueh2a24bjyg7r3twut\n",
-      "PHID-TASK-dx4wusevsujq7v5py7nu\n",
-      "PHID-TASK-vussyglstlop2mytex2t\n",
-      "PHID-TASK-347gkxmboadsdufxjprl\n",
-      "PHID-TASK-repvwi7xaiozmntsb6ul\n",
-      "PHID-TASK-jseusuuyitcemiu5pnrs\n",
-      "PHID-TASK-xissc7qsu7tkv7xx7nkr\n",
-      "PHID-TASK-xigwlc2e3gsxx4kbk5ix\n",
-      "PHID-TASK-gwdegmhrhwhz5sbml3r5\n",
-      "PHID-TASK-4g6i4gjynjlxlyawm244\n",
-      "PHID-TASK-clgmrlcl24aptweuxikz\n",
-      "PHID-TASK-f7uhw2bgeh3f77k6lvjh\n",
-      "PHID-TASK-cqzkozq3w62lx7y4ycf7\n",
-      "PHID-TASK-mpn6fh3vjrwqonjyzkti\n",
-      "PHID-TASK-5fxfxopay5yizt3sptbe\n",
-      "PHID-TASK-srm34yak2agbaxyhgjji\n",
-      "PHID-TASK-zk5ndm764k2ntbyz65kz\n",
-      "PHID-TASK-gvjursv5fwpt4kgzz2v7\n",
-      "PHID-TASK-gfvkr44kb7p4gblp7hfj\n",
-      "PHID-TASK-kz7ltfye5vll22zw4wk3\n",
-      "PHID-TASK-tunsh3had56hubhfkhlt\n",
-      "PHID-TASK-y3iolseqcvefdxx6knc3\n",
-      "PHID-TASK-csz2uil7ibkp5pr2bftr\n",
-      "PHID-TASK-mjskqwel42qqecgndgvg\n",
-      "PHID-TASK-xk6dzyzmisj4aabwvaxm\n",
-      "PHID-TASK-ydyactq6zkhdtz4zvqql\n",
-      "PHID-TASK-gho3zvnxqkwy4kgvoeo4\n",
-      "PHID-TASK-5kt2ttqsqdttw35wyuft\n",
-      "PHID-TASK-ufpvladvj4hbtquskrvo\n",
-      "PHID-TASK-jy7hdkzqail6eg6yzt7t\n",
-      "PHID-TASK-7loco2tyuhwahwjzohkg\n",
-      "PHID-TASK-ym3q5jy7edmc533tzdy5\n",
-      "PHID-TASK-fvmxjg6y2457g7m277ut\n",
-      "PHID-TASK-cid7l2qphwhjkog4ga2f\n",
-      "PHID-TASK-h725ojkqatxs3kupeh7s\n",
-      "PHID-TASK-fb2f5khj7vp3u2bzxxv6\n",
-      "PHID-TASK-d3rxpccf3znjcbyhsazz\n",
-      "PHID-TASK-7upi3shakwholt2fwmgg\n",
-      "PHID-TASK-lfafbeovak6pyjwejllz\n",
-      "PHID-TASK-63upowwh7qb6xl3mg3rx\n",
-      "PHID-TASK-6k4njahaswdgisg5ovok\n",
-      "PHID-TASK-53ehcwcdlxysbyk5zh6q\n",
-      "PHID-TASK-el77qq7juolzlky357jd\n",
-      "PHID-TASK-cj3vl62yqcs5xpvo2hyk\n",
-      "PHID-TASK-jaospgjrwtyxcof7isza\n",
-      "PHID-TASK-q4wvmsyfsol7m35pdvvw\n",
-      "PHID-TASK-ykvk2t5okmz64pbkm7sn\n",
-      "PHID-TASK-szhiff6d7luj5xmsrczv\n",
-      "PHID-TASK-jbzu5w4c3nerq2feaawm\n",
-      "PHID-TASK-uav3b7isy6kd7g73ifwt\n",
-      "PHID-TASK-tkjl47hcghbp2eadvr32\n",
-      "PHID-TASK-omlsw3dhgwnwrd5t5gd6\n",
-      "PHID-TASK-53i433yt4zo2nejhcsxm\n",
-      "PHID-TASK-ysnk6kht23okwwdp5gp5\n",
-      "PHID-TASK-6hasow53qizwpe3vbpsp\n",
-      "PHID-TASK-swo2rxiy6wgm2jbww3gv\n",
-      "PHID-TASK-zrsnll62nd3qae3uw3jx\n",
-      "PHID-TASK-3vjexhza3sstfguvlk4h\n",
-      "PHID-TASK-24czob2fjkxcqpu77r5w\n",
-      "PHID-TASK-57aftv3xzvmq2c2u7ztm\n",
-      "PHID-TASK-lyvz6pfbh5iamln4kped\n",
-      "PHID-TASK-7qab3gnaeczpqu366xpc\n",
-      "PHID-TASK-3shl4mcz2khwbu4uvoja\n",
-      "PHID-TASK-ibnihv52xnshteoxrd3r\n",
-      "PHID-TASK-yyzfeh3uodjnkeirw6ar\n",
-      "PHID-TASK-difb2qmugpstitptxrln\n",
-      "PHID-TASK-fv7pgm7ma7rzqtzsf675\n",
-      "PHID-TASK-3gt4ltdm5464h2so4dbt\n",
-      "PHID-TASK-si5gnqfnmh6gbx5l4jrp\n",
-      "PHID-TASK-pz2ixq5zf5t25xrb4rxy\n",
-      "PHID-TASK-fynwqc5w5zeshpbxgfhb\n",
-      "PHID-TASK-eegih6kooypkdgwbf43y\n",
-      "PHID-TASK-ruav2ogzbcqvzadctvdr\n",
-      "PHID-TASK-jaeqm7s2wtu2hyzgjf62\n",
-      "PHID-TASK-jtmgedmpbpvmorw6vcq2\n",
-      "PHID-TASK-xttfxhpiryw6znoqo7lj\n",
-      "PHID-TASK-lrdaa764ev2rnhtfh6c7\n",
-      "PHID-TASK-3ia4hoqkuy3so5q5dge4\n",
-      "PHID-TASK-g2k2n2sjdlne5edkxabr\n",
-      "PHID-TASK-vtm3ino3v2y3b5ubwieo\n",
-      "PHID-TASK-47y76ef6fmsctze6gbby\n",
-      "PHID-TASK-ro4iqgaoik67vus6rg36\n",
-      "PHID-TASK-mlrh4edb5aomh7cflcn2\n",
-      "PHID-TASK-xbd775tm7a2kficmtwfv\n",
-      "PHID-TASK-3bxysrz3mthjheir6p4n\n",
-      "PHID-TASK-gmtmxwco32y632mfebna\n",
-      "PHID-TASK-lzzge4gnm7o6yqjh7rmy\n",
-      "PHID-TASK-k5kojkbwzvqt4d36hrd3\n",
-      "PHID-TASK-njmo4dxth5kyk5lgw2it\n",
-      "PHID-TASK-fscihqnuuufaxytwhfkf\n",
-      "PHID-TASK-o53zljq5pyonvqfryedx\n",
-      "PHID-TASK-qunjidjpc6zmzxdvlfx7\n",
-      "PHID-TASK-twvr5rqlyoly5q6lv355\n",
-      "PHID-TASK-6qrknx6d4rhbi2dfof45\n",
-      "PHID-TASK-i5g7enpuggt3etks6uiw\n",
-      "PHID-TASK-uktdpzihh2lhvffqgb4d\n",
-      "PHID-TASK-6qhvami4rv442prsl2cd\n",
-      "PHID-TASK-ixtz4sysk7h76zhcsyps\n",
-      "PHID-TASK-cfsuxmmxpeev6stnegu6\n",
-      "PHID-TASK-cbra3savyka36yjom4gn\n",
-      "PHID-TASK-3m3hkpshul72ld2jnj3z\n",
-      "PHID-TASK-hhbsyblnnelojfdxms2h\n",
-      "PHID-TASK-egjhqqohru7fvy2225t5\n",
-      "PHID-TASK-yrfd4dhbbio3uikl5u33\n",
-      "PHID-TASK-ijh5ohctbismuiczyzo7\n",
-      "PHID-TASK-myea7wfzzuri5j6zmpgx\n",
-      "PHID-TASK-5ho3axzxyziic5a47eop\n",
-      "PHID-TASK-swkths2fnka7qjw7zpsv\n",
-      "PHID-TASK-brrtew2a7sjhjj6dapyh\n",
-      "PHID-TASK-5s5qwgvvgi32pv6mawpw\n",
-      "PHID-TASK-hrp2vnudp6cwigusycqf\n",
-      "PHID-TASK-qez6iozv44a6hxiwzacj\n",
-      "PHID-TASK-tefwphwiw2bjgqazm5r5\n",
-      "PHID-TASK-lwpo5wymv4mwdrrzz7vg\n",
-      "PHID-TASK-6zm5srh6har3jnrlfrt6\n",
-      "PHID-TASK-6b35ocfdr4zn6ivnpbgr\n",
-      "PHID-TASK-avlkvijmssa6on3rse52\n",
-      "PHID-TASK-g5funys7osn7lmrgyu2r\n",
-      "PHID-TASK-7o7uuh5g6ufbb6vnjvbo\n",
-      "PHID-TASK-buuem2aad2voq2wmr3vg\n",
-      "PHID-TASK-ncw7c5qs6xrgoatblkas\n",
-      "PHID-TASK-4sxb362teoe7szw6jzp3\n",
-      "PHID-TASK-gyj6luke5ayhahap6efm\n",
-      "PHID-TASK-selst62j4vfcyd5gk5mu\n",
-      "PHID-TASK-rblj4bx5jecyxjn2maza\n",
-      "PHID-TASK-mrlzc7cbjms7mrkftzkz\n",
-      "PHID-TASK-7jtvwd2g3x4hb6rhdnxy\n",
-      "PHID-TASK-rsayshdqztdym7km5qd3\n",
-      "PHID-TASK-2gy2ywwq2p5i63mtdvsz\n",
-      "PHID-TASK-5rr6tldo3g3davlgjzkz\n",
-      "PHID-TASK-gpxl6tetek6gnjsolbm6\n",
-      "PHID-TASK-d27naw46rmmwvpednony\n",
-      "PHID-TASK-hkmxueiu32djdjwjf6qe\n",
-      "PHID-TASK-co3ofwxr32imhzpdqgr6\n",
-      "PHID-TASK-36q4opdcfxqgzrfpkocm\n",
-      "PHID-TASK-jyohwwldty3v4wbuw5lo\n",
-      "PHID-TASK-jq2yekad4c4aywwp7b2x\n",
-      "PHID-TASK-akuuuyc2bjx7xjtcjegr\n",
-      "PHID-TASK-foq2smoax4kgl2mj4anq\n",
-      "PHID-TASK-nhzlsr5aycf5vf4abhj6\n",
-      "PHID-TASK-vtqdjdocmtgvoothuoyh\n",
-      "PHID-TASK-n3l4te5qxvaeoc3fey5b\n",
-      "PHID-TASK-s24smc5kqzdyl5pvlpcz\n",
-      "PHID-TASK-y76rhjbfn2sjvcyboyko\n",
-      "PHID-TASK-wx2s3qbnx44xiegmal63\n",
-      "PHID-TASK-kg4z3siwsfs5p4zwouaz\n",
-      "PHID-TASK-er23tg3bi4off4fieogn\n",
-      "PHID-TASK-255bhdoqq2fqddmttfct\n",
-      "PHID-TASK-jd374nh4jydelfvamhck\n",
-      "PHID-TASK-manrmfmqhbwpodlyqqk2\n",
-      "PHID-TASK-y2vqmyz5nwnjkvcn4rft\n",
-      "PHID-TASK-5sljz2peyrsgbqkvdo5a\n",
-      "PHID-TASK-56srqkt3lcgu3p7kvj56\n",
-      "PHID-TASK-mnf2geb333qld3ax5dkc\n",
-      "PHID-TASK-grsmbxc6xcqg4so4enlg\n",
-      "PHID-TASK-q6kl2cnzpurtdprt2z7l\n",
-      "PHID-TASK-ojcdgofuxpjixghndf6z\n",
-      "PHID-TASK-td6bfetp5r2m3jb36nd3\n",
-      "PHID-TASK-nbibeqvqnm42dfuywhy4\n",
-      "PHID-TASK-r5hdqedtma6idm3jhqfo\n",
-      "PHID-TASK-2nfazteqrdf6h4dzw2tg\n",
-      "PHID-TASK-rzxhwx6c7jxhiti6ntu6\n",
-      "PHID-TASK-ee2cihypua6u4gysreal\n",
-      "PHID-TASK-b3kyg6embdoi5bsozap4\n",
-      "PHID-TASK-2vwr5t63vss7tgocwalj\n",
-      "PHID-TASK-6xksishkejfbmz5cphbk\n",
-      "PHID-TASK-kyycecb3ijdvy6pujf74\n",
-      "PHID-TASK-yjftwp5bygch5jgawu3q\n",
-      "PHID-TASK-m2mltnucijghdtio7lex\n",
-      "PHID-TASK-mcubwbacjd3vavyugrkq\n",
-      "PHID-TASK-4hlmsxmf5qswcobid4c5\n",
-      "PHID-TASK-2vt7ams74ruy224ob3kr\n",
-      "PHID-TASK-35qnbteoopi7ow3gqvxx\n",
-      "PHID-TASK-o4vsn4ihg5s72o4pgmhn\n",
-      "PHID-TASK-otqxqq3jfgirvkvr5ko2\n",
-      "PHID-TASK-yagspunhz2cfycrqyzbn\n",
-      "PHID-TASK-fpau7gga5ngffxkbjtka\n",
-      "PHID-TASK-wljhvk4gfcklidyyzcbh\n",
-      "PHID-TASK-fpifldug4t73yao6kw5o\n",
-      "PHID-TASK-gtvhfsoc4hivpuvxra7b\n",
-      "PHID-TASK-t7jppwsetf7fxoydv5qc\n",
-      "PHID-TASK-ppr5wcsdufpb6eyyasrg\n",
-      "PHID-TASK-4aq45pqxrqjz2qfggqde\n",
-      "PHID-TASK-tb2ge6debarxu3vvlo2k\n",
-      "PHID-TASK-xfhhffifiyg3hfxvn6x3\n",
-      "PHID-TASK-dztchev2qtofstunypcs\n",
-      "PHID-TASK-wqxkbe4urxqrr546bvml\n",
-      "PHID-TASK-dsrtx3tiu5iommxo6ovz\n",
-      "PHID-TASK-3e33c6y5allxgx2h75vj\n",
-      "PHID-TASK-sk77bsakmg2v6bm4lawd\n",
-      "PHID-TASK-kz6xwcltn5xmr2ey75r7\n",
-      "PHID-TASK-hjqdq6dhlnlap44q7i5f\n",
-      "PHID-TASK-vfujufijqzs5z2vprlzj\n",
-      "PHID-TASK-it6zs5tx5bzoz3374bjq\n",
-      "PHID-TASK-atsl3fekbsgfq2jon2lc\n",
-      "PHID-TASK-whjfcbb2dp7dyl7hx24q\n",
-      "PHID-TASK-afyzlqcbgonyyb4d3b7e\n",
-      "PHID-TASK-wus5sgrv22omy4zu47lx\n",
-      "PHID-TASK-v2h22jpv5cv6bvq6wozz\n",
-      "PHID-TASK-yzw2lh4x4ig5iyfc2jnv\n",
-      "PHID-TASK-l5om5dvvhar7j76c2fnz\n",
-      "PHID-TASK-i47lj2e2ftd5tvqh5r7r\n",
-      "PHID-TASK-f7abfvzj2vf4lqry7phg\n",
-      "PHID-TASK-3pikq7qftwx2jwebgh76\n",
-      "PHID-TASK-ookmj2wjll2ptshhb67g\n",
-      "PHID-TASK-25ulackf33wigk7bvnyg\n",
-      "PHID-TASK-cptw6scnn4zompkjhwyq\n",
-      "PHID-TASK-dakuttxcpl6bkvpemnmx\n",
-      "PHID-TASK-rwqvw5qcvrnogk334awp\n",
-      "PHID-TASK-pvooclgjtrwgebkle3fj\n",
-      "PHID-TASK-ccqdyfu36me32igrajec\n",
-      "PHID-TASK-upqk35oo5h6sa55ff7w5\n",
-      "PHID-TASK-xiyv4jixkvbxe2phirwu\n",
-      "PHID-TASK-7fbhbqnohmq5xaiuz462\n",
-      "PHID-TASK-rg7ifjxavegjy63g4nhz\n",
-      "PHID-TASK-7cbywnlba7fvo6mhudvs\n",
-      "PHID-TASK-qu2aqxrmqddq2le4yre5\n",
-      "PHID-TASK-ckkuvwdfjtbnqb4u7jpk\n",
-      "PHID-TASK-zwu3t35ebtuycwppeq65\n",
-      "PHID-TASK-2jvygydrgf5vwtxvhwak\n",
-      "PHID-TASK-knrygben5z6uuprlfcd4\n",
-      "PHID-TASK-cvzyzrek2t2cvehwvzle\n",
-      "PHID-TASK-k62fxro4rxguo7ka2mon\n",
-      "PHID-TASK-jb2rslshvyhiqokerp5m\n",
-      "PHID-TASK-he2d3umv5r6rhdzphakm\n",
-      "PHID-TASK-p4ulxppdivzqqe2umxe7\n",
-      "PHID-TASK-3p46j5ufygre5dauey6h\n",
-      "PHID-TASK-3gsbzhqvjcq7g3i67lcq\n",
-      "PHID-TASK-evnlmsxi5llkdqpags37\n",
-      "PHID-TASK-akhhxseet47blrfcikb5\n",
-      "PHID-TASK-hzlysdp33ce6zpzmy3wm\n",
-      "PHID-TASK-6rvja2kia3oue26e5a2q\n",
-      "PHID-TASK-f2wyattehq3ovuellsm6\n",
-      "PHID-TASK-tfngbl2qu7djqip3dbd3\n",
-      "PHID-TASK-zx4tbcdiu47yjmwyniwx\n",
-      "PHID-TASK-ty7ads3lpdrt4ghudt2s\n",
-      "PHID-TASK-esodzvlhnrqwgbidaff4\n",
-      "PHID-TASK-iun6kcufna6ud4g23brk\n",
-      "PHID-TASK-dwai2fmvvprbgn2msyx6\n",
-      "PHID-TASK-ify3mxiz6gcnqdo2h2sx\n",
-      "PHID-TASK-ly3c2pbora5rvknhb3sm\n",
-      "PHID-TASK-2ns4vqzbqzflsbtpszu5\n",
-      "PHID-TASK-hob5f3o6eqkkls7qd6k5\n",
-      "PHID-TASK-vmns7e2rmymfweongzav\n",
-      "PHID-TASK-lv7k67pbkstmigdp3rd7\n",
-      "PHID-TASK-lcf23f43lwbo3lfwkrca\n",
-      "PHID-TASK-uysfedps55fdczhfrfys\n",
-      "PHID-TASK-epe55jgajl2jerw3siyg\n",
-      "PHID-TASK-ghws2ohsdojmmph4ub27\n",
-      "PHID-TASK-mf6ollxu3yqurw4viu55\n",
-      "PHID-TASK-t7swuomd63q7e3mou7kp\n",
-      "PHID-TASK-kfr2fhuhxwwkvqg5jwuw\n",
-      "PHID-TASK-cfrutsorovcrc76vfomh\n",
-      "PHID-TASK-4yohlm5rptv4jnlli5mk\n",
-      "PHID-TASK-muxtuy47vttbiujlra5y\n",
-      "PHID-TASK-yuoxq5n2ii32plugotg4\n",
-      "PHID-TASK-is3n3dhxo4ti5nzgooot\n",
-      "PHID-TASK-vcq6z4aphzzlu3bsrflv\n",
-      "PHID-TASK-al543vpnemdlnqyld3n4\n",
-      "PHID-TASK-vnxcxik6c5qmqlw52xaj\n",
-      "PHID-TASK-vpzdercihud4opsstlu6\n",
-      "PHID-TASK-b2btpgodq22ee3ay6bt2\n",
-      "PHID-TASK-mnx5c5z533vu7ca4ybtp\n",
-      "PHID-TASK-5xysqxijiml4iixxb7sd\n",
-      "PHID-TASK-cqgpkdfnpdapeshycn57\n",
-      "PHID-TASK-dxrqwnd4epgrwlipk5o2\n",
-      "PHID-TASK-yj6unjc6sotp4kv2mflx\n",
-      "PHID-TASK-db7owolkladsvbupsv7m\n",
-      "PHID-TASK-wwi2e2vktmnorzseurla\n",
-      "PHID-TASK-7sgyl2imvttq6da7zqhg\n",
-      "PHID-TASK-ylv5ntuga7adnifnjbdx\n",
-      "PHID-TASK-ujchhacr3p2gtsdgmxlg\n",
-      "PHID-TASK-a5fu3pyzxhbjzmz25n7i\n",
-      "PHID-TASK-fn2b4izsi4dcu5lgaxmp\n",
-      "PHID-TASK-43yopxeqsvyzzvqfuavz\n",
-      "PHID-TASK-qyjx6fdbrrh3weriir7z\n",
-      "PHID-TASK-mgmwirwldz45agzrgg3n\n",
-      "PHID-TASK-ta7jealrbrncqvj3zzez\n",
-      "PHID-TASK-aag3cwflmkojbhxxal5q\n",
-      "PHID-TASK-dyxvwjhctefty5l6omxi\n",
-      "PHID-TASK-2uz6thdqdeegj4cxnbup\n",
-      "PHID-TASK-jldo3wo4jenhs2iglbfo\n",
-      "PHID-TASK-jzpbyio6ibhoo7ft5azi\n",
-      "PHID-TASK-342y4tkwn6enbyuyqjn3\n",
-      "PHID-TASK-bjxf522olmedsdx6rpbc\n",
-      "PHID-TASK-6ivr3ri6bvcbt55jfp2f\n",
-      "PHID-TASK-lmosmab7pjd2m5cnmo2t\n",
-      "PHID-TASK-reeypst4562edb7eoqfi\n",
-      "PHID-TASK-pu5wfoxxn6nblwrmsxy7\n",
-      "PHID-TASK-l6w6nyonc7ci3mnehffx\n",
-      "PHID-TASK-26knsdpm5excrpowc3dw\n",
-      "PHID-TASK-pxgyjw5isiqywctk5c7e\n",
-      "PHID-TASK-ur6ykzlvrepzlje7qdsa\n",
-      "PHID-TASK-jbmwpl35zyrkzdw4hfwx\n",
-      "PHID-TASK-gi6xthiyrxw7c2mnmgvl\n",
-      "PHID-TASK-s55lzef3gmpfhhdexj66\n",
-      "PHID-TASK-cq2sis2akuochldidpvr\n",
-      "PHID-TASK-unso5k7lgj5lojo4gz7w\n",
-      "PHID-TASK-upzv2zqhai5rvy7wc6sm\n",
-      "PHID-TASK-jacp3aj4vm5u6h6b4chc\n",
-      "PHID-TASK-nfvv4eym3zcif2i7nb4d\n",
-      "PHID-TASK-dy2dbpcxtagget43fzoa\n",
-      "PHID-TASK-sjrtlm4n5ikwytrhpwex\n",
-      "PHID-TASK-ffqjhxzn42bsoktzv7bm\n",
-      "PHID-TASK-fnziglwvvwpmlxekyjvk\n",
-      "PHID-TASK-zckv7xwfgl4cxjix23f5\n",
-      "PHID-TASK-wvw2grcusq5k2ipkgxi4\n",
-      "PHID-TASK-txrorpbrj6b5ssangri4\n",
-      "PHID-TASK-rafmsmstj5wsl5tvqzu5\n",
-      "PHID-TASK-iwu723btthb7y2jwtq7u\n",
-      "PHID-TASK-ga36aloq6psrxy7t2mlx\n",
-      "PHID-TASK-x7gbeomejfcfsu7jr2ib\n",
-      "PHID-TASK-atfd2medq2qoyjgabdcf\n",
-      "PHID-TASK-cvljbzolxfeydqmcoo2c\n",
-      "PHID-TASK-btbym6mlgax3tzzbkzr4\n",
-      "PHID-TASK-f3cdxehcze5c6igk2koe\n",
-      "PHID-TASK-dv44kcirtbdcglt6wfni\n",
-      "PHID-TASK-zpdzyjmznhwuqu7y5wnu\n",
-      "PHID-TASK-beeof7d2r6t7gnezbj7a\n",
-      "PHID-TASK-nbkquo5siurqmbtxqe3i\n",
-      "PHID-TASK-ykcis27ybwjtiim3musu\n",
-      "PHID-TASK-lreoxwdcbus6wy6gbdcn\n",
-      "PHID-TASK-zatiesduw4yvsu33o45q\n",
-      "PHID-TASK-lusbxefwae6sj2xokbvm\n",
-      "PHID-TASK-tddypvggbabpq3kxu4cc\n",
-      "PHID-TASK-wgyduwg7w4wdsktqalds\n",
-      "PHID-TASK-sfwbwm73nkcseqpbk5if\n",
-      "PHID-TASK-hsvzb36avth2iqas7oad\n",
-      "PHID-TASK-y2wr4truqmwwemxh72yk\n",
-      "PHID-TASK-bmgl5fdektu6pj27wpm4\n",
-      "PHID-TASK-jg5w64dq46rdbpyabqp7\n",
-      "PHID-TASK-yluaahg4ge2upl35udiq\n",
-      "PHID-TASK-i65x4dklyvkvelmyu7om\n",
-      "PHID-TASK-odseemabxyqbdz2dgloa\n",
-      "PHID-TASK-pyseattqnc7yj362nndp\n",
-      "PHID-TASK-onafhjfu75ziw55sv6d6\n",
-      "PHID-TASK-bdnotllyeea37ihjkmr3\n",
-      "PHID-TASK-cn7rkjg6saedlg6no5bg\n",
-      "PHID-TASK-73q6sosb7r2syig35llq\n",
-      "PHID-TASK-3r7ax46g5ehieydsuuvm\n",
-      "PHID-TASK-sl6ozzm6vdvlvv4lpkc6\n",
-      "PHID-TASK-7abqyeltz5gnkmdn4t4n\n",
-      "PHID-TASK-25n5vcma7cdemv6yuhj7\n",
-      "PHID-TASK-hkdfdeny5avjlyz74jqn\n",
-      "PHID-TASK-mztpccwdq5aifemh7iim\n",
-      "PHID-TASK-qeadal5vtjyli2cuuxzk\n",
-      "PHID-TASK-rggykpwnizk34bvpsjp6\n",
-      "PHID-TASK-ing4zbhpdsfypnokceeg\n",
-      "PHID-TASK-apnlro5ql64fbmr7qoty\n",
-      "PHID-TASK-npzavnntwnz6xylar7kw\n",
-      "PHID-TASK-4uk2cqp2bkhf3so3ifse\n",
-      "PHID-TASK-jfjnga5p64vzxczhpota\n",
-      "PHID-TASK-ateveyfcbqb3i4wfvvxx\n",
-      "PHID-TASK-hlwmurrr6a42vwsh4edb\n",
-      "PHID-TASK-52xvekcadppljx7wxtjw\n",
-      "PHID-TASK-ztoidsuy5fwdvtm6hoxa\n",
-      "PHID-TASK-evgaeiyun2bs3jdkzmuq\n",
-      "PHID-TASK-64zcrx2xmqdtz5ns3ivt\n",
-      "PHID-TASK-ganyn24uk5sn6pp36vou\n",
-      "PHID-TASK-buz4r3nu6zcrowjeto7w\n",
-      "PHID-TASK-4e4lr7gjx3fhin7zieit\n",
-      "PHID-TASK-cb45x4k3rxys6v2cqzcc\n",
-      "PHID-TASK-ujehggdfeqiirechz6c2\n",
-      "PHID-TASK-wcreo2gxsoyscsxloyxc\n",
-      "PHID-TASK-xnlwaxwz6vxmxx7sxwlh\n",
-      "PHID-TASK-32x2jdddgorx6i4qqszg\n",
-      "PHID-TASK-i6t6lpxllw2dz6rjfyz5\n",
-      "PHID-TASK-tv63msunrr34jh3gj3an\n",
-      "PHID-TASK-f6ao6kmtchv7v27bft42\n",
-      "PHID-TASK-rdzse5grzzixnnifzj2z\n",
-      "PHID-TASK-ascdutdvqb4aq6opfuse\n",
-      "PHID-TASK-dwpuhdlnvzi2y7re3asf\n",
-      "PHID-TASK-qh3lrsa2vheyfhks3klm\n",
-      "PHID-TASK-k3k3gj4cbyainkrjcrt7\n",
-      "PHID-TASK-h64w6lawxsfffv5qe4yw\n",
-      "PHID-TASK-bevtevpkvtmwwlk2gved\n",
-      "PHID-TASK-izrcwmsj2eh7uaufp4mk\n",
-      "PHID-TASK-pl2ghnqidzao7i2kjzgp\n",
-      "PHID-TASK-ygze3evr6iu2qv2rw7yu\n",
-      "PHID-TASK-gqdob64njr6frqrzr75a\n",
-      "PHID-TASK-aeyfn2tjv55fvu4s3qp4\n",
-      "PHID-TASK-t4cpdxjr67bsgbbjfn5v\n",
-      "PHID-TASK-cdpx3zolbm5hnu4e76jg\n",
-      "PHID-TASK-ee572n6mn4yah76xipnp\n",
-      "PHID-TASK-fe5263dfospwtagdlyvz\n",
-      "PHID-TASK-gguvte4hcswafvyrrjsm\n",
-      "PHID-TASK-mjeduabrtvm33uiu3e4a\n",
-      "PHID-TASK-pkpe26l4yvkcclna5vl6\n",
-      "PHID-TASK-67wpkhw2f4styiyn7rfv\n",
-      "PHID-TASK-dokktb23gmzzq6sf5ts5\n",
-      "PHID-TASK-d2aeownijzkra4jifb23\n",
-      "PHID-TASK-sazwqzfkazbagnggd2du\n",
-      "PHID-TASK-iwpzwdpnv56ft4z3qyze\n",
-      "PHID-TASK-v6t7ev5julnky6rafmtd\n",
-      "PHID-TASK-mwemxfe2uqw3orx4x7j5\n",
-      "PHID-TASK-xtmuxxa5rnveu7aqbphi\n",
-      "PHID-TASK-vjl47zkqiz6gdd6vv7bq\n",
-      "PHID-TASK-7oml5hricm47p3yxxcje\n",
-      "PHID-TASK-33ykzddzyqsfzj3qavxw\n",
-      "PHID-TASK-cq56uabry7nuedxb56e6\n",
-      "PHID-TASK-faz57akdhnnsrbbitdmo\n",
-      "PHID-TASK-oyxqdt66z23wvh7pe5mo\n",
-      "PHID-TASK-yxjf5ed7ojxtui2z6sss\n",
-      "PHID-TASK-tlllnzr2q3k5zu3yv6nh\n",
-      "PHID-TASK-3ydcw352v55xv74m7jhi\n",
-      "PHID-TASK-cudr7dbtubp7jj3ldgha\n",
-      "PHID-TASK-zg7dy72bmhpynpamskgq\n",
-      "PHID-TASK-dfaq53vqbeqqxygg7gqr\n",
-      "PHID-TASK-grvae3imieydt4li7k7h\n",
-      "PHID-TASK-biusmqvxgixprlg4xp34\n",
-      "PHID-TASK-5tthiu6szwn225okbzla\n",
-      "PHID-TASK-x25765urrimfm7ul6ci4\n",
-      "PHID-TASK-7fduwzpt3wlf2h5imzyr\n",
-      "PHID-TASK-u5vpeaoeulxl7k3l2bmg\n",
-      "PHID-TASK-wvxangmpnag4krm3mcnl\n",
-      "PHID-TASK-d6zgk46zgybexfzzc4pr\n",
-      "PHID-TASK-6lutt2i5yzl6odq5e46s\n",
-      "PHID-TASK-uejijc4imv5i4n5hfjzf\n",
-      "PHID-TASK-xucom3pjxavt6vbh6mcr\n",
-      "PHID-TASK-kpw2y2iowrttt6zxpjia\n",
-      "PHID-TASK-oqqiylk3iqavc5qnj32p\n",
-      "PHID-TASK-n6pkynrqsgqpbnp7oitd\n",
-      "PHID-TASK-vqlk4nl6b5bryutwjnk3\n",
-      "PHID-TASK-ysfxvsvtwjpipqsulyul\n",
-      "PHID-TASK-rhordq7y2ulyxaighkvm\n",
-      "PHID-TASK-wzei4tpax7kpf3oq25mp\n",
-      "PHID-TASK-drqb66ingqes5mea47vp\n",
-      "PHID-TASK-k6ov7zzpw2ljayjxrczz\n",
-      "PHID-TASK-32cvx6zgypptrjsr7sri\n",
-      "PHID-TASK-clyi3kkewgt6by3dskxa\n",
-      "PHID-TASK-7b3ttjryq7h2dwfsiked\n",
-      "PHID-TASK-tl2v542il5zhvqmae5zl\n",
-      "PHID-TASK-wyt43e5vzv4rp23bx4s7\n",
-      "PHID-TASK-75qcblrq4xxtwfp5s76f\n",
-      "PHID-TASK-jktlvnskifhm2sbbalki\n",
-      "PHID-TASK-2xs7662hh3qdt5fonxnb\n",
-      "PHID-TASK-poawg73ix2eh7lpylhyd\n",
-      "PHID-TASK-6fjqaicfdcw65wigvygy\n",
-      "PHID-TASK-qdoykgze5mrfb2vlwluc\n",
-      "PHID-TASK-q7kvrcess52gstbba6tv\n",
-      "PHID-TASK-ofqsbhnx4zke4uzfi4r7\n",
-      "PHID-TASK-h6w322yrax25ai4skgpq\n",
-      "PHID-TASK-yifg3bkbmsq2tzfrga4q\n",
-      "PHID-TASK-rstmsueangena7h4cdaj\n",
-      "PHID-TASK-p5tj36n2mckefr5apd2o\n",
-      "PHID-TASK-r3jcy4x4njr5hh24ytpk\n",
-      "PHID-TASK-dljoa7k34bkwqsbvudos\n",
-      "PHID-TASK-zgftkji5nk4n25cdqxjy\n",
-      "PHID-TASK-e3ncbibtfnsjabzzzce6\n",
-      "PHID-TASK-ztq7heekc4zpnp4mj6uf\n",
-      "PHID-TASK-uou7qnzilekcbteofdw4\n",
-      "PHID-TASK-xnegl5h6ucwhzlod3aip\n",
-      "PHID-TASK-msldrstq5fb4d2d5owxm\n",
-      "PHID-TASK-oipcbzqxlofc3iyaefws\n",
-      "PHID-TASK-gk2uxvqxmdwjks3o6oar\n",
-      "PHID-TASK-cka2ffmhei6ufmfdjpyi\n",
-      "PHID-TASK-e6ljc4wlzprcqdkdk7fk\n",
-      "PHID-TASK-qf4dixqxm23hinqfnhhq\n",
-      "PHID-TASK-u7fscppwehap7w2btqmk\n",
-      "PHID-TASK-262uhvu3ikqle2l6ewsw\n",
-      "PHID-TASK-kpzuaoygi6lx5pro226s\n",
-      "PHID-TASK-qh6gg46z66xqohu77fjn\n",
-      "PHID-TASK-i4fozwumgivhnul7k3yd\n",
-      "PHID-TASK-6lw5ypbid2gpphswv2j6\n",
-      "PHID-TASK-knvyif3q5u66km5ufvcb\n",
-      "PHID-TASK-4bokg6oohi7iw7rzhciv\n",
-      "PHID-TASK-4iulhoim62acub7cms4q\n",
-      "PHID-TASK-owjlus7kvzpryeunybdk\n",
-      "PHID-TASK-lunpphbvjkp5qsin6ywz\n",
-      "PHID-TASK-3tivkrvvx7tiwvalguwy\n",
-      "PHID-TASK-qglalluk4kbrg2flbvzv\n",
-      "PHID-TASK-wdo3c45xgv7mte4en6az\n",
-      "PHID-TASK-lxnhaohtjgjw5zamlish\n",
-      "PHID-TASK-cci6rbbarnfeumyquutn\n",
-      "PHID-TASK-jhka5utrurrafo6ytxhv\n",
-      "PHID-TASK-drv4cgq5tb5q7a75rjxp\n",
-      "PHID-TASK-4fybw5go6fyidok4tmp7\n",
-      "PHID-TASK-zolq2daof5tqslp44gue\n",
-      "PHID-TASK-ox6rq6ltvn2e7lv2xj47\n",
-      "PHID-TASK-necjrhau4bastnyumud5\n",
-      "PHID-TASK-pwct3nalejruvwpszxyi\n",
-      "PHID-TASK-fs4ayby7t52qjcroab4t\n",
-      "PHID-TASK-nkytk4yj27kjhhclg73g\n",
-      "PHID-TASK-xc3udo6fxmbjckxyjow3\n",
-      "PHID-TASK-em5ivp4uf7qvneztv3ep\n",
-      "PHID-TASK-zdwyyiwstl6uz4rcbn5g\n",
-      "PHID-TASK-2izho3en3c7veqknv2wr\n",
-      "PHID-TASK-v3h2ouiwohdu44mwy2g6\n",
-      "PHID-TASK-lr6aehasmla6m24l7lfy\n",
-      "PHID-TASK-nqzemfntve3l7ortesoj\n",
-      "PHID-TASK-tz5is7r52hxlpbizafzp\n",
-      "PHID-TASK-fr22j5swh5wt5gmpgdnh\n",
-      "PHID-TASK-r3vxaorhac46omf45tpw\n",
-      "PHID-TASK-vebapwqy2gnmj6e46row\n",
-      "PHID-TASK-tux6tzschtwynlmfypkk\n",
-      "PHID-TASK-iciq5e24fktvreyuptk3\n",
-      "PHID-TASK-v7kj4prknc3sujshfgg3\n",
-      "PHID-TASK-eyovzj2nicd45d4mqp3j\n",
-      "PHID-TASK-b7iac2xw43i4wyam3nwq\n",
-      "PHID-TASK-hd4snxw47ckt4oowe3xb\n",
-      "PHID-TASK-2imau6pf732mnvgzug5k\n",
-      "PHID-TASK-o7nh4k5ffcmrnlrox5vs\n",
-      "PHID-TASK-2jnxk3ykpceaf3icyoim\n",
-      "PHID-TASK-6g7xrokkwj7xvlcpixpd\n",
-      "PHID-TASK-qrmj2zvtj5xzsxn37rp3\n",
-      "PHID-TASK-ynic2zitioz5lqrrxvlq\n",
-      "PHID-TASK-lshlhzbjuwcfnblbdwsc\n",
-      "PHID-TASK-dxxwsml3j6lvywpngjgf\n",
-      "PHID-TASK-bw6slpyeq2u23y3ltra6\n",
-      "PHID-TASK-n4lw5kls7dkiwbydrbtn\n",
-      "PHID-TASK-6hp73xqwptdzkhjkx2ki\n",
-      "PHID-TASK-fbrnpd67ntdl7dxrvivk\n",
-      "PHID-TASK-o2degjsneil7pojmpiav\n",
-      "PHID-TASK-odpakiqqpzglf5pzvu3o\n",
-      "PHID-TASK-rtnmynqsvowvjvcit3ww\n",
-      "PHID-TASK-whtfrzztibmjwea3vy7l\n",
-      "PHID-TASK-zborcq5aeddm5rc2upgl\n",
-      "PHID-TASK-5sshjiczpsr7gablgejn\n",
-      "PHID-TASK-rmktbubqqol74vvmg4zn\n",
-      "PHID-TASK-64pve3q3gx7xk5rm2nk4\n",
-      "PHID-TASK-j5lt672qs5xqtdfzq6de\n",
-      "PHID-TASK-xk6tqgbthziuxrrlpn37\n",
-      "PHID-TASK-tnwafiqbhbl7tln47v6a\n",
-      "PHID-TASK-ywjb7uxxy5pimzykpwh2\n",
-      "PHID-TASK-sdeqwu5trbiv6f7fqfg7\n",
-      "PHID-TASK-3cu7p6qfbrrfjek7shaw\n",
-      "PHID-TASK-5tc7u6hpj3ir3jtg2fhh\n",
-      "PHID-TASK-vus23yeu76aembddoyxe\n",
-      "PHID-TASK-3hi7my5pvgnqne4eigdb\n",
-      "PHID-TASK-zivm3qjikccdl4xebglv\n",
-      "PHID-TASK-lin2kfpz66zdn3l3uhx2\n",
-      "PHID-TASK-ewbthsndzjv2jnkqp2ly\n",
-      "PHID-TASK-dc5kyuqpkf3s6kddlzao\n",
-      "PHID-TASK-tq6ygkwi32qnc2l6vv5h\n",
-      "PHID-TASK-ffowylul32ecwhb6soji\n",
-      "PHID-TASK-nnoorqwvduraaxjx3s3c\n",
-      "PHID-TASK-2mqmky2wjztbg6g74ags\n",
-      "PHID-TASK-mzqqlikp4a7wrk4foid4\n",
-      "PHID-TASK-d6ih3cdrbybmct3lwinv\n",
-      "PHID-TASK-er2j2jzi7wxs7w6xckns\n",
-      "PHID-TASK-pjkjsbfhouqskvpvg6ev\n",
-      "PHID-TASK-nm5db6sizlej6gdhkkqp\n",
-      "PHID-TASK-vedbqhk6swjrkcfcznus\n",
-      "PHID-TASK-o2rqx7ng2feqhiottjsd\n",
-      "PHID-TASK-abb2jsunmv7mixlbbgye\n",
-      "PHID-TASK-u4tbayn5u7dwwaa4yhrw\n",
-      "PHID-TASK-53f6o63dslfan6juoyu2\n",
-      "PHID-TASK-y3mmi3dje57c7pi3w742\n",
-      "PHID-TASK-gwjsvonglc5wqb5w3xah\n",
-      "PHID-TASK-3h2cevtlx5g2a6ncai2m\n",
-      "PHID-TASK-zdr6lujpo7t7bcteewl4\n",
-      "PHID-TASK-lkomsrc6uy5sho4rnfh7\n",
-      "PHID-TASK-forssl3t3nzyfxttmbjs\n",
-      "PHID-TASK-msazj7jjbjrha34imxrt\n",
-      "PHID-TASK-t3ipmvj7oq3ez2aqp4mq\n",
-      "PHID-TASK-zgw6ir3d7s2sg2njimma\n",
-      "PHID-TASK-cxha3l6ahwyau5brwb5g\n",
-      "PHID-TASK-jzhc7bilulnwxwe466rc\n",
-      "PHID-TASK-tyw6vxwg2iqhnxtqi2eo\n",
-      "PHID-TASK-2yyksazxkjyor5p6mer4\n",
-      "PHID-TASK-ovut64wzzg2st7xdxqrv\n",
-      "PHID-TASK-byqi7qvbtypqe3qpqvys\n",
-      "PHID-TASK-w22wdpvzx7smcv2ec6cy\n",
-      "PHID-TASK-eype2avbpoowyttmdlqv\n",
-      "PHID-TASK-bq2wcgmbdrspfxuefmjq\n",
-      "PHID-TASK-xiaw7dpykpv6pphvabfq\n",
-      "PHID-TASK-klisuk3f7xmyrpypvmbw\n",
-      "PHID-TASK-d5x4qtlwe24swelvcnf7\n",
-      "PHID-TASK-3yeacms7h4ndqwnaljiw\n",
-      "PHID-TASK-f2cowtgtc2wzg3hsmtjy\n",
-      "PHID-TASK-nww4b27vuz6kurpzyhrl\n",
-      "PHID-TASK-km5nj6ibsdxpfztnkkyo\n",
-      "PHID-TASK-avlvuxsstbitv7gqtjze\n",
-      "PHID-TASK-lsoz6uynuyo3es6wev2y\n",
-      "PHID-TASK-yjmyhigfoa4mxqt7ha7t\n",
-      "PHID-TASK-ewjtzp76256uwhrcagor\n",
-      "PHID-TASK-ct4l6w4mrliejtnz6hwi\n",
-      "PHID-TASK-rgsze6qyeosq3v4u4bgt\n",
-      "PHID-TASK-4vao55kg5dno6lnw3rh7\n",
-      "PHID-TASK-nx6rwv65d53u3tb74upy\n",
-      "PHID-TASK-kjrhrj6aczzaskvfkmpl\n",
-      "PHID-TASK-bigy3voacwmstnxfox2p\n",
-      "PHID-TASK-j5yw5s756nhxpysj3ya6\n",
-      "PHID-TASK-v25fzfcgl7xz24bzsekb\n",
-      "PHID-TASK-vnsbzpm2rpsys35in4is\n",
-      "PHID-TASK-kozwn3k45tsayt7lttoe\n",
-      "PHID-TASK-2rcyzuif3kfiujpetxoz\n",
-      "PHID-TASK-h6gl5kl5rbsafwe4bbxb\n",
-      "PHID-TASK-wcav44bst4bw55h5vacr\n",
-      "PHID-TASK-kv3qzdtcovilhit5wojg\n",
-      "PHID-TASK-jx334o6lve2gveakyge4\n",
-      "PHID-TASK-2wlcma4q7b3q3yusckvl\n",
-      "PHID-TASK-3wq7rvzz7yhgz4hc5nya\n",
-      "PHID-TASK-m2eygkjsu6uashwjrsks\n",
-      "PHID-TASK-3ojjmktdxwslnqst6zf3\n",
-      "PHID-TASK-sz5p6z5c3eaapd6a7hxt\n",
-      "PHID-TASK-bg7mho6ovlk6kuy4oasm\n",
-      "PHID-TASK-aanfzw3dbp4of5eqkf3w\n",
-      "PHID-TASK-yueggycui2i6sogbyidl\n",
-      "PHID-TASK-wia5kvwoexms6u3azcgb\n",
-      "PHID-TASK-ysyptgmfd7iy7rypjjx3\n",
-      "PHID-TASK-j43eul4onpngbxmfr2sa\n",
-      "PHID-TASK-x6kwfnzot4hyoo5g6hzg\n",
-      "PHID-TASK-cjqylbv337cm23t2r2z6\n",
-      "PHID-TASK-bbylgmiwgkujcoiek33q\n",
-      "PHID-TASK-jslvrd4uihevdc3j7qsn\n",
-      "PHID-TASK-xgn6yi4nvtbkl7ouzmwj\n",
-      "PHID-TASK-ysksgctttx7kwjm25imt\n",
-      "PHID-TASK-qbjbd5yessxi474lujxf\n",
-      "PHID-TASK-etg24hhx2qupzouy5rnw\n",
-      "PHID-TASK-5cganofaldk4meetlmoe\n",
-      "PHID-TASK-qhfyvgtoq7dd2wahxu7j\n",
-      "PHID-TASK-xiestiqvpxbtrw7ppizw\n",
-      "PHID-TASK-miv67zvinnq5ma6mdz7k\n",
-      "PHID-TASK-ja5zqpx3lc7f2cjcms4a\n",
-      "PHID-TASK-nz63pogjll27mlyr4bfz\n",
-      "PHID-TASK-kfwclljbfb2twseyrniu\n",
-      "PHID-TASK-fwu3dpls26ckqdml4hft\n",
-      "PHID-TASK-shlqtr6tjud3djafldgi\n",
-      "PHID-TASK-5lq7dixzl5nvcmty4r7v\n",
-      "PHID-TASK-fzczz22mbckxwxyidfg7\n",
-      "PHID-TASK-pfqaskw64eurbsarzh27\n",
-      "PHID-TASK-p75r2s6odgzvudzsebc2\n",
-      "PHID-TASK-kvgadhnokjawoz2a3myt\n",
-      "PHID-TASK-ma2djbmaav4mlnfs25tp\n",
-      "PHID-TASK-zddhewpobyqo3lkurdqv\n",
-      "PHID-TASK-qi6wc6gcqjrnpifmlnvz\n",
-      "PHID-TASK-3eutuphwveuy6tgpm2lo\n",
-      "PHID-TASK-eudgmmbmz7t3therwbwh\n",
-      "PHID-TASK-j2mehk62spszuq5kxa3y\n",
-      "PHID-TASK-u6zd7ambsyqiu2ueio6t\n",
-      "PHID-TASK-gdczdi6me4o4ykhiyif2\n",
-      "PHID-TASK-nnnclbqpn5cgksi3kujo\n",
-      "PHID-TASK-oycdhxzb7vj25wmx37yl\n",
-      "PHID-TASK-qhhgdhl7wtfejwnw6kuy\n",
-      "PHID-TASK-j3rfh4pmjx4pel7dk2tn\n",
-      "PHID-TASK-hryitnavu3rbrhqscuk7\n",
-      "PHID-TASK-wjmyqwnbfehyswxiilbk\n",
-      "PHID-TASK-d4viyvnin3zjuou7itc4\n",
-      "PHID-TASK-6bdm7pcljc4dgt4wt7gc\n",
-      "PHID-TASK-7kzo6bgqrlkpwpxqbvsn\n",
-      "PHID-TASK-hmwjwgzjxsoee75bqkok\n",
-      "PHID-TASK-mef22t3vme6fkzexu6mp\n",
-      "PHID-TASK-un4pzbob5j2l45f2pfnt\n",
-      "PHID-TASK-gys4tf753s77f4zdjpsb\n",
-      "PHID-TASK-7ylkp2sxhpczkkcpbdi6\n",
-      "PHID-TASK-ncpmmwig7janid6ikysj\n",
-      "PHID-TASK-r3avdlac5as6usqbtpvz\n",
-      "PHID-TASK-g66fda6j3q2ga6eul3do\n",
-      "PHID-TASK-jtv2xb4ipsbwnbem7fka\n",
-      "PHID-TASK-zsmkxbjmo6bthiyirco6\n",
-      "PHID-TASK-ppmnn62nd4u24sclez4h\n",
-      "PHID-TASK-imjhsazltcwrba7knjzi\n",
-      "PHID-TASK-qrsg7i26ioq3iroi5j3v\n",
-      "PHID-TASK-dpwiikhbs2gw5p5foc5a\n",
-      "PHID-TASK-ks4nmmzc4p4mogffuzxg\n",
-      "PHID-TASK-z3skamqtqkfqxyfwcbsx\n",
-      "PHID-TASK-mivgnyfxfz6yjozsfgrs\n",
-      "PHID-TASK-3geuv3zh7grvfypwtx6m\n",
-      "PHID-TASK-ksoksajvjcd37y5wvvq2\n",
-      "PHID-TASK-jfzrmnmoj3qahau2ohse\n",
-      "PHID-TASK-kttslfnxq434mabydy2v\n",
-      "PHID-TASK-pdpuwrbqccg6nncfnxuk\n",
-      "PHID-TASK-g36wsrlii3gd62hxtn2u\n",
-      "PHID-TASK-eulhe75w7cy7if64iutj\n",
-      "PHID-TASK-kloqgpjwhtcokmj7eica\n",
-      "PHID-TASK-w4y2nb4727kwbhfjqdup\n",
-      "PHID-TASK-tyu752voayr4g6elcmgx\n",
-      "PHID-TASK-n2g6v2vrtf3k3hkqsoi3\n",
-      "PHID-TASK-wxztsvwizvyvhpvx2lty\n",
-      "PHID-TASK-blsibbjjroitozskiyjq\n",
-      "PHID-TASK-nsv64fqtru36njpwa54p\n",
-      "PHID-TASK-r5vx4pebxayyrkdqlagy\n",
-      "PHID-TASK-io6eogshz2s3ntb5ae7u\n",
-      "PHID-TASK-g55t2yyhma4clcxdjjey\n",
-      "PHID-TASK-axbu733atg4fftym2lek\n",
-      "PHID-TASK-bzxuqebvczsa3yqj6fmu\n",
-      "PHID-TASK-cafdsbi6thmpaj3iik3u\n",
-      "PHID-TASK-4qp7cge7h2tflfmzkmov\n",
-      "PHID-TASK-yevsvpn7ps2wcpzwmbie\n",
-      "PHID-TASK-l5y2bm67zzyyrk4uvrke\n",
-      "PHID-TASK-e53nvp2e24hk4kjigmbx\n",
-      "PHID-TASK-tsmqnxcmfpxq6jai5pux\n",
-      "PHID-TASK-bplfh6ygtxtpnfjjomyl\n",
-      "PHID-TASK-h4j7vw6gh3bn7a3uis4l\n",
-      "PHID-TASK-ss5sivrosviwhazfuu4q\n",
-      "PHID-TASK-giw7fw2ejpup3mkxp5z7\n",
-      "PHID-TASK-idlocbtqlilq2tqfojzu\n",
-      "PHID-TASK-sqaxwrwatnj3ric4i2qs\n",
-      "PHID-TASK-xb522jegn4symvyf4f4u\n",
-      "PHID-TASK-edwajw6htxppl743yg5e\n",
-      "PHID-TASK-utiy7prmp4a62qvvpo6d\n",
-      "PHID-TASK-flnjgejb5tcqxovz54rt\n",
-      "PHID-TASK-ciosa56mnibqn4lx27ub\n",
-      "PHID-TASK-guukovmsjsnlpphgujcv\n",
-      "PHID-TASK-uztlkap77g3rnibwjzla\n",
-      "PHID-TASK-2u5uxjiqhth3znfq26qw\n",
-      "PHID-TASK-yo4pzdo2eh7soywdrv2r\n",
-      "PHID-TASK-hs2662uteqpf2jylzi43\n",
-      "PHID-TASK-ov5tmb6ogxr2kfhnpik4\n",
-      "PHID-TASK-dnx6tmydfht55cpjp4ur\n",
-      "PHID-TASK-svlkli7eygnwnscchzm6\n",
-      "PHID-TASK-dvfnj4v6d6wmzjocacpy\n",
-      "PHID-TASK-usebfh653647q2fmkkwk\n",
-      "PHID-TASK-mdlouwe6duqgfyx233gy\n",
-      "PHID-TASK-qz33ogip6xbczaatjhcs\n",
-      "PHID-TASK-lksk7iecqxpzkmtpqlr5\n",
-      "PHID-TASK-2teo2k6a5oyvyz7ddfv7\n",
-      "PHID-TASK-s5at4xy2rbu4kz3beaqh\n",
-      "PHID-TASK-bzskyradcmgpuo2efgwc\n",
-      "PHID-TASK-jwtr42v56pyz6l6jnzpx\n",
-      "PHID-TASK-bm7u2vdbvfhrl7phrzgv\n",
-      "PHID-TASK-qku5ds4p6huc4ehidnf2\n",
-      "PHID-TASK-l2wcdsvwatewpompucdp\n"
+      "{'name': 'EchoTitleLocalCacheTest::testGet fails when tests are run with other extensions', 'description': {'raw': 'When running Echo extensions tests under HHVM/Zend, Jenkins ends up with a failure:\\n\\n```\\n1) EchoTitleLocalCacheTest::testGet\\nFailed asserting that null is an instance of class \"Title\".\\n\\nextensions/Echo/tests/phpunit/includes/cache/TitleLocalCacheTest.php:37\\ntests/phpunit/MediaWikiTestCase.php:141\\n```\\n\\nIn a workspace with the following extensions:\\n\\nmediawiki/extensions/Echo\\nmediawiki/extensions/JsonConfig\\nmediawiki/extensions/Mantle\\nmediawiki/extensions/MobileApp\\nmediawiki/extensions/MobileFrontend\\nmediawiki/extensions/VisualEditor\\nmediawiki/extensions/WikiGrok\\nmediawiki/extensions/ZeroBanner\\nmediawiki/extensions/ZeroPortal\\n\\n\\nRunning the Echo tests standalone pass ( php tests/phpunit/phpunit.php extensions/Echo )\\n\\nThe whole testsuite fails though:\\n```\\ncd tests/phpunit\\nphp phpunit.php --testsuite extensions\\n```\\n\\nOr slightly faster:\\n```\\ncd tests/phpunit\\nphp phpunit.php --testsuite extensions --filter \\'Echo\\' --stop-on-failure\\n```'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-r5pzlcquei6f4hb53rfg', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'dateClosed': 1422579586, 'spacePHID': None, 'dateCreated': 1418676203, 'dateModified': 1471002847, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor has been disabled unexpectedly on fr.wiktionary', 'description': {'raw': 'Hi,\\n\\nVisual Editor has been enabled on fr.wikt after https://phabricator.wikimedia.org/T65187 ; but now it has been disabled, it seems since last night (maybe since the installation of the version 1.25wmf9 of MediaWiki).\\n\\nAny idea?'}, 'authorPHID': 'PHID-USER-76b52mrhaky23u2wzwmg', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417046899, 'spacePHID': None, 'dateCreated': 1417040370, 'dateModified': 1572642861, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor does not open at en.wikipedia.beta.wmflabs.org', 'description': {'raw': '- go to http://en.wikipedia.beta.wmflabs.org/\\n- log in as Selenium user\\n- make sure VisualEditor is enabled at http://en.wikipedia.beta.wmflabs.org/wiki/Special:Preferences#mw-prefsection-betafeatures\\n- go to http://en.wikipedia.beta.wmflabs.org/wiki/Language_Screenshot?veaction=edit\\n- VisualEditor never opens\\n- the loading bar in the top-right part of the screen just cycles (see screen shot) {F15998}'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'dateClosed': 1416943522, 'spacePHID': None, 'dateCreated': 1416911298, 'dateModified': 1416943522, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:[Regression wmf8] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box', 'description': {'raw': '\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416275852, 'spacePHID': None, 'dateCreated': 1416275760, 'dateModified': 1417049187, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73542', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Fatal error: Class undefined: ResourceLoaderTemplateModule in /srv/mediawiki/php-master/includes/resourceloader/ResourceLoader.php on line 506', 'description': {'raw': 'see e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Links_VisualEditor_Test?vehidebetadialog=true&veaction=edit\\n\\nsee screen shot for error\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415911888, 'spacePHID': None, 'dateCreated': 1415899860, 'dateModified': 1454003778, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73377', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression pre-wmf8] \"Uncaught Error: Unknown dependency: rangefix\"  appears while trying to load mobile VE', 'description': {'raw': 'screenshot\\n\\n\"Uncaught Error: Unknown dependency: rangefix\"  appears while trying to load mobile VE\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker\\n\\n**Attached**: {F15023}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415663306, 'spacePHID': None, 'dateCreated': 1415213160, 'dateModified': 1417049187, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73038', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf7] Cite command not working (but cite-tranclusion does)', 'description': {'raw': \"Can't work out why; supportedSelections is set for both.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415233236, 'spacePHID': None, 'dateCreated': 1415152200, 'dateModified': 1417049188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73001', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] VisualEditor gets unresponsive after adding a template', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Insert any template in the page\\n\\nObserved Result:\\nVE gets completely unresponsive after this action,Cannot make any other change or save the page. No error in the console.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415127700, 'spacePHID': None, 'dateCreated': 1415127300, 'dateModified': 1417049189, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72961', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] Cannot add any Citations or Basic reference in a page , throwing Typeerror \" Cannot read property \\'replace\\' of undefined \"', 'description': {'raw': 'On any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit\\n\\nClick Cite/Website or any other Cite selection. \\n\\nNothing happens. No Cite inspector appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415151534, 'spacePHID': None, 'dateCreated': 1415111400, 'dateModified': 1417049188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72948', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] Empty Add Template dialog appearing upon trying to open an existing template from a page', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a template for example: Cite Web/Citation needed\\n3.Save the page\\n4.Reopen the page\\n5.Reopen the Transclusion dialog for the template you just added\\n\\nObserved Result:\\nInstead of the template dialog with all the parameters in it , it appears as an empty \"Add Template\" dialog \\n\\nSee the screenshot attached\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14841}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414703188, 'spacePHID': None, 'dateCreated': 1414622880, 'dateModified': 1417049189, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72719', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking in a table that contains templated rows causes JS error', 'description': {'raw': '1. Go to http://en.wikipedia.beta.wmflabs.org/wiki/User:RoanKattouw/Evil_table?veaction=edit\\n2. Click on a non-templated cell in the table (e.g. the cell that says \"simple\" in row 2)\\n3. \"undefined is not a function\" error appears in console\\n\\nWhat happens is that TableMatrix#update runs, and when it hits cell (2,0) (3rd row, 1st column), it will find that cellNode is a ve.dm.MWTransclusionNode rather than a ve.dm.TableCellNode, and so calling .getRowSpan() on it will explode.\\n\\nWe probably need some way to deal with templated rows/cells in the middle of an otherwise normal table, but I\\'m not entirely sure what that should look like. Maybe we can get away with skipping over these rows/cells everywhere in a consistent manner, and hopefully that will work out OK?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415041264, 'spacePHID': None, 'dateCreated': 1414622340, 'dateModified': 1417049188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72717', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cut+paste of {{convert}} and {{cite web}} unleashes invasion of snowman clone army in endless loop', 'description': {'raw': 'Steps to reproduce:\\n\\n* Open https://en.wikipedia.org/wiki/Snowman?veaction=edit\\n\\n* Mark the sentence \"It was 113\\xa0feet 7\\xa0inches (34.62\\xa0m) tall and weighed over 9,000,000 pounds (4,080,000\\xa0kg).[1]\" and cut it (Strg+X).\\n\\n* Paste it in again (Strg+V).\\n\\n* Click before \"It\" to place the cursor at the beginning of the sentence.\\n\\n\\nResult: The editor starts adding copies of the sentence in an endless loop, with the templates (see below) replaced by snowmen:\\n\\n\"It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ☃☃ tall and weighed over ☃☃.☃☃It was ...\"\\n\\n(Actually, if one scrolls or clicks somewhere in the page, the loop may stop, but I\\'ve observed it going on for more than a minute, generating 378 copies of the sentence.)\\n\\n\\nHere is the wikitext source of the sentence:\\n\\n\"It was {{convert|113|ft|7|in|m}} tall and weighed over {{convert|9000000|lb|kg|-4}}.<ref>{{cite web|url=http://www.sundayriveron-line.com/AngusSnowman_1.htm|title=Angus, King of the Mountain &mdash; World\\'s Largest Snowman|date=February 19, 1999|publisher=Sunday River On-Line|archiveurl=http://web.archive.org/web/20071012082219/http://www.sundayriveron-line.com/AngusSnowman_1.htm|archivedate=2007-10-12}}</ref>\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wlku5ja6envbi4cz2etp', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414625279, 'spacePHID': None, 'dateCreated': 1414245600, 'dateModified': 1417048866, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72512', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf4] “Uncaught TypeError: undefined is not a function” when Citation dialog opens', 'description': {'raw': \"screenshot\\n\\nEnvironment- beta\\n\\n1> click on Cite and pick any citation(book/web/news/journal).E.g- select cite -> book. Cite book dialog opens.\\n2> JS console error “Uncaught TypeError: undefined is not a function”.\\n3> Click to Add more information and error in console is “Uncaught TypeError: Cannot read property 'on' of undefined”. See screenshot.\\n4> Clicking on cancel or insert does not close the dialog.\\n\\nScreenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14994}\"}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413319128, 'spacePHID': None, 'dateCreated': 1413212460, 'dateModified': 1417049189, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71997', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf2] Deleting any focusable node throws \"error:NS_ERROR_FAILURE:\" in Firefox and wrong context menu starts appearing for other nodes', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Select any focusable node: citation note,math ,template or image\\n\\nObserved Result:\\n\\nThe following error appears in the console:\\nNS_ERROR_FAILURE: \\n\\nThe context menu for that focusable note is still active in CE ,if you select some other focusable note after this, no context menu appears for it or the one for previous node appears on top of it\\n\\nEnvironment:test2 and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F15335}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412358876, 'spacePHID': None, 'dateCreated': 1412290980, 'dateModified': 1417049190, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71580', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: The GIT Plugin is broken for submodules (\"git-submodule: git reset: not found\")', 'description': {'raw': 'Jobs running on Ubuntu Trusty for repositories with submodules are currently broken due to a bug in the Jenkins GIT Plugin.\\n\\nWe use Jenkins GIT Plugin 1.5.0, which uses git-client-plugin 1.0.6:\\nhttps://github.com/jenkinsci/git-client-plugin/blob/git-client-1.0.6/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L401-L412\\n\\n        args.add(\"submodule\", \"foreach\");\\n        if (recursive) {\\n            args.add(\"--recursive\");\\n        }\\n        args.add(\"git reset\");\\n        if (hard) {\\n            args.add(\"--hard\");\\n        }\\n\\nhttps://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/4684/console\\n\\n\\nCleaning workspace\\nResetting working tree\\nFATAL: Command \"submodule foreach --recursive git reset --hard\" returned status code 1:\\nstdout: Entering \\'lib/ve\\'\\nstderr: /usr/lib/git-core/git-submodule: 552: /usr/lib/git-core/git-submodule: git reset: not found\\nStopping at \\'lib/ve\\'; script returned non-zero status.\\n\\nTrying to reproduce:\\n\\njenkins-deploy@integration-slave1007:/mnt/jenkins-workspace/workspace/mwext-VisualEditor-npm$ git submodule foreach --recursive git reset --hard\\n> works fine\\n\\nThe version of git on Ubunty and Precise both support this command.\\nThe problem lies in the quoting and separation of the arguments.\\n\\njenkins-deploy@integration-slave1007:/mnt/jenkins-workspace/workspace/mwext-VisualEditor-npm$ git submodule foreach --recursive \\'git reset\\' --hard\\n> /usr/lib/git-core/git-submodule: 552: /usr/lib/git-core/git-submodule: git reset: not found\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412204994, 'spacePHID': None, 'dateCreated': 1412198400, 'dateModified': 1432822495, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71533', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf1] \"Uncaught NotFoundError: Failed to execute \\'insertBefore\\' on \\'Node\\': ..\" while inserting a comment', 'description': {'raw': \"screenshot\\n\\nEnvironment-test2\\n\\n1> In a blank page, insert a comment.\\n2> open edit comment dialog. While the dialog is still open and cursor is blinking inside it, select any of the font styles except Language. For ex- select Bold or Italic.\\n\\nJS console error is -:\\n\\n“Uncaught NotFoundError: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node”\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n\\n**Attached**: {F14867}\"}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412039720, 'spacePHID': None, 'dateCreated': 1412007720, 'dateModified': 1417048867, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71418', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf1] Comment box is not opening in Betalabs', 'description': {'raw': \"Cannot open comment box in Betalabs. Throwing the following error in the console:\\nUncaught TypeError: Cannot read property '0' of undefined\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411587035, 'spacePHID': None, 'dateCreated': 1411584480, 'dateModified': 1443277990, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71246', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf1] Link button does nothing', 'description': {'raw': 'Edit any page on beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit\\n\\nClick the Link button. Nothing happens.\\n\\nError console shows \"TypeError: this.isValid(...).done is not a function\"\\n\\nNo other controls seem to be affected by this issue.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411587015, 'spacePHID': None, 'dateCreated': 1411574820, 'dateModified': 1443277991, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71237', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Saving replaces categories with [[MediaWiki:Badtitletext]]', 'description': {'raw': 'http://de.wikipedia.org/w/index.php?diff=134089498\\nhttp://de.wikipedia.org/w/index.php?diff=134090414\\n\\nVisualEditor is replacing categories in articles with \"[[MediaWiki:Badtitletext]]\". Please fix it as soon as possible or deactivate VE. We do not have any time or desire to check and correct hundreds of revisions caused by broken software.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-vvufz7opk2hhimdzyznx', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410895179, 'spacePHID': None, 'dateCreated': 1410893460, 'dateModified': 1443277994, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70897', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Style and bgcolor attributes normalized by Internet Explorer', 'description': {'raw': 'When you edit a page with VE in IE, CSS styles are normalized, causing dirty diffs. This is because Internet Explorer very aggressively normalizes styles, to the point where we can\\'t tell what the original value was without some nasty hackery.\\n\\nIn practice, this means that any time you save a page in IE, things like style=\"color: #ffffdd;\" get normalized to style=\"color: rgb(255, 255, 221);\", bgcolor=\"#FFFFDD\" gets normalized to bgcolor=\"#ffffdd\" and invalid CSS is removed. The former two are annoying dirty diffs, the latter is actual information loss (someone else can come along later and fix invalid CSS, but not if we remove it).\\n\\nThis normalization is a bug in Internet Explorer. I\\'m working on a workaround where I extract the original value using an XML parser and stash it so I can restore it later.\\n\\nhex to rgb normalization: https://fr.wikipedia.org/?diff=107359735\\nbgcolor normalization: https://sv.wikipedia.org/?diff=27502354\\nInvalid CSS removal: https://cs.wikipedia.org/?diff=11849661\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410837485, 'spacePHID': None, 'dateCreated': 1410805080, 'dateModified': 1443277994, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70856', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] Inserting multi-node template (?) causes endless snowmen', 'description': {'raw': 'Initial case:\\n\\n1. Go to https://www.mediawiki.org/wiki/VisualEditor/status?veaction=edit.\\n2. Scroll to the final section, remove the \"…\", and insert template.\\n3. Pick \"key press\" in the normal way.\\n4. Set parameter 1 as \"Ctrl\", parameter 2 as \"Shift\", and parameter 3 as \"V\".\\n5. Press \"Insert\".\\n\\nResult: dialog remains pending whilst endless snowmen get inserted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://www.mediawiki.org/w/index.php?title=VisualEditor/status&oldid=1152478'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410561601, 'spacePHID': None, 'dateCreated': 1410545940, 'dateModified': 1443277999, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70777', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf18] Cite, Insert, format dropdown elements do not bring up dialog', 'description': {'raw': 'On any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Cite_VisualEditor_Test?veaction=edit\\n\\nclick Cite, then choose any of Website, Book etc. \\n\\nUser should see an inspector dialog for that cite, but nothing appears\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408642084, 'spacePHID': None, 'dateCreated': 1408638180, 'dateModified': 1443278026, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69856', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Cannot load Mobile VE in Betalabs in iOS safari', 'description': {'raw': 'I cannot load any page with Mobile VE with iOS safari but it works fine in desktop Safari.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406927676, 'spacePHID': None, 'dateCreated': 1406840040, 'dateModified': 1443278043, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68949', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression pre-wmf16] Scrolling and tapping into CE goes dead after using link inspector', 'description': {'raw': \"This just appeared as of a couple hours ago:\\n\\n1. Go into VE edit mode on beta labs\\n2. Select a word and tap link inspector icon in toolbar\\n3. Tap done to make the word a link\\n4. When you return to the article in edit mode, you're no longer able to scroll the content or tap in to drop the cursor anywhere. All you can do is save, reopen the link inspector, or abandon changes.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-yu5wnmvkjecufsjgh2fa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406761982, 'spacePHID': None, 'dateCreated': 1406757000, 'dateModified': 1443278044, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68878', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Changes made after reviewing changes are not sent (when caching is enabled)', 'description': {'raw': \"1. Make a change to a page on en.wiki and click review changes form the save dialog\\n2. Close the save dialog and make another change, go back to the review changes page\\n\\nObserve that only your first change is visible. The same is true if you submit the change.\\n\\nThis does not happen on my local wiki where I don't have pre-save caching enabled, so presumably it has something to do with that.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406390642, 'spacePHID': None, 'dateCreated': 1406389140, 'dateModified': 1443278055, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68619', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf16] Cannot open any page with Mobile VE in Betalabs', 'description': {'raw': 'I cannot open any page with Mobile VE with iOS Safari, however in desktop Safari I am not seeing this issue\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406656292, 'spacePHID': None, 'dateCreated': 1406315700, 'dateModified': 1443278058, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68584', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: MobileContext is not in the DOM', 'description': {'raw': \"**Author:** `jgonera`\\n\\n**Description:**\\nWhen running VE on mobile, in the console:\\n\\n$('.ve-ui-context')\\n[]\\n$('.ve-ui-mobileContext')\\n[]\\n\\nI thought that the context not appearing on mobile was a CSS regression but it seems it's no longer attached to the DOM. Too tired today to figure out why (or to figure out how DesktopContext is attached to DOM).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406342047, 'spacePHID': None, 'dateCreated': 1406248440, 'dateModified': 1443278059, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68546', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf15] Pressing return after a link is throwingTypeError: Cannot read property 'getOuterLength' of undefined VM112:521\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which contains a link \\n2.Press return after the link\\n\\nObserved Result:\\nUncaught TypeError: Cannot read property 'getOuterLength' of undefined VM112:521 \\nappears in the console\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14637}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406080047, 'spacePHID': None, 'dateCreated': 1406073900, 'dateModified': 1443278066, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68415', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When making text bold or italic following a template, pawn symbol appears', 'description': {'raw': 'In hebrew wikipedia, when I have created a new article, added a tamplate to it, wrote text and made it bold or italic - instead of the text appeared a pawn symbol, that was bold or italic according to the button I have clicked.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68147\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68691'}, 'authorPHID': 'PHID-USER-em3l7mquu7qcck24eqq5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406660955, 'spacePHID': None, 'dateCreated': 1405590900, 'dateModified': 1443278075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68151', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf14] The cursor stays enabled in readmode after saving a page', 'description': {'raw': 'Screenshot\\n\\nAfter saving a page,cursor still remains enabled on readmode in Betalabs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14361}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406220733, 'spacePHID': None, 'dateCreated': 1405447980, 'dateModified': 1443278082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68048', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor positioning broken after about-grouped inline alien', 'description': {'raw': 'From bug 58221:\\n\\nTilman Bayer 2014-07-14 04:16:20 UTC\\n\\nAnother example:\\n\\nIn https://en.wikipedia.org/w/index.php?oldid=616866203&veaction=edit , place the cursor left of \"F\" in the word \"Former\" in the first paragrah, and hit the delete key. The \"F\" is deleted correctly, but the cursor jumps two to the left (between \"s\" and \".\").\\n\\nReproduced in Firefox and Chromium under Ubuntu 14.04.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405381338, 'spacePHID': None, 'dateCreated': 1405341540, 'dateModified': 1443278085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67985', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf13] None of the cite options or template dialogs are opening, throwing error:Uncaught TypeError: Cannot read property 'bind' of undefined\", 'description': {'raw': \"Cannot open any cite options or template in betalabs or add it in an article throwing error:\\nUncaught TypeError: Cannot read property 'bind' of undefined\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405027059, 'spacePHID': None, 'dateCreated': 1405015260, 'dateModified': 1443278089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67814', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf12] The Math Inspector loses its focus each time a character is inserted when it tries to parse the new value', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Formula\\n3.Attempt to insert \"\\\\pi\" inside the inspector\\n\\nObserved Result:\\nAs soon as you type \\\\ in the inspector , it loses its focus and tries to parse that \\\\ and shows error \"Failed to parse (lexing error)\"\\n\\n\\nEnvironment:Betalabs\\nSee the screenshot attached\\nBrowser:Chrome\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14534}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406162644, 'spacePHID': None, 'dateCreated': 1404157860, 'dateModified': 1443278106, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67326', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Revert of Math extension in wmf9 causes VisualEditor to crash with \"Models must be subclasses of ve.dm.Model\" on every page', 'description': {'raw': 'On https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-06-11?veaction=edit I am getting this stack trace from VE:\\n\\nError: Models must be subclasses of ve.dm.Model\\n    at VeDmModelRegistry.ve.dm.ModelRegistry.register (eval at <anonymous> (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:4:670), <anonymous>:276:655)\\n    at mw.loader.implement.math-visualeditor-mwmathinspector-title (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.math.visualEditor&skin=vector&version=20140613T004358Z&*:1:363)\\n    at runScript (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:171:201)\\n    at checkCssHandles (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:171:602)\\n    at execute (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:172:384)\\n    at Object.mw.loader.implement (https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&m…w.MwEmbedSupport&only=scripts&skin=vector&version=20140612T192101Z:178:208)\\n    at https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.math.visualEditor&skin=vector&version=20140613T004358Z&*:1:11\\n\\nChromium 35.0.1916.153, Linux\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402683992, 'spacePHID': None, 'dateCreated': 1402629360, 'dateModified': 1402683992, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66566', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf7] Cursor is no longer getting automatically placed in the edit summary field; document isn't unfocussed in Firefox\", 'description': {'raw': 'Note: This happens in mediawiki.org (1.24wmf7 (941d0e1)), but not in en.wikipedia (1.24wmf6 (4331f6b)).\\n\\nTo reproduce:\\n1. Edit an article. Make a change.\\n2. Press \"Save page\".\\n3. Try writing an edit summary.\\n\\nObserved: The text is added to the article.\\n\\nExpected: The cursor must automatically focus in the edit summary field.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402080269, 'spacePHID': None, 'dateCreated': 1401957480, 'dateModified': 1443278145, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66168', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: SurfaceWidget always creates a DesktopSurface, even when the target is mobile', 'description': {'raw': 'This is bad.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401324126, 'spacePHID': None, 'dateCreated': 1400777100, 'dateModified': 1443278162, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ResourceLoader seems to sometimes not see Gadget modules (due to mw1151)', 'description': {'raw': 'A few users are reporting (default) gadgets are missing on Portuguese Wikipedia:\\n* https://pt.wikipedia.org/w/index.php?oldid=38937709#Scripts_n.C3.A3o_funcionando.21\\n* https://pt.wikipedia.org/w/index.php?oldid=38937709#Sem_fast-buttons.2C_sem_hot-cat\\n* https://pt.wikipedia.org/w/index.php?oldid=38937709#Problema_com_naveboxes\\n* https://pt.wikipedia.org/w/index.php?oldid=38937709#Marcas_de_destaque_n.C3.A3o_aparecem\\n\\nCurrently, ptwiki is running 1.24wmf4.\\n\\nMaybe related:\\n* Bug 65340\\n* Bug 65375\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Caf%C3%A9_dos_programadores&oldid=38938024#Problemas_com_os_gadgets'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400289578, 'spacePHID': None, 'dateCreated': 1400280420, 'dateModified': 1401904218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65424', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Firefox throws NS_ERROR_NOT_AVAILABLE when clicking save button', 'description': {'raw': 'Seen in Firefox 27 on Windows 8, FF 29 on OSX 10.6\\nReported also on Win7, OSX 10.9\\n\\nEdit any page on mw.o (or beta labs)\\n\\nSave button is clickable but does nothing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400260271, 'spacePHID': None, 'dateCreated': 1400256360, 'dateModified': 1417049196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65401', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression 1.24wmf5] OOjs UI: Firefox throws NS_ERROR_NOT_AVAILABLE when opening certain dialogs', 'description': {'raw': 'NS_ERROR_NOT_AVAILABLE: appearing while trying to save a page in Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400540821, 'spacePHID': None, 'dateCreated': 1400192580, 'dateModified': 1427403770, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65373', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf3] Changing a citation in the citation tool inserts a new citation, doesn't replace the old one\", 'description': {'raw': 'Intention:\\nFix the URL in a citation\\n\\nSteps to Reproduce:\\n1. Open an existing citation, using the citation tool.\\n\\n2. Change something.\\n\\n3. Apply changes.\\n\\n4. Look, now you have two:  first an old/wrong version, then a new/corrected version.\\n\\nhttp://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_%28WMF%29/Sandbox&diff=91692&oldid=91691\\n\\n\\n\\nReproducible: Always\\n\\nSame problem in Firefox and Safari.  No problems with this using the Insert>Reference editor, even though that opens the citation tool for editing citation templates.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399334428, 'spacePHID': None, 'dateCreated': 1398978480, 'dateModified': 1443278188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64717', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf2] \"Undo\" button remains disabled through out the edit session in Betalabs', 'description': {'raw': 'Type anything or do any edit on any page in Betalabs \\n\\nThe undo button remains disabled even you made some changes to that page\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398109461, 'spacePHID': None, 'dateCreated': 1398104580, 'dateModified': 1443276211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64194', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf1] While trying to open Hiero/Math/Gallery inspector TypeError:Cannot read property 'forcedLtr' of undefined appears in the console\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Try to open the Heiroglyphics inspector\\n\\nObserved Result:\\nThe following error shows up in the console:\\nUncaught TypeError: Cannot read property 'forcedLtr' of undefined \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13714}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398110223, 'spacePHID': None, 'dateCreated': 1397767500, 'dateModified': 1443276214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64072', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf1] Save page button does not become enabled upon adding any text/changing format/adding reference in CE for Betalabs', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a text/change the format of a text\\n\\nObserved Result:\\nThe\"Save Page\" button remains disabled on the page\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397701109, 'spacePHID': None, 'dateCreated': 1397695080, 'dateModified': 1443276214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64042', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf1] Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds is appearing in Mobile VE after reopening a page for the second time and hitting return twice', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Mobile VE\\n2.Close the VE for it\\n3.Again reopen the page with VE\\n4.Go to the last and hit return twice\\n\\nObserved Result:\\nThe following error appears in the console:\\nUncaught Error: ve.dm.Document.getNodeFromOffset(): offset 339 is out of bounds\\n\\nSee the screenshot attached\\n\\nTest Environment:http://en.m.wikipedia.beta.wmflabs.org/\\nPage: http://en.m.wikipedia.beta.wmflabs.org/wiki/New_page_for_testing_the_special_characters_by_creating_a_new_page#editor/0\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13638}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398127109, 'spacePHID': None, 'dateCreated': 1397687700, 'dateModified': 1443276217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64034', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf1] Cannot add reflist in a page in Betalabs', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Add some references\\n3.Insert a reflist\\n4.Click on the \"Save Page\" button\\n5.Click on \"Review your changes\"\\n\\n\\nObserved Result:\\nThere is no wikitext for the reflist , in the review changes panel it says:\\nCould not start the review because your revision matches the latest version of this page.\\n\\nAfter saving the page no reflist is appearing on the page\\nAn error is appearing on the read mode:\\n\\n\\n\\nCite error: There are <ref> tags on this page, but the references will not show without a {{Reflist}} template or a <references /> tag; see the help page. ().\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397675583, 'spacePHID': None, 'dateCreated': 1397673360, 'dateModified': 1443276218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot call method 'isCollapsed' of null appearing and cannot create a new page in Betalabs\", 'description': {'raw': \"While trying to edit a new page the following error appears in the console:\\nUncaught TypeError: Cannot call method 'isCollapsed' of null\\n\\nAlso there is no toolbar appearing over the page\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63945\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397603371, 'spacePHID': None, 'dateCreated': 1397585820, 'dateModified': 1443276221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63954', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf1] Selection in Firefox can get to 0,0 which then breaks horribly', 'description': {'raw': 'seen on beta labs as of 15 April in Firefox not in Chrome\\n\\non a page that begins with text such as \"two words\" open VE and click link without clicking any other item in the page\\n\\ninsert a link such as \"http://www.example.com\"\\n\\nin Chrome this correctly creates a link like \\n\\n\\t\\n[http://www.example.com two] words\\n\\n\\nbut in Firefox we get incorrectly instead \\n\\n\\t\\nhttp://www.example.com \\t\\n  \\t\\ntwo words\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397680015, 'spacePHID': None, 'dateCreated': 1397573220, 'dateModified': 1606253500, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63943', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Faulty wmf21 OOjs UI deploy -> Exception on load \"Uncaught TypeError: Object #<Object> has no method \\'lookup\\'\"', 'description': {'raw': \"After wmf21 deployment cannot load VE on en.wiki.GEtting the following error:\\n\\nUncaught TypeError: Object #<Object> has no method 'lookup' VM734:1505\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397169111, 'spacePHID': None, 'dateCreated': 1397166240, 'dateModified': 1449787238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63791', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] Cannot add a new category in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Page options>Categories section\\n3.Type in a category name which does not already exist\\n\\nObserved Result:\\nThe new category does not get added \\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63544\\n\\n**Attached**: {F13724}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396911172, 'spacePHID': None, 'dateCreated': 1396643100, 'dateModified': 1443276233, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63547', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] Cannot select the first match in the transclusion selection dialog box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Template\\n3.Search for a template by typing in something on the search box for example: Cite\\n4.When the matching transclusion names appear in the list try to select the first name\\n\\nObserved Result:\\n\\nThe first match does not get selected .\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63547\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63554\\n\\n**Attached**: {F13706}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396911205, 'spacePHID': None, 'dateCreated': 1396638000, 'dateModified': 1443276233, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63544', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf20] Adding a space after a formatted link throws error Uncaught TypeError: Cannot read property 'constructor' of undefined\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Add a link\\n2.Apply format on it like Bold/Strikethrough\\n3.Now add a space right after that and add a text\\n\\n\\nObserved Result:\\nAn error appears in the console  Uncaught TypeError: Cannot read property 'constructor' of undefined and the text gets added in a weird way: One letter appears before the link and some letters gets typed inside the link text\\n\\nSee the screenshot attached\\n\\n\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/31stMarChrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13199}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396915834, 'spacePHID': None, 'dateCreated': 1396304520, 'dateModified': 1443276235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63333', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Unbalanced set of replace operations found\" when deleting table cells', 'description': {'raw': 'Screencast\\n\\nIf I select a few cells in a table at\\nhttps://pt.wikipedia.org/wiki/Quadrado_perfeito?oldid=38495158&veaction=edit\\nand then press DELETE, I get the error \"Unbalanced set of replace operations found\".\\n\\nSee the screencast.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13276}'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415883023, 'spacePHID': None, 'dateCreated': 1395835140, 'dateModified': 1418273595, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63103', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf20] Cannot save a page after undoing inserting reference on it', 'description': {'raw': 'screenshot\\n\\nThere are wide varieties of type errors I get for undoing typing references in different way.I will try to document each cases in this same bug report:\\n\\n\\nCase 1:\\n\\nSteps to reproduce:\\n\\n1.Insert a reference with text for example : reference[1]\\n2.Press \"Undo\"\\n\\nError 1:\\nUncaught TypeError: Cannot read property \\'length\\' of undefined \\n\\n3.Place the cursor at the end of the text\\n\\nError 2:\\nUncaught Error: ve.dm.Document.getNodeFromOffset(): offset 12 is out of bounds \\n\\n\\nCase 2:\\n\\n1.Insert two references with text , for example:\\nreference [1]\\nreference [2]\\n\\n2.Now keep on pressing Undo untill the page gets empty\\n\\nErrors:\\nUncaught TypeError: Cannot read property \\'length\\' of undefined VM484:296\\nUncaught Error: Offset could not be translated to a DOM element and offset: 12 VM484:447\\nUncaught Error: Invalid end offset: 21 VM484:252\\nUncaught Error: Unbalanced input passed to document \\n\\nIn both cases, after the Undo action , clicking on \"Save Page\" does not do anything.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13217}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395781781, 'spacePHID': None, 'dateCreated': 1395775560, 'dateModified': 1443276242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63085', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf20] Mobile VE fails to appear in beta labs due to generateCitationFeatures() exploding when citation code isn't loaded\", 'description': {'raw': 'On http://en.m.wikipedia.beta.wmflabs.org/\\n\\nLog in to edit\\nSettings to alpha to get VisualEditor\\nAttempt to edit any page\\n\\nA spinner appears and spins forever.  The VE UI never appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395773498, 'spacePHID': None, 'dateCreated': 1395761400, 'dateModified': 1417049200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63074', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf19] Media Settings icon is not clickable since it got overlayed by image highlight box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add an image\\n3.Select the image\\n\\nObserved Result:\\nThe media settings icon is getting hidden by the  Image highlight box and hence not clickable\\n\\nSee the screenshot attached,\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Slug?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n\\n**Attached**: {F12847}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394831715, 'spacePHID': None, 'dateCreated': 1394829300, 'dateModified': 1417048878, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62659', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf18] Cannot read property 'saveDialogSave' of undefined appearing when saving a page\", 'description': {'raw': \"I am getting this error while trying to save a page on betalabs:\\nUncaught TypeError: Cannot read property 'saveDialogSave' of undefined\\n\\nHowever, if you cancel the dialog box and reload again, it shows that the new content actually got saved\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394489589, 'spacePHID': None, 'dateCreated': 1394480520, 'dateModified': 1443276258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62508', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf16] Unrelated edit removes \"upright\" parameter from images', 'description': {'raw': 'Verified in the linked URL (I\\'m using Chrome, Win7, Vector), all I did was adding a few words at the top. I\\'ll add that the edit did trigger the \"corrupted edit, please check\" warning, but I didn\\'t verify what that caught, since the article is very large.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**URL**: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=598527246&oldid=598527036\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53853'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394223314, 'spacePHID': None, 'dateCreated': 1394185740, 'dateModified': 1443276258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62366', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection appearing in en.wiki\", 'description': {'raw': \"Screenshot\\n\\nTried to load VE in en.wiki getting the following error in the console and the label of insert button is missing:\\n\\nUncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'restoreEditSection\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13187}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393015148, 'spacePHID': None, 'dateCreated': 1393007340, 'dateModified': 1443276278, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61759', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In alpha mode/beta labs, attempting to edit (using VE) results in only a spinner', 'description': {'raw': \"Seen on for example  http://en.m.wikipedia.beta.wmflabs.org/wiki/Selenium_Edit_Test \\n\\nAs logged-in user with 'alpha' mode set, attempt to edit a page on beta labs. \\n\\nVE never appears, Mobile user sees only a spinner. \\n\\nVE seems to work correctly for non-Mobile user.  \\n\\n(Possibly related may be a recent change to Parsoid on beta labs https://bugzilla.wikimedia.org/show_bug.cgi?id=60694)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391732958, 'spacePHID': None, 'dateCreated': 1391631060, 'dateModified': 1443276297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60912', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot Save any page on Betalabs:\"TypeError: this.toolbar is null\" appears', 'description': {'raw': 'Screenshot\\n\\nI cannot save any page on Betalabs with FireFox and Chrome.It shows an error Unknown error on the dialog box and in the console it shows:\\nTypeError: this.toolbar is null\\n\\nFor Chrome, it shows:\\nGET http://bits.beta.wmflabs.org/static-master/extensions/VectorBeta/less/images/unwatch-icon.svg 404 (Not Found) \\n\\nAlso ,Edit button is not loading VE sometimes.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13034}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391121486, 'spacePHID': None, 'dateCreated': 1391108340, 'dateModified': 1417570689, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60631', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Trying to open gallery inspector when an image or reference is selected causes JS error', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Select an image\\n3.Go to Insert>Gallery\\n\\nObserved Result:\\nAn error appears in the console \"Uncaught TypeError: Cannot read property \\'body\\' of undefined\"\\n\\nAfter that the Media Settings option does not appear on any other image .Also the reference dialog option does not show up when you select a reference note.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391487316, 'spacePHID': None, 'dateCreated': 1390861980, 'dateModified': 1443276303, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60502', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The Page suggestions are not appearing in the link inspector while creating link on Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Select a Text and press command+k\\n\\nObserved Result:\\nObserve that no page suggestions are appearing on the link inspector regardless of whether it is a new page or an existing page.\\n\\n\\nSee the screenshot attached.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13086}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390862075, 'spacePHID': None, 'dateCreated': 1390502760, 'dateModified': 1443276307, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60374', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot save a page after adding gallery to a page', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a gallery from Insert>Gallery or just simply close the inspector without adding anything.\\n3.Click on the \"Save Page\" button\\n\\nObserved Result:\\n\\nThe page cannot be saved.\\n\\nAn error appears in the console:\\nUncaught Error: InvalidCharacterError: DOM Exception 5\\n\\nSee the screenshot attached.\\n\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/w/index.php?title=Thedomtest&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12917}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391487323, 'spacePHID': None, 'dateCreated': 1390339800, 'dateModified': 1443276307, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60307', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying references is completely broken', 'description': {'raw': 'Comment to follow from Roan.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390936578, 'spacePHID': None, 'dateCreated': 1389836760, 'dateModified': 1443276310, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60117', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Content format needed for faux request now that content format is validated -> VE down in wmf10', 'description': {'raw': 'Attempt to invoke VE by clicking the Edit button on my near-empty user page http://en.wikipedia.beta.wmflabs.org/wiki/User:Cmcmahon, get error: \\n\\nError loading data from server: internal_api_error_ErrorPageError: Exception Caught: &lt;editpage-notsupportedcontentformat-text&gt;. Would you like to retry?\\n\\nNote: several hours ago a number of automated browser tests failed by timing out waiting for 10 seconds for the diff viewer to manifest in the browser.  There may have been a performance problem before this error appeared.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389371498, 'spacePHID': None, 'dateCreated': 1389282300, 'dateModified': 1443276313, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59867', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting copied template cause it to be inserted twice, once broken (span tag, data-ve-ignore)', 'description': {'raw': 'https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=63377772&oldid=63377716\\n\\nI added the Citazione Necessaria template to my sandbox,\\nand added some text to its only parameter.\\n\\nAs a result I get an additional superscripted \"Citazione necessaria\" which is broken:\\n<sup data-ve-ignore=\"true\" class=\"noprint\"><span title=\"Il testo selezionato deve essere comprovato da una fonte affidabile. Modifica la pagina per aggiungere fonti.\" style=\"color:red;\">[\\'\\'<a href=\"/wiki/Wikipedia:Uso_delle_fonti\" title=\"Wikipedia:Uso delle fonti\">senza fonte</a>\\'\\']</span></sup>\\n\\n(Not sure if bug 59154/bug 55855 are related.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390322597, 'spacePHID': None, 'dateCreated': 1388857800, 'dateModified': 1443276317, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59653', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'SVG icons embedded in stylesheets broken in Wikimedia production due to mime-type confusion', 'description': {'raw': 'Screenshot of problem in production.\\n\\nAs of recently, we have SVG versions of the external link icons in MediaWiki. These are embedded as base64 encoded data uris by CSSMin in ResourceLoader.\\n\\nLocally, these are working fine for me. Comes out as:\\n\\n background-image: linear-gradient(transparent,transparent),url(data:image/svg+xml;base64,PD...\\n\\nIn production, however, they are broken.\\nE.g.: https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet#Links\\n\\n background-image: linear-gradient(transparent,transparent),url(data:application/xml;base64,PD...\\n\\nI can consistently reproduce this in Chrome (latest stable). I eliminated other causes by verifying that it breaks locally if I change the mime type in the CSS manually, and visa versa by changing it to image/svg+xml in the browser console when looking at production.\\n\\n\\nNot sure if this supposed to work according to the spec, but fact is, Chrome (maybe other browsers as well) does not accept application/xml in data uris for background images.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: major\\n\\n**Attached**: {F12090}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388755125, 'spacePHID': None, 'dateCreated': 1388754600, 'dateModified': 1454003843, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59249', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'CSSMin: Embedded SVG icons are broken in Wikimedia production due to bad mime type', 'description': {'raw': 'On MediaWiki.org (1.23wmf9), MW thinks that the appropriate MIME type for SVGs embedded in CSS as data: URIs is application/xml instead of image/svg+xml, causing them not to show up in any browser. It works for me locally.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: major\\n**URL**: https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet#Links'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389052804, 'spacePHID': None, 'dateCreated': 1388703960, 'dateModified': 1612330025, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59234', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Broken on mobile due to ULS dependency', 'description': {'raw': \"When loaded in alpha on beta labs I get \\nError: Unknown dependency: jquery.uls Error {} \\n\\nGiven this is the second dependency related error I've now seen I'm a bit concerned about the speed at which dependencies are added to the mobile version of VisualEditor. Is there a way to better sandbox the mobile code? I find it hard to believe that ULS is actually needed for the stripped down mobile version.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387418441, 'spacePHID': None, 'dateCreated': 1387229700, 'dateModified': 1417049206, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58551', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Internal Server Error 500 appears while saving any page on Betalabs', 'description': {'raw': 'http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Something&veaction=edit\\n\\nThe error is :\\nailed to load resource: the server responded with a status of 500 (Internal Server Error) http://en.wikipedia.beta.wmflabs.org/w/api.php\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-oetk6bbl6omm354ejz3b', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386265469, 'spacePHID': None, 'dateCreated': 1386196320, 'dateModified': 1386265469, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58008', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] \"Switch to source editing\" dies', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on Switch to source editing from the down menu for an article on betalabs\\n\\nObserved Result:\\nNothing happens.It does not switch to source editing from VE\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386110720, 'spacePHID': None, 'dateCreated': 1386101520, 'dateModified': 1417049205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57947', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'beta: Parsoid is returning the wrong articles', 'description': {'raw': '- go to any article\\n- edit it with visual editor\\n- instead of text of the article in visual editor, text of another article appears\\n\\n- reproducible for every article I have tried at http://en.wikipedia.beta.wmflabs.org/\\n- not reproducible at http://test2.wikipedia.org/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57233'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386108793, 'spacePHID': None, 'dateCreated': 1386082320, 'dateModified': 1454003847, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57926', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Cannot Save a page after adding an image/template/link in the article in beta', 'description': {'raw': 'Screenshot attached\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button\\n2.Add any image/template/link in the article\\n3.Click the \"Save Page\" button\\n\\nObserved Result:\\nCannot Save the Article.\\n\\nThe following error is found in the developers tool:\\n\\nUncaught TypeError: Object #<VeDmInternalItemNode> has no method \\'isCollapsed\\'\\nve.dm.Transaction.newFromRemoval\\nve.ui.MWReferenceDialog.teardown\\nOO.ui.Window.close\\n(anonymous function)\\nproxy load.php:10\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker\\n\\n**Attached**: {F12504}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386012532, 'spacePHID': None, 'dateCreated': 1385855220, 'dateModified': 1417049207, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57785', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference is not getting added; cannot save a page after adding an image/template/link in the article in Beta', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit page\\n2.Select a text or place the cursor at the end of any text\\n3.Click on More>Reference\\n4.Click on Insert reference\\n5.Click on Save Page\\n\\nObserved Result:\\nNo reference is getting added in the article.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388769354, 'spacePHID': None, 'dateCreated': 1385585280, 'dateModified': 1417049205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57683', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspectors fail to appear at all in Firefox', 'description': {'raw': 'Seen in Firefox on beta labs as of Nov 25 (Chrome behaves correctly):\\n\\nLogin and navigate to some page with text, e.g. as Selenium_user/User:Selenium_user\\n\\nWithout touching anything on the page, click the \"Link\" icon in the menu bar. \\n\\nExpected:  First word in the page is highlighted and link UI appears, referring to highlighted text. \\n\\nActual:  Link icon shows being pressed, but no link UI appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386019466, 'spacePHID': None, 'dateCreated': 1385424900, 'dateModified': 1417049206, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57568', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"MassMessage thinks namespaces that don't exist on the submission site are NS_MAIN\", 'description': {'raw': 'As discovered today with the Wikidata weekly summaries run, MassMessage ignores the namespace if it is a interwiki link.\\n\\nExample; {{#target:Wikidata:Status updates|www.wikidata.org}}\\n\\nThe message gets delivered to https://wikidata.org/wiki/Status_updates which then errors due to it being in NS_MAIN and not NS_PROJECT which was specified.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58524'}, 'authorPHID': 'PHID-USER-4n6zx4s5v23pjdztvtnr', 'ownerPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389298817, 'spacePHID': None, 'dateCreated': 1385166000, 'dateModified': 1430340095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57464', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] The list of reusable references does not provide any details except for reference number', 'description': {'raw': 'Try to reuse a reference in VE in an article featuring references.\\n\\nAll you get is the list of number in brackets, which are the numbers of the references, and nothing else.\\n\\n(Actually, if you test it in https://en.wikipedia.org/wiki/Alex_Timbers?veaction=edit , you will notice that it does provide the \"ref name\" for the first reference; but that\\'s it).\\n\\nIt seems it does not matter which OS, browser or skin you are using.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://commons.wikimedia.org/wiki/File:VisualEditor_ref_dialog_box_showing_numbers_and_ref_names.png'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391625632, 'spacePHID': None, 'dateCreated': 1384810020, 'dateModified': 1443276340, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57209', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Categories are showing up in wikitext format in the view mode of a page', 'description': {'raw': 'Categories\\n\\nSteps to reproduce:\\n\\n-Click on the Edit button of a page\\n-Click on the Page Settings button\\n-Add some category to this page\\n-Click on \"Apply Changes\"\\n-Click on the \"Save Page\"\\n\\nObserved Result:\\nThe categories appear in wiki text format in the view mode of the page.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12703}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383702017, 'spacePHID': None, 'dateCreated': 1383611400, 'dateModified': 1417049209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56595', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid web service breaks text encoding on all edits made with VisualEditor to pages with non-ASCII characters', 'description': {'raw': 'VE is breaking text encoding on *all* edits on fr.wp. Looks like UTF-8 is being intepreted as ISO-8859-2 or something.\\n\\nExample edits:\\nhttps://fr.wikipedia.org/w/index.php?title=Tulle&curid=51555&diff=98030422&oldid=98028576\\nhttps://fr.wikipedia.org/w/index.php?title=Herv%C3%A9_Jolly&diff=prev&oldid=98030048\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383599438, 'spacePHID': None, 'dateCreated': 1383596160, 'dateModified': 1454003853, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56583', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] \"More\" menu gets shorter (to -1px) when page scrolls after focus-loss close in Firefox', 'description': {'raw': \"Tested on both the Italian and the English Wikipedia;\\nReach the bottom of any page: the style drop down menu does not open (it does when you're at the top of the page); the link inspector does not present the list of options.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55465\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381281033, 'spacePHID': None, 'dateCreated': 1380976920, 'dateModified': 1417049209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55343', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editor does not load at all (ve.ui.TargetToolbar is undefined)', 'description': {'raw': 'load.php request for ve.base (when it crashes)\\n\\nAt this time, on most Wikipedias that have just been switched to 1.22wmf19, VisualEditor is fatally broken.\\n\\nIt cannot be consistently reproduced, but trying 3 or 4 times will hit the exception.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51766\\n\\n**Attached**: {F12689}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380839704, 'spacePHID': None, 'dateCreated': 1380831300, 'dateModified': 1417049210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54935', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Page settings dialog broken in Chrome (Uncaught TypeError: scrollTop of undefined)', 'description': {'raw': 'Splitting from bug 54322.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380843220, 'spacePHID': None, 'dateCreated': 1380823320, 'dateModified': 1417297777, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54928', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing at top of page shows pawn/slug character', 'description': {'raw': 'pawn character editing\\n\\nseen on master branch (beta labs) as of 30 September. \\n\\nopen 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}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380559585, 'spacePHID': None, 'dateCreated': 1380558180, 'dateModified': 1417048885, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54791', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Don't release any new VE updates for three months\", 'description': {'raw': '**Author:** `Wikifram`\\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. \\n\\nMultiplying 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. \\n\\nNo 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380394985, 'spacePHID': None, 'dateCreated': 1380383040, 'dateModified': 1380707473, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54737', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Snowmen appear near newly added references', 'description': {'raw': 'See last line of this diff: https://fr.wikipedia.org/w/index.php?title=T%C3%A9l%C3%A9com_SudParis&diff=next&oldid=97023702 .\\n\\nSteps to reproduce, as provided by user: Seudo.\\n\\n1) Go to https://fr.wikipedia.org/wiki/Cumul_des_mandats_en_France - 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.\"\\n6) 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.\\nSuedo adds that in his console Web he also got a Javascript error, TypeError: group.firstNodes[index2] is undefined (load.php:54) .\\n\\nI 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.\\n\\nMy edits in the sandbox could not reproduce the issue but generated https://bugzilla.wikimedia.org/show_bug.cgi?id=54341 instead.\\n\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54976'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406341511, 'spacePHID': None, 'dateCreated': 1380298800, 'dateModified': 1417048871, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54712', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed', 'description': {'raw': \"For example, you can't copy/paste in the edit summary box.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379977964, 'spacePHID': None, 'dateCreated': 1379680980, 'dateModified': 1417048886, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54375', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Unnamed references get their names corrupted', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Matt_Chandler_%28pastor%29&curid=37214846&diff=573675359&oldid=571858677\\n\\nFor some reason, multiple different unnamed references all get name=\":3\" there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54445'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379977955, 'spacePHID': None, 'dateCreated': 1379613840, 'dateModified': 1417049210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54341', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Corruption with circumflexes', 'description': {'raw': 'VisualEditor seems to take particular pleasure in abusing circumflexes.\\n\\nIssue 1: VE duplicates the first character entered after a circumflexed letter at the end of a line.\\n\\n* Steps to reproduce: In VE, enter the text êtt (actually enter the characters individually, don\\'t copy/paste) at the end of a line.\\n* Expected result: \"êtt\" is entered.\\n* Actual result: \"êtt<newline>t\" is entered.\\n\\nIssue 2: At the beginning of a line, VE turns a circumflexed letter into a pawn character when removing text entered after the circumflexed letter.\\n\\n* Steps to reproduce: In VE, enter the text êtt at the beginning of a line, then delete the last \\'t\\'.\\n* 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378959962, 'spacePHID': None, 'dateCreated': 1378943700, 'dateModified': 1417048670, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54047', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor breaks when Polish-language diacritics (ążśźęćńół) are input', 'description': {'raw': '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.\\n\\nThey\\'re all input using AltGr (right Alt) + diacritic-less version of the characters, with the exception of \"x\" mapping to \"ź\" (so, respectively, azsxecnol).\\n\\nI have been unable to replicate the issue myself, but it\\'s definitely happening.\\n\\npl.wp thread: https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#VisualEditor_a_polskie_diakrytyki\\n\\nThis is repeatedly breaking page text on the Polish Wikipedia, so I\\'m marking the bug \"highest critical\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**URL**: https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#VisualEditor_a_polskie_diakrytyki\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53680'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378958511, 'spacePHID': None, 'dateCreated': 1378296540, 'dateModified': 1417048669, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53747', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: annotating or linking newly added text containing accented or non-Latin characters causes corruption and pawns', 'description': {'raw': \"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.\\n\\nThis happens everywhere on a page including body text, tables and image captions.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53747\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378958522, 'spacePHID': None, 'dateCreated': 1378127940, 'dateModified': 1417048886, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53680', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Annotated text after a template is deleted', 'description': {'raw': '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.\\n\\nTo reproduce:\\n1. Open any page in VE.\\n2. 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.\\n\\nExamples: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox2&diff=570195482&oldid=570194023\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378222889, 'spacePHID': None, 'dateCreated': 1377477420, 'dateModified': 1378223041, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53334', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Link inspector prevents insertion of section links', 'description': {'raw': 'VE 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.\\n\\nI\\'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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n\\n**Attached**: {F11887}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392231560, 'spacePHID': None, 'dateCreated': 1377188700, 'dateModified': 1452888469, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53219', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template gets removed without editing it', 'description': {'raw': 'Steps to reproduce:\\n1. Go to http://en.wikipedia.org/wiki/Post_and_core\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-mapumhlp3gw5qefhvafn', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379348384, 'spacePHID': None, 'dateCreated': 1375867440, 'dateModified': 1417049208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52608', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix violation of PHP strict standard (\"Only variables should be passed by reference in VisualEditor/ApiVisualEditor.php on line 255\")', 'description': {'raw': '[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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ppvnwr24o32pux3le5ov', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375469052, 'spacePHID': None, 'dateCreated': 1375462680, 'dateModified': 1417049211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52466', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: autocomplete for wikilinks \"aggressively\" chooses what to link', 'description': {'raw': '<<When I was trying to add a link to Classic XI, (didn\\'t know it didn\\'t exist) it repeatedly took the word \"Classic\" and continually tried to make the link go to Classical music. [...] --buffbills7701 19:42, 1 August 2013 (UTC)>>\\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.\\nThanks!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375408346, 'spacePHID': None, 'dateCreated': 1375391400, 'dateModified': 1417049207, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52420', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor.php attempts to register a hook handler that was removed', 'description': {'raw': 'VisualEditor.php attempts to register a hook handler that was removed (summary credit goes to Ori)\\n\\nstack: http://paste.tstarling.com/p/GuTJEM.html\\n\\nTim says:\\n\\n> var_dump($wgHooks[\\'BeforeWelcomeCreation\\']);\\narray(2) {\\n  [0]=>\\n  string(42) \"VisualEditorHooks::onBeforeWelcomeCreation\"\\n  [1]=>\\n  string(44) \"GettingStartedHooks::onBeforeWelcomeCreation\"\\n}\\n\\n> print is_callable($wgHooks[\\'BeforeWelcomeCreation\\'][0]);\\n\\n> print is_callable($wgHooks[\\'BeforeWelcomeCreation\\'][1]);\\n1\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-7ey733eainlhx5xqp4d3', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375332474, 'spacePHID': None, 'dateCreated': 1375331160, 'dateModified': 1417049212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52368', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Save dialog sometimes attaches to context menu toolbar instead of platform toolbar', 'description': {'raw': 'Screenshot\\n\\nSince the VE update tonight the save dialog is half out of the screen on FF 23/Win7, but sometimes only.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52326\\n\\n**Attached**: {F11781}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375312939, 'spacePHID': None, 'dateCreated': 1375261620, 'dateModified': 1417049212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52317', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Anonymous users getting VisualEditor on German Wikipedia and making edits', 'description': {'raw': 'https://de.wikipedia.org/w/index.php?title=Spezial:Letzte_%C3%84nderungen&limit=500&days=30&hideliu=1&tagfilter=visualeditor\\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.\\n\\nMy 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52202'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375124710, 'spacePHID': None, 'dateCreated': 1375120080, 'dateModified': 1375156109, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52232', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Change to opt-in for registered users, postpone activation for IPs on the German Wikipedia', 'description': {'raw': '**Author:** `matthiasbecker1967`\\n\\n**Description:**\\nAccording 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\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49998\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52232'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375122779, 'spacePHID': None, 'dateCreated': 1375049820, 'dateModified': 1443024253, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52202', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: A <nowiki> on page causes \"Uncaught RangeError: Maximum call stack size exceeded\" in oojs.compare', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375139113, 'spacePHID': None, 'dateCreated': 1374661020, 'dateModified': 1417049211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51948', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Newly-added references need a page save before being reusable', 'description': {'raw': \"Apologies if this is a duplicate; I haven't found a report about this.\\n\\nIf 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377889823, 'spacePHID': None, 'dateCreated': 1374250680, 'dateModified': 1432297031, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51689', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Refactor references dialog to allow immediate insertion of reference content', 'description': {'raw': '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).\\n\\nWe 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.\\n\\n(Per discussion w/ James)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374646985, 'spacePHID': None, 'dateCreated': 1373508480, 'dateModified': 1417049212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51152', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Preserve unmodified data-mw attributes to avoid corrupting templates' whitespace\", 'description': {'raw': 'data-mw.i seems to be dropped on edit in latest VE, which causes a loss of round-trip information for spaces etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374636985, 'spacePHID': None, 'dateCreated': 1373505480, 'dateModified': 1428510510, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51150', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor/Parsoid: Beta release to en.wp IP users - blocking issues (tracking)', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373916884, 'spacePHID': None, 'dateCreated': 1373067660, 'dateModified': 1545563326, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50848', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Implement a better version of enwiki's reference pop-up for very easy reference inserting\", 'description': {'raw': '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.\\n\\n(Request from En Wikipedia)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://www.mediawiki.org/wiki/VisualEditor/Design/Reference_Dialog\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50110'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395701666, 'spacePHID': None, 'dateCreated': 1372968840, 'dateModified': 1443276394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50768', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)', 'description': {'raw': \"screenshot\\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.\\n\\nObserved on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F11031}\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373053892, 'spacePHID': None, 'dateCreated': 1372931040, 'dateModified': 1417049216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50731', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog sometimes shows items in \"Add parameter\" that are already used', 'description': {'raw': 'Screenshot of problem\\n\\nThis causing:\\n\\n* The label fallback (parameter name + ucfirst) not working.\\n* It is still available from the \"Add parameter\" dropdown.\\n* The user can actually add it again, causing a logic error.\\n\\nI 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.\\n\\nSee 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}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373497407, 'spacePHID': None, 'dateCreated': 1372910460, 'dateModified': 1417049215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50715', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Sometimes not correctly initialized (about 1 in 40-50 pageviews)', 'description': {'raw': '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.\\n\\nChrome/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'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373359485, 'spacePHID': None, 'dateCreated': 1372896120, 'dateModified': 1417049215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50708', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a GuidedTour for first-time VisualEditor users (ones for both newbies for and experienced editors?)', 'description': {'raw': \"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.\\n\\nPart 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.\\n\\n(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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T51820}\\n{T89074}\"}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1442955804, 'spacePHID': None, 'dateCreated': 1372793160, 'dateModified': 1442955804, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50601', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Edit tab points to the oldid not the newid when saving (except for when creating pages)', 'description': {'raw': \"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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50716\"}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373328432, 'spacePHID': None, 'dateCreated': 1372554780, 'dateModified': 1417049215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50441', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Invalid token\" message after period of inactivity leads to lost work', 'description': {'raw': '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. \\n\\nLoss 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. \\n\\nI would classify this as user-hostile behavior.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50402'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373917573, 'spacePHID': None, 'dateCreated': 1372520820, 'dateModified': 1417049213, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50424', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ref warning appears within template that contains references, post-modification', 'description': {'raw': \"Screenshot\\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 <references\\\\>, can't find a tag in the template itself, and freaks the heck out.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51337\\n\\n**Attached**: {F11303}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373852785, 'spacePHID': None, 'dateCreated': 1372515720, 'dateModified': 1417049214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50423', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference toolbar icon missing in wmf9', 'description': {'raw': \"The references list one is still there; did Trevor's change break it?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372442860, 'spacePHID': None, 'dateCreated': 1372404000, 'dateModified': 1417570691, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50349', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: &nbsp;s converted to space characters (32s not 160s) on round-trip', 'description': {'raw': 'http://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FGNoSR&diff=561873747&oldid=561873385\\n\\nRemoves non-breaking space.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373056593, 'spacePHID': None, 'dateCreated': 1372385580, 'dateModified': 1417570690, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50339', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'load.php error?  many symptoms...', 'description': {'raw': 'Log 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'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372325082, 'spacePHID': None, 'dateCreated': 1372290900, 'dateModified': 1372325082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50264', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Silent clean-up of untouched references and templates', 'description': {'raw': \"I made a grammar fix (one word), and did not check the differences before saving. Mistake! :) \\n\\nhttp://en.wikipedia.org/w/index.php?title=Abdullah_of_Saudi_Arabia&diff=prev&oldid=561571041\\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). \\n\\nNo recommended fix, exactly, but perhaps something to consider.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-kqwh3rvfxxh3wfsft7mu', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372294327, 'spacePHID': None, 'dateCreated': 1372281720, 'dateModified': 1417570692, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50259', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Be able to have enabled for all logged-in users but not anonymous users', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372726673, 'spacePHID': None, 'dateCreated': 1372267200, 'dateModified': 1417570690, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50246', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dialogs, inspector menu, link inspector etc. appear behind the document in Monobook', 'description': {'raw': 'Screenshot\\n\\nSee screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11809}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372340043, 'spacePHID': None, 'dateCreated': 1372263180, 'dateModified': 1417049217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50241', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Resize hover phantom has too high a z-index, so users are unable to click on the image inspector menu', 'description': {'raw': 'Screenshot\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F11665}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372379698, 'spacePHID': None, 'dateCreated': 1372146600, 'dateModified': 1417048891, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50159', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector creates the text twice if not running on a selection', 'description': {'raw': '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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372264523, 'spacePHID': None, 'dateCreated': 1372115280, 'dateModified': 1417570693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50140', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusions not properly round-tripped', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/wiki/Chloroplast?veaction=edit\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50070'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372708719, 'spacePHID': None, 'dateCreated': 1372106580, 'dateModified': 1417570690, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50129', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Categories/default sort sometimes duplicated to random position in DOM after edit', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Dina_bint_%27Abdu%27l-Hamid&diff=561398396&oldid=561397974\\n\\nI added a single letter (\"therafter\" --> \"thereafter\"). VisualEditor duplicated the categories and the default sort.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50385\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50332\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54169'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373500285, 'spacePHID': None, 'dateCreated': 1372100100, 'dateModified': 1437781492, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50120', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link editor does not work in the reference editor in Firefox', 'description': {'raw': 'Self-explanatory; Firefox 21.0, Windows 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372210400, 'spacePHID': None, 'dateCreated': 1372094820, 'dateModified': 1417049208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50115', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide way for local wikis to auto-prompt reference templates', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50768\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395701652, 'spacePHID': None, 'dateCreated': 1372089360, 'dateModified': 1444199692, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50110', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template-based references never editable from reference editor in Firefox', 'description': {'raw': 'Screenshot\\n\\nSee screenshot. Kiiinda worrying - if this is something a group of people > me is seeing it may be a blocker.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://en.wikipedia.org/wiki/Joe_Flacco?veaction=edit\\n\\n**Attached**: {F11445}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372040794, 'spacePHID': None, 'dateCreated': 1372035120, 'dateModified': 1417570693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50073', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: If a sanity check doesn't work out, encourage the user to do a wikitext diff before saving\", 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372387323, 'spacePHID': None, 'dateCreated': 1372029300, 'dateModified': 1417570691, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50067', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Metadata not preserved in references', 'description': {'raw': 'They get stripped out when rendered back to HTML.\\n\\ne.g.\\n\\n<ref>Foo<!--bar--></ref>\\n\\n->\\n\\n<ref>Foo</ref>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372039639, 'spacePHID': None, 'dateCreated': 1372007340, 'dateModified': 1417570693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50059', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inline text style annotations with different attributes should not be merged', 'description': {'raw': 'Moved from #48830.\\n\\nMerlijn van Deen 2013-06-23 11:20:36 UTC\\n----------------------------------------\\nhttps://www.mediawiki.org/w/index.php?title=Git%2FConversion%2Fpywikipedia&diff=714194&oldid=713893\\nThe only real edit is at the bottom.\\n\\nKrinkle 2013-06-23 11:25:31 UTC\\n-------------------------------\\nThis is due to the merging of the 2 <b> tags. Currently it fails compare custom\\nattributes like \"style\" when attempting to merge equal annotation sequences.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48830'}, 'authorPHID': 'PHID-USER-muirnivxp5hzppn2a3z7', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372001636, 'spacePHID': None, 'dateCreated': 1371986880, 'dateModified': 1483063975, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50050', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Opening \"Edit\" tab (and section edit links) with a middle-click / Ctrl-click / Shift-click (new tab/window) disabled somehow', 'description': {'raw': \"This doesn't work; not quite sure why/how. Should be fixed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373053912, 'spacePHID': None, 'dateCreated': 1371859260, 'dateModified': 1417049216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49993', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adjacent link annotations (one of which is from Parsoid, one from VisualEditor) should conjoin', 'description': {'raw': 'Steps 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]]\".\\n\\nActual result:\\nIf you started with \"[[Porcupine]]\", you end up with \"[[porcupine|p]][[Porcupine|orcupine]]\".\\n\\nThis 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50098'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372355114, 'spacePHID': None, 'dateCreated': 1371855300, 'dateModified': 1417570692, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49985', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'mediawiki/extensions.git does not update some extensions', 'description': {'raw': '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. \\n\\nIt 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'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390501982, 'spacePHID': None, 'dateCreated': 1371684540, 'dateModified': 1496862183, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49846', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parsoid ate a reference', 'description': {'raw': '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).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371782480, 'spacePHID': None, 'dateCreated': 1371656400, 'dateModified': 1371782480, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49828', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image insertion does not work', 'description': {'raw': '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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371782583, 'spacePHID': None, 'dateCreated': 1371582180, 'dateModified': 1417570695, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49763', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Page contents replaced 'undefined' (because of an edit conflict?)\", 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=McIntosh_%28apple%29&diff=560394609&oldid=560264020\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372027620, 'spacePHID': None, 'dateCreated': 1371542880, 'dateModified': 1417570694, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49737', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page with a <references /> block and no <ref>s throws fatal error on load', 'description': {'raw': \"Have a page with a <references /> block but no <ref>s and you get:\\n\\n| Uncaught TypeError: Cannot call method 'connect' of null \\n\\nThis is bad.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371479770, 'spacePHID': None, 'dateCreated': 1371431820, 'dateModified': 1417570696, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49668', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: HTML comments are dropped from transclusion calls', 'description': {'raw': '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.\\n\\nHowever, 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49603\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49655'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371511467, 'spacePHID': None, 'dateCreated': 1371265140, 'dateModified': 1417636735, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49608', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Adding a file/media fails with wrong wikicode (Image insertion sets resource='undefined')\", 'description': {'raw': 'Adding a file/media fails with wrong wikicode.\\n\\nThis wikicode is created, see URL:\\n\\n[[undefined|link=https://commons.wikimedia.org/wiki/File:CV.03326.jpg|right|framed|424x275px]]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://test.wikipedia.org/w/index.php?title=User:Raymond/image&diff=174461&oldid=174460'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371682009, 'spacePHID': None, 'dateCreated': 1371244680, 'dateModified': 1417570694, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49596', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: EventLogging gives the same pageViewSessionId for all edits', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371232257, 'spacePHID': None, 'dateCreated': 1371231960, 'dateModified': 1371234407, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49586', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: EventLogging doesn't log user_id so we can't split out user behaviour\", 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371234357, 'spacePHID': None, 'dateCreated': 1371231900, 'dateModified': 1371234402, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49585', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'New deployment of Parsoid leads to HTML insertion - needs deployed code reversion', 'description': {'raw': '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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371235366, 'spacePHID': None, 'dateCreated': 1371213300, 'dateModified': 1454003875, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49577', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: En hard-coded as TemplateData fetch language', 'description': {'raw': 'Should be user interface language.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371134692, 'spacePHID': None, 'dateCreated': 1370893260, 'dateModified': 1417570697, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49403', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Move back to \"normal\" Save dialog with optional rather than mandatory Review', 'description': {'raw': 'This is to restore the pre-December save workflow (Save dialog triggered, with Show Changes within it).\\n\\nThe \"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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370654365, 'spacePHID': None, 'dateCreated': 1370535240, 'dateModified': 1417570697, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49258', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link corruption oddity in production on links (Parsoid issue?)', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://pl.wikipedia.org/w/index.php?title=Ukryta_sie%C4%87&diff=36500666&oldid=36500549\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50720'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372017998, 'spacePHID': None, 'dateCreated': 1369387560, 'dateModified': 1417049214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48769', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox', 'description': {'raw': '1. 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371602123, 'spacePHID': None, 'dateCreated': 1368667200, 'dateModified': 1417048892, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48526', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression] Link inspector button doesn't work\", 'description': {'raw': '1. 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'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368638702, 'spacePHID': None, 'dateCreated': 1368622500, 'dateModified': 1417049208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48509', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn appears when creating new list item in Firefox', 'description': {'raw': '1. Go to a page with a bullet or a numbered list. Edit with VisualEditor.\\n\\n2. 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.\\n\\n3. Type something.\\n\\nEXPECTED\\n\\nYou are typing in the new line.\\n\\n\\nACTUAL 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\".\\n\\nThis happens at least at mediawiki.org with Firefox 22.0a2 (2013-05-07).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371142270, 'spacePHID': None, 'dateCreated': 1368561900, 'dateModified': 1417048892, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48468', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Indenting & unindenting multiple list items fails', 'description': {'raw': 'Problems in IndentationAction that Ed it working on right now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368471149, 'spacePHID': None, 'dateCreated': 1368392940, 'dateModified': 1417570698, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48390', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Lists badly broken again', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368477644, 'spacePHID': None, 'dateCreated': 1368386340, 'dateModified': 1417048882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48386', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Delete contents of slugged paragraph results in double line break visible', 'description': {'raw': \"* 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 <br> has appeared from nowhere:\\n  <p><br><span slug></span></p>\\n\\nAlso this paragraph gets sent to Parsoid resulting in an extra line break.\\n\\nRemoving the text by using undo doesn't result in this bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371781383, 'spacePHID': None, 'dateCreated': 1368384600, 'dateModified': 1417048891, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48385', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing a block level slug causes pawns to be inserted, content corruption', 'description': {'raw': \"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.\\n\\nThe 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.\\n\\nActual character: ♙\\nUnicode value: 2659\\nUTF-8 value: E2 99 99\\nBrowser: Firefox\\n\\n1. https://en.wikipedia.org/wiki/Wikipedia:Miscellany_for_deletion/Wikipedia:Chess_championship\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368498256, 'spacePHID': None, 'dateCreated': 1368250320, 'dateModified': 1417048882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48346', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Aborted empty list creates a pawn', 'description': {'raw': 'Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services\\nPut the cursor somewhere in the text.\\nType \"Enter\" 2 times.\\nType \"Up\".\\nClick Bullet List\\nType Enter\\nType Up\\nType Delete\\n\\nWild pawn appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368206273, 'spacePHID': None, 'dateCreated': 1368089940, 'dateModified': 1417048893, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48287', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Delete on empty first item of list -> pawn in Firefox', 'description': {'raw': 'Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services\\nPut the cursor somewhere in the text.\\nType \"Enter\" 2 times.\\nType \"Up\".\\nType \"Delete\".\\nClick Bullet List\\nType q\\nType Left\\nType Enter\\nType Up\\nType Delete\\n\\nWild pawn appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368211364, 'spacePHID': None, 'dateCreated': 1368089760, 'dateModified': 1417048893, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48286', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve.dm.Converter throws exception when encountering alien from [[en:Enterprise_content_management]]', 'description': {'raw': '1. Open http://en.wikipedia.org/wiki/Enterprise_content_management\\n2. Add a space and remove it\\n3. Press \"Review and Save\"\\n4. Wait forever.\\n\\nThe text stays greyed out and nothing changes. Changes can\\'t be saved.\\nSame for any article I tried.\\n\\nUbuntu 2012.10, Firefox 20.0\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368023940, 'spacePHID': None, 'dateCreated': 1367893860, 'dateModified': 1417570700, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48193', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Indenting multiple list items now broken in Firefox', 'description': {'raw': 'Multiple list items don\\'t indent properly.\\n\\nSteps to duplicate the bug:\\n\\nWrite a couple of lines. Mark all the lines and click the \"list\" button - producing bullet-list. \\n\\nIf the indent button is clicked when the cursor is on a single list item, that item will be indented. However, if you mark a couple of list items and indent them at once, the indentation is jumbled: some of the items are indented and some double-indented (and the item above the selection seems to be indented as well)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368465449, 'spacePHID': None, 'dateCreated': 1367650560, 'dateModified': 1417048893, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48069', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting text and hitting Function keys, PageUp/Down, End/Insert deletes the selected text in Firefox', 'description': {'raw': '*that* was an amusing bug to find.\\n\\nTested on mediawiki.org.\\n\\nSteps:\\n\\n1. Write text in an ordered list item\\n2. Select some of the text\\n3. Hit \"end\"\\n\\nExpected:\\n\\nCursor at end of line\\n\\nActual:\\n\\nCursor at end of line, text gone\\n\\nI would *suspect* this is an easy bug, unmark it if it\\'s not.\\n\\nFound bug on Firefox 23 alpha 1\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368221665, 'spacePHID': None, 'dateCreated': 1367530560, 'dateModified': 1417048882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48022', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE sometimes posting to the wrong API when serializing wikitext?', 'description': {'raw': 'See Parsoid bug 47998.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368216302, 'spacePHID': None, 'dateCreated': 1367509980, 'dateModified': 1417570699, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48006', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: JSON.stringify won't work if data contains DOM elements\", 'description': {'raw': 'Steps to reproduce problem:\\n1. Edit https://www.mediawiki.org/wiki/Git/Commit_message_guidelines in VisualEditor\\n2. Add some text\\n3. \"Review and save\"\\n4. \"Something is wrong\"\\n5. \"Report problem\"\\n\\nExpected behaviour:\\nMake an http request somewhere and report back in the UI.\\n\\nActual behaviour:\\nNo http request is made and UI is unresponsive.\\n\\nconsole:\\n> Uncaught TypeError: Converting circular structure to JSON\\n> at:\\n> > mw.Target.prototype.reportProblem = function(message) {\\n> > var ...., report = { title: .., oldid: .., .. };\\n> > $.post(mw.config.get(\\'wgVisualEditorConfig\\').reportProblemURL, {\\'data\\': JSON.stringify(report)}, function() {\\n\\ndebug:\\n\\nvar objs = [];\\nJSON.stringify(a, function (k, v) {\\n  var i;\\n  if (v === Object(v)) {\\n    i = objs.indexOf(v);\\n    if (i !== -1) {\\n      console.log(\\'dupe at #\\' + i, v);\\n    }\\n    objs.push(v);\\n  }\\n  return v;\\n});\\ndupe at #66 \\n<p data-parsoid=\\u200b\"{\"dsr\":\\u200b[0,139,0,0]\\u200b}\\u200b\">\\u200b\\n\"The \"\\n<b data-parsoid=\\u200b\"{\"tsr\":\\u200b[4,7]\\u200b,\"dsr\":\\u200b[4,24,3,3]\\u200b}\\u200b\">\\u200bcommit message\\u200b</b>\\u200b\\n\" play an important role in revision control systems. They are the first thing other people will see of your commit.\"\\n</p>\\u200b\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368038305, 'spacePHID': None, 'dateCreated': 1367434260, 'dateModified': 1417570700, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47948', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Message <anoneditwarning> should be displayed for anonymous users in the alerts box', 'description': {'raw': \"Currently we don't alert users that they're outing their IP when they save. This is a Bad Thing(tm).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367602898, 'spacePHID': None, 'dateCreated': 1367266320, 'dateModified': 1417570698, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47842', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing lists results in PILE_OF_POO symbol ;)', 'description': {'raw': '1. Edit a page with an unordered list.\\n\\n2. Delete all the text on the last line.\\n\\n3. Press the <delete key>. The bullet should be erased.  Instead, it will\\nremain and the cursor will move to the end of the previous line.\\n\\n4. down-arrow\\n\\n5. down-arrow off of the empty line.\\n\\nTurd appears in the empty line.\\n\\nVery many arrow-key actions will produce the turd.\\n\\nFirefox 20.0, linux.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367281446, 'spacePHID': None, 'dateCreated': 1367217060, 'dateModified': 1368720759, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47817', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest', 'description': {'raw': \"jQuery have WONTFIX'ed this bug (13821) so we'll have to work around.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttp://bugs.jquery.com/ticket/13821\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367097148, 'spacePHID': None, 'dateCreated': 1366992360, 'dateModified': 1417570782, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47737', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Saved annotated content cannot be unannotated', 'description': {'raw': 'This has reappeared (in live on hewiki and others) - if the page on load has bold annotation on some text, pressing the \"bold\" button doesn\\'t remove bold but adds a second bold annotation (which can be removed, but not in a way that stops the text being bold).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366937647, 'spacePHID': None, 'dateCreated': 1366932000, 'dateModified': 1417570782, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47680', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector crashes when trying to annotate first character in the document', 'description': {'raw': \"Make a selection that includes the first character, and press the access key for creating a link (Ctrl+K?). You'll get a JS error.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368208438, 'spacePHID': None, 'dateCreated': 1366853220, 'dateModified': 1417570699, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47623', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: No oldid is sent on POST to Parsoid', 'description': {'raw': \"As the title says. The bug seems to be in postHTML:\\n\\narray(\\n        'postData' => array( 'content' => $html ),\\n        'timeout' => $wgVisualEditorParsoidTimeout,\\n        'oldid' => $parserParams['oldid']\\n)\\n\\n\\nshould be:\\n\\narray(\\n        'postData' => array( 'content' => $html, \\n                             'oldid' =>  $parserParams['oldid']),\\n        'timeout' => $wgVisualEditorParsoidTimeout\\n)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366641892, 'spacePHID': None, 'dateCreated': 1366408980, 'dateModified': 1417570698, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47434', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] VisualEditor: Link tool produces \"undefined\" in normal use', 'description': {'raw': 'The link tool showing \"undefined\" in step 5 of the bug report\\n\\n1. Hit an article on English Wikipedia and click \"Edit\" to invoke Visual Editor. I used http://en.wikipedia.org/wiki/Savage%2C_Montana.\\n\\n2. Double-click any word to highlight it. I used the first word of the \"History\" section, \"Savage\".\\n\\n3. Click the Link Tool icon, and the tool pops up.\\n\\n4. Choose any article title in the dropdown (I chose \"Savage Land\") and press Enter.\\n\\n5. The dropdown closes, and in the tool\\'s text input, instead of saying \"Savage Land,\" it says \"undefined.\" (See screenshot to be uploaded.)\\n\\n6. Now click outside the tool -- somewhere else on the article. The tool becomes completely blank (see second screenshot) and article text disappears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n\\n**Attached**: {F10425}'}, 'authorPHID': 'PHID-USER-o5tv5cyrple4fn5xqopm', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366919875, 'spacePHID': None, 'dateCreated': 1366381800, 'dateModified': 1417570782, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47413', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Master broken (jsduck)', 'description': {'raw': 'Master is failing jenkins tests right now due to some JSDuck failures.\\n\\nExamples: https://gerrit.wikimedia.org/49364 , https://gerrit.wikimedia.org/r/57922\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1365449081, 'spacePHID': None, 'dateCreated': 1365447240, 'dateModified': 1429023848, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47018', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switch integration for deployed wikis from tabLayout \"add\" to \"replace\" mode', 'description': {'raw': 'In preparation for making the VisualEditor the \"default\" editor, we should have the existing integration switched over for users so that they can see, test and feedback on the final UX for triggering edits in the run-up to switch-over.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366320602, 'spacePHID': None, 'dateCreated': 1365032940, 'dateModified': 1417570783, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46872', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins merged a faulty change', 'description': {'raw': 'Aaron Schulz wrote:\\n\\nI noticed that https://gerrit.wikimedia.org/r/#/c/33971/ passed the tests but after it was merged, the new tests started failing for everything. The commit to revert it also failed so I override Jenkins and merged anyway, and the failures went away for new commits. This indicates that something broken is going, possibly Jenkins running tests just against master rather than master + the patch, which would explain this problem.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394446474, 'spacePHID': None, 'dateCreated': 1364653620, 'dateModified': 1425378376, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46723', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Leaving a link while the inspector is open can remove the link', 'description': {'raw': \"0. Open a document with links already in it.\\n1. Click on a MediaWiki link, then click the icon to open the inspector.\\n2. Click anywhere else in the document to lose focus.\\n3. You're link has now been removed :(\\n\\nNote that this doesn't happen if you have just created a link, or if you have edited a link, so I assume this is functionality for letting people abandon the creation of a link.\\n\\nThe only way to remove a link should be with the delete icon in the inspector, or clear formatting.\\n\\nThis doesn't appear to affect external links.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363139966, 'spacePHID': None, 'dateCreated': 1363095900, 'dateModified': 1417570832, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46025', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Node API re-write', 'description': {'raw': 'The re-write of the node API that dm provide up to the rest of VE is necessary for most of the added support that VE is aiming to provide this year.\\n\\n[Mostly done now.]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361576303, 'spacePHID': None, 'dateCreated': 1360975080, 'dateModified': 1424894574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45062', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting last n lines and deleting - last line not deleted (Parsoid selser issue?)', 'description': {'raw': \"**Author:** `phil`\\n\\n**Description:**\\nvisual editor after deleting lines 3 and 4 - note that 4 is still visible and the gap inbetween 2 and 4 is marked as 'cannot be edited'\\n\\nI had text\\n1\\n2\\n3\\n4\\n\\nselecting the last 2 lines ( 3 and 4 ) and deleting and saving, on looking at the page again '4' is visible and there is a gap that is marked as 'cannot be edited'\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10499}\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366396346, 'spacePHID': None, 'dateCreated': 1360728000, 'dateModified': 1419137720, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44926', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parsoid selective serialisation issue when single LI made from P (?)', 'description': {'raw': '**Author:** `phil`\\n\\n**Description:**\\nerror message on save after changing bullet format\\n\\nBlank page\\nAdd some text e.g. \\'test\\' and make it a numbered bullet\\nSave the page\\nEdit the page\\nRemove the text \\'test\\'\\nClick on the \\'1\\' and click the numbered bullet control to remove it\\nSave page\\n\"Error loading data from server: Unsuccessful request: Error contacting the Parsoid server.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10836}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366396184, 'spacePHID': None, 'dateCreated': 1360092960, 'dateModified': 1366396184, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44687', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace creating a slug then deletes again', 'description': {'raw': 'Pressing backspace creating a slug then deletes again:\\n\\n* Create a new page (or go to an existing one), and enter \"AB\\\\nCD\\\\nEF\"\\n* Place the cursor down-page of \"F\" and press backspace; \"F\" is deleted correctly.\\n* Then press backspace again; \"E\" is deleted, as is the remaining slug, and the cursor moves us.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354754116, 'spacePHID': None, 'dateCreated': 1354563540, 'dateModified': 1454004173, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42655', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Implement \"Show changes\" (wikitext diff) in Save dialog', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355176624, 'spacePHID': None, 'dateCreated': 1354562580, 'dateModified': 1454004173, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42654', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paragraph changed to be a heading using the drop-down has its content deleted', 'description': {'raw': 'A paragraph when changed to be a heading using the toolbar drop-down has its content deleted (but the presence still stays).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354225226, 'spacePHID': None, 'dateCreated': 1354218900, 'dateModified': 1454004177, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42555', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backwards selection fails over inline alien nodes', 'description': {'raw': 'Start with an article with an inline alien - e.g. \"ABC<tt>:-)</tt>DEF\". Place cursor \"up page\" (in LTR, left) of inline alien; selection with keyboard down-page works as expected. Now place the cursor \"down page\" (in LTR, right) of the inline alien; selection with keyboard up-page fails when reaching the alien, clearing the selection and placing the cursor immediately up-page of the alien.\\n\\nNote that in RTL this appears to work fine(!).\\n\\nConfirmed in both Chrome and Firefox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354066309, 'spacePHID': None, 'dateCreated': 1353718440, 'dateModified': 1454004181, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42401', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pass reference to data element to DM node constructor', 'description': {'raw': 'Post-December cleanup:\\n\\nRather than passing the type, length, attributes and (soon) annotations into the dm.Node constructors separately, we should just pass a reference to the data element. This will make a lot of things cleaner, and make the constructors more consistent between node types.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354056487, 'spacePHID': None, 'dateCreated': 1353704640, 'dateModified': 1454004182, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42400', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector should edit existing annotation rather than creating new one', 'description': {'raw': 'When editing an existing link, the link inspector should grab the existing annotation and edit it, rather than starting over with a brand new annotation.\\n\\nDestroying the existing annotation loses metadata we need for preserving syntactical variation (hrefPrefix and origTitle), which means that currently, simply inspecting a link without actually changing its target can cause that link to be changed in the wikitext.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353971898, 'spacePHID': None, 'dateCreated': 1353380340, 'dateModified': 1454004182, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42282', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: First character in empty document behaves strangely in Firefox', 'description': {'raw': 'Steps to reproduce:\\n1. Go to a nonexistent page\\n2. Click the Create tab\\n3. Type \"foobar\"\\n\\nResult: \"f\" appears on a line by itself, \"oobar\" appears on the next line. The document model only contains \"oobar\". The \"f\" jumps around when rerendering (e.g. when you press enter).\\n\\nCan NOT be reproduced if:\\n* you use Chrome\\n* you click out of the editor and back into it before typing\\n* you press Ctrl+A, Backspace before typing text\\n\\nThe editor document looks like this:\\n\\n<div contentEditable=\"true\"><p><span class=\"slug\"></span></p></div>\\n\\nI think the cause of this bug is that Firefox initially puts the cursor before the <p>, rather than inside the <p> or inside the <span>.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354052317, 'spacePHID': None, 'dateCreated': 1353377280, 'dateModified': 1454004182, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42277', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add tab layout that adds a ve-tab instead of replacing the default', 'description': {'raw': \"Taken from bug 42117 which I'm de-prioritising\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354131976, 'spacePHID': None, 'dateCreated': 1353122700, 'dateModified': 1454004182, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42221', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Edits should add a VisualEditor tag (using MW's revision tagging system) so they can be identified\", 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354052322, 'spacePHID': None, 'dateCreated': 1353021960, 'dateModified': 1454004188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42172', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Meta-fy comments', 'description': {'raw': \"Comments should be stored in the meta-linmod, right now they're just ignored, which leads to all comments being removed when we save a page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353384355, 'spacePHID': None, 'dateCreated': 1352940240, 'dateModified': 1454004188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42124', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add handling for mw:Entity', 'description': {'raw': 'Currently these are being alienated, which is bad.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353528384, 'spacePHID': None, 'dateCreated': 1352938560, 'dateModified': 1454004188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42118', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove feedback link for deployment', 'description': {'raw': \"Remove the MW feedback link for December deployment; it's not helpful given the different paradigm for users in this content.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352941206, 'spacePHID': None, 'dateCreated': 1351911840, 'dateModified': 1454004188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41722', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support most common citation templates (special-case)', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364928248, 'spacePHID': None, 'dateCreated': 1345761780, 'dateModified': 1422562388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39600', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support references', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422562386, 'spacePHID': None, 'dateCreated': 1345761720, 'dateModified': 1422564475, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39599', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link types need to be used by the UI so that the link inspector doesn't fail completely. :-)\", 'description': {'raw': 'As DM now has been adopted to the new RDFa link types, the UI needs to be adapted to them. Right now, all link inspectors fail utterly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1344376085, 'spacePHID': None, 'dateCreated': 1344375240, 'dateModified': 1417570837, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39111', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: New annotation API (tracking)', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360205356, 'spacePHID': None, 'dateCreated': 1343672040, 'dateModified': 1552745162, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38854', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: License text should not be hard-coded', 'description': {'raw': 'The save dialog mentions but does not link to CC-BY-SA license, Project:Copyright page. These should be linked so you can get to them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 100, 'name': 'Unbreak Now!', 'color': 'pink'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354824360, 'spacePHID': None, 'dateCreated': 1340905500, 'dateModified': 1417570834, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38034', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor incompatible with \"Fixed header\" beta feature', 'description': {'raw': 'IE11 on Windows 7 \\nSee the two screenshots to compare - VE in betalabs and in test2. \\nProduction VE looks like test2 VE.{F24999}\\n\\n{F25001}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1441739949, 'spacePHID': None, 'dateCreated': 1419370204, 'dateModified': 1441739949, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create right-click menus for VisualEditor', 'description': {'raw': \"When I do Wikipedia editing workshops with VisualEditor, participants repeatedly suggest adding a right-click context menu.\\n\\nSomething like that exists in Google Docs, and it's surprisingly useful. For MediaWiki It can include similar functions - formatting, styling, linking, commenting, suggesting edits, etc.\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420842469, 'spacePHID': None, 'dateCreated': 1419081869, 'dateModified': 1420842469, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': ' VisualEditor JavaScript and tests should only be added if VisualEditor is installed', 'description': {'raw': \"According to Antoine when he runs the tests using the following extensions together:\\n\\n- JsonConfig\\n- Mantle\\n- MobileApp\\n- MobileFrontend\\n- WikiGrok\\n- ZeroBanner\\n- ZeroPortal\\n\\nThis yields two failures:\\n\\nResourcesTest::testMissingDependencies\\nThe module 'ext.visualEditor.mobileViewTarget' required by\\n'mobile.editor.ve' must exist\\nFailed asserting that an array contains 'ext.visualEditor.mobileViewTarget'.\\n\\nResourcesTest::testUnsatisfiableDependencies\\nUndefined index: ext.visualEditor.mobileViewTarget\\n\\n\\n\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-c5xwrfdyp3dckkh2nkoj', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-c5xwrfdyp3dckkh2nkoj', 'dateClosed': 1419447707, 'spacePHID': None, 'dateCreated': 1419008593, 'dateModified': 1520397283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Familiarize yourself with edit-reportcard.wmflabs.org', 'description': {'raw': 'https://edit-reportcard.wmflabs.org is a very rough beginning in the analysis of data related to the use of VisualEditor in the main wikipedias. The VisualEditor team needs help improving this space, so it provides metrics that help the team understand problematic areas, trends, impact of new features...\\n\\nAt this point there is basically no documentation. T84926 and T84927 are very basic starts. Can you dig in these metrics and the raw data associated, and understand what is being shown there?\\n\\nAlso, these graphs are created using [[ https://www.mediawiki.org/wiki/Analytics/Limn | Limn ]]. Have a look at the documentation in order to understand how it works. Bonus point if you install it locally and play with it a bit. \\n\\nIf you have any questions about Limn you can ask in the [[ https://lists.wikimedia.org/mailman/listinfo/analytics | analytics mailing list ]]. In any case, considering your background it is a good idea to subscribe to this list.'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-d3457iccsv4uq5ki2zkw', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-u7w6n5ecde66oujx33pe', 'dateClosed': 1446022703, 'spacePHID': None, 'dateCreated': 1418947018, 'dateModified': 1446022703, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Special:MyLanguage should have a way to redirect to the fallback language if there is no translation', 'description': {'raw': 'If, for example, we want to give a link from VisualEditor in the Afrikaans Wikipedia to the VE user guide in mediawiki.org, we can only link to the source page in English. It would be more convenient to link directly to Afrikaans, but Special:MyLanguage only works if the user defined the language in the preferences of the same wiki, and [[VisualEditor/User guide//af]] will appear like a non-existent page if there is no translation.\\n\\nI can think of several options to fix this:\\n* Make a non-existent sub-page redirect to the fallback language.\\n* Make Special:MyLanguage work across wikis somehow.\\n* Global cross-wiki language options (this would be Very Useful for a lot of other things).\\n\\n'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'dateClosed': 1465538675, 'spacePHID': None, 'dateCreated': 1418930787, 'dateModified': 1465538675, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'The undo link in the page history leads to the source editor and not VisualEditor', 'description': {'raw': \"The undo link in the page history leads to the source editor and not VisualEditor. It should lead to the VisualEditor for people who prefer to use it.\\n\\nIt's probably not a high priority at this point, but if the VisualEditor is supposed to replace the source editor, this issue should be handled at some point.\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1418657683, 'dateModified': 1679882715, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[gdash] \"VisualEditor: Latency\" graphs look dead', 'description': {'raw': 'https://gdash.wikimedia.org/dashboards/ve/ seems to be missing data since the end of November.'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418663319, 'spacePHID': None, 'dateCreated': 1418651695, 'dateModified': 1418663319, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '<templatedata> cannot be used as Template Data', 'description': {'raw': 'I installed VisualEditor on MediaWiki 1.24.0. It works well now, I can edit and save pages.\\n\\nBut when I tried to add Template Data to my old template page, it cannot be formate as a table. VisualEidtor cannot use template data when editing pages.\\n\\nMy template data:\\n\\n```\\n<templatedata>\\n{\\n    \"description\": \"插入注意文本框，突出显示注意内容\",\\n    \"params\": {\\n        \"1\": {\\n            \"label\": \"注意内容\",\\n            \"description\": \"注意文本框的内容\",\\n            \"required\": true,\\n            \"type\": \"string\",\\n            \"aliases\": [ \"注意内容\" ]\\n        }\\n    }\\n}\\n</templatedata>\\n```\\n\\nTemplate page: http://xuexiii.org/w/%E6%A8%A1%E6%9D%BF:%E6%B3%A8%E6%84%8F\\n\\nYou can see template data is displayed as plain text. But in English Wikipedia, it should become a table.'}, 'authorPHID': 'PHID-USER-g2bnzp2j6voh3sihftsl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418406238, 'spacePHID': None, 'dateCreated': 1418381694, 'dateModified': 1438736767, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Feedback link in VisualEditor needs to play nicely with LiquidThreads', 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Open VisualEditor on MediaWiki.org.\\n2.  Click on \"Leave feedback\" in the help menu.\\n3.  Choose to leave feedback onwiki.  Type something and submit your feedback.\\n\\nResult:\\n\\nThe feedback is posted as a ==Regular section heading== with normal, signed ~~~~ comments to a feedback page that is using LiquidThreads.  It either needs to post correctly within LiquidThreads or it needs to post to a different page.'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418195777, 'spacePHID': None, 'dateCreated': 1418189771, 'dateModified': 1425671424, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Rationalize the project names of VE and wikitext editor', 'description': {'raw': 'Can we create consistency between the naming convention of the (sub)projects related to Visual Editor and Wikitext editor to make them more easily findable and have better parity?'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418165494, 'spacePHID': None, 'dateCreated': 1418160470, 'dateModified': 1459674623, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Compatibility in Beta Features', 'description': {'raw': '//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/35 //\\n\\n== Narrative ==\\n\\nAs a user, I want to know if a beta feature doesn\\'t work work for my browser or technical configuration.\\n\\n\\n\\n== Acceptance Criteria ==\\n\\nBrowser and technology compatibility can vary from one feature to another (VisualEditor in particular isn\\'t available for IE yet). Other features may require Javascript, CSS or other technical configurations as well, that could cause them to malfunction if not enabled.\\n\\nSo each beta feature extension needs to have a blacklist of platforms that it cannot support, stored in Javascript, JSON or other machine-readable format that can be sent to Beta Features.\\n\\nThe Beta Features (or the extension) then needs to check whether the user\\'s configuration matches one of these restricted platforms, so it can let the user know if their platform is not compatible with that feature.\\n\\nLast but not least, we also need to inform the user about features that are not compatible with their particular browser or configuration. For example, we may want to display a message like: \"This feature is not compatible with your browser yet.\"\\n\\nThis is required so the user understands why they cannot enable that feature (even though it\\'s still checked in their preferences -- so they can use it on other platforms).\\n\\nThat message could be bolded and/or colored in red, to provide a visual cue that this feature will not work. Maybe the entire feature could be grayed out, to make it even more explicit?\\n\\nHere are the types of notes we may need to display, when a feature is not compatible for the user\\'s configuration:\\n* Notes about browser compatibility\\n** Text displayed to user \"This feature is not compatible with your browser yet.\"\\n* Notes about JS compatibility\\n** Text displayed to user \"You must  [[http://www.enable-javascript.com/ | enable JavaScript]] in your browser to use this feature.\"\\n* Notes about CSS compatibility\\n** Text displayed to user \"Your site skin or custom CSS is not compatible with this feature, to enable it use the default site skin.\"\\n\\nOnly one error message should be displayed at any given time, the order of display should be as follows\\n# CSS/Skin compatibility\\n# JS compatibility\\n# Browser compatibility\\ne.g. if there is both a browser and JS compatibility issues the user would only see the JS issue.\\n\\nSee the most current feature requirements here:\\n\\n [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] \\n\\n\\n\\n== Related Bugs ==\\n\\n== Related Stories ==\\n\\n [[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/2 | #2]]  Beta features\\n\\nSee also:\\n\\n [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] '}, 'authorPHID': 'PHID-USER-64gvupsl7ajewpshylma', 'ownerPHID': 'PHID-USER-dbudsaorcqut7sg3vvbi', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-64gvupsl7ajewpshylma', 'dateClosed': 1418054216, 'spacePHID': None, 'dateCreated': 1418054212, 'dateModified': 1418056732, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing\", 'description': {'raw': 'OOUI\\'s svgo-optimized SVG files are not compatible with rsvg\\'s broken SVG parsing. \\n\\nsvgo emits SVG like `<path d=\"M-1-2 …\">` or `<path d=\"M.3.5 …\">` which rsvg is unable to parse (this is valid path data fragment that represents a points (-1; -2) and (0.3; 0.5), and the SVG 1.1 spec even explicitly discusses this syntax). The same issue affects ImageMagick when compiled with rsvg support.\\n\\nThis means that some of OOUI\\'s and VisualEditor\\'s icons will not appear correctly e.g. when uploaded to Commons, and blocks {T76473} since we\\'re unable to rasterize the SVGs to PNG.\\n\\nThis can be worked around using some search-and-replace, but this leaves some questions:\\n\\n* Can this be fixed in rsvg? Gotta file a bug, even if it\\'ll probably be ignored, and even if not no one is going to upgrade their copy.\\n* //Where// do we apply the workaround? To the files in git? During build process? In MediaWiki\\'s RL module from T76473?\\n* Should we maintain the workaround ourselves somewhere, or maybe it could be upstreamed to svgo? (As a command-line option for people who want rsvg compatibility at the cost of a few bytes, like us?)'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1417784237, 'spacePHID': None, 'dateCreated': 1417782237, 'dateModified': 1550848519, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'wikibugs fails to link Phab task in some IRC notifications', 'description': {'raw': 'wikibugs fails to link Phab task in some IRC notifications, dunno why. From #-visualeditor (times in CEST or something):\\n\\n```\\n[20:38]\\t<wikibugs> OOjs-UI: MediaWiki, Apex: Provide default margins for buttons and other widgets\\n...\\n[20:41]\\t<wikibugs> OOjs-UI: ComboBoxWidget: Provide a getMenu method\\n```\\n\\nThe tasks it should have linked are T76643 and T76646.'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'dateClosed': 1419290531, 'spacePHID': None, 'dateCreated': 1417635858, 'dateModified': 1419290531, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'wm-bot facts have too much bugzilla in them', 'description': {'raw': 'Ctrl + F on http://bots.wmflabs.org/~wm-bot/db/%23mediawiki.htm gives 27 usages\\n\\nSome are probably ok (aliases and such), but some plainly need updating\\n\\n[22:10:20] <Reedy> !bug\\n[22:10:20] <wm-bot> https://bugzilla.wikimedia.org/\\n\\nAnother being vebug giving \"Submit a new ticket on Bugzilla for the VisualEditor: https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditor\"'}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': 'PHID-USER-qgqq35kbi5wss2tlgmhg', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-qgqq35kbi5wss2tlgmhg', 'dateClosed': 1422127750, 'spacePHID': None, 'dateCreated': 1417558557, 'dateModified': 1422127750, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor \"basic\" image type should be called \"inline\"', 'description': {'raw': 'The media type \"basic\", described using the message Visualeditor-dialog-media-type-none does not explain the real meaning of how the image will be inserted.\\n\\nIt will be clearer to call it something like \"Inline\", and possibly to change the icon as well.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417542081, 'spacePHID': None, 'dateCreated': 1417524575, 'dateModified': 1433959744, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Module 'mobile.editor.ve' has incompatible target 'desktop'\", 'description': {'raw': \"```\\n2) ResourcesTest::testUnsatisfiableDependencies\\nThe module 'mobile.editor.ve' must not have target 'desktop' because its dependency 'ext.visualEditor.mobileViewTarget' does not have it\\n```\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'dateClosed': 1418245041, 'spacePHID': None, 'dateCreated': 1417494246, 'dateModified': 1520397306, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a project for \"verified in phase0\", \"verified in phase1\" and \"verified in phase2\" for QA', 'description': {'raw': 'This is so we can manage tasks as being definitely fixed, not just that it worked in test.\\n\\nDescriptions: \"Project for tasks verified by QA as being fixed in phase<N>.\"\\n\\nAccess as normal; icon as normal.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417042467, 'spacePHID': None, 'dateCreated': 1417042379, 'dateModified': 1623921585, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor is not displayed after clicking on Edit', 'description': {'raw': 'MediaWiki version is 1.25wmf9\\n\\nVisualEditor 1.25wmf9 is installed and enabled:\\n```\\nrequire_once \"$IP/extensions/Parsoid/Parsoid.php\";\\nrequire_once \"$IP/extensions/VisualEditor/VisualEditor.php\";\\n\\n$wgDefaultUserOptions[\\'visualeditor-enable\\'] = 1;\\n$wgHiddenPrefs[] = \\'visualeditor-enable\\';\\n//$wgDefaultUserOptions[\\'visualeditor-enable-experimental\\'] = 1;\\n$wgVisualEditorParsoidHTTPProxy = false;\\n$wgVisualEditorParsoidURL = \\'http://[my.nodejs.host]:80\\';\\n$wgVisualEditorParsoidPrefix = \\'myWiki\\';\\n//$wgSessionsInObjectCache = true;\\n$wgVisualEditorParsoidForwardCookies = false;\\n$wgVisualEditorNamespaces = array_merge( $wgContentNamespaces, array( NS_USER ) );\\n```\\n\\nIf I curl Parsoid for the Main Page (from the same host where MediaWiki is installed) I can see page parsed and a log on Parsoid\\n```\\ncurl http://[my.nodejs.host]/myWiki/Main_Page?oldid=1\\n```\\n\\nIf I click on Edit {F16470} the page is refreshed (?title=Main_Page&veaction=edit), but I can\\'t see the VisualEditor editing area. Moreover, nothing is logged on Parsoid (like if the request has never be done).\\nIf I click on Edit source the standard editor is displayed.'}, 'authorPHID': 'PHID-USER-aost7ybqf3mbefvdfsdc', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417041211, 'spacePHID': None, 'dateCreated': 1417033425, 'dateModified': 1438736334, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Mismatch between new page text seen by AbuseFilter and actual new page content', 'description': {'raw': 'On frwiki, we have false positives on a filter that tags edits that remove all categories.\\n\\nFilter: https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Filtre_antiabus/14\\nExample of false positive: https://fr.wikipedia.org/w/index.php?title=Bertrand_Chameroy&diff=prev&oldid=109458887 (it should not have the tag \"suppression des catégories\")\\nDetails of the AbuseFilter log event: https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1204633\\n\\nI am sure that this is not an error in the filter itself, because in the details of the AbuseFilter log event, the diff shows that categories are indeed removed. But this diff does not match the real diff, where categories are unchanged.\\n\\nExpected behavior: the content of the \\'new_text\\' variable of AbuseFilter should always match the new page text.\\n\\nI found 4 such false positives for this filter in the last two months. In all cases, modification also has the \\'VisualEditor\\' tag, so this could be related.\\n\\nOther cases:\\nhttps://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1200961\\nhttps://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1190456\\nhttps://fr.wikipedia.org/wiki/Sp%C3%A9cial:Journal_du_filtre_antiabus/1164028\\n'}, 'authorPHID': 'PHID-USER-5h57zgttfaaarfvo4g6s', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-jcypqodpdpbcicgwgh7j', 'dateClosed': 1417033415, 'spacePHID': None, 'dateCreated': 1417029094, 'dateModified': 1432407059, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cite inspector does not disappear upon clicking Insert, prevents page save', 'description': {'raw': 'Edit any page in beta labs, e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Cite_VisualEditor_Test?vehidebetadialog=true&veaction=edit\\n\\nClick Cite and fill in the textareas\\n\\nClick Insert\\n\\nCite inspector should disappear but does not. \\n\\nAlso note that the appearance of the Cite inspector is exceptionally small, in both Firefox and Chrome'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1423275807, 'spacePHID': None, 'dateCreated': 1416844281, 'dateModified': 1438736637, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Newly made links are red until page is saved', 'description': {'raw': 'When I put in the template \"Infobox road\" onto a subpage of my user page, and added some parameters, the links they made were red.\\n\\nScreenshot link:\\n\\n[[https://en.wikipedia.org/wiki/File:Philroc-VEBug.png|The screenshot (red links circled)]]\\n\\nMore info:\\n\\n[[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Newly_made_links_are_red_until_page_is_saved|The bug at Wikipedia]]\\n\\nI hope somebody gets to this soon.\\n\\nThanks!'}, 'authorPHID': 'PHID-USER-tx42osyrriffbzlseejv', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1429146825, 'spacePHID': None, 'dateCreated': 1416840250, 'dateModified': 1429147082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Maximum function nesting level\" fatal when visiting an imported page with nested conversations', 'description': {'raw': 'I imported https://www.mediawiki.org/wiki/VisualEditor/Feedback into Flow with the LQT importer (plus some small changes for https://gerrit.wikimedia.org/r/#/c/172925/ that are probably not relevant to this bug).\\n\\nThe import crashed (bug 73638), but a lot of stuff was already imported by then.  However, when I visit it, I get:\\n\\n\"Fatal error: Maximum function nesting level of \\'200\\' reached, aborting\"\\n\\nThe stack is https://phabricator.wikimedia.org/P98 .\\n\\nIt seems that the nesting level of a topic may influence the nesting level of the function stack, and cause it to go over the limit.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416454279, 'spacePHID': None, 'dateCreated': 1416453300, 'dateModified': 1418952758, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73639', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Detected overflow for millisecond timestamp\" UID error when importing large LQT board into Flow', 'description': {'raw': \"I hit this when testing https://gerrit.wikimedia.org/r/#/c/172925/ against https://www.mediawiki.org/wiki/VisualEditor/Feedback .\\n\\nSo far I haven't retested against master, since the import is pretty slow.  I suspect it will be present there.\\n\\nCommand was:\\n\\nmwscript extensions/Flow/maintenance/convertLqt.php --wiki=wiki User_talk:VE_Feedback_1 --allowunknownusernames 1 --remoteapi=https://www.mediawiki.org/w/api.php --srcpage=VisualEditor/Feedback --verbose \\n\\nLog is https://phabricator.wikimedia.org/P97 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-r5pzlcquei6f4hb53rfg', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'dateClosed': 1416977427, 'spacePHID': None, 'dateCreated': 1416452820, 'dateModified': 1418952757, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73638', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] VisualEditor: Switching to read mode after rendering diff leaves ve.ce.Surface behind', 'description': {'raw': 'Screenshot of Read mode after editing\\n\\nSteps to reproduce bug:\\n\\n1. Edit a page\\n2. Insert some text or a table\\n3. Click \"Save page\" in the toolbar\\n4. Click \"Review your changes\" in the dialog\\n5. Click \"Return to save form\"\\n6. Click \"Resume editing\" in the dialog\\n7. Click \"Read\" tab from the MediaWiki navigation\\n\\n\\nExpected:\\n\\nOriginal page re-appears.\\n\\nActual:\\n\\n* The modified state from the editor persists.\\n* Even the highlighting is still there (e.g. can highlight different cells in the table  we just inserted).\\n* The \"Edit\" tab in the MW nav is now broken (clicking it does nothing, no exception thrown).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15110}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416364083, 'spacePHID': None, 'dateCreated': 1416363840, 'dateModified': 1417570673, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73590', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"[Regression wmf9]Cannot create a new page in Firefox. Edit button doesn't respond\", 'description': {'raw': 'switch edit mode fails in Chrome\\n\\nThis manifests in several ways, see the browser test failures at\\nChrome: https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/\\nFirefox: https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/\\n\\nThe common case for Chrome and Firefox:\\n\\nAs a logged-in user with access to VisualEditor, edit any page. \\nAttempt to switch from the wikitext editor to VE using the dropdown controls. \\nNothing happens, VE does not show up.  See screen shot. \\n\\nThe Firefox-only issue: \\n\\nAttempt to edit a new page by supplying a bogus URL, e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Foobarbaz\\n\\nClicking the edit icon does nothing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F15094}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'dateClosed': 1416813165, 'spacePHID': None, 'dateCreated': 1416354960, 'dateModified': 1416813191, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73585', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:[Regression pre-wmf9] Inserted Media caption is not displayed correctly', 'description': {'raw': 'Caption without background\\n\\nBetalabs only in Chrome, FF, and Safari. test2 is fine.\\n\\n\\nVE - Insert Media and enter Caption - save the page. The Media caption is displayed with white background. \\nSee the attached screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15369}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416433677, 'spacePHID': None, 'dateCreated': 1416006000, 'dateModified': 1417570672, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73441', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'small race condition in Links inspector', 'description': {'raw': 'Edit a page on beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Links_VisualEditor_Test?vehidebetadialog=true&veaction=edit\\n\\nClick the Links inspector\\n\\nNote that the \"Done\" button is enabled\\n\\nQuickly paste (do not type by hand) an external link e.g. http://www.example.com in the link field\\n\\nNote that upon pasting \"http://www.example.com\", VE takes some time before displaying the \"External link/New page\" overlay. \\n\\nIf the user clicks \"Done\" after pasting text in the link field but before the \"External link/New page\" overlay appears, VE creates a local link [[foo]] instead of the desired external link [http://www.example.com foo]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1423276281, 'spacePHID': None, 'dateCreated': 1415985120, 'dateModified': 1438736628, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73421', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Safari - white spaces are dropped for copied formatted text', 'description': {'raw': \"Safari cut and paste formatted text-white spaces issue\\n\\nSteps to reproduce: \\n\\nSafari only - test2, Betalabs.\\n\\n1. In VE type some text - e.g. underlined text. Apply underlined format to 'underlined'.\\n\\n2. Highlight 'underlined text' and copy/paste it somewhere else on the page. \\n\\nIt will be displayed as: underlinedtext. Underlined formatting will be gone and a white space between words is lost. \\n\\nThis is affecting many options in formatted text - see the attached screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15096}\"}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415898350, 'spacePHID': None, 'dateCreated': 1415831700, 'dateModified': 1417048865, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73333', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using the VE toolbar in MSIE causes the cursor to jump to the start of the page', 'description': {'raw': 'Saw lots of bugs reported and fixed about the jumping of focus when using the toolbar.  Now seeing the problem in MSIE for many uses of the toolbar.  Would like a clue about fixing it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418417406, 'spacePHID': None, 'dateCreated': 1415771100, 'dateModified': 1487404429, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73294', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paste from Word to MSIE fails to insert anything', 'description': {'raw': 'Pasting anything besides plain text into MSIE fails.  Tried this with Word in FF and Chrome (see bug #73292) and had at least some success.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'dateClosed': 1429106123, 'spacePHID': None, 'dateCreated': 1415766540, 'dateModified': 1438736450, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73293', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: in category selector, clicking on scroll bar for drop down dismisses dropdown', 'description': {'raw': 'When the categories suggested in the drop down are long enough, a scroll bar appears.  Clicking on this scroll bar causes the drop down to close.\\n\\n\\nIt would be nice if you could use the scrollbar like others -- to scroll up and down the list.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415843475, 'spacePHID': None, 'dateCreated': 1415743920, 'dateModified': 1417570676, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73284', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:[Regression]Add text and a space before language annotation, then delete space, text looses language style', 'description': {'raw': 'Enviornment-test2, beta\\n\\n1> Select language and click done, when the language inspector opens.\\n2>type some text ,on the CE.\\n//the text has language style\\n3>now place the cursor to the start of the line and type in some more text.\\n// also has the language  style\\n4> after typing the additional text insert a space. Then delete that space.\\nNotice the cursor moves to the start of the line and also the language annotation from the recently typed text has been removed. Whereas the previously typed text still retains the annotation style.\\n\\nSee screencast.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1423524376, 'spacePHID': None, 'dateCreated': 1415627460, 'dateModified': 1438736555, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73218', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't delete text... which is actually not there\", 'description': {'raw': 'User added the words \"La mui\" to https://fr.wikipedia.org/wiki/Audiomachine#Utilisations_de_leurs_musiques . Then proceeded to edit elsewhere in the page. When he went back to those words, he found out he couldn\\'t remove them at all (see screencast at https://www.youtube.com/watch?v=IMlMZt1FMvY : all his actions seem to affect the header below). When he reviews his changes, that content is actually not there.\\n\\nWindows 7, Firefox Aurora 35.0a2 (2014-11-05), Vector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1423693003, 'spacePHID': None, 'dateCreated': 1415610300, 'dateModified': 1439679270, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73216', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tables wikitext can be inconsistent', 'description': {'raw': 'In wikitext editor, you can separate cells with a double bar \"||\" on the same line :\\n\\n|Cell 1 || Cell 2 || Cell 3\\n\\n(same thing for headers, except two exclamation marks \"!!\" are used).\\n\\nWhen adding a new cell with VE, the result will look like\\n|Cell 1 || Cell 2 || Cell 3\\n|Cell 4\\n\\nrather than |Cell 1 || Cell 2 || Cell 3 || Cell 4 .\\n\\nWhile this still works, it makes the table less understandable and usable for those who do not use VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1417042588, 'spacePHID': None, 'dateCreated': 1415608980, 'dateModified': 1417042588, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73215', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Annotation on top of a link produces inefficient wikitext ([[asd|''asd'']])\", 'description': {'raw': 'Annotation on top of a link produces inefficient wikitext ([[asd|\\'\\'asd\\'\\']]).\\n\\n1. Type text, for example \"asd\".\\n2. Select it.\\n3. Press Ctrl+K to create a link, accept \"asd\" as link target.\\n4. Press Ctrl+I to italicize.\\n\\nResult: [[asd|\\'\\'asd\\'\\']].\\n\\nCompare with:\\n\\n1. Type text, for example \"asd\".\\n2. Select it.\\n3. Press Ctrl+I to italicize.\\n4. Press Ctrl+K to create a link, accept \"asd\" as link target.\\n\\nResult: \\'\\'[[asd]]\\'\\'.\\n\\nI would expect both ways to produce the same wikitext, \\'\\'[[asd]]\\'\\'.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415618227, 'spacePHID': None, 'dateCreated': 1415552880, 'dateModified': 1415618227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73201', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [regression] Inserting new internal link inserts text, but doesn't linkify it, if you complete the dialog before page title suggestions appear\", 'description': {'raw': \"Inserting new internal link inserts text, but doesn't linkify it.\\n\\n1. Place cursor on empty paragraph\\n2. Open the link inspector (Ctrl+K)\\n3. Type in title of a page and press Enter\\n\\nA new link to that page should appear. Instead, only the text typed is inserted, without the link annotation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1423526453, 'spacePHID': None, 'dateCreated': 1415543760, 'dateModified': 1438736355, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73195', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Newly added template added with \"Template:\" prefix', 'description': {'raw': 'https://www.mediawiki.org/w/index.php?title=Google_Code-in_2014&diff=1255073&oldid=1255066\\n\\nNewly added \"Bug\" template was added as {{Template:Bug|…}} rather than just {{Bug|…}}. As far as I know I did nothing special to cause that.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416188116, 'spacePHID': None, 'dateCreated': 1415462520, 'dateModified': 1416260589, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73179', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Get Parsoid (and thus VisualEditor) working again on Wikitech', 'description': {'raw': 'They broke and were disabled, but we should get them back.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1426689638, 'spacePHID': None, 'dateCreated': 1415318040, 'dateModified': 1426689638, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73104', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core)\", 'description': {'raw': 'flow_tree_revision\\n\\nParsoid is running happily. I can edit pages using VisualEditor without issue.\\n\\nI can visit a Flow page and add a new topic or comment. However, upon saving I don’t actually see the content of the comment. Topic titles do show up.\\n\\nI’m not a DB guru, but upon inspecting the flow-specific database tables I noticed some weird syntax in the fields. Maybe it’s my editor (Sequel Pro) or an encoding issue.\\n\\nI turned on MW debugging and I see this message:\\n\\nWarning: DOMDocument::saveHTML() expects exactly 0 parameters, 1 given in /var/www/html/w/extensions/Flow/includes/Parsoid/Utils.php on line 273\\n\\n1.25wmf5, PHP 5.3.3, most recent head/master build of Flow, most recent build of Parsoid.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n\\n**Attached**: {F15052}'}, 'authorPHID': 'PHID-USER-xd3dshn3ykvvbsxmqbg6', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415386992, 'spacePHID': None, 'dateCreated': 1415226120, 'dateModified': 1418952760, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73048', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Calling VisualEditor from MF spins forever', 'description': {'raw': 'As a logged in user with VE available, edit any page in beta labs e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Cyrion_and_Candidus#/editor/0\\n\\nPage is white and shows spinner, editor never appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415213710, 'spacePHID': None, 'dateCreated': 1415213400, 'dateModified': 1417570678, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73039', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] Safari only - the page is blurred in Edit mode', 'description': {'raw': 'Safari blurs text\\n\\n1. Open a page in Safari VE Read mode - the text is displayed normally.\\n\\n2. Switch to Edit  - the beginning of the page displays a blurred text.\\nClicking in the text does not make it clearer. \\n\\nSee the attached screenshots.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15010}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417578010, 'spacePHID': None, 'dateCreated': 1415209920, 'dateModified': 1438736406, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73035', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Fix the language screenshot test for new VE architecture', 'description': {'raw': 'VE no longer has iframes.  I don\\'t really understand how \"iframe_element\" is being used: \\n\\n$ grep -r \"iframe_element\" *\\nfeatures/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.iframe_element], nil, -2)\\nfeatures/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.iframe_element], nil, -2)\\nfeatures/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.iframe_element], nil, 0)\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"VisualEditor_Page_Settings_Redirects-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.page_settings_heading_element, @current_page.prevent_redirect_element], @current_page.iframe_element, 0)\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"VisualEditor_Page_Settings_TOC-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.table_of_contents_element], @current_page.iframe_element, 0)\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"VisualEditor_Page_Settings_Edit_Links-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.page_settings_editlinks_element], @current_page.iframe_element, 0)\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"VisualEditor_Apply_Changes-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.settings_apply_button_element], @current_page.iframe_element, 3)\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.link_list_element, @current_page.iframe_element, @current_page.new_link_element], nil, 0)\\nfeatures/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.iframe_element])\\nfeatures/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.iframe_element], nil, 0)\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"VisualEditor_Media_alternative_text-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.media_alternative_block_element], @current_page.iframe_element)\\nfeatures/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.iframe_element], nil, 0)\\nfeatures/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.iframe_element])\\nfeatures/step_definitions/language_screenshot_steps.rb:    page.iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.iframe_element, @current_page.formula_image_element], nil, 0)\\nfeatures/step_definitions/language_screenshot_steps.rb:  on(VisualEditorPage).iframe_element.when_present.should be_visible\\nfeatures/step_definitions/language_screenshot_steps.rb:  capture_screenshot(\"#{@scenario.name}-#{ENV[\\'LANGUAGE_SCREENSHOT_CODE\\']}.png\", [@current_page.iframe_element], nil, 0)\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-b5bosdf7b7zp3vqofbug', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415625366, 'spacePHID': None, 'dateCreated': 1415209320, 'dateModified': 1418980183, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73033', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Safari only - typing text in a table cell - the page scrolls up', 'description': {'raw': '1. Safari - open any page and make sure that a page has enough content to have a vertical scrollbar. \\n\\n2. Insert a table at the bottom of the page.\\n\\nStart typing in a table cell - the page scrolls up with each typed character.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417577587, 'spacePHID': None, 'dateCreated': 1415149320, 'dateModified': 1438735434, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72999', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: line height in intro message is wrong causes collusions', 'description': {'raw': 'text collisions\\n\\nline height should be increased to not have text and controls run together.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14807}'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415130154, 'spacePHID': None, 'dateCreated': 1415128920, 'dateModified': 1415145904, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72964', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: featured article template is hidden and easy to accidently delete', 'description': {'raw': \"icon not showing in VE\\n\\nthe featured article template added a significant amount of blank headspace to articles and doesn't draw the icon, so it is easy to accidently delete.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14803}\"}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415129033, 'spacePHID': None, 'dateCreated': 1415128800, 'dateModified': 1415129033, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72963', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: unexpected results while copy/pasting reference contents', 'description': {'raw': 'See https://www.mediawiki.org/w/index.php?title=User:Elitre_(WMF)/sandbox&diff=prev&oldid=1249997 .\\n\\nReferences at the words \"this\" were created by copy/pasting the contents of the reference at the word \"complex\".\\n\\nNotice:\\n1) The spaces between the elements get removed (Bug 71718?)\\n2) The wikilink gets changed;\\n3) If you selected until after the \"citation needed\" template only, this wouldn\\'t appear when pasting (Bug 49396?).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415063629, 'spacePHID': None, 'dateCreated': 1415024640, 'dateModified': 1415063629, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72901', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:After adding a focusable node inside a content cell , placing cursor at the end of the table scrolls the page down', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Insert a table\\n2.Add any focusable node inside content cell like template/image/math function\\n3.Place the cursor at the end of the table\\n\\nObserved Result:\\nThe page scrolls down to the end of it\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'dateClosed': 1424204606, 'spacePHID': None, 'dateCreated': 1414734360, 'dateModified': 1425487587, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72804', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor does not display Files, and can not access the local files', 'description': {'raw': '**Author:** `lhug`\\n\\n**Description:**\\nIntention:\\nTrying to edit a page with linked files on a private wiki. Mainly to test if the Visual Editor functions are usable.\\n\\nSteps to Reproduce:\\n1. Open page with a linked file\\n2. click \"edit\"\\n3. wait and see\\n\\nActual Results:  \\nThe linked file simply disappears and is not visible to the editor. after saving, it is accessible again. Trying to insert media showed no local media.\\n\\nExpected Results:  \\nPicture is editable of course, and at least a list of media to add.\\n\\nReproducible: Always\\n\\nUsing vector as skin. Changing skin did not resolve the issue. Wiki is running on a CentOS with self certified SSL. \\nAccessing files that are on the commons is possible, and these are viewable by the editor. Copying the Link properties to other media links does not help, they are still invisible to the editor. Normal Text is editable and media are accessible there. Tried Workarounds found on several pages:\\n\\nChanging permissions to all-read-true and/or all-read-edit-true did not resolve the issue. (in fact, if I do that, many pictures are not viewable - they are still there and linked, but show broken image)\\nGranting the ImageSearch read permissions did not help.\\ngranting localhost, 127.0.0.1, our url and our IP read permissions did not help.\\n2 API-Queries returned expected results (https://dpaste.de/0Adz for ?action=query&prop=imageinfo&iiprop=url|size&iiurlwidth=220&titles=File:Logo.jpg&format=json and ?action=query&prop=imageinfo&iiprop=url|size&titles=File:Logo.jpg&format=json\\n\\nLocally (on a Ubuntu machine) the pictures are being shown, yet the local media repo is empty to the VE.\\n\\nWe are running parsoid as a service run by root, the log file reports API request failed when trying to edit a page with pictures in it.\\n\\nThe used versions are MediaWiki 1.23.5, VE Snapshot 1.23, nodejs 0.10.30, Parsoid snapshot 1.23\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1513167417, 'spacePHID': None, 'dateCreated': 1414670820, 'dateModified': 1513167417, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72760', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Build jsduck through Gruntfile', 'description': {'raw': 'VisualEditor build documentation via Grunt [1] and publish via Jenkins.\\nOne of the benefits of this is you can use a jsduckcatconfig that pulls in documentation from core.\\n\\nWe should do the same.\\n\\n[1] https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor/f35d577acb57319241ea992a95cb045298662cd8/Gruntfile.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-c5xwrfdyp3dckkh2nkoj', 'dateClosed': 1417428436, 'spacePHID': None, 'dateCreated': 1414622580, 'dateModified': 1418682574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72718', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: There is no Preview bar appearing at the top in iOS Safari for tablet and desktop browser while saving the edited content', 'description': {'raw': 'screenshot in desktop browser\\n\\nSteps to reproduce:\\n\\n1.Open the wikitext editor for any page in en.m.wikipedia.org \\n2.Make some edit\\n3.Click on \"Next\"\\n\\nObserved Result:\\n\\nThere is no preview bar appearing at the top of the page indicating it\\'s a preview as it does in iOS safari for iPhone.\\n\\n\\nSee the screenshots attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14824}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'dateClosed': 1418171147, 'spacePHID': None, 'dateCreated': 1414619880, 'dateModified': 1418171147, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72709', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Newly filed bugs with empty description are not accounced on IRC', 'description': {'raw': \"Newly filed bugs with empty description are not accounced on IRC. Bug 72705 wasn't pushed to #mediawiki-visualeditor when I filed it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-muirnivxp5hzppn2a3z7', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414620496, 'spacePHID': None, 'dateCreated': 1414619700, 'dateModified': 1496861847, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72708', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Issues with icons in alpha. Get fixed so we can move it to beta.', 'description': {'raw': \"* CtaDrawer down icon is not centered\\n* Switcher in VisualEditor/Wikitext editor\\n* Notification icon tiny mw-ui-icon-notification isn't sized correctly – font-size: 1.3em\\n* Clicking the notification icon doesn't hide it while the notifications are loading\\n* #page-actions .mw-ui-icon:before (the page actions) margin needs to be lowered\\nAnimation of the watchstar is broken\\n* Toggleable (?) elements (Contents, section headings) don't have cursor: pointer\\n* Watch star in page actions moves slightly to the left every time you click it\\n* Provide SVG versions of all icons which currently only use SVGS\\nThe watchstar in the search results is tiny\\n.mw-ui-icon-arrow-up isn't positioned hard-right when Contents is open\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415228819, 'spacePHID': None, 'dateCreated': 1414539120, 'dateModified': 1415228819, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72653', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor edit summary is not saved', 'description': {'raw': 'Example: https://www.mediawiki.org/w/index.php?title=Project%3ASandbox&diff=1242918&oldid=1242833\\n\\nSummary input: \"Test\". The summary was not saved.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-c5xwrfdyp3dckkh2nkoj', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416062866, 'spacePHID': None, 'dateCreated': 1414484940, 'dateModified': 1416062866, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72612', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Create and enable MobileFrontend npm test job', 'description': {'raw': \"I notice VisualEditor has lots of Grunt magic. If I'm not mistaken the Gruntfile on each merge [1].\\n\\nCan a similar job be setup on mobile and could I grab one of either Krinkle and Antoine to see what else Mobile can do to get the most out of this Gruntfile?\\n\\n[1] https://integration.wikimedia.org/ci/job/oojs-ui-npm/1740/console\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1416824767, 'spacePHID': None, 'dateCreated': 1414453200, 'dateModified': 1416947306, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72598', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'grrrit-wm: runs into infinite loop if unable to join channels', 'description': {'raw': 'Email I sent to Yuvi:\\n\\ntl;dr: grrrit-wm is broken right now, it\\'s not relying messages, and\\nwhen we try and attempt to kill it with qdel, it goes into some error\\nstate and keeps connecting/quitting.\\n\\nhuh (PiRSquared) thinks he broke it when quieting it in another channel,\\nit was down for a while before I came online. He asked if he could\\nupgrade the irc node module it was using, so I said sure since he\\nalready had access...that didn\\'t work, so he reverted it, but it\\'s still\\nnot working.\\n\\nI logged into gerrit-to-redis, and based on the log messages it appears\\nto be working fine (I also restarted it just in case, and it was working\\nfine after the restart)\\n\\nSo yeah...halp?\\n\\n<http://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-dev/20141026.txt> is\\nour log trying to figure stuff out.\\n\\n---\\n\\nSecond email:\\n\\nTo stop spam, we moved the config.yaml to \"config_moved-cuz-bug\" so it\\nwould stop joining. It also finally died from qstat.\\n\\nAt this point I\\'m not going to touch it until you or someone else has\\ntime to debug it...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ct4qymje4lpxby255tze', 'dateClosed': 1481910600, 'spacePHID': None, 'dateCreated': 1414294380, 'dateModified': 1481910600, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72523', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Link inspector opens with an animation from top while trying to open it for the first time in an edit session', 'description': {'raw': 'video capture\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.click on link inspector icon \\n\\nObserved Result:\\nLink inspector opens with an animation from top\\n\\nSee the video capture attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14920}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1421864810, 'spacePHID': None, 'dateCreated': 1414184760, 'dateModified': 1438735444, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72495', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Get Grunt setup in MobileFrontend', 'description': {'raw': 'VisualEditor team is using a grunt file. Flow have also moved to one of these.\\n\\nOne of the benefits of the Gruntfile is Jenkins will run `grunt test` on every commit meaning we can get Jenkins automating quite a few things for us.\\n\\nMobileFrontend should also use it.\\n\\nOne of the benefits of this will be jscs running on every Jenkins build (currently this only runs in a pre commit hook)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416103527, 'spacePHID': None, 'dateCreated': 1414090680, 'dateModified': 1418074926, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72443', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'At nowiki the nowiki-tag shows up in some edits done with VisualEditor', 'description': {'raw': 'It seems like nowiki-tags show up at edits done at nowiki with VisualEditor.\\n\\nThe first of the two examples (https://no.wikipedia.org/w/index.php?title=Cologne_Business_School&diff=13473599&oldid=13473538) could be a copy-paste. If so it is an user error and the same as in Bug 68928 VisualEditor: Copy/pasting causes <nowiki> and <em> tags to appear.\\n\\nThe second edit seems to be different (https://no.wikipedia.org/w/index.php?title=Bergen&diff=prev&oldid=13467156) and I\\'m not sure what has happened here. Perhaps it is Bug 49820 - VisualEditor: When user types in \\'[[\\' in the page or another DOM input widget, pop up a reminder that they\\'re using VisualEditor. If this is the case the user has clicked through a warning (has it failed?) and still saved.\\n\\nThere is a thread at nowiki about this, https://no.wikipedia.org/wiki/Wikipedia:Torget#Tomme_nowiki-tagger (\"Empty nowiki-tags\")\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-vlni4mhyozor7ghqnfkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421377390, 'spacePHID': None, 'dateCreated': 1414090140, 'dateModified': 1532186597, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72442', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Misaligned \"Cancel\" and \"Ok\" button in the confirmation dialogs for abandoning edit and switching to Edit Source mode', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE using desktop Safari\\n2.Edit something on the page, click on the back button at the top left corner and observe the alignment of \"Ok\" and \"Cancel\" button in the confirmation dialog for abandoning edit\\n3.Click cancel and now click on the button to switch to the edit source mode from the Settings menu\\n\\n4.Observe the alignment of \"Ok\" and \"Cancel\" button in the confirmation dialog for switching to edit source mode\\n\\nObserved Result:\\nThe buttons are misaligned as seen in the screenshot attached\\n\\nEnvironment:\\nBetalabs, test2 and production\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14709}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415070112, 'spacePHID': None, 'dateCreated': 1414022820, 'dateModified': 1417570679, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72408', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Možná hledáte\" template on cs.wp not easy to use with VE', 'description': {'raw': 'While some templates are easy to use in VE, this is not. At first VE doesnt load automatically its parameters, at second you need to enter hyperling to its values, but VE doesnt offer tools for that.\\n\\nIts often used template which gives information, about subjects with the same title.\\n\\nhttps://cs.wikipedia.org/wiki/%C5%A0ablona:Mo%C5%BEn%C3%A1_hled%C3%A1te\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414021368, 'spacePHID': None, 'dateCreated': 1413870600, 'dateModified': 1417570682, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72293', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Some links to URLs are being displayed as red', 'description': {'raw': 'This may only be happening to links inside templates or refs.  \\n\\nSteps to reproduce:\\n\\n1.  Click on https://en.wikipedia.org/wiki/HOSxP?veaction=edit\\n\\n2.  Watch the URL in the infobox turn red.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413849744, 'spacePHID': None, 'dateCreated': 1413849660, 'dateModified': 1413849744, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72287', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ext.eventLogging.subscriber.js broken', 'description': {'raw': \"File: https://github.com/wikimedia/mediawiki-extensions-EventLogging/blob/master/modules/ext.eventLogging.subscriber.js\\n\\n\\nThe ext.eventLogging.subscriber.js has not worked since past April. Visual Editor editor was using it to submit its events to EL. \\n\\nWhile VE is removing usage of this class (as it really not needed on their case) we should either fix it or remove other usages of it. Sounds like its only usage on the codebase (besides Visual Editor's) is to report usage of deprecated javascript functions.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-mwkkwzbzlkvdl4w2og44', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415254977, 'spacePHID': None, 'dateCreated': 1413581220, 'dateModified': 1415254977, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72197', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE instrumentation is not showing up in databases', 'description': {'raw': \"VE has a variety of schemas[1] that are not correctly feeding into the EL databases. They need assistance in figuring out what's happening.\\n\\nDario suspects that the events are failing validation.\\n\\n[1] https://meta.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=VisualEditor&fulltext=Search&ns470=1&profile=advanced\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ud7f5gp5h3uqup6viq4e', 'ownerPHID': 'PHID-USER-vbyvvtbztxaeuaxelxx4', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vbyvvtbztxaeuaxelxx4', 'dateClosed': 1421079666, 'spacePHID': None, 'dateCreated': 1413517140, 'dateModified': 1421079666, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72173', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Moving the cursor with keyboard over a footnote number goes back and forth', 'description': {'raw': '1. Go to https://www.mediawiki.org/w/index.php?title=Manual:Coding_conventions/Ruby&redirect=no&veaction=edit (revision: https://www.mediawiki.org/w/index.php?title=Manual:Coding_conventions/Ruby&oldid=1226556 )\\n\\n2. Put the caret at the end of the second paragraph after \"staff\".\\n\\n3. Move the caret forward with the keyboard using the \"right arrow\" key repeatedly\\n\\nExpected: The caret must move forward through the three footnote numbers.\\n\\nObserved: The caret moves to the first reference and then back before it.\\n\\nThis is similar to bug T73550.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423676182, 'spacePHID': None, 'dateCreated': 1413473340, 'dateModified': 1438735449, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72137', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor[Regression wmf3]:Category context menu appears out of position.', 'description': {'raw': 'screenshot\\n\\nEnvironment- test2, beta\\n\\n1> Add a new category say- Japan.\\n2> select the category to delete it. Notice the context menu appears out of position.\\n\\nsee screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F15006}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413817416, 'spacePHID': None, 'dateCreated': 1413215220, 'dateModified': 1417570686, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71999', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Editing and saving a page , then pressing back browser button takes to previously saved page.', 'description': {'raw': 'Environment- test2\\n\\n1> In VE enter external link e.g- http://lowes.com . Save the page. Takes you to Read mode.\\n2> Select Edit tab again and Edit the external link to google.com. Save the page.\\n3> In the Read mode click on the external link to open the page. Navigates to google page. Now click on the back browser button. You would expect this to navigate you to the most recently saved page in VE , but click on the link and it opens lowes page . \\n4> Now click on Edit tab and it would show google.com as the link.\\n\\n\\nPage in VE with lowes.com ->edit and saved the page with google.com -> google.com(current page)\\n                                                                            \\n                                                                                                                                                  \\n                                                                                                                                                                                                                                                                                            \\nHit the back button.\\n\\nPage in VE with lowes.com(takes me here)  -> edit and saved the page with google.com (should have navigated here)-> google.com\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414104706, 'spacePHID': None, 'dateCreated': 1412959980, 'dateModified': 1417570677, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71917', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Annotations pull-down closes before scrolling it.', 'description': {'raw': 'Environment- test2, beta\\n\\nIn the Reference dialog and Media Settings Caption dialog, before even  I could scroll down the Annotations menu list and select the Language tool or Clear styling,  the pull-down closes, making it difficult to  apply them to existing content.\\n\\n\\nEnvironment-test2 only\\n\\nSimilarly, in the Transclusion dialog -> Add a Template field, when you start typing and the suggestion list is shown, before you could scroll the list, it closes, making it unusable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows XP'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415807863, 'spacePHID': None, 'dateCreated': 1412775960, 'dateModified': 1417570676, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71794', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikilinks with a final space', 'description': {'raw': 'This bug has been observed for a while on fr.wp and thus unofficially reported time ago, but now User:Drongou has kindly provided instructions to replicate it, so:\\n\\n1) Copy/paste something between square brackets, say [[2013]]\\n2) Place the cursor before the 3 and type 4, so that it becomes [[20143]]\\n3) Type a space, so it now looks like [[2014 3]]\\n4) Remove the 3 and save.\\n \\nThe result will be <nowiki>[[2014 ]]</nowiki>.\\nConfirmed at least on Safari 7.1, Mac OS-X 10.9 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412365997, 'spacePHID': None, 'dateCreated': 1412365620, 'dateModified': 1412365997, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71620', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor switcher isn't visible\", 'description': {'raw': \"Switcher icon not visible\\n\\nIn EditorOverlay the icon for the editor switcher (VE or Source) isn't visible (see attachment). You can still click/tap on the position and you can switch, but nobody know, that the switcher is there.\\n\\nReported first on https://www.mediawiki.org/wiki/Thread:Extension_talk:MobileFrontend/visualeditor_abandoned\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F15397}\"}, 'authorPHID': 'PHID-USER-c5xwrfdyp3dckkh2nkoj', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412361115, 'spacePHID': None, 'dateCreated': 1412337840, 'dateModified': 1412361115, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71608', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Give the user a chance to understand if he made a mistake and to fix it', 'description': {'raw': 'The author of this revision https://fr.wikipedia.org/w/index.php?title=La_Grange_au_Lac&diff=107837547&oldid=107804115 realizes that the wikicode he copy/pasted was not valid. The question is, does VE really need 5 nowiki tags to inform us? Can there be a good way of warning the user, maybe one which at the same time allows unexperienced editors to avoid saving and fix that mess?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'dateClosed': 1430414002, 'spacePHID': None, 'dateCreated': 1412014620, 'dateModified': 1439679273, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71422', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Letters getting added and duplicated on pages featuring chess templates', 'description': {'raw': 'See https://de.wikipedia.org/wiki/Benutzer:Elitre_(WMF)/sandbox?veaction=edit .\\nPlace your cursor after the last period of any section, and start typing. \\nThe first letter of your word will get added to the beginning of the following line.\\nHit Backspace; now the whole word appears there.\\nVerified also on en.wp on the Chess article.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51932'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416182820, 'spacePHID': None, 'dateCreated': 1411981620, 'dateModified': 1429477696, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71404', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In Firefox \"TypeError: this.$documentNode is undefined\" appears while selecting a citation note for a second time but not consecutively', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Insert 3 citation notes next to a text\\n2.Now select the 3rd one\\n3.Select the second one and edit it\\n4.Select the first one and edit it\\n5.Again select the 3rd one to edit it\\n\\n\\nObserved Result:\\n\"TypeError: this.$documentNode is undefined\" appears in the console.\\n\\nSee the screenshot attached.\\n\\nThis happens in Firefox only.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14758}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1424134428, 'spacePHID': None, 'dateCreated': 1411774380, 'dateModified': 1438735459, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71375', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The \"Use this group\" drop down box is getting cut off in Basic Reference dialog', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Cite>Basic \\n3.Open the drop down box for \"Use this group\"\\n\\n\\nObserved Result:\\nThe drop down box appears very small \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14754}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411772879, 'spacePHID': None, 'dateCreated': 1411772520, 'dateModified': 1417570687, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71374', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Visual editor screenshot job fails', 'description': {'raw': 'Most of the language jobs fail with the same errors. This is example for cs[1]. The parent job is [2].\\n\\n...\\n00:18:18.444 Failing Scenarios:\\n00:18:18.444 cucumber features/language_screenshot.feature:42 # Scenario: VisualEditor_Page_Settings\\n00:18:18.444 cucumber features/language_screenshot.feature:142 # Scenario: VisualEditor_cancel_save\\n...\\n\\n1: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox/LANGUAGE_SCREENSHOT_CODE=cs,label=contintLabsSlave%20&&%20UbuntuPrecise/5/console\\n2: https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox/\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412082716, 'spacePHID': None, 'dateCreated': 1411650900, 'dateModified': 1412082716, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71298', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"remove messages for features that aren't going to be developed\", 'description': {'raw': 'Some features of WikiEditor probably aren\\'t going to be developed much in the future. One such feature that I noticed is \"Side by side preview\". (I might actually be wrong, and this feature may be in development.)\\n\\nIf these features will no be developed further, the messages for them should be removed, because currently translators\\' time is wasted on them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'dateClosed': 1426443107, 'spacePHID': None, 'dateCreated': 1411637940, 'dateModified': 1459677128, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71287', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Template editor does not load', 'description': {'raw': 'Intention:\\nI tried to insert a template using VisualEditor when editing or creating pages on dewiki.\\n\\nSteps to Reproduce:\\n1. Enable Visual Editor in the Beta preferences\\n2. Open a random page on dewiki and edit it.\\n3. Click ‘Einfügen’ → ‘Vorlage’ (= ‘Insert’ → ‘Template’).\\n\\nActual Results:  \\nA pop-up opens, but does not load (title: ‘Laden …’ = ‘Loading …’). The pop-up cannot be closed (hitting ‘Abbrechen’ = ‘Cancel’ does not work), so the previous changes are lost.\\n\\nExpected Results:  \\nInstead the template editor should open normally.\\n\\nReproducible: Always\\n\\nUsing vector with Firefox 32.0 on Kubuntu 14.04.\\n\\nJS error (Firefox web console):\\nTypeError: queue is undefined ve.dm.MWTransclusionModel.js:136\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-valtn43cik2zouepilqb', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411481741, 'spacePHID': None, 'dateCreated': 1411479300, 'dateModified': 1417570687, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71175', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Citations appear broken for a few moments, before getting inserted in a Basic Reference dialog .', 'description': {'raw': 'Citations broken display\\n\\nEnvironment- Test2, beta, production\\n\\n1> Cite Basic -> Select to insert any citation(book/journal/news/website)\\n2> In the resulting modal, just click insert button.\\n3> Notice the citation appears broken momentarily and then gets added to the Reference editor.\\n\\nSee screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows XP\\n\\n**Attached**: {F14809}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415031297, 'spacePHID': None, 'dateCreated': 1410879600, 'dateModified': 1417570680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70884', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: {{lowercasetitle}} is not reflected in Display title in Advanced page settings', 'description': {'raw': \"The article [[iOS]] in the English Wikipedia has {{lowercasetitle}}, which is a wrapper for {{displaytitle}}.\\n\\nIt works correctly for display, but isn't shown in the Advanced settings dialog.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423674802, 'spacePHID': None, 'dateCreated': 1410854280, 'dateModified': 1423674802, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70880', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In Safari, Citation dialog opens with a weird animation and placing the cursor inside a parameter field enlarges it', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the citation dialog for an existing citation\\n3.Place the cursor on any field that has an input in it.\\n\\nObserved Result:\\nThe citation dialog opens with a weird animation and the first textbox appears much larger\\n\\n\\nSee the screenshot attached.\\n\\nEnvironment:Betalabs, test2 and production\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14782}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417577714, 'spacePHID': None, 'dateCreated': 1410822360, 'dateModified': 1438735463, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70872', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor[Regression wmf21] :New Section/Add Topic tab when first enabled/disabled,  gets added to the toolbar only after clicking on the Edit Source tab.', 'description': {'raw': 'New Section tab in Beta\\n\\nEnvironment-Production, Test2, beta\\n\\n1> Go to Advanced Settings and enable the “Show a tab on this page to add a new section” and apply changes.\\n2> Save the page.Switch back and forth between the Edit beta and Read tab, notice the new section/Add topic tab is not added to the Toolbar. It gets added only after clicking on Edit Source tab and then Edit beta tab.\\n3>Now  go back to Advanced Settings.Change the “Show a tab on this page to add a new section”  to No and apply changes.\\n4>Save the page.\\n5> Go back to the editor and notice the new section tab is still visible . And it is only when you click on the Edit source tab, that the New Section tab goes away from the Toolbar.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows XP\\n\\n**Attached**: {F14727}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410805042, 'spacePHID': None, 'dateCreated': 1410796380, 'dateModified': 1417570688, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70848', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] :  Citations deleted, are still shown in “Use  this group” suggestion list.', 'description': {'raw': 'References list\\n\\nEnvironment- Test2, beta\\n\\n1> Have at least 2 citations on the page.\\n2> Select Basic  -> Use an Existing Reference. The selected citation to re-use gets inserted on the page.\\n3> Now while the  re-used citation is still highlighted. Select “Basic” again and type in a name  in the “Use this group” input box.\\n4> Apply changes.\\n5> In the editor that citation gets replaced by the group name. Now delete all the citations from the page.\\n6> Select Insert -> References list. And click on the arrow in the “Use this Group” drop-down. Notice the group name assigned in step#3 is still visible in the suggestion list drop-down.\\n\\nSame thing happens when you try to access the “Use this group” in the basic citation.\\nSee screenshots.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F14722}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410804727, 'spacePHID': None, 'dateCreated': 1410793920, 'dateModified': 1417570688, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70847', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Category description not displayed after save', 'description': {'raw': 'I added a description to my new category https://en.wikipedia.org/wiki/Category:Conspiracy_theories_in_popular_culture using VisualEditor.\\n\\nAfter I saved the category page, my new description was not visible. I had to reload the page, and then it was displayed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-bug3zrlooz3bdmi4fyl7', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415046616, 'spacePHID': None, 'dateCreated': 1410675780, 'dateModified': 1415046616, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70821', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Moving an image in the document results in pixelated thumbnail', 'description': {'raw': \"## Steps\\n\\n1. Select an image node.\\n   https://www.mediawiki.org/wiki/VisualEditor:Basic_example_worksheet#Media_files\\n2. Resize a one of the small ones to be bigger. It'll fetch a large thumbnail momentarily.\\n3. Drag and drop the image to a different position in the surrounding paragraph.\\n\\n## Unexpected behaviour\\n\\nThe original image resource is re-used after a drag/drop, but now upscaled by the browser, thus pixelated. And no new thumb is fetched, either.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1424211837, 'spacePHID': None, 'dateCreated': 1410639060, 'dateModified': 1438735466, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70816', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Ugly span tags appear in Parsoid rendering of {{infobox book}}, but not in the saved wikitext, if ref tag is present', 'description': {'raw': \"Span tag as seen in Firefox\\n\\nhttps://en.wikipedia.org/wiki/Everyone_Poops?veaction=edit produces an ugly span tag above the infobox.  \\n\\nThe infobox is not displaying correctly at all in Safari, but in both Firefox and Safari it shows a long, large, bold-face span tag.  This appears to be caused by the <ref> tags.  See https://en.wikipedia.org/w/index.php?oldid=625300040 for a single-parameter infobox that causes the mess.\\n\\nThese span tags are not saved, so they don't corrupt the wikitext.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15303}\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416237485, 'spacePHID': None, 'dateCreated': 1410561720, 'dateModified': 1416237485, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70796', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  \"Clear styling\" is confusing.  If it\\'s going to clear links, too, then it should say, \"Clear styling and links\"', 'description': {'raw': 'If \"clear styling\" is going to clear links, too, then it should say, \"Clear styling and links\".  \\n\\n(I\\'d rather that it didn\\'t clear links, because, when I copy a link from another page, I want a way to get rid of character formatting and colors without killing the links, too.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410482044, 'spacePHID': None, 'dateCreated': 1410464640, 'dateModified': 1417570688, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70739', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Links to disambiguation pages should be highlighted in a different color', 'description': {'raw': 'This is related to bug 61072 and bug 50240.\\n\\nPlease consider marking all links to disambiguation pages in a different color, not just in the link inspector tool itself, but in the regular text that editors see when typing in VisualEditor.  This will help editors realize that there is something different (and probably wrong) with links that were previously added to the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410488331, 'spacePHID': None, 'dateCreated': 1410463440, 'dateModified': 1410488331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70738', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Language dialog box didn't draw correctly\", 'description': {'raw': \"Language dialog box, as it's not meant to be\\n\\nWhile testing on Meta, the language inspector did not open correctly.  It had some odd box drawing and no buttons.  See the screenshot.\\n\\n(This is not the problem described in bug 70731.  This oddly drawn box was the correct size.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15132}\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417480518, 'spacePHID': None, 'dateCreated': 1410461400, 'dateModified': 1438735467, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70733', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Saving produced a \"Something went wrong\" generic error message, but it silently and successfully saved the page', 'description': {'raw': 'User:Mike Christie made ten small (often single-character) edits to [[w:en:2002 Pacific typhoon season]] recently.  Edits #1 and #3 produced a generic error of \"Something went wrong\", and it appeared the save had failed.  \\n\\nIn both cases, the save worked.  The diffs are https://en.wikipedia.org/w/index.php?title=2002_Pacific_typhoon_season&diff=624878218&oldid=624550518 and https://en.wikipedia.org/w/index.php?title=2002_Pacific_typhoon_season&diff=next&oldid=624881675  None of the other, similar edits made to the article (including one in between these two) produced any errors. \\n\\nMike usually edits in Chrome on Windows 7.  I\\'ve seen the same behavior with a generic \"There was an error\" message in Firefox on Mac OS 10.8.5, so it\\'s probably affecting everything.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53093'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417568918, 'spacePHID': None, 'dateCreated': 1410457800, 'dateModified': 1417568918, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70726', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"vagrant up\" fails with \"The SSH command responded with a non-zero exit status.\"', 'description': {'raw': 'I am following quick start instructions[1] on a Mac.\\n\\n1. https://www.mediawiki.org/wiki/MediaWiki-Vagrant#Quick_start\\n\\n```\\n$ sw_vers -productVersion\\n10.9.4\\n\\n$ git --version\\ngit version 2.1.0\\n\\n$ vboxmanage --version\\n4.3.16r95972\\n\\n$ vagrant -v\\nVagrant 1.6.5\\n\\n$ git pull origin master\\nFrom ssh://gerrit.wikimedia.org:29418/mediawiki/vagrant\\n * branch            master     -> FETCH_HEAD\\nAlready up-to-date.\\n\\n$ git submodule update --init --recursive\\n\\n$ ./setup.sh\\nPlugin vagrant-vbguest is already installed\\nInstalling plugin mediawiki-vagrant-0.1.4.gem\\n- Installing the \\'mediawiki-vagrant-0.1.4.gem\\' plugin. This can take a few minutes...\\n- Installed the plugin \\'mediawiki-vagrant (0.1.4)\\'!\\nYou\\'re all set! Simply run `vagrant up` to boot your new environment.\\n\\n$ vagrant destroy\\n    default: Are you sure you want to destroy the \\'default\\' VM? [y/N] y\\n==> default: Removing puppet created files...\\n==> default: Destroying VM and associated drives...\\n==> default: Pruning invalid NFS exports. Administrator privileges will be required...\\nPassword:\\n==> default: Running cleanup tasks for \\'lsb_check\\' provisioner...\\n==> default: Running cleanup tasks for \\'puppet\\' provisioner...\\n\\n$ vagrant up\\nBringing machine \\'default\\' up with \\'virtualbox\\' provider...\\n==> default: Importing base box \\'trusty-cloud\\'...\\n==> default: Matching MAC address for NAT networking...\\n==> default: Setting the name of the VM: vagrant_default_1410428807331_61896\\n==> default: Clearing any previously set forwarded ports...\\n==> default: Clearing any previously set network interfaces...\\n==> default: Preparing network interfaces based on configuration...\\n    default: Adapter 1: nat\\n    default: Adapter 2: hostonly\\n==> default: Forwarding ports...\\n    default: 80 => 8080 (adapter 1)\\n    default: 22 => 2222 (adapter 1)\\n==> default: Running \\'pre-boot\\' VM customizations...\\n==> default: Booting VM...\\n==> default: Waiting for machine to boot. This may take a few minutes...\\n    default: SSH address: 127.0.0.1:2222\\n    default: SSH username: vagrant\\n    default: SSH auth method: private key\\n    default: Warning: Connection timeout. Retrying...\\n==> default: Machine booted and ready!\\nGuestAdditions versions on your host (4.3.16) and guest (4.3.10) do not match.\\nstdin: is not a tty\\n * Stopping VirtualBox Additions\\n   ...done.\\nstdin: is not a tty\\nReading package lists...\\nBuilding dependency tree...\\nReading state information...\\nThe following packages were automatically installed and are no longer required:\\n  dkms fakeroot gcc gcc-4.8 libasan0 libatomic1 libc-dev-bin libc6-dev\\n  libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libfakeroot libfontenc1\\n  libgcc-4.8-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgomp1\\n  libice6 libitm1 libllvm3.4 libpciaccess0 libpixman-1-0 libquadmath0 libsm6\\n  libtsan0 libtxc-dxtn-s2tc0 libx11-xcb1 libxaw7 libxcb-dri2-0 libxcb-dri3-0\\n  libxcb-glx0 libxcb-present0 libxcb-sync1 libxcomposite1 libxdamage1\\n  libxfixes3 libxfont1 libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1\\n  libxshmfence1 libxt6 libxxf86vm1 linux-libc-dev manpages-dev x11-common\\n  x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common\\n  xserver-xorg-core\\nUse \\'apt-get autoremove\\' to remove them.\\nThe following packages will be REMOVED:\\n  virtualbox-guest-dkms* virtualbox-guest-utils* virtualbox-guest-x11*\\n0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.\\nAfter this operation, 12.1 MB disk space will be freed.\\n(Reading database ... 60914 files and directories currently installed.)\\nRemoving virtualbox-guest-dkms (4.3.10-dfsg-1) ...\\n\\n-------- Uninstall Beginning --------\\nModule:  virtualbox-guest\\nVersion: 4.3.10\\nKernel:  3.13.0-30-generic (x86_64)\\n-------------------------------------\\n\\nStatus: Before uninstall, this module version was ACTIVE on this kernel.\\n\\nvboxguest.ko:\\n - Uninstallation\\n   - Deleting from: /lib/modules/3.13.0-30-generic/updates/dkms/\\n - Original module\\n   - No original module was found for this module on this kernel.\\n   - Use the dkms install command to reinstall any previous module version.\\n\\n\\nvboxsf.ko:\\n - Uninstallation\\n   - Deleting from: /lib/modules/3.13.0-30-generic/updates/dkms/\\n - Original module\\n   - No original module was found for this module on this kernel.\\n   - Use the dkms install command to reinstall any previous module version.\\n\\n\\nvboxvideo.ko:\\n - Uninstallation\\n   - Deleting from: /lib/modules/3.13.0-30-generic/updates/dkms/\\n - Original module\\n   - No original module was found for this module on this kernel.\\n   - Use the dkms install command to reinstall any previous module version.\\n\\ndepmod....\\n\\nDKMS: uninstall completed.\\n\\n------------------------------\\nDeleting module version: 4.3.10\\ncompletely from the DKMS tree.\\n------------------------------\\nDone.\\nRemoving virtualbox-guest-x11 (4.3.10-dfsg-1) ...\\nPurging configuration files for virtualbox-guest-x11 (4.3.10-dfsg-1) ...\\nRemoving virtualbox-guest-utils (4.3.10-dfsg-1) ...\\nPurging configuration files for virtualbox-guest-utils (4.3.10-dfsg-1) ...\\nProcessing triggers for man-db (2.6.7.1-1) ...\\nProcessing triggers for libc-bin (2.19-0ubuntu6) ...\\nstdin: is not a tty\\nReading package lists...\\nBuilding dependency tree...\\nReading state information...\\ndkms is already the newest version.\\ndkms set to manually installed.\\nlinux-headers-3.13.0-30-generic is already the newest version.\\nlinux-headers-3.13.0-30-generic set to manually installed.\\nThe following packages were automatically installed and are no longer required:\\n  libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libfontenc1 libgl1-mesa-dri\\n  libgl1-mesa-glx libglapi-mesa libice6 libllvm3.4 libpciaccess0 libpixman-1-0\\n  libsm6 libtxc-dxtn-s2tc0 libx11-xcb1 libxaw7 libxcb-dri2-0 libxcb-dri3-0\\n  libxcb-glx0 libxcb-present0 libxcb-sync1 libxcomposite1 libxdamage1\\n  libxfixes3 libxfont1 libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1\\n  libxshmfence1 libxt6 libxxf86vm1 x11-common x11-xkb-utils xfonts-base\\n  xfonts-encodings xfonts-utils xserver-common xserver-xorg-core\\nUse \\'apt-get autoremove\\' to remove them.\\n0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.\\nCopy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso\\nstdin: is not a tty\\nmount: block device /tmp/VBoxGuestAdditions.iso is write-protected, mounting read-only\\nInstalling Virtualbox Guest Additions 4.3.16 - guest version is 4.3.10\\nstdin: is not a tty\\nVerifying archive integrity... All good.\\nUncompressing VirtualBox 4.3.16 Guest Additions for Linux............\\nVirtualBox Guest Additions installer\\nCopying additional installer modules ...\\nInstalling additional modules ...\\nRemoving existing VirtualBox DKMS kernel modules ...done.\\nRemoving existing VirtualBox non-DKMS kernel modules ...done.\\nBuilding the VirtualBox Guest Additions kernel modules ...done.\\nDoing non-kernel setup of the Guest Additions ...done.\\nStarting the VirtualBox Guest Additions ...done.\\nInstalling the Window System drivers\\nCould not find the X.Org or XFree86 Window System, skipping.\\nAn error occurred during installation of VirtualBox Guest Additions 4.3.16. Some functionality may not work as intended.\\nIn most cases it is OK that the \"Window System drivers\" installation failed.\\nstdin: is not a tty\\n==> default: Checking for guest additions in VM...\\n==> default: Setting hostname...\\n==> default: Configuring and enabling network interfaces...\\n==> default: Exporting NFS shared folders...\\n==> default: Preparing to edit /etc/exports. Administrator privileges will be required...\\n==> default: Mounting NFS shared folders...\\n==> default: Mounting shared folders...\\n    default: /tmp/vagrant-puppet-5/manifests => /Users/z/Documents/wmf/mediawiki/vagrant/puppet/manifests\\n    default: /tmp/vagrant-puppet-5/modules-0 => /Users/z/Documents/wmf/mediawiki/vagrant/puppet/modules\\n==> default: Running provisioner: lsb_check...\\n==> default: Running provisioner: puppet...\\n==> default: Running Puppet with site.pp...\\n==> default: stdin: is not a tty\\n==> default: Notice: Compiled catalog for mediawiki-vagrant.dev in environment production in 2.88 seconds\\n==> default: Info: Applying configuration version \\'1410428953.no-git\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/multiversion-install]/ensure: created\\n==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/51-cloudguest]/ensure: removed\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/mwscript]/ensure: created\\n==> default: Notice: /Stage[main]/Main/File[/etc/apt/apt.conf.d/20shared-cache]/ensure: defined content as \\'{md5}711fa2f2a913db3990e7beb15cf57b5b\\'\\n==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/00-header]/ensure: removed\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/alldbs]/ensure: created\\n==> default: Notice: /Stage[main]/Misc/Exec[fix_root_profile]/returns: executed successfully\\n==> default: Info: mount[files]: allowing mediawiki-vagrant access\\n==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d]/group: group changed \\'root\\' to \\'vagrant\\'\\n==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/bash_completion.sh]/ensure: removed\\n==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/mediawiki-vagrant.sh]/ensure: defined content as \\'{md5}e9dcf6a1136af35370d9d8191cb11483\\'\\n==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/Z99-cloud-locale-test.sh]/ensure: removed\\n==> default: Notice: /Stage[main]/Apache/File[/var/www]/ensure: created\\n==> default: Notice: /Stage[main]/Main/File[/srv]/owner: owner changed \\'root\\' to \\'vagrant\\'\\n==> default: Notice: /Stage[main]/Main/File[/srv]/group: group changed \\'root\\' to \\'www-data\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/MWMultiVersion.php]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/defines.php]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/resources]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/missing.php]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/CREDITS]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/opensearch_desc.php]/ensure: defined content as \\'{md5}7c39985a7e1c410e006aeb5897548ee9\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/api.php]/ensure: defined content as \\'{md5}7c39985a7e1c410e006aeb5897548ee9\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/MWScript.php]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/thumb_handler.php]/ensure: defined content as \\'{md5}7c39985a7e1c410e006aeb5897548ee9\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/skins]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/thumb.php]/ensure: defined content as \\'{md5}7c39985a7e1c410e006aeb5897548ee9\\'\\n==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/10-help-text]/ensure: removed\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/index.php]/ensure: defined content as \\'{md5}7c39985a7e1c410e006aeb5897548ee9\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/dblist.php]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/usr/local/bin/foreachwiki]/ensure: created\\n==> default: Notice: /Stage[main]/Misc/File[/etc/profile.d/Z97-byobu.sh]/ensure: removed\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/img_auth.php]/ensure: defined content as \\'{md5}7c39985a7e1c410e006aeb5897548ee9\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/COPYING]/ensure: created\\n==> default: Notice: /Stage[main]/Mysql/File[/home/vagrant/.my.cnf]/ensure: defined content as \\'{md5}ef06fc0c2fb48af1df465c01df0f9634\\'\\n==> default: Notice: /Stage[main]/Motd/File[/etc/update-motd.d/50-landscape-sysinfo]/ensure: removed\\n==> default: Info: /etc/update-motd.d: Scheduling refresh of Exec[update_motd]\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/load.php]/ensure: defined content as \\'{md5}7c39985a7e1c410e006aeb5897548ee9\\'\\n==> default: Notice: /Stage[main]/Misc/Motd::Script[mediawiki_vagrant]/File[/etc/update-motd.d/50-mediawiki-vagrant]/ensure: defined content as \\'{md5}3aba016b0d0dda7268fcb1b655ea78f9\\'\\n==> default: Info: /Stage[main]/Misc/Motd::Script[mediawiki_vagrant]/File[/etc/update-motd.d/50-mediawiki-vagrant]: Scheduling refresh of Exec[update_motd]\\n==> default: Notice: /Stage[main]/Motd/Exec[update_motd]: Triggered \\'refresh\\' from 2 events\\n==> default: Notice: /Stage[main]/Php::Composer/Exec[download_composer]/returns: executed successfully\\n==> default: Notice: /Stage[main]/Php::Composer/File[/usr/local/bin/composer]/mode: mode changed \\'0644\\' to \\'0755\\'\\n==> default: Notice: /Stage[main]/Apt/File[/etc/apt/sources.list.d/multiverse.list]/ensure: defined content as \\'{md5}a4108116df82d5428debf4b06fbd0f54\\'\\n==> default: Notice: /Stage[main]/Apt/File[/usr/local/share/wikimedia-pubkey.asc]/ensure: defined content as \\'{md5}39e2c3119a82a59d706317fce97a6bfc\\'\\n==> default: Info: /Stage[main]/Apt/File[/usr/local/share/wikimedia-pubkey.asc]: Scheduling refresh of Exec[add_wikimedia_apt_key]\\n==> default: Notice: /Stage[main]/Apt/Exec[add_wikimedia_apt_key]: Triggered \\'refresh\\' from 1 events\\n==> default: Notice: /Stage[main]/Apt/File[/etc/apt/sources.list.d/wikimedia.list]/ensure: defined content as \\'{md5}81cc6c07729914e993ebf1829da0e002\\'\\n==> default: Notice: /Stage[main]/Apt/Exec[update_package_index]/returns: executed successfully\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/extensions]/ensure: created\\n==> default: Notice: /Stage[main]/Php::Composer/Env::Var[COMPOSER_CACHE_DIR]/File[/etc/profile.d/set_COMPOSER_CACHE_DIR.sh]/ensure: created\\n==> default: Notice: /Stage[main]/Main/File[/etc/apt/apt.conf.d/01no-recommended]/ensure: defined content as \\'{md5}53ce69211afabdf3f0123353515e80f4\\'\\n==> default: Notice: /Stage[main]/Main/Package[build-essential]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Misc/Package[ack-grep]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Main/Package[python-pip]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Main/Package[ruby-dev]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Misc/Package[htop]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Php::Remote_debug/Package[php5-xdebug]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Redis/Package[redis-server]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Main/Package[python-dev]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Main/Package[chef-zero]/ensure: removed\\n==> default: Notice: /Stage[main]/Mysql::Packages/Package[mysql-server]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Main/Package[chef]/ensure: removed\\n==> default: Notice: /Stage[main]/Redis/File[/srv/redis]/ensure: created\\n==> default: Notice: /Stage[main]/Apache::Mod::Php5/Package[libapache2-mod-php5]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Misc/File[/etc/ackrc]/ensure: defined content as \\'{md5}744cd26afe93f6ae5e3f04cee2bbc188\\'\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/envvars]/content: content changed \\'{md5}331419cf134c3cdce519b0d0f151cbc9\\' to \\'{md5}adf14ad862398d9eaab25c196ffb4f40\\'\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/envvars]/group: group changed \\'root\\' to \\'vagrant\\'\\n==> default: Info: /Stage[main]/Apache/File[/etc/apache2/envvars]: Scheduling refresh of Service[apache2]\\n==> default: Info: /Stage[main]/Apache/File[/etc/apache2/envvars]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Apache::Mod::Proxy_fcgi/Apache::Mod_conf[proxy_fcgi]/Exec[ensure_present_mod_proxy_fcgi]/returns: executed successfully\\n==> default: Info: /Stage[main]/Apache::Mod::Proxy_fcgi/Apache::Mod_conf[proxy_fcgi]/Exec[ensure_present_mod_proxy_fcgi]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/File[/var/www/favicon.ico]/ensure: defined content as \\'{md5}b1d335c7c87c3d9b0693db6a5dc69d7b\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/File[/var/www/info.php]/ensure: defined content as \\'{md5}fb92f9147037f47dcf29c96dbc68154d\\'\\n==> default: Notice: /Stage[main]/Php/Package[php5-mysql]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Php/Package[php5-gd]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Php/Package[php-apc]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Php/Package[php5-mcrypt]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Php/Package[php5]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Apache::Mod::Headers/Apache::Mod_conf[headers]/Exec[ensure_present_mod_headers]/returns: executed successfully\\n==> default: Info: /Stage[main]/Apache::Mod::Headers/Apache::Mod_conf[headers]/Exec[ensure_present_mod_headers]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Php/Package[php5-sqlite]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/sites-enabled/000-default.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Php/Package[php-pear]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Php/Package[php5-curl]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/env-enabled]/ensure: created\\n==> default: Info: /Stage[main]/Apache/File[/etc/apache2/env-enabled]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Php/Php::Ini[debug_output]/File[/etc/php5/mods-available/_debug_output.ini]/ensure: defined content as \\'{md5}d063cce793713a4e99892c1076fcaa4c\\'\\n==> default: Info: /Stage[main]/Php/Php::Ini[debug_output]/File[/etc/php5/mods-available/_debug_output.ini]: Scheduling refresh of Service[apache2]\\n==> default: Info: /Stage[main]/Php/Php::Ini[debug_output]/File[/etc/php5/mods-available/_debug_output.ini]: Scheduling refresh of Exec[/usr/sbin/php5enmod -s ALL _debug_output]\\n==> default: Notice: /Stage[main]/Php/Php::Ini[debug_output]/Exec[/usr/sbin/php5enmod -s ALL _debug_output]: Triggered \\'refresh\\' from 1 events\\n==> default: Notice: /Stage[main]/Php/Php::Ini[session_defaults]/File[/etc/php5/mods-available/_session_defaults.ini]/ensure: defined content as \\'{md5}7236471110ece2bbd4ff508af9030132\\'\\n==> default: Info: /Stage[main]/Php/Php::Ini[session_defaults]/File[/etc/php5/mods-available/_session_defaults.ini]: Scheduling refresh of Service[apache2]\\n==> default: Info: /Stage[main]/Php/Php::Ini[session_defaults]/File[/etc/php5/mods-available/_session_defaults.ini]: Scheduling refresh of Exec[/usr/sbin/php5enmod -s ALL _session_defaults]\\n==> default: Notice: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/File[/etc/php5/mods-available/_remote_debug.ini]/ensure: defined content as \\'{md5}f1115221d2629974b905dc37476797a1\\'\\n==> default: Info: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/File[/etc/php5/mods-available/_remote_debug.ini]: Scheduling refresh of Service[apache2]\\n==> default: Info: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/File[/etc/php5/mods-available/_remote_debug.ini]: Scheduling refresh of Exec[/usr/sbin/php5enmod -s ALL _remote_debug]\\n==> default: Info: /etc/apache2/sites-enabled: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Php::Composer/Exec[update_composer]/returns: executed successfully\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/security.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Php/Php::Ini[session_defaults]/Exec[/usr/sbin/php5enmod -s ALL _session_defaults]: Triggered \\'refresh\\' from 1 events\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/other-vhosts-access-log.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/env-available]/ensure: created\\n==> default: Info: /Stage[main]/Apache/File[/etc/apache2/env-available]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Php::Remote_debug/Php::Ini[remote_debug]/Exec[/usr/sbin/php5enmod -s ALL _remote_debug]: Triggered \\'refresh\\' from 1 events\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/serve-cgi-bin.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/security.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/localized-error-pages.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/other-vhosts-access-log.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-available/charset.conf]/ensure: removed\\n==> default: Info: /etc/apache2/conf-available: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/charset.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/localized-error-pages.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/sites-available/default-ssl.conf]/ensure: removed\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/ports.conf]/content: content changed \\'{md5}a961f23471d985c2b819b652b7f64321\\' to \\'{md5}832989c376f29c4740c3bc5eb9ed3f12\\'\\n==> default: Info: /Stage[main]/Apache/File[/etc/apache2/ports.conf]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/site-confs]/ensure: created\\n==> default: Info: /Stage[main]/Apache/File[/etc/apache2/site-confs]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/conf-enabled/serve-cgi-bin.conf]/ensure: removed\\n==> default: Info: /etc/apache2/conf-enabled: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Mysql/Exec[set_mysql_password]/returns: executed successfully\\n==> default: Notice: /Stage[main]/Role::Mediawiki/Package[tidy]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Role::Mediawiki/Package[php5-tidy]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Redis/File[/etc/redis/redis.conf]/content: content changed \\'{md5}e79ac99a5236e6ab3faf86bdd99affaf\\' to \\'{md5}dedc5a2ff609b5cceadc08307646ad54\\'\\n==> default: Info: /Stage[main]/Redis/File[/etc/redis/redis.conf]: Scheduling refresh of Service[redis-server]\\n==> default: Notice: /Stage[main]/Redis/Service[redis-server]: Triggered \\'refresh\\' from 1 events\\n==> default: Notice: /Stage[main]/Redis::Php/Package[php5-redis]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Info: /Stage[main]/Redis::Php/Package[php5-redis]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Hhvm/File[/usr/local/bin/hhvmsh]/ensure: defined content as \\'{md5}db1312e407c8fb05c1fb193692ce5c2f\\'\\n==> default: Notice: /Stage[main]/Hhvm/File[/etc/hhvm]/ensure: created\\n==> default: Notice: /Stage[main]/Hhvm/Package[hhvm]/ensure: ensure changed \\'purged\\' to \\'latest\\'\\n==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-dev]/ensure: ensure changed \\'purged\\' to \\'latest\\'\\n==> default: Notice: /Stage[main]/Hhvm/File[/etc/hhvm/php.ini]/content: content changed \\'{md5}38e0be69fb5da2bebc90f17f7fe3c705\\' to \\'{md5}ef2004ca4a64aea1d212962c34738666\\'\\n==> default: Info: /Stage[main]/Hhvm/File[/etc/hhvm/php.ini]: Scheduling refresh of Service[hhvm]\\n==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/File[/etc/apache2/site-confs/hhvm-admin]/ensure: created\\n==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-luasandbox]/ensure: ensure changed \\'purged\\' to \\'latest\\'\\n==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-wikidiff2]/ensure: ensure changed \\'purged\\' to \\'latest\\'\\n==> default: Notice: /Stage[main]/Hhvm/File[/etc/hhvm/config.hdf]/ensure: defined content as \\'{md5}2a46fb84966afc8fc3b51fd9abe57378\\'\\n==> default: Info: /Stage[main]/Hhvm/File[/etc/hhvm/config.hdf]: Scheduling refresh of Service[hhvm]\\n==> default: Notice: /Stage[main]/Hhvm/Package[hhvm-fss]/ensure: ensure changed \\'purged\\' to \\'latest\\'\\n==> default: Notice: /Stage[main]/Hhvm/File[/etc/init/hhvm.conf]/content: content changed \\'{md5}48267cf8f84fd68070699cf68ce7f663\\' to \\'{md5}329e085674306cc428a3440a0916b40f\\'\\n==> default: Info: /Stage[main]/Hhvm/File[/etc/init/hhvm.conf]: Scheduling refresh of Service[hhvm]\\n==> default: Notice: /Stage[main]/Hhvm/Service[hhvm]/ensure: ensure changed \\'stopped\\' to \\'running\\'\\n==> default: Info: /Stage[main]/Hhvm/Service[hhvm]: Unscheduling refresh on Service[hhvm]\\n==> default: Notice: /Stage[main]/Php/Package[php5-intl]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/File[/etc/apache2/site-confs/hhvm-admin/00-default.conf]/ensure: created\\n==> default: Notice: /Stage[main]/Apache/File[/etc/apache2/sites-available/000-default.conf]/ensure: removed\\n==> default: Info: /etc/apache2/sites-available: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Git/Package[git]/ensure: ensure changed \\'purged\\' to \\'latest\\'\\n==> default: Notice: /Stage[main]/Git/Package[git-review]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/tests]/ensure: created\\n==> default: Notice: /Stage[main]/Php/Package[php5-readline]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Misc/File[/usr/local/sbin/isfresh]/ensure: defined content as \\'{md5}6fee8323b6bdd6afc7c37faa4491794a\\'\\n==> default: Notice: /Stage[main]/Apache/Misc::Evergreen[apache2]/Exec[check_apache2_freshness]/returns: executed successfully\\n==> default: Info: /Stage[main]/Apache/Misc::Evergreen[apache2]/Exec[check_apache2_freshness]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/var/www/w/MWVersion.php]/ensure: created\\n==> default: Notice: /Stage[main]/Php/Package[php5-dev]/ensure: ensure changed \\'purged\\' to \\'present\\'\\n==> default: Notice: /Stage[main]/Mediawiki/File[/usr/local/bin/run-mediawiki-tests]/ensure: defined content as \\'{md5}cb1918d4464e50c256399b91c411bb05\\'\\n==> default: Notice: /Stage[main]/Mediawiki/File[/usr/local/bin/import-mediawiki-dump]/ensure: defined content as \\'{md5}81874e61ef7c14f0a5b1aa87a337cfbb\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/vagrant/settings.d/wikis]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki/File[/var/cache/mediawiki]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/vagrant/settings.d/wikis/LoadWgConf.php]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki/File[/usr/local/bin/run-git-update]/ensure: defined content as \\'{md5}5ff218ed45bf3ea414f9c4776e9210d2\\'\\n==> default: Notice: /Stage[main]/Mediawiki/Env::Profile_script[add mediawiki vendor bin to path]/File[/etc/profile.d/50-add-mediawiki-vendor-bin-to-path.sh]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki/Env::Var[MW_INSTALL_PATH]/File[/etc/profile.d/set_MW_INSTALL_PATH.sh]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Multiwiki/File[/vagrant/settings.d/wikis/CommonSettings.php]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/jobrunner.json]/ensure: defined content as \\'{md5}670966939c990598a91362cb0ffb75ac\\'\\n==> default: Info: /Stage[main]/Mediawiki::Jobrunner/File[/etc/jobrunner.json]: Scheduling refresh of Service[jobrunner]\\n==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/default/jobrunner]/ensure: defined content as \\'{md5}baefee683608d285b2c4895c8f76c563\\'\\n==> default: Info: /Stage[main]/Mediawiki::Jobrunner/File[/etc/default/jobrunner]: Scheduling refresh of Service[jobrunner]\\n==> default: Notice: /Stage[main]/Mediawiki/File[/srv/images]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: Composer could not find a composer.json file in /vagrant/mediawiki\\n==> default: Notice: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: To initialize a project, please create a composer.json file as described in the http://getcomposer.org/ \"Getting Started\" section\\n==> default: Error: composer install --optimize-autoloader returned 1 instead of one of [0]\\n==> default: Error: /Stage[main]/Mediawiki/Php::Composer::Install[/vagrant/mediawiki]/Exec[composer-install--vagrant-mediawiki]/returns: change from notrun to 0 failed: composer install --optimize-autoloader returned 1 instead of one of [0]\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/wgConf.php]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/dbConf.php]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki/File[mediawiki_upstart_bridge]/ensure: defined content as \\'{md5}b1cfb3aa1f75ada7780442b4a8a1ca76\\'\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/settings.d]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/settings.d/puppet-managed]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/File[/vagrant/settings.d/wikis/wiki/settings.d/puppet-managed/README]/ensure: defined content as \\'{md5}64ae42537fb40c737e432f1e747355f7\\'\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_setup]/returns: executed successfully\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Wiki[devwiki]/Exec[wiki_include_extra_settings]/returns: executed successfully\\n==> default: Notice: /Stage[main]/Mediawiki/Exec[copy_LocalSettings]/returns: executed successfully\\n==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/logrotate.d/mediawiki_jobrunner]/ensure: defined content as \\'{md5}108922f7a7305cd4f69202fa6ba6d2ee\\'\\n==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Git::Clone[mediawiki/services/jobrunner]/Exec[git_clone_mediawiki/services/jobrunner]/returns: executed successfully\\n==> default: Info: Git::Clone[mediawiki/services/jobrunner]: Scheduling refresh of Exec[git_install_checkout_mediawiki/services/jobrunner]\\n==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Exec[git_install_reset_mediawiki/services/jobrunner]/returns: executed successfully\\n==> default: Info: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Exec[git_install_reset_mediawiki/services/jobrunner]: Scheduling refresh of Exec[git_install_checkout_mediawiki/services/jobrunner]\\n==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Git::Install[mediawiki/services/jobrunner]/Exec[git_install_checkout_mediawiki/services/jobrunner]: Triggered \\'refresh\\' from 2 events\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: fatal: destination path \\'/vagrant/mediawiki/skins/Vector\\' already exists and is not an empty directory.\\n==> default: Error: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]\\n==> default: Error: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Git::Clone[mediawiki/skins/Vector]/Exec[git_clone_mediawiki/skins/Vector]/returns: change from notrun to 0 failed: git clone --recurse-submodules   https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector.git /vagrant/mediawiki/skins/Vector returned 128 instead of one of [0]\\n==> default: Notice: /Stage[main]/Mediawiki/File[/var/www/mediawiki-vagrant.png]/ensure: defined content as \\'{md5}f9afb7d19e39247820bc1e81883a96f7\\'\\n==> default: Notice: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Dependency Exec[git_clone_mediawiki/skins/Vector] has failures: true\\n==> default: Warning: /Stage[main]/Mediawiki/Mediawiki::Skin[Vector]/Mediawiki::Settings[Vector]/File[/vagrant/settings.d/puppet-managed/10-Vector.php]: Skipping because of failed dependencies\\n==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/File[/etc/init/jobrunner.conf]/ensure: defined content as \\'{md5}e2302b512e81c3d406f8f2159dd4dbcd\\'\\n==> default: Info: /Stage[main]/Mediawiki::Jobrunner/File[/etc/init/jobrunner.conf]: Scheduling refresh of Service[jobrunner]\\n==> default: Notice: /Stage[main]/Mediawiki::Jobrunner/Service[jobrunner]/ensure: ensure changed \\'stopped\\' to \\'running\\'\\n==> default: Info: /Stage[main]/Mediawiki::Jobrunner/Service[jobrunner]: Unscheduling refresh on Service[jobrunner]\\n==> default: Notice: /Stage[main]/Apache::Mod::Rewrite/Apache::Mod_conf[rewrite]/Exec[ensure_present_mod_rewrite]/returns: executed successfully\\n==> default: Info: /Stage[main]/Apache::Mod::Rewrite/Apache::Mod_conf[rewrite]/Exec[ensure_present_mod_rewrite]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Apache/Apache::Conf[disable sendfile]/File[/etc/apache2/conf-available/50-disable-sendfile.conf]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/Apache::Conf[devwiki]/File[/etc/apache2/sites-available/50-devwiki.conf]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/Apache::Conf[devwiki]/File[/etc/apache2/sites-enabled/50-devwiki.conf]/ensure: created\\n==> default: Info: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/Apache::Conf[devwiki]/File[/etc/apache2/sites-enabled/50-devwiki.conf]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/Apache::Conf[php5-devwiki]/File[/etc/apache2/sites-available/50-php5-devwiki.conf]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/Apache::Conf[php5-devwiki]/File[/etc/apache2/sites-enabled/50-php5-devwiki.conf]/ensure: created\\n==> default: Info: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/Apache::Conf[php5-devwiki]/File[/etc/apache2/sites-enabled/50-php5-devwiki.conf]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/File[/etc/apache2/site-confs/php5-devwiki]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[php5-devwiki]/File[/etc/apache2/site-confs/php5-devwiki/00-default.conf]/ensure: created\\n==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/Apache::Conf[hhvm-admin]/File[/etc/apache2/sites-available/50-hhvm-admin.conf]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/File[/etc/apache2/site-confs/devwiki]/ensure: created\\n==> default: Notice: /Stage[main]/Mediawiki::Apache/Apache::Site[devwiki]/File[/etc/apache2/site-confs/devwiki/00-default.conf]/ensure: created\\n==> default: Notice: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/Apache::Conf[hhvm-admin]/File[/etc/apache2/sites-enabled/50-hhvm-admin.conf]/ensure: created\\n==> default: Info: /Stage[main]/Hhvm/Apache::Site[hhvm_admin]/Apache::Conf[hhvm-admin]/File[/etc/apache2/sites-enabled/50-hhvm-admin.conf]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Apache/Apache::Conf[disable sendfile]/File[/etc/apache2/conf-enabled/50-disable-sendfile.conf]/ensure: created\\n==> default: Info: /Stage[main]/Apache/Apache::Conf[disable sendfile]/File[/etc/apache2/conf-enabled/50-disable-sendfile.conf]: Scheduling refresh of Service[apache2]\\n==> default: Notice: /Stage[main]/Apache/Service[apache2]: Triggered \\'refresh\\' from 22 events\\n==> default: Info: Creating state file /var/lib/puppet/state/state.yaml\\n==> default: Notice: Finished catalog run in 180.74 seconds\\nThe SSH command responded with a non-zero exit status. Vagrant\\nassumes that this means the command failed. The output for this command\\nshould be in the log above. Please read the output to determine what\\nwent wrong.\\n```'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410524423, 'spacePHID': None, 'dateCreated': 1410429960, 'dateModified': 1458708362, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70705', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Media search not working in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Media\\n3.Enter something in the search box to search for images\\n\\n\\nObserved Result:\\n\\nNothing happens. \"No Results\" found message stays in the dialog instead\\n\\nEnvironment:Betalabs\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14832}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410302702, 'spacePHID': None, 'dateCreated': 1410289080, 'dateModified': 1417570689, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70621', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The Field description popup looks weird on mediawiki.org', 'description': {'raw': 'Field description popup for template:Bugzilla on mediawiki.org\\n\\nSee attachment. A lot of wasted empty space, and a scrollbar :) Possibly related to other reports, or a dupe.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70423\\n\\n**Attached**: {F14777}'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410356188, 'spacePHID': None, 'dateCreated': 1410258120, 'dateModified': 1410356188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70604', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The References List dialog looks too big, much unnecessary empty space', 'description': {'raw': 'References list trying to impress us\\n\\nSee screenshot (which was taken in IE), I tried with other browsers and it looked the same there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68226\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70423\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70016\\n\\n**Attached**: {F14773}'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414137121, 'spacePHID': None, 'dateCreated': 1410253440, 'dateModified': 1414137121, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70601', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The link inspector and comment box are appearing with no UI while opening them after an idle time', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Keep it open for a while (~10-15 mins)\\n3.After coming back to this page, open a link inspector or a comment box \\n\\nObserved Result:\\nThey open with no UI, see the screenshot attached.\\n\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61078\\n\\n**Attached**: {F14719}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1419349413, 'spacePHID': None, 'dateCreated': 1410209040, 'dateModified': 1419349413, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70580', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link icon stays selected but is not inserted, with language style text.', 'description': {'raw': 'screenshot\\n\\nEnvironment- test2, beta\\n\\n1> open a page in VE, insert some text. Open the language inspector and click on link icon.\\n2> Now click anywhere on the Editor and type in some more text, the language inspector closes but the link icon stays selected.See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows XP\\n\\n**Attached**: {F14676}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415643662, 'spacePHID': None, 'dateCreated': 1410192240, 'dateModified': 1417570677, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70562', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Bad things happen when you paste cruft-laden text from somewhere else', 'description': {'raw': 'An editor pasted text at the newly created https://en.wikipedia.org/w/index.php?title=Kalles_Fraktaler&oldid=624532595\\n\\nwhich resulted in this when the page was saved:\\n\\n<object type=\"cosymantecnisbfw\" cotype=\"cs\" id=\"cosymantecnisbfw\" style=\"width: 0px; height: 0px; display: block;\"></object><object type=\"cosymantecnisbfw\" cotype=\"bgpage\" id=\"cosymantecnisbfwbg\" style=\"width: 0px; height: 0px; display: block;\"></object><script type=\"text/javascript\" defer=\"defer\" id=\"NortonInternetSecurityBF\" tab=\"0\" browser=\"0\">function NavigateTo(url, newWindow) { var myObject = new Object(); myObject.url = url; myObject.newWindow = newWindow; theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'symcBFNavigateTo\\', false, false, myObject); document.dispatchEvent(theEvent); } function ChangeToolbarIcon(inText, inImage) { var myObject = new Object(); myObject.text = inText; myObject.image = inImage; theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'changeToolbarIconEventHandler\\', false, false, myObject); document.dispatchEvent(theEvent); } function DimPage() { dimElement = document.createElement(\\'div\\'); dimElement.id = \\'coShastaDimDiv\\'; dimElement.style.cssText = \\'z-index:10;width:100%;height:100%;background-color:black;opacity:0.60;position:absolute;top:0;left:0;\\'; var theBody = document.getElementsByTagName(\\'body\\')[0]; theBody.appendChild(dimElement); } function NPNNew() { theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'symcBFActivate\\', false, false, 0); document.dispatchEvent(theEvent); } function UpdatePageStatus(inURL) { var myObject = new Object(); myObject.blockURL = inURL; theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'updatePageStatusEventHandler\\', false, false, myObject); document.dispatchEvent(theEvent);}function UpdateToolbarMenu(inSafeSearch) { var myObject = new Object(); myObject.SafeSearch = inSafeSearch; theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'updateToolbarMenuEventHandler\\', false, false, myObject); document.dispatchEvent(theEvent);}function SetBarVisibility(barstatus) { var myObject = new Object(); myObject.barstatus = barstatus; theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'setBarVisibilityEventHandler\\', false, false, myObject); document.dispatchEvent(theEvent);}function SetCachedStrings(inText, inImage, inTextNA, inImageNA) { var myObject = new Object(); myObject.text = inText; myObject.image = inImage; myObject.textNA = inTextNA; myObject.imageNA = inImageNA; theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'setCachedStringsEventHandler\\', false, false, myObject); document.dispatchEvent(theEvent); } function SetResourceFolder(inFolder) { var myObject = new Object(); myObject.resFolder = inFolder; theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'setResourceFolderEventHandler\\', false, false, myObject); document.dispatchEvent(theEvent); } function SetSafeSearchValues(isSSEinPrefs, isSSEinSafeMgr,isBuzz, showMyAccount) { var myObject = new Object(); myObject.showMyAccount = showMyAccount; myObject.isSSEinPrefs = isSSEinPrefs; myObject.isBuzz=isBuzz; myObject.isSSEinSafeMgr=isSSEinSafeMgr; theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'setSafeSearchValuesEventHandler\\', false, false, myObject); document.dispatchEvent(theEvent); } function ShowSafeSearchOffering() {theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'symcShowSafeSearchOffering\\', false, false, 0); document.dispatchEvent(theEvent); } function SafeSearchOfferResponded() {theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'symcSafeSearchOfferResponded\\', false, false, 0); document.dispatchEvent(theEvent); } function SetSearchString(inQuery) { var myObject = new Object(); myObject.query = inQuery; theEvent = document.createEvent(\\'CustomEvent\\'); theEvent.initCustomEvent(\\'symcSetSearchString\\', false, false, myObject); document.dispatchEvent(theEvent); } </script><object type=\"cosymantecnisbfw\" cotype=\"cs\" id=\"SILOBFWOBJECTID\" style=\"width: 0px; height: 0px; display: block;\"></object> Kalles Fraktaler is a Windows-based fractal zoom computer program used for zooming into the Mandelbrot set or the Burning Ship fractal. <object type=\"cosymantecnisbfw\" cotype=\"cs\" id=\"SILOBFWOBJECTID\" style=\"width: 0px; height: 0px; display: block;\"></object>\\n\\ncosymantecnisbfw appears to be related to NortonInternetSecurityBF\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410130325, 'spacePHID': None, 'dateCreated': 1410129540, 'dateModified': 1410130325, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70537', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf21]TypeError: boundingRect is undefined and TypeError: surfaceRect is undefined appears when opening Media Settings dialog', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Media\\n\\nObserved Result:\\nThe following errors are appearing in the console:\\n\\n\\nTypeError: boundingRect is undefined\\n\\nTypeError: surfaceRect is undefined\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15082}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409952276, 'spacePHID': None, 'dateCreated': 1409946720, 'dateModified': 1417570754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70455', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Style texts when selected with Language inspector open, turns the drop-down selection blank.', 'description': {'raw': 'screenshot1\\n\\n1> open a blank page in VE, open the Language inspector. \\n2> Now click anywhere in the Editor, the inspector stays open but the language style text drop-down selection turns blank. After that any selection you make, it continues to stay blank. And if you type in any text, a pawn gets inserted beside the text. See screenshots.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F15074}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415143058, 'spacePHID': None, 'dateCreated': 1409943780, 'dateModified': 1417570679, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70451', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: comment feature should be removed by default', 'description': {'raw': '<!-- comments are not recommended for users: it is hidden!  -->\\n\\nComments aren\\'t recommended for new editors (and for 99% of the times for advanced users too), as must comments should be written in talk page.\\n\\nIt is not just a non useful feature, it is a harmful feature, as people get confused between reference and comments and it leads to \"too many icons\" problem. Please remove comment button from toolbar completely, or at least change it to opt-in/out feature.  (Only the toolbar icon, as the option to show and edit already written comments is important)\\n\\nSide benefit: less code to maintain and less bugs ;)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-cfsvvgbtlqnbt2yokfjf', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410198549, 'spacePHID': None, 'dateCreated': 1409923860, 'dateModified': 1417570754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70440', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'BetaFeatures should have means to provide a custom note on-wiki', 'description': {'raw': \"**Author:** `gryllida`\\n\\n**Description:**\\nI'd like to enable a new beta feature on a wiki, but I wouldn't like the users to enable it thoughtlessly, as it currently breaks a lot of things. For this reason, I'd like to be able to append a 'do NOT use this! only for developers' note to such beta feature in the beta tab.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409950426, 'spacePHID': None, 'dateCreated': 1409922720, 'dateModified': 1410060066, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70438', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor bugs: wikilinks, tables, nowiki and other', 'description': {'raw': 'VisualEditor editor is full of bugs. Since his implementation i have disabled it for me, because, as experimented user i just like to edit clean code.\\nSo, i noticed folowing bugs\\nwhen you edit a part of a wikilink (termination) visual editor leaves old wikilink as adrress and only add new edited variant as label. For example if you want to correct digit of an wikilinked year - your action will just add a correct label but wikilink will be the same, old.\\nI first noticed this on rowiki when anonymous users edited wikipedia. One fresh example can be this https://ro.wikipedia.org/w/index.php?title=Gustar_%28festival%29&diff=8812463&oldid=8805982\\nNow i tested myself this \"phenomenon\" on test2wiki and i obtained the same result\\nhttps://test2.wikipedia.org/w/index.php?title=Edit_page_for_firefox&diff=104063&oldid=104062\\n\\nOther bug: when you try to remove title of a section from a page (for merging 2 sections), visual editor removes only caption but it keeps the real section heading (====) and adds between equal sign an \"<nowiki/>\". The result will be ==<nowiki/>== and section will exist further without title. Test edit: https://test2.wikipedia.org/w/index.php?title=New_page_for_bugzilla&diff=104066&oldid=104065\\n\\nAlso there exists some problems when copying of tables in a page edited via VisualEditor. VisualEditor adds again some <nowiki> </nowiki> tags, and in some cases adds magic words like __INDEX__ and __NEWSECTIONLINK__\\nExample (real edit on rowiki): https://ro.wikipedia.org/w/index.php?title=Kiesza&diff=next&oldid=8808818\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kzriyxckmvupw2nlyshe', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410804889, 'spacePHID': None, 'dateCreated': 1409835300, 'dateModified': 1419347343, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70396', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Do not permit empty section headings (wikitext like == == or similar)', 'description': {'raw': \"Sometimes users set the format of a line to be a == Section heading ==, but never put anything in it.  In that case, the section heading formatting should be removed.  There's no good reason to have == == or === === by itself on a line.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415886608, 'spacePHID': None, 'dateCreated': 1409787120, 'dateModified': 1415886608, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70368', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Page Options Dialog width is not wide enough', 'description': {'raw': '**Author:** `josephsieh`\\n\\n**Description:**\\nOn http://en.wikipedia.beta.wmflabs.org/wiki/Cite_VisualEditor_Test?veaction=edit, when you click on the \"Page Options\" icon, the pop-up page options dialog appears to be too narrow.  Characters are missing.\\n\\nOS X 10.9.4.\\nSafari 7.0.6\\nFirefox 32.0\\n\\nvisual editor version: https://git.wikimedia.org/tree/mediawiki%2Fextensions%2FVisualEditor.git/bfbe8cbbebe0a461d0ee68c0491b901507636fe2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409767558, 'spacePHID': None, 'dateCreated': 1409704920, 'dateModified': 1417570755, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70316', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Adding a template to a redirect did not let me save the page', 'description': {'raw': \"Steps taken:\\n\\n1.  Open a redirect to edit.\\n\\n2.  Add a template:  {{R from other languages}}\\n\\n3.  Discover that I can't save.  The green 'save' button is still gray and non-functional.\\n\\n4.  Mash the keyboard to add some text to the page.  \\n\\n5.  Still can't save.  Give up and cancel the edit.\\n\\n\\nThis happened in Firefox on my Mac; when I closed the page and tried again, it worked correctly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423675003, 'spacePHID': None, 'dateCreated': 1409696880, 'dateModified': 1438735471, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70305', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  When image search results are returned very slowly, remove the \"No results found\" error message', 'description': {'raw': '\"No results found\" overlaps with the results that were found\\n\\nSteps to reproduce:\\n\\n1.  Open VisualEditor and Insert > Media\\n\\n2.  Search for File:Alf Cooke\\'s Packaging Factory - Hunslet Road - geograph.org.uk - 483165.jpg \\n\\n3.  Nothing happens:  \"No results found\".\\n\\n4.  Spend a few moments grumbling about the stupidity of a search tool that cannot find a file even when you give it the complete and exact file name.\\n\\n5.  Spend a few moments groaning because there\\'s no way to add this image unless the search tool can find it, even when you know the exact file name.\\n\\n6.  Hey!  Search finally found the image!  Why does VisualEditor still say \"No results found\" on top of the results?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F14693}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409669754, 'spacePHID': None, 'dateCreated': 1409620980, 'dateModified': 1424894575, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70273', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: inserted special characters doesn't respect the surrounding text formatting\", 'description': {'raw': 'To reproduce:\\n\\n1. Write text. Make it bold.\\n2. Put the caret in the middle of the bold text.\\n3. Insert a special character.\\n\\nActual: The inserted character is not bold.\\n\\nExpected: The inserted character is bold like the surrounding text.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409596086, 'spacePHID': None, 'dateCreated': 1409595060, 'dateModified': 1417570757, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70265', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Be able to copy the name of an image', 'description': {'raw': 'Sometimes you want to re-use an image (or otherwise need to know its name).  Some file names are too long to display in the tab.  It would be nice if something in the media dialog box exposed the name of the file, so that it could be copied.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420461463, 'spacePHID': None, 'dateCreated': 1409542860, 'dateModified': 1424894569, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70244', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Link target choice box scroll bar does not work', 'description': {'raw': 'If VisualEditor is used to introduce a link (Ctrl-K) and the list of suggested link targets is long enough to require a scroll bar, this scroll bar cannot be used: clicking on it immediately closes the target list.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows 7'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415807855, 'spacePHID': None, 'dateCreated': 1409432400, 'dateModified': 1417570677, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70218', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Incorrect highlight while trying to add reference in a slug', 'description': {'raw': 'Screenshot\\n\\nThe highlight that appears after inserting a reference in a slug is pretty weird.\\n\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14232}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1423749557, 'spacePHID': None, 'dateCreated': 1409086200, 'dateModified': 1438735471, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70065', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Hung while trying to save', 'description': {'raw': 'This edit was actually saved, but it seemed like it wouldn\\'t be at the time:  https://en.wikipedia.org/w/index.php?title=Integrated_circuit&diff=622517186&oldid=622152913\\n\\n\\nThe report was this:\\n\\nError saving to server: Empty server response\\n\\nHangs when editing \"Integrated circuit\" page - section SSI, MSI and LSI - tried to remove redirect wikilinks to SSI, MSI and LSI (keywords). Chrome 36.0.1985.143 m, Win7 64bit Kozuch (talk) 21:08, 23 August 2014 (UTC)\\n\\nHi, I see my edit was saved, but probably was later than what my patience allowed me to wait for :). I was looking at page history before cancelling the edit save, but it was not there, probably shower up later. VE interaction definitely ended up deadly though (hung on the \"saving\" dialog and when I canceled it the above error just was quickly show and then dialog closed by itself.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1513167493, 'spacePHID': None, 'dateCreated': 1409007600, 'dateModified': 1513167493, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70010', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'bits.beta.wmflabs.org down with 503', 'description': {'raw': 'http://bits.beta.wmflabs.org is entirely down with 503.  E.g.:\\n\\nhttp://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=true&lang=en&modules=ext.visualEditor.viewPageTarget.noscript&only=styles&skin=vector&*\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409777765, 'spacePHID': None, 'dateCreated': 1408737480, 'dateModified': 1420738470, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69921', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Language selector should be able to use div', 'description': {'raw': 'Currently language selector adds <span lang=\"..\" dir=\"...\"> which is good for multiple words. However, sometimes longer text such as [few] paragraphs, lists etc should be makred as different language, and in this case it should wrap it with div.\\n\\nExample: https://he.wikipedia.org/wiki/%D7%A9%D7%9E%D7%A2%D7%95%D7%9F_%D7%90%D7%95%D7%9C%D7%9E%D7%9F?veaction=edit&uselang=en - the second title is \"Books\" and since all the books are in English, the whole list should be wrapped with <div lang=\"en\" dir=\"ltr\">.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-cfsvvgbtlqnbt2yokfjf', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408734760, 'spacePHID': None, 'dateCreated': 1408703280, 'dateModified': 1417570757, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69892', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Media: bogus \"no results found\" message when searching media returns results', 'description': {'raw': 'bogus \"no results\" found in Media interface\\n\\nSeen if Firefox, less so in Chrome\\n\\nOn any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit \\n\\nClick Insert/Media.  Message \"no results found\" appears.\\n\\nSearch for media that returns results.  \"no results found\" message persists. See screen shot. \\n\\nIn Chrome, \"no results found\" flickers but ultimately disappears when media thumbs are displayed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14384}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408657052, 'spacePHID': None, 'dateCreated': 1408656900, 'dateModified': 1408657073, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69877', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Adding text to a category resulted in an extra section heading with span tags', 'description': {'raw': 'I have not been able to reproduce this at en.wikipedia.beta, and I didn\\'t want to edit live category pages for testing.\\n\\nIn Firefox, I added a line of text.  VisualEditor added a level 1 section headign after it:\\n\\n= <span dir=\"auto\">Category:Medical and health organizations</span> =\\n\\nYou can see the diff here:  https://en.wikipedia.org/w/index.php?diff=621943590&oldid=615616525\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1425594010, 'spacePHID': None, 'dateCreated': 1408562400, 'dateModified': 1438735473, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69803', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The custom tab does not get enabled after making an image of type \"Frame\" to full size', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Change the type of the image to \"Frame\"\\n4.Click on \"Apply Changes\"\\n5.Reopen the media settings dialog for that image\\n\\nObserve that the \"Make full size\" button is now active\\nClick on that.\\nThe Custom tab does not get enabled, even though the size has just been customized by making it full size.\\n\\nEnvironment:Betalabs\\nBrowser:Chrome\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423675100, 'spacePHID': None, 'dateCreated': 1408557240, 'dateModified': 1438735476, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69794', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Suggest templates more proactively in the template adding dialog', 'description': {'raw': 'Currently, in the template adding dialog there is just one search box and a lot of empty space.\\n\\nA user needs to know the name of the template to insert.\\n\\nA template could be suggested in a more proactive way. One idea can be to simply show the currently available templates by category, starting from the top and let the user drill down (in enwiki the top is https://en.wikipedia.org/wiki/Category:Wikipedia_templates ; the top category should probably be defined in a wg variable). This will require each project to maintain their templates neatly categorized, but this should be done anyway ;)\\n\\nAnother possibility is to let the projects define lists of commonly used templates, or to show a list of the most frequently transcluded ones.\\n\\n[And see also the trivial bug 69692.]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408571387, 'spacePHID': None, 'dateCreated': 1408550460, 'dateModified': 1417570758, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69787', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: saveOptions.summary is not updated if the summary is inserted using a tool (InputWidget relies on 'change' events rather than checking the value)\", 'description': {'raw': \"The Hebrew Wikipedia, as well as a few others, have a gadget for canned edit summaries:\\nhttps://he.wikipedia.org/wiki/MediaWiki:Gadget-Summarieslist.js\\n\\nIf the forceeditsummary user preference is enabled and the user uses this gadget to insert a summary, the warning about an empty edit summary is issued, even though it shouldn't.\\n\\nI suspect that the problem is in the VE code.\\nAs far as I can see, this preference is checked in\\nmodules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.js on line 867\\nand the summary values are not what I expect them to be.\\n\\n(See also Bug 52085.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421025800, 'spacePHID': None, 'dateCreated': 1408466400, 'dateModified': 1488318200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69749', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide content-based descriptions when focusing references or templates', 'description': {'raw': 'In particular we\\'ve had a community request to display a citation summary when focusing citation nodes.\\n\\nWe could list template values in order until we run out of room, but this may not lead to desirable results, for example the first parameter in {{Cite web}} is URL.\\n\\nA more complex solution would be to come up with a format for defining how to generate the summary of a template and store it in template data, either as a value on the column (summary order):\\n\\nField     Desc  Summary order\\nurl       ...   null\\npublisher ...   2\\ntitle     ...   1\\ndate      ...   3\\nmonth     ...   null\\n\\nA simplified version of this would just flag one field as being used in the summary.\\n\\netc.\\n\\nOr as a string concatenation message somewhere:\\n\\n\"{{{title}}}, {{{publisher}}} - {{{date}}}\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408464025, 'spacePHID': None, 'dateCreated': 1408463340, 'dateModified': 1417570759, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69744', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  After you create a link and close the link inspector, please de-select the newly linked text', 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Type some text:  \"Foo bar baz bat\"\\n\\n2.  Select the last word, because you want to create a wikilink before you finish typing the sentence.\\n\\n3.  Type Command-K to create a link.  \\n\\n4.  Make a link.  Click \"Done\".\\n\\n5.  Finish typing the sentence.\\n\\n6.  Oops, where did [[bat]] go?\\n\\n\\nResults:\\n\\nWhen you exit the link inspector, the linked text remains highlighted, and typing results in it being overwritten by your next character.  \\n\\nExpectation:  after I\\'ve made a link, de-select the link and put the cursor at the end of the word, so I can keep writing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423675223, 'spacePHID': None, 'dateCreated': 1408389720, 'dateModified': 1423675223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69711', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dropdown menu shows scrollbars', 'description': {'raw': 'screenshot of the problem\\n\\nConfirmed this on Safari 7, mac, Vector and Firefox 31, Windows 7, Monobook\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54705\\n\\n**Attached**: {F14614}'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409892989, 'spacePHID': None, 'dateCreated': 1408380300, 'dateModified': 1417570755, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69707', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: allow parameter per line in inserted templates', 'description': {'raw': 'It is customary for big templates with a lot of parameters, such as infoboxes, to have each parameter written on a separate line in the wiki source code.\\n\\nIf I am not mistaken, VE inserts all templates in one long line.\\n\\nAs long as source code editing is common, VE should insert templates according to the above community practice.\\n\\nHow to know whether to insert one line or multiple lines? Either do it with multiple lines if there are more than x parameters, say 4, or have a parameter in template data that suggests multiline insertion.\\n\\n**See Also**:\\n* {T52584}'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1442345274, 'spacePHID': None, 'dateCreated': 1408335060, 'dateModified': 1456704444, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69682', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Pasting a link label causes the link to split', 'description': {'raw': \"What I started with was a link to a disambiguation page:\\n\\n  Foo bar [[CML]] baz bat.\\n\\n\\nWhat I wanted was a link to a real article, so I repointed the link:\\n\\n  Foo bar [[chronic myelogenous leukemia|CML]] baz bat.\\n\\n\\nHmm, that initialism doesn't appear to be expanded anywhere on the page.  Okay, what we need is:\\n\\n  Foo bar [[chronic myelogenous leukemia]] baz bat.\\n\\n\\nSo I copied the long name out of the link tool's field, and pasted it into the middle.  It produced:\\n\\n  Foo bar [[chronic myelogenous leukemia|CM]]chronic myelogenous leukemia[[chronic myelogenous leukemia|L]] baz bat.\\n\\nNone of this would have been so difficult if we could edit labels in the link tool, in a separate box.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408272633, 'spacePHID': None, 'dateCreated': 1408236960, 'dateModified': 1417570759, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69653', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'firsteditve no longer points to VisualEditor', 'description': {'raw': 'The step in firsteditve that appears when you start editing the document in VisualEditor no longer points to the \"Save page\" button due to an incompatible change to the VE HTML DOM.\\n\\nIt still shows up, but it\\'s no longer attached.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408553774, 'spacePHID': None, 'dateCreated': 1408162620, 'dateModified': 1408553781, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'JS error on loading mobile VE: Discontiguous selection is not supported.', 'description': {'raw': \"When I open the VisualEditor on mobile in stable on enwiki using Chrome on desktop (OSX), I get the following JS error:\\nDiscontiguous selection is not supported. \\n\\nI loaded it with ?debug=true here's what I see in the console:\\nDiscontiguous selection is not supported. rangy-core-1.3.js:2842\\n(anonymous function) rangy-core-1.3.js:2842\\n(anonymous function) rangy-core-1.3.js:2852\\n(anonymous function) rangy-core-1.3.js:327\\ninit rangy-core-1.3.js:249\\nloadHandler rangy-core-1.3.js:365\\n\\nIncidentally, I'm also seeing this in the console with ?debug=true (however I do not see this without ?debug=true):\\nUncaught Error: Module not found: loggingSchemas/MobileWebClickTracking load.php?debug=true&lang=en&modules=mobile.head&only=scripts&skin=minerva&version=20140815T031511Z&*:53\\nmw.mobileFrontend.require load.php?debug=true&lang=en&modules=mobile.head&only=scripts&skin=minerva&version=20140815T031511Z&*:53\\n(anonymous function) load.php?debug=true&lang=en&modules=mobile.languages&only=scripts&skin=minerva&version=20140815T101…:67\\n(anonymous function)\\n\\nNot sure if the click tracking thing is related, a separate bug, or just a result of something going wonky with load order as a result of ?debug=true - if it seems like a separate issue, I'm happy to file another bug but figured it'd be worth mentioning here for now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-jh2oguhshocanixqvlfk', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412803537, 'spacePHID': None, 'dateCreated': 1408123380, 'dateModified': 1412803537, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69616', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Offer to pre-fill the DEFAULTSORT field', 'description': {'raw': \"Usually, DEFAULTSORT contents need only a little re-arranging or capitalization changes.  If the name is long or unfamiliar, it may be difficult to type it to make these relatively minor changes.  It would be nice to pre-fill the box with the page title.\\n\\nBut if VisualEditor simply fills in the box whenever you open the Page settings menu, then we'll get a lot of errors (because people won't notice that it needs to be updated).\\n\\nPossible solution:  Add a button next to the DEFAULTSORT item to insert the current page title as text that the editor can then change as needed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408096620, 'spacePHID': None, 'dateCreated': 1408048080, 'dateModified': 1417570760, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69568', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: removing a link takes me to the top of the page', 'description': {'raw': 'Steps to repro:\\n\\n1. In production/stable, enter VE edit mode and scroll down to a section that\\'s below the fold.\\n2. Tap on a wikilink\\n3. Use the \"remove\" button to remove the link & tap done.\\n\\nExpected: I am taken back to the section I was on.\\n\\nActual: I\\'m taken back to the top of the page.\\n\\nObserved on iPad 2 & mobile site on desktop Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-yu5wnmvkjecufsjgh2fa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409100209, 'spacePHID': None, 'dateCreated': 1408047960, 'dateModified': 1409100209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69567', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cannot copy text when dm.surface.enabled === false', 'description': {'raw': \"**Author:** `ryan.wold`\\n\\n**Description:**\\nWhen disabling an Editor's .target.surface (by calling .disable()), the text is no longer editable, which is great.  However, the text in the disabled Editor cannot be copied and pasted.  It does not appear to make it to the clipboard. \\n\\nDesired behavior is that the text can be be copied even when the editor is disabled.  Or perhaps there could be a setting/option around that.\\n\\n\\n\\nWe traced this to ve.dm.Surface.prototype.changeInternal, where it returns immediately if the surface is disabled.\\n\\nif ( !this.enabled ) {\\n  return;\\n}\\n\\nI found this here: https://doc.wikimedia.org/VisualEditor/master/source/ve.dm.Surface.html#ve-dm-Surface-method-changeInternal\\n\\n\\nI'm using OSX Mavericks and Google Chrome Version 36.0.1985.125.\\n\\nThanks!\\n\\n- Ryan Wold\\n  ryan.wold@neo.com\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407976455, 'spacePHID': None, 'dateCreated': 1407976380, 'dateModified': 1417570760, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69516', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Too much tabbing in the Template dialog', 'description': {'raw': 'From John Broughton:\\n\\n\"This is what tabbing through Cite templates (in the mini-editors) looks like: type, tab, tab, tab, type, tab, tab, tab, type, ... You have to tab three times to get from one field to the next. That\\'s because tabbing always includes both the “Field description” and “Remove field” icons. There isn\\'t any reason to include these icons in tabbing; tabbing should bypass these icons.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414084060, 'spacePHID': None, 'dateCreated': 1407974220, 'dateModified': 1417570685, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69512', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Links added to captions for new images not quite working', 'description': {'raw': 'What happens when you try to make a link.  (Notice that the box is too small; that will be a separate bug in a moment.)\\n\\nI can only make this happen in Safari, not Firefox, but I believe that the user reporting this was using Firefox.\\n\\nSteps to reproduce:\\n\\n1.  Open VisualEditor and Insert > Media.\\n\\n2.  Pick and image and add a caption.\\n\\n3.  Select a word and press Command-K to make an internal link. \\n\\n4.  Notice that you get no search results to help you find the correct page for your link.\\n\\n5.  Click inside the box.  Now you have search results.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14163}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410202699, 'spacePHID': None, 'dateCreated': 1407973740, 'dateModified': 1424894575, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69510', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Information fields in template dialogs are sometimes very large', 'description': {'raw': \"See https://en.wikipedia.org/wiki/File:Cite_dialog_with_large_boxes_for_fields.png\\n\\nThis is intermittent and may be relate to zooming in/large text size.  The fields go back to normal size when you click inside them.  Seen in both Firefox and Safari on Macs.\\n\\nToday, I'm getting pretty consistent results by opening https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&veaction=edit in Safari and selecting the infobox.  Opening it (double-clicking) the first time works as expected.  Cancelling it (escape key) and opening it again produces larger than necessary fields.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1421791472, 'spacePHID': None, 'dateCreated': 1407972240, 'dateModified': 1438735479, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69508', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  The Categories dialog should indicate which cats are red links', 'description': {'raw': 'Of a non-existent category has been added on a page, there is no indication in the Categories dialog that it is a red link.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414805875, 'spacePHID': None, 'dateCreated': 1407971580, 'dateModified': 1414805875, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69507', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Categories should be displayed at the end of the page', 'description': {'raw': \"VisualEditor should display categories in the page's footer, just like they will display when the page is saved.  Clicking on the footer could open the Categories editing tool.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437698082, 'spacePHID': None, 'dateCreated': 1407971340, 'dateModified': 1437698082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69506', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'HTML code is seen while editing the ru.wikipedia page about Bohuslav Tablic', 'description': {'raw': 'Article URL: https://ru.wikipedia.org/wiki/%D0%A2%D0%B0%D0%B1%D0%BB%D0%B8%D1%86,_%D0%91%D0%BE%D0%B3%D1%83%D1%81%D0%BB%D0%B0%D0%B2\\n\\nThe infobox is shown correctly while reading the article, but broken when editing in VisualEditor. HTML code is shown above the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408488269, 'spacePHID': None, 'dateCreated': 1407844800, 'dateModified': 1408488269, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69432', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Chrome not populating text fields correctly', 'description': {'raw': 'Reported by S Page at QA mailing list[1]. Reported to Sauce Labs support[2].\\n\\n1: http://lists.wikimedia.org/pipermail/qa/2014-August/001843.html\\n2: http://lists.wikimedia.org/pipermail/qa/2014-August/001846.html\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409590186, 'spacePHID': None, 'dateCreated': 1407767220, 'dateModified': 1425389805, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69399', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <ref>s in a section-edit get re-numbered', 'description': {'raw': 'https://en.wikipedia.org/wiki/Sonic_Adventure#Development\\n\\nWhen I go here and click \"edit beta\", the <ref>s are re-numbered when ?veaction=edit loads.\\n\\nFor example, at the implicit ?action=view:\\n\\n---\\nThe character of Sonic was redesigned for the game by Sonic Team artist Yuji Uekawa, with longer legs and spines that Iizuka subsequently noted were more suitable for 3D than Sonic\\'s original and more compact design, which was meant to be seen from the side.[46][47] \\n---\\n\\nAt ?veaction=edit:\\n\\n---\\nThe character of Sonic was redesigned for the game by Sonic Team artist Yuji Uekawa, with longer legs and spines that Iizuka subsequently noted were more suitable for 3D than Sonic\\'s original and more compact design, which was meant to be seen from the side.[42][43]\\n---\\n\\nThis is super-confusing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407719768, 'spacePHID': None, 'dateCreated': 1407700140, 'dateModified': 1407719768, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69373', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Dialog for inserting new templates doesn't play well with search results\", 'description': {'raw': 'Goal:  Insert a new template.\\n\\nSteps to reproduce:\\n\\n1.  Insert > Template\\n\\n2.  Start typing the template\\'s name:  Citation nee…\\n\\n3.  Think, \"Ah, it\\'s found it!  It\\'s highlighted and has a checkmark next to it!  Great, I can stop typing that long name and just hit return to add the template that I want.\\n\\n4.  Press return.\\n\\n5.  Think, \"Um, [[Template:Citation nee]] is a redlink.  Why did it add that?  Why didn\\'t it add the highlighted-and-checkmarked [[Template:Citation needed]]?\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1424904363, 'spacePHID': None, 'dateCreated': 1407651480, 'dateModified': 1438735479, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69358', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add parameterless GENDER as insertable', 'description': {'raw': 'When {{GENDER:|...}} is part of a source string, GENDER: is not available as insertable.\\n\\nExample string: https://translatewiki.net/wiki/MediaWiki:Visualeditor-editconflict/en\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-w5a723w3wes6jd5wskgg', 'ownerPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413456007, 'spacePHID': None, 'dateCreated': 1407519060, 'dateModified': 1574978648, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69306', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Distorted UI of Language Inspector/Special Character appears while trying to open them when the link inspector is already open in CE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Select a text\\n3.Click on Link inspector\\n4.While the link inspector is open, open Language inspector or Special Character inserter\\n\\nObserved Result:\\nThe UI of both the inspector appears a bit distorted having a whitespace at the bottom\\n\\nSee the screenshot attached\\n\\nEnvironment:Production,test2,Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14605}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1425002089, 'spacePHID': None, 'dateCreated': 1407356580, 'dateModified': 1427672913, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69202', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Edit beta tab not shown, when not logged in.', 'description': {'raw': 'Environment- beta, production\\n\\n1> Try to open your User page without logging in.\\n2> Shows the \"Welcome to VE\" popup, click on \"continue\" to proceed.\\n3> opens the page in VE mode , but the VE Edit tab is not seen on top.\\n\\nIn test2 follow the above steps and the page would open in the Read mode and all the tabs(Read, Edit and Edit source can be seen).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407364526, 'spacePHID': None, 'dateCreated': 1407343860, 'dateModified': 1407364526, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69194', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Enable toggling between tabs and dropdown menus in the Vector skin ,  does not make the Read, Edit tabs squeeze into one “View” tab for FF and Safari.', 'description': {'raw': 'screenshot\\n\\n1> Preferences -> Gadgets\\n2> Enable this under Appearance -> Enable toggling between tabs and dropdown menus in the Vector skin. \\n3> Save \\n4> go back to User page. Notice now the Tabs Read, Edit and Edit Source all have been moved into a single drop down labeled “View”. However, enabling the same appearance in FF and Safari does not show the “View” dropdown.\\nAlso, the “View” is out of position as compared to “More” and does not show the drop down arrow.See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F14485}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417577754, 'spacePHID': None, 'dateCreated': 1407271560, 'dateModified': 1417577754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69153', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Citation number 0', 'description': {'raw': '* Add a basic citation\\n* Add another non-basic(?) citation\\n* Go back and set group of basic citation to something, apply changes\\n* Undo changes twice\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414806524, 'spacePHID': None, 'dateCreated': 1407187800, 'dateModified': 1414806524, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69125', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Placing some templates in bulleted lists causes complex transclusions', 'description': {'raw': 'Steps to Reproduce:\\n1. Open https://ru.wikipedia.org/w/index.php?oldid=63644335&veaction=edit and look at the second section.\\n\\nThe wikitext is:\\n\\n=== Б ===\\n\\n* [[Борисов, Бойко Методиев]] (род. 1959)\\xa0— болгарский политик.\\n* {{NL|Борисов, Борис}}\\n\\n{{NL}} is a template that transcludes the rest of this short list.\\n\\n2. The first bullet point is plain wikitext.  Click on the first item and try to change some of the text (e.g., to change the birth date from 1959 to 1960).\\n\\n\\nActual Results:  \\nThe first bullet point can only be edited as the \"content\" part of a complex transclusion.  \\n\\nExpected Results:  \\nThat plain-text list items can be edited as plain old list items.\\n\\nReproducible: Didn\\'t try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408574718, 'spacePHID': None, 'dateCreated': 1407177240, 'dateModified': 1408574718, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69117', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Media Settings dialog does not close, when inserting a media with a link or language  \"Uncaught TypeError: undefined is not a function\"', 'description': {'raw': 'screenshot\\n\\nEnvironment-test2\\n\\nSteps- \\n\\n1> Insert-> Media.\\n2> In media Settings dialog insert a link or type in some text in a language.\\n3> Click on \"Insert media\". notice the file gets inserted in the background, and yet the media settings dialog never closes.\\n\\nSee screenshot.\\n\\nAlso See bug 65568.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Windows XP\\n\\n**Attached**: {F14256}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407162887, 'spacePHID': None, 'dateCreated': 1406931420, 'dateModified': 1417570761, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69031', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Can't re-use the same reference twice\", 'description': {'raw': 'Intention:\\nRe-use an existing reference\\n\\nSteps to Reproduce:\\n1.  Open a page containing a citation.\\n\\n2.  Cite > Re-use.  Click on a reference.\\n\\n3.  Go to another sentence.\\n\\n4.  Cite > Re-use.  Click on the same reference (it\\'s already highlighted).\\n\\n\\nActual Results:  \\nThe first time, it adds the ref.  The second time, it does nothing.  You have to insert a different (wrong) ref, delete that, and then add the one that you wanted (now that it\\'s stuck on the \"wrong\" one).  Canceling and trying again doesn\\'t help.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406929690, 'spacePHID': None, 'dateCreated': 1406928360, 'dateModified': 1417570761, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69027', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Insert -> Comment not working in Betalabs', 'description': {'raw': 'steps-\\n1> open a page in VE.\\n2> Insert -> Comment. Add/Edit Comment dialog does not pop.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows XP'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406921057, 'spacePHID': None, 'dateCreated': 1406912520, 'dateModified': 1417570762, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor Mobile:Mobile VE does not load after saving the first time edit in production (en.wiki), shows Error,can't load section\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Mobile VE in prouction\\n\\n2.Make any edit and save it\\n\\n3.Try to reopen the page with Mobile VE\\n\\nObserved Result:\\nVE does not load the page and the error appears:\\nError,can't load section\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14658}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409669905, 'spacePHID': None, 'dateCreated': 1406838660, 'dateModified': 1417570756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68948', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Weird behavior of the Cite extension with VisualEditor', 'description': {'raw': 'References in MediaWiki view mode (rendering correctly)\\n\\nThis is most likely due to Cite, but the extension works in \"view\" mode and fails in VE in my local wiki.\\n\\nThe problem: \\n\\nCitations/References work well in view mode but when VE loads, they appear as their \"raw\" tags <ref>Something</ref> and <references />. \\n\\nMore details: From within VE, even when the references appear broken like above, I can still add a reference, which renders correctly as [1]. When I save the page the wikitext is correct and the view mode recognizes all references (both those that were broken and those that were just inserted). Then if I re-edit the page, the references are broken again.\\n\\nDetails -\\n\\nCite extension is installed from the git repository, and this line is in LocalSettings.php:\\nrequire_once \"$IP/extensions/Cite/Cite.php\";\\n\\nThis happens in Chrome 36.0.1985.125 and Firefox 31.0 under Ubuntu 14.04\\n\\n\\nAttachments: \\n\\nView mode and edit mode of the same page (no change to wikitext)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14545}'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406832203, 'spacePHID': None, 'dateCreated': 1406787600, 'dateModified': 1417570762, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68899', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'MediaWiki 1.24wmf6 required when trying to install VisualEditor_REL1.23', 'description': {'raw': \"**Author:** `sure4us`\\n\\n**Description:**\\nA number of people trying to install 1.23.1 + VE + Parsoid are finding an error that crashes the site.\\n\\nhttps://www.mediawiki.org/wiki/Extension_talk:VisualEditor#MediaWiki_1.24wmf6_required_when_trying_to_install_VisualEditor_REL1.23_45012\\n\\n\\nI'm also experiencing it, here's the error messaging:\\n\\n\\n[d64ccb4d] /wiki/ Exception from line 3279 of /home/mywiki/public_html/wiki/includes/GlobalFunctions.php: MediaWiki 1.24wmf6 required--this is only 1.23.1\\n\\nBacktrace:\\n\\n#0 /home/mywiki/public_html/wiki/extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW(string)\\n#1 [internal function]: VisualEditorHooks::onSetup()\\n#2 /home/mywiki/public_html/wiki/includes/Setup.php(601): call_user_func(string)\\n#3 /home/mywiki/public_html/wiki/includes/WebStart.php(156): require_once(string)\\n#4 /home/mywiki/public_html/wiki/index.php(43): require(string)\\n#5 {main}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408566124, 'spacePHID': None, 'dateCreated': 1406767620, 'dateModified': 1417570758, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68891', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Categories when added are shown as return character in VE.', 'description': {'raw': 'screenshot1\\n\\nEnvironments-test2, betalabs, production.\\n\\nSteps-\\n1> open a blank page in VE and type in some text.\\n2> while the cursor is still at the end of the last character, add at least two categories.\\n3> Save the page.\\n4> Now open the page again in VE. Notice the categories are shown as return characters at the end of the text(one for each category added).See screenshots.\\n\\nHappens only in Chrome and Safari.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F14346}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406754254, 'spacePHID': None, 'dateCreated': 1406656560, 'dateModified': 1417048869, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68811', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Link Inspector icon is not appearing, when language is selected, in Media Settings dialog.', 'description': {'raw': 'screenshot\\n\\nEnvironments-test2\\n\\nSteps-\\n1> open a page in VE.\\n2> Insert ->Media. \\n3>Select to add a media file. Opens the Media Settings dialog.\\n4>Now click on “Caption” pane and Select to insert a Link .\\n5> Click on the style text menu to select the Language and type some text. See screenshot.\\n6> Now move the cursor to the link, notice the link icon is not appearing, but the icon in the toolbar does get selected. \\n7>Now  try to insert a new link by selecting the link icon on toolbar, does not open the link inspector and the text in the pane gets typed as normal text.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14342}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409345322, 'spacePHID': None, 'dateCreated': 1406652060, 'dateModified': 1443278046, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68810', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Caption pane toolbar is accessible when cursor is in Alternative text, in Media Settings dialog.', 'description': {'raw': 'screenshot1\\n\\nEnvironment-test2, production\\n\\nSteps-\\n1> Open a page in VE.\\n2> Insert ->Media. \\n3>Select to add a media file. Opens the Media Settings dialog.\\n4>Now click on “Alternative Text”, with cursor in this input field. Select to insert a Comment or Special Character or a link.\\n5> Notice that the inspectors open up in the Alternative text input field (see screenshots), but when entered they do show up in the Caption pane.\\nAlso see 62410 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F14337}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406655142, 'spacePHID': None, 'dateCreated': 1406650800, 'dateModified': 1417570764, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68809', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Merge master and cloudbees branch of integration/jenkins-job-builder-config repository', 'description': {'raw': 'cloudbees branch was a step in moving jobs from Cloudbees. Now that the move is finished, the branch should be merged with master.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409589895, 'spacePHID': None, 'dateCreated': 1406640060, 'dateModified': 1409589895, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68801', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.', 'description': {'raw': 'screenshot1\\n\\nEnvironment- test2,betalabs.\\n\\nSteps-\\n1>Open a page in VE.\\n2>open Advanced Settings .Enable Display title and enter a title. Click “Apply Changes”.\\n3>Click on “Save Page”\\n4>Click on “Review your Changes”. Notice DISPLAYTITLE:titlename is shown under your text.\\n5> Now click on Return to Save form. Click on “Cancel” on the Save your changes dialog.\\n6>Go to Advanced Settings again in Page options. \\n7>Uncheck the “Enable Display title” checkbox and click to “Apply Changes”. \\n8> Repeat step#3 and #4. Notice even after disabling the display title it is still visible under your text in the “Review your changes” dialog. Open the advanced settings and you would notice that the enable display title is unchecked, but it shows up in Review your changes.\\n\\nTry the above steps with the other settings such as “Let this page be indexed by search engines”, “Show a tab on this page to add a new section”and with Categories too.Please see screenshots.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F14247}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406578618, 'spacePHID': None, 'dateCreated': 1406578140, 'dateModified': 1417570766, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68764', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Applying changes in Advanced settings are not reflected in Review your changes dialog.', 'description': {'raw': 'screenshot1\\n\\nEnvironment- test2,betalabs.\\n\\nSteps-\\n1>Open a page in VE.\\n2>open Advanced Settings .Enable Display title and enter a title. Click “Apply Changes”.\\n3>Click on “Save Page”\\n4>Click on “Review your Changes”. Notice DISPLAYTITLE:titlename is shown under your text.\\n5> Now click on Return to Save form. Click on “Cancel” on the Save your changes dialog.\\n6>Go to Advanced Settings again in Page options. \\n7>Uncheck the “Enable Display title” checkbox and click to “Apply Changes”. \\n8> Repeat step#3 and #4. Notice even after disabling the display title it is still visible under your text in the “Review your changes” dialog. Open the advanced settings and you would notice that the enable display title is unchecked, but it shows up in Review your changes.\\n\\nTry the above steps with the other settings such as “Let this page be indexed by search engines”, “Show a tab on this page to add a new section”and with Categories too.Please see screenshots.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F14243}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406577779, 'spacePHID': None, 'dateCreated': 1406577600, 'dateModified': 1417570767, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68761', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Comment Edit dialog does not close, after inserting a list.', 'description': {'raw': 'screenshot\\n\\nEnvironment- test2 and betalabs\\n\\nSteps-\\n1> Open a blank page in VE and type in some text.\\n2>At the end of the text insert a comment.\\n3>Click on the Comment , to open the comment edit dialog.\\n4> Now while the cursor is till in the comment edit dialog , click to insert a bullet point / numbered list.\\n5>Now click on “Done” or “Remove” to close the dialog. The dialog stays open.Please see screenshot.\\n\\nSame behavior in Chrome, FF and Safari.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Windows XP\\n\\n**Attached**: {F14169}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406597593, 'spacePHID': None, 'dateCreated': 1406559660, 'dateModified': 1417048870, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68738', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor should display entire comment when the orange icon is clicked', 'description': {'raw': \"Screenshot of too-small comment popup\\n\\nCurrently, when the orange comment icon is clicked, we see only the first few words of the comment.\\n\\nTo read the whole comment, we have to click again, which takes us to the edit view. You shouldn't have to launch the editor just to read the whole text.\\n\\nThe little popup that comes up when you first click the icon (I've lost track of VE jargon, sorry) should show the entire comment text, over multiple lines if necessary, and preferably in black or a darker gray.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F14130}\"}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406564517, 'spacePHID': None, 'dateCreated': 1406542140, 'dateModified': 1417570765, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68722', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'beta: ResourceLoader CSS URL gzipped twice, causing skins to be broken', 'description': {'raw': \"One of the CSS resource loader URL yield content which is gzipped twice :-(\\n\\nThe content is shown by piping to gzcat twice:\\n\\ncurl 'http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles%7Cwikibase.client.init&only=styles&skin=vector&*'|gzcat|gzcat\\n\\nHeaders:\\n\\n> User-Agent: curl/7.30.0\\n> Host: bits.beta.wmflabs.org\\n> Accept: */*\\n> \\n< HTTP/1.1 200 OK\\n* Server Apache is not blacklisted\\n< Server: Apache\\n< Access-Control-Allow-Origin: *\\n< Expires: Mon, 28 Jul 2014 09:22:53 GMT\\n< X-Content-Type-Options: nosniff\\n< Content-Encoding: gzip, gzip\\n< X-Powered-By: HHVM/3.3.0-dev\\n< Cache-control: public, max-age=300, s-maxage=300\\n< Vary: Accept-Encoding\\n< Last-Modified: Thu, 24 Jul 2014 03:43:51 GMT\\n< Content-Type: text/css; charset=utf-8\\n< Content-Length: 24050\\n< Accept-Ranges: bytes\\n< Date: Mon, 28 Jul 2014 09:19:08 GMT\\n\\n\\n\\nSame goes on when passing Accept-Encoding: gzip\\n\\nI restarted varnish on the bits cache to clear up the bits cache, hasn't solved anything.\\n\\n\\nThe minified CSS cache key is enwiki:resourceloader:filter:minify-css:7:e07e6ad07840d291e66cf3fe9f0980c3\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411712675, 'spacePHID': None, 'dateCreated': 1406539320, 'dateModified': 1422894511, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68720', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edge case of unintentional image removal', 'description': {'raw': 'See https://it.wikipedia.org/w/index.php?title=Vallo_Atlantico&oldid=66317144&veaction=edit :\\nReach the paragraph \"Comandi del Vallo Atlantico\", see there\\'s a list there.\\nIt looks weird because the syntax for the picture on the right is in the middle of the list.\\nAverage user doesn\\'t actually know/realize this and just wants to fix the list.\\nS/he will place the cursor right after the word \"Danimarca\" on the second line and hit Canc. The pic suddenly disappears.\\n \\n(Right now there\\'s a further bug 68708 which did lead to the image being removed without the user really noticing it: he noticed that the \"Commando tedesco\" line was not aligned properly and tried to fix that by going on that line and hitting Backspace. He didn\\'t notice the pic getting highlighted and hit Backspace again, so the page lost focus and all he could see when he read the list again was that he had fixed it.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1444159075, 'spacePHID': None, 'dateCreated': 1406532480, 'dateModified': 1444159075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68709', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Changes made after canceling a Save are lost', 'description': {'raw': 'Steps to Reproduce:\\n1. Add some text to a page (\"abc\").\\n\\n2. Click \\'Save\\'.\\n\\n3. Think, \"Oops, I forgot to add…\"\\n\\n4. Click the cancel button on the Save dialog.\\n\\n5. Go add the other text (\"xyz\") (or add or change images, templates, refs, or remove the abc text that you typed earlier; it doesn\\'t matter what changes you make).\\n\\n6. Save the page.\\n\\n7. Where\\'s the \"xyz\" text I just added?!\\n\\nActual Results:  \\nThis is a \"lose most of your work\" bug:  \\n\\nEverything you do after cancelling the first time is irretrievably lost, and unless you just happen to Review Changes before saving, you won\\'t know that you\\'re going to lose everything until it\\'s too late to copy it to another page.\\n\\n\\nReproducible: Always\\n\\nReported in Safari 7.1 on OS X 10.9.4; confirmed in Safari 6.1.4 and Firefox 30 on Mac OS 10.8.5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406564584, 'spacePHID': None, 'dateCreated': 1406498640, 'dateModified': 1406564584, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68693', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn ♙ appears if you type near a [[Link]] after the {{convert}} template', 'description': {'raw': 'Intention:\\nAdd a missing word (\"and\") towards the end of a sentence.  \\n\\nSteps to Reproduce:\\n1. Start with a pragraph that contains:\\n\\n* the en.wp {{convert}} template\\n* several [[Links]] after the template\\n\\n2. Click before or after one of these links.\\n\\n3. Type a space and the word \"and\" (or any word, but don\\'t press return to create a new paragraph).\\n\\n4. See the pawns?\\n\\n5. Now click somewhere else, and watch the pawns and text replicate.\\n\\nActual Results:  \\nSee https://en.wikipedia.org/w/index.php?oldid=618713444#Composition for an example of the results.\\n\\n\\nReproducible: Always\\n\\nFound in Firefox 31 on Windows 7; confirm in Safari 6 on Mac OS 10.8.5\\n\\nMay be related to Bug 68151\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://en.wikipedia.org/w/index.php?oldid=618713444#Composition\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68151'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406565501, 'spacePHID': None, 'dateCreated': 1406497380, 'dateModified': 1417048871, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68691', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: copying a text and moving down using the arrow adds a space', 'description': {'raw': \"It often happens to me that I select a letter in a word, copy it using Ctrl-C, and move the caret to the next line using the arrow-down keyboard key, and a space is added before the letter that I selected.\\n\\nIt's not completely consistent, but it happens in about 70% of my attempts to do the above.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1425003685, 'spacePHID': None, 'dateCreated': 1406466780, 'dateModified': 1438735484, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68676', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'PHP Notice:  Undefined index: REQUEST_TIME in extensions/EventLogging/includes/EventLogging.php on line 56', 'description': {'raw': 'php5 phpunit.php\\n\\nWhen doing http://paste.debian.net/111811/ , phpunit incurs in this:\\n\\nPHP Notice:  Undefined index: REQUEST_TIME in /srv/vagrant/mediawiki/extensions/EventLogging/includes/EventLogging.php on line 56\\nPHP Stack trace:\\nPHP   1. {main}() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:0\\nPHP   2. MediaWikiPHPUnitCommand::main() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:160\\nPHP   3. PHPUnit_TextUI_Command->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiPHPUnitCommand.php:42\\nPHP   4. PHPUnit_TextUI_TestRunner->doRun() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/Command.php:176\\nPHP   5. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/TestRunner.php:350\\nPHP   6. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709\\nPHP   7. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709\\nPHP   8. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709\\nPHP   9. PHPUnit_Framework_TestSuite->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:749\\nPHP  10. MediaWikiTestCase->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:779\\nPHP  11. PHPUnit_Framework_TestCase->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiTestCase.php:133\\nPHP  12. PHPUnit_Framework_TestResult->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:783\\nPHP  13. PHPUnit_Framework_TestCase->runBare() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestResult.php:648\\nPHP  14. PHPUnit_Framework_TestCase->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:838\\nPHP  15. ReflectionMethod->invokeArgs() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988\\nPHP  16. SpecialNewPagesFeedTest->testAddArticles() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988\\nPHP  17. ApiTestCase->doApiRequestWithToken() /srv/vagrant/mediawiki/extensions/PageTriage/tests/phpunit/SpecialNewPagesFeedTest.php:100\\nPHP  18. ApiTestCase->doApiRequest() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:142\\nPHP  19. ApiMain->execute() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:99\\nPHP  20. ApiMain->executeAction() /srv/vagrant/mediawiki/includes/api/ApiMain.php:332\\nPHP  21. ApiEditPage->execute() /srv/vagrant/mediawiki/includes/api/ApiMain.php:907\\nPHP  22. EditPage->internalAttemptSave() /srv/vagrant/mediawiki/includes/api/ApiEditPage.php:401\\nPHP  23. Article->doEditContent() /srv/vagrant/mediawiki/includes/EditPage.php:1973\\nPHP  24. Article->__call() /srv/vagrant/mediawiki/includes/EditPage.php:1973\\nPHP  25. call_user_func_array() /srv/vagrant/mediawiki/includes/page/Article.php:1992\\nPHP  26. WikiPage->doEditContent() /srv/vagrant/mediawiki/includes/page/Article.php:1992\\nPHP  27. wfRunHooks() /srv/vagrant/mediawiki/includes/page/WikiPage.php:2032\\nPHP  28. Hooks::run() /srv/vagrant/mediawiki/includes/GlobalFunctions.php:4031\\nPHP  29. call_user_func_array() /srv/vagrant/mediawiki/includes/Hooks.php:206\\nPHP  30. WikimediaEventsHooks::onPageContentInsertComplete() /srv/vagrant/mediawiki/includes/Hooks.php:206\\nPHP  31. WikimediaEventsHooks::logPageCreation() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:254\\nPHP  32. EventLogging::logEvent() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:196\\n\\nNotice: Undefined index: REQUEST_TIME in /srv/vagrant/mediawiki/extensions/EventLogging/includes/EventLogging.php on line 56\\n\\nCall Stack:\\n    0.0005     252912   1. {main}() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:0\\n    3.1858   25034984   2. MediaWikiPHPUnitCommand::main() /srv/vagrant/mediawiki/tests/phpunit/phpunit.php:160\\n    3.1859   25047464   3. PHPUnit_TextUI_Command->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiPHPUnitCommand.php:42\\n   43.5670  196201632   4. PHPUnit_TextUI_TestRunner->doRun() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/Command.php:176\\n   43.6076  196524896   5. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/TextUI/TestRunner.php:350\\n 2979.9686 1021381672   6. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709\\n 2979.9689 1021383176   7. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709\\n 3006.5969 1036522696   8. PHPUnit_Framework_TestSuite->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:709\\n 3007.1232 1037095048   9. PHPUnit_Framework_TestSuite->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:749\\n 3007.1232 1037095048  10. MediaWikiTestCase->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:779\\n 3007.1233 1037095208  11. PHPUnit_Framework_TestCase->run() /srv/vagrant/mediawiki/tests/phpunit/MediaWikiTestCase.php:133\\n 3007.2455 1037095568  12. PHPUnit_Framework_TestResult->run() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:783\\n 3007.2457 1037096512  13. PHPUnit_Framework_TestCase->runBare() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestResult.php:648\\n 3007.6986 1037467560  14. PHPUnit_Framework_TestCase->runTest() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:838\\n 3007.6987 1037468504  15. ReflectionMethod->invokeArgs() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988\\n 3007.6987 1037468776  16. SpecialNewPagesFeedTest->testAddArticles() /srv/vagrant/mediawiki/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:988\\n 3007.6987 1037469976  17. ApiTestCase->doApiRequestWithToken() /srv/vagrant/mediawiki/extensions/PageTriage/tests/phpunit/SpecialNewPagesFeedTest.php:100\\n 3007.6987 1037471616  18. ApiTestCase->doApiRequest() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:142\\n 3007.6992 1037528872  19. ApiMain->execute() /srv/vagrant/mediawiki/tests/phpunit/includes/api/ApiTestCase.php:99\\n 3007.6992 1037528920  20. ApiMain->executeAction() /srv/vagrant/mediawiki/includes/api/ApiMain.php:332\\n 3007.7069 1037555016  21. ApiEditPage->execute() /srv/vagrant/mediawiki/includes/api/ApiMain.php:907\\n 3008.1653 1037899936  22. EditPage->internalAttemptSave() /srv/vagrant/mediawiki/includes/api/ApiEditPage.php:401\\n 3008.2155 1037909472  23. Article->doEditContent() /srv/vagrant/mediawiki/includes/EditPage.php:1973\\n 3008.2155 1037910264  24. Article->__call() /srv/vagrant/mediawiki/includes/EditPage.php:1973\\n 3008.2155 1037910704  25. call_user_func_array() /srv/vagrant/mediawiki/includes/page/Article.php:1992\\n 3008.2155 1037911512  26. WikiPage->doEditContent() /srv/vagrant/mediawiki/includes/page/Article.php:1992\\n 3008.3812 1037999520  27. wfRunHooks() /srv/vagrant/mediawiki/includes/page/WikiPage.php:2032\\n 3008.3812 1037999568  28. Hooks::run() /srv/vagrant/mediawiki/includes/GlobalFunctions.php:4031\\n 3008.3813 1038001544  29. call_user_func_array() /srv/vagrant/mediawiki/includes/Hooks.php:206\\n 3008.3813 1038002848  30. WikimediaEventsHooks::onPageContentInsertComplete() /srv/vagrant/mediawiki/includes/Hooks.php:206\\n 3008.3813 1038002848  31. WikimediaEventsHooks::logPageCreation() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:254\\n 3008.3813 1038003736  32. EventLogging::logEvent() /srv/vagrant/mediawiki/extensions/WikimediaEvents/WikimediaEventsHooks.php:196\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14495}'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1475706089, 'spacePHID': None, 'dateCreated': 1406409960, 'dateModified': 1475706089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68629', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: fresh accounts being taken to VE by default on beta labs', 'description': {'raw': \"Possible regression: Today I created a few fresh accounts on beta labs (desktop Chrome browser, mobile site) to test other stuff, and I noticed that when I tapped the edit pencil for the first time, I was taken to the VE editor instead of wikitext editor. Awhile back, we decided *not* to send new users to VE by default on any wiki and merged a patch to fix this -- looks like it's no longer working \\n:-/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-yu5wnmvkjecufsjgh2fa', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406742992, 'spacePHID': None, 'dateCreated': 1406312100, 'dateModified': 1406742992, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68583', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Sidebar button \"Add more information\" in template dialog is cut off / too long', 'description': {'raw': \"Screenshot of bug\\n\\nIn general items in the sidebar are wiki input (template names, parameter names) which are fine being cut off.\\n\\nWhen the item is a UI element for inserting a new parameter though, it shouldn't be cut off. We might as well put the ellipsis in the localisation message (joking) for it is never rendered fully... (also no tooltip with full version). This is even more problematic considered it's localised. In English the first two words are enough to make sense of it, but we can't assume that for all languages.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14224}\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415062542, 'spacePHID': None, 'dateCreated': 1406169480, 'dateModified': 1417570679, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68496', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template dialog should provide a way to add parameters up front', 'description': {'raw': 'Right now there\\'s imho two usability issues with the default (simplified) Template editor related to getting to the screen for adding parameters.\\n\\nI expect to see an input field and a pool of parameters to pick from right after clicking.\\n\\nInstead there is a widget labelled \"Add more information\". This is apparently the button to unhide the panel to add parameters. I\\'m not sure how this is useful, we can just ditch that button and have that always be visible? (maybe in the odd case of templates with no known parameters or explicitly documented as taking none we could hide it behind a button to avoid confusion, but we should optimise for the common case).\\n\\nThis widget is confusing because:\\n* It\\'s labelled \"more\" information, but at this point it\\'s the first parameter, not an additional one (unless you count the template name as information).\\n* It\\'s called \"information\" which is a bit vague (we use \"parameter\" and \"field\" elsewhere).\\n* After inserting a parameter, the insertion panel goes away and I have to re-open it again. I recall it being there from the start and staying there in the past. Because it\\'s implemented as a placeholder for an individual parameter now, this is presumably no longer possible. I think we should make this panel the \"add parameter\" interface, and not have \"add parameter\" insert this placeholder panel for a one-off use.\\n\\nI\\'d say, as a first step (enough to fix this bug), hide the button, have the panel be visible from the start. And then continue like it is now (after inserting the first, the \"add more information\" button is used to add additional parameters.'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1434390994, 'spacePHID': None, 'dateCreated': 1406169000, 'dateModified': 1438735485, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68495', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page Settings option is getting cut off in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open any page in betalabs with VE\\n2.Open the page settings option\\n\\nObserved Result:\\nThe Page Settings menu is getting cut off\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14188}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406156548, 'spacePHID': None, 'dateCreated': 1406154540, 'dateModified': 1417570768, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68483', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"don't run screenshot tests in normal VE build\", 'description': {'raw': 'Screenshot tests have their own build, we do not want them running in the regular VE build: https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/115/testReport/\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-b5bosdf7b7zp3vqofbug', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406286854, 'spacePHID': None, 'dateCreated': 1406143740, 'dateModified': 1406547587, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68467', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The highlight that appears after adding a template while selecting an image is not proper', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Select the image and insert a template like citation needed\\n\\nObserved Result:\\nA highlight appears all around the image \\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14620}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1425004221, 'spacePHID': None, 'dateCreated': 1406068320, 'dateModified': 1438735485, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68411', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The link inspector appears over the toolbar while trying to add it inside an image for the first time', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE.\\n2.Go to Insert>Media.\\n3.Search for an image.\\n4.Select an image.\\n5.When the Media Settings>General settings for that image appears,click on the link inspector icon\\n\\nObserved Result:\\nThe link inspector icon appears over the toolbar,overlapping with the border of the Media dialog\\n\\nSee the screenshot attached\\n\\n\\nThis issue was found in test2, I need to test it in master once Betalabs is alive again.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14472}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423675914, 'spacePHID': None, 'dateCreated': 1405986960, 'dateModified': 1438735489, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68355', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When highlighting and replacing a text, VE starts typing by itself', 'description': {'raw': \"When I select (highlight) some text on the edit mode and start to type some text by replacing the old text, Visual Editor starts copying the text and typing by itself. I've seen it happening only on few articles, like https://fi.wikipedia.org/w/index.php?title=Arseni_Jatsenjuk&veaction=edit and https://fi.wikipedia.org/w/index.php?title=Mykola_Azarov&veaction=edit\\n\\nI tried this with Firefox and Chrome, logged-in / logged-out, and the same happens on both browsers.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-6majuboi566q3ozbh27r', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415055305, 'spacePHID': None, 'dateCreated': 1405796700, 'dateModified': 1417048866, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68278', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: Internal error when following redlink to a non-existent page in Topic namespace', 'description': {'raw': 'https://test.wikipedia.org/w/index.php?title=Topic:Foo&action=edit&redlink=1\\n\\n[42ec2509] /w/index.php?title=Topic:Foo&action=edit&redlink=1 Exception from line 2340 of /usr/local/apache/common-local/php-1.24wmf14/includes/EditPage.php: This content model is not supported: flow-board\\n\\nBacktrace:\\n\\n#0 /usr/local/apache/common-local/php-1.24wmf14/includes/EditPage.php(960): EditPage->toEditText(Flow\\\\Content\\\\BoardContent)\\n#1 /usr/local/apache/common-local/php-1.24wmf14/includes/EditPage.php(536): EditPage->initialiseForm()\\n#2 /usr/local/apache/common-local/php-1.24wmf14/includes/actions/EditAction.php(49): EditPage->edit()\\n#3 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(431): EditAction->show()\\n#4 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(295): MediaWiki->performAction(Article, Title)\\n#5 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(603): MediaWiki->performRequest()\\n#6 /usr/local/apache/common-local/php-1.24wmf14/includes/MediaWiki.php(452): MediaWiki->main()\\n#7 /usr/local/apache/common-local/php-1.24wmf14/index.php(46): MediaWiki->run()\\n#8 /usr/local/apache/common-local/w/index.php(3): require(string)\\n#9 {main}\\n\\n--------------------------\\n**Version**: master\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=73443'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'dateClosed': 1418762041, 'spacePHID': None, 'dateCreated': 1405736340, 'dateModified': 1418952341, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68258', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  No Language selected in the Language Selector shows “$1”', 'description': {'raw': 'Screenshot\\n\\nSteps-\\n1> Select Language form the Style text drop down.\\n2>In the Language Selector dialog delete the two-letter code. Press done.\\n3> Now type in some text in the editor, notice that beside the Language icon there is “$1” in the tootltip. See Screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14154}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414136569, 'spacePHID': None, 'dateCreated': 1405639620, 'dateModified': 1443278072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68202', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"can't search image when inserting media in private wiki\", 'description': {'raw': '**Author:** `Coiby.Xu`\\n\\n**Description:**\\nI\\'m testing VisualEditor on 1.23.1. Everything is OK except for inserting an image. When you insert media, you can\\'t use search function. The error message is \\'error\":{\"code\":\"readapidenied\",\"info\":\"You need read permission to use this module\"}\\'. However if I set  $wgGroupPermissions[\\'*\\'][\\'read\\'] = true, the pictures will be shown.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406584368, 'spacePHID': None, 'dateCreated': 1405582980, 'dateModified': 1417570766, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68141', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Blank link inspector UI appears when trying to open it inside the Media Settings while selecting another image in the caption', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page and insert an image\\n2.Insert another image inside it\\n3.Select the image inside and try to open link inspector\\n\\nObserved Result;\\nThe link inspector appears without any UI'\\n\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14529}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416342840, 'spacePHID': None, 'dateCreated': 1405550460, 'dateModified': 1417570674, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68130', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Select text, type = garbled, repeated text + snowman on el.wp', 'description': {'raw': 'See https://el.wikipedia.org/w/index.php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82%3AElitre_%28WMF%29%2Fsandbox&diff=4757904&oldid=4757901 .\\nReplace one or more words with \"Foobar\" (that is, highlight the word(s), then type Foobar). Works once, works twice, then the third time corruption happens and le wild snowman appears.\\nMust say that I only managed to reproduce that in my sandbox, which features content from https://el.wikipedia.org/wiki/%CE%95%CF%80%CE%B9%CF%84%CF%8C%CE%BA%CE%B9%CE%BF , and in this article page.\\nIt happens in Chrome and Firefox, tested under Windows 7, Ubuntu 13.10 and OS X 10.8.\\nDuring an attempt to reproduce, VE also suppressed existing nowiki tags: https://el.wikipedia.org/w/index.php?title=%CE%A7%CF%81%CE%AE%CF%83%CF%84%CE%B7%CF%82:P.a.a/%CF%80%CF%81%CF%8C%CF%87%CE%B5%CE%B9%CF%81%CE%BF&diff=next&oldid=4757859 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406598882, 'spacePHID': None, 'dateCreated': 1405545780, 'dateModified': 1406598882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68124', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Easy way to reproduce a weird behavior with the link tool', 'description': {'raw': \"Take a page like https://en.wikipedia.org/wiki/Heliozela_rutilella?veaction=edit (that is, starting with a template, so there's some space above the first line of the article).\\nClicking on the link tool and pressing ESC will automatically make the first word (Heliozela) a link to the Heliozela article. \\nClick on the up arrow, then click on the link tool again, and press ESC. You get the word Heliozela again (with no links).\\n\\n**See Also**:\\nT70101\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1434390735, 'spacePHID': None, 'dateCreated': 1405518780, 'dateModified': 1438735489, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68102', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't allow a linking action if no text was highlighted before\", 'description': {'raw': 'Load VE. Say \"Foobar\" is the first word on the page.\\nIf you click on the link tool, by mistake or not, without selecting anything before, Foobar will automatically become a link to the Foobar page (it doesn\\'t help that pressing ESC doesn\\'t abort the action, the link gets applied anyway, as we know).\\nNicoV noticed this in several French articles, where you can quite tell links happened \"by mistake\" since the first word is an article, \"le\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68102'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407699357, 'spacePHID': None, 'dateCreated': 1405517940, 'dateModified': 1434390735, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68101', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'performance degradation with new UI', 'description': {'raw': 'Seen on beta labs as 15 July: \\n\\nUpon loading a simple page such as http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit\\n\\nThe contentEditable surface used to appear reliably in under ten seconds.  Now I am seeing 10+ second load times for about one page load of every three.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405467205, 'spacePHID': None, 'dateCreated': 1405466760, 'dateModified': 1405467222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68081', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Opens wrong page in Edit source after making change in VE in old version of artcle', 'description': {'raw': '*open old version of artcle\\n*press tab Edit\\n*make some changes\\n*press tab Edit source\\n*in warnng window press \"Discard changes\"\\n->will open this page https://en.wikipedia.org/w/index.php?action=edit&veswitched=1\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows 8.1\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-5joeladhczukimiv4rwl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405448377, 'spacePHID': None, 'dateCreated': 1405437840, 'dateModified': 1417570769, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68038', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: switching to \"Default\" image size in image inspector does not make Apply Changes button active', 'description': {'raw': 'in order to save this change a user must make another change in the dialog in addition to setting the image size to default\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406427644, 'spacePHID': None, 'dateCreated': 1405390800, 'dateModified': 1417570767, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68014', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: required parameter not showing', 'description': {'raw': '**Author:** `manueltassi91`\\n\\n**Description:**\\nIn itwiki, we\\'ve noticed that when including [it.wikipedia.org/wiki/Template:A] in a page using VE doesn\\'t show all required parameters, but just one. In fact, with VE there should be three required parameters (\"Motivazione\", \"Data di inserimento\" \"Argomento\"), but in the dialog only \"Motivazione\" is shown.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406314288, 'spacePHID': None, 'dateCreated': 1405346700, 'dateModified': 1406314301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67986', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In [[Pristina International Airport]] the backspace key makes the cursor jump further back', 'description': {'raw': 'I couldn\\'t reproduce this in any other article, but it may happen elsewhere:\\n\\n1. Edit https://en.wikipedia.org/wiki/Pristina_International_Airport (I tested in this version: https://en.wikipedia.org/w/index.php?title=Pristina_International_Airport&oldid=615886404 ).\\n\\n2. Put the caret in the first paragraph, in the word \"handles\".\\n\\n3. Press Backspace.\\n\\nExpected: The caret moves one character and deletes it.\\nObserved: The caret deletes one character before it, but moves back 26 characers to the beginning of the word \"international\".\\n\\nHappened to me in Firefox and Chrome on Fedora.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406319801, 'spacePHID': None, 'dateCreated': 1405201260, 'dateModified': 1417048871, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67933', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'A menu item of VisusalEditor in Ukrainian Wikipedia has been changed by mistake.', 'description': {'raw': \"**Author:** `002soym`\\n\\n**Description:**\\nIntention:\\nTo edit a wiki code\\n\\nSteps to Reproduce:\\nA menu item of VisusalEditor in Ukrainian Wikipedia has been changed by mistake. Now we have instead of the correct menu item '''Редагувати код''' (Edit code) the absolutely incorrect '''Править викитекст'''. It's not even in Ukrainian.\\n[https://uk.wikipedia.org/wiki/MediaWiki:Visualeditor-ca-editsource shows] the correct label here.\\n\\nActual Results:  \\nmenu item '''Править викитекст''' \\n\\nExpected Results:  \\nmenu item '''Редагувати код''' (Edit code)\\n\\nReproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://uk.wikipedia.org/wiki/%D0%92%D1%96%D0%BA%D1%96%D0%BF%D0%B5%D0%B4%D1%96%D1%8F\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405130110, 'spacePHID': None, 'dateCreated': 1405130040, 'dateModified': 1417048657, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67911', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Option to use VisualEditor not showing up on non-enwiki projects', 'description': {'raw': \"In production in beta. Steps to repro:\\n\\n1. Go to French, Polish, or Russian Wikipedia (where VE should be the default editing experience). \\n2. Opt into beta, log in, and attempt to edit a page.\\n\\nExpected: I am taken to VE editing mode, since VE is the default editing experience on those projects.\\n\\nActual: I am taken to wikitext editing. Furthermore, I don't have the option to switch to VE editing in the edit window (the cog that shows me the drop-down menu is missing). \\n\\nAlso observed on Portuguese and Spanish Wikipedia. It seems to be everywhere except enwiki.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-yu5wnmvkjecufsjgh2fa', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405116083, 'spacePHID': None, 'dateCreated': 1405115820, 'dateModified': 1405116083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67892', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: new autoadded reflist does not display when in VE edit mode', 'description': {'raw': 'new reflist behavior adds in the reflist to the saved/rendered display like TOC but when in VE edit mode the reflist is not displayed, which is confusing, especially when user is adding references\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417480920, 'spacePHID': None, 'dateCreated': 1405104840, 'dateModified': 1417480920, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67873', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Table cell templates are editable, but their re-rendering is broken', 'description': {'raw': 'Screenshot\\n\\nTable cell templates are editable, but their re-rendering is broken.\\n\\nExample: try modifying any of the table cell templates at https://nl.wikipedia.org/wiki/Gebruiker:Ad_Huikeshoven/jh?uselang=en&veaction=edit#Prestatietabel\\n\\nThey can be edited, such an edit can be saved and results in correct wikitext, but is rendered broken (the markup is rendered as text, instead of creating a table cell).\\n\\n(Found when playing with bug 67850.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://nl.wikipedia.org/wiki/Gebruiker:Ad_Huikeshoven/jh?uselang=en&veaction=edit#Prestatietabel\\n\\n**Attached**: {F14539}'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'dateClosed': 1436461309, 'spacePHID': None, 'dateCreated': 1405090260, 'dateModified': 1436461309, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67856', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawns and reverse typing', 'description': {'raw': 'Reported on fr.wp. Verified so far in Win 7 (Chrome and FF). \\n\\nYou can use this page https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_%28WMF%29/Prove2&oldid=105329509 to reproduce.\\nSteps:\\n\\n    1) Place the cursor immediatly after \"croisières\", before the non-breaking space.\\n    2) Add a space. This space is added after the cursor.\\n    3) Press Right Arrow then Left Arrow to make the cursor move, but it is finally at the same place.\\n    4) Add a space : the pawn appears in the link.\\n    5) Again right arrow, then add another space : a second pawn appears after the link.\\n    6) If you try to type text after the last pawn, only a pawns appears. No text.\\n\\n    To have text written from right to left :\\n    1) Place the cursor immediatly after \"croisières\", before the non-breaking space.\\n    2) Add a space. This space is added after the cursor.\\n    3) Press Right Arrow to make the cursor move.\\n    4) Add a space : the pawn appears.\\n    5) Again right arrow, then add another space (so efter the colon) : a second pawn appears.\\n    6) Left arrow twice (cursor before the colon) and type text : it\\'s written from right to left.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406341653, 'spacePHID': None, 'dateCreated': 1404992460, 'dateModified': 1406341653, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67797', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Cite tool\\'s dropdown menu is not displaying (it\\'s \"underneath\" the toolbar)', 'description': {'raw': \"Cite menu is inaccessible\\n\\nThe dropdown menu for the Cite tool is not displaying correctly for me in Safari 6.1.4.  \\n\\nThe screenshots show two different font sizes/resolutions.  This isn't consistent for me.  I zoomed in before it happened the first time.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14279}\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404965618, 'spacePHID': None, 'dateCreated': 1404928980, 'dateModified': 1404965618, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67741', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support non-image media (tracking)', 'description': {'raw': \"We currently don't. We should.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xqqqgn2dels45flxw5kb', 'dateClosed': 1470527026, 'spacePHID': None, 'dateCreated': 1404850380, 'dateModified': 1470527038, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67689', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Mobile: After saving a redlink page, the user is redirected to the previous page (typically the page the redlink was on) rather then the newly created page', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with Mobile VE with desktop safari or iOS safari\\n2.Create a link to a new page and save the page\\n3.Go to that new page that you just created link to\\n4.Edit that page and save it\\n\\nObserved Result:\\n\\nIt will redirect you to the page that you started with at step1\\n\\nEnvironment:Betalabs and test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60848\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65041\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=69559'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412632719, 'spacePHID': None, 'dateCreated': 1404775860, 'dateModified': 1412632719, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67639', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: A pawn appears while trying to type something to the the left/right of a reference note in Firefox', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Select a reference note in VE with firefox\\n2.Press right/left\\n3.Type something\\n\\n\\nObserved Result:\\nA pawn appears instead of the text\\n\\n\\nSee the screenshot attached\\n\\nEnvironment:Production (en.wiki)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14615}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404763355, 'spacePHID': None, 'dateCreated': 1404763200, 'dateModified': 1417570771, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67620', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clear styling does not work when the cursor is the middle of a text but de-selects the option from style menu', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Make a text Bold\\n3.Now place your cursor somewhere in the middle of that text\\n4.Select the option \"Clear Styling\" from style menu\\n\\n\\nObserved Result:\\nThe text is still styled as Bold, however the highlight on Bold option in style menu is not anymore there.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14613}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404762894, 'spacePHID': None, 'dateCreated': 1404762480, 'dateModified': 1417570771, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67619', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow users to disable VE in their preferences on otrswiki', 'description': {'raw': 'RD asked me to file this bug for him.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404688768, 'spacePHID': None, 'dateCreated': 1404687060, 'dateModified': 1404688768, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67574', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link annotation gets cut off when label contains linktrail end characters', 'description': {'raw': 'Screen recording of bug\\n\\n1. Edit page with a link is applied to multiple words in sequence.\\n   such as \"QUnit - Foo bar baz\".\\n2. Select part of it (e.g. \"Foo bar baz\")\\n3. Type something new (e.g. \"Quux\")\\n\\nExpected:\\n\\nQuux replaces \"Foo bar baz\" and is a link as well.\\n\\nActual:\\n\\nThe text is removed, the link now ends at \"-\" and the inserted text \"Quux\" is just plain unlinked text.\\n\\nThis might have to do with linktrail processing and the operation happening as separate delete/insert.\\n\\n\\nVideo: http://cl.ly/2K1q1A471G2N\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14240}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404353692, 'spacePHID': None, 'dateCreated': 1404349800, 'dateModified': 1441911418, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67447', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector should indicate link target when applied via keyboard shortcut', 'description': {'raw': 'Screen recording of bug\\n\\n1. Select text\\n2. cmd+K (Mac) to apply a link annotation\\n\\nExpected:\\n\\nEither it shows page titles with a default selection (e.g. a link to the exact link text), or only shows suggestions and require I pick one.\\n\\nActual:\\n\\nBecomes link to the exact link text but with no way of knowing that, nor with an intuitive way to select a different target (see attached video).\\n\\nhttp://cl.ly/3P2P2E1a1w1A\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14235}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404353268, 'spacePHID': None, 'dateCreated': 1404349500, 'dateModified': 1441911418, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67446', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid exceptionally slow for one user's set-up (IIS), so editing pages times out every time\", 'description': {'raw': '**Author:** `jazeckel`\\n\\n**Description:**\\nwiki debug log for navigating to and attempting to edit a page\\n\\nI am attempting to configure the VisualEditor REL1_23 to run with my MediaWiki instance.  I am using MediaWiki 1.23 and it is a private wiki.  It\\'s served by IIS on Windows Server 2012 R2.  I am able to create a very simple page using it, although it runs slowly.  However, any attempt to edit the page -- even a page containing only one simple sentence -- times out with Parsoid.  I ran all of the Parsoid tests following installation and they all passed, and from Parsoid\\'s test webpage (localhost:8000) I was able to run those tests and they succeed quickly.  However, I can\\'t edit any pages of my wiki.  This is the output from the Parsoid service during an edit attempt:\\n\\n[warning/api][null/Test] Failed API request, 8 retries remaining.\\n[info][localhost/Test] starting parsing\\n[info][localhost/Test?oldid=834] completed parsing in 45006 ms\\n\\nThe completed parsing line occurs after I click cancel on the prompt telling me the request timed out.  When I had the timeout set to 60s, I would see \"8 tries remaining\" and then \"7 tries remaining\" before it timed out (I have since changed the timeout to 45s).  The content of the page in this example is simply \"this is a visual editor test.\"\\n\\nRelevant information:\\n- Windows Server 2012 R2\\n- IIS v8.5.9600.16384\\n- 32-bit node.js\\n- Parsoid on port 8000\\n- Browser used is Chrome 35.0.1916.153 m\\n- MediaWiki 1.23, set to require log in to view/edit\\n- same problem in all skins that VisualEditor runs on\\n\\nA debug log from MediaWiki is attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: other\\n**Platform**: PC\\n\\n**Attached**: {F14490}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404321762, 'spacePHID': None, 'dateCreated': 1404148260, 'dateModified': 1404344823, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67313', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Core message reuse', 'description': {'raw': 'VisualEditor correctly introduces visualeditor-ca-editsource, visualeditor-ca-editsource-section to change meaning of action=edit links, but it seems to reuse messages such as editsection, monobook-view-edit, vector-view-edit for its own veaction=edit links.\\nhttps://www.mediawiki.org/wiki/Localisation#Avoid_message_reuse\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411782238, 'spacePHID': None, 'dateCreated': 1404045240, 'dateModified': 1621892210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67274', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'CirrusSearch: suggesting categories which do not exist and never did', 'description': {'raw': 'On it.wp, trying to add a category in VisualEditor.\\nIf you start typing \"Terminologia dello\", you\\'ll be prompted to add 3 categories.\\nOne of them though, \"Terminologia dello sport\", doesn\\'t exist and never did.\\n(Also, no articles or templates with that name).\\n\\nI\\'m told this link could be useful:\\nhttps://it.wikipedia.org/w/api.php?format=json&uselang=en-gb&action=query&list=allcategories&acprefix=Terminologia+dello+sport&acprop=hidden&redirects=\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1478127989, 'spacePHID': None, 'dateCreated': 1404023280, 'dateModified': 1478127989, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67269', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make new multi-part transclusions always put newlines between each transclusion (default whitespace of \\\\n)', 'description': {'raw': 'Some tables built from complex templates assume that there will be line breaks between the templates, so that this works:\\n\\n{{tabletop}}\\n{{tablerow}}\\n{{tablerow}}\\n{{tablerow}}\\n{{tableend}}\\n\\nbut this does not:\\n\\n{{tabletop}}{{tablerow}}{{tablerow}}{{tablerow}}{{tableend}}\\n\\n\\nThere\\'s another problem with transclusions containing content, which can be seen by opening the transclusion at https://en.wikipedia.org/wiki/Kilt#See_also in VisualEditor.  The template lines are fine, but the \"Content\" sections must always start with a blank line, to make up for the absence of line breaks at the end of the templates.  \\n\\nThe solution for both of these is probably the same:  Complex transclusions should always have line breaks after the templates.  I haven\\'t been able to find any (in my quick search) that would break if this were implemented.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405409435, 'spacePHID': None, 'dateCreated': 1404015660, 'dateModified': 1405409435, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67268', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor crashes if the DefaultSummaries gadget is enabled', 'description': {'raw': \"VisualEditor crashes when you try to save if the Defaultsummaries gadget is enabled. (https://en.wikipedia.org/wiki/MediaWiki:Gadget-defaultsummaries.js )  This is new; it used to work.\\n\\nWorkaround:  Disable the gadget.\\n\\n(Might be Firefox-specific.  I haven't tested it.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403970159, 'spacePHID': None, 'dateCreated': 1403930460, 'dateModified': 1403970159, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67236', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: deleting the text from the article and converting it to a redirect page still leaves in categories and Other Stuff', 'description': {'raw': \"Deleting the text from the article and converting it to a redirect page still leaves all the categories in it, as well as Other Stuff such as magic words and invisible templates.\\n\\nThis is a regression in comparison to the source editor, where the editor could just delete everything and be sure that categories, magic words, invisible templates and everything else is gone.\\n\\nJust redirecting an article shouldn't necessarily remove everything, because it's actually possible that the editor wants to leave the article in a category. Some projects, including enwiki, have categories, templates etc. in redirect pages. But probably some kind of a warning should be shown.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403885598, 'spacePHID': None, 'dateCreated': 1403884980, 'dateModified': 1417570773, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67200', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Error saving settings: ... have cookies enabled', 'description': {'raw': 'Clicking Save looks OK\\n\\nAfter logging in, attempt to set beta settings. \\n\\nAfter clicking Save, get message \"Error saving settings. Please make sure that you have cookies enabled\"\\n\\nThis causes test failures such as https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/36/testReport/(root)/VisualEditor/Going_back_from_save_screen_in_VisualEditor/\\n\\nThis is probably a problem in core, and very likely related to the VE bug https://bugzilla.wikimedia.org/show_bug.cgi?id=65709\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65709\\n\\n**Attached**: {F14190}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408054772, 'spacePHID': None, 'dateCreated': 1403825280, 'dateModified': 1408054772, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Tab order is bad in the Template dialog', 'description': {'raw': 'This is the same sort of problem as bug 67153 in the Save dialog.  \\n\\n\\nHere is the incomplete tab order in Safari 6:\\n\\n1.  Insert > Template\\n\\n2.  The cursor starts in the template name field.  (It doesn\\'t matter if you type something now.)  Tab:\\n\\na) \"Add template\" button\\nb)  Nothing—cursor disappears\\nc) \"Apply changes\" button \\nd) \"Show options\" (visually backwards, but maybe that\\'s okay)\\ne)  Escape the template dialog into the mess described in the Safari-specific bug 67156.\\n\\nNot accessible:  The X-to-cancel button at the top of the dialog.\\n\\n\\n\\nHere is the even more incomplete tab order in Firefox 30:\\n\\n1.  Insert > Template\\n\\n2.  The cursor starts in the template name field.  (It doesn\\'t matter if you type something now.)  Tab:\\n\\na) the browser\\'s URL bar\\nb) the browser\\'s search box (for search engines)\\nc) who knows?  It disappears.\\nd) the main Wikipedia search box \\ne) the top of the article\\nf) the MediaWiki \"More\" menu (where \"Move\" hides)\\ng) the icon/go button for the main Wikipedia search box\\nh) the languages (gear icon) button\\ni) the New template dialog (as a whole, not any useful piece of it)\\nj) who knows?  It disappears again.\\nk) the New template dialog (as a whole, not any useful piece of it)\\nl) who knows?  It disappears again.\\nm) back to the field for the template name, repeating endlessly.\\n\\nWhere it doesn\\'t go is:\\n\\nn) the Add template button\\no) the Show options button\\np) to the X at the top of the dialog box, so you can cancel adding a template and go back to editing. \\n\\n\\nIMO the order in all cases ought to be:\\n\\na)  Start in the template name field\\nb) \"Add template\" button\\nc) \"Apply changes\" button \\nd) \"Show options\"\\ne)  X to cancel the dialog and go back to editing\\n\\nand nothing else (repeat endlessly, if the person keeps pressing tab).\\n\\nI\\'m willing to have C and D reversed, because it would be visually more obvious (for left-to-right languages).  However, most users won\\'t be clicking that button, so it\\'d be more efficient to have it later in the tab order.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67153'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404849994, 'spacePHID': None, 'dateCreated': 1403809500, 'dateModified': 1417570759, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67159', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Tab order or behavior is bad in the Save dialog', 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Open a page and make a change.  \\n\\n2.  Click the Save button.\\n\\n3.  Tab.  The cursor starts in the edit summary box (good) and goes to (using en.wp/Vector):\\n\\na) tick box for minor edit\\nb) link to the minor edit help page**\\nc) tick box for watching the page\\nd) three links in the licensing statement**\\ne) Review your changes button\\nf) Save button (inside the dialog box)\\ng) the browser's URL bar\\nh) the main Wikipedia search box \\ng) the Cancel button (on VisualEditor's toolbar, and it works if you press return now)\\nh) the Save button (on VisualEditor's toolbar)\\ni) the top of the article\\nj) the slug at the top of the article, where it gets stuck forever.\\n\\nWhere it doesn't go is:\\n\\nk) to the X at the top of the dialog box, so you can cancel saving and go back to editing. \\n\\n\\n** I'd like these links to be skipped, but (a) maybe this is controlled by a browser setting and (b) maybe my opinion is in the minority.  I'd like these to be skipped so that I can save a page without having to press tab eight times between the edit summary and the final save button.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67159\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404848147, 'spacePHID': None, 'dateCreated': 1403806620, 'dateModified': 1443278798, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67153', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  In which it is apparently impossible to create a redirect to [[Foo]] because the list of possible links does not scroll', 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Go to Page settings to create a redirect on the English Wikipedia.\\n\\n2.  Type \"foo\" (an actual article—well, a redirect to an actual article about metasyntactic variables) in the field.\\n\\n3.  Look at the search results, which are all about football (plus one for [[Foot (length)]] and one for the US FDA).  Think, \"I must need to scroll down past all of this sports stuff\"... but it doesn\\'t scroll.\\n\\n\\nIf you click on any of these items, then your correct link to \"Foo\" gets replaced by whatever was highlighted.  \\n\\nIt turns out that you can actually get the link to \"Foo\", by clicking on any place outside the dialog box (to make the search results go away) and then clicking on \"Apply changes\", but this is really Not Good.  To make things worse, due to bug 61861, you can\\'t see what actually happened without either going to Review your changes or saving the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406753647, 'spacePHID': None, 'dateCreated': 1403805780, 'dateModified': 1406753647, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67150', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Section edit link is not appearing in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Load any page with sections in Betalabs\\n\\nObserved Result:\\nThere is no link for editing any section\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14604}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403735184, 'spacePHID': None, 'dateCreated': 1403732280, 'dateModified': 1417570773, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67100', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Creating a new link is unusable', 'description': {'raw': 'We have an imho fundamentally broken model for inserting links. I don\\'t know why we show the Link tool in the toolbar when there is no selected text because it\\'s pretty much impossible.\\n\\nThe tool is optimised for adding a link to existing text (or typing the label out first, which is unnatural for anyone who hasn\\'t acquired it as a habit due to this bug), and for changing the link target.\\n\\nA few use cases:\\n* Add link in list\\n  - Add item item (press return after the last item or create new list)\\n  - User has a page or url he wants to link to\\n  - Press \"Link\" tool\\n  - Type target page name or url\\n  - User wants to insert link with that label, or (more likely in case of an external link) have the label be something that is not the link target.\\n\\n* Add link while typing text\\n* Update mistake in text (e.g. text mentioning \"born in the US\" or \"born in 1955\" and the link and label of US/1955 should be another country or year).\\n\\nI think the frequency at which one needs to only update the link label or link target are significantly lower, but the other cases are certainly not edge cases.\\n\\nHere\\'s a recording of me painfully trying to insert a link:\\nhttp://cl.ly/3s460Q442L3S\\n\\nTo this day I have not once been able to insert a link without running into a bug that would\\'ve discouraged me as a user.\\n\\nI thought I filed these as separate bugs at some point but I can\\'t find them. Issues encountered in the video:\\n\\n1) Inserting a plain external link and then typing its label causes an exception (a pawn appears; see video).\\n\\n2) The link inspector seems to lack an intuitive way to apply the change. During the video you can see me at various points being confused and eventually pressing \"Back\" (or pressing Enter) to apply the change. Especially when inserting a new link or changing an internal link to an external link (albeit by accident) it\\'s counter-intuitive to not see anything in the page or to continue seeing a red link when I\\'ve already selected the value from the dropdown menu.\\n\\nI think when the user selects the value from the dropdown menu, that\\'s when we can apply the change (but keep the inspector open). An interface component like this one that has no \"Save\" button and implies automatic saving should either make sure the object being changed has no visual impact or make sure it is applied live (And not suddenly when clicking away / blurring the inspector)\\n\\n3) Adding a label (or rather, due to the lack of an input for the label, being forced to change the implied label) is unusable due to lack of text selection within the boundaries of the link (see video).\\n\\n4) After the link is inserted, the link text is selected in the surface (the link target in the inspector, which is still open, is also selected). It\\'s not clear whether typing will replace the label or the link target (see video).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403717655, 'spacePHID': None, 'dateCreated': 1403713920, 'dateModified': 1478462507, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67086', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Toolbar alignment out of whack', 'description': {'raw': 'screenshot of problem\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/MediaWiki?veaction=edit\\n\\n**Attached**: {F14540}'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403734997, 'spacePHID': None, 'dateCreated': 1403686200, 'dateModified': 1417570773, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67071', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Section headings look like they've been removed, but they're still present when the page is saved\", 'description': {'raw': 'Why did it merge that subsection heading into the paragraph I was typing?\\n\\nSteps to reproduce:\\n\\n1.  Start editing a page with existing section headings.  Create a new paragraph above one of the section headings.\\n\\n2.  At some point, it looks like the ==Section heading== has accidentally been merged to the paragraph that you\\'re typing.  It\\'s no longer present below (just a blank line where it had been), and the text of the section heading is now (in paragraph formatting) in the paragraph you\\'re typing.\\n\\n3.  Assume it\\'s your fault (did you backspace?), and clean it up.  Replace the missing section heading.  Finish typing your paragraph, if necessary; you might have to do this a couple of times if the error recurs.\\n\\n4.  Save the page.\\n\\n5.  Check the diff, e.g., https://en.wikipedia.org/w/index.php?title=Candy_making&diff=prev&oldid=614021270\\n\\n6.  Ask yourself, why are there three section headings named ==Safety== in a row?\\n\\n\\nIf you don\\'t replace the \"missing\" section heading, then everything works out:\\nhttps://en.wikipedia.org/w/index.php?title=Candy&diff=614296008&oldid=614177828\\n\\nAll of the attachments are from this diff.  I\\'ve only seen this in Firefox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14503}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423675861, 'spacePHID': None, 'dateCreated': 1403656140, 'dateModified': 1438734917, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67061', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Unable to select type \"string/line\" in the GUI editor', 'description': {'raw': 'I don\\'t see the option to change the type of a parameter to \"string/line\" when I edit\\nhttps://pt.wikipedia.org/wiki/Template:Marca_de_projeto/dados?action=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60693'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409440621, 'spacePHID': None, 'dateCreated': 1403369520, 'dateModified': 1409440621, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66920', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor fails to provision with rbenv error', 'description': {'raw': \"The error is:\\n\\nerr: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Browsertests::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Ruby::Bundle[/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]/Exec[bundle-install-/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/test/browser]: Could not evaluate: Could not find command '/usr/local/rbenv/shims/bundle'\\n\\n---\\n\\nFull list of roles:\\n\\n  accountinfo                geshi                      parsoid                 \\n  analytics                * gettingstarted             pdfhandler              \\n  antispam                   globalusage                poem                    \\n  antispoof                * guidedtour                 popups                  \\n  apisandbox                 gwtoolset                  proofreadpage           \\n  apparmor                   hadoop                     scribunto               \\n  babel                      hhvm                       simple_miser            \\n  betafeatures               hive                       simple_performant       \\n  browsertests               https                      sitematrix              \\n  centralauth                jsduck                     templatedata            \\n  centralnotice              labs_initial_content       textextracts            \\n  chromium                   mantle                     thumb_on_404            \\n  cirrussearch               massmessage                timedmediahandler       \\n  cite                     * math                       translate               \\n  cldr                       mathsearch                 uls                     \\n  codeeditor                 mleb                       uploadwizard            \\n  commonsmetadata          * mobilefrontend             urlshortener            \\n  confirmedit                multimedia                 vectorbeta              \\n  doublewiki                 multimediaviewer         * visualeditor            \\n  echo                       mysql                      wikidiff2               \\n  education                  navigationtiming         * wikieditor              \\n* eventlogging               newusermessage             wikihiero               \\n  flow                       oauth                      wikilove                \\n  fss                        pagedtiffhandler           wikimania_scholarships  \\n  fundraising                pageimages               * wikimediaevents         \\n  gadgets                    pagetriage                 wikimetrics             \\n  geodata                  * parserfunctions            xhprof\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-7bifphmxtcqgvdofuzla', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404938920, 'spacePHID': None, 'dateCreated': 1403054280, 'dateModified': 1506469729, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66764', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid outputs <figure> inside of <b>', 'description': {'raw': 'Wikitext: \\'\\'\\'foo[[File:Image.jpg|thumb]]bar\\'\\'\\'\\n\\nResulting DOM: <body><b><figure><a><img /></a></figure>bar</b>\\n\\nBlock nodes like figure aren\\'t supposed to occur inside of inline-ish (annotation) tags like b. When confronted with this, VisualEditor alienates the image to preserve its sanity (data model consistency), so bolded images can\\'t be edited in VE.\\n\\nReported by mattk_ on IRC.\\n\\n$ echo \"\\'\\'\\'foo[[File:Image.jpg|thumb]]bar\\'\\'\\'\" | node tests/parse.js\\n\\n<!DOCTYPE html>\\n<html prefix=\"dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/\"><head prefix=\"mwr: http://en.wikipedia.org/wiki/Special:Redirect/\"><meta property=\"mw:parsoidVersion\" content=\"0\"/><link rel=\"dc:isVersionOf\" href=\"//en.wikipedia.org/wiki/Main_Page\"/><title></title><base href=\"//en.wikipedia.org/wiki/Main_Page\"/><link rel=\"stylesheet\" href=\"//en.wikipedia.org/w/load.php?modules=mediawiki.skinning.elements|mediawiki.skinning.content|mediawiki.skinning.interface|skins.vector.styles|site|mediawiki.skinning.content.parsoid&amp;only=styles&amp;debug=true&amp;skin=vector\"/></head><body data-parsoid=\\'{\"dsr\":[0,37,0,0]}\\' lang=\"en\" class=\"mw-content-ltr mw-body-content\" dir=\"ltr\"><b data-parsoid=\\'{\"dsr\":[0,36,3,3]}\\'>foo<figure class=\"mw-default-size\" typeof=\"mw:Image/Thumb\" data-parsoid=\\'{\"optList\":[{\"ck\":\"thumbnail\",\"ak\":\"thumb\"}],\"dsr\":[6,30,2,2]}\\'><a href=\"./File:Image.jpg\" data-parsoid=\\'{\"a\":{\"href\":\"./File:Image.jpg\"},\"sa\":{},\"dsr\":[8,28,null,null]}\\'><img resource=\"./File:Image.jpg\" src=\"//upload.wikimedia.org/wikipedia/en/thumb/7/78/Image.jpg/220px-Image.jpg\" height=\"30\" width=\"220\" data-parsoid=\\'{\"a\":{\"resource\":\"./File:Image.jpg\",\"height\":\"30\",\"width\":\"220\"},\"sa\":{\"resource\":\"File:Image.jpg\"}}\\'/></a></figure>bar</b>\\n</body></html>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1532671743, 'spacePHID': None, 'dateCreated': 1403043660, 'dateModified': 1532723657, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66749', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid's local interwiki link check fails on non-Wikipedia wikis\", 'description': {'raw': 'Currently, Parsoid runs the following check to tell if an interwiki link points at the current wiki [1]:\\n\\nif ( interwikiInfo.prefix === env.conf.wiki.iwp.replace( /wiki/, \\'\\' ) ) {\\n\\nObviously this is inadequate when the wiki name doesn\\'t end in \"wiki\". (It\\'s slightly unclear to me what \"iwp\" is; it claims to be an interwiki *prefix*, but some of the tests set it to \"enwiki\", so I\\'m assuming it\\'s actually the DB name.)\\n\\nSee http://parsoid.wmflabs.org/_rt/mediawikiwiki/VisualEditor:Local. Currently the first link is \"mw:WikiLink\" and the second is \"mw:ExtLink\", which is wrong. The PHP parser renders them identically as internal links.\\n\\n---\\n[1] http://git.wikimedia.org/blob/mediawiki%2Fservices%2Fparsoid.git/18e31a06252db3813fe844b62f15248289cdf4cb/lib%2Fext.core.LinkHandler.js#L106\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411493364, 'spacePHID': None, 'dateCreated': 1403000460, 'dateModified': 1411493364, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66709', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Typing diacritics results in stray accent marks at the top of the page in Chrome', 'description': {'raw': 'María typed her name in VisualEditor on a Mac:  [SHIFT] m + a + r + [OPTION] e + i + a. \\n\\nShe runs Chrome on a MacBook Pro with a U.S. keyboard.  The result was this:\\n\\n\\n[top of page]\\n´\\n\\nLots of text here\\n\\nMaría\\n\\nThe rest of the page\\n\\n[end of page]\\n\\n\\nUsing a normal keyboard shortcut to add accents to characters should not result in  stray \"´\" characters at the top of the page.\\n\\nSee https://office.wikimedia.org/w/index.php?diff=113478&oldid=113425 for an example.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403127698, 'spacePHID': None, 'dateCreated': 1402958220, 'dateModified': 1403301845, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66693', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Getting Error loading data from server while reviewing changes from Save dialog', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Edit a page\\n3.Click on \"Save Page\"\\n4.Click on \"Review your changes\"\\n\\nObserved Result:\\n\\nGetting Error loading data from server while reviewing changes from Save dialog \\n\\nSee the screenshot attached\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13711}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402943552, 'spacePHID': None, 'dateCreated': 1402942920, 'dateModified': 1417570776, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66681', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Breaking VisualEditor breaks wikitext editor', 'description': {'raw': 'If VisualEditor ever throws an exception, which seems to be happening a lot, this means that the editor is inaccessible unless you resize the window and refresh.\\n\\nWhen an error occurs the wikitext editor should be loaded instead.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411691088, 'spacePHID': None, 'dateCreated': 1402941240, 'dateModified': 1411691088, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66678', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Re-using references isn't working very well\", 'description': {'raw': 'Incident #1:\\n\\nAdd a reference.  Try to re-use it.  It\\'s not in the list at all.\\n\\n\\nIncident #2:\\n\\nAdd a reference using the Cite tool.  Try to re-use it.  It\\'s not in the list at all.  Add a plain <references /> block (rather than {{reflist}}).  Go back and try to re-use it.  Now it\\'s there.\\n\\n\\nIncident #3:\\n\\nAdd a reference.  Try to re-use it.  Only the number (\"[1]\") is present in the references list; the old refs are all listed correctly.  Cancel and go look at the new ref to make sure that it actually has contents.  Try to re-use it again.  Now the full description appears.  (Perhaps it was just being slow?  Perhaps it needed something else to trigger it?)\\n\\n\\n(All of these happened in Firefox.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414810464, 'spacePHID': None, 'dateCreated': 1402789800, 'dateModified': 1414810464, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66629', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Make it possible to click on a link or URL that's inside a template (to open the link in another tab)\", 'description': {'raw': 'There are a lot of templates that create or display links to other pages.  It would be nice if it were possible to click on those links (to open the linked pages in another tab) while editing VisualEditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402688065, 'spacePHID': None, 'dateCreated': 1402600620, 'dateModified': 1417570777, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66549', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'add \"Cite\", \"TemplateData\", \"ParserFunctions\" and Lua extensions for \"visualeditor\" role', 'description': {'raw': 'References in VE do not work properly in the vagrant VM without also having the Cite extension in place.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402605806, 'spacePHID': None, 'dateCreated': 1402527600, 'dateModified': 1496861992, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66504', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'bare wiki + VE does not handle References properly', 'description': {'raw': 'Use existing references disabled for page with references\\n\\nfound in the course of enabling browser tests for the Vagrant role visualeditor: \\n\\nIn the mediawiki visualeditor role and also in a bare wiki having the VisualEditor extensions, references are not handled properly.  \\n\\nIn the pure page view the existing references are not interpreted by the <references /> tag.  See screen shot. \\n\\nIn VE, the \"Use an existing reference\" button is disabled. See screen shot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13915}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402527520, 'spacePHID': None, 'dateCreated': 1402527060, 'dateModified': 1402527520, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66502', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Footnote number is not localized while editing', 'description': {'raw': 'See the URL for an example.\\n\\nThe reference numbers are not localized in languages that use non-European numbers, such as Arabic and Persian. They are localized correctly while viewing the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://fa.wikipedia.org/wiki/User:Amire80/ref-numbers'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402329599, 'spacePHID': None, 'dateCreated': 1402213680, 'dateModified': 1417570779, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66338', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Javascript error when launching desktop VisualEditor (target.createSurface is not a function)', 'description': {'raw': \"Whenever I try to launch the desktop VE, I get a JS error...\\n\\nIn Firefox: 'target.createSurface is not a function'\\nIn Chrome: 'Uncaught TypeError: undefined is not a function'\\n\\nIn both cases it comes from ve.init.mw.Target.js, line 1312:\\ntarget.surface = target.createSurface( dmDoc );\\n\\nThe error doesn't happen in mobile VisualEditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402081615, 'spacePHID': None, 'dateCreated': 1402081500, 'dateModified': 1417570780, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66276', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'tracking: Flow loses session/token information', 'description': {'raw': 'Seen only one time:  https://wmf.ci.cloudbees.com/job/Flow-en.wikipedia.beta.wmflabs.org-linux-chrome/465/\\n\\nAs a logged-in user, create a new topic in Flow.  Topic was saved as anonymous, even though user logged in successfully and test showed no sign of user logging out. \\n\\nI want to note this because of the similarity to an intermittent issue when switching edit modes in VisualEditor, bug 65709\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\n{T67709}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-kms5nmb5gvqzcdep3cnl', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kms5nmb5gvqzcdep3cnl', 'dateClosed': 1418317389, 'spacePHID': None, 'dateCreated': 1401805680, 'dateModified': 1489594276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66076', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Duplicate setting of named parameter in template removed when you edit the template in some unrelated way', 'description': {'raw': '\"visual editor did more than i told it to: https://en.wikipedia.org/w/index.php?title=Cameroon&diff=611127082&oldid=610427158 \"\\n\"hmm looks like ve actually removed a duplicate parameter when i made that edit\"\\n\\nSeems this occurs when you edit a template in some way (e.g. adding a new parameter), if a named parameter has been set twice.\\n\\nNot sure if this is intended behaviour or not. Bug might be a dupe, might be in Parsoid instead of VE, or something else.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401758985, 'spacePHID': None, 'dateCreated': 1401654960, 'dateModified': 1401758985, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66009', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Visual inconsistencies between OOJS and VisualEditorOverlay', 'description': {'raw': 'exit overlay\\n\\nSee attachments\\n\\n* Different X icons used for VisualEditor close and OOUI close\\n* There are vertical borders in the VE toolbar\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13867}'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406571087, 'spacePHID': None, 'dateCreated': 1401478260, 'dateModified': 1406571087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65957', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Existing page shows up under New Page section inside Link Inspector in production', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page\\n2.Attempt to insert a link with an existing target page such as \"Test\"\\n\\nObserved Result :\\n\\nThe page \"Test\" appears under the New Page section inside Link Inspector.\\nSee the screenshot attached\\n\\nEnvironment:\\nhttps://en.wikipedia.org/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13800}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402016305, 'spacePHID': None, 'dateCreated': 1401412020, 'dateModified': 1417570780, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65927', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  When editing a page in the Category: namespace, the contents of the category do not display upon saving', 'description': {'raw': \"Intention:\\nChange the contents of a category page (the description, not the files in it).  See https://commons.wikimedia.org/w/index.php?title=Category:Cuberdon&diff=prev&oldid=125000311\\n\\nSteps to Reproduce:\\n1. Open the page in VisualEditor.\\n2. Change the description.\\n3. Save the page.\\n\\nActual Results:  \\nUpon savingm the description was displayed, but not the contents of the category.\\n\\nExpected Results:  \\nYou should be able to see all the images in that category, not just the text at the top of the cat page.\\n\\nReproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401408756, 'spacePHID': None, 'dateCreated': 1401407520, 'dateModified': 1401408756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65925', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'toggle to VE makes UI spin forever, no VE, js error', 'description': {'raw': 'on http://en.m.wikipedia.beta.wmflabs.org/ as logged-in user; set Settings mode for VE access; edit a page; toggle VisualEditor mode\\n\\nbrowser shows spinner forever\\n\\njavascript error is \"Error: Module not found: toggle \\nError\\nmessage: \"Module not found: toggle\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401233082, 'spacePHID': None, 'dateCreated': 1401203820, 'dateModified': 1401233082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65810', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor introduces <nowiki> and then breaks template syntax', 'description': {'raw': 'https://pt.wikipedia.org/wiki/Jos%C3%A9_Antonio_Reyes?diff=38627387\\nhttps://pt.wikipedia.org/wiki/Jos%C3%A9_Antonio_Reyes?diff=38645684\\nhttps://pt.wikipedia.org/wiki/Jos%C3%A9_Antonio_Reyes?diff=39007919\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1442345202, 'spacePHID': None, 'dateCreated': 1401103500, 'dateModified': 1442573663, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65767', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Hypothetical generation of strange characters at the beginning of pages', 'description': {'raw': 'Seasoned Catalan Wikipedia editors are finding strange diffs done by new editors using VisualEditor. See these examples:\\n\\nhttps://ca.wikipedia.org/w/index.php?title=Laocoont_o_sobre_els_l%C3%ADmits_en_la_pintura_i_poesia&diff=13401584&oldid=13401089\\n\\nhttps://ca.wikipedia.org/w/index.php?title=Joan_Francesc_Ferrer_Sicilia&curid=1102012&diff=13399985&oldid=13399856\\n\\nhttps://ca.wikipedia.org/w/index.php?title=Pere_Formiguera_i_Sala&oldid=13189613\\n\\nhttps://ca.wikipedia.org/w/index.php?title=Pere_Formiguera_i_Sala&diff=13276699&oldid=13276658\\n\\nWe are still figuring out whether these strange edits are made on purpose or not, by humans or by some VisualEditor bug. Reporting here to check whether someone else has seen something similar elsewhere, or can shed some light.\\n\\nRelated discussion (in Catalan)\\nhttps://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Ajuda#Curiositat\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1422959740, 'spacePHID': None, 'dateCreated': 1400848080, 'dateModified': 1438734929, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65674', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Error thrown when try to create new pages in wikitext when VisualEditor is default', 'description': {'raw': \"Go to a page that doesn't exist.\\nClick edit so that VisualEditor loads.\\nToggle to source mode.\\nA JavaScript exception is thrown and the loader never clears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401305001, 'spacePHID': None, 'dateCreated': 1400686260, 'dateModified': 1401305001, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65587', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '503 from Parsoid in beta labs', 'description': {'raw': 'attempt to edit any page in http://en.wikipedia.beta.wmflabs.org/ with VisualEditor\\n\\nget error \"Error loading data from server: parsoidserver-http-bad-status: 503. Would you like to retry?\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400619845, 'spacePHID': None, 'dateCreated': 1400619780, 'dateModified': 1400619845, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65555', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Edit button seems to have no effect in Wikivoyage', 'description': {'raw': \"I'm currently trying to edit Wikivoyage and nothing happens when I click edit. Very weird. hash does change...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400612482, 'spacePHID': None, 'dateCreated': 1400588160, 'dateModified': 1400612482, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65529', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cannot switch to VisualEditor after a reload', 'description': {'raw': 'Could have sworn I raised this bug previously but here we go again..\\nLoad Article#editor/0 in alpha\\nSee VisualEditor.\\nSwitch to source editor.\\nNow refresh the page using browser.\\nWikitext editor loads.\\nAttempt to switch to VisualEditor.\\nFail.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402339452, 'spacePHID': None, 'dateCreated': 1400532480, 'dateModified': 1402339452, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65506', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Special character inserter breaks up links to other pages', 'description': {'raw': 'Steps to Reproduce:\\n1. Start with a link to another page, e.g., [[abc]].\\n\\n2. Use the special character inserter tool to add a special character, with the goal of producing something like this:  [[abc|aübc]].\\n\\n\\n\\nActual Results:  \\nInstead of [[abc|aübc]], you get [[abc|a]]ü[[abc|bc]].\\n\\n\\nReproducible: Always\\n\\nReproduced in Firefox and Safari.  May be related to Bug 60476 about character formatting?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400546427, 'spacePHID': None, 'dateCreated': 1400521320, 'dateModified': 1400546427, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65497', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'beta labs mysteriously goes read-only overnight', 'description': {'raw': 'I\\'ve been seeing this in the overnight runs of the browser tests in recent times. The build for VisualEditor will fail with a modal dialog that says \"Error loading data from server: readonly. The wiki is currently in read-only mode. Would you like to retry?\"\\n\\nHere is an example from the overnight run Sunday 18 May: https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/512/testReport/(root)/VisualEditor/Edit_with_strings__outline_example_____Editing_with_%C3%84%C3%8B%C3%8F%C3%96%C3%9C___Editing_with_%C3%84%C3%8B%C3%8F%C3%96%C3%9C___/\\n\\nI can\\'t think of any reason why beta labs would be in read-only mode late on a Sunday (PDT).  \\n\\nI suspect this may also be the cause of the occasional failure in other builds with less information, for example \"too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout)\" that we see in the MobileFrontend builds: too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/571/testReport/(root)/Check%20UI%20components/Check_existence_of_important_UI_components_on_other_pages_/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68349'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406300465, 'spacePHID': None, 'dateCreated': 1400509680, 'dateModified': 1425573999, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65486', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The \"Review changes\" button should be disabled when save dialog is locked during saving', 'description': {'raw': 'It should be disabled/muted like we do in other cases.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400507426, 'spacePHID': None, 'dateCreated': 1400507340, 'dateModified': 1417570824, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65485', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Lock sign appearing over the Edit option on Mobile VE even if user has Beta and Experimental Mode on', 'description': {'raw': 'Screenshot\\n\\nI am getting this issue while trying to edit :https://en.m.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox\\n\\nI dont know how I stumbled upon it, but I can not edit my sandbox anymore with Mobile VE in any device/browser.\\n\\nHowever, if I add it to or remove it from my watchlist by tapping on star, only then the lock disappears from the edit icon and I can edit.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13821}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401418027, 'spacePHID': None, 'dateCreated': 1400272200, 'dateModified': 1417570821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65414', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'EventLogging errors when switching from VisualEditor', 'description': {'raw': 'Load VE and switch to wikitext editor - triggers Validation error against schema MobileWebEditing: Missing property: funnel\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401321316, 'spacePHID': None, 'dateCreated': 1400195040, 'dateModified': 1401321316, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65378', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Opening a popupToolGroup should disable other tools', 'description': {'raw': 'Per the design mock-up at https://trello.com/c/xCo6uLAZ/9-5-references-dropdown-from-toolbar-styling (and a conversation with Kaity to confirm), when a user opens a popupToolGroup, all other tools in the toolbar should be disabled. Clicking off the popupToolGroup should close the popup and reactivate the other tools.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400272697, 'spacePHID': None, 'dateCreated': 1400193060, 'dateModified': 1417570825, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65374', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor not opening consistently in Firefox', 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Be me, or one of several other people, but not James F.  (This step may be difficult to reproduce.  ;-)\\n\\n2.  Login on Firefox. \\n\\n3.  Try to open an article in VisualEditor.\\n\\n4.  Wait.  Wait.  Wait.  Wonder why a page that pops open in Safari in less than five seconds still hasn't opened in Firefox despite the animated blue bar showing for more than 30 seconds now.\\n\\n5.  Wait.  Wait.  Wait.  Wonder if this is ever going to open.   \\n\\n6.  Give up and reload.  Maybe it works this time; maybe it doesn't.  If it doesn't, consider restarting Firefox.  That usually helps... for one article.  Then it goes back to its old behavior of occasionally opening a page, but not usually.\\n\\n\\nI don't feel like I have a lot of useful information to give you, but this has been a problem for a couple of weeks and does not seem to be getting better.  Logging out may help, according to https://en.wikipedia.org/w/index.php?oldid=608667917#VE_does_not_start\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1513167765, 'spacePHID': None, 'dateCreated': 1400181900, 'dateModified': 1513167765, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65365', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The Advanced Settings opens up as a default tab for an image if that was the tab user opened for the last edited image', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduced:\\n\\n1.Open a page with VE\\n2.Insert an image and go to the advanced Settings to make some changes\\n3.Apply the changes \\n4.Now insert another image and open the media settings for it\\n\\nObserved Result:\\nInstead of starting from General Settings as default tab, it opens up the Advanced settings, moreover if you edited say the image size section of the last image, the scroll bar position for the newly added image is also at the same exact position.\\n\\nTest Environment:Betalabs, test2 and production\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13579}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414094776, 'spacePHID': None, 'dateCreated': 1400103600, 'dateModified': 1417570684, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65318', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Is it possible to set up VisualEditor on other skins instead of Vector skin?', 'description': {'raw': '**Author:** `sean.chen`\\n\\n**Description:**\\nhi,\\n\\nwe are using MediaWiki for our intranet on Government of Ontario and we are amazed by the new and cool VisualEditor! And we want to set up VisualEditor while we upgrade our MediaWiki to version 1.23.x.\\n\\nHowever we need a customized skin instead of the default Vector skin. Is that possible to set up VisualEditor on a customized skin and how?\\n\\nthanks a lot,\\n\\n-Sean\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400097823, 'spacePHID': None, 'dateCreated': 1400096640, 'dateModified': 1417570826, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65304', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Cite options are appearing in the toolbar for Mobile VE', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with mobile VE\\n\\nObserved Result:\\n\\nThe Cite option is appearing in the toolbar which is not supposed to be there just yet? The drop-down menu does not have any background layout.Clicking on any of the options make VE completely stuck\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401417868, 'spacePHID': None, 'dateCreated': 1400094420, 'dateModified': 1417570821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65302', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Raster icons missing from VE toolbar', 'description': {'raw': \"Toolbar with missing tool icons – undo, redo, all dropdown arrows, link, help, page notices, page options (several icons missing in the dropdowns too)\\n\\nIf one forces VE to load with the raster icons, a bunch of them are missing.\\n\\nI'm not sure if this actually happens if any of the supported or greylisted browsers right now, but it blocks a fix for Opera 12 which doesn't handle elements with SVG background images and border-radius set.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14072}\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400869128, 'spacePHID': None, 'dateCreated': 1400005140, 'dateModified': 1417570824, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65271', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Scroll bar appears to be a bit wider on hovering over it in Firefox', 'description': {'raw': 'scroll bar gets wider\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in Firefox\\n2.Open any drop down box which has a scroll bar in it\\n3.Hover over the scroll bar\\n\\nObserved Result:\\nThe scroll bar becomes a bit wider \\n\\nSee the video attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13998}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401417923, 'spacePHID': None, 'dateCreated': 1399926660, 'dateModified': 1417570821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65240', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'false \"wiki is read-only mode\" message in beta labs', 'description': {'raw': 'Seen in automated tests in beta labs 11 May and 12 May (and occasionally earlier). \\n\\nBrowser encounters a modal dialog saying \"Error loading data from server: readonly. The wiki is currently in read-only mode. Would you like to retry?\"  The wiki is almost certainly not in read-only mode. \\n\\nThis may not actually be a VE error, I think it\\'s coming from line 337 of ve.init.mw.ViewPageTarget.js, but I haven\\'t tracked it to whatever is feeding the \"read-only\" status message to VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414160812, 'spacePHID': None, 'dateCreated': 1399915500, 'dateModified': 1425574002, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65228', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  If you open the image inspector, and the image doesn't have a type specified (like thumb), then you can't get out again\", 'description': {'raw': 'Steps to Reproduce:\\n1. Create a page that contains at least one image with no thumb or similar file specification, e.g., \\n\\n[[File:Example.jpg|Here\\'s an image.]]\\n\\n2. Open the page in VisualEditor.  \\n\\n3. Select the image and open the image inspector.\\n\\n4. Try to get out of the image inspector.\\n\\nActual Results:  \\nThe \"Advanced settings\" pane in the image inspector has a spinning death spiral and the error message, \"Size values are invalid. Could not retrieve original file size.\" \\n\\nThe X to close the image inspector does not respond.\\n\\n\\nReproducible: Always\\n\\nThis was first reported by Magioladitis for the pdf\\'s listed here:  https://el.wikipedia.org/w/index.php?oldid=4650532#.CE.94.CE.B9.CE.B1.CE.BB.CE.AD.CE.BE.CE.B5.CE.B9.CF.82\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1424219697, 'spacePHID': None, 'dateCreated': 1399759500, 'dateModified': 1438734938, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65166', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Firefox displays new lists incorrectly, if you've just pasted the text onto the page\", 'description': {'raw': 'Steps to Reproduce:\\n1. Type a few paragraphs of plain text in another document (e.g., an e-mail message with rich text turned off).\\n\\n2. Open VisualEditor.  Copy and paste your paragraphs into VisualEditor.\\n\\n3. Place your cursor in the first paragraph.  Click the list button to turn the first line (only) into a list.\\n\\nActual Results:  \\nThe entire pasted section is indented as if it were a list (a list separated by <br>, not with a bullet in front of each paragraph).\\n\\nHowever, when you save the page, only the first paragraph has actually been turned into a list.\\n\\nSee you at http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=92716&oldid=92715\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1533062282, 'spacePHID': None, 'dateCreated': 1399489680, 'dateModified': 1533062282, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65014', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The suggestion dropdown box gets stuck inside the transclusion dialog box in Firefox when you click on Add template button as soon as the dropdown box appears', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Template\\n3.Type something in the textbox\\n4.As soos as the suggestion dropdown box for template appears click on \"Add template\" button\\n\\nObserved Result:\\nThe first suggestion of the dropdown box gets stuck in the transclusion dialog box\\n\\nSee the screenshot attached\\n\\nBrowser:Firefox\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14019}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414095454, 'spacePHID': None, 'dateCreated': 1399419540, 'dateModified': 1417570684, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64982', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Templates using interwiki transclusions fails at API request', 'description': {'raw': 'In LocalSettings.php I enabled scary transclusions:\\n$wgEnableAPI = true;\\n$wgEnableWriteAPI = true;\\n$wgEnableScaryTranscluding = true;\\n$wgTranscludeCacheExpiry = 0;\\n\\nThen in a template I have this:\\n{{raw:lo::{{{1}}}}}\\n\\nI see this in the log:\\n[info][localhost:Test] starting parsing\\n[warning/api][localhost:Test][oldid:306] Failed API request, 8 retries remaining.\\n... and so on.\\n\\nIf just {{raw:lo::someItem}} is on the page parsoid evaluates this OK. But when this is in a template the requests fail for some reason.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-6fjfcuicwjgrpuv3znmv', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399660124, 'spacePHID': None, 'dateCreated': 1399359720, 'dateModified': 1399660124, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64942', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Adding citations inside hieroglyphics, gallery, or mathematics blocks results in the inspector never closing', 'description': {'raw': 'Intention:\\nAdd a citation inside (not after) a hieroglyphics block.\\n\\nSteps to Reproduce:\\n1. Open page containing hieroglyphics.  Open hierglyphics tool.\\n\\n2. Open Citation tool (or Insert > Reference).  Add citation.  \\n\\n3. Close citation tool (\"Apply changes\").\\n\\n\\n\\nActual Results:  \\nThe refernce is correctly added, but the hieroglyphics inspector stays open and empty until you save the page.\\n\\n\\nReproducible: Always\\n\\nBonus bug:\\n\\nBefore saving page, try editing a nearby link, gallery, or math formula.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399333995, 'spacePHID': None, 'dateCreated': 1399321380, 'dateModified': 1417570828, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64915', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'MathJax menus (in Math extension) are not localized into Vietnamese', 'description': {'raw': \"When MediaWiki's interface language is set to Vietnamese and MathJax rendering is turned on, the MathJax menus appear in English even though a Vietnamese localization is available. This issue does not occur when uselang=es etc.\\n\\nSteps to reproduce:\\n\\n1. Go to [[mw:Special:Preferences#mw-prefsection-rendering]] and turn on MathJax.\\n2. Change the interface language to Vietnamese.\\n3. Go to [[mw:User:Mxn/MathJax vi]] and right-click on the matrix.\\n\\nExpected results:\\n\\nThe menus should all be translated, as they are at <https://github.com/mathjax/MathJax-i18n/tree/master/JSON/vi>.\\n\\nActual results:\\n\\nAll the menus are in English.\\n\\nNote that MathJax-i18n was missing entries in config.js for a number of languages, including Vietnamese, until very recently: <https://github.com/mathjax/MathJax-i18n/pull/1>.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/User:Mxn/64809\"}, 'authorPHID': 'PHID-USER-sxpswmchfwxkuo2wszeo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413756495, 'spacePHID': None, 'dateCreated': 1399157340, 'dateModified': 1413756495, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64809', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Math inspector is not working in Betalabs', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert  a math function with math inspector\\n\\nObserved Result:\\nNothing gets added\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399079949, 'spacePHID': None, 'dateCreated': 1399055580, 'dateModified': 1417570829, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64763', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"VisualEditor language tool\" beta feature links on test2 are broken', 'description': {'raw': 'https://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures\\n\\nUnder \"VisualEditor language tool\", if I click discussion or information I get sent to https://test2.wikipedia.org/wiki/&lt;visualeditor-preference-experimental-info-link&gt; or https://test2.wikipedia.org/wiki/&lt;visualeditor-preference-experimental-discussion-link&gt;\\n\\nLocalisation cache issue?\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**URL**: https://test2.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401709351, 'spacePHID': None, 'dateCreated': 1398992040, 'dateModified': 1401709351, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64729', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  You shouldn't be able to set bold or other text attributes for ref tags\", 'description': {'raw': \"Steps to Reproduce:\\n1.  Select a ref tag.\\n\\n2.  Click on bold in the character formatting menu.\\n\\n\\n\\nActual Results:  \\nIt dutifully adds the character formatting:  <ref>Foo</ref> becomes '''<ref>Foo</ref>'''\\n\\nhttp://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=91700&oldid=91692\\n\\n\\nReproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399080407, 'spacePHID': None, 'dateCreated': 1398979980, 'dateModified': 1399237665, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64718', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Mobile VE is redirecting to Google while trying to save a page', 'description': {'raw': 'For Chrome\\n\\nSteps to reproduce:\\n\\n1.Open this link:https://test2.m.wikipedia.org/wiki/0.8863089695452125?title=0.8863089695452125&campaign=random#editor/0\\n\\n2.Make some edit\\n\\n3.Save the page\\n\\nObserved Result:\\n\\nIn Chrome: The page suddenly disappears and redirects me to Google Search Page \\nIn FireFox: It keeps the VE edit mode open \\n\\nSee the screenshots attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13949}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398908742, 'spacePHID': None, 'dateCreated': 1398901080, 'dateModified': 1424344537, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64686', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Don't try to load VisualEditor in namespaces where it isn't supported\", 'description': {'raw': 'Right now, if you switch to alpha mode and click the edit button on a page like...\\nhttps://en.m.wikipedia.org/wiki/User_talk:Kaldari\\n...you get an error since VisualEditor is disabled for that namespace on en.wiki.\\n\\nTo fix this, we need to surface the config settings in wmgVisualEditorNamespaces on the client-side and use it in the editor loading process in editor.js.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400023539, 'spacePHID': None, 'dateCreated': 1398892320, 'dateModified': 1400023539, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64681', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting Media fails when caret is not positioned after initialization', 'description': {'raw': 'Original bug title:\\nVisualEditor: Inserting Media fails when caret is not positioned after initialization\\n\\nAnd this is how to reproduce the issue:\\n* Go to https://www.mediawiki.org/wiki/Sandbox?veaction=edit\\n* Confirm the \"This is our new tool ....\"\\n* Reload the page\\n* Press \"Insert\"\\n* Press \"Media\" (dialog opens)\\n* Click one of the images.\\n\\nResult:\\nMozilla Firefox:\\n* POST https://www.mediawiki.org/w/api.php [HTTP/1.1 200 OK 281ms]\\n** http://pastebin.de/124264\\n* TypeError: splice is undefined load.php:153\\n** http://pastebin.de/124263\\n* Nothing happens except that the dialog is closed.\\n* Pressing \"Insert\" -> \"Media\" now does not open any dialog\\n\\nOpera Next:\\n* Uncaught TypeError: Cannot read property \\'apply\\' of undefined VM140:146\\n* Nothing happens except that the dialog is closed.\\n* Pressing \"Insert\" -> \"Media\" now does not open any dialog\\n* Stacktrace: http://pastebin.de/124262\\n\\n--------------\\nExpected:\\n* Image inserted\\n* Being able to add further images to the page\\n\\n--------------\\nUnrelated question:\\n* Why are you using FormData for this specific request?\\n\\n\\n\\n--------------\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64759'}, 'authorPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399065928, 'spacePHID': None, 'dateCreated': 1398776460, 'dateModified': 1417570830, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64601', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Have redirected links in green at the edit mode', 'description': {'raw': \"In VisualEditor When we are at the edit mode it doesn't show redirected internal links in green.\\n\\nIt can be as an option in top tool box or in setting part\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dswbdv7ibhsefllcqarz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401417534, 'spacePHID': None, 'dateCreated': 1398748440, 'dateModified': 1401417534, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64584', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Math formula does not display correctly if preferences are set to both TeX and MathJax', 'description': {'raw': 'Steps to Reproduce:\\n1. Enable VisualEditor formulae editing at Special:Preferences#mw-prefsection-betafeatures.\\n\\n2. Change math-related preferences to:\\n   * Leave it as TeX (for text browsers) (radio button; it\\'s off by default)\\n   * MathJax (experimental; best for most browsers) (tick box; it\\'s off by default)\\n\\n3. Open a page like [[:w:Torque]] in VisualEditor.\\n\\n4. Select a math formula from the page.\\n\\n5. Open the math editing tool.\\n\\n6. Change some thing in the formula (e.g., replace \"alpha\" with \"beta\").\\n\\n7. Look at the mess in the new version of the math formula (the one on the page, not the TeX code in the editing tool).\\n\\n\\n\\nReproducible: Always\\n\\nSee screenshots here:\\n\\nhttps://en.wikipedia.org/wiki/File:Bug_with_using_VE_and_mathjax.png\\n\\nhttps://commons.wikimedia.org/wiki/File:MathJax_mess_2014-04-28_at_2.33.08_PM.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402295506, 'spacePHID': None, 'dateCreated': 1398721500, 'dateModified': 1417570779, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64572', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing Return at the end of the document throws  Error: Offset could not be translated to a DOM element and offset: 675', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Go to the last line of this page:http://en.wikipedia.beta.wmflabs.org/wiki/28thAprilChrome?veaction=edit\\n\\n2.Press return\\n\\nObserved Result:\\n\\nAn error appears in the console:\\nUncaught Error: Offset could not be translated to a DOM element and offset: 675 \\n\\nSee the screenshot attached\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13655}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1425602094, 'spacePHID': None, 'dateCreated': 1398716100, 'dateModified': 1438734939, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64567', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: PHP Notice on undefined index', 'description': {'raw': \"Patch for php notice\\n\\nPHP Notice:  Undefined index: visualeditor-enable-language in extensions/VisualEditor/VisualEditor.hooks.php on line 402\\n\\nAttaching patch since I can't submit to gerrit from here.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13607}\"}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399082873, 'spacePHID': None, 'dateCreated': 1398698640, 'dateModified': 1443276200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64552', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Cutting and pasting an {{essay}} template (containing shortcuts) resulted in a different template displaying', 'description': {'raw': 'Intention:\\nMove a tag from the middle of a page to the top.\\n\\nSteps to Reproduce:\\nSee https://en.wikipedia.org/w/index.php?title=User:WhatamIdoing/Sandbox_3&diff=606088818&oldid=606088072 for the (entirely correct) diff.\\n\\n1. Select the essay tag in the middle of the page.\\n\\n2. Command-X to cut it.\\n\\n3. Scroll to the top.  Place cursor in the slug at the top.  Command-V to paste it.\\n\\n\\nActual Results:  \\nThe template that was displayed (upon pasting) does not look like the template that was cut.  It showed a \"clean up\" broom.\\n\\nThe changes to the wikitext (upon saving) were correct, and the template displayed correctly upon refresh (after saving).\\n\\n\\nReproducible: Didn\\'t try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437791195, 'spacePHID': None, 'dateCreated': 1398633600, 'dateModified': 1438734938, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64514', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor won't start - With correct config\", 'description': {'raw': '**Author:** `petter.viippola`\\n\\n**Description:**\\nI\\'ve done these steps and VisualEditor still dosen\\'t work. There seems to be a problem with loading VisualEditor. I can only edit source, the command edit isn\\'t possible to use. I\\'ve removed all the Parsoid options.\\n\\ncd extensions\\ngit clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git  \\ncd VisualEditor\\ngit submodule update --init\\n\\nrequire_once(\"$IP/extensions/VisualEditor/VisualEditor.php\");\\n\\n$wgDefaultUserOptions[\\'visualeditor-enable\\'] = 1;\\n \\n\\n$wgHiddenPrefs[] = \\'visualeditor-enable\\';\\n\\nEverything else seems to be working the wiki, with got it ad-connected. Can there be any issues regarding to that?\\n\\nBest regards\\nPetter\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416183497, 'spacePHID': None, 'dateCreated': 1398424980, 'dateModified': 1416183497, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64428', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Uncaught TypeError: Cannot read property 'nodeType' of undefined appears while trying to add a newline after clicking on Edit Beta for Page Title heading\", 'description': {'raw': \"screenshot\\n\\nSteps to Reproduce:\\n\\n1.Go to this page: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_%28WMF%29/sandbox&veaction=edit\\n\\n2.Click on Edit beta for the Page Title\\n\\n3.Now press return after any line to add a new line in the page\\n\\nObserved Result:\\n\\nAn error appears in the console:\\nUncaught TypeError: Cannot read property 'nodeType' of undefined \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&oldid=605655480\\n\\n**Attached**: {F13859}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399083059, 'spacePHID': None, 'dateCreated': 1398372300, 'dateModified': 1417570828, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64392', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  \"Unknown error\" corrupts page upon saving, but saving again fixes the problems it created', 'description': {'raw': 'Actual Results:  \\nTeamGale added some citations and then saved the page.  She received an \"unknown error\" and assumed that the page did not get saved.  So she saved the page again.  Upon checking the history, she found that both attempts to save the page had resulted in a new version:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Sakis_Rouvas&diff=605148987&oldid=605133988\\n\\nhttps://en.wikipedia.org/w/index.php?title=Sakis_Rouvas&diff=605149076&oldid=605148987\\n\\nHowever, the first diff removed the end of the page, including the reference secyion, external links, navboxes, succession boxes, categories, and more.  These were automagically restored when she saved the second time.\\n\\n\\nReproducible: Didn\\'t try\\n\\nTeamGale usually edits with Firefox 28 on Windows 8.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1459666953, 'spacePHID': None, 'dateCreated': 1398359400, 'dateModified': 1459684584, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64375', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor-doc-publish jobs are failing', 'description': {'raw': 'See for example https://integration.wikimedia.org/ci/job/mwext-VisualEditor-doc-publish/2336/console from https://gerrit.wikimedia.org/r/#/c/129372/\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398342116, 'spacePHID': None, 'dateCreated': 1398327960, 'dateModified': 1398342116, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64352', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The default size is not getting applied on an image after clicking on \"Apply Changes\"', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Go to this page:https://test2.wikipedia.org/w/index.php?title=22ndaprilFF&veaction=edit\\n\\n2.Select the image:\"K\" which is now in 220x200 px size\\n\\n3.Now go to Advanced Settings and select the tab \"Default\" and click on \"Apply changes\"\\n\\nObserved Result:\\nIt turns the image into full size 600x600 px\\n\\nAlso,\\nIf you first make the image as full size, then click on default size and click on \"Apply Changes\" nothing happens\\n\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401213398, 'spacePHID': None, 'dateCreated': 1398277140, 'dateModified': 1417570823, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64303', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: \"Success! Your edit was saved\" message stays in the VE mode unless user scrolls down the page', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Edit something\\n3.Save the page\\n4.Without scrolling the page, again reopen the VE for that page\\n\\nObserved Result:\\n\\n\"Success! Your edit was saved\" message stays in the VE mode .\\n\\nSee the screenshot too\\n\\nTest Environment: https://test2.m.wikipedia.org/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13581}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400253782, 'spacePHID': None, 'dateCreated': 1398213660, 'dateModified': 1400253782, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64270', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Not getting any result for VisualEditor media search in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Media\\n3.Type something on the search box to search for a media\\n\\n\\nObserved Result:\\nNo search results for images appears in the dialog\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13537}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398274843, 'spacePHID': None, 'dateCreated': 1398192600, 'dateModified': 1425574006, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64253', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't save after editing categories\", 'description': {'raw': \"It just happened to me on both Chrome and FF, Win 7, Vector. \\nIf I remove a category on it.wp, that's not considered as a change? The Save button stays grey. I need to type something and then delete it in order to be able to save my edit.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406320242, 'spacePHID': None, 'dateCreated': 1398173340, 'dateModified': 1406320242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64241', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE should have a toolbar icon for cut-copy-paste', 'description': {'raw': 'Right now, we have cut-copy-paste feature in VE but there is no icon for these Clipboard actions.\\nIt would be nice to have them on the toolbar as it is a pretty good feature with no visual indication that it exists.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398124464, 'spacePHID': None, 'dateCreated': 1398119700, 'dateModified': 1417570917, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64210', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Citation dialog does not focus correct field when adding parameter', 'description': {'raw': \"In the template dialog, when you add a parameter, that parameter's input field is then focused. This makes perfect sense. In the citation dialog, this doesn't happen, and instead the input field that was focused most recently is focused.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398112734, 'spacePHID': None, 'dateCreated': 1398112620, 'dateModified': 1417570918, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64201', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cite Options dialog has \"Show Options\" button enabled when it is inside Reference Dialog box but not when they are added in Main CE or inside Media Settings dialog', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Go to Cite> Website/Book/Newspaper/Journal \\n3.Observe that, Cite Options dialog does not have \"Show Options\" button\\n4.Now open a reference dialog box and Go to Cite>Cite> Website/Book/Newspaper/Journal\\n\\nObserved Result:\\nIn this case, there is a \"Show Options\" button for Cite options\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/21staprilchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14020}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398113113, 'spacePHID': None, 'dateCreated': 1398105780, 'dateModified': 1417570918, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64196', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor cut off last several characters of article text during two edits at pl.wp', 'description': {'raw': \"VisualEditor cut off last several characters of article text during two edits at pl.wp.\\n\\nhttps://pl.wikipedia.org/w/index.php?diff=39198236\\nhttps://pl.wikipedia.org/w/index.php?diff=39246345\\n\\nThese are two consecutive edits to the same article, [[pl:Lamborghini Aventador]].\\n\\nContent maiming → marking as 'major'.\\n\\nOriginally reported at https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Lamborghini_Aventador_-_ko.C5.84cowe_znaki by WTM.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437686729, 'spacePHID': None, 'dateCreated': 1398083820, 'dateModified': 1438734943, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64182', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'font-size in VisualEditor is smaller than view mode', 'description': {'raw': \"It seems typography refresh enlarged body font size but VE didn't follow this change.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397903906, 'spacePHID': None, 'dateCreated': 1397885100, 'dateModified': 1397903906, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64124', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Re-used references don't always match\", 'description': {'raw': 'Intention:\\nRemove a copyright violation\\n\\nSteps to Reproduce:\\nI removed the first instance of a ref tag.  See https://en.wikipedia.org/w/index.php?title=Male_rape&diff=604793477&oldid=604792987\\n\\n\\nActual Results:  \\nThe re-used ref was \"moved\", but that had the effect of changing it, because the next instance of the same named ref had a different description.\\n\\n\\nReproducible: Didn\\'t try\\n\\nI don\\'t know how to solve this.  The wikitext shouldn\\'t have been written that way in the first place.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402332059, 'spacePHID': None, 'dateCreated': 1397856060, 'dateModified': 1402341486, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64104', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Wrapping is not working properly for Reference numbers in reflist as it gets overlapped by a left aligned image', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a image\\n3.Add some content in the page\\n4.Add some references\\n5.Make the image left aligned\\n6.Add a reflist in a way so that the references in that list is to the right of the image\\n7.Save the page\\n\\nObserved result:\\n\\nReference numbers in reflist are getting overlapped by the image\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13726}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401323215, 'spacePHID': None, 'dateCreated': 1397770740, 'dateModified': 1417570823, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64073', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: crashing when trying to save a reference?', 'description': {'raw': 'An IP user at sv.wp reports this (GoogleTranslated):\\nIn Ubuntu 10.13 crashes Firefox when I want to save a source.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414624719, 'spacePHID': None, 'dateCreated': 1397642280, 'dateModified': 1414624719, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63992', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"'Insert Media' in VE fails to search local repo, returns blank.\", 'description': {'raw': '**Author:** `tech`\\n\\n**Description:**\\nRunning an up-to-date VisualEditor extension and parsoid server on mediawiki-1.22.2, when I use \\'Insert Media\\' no matter the search term (exact filenames are no better) nothing is returned.\\n\\nChecking server logs and debugging client browser data shows that VE only goes as far as a call to the API \\'api.php?format=json&action=query&meta=filerepoinfo\\' which returns:\\n\\n{\\n  query: {\\n    repos: [\\n      {\\n        name: \"local\",\\n        displayname: null,\\n        rootUrl: \"/images\",\\n        local: true\\n      }\\n    ]\\n  }\\n}\\n\\nThere are no further queries to the API after this call.\\n\\nI can add wikiCommons, with \"$wgUseInstantCommons = true\", which successfully searches the wikiCommons, but has no effect on local media.\\n\\nI can manually add media with the standard editor and the [[File:image.ext]] syntax, but if I double click a previously attached image in VE all of the fields in the media dialog box are vacant and I can\\'t change any values or even close the dialog.\\n\\nA query of \\'api.php?action=query&list=allimages&format=json\\' returns a complete set of media as expected.\\n\\nFurther, looking at the API documentation on the server the example listed for filerepoinfo is \\'api.php?action=query&meta=filerepoinfo&friprop=apiurl|name|displayname\\', but it returns in the warnings field: \"Unrecognized value for parameter \\'friprop\\': apiurl\". Suggesting that perhaps a variable in LocalSettings.php is missing or inaccurate, I\\'ve looked over this several times, but don\\'t see any glaring issues.\\n\\nThe server in question is behind an intranet, but I\\'m happy to answer any questions.\\n\\nThanks,\\nPatrick\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406656996, 'spacePHID': None, 'dateCreated': 1397627580, 'dateModified': 1417570764, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63989', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor on the French Wikinews users preferences', 'description': {'raw': \"After two weeks of vote we've just deliberated in favor of the Visual Editor activation for the logged users who want to tick it only: https://fr.wikinews.org/wiki/Wikinews:Prise_de_d%C3%A9cision/Installation_de_l%27%C3%A9diteur_visuel.\\n\\nThank you for your work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-dtdj4p6jtxbzs7trc3c6', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397518536, 'spacePHID': None, 'dateCreated': 1397257620, 'dateModified': 1397520953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63841', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing a reference adds a separate extra reference in test2', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a reference \\n3.Open the reference dialog box again\\n4.Add a cite web template inside it\\n5.Save the reference\\n\\nObserved Result:\\nA separate reference gets added just next to the existing reference\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397244708, 'spacePHID': None, 'dateCreated': 1397240520, 'dateModified': 1417570922, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63829', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template parameters should resize on initialisation (when needed)', 'description': {'raw': 'Intention:\\nAdd a new infobox using VE (from scratch)\\n\\nSteps to Reproduce:\\n1. Go to https://sv.wikipedia.org/wiki/Anv%C3%A4ndare:Andr%C3%A9_Costa_%28WMSE%29/VEtest2?veaction=edit\\n2. Enter edit-mode for the template\\n3. Go to the \"medlemskap\" parameter. Click value.\\n4. Go to the \"budget\" parameter. Click the value.\\n\\nActual Results:  \\n3. Nothing happens. You must use the down arrow to reveal hidden text.\\n4. Value window re-sizes and introduces a scrollbar revealing previously hidden text.\\n\\nExpected Results:  \\nBoth cases: Window should have been re-seized on initialisation or indicated that there is more information than shown.\\nFirst case: Window should have been re-seized or a scrollbar introduced.\\n\\nReproducible: Always\\n\\nThe main issue is that you might not ever expect that there is more information in the template value than is initially shown.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420860386, 'spacePHID': None, 'dateCreated': 1397215500, 'dateModified': 1420860386, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63814', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Newarticletext points to API not PAGENAME', 'description': {'raw': 'Intention:\\nCreate a new article using VE\\n\\nSteps to Reproduce:\\n1. Go to https://en.wikipedia.org/wiki/THISISNOTANARTICLE?veaction=edit\\n2. Wait for notices to load\\n\\n\\nActual Results:  \\nAll references to the pagename are changed to API (e.g. hover over search, or see the Special:Mypage/API link.\\n\\nExpected Results:  \\nthese links should point to the pagename (e.g. Special:Mypage/THISISNOTANARTICLE)\\n\\nReproducible: Always\\n\\nThis is occurs for any site using a pagename reference in MediaWiki:Newarticletext\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397866699, 'spacePHID': None, 'dateCreated': 1397210520, 'dateModified': 1441912298, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63811', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector inserts plain text while trying to insert a link selecting a math formula', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a link\\n3.Insert a math node right after the link\\n4.Select the math formula\\n5.Click on the link inspector\\n6.When the link suggestions drop down appears close the inspector\\n\\nObserved Result:\\nThe link inspector inserts plain text right before the math node\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/9thapril2014?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13666}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397757927, 'spacePHID': None, 'dateCreated': 1397154780, 'dateModified': 1417570919, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63783', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image repositioning is not working correctly when the image is inside a bock slug', 'description': {'raw': 'Centered wrt the slug\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert an image just after a block slug\\n3.Now change the image position to Centre/Left and Image type to Frame\\n\\nObserved Result:\\n\\nThe Image is not centered/ left aligned with respect to the page width rather with the width of the slug\\n\\nTry the first image on this page: https://test2.wikipedia.org/wiki/9thapril2014?veaction=edit\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13663}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1423749104, 'spacePHID': None, 'dateCreated': 1397153220, 'dateModified': 1423749104, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63781', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  In the template dialog, the removal icon (trash can) should be visible on all items', 'description': {'raw': \"When you open an existing template, it looks like only the first parameter can be removed.  To discover that it is possible to remove a template parameter, you must first click in that parameter's data box. \\n\\nInstead, the trash icon should be visible on all items always.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397678465, 'spacePHID': None, 'dateCreated': 1397143740, 'dateModified': 1397678465, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63775', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE does not appear when it should, get wikitext editor instead', 'description': {'raw': 'On any editable page on http://en.m.wikipedia.beta.wmflabs.org/ a logged-in user in alpha mode should invoke VisualEditor when clicking the edit icon. \\n\\nInstead the user gets the normal non-VE editor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397622427, 'spacePHID': None, 'dateCreated': 1397059440, 'dateModified': 1397622427, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63736', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When VisualEditor not available, wikitext editor still shows a edit switcher button in toolbar', 'description': {'raw': 'To replicate:\\nDisable VisualEditor and load the editor. Wikitext editor loads but according to toolbar VisualEditor is available.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397669248, 'spacePHID': None, 'dateCreated': 1396979040, 'dateModified': 1397669271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63689', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parse link in Newarticletext', 'description': {'raw': 'screenshot of VE, mozilla ff\\n\\nWhen going to\\nhttps://en.wikipedia.org/wiki/File:Henri_Rousseau_009.jpg?veaction=edit\\nVE has 1 notice telling me:\\n\\n\"Du bist einem Link zu einer Seite gefolgt, die nicht vorhanden ist. Um diese Seite anzulegen, trage deinen Text in das untenstehende Bearbeitungsfeld ein (weitere Informationen auf der [/wiki/Help:Contents Hilfeseite]).\"\\n\\nNote the \"[/wiki/Help:Contents Hilfeseite]\" part. I guess it should be a link.\\n\\n\\n\"Newarticletext\" seems to be the only message containing this text. And there was only one hit for \"Newarticletext\" in the VE repo:\\nhttps://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/797430e9efd4c773c149718ad086f51f8aa042f6/ApiVisualEditor.php#L339\\n\\nIndeed, the issue seems to be at the PHP side;\\nPOST /w/api.php\\naction\\tvisualeditor\\nformat\\tjson\\npaction\\tparse\\npage\\tFile:Henri_Rousseau_009.jpg\\n\\nreturns the message as \"<p>Du bist einem Link zu einer [...] der [/wiki/Help:Contents Hilfeseite] [...] deines Browsers. </p>\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14035}'}, 'authorPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402295035, 'spacePHID': None, 'dateCreated': 1396961580, 'dateModified': 1402295035, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63673', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Edit button throws errors when VisualEditor not installed', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397669243, 'spacePHID': None, 'dateCreated': 1396913520, 'dateModified': 1397669273, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63658', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot open VE in test 2 as it is throwing error: TypeError: undefined is not a function TypeError {stack: (...), message: \"undefined is not a function\"}', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\nTry to open any page with VE in test 2\\n\\nObserved Result:\\nThe following error appears and VE does not load\\nTypeError: undefined is not a function TypeError {stack: (...), message: \"undefined is not a function\"}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13971}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414088145, 'spacePHID': None, 'dateCreated': 1396895520, 'dateModified': 1417570684, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63645', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Images placed inside a <small> text block cannot be edited', 'description': {'raw': 'VisualEditor incorrect display of image inside <small> tags\\n\\nThis may depend on Bug 51614 \"Tool to set/unset text as small\".\\n\\nStart with a page like https://en.wikipedia.org/w/index.php?oldid=603182124#Referenced_text that contains this wikitext:\\n\\n<small>\\n[[File:Example.jpg|thumb|Caption]]\\n</small>\\n\\nWhen you open the page in VisualEditor, the image \"thumb\" has a box the entire width of the screen, the image is the correct size, but centered, and you can\\'t select (and therefore can\\'t edit) the image.\\n\\nThe caption\\'s text is small, which is probably expected.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13959}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396901647, 'spacePHID': None, 'dateCreated': 1396893540, 'dateModified': 1396901647, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63641', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit notices widget confusingly mentions API (in plain text and/or links) when creating a new page', 'description': {'raw': 'See\\nhttps://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove5?veaction=edit\\nhttps://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE8?veaction=edit\\nand https://en.wikipedia.org/wiki/User:Elitre_(WMF)/Sandbox3?veaction=edit .\\nThe widget behaves as if you are attempting to create the article \"API\".\\nOn en.wp it also provides a direct link to create Special:Mypage/API.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396887928, 'spacePHID': None, 'dateCreated': 1396884660, 'dateModified': 1417570922, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63631', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'incorrect \"Wikitext markup detected\" message', 'description': {'raw': '**Author:** `richlv`\\n\\n**Description:**\\nvisual editor from git f8d56e6804a12248b485c2d3b49d4ff0ffa7220c\\n\\ntestcase : https://www.zabbix.org/wiki/Bugsquash_Days\\n(if creating a new account, real name is mandatory)\\n\\nedit the page with visual editor. using the cursor keys, modify on of the event link texts :\\n\\n\"Wikitext markup detected\\nYou are using VisualEditor - wikitext does not work here. Click \"Edit source\" to edit the page in wikitext mode – unsaved changes will be lost.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397592475, 'spacePHID': None, 'dateCreated': 1396874580, 'dateModified': 1397592475, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63618', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Uncaught TypeError: Object #<Object> has no method 'lookup' appears upon loading any page on test2\", 'description': {'raw': \"Screenshot\\n\\nFor all pages on test2 I am getting the following error upon loading and Ve does not open for that page\\n\\nUncaught TypeError: Object #<Object> has no method 'lookup' \\n\\nTry this page:\\nhttps://test2.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13741}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401475943, 'spacePHID': None, 'dateCreated': 1396653660, 'dateModified': 1417570781, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63551', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] Media selector hangs without offering save', 'description': {'raw': 'As a logged in user on http://en.wikipedia.beta.wmflabs.org/ edit any page. \\n\\nChoose \"Insert Media\"\\n\\nSearch for something e.g. \"San Francisco\"\\n\\nSelect a media image. \\n\\nInsert Media interface does nothing, but should offer a Save and then Review your changes options.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396571513, 'spacePHID': None, 'dateCreated': 1396537500, 'dateModified': 1443276235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63484', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs', 'description': {'raw': 'seen on beta labs http://en.wikipedia.beta.wmflabs.org/\\n\\nAfter clicking Edit for VisualEditor, sometimes the user waits longer than expected for the editable div to appear.  \\n\\nThere is a default timeout of 5 seconds in the automated browser tests, and these tests are failing more and more often because the edit surface in VE takes longer than 5 seconds to appear, for a page of reasonable size.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396478369, 'spacePHID': None, 'dateCreated': 1396474500, 'dateModified': 1417048874, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63447', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Firefox displays icons in odd places in dialog boxes', 'description': {'raw': 'Firefox display bug\\n\\nThis is related to Bug 63432, about the mis-display of an icon in the media settings dialog box, and Bug 63127, about the reference box.\\n\\nIt also displays incorrectly in template boxes (see attachment), references (the icon at \"Options\" for \"Use this group\"—see bug 63127), and pretty much everything in the \"Page options\" (three bars icon) menu.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63127\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63432\\n\\n**Attached**: {F13423}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397687806, 'spacePHID': None, 'dateCreated': 1396460880, 'dateModified': 1417570920, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63433', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Media dialog box has misplaced icon in Firefox', 'description': {'raw': 'Firefox-only display bug\\n\\nIf you open the image dialog box and go to \"Advanced settings\" in Firefox, the \"window\" icon next to the headline \"Positions\" is misplaced, so that it covers up the checkbox for \"Wrap content with this item\".\\n\\nThis cannot be reproduced in Safari or Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63127\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63433\\n\\n**Attached**: {F13420}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397687801, 'spacePHID': None, 'dateCreated': 1396460400, 'dateModified': 1417570920, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63432', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid giving 503s for VE in mobilefrontend on beta labs', 'description': {'raw': 'To replicate:\\n1) Browse to http://en.m.wikipedia.beta.wmflabs.org/ in a browser window with at least one dimension > 700px\\n2) Opt-in to MobileFrontend\\'s experimental feature (main menu -> settings -> beta -> \\'on\\' -> save; main menu -> settings -> experimental -> \\'on\\' -> save)\\n3) Browse to random article\\n4) Tap/click pencil icon to edit\\n\\nCurrent behavior:\\n Receive error \"Error, can\\'t load section\"\\nExpected behavrio:\\n VisualEditor interface loaded to edit article\\n\\n\\nWhen looking through the network requests, you should see an API request for the VE action (something like http://en.m.wikipedia.beta.wmflabs.org/w/api.php?format=json&action=visualeditor&paction=parse&page=0.019064959779951818) with a server response of:\\n\\'{\"servedby\":\"deployment-apache02\",\"error\":{\"code\":\"parsoidserver-http-bad-status\",\"info\":\"503\"}}\\'\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-jh2oguhshocanixqvlfk', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396461709, 'spacePHID': None, 'dateCreated': 1396397280, 'dateModified': 1428077516, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63400', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The hand icon remains active after opening the Media Settings dialog and Reference dialog which selects some part inside the dialog upon double clicking', 'description': {'raw': 'video capture of the bug\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n\\n2.Insert an image or a reference somewhere at the centre of the page for better viewing the effect of it.\\n\\n3.Now click on the Reference Icon or the Media Settings icon\\n\\nObserved Result:\\n\\nYou will see the hand icon inside the dialog box and upon double clicking it selects some part of the dialog box.\\n\\nSee the Video Capture attached.\\n\\n\\n\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13360}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1425680487, 'spacePHID': None, 'dateCreated': 1396394400, 'dateModified': 1438734944, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63398', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid crashes on request (TypeError: undefined is not a function)', 'description': {'raw': '**Author:** `koem`\\n\\n**Description:**\\nSetup:\\n - Ubuntu 12.04\\n - apache2\\n - mediawiki 1.22.4\\n - parsoid master 2014-04-01 12:58 UTC\\n - nodejs 0.10.26-1chl1~precise1\\n - VisualEditor snapshot REL1_22\\n\\nThis is the error I get when I do curl http://localhost:8000/localhost/Wiki_Test_Page or when I try to edit the page http://wiki.testwiki.com/wiki/Wiki_Test_Page as a logged in user (Popup says \"Error loading data from server: parsoidserver-http-request-error: MWHttpRequest error. Would you like to retry?\").\\n\\n\\n  /usr/local/parsoid/api/ParsoidService.js:355\\n                                        callback();\\n                                        ^\\n  TypeError: undefined is not a function\\n    at errCB (/usr/local/parsoid/api/ParsoidService.js:355:6)\\n    at /usr/local/parsoid/api/ParsoidService.js:361:12\\n    at /usr/local/parsoid/lib/mediawiki.parser.environment.js:241:3\\n    at setupWikiConfig (/usr/local/parsoid/lib/mediawiki.parser.environment.js:295:3)\\n    at Object.processSome [as _onImmediate] (/usr/local/parsoid/lib/mediawiki.ApiRequest.js:119:17)\\n    at processImmediate [as _immediateCallback] (timers.js:330:15)\\n  worker 2394 died (8), restarting.\\n   - worker(2425) loading...\\n   - worker(2425) ready\\n\\nThe worker crashes and is restarted immediately. Always.\\n\\nThe Wiki is private. It worked until I imported some templates and deleted them again. But I can\\'t imagine that this is the reason.\\n\\n\\nLocalPreferences.php:\\n\\n  require_once(\"$IP/extensions/VisualEditor/VisualEditor.php\");\\n  $wgVisualEditorParsoidURL = \\'http://localhost:8000\\';\\n  $wgDefaultUserOptions[\\'visualeditor-enable\\'] = 1;\\n  $wgHiddenPrefs[] = \\'visualeditor-enable\\';\\n  $wgVisualEditorParsoidForwardCookies = true;\\n\\n\\napi/localpreferences.js:\\n\\n  exports.setup = function( parsoidConfig ) {\\n        parsoidConfig.setInterwiki( \\'localhost\\', \\'http://wiki.testwiki.com/mediawiki/api.php\\' );\\n        parsoidConfig.useSelser = true;\\n  };\\n\\nBest,\\nKarsten\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396517054, 'spacePHID': None, 'dateCreated': 1396354080, 'dateModified': 1400704166, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63365', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Please add extension:variables to allow defining variables local to the current page', 'description': {'raw': \"**Author:** `andr55`\\n\\n**Description:**\\nI would like the extension:variables installed.\\n\\nIt is available at https://www.mediawiki.org/wiki/Extension:Variables\\n\\nIt is rated as stable.\\nIt allows creating local variables valid only in the current page.\\n\\nThe current use case is to define a long string to be used in over 100 templates as part of links inside a larger template page.\\nThis extension will help alleviate constant ongoing problems in a frequently accessed and edited page.  (Over 400 edits in the last month.)\\n\\n1) By using a local variable, it removes the problem of typos, very common in the page where it will be used.  As well, it will minimize the problem of broken links, as many editors avoid typing the long string necessary to create valid links.\\n\\n2) It keeps this string local to the only page where it will be used, thus not polluting the template namespace, and avoiding potential name conflicts with other templates.\\n\\n3) The variable can be defined at the beginning, with a brief description to ensure that it's use is understood, so it becomes self-documenting where it is used.\\n\\n4) A shorter and more useful name can be chosen than for a template, as a template name would have to avoid ambiguity with other template pages.\\n\\n5) In the likely case that this string needs to be changed in the future, it can be done more easily, as it will be on the page where it is used.\\n\\n6) Although this is for use as part of a link, it could equally be used for other cases, as presented in examples on the extension page.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1450880337, 'spacePHID': None, 'dateCreated': 1396294740, 'dateModified': 1602870005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63324', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Ever-growing list of edit summary menus if using the gadget', 'description': {'raw': 'Steps to Reproduce:\\n1.  Enable the edit-summary gadget at the English Wikipedia as described in Bug 63314.\\n\\n2.  Make a small change to any page.  Click \"Save\".  Notice the two drop-down menus underneath the edit summary textarea.\\n\\n3.  Oops, you need to make another change before you save.  Close the save dialog (e.g., press the Escape key).\\n\\n4.  No, that change is not important (or make another change; it doesn\\'t matter).  Go back to \\'Save\\'.\\n\\n5.  Count the number of dropdown menus present.\\n\\n\\n\\nReproducible: Always\\n\\nRepeating this process several times resulted in at least four pairs of dropdown menus in Firefox before I gave up.  \\n\\nIn Safari, I got two pairs, and then (consistently) on the third time, VisualEditor seemed to crash (whole page grays out [or \"whites out\", really], nothing happens until I hit Escape).  But after pressing Escape, everything\\'s fine, and the process can be repeated several more times, resulting in half a dozen pairs of drop downs.  (The white/apparent crash comes back after a few more rounds, but just press Escape again and keep going.)  \\n\\nSaving the page was ultimately successful.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396290695, 'spacePHID': None, 'dateCreated': 1396290300, 'dateModified': 1483835203, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63316', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Edit summary gadget looks like it's working, but edits are saved without edit summaries\", 'description': {'raw': 'Intention:\\nAdd a pre-set edit summary to an edit using a gadget.\\n\\nSteps to Reproduce:\\n1.  Turn on the gadget at en.wp:   Preferences > Gadgets > Editing > \"Add two new dropdown boxes below the edit summary box with some useful default summaries\"\\n\\n2. Edit any article with VisualEditor.\\n\\n3.  Save page.  Don\\'t click or type anything into the edit summary box.  Just click\\xa0on an item something from one of the dropdown menus added by the gadget, and then click on \\'Save\\'.\\n\\n4.  Look for the edit summary in the page history.\\n\\nActual Results:  \\nThe edit summary displays in the textarea of the save dialog, but it is not saved with the edit.\\n\\nIf you click in the textarea after (but not before) choosing an edit summary from the dropdown menu, then the edit is saved correctly.\\n\\n\\nReproducible: Always\\n\\nConfirmed in Chrome, Safari, and Firefox on Mac and Ubuntu.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396290681, 'spacePHID': None, 'dateCreated': 1396289760, 'dateModified': 1424041637, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63314', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When a template is in a section title, VE consider what is on the same line after as if it was into the template', 'description': {'raw': 'Impossible to delete this addition: https//fr.wiktionary.org/w/index.php?title=pr%C3%A9dominer&diff=prev&oldid=18065635\\n\\nbecause VE consider it as a template part: https://commons.wikimedia.org/wiki/File:VisualEditor_bug_on_fr.wikt.PNG\\n\\nTested on two PCs, including one with Firefox 28.0.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://fr.wiktionary.org/w/index.php?title=pr%C3%A9dominer&diff=prev&oldid=18065635'}, 'authorPHID': 'PHID-USER-dtdj4p6jtxbzs7trc3c6', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414624808, 'spacePHID': None, 'dateCreated': 1396225140, 'dateModified': 1414624808, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63289', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Template's CSS code shows on page when editing\", 'description': {'raw': \"picture of the bug\\n\\nTemplate's html code shows on page when editing. I don't know should we change something with our templates on fi-wiki, or is it possible to fix in VisualEditor.\\n\\nHow to reproduce:\\n1) go to https://fi.wikipedia.org/wiki/Australian_Grand_Prix_2014?veaction=edit\\n2) see the 2 templates on the bottom of the page\\n\\nIf you need more information, feel free to ask.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13012}\"}, 'authorPHID': 'PHID-USER-6majuboi566q3ozbh27r', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396191796, 'spacePHID': None, 'dateCreated': 1396097400, 'dateModified': 1396191796, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63259', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Clicking edit in VE tablet doesn't respond instantly\", 'description': {'raw': \"When you click the edit button the address bar changes but the editor doesn't overlay. Many a time I find myself clicking it several times.\\n\\nThe problem stems from VisualEditor code being loaded via mw.loader.using but no LoadingOverlay being shown.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396652764, 'spacePHID': None, 'dateCreated': 1395967680, 'dateModified': 1396652764, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63212', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When using browser zoom, image overlays (resize, edit) become too small and inaccesible', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400695607, 'spacePHID': None, 'dateCreated': 1395894960, 'dateModified': 1424894575, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Scrolling a long template parameter, then clicking causes the cursor to jump to the top of the long parameter field', 'description': {'raw': 'Navigate here: https://www.mediawiki.org/wiki/VisualEditor:Test12\\n\\nOpen the VisualEditor\\n\\nOpen the template editor for the page\\'s content — should be Template:Longformcontent\\n\\nScroll to the fourth parameter text entry field.\\n\\nScroll within the fourth parameter\\'s text entry field to \"Maecenas non condimentum risus.\"\\n\\nClick \"Maecenas non condimentum risus.\"\\n\\nDefect: the cursor is placed at the top of the text entry field, by \"Lorem ipsum dolor\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Mac OS X 10.9'}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403637258, 'spacePHID': None, 'dateCreated': 1395862260, 'dateModified': 1417570775, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63135', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Math inspector label is showing up as null in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13208}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395775955, 'spacePHID': None, 'dateCreated': 1395772260, 'dateModified': 1417570924, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63083', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'use new param in VE tests to get around beta warning', 'description': {'raw': 'see https://gerrit.wikimedia.org/r/#/c/119217/\\n\\nupdate VisualEditor appropriately\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395939039, 'spacePHID': None, 'dateCreated': 1395703860, 'dateModified': 1395939039, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63047', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: save button remains greyed out in IE9 even after modifying the document', 'description': {'raw': \"There is something that should be triggered to change the appearance of the save button in IE that isn't being triggered.  I need to find it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395784399, 'spacePHID': None, 'dateCreated': 1395702780, 'dateModified': 1395784399, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63043', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Various things wiggle on hover in Chrome', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image/reference\\n3.Inside the reference or media dialog box insert a link/special character inserter\\n4.Now hover over any button on the link inspector like close or delete button\\n\\nObserved Result:\\nThe dialog box is getting misplaced like flickering\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395876216, 'spacePHID': None, 'dateCreated': 1395687420, 'dateModified': 1513150356, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63020', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When tabbing inside the template inspector, don\\'t skip the \"Add Parameter\" option', 'description': {'raw': 'When reaching the bottom of a list of parameters for a given template, cursor in the box of the last parameter, if you hit Tab you\\'ll be taken directly to the \"Apply changes\" button, while some users would expect \"Add Parameter\" to be reachable then.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402553868, 'spacePHID': None, 'dateCreated': 1395675720, 'dateModified': 1417570777, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63014', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector icon remains enabled in the toolbar even after closing the link inspector', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Now open a link inspector\\n3.Do not insert any link, just close the link inspector by pressing \"<\" or the trash icon\\n\\nObserved Result:\\n\\nThe link inspector icon is still active on the toolbar\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12885}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398726819, 'spacePHID': None, 'dateCreated': 1395440220, 'dateModified': 1441911418, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62941', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'unexpected \"session no longer valid\" in automated test', 'description': {'raw': 'unexpected session no longer valid message\\n\\nSeen in some automated tests, for example https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/410/testReport/(root)/VisualEditor/Edit_with_strings__outline_example_____Editing_with_%C3%A1%C3%A9%C3%AD%C3%B3%C3%BA___Editing_with_%C3%A1%C3%A9%C3%AD%C3%B3%C3%BA___/\\n\\nin the span of less than 90 seconds, this test does these steps: \\n\\n* start a browser (Firefox)\\n* login to beta labs and navigate to an editable page\\n* dismisses the beta warning\\n* edits the page with a smallish string\\n* click Save page\\n* click This is a minor edit\\n* click Review your changes\\n* click Return to save form\\n* edit the description of the change\\n* click Save page the second time\\n\\nAt the last step, the result shows an error message \"Warning: we could not process your edit because the session was no longer valid...\" \\n\\nSee screen shot.  \\n\\nNote in the screen shot that the user is still logged in properly at the time they receive the error message.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12866}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417482592, 'spacePHID': None, 'dateCreated': 1395418080, 'dateModified': 1438734947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62931', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Load charset into special characters option', 'description': {'raw': 'I think its great that developers add special characters option. While I would see here an improvment to load on every different wikipedia its charset, which was after the years of its ussage developed. Its not an \"extra\" of folks, its the fact that every language has some specifics (Spanish ¿, Czech „“) which are not native to keyboards. But yet when we want to have a clear and quality ecyclopedia we use them.'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1438804265, 'spacePHID': None, 'dateCreated': 1395392760, 'dateModified': 1448096716, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62919', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Ctrl-clicking on redlinks (only) in a subpage takes you to the wrong page title', 'description': {'raw': 'Intention:\\nFind out why [[Page]] was a redlink by opening the link in another window.\\n\\nSteps to Reproduce:\\n1. Open a sandbox in a subpage, e.g. [[User:Example/Sandbox]]\\n\\n2. Add a redlink to a non-existent [[Page]].\\n\\n3. Ctrl-click on the redlink to open the non-existent page in another tab.\\n\\n4. See that the page actually opened in [[User:Example/Page]] instead of at [[Page]].\\n\\n\\n\\nReproducible: Always\\n\\nThis was fixed in Bug 59196 but has re-appeared for redlinks only.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395344091, 'spacePHID': None, 'dateCreated': 1395336660, 'dateModified': 1395344091, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62877', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Redirects not found when you try to make a link (wmf18)', 'description': {'raw': 'Intention:\\nAdd a link to a redirect page.\\n\\nSteps to Reproduce:\\n1. Go to Mediawiki.org.  Open a page in VisualEditor and type some text.\\n\\n2. Select a word and try to link it to [[Help:Help]], an existing redirect page.\\n\\n\\n\\nActual Results:  \\nIt claims that the existing page is a \"New Page\"/redlink.\\n\\n\\nReproducible: Always\\n\\nThis only happens at Mediawiki.org  The problem cannot be reproduced at either beta labs or at the Wikipedias, so it must be something in wmf18.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395185089, 'spacePHID': None, 'dateCreated': 1395184080, 'dateModified': 1395185089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62804', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Text-oriented templates don't wrap normally\", 'description': {'raw': 'What the page ought to look like\\n\\nIf you have an inline template (like {{highlight}} at en.wp) with a lot of text in it, the text needs to wrap instead of behaving like a block.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13155}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395169574, 'spacePHID': None, 'dateCreated': 1395169320, 'dateModified': 1395169574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62800', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Selection problems involving sfn template in Safari', 'description': {'raw': 'Steps to Reproduce:\\n1. Using Safari, open https://en.wikipedia.org/w/index.php?oldid=600087421 and scroll to the ==Referenced text== (first) section.\\n\\n2. Select a sentence in the first paragraph, including at least one <ref> tag.\\n\\n3. Control-click on your choice of \"refs\" in the next paragraph.  (These are all {{sfn}} templates.)\\n\\n4.  Pretty, isn\\'t it?\\n\\nActual Results:  \\nText all over the page was selected, but not box-type templates.\\n\\n\\nReproducible: Sometimes\\n\\nUnable to reproduce in Firefox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417578429, 'spacePHID': None, 'dateCreated': 1395103080, 'dateModified': 1438734947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62765', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Display the version of VisualEditor in help popup', 'description': {'raw': 'Would be nice to see this there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-b27lopawgf2h6utuuqyi', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395351525, 'spacePHID': None, 'dateCreated': 1395097560, 'dateModified': 1395351525, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62760', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  What you see is not the Babel box that you get', 'description': {'raw': 'Intention:\\nAdd a Babel box\\n\\nSteps to Reproduce:\\n1. Add {{#babel:en|de-1|es-1|vo-0}} using the workaround described in bug 62750.\\n\\n2. Look at the results.\\n\\n3. Save the page.  Look at the very different results.\\n\\nActual Results:  \\nSee the screenshot.  The first shows the left-aligned box before save; the second shows the right-aligned, colorful box after the save.\\n\\nExpected Results:  \\nWhat you saw in VisualEditor would have some signficant relationship to what you saw when the page was saved.\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1425682430, 'spacePHID': None, 'dateCreated': 1395083220, 'dateModified': 1438734947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62745', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When cutting and pasting list items, it is hard to achieve the intended formatting', 'description': {'raw': 'If I cut items from a bulleted list and try to past them into another bulleted list, the formatting gets confusing:\\n\\n*Extra empty bullets get left behind when I cut.\\n*The relationship between an existing list and new items I paste to the end of it can be wonky. Extra line breaks appear, and sub-bullets lost their relationship to each other, so that pressing tab to increase the level of indentation sometimes creates two bullets in a row instead of just increasing the level of indentation.\\n\\nSee this screen recording for more details of my experience: https://commons.wikimedia.org/wiki/File:Screen_recording_of_trying_to_move_bulleted_list_items_in_VisualEditor.ogv\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nyv6rqxnzdy3oe323a3d', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1429223062, 'spacePHID': None, 'dateCreated': 1395080580, 'dateModified': 1438734952, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62742', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit links are not appearing for the headings in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Add some headings\\n3.Save the page\\n\\nObserved Result:\\n\\nEdit links are not appearing for the headings\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13017}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395081382, 'spacePHID': None, 'dateCreated': 1395080160, 'dateModified': 1417570927, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62741', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Description of tags \"VisualEditor: Check\" and \"VisualEditor: Switched\" are hard to translate', 'description': {'raw': 'In its current form I\\'m always wondering \"check what?\" and \"switched what?\"\\n\\nCan\\'t them be replaced by sentences like \"Switched from VisualEditor\" and \"Check VisualEditor errors\" or something better?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400014248, 'spacePHID': None, 'dateCreated': 1394887140, 'dateModified': 1417570826, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62694', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: On opening a page that contains only a template, template is selected but you can't edit the template\", 'description': {'raw': \"Intention:\\nEdit https://www.mediawiki.org/wiki/User:Quiddity_(WMF)\\n\\n\\nSteps to Reproduce:\\n1. Click on https://www.mediawiki.org/wiki/User:Quiddity_%28WMF%29?veaction=edit\\n\\n2. Template is selected.\\n\\n3. But there's no puzzle piece, and you can't edit it.\\n\\n\\nActual Results:  \\nYou can't edit the template unless you click outside the template (e.g., in the title or on a blank spot in the sidebar) first.\\n\\n\\nReproducible: Always\\n\\nSee bug 62542, for inability to use cursor keys to deselect the template.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394818952, 'spacePHID': None, 'dateCreated': 1394818380, 'dateModified': 1394818952, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62650', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Visualization issues with Firefox Aurora 29.0a2', 'description': {'raw': 'See icons overlapping other elements at\\nhttps://commons.wikimedia.org/wiki/File:Bug_EV_insertion_mod%C3%A8les_ic%C3%B4ne_d%C3%A9plac%C3%A9e.png\\nhttps://commons.wikimedia.org/wiki/File:Bug_EV_-_insertion_mod%C3%A8les_ic%C3%B4ne_d%C3%A9plac%C3%A9e_02.png\\nhttps://commons.wikimedia.org/wiki/File:Bug_EV_-_insertion_mod%C3%A8les_ic%C3%B4ne_d%C3%A9plac%C3%A9e_03.png\\n\\nYou can also see this very easily through the Options menu on other sites.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420843450, 'spacePHID': None, 'dateCreated': 1394811240, 'dateModified': 1420843450, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62645', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'SemanticForms lies about content model (Title::getContentModel gives wikitext, yet it is json)', 'description': {'raw': 'Clicking \"Edit\" (VisualEditor) on https://wikitech.wikimedia.org/wiki/Shell_Request/Rxy shows an error from the server about content model json being incompatible.\\n\\nHowever VisualEditor shouldn\\'t initialise that far in the first place, we know the content model (conf.wgPageContentModel).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-7jqnferdzzzwelhzchyo', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405378673, 'spacePHID': None, 'dateCreated': 1394654460, 'dateModified': 1405388498, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62576', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'External link with embedded comment is not shown correctly', 'description': {'raw': 'The first external link in the \"Further reading\" section of https://en.wikipedia.org/w/index.php?title=State_Patty%27s_Day&oldid=597985640&veaction=edit is not shown the same in VisualEditor as the PHP parser.\\n\\nIn VE, the text shows as \"\\'s+Day%22&hl=en&sa=X&ei=7XQyUaeaD4LqiQL9zIHIBw&ved=0CDAQ6AEwAA#v=onepage&q=%22State%20Patty\\'s%20Day%22&f=false Early Adulthood in a Family Context - Alan Booth - Google Books\".\\n\\nIn a normal view (https://en.wikipedia.org/w/index.php?title=State_Patty%27s_Day&oldid=597985640), it shows as \"Early Adulthood in a Family Context - Alan Booth - Google Books\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398901917, 'spacePHID': None, 'dateCreated': 1394349000, 'dateModified': 1398901917, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62450', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Template converted to span tags at Javanese Wikipedia', 'description': {'raw': 'https://jv.wikipedia.org/wiki/Cithakan:Lahirmati (Template:Birth and death) is converted to span tags in this edit:  https://jv.wikipedia.org/w/index.php?title=Jojon&curid=74332&diff=881686&oldid=830430\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1533062237, 'spacePHID': None, 'dateCreated': 1394236920, 'dateModified': 1533062237, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62411', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Trying to add an image as a bullet list item removes the bullet but the Bullet list option remains selected in the menu', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a bullet list\\n3.Insert an image as an item to the bullet list.\\n\\nObserved Result:\\nThe bullet goes away but if you place the cursor in that position the bullet list icon remains active in the menu.\\n\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13399}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1438286130, 'spacePHID': None, 'dateCreated': 1394156280, 'dateModified': 1439425491, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62354', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing into empty paragraph with inspector open creates pawn', 'description': {'raw': '1. Open empty.html in SA demo\\n2. Open the language inspector or the special character inspector\\n3. Type, a pawn appears\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402834213, 'spacePHID': None, 'dateCreated': 1393957200, 'dateModified': 1417048873, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62220', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Follow-up to bug 48418: Treat {CREDITS|AUTHORS}.txt files as plaintext, not wikitext', 'description': {'raw': 'The fix for bug 48418 made the assumption that {CREDITS|AUTHORS}.* files were wikitext (with the implication that wikitext bullets should precede each file), contrary to expectations.\\n\\nInstead, we should treat their contents as the plain text they (mostly) were until this feature was added, and merely wrap them in <pre>s for Special:Version/Credits/… etc. purposes.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-uqcn2l4ng4murmyfnvyp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393873731, 'spacePHID': None, 'dateCreated': 1393866300, 'dateModified': 1602870006, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62153', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Upgrade Ruby to version 2.1.1', 'description': {'raw': 'List of repositories that need to be updated is here:\\n\\nhttps://github.com/wikimedia/mediawiki-selenium#links\\n\\nDo not forget mediawiki_selenium gem.\\n\\nTo update Ruby to version 2.1.1, locate Gemfile file, either in the root of the repository (mediawiki_selenium) or in tests/browser folder, or in /modules/ve-mw/test/browser folder (VisualEditor).\\n\\nThe first line in the Gemfile should be changed from:\\n\\n#ruby=ruby-2.1.0\\n\\nto\\n\\n#ruby=ruby-2.1.1\\n\\nThen, Jenkins jobs that run Selenium tests should be updated. The repository is located here:\\n\\nhttps://github.com/zeljkofilipin/jenkins-job-builder-config\\n\\nFind all files that contain this:\\n\\nRUBY_VERSION=2.1.0\\n\\nand replace it with:\\n\\nRUBY_VERSION=2.1.1\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-b5bosdf7b7zp3vqofbug', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407267501, 'spacePHID': None, 'dateCreated': 1393865280, 'dateModified': 1407267501, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62152', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Cannot go to a newline after undoing a heading format and Uncaught TypeError: Cannot call method 'getModel' of null appears in the console\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Create a heading\\n3.Undo creating the heading and type something in that line instead\\n4.Press enter\\n\\nObserved Result:\\n\\nUncaught TypeError: Cannot call method 'getModel' of null appears in the console and user cannot go to the next line anymore and has to cancel that session.\\n\\nSee the screenshot attached,\\n\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:\\nhttps://test2.wikipedia.org/w/index.php?title=27thfebchrome&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13193}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393530490, 'spacePHID': None, 'dateCreated': 1393529760, 'dateModified': 1417570950, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62015', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Uncaught TypeError: Cannot call method \\'getModel\\' of null \" appears while trying to add newline after a reflist', 'description': {'raw': \"Steps to reproduce:\\n\\n1.Open a page with VE which has a reflist at the end of the page\\n\\n2.Place your cursor at the end of the page and press enter to add a newline\\n\\nObserved Result:\\nNo newline gets added and an error appears in the console:\\n\\n\\nUncaught TypeError: Cannot call method 'getModel' of null load.php:268\\nve.ce.Surface.handleEnter load.php:268\\nve.ce.Surface.onDocumentKeyDown load.php:247\\nproxy load.php:10\\nve.EventSequencer.onEvent load.php:21\\n(anonymous function) load.php:20\\njQuery.event.dispatch load.php:45\\nelemData.handle.eventHandle load.php:38\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393474369, 'spacePHID': None, 'dateCreated': 1393368000, 'dateModified': 1417570934, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61932', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor in the \"Recherche:\" (104) namespace for frwikiversity', 'description': {'raw': 'Hello,\\nFrench Wikiversity need help to fixe the visual editor working on the \"recherche:\" space name.\\nThanks a lot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-mxwamhfxuzomk4umydpl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393289954, 'spacePHID': None, 'dateCreated': 1393274880, 'dateModified': 1393289954, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61874', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Cursor behavior inconsistent when setting redirects', 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Go to Page settings to set a redirect.  \\n\\n2.  Skip the tick box; just click in the field and type in your page name.\\n\\n3.  Apply changes.\\n\\n4.  Change your mind.  Go back to Page settings.  Untick the checkbox.\\n\\n5.  Apply changes.\\n\\n6.  Figure out the perfect target.  Go back to Page settings.  \\n\\n7.  Skip the tick box, just like you dud in Step 2; just click in the field.  Why won't it let me type there now?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393272393, 'spacePHID': None, 'dateCreated': 1393271520, 'dateModified': 1393272393, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61866', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parameter box is too small', 'description': {'raw': 'picture of the box\\n\\nParameter box is too small\\n\\nHow to reproduce:\\n1) go to https://en.wikipedia.org/wiki/Saint_Titus?veaction=edit\\n2) click the \"multiple issues\" template on the top of the page and click \"transclusion\"\\n\\nthere is in the \"issues\" box:\\n\\n{{refimprove|date=December 2010}}\\n{{lead too short|date=July 2013}}\\n\\nand I only can see a blank row and little bit of the first line of text. Boxes should be resizable/moveable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12824}'}, 'authorPHID': 'PHID-USER-6majuboi566q3ozbh27r', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393271161, 'spacePHID': None, 'dateCreated': 1393268700, 'dateModified': 1393271161, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61859', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Make references visible for re-use when they're 'hidden' inside templates, e.g., list-defined refs in the reflist template\", 'description': {'raw': 'This is related to Bug 57209.\\n\\nList-defined references (https://en.wikipedia.org/wiki/Wikipedia:LDR#WP:LDR) are listed in the {{reflist}} template rather than in the regular text of the page. References that are defined inside the {{reflist}} are not visible when you try to re-use an existing reference.\\n\\nSteps to reproduce:\\n\\n1. Open a page that uses list-defined references with the {{reflist}} template (rather than <references></ref>).\\n\\n2. Go to Insert > Reference to add a new reference.  Click \"Re-use existing reference\".\\n\\n3. Discover that the numbers (\"[1]\") and ref names are visible, but the contents are not.\\n\\nThis problem does not exist if the non-template method is used.  This problem also exists for refs inside blockquotes, infoboxes, and other templates.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393537301, 'spacePHID': None, 'dateCreated': 1393019340, 'dateModified': 1393537301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61777', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Gallery Highlight is not getting redrawn in correct position while changing the Heading style applied on it', 'description': {'raw': 'Screenshot-1\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a gallery\\n3.Select the gallery and apply the formated Preformatted and observe the blue highlight box\\n4.Deselect and again select the gallery\\n5.Change the format to Paragraph to Heading and observe the position of the blue highlighted box\\n\\nObserved Result:\\nThe highlight box does not get reposition according to the new position of the gallery.\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/21stfebff?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13200}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402921436, 'spacePHID': None, 'dateCreated': 1393012860, 'dateModified': 1417570775, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61766', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Opening Today's Featured Article produces a two copies in VisualEditor\", 'description': {'raw': 'Intention:\\nOpen https://en.wikipedia.org/wiki/Afroyim_v._Rusk (TFA) in VisualEditor.\\n\\nSteps to Reproduce:\\n1. Click to the Main Page.\\n2. Click to the article (https://en.wikipedia.org/wiki/Afroyim_v._Rusk)\\n3. Click on \"Edit beta\".\\n4. Wait a long time.\\n5. Discover two copies of the entire article.\\n\\nActual Results:  \\nTwo copies of the article appear, one above the other.  This happens in Safari 6 but not in Firefox 27; it happens only when editing the actual mainspace page, not when editing a copy in a sandbox.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392940376, 'spacePHID': None, 'dateCreated': 1392924060, 'dateModified': 1392940376, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61697', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"[Regression] VisualEditor: Page options menu doesn't open (Uncaught TypeError: undefined is not a function)\", 'description': {'raw': '* Latest master mediawiki-core and VisualEditor\\n* Edit Worksheet page\\n* Open \"Options\" dialog\\n\\nNothing happens, console shows:\\n\\n\\n\\n Uncaught TypeError: undefined is not a function\\n >         this.tableOfContents = new OO.ui.FieldLayout(new OO.ui.ButtonSelectWidget({\\'$\\': this.$}).addItems([new OO.ui.ButtonOptionWidget(\\'mwTOCForce\\', {\\'label\\': ve.msg(\\'visualeditor-dialog-meta-settings-toc-force\\')}), new OO.ui.ButtonOptionWidget(\\n VeUiMWSettingsPage\\n ve.ui.MWMetaDialog.initialize\\n oo.EventEmitter.emit\\n (anonymous function)\\n pollExternalStylesheets\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392865971, 'spacePHID': None, 'dateCreated': 1392864900, 'dateModified': 1392865971, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61576', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Redirects have ./ added to them in round-trip', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Go to Page Settings\\n3.Check the box Redirect this page to and specify the page/article to which it will redirect to.\\n4.Apply changes\\n5.Save the page\\n6.Reopen VE for this page\\n\\n\\nObserved Result:\\nThe page settings page pops up with ./ appended as prefix to the article name\\n\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/19thfebchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13414}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392862906, 'spacePHID': None, 'dateCreated': 1392855420, 'dateModified': 1443276281, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61570', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding content with newline in Edit source mode appears with return arrow in VE mode then placing the content in the preceding line', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Go to Edit Source mode\\n2.Add a text or anything else in a newline\\n3.Save the page\\n4.Open the page with VE\\n\\nObserved Result:\\nThe newly added text gets merged with the previous line adding a return character between the lines.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/19thfebchrome?veaction=edit\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13402}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393537023, 'spacePHID': None, 'dateCreated': 1392853920, 'dateModified': 1417570950, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61569', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Stop specifying the (default) size of media items in VisualEditor', 'description': {'raw': 'If you add \"File:Example.jpg\", without actively specifying a size, then you should get [[File:Example.jpg|thumb|Here is a caption]].  You should not get [[File:Example.jpg|thumb|220x220px|Here is a caption]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393447031, 'spacePHID': None, 'dateCreated': 1392851220, 'dateModified': 1424894578, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61565', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Word missing from wikilink', 'description': {'raw': 'During a test,\\nI tried to create a wikilink to\\nhttp://fr.wikipedia.org/wiki/Cabin_Fever:_Patient_Zero .\\nWhat I did was writing Cabin Fever: Patient Zero,\\nthen selecting all the 4 words, copy/pasting that precise URL and selecting the \"red\" option in the dropdown menu as if to link to a new page.\\nThe result is https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve2&diff=101406090&oldid=101406077 ,\\nthat shows up as [Fever: Patient Zero] in view mode, while the wikicode shows the word Cabin as an existing part of the label.\\nThis happened on both Chrome and FF, Win7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437687498, 'spacePHID': None, 'dateCreated': 1392833640, 'dateModified': 1438734956, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61550', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing tab does not take the cursor to the next field/parameter in a template dialog box', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page in VE\\n2.Go to Insert>Transclusion\\n3.Search for a template like Cite Web\\n4.Click on \"Add template\"\\n5.When all the parameters appear, insert a value in one of the parameters then press tab to go to the next parameter.\\n\\nObserved Result:\\nPressing tab does take user to the next tab\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/New_deep?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394076957, 'spacePHID': None, 'dateCreated': 1392774900, 'dateModified': 1443276281, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61529', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Return arrow is getting placed after every element inside Reference Dialog box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page in VE\\n2.Add a reference to the page\\n3.Open the reference dialog box\\n4.Add a text\\n5.Go to the next line and then a Cite web template \\n6.Go to the next line and add a math funtion\\n7.Save the page\\n8.Reopen the page and open the reference dialog box\\n\\nObserved Result:\\nAfter every element return arrow is getting placed.\\n\\nSee the screenshot attached\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/18thfebchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13281}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406754132, 'spacePHID': None, 'dateCreated': 1392755580, 'dateModified': 1417570763, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61510', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Math plugin displayed equation becomes jumbled during and after editing if using MathJax', 'description': {'raw': 'Split off from bug 43058.\\n\\nEditing the last equation at \\nhttps://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit\\n\\nif you actually make a change to the text of the equation the displayed equation becomes very jumbled. Any vertical positioning is lost, and text from different lines are overlaid on top of each other.\\n\\nThis happens with Chrome on a Mac.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52499'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-4sfm3grxdo6hnogm4iqe', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4sfm3grxdo6hnogm4iqe', 'dateClosed': 1437345483, 'spacePHID': None, 'dateCreated': 1392739320, 'dateModified': 1437346323, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61497', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Messages \"symbols\", \"accents\", \"math\" in special character inserter tool not translatable', 'description': {'raw': 'The special character inserter tool has hard-coded texts which are not translatable.\\n\\nThere is texts \"symbols\", \"accents\" and \"math\" which are not translatable, because there is no existing MediaWiki messages.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-6majuboi566q3ozbh27r', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392741532, 'spacePHID': None, 'dateCreated': 1392561840, 'dateModified': 1392741532, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61439', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE is unable to insert a internal reference with sub-section', 'description': {'raw': '**Author:** `paulomsimoes`\\n\\n**Description:**\\nVE is unable to insert a internal reference with sub-section. Example:\\n\\n[[\"Wikipédia Article name\"#\"Section name\"]], return only [[\"Wikipédia Article name\"]] (without redirect to section), as per [https://pt.wikipedia.org/w/index.php?title=Faculdade_Salesiana_de_Maca%C3%A9&diff=38176530&oldid=38176349|this edit].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401417280, 'spacePHID': None, 'dateCreated': 1392505740, 'dateModified': 1401417280, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61428', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Investigate VisualEditor browser test failures for \"headings\" test run via CloudBees', 'description': {'raw': '**Author:** `jhall`\\n\\n**Description:**\\nThe VisualEditor headings.feature has begun to fail[1] when run via CloudBees (but not when run locally).  Relevant Selenium log message is (example is for the \"Subheading1\" scenario, but the pattern is the same for all scenarios in this test):\\n\\n00:25:21.230 INFO - Executing: [find element: By.xpath: .//a[@title=\\'^3\\']] at URL: /session/83a0781b-247c-4f0a-88f8-a93cef166a15/element)\\n00:25:21.247 WARN - Exception thrown\\norg.openqa.selenium.NoSuchElementException: Unable to locate element: {\"method\":\"xpath\",\"selector\":\".//a[@title=\\'^3\\']\"}\\nCommand duration or timeout: 13 milliseconds\\nFor documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html\\nBuild info: version: \\'2.39.0\\', revision: \\'ff23eac\\', time: \\'2013-12-16 16:11:15\\'\\nSystem info: host: \\'chef\\', ip: \\'127.0.1.1\\', os.name: \\'Linux\\', os.arch: \\'i386\\', os.version: \\'3.2.0-56-virtual\\', java.version: \\'1.6.0_31\\'\\nSession ID: 185a49ff-3267-43a3-ad44-3e6881cd0d43\\nDriver info: org.openqa.selenium.firefox.FirefoxDriver\\nCapabilities [{platform=LINUX, acceptSslCerts=true, javascriptEnabled=true, browserName=firefox, rotatable=false, locationContextEnabled=true, version=26.0, cssSelectorsEnabled=true, databaseEnabled=true, handlesAlerts=true, browserConnectionEnabled=true, nativeEvents=false, webStorageEnabled=true, applicationCacheEnabled=true, takesScreenshot=true}]\\n\\nThe problem does not repro when the test is run on a MacBook, and the insertion of the following command into the headings_steps.rb file at appropriate points succeeds as expected:\\n\\n@browser.a(:xpath, \".//a[@title=\\'^3\\']\").should exist\\n\\nNeed to figure out why these test scenarios fail when run via CloudBees, since they seem to be perfectly legitimate test cases.\\n\\n[1] https://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/327/testReport/\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401746629, 'spacePHID': None, 'dateCreated': 1392418260, 'dateModified': 1401746629, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61398', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The search spinner continues indefinitely for some search strings in Image Search textbox', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce\\n\\n1.Open a page with VE\\n2.Go to Insert>Media\\n3.Insert the search string \"April\"\\n\\nObserved Result:\\n\\nAn error appears in the console:\\nUncaught TypeError: Cannot read property \\'0\\' of undefined \\n\\nand the search spinner continues indefinitely\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=14thfebchrome&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12972}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392862699, 'spacePHID': None, 'dateCreated': 1392407400, 'dateModified': 1443276283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61392', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page in test 2\\n\\n2.Select an image\\n\\n3.Go to the Media Settings >Advanced Settings for that image\\n\\nObserved Result:\\n All the button labels are missing for Media Type Section in Media Settings>Advanced Settings in test2\\n\\nSee the screenshot attached\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/13thfebchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12856}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392405621, 'spacePHID': None, 'dateCreated': 1392330060, 'dateModified': 1417570953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61343', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Blank edit notices for admins on each page at English Wikipedia', 'description': {'raw': 'As an admin on en.wp, I get a blank edit notice popup on every page I edit, with a red link to the page notice. I seem to recall that this is some interaction with local site JS/CSS, and that this was fixed at some point in the past.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=43013'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394490038, 'spacePHID': None, 'dateCreated': 1392322980, 'dateModified': 1394490038, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61335', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page Suggestions in link inspector are not appearing in FireFox on Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Create a link which has a target of existing page or a new page\\n\\nObserved Result:\\nThere is no drop down appearing with matched pages suggestion or a new page section.\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser:FF 25\\nOS: MAC OS X 10. 8. 5\\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_%28WMF%29&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13342}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402550077, 'spacePHID': None, 'dateCreated': 1392240360, 'dateModified': 1417570778, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61284', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"editing Wikipedia articles doesn't work in desktop Firefox with mobile interface\", 'description': {'raw': 'To reproduce:\\n\\n1. Go to https://en.m.wikipedia.org/wiki/ASCII in desktop Firefox.\\n2. Press the pencil button to edit.\\n\\nExpected: The mobile editing is supposed to open.\\nObserved:\\n1. The editing interface doesn\\'t open. The page stays the same.\\n2. The following errors are displayed in the JS console:\\n\\n\"Exception thrown by job.error\" (load.php:145)\\n\"Error: Container must be attached to the DOM\" [object Error] (load.php:145)\\n\\nThis works in desktop Google Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392401990, 'spacePHID': None, 'dateCreated': 1392153780, 'dateModified': 1392418256, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61233', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Media Settings dialog always goes back to General settings if you switch windows while in Advanced settings', 'description': {'raw': 'Intention:\\nLook up something in another window\\n\\nSteps to Reproduce:\\n1. Open Media settings for an existing image, using Safari.\\n\\n2. Click on \"Advanced settings\".  Don\\'t click inside any text field (e.g., width or height).\\n\\n3. Decide that you need to go to another window or browser tab for a moment, so click elsewhere.\\n\\n4. Go back to VisualEditor.\\n\\n5. Discover that the Media settings dialog has put you back in \"General settings\" again.\\n\\nConverse is also true:  if you put the text cursor in the \"Height\" box and then switch to \"General settings\" before leaving the page for a moment, you will be flipped back to \"Advanced settings\".\\n\\n\\n\\nReproducible: Always\\n\\nReproducible in Safari, not in Firefox.  Perhaps it\\'s because Safari \"helpfully\" flips the box to wherever the text cursor is, and Firefox ignores it?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392144760, 'spacePHID': None, 'dateCreated': 1392144240, 'dateModified': 1392144760, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61226', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Double return arrow getting added after adding Galley just before a hiero', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a special character \\n3.Add a hiero on the next line\\n4.Save the page \\n5.Reopen the page, add a gallery just after the special character but before hiero\\n6.Save the page\\n7.Reopen the page\\n\\nObserved Result:\\nDouble arrow appears just after gallery but before hiero\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/Justhiero?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13041}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406754182, 'spacePHID': None, 'dateCreated': 1392082080, 'dateModified': 1417570763, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61162', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image type is not getting changed accordingly with the selection in Media Settings>Advanced Settings', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the page in VE\\n2.Add an image\\n3.Go to Media Settings>Advanced Settings\\n4.Change the image type to Thumbnail ,Frame or Border\\n5.Apply the changes\\n\\nObserved Result:\\nThere is no apparent different in either of these image types when selected\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=10thFeb&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395354454, 'spacePHID': None, 'dateCreated': 1392063240, 'dateModified': 1417570926, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61153', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Insert Media only searches commons', 'description': {'raw': '**Author:** `robert.labrie`\\n\\n**Description:**\\nThe VisualEditor insert media only searches commons. I have a media item called \"WOM HighLevelDesign.png\" but when searching for HighLevelDesign there are no results. Looking at the request in Firebug:\\n\\nRequest:\\nGET http://commons.wikimedia.org/w/api.php?callback=jQuery18305320913342615314_1392057641882&format=json&action=query&generator=search&gsrsearch=HighLevelDesign&gsrnamespace=6&gsrlimit=15&gsroffset=0&prop=imageinfo&iiprop=dimensions%7Curl&iiurlheight=150 HTTP/1.1\\nHost: commons.wikimedia.org\\nUser-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0\\nAccept: */*\\nAccept-Language: en-US,en;q=0.5\\nAccept-Encoding: gzip, deflate\\nReferer: http://opsdocs.carnival.com/index.php?title=Main_Page&veaction=edit\\nConnection: keep-alive\\n\\nResponse:\\nHTTP/1.1 200 OK\\nVia: 1.1 varnish, 1.1 varnish, 1.1 CCLPRDINFTMG3\\nConnection: Keep-Alive\\nProxy-Connection: Keep-Alive\\nContent-Length: 110\\nAge: 0\\nDate: Mon, 10 Feb 2014 19:33:02 GMT\\nContent-Type: text/javascript; charset=utf-8\\nServer: Apache\\nAccept-Ranges: bytes\\nX-Powered-By: PHP/5.3.10-1ubuntu3.9+wmf1\\nx-content-type-options: nosniff\\nCache-Control: private\\nx-frame-options: SAMEORIGIN\\nVary: Accept-Encoding,X-Forwarded-Proto\\nX-Vary-Options: Accept-Encoding;list-contains=gzip,X-Forwarded-Proto,Cookie;string-contains=commonswikiToken;string-contains=commonswikiLoggedOut;string-contains=forceHTTPS;string-contains=commonswikiSession;string-contains=centralauth_Token;string-contains=centralauth_Session;string-contains=centralauth_LoggedOut;string-contains=mf_useformat;string-contains=stopMobileRedirect\\nX-Varnish: 2999015801, 4264856558\\nX-Cache: cp1055 miss (0), cp1052 frontend miss (0)\\n\\n\\njQuery18305320913342615314_1392057641882({\"query\":{\"searchinfo\":{\"totalhits\":0,\"suggestion\":\"Hauserdesign\"}}})\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392774395, 'spacePHID': None, 'dateCreated': 1392060960, 'dateModified': 1717447423, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61151', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Text in Insert menu and in Option menu displays differently', 'description': {'raw': 'This happens with Monobook (I tried this with Chrome on fr. and it.wp).\\nThe text in the Option menu is in a larger and different font than the one under Insert.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414624517, 'spacePHID': None, 'dateCreated': 1392060360, 'dateModified': 1414624517, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61150', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Gallery remains highlighted even after clicking elsewhere in the page', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n1.Open a page with Ve\\n2.Select a gallery\\n3.Open the gallery inspector \\n4.Click else where in the page to close the inspector\\n\\nObserved Result:\\nThe gallery remains highlighted in the page though it is not selected and link inspector is not appearing on the gallery\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12831}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402921625, 'spacePHID': None, 'dateCreated': 1391816040, 'dateModified': 1443278208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61068', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Odd removal of table inside an image caption', 'description': {'raw': \"Actual Results:  \\nVisualEditor loses most of the table.\\n\\n\\nReproducible: Couldn't Reproduce\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=Misl&diff=594020475&oldid=593707943\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49942\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415883136, 'spacePHID': None, 'dateCreated': 1391814720, 'dateModified': 1424894577, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61064', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'MathJax equations are centered', 'description': {'raw': 'MathJax has started centering displayed equations. For example\\nhttps://en.wikipedia.org/w/index.php?title=Wikipedia_talk:WikiProject_Mathematics&curid=148395&diff=594391082&oldid=594388357\\nthe display equation is centered. Previously they were aligned left.\\n\\nLooking at the generated the code we see \\n<div class=\"MathJax_Display\" role=\"textbox\" aria-readonly=\"true\" style=\"text-align: center;\">\\n  <span class=\"MathJax\" id=\"MathJax-Element-2-Frame\" style=\"\"> ...\\n  </span>\\n</div>\\n\\nthe centering is in the code rather than in a style sheet.\\n\\nAligning equations to the left is the desirable format.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413758059, 'spacePHID': None, 'dateCreated': 1391801640, 'dateModified': 1527603366, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61051', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Ve preview header bar doesn't make sense\", 'description': {'raw': 'What am I previewing?!\\n\\nIn story 1625 we removed preview from VisualEditor but we left the header in place.\\nhttps://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1625\\n\\nThis looks strange as demonstrated by attachment as nothing as being previewed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13434}'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393456009, 'spacePHID': None, 'dateCreated': 1391800260, 'dateModified': 1393456009, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61050', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Table of Contents is not appearing properly in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Add Sub-heading 1 to sub-heading 4 \\n3.Save the page\\n4.Observe the table of contents\\n\\nObserved Result:\\nThe table of content is appearing without any style and  order\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan28thff\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13292}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394502330, 'spacePHID': None, 'dateCreated': 1391722200, 'dateModified': 1417570929, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60995', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: TypeError: OO.ui.IconButtonWidget is not a constructor appears in production and \"Save Page\" and \"Cancel\" button is not appearing inside VE', 'description': {'raw': 'Screenshot\\n\\nTypeError: OO.ui.IconButtonWidget  is not a constructor appears in production and \"Save Page\" and \"Cancel\" button is not appearing inside VE\\n\\nPage:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13263}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396380412, 'spacePHID': None, 'dateCreated': 1391716320, 'dateModified': 1417570923, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60978', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: No vertical scrollbar on insert media (Firefox)', 'description': {'raw': 'Intention:\\nInsert media file in article using Firefox\\n\\nSteps to Reproduce:\\n0. Open up Firefox\\n1. Go to https://sv.wikipedia.org/wiki/Foo?veaction=edit&uselang=en\\n2. Click Insert -> Media\\n3. Write \"Foo\" in search window\\n4. Select image\\n5. Click Insert -> Media again\\n\\nActual Results:  \\nAfter 3: Image search returns 5*3 images\\nAfter 5: Image search returns more images accessible using the vertical scrollbar\\n\\nExpected Results:  \\nAfter 3: Image search returns more images accessible using the vertical scrollbar\\n\\nReproducible: Didn\\'t try\\n\\nThis problem becomes more severe since beginners don\\'t realise that there are ever more than 15 possible images, meaning they can usually not find an image they previously identified on Commons.\\n\\nWorks fine in Chrome though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404208489, 'spacePHID': None, 'dateCreated': 1391702640, 'dateModified': 1424894577, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60966', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs', 'description': {'raw': 'In the VE mode\\n\\nSteps to reproduce:\\n\\n1.Open the page with VE\\n2.Insert a reference for a text\\n3.Add the same reference again somewhere in the page\\n4.Add the reflist\\n5.Save the page\\n\\nObserved Result:\\n The repeated reference appears as (a,b) in the reflist in the readmode but as (1.0,1.1) inside VE in Betalabs.\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Ehat\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13133}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391659693, 'spacePHID': None, 'dateCreated': 1391649480, 'dateModified': 1417570954, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60934', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Page creation in alpha with VE wonky if you tap outside of the editable area', 'description': {'raw': \"In alpha, navigate to a non-existent page. You should see the text 'This page doesn't exist. Why not be bold and create it?'. Tap on the pencil edit icon. A cursor should show up in the editable area. Tapping outside of the editable area makes the cursor go away. Knowing where to tap in order to get the cursor back is a bit of a mystery. Perhaps we should make the tappable area for this visible to users.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-jh2oguhshocanixqvlfk', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391728851, 'spacePHID': None, 'dateCreated': 1391640660, 'dateModified': 1392248744, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60922', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't insert a new gallery if the user doesn't enter any contents for it\", 'description': {'raw': \"Steps to Reproduce:\\n1. Open the gallery inserter tool.\\n2. Don't add any content.\\n3. Discover that no matter what you do from here, it's going to add a pair of gallery tags that is difficult to select (for removal) in VisualEditor and pointless on the page.\\n\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394677396, 'spacePHID': None, 'dateCreated': 1391634600, 'dateModified': 1443276297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60915', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  You should be able to cancel a gallery without adding it', 'description': {'raw': 'Steps to Reproduce:\\n1. Click on Insert > Gallery\\n2. Think \"Oops, I meant to click on Transclusion\".\\n3. Try to get out of there without having a gallery added to your page.\\n\\nActual Results:  \\nClick the < button:  it adds a nearly invisible empty gallery.  Press the ESCape key:  it adds a nearly inisible empty gallery.  Click elsewhere:  it adds a nearly invisible empty gallery.\\n\\nExpected Results:  \\nI expected a trash can, but I\\'d prefer an X of the universal \"click here to cancel\" variety.\\n\\nReproducible: Didn\\'t try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391668703, 'spacePHID': None, 'dateCreated': 1391634360, 'dateModified': 1391668703, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60914', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enabling visualeditor does not result in usable visualeditor', 'description': {'raw': 'Steps to reproduce:\\n\\n#1 $ vagrant enable-role visualeditor\\nOk. Run \\'vagrant provision\\' to apply your changes.\\n\\n\\n\\n#2 $ vagrant list-roles\\nAvailable roles:\\n\\n  analytics\\n  antispam\\n  apisandbox\\n  betafeatures\\n  browsertests\\n  chromium\\n  cirrussearch\\n  cldr\\n  codeeditor\\n  commonsmetadata\\n  echo\\n  education\\n  eventlogging\\n  fundraising\\n  gadgets\\n  geodata\\n  geshi\\n  gettingstarted\\n  guidedtour\\n  hadoop\\n  hhvm\\n  hive\\n  massmessage\\n  math\\n  mathsearch\\n  mleb\\n  mobilefrontend\\n  multimedia\\n  multimediaviewer\\n  navigationtiming\\n  oauth\\n  parserfunctions\\n  pdfhandler\\n  proofreadpage\\n  remote_debug\\n  scribunto\\n  timedmediahandler\\n  uploadwizard\\n* visualeditor\\n  wikieditor\\n  wikimetrics\\n  xhprof\\n\\nRoles marked with \\'*\\' are enabled.\\nUse \"vagrant enable-role\" & \"vagrant disable-role\" to customize.\\n\\n\\n\\n#3 $ vagrant provision\\n[default] Running provisioner: puppet...\\nRunning Puppet with site.pp...\\ninfo: Applying configuration version \\'1391614793.16f99ad\\'\\ninfo: mount[files]: allowing mediawiki-vagrant access\\nnotice: /Stage[main]/Mediawiki::Parsoid/Package[nodejs]/ensure: ensure changed \\'purged\\' to \\'0.8.2-1chl1~precise1\\'\\nnotice: /Stage[main]/Mediawiki::Parsoid/File[/etc/init/parsoid.conf]/ensure: created\\nnotice: /Stage[main]/Mediawiki::Parsoid/Git::Clone[mediawiki/services/parsoid/deploy]/Exec[git clone mediawiki/services/parsoid/deploy]/returns: executed successfully\\nnotice: /Stage[main]/Mediawiki::Parsoid/File[localsettings.js]/ensure: defined content as \\'{md5}11ba3cfc1124f11f4a507a56cc70d34c\\'\\ninfo: /Stage[main]/Mediawiki::Parsoid/File[localsettings.js]: Scheduling refresh of Service[parsoid]\\nnotice: /Stage[main]/Mediawiki::Parsoid/Service[parsoid]/ensure: ensure changed \\'stopped\\' to \\'running\\'\\nnotice: /Stage[main]/Mediawiki::Parsoid/Service[parsoid]: Triggered \\'refresh\\' from 1 events\\nnotice: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Git::Clone[mediawiki/extensions/VisualEditor]/Exec[git clone mediawiki/extensions/VisualEditor]/returns: executed successfully\\nnotice: /Stage[main]/Role::Visualeditor/Mediawiki::Extension[VisualEditor]/Mediawiki::Settings[VisualEditor]/File[/vagrant/settings.d/puppet-managed/10-VisualEditor.php]/ensure: created\\nnotice: Finished catalog run in 587.81 seconds\\n\\n\\n\\n#4 Go to http://127.0.0.1:8080/wiki/Main_Page\\n\\n\\n\\n#5 Error page is displayed:\\n\\nMediaWiki 1.23wmf2 required--this is only 1.22alpha\\n\\nBacktrace:\\n\\n#0 /vagrant/mediawiki/extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW(\\'1.23wmf2\\')\\n#1 [internal function]: VisualEditorHooks::onSetup()\\n#2 /vagrant/mediawiki/includes/Setup.php(569): call_user_func(\\'VisualEditorHoo...\\')\\n#3 /vagrant/mediawiki/includes/WebStart.php(161): require_once(\\'/vagrant/mediaw...\\')\\n#4 /vagrant/mediawiki/index.php(55): require(\\'/vagrant/mediaw...\\')\\n#5 {main}\\n\\n\\n\\n#6 Looks like mediawiki-vagrant uses an old version of mediawiki (1.22alpha) and visualeditor needs version 1.23wmf2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391693357, 'spacePHID': None, 'dateCreated': 1391618640, 'dateModified': 1496862095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60905', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: template and link inspectors not working for some users at it.wp', 'description': {'raw': 'Might need to split this later, and/or add more details, here\\'s what we know now from it.wp users.\\n\\nNot logged in user, Firefox 26.0, Windows 7 reports the following.\\n*When you try to edit a template, the template inspector will look empty.\\n*When you try to add a new template, the inspector won\\'t provide any suggestions for existing ones.\\n*When you try to choose an option from the 3-bars menu on the right, none will work (nothing will happen clicking on those), except for the \"Switch to wikitext\" one.\\n\\nUser:Nnvu, Chrome ver. 32.0.1700.102 m, Windows 8.1, Vector reports having the same issues, plus:\\n*When you click on a wikilink anywhere in the page, instead than getting the box to edit it, you\\'ll be directed to the linked page (the page will even ask you if you\\'re sure you wanna leave).\\n*When you save the page, it will stay in edit mode. If you click Save again, you\\'ll get both the save dialog and the loading bar that keeps going. (The page results correctly saved from the history, nonetheless.) \\n\\nNnvu could check the console once, and said that this message\\n*event.returnValue is deprecated. Please use the standard event.preventDefault() instead.\\nappeared once the editing page was loaded, while\\n*Uncaught TypeError: Object #<Object> has no method \\'apiRequest\\' VM189:567\\nis what he got while trying to type inside the template inspector.\\n\\nVE will work fine for him:\\n*if he logs out (but while when he\\'s logged-in, disabling all BetaFeatures, all the gadgets and even blanking .js pages won\\'t still help);\\n*if he uses FF, as a logged-in user.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391793651, 'spacePHID': None, 'dateCreated': 1391612040, 'dateModified': 1391794669, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60899', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Math Inspector icon and Link inspector icon appears together on a Math formula which has link applied on it', 'description': {'raw': 'Two inspector icon together over the math function\\n\\nSteps to produce:\\n\\n\\n1.Open the page with VE\\n2.Add a Math function such as \\\\pi\\n3.Now add a text before that such as life of pi\\n4.Now select the text and the math function together\\n5.Apply link on it\\n6.Now select the Math function\\n\\nObserved Result:\\nThe Math inspector icon and the link inspector icon opens together over the math function.\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/w/index.php?title=Test2chrome&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56644\\n\\n**Attached**: {F12944}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399047303, 'spacePHID': None, 'dateCreated': 1391552880, 'dateModified': 1441911418, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60850', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Blanking a page doesn't remove protection templates\", 'description': {'raw': 'Similar to bug 52036.\\nWhen you blank a page with VE, protection templates like\\nhttps://en.wikipedia.org/wiki/Template:Pp-move-indef\\nor\\nhttps://en.wikipedia.org/wiki/Template:Pp-blp\\nwill stay.\\n\\nhttps://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=593889831\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52036'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393271673, 'spacePHID': None, 'dateCreated': 1391525700, 'dateModified': 1393271673, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60830', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Math Formula appears (However does not get placed) inside gallery while opening Latex over gallery', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a gallery\\n3.Select the gallery\\n4.Open a Math Formula window.\\n5.Type something on the editor\\n\\nObserved Result:\\nThe math function appears inside gallery .However, if you close the math inspector it will place the math function properly after the gallery not inside it.\\n\\nSee the screenshot attached.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12825}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397757894, 'spacePHID': None, 'dateCreated': 1391474580, 'dateModified': 1417570919, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60801', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Browser test for VisualEditor availability on production wikis', 'description': {'raw': \"**Author:** `jhall`\\n\\n**Description:**\\nPer a request from James Forrester, we should create a new browser test(s) in the VisualEditor repo that will verify the availability of VisualEditor on production wikis in two categories:\\n\\n1) Test whether VE loads if invoked on each of the currently ~300 wikis that VisualEditor is deployed to.  This is just checking that ?veaction=edit causes a VE surface to load.\\n\\n2) Test whether VE's edit tab appears on the ~150 wikis to which is is deployed to as default for all users.  This is checking that the tab for VisualEditor loads for logged-out users.\\n\\nSome caveats regarding this new test:\\n\\n1)  The test should not perform any writing actions to the wiki (just loading, no saving).\\n\\n2) We're probably only looking for a quick verification every week or so, rather than \\n\\u200bevery 12 hours (as with the existing schedule for other VE browser tests).\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60842\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392395125, 'spacePHID': None, 'dateCreated': 1391469180, 'dateModified': 1392395125, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60797', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: archive search in page header triggers error', 'description': {'raw': 'screenshot of error\\n\\nIf I have {{archives}} or {{Talk header}} in the page header area, Flow gives this error (screenshot):\\n\\nThe error message received was: Exception Caught: ID searchbox already defined\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60816\\n\\n**Attached**: {F13408}'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391644687, 'spacePHID': None, 'dateCreated': 1391463960, 'dateModified': 1391644687, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60785', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The Strikethrough and Underline gets overlapped for a superscript text', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Ve\\n2.Select a text\\n3.Apply Superscript\\n4.Apply Strikethrough\\n5.Apply Underline\\n6.Unselect superscript  \\n7.Make it superscript again (Observe that strikethrough is now below the text, this is one issue)\\n8.Unselect Underline\\n9.Make it underline again\\n\\nObserved Result\\nThe Strikethrough and Underline gets overlapped for a superscript text\\n\\n**This is a FireFox only bug.Works perfectly on Chrome**\\n\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nhttps://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13396}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402294906, 'spacePHID': None, 'dateCreated': 1391459760, 'dateModified': 1417570780, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60782', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  The special character inserter tool should use the full width of the toolbar, rather than a narrow floating box', 'description': {'raw': \"The floating palette for the special character tool is annoyingly out of reach if your cursor is at the bottom of your screen.  You have to scroll down (sometimes a lot) to reach the character that you want.  It's also narrow, which limits the number of characters that can be seen at once.\\n\\nIt should be replaced with a fixed, full-width tool that is attached to the main toolbar.  This allows more characters to be displayed at once and is always visible, no matter where you are typing.\\n\\nThis might also be convenient way to address the problems in bug 60657.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1425547616, 'spacePHID': None, 'dateCreated': 1391448240, 'dateModified': 1438734960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60770', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'parsoidserver-http-bad-status', 'description': {'raw': 'http://en.m.wikipedia.beta.wmflabs.org/w/api.php?format=json&action=visualeditor&paction=parse&page=Selenium_Edit_Test\\n\\nAny idea why this request ends up with the response:\\n{\"servedby\":\"deployment-apache32\",\"error\":{\"code\":\"parsoidserver-http-bad-status\",\"info\":\"404\"}}\\n\\nIt prevents VisualEditor from loading on mobile...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391651487, 'spacePHID': None, 'dateCreated': 1391408100, 'dateModified': 1391651487, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The Image resize handler along with the blue highlighted box gets displaced while resizing the window', 'description': {'raw': 'Screenshot attached\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which contains an image\\n2.Now select the image\\n3.Resize the window (Not the image)\\n\\nObserved Result:\\n\\n\\nThe image resize handle gets displaced\\n\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13198}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394128066, 'spacePHID': None, 'dateCreated': 1391208840, 'dateModified': 1417570932, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor - Inserting a gallery while having an image selected breaks the visual editor.', 'description': {'raw': '(Tested on Firefox 26, Windows Vista)\\nSteps to reproduce\\n- Edit the [[Jefferson Davis County Courthouse (Mississippi)]] page using the visual editor.\\n- Click the image present in the article.\\n- Press \"Insert => Gallery\".\\n\\nThe result of this is that the visual editor will break to a point where one cannot use it without entirely reloading the page. For example:\\n- Pressing \"Insert => Gallery\" again yields no reaction.\\n- Pressing \"Insert => Special Character\" results in a window that seems to be a hybrid of the gallery and character insertion tool.\\n- Clicking any page link in the article will no longer result in the usual \"Edit Link\" popup. Using the link button on the interface will result in a hybrid version of the link window and the gallery window.\\n\\nInterestingly, there are no errors in Firefox\\'s error console.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows Vista\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391204983, 'spacePHID': None, 'dateCreated': 1391204400, 'dateModified': 1417570955, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60699', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Content of different article is showing up in the Edit mode of VE in Betalabs; Parsoid does not find its config and uses default settings instead', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Create a page on Betalabs\\n2.Add some content and save it\\n3.Reopen the page with VE\\n\\nObserved Result:\\nContent of some article is showing up instead of my own edited content\\n\\n\\nSee the screenshot attached\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/31st_january\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13186}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391629537, 'spacePHID': None, 'dateCreated': 1391200560, 'dateModified': 1391635700, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60694', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide the character inserter everywhere that you can input text', 'description': {'raw': \"Intention:\\nAdd special characters\\n\\nSteps to Reproduce:\\nIf any of the following that happen to rely on special characters:\\n\\n* A template\\n* A parameter name in said template\\n* Data for parameter (e.g., the name of a person or place)\\n* A link to another page\\n* A category\\n* A media item (e.g., image) that you can't find otherwise\\n* An image or a caption in a image gallery\\n* An edit summary\\n\\nthen they cannot be successfully used in VisualEditor.  Probably there are uses for it in the Mathematics Formulae tool as well.  \\n\\nBasically, if you have a cursor for typing anything, anywhere in the entire VisualEditor interface, then you need access to the special character inserter.\\n\\n\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1425416329, 'spacePHID': None, 'dateCreated': 1391125500, 'dateModified': 1425523785, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60657', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When followed by a template, the template edit icon is appearing over an image', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Now add an image to the page\\n3.Now add a template infobox-country or any other infobox template like infobox-company\\n4.Save the page\\n5.Open the page again.\\n6.Now Select the template \\n\\nObserved Result:\\n\\nThe template edit icon is appearing over the image now\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Image_after_template\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13094}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393455560, 'spacePHID': None, 'dateCreated': 1391122080, 'dateModified': 1417570952, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60652', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:General Settings and Advanced Settings button/text field labels are missing on Media Settings widget for test2 and mw.org', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Insert and image \\n2.Go to Media Settings\\n\\nObserved Result:\\n\\nGeneral Settings and Advanced Settings button tags are missing on Media Settings widget\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13065}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391203627, 'spacePHID': None, 'dateCreated': 1391112720, 'dateModified': 1417570955, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking on Increase/Decrease Indentation button multiple times shows \"Confirm Navigation?\" dialog box on mediawiki.org', 'description': {'raw': 'Screenshot attached\\n\\nSteps to reproduce;\\n\\n\\n1.Open a page with VE\\n2.Add a bullet list or a numbered list\\n3.Keep on pressing the Add or decrease indentation  button for a bullet point \\n\\n\\nObserved Result:\\n\"Confirm Navigation?\" dialog box are showing up .\\n\\nSee the screenshot attached.\\n\\nTest Environment: mw.org\\nBrowser: Chrome Version 26.0.1410.65 & FF25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://www.mediawiki.org/w/index.php?title=User:RYasmeen_(WMF)&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13048}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1431640567, 'spacePHID': None, 'dateCreated': 1391111220, 'dateModified': 1438734964, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60637', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Review your changes\" and \"Save Page\" button layout missing in test2', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n\\n1.Open any page with VE in test 2\\n2.Add some content and Save page\\n\\nObserved Result:\\n\"Review your changes\" and \"Save Page\" button layout missing in test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13039}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391120091, 'spacePHID': None, 'dateCreated': 1391109780, 'dateModified': 1417570955, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60634', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Move Selenium tests from root folder of qa/browsertests repository to tests/browser folder', 'description': {'raw': 'It would make sense, since all repositories (except VisualEditor) have Selenium tests already there:\\n\\nhttps://github.com/wikimedia/mediawiki-selenium#links\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391772219, 'spacePHID': None, 'dateCreated': 1391077980, 'dateModified': 1391789269, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60614', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Getting exception error on Betalabs from /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php', 'description': {'raw': 'Screenshot\\n\\nCannot load any page on Betalabs.Getting the following error:\\n\\n6ca85571] /wiki/29th_January Exception from line 84 of /data/project/apache/common-local/php-master/extensions/Wikidata/extensions/Wikibase/repo/Wikibase.hooks.php: Wikibase: Incomplete configuration: $wgWBRepoSettings[\"entityNamespaces\"] has to be set to an array mapping content model IDs to namespace IDs. See ExampleSettings.php for details and examples.\\n\\nBacktrace:\\n\\n#0 [internal function]: Wikibase\\\\RepoHooks::onSetupAfterCache()\\n#1 /data/project/apache/common-local/php-master/includes/Hooks.php(206): call_user_func_array(string, array)\\n#2 /data/project/apache/common-local/php-master/includes/GlobalFunctions.php(3976): Hooks::run(string, array, NULL)\\n#3 /data/project/apache/common-local/php-master/includes/Setup.php(520): wfRunHooks(string)\\n#4 /data/project/apache/common-local/php-master/includes/WebStart.php(153): require_once(string)\\n#5 /data/project/apache/common-local/php-master/index.php(46): require(string)\\n#6 /data/project/apache/common-local/w/index.php(3): require(string)\\n#7 {main}\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n\\n**Attached**: {F12982}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391045340, 'spacePHID': None, 'dateCreated': 1391045040, 'dateModified': 1391090756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60606', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor isn't able to handle header and row templates\", 'description': {'raw': \"The VisualEditor template editor works on infobox templates like https://en.wikipedia.org/wiki/Template:Infobox_NRHP . On templates like https://en.wikipedia.org/wiki/Template:NRHP_header and https://en.wikipedia.org/wiki/Template:NRHP_row it doesn't work (yet) probably because these templates generate tables. We have a lot of these templates in a lot of different languages, see for example https://en.wikipedia.org/wiki/Category:Monument_list_templates . It would be nice if VE could be used to edit these templates.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-cw4amt4ewxdze5qcjdca', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437692927, 'spacePHID': None, 'dateCreated': 1391033760, 'dateModified': 1439425482, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60598', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After adding an empty gallery in a list, the list continues adding bullets/numbered points even after hitting return twice', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394488268, 'spacePHID': None, 'dateCreated': 1391024460, 'dateModified': 1417570930, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60592', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Special character inserter behaves oddly if you don't click somewhere in the page first\", 'description': {'raw': 'Intention:\\nAdd a special character.\\n\\nSteps to Reproduce:\\n1. Open a page in VisualEditor.  Don\\'t click anywhere in it.\\n\\n2. Go to Insert > Special characters to open the Special charater inserter tool.\\n\\n3. Click on a character (or several).\\n\\nActual Results:  \\nNothing is added, but the \"Save\" button lights up.  You can\\'t use it, though.\\n\\nIf you click elsewhere, the tool disappears, but nothing else happens.  \"Save\" is still green, but you still can\\'t use it.\\n\\nIf you go back into the special character tool and add a new special character, then all the original ones appear at the start of the page, but the tool\\'s dialog box is still open.  \\n\\nIf you then cancel (to get rid of the box), Bad Things happen, including snowmen and partial duplication of the page.  You still can\\'t save.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400546311, 'spacePHID': None, 'dateCreated': 1390866360, 'dateModified': 1411660186, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60507', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: 'mozMatchesSelector' called on an object that does not implement interface when launching VE\", 'description': {'raw': \"When launching VE in Firefox, it throws the following error:\\n'mozMatchesSelector' called on an object that does not implement interface\\n\\nHappens on beta labs and local master.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415884389, 'spacePHID': None, 'dateCreated': 1390864440, 'dateModified': 1415884389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60504', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Save dialog no longer expands when viewing diff', 'description': {'raw': 'When you click \"Review your changes\" in the save dialog, it used to grow to accommodate the fact that diffs tend to be bigger than the regular save dialog contents. However, it stopped doing this a while ago.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394066297, 'spacePHID': None, 'dateCreated': 1390857780, 'dateModified': 1443276303, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60494', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable on redirects', 'description': {'raw': 'Redirects are normal wiki pages of main ns. So why not should allow to edit them with VisualEditor? For example in cases, I remove redirect and want edit a page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390695336, 'spacePHID': None, 'dateCreated': 1390664940, 'dateModified': 1417570953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60425', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Page rendered completely blank', 'description': {'raw': \"When I loaded [[mw:Mobile wikitext editing]] recently as a logged-in user, the page looked completely blank. This may be an issue in VisualEditor, I'm not sure. Purging the page fixed the issue.\\n\\nMy suspicion is that Parsoid somehow returned blank content. Unfortunately I'm unable to reproduce this issue.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/Mobile_wikitext_editing\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391717249, 'spacePHID': None, 'dateCreated': 1390590840, 'dateModified': 1391717249, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60402', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Clicking the Media Settings Widget does not open the dialog', 'description': {'raw': \"I'm on 1.23wmf10 and the master build of both VisualEditor and Parsoid. I can insert and resize an image just fine, but clicking on the icon in the upper right performs no action. I discovered the following message:\\n\\nUncaught TypeError: undefined is not a function \\n\\nload.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%2Cmwcore%2Cmwgalle…:344\\nVeUiMediaSizeWidget load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%2Cmwcore%2Cmwgalle…:344\\nve.ui.MWMediaEditDialog.initialize load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%2Cmwcore%2Cmwgalle…:528\\noo.EventEmitter.emit load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.pl…:112\\n(anonymous function) load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.pl…:125\\npollExternalStylesheets load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Cmediawiki%2CviewPageTarget%7Cjquery.pl…:124\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xd3dshn3ykvvbsxmqbg6', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401744326, 'spacePHID': None, 'dateCreated': 1390582500, 'dateModified': 1417570760, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60397', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Make {{reflist}} update with new refs as you add them, just like <references /> does', 'description': {'raw': \"Intention:\\n<References /> automatically updates as you edit a page.  The {{Reflist}} template does not.  Can the handling of the template be improved so that refs inside the {{ref list}} template also update automatically?\\n\\n\\n\\n\\nReproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1434476263, 'spacePHID': None, 'dateCreated': 1390437480, 'dateModified': 1434476263, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60361', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The image resize handle is not appearing at the corner of the selection box around the image when it has a caption', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page which contains image with VE\\n2.Add a large caption to the image by going to Media Settings\\n3.Click on \"Apply Changes\"\\n4.Attempt to resize the image\\n\\nObserved Result:\\nThe image resize handle is not at the most bottom-left corner of the blue highlighted selection box around the image but at the corner of the image.\\nIt looks a bit odd to have it somewhere in the middle of the border when it has a large caption.\\nProbably ,having it at the corner most corner will look better.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F13020}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390585818, 'spacePHID': None, 'dateCreated': 1390423260, 'dateModified': 1417570956, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60355', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The selected parameter gets switched upon mouse-up beyond the right panel', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a template like Cite web\\n3.Select the parameter URL\\n4.Add a value in this field like http://yahoo.com\\n5.Now select this text from right to left\\n6.Mouse up just a little beyond the borderline between left panel and right panel\\n\\nObserved Result:\\n\\nThe parameter on the right panel gets switched to the next parameter which is \"Source Title\"\\n\\nSee the screenshot attached.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nPage:https://test2.wikipedia.org/w/index.php?title=22nd_january&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13019}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415054014, 'spacePHID': None, 'dateCreated': 1390419240, 'dateModified': 1417570680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60353', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE does not appear at all on beta labs', 'description': {'raw': 'Seen as of Jan 22\\n\\nAs a logged in user, edit any page on http://en.wikipedia.beta.wmflabs.org/ with VisualEditor. \\n\\nUser sees the ve-init-mw-viewPageTarget-loading bars moving, but VE never arrives. \\n\\nChecked in Chrome and Firefox\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390506391, 'spacePHID': None, 'dateCreated': 1390405560, 'dateModified': 1390506406, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60346', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Visualeditor:A Return character gets placed between two galleries placed one after another', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which has a gallery in it\\n2.Add another gallery code just after the already existing one\\n3.Save the page\\n4.Reopen the page with VE\\n\\nObserved Result\\nA return arrow appears between the two galleries\\n\\nSee the screenshot attached.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage: https://test2.wikipedia.org/wiki/Thedomtest?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12925}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406754223, 'spacePHID': None, 'dateCreated': 1390348620, 'dateModified': 1417570762, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60312', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The gallery inspector adds a newline while opening up a gallery', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which has for example the following gallery code:\\n<gallery>\\nFile:Joo Chiat Place.jpg|Item 1\\nFile:Joo Chiat Place.jpg|a link to [[Help:Contents]]\\nFile:Joo Chiat Place.jpg\\nFile:Joo Chiat Place.jpg|alt=An example image. It has flowers\\nFile:Joo Chiat Place.jpg| ''italic caption''\\n</gallery>\\n\\n2.Click on the gallery and open it with the new gallery inspector\\n\\nObserved Result:\\nThere is an extra newline inserted at the beginning of gallery code inside the inspector.\\n\\n\\nSee the screenshot attached.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/Thedomtest?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12923}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429599910, 'spacePHID': None, 'dateCreated': 1390346700, 'dateModified': 1442930214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60310', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference numbers do not display properly on fr.wp', 'description': {'raw': 'NemesisIII reports that when VEditing a page, existing reference numbers do not appear as \"superscripted\" as they should.\\nSee section \"projet\" of https://commons.wikimedia.org/wiki/File:Bug_%C3%A9diteur_visuel_affichage_appels_de_r%C3%A9f%C3%A9rence.png (from https://fr.wikipedia.org/wiki/Avenue_Foch?veaction=edit ).\\nNumber 3 and 4 are existing references, and they are very low. Number 5 instead is a newly added reference, which displays ok (note that this reference does not really exist in the article, it was added just to take the screenshot).\\n\\nAccording to my tests, only fr.wp seems affected. I was able to reproduce this with\\n*Firefox (both Vector and Monobook)\\n*Chrome (Monobook)\\n*Opera (while logged out).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414624599, 'spacePHID': None, 'dateCreated': 1390305780, 'dateModified': 1439679943, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60280', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Changes to VisualEditor on eswiki as result of vote', 'description': {'raw': '**Author:** `llamaal_wikis`\\n\\n**Description:**\\nIntention:\\nAfter the conclusion of https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual on the Spanish Wikipedia, some changes to the status of VE in that project have to be implemented:\\n\\n1. VE should now be opt-in\\n2. The \"edit\" tab should return to wikitext\\n3. VE should be presented as part of Beta Features\\n4. The tab for VE, if users activate it, should be \"Editor VisualBETA\"\\n\\nRegards,\\n\\nLlamaAl\\n\\n\\n\\n\\nReproducible: Didn\\'t try\\n\\nAfter the conclusion of https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual on the Spanish Wikipedia, some changes to the status of VE in that project have to be implemented:\\n\\n1. VE should now be opt-in\\n2. The \"edit\" tab should return to wikitext\\n3. VE should be presented as part of Beta Features\\n4. The tab for VE, if users activate it, should be \"Editor VisualBETA\"\\n\\nRegards,\\n\\nLlamaAl\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390011045, 'spacePHID': None, 'dateCreated': 1390009560, 'dateModified': 1487197650, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60189', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Only a single node is appearing to drag an image to resize', 'description': {'raw': 'Single node\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE which has image inside it\\n2.Select the image\\n\\nObserved Result:\\nThere is just one node appearing on the bottom-left corner of the image to resize it,previously there used to four nodes to drag.\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/, wmf11\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13171}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389907705, 'spacePHID': None, 'dateCreated': 1389907260, 'dateModified': 1417570962, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60150', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:\"Cite error: <ref> tags exist, but no <references/> tag was found \"  after adding a reference in the caption of an image although there was <references/> tag', 'description': {'raw': 'In edit source mode\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which has some references and <references/> tag added \\n2.Add an image in the page\\n3.Go to media settings and add a caption with reference inside it\\n4.Save the page\\n\\nObserved Result:\\nAn error appears in the read mode :\"Cite error: <ref> tags exist, but no <references/> tag was found \"\\n\\nAlso in the resulting wikitext, the reference inside image did not get added in the <references/> section\\n\\n\\n\\nAlthough if you go to Edit mode the reference inside the image is correctly showing up in the <references/> tag.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nSample Page:https://test2.wikipedia.org/wiki/Wmf11\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13149}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390022111, 'spacePHID': None, 'dateCreated': 1389902400, 'dateModified': 1417570960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60146', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Translatewiki.net is not tracking VisualEditor core messages, so they're not updateable\", 'description': {'raw': 'The i18n messages for the Toolbar insert button and the subsequent special character tree does not seem to sync with translated messages at Translatewiki. \\nFor some reason French and German gives correct messages but others give English default messages.\\n\\nThe strings are:\\nvisualeditor-toolbar-insert\\nvisualeditor-specialcharacter-button-tooltip\\nvisualeditor-specialcharacterinspector-title\\nvisualeditor-specialcharinspector-characterlist-insert\\n\\nPossibly related to them being marked as non-translatable on translatewiki.\\n\\nSee annotated screenshot at:\\nhttps://commons.wikimedia.org/wiki/File:VisualEditorBugInsert.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': 'PHID-USER-w5a723w3wes6jd5wskgg', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392138855, 'spacePHID': None, 'dateCreated': 1389894780, 'dateModified': 1392983896, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60140', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Detection of the edit button broken in GettingStarted guided tour 'gettingstartedtasktoolbar'\", 'description': {'raw': \"**Author:** `swalling`\\n\\n**Description:**\\nScreenshot on enwiki\\n\\nDetection of the 'edit' tab and section edit links is broken currently, probably due to https://gerrit.wikimedia.org/r/#/c/97701/ change in VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n\\n**Attached**: {F13059}\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389832577, 'spacePHID': None, 'dateCreated': 1389826140, 'dateModified': 1389832577, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60111', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Keep Going overlay overlaps with visualeditor overlay', 'description': {'raw': 'https://en.m.wikipedia.org/wiki/Lost_Coon_Lake?title=Lost_Coon_Lake&campaign=mobile-mainpage-keepgoing-links&mobileaction=alpha#editor/0\\n\\nExpected:\\nThe Keep Going overlay should appear below the VE overlay.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390607906, 'spacePHID': None, 'dateCreated': 1389820920, 'dateModified': 1392248882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60107', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Incorrect wiki code when applying category', 'description': {'raw': 'Hi\\nIf I apply a category to a page using VE, it generates an incorrect code (for example %2520 instead of _ I think) and it has only one square character.\\n\\nLatest git of VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: http://wiki.mc128k.info/index.php/Test'}, 'authorPHID': 'PHID-USER-vj2bbc63joi46qr5a5nq', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394972583, 'spacePHID': None, 'dateCreated': 1389650340, 'dateModified': 1394995516, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60018', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"First edit in VE doesn't launch KeepGoing campaign\", 'description': {'raw': \"**Author:** `kwang`\\n\\n**Description:**\\nIf you are in the keep going campaign and you are in alpha, when you click edit you don't get VE you get the wikitext editor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391213409, 'spacePHID': None, 'dateCreated': 1389403020, 'dateModified': 1392248866, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59932', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Image size is appearing differently in the tooltip in  VE compared to the set value in Edit Source mode', 'description': {'raw': 'Screenshot in the Edit source mode\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE \\n2.Insert any image\\n3.Resize the image to specific size.For example:587x687px\\n4.Save the page\\n5.Open the page in Edit Source mode\\n\\n\\nObserved Result:\\nThe Edit source mode shows the size of the image differently as 587x411\\n\\nTest Environment: mw.org\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12636}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389909797, 'spacePHID': None, 'dateCreated': 1389383700, 'dateModified': 1417570961, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59920', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't maintain the selection when exiting from an inspector because users don't expect it\", 'description': {'raw': \"Intention:\\nIf I understand it correctly, the user defines a link target for text. This seems to highlight/mark the text for that user, so if the user then enters a space as the next letter as s/he wants to continue writing, this will overwrite the marked text. Says this happens with Safari 6.1.1 and Firefox 26.0 on OS X 10.7.5 and 10.8.5 (all four combinations). Haven't tried other browsers/operating systems. \\n\\nSteps to Reproduce:\\n1. Tried but could not duplicate this problem in Firefox 26 or Chrome 31\\n2. \\n3. \\n\\n\\n\\nReproducible: Couldn't Reproduce\\n\\nAndre says: https://bugzilla.wikimedia.org/show_bug.cgi?id=57716 item 2# feels slightly related but not exactly the same.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://sv.wikipedia.org/wiki/Wikipedia:VisualEditor/%C3%85terkoppling#L.C3.A4nkad_text_blir_markerad_och_f.C3.B6rsvinner\"}, 'authorPHID': 'PHID-USER-brn4v5ta45bnw4f5as3h', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390023404, 'spacePHID': None, 'dateCreated': 1389313080, 'dateModified': 1417570959, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59891', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The images of the article gets disappeared in the read mode after clicking on a newly added image in test 2', 'description': {'raw': 'In read mode\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add few images to the page\\n3.Save the Page\\n4.Now click on any of the newly added images \\n5.Press back button from the browser to go back to the article\\n\\nObserved Result:\\nThe images in the page gets disappeared in the readmode though opening the VE shows up all the images.\\n\\nTest Environment:https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/Wmf10\\n\\n\\nSee the screenshots attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12534}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389832746, 'spacePHID': None, 'dateCreated': 1389309540, 'dateModified': 1417570962, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59888', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Cutting the section heading along with the content under it and pasting them back moves the heading under the content', 'description': {'raw': 'Section heading got moved below the link of heading\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which has a section with section heading\\n2.Cut the whole section with its heading\\n3.Paste it back in the same position\\n\\nObserved Result:\\nThe heading of the section gets placed under the heading line with the contect\\n\\nSee the screenshot attached.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/9th_jan?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12519}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1442271871, 'spacePHID': None, 'dateCreated': 1389296400, 'dateModified': 1442271871, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59877', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Fatal error: Call to a member function matchStartAndRemove() on a non-object at Parser.php on line 3262', 'description': {'raw': \"[09-Jan-2014 19:32:59] Fatal error: Call to a member function matchStartAndRemove() on a non-object at /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php on line 3262\\nServer: mw1149\\nMethod: GET\\nURL: http://www.mediawiki.org/w/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*\\nBacktrace:\\n#0 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(3262): Parser::braceSubstitution()\\n#1 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Preprocessor_DOM.php(1113): Parser->braceSubstitution(Array, Object(PPFrame_DOM))\\n#2 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(3147): PPFrame_DOM->expand(Object(PPNode_DOM), 0)\\n#3 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(620): Parser->replaceVariables('{{ns:project}}:...')\\n#4 /usr/local/apache/common-local/php-1.23wmf10/includes/parser/Parser.php(4842): Parser->preprocess('{{ns:project}}:...', NULL, Object(ParserOptions))\\n#5 /usr/local/apache/common-local/php-1.23wmf10/includes/cache/MessageCache.php(1002): Parser->transformMsg('{{ns:project}}:...', Object(ParserOptions), NULL)\\n#6 /usr/local/apache/common-local/php-1.23wmf10/includes/Message.php(856): MessageCache->transform('{{ns:project}}:...', false, Object(Language), NULL)\\n#7 /usr/local/apache/common-local/php-1.23wmf10/includes/Message.php(592): Message->transformText('{{ns:project}}:...')\\n#8 /usr/local/apache/common-local/php-1.23wmf10/includes/Message.php(649): Message->toString()\\n#9 /usr/local/apache/common-local/php-1.23wmf10/extensions/VisualEditor/VisualEditorDataModule.php(94): Message->text()\\n#10 /usr/local/apache/common-local/php-1.23wmf10/extensions/VisualEditor/VisualEditorDataModule.php(129): VisualEditorDataModule->getMessageInfo()\\n#11 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoader.php(102): VisualEditorDataModule->getMessages()\\n#12 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoaderStartUpModule.php(265): ResourceLoader->preloadModuleInfo(Array, Object(ResourceLoaderContext))\\n#13 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoaderStartUpModule.php(150): ResourceLoaderStartUpModule->getModifiedTime(Object(ResourceLoaderContext))\\n#14 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoaderStartUpModule.php(224): ResourceLoaderStartUpModule::getModuleRegistrations(Object(ResourceLoaderContext))\\n#15 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoader.php(761): ResourceLoaderStartUpModule->getScript(Object(ResourceLoaderContext))\\n#16 /usr/local/apache/common-local/php-1.23wmf10/includes/resourceloader/ResourceLoader.php(516): ResourceLoader->makeModuleResponse(Object(ResourceLoaderContext), Array, Array)\\n#17 /usr/local/apache/common-local/php-1.23wmf10/load.php(43): ResourceLoader->respond(Object(ResourceLoaderContext))\\n#18 /usr/local/apache/common-local/w/load.php(3): require('/usr/local/apac...')\\n#19 {main}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389298261, 'spacePHID': None, 'dateCreated': 1389296160, 'dateModified': 1389298261, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59875', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in duplicated section headings', 'description': {'raw': \"Intention:\\nCut the appendices from an article (to see if they were the source of a problem), and then put them back (because they weren't)\\n\\nSteps to Reproduce:\\n1. Select several sections from the end of an article, all the way to the end of the page.\\n\\n2. Command-x to cut.\\n\\n3. Command-v to paste.\\n\\nActual Results:  \\nThe section headings were duplicated, but the content was not.  The result is two sets of section headings, the first of which is empty.  \\n\\nhttps://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FS%26D&diff=588724359&oldid=588539903\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1429554879, 'spacePHID': None, 'dateCreated': 1389227760, 'dateModified': 1438734972, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59847', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The <nowiki/> tag remains even after deleting spaces in between the link and re-applying a new link on it', 'description': {'raw': 'wikitext after step 8\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Type the following text:\\nTex ted\\n3.Select this part of the text \"Tex t\" with a space in between.\\n4.Now apply a link on it with command+k\\n5.Save the page.\\n6.Go to Edit source and observe the resulting wikitext for this is:\\n[[tex t]]<nowiki/>ed\\n\\n7.Now reopen the page delete the space make it \"texted\" and delete the link applied.\\n8.Reapply another link by selecting the whole text \"texted\"\\n\\nObserved Result:\\nThe <nowiki/> tag still remains.The resulting wikitext after step 8 is:\\n[[texted|text]]<nowiki/>[[texted|ed]]\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan8th&action=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12427}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390023700, 'spacePHID': None, 'dateCreated': 1389209520, 'dateModified': 1417570959, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59829', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor only loads in alpha in landscape mode on an iPad mini', 'description': {'raw': 'When a page is loaded in portrait mode the VisualEditor is not loaded. We should get clever about when to load it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391456138, 'spacePHID': None, 'dateCreated': 1389206760, 'dateModified': 1392248887, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59827', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor in all namespaces', 'description': {'raw': \"At some point VisualEditor should be enabled in the remaining namespace.\\n\\nI've seen a few requests for it, so this tracking bug will also provide an easy answer for why it isnt feasible now. e.g.\\n\\nhttps://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(proposals)&oldid=589149415#VE_on_Wikipedia:_namespace\\n\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389987954, 'spacePHID': None, 'dateCreated': 1389178800, 'dateModified': 1468188688, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59818', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:\"NetworkError: 404 Not Found\" appears while creating a new page with VE in FireFox 25', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Attempt to create a new page with VE in FireFox 25 in any way.For example:Type this URL:\\nhttp://en.wikipedia.beta.wmflabs.org/w/index.php?title=Textnew&veaction=edit\\n\\nObserved Result:\\n\\nAn error appears in the console:\\n\\n\"NetworkError: 404 Not Found - http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Textnew&veaction=edit\"\\nindex....on=edit\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12343}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389910442, 'spacePHID': None, 'dateCreated': 1389124080, 'dateModified': 1389910442, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59787', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \" Uncaught TypeError: Cannot read property \\'langlinks\\' of undefined \" appears while opening up Categories dialog box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the Categories Dialog box from Settings>Categories\\n\\nObserved Result:\\nThe error \" Uncaught TypeError: Cannot read property \\'langlinks\\' of undefined \" appears in the console.\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan7th&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12329}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389909731, 'spacePHID': None, 'dateCreated': 1389122820, 'dateModified': 1417570961, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59783', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Removing a blank == <nowiki /> == section heading leaves a <nowiki /> and produces a dirty diff', 'description': {'raw': \"Intention:\\nRemove an empty section heading created in a previous edit (bug 59647) by VisualEditor\\n\\nSteps to Reproduce:\\n1. Select the empty section heading\\n2. Press the delete/backspace key\\n\\n\\nActual Results:  \\nThe line went away.  However, a nowiki tag remained, and the first item in the list of categories was added to the last paragraph on the page, instead of remaining on its own line.\\n\\nExpected Results:  \\nThe section heading would go away.  Zero nowiki tags would be present.  Content above and below would not get smashed into a single line.\\n\\nReproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=Celebrity_branding&diff=589156903&oldid=589156664\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390023730, 'spacePHID': None, 'dateCreated': 1388854020, 'dateModified': 1390023914, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59650', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE automatically cuts off certain characters', 'description': {'raw': 'On the page on mediawiki.org https://www.mediawiki.org/wiki/Manual:ISBN (check action=history) VisualEditor keeps removing certain characters after I try to use it to make changes to the page. An example is given at https://www.mediawiki.org/wiki/VisualEditor:Test\\n\\nReproduction steps:\\n1. Set up a new page using the following code\\n<space><space><space><url><apostrophe>\\n<newline><space><space><space>\\nexample text1\\n\\nexample text2\\nWhere <space> is one hit of the spacebar and <url> could be any URL\\n2. Modify other places in the text, such as \"example text2\".\\n3. See the first character in \"example text1\" get cut off.\\n4. Modify \"example text2\" again and see \"example text1\" get cut off again.\\n\\nExample permalink: https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&oldid=873656\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uhn27l5qsridnw4vbhko', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1421790926, 'spacePHID': None, 'dateCreated': 1388796000, 'dateModified': 1438734972, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59628', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Can't save page after simple editing\", 'description': {'raw': 'Intention:\\nCopyedit an article\\n\\nSteps to Reproduce:\\n1. I italicized two words.  I cut two sentences (including links and one ref) and pasted them in a different place.\\n2. I tried to save the page.\\n\\n\\nActual Results:  \\nThe \"Save\" button looks normal, but clicking on it does nothing.\\n\\nExpected Results:  \\nThat I could save the page.  When I re-opened the page in VisualEditor and made the same changes, it worked (https://en.wikipedia.org/w/index.php?title=Neuralgia&diff=589057635&oldid=580866827).\\n\\nReproducible: Couldn\\'t Reproduce\\n\\nFirefox 26\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414811622, 'spacePHID': None, 'dateCreated': 1388793420, 'dateModified': 1414811783, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59625', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Checkbox \"Watch this page\" in save dialog unchecked even that page is watched', 'description': {'raw': 'Checkbox \"Watch this page\" in save dialog unchecked even that page is watched\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394063679, 'spacePHID': None, 'dateCreated': 1388779620, 'dateModified': 1417570933, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59606', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:\"TypeError: response.visualeditor is undefined\" appears while opening up the dialog box for adding catagories', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in FireFox\\n2.Click on the Categories button to open up the dialog box to add categories\\n\\nObserved Result:\\nTypeError: response.visualeditor is undefined appears in the console\\n\\nSee the screenshot attached\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/3rd_janff?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12794}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389910015, 'spacePHID': None, 'dateCreated': 1388778720, 'dateModified': 1417570961, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59605', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: edits correctly saved are missing on da.wp', 'description': {'raw': 'Intention:\\nI used my userpage as a sandbox\\nhttps://da.wikipedia.org/w/index.php?title=Bruger:Elitre_(WMF)&action=history,\\nand the edits in which I tried to add references do not show up in the history,\\nalthough I did manage to save them and also got the message that confirms this.\\n\\n(For the record, I was trying to reproduce\\nhttps://da.wikipedia.org/w/index.php?title=F-35_Lightning_II&diff=prev&oldid=7409486\\nand\\nhttps://da.wikipedia.org/w/index.php?title=Enhedslisten&diff=prev&oldid=7414100\\n, where there might be a connection between adding a reference and getting a\\nduplicated infobox).\\n\\n\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-vignevg3qewvdhgbbwuh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vignevg3qewvdhgbbwuh', 'dateClosed': 1432727427, 'spacePHID': None, 'dateCreated': 1388769060, 'dateModified': 1438734972, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59599', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Cutting and pasting internal links converts them to external links in Firefox', 'description': {'raw': 'Intention:\\nMove a sentence to a diffeent place on the page.\\n\\nSteps to Reproduce:\\n1. In Firefox, open a page containing existing [[links]] to other pages on the wiki.\\n2. Cut one of them.\\n3. Paste it in a different spot.\\n\\nActual Results:  \\nThe link gets converted from [[Link]] into [http://en.wikipedia.org/wiki/Link].\\n\\nSee https://en.wikipedia.org/w/index.php?title=User:Edgepedia/VE/S%26D&diff=588724142&oldid=588539903 and https://en.wikipedia.org/w/index.php?title=Silaum_silaus&diff=588803158&oldid=587979575  \\n\\nExpected Results:  \\nThe [[Link]] would remain an internal link.\\n\\nReproducible: Sometimes\\n\\nOne of these pages involved the {{sfn}} (shortened footnotes) template.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390024188, 'spacePHID': None, 'dateCreated': 1388682000, 'dateModified': 1390024188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59216', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Page redirects are not recognized by VisualEditor's link inspector\", 'description': {'raw': '1. Edit an article with VisualEditor\\n2. Select a word for which a redirect exists (not an actual page)\\n3. Click the \"link\" icon.\\n\\nEXPECTED\\n\\nSince a redirect exists, the link inspector shows the option in blue (since the link is functional). All the better if it is shown in italics, just like redirects are shown by MediaWiki in lists of pages.\\n\\nACTUAL\\n\\nRedirects are ignored by the link inspector. They appear just as red as a missing string. This creates a lot of extra work having to search the string manually in another window.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50593\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50240'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390024134, 'spacePHID': None, 'dateCreated': 1388672340, 'dateModified': 1417570958, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59208', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Another problem with Parsoid's <base>?  Clicking on links in subpages assumes that the links are subpages, too\", 'description': {'raw': 'Intention:\\nClick on a link within VisualEditor\\n\\nSteps to Reproduce:\\n1. Open an existing page in a subpage (e.g., User:Example/Sandbox)\\n2. Control-click on any [[link]] and copy the link\\n3. Paste the link somewhere to see what it says\\n\\n\\nActual Results:  \\nInstead of the expected link to en.wikipedia.org/wiki/Link, the user saw links to en.wikipedia.org/wiki/User:Username/Link.  When this intermittent problem was happening, then all links on the page would do it.  However, it only happened during some editing sessions/some days.\\n\\n\\n\\nReproducible: Sometimes\\n\\nFirefox 26 on Windows 7, Vector skin.  Is intermittent there; could not be immediately reproduced in either Firefox or Safari on a Mac.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48915\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58314'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395363345, 'spacePHID': None, 'dateCreated': 1388619840, 'dateModified': 1395363345, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59196', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Clear formatting removes the link from a text', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Select a text  \\n3.Apply some formatting from the formatting menu in the toolbar for example:\\nBold/Italic/Superscript\\n4.Also apply a link on the text\\n5.Now from the formatting menu select the \"Clear formatting\" option\\n\\nObserved Result:\\n\\nAlong with all the text formatting, the link applied on the text also gets removed.\\nIt is better if Clear formatting only removes the text formatting not the link applied because that is not part of text formatting options.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390025103, 'spacePHID': None, 'dateCreated': 1388609640, 'dateModified': 1417570958, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59191', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Cannot go to the next line of an article after copy-paste of an hiero as the error \"TypeError: outermostNode is null\" appears', 'description': {'raw': \"TypeError\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which contains a hiero\\n2.Copy the hiero\\n3.Open another page in FireFox with VE\\n4.Paste the heiro\\n5.Save the page\\n6.Reopen the page and Press enter to go to the next line after the hiero\\n\\nObserved Result:\\nCannot go to the next line of an article after copy-paste of an hiero.The following error appears in the console:\\n \\nTypeError: outermostNode is null\\n\\n\\t\\n\\n...documentModel,selection.from,'\\\\n');}else{node.traverseUpstream(function(node){if...\\n\\nload.p...4146Z&* (line 261)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12558}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1442271794, 'spacePHID': None, 'dateCreated': 1388272560, 'dateModified': 1442271804, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59092', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:\"TypeError :this.timings is undefined \"appears while attempting to save a page which was open for a while', 'description': {'raw': 'Screenshot of the error\\n\\nI have got this error several times in Betalabs recently,it happens if I keep VE open for a while for a page and then do some more edit and hit the \"Save Page\" button.\\nI was still logged in to the previous session when this error appeared.\\n\\n\"TypeError :this.timings is undefined \"\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12542}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1495794415, 'spacePHID': None, 'dateCreated': 1388267400, 'dateModified': 1496167598, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59090', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Changing the selected content's formatting (heading/paragraph/preformatted) applies to the whole line, not just the selection\", 'description': {'raw': 'Selecting the whole line\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Select a text to apply the paragraph format \"Preformatted\".Select the text in a way so that it selects the whole line.Check the screenshot of selection to better understand.\\n\\n3.Now select the option preformatted from paragraph styling options\\n\\nObserved Result:\\nThe Preformatted option gets applied to the other following text/element even though they are not selected.\\n\\nIf the selection is done such way that it spans multiple empty lines then the preformatted options gets applied to those empty lines too.\\n\\nSee the screenshots attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/28th_december\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12538}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391810383, 'spacePHID': None, 'dateCreated': 1388266140, 'dateModified': 1417570921, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59089', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  List formatting not applied unless there is a blank line between items', 'description': {'raw': \"Intention:\\nTurn a list of seven single-spaced items into a properly formatted list.\\n\\nSteps to Reproduce:\\n1. Start with a page that contains a list of items that do not have blank lines between them.\\n\\n2. Open VisualEditor and select all the items.\\n\\n3. Click the 'list' button.\\n\\nActual Results:  \\nOnly the first item is given list formatting.\\n\\nIf some items are double-spaced and others are not, then double-spaced items are given list formatting, and any items without a blank line above them (except the first item, which always becomes list-formatted) is left as a plain paragraph rather than being formatted as a list item.\\n\\nExpected Results:  \\nAll the items would be given list formatting.\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=587947827&oldid=587947700\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1420909018, 'spacePHID': None, 'dateCreated': 1388168880, 'dateModified': 1420909018, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59001', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:500 (Internal Server Error) appearing while creating a link on betalabs', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the editor for a page\\n2.Create a link\\n\\n\\nObserved Result:\\nThere is no suggestion appearing for the link creation and also in the console the error 500 (Internal Server Error) appearing\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388167898, 'spacePHID': None, 'dateCreated': 1388081580, 'dateModified': 1417570963, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58974', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Edit button not working -  empty /lib folder after downloading VE extension', 'description': {'raw': 'I know this could be my fault, but I checked everything and it looks like it\\'s a bug. Please correct me if I am wrong.\\n\\nWhenever I click the edit button the webpage does nothing. I see from the javascript debugger that the code stops at this line:\\n\\nreturn typeof jQuery !== \"undefined\" && (!e || jQuery.event.triggered !== e.type) ? jQuery.event.dispatch.apply(eventHandle.elem, arguments) : undefined;\\n\\nAny clues?\\n\\nI checked parsoid, tried creating a new settings file with minimal options, upgraded to latest trunk version both core and visualeditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-vj2bbc63joi46qr5a5nq', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389632091, 'spacePHID': None, 'dateCreated': 1388002080, 'dateModified': 1389632091, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58966', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The page alignment of the articles in betalabs is appearing more towards left', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Open a page with editor.\\n2.Add some content and image\\n3.Save the page\\n\\nObserved Result:\\nThe content of the page is appearing more condensed and all the images are no more right aligned.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12290}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1439321255, 'spacePHID': None, 'dateCreated': 1387918680, 'dateModified': 1442284727, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58947', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Betalabs is not loading properly in Chrome 26.0.1410.65', 'description': {'raw': 'screenshot\\n\\nI was trying to open some page on betalabs , it appears that none of the resources are loading properly.\\n\\nGetting some errors like following while attempting to login:\\nFailed to load resource https://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=…m%7Cskins.common.interface%7Cskins.vector.styles&only=styles&skin=vector&*\\nFailed to load resource https://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*\\nFailed to load resource https://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*\\nFailed to load resource https://upload.beta.wmflabs.org/wikipedia/en/b/bc/Wiki.png\\nFailed to load resource https://bits.beta.wmflabs.org/static-master/skins/vector/images/search-ltr.png?303-4\\nFailed to load resource https://bits.beta.wmflabs.org/images/wikimedia-button.png\\nFailed to load resource https://bits.beta.wmflabs.org/static-master/skins/common/images/poweredby_mediawiki_88x31.png\\n\\nPlease see the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12273}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390025257, 'spacePHID': None, 'dateCreated': 1387905720, 'dateModified': 1417570958, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58938', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Clicking on parameters in the reference dialog box selects the wrong parameter', 'description': {'raw': 'Intention:\\nAdd a citation template\\n\\nSteps to Reproduce:\\n1. Choose Insert > Reference\\n\\n2. Choose Insert > Transclusion\\n\\n3. Type \"Cite web\" into the box. Hit return twice.\\n\\n4. Click \"URL access date\" to add that parameter to the list. Cursor jumped back to \"Add parameter\" (not unreasonable; you might want to add lots of parameters before filling any of them in).\\n\\n5. Click \"URL access date\", which is now the first item in the left-hand column\\'s list of parameters, so I can add today\\'s date to my reference. Cursor jumped back to \"Add parameter\" (definitely unreasonable).\\n\\n6. Repeat that step as many times as you feel like.\\n\\n7. Give up and click on the second parameter, which is \"Source title\". Cursor jumped to the parameter box for \"URL access date\".\\n\\n8. Click on the third parameter in the list, which is \"URL\". Cursor jumped to the parameter box for \"Source title\". The only way to fill in any information for the last parameter in the list is to scroll down the list in the right-hand column.\\n\\n9. Read the article on [[:en:Fencepost error]].  \\n\\n\\n\\nExpected Results:  \\nThat clicking on the second parameter would actually take me to the second parameter, not to the first one.\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390023047, 'spacePHID': None, 'dateCreated': 1387846800, 'dateModified': 1417570959, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58924', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:After deleting a reference list along with reference, the order of the first reference does not get deleted in FireFox 25', 'description': {'raw': 'Selecting the reference with reference list\\n\\nSteps to reproduce:\\n\\n1.Open a page which has reference and reference list with VE on FireFox25\\n2.Select the reference and the reference list and press delete\\n3.Save the page\\n\\nObserved Result:\\n\\nIn Edit mode the order (1.) remains in the page.However, in the read mode the order will not appear.In edit source mode , there is a # appearing.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/The_title\\n\\nThe wikitext of the page before deleting:\\nreference<ref>refererence</ref>\\n<references />\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12253}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1589143295, 'spacePHID': None, 'dateCreated': 1387839660, 'dateModified': 1589143295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58921', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: A lock icon is appearing in all references for a reference list in Firefox in test2', 'description': {'raw': 'screenshot of the lock icon appearing\\n\\nSteps to reproduce:\\n\\n1.Open the editor for a page which contains some references and a reference list\\n\\n2.Copy the references and the reference list and paste into anothe rVE\\n\\n3.Save the page\\n\\nObserved Result:\\n\\nA lock icon is appearing beside the reference for a reference list in FireFox in test2 \\nPage:https://test2.wikipedia.org/wiki/23rdtemplatepaste\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12241}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401472953, 'spacePHID': None, 'dateCreated': 1387833720, 'dateModified': 1417570820, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58917', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Cannot create a new page using VE on FireFox25 in test2', 'description': {'raw': 'the screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Open the editor for a existing VE\\n2.Create a link to a new page\\n3.Click on the link to open that new page in the same or a new tab\\n4.Click on the Create button\\n\\nObserved Result:\\n\\nVe does not load,An error is shown on the console:\\nTypeError: list[firingIndex] is undefined\\n\\t\\n\\n....split(core_rspace),function(_,flag){object[flag]=true;});return object;}jQuery....\\n\\nload.p...025514Z (line 12)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12227}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406320634, 'spacePHID': None, 'dateCreated': 1387830960, 'dateModified': 1417570768, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58912', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Image is appearing as link after copy paste from another VE in FireFox', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the Editor for a page which contains an image with FireFox\\n\\n2.Copy the image and paste it into another VE\\n\\n3.Save the page.\\n\\nObserved Result:\\nAfter copy paste before saving it appears as an uneditable object in VE .After saving the image appears as a link in the page as follows:\\n\\nIn read mode and Edit mode: \\n\\nlink=https://test2.wikipedia.org/wiki/File:158869_at_Truro.JPG|200x200px\\n\\nIn Edit Source mode:[[undefined|link=https://test2.wikipedia.org/wiki/File:158869_at_Truro.JPG|200x200px]]\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also:**\\n{T78026}\\n\\n**Attached**: {F12212}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1426872997, 'spacePHID': None, 'dateCreated': 1387825020, 'dateModified': 1438734976, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58905', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Edit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>', 'description': {'raw': 'In http://en.wikipedia.beta.wmflabs.org/\\nEdit Source and Edit button is appearing as <visualeditor-ca-editsource> and Edit<visualeditor-beta-appendix>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387841449, 'spacePHID': None, 'dateCreated': 1387819560, 'dateModified': 1417570964, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58899', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support <code> elements for text styling.', 'description': {'raw': 'Support adding and removing <code> elements.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394480631, 'spacePHID': None, 'dateCreated': 1387581000, 'dateModified': 1417570931, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58775', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow L10n-bot to merge in several Gerrit repos', 'description': {'raw': \"I tried to give L10n-bot the correct access rights, but failed; I've removed my attempts again. Please give L10n-bot the rights at URL so that it can merge its own submits, like in MediaWiki repos.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**URL**: https://gerrit.wikimedia.org/r/#/admin/projects/wikimedia/wikimania-scholarships,access\"}, 'authorPHID': 'PHID-USER-w5a723w3wes6jd5wskgg', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391529275, 'spacePHID': None, 'dateCreated': 1387579080, 'dateModified': 1391531703, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58769', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Math functions are getting overlapped with previous line', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the editor for a page\\n2.Add a text or a link or a numbered list\\n3.Copy a math formula from another VE\\n4.Paste it into the next line after step 2\\n5.Save the page\\n\\nObserved Result:\\nThe math formula is  getting merged with the previous element\\n\\nPlease check :http://en.wikipedia.beta.wmflabs.org/wiki/Mathpaste20th\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12767}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389047494, 'spacePHID': None, 'dateCreated': 1387576980, 'dateModified': 1417570963, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58765', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The numbered list does not get reordered properly after deleting the first item of the list creating a difference in Edit mode and Read mode', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the editor\\n2.Create a numbered list with 4 items.For example:\\n# item 1\\n# item 2\\n# item 3\\n# item 4\\n\\n3.Now place the cursor at the end of item 2 and press enter\\n4.Add a new item 3( it gets added properly)\\n5.Now place the cursor just before item 1 and press enter to move it to the next line \\n6.Type a new item1 in first line\\n7.Delete the new item\\n\\nObserved Result:\\n\\nThe order  (1.) does not get deleted.In read mode the list appears like this:\\n \\n 1.\\n 2. item 1\\n 3. item 2\\n 4. new item 3\\n 5. new item 4\\n 6. item 3\\n 7. item 4 \\n\\nAfter saving, in read mode the list appears as follows:\\n\\n1.item 1\\n2.item 2\\n3.new item 3\\n4.new item 4\\n5.item 3\\n6.item 4\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394504624, 'spacePHID': None, 'dateCreated': 1387567980, 'dateModified': 1417570928, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58757', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Investigate \"No data received\" errors from VE Chrome tests running via SauceLabs', 'description': {'raw': '**Author:** `jhall`\\n\\n**Description:**\\nWhen it is feeling uncooperative, SauceLabs will report test results like this from a Chrome/Linux test of some or other aspect of Visual Editor:\\n\\nhttps://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/222/testReport/(root)/VisualEditor%20general%20text%20markup%20features/VisualEditor_general_markup__outline_example_____Underline____u_This_is_a_new_line__u____/\\n\\nThe browser response at the time of the failure was this helpful message:\\n\\nhttps://saucelabs.com/jobs/58b6d51fe48b4eaf845939c1f3d6de20/0005screenshot.png\\n\\nThe Selenium log captured by SauceLabs reports:\\n\\n[22.414][FINE]:     Command received (/session/7a6fd70f2bc2c63555f62ec29cc9d507/element) with params {\\n   \"using\": \"xpath\",\\n   \"value\": \".//span[contains(concat(\\' \\', @class, \\' \\'), \\' oo-ui-iconedElement-icon oo-ui-icon-text-style \\')]\"\\n}\\n\\n[22.414][FINER]:    Waiting for all views to stop loading...\\n[22.414][FINER]:    Done waiting for all views to stop loading\\n[22.447][FINER]:    Waiting for all views to stop loading...\\n[22.447][FINER]:    Done waiting for all views to stop loading\\n[22.447][WARNING]:  Command finished (/session/7a6fd70f2bc2c63555f62ec29cc9d507/element) with response {\\n   \"sessionId\": \"7a6fd70f2bc2c63555f62ec29cc9d507\",\\n   \"status\": 7,\\n   \"value\": {\\n      \"message\": \"The element could not be found\"\\n   }\\n}\\n\\n…while the Sauce Log records several HTTP 500 conditions similar to this (I will attach the complete Sauce Log to this bug):\\n\\n    {\\n        \"HTTPStatus\": 500, \\n        \"between_commands\": 0.0773019790649414, \\n        \"duration\": 0.036900997161865234, \\n        \"in_video_timeline\": 19.80928897857666, \\n        \"method\": \"POST\", \\n        \"path\": \"element\", \\n        \"request\": {\\n            \"using\": \"xpath\", \\n            \"value\": \".//span[contains(concat(\\' \\', @class, \\' \\'), \\' oo-ui-iconedElement-icon oo-ui-icon-text-style \\')]\"\\n        }, \\n        \"result\": {\\n            \"message\": \"The element could not be found\"\\n        }, \\n        \"screenshot\": null, \\n        \"statusCode\": 7\\n    },\\n\\nNeed to investigate and figure out what is going on here...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401746056, 'spacePHID': None, 'dateCreated': 1387566480, 'dateModified': 1401746056, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58756', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference dialog retains style of copy/pasted contents', 'description': {'raw': 'On fr.wp,\\nNemesisIII usually copy/pastes titles of articles in the reference dialog.\\nThis led to this diff, https://fr.wikipedia.org/w/index.php?title=France_Roche&diff=prev&oldid=99244364, where the newly added link is among equal signs, as if its style was \"Page title\" rather than \"Paragraph\".\\n\\nWhen I tried to replicate this behavior,\\nI got a slightly different result https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve&diff=99382715&oldid=99382337.\\nReference #2 is now... definitely different from the others (waaay bigger), and certainly not standard as it should be.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1429553631, 'spacePHID': None, 'dateCreated': 1387465680, 'dateModified': 1590761059, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58689', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Adding a heading after hiero includes the <hiero> tags within the heading showing inconsistent heading format on Read mode', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the editor\\n2.Add a Hieroglyphic\\n3.When the cursor moves to the next line , add a heading and save the page\\n\\nObserved Result:\\nThe heading bar appears above the hiero where as the section edit options appear where the text of heading appears.The text styling for the heading changes to paragraph format.\\n\\nThe wikitext resulting from these actions is:\\n== <hiero>A\\n</hiero>heading following hiero ==\\n\\nFound in:http://en.wikipedia.beta.wmflabs.org/wiki/Nonexist\\nTest Environment: betalabs\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-cbjanejnwkkrbnj77d2d', 'dateClosed': 1568144619, 'spacePHID': None, 'dateCreated': 1387400760, 'dateModified': 1568144619, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58667', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Support x-method of entering special characters for Esperanto', 'description': {'raw': 'Esperanto commonly uses some special characters.  The \"x-method\" of entering them (cx -> ĉ, gx -> ĝ, hx -> ĥ, jx -> ĵ, sx -> ŝ, ux -> ŭ (and the capital letters)) is already implemented in the Universal Language Selector and other MediaWiki software at https://doc.wikimedia.org/mediawiki-core/master/php/html/LanguageEo_8php_source.html launguages/classes/LanguageEO.php  \\n\\nVisualEditor should support the same method.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389025443, 'spacePHID': None, 'dateCreated': 1387394340, 'dateModified': 1425554489, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58662', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Italic text should not contain trailing spaces', 'description': {'raw': \"In VisualEditor, enter\\n\\n   one[space][Ctrl-I]two[space][Ctrl-I]three\\n\\nThis will result in wiki text \\n\\n   one ''two ''three\\n\\nbut clearly\\n\\n   one ''two'' three\\n\\nwas intended. I don't think a trailing (or leading?) space in italic/bold wikitext is ever appropriate.\\n\\nThe fixed Bug 33108 is similar but deals with selected text.\\n\\n<editorial>\\nI believe some of the hostility towards VE in the Wikipedia community results from issues like this: editors with long watchlists feel they have to clean up after many such VE edits.\\n</editorial>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394501799, 'spacePHID': None, 'dateCreated': 1387321380, 'dateModified': 1394501799, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58605', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add \"BetaFeatures feature\" component to \"MediaWiki extensions\" Bugzilla product', 'description': {'raw': \"Right now we've a BetaFeatures component – https://bugzilla.wikimedia.org/buglist.cgi?component=BetaFeatures&product=MediaWiki%20extensions&list_id=259910 – but no single place to put bug reports about features that use BetaFeatures.\\n\\nSome of these have components of their own (e.g. MediaViewer) or even products (e.g. VisualEditor), but others don't (and probably won't).\\n\\nRight now, there's nowhere to raise a bug about e.g. Typography refresh that won't muddy up the bugs about BetaFeatures itself, as opposed to things that use it.\\n\\nSuggestions on better naming welcome. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387318880, 'spacePHID': None, 'dateCreated': 1387317120, 'dateModified': 1387386327, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58599', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: can\\'t submit/press \"save page\" button using return key', 'description': {'raw': 'When I tab through the various input controls and highlight the \"save page\" button in VisualEditor, I can\\'t seem to use the return key to submit the form/press the button. I\\'ll upload a screenshot momentarily.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396380391, 'spacePHID': None, 'dateCreated': 1387246920, 'dateModified': 1396380391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58564', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: copying and pasting header results in non-breaking space being inserted', 'description': {'raw': 'Input text ([[mw:VisualEditor:What A]]):\\n\\n---\\n=== test ===\\nwhat is \\'\\'\\'this\\'\\'\\' i don\\'t \\'\\'even\\'\\'\\n---\\n\\nI copy and paste this text from [[mw:VisualEditor:What A]] to [[mw:VisualEditor:What B]] and I end up with largely the same result, except an invisible non-breaking space is inserted before \"test\". If you view the HTML page source of [[mw:VisualEditor:What B]], it\\'s trivial to spot:\\n\\n---\\n<span class=\"mw-headline\" id=\".C2.A0test\">&#160;test</span>\\n---\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1421791391, 'spacePHID': None, 'dateCreated': 1387246800, 'dateModified': 1438734976, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58563', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: link inspector appears next to page title, pointing to what is an uneditable area of the page', 'description': {'raw': '1. Go to a non-existent page and edit it with VE\\n2. Click to the right of the article title\\n3. Click the link icon on the toolbar\\n\\nThe link inspector appears next to the page title, pointing to what is an uneditable area of the page.\\n\\nLink creation works correctly, despite the incorrect location of the inspector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398733687, 'spacePHID': None, 'dateCreated': 1387190940, 'dateModified': 1441912052, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58528', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Adding diatrics to letters in defaultsort causes VisualEditor to belive the page was not changed.', 'description': {'raw': 'I ran into an issue with VisualEditor, when I tried to replace an letter with an diatric letter in defaultsort. VisualEditor would not activate the \"Save page\" button, making me unable to save the change. Also, I noticed, that if I would add some random letters to the page, after the defaultsort change, VisualEditor would still not activate the \"Save page\" button.\\n\\nHere is one of three nearly indentical tests where I found this issue. The other two where to test whether the bug was reproducable.\\n# Change [[:is:Flokkur:Stjórnmál í Sádí-Arabíu]]\\n# Open the More settings panel, and choose Page settings.\\n# Sort the page as \"Sádí-Arabíu\" (without the hyphens).\\n# Click apply changes\\n# Notice that the \"Save page\" button does not activate.\\n\\nExpected behaviour: Should allow me to save the page, when changing an letter to an diatric letter. Adding text afterwards definatly should allow me to save the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zrsacwdcrbgp2u32d5pr', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388782680, 'spacePHID': None, 'dateCreated': 1387060200, 'dateModified': 1456526127, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58494', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Cursor misplaced while editing.  I click here, and it types over there.', 'description': {'raw': 'Intention:\\nCopyedit a sentence.  I clicked after the word \"elbow\" to add another phrase.\\n\\n\\nActual Results:  \\nIt typed my words in the middle of a sentence four lines lower.  The diff was correct, but did not include several of the last changes I made (e.g., adding paragraph breaks).  Also, in cutting and pasting another paragraph, the ref\\'s contents were removed.\\n\\n\\nReproducible: Didn\\'t try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1429551469, 'spacePHID': None, 'dateCreated': 1387058460, 'dateModified': 1438740891, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58493', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Edit\" tab not change to \"View source\" with protected template subpage', 'description': {'raw': '\"Edit\" tab not change to \"Vew source\" with protected template subpage, see https://commons.wikimedia.org/wiki/Template:Delete/layout\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://commons.wikimedia.org/wiki/Template:Delete/layout'}, 'authorPHID': 'PHID-USER-b27lopawgf2h6utuuqyi', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386959666, 'spacePHID': None, 'dateCreated': 1386959040, 'dateModified': 1387194211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying a template from one page to another: render is correct, but template is gone.', 'description': {'raw': 'Let\\'s copy the relatively simple {{irc}} template from \\n\\nhttps://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-12-04\\n\\nto\\n\\nhttps://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-12-18\\n\\n1. Open both pages in Edit mode.\\n\\n2. Copy \"#wikimedia-meetbotconnect\" from one page and paste it in the other.\\n\\nEXPECTED\\n\\nThe template is copied as i to the destination page.\\n\\nACTUALLY\\n\\nIf selecting only the text generated by the template, Ctrl-C seems to be not enough. Ctrl-V in the other page will still paste whatever you hadd in your clipboard before.\\n\\nIf selecting the text of the template plus some extra text, then Ctrl-C does copy something, and Ctrl-V does paste a visually equivalent text.\\n\\nHowever, when checking the wikitext source of the page one can see that the original template has been rendered as HTML.\\n\\nSee https://www.mediawiki.org/w/index.php?title=Architecture_meetings%2FRFC_review_2013-12-18&diff=841813&oldid=838192\\n\\nIf this is part of a secret, long-term Parsoid plan to convert all template instances to HTML, fine. However, if this is not the intended behavior...  ;)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415246826, 'spacePHID': None, 'dateCreated': 1386889980, 'dateModified': 1417570671, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58419', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'browsertests: triggers for Flow', 'description': {'raw': 'The browser tests for Flow should be triggered by Gerrit just like it\\nis already the case for ULS (bug 52120) or going to be for VisualEditor (bug 53691).\\n\\nThe tests need to be carefully filtered out since they are expecting content or\\nbehavior which are not to be found on a freshly installed wiki.\\n\\nCC QA\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408458857, 'spacePHID': None, 'dateCreated': 1386869640, 'dateModified': 1408458857, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58401', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'AccessDeniedError: Your wiki requires a logged-in account to access the API.', 'description': {'raw': \"**Author:** `littlesandra88`\\n\\n**Description:**\\nFor private wiki's that requires login\\n\\n$wgGroupPermissions['*']['createaccount'] = false;\\n$wgGroupPermissions['*']['edit'] = false;\\n$wgGroupPermissions['*']['read'] = false;\\n\\nI get this from nodejs\\n\\nStack trace: AccessDeniedError: Your wiki requires a logged-in account to access the API.\\n\\nwhen I do\\n\\nlynx  http://localhost:8000/localhost/x\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397847902, 'spacePHID': None, 'dateCreated': 1386867540, 'dateModified': 1397865528, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58398', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying a section throws undefined error', 'description': {'raw': \"Safari 7:\\n\\nhttps://www.mediawiki.org/wiki/Communication?veaction=edit\\n\\nCopy from under H1, including template up to just before the Chat header. I get:\\n[Error] TypeError: 'undefined' is not an object (evaluating 'delete children[i].values[attribute]')\\n\\tremoveAttributeRecursive (load.php, line 20)\\n\\tremoveAttributeRecursive (load.php, line 20)\\n\\tremoveAttributeRecursive (load.php, line 20)\\n\\tremoveAttributeRecursive (load.php, line 20)\\n\\tremoveHtmlAttribute (load.php, line 20)\\n\\tgetClonedElement (load.php, line 202)\\n\\tcloneElements (load.php, line 170)\\n\\tonCopy (load.php, line 292)\\n\\tproxy (load.php, line 10)\\n\\tdispatch (load.php, line 45)\\n\\teventHandle (load.php, line 38)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414452147, 'spacePHID': None, 'dateCreated': 1386842820, 'dateModified': 1417570670, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58384', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting a template throws undefined getModel error', 'description': {'raw': \"[Error] TypeError: 'undefined' is not an object (evaluating '$node.data('view').getModel')\\n\\tgetOffsetFromTextNode (load.php, line 244)\\n\\tgetOffset (load.php, line 244)\\n\\tgetRange (load.php, line 248)\\n\\tpollOnceInternal (load.php, line 319)\\n\\tpollOnce (load.php, line 319)\\n\\tdocumentOnBlur (load.php, line 287)\\n\\tproxy (load.php, line 10)\\n\\tfocus\\n\\tafterPaste (load.php, line 299)\\n\\t(anonymous function) (load.php, line 294)\\n\\tproxy (load.php, line 10)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1439321113, 'spacePHID': None, 'dateCreated': 1386842700, 'dateModified': 1442284717, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58383', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: undefined error during copy', 'description': {'raw': 'I selected all VE content from: \"It is important to make\", up to \"Mediawiki-l mailinglist thread \"mysql5 binary schema\" 25.03.2009\"\\n\\nI could pinpoint it to trying to copying the Header \"scripts\" and the warning template that follows it.\\n\\n[Error] TypeError: \\'undefined\\' is not an object (evaluating \\'delete children[i].values[attribute]\\')\\n\\tremoveAttributeRecursive (load.php, line 20)\\n\\tremoveAttributeRecursive (load.php, line 20)\\n\\tremoveHtmlAttribute (load.php, line 20)\\n\\tgetClonedElement (load.php, line 202)\\n\\tcloneElements (load.php, line 170)\\n\\tonCopy (load.php, line 292)\\n\\tproxy (load.php, line 10)\\n\\tdispatch (load.php, line 45)\\n\\teventHandle (load.php, line 38)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki?veaction=edit'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1428526886, 'spacePHID': None, 'dateCreated': 1386840240, 'dateModified': 1438734981, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58379', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:Inserting image gives error : Uncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function\", 'description': {'raw': \"screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the editor\\n2.Insert an image\\n\\nObserved Result:\\nAn error appears:\\nUncaught TypeError: Property 'jQuery18302923649437725544_1386807070459' of object [object Object] is not a function api.php:1\\n\\nsee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11996}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406740632, 'spacePHID': None, 'dateCreated': 1386807960, 'dateModified': 1417570763, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58364', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Investigate \"Selenium::WebDriver::Error::WebDriverError\" issues with Chrome via SauceLabs', 'description': {'raw': '**Author:** `jhall`\\n\\n**Description:**\\nThis seems to be happening somewhat regularly with Visual Editor jobs run in the \"Linux Firefox\" environment via CloudBees SauceLabs:\\n\\nhttps://wmf.ci.cloudbees.com/view/r-ve/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/203/testReport/(root)/VisualEditor%20Indent,%20Outdent/check_indent_and_outdent_enable_and_disable__outline_example_____Bullets___enabled___disabled___/\\n\\nError message reported from SauceLabs is:\\n\\nunexpected response, code=404, content-type=\"text/plain\"\\nERROR Job 68d1926e89f24b24a35272766e190eb5 is not in progress. It may have recently finished, or experienced an error. You can learn more at https://saucelabs.com/jobs/68d1926e89f24b24a35272766e190eb5 (Selenium::WebDriver::Error::WebDriverError)\\n./features/step_definitions/bullets_steps.rb:34:in `/^I click Bullets$/\\'\\nfeatures/indent_outdent.feature:11:in `When I click <control>\\'\\n\\nLooking at the Selenium log captured via SauceLabs, we may discover:\\n\\n[22.744][FINER]: Waiting for all views to stop loading...\\n559[22.745][FINER]: Done waiting for all views to stop loading\\n560[23.567][FINER]: Waiting for all views to stop loading...\\n561[23.625][FINER]: Done waiting for all views to stop loading\\n562[23.625][WARNING]: AfterExecuteCommand failed: Chrome did not respond to \\'WaitForAllTabsToStopLoading\\'. Elapsed time was 57 ms.\\n563[23.625][FINE]: Command finished (/session/78a6e87ee7f7d38f694da3813857645f/url) with response {\\n564 \"sessionId\": \"78a6e87ee7f7d38f694da3813857645f\",\\n565 \"status\": 0,\\n566 \"value\": {\\n567\\n568 }\\n569}\\n\\nThe same test runs without errors on a local Linux machine with Firefox.  From the Selenium log on SauceLabs, we discover the following configuration info:\\n\\n43[3.622][FINE]: Command received (/session/78a6e87ee7f7d38f694da3813857645f)\\n44[3.622][FINE]: Command finished (/session/78a6e87ee7f7d38f694da3813857645f) with response {\\n45 \"sessionId\": \"78a6e87ee7f7d38f694da3813857645f\",\\n46 \"status\": 0,\\n47 \"value\": {\\n48 \"acceptSslCerts\": false,\\n49 \"applicationCacheEnabled\": false,\\n50 \"browserConnectionEnabled\": false,\\n51 \"browserName\": \"chrome\",\\n52 \"chrome.chromedriverVersion\": \"26.0.1383.0\",\\n53 \"cssSelectorsEnabled\": true,\\n54 \"databaseEnabled\": false,\\n55 \"handlesAlerts\": true,\\n56 \"javascriptEnabled\": true,\\n57 \"locationContextEnabled\": false,\\n58 \"nativeEvents\": true,\\n59 \"platform\": \"linux\",\\n60 \"rotatable\": false,\\n61 \"takesScreenshot\": true,\\n62 \"version\": \"28.0.1500.95\",\\n63 \"webStorageEnabled\": true\\n64 }\\n65}\\n\\nThe \\'WaitForAllTabsToStopLoading\\' issue seems to be a long-resolved issue with chromedriver (see http://code.google.com/p/selenium/issues/detail?id=2996), so why is this still happening when these test run via CloudBees/SauceLabs?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401746563, 'spacePHID': None, 'dateCreated': 1386807660, 'dateModified': 1401746563, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58363', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: IMPLEMENT copy and paste from other VE instances (surfaces)', 'description': {'raw': 'Bug 41193 VisualEditor: Support copy and paste from other VE instances (surfaces) is now closed as FIXED yet a fully working cut and paste is not.\\nSome of the bits of copy and paste still not working are documented at http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=585650020&oldid=585645740\\n\\n#External links? {{Tick}} This seems usually to work (not completely the same, but near enough). Mind you, external links in templates go completely haywire though... \\n#Internal links? {{Cross}} I took one line from [https://www.mediawiki.org/wiki/Manual:FAQ?veaction=edit FAQ], \"where do I donwload MediaWiki?\". One single line, that\\'s all. [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840546] Most other examples below contain further cases of internal links gone wrong\\n#References? {{Cross}} I tried to copy [https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki?veaction=edit] (the whole page), to get a page with a reference (not common on Mediawiki). The result is baffling but amusing[https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840568]. If you go to the reference at the bottom of that page, and click the \"arrow\" at the left (taking you up to the place in the same page where that reference is used, no?) then suddenly you end at the original page, in VE edit mode! \\n#List bullets? {{Cross}} [https://www.mediawiki.org/wiki/Files_and_licenses_concept?veaction=edit], section Display, gives [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840576] Note how multiple lines from the original are squashed together in the copy\\n#Images? {{Cross}} I found an image in [https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design?veaction=edit], section Code, Status: but the result [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840580] has no image, as part of the syntax is lacking...\\n#Templates? {{Cross}} I tried copying the template from [https://www.mediawiki.org/wiki/Communication?veaction=edit here, on the right]: the result is [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840544]. Something simpler? <nowiki>{{Note}}</nowiki> changes into <nowiki><span class=\"\"><span class=\"\"></span></span><span class=\"\"> </span>\\'\\'\\'Note\\'\\'\\'<span class=\"\">:</span></nowiki> [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840555]\\n#Tables? {{Cross}} Taken from [https://www.mediawiki.org/wiki/Manual:Code?veaction=edit], but the result is not quite the same [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840555], not the contents (yuk) nor the layout. \\n#Code? {{Cross}} I tried to copy the code from [https://www.mediawiki.org/wiki/Manual:FAQ?veaction=edit FAQ], section \"How do I add extra namespaces?\", but the result [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840549] is not quite the same as the original, and looking at the actual code underneath makes this even more obvious\\n#Further bugs? {{Cross}}, e.g. the sudden appearance of (actually quite nice) clouds as section headers[https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840559]\\n#Further bugs part 2? {{Cross}} But extremely funny! No idea what happened here, but I tried to copy a section from [https://www.mediawiki.org/wiki/Download?veaction=edit], section \"Development releases\", and nothing more. The amazing result, starting from an empty page, is [https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=840564&oldid=840563]. Don\\'t ask me where that template at the bottom left comes from, I didn\\'t ask for it!\\n#Further bugs part 3? {{Cross}}, again funny, perhaps the same as the one above: From [https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design?veaction=edit] I copy the short sentence <nowiki>see the {{git file|project=mediawiki/core|file=resources/mediawiki.ui/sourcefiles|sourcefiles}} subdirectory.</nowiki> (shown here in wikitext format, but everything here is copied using VE only!), which looks originally like \"see the resources/mediawiki.ui/sourcefiles subdirectory\". The end result of this one sentence? [https://www.mediawiki.org/w/index.php?title=User:Fram/Sandbox&oldid=840587] Don\\'t you love it? \\n#Further bugs part 4? {{Cross}} If I want to copy [https://www.mediawiki.org/wiki/Flow_Portal/Design/FAQ?veaction=edit Flow Portal/Design/FAQ], I can\\'t. I can\\'t paste it into my sandbox, and if I paste it in multiple parts, I can\\'t save it (the save button doesn\\'t work).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386839759, 'spacePHID': None, 'dateCreated': 1386801180, 'dateModified': 1386850954, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58354', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Newline cannot be entered after copy pasting a text from another VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the editor\\n2.Copy a text or a link \\n3.Paste it into another VE\\n4.Press enter\\n\\nObserved Result:\\nNewline cannot be entered in the other VE where the text was pasted into .\\n\\nIt is giving an error :\\n\\nResource interpreted as Font but transferred with MIME type application/font-woff: \"http://bits.beta.wmflabs.org/static-master/extensions/UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.woff?version=20131205\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12813}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386962606, 'spacePHID': None, 'dateCreated': 1386797160, 'dateModified': 1417570964, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58350', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Fatal exception of type MWException', 'description': {'raw': '**Author:** `littlesandra88`\\n\\n**Description:**\\nAfter having upgraded from mw1.19 til mw1.22 I\\n\\ncd extensions\\ngit clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git\\n\\nand added\\n\\nrequire_once \"$IP/extensions/VisualEditor/VisualEditor.php\";\\n$wgDefaultUserOptions[\\'visualeditor-enable\\'] = 1;\\n$wgHiddenPrefs[] = \\'visualeditor-enable\\';\\n\\nto LocalSettings.php as described at\\n\\nhttp://www.mediawiki.org/wiki/Extension:VisualEditor\\n\\nWhen I visit the wiki I get in the browser\\n\\n[da26e58f] 2013-12-11 13:28:05: Fatal exception of type MWException\\n\\nUsing CentOS6 64bit\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386776520, 'spacePHID': None, 'dateCreated': 1386769680, 'dateModified': 1386777909, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58328', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Visual Editor UI should display MediaWiki:Edittools', 'description': {'raw': '**Author:** `William915`\\n\\n**Description:**\\nFor Cantonese Wikipedia, MediaWiki:edittools is quite a useful tool to insert special characters used solely in Cantonese and not in Mandarin. It would be really helpful if it is shown in the interface of VisualEditor as well. I am not sure whether other wikis have similar requests for this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387220238, 'spacePHID': None, 'dateCreated': 1386760620, 'dateModified': 1417570964, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58323', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Error contacting parsoid server error occurring while saving a page on betalabs', 'description': {'raw': 'Screenshot of the error\\n\\nError contacting parsoid server error occurring while saving or editing a page on betalabs\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12611}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395881797, 'spacePHID': None, 'dateCreated': 1386625380, 'dateModified': 1417570923, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58238', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:\"Apply changes\"  on the transclusion dialog box and \"Save Page\" button on the page remains active even though there is no change on the transclusion dialog box', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Open the Editor.\\n2.Open the transclusion dialog.\\n3.Click on the trash icon on the right\\n4.Click on \"Apply Changes\"\\n5.Click on Save Pages\\n6.Click on \"Review your changes\"\\n\\nObserved Result:\\n\\nAlthough there is no change in the template dialog box, the \"Apply changes\" button in the transclusion dialog box remains active.\\nAfter clicking on \"Review your changes\" it says: \\n\"Could not start the review because your revision matches the latest version of this page\"\\n\\nSee the scrrenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12587}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416357284, 'spacePHID': None, 'dateCreated': 1386618540, 'dateModified': 1417570674, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58231', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Using forward-delete key on a PC causes odd cursor placement', 'description': {'raw': \"Steps to Reproduce:\\nFrom Deryck at mw:VisualEditor/Feedback:\\n\\nSuppose I have:\\n\\nA foobar B\\nC foobar D\\nE foobar F\\n== foobarbaz ==\\nfoobar\\n\\n* When I hit delete at B, the paragraph break is removed correctly, but the cursor jumps to the beginning of the previous paragraph (A).\\n* When I hit delete at D, the paragraph break is also removed correctly, but the cursor jumps to or the right-hand side margin of the paragraph before that (to the right of B).\\n* Sometimes the paragraph break is removed, and the first letter of the next paragraph is moved to the beginning of the previous paragraph (can't figure out the conditions of this, only observed it once and can't replicate it).\\n* When I hit delete at F (just before a section header), the section header disappears... this might be the correct behaviour, but sadly hitting Ctrl+Z does not restore the section header.\\n\\n\\n\\n\\nReproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405341696, 'spacePHID': None, 'dateCreated': 1386614340, 'dateModified': 1405341696, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58221', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Attempt to copy/paste some content blocks leads to JavaScript error', 'description': {'raw': 'If I copy from\\nhttps://www.mediawiki.org/w/index.php?title=Wikimedia_Engineering/2013-14_Goals&veaction=edit\\n\\nto https://www.mediawiki.org/w/index.php?title=User:Eloquence/CP_tests&veaction=edit after clearing it\\n\\nand select the first section (from start to \"new opportunities.\" including the navigation template), I get a JavaScript error \\n\\nUncaught TypeError: Cannot call method \\'getType\\' of undefined  \\n\\non the console, and VisualEditor becomes unresponsive.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394489980, 'spacePHID': None, 'dateCreated': 1386573480, 'dateModified': 1394489980, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58199', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Transclusion\" is not a good description for the button which inserts \"templates\"', 'description': {'raw': 'How is a new user supposed to know the meaning of \"Transclusion\"?\\n\\nThis should be replaced by something easier to understand such as \"Template\". It should also be easier to translate....\\n\\nThe term is used on these messages:\\n\\t\\'visualeditor-dialog-transclusion-title\\' => \\'Transclusion\\',\\n\\t\\'visualeditor-dialogbutton-transclusion-tooltip\\' => \\'Transclusion\\',\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393525848, 'spacePHID': None, 'dateCreated': 1386436620, 'dateModified': 1417570951, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58163', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Link inspector UI gets broken pressing Command+K to modify a link right after inserting it.', 'description': {'raw': 'Broken UI 1\\n\\nSteps to reproduce:\\n\\n1.Open the Editor\\n2.Add a text and select it\\n3.Press command+k to add link onto the text\\n4.Again press command+k to modify it\\n \\n\\nObserved Result:\\n\\nThe link inspector UI gets broken \\n\\nSee the screenshots attached\\n\\nTest Environment: betalabs\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/The_link?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12374}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389911909, 'spacePHID': None, 'dateCreated': 1386367440, 'dateModified': 1417570960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58126', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Applying a special character insertion while selecting an image deletes the image', 'description': {'raw': 'Steps to  reproduce:\\n\\n1.Open the editor.\\n2.Select an image\\n3.Open the More>Special Character window\\n\\n\\nObserved Result:\\nThe image gets deleted\\n\\nTest Environment: betalabs\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=6th_december&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395355275, 'spacePHID': None, 'dateCreated': 1386363900, 'dateModified': 1429600915, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58118', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Empty <hiero> tags added & tooltip shown while switching to other window when hiero insertion tool is open', 'description': {'raw': 'Empty hiero tags\\n\\nSteps to reproduce:\\n\\n1.Open the editor\\n2.Open the hiero insertion tool\\n3.Now without closing it open another dialog box for example:Click on Latex/Special Characters/Reference etc.\\n4.Close the second window\\n5.Save the page\\n\\nObserved Result:\\nThe hiero insertion tool is also getting closed after step 4 but if you go to edit source you will see empty hiero tags \\nNow if you log out and press the back button on the browser and try editing the page as anonymous user , there are yellow bordered boxes saying \"Sorry this element can only be edited in source mode now\", on the positions where empty hiero tags are added\\n\\nSee the screenshots attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12355}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1590839983, 'spacePHID': None, 'dateCreated': 1386361620, 'dateModified': 1590839983, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58115', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The special character insertion tool does not open up if the cursor is placed after a link', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the Editor\\n2.Add a link\\n3.Place the cursor just after that link position\\n4.Go to More>Special Characters\\n\\nObserved Result:\\nThe special character insertion tool does not open up\\n\\nSee the screenshot attached\\n\\nTest Environment: betalabs\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=6th_december&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12351}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389825901, 'spacePHID': None, 'dateCreated': 1386359820, 'dateModified': 1417570962, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58113', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add more VisualEditor tests via CloudBees jobs for OSes beyond Linux', 'description': {'raw': '**Author:** `jhall`\\n\\n**Description:**\\nPer a request from James F, we should start to expand the selection of environments (OS and browser combinations) that Visual Editor automated tests run via CloudBees.  \\n\\nFor example, add a \"Internet Explorer 10 on Windows 8\" test, and related variations that CloudBees/SauceLabs can accommodate.\\n\\nPer Chris M, a good way to get started is to copy the existing \"Selenium\" template in CloudBees and figure out what we need to do to add Windows into the mix.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403988718, 'spacePHID': None, 'dateCreated': 1386357000, 'dateModified': 1403988718, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58110', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Multimedia Viewer: Keyboard shortcut to activate MV active inside VisualEditor', 'description': {'raw': \"When ve-activated class is set on the body, it would be lovely to deactivate this feature as it's rather irritating. Think it's Shift+cursor or Ctrl+Shift+cursor or something similar?\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386720820, 'spacePHID': None, 'dateCreated': 1386356220, 'dateModified': 1417685599, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58107', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Cite error for no {{reflist}} template shows up,when references are added after the reflist in the article', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Open the Editor\\n2.Add a reference to a line\\n3.Add a references list\\n4.Now add someother lines after the reflist with references\\n5.Save the page\\n\\nObserved Result:\\nThe following error appears where as there is already a reflist.\\n\\nCite error: There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page).\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12198}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1386272940, 'dateModified': 1519832530, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58049', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Pressing shift+Right arrow on a newly created page in VE opens up images/logos from media commons', 'description': {'raw': \"Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Click on Create beta\\n2.Press Shift+Right arrow\\n\\nObserved Result:\\nSome images/logos from media commons opens up with image viewer in VE.\\n\\nSee the screenshot attached.\\n\\nFollowing errors are found:\\nUncaught TypeError: Cannot read property 'pages' of undefined\\nXMLHttpRequest cannot load http://commons.wikimedia.org/w/api.php?action=query&format=json&list=users&ususers=Mike%2Elifeguard&usprop=gender. Origin http://en.wikipedia.beta.wmflabs.org is not allowed by Access-Control-Allow-Origin. /w/index.php?title=Rys&veaction=edit#mediaviewer/File:Wikibooks-logo.svg/1:1\\nUncaught TypeError: Cannot read property 'pages' of undefined\\nXMLHttpRequest cannot load http://commons.wikimedia.org/w/api.php?action=query&format=json&list=users&ususers=-xfi-&usprop=gender. Origin http://en.wikipedia.beta.wmflabs.org is not allowed by Access-Control-Allow-Origin.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12098}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395355311, 'spacePHID': None, 'dateCreated': 1386191040, 'dateModified': 1417570925, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58002', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Experiencing extreme slow response for all actions in VE in Betalabs', 'description': {'raw': 'Currently, while saving a page or when a link insertion too; searches for matching page it is taking longer than usual time in Betalabs.\\n\\nI am not facing it any other environment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386356657, 'spacePHID': None, 'dateCreated': 1386188280, 'dateModified': 1451195451, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'BetaFeatures: All icons must have RTL versions', 'description': {'raw': \"Beta features have icons to represent them at Special:Preferences.\\n\\nThey usually show a schematic representation of a MediaWiki page with a logo in the top left corner, and this of course means that they should be flipped for RTL languages.\\n\\nSome of them are trivial - just a horizontal flip.\\n\\nSome of them are less trivial - for example, in the one for the VisualEditor formula editing I flipped the image and then flipped the Sigma icon inside it so it would still look like Σ and not flipped.\\n\\nSome of them are even less trivial, for example the icons for the font style experiments. It shows the Latin letter A, and it's weird to show a Latin letter in the beginning of a right-to-left text. Luckily, there are only two major right-to-left scripts, so I made one icon for Hebrew and one for Arabic.\\n\\nSome relevant sample commits by myself, already merged:\\n* https://gerrit.wikimedia.org/r/#/c/94379/\\n* https://gerrit.wikimedia.org/r/#/c/94269/\\n* https://gerrit.wikimedia.org/r/#/c/94423/\\n\\nOn this commit Jon and Juliusz complained that the image should be re-saved with a smaller size and less metadata:\\n* https://gerrit.wikimedia.org/r/#/c/98159/\\n\\nThe SVGs from the previous merged commits may have to be re-done as well.\\n\\nAny future beta features should have RTL-compatible icons from the start, preferably done by professional designers.\\n\\nSee some more details here:\\nhttps://www.mediawiki.org/wiki/Design_best_practices#Right-to-left_languages\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387320035, 'spacePHID': None, 'dateCreated': 1386162480, 'dateModified': 1387320035, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57979', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: the {{phpi}} template in mediawiki.org is not showing any content while editing in VE', 'description': {'raw': \"Try editing https://www.mediawiki.org/wiki/User:Amire80/phpi in VE.\\n\\nThe template's content doesn't show when editing in VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400009090, 'spacePHID': None, 'dateCreated': 1386151980, 'dateModified': 1417570827, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57966', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Pawns and some other icons are appearing while typing fast on a page on betalabs', 'description': {'raw': 'Screenshot\\n\\nI am getting pawn while typing fast on some pages on betalabs sometimes.\\nIt is not always reproducible.\\nI will update the bug if i find any steps to reproduce.\\n\\nSee the screenshots attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12011}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406598559, 'spacePHID': None, 'dateCreated': 1386113580, 'dateModified': 1417570765, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57953', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Bugzilla should have Flow as a separate Product, not hidden under \"extensions\"', 'description': {'raw': '**Author:** `Wikifram`\\n\\n**Description:**\\nCurrently, bugs about Flow are shelved under Mediawiki extensions, unlike e.g. VisualEditor or less important things like QRpedia. Considering the probable serious influx of Flow bugs in the near future, I would propose that it gets its own \"level\", so that e.g. in the search box it is selectable (I mean that if you select \"search bugs\" on the left side, under \"Product\", you should be able to choose \"Flow\" directly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386069221, 'spacePHID': None, 'dateCreated': 1386068580, 'dateModified': 1386105307, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57917', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Reloading the page in read mode opens up the editor', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit beta button\\n2.Switch to Edit Source\\n3.Switch back to VE\\n4.Click on Cancel\\n5.Reload the page\\n\\n\\nObserved Result:\\nEven after cancelling the edit, in the URL \"&veaction=edit\" still remains appended , therefore after reloading the page, VE opens up.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386035934, 'spacePHID': None, 'dateCreated': 1386028260, 'dateModified': 1417571002, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57902', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Install node-csslint', 'description': {'raw': 'Also, set up initial jobs for projects that already use csslint in their local-dev Gruntfile (oojs-ui and visualeditor at the moment).\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390847427, 'spacePHID': None, 'dateCreated': 1386027300, 'dateModified': 1390847473, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57899', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The Save page seems to continue for indefinite amount of time for a specific case', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button\\n2.Type something on the first line\\n3.Place the cursor at the beginning of the line and insert a template \"Bronze Age\"\\n4.Save the page\\n5.Reopen the editor\\n6.Click on More>Reference and add a reference\\n7.Type something on the CE\\n8.Click on Save Page\\n\\nObserved Result:\\nThe Save page loader continues for indefinite amount of time.\\nThe following errors are found in the developers tool:\\n\\nUncaught TypeError: Cannot call method \\'apply\\' of undefined load.php:2\\nUncaught Error: Unbalanced input passed to document load.php:109\\nUncaught TypeError: Cannot read property \\'keyedNodes\\' of undefined load.php:201\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12768}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1498128539, 'spacePHID': None, 'dateCreated': 1386026340, 'dateModified': 1498301938, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57898', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The link icon appears on the template while attempting to apply a format on the article', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Click on the \"Edit\" button for a page\\n2.Type something with a link on the main page\\n3.Add a template for example:Bronze Age\\n4.Save the page\\n5.Reopen the editor\\n\\nObserved Result:\\n\\n1. Opening the editor selects/highlights the template,but if user attempts to press delete it deletes the first line gets deleted\\n\\n2.If user clicks on the numbered list or bullet list icon from the toolbar a link icon appears on the template\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12499}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402553504, 'spacePHID': None, 'dateCreated': 1385850960, 'dateModified': 1441912062, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57783', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The format of the text does not change if the cursor is at the end of the text though the options are highlighted in the menu', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Place the cursor at the end of the text or in the beginning or in the middle of a text\\n2.Now select any or all of the options from More>Computer Code/Strikethrough/Underline/Superscript/Subscript\\n\\nObserved Result:\\n\\nObserve that all the options are highlighted in the menu bar but the text format does not change accordingly.If the format of the text is not suppose to change, providing way to disable to the highlight will be better\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12445}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437700683, 'spacePHID': None, 'dateCreated': 1385763600, 'dateModified': 1439425512, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57759', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Deleting an image inside a image settings and reverting it back makes the editor unresponsive', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit button for a page\\n2.Insert a image in the page\\n3.Go to the media settings and add another image as caption\\n4.Save the page\\n5.Reopen the editor .\\n6.Open the image settings and delete the image as caption.\\n7.Undo the action\\n8.Click on the media settings button for the image that is as caption\\n\\nObserved result:\\nA media settings dialog box appears with no content but it cannot be crossed out .Also the \"apply changes\" button does not work therefore editor becomes unresponsive.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414869201, 'spacePHID': None, 'dateCreated': 1385757300, 'dateModified': 1417570680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57756', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Bare URLs of the [http://example.com] format cannot be edited', 'description': {'raw': 'Intention:\\nAdd a label to [http://example.com/]\\n\\nSteps to Reproduce:\\n1. Open the page in VisualEditor\\n2. Click on the link (which displays as \"[1]\")\\n\\n\\nActual Results:  \\nNothing.  It is not possible to edit the link.  If opened manually, the link inspector is empty.\\n\\nExpected Results:  \\n1. That the link icon would display when the link was selected.\\n2. That the link inspector would show the URL.\\n3. That a label could be added (to create [http://example.com Example.com])\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386000770, 'spacePHID': None, 'dateCreated': 1385755140, 'dateModified': 1386000770, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn (\"♙\") appears inside a media item\\'s caption while user is typing in the page', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the edit button for a page where you have some images on the right of the page\\n\\n2.Type something as the first line\\n3.Delete the first line by pressing backspace\\n4.When it deletes the first character of the line ,pressing backspace again still keeps the cursor in the main page\\n5.Now type something\\n\\n\\nObserved Result:\\nThough the cursor is in the main page,a pawn appears inside the caption of the image at the right.\\n\\nA pawn will appear in the main document for the following steps:\\n5. if after step 4 , user presses backspace again \\n6.While the image at the right is highlighted press the Right arrow > from the keyboard\\n7.When the cursor comes to the main article type something\\n\\nA Pawn appears in the main document.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387229504, 'spacePHID': None, 'dateCreated': 1385688600, 'dateModified': 1417048879, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57728', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Clicking on reference does not bring up the reference add dialog for a specific case in production', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the edit button for a page where you have a image on the right of the page which has another image as caption\\n\\n2.Type something as the first line\\n3.Delete the first line by pressing backspace\\n4.When it deletes the first character of the line ,pressing backspace again still keeps the cursor in the main page\\n5.Now add a reference to the empty space,which gets added to the caption of the image at the right.\\n6.Now type something on the second line and add a reference\\n\\nObserved Result:\\n\\nThe dialog box for adding reference does not appear anymore.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1429303505, 'spacePHID': None, 'dateCreated': 1385676300, 'dateModified': 1438734981, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57725', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Pawn (♙) appears in Media Settings when there is another media added in the caption', 'description': {'raw': 'Screenshot of the pawn\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button\\n2.Add an image in the caption of that media.\\n3.Type a text in the caption\\n4.Delete the text by pressing the backspace\\n5.When the cursor reaches the image at the right,Press the right arrow to go back to the initial position of the deleted text.\\n6.Type something again at that position.\\n\\nObserved Result:\\nA Pawn (♙) appears in the Media Setting\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12405}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406598618, 'spacePHID': None, 'dateCreated': 1385673960, 'dateModified': 1417570764, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57722', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Improve link inspector to address usability issues', 'description': {'raw': 'There\\'s currently two user experience issues that I think need to be addressed soon.\\n\\n1. Creating (or, more precisely, inserting) a new link.\\n\\nWhen creating a new link, there is no intuitive way to assign it a label until you decide to close the link inspector at which point the link target text appears as the link label.\\n\\n\\n2. Editing the label of an existing link.\\n\\nWhen editing the label one has to manually ensure all of the link text is selected and replaced. In doing so it is almost impossible not to accidentally delete the link.\\n\\nGiven \"foo <a>bar</a> baz\", selecting \"bar\" manually and typing will replace it with a text node. So essentially the only way to change is to do it in two arbitrary halves.\\n\\nAdditionally, even if selecting and replacing would work, selecting an entire external link (e.g. right after insertion and the url becoming the label) can be quite difficult since URLs tend to contain one or more word-boundaries (that is word-boundaries from the perspective from double-click make-word-selected features that browsers provide).\\n\\n2b. Anti-pattern: Ambiguous focus, unable to overwrite text\\n\\nWhen clicking on the link the \"right\" way, it opens the inspector at which point the entire link label is nicely selected (even if the link spans multiple space-separated words or things like urls that contain word-boundary characters), but it seems hard to retain this selection as any action outside the inspector collapses the selection (maybe impossible, at least I couldn\\'t).\\n\\nThis also makes it hard to fully delete a link. The unlink feature (or clear-formatting) leaves the text. So one would have to carefully make a selection that spans the entire link label and remove that.\\n\\n---\\n\\n\\nNote, there\\'s currently a few open bugs for technical problems (not UX problems) that might require a (whether or not temporary) solution to the above UX issues as they currently happen due to certain actions not being expected by the code. In fixing those, we most likely have to come up with some way to handle this.\\n\\nFor example: (bug  56976) Pawn appears when clicking into the label after creating a link\\n\\nWhen creating a new link and clicking (conceptually \"back\") in the document\\nwhere the cursor was from the link inspector, a pawn appears. This happens because right now links have no label until you close the inspector. So when creating a new link, the cursor position remains empty the entire time. When eventually manually closing the inspector (or clicking anywhere other than the current paragraph) the empty (internal pawn) placeholder label is replaced with the text of the link target.\\n\\nThe immediate fix would be to do the expansion earlier (or even live while the user is working on the link target), however that still leaves a smell of UX issue #2 afterwards.\\n\\n\\n--\\n\\nSummary of issues:\\n\\n* It is impossible to select a link label (selecting it also selects the open/close tag, which means typing over it removes the link). To change a label, one has to enter the new label inside the old (e.g. in the middle of it), and strip away the outer halves of the old label.\\n\\n* It is hard to provide a label for a new link as one has to close the inspector first.\\n\\n* It is hard to delete a link (as an object that is, unlinking text is easy) as one can\\'t focus it. And the auto-selection when opening the inspector always disappears when returning to the document from the inspector.\\n\\nPossible solutions:\\n\\n* Implement a new user interface concept in the content editable surface that would allow a cursor (and selection) to fully cover an annotation whilst not covering the open/close of the annotation. This would enable one to select (and replace) the label of a link.\\n\\n* Add the link label as an additional field to the link inspector.\\n\\n* (or; maybe) turn the link into a focusable node and have it no longer be an annotation. This naturally comes with complications, but may be for the best.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395197341, 'spacePHID': None, 'dateCreated': 1385657880, 'dateModified': 1525457395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57716', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'puppet config of Parsoid localsettings breaks in labs-vagrant', 'description': {'raw': 'Parsoid doesn\\'t work when you add the visualeditor role in Labs-Vagrant setup,\\nclients get 404 errors. After tweaking parsoid to log the actual error (bug 57694), /var/log/upstart/parsoid.log contains\\n\\n  Stack trace: DoesNotExistError: Page Fetch failure for null : Error: Invalid URI\\n  \"undef/w/api.php?format=json&action=query&meta=siteinfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensiontags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols\"\\n\\nObviously undef/w/api.php is going to give 404.\\n\\nThe bad URL path arises because puppet/manifests/roles.pp sets $server_url to \\'undef\\' if forwarded_port isn\\'t set, and it somehow isn\\'t set in labs-vagrant. puppet/modules/mediawiki/templates/parsoid.localsettings.js.erb propagates this to /srv/parsoid/js/api/localsettings.js which contains \\n  parsoidConfig.setInterwiki( \\'localhost\\', \\'undef/w/api.php\\' )\\n\\n(Erik Bernhardson figured all this out!)\\n\\nOne fix is to not set $server_url to undef. Patch coming.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385609666, 'spacePHID': None, 'dateCreated': 1385606640, 'dateModified': 1496862116, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Reflist is appearing as bullet list if while inserting reflist the cursor is at the end of an empty bulleted item', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Click on the \"Edit\" button\\n2.Type a text with reference in the page\\n3.Make it a bulleted list by selecting the option from toolbar.\\n4.Press Enter to entry the second item on the list but leave it blank \\n5.Now click on More>References list to add a reflist to the page\\n6.Save the page\\n\\nObserved Result:\\n\\nThe reflist is appearing as bulleted list\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12350}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437700979, 'spacePHID': None, 'dateCreated': 1385596680, 'dateModified': 1439425517, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57691', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn ♙ appears after deleting the preceding text of a reference icon', 'description': {'raw': 'Screenshot of the pawn\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button\\n2.Add a reference to a text\\n3.Select the reference icon\\n4.Press left arrow key to move the cursor to the left of the icon\\n5.Now delete all of the text on the left of the icon by pressing backspace button\\n\\nObserved Result:\\n\\nA pawn ♙ appears right next to the reference icon.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12224}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406598426, 'spacePHID': None, 'dateCreated': 1385509080, 'dateModified': 1417048870, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57632', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link is not getting added when the clear formatting is used while the link inspector was open', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Create the Edit button\\n2.Select a text\\n3.Open the link inspector\\n4.Click on the clear formatting icon from the toolbar\\n5.While the link inspector is still open select the first matching page\\n6.Apply the link\\n\\nObserved Result:\\nThe link did not get applied.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402550186, 'spacePHID': None, 'dateCreated': 1385488740, 'dateModified': 1441911418, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57604', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference', 'description': {'raw': 'The reference for the main page\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button\\n2.Add a reference to a text\\n3.In the reference dialog add an image\\n4.Also type some text into that reference box (for example \"The content\" in this case.)\\n5.Now select the image\\n6.Go to Media Settings\\n7.Now add a reference to that image\\n8.Type anything for this second reference box\\n9.Apply changes in all three dialog boxes\\n10.Save the changes \\n11.Reopen the editor\\n12.Select the reference [1]\\n13.Open the reference dialog box\\n\\nObserved Result:\\nThe text \"The content\" appears as a template with a highlighted blue box around it.Now click on the [1] reference on the image by going to the media settings of the image.\\nIt opens the same content for the first reference and it keeps on opening the same window as you repeatedly do it for all the reference windows appears.\\n\\nExpected Result:\\nThe reference on the main page and the reference on the image should be different content.But since the reference in image [1] is pointing to the same [1] for the article ,this issue arises.\\n\\nSee the screenshots attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58270\\n\\n**Attached**: {F12091}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1423527563, 'spacePHID': None, 'dateCreated': 1385427060, 'dateModified': 1438734985, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57573', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:When the cursor is in the middle of a text the formatting (Bold/Italic/No format) does not work properly', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit button\\n2. Place the cursor in the middle of a text, for example between u and r of \"cursor\"\\n3.Try different heading format and bullet or numbered list option:all of them work\\n4.But try formatting to Bold/Italic/No format: it does not work but the buttons are selected.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414138312, 'spacePHID': None, 'dateCreated': 1385409600, 'dateModified': 1417570683, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57554', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Attempting to delete a template at the beginning of an article deletes the whole paragraph following it', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the \"Edit\" button for a page in production\\n2.At the beginning of the article place a template\\n3.Write a paragraph following that template.\\n4.Save the page\\n5.Reopen the page in Edit mode\\n\\nObserved Result:\\nThe template gets selected(blue highlight appears) automatically.However the template icon does not appear to edit the template rather a four sided drag icon appears on it.\\nNow if you press the delete button while the template is selected ,the following paragraph gets deleted.Pressing undo does not get it back on the page.User have to cancel this edit session and restart again to by pass the issue.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1432052906, 'spacePHID': None, 'dateCreated': 1385408580, 'dateModified': 1438734986, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57553', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression?] Cursor appears misplaced after hitting Enter twice in a list', 'description': {'raw': 'This is where the cursor shows up in the text\\n\\nMight be related to https://bugzilla.wikimedia.org/show_bug.cgi?id=41064, or not.\\n\\n1. Reach https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=583262564 .\\n2. Put the cursor after the last reference.\\n3. Hit Enter once. A new bullet is correctly added.\\n4. Hit Enter again.\\n\\nPossible outcomes:\\n1) see screenshot: the cursor blinks between two lines, on the word \"cognitive\" (observed in Chrome, Vector/Monobook);\\n2) the cursor is attached to the top right corner of the picture of Emily Deschanel (Firefox, Vector);\\n3) the cursor is nowhere in sight (Firefox, Monobook).\\n\\nNotice that if you repeat the procedure at this point, it will work in Chrome, it will still fail in FF.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows 7\\n**Platform**: PC\\n\\n**Attached**: {F12043}'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395360338, 'spacePHID': None, 'dateCreated': 1385404860, 'dateModified': 1417048876, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57551', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: If a link that doesn't have a pipe is changed, the link target remains\", 'description': {'raw': 'Consider that you have an internal wiki link that doesn\\'t use a pipe, for example \"[[Danzig]]\". If you edit the page in VE and change the text from \"Danzig\" to \"Gdańsk\" without using the link inspector the result will be \"[[Danzig|Gdańsk]]\". See the history of https://en.wikipedia.org/wiki/User:Amire80/links-nopipe .\\n\\nIt is not obvious to the user what is happening - does the target or does it not? The users may want to achieve one result or the other in different cases. My own hunch is that users will more frequently want to change the target as well, although that is just a guess.\\n\\nIf we have a reason to think that one behavior is far more common than the other, then it should be the default. If we are not sure, than some more indication about the target will be useful. The only ways to be sure before saving are to check the diff to open the link inspector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54947'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1424371418, 'spacePHID': None, 'dateCreated': 1385296620, 'dateModified': 1530035374, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57506', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:A Return character appears when a text is followed by <math> code', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Create a page\\n2.Type something\\n3.From the \"Edit Source\" option add the following after the text:\\n<math>\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\n\\n\\n</math>\\n\\n4.Save the page\\n5.Click on Edit-beta again\\n\\n\\nObserved Result:\\nA Return character appears after the text in edit mode\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12681}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415882814, 'spacePHID': None, 'dateCreated': 1385162100, 'dateModified': 1417048866, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57454', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:After adding a reference the cursor jumps to the beginning of the first line of the page', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Create a page with a long content first\\n\\n2.Towards the end add references\\n\\nObserved Result:\\n\\nEvery time user adds a reference it takes him to the beginning of the article making him scroll down all the way down to get to where he was adding a reference\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386805579, 'spacePHID': None, 'dateCreated': 1385149560, 'dateModified': 1417570965, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57438', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: unnamed links can not be edited', 'description': {'raw': 'The two links at the end of the third line are external unnamed links.\\nVE does not allow editing them.\\nThe markup guide for en.wp says these links are \"Only used within article body\\nfor footnotes\", but of course they might be used also outside ns0.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=User:Elitre_%28WMF%29/sandbox&veaction=edit\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57418\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57420'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385489060, 'spacePHID': None, 'dateCreated': 1385123880, 'dateModified': 1385489060, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57419', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:References list does not appear when it follows a table in a page.', 'description': {'raw': 'Go to :https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/table_test\\n\\nSee that in the VE mode and Edit source mode the reference list is showing up but in Read mode there is no reference list.\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437707680, 'spacePHID': None, 'dateCreated': 1385077680, 'dateModified': 1437707680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57385', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:VE renders a table with border=\"0\" as border=\"1\"', 'description': {'raw': 'In read mode\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit source.\\n\\n2. Type the following:\\n\\ntable test title\\n\\n{| border=\"0\"\\n|+ my table\\n\\n|-\\n|first cell \\n|second cell \\n|third cell\\n|-\\n|1\\n|2\\n|3\\n\\n|}\\n\\n3.Save the page\\n4.View the page in read mode\\n5.Open the page in VE mode.\\n\\nObserved Result:\\nThere is not border for the table in read mode but when you open the page in VE mode it renders the table with a border=1.\\n\\nSee he screenshots attached.\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nExample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/table_test\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12479}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385123360, 'spacePHID': None, 'dateCreated': 1385062260, 'dateModified': 1417571003, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57368', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:References resulting from repeated citation cannot be edited in the VE mode  after changing the ref name from :0', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit mode\\n2.Add a reference \\n3.Add the same reference 5 times in that page\\n4.Save the page\\n5.Go to Edit Source\\n\\nObserved Result:\\nI think, due to repeated citation of the same reference with no defined name ,a name with value (:0) is added to the <ref> tags for all the references that is using the same reference\\n\\nBut, if user intends to change the name of the original reference to a more meaningful name for future reference purpose he might do the following steps\\n\\n6. Change the name value from \":0\" to \"bbc\" for the first references\\n7.Close the editor \\n8.Click on Edit now.\\n9.Hover over other references which were using same references\\n\\nObserved Result:\\nA message shows up this reference cannot be edited in the VE ,can only be edited in edit source mode.\\n\\nCan this message be more precise to point where the problem is?For example in the read mode it says \"Invalid <ref> tag; no text was provided for refs named :0\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398114542, 'spacePHID': None, 'dateCreated': 1385059320, 'dateModified': 1417570917, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57364', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enhance hooks.rb in mediawiki-selenium gem to warn when BROWSER_LABEL is undefined', 'description': {'raw': '**Author:** `jhall`\\n\\n**Description:**\\nThis is a follow-up to this recent change to the VisualEditor browser tests:\\n\\nhttps://gerrit.wikimedia.org/r/#/c/96793/\\n\\nSince a user may neglect to explicitly export a value for the BROWSER_LABEL environment variable, it might be a good idea to enhance hooks.rb for the mediawiki-selenium RubyGem to add a warning where that value is undefined.  \\n\\nThe danger is that where the BROWSER_LABEL value is undefined, individual tests will not target the intended wiki pages, since those pages are expected to have the BROWSER_LABEL string included in the page URL.\\n\\nThe hooks.rb file already issues similar warnings for the MEDIAWIKI_USER and MEDIAWIKI_PASSWORD variables in the \"Before(\\'@login\\')\" method:\\n\\nhttps://github.com/wikimedia/mediawiki-selenium/blob/master/lib/mediawiki/selenium/hooks.rb\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393019466, 'spacePHID': None, 'dateCreated': 1385059020, 'dateModified': 1393019466, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57363', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn appears near copy/pasted template', 'description': {'raw': 'This happens in FF (both skins).\\n1. https://fr.wikipedia.org/wiki/Utilisateur:Elitre_%28WMF%29/Prove?veaction=edit\\n2. reach the Sources section.\\n3. copy the (en) template and paste it before \"Franca C\".\\n4. hit space.\\n\\nA pawn appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406598703, 'spacePHID': None, 'dateCreated': 1385049060, 'dateModified': 1417048870, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57358', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression?] VisualEditor: Still get a pawn when select-all->replace in Firefox', 'description': {'raw': \"Intention:\\nI want to blank a page, and add new contents.\\n\\nSteps to Reproduce:\\nSince this does not seem to happen on each page, I'll add the steps I followed to reproduce it.\\n\\n1. VEdit https://it.wikipedia.org/wiki/Utente:Elitre_(WMF)/Sandbox_VE with Firefox and Monobook. \\n2. Right-click, select all, delete.\\n3. Click to re-gain focus.\\n4. Type something. A pawn will appear.\\n5. Review your changes. Notice that not all of the contents were actually deleted after #2. Also notice that some or all of your newly added text might be missing. \\n6. Save the page. Your text (most or all of it) shouldn't be there. What you have are random chunks of old text. And your pawn :)\\n\\n\\n\\nActual Results:  \\nWhile reproducing, the following also occurred to me:\\n1. After blanking, a weird cursor (like an arrow pointing up) appeared at the beginning of the line. After typing for a while, Back Space and the keyboard navigation arrows wouldn't work. \\n2. When VEditing the page created after #6, blanking it and then clicking on a line to make the cursor appear resulted in fragments of words appearing. If I tried to type, I'd also get rapidly multiplying pawns.\\n(All these behaviors are not new to me.)   \\n\\nExpected Results:  \\nI expected the page to be really blank, and pawn-less :)\\n\\nReproducible: Sometimes\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=42404\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399642730, 'spacePHID': None, 'dateCreated': 1385044860, 'dateModified': 1399642730, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57355', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save page button does not work if user includes reflist template while there is already reference list', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the edit button\\n2.Add some content in the page\\n2.Add some references in the page\\n3.Add references list from More>References list.\\n4.Now Go to More>Transclusion\\n5.Add the template reflist\\n6.Click on the \"Save Page\" button\\n\\nObserved Result:\\nThe save page button does not work ,user had to cancel this edit session and re-work again on the editor\\n\\nThere is no js error for this in the console.\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nSample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/reference_list_and_reflist_both?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437707342, 'spacePHID': None, 'dateCreated': 1384989060, 'dateModified': 1439425519, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57326', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Cannot save the content of a page after an idle time on the open editor', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the VE editor for a page.\\n2.Make some edit\\n3.Leave the editor open for a long time (more than an hour)\\n4.Come back after that idle time and click the button \"Save Page\"\\n\\n\\nObserved Result:\\nThe content does not get saved.Shows a js error in the console\\n\\nUncaught TypeError: Cannot read property \\'saveRetries\\' of undefined\\n(anonymous function)\\nfire load.php:12\\nself.fireWith load.php:14\\nself.fire load.php:14\\n(anonymous function)\\nfire load.php:12\\nself.fireWith load.php:14\\ndone load.php:119\\ncallback\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1431646766, 'spacePHID': None, 'dateCreated': 1384970580, 'dateModified': 1438734986, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57314', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The related parameters of templates are missing in test2 and beta environment', 'description': {'raw': 'While testing on production , I found that when I select a specific template all the related parameters show up on the dialog box.\\nHowever, in test 2 and beta I do not see any related parameter to select.\\nCan those parameters be included on these environment, so that the testing can be done on it in these environment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394502019, 'spacePHID': None, 'dateCreated': 1384970040, 'dateModified': 1394502019, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57313', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The reflist of the page disappears after adding a reflist to an image', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Click on the edit button\\n2.Add several references in the page\\n3.Add a template reflist onto it.\\n4.Insert an image\\n5.Go to the Media Settings for that image and add a reference and also add the template reflist to the image\\n6.Save the page\\n\\nObserved Result:\\n\\nThe reflist that was created for the page disappears and the error appears \"Cite error: There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page)\"\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12295}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423675642, 'spacePHID': None, 'dateCreated': 1384913460, 'dateModified': 1423675642, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57277', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'export REUSE_BROWSER for 4 VisualEditor tests in Jenkins builds', 'description': {'raw': \"As of today we have four tests that use the @make_selectable_line and @edit_user_page hooks, and that pass with or without the REUSE_BROWSER env variable.  \\n\\nI suggest we set that env variable REUSE_BROWSER=true for \\n\\nbullets.feature\\nindent_outdent.feature\\nheadings.feature\\ngeneral_markup.feature\\n\\nThis will save a significant amount of time for each of the four VE builds, since the four tests will log in only four times per build instead of a total of twenty-one times without REUSE_BROWSER=true. \\n\\nNote that setting REUSE_BROWSER=true does not affect our ability to analyze test failures.  For example, see the failure messages below for a run of the bullets test: \\n\\n----\\n\\ntimed out after 10 seconds (Watir::Wait::TimeoutError)\\n./features/step_definitions/bullets_steps.rb:26:in `block (2 levels) in <top (required)>'\\n./features/step_definitions/bullets_steps.rb:25:in `/^a \\\\# is added in front of input string in the diff view$/'\\nfeatures/bullets.feature:8:in `Then a <character> is added in front of input string in the diff view'\\n\\ntimed out after 10 seconds (Watir::Wait::TimeoutError)\\n./features/step_definitions/bullets_steps.rb:39:in `block (2 levels) in <top (required)>'\\n./features/step_definitions/bullets_steps.rb:38:in `/^a \\\\* is added in front of input string in the diff view$/'\\nfeatures/bullets.feature:8:in `Then a <character> is added in front of input string in the diff view'\\n\\ntimed out after 10 seconds (Watir::Wait::TimeoutError)\\n./features/step_definitions/bullets_steps.rb:52:in `block (2 levels) in <top (required)>'\\n./features/step_definitions/bullets_steps.rb:51:in `/^a \\\\#\\\\# is added in front of input string in the diff view$/'\\nfeatures/bullets.feature:21:in `Then a <character> is added in front of input string in the diff view'\\n\\ntimed out after 10 seconds (Watir::Wait::TimeoutError)\\n./features/step_definitions/bullets_steps.rb:61:in `block (2 levels) in <top (required)>'\\n./features/step_definitions/bullets_steps.rb:60:in `/^a \\\\*\\\\* is added in front of input string in the diff view$/'\\nfeatures/bullets.feature:21:in `Then a <character> is added in front of input string in the diff view'\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386000360, 'spacePHID': None, 'dateCreated': 1384899720, 'dateModified': 1386000360, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57274', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:\"Cannot open another window while another one is active\" error appears while attempting to save the page after deleting the transclusion \"reflist\"', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Click on the edit button\\n2.Add few references to the page\\n3.Go to more>Transclusion\\n4.Add the template reflist\\n5.Delete this template\\n6.An icon still appears for that template click on it\\n7.When the dialog for that template appears cross it out.\\n8.Click the button \"Save Page\"\\n\\nObserved Result:\\nThe Save page button does not work.User cannot save the edit made so far on the page. It requires to cancel the edit and reopen the editor.\\n\\nThe js error that appears on the console is:\\nUncaught Error: Cannot open another window while another one is active\\n\\nSee the screensshot attached\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nSample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/test_reference?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12289}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393528386, 'spacePHID': None, 'dateCreated': 1384897440, 'dateModified': 1417570951, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57272', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Template \"reflist\" does not get added immediately on the page', 'description': {'raw': 'No indication if there is any reflist added or not\\n\\nSteps to reproduce:\\n\\n1.Click  on the edit button\\n2.Add few references to the page\\n3.Now click on the More>Transclusion\\n4.Select the template \"reflist\" and add it to the page\\n\\nObserved Result:\\nThe reflist template does not get added rather an icon for the template shows up on the page.\\nIf you move your cursor that icon disappears too making user confused whether they have added any reflist or not.\\n\\nSee the screenshots attached.\\n\\nTest Environment: Production\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nSample Page:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/test_reference?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12287}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417480904, 'spacePHID': None, 'dateCreated': 1384895040, 'dateModified': 1417480904, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57271', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The math inspector (Latex) and Hieroglyphics is not opening up properly in test2 and beta', 'description': {'raw': \"Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Click on the edit button\\n2.Select a text or place your cursor in a blank space\\n3.Go to More>Latex/hieroglyphics option\\n\\nObserved Result:\\nNone of the inspectors open up .More over ,in one attempt they opened overlapping with each other and after that I could not close any of them.I had to cancel my editing and reopen the editor to get rid of them\\n\\nIt gives the following script error in the console:\\nUncaught TypeError: Cannot read property '$element' of null\\n\\n\\n\\nsee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12278}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386025050, 'spacePHID': None, 'dateCreated': 1384891380, 'dateModified': 1417571002, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57269', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Quickly switching between Read and Edit tab gives a JS error', 'description': {'raw': \"Steps to reproduce:\\n\\n1.Click the button Edit\\n2.Quickly switch to read tab and again switch back to edit button\\n\\nObserved Result:\\nAn error appears in the console\\nUncaught TypeError: Cannot call method 'getModel' of null load.php:37\\nve.init.mw.ViewPageTarget.updateToolbarSaveButtonState load.php:37\\n(anonymous function) load.php:43\\nfire load.php:12\\nself.fireWith load.php:14\\nself.fire load.php:14\\n(anonymous function)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395360091, 'spacePHID': None, 'dateCreated': 1384887120, 'dateModified': 1417570924, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57267', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Galleries containing refs produce errors, unless the <references /> are displayed within the gallery', 'description': {'raw': 'Intention:\\nEdit a page containing a gallery.  The gallery contains <ref> citations.\\n\\nSteps to Reproduce:\\n1. Open the page in VisualEditor.\\n2. Notice the big red errors inside each gallery that contains a <ref> citation.\\n\\n\\nActual Results:  \\nBig red errors are present at the bottom of each gallery that contains a <ref> citation.  Depending on whether the ref is part of a group, these are the two errors I saw:\\n\\nThere are <ref group=$1> tags on this page, but the references will not show without a {{reflist|group=$1}} template (see the help page).\\n\\nThere are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page).\\n\\n\\nExpected Results:  \\nThat VisualEditor would not produce an error.  (There were proper {{reflist}} templates at the bottom of the page.)\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414857389, 'spacePHID': None, 'dateCreated': 1384817640, 'dateModified': 1414857389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57216', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: opening square brackets can sometimes disappear', 'description': {'raw': \"Trying to type a word in brackets might lead to the disappearing of the opening brackets, no wikitext warning appears and no nowikis are added.\\n\\nHappened to me twice in sandboxes,\\nsee https://test.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/tests&oldid=185158 and https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=62542564&oldid=62363821 ;\\nit didn't happen in https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=582254513&oldid=581339890 and I also don't seem able to get this bug while VEditing ns0.\\nAll tests under Chrome and Vector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53856\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394677011, 'spacePHID': None, 'dateCreated': 1384805580, 'dateModified': 1414156189, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57207', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot save the content in test2 and mediawiki environment (Parsoid Vanish connexions limit too low?)', 'description': {'raw': 'Environment:test 2\\nSamplePage:\\nOS:MAC OS X 10.8.5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384841530, 'spacePHID': None, 'dateCreated': 1384797420, 'dateModified': 1417571004, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57202', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Add the tags to wikitext detection regex to show wikimarkup warning', 'description': {'raw': 'When a tag <ref> is inserted in visual editor it shows a wikitext warning to user but there are few more tags which I think will be good to be added to the wikitext detection regex such as \\n<s>\\n<math>\\n<poem>\\n\\nNone of them triggers wikitext warning right now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384841786, 'spacePHID': None, 'dateCreated': 1384562700, 'dateModified': 1417571018, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57125', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:\"ULS: Unknown language doi. ULS: Unknown language fonipa\" appears upon typing the on the \"Search Box\"', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Load any page on test2\\n2.Take your cursor to the \"Search Box\" and attempt to type something in it.\\n3.Observe Console>Errors from Developer tool\\n\\nObserved Result :\\nULS: Unknown language doi.\\nULS: Unknown language fonipa\\n\\nAppears on this section.\\n\\nNote:The selected language is English in this case\\n\\nNot sure if it is expected or not.Close the bug if it is not an issue. \\n\\nTest Environment:\\nBrowser:Chrome 26.0.1410.65\\nOS:MAC OS 10.8.5\\nTest Page:https://test2.wikipedia.org/wiki/Verify_56274\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384558760, 'spacePHID': None, 'dateCreated': 1384558620, 'dateModified': 1384558760, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57121', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'clean up obsolete VE API dependency', 'description': {'raw': 'AIUI, Flow no longer uses VE\\'s API to convert from/to wikitext/html, it posts API requests to Parsoid\\'s URL if its available.\\n\\nI think this means:\\n* Hooks.php onSetupAfterCache() is obsolete, (and has been since we occupied namespaces?!),\\n* Flow should have its own parameters $wgFlowParsoidURL, $wgFlowParsoidPrefix, $wgFlowParsoidTimeout which in comments can default to the $wgVisualEditor* values.\\n* Clean up obsolete comments in ParsoidUtils.php\\n\\nThis will make it clearer that Flow can work with Parsoid even if the VisualEditor extension isn\\'t installed.\\n\\n(Is the Parsoid extension even required on MediaWiki servers in a cluster arrangement where only one machine runs the Parsoid nodejs service?)  I guess yes in order to \"trigger Parsoid cache updates\".)\\n\\n--------------------------\\n**Version**: master\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384889081, 'spacePHID': None, 'dateCreated': 1384545240, 'dateModified': 1384889081, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57111', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Edit|Edit Source links are appearing on a blank heading', 'description': {'raw': 'edit/edit source option on blank space\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button for a page\\n2.Select the option sub-heading 1 in a blank space\\n3.Click the button \"Save Page\"\\n\\nObserved Result:\\nThe Edit/Edit Source link appears in the blank space\\n\\nBrowser:Chrome\\nPage:Any\\nEnvironment:test 2\\n\\nsee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12697}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1431471684, 'spacePHID': None, 'dateCreated': 1384382100, 'dateModified': 1438734990, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57035', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When changing image type, the type is added to the wikitext instead of replacing the old one', 'description': {'raw': \"This came up while working on the new Media dialog in VisualEditor. When changing a block image type, for instance from 'thumb' to 'frameless', the new type is added onto the wikitext instead of replacing the old type tag.\\n\\nOriginal wikitext:\\n[[File:image.png|thumb|right|caption goes here|466x466px]]\\n\\nAfter changing the type of the image to frameless (including all style changes and type attribute) the resulting post-save wikitext is this:\\n\\n[[File:image.png|thumb|right|caption goes here|466x466px|frameless]]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384299690, 'spacePHID': None, 'dateCreated': 1384290060, 'dateModified': 1384299690, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56957', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Changing image alignment attribute adds the alignment instead of replacing it in wikitext', 'description': {'raw': \"This came up while working on the new media dialog in VisualEditor. When there's a change in an image align attribute, the resulting wikitext adds the new alignment keyword instead of replacing the original.\\n\\nInitial wikitext:\\n[[File:image.png|thumb|right|caption goes here|466x466px]]\\n\\nAfter changing the image to right alignment (removing tright and replacing with tleft, and replacing the align attribute in the image object) -- the resulting wikitext post save is this:\\n\\n[[File:image.png|thumb|right|caption goes here|466x466px|left]]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384299493, 'spacePHID': None, 'dateCreated': 1384289880, 'dateModified': 1384299493, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56956', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template is not deselected when \"clicking out\" of it in certain circumstances', 'description': {'raw': '1. Edit [[mw:Manual:$wgEdititis]] in VE\\n2. Click the \"Language\" template at the bottom, to select it\\n3. Click in the blank space to the right of the word \"places\"\\n\\nNotice that the template is (correctly) deselected.\\n\\n4. Do steps 2 and 3 again\\n\\nThe template is not deselected this time. Even though the cursor is flashing in the right place (implying deselection), any typing will overwrite the template.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393633116, 'spacePHID': None, 'dateCreated': 1384236840, 'dateModified': 1417570949, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56929', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Offer help or descripition for parameters', 'description': {'raw': 'It would be nice to offer informative description of each parameter when filling it, to know what to fill. Some paremetr names, are not clear.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**Whiteboard**: aklapper-moreinfo'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384842688, 'spacePHID': None, 'dateCreated': 1384164660, 'dateModified': 1417571018, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56890', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'on an existing course page \"Create source\" is used instead of \"Edit source\" in the tab at the top', 'description': {'raw': 'On an existing course page \"Create source\" is used instead of \"Edit source\" in the tab at the top of the page. For an example, see https://en.wikipedia.org/wiki/Education_Program:University_of_Michigan/CHEM_540_%28Fall_2013%29\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384096303, 'spacePHID': None, 'dateCreated': 1384017120, 'dateModified': 1396986331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56844', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: JS parse error appears while enabling few gadgets for editors', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Go to Preferences>Gadgets\\n2.Enable few gadgets.I tried enabling all the gadgets under \"improved navigation\" , Interface : Editing and uploads and Interface:Files and Categories\\n\\n3.Now load the editor\\n\\nObserved Result:\\nThe following js error appears:\\n\\nError: JavaScript parse error: Parse error: Illegal token in file \\'MediaWiki:Gadget-popups.js\\' on line 1221 Error {} load.php:145\\nlog load.php:145\\nrunScript load.php:154\\ncheckCssHandles load.php:155\\n(anonymous function) load.php:155\\nfire load.php:12\\nself.fireWith load.php:14\\nself.fire load.php:14\\naddEmbeddedCSS load.php:149\\n(anonymous function)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414625049, 'spacePHID': None, 'dateCreated': 1383945720, 'dateModified': 1414625049, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56806', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Subscript and Superscript applied on same text, making it placed somewhere in the middle of the preceding text', 'description': {'raw': 'Superscript and Subscript\\n\\nSteps to reproduced:\\n\\n1.Click on the \"Edit\" button\\n2.Type a text X\\n3.Now type \"2\" and make it a superscript\\n4.Select the text 2 and make it subscript\\n\\nObserved Result:\\nThe text \"2\" now appears somewhere in the middle of the preceding text X which neither superscript nor subscript.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12152}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384111137, 'spacePHID': None, 'dateCreated': 1383939000, 'dateModified': 1417048883, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56795', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The table of content is not showing up until user adds sub-heading 3', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit button\\n2.Add a Heading to the page\\n3.Now add a sub-heading 1\\n4.Add a sub-heading 2 \\n5.Click on \"Save Page\"\\n\\nObserved Result:\\nThe table of contents does not appear.Now if the user adds sub-heading 3, the table of contents show up.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383936861, 'spacePHID': None, 'dateCreated': 1383936780, 'dateModified': 1417571003, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56791', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wiki markup and weird characters show up in the view mode while applying link to a text with reference', 'description': {'raw': 'Wiki markup and weird text\\n\\nSteps to reproduce:\\n\\n1.Click on the \"Edit\" button\\n2.Type a text and add a reference to it\\n3.Select the text with the reference and apply link to it by clicking on link icon or pressing command+k\\n4.Click on \"Save Page\"\\n\\nObserved Result:\\nSome weird text along with wiki markup shows up in the editor,\\n\\nSee the screenshot attached.\\n\\nPage:Any\\nEnvironment:Betalabs and test 2\\nBrowser:Chrome Version 26.0.1410.65 and firefox 20\\nReproducible :Yes\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12085}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383870381, 'spacePHID': None, 'dateCreated': 1383869820, 'dateModified': 1417048883, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56751', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'White space before \":\" is converted to nonbreaking space unicode char?', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=580632339#Space_between_.22:.22_and_characters_count_increase\\n\\nLooks like this could potentially be the xhtml serializer converting &nbsp; to a nonbreaking space unicode char?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391459179, 'spacePHID': None, 'dateCreated': 1383851100, 'dateModified': 1391459179, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56733', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Drop-down menu in VisualEditor toolbar causes alternating horizontal scroll bars in dropdown and page', 'description': {'raw': \"As seen on mediawiki.org (running 1.23wmf2 (020fe63)) in Firefox 24.\\n\\nWhen editing in VisualEditor, the first time I click on the menu icon, the dropdown is slightly too small and a horizontal scroll bar appears inside the dropdown.\\n\\nThe next time I click on the icon, the dropdown's width can accommodate the text and there is no scrollbar in the dropdown itself, but a horizontal scrollbar appears at the page level to accommodate the dropdown's extra width.\\n\\nThen, rinse and repeat: every other time, there's a scroll bar in the dropdown, and the next one there is one at the bottom of the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402331915, 'spacePHID': None, 'dateCreated': 1383820920, 'dateModified': 1402331915, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56713', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Bugzilla: Set up product for OOJS and OOJS UI', 'description': {'raw': \"OOJS components:\\n\\n- General\\n  The core utilities and unsorted issues.\\n\\n- EventEmitter\\n\\n- Registry\\n  Registries and factories.\\n\\n\\nImport from:\\nhttps://github.com/trevorparscal/oojs/issues\\n\\nOOJS UI components:\\n\\n- General\\n  The base classes (Dialog, Frame, Window etc.) and unsorted issues.\\n\\n- Elements\\n  OO.ui.Element and subclasses.\\n\\n- Layouts\\n  OO.ui.Layout and subclasses.\\n\\n- Tools\\n  OO.ui.Tool, ToolGroup and subclasses.\\n\\n- Widgets\\n  OO.ui.Widget and subclasses.\\n\\nNo existing issue tracker (we'll gradually move over issues from VisualEditor and MediaWiki core as needed).\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384517227, 'spacePHID': None, 'dateCreated': 1383779220, 'dateModified': 1386276878, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56698', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Categories are not being added instantly unless user refreshes the browser', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on te Edit-beta button\\n2.Click on the \"Settings\" button and go to \"Categories\" section\\n3.Add a new category\\n4.Click on the button \"Apply Changes\"\\n5.Now click on \"Save Page\"\\n\\nObserved Result:\\nThe newly added category is not showing up at the end of the page unless user refreshes it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383767137, 'spacePHID': None, 'dateCreated': 1383765060, 'dateModified': 1417048883, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56683', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter', 'description': {'raw': 'The first letter goes to the newline\\n\\nSteps to Reproduce:\\n\\n1.Click on the Edit button in firefox\\n2.Go to More>Reference\\n3.Type something to add as a reference \\n\\nObserved Result:\\nIn firefox, while typing on reference dialog box the first character always goes to the next line and cannot be deleted thereafter \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56274\\n\\n**Attached**: {F12795}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384856051, 'spacePHID': None, 'dateCreated': 1383694380, 'dateModified': 1417048881, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The text is going out of the border of the page for a lengthy content in math inspector', 'description': {'raw': 'Text going out of border\\n\\nSteps to reproduce:\\n\\n1.Click on the \"Edit\" button\\n2.Now from the toolbar click on More>LaTeX\\n3.In the dialog box for LaTeX enter a long equation. For Example:\\n\\n\\n\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\\\frac{-b \\\\pm \\\\sqrt{b^2 - 4ac}}{2a}\\n\\n4.Save the page\\n\\nObserved Result:\\nThe text is going out of the border of the page for a lengthy content in math inspector\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12792}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415882765, 'spacePHID': None, 'dateCreated': 1383692400, 'dateModified': 1417570675, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56637', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The <ref> and <references/> tags are showing up in the view mode [https://gerrit.wikimedia.org/r/#/c/92595]', 'description': {'raw': 'tags on view mode\\n\\nSteps to reproduce:\\n1.Click on the Edit button\\n2.Add a reference to the page\\n3.Add a reference list at the end of the page.\\n5.Click the button \"Save\" button\\n\\n\\n\\nObserved Result:\\nThe <ref> and <reference/> tags are showing up in the view mode\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12783}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383684301, 'spacePHID': None, 'dateCreated': 1383683040, 'dateModified': 1417571019, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56632', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'We need a way to do het-deploy in beta-labs for Parsoid/VisualEditor testing', 'description': {'raw': \"Currently en.wikipedia.beta.wmflabs.org runs master of VisualEditor and a manually-synced version of Parsoid that is the same as production. This is great for testing VE as to whether it's good to deploy into production, and had served us reasonably well so far.\\n\\nWe can't just run Parsoid as master, because (a) Parsoid master is occasionally not compatible with VisualEditor master for days or even weeks at a time as the APIs change, and (b) unless Parsoid is going to be pushed live at the same time as VisualEditor (and split into a het-deploy situation for the cluster's wmfX vs. wmfX+1 deployment) we wouldn't know if VE and Parsoid were truly OK to go out.\\n\\nHowever, bug 56583 showed that we also need to test master (and ideally also current production) of VisualEditor against *master* of Parsoid, in Labs, for automated browser testing and so on before any code goes live.\\n\\nDo we need en.wikipedia.beta.wmflabs.org to have en-Parsoid-master-VE-master.wikipedia.beta.wmflabs.org and en-Parsoid-master-VE-prod.wikipedia.beta.wmflabs.org duplicates? (Eww.)\\n\\nAlso, are there other teams who need their multiple independent components and cross-dependencies? Wikidata, perhaps?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401745964, 'spacePHID': None, 'dateCreated': 1383672540, 'dateModified': 1401746274, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56622', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Interface message visualeditor-mweditmodesource-title is missing in English for 1.23wmf2', 'description': {'raw': 'Noticed on mediawiki.org, in the VisualEditor toolbar, Menu icon, last item: <visualeditor-mweditmodesource-title>. \\n\\nSpecial:Version says mw.o is currently running 1.23wmf2 (88c7b3f).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383821933, 'spacePHID': None, 'dateCreated': 1383655680, 'dateModified': 1383821933, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56616', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Error loading data from server:parsoidserver-http-bad-status:503\" shows while attempting to edit using VE', 'description': {'raw': 'Error message\\n\\nSteps to reproduce:\\nClick on the edit button\\n\\nObserved Result:\\n\"Error loading data from server:parsoidserver-http-bad-status:503\" shows while attempting to edit using VE\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12683}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383598243, 'spacePHID': None, 'dateCreated': 1383598080, 'dateModified': 1417571020, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56584', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Can drag and drop non-editable elements from outside the VE surface area', 'description': {'raw': \"Video made by en user Atethnekos\\n\\nAs illustrated in the attached video, VE's drag and drop function has some odd quirks in Firefox.  One can select items from below the VE surface, such as the MediaWiki logo or the licensing disclaimer text, and drag them into the VE surface.  These items can only be added to the last line of an article.  Items seem to be added as bulleted items, increasing indent with each addition.\\n\\nTested on FF 24 Win 7 with Monobook, duplicated with FF 24 and Mac OS 10.6\\n\\nCould not duplicate using Chrome on the above Mac OS - may be a Firefox issue.\\n\\nDescribed here:https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_12#Moving_links_on_the_page_from_outside_the_VE_surface_into_the_VE_surface\\n\\nAnd here:https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Drag_and_drop_redux\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12668}\"}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403008759, 'spacePHID': None, 'dateCreated': 1383594960, 'dateModified': 1403544337, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56578', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't pre-annotate text for superscript and subscript\", 'description': {'raw': 'All in superscript/subscript format\\n\\nSteps to reproduce:\\n-Type a text x\\n-Select it and make to to superscript\\n-Now type 1 before x (1x) and both the letters are in superscript format\\n-Now type \"/\" between these two letters (1/x) and all three letters are in superscript format\\n-Now keep on typing anything before or after (1/x) all the letters are in superscript format.\\n-Press \"Enter\" to go to new line\\n \\nObserved Result:\\nNow the letter x and all other letters after that are in superscript format\\n\\nExpected Result:\\nUnless selected as superscript/subscript all the texts typed before or after it should be in normal text format.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12661}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394483008, 'spacePHID': None, 'dateCreated': 1383593280, 'dateModified': 1417570931, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56576', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'reasoning about javascript loading and test failures', 'description': {'raw': 'abnormal load.php requests\\n\\nthis is essentially the same problem as shown with UploadWizard in https://bugzilla.wikimedia.org/show_bug.cgi?id=56483\\n\\nWhen run in the Sauce Labs environment, tests for VisualEditor for Chrome display many many calls to ResourceLoader that are not shown in normal operation, nor in a browser test in a local environment.  \\n\\nAt least some of these calls to load.php fail with javascript errors, thus causing VE to fail and the test to fail.  \\n\\nOne recent example is shown at https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/117/testReport/junit/(root)/VisualEditor%20Links/Enter_non_existing_link/\\n\\nHere we see two distinct calls for the same code at ext.echo.alert, the second of which fails, see screen shot.  In detail, the first call succeeds, the second fails:\\n\\n[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.echo.alert%2Cbase%2Cdesktop%2Coverlay&skin=vector&version=20131021T193233Z&*\\n\\n[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.echo.alert%2Cbase%2Cdesktop%2Coverlay&skin=vector&version=20131021T193233Z&*\\nUncaught SyntaxError: Unexpected token ILLEGAL \\n\\nAlso in this particular run of the test find VE loading up code for ArticleFeedback and for Gadget code for DelAutoDropdown.  VE loading gadget code in normal operation has been documented, see screen shot for invisible_iframe\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56483\\n\\n**Attached**: {F12626}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384870912, 'spacePHID': None, 'dateCreated': 1383579480, 'dateModified': 1384870912, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56567', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"messages don't resolve in standalone VisualEditor\", 'description': {'raw': 'Standalone VisualEditor shows all messages as the raw [visualeditor-message] strings in tooltips and in general button strings. \\n\\n\"Format\" dropdown, for example, has \\n[visualedit-rformatdropdown-format-paragraph]\\n[visualedit-rformatdropdown-format-heading2]\\n[visualedit-rformatdropdown-format-heading3]\\netc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383721313, 'spacePHID': None, 'dateCreated': 1383414840, 'dateModified': 1417048667, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56519', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE button is disable on testwiki', 'description': {'raw': 'On test.wikipedia.org I enabled VisualEditor through Beta Features.\\nVisiting a page, display:none is applied to the VE edit button (li#ca-ve-edit). This css is at the header of the page.\\n\\nSince no button is shown, how anyone can use VE?\\nAm I missing something?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-e7gwd3ou5ocdumo42srg', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383392774, 'spacePHID': None, 'dateCreated': 1383382320, 'dateModified': 1394999873, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56510', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: [REGRESSION] content attribute missing from defaultsort tags', 'description': {'raw': 'Before https://gerrit.wikimedia.org/r/#/c/90449 :\\n\\n<meta property=\"mw:PageProp/categorydefaultsort\" content=\"Page, Main\" data-parsoid=\\'{\"src\":\"{{DEFAULTSORT:Page, Main}}\",\"dsr\":[1800,1826,null,null]}\\'/>\\n\\nAfter:\\n\\n<meta property=\"mw:PageProp/categorydefaultsort\" data-parsoid=\\'{\"src\":\"{{DEFAULTSORT:Page, Main}}\",\"a\":{\"content\":null},\"sa\":{\"content\":\"Page, Main\"},\"dsr\":[1800,1826,null,null]}\\'/>\\n\\nThis breaks editing of defaultsort in VisualEditor for obvious reasons, but it also triggers a failure mode in VisualEditor where missing content attributes aren\\'t expected and are normalized to content=\"null\", triggering corruption warnings and changing {{DEFAULTSORT:Foo}} to {{DEFAULTSORT:null}}. I\\'ll fix that in VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383351618, 'spacePHID': None, 'dateCreated': 1383337560, 'dateModified': 1383351618, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56489', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <ooui-toolbar-more> tag is showing up instead of \"More\" text in the toolbar in test2 environment', 'description': {'raw': '<ooui-toolbar-more> tag\\n\\nSteps to reproduce:\\n\\n-Click on the Edit button on a page in test 2 environment\\n-Observe the toolbar\\n\\nObserved Result:\\n\\n<ooui-toolbar-more> tag is showing up instead of \"More\" text in the toolbar in test2 environment\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12443}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384856040, 'spacePHID': None, 'dateCreated': 1383334620, 'dateModified': 1384856040, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56488', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Error:Database query error \" is showing up while attempting to save the content for the first time in test2 environment', 'description': {'raw': '\"Error:Database query error \"\\n\\nSteps to reproduce:\\n-Click on the Edit-beta button\\n-Type anything to made some changes in the CE\\n-Click on the Save button \\n\\nObserved Result:\\n\"Error:Database query error \" is showing up while attempting to save the content for the first time in test2 environment.\\n\\nHowever,attempting to save the content for the second time is saving the content.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12442}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384856027, 'spacePHID': None, 'dateCreated': 1383334260, 'dateModified': 1384856027, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56486', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'reasoning about javascript loading and test failures', 'description': {'raw': \"WIP: \\n\\nI am seeing a number of failures in the Selenium tests when running for Chrome. The failures seem to be caused by many calls to ResourceLoader, many repeated, many seemingly unnecessary, and some of these calls fail.  Other calls to other unexpected sources are also evident, this is just a single example.  \\n\\nEach failed test shows a different set of calls to load.php.  Here is one example:\\n\\nA normal load of UW on beta commons has 2 calls for two jquery things, one for the spinner and one for ULS. See screen shot. \\n\\nBut a failed automated test shows multiple repeated calls for jquery.ui.button. See screen shot. https://saucelabs.com/jobs/8fd3f6a483db46da9c4cfbbdcf7d2449\\n\\nA reference to jquery.ui.button is found only one place in all of the UploadWizard source code, line 473 of UploadWizardHooks.php.  It seem to be a dependency for ext.uploadWizard.campaign\\n\\nWhat causes UploadWizard to make multiple calls for a jquery feature jquery.ui.button that it would not normally need?\\n\\nUnder what circumstances would this happen to a normal user?\\n\\nWhen UW makes these multiple calls, it seems that what is returned from some of those calls is corrupt, possibly truncated, since the errors tend to be 'Uncaught SyntaxError: Unexpected token ILLEGAL' and similar. \\n\\nI think VisualEditor has a similar problem, possibly indicated in https://bugzilla.wikimedia.org/show_bug.cgi?id=55801 (see screen shot there)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56567\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384870964, 'spacePHID': None, 'dateCreated': 1383333720, 'dateModified': 1417692116, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56483', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Show the link to a missing page as a red link as it shows in the dialog', 'description': {'raw': 'Steps to reproduce:\\n-Click on the button Edit-beta\\n-Type a text to insert the link\\n-Click on the link icon from the toolbar or press ctrl+k or command+k\\n-Now select a new page which is not yet created\\n-Save the content\\n\\nExpected Result:\\nThe link to a missing page should be shown as a red link as it shows in the dialog\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383277462, 'spacePHID': None, 'dateCreated': 1383264480, 'dateModified': 1417048879, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56442', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Show suggested links' status with an indicator during auto-suggest\", 'description': {'raw': \"A link status indicator (red link, redirect, etc.)\\nduring autosuggest would be great, as long as it fires asynchronously\\nand the user isn't blocked on actions while it's loading.\\n[Suggested by Erik Moeller]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395359396, 'spacePHID': None, 'dateCreated': 1383256380, 'dateModified': 1417048877, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56435', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'central notice banner has js error, causes bogus test failures', 'description': {'raw': 'URLs such as the following examples appear in several browser tests and cause intermittent test failures in browsers other than Firefox, for example for UploadWizard on beta commons and for AFTv5 on beta enwiki: \\n\\nhttp://bits.beta.wmflabs.org/commons.wikimedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin.clearcookie%7Cext.uls.i18n%2Cime%2Cinit%2Cinterface%2Clanguagenames%2Cpreferences%2Cwebfonts%7Cext.uls.webfonts.repository%7Cjquery.client%2Ccookie%2CdelayedBind%2Ci18n%2CjStorage%2Cjson%2CmwExtension%2Ctipsy%2Culs%2Cwebfonts%7Cjquery.uls.data%2Cgrid%7Cmediawiki.Uri%2Capi%2Cnotify%2Cuser%2Cutil%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cskins.vector.js%7Cwikibase.client.init&skin=vector&version=20131026T061711Z&*\\nview data\\n\\n[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.centralauth.centralautologin%7Cext.uls.i18n%2Cime%2Cinit%2Cinterface%2Clanguagenames%2Cpreferences%2Cwebfonts%7Cext.uls.webfonts.repository%7Cext.visualEditor.viewPageTarget.init%7Cext.wikimediaShopLink.core%7Cjquery.byteLength%2Cclient%2Ccookie%2CdelayedBind%2Ci18n%2CjStorage%2Cjson%2CmwExtension%2Ctipsy%2Culs%2Cwebfonts%7Cjquery.uls.data%2Cgrid%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.language.data%2Cinit%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cskins.vector.js%7Cwikibase.client.init%2Cnolanglinks&skin=vector&version=20131031T104306Z&*\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391375202, 'spacePHID': None, 'dateCreated': 1383230520, 'dateModified': 1391375202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56422', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Two adjacent paragraphs made lists in separate actions are made into two lists, not one list with two items', 'description': {'raw': 'Wrongly ordered list\\n\\nSteps to reproduce:\\n\\n-Click on the \"Edit\" button of the Visual Editor.\\n-Have multiple lines to be listed in a Numbered list.\\nFor Example:\\nItem One\\nItem Two\\n-Now select the first line \"Item One\" and click on the icon of \"Numbered list\" to number this item\\n-Now again select the both lines \"Item One\" and \"Item Two\"\\n-Click on the icon of \"Numbered List\"\\n\\nObserved Result:\\nBoth the lines are now numbered with order 1 like following:\\n\\n1.Item One\\n1.Item Two\\n\\nExpected Result:\\nThe numbered list should maintain the continuous order if selected a previously ordered line like following:\\n\\n1.Item One\\n2.Item Two\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12117}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394504425, 'spacePHID': None, 'dateCreated': 1383079200, 'dateModified': 1417570929, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56342', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Do mass DM round trip testing with Wikipedia content', 'description': {'raw': \"Like, Parsoid's round-trip testing, we should do DM round-trip testing with content from Wikipedia. dirtydiffbot does this to some extent, but it tests the Parsoid output rather than the DM output and it uses the UI, which is hacky. We should have a proper service that just tests the DM HTML output is clean, which requires a test runner for that purpose in VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393640838, 'spacePHID': None, 'dateCreated': 1383070560, 'dateModified': 1417570934, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56330', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Controls stop working when browser window is small', 'description': {'raw': \"click Edit/beta, nothing happens at this size\\n\\nthis seems to manifest in several ways: \\n\\n* 'Edit/beta' link stops working, see screen shot\\n* Indent/outdent buttons disappear, see screen shot\\n* possibly more\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12066}\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404168962, 'spacePHID': None, 'dateCreated': 1383056100, 'dateModified': 1417570772, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56314', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Hitting Enter in a block slug does not create a new line', 'description': {'raw': 'Try to VEdit\\nhttps://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=578251398\\nor\\nhttps://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&oldid=62136875 .\\n\\nPlace your cursor at the bottom of the page.\\n\\nHit Enter.\\n\\nExpected result: a new line is created.\\nActual outcome: nothing happens.\\n\\nPlease note that this works fine if instead you type something, and hit Enter after doing so.\\n\\nIt happens on both FF and Chrome with both Vector or Monobook.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393983083, 'spacePHID': None, 'dateCreated': 1382960700, 'dateModified': 1393983083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56236', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Ruby lint should run after every patch set submission for all repositories that contain Ruby code', 'description': {'raw': 'I do not know how to check if this is already happening or not. This is the list of repositories that currently contain Ruby code:\\n\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/selenium\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/CirrusSearch\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Flow\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/MobileFrontend\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Translate\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/TwnMainPage\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/UniversalLanguageSelector\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/VisualEditor\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Wikibase\\nhttps://gerrit.wikimedia.org/r/#/admin/projects/qa/browsertests\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382708537, 'spacePHID': None, 'dateCreated': 1382704500, 'dateModified': 1382711100, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56156', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Set up Code Climate for all repositories that have Ruby code', 'description': {'raw': 'We have Code Climate set up for several repositories. Set it up for all repositories with Ruby code.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382692747, 'spacePHID': None, 'dateCreated': 1382690400, 'dateModified': 1382692753, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56151', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'qa/browsertests log in twice', 'description': {'raw': 'probably the new ruby gem.  see the video at \\n\\nhttps://wmf.ci.cloudbees.com/job/browsertests-en.wikipedia.beta.wmflabs.org-windows-internet_explorer_10/248/testReport/junit/(root)/Page/Move_existing_page_dialog/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382715751, 'spacePHID': None, 'dateCreated': 1382641860, 'dateModified': 1382730509, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56116', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Fail on trying to target a person with a message', 'description': {'raw': '2013-10-23 - 13:04:35  <marktraceur> !e VisualEditor | Svetlana\\n2013-10-23 - 13:04:36  <wm-bot> Svetlana: https://www.mediawiki.org/wiki/Extension:VisualEditor_%7c_Svetlana\\n\\nIt captured the \" | Svetlana\" part. That\\'s very annoying.\\n\\nThe message is currently https://www.mediawiki.org/wiki/Extension:$wiki_encoded_* - maybe that\\'s wrong?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-ppytiem7rcsbnstfsrvq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382559178, 'spacePHID': None, 'dateCreated': 1382559120, 'dateModified': 1382559178, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56065', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor for the Portal and Book namespaces on enwiki', 'description': {'raw': 'Following on from bug 48430 and bug 56000.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382640853, 'spacePHID': None, 'dateCreated': 1382460120, 'dateModified': 1382640853, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56001', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Please enable VisualEditor in ca.wikipedia.org Viquiprojecte namespace', 'description': {'raw': 'As requested at https://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Ajuda#Editor_visual_a_Viquiprojecte\\n\\nPlease enable VisualEditor in ca.wikipedia.org at the \"Viquiprojecte\" namespace.\\n\\nHaving it enabled in \"Portal\" wold be useful as well.\\n\\nCurrently VE is available also to anonymous users in the Main namespace at ca.wiki. The same behavior can be applied to these other namespaces. Thank you!\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382640836, 'spacePHID': None, 'dateCreated': 1382459760, 'dateModified': 1382724903, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*', 'description': {'raw': \"VE works well-enough for pages that aren't signed, except for ones where the pages rely on fiddly or partial wikitext munging, like the Template and MediaWiki namespaces. Consequently, we should be OK to enable VE in a larger number of namespaces, rather than just NS_MAIN and NS_USER:\\n\\n* NS_FILE\\t\\n* NS_HELP\\t\\n* NS_CATEGORY\\n* wgContentNamespaces generally?\\n\\nPart of the fun are things like the portal namespace which is defined per-wiki.\\n\\nSee also bug 55792 for comments about enabling VE in all namespaces, and why I think that's a bad idea.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382640790, 'spacePHID': None, 'dateCreated': 1382372460, 'dateModified': 1510291532, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55968', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page fragment parsing not interpreting raw citation template inserted into a \"content\" block correctly', 'description': {'raw': 'Intention:  To copy a reference (copied from en.wp\\'s article on [[Vanilla]]), using the \"+\" system within the transclusion editor into another article (Simple English\\'s [[Vanilla]]).\\n\\n\\nExpectation:  That the ref dialog box would display the citation correctly.\\n\\n\\nSteps to reproduce:\\n\\n1)  Click the menu item to insert a reference.\\n\\n2)  Click the transclusion item to insert a template.\\n\\n3)  Click the \"+\" and the \"[ ]\" to insert \\'content\\' rather than individual parameters.\\n\\n4)  Paste in the citation template, copied out of the English Wikipedia.  The citation template entered was:\\n{{cite web | title = FAO\\'s Statistical Database - FAOSTAT | year = 2011 | url = http://faostat3.fao.org}}\\n\\n5)  Click \"Apply changes\".\\n\\n\\nResult:\\n\\nSee https://commons.wikimedia.org/wiki/File:VisualEditor_Oct_2013_ref_dialog_box_with_oddly_formatted_citation_template.png\\n\\nIt should have displayed within the reference dialog box as:\\n\\n\"FAO\\'s Statistical Database - FAOSTAT\". 2011.\\n\\nwith the first part being the link.  Instead, it added a second copy of the URL at the end:\\n\\n\"FAO\\'s Statistical Database - FAOSTAT\". 2011.  http://faostat3.fao.org/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398113380, 'spacePHID': None, 'dateCreated': 1382051580, 'dateModified': 1417570917, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55855', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Customize Jenkins email notifications', 'description': {'raw': 'Could we use the same subject heading for these emails so they grouped\\ninto one thread? e.g. QA Report and move the current subject into the\\nemail body itself?\\n\\nCurrently I am getting lots of mails in the form:\\nBuild failed in Jenkins: MobileFrontend-en.m.wikipedia.org-linux-firefox #97\\n\\nand it is very hard to group and filter them.\\n\\nAs a result I tend to ignore them due to too much noise which is bad :).\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**Whiteboard**: gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks\\n**URL**: https://www.google-melange.com/gci/task/view/google/gci2013/5243150582939648'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-pdlnbp2w5h2rej2hikwj', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389293559, 'spacePHID': None, 'dateCreated': 1381984200, 'dateModified': 1499262344, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55824', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'significant intermittent performance problem in Chrome', 'description': {'raw': 'Seen in Chrome and not Firefox: \\n\\nSometimes initiating a VE session can take on the order of 3X the normal time (or possibly more).  This is a UX issue and also causes significant intermittent browser test failures in Chrome version 30.  Here are 10 runs of a script[*] that times how long it takes to bring up and dismiss the \"Welcome...\" iframe:\\n\\n2.194106\\n2.187554\\n2.222601\\n2.226447\\n2.369503\\n2.182237\\n7.639938 *\\n2.335375\\n2.397571\\n2.271333\\n\\nThis is on a fast connection.  The performance issue is exacerbated on a slow connection.\\n\\nSpeculation as to the root cause: \\n\\n* The \"Welcome...\" iframe is actually the second iframe in the page.  The first, much larger iframe in the page is invisible and is a complete copy of the base VisualEditor UI.  It could be that loading both iframes could cause intermittent performance problems. \\n\\n* (Note that the invisible first iframe on the page not only contains an entire VE UI, but may also contain gadget code like HotCat or ProveIt sourced from other places like bits, see screen shot and Bug 55759.)\\n\\n[*] The meat of the little Ruby timer script is: \\n\\n#CLICK EDIT\\nb.a(:title => /Edit this page with VisualEditor/).when_present.click\\n#SAVE START TIME\\nwelcome_start_time = Time.now\\n#CLICK CLOSE ON THE WELCOME IFRAME WHEN IT BECOMES CLICKABLE\\nb.frame(:index => 1).a(:title => \\'Close\\').when_present.click\\n#SAVE END TIME\\nwelcome_end_time = Time.now\\nwelcome_load_time = welcome_end_time - welcome_start_time\\nputs welcome_load_time.to_s\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383846541, 'spacePHID': None, 'dateCreated': 1381945440, 'dateModified': 1383846541, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55801', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Bogus phpcs failure in VisualEditor', 'description': {'raw': 'https://integration.wikimedia.org/ci/job/mwext-VisualEditor-phpcs-HEAD/1561/console is a bogus failure. The error messages are:\\n\\n14:41:05 FILE: ...orkspace/mwext-VisualEditor-phpcs-HEAD/maintenance/makeStaticLoader.php\\n14:41:05 --------------------------------------------------------------------------------\\n14:41:05 FOUND 2 ERROR(S) AFFECTING 2 LINE(S)\\n14:41:05 --------------------------------------------------------------------------------\\n14:41:05  78 | ERROR | Expected 1 space before \"?\"; 3 found\\n14:41:05     |       | (Squiz.WhiteSpace.OperatorSpacing.SpacingBefore)\\n14:41:05  80 | ERROR | Expected 1 space before \":\"; 3 found\\n14:41:05     |       | (Squiz.WhiteSpace.OperatorSpacing.SpacingBefore)\\n14:41:05 --------------------------------------------------------------------------------\\n\\nThe source code doesn\\'t have 3 spaces before the ?, only a bunch of tabs), but it does have a comment on the preceding line each time. Maybe that\\'s what\\'s confusing phpcs?\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383048850, 'spacePHID': None, 'dateCreated': 1381502640, 'dateModified': 1383048857, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55623', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Edit conflict: Review your changes performs different as Save page', 'description': {'raw': '**Author:** `felix`\\n\\n**Description:**\\n* Edit one section with VE\\n*:Example diff:\\n*:+ VEtext\\n\\n* Provoke edit conflict in another section\\n*:Example diff:\\n*:+ ConflictText\\n\\n* Click \"Review your changes\" in VE\\n\\n* Diff shows\\n** the changes made in VE\\n** the changes of the edit conflict as reverted (!)\\n*:Example diff:\\n*:+ VEtext\\n*:- ConflictText\\n\\n* Click \"Save page\"\\n** Both edits are successfully merged\\n*:Example diff:\\n*:+ VEtext\\n*:+ ConflictText\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55392'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384846589, 'spacePHID': None, 'dateCreated': 1381488000, 'dateModified': 1393690865, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55613', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE edit button shown on talk pages with titles starting with a full stop (period)', 'description': {'raw': 'On talk pages that have titles starting with a full stop (period) such as [[talk:.mp]] and [[it:Discussione:.uk]] the button to launch VE is shown despite not being enabled in that namespace. Clicking on it gives the following error message:\\n\\nError loading data from server: novenamespace: VisualEditor is not enabled in namespace 1. Would you like to retry?\\n\\n(incidentally this message is not translated for it.wp)\\n\\nPossibly this bug has the same cause as bug 55493\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55493'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381286891, 'spacePHID': None, 'dateCreated': 1381282140, 'dateModified': 1417571039, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55494', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Does not load on pages with titles starting with a full stop (period)', 'description': {'raw': 'At least in Firefox 24 on Linux (not tested in other systems) VisualEditor does not load on main namespace pages whose titles begin with a full stop (period). The URL changes and the page reloads but remains in view mode.\\n\\nTested at [[.mp]], [[.uk]], [[.300]] and [[.300 Remington American Magnum]] at en.wp and at the .uk articles at it.wp, de.wp, fr.wp and es.wp\\n\\nThe bug does not manifest in other namespaces, e.g. [[User:Thryduulf/.100]] and [[User:.anaconda]] load correctly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55494'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381286833, 'spacePHID': None, 'dateCreated': 1381281660, 'dateModified': 1417571040, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55493', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: dropdown menus only completely visible at top of page, and disappear lower down page in Vector skin', 'description': {'raw': 'TeamGale reports:\\n\\n\"while I was getting more down to the page, the drop down menus were getting \"shorter\" and sometimes disappear at the very end. I tried it to many pages to see if it was happening everywhere and it does. I don\\'t know exactly how to describe it that\\'s why I took screencaps from the page. All three are from the same page, in different height. See how the drop down menu of \"more\" can be seen entirely at the top of the page and how it gradually disappear as I get closer to the bottom. It\\'s really weird!! The same thing happens when I am trying to add a wiki link in the article\\'s text and to be honest, that\\'s how I notice the gradually disappearing.\"\\n\\nThe screenshot is at [[File:Drop Down Menus.jpg]]\\n\\nI can reproduce this in Firefox 24 on Linux when using the vector skin, but not when using Monobook. \\n\\nTrying to add a link after the end of the first paragraph I get no suggestions when my window is not maximised. Even when it is maximised it has completely disappeared by the end of the page. \\n\\nWhat seems to matter is where the view is, not where the cursor is.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381080286, 'spacePHID': None, 'dateCreated': 1381012260, 'dateModified': 1417571040, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55357', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] mediawiki.Title: jQuery.byteLength undefined', 'description': {'raw': \"Login at http://en.wikipedia.beta.wmflabs.org/ with VE enabled. \\n\\nClick edit on any page to invoke VE.\\n\\nPage reloads, VE is not invoked. \\n\\nJavascript errors: \\n\\nException thrown by ext.visualEditor.viewPageTarget.init: Object function (selector,context){return new jQuery.fn.init(selector,context,rootjQuery);} has no method 'byteLength' load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151\\nTypeError\\n load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151\\nException thrown by ext.gettingstarted.openTask: Object function (selector,context){return new jQuery.fn.init(selector,context,rootjQuery);} has no method 'byteLength' load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151\\nTypeError\\n load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130927T181331Z:151\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380907821, 'spacePHID': None, 'dateCreated': 1380899400, 'dateModified': 1380907821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54977', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [edit source | edit beta] links near page title when already in VE mode', 'description': {'raw': 'User report:\\n<<[...] The new one (for me at least, perhaps it already existed): when I edit a page in Beta (my sandbox, or a main space page), I get next to the page title two pale blue links, \"edit source / edit beta\", which bring me to the section editing for the lead. I don\\'t get these pale links for other sections, only next to the title. I can\\'t remember these being there, and I can\\'t see the use for them (and if they have a use, they would probably be wanted for other sections as well). Fram (talk) 12:01, 4 October 2013 (UTC) >>\\n\\nHe uses FF 24, I can\\'t reproduce but we have a screenshot at \\nhttps://en.wikipedia.org/wiki/File:VE_error_Fram_1.jpg .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381264538, 'spacePHID': None, 'dateCreated': 1380894960, 'dateModified': 1381266111, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54971', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Missing or wrong information in meta_p.wiki table', 'description': {'raw': '```\\n+----------------------+------+------+-------------+-----------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+\\n| dbname               | lang | name | family      | url                               | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |\\n+----------------------+------+------+-------------+-----------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+\\n| bat_smgwiki          | en   | NULL | wikipedia   | http://bat_smg.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n| be_x_oldwiki         | en   | NULL | wikipedia   | http://be_x_old.wikipedia.org     |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n| cbk_zamwiki          | en   | NULL | wikipedia   | http://cbk_zam.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n| centralauth          | en   | NULL | centralauth | NULL                              |    1 | s7.labsdb |         0 |        0 |               0 |                0 |            0 |\\n| fiu_vrowiki          | en   | NULL | wikipedia   | http://fiu_vro.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n| map_bmswiki          | en   | NULL | wikipedia   | http://map_bms.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n| nds_nlwiki           | en   | NULL | wikipedia   | http://nds_nl.wikipedia.org       |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n| roa_rupwiki          | en   | NULL | wikipedia   | http://roa_rup.wikipedia.org      |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n| roa_rupwiktionary    | en   | NULL | wiktionary  | http://roa_rup.wiktionary.org     |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |\\n| roa_tarawiki         | en   | NULL | wikipedia   | http://roa_tara.wikipedia.org     |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n| vewikimedia          | en   | NULL | wikimedia   | http://ve.wikimedia.org           |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |\\n| zh_classicalwiki     | en   | NULL | wikipedia   | http://zh_classical.wikipedia.org |    1 | s3.labsdb |         0 |        0 |               1 |                1 |            1 |\\n| zh_min_nanwiki       | en   | NULL | wikipedia   | http://zh_min_nan.wikipedia.org   |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n| zh_min_nanwikibooks  | en   | NULL | wikibooks   | http://zh_min_nan.wikibooks.org   |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |\\n| zh_min_nanwikiquote  | en   | NULL | wikiquote   | http://zh_min_nan.wikiquote.org   |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |\\n| zh_min_nanwikisource | en   | NULL | wikisource  | http://zh_min_nan.wikisource.org  |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |\\n| zh_min_nanwiktionary | en   | NULL | wiktionary  | http://zh_min_nan.wiktionary.org  |    1 | s3.labsdb |         0 |        0 |               0 |                0 |            0 |\\n| zh_yuewiki           | en   | NULL | wikipedia   | http://zh_yue.wikipedia.org       |    1 | s3.labsdb |         0 |        0 |               0 |                1 |            1 |\\n+----------------------+------+------+-------------+-----------------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+\\n```\\n\\nFor the wikis reported above lang is \\'en\\', name in NULL and URL is wrong (maybe this is the reason for the other missing information). For example isn\\'t http://roa_tara.wikipedia.org but http://roa-tara.wikipedia.org\\n\\nFor all the wikis, \\'size\\' column is always 1. This information can be get from:\\n* site_stats.ss_good_articles table of replica db, or\\n* API /w/api.php?action=query&meta=siteinfo&format=json&siprop=statistics under \"articles\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48626'}, 'authorPHID': 'PHID-USER-6ji4nw2pi3dgjy7tgmhp', 'ownerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vk6mlmacfhx77egryy5i', 'dateClosed': 1424404841, 'spacePHID': None, 'dateCreated': 1380879960, 'dateModified': 1437873075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54962', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Marathi/Devanagari: When using jquery.IME, type a word and press space bar = eliminates typed text immediately Typed content disappear while pressing Spacebar', 'description': {'raw': 'I am using Malayalam Inscript2 IME of ULS for typing in Malayalam Wikipedia. Problem is described here:\\n\\n1. Open an article from ml.wikipedia (for eg. https://ml.wikipedia.org/wiki/%E0%B4%B8%E0%B5%82%E0%B4%AB%E0%B4%BF )\\n2. Edit a section using VE\\n3. Add a new line at the end of the section and type a word using ULS IME\\n4. Press Spacebar, the typed word disappears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Windows 7\\n**Platform**: PC\\n**URL**: http://ml.wikipedia.org'}, 'authorPHID': 'PHID-USER-4jecvpv4h62htut6pxez', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1486157088, 'spacePHID': None, 'dateCreated': 1380877560, 'dateModified': 1486157088, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54960', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Editing refs in image descriptions', 'description': {'raw': \"As demonstrable in the last image inserted in:\\n\\nhttps://de.wikipedia.org/wiki/Tetrahedran\\n\\nrefs inserted in the description of media, here 1), can't be edited. Report:\\n\\nhttps://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=123123395#Einzelnachweise_in_Bildunterschriften\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380844957, 'spacePHID': None, 'dateCreated': 1380842100, 'dateModified': 1417048875, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54949', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Newly inserted templates / transclusions are not floated', 'description': {'raw': 'example of the non-float\\n\\nReproduced on Windows 7 and Mac OSX 10.8.5 — when a new template is added to an article it does not follow float:right. However, on page save and a re-entry of the VE it is properly floated.\\n\\nSee the attached screenshot. This really breaks the WYSIWYG nature of the VisualEditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12578}'}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380746310, 'spacePHID': None, 'dateCreated': 1380745680, 'dateModified': 1417048885, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54893', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create a \"hamburger\"-icon (☰) drop down menu for toolbar items which aren\\'t editing tools', 'description': {'raw': 'Such as:\\n* Page settings\\n* Help/about/version\\n* Switch to source editing\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380731297, 'spacePHID': None, 'dateCreated': 1380708480, 'dateModified': 1417571041, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54869', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Edit tab titles are not consistent', 'description': {'raw': 'Edit tab titles are not consistent (on hu.wikipedia):\\n\\n- If I am logged out, I see tab title \"visualeditor-ca-editsource\", and it opens the source edit page.\\n- If I am logged in, and I have opt-outed from VisualEditor, then I see \"vector-view-edit\", and it opens the source edit page.\\n- If I am logged in, and I have VisualEditor enabled (default), then I see \"vector-view-edit\", which opens the visual edit page, and also \"visualeditor-ca-editsource\", which opens the source edit page.\\n\\nSome user on hu.wikipedia complained, that the same \"vector-view-edit\" meant source edit 2 days ago, and it now means visual edit, which is confusing. So we would like to rename both tabs, to be clear for everyone: we want to create a \"Visual edit\" and a \"Source edit\" tab, with the same text for everyone. But this structure makes impossible to set translation according to this, because opt-outed users se the same text for source edit as non-opt-outed users for visual edit.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hfilh4urx5vchfwani3k', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380835091, 'spacePHID': None, 'dateCreated': 1380704760, 'dateModified': 1380835091, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54866', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Delete VisualEditor/core repo', 'description': {'raw': 'http://git.wikimedia.org/summary/?r=VisualEditor/core.git\\n\\nSeems unneeded.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380591667, 'spacePHID': None, 'dateCreated': 1380590700, 'dateModified': 1380591667, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54813', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"When editing using VisualEditor I see the '♙' character at every newline\", 'description': {'raw': \"Hi\\nJust like the title, if I edit the body of the text, at every newline it enters an ♙ character, and I have to manually delete every time (by writig, going back and deleting).\\n\\nAlso there are many other special characters displayed, like arrows for tab and return. Don't know if it's the same issue.\\n\\nThe wiki is hosted on a CentOS 6.4 box, running latest versions of apache and PHP, under a virtualhost. The client is an OSX 10.9 computer.\\n\\nPlease tell me if you need any additional information.\\n\\nThank you.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Platform**: Macintosh\"}, 'authorPHID': 'PHID-USER-vj2bbc63joi46qr5a5nq', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380559441, 'spacePHID': None, 'dateCreated': 1380546240, 'dateModified': 1417571042, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54785', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images are slow to update in the search index', 'description': {'raw': 'Inserting media with VE\\n\\nSometimes I cant add image, because it doesnt display. This time at https://cs.wikipedia.org/wiki/Seznam_památných_stromů_v_okrese_Rokycany\\n\\nadding File:Kařízský dub, pohled.jpg with FF 23.0.1\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**Whiteboard**: cirrus-fixed\\n\\n**Attached**: {F12341}'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382572188, 'spacePHID': None, 'dateCreated': 1380515400, 'dateModified': 1405511296, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54777', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Dragging elements to the end of the page should make a new empty line appear', 'description': {'raw': 'When you want to drag an element to the very bottom of the content editable area, the last position available for the cursor is the end of the last sentence. \\n\\nUsually you want to place elements not at the end of a line, but right after, in a new line. The behavior expected would be to see a new empty line appearing when you drag an element until the end of a page, and the possibility to drop your element in that empty line.\\n\\nTested with the {{Languages}} template at https://www.mediawiki.org/wiki/Groups \\n\\nThe last cursor position possible is at the end of the sentence: \"... to create your MediaWiki group.\" Dropping the template after the last dot puts it at the end of the page, in a new line. The end result is correct, but the behavior is unituitive.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51666'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381246558, 'spacePHID': None, 'dateCreated': 1380427800, 'dateModified': 1428727208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54756', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor opt-in preference disappears', 'description': {'raw': 'As user Selenium_user on beta labs enwiki, I have set my preference to opt-in to VisualEditor several times, but the preference then gets reset to default (opt-in not set) after a period of some hours.  \\n\\nThis causes failures in the browser tests and I wonder if it is a risk in the production environment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380642094, 'spacePHID': None, 'dateCreated': 1380234840, 'dateModified': 1380642094, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54671', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: (silently) renumbering references', 'description': {'raw': 'Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 :\\n<<[this edit] is the original problem. It gave all of those references the same \"name\" (\"ref name=\":4\"\"), which convinced the software using for viewing pages that they were all the same ref.>>\\n\\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\\n<<About half of the 18 references I typed into the article on Homesickness disappeared between yesterday and today. I was certain to follow the Save Changes procedure, but many different references reverted to the same single reference. [...] Same bug today. In VE, I placed the cursor in the text, chose \"Reference\" from the \"More\" menu, added a reference, (It appeared as it should with the appropriate numerical superscript), Saved the work, returned to check the page...references disappeared from the list. - Window 8, Chrome >>.\\n\\nTeamGale adds:\\n<<Hello...I have the same problem [...]. I didn\\'t realized that it happened while I was editing. I only saw it when I saved the article and the number of the references had decreased. This https://en.wikipedia.org/w/index.php?title=Michael_Giannatos&diff=next&oldid=573583391 is the change I was doing when it happened. Could it be related to editing a table with beta? Probably not since I don\\'t see any table on Christopher Thurber\\'s article. After I re-added the references and the new table, every time I click \"edit beta\" the refs are gone! Before I even do any change! Basically I can\\'t use beta at all on this article! I don\\'t have any issues using the source but, if it\\'s something simple that can be done with beta, I prefer to do it with it. But I can\\'t. Just wanted to say that this is happening to other articles as well. And it\\'s possible to happen and people don\\'t see it. That would be a problem to a long article with lots of references... Mozilla 21, Windows 8.>>\\n\\nTeamGale again:\\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] \\nUpdate: Tables were a coincidence. It happened to me again in main article\\'s text. I didn\\'t save the edit this time...>>\\n\\nI think I saw this renumbering issue at it.wp as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380220185, 'spacePHID': None, 'dateCreated': 1380214860, 'dateModified': 1380220185, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54654', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Section-editing lands user at wrong URL post-save', 'description': {'raw': \"After successfully section-editing <https://en.wikipedia.org/w/index.php?title=Black_Mail_%281973_film%29&section=2&veaction=edit> using VisualEditor, I land at <https://en.wikipedia.org/w/index.php?title=Black_Mail_%281973_film%29&section=2>.\\n\\nThis shouldn't happen. &section=2 doesn't do anything with the implicit &action=view.\\n\\nPossibly related to bug 53089.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392058252, 'spacePHID': None, 'dateCreated': 1380209340, 'dateModified': 1392058252, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54645', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Right half of toolbar disappears when image caption on first line contains \"page \" followed by any string', 'description': {'raw': 'When an image caption on the first line of a page contains the string \"page \" (including the trailing space) followed by any text the right half of the VisualEditor toolbar disappears (everything right of \"more\"). This includes the save button so edits cannot be saved (hence the \"major\" severity)\\n\\nThis is likely related to either bug 54379 (same symptoms) or bug 53312 (same trigger).\\n\\nComments on the VE/F report at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=574608525#Odd_one suggest this might be restricted to FireFox.\\n\\nMinimal test: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=574608905\\nReal-world example: https://en.wikipedia.org/w/index.php?title=Clarke,_Irwin_%26_Company&oldid=574526057\\n\\nTo reproduce:\\n1. Create a page with any image on the first line of page\\n2. Give the image a caption containing the string \"page \" (including the trailing space) followed by any text.\\n3. Save the page\\n4. Load the page in VE and observe the right half of the editing toolbar.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53312\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54379'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393531206, 'spacePHID': None, 'dateCreated': 1380206280, 'dateModified': 1417570950, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'wikitech.wikimedia.org needs to have VE enabled', 'description': {'raw': \"'coz I likes it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-2nnm76h4ykalvvref2ye', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380217469, 'spacePHID': None, 'dateCreated': 1380197400, 'dateModified': 1496862142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54636', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Linux font stack sometimes lies about font width, leading to odd wrapping of text in format menu', 'description': {'raw': 'subhead shows \"2\" in the wrong place\\n\\nseen in Firefox not in Chrome:  \\n\\nchoose some text and pick a headings format.  Subheads with numbers show the number below the selectbox.  see screen shot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12017}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399644958, 'spacePHID': None, 'dateCreated': 1380146220, 'dateModified': 1417570827, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54614', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'update other repos to qa/browsertests practices', 'description': {'raw': \"visualeditor browser tests don't use MEDIAWIKI_PASSWORD, they still use secret.yaml.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381410415, 'spacePHID': None, 'dateCreated': 1380120060, 'dateModified': 1381410431, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54600', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Aborting the insertion of a formula should not insert any content', 'description': {'raw': 'If you click to use LaTeX, the \"math editor\" option, you cannot cancel or escape out of input.  VisualEditor adds the <math></math> tags regardless and this can only be removed by saving and going to source.\\n\\nIdeally, a cancel [X] or keyboard options should work to remove this.\\n\\nhttps://www.mediawiki.org/w/index.php?title=User:Keegan_(WMF)/sandbox&action=history\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394480263, 'spacePHID': None, 'dateCreated': 1380089700, 'dateModified': 1417570931, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54591', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add Sikuli to the machines that run browser tests', 'description': {'raw': \"Sikuli ( http://www.sikuli.org ) is a tool for testing desktop interactions, such as mouse clicks and keyboard typing.\\n\\nThis tool is needed for testing typing in different languages, because the usual WebDriver tests are not able to generate proper keyboard events that completely emulate typing in advanced input methods for Japanese, Chinese and Indic scripts. We have many bugs in this area in the VisualEditor (e.g. Bug 52716), so we need proper regression testing.\\n\\nThis week I worked with Željko in the WMF office and we built a prototype test that uses Sikuli to test typing in Japanese:\\nhttps://gerrit.wikimedia.org/r/#/c/83966/\\n\\nThis works on Željko's laptop. The next step is to get it working on the virtual clients that run our continuous integration tests.\\n\\nThank you!\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412692524, 'spacePHID': None, 'dateCreated': 1379701560, 'dateModified': 1425618435, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54393', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Behaviour of <pre> tags', 'description': {'raw': 'VE allows editing text between <pre>...</pre> tags.\\nThat is, you seem to be able, for example, to add working wikilinks and references. Once you save though, everything is rendered as wikicode, as in [[France]] and <ref>France</ref>, and of course is not clickable.\\nThryduulf argues that \"VE shouldn\\'t show it as working if it won\\'t work after saving\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415881409, 'spacePHID': None, 'dateCreated': 1379694480, 'dateModified': 1415881409, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54382', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Some templates with images show full size images on Swedish Wikipedia', 'description': {'raw': 'In some templates (e.g. Template:Infobox fornminne) on Swedish Wikipedia, the image in it is shown in full size when you enter VE. \\n\\nArticle: https://sv.wikipedia.org/wiki/S%C3%B6dermanlands_runinskrifter_305\\nScreencast: https://dl.dropboxusercontent.com/u/8363895/out-8.ogv\\n\\nIt does not behave like that for all templates though. In an article with Template:Kommunfakta is seems to work fine. E.g. https://sv.wikipedia.org/wiki/Botkyrka_kommun\\n\\nBehaviour is observed from two different users and in both Firefox and Chromium.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380930193, 'spacePHID': None, 'dateCreated': 1379671920, 'dateModified': 1417048884, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54371', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Consistency when restoring a page', 'description': {'raw': '<<[...] When you edit an old version of a page, you get the \"save page\" at the top of the page, but a \"restore page\" button instead of the \"save page\" button at the edit summary page, even if you have made changes in the older version (and thus aren\\'t simply restoring it). Why we have two different buttons (save and restore), when we have only one name otherwise, isn\\'t clear. Beneath the \"restore page \" button, the small text says \"By clicking the \"save page\" button, you agree...\". It doesn\\'t indicate what I agree to by clicking the \"restore page\" button though... Fram (talk) 14:08, 19 September 2013 (UTC) >>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383767339, 'spacePHID': None, 'dateCreated': 1379602800, 'dateModified': 1383767339, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54329', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: blue template overlay overlaps other page elements', 'description': {'raw': 'Try clicking the commons template in https://pl.wikipedia.org/wiki/Omega_Centauri?veaction=edit for an example. This bug appeared a while back, and seems to have regressed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50970'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402294829, 'spacePHID': None, 'dateCreated': 1379555760, 'dateModified': 1402294829, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54301', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Media items are inserted after selection and do not replace them', 'description': {'raw': '**Author:** `renukaalurkar`\\n\\n**Description:**\\n1)Log into http://en.wikipedia.beta.wmflabs.org\\n2)Go to your user page\\n3)Click on Edit beta tab\\n4)Click on More\\n5)Click Media\\n6)Enter santa claus, select a image from the selection of images\\n7)Select the image(the image is displayed in light blue)\\n8)Again click on More, then Media and select another image.\\n\\nExpected:The original/old image should be replaced by the new image.\\nObserved: The new image is added and the original image is also displayed.\\n\\nAnother observation: Also, suppose there are 4 images Image1, Image2, Image3, Image4 one below the other. If Image2 is selected and I try to replace it with a new image, the new image appears in the place of Image3(instead of Image2).\\n\\nObserved on Firefox and Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51033'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380657485, 'spacePHID': None, 'dateCreated': 1379530500, 'dateModified': 1417571042, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54285', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding bold/italics to spaces before/after a word results in ugly wikitext', 'description': {'raw': \"Which is something like '' this '' as opposed to something like ''that''. Of course this is also true for the source editor, but since the wikilink tool already gets rid of spaces at the beginning or at the end of a word, I wanted to make sure this can/should also be done when just formatting it (and it's being requested).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383767551, 'spacePHID': None, 'dateCreated': 1379509800, 'dateModified': 1383767551, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54270', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: prevent creating internal links with no displayed text or warn this is happening', 'description': {'raw': \"It is not easy, but you can create an empty wikilink with VE, https://en.wikipedia.org/w/index.php?title=Ascending_cholangitis&curid=5544827&diff=572776141&oldid=566427601 (I was able to reproduce that somehow, I think I just added the link to an empty space).\\nI can't imagine a situation where this is desirable or useful, please correct me if I am wrong.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380072033, 'spacePHID': None, 'dateCreated': 1379502900, 'dateModified': 1380072033, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54266', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'visible parsoid HTML in existing Flow content on toro', 'description': {'raw': 'I updated Flow, Parsoid, and VisualEditor on toro. Adding a new post worked fine and brought up VE (after a long delay during which the text area should probably be locked) and I could WYSIWYG. \\\\o/\\n\\nBut existing summary and some posts on http://toro.wmflabs.org/wiki/Special:Flow/Sandbox_2 that have images and links in them show stuff like\\n  <a rel=\"mw:WikiLink\" href=\".//Subpage\" data-parsoid=\"{\"stx\":\"simple\",\"a\":{\"href\":\".//Subpage\"},\"sa\":{\"href\":\"/Subpage\"},\"dsr\":[89,101,2,2]}\">\\n\\nsuggesting Flow is having problems figuring out Parsoid HTML content.\\n\\nI had set $wgFlowUseParsoid=true, now I think obsolete. I tried setting $wgFlowContentFormat=\\'html\\', didn\\'t seem to change behavior.\\n\\nFirebug reported some XHR errors, possibly from some VE API call, but now not.\\n\\nIf the issue is existing content doesn\\'t render right, this is fine to mark WONTFIX. We haven\\'t promised data compatibility yet.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379545289, 'spacePHID': None, 'dateCreated': 1379482140, 'dateModified': 1379545289, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54257', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dimensions of small images are lost in rendering', 'description': {'raw': 'Images that have thumbnail sizes that are larger than the original should be rendered at the specified size, not the size of the original.\\n\\nMediaWiki core does this, but somewhere between MediaWiki/Parsoid/VisualEditor the specified dimensions are lost.\\n\\n\\nFor example, on https://www.mediawiki.org/wiki/VisualEditor/Team there are various uses of [[File:Wikimedia_Foundation_office_camera_shy.png]] (of which the full size is 140px). The thumbnail size on that page is 150px, and when viewing the page normally it is rendered at 150px (browser scales up from 140px non-thumb url), but when editing in VisualEditor the node has a width attribtue of 140 instead of 150.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415881118, 'spacePHID': None, 'dateCreated': 1379390340, 'dateModified': 1417048865, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54205', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cant edit as logged in', 'description': {'raw': \"Using FF 23.0.1 and Google Chrome 29.0.1547.66 m. Try edit w:en:Ondine's curse from a section #Treatment and prognosis. When logged the page shows to be in process, but never allowes editing. Why I log of editing via VE is possible within seconds.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker\"}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379376765, 'spacePHID': None, 'dateCreated': 1379362020, 'dateModified': 1417571044, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54182', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit summary field loses focus when pasting (Firefox)', 'description': {'raw': 'When pasting some text into the edit summary box in Firefox 23 (via Ctrl+V or context menu), the paste occurs, but the edit summary box loses focus.\\n\\nPossibly related to bug 53632??\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393634141, 'spacePHID': None, 'dateCreated': 1378792920, 'dateModified': 1417570948, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53979', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Templates and tables {{infobox ship begin}}', 'description': {'raw': 'This is going to give you a headache\\n\\n{{Infobox ship begin}}\\nhttp://en.wikipedia.org/wiki/Template:Infobox_ship_begin\\nis used in 26840 pages. I provides styling for tables used to make infoboxes relating to ships. It is used like\\n\\n{|{{Infobox ship begin}}\\n{{Infobox ship image\\n|Ship image=[[File:Whydah-model.jpg|300px]]\\n|Ship caption=The \\'\\'Whydah Gally\\'\\' (1716–1717)\\n}}\\n{{Infobox Ship Career\\n...\\n}}\\n|-\\n|Commanded by:\\n|Cap\\'t. [[Lawrence Prince]]\\n...\\n|}\\n\\nThe template transcludes {{WPMILHIST Infobox style}} which provides CSS styling\\nclass=\"infobox {{#if:{{{2|}}}|{{{2}}}}}\" style=\"float: right; clear: right; width: 315px; border-spacing: 2px; text-align: left; font-size: 90%;\"\\nSo the table start tag and its styling are separate.\\n\\nUnsurprisingly VE fails to edit pages with this template correctly. The following was reported at \\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=572065469\\n\\nOpen the article in the visual editor, e.g. by visiting https://en.wikipedia.org/wiki/Whydah_Gally?veaction=edit\\nObserve the article now leads with the out-of-place text \\n <nowiki>class=\"infobox \" style=\"float: right; clear: right; width: 315px; border-spacing: 2px; text-align: left; font-size: 90%;\"\\ufeff</nowiki>\\ntry to click \"save page\" but note that it is not active\\nmake a trivial change so that \"save page\" is active.  Click it\\nClick \"review your changes\", not that it says that\\n<nowiki>{{Italic title}}{|{{Infobox ship begin}}</nowiki>\\nwas replaced with\\n<nowiki>{{Italic title}}{{Infobox ship begin}}\\n{|{{Infobox ship begin}}</nowiki>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386015391, 'spacePHID': None, 'dateCreated': 1378673760, 'dateModified': 1386015391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53927', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Disallow media items in other media items' captions\", 'description': {'raw': 'This is a strange edit, where a new editor inserted an image in the image description of an existing image. A bug or something that should be able to be done? \\n\\nhttps://sv.wikipedia.org/w/index.php?title=Dry_Martini&diff=prev&oldid=23709630\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383759108, 'spacePHID': None, 'dateCreated': 1378584900, 'dateModified': 1383759108, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53896', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When editing an infobox, the labels are sorted alphabetically and not in the original order', 'description': {'raw': '**Author:** `lionel.allorge`\\n\\n**Description:**\\nIn an infobox, items are in a certain logical order, for exemple, the image item and the caption are next to each other but the VisualEditor sort them alphabetically making it more difficult to find them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380655447, 'spacePHID': None, 'dateCreated': 1378551060, 'dateModified': 1417048885, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53891', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'AssessmentBar gadget clashes with VisualEditor edit surface', 'description': {'raw': \"Bug pic\\n\\nShould this happen or shouldn't it?\\nBtw, steps:\\n1*  Install AssessmentBar from https://en.wikipedia.org/wiki/User:YuviPanda/AssessmentBar\\n2* Go to an article.\\n3* Go down to a picture or find the infobox.\\n4* Click on the picture or infobox (when it's halfway through the AssessmentBar) and it will highlight the AssessmentBar (treating it like a picture or an infobox) AND/OR Click on the part of the AssessmentBar where the picture or infobox is getting highlighted and the infobox or picture will get selected instead of the AssessmentBar.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11559}\"}, 'authorPHID': 'PHID-USER-wel3wo6tppcxgnrthxls', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378918457, 'spacePHID': None, 'dateCreated': 1378540620, 'dateModified': 1496862150, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53889', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: weird behavior with double square brackets', 'description': {'raw': 'Try to start a line with a wikilinked word as you might do in the source editor.\\n\\n1) Typing the opening double square brackets will not trigger the no-markup warning.\\n2) The opening brackets will immediately disappear, the closing ones will stay.\\n3) When you reach the second closing bracket, VE will also add another one on the following line. (If instead of moving to step 4 you use the keyboard arrows around the word, you will not be able anymore to type something outside the brackets, and will need your mouse to place yourself outside of them).\\n4) Keep typing something instead, then press Enter: whatever you added is automatically copied to the next line, while the \"third\" square bracket is furtherly moved onto the next line.\\n5) Now add the brackets to an already existing word, correctly triggering the warning. Save anyway.\\n6) Review the changes. The brackets that triggered the warning did not trigger the nowiki tags as well. An opening one and a closing one are gone, and what is left is weird anyway. (This can also be triggered before saving by hitting Back Space, but I can\\'t say where).\\nThe brackets that we added in the first place are all gone, the duplicated text is gone as well, just a lonely closing bracket stands still.\\n\\nhttps://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=61362482&oldid=61361463\\n\\nReminds me of https://bugzilla.wikimedia.org/show_bug.cgi?id=53079, actually.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57207'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383759476, 'spacePHID': None, 'dateCreated': 1378482300, 'dateModified': 1384805609, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53856', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editor changed a parameter in a template, but the parameter was removed when they clicked \"Apply Changes\"', 'description': {'raw': \"A user at it.wp reports that he could not successfully replace a picture with this edit https://it.wikipedia.org/w/index.php?title=Castello_di_Serravalle_%28Bosa%29&diff=61339995&oldid=61339964, although he managed to do so on other occasions, so he knows how it works.\\nHe just replaced Bosa Castle.jpg with Veduta del Castello.JPG, and correctly previewed the latter.\\nBut upon saving, the pic was gone - the field is empty. He tried again later, and managed to reproduce this behavior.\\nOther users, including me, are not able to reproduce this.\\nHe's using Chrome with Snow Leopard. Thanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62366\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383758872, 'spacePHID': None, 'dateCreated': 1378478400, 'dateModified': 1417570932, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53853', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikitext warning not triggered by <references />, <i>, etc.', 'description': {'raw': 'en.wp user Fram reports:\\n\"When I add something that VE decides needs \"nowiki\", it usually gives the warning \"Wikitext markup detected\". However, when I add <references/> to the bottom of a page, he wraps it in \"nowiki\"s, but no warning appears (while it does work with e.g. {{reflist}})\"\\n\\nMy testing at https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox2&diff=571756019&oldid=570197356 shows that <i> and <small> also get nowikied without triggering the warning.\\n\\n<!-- --> neither triggers the warning nor gets nowikied. I am about to start a discussion about whether that is desired or not.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56213'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383758460, 'spacePHID': None, 'dateCreated': 1378458780, 'dateModified': 1417571019, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53839', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"De.WP's quote template eats refs (or gets eaten)\", 'description': {'raw': 'The German template for quotes:\\n\\nhttps://de.wikipedia.org/wiki/Vorlage:Zitat\\n\\neats refs, or rather their display at the end of the article, if the refs are inserted in it & the article is loaded in VE. Example articles:\\n\\nhttps://de.wikipedia.org/wiki/Arvo_P%C3%A4rt -> ref 5 & 8\\n\\nhttps://de.wikipedia.org/wiki/The_Rolling_Stones -> 26, 123-125\\n\\nhttps://de.wikipedia.org/wiki/Chick_Corea -> ref 12\\n\\nReport:\\n\\nhttps://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=122231626#Einzelnachweise_am_Artikelende_werden_im_VE_nicht_angezeigt\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50474'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383003781, 'spacePHID': None, 'dateCreated': 1378330980, 'dateModified': 1434420282, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53777', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Corruption: Leading whitespace removed from pre block', 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=Epigram_%28programming_language%29&oldid=567048374&veaction=edit and click \"save\" (note that save box warns about corruption) and then \"view changes\" (ignoring the changes I have since made). The pre block has been corrupted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-bug3zrlooz3bdmi4fyl7', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379613849, 'spacePHID': None, 'dateCreated': 1378330500, 'dateModified': 1379613849, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53775', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Request for edit summary preview', 'description': {'raw': 'A De.WP user suggested to include a preview for the edit summary. Report:\\n\\nhttps://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=122207411#Vorschau_f.C3.BCr_Zusammenfassung_und_Quellen\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380545659, 'spacePHID': None, 'dateCreated': 1378253700, 'dateModified': 1395858748, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53729', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: adding section for references will suppress the Related Articles one', 'description': {'raw': 'See https://it.wikipedia.org/w/index.php?title=Bisanzio_Lupis&diff=61160806&oldid=51778070 .\\n\\nWhen creating a section for references and adding the relevant tag,\\nit will suppress the Related Articles section - just the heading, not the content.\\n\\nI reproduced it easily in my sandbox by just adding the contents that you can see in the diff above.\\nNote that it is not related to the reference being added in the same edit; here for instance https://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=61285258&oldid=61285224 it was added previously.\\n\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1425487289, 'spacePHID': None, 'dateCreated': 1378206960, 'dateModified': 1438627757, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53699', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikitext warning triggered without adding wikitext', 'description': {'raw': '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.\\n\\nTo reproduce:\\n1. Load https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&oldid=571089410&veaction=edit\\n2. 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). \\n\\nIt seems that the warning is triggered by the existence of wikitext markup in the VE editing surface, rather than by its addition.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378458424, 'spacePHID': None, 'dateCreated': 1378050300, 'dateModified': 1378458424, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53661', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show and make editable <nowiki>, </nowiki> and <nowiki /> tags', 'description': {'raw': 'There is discussion at https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=571087443#nowiki_tags about using the edit filter to block edits adding the <nowiki /> tag in mainspace. However it was pointed out that \"the user probably has no way to know what they need to fix in order to resubmit their edit.  They can\\'t find the nowiki tag, as it is invisible.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49806\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49603'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390023864, 'spacePHID': None, 'dateCreated': 1378049580, 'dateModified': 1417570823, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53659', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'text duplicated when following an image', 'description': {'raw': \"In some odd circumstances the text immediately following an image is duplicated. You can see the effect in\\nhttp://en.wikipedia.org/w/index.php?title=Danny_Nalliah&oldid=570830443&veaction=edit\\nwhere the text '''Daniel (Danny) Nalliah''' is duplicated. \\n\\nTo make things more confusing it does not occur for every revision \\nhttp://en.wikipedia.org/w/index.php?title=Danny_Nalliah&oldid=570591483&veaction=edit\\nworks fine.\\n\\nTo make things thoughly weird in this revision in my sandbox\\nhttp://en.wikipedia.org/w/index.php?title=User:Salix_alba/sandbox&oldid=570839025\\nthe text '''Daniel (Danny) Nalliah''' does not appear. Yet it magically appear in VE\\nhttp://en.wikipedia.org/w/index.php?title=User:Salix_alba/sandbox&direction=prev&oldid=570839025&veaction=edit\\n\\nThis issues is discussed at \\nhttp://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Still_looks_like_VE_Feedback_to_me\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1423705265, 'spacePHID': None, 'dateCreated': 1378023300, 'dateModified': 1423705265, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53643', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot paste into edit summary in Chromium', 'description': {'raw': 'I cannot paste text into the edit summary with Ctrl+V or right click and paste when I use Chromium Version 28.0.1500.71 Ubuntu 13.04 (28.0.1500.71-0ubuntu1.13.04.1). Nothing happens. It works fine in FireFox though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393634250, 'spacePHID': None, 'dateCreated': 1377976740, 'dateModified': 1393634250, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53632', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Delete tests from browsertests repository that are moved to other repositories', 'description': {'raw': 'We have moved ULS and VisualEditor tests to their repositories. Delete the code from browsertests repository.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382022159, 'spacePHID': None, 'dateCreated': 1377862680, 'dateModified': 1382022164, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53582', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Figure out how to reuse common test code between repositories', 'description': {'raw': 'At the moment we have similar setup code for browser tests in 6 repositories:\\n\\nhttps://github.com/wikimedia/qa-browsertests\\nhttps://github.com/wikimedia/mediawiki-extensions-CirrusSearch\\nhttps://github.com/wikimedia/mediawiki-extensions-MobileFrontend\\nhttps://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector\\nhttps://github.com/wikimedia/mediawiki-extensions-VisualEditor\\nhttps://github.com/wikimedia/mediawiki-extensions-Wikibase\\n\\nFigure out a way how to reduce code duplication. We should probably create a Ruby gem.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381410774, 'spacePHID': None, 'dateCreated': 1377862440, 'dateModified': 1381410782, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53581', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Update readme file so it contains links to all repositories with Selenium tests', 'description': {'raw': 'README.md[1] file has information about Selenium tests in\\n\\nhttps://github.com/wikimedia/mediawiki-extensions-MobileFrontend\\n\\nAdd links to:\\n\\nhttps://github.com/wikimedia/mediawiki-extensions-CirrusSearch\\nhttps://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector\\nhttps://github.com/wikimedia/mediawiki-extensions-VisualEditor\\nhttps://github.com/wikimedia/mediawiki-extensions-Wikibase\\n\\n1: https://github.com/wikimedia/qa-browsertests/blob/master/README.md\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382359575, 'spacePHID': None, 'dateCreated': 1377862320, 'dateModified': 1382419139, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53580', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make sure all repositories have the latest version of shared code', 'description': {'raw': '.ruby-gemset and .ruby-version should be removed and RVM setup should be moved to Gemfile[1].\\n\\nRepositories that are doing it right:\\nhttps://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector\\nhttps://github.com/wikimedia/mediawiki-extensions-VisualEditor\\n\\nRepositories that should be updated:\\n\\nhttps://github.com/wikimedia/mediawiki-extensions-CirrusSearch\\nhttps://github.com/wikimedia/mediawiki-extensions-MobileFrontend\\nhttps://github.com/wikimedia/mediawiki-extensions-Wikibase\\nhttps://github.com/wikimedia/qa-browsertests\\n\\n1: https://github.com/wikimedia/mediawiki-extensions-UniversalLanguageSelector/blob/master/tests/browser/Gemfile#L1-L2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382729080, 'spacePHID': None, 'dateCreated': 1377861960, 'dateModified': 1391447113, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53579', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Send e-mail notification to relevant people after jenkins job is completed', 'description': {'raw': 'Who gets e-mail notification is documented in jobs.md[1]. At the moment Chris and I get notification for all jobs. Michelle is added for MobileFrontend, Rachel and James for VisualEditor.\\n\\nNik Everett should be notified for CirrusSearch, Amir and Niklas for UniversalLanguageSelector.\\n\\n1: https://github.com/wikimedia/qa-browsertests/blob/master/docs/jobs.md\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381417555, 'spacePHID': None, 'dateCreated': 1377861600, 'dateModified': 1381846904, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53578', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Images after template are shielded and uneditable in RTL', 'description': {'raw': 'I could not replicate this in LTR wikis (en.wiki or MediaWiki.org) but I suspect this is not so much ltr/rtl but floating behavior of the templates and images.\\n\\nSee example here:\\nhttps://he.wikipedia.org/wiki/%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%D7%AA:Mooeypoo/%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99/%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_%D7%95%D7%9E%D7%A9%D7%97%D7%A7%D7%99%D7%9D?veaction=edit\\n\\nThe top two images are regular images (not templates) - they are perfectly editable if you remove the template at the top. They got their shielded status after I inserted that template.\\n\\nSteps to reproduce:\\n1. Edit a page\\n2. Insert some image (or more) to top\\n3. Save page\\n4. Edit again, insert template \"{{עליות}}\" just above the images. \\n5. Save.\\n6. Edit again. Observe: The images jumped to the left (wrong float side) and are now uneditable. \\n7. Interesting fact: Remove the template and save, then go back into the editor and the images are still uneditable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406318164, 'spacePHID': None, 'dateCreated': 1377795900, 'dateModified': 1417048872, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53542', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: broken reference tag swaps sections when VEditing', 'description': {'raw': \"If you open https://fr.wikipedia.org/w/index.php?title=Anna_Mouglalis&oldid=95468238&veaction=edit you'll notice a weird order of paragraphs. This is due to an extra space in the ref tag for the second reference. VE might probably autocorrect similar situations.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377786212, 'spacePHID': None, 'dateCreated': 1377784560, 'dateModified': 1377786212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53535', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parameters in RTL can be duplicated in the transclusion dialog', 'description': {'raw': 'To reproduce:\\n\\n1. Go to this page: https://he.wikipedia.org/wiki/%D7%90%D7%9C%D7%9B%D7%A1%D7%A0%D7%93%D7%A8_%D7%94%D7%92%D7%93%D7%95%D7%9C\\n2. Edit the infobox at the left side. \\n3. Behold! Some parameters appear both at the left panel (used) and also on the right panel (unused). Specific example, look for the parameters \"בן זוג\" and \"בת זוג\" \\n4. If you click the parameter \"בת זוג\" for example, on the left side (the used one) you will see data. If you click the one on the right side, it appears with empty textbox as if it\\'s new.\\n5. Click on the right side (as if to add param again) on \"בת זוג\" \\n6. Click again and again -- the parameter will keep being added to the list on the left in duplicates.\\n\\nAnd if the page is saved, the parameter is now completely removed.\\n\\n\\nThis has happened specifically in the hewiki but might be related to more than just RTL.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380749912, 'spacePHID': None, 'dateCreated': 1377741840, 'dateModified': 1417571041, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53515', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link insertion dialog should preserve the case of the initial character', 'description': {'raw': 'Currently whenever a user enters a link when no text is selected the first character of the displayed link is always capitalised. This is often incorrect, e.g. in the middle of a sentence or for articles like [[iPhone]] or [[grep]].\\n\\nEspecially until bug 50678 is fixed, correcting this is not at easy or intuitive.\\n\\nSo, at least until bug 48789 and bug 50945 are fixed and the display text is settable in the dialog, and probably beyond that, it would be best if the displayed link used the same case as the search term entered. i.e.\\n\\nUser entry ->  wikitext equivalent of desired output\\nGreen   ->  [[Green]]\\ngreen   ->  [[green]]\\niPad    ->  [[iPad]]\\nHAMmer  ->  [[Hammer]]\\nlondon  ->  [[london]]\\n\\nYes, this will result in some wrong captialisations, but no more than at present and will only be temporary (as noted above)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50678\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50745'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377802569, 'spacePHID': None, 'dateCreated': 1377720300, 'dateModified': 1489676436, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53495', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Right-click on newly linked page in VisualEditor opens invalid URL in new tab', 'description': {'raw': 'This is somewhat related to bug 50321.\\n\\nSteps to reproduce:\\n\\n1. Open your own sandbox/userpage (not a page in the mainspace) in VisualEditor.\\n2. Add a link to a word (\"xxx\").\\n3. Control-click/right-click/command-click the new link to open the link in a new tab or new window.\\n4. Discover that VisualEditor has sent you to an invalid URL:  http://en.wikipedia.org/w/Xxx or http://en.wikipedia.org/wiki/User:Whatamidoing_(WMF)/Xxx\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377718799, 'spacePHID': None, 'dateCreated': 1377715320, 'dateModified': 1377718799, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53491', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Move VisualEditor Selenium test to VisualEditor repository', 'description': {'raw': 'Requested by James Forrester at QA mailing list:\\n\\nhttp://lists.wikimedia.org/pipermail/qa/2013-August/000339.html\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377696492, 'spacePHID': None, 'dateCreated': 1377688440, 'dateModified': 1377860015, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53467', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Show edit summary after clicking save', 'description': {'raw': '**Author:** `molly.white5`\\n\\n**Description:**\\nOnly show the edit summary input box after the user clicks \"save\" (sort of like in the VisualEditor).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382039786, 'spacePHID': None, 'dateCreated': 1377659100, 'dateModified': 1382039786, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53450', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Media should be easily replaceable', 'description': {'raw': \"At the moment there doesn't appear to be a way to replace media - that is, to click on a media element, and select a different piece of media for that element. That's not a big deal at the moment, but we're going to move to a world where media settings are more complex - where alignment can be specified, referencing can be specified and permitted, so on and so forth.\\n\\nThe result of this is that media elements will have a lot of data associated with them - media it's pretty hard to type out again if you find that the image (or video, or...whatever) needs to be replaced. It would be good to have a way of replacing images without losing the associated caption, size and alignment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377621974, 'spacePHID': None, 'dateCreated': 1377621000, 'dateModified': 1417571047, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53409', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Search and replace feature needed', 'description': {'raw': 'We need a search-and-replace feature in VisualEditor. This seacrh box should also support ULS\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-qpuuryo2o37amdlkb5gk', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377460908, 'spacePHID': None, 'dateCreated': 1377447840, 'dateModified': 1377460908, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53326', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Inserting and editing tables', 'description': {'raw': 'There should be a facility in VisualEditor for creating new table or edit an existing table\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-qpuuryo2o37amdlkb5gk', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377528014, 'spacePHID': None, 'dateCreated': 1377447540, 'dateModified': 1377528014, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53325', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: inconsistency when reviewing changes after a null edit', 'description': {'raw': 'User report:\\n<<So I put a space and then a backspace.  Go to save, review changes to check and make sure it is a null edit, then it goes to this \"processing\" dialogue but then it shows \"Could not start the review because your revision matches the latest version of this page.\"  So then I press the little back link on the dialogue, but it just goes back to the processing dialogue.  If the page is small, the processing is really quick, so before I can even press back again, it goes back to the \"Could not start\" warning message.  Even if I do manage to press the back a second time quickly, it will only stay at the save dialogue for a split second and then again bring me to the warning message, although \\'\\'then\\'\\' pressing back does take me to the save dialogue securely.  FF 23.0.1 Win7.>>\\n\\nI managed to reproduce this on Chrome as well, so which is the intended left button behaviour?\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377426954, 'spacePHID': None, 'dateCreated': 1377426720, 'dateModified': 1377426954, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53314', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE does not finish initialization on KOWP', 'description': {'raw': \"**Author:** `ryuch`\\n\\n**Description:**\\nVE not can be enabled by options in preferences for beta testing.\\nWhen I click 'edit' on an article, the progress bar appear but does not finish initialization.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380703487, 'spacePHID': None, 'dateCreated': 1377353520, 'dateModified': 1417571041, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53301', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor tests fail due to introductory beta disclaimer popup', 'description': {'raw': 'cucumber features/visual_editor_anon.feature:5 # Scenario: Basic edit fails \\nbecause VisualEditor these days shows an introductory disclaimer:\\n\\n  This is our new, easier way to edit. It\\'s still in beta,\\n  which means you might find parts of the page you can\\'t edit...\\nand so it fails with\\n  expected \"You are not currently logged in. \\nwhich isn\\'t visible until you dismiss the popup.\\n\\nI think the same explains a\\n  timed out after 5 seconds, Element was not visible in 5 seconds\\nthat I\\'m getting in the similar\\ncucumber features/visual_editor_logged_in.feature:5 # Scenario: Basic edit\\nafter applying gerrit 80709.\\n\\nThe popup is in a div containing an iframe containing more divs until class=\"ve-ui-mwBetaWelcomeDialog-content\", and then tests have to click outside it to dismiss it; and some day it will go away.\\n\\nInstead it seems better to set the ve-beta-welcome-dialog cookie to 1 upon visiting the site, which will turn off this disclaimer dialog.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382983457, 'spacePHID': None, 'dateCreated': 1377334920, 'dateModified': 1382983457, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53295', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: add a wikilink to tags, the final inequality sign (>) is lost', 'description': {'raw': 'User report following:\\n<<If I start with a blank page, type in \"<br>\", select the entire text, press the link icon, select say \"France\" as the link, upon exiting the link dialog I am left with a link to [[France]] but the anchor is shortened to \"<b\".</nowiki>  I don\\'t get any \"Wikitext markup detected\" warning. >>\\nThis is true for other tags as well (I tried with <b>).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397676516, 'spacePHID': None, 'dateCreated': 1377286560, 'dateModified': 1397676516, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53280', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor is inserting greater than signs (>)', 'description': {'raw': 'While I was fixing a simple grammatical error, VE threw in a > sign at the start of a template further down the page thus breaking the template.\\n\\nhttps://en.wikipedia.org/w/index.php?title=Tesla_Model_S&diff=next&oldid=569876875\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394480185, 'spacePHID': None, 'dateCreated': 1377279060, 'dateModified': 1394480992, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53262', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unable to use save button using keyboard', 'description': {'raw': 'If I focus on the save button using [tab] from textarea, [enter] don’t save the page.\\n\\nApparently the focus goes on the <div role=\"button\"> while the click event is listened on the span.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398102157, 'spacePHID': None, 'dateCreated': 1377270420, 'dateModified': 1398102157, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53257', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Changing the first letter of wikilinked words is difficult', 'description': {'raw': \"Seems I had written about it in an unrelated bug, sorry. This happens on itwp: in order to do this\\nhttp://it.wikipedia.org/w/index.php?title=DNasi_attivata_da_caspasi&diff=60101664&oldid=60089990\\nI had to delete the word and link it back again. Our guidelines about style\\nrequire pages in that section to appear with the capital letter, so we need to be able to fix that easily.\\n\\nIt is also reported on en.wp, the user states <<When trying to correct a lower-case letter to a capital letter at the beginning of a link, I deleted the lower-case letter and found I couldn't type a capital letter and have it become part of the link, nor could I seem to extend the link over the capital. Eventually, I typed the capital after the lower-case letter and then deleted the lower-case letter. It might be good to have some way to extend a link over adjoining letters/words/text. Mount Flatten (talk) 05:31, 22 August 2013 (UTC) >>\\nThanks.\\n\\nps. Might be related to https://bugzilla.wikimedia.org/show_bug.cgi?id=50745 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50745\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377445650, 'spacePHID': None, 'dateCreated': 1377174060, 'dateModified': 1618767881, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53210', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: can't fix a broken template since this will result invisible\", 'description': {'raw': \"See http://en.wikipedia.org/w/index.php?title=User:Christian75/sandbox2&oldid=569697466 .\\nIf you edit the page with VE you won't see the broken template at all.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397676723, 'spacePHID': None, 'dateCreated': 1377164100, 'dateModified': 1425595037, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53205', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Need way to insert templates that set both key and value for a parameter into a template invocation, like {{subst:DATE}}', 'description': {'raw': \"Currently there is no way to use {{subst:DATE}} in a template invocation in VisualEditor. If you try to paste it into the value of a date field, it won't work because you get\\n\\n|date = date=August 2013\\n\\nwhich won't parse.\\n\\nVisualEditor should actually set the date automatically, always, for such templates (e.g. refimprove).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52345\"}, 'authorPHID': 'PHID-USER-bug3zrlooz3bdmi4fyl7', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377904404, 'spacePHID': None, 'dateCreated': 1377157620, 'dateModified': 1417571045, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53201', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links from a subpage are not rendered correctly in the editing surface', 'description': {'raw': 'If I add an unprefixed link to [[Main Page]] on\\n\\nhttps://www.mediawiki.org/wiki/Wikimedia_Engineering/WMF_Tech_Days_2013\\n\\nusing VisualEditor, the link points to [[Wikimedia Engineering/Main Page]] when previewed in VisualEditor (by right-clicking and opening in a new tab). \"Review changes\" suggests that the correct link will be added when saving the page, so this issue may be limited to the editing surface.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377727533, 'spacePHID': None, 'dateCreated': 1377130800, 'dateModified': 1377727533, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53190', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: nowiki when trying to edit an external link in references', 'description': {'raw': 'On de.WP, a user tried to replace an outdated link within an existing ref via VE and ran into a nowiki. \\n\\ndiff:\\n\\nhttp://de.wikipedia.org/w/index.php?title=Kin-dsa-dsa%21&diff=121506430&oldid=117367043\\n\\nreport:\\n\\nhttp://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121759646#nowiki_bei_unbeschriftetem_Link\\n\\nI could reproduce that; the previous is showing it prior to saving, too.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412470303, 'spacePHID': None, 'dateCreated': 1377124920, 'dateModified': 1417048868, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53183', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cannot enter multiple authors in cite web template', 'description': {'raw': 'When I add a reference and add a template of type \"cite web\" in the reference, the template only allows me to enter a single author last name and a single author first name. To enter multiple authors I\\'m supposed to use the attributes \"last1, first1 through last9, first9 for up to nine authors\", but VisualEditor doesn\\'t seem to offer the possibility of adding these attributes.\\n\\nThere is an \"others\" field, but this is only supposed to be used for people who are neither authors nor editors, e.g. illustrators.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-bug3zrlooz3bdmi4fyl7', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377114222, 'spacePHID': None, 'dateCreated': 1377110520, 'dateModified': 1377114222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53166', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Removal of template when adding reference list', 'description': {'raw': 'Screencast\\n\\nWhen trying to add a new section and a reference list an existing template (defaultsort) gets removed, see screencast attachment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11699}'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416183797, 'spacePHID': None, 'dateCreated': 1377029340, 'dateModified': 1416183797, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53114', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"edit lead section\" link incorrectly points to second section', 'description': {'raw': '**Author:** `sumanah`\\n\\n**Description:**\\nOn mediawiki.org, I have enabled the \"Add an [edit] link for the lead section of a page\" gadget and the \"Enable section editing via [edit] links\" Preference (in the Editing tab).\\n\\nIf I go to a wiki page on mediawiki.org and click \"edit\" or \"edit source\" next to the title of an article (e.g., on https://www.mediawiki.org/wiki/Wikimedia_Labs ), then the VisualEditor link correctly thinks I want section 0, the lead section:\\n\\nhttps://www.mediawiki.org/w/index.php?title=Wikimedia_Labs&veaction=edit&section=0\\n\\nbut the \"edit source\" link thinks I want section #1 and thus brings me to edit the \"Background\" section:\\n\\nhttps://www.mediawiki.org/w/index.php?title=Wikimedia_Labs&action=edit&section=1\\n\\nThis may be a problem with the gadget rather than with VE, but it only started recently, so I think it might be a VE-related issue.  (I have looked at Bug 51030 - \"Edit link for lead section no longer works\" which sounds sort of separate.)  I shall also mention this bug in the talk page of the relevant gadget.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376668133, 'spacePHID': None, 'dateCreated': 1376623920, 'dateModified': 1376668133, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52910', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Error: Unknown error\" when creating page on test2wiki', 'description': {'raw': '**Author:** `sumanah`\\n\\n**Description:**\\nclose-up of error message and greyed button\\n\\n1. Try to use the VE to create a page at https://test2.wikipedia.org (while logged in, if that makes a difference).\\n\\n2. Click \"Save page\" button.\\n\\nThe \"Save page\" button greys out and \"Error: Unknown error\" shows up to its left.  The user assumes that the page has not been saved.  But it has been created, e.g., https://test2.wikipedia.org/wiki/Kim_Stanley_Robinson .\\n\\nBy the way, if the user reacts to the error by clicking Review changes and then getting back to Save, everything works fine.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11279}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383015953, 'spacePHID': None, 'dateCreated': 1376614380, 'dateModified': 1383015953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52908', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit summary length counter \"hidden\" on it.wp', 'description': {'raw': 'This does not affect Firefox, from what I saw - I used Chrome.\\nI\\'d add a screenshot but it is really just as the summary says, \\nthe number is there and it is working but you can not see it because the equivalent for \"Watch this page\", which is \"Aggiungi agli osservati speciali\", overlaps it (only the last word, of course).\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394501931, 'spacePHID': None, 'dateCreated': 1376489160, 'dateModified': 1417570929, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52847', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'End of transcluded page not/incorrectly detected', 'description': {'raw': 'Screenshot 1\\n\\nhttps://de.wikipedia.org/wiki/Knebel transcludes https://de.wikipedia.org/wiki/Konrad_Knebel\\n\\nOnly 2 lines are transcluded but the VisualEditor does not detect the end of the transclusion, see screenshot 1.\\n\\nThe other 3 lines are handled as content of this \"template\", see screeshot 2.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://de.wikipedia.org/wiki/Knebel\\n\\n**Attached**: {F11960}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376639350, 'spacePHID': None, 'dateCreated': 1376417640, 'dateModified': 1376639350, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52814', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding more than one empty line (via Return) results in only 1 blank line being saved.', 'description': {'raw': \"Input in VisualEditor and Output after saving (+ Parsoid Server output)\\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 808cc39c81df83daaec458c81edbd126fd1dd19a\\nAuthor: Subramanya Sastry <ssastry@wikimedia.org>\\nDate:   Mon Aug 12 16:15:24 2013 -0500\\n\\n\\nAdding more than one empty line isn't possible in the VisualEditor extension. Is this a desired behaviour?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11917}\"}, 'authorPHID': 'PHID-USER-26asvhtv4jalaeeuigbm', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397676105, 'spacePHID': None, 'dateCreated': 1376401560, 'dateModified': 1422901896, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52798', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: support article layouts', 'description': {'raw': 'Pages started with a copy/paste of layouts (i.e. http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Football/Players ) are very, very common. VE does not seem to support this right now, making VE a very secondary choice to create articles. Probably related to https://bugzilla.wikimedia.org/show_bug.cgi?id=33105 , please feel free to mark this as a dupe if needed. Thanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383280378, 'spacePHID': None, 'dateCreated': 1376387040, 'dateModified': 1383281388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52787', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: reusing existing reference generates duplicate references', 'description': {'raw': 'All the references adding in this edit: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=568232613&oldid=568231803 were added using the \"use existing reference\" option. \\n\\nIt seems that only when I added the same reference on the same line (trying to reproduce a different bug) did it reuse the existing ref rather than creating a duplicate one.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401473395, 'spacePHID': None, 'dateCreated': 1376326380, 'dateModified': 1417570820, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"existing references\" in the references dialog not identifying references', 'description': {'raw': 'See https://pl.wikipedia.org/w/index.php?title=Wikipedysta:G%C5%BCdacz/brudnopis&oldid=37221362&veaction=edit for an example; only one citation appears as insertable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402332002, 'spacePHID': None, 'dateCreated': 1376287140, 'dateModified': 1417570778, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52742', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot backspace in Edit Summary window after reviewing changes', 'description': {'raw': '**Author:** `hagurganus`\\n\\n**Description:**\\nWhen typing an edit summary in the Edit Summary window, I was unable to backspace. It seemed to let me highlight and _replace_ text, but even then, I could not highlight and hit the backspace key to _remove_ the text, I had to highlight and hit spacebar to simply enter a space, etc.\\n\\nIt could be that this is intentional, but I highly doubt this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377833584, 'spacePHID': None, 'dateCreated': 1376249940, 'dateModified': 1377833584, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52733', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After \"wikimarkup\" popup, save button temporarily does not work', 'description': {'raw': 'An editor reports that he lost his work when an extensive edit unexpectedly triggered the \"wikimarkup\" popup and - after he dismissed it - the \"save\" button became unresponsive. The button appeared as normal but did not react to being selected.\\n\\nHe was using Windows 7 and Firefox.\\n\\nI reproduced this using Windows 7 and Chrome (didn\\'t matter if I removed the wikimarkup or not), and on further investigation found that the \"save\" button will respond as expected after a delay.\\n\\nThe issue, of course, is that if this editor aborted his edit because he thought the system would not save, others are likely to think that as well.\\n\\nNot sure if anything can be done to make the save button immediately responsive or to figure out why it wouldn\\'t be or to make it apparent to editors that the option to \"save\" will return.\\n\\nThe conversation can be found here:\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=567809017#Wikitext_error_message\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383015225, 'spacePHID': None, 'dateCreated': 1376050200, 'dateModified': 1383015225, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52669', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: don't display all tools by default to new editors\", 'description': {'raw': \"en.wp user Ruud Koot suggests that certain tools, such as underline and font colour (bug 52645) that are not normally wanted/needed in articles shouldn't be available to new editors.\\n\\nPersonally I think everything should be available (this avoids the need for new classes of editor permissions) but just not shown by default. What is shown/not shown by default needs to be configurable on-wiki per wiki (and possibly per namespace).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49617\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383015740, 'spacePHID': None, 'dateCreated': 1375957260, 'dateModified': 1383015787, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52646', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid or VisualEditor:  __NOTOC__ sometimes replaced by copy of categories', 'description': {'raw': 'en.wp user Ruud Koot reports that occasionally he gets \" weird, random and unexplainable corruptions of wikitext on save\" when using the VisualEditor.\\n\\nThe only example he gives is \"e.g., a __NOTOC__ being replaced with a copy of the categories\"\\n\\nBug 48231 might have something to do with this, but I confess to not understanding all the technical language there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376086189, 'spacePHID': None, 'dateCreated': 1375955220, 'dateModified': 1376086189, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52643', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: saving fails silently for some large edits', 'description': {'raw': 'en.wp user Ruud Koot reports:\\n\\n\"Occasionally, after a medium-sized editing session, the visual editor will silently refuse to save my edits. When clicking the save button the progress bar appears, disappears, and you stay in editing mode, with no new revision appended to the history. Trying again sometimes resolves the problem, sometimes it requires edit operations to be done in a different order or be broken up into smaller increments, saving in-between.\" \\n\\nHe also asks, \"Do you keep any statistics on how often an editor presses the save button versus how many times this actually results in a new revision being saved?\"\\n\\nBug 51423 might be related.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51243'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406598295, 'spacePHID': None, 'dateCreated': 1375954440, 'dateModified': 1417570765, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52640', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Bulleted bullets and bulleted headers produced; can't save\", 'description': {'raw': 'en.wp user Ruud Koot reports:\\n\"When performing structural editing tasks (i.e. things which are slight more complex than changing typos or adding a sentence in the middle of an existing paragraph) it is very easy to get the editor into some weird state where it is impossible to get out of other than aborting the edit session and trying again more carefully. This includes things like introducing \"bulleted headers\" and \"bulleted bullets\", which cannot possibly be represented as wikitext.\"\\n\\nHe notes that \"Copying and pasting around text and editing pages with tables [is a] fairly reliable method\" to reproduce it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1425633241, 'spacePHID': None, 'dateCreated': 1375953840, 'dateModified': 1425633241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52639', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Difficult to get a blank line when the page starts with a bulleted list', 'description': {'raw': 'If a page starts with a bulleted list, there\\'s no way to put the cursor \"in front of\" the list styling.  If you want to add a non-list paragraph, you have to make a new, blank first bullet item and then remove the list formatting from the paragraph.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52032'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1420846868, 'spacePHID': None, 'dateCreated': 1375918560, 'dateModified': 1420846868, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52620', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Edit notices don't scroll\", 'description': {'raw': 'Today\\'s Featured Article edit notice displayed in Firefox 22/Linux/Monobook on a 481px high window\\n\\nEdit 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).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51755\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52667\\n\\n**Attached**: {F11480}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377446690, 'spacePHID': None, 'dateCreated': 1375860960, 'dateModified': 1377446690, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52602', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Wikimedia editors aren't automatically enrolled in Bugzilla, reducing VE bug reporting\", 'description': {'raw': '**Author:** `gnu`\\n\\n**Description:**\\nThe unusually buggy deployment of the VisualEditor has caused large numbers of English Wikipedia editors to have bugs to report.  But the process of reporting bugs is a cumbersome many-step process -- starting with a requirement to \"log in\" using a credential that most editors do not have.\\n\\nThe rest of the Wikipedia universe uses a universal login system in which you log in with the same username and password to everything, and it all works together.  Somehow Bugzilla didn\\'t get integrated with that.\\n\\nSo instead anyone with a bug report for Visual Editor -- assuming they can even find Bugzilla, perhaps from a comment in an RFC about disabling the Visual Editor, as I found it -- then has to get through the \"New User\" process, which includes providing an email address, checking mail at that address, and accessing a URL which then demands that a new password be created and remembered.\\nThis step should be avoided for logged-in Wikipedia users.\\n\\nI\\'m sure that many, many Visual Editor bugs are noticed by editors, but are never reported due to the pain of the reporting process.  This shortage of bug reports may serve the political purposes of the WMF in attempting to ram the new editor down the throats of the community, but it is not a good management practice, nor will it result in eliminating the bugs that make the Visual Editor too troublesome for naive use at this point.\\n\\n(The remaining process of bug reporting is also cumbersome and complex -- but \\nin this bug report I have no suggestions on how to fix that.)\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375847060, 'spacePHID': None, 'dateCreated': 1375844100, 'dateModified': 1375847326, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52595', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Label for beta notice/menu should use mixed case not all caps (\"Beta\" not \"BETA\")', 'description': {'raw': 'From en.wp user Cryptic C62:\\nThe beta button on the toolbar \"should not be labelled \"Beta\", not \"BETA\". The latter looks like it might be a mysterious acronym. \"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393528505, 'spacePHID': None, 'dateCreated': 1375820700, 'dateModified': 1393528505, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52586', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot edit notes that use {{ref}} and {{note}} system.', 'description': {'raw': 'Where articles use the {{ref}} and  {{note}} pair of templates to generate footnotes, e.g. [[List of highest points of Canadian provinces and territories]], it is impossible to edit the contents of the notes in VisualEditor.\\n\\nThe {{ref}} template is editable in the transclusion editor, and works as expected.\\n\\nThe {{note}}-generated notes are apparently one block. No transclusion icon or indication of uneditablility (green stripes) appears on mouseover or when the block is clicked. \\n\\nIf a link in the notes is clicked it functions as a link would in read mode- ie. the link is followed and you leave the page. VE gives no warning about unsaved edits (although Firefox does).\\n\\nIf the backlink to the location of the {{ref}} template is clicked it functions as above - i.e. it loads the page in read mode at the position of the note, exactly as if you had followed a link to that anchor from any other page on the internet.\\n\\nIt is possible to select the block when selecting content before and after the block, although no indication is given that it has been selected. Once selected it is possible to apply bold/italic formatting to the block and other selected text using the B/I buttons, but it is not then possible to remove it using these buttons while the note block is selected. It is possible to remove bold/italic using the clear format button. The clear format button does not remove any links in the notes block, but does remove links from any other text selected at the same time.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393541169, 'spacePHID': None, 'dateCreated': 1375800120, 'dateModified': 1459349685, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52579', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't wait indefinitely for gadget servers that are not responding\", 'description': {'raw': 'When a user has installed a gadget that relies on data from an external server, VisualEditor appears to wait indefinitely for that server to respond. Normally this is OK, but when that server is down VE will apparently wait forever (or at least longer than the 5 minutes I was prepared to wait) for a response.\\n\\nThe source editor appears to give up after a wile (2 minutes?), and loads as if the gadget was not called. VE should exhibit this behaviour too.\\n\\nTested with the HAPPI gadget ([[User:EpochFail/HAPPI]]). As of 21:52 UTC 05 August 2013 that gadget depends on a server at wikipedia.grouplens.org that is not responding\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390419026, 'spacePHID': None, 'dateCreated': 1375739580, 'dateModified': 1390419026, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52563', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor or Parsoid: inserted HTML code instead of Wikilink', 'description': {'raw': 'At line 42 of https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&diff=567254040&oldid=566841354 attempting replace what appeared to be an empty image caption with \"The [[Sun]]\" (using ctrl+k for the link, no wikicode) resulted in the insertion instead of:\\nThe <a style=\"white-space:nowrap\" data-mw=\"{&quot;target&quot;:{&quot;wt&quot;:&quot;val&quot;,&quot;href&quot;:&quot;../Template:Val&quot;},&quot;params&quot;:{&quot;1&quot;:{&quot;wt&quot;:&quot;4.6&quot;},&quot;ul&quot;:{&quot;wt&quot;:&quot;byr&quot;}},&quot;i&quot;:0}\" rel=\"mw:WikiLink\" href=\"Sun\">Sun</a>\\n\\nThe images were left over from testing for Bug 52341 and so that bug may be related.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401418799, 'spacePHID': None, 'dateCreated': 1375709160, 'dateModified': 1417570821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52544', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create a design guideline to minimize clicks and key presses', 'description': {'raw': 'visual editor easily doubles mouse clicks and key presses. this can be seen, amongst others, on section editing, saving, adding a reference. to avoid bug reports in the line of \"please remove one mouse click while creating a reference\" create a (visual) design guideline mandatory to follow for all developers to minimize mouse clicks and key presses, and maximise screen estate available for editing/viewing the article.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-2ccnbnjo2s2q3diidydr', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376561195, 'spacePHID': None, 'dateCreated': 1375607280, 'dateModified': 1376561195, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52520', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'De.WP experiences wired edit labels on conversation pages', 'description': {'raw': 'Currently, De.WP talk, user talk, Wikipedia, Wikipedia talk..pages show for the last section not [Edit source] as En/Es/xy.WP do but [Add section / Edit source code / Add section] (Abschnitt hinzufügen Quelltext bearbeiten Abschnitt hinzfügen). It neither breaks anything technically as far as I can tell right now nor does it mix in VE interface but, where ever it might come from, it should be fixed asap\\n\\nhttp://de.wikipedia.org/w/index.php?title=Diskussion:Immanuel_Kant&oldid=120880638\\n\\nhttp://de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:JEissfeldt_(WMF)&oldid=120853192#VisualEditor_.2A_Projektseiten\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375492148, 'spacePHID': None, 'dateCreated': 1375491060, 'dateModified': 1395858754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52491', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Blacklist category for excluding pages from VisualEditor', 'description': {'raw': \"It would be helpful to be able to selectively disable VisualEditor (we should to indicate to a user who'd otherwise see VisualEditor that it is disabled, to reduce confusion). This would enable users to shield pages where VisualEditor/Parsoid cause roundtrip issues.\\n\\nA hidden blacklist category could be included in a page or template to achieve the desired effect, and could be used by developers to prioritize roundtripping issues.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375488138, 'spacePHID': None, 'dateCreated': 1375487760, 'dateModified': 1417571051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52489', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Image thumbnails that don't specify size should render at the wiki-default size\", 'description': {'raw': 'If one opens the VE editing interface, the user experience in relation to image formats varies significantly. The report: \\n\\nhttp://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121153156#Bilder_werden_im_VE_kleiner_angezeigt\\n\\nhas several examples with different browsers like \\n\\nFF 22 / Win 7: edgewise images smaller; rest bigger.\\nChrome 28 / Win 7: all significantly smaller.\\n\\nSee also screenshots in perma link.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380666480, 'spacePHID': None, 'dateCreated': 1375487460, 'dateModified': 1417048875, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52487', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: uneditable table lines displayed wrong', 'description': {'raw': 'The 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 <tr> is wrapped in a <span>. Not really WYSIWYG…\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11257}'}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385374740, 'spacePHID': None, 'dateCreated': 1375486440, 'dateModified': 1385374740, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52485', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'References created by Singlechart cannot be accessed properly', 'description': {'raw': '**Author:** `kwwilliams`\\n\\n**Description:**\\nhttp://en.wikipedia.org/wiki/User:Kww/singlechartreftest is a simple test case for accessing references created by the singlechart template.\\n\\nSinglechart directly creates references when called, using #ref (it cannot use <ref></ref> 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.\\n\\nWhen 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.\\n\\nsc_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.\\n\\n{{Certification Table Entry}} and {{albumchart}} should have identical problems.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377819444, 'spacePHID': None, 'dateCreated': 1375473900, 'dateModified': 1377862353, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52478', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: if the title page starts with a dot, VE won't load\", 'description': {'raw': 'http://en.wikipedia.org/wiki/.tl for instance,\\nif you click on the Edit tab, nothing will happen.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375464734, 'spacePHID': None, 'dateCreated': 1375462920, 'dateModified': 1375464734, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52467', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar not returning under the tabs', 'description': {'raw': 'Toolbar mixed with #p-personal\\n\\nSee the image. And I got the opposite, the toolbar staying at top of the article.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52504\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52326\\n\\n**Attached**: {F11123}'}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375991502, 'spacePHID': None, 'dateCreated': 1375403700, 'dateModified': 1417571050, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52433', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: {{clr}} prevents user from editing content', 'description': {'raw': '1. 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 <td>.\\n\\nOf 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395360523, 'spacePHID': None, 'dateCreated': 1375401360, 'dateModified': 1429479438, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52431', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link suggestions sometimes too foreceful, can't select the target you want.\", 'description': {'raw': '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.\\n\\nSteps 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375391536, 'spacePHID': None, 'dateCreated': 1375391460, 'dateModified': 1417571051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52421', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Undoing a larger cut restores selection incorrectly', 'description': {'raw': '- Chrome 30 (canary)\\n- https://en.wikipedia.org/w/index.php?title=Narayana_Gosain_Temple&oldid=565414421&veaction=edit\\n\\n\\nWhen selecting the following:\\n\\n> <selected>\\n> h2.Transport\\n> p.It is situated within 20km from NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar.\\n> h2.References\\n> references.\\n> \\\\n\\n> </selected>\\n> \\\\n\\n> h2.External links\\n\\n.. and cutting it, and then ctrl-Z. It restores both content and selection properly \\n\\n\\n\\nWhen selecting the following:\\n\\n> \\n> h2.Transport\\n> p.It is situated within 20km from <selected>NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar.\\n> h2.References\\n> references.\\n> \\\\n\\n> \\\\n\\n> h2.External</selected> links\\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\\n> \\n> h2.Transport\\n> p.It is situated within 20km from <selected>NH5 running between Chennai and Howrah. Nearest railhead is Jajpur Keonjhar Road or Byasanagar.</selected>\\n> h2.References\\n> references.\\n> \\\\n\\n> \\\\n\\n> h2.External links\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385398843, 'spacePHID': None, 'dateCreated': 1375381560, 'dateModified': 1417048880, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52410', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Stray bullet points around template and strange editing around them', 'description': {'raw': \"Screenshot: 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.\\n\\n\\n2) 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.\\n\\n\\n[1]  https://sv.wikipedia.org/w/index.php?title=Byrackorna&oldid=22981861\\n[2]  https://sv.wikipedia.org/wiki/Mall:IMDb-titel\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/User:Skalman/bullet_point_test\\n\\n**Attached**: {F11912}\"}, 'authorPHID': 'PHID-USER-pwsgofaoir7tnszvfzqi', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xqqqgn2dels45flxw5kb', 'dateClosed': 1468195329, 'spacePHID': None, 'dateCreated': 1375345320, 'dateModified': 1468195329, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52374', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'drag and drop for text', 'description': {'raw': 'Request to introduce drag and drop for text passages; there are also bugs for images around (obviously).\\n\\nReport:\\n\\nhttp://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121095343#Drag_.26_Drop_von_Textabschnitten\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375319436, 'spacePHID': None, 'dateCreated': 1375319220, 'dateModified': 1417570924, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52364', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Contents of pre-existing transclusion saved to article adjacent to transclusion', 'description': {'raw': 'https://pl.wikipedia.org/w/index.php?title=Octan_etylu&curid=217010&diff=37144425&oldid=37144363\\n\\nThis\\xa0may be a template that got subst\\'d in VisualEditor.  It produces this text:\\n\\n <div class=\"do-not-make-smaller refsection references-column-count references-1column\">\\n <references />\\n </div>\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393528114, 'spacePHID': None, 'dateCreated': 1375232040, 'dateModified': 1393528114, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52307', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing surface displays non-existent spaces after bullet points in Thai Wikipedia', 'description': {'raw': 'Image 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.\\n\\nDuplicated in FF, Chrome.  Ubuntu, OS 10.6.8\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11736}'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415880871, 'spacePHID': None, 'dateCreated': 1375213740, 'dateModified': 1666434962, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52291', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Following links in image captions that have a large <font size=> value takes over media settings dialog which can't then be closed\", 'description': {'raw': \"link target takes over media settings dialog\\n\\nIf text has a size specified, e.g <font size=12>, 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. <font size=12>text with a [[link]]</font>.\\n\\nIf 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.\\n\\nIf 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11727}\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385396898, 'spacePHID': None, 'dateCreated': 1375209840, 'dateModified': 1417571005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52285', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor should be themeable by the user with custom CSS', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384864881, 'spacePHID': None, 'dateCreated': 1375182720, 'dateModified': 1384945365, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52270', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: References not saved', 'description': {'raw': 'References 5-8 were not saved\\n\\nAt 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.\\n\\nThe 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n\\n**Attached**: {F11698}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376325366, 'spacePHID': None, 'dateCreated': 1375179540, 'dateModified': 1376325366, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52269', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid or VisualEditor: nowiki added around space following HTML comment', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375199871, 'spacePHID': None, 'dateCreated': 1375176300, 'dateModified': 1375199871, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52266', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikitext insertion warning needs to be more visible', 'description': {'raw': 'The wikitext insertion warning now works, and is visible regardless of the position of the user on the page.\\n\\nHowever, its color scheme is the same as other regular, confirmation-type notifications like \"you\\'ve added this page to your watchlist\".\\n\\nWikitext 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385396737, 'spacePHID': None, 'dateCreated': 1375169040, 'dateModified': 1417571003, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52264', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Recognise Labeled Section Transclusions as mw:Extension/Lst or similar in Parsoid', 'description': {'raw': 'Labeled Section Transclusion (<section begin=\"2012-07-monthly\"/>Text here<section end=\"2012-07-monthly\"/>) 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376428165, 'spacePHID': None, 'dateCreated': 1375142220, 'dateModified': 1376428165, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52252', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link input widget should not show \"New: (redlink)\" when a redirect exists by that name', 'description': {'raw': 'Screenshot of problem\\n\\nSee screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11666}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376073139, 'spacePHID': None, 'dateCreated': 1375142160, 'dateModified': 1417571049, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52251', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add guidance message into the reference dialog to tell a user what to put there', 'description': {'raw': '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. \\n\\nSome 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.\"\\n\\nThe message could be specified by a page in the MediaWiki: namespace.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375141752, 'spacePHID': None, 'dateCreated': 1375138020, 'dateModified': 1417571053, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52250', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide a way for the Behavior switches magic words to be inserted.', 'description': {'raw': \"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.\\n\\nBug 49996 and Bug 50855 also address magic words, but don't seem to cover the Behavior switches.\\n\\nThis was discussed at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Some_ideas_for_29_July\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385384185, 'spacePHID': None, 'dateCreated': 1375136040, 'dateModified': 1417571010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52248', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: template substituted in', 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=Cruz_Azul&diff=564888460&oldid=564725284 - very strange.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385395969, 'spacePHID': None, 'dateCreated': 1375130640, 'dateModified': 1385395969, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52242', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'inserting media into tables', 'description': {'raw': '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.\\n\\nTable:\\n\\nhttp://de.wikipedia.org/wiki/Prozessorsockel#Intel\\n\\nImage:\\n\\nhttp://commons.wikimedia.org/wiki/File:Intel_Socket_1150_IMGP8593_smial_wp.jpg\\n\\nThe file fails to show up, if you put its name in manually once you reach \"5\"\\n\\nReport:\\n\\nhttp://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121004381#Bildeinbindung\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383282089, 'spacePHID': None, 'dateCreated': 1375105920, 'dateModified': 1383282089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52218', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'reference clipboard errors', 'description': {'raw': \"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. \\n\\nIf 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.\\n\\nIf 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.\\n\\nIf one selects a sign to the right and to the left of the reference, it works.\\n\\nReport: http://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=120995561#Einzelnachweise_in_der_Zwischenablage\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375134084, 'spacePHID': None, 'dateCreated': 1375088700, 'dateModified': 1417570923, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52212', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar should fit on landscape iPad (and average non-maximised windows in general)', 'description': {'raw': 'Screenshot 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.\\n\\nWhen at 1281px, the width of just the toolbar (subtracted the mw sidebar) is 1103px.\\n\\nSo, a lot to cut down on. Any ideas?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11563}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380221526, 'spacePHID': None, 'dateCreated': 1375057440, 'dateModified': 1417571042, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52205', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Uncaught TypeError: Cannot read property \\'params\\' of undefined \\'content\\'\"', 'description': {'raw': 'Per http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Content_transclusion_causes_WTF_mode\\n\\nIf trying to add a template, only adding content (empty) and click apply, following error is thrown:\\n\\nTypeError: content is undefined\\nhttp://bits.wikimedia.org/static-1.22wmf11/extensions/VisualEditor/modules/ve-mw/dm/nodes/ve.dm.MWTransclusionNode.js\\nLine 192\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384198086, 'spacePHID': None, 'dateCreated': 1375037280, 'dateModified': 1417571019, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52198', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor doesn't confirm closing window\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ea6gwat27oulytc5tvsy', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390417310, 'spacePHID': None, 'dateCreated': 1374988380, 'dateModified': 1417570957, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52169', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Wikitext markup detected\" message should disappear automatically when there\\'s no more wikitext', 'description': {'raw': '\"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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375381691, 'spacePHID': None, 'dateCreated': 1374947400, 'dateModified': 1417571051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52155', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor - Using \"Select all\" (Ctrl+a) and deleting the selected content afterwards leaves the document uneditable.', 'description': {'raw': 'Tested on Firefox 22, Monobook and Vector skin. DOES NOT seem to affect Chrome 28 on Vector.\\n\\nSteps to reproduce:\\n- Open the [[Olive Branch High School]] in the visual editor.\\n- Press CTRL+A to select everything on the page.\\n- Press Delete.\\n\\nThe 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). \\n- 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<p data-parsoid=\"{&quot;dsr&quot;:[0,45,0,0]}\" class=\"ve-ce-branchNode\">\\n<span class=\"ve-ce-branchNode-slug ve-ce-branchNode-inlineSlug\">&#65279;</span></p>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375199198, 'spacePHID': None, 'dateCreated': 1374877260, 'dateModified': 1375199198, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52125', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor or Parsoid: Breaks and partially duplicates html tag', 'description': {'raw': '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 <br clear=all> was duplicated minus the leading <\\n\\nPossibly related to bug 51304?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379848985, 'spacePHID': None, 'dateCreated': 1374877200, 'dateModified': 1417571043, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52124', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor - EditIntro is incorrectly linked in the monobook skin.', 'description': {'raw': '(Tested on Firefox 22)\\n\\nIt seems that the \"&editintro=Template:BLP_editintro\" URL is accidentally reversed on Monobook. \\n\\nSteps to reproduce:\\n(Vector - Working correctly)\\n- Navigate to [[Martin J. Silverstein]].\\n-- The \"Edit\" link will be: https://en.wikipedia.org/wiki/Martin_J._Silverstein?veaction=edit\\n-- The \"Edit Source\" link will be: https://en.wikipedia.org/w/index.php?title=Martin_J._Silverstein&action=edit&editintro=Template:BLP_editintro\\n\\n(Monobook - Working incorrectly)\\n- Navigate to [[Martin J. Silverstein]].\\n-- The \"Edit\" link will be: https://en.wikipedia.org/wiki/Martin_J._Silverstein?veaction=edit&editintro=Template:BLP_editintro\\n-- The \"Edit Source\" link will be: https://en.wikipedia.org/w/index.php?title=Martin_J._Silverstein&action=edit\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385398255, 'spacePHID': None, 'dateCreated': 1374873360, 'dateModified': 1385398255, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52116', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: image followed immediately with wikilink causes dirty diff', 'description': {'raw': '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\\n\\nReproduced 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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379847739, 'spacePHID': None, 'dateCreated': 1374862080, 'dateModified': 1379847739, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52107', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Missing nowiki escaping when single quotes wrap new i/b tags', 'description': {'raw': 'Reported at: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Link_formatting_trick\\n\\nSimplified test cases here:\\n\\n[subbu@earth lib] echo \"[[Foo|\\'foo\\']]\" | node parse | sed \"s/foo/<i>foo<\\\\/i>/g;\" | node parse --html2wt\\n[[Foo|\\'\\'\\'foo\\'\\'\\']]\\n\\n[subbu@earth lib] echo \"[[Foo|\\'foo\\']]\" | node parse | sed \"s/foo/<b>foo<\\\\/b>/g;\" | node parse --html2wt\\n[[Foo|\\'\\'\\'\\'foo\\'\\'\\'\\']]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375305913, 'spacePHID': None, 'dateCreated': 1374857700, 'dateModified': 1375305913, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52103', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'User preference to disable VisualEditor (VE product)', 'description': {'raw': '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.\\n\\nThis 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.\\n\\nTo 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.\\n\\nIn 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).\\n\\nI 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 ).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50929'}, 'authorPHID': 'PHID-USER-2nopae2cxuamwcbndaih', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385396429, 'spacePHID': None, 'dateCreated': 1374837420, 'dateModified': 1385996565, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52086', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: References that are added by templates are not recognized by the references tool', 'description': {'raw': 'I saw bugs that are similar to this one, for example Bug 51289, but nothing exactly like this one.\\n\\nReferences 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 <ref> tag, but about template that add the <ref> tag itself (with {{#tag:ref}}).\\n\\nThis 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 <ref> is very hard to edit. This means that most of the references there are not usable for reusing in the \"Use an existing reference\".\\n\\n(This also means a bunch of other things, but I\\'ll report them separately.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374880234, 'spacePHID': None, 'dateCreated': 1374825720, 'dateModified': 1417571054, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52083', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Wrong tab-order on the \"Edit summary\" window', 'description': {'raw': 'A5b 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 <nowiki><Tab></nowiki> 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. \\n\\nIs 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\".\\n\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback#Wrong tab-order on the \"Edit summary\" window\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374818679, 'spacePHID': None, 'dateCreated': 1374817380, 'dateModified': 1417571054, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52080', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: only a part of word is linked and <nowiki/> is added', 'description': {'raw': 'When I select text that ends in the middle of the word and add a link, only the selected part is linked. Also, <nowiki/> is added after the link.\\n\\nFor 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 :)\\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.\\n\\nThis may be related to Bug 50127, though the description is not the same.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374797030, 'spacePHID': None, 'dateCreated': 1374778680, 'dateModified': 1530031685, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52044', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: blanking a page doesn't remove comments\", 'description': {'raw': '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\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60830'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393271493, 'spacePHID': None, 'dateCreated': 1374770400, 'dateModified': 1406199049, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52036', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: No easy way to add content before a template at the start of a line', 'description': {'raw': '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.\\n\\nThis is a problem if your workflow is to add the stub template before adding the external links, which is entirely reasonable.\\n\\nSteps to reproduce (option 1): \\n1. create page with references and a reflist.\\n2. 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).\\n\\nSteps to reproduce (option 2):\\n1. 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 )\\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).\\n\\nThere 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.\\n\\nDesired 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52620'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395357259, 'spacePHID': None, 'dateCreated': 1374765240, 'dateModified': 1417048877, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52032', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData should allow specifying default values for parameters', 'description': {'raw': 'TemplateData should allow some parameters to have default values which are prefilled when using the VisualEditor transclusion manager. \\n\\nAn example would be the current date for accessdate in citation templates.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375183466, 'spacePHID': None, 'dateCreated': 1374763800, 'dateModified': 1377900567, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52028', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When use Firefox to edit a section of an article, the VisualEditor ends up incorrect position', 'description': {'raw': '**Author:** `lovefilms`\\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, \\nhttps://en.wikipedia.org/wiki/Blue_Jasmine#Production\\nthe 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. \\n\\nAlso, 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Windows 7\\n**Platform**: PC\\n\\n**Attached**: {F11047}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377190936, 'spacePHID': None, 'dateCreated': 1374709260, 'dateModified': 1438111552, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51998', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"add template\" should have the same functionality as return in the template dialog', 'description': {'raw': \"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!\\n\\nHitting '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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385395164, 'spacePHID': None, 'dateCreated': 1374697260, 'dateModified': 1417571006, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51989', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Impossible to edit a specific section when switching from VisualEditor to \"legacy mode\" (due to reference to QuickEdit gadget in vector.js?)', 'description': {'raw': '**Author:** `l736ewiki`\\n\\n**Description:**\\nI\\'m an user on it.wiki, where VisualEditor is now enabled by default on the whole ns0.\\n\\nI 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).\\n\\n\\nVisualEditor 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.\\n\\nThis is heavily annoying when dealing with very long articles, with plenty of sections.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Mac OS X 10.8\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376324056, 'spacePHID': None, 'dateCreated': 1374686580, 'dateModified': 1376382078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51976', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: can't remove missing image\", 'description': {'raw': 'http://it.wikipedia.org/w/index.php?title=Pieve_di_San_Giovanni_Battista_%28Pieve_Fosciana%29&oldid=60196986\\n\\nIf you tried to edit with VE, the missing image link would just disappear.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377623981, 'spacePHID': None, 'dateCreated': 1374684900, 'dateModified': 1377623981, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51968', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor or Parsoid tried to convert slash-separate numbers into <a href=tel:> and refused to save', 'description': {'raw': 'An 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.\"\\n\\ninto \\n\\n:<nowiki>...in common with the Classes <a href=tel:313 / 314 / 315\">313 / 314 / 315</a> / 507 / 508 units.</nowiki>\\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.\"\\n\\nI have been unable to reproduce this using Firefox 22 on Linux, including editing the article in question.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53315'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374680186, 'spacePHID': None, 'dateCreated': 1374669600, 'dateModified': 1417571047, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51959', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <nowiki> tags not deleted when surrounding element or text is deleted', 'description': {'raw': 'User Atethnekos at en.wp reports:\\n\"If in the source code there is <<nowwiki/>blockquote>, and in VE I select \"<blockquote>\" and delete it, when I save the <nowiki/> is left behind in the source code.\" \\n\\nSee 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:\\nhttps://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox2&diff=565596772&oldid=565596703\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374879593, 'spacePHID': None, 'dateCreated': 1374661620, 'dateModified': 1417048887, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51950', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting last use of reference should remove the entry from <references>..</references>', 'description': {'raw': 'This is related to Bug 51741, which is about adding support for <references>...</references>\\n\\nIf the page already has <references>..</references>, and the last use of a named reference is removed, the entry inside <references>..</references> needs to be removed otherwise an error is generated after save.\\n\\nSteps to reproduce:\\n1. https://de.wikipedia.org/wiki/This_Is_War?veaction=edit\\n2. Delete one of the named references, e.g. [16] at present\\n3. Save & Review your changes.\\n\\nExpected results:\\nThe reference is removed from the content and the references list.\\n\\nActual results:\\nThe reference is removed from the content, but it remains in the references list, and if saved the error is:\\n\"Cite error: <ref> tag with name \"rockspot_1\" defined in <references> is not used in prior text.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385395008, 'spacePHID': None, 'dateCreated': 1374657660, 'dateModified': 1417571006, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51938', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Retain newlines between parameters in transclusion invocations', 'description': {'raw': \"Steps to reproduce:\\n1. https://nl.wikipedia.org/wiki/Dolichognatha_petiti?veaction=edit\\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\\nhttp://parsoid.wmflabs.org:8001/topfails/15\\n\\nRegarding the actual bug, I saw a similar diff ~20 hrs ago:\\nhttps://en.wikipedia.org/w/index.php?title=List_of_Sam_%26_Cat_episodes&curid=39469556&diff=565437324&oldid=565416618\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385397595, 'spacePHID': None, 'dateCreated': 1374642420, 'dateModified': 1417571005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51925', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: DEFAULTSORT suggestions should use/not use diacritics on based on wiki policy', 'description': {'raw': 'English 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\".\"\\n\\nLooking 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385382898, 'spacePHID': None, 'dateCreated': 1374609540, 'dateModified': 1417571011, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51907', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting media dialog has no confirmation button', 'description': {'raw': '**Author:** `jduranboger`\\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.\\n\\nAttached:Screenshot\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows 7\\n**Platform**: PC\\n\\n**Attached**: {F11730}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389677471, 'spacePHID': None, 'dateCreated': 1374608640, 'dateModified': 1424894574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51905', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dragging cursor through multi-part template responds unpredictably in Firefox', 'description': {'raw': 'A 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.\\n\\nOccurs 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'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385394193, 'spacePHID': None, 'dateCreated': 1374588720, 'dateModified': 1417048880, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51880', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'General non VE feedback goes to the VE feedback page.', 'description': {'raw': '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:\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390607728, 'spacePHID': None, 'dateCreated': 1374583260, 'dateModified': 1390607728, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51875', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Share VisualEditor and Parsoid puppet module between Vagrant and Wikimedia Labs', 'description': {'raw': '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).\\n\\nThis is a proof of concept for doing this more broadly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54160'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408666032, 'spacePHID': None, 'dateCreated': 1374573300, 'dateModified': 1424912168, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51858', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Changing login status / losing session data during edit causes VE to break silently', 'description': {'raw': 'Edits that would trigger this error silently break VE:\\n\"Sorry! We could not process your edit due to a loss of session data.\"\\n\\nOn 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.\\n\\nTo 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fgzcdbj3je3ksnhufo47', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385395314, 'spacePHID': None, 'dateCreated': 1374524640, 'dateModified': 1417571005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51835', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'FlaggedRevs/PendingChanges notices not appearing at pl.wikipedia.org', 'description': {'raw': 'From https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Krytyczne_zaniedbanie_interfejsu:_wersje_przejrzane\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374645680, 'spacePHID': None, 'dateCreated': 1374518520, 'dateModified': 1374645680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51833', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Long lines in <pre> blocks don't cause page formatting to extend right. The html page is extended massively further than needed\", 'description': {'raw': 'Long <pre> blocks rendered in Firefox 22 on Xubuntu Linux. Monobook skin.\\n\\nWhen <pre> blocks contain lines longer than the width of the page, the <pre> 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).\\n\\nExample page: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=565361164#save_page\\n\\nFirefox 22, Xubuntu Linux, Monobook skin.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11594}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374526756, 'spacePHID': None, 'dateCreated': 1374516900, 'dateModified': 1374526756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51831', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Removing a heading is hard, leaving ==<nowiki/>== or turning the next paragraph into a heading', 'description': {'raw': '1. Visit any page on Wikipedia today.\\n2. Click \"Edit\" to enter VisualEditor.\\n3. Find a section heading and highlight it.\\n4. Press the DEL key on your keyboard to delete it.\\n5. Click \"Save Page\" then \"Review your changes.\"\\n\\nThe heading text has been removed, but the following wikitext has been left in its place.\\n\\n==<nowiki/>==\\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.\\n\\nSo 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.\\n\\nI 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.\\n\\nIn 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-o5tv5cyrple4fn5xqopm', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374609807, 'spacePHID': None, 'dateCreated': 1374514920, 'dateModified': 1374609807, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51829', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tooltip shown when hovering over a link should also appear when link inspector icon is shown', 'description': {'raw': '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).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51824'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385392185, 'spacePHID': None, 'dateCreated': 1374512940, 'dateModified': 1417571007, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51827', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor renderizes the image a lot bigger than it should', 'description': {'raw': 'Screenshot from [[pt:TV TEM]]\\n\\nIn the page\\nhttps://pt.wikipedia.org/wiki/User:Helder.wiki/Testes?veaction=edit\\nthe image is a lot bigger than it is on view mode\\nhttps://pt.wikipedia.org/wiki/User:Helder.wiki/Testes?action=edit&oldid=36476193&preview=yes\\n\\n\\nThis is a minimal example for the problem reported at\\nhttps://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia%3AEditor_Visual%2FComent%C3%A1rios&diff=36476052&oldid=36474378#Logo_desproporcional\\nwhich can be seen on this article:\\nhttps://pt.wikipedia.org/wiki/TV_TEM?veaction=edit#footer\\nThe screenshot provided was this:\\nhttp://s22.postimg.org/owzuay0jl/image.jpg\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://pt.wikipedia.org/wiki/?oldid=36476128&veaction=edit\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51628\\n\\n**Attached**: {F11577}'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374548109, 'spacePHID': None, 'dateCreated': 1374512940, 'dateModified': 1417571073, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51826', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When window is narrowed, article title can display over the top of the toolbar', 'description': {'raw': 'From 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.\\n\\nOn 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.\\n\\nAnd 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.\\n\\nI\\'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.\"\\n\\n\\nSee images:\\n*http://en.wikipedia.org/wiki/File:Screenshot_of_title_overlapping_border.jpg\\n\\n*http://en.wikipedia.org/wiki/File:Screenshot_of_truncated_title_word_in_narrow_window.jpg\\n\\nOriginal thread here:\\nhttp://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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52187\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51867'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394477948, 'spacePHID': None, 'dateCreated': 1374511320, 'dateModified': 1417570928, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51820', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Transclusion editor: remove template creates blank dialog', 'description': {'raw': \"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.\\n\\nSteps 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\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374702151, 'spacePHID': None, 'dateCreated': 1374498600, 'dateModified': 1417571072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51812', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor shows rowspan=\"4\" on template generated tables', 'description': {'raw': 'Screenshot of the table\\n\\nSee the link above and the attached screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://pt.wikipedia.org/wiki/La_Liga_de_2006%E2%80%9307?oldid=36362539&veaction=edit\\n\\n**Attached**: {F11541}'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375726508, 'spacePHID': None, 'dateCreated': 1374495480, 'dateModified': 1375726508, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51806', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: It's possible to edit pages that were translated using the Translate extension\", 'description': {'raw': \"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.\\n\\nI'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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374854170, 'spacePHID': None, 'dateCreated': 1374495000, 'dateModified': 1417570956, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51805', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE: Page settings: Languages list cut off', 'description': {'raw': '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\\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}'}, 'authorPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'ownerPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374489509, 'spacePHID': None, 'dateCreated': 1374481140, 'dateModified': 1417571073, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51793', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData for redirected templates', 'description': {'raw': 'Many templates are redirects from a short name to a long name. An example is\\nhttp://en.wikipedia.org/wiki/Template:Commons_cat which is a redirect to\\nhttp://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. \\n\\nThere should be a way of making the dialog work for redirecting templates without having to duplicate the documentation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374641783, 'spacePHID': None, 'dateCreated': 1374470760, 'dateModified': 1417571072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51791', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Search box and button intermittently appearing atop transclusion editor in Monobook skin', 'description': {'raw': 'Reported 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.\\n\\nOccurs in Firefox v21.0, cannot replicate in Chrome v28.0\"\\n\\nSee image:\\nhttp://en.wikipedia.org/wiki/File:VE_Searchbox_Passthrough.jpg\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385392734, 'spacePHID': None, 'dateCreated': 1374415800, 'dateModified': 1417571007, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51771', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Uncaught TypeError: Cannot read property \\'info\\' of undefined\" (when saving the page)', 'description': {'raw': '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. \\n\\nHere 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wlku5ja6envbi4cz2etp', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395355910, 'spacePHID': None, 'dateCreated': 1374349320, 'dateModified': 1417570925, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51759', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make it clearer that the clear formatting button does something (clears pre-annotations) if any are set', 'description': {'raw': '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.\\n\\nEither 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395356968, 'spacePHID': None, 'dateCreated': 1374343560, 'dateModified': 1417048877, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51756', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In a page with many categories only the first categories are visible in the editor', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385391924, 'spacePHID': None, 'dateCreated': 1374334080, 'dateModified': 1417571008, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51752', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Removal of blank lines when there are HTML comments seems not to work', 'description': {'raw': 'As reported on the Swedish feedback page:\\nhttp://sv.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2F%C3%85terkoppling&diff=22695791&oldid=22693792\\n\\nWhen there are blank lines before and after HTML comments, it seems like it is not possible to remove all of them. \\n\\nIdeally it should pe bossible to edit this version:\\n\\nhttp://sv.wikipedia.org/w/index.php?title=Abrostola_major&oldid=21896423\\n\\nin a way that it gets like this:\\n\\nhttp://sv.wikipedia.org/w/index.php?title=Abrostola_major&diff=22695707&oldid=21896423\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390416862, 'spacePHID': None, 'dateCreated': 1374306840, 'dateModified': 1390416862, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51732', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Incorrect URL used for magic RFC links', 'description': {'raw': \"js/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 .\\n\\nI spotted this when looking at Firebug's HTML tab while VisualEditor was\\nopen on https://en.wikipedia.org/wiki/MD4#Security .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-3ampiwske4lc434cm6ot', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374508114, 'spacePHID': None, 'dateCreated': 1374285720, 'dateModified': 1374508114, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51726', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: add new categories after old categories', 'description': {'raw': '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\".\\n\\nWhat 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377833797, 'spacePHID': None, 'dateCreated': 1374267420, 'dateModified': 1417571045, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51714', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Rearranging transclusions breaks the ability to select parameters.', 'description': {'raw': '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.\\n\\nSteps to reproduce:\\n- Open any random page in the visual Editor.\\n- Open the \"Transclusion\" window. Select the \"Cite web\" template and click the \"Add template\" button. It should be added with two default parameters.\\n- Click the + icon in the bottom left of the Transclusion dialog, and click the button to add another template.\\n- Add another \"Cite web\" template as described in step 2. Again it should come with two default parameters.\\n\\nRight now you should have a transclusion window containing two cite web templates.\\n\\n- Click the bottom template, and press the ^ icon to move that template to the top of the list. \\n- 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. \\n- 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.\\n\\nTested on Firefox 22 and Chrome 28 on Windows 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385392298, 'spacePHID': None, 'dateCreated': 1374229860, 'dateModified': 1417571007, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51674', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Relabel buttons in \"cancel editing\" confirmation dialog', 'description': {'raw': '**Author:** `ignatzmice.wiki`\\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?\\n\\nOriginal 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374267909, 'spacePHID': None, 'dateCreated': 1374203640, 'dateModified': 1417571074, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51655', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Double-clicking inside edit surface sometimes causes uncaught JS \"offset could not be translated\" errors', 'description': {'raw': 'Steps to reproduce:\\n\\n1) Open https://en.wikipedia.org/wiki/Jam,_Iran?veaction=edit\\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'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385392053, 'spacePHID': None, 'dateCreated': 1374199860, 'dateModified': 1385392053, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51653', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Leave Feedback\" link greyed out; might confuse users', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385386362, 'spacePHID': None, 'dateCreated': 1374162180, 'dateModified': 1417571009, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51619', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Leave Feedback\" link rendering as two lines in some fonts', 'description': {'raw': '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 ;-)\"\\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?\"\\n\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=564802026#Follow-up\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374162111, 'spacePHID': None, 'dateCreated': 1374162000, 'dateModified': 1374162111, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51618', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image is not displayed on Visual Editor', 'description': {'raw': 'The image from [1] and is not rendered on VisualEditor [2].\\n\\n[1] https://pt.wikipedia.org/w/index.php?oldid=36419116\\n[2] https://pt.wikipedia.org/w/index.php?oldid=36419116&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51248'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395354371, 'spacePHID': None, 'dateCreated': 1374088140, 'dateModified': 1417570926, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51567', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <nowiki> tags added to all markup in paragraph, including pre-existing', 'description': {'raw': \"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 <nowiki> tags around it (correct according to apparent design, incorrect according to desired behaviour). \\n\\nHowever, it also added <nowiki> 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.\\n\\nBug 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375199816, 'spacePHID': None, 'dateCreated': 1374081420, 'dateModified': 1375199816, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51554', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Can't save\", 'description': {'raw': 'Using 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] https://www.mediawiki.org/wiki/VisualEditor/Portal/sv\\n[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\\n[3] {\"servedby\":\"mw1203\",\"error\":{\"code\":\"unknownerror\",\"info\":\"Unknown error: \\\\\"tpt-target-page\\\\\"\"}}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-pwsgofaoir7tnszvfzqi', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374071458, 'spacePHID': None, 'dateCreated': 1374070440, 'dateModified': 1374071458, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51534', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Visual Editor: Adding text after a link includes that text in the link', 'description': {'raw': \"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).\\n\\nThere 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.\\n\\nThis is not usually a problem, as you can work around by starting from after the space after the link.\\n\\nHowever, 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374679397, 'spacePHID': None, 'dateCreated': 1374065040, 'dateModified': 1417048888, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51531', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Tab key moves focus between citations; doesn't indent text as expected\", 'description': {'raw': '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.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395359458, 'spacePHID': None, 'dateCreated': 1374064500, 'dateModified': 1417048876, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51530', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Inserting whitespace in front of a paragraph shouldn't convert the paragraph to a preformatted block, but also shouldn't leave unneeded <nowiki>s\", 'description': {'raw': 'On 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.\\n*Saved. VE adds nowiki tags before the whitespace and after the first few words. Text displays without indent.\\n*Tried removing the whitespace in VE.\\n*VE won\\'t allow the whitespace to be removed, but instead will only permit the first few words to be deleted.\\nThis 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.\\n*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\\n\\n*It turned the first word into an uneditable element. See image: http://en.wikipedia.org/wiki/File:VEspaceremoval.png \\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.\" http://en.wikipedia.org/w/index.php?title=Marloth_Park&diff=564487138&oldid=557816381\\n\\n* It allowed me to remove the space in VE.\\n\\n\\n(Also using Chrome on 7.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385386267, 'spacePHID': None, 'dateCreated': 1374063600, 'dateModified': 1417571010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51528', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'update.php does not give any response.', 'description': {'raw': '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.\\n\\nexample: \\n [root@moegirl maintenance]# php  update.php\\n [root@moegirl maintenance]# \\nI tried other smaller site, it react like this:\\n<pre>\\nMediaWiki 1.22wmf9 Updater\\n\\nGoing to run database updates for enwiki\\nDepending on the size of your database this may take a while!\\nAbort with control-c in the next five seconds (skip this countdown with --quick)\\n ... 0\\n[root@moegirl maintenance]#\\n</pre>\\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.\\n\\nAnyone had ever meet same problem? Is this a new bug? How to solve it?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qrnoqj2szt6knvcqvaxt', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374051736, 'spacePHID': None, 'dateCreated': 1374048060, 'dateModified': 1374051736, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51514', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '&veaction= as a second parameter works on enwiki but not zhwiki', 'description': {'raw': \"Dunno why but:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Fish&veaction=edit loads VE-edit mode\\n\\nhttps://zh.wikipedia.org/w/index.php?title=%E9%B1%BC&veaction=edit doesn't.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382132030, 'spacePHID': None, 'dateCreated': 1374012540, 'dateModified': 1417571039, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51481', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Rearranging, removing, or reorganizing sections, then saving the page, causes the Table of Contents to link to 'Edit' instead of the section\", 'description': {'raw': 'From http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#How_did_it_go_to_Vedit_mode.3F\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows 7'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385374579, 'spacePHID': None, 'dateCreated': 1373999220, 'dateModified': 1385374579, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51456', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Wrong reference subnumbering used for some wikis', 'description': {'raw': 'Screenshot\\n\\nMultiple uses of a references are shown in the reference list:\\n\\nDefault: is \"1.0 1.1 1.2 1.3\" etc.\\n\\nSome wikis, like dewiki, uses \"a b c\" etc. \\n\\n\\nVE rendering always use the default.\\n\\nThis 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}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379788309, 'spacePHID': None, 'dateCreated': 1373997420, 'dateModified': 1379789381, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51453', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Category adding interface is hard to find', 'description': {'raw': \"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?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374010099, 'spacePHID': None, 'dateCreated': 1373996400, 'dateModified': 1417571075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Uncaught TypeError: Cannot read property \\'end\\' of null\"', 'description': {'raw': \"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.\\n\\n\\n> Uncaught TypeError: Cannot read property 'end' of null\\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\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385386303, 'spacePHID': None, 'dateCreated': 1373983800, 'dateModified': 1385386303, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51440', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector should make it easier to change the label', 'description': {'raw': '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.\\n\\n\\n1) 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.\\n\\nNow 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?).\\n\\nHowever 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.\\n\\n2) 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\\n > Some <a>link</a>\\n Select link (has to be done manually (tedious and error prone) \\n > Some [selection]<a>link</a>[/selection]\"\\n Type \"hello\".\\n > Some <a>h</a>ello.\\n\\nwtf?\\n\\n\\nThough 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 \"<a>first char</a>other chars\" case.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48463'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1433344273, 'spacePHID': None, 'dateCreated': 1373981640, 'dateModified': 1456047619, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51438', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Syndicated feeds of Watchlists include non-existent edits', 'description': {'raw': 'XML 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11634}'}, 'authorPHID': 'PHID-USER-34ciubbmtvmsgh53t6hb', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395065589, 'spacePHID': None, 'dateCreated': 1373959140, 'dateModified': 1395227569, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51427', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Adding formatting to wiki link formats text not link', 'description': {'raw': \"See http://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=564459649#Italicizing_wikilinks\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-f6l3bchko2ogbi4poj24', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377278955, 'spacePHID': None, 'dateCreated': 1373950620, 'dateModified': 1377278955, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51422', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Blanking last section of page corrupts heading', 'description': {'raw': 'Reported here: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=564438586&oldid=564436653\\n\\nIP editor removes contents from last section of page.  VE replaces heading text with nowiki.\\n\\nDiff:https://en.wikipedia.org/w/index.php?title=Best:_The_Greatest_Hits_of_S_Club_7&curid=3428260&diff=564438205&oldid=564438086\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373938090, 'spacePHID': None, 'dateCreated': 1373937720, 'dateModified': 1417048888, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51417', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'color picker', 'description': {'raw': 'Copied 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\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=564427033#Color_picker\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376120681, 'spacePHID': None, 'dateCreated': 1373929020, 'dateModified': 1376120681, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51409', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Disabling VisualEditor completely', 'description': {'raw': '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)?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dswbdv7ibhsefllcqarz', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373926494, 'spacePHID': None, 'dateCreated': 1373917620, 'dateModified': 1373926494, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51389', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: spurious parentheses added', 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=Wormshill&diff=564367057&oldid=557770558 for example.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385386705, 'spacePHID': None, 'dateCreated': 1373900400, 'dateModified': 1385386705, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51369', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '504 timeout with Parsoid service', 'description': {'raw': '**Author:** `brunsa2`\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux\\n**Platform**: PC\\n**Whiteboard**: aklapper-moreinfo'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374456028, 'spacePHID': None, 'dateCreated': 1373899320, 'dateModified': 1374456028, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51366', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit this Page button ignores &oldid=prev parameter.', 'description': {'raw': '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.\\n\\nSteps to reproduce:\\n\\n* Navigate to http://en.wikipedia.org/w/index.php?title=Baylor_University_Institute_for_Oral_History&diff=540967084&oldid=prev\\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. \\n\\n(Tested on Firefox 22, Monobook skin. Possibly related:50615)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385387326, 'spacePHID': None, 'dateCreated': 1373895180, 'dateModified': 1417571008, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51364', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add ULS language setting dialogue box in VisualEditor page settings', 'description': {'raw': \"Hi,\\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\\nhttp://www.mediawiki.org/wiki/Talk:Universal_Language_Selector#feature_to_make_content_language_input__default_28864\\n\\n\\t\\n\\nThanks and Warm Regards\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378122078, 'spacePHID': None, 'dateCreated': 1373886720, 'dateModified': 1378122078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51356', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ULS input options visibility in VE with a drop down menu', 'description': {'raw': \"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.  \\n\\n\\n\\n*To understand further the need for above request,please do refer to survey\\ndata and analysis provided at\\nhttp://www.mediawiki.org/wiki/Talk:Universal_Language_Selector#feature_to_make_content_language_input__default_28864 \\n\\n\\nThanks and Warm Regards\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373968970, 'spacePHID': None, 'dateCreated': 1373885880, 'dateModified': 1373968970, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51354', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Automatically add title of the section to edit summary', 'description': {'raw': '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.\\n\\nRationale: 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.\\n\\n2. 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.\\n\\nPseudo-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).\\n2. Find the first headline above the last change (a line that starts with that character or before it and matches the pattern for headlines).\\n3. If this headline is before the first change, you found the section.\\n4. Else look for the next headline before it of higher level.\\n5. If there is such a headline, go to step 3, else more than one section was changed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-tyjmn7xcw6s2b6rqagj7', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373932279, 'spacePHID': None, 'dateCreated': 1373878680, 'dateModified': 1417571075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51343', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: double-clicking \"create reference\" generates a quasi-broken ref form.', 'description': {'raw': '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.\\n\\nWindows 7, Firefox 22.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11430}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385383559, 'spacePHID': None, 'dateCreated': 1373871600, 'dateModified': 1417571010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51341', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Applying a transclusion that only contains content brackets breaks the edit toolbar.', 'description': {'raw': '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.\\n(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.)\\n\\nI can confirm the same issue also occurs for me on Firefox 22, Monobook interface.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385383181, 'spacePHID': None, 'dateCreated': 1373869620, 'dateModified': 1417571011, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51340', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deletion of alienated content blocks can delete across (rather than deleting them)', 'description': {'raw': '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.\\n\\nSteps to reproduce\\n1. Go to a page with a gallery (https://en.wikipedia.org/wiki/Branford,_Florida?veaction=edit)\\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.\\nIn the case of [[Branford,_Florida]], the \"See also\" changes from being a section to being a piece of normal text placed above the gallery.\\n\\nHowever, 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385384432, 'spacePHID': None, 'dateCreated': 1373847540, 'dateModified': 1417048880, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51332', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow wikitext e.g. links to documentation in templatedata', 'description': {'raw': '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\\nhttp://en.wikipedia.org/wiki/Template:Taxobox/doc\\nas there are lots of subtitles in using the template.\\n\\nFurther there is also a need for links in some of the individual parameter. \\nFor 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.\\n\\nas 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. \\n\\nGood documentation requires sufficient detail, more than can be provided in one line. \\n\\nI\\'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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49772'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1452893140, 'spacePHID': None, 'dateCreated': 1373780340, 'dateModified': 1452893140, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51311', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: External link missing in template due to linkname with ampersand in it', 'description': {'raw': 'Here in VE, the {{Discogs master}} template usage at the bottom of the page in the external links does not render.\\n\\nEscaping 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\\n\\nSo possible entity escaping problem\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=Bossalinis_%26_Fooliyones&oldid=564034183'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385386971, 'spacePHID': None, 'dateCreated': 1373700600, 'dateModified': 1417571004, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51280', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Interface has elements untranslated in Spanish', 'description': {'raw': '**Author:** `jduranboger`\\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\".\\n\\nEn 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'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373652398, 'spacePHID': None, 'dateCreated': 1373649540, 'dateModified': 1417571076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51249', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Images disappear when the editor is loaded', 'description': {'raw': 'Compare\\n1) https://pt.wikipedia.org/wiki/?oldid=36380720&action=edit&preview=yes\\n2) https://pt.wikipedia.org/wiki/?oldid=36380720&veaction=edit\\n\\nThere are two images in the first case, but they disappear in the second case.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373646127, 'spacePHID': None, 'dateCreated': 1373645640, 'dateModified': 1373646127, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51244', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cut and Pasting a section that contains an image truncates all the sections formatting after pasting it.', 'description': {'raw': '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. \\n\\nThe 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.\\n\\nSteps to reproduce:\\n- Navigate to https://en.wikipedia.org/w/index.php?title=Microsoft&oldid=563598458 and edit the page with the visual editor.\\n- 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.\\n\\nThe text that is pasted will be stripped of all formatting, and the image that was selected will be gone as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374459959, 'spacePHID': None, 'dateCreated': 1373610900, 'dateModified': 1374459959, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51220', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Botfixup: VisualEditor shows 6 items in a list which for which MW only generates 2 items', 'description': {'raw': 'Compare the result of the wikitext\\n#1\\n#\\n#\\n#\\n#\\n#6\\nin the following URLs:\\n1) https://pt.wikipedia.org/wiki/?oldid=36373624&veaction=edit\\n2) https://pt.wikipedia.org/wiki/?oldid=36373624&action=edit&preview=yes\\n\\nVisual Editor show us a list with 6 elements, but MediaWiki will only display two items.\\n\\nMaybe this is related to Tidy?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373599184, 'spacePHID': None, 'dateCreated': 1373577600, 'dateModified': 1373599184, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51200', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Template rearranging itself', 'description': {'raw': 'Copied 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. [http://en.wikipedia.org/w/index.php?title=Defiance_%28TV_series%29&diff=563767420&oldid=563763824 Here] is what happened.\\n<br>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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390416930, 'spacePHID': None, 'dateCreated': 1373569320, 'dateModified': 1390416930, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51191', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Template editing within referencing is complex to the point of hampering usability', 'description': {'raw': 'See http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563842762#Reference_Issues:_Omnibus_Edition\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385382810, 'spacePHID': None, 'dateCreated': 1373566080, 'dateModified': 1385382810, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51188', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Design of the reference re-use pane is confusing, with a bold \"Use an existing source\" title that doesn\\'t look like one', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385380627, 'spacePHID': None, 'dateCreated': 1373562300, 'dateModified': 1417571013, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51183', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid does not add newlines between parameters in new template invocations, making wikitext difficult to read', 'description': {'raw': \"**Author:** `kwwilliams`\\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 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374271260, 'spacePHID': None, 'dateCreated': 1373555340, 'dateModified': 1438815462, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51175', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '<nowiki/> added to wikilinks', 'description': {'raw': '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. \\n\\nSee 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=33091'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373567309, 'spacePHID': None, 'dateCreated': 1373553780, 'dateModified': 1530031685, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51173', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: blanking an article and starting from scratch causes malformations', 'description': {'raw': 'The 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374079614, 'spacePHID': None, 'dateCreated': 1373546700, 'dateModified': 1374079614, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51169', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: easier parameter selection', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377527402, 'spacePHID': None, 'dateCreated': 1373538900, 'dateModified': 1417571047, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51165', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Category interface is hard to find', 'description': {'raw': 'Finding the categories under page setting is non intuitive. Adding another icon next to references would help usability.\\n\\nThis is discussed at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Icons_are_incomprehensible\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50239'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437698082, 'spacePHID': None, 'dateCreated': 1373509140, 'dateModified': 1437698082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51153', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Intermittently unable to open page settings after deleting and then adding a stub template', 'description': {'raw': '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.\\n\\nI 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.\\n6. Click the \"page settings\" button on the tool bar.\\n\\nIf 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. \\n\\nA 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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397677941, 'spacePHID': None, 'dateCreated': 1373485620, 'dateModified': 1417601785, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51134', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Auto-generated (bare) external links converted to external links to target null', 'description': {'raw': 'VisualEditor appears to be inserting \"null\" into external links occasionally.\\n\\nExamples:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Carrie_(musical)&curid=7695755&diff=563576490&oldid=563235599\\n\\nat [[Ithaca College]] in [[Ithaca, New York]] by the Macabre Theatre Ensemble,<ref>[null http:///www.icmacabre.blogspot.com]</ref>\\n\\n----\\n\\nhttps://en.wikipedia.org/w/index.php?title=Embarcadero_Delphi&curid=349208&diff=563574811&oldid=561383018\\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'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385382685, 'spacePHID': None, 'dateCreated': 1373484720, 'dateModified': 1417571012, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51132', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Removing template & Adding content breaks editor', 'description': {'raw': 'Copied 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.\\n\\nMaggie\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385387104, 'spacePHID': None, 'dateCreated': 1373481780, 'dateModified': 1417571008, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51130', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Review changes should show the edit summary, if one has been provided.', 'description': {'raw': \"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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373480869, 'spacePHID': None, 'dateCreated': 1373479140, 'dateModified': 1373480869, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51125', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Transcluded pages quasi-template eats into subsequent entry', 'description': {'raw': '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:\\n\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=563687401#Transcluded_pages\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417482772, 'spacePHID': None, 'dateCreated': 1373474880, 'dateModified': 1417482772, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51119', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Auto-external links to image files which are broken (404/etc.) display as the filename and cannot be edited', 'description': {'raw': 'When a raw URL with no markup (e.g. http://www.sucs.org/~cmckenna/photos/quizes/tq2012/July/Jun03key.png\\ufeff ) 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.\\n\\nLinks 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.\\n\\nThis is not unlikely related to bug 51092 in some way.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373480408, 'spacePHID': None, 'dateCreated': 1373450100, 'dateModified': 1417048889, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51103', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Editing adds JavaScript', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kc6qx3zohjybu3nzffu3', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373724208, 'spacePHID': None, 'dateCreated': 1373430900, 'dateModified': 1373852205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51094', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector blown to pieces when pressing return after clicking \"Insert link\" (before the inspector has finishes opening)', 'description': {'raw': \"Screenshot 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).\\n* 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11776}\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373411601, 'spacePHID': None, 'dateCreated': 1373411220, 'dateModified': 1417571079, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51077', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Adding a {{cn}} template causes VisualEditor to silently add <nowiki>..</nowiki> to the edited paragraph', 'description': {'raw': '**Author:** `FT2.wiki`\\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.\\n\\nhttp://en.wikipedia.org/w/index.php?title=XFS&diff=563579994&oldid=562618140\\n\\nUnclear if this is the same or different as other <nowiki> issues on bugzilla\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373409131, 'spacePHID': None, 'dateCreated': 1373406240, 'dateModified': 1373409131, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51072', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link input field identifiers in DOM are bogus', 'description': {'raw': 'corrupt <class> identifier in DOM for Link\\n\\nsee screenshot\\n\\nwhat is this \"class\"?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11753}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375221769, 'spacePHID': None, 'dateCreated': 1373398680, 'dateModified': 1417571052, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51066', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: reference editing bringing you to the wrong citation (template problem?)', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385381556, 'spacePHID': None, 'dateCreated': 1373395500, 'dateModified': 1417571012, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51058', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: duplicate links created if parts of the link are differently italicised/bolded', 'description': {'raw': \"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]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394501875, 'spacePHID': None, 'dateCreated': 1373392500, 'dateModified': 1394501875, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51054', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The transparent color that shows the template goes up to the previous element instead of the top of the template', 'description': {'raw': \"a screenshot with the problem\\n\\nTo reproduce:\\n\\n1. Go to https://en.wikipedia.org/wiki/Boris_Ponomarev?veaction=edit\\n2. Click the template at the bottom of the article.\\n\\nObserved: 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.\\n\\nExpected: The transparent color must only cover the template itself and not other elements.\\n\\nSee the screenshot.\\n\\nTested on Firefox 22.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11723}\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385381652, 'spacePHID': None, 'dateCreated': 1373385480, 'dateModified': 1417048881, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51048', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: adding spaces?', 'description': {'raw': '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\").\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379455266, 'spacePHID': None, 'dateCreated': 1373365380, 'dateModified': 1379455266, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51024', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"clear formatting\" does not remove links', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373504485, 'spacePHID': None, 'dateCreated': 1373361000, 'dateModified': 1373504485, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51018', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template dialog crushing parameters together and nowiking links', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383004078, 'spacePHID': None, 'dateCreated': 1373359380, 'dateModified': 1417571038, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51017', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template highlight is sometimes misplaced in the reference inspector', 'description': {'raw': \"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. \\n\\nI'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\\nhttps://upload.wikimedia.org/wikipedia/en/5/5f/Bad_Ref_Edit.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373351191, 'spacePHID': None, 'dateCreated': 1373330760, 'dateModified': 1373351191, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50991', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)', 'description': {'raw': '1) Open an article such as\\nhttps://en.wikipedia.org/wiki/Convex_function?veaction=edit\\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.\\n\\nSimilarly, 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**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50160'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1486157050, 'spacePHID': None, 'dateCreated': 1373324220, 'dateModified': 1486157050, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50986', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Selecting text does not work', 'description': {'raw': 'How to reproduce:\\n* Go to https://www.mediawiki.org/wiki/Extension:TimedMediaHandler/Client_download?veaction=edit\\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.\\n\\nCurrent 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.\\nRainer Rillke\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377831826, 'spacePHID': None, 'dateCreated': 1373316060, 'dateModified': 1377831826, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50977', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Please turn off VisualEditor as long as it doesn't work\", 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373363212, 'spacePHID': None, 'dateCreated': 1373315640, 'dateModified': 1373363951, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50975', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Redlinks show up as bluelinks in VisualEditor mode', 'description': {'raw': '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. \\n\\nFor 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\\nhttps://en.wikipedia.org/wiki/User:Keegan_(WMF)/Sandbox\\n\\nThis may be a Parsoid issue?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373353929, 'spacePHID': None, 'dateCreated': 1373314500, 'dateModified': 1373353929, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50974', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: line endings are not preserved when copying from a text file', 'description': {'raw': \"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.\\n\\nYou can see an example here:\\nhttps://www.mediawiki.org/w/index.php?title=Language_portal/Definition_of_Done&oldid=726988\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373851066, 'spacePHID': None, 'dateCreated': 1373297700, 'dateModified': 1417048888, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50946', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'context specific editor for templates?', 'description': {'raw': 'On English Wikipedia, it is stated that some common templates need a context specific editor. \\n\\nExamples 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.\\n\\n*[[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.\\n\\n*[[Template:sfn]]\\nExplained above.\\n\\n*[[Template:efn]]\\nSimplicity- there is only one parameter. Though an alert may be needed if the Notes {*{notelist|notes=}*} structure is not in place.\\n\\n*[[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.\\n\\n([[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.)\\n\\n\\nI 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'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385381445, 'spacePHID': None, 'dateCreated': 1373241540, 'dateModified': 1385381445, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50915', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template editor turns links into [[link|name]] in CE', 'description': {'raw': \"screenshot of CE after transclusion editor\\n\\nhttps://en.wikipedia.org/wiki/Luton?veaction=edit\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11424}\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373354186, 'spacePHID': None, 'dateCreated': 1373233920, 'dateModified': 1417571080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50909', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The anchor for the template editor can easily become invisible', 'description': {'raw': 'Take a page with a reasonably sized infobox.\\nMake 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375717235, 'spacePHID': None, 'dateCreated': 1373233620, 'dateModified': 1417571050, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50907', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save dialog behaves as partial modal', 'description': {'raw': \"In some respects the save dialog is partially modal, which is a strange and unfamiliar concept to some.\\n\\nThe 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377814666, 'spacePHID': None, 'dateCreated': 1373232480, 'dateModified': 1417571046, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50903', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Nested <nowiki>s considered harmful', 'description': {'raw': 'Sometimes Parsoid will wrap a <nowiki> around an existing <nowiki>; 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**: https://en.wikipedia.org/w/index.php?title=Your_Face_Sounds_Familiar_%28UK_TV_series%29&diff=562149606&oldid=562149387'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373314749, 'spacePHID': None, 'dateCreated': 1373055060, 'dateModified': 1373637242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50835', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: edits fail on hitting the abuse filter (with a cryptic error message)', 'description': {'raw': '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\".\\n\\nProbably not helpful.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373054299, 'spacePHID': None, 'dateCreated': 1373053920, 'dateModified': 1373054299, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50828', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Keyboard shortcut for editing source', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373077734, 'spacePHID': None, 'dateCreated': 1373048100, 'dateModified': 1417571082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50817', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Whitespace immediately before a template at the start of the page is swallowed and so unremoveable', 'description': {'raw': 'Try removing the whitespace at the top of https://en.wikipedia.org/wiki/Burr%E2%80%93Hamilton_duel and see what happens.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://parsoid.wmflabs.org/en/User:Jdforrester_(WMF)/Bug_50797?oldid=564303673'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376618868, 'spacePHID': None, 'dateCreated': 1373026620, 'dateModified': 1376618868, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50797', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: VE's determination of image size should hook into user preferences\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372966971, 'spacePHID': None, 'dateCreated': 1372966680, 'dateModified': 1372967030, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50766', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: edit conflict handling', 'description': {'raw': \"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?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372956245, 'spacePHID': None, 'dateCreated': 1372954140, 'dateModified': 1372956245, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50753', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Once a user has inserted a new transclusion, offer to add another', 'description': {'raw': 'Copied 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'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383280851, 'spacePHID': None, 'dateCreated': 1372942020, 'dateModified': 1417571037, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50744', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Template inspector's parameter display causes smushing\", 'description': {'raw': 'See https://en.wikipedia.org/wiki/File:VisualEditor_-_Cite_template_layout_issue_%28TemplateData%29.png - Firefox 22, Monobook.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372937527, 'spacePHID': None, 'dateCreated': 1372937460, 'dateModified': 1417571083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50738', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: not showing new categories on reload', 'description': {'raw': 'If you add categories to a page and save, the newly-loaded version does not include the new additions.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373556875, 'spacePHID': None, 'dateCreated': 1372937340, 'dateModified': 1373556875, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50737', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '<nowiki> added to existing <nowiki> content', 'description': {'raw': 'This edit:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Percy_Jackson:_Sea_of_Monsters&diff=562794756&oldid=562792500\\n\\nis an example of a dirty diff where VisualEditor/Parsoid appears to have wrapped <nowiki> tags around existing <nowiki> content (in this case the \"|\" symbol in the title of a cited website) inside a template inside a reference.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373637242, 'spacePHID': None, 'dateCreated': 1372923600, 'dateModified': 1373637242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50724', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: alt text?', 'description': {'raw': \"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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372900959, 'spacePHID': None, 'dateCreated': 1372897260, 'dateModified': 1372900959, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50709', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Template auto-filled with wikitext on edit', 'description': {'raw': \"This came from the VisualEditor feedback page in Hebrew. I couldn't replicate, but the problem is evident in this diff:\\n\\nhttp://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\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376511764, 'spacePHID': None, 'dateCreated': 1372875720, 'dateModified': 1417571049, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50684', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inherited category becomes explicitly invoked', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385378094, 'spacePHID': None, 'dateCreated': 1372869900, 'dateModified': 1417571014, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50675', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Section 0 (lede) editing does not offer VisualEditor', 'description': {'raw': '**Author:** `wikipedia`\\n\\n**Description:**\\nUsing the [edit] next to the lede (section=0) only allows invoking the source editor.\\n\\nIdeally there should be consistency, and VE options should either be always shown, or never shown.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372848396, 'spacePHID': None, 'dateCreated': 1372847760, 'dateModified': 1372853500, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50653', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: image resizing causing implosion', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373578420, 'spacePHID': None, 'dateCreated': 1372842180, 'dateModified': 1417571077, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50651', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Unify post-edit notifications on Wikimedia wikis', 'description': {'raw': \"There are currently two similar, but distinct post-edit notifications on some Wikimedia wikis. I'll attach screenshots from <https://test.wikipedia.org> momentarily.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372834231, 'spacePHID': None, 'dateCreated': 1372833600, 'dateModified': 1372834231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Still dirty refs?', 'description': {'raw': 'There seem to be several dirty ref sections in this diff:\\n\\nhttps://en.wikipedia.org/w/index.php?title=God_of_War_%28series%29&diff=prev&oldid=562631132\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379613746, 'spacePHID': None, 'dateCreated': 1372827600, 'dateModified': 1417571044, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50637', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog does not handle missing parameter name', 'description': {'raw': \"To reproduce\\n\\n1. Click puzzle piece\\n2. Type cn ([[Template:cn]] redirecting to [[Template:Citation needed]])\\n3. Press enter twice.\\n\\n(I was experimenting see if there is a quick way to get out of the template dialog; this would be useful for templates like Template:cn that are commonly added without parameters).\\n\\n4. Type 'foo'\\n5. Click 'Apply changes'\\n6. It shows 'Template:Fooifsubst'\\n7. Code is generated as '{{Cn| = foo}'\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385375541, 'spacePHID': None, 'dateCreated': 1372810140, 'dateModified': 1417583592, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50627', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor \"leave BETA\" dialogue jumps around, making leave hard/impossible', 'description': {'raw': '**Author:** `wikipedia`\\n\\n**Description:**\\nTo reproduce:\\n\\n1. http://en.wikipedia.org/wiki/High_Speed_2?veaction=edit&vesection=6\\n2. Wait, hopefully the VisualEditor loads, and does not hang\\n3. Click \"BETA\"\\n4. Click Leave.\\n5. Try to type in this dialogue box\\n\\nWhat happens:\\n\\n6. The window scrolls around with each and every keypress.\\n7. The Leave BETA dialogue is very hard to complete.\\n\\nWhat should happen:\\n\\n6. The window should not scroll\\n7. The process of leaving should be easy and reliable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373152861, 'spacePHID': None, 'dateCreated': 1372794540, 'dateModified': 1373152861, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50602', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Editing sections one at a time results in editing old revisions', 'description': {'raw': \"When editing a section with VisualEditor the page loads and saves just fine.  However, if you next edit a different section *without refreshing the page*, VisualEditor does not recognize the version of the page you just saved as what you are editing and loads the last revision and warns you that you are editing an old revision.  This occurs in Chrome and Firefox using Windows 7 as I've tested it.\\n\\nFrom https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Editing_section_results_in_dirty_page_cache_--_have_to_reload_page_before_doing_additional_edits\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373155391, 'spacePHID': None, 'dateCreated': 1372788540, 'dateModified': 1373155391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50596', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Can \"edit section\" be restricted to only open the single section?', 'description': {'raw': 'Not sure if this is possible, but a user raises concerns about the behavior of VE opening the whole page for editing instead of editing specific sections, given that it increases the load time.\\n\\nSee:\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562566677#edit_one_section_only\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372793232, 'spacePHID': None, 'dateCreated': 1372783680, 'dateModified': 1372793232, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50592', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: warn on markup.', 'description': {'raw': \"Similar to bugs 50093 and 50527; users need to be warned when they're using markup in the VE. This is a source of a pretty large amount of corruption on enwiki, and I'm not sure how sustainable the community's patience for that is.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372859187, 'spacePHID': None, 'dateCreated': 1372768500, 'dateModified': 1372859187, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50581', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Infobox template shows HTML', 'description': {'raw': '**Author:** `warnckew`\\n\\n**Description:**\\nScreenshot showing infobox DIV HTML code\\n\\nLaunching VisualEditor to edit http://en.wikipedia.org/w/index.php?title=United_Nations_Security_Council_Resolution_1693&oldid=541044487 makes the heading of the infobox show some unexpected HTML contents, as shown in the attached browser screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11621}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372781074, 'spacePHID': None, 'dateCreated': 1372759800, 'dateModified': 1417571084, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50567', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Bad typing/backspacing behaviour for Malayalam', 'description': {'raw': 'I have noticed an unexpected behavior while tesing Visual Editor with Malayalam Wikipedia. Describing the steps below:-\\n\\n1. Added the following text on a page\\n\\nഡിസ്രയേലി\\n\\n2. When pressing a backspace immediately after the above text, it becomes\\n\\nഡസരയ\\n\\nie. many characters in between the original text disappeared. The expected result was ഡിസ്രയേ\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Windows 7\\n**Platform**: PC\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50507'}, 'authorPHID': 'PHID-USER-4jecvpv4h62htut6pxez', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374044478, 'spacePHID': None, 'dateCreated': 1372759140, 'dateModified': 1482599632, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50566', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"old version\" warning shows when opening VE after a VE edit', 'description': {'raw': \"Steps 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\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372747009, 'spacePHID': None, 'dateCreated': 1372746900, 'dateModified': 1372747009, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50555', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Likely round-trip failure involving categories and transclusion content on [[Michala Petri]]', 'description': {'raw': 'See http://en.wikipedia.org/w/index.php?title=Michala_Petri&diff=562483360&oldid=562482770\\n\\nIt looks like VE inserted categories and default sort at some random place in the DOM, potentially cutting encapsulated transclusion content in two?\\n\\nThe Parsoid template encapsulation and round-tripping for this page looks fine:\\n\\nhttp://parsoid.wmflabs.org/_rt/en/Michala_Petri?oldid=562482770\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373484208, 'spacePHID': None, 'dateCreated': 1372741440, 'dateModified': 1373484208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50554', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dialogs layer under the toolbar, hide close button', 'description': {'raw': 'I\\'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.\\n\\nIn 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'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374878989, 'spacePHID': None, 'dateCreated': 1372740840, 'dateModified': 1417571054, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50553', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Likely ref / transclusion round-trip failure', 'description': {'raw': 'This edit was flagged by VE as DOM-differing, and looks like a dirty ref/transclusion:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Abolitionism&curid=38894&diff=562492192&oldid=560500423\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385375352, 'spacePHID': None, 'dateCreated': 1372737300, 'dateModified': 1417571014, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50550', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Feedback form moves and jerks the screen around', 'description': {'raw': \"**Author:** `Shirudo`\\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.\\n\\nIf it makes a difference, I'm using Firefox 22 on Fedora 18, with Gnome 3 Fallback.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372894536, 'spacePHID': None, 'dateCreated': 1372723860, 'dateModified': 1417571015, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50538', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'IME selector appears when the VisualEditor headings style selector is clicked', 'description': {'raw': \"Enter a wiki with VE and ULS. (Enable ULS in preferences if needed.)\\n\\nStart editing a page using VE. Press the headings style dropdown.\\n\\nObserved: IME selector appears near the dropdown.\\n\\nExpected: IME selector must not appear. It's not a place for writing things.\\n\\nBackground: there's an <input> element hiding there to capture click events (according to Roan).\\n\\nhttps://gerrit.wikimedia.org/r/#/c/68339/ may be able to fix it (though some modifications may be needed).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Whiteboard**: ve\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375770944, 'spacePHID': None, 'dateCreated': 1372716720, 'dateModified': 1375770944, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50529', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Tagging articles using old markup on VE', 'description': {'raw': 'I note that if an editor uses old markup in VE (like [[link]]), it gets enclosed in <nowiki> 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**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49820'}, 'authorPHID': 'PHID-USER-65pjzcmoby2fsgzdrfjq', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375200134, 'spacePHID': None, 'dateCreated': 1372715580, 'dateModified': 1375352947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50527', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Buttons not showing up', 'description': {'raw': 'http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#.22Submit.22_button_doesn.27t_show_up\\n\\nEpicgenius reports the buttons not showing up, I have his same config and was not able to reproduce the issue.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374878756, 'spacePHID': None, 'dateCreated': 1372714740, 'dateModified': 1374878756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50524', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Ghost references in VisualEditor?', 'description': {'raw': \"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 [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.\\n\\nFull report at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE_picking_up_old_version_of_file.3F_-_27_ghost_references.21 .\\n\\nIt does the same for me (Vector on Chrome).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385375005, 'spacePHID': None, 'dateCreated': 1372712700, 'dateModified': 1385375005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50521', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting all content removes input marker', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374079583, 'spacePHID': None, 'dateCreated': 1372711380, 'dateModified': 1374079583, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50519', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Unexpected editing behavior for typing Malayalam text', 'description': {'raw': '**Author:** `harshanh1979`\\n\\n**Description:**\\nI have tested VisualEditor at ml.wikipedia at the following page\\n\\nhttps://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\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Linux\\n**Platform**: PC\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50566'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374044484, 'spacePHID': None, 'dateCreated': 1372699740, 'dateModified': 1482599632, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50507', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: thick line appearing', 'description': {'raw': \"Screenshot\\n\\nSee screenshot, from https://en.wikipedia.org/wiki/Jitter_%28disambiguation%29?veaction=edit - that line near the top shouldn't be there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11385}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384204290, 'spacePHID': None, 'dateCreated': 1372613820, 'dateModified': 1384204317, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50468', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Text wrongly being given pre-formatted format', 'description': {'raw': 'Screenshot\\n\\nSee screenshot - from https://en.wikipedia.org/wiki/Iphigenia?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11382}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385374964, 'spacePHID': None, 'dateCreated': 1372613700, 'dateModified': 1417571016, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50467', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links created in the userspace are treated as links to subpages', 'description': {'raw': '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\\n\\nThis seems somewhat suboptimal.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377445192, 'spacePHID': None, 'dateCreated': 1372612740, 'dateModified': 1377445192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50466', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Error saving data to server: Failed request: error.', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385375109, 'spacePHID': None, 'dateCreated': 1372608360, 'dateModified': 1417571016, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50463', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE feature request: visual \"tell\" when editing', 'description': {'raw': 'Can something - perhaps a faint background color or an outline - be added to make clear when one is in editing mode?\\n\\nCopied from http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Make_editing_view_more_distinctive_from_article\\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'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373852659, 'spacePHID': None, 'dateCreated': 1372595400, 'dateModified': 1373852659, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50456', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Insert media dialog is borked', 'description': {'raw': 'screenshot\\n\\nIt was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11359}'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372620610, 'spacePHID': None, 'dateCreated': 1372595100, 'dateModified': 1372620610, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50455', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Error saving data to server\" but actually successful, and spurious diff', 'description': {'raw': \"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 (&#124; -> <nowiki>|</nowiki>) in a section of the page I didn't edit.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385380712, 'spacePHID': None, 'dateCreated': 1372548840, 'dateModified': 1417583464, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50437', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Preserve wiki link href with ././ prefix', 'description': {'raw': 'The following HTML does not seem to properly round-trip through VE:\\n\\n<p><a rel=\"mw:WikiLink\" href=\"././Foo\">./Foo</a></p>\\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\\nhttps://en.wikipedia.org/w/index.php?title=DreamWorks_Animation&curid=1509817&diff=562129988&oldid=562129729\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372887258, 'spacePHID': None, 'dateCreated': 1372526940, 'dateModified': 1372920044, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50428', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Feature request: permit copy-paste of templates from history', 'description': {'raw': 'Taken 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'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373407947, 'spacePHID': None, 'dateCreated': 1372513920, 'dateModified': 1373407947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50421', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace from header line into empty paragraph changes header format into paragraph', 'description': {'raw': '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.\\n\\nNote 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50995'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384945237, 'spacePHID': None, 'dateCreated': 1372507500, 'dateModified': 1417048881, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50418', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor does not load on Opera when debugging with Dragonfly', 'description': {'raw': 'Would you believe that.\\n\\n[6/29/2013 1:44:17 PM] JavaScript - https://pl.wikipedia.org/wiki/Gródek_(obwód_lwowski)?veaction=edit\\nEvent thread: readystatechange\\nUncaught exception: Error: WRONG_ARGUMENTS_ERRError thrown at line 39, column 4 in <anonymous function: ve.copyDomElements>(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&*:\\n    return doc ? doc.importNode(domElement, true) : domElement.cloneNode(true);\\ncalled from line 38, column 3 in <anonymous function: ve.copyDomElements>(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&*:\\n    return domElements.map(function(domElement) {\\ncalled from line 9721, column 3 in <anonymous function: ve.ce.GeneratedContentNode.prototype.onUpdate>() 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&*:\\n    this.$.empty().append(ve.copyDomElements(store.value(index), doc));\\ncalled 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&*:\\n    this.onUpdate();\\ncalled 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&*:\\n    ve.ce.GeneratedContentNode.call(this);\\ncalled 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&*:\\n    ve.ce.MWTransclusionNode.call(this, model);\\ncalled via Function.prototype.apply() from line 50, column 2 in <anonymous function: ve.Factory.prototype.create>(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&*:\\n    constructor.apply(obj, args);\\ncalled from line 8132, column 4 in <anonymous function: ve.ce.BranchNode.prototype.onSplice>(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&*:\\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 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&*:\\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 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&*:\\n    ve.ce.BranchNode.call(this, model, config);\\n\\nAt this point `store.value(index)` is [undefined, undefined] on Opera, but [<span...>, <dl...>] on Firefox. Since `index` is not undefined, this would indicate some sort of an internal inconsistency.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372557668, 'spacePHID': None, 'dateCreated': 1372507500, 'dateModified': 1417571085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50417', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Text covered up by infobox when editing, if image in infobox is large', 'description': {'raw': \"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.\\n\\nSee 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372500786, 'spacePHID': None, 'dateCreated': 1372498200, 'dateModified': 1372500786, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50416', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: massively duplicating references on render', 'description': {'raw': 'https://en.wikipedia.org/wiki/Birbal has 3 references; https://en.wikipedia.org/wiki/Birbal?veaction=edit has 24.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383410182, 'spacePHID': None, 'dateCreated': 1372436400, 'dateModified': 1417571016, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50380', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar shows on top of Save dialog, prevents saving', 'description': {'raw': \"screenshot\\n\\nI'm not sure if this is bug 49514 ; feel free to dupe if it is.\\n\\nSee attached screenshot: the toolbar appears on top of the save dialog, which makes it difficult or impossible to save changes.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11157}\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372417299, 'spacePHID': None, 'dateCreated': 1372416960, 'dateModified': 1372417299, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50364', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: modifying some templates causes them to collapse in on themselves in edit mode', 'description': {'raw': 'Screenshot\\n\\nTry modifying the infobox in https://en.wikipedia.org/wiki/Defiance_%28TV_series%29?veaction=edit for example - see the screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11137}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372690696, 'spacePHID': None, 'dateCreated': 1372414740, 'dateModified': 1417571085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50361', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't drag and drop transclusions, text, references\", 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373663953, 'spacePHID': None, 'dateCreated': 1372414500, 'dateModified': 1373663953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50359', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor throws <nowiki> next to any square bracket [', 'description': {'raw': \"It is usual to use [square brackets], [...] inside quotes to cut or complete sentences in quotes. As for today, VisualEditor will add <nowiki> tags like this:\\n\\n<nowiki>[Square brackets]</nowiki>\\n\\n<nowiki>[...]</nowiki>\\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.\\n\\nAlso, according to Bug 47678 this means that editors won't be able to edit the content inside those brackets with VisualEditor, because of the <nowiki> tags.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\n{T54268}\"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372744432, 'spacePHID': None, 'dateCreated': 1372374900, 'dateModified': 1539403279, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50331', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cutting the text of a header leaves a blank header line behind', 'description': {'raw': 'Fairly self-explanatory.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373154763, 'spacePHID': None, 'dateCreated': 1372359060, 'dateModified': 1373154763, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50313', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: edit link on the history page needs updating', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372366680, 'spacePHID': None, 'dateCreated': 1372358460, 'dateModified': 1417571087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50312', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Carriage return shows up among text', 'description': {'raw': 'This is what Alberobello looks like under VE\\n\\nWhen 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11918}'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373854867, 'spacePHID': None, 'dateCreated': 1372348860, 'dateModified': 1444309256, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50295', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"ULS doesn't work while using VisualEditor\", 'description': {'raw': 'When VisualEditor is enabled there is no option to enable ULS, where I could type in Odia in the search bar using ULS.\\n\\nWhen 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11913}'}, 'authorPHID': 'PHID-USER-az3b22hiqzlaov5l2efk', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372351064, 'spacePHID': None, 'dateCreated': 1372346160, 'dateModified': 1417571087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50293', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: not permitting interaction with some media files (and formatting them weirdly)', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373852602, 'spacePHID': None, 'dateCreated': 1372344540, 'dateModified': 1373852602, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50290', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: references cannot be copied and pasted without losing formatting', 'description': {'raw': \"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 <ref>Jones (2003) p.23</ref> 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373851094, 'spacePHID': None, 'dateCreated': 1372337880, 'dateModified': 1417571076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50283', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page settings dialog adds categories with [[:Category:xyz]] syntax', 'description': {'raw': '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]].\\n\\nSeen on testwiki and enwiki.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372435698, 'spacePHID': None, 'dateCreated': 1372331040, 'dateModified': 1417571086, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50278', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar obscures save dialog when scrolled down the page', 'description': {'raw': 'Screenshot of bug\\n\\nWhen scrolled down the page, the top of the save dialog is obscured by the toolbar. See screenshot.\\n\\nSee also other z-index bugs: bug 49514 and bug 49275.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11882}'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372387036, 'spacePHID': None, 'dateCreated': 1372329960, 'dateModified': 1417571086, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50276', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: not adhering to column numbers when rendering', 'description': {'raw': 'See https://en.wikipedia.org/wiki/Microorganism?veaction=edit#See_also for example; that should be divided into 3 columns.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373520752, 'spacePHID': None, 'dateCreated': 1372301820, 'dateModified': 1373520752, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50267', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Unwanted Removal of text formatting', 'description': {'raw': \"In this edit:https://en.wikipedia.org/w/index.php?title=Blepsias_cirrhosus&diff=next&oldid=561719692\\n\\nBold/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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372284454, 'spacePHID': None, 'dateCreated': 1372280520, 'dateModified': 1417048891, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50258', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"'become' doesn't load ~/.bashrc\", 'description': {'raw': \"When you use 'become' to log into a shared account, ~/.bashrc isn't run.\\n\\ncatrope@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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372270000, 'spacePHID': None, 'dateCreated': 1372269540, 'dateModified': 1408297464, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50249', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"screen doesn't work from within 'become'\", 'description': {'raw': \"catrope@tools-login:~$ become visualeditor\\nlocal-visualeditor@tools-login:~$ screen\\nCannot open your terminal '/dev/pts/97' - please check.\\n\\n\\nHowever, running screen as myself and then running 'become visualeditor' in each screen window does work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383053606, 'spacePHID': None, 'dateCreated': 1372269480, 'dateModified': 1410849251, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50248', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Dialogs won't open after adding a template at the end of the page\", 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372271165, 'spacePHID': None, 'dateCreated': 1372263600, 'dateModified': 1372271165, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50242', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor not working due to unflushed ResourceLoader cache?', 'description': {'raw': '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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**Whiteboard**: aklapper-moreinfo'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372864641, 'spacePHID': None, 'dateCreated': 1372252500, 'dateModified': 1372864641, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50226', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Extra bullet point before template containing bulleted list', 'description': {'raw': 'VE rendering of [[WUEC#External_links]] does not match MW rendering.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372295480, 'spacePHID': None, 'dateCreated': 1372230840, 'dateModified': 1372295480, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50213', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: References prevent floats from being selected and edited', 'description': {'raw': 'screenshot\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11749}'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373164008, 'spacePHID': None, 'dateCreated': 1372228380, 'dateModified': 1373164008, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50211', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Opening Page settings dialog doesn't close heading format drop-down\", 'description': {'raw': \"screenshot\\n\\nSteps to reproduce:\\n* Click on the heading format drop-down menu. Don't close it.\\n* Click on the Page settings menu.\\n\\nExpected result:\\n* The heading format drop-down is closed before the Page settings dialog shows up.\\n\\nActual result:\\n* The heading format drop-down remains open (and selectable) on top of the Page settings dialog (see attached screenshot).\\n\\nObserved in Firefox 21.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11748}\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373163131, 'spacePHID': None, 'dateCreated': 1372227660, 'dateModified': 1417571080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50210', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image size parameter with spaces is ignored', 'description': {'raw': 'See [[testwiki:VisualEditor:Little or big]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372216311, 'spacePHID': None, 'dateCreated': 1372216200, 'dateModified': 1372216311, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50207', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Logging broken for GettingStarted (page-save-success logged as page-impression)', 'description': {'raw': '**Author:** `swalling`\\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. \\n\\nThis 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374273514, 'spacePHID': None, 'dateCreated': 1372206060, 'dateModified': 1374273514, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50204', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: weird behaviour on reload following save (JS not loading?)', 'description': {'raw': \"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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373162765, 'spacePHID': None, 'dateCreated': 1372172160, 'dateModified': 1417571081, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50181', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Odd behavior using arrow keys for cursor movement', 'description': {'raw': '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:\\n\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=561499916#Some_funnies\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=561499916#Some_funnies'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373162663, 'spacePHID': None, 'dateCreated': 1372159200, 'dateModified': 1417048890, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50168', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '<nowiki> tags added to (valid) list in a template parameter, corrupting them', 'description': {'raw': \"In general,\\n\\n{{foo\\nbar = \\n* 1\\n* 2\\n* 3\\n}}\\n\\n… is RT'ing to \\n\\n{{foo\\nbar = <nowiki>* 1\\n* 2\\n* 3</nowiki>\\n}}\\n\\nExamples: \\n\\n* https://en.wikipedia.org/w/index.php?title=Riddler&diff=561149660&oldid=561096940\\n* https://en.wikipedia.org/w/index.php?title=Schuylar_Oordt&diff=561438828&oldid=561406705\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50070\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372127067, 'spacePHID': None, 'dateCreated': 1372125540, 'dateModified': 1372127067, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50147', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Missing root git config file when cloning', 'description': {'raw': \"After 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 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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373095093, 'spacePHID': None, 'dateCreated': 1372121400, 'dateModified': 1424912192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50143', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images: Frameless images should not emit the \"caption\" as a <figcaption> even when it\\'s set', 'description': {'raw': \"[Not urgent.]\\n\\nFrameless 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 <figcaption> for images regardless of type (thumb, framed or frameless) - and doesn't output the alt at all, which is bug 45208.\\n\\nThere's a hack in VisualEditor to ignore <figcaption>s for these as part of bug 50113, but Parsoid should fix these in due course.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372121678, 'spacePHID': None, 'dateCreated': 1372119780, 'dateModified': 1372934057, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50142', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor adding spurious pipe separators to image syntax', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=History_of_Delta_Air_Lines&curid=38607247&diff=561387547&oldid=557734729\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372096490, 'spacePHID': None, 'dateCreated': 1372095840, 'dateModified': 1372096490, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50116', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor template parameter normalization results in dirty diffs', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Laura_Pannack&diff=561375041&oldid=561336738\\n\\nThe change should have only italicized a few publication names. Instead it changed...\\n\\n* Winner, Magenta Foundation award<ref>{{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}}</ref>\\n\\nto...\\n\\n* Winner, Magenta Foundation award<ref>{{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}}</ref>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373163467, 'spacePHID': None, 'dateCreated': 1372088640, 'dateModified': 1373163467, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50108', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor ref weirdness', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Laura_Pannack&diff=561336738&oldid=557984097\\n\\n<ref name=\"telegraph\"/> --> <ref name=\"telegraph\"></ref>\\n\\nWeird.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372091672, 'spacePHID': None, 'dateCreated': 1372088340, 'dateModified': 1372107851, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50106', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor spurious attribute normalization (resulting in dirty diffs)', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Christopher_Walken&curid=167790&diff=561335042&oldid=560573850\\n\\nhttps://en.wikipedia.org/w/index.php?title=Complement_fixation_test&diff=561335484&oldid=540954235\\n\\nhttps://en.wikipedia.org/w/index.php?title=List_of_first-class_cricket_records&curid=5507023&diff=561342472&oldid=560120426\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373163469, 'spacePHID': None, 'dateCreated': 1372086060, 'dateModified': 1373163469, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50101', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor dirty diff', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Paula_Deen&diff=561368754&oldid=561308417\\n\\nI did a section edit to link \"Food Network\". This was the resulting diff.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372091385, 'spacePHID': None, 'dateCreated': 1372085520, 'dateModified': 1372091385, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50099', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Impossible to review or save changes in IE10', 'description': {'raw': 'Screenshot of bug\\n\\nThe \"review changes\" flyout looks broken and doesn\\'t actually do anything.\\n\\nThere\\'s a script error:\\n\\nSCRIPT70: Permission denied \\nload.php, line 18 character 453\\n\\nWith \"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:\\n\\nfor(i=0,len=oldDoc.head.childNodes.length;\\n        i<len;\\n        i++){\\n\\nI tried to get a better output using debug=true, but this seems to totally break VE (in IE10 at least).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n\\n**Attached**: {F11482}'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372084871, 'spacePHID': None, 'dateCreated': 1372059000, 'dateModified': 1423674429, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50086', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: still making unrelated modifications', 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=Royal_Lancaster_Infirmary&diff=561254127&oldid=560972172 for example.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372039230, 'spacePHID': None, 'dateCreated': 1372037520, 'dateModified': 1373984013, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50080', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"read\" version after save page not picking up on category removals', 'description': {'raw': \"If a user hits edit, removes a category and saves, the read-only article they're then presented with still includes the old category - or at least, does on https://en.wikipedia.org/wiki/Sumali\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372036218, 'spacePHID': None, 'dateCreated': 1372034880, 'dateModified': 1372036218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50072', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor saves HTML instead of wikitext', 'description': {'raw': 'In the following edit, VE saved the internal page representation instead of the wikitext:\\n\\nhttps://nl.wikipedia.org/w/index.php?title=Eurosong&diff=prev&oldid=38007082\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-muirnivxp5hzppn2a3z7', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372004983, 'spacePHID': None, 'dateCreated': 1371986640, 'dateModified': 1372004983, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50049', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images turned into mw:Placeholder in certain cases', 'description': {'raw': 'When viewing [[testwiki:Visualeditor_image_captions]] in VE, the images cannot be seen. They are still \"known\" though - they don\\'t vanish on save.\\n\\n(My testing of this issue led to the filing of bug 50008, but the issue there seems to have gone away now. However, this one is still showing up for me, so I think this is a separate bug.\\n\\nPlease close this bug if it turns out to have fixed itself.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372104211, 'spacePHID': None, 'dateCreated': 1371972060, 'dateModified': 1372934068, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50035', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Provide build status images', 'description': {'raw': \"Assuming we do not yet have something like this, it'd be awesome if this Jenkins plugin could be installed:\\n\\nhttps://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin\\n\\nI want to be able to embed such a build status image on some website.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-mye6umixnhfo7lhpgzmj', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372235730, 'spacePHID': None, 'dateCreated': 1371912840, 'dateModified': 1372235730, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50022', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parametr adds =', 'description': {'raw': '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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://cs.wikipedia.org/w/index.php?title=Robert_z_Molesme&diff=10436403&oldid=10436394'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373161574, 'spacePHID': None, 'dateCreated': 1371911220, 'dateModified': 1417571080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50019', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Uncaught TypeError: Cannot read property 'description' of undefined\", 'description': {'raw': 'After loading the Visual Editor on\\nhttps://pt.wikipedia.org/wiki/Quadrado?veaction=edit&debug=1&uselang=pt&useskin=vector\\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:\\nhttps://bits.wikimedia.org/static-1.22wmf7/extensions/VisualEditor/modules/ve/dm/models/ve.dm.MWTemplateSpecModel.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371969869, 'spacePHID': None, 'dateCreated': 1371898920, 'dateModified': 1417571088, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50016', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide ability to alternate between visual and source editing', 'description': {'raw': 'A user suggested at\\nhttps://pt.wikipedia.org/wiki/WP:Editor_Visual/Coment%C3%A1rios?oldid=36175459#Alternar_entre_editores_sem_sair_da_p.C3.A1gina\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371855868, 'spacePHID': None, 'dateCreated': 1371855780, 'dateModified': 1417571089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49986', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Insecure image links on https', 'description': {'raw': 'When I open\\nhttps://pt.wikipedia.org/wiki/Jorge_VI_do_Reino_Unido?veaction=edit\\nI see several warnings like this on Google Chrome:\\n\\nThe 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371855005, 'spacePHID': None, 'dateCreated': 1371854820, 'dateModified': 1417571087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49984', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: not functioning on it.wiki', 'description': {'raw': \"Screenshot\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11224}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371828173, 'spacePHID': None, 'dateCreated': 1371825480, 'dateModified': 1371828173, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49960', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Required 'Edit Source' at Sections\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-4jecvpv4h62htut6pxez', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371827708, 'spacePHID': None, 'dateCreated': 1371805320, 'dateModified': 1371827708, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49950', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor translates templates into Uzbek language', 'description': {'raw': '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.).\\n\\nMore evidence of VE\\'s growing self-awareness? Caffeine-induced hallucination on the reporter\\'s part? Inquiring minds want to know.\\n\\nChrome/Ubuntu and FF/Ubuntu.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371829646, 'spacePHID': None, 'dateCreated': 1371798000, 'dateModified': 1372934049, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49939', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Internal wiki link using \"pipe trick\" [[/Foo/]] to link to sub page broken', 'description': {'raw': 'Screenshot of problem. Compares VE view and MWParser view.\\n\\nWikitext [[/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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11096}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371771658, 'spacePHID': None, 'dateCreated': 1371771480, 'dateModified': 1371771658, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49919', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: full sized images are displayed regardless of a |pictured parameter', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371769152, 'spacePHID': None, 'dateCreated': 1371748800, 'dateModified': 1372933999, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49891', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn ♙ appears when bolding multiple list items at same time', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-n6a5asuonlcdc2xmndl2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371774369, 'spacePHID': None, 'dateCreated': 1371738780, 'dateModified': 1371774369, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49877', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Existing image inclusions are duplicated and truncated by VisualEditor', 'description': {'raw': 'In the following edits, images that were already in the article were duplicated on save, and the duplicate was truncated:\\n\\nhttps://fr.wikipedia.org/w/index.php?diff=94163829\\nhttps://www.mediawiki.org/w/index.php?diff=713109\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371721408, 'spacePHID': None, 'dateCreated': 1371654120, 'dateModified': 1371721408, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49824', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid cannot parse some wikimarkup', 'description': {'raw': 'See https://en.wikipedia.org/wiki/User:Kephir/acid\\n\\nIn the VE: https://en.wikipedia.org/wiki/File:MediaWiki_acid_markup_-_VisualEditor.png\\nIn the normal, rendered page: https://en.wikipedia.org/wiki/File:MediaWiki_acid_markup_-_native_rendering.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371660571, 'spacePHID': None, 'dateCreated': 1371645900, 'dateModified': 1372934053, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49810', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: IE8 support', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371656351, 'spacePHID': None, 'dateCreated': 1371633600, 'dateModified': 1371658981, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49802', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Insert media create link to undefined', 'description': {'raw': 'https://en.wikipedia.org/?diff=560548908\\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'}, 'authorPHID': 'PHID-USER-ixwg3kf22idjy7x4ncxf', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371627753, 'spacePHID': None, 'dateCreated': 1371612300, 'dateModified': 1417571160, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49795', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: strange artefact in monobook when resizing images', 'description': {'raw': 'Screenshot\\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.\\n\\nWindows 7, Firefox 21.0\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11696}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373155495, 'spacePHID': None, 'dateCreated': 1371584640, 'dateModified': 1417571081, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49768', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE providing unasked-for removal of \"duplicate\" formatting', 'description': {'raw': 'See (ferinstance) https://en.wikipedia.org/w/index.php?title=User:JohnCD/draft&diff=560430675&oldid=560430611\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371574643, 'spacePHID': None, 'dateCreated': 1371574560, 'dateModified': 1371574643, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49756', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid uses nowiki tags for positional template parameters with '='s rather than just explicitly declaring them\", 'description': {'raw': '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}}.\\n\\nNow, 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|<nowiki>foo=bar</nowiki>|baz}}. However, \"foo=bar\" and \"<nowiki>foo=bar</nowiki>\" are not equivalent wikitext. For example, nowiki tags will break wikilinks.\\n\\nThere\\'s an example of the difference in this diff:\\nhttps://www.mediawiki.org/w/index.php?title=VisualEditor:Template_test&diff=712906&oldid=712905\\n\\nSee the effects for the revisions before and after (look at the \"Inline template\" section).\\n\\nBefore: https://www.mediawiki.org/w/index.php?title=VisualEditor:Template_test&oldid=712905\\nAfter: https://www.mediawiki.org/w/index.php?title=VisualEditor:Template_test&oldid=712906\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-rjtk3h6l2quifuajiime', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373561023, 'spacePHID': None, 'dateCreated': 1371545100, 'dateModified': 1373561023, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49739', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: visual representation of template breaks on 'apply changes'\", 'description': {'raw': 'Screenshot\\n\\nSee 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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11624}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372015399, 'spacePHID': None, 'dateCreated': 1371532800, 'dateModified': 1372015399, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49730', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable voting in VisualEditor product', 'description': {'raw': 'If I want to track a bug, I can just vote for it. This is pretty common practice, as I understand it. \\n\\nBut voting seems to be disabled in the VisualEditor product. Can we have it please?\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371527182, 'spacePHID': None, 'dateCreated': 1371524400, 'dateModified': 1371527182, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49728', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Possible to insert empty DEFAULTSORT', 'description': {'raw': 'Go to <https://test.wikipedia.org/wiki/IPod?veaction=edit>.\\n\\nClick \"Page settings\", enter \"hello\" for the default sort key, click \"Apply changes\".\\n\\nClick \"Page settings\", clear the default sort key, click \"Apply changes\".\\n\\nReview your changes. VisualEditor wants to insert \"{{DEFAULTSORT:}}\" into the page. I don\\'t think we want this behavior.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371845516, 'spacePHID': None, 'dateCreated': 1371514380, 'dateModified': 1417571089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49724', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Special:Contributions lists spurious AFT entries and takes 20 more seconds to load', 'description': {'raw': 'The 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: <https://en.wikipedia.org/w/index.php?limit=500&tagfilter=visualeditor&title=Special%3AContributions&contribs=newbie&target=&namespace=8&nsInvert=1&tagfilter=visualeditor&year=2013&month=-1>\\n\\n--------------------------\\n**Version**: master\\n**Severity**: major\\n**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'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-kms5nmb5gvqzcdep3cnl', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371566599, 'spacePHID': None, 'dateCreated': 1371500220, 'dateModified': 1374736115, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49714', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Can not create references on some pages', 'description': {'raw': '**Author:** `rachelqa99`\\n\\n**Description:**\\nOn this page, we cannot create a reference:   https://www.mediawiki.org/wiki/User:Cmcmahon%28WMF%29/references_bug\\n\\nWe can create a reference on this page: https://www.mediawiki.org/wiki/User:Rachel99/VisualEditor_Feature_Test_Charter/refs_demo\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371570816, 'spacePHID': None, 'dateCreated': 1371490500, 'dateModified': 1371572897, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49706', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Edit with VisualEditor duplicates content with subst'd version of the content\", 'description': {'raw': 'A user reported this edit\\n<https://pt.wikipedia.org/w/index.php?title=CMM_-_Canal_Meninos_e_Meninas&diff=36129698&oldid=36129686>, where he just meant to delete a sentence. However the content was duplicated and templates were substituted in this duplicated version.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-vyidforzdhnrsoweujao', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371515540, 'spacePHID': None, 'dateCreated': 1371485940, 'dateModified': 1372934032, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tables with a faulty <tr> at their end display it, confusing users', 'description': {'raw': 'See https://en.wikipedia.org/wiki/Daryle_Singletary?veaction=edit - the first three (but strangely, not the last) discography tables.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371496639, 'spacePHID': None, 'dateCreated': 1371470220, 'dateModified': 1371497885, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49691', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template displaying in the incorrect language', 'description': {'raw': \"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).\\n\\nI have no idea what's going on, but this seems pretty important to solve for.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371510441, 'spacePHID': None, 'dateCreated': 1371468780, 'dateModified': 1371510441, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49687', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: nowiki tags added to references (and references split up (and content dropped))', 'description': {'raw': '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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371671665, 'spacePHID': None, 'dateCreated': 1371466320, 'dateModified': 1372934078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49684', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unexpected padding', 'description': {'raw': 'See the tabs on https://en.wikipedia.org/wiki/User:Panpog1 for example.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372015377, 'spacePHID': None, 'dateCreated': 1371466080, 'dateModified': 1372015377, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49683', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'UniversalLanguageSelector Does not work with VisualEditor', 'description': {'raw': '**Author:** `bellayet`\\n\\n**Description:**\\nAt bn Wikipedia ULS does not working with recently added VisualEditor beta.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371409196, 'spacePHID': None, 'dateCreated': 1371403200, 'dateModified': 1371409196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49643', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor bugzilla component should be under MediaWiki extensions', 'description': {'raw': 'I failed to find it under extensions where I was expecting it to be.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371416756, 'spacePHID': None, 'dateCreated': 1371382800, 'dateModified': 1371422998, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49637', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Use the wikitext editor for editing sections while VisualEditor is in beta\" should be default', 'description': {'raw': 'The preference \"Use the wikitext editor for editing sections while VisualEditor is in beta\" should be enabled by default.\\n\\nMore 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.\\n\\nAnother possibility is to have two section edit links, like it is at the top of the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49666'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372279685, 'spacePHID': None, 'dateCreated': 1371315060, 'dateModified': 1417571085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49621', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Implement the same EventLogging of page edits in wikitext editor as in VisualEditor for comparison purposes', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371507422, 'spacePHID': None, 'dateCreated': 1371231960, 'dateModified': 1371507422, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49587', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Configure VisualEditor for section edit links to go to VisualEditor by default', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371161579, 'spacePHID': None, 'dateCreated': 1371155460, 'dateModified': 1371161579, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49547', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switch over to handle mw:WikiLink/Interwiki', 'description': {'raw': 'Currently links with mw:WikiLink/Interwiki get alienated\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371150585, 'spacePHID': None, 'dateCreated': 1371150540, 'dateModified': 1417571161, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49545', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: valid links are redlinked in the link inspector', 'description': {'raw': \"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'.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371153385, 'spacePHID': None, 'dateCreated': 1371145680, 'dateModified': 1371153385, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49540', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Extension tags starting with a capital (<Gallery>) seem to confuse the parser', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=User:TheDJ/sandbox&oldid=559712952\\n\\nTry adding a gallery that was made using <Gallery></Gallery>\\n\\nAnything following the opening <Gallery> 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\\n\\n\\nDiscussion: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=559712784#Spurious_gallery_tags\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371254899, 'spacePHID': None, 'dateCreated': 1371125760, 'dateModified': 1372934067, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49525', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Mass of extraneous quot and amp marks', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372014851, 'spacePHID': None, 'dateCreated': 1371117420, 'dateModified': 1372014851, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49522', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add the ability to drag highlighted text around with the mouse', 'description': {'raw': 'As requested at https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=559578396&oldid=559577689\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371058332, 'spacePHID': None, 'dateCreated': 1371058200, 'dateModified': 1380609083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49486', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Red links show as blue links in VisualEditor', 'description': {'raw': 'When editing for example http://pt.wikipedia.org/wiki/Rana with the VisualEditor, all the red links are shown as blue links.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-vyidforzdhnrsoweujao', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371049016, 'spacePHID': None, 'dateCreated': 1371027000, 'dateModified': 1371049016, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49475', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'new schedule for Jenkins jobs', 'description': {'raw': '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.  \\n\\nI 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. \\n\\nThen 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'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372762967, 'spacePHID': None, 'dateCreated': 1370906580, 'dateModified': 1372763433, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49418', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Linking to an image results in the image being loaded', 'description': {'raw': 'The 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11725}'}, 'authorPHID': 'PHID-USER-ixwg3kf22idjy7x4ncxf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370883912, 'spacePHID': None, 'dateCreated': 1370856240, 'dateModified': 1370883912, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49384', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Inconsistency in the URL (veaction=edit disappears)', 'description': {'raw': 'To edit an article using the VE, the URL is \"...?veaction=edit\".\\n\\nBut, by loading the page with the VE, the URL is changed and becomes the same than the one to display the article.\\n\\nThere is consequently an inconsistency between the URL and the page content.\\n\\n\"?veaction=edit\" and all other URL parameters should not be changed/removed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nwa6c3hm5nmv7ixrih4p', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370840639, 'spacePHID': None, 'dateCreated': 1370689740, 'dateModified': 1370840639, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49336', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Configure beta and MW.org to have $wgVisualEditorEnableExperimentalCode = true;', 'description': {'raw': \"VisualEditor's new features should be exposed for testing outside of our local development environments.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370741026, 'spacePHID': None, 'dateCreated': 1370270880, 'dateModified': 1370741026, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49084', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Various submodules in mediawiki/extensions are not being automatically updated', 'description': {'raw': \"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.\\n\\nFor example, let's take the message Visualeditor-linkinspector-suggest-matching-page:\\n\\n1. Update in transatewiki.net: https://translatewiki.net/w/i.php?title=MediaWiki%3AVisualeditor-linkinspector-suggest-matching-page%2Fhe&diff=4721642&oldid=4682586\\n\\n2. Commit to Gerrit: https://gerrit.wikimedia.org/r/#/c/63552/1/VisualEditor.i18n.php (line 1661)\\n\\n3. Still not updated in he.wikipedia: https://he.wikipedia.org/w/index.php?title=Special:AllMessages&prefix=visu&filter=modified&lang=he&limit=5000\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374227951, 'spacePHID': None, 'dateCreated': 1369745520, 'dateModified': 1602870013, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48893', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor misrepresents linked files as embedded inline, when editing', 'description': {'raw': '**Author:** `swalling`\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369114571, 'spacePHID': None, 'dateCreated': 1369114380, 'dateModified': 1417571163, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48669', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Enable section-editing on 'beta' profile of VisualEditor deployments\", 'description': {'raw': \"(This is only for action in the immediate run-up to VisualEditor deployment as beta.)\\n\\nThe 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371169125, 'spacePHID': None, 'dateCreated': 1369078800, 'dateModified': 1371169125, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48658', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"MediaWiki:Visualeditor-feedback-link doesn't use wiki language\", 'description': {'raw': 'Feedback gets submitted to a page given by the message MediaWiki:Visualeditor-feedback-link. The link can differ from language to language.\\nBut feedback gets submitted to the link for the user-chosen interface language, not the wiki/content language and so hitting different pages.\\n\\nex.:\\ngerman interface: https://de.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/R%C3%BCckmeldungen&diff=prev&oldid=118691535\\nenglish interface: https://de.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=prev&oldid=118691557\\n\\nThis may apply to other messages as well\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-jcypqodpdpbcicgwgh7j', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369068249, 'spacePHID': None, 'dateCreated': 1369067700, 'dateModified': 1369068249, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48645', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor expanding image links', 'description': {'raw': 'Screenshot of the English Wikipedia using VisualEditor, 2013-05-18\\n\\nVisualEditor seems to be expanding certain image links. Screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11087}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368979809, 'spacePHID': None, 'dateCreated': 1368849600, 'dateModified': 1368979809, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48596', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: API doesn't suggest thinks for string length <= 2, so don't show the suggestions box for links/categories/etc.?\", 'description': {'raw': 'Not sure how to proceed on this one.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368747382, 'spacePHID': None, 'dateCreated': 1368746160, 'dateModified': 1417571165, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48558', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'List looks like it has extra empty lines', 'description': {'raw': '1. Edit http://en.wikipedia.org/wiki/Refrigerator\\n2. Look at the list in paragraph \"Production by country\"\\n\\nThe list has extra empty lines, some with a bullet, some without.\\n\\nThe saved wikicode is OK, though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369080566, 'spacePHID': None, 'dateCreated': 1368684120, 'dateModified': 1417571164, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48527', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Expose order of template parameters call', 'description': {'raw': '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.\\n\\nAnd per the JSON specification (and as proven by inconsistent behaviour in different browsers), objects are \"an unordered set of name/value pairs\"[1].\\n\\nAnd 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.\\n\\nThough Parsoid is able to roundtrip the order (since it has the original wikitext and can put them in the right order), we can\\'t.\\n\\nI\\'d recommend the output is updated to output an array of some kind.\\n\\nSo 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] http://json.org/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368662919, 'spacePHID': None, 'dateCreated': 1368662520, 'dateModified': 1368662919, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48523', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Can not paste new link anchor', 'description': {'raw': \"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.\\n\\nYou can't use the link dialog for this either, since there is no anchor field.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368726943, 'spacePHID': None, 'dateCreated': 1368583740, 'dateModified': 1417583714, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48489', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor adds ↵ when editing user .js and .css pages', 'description': {'raw': '**Author:** `the.anonymouse.wikimedia`\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10832}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368569378, 'spacePHID': None, 'dateCreated': 1368565440, 'dateModified': 1368608655, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48471', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor link tool incorrectly shows a red link', 'description': {'raw': 'VisualEditor link dialog box incorrectly showing red text, 2013-05-13\\n\\nGo to <https://www.mediawiki.org/wiki/Sysadmin_hub>. 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10762}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368720868, 'spacePHID': None, 'dateCreated': 1368500280, 'dateModified': 1417571165, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48433', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"visualeditor-diff-nochanges\" exposed on mediawiki.org', 'description': {'raw': 'VisualEditor message key exposed on mediawiki.org, 2013-05-13\\n\\nURL: <https://www.mediawiki.org/wiki/MobileFrontend/Photo_upload/Analysis>\\n\\nError: see attached screenshot\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10756}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368545353, 'spacePHID': None, 'dateCreated': 1368497760, 'dateModified': 1368545353, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48431', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When the edit tab is replaced it breaks active/selected states and doesn\\'t replace \"Create\" tabs properly.', 'description': {'raw': '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.\\n\\nAdditionally on a non existent page \"Create\" gets replaced with \"Edit source\" instead of something like \"Create source\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-gibrlx54k2riiuit5paf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368150918, 'spacePHID': None, 'dateCreated': 1368150660, 'dateModified': 1417571163, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48316', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: HTML comment with immediately following table has newline split removed', 'description': {'raw': \"As per Subbu's report. (The corrupted table is going to be a different bug.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n**URL**: http://parsoid.wmflabs.org/_rt/en/BMW_801\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367944050, 'spacePHID': None, 'dateCreated': 1367872680, 'dateModified': 1372934001, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48179', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adjacent annotations which are equal by name but not reference do not serialise correctly.', 'description': {'raw': \"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\\n<b>Bold on load text</b><b>added text</b>\\n\\nWhich Parsoid converts to\\n\\n'''Bold on load text''''''added text'''\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367871652, 'spacePHID': None, 'dateCreated': 1367774100, 'dateModified': 1417571166, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48110', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Extra tags got inserted causing infobox layout to be broken', 'description': {'raw': '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\\n\\nAll change done manually is the insertion of \"编辑器测试\" at the first diff, then those extra </span> and </table> got added automatically.\\n\\nWhere\\'s that \"partial serialization\" mentioned before?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367545048, 'spacePHID': None, 'dateCreated': 1367290980, 'dateModified': 1367545048, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47860', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unread message notification will not mark itself read', 'description': {'raw': 'I have \"1 notice\", \"You are using an alpha version....\".\\n\\n1. Clicking the notice, it pops up.\\n2. Click the message contents, the popup hides.\\n\\n\"1 notice\" remains.  Maybe it will go away when I save the page I\\'m editing?\\n\\n3. Save the page, and edit again.\\n\\nThe notice is still there, and even expands when the editor is started.  Blargh!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367544785, 'spacePHID': None, 'dateCreated': 1367215380, 'dateModified': 1367544785, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47816', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'RTL Support for VisualEditor', 'description': {'raw': 'Add RTL support for page-, paragraph- and block-level elements in VisualEditor, as well as support for multi-language use in articles.\\n\\nFull proposal (GSoC2013 project) is available here: http://www.mediawiki.org/wiki/User:Mooeypoo/GSOC_2013_Proposal:_RTL_Support_in_VisualEditor\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367268091, 'spacePHID': None, 'dateCreated': 1367205180, 'dateModified': 1367268091, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47814', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[VisualEditor] CSS and JS pages should only be editable using the source editor', 'description': {'raw': '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.\\n\\n(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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367097296, 'spacePHID': None, 'dateCreated': 1367047080, 'dateModified': 1417571166, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47768', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Feedback is broken', 'description': {'raw': \"**Author:** `benedix`\\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:\\nhttp://www.youtube.com/watch?v=Zzt_2CBfTNI (35 seconds)\\n\\nThe feedback is sent to http://parsoid.wmflabs.org/_bugs/ but the request is canceled after a few seconds. \\n\\n\\nBtw. There is no visual feedback to the user that shows him to wait while the request is pending.\\n\\n\\nLukas\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367222196, 'spacePHID': None, 'dateCreated': 1367013780, 'dateModified': 1367222196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page', 'description': {'raw': 'See the URL for a demo.\\n\\nThe last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.\\n\\nIn the output page it is shown as \"1. 1. 1. 1. 1. 1. 1. A\".\\n\\nIn the VE it is shown as\\n1.\\n 1.\\n  1.\\n   1.\\n    1.\\n     1.\\n      1. A\\n\\nThis is an edge case but it should should probably be identical in any case.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367009441, 'spacePHID': None, 'dateCreated': 1367008080, 'dateModified': 1417571167, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47751', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Adding a hyperlink to an exsisting page deletes the line. The link doesn't get inserted (undefined)\", 'description': {'raw': '**Author:** `mh87`\\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.\\n\\nWhen 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'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366741802, 'spacePHID': None, 'dateCreated': 1366719660, 'dateModified': 1417571167, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47546', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dirty diffs with FF, but not in Chrome on pages with citations', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366391720, 'spacePHID': None, 'dateCreated': 1366388640, 'dateModified': 1366391720, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47419', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Problem with placing cursor inside slug (inline|block) with mouse', 'description': {'raw': '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).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366059192, 'spacePHID': None, 'dateCreated': 1366058760, 'dateModified': 1417571169, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47258', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add whitespace skipping to UnicodeJS.wordbreak for word skipping functionality', 'description': {'raw': \"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:\\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\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366142624, 'spacePHID': None, 'dateCreated': 1364916660, 'dateModified': 1417571169, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46794', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow nodes to handle their own children', 'description': {'raw': 'DM nodes should be able to handle their own children, rather than having the converter do it for them.\\n\\nThis 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.\\n\\nReflecting this, CE nodes should be able to take control of the rendering of their children as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366130702, 'spacePHID': None, 'dateCreated': 1364433480, 'dateModified': 1417571170, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46619', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor to edit infobox text fields', 'description': {'raw': 'Currently VisualEditor users can\\'t touch infoboxes. It would be great to have edit access to the text fields of infoboxes.\\n\\nBeing able to update images would be a plus.\\n\\nModification of the infobox itself (e.g. addition of new fields) is out of scope here.\\n\\n\\nI\\'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.\"\\nhttp://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#On-site_editing\\n\\nBy the time those Wikipedia infoboxes would be filled with Wikidata data, \\n\"easy editing\" should be provided by VisualEditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364167729, 'spacePHID': None, 'dateCreated': 1364167560, 'dateModified': 1364167729, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46520', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Generalise the Parsoid structure and internal representations.', 'description': {'raw': 'So Molly and I are at LibrePlanet talking about bug 37933.\\n\\nWe 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.\\n\\nObviously 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.\\n\\n2. 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.\\n\\nFootnote: 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.\\n\\nI\\'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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364323385, 'spacePHID': None, 'dateCreated': 1364163180, 'dateModified': 1454003905, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46516', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Just added single character, but at review all content is replaced', 'description': {'raw': 'Steps:\\n\\n1) Go to http://en.wikipedia.org/wiki/Jean_Nicolas\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364127463, 'spacePHID': None, 'dateCreated': 1364127180, 'dateModified': 1417571170, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46506', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Clicking outside of link edition popup removes link', 'description': {'raw': 'Steps:\\n\\n1) Go to http://en.wikipedia.org/wiki/Nicolas\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364164432, 'spacePHID': None, 'dateCreated': 1364126940, 'dateModified': 1417571170, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46505', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: store annotations in a document-wide index/value store and serialize as integer indexes', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366130603, 'spacePHID': None, 'dateCreated': 1363693320, 'dateModified': 1417571169, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46320', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Jenkins: Parsoid server check gets killed because of Jenkins' paranoia (re: file descriptors)\", 'description': {'raw': '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.\\n\\nDo 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://integration.mediawiki.org/ci/view/All/job/parsoid-server-sanity-check/'}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375350900, 'spacePHID': None, 'dateCreated': 1363637880, 'dateModified': 1454003942, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46296', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Incorrect rendering for [[Template:Disambiguation]]', 'description': {'raw': 'Screenshot of {{disambiguation}} on [[Loco]] at en.wikipedia.org\\n\\nUsing {{disambiguation}} on a page and editing it with VisualEditor shows an incorrect rendering.\\n\\nAttached are screenshots and dumps of the active DOM for the PHP parser and Parsoid/VisualEditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10462}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361832255, 'spacePHID': None, 'dateCreated': 1361749260, 'dateModified': 1454004087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45341', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid: Tables don't round-trip cleanly\", 'description': {'raw': '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.)\\n\\n* 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'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360889187, 'spacePHID': None, 'dateCreated': 1360879800, 'dateModified': 1454004124, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45024', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid crashes when serializing page with colon in title', 'description': {'raw': \"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:\\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.)\\n\\nFor this case, the Parsoid log shows:\\nParserError: Failed to parse the JSON response for Page Fetch null\\nworker 10132 died, restarting.\\n\\n\\nPOST /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.\\nError: 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].<anonymous> (/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].<anonymous> (/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\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360785028, 'spacePHID': None, 'dateCreated': 1360784520, 'dateModified': 1454004141, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44969', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE chokes on unexpected redirect response from Parsoid', 'description': {'raw': '**Author:** `phil`\\n\\n**Description:**\\nI created a page using the normal editor that was\\n\\n\\n<gallery>\\nFile:Example.jpg|Caption1\\n#REDIRECT [[Target page name]]\\n</gallery>\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1362769118, 'spacePHID': None, 'dateCreated': 1360730040, 'dateModified': 1417571171, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44927', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Multiple toolbars created if tabs switched before initialization is complete', 'description': {'raw': \"**Author:** `mwalker`\\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.\\n\\nI note that the page DOM becomes more and more unusable as I keep switching.\\n\\nAs 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360976726, 'spacePHID': None, 'dateCreated': 1360462980, 'dateModified': 1417571171, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44838', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: What Heading levels are offered should flex based', 'description': {'raw': '**Author:** `phil`\\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'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360376842, 'spacePHID': None, 'dateCreated': 1360297620, 'dateModified': 1417571172, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44780', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Linktrails should get a <nowiki /> added on serialisation', 'description': {'raw': '**Author:** `phil`\\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.\\nI 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}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360704683, 'spacePHID': None, 'dateCreated': 1360296540, 'dateModified': 1454004346, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44779', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Opening link inspector without selection in stand alone instance throws error.', 'description': {'raw': \"Open stand alone editor.  Trigger LinkInspector with cmd/ctrl+k or LinkInspector button.\\n\\nUncaught 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\"}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360105358, 'spacePHID': None, 'dateCreated': 1360091400, 'dateModified': 1417571172, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44686', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unexpected behavior when line starts with space', 'description': {'raw': 'nowiki tags\\n\\nedit a line in VE such that it starts with a space\\n\\nVE unexpectedly inserts <nowiki> 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 <nowiki> 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}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360208015, 'spacePHID': None, 'dateCreated': 1359487500, 'dateModified': 1424787347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44478', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid should support passing on an authenticated user's read right (when MW API supports that)\", 'description': {'raw': '**Author:** `mail`\\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 = \\'http://parsoid.wmflabs.org/\\';\\n\\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux\\n**Platform**: PC\\n**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360207511, 'spacePHID': None, 'dateCreated': 1359038700, 'dateModified': 1360207511, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44313', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'SMW: Refresh tab (purge) is always collapsed when using the Vector skin', 'description': {'raw': '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. \\n\\nHaving 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.\\n\\nEspecially for beginners it would be very helpful to make them aware of the possible need to refresh a page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-37d2msujvpp2rippbzoq', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1425405042, 'spacePHID': None, 'dateCreated': 1358094720, 'dateModified': 1454004453, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43925', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make link inspector aware of annotations, rather than just target strings', 'description': {'raw': '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.\\n\\nThis is related to bug 43063.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=43063'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358388388, 'spacePHID': None, 'dateCreated': 1357860900, 'dateModified': 1417571174, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43841', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Error loading data from server: error. Would you like to retry?\"', 'description': {'raw': '**Author:** `Coiby.Xu`\\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 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. \\nP.S. I\\'m using latest VE and Parsoid.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**OS**: Linux'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358280165, 'spacePHID': None, 'dateCreated': 1357052100, 'dateModified': 1358280165, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43566', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Empty editnotices appear as notices', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1356713507, 'spacePHID': None, 'dateCreated': 1356608820, 'dateModified': 1356713519, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43460', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Removing link trail doesn't affect the output\", 'description': {'raw': '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:\\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....\\n\\nSuggested 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.\\n\\n2. If that failed, try to find the old trail in the current text with a regex like /s$/. If you find it, emit it.\\n\\n3. 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358213523, 'spacePHID': None, 'dateCreated': 1356551700, 'dateModified': 1454004497, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'PHP Fatal error:  Call to undefined method Title::getEditNotices() in extensions/VisualEditor/ApiVisualEditor.php', 'description': {'raw': \"**Author:** `aderumier`\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1356106907, 'spacePHID': None, 'dateCreated': 1356106320, 'dateModified': 1356106907, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43323', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tooltip broken on outdent button', 'description': {'raw': '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\\n\\nChange\\nvisualeditor-outdentationbutton-outdent-tooltip\\nto\\nvisualeditor-indentationbutton-outdent-tooltip\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355942170, 'spacePHID': None, 'dateCreated': 1355898660, 'dateModified': 1417571176, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43258', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Reporter missing in IRC announcement of new issue', 'description': {'raw': 'The reporter is missing in the IRC announcements of new issues in #mediawiki.\\n\\nObserved IRC output:\\n\\n(NEW) VisualEditor: Support <hiero> extension - https://bugzilla.wikimedia.org/43118 normal; VisualEditor: General; ()\\n(NEW) File will not change from original version - https://bugzilla.wikimedia.org/43117 normal; MediaWiki: File management; ()\\n(NEW) prevent update.php from updating database schemata of wgSharedTables - https://bugzilla.wikimedia.org/43116 enhancement; MediaWiki: Installer; ()\\n\\nExpected IRC output: \"()\" replaced by \"(UserName)\":\\n\\n(NEW) VisualEditor: Support <hiero> extension - https://bugzilla.wikimedia.org/43118 normal; VisualEditor: General; (Raimond Spekking)\\n(NEW) File will not change from original version - https://bugzilla.wikimedia.org/43117 normal; MediaWiki: File management; (Adam Cuerden)\\n(NEW) prevent update.php from updating database schemata of wgSharedTables - https://bugzilla.wikimedia.org/43116 enhancement; MediaWiki: Installer; (Gregor Hagedorn)\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-w5a723w3wes6jd5wskgg', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355479865, 'spacePHID': None, 'dateCreated': 1355479740, 'dateModified': 1454004528, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43119', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor never loads', 'description': {'raw': 'After enabling the VisualEditor editing interface, as usual in the Vector skin, the tab appears but then the page actually never loads for editing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker\\n**OS**: Windows XP\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-wel3wo6tppcxgnrthxls', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355415643, 'spacePHID': None, 'dateCreated': 1355414040, 'dateModified': 1454004531, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43078', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Skip the inspector menu on links', 'description': {'raw': '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.\\n\\nEnhancement 1: provide a tooltip for the target when hovering with the mouse over a link. This will be helpful for mouse-based computing devices.\\n\\nEnhancement 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.\\n\\nI believe the link-chain-icon step can be skipped.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-grpjkpfolt5gz4ljlbfg', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355435276, 'spacePHID': None, 'dateCreated': 1355398980, 'dateModified': 1417571176, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43064', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Things are sometimes alienated as block when they should be inline', 'description': {'raw': '\"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\\n\\nBetter to use a span I think.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1357678696, 'spacePHID': None, 'dateCreated': 1355386260, 'dateModified': 1417571168, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43056', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Escape from LinkAnnotation editor closes annotation editor but leaves suggestion box floating', 'description': {'raw': 'Screenshot 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.\\n\\n\\nActual:\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10181}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355425528, 'spacePHID': None, 'dateCreated': 1355378640, 'dateModified': 1417571176, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43055', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Suggestion tool fails to close when escaping out of context menu.', 'description': {'raw': '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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355360935, 'spacePHID': None, 'dateCreated': 1355358660, 'dateModified': 1417571175, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43051', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: For initial deployment, do not over-ride edit-section links', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355829010, 'spacePHID': None, 'dateCreated': 1355344680, 'dateModified': 1417583744, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43036', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Undo just after load of the editor causes JS error.', 'description': {'raw': \"Open the editor, Hit Control/Command U.\\nThrows Exception:\\nUncaught TypeError: Cannot read property 'start' of null\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355360967, 'spacePHID': None, 'dateCreated': 1355342280, 'dateModified': 1417571199, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43033', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <visualeditor-toolbar-savedialog> message is missing', 'description': {'raw': 'Seen on the VE-editing interface of https://www.mediawiki.org/wiki/VisualEditor:Test\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355341256, 'spacePHID': None, 'dateCreated': 1355292540, 'dateModified': 1417571175, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42983', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: While using link inspector, transaction hangs and page eventually explodes.', 'description': {'raw': \"Reproduce by create a new article with VisualEditor.\\n\\nReturn down about 10 lines.\\nType some text, hit command+k (open link inspector)\\nSelect an item in the dropdown. Hit enter.\\n\\nPage 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\"}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355191424, 'spacePHID': None, 'dateCreated': 1355189160, 'dateModified': 1355192196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42935', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Inspector doesn't open properly\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355189209, 'spacePHID': None, 'dateCreated': 1355175300, 'dateModified': 1417571199, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42925', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Re-enable the feedback tool for deployment', 'description': {'raw': 'Point to [[Project:VisualEditor/Feedback]] for now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355194481, 'spacePHID': None, 'dateCreated': 1355171460, 'dateModified': 1417571200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42920', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar tooltips should also suggest key-commands', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=44012'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358469697, 'spacePHID': None, 'dateCreated': 1355168340, 'dateModified': 1417571174, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42919', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Notifications should not use db-variant of page titles', 'description': {'raw': 'Via viewPage.pageName (mw.config wgRelevantPageName)\\n\\nCreating or editing pages, the mw.notify send uses the db-variant straight from wgRelevantPageName.\\n\\nShould mw.Title.textify it for proper localisation and normalisation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354942098, 'spacePHID': None, 'dateCreated': 1354930620, 'dateModified': 1417571201, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42848', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support Internet Explorer', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1359516361, 'spacePHID': None, 'dateCreated': 1354926720, 'dateModified': 1359516372, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42847', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create a link at the beginning of the document throws rangy error', 'description': {'raw': \"Create a link at the beginning of the document, select it and open inspector.\\n\\nUncaught 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\"}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355164890, 'spacePHID': None, 'dateCreated': 1354920600, 'dateModified': 1417571159, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42842', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pre-parsed messages (minoredit, watchthis) should be in user language instead site language', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354832652, 'spacePHID': None, 'dateCreated': 1354771560, 'dateModified': 1454004556, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42764', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ext.visualEditor.specialMessages module cache invalidation broken', 'description': {'raw': '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].\\n\\n\\n> > mw.loader.getVersion(\\'ext.visualEditor.specialMessages\\')\\n> < \"20120908T000000Z\"\\n\\n\\nhttps://gerrit.wikimedia.org/r/gitweb?p=operations/mediawiki-config.git;a=blob;f=wmf-config/CommonSettings.php;h=8481e9b30130288b187cac5ebd7a6993320c91c4;hb=HEAD#l1347\\n\\nAssigning to self, being worked on. Filing as reminder and as future reference.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354654432, 'spacePHID': None, 'dateCreated': 1354596300, 'dateModified': 1454004573, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42670', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'LabeledSectionTransclusion: Fatal error:  Call to undefined method Title::getRedirectTarget()', 'description': {'raw': 'Fatal 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'}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353972863, 'spacePHID': None, 'dateCreated': 1353963360, 'dateModified': 1355073003, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42456', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Temporarily add IE to blacklist for December release as CE support is currently insufficient', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353530010, 'spacePHID': None, 'dateCreated': 1353529620, 'dateModified': 1454004643, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42335', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: i18n for alien tooltip', 'description': {'raw': 'The tooltip on aliens (\"Sorry, you can\\'t edit this with the Visual Editor\" or whatever) should be i18ned.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353114667, 'spacePHID': None, 'dateCreated': 1352940180, 'dateModified': 1454004654, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42123', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Change markers don't propagate when generated paragraphs are unwrapped\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353108588, 'spacePHID': None, 'dateCreated': 1352938800, 'dateModified': 1454004654, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42120', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] Parsoid now wrongly santising wikitext of tables', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352932611, 'spacePHID': None, 'dateCreated': 1352931660, 'dateModified': 1454004655, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42111', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Prepending to lists difficult', 'description': {'raw': 'At the moment, prepending to lists is not obvious. I think most people would try to do it by pressing enter on the preceding line to create a new paragraph, then pressing the make (bulleted) list button.\\n\\nFor some reason, this creates a list at the caret, but retains the blank paragraph afterwards (so you have list-para-list). Okay, so now you try to delete the para, but you can only deletes too much, for example merging the last list item on the first list with the first list item on the second list. In fact, pressing enter now works, but in any case the process is rather confusing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-n6a5asuonlcdc2xmndl2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352935201, 'spacePHID': None, 'dateCreated': 1352551740, 'dateModified': 1454004669, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41965', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Restore lost Change Markers', 'description': {'raw': 'In the change-markers2 branch, we have some trouble.\\n\\nIn a list item, there will be a <p> tag with change markers if I edit the content of the <li>. Roan decided to destroy those, and so did I. The change markers should instead be propagated to the <li>.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353107930, 'spacePHID': None, 'dateCreated': 1352509140, 'dateModified': 1454004671, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41947', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Post-uirewrite, list button does not behave as expected', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352499455, 'spacePHID': None, 'dateCreated': 1352499300, 'dateModified': 1454004671, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41936', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Overflow and background messed up in save dialog workflow', 'description': {'raw': 'Screenshot\\n\\nSee screenshot. Legal text is floating loose, and the heading in the toolbar is overlapping the buttons.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9759}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352466731, 'spacePHID': None, 'dateCreated': 1352465220, 'dateModified': 1454004674, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41918', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parsoid is sent text outside of any node for the first line of a new article', 'description': {'raw': 'Steps to repro:\\n\\n1. Open new page in VE.\\n\\n2. Click on first line, enter text, enter newline, enter more text.\\n\\n3. Click save.\\n\\nExpected behavior: Two paragraphs.\\n\\nActual behavior: One paragraph with a single line break where there should be two.\\n\\nTested locally and found that Parsoid\\'s web service gets the DOM as something like \"First line<p>Second line</p>\", which it can\\'t handle correctly (the fix breaks many other parser tests).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353133977, 'spacePHID': None, 'dateCreated': 1352420400, 'dateModified': 1454004674, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41905', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Please remove mw:Placeholder wrapper for first newline in <pre>', 'description': {'raw': 'Parsoid currently wraps the first newline in a <pre> in <span typeof=\"mw:Placeholder\"> , see also bug 41725 where I reported a bug in this behavior. Because of the way this interacts with VisualEditor, I would like Parsoid to drop this wrapping altogether. The reason for mw:Placeholder wrapping is supposed to be to protect things from VE, but we don\\'t need it here and it\\'s actually causing problems.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352225021, 'spacePHID': None, 'dateCreated': 1351978800, 'dateModified': 1454004689, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41753', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deal with mw:Placeholder span wrapping the first newline in a <pre>', 'description': {'raw': 'To distinguish between <pre>Foo</pre> and <pre>\\\\nFoo</pre>, Parsoid gives us HTML like <pre><span typeof=\"mw:Placeholder\">\\\\n</span>Foo</pre> for the latter. We don\\'t currently have any special handling for this placeholder in VE, so it shows up as an inline alien.\\n\\nI\\'m asking the Parsoid team to remove it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352492571, 'spacePHID': None, 'dateCreated': 1351915500, 'dateModified': 1454004693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41727', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: z-index problems in Monobook', 'description': {'raw': 'Screenshot of messed-up Monobook integration in Chrome\\n\\nThe VE integration in Monobook is messed up, see screenshot. The toolbar is positioned too high, obscuring the content actions tab bar, except for the edit tab which protrudes through the toolbar. The toolbar is also off to the left a bit. The font size in the edit area is way too small, and the font size in the save dialog is way too big.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10131}'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372893825, 'spacePHID': None, 'dateCreated': 1351914420, 'dateModified': 1454004693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41726', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Newlines in <pre> render wrongly', 'description': {'raw': 'Given the following wikitext:\\n\\n\\n<pre>\\nFoo\\nBar\\nBaz\\nQuux\\n</pre>\\n\\nthe CE rendering I get is a pre with Foo↵Bar↵Baz↵Quux , rather than a pre with actual line breaks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354155736, 'spacePHID': None, 'dateCreated': 1351912620, 'dateModified': 1454004693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41724', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Converting format across 2 lists with paragraphs in between fails', 'description': {'raw': \"1. Create a list, 2 paragraphs and then another list\\n2. Select from inside the first list to inside the second list\\n3. Change the format to Heading 2 using the toolbar\\n4. See errors in the console\\n\\nThis is to do with a bug in the ve.FormatAction class's convert function.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1351290052, 'spacePHID': None, 'dateCreated': 1351282140, 'dateModified': 1454004733, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41434', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Emptying paragraph in Firefox with backspace adds <br _moz_dirty>', 'description': {'raw': \"**Author:** `orbit`\\n\\n**Description:**\\nFirefox naturally leaves a <br _moz_dirty> when the contents of a paragraph has been deleted. There are 2 cases, deleting text in a paragraph and deleting text in a paragraph in a list item.\\n\\nIn the case of a paragraph NOT within a list item, the DOM is:\\n<p><br _moz_dirty></p>. ve.ce.TextNode onUpdate cleans the parent, removing the <br>. \\n\\nIn the case of a paragraph WITHIN a list item, the DOM is:\\n<li><p></p><br _moz_dirty></li>. Cleaning the parent doesn't remove the br, but parent.parent does. Maybe this needs to traverse up to the highest splittable node? \\n\\nIn both cases the focus does not return to the slug because the surface is locked, preventing showSelection (this is in the onChange method).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354755521, 'spacePHID': None, 'dateCreated': 1350672600, 'dateModified': 1454004754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41223', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: First 'space' in Firefox strands previous content in DIV outside of P element in new document\", 'description': {'raw': 'Go to a non-existent document and press \\'Create\\'\\n\\n1) Press a\\n   Expect: \"a\" in a <P> element\\n   Get: \"a\" in a <P> element\\n2) Press <space>\\n   Expect: \"a \" in a <P> element\\n   Get: \"a\" in the document <DIV> followed by a newline, then \" \" in a <P> element\\n3) Press b\\n   Expect: \"a b\" in a <P> element\\n   Get: \"a\" in the document <DIV> followed by a newline, then \" b\" in a <P> element\\n4) Press <enter>\\n   Expect: \"a b\" in a <P> element; a newline; then a <P> with a slug <SPAN>\\n   Get: \" b\" in a <P> element; a newline; a <P> with a slug <SPAN>; another newline; then \"a\" in the document <DIV>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350583392, 'spacePHID': None, 'dateCreated': 1350582840, 'dateModified': 1454004758, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41181', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting selection does not delete selected list bullet', 'description': {'raw': '1) Open http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Press: a b Enter c d\\n3) Make \"cd\" a list item\\n4) Press Delete\\n\\n\\nExpected:\\n\\nad\\n\\n\\nActual:\\n\\na\\n\\n・ d\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350672888, 'spacePHID': None, 'dateCreated': 1350553800, 'dateModified': 1454004763, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41158', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tooltips for Remove/OK/Cancel buttons in link dialog', 'description': {'raw': 'The available actions in the link dialog are 3 icon-only buttons (see attachment):\\n- \"no parking\" symbol\\n- check symbol\\n- cross symbol\\n\\nThe difference between \"no parking\" and \"cross\" is not obvious.\\nI had to try each to see which one means cancel and which one means \"remove link\".\\n\\nMy point is: Tooltips would be useful here.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354758675, 'spacePHID': None, 'dateCreated': 1350546360, 'dateModified': 1454004763, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41153', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Firefox is not displaying cursor in slugs', 'description': {'raw': '**Author:** `orbit`\\n\\n**Description:**\\nSteps to reproduce:\\nPlace cursor at the end of a paragraph.\\nHit \"Enter\" to create a new paragraph.\\nCursor is not shown in the new paragraph.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350502148, 'spacePHID': None, 'dateCreated': 1350496140, 'dateModified': 1454004767, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41120', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'CTRL-X does not remove selected text', 'description': {'raw': 'Steps:\\n1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Select a word or character\\n3) Press CTRL-X or select \"Cut\" in the context menu\\n4) Text is copied, but not removed\\n\\nIt guess many Wikimedia editors use cut-paste to reorder information, so it seems like a rather important feature to have.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350455700, 'spacePHID': None, 'dateCreated': 1350437460, 'dateModified': 1454004770, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41092', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn ♙ appears when deleting two paragraphs', 'description': {'raw': 'Steps:\\n1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Press: a Enter b Enter c Enter d Enter (that creates 4 paragraphs, each containing a single letter)\\n3) With the mouse, select b and c\\n4) Press Delete\\n5) Wild pawn appears ♙\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=41067'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366667522, 'spacePHID': None, 'dateCreated': 1350379140, 'dateModified': 1454004773, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41073', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Content not entirely deleted by pressing CTRL+A then Delete', 'description': {'raw': '1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Put your cursor anywhere in the text\\n3) Press CTRL+A to select everything\\n4) Press Delete\\n5) PROBLEM: Nothing happens. No content is removed.\\n\\nPressing Backspace instead of Delete works, though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350692324, 'spacePHID': None, 'dateCreated': 1350378600, 'dateModified': 1454004773, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41072', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace does not work after removing all content', 'description': {'raw': '1) Go to http://www.mediawiki.org/wiki/Special:VisualEditorSandbox with Firefox\\n2) Put your cursor anywhere in the text\\n3) Press CTRL-A (or select all text with the mouse)\\n4) Press \"Backspace\". All content disappears.\\n5) Type \"a\".\\n6) Press \"Backspace\". Problem: \"a\" is not removed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354217422, 'spacePHID': None, 'dateCreated': 1350378480, 'dateModified': 1454004774, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41071', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace in list: deleted character re-appears', 'description': {'raw': 'Steps:\\n0) Go to http://www.mediawiki.org/wiki/VisualEditor:Test\\n1) Between two simple text paragraph, insert a new paragraph by pressing \"Enter\".\\n2) Click the \"bullet list\" button.\\n3) Type \"a\".\\n4) Press \"Backspace\". \"a\" is removed, and the next paragraph moves down a bit.\\n5) Press \"Backspace\" again.\\n6) The \"a\" reappears.\\n\\nProblems: The move at step 4 and the miracle at step 6.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350669248, 'spacePHID': None, 'dateCreated': 1350376200, 'dateModified': 1454004777, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41066', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor appears misplaced after adding item to list', 'description': {'raw': 'Steps:\\n1) Open http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Click at the end of any list item\\n3) Press Enter\\n4) As expected, a new line is created in the list\\n5) PROBLEM: This cursor blinks at the beginning of the previous line (the one in which the cursor was before pressing Enter\\n6) When I begin typing, the text appears in the new line, so I guess the \"real cursor\" is actually at the right place, but its visualisation is misplaced.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350604430, 'spacePHID': None, 'dateCreated': 1350361740, 'dateModified': 1454004777, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41064', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: SHIFT-LEFT deletes text in lists', 'description': {'raw': 'Steps to reproduce:\\n1) Open http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Press \"Edit\"\\n3) Click at the end of any item in a list\\n4) Press SHIFT and LEFT, maintaining them pressed for a while\\n\\nExpected behavior: Text is selected\\nActual behavior: Text is deleted, leaving only some fragments near the bullets\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350377650, 'spacePHID': None, 'dateCreated': 1350356940, 'dateModified': 1454004777, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41062', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Pasting text doesn't work\", 'description': {'raw': \"I'm testing on mediawiki.org but am creating a bug report since these haven't been mentioned before so I don't believe they've been fixed in git.\\n\\nIf I try to paste some text in the editor, the paragraphs in it get stuck together, and it gets '↵' character inserted periodically, at places not corresponding to any line breaks in the text. Example:\\n\\nIf you want your user to be able to configure your extension, you'll ↵need to provide one or more configuration variables. It is a good idea ↵to give those variables a unique name. They should also follow MediaWiki↵ naming conventions\\n\\nThis happens both with pasting with Ctrl+v and with mouse. Firefox 16.0.1 on Windows XP SP 2.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-asiusr6cw73okn35tobw', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350601375, 'spacePHID': None, 'dateCreated': 1350339660, 'dateModified': 1454004778, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41055', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"There's no way to specify the directionality of a paragraph\", 'description': {'raw': 'In MediaWiki pages it is frequently required to write a paragraph in a different\\nlanguage, and possibly also with different directionality. For example, a\\nquotation in English in an article in the Hebrew Wikipedia.\\n\\nWith the plain wikitext editor this can be achieved using HTML, for example\\n<div lang=\"en\" dir=\"ltr\">. In some Wikipedias there are templates that do\\nthis.\\n\\nThere must be a way to do this using the VE GUI. For example, the user can\\nselect the text in a different language, open a dialog with \"Paragraph language\\nproperties\" and select \"Language: English\" and \"Directionality: Left-to-right\".\\n\\nFor reference and further details:\\nhttps://www.mediawiki.org/wiki/VisualEditor/Bidirectional_text_requirements\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350158076, 'spacePHID': None, 'dateCreated': 1350148320, 'dateModified': 1454004784, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41010', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Disabled toolbar Buttons should not respond to clicks', 'description': {'raw': 'screenshot of the problem\\n\\nWhen you click a button that is disabled, it still gives you the visual feedback of being pressed.\\n\\nThe screenshot shows me clicking the \"reduce indent level\" button while it is disabled. Note the shadow border that is added when you click it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9583}'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354216942, 'spacePHID': None, 'dateCreated': 1350045780, 'dateModified': 1454004792, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40976', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'wikibugs-l@ does not follow all products/components', 'description': {'raw': 'Not sure how the exact scope of wikibugs-l@ is defined (which products/components it is expected to cover) and what the expectations of people watching wikibugs-l@ in Bugzilla are, but wikibugs-l@ is NOT subscribed to ALL components/products.\\n\\nAfter spending 20min of investigating:\\n\\nProduct level:\\nTo get bugmail for any changes in the products Cortado, Datasets, Huggle, mwEmbed, Parsoid, (Security,) VisualEditor, the only chance is to follow the default assignee listed on https://bugzilla.wikimedia.org/describecomponents.cgi . But that also means receiving all other bugmail created by her/him no matter which product the changes were made in.\\n\\nComponents level:\\nSeveral components in the \"MediaWiki extensions\" product that don\\'t have the Default Assignee set to wikibugs-l@ do not always have wikibugs-l@ at least in the default CC list.\\nSame for \"VIAF\" and \"WM-Bot\" components in the \"Tools\" product.\\nSame for \"lucene-search-2\" and \"Prototype server\" components in the \"Wikimedia\" product.\\nSame for \"bots\" in \"Wikimedia Labs\".\\n\\n\\n(Fixing bug 37105 would be a different approach to solve part of the problem.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350036846, 'spacePHID': None, 'dateCreated': 1350032400, 'dateModified': 1353163615, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40973', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save dialog \"minor edit\" link should either give a pop-up explanation or target=_new', 'description': {'raw': 'Right now the \"This is a [minor edit]\" text in the save dialog tries to take the user to a new page in the current context, prompting them to abandon their changes (or not leave). This is sub-optimal. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354758513, 'spacePHID': None, 'dateCreated': 1349379660, 'dateModified': 1417571200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40773', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inline switching of styling mode does not correctly updating typed text when @EOL', 'description': {'raw': 'This is a bug in the functionality implemented for bug 33140\\n\\nPlatform: Safari 6, Mac Mountain Lion\\n\\nInsert cursor after the . of the Note in the lede of the VisualEditor:Test page (end of line).\\n\\nNow press ctrl-b\\ntype: text is in bold\\nPress ctrl-b again\\ntype: new text is STILL in bold, but should be non-bold\\nPress ctrl-b again\\ntype: The previous block is rerendered to be non-bold and the new text is rendered as bold.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350000478, 'spacePHID': None, 'dateCreated': 1349371140, 'dateModified': 1417571232, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40771', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection is wrongly restored on undo', 'description': {'raw': 'Steps to re-create:\\n* Go to a new page, insert the word \"Fascinating\"\\n* Select it (double-click, click-drag or select-all)\\n* Press a list button, and then undo\\n\\nWhat happens: The word \"Fascinating\" de-lists; the selection is set to \"scinati\".\\n \\nWhat should happen: The word \"Fascinating\" de-lists; the selection is set to \"Fascinating\".\\n \\n* Again, press a list button, and then undo\\n\\nWhat happens: The word \"Fascinating\" de-lists; the selection is set to \"ina\".\\n \\nWhat should happen: The word \"Fascinating\" de-lists; the selection is set to \"scinati\".\\n \\n* Again, press a list button, and then undo\\n\\nWhat happens: The word \"Fascinating\" de-lists; the selection appears to have disappeared.\\n \\nWhat should happen: The word \"Fascinating\" de-lists; the selection is set to \"ina\".\\n\\nEtc. :-) \\n\\nRob suggested that it was likely an issue in Transaction Builder?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350326683, 'spacePHID': None, 'dateCreated': 1348700340, 'dateModified': 1417571211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40538', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'labs-nfs1 full again', 'description': {'raw': '[ve-roundtrip2] ~ $ sudo du -sh /home/ori\\n16M\\t/home/ori\\n[ve-roundtrip2] ~ $ sudo df -h /home/ori\\nFilesystem                               Size  Used Avail Use% Mounted on\\nlabs-nfs1:/export/home/visualeditor/ori   18G   17G     0 100% /home/ori\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1348196377, 'spacePHID': None, 'dateCreated': 1348169460, 'dateModified': 1348196377, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40409', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Creating a link over-writes any existing annotations on the text', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1349115767, 'spacePHID': None, 'dateCreated': 1348000500, 'dateModified': 1417571234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40337', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit summary length counter confusing when in bytes', 'description': {'raw': 'Assuming we implement bug 39558. That means the counter in the corner of the save dialog will be decreasing more than 1 per character on average.\\n\\nEnglish users will likely not notice it as quickly, but € (EURO SYMBOL) for instance is 3 bytes. And in foreign languages it will be more common entirely.\\n\\nRight now the counter has no unit, which would be confusing (the natural expectation is to assume character count). We can add a unit word \"# bytes\" instead. But I\\'m not sure that is an improvement, do we want to face users with that?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=4715'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1347900984, 'spacePHID': None, 'dateCreated': 1346892540, 'dateModified': 1417571043, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40035', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing enter in a textarea should not submit the form (saveDialog-editSummary)', 'description': {'raw': \"Submitting the form on Enter in the current UI goes against all expectations.\\n\\nIt is hardcoded in the javascript to override the default behavior (browsers are actually quite sane in this case and know not to auto-submit from a textarea because that's bad).\\n\\nEither make it not a text area or make it not submit on Enter.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52133\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1347381271, 'spacePHID': None, 'dateCreated': 1346892300, 'dateModified': 1431785852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40034', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: By-word selection fails when mouse moves', 'description': {'raw': 'Word-by-word text selection by mouse fails as soon as the user moves the mouse.\\n\\nExamples: If a user double clicks on \"Lorem\" in a \"Lorem ipsum\" string and then moves the mouse to, say, after the letter \"p\", the selected text becomes just \"Lorem ip\", rather than the entirety of both words. If a user double clicks on a word, it becomes entirely highlighted, but if the mouse is moved, the only parts highlighted are the letters between the beginning of the word and the cursor.\\n\\nThe expected behavior is that after the user double clicks, the selection expands/shrinks only word-by-word, with the original selected word always highlighted.\\n\\nTested on Chrome on Windows 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350001255, 'spacePHID': None, 'dateCreated': 1346752740, 'dateModified': 1417571232, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39965', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: UI restores #toc as inline-block instead of table', 'description': {'raw': 'Bug in action\\n\\nWhen pressing Edit in VE mode, and then aborting (e.g. Parsoid is not running and the page is restored) the table of contents becomes an inline block which looks rather odd.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9671}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1346830749, 'spacePHID': None, 'dateCreated': 1346200560, 'dateModified': 1417571168, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39753', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Annotate the DOM to indicate on round-trip what's changed, so Parsoid can do partial serialisation\", 'description': {'raw': 'Per request of Parsoid team. Not sure if this is already a bug? Apologies if so. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352492599, 'spacePHID': None, 'dateCreated': 1345851360, 'dateModified': 1417571209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39634', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: DOM out of sync with data model when typing next to a link', 'description': {'raw': 'Reproduce by placing cursor just to the right of a link.  Start typing.  Force the node to re-render by changing the formatting to a heading. OR just save the page.  Notice that the new text is now part of the link.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354217099, 'spacePHID': None, 'dateCreated': 1345766400, 'dateModified': 1417571204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39603', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector should abridge completion results so users can distinguish multiple very long similar titles', 'description': {'raw': 'Proposal is to automatically put the ellipsis in the middle rather than at the end of the string.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1347302279, 'spacePHID': None, 'dateCreated': 1345748940, 'dateModified': 1417571234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39591', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Comments break splitting of paragraphs', 'description': {'raw': 'See http://parsoid.wmflabs.org/_rt/mw/VisualEditor:Test , and note how \"many of your questions\" and \"Note: The Edit button\" are on the same line, while they\\'re really supposed to be in separate paragraphs.\\n\\nBasically, what\\'s going on here is that the wikitext:\\n\\nFoo\\n<!-- Comment -->\\n\\nBar\\n\\nis turned into this HTML:\\n<p>Foo\\n<!-- Comment -->\\n\\nBar</p>\\n\\nwhile really the correct output is this:\\n<p>Foo</p>\\n<!-- Comment -->\\n\\n<p>Bar</p>\\n\\nThis results in the page rendering as \"Foo Bar\" rather than \"Foo [paragraph break] Bar\", and of course that means the way the editor renders it and lets you edit it is wrong as well.\\n\\nWhat\\'s maybe even scarier is that this round-trips \"correctly\", i.e. the wikitext->HTML conversion is wrong, but then the HTML->wikitext conversion is wrong in exactly the reverse way, and that causes it to round-trip. I suspect this is because of the presence of the newlines in the HTML, but that\\'s also a bug: ideally the serializer shouldn\\'t convert a single <p> to wikitext representing multiple paragraphs, regardless of newlines (this is very unlikely to be a practical problem for VE though).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1349299076, 'spacePHID': None, 'dateCreated': 1345593360, 'dateModified': 1349299076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39545', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Select all then replace causes first character to be swallowed in Heading mode', 'description': {'raw': \"To reproduce:\\n\\nGo to a blank VisualEditor page, click edit, change entry mode to Heading 1 (or whichever Heading mode), select all (Ctrl-A or Cmd-A), type in 'Abc'.\\n\\nThe 'A' will appear, then be replaced by the 'b'; the 'c' appears normally.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345502985, 'spacePHID': None, 'dateCreated': 1345502760, 'dateModified': 1417571239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39517', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Annotated content stripped from an LI on save', 'description': {'raw': 'See: https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=574056&oldid=574055\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1347302507, 'spacePHID': None, 'dateCreated': 1345492260, 'dateModified': 1417571233, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39512', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector should cache completion results', 'description': {'raw': 'If I type \"T\", then \"Te\", then press backspace, the link inspector will request suggestions for \"T\" for the second time. Instead, it should cache these results.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345571007, 'spacePHID': None, 'dateCreated': 1345484760, 'dateModified': 1417571237, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39511', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting all text and typing causes first typed character to be deleted', 'description': {'raw': 'To reproduce:\\n\\n1. Select all text in document (ctrl/cmd+a)\\n2. Start typing a word\\n3. Notice that the first character of the word disappears\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350001011, 'spacePHID': None, 'dateCreated': 1345239480, 'dateModified': 1417571230, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39465', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection issues re-write', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354812178, 'spacePHID': None, 'dateCreated': 1344882780, 'dateModified': 1468201515, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39315', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: JS error after saving document', 'description': {'raw': 'Open a document in the editor, change something, then save it. The following JS error appears in my console after saving:\\n\\nTypeError: $editorDocument.children(\".ve-ce-branchNode:last\").offset() is null\\n[Break On This Error] \\t\\n\\n$editorDocument.children( \\'.ve-ce-branchNode:last\\' ).offset().top\\n\\nve.Surface.js (line 184)\\n\\n\\nObserved in Firefox 14.0.1.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354812033, 'spacePHID': None, 'dateCreated': 1344637500, 'dateModified': 1417571202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39255', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Self-closing tags without trailing slash do not round-trip correctly', 'description': {'raw': 'Go to http://localhost:8000/_rtform/ and enter \"<br>\"; it\\'ll round-trip to \"<br />\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345656284, 'spacePHID': None, 'dateCreated': 1344466200, 'dateModified': 1345658396, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39181', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Round-tripping of double apostrophes causes them to be interpreted as wikitext', 'description': {'raw': 'Repro:\\n\\n1. Go to http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&action=edit&oldid=569294 , save, then edit it with VE\\n2. Insert \\'\\' in the word \"link\", save. diff: http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&diff=569295&oldid=569294\\n3. Edit it with VE again, select \"li\\'\\'nk\", and make it italic, save. diff: http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&diff=next&oldid=569295\\n4. So many unexpected quotes\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1344908105, 'spacePHID': None, 'dateCreated': 1344201240, 'dateModified': 1417571237, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39058', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid does not handle urlencoded interwiki prefixes correctly', 'description': {'raw': 'http://localhost:8000/localhost:VisualEditor:Foo works and parses VisualEditor:Foo on localhost\\n\\nhttp://localhost:8000/localhost:VisualEditor%3AFoo works too\\n\\nhttp://localhost:8000/localhost%3AVisualEditor%3A Foo does not work, it doesn\\'t recognize the interwiki prefix, falls back to the default interwiki (mw:), and tries to parse [[mw:Localhost:VisualEditor:Foo]].\\n\\nDebugging shows that in the \"Regular article parsing\" callback on line 397, req.params is set to [ undefined, \\'localhost:VisualEditor:Lists\\' ], whereas if the colons aren\\'t urlencoded it\\'s [ \\'localhost\\', \\'VisualEditor:Lists\\' ]. It looks like app.get()\\'s regex mode isn\\'t processing urlencoded characters correctly even though it does unescape the matches before putting them in req.params.\\n\\nThis is obviously a blocker for making VisualEditor always use an interwiki prefix.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343853258, 'spacePHID': None, 'dateCreated': 1343793720, 'dateModified': 1344281149, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38906', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: UserAgent blacklisting (using jQuery.client?)', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345671208, 'spacePHID': None, 'dateCreated': 1343672940, 'dateModified': 1417571235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38857', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"edit source\" link on oldid=foo should pass on the revision in the GET when going to action=edit, even though veaction=edit doesn\\'t support it yet.', 'description': {'raw': \"Right now we can't use VE on an old-id page due to Parsoid lacking the feature yet, but we could at least make the edit-source link work when users are looking at an old revision. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343674164, 'spacePHID': None, 'dateCreated': 1343424780, 'dateModified': 1417571242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38769', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: round-trip inline styles', 'description': {'raw': 'Input:\\n\\nThis is an <span style=\"background: red; color: white; font-weight: bold;\">Inline element</span>.\\n\\nThis sentence contains \\'\\'\\'wikitext bold\\'\\'\\' and <b>html bold</b>, <strong>html strong</strong> and <span style=\"font-weight: bold;\">inline style bold</span>.\\n\\nOutput:\\n\\nThis is an <span>Inline element</span>.\\n\\nThis sentence contains \\'\\'\\'wikitext bold\\'\\'\\' and \\'\\'\\'html bold\\'\\'\\', <strong>html strong</strong> and <span>inline style bold</span>.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345054334, 'spacePHID': None, 'dateCreated': 1343347860, 'dateModified': 1417571238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38738', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Round-trip <b> should not become '''syntax'''\", 'description': {'raw': \"Can not reproduce on parsoid.wmflabs.org but not sure which version runs where, so reporting as reminder to confirm that it is fixed once deployed on MediaWiki.org as well.\\n\\nInput:\\nThis sentence contains '''wikitext bold''' and <b>html bold</b>, <strong>html strong</strong>.\\n\\nOutput:\\nThis sentence contains '''wikitext bold''' and '''html bold''', <strong>html strong</strong>.\\n\\n\\nExample: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ADoom&diff=565804&oldid=565802\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=38738\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345054496, 'spacePHID': None, 'dateCreated': 1343347800, 'dateModified': 1417571238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38737', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Modify the Parsoid <-> DM converter to handle newlines properly', 'description': {'raw': '* New lines after headlines are being stripped\\n* New lines after lists are being stripped\\n* New lines after tables are being stripped\\n* New lines after <gallery> tags are being stripped\\n\\n\\nExample: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ADoom&diff=565804&oldid=565802\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1347302350, 'spacePHID': None, 'dateCreated': 1343347620, 'dateModified': 1417571235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38736', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing Enter/Return in the edit summary input field should trigger submission', 'description': {'raw': 'As the title says. Tried on MediaWiki.org\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343347540, 'spacePHID': None, 'dateCreated': 1343347500, 'dateModified': 1417571242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38735', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Table roundtripping is completely tripped up', 'description': {'raw': 'Several issues:\\n\\n* Ghost <nowiki></nowiki> tag pairs appearing\\n\\n* Syntax being normalized\\n\\n 1)\\n  ! foo !! bar !! baz\\n  becomes\\n  ! foo\\n  ! bar\\n  ! baz\\n\\n  Both are the same but should roundtrip if possible.\\n\\n 2)\\n  Row separators\\n  {|\\n  |-\\n  ! foo\\n  |-\\n  | bar\\n  |-\\n  |}\\n  becomes:\\n\\n  {|\\n  ! foo\\n  |-\\n  | bar\\n  |}\\n\\n  Although the first and last separator (|-) are optional, they should roundtrip\\n  if possible.\\n\\n 3) Syntax being broken due to new line insertion\\n  ! foo !! bar !! baz\\n  becomes:\\n  ! foo\\n  !! bar\\n  !! baz\\n\\n  This is not just syntax appearance, this is actually broken. Because of the new lines, the output of 3) is actually difference, because it will display the second exclamation mark of each heading.\\n\\n\\n\\nExample: https://www.mediawiki.org/w/index.php?title=VisualEditor%3ADoom&diff=565804&oldid=565802\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352492777, 'spacePHID': None, 'dateCreated': 1343347320, 'dateModified': 1417571209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38734', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] VisualEditor: Down arrow in the inspector icon is mis-aligned.', 'description': {'raw': 'Due to the change[1] to arrow-down.png recently, the inspector icon was broken. The padding inside the image is very specific for the drop-down menu. The inspector-triggering icon however, does not need this padding and is mis-aligned as a result of that.\\n\\n\\n[1] Change: Ib09a2a20b1 | https://gerrit.wikimedia.org/r/16218\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343180029, 'spacePHID': None, 'dateCreated': 1343176200, 'dateModified': 1417571243, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38658', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: User should be able to select text in the save dialog.', 'description': {'raw': 'The user-select: none; style from the ve-toolbar is cascading down into the save dialog, causing issues.\\n\\nSteps to reproduce:\\n* View https://www.mediawiki.org/wiki/VisualEditor:Test\\n* Change some text\\n* Press \"Save page\"\\n\\nUnexpected result:\\nUsers can\\'t select/highlight any text inside the Save page dialog. In Chrome users can at least still select text inside the input field, though in Firefox it applies to form elements as well.\\n\\nIf possible, the easiest fix would be to override user-select inside this save dialog and undo the \"none\" value. But its possible that that isn\\'t possible (just like like display: block; doesn\\'t do anything if an ancestor is display: none;).\\n\\nOtherwise it may have the be re-arranged to not be inside an element with class ve-toolbar.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343329073, 'spacePHID': None, 'dateCreated': 1343174820, 'dateModified': 1417571241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38657', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: White box syndrome strikes back!', 'description': {'raw': 'Screenshot of the white box overlapping regular text while using the editor\\n\\nFrom time time to time a white square appears in the editor, overlaying/masking part of the text.\\n\\nIt can appear both when clicking/typing, as well as when selecting text. In the latter case it is even more visible due to the blue selection being interrupted by the box.\\n\\nDebugging tells me it is the idle iframe idling in the bushes, pretending to be hidden.\\n\\nSteps to reproduce:\\n* Open https://www.mediawiki.org/wiki/VisualEditor:Test in Chrome 20 (Mac)\\n* Switch to \"Edit\" mode\\n* Select a word in the editor\\n* Bolden it\\n* Click \"Save Page\"\\n\\nUnexpected result:\\n* White box appears where the word was selected.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9946}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345747417, 'spacePHID': None, 'dateCreated': 1343172780, 'dateModified': 1417571236, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38655', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Bold and Italic UI buttons need to be internationalisable', 'description': {'raw': 'The Bold and Italic buttons say \"B\" and \"I\". Some languages can have different letters there; for example, Italian has \"G\" and \"C\" and German has \"F\" and \"K\".\\n\\nThe corresponding buttons in the WikiEditor extension can be localized, but not in Visual Editor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1359765195, 'spacePHID': None, 'dateCreated': 1342883880, 'dateModified': 1689316915, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38551', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Undo\" and \"Redo\" buttons must be flipped for RTL environments', 'description': {'raw': '\"Undo\" and \"Redo\" buttons must be flipped for RTL environments. Undo must point right and Redo must point left.\\n\\nThe same images can be used, but they must be swapped.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1347918222, 'spacePHID': None, 'dateCreated': 1342869480, 'dateModified': 1417571234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38548', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Bulleted list\" and \"Numbered list\" buttons in the editing toolbar must be reversed in RTL wikis', 'description': {'raw': 'This bug is almost the same as Bug 28544 in WikiEditor :)\\n\\nThe buttons \"Bulleted list\" and \"Numbered list\" must be mirrored in RTL wikis.\\n\\nThe numbers in \"Numbered list\" in languages he, yi, arc and dv should look like\\nregular Western numbers - not mirrored.\\n\\nIn languages written in the Arabic alphabet (ar, fa, ur, ps, mzn etc.)\\n[[Eastern Arabic numerals]] can be written there, but maybe Western numbers\\nare OK, too.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354216837, 'spacePHID': None, 'dateCreated': 1342869360, 'dateModified': 1417571205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38547', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: down arrow in drop-down menu in RTL interface overlaps with the text', 'description': {'raw': 'Configure the user language to be Hebrew. Try to edit a page. The down arrow in format selection drop-down menu will overlap with the text.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343346049, 'spacePHID': None, 'dateCreated': 1342866000, 'dateModified': 1417571241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38545', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: {Ctrl|Option}+{Delete,Backspace} should delete a word right, left of the caret', 'description': {'raw': 'Ctrl+{Delete,Backspace} should delete a word right, left of the caret; Option+{Delete,Backspace} on Mac.\\n\\nCurrently deletes a character right, left of the caret.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369782887, 'spacePHID': None, 'dateCreated': 1342570860, 'dateModified': 1417571162, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38461', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE does not check for global blocks or title blacklist on page edit/creation', 'description': {'raw': 'I found that neither the global block nor the blacklisting of this title  prevented a globally-blocked proxy from creating http://www.mediawiki.org/w/index.php?title=VisualEditor:Modern_Apizza&action=edit&redlink=1.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wqc7ciyvfzunj3l2tvjt', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354218456, 'spacePHID': None, 'dateCreated': 1341867660, 'dateModified': 1417707443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38268', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Selecting all text causes JS error in Firefox', 'description': {'raw': 'If I edit any page in Firefox 13 and select all text (using Ctrl+A), I get the following error:\\n\\nend is undefined\\nhttp://localhost/w/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js\\nLine 849\\nrangyRange.setEnd( end.node, end.offset );\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341519459, 'spacePHID': None, 'dateCreated': 1341519180, 'dateModified': 1417571245, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38207', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Instead of inspector-triggering icon, just trigger it whenever the user selects some content', 'description': {'raw': 'From user submission. Uses same design argot as iOS. Perhaps confusing for non-iOS situations?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360095133, 'spacePHID': None, 'dateCreated': 1340916840, 'dateModified': 1417571173, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38044', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: 'Enter' key does not submit edit from save dialog\", 'description': {'raw': 'My muscle memory really, REALLY wants to hit enter after typing a summary, but it does nothing. Have to go to the mouse and find the button manually. Eww!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340916283, 'spacePHID': None, 'dateCreated': 1340912820, 'dateModified': 1343341015, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38039', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: doesn't trigger in IE 9 (Internet Explorer 9)\", 'description': {'raw': 'Tested on Windows 7 SP1 w/ IE 9...\\n\\nEdit tab just gives me the classic edit page...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345671537, 'spacePHID': None, 'dateCreated': 1340910600, 'dateModified': 1417571236, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38038', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: select all (ctrl+a) throws JS error in Firefox', 'description': {'raw': 'Possibly harmless but worrying.\\n\\nSteps to repro:\\n* go to https://www.mediawiki.org/wiki/VisualEditor:Test?debug=true\\n* hit edit\\n* click in the article\\n* ctrl+a (cmd+a on mac) to select all\\n\\nExpected:\\n* all text of article should be selected\\n\\nActual:\\n* all text of article is selected\\n* AND there\\'s an error in the JS console: \"end is undefined\"\\nve.ce.Surface.js (line 832)\\nrangyRange.setEnd( end.node, end.offset );\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/VisualEditor:Test?debug=true'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350377414, 'spacePHID': None, 'dateCreated': 1340909880, 'dateModified': 1417571215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38037', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tooltips for formatting menu are broken', 'description': {'raw': 'From user feedback. They seem to be unescaped, too - \"&lt;visualeditor-formatdropdown-tooltip&gt;\" etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341617408, 'spacePHID': None, 'dateCreated': 1340834040, 'dateModified': 1417571245, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38008', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using page movement keys when focus is not in edit area still triggers movement', 'description': {'raw': \"If in a link inspector or in the edit summary, pressing Page Up, Page Down, Home or End works in that box but also triggers the main edit space to move to the top or bottom. It needs to ignore if it's not got the caret. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350690378, 'spacePHID': None, 'dateCreated': 1340833800, 'dateModified': 1417571214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38007', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Design of save button should make it more prominent', 'description': {'raw': 'From user request. \"Big Red Button\" requested, but we might want to consider within a wider design discussion. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1347303896, 'spacePHID': None, 'dateCreated': 1340833380, 'dateModified': 1417571233, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38006', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector button in toolbar should let users create a link without any text selected', 'description': {'raw': 'From user request. Possibly insert the name of the target automatically? So a link to [[foo]] will be entered as <a href=foo>foo</a>?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340833038, 'spacePHID': None, 'dateCreated': 1340832780, 'dateModified': 1417571248, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38005', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Ctrl + {left,right} arrow should skip a word left or right (Apple + ... on Mac OS X)', 'description': {'raw': 'From user request. There are other keybinding feature requests; possibly worth documenting all the ones we respect?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1349998405, 'spacePHID': None, 'dateCreated': 1340830740, 'dateModified': 1417571206, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cut all text, re-paste it: broken editor', 'description': {'raw': 'Steps to reproduce:\\n1) Go to http://www.mediawiki.org/wiki/Special:VisualEditorSandbox\\n2) Press CTRL-A (or select all text with the mouse)\\n3) Press CTRL-X to cut all this text. The text disappears.\\n4) Press CTRL-V to reinsert the text.\\n\\nPROBLEM1: Text is not reinserted, the page stays blank.\\nPROBLEM2: One can enter text, but not new lines. Pressing \"Enter\" does not have any effect.\\n\\nTested on Ubuntu 2012.04, Firefox 13.0.1\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341518416, 'spacePHID': None, 'dateCreated': 1340770860, 'dateModified': 1417571245, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37980', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using Mac OS X combination characters such as ˆ , ´ (e.g., más, â, äs) causes weird behaviour in Chrome; Safari', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-fgzcdbj3je3ksnhufo47', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350414720, 'spacePHID': None, 'dateCreated': 1340709300, 'dateModified': 1417571215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37962', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: DM support for nested lists', 'description': {'raw': 'As discussed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343673340, 'spacePHID': None, 'dateCreated': 1340654160, 'dateModified': 1417571242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37937', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: XYZ:Foo links round-trip surprisingly e.g. Categories, Images/Files, ….', 'description': {'raw': 'As discussed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341637505, 'spacePHID': None, 'dateCreated': 1340653980, 'dateModified': 1417571244, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37936', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Trim whitespace on headings, list items, other node types', 'description': {'raw': 'As discussed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345485423, 'spacePHID': None, 'dateCreated': 1340653920, 'dateModified': 1417571238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37935', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Placing the cursor (by clicking or through the cursor keys) into sub-lists breaks - it \"flashes\" in, but then disappears (is no longer drawn anywhere) and cannot be used (e.g. shift-left or etc. doesn\\'t work).', 'description': {'raw': '(From the casual list on the wiki.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343097980, 'spacePHID': None, 'dateCreated': 1340569500, 'dateModified': 1417571243, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37907', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Indent and outdent buttons do not exist', 'description': {'raw': '(From the casual list on the wiki.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343097650, 'spacePHID': None, 'dateCreated': 1340569500, 'dateModified': 1417571244, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37906', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unlisting should unlist all list levels', 'description': {'raw': '(From the casual list on the wiki.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352596148, 'spacePHID': None, 'dateCreated': 1340569440, 'dateModified': 1417571208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37905', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way to see the target of a link without triggering the inspector', 'description': {'raw': 'From MW.org report:\\n\\nLinks should probably have a title=\"\". I naturally hover over links to see their target. I wanted to see if the target was correct and I had to fiddle with the link editor just to see something that should have been easily available.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1357678591, 'spacePHID': None, 'dateCreated': 1340569140, 'dateModified': 1417571174, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37904', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way to preview the diff of the changes made', 'description': {'raw': '(Depends on us working out what diffing revisions should look like now.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345669770, 'spacePHID': None, 'dateCreated': 1340569020, 'dateModified': 1417571237, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37903', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit window scrolls to top of page after paste', 'description': {'raw': \"iOS 5.1 simulator on Mac OS X\\n\\nAfter pasting text into the document, the view is scrolled up to the top of the page. This is a bit distracting if you're somewhere further down in the document. :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354928052, 'spacePHID': None, 'dateCreated': 1340473080, 'dateModified': 1417571200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37875', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: toolbar mispositioned on iPad', 'description': {'raw': \"Screenshot of iPad simulator\\n\\nThe toolbar is slightly mispositioned on iPad, tested in iPad simulator on Mac OS X as my iPad isn't handy.\\n\\nSeems to be slightly up and to the left of where it should be. Screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9308}\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343668655, 'spacePHID': None, 'dateCreated': 1340472060, 'dateModified': 1417571241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37873', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Window-close prompt thinks I'm returning to view mode, and displays two warnings rather than one.\", 'description': {'raw': 'Tested in Safari 5.1.7.\\n\\nSteps to repro:\\n* open https://www.mediawiki.org/wiki/VisualEditor:Welcome\\n* hit \\'edit\\'\\n* close tab\\n\\nA prompt comes up:\\n\\n  https://www.mediawiki.org\\n  Are you sure you want to leave this page?\\n  Are you sure you want to go back to view mode without saving first?\\n  [Stay on page] [Leave page]\\n\\nThe \"Are you sure you want to go back to view mode without saving first?\" presumably comes from our code. This makes sense only if I were clicking on the \\'read\\' tab link.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345748822, 'spacePHID': None, 'dateCreated': 1340470920, 'dateModified': 1417571235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37869', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add inline editing after each link, accessed by hide/unhide icon', 'description': {'raw': 'Suggestion: after each link add a little icon which, when clicked, adds a directly editable inline element containing the link destination. No need to go to the top, no no modal popup dialog which has to separately confirmed... The inline link destination should not require closing to accept, it should just be a part of the text and changes to it are naturally saved together with all other text when the page is being saved.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360204987, 'spacePHID': None, 'dateCreated': 1340418720, 'dateModified': 1417571172, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37859', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unexpected behaviour of list editing - what level should the buttons operate, and is it consistent?', 'description': {'raw': 'From https://www.mediawiki.org/w/index.php?title=Thread:VisualEditor_talk:Welcome/Editing_numbered_Lists_is_broken&lqt_method=thread_history\\n\\nClick on one item in a three element numbered list and click on the numbered list button -> all three elements become unnumbered. Click again -> only the first element becomes numbered.\\nMark all three and click -> you sometimes get three elements in a numbered list, sometimes three numbered lists, each starting with number 1. Could not figure out when I get what...\\nWhen I mark three fresh, non numbered, non-bulleted lines, it seems generally to work becoming a three part numbered list. Although clicking again (which changing selection focus) on the button to undo here never works. That is: all three 1 to 3 selected, click on numbered list button to unnumber does not work, going to the first element click same button, unnumbers all.\\nHaving three line of unnumbered text where the second element is a bulleted list item, select, click numbered list (expecting to have a nested bullet within a numbered list) does not work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352481732, 'spacePHID': None, 'dateCreated': 1340418540, 'dateModified': 1417571210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37857', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Nested lists (tracking bug)', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343260962, 'spacePHID': None, 'dateCreated': 1340413620, 'dateModified': 1541508628, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37854', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: JS error on load in IE 10', 'description': {'raw': \"Seen in my JS console during loading in IE 10 on Windows 8 Release Preview:\\n\\nSCRIPT5007: Unable to get property 'to' of undefined or null reference\\nve.ui.Context.js, line 120 character 2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350327513, 'spacePHID': None, 'dateCreated': 1340405460, 'dateModified': 1417571216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37851', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Mouse selection very unreliable in Internet Explorer 10', 'description': {'raw': \"Testing on Windows 8 Release Preview running in VirtualBox.\\n\\nClick to set caret position and click-and-drag to select text don't seem to work reliably in IE 10. Tested both in desktop and Metro mode.\\n\\nMouse activity can be seen in mouseover and mousedown text decoration/coloring on links, but ... most of the time the caret doesn't move / selection doesn't change.\\n\\nOccasionally one gets through, it's not clear how/why.\\n\\nNote that selection with arrow keys+shift works fine.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350690829, 'spacePHID': None, 'dateCreated': 1340404680, 'dateModified': 1417571214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37850', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: All icons need hi-resolution version (HiDPI, Retina display)', 'description': {'raw': \"For mobile, tablets and laptops with high-resolution displays we'll want double-resolution or SVG versions of the icons served. Attached screenshot taken in Firefox 16 nightly with acceleration disabled on MacBook Pro Retina. Looks about the same in Safari.\\n\\nThe current icons appear to be PNG, with a PSD source file that's at low resolution. If the layers are vector shapes this should be easy to convert to high-resolution, but I don't have Photoshop on this machine to double-check.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1347302633, 'spacePHID': None, 'dateCreated': 1340401080, 'dateModified': 1629487069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37849', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Delete at end of document causes JS error', 'description': {'raw': 'As discussed. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340668774, 'spacePHID': None, 'dateCreated': 1340400480, 'dateModified': 1417571300, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37848', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Interface should have an obvious way to get back to reading mode', 'description': {'raw': 'The current VisualEditor interface has a prominent \"Save page\" button, but no \"Cancel\" button. It would be nice if there were a clear exit strategy in the interface.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354750533, 'spacePHID': None, 'dateCreated': 1340393700, 'dateModified': 1417571203, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37845', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Protection and AbuseFilter do not work for VisualEditor edits; create a 'usevisualeditor' permission\", 'description': {'raw': 'Based on some testing on MediaWiki.org, page protection and the abuse filter do not work - page protection does not change the ability of all non-blocked users to edit the page and abuse filter does not pick up any edits generated by the visual editor.\\n\\nI believe that the underlying problem is that using the visual editor is not a named action that can be restricted or filtered at the moment. If it was, then it would be possible to assign it to $wgRestrictionTypes and it would be possible for the abuse filter to log it (though the abuse filter does need the addition of some variables or other modification to accept visual editor edits).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wqc7ciyvfzunj3l2tvjt', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354216989, 'spacePHID': None, 'dateCreated': 1340391180, 'dateModified': 1417571204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37844', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Throws error when trying to edit blank (but existing) page', 'description': {'raw': 'I created a blank page at <https://www.mediawiki.org/wiki/VisualEditor:Hello_there>. When I try to edit the page using the VisualEditor extension, I receive the following error: \"Error loading data from server: No HTML content in response from server. Would you like to retry?\"\\n\\nI imagine this is a safety check somewhere in the code that needs to be tweaked. If page_len == 0, it isn\\'t always an error. Sometimes a blank page is just a blank page. ;-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1351287039, 'spacePHID': None, 'dateCreated': 1340390820, 'dateModified': 1446647276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37843', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Improperly escapes <nowiki>', 'description': {'raw': 'If I input <nowiki>a</nowiki> in VE, save the page, then go back to the editor, text is broken in VE there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1344447584, 'spacePHID': None, 'dateCreated': 1340390460, 'dateModified': 1532186484, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37838', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Shift-Page {Up,Down} selection only works upwards', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350000249, 'spacePHID': None, 'dateCreated': 1340388180, 'dateModified': 1417571231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37834', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Shift-cursor selection downwards switches to upwards selection once you use Up or Right arrow', 'description': {'raw': 'Place the caret. Press Shift and then a downwards selection key (i.e. Down or Right arrow). As expected, you move the caret downwards correctly using either key. \\n\\nHowever, after some text is selected, pressing Up or Left causes the caret to move to the start of the selection to expand (rather than allowing the leading edge of the selection to be reduced). All further shift-cursor key presses (Up/Down/Left/Right) only change the position of the earlier part of the selection, and you can no-longer select as desired.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350000874, 'spacePHID': None, 'dateCreated': 1340388060, 'dateModified': 1417571216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37833', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Creating link over an existing link is broken', 'description': {'raw': 'See https://www.mediawiki.org/w/index.php?title=VisualEditor:BugLinkSelection&action=history\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1344376920, 'spacePHID': None, 'dateCreated': 1340341920, 'dateModified': 1417571240, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37820', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Messages minoredit, watchthis not parsed in \"save page\" dialog box', 'description': {'raw': 'In \"Save page\" dialog, the content of message <minoredit> is not parsed and raw wikitext is displayed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1344881831, 'spacePHID': None, 'dateCreated': 1340341320, 'dateModified': 1417571240, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37819', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing in a numbered list before a section heading moves the cursor into the section heading', 'description': {'raw': '== section ==\\n\\n# number      <cursor pops up here>\\n# number\\n<enter>\\n<enter>\\n\\n== <when you type, the cursor pops down here and starts editing> section ==\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xs3vxsmgivmm2tuyxsrb', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341267913, 'spacePHID': None, 'dateCreated': 1340318220, 'dateModified': 1417571246, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37816', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor has broken delete behavior on end-of-file', 'description': {'raw': '* Move cursor to last line of the page.\\n* Delete till all subsequent empty lines are removed.\\n* The next delete will remove the first character of the line and subsequent deletes delete larger chunks of text.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341267573, 'spacePHID': None, 'dateCreated': 1340317440, 'dateModified': 1417571246, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37815', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Text added to line below cursor', 'description': {'raw': 'Steps to reproduce:\\n\\n* Create a bunch of empty lines by hitting enter key\\n* Move cursor up to the 1st/2nd empty line and start typing -- the first couple chars are inserted on the line below\\n\\nCan also reproduce this in other ways:\\n* delete to end of line, enter a bunch of empty lines, move cursor to one of the middle empty lines and start typing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350000047, 'spacePHID': None, 'dateCreated': 1340316960, 'dateModified': 1417571231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37814', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Lost text after deleting to/from EOF', 'description': {'raw': 'Steps to reproduce this on VE:\\n\\n* delete text to (or from) end of file using either backspace or delete key\\n* type text and hit the return key,\\n* the typed text is lost\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=37815'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341267341, 'spacePHID': None, 'dateCreated': 1340316720, 'dateModified': 1417571246, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37813', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: editing toolbar float trigger also triggers contextView icon, although there is no context to act on', 'description': {'raw': \"When the editing toolbar trigger is triggered (either floating or defloating the editing toolbar), it also triggers the contextView icon to appear wherever the text cursor is, even if no text is selected. And of course you can't use any of the contextView tools while no text is selected. Once this occurs, subsequent interaction with the page is inconsistent. For example if you try to reposition the cursor it jumps back to the old location as soon as you start typing. Verified in Firefox and Safari.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341258696, 'spacePHID': None, 'dateCreated': 1340315820, 'dateModified': 1417571247, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37811', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: bullet list breaking after changing window focus', 'description': {'raw': \"**Author:** `dbaran`\\n\\n**Description:**\\nBrowser = Chrome 19.0.1084.56\\n\\nClickstream:\\n\\n--used formatting toolbar to select bullet\\n--entered single word\\n--changed focus from browser to different window (skype I think)\\n--changed focus back to browser by mousing back to bullet list\\n--hit enter\\n--nothing happened.  cursor didn't move.  \\n\\n\\nI can reproduce consistently by typing in another window, then coming back to browser, and cursor will be stuck.  However if I perform some action in another tab of the browser, when I return to the tab in which I'm editing, the cursor works, although it requires hitting enter more than once.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows 7\\n**Platform**: PC\\n**URL**: https://internal.wikia-inc.com/wiki/New_Visual_Editor \\t\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341002667, 'spacePHID': None, 'dateCreated': 1340314980, 'dateModified': 1417571247, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37810', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Hit Enter at the end of a heading, blinking cursor disappears', 'description': {'raw': '**Author:** `sumanah`\\n\\n**Description:**\\nCursor should show up where the red circle indicates\\n\\nI went to https://www.mediawiki.org/wiki/VisualEditor:Test , hit Edit, clicked just at the end of a heading (got a blinking cursor), and hit Enter. A newline appeared, but there was no blinking cursor to indicate where I was; the cursor had disappeared.\\n\\nI can replicate this.  Firefox 11.0, Firebug is off, Ubuntu 11.10.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9494}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340315734, 'spacePHID': None, 'dateCreated': 1340314620, 'dateModified': 1351534183, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37809', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor freaks out on <span>', 'description': {'raw': 'After I vandalised the test page with[1], trying to edit this page resulted in \"renderers[annotation.type] is undefined\"\\n\\nvar openAnnotations = function( annotations ) {\\n    var out = \\'\\',\\n        annotation;\\n    for ( var hash in annotations ) {\\n        annotation = annotations[hash];\\n        out += typeof renderers[annotation.type].open === \\'function\\' ? <-- here\\n            renderers[annotation.type].open( annotation.data ) :\\n            renderers[annotation.type].open;\\n        hashStack.push( hash );\\n        annotationStack[hash] = annotation;\\n    }\\n\\n\\n----\\n[1] https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=552553&oldid=552537\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-aasrweh54ew7py3agvg2', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340315537, 'spacePHID': None, 'dateCreated': 1340314080, 'dateModified': 1351534191, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37808', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Backspace deletes more than one character on newly-added text', 'description': {'raw': 'If you type in something new using VisualEditor, and then you press the backspace key, you end up deleting all of what you wrote plus the character immediately before. This seems to delete about 3-5 characters at a time.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wqc7ciyvfzunj3l2tvjt', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340404706, 'spacePHID': None, 'dateCreated': 1340310360, 'dateModified': 1340404706, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37804', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link box should suggest page titles', 'description': {'raw': 'The input box used to select target pages for links should display suggestions for pages, like WikiEditor\\'s \"Insert link\" dialog box.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345486519, 'spacePHID': None, 'dateCreated': 1339495020, 'dateModified': 1417571239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37491', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: npm dependencies', 'description': {'raw': 'New file to track npm dependencies\\n\\nThis patch will make it simpler to install node module dependencies.  When the package.json file exists, running \"npm install\" with no arguments will create a directory \"node_modules\" and fetch dependencies.\\n\\nThere are some related improvements to be made, such as editing the Makefile to point NODE_PATH to this directory.  Actually, I don\\'t know what the recommended practice is here--seems like this should be in node\\'s default require path.\\n\\nMy focus was on running the tests, not sure about how to reuse this file for server configuration.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F9216}'}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340471199, 'spacePHID': None, 'dateCreated': 1332324240, 'dateModified': 1344281146, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35376', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable Semantic Forms on mrwiki', 'description': {'raw': '**Author:** `rahuldeshmukh101`\\n\\n**Description:**\\nIs it possible to make Extension:Semantic Forms available on mr.wikipedia .\\n\\nIf so please enable it for mr wiki.\\n\\nThanks\\n\\nRahul Deshmukh\\n\\nUser:rahuldeshmukh101\\nAdmin mr.wikipedia\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343163140, 'spacePHID': None, 'dateCreated': 1331345460, 'dateModified': 1343163140, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35108', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Polish : Date entry in citations should be automatically reformatted to community norms ', 'description': {'raw': 'Since incorrect date entry causes unnecessary work for other users, or new users to receive bot or user corrections, generally providing a negative experience, especially for new users. Additionally until fixed, this leads to inconsistencies in data. \\n\\nCorrecting these automatically, either at input time or post edit see — http://momentjs.com/'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-caadsxn4xg5gmxrpn6kz', 'dateClosed': 1490690476, 'spacePHID': None, 'dateCreated': 1415519616, 'dateModified': 1490690476, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor / General project should be imported as simply \"VisualEditor\"', 'description': {'raw': \"It's just a catch-all component, and isn't needed.\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 90, 'name': 'Needs Triage', 'color': 'violet'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1414165657, 'spacePHID': None, 'dateCreated': 1414164555, 'dateModified': 1414171154, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'in MobileFrontend, invoking the editor is incorrect and switching from VisualEditor to wikitext editor does nothing', 'description': {'raw': 'As a logged in user with beta access to VisualEditor using MobileFrontend, edit a new page on beta labs, e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/Apsidufapodifuasdf or some such. \\n\\nClick the pencil icon to edit the page.  I think this should bring up VE, but brings up wikitext editor instead. \\n\\nFrom the gear menu, click Edit to invoke VE\\n\\nAgain from the gear menu, click Edit source. \\n\\nVE fails to disappear. Wikitext editor does not appear. No VE controls like Bold/Italic/Link etc. function at this point. \\n\\nThis is the failure at https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/455/testReport/(root)/VisualEditor%20Mobile/Switch_from_VisualEditor_to_source_editor/\\n\\n'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1420510122, 'spacePHID': None, 'dateCreated': 1419890230, 'dateModified': 1520396802, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Uncaught TypeError when strating mobile VisualEditor', 'description': {'raw': \"ve.ui.Toolbar.js:224 Uncaught TypeError: Cannot read property 'triggerListener' of undefined\\n\\nExample: https://m.mediawiki.org/wiki/MediaWiki_1.25/Roadmap?debug=true#/editor/0\"}, 'authorPHID': 'PHID-USER-c5xwrfdyp3dckkh2nkoj', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1419625997, 'spacePHID': None, 'dateCreated': 1419625243, 'dateModified': 1419625997, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor not loading in el.wikipedia', 'description': {'raw': 'VisualEditor is not loading in el.wikipedia since yesterday.'}, 'authorPHID': 'PHID-USER-e7gwd3ou5ocdumo42srg', 'ownerPHID': 'PHID-USER-e7gwd3ou5ocdumo42srg', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-e7gwd3ou5ocdumo42srg', 'dateClosed': 1419079111, 'spacePHID': None, 'dateCreated': 1419072099, 'dateModified': 1419294852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Editing breaks and edit button does nothing after switching from VE to wikitext editor', 'description': {'raw': '\\nAs a logged-in user with access to VisualEditor visit any page e.g http://en.m.wikipedia.beta.wmflabs.org/w/index.php?title=Selenium_Test_Edit\\n\\nClick Edit to bring up VE\\n\\nFrom the gear menu select Edit source\\n\\nNo wikitext editor appears, but there is an edit icon on the page.\\n\\nClick the edit icon. It does nothing. '}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'dateClosed': 1418927703, 'spacePHID': None, 'dateCreated': 1418926603, 'dateModified': 1422688696, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor broken for MobileFrontend', 'description': {'raw': 'Broken since 11 December. \\n\\nAs a logged in user with access to VE, attempt to edit any page.  See a spinner. \\n\\nJavascript error shown in Chromium is \"TypeError: Illegal invocation TypeError: Illegal invocation \"\\n\\n'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1418902314, 'spacePHID': None, 'dateCreated': 1418766721, 'dateModified': 1520397334, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Have public bug day / triage sessions in February 2015 about VE', 'description': {'raw': 'Have triage sessions. Regarding topic, stakeholders and key developers, this will focus on VisualEditor and be on a weekly basis, and volunteers are very welcome:\\n\\nSee Task 86867 for \"VisualEditor Q3 Release Criteria\".\\nSee https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=645421507#VisualEditor_News_2015.E2.80.94.231 for announcement.\\n\\nSee https://www.mediawiki.org/wiki/Bug_management/Meeting_preparations for more information\\n\\nFirst bugday with Phabricator instead of Bugzilla.\\n\\nPotentially related Team-Practices tasks:\\n* https://phabricator.wikimedia.org/T88325 - \"Whole team chat with Damon RE burndown chart expectations\"\\n* https://phabricator.wikimedia.org/T88328 - \"Feasibility study for using Phab for burndown charts\"\\n* https://phabricator.wikimedia.org/T88365 - \"Burndown chart training and support - VE release support with Editing Team\"\\n'}, 'authorPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'dateClosed': 1427482483, 'spacePHID': None, 'dateCreated': 1418751245, 'dateModified': 1427482483, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Combine API requests required to load VE', 'description': {'raw': \"When I load VE on [[en:Gosford]], the following API requests are made:\\n\\n- 3x action=query&prop=imageinfo\\n- 1x action=query&prop=info\\n- 1x action=visualeditor&paction=parse (also see {T87553})\\n\\nFor a total of five API requests. Couldn't the VisualEditor API module expose an endpoint that combines this metadata into a single response?\"}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426531145, 'spacePHID': None, 'dateCreated': 1418709771, 'dateModified': 1426894328, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Special:Search on mw.org throwing an error - Advanced search checkboxes broken', 'description': {'raw': 'Clicking on \"Advanced\" search and changing the default namespaces to search and clicking search returns:\\n\\n``` lines=10\\n\"Exception thrown by mediawiki.special.search\" load.php:150\\n\"TypeError: this.form is null\" TypeError: this.form is null\\nStack trace:\\n@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:2:185\\njQuery.event.dispatch@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:65:771\\njQuery.event.add/elemData.handle@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:60:313\\njQuery.event.trigger@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:64:460\\n.trigger/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:75:425\\n.each@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:5:216\\njQuery.prototype.each@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:2:215\\n.trigger@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:75:404\\n@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:2:130\\njQuery.Callbacks/fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:44:928\\njQuery.Callbacks/self.add@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:45:488\\njQuery.fn.ready@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:48:879\\njQuery.fn.init@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:41:68\\njQuery@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:1:637\\n@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:1:84\\n@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:1:1\\nrunScript@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:160:473\\nexecute/</checkCssHandles@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:160:958\\nexecute/</cssHandle/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:161:96\\njQuery.Callbacks/fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:44:928\\njQuery.Callbacks/self.fireWith@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:46:258\\njQuery.Callbacks/self.fire@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:46:301\\naddEmbeddedCSS@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:155:871\\nexecute@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:161:552\\nmw.loader</<.implement@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:168:145\\n@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z line 4 > eval:42:29\\n.globalEval/<@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:4:655\\n.globalEval@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:4:621\\nmw.loader</<.work@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:164:68\\nrequest@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:162:258\\nmw.loader</<.load@https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141210T212029Z:169:720\\n@https://www.mediawiki.org/w/index.php?title=Special%3ASearch&profile=advanced&search=mw.util.addPortletLink&fulltext=Search:248:1\\n```'}, 'authorPHID': 'PHID-USER-qgqq35kbi5wss2tlgmhg', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1421434986, 'spacePHID': None, 'dateCreated': 1418658101, 'dateModified': 1423190463, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Many \"(Cannot contact the database server: Too many connections (208.80.154.18))\" errors', 'description': {'raw': 'Recently, there has been a rapid increase in errors like:\\n\\n```\\nSorry! This site is experiencing technical difficulties.\\n\\nTry waiting a few minutes and reloading.\\n\\n(Cannot contact the database server: Too many connections (208.80.154.18))\\n```\\n\\nThis happens not only when I open dozens of wikitech pages, but also when I reload single pages afterwards.'}, 'authorPHID': 'PHID-USER-vk6mlmacfhx77egryy5i', 'ownerPHID': 'PHID-USER-22bsa5u75jz3ci3wnplu', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-22bsa5u75jz3ci3wnplu', 'dateClosed': 1424571360, 'spacePHID': None, 'dateCreated': 1418544923, 'dateModified': 1496861803, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Wikitext editing toolbar for Flow', 'description': {'raw': 'Turns out Flow is a great tool for newbies compared to free-form wikitext. Well, at least until the point where they need to create a link or they want to add some basic formatting. Especially if the newbies are defaulting to VisualEditor, they might have difficulties posting anything other than plaintext and full URLs.\\n\\n{F21334 size=full}\\n\\nTrimming the selection was discussed, and discovered to be both subjectively-desirable and technically-complicated. Newcomers will eventually have an alternative VE interface, to satisfy the requests for a less complicated set of buttons. So, please implement the full/default WikiEditor toolbar.\\n\\nFurther notes at {T90052}\\n\\nSee also: {T93243}'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-uciss2jl2e4ifxqqk7wk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-uciss2jl2e4ifxqqk7wk', 'dateClosed': 1523032235, 'spacePHID': None, 'dateCreated': 1418336289, 'dateModified': 1585699802, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Wordbreak detection is faulty for selection starting just down-page of a single character', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Place a cursor after a text like \"sub-heading 1\"\\n3.Open the link inspector\\n\\nObserve that the character 1 is not getting selected and the link inspector is opening at the end of the line\\n\\n{F20734}\\n'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426728269, 'spacePHID': None, 'dateCreated': 1418251189, 'dateModified': 1427330408, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Message 'visualeditor-find-and-replace-regular-expression' missing\", 'description': {'raw': \"Message 'visualeditor-find-and-replace-regular-expression' missing.\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418238207, 'spacePHID': None, 'dateCreated': 1418237110, 'dateModified': 1443277961, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Chinese table contents are lost when saving in VisualEditor, unless the first letter is in the Latin alphabet', 'description': {'raw': \"[[ https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&offset=20141127161632#Input_Chinese_to_table_will_disappear_when_saving_unless_start_with_an_English_alphabet.__51109 | Original report ]] by Cwlin0416 on 27 November 2014:\\n\\nInput Chinese to table will disappear when saving unless start with an English alphabet.\\n\\nIf i just type Chinese into table, it can't be saved, if i start with an English alphabet, the problem is solved.\\n\\n\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418323773, 'spacePHID': None, 'dateCreated': 1418190225, 'dateModified': 1508045014, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Vertical alignment of the \"add template\" button and the search box is incorrect in template dialog in VisualEditor when using the OOjs UI MediaWiki theme', 'description': {'raw': 'See screenshot:\\n\\n{F20272}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418412481, 'spacePHID': None, 'dateCreated': 1418156342, 'dateModified': 1443277963, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'We need to pick a highlight colour and use it consistently in VisualEditor when using the OOjs UI MediaWiki theme', 'description': {'raw': 'See screenshot:\\n\\n{F20262}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418332790, 'spacePHID': None, 'dateCreated': 1418156052, 'dateModified': 1443277965, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Replace and Replace all buttons are clipped in VisualEditor when using the OOjs UI MediaWiki theme', 'description': {'raw': 'See screenshot:\\n\\n{F20257}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418411234, 'spacePHID': None, 'dateCreated': 1418155912, 'dateModified': 1443277970, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Vertical alignment of text in the search-and-replace field is off in VisualEditor', 'description': {'raw': 'See screenshot:\\n\\n{F20257}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418937172, 'spacePHID': None, 'dateCreated': 1418155886, 'dateModified': 1443277970, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parameter \"add more information\" label \"No unused fields\" placed oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme', 'description': {'raw': 'See screenshot:\\n\\n{F20244}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418411637, 'spacePHID': None, 'dateCreated': 1418155549, 'dateModified': 1443277970, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parameter \"add more information\" field floats very oddly in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme', 'description': {'raw': 'See screenshot:\\n\\n{F20244}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418411622, 'spacePHID': None, 'dateCreated': 1418155514, 'dateModified': 1443277975, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'We should set \"destructive\" on parameter remove buttons in the transclusion dialog in VisualEditor when using the OOUI MediaWiki theme', 'description': {'raw': 'See screenshot:\\n\\n{F20244}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418237159, 'spacePHID': None, 'dateCreated': 1418155481, 'dateModified': 1438736308, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Per-site configuration for enabling Media Viewer', 'description': {'raw': \"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/231 //\\n\\n== Narrative ==\\n\\nAs a development team, we can enable Media Viewer by default on a few pilot sites, so that we can try it out in a limited release before deploying it everywhere.\\n\\n== Acceptance Criteria ==\\n\\nAdd a site configuration option with which Media Viewer can be enabled for every user (including non-logged-in) on a few pilot wikis(e.g. Commons, French, Hungarian, Korean)\\n * Configure Beta Features so that when Media Viewer is enabled, it does not show up as a beta option anymore\\n * We can adapt the code used by VisualEditor for the same purpose\\n * After we've tested the feature on a few wikis, we may want to gradually increase the number of sites -- or enable it everywhere, based on community feedback.\\n\\n\\n== Related Bugs ==\\n\\n== Related Stories ==\\n\\n== Related Changesets ==\\n\\n\\n\\n [[https://gerrit.wikimedia.org/r/117374 | https://gerrit.wikimedia.org/r/117374]] \"}, 'authorPHID': 'PHID-USER-64gvupsl7ajewpshylma', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-64gvupsl7ajewpshylma', 'dateClosed': 1418056791, 'spacePHID': None, 'dateCreated': 1418056781, 'dateModified': 1418057019, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Opt-In for BetaFeatures', 'description': {'raw': \"//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/43 //\\n\\n== Narrative ==\\n\\nAs a user, I want the option to enable Visual Editor, if it is not available by default on this site.\\n\\n== Acceptance Criteria ==\\n\\nSome sites require user opt-in for the VisualEditor (the English and German Wikipedias in particular aren't ready yet to make this feature available by default). So we would like to make the basic version of VisualEditor available as a prominent BetaFeature -- but for those sites only. For example, we could handle this issue by having a site whitelist/blacklist for each beta feature -- or there may also be other technical solutions that work just as effectively to achieve the same results.\\n\\nSee more feature requirements here:\\n\\n [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] \\n\\n\\n\\n\\n\\n== Related Bugs ==\\n\\n== Related Stories ==\"}, 'authorPHID': 'PHID-USER-64gvupsl7ajewpshylma', 'ownerPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-64gvupsl7ajewpshylma', 'dateClosed': 1418054268, 'spacePHID': None, 'dateCreated': 1418054265, 'dateModified': 1418056731, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Expose the production citoid service publicly so we can start switching scripts over to use it', 'description': {'raw': \"AFAICT this hasn't been done yet?\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422075147, 'spacePHID': None, 'dateCreated': 1417898198, 'dateModified': 1461837156, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Show the VisualEditor toolbar/editor chrome as soon as VE scripts are loaded, rather than blocking on waiting for the content to load', 'description': {'raw': ''}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1425310298, 'spacePHID': None, 'dateCreated': 1417558133, 'dateModified': 1660398838, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor page options menu goes off-screen in RTL wikis', 'description': {'raw': 'The Page options menu, which appears when the \"hamburger\" button is clicked, goes off-screen in RTL wikis.\\n\\nScreenshot with wrong display in Hebrew:\\nhttps://commons.wikimedia.org/wiki/File:VisualEditorBug2a.png\\n{F168546}\\n\\nScreenshot with correct display in English:\\nhttps://commons.wikimedia.org/wiki/File:VisualEditorBug2b.png\\n{F168548}\\n\\n(I have a vague recollection that I reported it once, but I cannot find it now. If somebody does find it, please mark this one as a dupe.)'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418937160, 'spacePHID': None, 'dateCreated': 1417531699, 'dateModified': 1443277979, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Support legal requirements about publishing', 'description': {'raw': '**Context**\\n\\nAdjust the publishing UI to meet the legal requirements for attribution.\\n\\n**Narrative**\\n\\nAs a user, I can be informed about the terms under which my content gets published, so that I can just ignore them but no potential legal concerns are raised.  \\n\\n**Acceptance Criteria**\\n\\n  # When the user starts a translation, legal text is provided in the new panel dialog as shown in the design notes:\\n  ## The legal text is similar to the one appearing in the wikitext editor (those links should point to the same place).\\n  ## The only difference is that the \"By pressing the \\'X\\' button\" part should match the name of the button in the UI for all languages\\n  # We need to solve the case of users building a URL to access the translation view and thus bypassing the legal agreement, here is how we\\'ll do that:\\n  ## For users that started a translation (and have been exposed to the legal terms already) we should let them get into he translation at any time without any additional interruption.\\n  ## For users that try to access the translation view directly for an article they have not explicitly started before, instead of directing them to the Translation view, they will be directed to the Translation Dashboard. There, the new translation dialog will be open and they will be able to start the translation with a single click (after reading the legal terms, as we all usually do).\\n  # Read the acceptance criteria 1 again, and realise that this affects not only the \"new translation dialog\" but any entry point. Go and fix it for the red link entry point, and remember for future entry points to either (a) link to the Dashboard with the new translation fields pre-filled or (b) show the legal terms, or you may go to jail.\\n\\n**Design notes**\\n\\nThe new translation dialog should incorporate the legal text, and we need to make sure that users are exposed at leas once (and prefereably only once) to it:\\n\\n{F17019}\\n\\n\\nWhen a user tries to access another user\\'s draft:\\n- The draft content becomes non-interactive and translucent (opacity: 0.5) to indicate it is \"disabled\".\\n- Publish button and saving indicator are hidden.\\n- A dialog is shown in the warning area (view mockup below). It provides (a) a link to the translation author page, (b) a link to start a new translation (will go to the dashboard with the \"new translation\" dialog open and the fields pre-filled), (c) the legal text (note that the name of the button mentioned should match the current UI) and (d) a button to continue.\\n- If the user continues, the above described elements would disappear and the user would be allowed to edit the draft.\\n\\n{F17098}'}, 'authorPHID': 'PHID-USER-ttw4tpoosxc4pbmskrla', 'ownerPHID': 'PHID-USER-m2yck6646cdt5t6zkta4', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ttw4tpoosxc4pbmskrla', 'dateClosed': 1419258989, 'spacePHID': None, 'dateCreated': 1417153277, 'dateModified': 1426054999, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor not updating in beta labs', 'description': {'raw': 'As of this writing, http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version says beta labs is running a 20-hour old version of VE, and that seems to be accurate given that there are a few bugs that are fixed in master but not in beta.'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1417552368, 'spacePHID': None, 'dateCreated': 1417039011, 'dateModified': 1422982996, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'RESTBase / Parsoid integration - waiting for parsoid deploy', 'description': {'raw': \"We are getting ready to integrate Parsoid with RESTBase. This task tracks our progress and what's left to do.\\n\\nGenerally, we need a way to communicate multiple mime entities both in POST requests to Parsoid, and in responses from Parsoid back to RESTBase. We could use [RFC 2387](https://tools.ietf.org/html/rfc2387) or [RFC 2388](https://www.ietf.org/rfc/rfc2388.txt), but this seems to be a bit cumbersome especially for the response part. Instead, we can just use a simple JSON encoding with a structure that's otherwise basically identical to MIME.\\n\\nThe downside of using JSON is possibly efficiency (quite a bit more escaping going on, especially for HTML-in-JSON). However, we could address that later by optionally using a binary encoding like [msgpack](http://msgpack.org/) without changing the message structure itself.\\n\\nAnother option to consider would be to flatten the structure by using names like `original.html`. This would make it easy to encode the same message as `multipart/related`.\\n\\n== Implementation notes ==\\n\\n- Parsoid: Slightly simpler format done & deployed. Needs to be updated to indicate the mime types as documented above.\\n- RESTBase: Prototype implementation.\\n  - should pass to Parsoid:\\n    - previous revision's HTML + data-parsoid OnEdit\\n    - current revision's HTML + data-parsoid OnDependencyChange\\n- Parsoid WIP implementation: https://gerrit.wikimedia.org/r/#/c/165685/\\n- RESTBase to be done\\n\"}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'dateClosed': 1424194514, 'spacePHID': None, 'dateCreated': 1416964657, 'dateModified': 1463091195, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Rename MediaWiki release tags', 'description': {'raw': 'In BugZilla, the MediaWiki product had milestones like \"1.1 release\", \"1.20.x release\" and \"1.25.0 release\" etc.\\n\\nIndividual MediaWiki extensions didn\\'t have such a milestone, but we did have shared ones for extensions like \"MW 1.18 version\", \"MW 1.14 version\".\\n\\nTo avoid clashing with other project\\'s release tags (see also T75899), we should rename the MediaWiki core ones to include \"MediaWiki\" or \"MW\".\\n\\nWhile at it I\\'d like to propose merging the ones formerly for extensions to be the same (e.g. merge \"1.24.0 release\" and \"MW 1.24 version\" into \"MediaWiki-1.24\" or something like that.'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1421156230, 'spacePHID': None, 'dateCreated': 1416944367, 'dateModified': 1468339069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create remaining VisualEditor projects and migrate \"tracking\" tasks into the relevant projects', 'description': {'raw': 'We\\'re scrapping tracking bugs\\n\\n* All VE projects\\' descriptions should have \"Reminder: All VisualEditor-related tasks should be tagged with #VisualEditor as well, for tracking, triage and management purposes.\" appended.\\n* All projects are regular (briefcase) type.\\n\\n| Project | Description | Task it replaces\\n| #VisualEditor-Performance | Performance issues with #VisualEditor. | T51685 |\\n| #VisualEditor-CopyPaste | Copy paste issues with #VisualEditor. | T35105 |\\n| #VisualEditor-InterfaceLanguage | Multi-lingual interface (i18n, l10n, RTL) issues with #VisualEditor. | N/A |\\n| #VisualEditor-Links | Link editing in #VisualEditor (not #VisualEditor-MediaWiki specific). | N/A |\\n| #VisualEditor-Media | Media editing in #VisualEditor (not #VisualEditor-MediaWiki specific). | N/A |\\n| #VisualEditor-MediaWiki-Plugins | Performance issues with #VisualEditor. | T48803 |\\n\\n\\nMerge into existing projects:\\n\\n| Tracker | Projects |\\n| T68083 | #VisualEditor, #VisualEditor-ContentEditable |\\n| T69690 | #VisualEditor, #VisualEditor-MediaWiki-Media |\\n| T67955 | #VisualEditor, #VisualEditor-EditingTools |\\n| T72372 | #VisualEditor, #VisualEditor-MediaWiki-Mobile, #Browser_Support_Google_Android |\\n| T49780 | #VisualEditor, #VisualEditor-EditingTools |\\n| T52781 | #VisualEditor, #VisualEditor-Initialisation |\\n| T54327 | #VisualEditor, #VisualEditor-Initialisation |\\n| T50789 | #VisualEditor, #VisualEditor-MediaWiki-Links |\\n| T55604 | #VisualEditor, #VisualEditor-MediaWiki-Templates |\\n| T53792 | #VisualEditor, #VisualEditor-ContentLanguage |\\n| T35126 | #VisualEditor, #VisualEditor-ContentLanguage |\\n| T35077 | #VisualEditor, #VisualEditor-ContentLanguage |\\n| T41596 | #VisualEditor, #VisualEditor-Tables |\\n| T39870 | #VisualEditor, #VisualEditor-MediaWiki-Media |'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422425192, 'spacePHID': None, 'dateCreated': 1416938037, 'dateModified': 1468414651, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression pre-wmf10] VisualEditor does not load on beta labs', 'description': {'raw': 'Errors: \\n\\n\"Exception thrown by papaparse\" load.php:161\\n\"TypeError: document.getElementById(...) is null\"\\n\\n\"Exception thrown by user callback\" load.php:161\\n\"TypeError: mw.log.warning is not a function\"'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'dateClosed': 1416956559, 'spacePHID': None, 'dateCreated': 1416929762, 'dateModified': 1438736343, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'maiwiki: s3.labsdb server alias maiwiki.labsdb missing in /etc/hosts', 'description': {'raw': \"my bot found maiwiki at meta_p and tried to start running queries, but this fails.\\n\\nname value must be 'Wikipedia' but name is currently a char sequenze repeating hex E0A4B5\\n```\\nMariaDB [(none)]> select *, hex(name) from meta_p.wiki where dbname like 'mai%';\\n+---------+------+------------+-----------+--------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+--------------------------------------------------------------+\\n| dbname  | lang | name       | family    | url                      | size | slice     | is_closed | has_echo | has_flaggedrevs | has_visualeditor | has_wikidata |                                                    hex(name) | \\n+---------+------+------------+-----------+--------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+--------------------------------------------------------------+\\n| maiwiki | mai  | ?????????? | wikipedia | http://mai.wikipedia.org |    1 | s3.labsdb |         0 |        1 |               0 |                1 |            1 | E0A4B5E0A4BFE0A495E0A4BFE0A4AAE0A4BFE0A4A1E0A4BFE0A4AFE0A4BE |\\n+---------+------+------------+-----------+--------------------------+------+-----------+-----------+----------+-----------------+------------------+--------------+--------------------------------------------------------------+\\n1 row in set (0.00 sec)\\n```\\nmaiwiki.labsdb missing in /etc/hosts\\n```\\n$ mysql -hmaiwiki.labsdb\\nERROR 2005 (HY000): Unknown MySQL server host 'maiwiki.labsdb' (0)\\n```\\n\"}, 'authorPHID': 'PHID-USER-rbcxdzszrm6s4izt67kj', 'ownerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'dateClosed': 1416937178, 'spacePHID': None, 'dateCreated': 1416916519, 'dateModified': 1416937178, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Combine imageinfo requests on load', 'description': {'raw': '1. Go to http://en.wikipedia.org/wiki/Barack_Obama as a logged-in user in Chrome\\n2. Open the inspector, go to the network panel, click the filter icon and select \"XHR\"\\n3. Click Edit beta\\n4. Observe lots of POST /w/api.php requests, one for each image\\n\\nWe should combine these requests rather than doing a separate one for each image.'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422914635, 'spacePHID': None, 'dateCreated': 1416886111, 'dateModified': 1630659624, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression wmf9] VisualEditor fails to load (ve.ui.MobileContext.css not defined?)', 'description': {'raw': 'Open up the wikitext editor and attempt to switch to VE. It no longer works. Clicking has no effect and you remain on the wikitext editor.\\n\\nOn Chrome and Firefox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416515441, 'spacePHID': None, 'dateCreated': 1416483000, 'dateModified': 1443277984, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73646', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Non-numeric colspan/rowspan values are normalized, or corrupted to NaN', 'description': {'raw': 'See e.g. https://fr.wikipedia.org/?diff=109114947\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416006013, 'spacePHID': None, 'dateCreated': 1415995140, 'dateModified': 1417571284, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73430', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: shortcut(Ctrl+1) for Page Title does not work on Mac', 'description': {'raw': 'Betalabs and test2\\n\\nIn VE on Mac click Ctrl+1 which should insert Page Title - nothing happens. \\n\\nAll other shortcuts - Ctrl+0,2-7 - work.\\n\\n\\nCtrl+1 works in IE 11.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416431095, 'spacePHID': None, 'dateCreated': 1415837760, 'dateModified': 1417571287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73340', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf7] Button in Add a Template dialog is labeled as \"Hide Options\", instead of \"Show Options\"', 'description': {'raw': 'screenshot\\n\\nEnvironment- beta\\n\\n1> Select Insert -> Template \\n2> In the resulting add a template dialog the button is labeled \"Hide Options\".See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14839}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415652897, 'spacePHID': None, 'dateCreated': 1415647980, 'dateModified': 1417571286, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73235', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Viewport sometimes scrolls to bottom when loading some pages in Chrome', 'description': {'raw': \"If I open https://en.wikipedia.org/wiki/James_Braid_(surgeon)?veaction=edit in Chrome 38, the viewport initially jumps to the bottom of the page (the references list). If I press a cursor key, I'm back at the top. If I reload the page, the problem is not reproducible. Cannot reproduce in Firefox either.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415902195, 'spacePHID': None, 'dateCreated': 1415562720, 'dateModified': 1417571285, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73208', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf7] Template dialog no longer takes focus on load', 'description': {'raw': 'This is due to the fix applied in https://gerrit.wikimedia.org/r/#/c/170280/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415645584, 'spacePHID': None, 'dateCreated': 1415376420, 'dateModified': 1633290163, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73138', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf7] Deleted template parameters aren't actually deleted\", 'description': {'raw': 'When I click on the \"Bin\" icon to delete an empty parameter from a template, the system doesn\\'t delete it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-j3xqvy6nbc2vdqsijned', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415666118, 'spacePHID': None, 'dateCreated': 1415368440, 'dateModified': 1417571290, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73134', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf7] The cursor stays active on CE even after opening the dialog for Basic Reference/Citation/Reference list/Page Settings', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open any of the following dialog:\\nBasic Reference/Citation/Reference list/Page Settings\\n\\n2.Start typing\\n\\nObserve that , the text that you are typing is appearing on CE, as the cursor is active there instead of inside the dialog\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415618104, 'spacePHID': None, 'dateCreated': 1415309880, 'dateModified': 1417571286, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73097', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Drag-and-drop an inserted image slices a table', 'description': {'raw': 'Dragging images to table\\n\\n1. In VE insert a table(do not enter anything in the table).\\n2. Inser->Media-> select and insert any image outside the table.\\n3. Select the inserted image and drag it to the table - make sure that the insertion indication(an underscore) is displayed outside of the table,  on the right side. \\n\\nDrop the table  - the table becomes separated in two parts. The attached screenshot shows the result of several attempts of the described scenario\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14885}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415809490, 'spacePHID': None, 'dateCreated': 1415146800, 'dateModified': 1417571287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72995', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] Link Suggestions are not appearing on placing the cursor inside it', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Select a text\\n2.Press command+k\\n3.When the link inspector opens , place the cursor inside the textbox which already has the selected text as link target name\\n\\nObserved Result:\\nLink suggestions are not appearing after placing the cursor inside it.\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415140252, 'spacePHID': None, 'dateCreated': 1415126640, 'dateModified': 1417571291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72959', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using browser native interactive spell-check when the changed word in the only item in the paragraph causes endless insertions in Firefox', 'description': {'raw': 'Steps:\\n1. In Firefox, enable \"Preferences > Advanced > General > Browsing > Check my spelling as I type\"\\n2. On an empty line (slug), write \"occurence\"\\n3. Observe wiggly red line; right click and change it to \"occurrence\"\\n4. Observe explosion\\n\\nPossibly a unicorning issue?\\n\\n\\nWorking steps:\\n\\n1. On an empty line (slug), write \"Foo occurence\" or \"occurence bar\"\\n2. Observe wiggly red line; right click and change it to \"occurrence\"\\n3. Observe non-explosion\\n\\n(i.e., it works fine if there\\'s any other content in the content node)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1423854637, 'spacePHID': None, 'dateCreated': 1415058420, 'dateModified': 1424479034, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72929', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Fix nowiki heuristics for quotes', 'description': {'raw': \"See https://fr.wikipedia.org/w/index.php?title=Univers_cin%C3%A9matographique_Marvel&curid=5796605&diff=108676945&oldid=108668984 for a particularly bad sequence of nowikis.\\n\\nWe should examine this and NicoV's suggestions below and see what is realistic / feasible. But, at least a couple of back-to-back nowikis should be avoidable.\\n\\nNicoV says (on https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=631914857#Unnecessary_succession_of_nowiki)\\n\\n-----\\n    There are 4 sets of nowiki tags:\\n\\n        The first one is a combination of an opening tag and a closing tag <nowiki>...</nowiki>.\\n        The second one is a self-closing nowiki tag <nowiki/> (just after the previous set) : it's totally useless, and brings nothing except more complexity to the wikitext\\n        The third one is a self-closing nowiki tag <nowiki/> (just before the next set) : same remark as above\\n        The fourth one is a combination of an opening tag and a closing tag <nowiki>...</nowiki>.\\n\\n    My report is that 2 sets are completely useless (first and second are redundant; third and fourth are redundant).\\n    Of course, there's also the problem reported many times, a long time ago, that if nowiki are added they should be added only around the part that needs them not around a whole part of a sentence, but it was not the main issue I was reporting. For this, as it already been said so many times, my preferred methods (in order):\\n\\n        Use {{'}} (it should be possible to configure VE on each wiki to know if there's such a template, that's what I'm doing for example in WPCleaner's configuration)\\n        Use '<nowiki/>'' (nowiki between the single quote and the italic formatting)\\n        Use <nowiki>'</nowiki>'' (nowiki around the single quote)\\n-----\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1420556920, 'spacePHID': None, 'dateCreated': 1414811340, 'dateModified': 1428510506, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72844', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] Page Settings dialog box - an opacity issue', 'description': {'raw': \"Page settings box opacity issue\\n\\nfound in test2 and betalabs\\n\\nSteps to reproduce: \\n\\n1. In VE - click on Page options icon. \\n2. Select Page settings->click in the check box 'Redirect this page to'\\n3. Start typing 'Something' (no quotes)\\n4. At some point of typing(or after you type 'Something' and then start to delete it a letter by letter) - a drop-down list of suggestions appears partially displaying underlying options for 'Show the Table of Contents' options. Look at the attached screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15193}\"}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415039903, 'spacePHID': None, 'dateCreated': 1414790040, 'dateModified': 1417571291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72838', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Put table cell editing controls in the context of the cell/selection so they aren't so hard to find\", 'description': {'raw': 'screenshot\\n\\n(On beta.wmflabs) I had a very hard time finding the table editing menus for Merge cell. I knew they were available, but assumed they would be part of the normal attached-to-the-table menu system.\\n\\nI also didn\\'t notice the \"Content cell\" menu appear until it was pointed out to me.\\n\\nI think it would be more intuitive, to put those controls next to the elements I\\'m changing, as shown in the mockups at https://www.mediawiki.org/wiki/VisualEditor/Design/Table_editor#Version_2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F14988}'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-flenunkasbjk4topxvaj', 'dateClosed': 1417649426, 'spacePHID': None, 'dateCreated': 1414694280, 'dateModified': 1423098545, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72770', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Please let me drop the cursor into the table caption if it exists. Please?', 'description': {'raw': 'See e.g. the table in section 0 of the link.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/User:Jdforrester_(WMF)/Sandbox?veaction=edit'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415040528, 'spacePHID': None, 'dateCreated': 1414624080, 'dateModified': 1417571289, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72724', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf5] FocusableNodes not selectable when surface is blurred', 'description': {'raw': \"1. Open VE on a page that contains a focusable node\\n2. Click out of the surface so it's blurred and the toolbar tools are greyed out (selection is a ve.dm.NullSelection)\\n3. Try to select a focusable node by clicking on it\\n4. Nothing happens\\n5. Click to drop the cursor in some normal text\\n6. Repeat #3, observe that it works now\\n\\nThis also causes bug 72719: double-clicking focusable nodes fires their double-click handler and opens the associated dialog, but the selection is still null, so the dialogs don't open with the right context.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414780365, 'spacePHID': None, 'dateCreated': 1414623540, 'dateModified': 1417571293, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72721', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6] There is an extra space appearing at the top of the toolbar inside VE', 'description': {'raw': 'Screenshot\\n\\nThere is an extra space appearing at the top of the toolbar inside VE\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14781}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414633478, 'spacePHID': None, 'dateCreated': 1414608180, 'dateModified': 1417571291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72693', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting from a paragraph-terminating node to a paragraph-terminating node (?) is throwing \"Unbalanced set of replace operations found\"', 'description': {'raw': 'Reproduce:\\n\\n1. go to https://fi.wikipedia.org/wiki/User:Stryn/VE?veaction=edit\\n2. highlight all texts from the end of \"This is just a test.[1]\" to end of \"Visuaalinen muokkain.[2]\" and press backspace button or delete or whatever and nothing happens - VE just gets stuck.\\n3. you can\\'t save the page nor switch to wikitext editor even if you have made changes to the page.\\n\\nIf you highlight text from \"This is just a test.[1]\" to \"This is not.\" it\\'s working as it should. So probably the problem is with the references.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72640'}, 'authorPHID': 'PHID-USER-6majuboi566q3ozbh27r', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'dateClosed': 1426625539, 'spacePHID': None, 'dateCreated': 1414442040, 'dateModified': 1427127754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72579', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] “Uncaught Error: offset -1 out of bounds” when adding bullet/numbered list with link inspector open', 'description': {'raw': 'screenshot of the console error\\n\\nEnvironment- test2,production,beta\\n\\n1>In a blank page, open the link inspector,type in some text in the link input box and keep the inspector open.\\n2> While the inspector is open ,click on to add a bullet/numbered list.\\n3> JS  console error “Uncaught Error: offset -1 out of bounds” and the inspector remains open.See screenshot.\\n\\nClicking on Done or Remove does not close the inspector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72494\\n\\n**Attached**: {F15103}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415129466, 'spacePHID': None, 'dateCreated': 1414419600, 'dateModified': 1417571288, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72558', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf3] Wikitext warning not showing up anymore?', 'description': {'raw': \"I don't seem to be able to trigger the warning with anything on any production wiki today.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414172813, 'spacePHID': None, 'dateCreated': 1414156020, 'dateModified': 1417571293, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72475', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Opening a very large complex transclusion sometimes hangs in Firefox', 'description': {'raw': 'Firefox with the wrong box\\n\\nSteps to reproduce:\\n\\n1.  Open [[William Shakespeare]] in VisualEditor. \\n\\n2.  Scroll to the ==References== section and select the contents (a complex transclusion).\\n\\n3.  Try to open it so you can edit it.\\n\\n\\nThis hangs in Firefox 32 with this error message:\\n\\nWarning:  Unresponsive script\\n\\nA script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.\\n\\nScript: https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141016T200718Z:89\\n\\n\\nIt opens correctly (but slowly) in Chrome and Safari, and sometimes in Firefox, too.  When it fails to open correctly, then it displays the contents in the wrong dialog box (see attachment).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15370}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1426449550, 'spacePHID': None, 'dateCreated': 1414016880, 'dateModified': 1427317705, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72401', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Actually run MediaWiki-VisualEditor's tests for MWHeadingNode / MWPreformattedNode\", 'description': {'raw': \"Right now we have a hack in ve.test.utils.js that reregisters the core versions of HeadingNode and PreformattedNode to ensure MWHeadingNode and MWPreformattedNode aren't used, because using them would break the VE core tests when run in VE-MW.\\n\\nThis is horrible, because it makes us unable to test specific behavior in the MW nodes. For instance, https://gerrit.wikimedia.org/r/#/c/162310/3 fails its own tests because those tests use HeadingNode rather than MWHeadingNode, even though the tests in question were clearly designed to use MWHeadingNode.\\n\\nWe should come up with a way that MW nodes can be not registered for code tests, but be registered for MW tests.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1424199112, 'spacePHID': None, 'dateCreated': 1414016460, 'dateModified': 1424273392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72398', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Link inspector closes itself immediately in Internet Explorer', 'description': {'raw': 'IE11 test2 and betalabs\\n\\nSteps to reproduce: \\n\\n1. Open VE-> try to insert a link(via a shortcut or by clicking on the option) - the box(class=\"oo-ui-window-isolated oo-ui-ltr\" ) shows up and disappears momentarily.\\n\\n2. Editing links - presents the same problem \\n\\nDebugger complains about load.php \"Unable to get property \\'from\\' of undefined or null reference\\' rangeSelection is undefined.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414446810, 'spacePHID': None, 'dateCreated': 1414014960, 'dateModified': 1417571292, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72392', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf5] The \"Show Options\" inside Transclusion dialog box is blank, not bringing up the other options to add parameter/template/content', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Template\\n3.Select any template\\n4.Click on \"Show Options\"\\n\\n\\nObserved Result:\\nThere is no advanced option showing up on the left panel.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F15057}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413933486, 'spacePHID': None, 'dateCreated': 1413838440, 'dateModified': 1417571295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72278', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Adding category sort keys no longer working', 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Open a page and go to Page options > Categories.\\n\\n2.  (Add a category if none exist.)  Edit a category to add a sort key.\\n\\n3.  Save page.\\n\\n4.  Check diff:  no sort key was added.  :-(  \\n\\n\\nConfirmed in Firefox 32 and Safari 6.2 on Macs and Windows, so it's probably happening everywhere.\\n\\nThis doesn't seem to be bug 48555.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413936684, 'spacePHID': None, 'dateCreated': 1413506580, 'dateModified': 1417571294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72168', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression] Can't cut or (sometimes) paste in multiple browsers\", 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Open a page in Firefox (my version is 32).\\n\\n2.  Select some text.\\n\\n3.  Press Ctrl-X or Command-X.\\n\\n4.  Notice that nothing happened.\\n\\n\\nPaste (Ctrl-V) might be working intermittently, but you have to copy rather than cut the text to do that.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413654562, 'spacePHID': None, 'dateCreated': 1413504300, 'dateModified': 1417571293, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72164', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection starting on a tooled item (e.g. link) always shows the context menu', 'description': {'raw': 'Start a selection inside a link and drag to outside it. The context menu never disappears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413574383, 'spacePHID': None, 'dateCreated': 1413494100, 'dateModified': 1417571299, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72152', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf4] Red border is appearing around required parameters before focus moves away', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open Cite>Book or Cite>Journal\\n3.Place the cursor inside the Title field\\n\\nObserved Result:\\n\\nA weird red border is surrounding the textfield instead of light blue highlight\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15258}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413585719, 'spacePHID': None, 'dateCreated': 1413408120, 'dateModified': 1417571295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72096', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf4] After placing the cursor on a slug, placing it anywhere in the page which follows that particular slug throws \"TypeError: Cannot read property \\'getSelection\\' of null\"', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a bullet or numbered list\\n3.Keep on adding indentation to the list to create slugs\\n4.Place your cursor inside the slug to add an item to the list\\nObserved Result:\\nIt throws error in the console:TypeError: Cannot read property 'getSelection' of null\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15252}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413410282, 'spacePHID': None, 'dateCreated': 1413406020, 'dateModified': 1417571295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72095', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Convert mediawiki qunit from grunt-contrib-qunit (PhantomJS) to grunt-karma (Chromium)', 'description': {'raw': \"Current pipeline uses the global wmfgrunt slave-script:\\n* [/bin/wmfgrunt](https://github.com/wikimedia/integration-jenkins/blob/0b85d48e60/bin/wmfgrunt)\\n* [/tools/Gruntfile.js](https://github.com/wikimedia/integration-jenkins/blob/0b85d48e60/tools/Gruntfile.js)\\n\\nFetch integration-jenkins.git to test it. As dependencies are pre-compiled and committed to git for Ubuntu Precise, on other platforms, first `cd ./tools; rm -rf node_modules` and `npm install` to provide for your system's architecture.\\n\\nIt's invoked from this macro: https://github.com/wikimedia/integration-config/blob/0b85d48e60/jjb/macro.yaml#L344\\n\\n\\nFor many reasons, we should migrate from grunt-contrib-qunit to Karma, and use Chromium and/or Firefox as browser instead of PhantomJS:\\n* Performance. Chromium is faster.\\n* Accuracy.  PhantomJS is not a browser we support. Its layout and JavaScript engine and version thereof are irrelevant. It's based on a port from an old Safari build. Aside from being old it's also customised and under various abstraction layers. Ideally we'd run in multiple browsers, but even one would be a great start. PhantomJS does support nice features most browsers can't or wont implement, but those are not features we need to run unit tests. We want a real browser.\\n* Ability. While testing fallback behaviour is important, many new browser features are unavailable in PhantomJS. This is actively making it impossible to run tests against modern code such as from OOjs UI and VisualEditor that don't support Safari 4 or 5.\\n\\nhttps://github.com/karma-runner/karma\\nhttps://github.com/karma-runner/karma-chrome-launcher\\nhttps://github.com/karma-runner/karma-qunit\\nhttps://github.com/karma-runner/grunt-karma\\n\\nThis is already being used by OOjs, OOjs UI and VisualEditor standalone. This task is about migrating the pipeline for projects that rely on running in a MediaWiki context. This brings many complexities due to registering and loading of scripts. As well as migrating the bootstrapping code to support Ubuntu Trusty and labs instances (as opposed to prod slavs running Precise).\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426872839, 'spacePHID': None, 'dateCreated': 1413326580, 'dateModified': 1530907040, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72063', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf3] The context menus for Categories are appearing in an incorrect position and also not closing', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add some categories\\n3.Try to open the context menu for it\\n\\nObserved Result:\\nObserve that the context menu is appearing far towards left side of the dialog box and it is not closing when you navigate to other options.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15142}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413333864, 'spacePHID': None, 'dateCreated': 1413318120, 'dateModified': 1417571298, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72052', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  New and changed citations display with blank lines before and after the citation in <references />, if using citation templates', 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Open a page containing the <references /> block (so you can see what happens as you change citations).\\n\\n2.  Create a new citation or edit an existing one, using a citation template (e.g., Cite web) in the Cite menu.\\n\\n3.  See a blank line displayed before and after the citation.  \\n\\nThis can be reproduced in Safari 6.2 and Firefox 32 on Mac OS 10.8.5.  It happens with Marielle's script for Citoid and with manually completed citation templates. cannot be reproduced by adding text to the Basic citation dialog (although it can be reproduced by using the Cite menu within the Basic citation dialog).\\n\\nThis is a display-only problem.  When the page is saved, everything is normal (e.g., https://en.wikipedia.org/w/index.php?diff=629488479&oldid=629487984).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414013635, 'spacePHID': None, 'dateCreated': 1413234900, 'dateModified': 1417571296, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72006', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Edits via API (e.g. through VisualEditor) cause AbuseFilter to work on pre-automerged edit', 'description': {'raw': 'Reported at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Irrelevant_tags , quoting below:\\n\\n> Why would [this edit](http://en.wikipedia.org/w/index.php?title=M.R._Organisation_Limited&curid=44080416&diff=629153289&oldid=629153016) get tagged with copyright violation template removed and speedy deletion template removed if the edit did not remove the templates? Is this a bug in the tags system? The user used HHVM and VisualEditor, is this relevant? 109.79.177.119 09:43, 11 October 2014 (UTC)\\n\\n(The page in question has unfortunately been deleted since, but the data is still there, just hidden.)\\n\\nI did some quick investigating:\\n\\n* If you review the page history a bit (which I managed to do before\\n  it was deleted), the two templates were indeed removed at a point\\n  (and that was correctly tagged) and then restored, with the next\\n  edit being tagged incorrectly.\\n* You can examine the logic that led to that edit being tagged at\\n  [[Special:AbuseFilter/examine/log/10945503]] – if you look at the\\n  row described as \"Unified diff of changes made by edit\", you can see\\n  that AbuseFilter really thinks these tags were removed in that edit\\n  (although they were not).\\n\\n--------------------------\\n**URL**: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29/Archive_131#Irrelevant_tags\\n**See Also**:\\n* {T74329}'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1460198078, 'spacePHID': None, 'dateCreated': 1413023760, 'dateModified': 1490378611, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71947', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression] Link icon is missing in from the toolbar', 'description': {'raw': 'Screenshot\\n\\nLink inspector icon in the toolbar seems to be missing in \\nhttps://en.m.wikipedia.org/\\n\\nHowever, it is appearing in test2 and Betalabs.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14753}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413917906, 'spacePHID': None, 'dateCreated': 1412900640, 'dateModified': 1417571297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71903', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Bring back the edit summary byte counter in the save dialog', 'description': {'raw': \"It's ve-ui-mwSaveDialog-editSummary-count in MWSaveDialog, but there are several issues with it:\\n\\n* It should be stored in a variable, not searched for using jQuery .find() every time\\n* It should be modified with methods on OO.ui.LabelWidget, not jQuery .text()\\n* It should actually be visible\\n\\nI don't know why it's being hidden, but display: none; is set on it, so maybe .hide() is called somewhere?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412890340, 'spacePHID': None, 'dateCreated': 1412800080, 'dateModified': 1417571322, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71837', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf3] Getting stuck inside Media Settings dialog while attempting to change an image', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a new image\\n3.Open the media settings dialog again\\n4.Click on \"Choose a different image\" button\\n5.Select a different image\\n6.Click on \"Apply Changes\" button\\n\\nObserved Result:\\n\\nUser gets stuck inside Media Settings dialog.Cannot close the dialog anymore\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15264}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412799699, 'spacePHID': None, 'dateCreated': 1412798520, 'dateModified': 1417571300, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71832', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf3] For every Math expression, it is not appearing on CE when its gets evaluated for the first time', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a new page with VE\\n2.Go to Insert>Formula\\n3.Insert \"\\\\pi\"\\n\\nObserve that, nothing appears on CE. But if you save the page or review your changes , you will see it actually got added in the page .\\n\\nIf you reopen the page after saving, and try again adding the same math expression it will appear immediately.\\n\\nBut if you try adding a different math expression or modify the existing math function , say for example: make \"\\\\pi\" to \"\\\\sqrt\\\\pi\", it wont render on CE again. \\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=71852\\n\\n**Attached**: {F15254}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413836449, 'spacePHID': None, 'dateCreated': 1412797500, 'dateModified': 1417571297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71829', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Extra characters being inserted when typing in bulleted lists', 'description': {'raw': 'demonstration from office-wiki\\n\\nWhen typing at the end of a line of an item in a bulleted list some character are duplicated or appear on the wrong line, delete/backspace behaves erratically.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n//attachment VE character insertion.m4v ignored as private//'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412889585, 'spacePHID': None, 'dateCreated': 1412796180, 'dateModified': 1417571323, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71827', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf3] Citation dialog inserts empty reference', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert Cite>Website/News/Journal etc\\n\\nObserved Result:\\nAll citation notes are getting added as basic reference, opening them opens the basic reference dialog instead of the citation dialog.\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412799291, 'spacePHID': None, 'dateCreated': 1412795940, 'dateModified': 1417571321, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71825', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf3] Double-typing issues inside CE/media/reference dialogs again in Firefox', 'description': {'raw': 'But not only when typing fast.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412795779, 'spacePHID': None, 'dateCreated': 1412793540, 'dateModified': 1417571300, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71823', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"404 file Not Found Error\" when logging into betalabs', 'description': {'raw': 'While trying to login to betalabs i get \"404 file Not Found Error\" after clicking the Log In button.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412807704, 'spacePHID': None, 'dateCreated': 1412783520, 'dateModified': 1420738421, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71806', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases', 'description': {'raw': '1. Open https://www.mediawiki.org/wiki/QA/Selenium_Workshop in latest stable Chrome.\\n2. Click \"Edit\"\\n3. Put cursor in the first paragraph, insert a single character.\\n\\nExpected:\\n\\nSave button enables, allowing the user to save the page.\\n\\nActual:\\n\\nSave button stays disable, user is unable to save the edit.\\n\\nNo exceptions or warnings on the dev console.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413819814, 'spacePHID': None, 'dateCreated': 1412655300, 'dateModified': 1417571298, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71732', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting annotated text causes space to be removed at annotation separators', 'description': {'raw': 'See https://office.wikimedia.org/w/index.php?diff=118847&oldid=118846\\n\\nSteps to reproduce:\\n\\n1.  Start with a paragraph that says \"Foo \\'\\'\\'bar\\'\\'\\' baz blah blah\".\\n\\n2.  Cut paragraph.\\n\\n3.  Paste paragraph elsewhere.\\n\\n4.  Notice that it now says \"\"Foo \\'\\'\\'bar\\'\\'\\'baz blah blah\" (i.e., minus one space immediately after the word in bold-face formatting).\\n\\nThis also happened with <mark> formatting.\\n\\nThis edit was made in Safari 6 on Mac OS 10.8.5.  I was not immediately able to reproduce this in Firefox 32.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416256242, 'spacePHID': None, 'dateCreated': 1412625180, 'dateModified': 1582152601, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71718', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MWLink nodes inside sub-editor dialogs appear as zero-width', 'description': {'raw': '* Insert a reference (Cite > Basic)\\n* Insert an MWLink node (Ctrl + K > http://www.amazon.com)\\n\\nObserve magic zero-width node. Converting to an annotation makes it work fine.\\n\\nSame happens in media caption dialogs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413638809, 'spacePHID': None, 'dateCreated': 1412470080, 'dateModified': 1417571299, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71652', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The comment icon is repeatedly selected and deselected with the keyboard', 'description': {'raw': 'When selecting text with the keyboard (Shift-arrow), starting the selection range in adjacency to a comment icon repeatedly selects and deselects the icon. Starting the selection not in adjacency to the icon works as expected.\\n\\nIf this is hard to understand, see this page:\\nhttps://en.wikipedia.org/wiki/User:Amire80/comment\\n\\nIt has detailed instructions to reproduce.\\n\\nThis is broken in both LTR and RTL. RTL test page:\\nhttps://he.wikipedia.org/wiki/%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%D7%AA:Amire80/ve-comment-selection\\n\\nThanks to David Chan for helping with minimizing the test case :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/wiki/User:Amire80/comment'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423676261, 'spacePHID': None, 'dateCreated': 1412249460, 'dateModified': 1426018212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71550', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf2] \"Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden\" appears while trying to save a page', 'description': {'raw': 'Uncaught Error: Syntax error, unrecognized expression: div[id ^= mittoHidden appears while trying to save a page in Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412201322, 'spacePHID': None, 'dateCreated': 1412186460, 'dateModified': 1417571323, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71521', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf1] Add a Template dialog does not open, when adding a new Basic reference', 'description': {'raw': 'Environment- test2\\n\\n1> In VE, open Basic citation dialog and enter any citation(book,news,Web or Journal). For ex- enter a book citation.\\n2> Now while the citation is still highlighted select Insert  -> Template.Notice the Add a Template window does not open , instead it opens the Cite Book dialog.\\n\\nBut if you enter a book citation in the CE and while it is still highlighted try to open the Template dialog(Insert  -> Template) . Notice the Add a Template dialog opens.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412040341, 'spacePHID': None, 'dateCreated': 1412006940, 'dateModified': 1417571327, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71417', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf1] Link inspector does not close when clicking out into non-linked text', 'description': {'raw': '1. Open VisualEditor\\n2. Find or create a paragraph with a link followed by some non-linked text\\n3. Inspect the link\\n4. While the link inspector is open, click to drop the cursor in the non-linked text\\n\\nThe link inspector does not close, and instead moves to follow your selection.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=71151'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412090451, 'spacePHID': None, 'dateCreated': 1411770300, 'dateModified': 1417571326, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71373', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Typing more words into a ==Section heading== adds them into the next line, characters out of order', 'description': {'raw': 'See https://office.wikimedia.org/w/index.php?diff=118520&oldid=118519\\n\\nThis was all supposed to be on one line, essentially changing ===One=== to ===One and two===  It displays almost correctly, the equivalent of:\\n\\n===One and two===\\na\\n\\nbut saves completely wrong:\\n\\n===One===\\nndtwoa\\n\\n\\nJames F has a screenshot in e-mail.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415046514, 'spacePHID': None, 'dateCreated': 1411756740, 'dateModified': 1417571292, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71364', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: TitleInputWidget should validate inputs', 'description': {'raw': 'We have isValid() functions for similar inputs, but not this one, so it\\'s possible to try to create a redirect to \"|\" (which Parsoid turns into MediaWiki:Badtitle).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414606641, 'spacePHID': None, 'dateCreated': 1411586340, 'dateModified': 1417571288, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71249', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'API XHR requests from mediawiki do not transmit cookies when editing', 'description': {'raw': 'Looking at the network traffic from visiting a page on enwiki, I saw that when editing a page (both with VE enabled and without it) a few GET requests get performed to API, like in example:\\n\\nhttps://en.wikipedia.org/w/api.php?format=json&uselang=en&action=visualeditor&paction=parse&page=Moravian-Silesian_Region\\n\\nthese requests go out as XHR requests and my browser does not attach any cookie to the request. Of course, this means that any cookie-based test we might want to perform (like using HHVM) will not work as expected.\\n\\nThis would effectively block us from testing hhvm on the API cluster.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-fdo23otm6ztt674vjqko', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411571347, 'spacePHID': None, 'dateCreated': 1411540440, 'dateModified': 1602869330, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71222', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf 22] Inspector loses it UI after scrolling down the page and clicking somewhere else in the document', 'description': {'raw': 'No UI\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the link inspector/math inspector for an existing link\\n3.Close the inspector by clicking on \"Done\" button or you can keep the inspector open\\n4.Now scroll down the page so that the inspector goes outside the current surface\\n5.Now click somewhere else in the document\\n6.Now go back and reopen the previous inspector\\n\\nObserved Result:\\nThere is no UI for the inspector,if you try inspecting some other inspector on the current viewport that will also appear without any UI.\\n\\nfor link inspector if you switch tab and come back to VE, the link inspector will have only the link target suggestions inside it .\\n\\nEnvironment: Betalabs, test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14854}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411510719, 'spacePHID': None, 'dateCreated': 1411428360, 'dateModified': 1443277991, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71153', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf1] When the inspector is still open for a selected node, after placing the cursor in a different position, inspector flickers there', 'description': {'raw': 'video capture of the bug\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open any inspector-Link/Math/Special Character for any existing node\\n3.Now while the inspector is open, place the cursor any where else in the document\\n\\n\\nObserved Result:\\nThe inspector closes and flickers in the new position.\\n\\nSee the video capture attached\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=71373\\n\\n**Attached**: {F14852}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421258168, 'spacePHID': None, 'dateCreated': 1411426740, 'dateModified': 1438735462, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71151', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf 22] Selection does not work while trying to select multiples lines after dragging the selection horizontally over a focusable node', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert a citation/a comment/math node\\n3.Now place your cursor at the beginning of the node that you just added\\n4.Drag the selection vertically, you will be able to do the selection over the next lines\\n5.Now again place the cursor at the beginning of the node added in step 2\\n6.Select the line of the node horizontally and then try to drag the selection vertically\\n\\nObserved Result:\\nThe selection stops at the focusable node and does not get extended towards the next lines.\\n\\nEnvironment:Betalabs, test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411683857, 'spacePHID': None, 'dateCreated': 1411418760, 'dateModified': 1417571324, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71139', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre wmf1] Math inspector closes each time a character is inserted and it tries to parse it', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Formula\\n3.Attempt to insert \"\\\\pi\" inside the inspector\\n\\nObserved Result:\\nAs soon as you type \\\\ in the inspector , it closes and tries to parse that \\\\ and shows error \"Failed to parse (lexing error)\"\\n\\n\\nEnvironment:Betalabs\\nBrowser:Chrome\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413481348, 'spacePHID': None, 'dateCreated': 1411413300, 'dateModified': 1443277994, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71131', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] Jenkins: SQLite database is often locked causing queries to fail', 'description': {'raw': \"https://integration.wikimedia.org/ci/job/mwext-VisualEditor-qunit/11566/\\n\\nArtifact: mw-debug-www.log\\n\\nDatabaseBase::query: Writes done: REPLACE INTO objectcache (keyname,value,exptime) VALUES ('X')\\nSQL ERROR (ignored): database is locked\\n..\\n\\n\\nDatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')\\nSQL ERROR: database is locked\\n..\\n\\n\\nMessageBlobStore::insertMessageBlob failed to update DB: exception 'DBQueryError' with message 'A database error has occurred. Did you forget to run maintenance/update.php after upgrading?  See: https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script\\nQuery: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('en','jquery.ui.button','{}','20140919182152')\\nFunction: MessageBlobStore::insertMessageBlob/single-row\\nError: 5 database is locked\\n\\n\\nDatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')\\nSQL ERROR (ignored): database is locked\\nDatabaseBase::query: Writes done: REPLACE INTO objectcache (keyname,value,exptime) VALUES ('X')\\nSQL ERROR (ignored): database is locked\\n..\\n\\nSQL ERROR (ignored): database is locked\\nDatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')\\nSQL ERROR (ignored): database is locked\\nDatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')\\nSQL ERROR (ignored): database is locked\\nDatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')\\nSQL ERROR (ignored): database is locked\\nDatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')\\nSQL ERROR (ignored): database is locked\\nDatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')\\nSQL ERROR (ignored): database is locked\\nDatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')\\nSQL ERROR (ignored): database is locked\\nDatabaseBase::query: Writes done: INSERT OR IGNORE INTO msg_resource (mr_lang,mr_resource,mr_blob,mr_timestamp) VALUES ('X')\\n...\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1424632547, 'spacePHID': None, 'dateCreated': 1411151220, 'dateModified': 1424632547, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71058', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Dates replaced by [[MediaWiki:Badtitletext]]', 'description': {'raw': 'https://ast.wikipedia.org/w/index.php?title=Peligru_Mariellu&diff=747158&oldid=747157\\n\\nshows 1922 being replaced by [[MediaWiki:Badtitletext]].\\n\\nhttps://ast.wikipedia.org/w/index.php?title=Peligru_Mariellu&diff=747160&oldid=747159\\n\\nshows \"sieglu XX\" being replaced by [[MediaWiki:Badtitletext]].\\n\\nNothing is known about the user\\'s browser, skin, or OS.  It appears that the editor wrote this article at the Spanish Wikipedia, pasted the wikitext code into VisualEditor, and was trying to translate it into Asturian and correct the resulting nowiki mess when this happened.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1422986051, 'spacePHID': None, 'dateCreated': 1411065120, 'dateModified': 1422986051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71011', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Overlay doesn\\'t close, elements aren\\'t clickable when copying dir=\"auto\" values', 'description': {'raw': '1. Open any article\\n2. Select the article title (firstHeading), copy, open the page settings, and set the default sort, and apply.\\n3. try to click any element - it fails.\\n\\nInspect element tells you there is \"ve-ui-overlay-global ve-ui-overlay\" over all...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-cfsvvgbtlqnbt2yokfjf', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412359187, 'spacePHID': None, 'dateCreated': 1410725100, 'dateModified': 1443277996, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70831', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] Cannot open any inspector, throwing error \"Uncaught TypeError: Cannot read property \\'top\\' of undefined\"', 'description': {'raw': \"Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Try to open Link/Math/Language/Special Character inspector\\n\\nObserved Result:\\nNone of them opens and in the console it shows the following error:\\n\\nUncaught TypeError: Cannot read property 'top' of undefined \\n\\nEnvironment:test2.betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70770\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70768\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410559740, 'spacePHID': None, 'dateCreated': 1410551280, 'dateModified': 1443277997, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70782', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf 21] “Uncaught TypeError: Cannot read property 'top' of undefined” when Editor is launched\", 'description': {'raw': \"Environment- test2, beta\\n\\n1> open VE, I get JS console error as “Uncaught TypeError: Cannot read property 'top' of undefined” in Chrome.\\n\\n\\nIn FF the error is TypeError: rect is undefined\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70782\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70768\"}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410559714, 'spacePHID': None, 'dateCreated': 1410526980, 'dateModified': 1443277999, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70770', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The language dialog will not close if you paste in content with an auto direction and no language', 'description': {'raw': 'I haven\\'t tried to reproduce this.  \\n\\nI copied a page title from Meta and pasted it into VisualEditor on another wiki.  The text was set to =Page title= and highlighted in very pale blue, with a dashed line underneath, so I set it to Paragraph (that worked) and went to the character formatting menu to clear the formatting.  The \\'Language\\' item was highlighted, so I chose that.\\n\\nThe first time, the dialog box that popped up was tiny.  It was barely big enough to display the \"done\" button, which was overlapping with an odd \"$1 AUTO\" string in gray text.\\n\\nThe second time, the dialog box looked normal, but \\'Remove\\' didn\\'t actually remove anything.  \\'Clear formatting\\' also doesn\\'t remove anything.  \\n\\nThen the box got stuck open.  It would go away if I highlighted text, but \\'Done\\' didn\\'t close it and clicking outside it didn\\'t close it.\\n\\nI was able to keep editing and to save the page when I was finished, but it produced <span dir=\"auto\"> tags, which I didn\\'t want.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410558311, 'spacePHID': None, 'dateCreated': 1410461100, 'dateModified': 1443278001, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70731', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression wmf20] The link target suggestion drop down is appearing cut off to a very small size upon first time opening the link inspector', 'description': {'raw': 'link inspector\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Open a link inspector for any link\\n3.Tap on the text box to bring up the link target suggestions\\n\\nObserved Result:\\nLink target suggestion drop down are appearing cut off to a small size.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14991}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411596190, 'spacePHID': None, 'dateCreated': 1410379500, 'dateModified': 1443278001, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70683', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ”Use an Existing Reference“ button should be inactive if there are no references to add (the internal list is empty)', 'description': {'raw': 'screenshot1\\n\\nEnvironment-test2,beta, production.\\n\\n1> open a page in VE, add a Basic citation.\\n2>Click to add Basic citation again ,in the modal click on “Use an Existing Reference “.Select the citation that you just added.\\n3>In the editor pane, delete all the citations.\\n4> Select  to add Basic citation again. In the modal notice the “Use an Existing Reference “ button is  still active, although there are no citations to add to. Click on it and it opens a blank Reference modal.\\nSee screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14787}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410307712, 'spacePHID': None, 'dateCreated': 1410278760, 'dateModified': 1443278002, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70611', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] In Safari, Cannot enter any input in any dialog and VE gets unresponsive after trying to do that', 'description': {'raw': 'In Safari, Go to Insert>Media, try to enter something in the search box.\\nyou will get the following error in the console and wont be able to place your cursor in to the search box:\\n\\n\\napi.php:1TypeError: \\'undefined\\' is not a function (evaluating \\'jQuery111102360369882080704_1410208128038({\"warnings\":{\"main\":{\"*\":\"Unrecognized parameter: \\'uselang\\'\"}},\"query\":{\"searchinfo\":{\"totalhits\":0}}})\\')\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410809606, 'spacePHID': None, 'dateCreated': 1410208200, 'dateModified': 1443278005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70578', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf20] Edit notice displays at half-width', 'description': {'raw': 'Screenshot\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/w/index.php?title=Help:Extension:GlobalCssJs&veaction=edit\\n\\n**Attached**: {F14684}'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410542503, 'spacePHID': None, 'dateCreated': 1410197220, 'dateModified': 1443278007, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70565', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '404 errors for CSS and HTML from Bits in zh-yue wikipedia', 'description': {'raw': '**Author:** `yaukasin`\\n\\n**Description:**\\nzh-yue wikipedia does not load the stylesheets properly. When I view the source HTML code, I discover that there are many garbage stylesheets which would return error 404.\\n\\nBelow is the code after the line <link rel=\"canonical\" href=\"......\"> in zh-yue wikipedia \\n\\n=============================================================\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.gadget.internalLinkHelper-altcolor&amp;only=styles&amp;skin=vector&amp;*\" />\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.uls.nojs&amp;only=styles&amp;skin=vector&amp;*\" />\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.visualEditor.viewPageTarget.noscript&amp;only=styles&amp;skin=vector&amp;*\" />\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=ext.wikihiero&amp;only=styles&amp;skin=vector&amp;*\" />\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.legacy.commonPrint&amp;only=styles&amp;skin=vector&amp;*\" />\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.legacy.shared&amp;only=styles&amp;skin=vector&amp;*\" />\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.skinning.interface&amp;only=styles&amp;skin=vector&amp;*\" />\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=mediawiki.ui.button&amp;only=styles&amp;skin=vector&amp;*\" />\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=skins.vector.styles&amp;only=styles&amp;skin=vector&amp;*\" />\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/zh-yue.wikipedia.org/load.php?debug=true&amp;lang=yue&amp;modules=wikibase.client.init&amp;only=styles&amp;skin=vector&amp;*\" />\\n=============================================================\\n\\n\\nBelow is the code after the line <link rel=\"canonical\" href=\"......\"> in en wikipedia for comparison \\n\\n=============================================================\\n<link rel=\"stylesheet\" href=\"//bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&amp;lang=en&amp;modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cfeatured-articles-links%2CrefToolbar%2Cteahouse%7Cext.rtlcite%2Cwikihiero%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.vector.styles%7Cwikibase.client.init&amp;only=styles&amp;skin=vector&amp;*\" />\\n=============================================================\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410199718, 'spacePHID': None, 'dateCreated': 1410180900, 'dateModified': 1410204055, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70557', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf21] Adding a text as an image caption duplicates the text in the field with a following pawn', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Image\\n3.Try to type in a caption\\n\\nObserved Result:\\n\\n\\nThe text gets copied again in the text line and a pawn follows it.Also if you try to edit the caption of an existing image in a page , it is almost impossible to type in.\\n\\nEnviornment:Betalabs\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15068}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409961017, 'spacePHID': None, 'dateCreated': 1409943240, 'dateModified': 1443278010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70450', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression wmf20] Toolbar in mobile got squished in Betalabs and test2 both in desktop and iOS Safari', 'description': {'raw': 'Screenshot\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15012}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410374292, 'spacePHID': None, 'dateCreated': 1409878200, 'dateModified': 1443278010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70430', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Deleting from an empty paragraph to the end of an inline node throws an exception', 'description': {'raw': 'See https://en.wikipedia.org/wiki/File:VisualEditorTableCopyBugScreenshot.jpg for what the editor selected.  See https://en.wikipedia.org/wiki/File:VisualEditorTableCopyBugScreenshot2.jpg (top) for what he got when he pasted it into the new place.\\n\\nThis was found on Chrome and Windows 7.\\n\\nAlso, if he used Ctrl-X to cut the table, he was unable to save his changes.  Clicking on the Save button did nothing after that point.  Ctrl-C to copy the table did not disable the Save button.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426180583, 'spacePHID': None, 'dateCreated': 1409791740, 'dateModified': 1469823941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70375', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf20] Link target names are not appearing pressing command+K just applying the link text as link target straight off', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Select a text\\n3.Press commann+K\\n\\n\\nObserved Result:\\nLink inspector flickers and applies the link text as link target without showing any link target names.\\n\\nEnvironment:Betalabs\\nBrowser:Chrome\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409789096, 'spacePHID': None, 'dateCreated': 1409766540, 'dateModified': 1443278011, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70356', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"[l10n] LocalisationUpdate doesn't seem to run for VisualEditor\", 'description': {'raw': \"The message https://translatewiki.net/wiki/MediaWiki:Visualeditor-dialog-action-insert/he was translated on August 21, but still doesn't appear in the Hebrew Wikipedia: https://he.wikipedia.org/wiki/MediaWiki:Visualeditor-dialog-action-insert .\\n\\nIRC:\\nJames_F\\taharoni: Yeah, I've been looking at this.\\nJames_F\\taharoni: It looks like the i18n job for VE-core hasn't run for a while.\\nJames_F\\taharoni: I fixed it in If68193e7c3c78beeeb47975dc63ebaaec21448f3 and it worked… maybe that didn't stick?\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411540312, 'spacePHID': None, 'dateCreated': 1409598060, 'dateModified': 1420738693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70267', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Attempting to set an invalid range on undo', 'description': {'raw': \"1. Open a page with some content (a few paragraphs)\\n2. Select all and delete\\n3. Insert a math node\\n4. Press undo\\n\\nYou'll get an exception as selectionBefore in the undo stack is still the range of the whole original document, but your document should be empty.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409337366, 'spacePHID': None, 'dateCreated': 1409318940, 'dateModified': 1443278013, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70175', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf19] Cannot open Math inspector on a slug – TypeError: Cannot read property 'length' of null appears in the console\", 'description': {'raw': \"Screenshot\\n\\nthe following error is appearing in the console while trying to open Math inspector:\\n\\nUncaught TypeError: Cannot read property 'length' of null\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14629}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409071611, 'spacePHID': None, 'dateCreated': 1408999440, 'dateModified': 1443278021, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69991', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf19] Getting stuck in the Media Settings dialog after changing the image position as it is throwing TypeError: Cannot read property 'length' of null\", 'description': {'raw': \"Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Media and insert an image\\n3.Reopen the media settings dialog and change the image position to left/centre\\n\\nObserved Result:\\nThe following error appears in the con sole:\\nUncaught TypeError: Cannot read property 'length' of null \\n\\nUser gets stuck inside Media Settings dialog as it none of the button is working to escape from it.\\n\\n\\nEnvironment:Betalabs\\nBrowser:Chrome\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409010897, 'spacePHID': None, 'dateCreated': 1408997580, 'dateModified': 1443278021, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69988', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Populate LinkCache from MWLinkTargetInputWidget etc', 'description': {'raw': \"In MWLinkTargetInputWidget and other places, we perform API requests that give us exactly the kind of information (existence, redirect status, etc.) that goes into ve.init.mw.LinkCache, but we don't write it to the link cache. We should do that, so we can save ourselves some API requests.\\n\\nRight now, when you make a link, we do another API request to check if the link should be blue or red, even if the link target came from a suggestion list and we already know it should be blue.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410935207, 'spacePHID': None, 'dateCreated': 1408688640, 'dateModified': 1443278024, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69886', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Return of the whitespace bunny-hopping bug', 'description': {'raw': 'This mess:\\n\\n[[Help:Installing Japanese character sets|<span class=\"t_nihongo_icon\" style=\"color: #00e; font: bold 80% sans-serif; text-decoration: none; padding: 0 .1em;\">?</span>]]) [[Category:Articles containing Japanese-language text]]\\n\\nwas added in https://en.wikipedia.org/w/index.php?curid=31216768&diff=621842944&oldid=600210359\\n\\nto produce this:\\n\\n;Track & road events<ref name=\"JAAF20120611\">[http://www.jaaf.or.jp/fan/news/2012/20120611.html {{Nihongo||ロンドンオリンピック トラック・フィールド種目・競歩種目の日本代表選手|The Japanese national team of Track & Field and Race Walk at the 2012 Olympic Games}}][[Help:Installing Japanese character sets|<span class=\"t_nihongo_icon\" style=\"color: #00e; font: bold 80% sans-serif; text-decoration: none; padding: 0 .1em;\">?</span>]]) [[Category:Articles containing Japanese-language text]]{{ja icon}}. Japan Association of Athletics Federations (2012-06-11). Retrieved 19 June 2012.</ref>\\n\\nThe editor says s/he didn\\'t edit this line.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=69876'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409164517, 'spacePHID': None, 'dateCreated': 1408640880, 'dateModified': 1443278026, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69861', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Regression: Nested citations broken', 'description': {'raw': 'From https://bugzilla.wikimedia.org/show_bug.cgi?id=50749#c2\\n\\nLook at [[Otto I]].  It has 63 references, including ref #18 (\"Thompson\") from explanatory footnote [d].  This ref doesn\\'t appear in VisualEditor.\\n\\nhttp://en.wikipedia.org/wiki/Otto_I%2C_Holy_Roman_Emperor?oldid=621934593\\nhttp://parsoid.wmflabs.org/enwiki/Otto_I%2C_Holy_Roman_Emperor?oldid=621934593\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408997647, 'spacePHID': None, 'dateCreated': 1408586580, 'dateModified': 1408997647, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69827', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'BetaFeatures: wgBetaFeaturesFeatures is incomplete, causing wrong UI in preferences', 'description': {'raw': \"I'm not sure why, but wgBetaFeaturesFeatures is incomplete on my local MediaWiki-Vagrant install.\\n\\nIn the actual preferences UI, I see the following BetaFeatures:\\n\\n* Hovercards\\n* Compact personal bar\\n* Fixed header\\n* VisualEditor\\n* VisualEditor language tool\\n\\nBut wgBetaFeaturesFeatures is only:\\n\\n{ popups: null, visualeditor-enable-language: null }\\n\\nThat in turn means that these are the only ones looped over in betafeatures.js, which means other features don't have the JavaScript/browser blacklist processing.\\n\\nThis bug affects production as well.\\n\\nSide note, you can use:\\n\\n.client-js .mw-ui-feature-requirements-javascript {\\n  display: none;\\n}\\n\\nfor a simpler way to do the JS-hiding, but that doesn't address the underlying problem.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70371\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411237957, 'spacePHID': None, 'dateCreated': 1408581780, 'dateModified': 1411246176, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69823', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: White pawn \"♙\" appears on Alt+Shift+F in Firefox', 'description': {'raw': 'Alt+Shift+F is shortcut for search box (very useful to validate a name of article...)\\n\\nPressing Alt+Shift+F when the cursor is in the begining of article or in the dummy paragraph (slug) will cause a white pawn ♙ to appear. \\n\\n(appears in https://he.wikipedia.org/wiki/%D7%90%D7%99%D7%9C%D7%9F_%D7%9E%D7%9C%D7%9B%D7%90?veaction=edit)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-cfsvvgbtlqnbt2yokfjf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421282422, 'spacePHID': None, 'dateCreated': 1408566780, 'dateModified': 1438735473, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69810', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [iOS] abandoning edit takes me to unscrollable page', 'description': {'raw': \"Observed on iPad. Steps to repro:\\n\\n1. Go into VE edit mode on an article and enter the link inspector\\n2. Use browser back to exit the link inspector\\n\\nExpected: you get a message asking if you want to abandon changes and get taken back to the content if you say yes\\n\\nActual: no message about abandoning changes, and you're taken to the top of the page but can't scroll below the fold\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-yu5wnmvkjecufsjgh2fa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409163492, 'spacePHID': None, 'dateCreated': 1408143420, 'dateModified': 1443278030, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69630', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting into nodes with whitespace inserts ☀', 'description': {'raw': 'I copied part of a header from one page on se.wikimedia and pasted in an already started header on another page. After my paste the symbol ☀ was added:\\n\\nhttps://se.wikimedia.org/w/index.php?title=Projekt%3AWikidata_2014%2FAns%C3%B6kan_till_Vinnova&diff=34844&oldid=34843\\n\\n(Page I copied from: https://se.wikimedia.org/wiki/Projekt:Offentligkonst.se_2014/Ans%C3%B6kan_till_Vinnova )\\n\\nI used Google Chrome Version 35.0.1916.153 on Ubuntu 14.04.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408310129, 'spacePHID': None, 'dateCreated': 1408095180, 'dateModified': 1443278030, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69595', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking on a block format control when edit comment dialog is open throws \"Uncaught TypeError:Cannot Read Property \\'getSurface of null\\'\".', 'description': {'raw': 'screenshot\\n\\nenvironment- test2, production, beta\\n\\n1> open page in VE, insert a comment.\\n2> Open to edit the comment.\\n3>Now click on the Text Style Menu and select  any style, for ex-Page Title or the Heading style.\\n4> Notice the edit comment dialog turns blank.Please see screenshot.\\n\\nsame behavior found in FF.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F14201}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418323355, 'spacePHID': None, 'dateCreated': 1407444600, 'dateModified': 1438735479, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69262', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit conflict message provides no button to actually resolve the conflict', 'description': {'raw': '.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409102797, 'spacePHID': None, 'dateCreated': 1407261180, 'dateModified': 1443278040, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69150', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData:  If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags', 'description': {'raw': 'If TemplateData is added to a template page (not a /doc subpage), then it needs to be wrapped in <noinclude> tags.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**See also**\\n* {T52512}\\n* {T56140}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412898636, 'spacePHID': None, 'dateCreated': 1407256980, 'dateModified': 1431520672, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69149', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf16] Opening link inspector/comment box in an empty line, opens them at the end of the previous line', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Go to the end of a line\\n3.Press return to go the next line and click on link inspector or comment icon from the toolbar\\n\\nObserved Result:\\nThe link inspector and the comment box opens at the end of the previous line\\nAfter adding a link or a comment it appears on the next line though.\\n\\n\\nSee the screenshot attached\\n\\nEnvironment:Betalabs and test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14434}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413931552, 'spacePHID': None, 'dateCreated': 1407184260, 'dateModified': 1443278040, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69122', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In Betalabs,Media search is extremely slow, some images are not appearing and the progress bar keeps on moving infinitely', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open any page with VE\\n2.Go to Insert>Media\\n\\nObserve that ,the progress bar is active on the text field and never stops\\nIf you retype the search string, the search results comes up but very slowly, some of the images are not even loading completely inside the dialog box.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14212}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420843166, 'spacePHID': None, 'dateCreated': 1406919000, 'dateModified': 1438735936, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69018', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf16] Comment box is not opening in Firefox , throwing error:TypeError: ve.ui.WhitespaceTextInputWidget is not a constructor', 'description': {'raw': 'Happening on Betalabs and test2\\n\\nCannot open the new comment box\\n\\nGetting following error in the console:\\nTypeError: ve.ui.WhitespaceTextInputWidget is not a constructor\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406854389, 'spacePHID': None, 'dateCreated': 1406849160, 'dateModified': 1443278040, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68960', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector sets wrong title when clicking suggestion', 'description': {'raw': 'On enwiki:\\n\\n* Inspect an existing link\\n* Type \"N\" in the text box\\n* Click \"North America\" in the suggestions list\\n* Click Done\\n* Observe that the link now points to \"North American B-25 Mitchell\"\\n\\nWhat seems to happen is:\\n* you click North America\\n* the textbox is changed to North America\\n* a new suggestions list opens, with \"North America\" as the second item and \"North American B-25 Mitchell\" as the first\\n* this closes again, setting the annotation to NAB25M while keeping the text as NA\\n* when you click Done, the annotation is what\\'s saved, not the text\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1433344320, 'spacePHID': None, 'dateCreated': 1406829240, 'dateModified': 1433344320, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68934', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Triggering context on link after defocus throws \"TypeError: Cannot read property \\'isCollapsed\\' of null\"', 'description': {'raw': '1. Click on a link to show the context menu.\\n2. Right click on the description of the link in the context menu (eg. name of page the link points to).\\n3. Choose \"Inspect element\" which will defocus the page.\\n4. Click on the link again, thus putting the cursor back in the page; somewhere in the linked word.\\n\\nAfter the context menu re-appears, a callback from AnnotagionInspector run via a OO.ui.Process throws:\\n\\nUncaught TypeError: Cannot read property \\'isCollapsed\\' of null \\n> ve.ui.AnnotationInspector.prototype.getSetupProcess = function () {\\n>   ..\\n>   .. fragment.getRange().isCollapsed()\\n (anonymous function) ve.ui.AnnotationInspector.js:159\\n (anonymous function) oojs-ui.js:3030\\n (anonymous function)\\n jQuery.extend.Deferred\\n promise.then\\n OO.ui.Process.execute oojs-ui.js:3067\\n OO.ui.Window.setup oojs-ui.js:1902\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411594541, 'spacePHID': None, 'dateCreated': 1406807880, 'dateModified': 1417571331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68915', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: State of \\'Save\\' button stops being updated after opening and cancelling the \"Options\" dialog', 'description': {'raw': 'Shows that redirect page Save page (=Uložit stránku) is gray\\n\\nIn this case, I am adding a template to the redirect page (delete template), but I cannot safe it. The safe button stay gray (attachment).\\n\\nSteps to reproduce this bug (Windows Vista, FF 31.0):\\n1) open https://cs.wikipedia.org/w/index.php?title=Cristina_Fern%C3%A1ndez_de_Kirchner&redirect=no\\n2) click on Edit\\n3) Cencel options\\n4) Insert > Template > Smazat (Add more information: 1; randoom text) > Insert template\\n5) Save page = but you cannot!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14552}'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406814424, 'spacePHID': None, 'dateCreated': 1406789640, 'dateModified': 1443278043, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68901', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make VisualEditor transaction processing exception-safe', 'description': {'raw': 'If an exception occurs while processing a transaction, we should roll it back safely, so the converter will still work and the user can still save or bail to source mode.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426005750, 'spacePHID': None, 'dateCreated': 1406768880, 'dateModified': 1426018177, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68892', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: MWReferenceSearchWidget should only build the index if there isn't one or if it was built against a different version of the internal list\", 'description': {'raw': \"Right now we build it blindly every time, which is inefficient. Can we listen to the internal list or get its hash or something so that we don't have to re-build except if a reference is added, removed or altered?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408587014, 'spacePHID': None, 'dateCreated': 1406766720, 'dateModified': 1443278043, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68890', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf15] Re-use existing citation dialog never rebuilds list of references after first opening', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a reference (Basic/Citation)\\n3.Check Re-use existing reference dialog (The reference appears in the dialog though the reference name is missing which is a different bug:https://bugzilla.wikimedia.org/show_bug.cgi?id=67342)\\n4.Now add some citation/basic references \\n5.Check re-use existing reference dialog again\\n\\nObserved Result:\\nExcept the first one , none of the newly added references are appearing in the use existing dialog\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67342\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68582'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406767098, 'spacePHID': None, 'dateCreated': 1406743800, 'dateModified': 1443278046, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68869', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression pre-wmf16] Cannot scroll up/down a page in mobile when the keyboard is open and cursor active on CE', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Place the cursor somewhere at the top of the page\\n3.When the cursor is active on Ce and the keyboard is open, try scrolling down the page\\n\\nObserve dResult:\\nScrolling does not work\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409163669, 'spacePHID': None, 'dateCreated': 1406678220, 'dateModified': 1443278046, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68828', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Incorrect use of Russian translation on Ukrainian wiki when Ukrainian translation available (incorrect fallback merging?)', 'description': {'raw': 'This is an apparent separate bug discovered in the course of bug 67805.\\n\\nNiklas suggested, \"LC issue is possibly caused by incorrect fallback merging, because L10nupdate contains update for ru, but not for uk (because the translation is already up to date for uk):\"\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67805\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70686'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409854129, 'spacePHID': None, 'dateCreated': 1406604120, 'dateModified': 1602870076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68781', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Snowman character gets triggered, when trying to insert a template with Comment edit dialog open.', 'description': {'raw': 'screenshot\\n\\nEnvironment- test2\\n\\nSteps-\\n1>1> Open a blank page in VE and type in some text.\\n2>At the end of the text insert a comment.\\n3>Click on the Comment , to open the comment edit dialog.\\n4> Now while the cursor is still in the comment edit dialog , click to insert a Template.\\n5> As you start typing, add any template from the list that shows likely matches. For Example -select the “Bar” template.\\n6>Type in Field name and insert the template.\\n7>Notice the template does get added and then a snowman like character gets triggered after it.\\n\\nBehavior found in Chrome,FF and Safari.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14172}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406660968, 'spacePHID': None, 'dateCreated': 1406561340, 'dateModified': 1443278048, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68740', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Character duplication in paragraphs following the {{lang-it}} template (and others?)', 'description': {'raw': 'If a paragraph contains a template, and VisualEditor is used to insert two characters somewhere after the template, and the second character is deleted with backspace, then the first character will be replaced by another character that is duplicated from several positions before that character.\\n\\nTo reproduce, go to \\n\\nhttps://en.wikipedia.org/w/index.php?title=User:AxelBoldt/Sandbox&oldid=618813650&veaction=edit\\n\\nand change the word \"Italian\" in the first sentence to \"Itaxxlian\", then delete the second x. Result: \"Itatlian\", where the second \"t\" results from duplication of the first \"t\". \\n\\nThis is a consequence of the IPA template earlier in the paragraph. The test file also contains a paragraph without template, where the bug does not occur, and a paragraph with a convert template, where the bug does occur.\\n\\nWikipedia is at MW 1.24wmf15 and I\\'m on Windows 7 running Chrome 36.0.1985.125 m.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406660962, 'spacePHID': None, 'dateCreated': 1406552880, 'dateModified': 1443278051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68733', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove media or templates, page loses focus', 'description': {'raw': 'Take any article long enough to notice the effect (i.e. Cake on en.wp).\\nDelete any of the pics at the bottom of the article.\\nNotice the focus jumps back at the top.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58038\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68589'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407065098, 'spacePHID': None, 'dateCreated': 1406531520, 'dateModified': 1443278051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68708', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Weird behavior around a wikilink', 'description': {'raw': '1) VEdit https://fr.wikipedia.org/wiki/Marie_Coutant?veaction=edit .\\n\\n2) Reach the end of the second paragraph, find the word Métivier.\\n\\n3) Start typing right before the \"M\" or after the \"r\". Pawns appear and random letters can appear in the word. Click on the word again, and watch letters and pawns multiply.\\n\\n4) Abandon the edit, go back to step 1 and 2.\\n\\n5) Add an \"h\" after the \"t\": Méthivier.\\n\\n6) Enter the link tool and click Supprimer to suppress the link.\\n\\n7) Notice the \"h\" has become an \"é\": Météivier. This is just an example, you can get different results adding other letters.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406754678, 'spacePHID': None, 'dateCreated': 1406451840, 'dateModified': 1443278055, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68666', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing at the beginning of the document pulls annotations from the right; should instead be null', 'description': {'raw': \"1. Create a document with two paragraphs, and make both of them entirely bold\\n2. Put the cursor at the beginning of the first paragraph, and type a character. This character will be bold\\n3. Put the cursor at the beginning of the second paragraph, and type a character. This character will not be bold\\n\\n#2 and #3 should be consistent. In fact, #2 *only* happens at the very start of the document, #3 happens everywhere else.\\n\\nThe reason this is broken is that the code computing the new insertionAnnotations in ve.dm.Surface#setSelection by pulling from the left does not take paragraph boundaries into account at all. In case #3, it tries to pull from the left across the paragraph boundary, but because getAnnotationsFromOffset() doesn't work the way it thinks it does (the offset at the end of the first paragraph is a content offset, but getting its annotations returns an empty set) that doesn't work, and so text inserted at the beginning of this paragraph is not annotated. However, at the very start, the getRelativeContentOffset() call that computes the offset to the left bounces back and returns the offset to the right instead (1), so left === right, and we end up pulling from the right and bolding the inserted text.\\n\\nSo really, the code is trying to achieve the wrong behavior (#2), but in most cases that breaks and we end up with the right behavior (#3). So the correct behavior is achieved completely by accident, except in one edge case where the code successfully achieves the wrong behavior.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408557223, 'spacePHID': None, 'dateCreated': 1406337660, 'dateModified': 1443278055, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68597', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Putting cursor after reference list throws \"offset was inside a handlesOwnChildren node\" error', 'description': {'raw': 'Steps:\\n\\n1. Open http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit\\n2. Scroll to bottom\\n3. Place cursor in slug between gallery and references list\\n4. Cursor right twice\\n\\nExpected outcome: Cursor ends up in slug at end of the page after the references list\\n\\nActual outcome: Error thrown: \"offset was inside a handlesOwnChildren node\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408557238, 'spacePHID': None, 'dateCreated': 1406321880, 'dateModified': 1443278056, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68588', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: VE gets stuck when applying changes to settings window the second time it's open\", 'description': {'raw': 'VE get stucks when saving settings\\n\\nHow to reproduce:\\n1) click \"Options\" and then \"cancel\"\\n2) click \"Advanced settings\" and then \"apply changes\"\\n\\nAfter this it gets stuck. It\\'s \"applying changes\" even if you didn\\'t do any changes. You must reload the page to make your changes again.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-6majuboi566q3ozbh27r', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406307422, 'spacePHID': None, 'dateCreated': 1406298300, 'dateModified': 1443278059, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68573', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn gets added beside the comment, when inserting a whitespace after it.', 'description': {'raw': 'screenshot\\n\\nTest Environment-test2 and betalabs\\nSteps-\\n1> open a blank page in VE.\\n2>type some text and at the end of the last character (could be a space after the text or the last character in the text itself) insert a comment.\\n3>Now click to move the cursor after the comment, this closes the comment dialog too.\\n4> Insert a whitespace.I cannot see the cursor at this point.\\n5> click on the page again and the cursor appears before the start of the line. \\n6>Hit the spacebar and then press backspace key. A pawn appears next to the comment. Please see screenshot_chrome.\\n\\nIn Safari-\\nTry the same steps and at step#6 I get the WebKit2WebProcess.exe  dialog saying “WebKit2WebProcess.exe has encountered a problem and needs to close.”. After I click to send the error report and I get logged out of my account. \\n\\nIn FF 31- no issues were found when whitespace was inserted after a comment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14311}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406653811, 'spacePHID': None, 'dateCreated': 1406242920, 'dateModified': 1443278059, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68539', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf14] Each category is getting added twice in Betalabs, throws TypeError: categoryItem is undefined', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Page Settings option>Categories\\n3.Try to add categories \\n\\nObserved Result:\\nAfter typing into a category name, it getting added twice and trying again throws error:\\n\\nTypeError: categoryItem is undefined \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14192}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407349730, 'spacePHID': None, 'dateCreated': 1406155680, 'dateModified': 1443278063, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68484', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Upgrade gerrit to 2.12', 'description': {'raw': 'Please upgrade gerrit to 2.12.\\n\\nFollowing plugins needs to be tested and fixed in the new version (and blocks an upgrade):\\n\\n```\\nits-phabricator\\t2.8.1\\tEnabled\\nits-phabricator-from-bugzilla\\t2.8.1\\tEnabled\\ngithub-create-1.0-rc0\\t1.0-rc0\\tEnabled\\ndeleteproject\\t2.8.1\\tEnabled\\n```\\n\\nRelease notes for 2.12 are at https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.12.html\\n\\n--------------------------\\nSee Also: T65847'}, 'authorPHID': 'PHID-USER-bxp7xrbobtrp5o3q3swv', 'ownerPHID': 'PHID-USER-oetk6bbl6omm354ejz3b', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-oetk6bbl6omm354ejz3b', 'dateClosed': 1469428392, 'spacePHID': None, 'dateCreated': 1405777980, 'dateModified': 1469586342, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68271', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Unknown error\" on saving on officewiki', 'description': {'raw': 'We get \"Unknown error\" (not internationalised) when saving on officewiki.\\n\\nThis is because the response object given to ve.init.mw.Target.onSave is actually a jqXhr(?) object here for some reason, which has an error function. The data we actually want is in the responseJSON property of this, and we can also get it via .done( ... ).\\n\\nThis stuff comes through tryWithPreparedCacheKey and the way it fits together with everything else wasn\\'t very clear here (lots of chaining deferreds etc.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407034283, 'spacePHID': None, 'dateCreated': 1405716000, 'dateModified': 1443278068, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68235', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf14] Link inspector is not opening up in FF in first attempt, upon trying second time it throws error \"TypeError: manager.opening is null\" and appears with broken UI', 'description': {'raw': 'Screenshot\\n\\n1.Open a page with VE in FF\\n2.Click on Link inspector icon \\n3.The inspector does not open up\\n4.Now again click on the link tool on the toolbar\\n\\nObserved Result:\\nThe link inspector opens up with distorted UI and the following error appears in the console\\n\\nTypeError: manager.opening is null\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14196}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406161145, 'spacePHID': None, 'dateCreated': 1405707060, 'dateModified': 1443278072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68223', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf14] Langage and Special Character inspectors' UI is broken, and dialog titles are not correctly aligned\", 'description': {'raw': 'Screenshot\\n\\nOpen language inspector in betalabs and observe the brokenness\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14642}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405624867, 'spacePHID': None, 'dateCreated': 1405620240, 'dateModified': 1443278074, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68180', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: PopupToolGroup item not 'ticked' after changing\", 'description': {'raw': '1. Place the cursor in a paragraph and change it to a heading the the popup tool\\n2. Open the popup tool again and observe that nothing is selected (with a tick)\\n3. Change the context (click in another paragraph/heading, then back)\\n4. Open the popup tool, the correct item is now selected\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406060277, 'spacePHID': None, 'dateCreated': 1405615500, 'dateModified': 1443278075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68170', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ☃ symbol replicates when creating an article with a template', 'description': {'raw': \"When I have created an article in the hebrew version of wikipedia, ☃ symbol replicated.\\n\\nThe operations I did:\\n1. I copied an tamplate from another article.\\n2. I edited it's fields by the visual editor.\\n3. I started to write text in bold.\\n4. I changed the text state to normal.\\n5. The symbol ☃ started to replicate.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68151\"}, 'authorPHID': 'PHID-USER-em3l7mquu7qcck24eqq5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406660949, 'spacePHID': None, 'dateCreated': 1405587840, 'dateModified': 1443278076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68147', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf14] Save button in save dialog remains active while save is in progress and throws \"Uncaught TypeError: Cannot read property \\'$saveOptions\\' of null\"', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Make an edit \\n3.Click on the \"Save Page\"\\n4.While the saving is in progress,keep on clicking on the \"Save Page\" button on the Save dialog\\n\\nObserved Result:\\nThe following error appears in the console:\\n\\nUncaught TypeError: Cannot read property \\'$saveOptions\\' of null\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14424}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406083201, 'spacePHID': None, 'dateCreated': 1405459560, 'dateModified': 1443278078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68073', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf14] Cannot close VE by clicking on Cancel after making an edit in Betalabs', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Make an edit to the page\\n3.Click on the \"Cancel\" button next to \"Save Page\"\\n\\nObserved Result:\\nNothing happens, the confirmation dialog box does not appear neither it lets user close VE\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405544698, 'spacePHID': None, 'dateCreated': 1405457520, 'dateModified': 1443278078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68068', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf14] Highlight/Context Menu/Inspector are appearing over the toolbar in Chrome', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Select a math node/ a reference/image /open any inspector\\n2.Scroll down the page\\n\\nObserved Result:\\nThe highlights, context menus and inspectors everything is appearing over the toolbar\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14413}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405554506, 'spacePHID': None, 'dateCreated': 1405455840, 'dateModified': 1443278079, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68066', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression pre-wmf14] All inspector UI in mobile got completely broken', 'description': {'raw': 'Screenshot\\n\\nThe Link inspector in mobile became completely broken and unusable after new windows refactor change\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14399}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405548737, 'spacePHID': None, 'dateCreated': 1405453020, 'dateModified': 1443278081, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68061', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Context menu for Math is still appearing in Mobile VE', 'description': {'raw': 'Tapping on a math node is still bringing up the context menu on top of the page,letting user to open math inspector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405552407, 'spacePHID': None, 'dateCreated': 1405378440, 'dateModified': 1417572025, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68010', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs UI: When the text in buttons in confirmation dialogs is too long, some of the buttons may overflow, breaking the dialog', 'description': {'raw': \"Example with cyrillic text where one button overflows.\\n\\nWhen the dialog to switch from VisualEditor to wikicode edition is shown, its dimensions are sufficient to show all the buttons when the interface text is in English. However, in fr, crh-Cyrl and possibly in other languages, the text on the buttons is longer, and the buttons can fall and flow over the edge of the dialog (overflow). This makes it impossible to read the text on them.\\n\\nThis issue is best described by the screenshot attached to this message, and by the subsequent screenshots.\\n\\nTo reproduce:\\n\\n- Browse to this URL: https://en.wikipedia.org/w/index.php?title=User:Rastus_Vernon/VisualEditor_Sandbox&veaction=edit&uselang=fr.\\n- Open the VisualEditor menu.\\n- Click “Passer à l'édition de code”.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14277}\"}, 'authorPHID': 'PHID-USER-2rwkb3az6uklfhh5aqw5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405375780, 'spacePHID': None, 'dateCreated': 1405374540, 'dateModified': 1427403750, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68005', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Easy way to trigger a snowman and other corruption at fr.wp', 'description': {'raw': 'Based on feedback and test by French Wikipedians, which we always thank.\\n\\nAn editor reported getting a snowman here https://fr.wikipedia.org/w/index.php?title=Lucien_Dayle&diff=next&oldid=105411841 when all he did was removing a comma (Chrome, Mac OS X).\\nI wasn\\'t able to reproduce https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AElitre_%28WMF%29%2FProve2&diff=105432197&oldid=105432184 .\\n\\nThen another user created a sandbox with similar templates in it and I tested there as well; https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AZebulon84%2FBrouillon&diff=105432505&oldid=105431985 the snowman showed up in the exact place where I had added a comma.\\n\\nIn another case instead https://fr.wikipedia.org/w/index.php?title=Utilisateur%3AZebulon84%2FBrouillon&diff=105432576&oldid=105432561 the letter \"e\" shows up where I had put the comma. The user had previously replaced the template {{e}} with <sup> tags (https://fr.wikipedia.org/w/index.php?title=Utilisateur:Zebulon84/Brouillon&diff=prev&oldid=105422272 ).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406660943, 'spacePHID': None, 'dateCreated': 1405353120, 'dateModified': 1443278085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67992', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Down-page of {{IPA-es}} backspace behaviour is very broken', 'description': {'raw': '**Author:** `and1eternal1`\\n\\n**Description:**\\nWhen typing, inserting templates, hitting \"backspace\", and possibly more actions, the cursor moves two characters left after every action. Obviously, this makes editing nearly impossible.\\n\\nConfirmed and repeatable on: https://en.wikipedia.org/wiki/Corcovado_Volcano?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405967290, 'spacePHID': None, 'dateCreated': 1405097400, 'dateModified': 1443278086, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67862', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Local versions of system messages are ignored', 'description': {'raw': 'Yesterday a user reported on the Italian Wikipedia that several Mediawiki messages which have a local version there are being ignored (I guess the system is showing the original message available at Translatewiki, but can\\'t check since that site is currently down). This doesn\\'t seem to be targeting one product only.\\n\\nExamples:\\nThe button to launch the new TemplateData editor says \"Gestisci documentazione template\" (you can check at the top left of https://it.wikipedia.org/w/index.php?title=Template:Cassetto/man&action=edit ). It should read \"Gestisci TemplateData\" instead, as per https://it.wikipedia.org/wiki/MediaWiki:Templatedata-editbutton .\\n\\nOr see Table 1 at https://it.wikipedia.org/wiki/Discussioni_utente:Rotpunkt#Messaggi_che_non_funzionano . The link says \"Comprimi\"/\"Espandi\", but the correct messages, linked a few lines above the table, should actually be \"Nascondi\"/\"Mostra\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68781'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406713731, 'spacePHID': None, 'dateCreated': 1405001760, 'dateModified': 1602870076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67805', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression wmf12] Cite menu is missing in the toolbar for mobile VE for in both alpha and beta modes', 'description': {'raw': \"I don't see the option to add Cite/References in Mobile Ve anymore in any mode .Is it switched off intentionally?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405550482, 'spacePHID': None, 'dateCreated': 1404862020, 'dateModified': 1443278090, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: add tooltip/quick link to TD help page near new TD editor button', 'description': {'raw': 'Inspired by comments at various wikis and at bug 63389:\\npretty much what the summary says.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63389'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413914069, 'spacePHID': None, 'dateCreated': 1404763440, 'dateModified': 1413914069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67621', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf13] \"Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds\" appears upon selecting language or closing the language selector', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the language inspector\\n3.Now Open the language selector dialog\\n4.Select any language or just close the dialog\\n\\nObserved Result:\\nThe following error appears in the console:\\nUncaught Error: ve.dm.Document.getNodeFromOffset(): offset 1 is out of bounds\\n\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405426136, 'spacePHID': None, 'dateCreated': 1404756540, 'dateModified': 1443278095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67609', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Snowmen appearing for some reason', 'description': {'raw': 'https://pt.wikipedia.org/w/index.php?diff=39208742\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404767562, 'spacePHID': None, 'dateCreated': 1404736800, 'dateModified': 1417572120, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67591', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing right in a slug a the end of a document takes you back to before the slug-causing node', 'description': {'raw': 'See at http://en.wikipedia.beta.wmflabs.org/wiki/0.37197036937123?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405445429, 'spacePHID': None, 'dateCreated': 1404562920, 'dateModified': 1658737383, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67551', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Hovercards: Use a link interpreter instead of title attribute', 'description': {'raw': \"Currently Hovercards just takes the title attribute and uses that value as the article that it wants to preview.\\n\\nThis does not handle many types of links, nor is not very reliable in combination with image links.\\n\\nHovering an image like: [[File:S can.gif|18px|link=Cancer (astrology)|Cancer]] Will show you the article 'Cancer' instead of 'Cancer (astrology)' for instance, because inline images set their link title attribute to the caption.\\n\\n\\nA link interpreter is also much more flexible and would be able to identify, different types of links.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-a6qfpo5lwzvt6nddu2zv', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gc5hdyw5p4np7atqjynz', 'dateClosed': 1444923799, 'spacePHID': None, 'dateCreated': 1404379320, 'dateModified': 1449273693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67466', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Disable \"Apply changes\" button on Media Search dialog now that the Edit and search dialog both are merged', 'description': {'raw': 'Screenshot\\n\\n1.Open a page with VE\\n2.Select an image\\n3.Click on the \"Change Image\" button\\n4.It will take you back to the Media Search dialog box\\n\\n\\nObserved Result:\\nObserve that,the \"Apply Changes\" button is enabled on the search dialog box\\nClicking on that will not have any effect.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14223}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404350107, 'spacePHID': None, 'dateCreated': 1404346260, 'dateModified': 1443278098, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67443', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf12] Link Suggestions are now not appearing for Desktop VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Type a text\\n3.Select the text\\n4.Open the link inspector to apply link on it\\n5.Type something inside the link inspector\\n\\nObserved Result:\\nNo link suggestions are appearing in the link inspector.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14198}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411066338, 'spacePHID': None, 'dateCreated': 1404334680, 'dateModified': 1443278098, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67437', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: references context selection is wonky', 'description': {'raw': \"It's pretty much impossible to open the references context toolbar to edit an existing reference.\\n\\nSteps to reproduce:\\n\\n1. Open an article in VE editing mode on an iPad\\n2. Tap on any reference footnote in the body of the article – sometimes the reference context toolbar appears, sometimes it doesn't, and sometimes it appears for a second and scrolls away.\\n3. If you've managed to get the reference context toolbar to appear, tap it – sometimes it takes you to the link inspector, and sometimes it takes you to a new blank citation form\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67390\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67637\"}, 'authorPHID': 'PHID-USER-yu5wnmvkjecufsjgh2fa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406747326, 'spacePHID': None, 'dateCreated': 1404329700, 'dateModified': 1443278099, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67433', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Problems typing after cursoring off an inline focusable nodes in Firefox', 'description': {'raw': 'Copied from my Russian Wikipedia talk page:\\n\\nAfter reference VE added symbol \"♙\".\\n\\nsample for https://ru.wikipedia.org/w/index.php?title=Гёрлфренд&oldid=58928673&veaction=edit\\n\\nfind ref№3 -> \"к подруге.[3]\"\\nclick after the dot -> \"к подруге.|[3]\"\\ndelete the dot with backspace  back  ->\"к подруге|[3]\"\\npress en:Arrow keys  →  two times ->\"к подруге[3]|\"\\npress key dot  .  ->\\nexpected that will be shown the symbol \".\" -> \"к подруге[3].|\"\\nbut it shows the symbol \"♙\" ->\"к подруге[3]♙|\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405383746, 'spacePHID': None, 'dateCreated': 1404328260, 'dateModified': 1443278099, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67432', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf12] The icons for tabs and headings inside Media Settings dialog are missing in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Media and select any image after searching\\n\\nObserved Result:\\nWhen the Media settings dialog pop-up, observe that all the icons for the tabs General Settings, Advanced Settings and the headings Caption,Alternative text, Position,Image Type, Image Size etc are missing\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14179}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404351812, 'spacePHID': None, 'dateCreated': 1404325620, 'dateModified': 1443278101, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: In iOS Safari, the semi-highlight is still happening on selection of a node when there is no text cursor activation upon opening a page on Mobile VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Do not place your cursor anywhere on CE but try to select a node \\nObserved Result:\\nThe semi-highlight of lighter shade appears over the node and tapping on it for the second time selects it with darker highlight.\\n\\nIt might get resolved with :https://bugzilla.wikimedia.org/show_bug.cgi?id=57177\\n\\nStill I am filing it as a separate issue.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57177\\n\\n**Attached**: {F14690}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404780385, 'spacePHID': None, 'dateCreated': 1404249300, 'dateModified': 1443278102, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67389', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: In iOS Safari, after adding a link, the cursor still blinks on CE in the position where it was appearing inside the search box for link inspector', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE in iOS Safari\\n2.Select a text\\n3.Click on the link icon from the toolbar\\n4.Type a link target page inside link inspector and apply it\\n\\nObserved Result:\\nThe cursor that was appearing inside the search box of a link inspector remains on the screen appearing over the title of the page\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14689}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405558544, 'spacePHID': None, 'dateCreated': 1404245460, 'dateModified': 1443278102, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67388', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: For all templates , \"Template:\" is getting added as a prefix while searching from Template dialog box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Template\\n3.Type a template name such as \"Cite Web\"\\n\\nObserved Result:\\nIn the template suggestion drop dwon box all template names are appearing with a prefix \"Template:\"\\n\\nSee the screenshot attached\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14680}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404350668, 'spacePHID': None, 'dateCreated': 1404242520, 'dateModified': 1443278105, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67384', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawning prevention code in ve.ce.Surface sometimes prevents some legit keypresses from being handled (e.g. typing “ą” in Polish on a new line)', 'description': {'raw': 'Writing https://gerrit.wikimedia.org/r/143322 , I realized that the `ve.ce.isShortcutKey( e )` check in ve.ce.Surface (which rejects every keypress event where Ctrl or Cmd is pressed) sometimes prevent legit keypresses from being handled.\\n\\nTo reproduce (in any browser):\\n\\n* Place cursor on an empty line.\\n* Input \\'ą\\' ([[ą]]). This is accomplished by pressing AltGr+a (right Alt+a, Alt+Ctrl+a) when using the \"Polish (Programmers)\" keyboard layout on Windows 7 (this is the default layout for Polish).\\n* Type in something else. The \\'ą\\' disappears, because it was never handled by ve.ce, only by native contenteditable element.\\n\\nI only tested this on Windows 7, but I believe other operating systems all use the same method. Other letters with diacritics from the [[Polish alphabet]] are input in the same way (AltGr + base key), we have nine of them.\\n\\nOn Windows 7 you can enable this keyboard layout by typing \"keyboard layout\" into the Start menu, choosing \"Change keyboards…\" and adding the input method.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1419338125, 'spacePHID': None, 'dateCreated': 1404226500, 'dateModified': 1438735489, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67367', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The reference name for a newly added reference is not appearing in the dialog for \"Use existing reference\" while opening it for the first time', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a reference\\n3.Go to the option Use an existing reference\\n\\nObserved Result:\\nIn the dialog for using an existing reference, the reference name for the reference just added is missing just the reference number appears inside the bracket.\\nOpening it for the second time brings up the reference name\\n\\nSee the screenshot attached\\n\\nEnvironment:http://en.m.wikipedia.beta.wmflabs.org/\\nBoth on Desktop browser and iOS Device\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68869\\n\\n**Attached**: {F14576}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406765032, 'spacePHID': None, 'dateCreated': 1404175680, 'dateModified': 1443278106, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67342', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Embedded context menu gets in the way of content when live-editing a tall extension node', 'description': {'raw': '**Author:** `oliver.buchtala`\\n\\n**Description:**\\nProbably a matter of taste, but we find the embedded control not too appealing.\\nIn our case (a block equation) the button to open the inspector is typically below. However, when the element is growing (2+ lines), it is suddenly on the right-hand side.\\n\\nIt would be great if there was a way to control that and override the present behavior if desired.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408710950, 'spacePHID': None, 'dateCreated': 1404139740, 'dateModified': 1443278109, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67306', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor Mobile: Focusable nodes can't be deleted\", 'description': {'raw': \"(Chrome mobile)\\nClicking on a focusable node doesn't bring up the keyboard so there is no access to the backspace key. Even if you click on text then the focusable node, the backspace key doesn't work.\\n\\nRegardless a mobile user would expect to have a separate control for deleting focusable nodes.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407064915, 'spacePHID': None, 'dateCreated': 1403981520, 'dateModified': 1417571953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67257', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing \"delete\" / \"backspace\" when selecting a node sometimes does not delete it', 'description': {'raw': \"The same node sometimes is deleted and sometimes isn't. Appears to apply to block and inline nodes alike. Can't work out exact reproduction steps. Race condition?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403909418, 'spacePHID': None, 'dateCreated': 1403829360, 'dateModified': 1443278110, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67178', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing when a focusable node is selected should do nothing', 'description': {'raw': 'Correct outcome:\\n\\n* Select an inline image (or a reference or alien or…).\\n* Press \"a\".\\n\\nObserve that the reference has been deleted, and an \\'a\\' is in its place.\\n\\n\\nBad outcome;\\n\\n* Select a block image (or block template or…).\\n* Press \"a\".\\n\\nObserve that the block image has not been deleted, and the \\'a\\' is not in its place (and no transaction has occurred).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405551466, 'spacePHID': None, 'dateCreated': 1403829240, 'dateModified': 1443278113, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67177', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Double-click should not open items that shouldn't be opened\", 'description': {'raw': \"References defined inside a {{reflist}} aren't editable – but double-click now opens the reference dialog (to empty content).\\n\\nI imagine this happens for a few things.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404322246, 'spacePHID': None, 'dateCreated': 1403829060, 'dateModified': 1443278113, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67176', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Math tests dies when run with the Echo extensions', 'description': {'raw': \"I have tried running the unit tests with both Echo and Math installed and ends up with a database error:\\n\\n```\\n$ ls -1 extensions\\nEcho\\nMath\\nREADME\\n```\\n\\n```\\n$ cd tests/phpunit\\n$ php phpunit.php --tap --testsuite extensions\\nnot ok 588 - Error: MathDatabaseTest::testCreateTable\\nA database query error has occurred.\\nQuery: DELETE FROM unittest_math\\nFunction: MediaWikiTestCase::resetDB\\nError: 1 no such table: unittest_math\\n\\n\\n---\\n\\n#0 /core/includes/db/Database.php(1134): DatabaseBase->reportQueryError('no such table: ...', 1, 'DELETE FROM uni...', 'MediaWikiTestCa...', false)\\n#1 /core/includes/db/Database.php(2919): DatabaseBase->query('DELETE FROM uni...', 'MediaWikiTestCa...')\\n#2 /core/tests/phpunit/MediaWikiTestCase.php(572): DatabaseBase->delete('math', '*', 'MediaWikiTestCa...')\\n#3 /core/tests/phpunit/MediaWikiTestCase.php(138): MediaWikiTestCase->resetDB()\\n#4 /pear/PHPUnit/Framework/TestSuite.php(775): MediaWikiTestCase->run(Object(PHPUnit_Framework_TestResult))\\n#5 /pear/PHPUnit/Framework/TestSuite.php(745): PHPUnit_Framework_TestSuite->runTest(Object(MathDatabaseTest), Object(PHPUnit_Framework_TestResult))\\n#6 /pear/PHPUnit/Framework/TestSuite.php(705): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)\\n#7 /pear/PHPUnit/Framework/TestSuite.php(705): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)\\n#8 /pear/PHPUnit/Framework/TestSuite.php(705): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)\\n#9 /pear/PHPUnit/TextUI/TestRunner.php(349): PHPUnit_Framework_TestSuite->run(Object(PHPUnit_Framework_TestResult), false, Array, Array, false)\\n#10 /pear/PHPUnit/TextUI/Command.php(176): PHPUnit_TextUI_TestRunner->doRun(Object(PHPUnit_Framework_TestSuite), Array)\\n#11 /core/tests/phpunit/MediaWikiPHPUnitCommand.php(42): PHPUnit_TextUI_Command->run(Array, true)\\n#12 /core/tests/phpunit/phpunit.php(160): MediaWikiPHPUnitCommand::main()\\n#13 {main}\\n```\\n\\n\\nAlso the Math extension seems to be running the updater in the test.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4sfm3grxdo6hnogm4iqe', 'dateClosed': 1420904075, 'spacePHID': None, 'dateCreated': 1403805420, 'dateModified': 1420904075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67148', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor is appearing in the read mode in Firefox after canceling the edit in VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in FireFox\\n2.Without editing just click on \"Cancel\" button \\n\\nObserved Result:\\nThe cursor is still appearing at the end of the page in read mode.\\n\\nSee the screenshot attached\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14619}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416794925, 'spacePHID': None, 'dateCreated': 1403739000, 'dateModified': 1438734917, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67106', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Pawn appears when inserting a link (no preselected text) and implicitly exiting from the inspector', 'description': {'raw': '(from bug 67086)\\n\\n1. Press \"Link\" tool.\\n2. Enter a link target (url or page name).\\n3. Select the url or page name from the suggestions.\\n- Notice that the surface still shows your blinking cursor with no link or text\\n4. Click back into the surface and type text.\\n\\nExpected behaviour:\\n\\nThe link becomes a pre-annotation and the entered text the label.\\nOr, alternatively, the link autosaves and inserts itself and my text appears after the link.\\n\\nActual behaviour:\\n\\n* First character is eaten.\\n* Link is inserted.\\n* First character of link is unlinked.\\n* Pawn appears.\\n* Second and further characters inserted will remove the link and insert plain text\\n\\nSee http://cl.ly/3s460Q442L3S\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68590'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406324569, 'spacePHID': None, 'dateCreated': 1403714880, 'dateModified': 1443278115, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67088', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The highlight for images are appearing in wrong position after tapping on any image with Safari in iOS', 'description': {'raw': 'Screenshot-1\\n\\nSteps to reproduce:\\n\\n1.Open a page with safari in any iOS device which contains image in it\\n2.Now tap on the image to select it\\n\\nObserved Result:\\nThe highlight for the image is appearing much below the image \\n\\nSee the screenshots attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65326\\n\\n**Attached**: {F14511}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403806207, 'spacePHID': None, 'dateCreated': 1403656560, 'dateModified': 1443278115, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67063', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Highlight for multi-line inline template only applies to the first line of it', 'description': {'raw': 'It\\'s easiest to understand this from the screenshot.  This is a display bug.\\n\\nSteps to reproduce:\\n\\n1.  Open a page containing a (long-ish) citation dialog.\\n\\n2.  Select the ref and go to Insert > References.\\n\\n3.  Select the citation template (e.g., to copy it).\\n\\n4.  Ask yourself, \"Why is only the first line of this template being selected?  Why is the cite tag in the middle instead of underneath the template?\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F14508}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403696547, 'spacePHID': None, 'dateCreated': 1403656440, 'dateModified': 1417572137, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67062', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: On Chrome, new relocatable node does not work', 'description': {'raw': 'https://www.mediawiki.org/wiki/VisualEditor:Test1234?veaction=edit\\n\\nDragging the image on this page on Chrome Version 35.0.1916.153 on Mac OSX 10.9.3 does not relocate the image. The \"shadow\" and magic line appear as expected, but when the click is released the image does not move.\\n\\nThe entire interaction works properly for me on latest Firefox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403720355, 'spacePHID': None, 'dateCreated': 1403632800, 'dateModified': 1443278116, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67040', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Second tap on a reference navigates away from (closes) VE on iOS Safari', 'description': {'raw': '**Author:** `jgonera`\\n\\n**Description:**\\nAs mentioned in bug 66999 references require two taps on iOS Safari. Often, the first tap results in a lighter \"semi-selection\" appearing a bit below the actual reference. When that happens, second tap on the reference suddenly closes the editor (first video).\\n\\nThe editor doesn\\'t crash though, somehow cancel action is triggered. If you have unsaved changes, you\\'ll see a dialog asking you if you want to abandon the edit (second video).\\n\\nTested and recorder in iOS Safari 7.1.1. Does not happen on Chrome for Android.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66999\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65326'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404160121, 'spacePHID': None, 'dateCreated': 1403559480, 'dateModified': 1443278118, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67002', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: References/images require double tap to be selected on iOS Safari', 'description': {'raw': '**Author:** `jgonera`\\n\\n**Description:**\\nDouble tap required\\n\\nIf you open VE on mobile and want to edit an existing reference, you need to tap it twice. This is really hard, especially given that the tap target is quite small (which is a separate issue).\\n\\nTested and recorder in iOS Safari 7.1.1. Does not happen on Chrome for Android (just a single tap needed there).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65326\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67002\\n\\n**Attached**: {F14364}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404152708, 'spacePHID': None, 'dateCreated': 1403558880, 'dateModified': 1443278119, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66999', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf11] Template suggestions are not appearing in Betalabs while trying to add  a template', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Go to Insert>Template\\n3.Type a template name with matching suggestion in the text box\\n\\nObserved Result:\\nThere are no suggestions for template appearing in the dialog\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14341}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403639996, 'spacePHID': None, 'dateCreated': 1403548200, 'dateModified': 1443278119, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66987', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When editing a template, the title is truncated at first dot (period)', 'description': {'raw': '1. Edit [[mw:API:Meta]] in VisualEditor\\n2. Select the \"MediaWiki version 1.8\" template\\n\\nA popup appears showing the template\\'s correct name (\"MW 1.8\").\\n\\n3. Open the transclusion editor for the template\\n\\nVE thinks it is editing a template called \"MW 1\".\\n\\nAlso note that when you try to insert a template with a period in its name, like \"MW 1.8\", you get a whole lot of suggestions for \"MW 1\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403827141, 'spacePHID': None, 'dateCreated': 1403416680, 'dateModified': 1443278119, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66939', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Compress POST data in the client', 'description': {'raw': \"Until Parsoid removes metadata, large articles are going to consist of several megabytes of data (en:Barack_Obama = 3.4MiB). As browsers doesn't provide any mechanism for compressing post data, this is takes about 20s to upload on a typical 1Mbps up ADSL line.\\n\\nUsing a JS implementation of deflate, we could achieve 80-90% compression in a few hundred ms on a decent machine: http://jsperf.com/js-deflate\\n\\nA couple of considerations with performing such a complex calculation in pure JS:\\n\\n* Really bad JS engines or slow devices (old browsers, IE, mobile) may offer to little to overall speed benefit. We may want to detect these cases by user agent or performance profiling.\\n* The compression function will be synchronous and lock browser interaction. On slower machines this may give the appearance of crashing, or with memory leaks may actually crash. If this proves to be a significant problem we could look into encoding in chunks of 100k at a time so we could at least provide progress, and maybe improve memory usage (at the cost of overall compression).\\n\\n--------------------------\\n\\n**See Also**:\\n* {T61659}\\n* {T61660}\\n* {T66171}\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404172123, 'spacePHID': None, 'dateCreated': 1403358000, 'dateModified': 1570755337, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66914', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf11] Formula icon is missing in the Insert menu', 'description': {'raw': 'Screenshot\\n\\nFormula icon is missing in the Insert menu\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F14131}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403569456, 'spacePHID': None, 'dateCreated': 1403295660, 'dateModified': 1443278122, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66890', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking on \"Make full size\" switches to Custom tab, keeping the default size and not making it full size on the first attempt for all kind of images', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Open the Media Settings dialog for the image\\n4.Go to Advanced Settings tab\\n5.Click on \"Make full size\"\\n\\nObserved Result:\\nIt switches to the Custom tab and keeps the size value as default instead of making it full size.\\n\\nEnvironment:Betalabs,test2, en.wiki\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404843583, 'spacePHID': None, 'dateCreated': 1403221860, 'dateModified': 1443278122, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66863', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf10] Context menus are appearing and then disappearing right after adding cite options/references/formula/image', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a cite option/references/formula/image\\n\\nObserved Result:\\nObserve that the,context menus are appearing for these items for a second and then suddenly disappears right after adding\\n\\nEnvironment: Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403719650, 'spacePHID': None, 'dateCreated': 1403201760, 'dateModified': 1443278125, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66855', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix tabindexes in the citation dialog', 'description': {'raw': \"On English Wikipedia, tabbing in the citation dialog is broken.  To reproduce:\\n\\n1. Edit an article with VE.\\n2. Choose 'News' from the Cite menu.\\n3. Click the first field.\\n4. Tab to try to get to the next field.\\n\\nFocus goes to a help icon, and even tabbing repeatedly will not get it to leave that icon.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65554\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404152426, 'spacePHID': None, 'dateCreated': 1403155500, 'dateModified': 1443278125, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66824', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The Math and Heiro Inspector jumps to the beginning of the article while opening it for the first time of every edit session', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Attempt to insert a formula or a hiero with the inspectors\\n\\nObserved Result:\\nThe math inspector jumps to the beginning of the article then comes back to the right position where it was intended to open\\n\\nFor hiero, it gets stuck at that position.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14045}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403734360, 'spacePHID': None, 'dateCreated': 1403128380, 'dateModified': 1443278125, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66813', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf10] Save fails with fatal error', 'description': {'raw': 'as a logged in user on any page in http://en.wikipedia.beta.wmflabs.org/\\n\\nedit a page and attempt to save.\\n\\nSave your changes interface shows \"Error: unknown error\"\\n\\nfatal.log shows \\n\\n[2014-06-18 16:18:37] Fatal error: Call to a member function getDisplayTitle() on a non-object at /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditorEdit.php on line 120\\nServer: deployment-apache01\\nMethod: POST\\nURL: http://en.wikipedia.beta.wmflabs.org/w/api.php\\nCookie: enwiki-gettingStartedUserId=kJSYCjZCvJa3o9xl48ODXiGk1DaduG2m; centralauth_LoggedOut=1402329725; ve-beta-welcome-dialog=1; optin=beta; centralnotice_bucket=0-4.2; edittoolscharsubset=0; GeoIP=US:Tucson:32.2217:-110.9265:v4; uls-previous-languages=%5B%22en%22%5D; mediaWiki.user.sessionId=2vKzOP6dVykMZfazhyIC7OKY5jkC0O3t; enwikiUserID=54; enwikiUserName=Cmcmahon; enwikiSession=29dd771993d2f54b0eb86b9ccc4e85df; centralauth_User=Cmcmahon; centralauth_Session=caf75694c6a3d741ef094fac43c50f47\\nBacktrace:\\n#0 /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditorEdit.php(120): ApiVisualEditorEdit::execute()\\n#1 /srv/common-local/php-master/includes/api/ApiMain.php(908): ApiVisualEditorEdit->execute()\\n#2 /srv/common-local/php-master/includes/api/ApiMain.php(363): ApiMain->executeAction()\\n#3 /srv/common-local/php-master/includes/api/ApiMain.php(334): ApiMain->executeActionWithErrorHandling()\\n#4 /srv/common-local/php-master/api.php(85): ApiMain->execute()\\n#5 /srv/common-local/w/api.php(3): require(\\'/srv/common-loc...\\')\\n#6 {main}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66717'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403122941, 'spacePHID': None, 'dateCreated': 1403108460, 'dateModified': 1443278126, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66792', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor Mobile: There's no way to apply heading/etc. paragraph formatting\", 'description': {'raw': \"There's no way to apply heading styles.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420843119, 'spacePHID': None, 'dateCreated': 1403098140, 'dateModified': 1420843119, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66782', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression] Link suggestions are not appearing while trying to add link target from link inspector in Nexus 7(Android 4.4.2) and iOS', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE \\n2.Type a text in CE\\n3.Select that text\\n4.Click on Link inspector icon from the toolbar\\n\\nObserved Result:\\nThe link inspector dialog opens but there is no suggestion for link target, also the text selected should appear in the text field inside link inspector, which is not happening as well\\n\\nDevice: Nexus 7(Android 4.4.2)\\nEnvironment:Betalabs\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13913}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404331548, 'spacePHID': None, 'dateCreated': 1403045460, 'dateModified': 1443278128, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66753', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf9] In Firefox, closing the Language Inspector without making any change throws sel.nativeSelection is null', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in Firefox\\n2.Go to Insert>Language\\n3.Close the language inspector without making any change\\n\\nObserved Result:\\nAn error appears in the console:\\nTypeError: sel.nativeSelection is null\\n\\nSee the screenshot attached\\n\\nEnvironment:test2 and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13853}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403223776, 'spacePHID': None, 'dateCreated': 1403030700, 'dateModified': 1443278128, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66734', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template dialog throws error when target is a wikitext expression', 'description': {'raw': 'on https://www.mediawiki.org/wiki/Extension:Gadgets and edit throws following error:\\nTypeError: title is null\\nhttps://bits.wikimedia.org/static-1.24wmf9/resources/src/mediawiki/mediawiki.Title.js\\nLine 123\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404963452, 'spacePHID': None, 'dateCreated': 1403017560, 'dateModified': 1443278128, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66724', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page remains \"editable\" after saving', 'description': {'raw': 'VE editable div remains after Save\\n\\nAs a logged in user on beta labs http://en.wikipedia.beta.wmflabs.org/\\n\\nEdit any page and Save\\n\\nUser can continue to type in the saved page in a VE documentNode div\\n\\nSee screen shot\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66792\\n\\n**Attached**: {F13826}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403124705, 'spacePHID': None, 'dateCreated': 1403013420, 'dateModified': 1417572211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66717', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf10] In Firefox, Saving the edit on a page everytime throws error: this.debugBar is null and cannot re-open VE after that', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in Firefox\\n2.Go to Insert>Language\\n3.Close the language inspector without making any change\\n4.Click on \"Save Page\"\\n\\nObserved Result:\\nAfter step 3 you get the error: TypeError: sel.nativeSelection is null\\nAfter saving there is another error in the console:\\nTypeError: this.debugBar is null\\n\\nIf you had categories add on this page, they move to the top of the page\\nThe context menu for Language Inspector is still open in read mode\\nTry to reopen VE , clicking on Edit button, VE does not open.\\n\\nEnvironment: test2 and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13751}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403028723, 'spacePHID': None, 'dateCreated': 1402957200, 'dateModified': 1443278129, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66692', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Getting \"Error: Inserted data is trying to close the root node (at index 0)\" while trying to go the next line after inserting a Hiero in Firefox', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a pag with VE\\n2.Insert a Heiro\\n3.While the cursor is at the end of hiero, hit return to go the next line\\n\\n\\nObserved Result:\\nError: Inserted data is trying to close the root node (at index 0) appears and cannot go to the next line\\n\\nEnvironment:\\n\\nBetalabs, test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412360025, 'spacePHID': None, 'dateCreated': 1402956420, 'dateModified': 1443278132, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66691', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Scrolling for &vesection=N works correctly except for N=0, where it scrolls to the bottom of the document', 'description': {'raw': \"When a page is opened in the wikitext editor with section=0, the top of the page is presented for editing The is the desired and expected behavior:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Armadillo&action=edit&section=0\\n\\nHowever, VisualEditor does not do this when vesection=0 is opened up for editing. The cursor is placed at the top of the page, but the screen scrolls down to the bottom of the page. The expected behavior is that the scree stay at the top of the window:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Armadillo&veaction=edit&vesection=0\\n\\nThis does not occur when using section=0:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Armadillo&veaction=edit&section=0\\n\\nThis is particularly important to the Russian Wikipedia, where they regularly use edit&section=0 links and it's easy to wind up with vesection=0.\\n\\nHere's the report on my ru.wp talk page, with ru.wp links:\\nhttps://ru.wikipedia.org/w/index.php?title=%D0%9E%D0%B1%D1%81%D1%83%D0%B6%D0%B4%D0%B5%D0%BD%D0%B8%D0%B5_%D1%83%D1%87%D0%B0%D1%81%D1%82%D0%BD%D0%B8%D0%BA%D0%B0:Keegan_(WMF)&oldid=prev&diff=63662618\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403715275, 'spacePHID': None, 'dateCreated': 1402939800, 'dateModified': 1443278132, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66674', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression pre-wmf10] Review your changes throws fatal error', 'description': {'raw': 'On any page at http://en.wikipedia.beta.wmflabs.org/ \\n\\nMake an edit\\n\\nClick Review your changes\\n\\nUser sees a modal dialog saying \"Error loading data from server: error.\"\\n\\n\\nfatal log shows\\n\\n[2014-06-16 14:57:25] Fatal error: Call to a member function get() on a non-object at /srv/common-local/php-master/includes/api/ApiQueryRevisions.php on line 629\\nServer: deployment-apache02\\nMethod: POST\\nURL: http://en.wikipedia.beta.wmflabs.org/w/api.php\\nCookie: enwiki-gettingStartedUserId=kJSYCjZCvJa3o9xl48ODXiGk1DaduG2m; centralnotice_bucket=1-4.2; centralauth_LoggedOut=1402329725; ve-beta-welcome-dialog=1; edittoolscharsubset=0; optin=beta; GeoIP=US:Tucson:32.2217:-110.9265:v4; uls-previous-languages=%5B%22en%22%5D; mediaWiki.user.sessionId=y0AhKxKUggdcyUd7KMOLw6Bx8JuBJTqT; enwikiUserID=54; enwikiUserName=Cmcmahon; enwikiSession=090850308740c4e1214d05399aa6d221; centralauth_User=Cmcmahon; centralauth_Session=d47cf247a4d3ea1081576f3520609ffe\\nBacktrace:\\n#0 /srv/common-local/php-master/includes/api/ApiQueryRevisions.php(629): ApiQueryRevisions::extractRowInfo()\\n#1 /srv/common-local/php-master/includes/api/ApiQueryRevisions.php(402): ApiQueryRevisions->extractRowInfo(Object(stdClass))\\n#2 /srv/common-local/php-master/includes/api/ApiQuery.php(282): ApiQueryRevisions->execute()\\n#3 /srv/common-local/php-master/includes/api/ApiMain.php(908): ApiQuery->execute()\\n#4 /srv/common-local/php-master/includes/api/ApiMain.php(332): ApiMain->executeAction()\\n#5 /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditor.php(230): ApiMain->execute()\\n#6 /srv/common-local/php-master/extensions/VisualEditor/ApiVisualEditor.php(501): ApiVisualEditor->diffWikitext(Object(Title), \\'Starting a new ...\\')\\n#7 /srv/common-local/php-master/includes/api/ApiMain.php(908): ApiVisualEditor->execute()\\n#8 /srv/common-local/php-master/includes/api/ApiMain.php(363): ApiMain->executeAction()\\n#9 /srv/common-local/php-master/includes/api/ApiMain.php(334): ApiMain->executeActionWithErrorHandling()\\n#10 /srv/common-local/php-master/api.php(85): ApiMain->execute()\\n#11 /srv/common-local/w/api.php(3): require(\\'/srv/common-loc...\\')\\n#12 {main}\\n[2014-06-16 14:57:25]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402955700, 'spacePHID': None, 'dateCreated': 1402930860, 'dateModified': 1602870077, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66669', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Keyboard events not detected after selecting a focusable node with the mouse', 'description': {'raw': '1. Click on an image\\n2. Press delete\\n\\nNothing happens\\n\\nContrast with focussing an image by keyboard navigation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403055500, 'spacePHID': None, 'dateCreated': 1402836420, 'dateModified': 1443278133, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66638', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image CE HTML should match Parsoid', 'description': {'raw': 'When converting between block and inline images we hide the <figcaption> with CSS instead of removing it from the DOM tree. We need to preserve the caption in case the user converts from inline back to block, but this can be done in the model.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409254775, 'spacePHID': None, 'dateCreated': 1402736640, 'dateModified': 1443278133, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66610', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawns appear when undoing and redoing the highlighted character from text created in a blank link', 'description': {'raw': \"* Move your cursor anywhere in the document, don't select anything.\\n* Open the link inspector\\n* Set target anywhere\\n* Click back to document in the same position\\n* Press any key\\n* New character is shown, but is highlighted. If you undo and then redo, a pawn character appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68590\"}, 'authorPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406324798, 'spacePHID': None, 'dateCreated': 1402600500, 'dateModified': 1443278135, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66548', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: REL1_23 branch not compatible with MediaWiki 1.23', 'description': {'raw': 'After a fresh installation of MW 1.23 (from the tarball), adding VisualEditor and configuring parsoid, the \"Edit\" (or \"Create\") link of any page is not working.\\n\\nI am not the only one having this problem: https://www.mediawiki.org/wiki/Extension_talk:VisualEditor#Can_not_get_VisualEditor_extension_for_MediaWiki_REL1_23_working_on_freshly_installed_system_44018\\n\\nWhat I saw when I checked with FireBug:\\n* In an old (1.22) installation clicking \"Edit\" results in a POST-request with action=visualeditor&paction=parse&page=Main_Page&format=json as its content.\\n* In the new installation no request is visible in FireBug when clicking on \"Edit\".\\n\\nOne more finding: It seems to work in 1.23alpha. I used wikiapiary to search for sites using VisualEditor and found e.g. this one: http://techwiki.umbel.org/index.php/Special:Version where it works...\\n\\nSome more investigation:\\nusing the Poster-extension of Firefox to manually POST \\n\"action=visualeditor&paction=parse&page=Main_Page&format=json\" (application/x-www-form-urlencoded) to .../api.php\\nreturns good looking content of type \"application/json; charset=utf-8\" (see attachment \"visualeditor_postresponse.json\").\\n\\nBut the JS-compoments of VisualEditor are not displaying anything!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-3x5zfm7iedaghxnnelco', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403633787, 'spacePHID': None, 'dateCreated': 1402562460, 'dateModified': 1446146655, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66519', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Magic word strings aren't nowikid if the relevant DOM node is not in a start-of-line context\", 'description': {'raw': \"Right now they're not, which is irritating when I'm writing about how VE supports the functionality. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403644060, 'spacePHID': None, 'dateCreated': 1402552140, 'dateModified': 1403644060, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66514', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Work out whether removing repositionOnly parameter in DesktopContext.update() was a good idea', 'description': {'raw': \"It's unused now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405375988, 'spacePHID': None, 'dateCreated': 1402532640, 'dateModified': 1443278136, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66507', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Swapping an existing reference scrolls viewport to top', 'description': {'raw': '* Create two references, one above the fold and one below\\n* Scroll down to the one below the fold, inspect it, and use the \"Use existing reference\" feature to swap it out for the first one\\n* The page is now scrolled to the top\\n\\nI think this might be because we delete and reinsert the reference?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65882'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403060858, 'spacePHID': None, 'dateCreated': 1402442100, 'dateModified': 1443278138, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66462', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: GeneratedContentNode rerenders with double-escaped HTML entities', 'description': {'raw': '* Create a page with <syntaxhighlight lang=\"javascript\">foo && bar</syntaxhighlight>\\n* Open the page in VE\\n* Inspect the syntaxhighlight block and change bar to baz\\n* Observe &amp;&amp; instead of && in the preview\\n\\nSaving the change doesn\\'t double-encode the ampersands though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404435630, 'spacePHID': None, 'dateCreated': 1402436820, 'dateModified': 1417572124, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66456', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf9] Hovering over a context menu is not highlighting the entire context menu', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page in VE with Firefox\\n2.Add a link or reference\\n3.Select the node\\n4.When the context menu appears, hover over it\\n\\nObserved Result:\\nIts not highlighting the entire context menu, but some part of it\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13767}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402527451, 'spacePHID': None, 'dateCreated': 1402426980, 'dateModified': 1443278139, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66444', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Extension jobs are not reset properly (files no longer present in mediawiki-core@master still persist)', 'description': {'raw': 'QUnit is complaining whenever I try and +2 code and it is preventing merges from happened e.g. https://gerrit.wikimedia.org/r/#/c/138375/ https://integration.wikimedia.org/ci/job/mwext-MobileFrontend-qunit/6228/console\\n\\nAfter talking to Antoine we think it might be a side effect of the warnings produced by: https://gerrit.wikimedia.org/r/#/c/135429/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402508594, 'spacePHID': None, 'dateCreated': 1402417680, 'dateModified': 1402880758, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Getting  \"Your edit may have been corrupted – please review before saving\" message while making changes to an image in the page', 'description': {'raw': 'I have been getting this issue since this morning, I think this has something to do with changing image size when the size of an image gets adjusted or changed.\\nI do not have the exact steps to reproduce for now.But it happened this one time when I changed the thumbnail left aligned image to centre float.\\n\\nThis is the page where you will see the image on which I made the change and getting the edit conflict error :\\nhttp://en.wikipedia.beta.wmflabs.org/wiki/9thjunechrome?veaction=edit\\n\\nWe had encountered similar kind of issue quiet a while ago, which was fixed:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62172\\n\\nI am not sure, if the same cause is behind the bug or not\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402362353, 'spacePHID': None, 'dateCreated': 1402357800, 'dateModified': 1443278139, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66396', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ResourceLoader: Modules should be able to specify dependencies evaluated at run-time', 'description': {'raw': \"Sometimes modules have dependencies that can't be determined until runtime; most obviously, code that requires shims for browser functionality that may be missing on a few clients.\\n\\nIt would be great if instead of static dependencies, modules could specify dependencies that are evaluated at run-time and only loaded if needed.\\n\\n--------------------------\\n**Version**: 1.24rc\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56341\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402546156, 'spacePHID': None, 'dateCreated': 1402342020, 'dateModified': 1402546156, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66390', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot resize frame image in MediaWiki, but can in VisualEditor(?)', 'description': {'raw': '**Author:** `vojtech.dostal`\\n\\n**Description:**\\nA student of Education program at Czech Wikipedia noticed that she cannot resize an image which is inserted as a frame. It is well possible to adjust the size in the preview mode, but saving it does not produce appropriately resized image frame. \\n\\n\\nsee image under heading \"Půdorys\" at:\\nhttps://cs.wikipedia.org/wiki/Kostel_Nanebevzet%C3%AD_Panny_Marie_%28Charvatce%29\\n\\nThank you\\nVojtěch Dostál\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404226967, 'spacePHID': None, 'dateCreated': 1402266840, 'dateModified': 1443278142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66353', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf9] While changing an image type from Thumbnail/Frame to Frameless/Basic, the wrap option gets unchecked but the alignment tabs remain active in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Change the Image type from Thumbnail to Frameless/Basic\\n\\nObserved Result:\\n\\nThe checkbox for wrap option gets unchecked but the alignment tabs are still active\\n\\nSee the screenshot attached\\n\\nThis is happening in Betalabs but not on test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13997}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402518784, 'spacePHID': None, 'dateCreated': 1402095420, 'dateModified': 1443278142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66288', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] \"manual subst\" hack doesn\\'t work any more', 'description': {'raw': 'It\\'s not really possible to subst MediaWiki templates in VE yet (bug 49904). According to James F., it should be possible to write \"subst:Foo\" when inserting the template with some caveats.\\n\\nThis doesn\\'t seem to work at the time. For example, writing \"subst:Clarify\" in the English Wikipedia, shows the string \"{{subst:Clarify}}\", but as a template with a highlight. When the page is saved, the template {{Clarify|date=June 2014}} is inserted - not substed.\\n\\nFrom IRC:\\n\\naharoni: Is there a way to do a subst to a template in VE?\\nJames_F: aharoni: Ish.\\nJames_F: aharoni: To add a template called \"Foo\", instead tell it to insert subst:Foo\".\\nJames_F: aharoni: But it doesn\\'t get the TemplateData (so it\\'s pretty icky).\\nJames_F: aharoni: There\\'s a bug asking for an actual checkbox.\\n[...]\\naharoni: James_F: about that subst thing: It doesn\\'t seem to work. It inserts a literal {{subst:Foo}}.\\nJames_F: aharoni: Huh. That\\'s a regression, then. :-(\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49904'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402153458, 'spacePHID': None, 'dateCreated': 1402089360, 'dateModified': 1417572238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66281', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf8] Cannot switch to edit source mode , shows the message \"Some parts of the edit form did not reach the server; double-check that your edits are intact and try again.\" on top of the page', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open any page with VE in Firefox or Chrome\\n\\n2.Make an Edit\\n\\n3.Click on \"Switch to source editing\"\\n\\nObserved Result:\\nIt does not open the wikitext editor for the page, rather a message appears at the op of the page: \\nSome parts of the edit form did not reach the server; double-check that your edits are intact and try again.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13873}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402084650, 'spacePHID': None, 'dateCreated': 1402013460, 'dateModified': 1443278145, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66231', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Would be nice if copying/pasting kept working after a fatal', 'description': {'raw': \"Obviously it'd also be nice if fatals didn't happen, but I have less faith that that is possible in shorter time…\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427757067, 'spacePHID': None, 'dateCreated': 1402012080, 'dateModified': 1660398841, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66229', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf8] TypeError:this.documentView is null appearing after saving an edit and then reopening the VE again, also cannot switch to edit source mode after that in Firefox', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open any page in Betalabs or test2 with VE in Firefox\\n\\n2.Make an edit\\n\\n3.Save the page\\n\\n4.Reopen the page\\n\\nObserved Result:\\n\\nIn the console the following error appears:\\n\\n\\nTypeError: this.documentView is null\\n\\nAlso, another issue that is happening is, after editing if you try to switch to edit source mode, it is not opening the wikitext editor.Rather showing a message:\\nSome parts of the edit form did not reach the server; double-check that your edits are intact and try again.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13849}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403118259, 'spacePHID': None, 'dateCreated': 1402006920, 'dateModified': 1443278145, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66222', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <nowiki> tags appear when editing on the Hebrew Wiki', 'description': {'raw': '<nowiki> tags appear when editing on the Hebrew Wikipedia:\\n\\nExamples:\\nhttps://he.wikipedia.org/w/index.php?title=%D7%99%D7%A8%D7%95%D7%9F_%D7%9E%D7%A8%D7%92%D7%95%D7%9C%D7%99%D7%9F&curid=1154717&diff=15542199&oldid=15542181\\n\\nhttps://he.wikipedia.org/w/index.php?title=%D7%99%D7%A8%D7%95%D7%9F_%D7%9E%D7%A8%D7%92%D7%95%D7%9C%D7%99%D7%9F&curid=1154717&diff=15542199&oldid=15542181\\n\\nhttps://he.wikipedia.org/w/index.php?title=HOT&diff=15542428&oldid=15528284\\n\\nFrom the given examples, it seems to be related to editing internal links?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412539179, 'spacePHID': None, 'dateCreated': 1401996780, 'dateModified': 1417571325, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66210', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fields are case sensitive in citation dialog, allowing duplicates of the same field', 'description': {'raw': 'Two URL fields visible.\\n\\nThe citation dialog field selector is case sensitive. This allows the same field to be added multiple times as long as it\\'s a different case. This results in a \"multiple <field>\" error when the citation is inserted because the fields are treated as case insensitive. \\n\\nThis issue could organically come up if a citation was added using wikitext and then another user inspected the citation in VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F13823}'}, 'authorPHID': 'PHID-USER-evd3wnvnlb66lrwulch4', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408273027, 'spacePHID': None, 'dateCreated': 1401993720, 'dateModified': 1417571940, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66207', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: ve.dm.MWImageModel#getUpdatedAttributes shouldn't need to modify Scalable\", 'description': {'raw': 'See comments on https://gerrit.wikimedia.org/r/#/c/136981\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402425824, 'spacePHID': None, 'dateCreated': 1401925620, 'dateModified': 1443278146, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66149', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link inspector should not send invalid titles to the API for suggestions (because it won't be valuable)\", 'description': {'raw': 'VE does not seem to accept the following link:\\n\\nhttps://graphite.wikimedia.org/render/?width=588&height=310&_salt=1401910888.742&from=00%3A00_20140513&until=23%3A59_20140604&target=frontend.navtiming.totalPageLoadTime.desktop.authenticated.median&target=frontend.navtiming.totalPageLoadTime.desktop.anonymous.median\\n\\nInstead, it reverts to the highlighted text as the link target.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66139'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402090035, 'spacePHID': None, 'dateCreated': 1401911520, 'dateModified': 1443278148, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66135', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: isMsie doesn't catch MSIE 11+\", 'description': {'raw': \"So odd behaviour untested in MSIE11 for CE isn't done differently…\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409099544, 'spacePHID': None, 'dateCreated': 1401835080, 'dateModified': 1443278149, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66096', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf8] Clicking on \"Add Label\"/Close button in simple link inspector throws TypeError: this.linkNode is null', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page\\n2.Open a link inspector\\n3.Click on the Add label link\\n\\nObserved Result:\\nTypeError: this.linkNode is null shows up in the console and cannot close the link inspector afterwards.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14090}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401743306, 'spacePHID': None, 'dateCreated': 1401738360, 'dateModified': 1417572232, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66047', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The \"Cite\" toolbar item is not internationalised in the Media and Reference dialogs', 'description': {'raw': 'To reproduce:\\n1. Edit an article in the Hebrew Wikipedia.\\n2. Click Insert (הוספה) -> Reference (הערת שוליים).\\nObserved: The \"Cite\" item in the toolbar is in English.\\nThere seems to be a message for it - visualeditor-toolbar-cite-label, and it was translated to Hebrew on May 12 and exported to the code, but it doesn\\'t appear.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401927706, 'spacePHID': None, 'dateCreated': 1401723360, 'dateModified': 1417572289, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66039', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add reference (footnote) dialog is LTR in RTL wikis', 'description': {'raw': 'To reproduce:\\n1. Edit an article in the Hebrew Wikipedia.\\n2. Click Insert (הוספה) -> Reference (הערת שוליים).\\nObserve: The contenteditable div for writing the footnote text is forced to dir=\"ltr\".\\nExpected: It must be in the direction of the wiki - dir=\"rtl\", or simply without the dir, and inherit the direction.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406317992, 'spacePHID': None, 'dateCreated': 1401722160, 'dateModified': 1443278149, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66037', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: adding a new link shows the target of the previously-added link for a few moments in the link inspector', 'description': {'raw': 'To reproduce:\\n\\n1. Edit an article with the words Dog and Cat.\\n2. Select the word \"Dog\". Press Ctrl-K and add an internal link to Dog.\\n3. Select the word \"Cat\".\\n4. Press Ctrl-K.\\n\\nObserve: In the auto-suggestions, \"Dog\" appears for a few moments before it is replaced by \"Cat\".\\nExpected: Linking to \"Dog\" is irrelevant here. The previous target and auto-suggestions shouldn\\'t be reused here.\\n\\nI find this rather disruptive because I want to use the link inspector for its primary purpose of adding links quickly, and this actually delays me by a few seconds. What\\'s worse is that if I\\'m not careful, I can add a link with the wrong target.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402533386, 'spacePHID': None, 'dateCreated': 1401699120, 'dateModified': 1443278151, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66016', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf7] TypeError: sel.nativeSelection is null appears while closing the reference dialog or adding reference /using existing reference in Firefox', 'description': {'raw': 'Steps to reproduce;\\n\\n1.Open a page \\n2.Open the reference dialog \\n3.Click on use existing reference or just simply close it\\n\\nObserved Result:\\nTypeError: sel.nativeSelection is null aappears in the console\\n\\nEnvironment:test 2 and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401483044, 'spacePHID': None, 'dateCreated': 1401431160, 'dateModified': 1417572220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65935', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf7] Characters and Pawns are getting added in each line and throwing error: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds while trying to add a reference in Firefox', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce\\n\\n1.Open a page\\n2.Go to Insert>Reference\\n3.Type in a text as reference\\n\\nObserved Result:\\nEach letters are getting added in each line , ends with a pawn then the text appears.The following error appears in the console:\\n\\nError: ve.dm.Document.getNodeFromOffset(): offset -1 is out of bounds\\n\\nAfter clicking on \"Insert Reference\":\\n\\nTypeError: sel.nativeSelection is null\\n\\nAfter saving the page:\\nTypeError: elem.ownerDocument.defaultView is null\\n\\nThis issue is happening on Firefox only.\\n\\nEnvironmen:test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13820}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401483035, 'spacePHID': None, 'dateCreated': 1401430500, 'dateModified': 1417572220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65934', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Only insert block images at the start of a paragraph', 'description': {'raw': \"James's suggestion: never split a paragraph with a block image. It's not at all obvious what happened, especially if the image is floated right. Instead, we should put the image at the beginning of the paragraph. This would apply when inserting an image, converting an inline image to a block image, and when drag-and-dropping an image.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51666\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403134816, 'spacePHID': None, 'dateCreated': 1401320100, 'dateModified': 1443278155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65883', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Viewport scrolls to top after drag-and-dropping image', 'description': {'raw': \"Go to a page with an image that's below the fold (i.e. you have to scroll down to see it). Drag it and drop it in a position that's also below the fold.\\n\\nThe viewport scrolls up to the top, scrolling the image out of view :(\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62420\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66462\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402534735, 'spacePHID': None, 'dateCreated': 1401319920, 'dateModified': 1443278155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65882', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot go to the next line of an article after inserting a special character in a block slug and \"TypeError: Inserted data is trying to close the root node (at index 0)\" appears', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open this page with VE:http://en.wikipedia.beta.wmflabs.org/wiki/28thmayff?veaction=edit\\n\\n2.Insert a special character in the block slug just on top of the last image in the page\\n\\n3.Press enter to go to the next line\\n\\nObserved Result:\\nCannot go to the next line, the following error appears:\\n\\nError: Inserted data is trying to close the root node (at index 0)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13657}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1423749786, 'spacePHID': None, 'dateCreated': 1401309240, 'dateModified': 1425595422, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65873', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ExtensionDistributor: Some extensions have no versions available for download', 'description': {'raw': 'Since a few days, there are reports of the version dropdown being empty even though the branches exist. This makes it impossible to download extensions from ExtensionDistributor.\\n\\nhttps://www.mediawiki.org/wiki/Thread:Extension_talk:CirrusSearch/CirrusSearch_download\\nhttps://www.mediawiki.org/wiki/Thread:Project:Current_issues/Can%27t_download_extensions\\n\\n--------------------------\\n**Version**: master\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406830858, 'spacePHID': None, 'dateCreated': 1401283020, 'dateModified': 1406830858, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65852', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf7] Mobile VE doesn't load due to dependency on mediawiki.skinning.content.parsoid which is not available for mobile target\", 'description': {'raw': 'Error: Unknown dependency: mediawiki.skinning.content.parsoid Error {stack: (...), message: \"Unknown dependency: mediawiki.skinning.content.parsoid\"} load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:160\\n\\nlogload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:160\\nhandlePendingload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:169\\nrunScriptload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:170\\ncheckCssHandlesload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:171\\n(anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:171\\nfireload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:44\\nself.fireWithload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:46\\nself.fireload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:46\\naddEmbeddedCSSload.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:166\\n(anonymous function)load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:165\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401219438, 'spacePHID': None, 'dateCreated': 1401211500, 'dateModified': 1457110757, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65823', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'In automated browser tests, browser loses token or logs out when switching from VE to wikitext edit mode, and various other failures', 'description': {'raw': 'No manual repro or network trace so far, this is for tracking\\n\\nVE loses user token: \\nhttps://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/9/testReport/(root)/VisualEditor%20multi-edit%20workflow/Make_multiple_edits_to_the_same_article/\\n\\nVE logs user out:\\nhttps://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-firefox/12/testReport/junit/(root)/Switching%20between%20wikitext%20and%20Visual%20Editor%20modes/Switch_editing_modes_via_toolbar/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65710\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66076\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67171'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'dateClosed': 1423259465, 'spacePHID': None, 'dateCreated': 1400887020, 'dateModified': 1489594276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65709', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The reference list dialog opens with a bit wiggly animation while trying to open it first for every session', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>References list\\n3.Observe the animation that happens when you open it.\\n\\nObserved Result:\\nIn both Chrome and Firefox , there is a bit of irregular animation when you try to open the reference list for the first time\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402534756, 'spacePHID': None, 'dateCreated': 1400885220, 'dateModified': 1443278159, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65705', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: PageTriage UI appears after save', 'description': {'raw': \"PageTriage shown after saving edit.\\n\\nI've seen this a few times, but this is the first time I've been in a position to take a screen shot.  \\n\\nAfter saving an edit in VE, the PageTriage pager UI exists on the saved page.  See screen shot.\\n\\nNote: the page is still viable at http://en.wikipedia.beta.wmflabs.org/wiki/Special:NewPagesFeed\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13852}\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401320274, 'spacePHID': None, 'dateCreated': 1400884440, 'dateModified': 1443278159, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65702', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Use an existing reference\" in the reference dialog button should be disabled once user enters content in the text field and re-enabled upon deleting it', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Go to Insert>Reference\\n3.Type something in the text box\\n4.Click on \"Insert Reference\"\\n5.Again re-open that reference\\n6.Delete the content inside the text field\\n\\nObserved Result:\\nissue 1: The \"Use an existing reference\" button remains enabled when user has entered something in the textbox (step 3), it should be disabled as soon as user enters types something in the field.\\n\\nissue 2:After clicking on \"insert reference\" , when user reopens that reference, there is no \"Use an existing reference\" button in the reference dialog box (step5), the button should appear there but as \"Disabled\"\\n\\nOnce user deletes the content inside the text field (step 6), the button should again re-anabled.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402103229, 'spacePHID': None, 'dateCreated': 1400868360, 'dateModified': 1443278162, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65689', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6] For a left aligned thumbnail and Frame image, unchecking the wrapping option moves it to the right side of the page', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Make it Thumbnail or Frame\\n4.Make it left aligned\\n5.Now uncheck the wrap option \\n6.Click on \"Apply Changes\"\\n\\nObserved Result:\\n\\nThe image gets moved to the right side of the page\\n\\n\\nEnvironment : Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400903440, 'spacePHID': None, 'dateCreated': 1400715360, 'dateModified': 1443278164, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65617', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf6] Hovering over any right aligned and frameless image throws error:Uncaught TypeError: Cannot read property 'getSurface' of null\", 'description': {'raw': \"Steps to reproduce:\\n\\n1.Open a oage with VE\\n2.Insert an image\\n3.Make it right aligned and framless\\n4.Hover over it\\n\\nObserved Result:\\nIt throws the following error:\\nUncaught TypeError: Cannot read property 'getSurface' of null\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400800772, 'spacePHID': None, 'dateCreated': 1400714160, 'dateModified': 1443278164, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65616', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6] The wrapping option is getting restored again after unchecking for all Image Types', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image of any type\\n3.Now uncheck the wrapping option\\n4.Click on \"Apply Changes\"\\n5.Open the media settings dialog box again\\n\\nObserved Result:\\nThe wrap option is getting checked again\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401318622, 'spacePHID': None, 'dateCreated': 1400713740, 'dateModified': 1443278164, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65615', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6] Make full size button is getting disabled,the Default Size becomes empty after switching to custom size', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Go to this page: http://en.wikipedia.beta.wmflabs.org/wiki/21stmaychrome?veaction=edit\\n\\n2.Open the Media settings>Advanced Settings dialog for the first image\\n\\n3.Click on Custom tab for the image\\n\\n4.Once you get the size values are invalid, click on default tab\\n\\nObserved Result:\\n\\nThe fields for default size gets empty , switching back to custom also shows empty fields and the \"MAke full size\" button gets disabled\\n\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13636}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401311220, 'spacePHID': None, 'dateCreated': 1400713080, 'dateModified': 1443278165, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65611', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6] Left aligned Frameless/Basic image does not move to right upon changing the alignment to Right', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Make it frameless/basic\\n4.Change the alignment to Left\\n5.Now try to change the alignment to Right\\n6.Click on \"Apply changes\"\\n\\nObserved Result:\\nThe alignment is still set as left , not moving it to Right\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400902547, 'spacePHID': None, 'dateCreated': 1400698800, 'dateModified': 1443278167, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65596', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up unbinding of ConfirmDialog events', 'description': {'raw': 'Clean up the mess I made in https://gerrit.wikimedia.org/r/134546\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401494120, 'spacePHID': None, 'dateCreated': 1400638440, 'dateModified': 1417572292, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65571', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf6] Cannot close Media Settings dialog, empty caption field and the TypeError: TypeError: node.getCaptionNode is not a function appears', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1. Insert a frameless-left aligned image \\n2.Save the page\\n3.Reopen the page\\n4.Open the Media Settings dialog for the image\\n\\n\\nObserved Result:\\nThere is no text field for the caption,Cannot close the Media Settings dialog box.\\nThe following error appears in the console:\\nTypeError: node.getCaptionNode is not a function\\n\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13542}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400698871, 'spacePHID': None, 'dateCreated': 1400632140, 'dateModified': 1443278167, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65568', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf6] For all Image Types after changing the alignment to left, it automatically selects the alignment as right when it is positioned at the left of the page, but it doesn't change position in CE surface until save\", 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE \\n2.Insert an image \\n3.Change the Image type to \"Frame\"\\n4.Click on \"Apply changes\"\\n5.Reopen the media settings dialog\\n\\nObserved Result:\\nThough the image is on the right , the alignment is set to Left on the Media Settings dialog, and if you click on \"Apply Changes\" button now, it will move the image to left\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401921771, 'spacePHID': None, 'dateCreated': 1400626920, 'dateModified': 1417572219, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65564', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression] Switching to edit source mode throws TypeError: Cannot read property 'css' of null and TypeError: Cannot read property 'each' of null for a specific case\", 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Make an edit\\n3.Click on \"Switch to source editing \"\\n4.Click on \"No, cancel\"\\n5.Now click on the \"Cancel\" button of the editor \\n6.Click on \"Continue Editing\"\\n7.Now again go to \"\"Switch to source editing \"\\n8.This time click on \"Yes, switch\"\\n\\nObserved Result:\\nIt does not switch to edit source mode and throws the following errors in the console:\\n\\n\\nUncaught TypeError: Cannot read property \\'css\\' of null and \\nUncaught TypeError: Cannot read property \\'each\\' of null \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13495}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400681051, 'spacePHID': None, 'dateCreated': 1400622660, 'dateModified': 1443278167, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65557', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression] Can't tab to save form dialog buttons in Firefox\", 'description': {'raw': \"Bug 50047 and bug 51918 have regressed for Firefox – possibly as a result of Ed's changes to how the buttons work? Yay for Firefox and its attitude to tab indexes.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66824\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404152488, 'spacePHID': None, 'dateCreated': 1400619540, 'dateModified': 1443278167, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65554', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Non-'bitcoin:' external links with single brackets around it should be indicated as invalid external link inside link inspector\", 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the link inspector : insert [http://yahoo.com]\\n3.Apply the link\\n4.Save the page\\n\\nObserved Result:\\nThe link appears inside VE with single brackets around it: [http://yahoo.com]\\nAnd when you save the page, the unicode for the ending single bracket appears at the end of the link as a part of that link:[http://yahoo.com&#x5D;\\n\\nExpected Result:\\nThe link inspector should say to user that it is an invalid external link format.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13473}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402596313, 'spacePHID': None, 'dateCreated': 1400614080, 'dateModified': 1443278168, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65547', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Language selector from Language inspector takes long time (~15 secs) to load', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Language\\n3.Now click on \"Find Language\" button\\n\\nObserved Result:\\n\\nThe language selector dialog box takes a long time to load, approx. 15 secs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66124'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402349501, 'spacePHID': None, 'dateCreated': 1400540520, 'dateModified': 1443278170, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65512', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Category autocompletion is broken in RTL wikis', 'description': {'raw': 'a screenshot with the problem\\n\\nTo reproduce:\\n\\n1. Edit an article in the Hebrew Wikipedia using VE.\\n2. Go to the categories dialog.\\n3. Start typing a category name.\\n\\nExpected: autocompletion list appears under the input box.\\nActual: autocompletion list appears to the side of the input box.\\n\\nSee screenshot.\\n\\nThis is similar to Bug 51490.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13994}'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402426011, 'spacePHID': None, 'dateCreated': 1400505240, 'dateModified': 1443278170, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65483', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Save dialog's request for checkboxes should respect the uselang param\", 'description': {'raw': 'There is content in pt-BR after setting \"uselang=en\"\\n\\nSee the screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13936}'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402347283, 'spacePHID': None, 'dateCreated': 1400420160, 'dateModified': 1443278170, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65455', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove use of jQuery.browser', 'description': {'raw': 've.ce.Surface uses $.browser to do paste special casing; replace or remove this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401390896, 'spacePHID': None, 'dateCreated': 1400259180, 'dateModified': 1417572300, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65404', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs UI: Need a way to add a non-functional label to the top of a popupToolGroup (within the popup)', 'description': {'raw': 'See design mock-up at https://trello.com/c/xCo6uLAZ/9-5-references-dropdown-from-toolbar-styling.\\n\\nRight now, I can give a popupToolGroup a label by using the \\'label\\' param in a toolbarGroup definition:\\n{\\n    \\'label\\': \\'Cite\\',\\n    \\'type\\': \\'list\\',\\n    \\'icon\\': \\'reference\\',\\n    \\'title\\': OO.ui.deferMsg( \\'visualeditor-toolbar-cite-label\\' ),\\n    \\'include\\': [ { \\'group\\': \\'cite\\' } ]\\n}\\n\\nHowever, this puts the label above the popup (in the popupToolGroup-handle) rather than within the popup itself (as needed by the design linked to above).\\n\\nI can imagine two different ways of providing this functionality:\\n\\n1. Add a new type of param for toolbarGroups called something like \\'inner-label\\'\\n\\n2. Allow creating non-functional labels from the on-wiki group definition, for example:\\n[\\n    { \"label\": \"cite\" },\\n    { \"name\": \"web\", \"icon\": \"ref-cite-web\", \"template\": \"Cite web\" },\\n    { \"name\": \"book\", \"icon\": \"ref-cite-book\", \"template\": \"Cite book\" },\\n    { \"name\": \"news\", \"icon\": \"ref-cite-news\", \"template\": \"Cite news\" },\\n    { \"name\": \"journal\", \"icon\": \"ref-cite-journal\", \"template\": \"Cite journal\" }\\n]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402081686, 'spacePHID': None, 'dateCreated': 1400194680, 'dateModified': 1427424730, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65377', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Transclusion content blocks don't auto-expand in Firefox\", 'description': {'raw': 'Probably the same issue as we had for parameter fields?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420860223, 'spacePHID': None, 'dateCreated': 1400178360, 'dateModified': 1420860223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65356', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Blue link / red link logic should descend into links inside generated content nodes', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400178184, 'spacePHID': None, 'dateCreated': 1400178120, 'dateModified': 1417572310, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65355', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Blue link / red link logic should descend into links inside transclusions', 'description': {'raw': 'Redlinks are displayed as blue links in templates inside the VisualEditor\\n\\n\\nhttps://en.wikipedia.org/wiki/Javier_Payo?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412891280, 'spacePHID': None, 'dateCreated': 1400177400, 'dateModified': 1417571322, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65353', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: On saving a page in the File: namespace the file preview is not reshown (until reload)', 'description': {'raw': 'After saving an edit in the file namespace the big thumbnail of the file is not shown.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400523404, 'spacePHID': None, 'dateCreated': 1400164080, 'dateModified': 1443278174, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65349', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector ignores selected value', 'description': {'raw': '1. Edit some text (e.g the -> foo)\\n1. Edit existing link (e.g. on [[mw:VisualEditor]], link to \"Parsoid\")\\n2. Enter text that makes up part of a title (e.g. \"ResourceLoade\", note, the missing \"r\" at the end)\\n3. Select \"ResourceLoader\" from the suggestions\\n   (due to a bug in our search engine, this is the second suggestion, not the first:\\n   [ > ResourceLoade                                 ]\\n     - ResourceLoader/JavaScript Deprecations\\n     - ResourceLoader\\n     - ResourceLoader/Version 1 Design Specification\\n\\n4. Observe that the suggestions close after selecting an item, and the text field now contains \"ResourceLoader\". Do not press enter or click anywhere.\\n\\n5. Press Save Page\\n\\nVideo: http://cl.ly/11431q402d3A\\n\\nExpected:\\n\\n* Diff shows \"the -> foo\", and \"Parsoid -> ResourceLoader\".\\n\\n\\nActual:\\n\\n* Diff shows \"the -> foo\".\\n\\nBecause:\\n\\nWe both selected a value from the suggestions and then blurred the inspector by clicking \"Save page\". Either of those actions ought to save the value into the model, but doing both certainly should.\\n\\nThere are two weird things about this:\\n\\n* Changing step 4 and pressing Enter there instead of Save page, makes it save correctly.\\n\\nSo it seems that we just don\\'t save properly on selection or blurring and require one of Escape-key, Enter-key, Back-button or focussing surface (instead of blurring inspector / focussing anything in the main window, e.g. toolbar / save button as well, not just surface).\\n\\n* Changing step 2/3 to type \"ResourceLoader\" straight up, and not pressing Enter or clicking anywhere before clicking Save page also works. \\n\\nSo it seems that merely changing focus from input field to save page can be enough to have it saved. Maybe we have an exception for onkeyup/onchange and select is bypassing that?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408668160, 'spacePHID': None, 'dateCreated': 1400155260, 'dateModified': 1441912036, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65343', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Tapping on a link redirects to the link target page in Safari when the keyboard is hidden', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE that has link inside it.\\n2.Tap on any link \\n\\nObserved Result:\\nThe browser page gets redirected to the link target page\\n\\nTest Environment: https://en.m.wikipedia.org/\\nDevice: iPad Mini\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66999\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67002\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67063'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404243910, 'spacePHID': None, 'dateCreated': 1400114400, 'dateModified': 1443278174, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65326', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Use $.when() rather than sourceCount in MediaSearchWidget', 'description': {'raw': 'See inline comment on https://gerrit.wikimedia.org/r/#/c/133050/1/modules/ve-mw/ui/widgets/ve.ui.MWMediaSearchWidget.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406814778, 'spacePHID': None, 'dateCreated': 1400108760, 'dateModified': 1443278174, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65321', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf5] Make full size button remains disabled for any image in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Go to this page:http://en.wikipedia.beta.wmflabs.org/wiki/14thmaychrome?veaction=edit\\n2.Select the image on the page\\n3.Go to Media Settings>Advanced Settings>Image Size\\n4.Change the tab from Default to custom or Custom to Default\\n\\nObserved Result:\\n\\nThe \"Make full size\" button remains disabled for the image\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13562}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400108196, 'spacePHID': None, 'dateCreated': 1400101140, 'dateModified': 1443278177, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65314', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf5] TypeError: originalDimensions is undefined appears while saving the edit on an image', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Go to this page:http://en.wikipedia.beta.wmflabs.org/wiki/12thmayff?veaction=edit\\n\\n2.Select the first image on the page: Dau_ho_thoi_Ho.png\\n\\n3.Make any edit on the image\\'s caption field\\n\\n4.Click on \"Apply Changes\"\\n\\nObserved Result:\\n\\nThe Media Settings dialog does not get closed , the edit does not get saved\\n\\nThe following error appears in the console:\\n\\n\\nTypeError: originalDimensions is undefined\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13995}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400014137, 'spacePHID': None, 'dateCreated': 1399925160, 'dateModified': 1443278177, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65239', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels', 'description': {'raw': 'Earlier today, the toolbar in VisualEditor stopped displaying \"Cite\" on the new citation tool, and instead started displaying \"<visualeditor-toolbar-cite-label>\".  \\n\\nFor me, it displayed correctly until I changed languages to qqx to check something else; when I went back, it was broken.  For James F, it was displaying correctly until he logged out.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66543'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1445631158, 'spacePHID': None, 'dateCreated': 1399917120, 'dateModified': 1445631158, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65230', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Automatically place cursor in edit summary field', 'description': {'raw': \"TeamGale doesn't recall that in order to fill the edit summary field you need to click on that first - if she doesn't, the text she's typing, although the dialog is visible, ends up in the article instead (FF29, Win8).\\n\\nIf I hit Save changes in any of my browsers (Chrome, FF and Opera) and don't click on the dialog, nothing happens if I keep typing.\\nHowever I believe that if it is technically possible, the extra click shouldn't happen, there are no other places where the cursor should end up, and editors seeing it flashing might be encouraged to use the field a little more.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64521\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400523422, 'spacePHID': None, 'dateCreated': 1399906920, 'dateModified': 1443278178, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65222', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Cannot save any page on production after an edit with mobile VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open any page with Mobile VE \\n2.Make some Edit\\n3.Attempt to save the page\\n\\nObserved Result:\\nThe Page cannot be saved, the spinner does not go away from the page.\\nThe following error appears in the console:\\nTypeError: s is undefined\\n\\t\\n\\n...unction(s){return s.replace(/[\\'\"<>&]/g,escapeCallback);},element:function(name,a...\\n\\nload.p...203716Z (line 168)\\n\\nSee the screenshot attached\\n\\nFound on this page: https://en.m.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13680}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400191988, 'spacePHID': None, 'dateCreated': 1399673700, 'dateModified': 1443278180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65109', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: IME detection should not use useragent sniffing', 'description': {'raw': \"in ve.ce.Surface we the following line:\\n\\n if ( $.browser.msie === true && e.which === 229 ) {\\n\\nGive we haven't tested IE in so longer I suspect this might not work anymore, but if it does, we need another way to detect that this hack is needed as $.browser is deprecated.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414059000, 'spacePHID': None, 'dateCreated': 1399649400, 'dateModified': 1443278180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65077', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link icon in menu shown as \"selected\" (but only if link was created this session?)', 'description': {'raw': 'Screenshot showing link vs. formula icon to highlight difference\\n\\nIt\\'s possible to get a link inspector icon shown as \"selected\" in the inspector menu, which is… confusing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14013}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406756218, 'spacePHID': None, 'dateCreated': 1399416300, 'dateModified': 1443278184, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64979', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CTRL+A in Firefox creates a selection starting at 0 and ending after the document node', 'description': {'raw': 'Selections at non-content offsets are bad, e.g. pressing delete will throw an exception.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399626450, 'spacePHID': None, 'dateCreated': 1399324080, 'dateModified': 1443278184, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64917', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If a user has scrollbars on (e.g. on Windows/Linux), the width of the media search dialog is insufficient and so displays 4 results and a large margin per row', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Media\\n3.Type something to search a media file\\n\\nObserved Result:\\nWhen the search results appear observe that there is an extra empty column appearing at the right end in the search result dialog box.\\n\\nSee the screenshot attached\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64808\\n\\n**Attached**: {F13839}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401925033, 'spacePHID': None, 'dateCreated': 1399314000, 'dateModified': 1417572219, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64911', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve.ui.MWMediaSearchWidget fails on private wikis due to forced use of JSON-P (logged-out API)', 'description': {'raw': '**Author:** `b.coughlan2`\\n\\n**Description:**\\nTested on MW 1.22.6 with stable snapshot of VisualEditor, but looking at the master branches I\\'m quite sure that this still applies.\\n\\nSteps to reproduce\\n==================\\n\\n1. Set wiki to have read access only for users:\\n\\n   $wgGroupPermissions[\\'*\\'][\\'read\\'] = false;\\n   $wgGroupPermissions[\\'user\\'][\\'read\\'] = true;\\n\\n   Note that if testing on local environment, you will have to first open VE with the \\'Edit\\' button, so that Parsoid is not locked out by this configuration.\\n\\n2. Open the \\'Media\\' button in the VE toolbar and search for something.\\n3. The AJAX request will return \\'readapidenied\\', because it won\\'t recognise the user credentials.\\n\\n\\nCause\\n=====\\n\\nve.ui.MWMediaSearchWidget.js makes a JSONP request to the localhost. However, MediaWiki\\'s ApiMain.php:180 (https://git.wikimedia.org/blob/mediawiki%2Fcore.git/9db61c9ab58b11b639a1f95916b37b57530ec674/includes%2Fapi%2FApiMain.php#L180) will remove user credentials from JSONP requests for security reasons. Therefore, the user is treated as not being logged in and the \\'readapidenied\\' message is returned.\\n\\n\\n\\nSolution\\n========\\n\\nThere is already a TODO here from Trevor Parschal bf268e82:\\n\\n    // TODO: Only use JSON-P for cross-domain.\\n    // jQuery has this logic built-in (if url is not same-origin ..)\\n    // but isn\\'t working for some reason.\\n\\nHowever, I can\\'t see anything in the jQuery $.ajax docs that says it will switch from JSONP to JSON for same-origin requests.\\n\\nSo if it\\'s not automatic, the obvious fix is to add a function that checks for same-origin in the Javascript. But since this issue is hard to debug and may occur again for other extension developers, I think it would be better to patch the MW core so that it only strips user credentials for cross-origin JSONP requests ApiMain.php:180. \\n\\nI didn\\'t want to make a patch for this without checking about the security implications, and also to ask if there is an existing utility function in MediaWiki which checks if a request is same-origin?  \\n\\n\\nWorkaround\\n==========\\n\\nIf you are only searching the private wiki and no external sources, a temporary workaround is to change \"\\'datatype\\': \\'jsonp\\'\" to \"\\'datatype\\': \\'json\\'\"  in ve.ui.MWMediaSearchWidget.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'dateClosed': 1434050858, 'spacePHID': None, 'dateCreated': 1399207560, 'dateModified': 1443278184, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64822', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Get rid of div wrapping in template rendering', 'description': {'raw': \"Div wrapping of rendered templates causes problems, especially when the template generates something like a <tr>. We should try to get rid of this wrapping and instead put shields and what not directly in the tag itself.\\n\\nPotential issues:\\n* may not work for all tags\\n* may not work for inline tags\\n* won't work for non-tag things (text nodes, comments)\\n* tricky for multi-sibling templates\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404350131, 'spacePHID': None, 'dateCreated': 1399091520, 'dateModified': 1443278184, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64780', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'On VisualEditor load, async pre-load all the TemplateData for the page to make editing templates speedier', 'description': {'raw': \"Right now there's a noticeable delay; we can speed up user experience at the expense of resources.\\n\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426880111, 'spacePHID': None, 'dateCreated': 1399072260, 'dateModified': 1427320035, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64772', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf4] All inspector dialog UI is broken when added inside Reference/Media Settings dialog box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open a reference dialog box or Media Settings for an image\\n3.Try open any of the inspectors:Math/Hiero/Special Character\\n\\nObserved Result:\\nAll inspector appearing with broken UI\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13474}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416271003, 'spacePHID': None, 'dateCreated': 1399055460, 'dateModified': 1443278188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64761', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs UI: Auto-disabled tool group still responds to clicks', 'description': {'raw': '* Go to the tools demo\\n* Click \"auto-disabling list\"\\n* Click \"click to disable this tool\"\\n* \"auto-disabling list\" now appears greyed out\\n* Click \"auto-disabling list\"\\n* An active effect appears, even though the dropdown is disabled and you can\\'t interact with it at all\\n\\nOther disabled toolgroups don\\'t have this problem, it\\'s only the one that gets disabled dynamically.\\n\\nThis causes a bug in VisualEditor as well: click out of the editor (this disables most tools and auto-disables the Insert toolgroup), then click Insert. An active effect appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64601'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399065942, 'spacePHID': None, 'dateCreated': 1399055100, 'dateModified': 1427403775, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64759', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'mw.loader.store should not occupy all of localStorage', 'description': {'raw': \"In some cases, MediaWikiModuleStore can be quite large (over 1 MB). This can lead to local storage becoming full and causing random problems like T66716. According to https://support.mozilla.org/en-US/questions/963825 Firefox shares local storage space across all hosts on a single domain name, so this may be especially problematic for Firefox.\\n\\nIn theory, this shouldn't be an issue since people should always have some sort of fall-back behavior if there are problems with local storage, but in the interests of defensive programming, perhaps we should put a cap on the maximum size of MediaWikiModuleStore.\\n\\n--------------------------\\n**See Also**:\\n* {T66716} (bug 64716)\\n* {T67566} (bug 65566)\\n\\n**Upstream**;\\n* <https://bugzilla.mozilla.org/show_bug.cgi?id=1064466>\"}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'dateClosed': 1458258992, 'spacePHID': None, 'dateCreated': 1398981300, 'dateModified': 1650400355, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64721', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve.ce.ProtectedNode.prototype.onProtectedSetup is a performance hog', 'description': {'raw': \"Running JavaScript profiling on both desktop and mobile the majority of time is spent in jQuery.extend.css - the majority of which seems to be caused by ve.ce.ProtectedNode.prototype.onProtectedSetup\\n\\nOn mobile this seems to be even more severe.\\n\\nIn desktop 7.9% of execution time to load VisualEditor was spent in jQuery.extend.css - this was the most heavy function. In mobile it was also the most heavy - however in mobile a whopping 23.76% of time was spent in jQuery.extend.css\\n\\nStubbing out the contents of the foreach loop \\nthis.$element.add( this.$element.find( '*' ) ).each( function () {\\n\\nseems to remedy this problem.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51202\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404866176, 'spacePHID': None, 'dateCreated': 1398970740, 'dateModified': 1443278189, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64709', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf3] \"Use existing reference\" is not functioning at all in Betalabs', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page \\n2.Add few references\\n3.Now Go to Insert>Reference>Use an Existing Reference \\n4.Select one of the existing references\\n\\n\\nObserved Result:\\n\\nThe selected reference does not get added in the page and the \"Save Page\" remains disabled\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/30thAprilChrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398893712, 'spacePHID': None, 'dateCreated': 1398884040, 'dateModified': 1443276194, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64677', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up Monobook-specific mess in ViewPageTarget init code', 'description': {'raw': 'In particular, see comments on https://gerrit.wikimedia.org/r/#/c/130085/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398891382, 'spacePHID': None, 'dateCreated': 1398881280, 'dateModified': 1443276196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64672', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf3] \"Null\" appearing instead of \"Transclusion\" in the template insert dialog box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Go to Insert>Template\\n\\nObserved Result:\\n\\nObserve that, in the header of the dialog box , instead of text \"Transclusion\" ,\"Null\" is appearing\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13912}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398897127, 'spacePHID': None, 'dateCreated': 1398881220, 'dateModified': 1443276196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64671', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf3] Reference list dialog is no longer \"small\" size, but default \"large\"', 'description': {'raw': 'Larger reference dialog\\n\\nReference list dialog box is appearing much larger in size like the previous design that we had.\\n\\nSee the two screenshots attached and compare\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13908}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398908848, 'spacePHID': None, 'dateCreated': 1398880260, 'dateModified': 1443276197, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64670', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: For formulae (and some other nodes?), inspection trigger region is a single line, not the whole block', 'description': {'raw': 'The region you need to move the mouse over to get the inspector to popup.\\n\\nUsing the math editor beta feature. The region you need to position the mouse over the get the inspector icon to come up is quite small. Ideally it should be the whole size of the image.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50791\\n\\n**Attached**: {F13812}'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412588736, 'spacePHID': None, 'dateCreated': 1398807600, 'dateModified': 1642379681, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64625', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Content has too small font-size and squished line-height in MediaWiki Vector', 'description': {'raw': \"Screenshot of view and edit mode side-by-side\\n\\nEver since the typography update, the content looks malformed in the editor.\\n\\nThis is because the way the typography change in Vector was implemented, used rather specific selectors that cannot apply to VisualEditor's surface and thus it cascades in ways it wasn't supposed to.\\n\\nThe content line-height is squished, and the font size is too small.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13719}\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398899193, 'spacePHID': None, 'dateCreated': 1398772380, 'dateModified': 1443276200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64599', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Edit summary typed into the article instead of the Save dialog in Firefox', 'description': {'raw': \"Intention:\\nSave a page.\\n\\nSteps to Reproduce:\\n1. Rearrange a lot of text.\\n\\n2. Click the save button.\\n\\n3. Start typing the edit summary.\\n\\nActual Results:  \\nThe edit summary appeared where I'd last been typing in the article, rather than in the Save dialog.\\n\\nI tried to reproduce it once, with no success.\\n\\n\\nReproducible: Couldn't Reproduce\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65222\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401996489, 'spacePHID': None, 'dateCreated': 1398648360, 'dateModified': 1417572288, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64521', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Pressing tab while keeping the math inspector open throws TypeError: Cannot read property 'start' of null\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Formula\\n3.Without closing the Math Inspector keep on pressing tab\\n\\nObserved Result:\\nAn error appears in the console:\\n\\nUncaught  TypeError: Cannot read property 'start' of null\\n\\nSee the screenshot attached\\n\\nTest Environment: https://en.wikipedia.org\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14000}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398470614, 'spacePHID': None, 'dateCreated': 1398461400, 'dateModified': 1443276203, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64451', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: 0,0 initial selection in Firefox when opening a new or pre-existing references means inserting template causes fatal JS error', 'description': {'raw': \"Steps to Reproduce:\\n1. Open any page in VisualEditor.\\n\\n2. Go to Insert > Reference to add a reference.  Do NOT click inside the reference box.\\n\\n3. Go to Insert > Template to add a template.\\n\\n\\n\\nActual Results:  \\nYou can't add a template, you can't exit the dialog, you can't do anything except close the browser tab and lose all of your work.\\n\\n\\nReproducible: Always\\n\\nThis cannot be reproduced in Safari.  This cannot be reproduced if you first click inside the reference box.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398889785, 'spacePHID': None, 'dateCreated': 1398443040, 'dateModified': 1443276203, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64434', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf3] Typing fast in CE or reference dialog box shifts the first character of the text to the next line in Firefox', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412802831, 'spacePHID': None, 'dateCreated': 1398377400, 'dateModified': 1443276204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64399', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf2] Loading spinner appears in the Media Settings dialog while loading it for the first time', 'description': {'raw': 'screenshot of the loading spinner\\n\\nThere is a loading spinner appears on the Media Settings dialog box when I try to load it for the first time in a page.\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13831}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398365417, 'spacePHID': None, 'dateCreated': 1398364020, 'dateModified': 1417572408, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64377', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Snowmen inserted (or other bad breakage) with certain easy combinations of actions/keys that move the cursor out of the document', 'description': {'raw': \"<Krenair> Move the cursor to the end of a line before the start of a new section header, delete, enter, enter, up, delete, type a random character.\\n<James_F> Backwards delete or forwards delete?\\n<Krenair> Um. The delete next to 'Home' and 'End'\\n<Krenair> not backspace\\n<James_F> Forwards, then. :-)\\n<James_F> Whee, snowmen.\\n<James_F> I blame edsanders.\\n<Krenair> observed on http://en.wikipedia.org/wiki/Hippeastrum_calyptratum, depending on what random character you try (I hit 'f'), stuff breaks in a difficult to explain but quite obvious\\n<Krenair> especially if you do it twice to the same document\\n<James_F> So the first thing that happens is that the cursor ends up outside of the document.\\n<James_F> Which is Bad™.\\n<James_F> Everything breaking after this is non-deterministic, but definitely also Bad™.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398310296, 'spacePHID': None, 'dateCreated': 1398297840, 'dateModified': 1443276206, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64338', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In FireFox, the dropdown box for search results in Template dialog/ Redirect page/Categories gets sticked to the dialog if you click on Add/navigate to other tab in page settings keeping the dropbox open', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in FireFox\\n2.Go to Insert>Template\\n3.Type something in the textbox to search for templates\\n4.Now without selecting anything from the dropdown box, click on \"Add template\"\\n\\nObserved Result:\\nThe dropbox for the search results gets sticked to the template dialog box \\nIf you click on Show options button or just close the template dialog box and reopen again, it still stays\\n\\n\\nThis problem also exists for the search result dropbox for Redirect Target Page and Categories \\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser:  FF 25\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13701}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399325386, 'spacePHID': None, 'dateCreated': 1398295380, 'dateModified': 1443278192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64334', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add support for more types of ConfirmEdit captcha', 'description': {'raw': '<Krenair> The issue I get after adding ConfirmEdit to my wiki is \"Error: Unknown error\" when saving >_>\\n<Krenair> {\"visualeditoredit\":{\"result\":\"error\",\"edit\":{\"captcha\":{\"type\":\"simple\",\"mime\":\"text/plain\",\"id\":\"586723432\",\"question\":\"24+8\"},\"result\":\"Failure\"}}}\\n<James_F> Hmm.\\n<James_F> That kind of CAPTCHA isn\\'t supported yet.\\n<Krenair> meh. thought it would be something like that\\n<James_F> You\\'d need to add it to the save dialog\\'s logic.\\n[...]\\n<James_F> Krenair: It\\'s worth adding support, feel free to make a bug (I don\\'t have a list of CAPTCHA methods to support).\\n\\nI think at least Simple, Math, and Questy. Currently it looks like Fancy is supported though I haven\\'t tested it\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398978897, 'spacePHID': None, 'dateCreated': 1398290340, 'dateModified': 1443276206, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64328', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: \"Uncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method \\'saveDocument\\' \" appears while trying to save a page which was idle for a while', 'description': {'raw': \"Screenshot\\n\\nI tried to save which was open for a long time (probably ~3-4 hrs)and got the following error in the console which stopped me from saving the edited content:\\n\\nUncaught TypeError: Object #<VeInitMwMobileViewTarget> has no method 'saveDocument' \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13580}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398296076, 'spacePHID': None, 'dateCreated': 1398210960, 'dateModified': 1443276207, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64267', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression] Can't remove annotation\", 'description': {'raw': \"I challenge you!\\nVEdit https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&oldid=65498176.\\nMake the first line bold. Then un-bold it. I don't manage to.\\nWin7, Vector, Chrome/FF.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398298599, 'spacePHID': None, 'dateCreated': 1398174780, 'dateModified': 1443276209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64244', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Only most recently added parameter gets trash can icon in citation dialog', 'description': {'raw': 'Before applying the changes\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Cite>Website/Book/Newspaper/Journal\\n3.Add some optional parameters from the parameter list \\n4.Also add the parameter URL as an optional parameter\\n5.Apply changes\\n\\nObserved Result:\\nObserve that, before applying changes the parameter URL does not have a trash icon beside but the other optional parameter does.But, after applying the changes , the trash icon does appear for the parameter URL but not for the other one.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser:: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/21staprilchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14025}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398301828, 'spacePHID': None, 'dateCreated': 1398108060, 'dateModified': 1443276210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64199', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Update branches in mediawiki/extensions/* for REL1_23', 'description': {'raw': \"Current extension repositories have REL1_23 branch, but it was created when REL1_22 was created too, so basically it's outdated.\\n\\nExamples:\\n\\nhttps://git.wikimedia.org/branches/mediawiki%2Fextensions%2FCite.git\\n\\nhttps://git.wikimedia.org/branches/mediawiki%2Fextensions%2FImageMap.git\\n\\nhttps://git.wikimedia.org/branches/mediawiki%2Fextensions%2FCheckUser.git\\n\\nThey have REL1_23 updated as of 22-10-2013\\n\\nI've only found one exception, though:\\n\\nhttps://git.wikimedia.org/branches/mediawiki%2Fextensions%2FWidgets.git\\n\\n\\nOne particular change introduced on 1.23 release was the migration from PHP to JSON files for i18n. I think all the extensions were migrated to JSON files in master, but REL1_23 still doesn't have that change.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67270\"}, 'authorPHID': 'PHID-USER-jnta3z3spxto3vbxdngm', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1485513144, 'spacePHID': None, 'dateCreated': 1398010200, 'dateModified': 1485543614, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64157', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting a paragraph separator and subsequently typing any character messes up the page', 'description': {'raw': 'Steps to reproduce:\\n\\n1. Go to (say) https://en.wikipedia.org/w/index.php?title=Visual_editor&veaction=edit\\n\\n2. Place the cursor after the end of a paragraph (e.g. after the full stop in \"editors are.\")\\n\\n3. Hit the delete key to merge the paragraph with the subsequent one.\\n\\n4. Type any character (a letter, blank, etc.)\\n\\nResult: Chaos ;) - large swaths of text are deleted, and (apparently) random characters appear near the beginning of the page.\\n\\nReproduced in Chromium (Version 33.0.1750.152) and Firefox (28.0).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62333'}, 'authorPHID': 'PHID-USER-wlku5ja6envbi4cz2etp', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403060395, 'spacePHID': None, 'dateCreated': 1397889240, 'dateModified': 1443276212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64128', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Citation dialog does not focus correct field when adding a new parameter', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a Cite option like Cite Website/Cite Journal\\n3.Add some value for a parameter\\n4.Click on \"Add Parameter\"\\n5.Select a parameter\\n\\nObserved Result:\\n\\nThe cursor instead of moving to the new parameter, stays at the last edited parameter box\\n\\n\\nTest Environment:  http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398901241, 'spacePHID': None, 'dateCreated': 1397846160, 'dateModified': 1443276214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64098', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf1] Cursor jumps to the beginning of the document after adding citations/references', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a citation or a reference\\n\\nObserved Result:\\nThe cursor jumps to the beginning of the document \\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403724486, 'spacePHID': None, 'dateCreated': 1397693880, 'dateModified': 1443278192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64041', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf1] Uncaught TypeError: Cannot read property 'nextSibling' of undefined is appearing while trying to edit the next line after a saved edit in Mobile VE\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open any page with mobile VE\\n2.Add a text\\n3.Save the page \\n4.Reopen the page\\n5.Go to the next line of the text you added in step 2\\n6.Start typing something\\n\\nObserved Result:\\nThe following error appears in the console\\n\\nUncaught TypeError: Cannot read property 'nextSibling' of undefined\\n\\nSee the screenshot attached\\n\\nTest Environment:http://en.m.wikipedia.beta.wmflabs.org/\\nPage:http://en.m.wikipedia.beta.wmflabs.org/wiki/0.4040571254571662?title=0.4040571254571662&campaign=random#editor/0\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13635}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398122734, 'spacePHID': None, 'dateCreated': 1397686200, 'dateModified': 1443276217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64032', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf1] The textbox/icons/delete button inside transclusion dialog box is completely distorted  on Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\'\\n\\n1.Open a page with VE\\n2.Go to Insert>Template\\n3.Click on \"Show options\"\\n\\nObserved Result\\nThe template icon and the trash icon is overlapping with \"Add template\" button\\nThe NEw template heading is appearing below the textbox\\n\\nTry to add a content/parameter its broken for them too\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13598}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397699016, 'spacePHID': None, 'dateCreated': 1397677140, 'dateModified': 1443276217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64013', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copy-Paste of a block of HTML disables all further copy-paste of anything: FF28 on Linux', 'description': {'raw': '* Open https://www.mediawiki.org/w/index.php?title=Parsoid/Deployments&oldid=959448&veaction=edit\\n* Copy the section starting @ \"Monday, April 14, 2014 around 1pm PST : Deployed fba548cb\" including the list upto the next section\\n* Try pasting it -- nothing gets pasted.\\n* Now try copy-pasting othe things (even simple strings) .. everything fails.\\n\\nCan consistently reproduce this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402505914, 'spacePHID': None, 'dateCreated': 1397671800, 'dateModified': 1417572230, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64009', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] Vector: font-size and line-height should not be applied to #bodyContent (too specific, not applied to VisualEditor etc.)', 'description': {'raw': \"**Author:** `swalling`\\n\\n**Description:**\\nVE's edit surface has a body font size of 0.8em (equals 13px) which mismatches with the new default body font size (0.875em, which translates to 14px on Chrome and Firefox on most systems). The same is true for line-height, which is now 1.6em for body content. \\n\\nWe should make sure the two are consistent. The body font stack and heading settings do get translated to VE edit mode correctly, so we're close. :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63540\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398804515, 'spacePHID': None, 'dateCreated': 1397610060, 'dateModified': 1398813972, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63985', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting Advanced settings from the Page Options menu does not take to the Advanced Settings tab', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to page options\\n3.Select Page Settings\\n4.Go to Page options again\\n5.Select Advanced Settings from the menu\\n\\nObserved Result:\\nIt navigates to the tab that was last opened but not to Advanced Settings\\n\\nTest Environment: https://test2.wikipedia.org/ and v\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397664829, 'spacePHID': None, 'dateCreated': 1397608920, 'dateModified': 1443276220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63984', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Pull in Parsoid's new styling module so we don't need to duplicate locally\", 'description': {'raw': \"Per bug 51245 Parsoid now has the start of a CSS module –\\xa0gerrit 124785 –\\xa0which we should pull into VE. Once we've done that we can start upstreaming a lot of our local CSS hacks into Parsoid and save the effort. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60017\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51245\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398717521, 'spacePHID': None, 'dateCreated': 1397606880, 'dateModified': 1443276221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63983', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf1] Items in the page options menu stop working if you click outside the main editing area', 'description': {'raw': 'Intention:\\nSee if I could reproduce Alex\\'s bug.  I could.\\n\\nSteps to Reproduce:\\n1. Click http://en.wikipedia.beta.wmflabs.org/wiki/User:Whatamidoing_(WMF)/Sandbox?veaction=edit or open another page in VisualEditor.\\n\\n2. Click outside the main editing area.  For example, highlight part of the page title, or put the cursor in the search box.\\n\\n3. While your cursor is still outside the editing area, click the page options menu (three bars icon) and choose any item.  For example, choose \"Categories\".  (Perhaps you just used the search box to figure out how to spell the name of the category you\\'re interested in adding, and that\\'s why your cursor is in the search box.)\\n\\nActual Results:  \\nNothing happens.  \"Switch to source editing\" is the only menu item that produces a response.\\n\\nExpected Results:  \\nNormal editing behavior.  It doesn\\'t matter where my cursor is placed for these items, so they shouldn\\'t care.\\n\\nReproducible: Always\\n\\nConfirmed in Safari 6 and Firefox 28 on Mac OS 10.8.5, and assumed to affect everything.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63954'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397600481, 'spacePHID': None, 'dateCreated': 1397582280, 'dateModified': 1443276223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63945', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf1] The first letter of the reference text disappears after typing in the reference dialog box', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Reference\\n3.Type something inside the reference dialog box\\n\\nObserved Result:\\nAs soon as you type the first word the first letter diappears.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398889897, 'spacePHID': None, 'dateCreated': 1397501340, 'dateModified': 1443276223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63909', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Clicking out of inspector jumps selection back to inspected text', 'description': {'raw': \"If you click out of an inspector into some other text, it used to be that the cursor went to that text and stayed there, but now it jumps back to the text that was being inspected. I suspect this may have something to do with changes to ve.ui.DesktopContext. There seems to be a delay so maybe something's happening from a setTimeout( ..., 200 ) after the closing animation?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398124284, 'spacePHID': None, 'dateCreated': 1397496840, 'dateModified': 1443276226, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63906', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf22] Adding a reference adds an empty one; editing a reference inserts a new one', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert a reference\\n3.Type in something in the reference dialog box\\n4.Save the page\\n5.Reopen the page\\n6.Open the reference\\n\\n\\nObserved Result:\\nThere is no content in the reference dialog box\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397518479, 'spacePHID': None, 'dateCreated': 1397239320, 'dateModified': 1443276227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63828', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf22] Math inspector is not appearing in Betalabs and throwing Typeerror:Cannot call method 'getModel' of undefined\", 'description': {'raw': \"Try to open math inspector on betalabs:\\nThe following error appears on the console and the math function does not open up\\n\\nUncaught TypeError: Cannot call method 'getModel' of undefined VM2690:273\\nve.ui.MWMathInspector.setup VM2690:273\\n(anonymous function) VM2688:23\\nproxy load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2Cl…:10\\nlistenerWrapper VM2688:6\\noo.EventEmitter.emit VM2688:7\\n(anonymous function) VM2688:20\\npollExternalStylesheets\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398385253, 'spacePHID': None, 'dateCreated': 1397156220, 'dateModified': 1443276227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63785', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Icons render weirdly in IE10', 'description': {'raw': 'how the ...\\n\\nIn my Windows 7 VMWare machine the icons render strangely in the toolbar.  Image attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows 7\\n\\n**Attached**: {F13606}'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409960965, 'spacePHID': None, 'dateCreated': 1397082960, 'dateModified': 1423674434, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63749', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression] Back button in ?veaction=edit changes address bar but doesn't alter page state\", 'description': {'raw': 'Forking from bug 43844. Not good.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397687352, 'spacePHID': None, 'dateCreated': 1397067840, 'dateModified': 1443276230, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63739', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid outputs <small> as child of <figure>', 'description': {'raw': 'On http://parsoid.wmflabs.org/enwiki/User:Tamravidhir?oldid=603142295 , I see two images that look like:\\n\\n<figure><small><a href=\"...\"><img src=\"...\" /></a><figcaption>Caption text</figcaption></small></figure>\\n\\nYou can find them by opening that link in a browser and typing document.querySelectorAll(\\'figure>small\\') in a console, then clicking on the result (Firebug) or right-clicking the result and choosing \"Reveal in elements panel\" (Chrome).\\n\\nPutting a <small> inside a <figure> tag but wrapped around a <figcaption> tag is a violation of the image spec (in addition to just being insane), which causes VisualEditor to get very confused and corrupt the image, which causes Parsoid to output [[undefined|NaNxNaNpx|right|link=]], see https://en.wikipedia.org/w/index.php?title=User:Tamravidhir&diff=603142575&oldid=603142295 . This is reminiscent of bug 62805 (NaNxNaNpx).\\n\\nThe wikitext that triggers this is fairly complicated, and I haven\\'t been able to isolate a test case locally. It seems to be something like:\\n\\n* \\'\\'\\'Text\\'\\'\\'\\n<small>\\n[[File:Foo|right|200px|Caption]]\\n\\nText\\n\\n[[File:Foo|right|200px|Caption]]\\n</small>\\n* \\'\\'\\'Text\\'\\'\\'\\n<small>\\netc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1438291859, 'spacePHID': None, 'dateCreated': 1396894380, 'dateModified': 1660787087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression] Can't use save form checkboxes in Opera\", 'description': {'raw': '**Author:** `richlv`\\n\\n**Description:**\\nvisual editor from git f8d56e6804a12248b485c2d3b49d4ff0ffa7220c\\n\\nopera 12.16 on linux.\\n\\nin the save form, minor edit & watching checkboxes can not be marked\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410805662, 'spacePHID': None, 'dateCreated': 1396874100, 'dateModified': 1417571335, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63615', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'QUnit tests for jquery.makeCollapsible and jquery.color failing intermittently on Jenkins', 'description': {'raw': \"QUnit tests for jquery.makeCollapsible are often failing on Jenkins. I've seen this at least three times in the last week or so, most recently on https://gerrit.wikimedia.org/r/#/c/124051/ . Every time the failure was within the jquery.makeCollapsible tests (but I'm not entirely sure if on the same exact test).\\n\\nThis might be related to the fake timers being used in them.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405115134, 'spacePHID': None, 'dateCreated': 1396723500, 'dateModified': 1405115464, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63579', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf21] Caption field is not appearing for any image in Betalabs and throwing error TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection'\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert a media\\n3.Open the media Settings for the image\\n\\nObserved Result:\\nThe caption field is missing in the media settings dialog box .Also in the console the following error appears:\\n\\nUncaught TypeError: Object #<OoUiButtonSelectWidget> has no method 'initializeSelection'\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63544\\n\\n**Attached**: {F13747}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396911073, 'spacePHID': None, 'dateCreated': 1396658520, 'dateModified': 1443276231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63554', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf21] 'Switch to source editing' does nothing, causes js error\", 'description': {'raw': 'Reported by users and repro\\'d in beta labs\\n\\nLog in and edit any page with VE at http://en.wikipedia.beta.wmflabs.org/\\n\\nFrom the hamburger list select \"Switch to source editing\"\\n\\nNothing happens.  In the javascript console find the error \\n\\n\\nUncaught Error: OO.ui.Tool.onSelect not implemented in this subclass:function VeUiMWEditModeSourceTool(toolGroup,config){ve.ui.MWEditModeTool.call(this,toolGroup,config);}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396577482, 'spacePHID': None, 'dateCreated': 1396562520, 'dateModified': 1443276234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63503', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using browser native interactive spell-check tool causing repeated automatic deletion in Chrome', 'description': {'raw': 'Video showing issue\\n\\nChrome Version 33.0.1750.152\\n\\n1. Access spelling suggestion from right click menu\\n2. characters begin to be deleted (video attached)\\nor\\n3. Page content becomes corrupted, strange character insertions, loss of formatting. (image attached)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50822\\n\\n**Attached**: {F13521}'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423876215, 'spacePHID': None, 'dateCreated': 1396505280, 'dateModified': 1424479020, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63462', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Opening a Cite>Website/Book/Newspaper/Journal while selecting an image does not open the citation dialog', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Select an image\\n2.Click on Cite> Website/Book/Newspaper/Journal \\n\\nObserved Result:\\nIt throws an error: Uncaught TypeError: Object #<VeDmMWBlockImageNode> has no method 'getInternalItem' \\n\\nand VE gets stuck at this point, as you cannot close that dialog anymore\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Pageoffseterror?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13484}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396642409, 'spacePHID': None, 'dateCreated': 1396479120, 'dateModified': 1443276235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using browser native interactive spell-check tool adds the missing letters to the DM, but at the top of the page in Chrome', 'description': {'raw': 'Intention:\\nCorrect the spelling of a word\\n\\nSteps to Reproduce:\\n1. Open a page in Chrome.\\n\\n2. Pick a word that Chrome believes is misspelled.\\n\\n3. Right-click to correct the spelling.\\n\\n4. Save the page and check the diff.\\n\\nActual Results:  \\nTrying to change \"Minories\" to \"Minorities\" resulted in the missing \"ti\" being added at the very top of the page, rather than in the proper place.  (See http://en.wikipedia.org/w/index.php?title=User:Edgepedia/sandbox1&diff=next&oldid=602158018)\\n\\n\\n\\nReproducible: Didn\\'t try\\n\\nThis may be related to Bug 50822 or Bug 59748.  \\n\\nReported in Chrome Version 33.0.1750.154 m on Windows 7 using Vector.  Cannot be reproduced in Safari 6 (although there are other spelling problems in Safari.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50822'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409011116, 'spacePHID': None, 'dateCreated': 1396392120, 'dateModified': 1443278196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63395', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link does not get applied after concatenating a text to the existing link and reapplying the link', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n\\n2.Insert a link\\n\\n3.Now add a space and then a text next to it\\n\\n4.Now delete the space and concatenate the text with the exiting link\\n\\n5.Select the previous link and the text together\\n\\n6.Re-apply the link \\n\\n\\nObserved Result:\\nThe new link does not get applied and \"Save Page\" button remains disabled \\n\\n\\n\\nSee the screenshot attached\\n\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/1staprilChrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13327}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397090690, 'spacePHID': None, 'dateCreated': 1396377540, 'dateModified': 1443276235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63386', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf20] Parameter icons inside transclusion dialog are overlapping with the parameter name', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a Cite Web or Cite Book\\n3.Click on Show options to get the advanced widget\\n\\n\\nObserved Result:\\nParameter icons inside transclusion dialog are overlapping with the parameter name\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13392}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395962516, 'spacePHID': None, 'dateCreated': 1395880020, 'dateModified': 1443276239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63157', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf21] Uncaught Error: Unbalanced set of replace operations found (+ more) errors when trying to change bullet list to numbered list', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Create a page with VE\\n2.Add a bullet list\\n3.Add few items\\n4.Now change the list to numbered list\\n5.The cursor gets shifted to the start of the document\\n6.Now type something\\n\\nObserved Result:\\nEverything starts to behave weirdly .It starts to add text everywhere at the beginning of the page.The list disappears.\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/w/index.php?title=Checkcursorbullet&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13373}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396483556, 'spacePHID': None, 'dateCreated': 1395876240, 'dateModified': 1443276239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63154', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Update newarticletext usage for added parameter', 'description': {'raw': \"https://gerrit.wikimedia.org/r/#/c/83221/ added a parameter to newarticletext, but VE doesn't pass it, so now when you try to use VE on a nonexistent page with vanilla messages (enwiki's newarticletext message doesn't use $1) you see a raw $1 in the edit notice.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395875384, 'spacePHID': None, 'dateCreated': 1395868740, 'dateModified': 1443276240, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63146', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Cannot close the Media Settings dialog as the error Uncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode' appears in the console\", 'description': {'raw': \"screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Open the math inspector\\n3.Keep it open\\n4.Insert an image\\n5.Select the image\\n6.Click on undo \\n7.Click on the media settings icon that is still appearing at the right corner of the page\\n\\nObserved Result:\\n\\nThe Media Settings dialog box appears with empty caption field .An error appears in the console: \\nUncaught TypeError: Object #<VeDmMWMathNode> has no method 'getCaptionNode'\\n\\nAlso, you will not be able to close the Media Settings dialog box and will get stuck at this step.\\n\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_%28WMF%29?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13323}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401472140, 'spacePHID': None, 'dateCreated': 1395860460, 'dateModified': 1443278196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63132', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Citation tool matching should also match templates with whitespace before the first parameter', 'description': {'raw': 'The citation tool recongizes a citation template that starts like this:\\n\\n<ref>{{cite web|url= \\n\\nIt does not recognize one that starts like this:\\n\\n<ref>{{cite web |url=\\n\\nThe only difference is the (very common) addition of a space before the parameter.  It should understand both of these.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400095463, 'spacePHID': None, 'dateCreated': 1395859680, 'dateModified': 1443278199, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63129', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Firefox displaying icons in odd places in dialog boxes (reference, media, template, …)', 'description': {'raw': 'Intention:\\nEdit an existing reference\\n\\nSteps to Reproduce:\\n1. Open any article containing an existing citation in Firefox.  (I can\\'t reproduce this in Safari.)\\n\\n2. Open an existing reference.\\n\\n3. Look at the \"Options\" area.\\n\\nActual Results:  \\nThe icon overlaps with the text.  See screenshot.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63433\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63432'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397701125, 'spacePHID': None, 'dateCreated': 1395858900, 'dateModified': 1443276242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63127', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: An empty selection box is appearing while inserting a math formula', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Click on  Insert> Formula\\n3.Insert a formula inside then delete it \\n\\nObserved Result:\\nAn empty selection box appears\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13248}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397172262, 'spacePHID': None, 'dateCreated': 1395793260, 'dateModified': 1443276242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63093', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Close inspectors when the user clicks on the toolbar (e.g. on \"Save Page\") so it\\'s clear that it has applied to the document', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a gallery or a Link inspector\\n3.Edit something and close the inspector, this will make the save page button disabled\\n\\n4.Now again reopen that inspector and make further changes but do not close the inspectors .\\n\\n5.Click on the already active \"Save Page\" button\\n\\nObserved Result:\\nThe modified content of step 4 also gets saved even though user did not close the inspector to save it.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/24thmarchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401996119, 'spacePHID': None, 'dateCreated': 1395706620, 'dateModified': 1417572288, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63050', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cite options are appearing as empty dialog on a new empty page for some time', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a new page with VE\\n2.On this empty page select any option under Cite \\n\\nObserved Result:\\n\\nThe dialog box for cite options are appearing as empty dialog box \\nAfter a long time , the required parameters for Cite options appear\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Another24Marchrome&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F13128}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401418651, 'spacePHID': None, 'dateCreated': 1395702600, 'dateModified': 1443276245, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63042', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Launching a citation within a reference (rather than directly in a surface) fails to set up the dialog correctly (no TemplateData, brokenness).', 'description': {'raw': 'Without any required parameters\\n\\nSteps to reproduce:\\n\\n\\n1,Open a page with VE\\n2.Insert a reference\\n3.Open the reference dialog box select any option under Cite (Website/Book/Newspaper/Journal)\\n\\nObserve Result:\\nNone of the required parameters are showing up , in all cases the dialog to add a transclusion comes up.\\n\\n\\nSee the screenshot attached\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Another24Marchrome&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13118}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395874318, 'spacePHID': None, 'dateCreated': 1395701400, 'dateModified': 1443276245, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63037', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf20] Uncaught TypeError: Cannot read property 'keyedNodes' of undefined  appears while adding a reference in the page and makes VE unresponsive\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a reference\\n\\nObserved Result:\\n\\nUncaught TypeError: Cannot read property 'keyedNodes' of undefined appears in the console and VE gets unresponsive\\n\\nSee the screenshot attached.\\n \\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage: http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13105}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395701274, 'spacePHID': None, 'dateCreated': 1395697140, 'dateModified': 1443276245, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63031', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf20] Keyboard shortcut page is unformatted', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\nJust open the Keyboard shortcut page\\n\\nObserved Result: See the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13057}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '0', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395873768, 'spacePHID': None, 'dateCreated': 1395683880, 'dateModified': 1497374964, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63018', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression pre-wmf20] TOC widget doesn't tear itself down correctly, throws Cannot call method 'teardown' of undefined while trying to save a page on Betalabs\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a text\\n3.Try to Save the page\\n\\n\\nObserved Result:\\nAn error appears : Uncaught TypeError: Cannot call method 'teardown' of undefined\\nThe page seems to be in readmode but the cursor still appears on the page\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Toc_issue\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12876}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395434066, 'spacePHID': None, 'dateCreated': 1395424800, 'dateModified': 1467408119, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62934', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set up an IRC bot in #mediawiki-visualeditor to report visualeditor-needcheck edits on WMF wikis', 'description': {'raw': \"This will alert us to things going wrong quickly. Hopefully. (Yes, there's a risk of noise, but there should be 0 of these, anyway.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406140592, 'spacePHID': None, 'dateCreated': 1395281460, 'dateModified': 1443278199, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62860', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Template tabbing is odd in Firefox (loses focus between parameters?)', 'description': {'raw': 'Intention:\\nTab through the fields in a pre-existing infobox\\n\\nSteps to Reproduce:\\n1. In Firefox 27, open a page that contains an infobox.\\n\\n2. The cursor is (should be) in the first parameter, which should light up with a blue border.  Press the tab key. \\n\\n3. Where is the cursor now?\\n\\n4. Repeat.\\n\\n\\nBonus:  When you get nearly to the end of the template, use the mouse or arrow keys to click back in the first parameter.  Press tab.  The cursor should be in parameter #2, but sometimes it goes to the parameter after your pre-click location.\\n\\nActual Results:  \\nYou sometimes have to tab twice to get from parameter #1 to parameter #2.  If you do, then select-all from the keyboard will select the TemplateData descriptions.\\n\\n\\nReproducible: Sometimes\\n\\nI was unable to reproduce this in Safari.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397671011, 'spacePHID': None, 'dateCreated': 1395248040, 'dateModified': 1443276249, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62841', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <a rel=\"mw:WikiLink\" href=\"Foo\" ></a> shouldn\\'t ever be sent to Parsoid.', 'description': {'raw': 'From bug 50945#c3\\n\\n| However my testing showed that this was not reliable and sometimes resulted\\n| in odd wikicode, e.g. [[Ecuador|<nowiki/>]][[Egypt|E]][[Egypt|gypt]] when\\n| changing \"Ecudor\" to \"Egypt\".\\n| \\n| See https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&diff=563097916&oldid=563090562\\n\\n<p><a rel=\"mw:WikiLink\" href=\"./Ecuador\" ></a><a rel=\"mw:WikiLink\" href=\"./Egypt\">E</a><a rel=\"mw:WikiLink\" href=\"./Egypt\">gypt</a></p>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395196643, 'spacePHID': None, 'dateCreated': 1395196560, 'dateModified': 1443276249, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62819', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link inspector doesn't save changes when closing while XHR is pending\", 'description': {'raw': 'Introduce artificial delays in your API modules (sleep(2); at the top of ApiOpenSearch::execute() and ApiQueryInfo::execute(); alternatively, you can try this in production if you\\'re quick enough), then perform the following steps quickly:\\n\\n1. Inspect an existing link\\n2. Change its target\\n3. Before the API request completes, close the link inspector by clicking out or clicking the back arrow\\n4. Inspect the link again\\n\\nExpected: new target shows in inspector\\nActual: old target shows\\n\\nWith the keyboard it\\'s even weirder:\\n\\n1. Inspect an existing link\\n2. Type \"foo\". Wait for the API request to come back and display suggestions\\n3. Type \"bar\" at the end (so you now have \"foobar\"), then quickly (before the API call comes back) press Enter.\\n4. Expected: inspector closes. Actual: input value is reset to \"foo\"\\n(At least if you press Enter again, \"foo\" is actually saved.)\\n\\nYou can work around this and still reproduce the first bug:\\n\\n1. Inspect an existing link\\n2. Type \"foo\"\\n3. If a suggestion box is displayed (perhaps because \"f\" was in cache, or because the previous value was in cache), press Esc to dismiss it\\n4. Press Enter, the inspector closes\\n5. Inspect the link again\\n\\nExpected: \"foo\"\\nActual: previous value\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402548960, 'spacePHID': None, 'dateCreated': 1395195780, 'dateModified': 1441911960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62818', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: setResizableHandlesSizeAndPosition() shouldn't measure things on every keypress\", 'description': {'raw': \"In afterDocumentKeyPress, setResizableHandlesSizeAndPosition() is called and measures and repositions all ResizableNode resize handles, even though they're not even visible. This is wasteful.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412588928, 'spacePHID': None, 'dateCreated': 1395188760, 'dateModified': 1443278200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62812', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting a formula into a block slug throws \"Uncaught TypeError: Cannot call method \\'update\\' of null\" and inserts empty formula', 'description': {'raw': \"The error\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE which has slug in it\\n2.Place your cursor in the slug and open the math inspector\\n3.Now type something inside the math inspector\\n\\n\\nObserved Issue 1: \\nIt throws an error:\\nCannot call method 'update' of null\\n\\nAnd if you insert the math function and save the page and then go to edit source , you will see an empty math rag has also been added to the page\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:RYasmeen_(WMF)&action=edit\\n\\nSee the screenshots attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58286\\n\\n**Attached**: {F13147}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397704103, 'spacePHID': None, 'dateCreated': 1395166680, 'dateModified': 1417572485, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62797', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Long target names no longer get shortened in the link inspector', 'description': {'raw': 'Steps to reproduce:\\n\\n- go to http://en.wikipedia.beta.wmflabs.org/wiki/Snail\\n- edit the page with visual editor\\n- highlight text \"animal\"\\n- click Hyperlink tool\\n- paste http://en.wikipedia.beta.wmflabs.org/wiki/Animal into Hyperlink tool\\n- the link goes out of Hyperlink tool box (see attached screen shot)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401468546, 'spacePHID': None, 'dateCreated': 1395164040, 'dateModified': 1443276249, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62796', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The style of error message for invalid page title for link should be more apparent in style', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the link inspector \\n3.Now enter something invalid for link inspector , for example: File:Joo Chiat Place.jpg|Item 1\\n\\nObserved Result:\\n\\nAn error message appears for invalid page title , the style of the error message should be much more apparent like red \\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13049}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-or5bjqrmvxl6rczurt2w', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416054736, 'spacePHID': None, 'dateCreated': 1395097740, 'dateModified': 1443278202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62761', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Drag and drop inserted the relocatable node image marker as a data:image/gif;base64 string', 'description': {'raw': \"I don't know how the user did that, but take a look at this edit:\\nhttps://pt.wikipedia.org/wiki/Esporte_Clube_Pelotas?diff=38422037\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404421306, 'spacePHID': None, 'dateCreated': 1395063660, 'dateModified': 1417572124, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62728', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The message that appears while adding a template with no description should use the readable form of template name', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Transclusion\\n3.Insert a template that does not have any description.\\n4.For example: Country showdata for betalabs\\n\\nObserved Result:\\nA message comes up :You are adding the \"Country_showdata\" template to this page. It doesn\\'t yet have a description, but there might be some information on the template\\'s page.\\n\\nIn this message , the template name used should be in more readable form that is with underscores: Country showdata\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/User:RYasmeen_(WMF)?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F12888}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401475141, 'spacePHID': None, 'dateCreated': 1394836500, 'dateModified': 1443278202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62679', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing tab on a slug throws error \"Cannot call method \\'getParent\\' of null\" and does not go to the next line or next item', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Place the cursor in a slug\\n3.Press tab\\n\\nObserved Result:\\nAn error appears in the console:\\nUncaught TypeError: Cannot call method 'getParent' of null\\nve.Document.getCoveredSiblingGroups\\nve.ui.IndentationAction.increase\\nve.ui.Surface.execute\\nve.ui.Command.execute\\nve.ui.Surface.execute\\nve.ce.Surface.onDocumentKeyDown\\nproxy load.php:10\\nve.EventSequencer.onEvent\\n(anonymous function)\\njQuery.event.dispatch load.php:45\\nelemData.handle.eventHandle\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12844}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395076580, 'spacePHID': None, 'dateCreated': 1394827800, 'dateModified': 1443276252, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62657', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspector flickers and flashes continuously when resizing window', 'description': {'raw': 'When resizing the window with an inspector open, it continuously flickers and flashes blank, sometimes making a slow, fast or partial fade in/out, others when you let go of the resize handle it does a bunch of flashes in burst (as if they were queued up).\\n\\nScreen capture: http://cl.ly/0g2F0q2D3p1D\\n\\nSeems to relate to code that adds/removes the \"oo-ui-popupWidget-transitioning\" class.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397763968, 'spacePHID': None, 'dateCreated': 1394758800, 'dateModified': 1443276252, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62632', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Problem with getMobileToken in MobileContext causing browser tests to fail', 'description': {'raw': 'Seen often in browser tests run locally and on Cloudbees, this happens: \\n\\n\\n* default status of Beta toggle is OFF\\n* click Beta toggle to ON\\n* click Save\\n\\n* get error: \"Error saving settings. Please make sure that you have cookies enabled\"\\n\\n* Beta toggle goes back to OFF\\n* test fails\\n\\n\\nI have not yet triggered this manually. (but I haven\\'t tried that hard either)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400253495, 'spacePHID': None, 'dateCreated': 1394741760, 'dateModified': 1400253495, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62614', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf18] Moving default-sized image position from left to right makes image full sized', 'description': {'raw': 'After moving the image\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a thumbnail image\\n3.Move the image from Right to left\\n4.Again move the image from right to left\\n\\nObserved Result:\\nMoving the image from Left to Right or Right to Left changes the size of the image in the VE mode\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Test_62581?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13293}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394752079, 'spacePHID': None, 'dateCreated': 1394663460, 'dateModified': 1443276255, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62586', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection after deleting block focusablenode (e.g. image) is weird', 'description': {'raw': '1. Edit a document containing a block image\\n2. Click on the block image\\n3. Press delete\\n4. The selection looks odd\\n\\nInspection of the DM selection shows that it now covers [/paragraph, paragraph].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407064881, 'spacePHID': None, 'dateCreated': 1394658780, 'dateModified': 1417571953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62579', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Up and down cursor keys don't let you cursor from a focusable node into a slug\", 'description': {'raw': \"Intention:\\nEdit https://www.mediawiki.org/wiki/Sandbox\\n\\nSteps to Reproduce:\\n1. Click on https://www.mediawiki.org/wiki/Sandbox?veaction=edit\\n\\n2. Press down arrow key.  Nothing happens.\\n\\n3. Press up arrow key.  Nothing happens.\\n\\n4.  Huh, how do I get off this template?\\n\\nActual Results:  \\nLeft and right arrow keys take me to the slugs on either side, so why don't up and down arrow keys do the same?\\n\\nIn my brief testing, this doesn't happen if there is an infobox and text on the page.  https://www.mediawiki.org/wiki/Sandbox is the only page that I'm sure it always happens on.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://www.mediawiki.org/wiki/Sandbox?veaction=edit\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57477\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1423763282, 'spacePHID': None, 'dateCreated': 1394560560, 'dateModified': 1426989552, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62542', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link input widget sometimes picks wrong link target', 'description': {'raw': 'Use the VisualEditor to edit an article on mediawiki.org, enter the word \"bugzilla\" and turn it into a link (highlight, Ctrl-K). The link input widget proposes a list of link targets, starting with \"bugzilla\" (checked), \"Bugzilla/Notes/4198\" and \"Bugzilla\". Click on the third one (\"Bugzilla\"). With quick eyes, you will notice that \"Bugzilla/Notes/4198\" is checked instead, but the list disappears immediately and the target box contains the string \"Bugzilla\". It appears as if the desired \"Bugzilla\" had been accepted as link target. Close the link input widget and preview your changes: \"Bugzilla/Notes/4198\" is used as link target.\\n\\nAnother instance:\\n\\nGo to https://en.wikipedia.org/wiki/War?veaction=edit and turn the word \"integral\" in the second paragraph into a link. The link input widget proposes a list of link targets, starting with \"integral\" (checked), \"Integral domain\" and \"Integral\". Click on the third one (\"Integral\"). With quick eyes, you will notice that \"Integral domain\" is checked instead, but the list disappears immediately. It then appears as if the desired \"Integral\" had been accepted as link target. Close the link input widget and preview your changes: \"Integral domain\" is used as link target.\\n\\nIt\\'s likely that these cases won\\'t be reproducible for long since the suggested target list is highly dependent on the respective wiki\\'s current set of articles.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402551024, 'spacePHID': None, 'dateCreated': 1394469360, 'dateModified': 1441911966, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62492', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit notices widget should clip correctly and have a max height', 'description': {'raw': \"https://he.wikipedia.org/wiki/%D7%9E%D7%93%D7%99%D7%94_%D7%95%D7%99%D7%A7Sandbox?veaction=edit as an anon yields to edit notices which together are way taller than the screen, which produces really weird behavior where you can't scroll to reach the bottom part of the edit notices.\\n\\nEither the edit notices widget should be a ClippableElement, or it should have a max height and scroll beyond that (or both).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397067550, 'spacePHID': None, 'dateCreated': 1394231940, 'dateModified': 1417572493, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62408', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The \"Insert reference\" button remains enabled in the reference dialog even if it is empty', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Reference\\n3.Click on \"Apply Changes\" without inserting any content for the reference\\n\\nObserved Result:\\nThe empty reference gets added in the page and after saving it shows the error message:Cite error: Invalid <ref> tag; refs with no content must have a name; see the help page ().\\n\\nExpected Result:\\n\\nThe \"Apply Changes\" button should remain disabled unless user enters any content for the reference \\n\\nSee the screenshot attached.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nhttp://en.wikipedia.beta.wmflabs.org/wiki/7thmarchrome\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12857}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401479536, 'spacePHID': None, 'dateCreated': 1394219880, 'dateModified': 1417572294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62399', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Backwards cursoring of an image inside an image's caption selects the sub-image, not the main image (and then breaks nastily)\", 'description': {'raw': 'Intention:\\nDelete an image.\\n\\nSteps to Reproduce:\\n1. Click on http://en.wikipedia.beta.wmflabs.org/w/index.php?oldid=82527&veaction=edit\\n\\n2. Place cursor inside the ==Referenced text== section heading.\\n\\n3. Press the forward arrow key a few times.  At the end of the line, you\\'ll select the entire image-and-image-containing-caption block.  Forward-arrow once more, and you\\'ll end up in the first paragraph.  (This is all expected behavior.) \\n\\n4. If necessary, place your cursor in the first sentence after the ==Referenced text== section heading.\\n\\n5.  Press the back arrow key a few times.  This selects only the image that is inside the caption, not the entire two-image block.  You can remove the second image or change the caption for the first image (only) while your cursor is there.  If you keep back-arrowing, you\\'ll eventually select the whole block, and then end up in the ==Referenced text== section heading. \\n\\n\\nExpected Results:  \\nI expected forward- and backward- arrows to produce the same results.\\n\\nI like the \"backward\" result better.  Why not make it possible to edit captions simply by placing the cursor in the caption (either by clicking the caption [instead of the image] or with the keyboard)?\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413329674, 'spacePHID': None, 'dateCreated': 1394217540, 'dateModified': 1424894574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62395', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"If VisualEditor is open, it should be considered 'alreadyediting'\", 'description': {'raw': \"We deliberately don't show a CTA if they're already editing.  However, this is broken if they're editing with VE.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399319230, 'spacePHID': None, 'dateCreated': 1394158500, 'dateModified': 1399319230, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62357', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When an image has a full size which is smaller than the default size, it does not set the default size to the value of full size', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add an image which has an full size less than the default size for example: http://en.wikipedia.beta.wmflabs.org/wiki/File:FS_barnstar.png\\nIt has a full size of 111x107 px which is less than the default size 220x212 px\\n\\n3.Now if you switch to set to custom size , it will show Size values are invalid as it is larger than the full size.\\n\\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Betachrome5th?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13258}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400701822, 'spacePHID': None, 'dateCreated': 1394065020, 'dateModified': 1443278202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62293', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Too many draggable image resizing handlers for frameless, frame, and basic images (thumbnails working as intended)', 'description': {'raw': 'VisualEditor screenshot, showing number of image resizing handles in frameless vs thumb\\n\\nMay be related to bug 62139.\\n\\n1.  Open a right-aligned image in VisualEditor.  Set to \"thumb\".  Count image resizing handlers (answer:  1).\\n\\n2.  Change image to \"frameless\".  Count image resizing handlers (answer:  4).\\n\\nI believe this also happens in \"frame\" and \"basic\", but it\\'s a little hard to tell because of another bug (that sets them to full size).\\n\\nIt would make more sense to only have one handle for this situation.  Two (on the two lower corners) might make sense for centered images.  Probably nothing should have a handle on the top corners.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13223}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404850803, 'spacePHID': None, 'dateCreated': 1394057940, 'dateModified': 1424894573, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62283', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf17] Please round image sizes to whole numbers', 'description': {'raw': 'Wikitext code:  [[File:Hedrick (1921) - Bartlett.jpg|thumb|Caption]]\\n\\nOriginal image dimensions:  920 × 1,216 pixels.\\n\\nVisualEditor says:  166.32302405498282 × 220 pixels.\\n\\n\\nPlease round to whole numbers of pixels.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394488013, 'spacePHID': None, 'dateCreated': 1394056320, 'dateModified': 1443276262, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62279', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Uncaught TypeError: Cannot call method 'getChildren' of null appears while going to a newline after deleting an image\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Now select the image and delete it\\n4.Go to the next line by pressing enter\\n\\nObserved Result:\\n\\n\\nThe following error appears in the console:\\n\\n\\nUncaught TypeError: Cannot call method 'getChildren' of null \\nUncaught TypeError: Cannot call method 'getChildren' of null load.php:269\\nve.ce.Surface.handleEnter load.php:269\\nve.ce.Surface.onDocumentKeyDown load.php:247\\nproxy load.php:10\\nve.EventSequencer.onEvent load.php:21\\n(anonymous function) load.php:20\\njQuery.event.dispatch load.php:45\\nelemData.handle.eventHandle\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13081}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394659801, 'spacePHID': None, 'dateCreated': 1393974060, 'dateModified': 1443276262, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62235', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector dirties links, causes dirty diffs for links with underscores', 'description': {'raw': 'Edit a page with wikitext [[User:Trevor_Parscal|Trevor Parscal]] ([[User talk:Trevor_Parscal|talk]]). Inspect the second link (\"talk\"), wait for the suggestions to load, then click out of the inspector. The save button activates. Click the save button and review the diff, and you\\'ll see that the underscore in the link target went away.\\n\\nLooking at the DM transaction history, the link was replaced with a newly generated annotation that doesn\\'t have htmlAttributes and doesn\\'t have origTitle or any of the orig* attributes.\\n\\nFor whatever reason, this bug doesn\\'t happen for the first link. Maybe it\\'s because only the second link has a namespace prefix that contains a space?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/User:Catrope/Bug_62229'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400719999, 'spacePHID': None, 'dateCreated': 1393966320, 'dateModified': 1441911973, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62229', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression-pre-wmf17] Styling on \"New Page\" and \"Matching Pages\" messages inside Link Inspector missing', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Now type something and open a link inspector over it\\n\\nObserved Result:\\n\\nThe \"New Page\" and \"Matching Pages\" messages are not greyed out inside Link Inspector rather appearing in a more apparent style\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13045}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394068465, 'spacePHID': None, 'dateCreated': 1393963860, 'dateModified': 1443276265, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62226', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Provide information about preferred formatting of transclusions', 'description': {'raw': \"For the serialization of new transclusions we'd like to have information about the preferred formatting from TemplateData:\\n\\n* all parameters on a single line vs. one parameter per line\\n* (possibly) preferred order of parameters by key\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-cfsvvgbtlqnbt2yokfjf', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1445276384, 'spacePHID': None, 'dateCreated': 1393951920, 'dateModified': 1445276400, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62217', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf16] Getting  \"Your edit may have been corrupted – please review before saving\" message when page contains gallery/formula', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\nYet Unknown.I am getting it by following no specific steps.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12939}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394223289, 'spacePHID': None, 'dateCreated': 1393890420, 'dateModified': 1443276265, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62172', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression]: VisualEditor broken on private wikis', 'description': {'raw': \"#1 Go to https://office.wikimedia.org/wiki/HR_Corner/Massage_Signups#Standby_list\\n#2 Click edit\\n\\nNotice how you get a 'Error loading data from server: parsoidserver-http-curl-error: Couldn't resolve host 'HR_Corner%2FMassage_Signups'\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-qmantxp3p7omhisp3qgq', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393965639, 'spacePHID': None, 'dateCreated': 1393887000, 'dateModified': 1393965639, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression-pre-1.23wmf17] Cannot select input boxes inside dialogs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Go to Options>Categories\\n3.Try to add a category to the page\\n\\nObserved Result:\\nCannot place the cursor in the Add a category text box and cannot add a category\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8\\nPage: http://en.wikipedia.beta.wmflabs.org/wiki/Newpage3rdfeb?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n\\n**Attached**: {F12924}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393889696, 'spacePHID': None, 'dateCreated': 1393880460, 'dateModified': 1443276265, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62163', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Changing a media item type from \"thumbnail\" to \"frame\" doesn\\'t hide the zoom icon', 'description': {'raw': '1. \"frame\" thinks you can set a size other than original size, you can\\'t\\n2. changing from \"thumbnail\" to \"frame\" doesn\\'t hide the zoom icon\\n3. changing from \"thumbnail\" or \"frame\" to border doesn\\'t collapse the border\\n4. \"border\" images come up as inline so can\\'t be edited, even though you can convert to border from a block image\\n\\nI\\'m concerned we\\'re merging features before they\\'re ready. We should consider rolling back features that don\\'t fully work yet at is looks like there\\'s a lot still to do.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394486418, 'spacePHID': None, 'dateCreated': 1393851360, 'dateModified': 1443276266, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62139', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Undoing creation of empty heading places cursor at invalid offset', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Create a heading\\n3.Undo creating the heading and type something in that line instead\\n4.Press enter\\n\\nObserved Result:\\nUncaught Error: Inserted data is trying to close the root node (at index 0) is appearing in the console.\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Test62015&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13363}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394056180, 'spacePHID': None, 'dateCreated': 1393636920, 'dateModified': 1443276268, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62088', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf16] Floated images of type \"none\" display as only a couple of pixels wide, not full-size', 'description': {'raw': 'Steps to Reproduce:\\n1. Open the page:  http://en.wikipedia.beta.wmflabs.org/w/index.php?oldid=81526&veaction=edit\\n\\n2. Scroll down to the image of an apple.\\n\\n3. Why is it barely visible?\\n\\n\\n\\nReproducible: Always\\n\\nThis happens in both Safari and Firefox, but only at beta.wmflabs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: http://en.wikipedia.beta.wmflabs.org/w/index.php?oldid=81526&veaction=edit'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394066773, 'spacePHID': None, 'dateCreated': 1393527000, 'dateModified': 1443276271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62013', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add media does not search local repo when MW is in root', 'description': {'raw': '**Author:** `robert.labrie`\\n\\n**Description:**\\nIntention:\\nAdd media with visual editor\\n\\nSteps to Reproduce:\\nLocalSettings.php and wiresharks are attached. The MW search does work. I can do a partial name search for an image in the File namespace and it works. The gallery in mediawiki does not.\\n\\nActual Results:  \\nNo images\\n\\nExpected Results:  \\nImages\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394727592, 'spacePHID': None, 'dateCreated': 1393522440, 'dateModified': 1417572574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62007', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create relocatable markers for complex shapes, e.g. block templates', 'description': {'raw': \"Right now you can re-position an inline transclusion in the same way as images, with a click-drag feature. Unfortunately this isn't set for block transclusions.\\n\\nThis is particularly irritating for suers because when you initially insert a transclusion we assume it's inline, so let them move it, but then when they re-open the page it's now magically un-moveable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408650245, 'spacePHID': None, 'dateCreated': 1393521720, 'dateModified': 1443278205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62006', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Image can be resized down beyond 1x1px where user can no more find the image and Media Settings icon for it', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image \\n3.Make it frameless\\n4.Keep on resizing down the image going beyond 1x1 px.\\n5.Click anywhere on the page\\n\\nObserved Result:\\n\\nThe image becomes a dot size . and user can no more select or find Media Settings icon for it.\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13101}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394062463, 'spacePHID': None, 'dateCreated': 1393459860, 'dateModified': 1443276271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61973', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Use an Existing Reference\" button becomes disabled for the current session once user inputs an invalid search term for searching existing references', 'description': {'raw': 'Invalid input\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which has multiple references\\n2.Go to Insert>Reference>Use an existing reference\\n3.Now input something in the search box which will have no search result\\n4.Now cross out the dialog box\\n5.Again go to Insert>Reference\\n\\nObserved Result:\\nThe \"Use an existing reference\" button is disabled and it does not become enabled for the rest of the session unless user cancels the edit and reopen the page again with VE\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit\\n\\nSee the screenshots attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13055}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395294582, 'spacePHID': None, 'dateCreated': 1393448280, 'dateModified': 1443276272, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61960', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Breaking words on diacritics', 'description': {'raw': 'VisualEditor breaking words on diacritics\\n\\nA user was trying to remove the duplicated header which is on section \"Propriedades Algébricas\" of\\nhttps://pt.wikipedia.org/wiki/Logaritmo?oldid=38172637&veaction=edit\\n\\nAfter deleting the duplicated cells, Visual Editor also removes part of a word from the previous paragraph.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://pt.wikipedia.org/w/index.php?title=Logaritmo&diff=38264880&oldid=38264877\\n\\n**Attached**: {F13042}'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408983921, 'spacePHID': None, 'dateCreated': 1393436040, 'dateModified': 1417571933, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61955', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Move EventLogging component from MediaWiki extensions product to Analytics product', 'description': {'raw': 'Move EventLogging component from MediaWiki extensions product to Analytics product, as requested via email.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393419433, 'spacePHID': None, 'dateCreated': 1393417560, 'dateModified': 1393562778, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61946', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ApiQueryLogEvents STRAIGHT_JOIN queries slow', 'description': {'raw': 'enwiki has been seeing a bunch of slow ApiQueryLogEvents queries:\\n\\nSELECT /* ApiQueryLogEvents::execute */ /*! STRAIGHT_JOIN */ log_type, log_action, log_timestamp, log_deleted, log_id, page_id, log_user, log_user_text, user_name, log_namespace, log_title, log_comment, log_params FROM `logging` LEFT JOIN `user` ON ((user_id=log_user)) LEFT JOIN `page` ON ((log_namespace=page_namespace) AND (log_title=page_title)) INNER JOIN `change_tag` ON ((log_id=ct_log_id)) WHERE (log_type != \\'suppress\\') AND ct_tag = \\'Possible self promotion in userspace\\' ORDER BY log_timestamp DESC LIMIT 11\\n\\nSELECT /* ApiQueryLogEvents::execute */ /*! STRAIGHT_JOIN */ log_type, log_action, log_timestamp, log_deleted, log_namespace, log_title, ts_tags FROM `logging` LEFT JOIN `user` ON ((user_id=log_user)) LEFT JOIN `page` ON ((log_namespace=page_namespace) AND (log_title=page_title)) LEFT JOIN `tag_summary` ON ((log_id=ts_log_id)) INNER JOIN `change_tag` ON ((log_id=ct_log_id)) WHERE (log_type != \\'suppress\\') AND ct_tag = \\'VisualEditor\\' ORDER BY log_timestamp DESC LIMIT 11\\n\\n... and several other similar forms.\\n\\nIn all cases the STRAIGHT_JOIN forces an index scan on logging.times index, or more rarely a range access on logging.type_time index. Both query plans hit tens of millions of rows and take many minutes.\\n\\nRemoving the STRAIGHT_JOIN allows the MariaDB query optimizer to choose a plan that takes seconds. Often it includes a filesort step, but more importantly it allows \"index condition pushdown\" which makes the filesort cheap.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-lxluxbieyr4tgfyp5jru', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393375821, 'spacePHID': None, 'dateCreated': 1393296960, 'dateModified': 1602870079, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61889', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding a reflist while selecting an image does not add anything new in the page but the \"Save Page\" button becomes active', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which contains an image\\n2.Select the image\\n3.Go to Insert>References List\\n\\nObserved Result:\\nThe Save page button becomes active though there is no new reflist got added.If you click on \"Review Your Changes\" on the Save Dialog box, it will say \\n\"Could not start the review because your revision matches the latest version of this page\"\\n\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage: http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12904}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397504895, 'spacePHID': None, 'dateCreated': 1393288440, 'dateModified': 1443276274, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61885', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Don't set STATICREDIRECT if there's no redirect on the page\", 'description': {'raw': \"Steps to reproduce:\\n1.  Start with a blank page.\\n\\n2.  Go to Page settings.\\n\\n3.  Tick both redirect-related boxes, but don't provide a page name.\\n\\n4.  Apply changes.\\n\\n\\nResults:\\nIt sets __STATICREDIRECT__, which is not pointful on an otherwise blank page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61864\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393281933, 'spacePHID': None, 'dateCreated': 1393271280, 'dateModified': 1443276275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61865', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Disable the redirect input field unless the checkbox is checked', 'description': {'raw': 'In the \"Page settings\" dialog, it says \"Redirect this page to\" and a blank field for the target name.  If you put a name in there, then it sets a redirect, even if you don\\'t tick the checkbox.  \\n\\nVisualEditor should automatically tick the checkbox there if it\\'s going to set a redirect (e.g., as soon as you start typing).  Otherwise, it looks like it\\'s not going to redirect the page when you exit the dialog box.\\n\\n(Reproducing this has only been consistent if there is no redirect on the page at the start of the editing session.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61865'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393281938, 'spacePHID': None, 'dateCreated': 1393270920, 'dateModified': 1443276275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61864', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Reference names fixed when reference not altered but new reference added on particular page (and others?)', 'description': {'raw': 'Intention:\\nAdd one ref\\n\\nSteps to Reproduce:\\n1. Opened an existing ref, copied the contents, and cancelled out of the dialog.\\n\\n2. Opened a new ref, pasted what I\\'d just copied, changed the contents slightly, and applied changes.\\n\\n\\nActual Results:  \\nAll the <ref name = whatever> tags on the page were \"corrected\".\\n\\nExpected Results:  \\nNothing would change in paragraphs that I didn\\'t touch.\\n\\nReproducible: Didn\\'t try\\n\\nThis is presumably a regression, but search couldn\\'t find any bugs containing the word \"name\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=912199&oldid=840682'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393355731, 'spacePHID': None, 'dateCreated': 1393017180, 'dateModified': 1417572652, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61775', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If the edit summary is empty, don\\'t show a preview of it (\"()\") in the Review Changes panel', 'description': {'raw': 'Screenshot\\n\\nDo no Show empty summary preview: () when there is no summary in Review Changes dialog box\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13076}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393084678, 'spacePHID': None, 'dateCreated': 1392940980, 'dateModified': 1443276278, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61716', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copy/pasting blanks page, prevents saving', 'description': {'raw': 'Reported on fr.wp:\\n<<Here is how I did : on the page https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Ch%C3%A2teau_Rothschild_(Boulogne-Billancourt) opened with VE, \"Historique\" section, copy from \"Joseph Fleuriau d\\'Armenonville\" to \"évoqua brièvement le lieu.\" Then paste it somewhere on the page https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Brouillon [it\\'s a sandbox, it\\'s ok to test there], and everything will be deleted. \\nI also noticed that a few times nothing was deleted but nothing was pasted too. [...]\\nI have the same bug with FF 29 with both W7 and W8.1, and also Chrome 32 with W7. Nemesis III (me contacter), le 19 février 2014 à 19:16 (CET). >>\\n\\nI reproduced this as well.\\nIn addition, the first time it didn\\'t blank the destination page, and the same happened on one of my sandboxes. Then one time it blanked the page, allowed me to save, I got the confirmation message but nothing was recorded (the history doesn\\'t have signs of this).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409237174, 'spacePHID': None, 'dateCreated': 1392835080, 'dateModified': 1439679946, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61552', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Shift-selection of a template and then typing-replacement can cause pawns in Firefox', 'description': {'raw': 'VEdit https://fr.wikipedia.org/wiki/Utilisateur:Elitre_(WMF)/Prove2?veaction=edit in Firefox.\\n\\nPlace your cursor right below the initial template, press Shift and the Up arrow to select it, type something = pawn.\\n\\nNicoV, who found this, says you can also start from the line above the template, Shift + Down arrow in that case.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58675\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54917'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406598517, 'spacePHID': None, 'dateCreated': 1392821340, 'dateModified': 1443278206, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61538', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding a left aligned image just before the reflist distorts the position of reflist and \"Cannot call method \\'getModel\\' of null \" appears while trying to fix it by pressing return', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Add a text with reference\\n3.Add a reflist\\n4.Go to the next line of the text with reference and add an image\\n5.Go to the Media settings of the image and set the alignment to left(This should move the image between reference and reflist , instead it distorts the reflist position and it appears just beside the image instead of appearing below it)\\n6.Save the page\\n7.Reopen the page\\n8.Try to the position of reflist it by pressing enter \\n\\nObserved Result:\\nNo newline gets entered , an error appears in the console:\\nUncaught TypeError: Cannot call method 'getModel' of null \\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Anotherdeep?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13298}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393474403, 'spacePHID': None, 'dateCreated': 1392770580, 'dateModified': 1417572588, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61525', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn ♙ appears after deleting the text preceding and following a link by \"undo\" action', 'description': {'raw': 'pawn before the link\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Create a link\\n3.Type something just before the link\\n4.Type something just after the link\\n4.Click on \"Undo\" several times\\n\\nObserved Result:\\n\\nA pawn appears right before and after the link \\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=18thfebchrome\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13288}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421282613, 'spacePHID': None, 'dateCreated': 1392762420, 'dateModified': 1438734956, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61521', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Moving templates down is broken', 'description': {'raw': '1. Go to template dialog\\n2. Insert two templates (or a template and a content item, or whatever)\\n3. Click the bottom one and click the up arrow to move it up; this works\\n4. Click the top one and click the down arrow; nothing happens\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394073109, 'spacePHID': None, 'dateCreated': 1392420840, 'dateModified': 1443276281, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61402', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Box for alt text in the media dialog is too small', 'description': {'raw': 'This is related to bug 38129.\\n\\nThe alt text box in the media dialog is only about two-thirds the width of the screen, with no possibility of wrapping/scrolling down.  Maybe eight words fit in it (two-thirds of the example given in the lead of https://en.wikipedia.org/wiki/WP:ALT).  \\n\\nIt should be at least the normal width of the dialog.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392861666, 'spacePHID': None, 'dateCreated': 1392317880, 'dateModified': 1443276283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61329', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Don't specify the default alignment for images (in the resulting wikitext)\", 'description': {'raw': 'This is related to bug 51293, bug 61323, and the general bug 38129:\\n\\nThe alignment options in the media dialog\\'s advanced settings are:\\n\\nLeft\\nCenter\\nRight\\nNone\\n\\nIt is the convention to not specify the alignment when choosing the default, mostly to avoid needless clutter in the wikitext.  If the default is right (or left), and the user chooses that default, then VisualEditor should not add \"right\" but instead should leave the alignment setting empty.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393446964, 'spacePHID': None, 'dateCreated': 1392315180, 'dateModified': 1443276284, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61324', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Provide a button in the image dialog box\\'s advanced settings to set \"default\" alignment for images', 'description': {'raw': 'This is related to bug 51293 and the general bug 38129:\\n\\nThe alignment options in the media dialog\\'s advanced settings are:\\n\\nLeft\\nCenter\\nRight\\nNone\\n\\nThese are the four explicit settings provided in MediaWiki.\\n\\nMost users, even if they click on a few buttons to consider other options, are going to want the image at the default (i.e., on the right for left-to-right languages).  It is the convention to not specify the default, mostly to avoid needless clutter in the wikitext.\\n\\nMost users have no idea what \"None\" does because they\\'ve never encountered it before.  They\\'re going to think that it means \"unspecified default\", rather than left-and-clear.  \\n\\nIt would be good to offer a \"default\" button, even though this duplicates the function of one of the existing buttons.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393446869, 'spacePHID': None, 'dateCreated': 1392315060, 'dateModified': 1443276287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61323', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Make parameters' entry expand to their contents, so lengthy parameter content isn't obscured\", 'description': {'raw': 'Actual Results:  \\nYou can only see about 1.5 lines of text.  It should be tall enough to display two lines of text, even if people are using slightly larger fonts.\\n\\n\\nReproducible: Always\\n\\nMultiple complaints with screenshots:\\n\\nhttps://en.wikipedia.org/wiki/File:Euromaidan_VisualEditor_infobox.PNG\\n\\nhttps://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_13#Multiple_issues_-_minimal_space\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60541'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393009160, 'spacePHID': None, 'dateCreated': 1392253440, 'dateModified': 1443276287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61289', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image size is shrinking to a dot size after exceeding a specific value while setting the image size', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open this page with VE:http://en.wikipedia.beta.wmflabs.org/wiki/12thfebchrome?veaction=edit\\n\\n2.Go to the Media Settings for the image:[[File:Dau ho thoi Ho.png]]\\n\\n3.Set the Width size of the image to 8000 and Apply changes (Works fine)\\n\\n4.Set the Width of the image to 8000000 and apply changes (Still work fine)\\n\\n\\n5.Set the Width of the image to 80000000 and Apply changes \\n\\nObserved Result:\\nThe image shrinks to a dot size in the VE mode\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13328}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404850639, 'spacePHID': None, 'dateCreated': 1392233220, 'dateModified': 1424894573, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61282', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace deletes characters, collapses references, moves cursor and inserts text somewhere else, and inserts snowmen', 'description': {'raw': 'Intention:\\nedit Polish Wikipedia using VisualEditor\\n\\nSteps to Reproduce:\\n1. difflink 1: https://pl.wikipedia.org/w/index.php?title=Amalowie&diff=38322555&oldid=38322515\\n2. difflink 2: https://pl.wikipedia.org/w/index.php?title=Amalowie&diff=prev&oldid=38322515\\n3. discussion link: https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Edytor_wizualny_psuje_przypisy\\n\\nActual Results:  \\nsnowmen appear (see difflink 1) and text disappears or \"gets eaten\"\\n\\nExpected Results:  \\nno snowmen and text is inserted where it is wanted\\n\\nReproducible: Didn\\'t try\\n\\nplease see bug:54712 and bug:54976 re: snowmen\\n\\nplease see bug:51624 and bug:50286 re: backspace\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://pl.wikipedia.org/wiki/Wikipedia:VisualEditor/Opinie#Edytor_wizualny_psuje_przypisy'}, 'authorPHID': 'PHID-USER-brn4v5ta45bnw4f5as3h', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395252569, 'spacePHID': None, 'dateCreated': 1392226980, 'dateModified': 1417572510, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61272', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar shifted to the left (currently in wmf13 and Beta Labs)', 'description': {'raw': \"Misaligned Undo/Re-do buttons at Beta Labs\\n\\nThe Undo/re-do buttons aren't lined up properly in the toolbar at Beta Labs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13192}\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392254120, 'spacePHID': None, 'dateCreated': 1392142980, 'dateModified': 1443276287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61224', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Link inspector prevents addition of section links to existing links', 'description': {'raw': 'Take text. Make link to page (\"Foo\"). Observe wikitext. Good.\\n\\nTake text. Make link to page with section (\"Foo#Bar\"). Observe wikitext. Bad.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392231577, 'spacePHID': None, 'dateCreated': 1392138660, 'dateModified': 1443276287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61221', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting border in Media Settings>Advanced Settings does not add any value to the image type field', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to Media Settings>Advanced Settings for that image\\n4.Select the option Border under Image Type\\n\\nObserved Result:\\nThere is no value/Change appears for this image type\\nThe resulting wikitext is:\\n[[File:Wheat (flo).JPG|200x200px||left]]\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=10thFeb&action=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394047158, 'spacePHID': None, 'dateCreated': 1392064020, 'dateModified': 1443276290, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61155', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Resize text in Option menu or put it on two lines if too long', 'description': {'raw': 'In French, the option to switch to wikitext is called \"Basculer vers la modification du code\". In Italian, it\\'s \"Passa alla modifica sorgente\".\\nIn both languages the text is so long you need to slide to the right to see all of it. Is there a better way to display it?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401743910, 'spacePHID': None, 'dateCreated': 1392060000, 'dateModified': 1417572291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61149', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Split VE into modules, and for Mobile only load the needed ones to reduce loading unnecessary JS & CSS', 'description': {'raw': \"In mobile various JavaScript and CSS modules are loaded that are not needed including OO JS UI.css (see https://gerrit.wikimedia.org/r/#/c/109940/)\\n\\nAfter talking to Trevor and Timo we agreed that it would be a good idea to refactor and break out many of VisualEditor's modules to support a much slimmer mobile version.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393464256, 'spacePHID': None, 'dateCreated': 1391820360, 'dateModified': 1443276290, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61075', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector \"Matching/redirect/disambiguation page\" messages should be pluralized', 'description': {'raw': '\"visualeditor-linkinspector-suggest-matching-page\": \"Matching page\",\\n\"visualeditor-linkinspector-suggest-disambig-page\": \"Disambiguation page\",\\n\"visualeditor-linkinspector-suggest-redirect-page\": \"Redirect page\"\\n\\nThese messages should be something like {{PLURAL:$1|Matching page|Matching pages}} instead, and be passed the number of pages in the section.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391823074, 'spacePHID': None, 'dateCreated': 1391818380, 'dateModified': 1443276290, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61071', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The Advanced Settings of an image is showing the previous value even after a change unless user saves the page', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Add an image\\n3.Open the media settings for that image\\n4.Go to Advanced Settings tab\\n5.Change the image size to something different than what it is right now\\n6.Click on \"Apply Changes\"\\n7.Reopen the Media Settings again and go to Advanced Settings panel\\n\\nObserved Results:\\nThe Size values are still reflecting the previous value unless user saves the whole page and open the panel again it stays like this.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit#cite_ref-2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392253579, 'spacePHID': None, 'dateCreated': 1391803020, 'dateModified': 1443276291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61052', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Uncaught Error: Offset could not be translated to a DOM element and offset: 227 appears and Cannot unselect the image highlight after moving it to the center of the page', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE which contains a image at the right\\n\\n2.Select the image \\n\\n3.Go to the Media Settings> Advanced Settings\\n\\n4.Move the position of the image to center\\n\\n5.Select some other element or just click outside the image anywhere on the page\\n\\n\\nObserved result:\\nCannot select any other object in the page \\nAn error appears in the console:\\nUncaught Error: Offset could not be translated to a DOM element and offset: 227\\n\\nSee the screenshot attached.\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Ehat?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13303}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392861654, 'spacePHID': None, 'dateCreated': 1391732220, 'dateModified': 1443276294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61001', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Format action applies to nodes inside handlesOwnChildren node', 'description': {'raw': '1. Select a block image with caption\\n2. Press the list button\\n\\nExpected:\\nEither nothing, or a list is created above/below the image\\n\\nObserved:\\nThe caption is wrapped in a list\\n\\nClearly we need to ignore nodes which are inside handlesOwnChildren nodes when applying such actions.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60804'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391803295, 'spacePHID': None, 'dateCreated': 1391704140, 'dateModified': 1443276294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60969', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: HTML content model constraints are sometimes violated', 'description': {'raw': 'See \\nhttps://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE3&diff=63988076&oldid=63988055 ,\\nor https://it.wikipedia.org/w/index.php?title=Oreste_Tommasini&diff=63836558&oldid=61161898, or https://it.wikipedia.org/w/index.php?title=Frederic_William_Maitland&diff=63692381&oldid=59785358 .\\n\\nReproduced with Chrome, FF, Opera (unlogged), tested with both skins.\\n\\nYou only need to add the Template:Interprogetto to an existing page or a new one.\\nUseless code like <span data-ve-ignore=\"true\" about=\"g0.8632714317645878\"></span> is added.\\nJames, bug 59653, IMHO, had a similar problem.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60375'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391649521, 'spacePHID': None, 'dateCreated': 1391610120, 'dateModified': 1443276297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60897', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector is adding just a link text while opening up the inspector for the second time selecting another element', 'description': {'raw': 'link text appearing for the second time\\n\\nSteps to reproduce:\\n\\n1.Select a math function/image/gallery/hiero\\n2.Now open the link inspector\\n3.Insert a link (this link gets placed just before the selected element)\\n4.Again select the element\\n5.Open the link inserter\\n6.Observe that the link title of the previous link is appearing now in the link inspector\\n7.Close the link inspector.\\n\\nObserved Result:\\nThe link text title of the previous link is getting inserted just before the selected element.\\n\\nSee the screenshot attached.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/Image_then_gallery?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12936}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410955005, 'spacePHID': None, 'dateCreated': 1391544360, 'dateModified': 1441911986, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60843', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Images trigger creation of huge protectedNode-shields that cover the page', 'description': {'raw': 'Any time I try to use the mobile VisualEditor on a page that includes an image, it is not editable due to having a protectedNode-shield covering most of the page. You can see an example at:\\nhttps://en.m.wikipedia.org/wiki/Rice_flour#editor/0\\n\\nThe protectedNode-shield has a width of 100% and a height of 100% and it appears that each image creates a new one.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393453784, 'spacePHID': None, 'dateCreated': 1391542860, 'dateModified': 1443276297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60841', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding new content via an inspector (formula, gallery, hiero, etc.) and opening the save dialog results in confusion', 'description': {'raw': 'Intention:\\nAdd a gallery\\n\\nSteps to Reproduce:\\n1. Open a page in Safari.\\n\\n2. Go to Insert > Gallery\\n\\n3. Type in the name of an image and a caption.  *Don\\'t click or type anywhere else after this.*\\n\\n4. Click on the save button.\\n\\n5. Realize that the gallery dialog is still open, so cancel the save box.  The dialog will close and the gallery will display.\\n\\n6. Click on the save button again.\\n\\nActual Results:  \\nThe gallery displays on screen, but is not present in Review Changes or when the page is saved.\\n\\nIf you click outside the gallery dialog after typing the name, or if you click the mysterious < button, then it works as expected.\\n\\nExpected Results:  \\nA button at the bottom of the gallery inserter that says \"Insert this gallery now\".\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67049'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392231632, 'spacePHID': None, 'dateCreated': 1391540760, 'dateModified': 1443276301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60837', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Creating a link while selecting an image modified the link inside the caption', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a image\\n3.Open the media settings for the image\\n4.Insert a link as a caption\\n5.Save the page\\n6.Reopen the page and select the image\\n7.Open the link inspector and type in a different a link inside it\\n8.Save the page\\n9.Reopen the page and the Media Settings for the image\\n\\nObserved Result:\\nThe link inside the caption got changed by the link inserter in step 7\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60969\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58045'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396470538, 'spacePHID': None, 'dateCreated': 1391480580, 'dateModified': 1443276301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60804', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  It should not be possible to paste images from external websites into the references dialog', 'description': {'raw': \"Intention:\\nReplicate a mess seen at https://pt.wikipedia.org/w/index.php?title=Esporte_Clube_Pelotas&curid=68824&diff=38075497&oldid=38075466\\n\\nSteps to Reproduce:\\n1. Start creating a new reference.\\n2. Open nytimes.com and select both some text and one small image. \\n3. Copy the selection and paste it into the ref dialog box.\\n\\nActual Results:  \\nIn Safari, nothing pastes.  In Firefox, both text and image rich-paste into the ref dialog box, but I can't save the page.\\n\\nExpected Results:  \\nThat the image would be discarded, since it's not uploaded to the wiki.\\n\\nReproducible: Sometimes\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414011221, 'spacePHID': None, 'dateCreated': 1391457300, 'dateModified': 1417571296, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60780', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cite: Auto-filled references based on destination URL / DOI etc.', 'description': {'raw': '**As an editor I can get paste a link or DOI into a simple form to get an auto-filled citation.**\\n\\nA user has their cursor in a place they would like to add a citation. \\nThey click the Cite button on the toolbar. \\nAn inspector opens in context, showing the title \"Cite\" a URL field, and a \"Lookup\" button.\\n\\nClick-through prototype http://invis.io/HR2DK2FXM\\n\\n**Workflow**\\n{F55330}\\n\\n**Detail of citation inspector**\\nInclude line below field with link that opens the manual citation dialogue.\\n{F45790}\\n\\n**Manual Citation Dialogue**\\nFirst step now includes all items in the former Cite menu\\n{F43867}\\n\\n**Errors**\\nDOI error - if incorrect amount of characters entered\\n{F43776}\\n\\nURL error - if page not found\\n{F45749}\\n\\nGeneric error\\n{F45752}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-evd3wnvnlb66lrwulch4', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '160', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426536275, 'spacePHID': None, 'dateCreated': 1391446500, 'dateModified': 1660398841, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60768', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: VE doesn't load on mobile anymore\", 'description': {'raw': 'http://en.m.wikipedia.beta.wmflabs.org/wiki/Forty-seven_Ronin?mobileaction=alpha#editor/0\\n\\nError: Container must be attached to the DOM Error {stack: (...), message: \"Container must be attached to the DOM\"}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391192467, 'spacePHID': None, 'dateCreated': 1391133180, 'dateModified': 1443276303, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60662', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Closing a Math inspector deletes the selected node/element', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Now select an image or a reference note in the Page\\n3.Now Open the Gallery from Insert>Gallery\\n\\nObserved Result:\\n\\nIt deletes the image and the reference note.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402296411, 'spacePHID': None, 'dateCreated': 1391023680, 'dateModified': 1417572236, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60591', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Let skin variance for styling of <figures> in page content', 'description': {'raw': 'The CSS file modules/ve-mw/ce/styles/ve.ce.Node.css implements styling of page content. This styling should be handled by the skin, not by VisualEditor. It looks like someone already figured this out, as most of the styles include TODO notes about merging them into core styles.\\n\\nAs the mobile team is now implementing VE with a mobile-specific skin, now would be the best time to make these fixes. Otherwise, lots of !important overrides will be necessary.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392848159, 'spacePHID': None, 'dateCreated': 1390944600, 'dateModified': 1443276303, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60542', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikitext is appearing for linked pages in readmode and in VE mode in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Select a text for example: \"link with wikitext\"\\n3.Press command+k to apply link on it\\n4.Without adding anything just close the inspector.\\n5.Save the page.\\n6.Reopen the page in VE\\n\\nObserved Result:\\nThe wikitext for the link is appearing in Read mode and in VE\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/23rd_january\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13098}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390862089, 'spacePHID': None, 'dateCreated': 1390511280, 'dateModified': 1443276307, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60378', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Adding a template and removing a non-breaking space (nbsp) causes span tags with data-ve-ignore', 'description': {'raw': 'Intention:\\nAdd a template and remove a non-breaking space (&nbsp;) in the same line/paragraph\\n\\nSteps to Reproduce:\\n(Order matters!)\\n\\n1.  Begin with a page that contains the HTML code for a non-breaking space.  Open in VisualEditor.\\n\\n2.  On the line that contains the nbsp, add a template (e.g., {{fact}}).  The template should be added to the same \\'word\\' that contains the nbsp.\\n\\n3.  Then remove the nbsp (replace with a plain space, or just delete the whole \\'word\\').\\n\\nActual Results:  \\nVisualEditor added span text like <span about=\"g0.42287685585435686\" data-ve-ignore=\"true\"></span> when the nbsp was removed.\\n\\nAdding a fact template to the end of:\\n\\n1&nbsp;mg 2&nbsp;mg 3&nbsp;mg 4&nbsp;mg\\n\\nturns into:\\n\\n1&nbsp;mg 2&nbsp;mg 3&nbsp;mg 4 mg{{Fact}}<span data-ve-ignore=\"true\" about=\"g0.5170239245053381\"></span>\\n\\nHowever, adding the template to \"3 mg\" and deleting the nbsp from \"2 mg\" works correctly:\\n\\n1&nbsp;mg 2 mg 3&nbsp;mg{{Fact}} 4&nbsp;mg\\n\\n\\n\\n\\nReproducible: Always\\n\\nSee https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVisualEditor%2FFeedback&diff=591972176&oldid=591955710 and testing at https://en.wikipedia.org/w/index.php?title=User:Jay8g/sandbox&action=history on 23 January 2014 for many more details.\\n\\nFound in Firefox 26 on Windows 7 with Monobook, confirmed in Safari 6 on Mac OS 10.8.5 with Vector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60897'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391668943, 'spacePHID': None, 'dateCreated': 1390506600, 'dateModified': 1443276307, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60375', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  \"Edit\" tab not appearing sometimes', 'description': {'raw': 'Reproducible: Didn\\'t try\\n\\nTwo editors report that VisualEditor\\'s \"Edit beta\" tab occcasionally does not appear on their screens.  Both were using Firefox on Windows 7.  The button reappeared upon refreshing the screen, or spontaneously reappeared the next day.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397067449, 'spacePHID': None, 'dateCreated': 1390436160, 'dateModified': 1417572494, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60359', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'importImages.php broken on cluster', 'description': {'raw': 'reedy@tin:/tmp/uploads$ sudo -u apache mwscript importImages.php --wiki=commonswiki --user=\"Jdforrester_(WMF)\" /tmp/uploads\\nImport Images\\n\\nImporting linux.conf.au 2014 - VisualEditor presentation.ogv...PHP Warning:  fopen(/tmp/uploads/linux.conf.au 2014 - VisualEditor presentation.ogv): failed to open stream: Permission denied in /a/common/php-1.23wmf10/includes/filebackend/SwiftFileBackend.php on line 278\\n\\nWarning: fopen(/tmp/uploads/linux.conf.au 2014 - VisualEditor presentation.ogv): failed to open stream: Permission denied in /a/common/php-1.23wmf10/includes/filebackend/SwiftFileBackend.php on line 278\\ndone.\\n\\nFound: 1\\nAdded: 1\\nreedy@tin:/tmp/uploads$\\n\\n\\nThe added is a lie. The upload didn\\'t complete, it\\'s a 404\\n\\nhttps://upload.wikimedia.org/wikipedia/commons/e/ea/Linux.conf.au_2014_-_VisualEditor_presentation.ogv\\n\\n404 Not Found\\n\\nThe resource could not be found.\\n\\nFile not found: /v1/AUTH_mw/wikipedia-commons-local-public.ea/e/ea/Linux.conf.au_2014_-_VisualEditor_presentation.ogv\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60777'}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': 'PHID-USER-bmbmvb2e5bg6ztcangbq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391470372, 'spacePHID': None, 'dateCreated': 1390354860, 'dateModified': 1417692096, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60318', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Changes to VisualEditor on eswiki as result of vote', 'description': {'raw': '**Author:** `llamaal_wikis`\\n\\n**Description:**\\nIntention:\\nAfter the conclusion of https://es.wikipedia.org/wiki/Wikipedia:Votaciones/2014/Sobre_el_Editor_Visual on the Spanish Wikipedia, some changes to the status of VE in that project have to be implemented:\\n\\n1. VE should now be opt-in\\n2. The \"edit\" tab should return to wikitext\\n3. VE should be presented as part of Beta Features\\n4. The tab for VE, if users activate it, should be \"Editor VisualBETA\"\\n\\nRegards,\\n\\nLlamaAl\\n\\n\\n\\n\\nReproducible: Didn\\'t try\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392253962, 'spacePHID': None, 'dateCreated': 1390009440, 'dateModified': 1392253962, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60188', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Standalone demo toolbar breaks sometimes in Chrome', 'description': {'raw': \"Screenshot of the bug\\n\\nSee attached screenshot.\\n\\nThis is because the standalone demo initializes the target into a detached DOM element, then attaches it once it's done. But you can't do that, because it causes ve.ui.Toolbar.prototype.initialize to be run before the toolbar is attached to the DOM (and generally causes initialize to be run on unattached things, which is not allowed), which means its measurements will be wrong, and so the toolbar gets right: 1840px; (width of screen) rather than width: 63px; or whatever.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13274}\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390864797, 'spacePHID': None, 'dateCreated': 1389997140, 'dateModified': 1417572670, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60183', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor messages not updated for 1.23wmf11', 'description': {'raw': 'Broken inspector\\n\\nSteps to reproduce:\\n\\n1.Open the VisualEditor\\n2.Go to Insert menu and Settings menu\\n\\nObserved Result:\\n<visualeditor-mwgalleryinspector-title> and <visualeditor-dialog-commands>  is appearing in the Insert menu and Settings menu respectively.\\nAlso selecting <visualeditor-mwgalleryinspector-title> opens up a broken gallery inspector.\\n\\nSee the screenshot attached.\\n\\nTest Environment: https://test2.wikipedia.org/,wmf11\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13165}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389985486, 'spacePHID': None, 'dateCreated': 1389904560, 'dateModified': 1389985847, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60149', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switching insertion types for inspectable notes (e.g. hiero, formula, gallery) mid-creation breaks entertainingly', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a math function from Insert>Formula for example \\\\pi\\n3.While the added math formula is still selected go to Insert>Hiero\\n4.Observe that the math function previously added is now appearing in hiero inspector.\\n5.Close the inspector for hiero\\n6.Save the page\\n\\nObserved Result:\\nA hiero tag got added  in the wikitext as  <hiero>\\\\pi</hiero>\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/w/index.php?title=Wmf11&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13157}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391728232, 'spacePHID': None, 'dateCreated': 1389903480, 'dateModified': 1417572665, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60148', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection highlighting breaks on changing selection format (cursor moves to wrong place, selection is unhighlighted but still selected)', 'description': {'raw': 'Selecting a line of text and turning it into a header (ctrl+1) removes the selection highlighting but keeps the text selected. Additionally turning text into a header also moves the position marker to the wrong place (visually).\\n\\nAs a result e.g. the action of creating a header then pressing enter replaces the header by an empty line.\\n\\nSe screencast below for procedure and illustration.\\nhttps://www.youtube.com/watch?v=7OtpP5iS2uw\\n\\nReproducible in Chrome and Firefox\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394659271, 'spacePHID': None, 'dateCreated': 1389892740, 'dateModified': 1417572575, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60139', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Loading the San Francisco article on mobile causes massive breakage, unusable editor', 'description': {'raw': \"Oh nos!\\n\\nWhen trying to edit San Francisco with VE in mobile alpha mode all hell breaks lose.\\n\\nSee for yourself at this URL:\\nhttps://en.m.wikipedia.org/wiki/San_Francisco?mobileaction=alpha#editor/0\\n\\nand see screen for the sort of things that happen.\\n\\nI can't focus the textarea or make any changes. This makes me sad.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13080}\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394494444, 'spacePHID': None, 'dateCreated': 1389833400, 'dateModified': 1417572577, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60115', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  [Regression] External rich pasting in Firefox inserting newlines again', 'description': {'raw': 'https://jv.wikipedia.org/w/index.php?title=Kraton_Ngayogyakarta_Hadiningrat&curid=87083&diff=879162&oldid=845799\\n\\nThis begins with a =Level 1 heading= (perhaps the article title was copied?).  Some paragraphs are broken onto separate lines. The [[links]] are improperly converted to [[http://jv.wikipedia.org/wiki/Links]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421282899, 'spacePHID': None, 'dateCreated': 1389725880, 'dateModified': 1423077120, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60050', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:TypeError: currentDom[i].setAttribute is not a function appears while adding content from Template dialogbox', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Transclusion \\n3.Add some content and click on \"Apply changes\"\\n4.Click on \"Save Page\"\\n\\nObserved Result:\\n\\nThe \"Save Page\" button does not worl.In the console the following error appears:\\nTypeError: currentDom[i].setAttribute is not a function\\n\\nSee the screenshot attached.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/Jan_13th?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12850}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390317183, 'spacePHID': None, 'dateCreated': 1389651180, 'dateModified': 1443276310, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60019', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: TypeError: Cannot call method 'getModel' of null when adding a newline after a new media item\", 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which has some content\\n2.Add any image from Insert>Media after going to a newline.\\n3.Save the page\\n4.Reopen the page\\n5.Place the cursor in a new line and hit return\\n\\nObserved Result:\\nNewline cannot be added , in the console an error appears:\\nTypeError: outermostNode is null\\n\\t\\n\\n...documentModel,selection.from,'\\\\n');}else{node.traverseUpstream(function(node){if...\\n\\nload.p...1826Z&* (line 261)\\n\\nTest Environment: mw.org\\nBrowser: FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/w/index.php?title=User:Jdforrester_(WMF)/Sandbox_345&oldid=885285?veaction=edit\\n\\n**Attached**: {F12613}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393614615, 'spacePHID': None, 'dateCreated': 1389374820, 'dateModified': 1443276310, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59911', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting copied template cause it to be inserted twice, once broken', 'description': {'raw': 'Steps to reproduce:\\n\\n- go to page (for example [1]) that has only this as contents: {{done}}\\n- edit the page with visual editor\\n- copy/paste the template\\n- I was expecting the page now to contain only this text: {{done}}{{done}}\\n- instead, the page text is: {{done}}{{done}}<span data-ve-ignore=\"true\"> </span>\\'\\'\\'Done.\\'\\'\\'\\n- that causes \"Done.\" to be displayed three times (instead of two), see screenshot[2]\\n- two minute video recording reproducing the bug is available at [3]\\n- Sauce Labs is pretty slow to respond, so the actions looks really really slow, the best way to view the video is to download it from [4] and play it with VLC on maximum speed (4x)\\n\\n1: https://test2.wikipedia.org/wiki/Done\\n2: https://saucelabs.com/jobs/9dd0291def28413bb7f9ca3a9fd7e891/0001screenshot.png\\n3: https://saucelabs.com/tests/9dd0291def28413bb7f9ca3a9fd7e891\\n4: https://saucelabs.com/jobs/9dd0291def28413bb7f9ca3a9fd7e891/video_9dd0291def28413bb7f9ca3a9fd7e891.flv\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389904122, 'spacePHID': None, 'dateCreated': 1389356460, 'dateModified': 1417596605, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59902', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Document selection should be nullable', 'description': {'raw': 'Despite the fact that you can have the appearance of the document being blurred and having no active selections, we will always keep the last valid range as the current selection. This is a case of the model not matching the view.\\n\\nThe other solution (as used by Google Docs) is to always render a selection even when the document is unfocused, but as we are using native selections this may not be possible.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62410'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397491688, 'spacePHID': None, 'dateCreated': 1389282420, 'dateModified': 1443276313, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59868', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Cutting (removing) last sections on page, and then pasting them back in, results in increased indentation in Chrome', 'description': {'raw': \"Intention:\\nTest a bug.\\n\\nSteps to Reproduce:\\n1. Selecting the appendices on the page https://en.wikipedia.org/w/index.php?oldid=588539903&veaction=edit\\n\\n2. Cut them out (Control-x), and \\n\\n3. Paste them right back where they were.  \\n\\n\\nActual Results:  \\nThe indentation level for all the bulleted lists was increased.\\n\\n\\nReproducible: Didn't try\\n\\n**URL**: https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FS%26D&diff=588777573&oldid=588539903\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437603284, 'spacePHID': None, 'dateCreated': 1389228060, 'dateModified': 1465905585, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59849', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Mouse up outside the surface doesn't register a selection change.\", 'description': {'raw': '1. Open up the standalone demo /empty.html and type some text\\n2. Select text from right to left, mouse up outside the surface (or even outside the window)\\n3. Although the text is selected in CE pressing dump range gives a collapsed range. Formatting actions will fail too.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410487873, 'spacePHID': None, 'dateCreated': 1389195120, 'dateModified': 1443278211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59822', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector UI gets broken while applying link to a text at the end of the article', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390021348, 'spacePHID': None, 'dateCreated': 1389118200, 'dateModified': 1443276314, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59776', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Native browser interactive spell-check tool fails to get content into DM, just CE, in Safari', 'description': {'raw': 'Intention:\\nCorrect the spelling of a word.\\n\\nSteps to Reproduce:\\n1. Add some text, including a spelling error, to an article.\\n2. Use Safari\\'s built-in spellcheck to correct the spelling. \\n\\n\\nActual Results:  \\nThe correct spelling displays on the screen.  However, if you \"review changes\", only the old, incorrect spelling is present.  Also, the correct spelling stops being displayed on the screen if you hit return to start a new paragraph or list item.\\n\\nScreenshot shows the display and the review changes.  Confirmed in both lists and plain paragraphs.\\n\\n\\nReproducible: Always\\n\\nConfirmed in Safari 6 on Mac OS 10.8.5 using Vector.  It\\'s not present in Firefox 26.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50822'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1424273920, 'spacePHID': None, 'dateCreated': 1389056280, 'dateModified': 1424479028, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59748', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Use gzip compression when POSTing HTML', 'description': {'raw': \"Per Gabriel's report via email, when VE POSTs HTML to api.php , it should ensure that gzip compression is used for the POST body.\\n\\nTODO: Figure out how to actually tell the browser to do this\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403735953, 'spacePHID': None, 'dateCreated': 1388891040, 'dateModified': 1570755303, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59659', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Pasting should remove formats (and other types of content?) that aren't allowed in the target\", 'description': {'raw': 'Intention:\\nAdd a caption to an image without having to type out the name by hand.\\n\\nSteps to Reproduce:\\n1. Add an image in VisualEditor (e.g., an image of a person).  Open the caption dialog.\\n2. Go to another window (e.g., an article about the person) and copy a =Name= from the article title.\\n3. Paste the rich text into the caption.\\n\\nActual Results:  \\nThe pasted text retained rich formatting.  It is not possible to remove the =Heading= formatting.  Only \\'\\'\\'text\\'\\'\\' <s>formatting</s> can be added or removed in that dialog.  So if you copy the article title from [[George Washington]] and paste it into the caption box, then it produces this wikitext:\\n\\n= <span dir=\"auto\">George Washington</span> =\\n\\nand there is no way to remove the formatting.\\n\\nExpected Results:  \\nThat either you could remove the formatting, or ideally, that the caption box would strip the unwanted formatting automagically.  There\\'s no obvious reason why someone would need or want a ==Heading== of any level in a caption.\\n\\nReproducible: Didn\\'t try\\n\\nConfirmed in Safari 6 and Firefox 26\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391651684, 'spacePHID': None, 'dateCreated': 1388776980, 'dateModified': 1443276319, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59603', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make the insertion of a reference list suck less; e.g. show \"General references\" as placeholder text in the group box when it is empty', 'description': {'raw': 'I see now, that there is a dialog box for reference group, while in most cases, where refs are being used as citation, we dont need to fill that group. I propose than to give a tip below that dialox box saing: \"For reference list leave empty\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392860331, 'spacePHID': None, 'dateCreated': 1388573640, 'dateModified': 1443276322, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59180', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference is redirecting to the page from where it is copied in Firefox', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in FireFox which contains a reference and reference list\\nFor example:\\nreference<ref>reference</ref>\\n<references />\\n2.Copy the reference and the reference list\\n3.Open another page with VE in FireFox\\n4.Paste the reference and the reference list\\n5.Save the page\\n\\nObserved Result:\\nThe wikitext resulting from after copy-paste is:\\n\\nreference<span class=\"reference\" id=\"cite_ref-1-0\" rel=\"dc:references\"><sup href=\"http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit#cite_note-1\">[1]</sup></span>\\n#<span class=\"\" rel=\"mw:referencedBy\">[http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit#cite_ref-1-0 ↑]</span> reference\\n\\nAnd it redirects to the source page (in this case: http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit#cite_ref-1-0) \\n\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Newrefff\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12746}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390559944, 'spacePHID': None, 'dateCreated': 1388531940, 'dateModified': 1443276322, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59173', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference list is getting copied as bullet list instead as <references/> while doing copypaste from Chrome to FF', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in Chrome Browser which has references list in it \\n2.Copy the references list with the reference.For example copy the following:\\nreference<ref>reference</ref>\\n<references />\\n3.Open another page in FireFox with VE\\n4.Paste the copied reference and reference list\\n5.Save the page\\n\\nObserved Result:\\nThe reference list got copied as bullet list rather than as <references/>\\n\\nThe resulting wikitext is as follows:\\nreference<sup>[1]</sup>\\n# reference\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nChrome Page:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=31st_december&veaction=edit\\nFF Page:http://en.wikipedia.beta.wmflabs.org/wiki/Newrefff\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12743}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390559956, 'spacePHID': None, 'dateCreated': 1388527440, 'dateModified': 1443276322, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot copy paste a template from Chrome Browser to FF browser and shows error TypeError: item is undefined', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page in Chrome Browser with VE which has a template in it\\n2.Copy the template\\n3.Open another page in FirFox browser with VE\\n4.Paste the copied template\\n\\nObserved result:\\nThe template does not get copied and in the console an error appears:\\nTypeError: item is undefined\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/31st_decemberff?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12738}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390559897, 'spacePHID': None, 'dateCreated': 1388526240, 'dateModified': 1443276323, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59170', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference is getting copied as <sup>[1]</sup> instead of <ref> tags in Firefox', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE which has reference added to a text\\n2.Copy the text with the reference \\n3.Open another page with VE in FireFox\\n4.Paste the copied reference\\n\\nObserved Result:\\nInstead of getting copied as text <ref> reference </ref>, it is getting copied as text<sup> [1] </sup>\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: FF 25\\nOS: MAC OS X 10. 8. 5 \\nhttp://en.wikipedia.beta.wmflabs.org/w/index.php?title=30th_december_ff&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390559950, 'spacePHID': None, 'dateCreated': 1388450160, 'dateModified': 1443276323, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59154', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copy-paste of image is throwing typeerror, when its done from Chrome to FF', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the VE in Chrome browser for a page which contains image\\n2.Copy the image\\n3.Open another VE in FireFox browser\\n4.Paste the copied image\\n\\nObserved Result:\\nImage does not get copied.An error appears in the console:\\nTypeError: item is undefined\\n\\t\\n\\n...nction(){return this.getData(this.balancedRange);};ve.dm.LinearData=function VeD...\\n\\nload.p...2128Z&* (line 122)\\n\\nSee the screenshot attached.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nhttp://en.wikipedia.beta.wmflabs.org/wiki/30th_december_ff?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12694}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390559938, 'spacePHID': None, 'dateCreated': 1388441100, 'dateModified': 1443276326, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59145', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"You edit may have been corrupted\" Warning appears everytime after adding Cite Web template', 'description': {'raw': 'Warning in the save dialog box\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add the template Cite Web from Insert>Transclusion\\n3.Save the page\\n4.Reopen the page with VE\\n5.Do some more edit in that page\\n5.Click on \"Save Page\"\\n\\nObserved Result:\\nA warning appears in the save dialog box \"You edit may have been corrupted-Please review your changes\"\\n\\nThis error appears everytime I add this Cite Web template even though there is no apparent reason for being my edit corrupted.\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12545}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393360715, 'spacePHID': None, 'dateCreated': 1388269860, 'dateModified': 1443276326, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59091', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Cannot Edit any page in betalabs', 'description': {'raw': \"Attempting to edit any page in betalabs is giving following error:\\nError loading data from server: internal_api_error_MWException: Exception Caught: Tag hook for namespace is not callable.\\n\\nIn the console,I see the following error\\nUncaught TypeError: Cannot read property '$actions' of null\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27th_december\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388204152, 'spacePHID': None, 'dateCreated': 1388182380, 'dateModified': 1417572680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59010', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:Uncaught TypeError: Object [object Text] has no method 'setAttribute' appears while attempting to save after adding Cite Web template\", 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Open the editor for page\\n2.Go to Insert>Template\\n3.Search for template Cite Web\\n4.Add a a value for source title field but keep the URL field empty\\n5.Add the template\\n6.Click the button \"Save Page\"\\n\\nObserved Result: \\nThe \"Save Page\" button does not work .In the console it is showing an error:\\nUncaught TypeError: Object [object Text] has no method \\'setAttribute\\'\\n\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55985\\n\\n**Attached**: {F12409}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389900032, 'spacePHID': None, 'dateCreated': 1388169840, 'dateModified': 1443276326, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59002', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Alt + any key in a slug introduces a pawn in Firefox on Windows', 'description': {'raw': 'With FireFox (compulsory) on Windows\\ninsert a new line then enter : Alt A (or Alt + any key)\\n=> a pawn is inserted\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Platform**: PC\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61538'}, 'authorPHID': 'PHID-USER-hhw22zfd2xzrsyc22lp5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421282348, 'spacePHID': None, 'dateCreated': 1387409040, 'dateModified': 1423077104, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58675', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'BetaFeatures: Validate skin requirement is installed before showing it', 'description': {'raw': 'VisualEditor supports the \\'apex\\' skin, however that isn\\'t installed on WMF projects, so users using a non-supported skin will see \"&lt;skinname-apex&gt;\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410617419, 'spacePHID': None, 'dateCreated': 1387340940, 'dateModified': 1410617419, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58623', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Reference is getting copied as an empty <ref/> tag', 'description': {'raw': 'screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Go to this page:\\n\\nhttps://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/12th_december&veaction=edit\\n\\n2.Copy the reference and the reference list at the end of this page\\n3.Paste in into another VE\\n4.Save it\\n\\nObserved Result:\\n\\nThe wiki text for the text copied is: \\n\\nreference<ref>http://cnn.com</ref>\\n<references />\\n\\nThe wiki text on the page where it is copied to:\\nreference<ref />\\n<references />\\n\\nIn Edit mode it says:\\nThe reference is defined in a template or other generated block and for now can\\nonly be edited in source mode.\\n\\nand the reference cannot be edited using VE\\n\\n\\nIn read mode it shows:\\n\\nCite error: The opening <ref> tag is malformed\\nor has a bad name (see the help page).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12112}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387210816, 'spacePHID': None, 'dateCreated': 1386894600, 'dateModified': 1417572680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58427', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion template suggestions are no longer available', 'description': {'raw': '**Author:** `jhall`\\n\\n**Description:**\\nSeen in beta labs with these repro steps:\\n\\n1)  Open Visual Editor.\\n2)  Select \"Transclusion\" from the \"Insert\" menu.\\n3)  Type some characters in the \"New Template\" text box.\\n\\nIn previous releases of VE, the user would get a list of template suggestions.  That list of suggestions doesn\\'t seem to be displaying anymore :(\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53231'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388168683, 'spacePHID': None, 'dateCreated': 1386875760, 'dateModified': 1417572680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58406', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The toolbar design inside the MediaSettings and Reference does not match with the new toolbar design on main CE', 'description': {'raw': 'Screenshot inside reference\\n\\nWe have changed the toolbar design to have all the formatting under one button A (underlined) and all other options to add elements under Insert option.\\n\\nBut if you open up the Media Settings or a Reference the toolbar that appears there does not conform with the new design.\\nIt will better to have a consistent design everywhere the toolbar is used.\\n\\nSee the screemshots attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F12060}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386877360, 'spacePHID': None, 'dateCreated': 1386874140, 'dateModified': 1417572736, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58404', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clouds are added at the end of a paste', 'description': {'raw': 'A could sometimes suddenly appears. As well as \\'left over sections\\' it seems.\\n\\nhttps://www.mediawiki.org/w/index.php?title=User:TheDJ/sandbox&oldid=841359\\n\\nI think this was due to \"select all\" cmd-A, then cmd-v paste over the old content.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402508824, 'spacePHID': None, 'dateCreated': 1386844260, 'dateModified': 1443276327, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58389', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CE adds linebreaks when pasting into empty lines', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open the editor for a page which contains link\\n\\n2.Copy it.\\n\\n3.Paste it into a new line \\n\\n4.Save it\\n\\nObserved Result:\\nThe link is getting merged on to the end of the previous line\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387471583, 'spacePHID': None, 'dateCreated': 1386790440, 'dateModified': 1417572681, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58347', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot copy-paste anything after doing command+c on an empty/unselected position within a word', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the Editor.\\n2.Place the cursor inside a word or text but do not select anything\\n3.Press command+c\\n4.Now go to another page and do command+v (Nothing is getting copied, which is okay as per the fix given in https://bugzilla.wikimedia.org/show_bug.cgi?id=58138)\\n5.But now select anything from the source page by selecting it\\n6.Press command+c\\n7.Press command+V onto the other page where you were pasting.\\n\\nObserved Result:\\nNothing gets copied\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386808461, 'spacePHID': None, 'dateCreated': 1386788820, 'dateModified': 1417572737, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58346', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Special:ExtensionDistributor/VisualEditor not picking up REL1_22', 'description': {'raw': 'Maybe some new config has to be added for it to consider REL1_22 as a valid branch to download?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dpu5hmqvprhycqlkdzrk', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386805557, 'spacePHID': None, 'dateCreated': 1386779400, 'dateModified': 1386805557, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58334', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting a table with a caption breaks fixUpInsertion', 'description': {'raw': 'Safari 7\\n\\nCopy on https://www.mediawiki.org/wiki/VisualEditor?veaction=edit\\n\\nFrom and including the header Timeline, up to the paragraph before \"Notes\" headline (including the table).\\n\\nPast in an empty surface:\\n\\n[Error] TypeError: \\'undefined\\' is not an object (evaluating \\'source.clone\\')\\n\\tcopy (undefined, line 3)\\n\\tgetClonedElement\\n\\tfixupInsertion\\n\\tfixupInsertion\\n\\tnewFromDocumentInsertion\\n\\tafterPaste\\n\\tproxy (load.php, line 10)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386808472, 'spacePHID': None, 'dateCreated': 1386752340, 'dateModified': 1417571283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58318', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing between text and a reference produces a pawn in Firefox', 'description': {'raw': 'This came from the Hebrew Wikipedia feedback page, I could not replicate it in the English Wikipedia\\n\\nIt seems to happen only in Firefox.\\n\\n\\nTo reproduce -\\n\\n1. Go to this sample page: https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Nurick/%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_-_%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99&oldid=14834614&veaction=edit\\n\\n2. Put the cursor a couple of character to the left of the word \"יפן\" (third paragraph, the word with the reference attached)\\n\\n3. Move the cursor so it is between the word and the reference.\\n\\n4. Add a period.\\n\\nWatch a pawn appear.\\n\\n* Firefox 25.0.1 on Windows and on Ubuntu\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406596147, 'spacePHID': None, 'dateCreated': 1386748620, 'dateModified': 1443278215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58315', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: On sub-pages, new links are relative to the parent page, not the wiki', 'description': {'raw': 'This is an interesting feedback comment that came from the Hebrew Wikipedia and I managed to also replicate in the English Wikipedia. \\n\\nSteps to replicate:\\n\\n1. Go to a Sandbox page under a username. For example, this page https://en.wikipedia.org/w/index.php?title=User:Mooeypoo/Sandbox&veaction=edit\\n\\n2. Mark one of the words and add an existing page to link to it. For instance, I marked \\'some\\' and chose the link to \"Somerset\".\\n\\n3. Inspect the link while still in VisualEditor - the link is under the user namespace, so in my example, the link is now \"https://en.wikipedia.org/wiki/User:Mooeypoo/Somerset\"\\n\\n4. Save the page.\\n\\n5. After save, the link seems fine (points to https://en.wikipedia.org/wiki/Somerset as it should).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=59196'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395874616, 'spacePHID': None, 'dateCreated': 1386745260, 'dateModified': 1443276329, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58314', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Link inspector is not opening up for a link when selecting the entire annotation', 'description': {'raw': 'Broken UI\\n\\nSteps to reproduce:\\n\\n\\n1.Open the editor \\n2.create a link\\n3.Save the page\\n4.Re-open the editor.\\n5.Select the link to modify it\\n\\nObserved Result:\\n\\nLink inspector is not opening.Coming back from some other window opens it but the UI is totally broken\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12763}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386792105, 'spacePHID': None, 'dateCreated': 1386721860, 'dateModified': 1417572734, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58301', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting a formula into a block slug throws \"Uncaught TypeError: Cannot call method \\'getOuterRange\\' of null\"', 'description': {'raw': \"screenshot of the error and empty Latex window\\n\\nSteps to reproduce:\\n\\n1.Add a bullet list\\n2.Add a template as a bulleted item\\n3.Save the page and reopen the editor\\n4.Go to the next line of the bulleted list (get rid of bullets by pressing return twice)\\n\\n5.Click on More>Latex\\n\\nObserved Result:\\n\\nThe latex window is opening up at the right end, where the template is placed.\\n\\n6.Then if you change the focus by clicking somewhere on the page outside the latex window\\n\\nObserved Result:\\n\\nA blank Latex windows is opening up and a uncaught type error appears Uncaught TypeError: Cannot call method 'getOuterRange' of null \\n\\nIf you save the page and go to edit source , you will see empty <math> tag is getting placed\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62797\\n\\n**Attached**: {F12725}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398385279, 'spacePHID': None, 'dateCreated': 1386706860, 'dateModified': 1443276329, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58286', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting rich text from external sources inserts spurious new lines in Firefox', 'description': {'raw': \"E.g. copying the disclaimer from my staff page https://www.mediawiki.org/wiki/User:Jdforrester_%28WMF%29 takes:\\n\\n<p><b>Disclaimer:</b> Although I work for the Wikimedia Foundation, contributions under this account do not necessarily represent the actions or views of the Foundation unless expressly stated otherwise. For example, edits to articles or uploads of other media are done in my individual, personal capacity unless otherwise stated.</p>\\n\\n… and turns it into the wikitext:\\n\\n'''Disclaimer:'''\\n<nowiki> </nowiki>Although I work for the Wikimedia Foundation, contributions under this\\naccount do not necessarily represent the actions or views of the\\nFoundation unless expressly stated otherwise. For example, edits to\\narticles or uploads of other media are done in my individual, personal\\ncapacity unless otherwise stated.\\n\\n… (with the newlines showing before saving; not a Parsoid bug).\\n\\nNo new lines added when doing a plain paste.\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386721080, 'spacePHID': None, 'dateCreated': 1386702300, 'dateModified': 1465905551, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58283', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"LocalisationUpdate doesn't work with .i18n.php shims for new-style .json messages\", 'description': {'raw': \"Failed to read file: exception 'Exception' with message 'Expected open tag, whitespace, or variable., got T_STRING ('array_map')' in /a/common/php-1.23wmf6/extensions/LocalisationUpdate/QuickArrayReader.php:135\\nStack trace:\\n#0 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/QuickArrayReader.php(119): QuickArrayReader->except(Array, 'open tag, white...')\\n#1 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(528): QuickArrayReader->__construct('<?php $messages...')\\n#2 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(313): LocalisationUpdate::parsePHP('$messages = arr...', 'messages')\\n#3 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(435): LocalisationUpdate::loadFilesToCompare('VisualEditor', '/var/lib/l10nup...', '/a/common/php-1...', false, false)\\n#4 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(153): LocalisationUpdate::compareExtensionFiles('VisualEditor', '/var/lib/l10nup...', '/a/common/php-1...', false)\\n#5 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/LocalisationUpdate.class.php(113): LocalisationUpdate::updateExtensionMessages('/a/common/php-1...', 'VisualEditor', false, '/var/lib/l10nup...')\\n#6 /a/common/php-1.23wmf6/extensions/LocalisationUpdate/update.php(34): LocalisationUpdate::updateMessages(Array)\\n#7 /a/common/multiversion/MWScript.php(97): require_once('/a/common/php-1...')\\n#8 {main}\\nFailed to parse /var/lib/l10nupdate/mediawiki/extensions/VisualEditor/VisualEditor.i18n.php\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uqcn2l4ng4murmyfnvyp', 'ownerPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396360325, 'spacePHID': None, 'dateCreated': 1386642780, 'dateModified': 1602870080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58249', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: On load, don't select a node if it's the first thing in the document\", 'description': {'raw': 'Ed,\\n\\nThink you were working on this before? Would be lovely to finally get this fixed…\\n\\nJ.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57477'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389643356, 'spacePHID': None, 'dateCreated': 1386641760, 'dateModified': 1443276330, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58248', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MWReferenceList throws exception when pasted with a reference into a new document', 'description': {'raw': 'The Errors\\n\\nSteps to reproduce:\\n\\n1.Open an editor which has a text with reference and the reflist\\nFor example:\\n\\ntext with reference[1]\\n↑ ref\\n\\n2.Try to paste it into a different page\\n\\nObserved Result:\\nUncaught TypeError: Cannot read property \\'length\\' of undefined appears and nothing gets pasted.\\n\\nHowever the \"Save Page\" button is active and clicking on that gives the error:\\nUncaught TypeError: Cannot call method \\'getRange\\' of undefined\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12622}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386890311, 'spacePHID': None, 'dateCreated': 1386630120, 'dateModified': 1417572679, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58242', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template is getting pasted as a table while doing copy-paste', 'description': {'raw': 'Table format in destination page\\n\\nSteps to reproduce:\\n\\n1.Open the editor.\\n2.Copy a template with a parameter which has a value and paste it into a different page\\n3.Copy a template which does not have any parameter  and paste it into a different page\\n4.Copy a template with a parameter which does not have any value.\\n\\n\\nObserved Result:\\n\\n\\n1.All the template copied are getting pasted as a table\\n2.If you switch to the edit source you will see :\\n\\nthe template copied in step 2 has a table format\\nthe template copied in step 3 is getting pasted in an empty template wikitext format:{|\\n!\\n|}\\n\\nthe template copied in step 4 is getting pasted in a template wikitext format with the page name inside it:{|\\n!Copy\\n|}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12618}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386810363, 'spacePHID': None, 'dateCreated': 1386629040, 'dateModified': 1417570407, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58241', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying a link from one editor to another results in visible wikitext in the saved paste target', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the editor for a page\\n2.Place a link to a page\\n3.Rename the link text to something different than the destination page name\\n4.Save the page\\n5.Now copy this link and paste it to another page\\n6.Save the second page\\n\\nObserved Result:\\nIn the read mode of the second page the wikitext for the link is showing up\\n\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12566}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386973700, 'spacePHID': None, 'dateCreated': 1386614460, 'dateModified': 1417572735, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58222', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copied/pasted wiki links are prefixed with ./', 'description': {'raw': 'See: https://www.mediawiki.org/w/index.php?title=User:Eloquence/CP_tests&oldid=838815\\n\\nCopied from:\\nhttps://www.mediawiki.org/w/index.php?title=VisualEditor:Welcome&oldid=799120\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394489459, 'spacePHID': None, 'dateCreated': 1386573000, 'dateModified': 1417572577, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58198', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If copying from one VE instance to another, on pasting the result has a ☁ inserted too', 'description': {'raw': 'screenshot of the icon\\n\\nSteps to reproduce:\\n\\n1.Open the editor for an article\\n2.Place your cursor any position of a link and press command+c.\\n3.Open another page and press command+v\\n\\nObserved:\\n An icon ☁ appears on the second page.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58136\\n\\n**Attached**: {F12394}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386721032, 'spacePHID': None, 'dateCreated': 1386377460, 'dateModified': 1719480752, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58138', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Inserting a template or reference moves the cursor to the top of the page', 'description': {'raw': '**Author:** `Wikifram`\\n\\n**Description:**\\nVersion 2013-12-05 (MW 1.23wmf6), implemented at MediaWiki, now for the first time tested apparently (by me)... When you add a reference, the cursor is again positioned at the top of the article, no matter where you insert the reference. The focus (the part you actually see) of the page is where you added the reference, but when you start typing, you are actually adding text to the top of the page. This is confusing as hell. \\n\\nThe same applies when adding a template, but not with media.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386633441, 'spacePHID': None, 'dateCreated': 1386320580, 'dateModified': 1417572576, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58090', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] On init, page is scrolled to the bottom but cursor remains at the top in Firefox', 'description': {'raw': \"**Author:** `Wikifram`\\n\\n**Description:**\\nHave you ''really'' implemented a new version at MediaWiki that scrolls to the ''bottom'' of the page when opened in VE? Was this intentional or (if I'm allowed to say this) just something that should have been obvious with the most basic test, but somehow wasn't noticed? FF25, W7, nothing fancy or unusual. And no, this didn't happen in earlier versions, and doesn't happen when I use VE on enwiki...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386633345, 'spacePHID': None, 'dateCreated': 1386319980, 'dateModified': 1426363981, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58089', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Trying to un-bullet a bulleted line containing only floated content makes the browser completely unresponsive', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open any article on VE\\n2.Add a bullet list\\n3.Try to add an image as a bulleted item of that list ( the image goes to the right side but keep it like that)\\n4.Save the page\\n5.Reopen the editor\\n6.Now go to position where empty bullet list is.\\n7.Now try to remove it by clicking ob bullet list icon from the toolbar\\n\\nObserved Result:\\nThe Editor become completely unresponsive\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393445651, 'spacePHID': None, 'dateCreated': 1386284160, 'dateModified': 1443276334, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58060', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Button UI is missing in production for Link/Undo/Redo/Cancel formatting/Paragraph drop down/More options/computer code/Media/Help/Settings', 'description': {'raw': 'Screenshot\\n\\nButton UI is missing in production for Link/Undo/Redo/Cancel formatting \\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12207}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386282831, 'spacePHID': None, 'dateCreated': 1386277320, 'dateModified': 1417572741, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58052', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Uncaught Error:Invalid start offset:-1\" shows up while deleting the bullets of a bulleted list', 'description': {'raw': 'Steps to reproduce:\\n\\nThere are several issues in this bug.I tried to document all of them chronologically in one issue for convenience.\\n\\n\\n1.click on the Edit button\\n2.click on the bullet list icon.\\n3.Click on tab to add indentation to the list for several times.\\n4.Now press Enter/Return\\n5.It deletes the bullets, where as pressing delete does not do that.\\n6.After deleting all the bullets by pressing return it goes to the next line \\n7.Again add bulleted list with indentation on the first line\\n8.Now this time if you press Enter it goes to the next line but does not add next bullet.\\n9.Now go to the end of the first line and press enter, this time the next bullet gets added.\\n10.Now try adding indentation to the second item , it does not work\\n11.Delete the bullet and repeat the action again,this time it will add indentation.\\n12.Now if you save the page , you will see there is no bullets in the read mode\\n13.If you try to delete all the content by selecting with mouse pad, it gives the error:\\n\"Uncaught Error:Invalid start offset:-1\"\\n\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nExample Page where in the read mode there is no bullets but in the edit mode they appear:\\n\\nhttp://en.wikipedia.beta.wmflabs.org/wiki/New_bullet\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395441510, 'spacePHID': None, 'dateCreated': 1386192540, 'dateModified': 1417572504, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58003', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Launching VE in some ways throws TypeError due to Multimedia Viewer dependency clash', 'description': {'raw': \"Screenshot of the error\\n\\nSteps to reproduce:\\n\\nStill Unknown.Will update once I get it.\\n\\nMostly it occurred to me when I reload an open editor after an idle time or switch from Edit Source to VE it does not the editor and shows the following error:\\n\\n\\nTypeError:Cannot read property 'Element' of undefined >TypeError\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12080}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386266393, 'spacePHID': None, 'dateCreated': 1386178920, 'dateModified': 1417572736, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57990', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Pre-fetch VisualEditor modules to improve load speed', 'description': {'raw': \"First impressions count! You can make the initial experience of loading VE substantially faster by prefetching the modules on a standard article page if the DOM isn't busy.\\n\\nWhat I have in mind is something like this:\\n\\n    $( window ).load( function () {\\n        if ( !mw.loader.store.enabled ) {\\n            return;\\n        }\\n\\n        setTimeout( function () {\\n            var modules = [\\n                'ext.visualEditor.base',\\n                'ext.visualEditor.core'\\n                'ext.visualEditor.data',\\n                'ext.visualEditor.icons-vector',\\n                'ext.visualEditor.mediawiki',\\n                'ext.visualEditor.viewPageTarget',\\n                'ext.visualEditor.viewPageTarget.icons-vector',\\n            ]\\n\\n            mw.loader.using( modules.filter( function ( module ) {\\n                var key = mw.loader.store.getModuleKey( module );\\n                return key in mw.loader.store.items;\\n            } ) );\\n\\n        }, 0 );\\n    } );\\n\\n\\nYou'd need to ensure that the modules don't execute automatically somehow.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'dateClosed': 1442609143, 'spacePHID': None, 'dateCreated': 1386109920, 'dateModified': 1721174890, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57952', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paragraphs merged into image captions by backspace', 'description': {'raw': \"Wiktext:\\n[[File:Image.jpg|thumb|Foo]]\\nBar\\n\\nPlace the cursor the the left of 'B' and press backspace\\n\\nExpected: Image is focused\\nResult: 'Bar' is moved into the image caption\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386268505, 'spacePHID': None, 'dateCreated': 1386086400, 'dateModified': 1417572738, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57927', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cache key is not cleared when surface is torn down', 'description': {'raw': \"1. Open VE on a page\\n2. Make a change\\n3. Go into save dialog, review diff\\n4. Close save dialog without saving\\n5. Click Read tab, click through warning that you'll lose your changes\\n6. Click Edit tab to open VE again\\n7. Make a change that's very different from #2\\n8. Go into save dialog, review diff\\n9. Observe that the diff displayed is for #2, not #7\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386095103, 'spacePHID': None, 'dateCreated': 1386033660, 'dateModified': 1417572742, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57905', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Snowmen being created (no reproduction steps)', 'description': {'raw': 'On fr.wp at least a couple of edits were noticed that generated snowmen:\\n\\nhttps://fr.wikipedia.org/w/index.php?title=D%C3%A9sir_mim%C3%A9tique&diff=98365348&oldid=96841726\\nand https://fr.wikipedia.org/w/index.php?title=Andromaque&diff=98765089&oldid=97860409 (a vandalism).\\n\\nThe snowman appears in the word \"français(e)\" (so it\\'s possibly related to the ç character?).\\n\\nNo other details available - the first editor didn\\'t provide them, and the other was a vandal.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407061838, 'spacePHID': None, 'dateCreated': 1386018180, 'dateModified': 1545086198, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57884', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: API module issues', 'description': {'raw': 'For action=flow:\\n* The \"flowaction\" parameter lacks a description.\\n* The \"page\" parameter lacks a description.\\n* The \"flowaction\" parameter does not list available actions.\\n* The \"params\" parameter is poorly documented. Passing a json blob of \"params\" is rather awful. I might rather see a setup where \"flowaction\" selects a submodule, along the lines of how action=query works, so these parameters could actually be documented in api.php.\\n* getExamples() should be properly implemented.\\n* getHelpUrls() should be implemented.\\n* I\\'m assuming at least some of the possible flowactions are write actions. isWriteMode() should therefore return true.\\n* I note that ApiBase is already a ContextSource, so there is no need for $this->getContext()->getUser() instead of just $this->getUser().\\n* I see you\\'re setting \"_element\" directly. Use ApiResult\\'s method to handle that instead, please. The same goes if you\\'re setting \"*\" directly anywhere.\\n* I see that sometimes the \"result\" element in the result will be an associative array and sometimes it will be the string \"error\". I\\'d rather see a \"status\" element of some sort that is always a string and have \"result\" always be an associative array when it is present.\\n* I see you have a \"doRenderer\" protected method that is never actually called.\\n\\nFor list=flow:\\n* The link returned by getHelpUrls() does not actually document this API module.\\n* The \"flowaction\" parameter does not list available actions.\\n* Same criticisms of the \"params\" blob as above.\\n* You are setting \"_element\" directly instead of using ApiResult\\'s methods.\\n* You should be checking the return from ApiResult\\'s addValue method and properly handling failure.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uqcn2l4ng4murmyfnvyp', 'ownerPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405325549, 'spacePHID': None, 'dateCreated': 1385566620, 'dateModified': 1602870080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57659', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursoring off generted content nodes (images/templates/references) causes DM/CE inconsistency in Firefox', 'description': {'raw': 'Steps to reproduce:\\n* Click on an image before a text node. The image will be marked as selected.\\n* Press rightarrow to cursor next to the text.\\n* Start typing. The text will be inserted backwards.\\n\\nCause:\\nAfter cursoring off the image, the selection is in the text node (and the cursor is flashing), but the focus is not.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54917'}, 'authorPHID': 'PHID-USER-lliyevigiycjbybglftk', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385495554, 'spacePHID': None, 'dateCreated': 1385483520, 'dateModified': 1417572744, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57600', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Annotate body tag or #content tag when in edit mode with class', 'description': {'raw': 'Other modules (and gadgets) should be able to hide their interfaces when VisualEditor is opened - for example the Nearby pages BetaFeature (https://www.mediawiki.org/wiki/Beta_Features/Nearby_Pages) creates a blue button in the top right.\\n\\nIdeally this feature should be able to know when it is in edit mode and hide itself.\\n\\nMaybe abusing the action-edit / action-view classes would be useful here?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385506305, 'spacePHID': None, 'dateCreated': 1385409780, 'dateModified': 1417572744, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57555', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor jumps to the beginning of first line after changing the heading format of a text in an article', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button in a page\\n2.Select a text by dragging with mouse control.\\n3.Change the heading format of the text to any format for example:heading/paragraph etc.\\n\\nObserved Result:\\nThe cursor moves to a position which is the middle of the first and second line of the page\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58998\\n\\n**Attached**: {F12046}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393452987, 'spacePHID': None, 'dateCreated': 1385407560, 'dateModified': 1443276339, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57552', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MWExtensionInspector does not take directionality from context when creating', 'description': {'raw': \"https://gerrit.wikimedia.org/r/#/c/96984/ adds a workaround for the fact that getting the directionality from the FocusedNode doesn't work if there is no node focused (i.e. in creation mode), but it doesn't add any alternative logic for getting the directionality. We should look at the context in the CE tree somehow and figure out what directionality to use. Right now it just defaults to the UI directionality.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386967035, 'spacePHID': None, 'dateCreated': 1385125260, 'dateModified': 1417572735, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57421', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Auto-numbering CSS for external links should also apply to generated content', 'description': {'raw': 'At the end of the first paragraph there is reference #1.\\nIf you scroll to the reference list, it will look empty.\\n\\nActually, the reference, which can be edited, contains an unnamed link. \\nThe markup guide for en.wp says these links are \"Only used within article body\\nfor footnotes\", so it makes sense that VE should display them correctly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/w/index.php?title=User:Elitre_%28WMF%29/sandbox&veaction=edit\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57419'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385497110, 'spacePHID': None, 'dateCreated': 1385124180, 'dateModified': 1417572744, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57420', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar utilities menu items should not be cut off against browser edge', 'description': {'raw': '**Author:** `swalling`\\n\\n**Description:**\\nScreenshot from mediawiki.org\\n\\nThe box that appears on hover around dropdown menu items overlaps with the text for the \"Switch to source editor\" option. (See attachment)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12471}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409876443, 'spacePHID': None, 'dateCreated': 1385060520, 'dateModified': 1443278218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57366', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawning and reversed typing in Firefox', 'description': {'raw': '**Author:** `Wikifram`\\n\\n**Description:**\\nThere are a number of bugs about pawns and/or reverse typing, many of them \"resolved fixed\". But it is clear that in many circumstances, on different wikiversions, pawn characters and reverse typing still occur. \\n\\nSee [[en:Wikipedia:VisualEditor/Feedback#Line with template, pawn]] (and the linked sections on fr-wiki as well) for an explanation of some scenarios when this occurs. This has, in various guises, been reported since the first deployment of VE, and none of the fixes seem to have been permanent or fundamental. Can this please be tackled?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385472098, 'spacePHID': None, 'dateCreated': 1385030100, 'dateModified': 1417572745, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57347', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Change event reaction order', 'description': {'raw': \"The current event reaction order means that many IMEs including jQuery.IME and a number of Windows built-in input methods don't work in VE; we should change it to something that does – needs investigation as to what order is right.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '160', 'subtype': 'default', 'closerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'dateClosed': 1424368837, 'spacePHID': None, 'dateCreated': 1384939680, 'dateModified': 1424548950, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57290', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] References created in media item captions no longer appear in reference lists', 'description': {'raw': 'Regression of bug 52427.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413925579, 'spacePHID': None, 'dateCreated': 1384844400, 'dateModified': 1417571297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57228', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Cutting text undoes previous typing', 'description': {'raw': \"Intention:\\nCopyedit a page\\n\\nSteps to Reproduce:\\n1. Open a page with pre-existing content.\\n2. Type or change some of the text (I was adding a new first line).\\n3. Select and cut (⌘ Command+x) some pre-existing text (I cut mine from the end of the third line).\\n4. Notice that what you typed on the first line has been undone.\\n5. Paste what you cut (in my case, at the end of the first line).\\n6. Notice that what you typed on the first line has been redone.\\n\\n\\n\\nExpected Results:  \\nThat text would not magically disappear and reappear.\\n\\nReproducible: Always\\n\\nI experienced this on office.wikipedia.org using Safari 6 on Mac OS 10.7.5.  It was confirmed at en.wikipedia.org using Vector/Chrome 30/Windows 7, with the additional discoveries that:\\n\\nIf you type your new first line all in one go (so that 'undo' would remove the whole first line), the first character of the new line remains present.\\n\\nThe undone text only reappears if you paste your cut text onto the line with the now-missing text.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58724\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409345286, 'spacePHID': None, 'dateCreated': 1384818060, 'dateModified': 1443278218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57217', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: First character added to a blank dialog entry box (reference or caption) is mis-placed and never makes it into DM in Firefox', 'description': {'raw': \"With Vector in FF.\\nTry to add a caption to an image:\\nthe words will be splitted on multiple lines, with the first letter being automatically placed on the second line, the other letters on the first one, and no ability to fix this.\\n\\nI understand that https://bugzilla.wikimedia.org/show_bug.cgi?id=38129 is coming but I thought I'd file this anyway.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384923911, 'spacePHID': None, 'dateCreated': 1384811940, 'dateModified': 1417572751, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57211', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'MobileFrontend: VisualEditor loads without a cursor due to blurring of all CE elements', 'description': {'raw': \"On desktop, as soon as the visual editor is loaded, the cursor is activated at the beginning of the page content. This doesn't happen in the mobile version.\\n\\nClicking on the page content after the editor has loaded then has inconsistent behavior between browsers. In Firefox, clicking anywhere in the page content inserts the cursor at the beginning of the content. In Webkit browsers, it inserts the cursor at the click location.\\n\\nI believe that fixing the first problem will also fix the second problem in for free.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67389\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67390\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67399\"}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405637552, 'spacePHID': None, 'dateCreated': 1384765200, 'dateModified': 1405637552, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57177', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow links in Flow topic titles', 'description': {'raw': 'When a topic title includes an internal link, the title should render as a working link in the topic header.\\n\\nThis will use the edit summary parser.\\n\\nExamples: \\nThe topic title is [[Foo]] -- it will render as Foo -- a link to the article page Foo.\\nThe topic title is [[Foo|Bar]] -- it will render as Bar -- a link to the article page Foo.\\n~~The topic title is [http://foo.com Foo] -- it will render as Foo -- an external link to foo.com.~~ (We decided to use the edit summary parser, which does not support this.)\\n\\nNOTE #1: For posts, replies and edits to a post/reply -- in watchlist, recent changes and contributions, there will be a blue link that says Foo -- but this will NOT be a link to the article page Foo. It will be a link to the Topic:UUID. See screenshots below. \\n\\nNOTE #2: In topic history, board history, watchlist, recent changes and contributions, when there is a change to the topic summary, or moderation actions, the topic title will be rendered as Foo, no link. \\nFor example: created topic summary on Foo\\n\\n**Topic heading -- this should be a working link**\\n{F250640}\\n\\n**Contributions** -- \\nFor the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.\\nFor editing the topic summary, the link should render as the title, not linked.\\n\\n{F250665}\\n\\n**Recent changes** --\\nFor the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.\\nFor editing the topic summary, the link should render as the title, not linked.\\n\\n{F250670}\\n\\n**Watchlist** --\\nFor the post/reply/edit, the link should render as the title (no brackets), and should link to the Topic:UUID, not to the page.\\nFor editing the topic summary, the link should render as the title, not linked.\\n\\n{F250675}\\n\\n{F250677}\\n\\n**Board and Topic history** --\\nFor both post/reply/edit and editing the topic summary, the link should render as the title, not linked.\\n\\n{F250682}\\n\\n{F250686}\\n\\nSee {T115910}.\\n\\n---\\n\\nprevious version of the ticket: \\n\\nFlow: Wikitext formatting (such as [[links]] and \\'\\'italics\\'\\') doesn\\'t work in topic titles\\n\\nWhen you create a new Flow thread, there\\'s a \"topic\" field. This topic field is analogous to the \"subject\" field in a wikitext talk page. The topic field currently cannot support wikitext.\\n\\nExample: http://ee-flow.wmflabs.org/w/index.php?title=Sandbox&workflow=0509a3b2518b34dffb6efa163e68c4ac&action=view\\n\\nTopic input: \"here\\'s a new [[topic]]\"\\n\\nExpected behavior: \"[[topic]]\" becomes an internal hyperlink\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: http://ee-flow.wmflabs.org/w/index.php?title=Sandbox&workflow=0509a3b2518b34dffb6efa163e68c4ac&action=view\\n**See Also**:\\n* {T23445}\\n* {T59950}\\n* Tech News posts to LQT pages converted to Flow: https://www.mediawiki.org/wiki/Topic:Siez4a3hsji86cay\\n\\nhttps://trello.com/c/bj3IZSE5/190-limited-wikitext-formatting-in-topic-titles'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'dateClosed': 1449191233, 'spacePHID': None, 'dateCreated': 1384740180, 'dateModified': 1660398841, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57153', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Google Chrome's auto-translate of the contentEditable surface is very confusing for users\", 'description': {'raw': 'This isn\\'t a VE bug but ...\\nWith google translate and chrome when you choose \"always translate\" and then hide the translate bar, the look and feel is really WP:en or WP:yourlanguage\\n\\nWhen you choose to contribute with VisualEditor, everything is translated : text, button, message but the little \"search\" in the research box.\\n\\nThen contributions in different language appear on WP:fr ex : https://fr.wikipedia.org/w/index.php?title=Acrosport&diff=prev&oldid=98352033\\n\\nA little change in text saves the all translated bloc.\\n\\nMaybe, the VE edit button should be block with a warning message or the text display for edition should block google translate (I don\\'t know if it\\'s possible) like textarea does.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Whiteboard**: aklapper-moreinfo'}, 'authorPHID': 'PHID-USER-hhw22zfd2xzrsyc22lp5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427750456, 'spacePHID': None, 'dateCreated': 1384560300, 'dateModified': 1427750745, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57124', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: SurfaceObserver sets selection to start of document after closing reference dialog in Chrome', 'description': {'raw': '1. Edit an existing reference or insert a new one\\n2. When the dialog is closed, the reference is selected and a callout is displayed\\n3. 200ms later the selection moves to the start of the document\\n\\nSomehow, for some reason, SurfaceObserver is \"fixing\" the selection here.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394659143, 'spacePHID': None, 'dateCreated': 1384381260, 'dateModified': 1417572576, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57034', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Editor got unresponsive after a reference gets placed in a wrong position', 'description': {'raw': 'reference icon after the selected text\\n\\nSteps to reproduce:\\n\\n1.Click on the edit button for a blank page\\n2.Type a text on the first line\\n3.Now type another text on the second line\\n4.Add a template\\n5.Select the second text in a way that it also selects the template\\n6.Click on More>Reference \\n7.Add a reference\\n\\n\\n[Note] This might not be the exact steps to reproduce , I am trying to figure out the correct steps.I will update the steps once I am sure.Still filing it to keep track.\\n\\nObserved Result:\\nThe reference note gets added in the middle of the template and the second line in a blank line.After that the editor gets unresponsive\\n\\nAlso sometimes the reference icon gets added at the beginning of the first line\\n\\nSee the screenshot attached.\\n\\nBrowser:Chrome 26\\nEnvironment:test 2\\nOS: MAC OS X 10.8.5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12555}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398451871, 'spacePHID': None, 'dateCreated': 1384305720, 'dateModified': 1417572405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56982', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Switch to wikitext feature gives an Edit conflict warning when editing from IP', 'description': {'raw': \"I thought it was Opera's fault,\\nbut tested this again today and it's not related to the browser you're using.\\nIt appears that when you edit as an unregistered user (on wikis which allow you to...) you'll always get an Edit conflict page when you try to save after you switched to wikitext.\\nTested on multiple wikis on both ns0 and ns2.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56767\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396640124, 'spacePHID': None, 'dateCreated': 1383991740, 'dateModified': 1443276347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56835', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Indent and list-related icons' direction should depend on content dir and not GUI dir\", 'description': {'raw': 'Right now, CSSJanus flips toolbar icons by their definitions, so an icon indent-ltr would automatically turn to indent-rtl when user GUI is set to RTL.\\n\\nHowever, the indent and list-related buttons don\\'t depend on user GUI language but rather on the content language. If editing English content, the icon for \"increase indent\" should point from left to the right regardless of user GUI language, and the icon for \"decrease indent\" should point the other way.\\n\\nFor a quick demo, see:\\nhttps://www.mediawiki.org/wiki/User:Mooeypoo/IndentDemo?veaction=edit&setlang=he\\n(Wiki language is English/LTR and GUI is Hebrew/RTL)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386783624, 'spacePHID': None, 'dateCreated': 1383965220, 'dateModified': 1417572739, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56821', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Newlines after </li> cause dirty diffs with Parsoid', 'description': {'raw': \"We would like to revert the fix for bug 39617.  That bug should have been fixed via the 'whitespace' CSS property.\\n\\nThe 'fix' to bug 39617 caused Parsoid to begin creating dirty diffs (and failing its test suite) -- see https://gerrit.wikimedia.org/r/92978\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=39617\"}, 'authorPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404842267, 'spacePHID': None, 'dateCreated': 1383947760, 'dateModified': 1404842267, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56809', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspectors break up or appear in the wrong place after coming back from another window', 'description': {'raw': 'Misplaced\\n\\nSteps to reproduce\\n\\n1. Click on the Edit button for an article or click on the media icon on a image\\n2. Type something\\n3. Go to some other window of your browser\\n4.Come back to the editor after few minutes (approx. 5-10 minutes)\\n5.Now select the text and click on the link icon \\n\\nObserved Result:\\nThe link inspector appears broken or misplaced \\n\\n\\n\\nBrowser:Chrome\\nEnvironment:test2\\nPage:Any\\nReproducible: Mostly  \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12157}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398720912, 'spacePHID': None, 'dateCreated': 1383942000, 'dateModified': 1417572402, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56801', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The direction of the <textarea> in extension tags editor must correspond to the surrounding content direction', 'description': {'raw': \"Currently, if I go to https://www.mediawiki.org/wiki/User:Amire80/ve-poem and edit it using VE, I can edit the content of the <poem> tag. If my UI language is Hebrew, then the <textarea> for editing the poem is RTL. I would expect it to be LTR.\\n\\nIdeally the default direction for the <textarea> that this feature should be the direction of the surrounding text. If it's hard to get, then the direction of the page's content will probably suffice. (Currently it will be the same as the content language of the wiki, but it may change some day when we finally introduce page language.)\\n\\nThere can also be some tags for which the default direction must be different, such as <source>, but that's an issue for a separate bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383939037, 'spacePHID': None, 'dateCreated': 1383920040, 'dateModified': 1417572755, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56779', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switch to wikitext feature does not return in Firefox', 'description': {'raw': 'There are 2 users at least (Fram and myself)\\nreporting that the new option does not seem to work when using FF (in our case, version 25).\\nI tried to VEdit my sandboxes in several languages.\\nYou can use https://it.wikipedia.org/wiki/Utente:Elitre/Sandbox?veaction=edit if you need to.\\nAfter you click on the Switch button, and click OK on the warning message, the surfaces is \"grayed out\", and just stays that way without actually switching.\\nPlease notice you can still VEdit at this time, and even save.\\nThe chosen skin instead does not seem to matter (it didn\\'t work for me with any of them).\\n\\nIn Fram\\'s words:\\n<< I get the \"you are about to change\" message, but then the VE page gets \"bleached\" out, as if an opaque glass is put in front of it, and nothing further happens. I can still use the toolbox at this time, and can edit the article in VE, but it doesn\\'t have the normal look.>>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56835'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384864435, 'spacePHID': None, 'dateCreated': 1383909600, 'dateModified': 1417572681, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56767', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'localStorage nearly or totally filled with routine operation', 'description': {'raw': 'beta commons localStorage nearly full\\n\\nseen on beta labs while logged in as Selenium_user\\nseen in Chrome/Chromium, not checked in Firefox (yet)\\n\\nconsistent behavior seen:  \\ninitial load of VisualEditor in beta enwiki sets localStorage to 3.5MB\\ninitial load of UploadWizard in beta commons sets localStorage to 2.5MB\\n\\nroutine navigation to pages like \\n* wikitext editor\\n* Flow e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA\\n* Special:NewPagesFeed\\n* etc\\n\\ncontinues to fill localStorage until it maxes out.\\n\\ninconsistent behavior: \\n\\nI do not have a consistent repro to max out localStorage.  at first I thought that repeatedly hitting shift-reload/cancel on a ?veaction=edit page did it, but on my second attempt I was unable to max out localStorage that way\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56778\\n\\n**Attached**: {F12036}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1426116671, 'spacePHID': None, 'dateCreated': 1383847740, 'dateModified': 1426116671, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56728', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The handler MWCategoryWidget#onLookupInputKeyDown is not actually bound to anything', 'description': {'raw': \"For some reason, the 'keydown' event is being unbound when the suggestions popup appears, so the function is never firing. However, it seems like they shouldn't be listening to keydown anyway because they only care about when the enter key is pressed and that event is already available on the input as the 'enter' event (from OO.ui.TextInputWidget).\\n\\nWith love from the Wikia development team.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412973234, 'spacePHID': None, 'dateCreated': 1383782580, 'dateModified': 1417571322, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56700', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor in Flow: CE arrives much later than controls', 'description': {'raw': 'this may be more appropriate to assign to VisualEditor than Flow:\\n\\nin a fresh instance of the Chrome browser, log in and go to page http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA \\n\\n* click Start a new topic\\n* watch the spinner as VisualEditor loads up\\n* when the spinner stops and the editor controls are visible, attempt to type in the ContentEditable surface\\n\\n* only some seconds after the spinner stops and the controls appear is it possible to place the cursor in the CE surface and begin typing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386881313, 'spacePHID': None, 'dateCreated': 1383754500, 'dateModified': 1387247486, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56677', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Math inspector does not check type of node it's inspecting\", 'description': {'raw': 'Link inspector and Math inspector together\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit beta\\n2.Add a media such as image\\n3.Now open the Math inspector from More>Latex\\n\\nObserved Result:\\nThe Math inspector does not open,Now if you click on link both the inspectors open together.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12805}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397694799, 'spacePHID': None, 'dateCreated': 1383698100, 'dateModified': 1443276351, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56645', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Move OOjs and OOjs-UI to their own repos', 'description': {'raw': 'Currently OOjs is mastered in github(!) and OOjs-UI within VisualEditor; instead, they should be in their own repos so that other projects can re-use them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383932971, 'spacePHID': None, 'dateCreated': 1383587220, 'dateModified': 1390523805, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56571', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide a mechanism to transclude/include translatable templates', 'description': {'raw': 'If a template is made translatable, {{template}} no longer works as expected. While this is hard to fix, Translate extension should provide out of the box the functionality of https://www.mediawiki.org/wiki/Template:Translatable_template.'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'dateClosed': 1458719744, 'spacePHID': None, 'dateCreated': 1383283200, 'dateModified': 1458719744, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56451', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Image alt attribute resolves without alt= in wikitext', 'description': {'raw': \"This is related to bug #48924 and came up while working on VE's new media dialog.\\n\\nSymptoms :\\n1. Parsoid seems to ignore adding an alt attribute to an image that had no alt attribute previously -- the image still has no alt attribute post-save, even though the DM/CE in VisualEditor were both updated properly.\\n\\n2. When the alt string in 'alt=something' is changed, the resulting wikitext post-save is produced without the 'alt='\\n\\nSo, an original wikitext:\\n\\n[[File:Someimage.png|thumb|265x265px|some caption|right|alt=some alternate text]]\\n\\nAfter editing the alt property in VE, the wikitext post-save becomes:\\n\\n[[File:Someimage.png|thumb|265x265px|some caption|right|some alternate edited text]]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392847490, 'spacePHID': None, 'dateCreated': 1383174540, 'dateModified': 1392847490, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56400', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When cursor ends up outside of a content branch node, move it back into one', 'description': {'raw': 'Document:\\n\\n h2> Foo\\n p> Lorem ipsum.\\n h2> Bar\\n p> Bla bla bla.\\n\\nSteps:\\n\\n* Put cursor in the first heading between \"F\" and \"oo\".\\n* Change text style to paragraph (via menu or or use ctrl-0).\\n* Observe cursor going wild (disappears in Firefox, appears outside the document in the margin in Chrome, bug 50442)\\n* Type 3 characters (\"a\", \"b\", \"c\")\\n\\nFirefox result:\\n\\n3 new paragraph appear.\\n\\n p> o [new]\\n p> o [new]\\n p> a [new]\\n p> Foo\\n p> Lorem ipsum.\\n\\nAnd more on every subsequent keystroke. It seems to have copied this \"o\" from \"Foo\" somehow. And \"b\" and \"c\" never appear.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399418779, 'spacePHID': None, 'dateCreated': 1383076620, 'dateModified': 1443276353, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56340', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Changing text formatting dislodges the text cursor', 'description': {'raw': 'Screenshot of problem.\\n\\n1. Put cursor in a heading.\\n2. Change text style to paragraph (or use ctrl-0).\\n3. Observe the cursor is now outside the content area in the document margin.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12115}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386028032, 'spacePHID': None, 'dateCreated': 1383076200, 'dateModified': 1417572742, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56338', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Text formatting menu issues', 'description': {'raw': \"The text style menu has major issues. For all intends and purposes I declare it completely broken. Tracking them here in case they're related.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386028091, 'spacePHID': None, 'dateCreated': 1383076080, 'dateModified': 1470526571, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56336', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unexpected RETURN character upon first editing a page', 'description': {'raw': 'page after typing one character\\n\\nseen in Firefox not Chrome in master as of Oct 28\\n\\nEdit any page on http://en.wikipedia.beta.wmflabs.org\\n\\nWhen VE manifests, type any character\\n\\nExisting text of page jumps down one line, as if VE has inserted a RETURN command upon typing in the page. \\n\\nSeen only in Firefox, not Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56642\\n\\n**Attached**: {F12001}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384856020, 'spacePHID': None, 'dateCreated': 1382992380, 'dateModified': 1417572750, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56274', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Prevent application of link annotations to references', 'description': {'raw': '**Author:** `Wikifram`\\n\\n**Description:**\\nThis test edit[https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=809490&oldid=795427]: all I did was add [[Test]] at the end of the sentence (to check basic nowiki functionality in the new release 23). However, VE started moving the nowikis around, and now the ref, which was in the old diff a nice \"1\", is now a strange string, \"\\x7fUNIQ74171d8572aa65a1-nowiki-00000018-QINU\\x7f1\\x7fUNIQ74171d8572aa65a1-nowiki-00000019-QINU\\x7f\". This will probably be a rare occurrence, so not urgent in that regard, but it may be indicative of other problems.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384860606, 'spacePHID': None, 'dateCreated': 1382974020, 'dateModified': 1453560947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56250', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Vertical keyboard selection (shift+up/down cursor) over a node type boundary gives unexpected results in Firefox', 'description': {'raw': '**Author:** `Wikifram`\\n\\n**Description:**\\nI had entered this at enwiki VisualEditor/Feedback, but got no response. Apparently no bug for this has been filed, even though it is quite serious. All links are for pages on enwiki. \\n\\nI\\'m trying to select one template, but get unexpected results. If you go to [[Karl Popper]], put the cursor at the start of the header \"Backdrop to his thought\", and use the left side \"caps arrow\" plus the up-arrow from the four direction arrows (to select the line above it), the first time you do this, your cursor disappears. The second time, you select everything including half a line of the paragraph \\'\\'above\\'\\' the \"philosophy\" section header, the philosophy section header, and the \"main\" template. This is rather unexpected. \\n\\nSimilarly, only using the \"up\" arrow, starting again at the same place: first time, the cursor seems to disappear (looking more closely, it stands at the right side of the infobox, at the height of the \"main article\" template. Using it again movs it to the middle of the last line of the previous paragraph, skipping the template and the \"philosophy\" section header. \\n\\nThe reverse is even worse. Starting from the paragraph above the \"philosophy\" header and using the \"down\" arrow, your cursor moves to the end of the \"philosophy\" header (good!); using \"down\" again, it moves to the right of the infobox (at the same line as the \"main article\" template) (not good, perhaps acceptable); using down again, and again, and again, does absoluetly nothing anymore... \\n\\nStranger and stranger: going from the \"philosophy\" header using the right button works like a charm. If you then start using the \"up\" arrow though, you are no longer scrollong inside the text, but yo uare scrolling the whole webpage instead... I stopped testing after this, having had more than enough of this!\\n\\nBasically, the use of arrows in VE shows some very bizarre behaviour and should be thoroughly tested and bugfixed. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 15:02, 25 October 2013 (UTC)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51957'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420844427, 'spacePHID': None, 'dateCreated': 1382972940, 'dateModified': 1438734466, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56248', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Optimistically submit HTML to Parsoid for serialisation as soon as user clicks \"Save page\"', 'description': {'raw': 'Perceived performance could be substantially improved by having VisualEditor optimistically request serialization of the DOM as soon as the user hits \"Save page\". If the user ends up canceling the save, the serialized DOM would be discarded.\\n\\nUsers that take a few seconds to write the edit summary before confirming the save would experience near-instant saves this way.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55979'}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385139244, 'spacePHID': None, 'dateCreated': 1382470140, 'dateModified': 1449707215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56011', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't re-serialise HTML into wikitext through Parsoid after preview, but retain\", 'description': {'raw': 'Previewing a page and then saving it without further modifications should result in one serialization request being made to Parsoid, not two. The serialized DOM generated in course of responding to the preview request should be re-used when saving whenever VisualEditor can determine that no modifications intervene these two operations.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56011'}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385139234, 'spacePHID': None, 'dateCreated': 1382397660, 'dateModified': 1417572749, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55979', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: An empty edit notice is appearing at every page', 'description': {'raw': 'An empty edit notice is now appearing on any page.\\n\\nTested on Firefox and Safari\\n\\nhttps://en.wikipedia.org/wiki/LibreOffice?veaction=edit\\nhttps://en.wikipedia.org/wiki/Maxi_single?veaction=edit\\nhttps://en.wikipedia.org/wiki/Northeim?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394495869, 'spacePHID': None, 'dateCreated': 1382307480, 'dateModified': 1394495869, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55951', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When adding a new template, auto-open the \"add parameter\" section and put the cursor in the search dialog\\'s input when we tab to it', 'description': {'raw': 'Intention:  Add a parameter to a template.\\n\\n\\nExpectation:  That the cursor would automatically be present in the \"Add parameter\" text field (where it says \"Parameter name\"), so we could just start typing without having to reach for the mouse.\\n\\n\\nSteps to reproduce and results:\\n\\n1)  Add or open any template.\\n\\n2)  Start typing the name of a parameter.\\n\\n3)  Discover that you are no longer able to just start typing the name, but must first reach for the mouse or trackpad, and then click to put the cursor inside the only possible place where you might be typing on that screen.\\n\\n\\nThis was reported as a new and undesirable behavior with MediaWiki version 1.22wmf21, by a user who normally uses Firefox 24, Windows 8 and Vector skin and confirmed in Safari 6 on a Mac.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406072223, 'spacePHID': None, 'dateCreated': 1382221620, 'dateModified': 1443278223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55925', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When a template is completely empty, it is invisible in CE', 'description': {'raw': 'This bug came about from a misspelled parameter in a template on hewiki. The template returned a completely empty result when the required parameter was invalid, and there was no place to hover above the template and access the transclusion icon to change or remove it.\\n\\nTo replicate:\\n* Go to https://he.wikipedia.org/wiki/%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%D7%AA:Mooeypoo/%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99/%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_%D7%95%D7%9E%D7%A9%D7%97%D7%A7%D7%99%D7%9D?veaction=edit\\n* Click on transclusion, and add the template \"ערך מורחב\"\\n* Add parameter with the name \"1\"\\n* Add value to the parameter (invalid value) - \"[[blah]]\"\\n* Apply and click anywhere else on the document to clear the selection - the template vanished. However, it was added to the wikitext and is in the page after save, but there\\'s no way to access it from VisualEditor and remove it (or edit it)\\n\\nI have an idea on how to solve that, but I am not sure if the issue isn\\'t deeper.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382982243, 'spacePHID': None, 'dateCreated': 1381957920, 'dateModified': 1417572819, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55810', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Highlights, resize handles, etc. not repositioned on window resize', 'description': {'raw': \"If you have a right-floating image, select it by clicking on it, then make the window wider on the right-hand size, the image moves to the right but the highlight doesn't. Same goes for resize handles etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55787\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402446907, 'spacePHID': None, 'dateCreated': 1381931100, 'dateModified': 1443278227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55789', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method clearMessage\"', 'description': {'raw': \"Uncaught TypeError: Object #<VeInitMwViewPageTarget> has no method 'clearMessage'\\n\\nAppears to be thrown by line 792 of modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.js: 'this.clearMessage( 'captcha' );'.\\n\\nSeen on MediaWiki.org after trying to solve a Captcha, in the process of saving an edit to <https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team/Quarterly_review%2C_October_2013>.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381879688, 'spacePHID': None, 'dateCreated': 1381818480, 'dateModified': 1417572821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55726', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Exception after call_user_func causes error (PHP Notice: Undefined index: file, PHP Notice: Undefined index: line)', 'description': {'raw': \"Cause an exception from something with call_user_func in its stack.\\n\\nFor example, if you use wfUseMW( '2000.0' ); inside VisualEditor::onSetup (wgExtensionFunctions), you get:\\n\\n\\n\\nNotice: Undefined index: file in /includes/Exception.php on line 725\\nNotice: Undefined index: line in /includes/Exception.php on line 725\\nNotice: Undefined index: file in /includes/Exception.php on line 725\\nNotice: Undefined index: line in /includes/Exception.php on line 725\\n\\nMediaWiki 2000.0 required--this is only 1.22alpha\\n\\nBacktrace:\\n\\n#0 /extensions/VisualEditor/VisualEditor.hooks.php(23): wfUseMW('1.229wmf11')\\n#1 (): VisualEditorHooks::onSetup()\\n#2 /includes/Setup.php(592): call_user_func('VisualEditorHooks::onSetup')\\n#3 /includes/WebStart.php(153): require_once('/includes/Setup.php')\\n#4 /index.php(46): require('/includes/WebStart.php')\\n#5 {main}\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382977275, 'spacePHID': None, 'dateCreated': 1381515180, 'dateModified': 1382977275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55634', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Get rid of selection rendering on init', 'description': {'raw': \"Problems:\\n* The dm.Surface constructor initializes the selection at (1,1) because (0,0) is not a selection we can render in most documents\\n* ui.Surface.initialize has the following code:\\n// By re-asserting the current selection and forcing a poll we force selection to be something\\n// reasonable - otherwise in Firefox, the initial selection is (0,0), causing bug 42277\\nthis.model.getFragment().select();\\nthis.view.surfaceObserver.pollOnce();\\n* However, when VE loses focus then regains focus, we don't restore the selection\\n\\nIssues caused:\\n* Selections of (1,1) don't play nice with documents that start with a FocusableNode\\n* The fact that ui.Surface.initialize reasserts the selection means that VisualEditor focuses itself on initialization, which Flow is now having to work around\\n* When ULS blurs then refocuses VE during its initialization, the selection jumps back to the top\\n\\nWhat we should really be doing:\\n* Initialize the selection at the first content offset (this is 1 for most documents, but will be different for documents that start with a FocusableNode)\\n* Get rid of the model->view->model circular synchronization in ui.Surface.initialize and fix whatever problems it fixed differently\\n* Restore selection on focus\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391663171, 'spacePHID': None, 'dateCreated': 1381324560, 'dateModified': 1417572594, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55510', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Deprecate 'live' in favor or 'setup' and 'teardown'\", 'description': {'raw': \"Right now we emit both 'live' and 'setup'/'teardown' , and some classes listen to 'live' while others use 'setup'/'teardown'. We should converge on using setup/teardown and remove live.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406080767, 'spacePHID': None, 'dateCreated': 1381315200, 'dateModified': 1443278227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55505', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link inspector suggestions sometimes aren't displayed in Firefox\", 'description': {'raw': 'Tested on both the Italian and the English Wikipedia a few days ago;\\nReach the bottom of any page: the link inspector does not present the\\nlist of options.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55343'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402549384, 'spacePHID': None, 'dateCreated': 1381236120, 'dateModified': 1441912147, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55465', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Quotes and whitespace normalized in unedited <ref> tags', 'description': {'raw': 'Filing this since subbu wanted to take a closer look (\"Yes, VE/Parsoid shouldn\\'t be making dirty diffs -- and these kind of dirty diffs is an exception rather than the rule. This is a bug.\"):\\n\\n<<VE seems to make unnecessary changes. I wouldn\\'t mind so much if it always helped to maintain the layout of invisible elements, but normally it just screws them (like infoboxes, or position of templates), without any effect on the rendered page but with a less easily readable wikitext editing window.\\nWhat I notice now though are totally unnecessary and hard to explain changes to ref names. For some reason, VE decides that all ref names need to be in quotes, which is not true at all and doesn\\'t help one bit. It also decides that between the final quote and the forward slash, there needs to be a space. All this has no effect on the rendered page, and doesn\\'t make the wikitext page any easier (or harder) to read, so why does VE bother doing this, which only helps to make diffs a lot longer.\\nTake a look at e.g. [10]: can you easily see if any significant change has been made, and what that may be?\\nFirst difference; <ref name=\"globsec-arjun\"/> becomes \\n<ref name=\"globsec-arjun\" /> Further: <ref name=nomorearjuns> becomes <ref name=\"nomorearjuns\">\\nand so on. I have not found the actual significant difference between the old and new version. What is the purpose and benefit of this? If VE would always make the \"invisible\" layout clearer and better, fine, but VE doesn\\'t care one bit about wikitext layout, so I don\\'t get this useless editing. Fram (talk) 09:27, 7 October 2013 (UTC)>>\\n\\nhttps://en.wikipedia.org/w/index.php?title=Arjun_%28tank%29&curid=7648336&diff=576092971&oldid=575064244\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1418854972, 'spacePHID': None, 'dateCreated': 1381222380, 'dateModified': 1428438967, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55461', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'mediawiki.notification: div#mw-notification-area remains visible and steals events after dismissing notification', 'description': {'raw': '1. Trigger a notification\\n2. Click on the notification to dismiss it\\n3. The notification area (<div id=\"mw-notification-area\">) is now empty, but still obscures a narrow strip in the top right corner:\\n\\n> $(\\'#mw-notification-area\\').outerHeight()\\n12\\n> $(\\'#mw-notification-area\\').outerWidth()\\n269\\n> $(\\'#mw-notification-area\\').position()\\nObject {top: 89.59375, left: 1251.203125}\\n> $(\\'#mw-notification-area\\').css(\\'z-index\\')\\n\"10000\"\\n\\nThis is a problem because the div steals events and mouse interaction from the UI elements below it. For instance, in VisualEditor:\\n1. Open a page in VE\\n2. Type \\'[[\\'. The wikitext warning appears\\n3. Click the warning to dismiss it\\n4. Reveal #mw-notification-area in the inspector and observe how it\\'s on top of part of the save button\\n5. 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409942617, 'spacePHID': None, 'dateCreated': 1381220760, 'dateModified': 1409942617, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55457', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying text sometimes makes the page jump/scroll in Firefox', 'description': {'raw': \"1. Edit a page with VisualEditor.\\n2. Copy a line of text.\\n\\nSometimes it just copies the line to the clipboard without generating any move of the content (expected behavior). But sometimes just by typing ctrl-C with text selected you will see a jump of the page.\\n\\nI haven't found the pattern, but it looks like doing this close to the end of long pages makes it easier to reproduce.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409237218, 'spacePHID': None, 'dateCreated': 1381170060, 'dateModified': 1417571856, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55433', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Opening the drop-down for a category in the page settings > category pane can cause a category entry to be duplicated', 'description': {'raw': 'Fram reports:\\n<<Having looked a bit more at categories, I encountered another strange phenomenon. On Opel Laubfrosch https://en.wikipedia.org/wiki/Opel_Laubfrosch, which has a lot of categories, the order of the cats on the page settings tab changes. Initially I get 8 categories, from \"Opel vehicles\" to \"compact cars\". But when I e.g. click on the drop down button next to 1920s automobiles, and then click again in the \"categories\" window (to close the drop down without any changes), I get 10 cats instead of 8, and in a different order. \"Vehicles introduced in 1924\" and \"Sedans\" are doubled (explaining the increase from 8 to 10), and the 3rd one is now no longer \"1920s automobiles\" but \"1930s automobiles\"... This can go on for quite a while, with the occasional disappearance of a cat as well apparently (normally the last one). Things start to break down, with the page settings then no longer working, or it being no longer possible to add a cat, and so on.>>\\n\\nI can confirm what he says, and this bug does not look browser or skin specific.\\nVE will let you save in a situation where you have these cats duplicated, and a \"saved edit\" message will also pop-up, but there will be no trace of the edit in the history. Plain removal of all the categories works fine instead: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2Fsandbox&diff=576123603&oldid=576122965 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408096666, 'spacePHID': None, 'dateCreated': 1381145460, 'dateModified': 1417571940, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55405', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: FocusableNodes (e.g. Infoboxes) are too easy to accidentally delete, especially when floated', 'description': {'raw': 'Erik Moeller: \"\\nI agree with previous commenters that this is likely to be at the cause of a\\nlot of the accidental infobox deletions and such. I understand it\\'s a tricky\\nissue, but the current behavior is extremely confusing from the user\\'s point of\\nview, so we need to look at some viable solutions. \\n\\nRecapping the simple case: User is on what they perceive to be an unnecessary\\nnewline, presses delete to make the visual layout match the expected layout. A\\nseparate object (in the case of the infobox, right-aligned on the other side of\\nthe screen) suddenly disappears. This is very surprising and counter-intuitive\\nbehavior.\\n\\nWhy don\\'t we just suppress the delete key when pressing it would delete the\\nobject the slug is associated with? In some alternative editors like Google\\nDocs, it is actually not possible to nuke the entire document by just pressing\\ndown the delete key at the top of the page -- it will stop before certain\\nobjects. I\\'ve never had any problems as a result.\\n\\nThat seems like the simplest solution to me and does not require a redesign of\\nthe slugs.\\n\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381339690, 'spacePHID': None, 'dateCreated': 1380963660, 'dateModified': 1440780428, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55336', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn appears near deleted reference in Firefox', 'description': {'raw': 'https://en.wikipedia.org/wiki/Konami_code?veaction=edit , in Firefox.\\nLocate the sequence of references [5][6][7][8].\\nDelete one of them (not the first one), hit Space, a pawn appears. \\nEaster egg *in* Konami Code!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54712'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406599319, 'spacePHID': None, 'dateCreated': 1380898980, 'dateModified': 1417571961, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54976', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Outer whitespace of first/last node in document not validated', 'description': {'raw': \"Because we don't store the inner whitespace of the document, we can't validate the outer whitespace its first/last children.\\n\\n1. Create document with wikitext:\\n==Heading==\\nFoo\\n2. Delete 'Heading' and the empty line\\n3. You now have:\\n[{'type':'paragraph', 'internal': {'whitepsace': ['\\\\n']}}, 'F' ....\\nin the DM\\n4. This serialises to\\n\\\\n\\nFoo\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384945720, 'spacePHID': None, 'dateCreated': 1380880140, 'dateModified': 1417572750, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54964', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Unhandled <pre> tokenizing scenarios in tokenizer', 'description': {'raw': 'See test case below. For some reason the <pre> inside the <blockquote> and the p-tag before the blockquote (all of those conditions are necessary to reproduce the bug) is causing the content after the blockquote to not be wrapped in p-tags. See output below. Probably some edge case in the paragraph-wrapping code. \\n\\nBased on bug report here:\\nhttps://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=575631753#VE_removing_paragraph_gaps\\n\\n[subbu@earth lib] cat /tmp/x\\na\\n\\n<blockquote><pre>\\nb\\n</pre></blockquote>\\n\\nc\\n\\nd\\n[subbu@earth lib] node parse < /tmp/x\\n<body data-parsoid=\\'{\"dsr\":[0,49,0,0]}\\'><p data-parsoid=\\'{\"dsr\":[0,1,0,0]}\\'>a</p>\\n\\n<blockquote data-parsoid=\\'{\"stx\":\"html\",\"dsr\":[3,42,12,13]}\\'><pre data-parsoid=\\'{\"stx\":\"html\",\"autoInsertedEnd\":true,\"strippedNL\":\"\\\\n\",\"dsr\":[15,29,5,0]}\\'>\\n\\nb\\n&lt;/pre&gt;</pre></blockquote>\\n\\nc\\n\\nd\\n</body>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384538751, 'spacePHID': None, 'dateCreated': 1380841560, 'dateModified': 1400883820, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54946', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: New references added after existing re-used references (<ref name=\":0\" />) replacing rather than proceeding them', 'description': {'raw': 'De.WP\\'s ref templates interact unhelpfully with VE/Parsoid, resulting in unwanted insertion of \"<ref name=\":0\">\"; examples:\\n\\nhttps://de.wikipedia.org/w/index.php?title=Titl%C3%A1&diff=prev&oldid=122939538\\n\\ntemplate: https://de.wikipedia.org/wiki/Vorlage:Internetquelle\\n\\nhttps://de.wikipedia.org/w/index.php?title=Die_letzte_Vorstellung&diff=prev&oldid=123020177\\n\\ntemplate: https://de.wikipedia.org/wiki/Vorlage:Der_Spiegel\\n\\nIt also results in having the display of the ref being moved into another ref. This is different from the other issue debated in 53777\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402003070, 'spacePHID': None, 'dateCreated': 1380837600, 'dateModified': 1417572287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54944', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursoring around a node leads to pawning inserting the cursor before (not after) the text in Firefox', 'description': {'raw': '(Second browser-specific - Firefox - bug I file today after 54322).\\nIt was reported by Fram at en.wp, quickest way to duplicate:\\n<<cursor in front of ref, use the \"back arrow\" on your keyboard once (so the ref number gets \"blue\"), and type.>>\\n\\nhttps://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandbox&diff=575562298&oldid=575557792 (with a snowman as well).\\n\\nMore ways:\\n<<Type some text, add a ref, remove the ref using backspace, then change your mind and use the \"undo\" arrow of VE. No, change your mind again and use the \"undo\" arrow once more, again removing the ref. Now type. Notice anything strange? Yep, I\\'m typing backwards. https://en.wikipedia.org/w/index.php?title=User:Fram/sandbox&oldid=575553019\\n[...]\\nOther tests produced the snowmen, or the insertion of huge chunks of text by VE. https://en.wikipedia.org/wiki/In_My_Dreams_%28Emmylou_Harris_song%29?veaction=edit\\n[...]\\nEasy way to check the \"backwards typing\": go to https://en.wikipedia.org/wiki/In_My_Dreams_%28Emmylou_Harris_song%29?veaction=edit , put the cursor after ref 1, backspace, undo arrow, type.>>\\n\\nTeamGale adds:\\n<<I tried to reproduce it because I was curious and it\\'s a really weird bug! Although when I put my cursor at the end of the \"backwards typing\" and clicked space, I could type straight again! TeamGale 10:03, 3 October 2013 (UTC)>>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57600\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61538'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406599273, 'spacePHID': None, 'dateCreated': 1380799920, 'dateModified': 1417572010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54917', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: JavaScript crashes if an invalid keyword is used on an image', 'description': {'raw': 'To reproduce, go to the URL ([[User:Amire80/ve-invalid-image-keyword]]). Notice that the save button doesn\\'t appear in the toolbar. The JS console shows the following error:\\n\\n[15:59:08.469] Error: Offset could not be translated to a DOM element and offset: 3\\n\\nThe reason for this is the invalid keyword \"no_such_keyword\" that I used on the image.\\n\\nA better behavior would be to show the user some kind of a warning about the wrong keyword, rather than throwing a JS error and crashing.\\n\\nThis bug was discovered by User:Nurick in the Hebrew Wikipedia.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/wiki/User:Amire80/ve-invalid-image-keyword?veaction=edit'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388915037, 'spacePHID': None, 'dateCreated': 1380754920, 'dateModified': 1443276356, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54903', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Text formatting menu broken in Firefox', 'description': {'raw': \"The Paragraph style tool in toolbar is not working in Firefox most of the time.\\n\\nSteps to reproduce\\n1. https://www.mediawiki.org/wiki/special:random\\n2. Active VE (Click 'Edit')\\n3. Place cursor on normal text\\n\\nExpected results:\\nThe paragraph style selector should change to 'Paragraph'\\n\\nActual results (in Firefox 24/linux):\\n9 out of 10 times, nothing changes.  The tool does not work at all.  Changing style doesnt work.\\n\\nThis doesnt happen on enwp.\\n\\nIn debug=true mode, the paragraph selector nearly always changes to Paragraph, but sometimes it then doesnt change to Heading if the cursor is moved to a Heading and changing the style doesnt work.\\n\\nThere is nothing in the JS console to suggest what might be the problem.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393466785, 'spacePHID': None, 'dateCreated': 1380688320, 'dateModified': 1417572592, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54863', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In the save dialog, \"characters left\" is under the \"pending changes\" text', 'description': {'raw': 'When saving some page using VisualEditor, \"characters left\" (e.g. 255) is under the text which comes from the Pending changes extension.\\n\\nI have a picture to explain more. It\\'s taken from the Finnish Wikipedia where is the Pending changes extension.\\n\\nhttps://commons.wikimedia.org/wiki/File:To_explain_a_bug_with_VisualEditor_and_Pending_changes.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-6majuboi566q3ozbh27r', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380833625, 'spacePHID': None, 'dateCreated': 1380573780, 'dateModified': 1417572827, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54802', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Copying a heading's text doesn't copy its format (unless the entire node is copied)\", 'description': {'raw': \"From T56721 comment 2:\\n\\n> When I copy a portion of content beginning with a header, then paste it\\n> elsewhere in the same document, everything is retained  /except/ the header.\\n> However, if I begin before the header (the paragraph before the header, for\\n> example) the header is retained.\\n>\\n> For example, copy everything from 'Start' to 'Finish' on this test page:\\n> https://www.mediawiki.org/wiki/VisualEditor:Test1234567\\n>\\n> Everything is retained except the H2 formatting on 'Start'. See this\\n> screenshot as an example too:\\n> http://images.wikia.com/trevortest/images/5/54/Header_is_lost.png\\n> {F16005520}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381157444, 'spacePHID': None, 'dateCreated': 1380325500, 'dateModified': 1521842197, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54728', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't remove categories from 'Page Settings' modal in latest build\", 'description': {'raw': \"Currently on MediaWiki.org, categories cannot be removed from the 'Page Settings' modal. This is true of new categories added and existing categories.\\n\\nhttps://www.mediawiki.org/wiki/VisualEditor:Test1234567?veaction=edit\\n\\nInez says he's working on a fix now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380557959, 'spacePHID': None, 'dateCreated': 1380324960, 'dateModified': 1417572831, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54727', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Header formatting is stripped when copying (or cutting) and pasting inside a single article in Firefox', 'description': {'raw': 'Comparison 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 (https://en.wikipedia.org/wiki/Kitten?veaction=edit)\\n2. Copy any selection of text that has formatting (bold, italics, link, header, references)\\n3. Paste the content elsewhere in the same VE document.\\n4. You will see that all formatting has been stripped. See the attached file.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12231}'}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380325542, 'spacePHID': None, 'dateCreated': 1380310020, 'dateModified': 1521842197, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54721', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Sometimes the edit link for VE does not appear', 'description': {'raw': 'Edit 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. \\n\\nSeems to happen more frequently for Chrome than Firefox. \\n\\nThe 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12179}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408096458, 'spacePHID': None, 'dateCreated': 1380295680, 'dateModified': 1417571941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54706', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Render lock when changing selection prevents inspectors' changes from rendering\", 'description': {'raw': \"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).\\n\\nNarrated 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.\\n\\nAlternatively, 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382541648, 'spacePHID': None, 'dateCreated': 1380244140, 'dateModified': 1417572820, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54675', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Rendering of <source> MWExtensionNode is empty after the user edits it', 'description': {'raw': '1. Create a page with <source lang=\"JavaScript\">some content here</source>\\n2. Edit the page in VE. Note that the <source> tag renders correctly\\n3. Use the alien tag inspector to edit the contents of the <source> tag\\n4. The <source> tag rerenders as an empty block\\n\\nThis is because the HTML <source> tag is self-closing and cannot have any content. This leads to strange situations like:\\n\\n>>> extensionNode[0]\\n<source lang=\\u200b\"JavaScript\">\\u200bwhee\\u200b</source>\\u200b\\n>>> extensionNode[0].outerHTML\\n\"<source lang=\"JavaScript\"></source>\"\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57429'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386026779, 'spacePHID': None, 'dateCreated': 1380066060, 'dateModified': 1417572123, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54577', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] VisualEditor: Attribute name=\":0\" inserted into <ref>', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Daniel_Rowe_%28footballer%29&oldid=570278760&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54341'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380836921, 'spacePHID': None, 'dateCreated': 1379834280, 'dateModified': 1381323957, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54445', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor cannot move past references (or other nodes) when using arrow keys', 'description': {'raw': '**Author:** `swalling`\\n\\n**Description:**\\nSteps to reproduce:\\n\\n1. Place your cursor in page text. \\n2. 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380594405, 'spacePHID': None, 'dateCreated': 1379806800, 'dateModified': 1417572823, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54443', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Copy/paste of existing templates and images broken (unformatted text pasted only)', 'description': {'raw': '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.\\n\\nTemplates added in the current editing session can be copied and pasted as expected.\\n\\nPossibly this is a result of the fix to bug 49396?\\n\\nTo reproduce:\\n1. 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\\n\\n2. select and copy a template or image\\n3. Paste the somewhere else in the page.\\n\\nExpected behaviour: the full template or image is pasted\\nActual behaviour (templates): Only text output of the template is pasted, unformatted and unlinked.\\nActual behaviour (images): Only the image caption is pasted, unformatted and unlinked.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49396'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386031966, 'spacePHID': None, 'dateCreated': 1379720640, 'dateModified': 1611870911, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54410', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid jobs are not dequeued fast enough during heavy editing activity', 'description': {'raw': 'Parsoid is flooding the global job queue.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**Whiteboard**: [see comment 9]'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394719478, 'spacePHID': None, 'dateCreated': 1379716620, 'dateModified': 1394719478, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54406', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Right half of toolbar disappears when <center> or <div align=\"center\"> appears in image on first line of page', 'description': {'raw': 'When a page has an image on the first line and the image caption contains a <center> tag or a <div align=\"...\"> 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.\\n\\nCuriously, <p align=\"center\"> does not exhibit this problem.\\n\\nExample from an article: https://en.wikipedia.org/w/index.php?title=Little_Tich&oldid=573770305\\n\\nMinimal test case: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox4&oldid=573786703\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54642'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393531314, 'spacePHID': None, 'dateCreated': 1379688840, 'dateModified': 1417572590, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54379', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paste validation fails for images in FF', 'description': {'raw': \"Because firefox converts path attributes to absolute URLs, the hashes don't match up, so VE pastes the plain-text equivalent content (empty string).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379978107, 'spacePHID': None, 'dateCreated': 1379685180, 'dateModified': 1417572833, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54377', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Surface isn't updated properly for Language annotations\", 'description': {'raw': 'This is extremely weird, and is relatively new, and I am at a loss.\\n\\nSteps to reproduce:\\n1. Put cursor on some word in the article.\\n2. 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.\\n6. Notice: The word is surrounded with a language span, but it has the initial en/ltr values instead of the chosen annotation.\\n7. Save the article.\\n8. Click on \"Edit Source\" --> the language span contains the *correct* annotation (he/rtl)\\n\\nExpansion on that:\\n1. Repeat the above through step 6.\\n2. Select a separate word and annotate it with some random link.\\n3. Inspect the original language span -- *now* it\\'s updated!\\n\\nOne more weirdness:\\n1. Repeat above through step 6.\\n2. 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.\\n\\n\\n\\nI\\'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. \\n\\nI 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.\\n\\nLink 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.\\n\\nI\\'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).\\n\\nI\\'m at a loss. Help is appreciated!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382644915, 'spacePHID': None, 'dateCreated': 1379607000, 'dateModified': 1417572820, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54335', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting into a link with a trailing (linked) non-alphanumeric character causes link pre-annotation to fail', 'description': {'raw': \"Following 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.\\n\\ne.g. [[Link|Link.]] → [[Link]]<nowiki />s[[Link|.]]\\nbut [[Links]] → [[Linkers]] (this is the expected behaviour for all situations)\\n\\nSee https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox3&diff=573654600&oldid=573653290\\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.\\n\\nSee https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&diff=573655981&oldid=573654600\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51442\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380583304, 'spacePHID': None, 'dateCreated': 1379605860, 'dateModified': 1417572830, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54332', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Page settings dialog broken in Firefox', 'description': {'raw': 'Current VisualEditor-Version:\\ncommit c98a964d5f8495f0d16af9229abbeb0449042d1e\\nMerge: 3d01a5b e7aed52\\nAuthor: jenkins-bot <jenkins-bot@gerrit.wikimedia.org>\\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).\\n\\nI tried to debug with Firebug: When I click on categories the following error gets fired:\\n\\nTypeError: style is null\\nhttp://XYZ/load.php?debug=false&lang=de&modules=ext.visualEditor.core%2Cdata%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T072806Z&*\\nLine 9\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-26asvhtv4jalaeeuigbm', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380823394, 'spacePHID': None, 'dateCreated': 1379594760, 'dateModified': 1417572828, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54322', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: A pawn appears when undoing \"select transclusion and replace with text\"', 'description': {'raw': \"Steps 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.\\n\\nUpon 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).\\n\\nSo 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.\\n\\nWe 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.\\n\\nNot sure if this is a regression or not.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381281061, 'spacePHID': None, 'dateCreated': 1379589060, 'dateModified': 1417572824, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54314', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Collapse all the text styling buttons (except link?) into a single text-styling icon in the toolbar', 'description': {'raw': 'From en.wp.\\n\\nJohn Broughton: <<So there is now a new toolbar, and - bizarrely - the icons for media, reference, reference list, and transclusion \\'\\'\\'are no longer visible\\'\\'\\'. They are now under the \"More\" menu.\\nOkay, one could argue that these four are, somehow, \\'\\'advanced\\'\\' editing options (no matter how critical they are to editing articles). But I\\'d love to hear from someone as to why Bold and Italic (the first in particular \\'\\'rarely\\'\\' used in articles) still have icons visible on the toolbar, while five other formatting options are now under \"More\". It really, really would have been better to have a \"Format text\" drop-down menu that had all seven text formatting options on it, and to leave the media, reference, reference list, and transclusion icons where they were, visible on the toolbar. Or, worst case, leave them under the \"More\" menu [one more click, and thus one less reason for experienced editors to use VE, because this \\'\\'\\'makes it more cumbersome to use\\'\\'\\' those four things]; at least then they wouldn\\'t be paired with formatting options with which they have little in common. [...] (And don\\'t even get me started on the \\'\\'sequence\\'\\' within the new \"More\" drop-down menu - apparently the \\'\\'least\\'\\' important choices are at the \\'\\'top\\'\\' because that\\'s the way that \\'\\'no one else\\'\\' does drop-down menus, so obviously everyone else is wrong?!?)>>\\n\\nAndrew Davidson: <<Bold formatting is not rarely used.  It is used in all articles right at the beginning to emphasise the name of the topic and any synonyms.  But this usage is quite specialised and subject to the conventions of our manual of style.  The VE should understand this.  Either the use of bold text should be handled by a style sheet/template/wizard approach to article creation.  Or the appearance of the bold option in the toolbar should be context sensitive so that it only appears when editing the lead of an article and warnings appears if it seems to be used incorrectly. >>\\n\\nSalix alba: <<One problem I get is the toolbar frequently splits into two lines. If my browser less than 1100 pixels then the toolbar wraps leaving lots of white space which could be usefully filled. I\\'d be happier either with single line with more drop downs or two full lines, just not empty space.\\nI guess different editors will want different things on a toolbar. Doing inline maths you would want italics, sub, and sup to be easily added plus greek symbols eiπ. Other editors will have different requirements. Tooltips would be handy to get shortcuts for each action, (no I will not read the help page). The wikitext editor\\'s toolbar manages to make a lot of things easily accessible.>>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389667077, 'spacePHID': None, 'dateCreated': 1379510460, 'dateModified': 1417572676, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54271', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Warning:  Recursion detected in RequestContext::getLanguage in /includes/context/RequestContext.php on line 284', 'description': {'raw': \"I thought there was a bug for this, but I can't find it...\\n\\nWarning:  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 `_type: mediawiki` and `channel: recursion-guard`.\\n\"}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': 'PHID-USER-k6tmz5ylx4rzfl3bitse', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'error', 'closerPHID': 'PHID-USER-k6tmz5ylx4rzfl3bitse', 'dateClosed': 1487640775, 'spacePHID': None, 'dateCreated': 1379372820, 'dateModified': 1602870082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54193', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Move TemplateData to its own JSON-content namespace and associate with Template-namespace, or to its own TemplateData content model and revision slot', 'description': {'raw': 'e.g. Template:Information could be documented at TemplateData:Information instead of inside the source code of Template:Information.\\n\\nPros:\\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 <templatedata /> 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}'}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1379223360, 'dateModified': 1734888310, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54140', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Wikimedia thumbnail generator often returns HTTP 500 Internal Server Error', 'description': {'raw': \"When requesting random images from Commons' MediaWiki API and requesting a thumbnail for it, I often get a HTTP 500.\\n\\nFor example:\\n\\n\\n\\nGET http://upload.wikimedia.org/wikipedia/commons/thumb/f/fb/USMC-05934.jpg/400px-USMC-05934.jpg\\nHTTP 500\\n<html><head><title>Error generating thumbnail</title></head>\\n<body>\\n<h1>Error generating thumbnail</h1>\\n<p>\\nError creating thumbnail:\\n</p>\\n<!-- http://commons.wikimedia.org/w/thumb_handler.php/f/fb/USMC-05934.jpg/400px-USMC-05934.jpg -->\\n<!-- mw1154 -->\\n</body>\\n</html>\\n\\nUsually when trying again, it just works.\\n\\nI'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 <img>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.\\n\\nI 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\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379553025, 'spacePHID': None, 'dateCreated': 1378941420, 'dateModified': 1417692041, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54045', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[scap] Deployment: Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link', 'description': {'raw': \"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.\\n\\nHowever this does not seem to be true.\\n\\nFor one, the configuration around is working perfectly fine.\\n\\nThough 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).\\n\\nThe .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.\\n\\nAnd, in fact, [[Special:Version]] does show a git hash (maybe not the best one, but it does show something).\\n\\nIt 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.\\n\\nFor 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.\\n\\nI'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).\\n\\nDepending 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\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=36271\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-ll6tmaogat2b5q7tnqas', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404841358, 'spacePHID': None, 'dateCreated': 1378771740, 'dateModified': 1420738786, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53972', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Gerrit SSH: Intermittent key_verify failed for server_host_key and 'hash mismatch'\", 'description': {'raw': 'On 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\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404805916, 'spacePHID': None, 'dateCreated': 1378584660, 'dateModified': 1496862150, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53895', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Review and deploy BetaFeatures extension', 'description': {'raw': \"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.\\n\\nVisualEditor, 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.\\n\\nPlease 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.\\n\\nThanks!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/Extension:BetaFeatures\"}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384542962, 'spacePHID': None, 'dateCreated': 1378504020, 'dateModified': 1503741166, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53865', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Commit missing from mediawiki/exentions/MassMessage repo', 'description': {'raw': \"https://gerrit.wikimedia.org/r/#/c/82796/ - sha1: 8587e2e4b4f90ca9cdba0f39e647b235921a5ae8\\n\\nMissing on git.wm.o, gerrit, github:\\n\\nhttps://git.wikimedia.org/summary/mediawiki%2Fextensions%2FMassMessage.git\\n\\nhttps://github.com/wikimedia/mediawiki-extensions-MassMessage/commits/master \\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 http://translatewiki.net.\\nb9ccd1c Autocomplete suggestions for spamlist input\\n3027dc6 Localisation updates from http://translatewiki.net.\\n8d106e1 Localisation updates from http://translatewiki.net.\\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\"}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378697343, 'spacePHID': None, 'dateCreated': 1378444620, 'dateModified': 1378697343, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53836', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Marathi/Devanagari: Save button does not get enabled for same or lesser length change', 'description': {'raw': '*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.\\n\\n**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\\nhttps://mr.wikipedia.org/wiki/अभिमन्यु\\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.\\n**Please note do not move arrow keys or spacebar\\n\\n7 Save button does not apear\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381270319, 'spacePHID': None, 'dateCreated': 1378345920, 'dateModified': 1465905670, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53788', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[EPIC] Use Parsoid HTML for all page views', 'description': {'raw': '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.\\n\\nhttps://www.mediawiki.org/wiki/Parsing/Parser_Unification is the wiki page for this project.\\n\\nThis is a tracking task for getting this done. Subtasks track the specific work for getting this done.'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1378338120, 'dateModified': 1724822123, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53784', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Visualditor: Marathi/Devanagari: edit change not reflecting in edit preview', 'description': {'raw': '*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.\\n\\n\\nI suppose this would be easy to reproduce screen shot & will do it soon.\\n\\n\\n* Steps to reproduce:\\n1. Go to existing page with considerable Marathi Devnagari text may be like\\nhttps://mr.wikipedia.org/wiki/अभिमन्यु\\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.\\n\\n**Problem is not always but frequent .Tested on Win7 +Firefox\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381270232, 'spacePHID': None, 'dateCreated': 1378310460, 'dateModified': 1465905633, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53758', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Marathi/Devanagari: Backpace deletes  text on right side', 'description': {'raw': '*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 https://mr.wikipedia.org/wiki/अभिमन्यु\\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**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51472'}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385507002, 'spacePHID': None, 'dateCreated': 1378309560, 'dateModified': 1465905625, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53757', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page down and page up not working as expected in Firefox', 'description': {'raw': 'an 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.\"\\nThe 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. \\n\\nAt [[User:Thryduulf/sandbox]] and [[Timbuktu]] it works as expected from the start. \\n\\nAt [[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.\\n\\nAt [[Great Balls of Fire]] page down worked once, then didn\\'t. I clicked and it worked as expected subsequently.\\n\\nAt [[Malvern Link]] I saw the same as at [[Nigeria]], but after pressing page up both page up and page down then worked as expected.\\n\\nI\\'m struggling to see any pattern.\\n\\nBug 33047 was suggested as having potential relevance, but that was fixed in October 2012 so my gut feeling is that its unlikely.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51957\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50726'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399419475, 'spacePHID': None, 'dateCreated': 1378300380, 'dateModified': 1556665598, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53750', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'run VE browser tests in vagrant', 'description': {'raw': \"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:\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386002609, 'spacePHID': None, 'dateCreated': 1378218960, 'dateModified': 1386002609, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53712', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'browsertests: triggers for VisualEditor', 'description': {'raw': \"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…\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52120\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57560\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392915139, 'spacePHID': None, 'dateCreated': 1378156860, 'dateModified': 1427208652, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53691', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Selection-expansion doesn't trigger for Thai script text\", 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381269899, 'spacePHID': None, 'dateCreated': 1378126200, 'dateModified': 1417572824, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53679', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Removing formatting from part of a link causes a snowman', 'description': {'raw': \"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!\\n\\nI'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\"}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380838919, 'spacePHID': None, 'dateCreated': 1378013580, 'dateModified': 1417572827, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After adding a link, cursor appears before rather than after the new insertion', 'description': {'raw': '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.\\n\\nReproduce:\\n1. Go to an RTL wiki.\\n2. 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377815727, 'spacePHID': None, 'dateCreated': 1377807780, 'dateModified': 1417572937, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53560', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing a <syntaxhighlight> block with the experimental generic editor leads to brokenness because the attributes get blanked', 'description': {'raw': '**Author:** `wojciech.r`\\n\\n**Description:**\\nWhen I edit existing content in <source> 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.\\n\\nhttps://www.mediawiki.org/w/index.php?title=VisualEditor:Test&oldid=773552\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377958953, 'spacePHID': None, 'dateCreated': 1377796560, 'dateModified': 1417572841, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53543', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing up while next to an inline image throws an exception', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377736943, 'spacePHID': None, 'dateCreated': 1377729540, 'dateModified': 1417572940, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53507', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit tab replaced with \"Create source\" for Education Program pages', 'description': {'raw': '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\".)\\n\\nExample institution page:\\nhttp://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma\\n\\nExample course page:\\nhttp://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nyv6rqxnzdy3oe323a3d', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397705810, 'spacePHID': None, 'dateCreated': 1377700800, 'dateModified': 1443276365, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53477', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Metadata information missing from transaction when content is inserted', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378261401, 'spacePHID': None, 'dateCreated': 1377652560, 'dateModified': 1592821311, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53445', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Metadata should always be collapsed on replace', 'description': {'raw': \"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.\\n\\nWe should always merge metadata when a segment is deleted, so that it appears outside any new structure added.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378261378, 'spacePHID': None, 'dateCreated': 1377652320, 'dateModified': 1417572840, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53444', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Style Parsoid\\'s <figure>s to look like MediaWiki\\'s <div class=\"thumb\">s rather than replacing them', 'description': {'raw': \"Right now VisualEditor transforms the HTML Parsoid gives us (which is nicely-structured <figure>s) into the mess of <div>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 <div>s with known classes (and Parsoid's HTML has no <div>s), and is often over-ridden in wiki- or user-specific CSS (e.g. Wikia's sites' skins, or that on Cherokee Wikipedia).\\n\\nFrom 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\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386874061, 'spacePHID': None, 'dateCreated': 1377645300, 'dateModified': 1417572737, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53436', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Consider support for non-template transclusions (magic words, parser functions)', 'description': {'raw': \"Right now it is only intended for data about custom wiki-made templates.\\n\\nTo support magic words and parser functions, we'll need to make a few changes to make sure there are no conflicts or wrong assumptions.\\n\\nA 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).\\n* 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.\\n\\n 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377627060, 'dateModified': 1715869426, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53413', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor movement stalls after cut-pasting text containing ref tags', 'description': {'raw': 'Steps 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'}, 'authorPHID': 'PHID-USER-4jecvpv4h62htut6pxez', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1421454209, 'spacePHID': None, 'dateCreated': 1377562620, 'dateModified': 1438734480, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53385', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Firefox doesn't fire a copy event when only a FocusableNode is selected\", 'description': {'raw': \"Only workaround I can think of is to create a fake hidden selection whenever a FocusableNode(s) is selected on it's own.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378923366, 'spacePHID': None, 'dateCreated': 1377553200, 'dateModified': 1417572836, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53375', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: getNearestCorrectOffset doesn't ignore internal lists\", 'description': {'raw': '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)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397775737, 'spacePHID': None, 'dateCreated': 1377547260, 'dateModified': 1417572417, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53366', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Unnamed references don't register when cloned\", 'description': {'raw': \"1. 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377800786, 'spacePHID': None, 'dateCreated': 1377547080, 'dateModified': 1417572939, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53365', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Copying over nodes results in paste adding newlines', 'description': {'raw': 'Select text around a content node (e.g. a reference: \"foo [1] bar\" ) and then copy paste it. Note you now have extra newlines.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377800812, 'spacePHID': None, 'dateCreated': 1377545880, 'dateModified': 1417572938, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53364', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Document loses focus after cutting a FocusableNode', 'description': {'raw': '1. 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'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377634940, 'spacePHID': None, 'dateCreated': 1377545460, 'dateModified': 1417572941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53362', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Displayed content and DM out of sync with fast insertion (primarily from test scripts?)', 'description': {'raw': '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.  \\nclick 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}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377657017, 'spacePHID': None, 'dateCreated': 1377540900, 'dateModified': 1417572940, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53360', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Creating a new reference with blank content leads to insertion of a <ref/> tag in the wikitext', 'description': {'raw': \"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 :/.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377649422, 'spacePHID': None, 'dateCreated': 1377527760, 'dateModified': 1417572941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53345', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Don't allow nested <ref>s, because Cite.php doesn't\", 'description': {'raw': \"From http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE.2C_Sfn_template_within_reference.2C_Vcite_error\\n\\nAdding a <ref> tag (e.g., a bibliographic citation) inside another <ref> 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=570036528&oldid=570035364\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417468754, 'spacePHID': None, 'dateCreated': 1377373500, 'dateModified': 1511469032, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53303', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Math editor is called LaTeX, but that is not accurate and possibly confusing', 'description': {'raw': '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.\\n\\nThe 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.\\n\\nThe 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.\\n\\nWe 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**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=43058'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386810532, 'spacePHID': None, 'dateCreated': 1377252120, 'dateModified': 1417572682, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53251', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Nowiki tag not properly escaped when combined with other wiki markup', 'description': {'raw': \"From http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Bold_and_nowiki.2C_other_markup\\n\\nIf you add a nowiki tag by itself, the angle brackets get escaped out (&amp;lt;nowiki&amp;gt;, or does just plain &lt;/nowiki&gt; 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.\\n\\nTry this:\\n\\n* You need a </nowiki> tag '''here'''.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402417039, 'spacePHID': None, 'dateCreated': 1377197160, 'dateModified': 1402417039, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53228', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Slugs are created inside empty table rows, creating pawns if used', 'description': {'raw': '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\\n\\n|-\\n|}\\n\\ncaused 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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395077429, 'spacePHID': None, 'dateCreated': 1377184320, 'dateModified': 1469823941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53214', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Blank page, list, [enter] lose cursor', 'description': {'raw': \"<<If I edit a blank page, press on the number list or bullet list icon and then press enter, the page remains blank but I have no cursor. Then other strange things start to happen. Pressing the link icon does not seem to do anything. I can press some icons (transclusion, references, etc) and they will appear, but if I then exit it, pressing it again or any other icon does nothing. Undo works though. FF 23.0.1 Win7. --Atethnekos (Discussion, Contributions) 21:27, 21 August 2013 (UTC) >>\\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.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394678478, 'spacePHID': None, 'dateCreated': 1377164400, 'dateModified': 1417572574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53206', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: MW images shouldn't be able to take a link annotation\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379981344, 'spacePHID': None, 'dateCreated': 1377087600, 'dateModified': 1417572833, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53151', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Implement non-linear transitions', 'description': {'raw': 'Implement non-linear transitions between steps.  This is one of the key goals of the planned update to the API.  \\n\\nThe 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.\\n\\nThere 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).\\n\\nSimple 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402345387, 'spacePHID': None, 'dateCreated': 1377068880, 'dateModified': 1402345387, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53143', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Rapid typing with pre-annotation creates weird new characters (sometimes?)', 'description': {'raw': '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.\\n2. Click the \"Bold\" button.\\n3. 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.\\n\\nThis doesn\\'t happen when I typed regular language, I suspect, then, that it has to do with the speed of the insertion?\\n\\nBut 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377648335, 'spacePHID': None, 'dateCreated': 1376955360, 'dateModified': 1417572835, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53079', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'about=null entries on <figure> elements (because of dom-fragment reuse)', 'description': {'raw': 'From WP:VE/F page (http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=567413854)\\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 [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]] <sup>([[:fr:Discussion Utilisateur:NicoV|Talk on frwiki]])</sup> 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=47326'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389799516, 'spacePHID': None, 'dateCreated': 1376945880, 'dateModified': 1526349539, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53071', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: IME input into an empty slug causes characters to overwrite one another', 'description': {'raw': '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 \"中國\".\\n\\nObserved 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-lliyevigiycjbybglftk', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '40', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377348845, 'spacePHID': None, 'dateCreated': 1376939940, 'dateModified': 1438734485, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53064', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Expose build number', 'description': {'raw': 'Quite often we get bug reports for issues that have been recently fixed but not deployed to the smaller wikis.\\n\\nIt 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380148809, 'spacePHID': None, 'dateCreated': 1376930160, 'dateModified': 1452720458, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53050', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Line height on beta warning message is too narrow', 'description': {'raw': 'Line height example\\n\\nSee screenshot for 1.25em vs 1.5em.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F11545}'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377021133, 'spacePHID': None, 'dateCreated': 1376928720, 'dateModified': 1417572944, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53045', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Repeated insertion of multi-byte characters', 'description': {'raw': 'See the third example at https://www.mediawiki.org/w/index.php?title=User:Miya/VE4&oldid=762831.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378958990, 'spacePHID': None, 'dateCreated': 1376863380, 'dateModified': 1417048670, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing toolbar CSS disappears on hover, then the buttons do nothing', 'description': {'raw': 'I 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 <click>, and I have the arrow pointer.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406756283, 'spacePHID': None, 'dateCreated': 1376814420, 'dateModified': 1417571957, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52987', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Some magic combination of arrow keys and actions involving the heading level toolbar\" scrambles document', 'description': {'raw': 'screenshot\\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.\\n\\nI 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 <return> this time) caused a total HsiT scramble.  A sequence of characters of roughly equivalent length replaced the heading line I had been editing.\\n\\nThe damage seems to have spread elsewhere in the document.  See attached screenshot.\\n\\nSeparate 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}'}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377831473, 'spacePHID': None, 'dateCreated': 1376813040, 'dateModified': 1417572935, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52981', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Move info about template-affected attributes from meta tags into data-mw', 'description': {'raw': 'We currently use meta tags to mark up template-affected attributes:\\nhttp://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Templates_in_attributes\\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<table><tr title=\"{{echo|foo}}\"></tr></table>\\n\\nThey 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/\\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 https://gist.github.com/subbuss/6092148/raw/e153a444b6e252d9eebd690e996e28cdbb859df7/gistfile1.txt\\n\\nWe should work this out further in http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Templates_in_attributes\\nand implement the resulting spec. \\n\\nAn 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 \\'<div title=\"{{echo|foo}}\">{{echo|</div>}}\\' | 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.\\n\\nFragment 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.\\n\\nCurrently 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386110602, 'spacePHID': None, 'dateCreated': 1376628000, 'dateModified': 1386110602, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52913', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: FlaggedRevs inserts its tabs in the midst of the edit and edit source tabs', 'description': {'raw': \"Screenshot\\n\\nOn wikis with FlaggedRevs, the interface historically displays buttons in the order [edit][pending changes]. This seems logical.\\n\\nUnder 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11122}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391808894, 'spacePHID': None, 'dateCreated': 1376490900, 'dateModified': 1444199732, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52848', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspector fails to render correctly for embedded buttons', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376511662, 'spacePHID': None, 'dateCreated': 1376488380, 'dateModified': 1417572948, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52845', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting block level elements can lose annotations', 'description': {'raw': '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. \\n\\nFor example in \\nhttp://en.wikipedia.org/wiki/User:Salix_alba/VE_test \\nselecting the whole of the final paragraph and coping and pasting loses anotation.\\n\\nExamining the clipboard in this case its something like\\n<meta charset=\\'utf-8\\'><p data-parsoid ...</p><br class=\"Apple-interchange-newline\">\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52770'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381158661, 'spacePHID': None, 'dateCreated': 1376343780, 'dateModified': 1417570405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52771', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit to a template somehow removing equals signs in markup?', 'description': {'raw': '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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421281940, 'spacePHID': None, 'dateCreated': 1376320140, 'dateModified': 1422983020, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52752', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Regression: Wikitext for new lists has unnecessary newlines after bullets', 'description': {'raw': 'Output 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 <jenkins-bot@gerrit.wikimedia.org>\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11826}'}, 'authorPHID': 'PHID-USER-26asvhtv4jalaeeuigbm', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376522202, 'spacePHID': None, 'dateCreated': 1376317860, 'dateModified': 1376522202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52751', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add a keyboard shortcut to trigger Save dialog', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-4jecvpv4h62htut6pxez', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377814470, 'spacePHID': None, 'dateCreated': 1376299800, 'dateModified': 1417572937, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52745', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: cursor places itself after the first character when inserting a group of Japanese characters', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377202396, 'spacePHID': None, 'dateCreated': 1376191500, 'dateModified': 1417048671, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52716', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable Echo / Notifications on se.wikimedia.org', 'description': {'raw': 'The Swedish chapter would like to get Notifications enabled on their wiki at se.wikimedia.org. Please use the default settings.\\n\\nPoll here: http://se.wikimedia.org/wiki/Tråd:Wikimedia:Bybrunnen/VisualEditor_och_Notifications\\n\\n/Jan\\nCEO\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382727600, 'spacePHID': None, 'dateCreated': 1376179080, 'dateModified': 1382727600, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52714', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Register each VE experimental feature individually with the BetaFeatures extension', 'description': {'raw': 'Because we love Mark:\\n\\nhttp://m.mediawiki.org/wiki/Extension:BetaFeatures\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383280071, 'spacePHID': None, 'dateCreated': 1376107740, 'dateModified': 1417572758, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52686', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link suggestions list should vertically scroll if there's insufficient room for them on-screen\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393635105, 'spacePHID': None, 'dateCreated': 1376050440, 'dateModified': 1441912186, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52670', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] mediawiki.notification: Notification area remains visible when empty and steals pointer events', 'description': {'raw': 'Screenshot 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.\\n* 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.\\n* 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.\\n\\n----\\nExpected behaviour: Can move/protect page. Dropdown does not close out of the blue.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: normal\\n\\n**Attached**: {F11622}'}, 'authorPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409946198, 'spacePHID': None, 'dateCreated': 1375990260, 'dateModified': 1443965065, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52659', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Selser regression: pages with templates that generate tables and foster content out of the table are broken', 'description': {'raw': '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.\\n\\nThis 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.\\n\\nI think this may have something to do with the double }} closing in the infobox.\\n\\n$ mkdir tmp\\n$ cd tmp\\n$ wget \\'http://parsoid.wmflabs.org/en/Raven-Symon%C3%A9?oldid=566906720\\' -O originalHTML\\n$ wget \\'http://en.wikipedia.org/wiki/Raven-Symon%C3%A9?oldid=566906720&action=raw\\' -O originalWikitext\\n$ cp originalHTML editedHTML\\n$ vi editedHTML   # Change \\'<h2>Life and career</h2>\\' to \\'<h2>Life and careeer</h2>\\'\\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<BR>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.<ref>{{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]]}}</ref> \\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         = [http://www.myspace.com/ravensymone 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\\'\\'\\'<ref>[http://www.mlive.com/entertainment/saginaw/index.ssf/2008/08/ravensymone_steps_out_of_chara.html]</ref>, (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]]\\'\\'<!-- Per http://www.imdb.com/name/nm0712368/filmoseries#tt0086687 her first episode of \"A Different World\" was Nov. 2, 1989, while her first Cosby Show episode was Sept 21, 1989. --> 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]].<ref>[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.</ref> The next album, \\'\\'[[Undeniable (Raven-Symoné album)|Undeniable]]\\'\\', was released on May 4, 1999.\\n \\n 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.<ref name=\"billboard.com\">[{{BillboardURLbyName|artist=raven-symoné|chart=Billboard 200}} Raven-Symoné]. Billboard.com. Retrieved 2012-05-19.</ref> 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.\\n@@ -32,7 +10,7 @@\\n \\n In 2012, Raven-Symoné ranked number eight on \\'\\'[[VH1]]\\'\\'{{\\'s}} \"100 Greatest Kid Stars Of All Time\" list,<ref name=\"GKSAT\">[http://blog.vh1.com/2012-12-02/and-the-1-greatest-kid-star-of-all-time-is/ Greatest Kid Star Of All Time]</ref> and ranked number one on \\'\\'Loop21\\'\\'{{\\'s}} \"10 Richest Black Actresses Under 40\" list.<ref name=\"RBAU40\">[http://www.loop21.com/entertainment/10-richest-black-actresses-under-40 10 Richest Black Actresses Under 40]</ref>\\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]] <ref>http://www.tv.com/people/raven-symone/</ref><ref>http://xfinity.comcast.net/slideshow/entertainment-aachildactors/3/</ref><ref>http://ethnicelebs.com/raven-symone</ref><ref name=\"imdb\">http://www.imdb.com/name/nm0712368/bio</ref><ref>http://www.nndb.com/people/017/000103705/</ref> and [[Native Americans in the United States|Native American]] ancestry.<ref name=\"imdb\" /> At age three, her family moved to [[Ossining (village), New York|Ossining, New York]] where she attended Park School.<ref name=\"birthplace\">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.</ref><ref>[http://ftp.rootsweb.com/pub/usgenweb/la/winn/bios/sym1569.txt Rootsweb.com]{{Dead link|date=May 2010}}</ref> 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376528533, 'spacePHID': None, 'dateCreated': 1375953720, 'dateModified': 1377029359, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52638', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Some pages with short titles (incl all with single character titles) are not recognised as existing pages in the link box', 'description': {'raw': '**Author:** `sandrobt.wiki`\\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). \\n\\nNotice 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50898'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377808859, 'spacePHID': None, 'dateCreated': 1375847280, 'dateModified': 1417572938, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52596', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dragging mouse clicks VE buttons upon release', 'description': {'raw': 'From 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380610142, 'spacePHID': None, 'dateCreated': 1375737000, 'dateModified': 1417572818, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52561', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspectors should not display below visible page area', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411778807, 'spacePHID': None, 'dateCreated': 1375635660, 'dateModified': 1417571327, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52526', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot apply annotations to link in specific case in Firefox', 'description': {'raw': '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.\\n\\nI 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=Indian_massacre_of_1622&oldid=564508110&veaction=edit'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392860045, 'spacePHID': None, 'dateCreated': 1375600380, 'dateModified': 1443276372, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52517', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Top bar not staying at top', 'description': {'raw': 'It 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) 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.\\n\\n2) 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.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52433\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52441'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377563643, 'spacePHID': None, 'dateCreated': 1375562940, 'dateModified': 1417572837, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52504', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Protected node css with * selector breaks some template layouts', 'description': {'raw': 'Specifically [[Template:Football kit]] which was created in 2004 by some young genius.\\n\\nThe 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**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61497'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398962590, 'spacePHID': None, 'dateCreated': 1375529520, 'dateModified': 1443278231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52499', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference fails to display in reference list on init or change (but appears if you add a new use of it)', 'description': {'raw': '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:\\n\\nhttp://de.wikipedia.org/wiki/Google#Einzelnachweise 1 out of 55\\n\\nhttp://de.wikipedia.org/wiki/Chaim_Perelman#Einzelnachweise 0 out of 1\\n\\nhttp://de.wikipedia.org/wiki/Seilkorb#Einzelnachweise 5 out of 15\\n\\nhttp://de.wikipedia.org/wiki/Joan_Coromines#Fu.C3.9Fnoten 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?\\n\\nReport:\\n\\nhttp://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121153367#Einzelnachweise_am_Artikelende_werden_im_VE_nicht_angezeigt\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376930015, 'spacePHID': None, 'dateCreated': 1375489200, 'dateModified': 1417572503, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52490', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Fix \"TypeError: Cannot read property \\'content\\' of undefined\" (when applying template changes)', 'description': {'raw': \"Looks like we don't account for the API returning an error in ve.ce.MWTransclusionNode.prototype.generateContents. Unconditionally response.visualeditor.content is accessed.\\n\\nAPI has a clear path both for dieUsage() and result === success.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375493084, 'spacePHID': None, 'dateCreated': 1375482780, 'dateModified': 1417572950, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52483', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Data model should be able to default between equivalent annotations', 'description': {'raw': 'We 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'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376028793, 'spacePHID': None, 'dateCreated': 1375473840, 'dateModified': 1417572948, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52477', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Update tours for new edit tab selectors', 'description': {'raw': \"VE changed the edit tab selectors as part of their UI update to show it's in Beta.\\n\\nNow, 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376583765, 'spacePHID': None, 'dateCreated': 1375473480, 'dateModified': 1376583765, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52476', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  User guide should open in a new tab/window', 'description': {'raw': 'From 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375474715, 'spacePHID': None, 'dateCreated': 1375472100, 'dateModified': 1417572951, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52475', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Media insertion dialog should display a message if no media is found for the given search', 'description': {'raw': 'en.wp user:Wouterstomp asks.\\n\"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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400781276, 'spacePHID': None, 'dateCreated': 1375460760, 'dateModified': 1443278231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52463', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Inserting media when text is selected should not overwrite text', 'description': {'raw': '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).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378335667, 'spacePHID': None, 'dateCreated': 1375459440, 'dateModified': 1417572839, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52460', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Toolbar floating mode broken after opening an inspector', 'description': {'raw': '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)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52504'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375475301, 'spacePHID': None, 'dateCreated': 1375424760, 'dateModified': 1417572838, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52441', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: references in image captions are not included in reflists', 'description': {'raw': 'Similar to bug 51289 and bug 52398 references that are defined in image captions do not appear in reflists. Example at [[Radiocarbon dating]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51289\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52398\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50459'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384844452, 'spacePHID': None, 'dateCreated': 1375398120, 'dateModified': 1434414601, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52427', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using browser native interactive spell-check tool breaks in Firefox', 'description': {'raw': '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.\\n\\nOn 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. \\n\\nDetailed examples are at the above link.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398187598, 'spacePHID': None, 'dateCreated': 1375343460, 'dateModified': 1417572411, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52372', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make beta notice more prominent', 'description': {'raw': '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).\\n\\nThe notice that VisualEditor is beta software should be made more prominent.\\n\\nJames has suggested showing a more prominent notice for first-time VisualEditor users (presumably based on a cookie).\\n\\nMy preference is to make the notice dismissable (using a hidden user preference).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375423690, 'spacePHID': None, 'dateCreated': 1375328880, 'dateModified': 1417572951, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52366', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor (and possibly other beta tools) need an exposed, easy-to-use on/off switch', 'description': {'raw': '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.\\n\\nJames and I discussed the possibility of adding a switch to the user interface to enable or disable VisualEditor.\\n\\nThis 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.\\n\\nThis switch might affect only VisualEditor or it might affect all \"beta\" features deployed to Wikimedia wikis.\\n\\nThis switch will be available to both logged-in users and anonymous users.\\n\\nI believe this is a high priority bug to address.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54862'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392032698, 'spacePHID': None, 'dateCreated': 1375306080, 'dateModified': 1392032698, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52355', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection highlighting breaks if an inline alien wraps', 'description': {'raw': 'wrapped inline alien: incorrect highlighting in chromium\\n\\nIf an inline alien gets word wrapped, then selecting it leads to incorrect highlighting.\\n\\nReproducing: make a <tt> ... </tt> with enough content to word wrap. Select with the mouse (or use CTRL+A).\\n\\nIn chromium, the highlighter erroneously draws a box enclosing the first character and the last (see first attachment).\\n\\nIn firefox, the highlighter erroneously highlights to the end of the first line only (see second attachment).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11839}'}, 'authorPHID': 'PHID-USER-lliyevigiycjbybglftk', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403060255, 'spacePHID': None, 'dateCreated': 1375299180, 'dateModified': 1443278234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52339', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar overlaps top of page links', 'description': {'raw': \"Toolbar 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.\\n\\nI haven't figured out how to reliably reproduce this but the following sequence /usually/ seems to work.\\n1. 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.\\n7. scroll to the top of the screen and observe the position of the toolbar.\\n\\nIf it doesn't work, try again from step 2.\\nIt 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52317\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52433\\n\\n**Attached**: {F11800}\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375936189, 'spacePHID': None, 'dateCreated': 1375281660, 'dateModified': 1417585004, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52326', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Localised tag description should link to content language documentation page', 'description': {'raw': '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]].\\n\\nWhen 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.\\n\\n[1] https://www.mediawiki.org/w/index.php?title=Localisation&action=history&uselang=en\\n[2] https://www.mediawiki.org/w/index.php?title=Localisation&action=history&uselang=nl\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-w5a723w3wes6jd5wskgg', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375216402, 'spacePHID': None, 'dateCreated': 1375192200, 'dateModified': 1417572957, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52276', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing a pasted template alters copy buffer. Displayed result differs from saved result.', 'description': {'raw': '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.\\n\\n\"To reproduce:\\n\\n1   Edit [[User:Mike Christie/Sandbox3]] in VE.\\n2   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.\\n3    Copy the selected text and then paste it at the end of the sentence.\\n4    Click on the pasted template, click on the jigsaw piece, and change the 13 in parameter 1 to a 15. Apply changes.\\n5    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.\"\\n\\nAnother test case using a different template:\\n1. 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\\n2. select \"tlp: {{tlp|as of|1999}} :\" and copy it to the clipboard\\n3. paste the template elsewhere.\\n4. edit the template you have just pasted (change parameter 2 to 2013) and apply the changes.\\n5. paste the template again.\\nExpected 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49396'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378248030, 'spacePHID': None, 'dateCreated': 1375186860, 'dateModified': 1417570404, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52271', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link widget in a slug fails with \"No class registered by that name: undefined\"', 'description': {'raw': 've.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.\\n\\nThis leaves a broken widget that takes several clicks (not sure the exact pattern here) to clear.\\n\\n5. Try to open the link widget again.  It won\\'t be possible, either with Ctrl+K or the button.\\n\\nThis is live on English Wikipedia.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50446'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377888175, 'spacePHID': None, 'dateCreated': 1375145700, 'dateModified': 1417584941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52256', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: categories being duplicated', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54169\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375223654, 'spacePHID': None, 'dateCreated': 1375125960, 'dateModified': 1424367060, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52238', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE will not save multiple consecutive references', 'description': {'raw': \"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)\\n\\nI tested it all the way down to two.\\n\\nIn 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:\\nhttp://en.wikipedia.org/w/index.php?title=User%3AMdennis_%28WMF%29%2Fsandbox&diff=566306613&oldid=566306049\\n\\nI'm using Chrome, Windows 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377824944, 'spacePHID': None, 'dateCreated': 1375117380, 'dateModified': 1417572936, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52228', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using bold button on partially bolded selection causes double-bolding', 'description': {'raw': '+++ 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. \\n\\nI should mention that in my case, the font is Arial, which has an extra bold \"Arial-Black\" variant.\\n\\nBasically the same as 50170 except that this is narrower.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395164739, 'spacePHID': None, 'dateCreated': 1375013460, 'dateModified': 1443276375, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52189', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Replacing a selected template with a keyboard press creates a pawn (♙)', 'description': {'raw': '**Author:** `jonathan_haas`\\n\\n**Description:**\\nTo reproduce:\\n\\nGoto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit\\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.\\nThe article begins with \"♙The Binding of Isaac\" then.\\n\\nAlso, 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52113'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403060346, 'spacePHID': None, 'dateCreated': 1375009500, 'dateModified': 1443278234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52185', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Be able to add or remove tables, table rows and table columns', 'description': {'raw': \"**Author:** `jonathan_haas`\\n\\n**Description:**\\nI can't find a possible way to add or edit tables, except changing the content of cells.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52641\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414522013, 'spacePHID': None, 'dateCreated': 1375007700, 'dateModified': 1469823941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52181', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Save dialog's checkboxes layout terribly if you have more than 2 items, or long i18n strings\", 'description': {'raw': 'screenshot\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52176\\n\\n//attachment VE_de_Firefox_save_dialog .png ignored as obsolete//'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384842507, 'spacePHID': None, 'dateCreated': 1374996540, 'dateModified': 1417572752, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52175', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Select-all and typing makes document significantly out-of-sync in Firefox', 'description': {'raw': '**Author:** `jonathan_haas`\\n\\n**Description:**\\nTo reproduce:\\n\\n1. Goto http://de.wikipedia.org/wiki/Hint\\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'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404955719, 'spacePHID': None, 'dateCreated': 1374993900, 'dateModified': 1443278234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Reference list not being updated during editing session', 'description': {'raw': \"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.\\n\\nTo 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-2rwkb3az6uklfhh5aqw5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384838363, 'spacePHID': None, 'dateCreated': 1374967920, 'dateModified': 1417572752, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52160', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting an existing reference in the first paragraph in Firefox puts it at the start of the paragraph, not where the cursor is', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-2rwkb3az6uklfhh5aqw5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377019526, 'spacePHID': None, 'dateCreated': 1374966180, 'dateModified': 1417572748, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52159', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing a link spanning a comment splits the link', 'description': {'raw': 'Tested on Firefox 22 (Monobook) and Chrome 28 (Vector)\\n\\nSteps to reproduce:\\n- Edit the [[Nodeulseom]] page in the visual editor.\\n- Click reference [1] and edit it.\\n- Click the hyperlink in the reference and point it to \"http://www.koreatimes.co.kr/\" (Eg: Just remove the last part from the reference)\\n- Apply the change.\\n- Hit \"Save Page\" and review the changes.\\n\\nInstead 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.\\n\\n(Diff)\\n<ref>[http://www.koreatimes.co.kr/ (The Korea Times)][http://www.koreatimes.co.kr/www/news/nation/nation_view.asp?newsIdx=5635&categoryCode=115 <!-- Bot generated title -->]</ref>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406598194, 'spacePHID': None, 'dateCreated': 1374878820, 'dateModified': 1441912202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52127', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'browsertests: triggers for ULS', 'description': {'raw': '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 \\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52890\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53691\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57560'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386338149, 'spacePHID': None, 'dateCreated': 1374875220, 'dateModified': 1427208652, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52120', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Undo keyboard shortcuts clear undo / redo history if pressed too often (And other fun)', 'description': {'raw': 'Tested 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]].\\n- Add the word \"Test\" to the page.\\n- Press Ctrl + Z to undo the edit. Keep pressing till the edit is gone, then press it once more.\\n\\nOnce 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.\\n\\nInconsistent 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.\\n\\n- 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.\\n- The undo button suddenly inserting an endless steam \"♙\" in Firefox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51532\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52185'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376621406, 'spacePHID': None, 'dateCreated': 1374869820, 'dateModified': 1417572945, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52113', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting template into slug throws JS error (causing dialogs to break)', 'description': {'raw': 'Firefox 22 - Error console.\\n\\nTested on Firefox 22 (Monobook) and Chrome 28 (Vector)\\n\\nSteps to reproduce:\\n1) Open the [[Martin J. Silverstein]] in the visual editor.\\n2) 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.\\n4) 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.\\n\\nConsole log:\\n- The added screenshot is the error console as seen in Firefox. On step 3 the \"DOM Offset\" error is added.\\n- 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11357}'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394224334, 'spacePHID': None, 'dateCreated': 1374867180, 'dateModified': 1417572580, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52112', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Write newFromDocumentReplace so editing document slices is simple', 'description': {'raw': '\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380230165, 'spacePHID': None, 'dateCreated': 1374855900, 'dateModified': 1417571283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52102', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make the \"wikitext\" link of the popup open in a new window', 'description': {'raw': 'From 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.\\n\\nThe 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.\\n\\nI 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51585\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51122'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375203313, 'spacePHID': None, 'dateCreated': 1374846180, 'dateModified': 1417572958, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52093', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"APIEditBeforeSave isn't replacing sections like the documentation claims\", 'description': {'raw': 'Reported: https://en.wikipedia.org/wiki/Wikipedia_talk:Tags#Incorrect_tagging\\nand\\nhttps://en.wikipedia.org/wiki/Wikipedia:VPT#Blanking_filter_misfire\\n\\n**See Also**:\\n* {T54049}\\n* {T54062}'}, 'authorPHID': 'PHID-USER-z3l4i7dl52qicxtephy5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375288319, 'spacePHID': None, 'dateCreated': 1374810540, 'dateModified': 1602870083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52077', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template parameters with \"autofill\" TemplateData status should be autofilled', 'description': {'raw': '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. \\n\\nAn example would be the current date for an accessdate parameter.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411174623, 'spacePHID': None, 'dateCreated': 1374764040, 'dateModified': 1443278235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52029', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: floating toolbar causes scrolling of large pages to be very slow', 'description': {'raw': '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.\\n\\nTimo says he knows how to fix this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-k6tmz5ylx4rzfl3bitse', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375232987, 'spacePHID': None, 'dateCreated': 1374729120, 'dateModified': 1417572956, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52014', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting plain text from a large page with backspace or delete is very slow', 'description': {'raw': '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). \\n\\nBug 52012 also affects backspace performance.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-k6tmz5ylx4rzfl3bitse', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375233739, 'spacePHID': None, 'dateCreated': 1374728460, 'dateModified': 1417572955, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52013', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Blocked users are not blocked from using VE (just from saving); should instead show <Blockedtext> with log entry', 'description': {'raw': 'When 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.\\n\\nThis 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.)\\n*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.\\n\\nFor some users it is even worse that that - saving fails silently: Bug 51999\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51999\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51454\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51547\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53009'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395874866, 'spacePHID': None, 'dateCreated': 1374711420, 'dateModified': 1487707626, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52004', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't re-use a reference belonging to non-default group\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51838\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377889863, 'spacePHID': None, 'dateCreated': 1374710220, 'dateModified': 1417572934, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Saving fails silently for some blocked users', 'description': {'raw': 'A 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.\"\\n\\nI am on a shared connection so I do not want to do any testing of ipblocks, etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52004'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396032185, 'spacePHID': None, 'dateCreated': 1374709740, 'dateModified': 1417572497, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51999', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Thumb images are missing appropriate CSS classes', 'description': {'raw': \"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/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374793893, 'spacePHID': None, 'dateCreated': 1374704160, 'dateModified': 1417573071, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51995', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Infinite loop (browser lockup) when removing an initial list item with a node inside it (rangy bug?)', 'description': {'raw': 'Firefox - Detected script lockup.\\n\\nMisplacing 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.\\n- Click the \"Lauda Air Flight 004\" infobox and make sure it remains selected.\\n- Click the \"Bulleted List\" button. A list bullet is added to the article.\\n- Click right after the bullet that was just inserted. Now click the \"Bulleted list\" button again.\\n\\nNormally 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11897}'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383848723, 'spacePHID': None, 'dateCreated': 1374695580, 'dateModified': 1417572756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51987', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Action buttons of the toolbar (including \"Save\") don\\'t appear on some articles in Firefox because error is thrown', 'description': {'raw': \"The particular article in the URL field of this bug report doesn't not display the Save button in Firefox.\\n\\nThe Save button is displayed in Chrome, and it is displayed in other articles in Firefox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**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\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374700983, 'spacePHID': None, 'dateCreated': 1374694260, 'dateModified': 1417573074, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51986', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking the hyper link button twice breaks the button.', 'description': {'raw': \"(Tested in Firefox 22 and Chrome 28)\\n\\nSteps to reproduce:\\n- Open [[Portland Ice Arena (Oregon)]] with the visual editor.\\n- Click the hyperlink button (Don't select anything). The hyperlink window should pop up.\\n- Now click anywhere else in the article without entering any data in the hyperlink popup. \\n- An empty popup balloon will remain behind. There are no controls on that popup anymore.\\n- 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.\\n\\nThis may or may not be related to bug 48549, which seems to have been fixed in todays deployment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1433344352, 'spacePHID': None, 'dateCreated': 1374691440, 'dateModified': 1433344352, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51984', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: A template with the RLM control character doesn't work when editing in VE\", 'description': {'raw': \"The Hebrew Wikipedia frequently uses the template {{כ}} ( https://he.wikipedia.orgw/wiki/Template:Rlm ), which inserts the &rlm; 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.\\n\\nFor reference, see https://en.wikipedia.org/wiki/Right-to-left_mark .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://he.wikipedia.org/wiki/User:Amire80/ve-rlm\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407753932, 'spacePHID': None, 'dateCreated': 1374686820, 'dateModified': 1443278235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51978', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Firefox allows cursor to get into illegal position around wide objects (<gallery>, <references>, etc), leading to corruption, and prevents down arrow button navigation', 'description': {'raw': \"1. https://en.wikipedia.org/wiki/User:Raymond/Gallery?veaction=edit\\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.\\n\\n1. Sometimes two characters will appear: 'A' <new line> '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.\\n\\n2. Sometimes a pawn appears.\\n\\n3. Sometimes only one character appears, and the 'Save page' button remains disabled.\\n\\nOn the gallery at the bottom of https://de.wikipedia.org/wiki/Hollenegg?veaction=edit , option (3) happens most often.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53750\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56248\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399418661, 'spacePHID': None, 'dateCreated': 1374664140, 'dateModified': 1417572392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51957', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Overlapping template boxes make some transclusions difficult or impossible to access', 'description': {'raw': 'Overlapping 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.\\n\\nMore 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49922\\n\\n**Attached**: {F11785}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405201146, 'spacePHID': None, 'dateCreated': 1374655380, 'dateModified': 1417572030, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51933', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Change tab order in save dialog to be more like the wikitext editor's save form\", 'description': {'raw': 'Cloning 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\".\\n\\nI 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.\\n\\nIt 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381187048, 'spacePHID': None, 'dateCreated': 1374630480, 'dateModified': 1417572306, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51918', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Return of the invalid token on save attempt problem?', 'description': {'raw': '(This sounds exactly like bug 50424, but that was marked fixed on 2013-07-15 with \"deployed within the hour\".)\\n\\nI 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.\\n\\nFirebug\\'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 https://www.mediawiki.org/wiki/Special:Version in another tab shows me as still logged in.\\n\\nMaybe 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375297527, 'spacePHID': None, 'dateCreated': 1374622800, 'dateModified': 1417585019, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51915', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374779912, 'spacePHID': None, 'dateCreated': 1374604560, 'dateModified': 1417573072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51902', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Language templates replaced by snowmen at Japanese Wikipedia', 'description': {'raw': 'The error can be seen at http://ja.wikipedia.org/w/index.php?title=ロマン主義&diff=prev&oldid=48242310\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://ja.wikipedia.org/w/index.php?title=ロマン主義&diff=prev&oldid=48242310'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407061575, 'spacePHID': None, 'dateCreated': 1374589920, 'dateModified': 1666435058, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51883', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: By default, images should not set the alignment', 'description': {'raw': '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.\\n\\nThe best solution is simply not to set the alignment and let the user change if it is needed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374629227, 'spacePHID': None, 'dateCreated': 1374568080, 'dateModified': 1417573081, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51851', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Autocompletion for template names doesn't work in RTL\", 'description': {'raw': 'Given that I\\'m editing an article in an RTL wiki: https://he.wikipedia.org/wiki/ASCII\\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.\\n\\nThis bug is quite similar to Bug 51490.\\n\\n[This was an experiment with writing bug reports as Cucumber-style test scenarios. Let me know if you don\\'t like it.]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374634378, 'spacePHID': None, 'dateCreated': 1374514020, 'dateModified': 1417573076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51828', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Location of the inspector menu is wrong for floated content in RTL wikis', 'description': {'raw': 'screenshot\\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.\\n\\nIn an RTL wiki, this template appears outside of the transparent blue area on the other side of the screen.\\n\\nYou can test it with the following article:\\nhttps://he.wikipedia.org/wiki/%D7%9C%D7%95%D7%93?veaction=edit\\n\\nSee also the screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11560}'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374637806, 'spacePHID': None, 'dateCreated': 1374510180, 'dateModified': 1417573076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51819', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Dialog panels not scrollable', 'description': {'raw': 'TempalteData-provided parameter list in template editor is not scrollable.\\n\\nFor example, try adding [[pl:Template:Okręt infobox]] to any article there.\\n\\nConfirmed on latest versions of Firefox and Opera.\\n\\nScreenshot: http://i.imgur.com/e3VSqVs.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51672'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374605597, 'spacePHID': None, 'dateCreated': 1374316620, 'dateModified': 1417572842, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51739', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Create an editor for template data (in the wikitext editor)', 'description': {'raw': \"GUI 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).\\n\\nThe 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* http://en.wikipedia.org/wiki/User:NicoV/TemplateDataEditor\\n* http://fr.wikipedia.org/wiki/Utilisateur:Ltrlg/scripts/TemplateDataEditor.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50169\\n\\n**Attached**: {F11375}\"}, 'authorPHID': 'PHID-USER-o34e5i3eq4nstbvcf26w', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389806818, 'spacePHID': None, 'dateCreated': 1374308460, 'dateModified': 1401250605, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51734', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Inline templates don't wrap, assume width:100%, so break layout around floated items\", 'description': {'raw': '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.\\n\\nSteps to reproduce:\\n1. Insert a picture or other right-aligned object that text should wrap around.\\n2. 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.\\n\\nExpected behaviour: The last word(s) of the text produced by the template wraps onto a second line.\\nActual behaviour: The entire line moves to below the picture as a single unit.\\n\\nAny 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<br>1\" wraps correctly\\n\\n\"Long text\\n1\"\\n\"Long text<br>\" and\\n\"Long text<br>\\n<!--hidden-->\" all exhibit this bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52445\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50395'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403047655, 'spacePHID': None, 'dateCreated': 1374266280, 'dateModified': 1443278238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51708', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: unlinking via linking tool triggers weird behaviors', 'description': {'raw': \"See http://it.wikipedia.org/wiki/File:Pic_-_VE_-_it_-_18_July_2013.png .\\n\\nhttp://it.wikipedia.org/wiki/Tellururo_di_mercurio_e_cadmio\\n\\nMy understanding is that unlinking can be both done by the clear formatting button or by the trash button in the linking tool.\\n\\nIf 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. \\n\\nAccording to me and itwp users that happens with both FF and Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380650852, 'spacePHID': None, 'dateCreated': 1374237180, 'dateModified': 1417572829, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51679', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog parameter filter should search on both parameter name and parameter label', 'description': {'raw': 'Two 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.\"\\n\\nI\\'ve tested this with both {{cite web}} and {{cite book}}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51822\\n\\n**Attached**: {F11265}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377959027, 'spacePHID': None, 'dateCreated': 1374227460, 'dateModified': 1417572841, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51670', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Saving fails silently when the database is locked', 'description': {'raw': \"**Author:** `kwang`\\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.\\n\\nI ended up creating the link in the source.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53093\\n\\n**Attached**: {F11178}\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374676801, 'spacePHID': None, 'dateCreated': 1374179880, 'dateModified': 1417571336, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51636', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot move cursor backwards on ligature cluster on Chrome', 'description': {'raw': 'Browser: Chrome any version.\\n\\n1. Open VE\\n2. Type or copy-paste സന്തോഷ്\\n3. Move the cursor to the end of that word.\\n4. Press left arrow to move the caret backwards.\\n5. In the second keypress onwards cursor is stuck.(like സന്തോ|ഷ് )\\n\\nExpected: cursor keep moving to left. \\n\\nObserved. cursor stuck.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-m2yck6646cdt5t6zkta4', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385506972, 'spacePHID': None, 'dateCreated': 1374128220, 'dateModified': 1417048666, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51596', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Reduce number of load.php calls on VisualEditor open (down from 3)', 'description': {'raw': 'On a regular page load:\\n\\n* http://en.wikipedia.org/wiki/Roadblock_(disambiguation)\\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.'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426388649, 'spacePHID': None, 'dateCreated': 1374089160, 'dateModified': 1427126086, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51569', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reverse selections break copy paste functionality', 'description': {'raw': '* Select some text forwards and copy-paste it, everything is great.\\n* Select some text backwards and copy-paste it, you now have an extra linebreak.\\n\\n?!???!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377195467, 'spacePHID': None, 'dateCreated': 1374074040, 'dateModified': 1417570407, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51538', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CTRL+Z occasionally inserts a pawn', 'description': {'raw': \"When typing in visual editor, sometimes pressing CTRL+Z will replace the last entered character with a pawn (♙).\\n\\nI'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.\\n\\nThere 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51762\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52113\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406599341, 'spacePHID': None, 'dateCreated': 1374065460, 'dateModified': 1417571961, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51532', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Uncaught Error: Offset could not be translated to a DOM element and offset: 2409\"', 'description': {'raw': 'Screenshot of problem\\n\\n1. Open https://en.wikipedia.org/wiki/Pancytopenia?veaction=edit#External_links\\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\\n> Uncaught Error: Offset could not be translated to a DOM element and offset: 2409\\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}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401474060, 'spacePHID': None, 'dateCreated': 1374062040, 'dateModified': 1449517807, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51526', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Block slug deletion causing very odd corruption/skipping/repeat/pawns', 'description': {'raw': 'When doing the steps outlined below, strange \\'9\\' character plus a newline appears and input it jumped backwards after 3 character.\\n\\nSee http://youtu.be/A7MWIdu3dtk for how it looks; Using http://en.wikipedia.org/wiki/Ansaldo_Poggi as test ground.\\n\\n1. Place marker under \"References\" header\\n2. hit \"backspace\"\\n3. type \"foobar\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: http://en.wikipedia.org/wiki/Ansaldo_Poggi'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383848681, 'spacePHID': None, 'dateCreated': 1374059640, 'dateModified': 1417572756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51525', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Too many clicks needed to dismiss inlink editor', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5tluooawvjfhtqywnxag', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375304932, 'spacePHID': None, 'dateCreated': 1374057840, 'dateModified': 1417572953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51523', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add a keyboard shortcut for \"Clear formatting\"', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53682\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56453'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383284035, 'spacePHID': None, 'dateCreated': 1374037140, 'dateModified': 1417584792, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51507', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reduce event rapid fire in CE', 'description': {'raw': \"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.\\n\\nWe 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384939424, 'spacePHID': None, 'dateCreated': 1374029760, 'dateModified': 1417572751, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51502', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing in Devanagari puts vowels in unexpected places', 'description': {'raw': '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.\\n\\nTo 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).\\n\\nTo get that word with the InScript keyboard, type the following keys on the English-US keyboard:\\n\\nDxidjs;]r\\n\\nThe expected result is \"अंग्रेज़ी\".\\n\\nThe actual result on Firefox 22 is \"अंग्ेच़ीर\".\\n\\nThe actual result on Chrome 28 is \"्रेची\".\\n\\nI tried this with Firefox 22 on Fedora 18.\\n\\nI 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377202382, 'spacePHID': None, 'dateCreated': 1374009180, 'dateModified': 1417048672, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51477', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace deletes combined character clusters together with diacritics', 'description': {'raw': \"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.\\n\\nIn 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.\\n\\nFor 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.\\n\\nIn the VisualEditor, backspace immediately deletes the whole cluster. This behavior is unexpected for most users.\\n\\nTo 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49233\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53757\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '40', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385506960, 'spacePHID': None, 'dateCreated': 1374007020, 'dateModified': 1472394829, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51472', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't extend links over wordbreaks\", 'description': {'raw': '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.\\n\\nWe should change the logic to stop extending the annotation once a character is added that produces a new wordbreak.\\n\\nThere 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51442'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374677110, 'spacePHID': None, 'dateCreated': 1374001860, 'dateModified': 1417572942, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51463', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Strip whitespace from the start of paragraphs before sending to Parsoid', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T53509}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377800127, 'spacePHID': None, 'dateCreated': 1374001560, 'dateModified': 1484235354, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51462', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show the <newarticletext> message when creating a new article', 'description': {'raw': \"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.\\n\\nCompare:\\n\\nsource: https://en.wikipedia.org/w/index.php?title=Aklotspa&action=edit\\n\\nVE: https://en.wikipedia.org/wiki/Aklotspa?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374676711, 'spacePHID': None, 'dateCreated': 1374000660, 'dateModified': 1417573075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51459', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspectors and context menu should close when blurring the document and/or when opening the save dialog', 'description': {'raw': '1. 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\".\\n\\nThe surface dims, but the inspector stays open and at full opacity.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408734627, 'spacePHID': None, 'dateCreated': 1373981940, 'dateModified': 1443278238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51439', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector ignores typed text if user presses [enter] too quickly, explodes with new links', 'description': {'raw': '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:\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375304939, 'spacePHID': None, 'dateCreated': 1373936940, 'dateModified': 1441912210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51415', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog should prevent adding identically-named parameters (and aliases)', 'description': {'raw': '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?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406062458, 'spacePHID': None, 'dateCreated': 1373927820, 'dateModified': 1417572023, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51406', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector crashes when inserting link on non-linkable or empty selection', 'description': {'raw': '* 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'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375304925, 'spacePHID': None, 'dateCreated': 1373927580, 'dateModified': 1441912216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51404', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'AbuseFilter: API is responding with wikitext instead of HTML in the \"warning\" property', 'description': {'raw': 'Screenshot 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.\\n\\n        \"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] https://github.com/wikimedia/mediawiki-extensions-AbuseFilter/blob/a6b1dade840841ff7adf2ff289b6428f930d6796/AbuseFilter.hooks.php#L22-L57\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11585}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373987022, 'spacePHID': None, 'dateCreated': 1373926620, 'dateModified': 1429764792, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51403', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Add parameter type for selecting one of predefined values (like \"<select>\" or ENUM)', 'description': {'raw': 'Sometimes 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.'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '1', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373910060, 'dateModified': 1713709833, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51375', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set i18n toolbar icons for bold/italics', 'description': {'raw': 'Forked 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?)\\n* sv Swedish\\n'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373918452, 'spacePHID': None, 'dateCreated': 1373840940, 'dateModified': 1689317018, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51330', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Handle 'meta' templates better\", 'description': {'raw': \"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.\\n\\nPerhaps 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51420\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374676752, 'spacePHID': None, 'dateCreated': 1373810580, 'dateModified': 1417572950, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51322', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Whitespace corruption, HTML-like entities removed, and apparent DSR issues', 'description': {'raw': '**Author:** `wmdv`\\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 [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.\\n\\nI 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. [https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Extensive_diff_report. Support desk resolution.]\\n\\nI 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Extensive_diff_report%2E'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421282222, 'spacePHID': None, 'dateCreated': 1373764920, 'dateModified': 1438734510, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51304', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set image alignment in the media dialog', 'description': {'raw': \"From 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391656868, 'spacePHID': None, 'dateCreated': 1373723400, 'dateModified': 1443276381, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51293', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '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)', 'description': {'raw': 'From 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403005130, 'spacePHID': None, 'dateCreated': 1373723100, 'dateModified': 1424894572, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51292', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Mobile Google Chrome text cursor hides link object icon', 'description': {'raw': \"On 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.\\nThe link editor icon appears below the character of text selected.\\nThe text cursor makes it impossible? to click on the link editor icon.\\n\\nOne 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399324087, 'spacePHID': None, 'dateCreated': 1373672640, 'dateModified': 1441911419, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51270', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'tag_summary missing records', 'description': {'raw': 'tag_summary duplicates data in change_tag, but is missing some records. \\n\\nEg:\\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.\\n\\nRelevant recent activity:\\n\\nhttps://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VisualEditor_tag_not_working_correctly\\n\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=40867\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-lxluxbieyr4tgfyp5jru', 'ownerPHID': 'PHID-USER-lxluxbieyr4tgfyp5jru', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382126117, 'spacePHID': None, 'dateCreated': 1373656680, 'dateModified': 1391457999, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51254', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Annotated element metadata inside wrapper paragraphs being discarded', 'description': {'raw': \"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:\\n\\n*https://en.wikipedia.org/w/index.php?title=2013%E2%80%9314_Juventus_F.C._season&curid=39905874&diff=563942424&oldid=563942210\\n*https://en.wikipedia.org/w/index.php?title=A._Dakshinamurthy&curid=16805989&diff=563911982&oldid=563853744\\n*https://en.wikipedia.org/w/index.php?title=Body_Party&curid=38681444&diff=563891098&oldid=563879499\\n\\nIn the last 12 hours or so.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373662094, 'spacePHID': None, 'dateCreated': 1373632740, 'dateModified': 1417573094, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51235', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: VE/Parsoid (?) merging unnecessary annotations together (''foo''<sub>''bar''</sub> -> ''foo<sub>bar</sub>'')\", 'description': {'raw': '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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373711757, 'spacePHID': None, 'dateCreated': 1373632620, 'dateModified': 1417573093, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51234', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Protected page warning message should include log entry', 'description': {'raw': '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.\\n\\nThat functionality does not exist in the VisualEditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50415'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395164341, 'spacePHID': None, 'dateCreated': 1373598840, 'dateModified': 1443276385, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51215', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor UI does not display MediaWiki:Editpage-head-copy-warn or MediaWiki:Wikimedia-editpage-tos-summary', 'description': {'raw': 'The source editor transcludes [[MediaWiki:Editpage-head-copy-warn]] above the edit window. But this does not appear anywhere when using the visual editor.\\n\\nNote 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374675988, 'spacePHID': None, 'dateCreated': 1373533020, 'dateModified': 1374675988, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51160', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: {{referências}} injects additional HTML (<div><references /></div>) into wikitext', 'description': {'raw': '1. Go to\\nhttps://pt.wikipedia.org/wiki/Associação_Médico-Espírita_do_Brasil?oldid=36199569&veaction=edit\\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<div class=\"reflist references-small\" style><references /></div>\\nin the bottom of the page, as in this diff:\\nhttps://pt.wikipedia.org/wiki/Associação_Médico-Espírita_do_Brasil?diff=36364362&uselang=en\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51260'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383140692, 'spacePHID': None, 'dateCreated': 1373499540, 'dateModified': 1417571286, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51145', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Double-click on a parameter in the selection menu should insert it', 'description': {'raw': 'From 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'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373932741, 'spacePHID': None, 'dateCreated': 1373498580, 'dateModified': 1417572942, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51143', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing immediately after link introduces pawn (♙) if link is preceded by multibyte text', 'description': {'raw': 'Seems to happen specifically in https://en.wikipedia.org/wiki/Jabhala?veaction=edit for no apparent reason; try it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373926253, 'spacePHID': None, 'dateCreated': 1373495580, 'dateModified': 1417573090, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51140', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Should \"remove template\" be under a label such as \"actions\" instead of options?', 'description': {'raw': '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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51672'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394073325, 'spacePHID': None, 'dateCreated': 1373485740, 'dateModified': 1443276385, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51135', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: replacing the first character in the link text inserts ♙ instead of a proper symbol', 'description': {'raw': \"**Author:** `p.selitskas`\\n\\n**Description:**\\nPage 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\\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.\\n\\nIt 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.\\n\\nWorth 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373928303, 'spacePHID': None, 'dateCreated': 1373468880, 'dateModified': 1417573090, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51112', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing return prior to the input being focused while creating a link, replaces text with new line', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373421287, 'spacePHID': None, 'dateCreated': 1373408400, 'dateModified': 1417573137, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51075', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Resizing an image without an explicit size doesn't work\", 'description': {'raw': 'If an image is formatted as [[File:foo.jpg|thumb]] rather than |BARpx, image resizing does not work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374106684, 'spacePHID': None, 'dateCreated': 1373366640, 'dateModified': 1417573085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51026', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Heading overlays toolbar in non-HD Vector integration', 'description': {'raw': 'Attaching screenshot...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390878637, 'spacePHID': None, 'dateCreated': 1373337720, 'dateModified': 1443276386, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: TemplateData is not available to VisualEditor if the template is a redirect', 'description': {'raw': 'Not sure if this is TemplateData or VisualEditor, please move it if I’m wrong.\\n\\nIf 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400886921, 'spacePHID': None, 'dateCreated': 1373307420, 'dateModified': 1453775514, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50964', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Blanking the page using Ctrl-A and Delete keys prevents further editing in Firefox', 'description': {'raw': \"To reproduce:\\n\\n* Edit a page with some existing content in VisualEditor.\\n* Press Ctrl-A to select the whole text.\\n* Press the Delete key.\\n\\nObserved: The page cannot be edited any more.\\n\\nExpected: The page doesn't have any text, but text can be added.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380309457, 'spacePHID': None, 'dateCreated': 1373297880, 'dateModified': 1417572832, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50947', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikilink editing does not permit easy alteration of display text', 'description': {'raw': '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): \\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***\\n\\n(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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52240\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50678\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=33091\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50452\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53973'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403727795, 'spacePHID': None, 'dateCreated': 1373295960, 'dateModified': 1456047619, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50945', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Extension tags are not nowiki escaped during serialization.', 'description': {'raw': 'Typing certain tag based code into VE such as:\\n\\n<math>1+2=3</math>\\n<ref>Hi</ref>\\n\\nBug reported by [[User:Dragons flight|Dragons flight]] at https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Some_tags_are_not_properly_escaped\\n\\nConfirmed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373331687, 'spacePHID': None, 'dateCreated': 1373295960, 'dateModified': 1373331687, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50944', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection highlight for templates/etc. mis-placed', 'description': {'raw': 'Copied 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:\\nhttp://en.wikipedia.org/wiki/File:Misplaced_edit_for_a_template.jpg\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375298816, 'spacePHID': None, 'dateCreated': 1373238780, 'dateModified': 1417572954, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50913', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion icon appears on the opposite side of the page in RTL wikis', 'description': {'raw': 'Replication steps:\\n\\n1. 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\\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. \\n\\nHappens in Chrome and Firefox 22.0 under Windows.\\n\\nI suspect this is again a problem with the flipped position settings. I will take a look in the code.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377734473, 'spacePHID': None, 'dateCreated': 1373232900, 'dateModified': 1417572940, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50905', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Add tooltip to byte count of save dialog explaining what it's for\", 'description': {'raw': 'The character counter of the save dialog should have a tooltip/title explaining what the counter refers entails.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392253795, 'spacePHID': None, 'dateCreated': 1373232060, 'dateModified': 1443276389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50902', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor cannot get full TemplateData on zhwiki (language variant issue?)', 'description': {'raw': \"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.\\nI 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.\\n\\nWhy 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?\\n\\n( 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**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50431\\n\\n**Attached**: {F11387}\"}, 'authorPHID': 'PHID-USER-ixwg3kf22idjy7x4ncxf', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383257477, 'spacePHID': None, 'dateCreated': 1373206260, 'dateModified': 1383257477, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50888', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Display the contextual menu for templates much more visibly', 'description': {'raw': \"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.\\n\\nNow 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.\\n\\nFor instance, take the {{Refbegin}}-{{refend} block on this page https://en.wikipedia.org/wiki/Warehouse_control_system?veaction=edit on a fairly large monitor.\\n\\nIt 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.\\n\\nPoint 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414104265, 'spacePHID': None, 'dateCreated': 1373101500, 'dateModified': 1417571292, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50854', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edits made by users with +reviewer rights should not get flagged on pages with FlaggedRevs enabled', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49699'}, 'authorPHID': 'PHID-USER-yif6nz5uhka5cnltixpc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373145698, 'spacePHID': None, 'dateCreated': 1373091660, 'dateModified': 1417573142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50852', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspecting image immediately after inserting it causes exception', 'description': {'raw': '1. 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 </p><img></img><p> rather than just the image.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377894433, 'spacePHID': None, 'dateCreated': 1373080620, 'dateModified': 1417572842, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50850', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '<nowiki> tags should be applied to the minimal rather than maximal content (or well, a compromise thereof..)', 'description': {'raw': \"Right now the following HTML entered by a user:\\n\\n<p>Hello my [[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].</p>\\n\\n… turns into:\\n\\n<p>Hello my <nowiki>[[name]] is Julian and I live in the city of Rochester, New York with my friend Sandy; we write [[books]].</nowiki></p>\\n\\n… whereas ideally it should be minimal rather than maximal:\\n\\n<p>Hello my <nowiki>[[</nowiki>name<nowiki>]]</nowiki> is Julian and I live in the city of Rochester, New York with my friend Sandy; we write <nowiki>[[</nowiki>books<nowiki>]]</nowiki>.</p>\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374181853, 'spacePHID': None, 'dateCreated': 1373063340, 'dateModified': 1374203128, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50841', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Loading a page which requires many fonts causes high CPU load', 'description': {'raw': 'see report here:\\n[[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).\\n\\nInitial debugging of the issue points to the function injectCSS().\\nas 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.\\n\\napparently, 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.\\n\\nclearly, 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.\\n\\nthis 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.\\n\\n\\n(btw: the function itself is somewhat disgusting. how is it better than\\n\\nfunction injectCSS( css ) {\\n\\t$( \\'<style>\\' , {type: \\'text/css\\', rel: \\'stylesheet\\' } )\\n\\t.text( css )\\n\\t.appendTo (\\'head\\' );\\n}\\n\\n// really no need to return anything: the single callsite ignores \\n// the return value anyway. anywho, you can prepend \"return\" \\n// to make it behave more like existing code if you really want to...\\n\\n\\npeace.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technical%29&oldid=563037747#Heavy_Javascript_load_after_loading_some_articles.\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49935\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51073'}, 'authorPHID': 'PHID-USER-akv4ingxkspiiam6r2n4', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379659587, 'spacePHID': None, 'dateCreated': 1373056800, 'dateModified': 1379659587, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50836', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add support for spam blacklist errors in save dialog', 'description': {'raw': 'If a user hits the spam blacklist they VE responds merely by informing them \"Error: Invalid error code\". This is...not helpful.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374016034, 'spacePHID': None, 'dateCreated': 1373053740, 'dateModified': 1431126449, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50826', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using browser native interactive spell-check tool breaks in Firefox', 'description': {'raw': 'Quote: Using Firefox 19.0.2 on Windows Vista, editing Relativity Media. Find \"subsidairies\", right-click, select \"subsidiaries\". The word appears changed, but the \"Save\" button is not activated.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63462\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63395\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=59748'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415058499, 'spacePHID': None, 'dateCreated': 1373050560, 'dateModified': 1417584187, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50822', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Changing templates makes wikilinks ([[Foo|Bar]]) render as raw wikitext instead of parsed', 'description': {'raw': 'Template inspector before closing\\n\\nWikilinks like [[Foo|Bar]] are shown expanded in template inspector after closing it, see screenshots. \\n\\nSteps to reproduce:\\n\\n1. Edit a template which has wikilinks like [[Foo|Bar]] as a parameter value\\n2. Close the template inspector, with or w/o changes does not matter.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://de.wikipedia.org/wiki/VRB_H_2/3\\n\\n**Attached**: {F11204}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373559177, 'spacePHID': None, 'dateCreated': 1373030040, 'dateModified': 1417573095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50801', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Break lines for TemplateData description in template inspector', 'description': {'raw': 'Screenshot\\n\\nThe text of the TemplateData description should have an line break (wrap into span and style per CSS?) in the template inspector.\\n\\nLonger descriptions flows out of the template inspector box, see screenshot.\\n\\nRelated: Bug 50656 - Parse wikicode and/or HTML in interface text\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11203}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373420952, 'spacePHID': None, 'dateCreated': 1373028960, 'dateModified': 1417573138, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50800', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add close icon to page notices fly-out', 'description': {'raw': 'At the moment the only way to close a page notice is to click on the interface element that launches them - which feels somewhat counterintuitive. Could we have a little close button in the notices themselves?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383279877, 'spacePHID': None, 'dateCreated': 1373028000, 'dateModified': 1417572758, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50799', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using the formatting drop-down scrolls the page to the top (except in Firefox)', 'description': {'raw': 'This happened on MediaWiki, he.wiki and en.wiki on Chrome.\\n\\nOpen some article for editing (preferably a long one so the effect is seen)\\nadd some text in the middle or end, mark it and make it a \"Heading\". \\n\\nObserved result: The text turns into a heading, but the entire edit section scrolls up to the top of the page. This is especially annoying when the page is long and when the edit is done in the middle.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373415137, 'spacePHID': None, 'dateCreated': 1373007960, 'dateModified': 1417573138, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50792', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Move “add parameter” button to alongside the search field, not below the results list, so it can be found', 'description': {'raw': '**Author:** `turingt`\\n\\n**Description:**\\nAt the Transclusion dialog, after a click or double-click on the chosen parameter, nothing happens. Is the user expected to click on the \"Add parameter\" label at the top? To press Enter? To read the user guide for instruction on how  ? None of these steps help.\\n\\nThis is a usability bug - the actual button is hidden below the fold, at the end of a very long list that is not intended to be scrolled through, and thus hard to discover. The button should be always visible in the dialog - otherwise, the dialog becomes unusable with long lists of parameters.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373932787, 'spacePHID': None, 'dateCreated': 1372974060, 'dateModified': 1417573089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50774', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] VisualEditor: The \"Add parameter\" confirmation button should be close to the input field (at least visible)', 'description': {'raw': \"Especially when a template has many parameters;\\nscrolling until you find the actual button to add them,\\nhaving to add them one by one and having to do so by clicking each time on the name of the template itself to get to the list again, it's confusing users.\\nThere's already a bug about mandatory parameters not being enforced; I am not sure of the behaviour related to the order of the parameters, but it would be great if the editor could keep them in the same order they're being chosen with. Thanks :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374257794, 'spacePHID': None, 'dateCreated': 1372970700, 'dateModified': 1417585091, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50773', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Mark hidden categories as different in the meta-data dialog so users understand they won't display\", 'description': {'raw': 'The existing editing interface stores data on hidden categories, and on the templates in use. This is not displayed in the existing VE - it seems like the sort of thing the page settings page might be good for.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393467412, 'spacePHID': None, 'dateCreated': 1372964580, 'dateModified': 1444199712, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50763', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: broken <table> syntax causes VE to inject additional <table> html', 'description': {'raw': 'In this case, https://en.wikipedia.org/w/index.php?title=Long_Island&diff=562848384&oldid=562113547 - oh dear.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374329698, 'spacePHID': None, 'dateCreated': 1372954980, 'dateModified': 1374329698, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50754', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Incorrectly displaying nested references', 'description': {'raw': 'Copied from English Wikipedia:\\n\\nA similar bug was reported as #49536 , but closed as fixed a while ago. Article Otto I has a reference (\"ref\") to \"Thompson\" (numbered #11 in old edit mode) inside an explanatory footnote \"efn\". The notes are generated below the article using \"notelist\". Ref 11 Thompson is not included in the reflist of VE, but shown in regular read mode. Just compare the reference lists in read and in VE edit mode to see the difference. GermanJoe (talk) 13:03, 4 July 2013 (UTC)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51289\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52398'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408586751, 'spacePHID': None, 'dateCreated': 1372948260, 'dateModified': 1434414601, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50749', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters', 'description': {'raw': \"TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60358\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410982793, 'spacePHID': None, 'dateCreated': 1372947300, 'dateModified': 1443278246, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50747', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Transclusion dialog's layout of template's parameters broken (CSS caching issue?)\", 'description': {'raw': \"http://en.wikipedia.org/wiki/File:VisualEditor_-_Cite_template_layout_issue_%28TemplateData%29.png\\n\\nTested on Firefox 22, Mono skin:\\n\\n'''Steps to reproduce'''\\n* Open any random page in the visual editor.\\n* Add a new template - use Cite Web for this.\\n\\nThe output will be akin to the screenshot added. Some the template parameters end up next to each other, and are thus offscreen. Even if that is not the case the description will often be to long to be displayed. Would be nice if those ended up on a new line if that occurred.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373503064, 'spacePHID': None, 'dateCreated': 1372928700, 'dateModified': 1417573098, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50728', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Save action doesn't handle abort hooks very elegantly\", 'description': {'raw': 'When your edit trips the blacklist or an editfilter, you get a very technical and uninformative message.\\n\\nThe edit filter causes:  \"Error: The notification you tried to make was aborted by an extension hook\" to show in the \\'save\\' dialog.\\n\\nThe URL blacklist:  \"Invalid code error\" apparently.\\n\\nhttps://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562806113#Blocked_sites\\n\\nSince this is quite common for newbs to trip, it should be handled better.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**URL**: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562806113#Blocked_sites'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374112342, 'spacePHID': None, 'dateCreated': 1372928040, 'dateModified': 1417573085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50727', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Broken accesskey on edit tab (Ctrl-Alt-e)', 'description': {'raw': 'This broke during yesterdays deploy. Now shows <accesskey-ca-editsource> and no key is set. I think Timo fixed it already, but the fix might not have been deployed yet.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373051656, 'spacePHID': None, 'dateCreated': 1372926360, 'dateModified': 1417573142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50725', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Can no longer access save dialog (cursor keys/backspace/etc.) if it ever loses focus', 'description': {'raw': 'Steps to reproduce:\\n\\n* Navigate to [[Mariposa botnet]] and edit the page in the visual editor.\\n* Make any textual change - just add \"Test\" somewhere for example.\\n* click \"Save Page\"\\n* Adding a reason doesn\\'t matter. Just click to close the save page popup.\\n* Immediately open it again (Don\\'t click anywhere else)\\n* Try to add a text as the reason, then press backspace or delete what you just added.\\n\\nFor some reason delete and backspace won\\'t work anymore. My guess is that the backspace is send to the editing canvas instead of the textbox - try the following steps as well:\\n\\n* (Do all the steps from the first section)\\n* Press \"Review Your changes\".\\n* Wait for the review to load, then press \"Return To Save\", and close the resulting form.\\n* Now click the search block (In mono) and enter a random search criteria.\\n* Once entered, try to remove it again.\\n\\nWhat happens for me: Entering data in the search box works fine, but pressing backspace somehow causes text to be removed from the article, instead of the search box i was just typing in.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49569'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381187020, 'spacePHID': None, 'dateCreated': 1372923300, 'dateModified': 1417584853, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50722', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox', 'description': {'raw': '(Tested on Firefox 22, Monobook skin)\\n\\nSteps to reproduce\\n\\n- Go to the \"The Damned Thing (short story)\" page and edit it with the visual editor.\\n- Go to the \"Gothic elements\" selection, and select all the text from \"Gothic elements\" (Header) to \"inadequate.\" (Last word of the section). This should also select the image.\\n- Click and drag the entire section, and drop it of before the \"Analysis\" section (Just drop it right before the A in that word, make sure the text entry | is displayed. The image itself will be gone. But for the fun part: Click anywhere on the editing canvas text.\\n\\nSuddenly, your entire input screen will be white. What seems to happen is that the image is blanked (Replaced by a white square) and plastered full size all over the page. You can try to drag it away, but each time you try it will replace itself over the pages content.\\n\\nhttps://en.wikipedia.org/wiki/File:Visual_Editor_-_Giant_White_Image.png contains a screenshot of the problem.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50643'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375772188, 'spacePHID': None, 'dateCreated': 1372922700, 'dateModified': 1375772188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50721', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Transclusion dialog doesn't account for aliases when preventing duplicate entries from being added\", 'description': {'raw': 'Note that this is not the same as bug 50715. Though they behave the same from the user point of view, bug 50715 is for a case where aliases are not in play.\\n\\ne.g. given our Unsigned template with parameter \"user\", \"timestamp\" and aliases \"1\" and \"2\" respectively.\\n\\nHaving added \"mw.log(\\'addParameterSearch-select\\', name, names);\" to ve.ui.MWTransclusionDialog#getTemplatePage in the select event handler of the addParameterSearch object; editing the following invocations:\\n\\n case {{Unsigned|Foo|April 1}}\\n case {{Unsigned|1=Foo|2=April 1}}\\n    typing \"1\"\\n    >  addParameterSearch-select null [\"1\", \"2\"]\\n    >  addParameterSearch-select \"user\" [\"1\", \"2\"]\\n    > \"Add\" is enabled\\n    typing \"user\"\\n    >  addParameterSearch-select null [\"1\", \"2\"]\\n    >  addParameterSearch-select \"user\" [\"1\", \"2\"]\\n    > \"Add\" is enabled\\n\\n case {{Unsigned|user=Foo|timestamp=April 1}}\\n    typing \"1\"\\n    >  addParameterSearch-select null [\"date\", \"user\"]\\n    >  addParameterSearch-select 1 [\"date\", \"user\"]\\n    > \"Add\" is enabled\\n    typing \"user\"\\n    >  addParameterSearch-select null [\"date\", \"user\"]\\n    >  addParameterSearch-select null [\"date\", \"user\"] \\n    > \"Add\" is disabled\\n\\nThe latter case actually works as expected, although it is odd that the value given to the select callback is null and not \"user\" and that the button is already disabled (probably by the select widget?).\\n\\nAlso weird that the callback is constantly triggered twice, once for null and once for the actual value.\\n\\nAnyway, the solution is to resolve the names to their alias origins before doing the names.indexOf( name ) check.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373497400, 'spacePHID': None, 'dateCreated': 1372913640, 'dateModified': 1417573136, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50717', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Binding of section edit link should not be deferred to after document is loaded', 'description': {'raw': 'Split from bug 50540 which is entirely different. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376520602, 'spacePHID': None, 'dateCreated': 1372883340, 'dateModified': 1417572947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50692', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way for the user to one-way switch from VisualEditor into wikitext source editor mode without saving', 'description': {'raw': 'Copying from English Wikipedia:\\n\\nOkay, this one is probably quite tricky: When editing the source code, if an edit conflict arises, you can simply hit the back button, copy the code, and paste it into the updated version. However, with the Visual Editor, this is no longer possible. The content goes away, so you have to re-add it all, which is a huge pain if it involves references and other templates.--¿3family6 contribs 18:25, 3 July 2013 (UTC)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=47779\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52519\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56465'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383257358, 'spacePHID': None, 'dateCreated': 1372878900, 'dateModified': 1628817814, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50687', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Undo\" of image resizing causes wonky displacement', 'description': {'raw': 'From English Wikipedia:\\n\\n\\'\\'\\'Steps to reproduce:\\'\\'\\'\\n* Edit the [[Vogrie House]] article in the visual editor.\\n* Resize the image. Larger or smaller doesn\\'t matter.\\n* Press either CTRL + Z, or undo the edit using the undo button. \\n\\nInstead of undoing the edit, it suddenly enlarges the image object. The image is placed in the center of the screen, and the object itself even overlaps the main navigation in the Mono interface. Of course as always: Firefox 22 used to test this. [[User:Excirial|<font color=\"191970\">\\'\\'\\'Excirial\\'\\'\\']]</font><sup> ([[User talk:Excirial|<font color=\"FF8C00\">Contact me</font>]],[[Special:Contributions/Excirial|<font color=\"FF8C00\">Contribs</font>]])</sup> 18:03, 3 July 2013 (UTC)\\n\\nSee screenshot:\\nhttp://en.wikipedia.org/wiki/File:VisualEditor_-_Undoing_a_resize_issue.png\\n\\nI tried on Chrome on a Mac, and it didn\\'t work there, either, but instead shoved the image to the left of the screen\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372901775, 'spacePHID': None, 'dateCreated': 1372875420, 'dateModified': 1417573145, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50682', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Miscellaneous additions of nowiki tags', 'description': {'raw': 'In https://en.wikipedia.org/w/index.php?title=List_of_socialist_countries&curid=7252916&diff=562675715&oldid=562675131\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373638390, 'spacePHID': None, 'dateCreated': 1372853220, 'dateModified': 1417573093, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50659', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE interface overlapping with main WP interface in monobook w/ small resolutions', 'description': {'raw': 'See https://en.wikipedia.org/wiki/File:Visual_Editor_-_Overlapping_issue.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372893914, 'spacePHID': None, 'dateCreated': 1372843980, 'dateModified': 1417573147, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50652', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Resizing an image which doesn't already have an explicit size set doesn't work\", 'description': {'raw': 'What it says on the tin; if you resize an image, it with reports \"this isn\\'t a change, can\\'t save\" or saves and silently doesn\\'t do anything.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392223392, 'spacePHID': None, 'dateCreated': 1372840560, 'dateModified': 1417572732, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50645', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Space inserted before link after single-character deletion', 'description': {'raw': 'From https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE_adding_spaces.2C_messing_with_citation_access-dates:\\n\\nI noticed something odd when using VisualEditor. I decided to use it when snooping around for various \"it\\'s\" typos, for removing apostrophes seemed/is faster with VE than the old fashioned way. However, some of my edits seem to have done more than take out apostrophes. Seven times today ([http://en.wikipedia.org/w/index.php?title=Highcroft_Racing&diff=prev&oldid=562630195] [http://en.wikipedia.org/w/index.php?title=So_Emotional&diff=prev&oldid=562630132] [http://en.wikipedia.org/w/index.php?title=1988_in_British_television&diff=prev&oldid=562629968] [http://en.wikipedia.org/w/index.php?title=Olmaliq_FK&diff=prev&oldid=562629768] [http://en.wikipedia.org/w/index.php?title=FC_Jazz&diff=prev&oldid=562629613] [http://en.wikipedia.org/w/index.php?title=Brian_McDaniel&diff=prev&oldid=562629235] [http://en.wikipedia.org/w/index.php?title=Highlights_(band)&diff=prev&oldid=562629182]), VE added an extra space in a random place in the article (if it\\'s hard to tell, on the last one it added the space right after \"its\"). And then it altered references on [http://en.wikipedia.org/w/index.php?title=God_of_War_(series)&diff=prev&oldid=562631132 another], including changing access-dates. I don\\'t think that\\'s supposed to happen... [[User:Greengreengreenred|<font color=\"#014421\">Green</font>]][[User talk:Greengreengreenred|<font color=\"#50C878\">green</font>]][[Special:Contribs/Greengreengreenred|<font color=\"#66FF00\">green</font>]]<font color=\"red\">red</font> 02:25, 3 July 2013 (UTC)\\n\\n\\nMight be a Parsoid bug based on selser tracing. There seems to be only a single space both in the original and the edited HTML.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372829646, 'spacePHID': None, 'dateCreated': 1372821780, 'dateModified': 1374736002, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50636', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Split mw.ViewPageTarget init from integration handling', 'description': {'raw': 'This doesn\\'t mean that all of the integration needs to be independent (save dialog etc.) just the initialisation.\\n\\nIt used to be that the integration was only initialisation (instantiate the editor with the html document to edit, basically only up to a dozen lines of code) but it has become much more than that.\\n\\nWe need to separate integration and initialisation (initialisation will be part of the platform specific integration, but code-wise it should be the tip of the pyramid, not the bottom), so that our MediaWiki initialisation should be completely isolated so we can load it from the <head> and it will do only 2 things:\\n\\n1) Browser compatibility test (bug 50608)\\n   - May depend on jQuery and a few plugins\\n   - May not depend on any VE classes since those may break in our subset\\n     of supported browsers (compared to MediaWiki/jQuery)\\n\\n   (if passed)\\n2) Perform our changes to the interface to avoid flash of \"pre-init\" state\\n   - Edit tab (bug 50542)\\n   - Edit section links (bug 50540)\\n   - Handle setup/teardown of VE from either clicking an \"Edit\" link\\n     or by url query.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50677'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372894223, 'spacePHID': None, 'dateCreated': 1372800600, 'dateModified': 1428038331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50612', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Browser compatibility test should not be done in the middle of init after (pre)loading all of core', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372894193, 'spacePHID': None, 'dateCreated': 1372798800, 'dateModified': 1417573146, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50608', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Language links do not take namespace into account', 'description': {'raw': \"Check page settings for https://en.wikipedia.org/wiki/User:John_of_Reading?veaction=edit - it's probably not necessary to have language linking for userspace, but if we're going to do it the ability to distinguish sandboxes from articles would be good.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381266333, 'spacePHID': None, 'dateCreated': 1372756200, 'dateModified': 1417572824, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50565', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page notices overlap dialogs', 'description': {'raw': '**Author:** `Thehelpfulonewiki`\\n\\n**Description:**\\nPage notice overlaps the close button on page settings\\n\\nI tried to edit Barack Obama using the Visual Editor. The page notice came up - which is fine - but then I clicked on the page settings without dimissing the page notice and wasn\\'t able to dismiss the page notice. The page notice covers the close button so the only button I could press is \"apply changes\" to causes the page settings window to go away, allowing me to hide the page notice.\\n\\nI was told in #-visualeditor that you can click anywhere in the notice itself to dismiss it - something I didn\\'t even consider doing because that\\'s not standard behaviour for notifications (considering Facebook and even Echo). Please can we make the page notice dismissable by clicking on the \"1 notice\" area, even if you\\'ve got the page settings window up?\\n\\nSee attached screenshot for an illustration of the problem.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49059\\n\\n**Attached**: {F11576}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372809200, 'spacePHID': None, 'dateCreated': 1372730460, 'dateModified': 1417573087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50545', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"[edit | edit source]\" appears jumbled in RTL wiki with LTR interface', 'description': {'raw': \"Inside an RTL wiki, if you set your interface to English (or any other LTR language) you will see that the '[edit | edit source]' links are jumbled.\\n\\n(Example: https://he.wikipedia.org/wiki/%D7%A4%D7%99%D7%96%D7%99%D7%A7%D7%94 - use English interface)\\n\\nThis is probably again a case of bidi isolation. I can take a look at the code.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372781960, 'spacePHID': None, 'dateCreated': 1372726200, 'dateModified': 1417573149, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50543', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tab layout should be done from a top-loading module', 'description': {'raw': 'The \"Edit source\" tab loads/renders a little bit after the \"Edit\" tab, sometimes more noticeably so, sometimes less. Relatedly, clicking the \"Edit\" tab very early on sometimes invokes the wikitext editor. \\n\\nIt would be preferable for both tabs to be rendered simultaneously with the correct default behavior.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375423118, 'spacePHID': None, 'dateCreated': 1372725780, 'dateModified': 1417572951, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50542', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Display both \"edit\" and \"edit source\" links for sections without hover', 'description': {'raw': 'A long-standing editor feels that the delay before the \"edit source\" option in sections disadvantages those who wish to bypass VE. Is it possible to have the \"edit source\" link visible always?\\n\\nSee:\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562471642#Very_slow_and_featureless\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56337'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375464355, 'spacePHID': None, 'dateCreated': 1372724940, 'dateModified': 1417584837, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50540', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Firefox 10 and under have issues and should be blacklisted', 'description': {'raw': 'A firefox 5.0 user is reporting that blacklisting simply isn\\'t working - they\\'re seeing the VE, broken. Their response to \"are you spoofing user headers\" was along the lines of \"what the heck is that?\" which answers that question.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372727423, 'spacePHID': None, 'dateCreated': 1372719060, 'dateModified': 1464692696, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50534', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Searching to re-use an existing reference doesn't use the correct internal list\", 'description': {'raw': '**Author:** `rachelqa99`\\n\\n**Description:**\\nenter erroneous text for existing reference\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/User:Rachel99/testing_070113?veaction=edit\\n\\n**Attached**: {F11502}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380559887, 'spacePHID': None, 'dateCreated': 1372712580, 'dateModified': 1417572830, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50520', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Duplicating text in template on unrelated edit', 'description': {'raw': \"I suspect this may be related to an existing bug, but if so I can't figure out how to find it.\\n\\nLooking at the very bottom change on http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562259398, we see the first in a series of edits where editing elsewhere adds duplicated characters to a template that I don't believe is being edited directly. (Further duplication occurred in these edits to the same page: http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562359846, http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562363670, http://en.wikipedia.org/w/index.php?title=User:SLBohrman&diff=next&oldid=562363840)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383006754, 'spacePHID': None, 'dateCreated': 1372695120, 'dateModified': 1417572818, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50502', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Likely invalid HTML emitted for list items', 'description': {'raw': 'Screenshot of list indent problem\\n\\nIf I add indent to any list item, it breaks. \\n\\nThe indented line gets moved to the end of the previous line.\\n\\nThe live-changes looks as it is working properly, but the edit-diff (preview your changes) always shows it as broken. (See attachment)\\n\\nConfirmed with:\\n* Firefox and Chrome,\\n* with ordered and un-ordered list items, \\n* with items added to the middle of a list, and to the end of a list,\\n* and with both new items added to a list, and existing items given increased indent.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F11420}'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372709778, 'spacePHID': None, 'dateCreated': 1372641600, 'dateModified': 1372709778, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50483', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add a link to the User Guide to the interface', 'description': {'raw': \"As per http://www.mediawiki.org/wiki/Help_talk:VisualEditor/User_guide#Discoverability .\\nMight be handy, since we're pretty much beginners with it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372703974, 'spacePHID': None, 'dateCreated': 1372621440, 'dateModified': 1417573150, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50476', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show the warning of a triggered AbuseFilter filter in the save dialog', 'description': {'raw': '[Forked from the more general 50350.]\\n\\nCurrently when AbuseFilter blocks an edit made with VE, the only response we can display is:\\n\\n| The modification you tried to make was aborted by an extension hook\\n\\nWhen bug 32216 is done - AbuseFilter is changed to use the APIEditBeforeSave hook - we can display this significantly more nicely.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374090444, 'spacePHID': None, 'dateCreated': 1372618620, 'dateModified': 1417573083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50472', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Newest CSS not showing up in production for some users (so reference editor not correctly formatted)', 'description': {'raw': \"Screenshot\\n\\nSee screenshot. Firefox 21.0, Windows XP. As well as misplacing the toolbar it's also hiding the 'create new source' on articles with lots of sources.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11391}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373852943, 'spacePHID': None, 'dateCreated': 1372617600, 'dateModified': 1417573092, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50471', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clear annotations icon no longer clearing link annotations', 'description': {'raw': 'The formatting icons of the VisualEditor toolbar are currently \"B\" for bold, \"I\" for italics, the chain for links and the remove icon to clear formatting.\\n\\nThis series of icon seems to indicate that links are a kind of formatting. However; \"Clear formatting\" doesn\\'t affect links; it only removes bold and italics.\\n\\nEither links *are* a kind of formatting, and the \"Clear formatting\" action should remove them, or they aren\\'t, and the Link icon shouldn\\'t stand in the middle of icons that add and clear formatting. The current order and behavior are confusing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373930966, 'spacePHID': None, 'dateCreated': 1372600920, 'dateModified': 1417585118, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50461', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: References in media captions appear but aren't editable or successfully insertable\", 'description': {'raw': 'It is currently not possible to add a reference to an image/media caption, nor to edit existing ones.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52427\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49657'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380835418, 'spacePHID': None, 'dateCreated': 1372597320, 'dateModified': 1417572502, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50459', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Improvements to reference editing, including local wiki-specific workflows', 'description': {'raw': 'Screenshot1\\n\\nThere are, I think, some UI improvements to be made to the reference editor - User:Popcornduff gets credit for these :).\\n\\nWhen you first open the reference editor, you\\'re presented with something like screenshot 1, which asks you \"What do you want to reference?\" If the user is coming to try and add a new reference, this is highly confusing - the first UI element they\\'re presented with prompts them to put time into a series of actions that cannot possibly end with them finding what they want. The cue also doesn\\'t make clear to any user what the search bar is actually doing - filtering existing references. It seems like the blurb here might need changing to align it with what the search bar actually does; \"search existing references on this page\"?\\n\\nIf you click \"create new source\", absolutely nothing happens - it\\'s a highlightable element, and after a bit you can puzzle out that it unlocks \"create reference\", but it\\'s not immediately clear. Still, you end up with it highlighted (see screenshot2). The blurb in \"insert reference\" is rather confusing; what am I inserting? I\\'m here to /add/ a new reference, I haven\\'t written it out yet. My suggestion would be to have \"create new source\" take you straight to the source creation interface using a one-click mechanism, rather than having it free up \"insert no references\".\\n\\nStill, you click it, and you get to screenshot3, of a window tagged \"reference content\". Quoth the user, \"Is it reference the verb - am I referencing content here? Or am I giving content to the reference?\\n\\nWhat is the Options heading all about, and what does \"Use this group\" mean?\\n\\nI have a little window here to type into. I\\'m not sure what to type. Do I just write out my reference in Wikimarkup and click \"Apply changes\"? Or do I write them out as if I\\'m writing a list of references at the end of an essay?\\n\\nAt this point I\\'m really disappointed. I was hoping to be given a complete list of individual fields to fill out - a box for author, a box for date, a box for date accessed, a box for the title, a box for the URL, and so on - and have this generate the reference nicely for me. Instead, I seem to have the old system in a confusing UI.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51848\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53590\\n\\n**Attached**: {F11364}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401472375, 'spacePHID': None, 'dateCreated': 1372596600, 'dateModified': 1510753333, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50458', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: When inserting a new link (not annotating on existing text), the suggested link is capitalised even if your input text isn't, so leading to unexpected capitalisation of link anchors\", 'description': {'raw': \"When adding a new link to an existing page, the text is automatically capitalized, even if the user entered the text in lowercase. Many links don't need to be capitalized, so users shouldn't have to clean up after VisualEditor decides to capitalize them.\\n\\nNote that when you're adding a new link to a page that doesn't exist, the inserted link preserves the capitalization that was entered by the user (which is the expected behavior)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50945\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50678\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50745\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53566\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378254877, 'spacePHID': None, 'dateCreated': 1372587540, 'dateModified': 1566904183, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector in a slug can select content in the previous or following paragraphs', 'description': {'raw': \"If the cursor is in a slug and you press the link button, the selection jumps to the nearest content - which crosses out of the local <p> and into the <p> beforehand or afterwards (whoops).\\n\\nLink inspector should detect that it is in a slug and not attempt to mangle the selection with nearestContentOffset, but just trigger with a 'blank' selection.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52256\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377888669, 'spacePHID': None, 'dateCreated': 1372572900, 'dateModified': 1417572934, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50446', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: References with duplicated content are normalised away', 'description': {'raw': 'If you have a page like:\\n\\n<ref name=\"foo\">Foo</ref> ...... <ref name=\"foo\">Foo</ref>\\n\\nVE will normalize this to:\\n\\n<ref name=\"foo\">Foo</ref> ...... <ref name=\"foo\" />\\n\\nThe contents of the second <ref> tag are obviously ignored, but we should round-trip their existence correctly.\\n\\n\\nhttp://tools.wmflabs.org/visualeditor/dirtydiffs/2013-06-30_00-52/Genetic_history_of_the_Iberian_Peninsula.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372705872, 'spacePHID': None, 'dateCreated': 1372567200, 'dateModified': 1417573150, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50444', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: TemplateData hints doesn't show up on parameters in transclusion dialog\", 'description': {'raw': 'After having saved a template on a page, and edit it again, template data for the template is visible, but any parameter used is not showing templatedata, even though it displayed it correctly when I created the template\\n\\ntest I made on beta was {{test|name = hello}}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384200108, 'spacePHID': None, 'dateCreated': 1372554600, 'dateModified': 1417572817, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50440', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Process language fallback and conversion server-side', 'description': {'raw': 'After I added the <templatedata> to [[pt:Template:Referências]], I opened a page in which it is used, setting \"uselang=pt\" and \"uselang=pt-br\" in the URL:\\n1) https://pt.wikipedia.org/wiki/Arte?veaction=edit&uselang=pt\\n2) https://pt.wikipedia.org/wiki/Arte?veaction=edit&uselang=pt-br\\nIn the first case, when I opened the Transclusion dialog (by clicking in the references section, where the template is used) the template description was shown (as expected). Typing one of the template parameters, I also get its label normally.\\n\\nOn the other hand, for the second link the user language (pt-br) was different from the content language (pt) and the user see no description and no labels.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50888'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381172295, 'spacePHID': None, 'dateCreated': 1372534860, 'dateModified': 1381172295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50431', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Protected page warning messages are missing', 'description': {'raw': 'VE is missing the red \"semi-protected page\" box seen at\\nhttp://en.wikipedia.org/w/index.php?title=Muscle&action=edit and probably also the equivalent one for administrators on fully protected pages.\\n\\nThey should be displayed as a \"notice\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51215'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373498492, 'spacePHID': None, 'dateCreated': 1372489200, 'dateModified': 1417573095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50415', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '<span> floats out of a table(?)', 'description': {'raw': 'Possibly related to Bug 49892, VE is inserting random <span> parameters.  \\n\\nSee:\\nhttps://en.wikipedia.org/w/index.php?title=Ruger_P_series&diff=next&oldid=560801075\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373061530, 'spacePHID': None, 'dateCreated': 1372450980, 'dateModified': 1373061530, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50392', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edits triggering CAPTCHA cannot be saved', 'description': {'raw': 'On a CAPTCHA-triggering edit, VE does not display the CAPTCHA, instead showing an alert:\\n\\nError saving data to server: Failed request: error.\\n\\nMarking critical, because VE is in use by 50% of new users at enwiki, none of whom are now able to add external links for sourcing purposes.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372582072, 'spacePHID': None, 'dateCreated': 1372413660, 'dateModified': 1434768391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50356', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Message shown when edits are disallowed by API needs to be clearer', 'description': {'raw': 'When attempting an edit that is disallowed by AbuseFilter, you get a browser alert:\\n\\nError saving data to server: Unsuccessful request: The modification you tried to make was aborted by an extension hook.\\n\\nInstead, VE should show a less cryptic message specific to AbuseFilter.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372703938, 'spacePHID': None, 'dateCreated': 1372407600, 'dateModified': 1417573151, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50350', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VE does not support typing in Kannada', 'description': {'raw': \"VE's behaviour is not as expected when I invoke my own IME for entering Kannada text. If I press Enter after typing some text, it creates a blank line above the current line rather than below the line. Some conjuncts also get dissociated and show sthe constituent Unicode character instead of the conjuncts. I am using Windows 8 and Firefox (ver 21). I tried using the built-in IME as well as Baraa IME. in both cases I could not use the VE for typing in Kannada.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-qpuuryo2o37amdlkb5gk', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377202358, 'spacePHID': None, 'dateCreated': 1372403160, 'dateModified': 1417048672, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50346', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After setting a style (heading, paragraph, etc.) the cursor disappears', 'description': {'raw': 'As Rob spotted, we should (re-)place the cursor in the block.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372706749, 'spacePHID': None, 'dateCreated': 1372384440, 'dateModified': 1417573149, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50338', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Category leaks out of transclusion when round-tripped through VE', 'description': {'raw': \"Example diff:\\n\\nhttps://en.wikipedia.org/w/index.php?title=FC_Dila_Gori&curid=6581323&diff=561887535&oldid=561367008\\n\\nWorks in Parsoid:\\n\\necho '{{commons category}}' | node parse --wt2wt\\n{{commons category}}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50120\"}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373500548, 'spacePHID': None, 'dateCreated': 1372375380, 'dateModified': 1417573135, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50332', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Save dialog is obscured by toolbar if it's floating (the user has scrolled down)\", 'description': {'raw': 'Screenshot\\n\\nScreenshot - FireFox 21.0, Mac OS X 10.6.8\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11044}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372446220, 'spacePHID': None, 'dateCreated': 1372368720, 'dateModified': 1417573152, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50324', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a character insertion tool', 'description': {'raw': \"The VisualEditor doesn't currently have a mechanism for inserting special characters - while a lot of them are unnecessary (`~~~~` for example), things like en and emdashes can be quite important for content.\\n\\n**See Also**: {T13130}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386312920, 'spacePHID': None, 'dateCreated': 1372349160, 'dateModified': 1482692602, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50296', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace at the beginning of a line before an image inserts the succeeding text as a thumbnail caption', 'description': {'raw': 'Screenshot\\n\\nSee the screenshot; before and after the backspace, respectively.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51624\\n\\n**Attached**: {F11902}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384944160, 'spacePHID': None, 'dateCreated': 1372341120, 'dateModified': 1417572815, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50286', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template/Image node shields should not not appear on top of the toolbar', 'description': {'raw': 'Screenshot\\n\\nSee screenshot. The template inspector overlaps not only the document (that would be good - see 50241) - but the toolbar.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11898}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375298856, 'spacePHID': None, 'dateCreated': 1372339980, 'dateModified': 1417572953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50285', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Disable veaction=edit on translation pages, which are not editable directly', 'description': {'raw': 'Not sure if this should be filed under VisualEditor or Translate.\\n\\nWhen clicking the \"edit source\" button on a translation or a page that uses the Translate extension, it isn\\'t possible to edit the wikitext directly; instead, the user is told to use the Translate extension to change the content.\\n\\nWhen clicking the \"edit\" button on a translation of a page that uses the Translate extension, it\\'s possible to edit the text with VisualEditor. At first, I thought this was a feature, and that changes would be propagated to the Translate extension, until I tried to save the page and got the following error:\\n\\nError saving data to server: Unsuccessful request: Unknown error: \"tpt-target-page\".\\n\\nIf VisualEditor can\\'t be used to edit those pages, it probably shouldn\\'t lead users to believe it can :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48891\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61218'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395268154, 'spacePHID': None, 'dateCreated': 1372338540, 'dateModified': 1443276398, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50284', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE eats away the end of </ref>}} templates', 'description': {'raw': 'It has happened to me several times that after a simple edition VisualEditor or Parsoid breaks the \"</ref>}}\" at the end of a reference template. I still don\\'t know which is the pattern, but at least this time I realized it:\\n\\nhttp://ca.wikipedia.org/w/index.php?title=El_Chornaler&diff=11962426&oldid=11962407\\n\\nOther times a second editor had to come after me fixing the broken template. In the preview before saving everything looks fine.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375941682, 'spacePHID': None, 'dateCreated': 1372313340, 'dateModified': 1417572949, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50271', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'extension Campaigns (and some others?) not current', 'description': {'raw': 'http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version shows extension Campaigns not updated since 12 June, but should be current as of https://gerrit.wikimedia.org/r/#/c/69841/ at least.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372349281, 'spacePHID': None, 'dateCreated': 1372283340, 'dateModified': 1372415871, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50261', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't remove heading without header markup leaking to the rest of the page if it is the first element of the page\", 'description': {'raw': 'if an article starts with \\n==Foo==\\nBar Baz Fizz Buzz\\n\\nIt is impossible to remove ==Foo== without having the paragraph take on the h2 markup\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-n27daagbl3wqf3ghr4nk', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380876577, 'spacePHID': None, 'dateCreated': 1372276980, 'dateModified': 1417572826, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50254', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Yet another dirty-DOM on basic templates', 'description': {'raw': \"Link shows a diff made post-deploy doing (what happened to be white-space only) normalisation in two templates (that weren't touched). :-(\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/w/index.php?title=Pgeezy&curid=38061582&diff=561709972&oldid=561568473\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373518136, 'spacePHID': None, 'dateCreated': 1372274040, 'dateModified': 1417573096, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50253', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: migrate all jobs from master to slaves', 'description': {'raw': \"I want to get rid of jobs on the master instance and have them all on slaves.  Master is currently gallium.wikimedia.org which also have a slave installed on it and named 'gallium'.\\n\\nThis is a tracking bug.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373287838, 'spacePHID': None, 'dateCreated': 1372254540, 'dateModified': 1471123914, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50228', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add \"role\" attributes to UI elements where appropriate', 'description': {'raw': 'e.g. \"menuitem\" for options in our select widgets.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406079764, 'spacePHID': None, 'dateCreated': 1372205340, 'dateModified': 1443278247, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50203', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Guided tours cannot distinguish between read and edit modes with VisualEditor', 'description': {'raw': '**Author:** `swalling`\\n\\n**Description:**\\nThis tour step should only be shown in read mode.\\n\\nWhen starting the guided tour via the \"Show help\" help button with GettingStarted, guided tours thinks I am in read mode and displays broken steps, rather than skipping to the appropriate editing steps.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11708}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374192392, 'spacePHID': None, 'dateCreated': 1372184520, 'dateModified': 1394294815, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50186', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor doesn't work in be-x-old.wikipedia.org (parsoidserver-http-bad-status: 404)\", 'description': {'raw': '**Author:** `p.selitskas`\\n\\n**Description:**\\nDash-to-underscore conversion is frucked up yet again?\\n\\nWhen \"Edit\" is clicked, an API request is issued with params:\\naction:visualeditor\\npaction:parse\\npage:Новая_зямля\\noldid:1630719\\ntoken:[screened]\\nformat:json\\n\\nResponse: {\"servedby\":\"mw1141\",\"error\":{\"code\":\"parsoidserver-http-bad-status\",\"info\":\"404\"}}\\n\\nVE works at be.wikipedia.org, but it doesn\\'t work at be-x-old.wikipedia.org, bat-smg.wikipedia.org, and maybe other sites with dash in the site ID.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372215518, 'spacePHID': None, 'dateCreated': 1372164300, 'dateModified': 1372287816, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50173', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Attempting to de-bold a selection causes text to become \"extra-bold\"', 'description': {'raw': '1. Edit [[mw:VisualEditor:Sfioj]] in VE\\n2. Make a selection such as\\n\\n     These [words are] very bold\\nor \\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 21. \\n\\nI should mention that in my case, the font is Arial, which has an extra bold \"Arial-Black\" variant.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372190547, 'spacePHID': None, 'dateCreated': 1372162080, 'dateModified': 1417572815, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50170', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Groups of images are alienated under certain circumstances', 'description': {'raw': \"Groups of consecutive images are alienated under certain circumstances. \\n\\nIt might have something to do with the wikilinks in the image caption, however I really just have to throw you some testcases:\\n\\n---\\n(1) Works fine:\\nhttp://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493135&veaction=edit\\n\\n(2) Similar, but doesn't work:\\nhttp://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493351&veaction=edit\\n\\n(3) All three groups uneditable, even the group that is identical to (1) above:\\nhttp://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493252&veaction=edit\\n\\n(4) One group fine, the other alienated:\\nhttp://en.wikipedia.org/w/index.php?title=User:This,_that_and_the_other/sandbox/VE2&oldid=561493194&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372298506, 'spacePHID': None, 'dateCreated': 1372155360, 'dateModified': 1424894570, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50165', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: VE won't let user save after editing a reference\", 'description': {'raw': 'http://it.wikipedia.org/wiki/Utente:Syrio/Bozzoli, we tried changing the author\\'s name in ref.6 to \"abbé Paul Guérin\". VE allows editing it, but after clicking twice on Apply Changes, the former name is still displayed and the page can not be saved as the button does not work. (Also, it does not allow us to re-try immediately or to edit other references, you need to reload the page for that). So I did a dummy edit to plain text, and I was allowed to save then, but the result http://it.wikipedia.org/w/index.php?title=Utente%3ASyrio%2FBozzoli&diff=59659908&oldid=59651683 has nothing to do with poor abbé Guérin.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373417844, 'spacePHID': None, 'dateCreated': 1372150800, 'dateModified': 1417573138, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50161', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image insertion dialog shows thumbnails twice in non-English context (possibly due to repeated results under File: and Datei:?)', 'description': {'raw': 'Screenshot\\n\\nImage dialog shows thumbnails twice, see screenshots.\\n\\nMaybe 1 from local wiki and 1 from Commons, which are most of the times identical?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11660}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373763691, 'spacePHID': None, 'dateCreated': 1372146180, 'dateModified': 1417573093, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50158', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing leads to some characters (of wikitext) cut off in later section', 'description': {'raw': '**Author:** `brassratgirl`\\n\\n**Description:**\\nSee this diff: \\nhttps://en.wikipedia.org/w/index.php?title=Uganda&diff=561452947&oldid=560332103\\n\\nadding a sentence to the lede section saved properly, but also had unwanted behavior of cutting off the first letter of the first word of a random paragraph in a later section (removed \\'l\\' from \"Lake Kyoga\" under \\'geography\\'). \\n\\nFirefox 21.0 on Ubuntu 12.04.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373056082, 'spacePHID': None, 'dateCreated': 1372128420, 'dateModified': 1417573144, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50149', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Indentation toolbar buttons should not be enabled by default', 'description': {'raw': \"They're currently enabled on page load. Even when dismissing the notice and clicking around in the first paragraph it stays.\\n\\nIt finally disables itself after a node change (e.g. click the second paragraph and then back).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=44083\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372381096, 'spacePHID': None, 'dateCreated': 1372115880, 'dateModified': 1417573154, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50141', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Doing anything in a slug after an internal node throws an error', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372113370, 'spacePHID': None, 'dateCreated': 1372109460, 'dateModified': 1417573160, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50132', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: HTML comment not removed from user pasting (? from external source)', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Richard_Ned_Lebow&diff=561410032&oldid=545013166\\n\\nPerhaps unrelated to VisualEditor?\\n\\n<!-- /* Font Definitions */@font-face\\t{font-family:\"Courier New\";\\tpanose-1:2 7 3 9 2 2 5 2 4 4;\\tmso-font-charset:0;\\tmso-generic-font-family:auto;\\tmso-font-pitch:variable;\\tmso-font-signature:-536859905 -1073711037 9 0 511 0;}@font-face\\t{font-family:Times;\\tpanose-1:2 0 5 0 0 0 0 0 0 0;\\tmso-font-charset:0;\\tmso-generic-font-family:auto;\\tmso-font-pitch:variable;\\tmso-font-signature:3 0 0 0 1 0;}@font-face\\t{font-family:Wingdings;\\tpanose-1:5 0 0 0 0 0 0 0 0 0;\\tmso-font-charset:2;\\tmso-generic-font-family:auto;\\tmso-font-pitch:variable;\\tmso-font-signature:0 268435456 0 0 -2147483648 0;}@font-face\\t{font-family:\"ＭＳ 明朝\";\\tmso-font-charset:78;\\tmso-generic-font-family:auto;\\tmso-font-pitch:variable;\\tmso-font-signature:-536870145 1791491579 18 0 131231 0;}@font-face\\t{font-family:\"Cambria Math\";\\tpanose-1:2 4 5 3 5 4 6 3 2 4;\\tmso-font-charset:0;\\tmso-generic-font-family:auto;\\tmso-font-pitch:variable;\\tmso-font-signature:-536870145 1107305727 0 0 415 0;} /* Style Definitions */p.MsoNormal, li.MsoNormal, div.MsoNormal\\t{mso-style-unhide:no;\\tmso-style-qformat:yes;\\tmso-style-parent:\"\";\\tmargin:0in;\\tmargin-bottom:.0001pt;\\tmso-pagination:widow-orphan;\\tfont-size:12.0pt;\\tfont-family:\"Times New Roman\";\\tmso-fareast-font-family:\"ＭＳ 明朝\";\\tmso-fareast-theme-font:minor-fareast;\\tmso-bidi-font-family:\"Times New Roman\";\\tmso-bidi-theme-font:minor-bidi;}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph\\t{mso-style-priority:34;\\tmso-style-unhide:no;\\tmso-style-qformat:yes;\\tmargin-top:0in;\\tmargin-right:0in;\\tmargin-bottom:0in;\\tmargin-left:.5in;\\tmargin-bottom:.0001pt;\\tmso-add-space:auto;\\tmso-pagination:widow-orphan;\\tfont-size:12.0pt;\\tfont-family:\"Times New Roman\";\\tmso-fareast-font-family:\"ＭＳ 明朝\";\\tmso-fareast-theme-font:minor-fareast;\\tmso-bidi-font-family:\"Times New Roman\";\\tmso-bidi-theme-font:minor-bidi;}p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst\\t{mso-style-priority:34;\\tmso-style-unhide:no;\\tmso-style-qformat:yes;\\tmso-style-type:export-only;\\tmargin-top:0in;\\tmargin-right:0in;\\tmargin-bottom:0in;\\tmargin-left:.5in;\\tmargin-bottom:.0001pt;\\tmso-add-space:auto;\\tmso-pagination:widow-orphan;\\tfont-size:12.0pt;\\tfont-family:\"Times New Roman\";\\tmso-fareast-font-family:\"ＭＳ 明朝\";\\tmso-fareast-theme-font:minor-fareast;\\tmso-bidi-font-family:\"Times New Roman\";\\tmso-bidi-theme-font:minor-bidi;}p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle\\t{mso-style-priority:34;\\tmso-style-unhide:no;\\tmso-style-qformat:yes;\\tmso-style-type:export-only;\\tmargin-top:0in;\\tmargin-right:0in;\\tmargin-bottom:0in;\\tmargin-left:.5in;\\tmargin-bottom:.0001pt;\\tmso-add-space:auto;\\tmso-pagination:widow-orphan;\\tfont-size:12.0pt;\\tfont-family:\"Times New Roman\";\\tmso-fareast-font-family:\"ＭＳ 明朝\";\\tmso-fareast-theme-font:minor-fareast;\\tmso-bidi-font-family:\"Times New Roman\";\\tmso-bidi-theme-font:minor-bidi;}p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast\\t{mso-style-priority:34;\\tmso-style-unhide:no;\\tmso-style-qformat:yes;\\tmso-style-type:export-only;\\tmargin-top:0in;\\tmargin-right:0in;\\tmargin-bottom:0in;\\tmargin-left:.5in;\\tmargin-bottom:.0001pt;\\tmso-add-space:auto;\\tmso-pagination:widow-orphan;\\tfont-size:12.0pt;\\tfont-family:\"Times New Roman\";\\tmso-fareast-font-family:\"ＭＳ 明朝\";\\tmso-fareast-theme-font:minor-fareast;\\tmso-bidi-font-family:\"Times New Roman\";\\tmso-bidi-theme-font:minor-bidi;}.MsoChpDefault\\t{mso-style-type:export-only;\\tmso-default-props:yes;\\tmso-fareast-font-family:\"ＭＳ 明朝\";\\tmso-fareast-theme-font:minor-fareast;\\tmso-bidi-font-family:\"Times New Roman\";\\tmso-bidi-theme-font:minor-bidi;}@page WordSection1\\t{size:8.5in 11.0in;\\tmargin:1.0in 1.25in 1.0in 1.25in;\\tmso-header-margin:.5in;\\tmso-footer-margin:.5in;\\tmso-paper-source:0;}div.WordSection1\\t{page:WordSection1;} /* List Definitions */@list l0\\t{mso-list-id:85738127;\\tmso-list-type:hybrid;\\tmso-list-template-ids:1894403420 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}@list l0:level1\\t{mso-level-number-format:bullet;\\tmso-level-text:\\uf0b7;\\tmso-level-tab-stop:none;\\tmso-level-number-position:left;\\ttext-indent:-.25in;\\tfont-family:Symbol;}@list l0:level2\\t{mso-level-number-format:bullet;\\tmso-level-text:o;\\tmso-level-tab-stop:none;\\tmso-level-number-position:left;\\ttext-indent:-.25in;\\tfont-family:\"Courier New\";\\tmso-bidi-font-family:\"Times New Roman\";}@list l0:level3\\t{mso-level-number-format:bullet;\\tmso-level-text:\\uf0a7;\\tmso-level-tab-stop:none;\\tmso-level-number-position:left;\\ttext-indent:-.25in;\\tfont-family:Wingdings;}@list l0:level4\\t{mso-level-number-format:bullet;\\tmso-level-text:\\uf0b7;\\tmso-level-tab-stop:none;\\tmso-level-number-position:left;\\ttext-indent:-.25in;\\tfont-family:Symbol;}@list l0:level5\\t{mso-level-number-format:bullet;\\tmso-level-text:o;\\tmso-level-tab-stop:none;\\tmso-level-number-position:left;\\ttext-indent:-.25in;\\tfont-family:\"Courier New\";\\tmso-bidi-font-family:\"Times New Roman\";}@list l0:level6\\t{mso-level-number-format:bullet;\\tmso-level-text:\\uf0a7;\\tmso-level-tab-stop:none;\\tmso-level-number-position:left;\\ttext-indent:-.25in;\\tfont-family:Wingdings;}@list l0:level7\\t{mso-level-number-format:bullet;\\tmso-level-text:\\uf0b7;\\tmso-level-tab-stop:none;\\tmso-level-number-position:left;\\ttext-indent:-.25in;\\tfont-family:Symbol;}@list l0:level8\\t{mso-level-number-format:bullet;\\tmso-level-text:o;\\tmso-level-tab-stop:none;\\tmso-level-number-position:left;\\ttext-indent:-.25in;\\tfont-family:\"Courier New\";\\tmso-bidi-font-family:\"Times New Roman\";}@list l0:level9\\t{mso-level-number-format:bullet;\\tmso-level-text:\\uf0a7;\\tmso-level-tab-stop:none;\\tmso-level-number-position:left;\\ttext-indent:-.25in;\\tfont-family:Wingdings;}ol\\t{margin-bottom:0in;}ul\\t{margin-bottom:0in;}-->\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385505602, 'spacePHID': None, 'dateCreated': 1372105380, 'dateModified': 1417570402, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50128', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Applying link annotation to a selection containing link and image kills the image, inserts a <nowiki /> for the link's text\", 'description': {'raw': '* Go here http://en.wikipedia.org/w/index.php?title=User:ESanders_(WMF)/Sandbox&oldid=561403721&veaction=edit\\n* Select from the end of the image to inside the link\\n* Observe you now have a link inspector positioned over the image.\\nBonus:\\n* Use the inspector to edit the link\\n* Review your changes, the image has been killed, and the link as gone a bit crazy\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377195359, 'spacePHID': None, 'dateCreated': 1372102800, 'dateModified': 1417572943, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50127', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Serializer inserts odd whitespace eventhough nodes are no longer in DOM', 'description': {'raw': 'Screenshot of the problem in the serialization\\n\\nI think this is caused by Parsoid trying to preserver/re-add whitespace when round-tripping.\\n\\nSteps to reproduce issue:\\n* Create a page like the default MediaWiki main page:\\n\\n<<<MW\\n\\'\\'\\'MediaWiki has been successfully installed.\\'\\'\\'\\n\\nConsult the [//meta.wikimedia.org/wiki/Help:Contents User\\'s Guide] for information on using the wiki sandbox software. 12\\n\\n== Getting started ==\\n* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]\\n* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]\\n* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]\\n* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]\\nMW;\\n\\n* Edit it with VisualEditor\\n* Put the cursor before \"MediaWiki release mailing list\" and select back until before the first character of the heading \"Getting started\".\\n* Press backspace. You\\'re now left with 2 of 4 items in the list and an empty heading.\\n* Again, out the cursor before \"MediaWiki release mailing list\" and delete until you\\'re behind \"software. 12\". You\\'re now left with \"MediaWiki release mailing list\" in the paragraph and a list with 1 item.\\n* Save page -> Review changes (Screenshot attached)\\n\\nIt inserts a lot of new lines.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11588}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372370405, 'spacePHID': None, 'dateCreated': 1372101840, 'dateModified': 1372370405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50123', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: First character after a </pre> is lost on round-trip', 'description': {'raw': \"I edited a large page on meta (1.22wmf7) in VE. All seemed fine but review showed VE had removed the first character following several closing </pre> tags. It also removed a few characters within a <source> tag.\\n\\nHere's the diff showing the removal, it's self-explanatory.  <https://www.mediawiki.org/w/index.php?title=Extension%3AEventLogging%2FGuide&diff=716359&oldid=704840>.  I will restore the characters by hand.\\nI'm using Firefox 21.0 on Kubuntu 13.04.\\n\\nI tried editing the same document again and this time VE removed more characters from the source tag, added a space after a <pre>. Hmm. I'm setting to critical as it's recoverable data loss, but maybe it's intermittent.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372355490, 'spacePHID': None, 'dateCreated': 1372098360, 'dateModified': 1417573151, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50118', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: IME shift+ function for adding diacritical marks in Arabic broken', 'description': {'raw': 'From http://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Problem_with_using_shift%2B\\n\\n\"Hi. I have been using the visual editor for a while on ar Wikipedia, it is very nice and smooth for fast edits. However, I am facing a very strange problem when I need to add some Arabic diacritics known as tashkil; when I press shift+diacritic button (like x, e, or z) the letter I pressed starts to repeat itself endlessly, and it can only be stopped by refreshing the page and wasting the work I have did. Any thoughts?\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50631'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377202348, 'spacePHID': None, 'dateCreated': 1372087860, 'dateModified': 1437511418, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50105', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: HTML comments being removed inside templates', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Jason_Bateman&curid=685922&diff=561337061&oldid=559944750\\n\\nhttps://en.wikipedia.org/w/index.php?title=David_Stewart_(photographer)&curid=24365669&diff=561336970&oldid=529664374\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373851510, 'spacePHID': None, 'dateCreated': 1372086120, 'dateModified': 1417573092, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50102', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Templates' phantoms can overlap the toolbar, hindering saving/etc.\", 'description': {'raw': \"Screenshot\\n\\nSee screenshot; this is still happening as of [timestamp of this bug]. The VE interprets a click on 'save page' to be an attempt to interact with the infobox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49059\\n\\n**Attached**: {F11515}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372205712, 'spacePHID': None, 'dateCreated': 1372081680, 'dateModified': 1417573159, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50096', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reflist sometimes not fully being populated', 'description': {'raw': 'Compare the references section of https://en.wikipedia.org/wiki/A_Slight_at_the_Opera in read and edit mode.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52371'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375381775, 'spacePHID': None, 'dateCreated': 1372080180, 'dateModified': 1417572952, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50094', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Lag when selecting complex templates (especially in big pages)', 'description': {'raw': '(from bug 49922 comment 1)\\n\\nVE is slow at selecting templates and transclusions in big pages.\\n\\nFor example: [[World War II]]:\\n\\n - attempt to select infobox by clicking on it: takes ~3 seconds in \\n   Firefox 21 and Chrome 27, with no visual indication that anything\\n   is happening during the wait\\n\\n - attempt to select the reflist by clicking on it: just hangs in Firefox\\n   and Chrome, never actually seems to happen\\n\\nThis either needs to be sped up, or fail more gracefully.\\n\\nIn IE10, this is not such a problem \\\\o/ - lag is actually less, and the reflist can be selected (takes about 22 seconds).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406824618, 'spacePHID': None, 'dateCreated': 1372048320, 'dateModified': 1443278247, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50084', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When a page contains two identical templates right next to each other, one is removed', 'description': {'raw': 'See the unexpected changes at https://en.wikipedia.org/w/index.php?title=Thomson_Airways&diff=561270595&oldid=561268927\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372089793, 'spacePHID': None, 'dateCreated': 1372037280, 'dateModified': 1417573160, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50079', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Notice popup appears when there are, in fact, no notices because of enwiki's hack\", 'description': {'raw': 'Screenshot\\n\\nSee screenshot. What am I meant to be paying attention to?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11451}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373037205, 'spacePHID': None, 'dateCreated': 1372035900, 'dateModified': 1417573145, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50077', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deletion into a DL from a block slug breaks', 'description': {'raw': 'Click after the line \"Saptaitey Chiranjeevinaha[citation needed]\" on https://en.wikipedia.org/wiki/Chiranjivi and BANG! And the text is gone.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374186072, 'spacePHID': None, 'dateCreated': 1372035720, 'dateModified': 1417573084, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50076', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: HTML comments being removed inside references', 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=Beautiful_%28Mariah_Carey_song%29&diff=561243294&oldid=561242578\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372210324, 'spacePHID': None, 'dateCreated': 1372034760, 'dateModified': 1372210324, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50071', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Nowiki-ing inside templates' parameters\", 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=Riddler&diff=561149660&oldid=561096940\\n\\nThe user reports they were nowhere near the infobox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50147\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50129'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372218685, 'spacePHID': None, 'dateCreated': 1372034400, 'dateModified': 1372218685, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50070', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid: selser drops last three apostrophes in '''''foo'''''\", 'description': {'raw': \"See https://en.wikipedia.org/w/index.php?title=Port_of_Hull&diff=561131671&oldid=561056099 - an attempt to enter a dash led to bolding vanishing. Not sure what's going on there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372290747, 'spacePHID': None, 'dateCreated': 1372033860, 'dateModified': 1372291023, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50068', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Preserve ordering inside data-mw elements', 'description': {'raw': \"Currently we don't and cause major headaches for Parsoid.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372039643, 'spacePHID': None, 'dateCreated': 1372028700, 'dateModified': 1417573087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50066', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Metadata is not annotated', 'description': {'raw': \"Which causes this dirty diff:\\n\\n'''Foo<!--bar-->baz'''\\n\\n=>\\n\\n'''Foo'''<!--bar-->'''baz'''\\n\\nOf course annotating un-deletable metadata means if 'Foobaz' is erased you will be left with:\\n\\n'''<!--bar-->'''\\n\\nbut that's less of a problem, and could be fixed by Parsoid.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372038604, 'spacePHID': None, 'dateCreated': 1372009920, 'dateModified': 1417573162, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50060', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save dialog is far too small in Monobook, making edit summaries hard to write', 'description': {'raw': 'Screenshot\\n\\nSee the screenshot; it appears in Monobook on enwiki and mediawiki.org as of the latest release. Kiiinda a problem.\\n\\n(the other interstitials there - review your changes/save page - are also shrunk).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11418}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374793868, 'spacePHID': None, 'dateCreated': 1372005660, 'dateModified': 1417573071, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50058', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dialog/flyout buttons cannot be activated with Tab key', 'description': {'raw': 'You can\\'t tab from the edit summary box to the \"Save page\" button, or the reference inspector to the \"Apply changes\" button, etc.\\n\\nThis is important for accessibility. Currently, there is no way to confirm the action using only the keyboard.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50897'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374880834, 'spacePHID': None, 'dateCreated': 1371984240, 'dateModified': 1575898098, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50047', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Right-click in IE10 causes deletion of the selected content', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409959799, 'spacePHID': None, 'dateCreated': 1371982260, 'dateModified': 1423674434, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50045', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion editor broken in IE10 (stack overflow)', 'description': {'raw': 'In IE10, any attempt to open the transclusion editor leads to a stack overflow. \\n\\nIn the dev console I get this:\\n\\n--- \\nSCRIPT28: Out of stack space \\nload.php, line 46 character 700 [this location is different every time]\\n\\nSCRIPT5: Access is denied.\\nload.php, line 305 character 273\\n\\nSCRIPT5: Access is denied.\\nload.php, line 305 character 273\\n\\nSCRIPT5: Access is denied.\\nload.php, line 305 character 273 \\n[... ad infinitum]\\n\\nSCRIPT2343: Stack overflow at line: 46 [different every time]\\n\\nSCRIPT5: Access is denied.\\nload.php, line 305 character 273\\n---\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409958003, 'spacePHID': None, 'dateCreated': 1371982020, 'dateModified': 1423674434, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50044', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Chromium (< 30) crashes when attempting to cut content containing <link> or <style>', 'description': {'raw': '1. Use Chrome 27 to edit [[Pancytopenia#External links]] in VE\\n2. Try to cut the {{Commons category}} template (using Ctrl+X/Cmd+X or right click/Cut)\\n\\nThe browser tab crashes.\\n\\nSeen on Windows and Mac.\\n\\nNo idea how to find any debugging info about the crash.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377632908, 'spacePHID': None, 'dateCreated': 1371979920, 'dateModified': 1583423428, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50043', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: External links are double encoded', 'description': {'raw': 'Intended edit (ve-edit + fixup):\\n\\nhttps://www.mediawiki.org/w/index.php?title=Wikimedia_technical_search&diff=715707&oldid=715705\\n\\n-  [https://github.com/search?l=&q=wgWellFormedXml+%40wikimedia Search]\\n+  [https://github.com/search?l=&q=ResourceLoader+%40wikimedia Search]\\n\\nActual edit saved by Parsoid/VisualEditor:\\n\\n\\nhttps://www.mediawiki.org/w/index.php?title=Wikimedia_technical_search&diff=715706&oldid=715705\\n\\n-  [https://github.com/search?l=&q=wgWellFormedXml+%40wikimedia Search]\\n+  [https://github.com/search?l=&q=ResourceLoader+%2540wikimedia Search]\\n\\n\\nNote how the % got encoded to %25.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372442702, 'spacePHID': None, 'dateCreated': 1371979620, 'dateModified': 1372442702, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50042', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Search for filename with dashes on Commons does not return said file (seems to exclude string after dash)', 'description': {'raw': 'Screenshot\\n\\nI am unable to insert a media with a given file name from Commons.\\n\\nNeither\\n\\nFile:Kölnisches Stadtmuseum - 125 x gekauft - geschenkt - gestiftet-1120.jpg\\n\\nnor\\n\\nKölnisches Stadtmuseum - 125 x gekauft - geschenkt - gestiftet-1120.jpg\\n\\nis accepted (and any other file name)\\n\\nThe \"insert media\" button is still inactive, see screenhot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11348}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392141824, 'spacePHID': None, 'dateCreated': 1371909840, 'dateModified': 1392141824, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50018', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Consecutive images align incorrectly in \"edit\" mode and cannot be modified', 'description': {'raw': 'See, for example, https://en.wikipedia.org/wiki/Kaveri_River\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371972536, 'spacePHID': None, 'dateCreated': 1371896520, 'dateModified': 1371972536, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50013', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Thumbnailed images without descriptions get pipes added on edit', 'description': {'raw': 'Compare https://en.wikipedia.org/w/index.php?title=User:Edgepedia/sandbox3&diff=prev&oldid=560957268 to https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2Fsandbox3&diff=560957359&oldid=560957268\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372124850, 'spacePHID': None, 'dateCreated': 1371895500, 'dateModified': 1417573159, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images not displayed in latest VE deployment', 'description': {'raw': 'I hope this is a false alarm... but it seems to be real.\\n\\nCompare [[Locomotive]] (images visible - en is currently on 1.22wmf7) with [[testwiki:VisualEditor:Locomotive]] (no images - test is on 1.22wmf8).\\n\\nSeen on Firefox latest and Chrome latest.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372003922, 'spacePHID': None, 'dateCreated': 1371887280, 'dateModified': 1372003922, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50008', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor by default for phase 2 Wikipedias (selected from the \"top 10\"-ish)', 'description': {'raw': \"Currently scheduled for w/c 15 July. It's anticipated that this will not be possible for some wikis due to failings in VisualEditor and/or Parsoid; exact list to be determined closer to the time.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51792\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=33126\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=33077\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52202\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375105856, 'spacePHID': None, 'dateCreated': 1371860160, 'dateModified': 1488808087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49998', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor by default for all users of the English Wikipedia', 'description': {'raw': 'Currently scheduled for w/c 1 July.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373921229, 'spacePHID': None, 'dateCreated': 1371860100, 'dateModified': 1373921229, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49997', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor experimental mode on test* wikis as well as MW.org and Beta Labs', 'description': {'raw': 'After spending some time with VE in our various test environments, it would be convenient to have all features available in VE available in all of our test environments.  Right now it is possible to create citations in mediawiki.org but not in test2wiki, and VE in beta labs is not usable at all. \\n\\ntest2wiki gives us a production wiki where it is possible to make destructive or nonsense edits that are not welcome on mediawiki.org\\n\\nbeta labs gives us an environment to test possibly risky merged changes that are not yet deployed\\n\\nEnabling all of VE features in all test environments would be useful for testing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49703'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372377535, 'spacePHID': None, 'dateCreated': 1371827040, 'dateModified': 1372864721, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49963', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images: wikitext tables inside image captions are lost', 'description': {'raw': \"When editing a page which has an image with table data in its caption, the table is dropped (only its closing tab is kept). The rest of the caption is dropped as well.\\n\\nTest edit: https://hu.wikipedia.org/w/index.php?title=Vall%C3%A1s&diff=13696305&oldid=13696296\\n\\nYou don't need to interact with the image in any way for this to happen, just edit the page, change anything and save.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://hu.wikipedia.org/wiki/Vall%C3%A1s?oldid=13696307\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61064\"}, 'authorPHID': 'PHID-USER-a6p24cvyblhfzc7we7nc', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389680196, 'spacePHID': None, 'dateCreated': 1371799080, 'dateModified': 1392850811, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49942', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Part of link inspector interface sometimes remains (top-left of screen) after closing', 'description': {'raw': '1. In VE, highlight some text and open the link inspector\\n2. Type some characters into the textbox, but quickly click out of the link inspector before the autocomplete dropdown appears\\n\\nThe dropdown appears in the top-left corner of the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373413695, 'spacePHID': None, 'dateCreated': 1371798960, 'dateModified': 1417573088, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49941', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Links not doing pre-annotations ever (rather than just not spanning on ' ') is confusing for users\", 'description': {'raw': '1. Go to [[mw:VisualEditor:TTO]] and edit in VE\\n2. Double-click on a link in order to select it, or drag-select the whole link\\n3. Type a new link text\\n\\nOnly the first character you type remains linked, instead of the whole text you type.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374771607, 'spacePHID': None, 'dateCreated': 1371793260, 'dateModified': 1417573074, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49931', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking outside the \"Describe what you changed\" box locks it', 'description': {'raw': 'Steps to replicate:\\n\\n(1)Click \"Edit\" and make some change\\n(2)Click \"Save page\". The cursor is now blinking in the \"Describe what you changed\" box.\\n(3)Click on another dialogue box, such as the WP search box. The cursor now blinks there.\\n(4) Click back into \"Describe what you changed\". Bupkis.\\n\\nChrome 27.0.1453.116, Firefox 21.0, Windows 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372006698, 'spacePHID': None, 'dateCreated': 1371789780, 'dateModified': 1417573201, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49927', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Floated templates rendering oddly and overlapping text', 'description': {'raw': 'See screenshot, which is of https://en.wikipedia.org/wiki/Craig_Short - Firefox 21.0, Windows 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372463194, 'spacePHID': None, 'dateCreated': 1371789480, 'dateModified': 1417572816, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49925', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'imageinfo API returns incorrect data', 'description': {'raw': 'In this call http://en.wikipedia.org/w/api.php?action=query&prop=imageinfo&titles=File%3APowderfinger-My_Happiness-23s.ogg&iiprop=size%7Curl&iiurlwidth=200 it returns thumbwidth=\"1913\" thumbheight=\"-1\" as a size of an thumb, which is completly wrong.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'ownerPHID': 'PHID-USER-uqcn2l4ng4murmyfnvyp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372722142, 'spacePHID': None, 'dateCreated': 1371774060, 'dateModified': 1602870083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49921', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Miscellaneous <span> tags added', 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=User%3AEdgepedia%2FVE%2FMet&diff=560772671&oldid=560563847 for example; I have no idea why (problem with the template itself?)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373056128, 'spacePHID': None, 'dateCreated': 1371748980, 'dateModified': 1417573143, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49892', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: <span> annotations next to each other aren't necessarily the same\", 'description': {'raw': 'Two users have reported on this. \\n\\nSee:\\nhttp://en.wikipedia.org/w/index.php?title=User:AussieLegend/Vandals_etc&diff=prev&oldid=560719781\\n\\nAnd:\\nhttp://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Font_colors_in_signatures_changed\\n\\nI realize that this is probably tied into other behavior, but I lack code-fu to determine what. :)\\n\\nMaggie\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=42803'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373852393, 'spacePHID': None, 'dateCreated': 1371732540, 'dateModified': 1417573092, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49873', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Blank transclusion block doesn't get converted into blankness\", 'description': {'raw': 'Click \"add template\", then \"apply changes\" without adding a template (or add one, then remove it.\\n\\nExpected wikitext: none\\n\\nActual wikitext: <span property=\"mw:PageProp/noindex\" data-mw=\"{&quot;parts&quot;:[]}\"></span>\\n\\nWe\\'re clearly putting in a placeholder that we don\\'t delete if the block is empty; because we don\\'t display content blocks that don\\'t render in read, you can\\'t see these, which sucks and lets users do The Wrong Thing(tm).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371744867, 'spacePHID': None, 'dateCreated': 1371699420, 'dateModified': 1417573207, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49855', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Re-rendered transclusion of blocks comes back as wikitext, not HTML (eww)', 'description': {'raw': \"Something's gone wrong with our PHP parser re-render call; on re-render of block templates only, you get {{template call|param}} rather than nice lovely HTML. Presumably something to do with our hack yesterday? Plzfixkthxbai.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373555274, 'spacePHID': None, 'dateCreated': 1371699120, 'dateModified': 1417573095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49854', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Phantoms are not relative to the surface content', 'description': {'raw': 'Reproduce:\\n\\n1. Open page with a protected node\\n2. Click edit (visual editor)\\n3. Quickly mouse over the protected node (while VE loads)\\n4. See that the editor has slid the content down but the phantom is rendered under the mouse\\n\\nPerhaps the local overlay should be a peer of the documentNode.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372210873, 'spacePHID': None, 'dateCreated': 1371696840, 'dateModified': 1417573159, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49853', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images: Image insertion uses both the English and the localised syntax for \"right\"', 'description': {'raw': 'Reported initially in bug 49596:\\n\\nptwiki (\"direita,right\"): https://pt.wikipedia.org/w/index.php?&diff=36119075\\n\\nplwiki (\"prawo,right\"): https://pl.wikipedia.org/w/index.php?diff=36790309\\n\\nThis feels like a Parsoid issue (VisualEditor doesn\\'t know about localisations of these terms :-)) but Inez can tell us more details.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372192576, 'spacePHID': None, 'dateCreated': 1371690720, 'dateModified': 1372934016, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49849', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Weekly Bugzilla Report: \"Created reports per product\" lists random products, not those with highest numbers', 'description': {'raw': 'Whenever you think that you\\'ve fixed that damn script, you suddenly realize there\\'s something else that\\'s still wrong.\\n\\n\\nTesting the fix for bug 49758, looking at its results:\\n\\nCreated reports per component:\\nVisualEditor           General                       33\\nMediaWiki extensions   UniversalLanguageSelector     27\\nVisualEditor           Editing Tools                 25\\nVisualEditor           MediaWiki integration         12\\nWikimedia              Bugzilla                      11\\n\\nCreated reports per product:\\nMediaWiki                     43 \\nWikimedia                     45 \\nMediaWiki extensions          104\\nSecurity                      3  \\nTools                         5  \\n\\nit is clear that the \"product\" list does not list those products with the **highest** number of new tickets in the last week.\\n\\nThis can be also seen on\\nhttps://bugzilla.wikimedia.org/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfield=[Bug+creation]&chfieldvalue=&chfieldfrom=-7d&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap\\n\\nwhich right now lists these top 5 products:\\n\\nMediaWiki extensions  104\\nVisualEditor          95\\nMediaWiki             48\\nWikimedia             47\\nParsoid               23\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372340940, 'spacePHID': None, 'dateCreated': 1371682740, 'dateModified': 1372340940, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49845', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: TemplateSpecModel should expand aliases', 'description': {'raw': 'TemplateSpecModel currently doesn\\'t expand aliases, so if it knows something as \"foo\" with an alias of \"1\" and the dialog asks about \"1\", it returns nothing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372038971, 'spacePHID': None, 'dateCreated': 1371671820, 'dateModified': 1417572933, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49838', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Blank transclusion block doesn't get converted into blankness\", 'description': {'raw': 'Using Chrome27.0.1453.110 m\\nReplicated on Firefox 21.0\\n\\nAttempting to remove a template using the puzzle piece and \"remove\" function seems to succeed but leaves behind the following code:\\n<span data-mw=\"{&quot;parts&quot;:[]}\" class=\"metadata plainlinks ambox ambox-style ambox-Orphan\" style></span>\\n\\nSee:\\nhttp://en.wikipedia.org/w/index.php?title=Cocking-cloth&diff=560630933&oldid=324780702\\n\\nand \\nhttp://en.wikipedia.org/w/index.php?title=Cocking-cloth&diff=560631541&oldid=560631467\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371748525, 'spacePHID': None, 'dateCreated': 1371661680, 'dateModified': 1417573203, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49831', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: When user types in '[[' in the page or another DOM input widget, pop up a reminder that they're using VisualEditor\", 'description': {'raw': \"When a user inserts [[links]] or {{templates}}, VisualEditor automatically wraps them into <nowiki> tags. Experienced contributors who are very used to using this syntax sometimes add it inadvertently.\\n\\nIt would be a nice touch to show an unobtrusive warning to remind users that they need to use VisualEditor's menu to insert links, templates & other wikisyntax. LiquidThreads does this well when users insert their signature manually with ~~~ into their post\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49686\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50527\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50601\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375203346, 'spacePHID': None, 'dateCreated': 1371651600, 'dateModified': 1433879735, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49820', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Top left corner of the window shows blue rectangle when selecting templates in Firefox', 'description': {'raw': \"screenshot\\n\\nWhen selecting some templates in VisualEditor, a blue rectangle appears in the top left corner of the browser's window, and disappears when the template is unselected.\\n\\nEncountered on https://en.wikipedia.org/wiki/User:Jdforrester_%28WMF%29/Sandbox?veaction=edit (see screenshot)\\n\\nFirefox 21.0 on openSUSE 12.3\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50074\\n\\n**Attached**: {F11783}\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373512100, 'spacePHID': None, 'dateCreated': 1371649560, 'dateModified': 1417573096, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49818', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image dialog shows <visualeditor-dialog-media-content-section> instead of actual message', 'description': {'raw': 'Encountered on: https://en.wikipedia.org/wiki/Westplex?veaction=edit\\nFirefox 21.0 on openSuse 12.3\\n\\nWhen opening the \"Media settings\" overlay by clicking the icon on the image, the title shows <visualeditor-dialog-media-content-section> instead of what I assume should be the actual system message.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371748706, 'spacePHID': None, 'dateCreated': 1371649140, 'dateModified': 1371748706, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49817', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing escape should close a dialog', 'description': {'raw': 'Like we do with the link inspector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372378620, 'spacePHID': None, 'dateCreated': 1371644280, 'dateModified': 1417573155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49809', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image corruption edits - garbled text inserted into image description', 'description': {'raw': 'See, for example, http://en.wikipedia.org/w/index.php?title=Audie_Murphy&diff=560382883&oldid=560374610 - the line \"ad a private-pilot license and\" (image description) is clearly being taken from the article text \"had a private-pilot license and a reported 8, 000 hours of flying time\", but I have no idea how.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372016417, 'spacePHID': None, 'dateCreated': 1371640500, 'dateModified': 1417573162, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49807', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Some template dialog loading attempts fail with 'TypeError'\", 'description': {'raw': \"Steps to reproduce:\\n\\n1) Visit https://en.wikipedia.org/wiki/Deliciosamente_amoral?veaction=edit\\n\\n2) Attempt to manipulate the contents of the infobox by clicking the puzzle piece icon associated with it.\\n\\nExpected behavior:\\n\\nInfobox parameters should be editable.\\n\\nActual behavior:\\n\\nTemplate editor invocation fails with the following error on the console:\\n\\nUncaught TypeError: Cannot read property 'description' of undefined \\n\\nChrome/Ubuntu\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49493\"}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371748994, 'spacePHID': None, 'dateCreated': 1371614460, 'dateModified': 1417573207, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49797', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspector menu appears with blank entry in Firefox', 'description': {'raw': \"Example screenshot of the issue\\n\\nIn the given link, for reference 7's template; only in Firefox - works fine in Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/w/index.php?title=VisualEditor:TestReferenceContents&oldid=713075\\n\\n**Attached**: {F11716}\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372190121, 'spacePHID': None, 'dateCreated': 1371594720, 'dateModified': 1417573158, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49781', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn appears when Cmd-C over a selected inline image in Firefox', 'description': {'raw': \"https://en.wikipedia.org/wiki/List_of_highways_numbered_147?veaction=edit\\n\\nI selected an inline image in the editor (in itself strange, because it doesn't seem you can edit it). I then hit cmd-c, and the inline image was replaced by the pawn char.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371680649, 'spacePHID': None, 'dateCreated': 1371579000, 'dateModified': 1417573208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49760', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Nested identical annotations can be additive, not just identical', 'description': {'raw': \"<b><b>Foo</b></b> == <b>Foo</b> so it's not /so/ bad if VE corrects it (but it's still a bit dirty, but <small><small>Foo</small></small> != <small>Foo</small> (and the same with <big> and <sup> and …)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/w/index.php?title=User:JohnCD/draft&diff=560430675&oldid=560430611\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373503078, 'spacePHID': None, 'dateCreated': 1371574560, 'dateModified': 1417573098, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support creation/editing of references using an existing ref-name', 'description': {'raw': 'The reference editor allows me to group references, and allows me to include a ref name parameter to make them reusable, but has no way of actually calling that ref name.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372382660, 'spacePHID': None, 'dateCreated': 1371535560, 'dateModified': 1721383136, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49733', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B', 'description': {'raw': 'Screenshot\\n\\nSee associated character; italics in the reference editing interface causes a pawn to appear.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11627}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371680618, 'spacePHID': None, 'dateCreated': 1371533160, 'dateModified': 1417573206, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49732', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template inspector removing characters from header', 'description': {'raw': \"See associated screenshot; an attempt to add 'foo' to the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371657198, 'spacePHID': None, 'dateCreated': 1371532980, 'dateModified': 1417573209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49731', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Prevent headings in reference sub-editor dialogs', 'description': {'raw': '**Author:** `rachelqa99`\\n\\n**Description:**\\nMake a reference, then type text into Name content, and change format to Heading 5 or Heading 3.  When you save the file, you see the wikitext displayed for the heading format. \\n\\nSee page: https://www.mediawiki.org/wiki/User:Rachel99/testing_edit_source\\n\\nOn the bottom of the page, it looks like that.\\n\\n    ↑ ===test===\\n    ↑ =====Book reference=====\\n    ↑ ===footnote text===\\n    ↑ =====test5=====\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371845722, 'spacePHID': None, 'dateCreated': 1371500340, 'dateModified': 1417573202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49715', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor link to Parsoid broken in beta labs deployment?', 'description': {'raw': 'on beta labs only, not seen in mediawiki.org: \\n\\nOn any article e.g. http://en.wikipedia.beta.wmflabs.org/wiki/0.0924627428112147 \\n\\nClick Edit to invoke VE\\n\\nPage content is a different article.  In the case of http://en.wikipedia.beta.wmflabs.org/wiki/0.0924627428112147 I see the content for an article on \"TAT-1\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49963'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372390935, 'spacePHID': None, 'dateCreated': 1371486720, 'dateModified': 1372390935, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49703', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add FlaggedRevs \"accept pending revisions\" to save dialog', 'description': {'raw': 'Alongside the \"minor\" and \"watch\" checkboxes in the save dialog, for pages with FlaggedRevs switched on and outstanding unaccepted revisions, add a checkbox to \"accept pending revisions\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50852'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374649658, 'spacePHID': None, 'dateCreated': 1371485400, 'dateModified': 1417573075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49699', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Templates (incorrectly) expanded', 'description': {'raw': 'https://en.wikipedia.org/wiki/Template:Contradictory, on https://en.wikipedia.org/wiki/Necessity - in the VisualEditor it displays as \\ufeff[<span title=\"This text contradicts text in the article \"Necessity in English law\" (3 May 2011)\">contradictory]\\ufeff. Reproduced in Chrome 27/Safari 6.0.5 on a Mac, Firefox 21.0 on Windows 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371596252, 'spacePHID': None, 'dateCreated': 1371469920, 'dateModified': 1371596252, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49690', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid provides 200px-width default for sound files, rather than the sound icon at standard size', 'description': {'raw': 'See https://en.wikipedia.org/wiki/Hermann_M%C3%BCller_%28politician%29 for example; found in Chrome 27 on a Mac. In Safari 6.0.5 it displays differently (a large space appears, rather than a missing icon signifier) but is still broken. Not replicatable in Firefox 21.0/Windows 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://parsoid.wmflabs.org/en/Hermann%20M%C3%BCller%20(politician)'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1489187347, 'spacePHID': None, 'dateCreated': 1371469740, 'dateModified': 1489187347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49689', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: automagically convert wikitext (e.g. [[link]]) to VE-compatible elements', 'description': {'raw': \"Bug title may be a bit confusing; essentially, a user has suggested that the VE auto-convert wikimarkup entered ''into'' the VE, on save. The use case is users who keep typing [[link]], basically.\\n\\nMy feelings on this are mixed; I think it's perfectly possible that this would be useful, but it sounds like a ton of work and it's also perfectly possible that, once we go live, muscle memory will adapt and there'll be no point to this. For now, sticking it in as a potential future enhancement.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49820\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51899\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=47779\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377819704, 'spacePHID': None, 'dateCreated': 1371468300, 'dateModified': 1437770887, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49686', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Some template combinations make text not editable', 'description': {'raw': 'On Swedish Wikipedia, we have quite a few bot generated articles (some hundreds of thousands) like this one: https://sv.wikipedia.org/wiki/Macrothemis_ultima\\n\\nWhen in editing mode, somehow the first line of text cannot be edited. \\n\\nIf an article has a second line, it is possible to edit that one (but still not the first line), e.g. https://sv.wikipedia.org/wiki/Lepidosaphes_lithocarpi\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371825507, 'spacePHID': None, 'dateCreated': 1371462960, 'dateModified': 1417573204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49678', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Display a link to both VE and wikitext editor on every section header', 'description': {'raw': '[From bug 48429 comment 18]\\n\\n| It would be ideal to have section-edit links for [edit] and [edit source].\\n| ie.\\n|   Sandbox [edit]\\n| replaced with:\\n|   Sandbox [edit] [edit source]\\n| \\n| I believe this would prevent a LOT of complaints in the short term, and it\\n| would permit a lot of us to continue being active beta testers\\n| (section-editing is my most frequent type of edit), that it should be High\\n| priority, if at all possible. Thanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48429\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49621\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=47779\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56337'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372362973, 'spacePHID': None, 'dateCreated': 1371430320, 'dateModified': 1483620949, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49666', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Prevent certain kinds of structures in certain kinds of sub-editor dialogs', 'description': {'raw': 'In general, \"everything\" is allowed (text; annotations; inline and block images; headings; lists; HTML blocks; entities; transclusions; references; etc.), except for:\\n\\nImage captions\\n-> No lists\\n\\nReferences\\n-> No references (but transclusions of {{#tag:ref|text}} get around this for one level as an out ref; eww)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50459'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379657458, 'spacePHID': None, 'dateCreated': 1371422340, 'dateModified': 1417572932, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49657', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Show change tags on edit diff views', 'description': {'raw': \"From bug 49602 comment 0:\\n\\n| The VisualEditor edit tag (Tag: VisualEditor) should show on diffs, too.\\n| This will probably require a core change.  However, I'm filing it here, both\\n| so you're aware of it, and because it might need to be configurable (it might\\n| be we don't want all tags, such as AbuseFilter, etc. to show on diffs).\\n\\nThis is said request for a core change for this to be possible. :-)\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373019604, 'spacePHID': None, 'dateCreated': 1371419460, 'dateModified': 1425180374, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49656', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make some way to display display-less content (e.g. silent transclusions like {{lowercase title}})', 'description': {'raw': 'https://en.wikipedia.org/wiki/User:%C3%8F%C2%BF%C2%BD?veaction=edit\\n\\nIf a template has no output (such as <https://en.wikipedia.org/wiki/Template:Lowercase_title>), it has no visible output and becomes very easy to silently remove using VisualEditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49667'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374086311, 'spacePHID': None, 'dateCreated': 1371357660, 'dateModified': 1429898466, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49633', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Closing (as opposed to applying) a dialog with no changes undoes last item in the stack anyway', 'description': {'raw': 'https://en.wikipedia.org/wiki/Digital_Forensics_XML?veaction=edit\\n\\nI went there, I changed a header from h3 to h2 by selecting the header and using the drop-down menu. When I click \"Page settings\" and then close the dialog box without making any changes, my change to the header is inexplicably lost.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371584527, 'spacePHID': None, 'dateCreated': 1371355920, 'dateModified': 1417573209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49630', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: mw:Placeholder issue', 'description': {'raw': 'If there are 2 blank lines (line breaks) then the paragraph immediately after is uneditable (green striped overlay).\\n\\nConfirm here: http://en.wikipedia.org/w/index.php?title=User:Quiddity/sandbox&oldid=560048320\\n\\nand see thread here: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Paragraph_editing_disabled.3F.3F.3F\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371516882, 'spacePHID': None, 'dateCreated': 1371319260, 'dateModified': 1371516882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49623', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Display HTML comments to the editor (and make them editable/creatable/removable)', 'description': {'raw': 'VisualEditor should display HTML comments, which are often used as notes or warnings to other editors.  It would be nice if they were editable too.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49608\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=46440\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49806\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53659'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406161251, 'spacePHID': None, 'dateCreated': 1371261360, 'dateModified': 1443427691, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49603', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Swallowing of empty text annotations leads to dirty diffs and unexpected Parsoid normalisation', 'description': {'raw': 'VisualEditor caused this dirty diff (https://en.wikipedia.org/w/index.php?title=List_of_South_Korean_idol_groups_%282010s%29&diff=559356009&oldid=559228059) when editing a table.  Note the removal of the empty small elements, and the change to the align syntax.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371419290, 'spacePHID': None, 'dateCreated': 1371258600, 'dateModified': 1417585176, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49601', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Revive Inez's way of doing sub-surfaces\", 'description': {'raw': 'Per Roan - \"we were initially going to use this for references and captions, and then chose to use separate documents instead, but this is not compatible with the collaborative editing work; a VE instance should be able to collaborate with another instance on the same page, although I suppose there was some stuff about limiting the scope successfully as well\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416360265, 'spacePHID': None, 'dateCreated': 1371181800, 'dateModified': 1417571289, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49565', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Section edit link behaviour tweaks', 'description': {'raw': \"Clicking the section edit link into VE has three minor issues:\\n\\n* The cursor is positioned at the start of the heading of that section; it should probably go to the start of the next element straight after the section (in most cases, a paragraph)\\n* The page doesn't actually scroll to the correct area; ideally the page should be deliberately scrolled to that section (as it happens, you normally end up on roughly the right part because the page is already scrolled, but there are cases where VE pages are lengthier or shorter than PHP pages and so this can't be relied upon).\\n* The toolbar only appears once you scroll (because it's triggered on page movement, and the page doesn't move at first to get to the section because it's already there) - this means that it suddenly pops into view a bit too late.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372109901, 'spacePHID': None, 'dateCreated': 1371180060, 'dateModified': 1438111552, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49563', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CSS broken in RTL', 'description': {'raw': 'We have plans to use ResourceLoader which will fix a lot of this, but noting it here.\\n\\nMost obviously, the toolbar has two sections which in LRT appear as ABCDE  1234; in RTL they should be 4321  EDCBA, but instead appear as EDCBA  4321. Also issues in dialogs etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374592563, 'spacePHID': None, 'dateCreated': 1371155280, 'dateModified': 1417572930, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49546', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Incorrectly handling nested reference tags (blocked by Parsoid)', 'description': {'raw': 'This is a particular problem with \\'note\\' sections, and references used as notes; they commonly include citations for their statements, and you end up with markup that looks like <ref> some text here <ref> a citation for that text</ref></ref>\\n\\nThe VE is for some reason displaying it as a citation template, \"some text here\", a second citation template and a random </ref> tag. See note 1 in https://en.wikipedia.org/wiki/Fomitiporia_ellipsoidea for example.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371782246, 'spacePHID': None, 'dateCreated': 1371143340, 'dateModified': 1417573204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49536', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dropdown text style menu overlaps with other interface elements', 'description': {'raw': 'See https://upload.wikimedia.org/wikipedia/en/8/8f/Visual_editor_pulldown_menu_problem.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372007755, 'spacePHID': None, 'dateCreated': 1371122520, 'dateModified': 1417573199, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49524', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link input widget filters out redirects for target pages, but this logic is wrong for existing pages', 'description': {'raw': 'Have a link [[Foo]] which is a redirect to [[Foobar]].\\n\\nInspect link; it will suggest:\\n\\nNew pages\\n  Foo\\nExisting pages\\n  Foobar\\n\\nThis is because \"Foo\" does not come back in the list of pages you can link to - which is filtered to remove redirects - but we should special-case the existing link.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50240'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395441844, 'spacePHID': None, 'dateCreated': 1371075060, 'dateModified': 1417572505, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49502', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Capitalisation does not register as a change', 'description': {'raw': 'If someone capitalises a character(see https://en.wikipedia.org/w/index.php?title=Founder_effect&diff=559607253&oldid=558757694 for example) the VisualEditor does not recognise it as an alteration to page text and rejects their edit.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372015558, 'spacePHID': None, 'dateCreated': 1371063300, 'dateModified': 1417572943, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49495', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion inspector blank on opening some templates', 'description': {'raw': 'Screenshot\\n\\nSee associated screenshot - this is for https://www.mediawiki.org/wiki/Template:Extension\\n\\nWhen clicking the inspector icon, the window opens up but remains entirely blank and happily sits there like it for minutes* at a time. More worryingly, if I follow the normal workflow for a broken element (hit the X, make it go away, try and open it again) the inspector refuses to open at all, not just for that template but for other elements on the page.\\n\\n*I gave up waiting; it may load, eventually, or never load.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49797\\n\\n**Attached**: {F11051}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371831543, 'spacePHID': None, 'dateCreated': 1371060840, 'dateModified': 1417573201, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49493', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Some block objects when selected not triggering the inspector menu (no template/image icon)', 'description': {'raw': 'Screenshot\\n\\nScreenshot attached - from https://www.mediawiki.org/wiki/Extension:Syntax_Highlighting\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F11040}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372037973, 'spacePHID': None, 'dateCreated': 1371059580, 'dateModified': 1417573162, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49488', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save dialog should not preserve history when opening a second time', 'description': {'raw': '1. Make a change and press save\\n2. close the save dialog (^)\\n3. Press save again\\n\\nNote there is now a back button (<) which does nothing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372039076, 'spacePHID': None, 'dateCreated': 1371048240, 'dateModified': 1417573161, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49481', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Bad HTML when link seems to have been edited', 'description': {'raw': 'From a bug report in /mnt/bugs on parsoid.wmflabs.org.\\n\\nThe edited HTML snippet in question looks like this:\\n\\n\"<a href=\"./Turkish_sparrow\" rel=\"mw:WikiLink\" data-parsoid=\\'{\"a\":{\"href\":\"./Turkish_sparrow\"},\"sa\":{\"href\":\"Turkish sparrow\"},\"stx\":\"simple\",\"dsr\":[92,111,2,2]}\\'><a href=\"American%20sparrow\" rel=\"mw:WikiLink\">American sparrow</a></a>\"\\n\\nThe editor may tried to edit a link from Turkish -> American sparrow\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372215957, 'spacePHID': None, 'dateCreated': 1370981400, 'dateModified': 1417573158, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49451', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Surface should be able to inherit commands and toolbar from other surface', 'description': {'raw': 'Right now, we have to do the following in ve.ui.MWReferenceDialog and ve.ui.MWMediaDialog to set up the sub-editor\\'s surface correctly:\\n\\nthis.referenceSurface.addCommands( ve.init.mw.ViewPageTarget.static.surfaceCommands );\\n\\nInstead of accessing ve.init.mw (and assuming all surfaces with MW*Dialogs will be instantiated by ve.init.mw.ViewPageTarget), we should just be able to say \"initialize this new surface based on this existing surface\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417198558, 'spacePHID': None, 'dateCreated': 1370964780, 'dateModified': 1438734534, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49439', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deletion from slugged header causes preceding paragraph to appear to be deleted, but remain in the DM(?)', 'description': {'raw': '**Author:** `swalling`\\n\\n**Description:**\\nWhen attempting to remove an entire section with an h2 header, removing the text of the header does not remove the line separator underneath the header. \\n\\nAdditionally, one additional delete/backspace action deleted the entire preceding section, and it seems from the resulting content that I merely blanked the header but the wikitext for it remains.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386029219, 'spacePHID': None, 'dateCreated': 1370932440, 'dateModified': 1417572931, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49424', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Activation of a selected block which is the first content not possible', 'description': {'raw': \"You can select it but the inspector menu doesn't trigger. Works fine if there's any content before the block.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371844292, 'spacePHID': None, 'dateCreated': 1370912820, 'dateModified': 1417573202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49421', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link inspector surface doesn't pop up when the user language is right-to-left\", 'description': {'raw': 'Editing a page in a Hebrew wiki (possibly also in other RTL languages), adding a link does not show the popup. The word automatically becomes a wiki-link, no option to change the destination or make it an external link.\\n\\nThe link seems to work well in English wikis.\\n\\nTested on both my local install with the latest VE (VE-wmf6+) and on the hebrew wikipedia (VE-wmf5) and on both Firefox and Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373002553, 'spacePHID': None, 'dateCreated': 1370904180, 'dateModified': 1417573137, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49416', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid sometimes loads content from another wiki', 'description': {'raw': 'Screenshot of VisualEditor on the English Wikipedia\\n\\nI\\'m not even really sure how to explain this. I\\'ll just include a screenshot.\\n\\nI went to <https://en.wikipedia.org/wiki/Ready,_Willing_and_Able_(Daron_Norwood_song)> and clicked \"edit this page\". This is what appeared.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11769}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373560843, 'spacePHID': None, 'dateCreated': 1370897160, 'dateModified': 1373560843, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49411', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't copy/paste a reference or template unless you select text either side\", 'description': {'raw': \"Create a document:\\n\\nFoo <ref>Bar</ref> Baz\\n<references />\\n\\n=>\\n\\nFoo [1] Baz\\n1. Bar\\n\\n\\n==Test==\\n1. Select and copy from '[' to ']' (no whitespace)\\n2. Try to paste\\n3. Note you now just have plain text [1]\\n4. Note also if you make a larger selection (e.g. from 'o' to 'B'), copy/paste works fine.\\n\\nThis might be to do with whitespace truncation, and probably applies to other inline nodes.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52271\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54410\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415030920, 'spacePHID': None, 'dateCreated': 1370888760, 'dateModified': 1417570405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49396', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Restoring oldids broken', 'description': {'raw': \"On attempting to edit and restore an oldid, everything works fine (oldid contents appear, diff shows correct wikitext change, etc.) but on save VE appears to send the wrong page version (presumably the 'newer' version that's meant to be replaced?) to MW so nothing gets saved.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371588446, 'spacePHID': None, 'dateCreated': 1370882100, 'dateModified': 1417573209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49390', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspector buttons appear above save dialog', 'description': {'raw': '1. Focus a node which triggers an inspector icon\\n2. Hit save\\n3. http://i.imgur.com/5YPyQL5.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49275\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49059'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371766472, 'spacePHID': None, 'dateCreated': 1370781420, 'dateModified': 1417573206, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49361', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copy & paste should use ve.dm.Node#getClonedElement', 'description': {'raw': \"Because we want to be able to make certain properties non-cloneable, e.g. in ve.dm.MWReferenceNode.prototype.getClonedElement we strip 'contentsUsed'.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372379856, 'spacePHID': None, 'dateCreated': 1370612580, 'dateModified': 1417573154, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49307', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Review dialog obfuscated by phantoms', 'description': {'raw': \"Screenshot of VisualEditor on the English Wikipedia using the Monobook skin, 2013-06-06\\n\\nVisualEditor's review dialog box can be obfuscated by the green striped area from restricted areas of a page. This is when using Monobook, at least. Maybe Vector too, I don't know. I've attached a screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11508}\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372084364, 'spacePHID': None, 'dateCreated': 1370571600, 'dateModified': 1417573161, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49284', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Images loaded over HTTP unconditionally', 'description': {'raw': 'https://en.wikipedia.org/wiki/Jeffrey_Chiesa?veaction=edit\\n\\nWhen I go here currently, I get HTTPS warnings.\\n\\n---\\nThe page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/5/5f/New_Jersey_Attorne…effrey_S_Chiesa.jpg/144px-New_Jersey_Attorney_General_Jeffrey_S_Chiesa.jpg.\\n Jeffrey_Chiesa:1\\nThe page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/f/f0/Seal_of_the_United_States_Senate.svg/80px-Seal_of_the_United_States_Senate.svg.png.\\n Jeffrey_Chiesa:1\\nThe page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/8/8d/Seal_of_New_Jersey.svg/90px-Seal_of_New_Jersey.svg.png.\\n Jeffrey_Chiesa:1\\nThe page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/9/92/Flag_of_New_Jersey.svg/75px-Flag_of_New_Jersey.svg.png.\\n Jeffrey_Chiesa:1\\nThe page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/5/5f/New_Jersey_Attorne…effrey_S_Chiesa.jpg/144px-New_Jersey_Attorney_General_Jeffrey_S_Chiesa.jpg.\\n Jeffrey_Chiesa:1\\nThe page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/f/f0/Seal_of_the_United_States_Senate.svg/80px-Seal_of_the_United_States_Senate.svg.png.\\n Jeffrey_Chiesa:1\\nThe page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/8/8d/Seal_of_New_Jersey.svg/90px-Seal_of_New_Jersey.svg.png.\\n Jeffrey_Chiesa:1\\nThe page at https://en.wikipedia.org/wiki/Jeffrey_Chiesa displayed insecure content from http://upload.wikimedia.org/wikipedia/commons/thumb/9/92/Flag_of_New_Jersey.svg/75px-Flag_of_New_Jersey.svg.png.\\n Jeffrey_Chiesa:1\\n---\\n\\naction=view is fine (no console warnings). When I go to veaction=edit, the console fills with warnings. It looks like VisualEditor is loading thumbnails unconditionally through HTTP. This should be changed to be protocol-relative.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://en.wikipedia.org/wiki/Jeffrey_Chiesa?veaction=edit'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371576350, 'spacePHID': None, 'dateCreated': 1370571480, 'dateModified': 1373511816, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49283', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Phantoms appear above the save dialog, preventing saving', 'description': {'raw': '**Author:** `swalling`\\n\\n**Description:**\\nScreenshot\\n\\nIn attempting to test (as anon) on the MediaWiki.org sandbox, the page header template overlaps the diff and save functions, preventing me from saving my edit.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49361\\n\\n**Attached**: {F11481}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371766465, 'spacePHID': None, 'dateCreated': 1370553900, 'dateModified': 1417573206, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49275', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add a temporary option to have section edit links go to wikitext editor, not VisualEditor', 'description': {'raw': \"Necessary for beta rollout. Wording needs to be smithed carefully to ensure that it's clear that this is a temporary option.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371161777, 'spacePHID': None, 'dateCreated': 1370536440, 'dateModified': 1417573214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49260', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Arrow keying around multibyte unicode characters fails after an inline node', 'description': {'raw': \"For example in the second line of the multibyte.html test file in the standalone demo (after '<tt>香港</tt>' [Hong Kong])\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370969172, 'spacePHID': None, 'dateCreated': 1370520480, 'dateModified': 1417573218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49246', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters', 'description': {'raw': 'Visual Editor doesn\\'t behave correctly when editing and adding text with combining diacritics.\\n\\nFor example insert the text \"ɛ́\" (ɛ is character U+025B, combining acute is U+0301).\\nWhen the cursor is behind \"ɛ́\":\\n- pushing the left arrow doesn\\'t move the cursor\\n- adding text like \"ɛ́abcdef\" is fine but:\\n  - pushing backspace gives \"ɛ́abcda\" instead of expected \"ɛ́abcde\"\\n  - pushing return ives \"ɛ́abcde\\\\na\"\\n\\nSome languages require combining diacritics, many keyboard layouts allow their input or user can insert them by copying and pasting from somewhere else.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51472'}, 'authorPHID': 'PHID-USER-i5at67w766dqxs6ncxam', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371844259, 'spacePHID': None, 'dateCreated': 1370504280, 'dateModified': 1417573084, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49233', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: IE9/10 incompatibilities with saving process', 'description': {'raw': 'grey text, no diff appears after Review and save\\n\\nSeen in IE9 and below, works OK in FF and Chrome: \\n\\nMake an edit with VE\\nClick Review and save\\n\\nPage text is greyed out; no diff appears; Review and save button remains clickable; user cannot complete edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11329}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409960073, 'spacePHID': None, 'dateCreated': 1370450340, 'dateModified': 1423674433, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49187', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Arrow keying off end of throws an exception', 'description': {'raw': '* Move cursor to start/end of document\\n* Press left (start) or right (end)\\n* An exception is thrown by handleLeftOrRightArrowKey\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370447615, 'spacePHID': None, 'dateCreated': 1370295780, 'dateModified': 1417573220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49091', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Attribute order preservation is hopeless, get rid of it', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371207206, 'spacePHID': None, 'dateCreated': 1369928220, 'dateModified': 1417573212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48980', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add support for multi character grapheme clusters in UnicodeJS', 'description': {'raw': 'So that we can correctly calculate boundaries in unicode.wordbreak.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370532478, 'spacePHID': None, 'dateCreated': 1369926300, 'dateModified': 1417573219, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48975', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Respect Parsoid's <base>\", 'description': {'raw': \"Currently we don't -> lots of broken imagery in /w/index.php etc. entry points.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=59196\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382985540, 'spacePHID': None, 'dateCreated': 1369779540, 'dateModified': 1486157169, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48915', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: {Ctrl,Option}+{Delete,Backspace} doesn't delete a word in an RTL wiki\", 'description': {'raw': \"Pressing Ctrl-Backspace deletes a word in a <textarea> in Firefox. It works the same way in VisualEditor when the wiki's language is English, but if it's Hebrew, it only deletes one character.\\n\\nA GWT testing scenario for this would be something like this:\\n\\nGiven $wgLanguageCode is 'he'\\n        And I am editing an article\\n        And I wrote 'אחת שתיים שלוש'\\nWhen I press Ctrl-Backspace\\nThen the remaining text is 'אחת שתיים '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372962082, 'spacePHID': None, 'dateCreated': 1369777380, 'dateModified': 1417573140, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48912', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor before first character of heading and hitting Enter advances cursor one position', 'description': {'raw': \"Place the cursor at the first position of some heading (before the heading's first character). Hit Enter. As expected, an empty line appears before the heading, but the cursor is unexpectedly advanced by one position and is now located *after* the heading's first character.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372901377, 'spacePHID': None, 'dateCreated': 1369603080, 'dateModified': 1417573141, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48847', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Block-level media items' placement is incorrect (no clear after thumbs)\", 'description': {'raw': 'Open the VisualEditor on the page https://en.wikipedia.org/wiki/Battle_of_Paris_(1814) . The two images are placed side by side between the lead paragraph and the infobox; they should be placed below the infobox. \\n\\nIt appears that the VisualEditor generally arranges two images horizontally rather than vertically, unlike the wikitext renderer.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371083774, 'spacePHID': None, 'dateCreated': 1369599780, 'dateModified': 1424894570, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48845', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: List langlinks (readonly) in the meta-data dialog', 'description': {'raw': \"This is to make the categories pane less lonely; we will want to do this 'properly' (writable) later, though this is… challenging given the Wikidata complexities.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370489154, 'spacePHID': None, 'dateCreated': 1369497420, 'dateModified': 1417573220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48814', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Content is LTR even when the page language is RTL', 'description': {'raw': 'This is using Firefox under Ubuntu 13.x:\\n\\n\\nThe problem:\\nIf the wiki is RTL (Hebrew, for instance), start editing an empty page. The caret appears on the left side and the typing is done LTR.\\n\\n\\nI did a quick check, and noticed that there is a class added to the content box - \"ve-ui-surface mw-content-ltr\" even when the page language is rtl (defined in the <html dir=\"rtl\"..>\\n\\nI found this addition in the ve.init.mw.ViewPageTarget line 786:\\nthis.surface.$.addClass( \\'mw-content-\\' + mw.config.get( \\'wgVisualEditor\\' ).pageLanguageDir );\\n\\nIn my system this produced \"mw-content-ltr\" despite the fact the page language was Hebrew and the html direction was defined as rtl. \\n\\nHowever, I then tried to forcefully change it to rtl, just to test, and while the class appeared correctly (mw-content-rtl), the direction of the typed text was still LTR. It remained LTR when I changed the language to English.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369782964, 'spacePHID': None, 'dateCreated': 1369379280, 'dateModified': 1417573223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48765', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting and copying one node throws an exception', 'description': {'raw': \"Select an inline node (e.g. an inline image) on it's own (i.e. no whitespace either side of it), and trying to copy will throw an exception (ve.dm.Document.js:786 selection[0].range is undefined)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377634914, 'spacePHID': None, 'dateCreated': 1368892860, 'dateModified': 1417573070, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48604', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit triggered repeated inserts of existing text with snowman', 'description': {'raw': \"I used VE in Firefox 21.0 on Ubuntu to edit https://www.mediawiki.org/wiki/Backporting_Fixes . I changed a few headings, then pressed Enter between a heading and a numbered list below it to insert a new line (not sure if the caret was on the end of the heading or the start of the first item, I'm not sure if I started typing.\\n\\nVE began inserting the first sentence of the numbered list but with its link changed to two snowmen, about 15 times. Every time I clicked it would prepend some more.  Even scrolling would trigger this.\\n\\nBefore, the document contained\\n\\n== WMF Cluster Backports ==\\n# Make sure there is a bug registered in [[mw:Bugzilla|Bugzilla]] for the issue.\\n\\nI couldn't edit the document, but VE's review and save button worked fine. The new document showed as\\n\\n== ==\\n# Make sure there is a bug registered in ☃☃ for the issue.Make sure there is a bug registered in ☃☃ for the issue. <repeated 269 more times>Make sure there is a bug registered in [[mw:Bugzilla|Bugzilla]] for the issue.\\n\\nI don't know what happened to the heading, I didn't blank it out. I might have attempted a cut and paste, maybe that's what's going haywire, though I'm pretty sure the last thing I did was pressed Enter to add a sentence after the heading.\\n\\nI assume this is an Easter egg in the VE codebase: if you manipulate the document near an exhortation to file a bug, Parsoid detects it and repeats the phrase, with snow people 8-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371147355, 'spacePHID': None, 'dateCreated': 1368826620, 'dateModified': 1417573214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48592', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Spaces added before colons and links in some cases', 'description': {'raw': 'See https://fr.wikipedia.org/w/index.php?title=COE&diff=prev&oldid=93166267 for example.\\n\\nI only removed the link, but VisualEditor added a space before the colons.\\n\\nAnother example: https://fr.wikipedia.org/w/index.php?title=MSS&diff=prev&oldid=93166411\\n\\nThere was already two spaces, but VisualEditor added a third.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51024'}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383667577, 'spacePHID': None, 'dateCreated': 1368776580, 'dateModified': 1423674753, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48570', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Convert save dialog to use ve.ui.Dialog', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381186965, 'spacePHID': None, 'dateCreated': 1368753300, 'dateModified': 1417573069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48566', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't move to last item in category dialog suggester box with cursors\", 'description': {'raw': 'Not sure how to reproduce, but I get two items in the \"Matching categories\" section; I can only move to the top one, and pressing down doesn\\'t work (but pointer-highlighting and selection does).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371002039, 'spacePHID': None, 'dateCreated': 1368749160, 'dateModified': 1417573216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48565', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make a toolbar button to trigger the meta-data inspector', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369416082, 'spacePHID': None, 'dateCreated': 1368747960, 'dateModified': 1417573224, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48561', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Category changing in page doesn't cause footer to be updated on save\", 'description': {'raw': 'Do we need to trigger a re-render of the catlinks div? Can we?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52403'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389638336, 'spacePHID': None, 'dateCreated': 1368747000, 'dateModified': 1444199682, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48560', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking link button while link inspector is already open throws error', 'description': {'raw': 'The button should probably not do anything if the inspector is already open.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369256685, 'spacePHID': None, 'dateCreated': 1368737040, 'dateModified': 1417573225, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48549', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image resize handles persist on close', 'description': {'raw': \"If the image has focus when you click back on the 'Read' tab, the four circles stay on the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369454138, 'spacePHID': None, 'dateCreated': 1368698040, 'dateModified': 1417573223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48530', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switch document re-renderer from action=parse over to Parsoid API now it exists', 'description': {'raw': 'Once it exists being the relevant part. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397867827, 'spacePHID': None, 'dateCreated': 1368662820, 'dateModified': 1443276405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48524', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Switching back to 'Read' tab before 'Edit' tab has loaded throws an exception\", 'description': {'raw': \"In ve.init.mw.ViewPageTarget.prototype.tearDownToolbar, this.toolbar is undefined if the editor hasn't finished loading.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368885093, 'spacePHID': None, 'dateCreated': 1368653280, 'dateModified': 1417573278, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48520', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MWLinkTargetInputWidget should grok case sensitivity of suggested page title vs. the inputed text', 'description': {'raw': 'Screenshot of problem\\n\\nScenario:\\n* Document contains \" ... esams ... \"\\n* Wiki has a page called \"Esams\".\\n* Wiki does not have case-sensitive first character in the main namespace.\\n* Select \"esams\" and turn it into a link\\n* UI shows:\\n  [ esams            ]\\n  New page:\\n    <redlink> esams\\n  Matching page:\\n    Esams\\n    Esams cluster\\n    Esams patches\\n\\nThat first redlink is incorrect, it should show the same as when the input is \"Esams\" (with capital E), namely no \"redlink\" since the first match is in fact the input.\\n\\nIt needs to account for the $wgCapitalLinkOverrides and $wgCapitalLinkOverrides configuration etc. This is abstracted in PHP by MWNamespace::isCapitalized, which is exposed in javascript as \\'wgCaseSensitiveNamespaces\\' in mw.config.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F10838}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369183085, 'spacePHID': None, 'dateCreated': 1368573360, 'dateModified': 1566902904, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48476', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Heading on a slug is created on the wrong line in Firefox', 'description': {'raw': '1 Go to a page with several paragraphs. Edit with VisualEditor.\\n\\n2. Place cursor at the end of paragraph N and press Enter to create a new line. See the cursor blinking in a new line after paragraph N.\\n\\n3. Select \"Heading 2\" in the dropdown menu.\\n\\nEXPECTED\\n\\nA Heading 2 line appears at the end of paragraph N.\\n\\n\\nACTUAL OUTCOME\\n\\nA Heading 2 line appears at the end of paragraph N-1.\\n\\n\\nAs a matter of fact I find no way to place the header where I want, unless going to the end of paragraph N+1 only to trick the bug. Selecting an existing line and trying to make a header out of it doesn\\'t seem to work either (but this is probably a different bug).\\n\\nHappens at least in mediawiki.org with Firefox 22.0a2 (2013-05-07).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372371426, 'spacePHID': None, 'dateCreated': 1368554100, 'dateModified': 1417573153, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48464', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove alpha notice', 'description': {'raw': 'When I go to use the VisualEditor (e.g., <https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals> --> click \"edit\"), there\\'s a bothersome notice every time the VisualEditor form loads about how it\\'s the alpha version of the tool. There\\'s no way to dismiss the notice and it gets a bit grating after a while.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371057658, 'spacePHID': None, 'dateCreated': 1368496800, 'dateModified': 1417573216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48428', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pre-beta needs (tracker)', 'description': {'raw': 'Tracker for the bugs/enhancements that should be done for the beta.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393640096, 'spacePHID': None, 'dateCreated': 1368493800, 'dateModified': 1540684715, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48426', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images: Image links are interpreted as image inclusions', 'description': {'raw': '[[:File:SpecialPage_Filter_JS.png]]\\n\\nis being converted to:\\n\\n<a rel=\"mw:Image\" href=\"../File:SpecialPage_Filter_JS.png\" data-parsoid=\"{&quot;tsr&quot;:[21446,21481],&quot;src&quot;:&quot;[[:File:SpecialPage Filter JS.png]]&quot;,&quot;dsr&quot;:[21446,21481,null,null]}\"><img src=\"../Special:FilePath/SpecialPage_Filter_JS.png?width=200\" alt=\"SpecialPage_Filter_JS.png\" width=\"200\" style=\"vertical-align: middle;\" data-parsoid=\"{}\"></a>\\n\\nIt should be an <a> without the <img> inside it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://parsoid.wmflabs.org/mw/User:Dantman/Code_Ideas'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371761509, 'spacePHID': None, 'dateCreated': 1368389040, 'dateModified': 1372934030, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48387', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Whitespace preservation for auto-links not working sometimes(?)', 'description': {'raw': 'Putting this in DM because it seems the most likely suspect.\\n\\nOriginal bug occurred on enwiki (text in the test stolen from there). This feels like a bit of bug 43543 - which was fixed?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/w/index.php?title=VisualEditor:TestAutolinks&diff=688670&oldid=688669'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368379914, 'spacePHID': None, 'dateCreated': 1368315240, 'dateModified': 1417573286, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48367', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't delete-merge two paragraphs together if the first one ends with an inline-alien\", 'description': {'raw': \"This was happening with <ref>s, but it looks like it'll be an issue with an paragraph that ends with an inline alien:\\n\\n| Foo.<ref>Ref</ref>\\n| Bar.\\n\\nBackspace with the cursor to the left of the 'B', or delete with the cursor to the right of the <ref> block, has no effect.\\n\\nThe problem with <ref>s will go away(?) when that node handler code is enabled, but is this a wider issue?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372369220, 'spacePHID': None, 'dateCreated': 1368313200, 'dateModified': 1417573155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48366', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Re-factor key detection to be more robust and not occasionally break/pawn in Firefox', 'description': {'raw': 'Inez has some ideas about how to do this, so marking to him for now. Would be nice to document here /home/ we want to do this so someone can pick it up at some point. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371180920, 'spacePHID': None, 'dateCreated': 1368215940, 'dateModified': 1417573212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48335', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Keyboard up/down selection sometimes (but not always) selects two lines rather than one in Firefox', 'description': {'raw': 'Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services\\nPut the cursor somewhere in the text.\\nType \"Enter\" 2 times.\\nType \"Up\".\\nType a\\nType Enter\\nType b\\nType Up\\nType Left\\nPress Shift and hold it\\nType Down\\n\\nExpected: selection of 1 line\\nActually: selection of 2 lines\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372465847, 'spacePHID': None, 'dateCreated': 1368090660, 'dateModified': 1417573152, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48289', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tab in a slug in Firefox causes a pawn character to be inserted', 'description': {'raw': 'Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services\\nPut the cursor somewhere in the text.\\nType \"Enter\" 2 times.\\nType \"Up\".\\nType \"Tab\"\\n\\nWild pawn appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369093388, 'spacePHID': None, 'dateCreated': 1368090300, 'dateModified': 1417573228, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48288', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dirty diffs causing some citations to be duplicated', 'description': {'raw': 'Examining with user what browser/etc. to investigate.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: http://en.wikipedia.org/w/index.php?title=Indo-Pakistani_War_of_1965&diff=prev&oldid=552704403'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368803220, 'spacePHID': None, 'dateCreated': 1367950620, 'dateModified': 1417573280, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48227', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing at the end of linked causes DM and CE to get out of sync', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383768080, 'spacePHID': None, 'dateCreated': 1367866920, 'dateModified': 1417573069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unexpected non-pawn characters appear after CTRL-B and CTRL-I', 'description': {'raw': 'unexpected untyped characters\\n\\nUpon loading page in VE: \\n\\nClick CTRL-B and type some characters; \\nclick CTRL-I and type some characters; \\n\\n* often but not always reproducible, seen in Chrome/OSX, also reported in IE and FF: upon typing after ctrl-B or ctrl-I for \"bold\" or \"italic\", characters appear that have not been entered.  see screen shot\\n\\n* possibly related, seen but not reproducible:  some combination of actions will cause VE to type a string into a page over and over and over without any action on the part of the user.  I\\'ll file a new bug if I can figure out how to repron that behavior.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11070}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371781126, 'spacePHID': None, 'dateCreated': 1367863980, 'dateModified': 1417573205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48166', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pre-annotations not working in spans', 'description': {'raw': 'From this bug report on parsoid.wmflabs.org: /mnt/bugs/2013-05-04T01:11:28.439Z-Style_guide%252FAssets_and_gallery\\n\\n\"I typed some text in this paragraph that is styled as a span italic, and VE decided to close and reopen the span on either side of the link. I think that happened before I made the text a link. (This is User:S Page (WMF) here.)\"\\n\\nRelevant diff line below:\\n\\n− \\t\\n:<span style=\"font-style: italic;\">See Also: [[Commons:Category:MediaWiki style guide]]</span>\\n\\n+ \\t\\n:<span style=\"font-style: italic;\">See also: </span>[[Wikimedia Foundation Design/Agora Icon Set]] and<span style=\"font-style: italic;\"> [[Commons:Category:MediaWiki style guide]]</span>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369247921, 'spacePHID': None, 'dateCreated': 1367852460, 'dateModified': 1417573226, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48159', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Link insertion annotation makes it difficult to add plain text after a link', 'description': {'raw': \"If you add a link to the last word in your paragraph (quite common I'd imagine if you're in the middle of typing a sentence), the insertion annotation behaviour makes any text typed after the link part of that link - which in most cases is not what you meant to do.\\n\\nInsertion annotations make sense for text style annotations, but not link annotations. This is what Google Docs & LibreOffice do aswell.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368373764, 'spacePHID': None, 'dateCreated': 1367794320, 'dateModified': 1417573286, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48114', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Access keys - leave Ctrl+Option+e for the (newly-relabelled) \"edit source\" tab; Add Ctrl+Option+v for the VisualEditor \"edit\" tab', 'description': {'raw': \"Currently we steal all the things on action=edit for veaction=edit (so Ctrl-Option-e goes to VisualEditor, leaving nothing for the wikitext editor). We should add a new one - Ctrl-Option-s (for *s*ource) - though that's used for save in the wikitext editor, which is a bit odd. Ideas?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368232252, 'spacePHID': None, 'dateCreated': 1367769060, 'dateModified': 1417573287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48107', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link inspector shouldn't correct newly-created [[Foo|foo]] to [[Foo]]\", 'description': {'raw': 'I changed a link here: http://sv.wikipedia.org/w/index.php?title=Intellektuell_s%C3%A4rbeg%C3%A5vning&diff=21539781&oldid=21539483\\n\\nIn the VisualEditor interface, the word \"Känsla\" is showed with a lower case k, but when you are looking at the article, or source it is K.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368631481, 'spacePHID': None, 'dateCreated': 1367618160, 'dateModified': 1417573283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48060', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn characters created when moving cursors around inline images in Firefox', 'description': {'raw': 'All the pawns\\n\\nSee attached image, basically the idea is that indenting or de-indenting a list item will cause there to be a pawn in the list item. Also, when I used the arrow keys to navigate past some images, it put pawns next to the images.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10767}'}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369100291, 'spacePHID': None, 'dateCreated': 1367532360, 'dateModified': 1417573226, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48024', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In RTL, the \"Edit\" tab appears down-tab (to the left) rather than up-tab (to the right) of \"Edit source\"', 'description': {'raw': 'The order should be Edit then Edit tab. Looks like a hard-coded left somewhere?'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1506606636, 'spacePHID': None, 'dateCreated': 1367527740, 'dateModified': 1507135017, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48017', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: JS exception is thrown when trying to use list (ordered or bullet) tool in block slug', 'description': {'raw': 'There are probably two solutions - make it work - or disable list buttons while in block slug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372704235, 'spacePHID': None, 'dateCreated': 1367431680, 'dateModified': 1417573150, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47947', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: heading removal adds ♙', 'description': {'raw': \"The user was trying to edit http://de.wikipedia.org/w/index.php?title=Reiniger,_Gebbert_%26_Schall&direction=prev&oldid=117917379 to remove the first heading but keep the image. The result was http://de.wikipedia.org/w/index.php?title=Reiniger,_Gebbert_%26_Schall&direction=next&oldid=103767568 and the didn't manage to do it without adding the ♙.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368548559, 'spacePHID': None, 'dateCreated': 1367427120, 'dateModified': 1417573285, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47943', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support <div> blocks', 'description': {'raw': 'This just means supporting their use, not being able to set their parameters, but will de-alienate a large amount of content for trivial work at our end. The parameter setting/editing will need to come later.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367372802, 'spacePHID': None, 'dateCreated': 1367371680, 'dateModified': 1367372802, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47907', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Thread title containing \"</div>\" destroys entire page with $wgUseTidy = true', 'description': {'raw': 'Screenshot of LQT thread with </div> in title\\n\\nShould be treated the same as regular page titles: Escape everything.\\n\\n\\nOr, if we want to keep wikitext parsing (e.g. for wikilinks, sometimes done in section headings), then parse as inline block (not allowing any block level elements like <div> or <table>) and make sure open/close tags match (run Tidy).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://www.mediawiki.org/wiki/Thread:Project:Support_desk/visible_html_on_pages%3A\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=31244\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=29564\\n\\n**Attached**: {F10533}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1644958499, 'spacePHID': None, 'dateCreated': 1367340180, 'dateModified': 1644958499, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47885', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Blanked page content in edit mode using Firefox', 'description': {'raw': 'VisualEditor (50e8693)\\nParsoid (ba0b080)\\nMW: 1.22/wmf2 (814f75e)\\n\\nWhile editing a page in Firefox 20.0, the existing page content is blank in the editor.\\n\\nThe issues seems to be an issue with Firefox only, as Chrome and Safari work as expected.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**OS**: Mac OS X 10.7\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-evwol34rsld7viokxokd', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367288171, 'spacePHID': None, 'dateCreated': 1367254380, 'dateModified': 1367288171, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47834', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking away before VE loads completely throws JS error', 'description': {'raw': 'VE error when not completely loaded\\n\\non any page editable by VE:\\n\\ninvoke VE\\nimmediately click Preferences or other live link\\n\\nan alert appears saying \"Error loading data from server: error. Would you like to retry?\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10400}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368885099, 'spacePHID': None, 'dateCreated': 1367196780, 'dateModified': 1417573277, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47813', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Backspace over lists doesn't delete the LIs\", 'description': {'raw': \"Hi,\\n\\nThe problem is that when I have created a bullet list in Visual Editor and try to erase back the text using Backspaces, the numbers or bullet points don't delete even if I have deleted the whole text. Here is a trivial demonstration :\\n\\n1. Hello1\\n2. Hello2\\n3. Hello3\\n\\nNow when I try to delete it from the Hello3 using backspaces, all the text upto first bullet is deleted, but those bullet points are left as it is. \\n\\n1.\\n\\n2.\\n\\n3.\\n\\n\\nImages:\\n\\nhttps://docs.google.com/file/d/0B3eGCB261PalaDhqa1ZhcmFPUk0/edit?usp=sharing\\nhttps://docs.google.com/file/d/0B3eGCB261PalbndsZEFSdXpEZGM/edit?usp=sharing\\n\\nTested on Firefox 20.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-d3oiyxwdmebcjszfff7w', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368565464, 'spacePHID': None, 'dateCreated': 1367169780, 'dateModified': 1417573285, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47795', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide a way for the user to switch between VisualEditor and wikitext source editor modes without saving', 'description': {'raw': \"Add button to WikiEditor and VisualEditor for switching back and forth.\\n\\n* Only shown if in WE you have VE enabled (otherwise don't show)\\n* If no changes, switch immediately\\n* If there are changes, prompt the user (with the same OOUI message dialog we use in VE) whether to switch with or without their changes\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1446646641, 'spacePHID': None, 'dateCreated': 1367087280, 'dateModified': 1660398842, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47779', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit vs. edit source tab split not preserved across action=history, action=edit, Special:Undelete, …', 'description': {'raw': \"Right now you get | Edit | Edit source | on read and on VE edit (which are the same thing) but nowhere else, which is confusing.\\n\\n(Whilst we're at it, logs, diff view pages, and probably a few dozen others have edit links which will need to be replaced or augmented.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367860149, 'spacePHID': None, 'dateCreated': 1367086560, 'dateModified': 1417573291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47776', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Provide a language inspector to handle inline <span lang='xx' dir='yyy'>s\", 'description': {'raw': 'In [[en:User:Yamaha5/sandbox]] I tested it for Farsi every thing was OK except <div dir=\"rtl\"><div> which cause the test disable. in fa.wiki because of mixture of farsi and english or LTR Math formulas we use direction inside the text so it will cause problem for RTL languages\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-dswbdv7ibhsefllcqarz', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390007334, 'spacePHID': None, 'dateCreated': 1367020500, 'dateModified': 1443276409, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47759', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Trailing whitespace at end of paragraph or table cell dropped on round-trip', 'description': {'raw': 'Ubuntu/Firefox\\nGo to http://en.wikipedia.org/wiki/Alfresco_%28software%29\\nAt the end of a line, add a space and remove it\\nClick \"Save\"\\nNo changes should have happen, but there actually are changes, in the infobox:\\n\\n| caption = Alfresco Share / Repository Browser <br/> (Community Edition)\\nbecame\\n| caption =Alfresco Share / Repository Browser <br></table> (Community Edition)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367901947, 'spacePHID': None, 'dateCreated': 1366964340, 'dateModified': 1417573290, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47712', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Shift-Right deletes characters instead of selecting in Firefox', 'description': {'raw': \"Edit an article\\nPress down your keyboard's SHIFT key\\nWhile maintaining SHIFT pressed, press the RIGHT key a few times\\n\\nEXPECTED: Characters are selected\\nACTUALLY: Characters are deleted\\n\\nUbuntu/Firefox\\n\\nLooks like https://bugzilla.wikimedia.org/show_bug.cgi?id=41062 which had been fixed in October.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367286853, 'spacePHID': None, 'dateCreated': 1366963620, 'dateModified': 1417573294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47711', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn ♙ appears after pressing Down key (first thing) in Firefox', 'description': {'raw': \"Steps to reproduce:\\n\\n1. Open http://en.wikipedia.org/wiki/CMIS\\n2. Press Edit\\n3. Press your keyboard's Down key\\n4. Wild pawn ♙ appears\\n\\nAlso reproduced on http://ja.wikipedia.org/wiki/%E3%83%95%E3%83%AB%E3%83%BC%E3%83%AB%E3%83%BB%E3%83%89%E3%83%BB%E3%82%BB%E3%83%AB\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367004998, 'spacePHID': None, 'dateCreated': 1366963320, 'dateModified': 1417573298, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47710', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Hard-coded strings in ve.ui.MWLinkTargetInputWidget.prototype.populateMenu', 'description': {'raw': \"From user report:\\n\\n'externalLink', { '$$': menu$$, 'label': 'External link' }\\n'newPage', { '$$': menu$$, 'label': 'New page' }\\n'matchingPages', { '$$': menu$$, 'label': 'Matching page' }\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367019435, 'spacePHID': None, 'dateCreated': 1366955760, 'dateModified': 1417573296, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47706', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn ♙ appears when two paragraphs of different language are next to each other(?)', 'description': {'raw': 'https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Matanya/%D7%90%D7%A8%D7%92%D7%96_%D7%97%D7%95%D7%9C_2&diff=14076208&oldid=14076205\\n\\nhttps://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Matanya/%D7%90%D7%A8%D7%92%D7%96_%D7%97%D7%95%D7%9C_2&diff=14076218&oldid=14076208\\n\\n(Others.)\\n\\nUser says they get this when switching he/en and back again.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373221327, 'spacePHID': None, 'dateCreated': 1366933140, 'dateModified': 1417573096, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47687', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page', 'description': {'raw': 'EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the \"notices\" functionality.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369409008, 'spacePHID': None, 'dateCreated': 1366932300, 'dateModified': 1417573224, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47683', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After saving a page, the VisualEditor tab points at the oldid content not the new one', 'description': {'raw': \"Edit a page in VE, press save; enter VE again.\\n\\nWhat should happen: You edit the newly-updated page.\\n\\nWhat does happen: You edit the content of the page before you updated it (and VE doesn't know it's doing this).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367614840, 'spacePHID': None, 'dateCreated': 1366932180, 'dateModified': 1417573280, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47682', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE should not become active on non-wikitext ContentHandler-type', 'description': {'raw': 'The VE becomes active on .js and .css pages in the user namespace, even though it is not capable of handling this content type.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/wiki/User:TheDJ/common.js'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368463148, 'spacePHID': None, 'dateCreated': 1366469700, 'dateModified': 1426479187, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47456', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Edit source\" tab doesn\\'t become \\'active\\'', 'description': {'raw': \"If in a page you click 'Edit source', the tab does not receive the 'selected' styling/class as it is supposed to.\\n\\nThis was confirmed with Safari 6 mac.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367602843, 'spacePHID': None, 'dateCreated': 1366463880, 'dateModified': 1417573288, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: data-parsoid attribute sometimes not preserved properly', 'description': {'raw': \"a </table> tag is sometimes inserted into data-parsoid when set on a table element, for example in the 'Infobox settlement' at http://en.wikipedia.org/wiki/Beale_Township,_Juniata_County,_Pennsylvania.\\n\\nOriginal data-parsoid (part of):\\nBeale Township,<br/>Pennsylvania\\\\n\\n\\nVE output (editedHtml):\\nBeale Township,<br></table>Pennsylvania\\\\n\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366992022, 'spacePHID': None, 'dateCreated': 1366407120, 'dateModified': 1366992392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47430', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting to/from a blank lines fails', 'description': {'raw': 'If you have lines like so:\\n\\n| A\\n| B\\n| \\n| C\\n\\nDeleting backwards from up-page of C, or from within the blank line above C, causes the cursor to move (as expected) but no deletion.\\n\\nDeleting forwards from down-page of B, of from within the blank line below B, causes the cursor to stay (as expected) but no deletion.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371781860, 'spacePHID': None, 'dateCreated': 1366397400, 'dateModified': 1417573204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47424', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reopening page in VE immediately after saving page in VE loads old version', 'description': {'raw': '(a) open a page in VE and edit it\\n(b) save in VE \\n(c) reopen the same page right away in VE\\n\\nThe previous version (rather than saved version) is fetched.  I looked at POST params in chrome and looks like revision id (oldid) being sent is of the older version rather than the saved version.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373061639, 'spacePHID': None, 'dateCreated': 1366393860, 'dateModified': 1417573143, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47420', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Re-used refs wrongly expanded to <ref name=\"…\" ></span>', 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=User:Fluffernutter/Kinne&diff=551148728&oldid=551148307\\n\\nTo investigate.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366992579, 'spacePHID': None, 'dateCreated': 1366387680, 'dateModified': 1417573295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47417', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[TUX] Cannot confirm outdated translation on \"page\" view', 'description': {'raw': 'Screenshot of the problem\\n\\nOn the \"page\" view, when an outdated translation is opened, the editor shows a disabled \"save translation\" as the main action.\\n\\nIt should show an enabled \"Confirm translation\" button instead (as it is the case for the \"list\" view).\\n\\nI found the bug on outdated translations at https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-visualeditor&language=ca&filter=&action=page\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10395}'}, 'authorPHID': 'PHID-USER-c47vnc2yxmwfvvc4367q', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392664217, 'spacePHID': None, 'dateCreated': 1366356360, 'dateModified': 1392664217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47397', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] VisualEditor: Edit tab should have tooltip and accesskey', 'description': {'raw': 'Ordinarily there\\'s an accesskey (e.g. alt+shift+E in Firefox) on the \"Edit\" tab in Vector. The accesskey is made known to the user through a tooltip. VisualEditor eliminates this accesskey and tooltip, and adds a new \"Edit source\" tab without an accesskey or tooltip. \\n\\nIdeally both the \"Edit\" and \"Edit source\" tab should have accesskeys and tooltips to allow quick switching between the modes for power users.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366745664, 'spacePHID': None, 'dateCreated': 1366355400, 'dateModified': 1417573331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47396', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Double-click to overwrrite is broken', 'description': {'raw': '1. Open http://ve-change-marking.instance-proxy.wmflabs.org/wiki/Test\\n2. Double-click a word and type a single-char\\n   (you see that the selected word continues to show in the interface after the char you typed)\\n3. Look at review-and-save.\\n4. The word has actually been deleted => the interface is not updated as it should\\n\\n(4) causes the user (=me in this case) to repeatedly try and delete that word and is instead deleting newer words which will all show up in the diff without realizing that they are being deleted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366340790, 'spacePHID': None, 'dateCreated': 1366326300, 'dateModified': 1417573334, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47391', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Round-tripping failure - Extra newline added at end of body', 'description': {'raw': 'When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368557767, 'spacePHID': None, 'dateCreated': 1366312920, 'dateModified': 1417573284, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47373', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Lazy-update SurfaceFragment', 'description': {'raw': \"For performance reasons, we should lazy-update SurfaceFragments rather than updating them through a transact event handler.\\n\\nThe performance problem occurs when you create a bunch of fragments, then throw them away. The fragments are never actually destroyed, if only because the surface still has references to them because of the event binding. The discarded fragments continue to receive events about transactions and update themselves in response, but no one is using them any more.\\n\\nInstead, I propose the following:\\n\\n* The surface should have an ordered array of [transaction, direction] pairs that tracks everything that has ever been applied. This is not the same as the undo/redo stacks: this particular array is append-only\\n* Every SurfaceFragment has a property indicating which transaction (by index in the big array) is the last one that it knows about\\n* SurfaceFragments do not listen for transact events\\n* Instead, every time getRange() is called, the fragment asks the surface whether there are new transactions (with indices greater than the stored index), and if so it translates its range for them\\n** For this to work, all internal uses of this.range need to be changed to this.getRange()\\n\\nThis'll make the fragment lazy-update its range, and we won't spend any time updating fragments that aren't being used.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366656030, 'spacePHID': None, 'dateCreated': 1366245060, 'dateModified': 1417573332, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47343', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Refuse to load for pages which are redirects', 'description': {'raw': 'In advance of fixing bug 47328 (which will probably be after the July release), we need to prevent the broken behaviour outlined by C. Scott in bug 47328 comment 1 - so just refuse to load on a page which is a redirect?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=47328'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368884901, 'spacePHID': None, 'dateCreated': 1366224540, 'dateModified': 1417573279, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47329', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Report problem\" button, broken by IVStore change', 'description': {'raw': 'In ve.init.mw.Target.prototype.reportProblem, we pass an HTMLDocument to getDataFromDom(), but this function now takes two parameters, with the IVStore coming first, so it fatals with \"doc is undefined\".\\n\\nIn addition to passing in a store, we\\'ll also need to expand the returned data before transmitting it, per bug 47318.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366652317, 'spacePHID': None, 'dateCreated': 1366215060, 'dateModified': 1417573333, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47319', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way to expand data using an IVStore for transmission over the wire', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367017070, 'spacePHID': None, 'dateCreated': 1366214880, 'dateModified': 1417573297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47318', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: html/* attributes shouldn't be cloned when cloning elements\", 'description': {'raw': \"We're cloning html/data-parsoid which Subbu tells me messes with selser correctness\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366652364, 'spacePHID': None, 'dateCreated': 1366155600, 'dateModified': 1417573333, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47297', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"mw.loader.using should not throw an exception when an optional module doesn't exist\", 'description': {'raw': 'To give an example:\\nmediawiki.page.ready.js runs on mobile (it specifies targets=>mobile) however attempts to lazy load the tablesorter plugin which is not available on mobile (it specifies targets=>desktop)\\n\\nThis currently throws an exception.\\n\\nAvoiding a bike shedding conversation about whether jquery.tablesorter should be available on mobile, it is wrong to make the assumption that a module will always be available.\\n\\nExpected: Instead of seeing an exception I would like to allow the user to handle the error themselves - allowing optional modules to die silently.\\n\\ne.g.\\nmw.loader.using( \\'jquery.tablesorter\\', function () {\\n\\t$sortableTables.tablesorter();\\n}, function( e ) {\\nthrow e;\\n});\\n\\nor \\nmw.loader.using( \\'jquery.tablesorter\\' ).done( function () {\\n\\t$sortableTables.tablesorter();\\n});\\n\\nAnother example of this being a problem is on the edit page which asumes mediawiki.action.edit is available:\\n\\nmw.loader.using(\"mediawiki.action.edit\"\\n\\nCurrently there is a hack in MobileFrontend to get around this [1]\\n\\n\\n[1] https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/MobileFrontend.git;a=blob;f=includes/skins/SkinMobile.php;h=27ab4ef44fc138566bbf3e1ab32cd5af20daf246;hb=HEAD#l241\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383254422, 'spacePHID': None, 'dateCreated': 1366152300, 'dateModified': 1383254422, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47296', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve.getHash custom hashes are double-hashed', 'description': {'raw': \"Our current setup for custom hashing objects to to give them a method .getHash() which looks like this:\\n\\nT.prototype.getHash = function () {\\n  var someSubsetOfT = // code here\\n  return ve.getHash( someSubsetOfT );\\n}\\n\\nand to invoke we use\\n\\n ve.getHash( instanceOfT );\\n\\nHowever ve.getHash( instanceOfT ) === ve.getHash( ve.getHash( someSubsetOfT ) )\\nwhich isn't really what we want.\\n\\nOne solution would be to rename getHash to getHashableObject (or something) and have it return just someSubsetOfT directly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1365506219, 'spacePHID': None, 'dateCreated': 1365087000, 'dateModified': 1417573336, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46895', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting two paragraphs inside another paragraph results in the original paragraphs being separated by a blank paragraph', 'description': {'raw': 'e.g. inserting <p>c</p><p>d</p> into <p>ab</p> between a and b results in\\n\\n<p>a</p><p>c</p><p></p><p>d</p><p>b</p>\\n\\nThis is because fixUpInsertion fixes c & d separately and after inserting c (by closing out a) it decides to re-open the paragraph it closed (sensible), but the d comes along as splits that new paragraph (not sensible), resulting in a blank paragraph between the two.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366927098, 'spacePHID': None, 'dateCreated': 1364923620, 'dateModified': 1417573331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46800', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting content at start/end of paragraph leaves leading/trailing empty paragraph', 'description': {'raw': \"e.g. inserting a <p>Bar</p> into <p>Foo</p> after the last 'o' results in:\\n\\n<p>Foo</p><p>Bar</p><p></p>\\n\\nThe original paragraph is split, then the Bar is inserted, then the paragraph is reopened again.\\n\\nOr in transaction terms:\\n\\ninsert: '<p>Bar</p>'\\n\\ncoverts to\\n\\ninsert: </p><p>Bar</p><p>'\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367020450, 'spacePHID': None, 'dateCreated': 1364923440, 'dateModified': 1417573296, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46799', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Store rendered html of MW aliens in index-value store, hashed on parameters', 'description': {'raw': 'This is in preparation for performing transactions on templates and having to update the html asynchronously.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366130654, 'spacePHID': None, 'dateCreated': 1364316180, 'dateModified': 1417573336, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46571', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create meta item for defaultsort', 'description': {'raw': 'If Parsoid has a meta thing for defaultsort that is\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367275111, 'spacePHID': None, 'dateCreated': 1363989120, 'dateModified': 1417573295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46465', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Over-eager link inspector suggestion tool inhibits linking', 'description': {'raw': 'I am just trying at w:en:Vojníkov hyperlink from \"Louka\" to \"Louka (village)\". The actual link is incorrect. Using VisualEditor and FF 19.0 or G Chrome 25.0.1364.152 m. If I start to type \"Louka\" it adds \"Loukas Vyntra\" automaticaly. If I use backspace it allows me to delete \"Vyntra\" and when I delete \"s\" of \"Loukas\", it adds again \"Loukas Vyntra\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367548440, 'spacePHID': None, 'dateCreated': 1362608460, 'dateModified': 1417573292, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45807', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deploy to the Hebrew Wikipedia as an opt-in for testing', 'description': {'raw': \"VisualEditor should be deployed to the Hebrew Wikipedia as soon as possible. I did some basic testing on my machine, and I see that it's more or less as functional as it is on the English - basic formatting works, and even basic RTL is correct.\\n\\nObviously, there are many RTL issues to test there. I am doing such testing myself every now and then, but letting more people test will be far more beneficial.\\n\\nOf course, I am talking about a dark launch at this point - it should only be available to users who specifically request it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366909636, 'spacePHID': None, 'dateCreated': 1362513780, 'dateModified': 1366913248, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45749', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'IndexPager::buildQueryInfo (contributions page unfiltered) query needs tuning', 'description': {'raw': \"**Author:** `afeldman`\\n\\n**Description:**\\nThe FORCE INDEX provided in this query results in a /much/ slower query plan than without.  This is the case with both MySQL 5.1-facebook, and MariaDB 5.5, so it should just be removed.\\n\\nQuery:\\n\\nSELECT /* IndexPager::buildQueryInfo (contributions page unfiltered) user */  rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,user_name,page_namespace,page_title,page_is_new,page_latest,page_is_redirect,page_len,ts_tags  FROM `revision` FORCE INDEX (user_timestamp) INNER JOIN `page` ON ((page_id = rev_page)) LEFT JOIN `user` ON ((rev_user != 0) AND (user_id = rev_user)) LEFT JOIN `user_groups` ON ((ug_user = rev_user) AND  ug_group = 'bot') LEFT JOIN `tag_summary` ON ((ts_rev_id=rev_id))  WHERE (rev_user >18370655) AND (ug_group IS NULL) AND ((rev_deleted & 4) = 0) AND (rev_timestamp<'20130301192103')  ORDER BY rev_timestamp DESC LIMIT 51;\\n\\nTimes of the query as above:\\n\\nproduction enwiki master - mysql 5.1-facebook:  51 rows in set (7 min 23.03 sec) \\nmariadb 5.5.29:  51 rows in set (1.29 sec)\\n\\nTimes with the FORCE INDEX (user_timestamp) removed\\nproduction enwiki master - mysql 5.1-facebook:  51 rows in set (0.26 sec)\\nmariadb 5.5.29:  51 rows in set (0.20 sec)\\n\\nThe EXPLAIN without the FORCE INDEX looks worse on 5.1 without than with, based on number of rows examined, but it avoids a filesort.  It looks better without the FORCE INDEX on mariadb than mysql 5.1 with or without.  In both cases, rev_timestamp is used instead of user_timestamp.\\n\\n--------------------------\\n**Version**: 1.21.x\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386216223, 'spacePHID': None, 'dateCreated': 1362175380, 'dateModified': 1602870085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45619', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: 'generated' property should not be preserved when unwrapping\", 'description': {'raw': 'When we unwrap lists, we currently preserve the internal \\'generated\\' property on paragraphs inside those lists, but we really shouldn\\'t. The fact that we don\\'t currently clear this when unwrapping results in the following serious bug:\\n\\n1. Create a page with the following content\\nFoo\\nBar\\n* Baz\\n* Quux\\n* Whee\\nYay\\n2. Open the page in VE\\n3. Select across the three list items and click the list button to unlist them\\n4. VE now shows five paragraphs\\n5. Click \"Review and save\" and observe the diff.\\n\\nExpected diff: the asterisk and space before \"Baz\", \"Quux\" and \"Whee\" are removed.\\n\\nActual diff: the second line becomes \"BarBazQuuxWhee\", followed by three blank lines, then \"Yay\".\\n\\nThis happens because the converter unwraps paragraphs with the \\'internal\\': { \\'generated\\': \\'wrapper\\' } property, even if these paragraphs now appear in a different context and even if there are multiple such paragraphs adjacent to each other.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363139748, 'spacePHID': None, 'dateCreated': 1362090720, 'dateModified': 1417573342, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45590', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: You cannot create pre-formatted blocks spanning multiple lines', 'description': {'raw': '1. Create a document \"First line.Second line\"\\n2. Select this text and insert a newline between the \\'.\\' and the \\'S\\' (currently, using the Enter key).\\n\\nExpected result: a single <pre> block with a single newline after the full stop, converting to \" First line.\\\\n Second line\" in wikitext. Note that this is trivially-obvious on MW Vector due to the \"border: 1px dashed #2f6fab;\".\\n\\nActual result: two separated <pre> blocks (with a slug between them), converting to \" First line.\\\\n\\\\n Second line\" in wikitext.\\n\\nI presume that we\\'ll want to retain Enter as a break-me-out-of-this-context newline, and use Shift-Enter to allow insertion of the above.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361841038, 'spacePHID': None, 'dateCreated': 1361768160, 'dateModified': 1417573343, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45344', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Split out MediaWiki-specific dm stuff into a separate directory', 'description': {'raw': 'Stuff like ve.dm.MWInternalLinkAnnotation , ve.dm.modelRegistry.registerExtensionSpecificType( /^mw:/ ), etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372875470, 'spacePHID': None, 'dateCreated': 1361572320, 'dateModified': 1417573147, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45295', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing in a section causes changes elsewhere to be deleted (Parsoid selser bug?)', 'description': {'raw': 'Changes made in screen\\n\\nIssues of editing when making changes in a section of https://en.wikipedia.org/wiki/William_Francis_Magie - probably Parsoid selser issue. JDF to re-check when new Parsoid deployed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10305}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366396637, 'spacePHID': None, 'dateCreated': 1361474460, 'dateModified': 1366396637, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45245', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create isolate method in SurfaceFragement', 'description': {'raw': 'The method should isolate a selection of siblings from the siblings either side of it by creating close/open tags with either side of it where necessary.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363280996, 'spacePHID': None, 'dateCreated': 1361474340, 'dateModified': 1417573342, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45243', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove all code related to change markers', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367527194, 'spacePHID': None, 'dateCreated': 1360974360, 'dateModified': 1417573294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45061', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support transactions on metadata', 'description': {'raw': \"In order to implement a category editor, we'll need to be able to process transactions on metadata.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360891883, 'spacePHID': None, 'dateCreated': 1360890960, 'dateModified': 1417573347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45029', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Wikitext preview doesn't refresh in new page creation mode\", 'description': {'raw': '1. Load a new (i.e. not currently existing) page into VE\\n2. Type some text\\n3. Click \"Review and save\". The corresponding wikitext appears in a flyout\\n4. Close the flyout using the up arrow\\n5. Change the text in the editor\\n6. Click \"Review and save\" again.\\n\\nThe flyout that appears in #6 will display the same wikitext as in #3, even though you changed the document. The diff flyout handles this correctly (i.e. it caches the old diff until you change something), but the serialization flyout for new page creation never clears its cache.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360878886, 'spacePHID': None, 'dateCreated': 1360878660, 'dateModified': 1417573347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45021', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parsoid selective serialisation failure when deleting an LI (artefact of old version of Parsoid?)', 'description': {'raw': \"**Author:** `phil`\\n\\n**Description:**\\nshows the result after a save with 'friend' being duplicated\\n\\nText was several lines long\\nPlaced cursor at start of last line\\nPressed delete to move the line up to the same line as the second to last\\nSaved\\nThe last line has not been deleted and it also present on the second to last\\n\\nScreenshot attached\\nThis\\nis\\nthe\\nend\\nmy\\nfriend\\n\\n- put cursor at start of friend and pressed delete and then added a space\\n\\nScreenshot shows the result, 'friend' is now in twice\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10875}\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366396569, 'spacePHID': None, 'dateCreated': 1360124400, 'dateModified': 1366396569, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44702', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copy and paste at end of text loses some of copied text on save (Parsoid issue?)', 'description': {'raw': \"**Author:** `phil`\\n\\n**Description:**\\nPage after cut and paste of 'a b c' only showing the 'a'\\n\\nCreated a simple file\\na\\nb\\nc\\n\\nCopied all the text, placed the cursor after the 'c' and pasted it\\nThe 'a' from the copy was pasted, the 'b' and 'c' were lost\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10869}\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366396479, 'spacePHID': None, 'dateCreated': 1360122240, 'dateModified': 1417573334, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Template creating CSS in a table's cell does not come through\", 'description': {'raw': 'Screenshot\\n\\nWhen edited in VisualEditor, the following table:\\n\\n```\\n{| class=\"wikitable\"\\n|- \\n! Header\\n|-\\n| {{Yes}}\\n|}\\n```\\n... shows the following string in place of the {{Yes}} template:\\n\\nstyle=\"background: #90ff90; color: black; vertical-align: middle; text-align: center; \" class=\"table-yes\"|Yes\\n\\ufeff\\nSee screenshot.\\nLive at http://en.wikipedia.org/wiki/User:Nicolas1981/Sandbox\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50589\\n\\n**Attached**: {F10493}'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377186266, 'spacePHID': None, 'dateCreated': 1359530280, 'dateModified': 1598460414, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44498', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parsoid/aliens combinations causes data to be over-written on save', 'description': {'raw': 'diff about to delete existing text\\n\\nI\\'ve seen this a few times and I think this is the simplest reproduction. \\n\\nStart with a page that has a line of text \"this text should be preserved but is not\"\\n\\nIn VE, position the cursor at the front of the line and move it two spaces down. \\n\\nMove the cursor back to the top of the page. \\n\\nType a new line \"totally different stuff\"\\n\\nSave.  Note the incorrect diff. The string \"this text should be preserved but is not\" has been deleted erroneously upon save.  \\n\\nRepeat the operation but this time use strings that share words, like \"this text should be preserved\" and \"this text is new\"\\n\\nThe behavior is the same, the old text is erroneously deleted, but the diff seems to have intertwined the two strings, keeping their common elements.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=User:Cmcmahon(WMF)&oldid=535559576\\n\\n**Attached**: {F10454}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366396947, 'spacePHID': None, 'dateCreated': 1359488700, 'dateModified': 1366396947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44479', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Pre-save diff for new pages doesn't alter when aborted and restarted\", 'description': {'raw': 'Go to a new page. Enter some content. Press review-and-save. Observe diff. Press the \"leave this context\" button (\"^\"). Change the content. Press review-and-save again. Observe diff.\\n\\nExpectation: The diff shows the changes against the new content.\\nReality: The diff shows the changes against the original content (not re-done).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368043283, 'spacePHID': None, 'dateCreated': 1359415380, 'dateModified': 1417573289, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44446', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Implement TemplateData extension and get it deployed for the Template Inspector', 'description': {'raw': 'For the forthcoming Template Inspector to work, we will need a way to \"hint\" for the Inspector how the parameters of the VE should be used - we\\'re intending for now for this to be a template-hinting extension that allows editors to specify in the wikitext source what the parameters are called and how they should be used, akin to the Template documentation template on Commons.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369075541, 'spacePHID': None, 'dateCreated': 1359413640, 'dateModified': 1417573225, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44444', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Oddness repetition/wrong diff (from Parsoid?) on save with some funky markup', 'description': {'raw': 'empty review pane, should show heading markup for non-Latin string\\n\\nUsing a string like \"āæǣ\" or special characters like \"☺☻♥♦\"\\n\\nHighlight the string in VE\\nChoose \"Heading 1\"\\n\\nVE displays the string larger, as expected\\n\\nClick \"Review and save\"\"\\n\\nNote that review pane is empty, see screen shot. \\nClick \"Looks good to me\" and finish saving. \\n\\nThe non-Latin string has not been affected and the Heading not been applied. \\n\\nNote that normal ASCII latin strings work fine. \\nAlso note that the regular editor applies the Heading markup to non-latin strings correctly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=User:Cmcmahon(WMF)&oldid=535414434\\n\\n**Attached**: {F10377}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366414342, 'spacePHID': None, 'dateCreated': 1359412320, 'dateModified': 1485133574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44442', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Handle Parsoid error messages and codes sanely', 'description': {'raw': \"VE gets some error codes and messages from Parsoid, but not a lot. I'm expanding that a little bit in a new patch [0], and it would be cool if VE could handle the errors I've added.\\n\\n401: Unauthorized: Should be handled as a user-visible error. Usually this means that the API isn't readable by anonymous users, but could be later used for something else. The text of the HTTP response has details about the error, so showing that to the user might be an OK solution.\\n\\n404: Not found: Usually means that we couldn't find anything for the article you're trying to parse or serialize. This shouldn't usually happen, but when it does, it *probably* means that the interwiki isn't set properly. Maybe hint that the user should compare their localsettings.js file to the example.\\n\\n500: Server error: This is a catch-all, but we'll send as much information as we can in the text of the HTTP response. Showing the user the text would go a long way towards more useful bug reports (I currently see roughly 4 suggested duplicates that have roughly the same summary....differentiating them might be helpful)\\n\\nThese are all implemented in js/lib/mediawiki.ApiRequest.js in functions that inherit from the native Error object, so you can read it if you don't want to take my word for it.\\n\\nWe could implement other error codes as we see cases that require them, but these are the big three. And of course 200 is the main success code.\\n\\nWe might also be able to use some of the 3xx codes to represent redirects, but I'm not sure it would be totally useful. File a bug against Parsoid if it would be :)\\n\\n[0] https://gerrit.wikimedia.org/r/45794\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=43147\"}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1362522586, 'spacePHID': None, 'dateCreated': 1359142560, 'dateModified': 1417573343, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44354', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve.dm.SurfaceFragment.wordBoundaryPattern treats non-lower-ASCII word characters as boundaries', 'description': {'raw': 'See http://inimino.org/~inimino/blog/javascript_cset for some work in this area.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1365440622, 'spacePHID': None, 'dateCreated': 1358469000, 'dateModified': 1417573336, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44085', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Insertion tools (link inspector, media inserter, reference, reference list, …) don't work in slugs\", 'description': {'raw': \"Related to bug 44083\\n\\nBecause there is not yet a paragraph to insert content in, the link inspector won't be able to insert the new link text into a slug, even if bug 44083 is fixed.\\n\\nThe solution is probably to make the automatic paragraph insertion code in ve.ce.Surface.handleInsert more generic and moving it into ve.dm.SurfaceFragment.insertContent, triggered when inserting at a slug location.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=44083\"}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372462623, 'spacePHID': None, 'dateCreated': 1358467500, 'dateModified': 1417573152, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44084', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Placing the cursor in a slug doesn't cause a contextChange event\", 'description': {'raw': '1. Make an article that begins with an alien followed by a paragraph with some text\\n2. Click on a word in the paragraph\\n3. Click on the slug\\n4. Press the link button\\n5. See that rather than the link inspector knowing to begin inserting a new link inside the slug, it inspects the word you clicked on in the paragraph.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=44084\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50141'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383060862, 'spacePHID': None, 'dateCreated': 1358467260, 'dateModified': 1417573135, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44083', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Key commands should be \"platform-able\".', 'description': {'raw': 'Key commands should be able to vary based on language/locale and platform. E.g. toggling something as Bold could be:\\n\\n* Ctrl + b (Windows, English)\\n* Cmd  + b (Mac OS X, English)\\n* Meta + b (Solaris, English)\\n\\n* Ctrl + f (Windows, German)\\n* Cmd  + f (Mac OS X, German)\\n* Meta + f (Solaris, German)\\n\\n... etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=42919'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358469781, 'spacePHID': None, 'dateCreated': 1358279820, 'dateModified': 1417573351, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up canHaveGrandchildren mess', 'description': {'raw': '\"Can have grandchildren\" is a misnamed check that should be cleaned up. What it really appears to mean is \"is this a non-content-containing branch node\", given that it checks that the node can have children, is not content, and is not a content container.\\n\\ncanHaveGrandchildren seems to still be used in some places, it should be renamed and documented adequately.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363626201, 'spacePHID': None, 'dateCreated': 1357966200, 'dateModified': 1417573341, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43893', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Browser back button should work as expected', 'description': {'raw': 'We should use pushState such that pressing the back button after clicking VisualEditor takes you back to read mode.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397067880, 'spacePHID': None, 'dateCreated': 1357863540, 'dateModified': 1417572493, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43844', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: When the diff result is null (no changes), don't show a confusing blank diff but instead a message\", 'description': {'raw': 'When the diff result is null (no changes), don\\'t show a confusing blank diff but instead a message like \"There are no changes detected in your edit\" so that users aren\\'t confused.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368575229, 'spacePHID': None, 'dateCreated': 1357693440, 'dateModified': 1417573283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43754', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Whitespace preservation for list items not working', 'description': {'raw': \"For whatever reason (may be a bug in the DM, or in the seralizer, or in selser), whitespace preservation didn't work in this edit https://en.wikipedia.org/w/index.php?title=International_Air_Transport_Association_airport_code&diff=530666305&oldid=526301045 . The whitespace changes didn't show in the initial diff I was asked to verify, only in the final change.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366206699, 'spacePHID': None, 'dateCreated': 1356989040, 'dateModified': 1417573286, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43543', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: JS TypeError when Parsoid returns an error', 'description': {'raw': \"Steps to reproduce issue:\\n* Load VisualEditor on a page where the server will return in error\\n  (to simulate, call mw.loader.load('ext.visualEditor.viewPageTarget') from the console on a page where VE is not enabled, e.g. the Manual namespace on mw.org)\\n* Click Cancel on the server error alert()\\n* Witness said error on your console.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364318463, 'spacePHID': None, 'dateCreated': 1355786940, 'dateModified': 1417573337, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43216', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Tag edits made through Special:GettingStarted', 'description': {'raw': \"**Author:** `swalling`\\n\\n**Description:**\\nOn English Wikipedia, we should add a tag (https://www.mediawiki.org/wiki/Manual:Tags) to edits made to articles chosen from Special:GettingStarted by new editors. \\n\\nWe are logging actions anonymously with EventLogging, but providing a public tag of edits made through this interface has additional advantages:\\n\\n* It will allow product managers and analysts the ability to see a real time stream of the edits\\n* It will help community members inspect the overall stream of edits, and assess them for quality\\n* It will explain to anyone who is watching a page how new editors found the article, and why they are editing it\\n* It will allow us to find and contact the new editors who use Special:GettingStarted (right now vandals are being warned, but good editors are being ignored for the most part)\\n\\nIf we're adding a tag, we should assume that most community members won't know what Special:GettingStarted is. With that in mind, I propose the following for the tag text: [[Special:Tags|Tag]]: new editor [[Wikipedia:GettingStarted|getting started]]\\n\\nThis is also appropriately agnostic to the task type (copyediting, wikifying, etc.), which is likely to change as the project evolves. You can see other tags in use on English Wikipedia at Special:Tags.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358418277, 'spacePHID': None, 'dateCreated': 1355729280, 'dateModified': 1366647325, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43191', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Inline aliens behaving incorrectly in some cases, seems to depend on selection', 'description': {'raw': 'Inline image (used as icon) is incorrectly alienated, sometimes (?).\\n\\nTest case:\\n\\nOpen https://en.wikipedia.org/wiki/User:Raymond/inline_image in VisualEditor mode:\\n\\n1. Thumbed image and inline image are alienated\\n2. Dismiss the notice bubble\\n3. Thumbed image is alienated, but inline image is NOT. It is clickable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/wiki/User:Raymond/inline_image'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360365599, 'spacePHID': None, 'dateCreated': 1355677860, 'dateModified': 1417573349, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43174', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: A slug's new contents appear not to get inserted into the DM in at least once case\", 'description': {'raw': '* Click into VE on https://en.wikipedia.org/wiki/User:Thehelpfulone/test\\n* Click cursor into one of the many LI slugs of the multiply-indented list.\\n* Type some contents into the slug\\n* Press \"left\"; suddenly, the cursor is back at 0,0\\n* Click into the ultimate LI with \"real\" content (not the one just created) and outdent repeatedly; you will over-write the new LI as if it wasn\\'t there (indeed, it never reaches the DM).\\n\\nThis may be similar to other slug bugs, given the core issue. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371171784, 'spacePHID': None, 'dateCreated': 1355530440, 'dateModified': 1417573213, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43146', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Slug oddness - Prepending text to article starting with {{Infobox ..}} removes the entire article', 'description': {'raw': 'Screenshot showing the diff and the editor\\n\\nSteps to reproduce problem:\\n* Open VisualEditor on https://en.wikipedia.org/wiki/Buri_Ram_Airport\\n* The cursor will be on top of the article in a paragraph-placeholder with bold styling (because the first word of the article is bolded)\\n* Type \"a\"\\n\\nExpected result:\\nThe character is inserted. Showing the diff now shows the addition of \"\\'\\'\\'a\\'\\'\\'\" (either above or below the {{infobox}}, doesn\\'t really matter). Preferably below so that it is next to the paragraph it was added before.\\n\\nActual result:\\nThe character is inserted. Visually nothing else changed (the infobox and the rest of the article are stil there). However, clicking \"Review and save\" now will show a diff where the infobox and the entire article have been removed and \"\\'\\'\\'a\\'\\'\\'\" was added in its place.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9591}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371063971, 'spacePHID': None, 'dateCreated': 1355443440, 'dateModified': 1417573215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43103', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Slug oddness - new text in list item before alien node is ignored', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce problem:\\n* Open VisualEditor on https://en.wikipedia.org/wiki/Buri_Ram_Airport\\n* Put cursor in the placeholder slug in the second list item of the External links. There is an alien node here as the external link is generated with a template.\\n* Type \"a\"\\n* Press \"Review and save\"\\n\\nExpected result:\\nA diff adding the letter \"a\".\\n\\nActual result:\\nEmpty diff (see attachment)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9589}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371067225, 'spacePHID': None, 'dateCreated': 1355442900, 'dateModified': 1417573214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43102', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"localStorage is null\" error message', 'description': {'raw': 'Firefox 17.0.1 and Ubuntu 12.10; using the VE causes a failure with a \"localStorage is null\" error.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361832521, 'spacePHID': None, 'dateCreated': 1355424480, 'dateModified': 1417573345, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43087', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Race condition between \"Beginning of Line\" and \"New Line\" operations', 'description': {'raw': 'Here is normal behavior:\\n\\n1. In VisualEditor, type a line of text.\\n2. Position your cursor at the beginning of that line.\\n3. Press the Home key on your keyboard, to move the cursor to the beginning of the line.\\n4. Wait a moment.\\n5. Press Enter, and the current text is pushed downward one line. This is correct and expected.\\n\\nHere is the buggy behavior:\\n\\n1. In VisualEditor, type a line of text.\\n2. Position your cursor at the beginning of that line.\\n3. VERY QUICKLY, press the Home key followed by the Enter key.\\n4. The cursor moves down one line, so it is positioned below the line of text. The text did not move. This is incorrect behavior. The line of text should have been pushed downward.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-o5tv5cyrple4fn5xqopm', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371169075, 'spacePHID': None, 'dateCreated': 1355422260, 'dateModified': 1417573213, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43082', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Select All + Delete removes all text from sight, but not internally', 'description': {'raw': '1. Using VisualEditor, edit an article that already has some text in it.\\n2. Select all text with Ctrl-A.\\n3. Press the DELETE key. All text disappears as expected.\\n4. Click \"Review and Save\". The diff shows that text is STILL PRESENT in the article.\\n5. Finish saving. You will see that text is still in the article.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-o5tv5cyrple4fn5xqopm', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371505460, 'spacePHID': None, 'dateCreated': 1355422080, 'dateModified': 1417573210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43081', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Some elements not alienated', 'description': {'raw': 'The coord template is not hatched but still visible and the links are still clickable.\\n\\nhttps://en.wikipedia.org/wiki/User:Raymond/coords\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1357678877, 'spacePHID': None, 'dateCreated': 1355413560, 'dateModified': 1417573351, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43076', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Uncaught TypeError: Cannot read property \\'left\\'  / call method \\'getOuterLength\\'.\"', 'description': {'raw': \"A couple more uncaught TypeError, a la https://bugzilla.wikimedia.org/show_bug.cgi?id=43014:\\n\\nUncaught TypeError: Cannot read property 'left' of undefined\\n\\nUncaught TypeError: Cannot call method 'getOuterLength' of undefined\\n\\nReported http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Error_loading_data_from_server:_Server_error\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364318260, 'spacePHID': None, 'dateCreated': 1355346720, 'dateModified': 1417573338, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43041', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Deletion of slugs causes significant confusion (and shouldn't be possible?)\", 'description': {'raw': 'Example Page: http://en.wikipedia.org/wiki/Ansaldo_Poggi\\n\\n1. Go to the top, click into the empty line above the ineditable image (the normally right floating image). This empty line should not exist. It can however, be deleted (press \"delete\" on the keyboard) which causes the start text to jump in front of the \"Modern Bolognese Violin-Making Table\" image.\\n\\n2. Click somewhere inside \"References\". Move the cursor with the keyboard  to the position after the \"s\". Press \"delete\" on the keyboard. The line starting with \"Tito Gotti\" will be merged with the heading (ignoring the uneditable \"references\" tag and \"cite\" template).\\n\\n3. Similar to the above: Click somewhere inside \"References\". Move the cursor with the keyboard  to the position after the \"s\". Move one more right into the (errorneously existing) empty line between the heading and the uneditable references tag. Press \"delete\" on the keyboard. The line starting with \"Tito Gotti\" will jump above the uneditable \"references\" tag and \"cite\" template.\\n\\n4. Do the same as above, i.e. go to the empty line after the References-Heading. However, this time click with the mouse into the line. Press \"delete\" on the keyboard. This time the behavior is different, nothing is deleted and the cursor jumps to the start of the article. This in itself seems again to be an error in the ordering of page objects. Now try to repeat this with different browser windows screen or zoom sizes, so that the originally, the start of the article is not visible before clicking delete. It can be seen that the focus is not updated, the cursor is outside of the visible area. Press \"delete\" again and with seeing it, parts of the text can be deleted.\\n\\n5. Do the same as above, click on line below reference with the mouse, delete once, cursor jumps to top. Do not delete again, but put the cursor again into the line below the reference heading with the mouse. This time the ineditable <references> tag is deleted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-grpjkpfolt5gz4ljlbfg', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420844082, 'spacePHID': None, 'dateCreated': 1355334540, 'dateModified': 1438734540, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43026', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor extension on test.wikipedia.org and test2.wikipedia.org for all namespaces; for NS0 and NS2 on mediawiki.org', 'description': {'raw': \"According to <https://test.wikipedia.org/wiki/Special:Version>, the VisualEditor extension is installed, but it doesn't seem to be enabled. I think VisualEditor should be enabled for all namespaces, all skins, all users, etc. on test.wikipedia.org.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367270827, 'spacePHID': None, 'dateCreated': 1355330700, 'dateModified': 1367270827, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43018', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid gives VisualEditor insecure content when using HTTPS (should use protocol-relative URLs)', 'description': {'raw': 'When I go to <https://en.wikipedia.org/wiki/User:Trevor_Parscal> and click the \"visualeditor\" tab, my browser console says:\\n\\n---\\nThe page at https://en.wikipedia.org/wiki/User:Trevor_Parscal displayed insecure content from http://en.wikipedia.org/w?title=Special:FilePath/California_Bay_Area_county_map.svg&width=.\\n---\\n\\nConsequently, the pretty green lock icon in Google Chrome turns yellow.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372119634, 'spacePHID': None, 'dateCreated': 1355327160, 'dateModified': 1372934071, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43015', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parsoid call on \"Review and save\" slide hangs for pages with \"/\"s in them', 'description': {'raw': '[Wikitech-l] Alpha version of the VisualEditor now available on the English Wikipedia\\n\\nI tried it on enwiki in my sandbox. \\n\\nIt does not work: when I want to \"Review and save\" a box pops up \"Review your changes\" --- but nothing happens.\\n\\n* MediaWiki \\t1.21wmf5 (f4a44f9)\\n* VisualEditor (Version 0.1.0) \\t(2e6425a)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ppvnwr24o32pux3le5ov', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355429392, 'spacePHID': None, 'dateCreated': 1355299800, 'dateModified': 1417573352, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42988', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Removing copy/pasted link annotations removes the original as well', 'description': {'raw': \"1. Add a link to some text\\n2. Copy the text\\n3. Paste the text somewhere else\\n4. Remove the link using the link inspector's trash icon\\n5. See that both links are gone\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355193795, 'spacePHID': None, 'dateCreated': 1355191860, 'dateModified': 1417573353, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42937', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Type mismatch when inserting unbalanced content', 'description': {'raw': '**Author:** `orbit`\\n\\n**Description:**\\nSteps to reproduce:\\n1. Copy part of a headline and part of a following paragraph\\n2. Paste into a paragrah\\n\\nThe linmod being inserted will look something like this:\\n[\"s\", \"u\", \"m\", \"?\", Object, Object, \"C\", \"o\", \"n\", \"t\"]\\n\\nThe objects are closing heading and opening paragraph.\\n\\nThe error is in ve.dm.Document.js on 1145.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354916275, 'spacePHID': None, 'dateCreated': 1354837920, 'dateModified': 1417573355, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42806', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting across inline alien errors', 'description': {'raw': '**Author:** `orbit`\\n\\n**Description:**\\nTry creating \"some text <inlinealien>blah</inlinealien> more text\" and select across the inline alien and delete. \\n\\nUncaught TypeError: Cannot call method \\'getDataFromNode\\' of undefined\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354739553, 'spacePHID': None, 'dateCreated': 1354669260, 'dateModified': 1417573358, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42707', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace over a slug at the end of the document throws an error', 'description': {'raw': 'Pressing backspace in a slug at the end of the document throws an error:\\n\\n* Create a new page (or go to an existing one), and enter \"ABCD\\\\n\" at the end\\n* With the cursor in the new slug, press backspace; this throws an error:\\n\\nUncaught Error: ve.dm.Document.getNodeFromOffset(): offset 9 is out of bounds\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354755508, 'spacePHID': None, 'dateCreated': 1354563780, 'dateModified': 1417573358, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42657', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link inspector doesn't close when moving cursor to a different link\", 'description': {'raw': 'Inspect a link, then click on a different link, the inspector moves to the new cursor location and remains open.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354227540, 'spacePHID': None, 'dateCreated': 1354217520, 'dateModified': 1417573392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42552', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save dialog triggers error (selection bug?)', 'description': {'raw': \"On launching the save dialog, a console error is thrown:\\n\\nUncaught TypeError: Cannot read property 'nodeType' of null /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:117\\nve.ce.getOffset /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:117\\nve.ce.SurfaceObserver.poll /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:136\\nve.ce.SurfaceObserver.stop /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:82\\nve.ce.Surface.documentOnBlur /w/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js:324\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354155569, 'spacePHID': None, 'dateCreated': 1354155360, 'dateModified': 1417573392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42525', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Integrate edit conflict confirmation into the save dialog', 'description': {'raw': 'As of I002c5aa23704c1c46ef46fa1970a4254614b9eb1 when saving and an edit conflict occurs the user is shown a browser-provided confirmation box which allows them to either cancel or resolve the conflict manually.\\n\\nIt would be much better if this was integrated into the save dialog.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368574606, 'spacePHID': None, 'dateCreated': 1354147200, 'dateModified': 1417573284, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42522', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"mediawiki.Uri crashes in pages with '@' in their url\", 'description': {'raw': \"It isn't just that this would throw an exception:\\n\\n new mw.Uri('http://krinkle.dev/mediawiki/alpha/index.php?title=VisualEditor:S@box&action=edit');\\n\\nAlthough that is also bad (when done on non-@ pages), it is especially bad that on pages containing an @ in the url, the module won't even finish loading because of this line:\\n\\n defaultUri = new Uri( documentLocation );\\n\\nSo instead, mw.Uri stays undefined.\\n\\n--------------------------\\n**Version**: 1.19\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358621587, 'spacePHID': None, 'dateCreated': 1354127040, 'dateModified': 1358706140, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42513', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Converter crashes if a page has a <span> element with a <p> elements', 'description': {'raw': \"Wikitext to reproduce:\\n\\n<span>\\n[bunch of newlines]\\n</span>\\n\\nParsoid generates <span><p></p></span> for this, but it doesn't mark the span.\\n\\nTodo:\\n* Make the failure a bit more graceful\\n* Investigate whether p inside span is legal\\n* Investigate other cases where this breakage occurs\\n* File bug with Parsoid for proper protection of user-generated tags\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354826179, 'spacePHID': None, 'dateCreated': 1354071720, 'dateModified': 1417573357, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42487', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Still get a pawn when select-all->replace in Firefox', 'description': {'raw': 'Go to demos/ve/?page=aliens in Firefox; select all:\\n\\n  TypeError: end is undefined    ve.ce.Surface.js (line 980)\\n\\nPress \"a\" (or backspace and then \"a\"):\\n\\n  TypeError: start is undefined  ve.ce.Surface.js (line 995)\\n  \\n  (And a pawn appears in its own <p> above the a.)\\n\\nOn any click thereafter,\\n\\n  TypeError: node is null        ve.ce.Surface.js (line 1073)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57355'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353971144, 'spacePHID': None, 'dateCreated': 1353725160, 'dateModified': 1417573198, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42404', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selective serialisation has landed in Parsoid, now VE needs to handle that', 'description': {'raw': \"Due to gerrit 31118 being merged, Parsoid now has selective serialisation live. This means that VisualEditor needs to include Mark's patch to handle this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354056676, 'spacePHID': None, 'dateCreated': 1353721680, 'dateModified': 1417573394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42403', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Failure in saving integration code', 'description': {'raw': 'this.emit( \\'saveError\\', null, \\'Unsuccessful request: \\' + data.result, null );\\n\\n(ve.init.mw.Target.js line 131)\\n\\ncauses \"TypeError: data is undefined\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353724364, 'spacePHID': None, 'dateCreated': 1353719400, 'dateModified': 1417573398, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42402', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up meta nodes', 'description': {'raw': \"For after December:\\n* consolidate 'type': 'metaInline' / 'metaBlock' into 'type': 'meta'\\n* get rid of ve.{ce,dm}.Meta{Inline,Block}Node\\n* create ve.dm.MetaNode with converter stuff but don't inherit ve.dm.LeafNode\\n** eventually integrate that into the new node API\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1357679596, 'spacePHID': None, 'dateCreated': 1353702180, 'dateModified': 1417573333, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42398', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Delete and backspace broken around inline aliens in Firefox', 'description': {'raw': 'When I place the cursor before the template output, and press \"Delete\", it deletes the template and one more character after the template. When I place the cursor after the template output and press \"Backspace\", it does not delete the template (simply does nothing).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354149956, 'spacePHID': None, 'dateCreated': 1353576600, 'dateModified': 1417573393, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42350', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector suggestions box should instantly show, then populate with more as API returns', 'description': {'raw': \"Right now the link inspector's suggestions box displays only after the ; instead, it should show instantly, then populate with more data as API returns with a spinner. Trevor has some ideas if you want to bug him. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354302320, 'spacePHID': None, 'dateCreated': 1353543420, 'dateModified': 1417573392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42341', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Annotation of inline nodes fails', 'description': {'raw': 'Annotation of inline nodes fails - the data model is not updated to have any annotations added.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354056502, 'spacePHID': None, 'dateCreated': 1353542940, 'dateModified': 1417573394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42340', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Handle percent-encoding in MWInternalLinkAnnotation', 'description': {'raw': \"Per conversation with Gabriel, MWInternalLinkAnnotation needs to deal with percent-encoded hrefs. At least question marks (?) and percent signs (%) will be encoded. We need to decode these before presenting them to the user, encode the user input on the way out, and use href shadowing to make sure we don't change the href if the user didn't change the target (even if that would otherwise happen due to complete vs partial percent-encoding).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354921807, 'spacePHID': None, 'dateCreated': 1353441780, 'dateModified': 1417573354, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42298', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking link toolbar button with zero-length selection makes UI go crazy', 'description': {'raw': '...presumably because the link becomes a pre-annotation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353971422, 'spacePHID': None, 'dateCreated': 1353376740, 'dateModified': 1417573396, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42275', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Provide a way of users seeing the edit-notices and page protection level warnings as they're editing\", 'description': {'raw': \"From Max's bug 42142\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=42142\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354317270, 'spacePHID': None, 'dateCreated': 1353122280, 'dateModified': 1417573390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42220', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Trivial way to get a lot of errors', 'description': {'raw': '1. Go to https://www.mediawiki.org/wiki/VisualEditor:Testy and click edit\\n2. Select all using Ctrl-A (or Cmd-A) and press backspace\\n3. Press any content key (e.g. \"a\")\\n\\nWhat should happen:\\n\\n: You get a document with an \"a\" in its own paragraph.\\n\\nWhat does happen:\\n\\n: You get a document with an \"a\" in its own paragraph, and two console errors:\\n\\nTypeError: this.data[offset] is undefined\\n\\n...ation)===false){return null;}while(start>0){start--;if(this.offsetContainsAnnota...\\n\\nload.p...4105Z&* (line 89)\\n\\n\\nTypeError: this.data[offset] is undefined\\n\\n...ation)===false){return null;}while(start>0){start--;if(this.offsetContainsAnnota...\\n\\nload.p...4105Z&* (line 89)\\n\\n\\nThereafter, pressing return in the new context gives:\\n\\nTypeError: node is null\\n\\n...ve.Node.call(this,type);this.model=model;this.$=$element||$(\\'<div>\\');this.parent...\\n\\nEtc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353541840, 'spacePHID': None, 'dateCreated': 1353120840, 'dateModified': 1417573397, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42219', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Trivial way to get a pawn (♙) appearing', 'description': {'raw': '1. Go to https://www.mediawiki.org/wiki/VisualEditor:Testy and click edit\\n2. Select all using Ctrl-A (or Cmd-A) and press backspace\\n3. Press any content key (e.g. \"a\")\\n\\nWhat should happen:\\n\\n: You get a document with an \"a\" in its own paragraph.\\n\\nWhat does happen:\\n\\n: You get a document with an \"a\" in its own paragraph, and a pawn.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353138404, 'spacePHID': None, 'dateCreated': 1353120720, 'dateModified': 1417573400, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42218', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting text content around inline alien nodes throws an exception', 'description': {'raw': \"Specifically it fails when trying to insert text content between two inline aliens or after last inline alien inside its parent.\\n\\nException:\\nUncaught TypeError: Cannot read property 'start' of undefined ve.dm.TransactionProcessor.js:259\\nve.dm.TransactionProcessor.processors.replace\\n\\n// Set change markers on the parents of the affected nodes\\nfor ( i = 0; i < selection.length; i++ ) {\\n\\tthis.setChangeMarker(\\n\\t\\tselection[i].parentOuterRange.start + this.adjustment,\\n\\t\\t'content'\\n\\t);\\n}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353366778, 'spacePHID': None, 'dateCreated': 1353106740, 'dateModified': 1417573398, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42212', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Sync availability of \"minor edit\" with MW backend', 'description': {'raw': 'Currently when using VisualEditor to create a new page, the \"Save page\" dialog box offers two checkboxes below the edit summary field: \"This is a minor edit\" and \"Watch this page\".\\n\\nWhen creating a page, \"This is a minor edit\" does not typically show up. It\\'s a bug that the checkbox appears when creating a page with the VisualEditor interface.\\n\\nThis bug is closely related to bug 40774.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354565365, 'spacePHID': None, 'dateCreated': 1352957280, 'dateModified': 1417573389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42137', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Floated nodes don't get shields in Chrome\", 'description': {'raw': 'If you have a floated table inside an alien, it gets a shield (and a phantom) in Firefox but not in Chrome. This is because the table is floated with external CSS triggered by class=\"infobox\", rather than an inline style attribute. At the time when we check for $this.css(\\'float\\'), $this hasn\\'t been attached to the main DOM yet. Firefox computes styles on unattached nodes correctly, but Chrome doesn\\'t.\\n\\nThe solution is to wait until after the entire CE rendering has been built and attached to the DOM before generating shields and phantoms. Possible implementations:\\n\\n1. Add an onAttach function to ce.Node. After attaching, traverse the entire CE tree and invoke onAttach() on every node (bottom up). This is expensive, though, because you have to traverse the entire tree just to invoke onAttach on the few nodes that use it.\\n\\n2. Make the ce.Surface throw an \\'attached\\' event after attaching to the DOM, and make the ce.AlienBlockNode constructor listen for this event. This is not as clean, but more efficient, because only nodes that need processing are processed.\\n\\nI have a slight preference for #2, but I can be convinced either way.\\n\\nIn both cases, the call to onUpdate() in the ce.AlienBlockNode constructor would be removed, otherwise the HTML would be set twice.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353018780, 'spacePHID': None, 'dateCreated': 1352948940, 'dateModified': 1417573399, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42134', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Spinner keeps spinning after save fail', 'description': {'raw': 'If you try to save a page and it fails (e.g. because of an edit conflict, blocked user, Parsoid down, or whatever), then click Cancel, the spinner keeps spinning and the Save page button remains greyed out.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354054812, 'spacePHID': None, 'dateCreated': 1352940660, 'dateModified': 1417573395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42125', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paragraph generated for an empty document should not be unwrapped on the way out', 'description': {'raw': \"Currently, the DOM->data converter generates an empty paragraph if the input is an empty string. This paragraph is marked with .internal.generated=='wrapper', so it's unwrapped on the way out. This is bad because we lose change markers that way, and have no way to propagate them.\\n\\nInstead, it should use another generated marker which causes the paragraph to be unwrapped only if it is empty, and be preserved if it's not empty.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353123761, 'spacePHID': None, 'dateCreated': 1352938920, 'dateModified': 1417573396, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42121', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Converter should inline-alienate inline tags in wrapping mode even in the mw:unrecognized case', 'description': {'raw': 'Normally, unrecognized tags in wrapped blocks are alienated as inline or block depending on the tag name. This is broken for tags with unrecognized mw: types (and for about groups), which are always alienated as block when in wrapping mode.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353386649, 'spacePHID': None, 'dateCreated': 1352938680, 'dateModified': 1417573398, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42119', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Replaced Edit tab should use original label instead of fetching message \"edit\" msg', 'description': {'raw': 'When loading a page with VE enabled, the \"edit\" tab is changed from the \"vector-view-edit\" message to the \"edit\" message. This is apparent on enwiki, where these messages have different values. It\\'s also apparent when using ?uselang=qqx\\n\\nThis shouldn\\'t happen, the message for the edit tab should be consistent.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1365036328, 'spacePHID': None, 'dateCreated': 1352937420, 'dateModified': 1417573337, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42117', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Change marking branch appears to be live on MWwiki', 'description': {'raw': 'Possibly the wrong version of Parsoid updated? See https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=next&oldid=604180 as an example of \\'<p data-ve-changed=\"[...]\">\\' elements being created.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352939134, 'spacePHID': None, 'dateCreated': 1352858220, 'dateModified': 1417573400, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42092', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: A wild pawn character appeared!', 'description': {'raw': \"Roan told me that, if I ever saw one of your comical placeholder Unicode characters, that it was a pretty well-defined bug. So here:\\n\\n1. Create an unordered list\\n2. Enter some items\\n3. Hit enter twice\\n4. Type something\\n\\nExpected: Whatever I typed should appear on the screen.\\n\\nActual: Pawn character! It also prints my text, but only after '♙\\\\n'.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354656971, 'spacePHID': None, 'dateCreated': 1352856780, 'dateModified': 1417573359, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42091', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In bullet list, SHIFT-LEFT selection reseted when reaching deeper item', 'description': {'raw': 'Steps to reproduce:\\n1) Open http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Press \"Edit\"\\n3) Click at the end of an item in the big list at the bottom of the page.\\n4) Press SHIFT and LEFT, maintaining them pressed for a while\\n\\nExpected behavior: Text is selected as long as SHIFT-LEFT is pressed\\nActual behavior: Text is selected until deeper-level bullet is reached. When it is reached, the previous selection is unselected, and a new selection starts.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354222673, 'spacePHID': None, 'dateCreated': 1351564200, 'dateModified': 1417573390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41527', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: ve.ce throws Uncaught TypeError: Cannot read property 'nodeType' when suface loses focus\", 'description': {'raw': \"In Chrome, when I click inside the editor, then right-click outside the editor, I get an exception:\\n\\n\\nUncaught TypeError: Cannot read property 'nodeType' of null /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:118\\nve.ce.getOffset /w/extensions/VisualEditor/modules/ve/ce/ve.ce.js:118\\nve.ce.SurfaceObserver.poll /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:135\\nve.ce.SurfaceObserver.stop /w/extensions/VisualEditor/modules/ve/ce/ve.ce.SurfaceObserver.js:81\\nve.ce.Surface.documentOnBlur /w/extensions/VisualEditor/modules/ve/ce/ve.ce.Surface.js:322\\nproxy l.php:775\\njQuery.event.dispatch l.php:3063\\nelemData.handle.eventHandle l.php:2681\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354581902, 'spacePHID': None, 'dateCreated': 1351539120, 'dateModified': 1417573388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41504', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking inside an alien node throws an TypeError', 'description': {'raw': \"Uncaught TypeError: Cannot call method 'getModel' of undefined ve.ce.js:208\\nve.ce.getOffsetFromElementNode ve.ce.js:208\\nve.ce.getOffset ve.ce.js:121\\nve.ce.SurfaceObserver.poll ve.ce.SurfaceObserver.js:135\\nve.ce.SurfaceObserver.start ve.ce.SurfaceObserver.js:66\\nve.ce.Surface.onMouseUp ve.ce.Surface.js:352\\nproxy jquery.js:775\\njQuery.event.dispatch jquery.js:3063\\nelemData.handle.eventHandle\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354222915, 'spacePHID': None, 'dateCreated': 1351536660, 'dateModified': 1417573391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41501', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Vector: Default icon for \"profile\" in personal tools should be gender neutral and fit with other site icons look & feel', 'description': {'raw': \"We have this dude in the Vector skin next to the user name:\\n\\n{F26476317,size=full,layout=inline} http://bits.wikimedia.org/static-1.21wmf2/skins/vector/images/user-icon.png\\n\\nIf one specifies their gender in preferences as female, it would be cool to see a female user icon instead of the dude. :)  If we're interested in gender gap, this could be one tiny thing to help make the software more welcoming.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=45056\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51927\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53732\"}, 'authorPHID': 'PHID-USER-lzhljhpbm3qfphvqyill', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410560755, 'spacePHID': None, 'dateCreated': 1351487760, 'dateModified': 1539178044, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41484', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] mediawiki.action.edit.preview is not loaded at Commons despite \"Use live preview\" (wpuselivepreview) is activated in [[Special:Preferences]]', 'description': {'raw': 'Tested with IE 8 and latest RC of FF.\\n\\nCurrent behaviour:\\nWhen clicking the \"preview\" or \"show diff\" button, the page reloads.\\n\\nEvidence:\\n...after the DOM is ready...\\n...executed in JavaScript console...\\n> mw.loader.getState(\\'mediawiki.action.edit.preview\\');\\n\\'registered\\'\\n\\nExpected behaviour:\\nWhen clicking the \"preview\" or \"show diff\" button, live preview just replaces some elements in the DOM. No page reload.\\n\\n> mw.loader.getState(\\'mediawiki.action.edit.preview\\');\\n\\'ready\\'\\n\\nHow to reproduce:\\nSet your interface language to de or en, enable \"Use live preview\" in [[Special:Preferences]], go to a page, edit a section, click preview.\\n\\nNote:\\nUsing manually\\nmw.loader.load(\\'mediawiki.action.edit.preview\\');\\nworks perfectly: After it is loaded, LivePreview works as expected.\\n\\n--------------------------\\n**Version**: 1.20.x\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1350924643, 'spacePHID': None, 'dateCreated': 1350898080, 'dateModified': 1351012277, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41267', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Strange behavior after overwriting nowiki block', 'description': {'raw': '= Heading 1a =\\n<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>\\n\\n== Heading 2aa ==\\n\\n1) Put cursor within the nowiki block\\n2) Press a\\n3) Press Left\\n4) Press b\\n5) Problem: \"a\" has disappeared\\n\\n\\n(off-topic: with more complex moves I have spotted a self-replicating snowman ☃, now hunting him down)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360205998, 'spacePHID': None, 'dateCreated': 1350624900, 'dateModified': 1417573350, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41204', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paragraph containing nowiki block does not change style unless block selected', 'description': {'raw': '= Heading 1a =\\n<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>\\n\\n== Heading 2aa ==\\n\\n1) Put cursor at end of nowiki line\\n2) Select a different style\\n3) Problem: Style not applied\\n\\nThe style is applied if the line contains simple text instead.\\nThe style is applied if selecting the whole nowiki line instead of just putting the cursor at end of line.\\n\\nI guess nowiki in headers is not usual, though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367181672, 'spacePHID': None, 'dateCreated': 1350623940, 'dateModified': 1417573295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41203', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace does not remove paragraph when previous paragraph contains nowiki block', 'description': {'raw': '= Heading 1a =\\n<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>\\n\\n== Heading 2aa ==\\n\\n1) Put cursor at end of nowiki line\\n2) Press Enter\\n3) Press Backspace\\n4) Cursor moves back but newly created paragraph remains\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360362900, 'spacePHID': None, 'dateCreated': 1350622500, 'dateModified': 1417573348, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41202', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Text entered at left of nowiki block replaced with a slug character (pawn) when saved', 'description': {'raw': '= Heading 1a =\\n<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>\\n\\n== Heading 2aa ==\\n\\n1) Put cursor at end of line\\n2) Press Left\\n3) Press a\\n4) Problem: \"a\" does not seem to appear. Instead, it seems like the beginning of the block is being selected.\\n5) Save\\n6) Where \"a\" is expected, there is a pawn ♙\\n\\n= Heading 1a =\\n♙<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>\\n\\n== Heading 2aa ==\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360205789, 'spacePHID': None, 'dateCreated': 1350615420, 'dateModified': 1417573350, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41200', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support copy and paste from other VE instances (surfaces)', 'description': {'raw': '**Author:** `orbit`\\n\\n**Description:**\\nThis used to work by using localStorage, but was removed due to problems with stringifying and parsing annotationSets.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386799249, 'spacePHID': None, 'dateCreated': 1350601440, 'dateModified': 1417571282, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41193', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: LinkTrailed links appear differently before and after save-reload', 'description': {'raw': 'At first the last letter is not linked but after save-reload it becomes linked.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363987427, 'spacePHID': None, 'dateCreated': 1350557280, 'dateModified': 1417573339, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41160', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Backspace can't remove Preformatted\", 'description': {'raw': '1) Open http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Press: a Enter b Enter c\\n3) Select b with the mouse, set style to Preformatted\\n4) Click after c\\n5) Backspace as much as you can\\n\\nExpected result: c, b, a disappear\\nActual result: c disappears, subsequent newline disappears, then nothing disappears anymore.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360363655, 'spacePHID': None, 'dateCreated': 1350547200, 'dateModified': 1417573349, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41154', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Give user some notice if their browser is not supported', 'description': {'raw': 'I had a look at its code and finally found the compatibility map. See gerrit 41147.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368039230, 'spacePHID': None, 'dateCreated': 1350542220, 'dateModified': 1417573290, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41149', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Offset is incorrect after alienInline in Firefox', 'description': {'raw': '**Author:** `orbit`\\n\\n**Description:**\\nIf the linmod is \\nABC<alienInline></alienInline>DEF\\n0123            4             5678\\n\\nWhen the cursor is at 5, getOffset returns 3. Programmatically setting selection to 5 will correctly place the cursor, but once again, getting the offset will return 3.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364248074, 'spacePHID': None, 'dateCreated': 1350495360, 'dateModified': 1417573338, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41117', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unicode in links is percent-encoded when saved as wikitext', 'description': {'raw': '**Author:** `hydrogen_cyanide`\\n\\n**Description:**\\nwhen adding a link with Chinese characters, [[天安门广场]] in wikitext, the unicode character in the wikilink are percent-encoded, and the result i get after saving is [[%E5%A4%A9%E5%AE%2589%E9%2597%A8%E5%B9%BF%E5%9C%BA|天安门广场]]. \\n\\nit seems to be linked with the browser. my browser is firefox 14.0.1. the link added by others before are also encoded. see \\nhttp://www.mediawiki.org/w/index.php?diff=594584\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=40004'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355171819, 'spacePHID': None, 'dateCreated': 1350493800, 'dateModified': 1417573353, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41116', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Complex script (Indic) compatibility', 'description': {'raw': 'The tests mentioned in the link fail for Indic text.\\n\\n* Using styling icons.\\n* Deleting text properly using delete / backspace keys.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://www.mediawiki.org/wiki/VisualEditor/Typing/Indic'}, 'authorPHID': 'PHID-USER-3stle7x2whgjz463c4zz', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360364417, 'spacePHID': None, 'dateCreated': 1350483960, 'dateModified': 1417573349, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41109', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor jumps at the top/bottom of page after particular deletions/moves', 'description': {'raw': '1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Put your cursor anywhere in simple text\\n3) Press: Enter, Enter, Up\\n4) Click the bullet list icon\\n5) Press: Backspace, Enter, Down\\n6) Problem: Cursor jumps at the bottom of the page\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371773435, 'spacePHID': None, 'dateCreated': 1350451500, 'dateModified': 1417573273, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41093', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn ♙ appears after deleting list and moving cursor', 'description': {'raw': '1) Go to http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Put your cursor anywhere in simple text\\n3) Press: Enter, Enter, Up\\n4) Click the bullet list icon\\n5) Press: Backspace, Enter, Down\\n6) Surprise: A wild pawn appears! ♙\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369911007, 'spacePHID': None, 'dateCreated': 1350376800, 'dateModified': 1417585387, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41067', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Implement keyboard command registry', 'description': {'raw': 'From Trevor:\\n> [1] https://gerrit.wikimedia.org/r/#/c/26703/\\n> [2] https://github.com/madrobby/keymaster\\n> [3] https://github.com/ccampbell/mousetrap\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353111407, 'spacePHID': None, 'dateCreated': 1349804760, 'dateModified': 1417573400, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40896', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Pre-annotations don't work if at first character of a blank line (paragraph or list item)\", 'description': {'raw': 'Go to a blank paragraph. Press Ctrl-B or the Bold button; the button depresses, but if you type the text comes out unannotated.\\n\\nThis does not occur when the caret is at any point in the paragraph or list item which has any content in it, only when it is blank.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1349999541, 'spacePHID': None, 'dateCreated': 1349133000, 'dateModified': 1417573402, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40677', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Various actions that trigger retrieval of offsets throw uncaught exceptions', 'description': {'raw': \"Little hard to reproduce but has come up several times. Selecting some text, playing around with the inspector and pasting some text.\\n\\nStack:\\n\\nUncaught TypeError: Cannot call method 'canHaveChildren' of null\\n> ve.dm.Document.getNodeFromOffset\\n> ve.ui.Toolbar.updateTools\\n> ve.EventEmitter.emit\\n> ve.dm.Surface.change\\n> ve.ce.Surface.onPaste\\n> jQuery.extend.proxy.proxy\\n> jQuery.event.dispatch\\n> jQuery.event.add.elemData.handle.eventHandle\\n\\n\\nve.dm.Document.prototype.getNodeFromOffset = function(offset) {\\n        var node = this.documentNode.getNodeFromOffset(offset);\\n        if (!node.canHaveChildren\\nUncaught TypeError: Cannot call method 'canHaveChildren' of null\\n        ()) {\\n            node = node.getParent();\\n        }\\n        r\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354054590, 'spacePHID': None, 'dateCreated': 1348451460, 'dateModified': 1417573395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40463', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace deletes the wrong character', 'description': {'raw': 'The backspace button is sometimes deleting the character immediately ahead of the caret, instead of the character behind it. Other times, the backspace button functions fine, though I don\\'t know which situations it works or doesn\\'t work in. \\n\\nFor example, in [[VisualEditor:Test]], if one selects the place between the \"n\" and \"l\" in the word \"only\" on the third line and presses backspace, \"oly\" is displayed for a split second before changing to \"ony\".\\n\\nTested on Chrome/IE9/FF15 on Windows 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1349896759, 'spacePHID': None, 'dateCreated': 1348189080, 'dateModified': 1417573402, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40416', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Un-listing when the caret is at the end of the document throws an error', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354574782, 'spacePHID': None, 'dateCreated': 1348007700, 'dateModified': 1417573388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40339', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support templates', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=46521'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371609890, 'spacePHID': None, 'dateCreated': 1345761720, 'dateModified': 1459677998, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39598', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support categories', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370486004, 'spacePHID': None, 'dateCreated': 1345761720, 'dateModified': 1489397413, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39597', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit summary length counter counts characters instead of bytes', 'description': {'raw': 'The edit summary length counter (which counts backwards from 255) counts characters, not bytes. However, in languages that heavily rely on unicode charaters, a character is usually more than a byte.\\n\\nWhen saving an edit with a summary that is accepted by the counter but with more than 255 bytes, a part of the summary is cut off.\\n\\nCeterum censeo bug 4715 esse delendam.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=4715'}, 'authorPHID': 'PHID-USER-j27ofmod3h6tzafsujyq', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1346892931, 'spacePHID': None, 'dateCreated': 1345637520, 'dateModified': 1417573404, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39558', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Select all then replace causes 'Return' to act as 'cursor-left' in Heading mode\", 'description': {'raw': \"To reproduce:\\n\\nGo to a blank VisualEditor page, click edit, change entry mode to Heading 1 (or whichever Heading mode), select all (Ctrl-A or Cmd-A), type in some content, press 'Return'.\\n\\nThe content will appear (subject to bug 39517), but the 'Return' will cause the cursor to move to the left rather than inserting a newline. Indeed, further 'Returns' will insert newlines only to split a Heading, or when transitioning to a Paragraph or Pre-formatted block.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=39517\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345846648, 'spacePHID': None, 'dateCreated': 1345503180, 'dateModified': 1417573404, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39518', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: #<nowiki><p>http://www.wikipedia.de</p></nowiki> round-trips to #<nowiki><p><p>http://www.wikipedia.de</p></p></nowiki>', 'description': {'raw': \"http://www.mediawiki.org/w/index.php?title=VisualEditor:Sandbox&diff=569290&oldid=569131\\n\\nI didn't touch Line 29 at all.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\"}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1344907812, 'spacePHID': None, 'dateCreated': 1344201300, 'dateModified': 1417573405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39059', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: onbeforeunload throws Uncaught TypeError when leaving page from \"Read\" mode', 'description': {'raw': 'Steps to reproduce:\\n* Go to a page\\n* Switch to Edit mode\\n* Switch to Read mode\\n* Go to a different page (e.g. \"View history\" or \"Main Page\")\\n\\n> Uncaught TypeError: Cannot call method \\'getModel\\' of null\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392750003, 'spacePHID': None, 'dateCreated': 1343783700, 'dateModified': 1417573269, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38902', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Security: CSS positioning can be used to break out of the content area', 'description': {'raw': \"The `position` CSS attribute is allowed in wikitext and TemplateStyles CSS; it can be used to position parts of the user-generated content in places which are normally software-generated, e.g. on top of the sidebar menu or the search box. (Depending on the skin, `z-index` might or might not be also needed to achieve this.) A similar effect can be achieved with negative margins as well.\\n\\nThis is occasionally used for vandalism, e.g. [[https://hu.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Adminisztr%C3%A1torok_%C3%BCzen%C5%91fala&diff=19674665&oldid=19670961|flipping the contents of the page]] or [[https://en.wikipedia.org/w/index.php?title=Module:Dynkin&diff=prev&oldid=669919700|obscuring everything using absolute or fixed positioning]]. This is confusing for patrollers as it also affects difflinks, but still relatively easy to revert using the undo/rollback links in recent changes / page history / etc.\\nIn theory it could also be used for more dangerous things, by overlaying transparent links on top of clickable areas of the interface area it's possible to hijack clicks.\\n[[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5392|CVE-2012-5392]] has been reserved for this.\\n\\nOn the other hand, positioning is a fundamental part of anything with a nontrivial amount of formatting, and is regularly used in infoboxes, amboxes and similar templates. Even the ability to break out of the content area is (ab)used for displaying various indicators on top of the page (such as a featured star, or the coordinates of the article subject). [[https://www.mediawiki.org/wiki/Help:Page_status_indicators|Page status indicators]] have been provided as a replacement for this, but the old method is still being used, so fixing this issue is blocked on finishing that migration. (See T135802#2332298 for some problems communities have with using indicators.) They are also used decoratively on user pages (e.g. to modify the site logo); breaking that probably would not be the end of the world.\\n\\nSome potential solutions that were dicussed in the comments:\\n* Make the content are a stacking context (done in df10f03a7a28) and make sure everything else has a higher z-index (and non-transparent background, although positioning content behind a transparent interface block is harder to abuse). This would have to be done for every skin.\\n* Make the content area `overflow: hidden` (and either ban `position: fixed`, or make the content area a 3D rendering context). See T40848#1913661 for more details.\\n* Use [[https://caniuse.com/#feat=css-containment|CSS containment]]. Not widely supported yet though.\\n\\nPer T40848#1938655 the plan is to use `overflow: hidden`, first on a larger area so it's still possible to overlay the interface area where status indicators are, then on the content area once status indicator migration is finished. Status indicator blocks themselves would have to be secured (T135802). \"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1343661300, 'dateModified': 1694365777, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38848', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'security-bug', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Pressing 'Esc' in Save-dialog should exit saving, return to editor\", 'description': {'raw': '[From a user report.]\\n\\n\"If the user press ESC while the save popup is open, it should just return to the edit mode, but it does nothing unless we click in the [x] button.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343341026, 'spacePHID': None, 'dateCreated': 1343084880, 'dateModified': 1417573407, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38621', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Arrow keys move the caret in the opposite direction in RTL environment', 'description': {'raw': \"Arrow keys move the caret in the opposite direction in RTL environment. Simple textareas in browsers do this correctly, so as much as possible, the Visual Editor should rely on the browsers' behavior.\\n\\nSee https://www.mediawiki.org/wiki/VisualEditor/Internationalization_requirements .\\n\\nRelated: bug 38000.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369780070, 'spacePHID': None, 'dateCreated': 1342868640, 'dateModified': 1517519635, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38546', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Build out support for Monobook', 'description': {'raw': \"The VisualEditor extension currently only works with the Vector skin. It should work with other skins such as Monobook.\\n\\nFrom [mediawiki/extensions/VisualEditor.git] / VisualEditor.hooks.php (<https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/VisualEditor.git;a=blob;f=VisualEditor.hooks.php;h=e43fef59dd678ba5309f2335829dd6fe1e041a2d;hb=4fea35acd451c939a522ab7a4d7bd13e4ac95e76>):\\n\\n---\\nclass VisualEditorHooks {\\n\\t/**\\n\\t * Adds VisualEditor JS to the output if in the correct namespace.\\n\\t *\\n\\t * This is attached to the MediaWiki 'BeforePageDisplay' hook.\\n\\t *\\n\\t * @param $output OutputPage\\n\\t * @param $skin Skin\\n\\t */\\n\\tpublic static function onBeforePageDisplay( &$output, &$skin ) {\\n\\t\\tglobal $wgTitle;\\n\\t\\tif (\\n\\t\\t\\t// Vector skin supported for now.\\n\\t\\t\\t$skin->getSkinName() === 'vector' &&\\n\\t\\t\\t(\\n\\t\\t\\t\\t// Article in the VisualEditor namespace\\n\\t\\t\\t\\t$wgTitle->getNamespace() === NS_VISUALEDITOR ||\\n\\t\\t\\t\\t// Special page action for an article in the VisualEditor namespace\\n\\t\\t\\t\\t$skin->getRelevantTitle()->getNamespace() === NS_VISUALEDITOR\\n\\t\\t\\t)\\n\\t\\t) {\\n\\t\\t\\t$output->addModules( array( 'ext.visualEditor.editPageInit' ) );\\n\\t\\t}\\n\\t\\treturn true;\\n\\t}\\n---\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345745134, 'spacePHID': None, 'dateCreated': 1341350580, 'dateModified': 1417573404, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38154', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dialog to manipulate image properties (type, alignment, border, size, caption, alt text)', 'description': {'raw': 'More for the wishlist...\\n\\nNeed a dialog to manipulate image properties (size, alignment, border, caption).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394835371, 'spacePHID': None, 'dateCreated': 1341271020, 'dateModified': 1649101677, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38129', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor should not try to initialise if no ContentEditable support', 'description': {'raw': \"Example: Android 2.x browser (tested Kindle Fire), iOS < 5 browser.\\n\\nThe editor initializes, but since there's no ContentEditable support you can't actually type anything. In iOS 4.3.2 simulator initialization never quite completes...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370435524, 'spacePHID': None, 'dateCreated': 1341270660, 'dateModified': 1417573273, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38128', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Save dialog description field doesn't respond to 'Enter' or 'Return' keys\", 'description': {'raw': \"(Save needs to be selected as default action?) Very irritating for those of us that don't use the mouse much when we edit. ;-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50897\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374613842, 'spacePHID': None, 'dateCreated': 1340916180, 'dateModified': 1431785852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38042', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination', 'description': {'raw': 'When copy-pasting from the VisualEditor into LibreOffice 3 (tested 3.5.2.2 on Ubuntu 12.04), links are copied with the target URL of the wiki page being edited plus \"#\" on the end, eg <https://www.mediawiki.org/wiki/VisualEditor:Welcome#>\\n\\nThis doesn\\'t happen when copy-pasting from the view mode.\\n\\nSee also bug 33239 comment 6 -- if we retain the original href and use JavaScript to suppress regular clicking, I think this would lead to more natural cut-n-paste behavior with other apps.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=33105'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361834067, 'spacePHID': None, 'dateCreated': 1340905200, 'dateModified': 1417573344, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38033', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Initiate file upload by drag-and-drop', 'description': {'raw': \"Once basic image support is included, and there's some integration with UploadWizard or similar, it should be possible to initialize the upload tool with drag-and-dropped image files.\\n\\nThis would allow simply dragging one or more files from your file manager over to the spot in the document where you want them, ending up with a single image or gallery at the end.\\n\\nCompared to {T40030}, needs to be able to initialize the wizard with given File objects received via a drop.\\n\\n**See also**: {T11133}\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1444761013, 'spacePHID': None, 'dateCreated': 1340904000, 'dateModified': 1660398843, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38031', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Way in VisualEditor to initiate Commons file uploading, and insert image on completion', 'description': {'raw': 'Our traditional editor toolbars have buttons to insert a [[File:Foo.png]] or similar, but not that would help you with the actual editing process.\\n\\nA button that launches the UploadWizard -- possibly uploading to Commons -- and ends with inserting the image(s) into the article would be a big leap forward.\\n\\n--------------------------\\n\\nUser journey:\\n# User clicks on \"insert media\"\\n# In the dialog, user clicks on \"upload new\"\\n{F176539}\\n\\n //… or \\'User drags a file into the editor\\', see T40031 //\\n\\n3. Dialog is launched\\n{F176534}\\n\\n4. User confirms that the media file is theirs, and accepts that it will thus be under the default licence (CC-BY-SA-3.0); file starts uploading with a progress bar (indeterminate for now)\\n\\n{F176541}\\n\\n //… or user is directed to Special:Upload if local uploads are available.//\\n> \"To upload a file which cannot be freely re-used, please use the __restricted form__.\"\\n\\n //… or user is directed to Special:UploadWizard on Commons.//\\n> \"To upload a file created by someone else, or under a different licence, please use the __advanced form__.\"\\n5. User enters a title.\\n{F176543}\\n\\n6. User enters a description (default in the user\\'s interface language, with a control to set the language to something else).\\n{F1000}\\n\\n7. User optionally over-rides the date of creation from \\'today\\'.\\n{F1000}\\n\\n8. User optionally enters (Commons) categories.\\n{F176551}\\n\\n9. User clicks \"Publish and Insert\", and file is un-gated on the stash and published on Commons, and inserted locally as a `thumb|right` (or `|left` on RTL) at default size with the description as the caption (if the description is in the content language).\\n{F176555}\\n\\n //… or user clicks \"Cancel Publishing\" and the file is left in the stash for garbage collection, never published.//\\n\\n10. Done.'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1444246370, 'spacePHID': None, 'dateCreated': 1340903820, 'dateModified': 1660398843, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38030', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Triple-click to select block level element', 'description': {'raw': \"From user feedback. Expected behaviour is to select entire current context (i.e. paragraph or if you're in a table, the table cell).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372090012, 'spacePHID': None, 'dateCreated': 1340834460, 'dateModified': 1417573272, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38011', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'RFC: Implement rendering of redlinks in Parsoid HTML as post-processor', 'description': {'raw': \"## Requirements\\n\\n- Identify links to pages that do not exist.\\n- Support different red link behavior on desktop (class, link to edit view) and apps (remove links).\\n- Support re-styling of red links for skins & accessibility.\\n- Perform well, both server & client side.\\n\\n## Non-requirements\\n\\n- Stub thresholds: These can be implemented client side with a separate API request, for users that have this option enabled.\\n\\n## Solutions\\n\\n### 1) Separate metadata\\n\\nProvide a JSON array containing hrefs of pages that do not exist. On most pages, this array will be very short or empty.\\n\\nClients can then use this array to find links to non-existing pages, and apply the transformations they would like.\\n\\nAdvantages:\\n\\n- Easy to implement server side.\\n- Avoids latency overheads of server-side DOM parsing.\\n- Can be consistently applied to old content. However, a general limitation of red link updates for old revisions is that current link tables are only available for the latest revision, which means that links in old revisions might not be updated.\\n- Consistent matching interface helps clients render red links for specific use cases.\\n\\nDisadvantages:\\n\\n- Client requirements:\\n  - Process JSON and run JS.\\n  - Extra API request.\\n- API complexity: Need to expose metadata in separate API.\\n\\n\\n### 2) Parsoid DOM pass\\n\\nRetrieve list of red links in page (as in separate metadata solution), and rewrite href / add classes in DOM processing pass.\\n\\nAdvantages:\\n\\n- Still relatively easy to implement server side.\\n- Low extra cost.\\n- No need for JS on the client.\\n- Compatible with existing skins.\\n- No need for extra API.\\n- Records accurate 'at the time' snapshot of how a page looked.\\n\\nDisadvantages:\\n\\n- Implements a specific kind of handling / rewriting, which then needs to be undone / changed for other use cases.\\n- Changes in href (ex: linking to edit views) complicate matching for further post-processing. Not touching the href would mean that clients would need to modify the href dynamically, negating the advantage of not needing to execute JS.\\n- Does not automatically update for old revisions.\\n- Increases fraction of re-renders that change the content.\\n\\n\\n### 3) Parsoid DOM pass + html2html update end point\\n\\nAs in `Parsoid DOM pass`, but also update red link markup in old revisions through a Parsoid HTML2HTML end point.\\n\\nAdvantages: \\n\\n- As for `Parsoid DOM pass`.\\n- More up-to-date red link information in old revisions.\\n\\nDisadvantages:\\n\\n- Extra complexity in Parsoid and RESTBase.\\n- Increased latency and cost for accesses to old revisions, especially if the update is applied on each request.\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1497485443, 'spacePHID': None, 'dateCreated': 1340566560, 'dateModified': 1610119401, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37902', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Links are not shown as redlinks when their target is blank (or as 'stub-alternate-colour' if appropriate)\", 'description': {'raw': 'To show red links (and stub links) correctly, Parsoid will need to hint on each link as to the status of its target. Also some work in CE and UI. ;-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=38726'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395283543, 'spacePHID': None, 'dateCreated': 1340565720, 'dateModified': 1542028412, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37901', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cut-n-paste from one window to another loses formatting', 'description': {'raw': \"Tested in Firefox 16 nightly.\\n\\nSteps to repro:\\n* go to https://www.mediawiki.org/wiki/VisualEditor:Welcome\\n* hit 'edit'\\n* click in, select all, copy to clipboard\\n* go to https://www.mediawiki.org/wiki/VisualEditor:Blorpo etc\\n* hit 'edit'\\n* click in, paste\\n\\nExpected results:\\nBeautiful pasted HTML\\n\\nActual results:\\nAll formatting lost. Newlines are turned into little newline symbols.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375942744, 'spacePHID': None, 'dateCreated': 1340418900, 'dateModified': 1417573271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37860', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Nice error message for users without JavaScript', 'description': {'raw': 'VE should give nice error messages (where possible, graceful degradation?) to users without JavaScript or not using Vector as their skin.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345671293, 'spacePHID': None, 'dateCreated': 1340417940, 'dateModified': 1417573405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37855', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Does not insert a necessary <nowiki /> between </i></b> and <i>', 'description': {'raw': 'Create some text - e.g. \"Expe dit ious\". Set the first seven characters as bold, and the last seven as italics. Round-trip.\\n\\nExpected wikitext: \\'\\'\\'Expe\\'\\'dit\\'\\'\\'\\'\\'<nowiki></nowiki>\\'\\'ious\\'\\'\\n\\nExpected HTML: <strong>Expe<em>dit</em></strong><em>ious</em>\\n\\nActual wikitext:\\'\\'\\'Expe\\'\\'dit\\'\\'\\'\\'\\'\\'\\'ious\\'\\'\\n\\nActual HTML: <strong>Expe<em>dit\\'\\'</em></strong>ious\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355187426, 'spacePHID': None, 'dateCreated': 1340397840, 'dateModified': 1366647258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37846', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Handle edit conflicts', 'description': {'raw': 'From\\nhttps://www.mediawiki.org/w/index.php?title=Visual_editor/Feedback&oldid=553398#Are_there_edit_conflicts.3F\\n----\\nI\\'ve removed content[1] from previous edits but got no warning about that.\\n:Yes, we discovered this during deployment. A priority right away, certainly!\\n[1] https://www.mediawiki.org/w/index.php?diff=next&oldid=552684\\n----\\n\\nFrom\\nhttps://www.mediawiki.org/w/index.php?title=Visual_editor/Feedback&oldid=553398#mid-air_collisions_are_not_detected_.28currently.29\\n----\\nI \"lost\" my edits due to a mid-air collision. Currently there appears to be no mechanism to detect if someone edits a text which you opened and changed and saved before... I thought we have edit tokens\\n----\\n\\nFrom\\nhttps://www.mediawiki.org/wiki/Thread:VisualEditor_talk:Welcome/Some_issues\\n----\\nIt looks like the editor disables edit conflict handling. As I appear to have ended up overwriting an other user\\'s edit.\\n----\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker\\n**URL**: https://www.mediawiki.org/w/index.php?diff=next&oldid=552684'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354155486, 'spacePHID': None, 'dateCreated': 1340368080, 'dateModified': 1417573393, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37828', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unable to edit an old revision', 'description': {'raw': 'On https://www.mediawiki.org/w/index.php?title=VisualEditor:Welcome&oldid=551728 I click \"edit\", then I\\'m editing the current version of text.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345748642, 'spacePHID': None, 'dateCreated': 1340342220, 'dateModified': 1417573405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37821', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'HTML/JS/XSS injection in visual editor (attribute sanitation on links)', 'description': {'raw': 'Create a new link in the visual editor. Add this text as the link target (including quotes exactly):\\n\\n\" onmouseover=\"alert(document.cookie)\" alt=\\n\\nWhen mousing over the link in the editor, you\\'ll get an alert popup with cookie contents. Same occurs in the HTML serialization (\"preview\").\\n\\n\\nI notice that ve.Html.makeAttributeList() doesn\\'t do any escaping. Changing it locally to escape the text before putting it into an attribute seems to help on the preview (HTML serialization) but not in the editor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://test.wikipedia.org/wiki/Special:VisualEditorSandbox'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340319728, 'spacePHID': None, 'dateCreated': 1328826240, 'dateModified': 1351534215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34308', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Narayam not working in contenteditable div', 'description': {'raw': 'Narayam not working in contenteditable div. Example for such a  page:  https://www.mediawiki.org/wiki/Special:WebFonts?uselang=ta\\n\\nAlso has impact on visualeditor if contenteditable div is used, as discussed in Bug 33076\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**:   https://www.mediawiki.org/wiki/Special:WebFonts?uselang=ta'}, 'authorPHID': 'PHID-USER-m2yck6646cdt5t6zkta4', 'ownerPHID': 'PHID-USER-m2yck6646cdt5t6zkta4', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1332910288, 'spacePHID': None, 'dateCreated': 1328503560, 'dateModified': 1332910288, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34220', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"inArray's use of strict equals in es.ContentView.js may be inappropriate (FIX attached)\", 'description': {'raw': \"**Author:** `acocaracha`\\n\\n**Description:**\\nI've noticed a problem with es.ContentView.js when implementing tex equation support.  When you click text outside an annotation and then click back into the annotation, the new content is determined to have a different type than the surrounding text.  I believe this is because inArray uses strict equals and really the only thing it should be comparing is the type key and I don't think that necessarily needs to be strict (although I guess it could be).\\n\\nHere is a copy of the old code: https://jalto.net/equationdb/VisualEditor_save/demo/\\n\\nAnd the new code: https://jalto.net/equationdb/VisualEditor_old/demo/\\n\\nSteps to reproduce in old code:\\n1) Create an inline equation\\n2) Click a different section of the text\\n3) Click in the middle of the inline equation\\n4) Type something\\n\\nThe new code is working fine.  The commits are:\\n\\nhttps://github.com/jalto/VisualEditor/commit/5e544447e5d54b260f5c0333f4dc9da5f15124d7\\n\\nand\\n\\nhttps://github.com/jalto/VisualEditor/commit/0f5a139d24870f200070a95cd70539b04dc0ce33\\n\\nThanks,\\n\\nJohn\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340400649, 'spacePHID': None, 'dateCreated': 1326072600, 'dateModified': 1350341829, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz33596', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'MediaWiki Vagrant broken', 'description': {'raw': \"I am following [[ https://www.mediawiki.org/wiki/MediaWiki-Vagrant#Quick_start | quick start ]] instructions on a Mac.\\n\\n```\\n$ sw_vers -productVersion\\n10.9.5\\n```\\n\\n```\\n$ git --version\\ngit version 2.1.3\\n```\\n\\n```\\n$ vboxmanage --version\\n4.3.18r96516\\n```\\n\\n```\\n$ vagrant -v\\nVagrant 1.6.5\\n```\\n\\n```\\n$ git clone ssh://Zfilipin@gerrit.wikimedia.org:29418/mediawiki/vagrant\\nCloning into 'vagrant'...\\nremote: Counting objects: 1015, done\\nremote: Finding sources: 100% (390/390)\\nremote: Getting sizes: 100% (259/259)\\nremote: Compressing objects: 100% (127427/127427)\\nremote: Total 7887 (delta 94), reused 7780 (delta 91)\\nReceiving objects: 100% (7887/7887), 1.88 MiB | 379.00 KiB/s, done.\\nResolving deltas: 100% (3831/3831), done.\\nChecking connectivity... done.\\n```\\n\\n```\\n$ cd vagrant/\\n```\\n\\n```\\n$ git submodule update --init --recursive\\nSubmodule 'puppet/modules/cdh' (https://gerrit.wikimedia.org/r/operations/puppet/cdh) registered for path 'puppet/modules/cdh'\\nSubmodule 'puppet/modules/mariadb' (https://gerrit.wikimedia.org/r/operations/puppet/mariadb) registered for path 'puppet/modules/mariadb'\\nSubmodule 'puppet/modules/nginx' (https://gerrit.wikimedia.org/r/operations/puppet/nginx) registered for path 'puppet/modules/nginx'\\nSubmodule 'puppet/modules/wikimetrics' (https://gerrit.wikimedia.org/r/operations/puppet/wikimetrics) registered for path 'puppet/modules/wikimetrics'\\nCloning into 'puppet/modules/cdh'...\\nremote: Counting objects: 92, done\\nremote: Finding sources: 100% (5/5)\\nremote: Getting sizes: 100% (4/4)\\nremote: Compressing objects: 100% (5690/5690)\\nremote: Total 1292 (delta 0), reused 1288 (delta 0)\\nReceiving objects: 100% (1292/1292), 250.13 KiB | 171.00 KiB/s, done.\\nResolving deltas: 100% (677/677), done.\\nChecking connectivity... done.\\nSubmodule path 'puppet/modules/cdh': checked out '65335f7d027c635065966a15a7b4467c1ce311b5'\\nCloning into 'puppet/modules/mariadb'...\\nremote: Counting objects: 26, done\\nremote: Finding sources: 100% (18/18)\\nremote: Getting sizes: 100% (8/8)\\nremote: Compressing objects: 100% (4224/4224)\\nremote: Total 70 (delta 6), reused 66 (delta 6)\\nUnpacking objects: 100% (70/70), done.\\nChecking connectivity... done.\\nSubmodule path 'puppet/modules/mariadb': checked out 'b5690999702552cc7fea48b2206f4bb92191d8ca'\\nCloning into 'puppet/modules/nginx'...\\nremote: Total 61 (delta 0), reused 61 (delta 0)\\nUnpacking objects: 100% (61/61), done.\\nChecking connectivity... done.\\nSubmodule path 'puppet/modules/nginx': checked out '10a1e925fa707654102f39092b46a64c61710614'\\nCloning into 'puppet/modules/wikimetrics'...\\nremote: Counting objects: 40, done\\nremote: Finding sources: 100% (19/19)\\nremote: Getting sizes: 100% (12/12)\\nremote: Compressing objects: 100% (23171/23171)\\nremote: Total 263 (delta 4), reused 253 (delta 4)\\nReceiving objects: 100% (263/263), 57.59 KiB | 0 bytes/s, done.\\nResolving deltas: 100% (118/118), done.\\nChecking connectivity... done.\\nSubmodule path 'puppet/modules/wikimetrics': checked out '5f416bbce4188914f48a044a8df09f1c34b07183'\\n```\\n\\n```\\n$ ./setup.sh\\nPlugin vagrant-vbguest is already installed\\nInstalling plugin mediawiki-vagrant-0.2.1.gem\\n- Installing the 'mediawiki-vagrant-0.2.1.gem' plugin. This can take a few minutes...\\n- Installed the plugin 'mediawiki-vagrant (0.2.1)'!\\nYour git/Gerrit username\\nEnter 'anonymous' for anonymous access, leave blank to manage it yourself\\ngit_user: Zfilipin\\n\\n\\nYou're all set! Simply run `vagrant up` to boot your new environment.\\n```\\n\\n```\\n$ vagrant roles list\\nAvailable roles:\\n\\n  accountinfo                gwtoolset                  popups                  \\n  analytics                  hadoop                     proofreadpage           \\n  antispam                   hive                       renameuser              \\n  antispoof                  https                      scholarships            \\n  apisandbox                 hue                        scribunto               \\n  apparmor                   iegreview                  securepoll              \\n  babel                      imagemetrics               simple_miser            \\n  betafeatures               interwiki                  simple_performant       \\n  categorytree               jsduck                     sitematrix              \\n  centralauth                jsonconfig                 smtplog                 \\n  centralnotice              labledsectiontransclusion   svg                     \\n  chromium                   mantle                     templatedata            \\n  cirrussearch               massmessage                textextracts            \\n  cite                       math                       thumb_on_404            \\n  cldr                       mathoid                    timedmediahandler       \\n  codeeditor                 mathsearch                 translate               \\n  cologneblue                memcached                  uls                     \\n  commons                    mleb                       uploadwizard            \\n  commonsmetadata            mobileapp                  urlshortener            \\n  confirmedit                mobilefrontend             usermerge               \\n  doublewiki                 modern                     vectorbeta              \\n  echo                       molhandler                 visualeditor            \\n  education                  monobook                   warnings_as_errors      \\n  elk                        multimedia                 wikidata                \\n  eventlogging               multimediaviewer           wikidiff2               \\n  featuredfeeds              navigationtiming           wikieditor              \\n  flow                       newusermessage             wikigrok                \\n  fss                        nuke                       wikihiero               \\n  fundraising                oauth                      wikilove                \\n  gadgets                    oozie                      wikimediaevents         \\n  gadgets2                   pagedtiffhandler           wikimediaincubator      \\n  geodata                    pageimages                 wikimediamessages       \\n  geshi                      pagetriage                 wikimetrics             \\n  gettingstarted             parserfunctions            wikitech                \\n  globalcssjs                parsoid                    xhprof                  \\n  globaluserpage             pdfhandler                 zend                    \\n  graph                      phptags                    zero                    \\n  guidedtour                 poem                                               \\n\\nRoles marked with '*' are enabled.\\nNote that roles enabled by dependency are not marked.\\nUse `vagrant roles enable` & `vagrant roles disable` to customize.\\n```\\n\"}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'dateClosed': 1416519309, 'spacePHID': None, 'dateCreated': 1416497151, 'dateModified': 1416523985, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Use PHP Virtual REST Service to access Parsoid', 'description': {'raw': \"Write a Parsoid backend for VirtualRestService, and replace VisualEditor's and Flow's hacks with that. Incorporate the cookie forwarding hacks from VE as well.\\n\\nSee https://www.mediawiki.org/wiki/Requests_for_comment/PHP_Virtual_REST_Service and https://github.com/wikimedia/mediawiki/tree/master/includes/libs/virtualrest\\n\\nThis would also be a good opportunity to clean up the way the Parsoid URL (and whether it's available) is configured in mediawiki-config\\n\\nSee also: T74988\"}, 'authorPHID': 'PHID-USER-ll6tmaogat2b5q7tnqas', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420599381, 'spacePHID': None, 'dateCreated': 1415656386, 'dateModified': 1426214472, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'RfC: Allow styling in templates', 'description': {'raw': 'Currently the MediaWiki markup allows the inclusion of html elements with style attributes. Mixing layout with content causes various problems with reusability, maintainability and is not future proof. Already on the mobile version of MediaWiki problems are being seen with inline styles with how pages render on smaller screens which could be solved via css3 media queries, however these cannot be done in inline styles.\\n\\nIt should be possible for templates to have associated stylesheets so that media queries can be applied where necessary. This is related to T37704.\\n\\nThis RFC was proposed in 2013, discussed at two separate RFC meetings in 2014, and the status is unclear as of 2016-03-29.  More detailed status in the comments of this task\\n\\nFull writeup:\\n[[ https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates | Allow styling in templates RfC ]].\\n'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-a6p24cvyblhfzc7we7nc', 'dateClosed': 1519785718, 'spacePHID': None, 'dateCreated': 1411645188, 'dateModified': 1618941029, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Document a process to request new projects', 'description': {'raw': 'On Day 1 we will need a process to request a new project, because plain users will not be able to create projects themselves.\\n\\nIn fact, we need such progress already now in this Labs instance. We can define the process as we document it, and fine tune it as we see fit, real request after real request.\\n\\nI have started a draft at https://www.mediawiki.org/wiki/Phabricator/Help. @aklapper & co, feel free fine tuning it while satisfying the current requests for Labs.'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-3neel27i7dyu62jbbx2l', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'dateClosed': 1410486133, 'spacePHID': None, 'dateCreated': 1405443204, 'dateModified': 1426854807, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl457', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Figure out a process for backports: Create \"WMF-Server-Backports\" and \"MediaWiki-Tarball-Backports\" projects', 'description': {'raw': 'Currently the process (except for security) https://www.mediawiki.org/wiki/Backporting_fixes implies usage of flags.'}, 'authorPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1413283003, 'spacePHID': None, 'dateCreated': 1397887689, 'dateModified': 1468414588, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl167', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Decide how to organize iterations and releases', 'description': {'raw': \"Related task upstream: [[ https://secure.phabricator.com/T390#21 | Implement project types ]].\\n\\nI don't understand how we're going to mark release milestones: each release a blocked task, kept open for each sub-point release until the RELX_Y branch in question is frozen?\\n(Due to http://fab.wmflabs.org/T164 we can't have two levels of dependency so I suppose we'll instead give up on granularity.)\\n\\nA handful of MediaWiki extensions are maintained by teams who use sprints, so the sprints could then be mapped to the RELX_Y branch in which they first appear and to the corresponding task; in this case (in theory) we'd gain, for no cost, that WMF work would be visible to tarball users.\\n\"}, 'authorPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1413266763, 'spacePHID': None, 'dateCreated': 1397886924, 'dateModified': 1503723328, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl166', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Decide how to organize projects', 'description': {'raw': '> Project behavior in Maniphest is similar to keywords behavior in Bugzilla\\n\\nRight, but then... what about keywords? Are they supposed to be enabled separately or are we using projects literally as keywords?\\n\\nBy the way, since we may have finally a common system for keywords/tags across different tools, this might be relevant: https://www.mediawiki.org/wiki/Project:New_contributors/One_ontology\\n\\n**UPDATED**: \\n\\nProjects are keywords, keywords are projects, components might be projects if we want... We need to come up with a default organization of projects, knowing that user will come and create the projects they miss (unless we stop them by restricting permissions), just like wiki editors create categories.\\n\\n**RULES FOR MIGRATING PROJECT NAMES**\\n\\n\\n  buginfo[\"product\"] = buginfo[\"product\"].replace(\\'-\\', \\'_\\')\\n  buginfo[\"product\"] = buginfo[\"product\"].replace(\\' \\', \\'_\\')\\n  buginfo[\"component\"] = buginfo[\"component\"].replace(\\'/\\', \\'_and_\\')\\n  buginfo[\"component\"] = buginfo[\"component\"].replace(\\'-\\', \\'_\\')\\n  buginfo[\"component\"] = buginfo[\"component\"].replace(\\' \\', \\'_\\')\\n\\n  component_separator = \\'-\\' \\n  project = \"%s%s%s\" % (buginfo[\"product\"],\\n                       component_separator,\\n                       buginfo[\"component\"])\\n\\n\\nExamples:\\n\\n| Bugzilla product | Bugzilla component | Phabricator project |\\n| MediaWiki | Change tagging | MediaWiki-Change_tagging |\\n| MediaWiki‑Vagrant | labs-vagrant | MediaWiki_Vagrant-labs_vagrant |\\n| Wikimedia | Git/Gerrit | Wikimedia-Git_and_Gerrit |\\n| Wiki Loves Monuments | Unused images | Wiki_Loves_Monuments-Unused_images |'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1411557406, 'spacePHID': None, 'dateCreated': 1397154942, 'dateModified': 1472748057, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl68', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Identify features Trello users would miss in Phabricator', 'description': {'raw': \"Which features would Trello users really miss? If you are not sure whether feature X is supported, under development, roadmapped... just ask. Let's create new subtasks for features considered blockers.\"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 80, 'name': 'High', 'color': 'red'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'dateClosed': 1410484891, 'spacePHID': None, 'dateCreated': 1396569879, 'dateModified': 1585040705, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl45', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Automatically give pasted tables class=\"wikitable\" in VE-MW', 'description': {'raw': 'Paste the following table (or any table from a non-Mediawiki source) into VE. While in edit mode, it will look fairly normal, with borders and a grey background for header cells (due to VE\\'s own style rules). But after the page is saved, it will appear in read mode without any borders or background.\\n\\n| Animal | Ferocity | Cuddliness\\n| ------- | ---------- | -------------\\n| Bunny | 0 | 9\\n| Cat | 4 | 10\\n| Tiger | 10 | ? \\n \\n{F25893} \\n\\nThis is because pasted tables do not get `class=\"wikitable\"` which provides the normal table styling.\\n'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453489651, 'spacePHID': None, 'dateCreated': 1419983289, 'dateModified': 1453749534, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Edit source link broken after editing the page with VisualEditor', 'description': {'raw': 'Seen as both anon and while logged in: \\n\\nEdit any page at http://en.wikipedia.beta.wmflabs.org\\n\\nUse insert menu to insert almost anything: I had the same experience with Formula, Table, and Media. \\n\\nSave the page after inserting the element. \\n\\nAfter save, click the wikitext edit link, whether logged in or anonymous.  Nothing happens. \\n\\nI see no javascript errors when clicking the wikitext edit, but I do see a warning on saving the page in VE, but I\\'m not sure it\\'s relevant: \\n\\n load.php:61\\n\"Invalid _currentGuiderID.  Returning early\" load.php:153\\nconsole.trace(): load.php:154\\nmw.log</log.warn() load.php:154\\ntransition/<()'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420464647, 'spacePHID': None, 'dateCreated': 1419973179, 'dateModified': 1427672978, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Insert/Template inspector should put focus on input text_field when invoked but no longer does', 'description': {'raw': 'Seen in Firefox and Chrome: \\n\\nEdit any page in VE, e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit\\n\\nClick Insert/Template\\n\\nThe input text field briefly shows a cursor and a blue bar indicating that the element has focus, but then the focus disappears. User should be able to type directly into text field without needing to click the text field element first, but no longer can. \\n\\nThis is the failure at https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/423/testReport/(root)/VisualEditor%20Transclusion/Add_parameter_to_template/'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422075817, 'spacePHID': None, 'dateCreated': 1419893532, 'dateModified': 1633290163, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Back arrow appears before other VE controls in MobileFrontend but does nothing', 'description': {'raw': 'As a logged in user with access to VE in MobileFrontend, bring up a random page and click the pencil icon to edit with VE e.g. http://en.m.wikipedia.beta.wmflabs.org/wiki/0.6922277312143298#/random. \\n\\nNote that in the upper left, the back-arrow icon \"escape\" button appears before the other controls. \\n\\nClick the back-arrow escape icon as the page loads, before the page is finished loading. Nothing happens. \\n\\nThis is the failure at https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/455/testReport/(root)/VisualEditor%20Mobile/Going_back_from_save_screen_in_VisualEditor/'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'dateClosed': 1420605607, 'spacePHID': None, 'dateCreated': 1419890942, 'dateModified': 1443277954, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Lua error: too many language codes requested', 'description': {'raw': 'When trying to assemble the December\\'s issue of VE multilingual newsletter,\\nI got this message after [[ https://meta.wikimedia.org/w/index.php?title=VisualEditor%2FNewsletter%2FSandbox&diff=10833033&oldid=10815060  |  this edit ]] (I guess LUA can\\'t actually handle so many languages. If I\\'m right, this needs to change - 20-something languages aren\\'t \"many\" at all.)\\n\\nMore info:\\n\\nBacktrace:\\n[C]: in function \"isRTL\"\\nmw.language.lua:99: in function \"isRTL\"\\nmw.language.lua:132: in function \"getDir\"\\nModule:Assemble_multilingual_message:46: in function \"chunk\"\\nmw.lua:490: ?'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-uqcn2l4ng4murmyfnvyp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-uqcn2l4ng4murmyfnvyp', 'dateClosed': 1526814427, 'spacePHID': None, 'dateCreated': 1419877407, 'dateModified': 1711449363, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'the first time that the VisualEditor link inspector appears, it takes a very long time', 'description': {'raw': 'The first time I open a link inspector using \"[[\", Ctrl-K, or the toolbar button, it takes about 5 seconds on my laptop. The subsequent times I do it in the same editing session it opens immediately.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1420932545, 'spacePHID': None, 'dateCreated': 1419347942, 'dateModified': 1438736764, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Preparing for a multi-device world plenary at 2015 MediaWiki Developer Summit', 'description': {'raw': 'https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#Schedule\\nMonday 26, 10:30am\\n\\n@Tfinc is the owner of the Mobile theme at the #MWDS15. He is also in charge of organizing the Mobile plenary session, or find someone to organize it.\\n\\nmeeting notes: http://etherpad.wikimedia.org/p/MWDS2015_multi-device_world'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-qmantxp3p7omhisp3qgq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1424916580, 'spacePHID': None, 'dateCreated': 1419267000, 'dateModified': 1424916580, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Inspector titles clipped in VisualEditor on mobile', 'description': {'raw': '{F22740}\\n\\nThis is caused by MobileFrontend setting box-sizing: border-box on every element.'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429205400, 'spacePHID': None, 'dateCreated': 1419112500, 'dateModified': 1547059906, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Embedded \"user.tokens\" module changes on every request', 'description': {'raw': 'The output of the embedded `user.tokens` module changes on every request. I\\'m not entirely sure whether this was on purpose.\\n\\nTraced it back to https://github.com/wikimedia/mediawiki/commit/b1e4006b44\\n{b1e4006b44}\\n\\nThis is a bit of a problem since we minify this module, and by default all minifications are cached at a key that is the hash of the unminified contents. We should implement a way to bypass the minification cache.\\n\\nAs such, we\\'re creating a new cache key and populating it on every page view for every logged in user. And that key is never used again.\\n\\nExample from localhost:\\n\\n```\\n<script>...mw.loader.implement(\"user.tokens\",function($,jQuery){mw.user.tokens.set({\"editToken\":\"5da7f8da8cc2c12b40e63510d3b83f3754937d96+\\\\\\\\\",\"patrolToken\":\"bc1e366f8f7806ed27d067667cdeebe554937d96+\\\\\\\\\",\"watchToken\":\"c52e9fcc036b315fe8ba3e0135cb928d54937d96+\\\\\\\\\"});},{},{},{});\\n/* cache key: alphawiki:resourceloader:filter:minify-js:7:aed9432283c8152b3eaff1761844e771 */\\n```'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1435036147, 'spacePHID': None, 'dateCreated': 1418952452, 'dateModified': 1602870154, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'PHID-PROJ-koo4qqdng27q7r65x3cw'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Release VisualEditor-MediaWiki as \"1.0\"', 'description': {'raw': 'Lots of things to do here, but broadly they break down into six categories:\\n\\n[ ] Functionality – mostly done\\n[ ] Performance – main focus area left\\n[ ] User experience –\\xa0the current integration is a bit lacking, but otherwise this is not far off\\n[ ] Language support – still a lot of work for IME support here\\n[ ] Browser support – mostly done\\n[ ] Major bugs –\\xa0not many of these left (he says…)'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'release', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1418941653, 'dateModified': 1707419798, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Navigating via Tab between fields in TransclusionCitation boxes switches to the Find/Replace fields in the background', 'description': {'raw': 'In betalabs: \\n\\n1. On a page in VE open Find/Replace - not typing anything in it, just open - a cursor will be in the Find field.\\n1. Open an existing template on the page for editing.  \\n2. Place a cursor in the first field of the transclusion box and click Tab to navigate to the next field.\\n\\nThe cursor will be placed into Replace field; clicking Tab one more time brings the cursor back into Transclusion box. \\n\\nThe same issue is with Citation.'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1611951130, 'spacePHID': None, 'dateCreated': 1418935912, 'dateModified': 1611951130, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Convert eqiad imagescalers to HHVM, Trusty', 'description': {'raw': \"In our quest to convert the whole cluster to trusty and HHVM, we've got to the imagescalers.\\n\\nFrom what I can see from puppet/the current image scalers is that we have the following packages custom-built at the moment:\\n\\n  - ffmpeg2theora (disabled libav multithreading)\\n  - librsvg (external resources loading protection)\\n  - libvips31 (backport)\\n  - libvpx1 (backport)\\n\\nWe also need to evaluate the performance of HHVM under the peculiar imagescalers load, which is probably going to be non-optimal.\\n\\nFinally, testing should be very accurate to assess any rendering differences on trusty vs precise.\"}, 'authorPHID': 'PHID-USER-fdo23otm6ztt674vjqko', 'ownerPHID': 'PHID-USER-fdo23otm6ztt674vjqko', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fdo23otm6ztt674vjqko', 'dateClosed': 1438696002, 'spacePHID': None, 'dateCreated': 1418890706, 'dateModified': 1660398882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Search text for inserting media should be selected on open', 'description': {'raw': 'On a page such as http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit\\n\\nClick Insert/Media\\n\\nNote that the default text in the search box is the title of the page. \\n\\nClick inside the search box.\\n\\nDefault text should disappear but does not. RETURN also does not remove the default text.\\n\\nCompare to the Link interface which looks similar but behaves correctly. \\n'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429301507, 'spacePHID': None, 'dateCreated': 1418848456, 'dateModified': 1438736993, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ResourceLoader slow under MediaWiki-Vagrant with VirtualBox', 'description': {'raw': 'CSS via load.php sometimes takes as long as 10  seconds to be returned on my local instance.\\nIf I run\\n> redis-cli\\n> monitor\\n\\nI will notice that the log will considerably slow on lines which look like this:\\n\"GET\" \"wiki:resourceloader:filter:minify-css:7:ef038bf45ab521177624638cbeb85f3d\"\\n\\nAnyone know why this might be happening?\\n'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1470362133, 'spacePHID': None, 'dateCreated': 1418775220, 'dateModified': 1470362201, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Break up ve.ce.Surface.js by functionality', 'description': {'raw': 've.ce.Surface is a 130k beast (>4000 lines) - more than twice as long as Converter and Transaction, the next largest files. Working on it will kill your mouse wheel and sanity.\\n\\nWe should try and break it up by functionality, e.g.\\n\\n* Key strokes\\n* Copy/paste\\n* Drag/drop'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1418756950, 'dateModified': 1730315223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When I changed the website link in an infobox all other links got redlinks', 'description': {'raw': 'I tried to edit an infobox with the VisualEditor in the German Wikipedia. I changed the website address there.\\nBut when I closed the \"infobox editor\" all links in the infobox (except of the link I changed) got redlinks.\\n\\nI think this is only a display error, but anyway I didn\\'t saved the changes I made.'}, 'authorPHID': 'PHID-USER-qq2c7r7m35tr32zlbsc3', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1435940456, 'spacePHID': None, 'dateCreated': 1418491053, 'dateModified': 1435940456, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Performance issues in Internet Explorer 11', 'description': {'raw': 'This problem with VisualEditor\\'s performance was reported at MediaWiki.org by User:Leaderboard, who was editing on the English Wikibooks.  The problem is intermittent or at least variable in severity.  It may depend on the size of the page.  It appears to happen at MediaWiki (testing in the sandbox) as well, after about a page\\'s worth of text has been added.  Here\\'s the problem in his own words:\\n\\n> First , it is too slow to display text which I am typing. It shows it in a slow and slideshow speed. Looks like it\\'s quite slow. And , on Task Manager , it shows that it is using one and only 1 full(utilizes 100% CPU for that) thread for this. It stays at full utilization when I\\'m typing and becomes very slow. I\\'m using Internet Explorer 11.\\n>\\n> When testing using Performance Dashboard , it stays at 5-15% during idle and while typing , it spikes to 50-55% of total CPU usage.\\n>\\n> %%% Running on a Dell Inspiron 6400 with Intel Core2Duo T7200 @ 2Ghz and 4GB DDR2 with Windows 8.1 tested.\"\\n'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1632431721, 'spacePHID': None, 'dateCreated': 1418411665, 'dateModified': 1632431721, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Don't text-transform: capitalize; section headers in the special character inserter\", 'description': {'raw': 'In Polish, headlines are written with 1st-letter uppercase only. That\\'s why there are \"Polskie diakrytyzowane\" and \"Inne diakrytyzowane\" in [[https://translatewiki.net/wiki/MediaWiki:Visualeditor-specialcharinspector-characterlist-insert/pl|Translatewiki:MediaWiki:Visualeditor-specialcharinspector-characterlist-insert/pl]]. VE displays it wrong (as if English Case Style was Default). {F20866}'}, 'authorPHID': 'PHID-USER-gf5juv3z3p75bykrcrhf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418751359, 'spacePHID': None, 'dateCreated': 1418328634, 'dateModified': 1438736770, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parameter entries aren't indented in the transclusion dialog's booklet layout in VisualEditor when using the OOUI MediaWiki theme\", 'description': {'raw': 'See screenshot:\\n\\n{F20244}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418335887, 'spacePHID': None, 'dateCreated': 1418326903, 'dateModified': 1438736296, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Uncaught TypeError: Cannot read property \\'getSurface\\' of null\", on undoing a comment in block quote.', 'description': {'raw': 'Environment- test2, beta, Production\\nBrowser- Chrome 39\\n\\n1> Insert a comment.Click on \"Insert\" button to close the dialog.\\n2> While the comment is still highlighted, select any option from the Heading format list.For ex- select Block quote\\n3> Click to undo(keeping the comment highlighted).Notice the icon and the comment pop-up get detached. Also, JS error \"Uncaught TypeError: Cannot read property \\'getSurface\\' of null\" shows up in console.\\n\\nSee screenshot.\\n'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1692891005, 'spacePHID': None, 'dateCreated': 1418315290, 'dateModified': 1692891005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Limit effect of search-and-replace assessment on long documents', 'description': {'raw': '1. Click on https://www.mediawiki.org/w/index.php?title=VisualEditor/status&veaction=edit\\n2. Wait for editor to load\\n3. Use find-and-replace\\n4. Try to type \"now support \"\\n5. Observe system die in flames after \\'n\\' was typed, not letting you type \\'o\\' yet, let alone the rest.\\n6. Cry.\\n\\n250ms is our normal threshold. Let\\'s do that.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420648497, 'spacePHID': None, 'dateCreated': 1418275115, 'dateModified': 1427672971, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Chinese full stop disappears at the end of paragraphs, if preceded by ref tags', 'description': {'raw': \"In VisualEditor, it is not always possible to save a paragraph that ends with <ref>(cite source)</ref>。 Upon saving the page, the full stop disappears.  See [[ https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&offset=20141206172053#Symbol_after_citation_disappear_after_edit_50625 | the original report ]].\\n\\nI successfully added one [[ https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=1309016&oldid=1228107 | in my sandbox at MediaWiki ]], but (a) I pasted the Chinese full stop into the text, rather than entering it normally, and (b) when I pasted it after the ref, it gave me a black sun before the full stop.  Also, I'm running Safari on a Mac, so it may be browser or OS dependent.\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1440120521, 'spacePHID': None, 'dateCreated': 1418190956, 'dateModified': 1440157738, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Japanese text disappears (kanji and maybe hiragana, not katakana) when you are writing list entries', 'description': {'raw': '[[ https://www.mediawiki.org/w/index.php?title=VisualEditor/Feedback&offset=20141204053320#Japanese_in_lists_51392 | Original report from MediaWiki.org: ]] from a logged-out editor, on 4 December 2014:\\n\\n\"I just tried to add list items in Japanese. Katakana seemed ok in lists but kanji and maybe hiragana too seemed to delete automatically when pressing enter to go to the next list item.\"\\n\\nI believe that this is different from T74619 in which katakana can\\'t be typed at all.'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1435941289, 'spacePHID': None, 'dateCreated': 1418188190, 'dateModified': 1437511430, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Bottom border of text box in save dialog only appears when zoomed in, in VisualEditor when using the OOjs UI MediaWiki theme', 'description': {'raw': 'See screenshot:\\n\\n{F20270}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1442906589, 'spacePHID': None, 'dateCreated': 1418156285, 'dateModified': 1521697009, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Layout of the image size options is jarring in VisualEditor when using the OOjs UI MediaWiki theme', 'description': {'raw': 'See screenshots:\\n\\n{F20264}{F20266}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420853400, 'spacePHID': None, 'dateCreated': 1418156178, 'dateModified': 1438736307, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Clash between rounded corners and text content is jarring for the category editor in VisualEditor when using the OOjs UI MediaWiki theme', 'description': {'raw': 'See screenshot:\\n\\n{F20251}\\n\\n(A problem in Apex too, but feels worse in MW.)'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420821858, 'spacePHID': None, 'dateCreated': 1418155768, 'dateModified': 1427673365, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Local Info and Discussions for Visual Editor', 'description': {'raw': '//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/64 //\\n\\n== Narrative ==\\n\\nAs a user, I want localinfo and discussion pages forVisual Editor Beta Features, so I can read them and respond in my language.\\n\\n\\n\\n== Acceptance Criteria ==\\n\\nEnable local links for info and discussion pages forthe VisualEditor Beta Features.\\n\\n\\n\\n== Related Bugs ==\\n\\n== Related Stories ==\\n\\nSee more VE BF feature requirements here:\\n\\n [[https://www.mediawiki.org/wiki/Beta_Features#Tasks | https://www.mediawiki.org/wiki/Beta_Features#Tasks]] '}, 'authorPHID': 'PHID-USER-64gvupsl7ajewpshylma', 'ownerPHID': 'PHID-USER-dbudsaorcqut7sg3vvbi', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-64gvupsl7ajewpshylma', 'dateClosed': 1418054452, 'spacePHID': None, 'dateCreated': 1418054449, 'dateModified': 1438736312, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make a Herald rule add all #VisualEditor-* tasks to #VisualEditor', 'description': {'raw': 'This would be hugely appreciated.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1418681581, 'spacePHID': None, 'dateCreated': 1417905944, 'dateModified': 1468329335, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Heading of template editor is centered; hence most text currently covered by \"Apply changes\" button in some languages', 'description': {'raw': 'When editing the infobox in https://fr.wikipedia.org/w/index.php?title=S%C3%A9bastien_Texier&veaction=edit , the heading is misaligned (overlapping with button), see screenshot.\\n\\n{F19186}'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1433457283, 'spacePHID': None, 'dateCreated': 1417892100, 'dateModified': 1660398882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"A number of VisualEditor dialogs do not cover full screen when 'full' size\", 'description': {'raw': \"A number of VisualEditor dialogs do not cover full screen when 'full' size.\\n\\nI can't reproduce this in OOUI demo.\\n\\nTo reproduce:\\n\\n1. Open a page in VisualEditor\\n2. Insert → Template (or Insert → Media, or (hamburger) → Options, or others)\\n3. Resize browser window until it is narrower than the dialog\\n\\n{F19019}\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421428646, 'spacePHID': None, 'dateCreated': 1417791464, 'dateModified': 1427672931, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Clean up duplication between config options: TitledElement's 'title' and IconElement's 'iconTitle' / IndicatorElement's 'indicatorTitle' (deprecate and remove the latter)\", 'description': {'raw': '[x] Deprecate\\n[x] Replace all code instances in Wikimedia core & deployed extensions\\n  [x] `iconTitle` https://codesearch.wmflabs.org/search/?q=iconTitle&i=nope&files=&repos=\\n    [x] Kartographer\\n    [x] BlueSpiceVisualEditorConnector\\n    [x] CollaborationKit\\n    [x] CX\\n    [x] LanguageTool\\n    [x] PerformanceInspector\\n    [x] WikibaseQualityConstraints\\n  [x] `setIconTitle` https://codesearch.wmflabs.org/search/?q=setIconTitle&i=nope&files=&repos=\\n    [x] MW core APISandBox\\n  [x] `indicatorTitle` https://codesearch.wmflabs.org/search/?q=indicatorTitle&i=nope&files=&repos=\\n  [x] `setIndicatorTitle` https://codesearch.wmflabs.org/search/?q=setIndicatorTitle&i=nope&files=&repos=\\n    [x] VE\\n[x] Remove – https://gerrit.wikimedia.org/r/#/c/oojs/ui/+/495949/'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-caadsxn4xg5gmxrpn6kz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-caadsxn4xg5gmxrpn6kz', 'dateClosed': 1552587519, 'spacePHID': None, 'dateCreated': 1417635365, 'dateModified': 1685041000, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Rename a lot of getters for consistency', 'description': {'raw': '[x] OO.ui.BookletLayout.prototype.getPageName ➞ OO.ui.BookletLayout.prototype.get**Current**PageName https://gerrit.wikimedia.org/r/#/c/177799/\\n\\n[x] OO.ui.BookletLayout.prototype.getClosestPage ➞ OO.ui.BookletLayout.prototype.**find**ClosestPage\\n** [x] Deprecate https://gerrit.wikimedia.org/r/#/c/375935/\\n** [x] Fix https://gerrit.wikimedia.org/r/#/c/375937/\\n** [x] Break https://gerrit.wikimedia.org/r/#/c/375936/\\n\\n[x] OO.ui.SelectWidget.prototype.getTargetItem ➞ OO.ui.SelectWidget.prototype.**find**TargetItem https://gerrit.wikimedia.org/r/#/c/375938/\\n\\n[x] OO.ui.SelectWidget.prototype.getFirstSelectableItem ➞ OO.ui.SelectWidget.prototype.**find**FirstSelectableItem\\n** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/376171/\\n** [x] Fix\\n*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/#/c/376172/\\n*** [x] VE ➞ https://gerrit.wikimedia.org/r/#/c/376177/\\n*** [x] VE extension ➞ https://gerrit.wikimedia.org/r/#/c/376175/\\n*** [x] MediaWiki core ➞ https://gerrit.wikimedia.org/r/#/c/376176/\\n*** [x] TemplateData extension ➞ https://gerrit.wikimedia.org/r/#/c/376174/\\n** [x] Break ➞ https://gerrit.wikimedia.org/r/#/c/376173/\\n\\n[x] OO.ui.SelectWidget.prototype.getHighlightedItem ➞ OO.ui.SelectWidget.prototype.**find**HighlightedItem\\n** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/376501\\n** [x] Fix ➞ https://gerrit.wikimedia.org/r/376502\\n** [x] Break ➞ https://gerrit.wikimedia.org/r/376503\\n\\n[x] OO.ui.SelectWidget.prototype.getRelativeSelectableItem ➞ OO.ui.SelectWidget.prototype.**find**RelativeSelectableItem\\n** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/376183\\n** [x] Fix\\n*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/376184\\n*** [x] Mediawiki core: RCFilter ➞ https://gerrit.wikimedia.org/r/376186\\n** [x] Break ➞ https://gerrit.wikimedia.org/r/376185\\n\\n[x] OO.ui.ToolGroup.prototype.getTargetTool ➞ OO.ui.ToolGroup.prototype.**find**TargetTool https://gerrit.wikimedia.org/r/#/c/375940/\\n\\n[x] OO.ui.GroupElement.prototype.getItemFromData ➞ OO.ui.GroupElement.prototype.**find**ItemFromData\\n** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398004/\\n** [x] Fix \\n*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/#/c/398209/\\n*** [x] ContentTranslation ➞ https://gerrit.wikimedia.org/r/#/c/398217/\\n*** [x] AdvancedSearch ➞ https://gerrit.wikimedia.org/r/#/c/398223/\\n*** [x] Echo ➞ https://gerrit.wikimedia.org/r/#/c/398224/\\n*** [x] Flow ➞ https://gerrit.wikimedia.org/r/#/c/400466/\\n*** [x] CentralNotice ➞ https://gerrit.wikimedia.org/r/#/c/400467/\\n*** [x] TemplateData ➞ https://gerrit.wikimedia.org/r/#/c/400468/\\n*** [x] VisualEditor ➞ https://gerrit.wikimedia.org/r/#/c/400470\\n*** [x] VisualEditor-MediaWiki ➞ https://gerrit.wikimedia.org/r/#/c/400469/\\n*** [x] MediaWiki ➞ https://gerrit.wikimedia.org/r/#/c/398221/\\n** [x] Break https://gerrit.wikimedia.org/r/#/c/415227/\\n\\n[x] OO.ui.GroupElement.prototype.getItemsFromData ➞ OO.ui.GroupElement.prototype.**find**ItemsFromData\\n** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398004/\\n** [x] Fix\\n*** [x] OOUI ➞ https://gerrit.wikimedia.org/r/#/c/398209/\\n*** [x] ContentTranslation ➞ https://gerrit.wikimedia.org/r/#/c/398217/\\n** [x] Break https://gerrit.wikimedia.org/r/#/c/415227/\\n\\n[x] OO.ui.SelectWidget.prototype.getSelectedItem ➞ OO.ui.SelectWidget.prototype.**find**SelectedItem\\n** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398005/\\n** [x] Fix\\n*** [x] OOUI: https://gerrit.wikimedia.org/r/#/c/403934/\\n*** [x] {T184037}\\n*** [x] {T184041} \\n*** [x] {T184040}\\n*** [x] {T184039}\\n*** [x] Kartographer: https://gerrit.wikimedia.org/r/#/c/404669/\\n*** [x] CentralNotice: https://gerrit.wikimedia.org/r/#/c/414935/\\n*** [x] CollaborationKit: https://gerrit.wikimedia.org/r/#/c/414936/\\n*** [x] Math: https://gerrit.wikimedia.org/r/#/c/404671/\\n*** [x] ContentTranslation: https://gerrit.wikimedia.org/r/414937\\n*** [x] UploadWizard: https://gerrit.wikimedia.org/r/414942\\n*** [x] ProofreadPage: https://gerrit.wikimedia.org/r/#/c/404673/\\n*** [x] MultimediaViewer: https://gerrit.wikimedia.org/r/#/c/414943/\\n*** [x] VE: https://gerrit.wikimedia.org/r/#/c/404667/\\n*** [x] VE-MW: https://gerrit.wikimedia.org/r/#/c/404666/\\n*** [x] Mediawiki core: https://gerrit.wikimedia.org/r/414944\\n** [x] Break https://gerrit.wikimedia.org/r/#/c/415229/\\n\\n[x] OO.ui.MultiselectWidget.prototype.getSelectedItems ➞ OO.ui.MultiselectWidget.prototype.**find**SelectedItems\\n** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398006/\\n** [x] Fix\\n*** [x] Mediawiki core: https://gerrit.wikimedia.org/r/#/c/415224/\\n*** [x] UploadWizard: https://gerrit.wikimedia.org/r/#/c/415225/\\n** [x] Break https://gerrit.wikimedia.org/r/#/c/415231/\\n\\n[x] OO.ui.MultiselectWidget.prototype.getSelectedItemsData ➞ OO.ui.MultiselectWidget.prototype.**find**SelectedItemsData\\n** [x] Deprecate ➞ https://gerrit.wikimedia.org/r/#/c/398006/\\n** [x] Fix\\n*** [x] UploadWizard: https://gerrit.wikimedia.org/r/#/c/415226/\\n** [x] Break https://gerrit.wikimedia.org/r/#/c/415231/\\n'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-gc5hdyw5p4np7atqjynz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1525726070, 'spacePHID': None, 'dateCreated': 1417634878, 'dateModified': 1653976241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'K3. Run Flow tests with Parsoid on Jenkins', 'description': {'raw': \"@EBernhardson said that they are currently run with wikitext (without Parsoid).  It would be good to run them with Parsoid (since that's our main backend) in addition to or instead of wikitext.\\n\\n--------------------------\\n**Trello card**: [[ https://trello.com/c/YpgazY2B/701-k3-run-flow-unit-tests-with-parsoid-3 | YpgazY2B ]]\"}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '3', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1417606214, 'dateModified': 1650450751, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Explore performance gains from progressive (JIT?) de-alienation of content types in VisualEditor', 'description': {'raw': 'See {T54365} for the same idea, but for content blocks.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1417567272, 'dateModified': 1692389652, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Client-side approach to true section editing: Load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document', 'description': {'raw': 'Somehow(?) load/display document-level data (e.g. internal lists, meta lists) for the whole document but only the content for a part of the document.\\n\\nWill probably need {T49344} for the document splitting.\\n'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1552002023, 'spacePHID': None, 'dateCreated': 1417566671, 'dateModified': 1573262500, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor image resize icon must be flipped and moved to the opposite edge for RTL wikis', 'description': {'raw': 'The VisualEditor image resize icon must appear on the inner side of the page (inner in relation to the page). For RTL now it appears on the outer edge, which makes it not really usable. The direction of the arrow heads must be flipped, too.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1417526272, 'dateModified': 1691594500, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Blockquotes aren't ContentBranchNodes in reality, and our code shouldn't try to insist that they are\", 'description': {'raw': \"This is valid HTML:\\n```\\n<blockquote>\\n<p>\\nFoo\\n</p>\\n<p>\\nBar\\n</p>\\n</blockquote>\\n```\\nBut when such structure is edited in VE, the inner paragraphs get alienated.\\n//*sighs*//\\n\\n>>! In T154231, @dchan wrote:\\n> At present, BlockquoteNode behaves like a ContentBranchNode ; it should not.\\n> \\n> Right now, ve.ce.BlockquoteNode extends ve.ce.ContentBranchNode, but ve.dm.BlockquoteNode extends ve.dm.BranchNode . I would say BranchNode is the correct parent, because HTML blockquote elements can contain flow content such as paragraph elements (see https://html.spec.whatwg.org/multipage/semantics.html#the-blockquote-element ).\\n> \\n> If however there's some special weird reason to treat BlockquoteNode as a ContentBranchNode, then I'll implement that instead and document the special weird reason.\\n\\n>>! In T154231#2913587, @Jdforrester-WMF wrote:\\n> ISTR there is — or at least, was — a solid reason for doing this. But I don't recall at all what it was.\\n\\n>>! In T154231#4000786, @matmarex wrote:\\n> It seems the reason was that we treat it as a top-level block element, like paragraphs or heading.\\n> \\n>>>! @Esanders in https://gerrit.wikimedia.org/r/#/c/329448/\\n>> This is probably correct but it means we have to come up with a new tool for inserting block quote, as it is currently treated as a CBN conversion in the format dropdown. I think we did it that way because most blockquotes are only one paragraph.\\n>> \\n>> Alternatively, we could go the other way and make it fully ContentBranchNode, at least for the time being.\\n> \\n> It was actually changed to be fully ContentBranchNode in 94dbb244dd.\\n\\n\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1559171319, 'spacePHID': None, 'dateCreated': 1417481643, 'dateModified': 1559171320, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'New search interface for link dialogue', 'description': {'raw': 'As a new editor I want to see more information about pages so that I can choose the correct 1 to link to.\\n\\nProblem: The existing search interface doesn\\'t look like a list of articles on Wikipedia. \\nBased on usability testing, this is rated a 3 - Major usability problem: important to fix, so should be given high priority.\\nhttps://www.mediawiki.org/wiki/VisualEditor/Usability#Creating_a_link\\n\\nView click-through prototype here http://invis.io/NP2TOI4GU\\n\\n{F34278}\\n\\nTitle area of dialogue shows Link icon, \"Link to page\" and \"External link\". Clicking External link will take user to T76398\\n\\nThe search field will be filled with the text the user has selected to link.\\n\\nThe search items show:\\nImage thumbnail, article title, wikidata description\\nArticle icon if no lead image\\nIndicate Redirect to [[article]] with redirect icon\\nIndicate disambiguation page with its icon\\nEmpty page icon if redlink\\n\\n'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1430327853, 'spacePHID': None, 'dateCreated': 1417474573, 'dateModified': 1660398883, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Incorrect Parsoid output for image wrapped in bold and paragraph', 'description': {'raw': 'For this wikitext: \\n```\\n<p>\\'\\'\\'[[File:Wiki.png|thumb]]\\'\\'\\'</p>\\n```\\nParsoid produces HTMLDOM that has bold tag inside anchor tag inside figure tag - which is not consistent with https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec\\n```\\n<!DOCTYPE html>\\n<html prefix=\"dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/\"><head prefix=\"mwr: http://en.wikipedia.org/wiki/Special:Redirect/\"><meta property=\"mw:articleNamespace\" content=\"0\"/><meta property=\"mw:parsoidVersion\" content=\"0\"/><link rel=\"dc:isVersionOf\" href=\"//en.wikipedia.org/wiki/Main%20Page\"/><title></title><base href=\"//en.wikipedia.org/wiki/\"/><link rel=\"stylesheet\" href=\"//en.wikipedia.org/w/load.php?modules=mediawiki.legacy.commonPrint,shared|mediawiki.skinning.elements|mediawiki.skinning.content|mediawiki.skinning.interface|skins.vector.styles|site|mediawiki.skinning.content.parsoid&amp;only=styles&amp;debug=true&amp;skin=vector\"/></head><body data-parsoid=\\'{\"dsr\":[0,37,0,0]}\\' lang=\"en\" class=\"mw-content-ltr sitedir-ltr ltr mw-body mw-body-content mediawiki\" dir=\"ltr\"><p data-parsoid=\\'{\"stx\":\"html\",\"autoInsertedEnd\":true,\"dsr\":[0,6,3,0]}\\'><b data-parsoid=\\'{\"autoInsertedEnd\":true,\"dsr\":[3,6,3,0]}\\'></b></p><figure class=\"mw-default-size\" typeof=\"mw:Image/Thumb\" data-parsoid=\\'{\"optList\":[{\"ck\":\"thumbnail\",\"ak\":\"thumb\"}],\"dsr\":[6,29,2,2]}\\'><a href=\"./File:Wiki.png\" data-parsoid=\\'{\"a\":{\"href\":\"./File:Wiki.png\"},\"sa\":{},\"dsr\":[8,27,null,null]}\\'><b data-parsoid=\\'{\"tsr\":null,\"autoInsertedEnd\":true,\"autoInsertedStart\":true}\\'><img resource=\"./File:Wiki.png\" src=\"//upload.wikimedia.org/wikipedia/en/b/bc/Wiki.png\" height=\"155\" width=\"135\" data-parsoid=\\'{\"a\":{\"resource\":\"./File:Wiki.png\",\"height\":\"155\",\"width\":\"135\"},\"sa\":{\"resource\":\"File:Wiki.png\"}}\\'/></b></a></figure><p data-parsoid=\\'{\"autoInsertedStart\":true,\"stx\":\"html\",\"dsr\":[32,36,0,null]}\\'></p>\\n</body></html>\\n```\\nIt breaks rendering for such wikitext in VisualEditor.'}, 'authorPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1438291931, 'spacePHID': None, 'dateCreated': 1417463326, 'dateModified': 1438294521, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Goal: Newsletter extension for MediaWiki', 'description': {'raw': \"NOTE: This Google Summer of Code project has been completed successfully. Thank you @tinaj1234 for your contributions, and thank you @01tonythomas for your technical mentoring. This team has worked very well so far!\\n\\nFor details, read {T109288}.\\n\\nThe work continues at {T110170}. As always, your feedback and contributions are welcome. This is not an internship project anymore; patches are very welcome.  :)\\n\\n== Newsletter extension ==\\n\\nAn extension allowing publishers to create newsletters and announce new issues, and allowing users to browse and subscribe to newsletters.\\n\\nA #Google-Summer-of-Code-2015 project lead by @tinaj1234, mentored by @01tonythomas and @qgil.\\n\\nCurrently working on {T99784} and blockers.\\n\\nWeekly reports: T100997\\nWeekly meetings: every [[ http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150605T1030 | Thursday at 10:30 UTC ]] (4pm IST, 12:30 CEST, 3:30 PST) in `#wikimedia-ect` IRC. \\nURL of web proxy of Labs instance where development takes place : http://newsletter-test.wmflabs.org/\\n\\n== Plan ==\\n\\n=== Readers ===\\n\\n* **A catalog of newsletters in one multilingual wiki** (Meta). Let's start defining a single translatable location to find all the newsletters. Meta is the logical choice. No matter which project the newsletter authors come from, all of them would create and organize their newsletters in a common location.\\n* Easy subscription. As a logged-in user, click a button. As anonymous user, log in or create an account. (Ideally just entering an email address would work too, with confirmation). Question: should an email address in your profile be required? Can this be checked? Echo probably has solved this.\\n* A notification is received when a new issue is published. Notifications are handled via Echo, and therefore they can be received via web or email according to user preferences.\\n* Easy to unsubscribe. As a logged-in user, click a button. Accessing a URL from notifications should unsubscribe you as well, after confirmation.\\n* Usernames and emails of subscribes should be kept private. The number of users subscribed to a newsletter would be public (and eventually used to promote popular newsletters).\\n\\n=== Publishers ===\\n\\n* A process defining the conditions in which a newsletter can be created, featured, demoted, closed (actions that might imply database changes). Just a basic framework to promote best practices and prevent abuse.\\n* Once a newsletter is created, maintaining the content (homepage, subpages) could be done in a plain wiki way for creating pages, watching, editing, reverting, protecting if needed... New content is in practice a draft, since it hasn't been announced to the subscribers. Whoever wants to watch changes can read the drafts and get involved.\\n* Once a new issue (a page) is ready, the owners of the newsletter send a notification. This requires special permissions.\\n\\n**Permissions**\\nAny autoconfirmed user can become a publisher - create newsletters, announce issues, manage newsletters because of two particular reasons ( quoting Quim ):\\n  # Autoconfirmed users can create newsletter pages and issues anyway (even anonymous can).\\n  # Even if a publisher were to cause any kind of damage it will affect popularity of their newsletters as well. The extension takes care of subscriptions to the newsletter and notifications from newsletters and hence the creation of newsletters and issues are external to our extension.\\n=== Newsletters ===\\nA newsletter generally has one or more of the following properties (some newsletters have more of these than others):\\n\\n* Home page: a page that contains information about the newsletter and what it contains\\n* Current issue page: self-explanatory\\n* Archive pages: past editions of the newsletter that were previously published\\n* Authors / Editors: a group of people that are allowed and/or expected to contribute content\\n* Publishers: a group of people that are allowed to finalize an edition and publish it to readers\\n\\nMost likely, showing a user (on the preferences page mentioned above) a link to the home page, a description of the newsletter, and maybe a link to the current issue and archive pages would be useful.\\n\\nAs mentioned in a comment below, it would probably be best to shift management of authors and editors to the existing page protection feature, i.e., if the newsletter really needs to be protected from unauthorized editing, make a restriction level and assign authors the necessary permission. Publishers would probably need separate management, and would probably be maintained in the same interface that information about the newsletter itself is maintained.\\n\\n===Backend===\\nCheck this Etherpad entry on discussions with hoo: https://etherpad.wikimedia.org/p/newsletterExtension\\nWhile discussing with other developers, we realized there are two options for the extension's backend architecture - either use Contenthandlers or use Database( sql tables ). As of now while we prepare the patches for MVP, the database approach is taken. To choose the best for the extension out of all available options at it's earliest stages of development would be the apt thing to do, hence opening up this section for further discussions.\\n\\n=== See also ===\\n\\n* https://www.mediawiki.org/wiki/Extension:Newsletter\\n* https://meta.wikimedia.org/wiki/Grants:IdeaLab/Newsletter_extension_for_MediaWiki\\n\\n===Proposed Schedule===\\n\\n| **Tasks to be completed **|**Timeline**|**Remarks**|\\n|Create Wikimedia Labs project, create instance, community bonding| 28/03/15 - 30/04/15| Created Labs project 'newsletter' and instance, 'newsletter-test'. Successfully ssh-ed to the instance|\\n|Decide on MVP plan and create necessary tasks|01/05/15 - 05/05/15|Done |\\n|Create the Special:NewsLetterCreate interface, and design DB ( the new table )| 06/05/15 - 10/05/15|Done |\\n|Create the Special:NewsLetterManage interface - Publisher's view, Newsletter skeleton| 20/05/15 - 30/05/15|Done |\\n|Create Special:Newsletters and deploying features on vagrant| 31/05/15 - 15/06/15|Done |\\n|Adding newsletter in Notifications tab of Special:Preferences and completing T101546| 16/06/15 - 24/06/15|Done |\\n|  Mid Term Evaluation| 26/06/15 - 03/07/15|Done |\\n| Work on Blockers and complete extension considering case of Meta alone and no inter wiki newsletters| 04/07/15 - 20/07/15|Done |\\n| Work on T102945, T101832, T104829| 21/07/15 - 10/08/15|Done |\\n| Writing unit tests, testing the work flow, documentation, deployment | 11/08/15 - 20/08/15|Done|\\n| Final Report Submission| 21/08/2015|Done |\"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-3pzrnfkwxgwn4v6askvo', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1440494638, 'spacePHID': None, 'dateCreated': 1417165348, 'dateModified': 1471120785, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create Spelling-Dictionary project', 'description': {'raw': \"**Name:** Spelling-Dictionary\\n\\n**Type of Project:** Project, #spelldict\\n\\n**Policy:** Visible To Public \\n\\n**Description:** Spelling dictionaries for the major languages of the world (English, Italian, French) help make Wikipedia articles in these languages more readable and professional and provide an opportunity for participation in improving spelling. Many languages, however, don’t have spelling dictionaries.\\n\\nThis project aims at developing a collaborative dictionary which shall also have an additional feature of checking spellings of the words. This is to be achieved with the collaborative efforts of the mediawiki community using crowd-sourcing, as a MediaWiki extension integrated with VisualEditor, and possibly using Wikidata as a backend. We need to create something that's useful as VE module.\\n\\nThe essence of the project shall aim to develop an admin panel where the administrator/moderator will be able to manage the submissions: verify the suggested spellings of the words, accept them, reject them, filter and build new versions of the spelling dictionary upon them. A simple start to the project could be by starting with a simple list of words.\\n\\nThe detailed time line can be read [[ http://www.mediawiki.org/wiki/User:Ankitashukla/Proposal | here ]]\"}, 'authorPHID': 'PHID-USER-vktcpyhhgydpo36f44uz', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1417602843, 'spacePHID': None, 'dateCreated': 1417122558, 'dateModified': 1468888773, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Fix browsertests-VisualEditor-language-screenshot-windows_8.1-firefox Jenkins job', 'description': {'raw': 'The job: [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/VisualEditor/job/browsertests-VisualEditor-language-screenshot-windows_8.1-firefox/ | browsertests-VisualEditor-language-screenshot-windows_8.1-firefox ]]'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1424769641, 'spacePHID': None, 'dateCreated': 1417084690, 'dateModified': 1438736461, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression wmf10] <visualeditor-formatdropdown-format-blockquote> is displayed in Headings menu ', 'description': {'raw': 'Open VE-> Heading - under sub-heading 4, visualeditor-formatdropdown-format-blockquote will be displayed from <span class=\"oo-ui-tool-title-text\">&lt;visualeditor-formatdropdown-format-blockquote&gt;</span>(see the attached screenshot).\\n{F16461}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417228531, 'spacePHID': None, 'dateCreated': 1417031233, 'dateModified': 1417228531, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Loading indicators / Progress indicators are inconsistent. ', 'description': {'raw': 'There\\'s a range of different loading indicators in Wikimedia Foundation products. \\nLet\\'s unify them.\\n\\n=== Standard progress indicators\\n==== Progress bar (application, elevated above view)\\n- **VisualEditor** -   [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=widgets&theme=wikimediaui&direction=ltr&platform=desktop#Progress-bar | ProgressBarWidget (OOUI widget)]] as elevated application loading indicator\\n{F33930009 width=50%}\\n\\n==== Progress indicator (in page)\\n- **Three (bouncing) dots** for in-view loading content, for example RCFilters\\n  [[ https://codepen.io/Volker_E/pen/yqNXMe | CodePen with dots indicator example at 16px ]]. Depending on context product designers can also choose to go for 12px dot sizes. \\n\\n\\n---\\n\\n=== //Outdated, non-standard// progress indicators in Foundation products\\n\\n**Content translation** - loading article (content). \\n{F3067365}\\n\\n**Notifications** - loading notifications (content) \\n{F3067366}\\n\\n**Structured Discussion** - loading more topics (content) \\n|{F27614503}|{F3067367} \\n\\nloading contents on infinite scroll\\n{F3068028}\\n\\n**MobileFrontend** - loading \"nearby\" articles (content) \\n|{F27614726}|{F3067368}\\n\\n---\\n**Related notes:**\\n- User:Splarka has done some analysis [[ https://www.mediawiki.org/wiki/User:Splarka/Throbber | here ]] to see how loaders work in different colored backgrounds. \\n- Relevant [[ https://phabricator.wikimedia.org/T95137 | task about loading indicators should accelerate as it nears completion ]]\\n- {T78062}\\n\\n'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1416989044, 'dateModified': 1730913100, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'A message key appears instead of the actual message in visualeditor-dialog-meta-settings-newsectioneditlink-help', 'description': {'raw': 'In the help bubble that shows the message visualeditor-dialog-meta-settings-newsectioneditlink-help, the message \"vector-view-edit\" is mentioned. It is supposed to show \"Edit\" to the user, but it shows \"[vector-view-edit]\" instead. The value of the message should probably be sent as a parameter instead of using {{int:vector-view-edit}}.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417478296, 'spacePHID': None, 'dateCreated': 1416984339, 'dateModified': 1438736338, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create technical-debt project', 'description': {'raw': 'Name: technical-debt\\nType of project: Tag\\nDescription:\\n\\nTechnical debt (also known as design debt[1] or code debt) is a recent metaphor referring to the eventual consequences of poor system design, software architecture or software development within a codebase. The debt can be thought of as work that needs to be done before a particular job can be considered complete or proper. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on. Unaddressed technical debt increases software entropy. - https://en.wikipedia.org/wiki/Technical_debt\\nExamples: Missing unit tests, duplicate code.\\n'}, 'authorPHID': 'PHID-USER-mdihg2tyzmlvyhn3h32y', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418076522, 'spacePHID': None, 'dateCreated': 1416928132, 'dateModified': 1468889425, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cancel button does not work for Insert-Template and some Cite options in VisualEditor in Monobook', 'description': {'raw': 'The dialog boxes that have extremely small font(T75800)  get stuck on the screen when Cancel button is clicked. \\n\\n1. VE in beta with redirect=no&veaction=edit&useskin=monobook\\n2. Insert -> Template - click Cancel- nothing happens; the dialog box gets stuck on the screen, need to refresh.\\n\\nThe same issue with Cancel in Cite-Website, Book, News, Journal.\\n '}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1417561024, 'spacePHID': None, 'dateCreated': 1416870621, 'dateModified': 1438736346, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Update bits of VisualEditor still referring to Bugzilla', 'description': {'raw': 'The \"Leave feedback\" option in VE allows to report a bug:\\nThe \"list of known bugs\" link should point to its equivalent here;\\nThe \"I checked, report a new bug\" button needs to point to the (possibly partially pre-filled) task creation form here.\\n'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420464636, 'spacePHID': None, 'dateCreated': 1416833813, 'dateModified': 1427672967, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add an explanation about Alternative text in the media adding dialog', 'description': {'raw': 'The \"Alternative text\" label in the VisualEditor media adding dialog is not entirely clear to people who aren\\'t familiar with web authoring and accessibility technologies. It would be useful to add a little explanation in a small font near that label, that would explain what is alternative text for and how to write it so it will be really useful.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422846929, 'spacePHID': None, 'dateCreated': 1416831637, 'dateModified': 1427672928, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Decide what to do with tracking bugs', 'description': {'raw': 'There are a lot of them, see T4007 and the #tracking tag.\\n\\nI suppose they should eventually all be closed and replaced with tags or projects.\\n\\nSee also T266.'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1425050149, 'spacePHID': None, 'dateCreated': 1416790347, 'dateModified': 1469809317, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  When I click the Save button, please take my cursor out of the main text and focus it in the Save dialog', 'description': {'raw': 'Goal:\\n\\nSave page with edit summary \"Copyedit\".\\n\\n\\n(Almost) result:\\n\\nSave page with no edit summary, but with the word \\'Copyedit\\' added in the middle of the link that I had just fixed.\\n\\n\\nSteps to reproduce:\\n\\n1) Edit any page.\\n\\n2) Click the save button.\\n\\n3) Start typing your edit summary.\\n\\n4) Stop typing your edit summary and start backspacing.\\n\\n5) Click inside the Save dialog.\\n\\n6) Type your edit summary again.\\n\\n7) File another bug in Bugzilla.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420599707, 'spacePHID': None, 'dateCreated': 1416516180, 'dateModified': 1427672980, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73675', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: mw.Target / ViewPageTarget re-write', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1416365160, 'dateModified': 1643977414, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73593', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Decide whether this.active should be in mw.Target or mw.ViewPageTarget', 'description': {'raw': \"Right now ViewPageTarget defines this.active, but it's set to true by mw.Target. This is horrible. The obvious fix is to push the setting to true down to ViewPageTarget, but we should consider whether the Target class itself should have some sort of active state.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1416364980, 'dateModified': 1643977414, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73591', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Improve FileDropHandler API', 'description': {'raw': 'From comments at https://gerrit.wikimedia.org/r/#/c/173296/1/src/ui/filedrophandlers/ve.ui.DSVFileDropHandler.js :\\n\\n* Right now every child class calls createProgress( insertableDataDeferred.promise() ); in its process() method. This seems like something that should be in the base class instead. Would you ever want to not do that, or pass a different promise?\\n\\n* Child classes should not have to override abort() just to add this.reader.abort();, because this.reader is added by the base class.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1416338940, 'dateModified': 1643977414, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73570', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Warn if editing a citation that is used multiple times', 'description': {'raw': 'The fix 52792 will display a warning \"This reference is used [n] times on this page.\" when editing Basic citation only. \\n\\nApply the same warning when editing mutliple instances of any kind of citations.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1416331860, 'dateModified': 1643977415, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73566', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor in ca.wikiquote.org', 'description': {'raw': \"Hi, I'm posting this request on behalf of the https://ca.wikiquote.org admins. They want to bring VisualEditor to their users. We have discussed this idea, and I see no problem at all. At the end, most articles there have a very simple structure with initial paragraph, some pictures, and then the same template used always for adding quotes.\\n\\nI would be happy to help adding template data to the templates affected, and act as bridge in this test.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**URL**: https://ca.wikiquote.org/wiki/Viquidites:La_taverna#Editor_Visual_a_Viquidites\"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416330181, 'spacePHID': None, 'dateCreated': 1416135000, 'dateModified': 1602870156, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73483', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Undefined index: newtimestamp in …/ApiVisualEditorEdit.php', 'description': {'raw': 'Nov 15 12:32:30 mw1023:  #012Notice: Undefined index: newtimestamp in /srv/mediawiki/php-1.25wmf7/extensions/VisualEditor/ApiVisualEditorEdit.php on line 137\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416246510, 'spacePHID': None, 'dateCreated': 1416055080, 'dateModified': 1417571386, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73463', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector does not function correctly after closing it using \"Done\"/\"Remove\" button in Firefox while the cursor is never active on CE', 'description': {'raw': 'edit a page on beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit\\n\\nClick the Link inspector. Note the local link created.\\n\\nClick Remove. \\n\\nClick the Link inspector again. \\n\\nSee an entirely different UI showing \"New page/Matching pages\"\\n\\nClick in the ContentEditable part. \"New page/Matching pages\" UI disappears. \\n\\nClick the Link inspector again. \\n\\nNothing happens. Link inspector stops working completely.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1444488231, 'spacePHID': None, 'dateCreated': 1415985480, 'dateModified': 1444488241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73423', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression] Gallery gets added into media, if there is/was something in the media's caption\", 'description': {'raw': 'Gallery with caption gets added to the table inside the image\\n\\nEnvironment- test2, beta, production\\n\\n1> Insert -> media \\n2> insert a table in the caption sub- editor of Media Settings.Click to insert to the main editor.\\n2> Highlight the media, insert a gallery with just caption(no filename).\\n3> Now drag and drop the gallery on to the table inside the image. Notice the gallery gets added to the table inside the image.\\n4> click on the image’s context menu to go to media settings, notice the gallery shows up in the caption pane.See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15189}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416257466, 'spacePHID': None, 'dateCreated': 1415890380, 'dateModified': 1417571382, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73368', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor by default for all users on the Tagalog Wikipedia (currently a Beta Feature there)', 'description': {'raw': 'See https://tl.wikipedia.org/wiki/Wikipedia:VisualEditor/Komentaryo#Did_you_know_why.3F .\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**URL**: https://tl.wikipedia.org/wiki/Wikipedia:VisualEditor/Komentaryo#Did_you_know_why.3F'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416271503, 'spacePHID': None, 'dateCreated': 1415886300, 'dateModified': 1416271503, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73365', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector opens in a upper left corner in Safari', 'description': {'raw': 'Link inspector opens at the upper left corner\\n\\nOnly Safari(betalbs, test2, production)\\n\\n1. In VE type a word and convert it into a link.\\n\\n2. Place a cursor at the end of the word - the link inspector opens at the upper left corner of the screen. The screenshot is attached. \\n\\nNote: The link inspector opens correctly if the cursor is placed in the middle of an inserted link. Place a cursor at the end of the link and start moving left - the position of the link inspector will be changed from the correct.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15101}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416246810, 'spacePHID': None, 'dateCreated': 1415833020, 'dateModified': 1438736653, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73336', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Magic words like ISBN links in templates are rendered as red links now', 'description': {'raw': \"This is bug 72251 for magic words.  \\n\\n{{cite book|isbn=1234567890}} displays as a redlink, and it shouldn't.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415918355, 'spacePHID': None, 'dateCreated': 1415816280, 'dateModified': 1417571386, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73320', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Drag-and-drop of a block image doesn't remove the marker lines sometimes (?)\", 'description': {'raw': 'screenshot in chrome\\n\\nEnvironment- test2, beta\\n\\n1> Insert a media with default settings.\\n2> keeping the media highglighted,insert a gallery with just caption(no filename).\\n3> Now drag and drop the gallery to the image and then image to the gallery. Either way it draws focusablenode dropmarker lines above and below the media content. See screenshots.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14939}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1415724180, 'dateModified': 1416791821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73275', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When selecting FocusableNode with arrow keys, context flickers at position of last mouse click', 'description': {'raw': \"1. Open a document that contains a line of plain (not linked) text with an inline focusable node (e.g. template or reference)\\n2. Use the mouse to put the cursor on this line, some distance away from the text\\n3. Use the arrow keys to move the cursor to the focusable node\\n4. When the node is focused, the context flickers in the position where you clicked in step 2 before moving to the focusable node\\n\\nThis doesn't happen when you use the mouse to focus the node. It also doesn't happen when the context appears for an annotation (e.g. link).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416256606, 'spacePHID': None, 'dateCreated': 1415654940, 'dateModified': 1417571381, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73242', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Auto-save to increase chances of lost edits recovery', 'description': {'raw': 'Proposed in #community-wishlist-survey-2016. Received 41 support votes and was ranked #31 out of 265 proposals. [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Editing#Auto-saving_edits | View full discussion and votes here ]].  \\n\\n----\\n\\nAs a use who is preparing an edit, I\\'d like to be confident that if some bad interruption happens before I save it (e.g. power outage) I\\'ll likely be able to recover most of my work when I try to edit the page again, even if other countermeasures (e.g. browser cache, local copy) are missing or failed.\\n\\nLocal vs. remote storage, frequency of autosave, expiry etc. are negotiable. The less interface there is, the better; there should be no added preference(s).\\n\\nCreating because of https://lists.wikimedia.org/pipermail/wikitech-l/2014-November/079378.html and the lack of a bug in core to track this.\\n\\n----\\n\\nSomething else that I have had in the pipeline for a long while is autosave drafts. Basically, whenever you type, the article is saved to your local computer. If the browser crashes, and you visit the same article, it will prompt you for recovery. Making a Special:Autosave drafts index page would be trivial.\\n\\nImplementation:\\nhttps://gerrit.wikimedia.org/r/#/c/5130/ <https://gerrit.wikimedia.org/r/#/c/5130/>\\n\\nOf this, I also have an alternate implementation:\\nhttps://gerrit.wikimedia.org/r/#/c/157818/ <https://gerrit.wikimedia.org/r/#/c/157818/>\\nhttps://gerrit.wikimedia.org/r/#/c/159626/ <https://gerrit.wikimedia.org/r/#/c/159626/>\\n\\nThe original one is based on code by Joancreus and uses localStorage. It works, quite well actually, but while improving it, I became of the opinion that localStorage is basically so limited in storage and gives you so little feedback as an API and an enduser, that it\\'s not really suited for much more than usersettings (big cookies). Not for saving potentially multiple 1MB articles, with structured details.\\n\\nAs a storage layer, indexedDB is much nicer in that regard. API wise, it\\'s a bit convoluted, but a jQuery plugin makes it usable and readable. There are WebSQL polyfills for platforms that don\\'t have indexedDB, which would allow us to support browsers of the past 6 years.\\n\\nI would like some opinions on which way to go here. Additionally, i would love to hear what else people think would be required to make this usable for the Wikipedia audience and the naming. Would this be Drafts ? Autosave drafts ? autosave ? Would you say \\'recover\\' when asking the user to use the version from drafts, or just \\'use draft\\' etc?\\n\\nNote that the \\'2nd\\' version also has a few more improvements like a separate RL module and a preference option, but those can easily be added to the first implementation as well. \\n\\n----\\n\\nClearly, I prefer the word \"autosave\", which reminds people of the recovery features endemic in any document editing software; rather than \"draft\", which in the past caused a lot of confusion. LibreOffice, when restarted, asks if you want to \"recover\" a previous document, and many other FLOSS productivity softwares use the same terminology: what do they do on the devil\\'s side (M$ and Apple)?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**Possible consumers**:\\n* VisualEditor ({T57370})\\n* ContentTranslation, T113221#1844393 (currently DB-based: {rECTX00ebcc6e3e31b278092abde755cbd9009ef65cf4})\\n**See Also**:\\n* {T39992}\\n* {T11749}'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-hlhhe6qw6qfkl7wyfhxk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-hlhhe6qw6qfkl7wyfhxk', 'dateClosed': 1690505060, 'spacePHID': None, 'dateCreated': 1415654160, 'dateModified': 1729681457, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73241', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Drag-and-drop in IE9 doesn't work\", 'description': {'raw': \"I can successfully drag-n-drop an image from one part of the page to another in VE while using Chrome and Firefox, but not IE.\\n\\nChrome and FF provide feedback, indicating where the object will land if it is dropped, but IE doesn't.  Nor does dropping the object move it.\\n\\nI don't see any errors in the js console on IE during this process.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51669\"}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1461110878, 'spacePHID': None, 'dateCreated': 1415653560, 'dateModified': 1461111218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73240', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Removing table row where rowspanned cell starts un-merges the remaining spanned cells', 'description': {'raw': 'Removing the table row where rowspanned cell starts un-merges the remaining spanned cells.\\n\\n1. Look at the tables.html demo.\\n2. In \"Merged cells\" example, place cursor at the \"10\" cell.\\n3. Delete row.\\n\\nThe \"4\" cell has correctly changed from spanning three to two rows. However, the \"9\" cell has split into three cells, while it should have been changed from spanning four to three rows instead.\\n\\nAnalogous behavior occurs when removing the column where a colspanned cell starts. (Try with the \"16\" cell.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415645479, 'spacePHID': None, 'dateCreated': 1415582400, 'dateModified': 1417571390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73213', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Insert table\" tool in a separate menu to the other table tools (delete/merge/caption)', 'description': {'raw': 'VisualEditor: \"Insert table\" tool should be (also?) in the \"Table\" menu, not (or in addition to?) \"Insert\" menu. I was quite confused for a moment by the table icon being grayed out, and I\\'ve been told I\\'m not the only one.'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1454351561, 'spacePHID': None, 'dateCreated': 1415582100, 'dateModified': 1454539173, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73212', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When making a VisualEditor edit then marking the page as reviewed, the VisualEditor edit does not get marked reviewed', 'description': {'raw': \"After editing an unreviewed page using VisualEditor, reviewing the page doesn’t review the just-made edit if the page isn’t reloaded between publishing the edit and pressing review.\\n\\nHow to reproduce:\\n1) go to some article that hasn't been reviewed yet\\n2) make an edit to the article using Visual Editor. save the edit\\n3) review the article\\n4) when you look at the article history you can see that the article you marked as reviewed has one unreviewed change (the one you just did using VE)\\n\\nI tried this at https://test2.wikipedia.org/wiki/Testing_something\"}, 'authorPHID': 'PHID-USER-6majuboi566q3ozbh27r', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'bug', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1415453100, 'dateModified': 1731804456, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: IE11- inserting  a link with a shortcut(Cmd+K) opens and closes the link inspector momentarily', 'description': {'raw': \"Splitting the bug from 72392.\\n\\nOpen a page in VE and insert a link with the shortcut - Ctrl+K - the link inspector opens and closes momentarily. \\n\\nThe console displays the following(consistently): \\n\\nDOM7009: Unable to decode image at URL: 'data:image/gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA'.  File: gif;base64,R0lGODdhAQABAADcACwAAAAAAQABAAA\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1460644310, 'spacePHID': None, 'dateCreated': 1415390280, 'dateModified': 1462842909, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73154', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: handling preformatted text in tables', 'description': {'raw': \"Preformatted text in tables\\n\\nIn betalabs\\n\\n1. In VE insert a table and double-click in any cell to make it editable.\\n\\n2. Select the 'preformatted' option - the cell will be yanked from the table(similar to bug 72990). The preformatted are will be displayed outside of the table. \\n\\nThe same happens when you apply preformatted to the cells' text.\\n\\nLook at the screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15190}\"}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415581929, 'spacePHID': None, 'dateCreated': 1415313600, 'dateModified': 1417571384, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73100', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: Use PHP Virtual REST Service to access Parsoid', 'description': {'raw': 'From gerrit 170869:\\n> Gabriel suggested that in the future we migrate to the PHP Virtual REST Service and through that share code between Flow, VE and anything else that wants to talk with parsoid.\\nhttps://www.mediawiki.org/wiki/Requests_for_comment/PHP_Virtual_REST_Service\\n\\nWith [[ https://gerrit.wikimedia.org/r/#/c/181011/ | gerrit 181011]] VisualEditor is doing this, so Flow can do the same and remove whatever cookie hacks @Ebernhardson needed to access Parsoid from the private officewiki.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1415138880, 'dateModified': 1621977010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72988', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.', 'description': {'raw': 'screenshot of JS errors in beta\\n\\nEnvironment- test2, beta\\n\\n1> In a blank page, open the Language inspector.\\n2> While the inspector is open ,select any Heading format from the drop-down,for ex- select Heading.\\n2> The inspector closes and you see the language context menu. \\n3> type in some text, it doesn’t take the language annotation(looks like plain paragraph text)\\n4> Hit enter and JS error “Uncaught Error: Inserted data is trying to close the root node (at index 0)”. See screenshot.\\n5> Notice no matter where your cursor is on the page, the language context menu never moves from its place or closes for a new line.\\n\\nIn beta an additional  JS error appears at step#2, “Uncaught Error: Offset could not be translated to a DOM element and offset: 2”.\\n\\nReproducible in FF too.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Windows XP\\n\\n**Attached**: {F14776}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1629314979, 'spacePHID': None, 'dateCreated': 1415115600, 'dateModified': 1629314980, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72950', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"OOjs: v8 warns it won't optimize oo.Factory.create or oo.EventEmitter.emit\", 'description': {'raw': 'To reproduce:\\n\\n- Navigate to an article\\n- Open Chrome\\'s Developer Tools\\n- Click \\'Profiles\\'\\n- Select \\'Collect JavaScript CPU Profile\\'\\n- Click \\'Start\\'\\n- Click \\'Edit [beta]\\'\\n- Wait for VisualEditor to finish loading\\n- Click \\'Stop\\'\\n\\nResult:\\n\\nBoth oo.Factory.create or oo.EventEmitter.emit are flagged by the profiler with the warning: \"Not optimized: Inlining bailed out.\"\\n\\nTo investigate, I recommend reading <https://github.com/GoogleChrome/devtools-docs/issues/53>\\n\\nv8 comes with a \\'d8\\' executable that can be used for getting some performance debug info from v8. If you can craft a file that utilizes these functions without depending on the DOM API, you can try running it with:\\n\\n> d8 --trace-opt --trace-bailout some-js-file.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422040341, 'spacePHID': None, 'dateCreated': 1415064480, 'dateModified': 1597413055, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72933', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Save page dialog's edit summary text box is black in Internet Explorer 11\", 'description': {'raw': \"Edit summary textbox is black\\n\\nSteps to reproduce: \\n\\n In IE 11 perform some editing in VE and click Save page.\\n\\nObserve: 'Edit summary' text box is displayed black. When clicked in it - it becomes white. \\n\\nThe screenshot is attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15398}\"}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1461096698, 'spacePHID': None, 'dateCreated': 1415045640, 'dateModified': 1462842901, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72917', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Restore selection when user exits the save dialog (on clicking \"Resume editing\")', 'description': {'raw': 'Edit any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/Media_Interface_VisualEditor_Test?veaction=edit\\n\\nPerform some action, for example highlight text and indent some. \\n\\nClick Save page and then click Resume editing from the Save modal dialog.\\n\\nUpon returning to the edit page, VE edit tools should be enabled but are not enabled.  User must click again in the CE area to enable edit tools.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415820208, 'spacePHID': None, 'dateCreated': 1415037480, 'dateModified': 1417571382, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72911', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression] Don't let the user insert the same category multiple times\", 'description': {'raw': 'screenshot showing multiple Categories with same title\\n\\nEnvironment- production, test2\\n\\n1>Select Categories. Add a category for ex- “Japan”.\\n2>The cursor moves to the next input field. Type in “Japan” again. Click somewhere else in the modal, to move the focus. \\n3>Click back in the input field. While the cursor is in the field,hit enter key.\\n4>The category with the same name Japan gets added.See screenshot.\\n\\nIn beta, at step#2, after typing in the title, just click twice in the input field(to close the drop-down) and hit enter key. The category with the same title gets added.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15381}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415150926, 'spacePHID': None, 'dateCreated': 1415029080, 'dateModified': 1417571385, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72906', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs UI: Unreadable input box text with dark colour schemes', 'description': {'raw': 'There is text in these forms that can only be seen when selecting.\\n\\nThe same issue as described in bug 72188 applies in VisualEditor; namely that dark system settings lead to unreadable text in certain forms. This is almost certainly because the background colour has been defined and the text colour has been left to the system, leading, in this case, to white text on a white background.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15230}'}, 'authorPHID': 'PHID-USER-uku6gl4xeqbtbrcbr5ig', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415612066, 'spacePHID': None, 'dateCreated': 1414819200, 'dateModified': 1427403674, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72848', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  I can't select multiple refs when going backwards from the keyboard in Firefox\", 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Open a page in Firefox (v. 32.0.3 on Mac 10.8.5) that contains several refs in a row:  [1][2][3][4].\\n\\n2.  Decide that refs 1, 2, and 3 are inappropriate.  Place cursor between refs 3 and 4.\\n\\n3.  Press shift + back arrow to start selecting the refs.\\n\\n\\nResults:\\n\\nPress shift + left arrow once:  [3] is highlighted.  Press it again (i.e., to extend the selection to include [2]):  [3] is no longer highlighted.  Press it again:  [3] is highlighted again.  \\n\\nRepeat cycle of select-deselect as long as you would like.\\n\\n\\nWorkaround:\\n\\nPlace cursor before ref [1], and select the three refs by pressing shift + forward arrow.\\n\\n\\nI cannot reproduce this in Safari 6.1.2.  I haven't tested it in a LTR (left-to-right) language.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415040258, 'spacePHID': None, 'dateCreated': 1414787400, 'dateModified': 1417571384, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72835', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allowing creation of empty caption moves the column editing icon at the top of the empty space which looks odd', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Insert a table\\n2.Insert an empty caption to the table\\n3.Save the page\\n4.Now select any cell in the table\\n\\nObserve that,the column editing icon at the top of the empty space which looks odd \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15173}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416090787, 'spacePHID': None, 'dateCreated': 1414784820, 'dateModified': 1417571383, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72829', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] The options under Page Settings and Advances Settings of Page Options dialog are appearing very cramped', 'description': {'raw': 'Screenshot in Betalabs\\n\\nCompare the screenshots taken from Betalabs and test2 for the Page Settings tab and see how they are all cramped in Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F15065}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415047641, 'spacePHID': None, 'dateCreated': 1414705140, 'dateModified': 1417571389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72792', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6] The dropdown box for search results in Insert Template dialog sticks to the dialog if you click on \"Show Options\" button without closing the dropdown', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Template\\n3.Type a template name in the textbox\\n4.Now click on the \"Show Options\" button without selecting anything from the dropdown and closing it\\n\\nObserved Result:\\nThe drop down for search results stays in the dialog in the middle of the left panel and add template panel\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15056}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414796282, 'spacePHID': None, 'dateCreated': 1414704060, 'dateModified': 1417571387, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72789', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] The group names inside \"Use this group\" field are appearing in a short form like \"g...\" for both \"References list\" and \"Basic Reference\" dialog when you open these dialogs first time in a session', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Basic References or References list dialog\\n3.Place cursor inside the \"Use this group\" combo box\\n\\n\\nObserved Result:\\nThe group names for reference list are appearing in a short form\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15039}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415052664, 'spacePHID': None, 'dateCreated': 1414701480, 'dateModified': 1417571389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72783', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Ctrl+A no longer working since staging of slugs because a selection starting from a CE=false node in Chrome', 'description': {'raw': 'Please.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1433773199, 'spacePHID': None, 'dateCreated': 1414624320, 'dateModified': 1434583946, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72725', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Convert some MW core special pages to OOUI', 'description': {'raw': 'Convert several MW core special pages to OOUI as a demonstration that it\\'s possible now.\\n\\nPart of \"front-end standardisation\" Q2 priority project.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1437833990, 'spacePHID': None, 'dateCreated': 1414621860, 'dateModified': 1463778662, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72715', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When applying the <pre> formatting to multiple paragraphs, make them instead a single <pre> with newlines between the paragraphs', 'description': {'raw': 'I was wondering if we could have a feature whereby multiline selected text could be enveloped in one <pre> or <code> when the corresponding heading level or text formatting option is clicked from the toolbar.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-srhlj2447vmpmrfhqnfa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414619520, 'dateModified': 1643977415, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72706', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6] deleting text formatted as computer code produces: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.) in Safari', 'description': {'raw': 'Found in Safari test2.\\n\\n1. In VE type some text(spanned several lines), highlight it and apply computer code formatting option. \\n\\n2. Delete one line of code - Console shows: Failed to load resource: The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -10.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414614240, 'dateModified': 1462716697, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72698', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit notices popup shows out of screen in RTL', 'description': {'raw': \"a screenshot with the problem\\n\\nTo reproduce, edit an old version of a Hebrew Wikipedia article, e.g.:\\nhttps://he.wikipedia.org/w/index.php?title=ASCII&oldid=15904477&veaction=edit\\n\\nThe popup with the edit notice about editing an old version appears immediately. It's misaligned and shown mostly out of screen.\\n\\nSee the screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14738}\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414623664, 'spacePHID': None, 'dateCreated': 1414586280, 'dateModified': 1417571391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72673', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Content menu is embedding off-screen for left-floated node in RTL environment', 'description': {'raw': 'To reproduce:\\n\\n1. Edit the Hebrew Wikipedia article about Haifa:\\nhttps://he.wikipedia.org/wiki/%D7%97%D7%99%D7%A4%D7%94?veaction=edit\\n\\n2. Click the infobox on top left.\\n\\nObserved: The pop-up puzzle bubble for editing the template appears to the left of the infobox, goes off-screen and creates a horizontal scroll-bar.\\n\\nExpected: The pop-up puzzle bubble must appear in a visible convenient place.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1419722431, 'spacePHID': None, 'dateCreated': 1414580160, 'dateModified': 1438735443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72668', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Clicking on an image with wikilink opens up link inspector', 'description': {'raw': 'screenshot\\n\\nEnvironment- test2\\n\\n1> In a blank page insert an image with a wikilink as caption.\\n2> Now click on the image in the main editor. Notice in the context menu,  along with the name of the image now the link also appears.\\n3> click on the context menu and it opens the link inspector for you populated with the target.\\n\\nSee screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15374}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414558140, 'dateModified': 1462716697, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72660', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Be able to serialise the linear model', 'description': {'raw': 'For things like auto-save (T57370) and collaboration.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1472062233, 'spacePHID': None, 'dateCreated': 1414551060, 'dateModified': 1472062283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72658', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Some dialogs are showing with transparent backgrounds in IE11', 'description': {'raw': \"IE11 transparency flaws\\n\\nSteps to reproduce: \\n\\n\\n1. Open any page in VE on IE11(test2). \\n\\n2. Click on 'Page option' icon and select 'Options'\\n\\n3. Options-Advanced settings have three small info icons - click on each of them - the box becomes transparent(look at the attched screenshot). There is also a screenshot of how it behaves in Chrome, for comparison. \\n\\nAnother way to reproduce the bug - when in Step 3 you click on the first info icon, open another browser tab, go and return back - the box for Options will become transparent.  \\n\\nNote: does not happen with Insert-Template(a template should have one info icon).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15339}\"}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1460644121, 'spacePHID': None, 'dateCreated': 1414526520, 'dateModified': 1462842894, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72643', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"OOjs UI: [Regression] Menu width isn't working in IE11 any more – see VisualEditor's 'Page options' drop down menu\", 'description': {'raw': 'Page options drop down horizontal scroll bar\\n\\nSteps to reproduce: \\n\\n1. In IE 11 in full screen- open any page for edit in VE.\\n2. Click on Page option icon - the drop down menu options will be displayed partially and a horizontal window scroll bar will be displayed.\\n\\n{F15330}\\n\\n--------------------------\\n**See Also**:\\n{T74592}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418763261, 'spacePHID': None, 'dateCreated': 1414523340, 'dateModified': 1427403676, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72640', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Text in Japanese disappears', 'description': {'raw': 'First reported by miya at ja.wp:\\nwrite something in Japanese; press Enter; the whole line disappears. This also happens when adding a picture - in the Caption field.\\nThis does not seem to be browser or OS-specific.\\nmiya says that adding a \"single-byte character\" or a number at the beginning of the line, the line doesn\\'t disappear - I don\\'t seem able to confirm this (my tests are in Safari/X Yosemite).\\nI\\'m able to reproduce the general issue at mediawiki.org (using the laptop input system for Katakana; hope I\\'m doing this right).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72508'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1435941635, 'spacePHID': None, 'dateCreated': 1414497360, 'dateModified': 1437511423, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72619', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: When the context menu appears in mobile, the button alignment for \"Next\" and \"Page Settings\" option at the top right gets a bit lower', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Mobile VE\\n2.Select a link or a citation so that the context menu for it appears on the top\\n\\nObserved Result:\\nWhen the context menu appears observe the positions of the buttons at the left-\"Save\" and \"Settings\" icon also gets changed to a much lower position , they should be fixed while the context menu opens at the bottom of the menu bar\\n\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15145}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1438633929, 'spacePHID': None, 'dateCreated': 1414436160, 'dateModified': 1439508204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72570', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Math rendering 2.0 does not work in edit mode', 'description': {'raw': 'I just tested the feature\\nhttps://lists.wikimedia.org/pipermail/wikitech-ambassadors/2014-October/000991.html\\nwith VisualEditor and it seems to be using a low resolution image instead of MathMl (while editing). When I save the page,\\nhttps://pt.wikipedia.org/w/index.php?diff=40380507\\nthe formula disappears and it only reappear after I reload the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415885794, 'spacePHID': None, 'dateCreated': 1414357320, 'dateModified': 1417571383, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72539', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: a line started with Japanese input disappear when I switch to and start non-Japanese (latin) input', 'description': {'raw': 'Environment:\\nUbuntu 14.04.1 LTS\\nIBus 1.5.5\\nmozc 1.13.1651.102-2\\n\\nTest sequence:\\n0. Open a blank page with VisualEditor.\\n1. Switch to Japanese input.\\n2. Enter \"nihongo\".\\n3. Convert it (usually by pushing down the space key). You\\'ll see it converted \"日本語\" here.\\n4. Disable Japanese input.\\n5. Enter \"a\". You\\'ll see here \"日本語\" removed and only \"a\" remaining.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72619'}, 'authorPHID': 'PHID-USER-meyjnh7zdarfb7u7upzo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1435941596, 'spacePHID': None, 'dateCreated': 1414234140, 'dateModified': 1437511435, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72508', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking on somewhere else in the document after opening a link inspector inside a slug throws error \"TypeError: Cannot read property \\'previousSibling\\' of undefined\"', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a bullet list\\n3.Add some indentation \\n4.Now click on any slug that got created due to indentation\\n5.Open a link inspector on that position\\n6.While the link inspector is open, click somewhere else in the document to close the inspector\\n\\nObserved Result:\\nThe link inspector stays opened in that position and there is an error in the console:\\nTypeError: Cannot read property 'previousSibling' of undefined\\n\\nSee the screenshot attached\\n\\nEnvironment:Betalabs,test2 and en.wiki\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72558\\n\\n**Attached**: {F14916}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1424740541, 'spacePHID': None, 'dateCreated': 1414183680, 'dateModified': 1427672965, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72494', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf6] \"TypeError: Cannot read property \\'isDefault\\' of undefined\" appears when Media Settings dialog appears while adding a new image', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Media\\n3.Search for any image and select one \\n\\nObserved Result:\\nAs soon as you select any image and the Media Settings dialog appears,the following error appears in the console\\n\\nUncaught TypeError: Cannot read property 'isDefault' of undefined\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14910}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414427874, 'spacePHID': None, 'dateCreated': 1414181520, 'dateModified': 1417571390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72492', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"MediaWiki API Cache-Control headers are different than MediaWiki's which causes problems for VE users on some browsers\", 'description': {'raw': 'There are different controls for the Cache-Control headers for the API and MediaWiki\\'s OutputPage.  This may have seemed innocuous in the past, but it is causing problems now that VisualEditor is moving page editing to the API.\\n\\nOn my local wiki pages are served with:\\n\\n  Cache-Control: private, must-revalidate, max-age=0\\n\\nand, when mCacheMode is set to \\'private\\', the default, API responses are sent with:\\n\\n  Cache-Control: private\\n\\n[[ http://www.ietf.org/rfc/rfc2616.txt | RFC 2616 ]] says:\\n\\n  private\\n      Indicates that all or part of the response message is intended for\\n      a single user ... A private (non-shared) cache MAY cache the response.\\n\\nand:\\n\\n   A cache MAY be configured to return stale responses without\\n   validation, but only if this does not conflict with any \"MUST\"-level\\n   requirements concerning cache validation (e.g., a \"must-revalidate\"\\n   cache-control directive).\\n\\nand:\\n\\n   If a cache receives a 5xx response while attempting to revalidate an\\n   entry, it MAY either forward this response to the requesting client,\\n   or act as if the server failed to respond. In the latter case, it MAY\\n   return a previously received response unless the cached entry\\n   includes the \"must-revalidate\" cache-control directive (see section\\n   14.9).\\n\\n**old description:**\\nIE 11 seems to cache faulty parsoid responses.\\n\\nI had a misconfigured server and, even after I fixed the problem and other browsers were able to continue after clicking \"edit\", IE didn\\'t even attempt to make a request but just kept showing the alert box with the error message.\\n'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'dateClosed': 1426119916, 'spacePHID': None, 'dateCreated': 1414164780, 'dateModified': 1437609069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72480', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MWTitleInputWidget should return titles', 'description': {'raw': \"MWTitleInputWidget should have a .getTitle() getter (which can return null, if the value isn't a valid title). Using this getter should be preferred over .getValue(). Callers of MWTitleInputWidget.getValue() should be converted to .getTitle(), and they should check for null-ness, because we probably have more bugs like bug 71998 hiding in various places.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414607146, 'spacePHID': None, 'dateCreated': 1414114860, 'dateModified': 1417571394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72468', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reorganize and restrategize how Scalable information works with all existing images', 'description': {'raw': 'Make the API call for scalable information unified on load, and make sure the call only comes out once per image (at least) and is persistent between the image and the image model in the edit dialog.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414088400, 'dateModified': 1643977416, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72439', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Applying a rich annotation to an image causes inspector to open then close quickly in Chrome; die in Firefox', 'description': {'raw': 'inspector opens up on the left side in FF 33.0\\n\\nEnvironment- beta\\n\\n1> In VE, insert a media(with any settings but no content in \"Caption\") to blank page.\\n\\n2> Highlight the image and select link or language from the toolbar.The inspector opens and closes quickly.\\n\\nThis happens in chrome 38 only.\\n\\nIn FF 33.0, when you do the above steps, the inspectors do not open on top of the image.But always on the left side in the CE .See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14768}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414082160, 'dateModified': 1416854457, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72431', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Navbox rendering incorrect, all items in the same line', 'description': {'raw': 'Parsoid output has broken output because Mediawiki:common.css is not included.\\n\\nFor example:\\nhttp://parsoid-lb.eqiad.wikimedia.org/frwiki/Guerre_froide?oldid=108085194\\n\\nHere the original version:\\nhttps://fr.wikipedia.org/w/index.php?title=Guerre_froide&oldid=108085194\\n\\nAnd with the visual editor:\\nhttps://fr.wikipedia.org/w/index.php?title=Guerre_froide&oldid=108085194&veaction=edit\\n\\nLike you can see the infobox width is huge probably because there is no rule for the \"infobox_v2\" CSS class.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nwa6c3hm5nmv7ixrih4p', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1592506990, 'spacePHID': None, 'dateCreated': 1414054260, 'dateModified': 1592506990, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72416', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The Citation icon does not get highlighted upon clicking or tapping on it in Mobile VE using desktop Safari and iOS safari', 'description': {'raw': 'Screenshot\\n\\nSteps to reporduce\\n\\n\\nWhen you tap on Bold, Italic or Link buttons from the toolbar, the icons for these become highlighted in the toolbar.but when you tap on citation icon , there is no highlight on it, which looks a bit inconsistent\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14712}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1438966850, 'spacePHID': None, 'dateCreated': 1414024140, 'dateModified': 1438966850, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72410', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Cannot overwrite a text entered in CE in mobile VE using desktop Firefox', 'description': {'raw': \"Steps to reproduce:\\n\\n1.Open any page with mobile VE\\n2.Type a text\\n3.Select the text and type something else to overwrite it'\\n\\nObserved Result:\\nNothing gets entered into the CE and does not replace the old text\\n\\n\\nEnvironment: Production, test2 and Betalabs\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-cbjanejnwkkrbnj77d2d', 'dateClosed': 1568158597, 'spacePHID': None, 'dateCreated': 1414023600, 'dateModified': 1568158598, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72409', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Double clicking on citation note in Mobile using desktop Safari opens up the Basic reference dialog which was explicitly disabled for Mobile', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Mobile VE which has citation note in it using desktop Safari\\n\\n2.Now double click on citation \\n\\nObserved Result:\\nIt opens the Basic Reference dialog , which we explicitly disabled because there were lot of things we didn't implement inside that dialog\\n\\nSee the screenshot attached\\n\\nEnvironment: Betalabs, test2 and production\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15388}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429738870, 'spacePHID': None, 'dateCreated': 1414022220, 'dateModified': 1429738870, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72407', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The context menu for Citations are not appearing after tapping on it when the keyboard is closed', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Load a page with Citations with Mobile VE in iOS safari or desktop Safari\\n2.Keep the keyboard closed in iOS Safari so that the cursor is not active in CE, for desktop just click somewhere out of CE to keep the cursor inactive on CE\\n3.Now click or tap on Citation note\\n\\nObserved Result:\\nThe context menu for it does not appear and a light shade of highlight appears on top of it when I click but it also goes away\\n\\n\\n  \\nSee the screenshot attached\\n\\nEnvironment:test2, Betalabs and production\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15386}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434488130, 'spacePHID': None, 'dateCreated': 1414020240, 'dateModified': 1434492392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72406', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The label for \"Re-use\" tool is not greyed out when the tool is disabled (icon is greyed out)', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE which does not have any reference in it to re-use.\\n\\n\\nObserved Result:\\n\\nThe \"Re-use\" label for the button is not greyed out even if the button icon is \\n\\nSee the screenshot attached\\nEnvironment:Production,test2 and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15377}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415055081, 'spacePHID': None, 'dateCreated': 1414019340, 'dateModified': 1417571388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72405', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Move default value and autoValue code from MWParameterPage (UI) to MWParameterModel (DM)', 'description': {'raw': 'Half of dm.MWParameterModel is dedicated to looking things up in the parent template\\'s spec. Despite that, ui.MWParameterPage manually looks up the default value and autoValue because there are no getters in dm.MWParameterModel for those things, for no good reason whatsoever. Those getters should be added.\\n\\nWhat\\'s even worse is the \"if there is no real value, set the value to the autoValue\" logic (added in https://gerrit.wikimedia.org/r/168204 ). Currently this logic (which is fundamentally DM logic) is in ui.ParameterPage as well. Instead, MWParameterPage.getValue() should be smart enough to return either the real value or the autoValue if there is no real value.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414433853, 'spacePHID': None, 'dateCreated': 1414019220, 'dateModified': 1417571394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72404', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting in text containing a tab character causes VE to scroll to the top', 'description': {'raw': 'Intention:\\nPaste bibliographic information from Google books\\n\\nSteps to Reproduce:\\n1. Almost any book will do for this, but to pick an example http://books.google.co.uk/books?id=VYvS7MyaEE8C\\n2. Scroll down to the \"Bibliographic information\" section at the end\\n3. Select everything between the name of the publisher and the first ISBN number.  Ignoring whitespace, you should have something like \"Academic Press, 2012 ISBN 0123914213\" on the clipboard. It is important that the selection spans at least two lines and includes at least one tab character.  Other than that it is not vital what infomation from the bib is selected, but this is what I would normally select and gives me problems.\\n4. Choose a Wikipedia page with a substantial amount of text, or create one in sandbox\\n5. Launch VE and scroll down far enough so the top of the article is no longer visible.\\n6. Start a new line and type some text such as \"Author name, Book Title, \" (this step is essential)\\n7. Paste the clipboard contents immediately at the end of this line (this currently has to be done with right-click paste rather than CTrl-V due to another bug, but this was still happening before Ctrl-V got broke)\\n\\n\\nActual Results:  \\nThe part of the article you are working on (this will usually be the references or bibliography section right at the end of the article) disappears from sight as VE scrolls right to the top of the article.\\n\\nExpected Results:  \\nThe focus should stay at the pasting insertion point.\\n\\nScrolling to the top also occurs when a tab is typed from the keyboard, which I assume is related.  Possibly this is meant to be a feature, but it is not a very helpful one - I find myself typing tabs while in tables expecting to tab to the next cell as is common on internet forms.  I know VE doesn\\'t do this, but the expected behaviour is so ingrained I keep getting caught out.  In any case, a tab pasted in with text doing this is definitely a bug.\\n\\nReproducible: Didn\\'t try\\n\\nThe bug is quite intrusive to me, I am frequently pasting in source bibliographic information, almost every session.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**: {T73728}'}, 'authorPHID': 'PHID-USER-imut7wxehhy35ukuzaks', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1433463455, 'spacePHID': None, 'dateCreated': 1414014540, 'dateModified': 1438763443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72390', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting invalidly parented <figcaption> throws \"Uncaught TypeError: Cannot read property \\'type\\' of undefined\" in ve.dm.LinearData.static.getType', 'description': {'raw': \"1. Copy to the clipboard the below invalid rich content from NYTimes.com:\\n   <div><div …><a …><img …></a></div><figcaption …>Foo</figcaption></div>\\n\\n2. Go to any page in VE\\n\\n3. Paste; observe crash of paste engine.\\n\\nPaste rules are probably not checking parentage (HTML spec says no <figcaption>s except as children of <figures>s) and it's breaking things. Instead, we should… eh. Downcast to <div>?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1535731341, 'spacePHID': None, 'dateCreated': 1414011120, 'dateModified': 1535731342, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72385', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Use the local namespace for files, instead of the English default', 'description': {'raw': 'If you add a file in VisualEditor, then it sometimes adds the file using the English namespace or other English terms.  Examples:\\n\\nhttps://ca.wikipedia.org/w/index.php?diff=14187112&oldid=14185423 – \"File\" is not a Catalan word\\n\\nhttps://es.wikipedia.org/w/index.php?diff=77684034&oldid=73098946 – \"File\" is not a Spanish word\\n\\nhttps://de.wikipedia.org/w/index.php?diff=135103424&oldid=135103377 – German uses \"mini\" instead of \"thumb\"\\n\\nhttps://ro.wikipedia.org/w/index.php?diff=8882945&oldid=7944846 – \"File\" is not a Romanian word\\n\\nhttps://ru.wikipedia.org/w/index.php?diff=66358996&oldid=55356951 – or Russian\\n\\nhttps://sv.wikipedia.org/w/index.php?diff=28184524&oldid=20202611 – or Swedish\\n\\nhttps://pl.wikipedia.org/w/index.php?title=Pawe%C5%82_z_Eginy&diff=40760929&oldid=38644980 – or Polish \\n\\nhttps://it.wikipedia.org/w/index.php?title=Paolo_di_Egina&diff=68773170&oldid=63002904 – or Italian\\n\\n\\nIn other cases, it did use the local name, including French, Hungarian, and Estonian.  I\\'m not sure what the common thread is.  It\\'s possible that some of these communities deliberately choose to use the English namespace, but at least a few change such edits.  If we can use the local name more often, then we should be able to reduce the burden on local communities.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414004040, 'dateModified': 1583628882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72370', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Give a hint there is a save button in action=edit', 'description': {'raw': 'While observing three librarians editing each their own page, I noticed that they had uncertainties when asked to save their edit. I had to explain them they have to scroll the page, and exactly where to scroll: not the text area, the whole page.\\n\\nIndeed, the save button is easily outside the screen, even without overly long copyrightwarning areas. We should always give a hint to users so that they know where to proceed.\\n\\nSomething as simple as a biggish button on top of the text area, linking the [[#wpSave]] anchor, might even suffice. Worth some prototyping and usability testing IMHO.\\n\\nI filed a twin report for VisualEditor without realising:  T90864\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1413971040, 'dateModified': 1643977416, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72350', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf5] Scroll bar is appearing while opening a link inspector', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open Link inspector in an empty line \\n\\n\\nObserved Result:\\nA scroll bar is appearing inside the link inspector\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15203}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414022090, 'spacePHID': None, 'dateCreated': 1413931380, 'dateModified': 1457388467, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72338', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid 0.1.15 generates 500 errors when editing pages', 'description': {'raw': 'This site, https://wiki.transitionnetwork.org/ is running on amd64 Debian Wheezy with Parsoid installed using apt as per the instructions at https://www.mediawiki.org/wiki/Parsoid/Setup#Ubuntu_.2F_Debian_on_amd64\\n\\nToday the new GPG siging key was installed and Parsoid updated (see https://trac.transitionnetwork.org/trac/ticket/692#comment:103 ) to version 0.1.15 and this has caused all edits using the VisualEditor to generate 500 errors, this is what is logged when you try to save a page:\\n\\n  [info][localhost/Sandbox2?oldid=946] started parsing\\n  [fatal/request][localhost/Sandbox2?oldid=946] undefined is not a function\\n  TypeError: undefined is not a function\\n      at TreeBuilder.resetState (/usr/lib/parsoid/src/lib/mediawiki.HTML5TreeBuilder.node.js:61:17)\\n      at new TreeBuilder (/usr/lib/parsoid/src/lib/mediawiki.HTML5TreeBuilder.node.js:28:7)\\n      at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:231:17)\\n      at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:227:17)\\n      at ParserPipelineFactory.getPipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:363:15)\\n      at ParserPipelineFactory.parse (/usr/lib/parsoid/src/lib/mediawiki.parser.js:311:20)\\n      at /usr/lib/parsoid/node_modules/prfun/lib/index.js:436:24\\n      at new Promise (/usr/lib/parsoid/src/node_modules/es6-shim/es6-shim.js:1228:11)\\n      at /usr/lib/parsoid/node_modules/prfun/lib/index.js:419:14\\n      at /usr/lib/parsoid/src/api/routes.js:152:62\\n\\nThe error presented to editors is:\\n\\n> Error loading data from server: parsoidserver-http-bad-status: 500. Would you like to retry?\\n\\nI have reverted to the old version of parsoid to get around this issue:\\n\\n  apt-get install parsoid=0.1.12\\n\\nThere are some more details on this ticket https://trac.transitionnetwork.org/trac/ticket/799\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Linux\\n'}, 'authorPHID': 'PHID-USER-hlhhdspdobxg2jb5lyms', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1454650220, 'spacePHID': None, 'dateCreated': 1413895440, 'dateModified': 1454650220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72304', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Categories set in wikitext not showing up in category dialog on a category page', 'description': {'raw': 'Open https://it.wikipedia.org/wiki/Categoria:Personalità_del_buddhismo?veaction=edit .\\nNotice that no categories appear in the category dialog, while that page features 2 of them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61921'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413917443, 'spacePHID': None, 'dateCreated': 1413894840, 'dateModified': 1417571397, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72303', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf5] Cannot open Mobile VE in Betalabs , in the console \"TypeError: Cannot set property \\'MWMobileContext\\' of undefined\" appears', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Load a page from http://en.m.wikipedia.beta.wmflabs.org/wiki/\\n2.Open the page in Edit Source mode first\\n3.Now go to the Settings icon and try to open the page with Mobile VE\\n\\nObserved Result:\\nThe following error appears in the console and VE does not open, stays in Edit Source mode:\\n\"TypeError: Cannot set property \\'MWMobileContext\\' of undefined\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15064}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413922617, 'spacePHID': None, 'dateCreated': 1413842040, 'dateModified': 1417571392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72282', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ZH IME input sometimes inserts latin characters', 'description': {'raw': \"From a Wikia staff member working on ZH communities:\\n\\nBasically we need to type Pinyin (English words) first to select Chinese characters, but the New VisualEditors react very slowly or over fast. Before I make a Chinese word, the en words already pop up and are put in the editor.\\n\\nHere's a video of the bug happening on Mediawiki.org: http://youtu.be/G1WStvYrPPA \\n\\nReport comes from Mac/Chrome but it could be happening on more.\\n\\nI asked if this was the same issue as T63429 but he said it was not.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh\"}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-pb7r4bwzfkqxwgliqtet', 'dateClosed': 1589877303, 'spacePHID': None, 'dateCreated': 1413825840, 'dateModified': 1589878465, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72268', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf4] Annotation continuation is working but the browser styles it wrongly (i.e., not at all)', 'description': {'raw': 'Red color for link and blue background for language is not applied to the text\\n\\nEnvironment- test2\\n\\n1> Insert an internal link, the target is shown in red color. \\n2> Now while the cursor is at the last character of the link ,select the language annotation.\\n3> Click Done on the inspector and type in some text. Notice although the context menu shows both Language and link labels, but the text typed is not red in color(indicating a link) and also the background color for language annotation is not applied to it. Appears as plain paragraph text.Move the cursor back and forth on the  entire text , still no change.However, when you go to new line by pressing enter key it does appear.\\n\\nSee screenshot.\\n\\nIn beta, the background color for language gets applied immediately but the link color takes effect only after you hit enter key to go to a new line.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72108\\n\\n**Attached**: {F15009}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413940204, 'spacePHID': None, 'dateCreated': 1413819600, 'dateModified': 1417571396, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72261', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf4] \"Uncaught TypeError: Cannot read property \\'resolve\\' of null\" when applying language annotation to an image, the inspector remains open', 'description': {'raw': 'JS error in test2\\n\\nEnvironment- test2\\n\\n1> In VE,insert a media to a blank page with any settings, but without captions.\\n\\n2> highglight the image and then select the language from toolbar, the inspector opens on top of the image. JS error in console- \"Uncaught TypeError: Cannot read property \\'resolve\\' of null\". clicking on done or Remove does not close the inspector.\\n\\nIn beta , the inspector does not open when an image is highlighted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72258\\n\\n**Attached**: {F15001}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413943055, 'spacePHID': None, 'dateCreated': 1413815040, 'dateModified': 1417571392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72259', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf4] Applying link to an image gives \"Uncaught TypeError: Cannot read property \\'from\\' of null \", inspector stays open', 'description': {'raw': 'JS errors in test2\\n\\nEnvironment- test2, beta\\n\\n1>In VE, insert a media(with any settings but no content in \"Caption\") to blank page.\\n\\n2> Highlight the image and select link from the toolbar.JS Error-\\n\\nUncaught TypeError: Cannot read property \\'from\\' of null \\nUncaught TypeError: Cannot read property \\'resolve\\' of null \\nUncaught TypeError: Cannot read property \\'from\\' of null\\n\\nat this point.The inspector stays open and clicking on Remove or done does not close it.See screenshot. \\n\\nIn beta, the JS error(following the above steps) is - Uncaught TypeError: Cannot read property \\'from\\' of null.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72259\\n\\n**Attached**: {F14995}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413943064, 'spacePHID': None, 'dateCreated': 1413814140, 'dateModified': 1417571391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72258', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf3] External links in templates are rendered as red links now', 'description': {'raw': 'Since a few days all externl links, incl. coordinates in the upper right edge, are rendered as red links on dewiki. I guess this is a regression?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413816867, 'spacePHID': None, 'dateCreated': 1413800400, 'dateModified': 1417571391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72251', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: It\\'s not possible to \"Apply changes\" from the transclusion dialog after it has been emptied', 'description': {'raw': 'It\\'s not possible to \"Apply changes\" from the transclusion dialog after it has been emptied (all template and wikitext blocks in it have been removed), because the button is disabled.\\n\\nSplit off from bug 71701.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414433676, 'spacePHID': None, 'dateCreated': 1413566460, 'dateModified': 1478167491, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72191', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] \"Make full size\" is not enabling \"Apply Changes\" button when the image has been set to a custom size', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Change the image size to a custom one\\n4.Reopen the media Settings dialog\\n5.Click on \"Make full size\"\\nObserved Result:\\nIts changing the size values in the fields inside the dialog it does not enable the \"Apply Changes\" button\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14737}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413936371, 'spacePHID': None, 'dateCreated': 1413496980, 'dateModified': 1417571393, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72155', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Clicking the link tool or Ctrl+K keyboard command on an auto-numbered external link triggers the wrong (annotation) link inspector', 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Open a page that already contains an external link without a label: [http://example.com].\\n\\n2.  Try to change that link to [http://example.com anything].  No fair removing the whole link and re-adding it.\\n\\n\\nResults:\\n\\nYeah, I couldn't figure out how to do that either.\\n\\n\\n(According to the bug titles, bug 51309, bug 53505, and maybe some others address this, but the descriptions don't seem to match the titles very closely.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413946923, 'spacePHID': None, 'dateCreated': 1413492960, 'dateModified': 1417571396, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72150', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector inside dialog is clipped against dialog boundary, which makes it too small', 'description': {'raw': \"buggy link dialog\\n\\nLinks don't correctly autocomplete when adding them from the references dialog and not the main editor (see screenshot; Chrome, en.wp today).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F15331}\"}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1413424800, 'dateModified': 1706727607, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72121', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[upstream] Zuul prepareRef does not handle failure to connect to Gearman', 'description': {'raw': \"Screenshot of Zuul status\\n\\nA few hours ago the Zuul queue started to get stuck. A stack of three changes in mediawiki-extensions-DonationInterface was reviewed with CodeReview+3. The top one (commit C, depending on B, depending on A) had a merge conflict in it.\\n\\nC https://gerrit.wikimedia.org/r/#/c/166678/3\\nB https://gerrit.wikimedia.org/r/#/c/166803/1\\nA https://gerrit.wikimedia.org/r/#/c/166889/2\\n\\nSomehow this caused Zuul's gate-and-submit pipeline to get stuck indefinitely. Even changes from mwext-VisualEditor, mediawiki-core, mwext-MobileFrontend were all waiting.\\n\\nDebug information from Zuul's log\\n\\n-------\\n\\n```\\n$ cat /var/log/zuul/zuul.log.2014-10-15 | grep '166678,3'\\n2014-10-15 19:17:14,453 INFO zuul.Gerrit: Updating information for 166678,3\\n2014-10-15 19:17:15,169 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline check-only>\\n2014-10-15 19:17:15,169 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline check-voter>\\n2014-10-15 19:17:15,170 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline test>\\n2014-10-15 19:17:15,171 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes []\\n2014-10-15 19:17:17,470 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes []\\n2014-10-15 19:17:17,470 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0ff0590 166678,3> with dependent changes []\\n2014-10-15 19:17:17,474 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0ff0590 166678,3> with dependent changes []\\n2014-10-15 19:17:19,481 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes []\\n2014-10-15 19:17:19,481 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0ff0590 166678,3> with dependent changes []\\n2014-10-15 19:18:08,759 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f17b0ff0590 166678,3>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 2}>]\\n2014-10-15 19:18:08,842 INFO zuul.Gerrit: Updating information for 166678,3\\n2014-10-15 23:21:16,969 INFO zuul.Gerrit: Updating information for 166678,3\\n2014-10-15 23:21:17,284 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0ff0590 166678,3> to <Pipeline gate-and-submit>\\n2014-10-15 23:21:17,284 INFO zuul.DependentPipelineManager: Reporting start, action [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 0}>] change <Change 0x7f17b0ff0590 166678,3>\\n2014-10-15 23:21:17,359 INFO zuul.Gerrit: Updating information for 166678,3\\n2014-10-15 23:21:17,362 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0ff0590 166678,3> depends on changes [<Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:47:30,406 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:47:31,790 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:47:31,790 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:47:31,794 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:47:31,798 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:48:30,564 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:50:13,976 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:50:13,976 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,864 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,864 INFO zuul.Gearman: Launch job mwext-VisualEditor-qunit for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,868 INFO zuul.Gearman: Launch job mwext-VisualEditor-bundle-rubocop for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,876 INFO zuul.Gearman: Launch job mwext-VisualEditor-phpcs-HEAD for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,884 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,888 INFO zuul.Gearman: Launch job mwext-VisualEditor-npm for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,893 INFO zuul.Gearman: Launch job mwext-VisualEditor-lint for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,957 INFO zuul.Gearman: Launch job mwext-VisualEditor-doc-test for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:56,023 INFO zuul.Gearman: Launch job experiment-gating-dependencies for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n[00:45 UTC] zuul at gallium.wikimedia.org in /srv/org/wikimedia/integration ((no branch)%)\\n```\\n\\n-------\\n\\n```\\n$ cat /var/log/zuul/zuul.log.2014-10-15 | grep '166803,1'\\n2014-10-15 19:38:32,047 INFO zuul.Gerrit: Updating information for 166803,1\\n2014-10-15 19:38:32,382 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline check-only>\\n2014-10-15 19:38:32,405 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline check-voter>\\n2014-10-15 19:38:32,406 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline test>\\n2014-10-15 19:38:32,407 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes []\\n2014-10-15 19:38:34,115 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes []\\n2014-10-15 19:38:34,115 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0f64c10 166803,1> with dependent changes []\\n2014-10-15 19:38:34,119 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0f64c10 166803,1> with dependent changes []\\n2014-10-15 19:38:35,718 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes []\\n2014-10-15 19:38:35,718 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0f64c10 166803,1> with dependent changes []\\n2014-10-15 19:38:48,199 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f17b0f64c10 166803,1>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 2}>]\\n2014-10-15 19:38:48,273 INFO zuul.Gerrit: Updating information for 166803,1\\n2014-10-15 19:40:23,214 INFO zuul.Gerrit: Updating information for 166803,1\\n2014-10-15 19:40:23,668 INFO zuul.Gerrit: Updating information for 166803,1\\n2014-10-15 23:47:29,998 INFO zuul.Gerrit: Updating information for 166803,1\\n2014-10-15 23:47:30,326 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b0f64c10 166803,1> to <Pipeline gate-and-submit>\\n2014-10-15 23:47:30,327 INFO zuul.DependentPipelineManager: Reporting start, action [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 0}>] change <Change 0x7f17b0f64c10 166803,1>\\n2014-10-15 23:47:30,402 INFO zuul.Gerrit: Updating information for 166803,1\\n2014-10-15 23:47:30,406 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:47:31,790 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:47:31,790 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:47:31,794 INFO zuul.Gearman: Launch job mwext-DonationInterface-lint for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:47:31,798 INFO zuul.Gearman: Launch job mwext-DonationInterface-npm for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:48:30,564 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:50:13,976 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0f64c10 166803,1> depends on changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:50:13,976 INFO zuul.Gearman: Launch job mwext-DonationInterface-testextension for change <Change 0x7f17b0f64c10 166803,1> with dependent changes [<Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Resetting builds for change <Change 0x7f17b0c3d250 166918,2> because the item ahead, <QueueItem 0x7f180b290c10 for <Change 0x7f17b13caed0 166889,2> in gate-and-submit>, is not the nearest non-failing item, <QueueItem 0x7f17b10042d0 for <Change 0x7f17b0f64c10 166803,1> in gate-and-submit>\\n2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,864 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b0c3d250 166918,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,864 INFO zuul.Gearman: Launch job mwext-VisualEditor-qunit for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,868 INFO zuul.Gearman: Launch job mwext-VisualEditor-bundle-rubocop for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,876 INFO zuul.Gearman: Launch job mwext-VisualEditor-phpcs-HEAD for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,884 INFO zuul.Gearman: Launch job mediawiki-gate for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,888 INFO zuul.Gearman: Launch job mwext-VisualEditor-npm for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,893 INFO zuul.Gearman: Launch job mwext-VisualEditor-lint for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:55,957 INFO zuul.Gearman: Launch job mwext-VisualEditor-doc-test for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n2014-10-15 23:59:56,023 INFO zuul.Gearman: Launch job experiment-gating-dependencies for change <Change 0x7f17b0c3d250 166918,2> with dependent changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>]\\n```\\n\\n-------\\n\\n```\\n$ cat /var/log/zuul/zuul.log.2014-10-15 | grep '166889,2'\\n2014-10-15 22:33:35,953 INFO zuul.Gerrit: Updating information for 166889,2\\n2014-10-15 22:33:36,261 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline check-only>\\n2014-10-15 22:33:36,261 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline check-voter>\\n2014-10-15 22:33:36,262 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline test>\\n2014-10-15 22:33:36,263 INFO zuul.IndependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes []\\n2014-10-15 22:33:39,803 INFO zuul.IndependentPipelineManager: Unable to merge change <Change 0x7f17b13caed0 166889,2>\\n2014-10-15 22:33:39,803 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f17b13caed0 166889,2>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': -1}>]\\n2014-10-15 22:33:39,876 INFO zuul.Gerrit: Updating information for 166889,2\\n2014-10-15 23:48:30,171 INFO zuul.Gerrit: Updating information for 166889,2\\n2014-10-15 23:48:30,484 INFO zuul.Scheduler: Adding mediawiki/extensions/DonationInterface, <Change 0x7f17b13caed0 166889,2> to <Pipeline gate-and-submit>\\n2014-10-15 23:48:30,484 INFO zuul.DependentPipelineManager: Reporting start, action [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x1b6c310>, {'verified': 0}>] change <Change 0x7f17b13caed0 166889,2>\\n2014-10-15 23:48:30,559 INFO zuul.Gerrit: Updating information for 166889,2\\n2014-10-15 23:48:30,564 INFO zuul.DependentPipelineManager: Change <Change 0x7f17b13caed0 166889,2> depends on changes [<Change 0x7f17b0f64c10 166803,1>, <Change 0x7f17b0ff0590 166678,3>, <Change 0x7f17b0c2e750 166607,6>]\\n2014-10-15 23:48:31,761 INFO zuul.DependentPipelineManager: Unable to merge change <Change 0x7f17b13caed0 166889,2>\\n2014-10-15 23:59:51,805 INFO zuul.DependentPipelineManager: Resetting builds for change <Change 0x7f17b0c3d250 166918,2> because the item ahead, <QueueItem 0x7f180b290c10 for <Change 0x7f17b13caed0 166889,2> in gate-and-submit>, is not the nearest non-failing item, <QueueItem 0x7f17b10042d0 for <Change 0x7f17b0f64c10 166803,1> in gate-and-submit>\\n```\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**See Also**:\\nhttps://launchpad.net/bugs/1358517\\n\\n**Attached**: {F15298}\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1461058704, 'spacePHID': None, 'dateCreated': 1413420420, 'dateModified': 1461058704, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72113', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor Mobile: The down-arrow is not appearing in against the cite menu's icon in Mobile VE\", 'description': {'raw': 'Screenshot\\n\\nSee the screenshot attached to see the position of the arrow\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15292}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413830564, 'spacePHID': None, 'dateCreated': 1413419460, 'dateModified': 1417571397, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72111', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf3] Cannot open the dropdown box  for \"Use this group\" field inside References List dialog box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a group reference\\n3.Now go to Insert>References list\\n4.Click on the arrow to bring up the drop down box for the \"Use this group\" field\\n\\n\\nObserve Result:\\nThe drop down box with options of group names are not opening unless you type something in the textfield\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15267}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413413017, 'spacePHID': None, 'dateCreated': 1413412800, 'dateModified': 1417571395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72100', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf3] The dropdown box for \"Use this group\" field inside Reference dialog is not closing upon de-focusing', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the basic reference dialog\\n3.Place the cursor inside the field \"Use the group\"\\n4.Type something or keep it empty while the drop down is open.\\n5.Place cursor somehwhere else in the dialog to close it\\n\\nObserved Result:\\nThe drop down box does not get closed\\n\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15265}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413413104, 'spacePHID': None, 'dateCreated': 1413411180, 'dateModified': 1417571394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72099', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  If I click on \"show all fields\" and add a parameter, then leave the list of all fields open so I can add another (and another and another)', 'description': {'raw': \"This is from Salix alba, and I don't believe that I can improve upon his description:\\n\\n\\nI wanted to add {{tl|Infobox musical artist}} to an article and it proved to be much more painful than it needs to be. \\n\\nIf you want add one of the minor fields like {{param|genre}} you have to\\n#Click on '''Add more information'''\\n#Click on '''Show 17 more fields'''\\n#scroll down to find the field you want and click on it\\n#The window will then scroll to the top of the form so you have to\\n#scroll down again to find the field you want and fill in the value\\n#repeat the whole process again.\\n\\nThis could be made easier. Why do I need to click twice to show all fields? Why do I need to go back to square one after adding a field? Why does it not auto scroll to the correct place (actually why not simply show the field under it description in the list of fields).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=69734\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1413395280, 'dateModified': 1643977416, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72083', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression ?wmf3] Non-normalised category names cause \"Uncaught TypeError: Cannot read property \\'hidden\\' of undefined\" to be thrown', 'description': {'raw': '--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416971541, 'spacePHID': None, 'dateCreated': 1413386880, 'dateModified': 1438735454, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72080', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: When auto-filling citations using citoid, don't add any empty parameters\", 'description': {'raw': 'See the empty author parameters in this:  https://en.wikipedia.org/w/index.php?diff=629488479&oldid=629487984\\n\\nEmpty, non-required parameters would ideally not be added by Citoid.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-evd3wnvnlb66lrwulch4', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414247566, 'spacePHID': None, 'dateCreated': 1413235020, 'dateModified': 1417571393, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72007', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: “Uncaught Error: Unable to parse title” when entering \"Talk:\" as a template', 'description': {'raw': 'screenshot\\n\\nEnvironment- test2, beta, production.\\n\\n1> Select template. In the Add a Template dialog when the cursor is in the input box, hit spacebar.\\n2> The Add a Template button becomes active.click on it. \\nJS console error-“Uncaught Error: Unable to parse title”.\\n\\nScreenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14999}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415064169, 'spacePHID': None, 'dateCreated': 1413214140, 'dateModified': 1417571384, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71998', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Categories\" dialog behaves differently for existing values and entered values', 'description': {'raw': 'Screenshot of initial render with 1 category present\\n\\nWhen opening the dialog and one category is already on the page, that category is rendered on its own line and the input field has its own line too (full width).\\n\\nWhen removing that category and re-adding it, the input field shrinks and the category bubble is in front of it on the same line.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14793}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1420773172, 'spacePHID': None, 'dateCreated': 1412973900, 'dateModified': 1438735455, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71921', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'First line in edit window is sometimes hidden in Safari', 'description': {'raw': 'Intermittent bugs are the worst.\\nThis is happening to me randomly in Safari 7.1: when I try to create a new page, what I type won\\'t show up sometimes. It seems like the first line (or two) of the edit window is \"hidden\" under the edit toolbar. It just happened to me several times in a row on a page similar to https://meta.wikimedia.org/w/index.php?title=Talk:Tech/News/2014/39&action=edit&redlink=1 .\\nIt also happens on existing pages: I remember I had difficulties placing templates at the top of a page on Meta, so I just tried to edit https://meta.wikimedia.org/w/index.php?title=Talk:Community_Engagement_(Product)/Media_Viewer_consultation/Other&action=edit , and the first two lines are \"missing\". Nothing happens if I try to scroll up and down, with mouse or keyboard (except I can\\'t see the cursor blinking if it is on one of those lines).\\n\\n--------------------------\\n**Version**: 1.25-git\\n**Severity**: normal\\n**OS**: Mac OS X 10.9'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'dateClosed': 1458573763, 'spacePHID': None, 'dateCreated': 1412932980, 'dateModified': 1458573763, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71909', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf3] In Firefox, Cursor is appearing in Read mode at the end of the document after saving a page and after discarding the current edit in Firefox', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE with Firefox\\n2.Edit the page\\n3.Save the page or just navigate to Readmode after discarding the edit\\n\\n\\nObserved Result:\\nCursor appears in the last line of the page in readmode.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=71829\\n\\n**Attached**: {F15300}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415152313, 'spacePHID': None, 'dateCreated': 1412806320, 'dateModified': 1417571388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71852', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor Mobile: Can't select an image node if the cursor is active?\", 'description': {'raw': \"If you open the editor and click on an image it works fine (albeit alienated), but once you've dropped the cursor anywhere in the document, even in a slug, it doesn't seem possible to select the node any more?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434488283, 'spacePHID': None, 'dateCreated': 1412803320, 'dateModified': 1434492395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71841', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying text causes browser to scroll to the top of the page and move the cursor to the top in Safari', 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Open a long page in Safari 6.2 (maybe others?)\\n\\n2.  Scroll down a ways and select some text.\\n\\n3.  Copy (Command-C) that text.\\n\\n\\nResults:\\n\\nAfter a brief delay (one second?), the page scrolls all the way to the top.  The cursor is located at the very beginning of the page.  (The text is correctly copied.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**: {T74390}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1718626314, 'spacePHID': None, 'dateCreated': 1412650920, 'dateModified': 1718626314, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71728', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot enable or disable formatting of lines starting with semicolon markup', 'description': {'raw': 'If there is a line on a page that includes the semicolon syntax, VisualEditor does not handle this well. For example:\\n\\n<example>\\n;Foo\\n\\nSome more text.\\n</example>\\n\\nIn VE, if I place the cursor either immediately before or immediately after the (bold-formatted) text \"Foo\", and then I add several new lines, I end up with multiple lines that include the semicolon formatting, such as:\\n\\n<example>\\n;Bar\\n;\\n;Foo\\n;Baz\\n\\nSome more text.\\n</example>\\n\\nThere is no way (that I can tell) to disable such formatting, and highlighting the (apparently) bold text and trying to select \"clear formatting\" has no effect.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nyv6rqxnzdy3oe323a3d', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-cbjanejnwkkrbnj77d2d', 'dateClosed': 1568158361, 'spacePHID': None, 'dateCreated': 1412634780, 'dateModified': 1568158361, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71721', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"mw:PageProp/redirect to a Category when there's no matching mw:WikiLink/Category should output [[:Category:Foo]] not [[Category:Foo]]\", 'description': {'raw': 'Pages with a <link rel=\"mw:PageProp/redirect\" href=\"./Category:Foo\"> but without a <link rel=\"mw:WikiLink/Category\" href=\"./Category:Foo\"> should be serialised to [[:Category:Foo]] per the spec, but instead are becoming [[Category:Foo]] which (a) is wrong and (b) doesn\\'t round-trip.\\n\\n----\\n\\n//Original VE complaint://\\n\\nThe VE\\'s Page Settings dialog redirect options work badly for category destinations.\\n\\nFor example, if you choose \\'Category:Article stubs\\' as your destination, it inserts this:\\n\\n#REDIRECT [[Category:Article stubs]]\\n\\nWhile this does redirect the page, it also places that page in the \"Article stubs\" category.\\n\\nIt *should* put this on the page:\\n\\n#REDIRECT [[:Category:Article stubs]]\\n\\nNote the additional \":\" - this prevents the category being interpreted wrongly.\\n\\nhttps://www.mediawiki.org/w/index.php?title=VisualEditor:Redirecttest&action=history\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': 'PHID-USER-56wtmb23orq4pu5liyj5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-56wtmb23orq4pu5liyj5', 'dateClosed': 1426846636, 'spacePHID': None, 'dateCreated': 1412614020, 'dateModified': 1428510525, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71708', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Annotation tools should be visibly disabled when selection is a formula node (which doesn't take annotations)\", 'description': {'raw': 'Screenshot\\n\\nEnvironment: test2, beta\\n\\n1> Insert a formula .\\n2>highlight the formula and change its formatting to Bold/Italic/Underline/Strikethrough. None of these styles get applied to it.\\n\\nNow select Language, it opens the language inspector. Language should be disabled for formulas.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F14907}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1412612100, 'dateModified': 1643977416, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71707', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf5] Comment inspector closes and saves empty comment when tool is used', 'description': {'raw': 'Screenshot\\n\\nEnvironment- test2, beta, production\\n\\n1> insert a comment in a blank page.\\n2> open the Edit comment box\\n3> while the cursor is still blinking in the comment box, click to add numbered / Bullet point. The comment box closes and the comment is shown as the bullet/numbered list item\\n4> Now open the edit comment box again and decrease the indentation.I get \"JS console error, Uncaught Error: Cannot set attributes on closing element\".See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14904}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416248743, 'spacePHID': None, 'dateCreated': 1412607240, 'dateModified': 1417571382, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71706', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links to Draft namespace show as red links in link inspector search', 'description': {'raw': 'Draft namespace articles incorrectly showing as red links in search\\n\\nDraft namespace articles incorrectly showing as red links in search\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14790}'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415031827, 'spacePHID': None, 'dateCreated': 1412502240, 'dateModified': 1417571390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71659', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The icons for Media and Comment are appearing a bit darker in Insert menu', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the Insert menu\\n\\nObserve that, the icon for Media and Comment are appearing a bit darker compared to other options in the menu.\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15228}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413483556, 'spacePHID': None, 'dateCreated': 1412210640, 'dateModified': 1417571395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71541', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Check locally for the user preference to prompt an edit summary, rather than waiting for the API to round-trip', 'description': {'raw': 'Right now we rely on the API moaning about this, which means you have to wait for the whole page to be serialised, returned and saved before we prompt the user to do something that takes up some cycles, and so avoids them wasting time.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412289219, 'spacePHID': None, 'dateCreated': 1412202840, 'dateModified': 1417571398, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71535', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable the MediaWiki UI / \"Form Refresh\" Beta Feature in production', 'description': {'raw': \"Now that it's been created, launching this should be scheduled…\\n\\nRelease requirements from https://www.mediawiki.org/wiki/Beta_Features/Package :\\n\\n[x]    Make an extension - [[https://www.mediawiki.org/wiki/Extension:VectorBeta |Extension:VectorBeta]]\\n[]    Get prelim design review\\n[]    Get prelim security review\\n[]    Get prelim performance review\\n[]    Make sure there is a wiki page on mw.org for it that is understandable to the general public\\n[]    Flowify the Talk page for the project\\n[]    Make sure there is someone on point for feedback - a product manager (either volunteer or WMF staff)\\n[]    Make a bugzilla component for the extension\\n[]    Enable the Final Version of the code on Beta Cluster at least a week before you want to go for production.\\n[]    Make gerrit change (do not merge) to the BF whitelist in mediawiki config\\n[]    Deploy!\\n\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'dateClosed': 1432471403, 'spacePHID': None, 'dateCreated': 1412100840, 'dateModified': 1435247964, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71477', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf1] Adding categories, removing them, then cancelling the dialog throws “Uncaught TypeError: Cannot read property 'disconnect' of undefined”\", 'description': {'raw': \"screenshot 1\\n\\nEnvironment- test2, beta\\n\\n1> In VE, go to Options  -> Categories. And add two categories.\\n2> Now delete the categories.Click on “Cancel” to close the  options dialog.\\n3> Error in console, “Uncaught TypeError: Cannot read property 'disconnect' of undefined”(see screenshot 1)\\n\\nAfter this step, reopen the Options dialog , notice the first Category is repeated( see screenshot 2).\\n\\nTrying to delete any of the categories throws errors in console “Uncaught Error: Cannot remove detached item” and “Uncaught TypeError: Cannot read property 'metaItem' of undefined”.Clicking on Cancel or Apply changes does not close the dialog.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F15029}\"}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412204214, 'spacePHID': None, 'dateCreated': 1412092140, 'dateModified': 1417571693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71471', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector UI gets broken if the link target suggestion dropdown overlaps with the border of the page', 'description': {'raw': 'video capture of the bug\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a link some where towards the end of the current viewport so that when you open the link inspector the link target suggestions overlap with the border of the page\\n3.After inserting the link, reopen the link inspector and place cursor inside to bring up the link target suggestion \\n4.When the link target suggestion dropdown appears, scroll up the page \\n\\nObserved Result: \\nThe UI for the link inspector is open. \\n\\nSee the video capture attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14747}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411778730, 'spacePHID': None, 'dateCreated': 1411769040, 'dateModified': 1417571692, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71371', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting a comment before the last word in a Language (RTL direction)Text moves the word to the start of the line.', 'description': {'raw': 'Environment-test2, beta\\n\\n1> Insert Language in RTL direction.\\n2>insert a comment in the language text, right before the last word. Notice the word moves to the start of line.See screencast.\\n3>Now place the cursor at the end of the last char in the langauge text and press backspace to delete.\\n\\nThis also happens while inserting a citation or a formula.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows XP'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1411668480, 'dateModified': 1416791948, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71320', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: *-npm jobs broken for mediawiki-core and extensions', 'description': {'raw': 'https://integration.wikimedia.org/ci/job/mediawiki-core-npm/2469/console\\n\\nhttps://integration.wikimedia.org/ci/job/VisualEditor-npm/3226/console\\n\\nEtc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: blocker'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411757722, 'spacePHID': None, 'dateCreated': 1411664160, 'dateModified': 1425133100, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71314', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: After tapping on \"Go back\"/\"Continue Anyway\" in the \"Required parameter missing\" confirmation dialog in iOS Safari, it flickers at the top of the screen', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with mobile VE in iOS Safari\\n2.Open Cite>Website\\n3.Keep one of the required parameters empty and click on Insert\\n4.When the confirmation dialog for required parameter being missing shows up, click on Go back or Continue anyway.\\n\\n\\nObserved Result:\\nObserve that, the animation of the confirmation dialog appearing and disappearing is not same as how it is in desktop safari.Also, when closing the dialog, by tapping on \"Go back\"/\"Continue Anyway\", instead of sliding up it flickers at the top of the screen.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434488277, 'spacePHID': None, 'dateCreated': 1411599540, 'dateModified': 1434492398, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71259', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting in image caption with a repeated reference causes VE to crash', 'description': {'raw': 'I found this bug while trying to swap the captions of two images, but it can be duplicated with just one image:\\n\\n1. Paste this into a page and save:\\n\\nExample text<ref name=Ref1>Ref 1</ref>\\n[[File:Example.jpg|thumb|Example text.<ref name=Ref1/>]]\\n\\n2. Launch VE\\n3. Click the image and open the Media settings dialogue\\n4. Select all the caption text (Ctrl-A) and cut it out (Ctrl-X)\\n5. Apply changes\\n6. Reopen the Media settings dialogue\\n7. Paste the caption text back in (Ctrl-V)\\n8. Apply changes\\n\\nVE will now hang on the Media settings dialogue.  The dialogue will not complete and will not cancel.  It is completely impossible to carry on editing, all the changes up to that point have to be discarded.\\n\\nI am using FF32, Windows 7, Monobooks\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-imut7wxehhy35ukuzaks', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'bug', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1411520940, 'dateModified': 1714649234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71214', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf1] Template parameter autovalues are not saved', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert the template \"Citation needed\"\\n3.Observe that in the field for \"Month and year\", the following has been used:\\n{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}\\n4.Now click on \"Apply Changes\"\\n5.Save the page\\n6.Reopen the page\\n7.Open the transclusion dialog for the \"Citation Needed\" template\\n\\nObserved Result:\\nThe current month name and current year value did not get added in the field.\\n\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14868}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414627293, 'spacePHID': None, 'dateCreated': 1411432560, 'dateModified': 1417571683, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71157', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf1] Increasing indentation to a bullet/numbered list is also adding a slug with a new bullet/numbered point each time', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert a bullet list or numbered list\\n3.Now try to add indentation to one of the item\\n\\nObserved Result:\\nApart from adding indentation, it ia also adding a new line and a new bullet point/numbered point\\n\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14804}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416243978, 'spacePHID': None, 'dateCreated': 1411416780, 'dateModified': 1417571678, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71134', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Pressing Backspace/Delete or creating a heading causes the page to abruptly scroll up on Internet Explorer 11', 'description': {'raw': '**Author:** `d_iarnov`\\n\\n**Description:**\\nwin 8.1  сенсорный .вообще нереально написать нажимая backspace  чтоб стереть  ошибочно написанное страницу подбрасывает вверх. и на этом точка. дальше работать соответственно не возможно. мало того в плиточном браузере вообще говорится что он не поддерживается. все браузеры у меня IE\\n\\n**See Also**: {T73561}\\n\\n---\\nAlternative steps to reproduce (in English, from T89196):\\n\\n1. Edit [[Nausea]] in VE: https://en.wikipedia.org/wiki/Nausea?veaction=edit\\n2. Scroll down to the \"Medications\" section\\n3. Click in the middle of a sentence and hit \"backspace\" a few times.\\n\\nEach time you do this, the page jumps, and the sentence in which the cursor is located always ends up at the very bottom of the viewport.\\n\\n4. Press \"delete\" key a few times\\n\\nSame behaviour.\\n\\n5. Now click in the middle of the very long paragraph under \"Diagnostic approach\". Hit \"backspace\" a few times.\\n\\nOnce again, the page jumps, but now it is worse, because the page lands with the cursor offscreen.'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'dateClosed': 1487404429, 'spacePHID': None, 'dateCreated': 1411392420, 'dateModified': 1549986756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71119', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Applying link to the caption of an image does not enable \"Apply Changes\" button', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image with caption\\n3.Reopen the media settings dialog \\n4.Now apply link to the existing caption\\n\\nObserved Result:\\nThe \"Apply changes\" button does not become enabled after applying link unless user make some other change for that image\\n\\nEnvironment: Betalabs, Test2 and Production\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420597574, 'spacePHID': None, 'dateCreated': 1411156560, 'dateModified': 1438735462, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71065', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'running browser tests \"unable to obtain stable firefox connection\"', 'description': {'raw': '**Author:** `physik`\\n\\n**Description:**\\nOn a fresh vagrant box with the role math enabled I get the following error message while trying to run the browser tests for math\\n\\n unable to obtain stable firefox connection in 60 seconds (127.0.0.1:7055) (Selenium::WebDriver::Error::WebDriverError)\\n  /srv/vagrant/mediawiki/extensions/Math/tests/browser/.gem/ruby/2.0.0 /gems/selenium-webdriver-2.42.0/lib/selenium/webdriver/firefox\\nsee\\n https://gist.github.com/physikerwelt/8a9ff6b292609449a2df\\n\\nI was doing nothing else beside running\\n bundle exec cucumber features/math.feature\\n\\nI checked my environment variables\\nMW_INSTALL_PATH=/vagrant/mediawiki\\nMEDIAWIKI_API_URL=http://127.0.0.1/w/api.php\\nMEDIAWIKI_USER=Selenium_user\\nMEDIAWIKI_PASSWORD=vagrant\\nINSTANCEPROJECT=math\\nCOMPOSER_CACHE_DIR=/vagrant/cache/composer\\nMEDIAWIKI_URL=http://127.0.0.1:8080/wiki/\\n\\nbut could not detect any problems there\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411069276, 'spacePHID': None, 'dateCreated': 1411049880, 'dateModified': 1496861865, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Highlight missing parameters in template dialog when complaining about them', 'description': {'raw': 'TODO someone needs to figure out what the visual treatment should look like\\n\\nThe inputs in question already match :required:empty , so we can probably do most of this with CSS.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413312131, 'spacePHID': None, 'dateCreated': 1410984600, 'dateModified': 1508526792, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70957', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Uncaught TypeError: Cannot read property \\'getSurface\\' of null\" when applying a heading format on citation', 'description': {'raw': 'screenshot\\n\\nEnvironment- Test2, beta, production\\n\\nHighlight a citation and select any text style from the drop-down. I get \"Uncaught TypeError: Cannot read property \\'getSurface\\' of null\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows XP\\n\\n**Attached**: {F14829}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1519405233, 'spacePHID': None, 'dateCreated': 1410886020, 'dateModified': 1519405233, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70888', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] The Cite and Re-use options remains enabled even if the toolbar gets disabled when user clicks outside', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a citation in the page\\n3.Now click outside the page\\n\\nObserved Result:\\nThe Cite option and the Re-use option inside it remains enabled in the toolbar\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14780}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410823299, 'spacePHID': None, 'dateCreated': 1410820020, 'dateModified': 1443277994, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70870', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] In media dialog, \"Size values are invalid\" message does not show up, when choosing a different image and then setting its size to 0 x 0 px', 'description': {'raw': 'size invalid message shown\\n\\nEnvironment- Test2, beta\\n\\n1> Go to media settings dialog for any image.\\n2>Go to Advanced Settings -> In Image size, click on custom and change its size to 0x0px.Notice message saying “Size values are invalid” shows up under the Make Full size button.\\n3> Now choose a different image and for that image repeat steps #2.Notice “Size values are invalid” does not show up.\\n\\nAlso if the image size is invalid then the insert button should get disabled, preventing the user from inserting it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows XP\\n\\n**Attached**: {F14762}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412646271, 'spacePHID': None, 'dateCreated': 1410809520, 'dateModified': 1417571695, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70861', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] \"Uncaught TypeError: undefined is not a function\", when using media search dialog', 'description': {'raw': 'Environment- Test2, beta\\n\\n1> Go to Media Search dialog, it opens with the input box populated with the user name in it.\\n2> I get JS console error Uncaught TypeError: undefined is not a function   , while the media search is still in progress .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413386695, 'spacePHID': None, 'dateCreated': 1410808800, 'dateModified': 1417571688, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70860', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'BetaFeatures: Warnings about allowed skins are not displayed', 'description': {'raw': \"The list of allowed skins of the BetaFeatures extension (in $prefs[$key]['requirements']['skins']) is not displayed in the HTML code.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-betafeatures\"}, 'authorPHID': 'PHID-USER-2nopae2cxuamwcbndaih', 'ownerPHID': 'PHID-USER-2nopae2cxuamwcbndaih', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411233187, 'spacePHID': None, 'dateCreated': 1410615900, 'dateModified': 1411237998, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70814', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying and pasting a template causes comment to be inserted in Chrome on Windows due to broken native clipboard behaviour', 'description': {'raw': '**Author:** `thalia.chan`\\n\\n**Description:**\\nCopied the heading \"Lilypond source\" and the line of text below from this page: https://commons.wikimedia.org/wiki/File:C_sharp_and_double_sharp_music.svg?veaction=edit\\n\\nPasted it into a similar page, open in a different tab, and a grey circle containing a question mark appeared at the end, which I am reliably informed is a comment. (Abandoned my edit in the end, so there\\'s nothing to clean up.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410803989, 'spacePHID': None, 'dateCreated': 1410569820, 'dateModified': 1443277996, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70799', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Errors in one module can affect other modules via $.ready', 'description': {'raw': 'This is not really a ResourceLoader bug but serious enough that some workaround is needed and that probably has to be done via RL.\\n\\nDue to jQuery bug #10251 [1] (wontfixed), errors in a jQuery domready handler prevent all subsequently added domready handlers from running. This means that errors in less reliable scripts like gadgets or user scripts can break any production code that is loaded after them and relies on $.ready (which is true for most extensions).\\n\\n\\n[1] http://bugs.jquery.com/ticket/10251\\n'}, 'authorPHID': 'PHID-USER-a6p24cvyblhfzc7we7nc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1442610911, 'spacePHID': None, 'dateCreated': 1410534420, 'dateModified': 1442610911, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70772', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] Editor is displayed with two toolbars on second initialisation', 'description': {'raw': 'double Toolbars in VE\\n\\nEnvironment- Test2, beta\\n\\n1> switch from Edit beta mode to Read mode notice the toolbar has slide down and is still visible in the Read mode.\\n\\n2> Click on Edit beta again,the Editor is displayed with two toolbars.See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70770\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70782\\n\\n**Attached**: {F15240}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411586958, 'spacePHID': None, 'dateCreated': 1410526140, 'dateModified': 1443278000, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70768', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Write unit tests for dm.Converter's use of dm.Model APIs\", 'description': {'raw': \"There are no unit tests exercising features of dm.Converter that are currently unused by our node types, like returning null/undefined from toDataElements to trigger alienation, returning one a different type from toDataElements, returning an annotation type from a node's toDataElements, etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1410487620, 'dateModified': 1643977417, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70751', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Up/down arrow in Firefox broken after using left/right', 'description': {'raw': '1. place cursor in large body of text in FF\\n2. Cursor up then down, everything is fine\\n3. Cursor right a dozen or so times, then up\\n\\nThen cursor jumps up and left to the same place it was after (2).\\n\\nInitial investigations show that disabling handling of up/down arrows makes no difference, but disabling handling of left/right does fix, so probably something to do with the surfaceObserver state?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.mozilla.org/show_bug.cgi?id=1075901'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1410456540, 'dateModified': 1416791988, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70724', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ContextItemWidget\\'s \"edit\" label should be a sibling of the description', 'description': {'raw': 'Per Ed:\\n\\n| FIXME: This should be a sibling of the description label, with enough space\\n| left to the right of the description so it shows even if the description is\\n| too wide (e.g. an external link)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1493661496, 'spacePHID': None, 'dateCreated': 1410389880, 'dateModified': 1493661496, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70691', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Dropdowns in the VE toolbar opening \"under\" the content area in the Chameleon skin', 'description': {'raw': 'There is an issue in Chrome when using the VisualEditor extension. The dropdowns in the VE toolbar seem to be opening \"under\" the content area, hiding their contents.\\n\\nThe problem is a bug in the jQuery 1.8 lib used in MW <1.24 (or a variation thereof): http://bugs.jquery.com/ticket/11635\\n\\nTodo: Backport the fix in jQuery 1.11.\\n\\n--------------------------\\n**Version**: 1.23\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-cc6dswbtmstfsb4ldmit', 'ownerPHID': 'PHID-USER-cc6dswbtmstfsb4ldmit', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-cc6dswbtmstfsb4ldmit', 'dateClosed': 1433587596, 'spacePHID': None, 'dateCreated': 1410377400, 'dateModified': 1438735684, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70678', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: LinkCache should also cache mw-redirect and mw-disambig statuses', 'description': {'raw': '… and use them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412718801, 'spacePHID': None, 'dateCreated': 1410376320, 'dateModified': 1417571695, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70674', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In template dialog, the “show one more field” control appears when there are 4 entries', 'description': {'raw': 'screenshot1\\n\\nEnvironment- test2, beta, production\\n\\n1> open a page in VE, add a template. Add a Field name to the template, now delete that name.\\n2>click to add more information again, notice  the previous field name entry is shown  in a list.\\n3>  In the same Field name, type in another name , now delete that name.\\n4> Repeat steps #2 and 3. Until you get the show one more field(this appears after the 4th entry). Click on it and it seems to add nothing to the existing Template data.\\nSame behavior can be seen with Templates having at least 4 parameters, for ex- Reflist.\\nSee screenshots.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14783}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410913625, 'spacePHID': None, 'dateCreated': 1410275700, 'dateModified': 1443278005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70609', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save page button is not fully clickable', 'description': {'raw': \"In Chrome and Internet Explorer it is perfectly possible to click repeatedly on the Save button and achieve nothing. On large portions of it (especially at the top, but you can also place the pointer exactly between the two words and get the same result) the pointer won't change.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410461670, 'spacePHID': None, 'dateCreated': 1410254700, 'dateModified': 1443278005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70602', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to add/edit LabelledSectionTransclusion markers', 'description': {'raw': 'The LST markers <section begin=\"2011-07-25\" /> and <section end=\"2011-07-25\" /> used to be unparsed, but now that Parsoid parses them to <meta>s they\\'re uneditable. Boo.\\n\\n(The actual transclusion {{#lst:Foo|Bar}} as a parser function \"just works\".)\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'stalled', 'name': 'Stalled', 'color': 'yellow'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1410209220, 'dateModified': 1643977417, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70581', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf21] Checking \"Border\" in media settings dialog is not enabling \"Apply changes\" button', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Open Media Settings dialog for a Frameless/Basic type image which does not have \"Border\" set to it.\\n3.Now check the \"Border\" checkbox\\n\\n\\nObserved Result:\\nIt does not enable the \"Apply Changes\" button in the media Settings dialog\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410396413, 'spacePHID': None, 'dateCreated': 1410206160, 'dateModified': 1443278005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70575', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: After you insert a new node, don't select it but drop the cursor immediately after it instead\", 'description': {'raw': 'This is similar to Bug 69711.\\n\\nSteps to reproduce:\\n\\n1.  Type some text:  \"Foo bar baz bat\"\\n\\n2.  Add a citation.\\n\\n3.  Finish typing the sentence.\\n\\n6.  Oops, where did the citation go?\\n\\n\\nResults:\\n\\nWhen you exit the ref dialog, the new ref text remains highlighted, and typing results in it being overwritten by your next character.  \\n\\nExpectation:  after I\\'ve made a ref, de-select the ref and put the cursor at the end, so I can keep writing or add a second ref.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1410205260, 'dateModified': 1643977417, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70573', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When CE gets re-enabled, the cursor always jumps to the beginning index of the first line irrespective of where user wanted to position it', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with VE which has some text in it\\n2.Place somewhere outside the CE to disable it\\n3.Now click at the end of a text to place your cursor on that position of article to make an edit\\n\\nObserved Result:\\nThe cursor jumps to the beginning of the first line of the article.\\n\\n\\nEnvionment:Betalabs,test2,production\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1410200160, 'dateModified': 1416791991, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70569', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Insert > References list is very large in Firefox', 'description': {'raw': 'This may be the opposite of bug 68226:  \\n\\nThe References List dialog in Firefox 31 on my Mac is the expected width, but it is the full height of the screen.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70317'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411417195, 'spacePHID': None, 'dateCreated': 1410150120, 'dateModified': 1443278007, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70545', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Consider aborting link annotation extension on paste of rich content with terminal word-seperator(s)', 'description': {'raw': 'I was cutting & pasting sentences and it worked nearly flawlessly, including the references! :)\\n\\nThough, somehow during cut & paste of a reference to the end of a sentence, the period ended up inside the wiki link:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Tim_Hortons&diff=624612573&oldid=624559527\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-lzhljhpbm3qfphvqyill', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1491406979, 'spacePHID': None, 'dateCreated': 1410140640, 'dateModified': 1491407105, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70542', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Inserted link annotations don't take pre-annotations (but inserted language annotations do)\", 'description': {'raw': 'cmd K (and link button) after a space lost previous italic or/and bold formatting\\n\\nMac OS/X Chrome and Safari\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hhw22zfd2xzrsyc22lp5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410802268, 'spacePHID': None, 'dateCreated': 1410121020, 'dateModified': 1443278007, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70534', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf21] Link inspector is taking a long time on opening up on the first attempt of an edit session', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Click on the link inspector icon from the toolbar\\n\\n\\nObserved Result:\\nThe link inspector is not opening up in the first session\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409961133, 'spacePHID': None, 'dateCreated': 1409954460, 'dateModified': 1443278007, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70467', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: when enabled on a subpage, doesn\\'t show \"< grandparent | parent\" crumb trail', 'description': {'raw': 'Compare https://www.mediawiki.org/wiki/Talk:VisualEditor/Beta_Features/Language\\nwith https://www.mediawiki.org/wiki/Roadmap/Archive\\n\\nThe Flow page doesn\\'t show the < Talk:VisualEditor | Beta_Features \"crumb trail\" to parent pages that you normally see under the page title of a subpage in a <div id=\"contentSub\"><span class=\"subpages\">.\\n\\nI think includes/skins/Skin.php\\'s subPageSubtitle() normally fabricates this.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409952060, 'dateModified': 1621977012, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70465', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor [Regression wmf20] Template dialog no longer displays added template fields' names\", 'description': {'raw': 'Missing template field name\\n\\nOn any page e.g. http://en.wikipedia.beta.wmflabs.org/wiki/0.2619265827018721?veaction=edit\\n\\nClick Insert/Template\\n\\n\\nType a name like \"New template\" and click \"Add template\"\\n\\nIn the resulting box, type \"New template field\" or some such. \\n\\nClick the \"Unknown field\" to add the field to the template\\n\\nResult should show \"New template field\" but instead is blank.  Note that a \"Remove field\" icon is in place for the invisible template field. \\n\\nSee screen shot comparing beta labs with test2wiki.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14914}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409866416, 'spacePHID': None, 'dateCreated': 1409851740, 'dateModified': 1443278010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70406', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[DO NOT USE] VisualEditor Mobile: Support Android (tracking) [superseded by #VisualEditor-MediaWiki-Mobile]', 'description': {'raw': \"We should even if it's a minuscule part of the market for tablets, because we're going to eventually support phones (and for decency's sake).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422405435, 'spacePHID': None, 'dateCreated': 1409789520, 'dateModified': 1492118254, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70372', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cannot type in Korean using Mozilla on Windows 7 with dual-script keyboard', 'description': {'raw': \"Kdammers is running the current version of Mozilla on Windows 7 with a dual-script keyboard.  Typing in Hangul (한글) is not working in VisualEditor:  letters can be removed but when they are typed, they just disappear.\\n\\n\\nStefan2 did some related testing:\\n\\nIbus-hangul (Korean) seems to work correctly in Firefox 32.0. In Chromium 37.0.2062.94, it produces spaces instead of Hangul letters. However, if a syllable only consists of two letters, the syllable shows up after typing in the second letter. It seems that syllables consisting of more than two letters can't be typed in using Chromium.\\n\\nAnthy (Japanese) is broken in both browsers.\\n\\n**See Also**: {T52631}\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1457046550, 'spacePHID': None, 'dateCreated': 1409765460, 'dateModified': 1457046550, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70353', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf20] anoneditwarning notice displays unparsed links with $1 and $2', 'description': {'raw': \"Screenshot of bug.\\n\\nThe anoneditwarning message now takes parameters apparently. ApiVisualEditor.php.\\n\\nSee mediawiki-core's EditPage.php for example.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14741}\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409859524, 'spacePHID': None, 'dateCreated': 1409736780, 'dateModified': 1443278013, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70334', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor should respect [[MediaWiki:Noarticletext]]', 'description': {'raw': '**Author:** `gryllida`\\n\\n**Description:**\\n[[MediaWiki:Noarticletext]] is shown when someone is creating a page, above the edit box. See:\\n\\nhttps://en.wikiversity.org/w/index.php?title=MediaWiki:Noarticletext\\nhttps://en.wikiversity.org/w/index.php?title=Lalala&action=edit\\n\\nVisualEditor should respect this and also show such text in some prominent place.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409781154, 'spacePHID': None, 'dateCreated': 1409710020, 'dateModified': 1417571850, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70322', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switch to source editing dialog too tall', 'description': {'raw': '**Author:** `josephsieh`\\n\\n**Description:**\\nscreen shot of \"Switch to source editing\" dialog too tall issue on Safari.\\n\\nAfter user modified something in Visual Editor and then tries to click on \"Edit\" without clicking \"Save page\", the \"Switch to source editing?\" dialog appears to be too tall as the attached screenshot shows.\\n\\nIt happens on \\n\\nOSX 10.9.4\\nSafari 7.0.6.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70545\\n\\n**Attached**: {F14706}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411417872, 'spacePHID': None, 'dateCreated': 1409705580, 'dateModified': 1443278013, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70317', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding a link right before a wikilinked word leads to unexpected results, including a nowiki', 'description': {'raw': 'This can be seen by placing the cursor right at the beginning of any existing wikilinked word, then trying to add any kind of link. \\nUser\\'s expectation is that this changes the wikilink target with no corruption.\\n\\n<<To reproduce this:\\n* [https://fr.wikipedia.org/w/index.php?title=Boys_band&veaction=edit Edit Boys band on frwiki]\\n* In the history chapter, 4th paragraph, put the cursor before the S of the link to Super Junior\\n* Click on link icon in the toolbar\\n* Copy the URL <code><nowiki>https://fr.wikipedia.org/wiki/B.A.P</nowiki></code> in the link inspector and click Terminé\\n* When previewing modifications, you can see that it has been replaced by <code><nowiki>[[B.A.P]] [[Super Junior|<nowiki/>]][[B.A.P|Super]] Junior</nowiki></code> which shows several problems: there\\'s a link without text displayed, the existing link has been cut in two\\n* And also, what is displayed in VE doesn\\'t match at all what the result will be when saved:\\n** \"Super\" is displayed as an external link, but in the modifications preview, you see it\\'s an internal link\\n** If you hover over \"Super\", both \"Super\" and \"Junior\" get underlined, but in the modifications preview, \"Junior\" is not inside the link\\n** \"Junior\" is displayed as an internal link, but in the modifications preview, you see it\\'s now just text\\n** If you hover over \"Junior\", both \"Super\" and \"Junior\" get underlined, but in the modifications preview, \"Junior\" is not inside a link .>> Instructions by NicoV.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'dateClosed': 1426638000, 'spacePHID': None, 'dateCreated': 1409660820, 'dateModified': 1428689552, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70286', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Documentation for the message Visualeditor-dialog-action-done is misleading', 'description': {'raw': 'The qqq documentation for the message Visualeditor-dialog-action-done is either misleading or I misunderstand it :)\\n\\nIt says: \"Label text for button to exit from a dialog that has no changes to make.\"\\n\\nHowever, this message is used in the link inspector - this is not quite a dialog, and it does make changes.\\n\\nI can think of three options:\\n* I misunderstand something :)\\n* This message shouldn\\'t be used in the link inspector\\n* This message\\'s documentation should be changed\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421258102, 'spacePHID': None, 'dateCreated': 1409645820, 'dateModified': 1427672924, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70281', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable the TemplateData GUI editor on Norwegian Bokmål Wikipedia', 'description': {'raw': \"Just discovered this tool, and since it makes it so much easier to add TemplateData, it would be a huge improvement for us template editors, and consequently for the VisualEditor users out there. Can't see any reason it should be controversial, but if requested I'll bring it up in our village pump.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-jqjb54lbf7psat6shbcc', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409671057, 'spacePHID': None, 'dateCreated': 1409430780, 'dateModified': 1409671057, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70216', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Performance issue with adding Citations in Mobile', 'description': {'raw': 'There is a noticeable lag observed while trying to add any citation in mobile in Beta labs environment.'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1439257531, 'spacePHID': None, 'dateCreated': 1409339820, 'dateModified': 1439257531, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70184', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: non-editable element inserted before a colon', 'description': {'raw': '*Sorry about the lame summary*\\n\\nThis bug can probably have a better title.\\n\\nA rather simple and innocent edit in the Hebrew Wikipedia introduced an element that had no reason to appear in the code. Here\\'s the edit:\\nhttps://he.wikipedia.org/w/index.php?title=%D7%9B%D7%99%D7%91%D7%95%D7%A9%D7%99_%D7%90%D7%9C%D7%9B%D7%A1%D7%A0%D7%93%D7%A8_%D7%94%D7%92%D7%93%D7%95%D7%9C_%D7%91%D7%90%D7%A1%D7%99%D7%94_%D7%94%D7%AA%D7%99%D7%9B%D7%95%D7%A0%D7%94&diff=15812721&oldid=15812716\\n\\nThe problematic element appears between the words \"מטרות נוספות היו\" and the colon.\\n\\nThe element was removed in the following edit:\\nhttps://he.wikipedia.org/w/index.php?title=%D7%9B%D7%99%D7%91%D7%95%D7%A9%D7%99_%D7%90%D7%9C%D7%9B%D7%A1%D7%A0%D7%93%D7%A8_%D7%94%D7%92%D7%93%D7%95%D7%9C_%D7%91%D7%90%D7%A1%D7%99%D7%94_%D7%94%D7%AA%D7%99%D7%9B%D7%95%D7%A0%D7%94&diff=15887470&oldid=15878013\\n\\nWhen editing it in the VisualEditor, the element appears as \"Sorry, this element can only be edited in source mode for now.\"\\n\\nWhen I showed this to David, he thought that it may be somewhat related to the \"unicorn\" patch, but it is not certain.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409312820, 'dateModified': 1424895080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: wikitext warning doesn't auto-hide the first time you enter wikimarkup\", 'description': {'raw': \"Verified with Chrome and Safari.\\nIf you type wikitext ( I tried with * ) and then delete it, the wikitext warning won't go away automatically.\\nIf you click on it to make it disappear, proceed to add more wikitext and delete this again, then the box will auto-hide correctly.\\n\\n(Two square parentheses don't seem to trigger the warning at all?)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51701\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409344203, 'spacePHID': None, 'dateCreated': 1409308440, 'dateModified': 1443278016, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70168', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Applying a link to an invalid title triggers an undo', 'description': {'raw': '1. Type some text which is an invalid title in MW, e.g. \"|InvalidTitle\"\\n2. Select it and hit link\\n-  Notice that there are no suggestions, and no initial link is applied\\n3. Type in a valid page name, e.g. \"Main page\" and press Done\\n-  Notice some of your text has been deleted (by and undo operation) before the link was applied\\n\\nThe bug is actually in core AnnotationInspector#getTeardownProcess. We call a surface undo() to remove the initial annotation, but in the case of an invalid title there is no initial annotation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409337422, 'spacePHID': None, 'dateCreated': 1409306340, 'dateModified': 1443278016, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70167', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'create browser test build for IE11/VisualEditor', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70744'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410541891, 'spacePHID': None, 'dateCreated': 1409239140, 'dateModified': 1410541891, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70126', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor redlink detection should obey Title::isAlwaysKnown (so that links to Special pages, EducationProgram pages and GlobalUserPages render correctly)', 'description': {'raw': 'Education Programme:\\n> On page\\n> https://pt.wikipedia.org/wiki/User:Alpha_Centaurus?veaction=edit&oldid=39924153&uselang=en\\n> the link to\\n> https://pt.wikipedia.org/wiki/Ensino:Universidade_Federal_do_Rio_Grande_do_Sul/C%C3%A1lculo_Num%C3%A9rico_%28MAT01169%29_%282014-2%29\\n> is red, but it should be blue because (from the user\\'s point of view) the page exists.\\n\\nGlobalUserPages:\\n> Viewing https://www.mediawiki.org/wiki/Extension:TemplateData shows a blue link for \"James Forrester\". However, when editing with VisualEditor, the link is red.\\n\\n\\n----\\nSee also: {T134073}'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-mvx4x7ywk2flsaku2dbk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1476319581, 'spacePHID': None, 'dateCreated': 1409234640, 'dateModified': 1476350740, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70123', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The page focus always bumps up to the top irrespective of cursor position', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Tap somewhere in the middle of the page or towards the end\\n\\nObserved Result:\\nThe page focus bumps up to the top of the page, not getting scrolled down to the point where the cursor is actually positioned.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434488620, 'spacePHID': None, 'dateCreated': 1409181600, 'dateModified': 1434492387, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70111', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf19] The trash icon for deleting other templates/parameters/content gets missing from the left panel of transclusion dialog after selecting a required parameter', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Template\\n3.Click on \"Show Options\"\\n4.Add the template \"Cite Web\"\\n5.Select one of those required parameter from the left panel of the dialog\\n6.Add some more template with some optional parameters and content in the transclusion dialog\\n7.Now select one of the required parameter for the \"Cite Web\" template from the left panel\\n8.Now from left panel,select any other template/optional parameter/content or even the \"Cite web\" template \\n\\nObserve that the trash icon that used to appear at the corner of the left panel for other template/optional parameter/content or \"Cite web\" template are not appearing now.\\n\\n\\nSee the screenshots attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14309}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409175070, 'spacePHID': None, 'dateCreated': 1409168760, 'dateModified': 1443278016, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70101', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: .topicon icons are taking editors to linked pages, rather than letting them edit the template, in MonoBook on English Wikipedia', 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Open page containing the {{good article}} (or similar) template in VisualEditor, such as https://en.wikipedia.org/w/index.php?oldid=622810787 (which contains only that template)\\n\\n2.  Click the good article icon/template\\n\\n3.  VisualEditor exits, and you are reading the Wikipedia:Good article page (the same one that you would be reading if you clicked that icon in 'read' mode).\\n\\n\\nExpected behavior:\\n\\n1.  Open page containing {{good article}} in VisualEditor\\n\\n2.  Click the good article icon/template\\n\\n3.  Edit the template just like any other.\\n\\n\\nIt's possible that this can only be reproduced on Windows, because on my Mac, when I open the page, the template isn't even visible.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411509939, 'spacePHID': None, 'dateCreated': 1409099760, 'dateModified': 1443278017, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70074', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Category suggestion lists no longer existing categories', 'description': {'raw': 'Take this query from the suggester:\\n\\nhttps://en.wikipedia.org/w/api.php?format=jsonfm&uselang=en&action=query&list=allcategories&acprefix=1895+es&acprop=hidden&redirects=\\n\\nNow read [[mw:Manual:Category table]]:\\n\"Track all existing categories. Something is a category if it has an entry somewhere in categorylinks, or it once did.\"\\n\\nSo it\\'s logical that something like 1895 establisANONYMOUS IS LEGIONhments is in the suggestion list, but it is really not desirable. It contains many \\'bad\\' words and deleted stuff that we don\\'t really want to present to users.\\n\\n\\nhttps://en.wikipedia.org/w/api.php?format=jsonfm&uselang=en&action=query&list=allcategories&acprefix=1895+es&acprop=hidden&redirects=&acprop=size|hidden\\n\\nThis can be easily solved by adding:\\nacmin=1 to the query.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409083081, 'spacePHID': None, 'dateCreated': 1409044020, 'dateModified': 1443278017, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70025', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Shrink back the Basic Reference dialog size', 'description': {'raw': 'Reference dialog in test2\\n\\nThe size of the Reference dialog got changed to a bigger size after wmf18\\n\\nSee the screenshots attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70601\\n\\n**Attached**: {F14691}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411065647, 'spacePHID': None, 'dateCreated': 1409012040, 'dateModified': 1443278017, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70016', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Open button in link inspector should be disabled when the link target field is empty', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409869692, 'spacePHID': None, 'dateCreated': 1409011560, 'dateModified': 1443278021, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70015', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Category names are taking long time (~6-7 secs)to appear in the Category section', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Add some categories to the page\\n3.Save the page\\n4.Reopen the page and go to the categories section\\n\\nObserved Result:\\nThe categories are not appearing immediately,after waiting for approx. 6-7 secs they do appear in that section.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409011011, 'spacePHID': None, 'dateCreated': 1409009400, 'dateModified': 1417571858, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  {{#tag:ref}} is not processed by VisualEditor, so the references list claims that there are no refs in that group', 'description': {'raw': \"This may be related to bug 51289 and bug 61777.\\n\\n\\nSteps to reproduce:\\n\\n1.  Open a page that contains refs formatted like this:  {{#tag:ref|Text goes here. |group=n |name=Foo}}\\n\\n2.  Add a references list for the group.\\n\\n3.  Read the error message.  VisualEditor says that there are no refs in group 'n' on the page.\\n\\n\\nExpectation:\\n\\nRefs would be properly recognized and displayed even if they use this rather odd format.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409008680, 'dateModified': 1422076039, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70011', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The article Sindhi language cannot be edited in VE if the Language tool is enabled', 'description': {'raw': \"Trying to edit the article [[Sindhi language]] in VE while the language tool is enabled produces gets the browser stuck with the animated loading bar and produces a JavaScript error in the console:\\nUncaught TypeError: Cannot read property 'toLowerCase' of null ve.ce.LanguageAnnotation.js:52\\n\\n(This is from Chrome; the error in Firefox is slightly different, but it's broken there as well.)\\n\\nIf the language tool beta feature is disabled, then the article can be edited.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408987209, 'spacePHID': None, 'dateCreated': 1408870740, 'dateModified': 1443278021, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69955', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Improve nowiki additions to only wrap the string that needs protection', 'description': {'raw': 'Sometimes you want a single quotation mark next to an italicized (or bolded) word. \\nIt would be nice if VisualEditor/Parsoid did something elegant with the wikitext, like \"celui d\\'<nowiki/>\\'\\'Homo sapiens\\'\\'\" instead of wrapping half a sentence inside nowiki tags to deal with a single character.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-56wtmb23orq4pu5liyj5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426100241, 'spacePHID': None, 'dateCreated': 1408839360, 'dateModified': 1438735793, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69950', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Selection overlaps menu in Monobook, so you can't click on the covered items\", 'description': {'raw': \"This might be related to Bug 49524.\\n\\nSee https://commons.wikimedia.org/wiki/File:VE_selection_box_goes_over_menus.png\\n\\nWhen you open https://en.wikipedia.org/w/index.php?oldid=620028233 in Firefox on Windows 7, the sandbox template is autoselected.  If you click on a menu (e.g., to set bold text), the menu drops down but the items that overlap with the auto-selected template can't be chosen.\\n\\nI am unable to reproduce this in either Safari or Firefox on a Mac.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409247861, 'spacePHID': None, 'dateCreated': 1408839060, 'dateModified': 1443278024, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69949', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable DOM editing of transclusion parameters', 'description': {'raw': 'This is needed to allow VisualEditor to support such lovely wikitext as {{echo|{{echo|Foo!}}}} and more complex variations.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1408649880, 'dateModified': 1643977417, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69870', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf18] Save Page no longer completes save actions', 'description': {'raw': 'Save button not working after creating citation\\n\\nAfter fixing https://bugzilla.wikimedia.org/show_bug.cgi?id=69856\\n\\nDo everything to create a Citation as shown in the screen shot. \\n\\nClick Save. Save does nothing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14354}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408664943, 'spacePHID': None, 'dateCreated': 1408645140, 'dateModified': 1443278024, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69864', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor shows double page title after edit when 'edittop' gaget (or similar) is enabled\", 'description': {'raw': \"Screenshot\\n\\nVisualEditor shows double page title after edit when the 'edittop' gaget (or similar) is enabled.\\n\\nThis is because the code to update page's DISPLAYTITLE is too aggressive.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F14331}\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408641962, 'spacePHID': None, 'dateCreated': 1408638660, 'dateModified': 1443278026, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69857', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reinstate the semantic class on the \"Save page\" button', 'description': {'raw': 'The firsteditve tour (the \"first edit\" tour, specialised for VE) relied on the ve-ui-toolbar-saveButton class to attach a guider to the \"Save page\" toolbar button. The class was removed as part of https://git.wikimedia.org/commit/mediawiki%2Fextensions%2FVisualEditor.git/cc089d6bd3334791453c6474c56f49d4a2d243dd.\\n\\nAt the moment, there\\'s no resilient selector that we can use to reference just that element. Can the class be reinstated?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-w3pd7vqenmta6vpmhwcn', 'ownerPHID': 'PHID-USER-w3pd7vqenmta6vpmhwcn', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408553628, 'spacePHID': None, 'dateCreated': 1408547940, 'dateModified': 1443278026, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69784', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Search results (for links, redirects, categories…) should select the exact match by default', 'description': {'raw': 'This is somewhat related to {T64917}.\\n\\nWhen you add an internal link, or otherwise are looking at search results, VisualEditor should defaultly select any page that is an exact match for what you\\'ve typed.  In particular, if you search for \"Computer\", and there actually is a page at [[Computer]], then it should default to [[Computer]], not to [[Computer science]] or whatever else comes up first in the search system.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T71780}\\n{T57390}\\n{T64917}\\n{T71716}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1490394554, 'spacePHID': None, 'dateCreated': 1408396020, 'dateModified': 1490394556, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69716', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"TypeError: undefined is not a function\" when saving after pasting an external link into a basic citation', 'description': {'raw': 'I get \"TypeError: undefined is not a function\" when saving after pasting an external link into a basic citation. This is rather insidious, as the error only happens when trying to save the page, which causes you to lose some work. (The same error happens when trying to switch to wikitext.)\\n\\n1. https://en.wikipedia.org/wiki/Combining_Grapheme_Joiner?veaction=edit\\n2. Click the \"[1]\" link in the first paragraph, \"Add label\" from inspector\\n3. Ctrl+X to cut the link (which should have been automatically selected)\\n4. Click \"Cite\" → \"Basic\" to insert citation at the same spot\\n5. Ctrl+V to paste the link, \"Insert reference\"\\n6. Click \"Save page\", receive error\\n\\nI\\'m not sure if step 2 is relevant, but I can consistently reproduce like this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414008955, 'spacePHID': None, 'dateCreated': 1408381140, 'dateModified': 1417571687, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69709', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Stop using inline <img> for thumbnail magnify icon', 'description': {'raw': \"Let's stop using inline <img> for thumbnail magnify icon. According to bug 69277 comment 11, there are 87619775 requests per day for 'magnify-clip.png'. It should be embedded in some piece of CSS.\\n\\n(Bug 65160 / [[mw:Thumbnail style update]] call for complete removal of the icon, but it would only affect the Vector skin.)\\n\\n--------------------------\\n**Version**: 1.24rc\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411168921, 'spacePHID': None, 'dateCreated': 1408301100, 'dateModified': 1411169229, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69673', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: tapping into middle of link inspector text causes lots of issues', 'description': {'raw': 'Steps to repro:\\n\\n1. In prod/stable on iPad, enter VE edit mode and tap on a 2-word wikilink (e.g. [[European robin]])\\n2. Open link inspector\\n3. Tap on the end of the second word (e.g., after \"European\") to drop cursor between the two words\\n4. Attempt to backspace and enter new text\\n\\nI\\'ve seen a number of weird things happen after this step:\\n\\n* No suggestions come up in the drop-down, even when there clearly should be some\\n* Adding new text or spaces is impossible; you can only backspace\\n* Backspacing too fast closes the dialog (known issue) or crashes Safari (not sure if known issue)\\n\\nNone of these seem to happen if you tap at the end of the text in the link inspector (e.g., after \"robin\") and backspace/add new text from there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-yu5wnmvkjecufsjgh2fa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434487324, 'spacePHID': None, 'dateCreated': 1408053060, 'dateModified': 1434492385, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69578', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Category input box is too small (sometimes)', 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Add a short category or three.  (At en.wp, you can add Category:1, Category:2, and Category:3, etc.)  The box for adding the next cat should still be on the same (first) line.\\n\\n2.  Now try to add a very long category name.  If you're on Meta, try Category:Association of Wikipedians - AWWDMBJAWGCAWAIFDSPBATDMTD\\n\\n\\nResult:  \\n\\nThe search field pops up, but you can't really see much of it.  In particular, unless what you're trying to add can be reliably added from the first and last few characters, then you might add the wrong category.\\n\\n\\nExpectation:  \\n\\nThe category field will be wide enough to see what's in the search list.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57200\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1613505051, 'spacePHID': None, 'dateCreated': 1408050900, 'dateModified': 1615468393, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69574', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots', 'description': {'raw': 'Fonts for Japanese and Chinese must be installed for VisualEditor localized screenshots. Without this all the screenshots in these languages show squares instead of the correct characters.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412025554, 'spacePHID': None, 'dateCreated': 1408020900, 'dateModified': 1423533627, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69535', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Undo resizing of image with explicit dimension in core doesn't render correctly\", 'description': {'raw': \"1. Create an image in VE standalone with no width/heigh attrs (using the html editor mode)\\n2. Resize the image in VE and undo\\n\\nThe image doesn't go back to it's original size (in the view).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408017797, 'spacePHID': None, 'dateCreated': 1408015440, 'dateModified': 1443278033, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69531', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cannot copy text when dm.surface.enabled === false', 'description': {'raw': \"**Author:** `ryan.wold`\\n\\n**Description:**\\nWhen disabling an Editor's .target.surface (by calling .disable()), the text is no longer editable, which is great.  However, the text in the disabled Editor cannot be copied and pasted.  It does not appear to make it to the clipboard. \\n\\nDesired behavior is that the text can be be copied even when the editor is disabled.  Or perhaps there could be a setting/option around that.\\n\\n\\n\\nWe traced this to ve.dm.Surface.prototype.changeInternal, where it returns immediately if the surface is disabled.\\n\\nif ( !this.enabled ) {\\n  return;\\n}\\n\\nI found this here: https://doc.wikimedia.org/VisualEditor/master/source/ve.dm.Surface.html#ve-dm-Surface-method-changeInternal\\n\\n\\nI'm using OSX Mavericks and Google Chrome Version 36.0.1985.125.\\n\\nThanks!\\n\\n- Ryan Wold\\n  ryan.wold@neo.com\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416318771, 'spacePHID': None, 'dateCreated': 1407976320, 'dateModified': 1417571676, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69515', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Link tool is too small when adding captions to new images', 'description': {'raw': '\"Before\".  This is what you see at step #4.\\n\\nSee attached screenshots.  \\n\\nSteps to reproduce:\\n\\n1.  Open VisualEditor and Insert > Media.\\n\\n2.  Pick and image and add a caption.\\n\\n3.  Select a word and press Command-K to make an internal link. \\n\\n4.  Notice that the link inspector ought to be bigger, so you can see all the new buttons.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14165}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410202626, 'spacePHID': None, 'dateCreated': 1407973920, 'dateModified': 1443278033, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69511', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspectors close immediately in IE', 'description': {'raw': \"In Internet Explorer, if you open a link or comment inspector, it closes immediately after opening. It doesn't matter if you use Ctrl+K or the context or the toolbar or double-click or enter to open the inspector, the exact same thing happens.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408666091, 'spacePHID': None, 'dateCreated': 1407970620, 'dateModified': 1443278034, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69503', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: If 'summary' parameter is provided in URL, it should be the default edit summary\", 'description': {'raw': 'This is related to bug 50872.\\n\\nIf you click the edit link on a section, then that section\\'s heading is pre-populated in the edit summary when you save.\\n\\nThis does not work very well if you have turned on https://en.wikipedia.org/wiki/MediaWiki:Gadget-edittop.js (\"Add an [edit] link for the lead section of a page\") in the gadgets for your preferences.  Editing the first (lead) section of the page gets a suggested edit summary that includes the first section heading on the page i.e., the section heading immediately underneath the section you were actually editing.\\n\\nThe link for \\'edit source\\' says:\\n\\nhttps://en.wikipedia.org/w/index.php?title=User:WhatamIdoing&action=edit&section=0&summary=/*%20top%20*/%20 \\n\\nThe link for \\'edit\\' says:\\n\\nhttps://en.wikipedia.org/w/index.php?title=User:WhatamIdoing&veaction=edit&vesection=1\\n\\nThe subsequent section editing links are all correct.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409263347, 'spacePHID': None, 'dateCreated': 1407969600, 'dateModified': 1443278034, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69501', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"When the user adds an internal link that looks like a URL, MediaWiki needs to insert a ':' prefix for it to work\", 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Open VisualEditor and select a word.\\n\\n2.  Press Command-K to open the link inspector.\\n\\n3.  We\\'re going to make an external link to http://www.example.com so start typing:  h-t-t-p-:-/-/-w-w-w-\\n\\n4.  Why is it trying to find an internal page for the URL I\\'m typing?\\n\\n\\nIf you\\'re obviously typing in a URL, the search feature should be disabled.  Offering to make a link to the \"local page\" http://www.example.com risks broken links like this:  https://en.wikipedia.org/w/index.phpdiff=621124784&oldid=620566012\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=44011'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1407968460, 'dateModified': 1643977418, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69500', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Use {{!}} rather than <nowiki>|</nowiki> when inserting a | in a template argument', 'description': {'raw': 'In https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=621079160&oldid=621075505 it is pointed out that if an argument to a template contains a | then <nowiki>|</nowiki> is added. The new magic word {{!}} might be a better alternative.\\n\\nSee also bug 67863\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-56wtmb23orq4pu5liyj5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426100252, 'spacePHID': None, 'dateCreated': 1407949080, 'dateModified': 1438735797, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69482', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference & cite tooltips should show content snippets, instead of generic labels', 'description': {'raw': 'For citation template references we may also want to specify a subset of parameters to show first.\\nLinks and citation mocks:\\n{F18090}\\n\\n{F18092}\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1424972571, 'spacePHID': None, 'dateCreated': 1407939960, 'dateModified': 1660398884, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69474', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If you just change an image, the border parameter setting is lost', 'description': {'raw': 'When you just change image on a media, the border parameter is lost.\\n\\nhttps://test2.wikipedia.org/w/index.php?title=BorderLost&diff=98843&oldid=98842\\n\\nSafari/Mac OS X\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hhw22zfd2xzrsyc22lp5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409242159, 'spacePHID': None, 'dateCreated': 1407887580, 'dateModified': 1443278036, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69450', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After inserting a comment and a link, a cursor is moved at the end of the line, but typed text gets inserted between the comment and the link', 'description': {'raw': 'screenshot\\n\\n1> open a page in VE, insert a comment.\\n2> While the comment is still highlighted, insert a link. Notice the cursor is in between the comment and the link.\\n3>Now select the Language style text. Click “Done” in the language inspector.\\nNotice the cursor has now moved to the end of the comment. Type in some text, it gets inserted after the link. See screenshot.\\n\\nTry the above steps, but instead of comment insert a Formula.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14630}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1407858060, 'dateModified': 1421282850, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69438', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'The \":\" char in a definition list should be parsed differently depending on html-tag context it is found in.', 'description': {'raw': 'See e.g. http://parsoid-lb.eqiad.wikimedia.org/wikimania2014wiki/Submissions%2FVisualEditor_%E2%80%94_engineering_against_the_odds?oldid=47825 vs https://wikimania2014.wikimedia.org/wiki/Submissions/VisualEditor_%E2%80%94_engineering_against_the_odds?oldid=47825\\n\\nWikitext:\\n\\n; \\'\\'\\'Sunday August 10, 12:30, [[Frobisher 123]]\\'\\'\\'\\n\\nParsoid HTML:\\n\\n<dl><dt> <b>Sunday August 10, 12</b></dt><dd><b>30, <a rel=\"mw:WikiLink\" href=\"./Frobisher_123\">Frobisher 123</a></b></dd></dl>\\n\\n\\nPHP parser HTML:\\n\\n<dl><dt><b>Sunday August 10, 12:30, <a href=\"/wiki/Frobisher_123\" title=\"Frobisher 123\">Frobisher 123</a></b></dt></dl>\\n\\nIt looks like this might be a syntax ambiguity, but hopefully we can have bug-for-bug compatibility with the PHP parser? :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1418248339, 'spacePHID': None, 'dateCreated': 1407406200, 'dateModified': 1428510506, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69219', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: visualeditor-beta-warning help mentions non-existent Cancel button', 'description': {'raw': 'VE\\'s help icon popup includes this \"visualeditor-beta-warning\" text:\\n\\n\"VisualEditor is in \\'beta\\'. You may encounter software issues, and you may not be able to edit parts of the page. To switch back to source editing at any time without losing your changes, open the dropdown next to \\\\\"{{int:visualeditor-toolbar-cancel}}\\\\\" and select \\\\\"{{int:visualeditor-mweditmodesource-title}}\\\\\".\"\\n\\nBut I don\\'t see this Cancel button in the VE UI these days. The page options \"hamburger\" dropdown is now between (?) and [Save page].  It would be more helpful to show the hamburger icon in the help message, maybe WikiFont some day.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407361045, 'spacePHID': None, 'dateCreated': 1407356520, 'dateModified': 1443278037, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69201', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In the image advanced settings dialog, the alignment button order is wrong in RTL UI', 'description': {'raw': 'In the image advanced settings dialog the image alignment buttons say \"right\", \"center\" and \"left\". In RTL UI their order is confusing, because the \"right\" button is on the \"left\" and vice versa. They should be in a more logical order. (The icons are correct, however.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407331985, 'spacePHID': None, 'dateCreated': 1407316680, 'dateModified': 1443278040, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69165', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'vagrant_ram overrides sometimes ignored/forgotten', 'description': {'raw': \"I have two overrides for vagrant_ram:\\n\\n* CirrusSearch has a puppet-managed override setting it to 1536\\n* I have a .settings.yaml with the following contents:\\n---\\nvagrant_ram: 2048\\ngit_user: ''\\npuppet_debug: true\\n\\nHowever, sometimes it's lower than both of those.  I.E.:\\n------\\n             total       used       free     shared    buffers     cached\\nMem:           993        933         60         18          0         23\\n-/+ buffers/cache:        909         84\\nSwap:            0          0          0\\n------\\n\\nTested with 6b27f39 (I know that's a little old, so feel free to close if you think it's been fixed since).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=69720\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-2rnfxoezl66afpa7w7in', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410294111, 'spacePHID': None, 'dateCreated': 1407194880, 'dateModified': 1496861918, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69131', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  \"Cancel\" button in the Save dialog is confusing.  How about \"Resume editing\"?', 'description': {'raw': 'The new Save dialog has two buttons at the top:  \"Cancel\" and \"Save\"\\n\\nIt\\'s not clear whether Cancel means \"exit this dialog\" or \"lose all your work\".  Please change the label to something like \"Return to editing\" or \"Resume editing\", or something that clearly indicates that this button allows you to keep editing and will not exit VisualEditor and cause you to lose all of your work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410471186, 'spacePHID': None, 'dateCreated': 1407175800, 'dateModified': 1443278040, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69116', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"LivePreview doesn't allow interaction with page content outside of #wikiPreview (it is not passed to mw.hook)\", 'description': {'raw': 'Currently, LivePreview only passes the $wikiPreview to the hook\\nhttps://github.com/wikimedia/mediawiki/blob/6709a1fd082bcbc1b89d499edeafa04fd2e8a517/resources/src/mediawiki.action/mediawiki.action.edit.preview.js#L101\\nbut the script changes the page content in many other places:\\nhttps://github.com/wikimedia/mediawiki/blob/6709a1fd082bcbc1b89d499edeafa04fd2e8a517/resources/src/mediawiki.action/mediawiki.action.edit.preview.js#L31-L43\\nThe new content for these parts should also be made available to the user, by passing them to the hook (as VisualEditor does, for example\\nhttps://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/ccdc215a9882d6bb3e079ca822f64c9089c0d363/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.js#L1574\\n).\\n\\nThis would allow scripts like\\nhttps://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-featured-articles-links.js&oldid=619815637\\nto update the modifications of the language links after the user makes some changes and use the live preview (in the example, the \"badges\" for featured/good articles in other languages).\\n\\nAlso, this is likely what UniversalLanguageSelector needs in order to fix bug T53029.'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1407163740, 'dateModified': 1724618220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69108', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting <em> content into a VE-MW surface should down-convert <em>s to <i>s (and <strong>s to <b>s)', 'description': {'raw': 'See diff at https://de.wikipedia.org/w/index.php?title=Schotts_Sammelsurium&diff=prev&oldid=132639553 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1428475764, 'spacePHID': None, 'dateCreated': 1406824380, 'dateModified': 1428475791, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68928', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar should update fixed position after resize if MediaWiki layout changed (e.g. Vector skin goes below 982px SD/HD boundary)', 'description': {'raw': 'When resizing the window, after a certain point the MediaWiki page layout may change (media queries). This affects the offset from the left side of the page (specifically, width of the sidebar).\\n\\nHowever the toolbar caches its computed offset once and never updates it.\\n\\n1. Open window wider than 1024px with Vector skin in MediaWiki.\\n2. Enter VisualEditor.\\n3. Resize to < 980px.\\n\\nExpected:\\n\\nSidebar shrinks (per Vector styles) and toolbar should still align with left edge of the page.\\n\\nActual:\\n\\nSidebar shrinks but toolbar stays behind causing an awkward gap to appear as well as odd interruption in the shadow. It results in part of the Save page button to go off-screen. \\n\\nOther:\\n\\nThe reverse happens as well. Opening a narrow window and scaling it up will cause it to stay behind in the other direction. It results in part of the toolbar overlapping links in the sidebar.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414448207, 'spacePHID': None, 'dateCreated': 1406808480, 'dateModified': 1417571677, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68916', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Put in hacks to scrub plugin garbage (e.g. myEventWatcherDiv)', 'description': {'raw': \"These seem to be the leading cause of edit corruption right now.\\n\\nmyEventWatcherDiv: https://ru.wikipedia.org/?diff=64516612 https://ru.wikipedia.org/?diff=64516412 https://pt.wikipedia.org/?diff=39659121 https://pt.wikipedia.org/?diff=39659108\\n\\n<embed> tags: https://pt.wikipedia.org/?diff=39696565\\n\\n<object> tags: https://fr.wikipedia.org/?diff=105796883 https://fr.wikipedia.org/?diff=105796959 https://fr.wikipedia.org/?diff=105797061\\n\\nI'm thinking we should put in hacks to remove these kinds of tags. Maybe at the point where we serialize the HTML and send it to Parsoid (ve.init.mw.Target#getHTML). If these tags are added immediately upon document creation (we'd need to get our hands on one of these bad plugins to test that) we could also consider trying to work around this in ve.createDocumentFromHtml instead. I suspect, though, that these tags are probably added asynchronously, and probably only in cases where we fall back to the iframe trick because DOMParser HTML support is not available.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412114053, 'spacePHID': None, 'dateCreated': 1406788020, 'dateModified': 1417571832, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68900', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression]Disable the context menu for the Basic reference/Group Reference/Math/Reference list for mobile', 'description': {'raw': 'The context menu for Basic Reference is still appearing, letting user to get stuck inside it after adding dfferent elements in it.\\nWe need to disable it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1428507916, 'spacePHID': None, 'dateCreated': 1406774460, 'dateModified': 1428507916, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68897', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor lost the first character when inputting with some IME', 'description': {'raw': '**Author:** `hu60.cn`\\n\\n**Description:**\\nThere is a strange trouble happen when I edit with Baidu Pinyin (a Chinese IME) on Firefox runing on Windows 8.1. Baidu Pinyin can input two or more characters once. When I input \"你好\" at once, display is OK. But when I save or delete some characters, the display refreshs and \"你\" lost, a blank instead of the character.\\n\\nExample:\\n\\nI input \"可视化编辑器已可用。\"\\n\\nAnd save, it looks like:\\n\\n 视化 辑器 可用。\\n\\nThe first character at each input lost.\\n\\nHowever, when I switch IME to Microsoft Pinyin, the BUG disappear. All input works fine. Switch to Baidu Pinyin, the BUG continuing.\\n\\nI don\\'t know what happened.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows 8.1\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1406770740, 'dateModified': 1702778267, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68893', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile:CE is getting zoomed in on rotating the screen orientation in iPad Mini', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with Mobile VE\\n2.Place the cursor anywhere in CE\\n3.Change the screen orientation to landscape\\n4.Again rotate the screen\\n\\nObserved Result:\\nCE gets zoomed in each time I rotate the screen\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434487201, 'spacePHID': None, 'dateCreated': 1406760900, 'dateModified': 1434492379, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68883', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Automatic newline prepending to table-template causes incorrect rendering and messed up HTML in Parsoid parser', 'description': {'raw': \"+++ This bug was initially created as a clone of Bug #68297 +++\\n\\nOn mediawiki.org, there is a family on fancy templates like [[mw:Template:MW 1.23]] that generate a right-floated MediaWiki version number in a frame.\\n\\nThese templates generate a wikitext table (starting with '{|'), which means that due to bug 529 / bug 12974 a newline is prepended before it. This behavior is incredibly annoying in practice, but it seems that we're very much wedded to it because it made Parsoid people's lives easier.\\n\\nHowever, Parsoid rendering of this particular template is inconsistent with PHP. On [[mw:Manual:Skinning#Localisation_messages]], PHP generates an empty paragraph before the table, while Parsoid doesn't and produces an about-grouped pair of <span>\\\\n</span><table>…</table> (the span tag only contains the prepended newline).\\n\\nThis rendering, that looks good in Parsoid/VisualEditor, therefore looks like crap in PHP parser.\\n\\nNote that the <span> is not nested in a <p> or any other block-level element, it just sits there right in the <body>. (It is not visible since, as I mentioned, it just contains some whitespace.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1590706405, 'spacePHID': None, 'dateCreated': 1406735100, 'dateModified': 1590706405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68862', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Cannot type the reference name inside Re-use existing reference dialog unless select a reference from that dialog', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with Mobile VE\\n2.Add few references \\n3.Now open Re-use existing reference dialog\\n4.Try to type a reference name in the field\\n\\nObserved Result: \\nNothing happens\\n\\n5.Save the page\\n6.Reopen the page and try again typing reference name in the field,\\n\\nObserved Result:\\nNothing happens\\n\\n\\n7.Now select any reference from the list\\n8.Reopen the Re-use dialog,try typing a reference name in that dialog\\n\\nObserved Result\\nthis time it will work\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434488531, 'spacePHID': None, 'dateCreated': 1406673660, 'dateModified': 1434492403, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68824', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Language Inspector is not opening in the caption of the Media Settings dialog when in insertion mode (because dm.document's this.lang is null).\", 'description': {'raw': 'screenshot1\\n\\nEnvironment- test2\\n\\nSteps-\\n1> open a page in VE.\\n2> Insert ->Media. \\n3>Select to add a media file. Opens the Media Settings dialog.\\n4>Now click on “Caption” pane and Select Language from the text style menu, closes the drop down.\\n5>Cursor is at the beginning of the line. Click again on the style text menu to see that the Language is selected . See screenshots.\\n6> Notice typing the first letter deselects the Language from the drop-down, and so the language inspector never appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14328}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406765072, 'spacePHID': None, 'dateCreated': 1406649060, 'dateModified': 1443278047, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68808', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Selecting the Alt Text box in the Media Settings dialog should disable the Caption box's toolbar\", 'description': {'raw': 'screenshot\\n\\nEnvironment- test2,betalabs, production.\\nSteps-\\n1> Open a page in VE.\\n2> Insert ->Media. \\n3>Select to add a media file. Opens the Media Settings dialog.\\n4>Now click on “Alternative Text”. This should make the “Caption” inaccessible, but it is not. See screenshot.\\nNow click on Caption pane, and then into Alternative Text, this makes the toolbar in the Caption pane blurred.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14322}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406670241, 'spacePHID': None, 'dateCreated': 1406647800, 'dateModified': 1443278047, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68806', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid list with newlines roundtrip issue: HTML \"<ul><li>asd\\\\nsdf</li></ul>\" → Wikitext \"* asd\\\\nsdf\" → HTML \"<ul><li>asd</li></ul><p>sdf</p>\"', 'description': {'raw': \"Take this HTML:\\n```\\n<ul><li>asd\\nsdf</li></ul>\\n```\\nParse to wikitext:\\n```\\n* asd\\nsdf\\n```\\nParse back to HTML:\\n```\\n<ul><li>asd</li></ul>\\n<p>sdf</p>\\n```\\nI'm not sure what should happen here, but definitely not this.\\n\\nIt's rather easy to run into this in VisualEditor – take a paragraph with newlines and convert it to a list item. I ran into it making this edit: https://en.wikipedia.org/w/index.php?title=Polish_nationality_law&diff=prev&oldid=618961884 (I manually replaced the newlines with spaces before saving).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**: {T55568}\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1425599006, 'spacePHID': None, 'dateCreated': 1406638920, 'dateModified': 1425599006, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68800', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Opening the link inspector and then closing, while selecting an image moves the image to the previous position', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Make it thumbnail-left\\n4.Now while the image is selected,Open the link inspector tool\\n5.Without making any change, just close the link inspector by clicking on Done button\\n  \\nObserved Result:\\nThe image gets repositioned as thumbnail-right again.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410031260, 'spacePHID': None, 'dateCreated': 1406577840, 'dateModified': 1443278048, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68762', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Unable to upload new version of images in commons beta lab', 'description': {'raw': 'Output of the error in commons beta lab\\n\\nError: \\n\\nCould not read or write file \"mwstore://local-backend/local-public/3/3d/VisualEditor_save_dialog-he.png\" due to insufficient permissions or missing directories/containers.\\n\\nCould not store file \"/tmp/UgKpr4\" at \"mwstore://local-backend/local-public/3/3d/VisualEditor_save_dialog-he.png\".\\n\\nI had got similar error while uploading images through API: \\n\\n{    \\n     \"servedby\": \"deployment-mediawiki02\",     \\n     \"error\":\\n          {         \\n              \"0\": [             \"backend-fail-usable\",             \"mwstore://local-backend/local-public/6/68/VisualEditor_Insert_Menu-he.png\"         ],         \\n              \"1\": [             \"backend-fail-store\",             \"/tmp/owzHOG\",             \"mwstore://local-backend/local-public/6/68/VisualEditor_Insert_Menu-he.png\"         ],         \\n              \"code\": \"internal-error\",         \\n              \"info\": \"An internal error occurred\"     \\n          } \\n}\\n\\nScenario: \\n\\n* I go to one of the image which I had already uploaded in commons[0].\\n\\n* I click on upload new version of this file at the bottom of the page.\\n\\n* I add a new image[1] by browsing my file system and I click Upload file.\\n\\n* Then I get the error reported above or the image in attachment.\\n\\n-\\n[0]: http://commons.wikimedia.beta.wmflabs.org/wiki/File:VisualEditor_save_dialog-en.png\\n\\n[1]: http://commons.wikimedia.beta.wmflabs.org/w/index.php?title=Special:Upload&wpDestFile=VisualEditor_save_dialog-en.png&wpForReUpload=1\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14238}'}, 'authorPHID': 'PHID-USER-b5bosdf7b7zp3vqofbug', 'ownerPHID': 'PHID-USER-z3l4i7dl52qicxtephy5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-z3l4i7dl52qicxtephy5', 'dateClosed': 1416949018, 'spacePHID': None, 'dateCreated': 1406576520, 'dateModified': 1564509090, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68760', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Comment icon is truncated', 'description': {'raw': 'Screenshot\\n\\nSee screenshot, from \"Barack Obama\" on enwiki beta. I assume it\\'s meant to be an entire orange circle...\\n\\nThis was seen in Firefox 30.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14125}'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406594236, 'spacePHID': None, 'dateCreated': 1406541780, 'dateModified': 1443278051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68721', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Please mention a way of reporting bugs in the Save dialog', 'description': {'raw': 'From User:Encyclopedant:\\n\\nThe Save dialog should have a link to open a new window to a bug report form. This is a good time to start a bug report because you have what you need at hand to write clearly about the bug.\\n\\nThere is no link to report a bug. There is a \"leave feedback\" item under the ? help link in the editor toolbar, but that\\'s kind of hidden, and it doesn\\'t take you to a real bug report form.\\n\\nThere should be a link to open a new window to a bug report form. The link should be explicit that you won\\'t lose what you\\'re doing and that the bug report form will open in a new window.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1438370753, 'spacePHID': None, 'dateCreated': 1406497740, 'dateModified': 1438370753, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68692', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: version number in the help panel must be bidi-isolated', 'description': {'raw': \"The version number in the help panel must be bidi-isolated so it won't mess up the date in RTL wikis.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406742261, 'spacePHID': None, 'dateCreated': 1406488800, 'dateModified': 1443278051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68688', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Typing over a link doesn't undo correctly\", 'description': {'raw': '1. Select a link fully\\n2. Type one letter\\n3. Press undo\\n\\nObserver the first letter of the link is no longer linked.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406593724, 'spacePHID': None, 'dateCreated': 1406466900, 'dateModified': 1443278052, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68677', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"browsertests: Error: Working directory '/srv/browsertests/tests/browser' does not exist (and others)\", 'description': {'raw': 'Something wrong with the browsertests role, got after http://paste.debian.net/111811/\\n\\nNotice: /Stage[main]/Role::Browsertests/File[/srv/browsertests/config]/ensure: created\\nNotice: /Stage[main]/Role::Browsertests/File[/srv/browsertests/config/secret.yml]/ensure: defined content as \\'{md5}b0aa09943ae3b5df22215876b3573a05\\'\\nError: Working directory \\'/srv/browsertests/tests/browser\\' does not exist\\nError: /Stage[main]/Role::Browsertests/Browsertests::Bundle[/srv/browsertests/tests/browser]/Ruby::Bundle[/srv/browsertests/tests/browser]/Exec[bundle_install_/srv/browsertests/tests/browser]/returns: change from notrun to 0 failed: Working directory \\'/srv/browsertests/tests/browser\\' does not exist\\n\\n[...]\\n\\nNotice: /Stage[main]/Browsertests/Mediawiki::User[Selenium_user]/Exec[mediawiki_user_Selenium_user]/returns: include_once \"$IP/extensions/WikimediaIncubator/WikimediaIncubator.php\";Account exists. Perhaps you want the --force option?\\nError: php5 createAndPromote.php Selenium_user vagrant returned 1 instead of one of [0]\\nError: /Stage[main]/Browsertests/Mediawiki::User[Selenium_user]/Exec[mediawiki_user_Selenium_user]/returns: change from notrun to 0 failed: php5 createAndPromote.php Selenium_user vagrant returned 1 instead of one of [0]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-7bifphmxtcqgvdofuzla', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406608897, 'spacePHID': None, 'dateCreated': 1406399160, 'dateModified': 1506469726, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68625', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursoring off focusable nodes scrolls viewport to the top of the document', 'description': {'raw': \"Steps:\\n\\n1. Open http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit\\n2. Scroll to bottom\\n3. Select the gallery\\n4. Cursor right\\n5. Press a letter.\\n\\nExpected outcome: Cursor ends up in slug after the gallery, with an 'a' in it; focus stays.\\n\\nActual outcome: Focus moves to the top of the document, then restores when 'a' is typed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68708\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407065093, 'spacePHID': None, 'dateCreated': 1406322000, 'dateModified': 1443278055, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68589', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The link text is not appearing in the link target field inside the link inspector for Android', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with Mobile VE in Android with Chrome browser\\n2.Type a text in CE\\n3.Select the text\\n4.Open the link inspector\\n\\nObserved Result:\\nThe link text is not appearing inside the link inspector in the link target field, it is just empty.\\n\\nEnviornment:Betalabs, test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'dateClosed': 1430341151, 'spacePHID': None, 'dateCreated': 1406316240, 'dateModified': 1430349773, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68585', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cannot include the same existing reference after adding it once in an article', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE which has 4 citations \\n2.Open Cite>Re-use\\n3.Select the first reference to re-use\\n4.Now again open the use existing reference dialog and observe that the last reference that you added is selected\\n5.Try to add it in the article\\n\\n\\nObserved Result:\\n\\nIt does not get added, if you select some other reference and then try to add the previous one , it will work\\n\\n\\nEnvironment:Betalabs, test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68869'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406767152, 'spacePHID': None, 'dateCreated': 1406311980, 'dateModified': 1443278058, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68582', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'The checkboxen in the save dialog wrap poorly if the texts are too long', 'description': {'raw': 'VisualEditor: in the saving dialog, the \"Watch this page\" box can move to the next line with very large spacing between the lines. This happens in languages where it\\'s longer than it is in English.\\n\\nHere\\'s a screenshot of the problem (in Russian):\\n\\n{F14387}\\n\\nPossible solutions include:\\n* Putting these boxes on separate lines form the start.\\n* Making the line spacing smaller. This is a bit problematic, because the text of the second box may appear under the second, and this may be confusing.\\n'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1439834067, 'spacePHID': None, 'dateCreated': 1406297400, 'dateModified': 1441125404, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68572', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding nowiki tags in unrelated edit', 'description': {'raw': 'https://fr.wikipedia.org/w/index.php?title=M%C3%A9thyl%C3%A8nedioxypyroval%C3%A9rone&curid=7265462&diff=105673189&oldid=102426146\\n\\nIf you change anything in the template, nowiki tags will be added into the IUPAC name field. Also happens for the same article in other languages where the name is written in the same way (i.e. English or Spanish).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-56wtmb23orq4pu5liyj5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-56wtmb23orq4pu5liyj5', 'dateClosed': 1430474728, 'spacePHID': None, 'dateCreated': 1406216520, 'dateModified': 1438735772, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68511', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Language dialog launched from inspector doesn't open in a global overlay\", 'description': {'raw': 'Environment-test2\\n\\nsteps-\\n\\n1> open a page in VE and open language inspector.\\n2> Click upon \"English\" in the inspector, to open the Language Selector dialog.\\n3> Now click on Language selector icon on top of the page, beside the username link (This extension is used for viewing pages in the language specified by the user\\'s preferences).\\n4> Notice dialog saying \"Select a Language\" appears and the Language Inspector gets closed.But the Language Selector dialog(with two-letter code for languages) is still open.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406677067, 'spacePHID': None, 'dateCreated': 1406156220, 'dateModified': 1443278062, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68486', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"TypeError: Cannot read property \\'context\\' of undefined\" on pressing return after a reference node', 'description': {'raw': \"Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Place the cursor after a reference note\\n3.Press return\\n\\nObserved Result:\\n\\nUncaught TypeError: Cannot read property 'context' of undefined appears and the cursor jumps to the beginning of the document\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406143164, 'spacePHID': None, 'dateCreated': 1406141820, 'dateModified': 1443278065, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68462', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: after dismissing the little pink saving error window, the Save page button remains disabled', 'description': {'raw': 'I tried editing a page. I pressed Save and received a little \"Something went wrong\" window. I pressed \"Dismiss\". I wanted to try saving again, but the \"Save page\" button was disabled.\\n\\nIt should probably be re-enabled.\\n\\nVE Version: 234e4e6, on mediawiki.org.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412378420, 'spacePHID': None, 'dateCreated': 1406140800, 'dateModified': 1417571699, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68460', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting Whitespaces at the end of a preformatted text takes the cursor out of the pre tags.', 'description': {'raw': 'screenshot_chrome1\\n\\nIn Chrome 36-\\nScenario#1-\\n1> Open a page in VE and select Preformatted from text style menu.\\n2> enter some text at the beginning and hit the spacebar till the cursor reaches the end of the line. Further pressing the spacebar takes the cursor out of the </pre> tag. See screenshot_chrome1.\\n\\nScenario#2- tried the above steps, but with some characters at the end of the line and then inserting whitespace.See screenshot_chrome2. The cursor still  moves out.\\n\\nIn FF 31-\\nTried the above steps without any characters at the end of the line and just inserting whitespaces. The cursor moves out.\\n\\nIn Safari- No issue found.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14120}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429610947, 'spacePHID': None, 'dateCreated': 1406137200, 'dateModified': 1441065332, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68455', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Breadcrumb doesn't reappear upon saving page\", 'description': {'raw': 'After using VE to edit a subpage in a namespace with subpages enabled, and saving changes, the breadcrumb link (< ParentPageName) underneath the page title does not come back.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406311553, 'spacePHID': None, 'dateCreated': 1406111820, 'dateModified': 1443278065, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68432', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add non-breaking space (nbsp) to the \"special character\" dialog', 'description': {'raw': '**Author:** `misc2006`\\n\\n**Description:**\\nThe most obvious way to add a non-breaking space (other than typing it, see T53045) would be the Insert -> Special Characters dialog.\\n\\n--------------------------\\nAlternative: {T53045}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1617164550, 'spacePHID': None, 'dateCreated': 1406106000, 'dateModified': 1681387852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide tooltips for some items in the Special Character inserter so users can tell items from each other', 'description': {'raw': '**Author:** `misc2006`\\n\\n**Description:**\\nThere are at least two dash-like characters in the \"Special character\" dialog. They should have a tooltip describing them, otherwise it won\\'t be obvious to most users which character is to be used in which situation. Actually, why not add a descriptive tooltip to all special characters?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429751936, 'spacePHID': None, 'dateCreated': 1406103960, 'dateModified': 1429769485, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68425', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf14] ooui-dialog-* messages not imported', 'description': {'raw': 'no Message for error\\n\\n\"Not logged in\" message has no Message text, shows placeholder id, see screen shot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14425}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406129852, 'spacePHID': None, 'dateCreated': 1405964460, 'dateModified': 1443278066, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68327', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting more than one paragraph is painfully slow in large documents', 'description': {'raw': 'Pasting more than one paragraph triggers a full document re-render. This is clearly seen in the standalone client where all the paragraphs flash grey on re-render.\\n\\nOn en:Cat in Firefox it takes ~2s.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406081202, 'spacePHID': None, 'dateCreated': 1405887180, 'dateModified': 1443278066, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68301', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Investigate parsing/rendering/behavior of \"{{MW 1.23}}\" on mediawiki.org [mini-tracking]', 'description': {'raw': '(This bug notes issues with both Parsoid and VisualEditor. I think all of this is caused by the terrible mistake that is bug 529 / bug 12974. I\\'ll leave it for you to figure out this mess. :) )\\n\\n----\\n\\nOn mediawiki.org, there is a family on fancy templates like [[mw:Template:MW 1.23]] that generate a right-floated MediaWiki version number in a frame.\\n\\nThese templates generate a wikitext table (starting with \\'{|\\'), which means that due to bug 529 / bug 12974 a newline is prepended before it. This behavior is incredibly annoying in practice, but it seems that we\\'re very much wedded to it because it made Parsoid people\\'s lives easier.\\n\\n----\\n\\nHowever, Parsoid rendering of this particular template is inconsistent with PHP. On [[mw:Manual:Skinning#Localisation_messages]], PHP generates an empty paragraph before the table, while Parsoid doesn\\'t and produces an about-grouped pair of <span>\\\\n</span><table>…</table> (the span tag only contains the prepended newline).\\n\\nThis rendering, that looks good in Parsoid/VisualEditor, therefore looks like crap in PHP parser.\\n\\nNote that the <span> is not nested in a <p> or any other block-level element, it just sits there right in the <body>. (It is not visible since, as I mentioned, it just contains some whitespace.)\\n\\n----\\n\\nMore problems appear when you try to edit text with this template in VisualEditor.\\n\\nFor example, testing on [[mw:Manual:Skinning#Localisation_messages]]:\\n\\n* Place cursor before/after one of the templates.\\n* Press \\'Right\\'/\\'Left\\' keyboard key twice.\\n** First press selects the template, as expected.\\n** Second press scrolls the page all the way up.\\n\\n* Try inserting the \"MW 1.23\" template on an empty line.\\n** Observe that the blue highlights are different than for the\\n   templates already present on the page – there is both the table, as\\n   well as a single \"space\" (?) in text flow. Observe that the context\\n   menu is placed weirdly in the middle of the page.\\n** Place cursor after the \"space\" and try typing. Weird things happen,\\n   sometimes I get an exception \"Uncaught Error: Unbalanced set of\\n   replace operations found\", sometimes my input is duplicated or I\\n   get snowmen and pawns.\\n** Try deleting the template in any way. It is deleted, but the page\\n   is scrolled all the way up.\\n\\n* Edit the two paragraphs right after the \"Localisation messages\"\\n  heading (add a letter somewhere in the middle or something).\\n* Try saving the page.\\n** Observe that multiple newline-related changes appear to have been\\n   made. Strangely, there are actually no changes, but the *before*\\n   half of the comparison has some newlines removed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412889795, 'spacePHID': None, 'dateCreated': 1405871700, 'dateModified': 1590706405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68297', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The show/hide text a collapsed navbox disappear afted have edited', 'description': {'raw': '**Author:** `gabrasca2`\\n\\n**Description:**\\nThe text show/hide in the right of the navbox disappear after have edited a page where there is a navbox collapsed and the navbox appears uncollapsed, until the page is refreshed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415210380, 'spacePHID': None, 'dateCreated': 1405797900, 'dateModified': 1417571682, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68279', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: In android, while trying to apply a link on a selected text, strips off the first letter of the text in the link inspector', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with Mobile Ve in android with Chrome browser\\n2.Select a text such as \"Text\"\\n3.Click on link inspector tool\\n\\nObserved Result:\\nObserve that in the link inspector, the \"text\" is appearing as \"ext\"'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1405725780, 'dateModified': 1592583998, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68244', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After changing the size of an image and applying changes, the image size changes but does not get updated in the Media dialog until saving the page', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to the Advanced Settings and change the image size\\n4.Click on Apply changes\\n5.Reopen the Advanced Settings panel for that image again\\n\\n\\nObserved Result:\\nObserve that, the size values of the image are still showing the previous ones , though the image actually got resized\\nIf I save the page and reopen it and then check the Advanced Settings dialog , I see the updated values then.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406161762, 'spacePHID': None, 'dateCreated': 1405722900, 'dateModified': 1443278068, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68242', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Use existing reference dialog gets squished upon resizing the window down and does not retain back its UI upon making window size normal', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Go to Cite>Basic\\n3.Click on \"Use an existing reference\" button\\n4.Now resize down the window \\n\\nObserved Result:\\nThe \"Use Existing Reference\" dialog suddenly gets squished in and if I drag the window to its original size it stays like that.\\nNow if you click on \"Go Back\" button the basic reference dialog also appears that way\\n\\nSee the screenshot attached\\n\\nBrowser: Chrome and Firefox\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14226}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406081224, 'spacePHID': None, 'dateCreated': 1405712280, 'dateModified': 1443278068, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68232', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The size of References List dialog is appearing a bit small in Firefox making the text field almost overlap with the edge of the dialog', 'description': {'raw': 'Screenshot\\n\\nThe references list dialog is appearing a bit smaller in Firefox which also makes the text field for group name overlap with the border of the dialog.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70601\\n\\n**Attached**: {F14204}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406162665, 'spacePHID': None, 'dateCreated': 1405709100, 'dateModified': 1443278069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68226', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The \"Go back\" button in use existing reference dialog in mobile takes to Basic Reference dialog', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open a page with mobile VE\\n2.Select the option \"USe existing reference\" from Cite menu options\\n3.Click on the \"Go Back\" button on use existing reference\\n4.It takes you to the basic reference dialog\\n\\n\\nIssue 1: Type something in the dialog pawn appears\\nIssue 2: Click on \"Insert Reference\" nothing happens\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406064769, 'spacePHID': None, 'dateCreated': 1405638780, 'dateModified': 1443278072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68201', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression pre-wmf15] The highlights of the nodes are appearing over the toolbar menu', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Select any node such as reference in mobile VE using iOS or desktop safari\\n\\n2.Now open the cite menu option from the toolbar\\n\\nObserved Result:\\nObserve that, the highlight of the reference node is appearing over the cite menu option.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14137}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406747398, 'spacePHID': None, 'dateCreated': 1405637040, 'dateModified': 1443278072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68198', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: In iOS, while opening the link inspector for the second time, the inspector gets zoomed making the inspector title overlapped with the browser tab', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Mobile VE\\n2.Place the cursor in the CE\\n3.Open Link inspector and insert a link\\n4.Click on the link inspector icon again.\\n\\nObserved Result:\\nThe inspector appears a bit zoomed , which makes the title \"Link\" and the button \"Done\" on the top overlapped with the browser tabs\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14134}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406751119, 'spacePHID': None, 'dateCreated': 1405635840, 'dateModified': 1443278073, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68197', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The Remove button for the link inspector in mobile is not styled as Red', 'description': {'raw': 'Screenshot\\n\\nSee the screenshot attached\\nThe \"Remove\" button in the link inspector is not styled as Red\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14123}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406748754, 'spacePHID': None, 'dateCreated': 1405634400, 'dateModified': 1443278074, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68194', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Use new labs project (extdist.wmflabs.org) for ExtensionDistributor', 'description': {'raw': \"I've set up a new labs project for ExtensionDistributor to serve tarballs instead of using github. Example tarball: http://extdist.wmflabs.org/?version=REL1_23&ext=VisualEditor\\n\\nThis will provide better privacy for users, and also fix a few bugs like submodule support (bug 44022).\\n\\nYuvi is helping puppetize the setup.\\n\\nI want to temporarily enable ExtensionDistributor on testwiki, point it labs, make sure there are no issues, and then turn it on on mediawiki.org.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406830792, 'spacePHID': None, 'dateCreated': 1405545060, 'dateModified': 1638508956, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68122', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:[Regression pre-wmf14] While switching to Edit source mode from the tab in toolbar , selecting \"Discard Changes\" redirects to the Edit source mode of the main page', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Edit the page\\n3.Now click on the \"Edit Source\" tab\\n4.Click on the option \"Discard Changes\"\\n\\nObserved Result:\\nIt redirects to the edit source mode of the main page .\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14497}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405964265, 'spacePHID': None, 'dateCreated': 1405544880, 'dateModified': 1443278078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68121', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Re-use an existing reference shouldn't require a reference list to be or have been on the page to work\", 'description': {'raw': 'Script error for each citation\\n\\nTest Environment-test2\\nSteps to Reproduce-\\n\\nScenario#1-\\n1> Select the ” Cite “ drop down and add a Journal, News, Book,  one of each citations.\\n2> Now click on “Insert” and select “Media”. Click on any picture returned in the dialog(do not enter any search term)\\n3> In the Media Settings dialog click on “Insert” again and select “Media” from the Caption toolbar. Click on any picture returned in the dialog.\\n4> Now close all the dialogs. \\n5> Repeat again steps #2,3 and 4.\\n6>In the main VE window  click on “Cite”  and select “Basic”. Reference dialog opens.\\n5> In the Reference dialog select “Use an existing reference”.\\n6> Script Error is shown as existing reference.\\n\\nScenario#2-\\n1> Go to the Media Settings dialog. \\n2> While General Settings is highlighted, select the ” Cite “ drop down and add a Journal, News, Book,  one of each citations to the Caption pane.\\n3> Now click on “Insert “dropdown and select “Media”.\\n4>Click on any picture in the media search dialog. Media Settings dialog pops. Close this dialog.\\n5> Repeat steps 3 and 4 again.\\n5> Notice that the previously opened Media Settings dialog is still open with the citations in the Caption pane.\\n6> Click on “Cite” again and select “Basic”. Reference dialog opens.\\n7> In the Reference dialog select “Use an existing reference”.\\n8> Script Error is shown as existing reference.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14429}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406770961, 'spacePHID': None, 'dateCreated': 1405466460, 'dateModified': 1443278078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68079', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Undoing the edit from toolbar does not disable the \"Apply Changes\" button inside Media Settings dialog', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the media settings dialog for an image\\n2.Edit something in the caption field to enable the \"Apply Changes\" button\\n3.Undo the edit from the toolbar\\n\\nObserved Result:\\nThe \"Apply Changes\" button still remains enabled\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409865352, 'spacePHID': None, 'dateCreated': 1405450800, 'dateModified': 1443278081, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68058', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Gerrit: Use GitHub redirects instead of duplicate mirrors', 'description': {'raw': 'For repositories that we\\'re (also) mirroring at a custom name, they are currently being mirrored twice.\\n\\nFor example:\\n\\n* https://github.com/wikimedia/VisualEditor\\n  https://github.com/wikimedia/VisualEditor-VisualEditor\\n\\n\\n* https://github.com/wikimedia/oojs\\n  https://github.com/wikimedia/oojs-core\\n\\n* https://github.com/wikimedia/puppet-kafka\\n  https://github.com/wikimedia/operations-puppet-kafka\\n\\nThis is confusing and also decentralises things like Watching and Fork tracking. But, more importantly, it also makes our Star rating and Pull requests harder to maintain.\\n\\n\\nI don\\'t know whether we intentionally do both, or whether it was just easier to implement this way.\\n\\nI\\'d recommend we get rid of the full names where we want to publish the repo under a different name.\\n\\nIf it was a conscious choice to do this I\\'m curious why. The only reason I can think of is to make them easier to find on GitHub, which is hardly a big issue since they have excellent search for repo names right on https://github.com/wikimedia.\\n\\nAnother reason might be being able to automatically generate a GitHub address for a Git repo, but I\\'m not sure that\\'s a big issue.\\n\\nAlso note that GitHub supports renaming of repositories and automatically keeps redirects[1]. So we can remove the \"unwanted\" names from Gerrit replication config and have our github.com/wikimedia admins delete the repos and create a redirect (by renaming the good one to the bad one and then renaming it back).\\n\\nAs an example I\\'ve created a redirect from https://github.com/wikimedia/mediawiki to https://github.com/wikimedia/mediawiki-core. Eventually this should be done the other way around but this was easier to set up since Gerrit replag currently did not push to /mediawiki yet (unlike oojs and VisualEditor).\\n\\n\\n[1] https://github.com/blog/1508-repository-redirects-are-here\\n[2] https://help.github.com/articles/renaming-a-repository\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1416840790, 'spacePHID': None, 'dateCreated': 1405448880, 'dateModified': 1424369858, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68054', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Scroll bar is appearing inside the language inspector', 'description': {'raw': 'Screenshot\\n\\nOpen a language inspector, a scroll bar is appearing inside the inspector\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14372}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405968048, 'spacePHID': None, 'dateCreated': 1405448700, 'dateModified': 1443278082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68053', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Text cannot be pasted into link inspector search field from mobile browser', 'description': {'raw': 'Tap, or tap and hold on text input field in tablet VE, expected behavior, native iOS copy/paste flag should be shown, but it us not.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434487876, 'spacePHID': None, 'dateCreated': 1405412580, 'dateModified': 1434492405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68018', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf14] In the media dialog, switch to default size button is not changing the size values to default after setting a custom size', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Insert an image in a page\\n2.Change the size of the image by going to Custom tab\\n3.Click on \"Apply Changes\"\\n4.Now again open the media settings dialog and switch to default tab\\n\\n\\nObserved Result:\\nPreviously as soon as user switched to default tab, it used to set the text fields to default size, but now its keeping the custom size values.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409864430, 'spacePHID': None, 'dateCreated': 1405363500, 'dateModified': 1443278085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf14] The context menu for already added category is appearing as blank in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add some categories\\n3.Click on the newly added category to bring up the context menu for the category\\n\\nObserved Result:\\n\\nThe context menu for the newly added category is appearing as blank with no option to specify \"sort this page as if it is called\" field value.\\n\\nSee the screeshot attached\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14597}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405123633, 'spacePHID': None, 'dateCreated': 1405110420, 'dateModified': 1443278085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67885', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Disable Media Viewer by default on the English Wikipedia', 'description': {'raw': '[[https://en.wikipedia.org/wiki/Wikipedia:Media_Viewer/June_2014_RfC|Wikipedia:Media Viewer/June 2014 RfC]]\\n\\nThe consensus on the English Wikipedia is to disable Media Viewer by default.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/wiki/Wikipedia:Media_Viewer/June_2014_RfC\\n**See Also**:\\n* {T71080}\\n* {T71292}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405037582, 'spacePHID': None, 'dateCreated': 1405031700, 'dateModified': 1668243339, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67826', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After selecting a focusable node backwards by cursoring, pressing up/down throws an exception', 'description': {'raw': \"Steps to reproduce:\\n\\n1.Open a page with VE which has a reference note in it\\n2.Now place your cursor after the reference note\\n3.Press backspace to select the reference note\\n4.Now press down key to go to the next line\\n\\nObserved Result:\\nThe cursor does not go to the next line and an error appears in the console:\\n\\nUncaught NotFoundError: Failed to execute 'selectNode' on 'Range': The node provided is null. \\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405444908, 'spacePHID': None, 'dateCreated': 1404944220, 'dateModified': 1443278089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf13] TypeError: Cannot read property 'context' of undefined appears when you try to insert another image that appears on the same index as the previous search, right after you inserted one\", 'description': {'raw': \"Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Media\\n3.Enter a search term\\n4.Select the first image that appears on the search result\\n4.Click on Change image immediately\\n5.Enter a different search term\\n6.Now try to select the first image on of the new search results \\n\\n\\nObserved Result:\\nIt throws an error:Uncaught TypeError: Cannot read property 'context' of undefined \\n\\nand cannot select that image\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406757740, 'spacePHID': None, 'dateCreated': 1404935520, 'dateModified': 1443278089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67749', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Crossing out the media settings dialog after changing the image size, retains those changes', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE which has image inside it\\n2.Open the media settings dialog for the image\\n3.Edit the values for the image size\\n4.Without saving this change just close the Media Settings dialog\\n5.Reopen the media settings dialog again and check the image size values\\n\\nObserved Result:\\nIt shows the changed value even though you have not saved it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67684'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405550777, 'spacePHID': None, 'dateCreated': 1404849360, 'dateModified': 1443278091, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67687', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf12] Entering a custom size value in the Advanced Settings dialog for an image does not enable \"Apply Changes\" button', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE which has an image inside it\\n2.Open the advanced settings dialog for that image \\n3.Type something in the Custom fields \\n\\nObserved Result:\\nThe Apply changes button does not get enabled upon changing the size value, it should change the tab to custom and enable the button\\n\\nEnvironment:Betalabs and test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67687'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405550833, 'spacePHID': None, 'dateCreated': 1404848100, 'dateModified': 1443278091, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67684', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: In iOS Safari, the context menu of previously selected link is appearing upon placing the cursor in a different position in the document', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with mobile VE with iOS Safari\\n2.Tap the cursor on a link to bring up the context menu for it\\n3.Now tap at the end of some other text to place the cursor there\\n\\nObserved Result:\\nThe context menu for the previous link is appearing on top of the article.\\n\\n\\nEnvironment : Betalabs and test2\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67433\\n\\n**Attached**: {F14661}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406747354, 'spacePHID': None, 'dateCreated': 1404773940, 'dateModified': 1443278091, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67637', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Make full Size\" is not enabling \"Apply changes\" button therefore cannot make any image fullsize', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to the Advanced Settings of an image\\n4.Click on \"Make full size\"\\n\\n\\nObserved Result:\\nThe \"Apply Changes\" button is still disabled , cannot make any image full size\\n\\nEnvironment:test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404865232, 'spacePHID': None, 'dateCreated': 1404764520, 'dateModified': 1443278092, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67624', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable Visual Editor by default on pt.Wikiversity', 'description': {'raw': 'Ni!\\n\\nSince early this year we at pt.wikiversity have used the Visual Editor as an opt-in \"beta feature\".\\n\\nAfter this experimental phase, we have agreed that we want the Visual Editor to be enabled as default editor for everyone on pt.wikiversity, including unregistered users.\\n\\nhttps://pt.wikiversity.org/wiki/Wikiversidade:Esplanada#Habilitar_editor_visual_por_padr.C3.A3o\\n\\nWe\\'d really appreciate if this could happen before the end of the July, since classes in Brazil start on early August.\\n\\nCheers,\\nSolstag\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wr7prgh3p37xrvbdr6w5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404775431, 'spacePHID': None, 'dateCreated': 1404719340, 'dateModified': 1404775551, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67582', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Annotations are not preserved between edits', 'description': {'raw': \"**Author:** `drobbins`\\n\\n**Description:**\\nCurrently, any edits to a page will create a new page with no annotations, which makes this extension very difficult to use. You must look at the page history, and look at each revision for potential annotations that people may have added, and there is no icon or other indication that a revision actually *has* annotations. So they are likely to be lost or ignored.\\n\\nIdeally, annotations would be preserved through wiki edits and apply to newer revisions of pages. This would likely require updates to the editor.\\n\\nI realize that this may be technically challenging to implement. However, the preservations of annotations across edits does seem to be essential for really ensuring that this extension is useful (In fact, I wouldn't consider this annotation feature actually fully implemented until this is supported.)\\n\\nThe true ideal implementation would be to display annotations in the editor, and like a true word processor, track changes to the underlying text to ensure that the annotation still existed even if the underlying text was modified in some way, as is how annotations work in word processors. This would have the added benefit of allowing editors to view annotations in real-time as they are editing a document, which would be extremely handy as many annotations deal with changes to the document that need to be made (or at least, should be addressed in some way during an edit cycle.\\n\\nProposed design:\\n\\n[ editor window top ]\\n\\n\\n[ Highlighted yellow: Editing this line in the editor.... ]\\n\\n\\n[ editor window bottom ]\\n\\n[ Annotation: Display annotation(s) related to cursor position here. ]\\n[ Button: add comment ] <-- editor would use this to add comment to existing annotation, related to any edits.\\n\\nI don't know if that is helpful for conveying how annotations could work in the editor, or not. I think this should be added to the default editor, and VisualEditor can add its own support. I don't think this feature should be VE-only.\\n\\nA possible work-around to make things a bit more bearable in the mean-time would be to add some kind of icon in the page history to indicate revisions that have annotations, so that the maintainer of the page can go through the page's history and look for annotations from people.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xvs3y6hf6yrfn6sxrk5d', 'dateClosed': 1521636419, 'spacePHID': None, 'dateCreated': 1404696600, 'dateModified': 1521636419, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67576', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: On wikis where anons can't create pages, you aren't told this until you try and save\", 'description': {'raw': \"Admittedly there are no links to take you to edit the page, but navigating to New_page?action=edit gives you and error, whereas New_page?veaction=edit let's you start editing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406074701, 'spacePHID': None, 'dateCreated': 1404562740, 'dateModified': 1443278095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67550', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Produce/preserve the metadata about additional ResourceLoader modules required by extension tags', 'description': {'raw': 'Parsoid must produce/preserve the metadata about additional ResourceLoader modules required by extension tags. (I\\'ve heard some gossip that it falls back to PHP parser to do this, so this should be easy to do.)\\n\\nFor example, in PHP parser, \"<syntaxhighlight lang=php>$foo</syntaxhighlight>\" will add up to two modules to ParserOutput\\'s $mModuleStyles:\\n* \\'ext.geshi.language.php\\' (there is such a module for every supported language)\\n* \\'ext.geshi.local\\' (if $wgUseSiteCss is true)\\n\\nThis information must somehow be provided by the API used by VisualEditor.\\n\\nThe minimum set of things that have to be provided is the ones provided by OutputPage::addParserOutputContent() in PHP, that is modules, module styles, module scripts, module messages and JS config vars. (These are available via the action=parse&prop=modules API in core.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1632170095, 'spacePHID': None, 'dateCreated': 1404491460, 'dateModified': 1657243478, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67540', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression wmf12] In iOS Safari, cannot open any page as it throws error \"Error,can\\'t load section\"', 'description': {'raw': 'Screenshot\\n\\nTry to open any page with mobile VE in iOS Safari on Betalabs, the page does not load in VE and it shows an error at the bottom:\\n\"Error,can\\'t load section\"\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14353}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404755143, 'spacePHID': None, 'dateCreated': 1404429960, 'dateModified': 1443278095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67508', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: In iOS Safari, the link suggestions are appearing on CE when you close the link inspector keeping the keyboard open', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Tap on a link\\n3.When the context menu for that link appears tap on that\\n4.Try to edit the link target name in the search box for link inspector\\n5.No Link target page suggestions will appear inside the link inspector\\n6.Close the link inspector\\n7.Close the keyboard that is still appearing on CE\\n\\nObserved Result:\\nThe link suggestions are appearing on CE now\\nSee the screenshot attached\\n\\n\\nThis issue started happening after merging the new code for context menu on Mobile VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57177\\n\\n**Attached**: {F14100}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404331543, 'spacePHID': None, 'dateCreated': 1404258420, 'dateModified': 1443278101, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67399', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile:In iOS Safari, the toolbar for Mobile VE also scrolls down when you try to scroll down the page having a node selected', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Do not place your cursor anywhere on CE but try to select a node \\n3.Scroll down the page\\n\\nObserved Result:\\nThe toolbar also gets repositioned down while scrolling down the page.\\n\\nIt might get resolved with :https://bugzilla.wikimedia.org/show_bug.cgi?id=57177\\n\\nStill I am filing it as a separate issue.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57177\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60110\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67433\\n\\n**Attached**: {F14695}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406746351, 'spacePHID': None, 'dateCreated': 1404250320, 'dateModified': 1443278101, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67390', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template dialog wrongly prefixes suggestions from User namespace with colon', 'description': {'raw': 'Steps:\\n\\n1. Create page with VE\\n2. Insert New Template\\n3. Enter text that is the prefix of one or more pages in the User namespace with template data\\n\\nExpected result:\\n\\nSuggestions show up as:\\n User:Foo/Template:Example\\n User:Foo/Template:Unsigned\\n User:Foo/Template:Unsigned2\\n\\nActual result:\\n\\nSuggestions show up as\\n :User:Foo/Template:Example\\n :User:Foo/Template:Unsigned\\n :User:Foo/Template:Unsigned2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405465885, 'spacePHID': None, 'dateCreated': 1404243060, 'dateModified': 1443278105, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67386', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Maximum execution time\" error in JavaScriptMinifier while minifying QUnit test modules', 'description': {'raw': 'It might possible to make this less likely by grouping them into smaller requests.\\n\\nThe request is:\\n\\n---\\nhttp://127.0.0.1:8080/w/load.php?debug=false&lang=en&modules=Base64.js%7Ceasy-deflate.core%2Cdeflate%7Cext.eventLogging%2Cmantle%7Cext.eventLogging.tests%7Cext.flow.new.handlebars.tests%7Cext.flow.new.tests%7Cext.gettingstarted.user%7Cext.gettingstarted.user.tests%7Cext.guidedTour.lib%2Cstyles%7Cext.guidedTour.lib.internal%2Ctests%7Cext.mantle.handlebars%2Ctemplates%7Cext.templateData.test%7Cext.templateDataGenerator.core%7Cext.visualEditor.base%2Ccore%2Clanguage%2Cmediawiki%2Cmwalienextension%2Cmwcore%2Cmwformatting%2Cmwgallery%2Cmwimage%2Cmwlink%2Cmwmeta%2Cmwreference%2Cmwtransclusion%2Cstandalone%2Ctest%2CviewPageTarget%7Cext.visualEditor.core.desktop%7Cext.visualEditor.mwimage.core%7Cext.visualEditor.viewPageTarget.init%7Cjquery.accessKeyLabel%2CautoEllipsis%2CbyteLength%2CbyteLimit%2CcheckboxShiftClick%2Cclient%2Ccookie%2CgetAttrs%2ChighlightText%2Ci18n%2Cjson%2CmakeCollapsible%2Cmw-jump%2CmwExtension%2Cplaceholder%2Cqunit%2CtabIndex%2Cthrottle-debounce%2CvisibleText%7Cjquery.qunit.completenessTest%7Cjquery.uls.data%7Cmediawiki.Title%2CUri%2Capi%2Ccldr%2Cfeedback%2CjqueryMsg%2Clanguage%2Cnotify%2Cuser%2Cutil%7Cmediawiki.api.edit%7Cmediawiki.language.init%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.guiders%2Cpluralruleparser%7Cmediawiki.page.ready%2Cstartup%7Cmediawiki.skinning.content.parsoid%7Cmediawiki.special.javaScriptTest%7Cmediawiki.ui.button%7Coojs%2Coojs-ui%2Crangy%7Cskins.vector.js%7Ctest.mediawiki.qunit.testrunner%7Ctest.sinonjs%7Cunicodejs.wordbreak&skin=vector&version=20140701T185441Z&*\\n\\n---\\n\\nThe error response is:\\n\\n\\nFatal error: Maximum execution time of 30 seconds exceeded in /vagrant/mediawiki/includes/libs/JavaScriptMinifier.php on line 428\\n\\nCall Stack:\\n    0.0021     656184   1. {main}() /vagrant/mediawiki/load.php:0\\n    0.2177   10838400   2. ResourceLoader->respond() /vagrant/mediawiki/load.php:43\\n    0.4901   11686616   3. ResourceLoader->makeModuleResponse() /vagrant/mediawiki/includes/resourceloader/ResourceLoader.php:543\\n    2.1315   19034048   4. ResourceLoader->filter() /vagrant/mediawiki/includes/resourceloader/ResourceLoader.php:923\\n    2.1480   19272904   5. JavaScriptMinifier::minify() /vagrant/mediawiki/includes/resourceloader/ResourceLoader.php:181\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1448401815, 'spacePHID': None, 'dateCreated': 1404241500, 'dateModified': 1449449435, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67383', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Converting a numbered external link to a regular one from the link inspector drops the annotations', 'description': {'raw': \"Converting a MWNumberedExternalLinkNode to MWExternalLinkAnnotation from the UI (link inspector) loses annotations on the node, even though there is code in place that aims handle this.\\n\\nSee the behavior of the 'convert' variable in ve.ui.MWLinkNodeInspector.prototype.getTeardownProcess.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406076653, 'spacePHID': None, 'dateCreated': 1404236940, 'dateModified': 1441911911, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67377', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  The Help menu does not scroll on small screens while using Monobook', 'description': {'raw': \"Steps to reproduce:\\n\\n1.  Make your browser window short (<400 pixels?).\\n\\n2.  Open a page using the Monobook skin, e.g., https://en.wikipedia.org/wiki/Nicholas_Rigby?veaction=edit&useskin=monobook.\\n\\n3.  Click the (?) button to open the Help menu.\\n\\n4.  Because of the short screen, the entire menu does not fit on the screen at once.  Try to scroll down to read the last line on the Help menu.\\n\\n\\nThe Help menu is not scrolling, so you can't see anything that doesn't fit on your screen.  This is not a problem in Vector.  I have confirmed this in both Safari 6.1.4 and Firefox 30.\\n\\nOriginal report:  https://ru.wikipedia.org/w/index.php?diff=63851178 from Sunpriat\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413330573, 'spacePHID': None, 'dateCreated': 1404228840, 'dateModified': 1417571690, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67370', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: For long drop down menus the options are not at all accessible when the screen is set to landscape in iOS device', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Rotate the screen of your iOS device to landscape\\n2.Open a page with mobile VE\\n3.Tap on a drop down menu which has lot of options under it like for now we have \"Reference\" menu\\n4.Open that menu\\n5.Try to select the options from the bottom of the menu such as \"Use an existing reference\" or \"Journal\"\\n\\nObserved Result:\\nCannot select any of those options since the keyboard is always open and overlapping with the menu,and scrolling down menu again drags the screen back to the top\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14572}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1535711851, 'spacePHID': None, 'dateCreated': 1404174840, 'dateModified': 1535711852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67340', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: On a redirected page, VE URL retains original searched title instead of redirect title', 'description': {'raw': \"If I go to a page that has been redirected, the URL retains the original title instead of the redirected title. So if I enter VE and then refresh, I'm taken to the editing the original page instead of the redirect page.\\n\\nFor example, go here: https://en.wikipedia.org/wiki/Zedonk, then click VE, then refresh the page. \\n\\nURL should be changed to: https://en.wikipedia.org/wiki/Zebroid?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-flenunkasbjk4topxvaj', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408570153, 'spacePHID': None, 'dateCreated': 1404163440, 'dateModified': 1417571938, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67330', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Template dialog doesn't display very long template names gracefully\", 'description': {'raw': 'See https://commons.wikimedia.org/wiki/File:VE_bug-Template_name_overlaps_remove_icon_in_advanced_dialog.png\\n\\nIf the name of the template is very long, then it overlaps with the trashcan icon for removing it.\\n\\nThis may or may not remain a consideration with the upcoming change to labels (instead of icons) and the redesign of all the boxes.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412590143, 'spacePHID': None, 'dateCreated': 1404014220, 'dateModified': 1443278109, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67267', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: resizing audio file causes it to resize 0px dialogs do not report size.', 'description': {'raw': 'resize and size reporting issue with audio files\\n\\nissue is highlighed on https://en.wikipedia.org/wiki/Iceberg\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14397}'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701963934, 'spacePHID': None, 'dateCreated': 1404012180, 'dateModified': 1701963934, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67265', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Floating toolbar is mis-aligned in non-HD vector css', 'description': {'raw': 'Detached toolbar when floating in non-HD Vector\\n\\nWorks fine when normally placed, but is out by ~ 30px when floating.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14365}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405555416, 'spacePHID': None, 'dateCreated': 1403981160, 'dateModified': 1443278110, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67256', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Merge the inserting and editing media dialogs', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404328355, 'spacePHID': None, 'dateCreated': 1403824980, 'dateModified': 1443278113, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67170', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Can't tab from Caption to Alt text fields in image media dialog box, in Safari only\", 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Open a page containing an image in Safari.\\n\\n2.  Open an image in the media dialog box.  The cursor begins in the Caption field (of General settings).\\n\\n3.  Press tab (to get to the next field).\\n\\n\\nResults:\\n\\nNothing happens.  The cursor is stuck in the Caption field.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67156'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404954523, 'spacePHID': None, 'dateCreated': 1403810760, 'dateModified': 1443278115, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67162', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs UI: Do not let me tab outside a dialog box in Chrome/Safari', 'description': {'raw': \"This is related to {T69153}, but specific to Chrome/Safari:\\n\\nWhatever the dialog box, once you've tabbed through whatever links and buttons are inside that dialog (and on the tab list, which isn't always all of them), then pressing tab takes you outside the dialog box to these items:\\n\\n1) the browser's URL bar\\n2) the main Wikipedia search box \\n3) the Cancel button (on VisualEditor's toolbar)\\n4) the Save button (on VisualEditor's toolbar)\\n5) the top of the article\\n6) the slug at the top of the article, where it gets stuck forever.\\n\\nand never lets you get back to the dialog box.  This means that if you press tab one time more than you meant to, you cannot use or close the dialog box without taking your hands off the keyboard.\\n\\n**See Also**: {T69162}\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1442847165, 'spacePHID': None, 'dateCreated': 1403808420, 'dateModified': 1448073038, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67156', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: When adding a link to a reference without dismissing the link inspector, the link isn't applied (race condition)\", 'description': {'raw': \"When adding a link inside a reference in VisualEditor, if one clicks 'apply' without first clicking outside the link inspector, the link is not added.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60837\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1420070837, 'spacePHID': None, 'dateCreated': 1403637660, 'dateModified': 1438734920, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67049', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar is sometimes misaligned and ugly in Safari; corrects itself after interaction', 'description': {'raw': \"Misaligned toolbar\\n\\nThe bottom of the bar is too high, the Cancel and Save buttons are at different heights.  \\n\\nHowever, I can't reproduce it consistently, and changing the font size caused everything to realign correctly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14345}\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1508930094, 'spacePHID': None, 'dateCreated': 1403548380, 'dateModified': 1509037818, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66988', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Turn structure dropdown into a \"split button\" with \"make bulleted list\" the primary action', 'description': {'raw': 'A split button consists of a \"command button\" and a \"dropdown button\". These are two separate clickable entities. The command button behaves like a regular toolbar button, but it displays the most recent command the user invoked from the dropdown menu.\\n\\nIt was suggested by User:Theflyer to convert VE\\'s list toolbar button into a split button:\\n\\n\\n> When selecting an item from the menu, like lists, I think the button should be sticky and perform the action that is currently shown rather than requiring two clicks to take an action. The example that brought this to my attention is when creating bullets. The default icon shows a traditional bullet so when I click on that, I expect it to just start a bullet. However, the action I get is to open the menu where I then have to select which bullet list option I would prefer. I think there should be a way to act on the existing icon (and it should change to whatever I had last selected) and also a way to pull down the list if I want to change to a different type of action. This is the way Microsoft Word works. There are two clickable hotspots. Thanks. Don Theflyer (talk) 15:55, 21 June 2014 (UTC)\\n\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1403417400, 'dateModified': 1643977421, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66940', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Use comma-separator interface message', 'description': {'raw': \"There are a few places where we use the string ', ' but in all of those cases we should really be using the comma-separator message. This requires backfilling comma-separator for standalone OOUI, since we also use commas in VE core and OOUI.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416427259, 'spacePHID': None, 'dateCreated': 1403310780, 'dateModified': 1417571675, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66894', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: mw.Title invocations for template titles should use template namespace as default namespace', 'description': {'raw': 'Right now we have things like mw.Title.newFromText( template ); , while really that should use something like mw.Title.newFromText( template, 10 ); or whatever. This is probably fine in practice, but theoretically matters is NS_MAIN and NS_TEMPLATE have different capitalization settings.\\n\\nWe also currently render the titles of {{foo}} (which points to Template:Foo, renders as Foo) and {{:foo}} (which points to Foo, also renders as Foo) the same, we should fix that.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404350702, 'spacePHID': None, 'dateCreated': 1403310360, 'dateModified': 1443278122, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66893', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: For large SVG images while trying to make it full size, it says \"Size values are invalid\"', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a svg image with large size \\n(I found this issue with this image: https://test2.wikipedia.org/wiki/File:MO-123.svg, which has full size of 2,543 × 2,160 pixels.\\nI tried with svg images of upto 2000 x 2000 pixels, but could not reproduce for them.)\\n\\n3.Go to Media Settings tab of this image and go to Advanced Settings\\n4.Click on Make full size (it wont try to make it full size which is another bug)\\n5.Now again click on Make full size\\n\\nObserved Result:\\nIt changes the size values to the full size of the images but it also says \"Size values are invalid\"\\n\\nPage:https://test2.wikipedia.org/wiki/19thjanFF?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403822272, 'spacePHID': None, 'dateCreated': 1403223600, 'dateModified': 1443278122, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66865', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"mediawiki.feedback: The 'submit feedback' form does not add the feedback page to the user's watchlist\", 'description': {'raw': \"Users who submit feedback through the in-VisualEditor form may not see any responses to their feedback because the page is not added to their watchlists, and there's no option to add it.\\n\\nThis feature comes from the `mediawiki.feedback` module in MediaWiki core.\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1586711588, 'spacePHID': None, 'dateCreated': 1403195700, 'dateModified': 1586711589, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66848', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Strip initial and trailing <br>s out of section headings', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?diff=612724427&oldid=612719708 added an invalid section heading:\\n\\n===== <br>\\nBuses =====\\n\\n\\nVisualEditor should always strip <br> out of section headings.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1437698410, 'spacePHID': None, 'dateCreated': 1403195100, 'dateModified': 1443094518, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66846', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Clear the 'search memory' after making a link\", 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Open a page in VisualEditor and make a link:  [[Foo]].  Easy, right?  Select text, press Command–K, and hit return twice.  You know the page exists under that name and that it doesn\\'t need to be piped, so you don\\'t even need to wait for the link inspector to get the information back from search.\\n\\n2.  Make another link the same way, but to a different page:  [[Bar]].\\n\\n3.  Why does VisualEditor offer to point that second link to [[Foo]]?\\n\\n\\nSteps to avoid this problem:\\n\\n1.  Open a page in VisualEditor and make a link:  [[Foo]].\\n\\n2.  Start to make another link to a different page ([[Bar]]), but after you\\'ve opened the link inspector, just stop and wait and wait and wait.\\n\\n3.  Ah, it\\'s finally figured out that [[Bar]] is not [[Foo]] and stopped trying to tell me that I want to link this to [[Foo]].  *Now* you can hit return twice and go on with your editing.\\n\\n\\nCan we make VisualEditor \"forget\" the search results in between attempts to link pages?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403144528, 'spacePHID': None, 'dateCreated': 1403144040, 'dateModified': 1443278125, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66821', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Backport mediawiki.skinning.content.parsoid to MW 1.23.x so VisualEditor master can run there', 'description': {'raw': 'In advance of rewriting the skins system, MediaWiki 1.24 introduces a mediawiki.skinning.content.parsoid module which is a dependency of VisualEditor master.\\n\\nMaking it so that downstream users can use newer versions of VisualEditor but not bleeding-edge MediaWiki would be a nice improvement for them, especially for LTS versions.\\n\\nHowever, we may want to have it settle down a bit more until now?\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'dateClosed': 1489977944, 'spacePHID': None, 'dateCreated': 1403122680, 'dateModified': 1489980005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66812', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor Mobile: Cursor moving handle (?) doesn't appear in Android\", 'description': {'raw': 'On mobile devices there\\'s the \"stick\" blinking cursor, and usually also another handle for moving the cursor around more conveniently. I\\'m not sure what is it called.\\n\\nI cannot see it in the mobile VE.\\n\\nI\\'m using ASUS Transformer with Android 4.2.1.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1403098320, 'dateModified': 1592583998, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66783', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: For the first time in each edit session in Nexus 7 (Android 4.4.2), Link Inspector gets auto-zoomed in, which looks like partial rendering of the UI', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Mobile VE\\n2.Select a text\\n3.Click on the link inspector icon from the toolbar\\n\\nObserved Result:\\nThe link inspector appears a bit zoomed, which at first glance made me feel like a failure in rendering the inspector.\\n\\nSee the screeshot attached\\n\\nDevice: Nexus 7(Android 4.4.2)\\nEnvironment:Production (en.wiki) and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13925}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'dateClosed': 1430340251, 'spacePHID': None, 'dateCreated': 1403051220, 'dateModified': 1430349779, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66759', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Tapping at the end of each link duplicates the preceding link text in Nexus 7 (Android 4.4.2)', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Tap at the end of a link\\n\\nObserved Result:\\nThe link gets copied at the position your cursor was on and it will keep continue doing that everytime you place your cursor at the end of extended link.\\n\\nSee the screenshot attached\\n\\nDevice: Nexus 7(Android 4.4.2)\\nEnvironment:Production (en.wiki) and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13918}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1604273725, 'spacePHID': None, 'dateCreated': 1403046960, 'dateModified': 1604273725, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66754', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Dump the change_tag table', 'description': {'raw': 'https://www.mediawiki.org/wiki/Manual:Change_tag_table , no private data involved and very useful for research (public editing patterns of all sorts and now visualeditor, mobile etc.).\\n\\nOn wikitech-l nobody could find a reason not to do it.\\nhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070255.html\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-jtxavgb3caz53o45csni', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-jtxavgb3caz53o45csni', 'dateClosed': 1443610896, 'spacePHID': None, 'dateCreated': 1402992420, 'dateModified': 1468524097, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66700', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Cursor jumps to the beginning of the article, irrespective of the position user trying to tap and put the cursor into', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with Mobile VE\\n2.Tap somewhere in the middle of the article\\n3.Insert some text\\n4.Close the keypad\\n5.Now again tap at the end of the text that you typed in\\n\\nObserved Result:\\nThe cursor moves to the beginning of the article, not where the user wanted to start his edit.\\n\\nDevice: iPad Mini\\niOS:7.1.1\\nEnvironment:Production and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409098401, 'spacePHID': None, 'dateCreated': 1402962060, 'dateModified': 1443278128, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66697', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression pre-wmf10] Dependency on jquery.uls.data not met for mobile so VE does not appear, spins forever', 'description': {'raw': 'As a logged in user at http://en.m.wikipedia.beta.wmflabs.org/\\\\\\n\\nWith beta setting enabled\\n\\nClick edit\\n\\nVE never appears, user sees just a spinner. \\n\\njs error is: Uncaught Error: Unknown dependency: jquery.uls.data\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-grftjc3ekkyjf6bwlsqi', 'dateClosed': 1423616745, 'spacePHID': None, 'dateCreated': 1402677300, 'dateModified': 1443278135, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66594', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing multiple deadkeys at the end of text expands selection to new line', 'description': {'raw': '**Author:** `oliver.buchtala`\\n\\n**Description:**\\nPut the cursor at the end of a text node and e.g. type ``.\\nAfter short delay the selection expands to the begin of the next node.\\n\\nThis happens for me under OSX Chrome 35 and Safari 7.0 for  VE@356f325ab21731e0aa5c83f90fb4fa037cc60cff.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1402673820, 'dateModified': 1442447661, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66592', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Gallery and Math inspector closes with an animation from right to left after clicking on \"<\" to close them', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the gallery inspector for an already added gallery or open the math inspector\\n3.Close the gallery inspector or math inspector after inserting math function\\n\\nObserved Result:\\nThe inspector closes with an animation coming from right to left\\n\\nEnvironment:Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60501'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405375906, 'spacePHID': None, 'dateCreated': 1402602720, 'dateModified': 1443278135, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66552', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspector of FocusNodes with embedded menu should not be embedded in some cases', 'description': {'raw': \"**Author:** `oliver.buchtala`\\n\\n**Description:**\\nCurrently, if the menu for a FocusNode gets embedded, this also happens for the Inspector. It would be better to let the Inspector itself decide.\\n\\nDetails:\\n\\nThis gets executed when the menu for a focus node is shown. 'this.embedded' is set according to the size of the focus node:\\n\\nhttps://github.com/wikimedia/VisualEditor/blob/356f325ab21731e0aa5c83f90fb4fa037cc60cff/modules/ve/ui/ve.ui.DesktopContext.js#L428-L435\\n\\nOTOH, when the inspector gets opened, 'this.embedded' is not recomputed:\\n\\nhttps://github.com/wikimedia/VisualEditor/blob/356f325ab21731e0aa5c83f90fb4fa037cc60cff/modules/ve/ui/ve.ui.DesktopContext.js#L420-L425\\n\\nThis has the consequence that the inspector is rendered over the focussed node.\\nIMO, at least the same embedded check should be done in the 'inspector' case.\\nAlso the tail should be enabled accordingly.\\n\\nTo leave the inspector implementation even more control I would suggest to add something like this to the Inspector interface:\\n\\n/**\\n * @returns {boolean}\\n */\\nInspector.prototype.isEmbedded = function() {};\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408731144, 'spacePHID': None, 'dateCreated': 1402596900, 'dateModified': 1443278136, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66542', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Creating a new page shows footer above the article', 'description': {'raw': 'Screencast of the behaviour.\\n\\nWhen I create a new article on Swedish Wikipedia with VE, the page footer is displayed above the cursor but below the title (se attached ogv).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13951}'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1516116364, 'spacePHID': None, 'dateCreated': 1402561200, 'dateModified': 1518742120, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66517', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: For an image inside sub-surfaces (e.g. caption of an image) the context menu appears aligned differently with the image shield', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Insert another image inside the caption of it.\\n4.Select the image and observe the position of the context menu that appears on top of the image\\n\\nObserved Result:\\nThe context menu's position is shifted few pixels to the right.\\nSee the screenshot to compare the position of it .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13897}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403995987, 'spacePHID': None, 'dateCreated': 1402515000, 'dateModified': 1443278138, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66494', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Design a good solution for image alignment \"none\" vs \"default\"', 'description': {'raw': 'There is a difference in behavior between explicitly stating \"none\" in the image wikitext and setting no alignment (which is usually default) This difference is especially complicated when we\\'re dealing with switching between block to inline, as inline images basic/frameless have no initial alignment (attrs.align = undefined) but if an alignment is chosen in basic/frameless they turn into blocks.\\n\\nThere is no real way to choose \"none\" alignment for inline blocks with our current GUI.\\n\\nYou can see the outcome and differences between default/no alignment to \\'none\\' and other alignments in each of the different image types in this table:\\nhttps://www.mediawiki.org/wiki/User:Mooeypoo/VE_ImageAlignment\\n\\n\\nI\\'ve tried to explore what other programs do in this case, but there doesn\\'t seem to be a good analogy for the difference between having \\'float\\' value and not having a float value while mixing block with inline. \\n\\nIn Microsoft Word 2013, images are inserted as block image with default alignment that is the direction of the text (left for ltr, right for rtl) *BUT* without text wrapping - so no float. You can change the image to inline (\"In Line with Text\") or to be wrapped (\"With Text Wrapping\") but the wrapping options are limited to how close the text is around the image; the user is then allowed to manually drag the image wherever they want ti to be (no actual \\'left\\' / \\'center\\' / \\'right\\')\\n\\nWe should find a working solution to let users decide between having \\'none\\' alignment explicitly while still having the default value available for both inline and block images.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1402440600, 'dateModified': 1643977422, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66460', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Quickly clicking on \"Apply Changes\" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Image\\n2.Open the Media Settings dialog\\n3.Now quickly double click on Apply changes Button\\n\\nObserved Result:\\nAn error appears in the console:\\n\\nUncaught TypeError: Cannot read property 'getSurface' of null\\nMedia Settings dialog for that image and all other images on that page becomes unresponsive.\\n\\nThis is happening in Betalabs and test , not on production(en.wiki)\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13637}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402527073, 'spacePHID': None, 'dateCreated': 1402341840, 'dateModified': 1443278142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66389', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters', 'description': {'raw': 'To reproduce:\\n1. Edit an article in Arabic.\\n2. Move the caret forward using the arrow keys.\\n\\nObserved: The Arabic letters next to which the caret moves are disconnected.\\n\\nExpected: Moving the caret must only move the caret. It must not change the appearance of the text.\\n\\nThis works well in Firefox, but broken in Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1420878426, 'spacePHID': None, 'dateCreated': 1402213980, 'dateModified': 1438734924, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66339', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf8] Cannot check the wrap option after changing a Thumbnail/Frame image to Frameless/Basic', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in test2\\n2.Insert an image\\n3.Change the image type to Frameless/Basic\\n4.Now observe the checkbox for wrap is now unchecked\\n5.Try to check the checkbox\\n\\nObserved Result:\\nIt does not check the checkbox , but all the alignment tabs becomes visible .\\n\\nThis is happening in test2 only,\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14010}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402102858, 'spacePHID': None, 'dateCreated': 1402096260, 'dateModified': 1443278142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66291', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: TypeError: node is null appearing while trying to open an image which was modified to Right-Basic-Border just after inserting it in the previous edit session', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Initially the image is Thumbnail-right\\n4.Now change the image type to Basic-Right-Border\\n5.Apply changes\\n6.Save the page\\n7.Reopen the image\\n8.Try to open the media settings dialog for the image\\n\\nObserved Result:\\nCaption field is missing in the Media Settings dialog and cannot close the media settings dialog for the image.\\n\\nThe following error appears in the console:\\n\\nTypeError: node is null appears in the console \\n\\nThis is happening in en.wiki and betalabs but not for some reason in test2\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13991}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402427523, 'spacePHID': None, 'dateCreated': 1402092600, 'dateModified': 1417572221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66286', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Default image alignment is not applied to parsoid-output figure elements', 'description': {'raw': 'If the alignment of an image is not explicitly set, Parsoid does not output an alignment class for the resultant figure element. This can lead to the image not being aligned/floated.\\n\\nWe need to modify content.parsoid.less to apply the default right-alignment styling to all images and then override this in cases where the alignment is explicitly set.\\n\\n--------------------------\\n**Version**: 1.24rc\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'dateClosed': 1446511243, 'spacePHID': None, 'dateCreated': 1402089360, 'dateModified': 1447443831, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66282', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: vesection not removed on save/cancel', 'description': {'raw': 'veaction is removed on save, but not vesection.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405001353, 'spacePHID': None, 'dateCreated': 1402021260, 'dateModified': 1443278142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66237', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Some images not displayed in the correct place ? due to floating', 'description': {'raw': 'Where the image was displayed before saving\\n\\nSteps to reproduce:\\n\\n1.  Open an article with a lot of images.  I started with https://en.wikipedia.org/w/index.php?title=Candy&oldid=611646505\\n\\n2.  Pick a right-aligned image and switch it to left-aligned.\\n\\n3.  Think, \"That\\'s weird:  it seems to have put it in the middle of a paragraph or something\".\\n\\n4.  Drag the image to a more appropriate location.\\n\\n5.  Think, \"Hey, I put it up there, so why is it all the way down there?\"\\n\\n\\nNB that the diff here:  https://en.wikipedia.org/w/index.php?title=Candy&diff=611749324&oldid=611748715\\nalso places the image in between the text and the invisible {{anchor}} template that ought to be attached to the text.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62850\\n\\n**Attached**: {F13861}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1402010880, 'dateModified': 1643398590, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66228', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Replace uses of push.apply with something safe', 'description': {'raw': 'Similar to how we have ve.batchSplice for splice.apply\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413487362, 'spacePHID': None, 'dateCreated': 1401993060, 'dateModified': 1417571690, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66206', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector should catch 400 errors from sending overly-long queries to the API', 'description': {'raw': 'This results in a quite bad outcome for the user, totally inexplicably. Instead we should just catch these errors and state them as invalid links (or have a different message?).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66135'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402090044, 'spacePHID': None, 'dateCreated': 1401914520, 'dateModified': 1443278146, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66139', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create distribution files for VE core', 'description': {'raw': 'OOJS(UI) has a build script which creates a dist folder with concatenated JS/CSS and copied images and i18n files. VE should have the same so that:\\n\\n* We avoid IE9 stylesheet limits (31 files, 4096 rules)\\n* We can create an RTL stylesheet using Janus.\\n* We can embed small images inside the stylesheets.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404356574, 'spacePHID': None, 'dateCreated': 1401887280, 'dateModified': 1443278148, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66117', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: For all drop down boxes, the first match with check mark and highlight, loses it highlight upon hovering over it and then moving mouse out of the object', 'description': {'raw': 'Screenshot\\n\\nSteps to reprduce:\\n\\n1.Open VE\\n2.Open any drop down box that comes up with a list of matching suggestions:for example:Link inspector, Category editor, template etc.\\n3.Type something in the text box\\n4.When the matching suggestions appear in the drop down box,observe that the first match which has a check mark next to it, is highlighted\\n5.Now mouse over that match in the drop down and \\n\\nObserved Result:\\nThe selection loses it highlight\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13596}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402921830, 'spacePHID': None, 'dateCreated': 1401841740, 'dateModified': 1443278148, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66106', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If you have added a category already, typing it in a second time doesn\\'t show it in the list — except if the category is a \"red link\", in which case it will suggest it as a new one again', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open VE\\n2.Go to Page options>Categories\\n3.Insert a new category:Ca, it appears under matching categories section according to the change on https://bugzilla.wikimedia.org/show_bug.cgi?id=49044\\n4.Select the first match Ca\\n4.Now again type Ca\\n\\nObserved Result:\\nThis time it appears under New Category section.\\n\\n\\nsee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13594}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401920048, 'spacePHID': None, 'dateCreated': 1401840480, 'dateModified': 1417572218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66105', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Issues with shields/highlights/phantoms (tracking)', 'description': {'raw': 'This is a tracking bug for all shields/highlights/phantoms related issues.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411510006, 'spacePHID': None, 'dateCreated': 1401819000, 'dateModified': 1553164190, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66083', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Upgrade nodejs from 0.8.x to 0.10.x on wmflabs integration slaves', 'description': {'raw': \"This is overdue.\\n\\nVarious packages used by individual Grunt tasks used by local projects already throw warnings for the engine being unsupported.\\n\\nThese are not the packages for the legacy global tools in package.json in integration/jenkins.git:/tools aka slave-scripts, but the local package.json in projects like oojs, oojs-ui and VisualEditor.\\n\\nAs far as I can see these jobs seem to function fine, but it's really dangerous territory. The packages are explicitly indicated as requiring 0.10.x or higher (it's like executing a PHP application documented as requiring PHP 5.3 under PHP 5.1.x).\\n\\nBoth the upstream developer, their integration tests and the developers in our teams working locally already use Nodejs 0.10.x or higher, so this is waiting for something to fail.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410826571, 'spacePHID': None, 'dateCreated': 1401749760, 'dateModified': 1429023900, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66056', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Be able to specify a file name in the media or image dialog, even if search can't find the file\", 'description': {'raw': 'This might be something that could be associated with Bug 52463:\\n\\nIf Search can\\'t find an image—which happens fairly often with images that the user just uploaded—then please let the user specify the file name anyway.  Right now, if Search didn\\'t happen to index your file yet, then you cannot add the image.  \"Try again tomorrow, because maybe the search index will have caught up by then\" is not an ideal user experience.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409583730, 'spacePHID': None, 'dateCreated': 1401737880, 'dateModified': 1424894574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66046', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cross-link stats.wikimedia.org and ee-dashboard.wmflabs.org', 'description': {'raw': 'There should be links http://stats.wikimedia.org/EN/EditsRevertsIT.htm <-> http://ee-dashboard.wmflabs.org/dashboards/itwiki-metrics#reverts-graphs-tab and http://ee-dashboard.wmflabs.org/dashboards/itwiki-metrics#registrations-graphs-tab <-> http://ee-dashboard.wmflabs.org/dashboards/itwiki-metrics#registrations-graphs-tab .\\nOnly applies to the ten Wikipedias having them: https://meta.wikimedia.org/wiki/Research:VisualEditor\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1463086361, 'spacePHID': None, 'dateCreated': 1401617460, 'dateModified': 1463086361, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65994', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Do not allow creation of empty lists inside tables (?!)', 'description': {'raw': 'This should not happen:\\nhttps://pt.wikipedia.org/w/index.php?diff=39042930\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1401531960, 'dateModified': 1416792037, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65970', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Unrelated content in produced PDF', 'description': {'raw': 'Sample PDF\\n\\n1) http://eo.wikipedia.beta.wmflabs.org/wiki/Headings_VisualEditor_Test\\n2) \"Elŝuti kiel WMF PDF\"\\n\\nResult: a page with content coming from I have no idea where, see attachment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13832}'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406235095, 'spacePHID': None, 'dateCreated': 1401439440, 'dateModified': 1418753859, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65939', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove gallery button from the Insert Menu', 'description': {'raw': 'Screenshot\\n\\nI dont see any option to insert gallery in the Insert medu suddenly.\\nHappening in betalabs and test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13825}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401471842, 'spacePHID': None, 'dateCreated': 1401431340, 'dateModified': 1443278151, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65936', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking on Edit link beside a section heading does not take user to that specific heading rather takes to the beginning of the article', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit/Edit Beta link beside a section heading of an article\\n\\nObserved Result:\\nIt places the cursor at the beginning of the document .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403726656, 'spacePHID': None, 'dateCreated': 1401412380, 'dateModified': 1443278151, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65928', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: On pages which are redirects, veaction=edit should actually do redirect=no&veaction=edit', 'description': {'raw': 'Steps to Reproduce:\\n1. Click on https://en.wikipedia.org/wiki/Sugar_candies?veaction=edit\\n\\n2. Wonder why it is editing https://en.wikipedia.org/wiki/Sugar_candy (the target) instead of https://en.wikipedia.org/wiki/Sugar_candies (the redirect)?\\n\\n\\nActual Results:  \\nIt first redirects me to the target page, and then opens the target page for editing.  This makes it impossible to change the redirect to some other page, unless you modify the URL to say https://en.wikipedia.org/wiki/Sugar_candies?veaction=edit&redirect=no (either manually or by first visiting to the redirect page).\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65621'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402422604, 'spacePHID': None, 'dateCreated': 1401409620, 'dateModified': 1511311226, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65926', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Inline images don't display correctly if converted to floating images and then back\", 'description': {'raw': 'Steps to Reproduce:\\n1. Open a page that contains inline images at the start of a paragraph or list item.\\n\\n2. Select the image, open the image dialog, and de-select the \"Wrap text around\" item.  The item will float right.\\n\\n3. Change your mind.  Open the imge dialog again, and re-select the \"Wrap text around\" item.\\n\\nActual Results:  \\nThe inline image appears to be, but isn\\'t actually, on its own line.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403035582, 'spacePHID': None, 'dateCreated': 1401406980, 'dateModified': 1443278152, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65924', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Media settings dialog shows two selected values of alignment if you unchecking then checking the wrap option', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Insert an image of any type\\n\\n2.Uncheck the wrap option\\n\\n3.Check the wrap option again\\n\\n4.Checking the wrap option automatically selects the \"Right\" as alignment again\\n\\n5.Now click on one of the other alignment option:Centre/Left\\n\\nObserved Result:\\n\\nThe alignment tab for \"Right\" is still selected, also the new one of step 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13768}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402102893, 'spacePHID': None, 'dateCreated': 1401400020, 'dateModified': 1443278155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65916', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: When providing a list of potential links, show redirects' destinations, not just that they are redirects\", 'description': {'raw': 'VisualEditor can determine if the link you are adding is a redirect or not (since Bug 50240), but it doesn\\'t tell what the redirect page goes to. Just seeing \"Redirect page\" in the linking tool doesn\\'t tell the user whether or not they\\'re linking to the page they want to be linking to, so I think it should say \"Redirect page to $1\", where $1 is the destination of the redirect that\\'s being linked.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-qze3uk4zsetjvgf7liey', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1435939976, 'spacePHID': None, 'dateCreated': 1401343080, 'dateModified': 1439331331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65890', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Changing image from floated (right+basic) to thumb does not update size correctly', 'description': {'raw': \"Take an image like [[File:Bigimage.png|border|right]], inspect it, and change it to a thumbnail. You get a thumbnail image of the exact same dimensions. But when you save, this serializes to [[File:Whatever.png|thumb]], which renders in read mode (and when you reopen it in VE) as a much smaller image, because it's using the default thumb size.\\n\\nI would argue that, when you switch to thumb, it should use the default size for thumbs right then and there, but in any case, it's clear here that what's being displayed in CE is not an accurate reflection of what's actually going to happen when the user saves, and that's a problem.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401926542, 'spacePHID': None, 'dateCreated': 1401325260, 'dateModified': 1417572289, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65886', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make SurfaceWidget constructor not depend on global target', 'description': {'raw': \"See discussion at https://gerrit.wikimedia.org/r/#/c/135012/ . I think the SurfaceWidget constructor shouldn't use the global target, but instead take a config option telling it what kind of surface to construct, or take a surface object, or something.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1401319080, 'dateModified': 1643977423, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65881', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  If the TemplateData description for a parameter is just whitespace, then hide the help/information button', 'description': {'raw': 'If the \"description\" field for TemplateData is empty, clicking the help/information button (an i with a circle around it) for the parameter produces a very skinny, empty box.  Nothing should be displayed when there is no description to display.\\n\\nAlternatively, it\\'s possible that some standard text could be put in the box, like \"There is no description for this item\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401471687, 'spacePHID': None, 'dateCreated': 1401297960, 'dateModified': 1417572295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65862', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] Making an image Frameless/Basic with centre alignment moves the image to the left', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a new image\\n3.Select the option \"Centre\" for wrapping the text around it\\n4.Select the type as \"Frameless\" or \"Basic\"\\n5.Save the page\\n\\nObserved Result:\\n\\nThe image moves to the left side of the page \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13568}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401313400, 'spacePHID': None, 'dateCreated': 1401230100, 'dateModified': 1443278155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65836', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Issues with new Image model (tracking)', 'description': {'raw': 'This is a tracking bug for all the issues related with new Image model\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403117822, 'spacePHID': None, 'dateCreated': 1401217980, 'dateModified': 1443278155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65829', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: [Regression wmf5] Beta warning appears for every edit for users who didn't get a cookie set whilst anon\", 'description': {'raw': 'On mediawiki.org in both Chrome and FF. \\n\\nEdit any page with VE, either logged in or not.  Note that you get the beta warning.\\n\\nSave your edit. Edit the page again. \\n\\nSee the beta warning again.\\n\\nAfter one new VE edit, the user should never see the beta warning again.  This is controlled by setting a cookie in the browser.  No betawarning cookie is being set now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401485379, 'spacePHID': None, 'dateCreated': 1401210720, 'dateModified': 1417572292, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65821', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enabling TemplateData editor in Catalan Wikipedia', 'description': {'raw': '/me waves with my volunteer ca.wiki tech ambassador hat on.\\n\\nThe Catalan Wikipedia community wants to try the TemplateData editor. Can you enable it, please? Discussion (in Catalan) at\\n\\nhttps://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Ajuda#VisualEditor_global_newsletter.E2.80.94May_2014\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402010019, 'spacePHID': None, 'dateCreated': 1401145140, 'dateModified': 1402084129, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65785', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Left/right cursoring into block slug doesn't trigger animations\", 'description': {'raw': '--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1424740573, 'spacePHID': None, 'dateCreated': 1401018180, 'dateModified': 1427672929, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65742', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The image does not remain highlighted but the areas around it are instead, after making an image frameless-right or basic-right', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Make it Frameless-right or Basic-Right\\n4.Hover over the image after that\\n\\nObserved Result:\\nThe area around the image remains highlighted but not the image itself\\n\\nSee the screenshot attached\\nEnvironment: Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13899}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403200726, 'spacePHID': None, 'dateCreated': 1400889120, 'dateModified': 1443278159, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65716', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] The previous line is also getting highlighted while adding a reference list/image', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403200723, 'spacePHID': None, 'dateCreated': 1400885280, 'dateModified': 1443278159, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65706', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: avoid causing \"Translation unit markers in unexpected position\" edit abort', 'description': {'raw': '\"Translation unit markers in unexpected position.\" can just go die in Hell. Gah.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also:** {T58451}, {T73730}, {T50891}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400786640, 'dateModified': 1516414993, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65653', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Categories and DEFAULTSORT meta items getting modified to strip default whitespace?', 'description': {'raw': 'Sometimes editing a page in VisualEditor is rearranging categories so that they always end up on a single line, which is inconvenient for people looking at the wikitext source later.\\n\\nSee https://fr.wikipedia.org/w/index.php?title=Jean-Baptiste_Vallière&diff=prev&oldid=104017086\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400782560, 'dateModified': 1462716700, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65647', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Span tags for Language tool only mark part of the page', 'description': {'raw': 'Intention:\\nMark almost an entire page with language (en) and direction (LTR).\\n\\nSteps to Reproduce:\\n1.  Open the page and select almost all of the content.\\n \\n2.  Insert > Language\\n\\n3.  Set the language to English and the direction to LTR.\\n\\nActual Results:  \\nOnly a small fraction of the page was marked with span tags.  See https://office.wikimedia.org/w/index.php?diff=112247&oldid=112246\\n\\nExpected Results:  \\nI wanted this:\\n\\n<span lang=\"en\" dir=\"ltr\">\\nDiv box \\nImage\\nText\\nImage\\nSome text\\nEnd of div box\\nLots and lots and lots of text\\n</span>\\n\\nI got this:\\n\\nDiv box \\nImage\\n<span lang=\"en\" dir=\"ltr\">Text</span>\\nImage\\n<span lang=\"en\" dir=\"ltr\">Text</span>Some te</span>xt\\nEnd of div box\\nLots and lots and lots of text\\n\\n\\nReproducible: Always\\n\\nThis was exactly repeatable on this page:  the last span tag always ended in the middle of the same word.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://office.wikimedia.org/w/index.php?diff=112247&oldid=112246'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400781180, 'dateModified': 1416792050, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65645', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add redirect=no to URL after a page is newly created as a redirect', 'description': {'raw': \"When you create a redirect with wikitext, it adds redirect=no.\\n\\nHowever, VisualEditor does not (just venotify=created), so you end up going to the target.  Besides being inconsistent, that means it's one extra step to check WhatLinksHere, etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65926\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402422803, 'spacePHID': None, 'dateCreated': 1400742720, 'dateModified': 1443278163, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65621', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Can't cut or copy citation template in Reference dialog\", 'description': {'raw': \"Intention:\\nCopy a reference's contents (not including ref tags).\\n\\nSteps to Reproduce:\\n1. Open a page in Safari.  Add a citation using the Cite tool.\\n\\n2. Open the new reference in the Reference dialog via Insert > Reference.\\n\\n3. Select the contents, and press Command-X to cut it.\\n\\nActual Results:  \\nNothing happens.  The template is not cut.\\n\\nExpected Results:  \\nIt should be possible to copy and paste citation templates, so that you can modify them for other citations or display them on the page outside of <ref> tags.  \\n\\nReproducible: Always\\n\\nThis bug cannot be reproduced in Firefox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701963637, 'spacePHID': None, 'dateCreated': 1400688180, 'dateModified': 1701963637, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65593', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Categories without description pages don't show as red\", 'description': {'raw': \"It's possible to have a category bubble in the category editor for a category that doesn't have a description page. It would be useful to see that it doesn't exist.\\n\\nIn the source editor this can be achieved while editing by doing a preview and seeing that the link at the bottom is red, so this is a bit of a regression.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49044\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415543481, 'spacePHID': None, 'dateCreated': 1400565480, 'dateModified': 1417571674, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65517', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Disentangle MWSaveDialog and mw.ArticleTarget', 'description': {'raw': \"Right now, the way that the save button is disabled when you click it is that MWSaveDialog listens to the button's click event, in response to that it fires the 'save' event, ArticleTarget gets that event, reaches into the save dialog and disables the button.\\n\\nThis is only one of many insane things about the totally dysfunctional MWSaveDialog - ArticleTarget relationship; the whole way these two interact should be refactored.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400545500, 'dateModified': 1643977423, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65513', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Instrument all actions in visual editing toolbar for organization and frequency of use analysis and improvements', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64711'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400535300, 'dateModified': 1643977423, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65510', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template editor is missing accessibility features', 'description': {'raw': 've-ui-mwParameterPage-actions have tabindex=-1, which makes them unreachable by keyboard, the same for the \"Add parameter\" button.\\n\\n\\nThe text area of the fields is missing the \\'required\\' attribute for fields that are required.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65473\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62337'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401928390, 'spacePHID': None, 'dateCreated': 1400491140, 'dateModified': 1575898098, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65474', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: From a cold start using debug=true, there's no indication VE is loading for a few seconds; move some init stuff further up?\", 'description': {'raw': 'When I access\\nhttps://pt.wikipedia.org/w/index.php?title=Usuário(a):Helder.wiki/Testes&oldid=38949256&veaction=edit&debug=1\\nwith an empty cache on Firefox 29, it takes at 5+ seconds until I see any progress bar. Sometimes this makes me click in the edit link again because it seems not to be loading at all...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413928460, 'spacePHID': None, 'dateCreated': 1400418840, 'dateModified': 1417571689, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65453', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Link inspector gets unresponsive once you delete all the content of a page and click on link inspector icon', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Mobile VE which has some content in it\\n2.Delete all the content\\n3.Click on the Link inspector icon from the toolbar\\n\\nObserved Result:\\n\\nUser gets stuck at this point , cannot close the link inspector dialog anymore by tapping on \"<\" or trash icon\\n\\nTest Environment: https://en.m.wikipedia.org/\\nDevice: iPad Mini\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13828}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404167469, 'spacePHID': None, 'dateCreated': 1400275140, 'dateModified': 1443278171, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65418', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Cells in tables are styled like regular paragraphs, and they shouldn't be\", 'description': {'raw': \"Reproducible: Didn't try\\n\\nTables like the ones seen at https://en.wikipedia.org/w/index.php?oldid=608813235#Early_years don't display with the correct row height when editing, because VisualEditor assumes that table cells' paragraphs should be styled like other paragraphs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403720007, 'spacePHID': None, 'dateCreated': 1400272920, 'dateModified': 1469823941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65416', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: VE is not appearing as an option to edit even if Beta-Experimental mode is on in iPhone 4S', 'description': {'raw': 'Screenshot\\n\\nI am not getting the VisualEditor for mobile even after enabling it through Beta-Experimental mode while trying to edit this page:https://en.m.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox\\n\\nsee the screenshot attached:\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13822}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401417974, 'spacePHID': None, 'dateCreated': 1400272860, 'dateModified': 1417572298, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65415', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The tapping on Mobile VE is extremely inconsistent compared to standard', 'description': {'raw': 'I experienced a huge inconsistency around the precision of tapping action for Mobile VE in all kind of iOS devices I have tried so far.The devices I observed this issue are: iPad 2 with iOS 7.1.1 , iPhone 4S with iOS 7.1.1 and iPad Mini with iOS 7.0.6\\n\\nSome times , to open the VE and to select a menu options like Settings/Random/Username , it literally takes me to tap twice.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434488548, 'spacePHID': None, 'dateCreated': 1400271360, 'dateModified': 1434492400, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65413', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The keyboard stays in the ReadMode after tapping on the Browser back button/ the cross button on the Mobile VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with Mobile\\n2.Attempt to edit it\\n3.While keyboard is still appearing tap on the \"X\" button on the top left of VE or just tap on the browser back button.\\n\\nObserved Result:\\nUser is redirected to Readmode but the keyboard is still appearing .\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13816}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434487692, 'spacePHID': None, 'dateCreated': 1400270460, 'dateModified': 1434492390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65411', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: URLs followed immediately by {{templates}} are improperly displayed and cannot be edited', 'description': {'raw': 'Something like `http://example.com{{deadlink}}` cannot be properly edited in VisualEditor. It should be processed as two pieces:  one external link that is followed immediately by one template.  Instead, it is presented as the text \"http://example.com[]\", linked to `http://example.com[]`. '}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400180460, 'dateModified': 1705333221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65362', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit led to a <noinclude> tag being removed (?)', 'description': {'raw': \"* https://www.mediawiki.org/w/index.php?diff=prev&oldid=1002914\\n\\nI performed the edit by highlighting the digit '3' with my mouse, and pressing the alphanumerical key '5' on my keyboard; my intention was only to change the date, but VE also removed the <noinclude> tag (I re-added it in a subsequent edit).\\n\\nFiling this bug after a request from James on IRC.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://www.mediawiki.org/w/index.php?title=MediaWiki_1.24/Roadmap&diff=prev&oldid=1002914\"}, 'authorPHID': 'PHID-USER-hxjysvdvogekpjub3nd3', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403220256, 'spacePHID': None, 'dateCreated': 1400179560, 'dateModified': 1417572145, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65360', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Cursor appears over the toolbar in iPad Mini and Nexus 7 for Mobile VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with Mobile VE which has some content in it\\n2.Scroll a bit down \\n3.Tap on any text and then keep on tapping on Return until it deletes the whole line just after the toolbar \\n\\nObserved Result:\\nAfter deleting the line just after where the toolbar starts it moves over the toolbar\\n\\nSee the screenshot attached\\n\\nTest Environment: https://en.m.wikipedia.org/\\nDevice: iPad Mini\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13595}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434488607, 'spacePHID': None, 'dateCreated': 1400113740, 'dateModified': 1434492402, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65325', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create hooks for extensions to show/hide things when VE activates/deactivates', 'description': {'raw': 'A more generic way of doing https://gerrit.wikimedia.org/r/133379\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400110506, 'spacePHID': None, 'dateCreated': 1400108520, 'dateModified': 1443278175, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65320', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The \"Review your changes\" button should be disabled when save dialog is busy', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Make some edit\\n3.Click on Save Page on the Save page dialog\\n4.While loading bar is in progress click on \"Review your changes\"\\n\\n\\nObserved Result:\\nIt opens up the Review section while the loading bar is still showing up above and below the dialog.\\n\\nEnvironment:Betalabs,test2 and production\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13552}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415234332, 'spacePHID': None, 'dateCreated': 1400099820, 'dateModified': 1417571681, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65310', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Vector: Menu items that are hidden should not be made visible by collapsibleTabs', 'description': {'raw': 'Add an item to the tab area with class \"collapsible\" and display none applied.\\n\\nThen make the window narrow (so it moves into the vector menu), and expand again (so it becomes a tab again).\\n\\nThe item is now visible when it was previously hidden.\\n\\nvector.collapsibleTabs.js should not override this state.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400527665, 'spacePHID': None, 'dateCreated': 1400088600, 'dateModified': 1469893978, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65294', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When editor is unavailable, edit menu item can re-appear', 'description': {'raw': 'Steps to Reproduce:\\n1.  Open a Wikipedia article in the article namespace. \\n\\n2.  Resize the window to a very small size so that the buttons overlap to the next line. \\n\\n3.  Resize the window to the original size and see that the \"Edit beta\" button shows up, which was previously not there.\\n\\n4.  Click on the new button to open VisualEditor.\\n\\nActual Results:  \\nClicking the button produces an error message:\\n\\nError loading data from server: novenamespace: VisualEditor is not enabled in namespace 4. Would you like to retry?\\n\\nClicking OK closes this dialog, but immediately pops up another one of the same kind. \\n\\nExpected Results:  \\nThat the button wouldn\\'t ever be visible, and that if it were, that it wouldn\\'t give an error message about namespace 4.\\n\\nReproducible: Didn\\'t try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400523393, 'spacePHID': None, 'dateCreated': 1400086320, 'dateModified': 1443278177, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65292', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Using \"page down\" (PgDn) key to scroll down moves the wrong number of lines if the toolbar is on multiple lines', 'description': {'raw': \"Steps to Reproduce:\\n1. Open a long page in VisualEditor.  Press Ctrl-+ several times, until the toolbar is too wide to fit on a single line.\\n\\n2. Press PgDn (the page down key).\\n\\n\\n\\nActual Results:  \\nThe wrong number of lines is moved, so that a couple of lines is never seen.\\n\\n\\nReproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1399935060, 'dateModified': 1605232591, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65241', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Change \"newspaper\" to \"news\"', 'description': {'raw': 'https://en.wikipedia.org/wiki/MediaWiki:Visualeditor-cite-tool-definition.json says:\\n\\n   { \"name\": \"news\", \"icon\": \"ref-cite-news\", \"template\": \"Cite news\" },\\n\\n\\nShouldn\\'t the \"name\" part determine the name that\\'s showing in the list?\\n\\nThe actual tool says \"newspaper\" instead of \"news\".  I want it to say \"news\" (because the news might come out of a news-magazine or a news-TV show or a news-website, not just a news-paper).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400279121, 'spacePHID': None, 'dateCreated': 1399852860, 'dateModified': 1443278180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65207', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit led to a DEFAULTSORT entry being removed(?)', 'description': {'raw': \"Just don't.\\n\\n* https://pl.wikipedia.org/w/index.php?diff=39429954&oldid=38515622\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-hxjysvdvogekpjub3nd3', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1457475200, 'spacePHID': None, 'dateCreated': 1399826160, 'dateModified': 1461807085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65200', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a wiki-specific tool in the formatting menu that wraps selections in templates for semantic mark-up', 'description': {'raw': 'e.g. in wiktionary semantic classes such as \"distinct feature,\" \"usage example,\" \"syllables,\" \"pronunciation,\" etc.\\n\\nThese would likely be more important for this community than the default preformatted styles used on wikipedia.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1399769820, 'dateModified': 1643977423, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65173', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor as Beta Feature on Wikimedia Commons', 'description': {'raw': 'Please enable VisualEditor as a Beta Feature on Wikimedia Commons, not enabled by default.\\n\\nBeta features are (as far as I know) completely harmless so I do not think a community discussion is necessary but I would be happy to start one if necessary.\\n\\nI will post a heads-up on this on Wikimedia Commons village pump.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-m7etbwqrv6cfrg5ymrwx', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400137590, 'spacePHID': None, 'dateCreated': 1399639800, 'dateModified': 1540682746, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65067', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Standalone doesn't have an RTL stylesheet\", 'description': {'raw': 'Build a grunt task out of https://github.com/trevorparscal/cssjanus ?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404322288, 'spacePHID': None, 'dateCreated': 1399629240, 'dateModified': 1443278180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65057', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Put block slugs in the DM rather than fake them in CE', 'description': {'raw': \"The concept of a block slug from a UX POV is great, but why do we need to keep them out of the DM? It seems to be the source of far too many getOffset hacks, as you can put your cursor somewhere that doesn't have a real offset (model-view inconsistency). We already have a way of marking a paragraph as to-be-ignored-by-the-converter-if-empty ({internal:'empty'}), so let's just put them in the DM, and throw them away at convert time if they're empty.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412898085, 'spacePHID': None, 'dateCreated': 1399621440, 'dateModified': 1417571691, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65052', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Media dialog search box is blank after the first use; should instead be reset to the page name', 'description': {'raw': 'page title in media search box\\n\\non any page in beta labs e.g. http://en.wikipedia.beta.wmflabs.org/wiki/0.8782466280521993?veaction=edit\\n\\non first page load, select some text in the page, and then open Media\\n\\n* page title may be in Media search box. see screen shot.\\n\\nclose the Media inspector, select text again, open Media inspector\\n\\n* Media search box is now blank\\n\\n** Sometimes selected text is in the Media inspector search box instead of page title.  see other screen shot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64655\\n\\n**Attached**: {F13511}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404405491, 'spacePHID': None, 'dateCreated': 1399574700, 'dateModified': 1443278180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65038', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting plain text from external sources inserts spurious double new lines between paragraphs in Safari', 'description': {'raw': 'Intention:\\nPaste some plain text.\\n\\nSteps to Reproduce:\\n1. Type a few paragraphs of plain text.  I typed mine into an Apple Mail message with rich text turned off.  My text was:\\n\\nI get to play with lists.\\nI like to play with lists.\\n\\nI wonder if this will do what I want.\\n\\nWhat I want is for this not to be in a list.\\n\\n\\n2. Open VisualEditor.\\n\\n3. Copy and paste the plain text into VisualEditor.\\n\\n\\nActual Results:  \\nInstead of getting this:\\n\\nI get to play with lists.\\nI like to play with lists.\\n\\nI wonder if this will do what I want.\\n\\nWhat I want is for this not to be in a list.\\n\\n\\nI got this:\\n\\nI get to play with lists.\\nI like to play with lists.\\n\\n\\nI wonder if this will do what I want.\\n\\n\\nWhat I want is for this not to be in a list.\\n\\n\\nWhen it saved, there were actually three blank lines between the paragraphs.  This can be seen at http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=92715&oldid=92368\\n\\n\\nReproducible: Always\\n\\nThis is not the same as Bug 58283.  Also, I could not reproduce this in Firefox 29.  It happens every time in Safari 6.1.3.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1399495620, 'dateModified': 1416792243, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65021', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switching to source mode should show a spinner, pending state or similar', 'description': {'raw': 'As of May 6th, I am experiencing a lag in switching from VE to Edit source mode, after clicking on Ok on \"Switch to source editing\" dialog, for 5-6 secs, it seems like nothing is happening on my browser. \\n\\nThis is happening even if I have perfect network speed and all other things loading properly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410911296, 'spacePHID': None, 'dateCreated': 1399489320, 'dateModified': 1443278180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Vertical cursoring can get cursor stuck on a paragraph-terminal reference in Firefox', 'description': {'raw': 'From bug 50726 comment : \\n\\n| Steps to reproduce:\\n| 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.\\n| 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.\\n| 3. Press down. (the cursor should now be directly right of of the first reference)\\n| 4. Press down.\\n| \\n| Result: The cursor is stuck on the first reference.\\n| \\n| (The same result can be achieved by placing the cursor in the second paragraph and pressing up)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/wiki/Jos%C3%A9_Cl%C3%A1udio_Ribeiro_da_Silva?veaction=edit'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1493661863, 'spacePHID': None, 'dateCreated': 1399419720, 'dateModified': 1493661863, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64983', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] \"Middle click\" / Cmd+Click on mac no longer open links\\' targets in a new tab', 'description': {'raw': 'open in new tab used to work for links while in VE with CMD+Click on mac, this no longer works\\n\\nMac 10.9.2 / Chrome Version 35.0.1916.86 beta\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402552906, 'spacePHID': None, 'dateCreated': 1399414860, 'dateModified': 1417572224, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64974', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fail gracefully (not \"fatal exception\") when being run on MW 1.22.6 rather than supported version', 'description': {'raw': '**Author:** `richlv`\\n\\n**Description:**\\nmw 1.22.6. enabling latest visual editor from git results in :\\n\"Fatal exception of type MWException\"\\n\\nafter some testing, no specific error messages could be seen in apache error log.\\n\\naccording to James_F, \"VE master needs MW 1.23, yes - but it should also fail gracefully when you try to start it, rather than have random fatal errors\" :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1613562732, 'spacePHID': None, 'dateCreated': 1399412280, 'dateModified': 1613562732, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64971', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  A straight line appears above the image while making it (Frameless/Basic-Left/Right-border)', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Make it frameless-left-border or basic-left-border \\n\\nObserved Result:\\nA straight line appears over the image.If you now move the image to center it will go away, but if you again change it to frameless-right-border or basic-right-border from center, the straight line will appear again\\n\\n\\nSee the screenshot attacahed\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13981}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404866921, 'spacePHID': None, 'dateCreated': 1399403760, 'dateModified': 1417572039, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64966', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support magic pasting of HTML that contains a transclusion of or link to a wiki image', 'description': {'raw': 'Right now if you have some rich content with an image and paste it into VisualEditor, we discard the image.\\n\\nHowever, it\\'d be nice to add some special handling in VisualEditor\\'s paste for the HTML of images so that those from Commons used on a MediaWiki instance get sought out and inserted instead.\\n\\nPerhaps via a special custom attribute VE would sniff for, that would make VE try to find the image from Commons (if the wiki was configured for InstantCommons), or other fileRepos?\\n\\nMediaViewer\\'s \"embed\" HTML looks like:\\n\\n| <p><a href=\"http://commons.wikimedia.org/wiki/File:Beach_sand.jpg#mediaviewer/File:Beach_sand.jpg\"><img src=\"http://upload.wikimedia.org/wikipedia/commons/c/c5/Beach_sand.jpg\" alt=\"Beach sand.jpg\" height=\"1200\" width=\"1600\"></a>[…]</p>\\n\\nIf we asked them to add an attribute, e.g. (simplified):\\n\\n| <p><a href=\"…\"><img src=\"…\" alt=\"…\" ve-data=\"ve-pastableImage\" ></a>[…]</p>\\n\\n… could we do this?\\n\\n(Also, yes, they should be using <figure> instead of <p><img></p>.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1399337460, 'dateModified': 1643977424, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64935', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'mediawiki.Uri does not support IPv6 URIs', 'description': {'raw': \"mediawiki.Uri does not support IPv6 URIs:\\n\\n```\\n> var uri = new mw.Uri( 'http://127.0.0.1/' )\\nundefined\\n> var uri = new mw.Uri( 'http://[::1]/' )\\nError: Bad constructor arguments\\n```\"}, 'authorPHID': 'PHID-USER-3dmql6z7s5lnn5lu2vs3', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1645032574, 'spacePHID': None, 'dateCreated': 1399291380, 'dateModified': 1671055878, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64884', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Ctrl+cursor (Opt+cursor on Mac) moves the caret too far in Hebrew', 'description': {'raw': 'Ctrl-Arrow is supposed to move the caret one word in the direction of the arrow.\\n\\nIn RTL wikis it moves too far. It looks like to goes to the next reference or the next sentence rather than the next word.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399626919, 'spacePHID': None, 'dateCreated': 1399285200, 'dateModified': 1443278184, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64872', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Keyboard shortcut dialog lists heading change incorrectly labelled on Mac', 'description': {'raw': 'Noticed on our Wikia integration, and saw that it was incorrect here: https://www.mediawiki.org/wiki/VisualEditor?veaction=edit\\n\\nhttp://screencast.com/t/sin5AakmN0\\n\\nThe shortcut list shows that Command plus a number changes the heading value. This is incorrect, as it controls the browser\\'s tabs. The correct label should be \"Command\".\\n\\nI tested this in latest Firefox and latest Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399323214, 'spacePHID': None, 'dateCreated': 1399069920, 'dateModified': 1443278185, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64771', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Optimistic saving', 'description': {'raw': 'We should adapt the save prediction / optimistic parsing logic in VisualEditor and provide it for the standard wikitext editor. See T58011 for the full description.\\n\\nAdding Roan as CC since he implemented this for VisualEditor and thus may have useful feedback.\\n\\n--------------------------\\n**Version**: 1.24rc\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': 'PHID-USER-bmbmvb2e5bg6ztcangbq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-bmbmvb2e5bg6ztcangbq', 'dateClosed': 1428434954, 'spacePHID': None, 'dateCreated': 1399063020, 'dateModified': 1449707215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64767', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transition between read mode and edit mode should have minimal visual shifts', 'description': {'raw': \"Issues right now:\\n\\n* Different set of elements (e.g. #contentSub is shown in read mode, but not in edit mode. The same goes for TOC, though we do account for that one).\\n\\n* Different offset (the toolbar is injected which causes an abrupt visual shift).\\n\\n* Different scroll offset (same as before, but applies when you open the editor when scrolled down the page, after the transition, you're looking at a potentially very different part of the document, we should preserve it or jump to the top, not leave you somewhere randomly).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399344356, 'spacePHID': None, 'dateCreated': 1399049040, 'dateModified': 1457223239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64751', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Dialog panes don't seem to apply any padding to the bottom of their content in Firefox (but not Chrome), so the contents of the pane can almost overlap with the border of the dialog\", 'description': {'raw': 'In Firefox\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE in Firefox\\n\\n2.Insert a media\\n\\n3.Go to Media Settings of that image\\n\\n4.Scroll down the dialog box \\n\\nObserved Result:\\n\\nThere is no gap between the textbox for Alternative text and the border of the dialog , its almost overlapped with the border as compared to how it appears in Chrome\\n\\nSee the screenshots attached\\n\\nTest Environment:\\nhttp://en.wikipedia.beta.wmflabs.org/ and \\nhttps://en.wikipedia.org/\\n\\nBrowser: FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14031}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1697485606, 'spacePHID': None, 'dateCreated': 1398981780, 'dateModified': 1697485606, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64723', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Citation tool should not add empty citation templates', 'description': {'raw': 'Steps to Reproduce:\\n1. Citation > Cite web\\n\\n2. Don\\'t add any information.  Just click \"Apply changes\".\\n\\nResult:  <ref>{{Cite web|url = |title = |date = |accessdate = |website = }}</ref>\\n\\nThat\\'s pointless.  If the fields are blank, don\\'t add it (or remove it).\\n\\n\\nSteps to reproduce, part 2:\\n\\n1. Citation > Cite web\\n\\n2. Don\\'t add any information.  Delete all the parameters. \\n\\n3. Click \"Apply changes\".\\n\\nResult:  <ref>{{Cite web}}</ref>\\n\\nThat\\'s even more pointless.  If there are no parameters, don\\'t add it (or remove it).\\n\\n\\n\\n\\n\\nReproducible: Didn\\'t try\\n\\n(The \"invalid\" parameter in that diff was manually created by me.  I don\\'t think you can do anything to help the person adding invalid parameters, because there\\'s no way to differentiate between invalid parameter names and valid names that don\\'t happen to be defined in TemplateData.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Whatamidoing_(WMF)/Sandbox&diff=91690&oldid=91686'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401922554, 'spacePHID': None, 'dateCreated': 1398976860, 'dateModified': 1417572289, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64715', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Citation tool opens if you click the icon, but if you double-click the ref or press the return key, the Reference dialog opens instead', 'description': {'raw': \"Intention:\\nEdit an existing citation.\\n\\nSteps to Reproduce:\\n1.  Select an existing citation (one using a citation template).\\n2.  Press the return key to open it.\\n3.  That's odd, I'm in the Reference dialog.  Exit.  \\n4.  Re-select the citation.  \\n5.  Double-click to open it.  \\n6.  That's odd, I'm in the Reference dialog.  Exit.  \\n7.  Re-select the citation.  \\n8.  Click the little cite-web icon.  That opens the citation tool's simplified dialog.\\n\\nThis happens in both Safari and Firefox, so presumably everywhere. \"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1531409201, 'spacePHID': None, 'dateCreated': 1398975240, 'dateModified': 1531409202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64712', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector does not highlight/remove default linked text sometimes in automated testing in Chrome', 'description': {'raw': 'first word in page text is still in link box after clicking and typing\\n\\nseen in Chrome only as of 30 Apr: \\n\\nas a logged in user on beta labs, invoke VE on a page containing text\\n\\nwithout typing or clicking anything else, click the Link icon\\n\\nthe first word in the page text is in the box to create the link\\n\\n* problem: the text in the link box is not automatically highlighted\\n\\nclick in the link box to create the link text\\n\\n* problem: default text in the link box that should be highlighted should also be removed when the user clicks in the box to type their own link\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65038\\n\\n**Attached**: {F13875}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401818677, 'spacePHID': None, 'dateCreated': 1398867000, 'dateModified': 1417572290, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64655', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf22] \"Edit source\" tab for wikitext no longer selected on action=edit', 'description': {'raw': 'In Vector/1.24wmf2, the \"Edit source\" tab is not highlighted when editing a page in source mode (no tab is highlighted).\\n\\nExample:\\nhttp://www.mediawiki.org/w/index.php?title=Help:Preferences&action=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398899187, 'spacePHID': None, 'dateCreated': 1398829320, 'dateModified': 1443276198, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64646', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: 500 server error from api.php and \"Unknown Error\" appears on the Save dialog box if only a newline is added to the document after a gallery', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Just add a newline by pressing the return\\n3.Click on the \"Save Page\" button which got enabled \\n\\nObserved Result:\\n \"Unknown Error\" appears on the Save dialog box\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: http://en.wikipedia.beta.wmflabs.org/wiki/28thAprilChrome?veaction=edit\\n\\n**Attached**: {F13652}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399994453, 'spacePHID': None, 'dateCreated': 1398715020, 'dateModified': 1417572390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64566', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The highlight boxes for templates/images/cite notes/math/references inside the caption of an image are appearing on hovering over the image inside VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.In the caption of the image add templates/images/cite notes/math/reference\\n4.Click on \"Apply Changes\"\\n5.Now hover over the image\\n\\nObserved Result:\\nThe highlight boxes for templates/images/cite notes/math/references are appearing as well while highlighting the image\\n\\nSee the screenshot attached.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62681\\n\\n**Attached**: {F13649}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402446768, 'spacePHID': None, 'dateCreated': 1398710700, 'dateModified': 1443278192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64563', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When \"__FORCETOC__\" is set, inside VE instead of \"Hide\" the link to hide the TOC appears as \"<hidetoc>\"', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add Heading\\n3.Add Subheading 1\\n4.Now go to Page Settings and set the option to show the TOC as Always\\n\\nObserved Result:\\nIn the TOC inside VE the link to hide the TOC appears as <hidetoc> instead of Hide\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14029}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398470579, 'spacePHID': None, 'dateCreated': 1398468240, 'dateModified': 1443276201, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64464', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs UI: Menus appearing behind page content in Safari 6.1.3 and 7.0.5 when zoomed in', 'description': {'raw': \"A screenshot indicating where exactly between the VisualEditor toolbar and the content being edited with VisualEditor the 'Insert' menu becomes hidden under such content being edited\\n\\nAs shown in the attached screenshot, attempting to open VisualEditor's 'Insert' menu causes it to open behind the content of the page that you have opened within VisualEditor.  This occurs when VisualEditor is used in Safari 6.1.3 under OS X 10.8.5 'Mountain Lion' when this OS is run on a mid-2007 aluminum iMac with a 2.4-GHz Intel Core 2 Duo processor, 4 GB of 667-MHz DDR2 SDRAM, and an ATI Radeon HD 2600 Pro with 256 MB of dedicated VRAM.  For some reason, though, this bug has been somewhat intermittent over the past month or so (it showed up for a while at first, then appeared as if it had been fixed before whatever patch that fixed it was reverted or otherwise messed with.)  Is my bug a duplicate of another one even though I couldn't find a similar one via Bugzilla's search mechanism?  If so, have there been notices in the comments of this other bug about its status?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Mac OS X 10.9\\n**Platform**: Macintosh\\n\\n**Attached**: {F13846}\"}, 'authorPHID': 'PHID-USER-tulrxb4ebie42howqlxj', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-tulrxb4ebie42howqlxj', 'dateClosed': 1427663532, 'spacePHID': None, 'dateCreated': 1398369840, 'dateModified': 1488318139, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64388', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: In Firefox, the context menu's background sometimes does not appear for items inside a media caption (but the icons appear still)\", 'description': {'raw': 'cite icon not having any layout\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE in Firefox\\n2.Insert a media file\\n3.Now go the media settings for this image\\n4.Add some cite options and reference inside media settings icon\\n\\nObserved Result:\\n\\nJust after adding the cite options and references, observe that the icon layouts for cite options and reference are missing\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13698}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437756412, 'spacePHID': None, 'dateCreated': 1398292980, 'dateModified': 1439331284, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64332', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Input box for template parameters does not handle two-line parameters well in Iceweasel (maybe other browsers?)', 'description': {'raw': 'Template parameter input with one line of text\\n\\nIf I am entering text for a template parameter and then I press enter to start a new line, the input box remains the same (small) vertical size and the first line of text disappears. A very small scroll handle appears at the right, but it is not obvious that this is what it is.\\n\\nPress enter again to add a third line will enlarge the input box so that both the second and third lines are visible, and the dark grey scroll handle disappears (but the light grey slot for it remains. Once it gets to four lines it starts working as expected.\\n\\nThis input box should expand enough with the first few lines, at least, that no scrolling is even necessary. By the time it becomes necessary, it should already be large enough that the scroll handle will be recognizable to users.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13516}'}, 'authorPHID': 'PHID-USER-nyv6rqxnzdy3oe323a3d', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420860386, 'spacePHID': None, 'dateCreated': 1398186840, 'dateModified': 1420860386, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64250', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Need to refresh to see category tree and updated footer on category page', 'description': {'raw': 'Related to bug 48560?\\nIP editor reports that when he removed categories from this category https://it.wikipedia.org/w/index.php?title=Categoria%3AMarketing&diff=65461531&oldid=60402800 , all he could see after he saved was the category description.\\nThe category tree and the list of the categories at the bottom only appeared after refreshing the page.\\n\\nHis setup: Firefox 28.0 , Vector, Windows 7\\nI reproduce the same issue with that setup in this edit: https://it.wikipedia.org/w/index.php?title=Categoria%3AVisualEditor&diff=65497855&oldid=64118006 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401737277, 'spacePHID': None, 'dateCreated': 1398172860, 'dateModified': 1417572291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64239', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Define an official thumb API', 'description': {'raw': 'See also:\\n* {T89971}\\n\\n------\\n\\n\\nMediaWiki never had an official API for the retrieval of thumbnailed images. Existing thumb URLs are considered private, and are not designed for use as a public API. Instead, clients are supposed to request a URL individually from the action API. This complicates API design and API response caching whenever the response references a thumb, and makes it difficult to dynamically select image size or quality in a client.\\n\\nThe move to content-based addressing could provide a good opportunity to address this by defining a simple and stable thumb API.\\n\\n### Use cases / problem statement\\n\\n- **Dynamic client-side thumb size / quality selection without extra round-trips**: Clients would like to adapt image size and quality to actual network and device characteristics. Most current techniques for lazy-loading and dynamic resource selection are using JS. Having the ability to select the thumb size and quality in this code without extra round-trips would enable interesting performance optimizations.\\n\\n- **Caching of API responses referencing thumbnails**: Many cached API responses (such as [summary](https://rest.wikimedia.org/en.wikipedia.org/v1/?doc#!/Page_content/get_page_summary_title) or [related pages](https://rest.wikimedia.org/en.wikipedia.org/v1/?doc#!/Page_content/get_page_related_title)) contain references to thumbnails. Currently, there is no way for clients to sanely select thumb sizes, which means that we either need to fragment caches on thumb size, or try to include several sizes in the response. Good caching of API responses is becoming more pressing as high-traffic features like hovercards (see T70860) are built as direct API consumers. The need to negotiate thumb sizes supported by API end points introduces delays, and reduces the design flexibility in clients. \\n\\n- **Image info caching**: Parsoid and other clients like VisualEditor currently need to request image information in order to render thumbnails. Those requests are very common, making imageinfo one of the most-used API entry points. Currently, the request necessarily contains the desired thumb size, which renders caching of imageinfo responses ineffective. If the response was dimension-independent instead, most of these responses could be served directly from caches. This would reduce response latency and load on the API cluster and related infrastructure.\\n\\n### API requirements\\n\\n- Simple selection of thumb size and -quality without a need for extra API calls.\\n- Avoid cache fragmentation with deterministic URLs.\\n- Support for encoding complex options in a uniform and extensible manner, without breaking existing use cases or introducing non-determinism.\\n- Optional support for content negotiation (ex: client hints) in the future.\\n- Support migrating to hash-based image identification in a later stage.\\n\\n## API proposal: Use query strings\\n\\n- `/v1/someimage.jpg`: Original. Returned by API end points referencing thumbnails. \\n- `/v1/someimage.jpg?w=220`: JPG thumb 220px wide. \\n- `/v1/someimage.jpg?p=22&w=500`: 500px thumb of page 22 in a multi-page document.\\n- `/v1/someimage.jpg?t=2m30s\\ufeff&w=220`: Thumb of a video at 2m30s.\\n- `/v1/someimage.jpg?lang=fr\\ufeff&w=220`: Thumb of an SVG, rendered to a PNG using French texts. We aren\\'t explicitly mentioning the file format, so the client does not need to know that the original is an SVG, or that it is rendered to a PNG image.\\n\\nServer side requirements:\\n\\n- Audit and document the [existing query string API](https://commons.wikimedia.org/w/thumb.php?f=Camera2_mgx.svg&w=100&lang=fr) in [thumb.php](https://github.com/wikimedia/mediawiki/blob/master/thumb.php). T153497\\n- Add strict parameter validation. Each thumb should have only a single URL. Don\\'t allow unknown parameters, and (generally) avoid specifying default values explicitly. Exceptions can be made for page & time offset parameters, where little actual fragmentation is expected, and consistency in the use of the parameter is important.\\n- Query string order normalization in Varnish (vmod): T138093\\n\\n### Providing original dimensions to clients\\n\\nIn order to accurately calculate and select thumbnail dimensions, clients need to know the original image\\'s dimensions (where applicable). Using this informations, clients can then construct a unique URL for a given thumbnail size, independent of the constraints it applied to select this size. They can also avoid content jumping around by updating image dimensions to the exact thumbnail dimensions, before the thumbnail has loaded. \\n\\nCurrently, MediaWiki already provides original dimensions in `data-file-{width,height}` attributes for MediaViewer\\'s benefit. Some API responses referencing thumbnails include the equivalent information in JSON:\\n\\n```\\nimage: {\\n  src: \"/2fd4e1c67a2d28fced849ee1bb76e7391b93eb12\",\\n  width: 640,\\n  height: 480\\n}\\n```\\n\\nWe can either stick to these different formats, or consider unifying this information in the URL, either in query parameters (**`/someimage.jpg?oh=768&ow=1024&w=100`**), or separately in a fragment (**`/someimage.jpg?w=100#oh=768&ow=1024`**). The latter avoids sending back purely informational parameters to the server.\\n\\n\\n### Pros\\n\\n- Familiar query string syntax with wide parsing support.\\n- Does not distinguish between advanced & frequently changed properties.\\n\\n### Cons\\n\\n- Requires custom ordered query string serialization code for both simple (size, quality) & more complex use cases.\\n  - Subtlety of ordering requirement (still works) means that users will often ignore it, causing client side cache fragmentation.\\n- Need for general query string normalization in Varnish. Weak con, as this would be generally useful.\\n\\n## Options for content negotiation and -selection\\n\\nWe would like to use modern thumbnail formats where this has a benefit for users, but need to make sure that we don\\'t break older clients with insufficient support in the process.\\n\\nThe two main approaches for this content negotiation process are: \\n\\na) Server-side HTTP content negotiation, using client supplied headers like `accept`, and\\nb) client-side JS explicitly requesting specific formats.\\n\\nThere are pros & cons to either method, and they aren\\'t mutually exclusive. HTTP content negotiation can work without any client-side effort for bitmap formats (ex: Chrome advertises WebM support). Client side JS can add explicit parameters for more fine-grained control, but also has only limited information to base such decisions on.\\n\\nEither way, the status quo and starting point is to serve widely supported formats (JPG and PNG) by default. We don\\'t need to solve this question right away, and the proposed API is leaving all options for content negotiation open.\\n\\n## Deployment strategy\\n\\nA change like this isn\\'t complete without a strategy that allows us to roll out new-style thumbs gradually. To avoid performance impacts, all (simple) requests for a thumb of a given size should map to the same cache entries using either URL scheme. To this end, we can roll things out in a way that lets us *rewrite* one URL scheme to the other.\\n\\n- New to old style:\\n\\n  - Simple thumbs (only width parameter specified):\\n    1) Prefix the image name with the width parameter value followed by \\'px-\\'.\\n    2) Calculate the MD5 of the image name, and prefix first & first two chars of hex encoding to path (ex: `/7/72/`).\\n  - Complex thumbs: Let PHP code handle the request & cache the response separately.\\n- Old to new style:\\n  - Simple thumbs (need to check if we can determine this with a regex):\\n    1) Extract & strip width parameter\\n    2) Send a request with a query string to backend\\n  - Complex thumbs: Let PHP code handle the request & cache the response separately.\\n\\n\\n### Users / apps making assumptions about the current thumb URL format\\n\\nSee T153498.\\n\\n### Migration strategies in Varnish\\n\\n- Feasibility of rewriting majority of \"simple\" thumbnails (no key-value parameters) in Varnish.\\n- Feasibility of avoiding redirect latency penalty by resolving redirect responses from thumb service in Varnish.\\n\\n## Small MediaWiki installs\\n\\nCurrently, MediaWiki defaults to serving thumbnails directly from an upload directory. This means that there is no PHP code involved in serving thumbnails. This is good for performance (especially without caching), but also means that on-demand generation & a parameter-based API cannot be supported out of the box. There are several options we can pursue:\\n\\n1) Start to serve all thumbs through thumb.php (or an API module). The migration to this would generally be easy (especially with the API), but we would add the overhead of serving thumbs through PHP. Authentication would be supported out of the box. Caching could eliminate the performance issue for higher volume installs, or in an appliance container install that includes Varnish.\\n2) Create a new way of supporting direct file serving with 404 handler and storage based on encoded query strings. This requires an advanced web server configuration, and might not be possible with less common web servers.\\n\\nAt this point, the default option would be 1), but we can always optimize the setup with 2). We can provide 2) by default in a container-based distribution solution.\\n\\n\\n'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1398126240, 'dateModified': 1719943100, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64214', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't bind the 'v' accesskey for VisualEditor in namespaces where VE is not enabled\", 'description': {'raw': 'Visual editor adds accesskey \\'v\\' for visual edit in namespaces where the editor is not enabled. For example (in Firefox) pressing alt+shift+v in [[sv:Diskussion:Stockholm]] shows the error message:\\n\\n\"Error loading data from server: novenamespace: VisualEditor is not enabled in namespace 1. Would you like to retry?\"\\n\\nIt should be possible to avoid getting an error message by removing the access key. (Also, if Visual editor is not enabled there is no point in asking users to retry.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-axibsactcdotqkfh3mfe', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400522015, 'spacePHID': None, 'dateCreated': 1397938920, 'dateModified': 1443278192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64142', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor extension on AffCom wiki', 'description': {'raw': '**Author:** `admin`\\n\\n**Description:**\\nGreetings,\\nPlease add the VisualEditor extension - and any related elements - to the AffCom wiki (chapcom.wikimedia.org).\\n\\nThank you!\\n-greg aka varnent\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-tbsqok4i4d2fpoef36s2', 'dateClosed': 1433053732, 'spacePHID': None, 'dateCreated': 1397915580, 'dateModified': 1433071217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64134', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support editing <div>s with mw:ExpandedAttrs due to a template in their style', 'description': {'raw': 'Div tags like the ones seen in https://meta.wikimedia.org/wiki/Grants:IdeaLab cause \"alienated content\"/prevent people from editing the page.  VisualEditor should support div tags.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1397572320, 'dateModified': 1652133852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63941', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Existing non-positional metas (like categories) get wrapped in format changes, but new ones get appended in a terminal paragraph', 'description': {'raw': 'Steps to reproduce:\\n* go to https://test.wikipedia.org/wiki/Page466?veaction=edit\\n* select the whole article content (Ctrl + A)\\n* from the format menu, select one of the options (except \"Paragraph\")\\n* go to \"Save page\" > \"Review your changes\"\\n\\nNo matter if you selected \"Heading\", \"Preformatted\" or something else, all existing categories would get that format. So one can accidentally put a category in a header.\\n\\nHowever, if you add one or more categories in VE using the dedicated menu, then (without saving) repeat those steps, you will see that the newly added categories are left out of the formatting change.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://test.wikipedia.org/w/index.php?diff=197978'}, 'authorPHID': 'PHID-USER-je4a7kqdfgacwkyhtg4c', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1397524380, 'dateModified': 1416792069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63929', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid and Tidy differ in how they deal with misnested tags', 'description': {'raw': 'I edited https://www.mediawiki.org/w/index.php?title=MediaWiki-Vagrant&oldid=946962 with VisualEditor.  Everything after the \"Quick Start\" section appeared in monospace.\\n\\nI repro\\'d with the smaller test page https://www.mediawiki.org/wiki/User:S_Page_(WMF)/VE_span_bug\\n\\nI think the issue lies in\\n\\n <p style=\"font-size: 1.2em; margin-top: 1.2em;\">When Vagrant is done configuring your machine, browse to <span class=plainlinks>http://127.0.0.1:8080/</span> to find your MediaWiki instance. The admin password is <code>vagrant<code>.</span>\\n\\nNote its incorrect second opening <code> instead of closing the code, and a second closing </span>. Yet regular wiki parsing can handle it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/User:S_Page_(WMF)/VE_span_bug'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1513635415, 'spacePHID': None, 'dateCreated': 1396988880, 'dateModified': 1523588947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63699', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fatal \"SCRIPT16389: Unspecified error\" error in IE9', 'description': {'raw': 'Turning on debugging in IE9 and then hitting \"Edit\" ends up with this in the console:\\n\\n  SCRIPT16389: Unspecified error. \\n  load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cdata%2Cicons-\\n  vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&\\n  version=20140408T180250Z&*, line 642 character 159\\n\\n\\nThe line that is highlighted (running with \"Format JavaScript\" checked) is:\\n\\n  this.nativeSelection.addRange(getNativeRange(range).cloneRange());\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1461148432, 'spacePHID': None, 'dateCreated': 1396985820, 'dateModified': 1461597362, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63697', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Newly inserted inline templates do not take annotations from the surrounding text', 'description': {'raw': 'When adding templates such as https://fr.wikipedia.org/wiki/Mod%C3%A8le:E (which adds a superscripted \"e\" to words), the letter will need further formatting to match the surrounding text if that is italic, bold, ... .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1396954980, 'dateModified': 1579632517, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63670', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Update integration to cope with the new \"view on <repo>\" tabs on file pages', 'description': {'raw': '1. Log in at http://en.wikipedia.beta.wmflabs.org\\n2. Enable VE\\n3. Visit http://en.wikipedia.beta.wmflabs.org/wiki/File:ButtonsReversed.png\\n   (or any foreign file with no local description page)\\n\\nYou see the following views (tabs):\\n    Read\\n    View on Wikimedia Commons\\n    Create source\\n    Add local description ^beta\\n\\n4. Visit http://en.wikipedia.beta.wmflabs.org/wiki/File:Button_hover.svg\\n   (or any foreign file with an existing local description page)\\n\\nYou see:\\n    Read\\n    View on Wikimedia Commons\\n    Edit source\\n    Edit local description ^beta\\n    View history\\n\\nThe tab name \"Create/Edit source\" does not sit well next to \"Add/Edit local description ^beta\". The wikitext-editing tab needs a better name when viewing foreign files.\\n\\nAdmittedly these tabs were altered in core [1] without consulting the VE people, but of course, it is the responsibility of extension authors to catch up to new core functionality.\\n\\n[1] Gerrit change 104182\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397243567, 'spacePHID': None, 'dateCreated': 1396949940, 'dateModified': 1443276231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63666', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Double clicking nodes should open them, but it's not working for hieroglyphics\", 'description': {'raw': 'This is related to bug 50996.\\n\\nOpen a page that contains hieroglyphics, like https://www.mediawiki.org/w/index.php?oldid=942532#Hieroglyphics\\n\\nYou should be able to open the hieroglyphics \"node\" by double-clicking, but it isn\\'t working.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396987666, 'spacePHID': None, 'dateCreated': 1396903680, 'dateModified': 1443276230, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63651', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing Escape or Tab in an empty line inserts pawn symbol (♙) in Opera 12', 'description': {'raw': '**Author:** `richlv`\\n\\n**Description:**\\nvisual editor from git f8d56e6804a12248b485c2d3b49d4ff0ffa7220c\\n\\nedit a page with opera 12.16 on linux, place cursor on an empty line, hit \\'esc\\' - \\nsymbol ♙ is inserted.\\n\\nbug #51140 was about this symbol being inserted in a different situation and is supposed to be fixed.\\n\\nreproducible at https://www.zabbix.org/wiki/Docs/visual_editor_test (if you would like to create a test account, \"real name\" is mandatory)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404383583, 'spacePHID': None, 'dateCreated': 1396884180, 'dateModified': 1443278192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63630', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor : {{FULLPAGENAME}} in <newarticletext> replaced by “API”', 'description': {'raw': \"Both enwiki and frwiki (at least) use {{FULLPAGENAME}} in [[MediaWiki:newarticletext]], which is unusable, because it is replaced by “API” in VisualEditor.\\n\\nSo the warnings contain texts like\\n — “You can also start your new article at Special:Mypage/API.” (https://en.wikipedia.org/wiki/Nawak?veaction=edit)\\n — “Comment faire pour créer l'article API ?” (https://fr.wikipedia.org/wiki/Nawak?veaction=edit)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=59608\"}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397879871, 'spacePHID': None, 'dateCreated': 1396819500, 'dateModified': 1441911939, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63600', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Some icons need to be flipped for RTL languages', 'description': {'raw': \"Some icons need to be flipped for RTL languages. Here's what I found till now:\\n\\nIn lib/ve/lib/oojs-ui/images/icons:\\n* help.svg - This is a question mark in a circle. This should be flipped for all RTL languages, but *not* for Hebrew (he) and Yiddish (yi).\\n\\nIn lib/ve/modules/ve/ui/styles/images/icons:\\n* external-link.svg\\n\\nIn modules/ve-mw/ui/styles/images/icons:\\n* gallery.svg\\n* parameter.svg\\n* parameter-set.svg\\n* ref-cite-book.svg\\n* ref-cite-journal.svg\\n* ref-cite-news.svg\\n* reference.svg\\n* references.svg\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417566229, 'spacePHID': None, 'dateCreated': 1396793460, 'dateModified': 1438734944, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63593', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf21] Math inspector is not opening up', 'description': {'raw': 'Try to open math inspector, it does not open up.\\nNot showing any error in the console\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397086640, 'spacePHID': None, 'dateCreated': 1396636260, 'dateModified': 1443276233, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63541', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Update styling of the MW format paragraph menu to match changes to Vector', 'description': {'raw': 'It would be nice if the new typography (e.g. serifed fonts for headlines) were reflected in VisaulEditor\\'s \"format paragraph\" menu.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63985'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398975131, 'spacePHID': None, 'dateCreated': 1396635960, 'dateModified': 1443278196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63540', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"mediawiki.util: Deprecate mw.util.$content in favor of mw.hook( 'wikipage.content' )\", 'description': {'raw': \"`mw.util.$content` from module `mediawiki.util` seems to be needless.\\n\\n```lang=js\\n\\t$( function () {\\n\\t\\tmw.util.$content...\\n\\t} );\\n```\\ncan be replaced by\\n```lang=js\\n\\tmw.hook( 'wikipage.content' ).add( function ( $content ) {\\n\\t\\t$content...\\n\\t} );\\n```\\n`mw.hook()` is necessary to support [[https://www.mediawiki.org/wiki/Manual:Live_preview|Live Preview]].\"}, 'authorPHID': 'PHID-USER-3dmql6z7s5lnn5lu2vs3', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1396517640, 'dateModified': 1710039243, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63466', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Vector: Headings have excessive top margin when used as first element in a content container', 'description': {'raw': \"Screenshot of excessive whitespace on top of an in-content dialog with h2 heading\\n\\nSince inner padding of the dialog container and top margin of the header don't collapse, they get stacked and now have an excessive amount of whitespace (see screenshot).\\n\\nThe margin-top of 'div#content h2' should be safe to remove. We didn't have it in the past, and in any regular text flow context it is already spaced away from the preceding element by the bottom margin of block level elements (like paragraphs and tables).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63312\\n\\n**Attached**: {F13341}\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403031035, 'spacePHID': None, 'dateCreated': 1396381920, 'dateModified': 1469893978, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63390', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Adding content to an empty table cell written in inline form results in the serialised wikitext being in the one-cell-per-line format', 'description': {'raw': 'Intention:\\nAdd a value to an empty cell in a table using VE\\n\\nSteps to Reproduce:\\n1. You need a page with a table with at least one empty cell (e.g. https://en.wikipedia.beta.wmflabs.org/wiki/User:ESanders_(WMF)/sandbox/T65356)\\n2. Open page for VE editing\\n3. Double click on the empty cell, then add some text\\n4. Show the wikitext diff in the save dialog\\n\\nActual Results:  \\nIn addition to the entered text a line-break is added\\n\\nExpected Results:  \\nNo additional line-break\\n\\nReproducible: Always\\n\\nNote that this does not happen for cells which already contains a value\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1616105928, 'spacePHID': None, 'dateCreated': 1396347240, 'dateModified': 1616105929, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63356', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Double colons when linking to File/Category', 'description': {'raw': 'Intention:\\nLinking to a file using visual editor\\n\\nSteps to Reproduce:\\n1. Edit page on using VE\\n2. Click add link\\n3. Enter a filename with File-prefix (e.g. File:Foo.svg)\\n4. Press enter\\n5. Press enter again\\n\\nThe same thing happens for categories or if the preceding colon is added manually.\\n\\n\\nActual Results:  \\n4. Inserted text is changed to :File:Foo.svg\\n5. Inserted text is changed to ::File:Foo.svg\\n\\nExpected Results:  \\n4. As result\\n5. No change\\n\\nReproducible: Sometimes\\n\\nThe same thing happens for categories or if the preceding colon is added manually. I can get this to happen repeatedly but occasionally VE will correctly know not to add the second colon (have not identified when though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63355'}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403995088, 'spacePHID': None, 'dateCreated': 1396343280, 'dateModified': 1417572132, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63353', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove transclusion node if we were just going to set it to empty content', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Template\\n3.Click on Show Options\\n4.Click on the trash icon.\\n5.Click on \"Add Content\"\\n\\nObserved Result:\\nThe \"Insert transclusion\" button becomes enabled and an empty transclusion with empty content gets added upon clicking on it.\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13225}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414624755, 'spacePHID': None, 'dateCreated': 1396312320, 'dateModified': 1417571680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63341', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Insert Transclusion\"  button becomes enabled after adding a second empty template', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open the transclusion add dialog box by going to Insert>Template\\n3.Click on the \"Show Options\" button\\n4.Now click on the \"Add template\" button\\n\\nObserved Result:\\nThe \"Insert Transclusion\" button becomes enabled and clicking on that does nothing \\n\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13220}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414098890, 'spacePHID': None, 'dateCreated': 1396311480, 'dateModified': 1417571687, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63340', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: There is no keyboard function to exit the Math Inspector and Gallery', 'description': {'raw': 'Right now, there is no keyboard function to exit the Math Inspector and Gallery inspector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402296299, 'spacePHID': None, 'dateCreated': 1396306440, 'dateModified': 1417572236, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63336', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Media selector doesn't find local media in private wiki\", 'description': {'raw': 'The media selector (both in WikiEditor and Visual Editor) does not find local images in a private wiki. When the same wiki is set to public, it works.\\n\\nI\\'ve tried this with 3 different installations (1.22 and 1.23wmf20) on two different servers, both with Visual Editor and WikiEditor. \\n\\nThe relevant setting is\\n\\n$wgGroupPermissions[\\'*\\'][\\'read\\'] = false;\\n\\nWhen this is set to false, when a user (logged in and registered) edits a page and starts typing the name of an existing file in the media selector, the input box remains empty and does not suggest existing file names. \\n\\nWhen the read permission is set to true, then it works as expected (giving a list of suggestions in the input box) - but of course then the wiki is no longer private.\\n\\nOn the other hand, the link selector finds the files when I type \"File:Filename..\". Also, the image is actually shown in the article when I insert it with Wiki markup, or when I type in the correct filename in the selector and click on \"insert\".\\n\\nSo somehow the media selector (but not the link selector) does not understand the permission correctly for a logged-in user.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-mn2oreq3jstq45jm3fp5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416312559, 'spacePHID': None, 'dateCreated': 1396213080, 'dateModified': 1717452855, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63282', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Reference's highlight is misplaced if it appears after a references list block\", 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a Cite reference like Cite>Web/Book/Newspaper/Journal\\n\\nObserved Result:\\nThe selection highlight box is appearing a bit above the reference note\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F12974}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411403567, 'spacePHID': None, 'dateCreated': 1396046220, 'dateModified': 1417571837, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63244', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Quotation marks added via special characters tool should wrap selected text, not replace it', 'description': {'raw': 'Guillemets, French quotation marks (https://en.wikipedia.org/wiki/International_variation_in_quotation_marks#French), are now available through the special characters tool in VE on fr.wiki.\\nWhen you select a word and then add the guillemets in the wikitext editor, the word gets wrapped in them.\\nThis is not the case in VE - the symbols appear, the word gets deleted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429751913, 'spacePHID': None, 'dateCreated': 1396007580, 'dateModified': 1433205573, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63227', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Changing format of a list item right above a nested list item breaks', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with\\n2,Add a bullet list or numbered list\\n3.Add an empty bullet item \\n4.Add indentation to it\\n5.Select the previous item\\n6.Change the paragraph style of the previous item\\n\\n\\nObserved Result:\\nAn error appears in the console\\nUncaught Error: Unbalanced set of replace operations found \\n\\nNow press enter to add another item :\\nUncaught Error: Unbalanced input passed to document \\n\\nPress undo:\\nUncaught Error: Offset could not be translated to a DOM element and offset\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/27thmarChrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12902}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397140593, 'spacePHID': None, 'dateCreated': 1395962100, 'dateModified': 1443276239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63209', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector icon appears after deleting the content of the page and closing the inspector causes an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 65', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open this page: https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox?veaction=edit\\n\\n2.Select all the content \\n\\n3.Delete it.\\n\\n4.A link inspector icon appears in the page.\\n\\n5.Open the link inspector\\n\\n6.Close it \\n\\nObserved Result:\\nThe links inspector gets all blank and an error appears in the console:\\nUncaught Error: Offset could not be translated to a DOM element and offset: 65\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12901}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396299556, 'spacePHID': None, 'dateCreated': 1395959940, 'dateModified': 1443276239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63208', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The link inspector opens after gallery , if there is gallery just after the text on which the link is getting applied', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a text\\n3.Add a gallery right after that.\\n4.Select the text by selecting whole line\\n5.Click on the link inspector\\n\\nObserved Result:\\nThe link inspector opens after the gallery \\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/27thmarChrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12878}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402553191, 'spacePHID': None, 'dateCreated': 1395952200, 'dateModified': 1441911946, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63200', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor by default on French Wiktionary and French Wikibooks', 'description': {'raw': 'Consequently to the success of VisualEditor on the French Wikipedia and Wikiversity, the French Wiktionary and Wikibooks have voted in favor of its utilization:\\n\\nhttps://fr.wiktionary.org/wiki/Wiktionnaire:Prise_de_d%C3%A9cision/Installation_de_l%27%C3%A9diteur_visuel\\n\\nhttps://fr.wikibooks.org/wiki/Wikilivres:Prise_de_d%C3%A9cision/Installation_de_l%27%C3%A9diteur_visuel\\n\\nSo, thank you to deploy it on fr.wikt and fr.b please.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-dtdj4p6jtxbzs7trc3c6', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396021903, 'spacePHID': None, 'dateCreated': 1395927360, 'dateModified': 1580068354, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63187', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parameter add icon remains enabled in empty transclusion dialog box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Transclusion\\n3.Insert a template for example : The Cite web\\n4.Click on \"Show options\"\\n5.Keep on clicking on trash icon until you delete all the parameters and the template itself\\n\\nObserved Result:\\n\\nObserve that, even if there is no template in the dialog box , the add parameter button remains enabled , it should be disabled if there is o template.\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13393}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414442405, 'spacePHID': None, 'dateCreated': 1395881520, 'dateModified': 1417571682, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63158', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'BetaFeatures: Skin warning message pulls in skin names regardless of whether skin is available', 'description': {'raw': 'On beta features tab in your user preferences http://de.wikipedia.org/wiki/Spezial:Einstellungen?useskin=modern&uselang=de#mw-prefsection-betafeatures visualeditor shows a red requirement warning if the current skin is not supported. But this warning uses not available system messages:\\n\\nThis feature only works with the following skins:\\n    Vector\\n    &lt;skinname-apex&gt;\\n    MonoBook\\n    &lt;skinname-minerva&gt; \\n\\nThe problem on wikimedia wikis is that both skins, apex and minerva, are not installed and so the system messages skinname-apex and skinname-minerva are missing.\\n\\nI think there are two options how to fix this bug:\\n1. add these two messages to localisation files used by wmf\\n2. test if a skin is available before adding it to the skin list of the warning message\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n**URL**: http://de.wikipedia.org/wiki/Spezial:Einstellungen?useskin=modern#mw-input-wpvisualeditor-enable'}, 'authorPHID': 'PHID-USER-rbcxdzszrm6s4izt67kj', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395898645, 'spacePHID': None, 'dateCreated': 1395871980, 'dateModified': 1395898645, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63151', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When API returns HTTP 500, present a more useful error message to the user', 'description': {'raw': \"I don't know what it should be, but the following is not very clear:\\n\\nError loading data from server: error. Would you like to retry?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=39057\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=43147\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409684423, 'spacePHID': None, 'dateCreated': 1395869100, 'dateModified': 1443278196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63149', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Icons for citation tool don't all appear to be the same (visual) weight — the book icon looks darker than the others\", 'description': {'raw': \"The icons for the new citation tool don't all appear to be the same weight.  The book icon looks darker than the others, which makes it seem like it's more important than other others, or perhaps that the others are non-functional/grayed out.  Perhaps it could be a dark gray?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-flenunkasbjk4topxvaj', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401472252, 'spacePHID': None, 'dateCreated': 1395859980, 'dateModified': 1443278196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63130', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Citation tool adds stray line break at the end of the template', 'description': {'raw': 'Intention:\\nAdd a citation with the new citing tool\\n\\nSteps to Reproduce:\\n1. Add a citation.\\n\\n2. Look at the dirty diff that results.\\n\\n\\n\\nActual Results:  \\nThe new cite tool produces this\\n\\n<ref>{{Cite web|url = http://example.com|title = Example Title|date = 2014|last = Expert|first = Alice}}\\n</ref> \\n\\n(on two lines) rather than one line that it should:\\n\\n<ref>{{Cite web|url = http://example.com|title = Example Title|date = 2014|last = Expert|first = Alice}}</ref> \\n\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399336298, 'spacePHID': None, 'dateCreated': 1395859560, 'dateModified': 1443278199, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63128', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor removes a colon from the first existing indented list item when adding another item to the list', 'description': {'raw': 'When adding an item to a list, VisualEditor is stripping the first indent (colon in wikisyntax) when adding a new one in the list.\\n\\nExample:\\nhttps://www.mediawiki.org/w/index.php?title=User%3AKeegan_%28WMF%29%2Fsandbox&diff=939610&oldid=939609\\n\\nSteps to reproduce:\\n1. Create an indented list, save\\n   :*a\\n   :*b\\n   :*c\\n2. Add a new item to the list, looks fine before saving\\n   :*a\\n   :*b\\n   :*q\\n   :*c\\n3. Save, and the result is\\n   *a\\n   :*b\\n   :*q\\n   :*c\\n\\nWindows 7/Chrome 33.0.1750.154 m & Firefox 28.0\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1625945177, 'spacePHID': None, 'dateCreated': 1395768720, 'dateModified': 1625945177, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63079', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Long parameter names get hidden under their input fields', 'description': {'raw': 'This happen when you\\'re editing a template, or, if you\\'re just adding it instead, once you add the parameter as well.\\nFor example of very long names try to change Infobox settlement in https://en.wikipedia.org/wiki/Ames,_Iowa?veaction=edit .\\nSince some of these parameters only differ at the very end, like Fram noted, the user can be confused when seeing what is apparently the same parameter just repeated. Some of them also lack a description, so the description alone wouldn\\'t solve the problem.\\nWhile he suggests that \"a pop-up that displays the full name may be some initial solution\", I think adjusting the character size or window size might work better.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402553952, 'spacePHID': None, 'dateCreated': 1395754800, 'dateModified': 1443276245, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63065', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid should not replace namespace aliases by other translations', 'description': {'raw': 'See reproduction below\\n```\\n[subbu@earth:~/work/wmf/parsoid] cat /tmp/wt\\n[[Imagem:Ellipse PLS en.png|256px|thumb|Parâmetros de uma elipse.]]\\n[subbu@earth:~/work/wmf/parsoid] php bin/parse.php --wt2wt < /tmp/wt\\n[[Imagem:Ellipse PLS en.png|256px|thumb|Parâmetros de uma elipse.]]\\n\\n[subbu@earth:~/work/wmf/parsoid] php bin/parse.php --domain pt.wikibooks.org < /tmp/wt > /tmp/old.html\\n[subbu@earth:~/work/wmf/parsoid] cp /tmp/old.html /tmp/new.html\\n\\n... edit new.html and change the image ...\\n\\n[subbu@earth:~/work/wmf/parsoid] php bin/parse.php --domain pt.wikibooks.org --html2wt < /tmp/new.html \\n[[Ficheiro:Ellipse_PLS_en.snv|256px|thumb|Parâmetros de uma elipse.]]\\n```\\n\\n----------\\nOn this edit\\nhttps://pt.wikibooks.org/wiki/Matem%C3%A1tica_elementar/Trigonometria/Arcos_e_%C3%A2ngulos?diff=270018\\nVisualEditor replaced the good namespace \"Imagem\" by \"Ficheiro\", which is worse.\\nThe word \"Ficheiro\" is not appropriated here:\\n* It is not used in the pt-BR variant, so per discussion in the community it should be avoided whenever it is possible[1][2]. And it is always possible to be avoid this word if the file is an image (because \"Imagem\" is a common word in pt-BR and pt-PT);\\n* It replaced a precise description of the file by a generic one. There is nothing wrong in saying that \"Foo.PNG\" is a image.\\n\\n[1] https://pt.wikipedia.org/wiki/WP:Esplanada/propostas/Incentivar_o_uso_de_%22Imagem%22_em_vez_de_%22Arquivo%22_ou_%22Ficheiro%22_(12mar2011)\\n[2] http://sourceforge.net/p/pywikipediabot/bugs/1323/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395750540, 'dateModified': 1589581274, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63060', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing delete on an indented list item does not unindent it rather merges it with the previous item in a numbered list', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a numbered or bullet list\\n3.Edit the first item of the list\\n4.Add indentation to it\\n5.Place the cursor just before the list\\n6.Press delete\\n\\nObserved Result:\\nInstead of unindenting it, it rather merges it with the previous line .\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage: https://test2.wikipedia.org/wiki/24thmarchrome?veaction=edit\\n\\n**See Also**: {T63863}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395707640, 'dateModified': 1642378712, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63051', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Trying to insert anything in the slug inside a media dialog box throws Uncaught Error: Offset could not be translated to a DOM element and offset: 63', 'description': {'raw': 'screenshot 1\\n\\nSteps to reproduce:\\n\\n1.Go to the media settings of an image\\n2.Create a slug \\n3.Try to insert a special character/link/reference in the slug\\n\\n\\nObserved Result:\\n\\nIt shows an error in the console: Uncaught Error: Offset could not be translated to a DOM element and offset: 63\\nAlso if it is an inspector it goes all blank\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\n: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/24thMarchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13082}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413415239, 'spacePHID': None, 'dateCreated': 1395688860, 'dateModified': 1417571686, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63025', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Gallery code gets added in the Table of Content and gets overlapped with the next item in the VE mode', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:]\\n\\n\\n1.Open a page with VE\\n2.Select the whole line just preceding a Heading\\n3.Insert a gallery with some invalid code: for example:\\n\\n\\nAn example image. It has flowers and flowers It has flowers and flowersIt has flowers and flowersIt has flowers and flowersIt has flowers and flowersIt has flowers and flowers\\n\\n\\nObserved Result:\\n1. The text inside gallery inspector gets overlapped with the heading \\n2. After saving you will see the gallery code got inserted in the TOC \\n3.The heading got converted to paragraph format\\n4.The gallery code is appearing just beside the heading in paragraph format ( in addition to appearing inside the gallery)\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Newpagetocheck62934\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12890}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395444300, 'dateModified': 1416846415, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62943', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"It should be possible to specify that APIs are internal and shouldn't be documented in api.php's output\", 'description': {'raw': \"For example, action=visualeditor is an internal API for the VisualEditor client to talk to its server, isn't really useful for third parties, and isn't remotely stable. However, because it's a built-in assumption that APIs are for third-party use rather than every tool being the first client of its API, this isn't possible. Boo.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-uqcn2l4ng4murmyfnvyp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413239512, 'spacePHID': None, 'dateCreated': 1395361800, 'dateModified': 1710457249, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62905', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image flickers but shield stays in the correct position while dragging the page on Mac', 'description': {'raw': 'Steps to reproduce:\\n\\nIf you drag a page down which contains an image large enough to go beyond the border of developer tool and has the developer tool open ,the image seems to flicker and appear again while the shield stays in the same position.\\n\\nTry this page.\\nSee the Video Capture attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404851230, 'spacePHID': None, 'dateCreated': 1395359220, 'dateModified': 1424894573, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62898', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Small default sized SVG images behave differently than small default sized PNG images', 'description': {'raw': 'screenshot attached\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a small default sized SVG image for example a SVG image with 50x50px :https://en.wikipedia.org/wiki/File:Gnome-fs-home.svg\\n\\n3.Now Save the page\\n\\nObserved Result:\\nThe image size that appears after saving is much larger (200x200px) \\n\\nSee the screenshot attached.\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65\\nPage:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/sandbox\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13403}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401927904, 'spacePHID': None, 'dateCreated': 1395351720, 'dateModified': 1417572219, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62893', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make available original image dimensions info from the API in Parsoid DOM.', 'description': {'raw': \"Since Parsoid already runs an API call for each image given to it in wikitext, it would be extremely helpful for the editing in terms of user experience if the call also asked for the original dimensions.\\n\\nAt the moment, VisualEditor asks for details from the API on each edited image to get its original dimensions. When this is done for the edit dialog the asynchronous call works fine because we don't mind letting the user wait the seconds it takes the async call to finish.\\n\\nBut when the user resizes images with the mouse (with the resize handles) the information about original dimensions usually comes too late. The user may (and often does) resize the image to above its limits, and by the time VE gets the API response, the user is already done resizing. On top of that, calculating aspect ratio from original size is a lot more accurate than calculating it from the given (usually smaller) size, though, granted, this is a lot less crucial.\\n\\nWe have some fall backs and we are considering an after-the-fact user experience ideas to make this work, but it would be extremely helpful if the information was already available when it comes from Parsoid -- especially since Parsoid already asks for information from the API.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1427414277, 'spacePHID': None, 'dateCreated': 1395339300, 'dateModified': 1442426448, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62881', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save dialog animates size while animating open if it was large when it was closed', 'description': {'raw': \"1. Open save dialog. It animates normally to small size.\\n2. Click Review changes. Dialog animates to medium size.\\n3. Close dialog.\\n4. Open dialog again.\\n\\nWhen the dialog opens again, it's still medium size from last time, which we animate back to small. But this animation is concurrent with the scale 0.5->1.0 opening animation, and the result of the two animations combined is pretty strange-looking.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402551181, 'spacePHID': None, 'dateCreated': 1395279120, 'dateModified': 1443278199, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62859', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector opens up in the wrong place after inside Media Settings dialog', 'description': {'raw': 'screenshot-1\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image \\n3.Go to Media Settings>General Settings \\n4.Click outside the caption textbox\\n5.Click on link inspector icon\\n\\nObserved Result:\\nThe link inspector opens outside the textbox.\\nSee the screenshot attached\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nChrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13306}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402549198, 'spacePHID': None, 'dateCreated': 1395274860, 'dateModified': 1441911953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62857', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf18] Making an image Right, Basic and Border does not include the Right and Border in the wikitext', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Now change the image settings to Right,Basic and Border \\n3.Save the page\\n\\nObserved Result:\\nIn the wikitext the options \"Right\" and \"Border\" are missing\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\n: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400903430, 'spacePHID': None, 'dateCreated': 1395266640, 'dateModified': 1443278200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62852', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Centre floated image next to right floated image means image is shown partially offscreen, and shield is put in the wrong place', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\nThis issue was found specifically on this page for the second image:\\n\\nhttp://en.wikipedia.beta.wmflabs.org/wiki/19thMarChrome?veaction=edit\\n\\nThe original settings for the image was Right,Basic and Border.\\n\\nWhen I changed the image position to \"Centre\", it appeared distorted with irregular highlight box for the image\\n\\nSee the screenshot attached:\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\n: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62590\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66228\\n\\n**Attached**: {F13287}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395265200, 'dateModified': 1425264503, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62850', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create infrastructure for creating annotations/nodes from the UI', 'description': {'raw': \"Right now, MWLinkInspector needs to know exactly how to construct a new link annotation with the right attributes. This pattern is repeated (albeit somewhat less egregiously) for every single annotation and node created by any UI component anywhere. This is horrible. The DM should provide helpers so UI classes can much more easily create linmod elements from data.\\n\\n----\\n\\nUpdate, 2015-08-25: We now have a bespoke method for the MW link inspector, but the general pattern across VE's UI is still there.\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395194460, 'dateModified': 1453508875, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62816', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Extract red link API code from VE and put into Parsoid', 'description': {'raw': 'Duplicated logic is bad.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1554948839, 'spacePHID': None, 'dateCreated': 1395179580, 'dateModified': 1554948849, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62803', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Slugs don't animate when jumping from one to another\", 'description': {'raw': \"1. Create a page with just a table\\n2. Focus the top slug (it animates)\\n3. Focus the bottom slug\\n\\nExpected:\\nTop slug collapses, bottom slug expands\\n\\nObserved:\\nNothing\\n\\nThe logic for adding animation classes only checks to see if we've gone from in a slug to not in a slug, so we'll need to check if the slug has changed as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395164454, 'spacePHID': None, 'dateCreated': 1395150300, 'dateModified': 1443276249, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62783', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The Save dialog box prompts to fill out a new captcha if a user goes to review changes section and switches back after filling out the captcha field for the first time', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an external link in the VE so that it prompts to enter a captcha \\n3.Click on the Save Page button\\n4.Click on the Save Page button on the Save dialog\\n5.Fill up the textbox for the captcha\\n6.Click on \"Review Your Changes\"\\n7.Return to the save form\\n\\n\\nObserved Result:\\nIt again asks you to fill up a new captcha\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398882077, 'spacePHID': None, 'dateCreated': 1395106620, 'dateModified': 1443276252, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62766', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Improve VisualEditor's performance on tablet devices\", 'description': {'raw': 'Kenan reports some sluggishness on iPads, and will update this bug with more details.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1534438142, 'spacePHID': None, 'dateCreated': 1395094920, 'dateModified': 1534438142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a clean interface for rendering detached CE nodes', 'description': {'raw': \"In ve.ce.MWTreferenceListNode we do something quite evil, which is creating a one-off CE node, adding it's $element to the DOM, then destroying it. This happens to work because destroy doesn't abort async rendering processes, but in the future this may change. It's also quite messy to do things this way, and all we really need is a simple way to get a rendering from a model.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1580721921, 'spacePHID': None, 'dateCreated': 1394842740, 'dateModified': 1580721921, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62682', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The image highlight box is not getting redrawn properly while changing image type to thumbnail/frame', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Add a caption to it\\n3.Save the page \\n4.Reopen the page\\n5.Go to the Media Settings of that image and change the image type to thumbnail/frame\\n\\n\\nObserved Result:\\nThe image highlight box does not appear properly, caption also gets missing\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/14thmarchwmf18\\n\\nTry the image in this page\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64563\\n\\n**Attached**: {F12893}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404851133, 'spacePHID': None, 'dateCreated': 1394842020, 'dateModified': 1424894573, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62681', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Make CE-surface fixes to make TMH's media items display correctly\", 'description': {'raw': \"Moved out of bug 38129's wishlist into its own bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1538513853, 'spacePHID': None, 'dateCreated': 1394835240, 'dateModified': 1538513865, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62678', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Be able to set a non-image multi-paged item's display page (page=) in the media dialog\", 'description': {'raw': \"Moved out of bug 38129's wishlist into its own bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394834880, 'dateModified': 1686934747, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62673', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Be able to set an item's size in upright terms in the media edit dialog\", 'description': {'raw': \"Moved out of bug T40129's wishlist into its own bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394834700, 'dateModified': 1692558939, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62671', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: An Undefined parameter appears in the template dialog box after clicking on \"Add parameter\" but not adding any new parameter', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a template\\n3.Click on Add Parameter\\n4.But do not add any parameter just click on \"Apply Changes\"\\n5.Reopen the template\\n\\nObserved Result:\\nAn undefined parameter appears inside the template dialog box\\n\\nSee the screenshot attached\\n\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage: https://en.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F13443}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395293488, 'spacePHID': None, 'dateCreated': 1394744880, 'dateModified': 1443276253, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62621', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MediaWiki <source>  used between text nodes should render block instead of inline-block', 'description': {'raw': 'Screenshot of MediaWiki rendering\\n\\nWikitext:\\n\\n=== Example ===\\nFoo <code>bar</code> baz.\\nYou\\'ll want to add <source lang=\"javascript\">\\n        \"predef\": [\\n                \"OO\",\\n        ]\\n</source> x y.\\n\\n\\nIn MediaWiki\\'s PHP parser:\\n\\n  <h3>..</h3>\\n  <p>Foo <code>bar</code> baz.</p>\\n  <p>You\\'ll want to add</p>\\n  <div> .. syntax highlgiht ..\\n  <p>x y.</p>\\n\\nIn Parsoid:\\n\\n  <h3>..</h3>\\n  <p>Foo <code>bar</code> baz.</p>\\n  You\\'ll want to add\\n  <div> .. syntax highlgiht ..\\n  x y.\\n\\nNotice the lack of paragraphs from the Parsoid DOM, though this is odd, it still renders fine visually in browsers.\\n\\nIn VisualEditor:\\n\\n  <h3 class=\"ve-ce-branchNode\">Naming</h3>\\n  <p class=\"ve-ce-generated-wrapper ve-ce-branchNode\">\\n    You\\'ll want to add&nbsp;\\n    <span class=\"ve-ce-leafNode ve-ce-generatedContentNode ve-ce-mwExtensionNode ve-ce-mwAlienExtensionNode ve-ce-protectedNode\" contenteditable=\"false\">\\n      <div dir=\"ltr\" class=\"mw-geshi mw-code mw-content-ltr\" typeof=\"mw:Extension/source\" data-mw=\"..\" about=\"#mwt24\">..</div>\\n    </span>\\n    &nbsp;x y.\\n  </p>\\n\\nIt renders as an inline-block within a paragraph, that\\'s where it goes wrong.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13385}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394734980, 'dateModified': 1416846410, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62609', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs UI: Hovering icons makes them jump around 1-2px in Chrome', 'description': {'raw': '* Latest mediawiki and VisualEditor master locally\\n* Chrome incognito\\n* Sandbox?veaction=edit\\n\\nShows:\\n\\n 1 notice                      X\\n ----\\n Warning: You are not logged in.\\n Your IP address will be recorded\\n in this page\\'s edit history.\\n\\nWhen hovering over the [X], the text \"1 notice\" and \"Warning: .. \" go down 1px and then back up again.\\n\\nNot sure what it causing it, could be a browser rendering bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395879396, 'spacePHID': None, 'dateCreated': 1394667060, 'dateModified': 1512598626, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62591', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf18] If you insert an image into the page with default settings, save, then re-open the page without refresh, JS errors on load', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Save the page\\n4.Reopen the page\\n5.Open the media settings for the image \\n\\nObserved Result:\\nThe following error appears in the console and Media Settings dialog box cannot be closed:\\n\\nUncaught TypeError:Cannot read property 'width' of null\\nUncaught TypeError:Cannot call method 'getItemFromData'of undefined.\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=12thmarchchrome\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13283}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394752129, 'spacePHID': None, 'dateCreated': 1394660040, 'dateModified': 1443276255, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62581', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Beat the reference toolbar button in the reference dialog back down into its grave', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page in VE\\n2.Insert a reference\\n3.Open the reference dialog \\n4.Insert another reference inside it\\n5.Save the page\\n\\nObserved Result:\\nIn read mode :Cite error: Closing </ref> missing for <ref> tag appears\\nInside VE: for the reference that is inside another reference, the wikitext appears in the reflist section\\n\\nSee the screenshots attached\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13271}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395295429, 'spacePHID': None, 'dateCreated': 1394653320, 'dateModified': 1443276255, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62575', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'investigate updating test2 Jenkins builds weekly to pull by branch', 'description': {'raw': \"I learned today from Rob Lanphier that it has recently become possible to do this reliably in every extension repo as well as mw core: \\n\\n$ git checkout wmf/1.23wmf17\\n\\n\\nFor example: \\n\\n/VisualEditor$ git checkout wmf/1.23wmf17\\nBranch wmf/1.23wmf17 set up to track remote branch wmf/1.23wmf17 from origin.\\nSwitched to a new branch 'wmf/1.23wmf17'\\n\\nThe current branch of each wiki is tracked in https://git.wikimedia.org/blob/operations%2Fmediawiki-config/HEAD/wikiversions.json\\n\\nThe current branch of core (which should be consistent across all extensions also) is available on https://test2.wikipedia.org/wiki/Special:Version (and theoretically in the API somewhere)\\n\\nIt would be good if we could change our Jenkins builds with test2 as a target to pull the current wmf branch instead of master. \\n\\nIn the short term, we could update the build config manually every Thursday. \\n\\nIn the slightly longer term it should be possible to read Special:Version or the wikiversions.json file in order to determine at run time the proper version of the tests appropriate for test2 (and any other target environment not beta labs, e.g. enwiki or commons)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407233064, 'spacePHID': None, 'dateCreated': 1394483880, 'dateModified': 1407233064, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62509', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Changing the format of a block slug between a list and a block template breaks badly', 'description': {'raw': \"In this page https://fr.wikipedia.org/w/index.php?title=Utilisateur:Elitre_(WMF)/Prove2&oldid=101942635, if you click Enter twice after the last sub-item of the list and then select Titre de section (Heading), that item and the Portal template below disappear, and results from the Undo action may vary (the French user who found this reports that a couple of CTRL+Z blank the page for him; for me, nothing happens, or the item comes back but the template doesn’t). \\nNothing changes if the list is unordered or ordered, but it does seem to matter that it features sub-items and not just items (as a matter of fact I couldn't reproduce with a simple list here http://en.wikipedia.beta.wmflabs.org/w/index.php?title=User:Elitest&oldid=82999).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://fr.wikipedia.org/wiki/Utilisateur:Elitre_%28WMF%29/Prove2?oldid=101942635&veaction=edit\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50250\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1423749922, 'spacePHID': None, 'dateCreated': 1394455740, 'dateModified': 1438734952, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62475', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image as part of the anchor of a link is stripped on round-trip', 'description': {'raw': 'As reported by NicoV on fr.wp, \\nunrelated edits remove the syntax for an image from an external wikilink.\\nSee tests at https://fr.wikipedia.org/w/index.php?title=Utilisateur%3ANicoV%2FTest&diff=101782688&oldid=101782616 , https://www.mediawiki.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandboxVE&diff=924704&oldid=924702 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1608126943, 'spacePHID': None, 'dateCreated': 1394446440, 'dateModified': 1608126944, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62473', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Be able to specify a \"no parameters accepted\" definition', 'description': {'raw': 'Some (many) templates do not use any parameters (e.g., hundreds of templates like https://en.wikipedia.org/wiki/Template:Stub).  However, if you add those templates, VisualEditor will ask you for parameters, just like it does for any other template.  It would be nice to have a TemplateData setting for \"no parameters here, so don\\'t bother asking\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394239320, 'dateModified': 1681234486, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62417', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector opens up in the Alternative textbox inside Media Settings', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE which has an image inside it.\\n2.Now open the Media Settings for the image\\n3.Type something for the Alternative Text\\n4.Select the text and click on the Link Inspector icon \\n\\nObserved Result:\\nThe link inspector opens up in the Alternative text textbox as it appears in the screenshot.However, it does get placed inside the caption textbox\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=59868\\n\\n**Attached**: {F12881}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397600820, 'spacePHID': None, 'dateCreated': 1394234880, 'dateModified': 1443276258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62410', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parameter descriptions in the new template dialog are too low contrast', 'description': {'raw': 'Intention:\\nRead the description from TemplateData\\n\\n\\nActual Results:  \\nThe description of the parameter from TemplateData is too pale.  People with poor eyesight, lower quality monitors, in sunlight on their mobile devices, etc. will not be able to read it.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1486169504, 'spacePHID': None, 'dateCreated': 1394218380, 'dateModified': 1486172196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62397', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"returnto and returntoquery in login/signup links doesn't get updated on pushState or popstate\", 'description': {'raw': \"VisualEditor uses pushState to add veaction=edit to the URL when you click the VE edit tab, without causing a true reload.  However, this does not cause a true reload.  Similarly, when you click Read, the same happens to go back to read mode.\\n\\nUnfortunately, this does not update the returnto and returntoquery in the login and signup links.  So if you click the tab for VE, then go to login and signup in the top right, you will no longer be in VE when you get back.\\n\\nVE could make a custom solution for this, but a general method might be nice.  \\n\\nIt's possible to listen to user-initiated navigation (e.g. back/forward) with the popstate event.  That could solve the problem for back and forward.\\n\\nHowever, that doesn't tell you about pushState.  So perhaps there should be a mw.pushState that updates these links, then calls the underlying browser method.\\n\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394157660, 'dateModified': 1693165528, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62355', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Removing last char from paragraph removes entire paragraph and throws in IE', 'description': {'raw': 'Screenshot of bug (incl. console error)\\n\\nEncountered in IE9 using BrowserStack \"Windows 7/IE9\" using latest MediaWiki and VisualEditor master via a tunnel. Could either be a browser bug we have to work around, or something on our end applicable to other browsers as well.\\n\\n\\n* Put the cursor at the end of the second paragraph in a simple document\\n* Removing the last character (e.g. full stop)\\n\\nIt suddenly removes the entire paragraph and then throws an uncaught exception:\\n\\n> “Offset could not be translated to a DOM element and offset: 112”\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64128\\n\\n**Attached**: {F13344}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1460637744, 'spacePHID': None, 'dateCreated': 1394128260, 'dateModified': 1462842876, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62333', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Uncaught Type: Cannot call method \\'attr\\' of undefined\"', 'description': {'raw': \"When VisualEditor deactivates itself after Parsoid fails, this exceptions thrown because the property never got set.\\n\\n\\n\\n  ve.init.mw.ViewPageTarget.prototype.deactivate = function(override) {\\n    if (..) {\\n      if (..) {\\n        this.deactivating = true;\\n        if (ve.msg('accesskey-save') !== '-' && ve.msg('accesskey-save') !== '') {\\n          this.elementsThatHadOurAccessKey.attr('accesskey', ..);\\n                        ^\\n\\nve.init.mw.ViewPageTarget.prototype.setupToolbarButtons = function () {\\n  ..\\n    if (ve.msg('accesskey-save') !== '-' && ve.msg('accesskey-save') !== '') {\\n      this.elementsThatHadOurAccessKey = $( .. );\\n\\n\\nThe code in deactivate() shouldn't be repeating conditions like that as they're no longer semantically relevant, and in this case even incorrect. Instead the top one (which usually runs after setupToolbarButtons) should limit its interest to elementsThatHadOurAccessKey itself which we either set to null or to a jQuery object.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394151634, 'spacePHID': None, 'dateCreated': 1394125680, 'dateModified': 1443276258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62329', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Caption of nested image is centered in image dialog box', 'description': {'raw': 'Screenshot of image dialog\\n\\n1.  Go to page with images nested iside captions, e.g., the sandboxes at http://en.wikipedia.beta.wmflabs.org/w/index.php?&oldid=82442\\n\\n2.  Open the images and look at the caption for the first one.  The second image is displayed there, with its own caption centered.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F13240}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'bug', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701963258, 'spacePHID': None, 'dateCreated': 1394060040, 'dateModified': 1701963258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62287', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Block slugs don't shrink back when selection moves to a FocusableNode\", 'description': {'raw': \"1. Click in a block slug\\n2. The slug expands\\n3. Click in another paragraph\\n4. The slug contracts, as expected\\n5. Click in the slug again\\n6. The slug expands\\n7. Click on a FocusableNode (reference, template, etc.)\\n8. The slug doesn't contract\\n9. Click in a paragraph somewhere\\n10. Now the slug does contract\\n\\nThis is because contracting the slug when it's unfocused happens in pollOnceInternal, which is not invoked when selecting FocusableNodes (and only invoked by accident when changing the selection programmatically). onModelSelect in ce.Surface should probably clear the focusedness of the focused slug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394241829, 'spacePHID': None, 'dateCreated': 1394058780, 'dateModified': 1443276262, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62285', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Phantoms are appearing at wrong place while selecting an image after making it fullsize', 'description': {'raw': 'Phantoms appearing in wrong position\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert an image which has large enough original size to go beyond the page say for example: http://en.wikipedia.beta.wmflabs.org/wiki/File:Ho-Ho-Kus_Inn.jpg\\n\\n3.Make it full size \\n4.Save the page\\n\\n5.Reopen the editor\\n6.Select the image by clicking on a but further from the border of the image\\n\\nObserved Result:\\nThe phantom for selection is appearing in the wrong position\\n\\nSee the screenshots attached\\n\\nNow to observe some additional behavior:\\nSet the image size back to default size and observe the shield is still appearing in the previous position in the page\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13227}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406752402, 'spacePHID': None, 'dateCreated': 1394058180, 'dateModified': 1443278205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62284', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Sizing of `framed` images', 'description': {'raw': 'https://www.mediawiki.org/wiki/Help:Images#Size_and_frame says:\\n\\n> An image with frame always ignores the size specification, the original image\\n> will be reduced if it exceeds the maximum size defined in user preferences.\\n\\nHowever, as bug 53514 describes, the actual behavior seems to have regressed at some point.  The code in includes/Linker.php to check the user preference for size (which seems to be the same as the thumbnail size preference) is unreachable.  As presently written, framed images are always rendered at their \"natural\" size, *unless a height* is specified, in which case the height is honored (and the width, if any, ignored).\\n\\nIt\\'s not entirely clear what the proper fix should be.  There are three options:\\n\\n1. Leave the code as is, and update the spec on the wiki.\\n2. If a height is specified, honor the height *and* width (conservative, should change few pages)\\n3. Implement what I think was the original idea: *always* ignore the width and height, and limit the maximum image size with the user\\'s thumbnail size preference.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400696244, 'spacePHID': None, 'dateCreated': 1394031840, 'dateModified': 1490300192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62258', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show the \"*\" mark beside the required parameter in the Add Parameter section', 'description': {'raw': 'screenshot\\n\\nRight now , we are not showing the * mark beside the required parameter in the Add Parameter section.I think we should show it there too, because if a user accidentally deletes a required parameter from the left panel of transclusion dialog then he will not have any indication on the required parameter anymore.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F12919}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414085457, 'spacePHID': None, 'dateCreated': 1393876980, 'dateModified': 1417571687, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62161', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Display description for selected and required parameters in transclusion dialog', 'description': {'raw': \"Not exactly Bug 51774, but:\\nwhile descriptions of what a parameter is supposed to mean/do are provided in the list of available parameters inside the template inspector, this is not (no longer?) true for required and already selected parameters. The only way to read their description is to remove them from the left panel and get them back in the list, where they can be selected again, but clearly this is not optimal. Not sure a tooltip would be the way, so I'm filing this separately.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51774\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393868175, 'spacePHID': None, 'dateCreated': 1393854120, 'dateModified': 1443276266, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62142', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Edit link inconsistencies on Foreign file pages - skins which use doEditSectionLink  incompatible with FileRepo', 'description': {'raw': \"Navigate to https://commons.wikimedia.org/wiki/File:Apthorp_south_jeh.JPG\\nNow navigate to the same page via a ForeignAPI https://en.wikipedia.org/wiki/File:Apthorp_south_jeh.JPG\\n\\nNotice that in the latter a broken VisualEditor link appears.\\nExpected: No VisualEditor link\\n\\nSimilarly if you go to the mobile site you will see the same problem - an edit link appears in square brackets rather than an edit icon (see bug 61807). The mobile skin uses doEditSectionLink which seems to be incompatible with FileRepo.\\n\\n I've spent the morning talking with Brion to understand more about how the magic commons file page works and how the page is rendered.\\n\\nBasically the problem is in FileRepo.php\\ngetDescriptionRenderUrl creates an API request to something akin to https://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en\\nIf we can route this through the current skin this problem goes away.\\ne.g.\\nhttps://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useformat=mobile\\nor\\nhttps://commons.wikimedia.org/w/index.php?title=Image:Apthorp_south_jeh.JPG&action=render&uselang=en&useskin=vector\\n\\nBrion is taking a look to see if he can add a hook.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54259\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1539896996, 'spacePHID': None, 'dateCreated': 1393617960, 'dateModified': 1539896996, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62071', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"ResourceLoader: Change doesn't invalidate if change only touches a 'skinStyles' file\", 'description': {'raw': \"Applying the patch from Ie6b47f5d192953366911 in VisualEditor did not result in a module change update.\\n\\nI kept refreshing and purging but nothing happened.\\n\\nTurns out the way we fetch files in #getModifiedTime is broken for 'skinStyles'.\\n\\nFor some reason, this method duplicates the logic to interpret the 'skinStyles' array structure from #getStyleFiles (instead of using that method), and did so incorrectly causing it to always end up with an empty array.\\n\\nThe bug is quite subtle in that the module is capable of including these files (they're not missing from the css build), it's just that the module cache isn't invalidated if a commit only changed files listed in that part of a module.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393624328, 'spacePHID': None, 'dateCreated': 1393615200, 'dateModified': 1411500953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62068', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor navigation loops in block slugs at the start/end of the document', 'description': {'raw': \"Start case:\\n1. Create a document that starts with {{echo|<div>foo</div>}} followed by some more content\\n2. Put the cursor on the paragraph below the template\\n3. Press left arrow until you're selecting the template\\n4. Press left arrow; the cursor is now in the block slug\\n5. Press left arrow; the cursor is now on the template\\n6. Go to step 4\\n\\nEnd case:\\n\\n1. Create a document that ends with <references /> preceded by some content\\n2. Put the cursor in the paragraph above the reflist\\n3. Press right arrow until you're at the end of this paragraph\\n4. Press right arrow; the cursor is now on the reflist\\n5. Press right arrow; the cursor is now in the block slug\\n6. Press right arrow; the cursor is now before the reflist \\n7. Go to step 4\\n\\nNote how the end case differs from the start case in that the loop is 3 keypresses long rather than 2.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1423750743, 'spacePHID': None, 'dateCreated': 1393612500, 'dateModified': 1423750743, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62066', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor for all users and IPs by default on French Wikiversity', 'description': {'raw': \"Hello,\\n\\nJust to ask if it's possible to unable the Visual Editor for IP user on fr.wikiversity like fr.wikipedia.\\n\\nThanks a lot and have a nice day.\\n\\nLionel\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-mxwamhfxuzomk4umydpl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396023734, 'spacePHID': None, 'dateCreated': 1393587180, 'dateModified': 1397521192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62045', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block)', 'description': {'raw': 'In Thai language, it is possible that many characters (at most 3 or 4) will be on top each other. For example, \"ที่\" consists of three characters: \"ท\", \"ี\", and \"่\". In standard textbox/textarea, including normal wikieditor, when you press left, the cursor will go left by 1 block = 3 characters in case of \"ที่\". However, for VE\\'s editor, it will go left by only 1 character, making editors feel that he unsuccessfully pressed the key. More importantly, with the way VE\\'s editor is, it opens possibility that editors, thinking that the cursor is after \"่\", will accidentally insert text between \"ี\" and \"่\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-vuus2gmqsnxh6mnavgml', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'dateClosed': 1536154773, 'spacePHID': None, 'dateCreated': 1393547460, 'dateModified': 1666438856, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62028', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Initial focus when the meta-dialog is opened is still the main document body, so typing inserts the text in CE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Page Settings page\\n3.Now type something \\n\\nObserved Result:\\n\\nIt inserts the text in the CE\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Imageghau&veaction=edit\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13238}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393615362, 'spacePHID': None, 'dateCreated': 1393545840, 'dateModified': 1443276268, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62027', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf16] TypeError: this.typeInput.getSelectedItem(...) is null appearing and cannot close the Media Settings dialog for an image with left position and border format', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to Media Settings>Advanced Settings for that image\\n4.Set the position to left and image type to border\\n5.Save the page\\n6.Reopen the page \\n7.Select the image and open the media settings for it\\n\\nObserved Result:\\n\\nTypeError: this.typeInput.getSelectedItem(...) is null appears in the console and also I could not cross out the media settings page for that image and got stuck in VE.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=27thfebff&veaction=edit\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13211}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395701559, 'spacePHID': None, 'dateCreated': 1393541100, 'dateModified': 1443276268, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62024', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Getting \"Uncaught TypeError: Cannot call method \\'getOffset\\' of null\" error when I open a page that contains a bullet list with floated content', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Create a page with VE\\n2.Add a bullet list\\n3.Add an image as a bulleted item of that list (\\n4.Save the page\\n5.Reopen the editor\\n\\nObserved Result:\\nAs soon as I open the page I get the error:\\n \"Uncaught TypeError: Cannot call method \\'getOffset\\' of null\"\\n\\nAnd then clicking on Bullet list icon again does not un-bullet the list\\nAlso, every time I switch to this page from other window/page it shows this error again and again. \\n\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/27thfebchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13207}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393633180, 'spacePHID': None, 'dateCreated': 1393538400, 'dateModified': 1443276271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62022', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Using the language link tool in the sidebar when inside VisualEditor loses the edit without warning', 'description': {'raw': \"A user at en.wp reported today that you can add interlanguage links while you're in VE. The last step when doing so means the whole page gets reloaded, so whatever was done in VE until that moment gets lost. I am not aware of ways to prevent this, and there is no indication in VE that this will happen when you start that procedure.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Whiteboard**: u=dev c=backend p=0\\n**See Also**:\\n{T54105}\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1540258002, 'spacePHID': None, 'dateCreated': 1393520520, 'dateModified': 1540258006, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62005', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deal with universal types like mw:Error, mw:ExpandedAttrs, mw:Placeholder', 'description': {'raw': 'Some types like mw:ExpandedAttrs are universal, meaning they can apply to any element and their presence shouldn\\'t be taken into account when figuring out which node handler to invoke. The node handlers themselves probably do need to make decisions based on their presence, but that\\'s fine, they can do that already.\\n\\nFor now the approach I\\'m considering is to add the concept of a universal RDFa type, which will be ignored by ve.dm.ModelRegistry#matchElement for all purposes (including the \"if not all mw: types are matched it\\'s not a match\" logic and all of that). mw:ExpandedAttrs and mw:Error (the latter would be introduced by bug 50788) would be universal types. mw:Placeholder wouldn\\'t be one, because it needs to trigger alienation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1652133850, 'spacePHID': None, 'dateCreated': 1393458480, 'dateModified': 1652133852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61969', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor\", 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to Media Settings of that image\\n4.Insert another image inside it in the General Settings section\\n5.Go to Media Settings for that image and set the Image type as Frameless and keep the position to right\\n\\nObserved Result:\\nThe image resize handlers appear at all four corners instead of appearing only at bottom left corner\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404850889, 'spacePHID': None, 'dateCreated': 1393456440, 'dateModified': 1424894573, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61968', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clear the previous search term while opening the \"Use an existing reference\" and \"Insert Media\" dialog again', 'description': {'raw': 'Use Existing reference dialog  box\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Reference >Use an existing reference\\n3.Type a search term in the search box\\n4.Select a reference from the search result.\\n5.Now again attempt to add another existing reference \\n\\nObserved Result:\\nWhen the page of existing references opens up it still keeps the search term from previous attempt and shows the search results , it should rather clear the previous search term and let user to start over.\\nThis issue also occurs for new media adding dialog\\n\\nSee the screenshots attached.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13051}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395875349, 'spacePHID': None, 'dateCreated': 1393447320, 'dateModified': 1443276272, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61959', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inherited categories not showing up in category dialog on a category page (should show up clearly differentiated)', 'description': {'raw': 'Specifically on this page, https://it.wikipedia.org/w/index.php?title=Categoria:Aggiornare_-_economia&veaction=edit .\\nI tried adding all those categories to my sandbox but they work fine there (https://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&oldid=64431369&veaction=edit ), same if I add the rest of the content of that page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72303'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1393352640, 'dateModified': 1643977428, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61921', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  \"Notices\" tooltip says \"$1 notices\" rather than the correct number', 'description': {'raw': 'Steps to Reproduce:\\n1. Open a page (like Today\\'s Featured Article) that will have notices.\\n2. Hover over the \"Notices\" triangle.\\n3. Read the tooltip.\\n\\n\\n\\nReproducible: Didn\\'t try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393464417, 'spacePHID': None, 'dateCreated': 1393309740, 'dateModified': 1443276274, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61891', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing backspace when cursor is in the first position in a nested list item should unindent, not merge it with the previous item in the parent list', 'description': {'raw': 'Steps to reproduce:\\n\\n- Create a numbered list as follows:\\n```\\n1.item 1\\n2.\\n3.item 3\\n```\\n- Now add indentation to the third item , so it becomes:\\n```\\n1.item 1\\n2.\\n      1.item 3\\n```\\n- Now place the cursor just before the item 3 and press delete\\n\\nInstead of having the item 3 unindented the resulting list comes up as: \\n```\\n1.item 1\\n2. 1. item 3\\n```\\nSee the screenshot: {F12837}\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage: http://en.wikipedia.beta.wmflabs.org/wiki/24thfebchrome?veaction=edit\\n\\n**See Also**: {T65051}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701963109, 'spacePHID': None, 'dateCreated': 1393270740, 'dateModified': 1701984700, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61863', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Place redirects at the top of the page, not the bottom', 'description': {'raw': \"The proper order is #REDIRECT[[Whatever]], then categories and other stuff.  If you place the redirect anywhere other than the very top of the page, it won't work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393537213, 'spacePHID': None, 'dateCreated': 1393270500, 'dateModified': 1443276278, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61862', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show something other than a blank page when editing a redirect page', 'description': {'raw': \"When you set a redirect in VisualEditor, it doesn't display anything, so it looks like it didn't work.\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-mvx4x7ywk2flsaku2dbk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1458262104, 'spacePHID': None, 'dateCreated': 1393270380, 'dateModified': 1481110828, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61861', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Improve the UX of the template editor', 'description': {'raw': 'I find the whole thing to be rather confusing. It\\'s much too technical. Also it partially mixes the concept of ToC with that of a structure editor. It has some widgets on the ToC (add template, add content, change order) and others inside the editor (Add param, del param, del template). This is terribly inconsistent. And makes you having to scan the screen too much.\\n\\nAlso by default it tries to introduce you to the concept of chained templates ( starttemplate, content, endtemplate ). Which is rather complex and often not even needed.\\n\\nThis needs serious work to make the usability much more consistent and predictable. I would take the following into account.\\n\\n\\n1: Make a decision. Is it a toc, or a structure editor ? If the latter, then put all structure controls in the structure editor. Otherwise avoid putting them in there.\\n2: By default, don\\'t show the buttons for chained/wrapping templates. Instead, only add them if Parsoid assumes there is content wrapping happening. For new templates insertion, make an addition to templatedata \"openedBy, closedBy\", and only add the buttons if the template data says they are needed.\\n3: Keyboard control. I try tab key to move focus to the \"Add template\" button next to the field. Seems this is captured by the UI, so I cannot move focus that way. It seems I can only click the button. BAD... Also seems that the add button and the delete buttons do not have a :focus state. Or rather, it seems that buttons have focus state, but the focusable element is the <a> inside it, so it doesn\\'t really work.\\n4: The layout of the params view.. I don\\'t know how to do it better right now, but this needs work. too many lines/blocks, it\\'s too cluttered. Do you need a double line separator if you have a heading ?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394130209, 'spacePHID': None, 'dateCreated': 1393171260, 'dateModified': 1443276278, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61822', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Flow: Parsoid HTML for videos doesn't work\", 'description': {'raw': 'eg. https://ca.wikipedia.org/wiki/Tema:T3edcbkgt2ns31ff \\n\\n(Old example: http://ee-flow.wmflabs.org/w/index.php?title=User_talk:Quiddity&topic_postId=rpnkneesuic1rsx8&workflow=rnhr0vbpmcq1wj5m#flow-post-rpnkneesuic1rsx8 )\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: http://ee-flow.wmflabs.org/w/index.php?title=User_talk:Quiddity&topic_postId=rpnkneesuic1rsx8&workflow=rnhr0vbpmcq1wj5m#flow-post-rpnkneesuic1rsx8'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1489186341, 'spacePHID': None, 'dateCreated': 1393014300, 'dateModified': 1492817612, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61769', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Extension tags that create block-level items aren't allowed inside pre-formatted rows in MW\", 'description': {'raw': \"If you add a formula (or other inline item) to a normal paragraph, everything works in VE consistently with MW (yay).\\n\\nIf you add a formula (or other inline item) to a pre-formatted paragraph, everything still works works (yay).\\n\\nIf you add a gallery (or other block item) to a normal paragraph, everything works in VE consistently with MW (yay).\\n\\nIf you add a gallery (or other block item) to a pre-formatted paragraph, VE tries to let you do that, and MW decides retroactively that the paragraph wasn't actually pre-formatted (boo), unless it's a <pre>-formatted rather than indent-pre-formatted block, in which case galleries don't work.\\n\\nNot tested with Headings, but there's probably similar wonkiness there too.\\n\\n*sighs*\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1493661754, 'spacePHID': None, 'dateCreated': 1393014300, 'dateModified': 1493661756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61767', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make VisualEditor opt-out on Portuguese Wikibooks', 'description': {'raw': 'We are currently using a hack[1] to make VisualEditor to be the default edit mode on Portuguese Wikibooks.\\n\\nCould someone make it the default in the right way?\\n\\n[1] https://pt.wikibooks.org/wiki/MediaWiki:Gadget-VisualEditorByDefault.js\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**URL**: https://pt.wikibooks.org/wiki/T%C3%B3pico:Wikilivros_Discuss%C3%A3o:Portal_comunit%C3%A1rio/Testes_com_o_Editor_Visual_no_Wikilivros/resposta_%284%29'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393287716, 'spacePHID': None, 'dateCreated': 1393011960, 'dateModified': 1393327454, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61762', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Remove Flow from Meta-Wiki', 'description': {'raw': 'Please uninstall the Flow extension from Meta-Wiki. Relevant discussion: <https://meta.wikimedia.org/w/index.php?title=Meta:Babel&curid=69328&diff=16251209&oldid=16240965>.\\n\\nThe extension was installed in <https://gerrit.wikimedia.org/r/114088>.\\n\\nExplicit consensus for complete removal (and lack of consensus for any partial survival of the extension): https://meta.wikimedia.org/w/index.php?title=Meta:Babel&oldid=16337330#Proposal_to_remove_Flow_on_Meta-Wiki'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'dateClosed': 1488495297, 'spacePHID': None, 'dateCreated': 1392946860, 'dateModified': 1730423779, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61729', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar broken in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\nOpen the VE and observe the toolbar\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13046}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392937699, 'spacePHID': None, 'dateCreated': 1392934800, 'dateModified': 1443276279, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61708', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: modules/syntaxhighlight/rules/mysql.json has unescaped double quotes in a double quoted string', 'description': {'raw': 'The file modules/syntaxhighlight/rules/mysql.json has at least one double quoted string containing unescaped double quotes. I.e something like:\\n\\n{\\n \"match\" : \"\"\"\\n}\\n\\nThat cause PHP json_decode() to choke with a syntax error.  I wrote a json linter to lint json files in Jenkins.  You can try it using integration/jenkins.git and running bin/json-lint.php\\n\\n ./modules/syntaxhighlight/rules/mysql.json: Syntax error\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392926436, 'spacePHID': None, 'dateCreated': 1392906540, 'dateModified': 1392926451, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61659', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference group input should be a \"ComboBox\" suggesting possible values', 'description': {'raw': 'Right now the reference group input (in both MWReferenceDialog and MWReferenceListDialog) is a plain text input box (with a placeholder).\\n\\nInstead, it should be a drop-down that suggests existing groups, as well as giving the ability to write in a new value, aka a ComboBox.\\n\\nThe default value should still have a placeholder, I think.\\n\\n[Blocked on OOjs UI having a ComboBox widget.]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409689348, 'spacePHID': None, 'dateCreated': 1392861240, 'dateModified': 1443278205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61574', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Factor out ./ stripping logic', 'description': {'raw': \"Right now it's in MWInternalLinkAnnotation and MWRedirectMetaItem just calls into that (see https://gerrit.wikimedia.org/r/#/c/114381/). There's also some ./ stripping regexes strewn across the rest of the codebase. This should all be factored out and centralized.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1392860160, 'dateModified': 1643977429, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61572', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  In the category dialog, there should be a drop down indicator on existing categories', 'description': {'raw': \"Inside the category editor, there used to be a drop-down indicator on categories.  It's not there now.  Not at MediaWiki, not at Wikipedias, not in Safari 6, not in Firefox 26 (on Mac OS 10.8.5).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392859556, 'spacePHID': None, 'dateCreated': 1392858900, 'dateModified': 1443276281, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61571', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Burn ve.ce.getElementOffset down to the ground', 'description': {'raw': \"It's incredibly confusing spaghetti code that's not documented well. Kill it with fire and start from scratch.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404350652, 'spacePHID': None, 'dateCreated': 1392852060, 'dateModified': 1417572126, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61567', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't allow users to insert images inside images' captions inside images' captions, as MediaWiki can't cope with that\", 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to Media Settings of that image and add another image inside it\\n4.Now Go to the media settings of the image that you just added\\n5.Type something in the caption of the second image\\n6.Apply changes\\n7.Save the page\\n\\nObserved Result:\\nThe wiki text for the image shows up in the read mode\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/19thfebFF\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13390}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437755749, 'spacePHID': None, 'dateCreated': 1392850500, 'dateModified': 1437755749, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61564', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Revert image |link= hack for Parsoid bug 49844', 'description': {'raw': \"Parsoid's bug 49844 with link attributes has been fixed.\\n\\nIn https://bugzilla.wikimedia.org/show_bug.cgi?id=49844#c5 James Forrester wrote:\\n\\nThis is worked around (albeit with potentially a bit of a hack) in VisualEditor, so not so important now from VisualEditor's POV.\\n\\nNow that the parsoid fix has been deployed (for a while now), I'm opening a new bug to revert Visual Editor's hack.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395082995, 'spacePHID': None, 'dateCreated': 1392847560, 'dateModified': 1417572513, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61560', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Error thrown when typing something while a left aligned image is selected', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert an image .\\n3.Go to Media Settings>Advances Settings\\n4.Set the image alignment to left/None\\n5.Save the page\\n6.Reopen the page\\n7.Select the image\\n8.Start typing something\\n\\n\\nObserved Result:\\nncaught Error: Offset could not be translated to a DOM element and offset: 143 appears in the console \\n\\nSee the screenshot attached\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=18thfebchrome&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13297}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701962955, 'spacePHID': None, 'dateCreated': 1392767520, 'dateModified': 1701962955, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61524', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow lacking accesskeys for preview/submit', 'description': {'raw': 'It seems Flow has not defined any HTML accesskeys for previewing/submitting posts and topics.\\n\\nThe default accesskey \"p\" should be added to the \"Preview\" button.\\nThe default accesskey \"s\" should be added to the \"Reply\"/\"Add Topic\"/\"Submit changes\" buttons when replying to a topic/adding a topic or editing a post respectively.\\n\\nDocs (I\\'m not sure which of these are most uptodate):\\n* https://www.mediawiki.org/wiki/Manual:Interface/Access_keys\\n* https://meta.wikimedia.org/wiki/Help:Keyboard_shortcuts\\n* https://en.wikipedia.org/wiki/Wikipedia:Keyboard_shortcuts\\n* https://www.mediawiki.org/wiki/VisualEditor/Portal/Keyboard_shortcuts\\n\\nSee also {T158779}\\n'}, 'authorPHID': 'PHID-USER-v3yn5qf233ggnnnmvejc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1392758820, 'dateModified': 1621977018, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61517', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Have an i18n CI job that ensures there's a qqq message for each en message\", 'description': {'raw': \"For projects built with npm (e.g. VE, OOjs UI) this could be relatively easy, but for MW core I imagine it's a bit harder to parse .php files.\\n\\n(For VE we'd want this blocking merge, but that's a distinct conversation.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397692309, 'spacePHID': None, 'dateCreated': 1392753720, 'dateModified': 1397823691, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61509', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] Jenkins: Jobs for npm testing are broken due to npm certificate issues on the new slaves', 'description': {'raw': \"Last working job:\\n  https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/942/console\\n\\n  - Feb 16, 2014\\n  - Building remotely on integration-slave01\\n\\n  - node v0.10.22\\n  - npm v1.1.38\\n\\nFirst failing job:\\n  https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/943/console\\n\\n  - Feb 18, 2014\\n  - Building remotely on integration-slave02\\n\\n  - node v0.8.2\\n  - npm v1.1.39\\n\\n16:23:41 npm ERR! Error: SSL Error: CERT_UNTRUSTED\\n16:23:41 npm ERR!     at ClientRequest.<anonymous> \\n16:23:41 npm ERR!     at Socket.ondata (stream.js:38:26)\\n16:23:41 npm ERR!  [Error: SSL Error: CERT_UNTRUSTED]\\n\\nServer log:\\n  https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&diff=99596&oldid=99549\\n\\n\\n  - February 17\\n    - 16:15 hashar: Jenkins deleting slave integration-slave01\\n    - 16:14 hashar: Jenkins added two labs slaves with 4 CPU: integration-slave02 and integration-slave03\\n    - 08:46 hashar: Upgrading Jenkins, half an hour downtime\\n\\n\\n\\nSo npm was upgraded one minor version, and nodejs was downgraded *2 major versions*, and (possibly unrelated) it seems to be unable to verify the certificate properly.\\n\\nAccording to existing bug reports, this is related to it being a self-signed certificate, however this shouldn't be a problem since a validation mechanism for their official certificate ships with the npm package. Upstream recommends upgrading to the most recent minor version, but that doesn't seem to be the problem considering the bug started happening for us overnight (no certificate change upstream) when we went from v1.1.38 to v1.1.39 (not down).\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**See Also**:\\nhttps://github.com/npm/npm/issues/4838\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405742229, 'spacePHID': None, 'dateCreated': 1392752580, 'dateModified': 1405742229, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61508', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Reusing references inside the VE template dialog', 'description': {'raw': 'The VE template dialog can - with the help of #templatedata - show input fields for a template\\'s parameters. Usually these are simple text fields that offer no editing tools.\\n\\nAs a user it would be nice to have a simple way to add references or re-use reference from the main article to input fields in dialog.\\n\\nA way to move forward here could be:\\n- For a specific template parameter type (e.g. `content`) add...\\n- ...either a button that opens the Citation dialog and adds wikitext, similar to how it\\'s done in the WTE2017\\n- ...or add a \"inline\" VisualEditor similar to what\\'s done for the image dialog\\'s caption field '}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1392748620, 'dateModified': 1683795706, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61505', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Automatically remove empty ref tags (and refuse to insert new ones)', 'description': {'raw': 'If you add an empty, unnamed reference in wikitext (\"<ref />\"), then you get an empty, invalid reference.\\n\\nIf you add an empty, unnamed reference in VisualEditor (Insert>Reference, then \"Add reference\" without typing anything), then you get an empty, invalid reference.\\n\\nVisualEditor should do better than wikitext:  it should detect empty, unnamed ref tags and refuse to insert them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403743200, 'spacePHID': None, 'dateCreated': 1392746820, 'dateModified': 1429032574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61503', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Document what is needed in terms of support for custom MediaWiki skins', 'description': {'raw': \"**Author:** `duongxvu`\\n\\n**Description:**\\nI was wondering whether it is possible for VisualEditor to work with other skins besides the officially supported ones (which I believe to be Vector, Monobook, and Apex). I’ve been tasked with creating a custom skin to meet my organization’s existing design standards, but it does not seem so easy to add support for VisualEditor in this regard. And documentation addressing similar issues to mine seem to be rare at the moment.\\n\\nFor now, I've heavily modified Vector as a workaround, but would prefer a more long-term solution if one exists. I assume that the Vector skin will continue to receive regular updates in the future, and I’d like to avoid having to modify it every time that happens.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://www.mediawiki.org/wiki/VisualEditor/Skin_requirements\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401204582, 'spacePHID': None, 'dateCreated': 1392743160, 'dateModified': 1512588750, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61500', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using auto select zhu-yin input and it keeps bouncing duplicate chinese characters', 'description': {'raw': 'Please go to the youtube link for fully demo http://www.youtube.com/watch?v=DZ90EDLqHUI\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Mac OS X 10.6\\n**Platform**: Macintosh'}, 'authorPHID': 'PHID-USER-adqeptkffhhfdhukexph', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1392515640, 'dateModified': 1482837343, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Ref group does not get updated when the group name is changed from References List dialog', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a reference with a group name \"first group\"\\n3.Now Add a references list but under Use this group, type \"first group one\"\\n4.Apply changes.(\"there are no references with this group\" will appear which is correct)\\n5.Now reopen the References list dialog again.\\n6.Just delete the \"one\" from \"first group one\" to make it \"first group\"\\n7.Apply changes\\n\\nObserved Result:\\nEven this time it says \"there are no references with this group\" which is wrong.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser:FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1540268768, 'spacePHID': None, 'dateCreated': 1392415980, 'dateModified': 1540268769, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61396', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: A black shadow is appearing in the Cite Web template dialog inside Media Settings after scrolling down a bit', 'description': {'raw': 'The shadow\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to Media Settings for that image\\n4.Go to Insert>Transclusion\\n5.Search for the Cite Web template\\n6.Add a value for URL and Source Title\\n7.Apply Changes\\n8.Now again re-open the cite web dialog for the template you just added\\n9.When all the parameter list appears in the dialog box , scroll down a bit.\\n\\nObserved Result:\\n\\nObserve that,there is a black shadow appearing on the border above the Apply Changes button, it seems to me coming from the \"URL Access Date\" field as it was initially aligned with that border.\\n\\n\\nSee the screenshot attached to better understand the problem\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12975}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401418554, 'spacePHID': None, 'dateCreated': 1392411060, 'dateModified': 1417572294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61394', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Be able to access a display file's description page from within VE (e.g. in the media settings dialog)\", 'description': {'raw': \"On inserting an image, or editing an image, it should be possible to visit the file description page. Currently it's not even possible to get the filename of an image when in VE.\\n\\nWhy this is needed: In order to access the captions on the image page or verify the license or similar. E.g. on inserting an image of Obama shaking hands with some other important person into the Obama article you might want to find out who this other person is\\n\\nSuggested solution: Add a link to the filepage in media settings.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'dateClosed': 1434918715, 'spacePHID': None, 'dateCreated': 1392369960, 'dateModified': 1438734960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61367', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Uncaught SyntaxError: Invalid flags supplied to RegExp constructor 'index'  appears in production while saving any change from Edit Source mode\", 'description': {'raw': \"Screenshot attached\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Make some changes\\n3.Switch to edit source mode\\n4.Save the page from Edit source mode\\n\\nObserved Result:\\nUncaught SyntaxError: Invalid flags supplied to RegExp constructor 'index' appears in the console\\n\\nTest Environment: production\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12828}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392335656, 'spacePHID': None, 'dateCreated': 1392322440, 'dateModified': 1417572658, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61333', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Rich paste fails and crashes surface with (? specific) content', 'description': {'raw': 'Steps to replicate:\\n\\n1. Edit an article in VisualEditor (or start a new one)\\n2. Go to http://git-scm.com/download/linux\\n3. Copy the list, from \"Debian/Ubuntu\" to the end of the content in the white space.\\n4. Paste into the article in VE.\\n\\nObserved: \\n\\n\"Uncaught TypeError: Cannot call method \\'getComparableObjectForSerialization\\' of undefined\"\\n\\nAfter that, interaction with the CE - mostly with link inspector and surface widgets produces errors or is unresponsive (Without console error)\\n\\nI got this when I tried to add a link: \"Uncaught TypeError: Cannot call method \\'getSurface\\' of null\"\\n\"\\n\\n\\n\\nChrome 32.0.1700.107 under Ubuntu 12.04.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392853839, 'spacePHID': None, 'dateCreated': 1392321600, 'dateModified': 1443276283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61332', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Beta tag ({{int:visualeditor-beta-appendix}}) should not always be displayed in the guider description', 'description': {'raw': '**Author:** `swalling`\\n\\n**Description:**\\nFrancais\\n\\nEdit beta is specific to English Wikipedia but we hard coded it in the tour text for GettingStarted, so it is showing up incorrectly in translated versions such as French etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12815}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393003728, 'spacePHID': None, 'dateCreated': 1392312420, 'dateModified': 1422512618, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61321', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable Extension:Translate on OTRS wiki', 'description': {'raw': 'After a discussion with no objections amongst the OTRS administrators on our mailing list, we would like to have the Translate extension enabled on OTRS wiki to facilitate translating messaging. Thanks!\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-hxjysvdvogekpjub3nd3', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393368243, 'spacePHID': None, 'dateCreated': 1392259920, 'dateModified': 1658162155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61297', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using \"Make full size\" doesn\\'t work when size is default', 'description': {'raw': 'Maggie Dennis on bug 50645:\\n> I\\'m not sure if this is the same issue, but as reported on English Wikipedia\\n> and tested by myself, using the image resizer to \"Make full size\" resulted in\\n> either a notice that no change had been made or a silent failure to save.\\n> \\n> This was tested on FF26, W7 and Chrome 32.0.1700.107 m, W7. \\n> \\n> The reporting editor concludes that \"These new settings, for what they are\\n> worth, only work if the image already has a size indication (200px,\\n> 250px*250px, whatever), not when it only has a \\'thumb\\' indication. Sadly, the\\n> latter is the default and by far most common situation.\"\\n> \\n> He also questions the purpose of \"Make full size\", but I\\'ll report that\\n> separately. \\n> \\n> See:\\n> https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/\\n> Feedback&oldid=595141503#Advanced_image_settings.\\n> 3F_More_VisualEditor_rubbish.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392254177, 'spacePHID': None, 'dateCreated': 1392223320, 'dateModified': 1443276287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61270', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create wiki (legalteamwiki) for Wikimedia Foundation legal team', 'description': {'raw': \"In an effort to allow the legal and lca team to work directly on a wiki more often (including for legally sensitive work) and to move away from google docs and the like as much as possible we would like to set up a private wiki for the team.\\n\\nIn general Ombudsmanwiki would be a good wiki to copy settings from but for the ones I can think of off the top of my head:\\n\\nWiki domain should be legalwiki.wikimedia.org.\\nLanguage should be English.\\nLogo can be $stdlogo.\\nFavicon can be wmf.ico\\nCanonical server should be https (forced should be on).\\nAccount creation should be bureaucrat only (not sysop).\\nTranswiki destinations of office, collab and meta would be helpful. (Not sure if private wikis can be tw destinations though... if not that's fine.\\nwmgUseDisableAccount should be true\\n\\nI can be the original sysop/crat.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-f6l3bchko2ogbi4poj24', 'ownerPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394607638, 'spacePHID': None, 'dateCreated': 1392140760, 'dateModified': 1503509410, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61222', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor on frwikiversity', 'description': {'raw': 'Per e-mail request\\n\\nConsensus: https://fr.wikiversity.org/wiki/Projet:Wikiversit%C3%A9/Editeur_Visuel\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392253986, 'spacePHID': None, 'dateCreated': 1392067440, 'dateModified': 1397521192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61157', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting \"None\" as position in Media Settings>Advanced Settings shifts the image to the right of the page', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to Media Settings>Advanced Settings for the image\\n4.Select the value \"None\" under the postion \\n\\nObserved Result:\\nSelecting \"None\" as position in Media Settings>Advanced Settings shifts the image to the right of the page\\n\\nSee the screenshot attached.\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/10thFeb\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13027}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395354482, 'spacePHID': None, 'dateCreated': 1392061500, 'dateModified': 1417572508, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61152', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __DISAMBIG__ status in the page meta-data panel', 'description': {'raw': \"'Cos we do most of the others.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402341590, 'spacePHID': None, 'dateCreated': 1391818800, 'dateModified': 1443278208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61073', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector is appearing broken or towards the end of the page while applying link by selecting a whole link', 'description': {'raw': 'Appears towards the end of the page\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Select a text in such way that it selects the whole line\\n3.Now open the link inspector\\n\\nObserved Result:\\n\\nSometimes the link inspector appears in a broken way and sometimes it appears little below the text towards the end of the page\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12833}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406322759, 'spacePHID': None, 'dateCreated': 1391817120, 'dateModified': 1441911980, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61069', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After inserting a gallery, the newly inserted gallery does not remain highlighted but the inspector icon shows up at the corner of the page', 'description': {'raw': 'Screenshot\\n\\nsteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Gallery \\n3.Insert a gallery\\n\\nObserved Result:\\nThe newly inserted gallery is not highlighted but the gallery inspector icon is appearing at the corner of the page which is not consistent with the behavior observed with other link inspectors like Math/Hiero\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nSample Page:http://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12822}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402921585, 'spacePHID': None, 'dateCreated': 1391814840, 'dateModified': 1443278208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61065', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switching browser tab/window changes the tab selection from Advanced Settings tab to General Settings', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE which contains an image\\n\\n2.Open the media settings for the image\\n\\n3.Go to the advanced settings page\\n\\n4.Now switch the browser tab or window and then again switch back\\n\\n\\nObserved Result:\\n\\nThe tab in Media Settings got switched to General Settings from Advanced Settings.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416264866, 'spacePHID': None, 'dateCreated': 1391813340, 'dateModified': 1417571677, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61062', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting the first digit of the size in Media Settings removes the entire value in the both fields', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the page in VE\\n2.Insert an image\\n3.Go to Media Settings>Advanced Settings\\n4.Now delete the first digit of the size.For example:if you have size :600*450\\nJust attempt to make it 500*450\\n\\nObserved Result:\\nThe Width and the Height both values turned into 0.User have to again type the input of Height value which he might not wanted to change.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nhttp://en.wikipedia.beta.wmflabs.org/wiki/7thfeb?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394047167, 'spacePHID': None, 'dateCreated': 1391812020, 'dateModified': 1443276291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61059', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor should enforce TemplateData's 'type': 'line' for template parameters (no multiline input)\", 'description': {'raw': \"Intention:\\nAdd a link to a template using {{tl}} on English Wikipedia.\\n\\nSteps to Reproduce:\\n1.  Add Template:Tl.\\n2.  Add any template name, and press return afterwards (so that the parameter field is name+return)\\n3.  Apply changes.\\n\\nExpected Results: No newline is inserted.\\n\\nActual Results:  \\nThe template is broken because the parameter can't support the inclusion of a return.\\n\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1391799720, 'dateModified': 1423676405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61049', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Pipe trick in templates displays wikitext rather than link', 'description': {'raw': 'Intention:\\nAdd more information to an infobox.\\n\\nSteps to Reproduce:\\n1. Open the infobox.\\n\\n2. Add a parameter with a link to a disambiguated page name.\\n\\n3. Use the pipe trick to label the link: [[Wooden spoon (award)|]]\\n\\n4.  Apply changes.\\n\\nActual Results:  \\nIn VisualEditor, the template displays raw wikitext for that item:   [[Wooden spoon (award)|]] \\n\\nExpected Results:  \\nThat VisualEditor would display the same blue link with the same link label as the page will when it is saved (\"Wooden spoon\")\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=594279537&oldid=593922721'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392175419, 'spacePHID': None, 'dateCreated': 1391726580, 'dateModified': 1443276294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60998', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'WikiEditor: Provide some basic formatting and action keyboard shortcut commands', 'description': {'raw': 'CTRL/CMD+B for bolding highlighted text\\nCTRL/CMD+I for italicising highlighted text\\nCTRL/CMD+U for underline highlighted text\\n\\nCTRL+1,2,3 for H1,H2, H3, etc\\n\\nCTRL/CMD+K for linking highlighted text\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-52k2lmr37woy42l6kdmv', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-52k2lmr37woy42l6kdmv', 'dateClosed': 1731648287, 'spacePHID': None, 'dateCreated': 1391648220, 'dateModified': 1733607058, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60928', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Use an Existing Reference\" option remains disabled for a reference inside Media Settings while there is a reference available to re-use in the page', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the page with VE\\n2.Add a text with reference\\n3.Add an image\\n4.Go to Media Settings for the image\\n5.Go to Insert>Reference\\n\\nObserved Result:\\nObserve that, the \"Use an existing reference \" button remains disabled even if there is a reference added in the page\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/Wmf12chrome?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13113}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1391638020, 'dateModified': 1683791054, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60919', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor in the Projekt namespace on se.wikimedia.org', 'description': {'raw': 'Please enable VisualEditor also in the \"Projekt\" namespace on the wmse chapters wiki.\\n\\nPlease note that this is not the same as the NS_PROJECT/Wikimedia\\nnamespace.\\n\\nPoll/request at: https://se.wikimedia.org/wiki/Tr%C3%A5d:Wikimedia:Bybrunnen/VisualEditor_p%C3%A5_Projekt:-sidorna\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': 'PHID-USER-hxjysvdvogekpjub3nd3', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392330904, 'spacePHID': None, 'dateCreated': 1391599320, 'dateModified': 1392330904, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60882', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create an API module to allow apps to set global preference', 'description': {'raw': 'Discussion: {T196314}\\n\\nDeliverables:\\n* API module to allow apps to set global value for a preference.\\n\\nSee also:\\n* {T197259}\\n* {T197260}\\n'}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': 'PHID-USER-aasrweh54ew7py3agvg2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '5', 'subtype': 'default', 'closerPHID': 'PHID-USER-qztkawkvfnwvkspdr46l', 'dateClosed': 1530895601, 'spacePHID': None, 'dateCreated': 1391567760, 'dateModified': 1534335522, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60856', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Broken local Common.js causes VE not to be available on some wikis', 'description': {'raw': \"**Author:** `jhall`\\n\\n**Description:**\\nWhile developing a browser test for bug 60797, I've noticed that some production wikis where VisualEditor is expected to be available do not load VE as expected.  In each case, the error message captured at the browser level is (with some variation in the specific line numbers referenced):\\n\\n\\n[Error] Error: JavaScript parse error: Parse error: Missing operand in file 'MediaWiki:Common.js' on line 125\\n\\tglobal code (load.php, line 1)\\n\\n\\n\\nRepro steps:\\n\\n1) Visit a production wiki where VE is expected to be available, and request a random article with a VE edit param: http://cv.wikipedia.org/wiki/Special:Random?veaction=edit\\n\\n2) In browser error console, note JavaScript error mentioned above, and note also that the VE editing surface simply never loads (although it appears to keep trying!)\\n\\n\\nI'll add list(s) of production wikis where this problem occurs as I uncover them in comments on this bug ticket.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60797\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397858975, 'spacePHID': None, 'dateCreated': 1391544360, 'dateModified': 1443276297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60842', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Native Mac OS special character inserter fails to get content into DM, just CE, in Safari', 'description': {'raw': \"Intention:\\nAdd a special character from the built-in Mac OS character inserter.\\n\\nSteps to Reproduce:\\n1. Using Safari, open a page in VisualEditor.\\n\\n2. In Safari's menu bar, choose Edit > Special Characters...\\n\\n3. Double-click on special characters to add them.\\n\\nActual Results:  \\nThe special characters display on the screen, but are not present when you try to save the text.  Characters that were typed from the keyboard are saved.  No characters (even if they are 'normal' ones) are saved if they were added with the character inserter.\\n\\n\\nReproducible: Always\\n\\nIt works in Firefox 26.  It does not work in Safari 6.  I haven't tested Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1428511594, 'spacePHID': None, 'dateCreated': 1391541420, 'dateModified': 1438734960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60839', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE stops responding while opening Media Settings for an image that contains another image', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add an image in the page\\n3.Open the Media Settings for that image\\n4.Insert another image inside it.\\n5.Apply Changes\\n6.Save the page\\n7.Reopen the page again\\n8.Open the media settings again for the image on the page\\n\\n\\nObserved Result:\\nVE stops reposnding.Cannot cross out the dialog box.\"Apply Changes\" does not close the dialog box.\\nAn error appears in the console\\nError: Offset could not be translated to a DOM element and offset: 22\\n\\t\\n\\n(297 out of range 182)\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/3rdfebFF?veaction=edit\\n\\nSee the screenshot attached,\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12818}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391651549, 'spacePHID': None, 'dateCreated': 1391467620, 'dateModified': 1443276301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60796', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Media Settings for an image is not opening when it is inside Reference dialog box or inside another media settings', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Insert an image and a reference\\n3.Open the Media Settings for the image and include another image\\n4.Click on the Media Settings icon on the second image that you just inserted\\nOR\\n5.Open the reference dialog box\\n6.Add an image inside\\n7.Click on the Media Settings icon on the image you just inserted\\n\\nObserved Result:\\nIn both cases after step 4 and step 7, Media Settings dialog box does not open up\\nIn the console following error appears:\\nNS_ERROR_NOT_AVAILABLE:\\n\\t\\n\\n...w Date()).getTime();}});jQuery.ready.promise=function(obj){if(!readyList){readyL...\\n\\nload.p...034436Z (line 11)\\n\\nSee the screenshot attached\\n\\n**This is happening in FireFox only** \\n\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/w/index.php?title=3rdfebFF&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13424}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391651533, 'spacePHID': None, 'dateCreated': 1391465040, 'dateModified': 1443276301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60788', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Empty gallery editor is getting inserted in a page when clicked on close button without adding any content', 'description': {'raw': 'screenshot of empty gallery in edit mode\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Go to Insert>Gallery\\n3.Just close the inspector\\n\\nObserved Result:\\nAn empty gallery inspector is getting added in the page\\n\\n\\nSee the screenshot attached.\\n\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:\\nhttps://test2.wikipedia.org/w/index.php?title=31st_january&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13379}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391660307, 'spacePHID': None, 'dateCreated': 1391456820, 'dateModified': 1443276303, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60779', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Fix dialog animation in Firefox', 'description': {'raw': 'Firefox also supports CSS3 animations and transitions, see how it can be done: http://tympanus.net/Development/ModalWindowEffects/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-b27lopawgf2h6utuuqyi', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394980634, 'spacePHID': None, 'dateCreated': 1391263200, 'dateModified': 1417572566, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60721', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After saving a page, the FlaggedRevs notice \"1 change in this version is pending review ...\" is not shown', 'description': {'raw': 'For wikis with FlaggedRevs extension: After saving a page the notice on top of page \"1 change in this version is pending review ...\" is not shown.\\n\\nI guess due to not reloading the whole page.\\n\\nThis is a bad experience for every editor w/o reviewer right. No chance to spot that the new revision has to be sighted first.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415911539, 'spacePHID': None, 'dateCreated': 1391255160, 'dateModified': 1417571679, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60718', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make it clear that invalid settings in the media dialog won\\'t be set when \"apply changes\" button is clicks', 'description': {'raw': 'Screenshot attached\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add any image \\n3.Go to Media Settings>Advanced Settings\\n4.Say for example the original dimension of the image is  150x150\\n5.Change the values in such way that it exceeds the original size for example: 300x300\\n\\nObserved Result:\\nApply Changes button remains active even though \"Size values are invalid \" appears in the dialog box.\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nSample Page:http://en.wikipedia.beta.wmflabs.org/wiki/29th_January?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F12971}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1540269111, 'spacePHID': None, 'dateCreated': 1391035980, 'dateModified': 1540331911, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60602', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Removing or breaking HTML tags (</small> and </code> tags vanish)', 'description': {'raw': 'Ex. #1, https://fr.wikipedia.org/w/index.php?title=%C3%89conomie_de_la_France&diff=100357906&oldid=100354236 , the </small> tag vanishes (the user said he fixed the spaces and removed a link);\\nex. #2, https://fr.wikipedia.org/w/index.php?title=Utilisateur:NemesisIII/Brouillon&diff=100052444&oldid=99902909 , the </code> tag misses the less-than sign (the user had just added a link);\\nex. #3, https://fr.wikipedia.org/w/index.php?title=Utilisateur:NemesisIII/Brouillon&diff=99902829&oldid=99228289 the same thing happens (the user just deleted a template).\\nSome curly brackets went missing as well.'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1437586955, 'spacePHID': None, 'dateCreated': 1391013480, 'dateModified': 1465905603, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60585', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add support for running headless browser tests to mediawiki-selenium Rubygem', 'description': {'raw': '**Author:** `jhall`\\n\\n**Description:**\\nFollow-up to a pairing session between Jeff and Željko on 1/29/2013.  In order to make headless browser testing available in as many WMF repositories as possible, we should add headless support[1] to the env.rb and hooks.rb setup in the mediawiki-selenium Rubygem[2].\\n\\n\\n[1] http://watirwebdriver.com/headless/\\n[2] https://git.wikimedia.org/tree/mediawiki%2Fselenium/ef67a1f40db97a7e0b456fcc3fbf20c6a8ec4e81/lib%2Fmediawiki%2Fselenium\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391433746, 'spacePHID': None, 'dateCreated': 1391012400, 'dateModified': 1391439349, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60584', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Gallery inspector/Link inspector opens with an animation from left to right for a specific case', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Select a reference note or a text and open the gallery inspector or a Link inspector\\n3.Close the inspector and go to the next line\\n4.Again go to Insert>Gallery or Open the link inspector\\n\\nObserved Result:\\nThe inspector opens up with an animation from left to right\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66552'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405375924, 'spacePHID': None, 'dateCreated': 1390861440, 'dateModified': 1441912042, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60501', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Diff styling in save dialog is broken', 'description': {'raw': \"Screenshot of the bug\\n\\nThe diff in the save dialog isn't being styled correctly, which causes highlighted text to overlap with text above it. Timo tells me that this is due to a missing line-height style.\\n\\nThis is exacerbated by bug 60494. which causes the save dialog to be narrower than it should be, which means lines wrap more often and highlighted text more frequently has text directly above it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13394}\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404168811, 'spacePHID': None, 'dateCreated': 1390859040, 'dateModified': 1417596390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60497', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Character inserter does not inherit annotations of context (no pre-annotation), so breaks up links, isn't styled, etc.\", 'description': {'raw': 'When adding a special character via the new tool,\\nthis will not retain styles applied to what was being typed; that is,\\nit will not appear for example in bold or italics.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409596478, 'spacePHID': None, 'dateCreated': 1390841520, 'dateModified': 1443278211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60476', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Stop users from deleting parameters in the template dialog if they\\'re marked as \"required\" in TemplateData', 'description': {'raw': 'Screenshot attached\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE \\n2.Go to Insert>Transclusion\\n3.Search for the template Cite Web\\n4.Observe that the required parameters are now marked with * symbol\\n5.Delete the required parameters\\n\\nObserved Result:\\n\\nThe required parameters gets deleted\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50747\\n\\n**Attached**: {F13028}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409263132, 'spacePHID': None, 'dateCreated': 1390435920, 'dateModified': 1615508693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60358', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create browser tests for using VE via Mobile UI', 'description': {'raw': '**Author:** `jhall`\\n\\n**Description:**\\nThe time has come to create additional VisualEditor browser tests for accessing VE via the Mobile interface.\\n\\nJames F had great feedback on which repo (MobilefrontEnd vs. VisualEditor) these tests belong in:\\n\\n\"\\u200bOne way of looking at it is on the blocking model. If (when!) these tests were to block merge, which repo\\'s changes should they be triggered by? In this case, I think there\\'s a case for some basic browser tests for VE-on-Mobile to be in VisualEditor (specifically, in the MediaWiki VisualEditor repo) with the major tests be in MobileFrontend.\"\\n\\nAn example URL for accessing VE via Mobile UI is: [1]\\n\\n\\n[1] http://en.m.wikipedia.beta.wmflabs.org/wiki/0.04730373828804457?mobileaction=alpha#editor/0\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1390322220, 'dateModified': 1643977431, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60290', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add a shortcut for strikethrough (?which?)', 'description': {'raw': 'Daniel on Mediawiki.org says they use strikethrough a lot and would like a shortcut for it.\\n'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1579113752, 'spacePHID': None, 'dateCreated': 1390231620, 'dateModified': 1579113752, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60257', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Provide a language inspector to handle <div lang='xx' dir='yyy'> blocks and similar\", 'description': {'raw': \"[Split from bug 47759 to cover block level items.]\\n\\nBug 47759 covers a language inspector to handle <span lang='xx' dir='yyy'>s, but for <div lang='xx' dir='yyy'> blocks and similar (like annotations on <ul>s or <li>s) we'll need a totally different editing concept.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1390006800, 'dateModified': 1643977431, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60187', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor on ptwikiversity and ptwikibooks for testing', 'description': {'raw': 'Opt-in state, per community member requesting.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://pt.wikibooks.org/wiki/Tópico:Wikilivros_Discussão:Portal_comunitário/Testes_com_o_Editor_Visual_no_Wikilivros'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391711278, 'spacePHID': None, 'dateCreated': 1389996660, 'dateModified': 1397521192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60182', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: No scroll bar appears in keyboard shortcut page after resizing the window', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Open VE for a page\\n2.Now resize the window down\\n2.Go to Settings>Keyboard shortcuts\\n\\nObserved Result:\\nThere is no scroll bar in this window therefore cannot see the last line of it as it is getting cut off.\\n\\nSee the screenshot\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13257}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393880384, 'spacePHID': None, 'dateCreated': 1389992460, 'dateModified': 1443276308, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60180', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Deploy TemplateData's GUI editing tool to all wikis\", 'description': {'raw': \"Once we're happy with it. Currently feature-flagged off.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415298271, 'spacePHID': None, 'dateCreated': 1389930720, 'dateModified': 1415298271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60158', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide a way to have a demo directory alongside the documentation on doc.wikimedia.org', 'description': {'raw': \"The OOjs UI library has a useful demos directory, which shows off each of the widgets available. Similarly, VisualEditor also has a demos directory, and I imagine other projects do (or would if it became an established pattern.\\n\\nIt would be really great if we could somehow expose these alongside their projects' documentation, so we can point people to a living thing rather than telling them to checkout the repo and play. Something like…\\n\\nhttps://doc.wikimedia.org/visualeditor/master/\\nhttps://doc.wikimedia.org/visualeditor/master/demo/\\n\\nhttps://doc.wikimedia.org/visualeditor/v0.1.0/\\nhttps://doc.wikimedia.org/visualeditor/v0.1.0/demo/\\n\\nhttps://doc.wikimedia.org/oojs-ui/master/\\nhttps://doc.wikimedia.org/oojs-ui/master/demos/\\n\\nhttps://doc.wikimedia.org/oojs-ui/v1.0.6/\\nhttps://doc.wikimedia.org/oojs-ui/v1.0.6/demos/\\n\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1438801669, 'spacePHID': None, 'dateCreated': 1389900720, 'dateModified': 1438801669, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60143', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Math inspector live preview double-escapes angle brackets', 'description': {'raw': \"1. Create a new math node (Insert -> Formula)\\n2. Type L' = \\\\{\\\\<x, \\\\underbrace{1111\\\\dots1111}_{s(|x|)}0\\\\> | x \\\\in L\\\\} into the input box\\n3. Observe &lt; and &gt; in the preview :(\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404431099, 'spacePHID': None, 'dateCreated': 1389829140, 'dateModified': 1417572124, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60113', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Selecting nodes (references/images/templates) on iOS < 8 causes the on-screen keyboard to close, so they cannot be deleted', 'description': {'raw': \"Intention:\\nDelete a template.\\n\\nSteps to Reproduce:\\n1. Open an article containing a template.\\n2. Select the template.\\n3. Try to press the delete key on the now-non-existent keyboard.\\n\\nActual Results:  \\nThe keyboard closes, so you can't delete them.\\n\\n\\nReproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67390\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1439318726, 'spacePHID': None, 'dateCreated': 1389825480, 'dateModified': 1643389817, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60110', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Namespace mixin properties', 'description': {'raw': 'Especially now that we have mixins adding properties with very generic names like this.min and this.max (ResizeableNode), we should look at namespacing them. Maybe an object to contain them all, like this.resizeableNode = { min: 1, max: 1000 }; ?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1389822180, 'dateModified': 1643977431, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60108', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Zuul: python git assert error assert len(fetch_info_lines) == len(fetch_head_info)', 'description': {'raw': 'Spotted by EdSanders on https://gerrit.wikimedia.org/r/#/c/107036/\\n\\n\\n2014-01-12 14:29:20,163 INFO zuul.IndependentPipelineManager: Change <Change 0x7f30084dcf10 107036,1> depends on changes []\\n2014-01-12 14:29:20,165 DEBUG zuul.Repo: Resetting repository /srv/ssd/zuul/git/mediawiki/extensions/VisualEditor\\n2014-01-12 14:29:20,165 DEBUG zuul.Repo: Updating repository /srv/ssd/zuul/git/mediawiki/extensions/VisualEditor\\n2014-01-12 14:29:24,064 DEBUG zuul.Repo: Checking out master\\n2014-01-12 14:29:26,280 DEBUG zuul.Merger: Unable to merge <Change 0x7f30084dcf10 107036,1>\\nTraceback (most recent call last):\\n  File \"/usr/local/lib/python2.7/dist-packages/zuul/merger.py\", line 206, in _mergeChange\\n    repo.merge(change.refspec, \\'resolve\\')\\n  File \"/usr/local/lib/python2.7/dist-packages/zuul/merger.py\", line 97, in merge\\n    self.fetch(ref)\\n  File \"/usr/local/lib/python2.7/dist-packages/zuul/merger.py\", line 111, in fetch\\n    origin.fetch(ref)\\n  File \"/usr/lib/python2.7/dist-packages/git/remote.py\", line 593, in fetch\\n    return self._get_fetch_info_from_stderr(proc, progress or RemoteProgress())\\n  File \"/usr/lib/python2.7/dist-packages/git/remote.py\", line 539, in _get_fetch_info_from_stderr\\n    assert len(fetch_info_lines) == len(fetch_head_info), \"len(%s) != len(%s)\" % (fetch_head_info, fetch_info_lines)\\nAssertionError: len([\"3d35f5b84a26171535e869fed4a1c73dbeaeec69\\\\t\\\\t\\'refs/changes/36/107036/1\\' of ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor\\\\n\"]) != len([\\'Total 9 (delta 7), reused 9 (delta 7)\\', \\' * branch            refs/changes/36/107036/1 -> FETCH_HEAD\\'])\\n2014-01-12 14:29:26,318 INFO zuul.IndependentPipelineManager: Unable to merge change <Change 0x7f30084dcf10 107036,1>\\n2014-01-12 14:29:26,319 DEBUG zuul.IndependentPipelineManager: Reporting change <Change 0x7f30084dcf10 107036,1>\\n2014-01-12 14:29:26,319 INFO zuul.IndependentPipelineManager: Reporting change <Change 0x7f30084dcf10 107036,1>, actions: [<ActionReporter <zuul.reporter.gerrit.Reporter object at 0x25821d0>, {\\'verified\\': -1}>]\\n2014-01-12 14:29:26,319 DEBUG zuul.reporter.gerrit.Reporter: Report change <Change 0x7f30084dcf10 107036,1>, params {\\'verified\\': -1}, message: Build failed.\\n\\nThis change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset.\\n\\n\\n\\nThere is a few occurrences in the Zuul debug log: fgrep assert /var/log/zuul/debug*\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1446722644, 'spacePHID': None, 'dateCreated': 1389609900, 'dateModified': 1452717530, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59991', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Exception thrown placing cursor at end of document with no content offsets', 'description': {'raw': '1. Create a document with just a block image [[File:Foo.jpg|thumb]] on one line\\n2. Edit the document and try to place the cursor in the second slug (after the image)\\n3. An exception is thrown (getNearestContentOffset(selection.end) returns -1 and this is fed into getAnnotationsFromOffset)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389642948, 'spacePHID': None, 'dateCreated': 1389539280, 'dateModified': 1443276310, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59972', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikitext is appearing in the readmode for the numbered list and bullet list that is inside reference dialog box', 'description': {'raw': 'In the read mode\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a reference to a text by going to Insert>Reference\\n3.When the reference dialog box opens up insert a numbered list and then type the reference for example as: 1.reference\\n4.Click on \"Insert Reference\"\\n5.Save the page\\n\\nObserved Result:\\nIn the read mode,the serials of the numbered list are appearing in wikitext with #.\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Jan7th\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12322}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391650611, 'spacePHID': None, 'dateCreated': 1389122340, 'dateModified': 1443276313, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59781', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Special Character option remains selected even after closing the window', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Select Insert>Special Character\\n3.Close the special character window.\\n4.Go to Insert option in the toolbar\\n\\nObserved Result:\\nThe Special Character option is still appearing selected even after closing the window\\n\\nSee the screenshot attached.\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Jan7th?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12316}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389900742, 'spacePHID': None, 'dateCreated': 1389120960, 'dateModified': 1443276314, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59779', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"mediawiki/extensions.git is broken again (so VisualEditor isn't getting updated on betalabs)\", 'description': {'raw': 'Bug 49846 was this happening last time around. Possibly the same cause.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389149751, 'spacePHID': None, 'dateCreated': 1389084780, 'dateModified': 1389149751, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59758', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add tooltips to drop-down menus', 'description': {'raw': 'Especially if the icon for a menu button is a mere symbol, add a tooltip to that button (i.e., the three-bars icon).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392253940, 'spacePHID': None, 'dateCreated': 1389017400, 'dateModified': 1443276317, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59719', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Use multipart/form-data encoding when POSTing HTML', 'description': {'raw': 'Per Gabriel\\'s report via email, when VE POSTs HTML, it uses multipart/x-www-urlencoded to encode the POST body, which results in a lot of URL-encoding of special characters (especially <>\") in the HTML. We should instead use multipart/form-data , which is more efficient for such large POST bodies with many special characters.\\n\\nTODO: Figure out how to tell the browser to use this encoding when sending an AJAX request.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389825540, 'spacePHID': None, 'dateCreated': 1388891640, 'dateModified': 1570755337, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59660', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Can't add new paragraphs to the end of the page, if the last line is an empty section heading == <nowiki/> ==\", 'description': {'raw': 'Intention:\\nAdd a new paragraph at the bottom of a page that ended in == <nowiki/> == (not counting the category after the empty section heading).\\n\\nI was hoping that adding a new paragraph underneath the blank section heading would allow me to select, and therefore to remove, the blank section heading.\\n\\n\\nSteps to Reproduce:\\n1. Edit a page that ends in a == <nowiki/> ==, like https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox2&oldid=589158823\\n\\n2. Place the cursor in the empty section heading.\\n\\n3. Hit return.\\n\\nActual Results:  \\nPressing return adds blank paragraphs *above* the empty section heading. \\n\\nIf you type anything into the section heading, then it starts behaving normally.\\n\\nExpected Results:  \\nDoing the same thing for an empty (or non-empty) section heading anywhere else on the page adds new paragraphs *under* the empty section heading.  Pressing return in a section heading should produce the same behavior everywhere on the page.\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410802281, 'spacePHID': None, 'dateCreated': 1388854920, 'dateModified': 1443278211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59652', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] On FlaggedRevs wikis: Checkbox \"Accept this version (includes n pending changes)\" in save dialog is missing', 'description': {'raw': 'On FlaggedRevs wikis: Checkbox \"Accept this version (includes n pending changes)\" in save dialog is missing\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63600'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397879986, 'spacePHID': None, 'dateCreated': 1388780520, 'dateModified': 1443276319, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59608', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: adding a reference duplicates infobox on da.wp', 'description': {'raw': \"https://da.wikipedia.org/w/index.php?title=F-35_Lightning_II&diff=prev&oldid=7409486\\nand\\nhttps://da.wikipedia.org/w/index.php?title=Enhedslisten&diff=prev&oldid=7414100 seem a few examples of what the title says. \\n\\nI couldn't reproduce because of {T61599}.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See also**: {T51823}\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437602943, 'spacePHID': None, 'dateCreated': 1388769180, 'dateModified': 1439331264, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59600', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make it more obvious when the user is doing something foolish with links (e.g. extending the wrong one)', 'description': {'raw': 'Minor corruption:\\n\\n<https://www.mediawiki.org/w/index.php?title=Architecture_Summit_2014/Straw_poll&diff=870066&oldid=870065&diffonly=1> and <https://www.mediawiki.org/w/index.php?title=Architecture_Summit_2014/Straw_poll&diff=870064&oldid=870063&diffonly=1>\\n\\nMore serious corruption:\\n\\n<https://www.mediawiki.org/w/index.php?title=Architecture_Summit_2014/Straw_poll&diff=870067&oldid=870066&diffonly=1>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1443035624, 'spacePHID': None, 'dateCreated': 1388701200, 'dateModified': 1443035624, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59229', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying part of a table into an existing cell should over-write cell values, not insert it as a sub-table', 'description': {'raw': 'Steps to reproduce:\\n\\n1) Begin with an existing wikitext table (e.g., 4 rows, 4 columns).  Open the page in VisualEditor.\\n\\n2) Copy part of a different table or spreadsheet (e.g., 2 rows, 4 columns).\\n\\n3) Place cursor inside a cell of the table in VisualEditor.\\n\\n4) Paste the copied table.\\n\\n\\nResults:\\n\\nVisualEditor places the entire new/rich-copied table, including wikitext formatting, inside the first cell.  The wikitext parser does not deal very gracefully with table-within-table formatting.\\n\\n\\nDesired outcome:\\n\\nVisualEditor should overwrite the contents of the cells with the new material.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/w/index.php?diff=588462959&oldid=588405367#Create_and_copy_table.'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1454136210, 'spacePHID': None, 'dateCreated': 1388613660, 'dateModified': 1454539180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59192', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'mw.user.tokens does not include all token types', 'description': {'raw': 'mw.user.getToken only supports edit, watch and patrol.\\nIt should support all other types of token.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1571098112, 'spacePHID': None, 'dateCreated': 1388444160, 'dateModified': 1571098112, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59148', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copy paste is not working for Math elements', 'description': {'raw': 'screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Open a page using VE in Chrome browser.\\n2.Copy a math function or item from that page\\n3.Open another page with VE in FireFox\\n4.Paste the copied math item in this page\\n\\nObserved Result:\\nThe math item does not get copied and in the console there is an error appearing:\\n TypeError:Item is undefined\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12369}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1442495255, 'spacePHID': None, 'dateCreated': 1388093400, 'dateModified': 1442495255, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58981', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The link is appearing within [] bracket with lock icon after copy-paste from another VE in Firefox', 'description': {'raw': 'screenshot of the link after copy paste\\n\\nSteps to reproduce:\\n\\n1.Open an editor in Firfox which contains a link\\n2.Copy the link \\n3.Paste it into another VE and save it\\n\\nObserved Result:\\nThe link is appearing within [] bracket and with a lock icon beside it.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12199}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389902753, 'spacePHID': None, 'dateCreated': 1387823880, 'dateModified': 1443276326, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58902', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding newlines at start/end of preformatted text is broken', 'description': {'raw': '[14:38] <gwicke> in native CE shift-enter inserts a newline in a pre\\n[14:38] <gwicke> normal enter splits it\\n[14:40] <gwicke> woah: shift-enter actually works in VE as long as it is not on the last line of a pre\\n[14:41] <gwicke> it does not work when the cursor is on the first or last char in a pre\\n[14:41] <gwicke> before first char a paragraph is inserted before the pre\\n[14:41] <gwicke> after last char a paragraph is inserted after the pre and the cursor moves there\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1657241327, 'spacePHID': None, 'dateCreated': 1387579680, 'dateModified': 1657241327, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58773', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Pasting formulæ isn't working in Firefox\", 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Create a new page in FF\\n2.Copy a math function from another VE \\n3.Paste it in this new page\\n4.Click on Save Page\\n\\nObserved Result:\\n\"Error: Creating new, empty pages is not allowed\" appears\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12772}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437756695, 'spacePHID': None, 'dateCreated': 1387577640, 'dateModified': 1439331258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58767', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Math formula does not appear immediately after copy-paste in test2', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the editor for a page\\n2.Open the latex window and insert \"\\\\sqrt\\\\pi\"\\n3.Click on the \"<\" button to close the latex window\\n4.Copy the formula immediately\\n5.Paste it onto another page\\n\\nObserved Result:\\nThe math elements does not appear on the page after pasting.However after saving it appears there are multiple of those \\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/19th_december?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415881871, 'spacePHID': None, 'dateCreated': 1387485660, 'dateModified': 1417571680, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58713', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'New line at end of document sometimes merged into previous line on paste', 'description': {'raw': 'Copied from bug 58347:\\n\\n1.Create a page \"A\" with three links in three consecutive lines.\\n2.Create another page \"B\" where you will copy these links to.\\n3.Copy the first and second link to \"B\"\\n4.Save it.\\n5.Reopen the editor.\\n6.Now copy the third link and paste it to the third line of \"B\"\\n7.Save it.\\n\\nObserved Result:\\nThe second and the third link in page B is getting merged.\\n\\nExample Pages:\\n\\nA:http://en.wikipedia.beta.wmflabs.org/wiki/19th_december_source?veaction=edit\\nB:http://en.wikipedia.beta.wmflabs.org/wiki/19th_destination\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1387471560, 'dateModified': 1436300030, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58695', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Add property to indicate in which namespaces a template should be used', 'description': {'raw': \"**Author:** `prlpz`\\n\\n**Description:**\\nI suggest including in TemplateData a field about the namespaces where the template is intended to be used. VisualEditor should use this field to suggest the template only in the right namespaces.\\n\\nFor example, nowadays VisualEditor suggest using template documentation templates while editing articles, but such templates should only be used in template namespace. TemplateData could make VisualEditor know that those templates shouldn't be suggested there.\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-yawytiq5q7eduxmvnkid', 'dateClosed': 1622009833, 'spacePHID': None, 'dateCreated': 1387393320, 'dateModified': 1622009833, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58656', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Generate CSS docs from LESS and publish to doc.wikimedia.org', 'description': {'raw': \"Core has a build system to generate HTML from kss-formatted CSS/LESS (docs/kss). It would be nice if this documentation appeared in doc.wikimedia.org along with other generated documentation.\\n\\nThis sounds like T50337. Presumably there's some Zuul job somewhere building the doc that appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'dateClosed': 1532486031, 'spacePHID': None, 'dateCreated': 1387336620, 'dateModified': 1532486031, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58620', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Computed href in Firefox normalises ' ' to '%20'\", 'description': {'raw': \"This causes the test 'document with meta elements: data' in ve.dm.MWConverter to fail. Not sure if it is any more serious than that.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1387307700, 'dateModified': 1574099357, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58586', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cut and Paste of references occasionally fails', 'description': {'raw': 'Occasionally, cut and paste of text that includes a reference will fail in a weird way. I was able to isolate one reproducible case: \\n\\n1. The article contains text S, followed by a reference for S, some more text T, followed by a reference for T.\\n\\n2. We cut (Ctrl-X) part or all of text T, including its reference.\\n\\n3. We paste (Ctrl-V) somewhere in the middle of text S (*not* at the beginning of S)\\n\\nResult: the article view is scrolled to the top, the pasted text is in wrong order, all of a sudden we have three references.\\n\\nSee https://www.mediawiki.org/wiki/VisualEditor:TestAxelBoldt#Regression_15:_Cut.2FPaste_of_references for a sandbox where you can try it out.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1436503698, 'spacePHID': None, 'dateCreated': 1387229820, 'dateModified': 1439331253, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58552', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor in the Reports namespace on officewiki', 'description': {'raw': \"Per Guillaume's request on IRC. This is namespace 100.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387324738, 'spacePHID': None, 'dateCreated': 1387226280, 'dateModified': 1387324738, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58547', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: removeHtmlAttributes throws an exception when copying complex templates', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open the editor.\\n2.Add a template\\n3.Save the page\\n4.Reopen the editor\\n5.Copy the template \\n\\nObserved Result:\\n\\nIt gives an error:Uncaught TypeError: Cannot convert null to object .However, it does get pasted correctly onto other VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386990710, 'spacePHID': None, 'dateCreated': 1386890940, 'dateModified': 1417572679, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58421', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The active template sprite stays at the same place when a window is resized', 'description': {'raw': 'To reproduce:\\n\\n1. Edit a page with a template.\\n2. Click the template so the darker blue sprite appears.\\n3. Resize the window.\\n\\nObserved: The transparent blue sprite stays at the same place on the screen.\\n\\nExpected: The transparent blue sprite should move to the new location of the template of the screen.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394223139, 'spacePHID': None, 'dateCreated': 1386863460, 'dateModified': 1417572581, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58395', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <visualeditor-toolbar-insert> is showing up in the toolbar instead of \"Insert\" in betalabs', 'description': {'raw': 'screenshot\\n\\n<visualeditor-toolbar-insert> is showing up in the toolbar instead of More in betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11989}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386821225, 'spacePHID': None, 'dateCreated': 1386806520, 'dateModified': 1386982882, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58360', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'opensearch: Querying for \"Big\" or \"Big!\" should include \"Big\" or \"Big!\" as first suggestion', 'description': {'raw': 'The following pages all exist on en.wikipedia.org:\\n\\n* [[Bird]]\\n* [[Big]]\\n* [[Big!]]\\n* [[Big Ten Conference]]\\n\\nWhen querying action=opensearch for:\\n\\n* \"Bir\": 0 => \"Bird\"\\n   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Bir\\n   [input,[\"Bird\",\"Birmingham\",..]]\\n\\n* \"Bird\": 0 => \"Bird\"\\n   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Bird\\n   [input,[\"Bird\",\"BirdLife International\",..]]\\n\\n* \"Big\": \\n   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Big\\n   [\"Big\",[\"Big Ten Conference\",\"Big band\",...]]\\n\\n* \"Big\": \\n   https://en.wikipedia.org/w/api.php?format=json&action=opensearch&namespace=0&search=Big!\\n   [\"Big!\",[\"Big Ten Conference\",\"Big band\",...]]\\n\\nIn the last two, \"Big\" and \"Big!\" are nowhere in the response.\\n\\nFiling against Wikimedia for now, because this seems related to one of our search backends, not plain MediaWiki core or plain MediaWiki core with Extension:TitleKey installed.\\n\\nThis is currently causing issues in VisualEditor when making a link to a page called \"Big\", or \"Big!\" as it will think the page doesn\\'t exist and suggest to make a red link, as, thus far, we\\'ve always assumed that if a page by the exact title exists, it should be the first suggestion.\\n\\nIt normalising casing and/or special characters is fine, but shouldn\\'t make it not give an exact match as first result.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**Whiteboard**: cirrus-fixed'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1478802678, 'spacePHID': None, 'dateCreated': 1386736380, 'dateModified': 1478802678, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58309', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: HTML non-breaking spaces (&nbsp;) converted to \",[object Object], ,[object Object],\"', 'description': {'raw': \"Reproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://en.wikipedia.org/w/index.php?title=Toronto_Maple_Leafs&diff=585067098&oldid=584791615\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429612070, 'spacePHID': None, 'dateCreated': 1386701940, 'dateModified': 1429612070, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58282', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Add a lint job for JSON', 'description': {'raw': \"We're seeing more and more JSON files entering our repos, and there is an RfC in discussion[1] to move to JSON files for our localisation.\\n\\nPlease add standard JSON linting when patch sets that have Jenkins jobs configured.\\n\\n[1] https://www.mediawiki.org/wiki/Requests_for_comment/Localisation_format\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-w5a723w3wes6jd5wskgg', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1420725969, 'spacePHID': None, 'dateCreated': 1386696900, 'dateModified': 1420726011, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58279', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make the media dialog one dialog again', 'description': {'raw': 'Merge MWMediaInsertDialog and MWMediaEditDialog into one dialog that has an insert page and an edit page, and a BookletLayout without an outline. This way we can switch between modes without closing one dialog and opening another.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412590279, 'spacePHID': None, 'dateCreated': 1386638100, 'dateModified': 1417571698, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58245', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Tool Labs: Provide anonymized view of the user_properties table', 'description': {'raw': 'Toolserver has a limited and anonimized view of the user_properties table available. This is used for reports like https://en.wikipedia.org/wiki/Wikipedia:Database_reports/User_preferences\\n\\nmysql> describe user_properties;\\n| Field       | Type           | Null | Key | Default | Extra |\\n| -----  | -----  | -----   | ----- | ----- | ----- |\\n| up_user     | int(11)        | NO   |     | 0       |       |\\n| up_property | varbinary(255) | YES  |     | NULL    |       |\\n| up_value    | blob           | YES  |     | NULL    |       |\\n3 rows in set (0.00 sec)\\n\\nmysql> describe user_properties_anonym;\\n| Field                   | Type           | Null | Key | Default | Extra |\\n| -----  | -----  | -----   | ----- | ----- | ----- |\\n| up_property             | varbinary(255) | YES  |     | NULL    |       |\\n| up_value                | blob           | YES  |     | NULL    |       |\\n| ts_user_touched_cropped | varbinary(8)   | NO   |     |         |       |\\n3 rows in set (0.00 sec)\\n\\nOnly preferences that are considered to be public are replicated, the list from enwiki_p is:\\nmysql> select distinct(up_property) from user_properties;\\n| up_property    |\\n| -----  |\\n| disablemail    |\\n| fancysig       |\\n| gender         |\\n| language       |\\n| nickname       |\\n| skin           |\\n| timecorrection |\\n| variant        |\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\n* {T27302}\\n* {T21288}'}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'dateClosed': 1448850365, 'spacePHID': None, 'dateCreated': 1386566220, 'dateModified': 1496862111, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58196', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If copying from one VE instance to another, pasted links result in broken wikitext (external URL, internal link format)', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Open the editor for a page which contains a link\\n2.Copy the link\\n3.Now open VE for another article and paste the copied link onto it\\n4.Save the page\\n\\n\\nObserved Result:\\n\\nThe copied link appears as a plain text on the read mode where as in the Edit Source/Edit mode it appears as a link\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58138'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390442043, 'spacePHID': None, 'dateCreated': 1386376320, 'dateModified': 1443276330, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58136', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The icon for underline option is missing in betalabs', 'description': {'raw': 'screenshot\\n\\nThe icon for underline option is missing in betalabs:http://en.wikipedia.beta.wmflabs.org/wiki/The_link?veaction=edit\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12362}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386370145, 'spacePHID': None, 'dateCreated': 1386364620, 'dateModified': 1417572740, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58119', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <ooui-toolbar-more> is showing up instead of More button in betalabs', 'description': {'raw': 'Screenshot\\n\\n<ooui-toolbar-more> is showing up instead of More button in betalabs\\nhttp://en.wikipedia.beta.wmflabs.org/wiki/6th_december?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12338}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386392274, 'spacePHID': None, 'dateCreated': 1386356940, 'dateModified': 1386392274, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58109', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: History actions should scroll the location of the transaction into view (unless it's a meta-data transaction which has no location?)\", 'description': {'raw': '**Author:** `Wikifram`\\n\\n**Description:**\\nWhen you have made changes to a page in VE, you can use the \"undo\" button to reverse these. However, the page doesn\\'t scroll when doing this, so you don\\'t \"see\" what the undo is actually doing. The same probably applies to the \"redo\" button, I haven\\'t checked that one\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51911'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1456235332, 'spacePHID': None, 'dateCreated': 1386321060, 'dateModified': 1461807078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58091', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Auto context links (#contentSub) under the title in the User: namespace is only hidden, not suppressed, so can still be clicked', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the VE for a page in a User's namespace\\n2.Hover your mouse over the position where the link to user namespace appears in the Read mode.\\n3.Click on that position\\n\\nObserved Result:\\nIt redirects to user namespace from VE.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52243\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54325\\n\\n**Attached**: {F12247}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390607922, 'spacePHID': None, 'dateCreated': 1386288540, 'dateModified': 1443276334, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58063', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting a hieroglyphics block when the cursor is in the middle of a link causes a broken inspector to show, newline to be inserted', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open the editor\\n2.Place the cursor in the middle of a text\\n3.Then click on More>Hieroglyphics\\n4.The inspector does not open just the < icon in that position.\\n5.Save the page\\n6.Reopen the editor.\\n\\n\\nObserved Result:\\nThe text after that cursor position gets shifted to the newline and a return arrow appears after reopening the editor.\\n\\nFor a text which is not link it just goes to the next line but the return arrow does not get added.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12190}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410033747, 'spacePHID': None, 'dateCreated': 1386269880, 'dateModified': 1417571847, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58047', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Creating a formula/hieroglyphics insert while selecting an image tries to modify the caption, dies', 'description': {'raw': \"Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open the editor.\\n2.Select an image\\n3.Select the option More>Latex/Hieroglyphics\\n\\nObserved Result:\\n\\nA small input window opens up over the window where text can be inserted.\\n\\nIn the console I get the following error:\\nUncaught TypeError: Cannot read property 'body' of undefined load.php:521\\nve.ui.MWExtensionInspector.setup load.php:521\\n(anonymous function) load.php:113\\nproxy load.php:10\\nlistenerWrapper load.php:98\\noo.EventEmitter.emit load.php:98\\n(anonymous function) load.php:110\\npollExternalStylesheets\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60804\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56644\\n\\n**Attached**: {F12183}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398385287, 'spacePHID': None, 'dateCreated': 1386268980, 'dateModified': 1443276334, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58045', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Cursoring off the page with left/right doesn't scroll the cursor in to view\", 'description': {'raw': 'Contrast with up/down which always keeps the cursor in view.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68708'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1443036355, 'spacePHID': None, 'dateCreated': 1386258480, 'dateModified': 1443036355, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58038', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'S2. Flow API: Let code add a new topic with action=edit&section=new', 'description': {'raw': \"LQT intercepts section=new from users to add a new thread (but not via the API, see bug 41276). It'd be really awesome if Flow could let you add a new topic like this, using the old API.\\n\\nhttps://www.mediawiki.org/wiki/API:Edit#Example\\n\\n--------------------------\\n**See Also**: \\n* {T43276}\\n* {T85197}\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '2', 'subtype': 'default', 'closerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'dateClosed': 1426116024, 'spacePHID': None, 'dateCreated': 1386178920, 'dateModified': 1442537056, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57989', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting a reflist along with some content and saving the page keeps the previous the content on the page', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit button for a page\\n2.Type two paragraphs\\n3.Add a text with reference\\n4.Add a reflist\\n5.Save the page\\n6.Re-open the editor\\n7.Delete the reference and the reflist and the second paragraph\\n8.Save the page\\nObserved Result:\\nThe second paragraph and the text with reference did not get deleted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387299214, 'spacePHID': None, 'dateCreated': 1386119340, 'dateModified': 1417572681, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57956', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Print/Export tools are enabled while editing', 'description': {'raw': 'Actual Results:  \\nWhen you open VisualEditor, the Print/Export section in the sidebar is still present.  It is not displayed when you open the same page in the wikitext editor.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398296787, 'spacePHID': None, 'dateCreated': 1386098520, 'dateModified': 1443276335, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57940', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deactivating editor after activating by url query leaves veaction=edit', 'description': {'raw': 'screenshot\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit beta button\\n2.Switch to Edit Source\\n3.Switch back to VE\\n4.Click on Cancel\\n5.Reload the page\\n\\n\\nObserved Result:\\nEven after cancelling the edit, in the URL \"&veaction=edit\" still remains appended , therefore after reloading the page, VE opens up.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F12776}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394659856, 'spacePHID': None, 'dateCreated': 1386028200, 'dateModified': 1443276336, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57901', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Ref name \":0\" appears in the dialog box of adding existing reference which has repeated citations', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Click on Edit for a page\\n2.Add a reference\\n3.Use same reference multiple times in the page\\n4.Now again while adding reference click on \"Use an Existing reference\"\\n\\nObserved Result:\\nOn this dialog box beside the reference [1] the ref name \":0\" appears.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12716}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391648680, 'spacePHID': None, 'dateCreated': 1386013680, 'dateModified': 1463358964, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57875', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing \"undo\" deletes the content of an article making the \"save page\" button disable for that session', 'description': {'raw': 'Screenshot of the error\\n\\nSteps to reproduce:\\n\\n1.Click on the \"Edit\" button for a page\\n2.Type something with a link on the main page\\n3.Add a template for example:Bronze Age\\n4.Add another line with a reference\\n5.Add reflist to the article\\n6.Save the page\\n7.Reopen the editor\\n8.Press Delete (Deletes the first line)\\n9.Press Delete again (Nothing happens)\\n10.Press Undo\\n\\nObserved Result:\\n\\n1.Deletes all the content of the article.\\n2.Only the blue empty highlighted box remains at the right\\n3.Save Page button becomes disabled\\n4.Make further edit but still the \"Save Page\" button remains disabled for that session\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12501}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410461760, 'spacePHID': None, 'dateCreated': 1385853780, 'dateModified': 1443278215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57784', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: newFromDocumentInsertion not implemented properly for reference/media insertions', 'description': {'raw': \"Currently inserting a new reference fails because of changes to newFromDocumentInsertion. The first thing that looks wrong is that the 'empty' document we generate for new references/media captions contains one paragraph and an empty internal list, I suspect we need to copy the existing internal list over.\\n\\nEven with that fixed it appears we aren't generating the correct sequence of transactions so they need to be reviewed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386931739, 'spacePHID': None, 'dateCreated': 1385836200, 'dateModified': 1417572735, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57778', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: All metadata moved from bottom of the page into a reference', 'description': {'raw': \"On fr.wp, see:\\nhttps://fr.wikipedia.org/w/index.php?title=Indicateur_du_d%C3%A9veloppement_durable&diff=98505933&oldid=98352104\\n\\nhttps://fr.wikipedia.org/w/index.php?title=Dan_Flavin&diff=prev&oldid=98639433\\n\\nSomehow, categories (and in one case, DEFAULTSORT) move from the bottom of the page and get inside a reference.\\n\\nI'll very roughly translate for you the comment of Drongou, who tried to replicate but didn't manage to:\\n\\n<<I can't reproduce this bug (on Mac OS X) but what they have in common is the suppression of a template at the top of the page. For the reference, I have tried to manipulate one several times but that didn't lead to anything. Since it's always the first reference which is affected, I think this [...] is probably due to the template being deleted but not in an usual way. Regards.>>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-unpoeiyj52rmcfqi5rbw', 'dateClosed': 1697897193, 'spacePHID': None, 'dateCreated': 1385747760, 'dateModified': 1697897193, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57753', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Expand commands (keyboard shortcuts) to target level commands', 'description': {'raw': \"Currently commands are executed on the surface, and don't fire at all when not in a surface context (e.g. a dialog), however we want to have target level shortcuts (save, show menu, show help, etc.) that don't just fire when the document is fired.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401473606, 'spacePHID': None, 'dateCreated': 1385674920, 'dateModified': 1443276337, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57723', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Review mediawiki.ApiRequest.js to ensure that DoesNotExistError logging is useful and informative in all cases.', 'description': {'raw': 'We are trying to debug a failure with the way parsoid is set up in the Labs-Vagrant visualeditor role setup\\n<https://wikitech.wikimedia.org/wiki/Talk:Labs-vagrant#Parsoid_errors_using_VisualEditor_role>\\n\\nWhen the client gets 404 errors, the error in /var/log/upstart/parsoid.log is just \\n  ERROR in localhost:Main_Page\\n  Stack trace: DoesNotExistError: Page Fetch failure for null\\n  worker 25269 died (1), restarting.\\n\\nbut it doesn\\'t say what the error is.\\nebernhardson tweaked the second line to actually say what\\'s going wrong by adding error to the output, so the second line becomes\\n\\n  Stack trace: DoesNotExistError: Page Fetch failure for null : Error: Invalid URI \"undef/w/api.php?format=json&action=query&meta=siteinfo&siprop=namespaces%7Cnamespacealiases%7Cmagicwords%7Cfunctionhooks%7Cextensiontags%7Cgeneral%7Cinterwikimap%7Clanguages%7Cprotocols\"\\n\\n, and now we can get somewhere :)\\n\\nTwo-line patch on its way\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386966100, 'spacePHID': None, 'dateCreated': 1385598780, 'dateModified': 1386966100, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57694', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pre-annotation in a block slug should never read from the next character', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button.\\n2.Add a template to a page.\\n3.Add another template on it.\\n4.Type something on the next line of second template and format it to Preformatted ,Bold,Italic,Subscript/Underlined.\\n5.Now type something between the two templates.\\n\\nObserved Result:\\nThe text added between two templates takes the format of the next line to the second template.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12332}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409596597, 'spacePHID': None, 'dateCreated': 1385588100, 'dateModified': 1417571852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57685', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save dialog not torn down properly after edit', 'description': {'raw': 'Consequently the second time you edit a page, it thinks the save dialog already exists so it isn\\'t set up again, and it fails to render.\\n\\nWe should add a \"double edit\" workflow to our Selenium or manual tests.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386026721, 'spacePHID': None, 'dateCreated': 1385559240, 'dateModified': 1417572743, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57654', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adjacent lists should be easily joinable', 'description': {'raw': \"It is quite easy to create two adjacent lists that appear to be one list (but for a small amount of extra spacing) through copy/paste or deletion. More often than not this is not what the user means semantically, so such a situation should be highlighted to the user and they should be given an easy way to fixup the code.\\n\\nI have yet to see an editor which does this well, but that shouldn't stop us being the first.\\n\\n==Steps to reproduce==\\nJust as a helpful example.\\n\\n1. Create a list.\\n1. Decide to end the list by pressing enter while on a blank bullet.\\n1. Change your mind and decide to continue the list by clicking the list buttons.\\n1. Now the document has two separate lists, but your mental model only has one.\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1385558520, 'dateModified': 1443036604, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57653', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: External paste of list into list should unwrap pasted list', 'description': {'raw': 'Currently pasting a list into a list creates a sub-list. From a technical point of view this is correct (the paste contents will always be a full list) but from a user expectation point of view this will be wrong 99% of the time, so we should unwrap the pasted list so it flattens to the same list level as the target.'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1385558160, 'dateModified': 1443041623, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57652', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: There should be tests asserting we use code points as opposed to grapheme clusters', 'description': {'raw': \"Timo astutely observed that no tests had to be changed in https://gerrit.wikimedia.org/r/#/c/80689 despite the change from grapheme clusters to code points. I share his feeling that there should have been tests that would have been broken by that change. It's never too late to write some :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1385507220, 'dateModified': 1643977433, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57630', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Get rid of ve.splitClusters', 'description': {'raw': 'It has a comment that says TODO: strip out calls to splitClusters then delete this method.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412779609, 'spacePHID': None, 'dateCreated': 1385506740, 'dateModified': 1417571694, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57628', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cite: Error message for an empty reference should be more appropriate and helpful', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the \"Edit\" button\\n2.Insert a reference with no content.\\n3.Save the page\\n\\nObserved Result:\\n\\nThe error message that appears on the page is \"Cite error: The opening <ref> tag is malformed or has a bad name\" where as \\nwhen you edit a reference (not first time insert) to an empty content the error message that appears is \"Cite error: There are <ref> tags on this page without content in them\"\\n\\nThe later one is more understandable for a user.So maybe we can change the message to the later one.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'dateClosed': 1506637608, 'spacePHID': None, 'dateCreated': 1385497740, 'dateModified': 1621892223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57619', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Consider using document.implementation.createHTMLDocument() in ve.createDocumentFromHTML', 'description': {'raw': 'To figure out:\\n* Does this work in all browsers we support? I have anecdotally confirmed support in Firefox 25 and Chrome 30\\n* Protocol-relative URLs in <base> are broken, because documents created this way don\\'t have a creator context or whatever.\\n\\nBenefits:\\n* Not a hack involving iframes :)\\n* Faster than the iframe hack\\n* Does not have issues with HTTPSEverywhere in Firefox\\n\\nFor the <base> issue, it looks like something like this will work:\\n\\n>>> d.querySelector(\\'base\\')\\n<base href=\\u200b\"/\\u200b/\\u200bexample.com\">\\u200b\\n>>> d.baseURI\\nnull\\n>>> d.querySelector(\\'base\\').getAttribute(\\'href\\')\\n\"//example.com\"\\n>>> d.querySelector(\\'base\\').setAttribute(\\'href\\', \\'http://example.com\\');\\nundefined\\n>>> d.baseURI\\n\"http://example.com/\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395876892, 'spacePHID': None, 'dateCreated': 1385472240, 'dateModified': 1443276337, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57586', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create \"Draft\" namespace on the English Wikipedia', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28proposals%29&oldid=582561035#Proposed_new_Draft_namespace\\n\\nI believe this discussion demonstrates sufficient community consensus to create a \"Draft\" namespace on the English Wikipedia.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28proposals%29&oldid=582561035#Proposed_new_Draft_namespace\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57315'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387326342, 'spacePHID': None, 'dateCreated': 1385425560, 'dateModified': 1642315150, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57569', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'browsertests: triggers for MobileFrontend', 'description': {'raw': 'The browser tests for MobileFrontend should be triggered by Gerrit just like it is going to be the case for ULS (T54120) or VisualEditor (T55691).\\n\\nThe tests need to be carefully filtered out since they are expecting content or behavior which are not to be found on a freshly installed wiki.\\n\\n\\nCC:\\n- Zeljkof  our Selenium Guru\\n- Arthur our Mobile scrum master\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53691\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52120'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1427208623, 'spacePHID': None, 'dateCreated': 1385415180, 'dateModified': 1440045549, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57560', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make fakeIme QUnit testing more rigorous', 'description': {'raw': \"The fakeIme tests pass IME-like event sequences into the CE Surface and check that it behaves reasonably. Currently the tests are too weak, in that they don't detect certain problematic behaviour:\\n\\n1. Calls to the simulated preventDefault do nothing at all.\\n\\n2. Some tests are disabled because they fail.\\n\\n3. Only plain text in a single blank paragraph is tested.\\n\\n4. In real usage, changing the CE surface content/selection during input will close the candidate window and commits the candidate text. The tests currently do not check for this. The test data does not show which pieces of text are candidates, since there is no way to detect this from Javascript, but we can infer that at least any text which is subsequenctly changed was a candidate.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-lliyevigiycjbybglftk', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1385387460, 'dateModified': 1643977434, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57538', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Please add a shortcut for adding a reference to a page (?which?)', 'description': {'raw': 'Intention:\\nAdd a reference\\n\\nSteps to Reproduce:\\n1. Took hands off the keyboard.\\n2. Grabbed mouse.\\n3. Clicked \"More\" menu.\\n4. Scrolled down.\\n5. Clicked on \"Reference\".\\n\\nActual Results:  \\nWorks as designed.\\n\\nExpected Results:  \\nThat it would work better than as designed:  Leave hands on keyboard, press a couple of keys, and have the reference dialog pop open.\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437764874, 'spacePHID': None, 'dateCreated': 1385161380, 'dateModified': 1437765204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow the VE dialog for math elements to be movable and resizable', 'description': {'raw': 'Copied from bug 43058 \\n\\nScreenshot of editing a math block\\n\\nSome small tweaks are needed to the dialog box. Editing the last equation at\\nhttps://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit\\nthere are a a few problems\\n\\n1) The dialog obscures the actual equation\\n2) The dlalog is too small to see the whole source text of the equation\\n\\nThis could be solved the making the dialog, moveable and resizeable.\\n\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=12223\\n\\n//attachment missing in source//'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1385145960, 'dateModified': 1643977434, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57437', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Right floated elements other than images and info boxes are not placed correctly', 'description': {'raw': 'There are many templates in Wikipedia that create right floated content other than info boxes and images.\\n\\nExamples are for instance Template:Stack, but there are many similar templates. These are currently not rendering as right floated.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427403947, 'spacePHID': None, 'dateCreated': 1384944720, 'dateModified': 1438734990, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57296', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Table with attribute border=0 is displayed as if border=1', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Mozarteum_University_of_Salzburg&oldid=582046262\\n\\nhttps://parsoid.wmflabs.org/enwiki/Mozarteum_University_of_Salzburg?oldid=582046262\\n\\nYet when opened in VE, the dom shows border=\"1\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412114211, 'spacePHID': None, 'dateCreated': 1384944240, 'dateModified': 1417571832, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57295', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images: {{Gallery}} template parsed differently by PHP parser and Parsoid', 'description': {'raw': '{{Gallery}} is implemented by a Lua template here: https://en.wikipedia.org/wiki/Module:Gallery\\n\\nSee example below\\n\\n```\\n[subbu@earth lib] cat /tmp/gallery\\n{{Gallery\\n| lines = 2\\n| File:Arc de Triomphe de l\\'Etoile - Projet Chalgrin - 02.jpg|1806: Architectural drawing project of [[Jean Chalgrin]]\\n}}\\n[subbu@earth lib] node parse --dump tplsrc < /tmp/gallery\\n=================================\\nTemplate:Gallery\\n---------------------------------\\n<table style=\"background:transparent;border:1px solid #f0f0f0;margin-top:0.5em;\"><tr><td><table style=\"width:200px;float:left;border-collapse:collapse;margin:3px;\"><tr><td style=\"height:200px;border:1px solid #CCCCCC;background-color:#F8F8F8;padding:0px;text-align:center;\">[[File:Arc de Triomphe de l\\'Etoile - Projet Chalgrin - 02.jpg|center|border|180x180px|alt=|1806: Architectural drawing project of [[Jean Chalgrin]]]]</td></tr><tr style=\"vertical-align:top;\"><td style=\"display:block;font-size:1em;height:3.2em;padding:0px;\"><div class=\"gallerytext\" style=\"height:3.1em;width:187px;line-height:1.3em;padding:2px 6px 1px 6px;overflow-y:auto;margin:0px;border:none;border-width:0px;\">1806: Architectural drawing project of [[Jean Chalgrin]]&nbsp;</div></td></tr></table></td></tr></table>\\n---------------------------------\\n```\\n\\nSo, the {{Gallery}} template emits the image in a <td> and the caption in a separate <tr> below. As far as I can tell, Parsoid therefore (correctly) duplicates the caption in both the <tr>s. However, somehow, the PHP parser magically suppresses the first caption (see https://en.wikipedia.org/w/index.php?title=User:Ssastry/sandbox&oldid=582405791)\\n\\nThis is based on a report on VE/F @ https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=582367222#Pages_that_go_wrong_in_VE'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1491864814, 'spacePHID': None, 'dateCreated': 1384885800, 'dateModified': 1491864814, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57263', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add a link to the new guided format in the Navigation menu', 'description': {'raw': 'Pretty much what the Summary says:\\nI would have used the new format but I keep forgetting how to reach it!\\nI had proposed that the link reads \"Enter a new bug (guided)\" but in the end everything is actually ok for me as long as it\\'s easy to discover for everyone, obviously.\\nCheers.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389089823, 'spacePHID': None, 'dateCreated': 1384878480, 'dateModified': 1389089823, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57254', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't use deprecated mw.util.wikiGetlink function\", 'description': {'raw': 'When in debug mode the browser console always shows a message\\n\\nMWDeprecationWarning: Use of \"wikiGetlink\" property is deprecated. Use mw.util.getUrl instead.\\n\\ncaused somewhere in VE\\'s startup module. When you are trying to find uses of deprecated functions in your own scripts this message is a bit annoying, as you can\\'t do anything about it and it shows up on every page. So please replace all calls to .wikiGetlink with .getUrl (in startup module and possibly elsewhere).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-tyjmn7xcw6s2b6rqagj7', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384857395, 'spacePHID': None, 'dateCreated': 1384856940, 'dateModified': 1417572753, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57237', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Opening and closing the link inspector dirties the link, adding a pointless transaction', 'description': {'raw': 'Steps to reproduce:\\n\\n\\n1.Click on the edit button\\n2.Click on a link and click on the link insertion icon.\\n3.Without making any change just close the link inspector\\n\\nObserved Result:\\nThe \"Save Page\" button becomes active though if you review the changes it will say that this revision matches the lastest version of the page.\\n\\nExpected Result:\\nIf there is not modification in the content it is probably better to keep the \"Save Changes\" button inactive.\\n\\nSample Page:\\n\\nhttps://en.wikipedia.org/w/index.php?title=Tea_tree_oil&veaction=edit\\n\\nBrowser: Chrome Version 26.0.1410.65\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402549147, 'spacePHID': None, 'dateCreated': 1384800900, 'dateModified': 1441912068, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57205', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __HIDDENCAT__ status in the page metadata panel', 'description': {'raw': 'Checkbox flag, category namespace only.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398124350, 'spacePHID': None, 'dateCreated': 1384754520, 'dateModified': 1443276343, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57170', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Flow: syntax highlighting tags (GeSHi) don't get styled\", 'description': {'raw': 'Syntax highlighting doesn\\'t work with Flow.\\n\\nExample input:\\n\\n```\\n<syntaxhighlight lang=\"css\">\\n.foo {\\n    font-weight: bold;\\n}\\n</syntaxhighlight>\\n```\\nOutput is not appropriately highlighted: https://www.mediawiki.org/wiki/Topic:Sb29d13fybslwgjh\\nIt should look like this: https://www.mediawiki.org/w/index.php?title=User:Quiddity_%28WMF%29/sandbox&oldid=1397603\\n\\n----\\nTheDJ notes (in comment below) that this might be related (plus its blockers): {T69540}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1384750140, 'dateModified': 1657241922, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57159', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Browser tests assume the User namespace is VE-editable', 'description': {'raw': 'The browser tests are acting on User:Selenium_user. On a default VisualEditor installation, the User namespace does not have VisualEditor enabled.\\n\\nThe easiest would be to enable VisualEditor on user page I guess.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394660282, 'spacePHID': None, 'dateCreated': 1384522740, 'dateModified': 1443276347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57104', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Browser tests assume User:Selenium_user exists', 'description': {'raw': 'The browser tests are assuming the user Selenium_user exist. It should instead rely on the user passed within the environment variable MEDIAWIKI_USER and its associated password in MEDIAWIKI_PASSWORD.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386263541, 'spacePHID': None, 'dateCreated': 1384522140, 'dateModified': 1386264476, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57103', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting text with command+down actually selects the whole current paragraph and also the 0th character of the next one; show this more obviously', 'description': {'raw': 'Paragraph turned into heading format\\n\\nSteps to reproduce:\\n\\n1.Click the edit button on a page\\n2.Write down a paragraph and the text for its heading \\n3.Select the text to be heading of the paragraph\\n\\nObserved Result:\\n\\nThe whole paragraph including the text turns into heading format.\\n\\nSee the screenshot attached\\n\\nFound in:\\n\\nhttp://en.wikipedia.beta.wmflabs.org/\\n(Example Page:http://en.wikipedia.beta.wmflabs.org/wiki/Test_52608?veaction=edit)\\n\\nBrowser:FireFox 25 \\nOS:MAC OS X 10.8.5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11950}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701814075, 'spacePHID': None, 'dateCreated': 1384472820, 'dateModified': 1701814075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57085', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting text with command+down and then pressing command+right takes the cursor to the end of the next line', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit button of a page which has multiple lines\\n2.Select the text in the first line by pressing command+down\\n3.Press on command+right \\n\\nObserved Result:\\n\\nInstead of moving to the end of the line for the selected text, the cursor goes to the end of the second line.\\n\\nHowever, when you select the text with command+right/left it goes to end of the selected line.\\n\\nFound in:\\n\\nhttp://en.wikipedia.beta.wmflabs.org/\\nBrowser:FireFox 25, Chrome Version 26.0.1410.65\\nOS:MAC OS X 10.8.5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1384469880, 'dateModified': 1443019817, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57082', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add CSS classes based on writing system code', 'description': {'raw': 'It would be useful to have the languages that MediaWiki supports be aware of the alphabet in which they are written.\\n\\nISO 15924 writing systems code can be used for the most part, so it will be \"latn\" for English, French, Vietnamese, etc.; \"cyrl\" for Russian, Udmurt, etc.; \"deva\" for Hindi, Marathi, etc. - and so on.\\n\\nThis is useful for applying special styles that are common to all languages written in a script. For example the notorious line-height fix is applied in shared.css by element name and language code, and it could be greatly simplified by using the relevant script codes so instead of having selectors for bh, bho, hi, ks, mr, mai, ne, new, pi and sa, there would only be one selector for class deva.\\n\\nOf course, it will have to take into account language variants (Serbian Cyrillic / Latin, Kazakh Cyrillic / Latin / Arabic etc.) and also special cases not covered by ISO 15924, such as the internal differences between styles of Arabic (so Arabic may use \"arab\" and Urdu may use something like \"arab-nastaleeq\").\\n\\nAn easy way to implement this would be to add a variable to each Messages file, similarly to $rtl. (In fact, this can make $rtl obsolete, because the direction is inherent in the writing system.)\\n\\nComment 1: In this bug, \"writing system\", \"script\" and \"alphabet\" are synonyms. I mentioned all to make it easier to find.\\n\\nComment 2: I vaguely recall that there is a bug for this, but I cannot find it. If there is one, please mark this one as a dupe.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1384410720, 'dateModified': 1722301447, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57045', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pawn (\"♙\") appears when clicking into the blank space above a new link inspector and inserting content', 'description': {'raw': 'Steps:\\n* Edit page\\n* Add heading \"External links\"\\n* Press Enter, click \"Bulleted list\" in toolbar\\n* Click on the link tool and paste a url in the link input widget\\n* Type a label where the cursor is\\n\\nExpected:\\n\\n <h2>External links\\n <ul><li> <a>Typing</a>\\n\\nActual:\\n\\n <h2>External links\\n <ul><li> <a>http://example.org/foobarTyping</a>♙\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386106849, 'spacePHID': None, 'dateCreated': 1384301160, 'dateModified': 1417572673, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56976', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The language selector takes user to the top of a page making user to scroll down again to the line where he was editing.', 'description': {'raw': 'Taking user to the top of the page\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button for a page with long article(For Example:https://test2.wikipedia.org/wiki/First_line?veaction=edit)\\n2.Go to the end of the article\\n3.Click the button More>Language\\n\\nObserved Result:\\nThe language selector takes user at the top of the page which is a bit inconvenient for user editing long article as he has to scroll down again to the point where he was editing.\\n\\nSee the video attached\\n\\nBrowser: Chrome Version 26.0.1410.65\\nOS:MAC OS X 10.8.5\\nEnvironment:test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12431}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399641526, 'spacePHID': None, 'dateCreated': 1384218720, 'dateModified': 1417572390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56922', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit {{DISPLAYTITLE:xxx}} in the page metadata panel', 'description': {'raw': 'A limited rich text box, defaulting to page title.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53566\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49076'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402547577, 'spacePHID': None, 'dateCreated': 1384101420, 'dateModified': 1443278219, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56868', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __NOTOC__ status in the page metadata panel', 'description': {'raw': 'A checkbox, setting:\\n\\n  <meta property=\"mw:PageProp/notoc\">\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388918582, 'spacePHID': None, 'dateCreated': 1384101120, 'dateModified': 1443276347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56866', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit behaviour flags in the page metadata panel (tracker)', 'description': {'raw': 'Tracking bug for support for setting #REDIRECT, __NOTOC__, etc. behavioural flags.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402547626, 'spacePHID': None, 'dateCreated': 1384100940, 'dateModified': 1443278222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56865', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Instead of adding indentation to the new line, pressing \"Tab\" from the keyboard adds indentation to other numbered/bulleted list', 'description': {'raw': 'tab not adding indentation to newline\\n\\nSteps to reproduce:\\n\\n1.Add a numbered/bulleted list in the editor \\n2.Go to a newline afte the list\\n3.Now click on \"tab\" from keyboard\\n\\nObserved Result:\\nInstead of adding indentation to the new line, it keeps on adding indentation to first line of the numbered list.\\n\\nSometimes it also selects other items outside the editor.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12204}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1383948660, 'dateModified': 1416846497, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56810', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Math inspector(LaTeX) does not open up after adding a reference to the article', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the Edit button\\n2.Add a reference to a text from More>Reference\\n3.Now try to open up LaTeX window for any text in the article\\n\\nObserved Result:\\n\\nThe math inspector does not open up after adding a reference to the article\\n\\n\\nEnvironment:Test 2\\nPage:Any\\nBrowser:FireFox 20 and Chrome Version 26.0.1410.65\\nReproducible: Yes\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386024583, 'spacePHID': None, 'dateCreated': 1383940080, 'dateModified': 1417572743, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56799', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The default direction of the <textarea> for editing the content of <source> must be LTR', 'description': {'raw': \"Currently, if I go to https://www.mediawiki.org/wiki/User:Amire80/ve-source and\\nedit it using VE, I can edit the content of the <source> tag. If my UI language\\nis Hebrew, then the <textarea> for editing the poem is RTL. I would expect it\\nto be always LTR by default, because source code is almost always LTR. (There are some RTL programming languages like Hebrew Logo and Arabic Alb, but these are very rare exceptions and the <source> tag doesn't support them anyway.)\\n\\nThis is comparable to Bug 56779, but unlike in that bug, here the request is that the direction will be explicitly set to ltr rather than the surrounding direction.\\n\\nThere may be other tags for which something like this would be useful, but I can't think of any at the moment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383965012, 'spacePHID': None, 'dateCreated': 1383920820, 'dateModified': 1417572755, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56780', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When using citation templates, the page title and access date fields should be filled automatically', 'description': {'raw': 'When cite web is used, webpage title, and access date should be filled automatically for 1 click web citations.\\n\\n\\n**Status:**  Title and other information is done via #citoid, but auto-adding the current date to the access-date parameter is a problem because of {T4700}.'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1383914040, 'dateModified': 1677499236, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56772', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Present the wikitext warning to users writing <ref> tags', 'description': {'raw': \"Intention:\\nTo add a ref (incorrectly, by typing out the wikicode)\\n\\nSteps to Reproduce:\\n1.  Open a page. \\n2.  Type <ref>Whatever</ref>\\n3.  Discover that there is no warning about wikitext markup being detected.\\n\\nActual Results:  \\nNothing.\\n\\nExpected Results:  \\nIt should display the same wikitext markup warning that typing ''' produces.\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385139365, 'spacePHID': None, 'dateCreated': 1383875160, 'dateModified': 1417572749, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: wiki markup for link shows up if a template is selected with another text and applied link onto them together', 'description': {'raw': 'wiki markup\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button for any page \\n2.Type a text in the editor.\\n3.Add a template for example:citation needed,\\n4.Now select both the text and the template and press command+l or link icon\\n5.Apply a link to them through link inspector\\n\\nObserved Result:\\nThe wiki markup for link shows up in the view mode\\n\\nSee the screenshot attached.\\n\\n\\nFound this bug using firefox 20 or chrome Version 26.0.1410.65 in MAC OS\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12078}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402553588, 'spacePHID': None, 'dateCreated': 1383868860, 'dateModified': 1441912074, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56749', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The link inspector and the language selector opens up outside the editor while selecting a text outside the editor', 'description': {'raw': \"Link inspector\\n\\nSteps to reproduce:\\n\\n1. Click on the Edit button on any page \\n2. Go to a new line by pressing enter\\n3. Now click at the top of the page or select the current user's name.\\n4. Click on the link icon or More>Language from the toolbar\\n\\nObserved Result:\\nThe link inspector and the language selector opens up at the top right corner of the page ,outside the editor\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12072}\"}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398726576, 'spacePHID': None, 'dateCreated': 1383866520, 'dateModified': 1441912081, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56747', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Launch the 'gettingstartedtasktoolbar' tour by default\", 'description': {'raw': '**Author:** `swalling`\\n\\n**Description:**\\nRight now, the workflow for GettingStarted tours is as follows:\\n\\n- The user gets \\'gettingstartedtasktoolbarintro\\' once and immediately on their first view of a suggested task page. This is a one step intro tour, and then is never seen again. \\n- The user is then shown the task page, with the GettingStarted toolbar. They can click \"Show me how\" in the toolbar, which launches the \\'gettingstartedtasktoolbar\\' tour. \\n\\nWithout changing the toolbar behavior, let\\'s automatically launch the \\'gettingstartedtasktoolbar\\' tour after the user completes the intro tour. Right now, only 9% of users are using the tour provided by \"Show me how\", which is fewer than we intended.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391575905, 'spacePHID': None, 'dateCreated': 1383779160, 'dateModified': 1391575905, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56697', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Use mw.Api library in mw.Target instead of our own functions', 'description': {'raw': 'mw.Api has nice features now like automatically retrying bad tokens, we should migrate to it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1424886124, 'spacePHID': None, 'dateCreated': 1383724260, 'dateModified': 1438734142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56659', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Restore selection after blur+focus', 'description': {'raw': \"When the surface is blurred, then focused, we should restore the selection. Right now we don't, and that causes section editing to break when ULS is present.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383856582, 'spacePHID': None, 'dateCreated': 1383702120, 'dateModified': 1417572756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56651', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Exception when undoing foreign image insertion', 'description': {'raw': \"1. Insert an image from Commons\\n2. Press Ctrl+Z quickly\\n\\nWhen you undo the image insertion, there's still an API request pending. When it comes back, ve.ce.GeneratedContentNode.prototype.doneGenerating crashes because the node is now detached.\\n\\nGCNode should protect against being detached, and should abort any pending requests when it's detached (the latter alone is not enough: GCNode promises aren't guaranteed to be abortable).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384945498, 'spacePHID': None, 'dateCreated': 1383699720, 'dateModified': 1417572750, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56649', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Insert media dialog lets you select an image via mouseup even if mousedown occurred elsewhere', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Click on the \"Edit\" button\\n2.Click on More>Media\\n3.Now attempt to drag the dialog downward\\n\\nObserved Result:\\nThe dialog box for media inclusion closes upon dragging down\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404866655, 'spacePHID': None, 'dateCreated': 1383699180, 'dateModified': 1443278222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56648', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make byte counter in save dialog use widget accessors rather than $textarea', 'description': {'raw': 'var $textarea = this.editSummaryInput.$input is bad, should just use .getValue() or whatever it is.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412800505, 'spacePHID': None, 'dateCreated': 1383698880, 'dateModified': 1417571694, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56647', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'visualeditor-q3VisualEditor: Open formula inspector breaks when clicking onto a link/reference/image/template/…', 'description': {'raw': 'Empty inspector\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button\\n2.Click on More>LaTeX\\n3.Type something on the dialog box\\n4.While keeping this dialog box open , Click on More>Reference\\n5.Add something as reference \\n6.Click the button \"Insert Reference\"\\n\\nObserved Result:\\nA blank inspector comes up which also does not get closed unless user reopens the editor\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58045\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60850\\n\\n**Attached**: {F12800}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1427822306, 'spacePHID': None, 'dateCreated': 1383696720, 'dateModified': 1438734157, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56644', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The search textbox is going beyond the dialog box for selecting language after clicking on \"Change Language\"', 'description': {'raw': 'The search text box\\n\\nSteps to reproduce:\\n\\n1. Click on the \"Edit-beta\" button on beta-labs\\n2.Click on the Language option from the toolbar\\n3. Click the button \"Change language\"\\n\\nObserved Result:\\nThe search textbox is going beyond the dialog box for selecting language.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F12789}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399641326, 'spacePHID': None, 'dateCreated': 1383691440, 'dateModified': 1417596569, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56636', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Send Accept-encoding: gzip to Parsoid service', 'description': {'raw': \"We want to cache gzipped responses in Varnish. For this to work all clients need to send an Accept-Encoding header that includes 'gzip'.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401227796, 'spacePHID': None, 'dateCreated': 1383635820, 'dateModified': 1417572301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56605', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Templates with a conditional <li> asterisk in the beginning render in VE with it always visible', 'description': {'raw': \"Some frequently-used templates in the Hebrew Wikipedia, for example {{ynet}} have an asterisk in the beginning, which is inserted conditionally according to a parameter.\\n\\nThey don't appear in the rendered article, but they appear as bullets when editing the article in VE.\\n\\nFor an example see the URL.\\n\\nI demonstrated the issue to Moriel.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://he.wikipedia.org/wiki/%D7%A9%D7%9C%D7%93_%D7%91%D7%95%D7%A8%D7%A1%D7%90%D7%99\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1383564420, 'dateModified': 1416846499, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56558', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: line breaks are added before and after image description when it is changed', 'description': {'raw': \"I'm not sure that it happens always, but in this edit I changed the description of an image, and line breaks were added:\\n\\nhttps://he.wikipedia.org/w/index.php?title=%D7%90%D7%95%D7%A4%D7%A7_%28%D7%A4%D7%93%D7%95%D7%9C%D7%95%D7%92%D7%99%D7%94%29&diff=14768833&oldid=13742934\\n\\nIt's the first change in the diff.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1420843419, 'spacePHID': None, 'dateCreated': 1383561060, 'dateModified': 1438734461, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56553', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Rename the BetaFeatures extension', 'description': {'raw': 'I realize it\\'s probably already water under the bridge, but I believe\\nthis should be said anyway. Just WONTFIX the bug if we can\\'t do\\nanything about it.\\n\\nThe name \"BetaFeatures\" is bad. Like, really bad. And I don\\'t think\\nthis is just my personal opinion (but I don\\'t like it personally\\neither).\\n\\n* We have so many things named \"beta\" right now live on the wikis that\\n  it\\'s not even funny. VisualEditor is beta. MobileFrontend has some\\n  beta stuff. Now we\\'re also going to have \"beta\" features.\\n  Depending on the person, the \"beta\" label has either lost its\\n  meaning or is negatively associated with past deployment failures.\\n\\n* It\\'s non-descriptive. It may be the non-native English speaker in\\n  me, but it sounds like marketing-speech. \"beta\" doesn\\'t mean much\\n  these days (see point 1); \"feature\" is a catch-all buzzword.\\n\\n* It\\'s stupidly hard to translate:\\n  * Most languages don\\'t even have a word for \"beta\" – unless somebody\\n    talented does the translation, these will keep using the English\\n    word in likely very awkward ways – most of currently translated\\n    messages just keep the \"beta\" label tacked onto a normal word:\\n    [[translatewiki:Special:Translations/Mediawiki:Prefs-betafeatures]],\\n    some went with \"experimental\" instead.\\n  * Similarly, most languages don\\'t have a word for \"feature\" – in the\\n    link above, most translations say the equivalent of\\n    \"functionality\" or \"function\", and neither is a friendly word.\\n    Basically, any translation of this will consist solely of\\n    English/Latin loanwords in almost all languages, which may make it\\n    sound \"remote\" or \"unfriendly\".\\n\\n\\nSo what do we do about it?\\n\\n* We can try renaming the project. We could go with the lowest\\n  friction option and call it \"Experimental features\", which would be\\n  at least a little better.\\n\\n* Or we could use others\\' experiences and name that section\\n  \"Laboratory\", which would also give us an obvious, clear icon to use\\n  (laboratory beaker) – Google does this with their experimental\\n  options and it has always seemed like a great idea to me.\\n\\n\\nNo idea if \"rebranding\" as this point is still viable – it might be\\npossible, as I don\\'t think it was widely announced yet. But I\\'m just\\nsaying.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384293799, 'spacePHID': None, 'dateCreated': 1383491580, 'dateModified': 1419938174, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56537', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Saving a page should update both wgRevisionId and wgCurRevisionId', 'description': {'raw': 'When we open a random page, we get\\nwgCurRevisionId === wgRevisionId\\nand if we make an edit using the source editor, both variables are increased to a new Id.\\n\\nOn the other hand, if the edit is made using the VisualEditor, only the wgCurRevisionId is updated.\\n\\nThis inconsistent behavior should be fixed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398110278, 'spacePHID': None, 'dateCreated': 1383474420, 'dateModified': 1443276351, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56532', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Shows \"<\"  icon on the last clicked link, if user clicks on the link icon from the toolbar on a blank space', 'description': {'raw': 'The \"<\" icon on last clicked link\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit button\\n2.click on a text which has link on it but do not open the link inspector\\n3.Now click on a blank space\\n4.Click on the link icon from the toolbar.\\n\\nObserved Result:\\n\\nThe \"<\" icon shows up at the end of the text in step 2.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12481}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402329509, 'spacePHID': None, 'dateCreated': 1383350520, 'dateModified': 1441912089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56503', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make the external link option available when a user types a valid URL pattern', 'description': {'raw': 'Steps to reproduce:\\n\\n-Click on the Edit button\\n-Click on the icon to insert a link from the toolbar or press ctrl+k or command+k -Now type a valid URL without http:// for example:yahoo.com\\n\\nObserved Result:\\nThere is no option for selecting this link as external link other than creating a new page.\\n\\nIt would be better if the external link option is made available to user when they type a valid URL (text with \".\" inside it), and then transforms it into a HTTP link if no prefix is provided.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402609062, 'spacePHID': None, 'dateCreated': 1383339600, 'dateModified': 1417572222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56490', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Demote the \"New Page\" part of the link inspector to below the \"External link\" one when inserting a link as URL pattern', 'description': {'raw': 'Difference in the view mode\\n\\nSteps to reproduce:\\n\\n1.Click on the Edit-beta button\\n2.Type a text to apply link on it, For example: CNN\\n3.Now click on the link icon from the tool bar or press ctrl+k/ Command+K\\n4.Now type the link as http://cnn.com as an external link.\\n5.Now type again another text CNN\\n6.Now apply link insertion onto it as : http://cnn.com as new page\\n7.Press the button \"Save\"\\n\\nObserved Result:\\nNow observe that the link created in step 4 looks reasonable to have an external\\nlink when the URL is specific in the link inspector.\\nBut user wont usually want a new page while specifying the URL itself and might accidentally to do that without any intention to do that.\\n\\nAlso, observe the output format of step 6 looks wrong as the wiki markup for link shows up in the CE in view mode with a number.Though functionally, it works same as a link to external page.   \\n\\nExpected Result:\\nAs a suggestion,collapse the \"New Page\" part of the link inspector when a URL pattern detected.\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F12432}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402680839, 'spacePHID': None, 'dateCreated': 1383333240, 'dateModified': 1441912106, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56482', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Echo: The \"You have new messages\" link should go to a diff and/or subsection of the user\\'s talk page where the talk page resides', 'description': {'raw': '==== Problem\\nThe orange \"You have new messages\" talkpage-message Notification, currently leads just to the top of the user\\'s Talk page. (Ie. [User talk:Quiddity])\\nThis is potentially confusing and makes it harder for users to locate the new message.\\n{F26220991}\\n\\n==== Proposed solution\\n* Tapping on \"new messages\" should take the user to the specific subsection (if known, and if there\\'s just one new message); and\\n* Append the message with a \"(view changes)\" link which takes the user to the diff (if subsection is unknown, or if there are multiple new talkpage messages).\\n\\n(Note: This essentially follows the same message format as shown to users of the gadget to \"Display a floating alert for new talk page messages\" (link to [[ https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets | gadget on enwiki ]])\\n\\n\\n// One user has requested that it *always* lead to the diff, which /would/ be more consistent, but I also understand the desire to not confront everyone with a diff (VE, newcomer friendliness, etc etc). ( https://en.wikipedia.org/wiki/Wikipedia_talk:Notifications#Two_clicks_instead_of_one:_Why.3F ) //\\n\\n'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1630715990, 'spacePHID': None, 'dateCreated': 1383326040, 'dateModified': 1630715991, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56475', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Track in some way (add tag to revision?) edits where user switched into wikitext editor', 'description': {'raw': 'Since bug 50687 was fixed, I was wondering if wouldn\\'t be a good idea to identify which edits made using the wikicode editor were actually started using Visual Editor. This could be useful to identify potential areas of improvement of Visual Editor, providing a list of actions which users are unable to complete using it.\\n\\nA way to do this would be the use of a new tag (similar to the \"visualeditor\" and \"visualeditor-needcheck\" tags).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50687'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393465167, 'spacePHID': None, 'dateCreated': 1383304560, 'dateModified': 1443276352, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56465', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add a second keyboard shortcut for Clear Formatting for keyboards without a \"\\\\\"', 'description': {'raw': 'Split from bug 51507 which introduced Ctrl/Cmd + \\\\ as a trigger for this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51507'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394056097, 'spacePHID': None, 'dateCreated': 1383283920, 'dateModified': 1443276353, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56453', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: It should be possible to add a link with only pressing enter once', 'description': {'raw': 'Steps to reproduce:\\n1.Click on the \"Edit-Beta\" button\\n2.Type a text on which to insert link\\n3.Press \"Enter\" to select the suggested links or if there is no match just press \"Enter\"\\n4.Then again press \"Enter\"\\n\\nObserved Result:\\nTo insert a link the step 4 is a redundant step , Pressing enter once should just add the link.\\n\\nPressing the \"Enter\" twice seems justified in the case, where the content of the link box is different from what user initially typed into.\\n\\n[Suggested by Erik Moeller]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402552625, 'spacePHID': None, 'dateCreated': 1383255660, 'dateModified': 1441912116, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56434', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:The cursor position for newly inserted link should be at the end of the link that is being created', 'description': {'raw': 'Screenshot showing cursor at the beginning of the text \"Yahoo\"\\n\\nSteps to reproduce:\\n-Click on the Edit-beta button\\n-Type a text on which you will insert a link.\\n-click on the link icon from the toolbar or use shortcut keys ctrl+k/command+k(MAC)\\n-Type the link on the dialog box that appears .\\n-Press \"Enter\" to apply that.\\n\\nObserved Result:\\nThe cursor position postion moves to the beginning of the text on which the link inserted making user to reposition it to the end of it to continue editing.\\n\\nExpected Result:\\nThe cursor position for newly inserted link should be at the end of the link to ease user experience.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12328}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402552556, 'spacePHID': None, 'dateCreated': 1383251880, 'dateModified': 1441912123, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Change DOM rendering of <nowiki /> to be <span typeof=\"mw:Nowiki\"></span> or similar?', 'description': {'raw': 'VisualEditor deliberately drops <span typeof=\"mw:Nowiki\"> annotations on changed content to prevent originally-necessary <nowiki> blocks interfering with editing. This means that HTML editors don\\'t need to know or care about <nowiki>s, and they are just magically sorted out in the back-end so the resultant wikitext is the most like what a human would create.\\n\\nHowever, <nowiki />s come out as a <meta typeof=\"mw:Placeholder\">, which VisualEditor doesn\\'t show to users but also won\\'t ever remove, leading to potential issues where a no-longer-needed <nowiki /> sits in the wikitext, disruptively confusing to wikitext editors.\\n\\nIf Parsoid instead represented it as <span typeof=\"mw:Nowiki\"></span> or similar, VisualEditor could do the same (well, a bit more work) and so drop it when the context has been edited, letting Parsoid re-generate it if needed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/w/index.php?title=Footprints_%28film%29&curid=39472392&diff=579475542&oldid=579357688'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1486493729, 'spacePHID': None, 'dateCreated': 1383161460, 'dateModified': 1629724523, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56381', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Language names blurred and difficult to read using the hardcoded \"Autonym\" font on Windows computers', 'description': {'raw': 'Blurred Autonym font\\n\\nInterwiki names blurred and legible with difficulty (using the hardcoded \"Autonym\" font)\\n\\nFirefox 25 / WinXPSP3 / standard antialiasing (= no ClearType)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Windows 7\\n**Platform**: PC\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=40874\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56552\\nhttps://github.com/santhoshtr/AutonymFont/issues/38\\nhttps://github.com/santhoshtr/AutonymFont/issues/50\\n\\n**Attached**: {F12122}'}, 'authorPHID': 'PHID-USER-xqqqgn2dels45flxw5kb', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390369610, 'spacePHID': None, 'dateCreated': 1383081900, 'dateModified': 1444685692, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56346', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid ignores unclosed <ref>, whereas Cite extension truncates the page', 'description': {'raw': 'An unclosed <ref> tag on the page eats up the rest of the page, typically including the requisite <reference> tag at the bottom of the page. However, VisualEditor handles the unclosed <ref> tag more gracefully, treating it as plain text.\\n\\nAt the URL above, the wikitext:\\n\\n    Before <ref> during\\n    after\\n    <references />\\n\\nis rendered:\\n\\n    Before[1]\\n    Cite error: <ref> tag found without <references/>\\n\\nwhereas VisualEditor shows:\\n\\n    Before <ref> during↵after\\n    There are no references on this page to include on this list.\\n\\nThis issue was brought to my attention by an editor who somehow created the unclosed <ref> tag in VisualEditor. (See the initial revision of [[vi:Danh sách các chi tiết gợi nhớ đến Disney trong phim Enchanted]].) I’ve reached out to the editor for information on how they might’ve gotten into that state.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/User:Mxn/56306'}, 'authorPHID': 'PHID-USER-sxpswmchfwxkuo2wszeo', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1453350985, 'spacePHID': None, 'dateCreated': 1383041940, 'dateModified': 1453350985, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56306', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make ULS more lightweight', 'description': {'raw': \"For many users, ULS serves no practical purpose. It is also quite large, which can be problematic if you're not on a first-world internet connection (or are in rural US), is occasionally host to somewhat problematic bugs, and generally is not worth the trouble if you're not part of the target audience.\\n\\nSo there should be a way for such people to just turn the thing off, not load it at all, and be happy.\\n\\nI appreciate that adding an option for this has been been wontfixed, though I don't know why, but even without there being an option in the interface, there SHOULD be support in the extension itself to disable it, regardless of where it actually appears.\\n\\nThere should be a way for users who are truly and consistently inconvenienced by it to actually solve the underlying problem (such as with a hidden preference or cookie), instead of just hiding it. There should also be a way for third-party hosts to add such an option for their users who also fit the target audience, even if they don't necessarily want it on for everyone.\\n\\nAs it is it seems to inconvenience as many people as it helps on wikimedia projects, and isn't very appealing to third-party hosts, either, despite it solving some very real problems facing some of our users as well.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-nv2bu7uh3huvidyjo4lk', 'ownerPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'dateClosed': 1468323177, 'spacePHID': None, 'dateCreated': 1383019140, 'dateModified': 1472675248, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56292', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When editing a file/category page, show the non-page composite components outside the VE surface in their \"normal\" place', 'description': {'raw': 'When editing a category page in VE, the page contents, such as a Subcategories heading and the list of categories in the cat, do not display.  \\n\\nA requested enhancement would be to display these items using the greyed/lined out display VE uses for other non-editable items.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1464277438, 'spacePHID': None, 'dateCreated': 1383010800, 'dateModified': 1660398888, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56289', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Get rid of ve.ce.Surface.prototype.setContentBranchNodeChanged', 'description': {'raw': 'Was introduced as a hack in https://gerrit.wikimedia.org/r/#/c/91786 but we should really find a way to make this unnecessary.\\n'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1382983860, 'dateModified': 1531525880, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56264', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Hatnote cleanup problem', 'description': {'raw': \"User reports:\\nThere does not seem to be a way to delete the first of two hatnotes without leaving extra space at the top of the article. 28bytes (talk) 03:20, 15 October 2013 (UTC)\\n\\nLink: https://en.wikipedia.org/w/index.php?title=Maxi_single&diff=577225537&oldid=568995072\\n\\nUser config: Firefox 24.0/Windows 7/Monobook, but the same's true for Safari and for Macs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1421452537, 'spacePHID': None, 'dateCreated': 1382954280, 'dateModified': 1438734466, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56234', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] \"Watch this\" checkbox checked in Save dialog regardless of the user preference', 'description': {'raw': 'I think this is a code regression:\\n\\nThe \"Watch this\" checkbox is always checked in Save dialog regardless of the user preference.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385457692, 'spacePHID': None, 'dateCreated': 1382820900, 'dateModified': 1417572745, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56206', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Refactor CSS so CE doesn't need to position things relative to the UI surface\", 'description': {'raw': \"I see a lot of code like this:\\n\\nve.Element.getRelativePosition( [something], this.getRoot().getSurface().getSurface().$ );\\n\\nIdeally, CE classes wouldn't need to reach into the UI surface for stuff like this. Positioning against the CE surface should just work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1382473500, 'dateModified': 1643977435, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dialogs should disable \"Apply changes\" until a change is present', 'description': {'raw': 'Seen in Reference and Transclusion, anywhere with an overlay containing a button saying \\'Apply changes\\'. \\n\\n* Hover the cursor over an existing Reference or Transclusion. \\n* Click the icon to invoke the Reference or Transclusion overlay\\n* Without making any changes, click \\'Apply changes\\'\\n\\n* Save page button goes from grey to active.\\n\\n* Click Save page\\n* Click Review your changes. \\n\\nGet message \"Could not start the review because your revision matches the latest version of this page.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423610320, 'spacePHID': None, 'dateCreated': 1382388360, 'dateModified': 1438733814, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55976', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up constructor params to dm.Node subclasses', 'description': {'raw': \"* dm.LeafNode has (length, element), where length is ignored and forced to 0 by all subclasses except for dm.TextNode\\n* dm.BranchNode has (children, element), length is computed while children are added\\n\\nThe code in dm.Document constructing node trees needs to be aware of this, but at the same time it doesn't even use these parameters, because branch nodes are created as childless nodes that have their children added later, and text nodes are created with length zero and have the correct length set later. So we should just get rid of these parameters and make the constructors take a single element parameter, that would get them in line with other dm.Model subclasses (dm.Annotation and dm.MetaItem) as well.\\n\\nWhile we're at it, we should also fix the documentation that claims that the element parameter is optional, it really isn't.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412590447, 'spacePHID': None, 'dateCreated': 1382100600, 'dateModified': 1443278227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55871', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Removing stub template removes too many lines', 'description': {'raw': \"Intention:  To remove a stub template\\n\\n\\nExpectation:  That the stub template would disappear and everything else (references list, navbox) would remain the same\\n\\n\\nSteps to reproduce:\\n\\n1)  Go to https://en.wikipedia.org/w/index.php?title=Gastric_volvulus&oldid=567517399 or (probably) any other article that contains these items on separate, adjacent lines:\\n\\n * A list of references (in this case, a single bulleted list item)\\n * A blank line\\n * A stub template\\n * A navigation template\\n\\n2)  Open the article in VisualEditor.\\n\\n3)  Click on the the stub template to select it.\\n\\n4)  Press the delete/backspace key (it's same key on a Mac) one time to delete the stub template (and nothing else).\\n\\n\\nResult:\\n\\nInstead of getting the slightly shorter expected list:\\n\\n * A list of references (in this case, a single bulleted list item)\\n * A blank line\\n * A navigation template\\n\\nthis produced a single line containing both the reference list item and the navbox, with no intervening spaces or lines:\\n\\n * A list of references (in this case, a single bulleted list item)Navigation template\\n\\nThis broke the navbox formatting for readers.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=Gastric_volvulus&diff=577403274&oldid=576282874\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1382053680, 'dateModified': 1421777878, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55856', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector does not show suggestions dropdown on open if link target is the same as the target of the most recently inspected link', 'description': {'raw': \"1. Create a page with two links that point to the same page or URL, and a link that points to a different page/URL\\n2. Inspect one of the twin links with the link inspector. The suggestions dropdown is displayed (*)\\n3. Inspect the other twin link. The suggestions dropdown isn't displayed\\n4. Inspect the third link. The suggestions dropdown is displayed again\\n5. Inspect the link from #3. The suggestions dropdown is displayed now\\n6. Close the inspector, the inspect the same link again. The suggestions dropdown isn't displayed\\n\\nThis is because the value in the text input doesn't change when you inspect the same link twice or inspect two links with the same target. The link inspector should consistently display the dropdown when it opens.\\n\\n(*) I would argue that we should /not/ display the dropdown in this case, IMO it's useless and confusing. But the point of this bug is that we should have consistent behavior.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402548843, 'spacePHID': None, 'dateCreated': 1382019060, 'dateModified': 1441912129, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55839', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Don't fragment bugzilla conversation/IRC output\", 'description': {'raw': 'According to https://gerrit.wikimedia.org/r/#/c/54984 , the new wikibugs code (not yet deployed) will split the wikibugs output into a myriad of channels (this is independent from the name of the default channel).\\n\\nThis fragmentation is very annoying because it effectively subtracts important parts of the code/development/discussion from the normal public view on the main channel (whatever its name is) even though they are offtopic, hiding them in some secondary channel.\\nThe secondary channels should receive additional copies of the relay, but not remove them from the main channel if they are on topic (for instance, the visual editor for MediaWiki obviously is on topic for #mediawiki and #wikimedia-dev).\\n \\nAs a fallback, if people really think those products are so unimportant/trashy (\"noise\") as to be ignored by people on the main channel, I\\'d like a single unified feed somewhere, e.g. #mediawiki-feed (it\\'s not clear to me what wm-bot4 [~wm-bot@wikimedia/bot/wm-bot] is doing there exactly).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52529\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=10760'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400568876, 'spacePHID': None, 'dateCreated': 1381952940, 'dateModified': 1400568876, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55807', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support the Command+Delete keyboard command on Mac (delete current line) and others', 'description': {'raw': 'On Chrome Version 30.0.1599.69 on Mac OSX 10.8.5 the Command+Delete keyboard shortcut is ignored. In most text editors it deletes the entire line of content (try it in gmail or on bugzilla!)\\n\\nThe Option+Delete keyboard key (to delete the previous word) and Option+Fn+Delete (to delete the following word) do work correctly. There is no Command+Fn+Delete shortcut.\\n\\nI do not have easy access to test this shortcut on other versions of Chrome, nor do I know what the shortcut is on Firefox.'}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1434667863, 'spacePHID': None, 'dateCreated': 1381942500, 'dateModified': 1438734469, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55799', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Highlights triggered while resizing aren't moved correctly\", 'description': {'raw': \"While resizing an image with live preview, the highlight on the image is updated correctly. But if you mouse over another image while resizing, then that image's highlight isn't updated for the resize. This is a problem in situations where resizing the first image moves the second image, in that case the highlight stays where it was when you first entered the image.\\n\\nMaybe we just shouldn't show highlights at all while dragging?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55789\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400696049, 'spacePHID': None, 'dateCreated': 1381926000, 'dateModified': 1424894572, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55787', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Move floating functionality from SurfaceToolbar to Toolbar?', 'description': {'raw': \"The floating code is in ve.ui.SurfaceToolbar instead of OO.ui.Toolbar, but cursory inspection of the code indicates that it doesn't reach into the surface and doesn't receive any events from the surface, apart from a minor bit that ensures the cursor isn't obscured by the toolbar.\\n\\nWanting to float a toolbar seems generic enough, so couldn't this be made into generic OO.ui functionality?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1381921260, 'dateModified': 1643977436, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55784', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying and pasting results in new blank section heading: \"== <nowiki /> ==\"', 'description': {'raw': \"Intention:  To create a block of text to check line wrapping.\\n\\n\\nExpectation:  That I'd end up with a block of plain paragraph-formatted text.\\n\\n\\nSteps to reproduce:\\n\\n1)  Start with a page containing some text and a few section headings.  In my case, it was a list.  \\n\\n2)  Select all the text in one section using arrow/cursor keys, including all of the last line (including the blank part at the end of the paragraph), but none of the section heading that follows.\\n\\n4)  Copy this.\\n\\n5)  Make a new, blank paragraph-formatted line.\\n\\n6)  Paste the copied text into the new line.\\n\\n\\nResults:  You get the desired paragraph, followed by a == <nowiki /> == section heading.\\n\\nSee https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=577354576&oldid=577352415\\n\\n(For bonus points, if you skip step #5, you'll get your pasted text set to ==Section heading== formatting.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\n{T52100}\\n{T61647}\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426893936, 'spacePHID': None, 'dateCreated': 1381881120, 'dateModified': 1428879415, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55769', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Multiline list items rendering differently in ContentEditable than the resulting wikitext', 'description': {'raw': 'This is an interesting issue that, as far as I understand, can be either (or both) VE and Parsoid, and seems to be limited by wikitext. \\n\\nI\\'m not entirely sure what the strategy here should be -- If the final article markup is \"the way things are supposed to be\" then the fix should be to correct the way things look to the user in ContentEditable so they match the final article display. \\n\\nHowever, there might be a creative way to manipulate the wikitext in Parsoid (or the html VE sends to Parsoid) so that the end result fits what VisualEditor presents.\\n\\nThe first solution will disallow multiline list items. The second solution would run the risk of having html tags in wikitext, or worse, having the dreaded dirty diffs if the desired multiline list item is more complex.\\n\\nHere\\'s how to see the issue:\\n(Refer to this image: http://mg.viewskew.com/mgoblin_media/media_entries/432/ve_listbug.png )\\n\\n1. Edit some wiki page (can be empty/new)\\n2. Type 3-4 lines\\n3. Mark the lines and make them a list with the list button\\n4. Go to the second element (or whatever one that is in the middle of the list)\\n5. Go to the end of that listItem\\'s line, and hit \"Shift-Enter\"\\n6. In VisualEditor, the behavior is similar to other word processors with multiline list element -- you get a second line that is indented the same as the list item you\\'re under.\\n7. Type something so you have text on that multiline segment. (#1 in the image) \\n8. Click \\'save\\' and review changes; wikitext is not representing what we see on the screen (see #2 in the image)\\n9. Save the article -- the article presents a different format than what VE showed (#3 in the image) and presents a different content to edit if we want to edit that article again (#4 in the image)\\n\\nThe way I see it (and I may well be wrong, as I\\'m not that familiar with wikitext) -- we can either fix this bug so VE presents the same display as the final article (as in, disallow shift-enter in lists) or we need to split multiline items into paragraphs that can render as such into wikitext (not sure if that\\'s possible) -- the other alternative is to force a <br /> on multiline lists, which would make the wikitext into something like\\n\\n* item 1\\n* item 2\\n* item 3<br />and its multiline\\n* item 4\\n\\nAnd that works perfectly in the article and in edit mode -- but it can be limited in what can be done inside a multiline list item, and requires the use of <br /> tag inside the wikitext. \\n\\nAlso, there may be more cases of complex list items with VE\\'s expanding features. For instance, there can be cases where a multiline list item should contain a certain language block, or a short code highlight segment, or a <math> block. Right now they render proplery in CE if added as multiline list item, but break the list and become separate paragraph items on save.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701961626, 'spacePHID': None, 'dateCreated': 1381854300, 'dateModified': 1701961626, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55746', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wrong link rendered in edit mode when you click link in drop-down', 'description': {'raw': \"To reproduce:\\n\\n1. Goto https://en.wikipedia.org/w/index.php?title=Lancaster,_Pennsylvania&oldid=576777823&veaction=edit\\n3. Highlight 'Brownfields'\\n4. Press Ctrl-K\\n5. Type 'brownfield land' as target.\\n6. Click matching entry in drop-down once to accept.\\n7. Click on unrelated text to hide the link widget.\\n\\nThe internal representation is correct (as shown in e.g. 'Review your changes'), but the displayed/rendered link goes to https://en.wikipedia.org/w/Brownfields , not the correct target.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402549905, 'spacePHID': None, 'dateCreated': 1381813980, 'dateModified': 1441912141, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55724', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fetch new image rendering after resize', 'description': {'raw': 'To prevent images which have just been scaled up from looking pixelated.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381966927, 'spacePHID': None, 'dateCreated': 1381761840, 'dateModified': 1417572822, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55697', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add mediawiki.ui dialogs', 'description': {'raw': 'mediawiki.ui should have dialogs/modals.  The new dialogs in GettingStarted can be used as a starting point, but more work is needed.  This includes choosing the right level of abstraction, and how to implement them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1426301201, 'spacePHID': None, 'dateCreated': 1381359000, 'dateModified': 1463778127, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55534', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MWSyntaxHighlight* is badly broken', 'description': {'raw': 've.dm.MWSyntaxHighlightNode.static.toDataElements:\\n* Assumes it always receives two DOM elements, one div and one span. This is dependent on an interaction issue between Parsoid and MediaWiki, and isn\\'t always the case.\\n* Stores the span and the div as two separate attributes, rather than a single domElements attribute containing an array\\n* Stores the span and the div by reference rather than cloning them\\n\\nve.dm.MWSyntaxHighlightNode.static.toDomElements:\\n* Assumes attributes.span is always set, although per the above it may be undefined. In case it is undefined, this function returns [<div>, undefined] which ends up crashing VE with a DOM error (\"DOM Exception 8\") because undefined is fed to appendChild() by the converter\\n* Uses attributes.div and attributes.span by reference. This is bad because:\\n** calling .appendChild() on a node that\\'s already attached elsewhere removes it from its old location\\n** the original nodes received by toDataElements() are in a different document than the output of this function is supposed to be, so we end up attaching nodes to the wrong document\\n** the correct way to do this is ve.copyDomElements( originalDomElements, doc ) where doc is the second parameter\\n* Unconditionally sets the data-mw attribute, without checking if anything actually changed. This should be avoided, because reordering of keys in the JSON blob may dirty the DOM and trigger a corruption warning. See the last bit of ve.dm.MWReferenceNode.static.toDomElements (dealing with originalMw) for an example of how to do this correctly\\n** Note that this .setAttribute() call is once again modifying the original <div> by reference\\n* Assumes attributes.div is always set, which won\\'t be true for newly created MWSyntaxHighlightNodes that didn\\'t come from Parsoid but were created by the user in VE. For such nodes, the .setAttribute() call will crash the editor. But we never get there because ...\\n\\nve.ui.MWSyntaxHighlightDialog.prototype.onOpen:\\n* Assumes that there\\'s always a FocusedNode when the dialog opens. However, this isn\\'t true in creation mode (i.e. when opening the dialog from the toolbar without selecting an existing node), and so opening the dialog in creation mode crashes the editor when trying to do this.sourceNode.getModel(). This means it\\'s impossible to create new MWSyntaxHighlightNodes with VE\\n* Note that there\\'s also no if ( this.sourceNode instanceof ve.dm.MWSyntaxHighlightNode ) check, which means this dialog will attempt to edit other types of nodes if it\\'s opened while such a node is focused\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1381358700, 'dateModified': 1445531027, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55533', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enforce proper nesting of most templates, and encapsulate compound content blocks', 'description': {'raw': 'Transclusions can currently affect arbitrary parts of the page by producing unbalanced HTML. This makes both WYSIWYG editing and efficient updates difficult. We would thus like to move towards properly nested templates as much as possible. For existing multi-transclusion content we would like to enforce nesting as a unit, possibly using a <domparse> extension-like tag wrapping such a content block. This would still let us reuse expansions for multi-template content, which is important for large list pages like http://fr.wikipedia.org/wiki/Liste_des_premiers_pr%C3%A9fets_fran%C3%A7ais_(1800-1815).\\n\\nThe solution should:\\n* work with old and new revisions, with predictable HTML diff behavior\\n* support multi-transclusion/extension content reuse\\n* support a mix of transclusions, extension tags and page content\\n* work well with the VisualEditor preview\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1582154924, 'spacePHID': None, 'dateCreated': 1381345200, 'dateModified': 1582154924, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55524', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'PHP CodeSniffer reports line length based on bytes, not on characters', 'description': {'raw': \"From https://integration.wikimedia.org/ci/job/mwext-cldr-phpcs-strict/1/console:\\n\\n11:21:52 FILE: ...nkins-slave/workspace/mwext-cldr-phpcs-strict/CldrNames/CldrNamesMy.php\\n11:21:52  643 | ERROR   | Line exceeds maximum limit of 120 characters; contains 162\\n11:21:52  648 | WARNING | Line exceeds 100 characters; contains 109 characters\\n\\nThese are the lines in question:\\n\\n\\t'UM' => 'ယူနိုက်တက်စတိတ် အပြင်ထွက် နေသည့် သေးငယ်သောကျွန်းများ',\\n\\t'VC' => 'စိန့်ဗင့်ဆင့်နှင့် သည်ဂရဲနာဒင်းစ်',\\n\\nAssuming tab width is 4, the line lengths are 67 and 48 respectively.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-w5a723w3wes6jd5wskgg', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382434399, 'spacePHID': None, 'dateCreated': 1381318620, 'dateModified': 1425968821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55508', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Disable jquery.IME operating on VisualEditor surfaces', 'description': {'raw': \"Right now jQuery.IME is horrendously, horribly broken when using VisualEditor (a quick perusal of bugs that make it unusable include bug 54421, bug 53700, bug 53701, bug 53705, bug 53706, bug 53711, bug 54283, bug 54331, bug 54334 and others).\\n\\nHaving the jQuery.IME icon show up when it is actively broken makes a promise to the user that we can't possibly hope to meet right now.\\n\\nPlease disable jquery.IME from VisualEditor surfaces entirely until we can get some proper testing and work done.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-m2yck6646cdt5t6zkta4', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381329332, 'spacePHID': None, 'dateCreated': 1381280040, 'dateModified': 1381329931, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55492', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: DM's list of the page's categories can be invalidated by e.g. adding a template that inherits a category\", 'description': {'raw': \"When adding a template that also adds a category, after saving the list of categories is not updated until the page is reloaded.\\n\\nTo reproduce:\\n\\n1. Load any page in VE\\n2. Add any template that also adds a category, e.g. {{user en}}\\n3. Save page\\n\\nExpected behaviour: The list of categories includes the newly added category, e.g. [[Category:User en-N]]\\nActual behaviour: The list of categories is not updated.\\n\\nIt doesn't seem to matter whether the category is plain or hidden.\\n\\nFirefox 24 on Linux using Monobook skin\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1381104060, 'dateModified': 1416846180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55382', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Epic] VisualEditor: Implement some form of auto-save to help with browser crash recovery and accidental tab closing', 'description': {'raw': 'With wikitext editing, people work around this by writing long articles in word, or relying on browsers remembering form data if it crashes.\\n\\nPerhaps with local storage we can take periodic snapshots of DM HTML, or even the entire surface state (DM data, IV store, internal list, transaction history etc.) and offer to restore it if the changes went unsaved.\\n\\nSee also:\\n* T39992 - Review and deploy Drafts extension to Wikimedia wikis\\n* T75241 - Auto-save to increase chances of lost edits recovery'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1520342434, 'spacePHID': None, 'dateCreated': 1381073520, 'dateModified': 1660398888, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55370', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid cannot connect to https-only host?', 'description': {'raw': \"Hi\\nWhen I run parsoid linked to a wiki which is https only, it doesn't work. This can be reproduced in any installation.\\n\\nI set port 80 to be a redirect to port 443, and the parsoid URL is https://wiki.name/api.php in localsettings.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-vj2bbc63joi46qr5a5nq', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1428267398, 'spacePHID': None, 'dateCreated': 1381073520, 'dateModified': 1428267398, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55369', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link tooltip is not updated if link inspector is not explicitly closed', 'description': {'raw': 'Germanjoe reports:\\n\"A small (very small) bug: mouse display of links doesn\\'t get actualized, when the editor leaves the small edit dialog to change links without pressing the \"<\" button (just by clicking somewhere else in the text the edit dialog closes aswell). \\n\\nExample: change German to \"German language|German\" in some test article and leave the link editor without pressing \"<\". The mouse display should show \"German language\" as internal link info, but still shows \"German\". However, \"German language|German\" is correctly saved to the source text (just the display is wrong).\"\\n\\nFurther testing shows that this can be demonstrated multiple ways. In all cases close the link input widget by clicking elsewhere on the editing surface, do not click < (that works as expected)\\n\\n*Change \"[[German]]\" to \"[[German language|German]]\". Tooltip is \"German\" (expected \"German language)\\n*Change \"[[Welsh language]]\" to \"[[Welsh language literature|Welsh language]]\". Tooltip is \"Welsh language\" (expected \"Welsh language literatue\")\\n*Change \"French\" to \"[[French language|French]]\". Tooltip is \"French\" (expected \"French language\")\\n*Change \"Portuguese\" to \"[[Brazillian|Portuguese]]\". Tooltip is \"Portuguese\" (expected \"Brazillian\")\\n*Change \"Polish language\" to \"[[Polish Language Council|Polish language]]\". Tooltip is \"Polish language\" (expected \"Polish Language Council\")\\n\\nThe tooltip is corrected as soon as one of the following actions happens:\\n*The link input widget is opened on that link again. Even if no changes are made and it is closed by clicking elsewhere.\\n*The link display text is amended on the editing surface, e.g. \"[[Polish Language Council|Polish language]]\" → \"[[Polish Language Council|Polish informal language]]\"\\n*Text is typed adjacent to either end of a link, e.g. [[Italian]] → [[Italian]]s\\n*Annotation is applied to the display text.\\n\\nI\\'ve marked the severity as \"trivial\" because in all cases the correct target is displayed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402549108, 'spacePHID': None, 'dateCreated': 1380909000, 'dateModified': 1441912154, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54984', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Spellcheck freaks out in Firefox when focusable nodes are focused', 'description': {'raw': \"* Open a document in a language that is not your default language,\\n  for example:\\n  https://fr.wikipedia.org/wiki/Cumul_des_mandats_en_France?veaction=edit\\n  (if you're not French).\\n* Assuming your browser does have a French dictionary, the article should\\n  have few to 0 red-underlined words.\\n* Click on a [1] reference.\\n* Observe suddenly almost every word is spellcheck invalidated by red lines\\n* Moving the cursor by keyboard arrows still keeps them invalid.\\n* As soon as you actually use the mouse to click for a cursor move, that is\\n  when it switches back to the correct language (or perhaps it disables\\n  spellcheck)\\n\\nNot sure, but I think this is a regression.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1530906787, 'spacePHID': None, 'dateCreated': 1380896700, 'dateModified': 1530906787, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54975', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid renders template as comment, breaking serialization', 'description': {'raw': 'I simply deleted a word from the leading paragraph in the article below, and got this as diff:\\nhttps://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9%3ANurick%2F%D7%91%D7%93%D7%99%D7%A7%D7%95%D7%AA_-_%D7%A2%D7%95%D7%A8%D7%9A_%D7%97%D7%96%D7%95%D7%AA%D7%99&diff=14670508&oldid=14667916\\n\\nTo reproduce: Revert to the previous version in that diff, edit the article in VE, and delete a word from the leading paragraph.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382551948, 'spacePHID': None, 'dateCreated': 1380822960, 'dateModified': 1383851745, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54927', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Linktrail & linkprefix appear to be active on zhwiki when they shouldn't be\", 'description': {'raw': 'Repro:\\n\\n1. Create a new page with wikitext \"[[中文]]\" on zhwiki\\n2. VisualEditor-edit this page and type \"s\" at the end\\n3. The whole document now looks as if it has a link to \"中文\" with text \"中文s\"\\n4. Save the page\\n5. Resulting wikitext is \"[[中文]]s\", and in rendered HTML (both PHP and Parsoid - bug 41151), \"s\" is not a part of the link text\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381273288, 'spacePHID': None, 'dateCreated': 1380741240, 'dateModified': 1417572823, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54891', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Long labels in the toolbar's format drop-down causes text to scroll under the down-arrow or be split into two lines\", 'description': {'raw': 'See https://fr.wikipedia.org/wiki/Fichier:Bug_%C3%A9diteur_visuel_barre_de_menu_style_de_texte_sur_deux_lignes.png .\\nIn languages like French and Italian some options in that menu are long (multiple words names like Titre de section) and the last word will appear under the toolbar itself.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380837026, 'spacePHID': None, 'dateCreated': 1380711000, 'dateModified': 1417584747, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54870', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Welcome to VisualEditor\" iframe causes Chrome to re-render the page', 'description': {'raw': 'Best seen on a slow connection e.g at crossbrowsertesting.com; I used Chrome 29 on OSX 10.7\\n\\nSeen on beta labs and test2wiki with a fresh browser instance: \\n\\n* Click Edit/beta, invoke VE\\n\\n** View of page appears, then disappears, refreshes and appears again before \"Welcome to...\" iframe appears\\n\\n* Click X to dismiss iframe\\n\\n** iframe disappears for a moment, then reappears, then disappears again\\n\\nGiven a slow enough connection, this behavior could be bothersome for regular users of VE.  \\n\\nIt definitely causes constant failures in the browser tests for Chrome on both beta labs and test2wiki. \\n\\nThis is not seen in Firefox\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55756'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381934805, 'spacePHID': None, 'dateCreated': 1380670380, 'dateModified': 1417596633, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54854', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing \"enter\"/\"return\" on a selected node should open its dialog', 'description': {'raw': 'When a template is selected in the VE editing surface pressing enter should open the transclusion dialog.\\n\\nWhen an image is selected in the VE editing surface pressing enter should open the media settings dialog.\\n\\nThese will be of benefit to people making textual changes to the surrounding context who want to make textual changes to the template output / image caption.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50996'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395274918, 'spacePHID': None, 'dateCreated': 1380637920, 'dateModified': 1443276357, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54827', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images: {{largethumb}} template on nlwiki getting substituted on save', 'description': {'raw': \"**Author:** `romaine.wiki`\\n\\n**Description:**\\nThe VisualEditor substitutes templates that shouldn't been substituted. The largethumb template got substituted on several occasions, like:\\n\\nhttps://nl.wikipedia.org/w/index.php?title=Managua_%28stad%29&diff=38749742&oldid=38743043\\n\\nIf this continues to happen too long, we are forced to disable the VisualEditor for everyone as it changes things that absolutely should not be changed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54315\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392422883, 'spacePHID': None, 'dateCreated': 1380575880, 'dateModified': 1392422883, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54803', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Linebreaks not preserved when converting preformatted text to paragraph text. ↵ Displayed in VE but not saved.', 'description': {'raw': 'Screenshot explaining issue with visualeditor\\n\\nHi\\nThese are the steps:\\n\\n*Create a preformatted multiline text, inserting a space before each line, in source mode.\\n*Open visualeditor, select the text inside the box (the preformatted text)\\n*Change text type to \"paragraph\"\\n*The text is badly converted, return characters appear on the line. If the text is saved the return characters are lost.\\n*This happens in other cases too, tab symbols are displayed sometimes.\\n\\nThank you.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12384}'}, 'authorPHID': 'PHID-USER-vj2bbc63joi46qr5a5nq', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1380563940, 'dateModified': 1421281953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54794', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way (beyond Ctrl-Click, middle-click, or right-click/tab) to open links in another window', 'description': {'raw': \"I couldn't find a way to click the links while editing and go to the target page. It's not easily available in the source editor, so it's not really a regression, but I find myself needing this features every time I edit, because the links are blue and look like links.\\n\\nGMail and Google have reasonably good ways of going to links' targets in editing mode, so hints can be taken from them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50321\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405375886, 'spacePHID': None, 'dateCreated': 1380443280, 'dateModified': 1441912160, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54759', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show user that drag-and-drop of textual content is not supported', 'description': {'raw': \"+++ This bug was initially created as a clone of Bug #50643 comment 6 +++\\n\\nSteps to reproduce:\\n1. Edit a page in VE\\n2. Select a piece of textual content without any fancy stuff in it.\\n3. Drag it to another location in the page\\n\\nExpected results:\\nThe cursor should be a disabled-drop icon\\n\\nActual results:\\nThe cursor is an 'image' icon\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403008828, 'spacePHID': None, 'dateCreated': 1380437160, 'dateModified': 1417572217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54757', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dropdown clipping is a bit too aggressive', 'description': {'raw': \"Dropdown clipping\\n\\nReferring to the attached screenshots there are two issues:\\n\\n1. The width is not adjusted to account for the OS scrollbacks. I assume this is because has one of those fancy Macintosh computers that doesn't know how to draw a big chunky old-fashioned scroll bar.\\n\\n2. The assumption is made the the height of the VE container is the maximum height the scrollbar expand to. Here that is clearly not the case. It may be the case that because we don't know what lies beyond the borders of VE (e.g. z-index 9999 banner), we can't do anything about this. Maybe we can make the assumption the page content is sane, and if the dropdown ends up obscured, leave that as an integration problem for the user?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=69707\\n\\n**Attached**: {F12176}\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415881674, 'spacePHID': None, 'dateCreated': 1380295440, 'dateModified': 1443278228, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54705', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Switching from categories to languages while suggestion popup is open doesn't close popup\", 'description': {'raw': \"Screenshot of languages dialog tab with the new-category popup in front\\n\\nSwitching from categories to languages while suggestion popup is open doesn't close popup -- see screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12105}\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398184329, 'spacePHID': None, 'dateCreated': 1380219960, 'dateModified': 1417572411, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54657', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Category editing tool should preview or at least link to the input categories', 'description': {'raw': \"Screenshot of category dialog, showing no apparent way to get at the listed categories\\n\\nThe category suggestion tool seems to provide a simple typeahead search, but provides no way to go and see if the categories you've found are relevant.\\n\\nAt a minimum, you should be able to open up the category page via a link from the search box and and the little tag display.\\n\\nBetter still might be a little preview that pulls the description text (if any) and some sample contents right within the dialog box.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F12103}\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1380219780, 'dateModified': 1643977437, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54656', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make tutorial video on how to use Bugzilla', 'description': {'raw': \"This is kind of a meta bug and not an actual issue in BZ. Couldn't think of a better place to file it...\\n\\nFiling bugs/enhancements is difficult for some people to figure out. We can lower the barrier pretty easily by making a 1 or 2 minute video showing you how. Upload to commons, link to from BZ main page.\\n\\nKey components:\\n- Sign up\\n- Choosing the right product\\n- Giving clear description of the problem/request\\n-- Screenshots are fantastic\\n-- Providing links is great too\\n- Make sure to emphasize to not worry about filling all the fields out properly, the important step is opening the bug!\\n\\nMajor props to User:Biosthmors on enwiki for coming up with the idea.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**Whiteboard**: gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks\\n**URL**: https://commons.wikimedia.org/wiki/File:How_to_file_a_report_in_Bugzilla.webm\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52696\"}, 'authorPHID': 'PHID-USER-oetk6bbl6omm354ejz3b', 'ownerPHID': 'PHID-USER-oyf7m4w6q3dcftbg22jg', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389653591, 'spacePHID': None, 'dateCreated': 1380129240, 'dateModified': 1389707273, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54606', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Improve handling of stray table tags / Verify that we handle stray table tags correctly', 'description': {'raw': 'Occasionally, pages have stray opening table tags which may end up screwing up DSR computations (which in turns messes up selser). It is possible that our latest foster parenting code implicitly handles this by wrapping the entire table as templated and protected a large body of code (which could then serve as a flag to the user to look for bugs in the wikitext souce). So, it might be worth verifying this and adding tests to spec this behavior.\\n\\nSee the bug report: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=574391235#Duplicated_content_when_deleting_apparently_blank_lines\\n\\nSee my response that fixed the problem in the wikitext source: https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=574483272#References_and_tables\\n\\nIf this is not already handled by our handleUnbalancedTables and markFosteredContent DOM passes, we may need to tackle this -- by maybe adding a fixup in TokenStreamPatcher that enforces limited table scope (section boundaries is the obvious scope limiter => close unclosed tables whenever section heading tokens are encountered).\\n\\nTo be investigated and fixed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1592505284, 'spacePHID': None, 'dateCreated': 1380128640, 'dateModified': 1592505284, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54605', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Large number of CSS rules for external links', 'description': {'raw': 'Assigning to Parser as I suspect this is what would need to be fixed up to support this.\\n\\nThis patch [1] demonstrates the large number of rules exist for external links:\\n\\nThe browser matches styles from right to left, so the rightmost selector is really important.\\n\\nWe shouldn\\'t need to have to resort to CSS rules in the form div#content a.external[href ^=\"https://\"] - a link with class external should also have a class describing what type of external link it is if it is necessary. These selectors are less efficient and are not supported by older browsers.\\n\\nIdeally we should simply these rules to become something like:\\n\\n.link-audio,\\n.link-video,\\n.link-document,\\n.link-irc,\\n.link-ftp,\\n.link-https,\\n.link-news,\\n.link-mailto {\\npadding-right: 13px;\\nbackground: transparent center right no-repeat;\\n}\\n\\nwith rules for each of them for their correct icon.\\n\\n[1] https://gerrit.wikimedia.org/r/#/c/85920/2/skins/vector/externalLinks.less\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63725\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63521'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1418744455, 'spacePHID': None, 'dateCreated': 1380128040, 'dateModified': 1641334856, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54604', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: this.referenceSurface should be a Surface, not a SurfaceWidget', 'description': {'raw': \"In ve.ui.MWReferenceDialog, this.referenceSurface changed from being a Surface to a SurfaceWidget. I noticed this because I rebased some old code that used this.referenceSurface.getModel() and broke, but this seems to have happened a while ago with the introduction of SurfaceWidget.\\n\\nWhen a variable name is 'fooSurface', it should be a Surface, not something else. In particular, you shouldn't have to do this.referenceSurface.getSurface() to get the surface.\\n\\nThe same applies to this.captionSurface in ve.ui.MWMediaEditDialog.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1533388170, 'spacePHID': None, 'dateCreated': 1380077400, 'dateModified': 1533388170, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54588', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserting a reference breaks up annotations around it', 'description': {'raw': 'When you insert a reference in the middle of a bolded word, the reference itself doesn\\'t receive a bold annotation, and so the resulting text is something like \\'\\'\\'He\\'\\'\\'<ref name=\"hello\" />\\'\\'\\'llo\\'\\'\\', with the bold breaking around the reference.\\n\\nWhen we insert inline nodes like references from the UI, they should take annotations. This is probably a wider problem beyond just references.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1380074640, 'dateModified': 1420844151, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54587', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: MWExtensionNode/GeneratedContentNode should avoid emitting 'rerender' twice when rendering <img>s\", 'description': {'raw': \"ce.MWExtensionNode.onParseSuccess contains the following code:\\n\\n\\t// Rerender after images load\\n\\tthis.$.find( 'img' ).on( 'load', ve.bind( function () {\\n\\t\\tthis.emit( 'rerender' );\\n\\t}, this ) );\\n\\nProblems:\\n* Why is this in MWExtensionNode? Shouldn't it just be in GCNode?\\n* This potentially emits multiple rerender events, one for each image\\n* The first rerender event has already been emitted because we've already resolved the promise and attached the nodes to the DOM\\n\\nWhat we should really do is attach the nodes somewhere else (where?) so that the images load, then reattach them to a wrapper and resolve the promise with that. That way we only emit rerender once, and we correctly only resolve the promise once everything has actually loaded.\\n\\nIn practice, this means the math inspector moves around twice after typing LaTeX in certain cases: once because of the 'rerender' event caused by the <img> tag being put on the page (at which point it measures 0x0), and once because of the 'rerender' event caused by the image actually loading (at which point it measures correctly).\\n\\nOpen questions:\\n* How does this work for images with invalid/unavailable sources?\\n* Really what we care about here is the dimensions of the images. If those are known, we can render the node without its dimensions changing later\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380232745, 'spacePHID': None, 'dateCreated': 1380072600, 'dateModified': 1417572831, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54584', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ce.GeneratedContentNode.generateContents() should be static, so we can cache based on config objects alone', 'description': {'raw': \"Right now, GCNode caching uses both the model hash and the hash of the config object. However, when properties in the config override properties in the model, the preview of a change and the new model node after the actual change will be the same but have different hashes (because the model is different, and because in the second case the config object is empty/undefined).\\n\\nWe should make generatedContents() static, so it can't inspect the model or any object state, and have a function that provides the default config that is then used to extend the provided config. That way we don't end up duplicating things in cache and rendering things twice.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1380071580, 'dateModified': 1643977437, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54582', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Bugzilla data scanned for tech metrics must be aligned with repos scanned', 'description': {'raw': \"Currently http://korma.wmflabs.org/browser/its-repos.html shows that the Bugzilla products scanned are MediaWiki, All extensions, VisualEditor and Parsoid. However, this list must be in sync with http://korma.wmflabs.org/browser/scm-repos.html - which in turn is synced with https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects\\n\\nLet's update that wiki page with the relevant products / components. A 100% match is probably impossible, but a 90% (or so) should be feasible.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49744\"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382549565, 'spacePHID': None, 'dateCreated': 1379952300, 'dateModified': 1382560830, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54469', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Broken wikitext with bold inside and outside a label wrongly interpretted as correct by Parsoid', 'description': {'raw': '**Author:** `jmichrina`\\n\\n**Description:**\\nExample:\\nLine from \"International_Air_Transport_Association_airport_code\"\\n\\nDFW for Dallas–Fort Worth, DTW for Detroit–Wayne County, RDU for Raleigh–Durham, MSP for Minneapolis–St. Paul and LBA for Leeds Bradford (Airport).\\n\\nLine appears correctly formatted in editor [caps represent bold]:\\ndfw for Dallas-Fort Worth, dtw for DetroiT-Wayne county, rdu for Raleigh-DUrham, msp for Minneapolis-St. Paul and lba for Leeds Bradford (Airport).\\n\\nLine appears incorrect on page [caps represent bold]:\\ndfw for DALLAS-FORT WORTH, stw for dEtROIT-wAYNE COUNTY, rdu for RALEIGH-DURHAM, msp for mINNEAPOLIS-sT. pAUL and lba for LEEDS BRADFORD (AIRPORT).\\n\\nNote that the correct version appears in the editor even after it\\'s saved.\\n\\nPossibly related to bug 53208, but I didn\\'t have time to verify.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386117085, 'spacePHID': None, 'dateCreated': 1379880120, 'dateModified': 1386117085, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54454', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editor incorrectly selects slug and infobox onload', 'description': {'raw': 'Screenshot\\n\\nhttps://en.wikipedia.org/w/index.php?title=Daniel_Rowe_%28footballer%29&oldid=570278760&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11872}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380049211, 'spacePHID': None, 'dateCreated': 1379834460, 'dateModified': 1417572833, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54446', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Automatic Incorrect caret movement with ULS', 'description': {'raw': \"This is a separate report for automatic caret movement from one place to another when using VE with ULS.\\n\\nThis problem has been seen with some other bugs, specifically, in the fourth[1], seventh[2] and tenth[3] comments of Bug 53708 and the original report of Bug 54421\\n\\nI also suspect that the problem in Bug 53701 is a form of this bug only.\\n\\nHowever, I am reporting this as a separate bug since I was able to reproduce it independent of these bugs.\\n\\nSystem environment:\\nWin 7 X64 SP1\\nGoogle Chrome 29.0.1547.66 m\\n\\nTest Url:\\nhttps://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit\\n\\nSteps:\\n1 Enable ULS IME hindi transliteration\\n2 Take the caret to the end of the first paragraph using the mouse (i.e click at the end of the first paragraph to take the caret there)\\n3 Input [RETURN KEY][RETURN KEY]a\\n\\nExpected output:\\n[NEWLINE][NEWLINE]अ\\n\\nActual Output:\\n[NEWLINE]अ[NEWLINE]\\n\\nAs long as the return keys have been pressed, everything is fine and the caret is in the second newline. However, as soon as a is pressed, the input is in the first new line and not the second. The caret has hence moved up one line before the input is placed into the output text. The caret does not move back and is after the output अ\\n\\nThis text is selectable, but can't be copy-pasted into an external text editor.\\nThe text is removable, so this is not entirely Bug 53708 . However, pressing a backspace when the caret is after अ removes अ along with the newline that precedes it.\\n\\n[1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c4\\n[2]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c7\\n[3]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53708#c10\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453748480, 'spacePHID': None, 'dateCreated': 1379768640, 'dateModified': 1453749518, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54424', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Text duplication when using jquery.IME on existing pages', 'description': {'raw': 'Screenshot showing text duplication\\n\\nThis bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3\\n\\nThe entire test procedure is as follows:\\n\\nSystem Environment:\\nWindows7 X64 SP1\\nGoogle Chrome 29.0.1547.66 m\\n\\nTest Url:\\nhttps://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit\\n\\nSteps:\\nEnable ULS IME hindi transliteration\\nTake a caret to the end of the first paragraph using the mouse (i.e click at\\nthe end of the first paragraph to take the caret there.)\\nInput ag\\nOutput will be अग् as expected but with incorrect selection as reported in the comment linked above\\nFurther input a\\nThis causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.\\n\\nWhat should have happened:\\nThe original output अग् should have been changed to अग at the end of the first paragraph.\\n\\nSo effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated.\\n\\nNote: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11824}'}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749177, 'spacePHID': None, 'dateCreated': 1379764980, 'dateModified': 1453749516, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54421', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'browsertests: configure Zuul', 'description': {'raw': 'This is a sub project of bug 53697 https://www.mediawiki.org/wiki/Continuous_integration/Browser_tests\\n\\nIt covers setting up the Zuul configuration to trigger browser tests. From the wiki page:\\n\\nThe exact workflow would need to be figured out with the VisualEditor team. A first step would be to run the browser tests after a change has been merged and report back in Gerrit for their information.\\nAt first we will only want to run browser tests after a change has been merged. This let us load the system progressively without disrupting the VisualEditor authors.\\n\\nWe can later on make Zuul report back in Gerrit a message stating the result of the tests, that will raise awareness among developers and they can work on fixing the unsuccessful tests. Additionally, we can have the browser tests to be triggered on every patchset, the labs instance load will have to be carefully monitored.\\n\\nOnce tests are properly passing and the setup has been proven useful, we can make Zuul to block patchsets not passing the browser tests. The developers would then be required to fix the code or the test to have their change merged in\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385993818, 'spacePHID': None, 'dateCreated': 1379695800, 'dateModified': 1385993818, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54387', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add _rtselser end point in web api', 'description': {'raw': 'For end users and VE folks the non-selser _rt end point is often confusing, as it shows diffs that are normally avoided by selser. It would be useful to add a _rtselser end-point that serializes to HTML, re-parses that HTML (to catch foster-parenting issues) and then serializes it back with selser enabled.\\n\\nThis will provide us with a quick sanity check for the selser code, and a better link for end users and VE to establish that something has indeed dirtied the DOM.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-56wtmb23orq4pu5liyj5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380131264, 'spacePHID': None, 'dateCreated': 1379611080, 'dateModified': 1380131264, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54339', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Uncaught TypeError: Cannot call method \\'getOffset\\' of null\" triggered using jquery.IME', 'description': {'raw': \"Screenshot of Console Error and Blanked Page\\n\\nThis bug was found when testing per the sixth and seventh comment at Bug 53708\\nThis is very similar to Bug 54331 , however, this one is reproducible.\\n\\nSystem Environment:\\nWindows7 X64 SP1\\nGoogle Chrome 29.0.1547.66 m\\n\\nTest Url:\\nhttps://www.mediawiki.org/wiki/Project:Sandbox?veaction=edit\\n\\nSteps to reproduce:\\nEnable ULS IME hi transliteration\\nInput the following (below the 'Testing Area' heading):\\nagar[SPACE][SPACE][BACKSPACE][BACKSPACE]\\n\\nWhat happens:\\nApart from a bunch of buggy behaviour described in the seventh comment at Bug 53708 , the template is entirely removed and the following console error shows up once the second [BACKSPACE] is pressed:\\n\\nUncaught TypeError: Cannot call method 'getOffset' of null load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:231\\nve.ce.Document.getNodeAndOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:231\\nve.ce.Surface.showSelection load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:287\\nve.ce.Surface.onChange load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:274\\noo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139\\nve.dm.Surface.change load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:86\\nve.ce.Surface.handleDelete load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:286\\nve.ce.Surface.onDocumentKeyDown load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:267\\nproxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10\\nve.EventSequencer.onEvent load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:19\\n(anonymous function) load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:18\\njQuery.event.dispatch load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:45\\nelemData.handle.eventHandle load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:38\\n\\nThe file urls are:\\n\\nhttps://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*\\n\\nhttps://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11639}\"}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749226, 'spacePHID': None, 'dateCreated': 1379606220, 'dateModified': 1453749514, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54334', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Uncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds\" triggered using jquery.IME', 'description': {'raw': \"This bug was found when testing per the sixth and seventh comment at Bug 53708\\nIt seems somewhat heisenbuggy and I haven't been able to reproduce it yet. However, I'm sure of the steps which caused it.\\nReporting this so that it's documented in case it is ever seen again.\\n\\nSystem Environment:\\nWindows7 X64 SP1\\nGoogle Chrome 29.0.1547.66 m\\n\\nTest Url:\\nhttps://www.mediawiki.org/wiki/Project:Sandbox?veaction=edit\\n\\nSteps to reproduce:\\nEnable ULS IME hindi (hi) transliteration (labelled लिप्यंतरण)\\nInput the following:\\nagar[SPACE][SPACE][BACKSPACE]\\n\\nWhat happens:\\nApart from a bunch of buggy behaviour (described in the seventh comment at Bug 53708 ), the following console error shows up once the [BACKSPACE] is pressed:\\n\\nUncaught Error: ve.dm.Document.getNodeFromOffset(): offset 804 is out of bounds load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:106\\nve.dm.Document.getNodeFromOffset load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:106\\nve.dm.Surface.change load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…wPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:84\\nve.ce.Surface.onSelectionChange load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:275\\noo.EventEmitter.emit load.php?debug=false&lang=hi&modules=ext.visualEditor.base%2Cmediawiki%2Cvi…ck%7Coojs%7Cunicodejs.wordbreak&skin=vector&version=20130919T025548Z&*:139\\nve.ce.SurfaceObserver.pollOnceInternal load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:292\\nve.ce.SurfaceObserver.pollOnce load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:291\\nve.ce.SurfaceObserver.timerLoop load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperim…PageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*:290\\nproxy load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.…l%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z:10\\n\\nThe file urls are:\\n\\nFor the last line:\\nhttps://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=jquery%2Cmediawiki%2CSpinner%7Cjquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil%7Cmw.MwEmbedSupport&only=scripts&skin=vector&version=20130912T173512Z\\n\\nFor all other lines:\\nhttps://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=hi&modules=ext.visualEditor.core%2Cdata%2Cexperimental%2Cicons-vector%7Cext.visualEditor.viewPageTarget.icons-vector%7Crangy&skin=vector&version=20130919T025548Z&*\\n\\nAlso, the template's formatting was gone with the input hindi text appearing alongside the template text.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749257, 'spacePHID': None, 'dateCreated': 1379605200, 'dateModified': 1453749520, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54331', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Oldid pages' links to other versions in the page strapline (#contentSub) get hidden but are still there\", 'description': {'raw': 'I am trying to VEdit https://en.wikipedia.org/w/index.php?title=User:Elitre_%28WMF%29/Sandbox&oldid=573480590&veaction=edit , which is a blank version of my sandbox. There\\'s a lot of white space between the title of the page and the point where I can start adding text, and although the source editor says the page is really empty, looks like there\\'s still something there.\\n\\nIf I hover with the mouse right below the comma in the tagline \"Wikipedia, the free encyclopedia\", the cursor changes as if there\\'s an invisible link.\\n1) Right under the comma, the \"link\" points to my userpage (it\\'s clickable, and the page will open in the same tab);\\n2) some pixels below, the link will point to [[Help:Page History]];\\n3) going further down, it points to a diff of the sandbox.\\nThere are other points in the page which trigger the links, but the page history one is not easy to spot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52243\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58063'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389633364, 'spacePHID': None, 'dateCreated': 1379602440, 'dateModified': 1443276360, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54325', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Wikitech: Install TemplateData extension', 'description': {'raw': 'VisualEditor is installed already. Would be nice to have TemplateData as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1426690252, 'spacePHID': None, 'dateCreated': 1379590500, 'dateModified': 1426690280, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54316', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '(Re-) unify data and metadata', 'description': {'raw': \"Because about half the code in the DM is solely there to keep this delicate data structure together, and now that we don't need ±1 cursoring it seems like a lot of effort for nothing.\\n\\nThe behaviour it provides (protecting metadata from deletion) can all be done in the transaction builders, and in fact we already do this for internal lists)\\n\\nGoing forward this will make multi user editing a lot easier to.\\n\\nThat said this is going to be a massive commit.\\n\\n-----\\n\\nCurrently, MetaItems are stored outside the main linear data structure, in a separate meta linear data structure. This complicates the processing of linear data: transaction processing, rebasing, serialization/deserialization etc, and makes it harder to reason about document correctness. Instead:\\n* Store metadata as block nodes in the main data list\\n* On conversion from HTML, hoist metadata found in a content position to a legal structural position\\n* On conversion back to HTML, roundtrip metadata hoisted from unmodified content branch nodes back into the original content position\\n* When deleting across metadata (e.g. <p>foo[-</p><meta/><p>-]bar</p>), hoist metadata to a legal structural position as necessary\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '160', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1517245931, 'spacePHID': None, 'dateCreated': 1379550420, 'dateModified': 1682006049, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54299', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: ResizableNode should be able to live-preview the node it's resizing as you drag\", 'description': {'raw': 'This would also solve the problem of the resize marker having to snap into the right position at the end of a drag if you use the wrong handle (or any handle if the image is centred)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381936853, 'spacePHID': None, 'dateCreated': 1379549580, 'dateModified': 1417572822, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54298', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor jumps to the beginning of the sentence/paragraph when using jquery.IME', 'description': {'raw': '**Author:** `renukaalurkar`\\n\\n**Description:**\\n1)Logged in to http://en.wikipedia.beta.wmflabs.org/wiki/Main_Page\\n2)Go to your user page.\\n3)Click on Languages/cog, select Input and click on Enable Input tools.\\n4)Click on Edit beta tab.\\n5)Click on More, and using Media, select a couple of pictures\\n6)Click on the tiny keyboard/typewriter and select language as Hindi or Telugu\\n7)Now start entering text in Hindi or Telugu.\\n\\nObservations:\\n1)After typing a few letters, the cursor jumps back to the beginning of the sentence.\\n2)Sometimes, when Enter is hit, the cursor goes back to the beginning of the paragraph.\\n3)Sometimes, when Enter is hit one of the images disappears.Write some more and the other image also disappears.\\n4)Click on Save page button\\n5)Now both the images are visible again.\\n\\nObserved on Firefox 24.0 and Chrome 29.0.1547.66\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453748296, 'spacePHID': None, 'dateCreated': 1379529000, 'dateModified': 1453749529, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54283', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'RTL for Notification Tool: ? should be ؟ icon', 'description': {'raw': '? should be ؟ icon\\n\\nFor  Notification Tool for  RTL languages Please change \"?\" icon in attached image to RTL icon\\n\\nSee @Amire80\\'s comment.  Not the same for all languages.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54252\\n\\n**Attached**: {F11507}'}, 'authorPHID': 'PHID-USER-dswbdv7ibhsefllcqarz', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1488434919, 'spacePHID': None, 'dateCreated': 1379514480, 'dateModified': 1550841172, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54276', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Duplicating references groups', 'description': {'raw': 'See\\nhttps://en.wikipedia.org/w/index.php?title=Fizeau_experiment&diff=573001070&oldid=572299847 - the user corrected a typo and this resulted in the references groups getting duplicated.\\nReproduced in \\nhttps://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=573341379 and https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=next&oldid=573340833 while just testing wikilinks, as you can see. My first attempt to reproduce this actually resulted in more weird (although known, I think) behaviour: https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&diff=prev&oldid=573176079 .\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1429223936, 'spacePHID': None, 'dateCreated': 1379500080, 'dateModified': 1438734473, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54265', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: mw:Entity not preserved if data-parsoid missing', 'description': {'raw': 'Edit a page with One&nbsp;Two which displays as One Two.  Select the entire text, copy, past at end of the string.  Displays in VE fine at first.  Saving however produces One&nbsp;TwoOneTwo which displays as One TwoOneTwo. \\n\\nOriginally from \\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=573462315&oldid=573461696\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381554139, 'spacePHID': None, 'dateCreated': 1379493780, 'dateModified': 1548259483, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54262', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show percentage of progress in loading animation', 'description': {'raw': 'DKqwerty at en.wp reports: \"Article Futurama took 58 seconds to load into VE, with the loading bar running the entire time. I think this is unacceptable as it is probably off-putting to inexperienced users. Further, the bar just fills, empties, fills, empties, etc. rapidly and continuously until the page is loaded... Would it be possible to make this bar actually indicate what percentage has been loaded so editors have at least a hint that something is being processed?\"\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'dateClosed': 1427850989, 'spacePHID': None, 'dateCreated': 1379426040, 'dateModified': 1438733874, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54225', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Support for text/syntax/markup driven or WYSIWYG editable charts, diagrams, graphs, flowcharts etc. (Identify, develop, review and deploy extension on Wikimedia wikis to add)', 'description': {'raw': \"Moving here the following proposals:\\n<https://strategy.wikimedia.org/wiki/Proposal:Text_or_Syntax_driven_Charts,_Diagrams,_Graphs_and_more>\\n<https://strategy.wikimedia.org/wiki/Proposal:Editable_Graphics>\\n<https://strategy.wikimedia.org/wiki/Proposal:Markup_for_charts_and_graphs>\\n(with some of the participants in cc).\\n\\n* «By now Wikipedia has markup/code for everything—math (TeX), parser functions, location maps, and even SVG is supported. However, what is notably missing from many articles (other than high-quality portraits) are graphs and charts.»\\n* «There are many types of diagrams. The need for collaborative graphics is wide ranging, from map making to biochemical pathways to flow charts to genealogy to general charting. Each type of graphic has or could have a little language, XML or other representation to define graphics of that type succinctly. Whilst all can be presented as .pngs or .SVGs, the more succinct description is necessary for editability.»\\n\\nThis is distinct from bug 43616 (Provide a way to create interactive 2D/3D timelines and infographics e.g. Java applets, AJAX, Flash) in that it's not about *interactive* stuff and that there are some existing extensions which someone should assess and develop for Wikimedia purposes. I'd also leave maps out of it because that's being addressed (at last) elsewhere.\\nPart of it will be solved by bug 38271, but only to a degree.\\n\\nMentioned extensions: [[mw:Extension:Graph]], [[mw:Extension:GnuplotBasic]], [[mw:Extension:Plotters]], [[mw:Extension:WikiPlot]].\\n\\nKeywords from the proposals: http://bloodgate.com/perl/graph/, Java .jar, Flash .swf, Silverlight .scr, ActiveX .ocx, Vector (.svg) .svg (XML), AnyWikiDraw, AnyWikiDraw, WikiPathways, WikiTex, Graph Plugin, DPL Bundle, TeX, gluplot, pgfplots.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1379420040, 'dateModified': 1643977437, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54221', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Use node-jscs as checkstyle for javascript coding style', 'description': {'raw': \"See https://github.com/mdevils/node-jscs\\n\\nThis is the first tool I've seen in the category of asserting coding style for javascript that actually looks like it is worth looking into further.\\n\\nI intend to experiment with it in the near future for 1 or 2 projects, first in non-voting mode and perhaps later to become a standard enabled job for many projects.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409154874, 'spacePHID': None, 'dateCreated': 1379415660, 'dateModified': 1582796300, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54218', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Language link dialog should show language names and two-letter codes', 'description': {'raw': 'e.g. fr -> Français, cy -> Cymraeg\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386791658, 'spacePHID': None, 'dateCreated': 1379014140, 'dateModified': 1417572738, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54086', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <pre> tags have leading whitespace removed', 'description': {'raw': 'Around the time when VE started to support editing of pres we started to get dirty diffs like this:\\n\\nhttp://www.mediawiki.org/w/index.php?title=Parsoid&diff=779292&oldid=777387\\n\\nThis might either be a selser issue, or VE dirtying the DOM.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379569694, 'spacePHID': None, 'dateCreated': 1379007960, 'dateModified': 1417572834, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54083', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide support for BLP edit notices on enwiki', 'description': {'raw': \"For BLP's and disambiguation pages on the English Wikipedia, an extra edit notice is provided through the https://en.wikipedia.org/wiki/Wikipedia:EDITINTRO system using Extension:InputBox and some code in MediaWiki:Common.js. VisualEditor does not work with Extension:InputBox, so the edit notice is not displayed. \\n\\nThis hack is being used in several Wikimedia wikis besides the English Wikipedia:\\n\\n* https://ja.wikipedia.org/wiki/MediaWiki:Common.js\\n* https://zh.wikipedia.org/wiki/MediaWiki:Common.js\\n* https://vi.wikipedia.org/wiki/MediaWiki:Common.js\\n\\nSee also [[https://www.wikidata.org/wiki/Q10566946| Template:BLP editintro (Q10566946)]] and [[https://www.wikidata.org/wiki/Q14400704|  Template:Disambig editintro (Q14400704) ]] for more of the potentially affected wikis.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1692749630, 'spacePHID': None, 'dateCreated': 1378929900, 'dateModified': 1693089192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54029', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Investigate where we can replace setTimeouts with EventSequencer', 'description': {'raw': 'For example, onBeforePaste/onAfterPaste in ve.ce.Surface\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1378834020, 'dateModified': 1643977438, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension)', 'description': {'raw': \"<translate>…</translate> and the related <tvar>…</tvar> are currently un-parsed and shown as plain wikitext in VisualEditor because they're not recognised, per T50891; however, once that is fixed, the blocks won't be editable except as alien nodes (in wikitext), and won't be createable.\\n\\nMaking a proper VisualEditor plugin to translate these in-page as a rich editor shouldn't be particularly hard (he says…).\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1378773120, 'dateModified': 1694793076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53974', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Move to using white-space: pre-wrap instead of using nbsp's to fake spaces\", 'description': {'raw': ''}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1448930058, 'spacePHID': None, 'dateCreated': 1378691520, 'dateModified': 1544629304, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53931', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Hide \"version false\" in the help menu if it can\\'t be shown', 'description': {'raw': '== Steps ==\\n1) Go to\\nhttps://www.mediawiki.org/wiki/BUG?veaction=edit&uselang=en\\n2) Click on \"BETA\"\\n\\n== Actual result ==\\nThere is the text \"Version false\" generated by the HTML:\\n\\n<div>\\n <span class=\"ve-init-mw-ViewPageTarget-version-label\">Version</span> \\n <a class=\"ve-init-mw-ViewPageTarget-version-link\"\\n    target=\"_blank\"\\n    href=\"false\">false</a> \\n <span class=\"ve-init-mw-ViewPageTarget-version-date\"></span>\\n</div>\\n\\n== Expected result ==\\nThere should be some version number instead of the \"false\" text\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380740276, 'spacePHID': None, 'dateCreated': 1378656660, 'dateModified': 1417572829, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53917', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Protection edit notice should also show when under cascaded protection from another page', 'description': {'raw': 'Article tabs are wrong when page is protected via cascading from another page.\\n\\nTo reproduce: visit https://pl.wikipedia.org/wiki/Wikipedia:Strona_główna?uselang=en and behold the \"Edit source\" link, even if you\\'re anonymus.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=11700'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398277508, 'spacePHID': None, 'dateCreated': 1378575540, 'dateModified': 1443276361, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53893', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'provisioning browsertests role fails', 'description': {'raw': 'I added role \"browsertests\", but every time I run `vagrant provision` it fails. It seems to be trying to install an \"ffi\" (foreign function interface) module.\\n\\nFri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Using rake (10.1.0)\\nFri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Using builder (3.2.2)\\nFri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): 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)\\nFri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice):\\nFri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice):         /usr/bin/ruby1.9.1 extconf.rb\\nFri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice):\\nFri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Gem files will remain installed in /home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.0 for inspection.\\nFri Sep 06 20:26:53 +0000 2013 /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns (notice): Results logged to /home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.0/ext/ffi_c/gem_make.out\\n\\ngem_make.out has only:\\n   /usr/bin/ruby1.9.1 extconf.rb\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=69874'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-7bifphmxtcqgvdofuzla', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410462222, 'spacePHID': None, 'dateCreated': 1378503240, 'dateModified': 1424912158, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53864', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting text into VE from external text processor removes newlines', 'description': {'raw': 'System environment:\\nWin7 X64\\nGoogle Chrome 29.0.1547.62 m\\n\\nSteps to reproduce:\\nOpen a page\\nEdit it in VE\\nCopy-paste the following text:\\na\\nb\\nc\\nd\\ne\\n\\nExpected output:\\na\\nb\\nc\\nd\\ne\\n\\nActual output:\\nabcde\\n\\nThe problem has been tested with notepad++ as the external editor, with line endings in windows format (CRLF), UNIX format (LF) and MAC format (CR). Newline is not copied in any of the cases.\\n\\nThe problem has also been tested by trying to copy-paste html text from chrome itself. Newline is not copied.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52096'}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385505615, 'spacePHID': None, 'dateCreated': 1378418160, 'dateModified': 1417570403, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53828', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Lazy load extensions' large resources in VisualEditor, rather than blocking load\", 'description': {'raw': \"Extensions such as Math or SyntaxHighlight may require the inclusion of large(ish) JS libraries. It would be good if we didn't load these on every VE page load, but rather when these elements are present, or become present (e.g. I add a formula to a new document)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1378414320, 'dateModified': 1643977438, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53826', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"mw.config doesn't expose page existence information about the target of a special page\", 'description': {'raw': 'For special pages, no information about page existence is exposed to mw.config, which means that VisualEditor is forced to assume it exists regardless.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66885'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416369086, 'spacePHID': None, 'dateCreated': 1378324980, 'dateModified': 1416369714, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53774', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <div class=\"ve-ce-protectedNode\"> not always preventing editing in VE', 'description': {'raw': '**Author:** `kwwilliams`\\n\\n**Description:**\\nWhen articles contain items that lead VE to corrupt the article, we\\'ve been protecting them by wrapping the article with <div class=\"ve-ce-protectedNode\"> and </div>. This used to keep VE from being able to select any material within the article, which allowed us to keep the article from being corrupted.\\n\\nVE is now allowing edits to templates inside the article (see https://en.wikipedia.org/w/index.php?title=Teenage_Dream_%28Katy_Perry_album%29&veaction=edit for an example), so we now have no way to protect articles that we know VE cannot handle.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52141'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403741232, 'spacePHID': None, 'dateCreated': 1378317960, 'dateModified': 1461291027, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53767', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Range around an annotated alien calculated incorrectly', 'description': {'raw': \"1. Create '<p>Foo<cite>Bar</cite>Baz</p>'\\n2. Select Bar\\n3. Range is now [4,6] (correct as <cite/> becomes [<alien>,</alien>])\\n4. Bold the selection\\n5. Range is now [6,6] :(\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378399268, 'spacePHID': None, 'dateCreated': 1378317600, 'dateModified': 1417572838, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53766', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Impossible to insert the \"ę\" character when editing in Module: namespace with the code editor', 'description': {'raw': '[Please move this to a different component if applicable, I\\'m not sure where the editor comes from.]\\n\\nIt is impossible to insert the \"ę\" or \"Ę\" characters (latin letter \"e\"/\"E\" with ogonek) from keyboard when editing in Module: namespace with the code editor on the Polish Wikipedia.\\n\\n\"ę\" is inserted on the Polish keyboard using AltGr+e (aka Ctrl+Alt+e). If the editor uses this as a hotkey, it shouldn\\'t (nor should it use any other Ctrl+Alt combinations).\\n\\n(Reported at https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#VisualEditor_a_polskie_diakrytyki)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1702336181, 'spacePHID': None, 'dateCreated': 1378316100, 'dateModified': 1702336181, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53763', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Implement script-specific cursoring for Devanagari if native cursoring is insufficient', 'description': {'raw': '* This is language/script specific diacritic specific bug split from {T53472}\\n\\n* For language Marathi Script Devanagari anuswara diacritic is  ं \\n* If one types the anuswara diacritic  ं  after any devanagari script alphabet it is usually place above the concerned alphabet. For example  क is a Marathi/Devanagari alphabet if I type क+ ं I get  कं  \\n* If I place cursor before the cluster कं and press delete then whole cluster gets deleted and that is right way to happen, and this behaviour needs to be retained (since if basic alphabet is not there then no need of anuswara diacritic  ं) .\\n* Problem: In Visual Editor if I place cursor after the cluster e.g. after कं and press backspace current behaviour is the whole cluster gets deleted. Example कं + Backspace key = results in whole cluster getting deleted.\\n* Expected behaviour is: Cluster with anuswara diacritic (कं) + Backspace key = retain rest of cluster(retain क ) and only anuswara diacritic  ं should get deleted.\\n* Reason: During spell correction many times we need to retain rest of the cluster and only change the diacritics. For anuswara   ं diacritic spell change is required frequently for various reasons like change in singular-plural tense. Every time retyping the whole cluster is cumbersome. Traditional Source editing behaviour is proper and expected and problem is coming only with VisualEditor behaviour.\\n* For example please see this https://mr.wikipedia.org/w/index.php?title=कृष्ण_श्रीनिवास_अर्जुनवाडकर&diff=1198833&oldid=1198826 edit difference a user had to change this diacritic at several places.\\n\\nSince users would be reluctant to use VE without correct behaviour, I would prefer this being treated as a bug not just enhancement and to have  fair importance level.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1449602907, 'spacePHID': None, 'dateCreated': 1378306620, 'dateModified': 1449603913, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53754', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [[MediaWiki:Anoneditwarning]] has an editor-specific link rather than taking you to the appropriate one', 'description': {'raw': 'en.wp user Professor Hog reports:\\n\"If you try and use beta to edit a page, but you\\'ve forgotten to log in, so you log in directly off the beta page, once you have successfully logged in it takes you back to the edit source page instead of the beta page. Minor, but thought you may want to correct it? \"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52281'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mvx4x7ywk2flsaku2dbk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-mvx4x7ywk2flsaku2dbk', 'dateClosed': 1455934739, 'spacePHID': None, 'dateCreated': 1378296540, 'dateModified': 1455934739, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53746', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Inserting some content in a QA script doesn't round-trip (null diff) - failure to inserting CE content into DM somehow?\", 'description': {'raw': \"**Author:** `rachelqa99`\\n\\n**Description:**\\nshows error message\\n\\nI got this message when running a test automation script, that puts in a line of code and tries to save it. It doesn't recognize the new line of code I put in, so it gives this error message upon save. Not sure if you are aware of this particular scenario, which is why I am submitting it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11191}\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1449024014, 'spacePHID': None, 'dateCreated': 1378241340, 'dateModified': 1465905713, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53721', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: jquery.IME doesn't work in VisualEditor's iframes (template, reference, reference list, media, and page settings dialogs, and language, maths, code and link inspectors)\", 'description': {'raw': 'The ULS input methods (jquery.ime) currently do not work with the popup windows of VE. These include the template, reference, reflist, image, link and page settings popups.\\n\\nThe problem has been tested by me on Win7 X64 with Google Chrome 29.0.1547.62 m and possibly by others on other browsers. The problem was originally reported on [1] by mr-wp users.\\n\\n[1]: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#VE_.2B_ULS_unicode_Devnagari_Script_input_issues\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427915110, 'spacePHID': None, 'dateCreated': 1378231800, 'dateModified': 1427915284, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53717', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor cannot move through text created with jquery.IME when editing bulleted text', 'description': {'raw': 'System environment:\\nWin 7 X64\\nGoogle Chrome 29.0.1547.62 m\\n\\nSteps to reproduce:\\nOpen a blank page\\nEdit it in VE\\nEither use google input tools for hindi or enable ULS hindi transliteration\\n\\nInput:\\nSelect bullet formatting from the VE toolbar\\nagar[SPACE]main[SPACE]\\n\\nExpected output:\\nwith ULS: अगर[SPACE]मैन[SPACE]\\nwith Google input tools (depends on translation history, macros etc and may differ user-to-user): अगर[SPACE]मैं[SPACE]\\n\\nActual output:\\nText output is same as expected. However, the text is partially non-navigable, ie pressing the left arrow key from the end of the text takes the caret to the beginning, and then left/right arrow key presses have no effect on the caret. Simultaneously, if the text is navigated by specifically placing the caret at a particular point using the mouse, the value shown for the formatting dropdown in the toolbar may go blank at one point in the text and become paragraph at the next.\\n\\nThe text is also irremovable ie bug 53708\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53708'}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749286, 'spacePHID': None, 'dateCreated': 1378217520, 'dateModified': 1453765554, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53711', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Incorrect and irremovable text placement with IMEs', 'description': {'raw': 'Screenshot of incorrect text placement\\n\\nSystem environment:\\nWin 7 X64\\nGoogle Chrome 29.0.1547.62 m\\n\\nSteps to reproduce:\\nOpen a blank page\\nEdit it in VE\\nEnable ULS IME hindi transliteration\\n\\nInput:\\n[ENTER/RETURN KEY]x2 (two newlines)\\nagar[SPACE]ma\\n\\nExpected output:\\n[NEWLINE]x2 (two newlines)\\nअगर[SPACE]म\\n\\nActual output:\\n[NEWLINE]x2 (two newlines)\\nअग[NEWLINE]र[SPACE]म\\n\\nOnce [ENTER/RETURN KEY]x2 followed by agar[SPACE] has been pressed, Bug 53706 shows up. If one continues the input, this bug is what happens. The incorrect placement is accompanied by the following incorrect bahaviours:\\n\\nThe VE toolbar shows no format (while the editing had been begun with paragraph)\\n\\nCursor movement is incorrect. When the cursor is at the end, pressing up key takes it to the end of the first line, then pressing the down key takes it in the second line after the [SPACE] and before म It is here that the incorrect behaviour occurs. Pressing either the left or the right arrow keys takes it to the end of the line (ie after म) While this should happen on right arrow key press, the left arrow key press should take the cursor(caret) to before the space.\\n\\nAlso, when at the end of the second line, pressing backspace does nothing. Similarly pressing delete anywhere in the second line does nothing. The second line effectively becomes irremovable, while the first line can be removed.\\n\\nNote: Page used for this test is [[:w:hi:सदस्य:Siddhartha Ghai/sandbox]]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53711\\n\\n**Attached**: {F11165}'}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749321, 'spacePHID': None, 'dateCreated': 1378212900, 'dateModified': 1453749527, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53708', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reset title opacity on API call failure', 'description': {'raw': 'System environment:\\nWin 7 X64\\nGoogle Chrome 29.0.1547.62 m\\n\\nSteps to reproduce:\\nOpen a blank page\\nEdit it in VE\\nLet the API call for the parsed json output fail\\nVE asks if you would like to retry, press Cancel\\n\\nExpected behaviour:\\nVE should reset the opacity for the title and sitesub back to 1 from 0.6\\n\\nActual behaviour:\\nOpacity is not changed, leaving it 0.6 although the user is effectively reading the article, not editing it with VE\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402329926, 'spacePHID': None, 'dateCreated': 1378211220, 'dateModified': 1443276362, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53707', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Incorrect text selection with jquery.IME', 'description': {'raw': 'Screenshot of selection error\\n\\nSystem environment:\\nWin 7 X64\\nGoogle Chrome 29.0.1547.62 m\\n\\nSteps to reproduce:\\nOpen a blank page\\nEdit it in VE\\nEnable ULS IME hindi transliteration\\n\\nInput:\\n[RETURN/ENTER KEY]x4 (four newlines)\\nagar[SPACE]\\n\\nExpected output:\\n[NEWLINE]x4 (four newlines)\\nअगर[SPACE]\\n\\nno text selection should be there\\n\\nActual output:\\n[NEWLINE]x4 (four newlines)\\nअगर[SPACE]\\n\\nthe ending [SPACE] is selected with a newline. Also, the toolbar shows that VE has somehow jumped to changing the formatting to bulleted and numbered list from the original paragraph formatting.\\n\\nFurther, pressing a backspace deletes not only the selected space/newline, but also the typed text अगर. I think this is Bug 53705 though I may be wrong.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53700\\n\\n**Attached**: {F11150}'}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749345, 'spacePHID': None, 'dateCreated': 1378210380, 'dateModified': 1453749526, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53706', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Content disappears when using jquery.IME', 'description': {'raw': \"System environment:\\nWin 7 X64\\nGoogle Chrome 29.0.1547.62 m\\n\\nSteps to reproduce:\\nOpen a blank page\\nEdit it in VE\\nEnable ULS IME hindi transliteration\\n\\nInput 1:\\nagar[SPACE][ENTER/RETURN KEY]\\n\\nInput 2:\\nkyaa[SPACE]\\n\\nExpected output 1:\\nअगर[SPACE][NEWLINE]\\n\\nExpected output 2:\\nक्या[SPACE]\\n\\nActual output 1:\\n[NEWLINE]\\n\\nActual output 2:\\n[SPACE]\\n\\nFor the first case, when the given characters are typed, everything is fine upto the pressing of the return key, ie agar[SPACE] gives अगर[SPACE] as expected. However, as soon as the return key is pressed the entire text disappears leaving only a newline.\\n\\nFor the second case, everything is fine till [SPACE] is pressed.\\n\\nIf the page is not blank, extreme weirdness occurs, which can only be explained with further bugs (which I'm about to file). In short though, the disappearances persist, along with other buggy effects.\\n\\nNote: Page used for this test is [[:w:hi:सदस्य:Siddhartha Ghai/sandbox]]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749382, 'spacePHID': None, 'dateCreated': 1378209360, 'dateModified': 1453749522, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53705', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Marathi/Devanagari: After typing first character cursor moves in wrong direction when using jquery.IME', 'description': {'raw': '*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*Problem description =In normal speed typing,after we type first alphaabate cursor moves from right to left direction.Word marathi need to apear मराठी with VE+ULS instead is coming राठीम \\t\\n\\n**additional details = Marathi language devanagari is written in left to right direction.But when we use ULS Method of input = अक्षरांतरण with VE cursor is moving in opposite direction after typing first charecter as if we are typing a right to left script after typing first charecter and then again moves left to right \\n\\n*Screenshot will be added\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49569'}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749409, 'spacePHID': None, 'dateCreated': 1378208100, 'dateModified': 1453749524, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When using jquery.IME, type a word and press space bar = eliminates typed text immediately', 'description': {'raw': '*VisualEditor+ULS Method of input = अक्षरांतरण language=Marathi  Script=Devanagari  (Non-VE source edit environ,ULS Method of input = अक्षरांतरण works normal \\t\\n\\n*Tested Browser and OS =Firefox+Win7\\n\\n*Problem description = No other text on a page> Type a word + space bar = eliminates typed text imidiately\\n\\n**additional details = If some text is already there on the page or we copy paste then we can give the space bar with less frequency of this problem.\\n\\n\\n*Screen shot or Difference of edit if available = Can not create the screen shot/or edit diff\\n\\n\\nThanks and Regards\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49569\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53706'}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749441, 'spacePHID': None, 'dateCreated': 1378207380, 'dateModified': 1486157088, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53700', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Trigger keys can end up in CE surface, but not in DM', 'description': {'raw': 'A user reported a problem to use the \"clear formatting\" shortcut with a french AZERTY keyboard. The shortcut is \"Ctrl + \\\\\", but \"\\\\\" is only accessible as \"AltGr + 8\".\\n\\nFirst, even with, \"Ctrl + AltGr + 8\", the shortcut doesn\\'t work. I was unable to find a keyboard combination that triggers the \"clear formatting\" shortcut. When using a classic QWERTY keyboard, \"Ctrl + \\\\\" works on the same computer/browser.\\nSee https://bugzilla.wikimedia.org/show_bug.cgi?id=51507\\n\\nBut, when testing, I noticed an other problem, with a behaviour depending on OS/browser when using \"Ctrl + AltGr + 8\" with text selected:\\n* On W7 + Chrome 29, the selected text is replaced by \"\\\\\", but VE doesn\\'t see any modification: save is disabled, undo is disabled, ...\\n* On W7 + Firefox 23, the selected text is replaced by \"\\\\\", and VE sees that text has been modified\\n* On Ubuntu 12.04 LTS + Firefox 20, a user report that all page is selected.\\n\\nSame kind of problems happen with \"Ctrl + Alt + 8\", \"Alt + 8\", ... or other digits.\\n\\nhttps://fr.wikipedia.org/w/index.php?title=Wikipédia:ÉditeurVisuel/Avis#Raccourci_clavier_pour_effacer_la_mise_en_forme\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51507'}, 'authorPHID': 'PHID-USER-o34e5i3eq4nstbvcf26w', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1449101621, 'spacePHID': None, 'dateCreated': 1378132560, 'dateModified': 1449105056, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53682', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Table rows with no defined cells rendered as an empty line', 'description': {'raw': 'At https://en.wikipedia.org/w/index.php?title=Flight_endurance_record&oldid=571122193#Free_Balloon.2C_Manned the table begins with an empty row where there would normally be a header:\\n{|class=\"wikitable\"\\n|-\\n|-\\n|content\\n\\nIn view mode this empty line is not shown, but it does appear in VE.\\n\\nTesting at https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=571124234#Tables_with_empty_rows shows that the same thing happens, wherever the blank line is in the table. Oddly though the line is shown at full height when its in last position but ~half height elsewhere.\\n\\nIn itself this isn\\'t a problem, it\\'s just different to what happens in view mode where the second |- is ignored.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404172794, 'spacePHID': None, 'dateCreated': 1378066380, 'dateModified': 1417572129, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53665', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In the transclusion dialog\\'s panel for a parameter, use \"Param#deprecated\" from TemplateData', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398901249, 'spacePHID': None, 'dateCreated': 1377905520, 'dateModified': 1443276362, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53612', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In the transclusion dialog\\'s panel for a parameter, use \"Param#required\" from TemplateData', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389902644, 'spacePHID': None, 'dateCreated': 1377905340, 'dateModified': 1443276365, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53611', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In the transclusion dialog, cursor keys can let you select parameters in the search results off the > screen and the dialog doesn’t scroll', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379435340, 'spacePHID': None, 'dateCreated': 1377905220, 'dateModified': 1417572835, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53610', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog improvements (tracking)', 'description': {'raw': \"[Now tracked as #VisualEditor-MediaWiki-Templates instead.]\\n\\n\\nFork from bug 49833, which wasn't meant to be used this way.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416798469, 'spacePHID': None, 'dateCreated': 1377900000, 'dateModified': 1545563376, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53604', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add a functionality to gray out gadgets on gadgets preference tab that are dependent on other gadgets.', 'description': {'raw': 'Gadget checkboxes should be able to be grayed out (inaccessible) dependent on if another gadget is on or off, if other extensions exist that gadgets are unable to use, or if they require a specific skin to work.  For example, on en.wikipedia the current \"Editing\" section of the gadget tab on the preferences page looks like:\\n \\n[[ https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(current).png | commons:File:Special_Preferences_mw-prefsection-gadgets_(current).png ]]\\n\\nThere should be a way to gray out functions, like:\\n \\n[[ https://commons.wikimedia.org/wiki/File:Special_Preferences_mw-prefsection-gadgets_(proposed).png | commons:File:Special_Preferences_mw-prefsection-gadgets_(proposed).png ]]\\nIf (in this instance) VisualEditor is enabled.'}, 'authorPHID': 'PHID-USER-qgqq35kbi5wss2tlgmhg', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377865740, 'dateModified': 1661603140, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53584', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: histograms are duplicated while editing', 'description': {'raw': 'https://fr.wikipedia.org/w/index.php?title=Polisy&veaction=edit\\nor\\nhttps://fr.wikipedia.org/w/index.php?title=Aix-en-Othe&veaction=edit\\n\\nThe demographic histogram gets duplicated while VEditing, although everything will be fine again once you save, but I see this can confuse users.\\n\\nLooks like it is generated, like other parts of the Démographie section, by https://fr.wikipedia.org/wiki/Mod%C3%A8le:Section_d%C3%A9mographie_d%27article_de_commune_de_France .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1424365332, 'spacePHID': None, 'dateCreated': 1377864060, 'dateModified': 1439679156, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53583', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'IndexPager::buildQueryInfo (LogPager) query needs tuning', 'description': {'raw': \"Have seen multiple instances of this one backing up on commonswiki slaves recently:\\n\\nSELECT /* IndexPager::buildQueryInfo (LogPager) 148.160.132.46 */  log_id,log_type,log_action,log_timestamp,log_user,log_user_text,log_namespace,log_title,log_comment,log_params,log_deleted,user_id,user_name,user_editcount,ts_tags  FROM `logging` FORCE INDEX (times) LEFT JOIN `user` ON ((log_user=user_id)) LEFT JOIN `tag_summary` ON ((ts_log_id=log_id))  WHERE (log_action != 'revision') AND (log_type != 'suppress') AND log_type IN ('delete','move')  AND log_namespace = '0' AND log_title = '0' AND ((log_deleted & 1) = 0)  ORDER BY log_timestamp DESC LIMIT 11\\n\\nIt runs in excess of 10 minutes.\\n\\nEXPLAIN says the FORCE INDEX sends MySQL onto a very slow index scan over `times` (log_timestamp) which is hardly better than a table scan in this case.\\n\\nRemoving the FORCE allows `page_time` index be used which reduces execution time to a few seconds.\\n\\nSuggest either filtering by a range on log_timestamp or removing the FORCE.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54122\"}, 'authorPHID': 'PHID-USER-lxluxbieyr4tgfyp5jru', 'ownerPHID': 'PHID-USER-lxluxbieyr4tgfyp5jru', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396153047, 'spacePHID': None, 'dateCreated': 1377856620, 'dateModified': 1496861859, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53577', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unexpected editing behaviour for Malayalam Text', 'description': {'raw': 'Attachment 1\\n\\nVisual Editor became quite unusable (possibly) after a recent update in Malayalam Wikipedia. There are several selection, editing and linking problems started to appear recently. Two such problems are described here.\\n\\nSee the example below\\n\\n1. Copy the following text and paste it in a test page at Malayalam Wikipedia using conventional editor and save it. \\nഈ ദുരന്തം ഐറിഷ് രാജ്യാതിർത്തി\\n\\n2. Edit the page using VE.\\n\\n3. Change the third word \"ഐറിഷ്\" to \"അയർലൻഡ്\". To do that, select the word \"ഐറിഷ്\" by double clicking on it and type the word അയർലൻഡ്.\\n\\n4. Now I want to create a wikilink for അയർലൻഡ്. For that, I used shift+ctrl+left arrow. Now, instead of selecting the entire word, A PORTION OF THE WORD WAS SELECTED. See the attachment 1. \\n\\n5. Select the entire word അയർലൻഡ് using double clicking on it\\n\\n6. Press ctrl+k. Now instead of popping up a linking suggestion for the word അയർലൻഡ്, THE WORD DISAPPEARED AND LINKING SUGGESTION FOR A PART OF NEXT WORD POPS UP. See the attachment 2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Linux\\n**Platform**: PC\\n\\n**Attached**: {F11751}'}, 'authorPHID': 'PHID-USER-4jecvpv4h62htut6pxez', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379322294, 'spacePHID': None, 'dateCreated': 1377824820, 'dateModified': 1482599632, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53572', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Automatically switch from wikitext to HTML syntax in serializer when attributes were added to elements', 'description': {'raw': 'When editing a document that contains:\\n\\n* Foo\\n* Bar\\n* Baz\\n\\nAdding an attribute to one of the list items in VE doesn\\'t roundtrip (they serialise back to * instead of forcing <ul><li>..</ul>, as it will have to).\\n\\nRight now VisualEditor never does this, but earlier today I was experimenting with this (the language inspector might need to do this to properly flip the directionality of an individual list item, wrapping the inner content is not an option as then the number would be on the wrong side).\\n\\nWhen trying to reproduce this I noticed that it also happens when creating a new document (e.g. there is no existing page, it has no reason to force \"*\" instead of \"<li>\" other than that being the preferred default for wikitext).\\n\\n\\nhttp://parsoid.wmflabs.org/_html/:\\n\\nIn:\\n<div dir=\"ltr\">\\n<ul>\\n<li>a\\n<li lang=\"he\" dir=\"rtl\">b\\n<li>c\\n</ul>\\n</div>\\n\\nOut:\\n<div dir=\"ltr\">\\n\\n* a\\n* b\\n* c\\n\\n</div>\\n\\nThe only case where Parsoid kept the attributes is when not editing a document with wikitext, and not creating a new document, but when editing an existing document with \"<li>\" in wikitext already, it did roundtrip those.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=68800'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377813060, 'dateModified': 1583447083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53568', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar scrolling off the screen on longer articles, possibly due to touch-screen environment', 'description': {'raw': 'MyOnlyEye says, \"When I write long articles in VisualEditor the whole screen scolls - and the VisualEditor toolbar is scrolling upward and out of the screen. If I want to make a headline or instert a picture I\\'ll have to scroll up to the top to reach the toolbar. I\\'ve tried it in the lastest edition of Firefox and Chrome in Win8 - on my own mediawiki with visualeditor and Wikipedia and Mediawiki....On every page that is longer than the screen - e.g. http://en.wikipedia.org/wiki/Electron?veaction=edit\\nI\\'ve tested a bit (after I wrote the feedback) and it seems to be OK on my Win7 and Linux-box (chrome and firefox, both in 64-bit), but it\\'s not working on Win8 (32-bit). Both the lastest 32-bit edition of Chrome and Firefox have the \"scrolling error\" on my Acer W510 Win8-laptop in desktop-mode (and in tile-mode :-)....I tried the electron-article and updated my own wiki (with git pull on mediawiki developer and visualeditor). I tried it in Firefox and Chrome (latest 32-bits editions)....I\\'ve installed a virtualbox with Win8 (32-bit, same as my Acer W510) and ran some wiki-pages with visualeditor in Chrome. No problem with the toolbar. So there seems to be two options left - 1) it\\'s the intel screen driver (Intel HD 9.14.3.1102) or 2) it\\'s how the browsers behave in a touch screen environment. My W510 has touch screen, the virtualbox Win8 hasn\\'t....\\nI\\'ve tested it on another Win8-machine (ASUS VivoBook S400 14\" HD touch) with different hardware than Acer W510 _but_ with a touch screen - and... the toolbox/-bar scrolled out of the screen. So my guess is that this is something that happens when the browser knows that the user can scroll the webpage with the fingers.\"\\n\\nIt is apparently not quite the same as https://bugzilla.wikimedia.org/show_bug.cgi?id=52504\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1519404026, 'spacePHID': None, 'dateCreated': 1377802500, 'dateModified': 1519404026, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53550', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: nowiki tags thrown right after a template', 'description': {'raw': \"I am filing a related common problem we meet at it.wp.\\n\\nWe had troubles with nowikis being thrown right after some templates when the\\nuser did not add an extra space there, but simply edited something in that\\npage. See\\nhttps://it.wikipedia.org/w/index.php?title=Wikipedia&diff=61171396&oldid=61171228\\n.\\n\\nWe actually found a workaround for this:\\nhttps://it.wikipedia.org/w/index.php?title=Template:Quote&curid=224372&diff=61173726&oldid=60749506\\nbut since this addition is apparently a nonsense, users demand that VE prevents\\nthat behaviour instead.\\n\\nThey also think this is related to templates featuring some kind of table.\\n\\nI did some tests as well.\\nI was able to reproduce an unwanted situation where the first line and the\\ntable (which is actually a template) were mingled in a non-editable block\\nhttps://it.wikipedia.org/w/index.php?title=Utente%3AElitre_%28WMF%29%2FSandbox_VE&diff=61181542&oldid=61181524\\n.\\n\\nBut I was also able to avoid nowikis, even if the extra span tags were not\\nadded to the template: as you can see here\\nhttps://it.wikipedia.org/w/index.php?title=Utente:Elitre_(WMF)/Sandbox_VE&diff=prev&oldid=61181473,\\nif the first letter of the line is actually closer to the template's final\\nbrace (with no space between), VEditing that page will result in the text\\ngetting automatically placed in a better position, and no nowikis in sight,\\neven after multiple saves of the page.\\n\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377800880, 'dateModified': 1435425998, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53548', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Added templates in RTL wikis should float in appropriate direction', 'description': {'raw': 'Templates that are inserted to a page in RTL appear first floating on the right side, then only after save and re-edit they appear correctly.\\n\\nReplicate:\\n1. Go to hewiki (or any other rtl wiki)\\n2. Add a template - for instance {{עליות}} which is supposed to be floated left - yet it is inserted floating right.\\n3. Save the page. Edit it again -- the template floats in the correct direction.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701813764, 'spacePHID': None, 'dateCreated': 1377798180, 'dateModified': 1701813764, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53544', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: RTL entries don\\'t receive dir=\"rtl\" in Page settings / Languages', 'description': {'raw': '**Author:** `p.selitskas`\\n\\n**Description:**\\nEntries in Page settings / Languages don\\'t have dir attributes for the link text. It leads to bidi issues for RTL languages.\\n\\nReproducing:\\n1. Go to an article with a langlink to Hebrew, for instance. Here\\'s my favourite: [[en:August 3]].\\n2. Open the VisualEditor.\\n3. Go to Page settings / Languages and scroll down to \\'he\\'.\\n4. Link text reads as \"3 באוגוסט\", but it should read with \"3\" after Hebrew characters (reading left-to-right, of course; in the beginning of the string, if right-to-left).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377895476, 'spacePHID': None, 'dateCreated': 1377728640, 'dateModified': 1417048671, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53503', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue\", 'description': {'raw': 'See numbers 49 and 50 in https://pl.wikipedia.org/w/index.php?title=Biurokracja&oldid=37367869 and https://pl.wikipedia.org/w/index.php?title=Biurokracja&oldid=37367869&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51289\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52300'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377823295, 'spacePHID': None, 'dateCreated': 1377708300, 'dateModified': 1434414601, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53486', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion editor should not allow parameters with unmet dependencies', 'description': {'raw': \"The transclusion editor should not allow (or at least should warn about) template parameters with unmet dependencies.\\n\\nFor example in [[template:For]] parameter 4 has no effect unless parameter 3 is also specified, so the transclusion editor should not allow/warn about template 4 without an accompanying parameter 3. (parameter 3 is otherwise optional and can be present without parameter 4).\\n\\nIn at least some cite templates, parameter author2 requires the existence of author1, etc. \\n\\nI'm fairly sure that this functionality depends on bug 50407, which requests that TemplateData allows dependency relationships like this to be defined.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377690300, 'dateModified': 1643977439, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53469', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Where VisualEditor is the primary editor, redlinks in read mode should open VE (not wikitext editor)', 'description': {'raw': 'Redlinks right now always take you into wikitext editor, regardless of what editor is primary on your wiki.\\n\\n--------------------------\\n**See Also**:\\n{T54162}\\n{T54281}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1455641745, 'spacePHID': None, 'dateCreated': 1377650040, 'dateModified': 1660398889, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53441', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing a modifier key (Ctrl/Alt/Shift/Cmd/etc.) when cursor is offscreen or under the toolbar causes the page to scroll up', 'description': {'raw': '**Author:** `p.selitskas`\\n\\n**Description:**\\nReproducing:\\n1. Open the VisualEditor\\n2. Put the cursor in a place where \"Paragraph\" (or whatever else) disappears. (For example, into the ugly and unbearable empty line in pages with infobox at the very beginning.) The content editor must be kept active and cursor blinking.\\n3. Scroll it down a bit.\\n4. Press Ctrl, Alt, or Shift, or every possible combination of these\\n5. See the content editor scroll up step by step (or as many steps per time as many keys are in combination.\\n\\nI can reproduce this in Chrome 29.0.1547.57 and Firefox 23.0.1 on Windows.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437759675, 'spacePHID': None, 'dateCreated': 1377634200, 'dateModified': 1438734480, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53420', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar icons - \"Transclusion\" (puzzle piece) alternatives or improvements', 'description': {'raw': 'en.wp user Risker reports from an editathon that of the participants:\\n\"not a one of them understood what the \"puzzle piece\" was supposed to represent, and when shown, all of them still thought it was a poorly chosen icon.  Most had no suggestion as to an alternative, although two thought \"curly brackets\" would be a good idea.  I suspect that\\'s because they\\'d seen curly brackets for templates when using wikitext.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51372'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377598380, 'dateModified': 1643977439, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53396', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Broken wikitext inside a table leads to it and the table header being duplicated', 'description': {'raw': \"This is probably an occurrence of an existing bug, but I couldn't find one that really fitted.\\n\\nIn these edits, the table header was duplicated several times:\\n\\nhttps://fr.wikipedia.org/w/index.php?title=CM_Punk&diff=95906046&oldid=95898800\\nhttps://fr.wikipedia.org/w/index.php?title=CM_Punk&diff=95848040&oldid=95838194\\nhttps://fr.wikipedia.org/w/index.php?title=CM_Punk&diff=95778036&oldid=95766921\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1418097332, 'spacePHID': None, 'dateCreated': 1377596700, 'dateModified': 1469823941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53394', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow multiple commands (\"keyboard shortcuts\") per tool on the same platform', 'description': {'raw': \"Right now the CommandRegistry only takes a single command that can be used as a keybinding for a tool on a given platform (i.e. Mac, PC, etc.); it's thus not possible to have two keyboard shortcuts for the same tool, such as Undo (where both Ctrl+Y and Ctrl+Shift+Z are commonly used).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394076375, 'spacePHID': None, 'dateCreated': 1377533460, 'dateModified': 1443276365, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53356', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When text is being made superscripted and is already subscripted, clear the latter (and vice versa)', 'description': {'raw': 'VE allows to mark text as both superscripted and subscripted (<sup><sub>text</sub></sup> or the other way). That sounds like a bad idea; such text simply ends up being displayed in smaller font.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404341917, 'spacePHID': None, 'dateCreated': 1377465840, 'dateModified': 1443276366, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53330', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"ULS support needed in VisualEditor's dialog boxes\", 'description': {'raw': 'We need ULS support in dialog boxes-\\n\\n1) Template dialog boxes - adding existing template for setting paratmeters\\n2) Image dialog box\\n3) Adding or editing references\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-qpuuryo2o37amdlkb5gk', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1454774965, 'spacePHID': None, 'dateCreated': 1377447360, 'dateModified': 1454774965, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53324', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't return to save dialog after reviewing null edit\", 'description': {'raw': 'reported on en.wp by Atethnekos:\\n\\n\"So I put a space and then a backspace. Go to save, review changes to check and make sure it is a null edit, then it goes to this \"processing\" dialogue but then it shows \"Could not start the review because your revision matches the latest version of this page.\" So then I press the little back link on the dialogue, but it just goes back to the processing dialogue. If the page is small, the processing is really quick, so before I can even press back again, it goes back to the \"Could not start\" warning message. Even if I do manage to press the back a second time quickly, it will only stay at the save dialogue for a split second and then again bring me to the warning message, although then pressing back does take me to the save dialogue securely. FF 23.0.1 Win7\"\\n\\nI\\'ve confirmed this in Firefox 23.0 on Linux.\\nThe issue is with the < link only. Clicking the ^ does return you to the editing screen as expected.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381187081, 'spacePHID': None, 'dateCreated': 1377426420, 'dateModified': 1417572825, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53313', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When reversing a transaction, create a new transaction rather than reusing the old one', 'description': {'raw': \"Rather than passing around boolean parameters called 'reversed' all over the place, we should use each transaction only once, and implement a function that creates a new transaction that's the reverse of an existing transaction.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394478857, 'spacePHID': None, 'dateCreated': 1377192420, 'dateModified': 1417572579, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53225', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Undo/redo doesn't go through dm.Surface.change() code path\", 'description': {'raw': 'dm.Surface.undo() and .redo() just call documentModel.rollback() / .commit() directly, without going through all the other stuff in .change() . Presumably this other stuff is useful, so we should figure out if bypassing it causes bugs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382735392, 'spacePHID': None, 'dateCreated': 1377191640, 'dateModified': 1417572819, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53224', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: When editing a section, don't wait for loading to be complete before scrolling to the section\", 'description': {'raw': \"When loading VisualEditor from a section edit link, the editor opens at that position on the page. However, as the TOC is not displayed in edit mode (bug 49224) the content is effectively rendered higher up so a later section in the article moves into the view (from a users point of view this is perceived as scrolling to a random point). \\n\\nThe view point does move to the new location of the desired section as the final step of loading, but only if the user has not scrolled at any point while waiting. \\n\\nIf they have attempted to find the section themselves while VE is loading then either (a) the view point subsequently doesn't move when loading completes, or (b) moves by the amount it would have done if the user had not scrolled (meaning it now points at a different point to desired). I have not worked out how to specifically induce one behaviour or indeed what causes either.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T51224}\\n{T52206}\\n{T54577}\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'dateClosed': 1425509611, 'spacePHID': None, 'dateCreated': 1377187440, 'dateModified': 1425524010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53217', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Feedback dialogs not scrolled to when editing section on long page', 'description': {'raw': \"I clicked to edit a section of a long article, and when I tried to file a bug, it looked like the screen just went dark - I couldn't immediately see a dialog box. It turned out to be because the feedback dialog was overlayed above the section I was editing, which was way, way down the page, and the browser didn't scroll to that part of the page when I pressed the button.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-bug3zrlooz3bdmi4fyl7', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1590842330, 'spacePHID': None, 'dateCreated': 1377115140, 'dateModified': 1590842330, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53173', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Annotating an inline alien breaks node protection', 'description': {'raw': \"1. Create a document with:\\n   Foo <cite>Alien</cite> Bar\\n2. Select all and bold\\n\\nResults\\n3. 'Alien' is bolded, despite being protected (questionable)\\n4. The shield has disappeared.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1579117639, 'spacePHID': None, 'dateCreated': 1377085200, 'dateModified': 1579117640, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53149', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Move MW-specific code out of the VE-core model registry', 'description': {'raw': 'Both ve.dm.ModelRegistry.js and its test file have references to  /^mw:/ . Any code relating to mw should be in modules/ve-mw/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393874721, 'spacePHID': None, 'dateCreated': 1377084540, 'dateModified': 1443276368, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53148', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Clean up single vs. multi-part data-mw', 'description': {'raw': 'We currently use { target: {}, params: {} } for single-transclusion content, and {parts: [{template:{target: {}, params: {}, i: 0}}]} for multi-part transclusions and extensions. This creates special cases and makes it necessary to know all keys to convert the single-transclusion format into the parts bit.\\n\\nThe missing namespacing also makes it harder than necessary to add additional information to data-mw.\\n\\nTo clean this up, we should consider moving to always using an array format like this:\\n\\nparts: [{\"@type\":\"mw:Transclusion\", target: {}, params: {}}]\\n\\nThe change to always use an array is already supported by VisualEditor. Flattening the nested object and using a JSON-LDish @type key makes the parts structure more regular and easier to extend. It also moves it closer to the RDFa names. Both us and VE can support both formats as an input for a while to avoid caching issues, but should start by only emitting the new format.\\n\\nSee also:\\nhttp://json-ld.org/playground/index.html -- some example JSON-LD\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377042960, 'dateModified': 1537463801, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53135', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: be & be-tarask locales need a different i18n Bold toolbar icon', 'description': {'raw': '**Author:** `p.selitskas`\\n\\n**Description:**\\nPlease create an icon with bold cyrillic \"Т\" for [be] and [be-tarask].\\n\\nIn Belarusian locales ([be] and [be-tarask]), the Bold icon is now read as \"Тл\" which may be interpreted as \"Тлусты\" (fat), but in fact it makes the selected text not fat, but bold (\"Тоўсты\"). :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379364856, 'spacePHID': None, 'dateCreated': 1377007260, 'dateModified': 1417572836, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53094', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'For very large pages on slow connections (when a timeout happens?), users get an \"Error: Unknown error\" on saving changes in VisualEditor (but change is indeed saved)', 'description': {'raw': 'It first happened to the user who was trying to add a wikilink to a large page,  https://en.wikipedia.org/wiki/List_of_Criterion_Collection_DVD_and_Blu-ray_releases; he got the error while in VE so he made that edit with the classic editor later.\\nHe then copied the contents of the page to a sandbox - https://en.wikipedia.org/wiki/User:Marc_Kupper/sandbox2 -  for further testing and these are his findings:\\n\\n<< It took 74 seconds to load the page in VE, I made the change, save-page, give a reason (wikilink - testing VE), save-page again. After 1:45 (105 seconds) I got \"Error: Unknown error\" in the lower part of VE\\'s edit-summary box. The save-page button is grayed out.\\nI don\\'t think the actual edit I did matters. If someone wants to reproduce using my sandbox then the edit was in the last paragraph of the lead. Where it says \"...Essential Art House, Eclipse, and Merchant Ivory Collection...\" I changed \"Eclipse\" to [[Eclipse (DVD)|Eclipse]] by double-clicking on Eclipse to select, control-K to bring up the insert/edit link box, appending \" (d\" to the link-to value, click \"Eclipse (DVD)\" in the list of offerings, and then press <enter> a couple of times to close out the box. I suspect you can make any change you want. --Marc Kupper|talk 22:06, 19 August 2013 (UTC)\\n\\n\\nAfter documenting how I did the edit I tried the save again and again got the error. It happened 1:44 (104 seconds) after clicking save. I suspect the 105 seconds above is simply because I was a bit slow reacting as this time I was waiting for the error right around the 1:45 mark. --Marc Kupper|talk 22:06, 19 August 2013 (UTC)\\nI then did the following tests\\nI replaced all non-alphabetic characters with the letter \"x\" and can edit the page with VE. It appears the issue is with something in the page content, possibly combined with the page size.\\nI removed all \\'ref\\' tags. Saving from VE still fails after 1:44\\nI removed most of the templates transcluded on the page. Saving with VE worked and took 1:17. However, I had intended to just add \"xxx\" in the middle of a word. VE also stripped a table in another part of the article of wikitext. (https://en.wikipedia.org/w/index.php?title=User%3AMarc_Kupper%2Fsandbox2&diff=569295763&oldid=569295507 ) --Marc Kupper|talk 23:16, 19 August 2013 (UTC)\\n\\nI don\\'t have time to debug this further at present - particularly as we now have two VE issues. The next step is to revert back to 22:48, 19 August 2013 and to then see if I can narrow it down from there. --Marc Kupper|talk 23:11, 19 August 2013 (UTC) >>\\n\\nI tested on the first version of the sandbox as well, it took me almost 75 secs as well to load the page, I wikilinked a word and then hit Save - it took me 2min 15sec to get the error message while actually the edit was saved.  Thanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70726\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51636'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377006180, 'dateModified': 1687886083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53093', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Globally-blocked logged-out users are not blocked from using VE (just from saving); should instead show the relevant global block message', 'description': {'raw': 'Screenshot\\n\\nBlocked IP addresses can see the VisualEditor, use it, and are presented with the error in the screenshot when saving.\\n\\nReporting distinctly from bug 52004 because the error message and use case are both somewhat different.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52004\\n\\n**Attached**: {F11450}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398210636, 'spacePHID': None, 'dateCreated': 1376861280, 'dateModified': 1444199736, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53009', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking \"Review changes\" collapses save dropdown, and disappears the thermometer', 'description': {'raw': 'The thermometer is important, as it explains why a radically modified document would give me an empty \"review changes\" box.\\n\\nSeparate bugs: the thermometer never stops spinning, and my changes for review never appear--maybe Parsoid is gagging.  And, is that UI javascript running without a setTimeout?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392062928, 'spacePHID': None, 'dateCreated': 1376813460, 'dateModified': 1417572662, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52982', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Creation of tl-informal as a new interface language', 'description': {'raw': '**Author:** `jamesjoshualim`\\n\\n**Description:**\\nHi, everyone.  Yesterday, we had a meetup here in Manila, and I discussed with two Tagalog Wikipedia editors (including a fellow bureaucrat) about the creation of a new interface language for Tagalog in a bid to resolve long-standing differences over how the interface should be translated.  We agreed on a compromise solution, where we would accommodate Taglish (code-switched Tagalog and English) as a new interface language called \"Tagalog (informal)\" for the Tagalog-language projects, similar to how there is an interface language for formal German (de-formal).\\n\\nWe decided that this new interface language will become the default interface language for all anonymous and new users on the Tagalog Wikipedia, in order to attract new editors who may be confused by the formal language used for the current Tagalog interface.  The current interface will be opt-in for those who want to use the interface as it currently is, and users will have the ability to select their preferred language using the Universal Language Selector which will only have Tagalog, Tagalog (informal) and English as the options.  All other languages may still be selected through the preferences.\\n\\nIf this is possible to do, I\\'d love to see this come to fruition, and I hope to hear from all of you soon.  Thanks! :)\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'stalled', 'name': 'Stalled', 'color': 'yellow'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1376723820, 'dateModified': 1643977439, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52957', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'GettingStarted toolbar overlaps with VE post edit confirmation', 'description': {'raw': '**Author:** `swalling`\\n\\n**Description:**\\nHidden VE postedit confirmation\\n\\nIf you edit successfully via wikitext, we delay loading the GettingStarted toolbar until after the post-edit confirmation disappears. We should do the same for the new style of postedit confirmation from VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11351}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-w3pd7vqenmta6vpmhwcn', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392361469, 'spacePHID': None, 'dateCreated': 1376715240, 'dateModified': 1392361469, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52955', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Refactor sanitizer to work on the DOM too', 'description': {'raw': 'Currently we always serialize to wikitext and re-parse that to HTML, which runs the sanitizer on the token stream to ensure that our final HTML does not cause bad things to happen.\\n\\nSoon both us and the Flow team want to store HTML from the VisualEditor directly without first serializing to wikitext. This means that we need to perform the sanitization on the HTML instead of the token stream. For performance, sanitizing on the way in would be preferable. We should however support re-sanitization when new issues were discovered. This could potentially be coupled with the versioning discussed in bug 52937. A new sanitizer could bump the version number, and the upgrade path would then run the new sanitizer on old HTML (and probably update the storage with the newly sanitized version).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1376677680, 'dateModified': 1589409907, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52941', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Switch to use MediaWiki's built-in messages for post-edit notifications (and add to them so we cover all three cases)\", 'description': {'raw': '**Author:** `swalling`\\n\\n**Description:**\\nScreenshot at 1024x768\\n\\nVery happy to see that VE is now using the same post-edit styling as wikitext! This is a big win for usability, since it is fixed position and so on.\\n\\nI did find one suboptimal fact though... Since the text of the message includes the page title, it is very variable width, depending on the page title length and the browser width. \\n\\nOne of the UX goals for this notification is to have new users notice it, but for it to eventually fade out of your attention as you become used to it. Since the page title produces very different widths as you edit different pages, this calls a lot more attention to the notification even if you\\'ve edit thousands of times. \\n\\nMy recommendation would be to match what\\'s in the wikitext version, \"Your edit was saved.\" since we A/B tested it and we know it meets the goals I mentioned above. Another good solution is simply removing the page title, so that the VE version says, \"Your changes have been saved.\" That seems functionally the same, though I think using edit is good for consistency with the tab names etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11185}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398987428, 'spacePHID': None, 'dateCreated': 1376526420, 'dateModified': 1443278228, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52871', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <references /> empty in edit mode', 'description': {'raw': 'The <references /> section is empty in edit mode, see URL.\\n\\nOther examples:\\n\\nhttps://de.wikipedia.org/wiki/Joachim_Wiesner\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://de.wikipedia.org/wiki/Bahnhof_K%C3%B6ln_Eifeltor'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378992675, 'spacePHID': None, 'dateCreated': 1376480280, 'dateModified': 1380558146, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52841', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Handle \"Search\" --> \"Advanced options\" section of Special:Preferences on Special:Search itself', 'description': {'raw': 'https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-searchoptions\\n\\nThe \"Advanced options\" section of the \"Search\" tab in MediaWiki currently looks like this:\\n\\n---\\nAdvanced options\\n\\n[ ] Search in all namespaces\\n\\nSearch in these namespaces by default:\\n[ ] (Main)\\n[ ] Talk\\n[ ] User\\n[ ] User talk\\n[ ] Project\\n[ ] Project talk\\n[ ] File\\n[ ] File talk\\n[ ] MediaWiki\\n[ ] MediaWiki talk\\n[ ] Template\\n[ ] Template talk\\n[ ] Help\\n[ ] Help talk\\n[ ] Category\\n[ ] Category talk\\n[ ] Thread\\n[ ] Thread talk\\n[ ] Summary\\n[ ] Summary talk\\n[ ] Manual\\n[ ] Manual talk\\n[ ] Extension\\n[ ] Extension talk\\n[ ] API\\n[ ] API talk\\n[ ] Skin\\n[ ] Skin talk\\n[ ] Module\\n[ ] Module talk\\n[ ] Translations\\n[ ] Translations talk\\n[ ] VisualEditor\\n[ ] VisualEditor talk\\n---\\n\\nThis list looks silly and excessive. While {T39878} has requested a layout change, I think we need to reconsider how this list is implemented.\\n\\nWhat about adding a checkbox to [[Special:Search]]\\'s advanced search section that looks something like this:\\n\\n[ ] Use these namespaces as my default\\n\\nThis would de-duplicate the namespace listing (between Special:Preferences and Special:Search) and would allow the search user preference to be set more easily from the search interface itself.\\n\\nRather than using Special:Preferences and having heavy user interface exposure, any custom search namespace preferences could be \"hidden\" user preferences. That is, they\\'ll still be stored if they don\\'t match the site-wide default, but they\\'ll not clutter up Special:Preferences.\\n\\n--------------------------\\n**See Also**:\\n{T50615}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402249236, 'spacePHID': None, 'dateCreated': 1376420940, 'dateModified': 1645152073, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52817', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Remove \"Enable section editing via [edit] links\" user preference from MediaWiki core', 'description': {'raw': 'The \"Enable section editing via [edit] links\" user preference should be removed from MediaWiki core.\\n\\nUsers interested in hiding section-edit links can use per-user (or site-wide) CSS.\\n\\nThis should be an easy bug to resolve; marking it with the Bugzilla keyword\\naccordingly.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-b3xlpjqyzhcppjoumu63', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391604424, 'spacePHID': None, 'dateCreated': 1376416020, 'dateModified': 1520289019, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52811', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Support Parsoid HTML+RDFa storage alongside or instead of wikitext', 'description': {'raw': \"A user asks if VE shouldn't now get rid of apostrophes used for formatting and use common tags instead <b>, <i>...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380661120, 'spacePHID': None, 'dateCreated': 1376398800, 'dateModified': 1434175551, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52796', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Warn if editing a reference that is used multiple times', 'description': {'raw': '<< When editing a reference, there is no indication at all if it is used multiple times throughout the article. This makes it very easy to screw up references, e.g. when you replace a ref for one sentence by changing it and it gets propagated throughout the article. WS (talk) 11:45, 13 August 2013 (UTC) >>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414517796, 'spacePHID': None, 'dateCreated': 1376394960, 'dateModified': 1417571676, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52792', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: cutting block level elements changes the type of following element', 'description': {'raw': '\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52771'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1703086644, 'spacePHID': None, 'dateCreated': 1376340600, 'dateModified': 1703086644, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52770', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: In the transclusion dialog, use TemplateData to hint the parameter's default value, if set\", 'description': {'raw': '**Author:** `l736ewiki`\\n\\n**Description:**\\nThe data model for TemplateData allows the tag \"default\" to assign the default value for parameters which foresee it.\\n\\nHowever, when adding a template to an article via VisualEditor, the default value is not presented inside the corresponding input field, which appears empty, nor there are automatic hints about the default value (unless who generated the TemplateData object inserted it into the textual \"description\" item).\\n\\nI would have expected that:\\n* either the user is presented with the input field already pre-filled with the default value as specified inside the TemplateData description - this would improve usability\\n* or, if this pre-population of the input field is too complex/costly to achieve, at least the information about the \"default\" value is taken and highlighted using the corresponding \"default\" attribute from the parameter description.\\n\\nYou can test this on it.wiki, by trying editing a new article using VE and adding the template named \"Azienda\", whose \"logo_dimensioni\" parameter has been defined in JSON with \"default\":\"200\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394072873, 'spacePHID': None, 'dateCreated': 1376324640, 'dateModified': 1443276372, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52753', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Show a message explaining how to edit references when user selects a references list', 'description': {'raw': \"Reports such as https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=568123469#I_can.27t_edit_the_references suggest that the references list being present but not editable is causing confusion for editors.\\n\\nIt would therefore be helpful for VE to display a message (popup? tooltip?) whne the reference list is selected that explains how to edit references. The text of this message should be set on a MediaWiki namespace page.\\n\\nI don't have a suggested default wording at present.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52750\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1724164016, 'spacePHID': None, 'dateCreated': 1376257440, 'dateModified': 1724164016, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52736', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Typing problem in Assamese', 'description': {'raw': \"**Author:** `gitartha.bordoloi`\\n\\n**Description:**\\nHello,\\nVisual editor was deployed as an opt-in editing tool in Assamese wikipedia about 2 months ago. However it seems the tool doesn't support Assamese script well. While writing with some tools reproduces only vowels or consonants, the in-built keyboards do not work at all. Kindly look into this matter urgently before it is released as default editing tool. The discussions can be found here: http://as.wikipedia.org/wiki/%E0%A7%B1%E0%A6%BF%E0%A6%95%E0%A6%BF%E0%A6%AA%E0%A6%BF%E0%A6%A1%E0%A6%BF%E0%A6%AF%E0%A6%BC%E0%A6%BE_%E0%A6%AC%E0%A6%BE%E0%A7%B0%E0%A7%8D%E0%A6%A4%E0%A6%BE:%E0%A6%AD%E0%A6%BF%E0%A6%9C%E0%A7%81%E0%A7%B1%E0%A7%87%E0%A6%B2_%E0%A6%8F%E0%A6%A1%E0%A6%BF%E0%A6%9F%E0%A7%B0\\n\\nThank you.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1644959034, 'spacePHID': None, 'dateCreated': 1376210460, 'dateModified': 1644959034, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52726', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Review and deploy MassMessage extension to Wikimedia wikis', 'description': {'raw': 'MassMessage is an extension that allows a user to send a message to a list of pages through a special page and the job queue. It is intended to replace [[m:Global message delivery]].\\n\\nMore details are available at [[mw:Extension:MassMessage]], and there is a test instance at http://legoktm.instance-proxy.wmflabs.org/wiki/Main_Page\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**URL**: https://www.mediawiki.org/wiki/Extension:MassMessage'}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384889083, 'spacePHID': None, 'dateCreated': 1376204700, 'dateModified': 1503741172, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52723', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor on se.wikimedia.org', 'description': {'raw': 'The Swedish chapter would like to get the VisualEditor enabled on their wiki at se.wikimedia.org. \\n\\nPoll here: http://se.wikimedia.org/wiki/Tråd:Wikimedia:Bybrunnen/VisualEditor_och_Notifications\\n\\n/Jan\\nCEO\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386022170, 'spacePHID': None, 'dateCreated': 1376178900, 'dateModified': 1397521192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52713', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: In Firefox's High Contrast mode, buttons on the toolbar are unidentifiable\", 'description': {'raw': 'en.wp user Cryptic C62 reports that using Firefox with Windows Vista \"high contrast\" mode renders VE entirely unusable:\\n\\n\"Using Windows Vista, press Shift + Alt + Print Screen to activate \"high contrast\" mode. Open VE in Firefox. Weep uncontrollably (see screenshot).\"\\n\\nScreenshot: [[File:VE High Contrast.jpg]]\\n\\n\\nIt is worth noting that, when using the high contrast extension for Chrome, the interface is fully visible in every setting. Hooray!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-caadsxn4xg5gmxrpn6kz', 'dateClosed': 1459916766, 'spacePHID': None, 'dateCreated': 1376068440, 'dateModified': 1517844777, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52675', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Welcome dialog doesn't expand/scroll to fit large fonts\", 'description': {'raw': \"When a user has a larger font size than defualt, or a non-default font then the welcome dialog (the one controlled by the ve-beta-welcome-dialog cookie) doesn't expand or scroll to accommodate the extended length of the message and the text is cropped.\\n\\nScreenshot at [[File:WARNINGforVE.png]]\\n\\nThis might be another example of bug 52602 but I'm not certain.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52602\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51755\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50885\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378335744, 'spacePHID': None, 'dateCreated': 1376041620, 'dateModified': 1417572839, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52667', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Template {{-}} can be moved into following heading because it doesn't render\", 'description': {'raw': 'en.wp user Redrose64 reports:\\nWith this edit: https://en.wikipedia.org/w/index.php?title=Paisley_Gilmour_Street_railway_station&diff=prev&oldid=567709873 \"the {{-}} was moved from the bottom of a section into a heading, effectively yielding the HTML <h3><span class=\"mw-headline\" id=\"2013\">2013<br style=\"clear:both;\" /></span>[edit]</h3> \"\\n\\nI can reproduce that on that article by:\\n1. Deleting with backspace the header \"Post-2008\" (and nothing else)\\n2. Typing \"2013\"\\n\\nI can\\'t reproduce it in my sandbox with {{-}} (or {{clear}}) before a header and then changing the header.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376609977, 'spacePHID': None, 'dateCreated': 1375989720, 'dateModified': 1417572945, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52658', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Thai Wikipedia's coordinates template displays badly in tables\", 'description': {'raw': 'During the edit\\n\\nThis has been noted on the Thai wikipedia.  \\nSee screenshots for how it looks.  \\n\\nBasically, in edit mode, the sixth column of this table, containing Goehack coordinate links, displays as an HTML string in edit mode. Not only very messy, but it pushes the following columns off the page.\\n\\nAppears to save normally.\\n\\nReplicated on current FF, Chrome, on Mac OS and Ubuntu\\n\\nPage on Thai.wiki: https://th.wikipedia.org/wiki/%E0%B8%A3%E0%B8%B2%E0%B8%A2%E0%B8%8A%E0%B8%B7%E0%B9%88%E0%B8%AD%E0%B9%82%E0%B8%9A%E0%B8%A3%E0%B8%B2%E0%B8%93%E0%B8%AA%E0%B8%96%E0%B8%B2%E0%B8%99%E0%B9%83%E0%B8%99%E0%B8%81%E0%B8%A3%E0%B8%B8%E0%B8%87%E0%B9%80%E0%B8%97%E0%B8%9E%E0%B8%A1%E0%B8%AB%E0%B8%B2%E0%B8%99%E0%B8%84%E0%B8%A3_(%E0%B9%80%E0%B8%82%E0%B8%95%E0%B8%9E%E0%B8%A3%E0%B8%B0%E0%B8%99%E0%B8%84%E0%B8%A3_%E0%B8%9B%E0%B9%89%E0%B8%AD%E0%B8%A1%E0%B8%9B%E0%B8%A3%E0%B8%B2%E0%B8%9A%E0%B8%A8%E0%B8%B1%E0%B8%95%E0%B8%A3%E0%B8%B9%E0%B8%9E%E0%B9%88%E0%B8%B2%E0%B8%A2_%E0%B9%81%E0%B8%A5%E0%B8%B0%E0%B8%AA%E0%B8%B1%E0%B8%A1%E0%B8%9E%E0%B8%B1%E0%B8%99%E0%B8%98%E0%B8%A7%E0%B8%87%E0%B8%A8%E0%B9%8C)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11613}'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414165021, 'spacePHID': None, 'dateCreated': 1375975140, 'dateModified': 1666438772, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52653', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog should validate template parameter values using TemplateData information', 'description': {'raw': 'If a parameter has \\'\"type\": \"number\"\\', VisualEditor should not allow the user to insert other kind of values. Alternativelly, it could just warn the user but still allow a value of the wrong type to be inserted.\\n\\nThis should not be restricted just to the \"number\" type. Other types would also benefity from some validation (e.g., if at some point we have a type \"string/image-name\", VE should check if the user provided the name of an existing image).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52652'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375969680, 'dateModified': 1643977440, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52651', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When getting TemplateData, VE automatically adds \"Template:\" even if another namespace is provided', 'description': {'raw': 'If you want to add a \"template\" that is not in the template namespace, for example: \"User:UBX\"; VE will make an API request like: \"GET https://en.wikipedia.org/w/api.php?format=json&action=templatedata&titles=Template%3AUser%3AUBX\".\\n\\nIt should automatically detect that \"User:\" is a valid namespace, and not add the \"Template:\" prefix.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404157232, 'spacePHID': None, 'dateCreated': 1375875780, 'dateModified': 1443278231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52609', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Get rid of IVStore check in toDomElements in GCNode subclasses', 'description': {'raw': \"Some toDomElements functions reach into the store, but they shouldn't and the check is redundant.\\n\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375853340, 'dateModified': 1531524566, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52599', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add keyboard shortcut for code element/style', 'description': {'raw': \"A keyboard shortcut for code would be helpful, particularly for MediaWiki.org.  We'll need to think of what to use.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410825475, 'spacePHID': None, 'dateCreated': 1375852380, 'dateModified': 1443278231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52597', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Allow hinting to specify auto-numbered parameter names in some fashion', 'description': {'raw': \"Some templates use numbered arguments (see for example http://en.wikipedia.org/wiki/Module:Citation/CS1/Whitelist in the numbered_arguments list). For example, you can use author1, author2, ... (no limit).\\n\\nCurrently, there's no way to define such parameters in TemplateData, and the VE interface is not also optimal for them.\\n\\nWould it be possible to handle numbered arguments in TemplateData: a parameter named author# would define a numbered parameter named author with a numerical suffix. It should be possible to define lower bound (1 by default) and upper bound (no limit by default).\\n\\nThen VE should handle them accordingly: only propose the first parameter available in the list of parameters than can be added.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\n{T53740}\"}, 'authorPHID': 'PHID-USER-o34e5i3eq4nstbvcf26w', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375805280, 'dateModified': 1727290501, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52582', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Scroll to the user's position when VE is invoked via shortcut (Ctrl+Alt+V)\", 'description': {'raw': \"I don't know if this is possible, or if it's been requested elsewhese, but a few users on the French-language Wikipedia have suggested that, when the user has scrolled through the page and invoked VisualEditor via the keyboard shortcut, VE should automatically scroll to that same position on the page when it opens (similarly to what the section edit link does).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53217\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375799880, 'dateModified': 1663959026, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52577', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Repetition of the parameter (\"box\") icon in the transclusion dialog is a bit heavy', 'description': {'raw': '<< Icons can be useful to help a user navigate an interface, however in the transclusion dialog, the same box-shaped icon with the thick left border is shown so many times (when editing a template with more than a few parameters) that it is obnoxious. Almost every occurrence should be removed, keeping it displayed at at most one or two places.--[[User:Wouterstomp|WS]] ([[User talk:Wouterstomp|talk]]) 11:22, 6 August 2013 (UTC) >>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49833'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394072888, 'spacePHID': None, 'dateCreated': 1375794000, 'dateModified': 1443276372, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52576', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Gadgets: Add support to understand whether a gadget supports VisualEditor (or another feature?) and allow it to be greyed out', 'description': {'raw': '[15:52] <T13> VE Question.  How is VE currently set up to handle users that have opted-in to gadgets that modify the editing window such as wikEd?\\n...\\n[15:54] <T13> Do those gadgets still load even though the hooks they use don\\'t exist? Shouldn\\'t having VE enabled disable those gadgets and grey out the optiobs for them in the gadgets tab of preferences?\\n[15:56] <T13> I\\'m guessing some of the \"VE\" bugs are caused by these gadgets trying to do what they no longer can.\\n...\\n[16:06] <mooeypoo> T13: I think most of the edit-related gadgets work on the action=edit condition, and ve goes with action=vedit\\n[16:07] <mooeypoo> but I am not sure :) you\\'ll be safer getting the answer from the VE team\\n[16:09] <MatmaRex> T13: i\\'m not on the team, but i\\'m pretty sure that\\'s the reason\\n[16:10] <MatmaRex> T13: basically there are two ways to detect if we\\'re inedit mode - either look if \\'action\\' is \\'edit\\' or \\'submit\\', or look for some elements that are parts of theedit form, like #wpTextbox1 (the main textbox)\\n[16:10] <MatmaRex> VE avoids them both\\n[16:11] <T13> I\\'ve seen questions on WP:THQ with a link to a screenshot of wikEd and the user thinking they were using VE.  So, I was curious how it was handled.\\n[16:11] <T13> I\\'ll add the suggestion to gray out the unusable with VE gadgets \\n[16:11] <mooeypoo> Ah, *that* kind of user errors. Hm. Not sure how you can handle those other than politely correct the user\\'s false assumption\\n[16:11] <T13> On Bugzilla...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-qgqq35kbi5wss2tlgmhg', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375737720, 'dateModified': 1643977440, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52562', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace should not delete list and line in same action', 'description': {'raw': '**Author:** `mcdevitd`\\n\\n**Description:**\\nTypically, the expected behavior from hitting backspace at the beginning of a list line is to remove the bullet/number at that indent level so it is no longer a list, and no more. VisualEditor will completely delete the line itself and move the text to the end of the previous line. This is not how OpenOffice or Word works.'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375729680, 'dateModified': 1650774324, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52557', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unindent should not remove lists', 'description': {'raw': \"**Author:** `mcdevitd`\\n\\n**Description:**\\nThe expected behavior in most word processors (Word and OpenOffice) is that the user can unindent (shift-tab) only to get to the initial list indent level but it should not actually delete the bulleting/numbering itself when you to the end. In VisualEditor, unindenting once too many times can remove the initial bullet/number entirely.\\n\\nThis becomes particularly annoying when (because of the behavior described in bug 48051) you accidentally split a list into two lists which can't be fixed clicking the list button again to re-add the bullet/number.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375726080, 'dateModified': 1643977440, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52554', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Change the order of the \"edit\" (VE) and \"edit source\" (WT) tabs on hewiki to have WT as primary', 'description': {'raw': 'Users are requesting VE August update (https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/August_2013_update) to be deployed in on hewiki.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**URL**: https://he.wikipedia.org/wiki/%D7%A9%D7%99%D7%97%D7%AA_%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:%D7%A2%D7%A8%D7%9F#.D7.A9.D7.99.D7.A0.D7.95.D7.99_.D7.91.D7.9E.D7.99.D7.A7.D7.95.D7.9D_.D7.94.D7.A7.D7.99.D7.A9.D7.95.D7.A8_.22.D7.A2.D7.A8.D7.99.D7.9B.D7.94_.D7.91.D7.A7.D7.95.D7.93_.D7.9E.D7.A7.D7.95.D7.A8.22_-_.D7.9B.D7.9E.D7.95_.D7.91.D7.95.D7.95.D7.99.D7.A7.D7.99.D7.A4.D7.93.D7.99.D7.94_.D7.94.D7.90.D7.A0.D7.92.D7.9C.D7.99.D7.AA'}, 'authorPHID': 'PHID-USER-cfsvvgbtlqnbt2yokfjf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381515689, 'spacePHID': None, 'dateCreated': 1375721160, 'dateModified': 1381515689, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52552', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Empty HTML elements are not identifiable', 'description': {'raw': \"Slightly related to bug 51322 \\n\\nTake the Link FA templates on https://en.wikipedia.org/wiki/The_Adventures_of_Tintin?veaction=edit for instance. \\n\\nThese produce empty elements, and don't qualify under 'solely metadata' of bug 51322, even though they are somewhat similar to it.\\n\\nThe templates are represented with the char: ↵\\ufeff\\nUsing the arrow keys to cursor trough this sequence will sometimes produce the template editor indicator. However their is little identifying these templates to the user and due to the interspersed ↵\\ufeff, users think they should be deleted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393529166, 'spacePHID': None, 'dateCreated': 1375720020, 'dateModified': 1417572591, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52551', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Floated node's action icon (e.g. for template) appearing in wrong location, relative to its initial position, not its actual position\", 'description': {'raw': 'From http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Quote_box\\n\\nIn the adventures of tintin \\nhttp://en.wikipedia.org/wiki/The_Adventures_of_Tintin?veaction=edit\\n\\nthe first {{quote box}} has been pushed down by the info box. The transclusion icon for this appears appear where the quote box was initially (just below the History section header on the right hand side) not where it actually appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51548'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1519404104, 'spacePHID': None, 'dateCreated': 1375712940, 'dateModified': 1519404104, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52547', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'User preferences are inconsistently stored (bool/int as default, string for overrides)', 'description': {'raw': 'Just look at my mw.user.options table added below. 1 vs true vs \"1\". I\\'m in favor of using numbers over booleans here, but why do we have string values for numbers ?\\n\\nWorse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return \"1\".\\n\\nWe should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.\\n\\n```\\naftv5-last-filter: null\\nccmeonemails: 0\\ncols: \"120\"\\ndate: \"mdy\"\\ndiffonly: \"1\"\\ndisablemail: 0\\ndisablesuggest: 0\\necho-email-format: \"html\"\\necho-email-frequency: 0\\necho-notify-show-link: true\\necho-show-alert: true\\necho-subscriptions-email-article-linked: false\\necho-subscriptions-email-edit-thank: false\\necho-subscriptions-email-edit-user-talk: 1\\necho-subscriptions-email-mention: false\\necho-subscriptions-email-other: false\\necho-subscriptions-email-page-review: false\\necho-subscriptions-email-reverted: false\\necho-subscriptions-email-system: true\\necho-subscriptions-web-article-linked: \"1\"\\necho-subscriptions-web-edit-thank: true\\necho-subscriptions-web-edit-user-talk: true\\necho-subscriptions-web-mention: true\\necho-subscriptions-web-other: true\\necho-subscriptions-web-page-review: true\\necho-subscriptions-web-reverted: true\\necho-subscriptions-web-system: true\\neditfont: \"default\"\\neditondblclick: 0\\neditsection: 1\\neditsectiononrightclick: 0\\nenotifminoredits: 0\\nenotifrevealaddr: 0\\nenotifusertalkpages: 1\\nenotifwatchlistpages: 0\\nep_bulkdelcourses: true\\nep_bulkdelorgs: false\\nep_showdyk: true\\nep_showtoplink: false\\nextendwatchlist: 0\\nfancysig: \"1\"\\nflaggedrevseditdiffs: true\\nflaggedrevssimpleui: 1\\nflaggedrevsstable: 0\\nflaggedrevsviewdiffs: false\\nforceeditsummary: \"1\"\\ngadget-BugStatusUpdate: \"1\"\\ngadget-DRN-wizard: 1\\ngadget-HotCat: \"1\"\\ngadget-Navigation_popups: \"1\"\\ngadget-NoAnimations: \"1\"\\ngadget-PrintOptions: \"1\"\\ngadget-ReferenceTooltips: 1\\ngadget-UTCLiveClock: \"1\"\\ngadget-addsection-plus: \"1\"\\ngadget-charinsert: 1\\ngadget-contribsrange: \"1\"\\ngadget-edittop: \"1\"\\ngadget-exlinks: \"1\"\\ngadget-metadata: \"1\"\\ngadget-mySandbox: 1\\ngadget-purgetab: \"1\"\\ngadget-teahouse: 1\\ngadget-widensearch: \"1\"\\ngadget-wikEd: \"1\"\\ngadget-wikEdDiff: \"1\"\\ngender: \"male\"\\ngettingstarted-task-toolbar-show-intro: \"\"\\nhideminor: 0\\nhidepatrolled: 0\\nimagesize: 2\\njustify: 0\\nlanguage: \"en\"\\nmath: \"6\"\\nmfWatchlistFilter: \"all\"\\nmfWatchlistView: \"feed\"\\nminordefault: 0\\nnewpageshidepatrolled: 0\\nnocache: 0\\nnoconvertlink: 0\\nnorollbackdiff: 0\\nnumberheadings: 0\\npreviewonfirst: 0\\npreviewontop: 1\\nrcdays: 7\\nrclimit: 50\\nrcshowwikidata: \"1\"\\nrememberpassword: 0\\nrows: \"30\"\\nsearchNs0: true\\nsearchNs1: false\\nsearchNs2: false\\nsearchNs3: false\\nsearchNs4: false\\nsearchNs5: false\\nsearchNs6: false\\nsearchNs7: false\\nsearchNs8: false\\nsearchNs9: false\\nsearchNs10: false\\nsearchNs11: false\\nsearchNs12: false\\nsearchNs13: false\\nsearchNs14: \"1\"\\nsearchNs15: false\\nsearchNs100: false\\nsearchNs101: false\\nsearchNs108: false\\nsearchNs109: false\\nsearchNs446: false\\nsearchNs447: false\\nsearchNs710: false\\nsearchNs711: false\\nsearchNs828: false\\nsearchNs829: false\\nsearchlimit: 20\\nshowhiddencats: \"1\"\\nshowjumplinks: 1\\nshownumberswatching: 1\\nshowtoc: 1\\nshowtoolbar: 1\\nskin: \"vector\"\\nstubthreshold: \"2000\"\\nthumbsize: 4\\ntimecorrection: \"ZoneInfo|120|Europe/Amsterdam\"\\nuls-preferences: \"\"\\nunderline: 2\\nusebetatoolbar: 1\\nusebetatoolbar-cgd: 1\\nuseeditwarning: 1\\nuselivepreview: 0\\nusenewrc: \"1\"\\nuserjs-curationtoolbar: \"hidden\"\\nvariant: \"en\"\\nvector-collapsiblenav: 1\\nvector-simplesearch: 1\\nvisualeditor-betatempdisable: 0\\nvisualeditor-enable: 1\\nwatchcreations: 1\\nwatchdefault: 0\\nwatchdeletion: 0\\nwatchlistdays: 3\\nwatchlisthideanons: 0\\nwatchlisthidebots: 0\\nwatchlisthideliu: 0\\nwatchlisthideminor: 0\\nwatchlisthideown: 0\\nwatchlisthidepatrolled: 0\\nwatchmoves: 0\\nwikilove-enabled: 1\\nwllimit: 250\\nwlshowwikibase: \"1\"\\n```\\n--------------------------\\n**See Also**:\\n{T29471}'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375702860, 'dateModified': 1709067394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52542', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In the save dialog, also show the \"switch to wikitext\" button in the wikitext diff so they can fix last-minute issues', 'description': {'raw': 'when saving, there is possibility to check the result visually. allow to edit it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T52687}'}, 'authorPHID': 'PHID-USER-2ccnbnjo2s2q3diidydr', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375606860, 'dateModified': 1643977440, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52519', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: The 'beta' element in the edit tab has an overline instead of underline in Firefox\", 'description': {'raw': 'Greg also reproduced this.  He sees a superscript, but I have an additional issue, that the beta is roughly the same horizontal position.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408815618, 'spacePHID': None, 'dateCreated': 1375503180, 'dateModified': 1417584198, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52493', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors', 'description': {'raw': 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects.\\n\\nHowever, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.\\n\\nThere will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.\\n\\nAs it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don\\'t recognise the response. Sort of a:\\nIF editor=\"VisualEditor\" THEN do X ELSE do Y\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375469280, 'dateModified': 1643977440, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52471', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dialogs should have a \"cancel\" button next to \"Apply changes\"', 'description': {'raw': 'What it says on the tin: The transclusion editor should have a \"cancel\" button next to \"Apply changes\". This would close the editor without saving any changes.\\nPossibly it should require a confirmation if one or more templates have been selected.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52386'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410807070, 'spacePHID': None, 'dateCreated': 1375460340, 'dateModified': 1456047619, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52462', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'In the VisualEditor media selector, show the name of each file so it can be identified', 'description': {'raw': 'User:Wouterstomp at en.wp suggests that in the media selection dialog, the full name of an image should be shown in a tooltip when you hover over it. Either for all images or only those whose name is too long to be shown in full beneath the image.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421466756, 'spacePHID': None, 'dateCreated': 1375458480, 'dateModified': 1438734490, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52459', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion editor should should give an \"are you sure?\" message if an unknown template is selected', 'description': {'raw': 'en.wp editor GermanJoe suggests that if you try to add a template not in the transclusion editor\\'s list of known templates that it should give a warning or \"are you sure?\" message.\\n\\nSuch a message would note that very new templates might not appear in he list.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1518444836, 'spacePHID': None, 'dateCreated': 1375435380, 'dateModified': 1518742505, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52449', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Transclusion dialog should not suggest documentation sub pages as templates', 'description': {'raw': \"Currently the the transclusion editor's list of templates includes /Doc and other subpages of templates that are not themselves actual templates.\\n\\nAt https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_2#Removing_template_subpages_from_the_template_selection_list.3F there was a discussion about this which suggested possible ways forward:\\n* Exclude all subpages except those explicitly marked as templates, e.g by magic word or category\\n* Include all subpages except those explicitly marked as not being templates, e.g. by magic word or category\\n\\nSee also:\\n* {T52512}\\n* {T58516}\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1557451094, 'spacePHID': None, 'dateCreated': 1375434960, 'dateModified': 1660398889, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52448', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying and pasting the first reference on a page, then deleting the pasted reference results in ref \"0\"', 'description': {'raw': 'I was able to produce a reference labelled \"0\" in the VisualEditor using the following steps:\\n\\n1. Create a simple page with some text and a reference. (I\\'ve made an example at [[User:Mr. Stradivarius/ref0]].)\\n2. Copy and paste the reference to somewhere else in the page.\\n3. Delete the reference from the text that has just been copied and pasted.\\n4. The first reference is automatically renumbered to \"0\".\\n\\nThe numbering of the first is fixed (back to \"1\") if you delete the line of text that you were on, but if you add new lines of text the first reference remains laballed \"0\" even if the pasted line is subsequently removed. The numbering still starts at 0 if you add another reference, so you get ref \"0\", ref \"1\", etc.\\n\\nThis is on Firefox 22.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-rjtk3h6l2quifuajiime', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379656831, 'spacePHID': None, 'dateCreated': 1375433040, 'dateModified': 1417572834, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52446', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Firefox up-down cursoring around aliens is broken, takes user to end of page sometimes', 'description': {'raw': 'When the first line of an article is a hatnote template that generates exactly 1 line of text in the visual editor, pressing down twice takes you to the end of the article. When the hatnote template generates more than one line then pressing down takes you to the end of the first line but no further.\\n\\nI have been unable to reproduce this with templates other than hatnotes. \\n\\nSteps to reproduce (short hatnote):\\n1. Load a page with a short hatnote in VE, e.g. [[Laurence of Canterbury]]\\n2. Press the down cursor twice\\n\\nExpected behaviour: you end up on the third line of the page\\nActual behaviour: you end up on the last line of the page\\n\\nSteps to reproduce (long hatnote):\\n1. Load a page with a long hatnote in VE, e.g. [[An American in Paris]]\\n2. Press the down cursor three or more times.\\n\\nExpected behaviour: you end up on the third or fourth etc. line of the page\\nActual behaviour: you end up at the end of the first line of the hatnote.\\n\\nSandbox pages to test:\\nLong hatnote: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=566827194&veaction=edit\\nShort hatnote: https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox2&oldid=566827110&veaction=edit\\n\\nThis might be related to bug 51708\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51708'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380754670, 'spacePHID': None, 'dateCreated': 1375432860, 'dateModified': 1417572828, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52445', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"The on-page notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices, unlike all the other status notes\", 'description': {'raw': \"Flagged Revisions provides a number of edit notices about the status of the page being edited, but this one (about the status of the transcluded components thereof) isn't. This feels wrong. It also means VisualEditor can't warn people about it.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52280\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-qaoxfiqu6bxhd5ehlwhc', 'dateClosed': 1422041644, 'spacePHID': None, 'dateCreated': 1375423920, 'dateModified': 1422041644, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52440', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector should have bottom margin to avoid cutting the page (UX)', 'description': {'raw': \"Screenshot of problem\\n\\nWhen the link inspector is fairly tall and the space somewhat narrow (e.g. a red link, 10 suggestions in the inspector, and the link itself is towards the bottom of the screen), the box will expand further than the page goes (triggering a scrollbar if needed).\\n\\nThat's fine, except that it is hard to see for the user whether there is more or not. Especially with OSX hiding scroll bars by default.\\n\\nThere should be some bottom margin so that it can be clearly seen that the bottom of the list is the bottom, ans eparated from the bottom of the (now expanded) page.\\n\\nSee attached screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11124}\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1428490652, 'spacePHID': None, 'dateCreated': 1375410180, 'dateModified': 1441911419, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52436', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Extending an existing DL-indentation renders correctly in CE, but doesn't come through on save\", 'description': {'raw': 'Pressing enter at the end of a colon indented line and typing more text displays as an indented, but, on save, (and review changes) the colon has not been added to the new line.\\n\\nSteps to reproduce:\\n\\n0. Start with a simple colon indented section. (See here: http://en.wikipedia.org/w/index.php?title=User:Markhurd/Sandbox&oldid=566721115 )\\n1. Edit with VE.\\n2. Click at end of last indented line.\\n3. Press Enter. Note this displays as continuing the indentation.\\n4. Type some text.\\n5. Save. Note that the colon is not included. (You can see it missing with Show Changes.)\\n\\nMy diff: http://en.wikipedia.org/w/index.php?title=User:Markhurd/Sandbox&diff=566721183&oldid=566721115\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fgul5wwrgbtdpd5fved3', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375368960, 'dateModified': 1721164816, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52399', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit notices (and other toolbar notices) should have a close button', 'description': {'raw': 'It isn\\'t obvious to all users that clicking on the warning about Wikitext will make it disappear.\\n\\nFor example, PamD at en.wp said:\\n\"I edited an article and found I\\'d got the popup saying I\\'d been using wiki markup, I should go into Edit Source, my edits wouldn\\'t be saved, etc. I knew I\\'d input a pair of \\'\\'s at one time but had then remembered the error of my ways, removed them, and marked the title as italic in VE style, so was pretty confident I hadn\\'t used any wiki markup and went ahead and saved the edit (difficult because the popup was sitting on top of the savepage box).\"\\n\\nThe main issue there is Bug 52155, but after being pointed to that bug she replied:\\n\\n\"so if I\\'d clicked on the box it would have gone away... ? Not obvious!\"\\n\\nIt would be good to add an X in the upper right corner to indicate that it can be closed. This wouldn\\'t change the behaviour that clicking anywhere on the box dismisses it, just give a visual indication that it can be done.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51701\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52462'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380932424, 'spacePHID': None, 'dateCreated': 1375356660, 'dateModified': 1417572826, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52386', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <references /> not fully populated but {{reflist}} is', 'description': {'raw': 'In some cases it seems that <references /> is not fully populating the references list while {{reflist}} does.\\nExample at: At https://en.wikipedia.org/w/index.php?title=Christian_Scott&oldid=566681769\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50094'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386608699, 'spacePHID': None, 'dateCreated': 1375341060, 'dateModified': 1417572740, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52371', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Explore performance gains from progressive (JIT?) de-alienation in VisualEditor', 'description': {'raw': 'Random idea that might improve load performance: initially alienate the entire document, then progressively convert and dealienate it. This should bring the editor into view quickly and allow the first paragraph to be edited quickly while the rest of the page is still processing.\\n\\nPossible pitfall: reference numbering and other crazy stuff in MWReferenceNode\\n\\nSee {T76544} for the same idea, but for content blocks.'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375323540, 'dateModified': 1595627783, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52365', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <tt> annotations should be handled by the <code> annotation code', 'description': {'raw': 'en.wp user Cryptic C62 comments:\\n\"Take a look at the text this page. The first two sentences may appear to be identical. If one activates VE, one will find that the first sentence (which employs <tt>) cannot be edited, but the second one (which employs <code>) can. My question is this: If the editor is supposed to be visually intuitive, why are two (almost) visually identical elements handled differently? \"\\n\\nThe page referred to is: https://en.wikipedia.org/w/index.php?title=User:Cryptic_C62/sandbox&oldid=566625027\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375933962, 'spacePHID': None, 'dateCreated': 1375304640, 'dateModified': 1417572949, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52352', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: API does not apply PST (pre-save transform) when generating its diff', 'description': {'raw': 'It is possible to insert a substituted template (by just putting in \"subst:whatever\" as its name). This will be saved correctly (substituted), but the diff shown in the review dialog shows the non-substituted wikitext.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53201'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398283331, 'spacePHID': None, 'dateCreated': 1375301760, 'dateModified': 1443276372, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52345', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images: Links in alt (and maybe other) attributes of images generates incorrect HTML', 'description': {'raw': 'en.wp user User:Timwi reports\\n\\n\"On the page [[Earth]], we had the following markup code:\\n\\n[[File:(filename)|thumb|700px|center| (caption here) |alt= (alt text here) ]]\\n\\nThe VisualEditor parsed this incorrectly and assumed that “alt= (alt text here)” was the \\'\\'caption\\'\\'.\\n\\nChanging the order of the items fixed this despite having no effect on the rendered page, which indicates that it’s a bug in VisualEditor and not incorrect MediaWiki markup.\" http://en.wikipedia.org/w/index.php?title=Earth&diff=566614668&oldid=566595613 \\n\\nI\\'ve done some testing in my sandbox and it seems like the issue is somehow related to the presence of the {{val}} template. I wasn\\'t able to replicate the bug with the {{small}} or {{convert}} templates for example, but I\\'ve not done extensive testing with the latter or with any other template.\\n\\nhttps://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox&oldid=566618437&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://parsoid-lb.eqiad.wikimedia.org/enwiki/User:Thryduulf/sandbox?oldid=566618437'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1426634110, 'spacePHID': None, 'dateCreated': 1375300620, 'dateModified': 1428510524, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52341', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Broken browser plugins cause cruft to be injected into the page (tracking)', 'description': {'raw': '\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1524218709, 'spacePHID': None, 'dateCreated': 1375286580, 'dateModified': 1640118714, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52327', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Media items are clearing templates (or they're being forced to width:100%?)\", 'description': {'raw': 'Screenshot\\n\\nAdding an image with caption besides a list creates whitespace in edit mode, see screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://de.wikipedia.org/wiki/116._Panzer-Division_(Wehrmacht)\\n\\n**Attached**: {F11788}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394223928, 'spacePHID': None, 'dateCreated': 1375271820, 'dateModified': 1417572580, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52320', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference defined inside a reference list but of a different group inside template appears as part of the template and also in the appropriate reference list, but blank this time', 'description': {'raw': '**Author:** `kwwilliams`\\n\\n**Description:**\\nIn http://en.wikipedia.org/w/index.php?title=List_of_record_charts&oldid=566209687, notice how Note 1 gets transformed in the string \"1.0.1.1\" and the actual contents of Note 1 becomes reference 19, which is completely unused in the article body.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53486'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375225080, 'dateModified': 1416846538, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52300', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE should use the existing \"action\" URL parameter instead of the new \"veaction\"', 'description': {'raw': \"When we edit using the visual editor, we still get\\nmw.config.get( 'wgAction' ) === 'view'\\ninstead of\\nmw.config.get( 'wgAction' ) === 'edit'\\n\\nSee also\\nhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070603.html\\nwhich quotes\\nhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070601.html\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\n* {T53421}\\n* {T55746}\\n* {T55441}\"}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1455664404, 'spacePHID': None, 'dateCreated': 1375206000, 'dateModified': 1527625310, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52281', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"The on-page Flagged Revisions notice about transcluded files or templates having outstanding changes doesn't appear in the edit notices\", 'description': {'raw': 'When a page has pending edits and it is opened for editing using VisualEditor, there is a dropdown box with a notice about this.  When a page has a template or a file with pending changes is opened for editing, the dropdown box does not appear.\\n\\nAn example on the Russian Wikipedia:\\nhttps://ru.wikipedia.org/wiki/%D0%98%D1%80%D0%B3%D0%B8%D1%88\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52440'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422422963, 'spacePHID': None, 'dateCreated': 1375204500, 'dateModified': 1438734490, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52280', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Improve nowiki escaping of template arguments by using global context', 'description': {'raw': 'When an unmatched literal square bracket is used in the title of a reference, Parsoid or VisualEditor encloses it in a nowiki tag.\\n\\nExample on the live wiki: https://en.wikipedia.org/w/index.php?title=Wikipedia&diff=566045928&oldid=566042453#cite_ref-209 (line 360)\\nExamples in testing: https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=566402676&oldid=566401436\\n\\nIt is possible this is a reappearance of or related to T45067\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\n{T45067}\\n{T52331}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375178760, 'dateModified': 1583898264, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52268', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE edit tab points to the wrong oldid on diff pages (earlier version not later one)', 'description': {'raw': '**Author:** `sandrobt.wiki`\\n\\n**Description:**\\nThe (visual)edit button in a diff (such as http://it.wikipedia.org/w/index.php?title=Kawakami_Gensai&diff=20609681&oldid=18301858) makes you edit the last version (in the example above the edit button gives the link http://it.wikipedia.org/wiki/Kawakami_Gensai?veaction=edit), whereas clicking on edit source makes you edit the old version (the newest of the two compared versions).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397598107, 'spacePHID': None, 'dateCreated': 1375161360, 'dateModified': 1417572488, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52261', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Subpages' link to their parent in the page strapline (#contentSub) get hidden but are still there\", 'description': {'raw': 'Steps to reproduce:\\n\\nGo to any page that is a subpage, such as a user sandbox. Observe the link to the parent page, located just under \"From Wikipedia...\". Activate VE. Observe that the aforementioned link disappears.\\n\\nFound in firefox 22, chrome 28, in both monobook and vector. Screenshot at https://en.wikipedia.org/wiki/File:VE_Phantom_Link.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54325\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58063'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389633369, 'spacePHID': None, 'dateCreated': 1375131300, 'dateModified': 1444199726, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52243', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Render absolute URLs as links inside the editor', 'description': {'raw': \"When you copy & paste a link into VisualEditor, it will not be recognized as a URL, but will appear as plaintext. The MediaWiki parser does render it as a clickable link, of course.\\n\\nThis is annoying especially for references, because you might be confused why your link you're adding as a citation doesn't appear to be clickable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52204\"}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394489652, 'spacePHID': None, 'dateCreated': 1375129740, 'dateModified': 1428506692, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52241', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Automatically recognise bare links and magic links (ISBN/etc.), and display as a link', 'description': {'raw': 'Adding \"ISBN 0-471-17864-0\" doesn\\'t render the ISBN as a link.  This is more important in the reference tool, but should work on all rich text surfaces.\\n\\nSee also:\\n* {T54241}\\n* {T63558}'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1439918046, 'spacePHID': None, 'dateCreated': 1375057320, 'dateModified': 1441745262, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52204', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Invocations of deleted images don't render at all\", 'description': {'raw': '**Author:** `wikipedia`\\n\\n**Description:**\\nWhen a file is deleted and still is being used in an article, this file is shown in the article as a box with a red link in it. Starting VE to remove the link, the link is no more visible and thus cannot be removed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows 7'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389632313, 'spacePHID': None, 'dateCreated': 1375010460, 'dateModified': 1487999636, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52186', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph', 'description': {'raw': '**Author:** `jonathan_haas`\\n\\n**Description:**\\nSteps to reproduce:\\n\\n1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit\\n2. Position the cursor at the start of the page directly before the bold \"T\".\\n3. Hit Backspace (to delete infobox)\\n4. Hit Ctrl+Z (undo)\\n5. Hit Backspace again\\n6. Hit Ctrl+Z again\\nRepeat as long as you want\\n\\nActual result:\\n\\nOn each Ctrl+Z a paragraph more is selected\\n\\nExpected result:\\n\\nSelection stays the same, undo should undo the action and not change the selection\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394503778, 'spacePHID': None, 'dateCreated': 1375008900, 'dateModified': 1443276375, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52184', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: On \"applying changes\" in a reference dialog, if the contents are blank, just delete the reference', 'description': {'raw': 'Removing the content from out of a <ref> .. </ref> should prompt the user that they need to delete the reference.  Perhaps a tooltip, or this might be an opportunity to use a hover trick to give the user something to click to acknowledge they intended to delete the ref.\\n\\nIt shouldnt be possible to save with an empty ref, as that is an error condition.\\n\\nhttps://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&diff=566133128&oldid=566132993\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50609'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405038215, 'spacePHID': None, 'dateCreated': 1375008300, 'dateModified': 1417572032, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52182', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If VisualEditor is the primary editor, type=create and type=fulltext buttons should point to VE, not WT editor', 'description': {'raw': \"If VisualEditor is default, why after clicking on a red link there's 'action=edit' in url and the source editor runs instead of 'veaction' and VE? I've checked it out on the enwiki and plwiki, but it concerns the rest of phase 2 as well and creating a new page in general. Furthermore, it makes inputboxes ('type=create') incompatible with VE and it can be a bothering problem on some wikis.\\n\\n**See Also**: {T55441}\"}, 'authorPHID': 'PHID-USER-gf5juv3z3p75bykrcrhf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374969780, 'dateModified': 1558261962, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52162', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add CTRL+Y as a second shortcut for redo', 'description': {'raw': 'An editor on en.wp has requested that Ctrl+Y should initiate the redo action. Presently the shortcut is ctrl+shift+z.\\n\\nIn my experience both shortcuts are used in about 50% of applications (Xubuntu Linux) so it would be ideal if both shortcuts could be used.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394055873, 'spacePHID': None, 'dateCreated': 1374931680, 'dateModified': 1443276375, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52140', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Come up with something better than .offsetOf()', 'description': {'raw': 'We overuse both \"index\" and \"offset\" in our vocabulary, and one of the more cringe-worthy results is the rename of .indexOf() to .offsetOf() in AnnotationSet. We should refactor our vocabulary and rename this to something saner.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374887040, 'dateModified': 1643977440, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52130', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding support to Grammar/Orthography fixes custom wiki defined button to be applied on texts visually on client side', 'description': {'raw': '**Author:** `nzmoihue`\\n\\n**Description:**\\nI think one nice/needed addition to Visual Editor would be supporting custom wiki defined scripts for fixing text [without interfering with wiki text]. For example on Persian Wikipedia we have an edit tool script [1] [2] that wiki users are very depends on it for fixing article texts and without it Visual Editor would be useless for them.\\n\\n\\n 1. http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%E2%80%8C%D9%BE%D8%AF%DB%8C%D8%A7:%D8%A7%D8%A8%D8%B2%D8%A7%D8%B1%D9%87%D8%A7%DB%8C_%D9%88%DB%8C%D8%B1%D8%A7%DB%8C%D8%B4%DB%8C\\n 2.http://fa.wikipedia.org/wiki/MediaWiki:Gadget-Extra-Editbuttons-Functions.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374875580, 'dateModified': 1643977441, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52122', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Story] VisualEditor: Ability to edit language links on Wikidata from within the editor', 'description': {'raw': 'People would like to be able to edit the language links that are coming from Wikidata in the page settings dialog. A link from there to Wikidata would probably also be a good first step.\\n\\n**See Also**:\\n{T59929}\\n{T64005}\\n{T74178}'}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374859560, 'dateModified': 1710415739, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52105', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"loadImages bad\" error on uploading ~85MB .ogv files', 'description': {'raw': '**Author:** `molly.white5`\\n\\n**Description:**\\nTwice now I\\'ve uploaded .ogv files (made with RecordMyDesktop, if that helps) and gotten a popup that very helpfully informs me, \"loadImages bad\". This appears directly after I choose the file to upload, and I\\'m guessing it has something to do with the inability to find a thumbnail image? Anyway, at the very least a more descriptive error message might be nice.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'dateClosed': 1449164913, 'spacePHID': None, 'dateCreated': 1374796680, 'dateModified': 1449164913, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52070', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow extension options to be specified in API calls', 'description': {'raw': 'The rendering of a page can be affected by user extension options (e.g. their choice of renderer for the Math extension) so we should be able to pass through these options to the API.\\n\\nThis is blocking proper support of the Math extension in VisualEditor.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374764640, 'dateModified': 1602867757, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52031', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve.ui.Context#toolbar is null in MediaWiki', 'description': {'raw': \"Following the documentation[1] starting at ve.ui.Surface (from ve.instances[0]) one would go to #getContext and access .toolbar. But though that property is defined, it is set to null.\\n\\nI'm not sure why, but apparently our MediaWiki's init is instantiating its own and is only accessible from ve.init.mw.ViewPageTarget#toolbar (ve.init.mw.targets[0].toolbar).\\n\\nIt probably shouldn't have to instantiate its own one, and certainly not make it inaccessible to the rest of VE.\\n\\n\\n[1] https://doc.wikimedia.org/VisualEditor/master/#!/api/ve.ui.Surface\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412590622, 'spacePHID': None, 'dateCreated': 1374716460, 'dateModified': 1417571697, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52011', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Minor Edit\" and \"Watch this page\" checkboxes on the save page form are not visible when logged out', 'description': {'raw': 'It seems that Chrome 28 does not display the \"Minor Edit\" and \"Watch This Page\" checkboxes on the save page form. This does work in Firefox 22. Does not seem skin related - Vector and Monobook have the same problem in either browser\\n\\nSteps to reproduce:\\n- Open any page in edit mode.\\n- Make a small change, press Save page.\\n- (Firefox): There will be checkboxes stating \"Watch this page\" and \"This is a minor edit\"\\n- (Chrome): Those checkboxes are not present.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374693622, 'spacePHID': None, 'dateCreated': 1374688740, 'dateModified': 1417573075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51981', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Undo does not invalidate cached wikitext diff content', 'description': {'raw': 'English Wikipedia user Atethnekos reports: \\n\"If I make 2 changes, review changes, exit review/save dialog, undo last change, and then review changes again, the review shows both changes, though saving only saves the first.\"\\n\\nSteps to reproduce:\\n1. Make two changes to a page in VE\\n2. Undo one change\\n3. Click save and review your changes. \\n-Expected behaviour: Only the first change is shown\\n-Actual behaviour: Both changes are shown.\\n4. Save the page. Only the first change has been saved.\\n\\nThis means that the review your changes is incorrect.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392062273, 'spacePHID': None, 'dateCreated': 1374660840, 'dateModified': 1417572663, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51947', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pending Changes dropdown overlaps toolbar in Monobook', 'description': {'raw': 'Reported by Atethnekos on EnWiki, who also provided an image: https://en.wikipedia.org/wiki/File:Platovesample1.png\\n\\n\"When I edit a page with the pending changes revision dropdown, and I am scrolled to the very top, the dropdown and the VE page settings link become mangled.  See highlight in included image.  Firefox 22 on Win7 Pro SP1.\"\\n\\nI can reproduce this in both Firefox 22 and Chrome 28. The issue seems specific to the Monobook skin - Vector renders the pending changes dropdown somewhat lower in both browsers.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374648228, 'spacePHID': None, 'dateCreated': 1374647880, 'dateModified': 1374648228, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51926', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Multicol/BeginKolommen/Colonne and wikitext leaking into VE', 'description': {'raw': \"Wikitext appearing in transclusion dialog\\n\\nThe underlying cause of this might be covered in bug 48231 or bug 51217 or others ... I thought I saw a bug about this, but cant find it now.\\n\\n[[template:multicol]] with wikisyntax inside it results in the attached screenshot, with wikitext visible in the transclusion dialog as 'Content' blocks.\\n\\nhttps://nl.wikipedia.org/wiki/Gebruiker:John_Vandenberg/test?veaction=edit\\n\\nSection headers & list items also cause this; see the last block here:\\nhttps://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=565567699&veaction=edit\\n\\nIf it helps, this issue is present on one of the parsoid topfails:\\n\\nhttps://nl.wikipedia.org/wiki/Eerste_divisie_1996/97?veaction=edit\\n\\nBeginKolommen occurs on nlwp 3047 times.  11362 times in enwp.  8861 times in eswp. 40985 times on itwp!, which is roughly 4% of the content pages.\\n\\nConfirmed this is happening on every itwp invocation that I edit\\nhttps://it.wikipedia.org/wiki/Speciale:PuntanoQui/Template:Colonne\\ne.g.\\nhttps://it.wikipedia.org/wiki/Aeroplano?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11763}\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374638040, 'dateModified': 1420846001, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51922', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Scroll to an item when it is selected e.g. when it has been newly inserted', 'description': {'raw': \"The bug 51905 made me realize of a potential problem. When a media, say an image, is inserted, sometimes it may be inserted outside the field of view of the user, and this may lead some users to think that it wasn't inserted at all, causing aborted edits, confusion, frustration, and even bad edits. For example if there is an infobox in the article, or a bunch of images aligned to the right, then if the user inserts an image, in many cases it will be inserted below all this, and the user will not see it without scrolling the screen.\\n\\nThe solution to this potential problem is, I think, fairly simple: make the VisualEditor detect if the image is in the field of view of the user, and if it's not, then scroll the screen so that it is!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58091\"}, 'authorPHID': 'PHID-USER-lucj4cqevg3ebah7vybd', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427668322, 'spacePHID': None, 'dateCreated': 1374614520, 'dateModified': 1427741121, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51911', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page content not rendered after unclosed  <center> tag in image caption of non-thumbnails', 'description': {'raw': 'When an image file is included directly in an article (i.e not as a thumbnail and not in a frame) with an unclosed <center> tag in the caption causes Visual Editor to not render any page content after the image.\\n\\nSee https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox2&oldid=565498603 for an example.\\n\\nAll the following conditions must be true to see this bug:\\n* Image must not be a thumbnail or in a frame\\n* The image caption must contain an unclosed html tag specifying text alignment in the caption. Tested with <center>, <p align=\"center\"> and <div align=\"right\">\\n* The image placement (left, right or center) must be specified\\n\\nThe bug does not occur with an unclosed italic html tag. I haven\\'t tested with other tags.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380746942, 'spacePHID': None, 'dateCreated': 1374598740, 'dateModified': 1417572829, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51893', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: editing window does not horizontally scroll for wide tables or other elements', 'description': {'raw': 'first table at [[Comparison of container formats]] rendered in a 1024px wide window. Firefox 22 on Linux\\n\\nIn VisualEditor the editing window does not horizontally scroll to accommodate wide tables. Table cells and their contents render as if the window did scroll, but as it does not they are truncated.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51755\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51820\\n\\n**Attached**: {F11662}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1538407902, 'spacePHID': None, 'dateCreated': 1374578220, 'dateModified': 1538407903, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51867', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Image options should be serialized in the wiki's language in rtl locales - localization i18n\", 'description': {'raw': 'When VisualEditor inserts an image, the thumbnail keywords are written in English: \"File:\", \"thumb\", \"right\" (but see Bug 51851).\\n\\nThis should not, theoretically, be a problem, because the VisualEditor is supposed to make these keywords unimportant and hidden from the end-user. However, while the source editor is still being widely used, this is a problem, especially for right to left languages: it is very hard to edit these English keywords when they are mixed with right-to-left text.\\n\\nThese keywords should be inserted in the language of the wiki.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1459884179, 'spacePHID': None, 'dateCreated': 1374569160, 'dateModified': 1660398889, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51852', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Disable 'Use existing reference' on pages without a reference\", 'description': {'raw': \"Steps to reproduce\\n1. start an empty sandbox (https://en.wikipedia.org/wiki/User:John_Vandenberg/mtgg?veaction=edit)\\n2. insert reference\\n3. use an existing reference\\n\\nExpected results:\\n'Use an existing reference' should be disabled, as there are none to select.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50458\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377889832, 'spacePHID': None, 'dateCreated': 1374557100, 'dateModified': 1417572843, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51848', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Recursive word addition with Google Input Tools in reference tool on Firefox', 'description': {'raw': \"Steps to reproduce:\\n1. Download and install Google input tools for windows www.google.co.in/inputtools\\n2. Open any page in firefox\\n3. Open VE\\n4. Edit a reference\\n5. Type anything in the reference. The word is input by the tools when the word is complete and one presses space/enter\\n\\nExpected Behaviour:\\nThe word is input and if the spacebar has been pressed, a space is input too.\\n\\nWhat happens instead:\\nThe word is entered recursively over and over. The space isn't input at all.\\n\\nSystem environment:\\nWin 7 X64 SP1\\nFirefox 15.0.1\\nGoogle input tools for languages hindi and punjabi(gurmukhi script)\\n\\nThe problem didn't seem to arise when using input tools for urdu, though its possible that's just coz the wiki is ltr and urdu is rtl.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378958789, 'spacePHID': None, 'dateCreated': 1374549360, 'dateModified': 1417048669, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51847', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Cursor not moving past \"ग्र\" and other multiple code-unit grapheme clusters on left arrow key press', 'description': {'raw': \"Steps to reproduce:\\n1. Open any page\\n2. Open VE\\n3. Type (or copy-paste) ग्र\\n5. Press left arrow key\\n\\nWhat should happen:\\nCursor should move to the left of the glyph\\n\\nWhat happens:\\nCursor stays there\\n\\nSystem environment:\\nWin 7 X64 SP1\\nGoogle Chrome 28.0.1500.72 m\\n\\nThe problem arises regardless of what follows ग्र . I've tried with space, tab, the letter a, devanagari characters that do not combine with the glyph, like क, and devanagari characters that do combine with the glyph, such as ि to produce ग्रि and ी to produce ग्री\\n\\nThe problem doesn't seem to affect firefox 15.0.1.\\n\\nIn chrome, the problem doesn't arise in the link editing window, or when editing parameter of a template. It does, however, arise when editing a reference.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1430334001, 'spacePHID': None, 'dateCreated': 1374547560, 'dateModified': 1438734496, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51846', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Reference dialog re-use search form doesn't recognise uppercase group names\", 'description': {'raw': 'The re-use tab in the reference dialog allows searching for group names. This was always possible. However, it doesn\\'t work when the group name is uppercase or contains an uppercase character. For example, it works when the group name is \"note\" but not when the group name is \"A\". It doesn\\'t matter if I search for \"a\" or \"A\", it\\'s not found.\\n\\nTurns out the relevant code is incomplete ever since it was written in 2013, see https://gerrit.wikimedia.org/r/70364. The relevant ticket was {T51733}.'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'bug', 'closerPHID': 'PHID-USER-k5wpqok2x66oei3wguaf', 'dateClosed': 1721831979, 'spacePHID': None, 'dateCreated': 1374525480, 'dateModified': 1729667258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51838', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion editor template search should additionally find in-string matches', 'description': {'raw': 'Split from bug 51436, Original comment was:\\n\"Also typing a word only shows template names starting with that word, not\\ncontaining it, which is a weird search behaviour.\\n\\nIf I type \"book\", template \"Cite book\" is not shown, which limits the search\\nfunctionality to be useful only for people who already know template names\\n(i.e. those who don\\'t need it).\"\\n\\nA further relevant comment was:\\n\"This is asking for VisualEditor ... 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.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51670'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374511680, 'dateModified': 1643977441, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51822', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: As much as possible, the link to the user manual should lead directly to a manual in the user's language\", 'description': {'raw': \"The VisualEditor's user manual is translatable in Meta, which is a Good Thing. Currently the help link uses Special:MyLanguage. This uses the user's UI language as defined on Meta, which is likely not to be the same as the user's UI language on a non-English site.\\n\\nAs much as possible, the link should point directly to the user manual in the language that the user is using currently for the UI.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374488220, 'dateModified': 1643977441, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51797', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Non-English Wikipedia issues (tracking)', 'description': {'raw': 'Tracking for VE issues of problems that are specific to a Wikipedia other than English Wikipedia, excluding RTL issues as they are tracked by bug 33126.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\n{T51998}\\n{T51999}'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422425002, 'spacePHID': None, 'dateCreated': 1374480780, 'dateModified': 1701795362, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51792', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Loading animation shows at top of page rather than top of window, so can be non-visible when editing a section', 'description': {'raw': 'When you type \"[[\" in visual editor, there is a \"wiki markup text\" popu (nice touch - Thanks, devs).\\n\\nHowever, this warning popup shows at top of page, so it\\'s not visible when the page is scrolled even a few lines.\\n\\nVE toolbar floats at the top of the browser\\'s page even when we edit at the middle of the article. the warning popu should do the same. \\n\\nREPRODUCTION INSTRUCTIONS\\n0) open [[en:The Rolling Stones]]\\n1) select one of the sections from the TOC\\n2) Click \"Edit\"\\n3) wait, wait, wait, wait...\\n4) close the edit notice\\n5) type \"[[\"\\n\\nEXPECTED\\n1) during the wait (3 above) there is a nice image asking you to wait: this image is expected to be visible\\n\\n2) when the \"edit notice\" shows up, you expect some clear way to close it.\\n\\n3) when typing \"[[\", you expect the \"wikitext warning\" popup to show up\\n\\nWHAT ACTUALLY HAPPEN\\n\\n1) the \"please wait\" image appears, but unfortunately it\\'s outside the screen, so you do not know why the page appears milky, and have no indication that this would eventually end.\\n\\n2) depending on your luck, clicking on various parts of the page *will* close the edit notice (if you\\'re lucky), or will take you to [[en:Template:Editnotices/Page/The Rolling Stones]] (i.e., another page from the one you are trying to edit) if you\\'re unlucky.\\n\\n3) the warning popup appears, but it\\'s at the top of the page, so unless you are editing the very first part of the page, you do not see it.\\n\\n\\nCOMMENTS:\\n1) VE is clever enough to have its toolbar visible even when scrolling down, using \"position:fixed\". same should be done for the \"please wait\" image and for the warning popup(s).\\n\\n2) the \"1 notice\" and the warning triangle on the toolbar should indicate that they are the gate to hiding the notice: e.g., change the \"1 Notice\" text to \"Hide notice\" when the notice is visible.\\n\\n3) it seems that the wikitext notice is not yet translated to all languages.\\n\\n\\npeace.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-akv4ingxkspiiam6r2n4', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379436668, 'spacePHID': None, 'dateCreated': 1374442980, 'dateModified': 1417572835, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51785', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Structural content inside a <small> should be alienated but this fails because they are inline rather than inline-block', 'description': {'raw': 'In an (un)ordered list nested in a table I am unable to edit wikilinks. While hovering above a wikilink the wikilink is an active weblink, instead of showing the icon of the link inspector, see URL.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://test.wikipedia.org/wiki/User:Raymond/nested'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1642381371, 'spacePHID': None, 'dateCreated': 1374430980, 'dateModified': 1642381371, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51778', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'git.wikimedia.org (gitblit) goes down when getting overloaded by Googlebot', 'description': {'raw': \"From the mailing list\\n\\n> from:\\t planetenxin <planetenxin@web.de> via gmail.com \\n> reply-to:\\t Wikimedia developers <wikitech-l@lists.wikimedia.org>\\n> to:\\t wikitech-l <wikitech-l@lists.wikimedia.org>\\n> date:\\t Sun, Jul 21, 2013 at 10:15 PM\\n> subject:\\t [Wikitech-l] Git Proxy Error\\n\\n> Hi folks,\\n> I'm constantly getting the following error on https://git.wikimedia.org/:\\n> Proxy Error\\n> The proxy server received an invalid response from an upstream server.\\n> The proxy server could not handle the request GET /.\\n> Reason: Error reading from remote server\\n>/Alexander\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51656\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49371\"}, 'authorPHID': 'PHID-USER-hwuumsjqciw7ji5qhpc7', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1441874873, 'spacePHID': None, 'dateCreated': 1374410040, 'dateModified': 1452717532, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51769', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Bypass browser blacklist', 'description': {'raw': 'Could we have a way to bypass the browser blacklist. e.g.\\n1. 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.\\n\\nFor 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55900'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381630832, 'spacePHID': None, 'dateCreated': 1374370800, 'dateModified': 1417572821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51765', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Visual editor: issues with removing leading space pre blocks', 'description': {'raw': \"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.\\n\\n* 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.\\n* 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.\\n* 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.\\n*If the block follows another pre-formatted block, the contents gets appended to the end of that block.\\n\\nIn all cases this can be worked around by inserting and then backspacing a new line at the start of the block.\\n\\nIn 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.\\n\\nThe differing behaviour of single and multi-line templates may be related to {T53708}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437778276, 'spacePHID': None, 'dateCreated': 1374347580, 'dateModified': 1438734499, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51758', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Wikitext warning triggered when editing paragraph with wikitext in it, even though none was added in this edit', 'description': {'raw': '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.\\n\\nVisualEditor flagged this as my adding wikimarkup and gave me the nowiki warning. :)\\n\\nSee http://en.wikipedia.org/wiki/File:Wikimarkup_warning_without_case.png which is confusingly titled, because I missed the \"u\" in \"cause.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416962052, 'spacePHID': None, 'dateCreated': 1374332100, 'dateModified': 1438734499, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51751', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Default whitespace for headings should include spaces before/after ==', 'description': {'raw': 'As a follow-up to bug 49428 and bug 50771, default whitespace for headings should includespaces before/after ==.\\n\\nOr in other words: prefer \"== Heading ==\" to \"==Heading==\".\\n\\n(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 )\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386965698, 'spacePHID': None, 'dateCreated': 1374320940, 'dateModified': 1386965698, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51744', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Rich content copied from sub-documents (image captions, references, etc.) down-cast to plain text when the sub-document is closed', 'description': {'raw': '**Author:** `lunarjam.mcgahan`\\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}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1535731638, 'spacePHID': None, 'dateCreated': 1374285540, 'dateModified': 1604402754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51725', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Output MathJax rendering for Math tags instead of images', 'description': {'raw': 'When MathJax is enabled we should render a <span> containing TeX, instead of an image.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1442497839, 'spacePHID': None, 'dateCreated': 1374264060, 'dateModified': 1442497908, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51698', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Links to local namespace Wikipedia:Foo rendered as mw:WikiLink/Interwiki to enwiki', 'description': {'raw': 'http://it.wikipedia.org/wiki/Utente:Elitre_%28WMF%29/Sandbox?veaction=edit\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://parsoid.wmflabs.org/it/Utente:Elitre_(WMF)/Sandbox'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-56wtmb23orq4pu5liyj5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380818608, 'spacePHID': None, 'dateCreated': 1374238320, 'dateModified': 1380818608, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51680', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Rapidly multiplying pawns after editing near a link in MobileSafari on iPad', 'description': {'raw': 'An 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.\"\\n\\nBased 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: other\\n**Platform**: Tablet PC\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50465'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434487685, 'spacePHID': None, 'dateCreated': 1374234180, 'dateModified': 1434492388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51677', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Search of parameters in transclusion editor should be case insensitive', 'description': {'raw': 'The 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11271}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394405793, 'spacePHID': None, 'dateCreated': 1374229560, 'dateModified': 1443276380, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51673', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Move the remove template/parameter button to somewhere more prominent?', 'description': {'raw': '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).\\n\\nBoth 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51739\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51135\\n\\n**Attached**: {F11269}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394073936, 'spacePHID': None, 'dateCreated': 1374229080, 'dateModified': 1443276380, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51672', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Drag-and-drop requires the item (image/reference/template) to be selected before it can be dragged', 'description': {'raw': 'A user on the English Wikipedia reports two problems when attempting to drag and drop an image.\\n\"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.\\n\\nProblem 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.\"\\n\\nThey are using Firefox 21, I can confirm both problems in Firefox 22.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54472'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403019840, 'spacePHID': None, 'dateCreated': 1374224700, 'dateModified': 1443278238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51665', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove (and stop adding) useless documentation', 'description': {'raw': '/**\\n * Creates an ve.Element object.\\n *\\n * @class\\n * @abstract\\n *\\n * @constructor\\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.\\n\\nSo, 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).\\n\\nI (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).\\n\\nThanks\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1530904290, 'spacePHID': None, 'dateCreated': 1374197220, 'dateModified': 1530904291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51650', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Page actions are wrong for VisualEditor', 'description': {'raw': 'mw.gettingStarted.logging.getPageSchemaAction returns the wrong values for VE.  For instance, it returns page-impression when the VE edit screen is open.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1703380210, 'spacePHID': None, 'dateCreated': 1374179400, 'dateModified': 1703380210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51634', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images specified with size foopxpx render at native size', 'description': {'raw': 'If a stub template includes an image size declaration that includes \"px\" then that image is shown at native resolution in the editor.\\n\\nThis 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\" [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]. \\n\\nInterestingly it renders as intended in VE when the template is initially placed, but does on every subsequent time it\\'s opened in VE.\\n\\nFeel 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51826'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393438887, 'spacePHID': None, 'dateCreated': 1374171240, 'dateModified': 1726475742, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51628', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Delete immediately before (or backspace after) a table cell moves text out of/into cell', 'description': {'raw': \"User: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.\\n*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.\\n\\nI 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.\\n*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.\\n*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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50286\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429468017, 'spacePHID': None, 'dateCreated': 1374166740, 'dateModified': 1438734504, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51624', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clarify beta explanation text', 'description': {'raw': '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\".\\n\\nWhile 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374257435, 'spacePHID': None, 'dateCreated': 1374162360, 'dateModified': 1417573084, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51620', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: If running on an old MW so jquery.client doesn't have what we need, don't just fail silently\", 'description': {'raw': 'Right now lots of users try VE with MW 1.21.x and are confused as to why they get nothing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375297757, 'spacePHID': None, 'dateCreated': 1374158040, 'dateModified': 1417572954, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51606', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Remove formatting drop-down's horrendous use of strings as implicit message names\", 'description': {'raw': \"'label': 'foo' should mean that the label is 'foo', not ve.msg( 'foo' );\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380056460, 'spacePHID': None, 'dateCreated': 1374109200, 'dateModified': 1417572832, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51592', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support the <code> tag as a text annotation', 'description': {'raw': 'VisualEditor should support adding and editing the code tag (<code></code>).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374868236, 'spacePHID': None, 'dateCreated': 1374109140, 'dateModified': 1417585053, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51590', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add more mw.hook events for wikipage: diff, categories etc.', 'description': {'raw': '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).\\n\\nA few others we should add for things outside the content:\\n\\n* [DONE in rMW125bfdfec63c3be1b7d94be2d03e21226fcf23f5] `wikipage.categories`\\n  arguments: `.catlinks`\\n\\n  Fired initially and from live preview.\\n  e.g. for things like HotCat to listen to\\n\\n* `wikipage.langlinks`\\n  arguments: `#p-lang`\\n\\n  Fire initially if `#p-lang` exists/non-empty, and from live preview.\\n\\n* [DONE in rMW9cfb9cb9fba4dcfd25a0924237681b7cc86a20df] wikipage.diff\\n  arguments: `#wikiDiff`\\n\\n  Fire initially if page has a diff on it, and from live preview if user\\n  did \"show changes\".\\n\\n  e.g. for patrolling tools to hook into the diff and the [mark as patrolled] link.\\n\\n* [DONE in rMW8d0dcb863701e78cb4b066f176da89091bba67b3] `wikipage.editform`\\n  arguments: (common parent of `.mw-summary-preview`, `.templatesUsed`, `.hiddencats`)\\n\\n  e.g. for vector.footerCleanup and other things that hook into this.\\n\\n--------------------------\\n**Version**: 1.21.x\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1538452334, 'spacePHID': None, 'dateCreated': 1374104340, 'dateModified': 1675614246, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51583', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Re-run wikipage content handlers (jquery.makeCollapsible, jquery.tablesorter) when rendering new revision after save', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383478009, 'spacePHID': None, 'dateCreated': 1374087720, 'dateModified': 1417584774, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51565', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Node action icon (e.g. for template) appearing in wrong location', 'description': {'raw': 'screenshot 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52547\\n\\n**Attached**: {F11877}'}, 'authorPHID': 'PHID-USER-nyv6rqxnzdy3oe323a3d', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423881296, 'spacePHID': None, 'dateCreated': 1374077760, 'dateModified': 1438734505, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51548', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Abandoning VE load by navigating away before Parsoid load complete throws API error dialog', 'description': {'raw': \"1. 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391025576, 'spacePHID': None, 'dateCreated': 1374077220, 'dateModified': 1443276380, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51546', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Default $wgVisualEditorNamespaces to $wgContentNamespaces instead of array( NS_MAIN )', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52188'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383942801, 'spacePHID': None, 'dateCreated': 1374063480, 'dateModified': 1417572754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51527', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unsetting \"minor edit\" for users with the \"mark all my edits as minor by default\" doesn\\'t work', 'description': {'raw': '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:\\n\\nFF:\\n\\nhttp://de.wikipedia.org/w/index.php?title=Benutzer:Thoken/test1&diff=prev&oldid=120588869\\n\\nChrome:\\n\\nhttp://de.wikipedia.org/w/index.php?title=Benutzer:Thoken/test1&diff=prev&oldid=120590664\\n\\ndiscussion on De.WP:\\n\\nhttp://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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374676726, 'spacePHID': None, 'dateCreated': 1374049980, 'dateModified': 1417572503, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51515', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Beta notice incorrectly highlights \"Leave feedback\" link when hovering the notice', 'description': {'raw': '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.\\n\\nIf 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.\\n\\n.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'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383002871, 'spacePHID': None, 'dateCreated': 1374026460, 'dateModified': 1417572759, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51500', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Spaces at the ends of template parameter values are trimmed', 'description': {'raw': 'In both named and unnamed parameters.\\n\\nThe unnamed one should be of course a bug.\\n\\nShould we manage to protect named ones from being trimmed in PHP parser?\\n\\nie. generate ({{P1|1= hello <nowiki/>}}) to protect the trailing space?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61049'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385385582, 'spacePHID': None, 'dateCreated': 1374013440, 'dateModified': 1423675689, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51484', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Generic first edit tour', 'description': {'raw': 'Make a \"First Edit\" tour to help someone make their first edit, in general.  This should not have any connection to GettingStarted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381904718, 'spacePHID': None, 'dateCreated': 1374012600, 'dateModified': 1381904718, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51483', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: blocked-notice-logextract doesn't appear when editing user pages of blocked users with VE\", 'description': {'raw': \"When editing the user page of a blocked user, some messages appear at the top of the page, for example blocked-notice-logextract.\\n\\nThey don't appear when editing with the VisualEditor.\\n\\nCompare:\\n\\nGood: https://en.wikipedia.org/w/index.php?title=User:SEAROSE8&action=edit\\n\\nBad: https://en.wikipedia.org/wiki/User:SEAROSE8?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52004\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395874791, 'spacePHID': None, 'dateCreated': 1373998440, 'dateModified': 1443276381, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51454', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page text sometimes pops up through the Media insertion dialog', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-nyv6rqxnzdy3oe323a3d', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437781075, 'spacePHID': None, 'dateCreated': 1373995560, 'dateModified': 1439331210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51450', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Template search results list should contain each template's descripton\", 'description': {'raw': \"**Author:** `turingt`\\n\\n**Description:**\\nSee this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ]\\n\\nThe search results for parameters include each parameter's description, making it easy to select the right one. \\n\\nBut 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).\\n\\nSo, add the template description to the search results list.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51774\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429285347, 'spacePHID': None, 'dateCreated': 1373980800, 'dateModified': 1660398890, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51436', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Add an \"autofill\" attribute for parameters which clients would automatically insert if none specified', 'description': {'raw': 'In 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.\\n\\nI think for example of some templates that have a date parameter to be filled with the date at which the template was inserted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-o34e5i3eq4nstbvcf26w', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411171613, 'spacePHID': None, 'dateCreated': 1373959860, 'dateModified': 1412789057, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51428', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow AbuseFilter rules to identify VE edits', 'description': {'raw': '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.\\n\\nBecause 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T54281}'}, 'authorPHID': 'PHID-USER-fuj45iylbizjg3yhehjt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373945100, 'dateModified': 1720034624, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51421', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page loading animated image is only LTR', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377205420, 'spacePHID': None, 'dateCreated': 1373924940, 'dateModified': 1417572943, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51401', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Add parameter type for wikitext', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52652'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383945230, 'spacePHID': None, 'dateCreated': 1373909880, 'dateModified': 1477067771, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51374', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar icons - \"reference\" (bookmark) alternatives or improvements', 'description': {'raw': 'Original icon, and 2 suggested alternatives\\n\\nThe \"Insert reference\" icon is not very intuitive. I\\'ve made a sketch of two alternatives.\\n\\nSee attachment, or on-wiki at http://commons.wikimedia.org/wiki/File:VisualEditor_-_Toolbar_-_Reference-edit1.png\\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]. \\n\\nThe grey text could be made into abstract letterforms - squiggles - (rather than the letters REF) in order to make it usable by all languages. \\n\\nOr we could use a grey \"+\" sign with the blue [number]. \\n\\n(The only problem is RightToLeft languages. Not sure how to solve that.)\\n\\nThe 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53396\\n\\n**Attached**: {F11513}'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': 'PHID-USER-flenunkasbjk4topxvaj', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401472548, 'spacePHID': None, 'dateCreated': 1373906820, 'dateModified': 1443278239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51372', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Improve how we suppress reference warnings in template rendering', 'description': {'raw': \"Currently it's a hack; it'd be nice to be a bit less of one.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50423\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375327521, 'spacePHID': None, 'dateCreated': 1373852760, 'dateModified': 1417572953, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51337', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Beta notices fly-out too narrow on some systems (even though its width is specified in ems)', 'description': {'raw': 'The Beta notice looks strange to me: \\nhttp://i.imgur.com/H5n3XdD.png\\nff23 linux\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52176'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393633638, 'spacePHID': None, 'dateCreated': 1373850240, 'dateModified': 1417572588, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51335', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create toolbar icons for bold/italic/underline/superscript/subscript/etc. for scripts/languages as appropriate', 'description': {'raw': \"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.).\\n\\nWe already have https://commons.wikimedia.org/wiki/WikiEditor_Toolbar_Icons#List_by_language -- cannot we use that?\\n\\n----\\n\\nSee also: https://usability.wikimedia.org/wiki/Opinion_Icons\"}, 'authorPHID': 'PHID-USER-7clmfrlb7fwuko4jdjbs', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386877406, 'spacePHID': None, 'dateCreated': 1373799300, 'dateModified': 1695780276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51314', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Templated calls to <references /> (e.g. enwiki's {{reflist}}) don't get updated whilst the user is editing\", 'description': {'raw': \"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, \\n\\nbut ..\\n\\nThe references section at the bottom did not display the reference.\\n\\nSteps 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1434495137, 'spacePHID': None, 'dateCreated': 1373770740, 'dateModified': 1434495137, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51306', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Default insert type for RTL wikis should be thumb|left not thumb|right', 'description': {'raw': '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?\\nThis issue might apply to other elements, such as infobox templates.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374619928, 'spacePHID': None, 'dateCreated': 1373734200, 'dateModified': 1417573081, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51295', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"References inside templates don't appear in the reference list in VisualEditor\", 'description': {'raw': '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.\\n\\nExample articles: [[https://en.wikipedia.org/wiki/Popocatépetl|w:en:Popocatépetl]] and [[East Toowoomba, Queensland]].\\n\\nPossibly related to T52474 and/or T52479\\n\\n**See Also**:\\nT54398\\nT52474\\nT52749\\nT54427\\nT55486\\nT52896'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1434419773, 'spacePHID': None, 'dateCreated': 1373722680, 'dateModified': 1683727021, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51289', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Stronger highlight of selected item in the media inserter dialog', 'description': {'raw': 'From 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377829266, 'spacePHID': None, 'dateCreated': 1373722440, 'dateModified': 1417572935, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51287', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Samsung browser fails the blacklist', 'description': {'raw': 'VisualEditor is disabled on the built-in & default browser, which has the user agent:\\n>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\\n\\n'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1718626061, 'spacePHID': None, 'dateCreated': 1373683500, 'dateModified': 1718626061, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51274', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Support editing <references /> tags to set multi-column display on/off', 'description': {'raw': \"For VisualEditor, we are continuously-bitten by <references /> tags that are embedded within generated content like the English Wikipedia's {{reflist}} (T52769). \\n\\nIt 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 <references /> tag.\\n\\nPoints of agreement include:\\n* The main requirements are for <references /> 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 [[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.\\n\\nThis 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 <references /> tag or by applying CSS classes, which are then given CSS properties on a per-wiki or global level.\\n\\nThis 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.\\n\\n**See Also**: T53145, T8019\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1505846752, 'spacePHID': None, 'dateCreated': 1373662620, 'dateModified': 1576850719, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51260', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove obsolete retry token logic in mw.Target', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376579824, 'spacePHID': None, 'dateCreated': 1373654940, 'dateModified': 1417572947, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51253', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Install Notifications (Echo) on the Polish Wikipedia', 'description': {'raw': \"Please install Notifications (Echo) on the Polish Wikipedia. I think the community supports this in general.\\n\\nIs it even possible? It seems some similar requests were rejected (bug 50064?).\\n\\nI'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\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52510\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377773546, 'spacePHID': None, 'dateCreated': 1373650320, 'dateModified': 1452786861, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51251', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add the capacity for help pages in dialogs', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51798\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403824508, 'spacePHID': None, 'dateCreated': 1373636880, 'dateModified': 1483239034, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51237', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Implement way to round-trip tables with fosterable content that migrates out of the table', 'description': {'raw': \"Simple example:\\n\\n{|\\nfoo\\n|}\\n\\nThis doesn't RT correctly. \\n\\nReal world test case: [[All-Ireland_Senior_Camogie_Championship_1992]]\\nRelated report: https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#A_simple_table_gets_doubled_after_an_unrelated_edit_of_plain_text\\n\\nInterestingly enough, we have more robust handling for templated content.  The example below is handled properly and RTs correctly.\\n\\n{|\\n{{echo|foo}}\\n|}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53402\"}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376526837, 'spacePHID': None, 'dateCreated': 1373603700, 'dateModified': 1377612840, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51217', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Draw VisualEditor's non-CE block highlights using SVG polygons\", 'description': {'raw': \"Shields/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.\\n\\n2. We are limited to a single rectangle per protected node, which for inline elements is especially problematic since they are meant to wrap.\\n\\nUsing 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64709\"}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373579640, 'dateModified': 1650404810, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51202', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Re-enable user preference to disable VisualEditor', 'description': {'raw': 'The user preference for disabling VisualEditor has gone missing. It should be restored.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373557556, 'spacePHID': None, 'dateCreated': 1373556900, 'dateModified': 1373557556, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51179', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Print helpful 'your API is not reachable' message instead of TypeError: Cannot set property '0' of null at Object.WikiConfig\", 'description': {'raw': '**Author:** `stephdechine`\\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 http://localhost:8000/en/Main_Page does not work as expected, and some error messages are thrown out.\\n\\n 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.\\n\\nI fetched the Parsoid extension by using git.\\n\\nI 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.\\n\\nnet-libs/nodejs Installed versions:  0.10.8^t(19:04:51 07/10/13)\\n(masked by default, I unmasked that.)\\n\\nAnd the remaining installation process are with no error.\\n\\nI 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.\\n\\nThat is all I have done to the whole Parsoid.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Linux\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373610519, 'spacePHID': None, 'dateCreated': 1373507520, 'dateModified': 1373610519, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51151', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Newline migration issue', 'description': {'raw': 'As discovered in bug 50120, we need to find out what this is and fix it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373503560, 'dateModified': 1440107033, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51148', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Parsoid's render of {{reflist}} has no context, so no references appear; similarly, edited templates inside structures, look odd on edit\", 'description': {'raw': \"From 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.... \\n\\nEditing 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.\\n\\nThis 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.\\n\\nApologies 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\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373500740, 'dateModified': 1732046247, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51146', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Nicer removal of Cite.php's class=error\", 'description': {'raw': \"Currently this is really ugly; Trevor's better class will help, but in general we want to do this better.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1645470453, 'spacePHID': None, 'dateCreated': 1373497500, 'dateModified': 1645470648, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51141', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Red \"remove xyz\" button may not be ideal styling in dialogs', 'description': {'raw': '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\"\\n\\nI myself wonder if it might not show up as pale grey (hence suggesting it will not work) to the color blind.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393632765, 'spacePHID': None, 'dateCreated': 1373485620, 'dateModified': 1417572589, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51133', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Offer \"cancel\" option in save dialog to escape VisualEditor', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400626382, 'spacePHID': None, 'dateCreated': 1373473020, 'dateModified': 1417572306, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51116', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"[[./Foo]] is not valid wikitext for links and shouldn't be rendered as one\", 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=33094'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397770003, 'spacePHID': None, 'dateCreated': 1373422620, 'dateModified': 1397770003, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51090', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link editor requires ENTER for input', 'description': {'raw': 'On any page, click Link icon\\n\\nEnter text in text field\\n\\nClick the \"<\" symbol\\n\\nCheck the diff or save the page.  \\n\\nThe link is created but the text entered is not preserved.  \\n\\nSuggest 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'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375304913, 'spacePHID': None, 'dateCreated': 1373398440, 'dateModified': 1441912234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51065', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't let the user enter multiple consecutive spaces (except in preformatted blocks), because that's not how HTML works\", 'description': {'raw': \"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 :).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373394900, 'dateModified': 1417808740, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51056', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Provide property \"example\" for template parameters', 'description': {'raw': 'From\\nhttps://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/About_TemplateData\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427404340, 'spacePHID': None, 'dateCreated': 1373390040, 'dateModified': 1660401952, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51049', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: OpenSearch results aren't perfect for checking for page existence\", 'description': {'raw': \"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.\\n\\nThis, along with bug 50898, suggests that the VE team might need to implement its own wrapper web API for link suggestions.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54361\"}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412977342, 'spacePHID': None, 'dateCreated': 1373356200, 'dateModified': 1433607589, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51013', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make defaultsort input field wider', 'description': {'raw': \"To fit long page titles. \\n\\nThere's plenty of empty space in the dialog box that could be put to use.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-evd3wnvnlb66lrwulch4', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395083036, 'spacePHID': None, 'dateCreated': 1373355240, 'dateModified': 1443276385, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Apply changes\" label should be replaced with \"Insert template/reflist\" when inserting template/reflist', 'description': {'raw': '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\".\\n\\nSimilarly, when inserting the list of references, the button should be labeled \"Insert references list\", not \"Apply changes\".\\n\\nIn contrast, when inserting a footnote or media file, the button is correctly labeled \"Insert reference\" or \"Insert media\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394666798, 'spacePHID': None, 'dateCreated': 1373336940, 'dateModified': 1443276389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50998', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: More gracefully handle situations where due to page length/slow client, slowness to load means browser kills VE', 'description': {'raw': 'Splitting from bug 50475 comment 1.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373335140, 'dateModified': 1643977442, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50997', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Double-clicking on a node (image/template/reference/…) should open its dialog', 'description': {'raw': '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.\\n\\nFor 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54827'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395274875, 'spacePHID': None, 'dateCreated': 1373333700, 'dateModified': 1443276389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50996', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace from (or deleteing down) into a DL breaks badly', 'description': {'raw': '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. \\n\\nhttps://en.wikipedia.org/w/index.php?title=Ernestine_Eckstein&oldid=563439288&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50418'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429467886, 'spacePHID': None, 'dateCreated': 1373332680, 'dateModified': 1438734519, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50995', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Display references rendered by {{#tag:ref}} in superscript', 'description': {'raw': \"Screenshot of odd rendering when using {{#tag:ref}}\\n\\nhttps://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet?veaction=edit\\n\\nSee attachment, [11] renders as span instead of as <sup> (like [10]) and as such isn'y styled correctly (text is too big).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11600}\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373993621, 'spacePHID': None, 'dateCreated': 1373316780, 'dateModified': 1417573086, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50978', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide some way of opening external links within templates', 'description': {'raw': \"From 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\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437782973, 'spacePHID': None, 'dateCreated': 1373310540, 'dateModified': 1439331204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50966', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clearer message when cancelling out of active edit', 'description': {'raw': 'An 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'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400137934, 'spacePHID': None, 'dateCreated': 1373301660, 'dateModified': 1443278241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50955', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Handle transclusions within a table better', 'description': {'raw': '**Author:** `adaml`\\n\\n**Description:**\\nWhen 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. \\n\\nIn 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**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50589\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50607'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404172723, 'spacePHID': None, 'dateCreated': 1373299560, 'dateModified': 1443278242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50951', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Hyperlink tool obscures reference box when many options (CSS caching issue?)', 'description': {'raw': 'An editor had an issue on English Wikipedia with the hyperlink tool when used within the reference editor.\\n\\nSpecifically, 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. \\n\\nI reproduced this and took a screenshot. \\n\\nhttp://en.wikipedia.org/wiki/File:VisualEditor_Reference_issue.jpg\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1552091050, 'spacePHID': None, 'dateCreated': 1373294940, 'dateModified': 1552091051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50943', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'User preference to disable VisualEditor', 'description': {'raw': '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:\\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.\\n\\n[1] https://en.wikipedia.org/wiki/Wikipedia:Vpt#.22Opt_out.22_of_VE_needed_under_preferences\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/wiki/Wikipedia:Vpt#.22Opt_out.22_of_VE_needed_under_preferences\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52086'}, 'authorPHID': 'PHID-USER-tyjmn7xcw6s2b6rqagj7', 'ownerPHID': 'PHID-USER-hxjysvdvogekpjub3nd3', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374826648, 'spacePHID': None, 'dateCreated': 1373276400, 'dateModified': 1416216072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50929', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit section links below a diff should point to the rev shown, not the (older) rev the diff compares against', 'description': {'raw': 'See: https://en.wikipedia.org/w/index.php?title=New%20Zealand%20English&diff=0&oldid=123\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/w/index.php?title=New%20Zealand%20English&diff=0&oldid=123'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373328454, 'spacePHID': None, 'dateCreated': 1373273160, 'dateModified': 1417573139, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50925', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Preview the result of the transclusion dialog whilst it\\'s be edited (before \"Apply changes\")', 'description': {'raw': 'Taken 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'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373241780, 'dateModified': 1643977442, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50916', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CE CSS munging issue with specific (highly used) hewiki template', 'description': {'raw': \"Reproduce:\\n\\n1. 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)\\n\\n2. Edit the page. The image is now stretched all across the content area, pushing the text down.\\n\\nThis 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\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50395\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389062817, 'spacePHID': None, 'dateCreated': 1373235720, 'dateModified': 1443276389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50910', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Label the edit summary box as such', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383280539, 'spacePHID': None, 'dateCreated': 1373231700, 'dateModified': 1417572757, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50900', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link dialog lies about existence of page due to case insensitive matching', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52596\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377809024, 'spacePHID': None, 'dateCreated': 1373231160, 'dateModified': 1417572938, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50898', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Ctrl-Alt-s / ⌘-Opt-s should trigger the save dialog, and the save button when inside said dialog', 'description': {'raw': '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.\\n\\nWe could just add ctrl-s/cmd-s to the Save button ?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=38042\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50047'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392849015, 'spacePHID': None, 'dateCreated': 1373228820, 'dateModified': 1443276390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50897', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support editing citations defined within a template', 'description': {'raw': 'For example, look at https://en.wikipedia.org/w/index.php?title=Peach_Springs_Trading_Post&oldid=563257259&veaction=edit.\\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.\"\\n\\nThis 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.\\n\\n**See Also**:\\nT53289'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373224920, 'dateModified': 1722184639, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50896', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspector widget should not stay open when moving the cursor to similar annotation', 'description': {'raw': \"This happens with the Link annotation, but also happened to me with my Language annotation prototype when I play with it.\\n\\nSteps to view the problem:\\n1. Go to some link in the text, put the cursor on it.\\n2. 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.\\n3. 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. \\n\\nI 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.\\n\\n(I hope this makes sense, I can post some screenshots if needed)\\n\\nI use Firefox 22.0 under Ubuntu.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373986645, 'spacePHID': None, 'dateCreated': 1373224800, 'dateModified': 1417573087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50895', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Long editnotices are truncated with no way to scroll', 'description': {'raw': '[[Jyllands-Posten Muhammad cartoons controversy]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51755\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52667'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397067646, 'spacePHID': None, 'dateCreated': 1373199360, 'dateModified': 1443276390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50885', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove the disablement of VisualEditor for redirect pages', 'description': {'raw': 'If you click in the link\\nhttps://en.wikipedia.org/wiki/Math?veaction=edit\\nyou will be redirected to [[Mathematics]] and the VisualEditor will load on that page instead of in the redirect page [[Math]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/wiki/Math?veaction=edit\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54921\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=25470'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392349767, 'spacePHID': None, 'dateCreated': 1373160600, 'dateModified': 1501536259, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50878', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editor not triggered on system redirects', 'description': {'raw': 'If you click in the link\\nhttps://en.wikipedia.org/wiki/Special:MyPage?veaction=edit\\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**: https://en.wikipedia.org/wiki/Special:MyPage?veaction=edit'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400888355, 'spacePHID': None, 'dateCreated': 1373160480, 'dateModified': 1443278242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50877', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Check whether we work in IE11 fine, and if so, add to the whitelist', 'description': {'raw': 'Lots of testing involved here; currently assigning to myself.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434589709, 'spacePHID': None, 'dateCreated': 1373152020, 'dateModified': 1434589737, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50874', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pre-fill the section title in the edit summary when launched from a section edit link', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56891\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51903'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374634478, 'spacePHID': None, 'dateCreated': 1373150220, 'dateModified': 1438194977, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50872', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'mediawiki.notification: Notification area should remain visible when scrolled down', 'description': {'raw': 'Original 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 <h1> heading (the title) and the bubble disappears after about 5s.\\n\\nWhy this is an issue:\\nBut if you have scrolled-down the page, the notification disappears without being read.\\n\\nWhere 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.\\n\\nExpected behaviour:\\nBubble shown, no matter of the current scroll position.\\n\\nPossible implementation:\\nFixed position.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374636514, 'spacePHID': None, 'dateCreated': 1373144520, 'dateModified': 1381254374, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50870', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow launching once per-user, per-situation', 'description': {'raw': \"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\\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.\\n\\nIdeally, it will allow launching immediately, and pre-launching by setting a cookie (we did this once with GettingStarted).\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373067480, 'dateModified': 1653546608, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50847', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Clean up 'cache': 'false'\", 'description': {'raw': \"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.\\n\\nThis seems bad and in need of cleanup. Assigning to Timo.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393640938, 'spacePHID': None, 'dateCreated': 1373062140, 'dateModified': 1417572587, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50840', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: For alienated block nodes in inline positions, alienation area is a single line, not the whole block', 'description': {'raw': 'Take for example this: \\nhttps://en.wikipedia.org/wiki/AMS-LaTeX?veaction=edit\\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}'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1642379773, 'spacePHID': None, 'dateCreated': 1373006760, 'dateModified': 1642381371, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50791', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: We need a representation of red-linked images', 'description': {'raw': '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:\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-3opzim4jsscetzlrotnj', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1431796201, 'spacePHID': None, 'dateCreated': 1373006100, 'dateModified': 1487999636, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50788', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Browser blacklist issues (tracking)', 'description': {'raw': \"Tracking bug for:\\n\\n- Browsers that shouldn't be blacklisted but are;\\n\\n- Browsers that should be blacklisted but aren't.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422424851, 'spacePHID': None, 'dateCreated': 1372987020, 'dateModified': 1718626061, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50781', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Firefox 11 and 12 also need to be blacklisted', 'description': {'raw': '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.\\n\\nReported by user for Firefox 12, and confirmed in crossbrowsertesting.com.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373048811, 'spacePHID': None, 'dateCreated': 1372986900, 'dateModified': 1464692696, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50780', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Deleting a sole LI in front of a GC block doesn't, but selects the GC block\", 'description': {'raw': 'May be dup of 50213? \\n\\nUser:Joe Decker reports:\\n\\nThe 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)\\n\\nReplicated by me.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410034029, 'spacePHID': None, 'dateCreated': 1372980600, 'dateModified': 1417571847, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50779', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add Amazon Silk browser to blacklist', 'description': {'raw': \"Copied 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\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391811891, 'spacePHID': None, 'dateCreated': 1372978080, 'dateModified': 1448998747, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50777', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Alien shield is mis-sized for inline content (assumes it's just one line of text high)\", 'description': {'raw': \"Copied from English Wikipedia:\\n\\nHovering over a displayed math formula in <math> 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\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562893799#Math_tags\\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\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412608037, 'spacePHID': None, 'dateCreated': 1372977300, 'dateModified': 1443278242, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50776', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Moving cursor up or down before a reference behaves as page up/down in Firefox', 'description': {'raw': \"Use Firefox 20 or 21.\\n\\nPlace 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.\\n\\nI don't see this on Safari 6.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53750\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399419638, 'spacePHID': None, 'dateCreated': 1372926900, 'dateModified': 1417572391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50726', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Generated blocks that create images directly aren't converted to use MW's skin\", 'description': {'raw': '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)\\n\\n\\'\\'\\'Steps to reproduce:\\'\\'\\'\\n* Navigate to https://en.wikipedia.org/w/index.php?title=User:Excirial/Playground/Content&oldid=562754871 (Historical revision of my sandbox)\\n* Edit the page in the Visual Editor. You will immediately notice that the template isn\\'t correctly displayed.\\n* Enter the template setting screen and just select \"Apply Settings\".\\n\\nOnce 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ohetl546bwt5ac2szu5w', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1660956979, 'spacePHID': None, 'dateCreated': 1372923480, 'dateModified': 1660956979, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50723', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Separate ve.init and ve.platform', 'description': {'raw': '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.\\n\\n### Goal\\n\\nIntegration 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.\\n\\nThe 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.\\n\\nFor 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). \\n\\n### 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.\\n\\nClass structure:\\n * ve.init.Platform\\n * ve.init.Target.\\n * 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.\\n * ve.init.sa.Target becomes ve.sa.init.Target.\\n * ve.init.mw.Target becomes mw.ve.init.Platform.\\n\\nAlso 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.\\n* Feature detection (ve.support)\\n * `support.es5`\\n * `support.contentEditable`\\n * (maybe)  `support.svg`, since we\\'re currently repeating` ( document.createElementNS && document.createElementNS( \\'http://www.w3.org/2000/svg\\', \\'svg\\' ).createSVGRect` in five places.\\n* Browser sniffing (ve.support.browsers.{whitelist,blacklist})\\n\\n\\n\\nSee also:\\n{T52612}\\n{T75593} (and its dependencies)'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372894740, 'dateModified': 1531936631, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50707', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"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)\", 'description': {'raw': 'I apologize for the lousy name this is starting off with - I have no idea what toc all this.\\n\\nTaken 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.\\n* Click the \"Aristeas and bugonia. Virgil\\'s Georgics. Lyon. 1517\" image, which is about halfway down the article.\\n* There is an uneditable section a bit higher. It starts with the text \"If any further evidence is necessary\". Click that one.\\n* Now click the hyperlink button. A slight white block will appear on the image.\\n* Select any other word in the image and click the hyperlink button.\\n\\nFor 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:\\nhttp://en.wikipedia.org/wiki/File:VisualEditor_-_Hyperlink_Dialog_glitch.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385377902, 'spacePHID': None, 'dateCreated': 1372883940, 'dateModified': 1417572747, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50693', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Init loads oo.js on every page view (before browser blacklist) which throws an error in IE10 + compatibility mode', 'description': {'raw': \"On every page I load on IE10, when switched into compatibility mode, I currently get the following error.\\n\\noo.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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50612\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372901827, 'spacePHID': None, 'dateCreated': 1372872180, 'dateModified': 1417573145, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50677', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Parse wikicode and/or HTML in interface text', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://de.wikipedia.org/w/index.php?title=Vorlage:Normdaten/Doku&diff=120168256&oldid=120165159\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49772\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48451'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372850220, 'dateModified': 1677994578, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50656', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Disable drag-and-drop of non-media content in Firefox until we support that', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49981\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50721'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380437291, 'spacePHID': None, 'dateCreated': 1372836600, 'dateModified': 1417572830, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50643', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Display and let users edit arbitrary HTML anchors, e.g. in section headings', 'description': {'raw': 'Some pages use anchors in the headings - useful for redirected articles.  Can VE display these and make them editable?\\n\\nOriginal request:\\n\\nI 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.\\n\\nYou 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.\\n\\nWhile 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.\\n\\nUbcule (talk) 22:28, 2 July 2013 (UTC)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1425595132, 'spacePHID': None, 'dateCreated': 1372819920, 'dateModified': 1660398890, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50633', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CE eats up syllables except a last syllable of a word in Korean IME', 'description': {'raw': '**Author:** `ryuch`\\n\\n**Description:**\\nKorean input is not complete. \\n\\nI tried to input \"한글 시험 합니다.\". \\nBut it eats up some letters and produce \"글 험 다.\".\\n\\nI tested with Chrome and Safari on Mac OSX. And it is all the same with Chrome on Windows XP.\\n\\n**See Also**: {T52105} {T72353}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-mndznmqvm6ihjfmb6xap', 'dateClosed': 1443085342, 'spacePHID': None, 'dateCreated': 1372815240, 'dateModified': 1465905705, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50631', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Error contacting the Parsoid server\" while editing a section in a diff', 'description': {'raw': 'From 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 http://en.wikipedia.org/w/index.php?title=Baylor_University_Institute_for_Oral_History&diff=555106174&oldid=prev\\nTry to edit the \"Mission\" section in the VE.\\nResult: An error popup stating Error loading data from server: parsoidserver: Error contacting the Parsoid server. Would you like to retry?\\nThis 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373894349, 'spacePHID': None, 'dateCreated': 1372801620, 'dateModified': 1417573088, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50615', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cancelling out of adding a reference adds an empty reference', 'description': {'raw': '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 </re>.  See here:\\nhttps://en.wikipedia.org/w/index.php?title=User:David_Gerard&diff=562600190&oldid=545746964\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52182'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392747780, 'spacePHID': None, 'dateCreated': 1372799760, 'dateModified': 1417572731, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50609', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Templated table cells not rendered properly in VE, but correct in Parsoid output', 'description': {'raw': 'Compare the charts table in \\n\\n* http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29?oldid=561481881\\n* http://parsoid.wmflabs.org/en/2012_%28It_Ain%27t_the_End%29?oldid=561481881\\n* http://en.wikipedia.org/wiki/2012_%28It_Ain%27t_the_End%29?veaction=edit&oldid=561481881\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50951'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404172672, 'spacePHID': None, 'dateCreated': 1372797900, 'dateModified': 1443278246, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50607', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Templates that create multiple table cells don't work\", 'description': {'raw': '**Author:** `kwwilliams`\\n\\n**Description:**\\nVE can\\'t properly display any table using {{singlechart}} on English Wikipedia, which makes any editing of the fields pretty dicey.\\n\\nTaking 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.\\n\\nThis 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.\\n2) Singlechart generates another | between the two data items it outputs to separate the fields in the table row.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50366\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=44498\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50951\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52296'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377030097, 'spacePHID': None, 'dateCreated': 1372780080, 'dateModified': 1377030097, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50589', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reconsider CSS content munging', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429615710, 'spacePHID': None, 'dateCreated': 1372767420, 'dateModified': 1438734526, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50577', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: round-trip adjacent and nested annotations', 'description': {'raw': '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).\\n\\nBoth will lead to a DOM diff and thus likely to a dirty wikitext diff.\\n\\nNote that this only applies to existing content- merging identical annotations in new content is fine.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380845963, 'spacePHID': None, 'dateCreated': 1372734720, 'dateModified': 1417572826, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50549', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': './ still appearing in links.', 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=Russkaya_Mysl&curid=38914039&diff=562427330&oldid=555891306\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50720'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373020641, 'spacePHID': None, 'dateCreated': 1372724400, 'dateModified': 1373020641, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50539', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Permit removal of parent template while retaining subtemplate', 'description': {'raw': '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.\\n\\nRealizing this is not likely to be a high priority, given more urgent issues, just putting in the request. :)\\n\\nSee\\nhttp://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=562454889#Can.27t_unwrap_template_within_template\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372715400, 'dateModified': 1643977443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50526', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Complete and document VisualEditor's integration and plugin system\", 'description': {'raw': '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.\\n\\nEnjoy.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372706340, 'dateModified': 1643977443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50514', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Close icon shown at 2x size and so truncated', 'description': {'raw': 'Screenshot\\n\\nSee screenshot - monobook, windows 7, firefox 22.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11469}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377830355, 'spacePHID': None, 'dateCreated': 1372699920, 'dateModified': 1417572935, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50508', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Share ref / references re-rendering code with Parsoid', 'description': {'raw': '>>! In T52505#562403, @GWicke wrote:\\n> 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.\\n\\n--------------------------\\n\\n**See Also**:\\n{T52474}'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1578935420, 'spacePHID': None, 'dateCreated': 1372698960, 'dateModified': 1578935420, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50505', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link input widget is not oriented for RTL', 'description': {'raw': \"A 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.\\n\\nThe arrow icon is supposed to point to the right, and be placed in the right corner, separated by a vertical line.\\n\\nThe title is supposed to be aligned to the right.\\n\\nThe chain icon is supposed to be next to the title on its left side.\\n\\nThe trash bin is supposed to be in the left corner.\\n\\nSee 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).\\n\\nThis bug is similar to bug 49613.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n//attachment link-inspector-rtl.png ignored as obsolete//\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374495347, 'spacePHID': None, 'dateCreated': 1372670160, 'dateModified': 1417573082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50490', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: <u><u> created, and meta-data removed, from [[Bahá'u'lláh]] on edit\", 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Bah%C3%A1%27u%27ll%C3%A1h&diff=562302216&oldid=561967071 - finding out browser/OS now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372631880, 'dateModified': 1420844132, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50481', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: More gracefully handle situations where Parsoid returns a timeout failure code (HTTP 504)', 'description': {'raw': '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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=39057'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394672264, 'spacePHID': None, 'dateCreated': 1372620960, 'dateModified': 1443276398, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50475', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'In VisualEditor, references in templates cannot be reused and are numbered separately from references in the text.', 'description': {'raw': '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 [[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. \\n\\n**See Also**:\\n{T52505}\\n{T53289}\\n{T54398}\\n{T55777}\\n{T54262}\\n\\nPossible duplicate but might have additional implications: \\n{T87134}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372620660, 'dateModified': 1723756941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50474', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cut-and-paste swap of reference list creates massive content duplication, pawns (♙) and snowmen (☃) galore', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51677\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378550137, 'spacePHID': None, 'dateCreated': 1372612320, 'dateModified': 1417572838, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50465', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: One should be able to select (and copy) the text of an edit notice', 'description': {'raw': \"When a notice is shown (on beta), it's not possible for the user to mark the text and copy.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383280412, 'spacePHID': None, 'dateCreated': 1372555020, 'dateModified': 1417572817, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50442', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog should truncate spaces from parameter input', 'description': {'raw': '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.\\n\\nExample 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**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61049'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414004857, 'spacePHID': None, 'dateCreated': 1372554420, 'dateModified': 1423675689, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50439', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Creating TemplateData blocks should be direction neutral', 'description': {'raw': 'This is a bug/design issuse with TemplateData.\\n\\nTo use TemplateData in RTL wikis, the syntax mix English and Arabic/Hebrew (etc).\\n\\nEditing 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).\\n\\nExample :\\n<templatedata>\\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</templatedata>\\nIt is very hard to edit such syntax as above. (<templatedata> 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).\\n\\nSee 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).\\n* bug 50370 - translation of interface items\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50370'}, 'authorPHID': 'PHID-USER-cfsvvgbtlqnbt2yokfjf', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415310061, 'spacePHID': None, 'dateCreated': 1372540320, 'dateModified': 1415310061, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50436', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Wikitext list after implicit <td> not properly recognized', 'description': {'raw': \"I did not add this to closed bug 50012 because while it may be related it's not exactly the same.\\n\\nThis 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 (|}|}|}|}|}|})\\n\\nSee http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Unwanted_format_changes_throughout_article\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372829597, 'spacePHID': None, 'dateCreated': 1372512240, 'dateModified': 1372829597, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50420', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference list display being cut off in some pages', 'description': {'raw': 'Screenshot, 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11283}'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377828038, 'spacePHID': None, 'dateCreated': 1372468740, 'dateModified': 1417572936, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50411', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"TypeError: focusedNode is null\" thrown when applying a link to a template', 'description': {'raw': 'Creating a template entry, marking it and click on \"Link\" button results in following error (twice in a row):\\n\\nTypeError: focusedNode is null\\nhttps://bits.wikimedia.org/static-1.22wmf9/extensions/VisualEditor/modules/ve/ui/ve.ui.Context.js\\nLine 260\\n\\nVE is in a bad state after this cannot access template edit at all after this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384202462, 'spacePHID': None, 'dateCreated': 1372462920, 'dateModified': 1417572816, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50406', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Behaviour of default \"Edit\" tab should not vary by namespace (action=edit vs. veaction=edit)', 'description': {'raw': '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\".\\n\\nSince 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).\\n\\nVE 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.\\n\\n\\nThis 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.\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50424'}, 'authorPHID': 'PHID-USER-v3yn5qf233ggnnnmvejc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375423094, 'spacePHID': None, 'dateCreated': 1372459800, 'dateModified': 1417572952, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50402', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it\", 'description': {'raw': 'Try editing the professional ratings template in https://en.wikipedia.org/wiki/All_6%27s_and_7%27s?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50551\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50910\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51708'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1554826913, 'spacePHID': None, 'dateCreated': 1372453440, 'dateModified': 1554826913, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50395', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Do not add size for standard thumbnail images when inserting them', 'description': {'raw': 'Wikicode for inserting animage in a standard ways into Wikipedia: \\n\\n[[File:Name.jpg|thumb|Text]] without any size.\\n\\nVE adds a fixed size of 225x225px (why these numbers?) to the wikicode which is wrong for most Wikipedias.\\n\\nThe size of a standard thumbnail depends on $wgThumbLimits and $wmgThumbsizeIndex or the size set in the user preference.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://fr.wikipedia.org/w/index.php?title=Yael_Bartana&diff=94503286&oldid=90892725\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=47804'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393446774, 'spacePHID': None, 'dateCreated': 1372429740, 'dateModified': 1444199698, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50379', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Updated TemplateData from transcluded items take a long time to show up', 'description': {'raw': 'TemplateData from transcluded items (i.e. doc pages) takes a long time to show up in the API. \\n\\nA 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. \\n'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'stalled', 'name': 'Stalled', 'color': 'yellow'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372421640, 'dateModified': 1713637244, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50372', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Section edit links disappear following an unclosed {{', 'description': {'raw': \"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.\\n\\nFor a reduced testcase see <https://test.wikipedia.org/wiki/Section_edit_links_bug2>. 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).\\n\\nSorry I can't be more specific.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=73182\"}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372420380, 'dateModified': 1647381996, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50369', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Templates that create part (but not all) of a table cell don't work\", 'description': {'raw': 'Screenshot\\n\\nSee screenshot; Windows 7, Firefox 21.0, on https://en.wikipedia.org/wiki/Rage_Against_the_Machine?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50589\\n\\n**Attached**: {F11166}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374455443, 'spacePHID': None, 'dateCreated': 1372417680, 'dateModified': 1374455443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50366', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Hatnote templates not displaying properly', 'description': {'raw': 'How 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.\\n\\nAs 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}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375118083, 'spacePHID': None, 'dateCreated': 1372416900, 'dateModified': 1417572958, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50363', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: backspacing sometimes inserts a breaking space', 'description': {'raw': \"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\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1562866092, 'spacePHID': None, 'dateCreated': 1372414260, 'dateModified': 1562866092, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50358', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add support for editing templates\\' parameters as DOM elements (\"visually\"), including supporting nested templates', 'description': {'raw': 'Many templates serve merely as wrapper around free-form wikitext content. TemplateData specifies the parameter type \"content\" for this purpose.\\n\\nThis 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.\\n\\nUse cases:\\n* Wrap-templates. Such as message boxes, and the parameter-consuming variants of the \"something-start\"/\"something-end\" templates.\\n* Nested infoboxes.\\n* Simple infobox fields that support text but allow/encourage use of inline templates for formatting. Currently these expose raw wikitext to end-users.\\n\\n>>! @Ironholds wrote\\n> 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.\\n\\n'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372412940, 'dateModified': 1722927064, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50355', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog should make it easier to add parameters and see other values', 'description': {'raw': \"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.\\n\\nIt'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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51774\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49772\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377906050, 'spacePHID': None, 'dateCreated': 1372412100, 'dateModified': 1449525449, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50354', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add a block slug at the end of pages', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1423750227, 'spacePHID': None, 'dateCreated': 1372411380, 'dateModified': 1423750227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50353', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Title is not updated on save if DISPLAYTITLE changed', 'description': {'raw': '1. 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.\\n\\nExpected to see \"displaytitle\" in italics. This is what you see when you refresh the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49667'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404250963, 'spacePHID': None, 'dateCreated': 1372389360, 'dateModified': 1443278246, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50341', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page\", 'description': {'raw': 'Using ctrl-click (but not middle-click) on a \"content editable\" link, does not currently work with Chromium37, but does work with Firefox39.\\nUsing 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.\\n\\n(Prior description had different results for Firefox 22.\\nEd notes below, that this is all browser-specific behaviour, and rather than overriding that, we should just solve {T56759} (Done))\\n\\nSee also: {T52741}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1438983806, 'spacePHID': None, 'dateCreated': 1372367280, 'dateModified': 1441911419, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50321', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: VE won't load on empty page containing only a magic word\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373905170, 'spacePHID': None, 'dateCreated': 1372344120, 'dateModified': 1417573091, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50289', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Empty transclusion editor is empty, needs some kind of reassuring message', 'description': {'raw': '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?)\\n\\nThere 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'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-5jrv5iukbhgvtdchqmrt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427406351, 'spacePHID': None, 'dateCreated': 1372335660, 'dateModified': 1427673038, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50281', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link input widget outwits itself with the leading colon for Category/file links', 'description': {'raw': '1. 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\").\\n\\nProbably, the link inspector should be ignoring/stripping the preceding colon when checking whether the page exists.\\n\\nSame thing for links to File: pages.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403746179, 'spacePHID': None, 'dateCreated': 1372331940, 'dateModified': 1441912252, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50279', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: enwiki template {{columns-list}} looks particularly-broken at high zoom/low width', 'description': {'raw': \"Screenshot\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11863}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404168653, 'spacePHID': None, 'dateCreated': 1372302300, 'dateModified': 1424710735, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50269', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Let users relabel (or renumber if auto-numbered) parameters in the transclusion dialog', 'description': {'raw': 'See the report at https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Failed_attempt_to_use_VE_to_remove_a_template_parameter\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372302060, 'dateModified': 1643977443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50268', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: User personal links appear above VE dialogs', 'description': {'raw': '**Author:** `rachelqa99`\\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'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373077152, 'spacePHID': None, 'dateCreated': 1372267920, 'dateModified': 1417573142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50247', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Have the link inspector inform users if they're linking to a disambiguation or redirect page, or reinserting the same link\", 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50160\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=59208\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49502\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391818637, 'spacePHID': None, 'dateCreated': 1372262940, 'dateModified': 1486157051, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50240', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: migrate qunit jobs from master to gallium', 'description': {'raw': 'The Qunit jobs are currently running on the master, they need to be moved to\\ngallium slave nodes.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373031803, 'spacePHID': None, 'dateCreated': 1372254900, 'dateModified': 1373031803, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50231', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Non-primary edit tab <li> should have class=\"collapsible\"', 'description': {'raw': 'Screenshot: 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.\\n\\nThe \"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).\\n\\nIt 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11766}'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396642509, 'spacePHID': None, 'dateCreated': 1372251780, 'dateModified': 1443276399, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50225', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Middle-clicking/Ctrl+clicking on wikilinks fails when using full index.php URL', 'description': {'raw': '1. Go to http://en.wikipedia.org/w/index.php?title=Black&veaction=edit\\n2. Middle-click or ctrl+click on any wikilink\\n\\nYou get a 404 page, e.g. http://en.wikipedia.org/w/Outer_space\\n\\nVE should use fully qualified hrefs (/wiki/foo), just as MW always does.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372270074, 'spacePHID': None, 'dateCreated': 1372231980, 'dateModified': 1417573097, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50216', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Possible to have links nested inside links', 'description': {'raw': '(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!)\\n\\n1. 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.\\n\\n5. Save page > Review changes\\n\\nWikitext output has two links side-by-side, pointing to the same target.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372260507, 'spacePHID': None, 'dateCreated': 1372220460, 'dateModified': 1417573157, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50208', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make ve.ui.PopupWidget#display signature not insane', 'description': {'raw': '3 parameters is the limit, 6 is crazy.\\n\\nve.ui.PopupWidget.prototype.display = function ( x, y, width, height, transition, embedded ) {\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412209365, 'spacePHID': None, 'dateCreated': 1372192080, 'dateModified': 1417571699, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50197', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add support for making some templates directly \"visually editable\" in the DOM, as if they were tables (e.g. infoboxes)', 'description': {'raw': \"screenshot of nested templates in VisualEditor\\n\\nTemplates 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.\\n\\nVisualEditor 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F11704}\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372175760, 'dateModified': 1716418601, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50182', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: {{NAMESPACE}} not running in context so doesn't know what namespace you're in\", 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397880064, 'spacePHID': None, 'dateCreated': 1372164120, 'dateModified': 1444199687, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50172', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Re-label the group UI element in the reference dialog to explain what it does', 'description': {'raw': 'In 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.\\n\\nSomething simpler, like \"Reference name (optional)\" and \"Reference group (optional)\" could be better. \\n\\nSame 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'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372162920, 'dateModified': 1643977443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support unicode equivalence for client side text searches', 'description': {'raw': 'Planned features, such as searching for an existing reference by content, will require us to implement some http://en.wikipedia.org/wiki/Unicode_equivalence .\\n\\nWe 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\\'.\\n\\nhttps://github.com/walling/unorm looks like a good library for the job. We may want to fork it into UnicodeJS.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372158120, 'dateModified': 1643977443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50167', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't copy/paste header from start of document without losing formatting\", 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1521857381, 'spacePHID': None, 'dateCreated': 1372102560, 'dateModified': 1522075401, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50126', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Uses of enwiki's {{Plain image with caption}} cause alt text to be displayed as a caption\", 'description': {'raw': 'See https://en.wikipedia.org/wiki/Chloroplast?veaction=edit for example.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372120126, 'spacePHID': None, 'dateCreated': 1372091520, 'dateModified': 1372120126, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50113', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deletion across a header caused it to remain without WS, leading Parsoid to output \"==<nowiki/>==\"', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=AES11&diff=prev&oldid=561340674\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\n{T57769}\\n{T61647}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429293419, 'spacePHID': None, 'dateCreated': 1372085880, 'dateModified': 1429330072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50100', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Use [[ as a 'hotkey' trigger for opening the 'create a link' dialog\", 'description': {'raw': \"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.\\n\\nInstead 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.\\n\\nThese 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416971243, 'spacePHID': None, 'dateCreated': 1372078500, 'dateModified': 1438734530, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50093', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reflist columns parameter getting ignored/changed for display', 'description': {'raw': 'Compare the number of columns in https://en.wikipedia.org/wiki/Kartik_Poornima in read and VEdit mode.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373929765, 'spacePHID': None, 'dateCreated': 1372035540, 'dateModified': 1417573089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50075', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: clicking on a template in the reference inspector causes odd blue shadowing', 'description': {'raw': 'Screenshot\\n\\nSee screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49818\\n\\n**Attached**: {F11448}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372118661, 'spacePHID': None, 'dateCreated': 1372035240, 'dateModified': 1417573097, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50074', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Unreferenced section template not displaying properly', 'description': {'raw': 'See screenshot; problem with the template or with the parsing of it?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373155344, 'spacePHID': None, 'dateCreated': 1372033980, 'dateModified': 1373155344, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50069', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff', 'description': {'raw': '...and quite dramatically - take a look at https://en.wikipedia.org/w/index.php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nT50830'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1642380969, 'spacePHID': None, 'dateCreated': 1371995700, 'dateModified': 1642380969, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50052', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Set $wgWellFormedXml = false by default', 'description': {'raw': 'The main reason for this still being true was screen-scraping bots (together with $wgHtml5).\\n\\nFor some reason when $wgHtml5 was finally enabled we forgot to also get rid of wgWellFormedXml=true.\\n\\nWe should disable it by default for the same reason we now enable wgHtml5 by default.\\n\\nThis 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\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375143938, 'spacePHID': None, 'dateCreated': 1371977520, 'dateModified': 1468992024, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50040', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: cannot reposition typing cursor using the mouse in edit summary', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372007051, 'spacePHID': None, 'dateCreated': 1371896940, 'dateModified': 1417573073, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50014', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make defaultsort input field always use \"real\" text, not a placeholder', 'description': {'raw': 'From [[Wikipedia:VisualEditor/Feedback#Editing_Defaultsort]]:\\n\\n> 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.\\n> \\n> This is because the default defaultsort value (article title) is implemented as \"placeholder\" text. Instead, it should be normal editable text.\\n> \\n> 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\".'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1540933484, 'spacePHID': None, 'dateCreated': 1371864600, 'dateModified': 1540933484, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50002', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Drag-and-drop of content (text, transclusions, references, …) to move it', 'description': {'raw': 'More general bug, following on from bug 41150 - this is for text selections, for other generated content blocks, ? others.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50643'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403055832, 'spacePHID': None, 'dateCreated': 1371851820, 'dateModified': 1443278251, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49981', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Closing a dialog scrolls you up to the top of the document', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372264572, 'spacePHID': None, 'dateCreated': 1371844500, 'dateModified': 1417573157, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49977', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE not detecting colour/boxing around multiple issues template', 'description': {'raw': 'See https://en.wikipedia.org/wiki/Virivilai for example - bug with the VE or bug with the template?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373160219, 'spacePHID': None, 'dateCreated': 1371833340, 'dateModified': 1417573141, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49968', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Saving or closing the editing pane does not restore the default view of the article', 'description': {'raw': \"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.\\n\\n(sorry if this sounds nonsensical; it's difficult to explain at this end).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399325038, 'spacePHID': None, 'dateCreated': 1371829500, 'dateModified': 1417572393, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49964', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide a neater way to edit transclusions that do not take a pipe (e.g. {{formatnum:…}}, {{lc:…}}, {{int:…}}, {{#dateformat:…}}})', 'description': {'raw': \"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'.\\n\\nThe editor should allow changing the number without having to remove the 'template'.\\n\"}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371816900, 'dateModified': 1706714108, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49954', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Window title for \"Creating\" should support parser functions', 'description': {'raw': '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.\\n'}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1428960831, 'spacePHID': None, 'dateCreated': 1371806460, 'dateModified': 1428960848, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49951', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Edit\" should load the latest version without hardcoding the \"current\" revision id (due to race condition and cache)', 'description': {'raw': 'Steps 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).\\n\\nActual result: VE happily edits the old revision, and shows [[MediaWiki:Editingold]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-a6p24cvyblhfzc7we7nc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373334098, 'spacePHID': None, 'dateCreated': 1371799440, 'dateModified': 1417573139, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49943', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid not correctly rendering bold/italic text', 'description': {'raw': 'See, for example, the lead of https://en.wikipedia.org/wiki/Flaming_Pie in the VisualEditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377546664, 'spacePHID': None, 'dateCreated': 1371789600, 'dateModified': 1377546664, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49926', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Refactor dialog to not need hardcoded padding for each subclass', 'description': {'raw': \"e.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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1530904214, 'spacePHID': None, 'dateCreated': 1371780960, 'dateModified': 1530904214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49924', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Rename internal use of \"Reference list\" to \"References list\"', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408586995, 'spacePHID': None, 'dateCreated': 1371780900, 'dateModified': 1443278251, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49923', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'monitor mediawiki extensions superproject misconfiguration', 'description': {'raw': '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).\\n\\nIt would be nice to run a SQL query daily that would mail gerritadmin about any misconfiguration.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389653066, 'spacePHID': None, 'dateCreated': 1371759600, 'dateModified': 1389653066, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49906', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid should have template parameter key/value whitespace of \" = \" not \"=\"', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372007229, 'spacePHID': None, 'dateCreated': 1371753840, 'dateModified': 1372007229, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49901', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion editor shows empty \"content\" sections for newlines', 'description': {'raw': '1. 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393526293, 'spacePHID': None, 'dateCreated': 1371722040, 'dateModified': 1417572591, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49866', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images: New images get a link=… set whether or not they need it', 'description': {'raw': \"Follow-on from bug 49596.\\n\\nThe insertion of a new image adds link=… whether or not it's been actively set away from the default.\\n\\nThus (in the example in bug 49596 comment 0) we get:\\n\\n[[File:CV.03326.jpg|link=https://commons.wikimedia.org/wiki/File:CV.03326.jpg|right|framed|424x275px]]\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395180712, 'spacePHID': None, 'dateCreated': 1371681900, 'dateModified': 1395180712, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49844', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Quick transclusion dialog UX improvements', 'description': {'raw': 'Template 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**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52576'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377905614, 'spacePHID': None, 'dateCreated': 1371667800, 'dateModified': 1417572932, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49833', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Infobox is duplicated and duplicate is substed', 'description': {'raw': \"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:\\nhttps://fr.wikipedia.org/w/index.php?diff=94112508\\nhttps://fr.wikipedia.org/w/index.php?diff=94163787\\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\"}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373519486, 'spacePHID': None, 'dateCreated': 1371653940, 'dateModified': 1425508820, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49823', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Hidden templates should display as an icon in-page in VisualEditor so they can be interacted with (e.g. a puzzle piece?)', 'description': {'raw': '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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49603\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53659'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1425595037, 'spacePHID': None, 'dateCreated': 1371640200, 'dateModified': 1660398890, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49806', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion nodes should re-evaluate their block/inline status on every update', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1463387195, 'spacePHID': None, 'dateCreated': 1371595680, 'dateModified': 1463389222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49784', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template dialog should look up TemplateData for newly-added templates', 'description': {'raw': \"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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372553711, 'spacePHID': None, 'dateCreated': 1371592380, 'dateModified': 1417572933, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49778', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Images, when resized, appear on top of (rather than underneath) other UI elements', 'description': {'raw': 'Screenshot\\n\\nSee associated screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11694}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372016119, 'spacePHID': None, 'dateCreated': 1371583860, 'dateModified': 1417573199, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49767', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide an easy way to sanity-check VE input / output behavior', 'description': {'raw': '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. \\n\\nWe 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.\\n\\nThis would at least allow basic manual debugging.\\n\\nOptionally, 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371579720, 'dateModified': 1643977443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49761', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Rename [big|small]Stack variables in ve.dm.Surface', 'description': {'raw': 'To something which describes their function, not form.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386737312, 'spacePHID': None, 'dateCreated': 1371571320, 'dateModified': 1417572930, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49754', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: You can't select text in the save dialog\", 'description': {'raw': \"You really should be able to. I mean, the cursor pointer triggers and everything. Tsk.\\n\\n(Actually, it's ignoring all clicks that aren't on the buttons, or so it seems.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371775703, 'spacePHID': None, 'dateCreated': 1371521220, 'dateModified': 1417573205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49725', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link duplicated', 'description': {'raw': 'Screenshot\\n\\nSee associated screenshot, from the page https://en.wikipedia.org/wiki/Henkle_v._Gregory\\n\\nReproduced in Chrome, Safari and Firefox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11483}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372863371, 'spacePHID': None, 'dateCreated': 1371465120, 'dateModified': 1417573148, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49682', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting the slug a floated image appears in deletes the image… but retains the caption as a paragraph', 'description': {'raw': 'Deleting 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://test.wikipedia.org/w/index.php?title=User:Raymond/image&diff=174494&oldid=174493'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383957760, 'spacePHID': None, 'dateCreated': 1371404760, 'dateModified': 1417572931, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49645', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add support for (the equivalent of?) editintro and preload', 'description': {'raw': \"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.\\n\"}, 'authorPHID': 'PHID-USER-cfsvvgbtlqnbt2yokfjf', 'ownerPHID': 'PHID-USER-hdkktg27rkwebepkv6yw', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1506351148, 'spacePHID': None, 'dateCreated': 1371315660, 'dateModified': 1714836949, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49622', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Section edit links opens the source editor after saving the section using the visual editor', 'description': {'raw': 'To reproduce:\\n\\n1. Open a page with several sections.\\n2. 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.\\n3. Press the same \"edit\" link again.\\n\\nObserved: The source editor opens.\\n\\nExpected: The visual editor opens.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372109956, 'spacePHID': None, 'dateCreated': 1371313740, 'dateModified': 1417573141, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49620', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"View source\" is missing on protected LQT pages', 'description': {'raw': 'As indicated on\\n[[mw:Thread:VisualEditor/Feedback/source code?]]\\nthe page\\nhttps://www.mediawiki.org/wiki/VisualEditor/Feedback\\nwhich was protected recently has no \"View source\" link to see the content of the header. There should be one, pointing to\\nhttps://www.mediawiki.org/wiki/VisualEditor/Feedback?action=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376116339, 'spacePHID': None, 'dateCreated': 1371298920, 'dateModified': 1402294684, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49618', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Visually discourage use of \"legal\" but unwanted structures in sub-editors (e.g. lists in references)', 'description': {'raw': '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.\\n\\nThis is a nonsensical capability. The only required formatting here is bold, italic and wikilink, if that.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52646'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371297660, 'dateModified': 1643977443, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49617', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Run an A/B split test for VisualEditor enabled by default on enwiki for new accounts', 'description': {'raw': \"This is to run from 19 June (end on with the Notifications split test, so we don't much their data up).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/70737\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49727\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372093892, 'spacePHID': None, 'dateCreated': 1371261480, 'dateModified': 1372257598, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49604', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show VisualEditor tag in diffs', 'description': {'raw': \"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).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373486407, 'spacePHID': None, 'dateCreated': 1371258900, 'dateModified': 1373582616, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49602', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make ULS input methods work in content editable divs of VisualEditor', 'description': {'raw': 'ULS IME not working with Visual Editor fields\\n\\n--------------------------\\n**Version**: master\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50722\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53700\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53701\\nhttps://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/3493'}, 'authorPHID': 'PHID-USER-4jecvpv4h62htut6pxez', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453749464, 'spacePHID': None, 'dateCreated': 1371201120, 'dateModified': 1660398890, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49569', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Review behaviour in CE with <p><br /></p>s', 'description': {'raw': 'Need to review and get working so we can ask Parsoid to re-enable these (stop them being wrapped as <mw:Placeholder>s) - bug 47403 comment 3.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371181020, 'dateModified': 1416846547, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49564', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: UI loading should trigger events that other tools can listen for', 'description': {'raw': \"I'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. https://en.wikipedia.org/wiki/Wikipedia:Editnotice#Edit_intros\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371162780, 'dateModified': 1643977444, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49552', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't paste into a selection covering the end of the document\", 'description': {'raw': '1. 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!\\n\\nProblem 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'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371233886, 'spacePHID': None, 'dateCreated': 1371162120, 'dateModified': 1433959742, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49551', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Dialogs are quite big, maybe they could be smaller', 'description': {'raw': 'It should allow the editor to see the page content while specifying a reference.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49969\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51755'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399324736, 'spacePHID': None, 'dateCreated': 1371158700, 'dateModified': 1417572394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49549', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: z-index for .ve-ui-surface-overlay is too high (and we shouldn't use them anyway)\", 'description': {'raw': \"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).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416502788, 'spacePHID': None, 'dateCreated': 1371107160, 'dateModified': 1417571674, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49514', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog for objects without params should give you some clue as to what to do', 'description': {'raw': 'Screenshot\\n\\nAn 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\\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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11046}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371437544, 'spacePHID': None, 'dateCreated': 1371060180, 'dateModified': 1417573211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49491', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Whitespace-only headings should be collapsed to (blank) paragraphs', 'description': {'raw': 'When an editor tried to remove a heading, the following empty h3 tag seems to have been left behind:  <h3 data-parsoid=\\'{\"dsr\":[4514,4534,3,3]}\\'></h3>\\n\\nSerializes to ===<nowiki/>=== and the user complained about it.\\n\\nFrom 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'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1428879414, 'spacePHID': None, 'dateCreated': 1370981700, 'dateModified': 1428895565, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Grunt leaves behind temporary html file if tests fail', 'description': {'raw': 'modules/ve/test/index-phantomjs-tmp.html is not deleted if the tests fail.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371495128, 'spacePHID': None, 'dateCreated': 1370954520, 'dateModified': 1417573210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49431', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding a new heading should add a newline before the heading too', 'description': {'raw': 'I think it is standard in in (all?) Wikipedias to add a newline before adding a new heading.\\n\\nThis is currently not done by the VisualEditor, see URL.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://de.wikipedia.org/w/index.php?title=Benutzer:Raymond/heading&diff=119444892&oldid=119444326'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1370952120, 'dateModified': 1643977444, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Default whitespace for headings should have two new lines beforehand (i.e., one blank line before a heading)', 'description': {'raw': 'Steps to reproduce:\\n\\n1. Go into a heading\\n\\n2. Change heading level from 2 to 3 (i.e.)\\n\\nExpected 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://de.wikipedia.org/w/index.php?title=Benutzer:Raymond/heading&diff=119444161&oldid=119444142'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372103155, 'spacePHID': None, 'dateCreated': 1370950980, 'dateModified': 1372103155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49428', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Rendering of categories fails on first load sometimes in Chrome (Webkit?)', 'description': {'raw': '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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1493662142, 'spacePHID': None, 'dateCreated': 1370912280, 'dateModified': 1493662142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49420', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Images: Handle templated image options containing pipes', 'description': {'raw': 'Some perverse templates such as {{Largethumb}} return a string with several options separated by pipes (\"thumb|<number>px\"). In the PHP parser those pipes are then picked up by the link regexp, so result in the regular image options.\\n\\nIn 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.\\n\\nWe 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1586539013, 'spacePHID': None, 'dateCreated': 1370889600, 'dateModified': 1586539013, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49400', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Misc. issues', 'description': {'raw': \"https://en.wikipedia.org/w/index.php?title=Mavericks_(location)&diff=559262706&oldid=559261658\\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 <nowiki> 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.\\n\\nI'm not sure how these issues should be split out or if there are existing bug reports for all three of these issues.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=visualeditor\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371227728, 'spacePHID': None, 'dateCreated': 1370887500, 'dateModified': 1371227728, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49394', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '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.)', 'description': {'raw': 'There are a couple of ways to configure references to display differently:\\nhttp://www.mediawiki.org/wiki/Extension:Cite/Cite.php#Set_references_to_use_.5E_and_letters_like_Wikipedia\\nwe should access these so the rendering in edit mode is consistent with the that in read mode.\\n'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1370728680, 'dateModified': 1555009533, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49346', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create Wikipedia Tuvan', 'description': {'raw': 'The language committee and WMF Board have approved the creation of Wikipedia Tuvan.\\n\\nLanguage code: tyv\\nSite URL: tyv.wikipedia.org\\nProject name: Википедия\\nProject namespace: Википедия\\nProject talk namespace: Википедия дугайында сүмелел\\nProject logo: http://commons.wikimedia.org/wiki/File:Wikipedia-logo-v2-tyv.png\\nTimezone: Asia/Krasnoyarsk\\nLanguage name: Тыва дыл\\nEnable uploads: yes\\n\\n\\nThank you.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**URL**: //meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Tuvan'}, 'authorPHID': 'PHID-USER-7e4yonmruupxzg23swum', 'ownerPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376684880, 'spacePHID': None, 'dateCreated': 1370654940, 'dateModified': 1503509410, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49328', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Sometimes ignores changing a wikilink with an underscore to one with a space', 'description': {'raw': '**Author:** `the.anonymouse.wikimedia`\\n\\n**Description:**\\nI 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].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=42140'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402688105, 'spacePHID': None, 'dateCreated': 1370622300, 'dateModified': 1417572218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49310', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Images' selection blocks can overlap the toolbar and prevent saving/etc.\", 'description': {'raw': '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}'}, 'authorPHID': 'PHID-USER-pts53ljtnbn3jhkllas6', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373649909, 'spacePHID': None, 'dateCreated': 1370617380, 'dateModified': 1417573094, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49308', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide full grapheme cluster boundary detection', 'description': {'raw': 'Per Ed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371423759, 'spacePHID': None, 'dateCreated': 1370532360, 'dateModified': 1417573211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49257', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Review your changes\" - cancel-arrow needs a tooltip; possibly replace with an \"X\"?', 'description': {'raw': '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. \\n\\nI suggest: \"Cancel review, go back to current edit\" or similar.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F11244}'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395021940, 'spacePHID': None, 'dateCreated': 1370371920, 'dateModified': 1417572566, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49147', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Use figure and figcaption HTML5 elements when possible', 'description': {'raw': 'Since MediaWiki allows images that are clearly separated out, we should see if we can use `<figure>` and `<figcaption>`.  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.\\n\\nThe 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 `createElement(tagName)` once for each of the relevant tag names.\\n\\nFor issue number 2, I think jQuery\\'s internal `createSafeFragment` already takes care of old IE.  So only the styling issue remains.\\n\\n--------------------------\\nSee also: {T25932}'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1689005142, 'spacePHID': None, 'dateCreated': 1370315820, 'dateModified': 1689005142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49097', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reference lists should update more intelligently (i.e. less often)', 'description': {'raw': \"Currently a reference list (<references /> 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.\\n* 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.\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1370299680, 'dateModified': 1434413967, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49092', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor alpha on all Wikipedias', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370741034, 'spacePHID': None, 'dateCreated': 1370286120, 'dateModified': 1370741034, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49089', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Phantoms appear above edit notices', 'description': {'raw': \"Even though the edit notices appear above text, they don't appear above overlays, e.g. block phantoms.\\n\\nhttp://i.imgur.com/RAOdlIZ.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49361\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50096\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50545\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372809190, 'spacePHID': None, 'dateCreated': 1370181480, 'dateModified': 1417573148, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49059', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Piping used unnecessarily when modifying an existing link', 'description': {'raw': \"I edited https://en.wikipedia.org/w/index.php?title=Eagle_Lake_%28Florida%29&oldid=557775556 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]].\\n\\n(irrelevant parts after omitted).\\n\\nIt should just be:\\n\\n[[Eagle Lake, Florida]]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370467151, 'spacePHID': None, 'dateCreated': 1370056740, 'dateModified': 1370467182, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49034', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Incorrect tab text (create vs. edit) shown on Special:MovePage, Special:Undelete, others?', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66885'}, 'authorPHID': 'PHID-USER-kc6qx3zohjybu3nzffu3', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393380862, 'spacePHID': None, 'dateCreated': 1369958460, 'dateModified': 1417572139, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Formatting styles drop down menu rendered behind the page title', 'description': {'raw': '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\\n\\nhttp://i.imgur.com/O3OvK3w.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370632871, 'spacePHID': None, 'dateCreated': 1369942140, 'dateModified': 1417573217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48993', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MWTemplateDialog should visually distinguish between wikitext and template name', 'description': {'raw': 'Screenshot while editing template with wikitext-generated target\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F11029}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1668706778, 'spacePHID': None, 'dateCreated': 1369920600, 'dateModified': 1668706778, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48974', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cut-Paste of paragraphs seems broken in Firefox', 'description': {'raw': 'Problem 1:\\n\\n1. Open [[User:Ssastry]]\\n2. Select Paragraph 3 completely.\\n3. Ctrl-X\\n4. Move to beginning of Paragraph 2.  Hit Enter.\\n5. Ctrl-V on empty line\\n\\nThe paragraph gets pasted on the same line as Paragraph 3.  \\n\\nProblem 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.\\n\\nThis problem seems specific to Firefox.  Cannot reproduce on Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372007590, 'spacePHID': None, 'dateCreated': 1369888320, 'dateModified': 1417573200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48960', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make ve.dm.Transaction chainable', 'description': {'raw': 'tx push\\ntx push\\ntx push\\ntx push\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1530903558, 'spacePHID': None, 'dateCreated': 1369777440, 'dateModified': 1530903558, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48913', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Mark up http errors + missing TEMPLATE errors with generic error attributes + error info in data-mw', 'description': {'raw': '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.\\n\\nTwo 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.\\n\\n(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.\\n- 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.\\n- Add a special rdf type on the image/wrapper tag: mw:Image/Missing maybe?\\n\\nEDIT: These properties should apply to missing templates as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1487999636, 'spacePHID': None, 'dateCreated': 1369760400, 'dateModified': 1487999636, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48900', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid should support <translate> and <tvar> natively as they are not normal parser tags', 'description': {'raw': 'screenshot\\n\\nExample: https://www.mediawiki.org/wiki/Communication\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50284\\n\\n**Attached**: {F10855}'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1451432369, 'spacePHID': None, 'dateCreated': 1369744440, 'dateModified': 1666689354, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48891', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Load visualeditor modules in a closure mapping $/mw/ve to their globals', 'description': {'raw': 'This may introduce a really large number of scopes and have undesirable performance effects, but we need to come up with a solution nonetheless.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1551737186, 'spacePHID': None, 'dateCreated': 1369733100, 'dateModified': 1551737186, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48885', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Multiple empty lines turn into uneditable elements due to mwPlaceholder', 'description': {'raw': '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.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372007435, 'spacePHID': None, 'dateCreated': 1369598340, 'dateModified': 1372007435, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48844', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Invalid or non-matching tags should not be normalised in unchanged sections of the document', 'description': {'raw': 'In this edit the user only made the \"die -> der\" change. In addition the </small> was removed by the VisualEditor.\\n\\nhttp://de.wikipedia.org/w/index.php?title=Fu%C3%9Fball-Bremen-Liga_2012%2F13&diff=118880158&oldid=118873211\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nT52052\\nT52050'}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1642380960, 'spacePHID': None, 'dateCreated': 1369561740, 'dateModified': 1642380960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48830', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Write test cases for ElementLinearData#getAnnotationIndexesFromOffset', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1369560000, 'dateModified': 1643977445, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48829', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting a line break causes strange results', 'description': {'raw': 'Steps to Reproduce:\\n\\n1. Go to https://www.mediawiki.org/wiki/API:Alltransclusions\\n2. Insert a blank line after the first paragraph.\\n3. Use the Del key (not backspace) to delete that line.\\n\\nRather 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ea6gwat27oulytc5tvsy', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372007371, 'spacePHID': None, 'dateCreated': 1369423680, 'dateModified': 1417573200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48796', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Improvements and  behaviour changes to the link input widget (tracking)', 'description': {'raw': \"There 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.\\n\\n#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.\\n\\nI'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.\\n\\n#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.)\\n\\nI 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. \\n\\nI believe both of these changes make a lot of sense.\\n\\nWhen 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.\\n\\nThere 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\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422402760, 'spacePHID': None, 'dateCreated': 1369411380, 'dateModified': 1542977047, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48789', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Protect Parsoid-generated token-names, about-ids, typeofs from conflicts with user-provided names.', 'description': {'raw': \"User can enter html tags or provide tag attributes or attribute values that Parsoid (and downstream clients) treat specially.\\n\\nEx: #mwt3 for about-ids, or mw:Object/* for typeofs or <template> tags or any of the special attributes/types found on http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec\\n\\nIf Parsoid doesn't detect these and escape/handle them somehow, Parsoid will mislead clients like VisualEditor and/or incorrectly serialize them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1369392240, 'dateModified': 1614017123, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48772', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Return at start of header causes cursor to move two characters down-page, not one', 'description': {'raw': 'On my user page https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29 and now on a test page https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29/VE_bugs every time I try to add a new section VE goes haywire\\n\\n1. Edit (with VE)\\n2. Click at start of first heading (\"welcomecreation...\")\\n3. Press Enter, it prepends new heading (good)\\n4. Press up arrow to move up to this new blank heading.\\n5. Start typing the heading, e.g. press \\'X\\'\\n6. That was wrong, so press Backspace (or left arrow)\\n\\nResult:\\nThe text of the heading underneath leaps above the new heading, joining text above it.\\nI can edit other parts of the document, but whenever I return to my new heading to add or backspace, the caret jumps elsewhere.\\nIf I undo enough times, VE undoes to a state where the new header displays below the existing header. The document looks different to what it did before, but [Review and save] is grayed out.\\n\\nI created a new document https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29/VE_bugs and similar stuff happens in that.\\n\\nThis is in Firefox 21 on Ubuntu, and mediawiki.org\\'s VE as of today.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372370158, 'spacePHID': None, 'dateCreated': 1369264200, 'dateModified': 1417573155, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48735', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar should clear float to avoid misalignment by extra elements', 'description': {'raw': 'On wikis where certain \"topicons\" are moved out of the mw-content-text wrapper into the root of #content the VisualEditor toolbar shows a weird blank space.\\n\\nThe icons in question are invisible due to float overlap, but they do push down the toolbar and occupying space to the right of the \"Save and review\" button thus pushing it and the rest of ve-ui-toolbar-actions to the left.\\n\\nTo reproduce this situation, run the following one or more times:\\n\\n    $(\\'#content\\').prepend(\\n        \\'<div class=\"mw-topicon\" style=\"display: block; width: 20px; height: 20px; background: pink; float: right; margin-left: 3px;\">x</div>\\'\\n    );\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369300408, 'spacePHID': None, 'dateCreated': 1369263840, 'dateModified': 1417573225, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48734', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Paste of content does not use the context's annotation\", 'description': {'raw': 'If you have some text with an annotation (e.g. bold, italics or a link) and copy in some text, the annotation is closed off, the text is insert as plain text, and then the annotation is restarted.\\n\\nI think users will expect \"paste as current style\" over \"paste as plain text\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1491408734, 'spacePHID': None, 'dateCreated': 1369247880, 'dateModified': 1491411355, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48720', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking Notices button or closing its dialog scrolls user back to the top', 'description': {'raw': \"Whenever you're scrolled down in a document and close or re-open the Notices flyout, the user is brought back to the top of the page (instead of staying where they are, like any other toolbar button would).\\n\\nThe toolbar floats and follows the user as they view the document, it is expected that interacting with it does not change the scroll offset. Most buttons abide by this except for Notices.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370972881, 'spacePHID': None, 'dateCreated': 1369144860, 'dateModified': 1417573217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48681', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Mediawikiwiki: Make VisualEditor a hidden preference', 'description': {'raw': 'The newsletter update states that Visual Editor is now functioning in the content namespaces at MW, which includes the extension: and manual: namespaces (and it does).  That said, the default text for \"MediaWiki:Visualeditor-preference-enable\" just states user and main at that wiki. I am presuming that this is a WikimediaMessages update somewhere\\n\\nAs a temporary measure I have created [[mw:MediaWiki:Visualeditor-preference-enable]] that mentions the extra two namespace.\\n\\nAs a note the mention of {{MediaWiki:Visualeditor-extensionnamespacepagelink}} and {{MediaWiki:Visualeditor-manualnamespacepagelink}} failed, so I didn\\'t link, and we will need to look to how these extra namespaces are going to be linked, and documented.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-bmenasgfntvftznu6wxs', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373933935, 'spacePHID': None, 'dateCreated': 1369100100, 'dateModified': 1591191670, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48666', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: DOM for template objects should expose template name', 'description': {'raw': \"{{foo}} -> Template:Foo\\n{{:foo}} -> foo\\n{{:user:Foo}} -> User:Krinkle\\n{{Template:foo}} -> Template:Foo\\netc.\\n\\nVisualEditor needs the name of the page that ends up being transcluded by the template invocation.\\n\\nFrom conversation with Gabriel I gather that currently the entire tranclusion system (at least in production) is deferred to the PHP parser (including the invocation itself). Which means Parsoid is unable to determine it itself right now.\\n\\nGabriel suggested Parsoid will provide the name the best it can for simple cases that don't dynamically construct the page name (e.g. not something like:\\n {{ {{getTemplateName|x=foo}} | bar }}\\n).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370462741, 'spacePHID': None, 'dateCreated': 1369093620, 'dateModified': 1370462741, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48663', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Toolbar floats only down to the top of the last BranchNode (which isn't always at the end)\", 'description': {'raw': 'Toolbar in VE floats to position of last BranchNode but should instead just use the bottom of the document or something.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371688425, 'spacePHID': None, 'dateCreated': 1369088700, 'dateModified': 1417573208, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48662', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide clean way to clone a linmod slice', 'description': {'raw': 'Complete with its own sub-store and everything, for consumption by a subsurface.\\n\\nRight now Trevor is committing crimes against humanity to make this work (converting to DOM then back to linmod again)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412590792, 'spacePHID': None, 'dateCreated': 1369072260, 'dateModified': 1417571696, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48651', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Data model needs characters, not code points', 'description': {'raw': 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs:\\n\\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 (\\'elevator\\' in Cantonese) is a single character represented in Javascript as \"\\\\uD860\\\\uDEE2\". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).\\n\\n2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string \"m\\\\u0300\" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.\\n\\nThese kinds of issues occur because the DataModel uses Arrays with code point elements, say [\\'\\\\uD860\\', \\'\\\\uDEE2\\', ..., \\'m\\', \\'\\\\u0300\\']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say [\\'\\\\uD860\\\\uDEE2\\', ..., \\'m\\\\u0300\\'], where each element represents a whole character.\\n\\nA good start would be to abstract out away calls to string.split( \\'\\' ) into a single function like this:\\n\\n  ve.splitCharacters = function ( value ) {\\n      return value.split( /(?![\\\\uDC00-\\\\uDFFF])/ ); // don\\'t split surrogate pairs\\n  };\\n\\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed.\\n\\nAlternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could \"encode\" the exceptional multi-code point characters as objects, so that \\'typeof data[i] === \"string\"\\' can still detect the simple cases.\\n\\nThis sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-lliyevigiycjbybglftk', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370532382, 'spacePHID': None, 'dateCreated': 1369029300, 'dateModified': 1417573215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48630', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide wiki metadata in the databases similar to toolserver.wiki', 'description': {'raw': \"Toolserver has the local table toolserver.wiki on all databases that provides metadata about the wikis including the server the wiki's database is kept on:\\n\\n```\\n| mysql> SELECT * FROM toolserver.wiki LIMIT 5;\\n| +----------------+------+------------+------------------+------+---------+-----------+--------------+--------------+---------------+--------+-------------+\\n| | dbname         | lang | family     | domain           | size | is_meta | is_closed | is_multilang | is_sensitive | root_category | server | script_path |\\n| +----------------+------+------------+------------------+------+---------+-----------+--------------+--------------+---------------+--------+-------------+\\n| | aawikibooks_p  | aa   | wikibooks  | NULL             |    3 |       0 |         1 |            0 |            0 | NULL          |      3 | /w/         |\\n| | aawiki_p       | aa   | wikipedia  | NULL             |    6 |       0 |         1 |            0 |            0 | NULL          |      3 | /w/         |\\n| | aawiktionary_p | aa   | wiktionary | NULL             |    1 |       0 |         1 |            0 |            1 | NULL          |      3 | /w/         |\\n| | abwiki_p       | ab   | wikipedia  | ab.wikipedia.org |  807 |       0 |         0 |            0 |            0 | NULL          |      3 | /w/         |\\n| | abwiktionary_p | ab   | wiktionary | NULL             |    0 |       0 |         1 |            0 |            1 | NULL          |      3 | /w/         |\\n| +----------------+------+------------+------------------+------+---------+-----------+--------------+--------------+---------------+--------+-------------+\\n| 5 rows in set (0.00 sec)\\n\\n| mysql>\\n```\\n\\nMost of the information can probably be extracted from operations/mediawiki-config, but I don't know which sources there are authoritative.\\n\\nSee also: {T50625}\"}, 'authorPHID': 'PHID-USER-vk6mlmacfhx77egryy5i', 'ownerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1377636000, 'spacePHID': None, 'dateCreated': 1369024500, 'dateModified': 1437935730, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48626', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor, CodeEditor, etc: User experience of editing page source directly', 'description': {'raw': 'There are now at least three ways to edit a page via index.php (not including other crazy things like Wikidata). I couldn\\'t find a bug tracking this user experience issue, so I\\'m filing this one.\\n\\nThe three ways I\\'m initially focused on are:\\n\\n* directly editing the wikitext (which can appear as an \"edit source\" page tab when VisualEditor is enabled);\\n* VisualEditor [https://www.mediawiki.org/wiki/VisualEditor]; and\\n* CodeEditor [https://www.mediawiki.org/wiki/Extension:CodeEditor] (automatic for pages in the Module namespace and soon the CSS/JS pages as well; has a toggle in the edit toolbar).\\n\\nIn particular to switch to editing the source, I\\'m worried about divergent approaches in the user interface. For example, a page tab v. a toggle in the edit toolbar.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-escte3psz5yfd2nj3jzr', 'dateClosed': 1725936323, 'spacePHID': None, 'dateCreated': 1368935460, 'dateModified': 1725936323, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48610', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Empty annotations are dropped', 'description': {'raw': 'VE drops things like <i></i>, which Parsoid sometimes uses to preserve strange things.\\n\\nI think a solution might be to store this as an inline node or as a meta item.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371840406, 'spacePHID': None, 'dateCreated': 1368896280, 'dateModified': 1529602765, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48605', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] Cursor should move to end of inserted contents after paste', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369092019, 'spacePHID': None, 'dateCreated': 1368891000, 'dateModified': 1417573275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48603', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paste is broken', 'description': {'raw': 'Throws an exception on line 564 of ve.ce.Surface, ve.getWindow is undefined.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368978729, 'spacePHID': None, 'dateCreated': 1368890520, 'dateModified': 1417573276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48602', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: 'Review and save' disabled after undo on oldid page\", 'description': {'raw': \"'Review and save' is enabled on loading an old version of a page (as it should) but becomes disabled briefly after the first transaction is committed, and again if you undo to the top of the stack.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368885016, 'spacePHID': None, 'dateCreated': 1368819600, 'dateModified': 1417573278, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48584', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Text field seems to lose focus, selection not possible any more', 'description': {'raw': 'When \"deselecting\" the text field of the visual editor (e.g. by clicking into the summary field) it seems to somehow loose focus.\\n\\nIt\\'s then not possible to directly select text (with the mouse) anymore. One needs to first click one time into the text field to be able to normally select text again.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-v3yn5qf233ggnnnmvejc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395789580, 'spacePHID': None, 'dateCreated': 1368796920, 'dateModified': 1395789580, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48576', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Move this category here\" should not appear in category suggestions when you\\'ve not picked one that exists', 'description': {'raw': \"It should only appear when you're matching to a single, extant category - it doesn't appear for a new category, but appears (with no content) where you match more than one, which is confusing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370567377, 'spacePHID': None, 'dateCreated': 1368749040, 'dateModified': 1417573219, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48564', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Move this category here\" should not appear for the last category', 'description': {'raw': \"It's a no-op, and is confusing. (But is it more confusing to list it?)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370986001, 'spacePHID': None, 'dateCreated': 1368745380, 'dateModified': 1417573216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48556', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'mw.hook listeners for GuidedTour for shouldSkip', 'description': {'raw': 'Investigate how mw.hook could be useful for GuidedTour.  One idea is subscribing to state changes for shouldSkip.  For instance, UploadWizard has an AJAX-type interface where you go from step to step without changing pages.\\n\\nIf we could listen to those steps, we could trigger the shouldSkip check (by calling guiders.resume or maybe another method that only checks this).\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402344878, 'spacePHID': None, 'dateCreated': 1368612900, 'dateModified': 1455464898, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48507', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'beta: Get SSL certificates for *.{projects}.beta.wmflabs.org', 'description': {'raw': \"We now have nginx SSL proxies in front of the beta caches (Bug T38648). We still have to fix the certificate (that is *.wmflabs.org for now).\\n\\nWe need certificates generated by 'Labs CA' for the entries listed in role::protoproxy::ssl::beta and some more.  I guess the easiest would be to create *.beta.wmflabs.org cert that will also contains the following DNS entries:\\n\\n*.wikimedia.beta.wmflabs.org\\n*.wikibooks.beta.wmflabs.org\\n*.wikinews.beta.wmflabs.org\\n*.wikipedia.beta.wmflabs.org\\n*.wikiquote.beta.wmflabs.org\\n*.wikisource.beta.wmflabs.org\\n*.wikiversity.beta.wmflabs.org\\n*.wikivoyage.beta.wmflabs.org\\n*.wiktionary.beta.wmflabs.org\\n\\nAnd the mobile ones:\\n\\n*.m.wikimedia.beta.wmflabs.org\\n*.m.wikibooks.beta.wmflabs.org\\n*.m.wikinews.beta.wmflabs.org\\n*.m.wikipedia.beta.wmflabs.org\\n*.m.wikiquote.beta.wmflabs.org\\n*.m.wikisource.beta.wmflabs.org\\n*.m.wikiversity.beta.wmflabs.org\\n*.m.wikivoyage.beta.wmflabs.org\\n*.m.wiktionary.beta.wmflabs.org\\n\\n*.zero.wikipedia.beta.wmflabs.org\\n\\n**See Also**:\\n{T56065}\\n{T70387}\\n{T71269}\"}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1472656512, 'spacePHID': None, 'dateCreated': 1368604800, 'dateModified': 1513299970, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48501', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Expose a parsoid public web API end point in the MediaWiki API', 'description': {'raw': 'We need a public API end point integrating with the general MediaWiki API that provides at least the following functionality:\\n\\n* HTML DOM retrieval per page and revision. Basically the /en/Foo?oldid=<n> end point.\\n* HTML DOM expansion: POST a DOM (or fragment), return re-expanded DOM\\n* HTML DOM saving: POST a modified DOM and a summary, and save it as a new revision.\\n\\nAs long as we are using Wikitext as our storage format, saving requires a conversion to HTML and a separate save step. The individual steps should *internally* be exposed to other users including the VisualEditor extension. There is probably no need to expose the HTML2WT conversion. We should instead aim to provide an HTML-only public interface.\\n\\nThe integration should use an URL schema that makes it easy to map some or all of the functionality to a stand-alone (non-PHP) backend to avoid PHP startup costs in the future.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'dateClosed': 1426214472, 'spacePHID': None, 'dateCreated': 1368578460, 'dateModified': 1602870180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48483', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Links created with VE are piped links even when linktrail could be used', 'description': {'raw': 'Currently the VisualEditor linkes like this: [[Glas|Glases]]\\nThe German-language Wikipedia prefers this though: [[Glas]]es\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51438\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49940\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52240'}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1368551520, 'dateModified': 1635718521, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48463', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Green striped area doesn't align properly in Monobook\", 'description': {'raw': \"When VisualEditor comes across a part of a page it can't edit, it adds a green striped area. However, VisualEditor seems to have very bad aim in Monobook. Screenshots forthcoming.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370362551, 'spacePHID': None, 'dateCreated': 1368498360, 'dateModified': 1417573221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48432', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor on all content namespaces on mediawiki.org', 'description': {'raw': \"Currently VisualEditor is only enabled on the user/main namespaces on mediawiki.org. It'd be nice if it were enabled on all namespaces on mediawiki.org.\\n\\nPerhaps test.wikipedia.org and test2.wikipedia.org as well.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369075886, 'spacePHID': None, 'dateCreated': 1368497580, 'dateModified': 1369075886, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48430', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Round-trip failures', 'description': {'raw': 'Bad diff from VisualEditor on mediawiki.org, 2013-05-13\\n\\nGo to <https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals>. Click \"edit\". VisualEditor form loads. Add a space after the sentence \"that drive editor engagement;\". Remove the space. Click \"Review and save\".\\n\\nExpected behavior: a diff showing no changes at all (space was added to the end of the line and then removed).\\n\\nCurrent behavior: see attached screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10742}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371867377, 'spacePHID': None, 'dateCreated': 1368496740, 'dateModified': 1371867377, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48427', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Categories with multiple \"../\"s in their hrefPrefix broken', 'description': {'raw': 'VisualEditor added \"../\" inside [[Category:QA]], breaking the link. I swear I didn\\'t touch the category itself. I was just editing an unrelated paragraph.\\n\\nSee https://www.mediawiki.org/w/index.php?title=Groups%2FProposals%2FFeatures_testing&diff=689563&oldid=689504\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368487340, 'spacePHID': None, 'dateCreated': 1368466500, 'dateModified': 1417573285, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48408', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Set up JavaScript code coverage analysis', 'description': {'raw': 'Any plans of having JSCover (JavaScript code coverage analysis) being integrated and run by Jenkins (in away that is usable for core and extensions as well)?\\n\\n[1] http://tntim96.github.io/JSCover/\\n\\n[2] http://tntim96.github.io/JSCover/example-qunit/out/jscoverage.html?test/index.html\\n\\n[3] http://tntim96.github.io/JSCover/manual/manual.xml#automatingPhantomJS\\n\\n[4] http://tntim96.github.io/JSCover/manual/manual.xml#automatingAnt\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ldehclaehsvglrqxywsj', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411761995, 'spacePHID': None, 'dateCreated': 1368310740, 'dateModified': 1416334050, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48365', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ↵ is shown when wikicode contains single newline, which is not very WYSIWYG', 'description': {'raw': 'Single newlines have no effect on the way a wiki page is displayed.\\nSo they should be ignored in a WYSIWYG editor.\\n\\nExample: Third line at http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services#Specification_progress_.26_TC_members'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1368091860, 'dateModified': 1657957730, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48290', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Enter 2 times, Backspace 2 times -> not deleted in Firefox', 'description': {'raw': 'Go to http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services\\nPut the cursor somewhere in the text.\\nType \"Enter\" 2 times.\\nType \"Backspace\" 2 times.\\n\\nExpected: as original\\nActually: The newlines remain\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370445778, 'spacePHID': None, 'dateCreated': 1368089280, 'dateModified': 1417573221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48284', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'PostEdit: Core-ify this', 'description': {'raw': 'As discussed with Steven W. just now, we should move this into MW core (so, amongst other things, VisualEditor can depend on it and not have to re-invent the wheel).\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=16066'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370049933, 'spacePHID': None, 'dateCreated': 1368050160, 'dateModified': 1418756871, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48276', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: For edit summary field, give users an auto-fill drop-down (or similar) of recent edit summaries they've used\", 'description': {'raw': \"We use textarea which means that browsers don't suggest text from previous uses.\\n\\n**See Also**:\\n{T53903}\\n{T54859}\\n{T54085}\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1561611645, 'spacePHID': None, 'dateCreated': 1368048660, 'dateModified': 1660398891, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48274', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Alienation shield for images in table are not the right size, so images are still clickable', 'description': {'raw': 'Images in a table are incompleted alienated and still clickable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://de.wikipedia.org/wiki/Liste_der_Hochh%C3%A4user_in_Deutschland'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369093449, 'spacePHID': None, 'dateCreated': 1368003600, 'dateModified': 1417573227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48254', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't close/re-open annotation when pasting text into a comparable context\", 'description': {'raw': 'Not sure whether this is ContentEditable, DataModel or LinearModel.\\n\\nWhen pasting italicised text (from elsewhere on the same page) into an already italicised sentence we currently close, re-open, close, re-open that annotation.\\n\\nSteps to reproduce problem:\\n* start with:\\n  <p><i>Original text here.</i></p><p><i>Something else there.</i></p>\\n* select \"else\"\\n* copy\\n* select \"text\"\\n* paste to replace\\n* end state:\\n  <p class=\"ve-ce-branchNode\"><i class=\"ve-ce-TextStyleAnnotation ve-ce-TextStyleItalicAnnotation\">Original </i><i class=\"ve-ce-TextStyleAnnotation ve-ce-TextStyleItalicAnnotation\">else</i><i class=\"ve-ce-TextStyleAnnotation ve-ce-TextStyleItalicAnnotation\"> here.</i></p>\\n\\nNow this wouldn\\'t be a major issue (merely inefficient) if it weren\\'t for bug 48194 in Parsoid.\\n\\nReal example:\\n* Intended edit: https://www.mediawiki.org/w/index.php?title=Watchlist_wishlist&diff=686477&oldid=686247\\n* Actual edit as seen in the Review and save dialog of VisualEditor (and saved as-is): https://www.mediawiki.org/w/index.php?title=Watchlist_wishlist&diff=686475&oldid=686247\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: critical'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368554438, 'spacePHID': None, 'dateCreated': 1367894520, 'dateModified': 1368726943, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48195', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Non-contiguous rendering of references in LTR text in RTL mode', 'description': {'raw': \"* Create an English article with a <ref> tag at the end of a paragraph\\n* Set $wgLanguageCode = 'en-rtl';\\n* View the article. You'll see something like ]My text[1 (this rendering seems wrong)\\n* Edit the article in VE. The non-contiguous reference causes problems:\\n** The phantom is rendered wrongly so it's not visible\\n** When you select the reference, the selection looks really strange\\n\\nShould we wrap things in a <bidi> tag or whatever to ensure better rendering?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369783170, 'spacePHID': None, 'dateCreated': 1367879940, 'dateModified': 1417573222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48185', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: JS error on (null) diffing [[BMW 801]] but only if debug=false', 'description': {'raw': 'Make a null edit (space and backspace), then trigger a diff. JS error thrown in Firefox but not Chrome:\\n\\nError: 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\\n\\nHowever, for debug=true, no such error occurs. Is this just going to be a transient RL issue?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367972703, 'spacePHID': None, 'dateCreated': 1367874000, 'dateModified': 1417573290, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48181', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Throttle or otherwise handle large copy-paste input', 'description': {'raw': 'I watched a user using Chrome paste a 32400-character buffer of special characters into VE.  Chrome became unresponsive. \\n\\nThis user then did that in multiple tabs and the entire computer became unresponsive.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1367867040, 'dateModified': 1643977445, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48172', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Serve interface components as SVGs over PNGs to any browser which supports it', 'description': {'raw': \"(Provided we are happy with the rendering quality)\\n\\nCurrently we only serve SVGs when window.devicePixelRatio > 1.\\n\\nOn suggested test for SVG support is:\\n\\ndocument.createElementNS && document.createElementNS( 'http://www.w3.org/2000/svg', 'svg' ).createSVGRect\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368135541, 'spacePHID': None, 'dateCreated': 1367837220, 'dateModified': 1417573288, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48148', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Vector drop down menu hidden behind toolbar', 'description': {'raw': 'As the title says: when the VisualEditor is active, the drop down menu (p-caction) under Vector skin is dropped down behind the VE toolbar, making it impossible to click on. May be a simple z-index issue.'}, 'authorPHID': 'PHID-USER-t4cbxxxhiswoecybwxy2', 'ownerPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368205844, 'spacePHID': None, 'dateCreated': 1367661720, 'dateModified': 1465905507, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48078', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Table captions were alienated so looked wrong and couldn't be edited\", 'description': {'raw': 'Expected layout\\n\\nI included two screenshots, illustrating the problem.\\n\\nApple Safari 6, Mountain Lion\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/wiki/Meurchin\\n\\n**Attached**: {F10895}'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367681845, 'spacePHID': None, 'dateCreated': 1367650560, 'dateModified': 1417573292, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48070', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Newly-created list items are deliberately not merged with nearby lists - change this?', 'description': {'raw': 'In Firefox 20.0.1:\\n\\n1. Edit a page that has a bulleted list.\\n2. Place the cursor on the first bullet item.\\n3. Click the \"Bullet List\" button. The first bullet item loses its bullet. (Correct.)\\n4. Click the \"Bullet List\" button a second time. The first bullet comes back (correct), but there is now a blank line displayed below it.\\n\\nSimilarly, if you remove & add a bullet in the middle of the list, you get blank lines above AND below the item.\\n\\nSimilarly, if you do this with a numbered list, the blank line breaks the numbering: the list items below the blank line start over from \"1\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-o5tv5cyrple4fn5xqopm', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1367598960, 'dateModified': 1643977445, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48051', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Indent buttons should be used for in-/out-denting paragraphs as well as lists.', 'description': {'raw': 'The indent and outdent buttons are always grayed out.\\n\\n(reported at http://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Alpha2013-04#Link_einbinden_.2F_Einzug)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1367512920, 'dateModified': 1643977446, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48010', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support language variant conversion labels', 'description': {'raw': 'Conversion labels shown\\n\\nThe conversion labels (i.e. { } ) for wikis like zhwiki is shown when editing using the VisualEditor.\\n\\nThose labels should be hidden, or otherwise newbies using the editor will break them easily.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F10580}'}, 'authorPHID': 'PHID-USER-ixwg3kf22idjy7x4ncxf', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1430156980, 'spacePHID': None, 'dateCreated': 1367389920, 'dateModified': 1430157028, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47913', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Regression] mwCustomEditButtons from user script should work', 'description': {'raw': 'From the fall out of bug 47457\\'s resolution:\\n\\n(bug 47457 comment #63 by Liangent)\\n> (bug 47457 comment #54 by Krinkle)\\n> > Change-Id: Ic3d0c937268d0943d2f770f3ca18bcf4e1eed346\\n> \\n> This fix causes breakage of any user of site scripts which assume that\\n> they\\'re\\n> loaded before $(document).ready(). Maybe someone can move jQuery.ready() call\\n> to a position just before </body> and after all other script references?\\n\\n(bug 47457 comment #64 by matma.rex)\\n> And it also breaks the old \\'mwCustomEditButtons\\' interface to add custom\\n> buttons to the old edit toolbar, which apparently everyone and their dog are\\n> using across the wikis. (Since the user JS is loaded from the bottom queue,\\n> but\\n> the toolbar script either from the top or using inline <script> tags with\\n> $.ready inside.)\\n> \\n> Reopening. Moving the jQuery.ready() call after the bottom queue seems like a\\n> good idea.\\n\\n\\n(bug 47457 comment #66 by Brad Jorsch)\\n> (bug 47457 comment #63 by Liangent)\\n> > Maybe someone can move jQuery.ready() call to a position just before \\n> > </body> and after all other script references?\\n> \\n> (bug 47457 comment #64 by matma.rex)\\n> > Moving the jQuery.ready() call after the bottom queue seems like a good idea.\\n> \\n> We tried that, see patchset 5 in https://gerrit.wikimedia.org/r/#/c/61057/5.\\n> It didn\\'t work.\\n> \\n> But unless the browsers were delaying the DOMContentLoaded event until after\\n> the async-loaded scripts in the bottom queue were loaded, I don\\'t know how\\n> this wasn\\'t already a problem. Krinkle, any ideas?\\n\\nA few important questions I\\'d like answered:\\n\\n@Liangent: Can you given an example where it matters for a user script whether the document becomes ready before or after they are loaded? The user scripts are loaded from the bottom of the <body> before </body>. Practically the document is already ready at this point, just $(document).ready() hasn\\'t fired yet. Any user script code that isn\\'t wrapped in $(document).ready() will still execute at exactly the same time. Any user script code that *is* wrapped in $(document).ready() will now execute immediately after loading instead of... immediately after loading. Exactly the same, not?\\n\\n@Matma.rex: You mean the fact that the deprecated mwCustomEditButtons global (unlike the mw.toolbar interface) is inspected only once by mediawiki.action.edit.js, namely at the domready event. And if it is triggered before the user script, adding to that array will become a no-op.\\n\\nThough there is a lot of usage of this feature, lets not forget the context:\\n\\n* The mwCustomEditButtons interface is for the classic toolbar (aka \"Monobook editor\", though Vector users can also disable WikiEditor to get to it). This is already a large minority of users.\\n* The mwCustomEditButtons interace has been deprecated in favour of mw.toolbar.addButton, which I created especially for the legacy toolbar users last year to address the many declined bug reports for mwCustomEditButtons which could not be otherwise addressed because mwCustomEditButtons is beyond repair, it is a flawed concept and it keeps breaking for many reasons.\\n\\nI don\\'t think anything related to mwCustomEditButtons can justify a change of any kind unless it comes at absolutely no overhead and downside.\\n\\n@Brad Jorsch: It seems that the Firefox bug with document.write being disabled before DOMContentReady is worse than we thought. It is disabled even before the end of the </body> has been reached. We found through trial-and-error that placing it after the main content but before the bottom queue worked.\\n\\nAs Brad pointed out, $.ready being triggered earlier makes no difference for the bottom queue because they are loaded asynchronously, they always execute without blocking the parser or the DOM ready event. In fact (while designing this) Roan and I made very sure to test this across the entire board of browsers we even remotely support (IE6-10, FF2-17, Chrome10-23, Opera9-11.x). And in any browser that we couldn\\'t load it async, we scheduled the addScript to after dom-ready manually (only in Opera).\\n\\nHowever note that the user scripts (like the site scripts) are *not* loaded through mw.loader because we still support legacy global scope for them. They are loaded by a hardcoded script tag in the DOM. Which means they are blocking and used to block dom-ready, and now they run after dom-ready (well, they still block dom-ready, but we trigger that callback queue earlier).\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50310'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370831532, 'spacePHID': None, 'dateCreated': 1367327220, 'dateModified': 1602869345, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47872', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: For images, ensure that the HTML structure rendered in VE is the same as output by PHP parser so that styles/scripts work as expected and images look normal', 'description': {'raw': 'Screenshot in edit mode\\n\\nImages on pages are normally included using the \"thumb\" syntax:\\n\\n[[File:Foo.jpg|thumb|description]]\\n\\nIn the edit mode no thumb frame is shown, see screenhots.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/thumb\\n\\n**Attached**: {F10382}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369093729, 'spacePHID': None, 'dateCreated': 1367185320, 'dateModified': 1417573227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47803', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Slugs should be more obvious to the user that they\\'re not \"really\" blank lines', 'description': {'raw': 'Simple test case, see URL:\\n\\n* foo\\n: bar\\n\\nadds a newline in edit mode. When removing this newline in edit mode the : is killed by the parser.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/Finissage\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60535'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394077374, 'spacePHID': None, 'dateCreated': 1367166420, 'dateModified': 1443276409, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47790', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Coordinate template on dewiki not alienated', 'description': {'raw': 'Coordinate template on dewiki not alienated. Shown as active hyperlink to the toolserver.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://de.wikipedia.org/wiki/Breslauer_Platz_%28K%C3%B6ln%29'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374527977, 'spacePHID': None, 'dateCreated': 1367154120, 'dateModified': 1417573082, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47788', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor on viwiki', 'description': {'raw': 'Per community request; will throw in a change on Monday.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367270838, 'spacePHID': None, 'dateCreated': 1367123340, 'dateModified': 1367270838, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47784', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar tooltip text throbs when un-floated', 'description': {'raw': \"If you scroll down from the top of the page with the edit notice open and then scroll back up, the text content of the notice 'throbs' a little. I think it has to do with the dynamic addition / removal of the 've-ui-toolbar-wrapper-floating' class on ve-ui-toolbar-wrapper.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416181878, 'spacePHID': None, 'dateCreated': 1367030520, 'dateModified': 1417571678, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47766', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: A lot of time needed to load <math> blocks?', 'description': {'raw': \"I tested it on the [[Bayes' theorem]] which has <Math></Math> inside the article with chrome 28 and it couldn't load the page!.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-dswbdv7ibhsefllcqarz', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367548087, 'spacePHID': None, 'dateCreated': 1367021760, 'dateModified': 1367548087, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47760', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: No warning is shown when saving a page without an edit summary despite user preference', 'description': {'raw': 'No warning is shown when saving a page without an edit summary even when the \"Prompt me when entering a blank edit summary\" preference is enabled.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369092004, 'spacePHID': None, 'dateCreated': 1367008860, 'dateModified': 1417573275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47752', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Aliens' phantoms don't appear in the Hebrew Wikipedia (cache/CSSJanus issue?)\", 'description': {'raw': \"When I edit an article in the English Wikipedia and hover over a template or an image, green diagonal stripes appear over it, meaning that it can't be edited.\\n\\nThese green stripes don't appear in the Hebrew Wikipedia.\\n\\nSee the URL for a demo.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://he.wikipedia.org/wiki/ASCII\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367280339, 'spacePHID': None, 'dateCreated': 1367005440, 'dateModified': 1417573294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47746', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Moving the cursor using an arrow makes templates and footnote numbers disappear', 'description': {'raw': 'Steps:\\n\\n1. Go to the URL.\\n2. Start editing the page using the VisualEditor.\\n3. Move the cursor using the keyboard arrow keys forward (right).\\n\\nObserved:\\n\\nWhen you get to the \"Done\" template and go on moving the cursor, the whole template disappears.\\n\\nThe same happens when you get to the reference number on the second line (\"[1]\").\\n\\nThe cursor must probably skip over them and definitely not make them disappear.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/VisualEditor:Disappearing_template'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367005458, 'spacePHID': None, 'dateCreated': 1367005140, 'dateModified': 1417573297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47745', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Message <visualeditor-feedback-link> should be used in content language', 'description': {'raw': 'Having users using different languages to post feedback on different pages on the same site makes it difficult to manage.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374012385, 'spacePHID': None, 'dateCreated': 1366981200, 'dateModified': 1417573086, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47730', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[mediawiki.feedback.js] Feedback should follow redirect', 'description': {'raw': \"I tried to edit MediaWiki:Visualeditor-feedback-link on zhwp but it doesn't affect the feedback target page at all. Is that even the correct message to change?\\n\\nI then turn the target page into a redirect, but feedback are still sent to that page without following the redirect.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-hoj4lurwi6bejyjy5qlp', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1419984894, 'spacePHID': None, 'dateCreated': 1366979940, 'dateModified': 1419984894, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47729', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: using non-ASCII characters in the VisualEditor edit summary insertion can make the remaining character count negative', 'description': {'raw': \"Try typing non-ASCII characters in the VisualEditor edit summary field. For example, just type the Russian letter ж continuously. Towards the end it won't stop at 0, but at -1. Example screenshot from the Hebrew Wikipedia: http://j.mp/ZoQKX6 .\\n\\nThis should be handled in a cleaner way. Either disallow typing anything that would go beyond zero, or allow all text to go beyond zero, as in Twitter or MoodBar.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368885077, 'spacePHID': None, 'dateCreated': 1366970520, 'dateModified': 1424041667, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47718', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector input text always has LTR direction', 'description': {'raw': \"Steps:\\n\\n1. Write some text in VisualEditor in the Hebrew Wikipedia.\\n\\n2. Select a word.\\n\\n3. Press the link button in the toolbar. A small link insertion panel appears.\\n\\nObserved: The direction of the <input> element for the link is ltr.\\n\\nExpected: The direction of the <input> element for the link is supposed to be rtl.\\n\\nComment: It does make sense to set ltr direction by default for external links (http://www.example.com). For internal links the default direction should be the same as that of that Wikipedia's content language.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367529320, 'spacePHID': None, 'dateCreated': 1366970040, 'dateModified': 1417573293, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47717', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE tab is on the left (not right) of the \"edit source\" tab in RTL languages', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368639099, 'spacePHID': None, 'dateCreated': 1366932480, 'dateModified': 1417573281, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47684', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support editing nowiki blocks', 'description': {'raw': \"If users can't edit in nowiki blocks, they will make accidental wikitext-like items and be forever unable to edit them in future.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374262258, 'spacePHID': None, 'dateCreated': 1366930860, 'dateModified': 1417573070, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47678', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Re-label the 'cancel' toolbar message to 'exit without saving'\", 'description': {'raw': 'The \\'cancel\\' message is used confusingly.\\n\\nI only noticed it recently. I know of two places where it is used, though there may be more:\\n\\n1. As a link near the \"Show changes\" button when editing a page.\\n\\n2. As a button near the \"Review and save\" button in the VisualEditor.\\n\\nIn both cases it\\'s better to say something like \"Exit without saving\". The \"Cancel\" button is usually used in dialog boxes and not in editors\\' user interfaces.\\n\\nThe message may be used in other places and in extensions, so it\\'s probably better not to change it. For these actions a new message should be created, or maybe even two messages.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368804205, 'spacePHID': None, 'dateCreated': 1366929720, 'dateModified': 1406470421, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47676', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Empty list items goes missing in the PHP parser when tidy is enabled', 'description': {'raw': \"Take a look at the URL.\\n\\nWhen you see the output page, the list has three items. If you edit it in the source editor, you'll see that there's an extra empty item in the end of the list. If you edit it in the VisualEditor, you'll see it rendered.\\n\\nThe VisualEditor behavior actually makes more sense to me. Gabriel Wicke suggested on IRC to open this issue at the PHP parser.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/VisualEditor:Empty_list_item\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-k6tmz5ylx4rzfl3bitse', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1494287494, 'spacePHID': None, 'dateCreated': 1366928220, 'dateModified': 1494845987, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47673', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Sequential floated images are stacking', 'description': {'raw': '**Author:** `owen`\\n\\n**Description:**\\nLooking at [[Principality of Stavelot-Malmedy]] in the Visual Editor, immediately after the heading \"Development and the High Middle Ages\" there are two images floated right.\\n\\nIn Read mode, these images are given `float: right; clear: right;`. In VE mode, however, the `clear: right;` appears to be missing, so the images are stacking up.\\n\\nIn case it makes a difference, I\\'m running Chrome 26.0.1410.64 m, on 64-bit Windows 7 Home Premium (Build 7601, Service Pack 1).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://en.wikipedia.org/wiki/Principality_of_Stavelot-Malmedy'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369093908, 'spacePHID': None, 'dateCreated': 1366925940, 'dateModified': 1417573227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47672', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"[TUX] Page view doesn't fit long page titles\", 'description': {'raw': 'A long title all mixed\\n\\nLong titles get compressed until they become unreadable, see URL and screenshot.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: minor\\n**URL**: https://meta.wikimedia.org/w/index.php?title=Special:Translate&language=de&group=page-Wikimedia+Blog%2FDrafts%2FTry+out+the+alpha+version+of+the+VisualEditor%2C+now+in+15+languages&filter=&action=page\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=45924\\n\\n**Attached**: {F10857}'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'dateClosed': 1607413610, 'spacePHID': None, 'dateCreated': 1366899360, 'dateModified': 1607413610, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: API paction=serialize should say so if Parsoid is unavailable (instead of status \"success\" with missing content)', 'description': {'raw': '1. Parsoid not running, VisualEditor enabled on to-be-created page X\\n2. Enter a few words \\n3. \"Review and Save\"\\n4. Loader keeps spinning indefinitely\\n\\nRequest:\\n\\naction=visualeditor&paction=serialize&html=%3Cp+data-ve-changed%3D%22%7B%26quot%3Bcontent%26quot%3B%3A7%7D%22%3Edfgdg%3C%2Fp%3E&page=Sandbox%2F1&oldid=0&token=%2B%5C&format=json\\n\\nResponse:\\n\\n{\"visualeditor\":{\"result\":\"success\",\"content\":false}}\\n\\nNo errors.\\n\\nNote this bug could also be reported as \"Loader keeps spinning forever when creating a new page and trying to review/save it\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368638813, 'spacePHID': None, 'dateCreated': 1366757460, 'dateModified': 1417573282, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47581', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to add/edit musical scores', 'description': {'raw': 'As a VisualEditor plugin inside the extension, provide a visual way for users to create and edit musical scores.\\n\\nThis would be a (very) major undertaking, even if there is an existing JavaScript-based visual Lilypond score editor, or failing that, a visual score editor with a different output format which would need to be converted to Lilypond. A brief search found a few promising leads for ABC editors, but mostly based in Flash.\\n\\nStill, hopefully not just a pipedream. :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1366688580, 'dateModified': 1670271788, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47528', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Sanity-check the browser by internally round-tripping HTML to linmod and ensuring it's the same\", 'description': {'raw': 'On VE load, do an \"originalHtml == serialise(linmod(originalHtml)\" or whatever and fail out of the VE if false; ideally, also allow the user to submit a failure report for debugging purposes (this will need to get checked through with legal).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372387346, 'spacePHID': None, 'dateCreated': 1366667700, 'dateModified': 1417573153, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47521', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support \"Language conversion blocks\" for multi-script wikis', 'description': {'raw': 'The \"language conversion blocks\" are a wikitext feature that allow users to define text content in parallel scripts. The most high profile is in Chinese, which has two major writing systems and automated conversion between them, but there are 28 others, some of which are not automated conversion (so VE will need to not just mark the text with an appropriate <span>, but allow the user to understand when they have edited text that needs editing twice or thrice (possibly in scripts they cannot/do not want to use?) - see https://meta.wikimedia.org/wiki/Wikipedias_in_multiple_writing_systems\\n\\nDocumentation of the feature (focussed on the syntax) is here: https://www.mediawiki.org/wiki/Writing_systems/Syntax\\n\\nParsoid will need to add support for this first, which is {T43716}.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'dateClosed': 1513281041, 'spacePHID': None, 'dateCreated': 1366380120, 'dateModified': 1627374147, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47411', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MWTemplateNode should serialize original HTML if unchanged', 'description': {'raw': \"If we get an MWTemplateNode and the user doesn't change it, then in the data->DOM conversion we should serialize it back out the way it came in, including all the other nodes (the template contents) that we normally discard.\\n\\nDiscarding these nodes when the user did change the template (i.e. the attributes changed) is fine and encouraged, but if we also do it when nothing changed, Parsoid's DOM diff algorithm will notice that we changed something in the DOM, causing selective serialization not to skip the template while it should.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366733313, 'spacePHID': None, 'dateCreated': 1366341300, 'dateModified': 1417573332, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47394', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Caption tags are stripped from tables when VE converts data model to DOM', 'description': {'raw': '1. Go to: http://ve-change-marking.instance-proxy.wmflabs.org/wiki/Test2\\n2. Open page in VisualEditor\\n3. Open browser console.\\n4. Run ve.dm.converter.getDomFromData( ve.instances[0].documentModel.store, ve.instances[0].documentModel.data.data ).body.outerHTML\\n5. You get the following output:\\n--------------\\n<body><table data-parsoid=\"{&quot;tsr&quot;:[0,3],&quot;dsr&quot;:[0,49,3,2]}\">\\nThis is a caption\\n<tbody data-parsoid=\"{&quot;dsr&quot;:[24,47,0,0]}\"><tr data-parsoid=\"{&quot;tsr&quot;:[24,26],&quot;startTagSrc&quot;:&quot;|-&quot;,&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[24,46,2,0]}\">\\n<td data-parsoid=\"{&quot;tsr&quot;:[27,28],&quot;autoInsertedEnd&quot;:true,&quot;dsr&quot;:[27,46,1,0]}\">Table cell content</td></tr>\\n</tbody></table></body>\\n----------------\\n\\nNotice the missing <caption> .. </caption> tags.\\nSo, when Parsoid gets this, the caption is fostered out and shows up as a diff.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366298405, 'spacePHID': None, 'dateCreated': 1366256040, 'dateModified': 1417573335, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47349', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit #REDIRECT status in the page metadata panel', 'description': {'raw': 'See bug 45808 for the corresponding Parsoid bug.\\n\\nCurrently editing a redirected page (say \"OLPC\") causes the following Bad Things to happen.\\n\\na) the edited page content is saved back to \"OLPC\", overwriting the original #REDIRECT\\n\\nb) the page content is from \"One Laptop Per Child\", but with an added {{Redirect:OLPC}} template at the top; this extra template gets saved back with the rest of the edits.\\n\\nIn bug 45808, Parsoid will return a special <meta> or <link> tag in the body for redirected pages.  This bug is for the corresponding VE support to recognize that tag and provide a user-friendly interface for editing redirects.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=47329'}, 'authorPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392349729, 'spacePHID': None, 'dateCreated': 1366223100, 'dateModified': 1443276410, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47328', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Zuul: Gerrit's ssh event stream unavailable\", 'description': {'raw': \"Since at 2013-04-05 04:29:46 UTC, Zuul no more receives events from Gerrit. It uses a CLI command such as:\\n\\n    ssh -p 29418  jenkins-bot@manganese.wikimedia.org gerrit stream-events\\n\\nI did stream-events using both the jenkins-bot user and my own account 'hashar'. While submitting a new patchset or posting a comment: nothing is reported.\\n\\nThe end effect is that no jobs are triggered in Jenkins.\\n\\n--------------------------\\n\\nSummary (13/12/2017)\\n\\nThe sshd daemon (Mina) would lost connection on one way connections and hitting some kind of timeout.  That affected Zuul which idles with a `gerrit stream-events`.\\n\\nGerrit sshd.idleTimeout got set to 10 days as a workaround https://gerrit.wikimedia.org/r/#/c/58126/\\n\\nGerrit patch:\\n\\nhttps://gerrit-review.googlesource.com/c/gerrit/+/44472 ([[ https://gerrit.googlesource.com/gerrit/+/79b91bfe746121a81a785bdd3b24df2096410c55 | 79b91bfe ]]) is the Gerrit patch.\\n\"}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370873901, 'spacePHID': None, 'dateCreated': 1365152280, 'dateModified': 1513190529, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46917', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Normalize all preservation to use HTML store', 'description': {'raw': 'All HTML preservation should be changed to store the full HTML of the node/annotation and use the HTML store. This means removing the html/* attributes from nodes, and the strange things (original tag name and attributes) we put in annotations.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370307483, 'spacePHID': None, 'dateCreated': 1364432880, 'dateModified': 1417573222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46618', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to insert/edit references to Wikidata queries', 'description': {'raw': 'Though T41598 will mean that VisualEditor will be able to edit infoboxes as they are now (alongside other templates), in the near-future Wikidata will replace a great many of the entries in these infoboxes with Wikidata queries (syntax still to be locked down).\\n\\nFor the VisualEditor to be truly useful for users in this context, users should be able to:\\n* add, review, modify and remove references to existing Wikidata queries;\\n* add or amend arbitrary Wikidata queries for the above; and\\n* do so in both VisualEditor-mode contexts (paragraphs of text etc.) and wikitext-mode contexts (like the template dialog as it will initially be).\\n\\n--------------------------\\n**See Also**:\\n{T41598}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1364168100, 'dateModified': 1709801126, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46521', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Annotation API fixes', 'description': {'raw': '* Make toHTML() return real DOM nodes, we don\\'t need the weird construction for CE any more\\n* Pass in the content so it\\'s possible to have rules like \"if the annotation only covers whitespace, strip it\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1428423688, 'spacePHID': None, 'dateCreated': 1363986660, 'dateModified': 1438734540, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46464', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"[Regression] VisualEditor: Error in load() leaves page in dimmed state (Uncaught TypeError: Cannot call method 'removeAllListeners' of null)\", 'description': {'raw': 'Steps to reproduce issue:\\n* MediaWiki + VisualEditor (no Parsoid)\\n* Edit page (dims the page while loading)\\n* Error pops up (parsoidserver-http-curl-error)\\n* Cancel\\n\\nExpected:\\n Page undims.\\n\\nActual:\\n Page still dimmed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363982636, 'spacePHID': None, 'dateCreated': 1363973460, 'dateModified': 1417573134, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46456', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Trying to auto select a word just after an alien node causes an exception in rangy.', 'description': {'raw': \"1. Load the 'aliens' example document.\\n2. Place the cursor in front of the first 'Lorem' and hit the link button.\\n3. Observe the exception\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364218671, 'spacePHID': None, 'dateCreated': 1363548060, 'dateModified': 1417573339, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46246', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to add/edit Listings', 'description': {'raw': \"**Author:** `lukebenes`\\n\\n**Description:**\\nI see from [http://en.wikivoyage.org/wiki/Wikivoyage:Accommodation_listings The Accomodations Listing suggested style you want people to continue to use the wikitravel tags. But I do not see any tools to automate the process. \\n\\nIf you look at the Add and Edit Listing Feature listing like those that can be found [http://wikitravel.org/en/Wikitravel:Small_city_article_template#Sleep here] and [http://wikitravel.org/en/Trat#Sleep here]? You'll see there is a tool to edit these tag. \\n\\nThis tags is extremely useful to organize data and make quick edits. For example, I have fixed many incorrect phone numbers and addresses using this helpful tool. Please consider adding this feature the MediaWiki.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-escte3psz5yfd2nj3jzr', 'dateClosed': 1719889959, 'spacePHID': None, 'dateCreated': 1363453140, 'dateModified': 1719889959, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46225', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up inconsistent documentation of event emissions', 'description': {'raw': 'Some events are undocumented (like ve.dm.Surface.prototype.change, which emits multiple events but documents none), most have the event name without quotes, but some have single quotes (ve.dm.Surface.addInsertionAnnotation) or double quotes (ve.ui.Toolbar.prototype.onContextChange). Parameters sometimes are documented and sometimes aren\\'t, there\\'s no clear distinction between \"parameters aren\\'t documented\" and \"there aren\\'t any\", and in no case do we document the types and descriptions of event parameters, we only ever document their names.\\n\\nWe probably also don\\'t document events with @event nearly as often as we should. It\\'s a huge mess.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363798993, 'spacePHID': None, 'dateCreated': 1362706560, 'dateModified': 1417573340, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45872', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: VE should be able to be 'default' for some namespaces and by user preference elsewise/in others\", 'description': {'raw': \"Right now VE is either 'default' for some given namespaces, or enabled but only exposed by user preference for some namespaces; it should be possible to have a mixed-installation for testing/etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367604375, 'spacePHID': None, 'dateCreated': 1362704940, 'dateModified': 1417573292, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45871', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: split paragraphs in a listItem should not be considered 'wrapper' paragraphs\", 'description': {'raw': \"Start a list item and type 'a', now hit shift-enter and type b.\\n\\nExpected diff:\\n*a<p>b</p>\\n\\nActual diff:\\n*ab\\n\\nThe paragraph created when you create the list has internal.generated = 'wrapper'. This property gets copied when you split the list. Two wrapper paragraphs next to each other apparently get merged into one.\\n\\nThe only way wikitext can have two paragraphs in a list is with HTML so extra paragraphs must be full HTML paragraphs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363373310, 'spacePHID': None, 'dateCreated': 1362418080, 'dateModified': 1417573341, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45710', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[TUX] Browser support matrix', 'description': {'raw': 'Create a list of supported browsers and document it.\\n\\nAlso make sure that TUX actually works with those browsers.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement\\n**URL**: http://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix'}, 'authorPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'ownerPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-732lqsmz4v6bss3kln2v', 'dateClosed': 1607415848, 'spacePHID': None, 'dateCreated': 1362144360, 'dateModified': 1607415848, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45602', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Implement remaining wrap(each) methods in SurfaceFragment', 'description': {'raw': \"unwrapNodes & rewrapNodes are not implemented, and wrapNodes doesn't calculate selections correctly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368042225, 'spacePHID': None, 'dateCreated': 1361910180, 'dateModified': 1417573289, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45445', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Checkstyle report unable to fetch context, showing \"No description available. Please upgrade to latest checkstyle version.\"', 'description': {'raw': 'e.g. https://integration.mediawiki.org/ci/job/mwext-Scribunto-jslint/233/checkstyleResult/file.984307183/type.1174449419/\\n\\nIt does that almost everywhere (including VisualEditor and MediaWiki core). Sometimes it does work though, weird.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372185531, 'spacePHID': None, 'dateCreated': 1361834280, 'dateModified': 1372185531, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45395', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Split MediaWiki extension that initiates VE from the VisualEditor itself', 'description': {'raw': 'MW-specific code should be split from the VisualEditor itself; mediawiki/extensions/VisualEditor.git should only be the MW-specific items (integration; MW-specific plugins; MW-specific plugin overloading).\\n\\nTarget repository for VE itself already exists: VisualEditor/core.git\\n\\n(Future plugins should be under VisualEditor/plugin/….git.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387564647, 'spacePHID': None, 'dateCreated': 1361756160, 'dateModified': 1443276410, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45342', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Generalize logic in ve.FormatAction', 'description': {'raw': '* Rules for \"heading should not be in list\" in CE rather than DM\\n* Function that isolates and unwraps things until they conform to the CE rules\\n** FormatAction does these things, but is hardcoded for lists\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363626350, 'spacePHID': None, 'dateCreated': 1361475480, 'dateModified': 1417573341, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45247', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Refactor ve.FormatAction.splitAndUnwrap to use SurfaceFragment', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361839902, 'spacePHID': None, 'dateCreated': 1361474880, 'dateModified': 1417573344, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45246', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Implement remaining wrapAll methods in SurfaceFragment', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361839869, 'spacePHID': None, 'dateCreated': 1361474340, 'dateModified': 1417573344, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45242', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: IME input into an empty slug causes characters to overwrite one another', 'description': {'raw': '**Author:** `visionary.incident`\\n\\n**Description:**\\nI cannot input japanese consecutive characters in the beginning of the line.\\n\\nFirefox version is 18.0.2 .\\n\\nFor example\\n\\ninputed\\nあああああ\\n\\noutputed\\nああ\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1423750103, 'spacePHID': None, 'dateCreated': 1361473320, 'dateModified': 1438734540, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45240', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Increase test coverage of ve.FormatAction', 'description': {'raw': 'We currently have 0 tests for ve.FormatAction.*\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361566138, 'spacePHID': None, 'dateCreated': 1361404500, 'dateModified': 1417573345, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45216', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix dependency issues between ve.js and ve.init.platform', 'description': {'raw': \"In ve.js, function ve.msg:\\n// TODO: Fix dependency issues between ve.js and ve.init.platform\\n\\nI don't know how this should be fixed exactly, Timo put this comment in in 407de829dd8f2e51c22a8378dc70c79fc6645d1e . I did notice that running the VE tests from Special:JavaScriptTest doesn't work because ve.msg() errors out with 've.init.platform' undefined.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1365058343, 'spacePHID': None, 'dateCreated': 1361311500, 'dateModified': 1417573337, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45175', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'AutoLoader adds $IP to network share path', 'description': {'raw': '**Author:** `kevinrose`\\n\\n**Description:**\\nI am running under IIS with the files stored on network storage.\\nI get an error from line 1142 in includes\\\\AutoLoader.php when the $filename being passed is already a network share. Specifically in my case it then adds $IP a second time.\\n\\nHere are the variables from my situation:\\n\\nFrom debugging we know that:\\n$IP is set to \"\\\\\\\\server\\\\share\\\\mediawiki\"\\n\\nThe offending class being loaded in LocalSettings.php:\\n\\nrequire_once(\"$IP/extensions/WikiEditor/WikiEditor.php\" );\\n\\nAfter line 1142 $filename = \"\\\\\\\\server\\\\share\\\\mediawiki\\\\\\\\server\\\\share\\\\mediawiki\\\\extensions\\\\WikiEditor\\\\WikiEditor.php\"\\n\\nLine 1140 checks if the first character is a / (root), or the second character is a : (windows local drive).\\n\\nTo work around the problem I added a third check, that the second character is a slash (windows network share):\\n\\n\\t\\tif ( substr( $filename, 0, 1 ) != \\'/\\' && substr( $filename, 1, 1 ) != \\':\\' && substr( $filename, 1, 1 ) != \\'\\\\\\\\\\') {\\n\\n--------------------------\\n**Version**: 1.20.x\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-5dqihbanu3caaj7pigif', 'dateClosed': 1586895753, 'spacePHID': None, 'dateCreated': 1360770540, 'dateModified': 1586895753, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44953', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid should support passing on an authenticated user's read right (when MW API supports that)\", 'description': {'raw': \"[Very much a longer-term enhancement.]\\n\\nParsoid doesn't currently have support for passing on an authenticated user's read right when fetching the wikitext (because the API doesn't support that yet).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382479475, 'spacePHID': None, 'dateCreated': 1359492240, 'dateModified': 1383678031, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44483', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parsoid (?) issues in deleting text on [[W:User:Edinwiki]]', 'description': {'raw': 'Deleting multiple lines of selected text\\n\\nWhen trying to delete a line of added text, the editor failed. See screenshot.\\n\\nWhen reviewing the changes I get an empty \"Latest revision\" and empty \"Your text\". Tried with Chrome and Firefox. When saving, the changes are not committed either.\\n\\nWhen trying to delete two lines (see screenshot on the right side), only one line is marked for deletion:\\n\\n    - Mostly active on [[:bs:Korisnik:Edinwiki|bs-wiki]].\\n\\nWhen selecting multiple lines in the same way, it seems that each time only the first line is selected.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://en.wikipedia.org/wiki/User:Edinwiki\\n\\n**Attached**: {F10938}'}, 'authorPHID': 'PHID-USER-qaslvze35cdv2crgkxjb', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366396774, 'spacePHID': None, 'dateCreated': 1359113220, 'dateModified': 1366396774, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44340', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link inspector doesn't function properly when opened in location surrounded by word boundaries\", 'description': {'raw': '1. Type 2 spaces\\n2. Move the cursor between the two spaces\\n3. Press link button or (command|control)+k\\n4. Type text for target (if in mw integration you can also choose a suggested target)\\n5. Press enter (or click outside the inspector, or press esc)\\n6. See that the target text was inserted, but not annotated\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360613038, 'spacePHID': None, 'dateCreated': 1358470200, 'dateModified': 1417573348, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44086', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor jumps when backspacing character after alien node', 'description': {'raw': 'Steps to reproduce:\\n1. Find a paragraph that has an inline node (alien or entity) in it, but not at the end\\n2. Move the cursor to the end of the paragraph\\n3. Repeatedly press backspace\\n4. When there is only one remaining character after the inline node, pressing backspace will remove that character (correct) and move the cursor to the beginning of the line (bad)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371780950, 'spacePHID': None, 'dateCreated': 1358461560, 'dateModified': 1417573205, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44078', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Include git submodules, by default, or optionally', 'description': {'raw': 'Some extensions, such as Extension:GuidedTour, require git submodules.\\n\\nIt would be a very useful enhancement if ExtensionDistributor included these in the download, by default or optionally.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement\\n**URL**: https://www.mediawiki.org/wiki/Extension_talk:ExtensionDistributor#Doesn.27t_do_submodules'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406830829, 'spacePHID': None, 'dateCreated': 1358310660, 'dateModified': 1406830829, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44022', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Diff viewer in weird state after Parsoid error', 'description': {'raw': 'Steps to reproduce:\\n1. Open VE on a page\\n2. Make changes\\n3. Stop Parsoid\\n4. Click \"Review and save\"\\n5. Get an error dialog about Parsoid being down. Click \"Cancel\".\\n\\nThe box that\\'s supposed to show the diff is left empty, but the \"Something\\'s wrong\" and \"Looks good to me\" buttons are still there. I can dismiss the box with the up arrow to go back to editing, but we should be doing this (or at least *something*) automatically on failure.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392756925, 'spacePHID': None, 'dateCreated': 1357693020, 'dateModified': 1417573133, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43753', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create API to expose editnotices', 'description': {'raw': \"Editnotices for pages are not currently exposed in the API, but are expected to be used by any interface of a Wikipedia  editor. This implies that the information should be easily retrievable.\\n\\nIt should be noted that the VisualEditor api has it's own private implementation of listing all edit notices that should be presented to users: https://en.wikipedia.org/w/api.php?action=visualeditor&format=json&paction=metadata&page=List_of_emoticons&uselang=en&oldid=846338965\\n\\nThis should probably be moved to core as well as be exposed via restbase or something similar.\\n\\n--------------------------\\n**Version**: 1.21.x\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-a6jwrurphpx6yl4coupk', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1684603866, 'spacePHID': None, 'dateCreated': 1357492860, 'dateModified': 1684603866, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43683', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Link translatable help pages on mediawiki.org from the relevant special pages, actions etc.', 'description': {'raw': \"The Translate extension has very nice info icons which bring users from the interface/feature they're seeing to the relevant (translatable) help page on mediawiki.org (all components are documented). See for instance [[ https://meta.wikimedia.org/wiki/Special:PageTranslation | m:Special:PageTranslation ]].\\n\\nThis is a huge task, but it should be done for core as well.\\n\\nThe problem is of course that there's no real(istic) plan to get such help pages done in the next few decades, as they continue to live either on Meta for copyright reasons or even on local wikis for the same + [[ https://meta.wikimedia.org/wiki/Not_my_wiki | m:Not my wiki]] syndrome. This part of the problem should be discussed on wiki, probably the talk of the project.\\n\\n--------------------------\\n**URL**: https://www.mediawiki.org/wiki/Project:PD_help\\n**See Also**:\\n{T19557}\\n{T14306}\\n{T46286}\"}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'dateClosed': 1433346304, 'spacePHID': None, 'dateCreated': 1357145040, 'dateModified': 1731271901, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43591', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parser misinterprets en.wikipedia Infobox (inline \"style\" attribute ends up in text nodes)', 'description': {'raw': 'Screenshot of bug and edit screens\\n\\nNative parser rendering:\\nthe Netherlands\\n\\nParsoid/VisualEditor rendering:\\nstyle=\"font-size: larger; font-weight: bold\" | the Netherlands\\n\\n[[Flag of the Kingdom of the Netherlands]]:\\n{{Infobox flag\\n| Name = the Netherlands\\n...\\n\\n[[Template:Infobox flag]]:\\n> {| class=\"infobox\" style=\"width: 22em; font-size:88%; text-align:left; line-height: 1.5em\"\\n|+ style=\"font-size: larger; font-weight: bold\" | <br>{{{Name|{{PAGENAME}}}}}\\n|-\\n...\\n\\n\\nSee attachment for rendering.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F10351}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358293142, 'spacePHID': None, 'dateCreated': 1357121460, 'dateModified': 1358293142, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43582', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Mouse leaving a phantom and also the .ve-surface DIV area causes phantom to remain', 'description': {'raw': 'Hovering over an uneditable element in VisualEditor makes the element be covered by green stripes until the mouse is moved away, but when the cursor moves directly to the sidebar or the right margin, the stripes stay there until some part of the .ve-surface is hovered over.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361487636, 'spacePHID': None, 'dateCreated': 1356609300, 'dateModified': 1417573346, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43461', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Sometimes the HotCat gadget appears at the top of the CE surface', 'description': {'raw': \"From user report (but I've had this myself):\\n\\n| HotCat is a popular gadget and any conflict with it should be avoided. For\\n| example, use VisualEditor on [[User:This, that and the other/sandbox/Schfoof]]\\n| with HotCat enabled. The HotCat bar appears in the wrong place. (It probably\\n| shouldn't appear at all.)\\n|\\n| …\\n|\\n| The conflict now appears to be fixed... very strange.\\n\\nGiven that it appears and also doesn't appear between refreshes - i.e., on the same page with the same version of the VE and HC code bases in the same accounts in the same browsers - I'm assuming it's some sort of race-condition, but I'm not sure.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414009552, 'spacePHID': None, 'dateCreated': 1356129540, 'dateModified': 1417596420, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43335', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add a (small) left margin to the CE so that users can select whole lines at once', 'description': {'raw': 'From a user suggestion:\\n\\n| Normally word processors and text editors have a left margin, allowing\\n| whole lines to be selected. There would normally be a small gap of a few\\n| pixels between the left column of text and the left margin, allowing a\\n| \"margin of error\" for regular text selection. To the left of this gap,\\n| any clicks select entire lines, and any drags up or down select many\\n| lines at once. \\n|\\n| I don\\'t know if there is a need for the complete left margin\\n| functionality in VisualEditor, but certainly, the editing area shouldn\\'t\\n| stop at the exact edge of the letters. Perhaps the padding on the VE\\n| container needs to be increased with a compensating decrease in the\\n| margin - or maybe that\\'s totally wrong, but you get the idea.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369426246, 'spacePHID': None, 'dateCreated': 1356128220, 'dateModified': 1417573223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43333', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting content between a heading and an alien fails?', 'description': {'raw': 'In https://en.wikipedia.org/w/index.php?title=Lynn_Hill&oldid=528045441 (and other versions), go into VE, go to the bottom, delete the list item (and so the list) from the External links section.\\n\\nve.instances[0].documentModel.data confirms that the model has this removed - \"/heading\" object followed by the alienated table from the \"{{Authority control}}\" template - but on diff Parsoid thinks that there is no change in this area. Is this is a Parsoid, or is change marking broken (or both)?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1359143154, 'spacePHID': None, 'dateCreated': 1355510820, 'dateModified': 1359143154, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43135', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to add/edit imagemaps', 'description': {'raw': '<imagemap>....</imagemap> is unparsed but shown as plain wikitext:\\nhttps://en.wikipedia.org/wiki/User:Raymond/imagemap\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/wiki/User:Raymond/imagemap'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1355487780, 'dateModified': 1643977451, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43127', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to add/edit SyntaxHighlight blocks', 'description': {'raw': 'Support <syntaxhighlight> tag too. It is a synonym to <source> which works already\\n\\nhttps://en.wikipedia.org/wiki/User:Raymond/source\\n\\nSee https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/SyntaxHighlight_GeSHi.git;a=blob;f=SyntaxHighlight_GeSHi.php#l67 for the definiton of the parser hooks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/wiki/User:Raymond/source'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1435183429, 'spacePHID': None, 'dateCreated': 1355486220, 'dateModified': 1660398891, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43126', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Second column heading missing of table with template-generated header', 'description': {'raw': 'Screenshot showing the regular view, visualeditor view and wikitext\\n\\nSteps to reproduce problem:\\n* Open VisualEditor on https://en.wikipedia.org/wiki/Buri_Ram_Airport\\n\\nExpected result:\\nTable has header on both columns.\\n\\nActual result:\\nHeader of second column is missing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9595}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1359417431, 'spacePHID': None, 'dateCreated': 1355443620, 'dateModified': 1372933991, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43104', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Elements nested inside Aliens with z-index appear on top of the zebra pattern', 'description': {'raw': \"Try editing the page [[:en:Buri_Ram_Airport]] with VisualEditor. Mouse over the infobox. There's an element that sticks above the alien marking, because it has a z-index attribute.\\n\\nI don't know how best to fix this, I assume it would be bad to simply set z-index=1000 and be on your way, but it's an inconsistent appearance and something to be fixed eventually.\\n\\nI suspect this may also be a good beginner bug, so if someone from the VE team can mark this as easy, then we can leave it for a newcomer.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://en.wikipedia.org/wiki/Buri_Ram_Airport\"}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355696389, 'spacePHID': None, 'dateCreated': 1355441880, 'dateModified': 1417573352, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43098', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a visual VisualEditor plugin tool to add/edit maths blocks', 'description': {'raw': 'Math is editable, but only as plain LaTeX like in the wikitext editor: https://en.wikipedia.org/wiki/User:Raymond/Math\\n\\n{F199473}\\nFigure 1: Current non visual visual editor'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1355386860, 'dateModified': 1592976212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43058', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Review window behind article', 'description': {'raw': '**Author:** `jnichols`\\n\\n**Description:**\\nI can only see the very top few lines of the review-and-save window, the notices window, and the edit summary window. The rest of them seem to be behind the article window. I can scroll down the review window, looking at it three lines at a time in the little area between the top of the article and the tabs. The notices window and the edit summary windows don\\'t scroll, which means I can\\'t get down to the final \"save\" button.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366174654, 'spacePHID': None, 'dateCreated': 1355378580, 'dateModified': 1417573335, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43054', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: edits marked as \"minor\" without explicit user selection', 'description': {'raw': 'See http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Marking_edits_as_minor for the report and http://en.wikipedia.org/w/index.php?title=Ginger_nut&diff=527654509&oldid=526997552 as an example.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355374103, 'spacePHID': None, 'dateCreated': 1355346240, 'dateModified': 1417573352, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43040', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Deal with en.wikipedia.org's edit notice system\", 'description': {'raw': 'There is only one notice, but it says there are 2!\\n\\nSee the screenshot and also\\nhttps://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&diff=527687053&oldid=527683727\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61335\\n\\n**Attached**: {F10115}'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410207320, 'spacePHID': None, 'dateCreated': 1355324760, 'dateModified': 1507707751, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43013', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Automatically convert external links to local resources to local wiki links if possible', 'description': {'raw': 'Like this: https://www.mediawiki.org/w/index.php?title=VisualEditor:Test&diff=615802&oldid=615801\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1355298420, 'dateModified': 1643977451, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42986', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Retries when badtoken happened should request new tokens', 'description': {'raw': 'When I\\'m using VisualEditor, session failed for unknown reason. The VisualEditor then keep asking whether I want to try again but it always tries with the old token and error \"badtoken\" keeps coming.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369080457, 'spacePHID': None, 'dateCreated': 1355292720, 'dateModified': 1417573275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42984', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save button should be disabled if dm state is identical to page when it was loaded', 'description': {'raw': \"Right now, the Save button starts disabled, but when the transaction depth is non-zero it's enabled. This means that two actions that reverse each other (rather than being formally undone) let the user make a 'null edit', which MW then silently accepts.\\n\\nIdeally, the Save/Create button should be disabled if dm state is identical to page when it was loaded (except for the special-case of oldid pages, where it should always be enabled). Roan suggests a string comparison of the current and original HTML is the least-bad option, given the lack of hash functions in JavaScript.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=43270\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363370183, 'spacePHID': None, 'dateCreated': 1355199480, 'dateModified': 1417573340, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42939', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: HTML entities following double-bracket links are not displayed correctly', 'description': {'raw': 'Try to VE-edit this page: http://www.mediawiki.org/wiki/VisualEditor:Extension:ConfirmAccount\\n\\nCompare: http://parsoid.wmflabs.org/mw/VisualEditor:Extension:ConfirmAccount\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361383659, 'spacePHID': None, 'dateCreated': 1355068140, 'dateModified': 1417573346, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42897', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting multiple empty paragraphs results in selection decreasing by one line per poll interval', 'description': {'raw': 'Steps to reproduce:\\nEdit a page with VisualEditor.\\nPress return key a few times.\\nSelect those empty lines with mouse or shift+arrows.\\nWatch in awe as the selected lines decrease one per polling interval.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354844641, 'spacePHID': None, 'dateCreated': 1354835520, 'dateModified': 1417573355, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42801', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector suggestions highlight multiple items if they have the same label', 'description': {'raw': 'Reproduce:\\n\\n1. Make a link to http://www.google.com\\n2. Click out of the link\\n3. Inspect the link\\n4. Both new page and external link are selected\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354652046, 'spacePHID': None, 'dateCreated': 1354583100, 'dateModified': 1417573359, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42665', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Context menu shows up in the wrong place on load if document starts with link', 'description': {'raw': \"When a document starts with a link, the animation on the page cause the context's location to be incorrect.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354589382, 'spacePHID': None, 'dateCreated': 1354572300, 'dateModified': 1417573360, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42661', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Leading newlines in <pre>s get eaten', 'description': {'raw': 'https://www.mediawiki.org/w/index.php?title=VisualEditor%3APre&diff=609875&oldid=609874\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354757611, 'spacePHID': None, 'dateCreated': 1353980580, 'dateModified': 1417573357, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42469', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After clicking out of link inspector, pressing enter removes wrong text', 'description': {'raw': '1. Type the text \"Foo bar baz\"\\n2. Select \"bar\"\\n3. Click the link toolbar button\\n4. Click between the a and the z (\"ba|z\") to cause the inspector to close\\n5. Press enter\\n\\nExpected result: paragraph is split with \"z\" in a new paragraph\\nActual result: \"bar\" is removed, paragraph is split with \"baz\" in a new paragraph\\n\\nOccurs in both Firefox and Chrome. Isn\\'t reproducible 100% of the time.\\n\\nTheory:\\n1. User changes selection to ba|z\\n2. SurfaceObserver notices and adjusts its selection\\n3. Link inspector notices and triggers annotation on a fragment with a different range (the link)\\n4. Some bug in SurfaceObserver or SurfaceFragment causes SO to believe the current selection is now the link\\n5. User presses enter, SO removes what it believes is the selection\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353971697, 'spacePHID': None, 'dateCreated': 1353378540, 'dateModified': 1417573395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42278', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Zero-length selection in link should show inspector icon', 'description': {'raw': 'This currently works for selections within links, but not for zero-length selections. Except if you hit bug 42275, then the inspector icon will appear on every zero-length selection, anywhere, and will chase you forever and ever.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353971278, 'spacePHID': None, 'dateCreated': 1353376860, 'dateModified': 1417573396, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42276', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't offer Edit button when user cannot edit page\", 'description': {'raw': 'The VisualEditor interface does not currently recognize page protection. If a user visits a protected page (a page to which he or she does not have access to edit), VisualEditor will still display a working edit form and the first click of the \"Save page\" button will work. It will produce a dialog box that will present a second \"Save page\" button that does not work. Ideally, VisualEditor would not let a user get this far without indicating that the page is uneditable.\\n\\nRelated to this, there\\'s no warning for administrators that a page is protected when they\\'re editing the page. This may be a separate bug, however.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354131981, 'spacePHID': None, 'dateCreated': 1352958960, 'dateModified': 1417573393, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42142', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Internal page links touched by VisualEditor contain underscores', 'description': {'raw': 'Currently when a user uses the link dialog box tool thing in VisualEditor to specify where certain text should link to, if the user specifies an internal page as the target, the wikitext for the link will use underscores.\\n\\nFor example, I highlight some text in VisualEditor with my mouse and then click the link icon. A \"Hyperlink\" dialog box appears and I enter \"MediaWiki on IRC\" into the text input area. I hit the \"return\" key on my keyboard to make the dialog box disappear and now I have a blue link in my VisualEditor interface. If I then save this page and look at its wikitext source, I see:\\n\\n[[MediaWiki_on_IRC|fffffffff]]\\n\\nInternal links are using underscores. This is wrong.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49310'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353380505, 'spacePHID': None, 'dateCreated': 1352957940, 'dateModified': 1417573199, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42140', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: There is not preview of edit summaries (which are wikitext) - show it in the wikitext diff?', 'description': {'raw': 'The current VisualEditor interface has a \"Save page\" dialog box with an edit summary input field. However, this edit summary input field accepts wikitext, but has no preview feature for what the rendered wikitext will look like. This is a regression from the standard (non-VisualEditor) interface.\\n\\nRoan said that there be a mini-editor or mini-parser or something stuck in the edit summary area at some point.\\n\\n**See Also**: {T62535}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392853679, 'spacePHID': None, 'dateCreated': 1352957640, 'dateModified': 1465905460, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42139', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pressing a list button when covering a selection of a list should unlist only that portion', 'description': {'raw': 'Pressing a list button on: \\n\\n1. Foo\\n2. Bar\\n   * Baz\\n   * Bang\\n     1. Boom\\n3. Bing!\\n\\nwith a selection of Bang and Boom should produce:\\n\\n1. Foo\\n2. Bar\\n   * Baz\\n     Bang\\n     Boom\\n3. Bing!\\n\\n(i.e. the selected LIs should be down-converted into a <P> of the most local parent list).\\n\\nAlso, out-dent should stop a list nest level 1, not 0.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1352498880, 'dateModified': 1437759568, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41935', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"List\" buttons causes whole list to be de-listed, or converted to other list type, when only part of it is selected', 'description': {'raw': 'Expected behaviour is that the part of the list that is selected is transformed, and the rest of the list is left as it was.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354589338, 'spacePHID': None, 'dateCreated': 1352482200, 'dateModified': 1417573360, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41929', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Highlighting syntax within editing window by default', 'description': {'raw': \"**Author:** `IJethrobot`\\n\\n**Description:**\\nHaving read <https://bugzilla.wikimedia.org/show_bug.cgi?id=16268> and <https://bugzilla.wikimedia.org/show_bug.cgi?id=11627>, this enhancement proposal is sufficiently different and is based on different discussion.\\n\\nThere is a wide consensus of editors who would like to see syntax highlighting in the standard editing window turned on by default, particularly for references, for wiki markup.  This consensus has been reached in two discussions on en.wiki, one at the Village Pump <http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_92#Differentiating_reference_syntax_in_the_editing_window.> and one in a Request For Comments that was a part of Centralized Discussion for 30 days:  <http://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment/Syntax_differentiation_in_editing_window>.  Given the course of the discussion, and the overwhelming support for this functionality, I decided to submit this proposal to bugzilla.  \\n\\nMany participants in the above discussions expressed that adding a syntax highlighter would make editing a more accessible experience for newer users.  In fact, direct feedback from new editors has suggested that this has been a problem (e.g. <http://en.wikipedia.org/wiki/Special:FeedbackDashboard/46104>).  They are also unsatisfied with \\n\\nPrevious proposals have stated that implementing this internally is not possible.  However, this is incorrect; there are at least some examples of non-external editors that work or could work reasonably well:\\n- jsfiddle:  <http://jsfiddle.net/> (with implementation: <http://doc.jsfiddle.net/>)\\n- AceWikiEditor:  <http://no.wikipedia.org/wiki/Hjelp:AceWikiEditor>\\n- en.wikipedia user RememberTheDot's syntax highlighter: <http://meta.wikimedia.org/wiki/User:Remember_the_dot/Syntax_highlighter> (which I use).\\n\\nThe only thing I would have liked to see more of in the above discussions were persons who might be able to discuss a specific implementation.  Some discussion of that is here: <http://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment/Syntax_differentiation_in_editing_window#Implementation>.  Such discussion would be helpful here, given the above information on how it may be viable to implement this internally.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1352058259, 'spacePHID': None, 'dateCreated': 1352053440, 'dateModified': 1416220518, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41770', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create simple interface for adding a page redirect to MediaWiki core', 'description': {'raw': 'Splitting this off from bug 27311 (in light of bug 27683 comment 5).\\n\\nMediaWiki core should have a \"create a redirect\" form. The current system is painfully unintuitive. It requires first figuring out how to create a page at all and then figuring out that you need special \"#REDIRECT [[ ]]\" syntax. Some people make the argument that this toughens people up and prepares them for the wikitext world. I believe that a form really wouldn\\'t kill us here.\\n\\nMoving a page is sort of a form for making a redirect, but that requires a page already existing. In this bug, we want a form, in MediaWiki core, for creating a redirect. Special:CreatePage or Special:CreateRedirect or something.\\n\\nThis bug might be a dupe of bug 27311, but we can\\'t really know until someone actually implements one or the other.\\n\\n**See Also**: T29311 T59315'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1351128360, 'dateModified': 1610566301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41363', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[mediawiki.feedback.js] Add checkbox to submit user-agent info', 'description': {'raw': \"resources/mediawiki/mediawiki.feedback.js is a little-known built-in software feedback feature that's used by a couple of extensions, notably UploadWizard and VisualEditor.\\n\\nIt posts feedback to a wiki page. It used to also post user-agent information for debugging alongside the feedback. The user-agent information from posted feedback was removed in:\\n\\nhttps://gerrit.wikimedia.org/r/#/c/26417/\\n\\nWhile the fact that user-agent information is published was disclosed, there was concern that it would be preferable to add an explicit checkbox. The following text has been vetted by legal:\\n\\n[ ] I understand that my user agent information includes information about my exact browser and operating system version and will be shared publicly alongside my feedback. I agree to provide feedback in accordance with the Terms of Use. \\n\\nOn WMF sites, that would link to https://wikimediafoundation.org/wiki/Terms_of_Use - not sure we have a standard MW message that would apply here.\\n\\n--------------------------\\n**Version**: 1.21.x\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=33365\"}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1425406653, 'spacePHID': None, 'dateCreated': 1350950160, 'dateModified': 1442559444, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41291', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor misplaced after clicking on nowiki block', 'description': {'raw': '= Heading 1a =\\n<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>\\n\\n== Heading 2aa ==\\n\\n1) Open http://www.mediawiki.org/wiki/VisualEditor:Test\\n2) Click within the nowiki block\\n3) Press Left\\nProblem: Cursor is now at top of page\\n\\nRepeating from step 2, the cursor then appears in various places.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360206039, 'spacePHID': None, 'dateCreated': 1350626220, 'dateModified': 1417573350, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41205', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clicking at the left of a wikicode block does not put the cursor there.', 'description': {'raw': 'With this wikicode\\n\\n= Heading 1a =\\n<nowiki>[[File:VectorEditorBasic-en.png]]</nowiki>\\n\\n== Heading 2aa ==\\n\\n\\nProblem: Clicking at the left of the wikicode block does not put the cursor there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360795517, 'spacePHID': None, 'dateCreated': 1350615240, 'dateModified': 1417573347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41199', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Link targets and display are corrupted when removing annotations from part of the link', 'description': {'raw': 'See https://www.mediawiki.org/w/index.php?title=VisualEditor:LinkTrailReEditBug&diff=594998&oldid=594997&vewhitelist\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360171044, 'spacePHID': None, 'dateCreated': 1350557700, 'dateModified': 1360171044, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41161', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Position of VisualEditor\\'s \"Create\" tab is wrong', 'description': {'raw': 'See [[mw:VisualEditor:ThisPageDoesNotExist]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354565326, 'spacePHID': None, 'dateCreated': 1350557100, 'dateModified': 1417573389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41159', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Click-dragging of media items to move them', 'description': {'raw': 'It might be impossible to implement, but I am sure many users will wonder why it does not work, so here is the idea:\\n\\n1) Select some text with the mouse\\n2) Press the mouse over the selected text\\n3) While staying pressed, move the mouse to somewhere else, then release the mouse button.\\n\\nExpected: The text is cut-pasted from origin to destination.\\nActual: Nothing happens.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-qmcrs2npimuywblubznv', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371851883, 'spacePHID': None, 'dateCreated': 1350544500, 'dateModified': 1417573202, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41150', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add support for adding dir/lang attributes to paragraphs and similar arbitrary elements (div, p, lists etc.)', 'description': {'raw': 'In MediaWiki pages it is frequently required to write some text in a different languages, and possibly also with different directionality. For example, an quotation in English in an article in the Hebrew Wikipedia.\\n\\nWith the plain wikitext editor this can be achieved using HTML, for example <span lang=\"en\" dir=\"ltr\">. In some Wikipedias there are templates that do this.\\n\\nThere must be a way to do this using the VE GUI. For example, the user can select the text in a different language, open a dialog with \"Language properties\" and select \"English language\" and \"Directionality: Left-to-right\".\\n\\nFor reference and further details:\\nhttps://www.mediawiki.org/wiki/VisualEditor/Bidirectional_text_requirements\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1350148140, 'dateModified': 1691590946, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41009', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Only show minor edit option if user has \"minoredit\" right', 'description': {'raw': 'Right now the \"This is a [minor edit]\" text in the save dialog appears whether or not you are logged in, which is incorrect behaviour compared to the current editor\\'s save process, and is meaningless (anons can\\'t have edits marked as minor).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354577109, 'spacePHID': None, 'dateCreated': 1349380320, 'dateModified': 1417573388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40774', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector: Width of suggested titles too short', 'description': {'raw': 'The width of suggested titles in the link inspector is too short for practical purposes, see: http://imgur.com/cJEnn\\n\\nIn production wikis like en.wp this will be an issue with titles that are long and hard to disambiguate, e.g. \"List of countries by GDP (nominal) per capita\" vs. \"List of countries by GDP (PPP) per capita\", which would both be abbreviated to \"List of cou...per capita\".\\n\\nPerhaps the dropdown could dynamically expand in a similar manner to the search box suggestions.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354304666, 'spacePHID': None, 'dateCreated': 1349129640, 'dateModified': 1417573391, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40675', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: High-res icons don't display if small screen is resized to large\", 'description': {'raw': \"Broken out from bug 37849: window.devicePixelRatio is checked when loading stuff, and then either a stylesheet for 1.0x PNGs or one using scalable SVGs gets loaded depending on the ratio.\\n\\nThis leads to being stuck with the 1.0x PNGs if you started editing on a low-resolution screen, then moved the window (or detached an external monitor) and moved it to a high-resolution screen.\\n\\nPer bug 37849 comment 9 there are probably two ways to fix this:\\n\\n1) Detect resolution changes (window.onresize?) and switch the stylesheet based on the updated window.devicePixelRatio\\n\\nor\\n\\n2) Always use SVG icon set if SVG is supported in the browser.\\n\\nNote that Firefox doesn't yet support window.devicePixelRatio, but it's about to come in in nightlies, before actual HiDPI support for Mac OS X :) -- https://bugzilla.mozilla.org/show_bug.cgi?id=564815\\n\\nIE 10 doesn't support window.devicePixelRatio at all, which is a bit annoying although it does support SVG and high-resolution screens eg on Windows 8. We can leave that as a corner case for the moment, though use of SVG at all resolutions would conveniently work around it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368811438, 'spacePHID': None, 'dateCreated': 1347307920, 'dateModified': 1417573279, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40140', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links in the CE surface should have the \"cursor:pointer;\" CSS attribute', 'description': {'raw': 'Suggested by a user.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380214425, 'spacePHID': None, 'dateCreated': 1346774040, 'dateModified': 1417573269, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39976', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Scap doesn't build use correct extension versions on deployment of new versions\", 'description': {'raw': \"I've been noticing this for a while, but I'm not quite sure why...\\n\\nI have put in a copy of the ExtensionMessages file from the old version to the newer one, but that uses $IP...\\n\\n\\nOn the first run of scap after adding a new version, we get a weird output:\\n\\nUpdating ExtensionMessages-1.20wmf10.php...\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/AbuseFilter/AbuseFilter.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiBot/AntiBot.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiSpoof/AntiSpoof.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ApiSandbox/ApiSandbox.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedback/ArticleFeedback.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/AssertEdit/AssertEdit.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Babel/Babel.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CategoryTree/CategoryTree.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralAuth/CentralAuth.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralNotice/CentralNotice.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CharInsert/CharInsert.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CheckUser/CheckUser.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/Cite.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/SpecialCite.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/cldr/cldr.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClientSide/ClientSide.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClickTracking/ClickTracking.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeEditor/CodeEditor.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeReview/CodeReview.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Collection/Collection.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Contest/Contest.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityApplications/CommunityApplications.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityHiring/CommunityHiring.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityVoice/CommunityVoice.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/ConfirmEdit.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/FancyCaptcha.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPage/ContactPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPageFundraiser/ContactPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionReporting/ContributionReporting.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionTracking/ContributionTracking.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/DisableAccount/DisableAccount.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/DismissableSiteNotice/DismissableSiteNotice.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/DonationInterface/donationinterface_langonly.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/DoubleWiki/DoubleWiki.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/E3Experiments/Experiments.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Echo/Echo.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/EditPageTracking/EditPageTracking.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/EducationProgram/EducationProgram.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/EmailCapture/EmailCapture.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExpandTemplates/ExpandTemplates.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExtensionDistributor/ExtensionDistributor.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/FeaturedFeeds/FeaturedFeeds.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/FlaggedRevs/FlaggedRevs.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/FormPreloadPostCache/FormPreloadPostCache.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/FundraiserLandingPage/FundraiserLandingPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Gadgets/Gadgets.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/GeoData/GeoData.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalBlocking/GlobalBlocking.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalUsage/GlobalUsage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ImageMap/ImageMap.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/InputBox/InputBox.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/intersection/DynamicPageList.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Interwiki/Interwiki.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LabeledSectionTransclusion/lst.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LandingCheck/LandingCheck.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LastModified/LastModified.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LiquidThreads/LiquidThreads.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LocalisationUpdate/LocalisationUpdate.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MarkAsHelpful/MarkAsHelpful.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MoodBar/MoodBar.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MobileFrontend/MobileFrontend.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MwEmbedSupport/MwEmbedSupport.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MWSearch/MWSearch.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Narayam/Narayam.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/NewUserMessage/NewUserMessage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Nuke/SpecialNuke.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/OAI/OAIRepo.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/OggHandler/OggHandler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/OpenSearchXml/OpenSearchXml.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Oversight/HideRevision.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/PagedTiffHandler/PagedTiffHandler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/PageTriage/PageTriage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ParserFunctions/ParserFunctions.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/PdfHandler/PdfHandler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Poem/Poem.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/PoolCounter/PoolCounterClient.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ProofreadPage/ProofreadPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Quiz/Quiz.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/RandomRootPage/Randomrootpage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ReaderFeedback/ReaderFeedback.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Renameuser/Renameuser.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/RSS/RSS.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ScanSet/ScanSet.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Scribunto/Scribunto.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SecurePoll/SecurePoll.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ShortUrl/ShortUrl.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleAntiSpam/SimpleAntiSpam.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleSurvey/SimpleSurvey.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SiteMatrix/SiteMatrix.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SkinPerPage/SkinPerPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Schulenburg/Schulenburg.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Tomas/Tomas.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SpamBlacklist/SpamBlacklist.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SubPageList3/SubPageList3.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SwiftCloudFiles/SwiftCloudFiles.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/UserThrottle/UserThrottle.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TimedMediaHandler/TimedMediaHandler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/timeline/Timeline.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleBlacklist/TitleBlacklist.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleKey/TitleKey.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TorBlock/TorBlock.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Translate/Translate.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TranslationNotifications/TranslationNotifications.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TrustedXFF/TrustedXFF.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/UnicodeConverter/UnicodeConverter.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadBlacklist/UploadBlacklist.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadWizard/UploadWizard.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Vector/Vector.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiEditor/WikiEditor.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsScaler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsTest.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/VisualEditor/VisualEditor.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WebFonts/WebFonts.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/wikihiero/wikihiero.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiLove/WikiLove.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaIncubator/WikimediaIncubator.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaLicenseTexts.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaMessages.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaShopLink/WikimediaShopLink.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php\\n\\nUpdating LocalisationCache for 1.20wmf10... done\\nUpdating ExtensionMessages-1.20wmf11.php...\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/AbuseFilter/AbuseFilter.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiBot/AntiBot.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/AntiSpoof/AntiSpoof.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ApiSandbox/ApiSandbox.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedback/ArticleFeedback.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/AssertEdit/AssertEdit.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Babel/Babel.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CategoryTree/CategoryTree.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralAuth/CentralAuth.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CentralNotice/CentralNotice.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CharInsert/CharInsert.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CheckUser/CheckUser.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/Cite.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Cite/SpecialCite.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/cldr/cldr.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClientSide/ClientSide.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ClickTracking/ClickTracking.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeEditor/CodeEditor.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CodeReview/CodeReview.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Collection/Collection.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Contest/Contest.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityApplications/CommunityApplications.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityHiring/CommunityHiring.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/CommunityVoice/CommunityVoice.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/ConfirmEdit.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ConfirmEdit/FancyCaptcha.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPage/ContactPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContactPageFundraiser/ContactPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionReporting/ContributionReporting.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ContributionTracking/ContributionTracking.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/DisableAccount/DisableAccount.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/DismissableSiteNotice/DismissableSiteNotice.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/DonationInterface/donationinterface_langonly.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/DoubleWiki/DoubleWiki.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/E3Experiments/Experiments.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Echo/Echo.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/EditPageTracking/EditPageTracking.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/EducationProgram/EducationProgram.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/EmailCapture/EmailCapture.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExpandTemplates/ExpandTemplates.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ExtensionDistributor/ExtensionDistributor.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/FeaturedFeeds/FeaturedFeeds.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/FlaggedRevs/FlaggedRevs.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/FormPreloadPostCache/FormPreloadPostCache.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/FundraiserLandingPage/FundraiserLandingPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Gadgets/Gadgets.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/GeoData/GeoData.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalBlocking/GlobalBlocking.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/GlobalUsage/GlobalUsage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ImageMap/ImageMap.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/InputBox/InputBox.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/intersection/DynamicPageList.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Interwiki/Interwiki.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LabeledSectionTransclusion/lst.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LandingCheck/LandingCheck.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LastModified/LastModified.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LiquidThreads/LiquidThreads.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/LocalisationUpdate/LocalisationUpdate.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MarkAsHelpful/MarkAsHelpful.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MoodBar/MoodBar.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MobileFrontend/MobileFrontend.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MwEmbedSupport/MwEmbedSupport.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/MWSearch/MWSearch.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Narayam/Narayam.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/NewUserMessage/NewUserMessage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Nuke/SpecialNuke.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/OAI/OAIRepo.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/OggHandler/OggHandler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/OpenSearchXml/OpenSearchXml.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Oversight/HideRevision.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/PagedTiffHandler/PagedTiffHandler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/PageTriage/PageTriage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ParserFunctions/ParserFunctions.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/PdfHandler/PdfHandler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Poem/Poem.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/PoolCounter/PoolCounterClient.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ProofreadPage/ProofreadPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Quiz/Quiz.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/RandomRootPage/Randomrootpage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ReaderFeedback/ReaderFeedback.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Renameuser/Renameuser.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/RSS/RSS.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ScanSet/ScanSet.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Scribunto/Scribunto.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SecurePoll/SecurePoll.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ShortUrl/ShortUrl.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleAntiSpam/SimpleAntiSpam.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SimpleSurvey/SimpleSurvey.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SiteMatrix/SiteMatrix.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SkinPerPage/SkinPerPage.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Schulenburg/Schulenburg.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/skins/Tomas/Tomas.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SpamBlacklist/SpamBlacklist.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SubPageList3/SubPageList3.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SwiftCloudFiles/SwiftCloudFiles.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/UserThrottle/UserThrottle.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TimedMediaHandler/TimedMediaHandler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/timeline/Timeline.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleBlacklist/TitleBlacklist.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TitleKey/TitleKey.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TorBlock/TorBlock.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Translate/Translate.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TranslationNotifications/TranslationNotifications.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/TrustedXFF/TrustedXFF.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/UnicodeConverter/UnicodeConverter.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadBlacklist/UploadBlacklist.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/UploadWizard/UploadWizard.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/Vector/Vector.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiEditor/WikiEditor.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsScaler.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/VipsScaler/VipsTest.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/VisualEditor/VisualEditor.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WebFonts/WebFonts.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/wikihiero/wikihiero.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikiLove/WikiLove.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaIncubator/WikimediaIncubator.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaLicenseTexts.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaMessages/WikimediaMessages.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/WikimediaShopLink/WikimediaShopLink.php\\nLoading data from /home/wikipedia/common/php-1.20wmf10/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php\\n\\nUpdating LocalisationCache for 1.20wmf11... done\\n\\n\\n\\nUpon the second run, it seems to work fine (but necessitates 2 runs of scap)..\\n\\nWill post output when I get round to it\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1357150957, 'spacePHID': None, 'dateCreated': 1346688240, 'dateModified': 1420738824, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39944', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Switch post-edit feedback to use Extension:PostEdit (once that's core-ified)\", 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375140242, 'spacePHID': None, 'dateCreated': 1345842600, 'dateModified': 1417573271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39632', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Refactor VisualEditor editing plugin for Cite back into the Cite extension', 'description': {'raw': 'Depends on VisualEditor having a (stable) API. As soon as it is considered stable enough, we can implement support for it in the Cite extension using whatever hook/api it offers.\\n\\nAlso needs detection since there are (obviously) wikis that have Cite but not VisualEditor. So probably some conditionally loaded module.'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1454611525, 'spacePHID': None, 'dateCreated': 1345821600, 'dateModified': 1454611615, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39621', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"jquery.wikiEditor.dialogs: 'missing' and 'invalid' properties should check against undefined instead of truthy\", 'description': {'raw': 'See module\\'s code at https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/WikiEditor.git;a=blob;f=modules/jquery.wikiEditor.dialogs.config.js;h=76a3a57e27b6b7d87266171c26baf2a82d9f703a;hb=e7a0484eb56d72e5326282a54288580fdfcd144f\\n\\nThe if conditions at lines 201 and 203 must probably be corrected.\\n\\nfrom :  if ( page.missing )\\nto   :  if ( page.missing !== undefined )\\n\\nand\\n\\nfrom :  if ( page.invalid )\\nto   :  if ( page.invalid !== undefined )\\n\\nThis code checks the api query result,\\nwhich, for instance, has\\n    page.missing === \"\"\\nif queried title doesn\\'t exist.\\n\\nAs it is, the \"Insert link\" dialog shows \"Page exists\"\\nfor every title inserted in the \"Target page or URL:\" field.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-6dh2mmgw4sia7dmkixtb', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1344362215, 'spacePHID': None, 'dateCreated': 1344312120, 'dateModified': 1459675238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39091', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved\", 'description': {'raw': 'To reproduce, go to http://www.mediawiki.org/wiki/VisualEditor:Sandbox?veaction=edit , blank the page, save, then you get \"Error saving data to server: ...\" without too much explaination.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50475\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=43147\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63149'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1344201000, 'dateModified': 1643977455, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39057', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Full protection expiry should not affect semi-protection', 'description': {'raw': '**Author:** `jack`\\n\\n**Description:**\\nSometimes, it is necessary to fully protect a page which is already semi-protected. Often, the reason for the different protections is different (vandalism and edit warring is a common example), and will have different expiry times. However, if I choose to fully protect a page for a short amount of time, any semi-protection that is set to last longer (or indefinitely) will be erased. It would be helpful if full and semi protection could operate independently of one another, so that a week of full protection would not affect a month of semi-protection.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ksxcfwf6vvnfvopbps4h', 'dateClosed': 1731923093, 'spacePHID': None, 'dateCreated': 1344094140, 'dateModified': 1731923093, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39038', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Bugzilla products could use a re-examination', 'description': {'raw': \"The current set of Bugzilla products doesn't make any sense to me. It's a hodgepodge of arbitrary projects, extensions, and other vague or broad categories. It'd be nice to rearrange the products to be a bit more sane. This will help bug filers and developers alike.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://bugzilla.wikimedia.org/enter_bug.cgi\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=43459\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53986\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1416786026, 'spacePHID': None, 'dateCreated': 1343952060, 'dateModified': 1416786029, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38990', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports]', 'description': {'raw': 'MediaWiki bugs to be fixed for WMF deployment'}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fn7qnpccfbitivgtw2rt', 'dateClosed': 1427763864, 'spacePHID': None, 'dateCreated': 1343681340, 'dateModified': 1472371824, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38865', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Use prefix when accessing parsoid', 'description': {'raw': 'Use a prefix when accessing parsoid. See https://gerrit.wikimedia.org/r/#/c/15626/ for details.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1345485579, 'spacePHID': None, 'dateCreated': 1343673300, 'dateModified': 1417573406, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38859', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links should follow the local CSS rules as if they were rendered in the view mode (e.g. external links shown with the external icon)', 'description': {'raw': 'This sounds to me like it might be hideously complicated, but putting it in here - e.g. a link to [http://foo.com] gets an external link notification icon on its right on the English Wikipedia, and this should show up as appropriate.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=33084\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=37901'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409609753, 'spacePHID': None, 'dateCreated': 1343330820, 'dateModified': 1497485444, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38726', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Long preformatted nodes display content splitting words at exactly browser width, not word-wrapped', 'description': {'raw': 'From user submission. See also https://mediawiki.org/wiki/File:VE_-_sentence_break_pre_formatted_text.png\\n\\n{F117608,size=full}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369428648, 'spacePHID': None, 'dateCreated': 1340916420, 'dateModified': 1429475153, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38043', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make it hard for users to partially-select some unlinked text for linking', 'description': {'raw': \"From bug T35091:\\n\\n- The UI of the visual editor should have a change to the user's interaction\\nwith link creation to make it harder to accidentally create things like\\n<a>foo</a>bar.\\n\\nI'm not quite sure what the ui change should be. Perhaps something like making\\nit so that when you try to create a link the selection might be altered to\\ncover the full word. Something that would require the user to force the editor\\nto use the selection that would create a <nowiki/> instead of just accepting it\\nas-is.\\n\\nWhatever the case, we do not want the user who partially selects a run of text\\nand turns it into a link to inadvertently create a <nowiki/> when they likely\\nintended to make a link of the whole thing.\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1340654460, 'dateModified': 1601077640, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37939', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support media (tracking)', 'description': {'raw': 'I know this isn\\'t ready yet, but that\\'s why we need a bug in the bug tracker. :)\\n\\nSteps to repro:\\n* create a new page in classic editor\\n* include [[Image:Wiki.png]]\\n* edit in visual editor\\n* save\\n\\nExpected:\\nImage should display in edit mode. After saving, nothing should have changed.\\n\\nActual:\\nImage becomes invisible in edit mode. After saving, it turns into literal HTML:\\n<img src=\"http://upload.wikimedia.org/wikipedia/commons/b/bc/Wiki.png\" alt=\"Wiki.png\" height width=\"200px\"></img>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422425089, 'spacePHID': None, 'dateCreated': 1340471220, 'dateModified': 1541508140, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37870', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: Escape plaintext three-tildes ~~~ are expanded to signature unexpectedly', 'description': {'raw': \"If I input ~~~, it's converted to my signature. If I input <nowiki>~~~</nowiki>, the nowiki tag is escaped and wrapped and ~~~ is still PST'ed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355190566, 'spacePHID': None, 'dateCreated': 1340390580, 'dateModified': 1366647357, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37841', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When \"Error saving data to server: Unsuccessful request: error.\" the spinner for saving doesn\\'t go away', 'description': {'raw': 'After an error message, the spinner is still there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354834279, 'spacePHID': None, 'dateCreated': 1340390280, 'dateModified': 1417573356, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37837', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Throw a clean error when user is blocked', 'description': {'raw': 'When you attempt to edit something using VisualEditor but you\\'re blocked, in Chrome a \"Error loading data from server: error. Would you like to retry?\" dialog appears instead of the expected MediaWiki:Blockedtext or MediaWiki:Globalblocking-ipblocked error message(s).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wqc7ciyvfzunj3l2tvjt', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340311908, 'spacePHID': None, 'dateCreated': 1340309160, 'dateModified': 1350341826, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37802', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Search does not find some pages', 'description': {'raw': '**Author:** `saibotrash`\\n\\n**Description:**\\nA search for Dateiverschieber https://commons.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=Dateiverschieber&fulltext=Search&ns8=1&redirs=1&profile=advanced should find [[commons:MediaWiki:RenameRequest.js]]\\n\\nBut it does not. Similarly for other query strings. The word is on that page since at least three months.\\n\\nIt works for other, even older pages.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**Whiteboard**: cirrus-fixed\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52782'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391825471, 'spacePHID': None, 'dateCreated': 1339634040, 'dateModified': 1391874790, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37578', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ResourceLoader does not check dependencies for existance', 'description': {'raw': \"**Author:** `questpc`\\n\\n**Description:**\\nI developed my extension in 1.18wmf1 then in 1.20 master. One of ResourceLoader modules, defined by extension has the following dependency:\\n\\n\\t\\t\\t'dependencies' => 'mediawiki.jqueryMsg',\\n\\nThe 'mediawiki.jqueryMsg' module and it's script is present in 1.18wmf1, 1.19, 1.20 master, but I was really surprised that in 1.18.2 it does not exists so the page scripts where my extension module is requested were broken with the following Chrome console errors:\\n\\nUncaught Error: Unknown dependency: mediawiki.jqueryMsg load.php:9427\\nUncaught TypeError: Cannot read property 'options' of undefined GmapFunc:255\\nUncaught TypeError: Cannot read property 'tokens' of undefined GmapFunc:260\\n\\nCan I try to catch the client-side error in load.php? I don't know how. Instead, I implemented the following server-side method to check whether the dependent modules actually exists:\\n\\n\\tstatic protected function checkAllModulesExists() {\\n\\t\\t$allModules = array_keys( self::$mapModules );\\n\\t\\tforeach ( self::$mapModules as $moduleName => $moduleDefinition ) {\\n\\t\\t\\tif ( !array_key_exists( 'dependencies', $moduleDefinition ) ) {\\n\\t\\t\\t\\tcontinue;\\n\\t\\t\\t}\\n\\t\\t\\tif ( is_array( $moduleDefinition['dependencies'] ) ) {\\n\\t\\t\\t\\t$allModules += $moduleDefinition['dependencies'];\\n\\t\\t\\t} else {\\n\\t\\t\\t\\t# We do not check for multiple matches in values:\\n\\t\\t\\t\\t# it would only decrease performance in this case.\\n\\t\\t\\t\\t$allModules[] = $moduleDefinition['dependencies'];\\n\\t\\t\\t}\\n\\t\\t}\\n\\t\\t$nonExistantModules = array_diff(\\n\\t\\t\\t$allModules,\\n\\t\\t\\tself::$out->getResourceLoader()->getModuleNames()\\n\\t\\t);\\n\\t\\tif ( count( $nonExistantModules ) > 0 ) {\\n\\t\\t\\tthrow new MWException( 'Cannot find requested module(s): ' .\\n\\t\\t\\t\\timplode( ',', $nonExistantModules ) .\\n\\t\\t\\t\\t' in ' . __METHOD__\\n\\t\\t\\t);\\n\\t\\t}\\n\\t}\\n\\nWhich produces the following page message, at least (that is more informative than Chrome console message):\\n\\nCannot find requested module(s): mediawiki.jqueryMsg in GMFn::checkAllModulesExists\\n\\nIt would be nice if ResourceLoader itself checked the dependencies of added modules.\\n\\n--------------------------\\n**Version**: 1.18.x\\n**Severity**: normal\\n**Whiteboard**: aklapper-moreinfo\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376496553, 'spacePHID': None, 'dateCreated': 1337677620, 'dateModified': 1382552231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37013', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Set $wgDefaultUserOptions['math']=2 on Wikimedia wikis (i.e. enable MathJax by default)\", 'description': {'raw': 'NOTE: this request may be superseded by {T78046}.\\n\\nFrom bug 31406 comment 0:\\n> A lot of work has gone into making it possible to use MathJax to view\\n> TeX on Wikipedia.  Probably more than 20,000 article use TeX (or\\n> whichever variant of TeX Wikipedia uses).  I have corresponded with\\n> Robert Miner, MathJax Project Director and Vice President or Research\\n> and Development at Design Science, Inc. about the fact that MathJax\\n> could now be used.  I told him that possibly in coming months MathJax\\n> would be adopted as the default means of viewing TeX on Wikipedia.\\n\\nAs I understand it, Michael Hardy was proposing MathJax as the **default** math mode, but since setting $wgMathUseMathJax = true on Wikimedia wikis doesn\\'t imply that it would be the default mode, I\\'m opening this bug to track what still needs to be done. This will also helps to separate the blockers of a \"experimental deployment\" (which is already done) and the blockers of a \"full deployment\" of MathJax on WMF wikis.\\n\\nIf I understood it correctly, this would be the new setting:\\n $wgDefaultUserOptions[\\'math\\'] = 2;\\n\\nFell free to move some blockers/dependencies from bug 31406 to this one as needed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48036'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413742990, 'spacePHID': None, 'dateCreated': 1336073820, 'dateModified': 1483240960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz36496', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '#mw-content-text is incorrectly placed on preview', 'description': {'raw': 'The id #mw-content-text, as I understand it, is normally attached to the .mw-content-ltr/rtl div so that the element directly holding the content is accessible through javascript. However, during preview, the ID is instead attached to a different element, which has #wikiPreview as a child element, which then has an ID-less (and thus inaccessible) .mw-content-ltr/rtl div holding the content. #mw-content-text should consistently be the content-holding div.\\n\\n--------------------------\\n**Version**: 1.19\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1588452442, 'spacePHID': None, 'dateCreated': 1336042080, 'dateModified': 1588452442, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz36476', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"MathJax doesn't work in LivePreview\", 'description': {'raw': 'Raw TeX commands are displayed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'dateClosed': 1424939822, 'spacePHID': None, 'dateCreated': 1334738220, 'dateModified': 1424940836, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz36060', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Backspace, cursor, among others not working in the insert link dialog', 'description': {'raw': \"See title. Maybe it's due to handling the keydown event and return'ing false or preventing default, I don't know.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-d2y3fvmumrowgb4efuvo', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340403895, 'spacePHID': None, 'dateCreated': 1333706040, 'dateModified': 1340403895, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'content-holding <div> should only contain the page text', 'description': {'raw': '**Author:** `a.d.bergi`\\n\\n**Description:**\\nThe new bidirectionality-improving div should only contain the parsed page content, nothing else. This is perfect when viewing articles, and helps scripts a lot when extracting that content.\\n\\nBut I think it is only needed for article views. For example in diff mode, it contains \\n```lang=html\\n <form id=\"mw-fr-reviewform\">\\n <div id=\"mw-fr-diff-headeritems\">\\n <table class=\"diff\">\\n <hr class=\"diff-hr\"/>\\n <h2 class=\"diff-currentversion-title\">\\n```\\n ...and then the real content\\n\\nAlso, in edit mode the `<div id=\"mw-content-text\">` contains\\n```lang=html\\n <div id=\"editnotice-ns-0\"/>\\n <div id=\"mw-edit-longpage-hint\">\\n <div id=\"wikiPreview\" class=\"ontop\" style=\"display: none;\"/>\\n <form id=\"editform\">\\n```\\nNone of them is really content-text, I suspect. I think it would be better to have the div only appear (maybe empty) in the `#wikiPreview`.\\n\\nAlso, it for example broke my script which tried to\\n```lang=javascript\\ndocument.getElementById(\"bodyContent\").insertBefore(newElement, document.getElementById(\"editform\"));\\n```'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-uqcn2l4ng4murmyfnvyp', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-uqcn2l4ng4murmyfnvyp', 'dateClosed': 1494273236, 'spacePHID': None, 'dateCreated': 1331837760, 'dateModified': 1697724682, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35247', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Undoing \"Clear formatting\" does not work', 'description': {'raw': 'Clicking \"Undo\" after using the \"Clear formatting\" button does not work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340403504, 'spacePHID': None, 'dateCreated': 1330562220, 'dateModified': 1340403504, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34824', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Page doesn't scroll when dragging selection off bottom of window in VisualEditor\", 'description': {'raw': '* Open up https://test.wikipedia.org/wiki/Special:VisualEditorSandbox\\n* click-and-drag to select...\\n* ...keep dragging down to the bottom of the window and beyond\\n\\nExpected behavior:\\nDocument should scroll so we can keep selecting stuff.\\n\\nActual behavior:\\nDocument does not scroll; cannot select anything further by mouse.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://test.wikipedia.org/wiki/Special:VisualEditorSandbox\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51669'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340401398, 'spacePHID': None, 'dateCreated': 1328824440, 'dateModified': 1443278787, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34307', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Window resizing crashes VisualEditor if too small', 'description': {'raw': 'In certain browsers (including Chrome and IE9), if one resizes the window to smaller than a certain size, the VisualEditor will crash.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340401269, 'spacePHID': None, 'dateCreated': 1328532960, 'dateModified': 1351534204, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34224', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Special:Translate unable to save where CAPTCHA is required', 'description': {'raw': \"**Author:** `aokomoriuta`\\n\\n**Description:**\\nWhen I don't have skipcaptcha right, page translation with external link got error.\\nCan we pass CAPTCHA test in translation function?\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1328258040, 'dateModified': 1715529180, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34182', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Spell check not working in VisualEditor interface', 'description': {'raw': '**Author:** `utsavsabharwal`\\n\\n**Description:**\\nI wrote following line and was expecting the editor to help me with the spell of gud and notify me about invalid word \\'Yra\\' but it dint :(\\n\\n\"Yra Utsav is gud boy \"\\n\\nI am using Chromium 15.0.874.106 (Developer Build 107270 Linux) Ubuntu 11.10\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340398658, 'spacePHID': None, 'dateCreated': 1325686140, 'dateModified': 1351534201, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz33511', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Revision wrongly flagged as \"automatically checked\" after edit conflict', 'description': {'raw': 'See URL for an example.\\n\\nRevision 97771495 is flagged as \"automatically checked\" though the previous version isn\\'t. I think this is what happened:\\n\\n1. The base version is the version from 17:14 (CET), a flagged version.\\n2. Elmar Nolte (with autoreview right) starts to edit.\\n3. The IP starts to edit and saves first. The revision is not flagged.\\n4. Elmar Nolte saves. The software detects an edit conflict which is resolved automatically. So no warning is shown. The FR extension still sees this edit based on the previous flagged version and flags the new revision as automatically checked.\\n\\nBut in fact Elmar Nolte\\'s revision is based on the unflagged revision by the IP and should not be flagged automatically.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://de.wikipedia.org/w/index.php?title=Emanuel_Semper&action=history&uselang=en'}, 'authorPHID': 'PHID-USER-tyjmn7xcw6s2b6rqagj7', 'ownerPHID': 'PHID-USER-bmbmvb2e5bg6ztcangbq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374026846, 'spacePHID': None, 'dateCreated': 1325581020, 'dateModified': 1374026846, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz33481', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Repositories with Ruby code should be documented and appropriate Jenkins jobs should be running', 'description': {'raw': '- it is documented at [[ https://www.mediawiki.org/wiki/Repositories_with_Ruby_code | Repositories with Ruby code ]] page?\\n- is ruby syntax check running after every commit?\\n- is rubocop  running after every commit?\\n- is browser test jenkins job created? (optional)\\n\\nRepositories:\\n\\ngerrit\\n\\n|name|ruby|rubocop|\\n|mediawiki/core|1.9.3|0.32.1|\\n|mediawiki/extensions/ArticleFeedbackv5|1.9.3|0.26.1|\\n|mediawiki/extensions/CentralAuth|1.9.3|0.29.1|\\n|mediawiki/extensions/CentralNotice|1.9.3|0.29.1|\\n|mediawiki/extensions/CirrusSearch|1.9.3|0.26.1|\\n|mediawiki/extensions/ContentTranslation|1.9.3|0.29.1|\\n|mediawiki/extensions/Echo|1.9.3|0.29.0|\\n|mediawiki/extensions/Flow|1.9.3|0.32.1|\\n|mediawiki/extensions/Gather|1.9.3|0.34.1|\\n|mediawiki/extensions/GettingStarted|1.9.3|0.29.1|\\n|mediawiki/extensions/Math|1.9.3|0.27.0|\\n|mediawiki/extensions/MobileFrontend|1.9.3|0.29.1|\\n|mediawiki/extensions/MultimediaViewer|1.9.3|0.29.1|\\n|mediawiki/extensions/PageTriage|1.9.3|0.26.1|\\n|mediawiki/extensions/PdfHandler|1.9.3|0.26.1|\\n|mediawiki/extensions/PoolCounter|1.9.3|0.27.1|\\n|mediawiki/extensions/QuickSurveys|1.9.3|0.29.1|\\n|mediawiki/extensions/Translate|1.9.3|0.26.1|\\n|mediawiki/extensions/TwnMainPage|1.9.3|0.26.1|\\n|mediawiki/extensions/UniversalLanguageSelector|1.9.3|0.29.1|\\n|mediawiki/extensions/UploadWizard|1.9.3|0.29.1|\\n|mediawiki/extensions/VisualEditor|1.9.3|0.32.1|\\n|mediawiki/extensions/WikiLove|1.9.3|0.26.1|\\n|mediawiki/extensions/ZeroBanner|1.9.3|0.26.1|\\n|mediawiki/extensions/ZeroPortal|1.9.3|0.26.1|\\n|mediawiki/ruby/api|1.9.3|0.29.1|\\n|mediawiki/selenium|1.9.3|0.29.1|\\n|mediawiki/vagrant|1.9.3|0.33.0|\\n|oojs/ui|2.0|0.27.1|\\n|operations/puppet|1.9.3|0.33.0|\\n|VisualEditor/VisualEditor|1.9.3|0.29.1|\\n\\ngithub\\n\\n|name|ruby|rubocop|\\n|amire80/commons_upload|2.2.0|0.33|\\n|amire80/screenshot.git|2.2.0|?|\\n|wmde/WikidataApiGem|1.9.3|-|\\n|wmde/WikidataBrowserTests|1.9.3|0.32.1|'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'dateClosed': 1443456873, 'spacePHID': None, 'dateCreated': 1416490011, 'dateModified': 1471122100, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'browsertests-VisualEditor-language-screenshot jenkins job failing', 'description': {'raw': 'At the moment, we have a couple of jenkins jobs:\\n\\n  - [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-VisualEditor-language-screenshot-linux-firefox/ | browsertests-VisualEditor-language-screenshot-linux-firefox ]]\\n  - [[ https://integration.wikimedia.org/ci/view/BrowserTests/view/-All/job/browsertests-VisualEditor-language-screenshot-linux-firefox-sauce/ | browsertests-VisualEditor-language-screenshot-linux-firefox-sauce ]]\\n\\nThe first job runs local firefox and fails randomly.\\n\\nOptions:\\n\\n- check if any of the headless environment variables helps\\n- check if any of the reuse browser environment variables helps\\n- check if switching to local chromium helps\\n\\nThe second job run a remote browser on sauce labs, but it does not support Chinese and Japanese fonts (at least), but only on linux host.\\n\\n- check if running the job on windows (or mac) helps.'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1424769549, 'spacePHID': None, 'dateCreated': 1416327470, 'dateModified': 1438727633, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Team (and other non-project) tags should be available for filtering', 'description': {'raw': \"It's not immediately clear which projects should be in the actual message. As things are looking now, just team and project is OK, but maybe tags should also be added.\\n\\nSee https://github.com/legoktm/wikibugs2/commit/f2d91f6e6a1d8ccba54041d3376ed7719585c8d3 -- all tags should be reported to the IRC bot, not just projects.\\n\\n\\nSee also:\\n -  T1209 - Add 'team' (purple) to output\\n - T1122 - Don't include closed projects in wikibugs2 output\"}, 'authorPHID': 'PHID-USER-muirnivxp5hzppn2a3z7', 'ownerPHID': 'PHID-USER-muirnivxp5hzppn2a3z7', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-muirnivxp5hzppn2a3z7', 'dateClosed': 1423341471, 'spacePHID': None, 'dateCreated': 1416306634, 'dateModified': 1711312271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Remove old wmf/* deployment branches (recurring chore)', 'description': {'raw': \"We don't have any real need for 1.23wmf* and 1.24wmf* deployment branches anymore. They should probably be changed to tags.\\n\\nChad, do you have a script for doing this? Timo seemed to think you had from before...\\n\\n-----\\n**EDIT**: Krinkle used the following script for individual repositories at [https://github.com/Krinkle/dotfiles/tree/master/hosts/KrinkleMac/bin](https://github.com/Krinkle/dotfiles/tree/db0e65f/hosts/KrinkleMac/bin):\\n{P3455}\\n{P531}\"}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': 'PHID-USER-oetk6bbl6omm354ejz3b', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-oetk6bbl6omm354ejz3b', 'dateClosed': 1494861695, 'spacePHID': None, 'dateCreated': 1416143148, 'dateModified': 1494861695, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor loading indicator should feel more integrated into the mobile interface', 'description': {'raw': 'Something like PACE minimal or barbershop http://github.hubspot.com/pace/docs/welcome/'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-ujgufealwngqoe65jj3h', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1563502297, 'spacePHID': None, 'dateCreated': 1415512766, 'dateModified': 1563502297, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add documentation links to TechTalk Youtube Videos ', 'description': {'raw': 'The goal is to have good descriptions in the most relevant videos at https://www.youtube.com/user/watchmediawiki\\nLinks to all past tech talk videos: https://www.mediawiki.org/wiki/Tech_talks#Past_tech_talks\\n\\nStep 1: Add one-line bio of the speaker(s) of the video\\nStep2: Go through the video and extract relevant links\\nStep3: Add the new description to commons\\n\\nTemplate for the description:\\n-Speaker Name (Their one-line bio)\\n-Summary\\n-Relevant links\\n\\n\\n| Youtube video | Description in Youtube | Description in Commons | Embedded in Wikimedia pages\\n| [[ https://www.youtube.com/watch?v=Qo4XIzCJZVs | Tech Talk: New readership data]] | Done | [[ https://commons.wikimedia.org/wiki/File:Tech_Talk_-_New_readership_data_-_Some_things_we%27ve_been_learning_recently_about_how_Wikipedia_is_read.webm#.7B.7Bint:filedesc.7D.7D | Done]] | \\n|[[https://www.youtube.com/watch?v=_yr5z9Ix2f8 | Phabricator for Wikimedia projects]] | Done | [[https://commons.wikimedia.org/wiki/File:Phabricator_for_Wikimedia_projects.webm | Done]] | |\\n| [[https://www.youtube.com/watch?v=ltEL-kPURKs |Automated citations in Wikipedia]] |Done | [[https://commons.wikimedia.org/wiki/File:Tech_Talk_-_Automated_citations_in_Wikipedia_-_Citoid_and_the_technology_behind_it.webm#.7B.7Bint:filedesc.7D.7D | Done]] | \\n| [[https://www.youtube.com/watch?v=sWiDimlK4bE |  Introduction to Free and Open Source Licensing at Wikimedia]] | Done | [[https://commons.wikimedia.org/wiki/File:Tech_Talk_-_Introduction_to_Free_and_Open_Source_Licensing_at_Wikimedia.webm | Done]] | |\\n'}, 'authorPHID': 'PHID-USER-vcyz3oe6mrt5w42lpqeh', 'ownerPHID': 'PHID-USER-k7tm37wvr4juk56sjsxf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1505207051, 'spacePHID': None, 'dateCreated': 1415224479, 'dateModified': 1505207063, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a survey that MediaWiki users can use to provide us with information', 'description': {'raw': 'https://www.mediawiki.org/wiki/2015_MediaWiki_User_Survey\\n\\nhttps://docs.google.com/forms/d/1j2ThONROvc0bGY5d3yx4tJln4Aa2Fs130j5OlHbjW14/viewform\\n\\nPresentation reporting preliminary results.\\n\\nhttps://commons.wikimedia.org/wiki/File:2015_MediaWiki_User_Report.pdf'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-xd3dshn3ykvvbsxmqbg6', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xd3dshn3ykvvbsxmqbg6', 'dateClosed': 1437248933, 'spacePHID': None, 'dateCreated': 1415210988, 'dateModified': 1503181244, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Audit groups of metrics in Graphite that allocate a lot of disk space', 'description': {'raw': 'New report as of 2017/06/21. eventstreams is tracked at {T160644} already\\n\\n```\\nroot@graphite1001:/var/lib/carbon/whisper# du -hcs /var/lib/carbon/whisper/* | grep G | sort -rn\\n433G\\t/var/lib/carbon/whisper/eventstreams\\n199G\\t/var/lib/carbon/whisper/servers\\n199G\\t/var/lib/carbon/whisper/instances\\n137G\\t/var/lib/carbon/whisper/ores\\n71G\\t/var/lib/carbon/whisper/MediaWiki\\n50G\\t/var/lib/carbon/whisper/zuul\\n46G\\t/var/lib/carbon/whisper/varnishkafka\\n35G\\t/var/lib/carbon/whisper/frontend\\n```'}, 'authorPHID': 'PHID-USER-wr3pospifdaxghmtobvr', 'ownerPHID': 'PHID-USER-wr3pospifdaxghmtobvr', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wr3pospifdaxghmtobvr', 'dateClosed': 1501145271, 'spacePHID': None, 'dateCreated': 1415116064, 'dateModified': 1539613340, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'unable to obtain stable firefox connection in 60 seconds', 'description': {'raw': 'This error message happens [[ https://integration.wikimedia.org/ci/job/browsertests-VisualEditor-language-screenshot-linux-firefox/LANGUAGE_SCREENSHOT_CODE=nl,label=contintLabsSlave%20&&%20UbuntuTrusty/29/consoleFull | intermittently ]]:\\n\\n  unable to obtain stable firefox connection in 60 seconds (127.0.0.1:7055) (Selenium::WebDriver::Error::WebDriverError)\\n\\nLooks like it is a known problem:\\n\\nhttps://code.google.com/p/selenium/issues/detail?id=4967\\nhttps://github.com/leonid-shevtsov/headless/issues/33\\n'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1416479903, 'spacePHID': None, 'dateCreated': 1415110910, 'dateModified': 1416524009, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Monthly report of total / active Phabricator users', 'description': {'raw': \"Thanks to @Dzahn we have been collecting the number of [[ https://www.mediawiki.org/wiki/Talk:Community_metrics#Bugzilla_stats | active Bugzilla users every month ]] for almost two years now. It would be useful to collect this data --or any approximation-- on a monthly basis:\\n\\n[x] Number of accounts created \\n[ ] Number of users logging \\n[x] Number of users performing any action in Maniphest \\n\\nExtended Play\\n\\nIt would be interesting to know whether it is possible to extract these values as well (total and past month):\\n\\n[x] Number of task creators\\n[ ] Number of comment posters\\n[x] Number of task //closers//\\n[ ] Number of workboard movers\\n\\n[x] Number of tasks created\\n[x] Number of tasks closed\\n[x] Median age in days of open tasks by priority\\n\\nVery Extended Play\\n\\nThen we could open two parallel ways:\\n* Other metrics per app: who is subscribing to Projects, who uses Differential...\\n* Filter these metrics by project, with a possibility to aggregate projects (i.e. let's count only the engineering projects)\\n\\nThe extended plays are inspirational only. This task can be closed as soon as we can publish monthly metrics for total amount of users and active in the past month.\\n\\n**First report, sent on January 1st (for the record)**\\n\\n> Hi Community Metrics team,\\n>\\n> this is your automatic monthly Phabricator statistics mail.\\n> \\n> Number of accounts created in (2014-12): 395\\n> Number of active users (any activity) in (2014-12): 619\\n> Number of task authors in (2014-12): 384\\n> Number of users who have closed tasks in (2014-12): 213\\n> Number of tasks created in (2014-12): 3424\\n> Number of tasks closed in (2014-12): 2529\\n> Number of tasks in the shell project closed as resolved,fixed in (2014-12): 12\\n>\\n> Number of open and stalled tasks in total: 18125\\n>\\n> Median age in days of open tasks by priority:\\n> Unbreak now: 115\\n> Needs Triage: 147\\n> High: 199\\n> Normal: 437\\n> Low: 686\\n> Needs Volunteer: 536\\n>\\n> TODO: Numbers which refer to closed tasks might not be correct, as described in T1003.\\n\"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fo56wm4wxiwpoofn2xdu', 'dateClosed': 1419342160, 'spacePHID': None, 'dateCreated': 1414696282, 'dateModified': 1522603344, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Migration of Research & Data to Phabricator', 'description': {'raw': \"Let's track progress on the migration of this team to Phabricator. Feel free editing this task description.\\n\\n[ ] Team member assigned to this task\\n[ ] Link(s) to the current projects in Mingle, Trello, other\\n[ ] (optional) Have you scheduled a team meeting with @Qgil to discuss the migration? (yyyy-mm-dd)\\n[ ] Blockers of the migration identified: (list the task numbers between {curly brackets})\\n[ ] Planned date for the migration/creation of a first real project: yyyy-mm-dd\\n[ ] Do you plan to have all your projects moved by the end of 2014? Yes/No, and if not, why\\n(...)\\n[ ] More than half of our team members and ongoing sprints are working in Phabricator now (yyyy-mm-dd)\\n[ ] All our projects have been moved to Phabricator. Mission completion! (yyyy-mm-dd)\"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-boqv2doznygy3kwrkyly', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-qb5aoo443n6fezsozhv4', 'dateClosed': 1433943903, 'spacePHID': None, 'dateCreated': 1414050574, 'dateModified': 1569179499, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Deliver (global version of) VisualEditor newsletter #9 for 2014', 'description': {'raw': ''}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'dateClosed': 1416060820, 'spacePHID': None, 'dateCreated': 1414000841, 'dateModified': 1425350553, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Write VisualEditor newsletter #9 for 2014', 'description': {'raw': ''}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'dateClosed': 1422299256, 'spacePHID': None, 'dateCreated': 1414000792, 'dateModified': 1425350556, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Work on the VisualEditor newsletter for November 2014', 'description': {'raw': ''}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'dateClosed': 1416060894, 'spacePHID': None, 'dateCreated': 1413980113, 'dateModified': 1552650409, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Severity information is not being migrated', 'description': {'raw': 'We agreed that the Severity information would be printed in the task description, since we decided not to have such field in Phabricator. Currently this information is missing in bugzillapreview. See for instance https://bugzilla.wikimedia.org/show_bug.cgi?id=57540 (Severity: critical)'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1416478566, 'spacePHID': None, 'dateCreated': 1413672057, 'dateModified': 1423684079, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Print URL, Version, etc only when they contain data', 'description': {'raw': 'Currently these fields are being always printed in the bugzillapreview:\\n\\n> URL: none\\n> Version: unspecified\\n> See Also: none\\n> Hardware/OS: unknown/unknown\\n\\nSee for instance https://bugzillapreview.wmflabs.org/T6408\\n\\nIf these fields contain just the defaults, they don\\'t offer any information and are pure noise. Can we migrate these fields only when they have specific information (not the default)?\\n\\n**DECISION**\\n\\nFields to always keep in the initial description of a Phab task, no matter what the value is set to:\\n* Version\\n* Severity\\nFields to drop from the initial description of a Phab task only if set to default value \"All\":\\n* Platform/Hardware\\n* OS\\nFields to drop from the initial description of a Phab task only if value is entirely empty:\\n* URL\\n* Whiteboard\\n* See Also'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-3neel27i7dyu62jbbx2l', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-3neel27i7dyu62jbbx2l', 'dateClosed': 1415209973, 'spacePHID': None, 'dateCreated': 1413671789, 'dateModified': 1423684080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create use cases for two test cluster (\"Beta Cluster\" and the yet-to-be-created and yet-to-be-named cluster)', 'description': {'raw': '\\nOver the past two years, a growing number of teams have come to rely on having unreleased software available for use in the beta labs cluster shared test environment.  The ways that teams use beta labs has become more sophisticated, more diverse, and more important.  Disruption of service or unexpected system behavior on beta labs is therefore quite expensive across all of WMF and the development community. \\n\\nAt the same time, we need a shared test environment where we can test big risky system-wide software changes in a realistic test environment.\\n\\nA little history:\\n\\nTwo years ago beta labs was a hodgepodge of symlinks, old versions of core and some extensions, and not much else.  There were no policies at all governing its use. Over time we made it so that beta always ran the latest version of the master branch of code. As beta became more valuable, we instituted one policy there: the only code allowed on beta labs was for extensions and features that already existed in the production cluster. Beta labs has never been a \"wild west\" environment, we have always controlled closely what software runs there. My vision was that beta labs would become the system of record for testing WMF software, and this sort of control is required for beta labs to be such a system.\\n\\nBut as our software matured, it became more feasible to implement large-scale system-wide changes. Beta labs was the only reasonable environment in which to test such large-scale changes.  So we changed the policy: we would allow non-production software on beta labs only if that software had a scheduled release to the production environment. Our first such project in beta labs was CirrusSearch, the next was the Flow extension, then HHVM after that.  Besides these, we have also had some experiments with existing beta labs infrastructure like changing the Varnish cache and changing the database master-slave relationship. \\n\\nEvery one of these system-wide changes on beta labs has caused significant disruption, down time, and problems for automated testing. \\n\\nBut that was okay at the time.  Beta labs has always been primarily a target for automated browser tests, and very few teams used it in any meaningful way early in its history. \\n\\nBut that situation has changed dramatically over the last year or so.  As we discovered when HHVM testing brought down all of beta labs for extended periods of time, almost all of WMF relies on beta labs in one way or another to do their work, from testing bleeding-edge software changes, to public demonstrations of new features, to community engagement.\\n\\nSo we need test environments to serve the parties addressed by both of our previous beta labs policies.  We need to support the latest unreleased changes to software that already exists in production; but we also need a realistic test environment for *unreleased* software with the potential to disrupt the entire cluster.\\n\\nSo I propose two beta-labs-like test environments.  These test environments will not differ in the software features they offer, nor in their nominal response to users, but only in the policies governing their use. \\n\\nBoth environments would: \\n\\n* be updated automatically with the master branch of core and extensions\\n* have their databases updated automatically as they are today\\n* be the target of automated browser test builds\\n* be available to the public as beta labs is today\\n* serve as the system of record for software testing and software changes\\n\\nConservative beta labs would follow our original maintenance policy: no software or systems in place other than those already released to production.  This would very likely be the existing beta labs cluster, so as to disrupt the teams using it already as little as possible.   The aim of this system would be to supply as reliable a user experience as possible given that the system will be running the master branch of all production code and nothing other than production code. \\n\\nLiberal beta labs would follow our amended maintenance policy: software with a projected release to production would be in use here.  If it is not in production already, liberal beta labs would be the place to make it work.  Liberal beta labs might host major changes to cross-cutting systems such as\\n\\n* Search (affects Core, MobileFrontend, VisualEditor, etc.)\\n* System optimizations (HHVM, new caching schemes, major db changes, etc.)\\n* New extensions (especially those requiring untested db updates)\\n* Any system-wide config change needing testing\\n* Potentially, this system could host experiments not destined for a production release, but that exist for research purposes\\n\\nTesting HHVM proved that we are stretching the capacity and capability of beta labs beyond what we can reliably support.  Having a conservative beta labs test environment for features bound for production would serve our existing users, while having a liberal beta labs test environment where we can manipulate the entire system would serve our future users.\\n\\n\\n'}, 'authorPHID': 'PHID-USER-z3l4i7dl52qicxtephy5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'dateClosed': 1410486532, 'spacePHID': None, 'dateCreated': 1409872045, 'dateModified': 1425500453, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl621', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Decide which task statuses we want to have in Maniphest', 'description': {'raw': '**Proposed statuses:**\\n\\n| **Status name in Phab** | **Explanation** | **Resembling in Bugzilla** |\\n| open | Default state | {UNCONFIRMED, NEW, ASSIGNED, REOPENED, PATCH_TO_REVIEW*} {} |\\n| stalled | Stalled |  |\\n| resolved | A change that fixes the task has been merged. | {RESOLVED, VERIFIED, CLOSED} FIXED |\\n| invalid | This is not a task, or it is out of scope in Wikimedia Phabricator. | {RESOLVED, VERIFIED, CLOSED} INVALID |\\n| declined | Bad idea, can not be reproduced, missing information has not been provided, or an acceptable alternative exists. | {RESOLVED, VERIFIED, CLOSED} {WONTFIX, LATER, WORKSFORME} |\\n| //(marked as duplicate)// | | RESOLVED DUPLICATE |\\n\\n*For PATCH_TO_REVIEW, create a project and add it to Phab tasks. See T169.\\n\\n---\\n---\\nFor historical reasons: Initial task description:\\n\\nBy default, Phabricator offers OPEN, RESOLVED, WONTFIX, INVALID as statuses (and we can resolve tasks as duplicates).\\nCustom statuses can be added via /config/edit/maniphest.statuses/\\n\\nSubtasks I see here:\\n * Bugzilla also offers WORKSFORME (CANNOT_REPRODUCE). DO we want this?\\n * NEEDINFO/NEEDS_MORE_INFO: marking an item as not actionable is a recurring request for Bugzilla, see https://bugzilla.wikimedia.org/show_bug.cgi?id=36064\\n * INVALID sounds harsh so we might want to bikeshed on a better wording.'}, 'authorPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'ownerPHID': 'PHID-USER-3neel27i7dyu62jbbx2l', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1415632148, 'spacePHID': None, 'dateCreated': 1401463475, 'dateModified': 1629152116, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl359', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Decide whether we need to add a severity (impact) field to match Bugzilla's\", 'description': {'raw': 'I don\\'t see a tracking of severity distinct from priority. Considering that priority has no universal meaning, but only a per-component meaning (at best), this seems very inappropriate for a disperse project like ours.\\nhttp://c2.com/cgi/wiki?DifferentiatePriorityAndSeverity\\n\\nMoreover, the main use we make of \"Priority\" in bugzilla, i.e. how hard/expensive a bug is, is already covered by \"Points\".\\n\\n----\\n\\n**See also**: {T93499}'}, 'authorPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'dateClosed': 1410485361, 'spacePHID': None, 'dateCreated': 1397888043, 'dateModified': 1567372368, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl168', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Name and domain for Wikimedia's Phabricator instance: phabricator.wikimedia.org\", 'description': {'raw': 'DECISION: We will use `phabricator.wikimedia.org` as the domain for the service.\\n\\ncnames for any shortened version\\n\\n----\\n\\nWe need to decide a domain (and therefore a name) for the Phabricator instance in Wikimedia.\\n\\nDo we want to use something around the \"Phabricator\" brand or do we prefer to go for a descriptive alternative, or a totally invented name?\\n\\nWe have used bugzilla.wikimedia.org and gerrit.wikimedia.org, therefore phabricator.wikimedia.org cannot be too wrong. Still, it is long, and I\\'m personally not convinced of relying so much on product names.'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'dateClosed': 1410485245, 'spacePHID': None, 'dateCreated': 1397747363, 'dateModified': 1417649605, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl142', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Document benefits for Bugzilla users', 'description': {'raw': \"**Document moved to https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/versus_Bugzilla -- you are welcome to edit and discuss there.**\\n\\nAs a bugzilla volunteer user, I want to know what I'm supposed to gain from the migration to phabricator, which is bound to add work I've not asked for.\"}, 'authorPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 50, 'name': 'Medium', 'color': 'orange'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'dateClosed': 1410485129, 'spacePHID': None, 'dateCreated': 1397721605, 'dateModified': 1412769607, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl116', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid page views: need to do something about {{int:}}', 'description': {'raw': 'Currently, {{int:}} is (ab)used to localize content, either directly by showing a localised message or by using e.g. [[ https://commons.wikimedia.org/w/index.php?title=Special%3ASearch&search=MediaWiki%3ALang&fulltext=1 | MediaWiki:Lang ]] to achieve conditional transclusion à-la {{sometemplate/{{int:lang}}}}. However, Parsoid always assumes content language for this parser function. This is generally not a problem for VisualEditor where it even makes sense to display a \"canonical\" version of text, but page views on multilingual projects like meta and commons are different because these sites rely heavily on user language to display content in it. A few examples:\\n\\n\\n  - File description pages, compare https://commons.wikimedia.org/wiki/File:Sao_Paulo_Railway.jpg?uselang=en vs. https://commons.wikimedia.org/wiki/File:Sao_Paulo_Railway.jpg?uselang=fr\\n  - Talk page templates, compare https://commons.wikimedia.org/wiki/Commons:Bistro?uselang=fr vs. https://commons.wikimedia.org/wiki/Commons:Bistro?uselang=en\\n  - Esoteric templates, e.g. https://commons.wikimedia.org/w/index.php?title=Template:Localized_link&action=edit or even in Lua: https://commons.wikimedia.org/wiki/Module:Fallback\\n\\nWe need to develop a strategy to mitigate thiese problems for Parsoid-based pageviews.'}, 'authorPHID': 'PHID-USER-aasrweh54ew7py3agvg2', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1419990114, 'dateModified': 1720680225, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Pasting Excel cells into Internet Explorer doesn't work\", 'description': {'raw': \"Pasting from Excel into Chrome works.  Highlighting that content in Chrome and then pasting it into IE works.\\n\\nPasting the content straight from Excel into IE11 doesn't work.\\n\\nHow can I enable pasting straight from Excel?\"}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1681402595, 'spacePHID': None, 'dateCreated': 1419973446, 'dateModified': 1681402595, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Regression: Using Unicode Combining diacritics duplicates/replaces/adds unwanted characters', 'description': {'raw': 'This is similar to T53472.\\n\\nSome languages or writing systems require combining diacritics.\\nIn theory most characters with diacritics can be input with combining diacritics, for example é (e + combining acute) is equivalent to é (eacute). **For some combinations in some languages only the use of combining diacritics is possible, for exemple ɔ́ (open o + combining acute).**\\n\\nWhen typing or pasting text with combining diacritics the following occurs:\\n  - the first character after a combining diacritics is duplicated on a new line below the cursor.\\n  - pressing backspace pushes the characters after the first combining diacritics to that line below, the cursor jumps to the end of the newline and the first character that was duplicated jumps behind the cursor as well.\\n  - pressing backspace gets stuck a the combining diacritics, erasing the duplicated character last, after the characters that jumped and the line return but not erasing the combining diacritics and its base character.\\n\\nFor example, typing\\n\\n```\\nté\\n```\\nis fine.\\nBut typing other characters becomes:\\n\\n```\\ntél\\nl\\n```\\nthen\\n\\n```\\ntélévision\\nl\\n```\\n\\nPressing backspace with the cursor at the end of the first line:\\n\\n```\\nté\\nélvisio\\n```\\nwith the cursor before the o, but the next backspace will delete the o and the cursor jumps before the i.\\n\\nThe expected result should be the word \"télévision\" and pressing backspace should delete the character before the cursor or the character cluster before the cursor.'}, 'authorPHID': 'PHID-USER-i5at67w766dqxs6ncxam', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-v7iovheqigasai3pzdax', 'dateClosed': 1544804245, 'spacePHID': None, 'dateCreated': 1419151474, 'dateModified': 1544804245, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Text in Templates is not found by VisualEditor's Find / Search\", 'description': {'raw': 'Found when investigating T62451 - a page consists entirely of text entered via Templates fields: https://pt.wikibooks.org/w/index.php?title=C%C3%A1lculo_(Volume_1)/An%C3%A1lise_de_fun%C3%A7%C3%B5es_elementares_(2)&redirect=no&veaction=edit \\n\\nText is not searchable via VE Find, but can be searched via browser Find.'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437698862, 'spacePHID': None, 'dateCreated': 1418936627, 'dateModified': 1437698862, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'convert the RTL blocking bug T2745 into a tag', 'description': {'raw': 'The RTL blocking/tracking bug T2745 can be converted into a Phabricator tag.\\n\\nIt also has some \"sub-tracker\" bugs, for example T35126, which is for RTL bugs in VisualEditor. These can eliminated as well. They should have the RTL tag and the appropriate project tag.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1433255137, 'spacePHID': None, 'dateCreated': 1418744270, 'dateModified': 1574458472, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor language screenshots come out with pixelated fonts', 'description': {'raw': 'The screenshots that are uploaded by the latest builds of the VisualEditor language screenshot job have pixelated fonts.\\n\\nCompare:\\n* Current, pixelated: https://upload.wikimedia.org/wikipedia/commons/f/fe/VisualEditor_Toolbar_Headings-en.png\\n* Older, non-pixelated: https://upload.wikimedia.org/wikipedia/commons/archive/f/fe/20141203163056!VisualEditor_Toolbar_Headings-en.png\\n\\nThis may be happening because on the clients where the test jobs run there is a problem with the screen driver or maybe fonts anti-aliasing is disabled. Either the configuration of this client machines must be fixed, or the tests must run on a different platform, maybe Mac. (But it must be tested that they have fonts for all the languages, in particular Arabic, Japanese and Hebrew.)'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1421145680, 'spacePHID': None, 'dateCreated': 1418732838, 'dateModified': 1438736924, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor screenshots-taking tests should link to the job that uploaded them from the file description page', 'description': {'raw': 'VisualEditor screenshots-taking tests (currently language_screenshots.feature) upload the files to Commons. It would be useful to have a link from the file description page to the Jenkins job that uploaded the file so it would be easier to debug the problems in it if there are any.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1418732537, 'dateModified': 1446832010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"make-wmf-branch doesn't play nice with existing extension branches\", 'description': {'raw': \"```\\n'git' 'clone' '-q' 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git' 'VisualEditor'\\nTotal 73708 (delta 49816), reused 73204 (delta 49799)\\ncd VisualEditor\\n'git' 'checkout' '-q' '-b' 'wmf/1.25wmf12'\\n'git' 'commit' '-a' '-q' '-m' 'Creating new wmf/1.25wmf12 branch'\\n'git' 'push' 'origin' 'wmf/1.25wmf12'\\nTo ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git\\n ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)\\nerror: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'\\nTo prevent you from losing history, non-fast-forward updates were rejected\\nMerge the remote changes (e.g. 'git pull') before pushing again.  See the\\n'Note about fast-forwards' section of 'git push --help' for details.\\nsleeping for 5s\\n'git' 'push' 'origin' 'wmf/1.25wmf12'\\nTo ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git\\n ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)\\nerror: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'\\nTo prevent you from losing history, non-fast-forward updates were rejected\\nMerge the remote changes (e.g. 'git pull') before pushing again.  See the\\n'Note about fast-forwards' section of 'git push --help' for details.\\nsleeping for 5s\\n'git' 'push' 'origin' 'wmf/1.25wmf12'\\nTo ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git\\n ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)\\nerror: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'\\nTo prevent you from losing history, non-fast-forward updates were rejected\\nMerge the remote changes (e.g. 'git pull') before pushing again.  See the\\n'Note about fast-forwards' section of 'git push --help' for details.\\nsleeping for 5s\\n'git' 'push' 'origin' 'wmf/1.25wmf12'\\nTo ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git\\n ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)\\nerror: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'\\nTo prevent you from losing history, non-fast-forward updates were rejected\\nMerge the remote changes (e.g. 'git pull') before pushing again.  See the\\n'Note about fast-forwards' section of 'git push --help' for details.\\nsleeping for 5s\\n'git' 'push' 'origin' 'wmf/1.25wmf12'\\nTo ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git\\n ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)\\nerror: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'\\nTo prevent you from losing history, non-fast-forward updates were rejected\\nMerge the remote changes (e.g. 'git pull') before pushing again.  See the\\n'Note about fast-forwards' section of 'git push --help' for details.\\nsleeping for 5s\\n'git' 'push' 'origin' 'wmf/1.25wmf12'\\nTo ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git\\n ! [rejected]        wmf/1.25wmf12 -> wmf/1.25wmf12 (non-fast-forward)\\nerror: failed to push some refs to 'ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/VisualEditor.git'\\nTo prevent you from losing history, non-fast-forward updates were rejected\\nMerge the remote changes (e.g. 'git pull') before pushing again.  See the\\n'Note about fast-forwards' section of 'git push --help' for details.\\nsleeping for 5s\\ngit exit with status 1\\n```\"}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-oetk6bbl6omm354ejz3b', 'dateClosed': 1526375741, 'spacePHID': None, 'dateCreated': 1418240952, 'dateModified': 1526375741, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'error on doing vagrant up \"mount.nfs: access denied by server while mounting\" in ubuntu 14.04', 'description': {'raw': 'I tried to set up the MediaWiki Vagrant environment according to the steps described here: http://www.mediawiki.org/wiki/MediaWiki-Vagrant \\nI used the most current VirtualBox and Vagrant.\\nWhen I tried to do vagrant up: mount.nfs: access denied by server while mounting. \\n\\nFind the complete error here: {F20641}'}, 'authorPHID': 'PHID-USER-pxdyvyvhcyeu5efcjcgj', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1624383762, 'spacePHID': None, 'dateCreated': 1418226811, 'dateModified': 1624383762, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Sort out Performance Metrics Dashboard mentorship', 'description': {'raw': \"Due to a combination of factors, we haven't been able to line up a good mentorship for @memeht in the #Performance-Metrics-Dashboard project yet. This has caused a delay in her start on this program. This needs to be solved urgently. @Qgil is working on this. \"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1421403221, 'spacePHID': None, 'dateCreated': 1418208428, 'dateModified': 1421403221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Menu items in table popup widget (e.g. \"Insert before\") truncated in most languages (box not wide enough)', 'description': {'raw': 'Steps to reproduce:\\n\\n1. Set language to Indonesian (id).\\n2. Open page in VisualEditor.\\n3. Insert a table, or select an existing one.\\n4. Click on the \"▾\" (down arrow) indicator next to the first cell.\\n5. Notice that the words end with … rather than spelling out the entire text.\\n\\nProposed solution:  Make the menu wider, because some languages require more space than English.\\n'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1441740277, 'spacePHID': None, 'dateCreated': 1418189274, 'dateModified': 1442268521, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Extra space before the start of the citation/template (not multiple transclusion) dialog contents', 'description': {'raw': 'See screenshot:\\n\\n{F20260}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423066309, 'spacePHID': None, 'dateCreated': 1418156016, 'dateModified': 1438736673, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'wikimediafoundation.org search results should not include files from Wikimedia Commons', 'description': {'raw': \"https://wikimediafoundation.org/w/index.php?title=Special:Search&search=please%20check%20back&fulltext=Search&profile=all\\n\\nThe search results here include files from Wikimedia Commons. This is kind of weird. It might be helpful if the Commons search results are of media that's actively used/referenced on the local wiki, but otherwise it's just kind of strange and unexpected to include a foreign wiki's search results alongside the local wiki's, especially without a clear opt-out mechanism.\\n\\nSee also: {T94856}\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1441035308, 'spacePHID': None, 'dateCreated': 1417909769, 'dateModified': 1451538637, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Exact matches should always win when suggesting/auto-completing', 'description': {'raw': 'Upstream reports: https://secure.phabricator.com/T6102 and https://secure.phabricator.com/T8510\\n\\n**Workaround by valhallasw: \\nExecute `JX.TypeaheadSource.prototype.setMaximumResultCount(100)` in the javascript console (or a userscript)** to get more results displayed. Userscripts at P2444 (Chrome) and P2445 (Firefox)\\n\\nWhen typing in the \"projects\" field in the \"edit task\" or \"edit search\" view, phabricator offers up to 5 suggestions/completions. But sometimes, the exact match for what I just typed is not included in this list. This makes it impossible for me to enter these projects anywhere (for me, this happens for \"wikidata\" - I see \"wikidata.org\" etc, but not \"wikidata\"). Interestingly, these suggestions look different for other users (with the same input, they do get \"wikidata\", though it\\'s only in the 4th slot), so it seems the ranking in the suggester is user-specific (projects that I am a member of get boosted, or some such). \\n\\nIn any case: exact matches should always win. If I enter a full name and hit enter, this should always work if a project by this name exists.\\n\\nI\\'m setting this to \"high\" since it makes it pretty much impossible for me to work with phab.\\n\\nPS: I suppose the same issue exists for all fields that use the suggester/tag logic, but I did not run into any problems with other fields yet.\\n\\n{F39253}'}, 'authorPHID': 'PHID-USER-5dqihbanu3caaj7pigif', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1530265110, 'spacePHID': None, 'dateCreated': 1417710278, 'dateModified': 1530453845, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide real-time collaboration in VisualEditor-MediaWiki', 'description': {'raw': 'Exceptionally hard, many issues, yada yada yada.\\n\\nStill, this would be an excellent thing to provide our users.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1417568581, 'dateModified': 1732253599, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide real-time collaborative editing in VisualEditor', 'description': {'raw': 'This is about VisualEditor-core, not VisualEditor-MediaWiki for which there are a bunch of issues that would need to be solved first.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1417568021, 'dateModified': 1710361808, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Convert hyphens to en dashes when written in VisualEditor', 'description': {'raw': 'I dont know, how is it in English punctuation, but suprisinglly hyphen mark, which is naturally present on all keyboards is not so much used in the texts. Wikipedia is based especially on texts so it would be a nice feature to VE to have a choise to replace hyphen by En dash, which is much more need in the text at times when you hit hyphen bar.\\n\\nNow we should insert that symbol, by inserting the symbol - that is in fact not known to not skilled newbies. On the other side, it slow down the skilled editors. If they want to write a clear text from the beggining, the have to stop, insert en dash and continue.'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-xqqqgn2dels45flxw5kb', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xqqqgn2dels45flxw5kb', 'dateClosed': 1454199276, 'spacePHID': None, 'dateCreated': 1417305712, 'dateModified': 1454199276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'The message visualeditor-recreate says \"Press continue\", but it\\'s unclear what does \"continue\" refer to', 'description': {'raw': 'The message visualeditor-recreate says \"Press continue\", but it\\'s unclear what does \"continue\" refer to. It should probably include the \"continue\" message as a parameter.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1417197627, 'spacePHID': None, 'dateCreated': 1416988401, 'dateModified': 1438736338, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Load VisualEditor file from modules.json as a manifest, rather than tediously copying it into extension.json', 'description': {'raw': ''}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1551814413, 'spacePHID': None, 'dateCreated': 1416971459, 'dateModified': 1551814593, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Calling buildNodeTree() manually should not be needed', 'description': {'raw': 'We explicitly call buildNodeTree() in a few places. Ideally, we would not need to do this outside of ve.dm.Document.\\n\\nSuspect calls (excluding dm.Document, excluding tests):\\n\\nlib/ve/src/ce/ve.ce.Surface.js\\n1000:\\t\\t\\tdoc.buildNodeTree();\\n1711:\\t\\tdoc.buildNodeTree();\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1416338280, 'dateModified': 1442447696, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73569', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: DOM Exception (no user-facing loss of functionality?) after a long editing session', 'description': {'raw': 'After a prolonged session of editing in Safari, the following error was displayed: \\n\\n[Error] Error: QuotaExceededError: DOM Exception 22 DOMException\\n\\tlog (load.php, line 150)\\n\\tflush (load.php, line 173)\\n\\n\\nNo degradation in responsiveness/functionality was noticed. Should we handle this exception?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1416273720, 'dateModified': 1425420042, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73540', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Discrepancy in displaying text with <mark>  in Edit and Read modes', 'description': {'raw': 'Read mode - all text is highlighted\\n\\n1. In VE type some text. Hit enter for the second line.\\n\\nSome text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling.\\n \\n2. Open Edit source(Keep changes) and add <mark> as in the sample below: \\n\\n<mark>\\nSome text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling. Some text in bulk to check scrolling. \\n\\n3. Save - in Read mode all text on the page will be highlighted with the yellow background. \\n\\n4. Switch to Edit mode again - only the first line will be displayed as highlighted. \\n\\nThe screenshots are attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F14967}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1558272914, 'spacePHID': None, 'dateCreated': 1416269700, 'dateModified': 1558272915, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73536', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve-ce-focusableNode-dropMarker is displayed as a horizontal line when Gallery is dragged-drop to Media Caption', 'description': {'raw': 'dragging gallery to Media\\n\\n1. VE: insert media(a picture) and a gallery.\\n\\n2. Attempt to drag a gallery into Media and drop - a horizontal vertical line will be displayed. The screen recording is attached.  \\n\\ne.g.\\n<div class=\"ve-ce-focusableNode-dropMarker\" style=\"width: 1048px;\">\\n\\n\\nNote: happens *only* with dragging  a gallery.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14943}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1577744177, 'spacePHID': None, 'dateCreated': 1416263460, 'dateModified': 1579632591, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73528', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs UI: trouble with CheckboxInputWidget in Opera', 'description': {'raw': 'User:Tacsipacsi at the Hungarian Wikipedia reports issues with \"the new buttons\" and provides the following log:\\n\\n```\\n[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/index.html\\nHTML style attribute\\nInvalid value for property: zoom\\nLine 1:\\n  display:inline;margin:0;border:0;padding:1px;width:1px;zoom:1\\n  -------------------------------------------------------------^\\n[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/oojs-ui-mediawiki.svg.css\\nLinked-in stylesheet\\nInvalid value for property: -webkit-transform\\nLine 957:\\n    -webkit-transform: translateZ(0px);\\n  -------------------------------------^\\n[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/oojs-ui-mediawiki.svg.css\\nLinked-in stylesheet\\nInvalid value for property: -o-transform\\nLine 960:\\n    -o-transform: translateZ(0px);\\n  --------------------------------^\\n[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/dist/oojs-ui-mediawiki.svg.css\\nLinked-in stylesheet\\nInvalid value for property: transform\\nLine 961:\\n    transform: translateZ(0px);\\n  -----------------------------^\\n[2014.11.15. 14:41:15] CSS - https://tools.wmflabs.org/oojs-ui/oojs-ui/demos/styles/demo.css\\nLinked-in stylesheet\\nDeclaration syntax error\\nLine 197:\\n   width: calc(100% - 40px);\\n  --------------------------^\\n```\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1424354295, 'spacePHID': None, 'dateCreated': 1416245640, 'dateModified': 1427403671, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73517', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: FlaggablePageView::setPageContent() called incorrectly', 'description': {'raw': 'ApiVisualEditorEdit.php:142, $view->setPageContent() should be passing 2 parameters\\n\\n\\tpublic function setPageContent( &$outputDone, &$useParserCache ) {\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416246428, 'spacePHID': None, 'dateCreated': 1416057420, 'dateModified': 1417571386, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73469', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tables that are inserted into Media captions will display Table caption below the table', 'description': {'raw': 'Inserted table with caption\\n\\nSteps to reproduce: \\n\\n1 VE - Insert a media\\n2. In Media Settings box insert a table and add a caption to a table. Click Insert.\\n\\nThe media will be inserted with a table and the table caption will be displayed below the table. The screenshot is attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F15354}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1453165589, 'spacePHID': None, 'dateCreated': 1416001080, 'dateModified': 1453165589, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73435', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Ctrl-v of text into a pre-formatted area ends up with <br> added to each line', 'description': {'raw': 'I was inserting log lines into a preformatted area.  It looked fine on the page, but after saving, there were clearly extra spaces added.  Went into wikitext to remove them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1655736850, 'spacePHID': None, 'dateCreated': 1415998020, 'dateModified': 1655736850, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73433', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Tables inside references aren't allowed in wikitext (but are in VE and Parsoid)\", 'description': {'raw': 'Tables in References list\\n\\nShould we allow inserting tables in Basic citation? \\n\\n1. VE - insert Cite->Basic \\n\\nWhen inserting Basic citation the dialog box shows all toolbar options in Reference dialog box including tables. \\n\\n2. Insert a table from the Reference dialog box for the Basic citation. Type some text in that table. \\n\\nThe reference list accommodate the table but does not how any table structure - see the attached screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15121}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1415840100, 'dateModified': 1416846008, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73341', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Drag-and-drop of a block image into a table slices the table rather than inserting inside the cell', 'description': {'raw': 'dragging block images split tables\\n\\nThe bug is split from 72995\\n\\nDragging an image and placing the insert cursor outside a table will split the table.\\n\\nSee the at attached screen recording.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15063}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1452965061, 'spacePHID': None, 'dateCreated': 1415813220, 'dateModified': 1461807098, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73318', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paste from Word to Firefox inserts garbage', 'description': {'raw': \"Cut 'n paste from a MS Word document into FF inserts several HTML comments which appear in VE as circled exclamation marks.  Hovering reveals the lengthy MSIE-specific comments.\\n\\nNote that pasting the same thing into Chrome does not end up with the lengthly comments.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1590761121, 'spacePHID': None, 'dateCreated': 1415765760, 'dateModified': 1590761121, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73292', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: receiving a 'not logged in' warning on a page that shows that a user is logged in\", 'description': {'raw': 'Not logged in warning\\n\\nIn test2 and in Betalabs a warnings gets displayed \"You are not logged in...\". The page displays a user status as being logged in in the upper right corner.(see the attached screenshot).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14878}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1415667240, 'dateModified': 1698776965, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73250', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:[Regression wmf7] Inconsistent behavior in Chrome compared to FF, on applying  a link or language annotation to a gallery.', 'description': {'raw': 'Environment- test2, beta\\n\\nJust like media files , the gallery also does not take link or any annotations. But the behavior is inconsistent in Chrome when compared to FF.\\n\\nTested in Chrome 38 and FF 33.1.\\n\\n1> In a blank page, insert a Gallery with some caption\\n2> Click to highlight the gallery and while it is still highlighted, select to insert link.\\n3> In FF, the link inspector opens above the Gallery.\\nIn Chrome, the link inspector opens and closes in a split second.\\n\\nThe same thing happens when trying to language annotations to a Gallery.\\n1> > insert a Gallery with a file name and caption\\n2> Click to highlight the gallery and while it is still highlighted, select to apply language.\\n3> In FF, the langauge inspector opens below  the Gallery.\\n\\nIn Chrome, the language inspector opens and closes instantly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1415642340, 'dateModified': 1462716693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73233', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Gallery with no images (invalid characters as gallery contents) creates an invisible node and can't be edited\", 'description': {'raw': 'Gallery with no images (invalid characters as gallery contents) creates an invisible node and can\\'t be edited.\\n\\nFor example, create a page with the following wikitext:\\n```\\n<gallery>\\n>>\\n</gallery>\\n```\\nExample: https://en.wikipedia.org/w/index.php?title=User:Matma_Rex/sandbox&oldid=826934821\\n\\nThis renders as an empty gallery (`<ul class=\"gallery mw-gallery-traditional\"></ul>`).\\n\\nIn VE, it displays a placeholder, but it seems that it can\\'t be clicked to focus it:\\n{F13935446}\\nWhen focussed using arrow keys, it displays a completely mispositioned context menu:\\n{F13935448}\\nTrying to use the \"Edit\" button causes a JS error in the console:\\n```\\nTypeError: Cannot read property \\'toggleHighlighted\\' of undefined\\n    at VeUiMWGalleryDialog.ve.ui.MWGalleryDialog.onHighlightItem (https://en.wikipedia.org/w/extensions/VisualEditor/modules/ve-mw/ui/dialogs/ve.ui.MWGalleryDialog.js?22058:591:7)\\n    at https://en.wikipedia.org/w/extensions/VisualEditor/modules/ve-mw/ui/dialogs/ve.ui.MWGalleryDialog.js?22058:342:13\\n    at fire (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3317:31)\\n    at Object.add [as done] (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3376:7)\\n    at VeUiMWGalleryDialog.<anonymous> (https://en.wikipedia.org/w/extensions/VisualEditor/modules/ve-mw/ui/dialogs/ve.ui.MWGalleryDialog.js?22058:341:9)\\n    at https://en.wikipedia.org/w/resources/lib/oojs-ui/oojs-ui-windows.js?f9a29:748:28\\n    at mightThrow (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3583:29)\\n    at process (https://en.wikipedia.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=vector&version=14kbqyi:3651:12)\\n```'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1519297416, 'spacePHID': None, 'dateCreated': 1415641200, 'dateModified': 1520034195, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73230', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:[Regression wmf7] Inserting media, while Gallery inspector is open, makes the cursor active in the main editor', 'description': {'raw': \"Environment- test2, beta\\n\\n1> Select to insert a gallery.Type in  some caption in the resulting  dialog.\\n2> Click done. \\n3> open the gallery inspector again and while it is open, select Insert -> Media.\\n4> After the Media Search dialog opens notice the cursor instead of being active in the dialog's input field , is active in the main editor. See screencast.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\"}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1423522526, 'spacePHID': None, 'dateCreated': 1415637000, 'dateModified': 1438736615, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73226', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:[Regression wmf7] Uncaught TypeError: Cannot read property 'nodeType' of undefined ,on deleting the content in the Gallery inspector and clicking done\", 'description': {'raw': \"screenshot of JS error\\n\\nEnviornment- test2, beta\\n\\n1> Select to insert a gallery. When the inspector opens just type in some text.\\n2> Now highlight the gallery and click on the gallery context menu. The gallery inspector opens.\\n3> delete the content in the dialog and then press done.Generates JS error Uncaught TypeError: Cannot read property 'nodeType' of undefined in the console.See screenshot.\\n\\nSame behavior found in FF 33.1. \\nJS error - TypeError: currentNode.children[(nao.offset - 1)] is undefined.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP\\n\\n**Attached**: {F14822}\"}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1423526211, 'spacePHID': None, 'dateCreated': 1415632380, 'dateModified': 1438736517, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73224', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support discontiguous table selections', 'description': {'raw': 'We currently sort of support this is that row/col deletion skips over merged cells, but the user should probably be able to create such a selection themselves. The current canonical form of a table selection is [fromCol,fromRow,toCol,toRow] so this would need to be changed/extended. There are also a lot of places where we assume the selection to be rectangular.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1415623800, 'dateModified': 1643973174, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73217', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link annotations can be split into two adjacent ones when other annotations overlap', 'description': {'raw': 'I dug deeper after filing bug 73201.\\n\\n1. Type \"abcdef\".\\n2. Make \"ab\" italic.\\n3. Make \"ef\" italic.\\n4. Make \"bcde\" a link.\\n\\nResult:   \\'\\'a[[bcde|b]]\\'\\'[[bcde|cd\\'\\'e\\'\\']]\\'\\'f\\'\\'\\nExpected: \\'\\'a\\'\\'[[bcde|\\'\\'b\\'\\'cd\\'\\'e\\'\\']]\\'\\'f\\'\\'\\n\\nThe result doesn\\'t seem to depend on the order of operations here.\\n\\nVisualEditor should avoid splitting link annotations.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1525297392, 'spacePHID': None, 'dateCreated': 1415553420, 'dateModified': 1525297392, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73202', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tables Caption - moving a cursor with keyboard forces a cursor to the begininng of the page', 'description': {'raw': '1. Open a page in VE and insert a table with a caption. Make sure that you have some chunk of text above the inserted table or a block of some content, so the page needs to be scrolled down to the table.\\n\\n2. Place a cursor in the table caption and press the right arrow on a keyboard to navigate to the end of the caption. Press one more time - the page scrolls up and the cursor is placed at the beginning of the page. \\n\\nNote: moving a cursor with the left arrow to the beginning of the caption and pressing it one more time will simply place it at the last character of a previous sentence.'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1471888514, 'spacePHID': None, 'dateCreated': 1415228580, 'dateModified': 1472671126, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73055', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'If the input for the redirect in the meta dialog is invalid, as well as show a red outline, block the user from closing the dialog with a prompt to fix it', 'description': {'raw': 'This task is about [VisualEditor](https://www.mediawiki.org/wiki/VisualEditor). See its [user guide](https://www.mediawiki.org/w/index.php?title=Help:VisualEditor/User_guide) for general information.\\n\\nIn the VisualEditor, click the ≡ icon, click \"Options\", and choose \"Page Settings\".\\nIf someone puts an invalid page name / page title in the \"Target page for [redirection](https://www.mediawiki.org/wiki/Help:Redirects)\" field (like the page name \"Talk:\" or a page name with a pipe character `|` in it), and tries to apply the changes, an exception is caused and the editor is locked up. \\n\\nThe \"Apply Changes\" button should be disabled when the input is not valid (like in e.g. the \"Insert ➙ Media\" dialog when file dimensions are invalid). \\n\\nYou are expected to provide a patch in Wikimedia Gerrit. See https://www.mediawiki.org/wiki/Gerrit/Tutorial for how to set up Git and Gerrit.'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-jho7mi4ksndgagtb2pj3', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1541111048, 'spacePHID': None, 'dateCreated': 1415132640, 'dateModified': 1541696368, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72971', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression pre-wmf7] The down arrow to bring up the context menu for Categories is not center-aligned, again', 'description': {'raw': 'Betalabs\\n\\nThe down arrow to bring up the context menu for Categories is not center aligned.\\n\\nCompare the screenshots from Betalabs and test2\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14800}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415148942, 'spacePHID': None, 'dateCreated': 1415128320, 'dateModified': 1417571388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72962', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6] A Label appears momentarily, showing all \"Use this Group\" options, when Re-Using a Reference', 'description': {'raw': 'Environment- production, beta\\n\\n1> Cite -> Basic. Type a name in the “Use this Group”. Type some text in the sub-editor to make the insert button active and click to insert.\\n2> Cite -> Re Use. Select the Reference from the list.\\n3> Notice a label shows up with General References and the Group name momentarily, before the reference gets inserted to the main editor. See the screencast(pause it at 0.07).\\n\\nIn beta, it appears on the top-left corner of the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1664897272, 'spacePHID': None, 'dateCreated': 1415027160, 'dateModified': 1664897273, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72904', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  References inside galleries being displayed separately, inside the gallery, instead of in the correct <references /> block at the end of the page', 'description': {'raw': 'Open a page containing some refs, and then a gallery that contains <ref> tags but no <references /> block inside the gallery.  (The references block can be elsewhere on the page.)  For example:\\n```\\n==Section==\\nHello world.<ref>First footnote</ref>\\n\\n==Gallery==\\n<gallery>\\nFile:Example.jpg|An image<ref>A footnote for the image</ref>\\n</gallery>\\n\\n==References==\\n<references />\\n```\\n\\nIn read mode, everything looks right:\\n\\n> Section\\n> Hello world.[1]\\n> \\n> Gallery\\n> An image[2]\\n> \\n> References\\n> 1. ^ First footnote\\n> 2. ^ A footnote for the image\\n\\nIn VisualEditor, you get this:\\n\\n> Section\\n> Hello world.[1]\\n> \\n> Gallery\\n> An image[1]\\n> 1. ^ A footnote for the image\\n> \\n>References\\n> 1. ^ First footnote\\n\\n{F15268}\\n\\nVisualEditor seems to be inserting a ref block into the gallery, even though none exists at that point on the page.  Also, it restarts the numbers for the gallery.'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1441041207, 'spacePHID': None, 'dateCreated': 1414858200, 'dateModified': 1442272360, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72865', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'MWTidy: Old versions of Tidy break flow content out of <caption> and <table>', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce\\n\\n1.Insert a table\\n2.Insert a caption \"text2\"\\n3.Make the caption a bullet point to create a slug above it\\n4.Now add some other text in that slug \"text1\"\\n5.Save the page\\n\\nObserved Result:\\nThe order of \"text1\" and \"text2\" gets reversed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15176}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-yawytiq5q7eduxmvnkid', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-yawytiq5q7eduxmvnkid', 'dateClosed': 1534452609, 'spacePHID': None, 'dateCreated': 1414786140, 'dateModified': 1621252635, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72833', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Tables - adding formatted headings  to <visualeditor-table-caption> displays Uncaught TypeError', 'description': {'raw': \"1. In VE highlight any portion of an inserted table and add <visualeditor-table-caption>.  \\n\\n2. Without typing any text in the caption, select any format for headings format - Uncaught TypeError will be displayed.\\n\\nUncaught TypeError: Cannot read property 'nodeType' of undefined VM8471:495ve.ce.Document.getNodeAndOffset VM8471:495ve.ce.Surface.focus VM8471:538ve.ui.FormatAction.convert VM8471:661ve.ui.Surface.execute VM8471:629ve.ui.Command.execute VM8471:645ve.ui.Tool.onSelect VM8471:638OO.ui.ToolGroup.onPointerUp VM8471:66OO.ui.PopupToolGroup.onPointerUp VM8471:91jQuery.event.dispatch load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20141030T0…:65elemData.handle \\n\\n3. Attempt to delete the added caption displays: \\n\\nUncaught Error: Unbalanced set of replace operations found (program):321ve.dm.TransactionProcessor.processors.replace (program):321ve.dm.TransactionProcessor.executeOperation (program):314ve.dm.TransactionProcessor.process (program):314ve.dm.Document.commit (program):390ve.dm.Surface.changeInternal (program):366ve.dm.Surface.change (program):365ve.dm.SurfaceFragment.change (program):370ve.dm.SurfaceFragment.delete (program):380ve.ce.Surface.handleLinearDelete (program):578ve.ce.Surface.onDocumentKeyDown (program):546ve.EventSequencer.callListener (program):257ve.EventSequencer.onEvent (program):254(anonymous function) (program):252jQuery.event.dispatch load.php:65elemData.handle\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415883590, 'spacePHID': None, 'dateCreated': 1414771500, 'dateModified': 1469823941, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72816', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf6] For a re-used reference dialog the group names for reference lists are not at all visible in the \"Use this group\" combo box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page woth VE\\n2.Add a basic reference\\n3.Re -use that reference\\n4.Open the reference dialog for the re-used reference\\n5.Open the dropdown for the Use this group comb box \\n\\nObserved Result:\\nCannot see any groups names there as its getting cut off\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15043}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414796081, 'spacePHID': None, 'dateCreated': 1414701900, 'dateModified': 1417571387, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72785', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: No indication in the toolbar what text styles are active because they're in a menu\", 'description': {'raw': 'screenshot\\n\\nScreenshot show my cursor within a string of bold text. However the toolbar menu button doesn\\'t change to indicate that text-formatting is currently active. \\n\\nThis is particularly a problem if I place my cursor at the *end* of a string of bold/formatted text, as I cannot know at-a-glance, whether the text I\\'m about to type will come out formatted in some way.\\n\\nIn many other programs/sites (eg. gmail, gdoc), there is always an onscreen indicator (usually the button appears \"pressed\"), which helps me understand whether text-formatting is active or not.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14998}'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414695900, 'dateModified': 1542693764, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72772', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switching out the image clears the \"link\" parameter', 'description': {'raw': 'Steps to reproduce:\\n* Went to my user page, mw:User:Adamw .\\n* Clicked \"Edit\" to use the VisualEditor.\\n* Clicked the thumbnail at the top, to edit.\\n* Clicked the image title to open the editor dialog.\\n* Clicked \"Choose a different image\".\\n* Pasted the name of an image into the search field, and selected my image.\\n* Apply changes.\\n* Save chages to page.\\n\\nThis all seemed to go swimmingly, until I looked at the diff:\\n\\nhttps://www.mediawiki.org/w/index.php?title=User%3AAdamw&diff=1246151&oldid=1041988\\n\\nThe \"link\" parameter is missing.\\n\\nClient system: Linux, FF 32.0.3\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414657080, 'dateModified': 1553184432, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72750', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: After saving the page, external links in media always take preference in auto-numbering irrespective of their locations', 'description': {'raw': 'Environment- test2, beta, production\\n\\n1> insert an external link to a blank page. Number generated for this link is “1”.\\n2> hit enter a couple of times, to move the cursor down\\n3> Click to insert media ,in the media settings dialog enter  the same external link in the caption sub-editor.Click to insert.\\n4> notice the auto-numbers generated beside the external links.Number generated for the link in media is “2”.\\n5> Save the page. And notice that the media file external link’s auto-number has now changed to #1 and the external link in the page is #2.\\n\\nSee screencast.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'bug', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414507740, 'dateModified': 1644071627, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72625', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Editing has become awfully slow', 'description': {'raw': 'Timing response editing at enwiki\\n\\nThe save operation has become very slow lately, and it seems to have accelerated this month, possibly in the middle of this month (October).\\n\\nI did a test edit and the first POST request with submit action took 20562 ms, aka the \"save\". The later GET request on the page took 12627 ms. Some users report edit delays in the order of a minute or more.\\n\\nThis is on a 75Mbps symmetric fiber line, using HTTPS, with Firefox browser on Ubuntu 14.10. Other users have experienced this problem on other platforms and browsers, and both when they are logged in and not logged in.\\n\\nPreferences for my part is pretty standard, I can make an export if necessary, but as this is reported from several users editing at several sites I don\\'t think this has anything to do with preferences.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Whiteboard**: aklapper-moreinfo\\n\\n**Attached**: {F15172}'}, 'authorPHID': 'PHID-USER-vlni4mhyozor7ghqnfkl', 'ownerPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1426776217, 'spacePHID': None, 'dateCreated': 1414441560, 'dateModified': 1426776217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72577', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:[Regression wmf5] Inserting a Link target after a text,instead gets added in between the typed text.', 'description': {'raw': 'Environment- beta, test2,production\\n\\n1>In a blank page in VE,type in some text in paragraph format.\\n2>Enter a space and select to insert a link. Type in some text in the link input box and keep the inspector open.\\n3>Now while the inspector is open, click on to add a bullet/numbered list.\\n4>Notice the list gets added and deleted quickly and the link target gets inserted in between the text(right before the last character of the previously typed text). See screencast.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: Windows XP'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1508929909, 'spacePHID': None, 'dateCreated': 1414422900, 'dateModified': 1509740389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72562', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't allow whitespace-only comments to be inserted\", 'description': {'raw': \"screenshot of the comment popup\\n\\nEnvironment- test2,beta,production\\n\\n1> In VE, select to insert a comment.\\n2> When the dialog opens just enter space in the text area and click Done.\\n3> Notice the comment popup’s appearance (appears to be smaller, than the regular size).See screenshot.\\n4> Click on the popup. Notice the Edit comment box's textarea is empty  with no space taken up for the whitespace characters.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15118}\"}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429663826, 'spacePHID': None, 'dateCreated': 1414421400, 'dateModified': 1430950616, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72561', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Escape brackets in URLs of new/changed links', 'description': {'raw': 'It would be nice if the VisualEditor dialogs were able to escape (percent-encode) URLs as this one in a way that makes them work in wikitext.\\n\\nCurrently it fails to do so both when changing an existing URL https://it.wikipedia.org/w/index.php?title=PAGEPress_Publications&diff=68792069&oldid=68792024 and when adding it from scratch. I had to manually use urlencode: as usual in wikitext.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: http://doaj.org/search?source={%22query%22:{%22filtered%22:{%22query%22:{%22query_string%22:{%22query%22:%22Italy%22,%22default_operator%22:%22AND%22}},%22filter%22:{%22bool%22:{%22must%22:[{%22term%22:{%22_type%22:%22journal%22}},{%22term%22:{%22index.publisher.exact%22:%22PAGEPress%20Publications%22}}]}}}}}'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414071720, 'dateModified': 1643973176, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72425', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression wmf4] Link suggestions are appearing in a broken way inside Link Inspector in mobile', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Type a text\\n3.Apply a link on the text\\n4.Reopen the link inspector for it\\n\\nObserved Result:\\nThe link suggestions are appearing in a broken way .See the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15372}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1430336126, 'spacePHID': None, 'dateCreated': 1414017480, 'dateModified': 1438735777, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72402', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Banish the TOC and section edit link controls from the main page settings page, and show the display title one instead', 'description': {'raw': 'Fram says that the \"Page settings\" item should be the three items most commonly wanted by encyclopedia article editors:\\n\\n* redirect\\n* disambiguate\\n* displaytitle\\n\\nand that all the other options should be \"Advanced settings\" (or not displayed at all as described in {T74396}).\\n'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414016400, 'dateModified': 1434829741, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72397', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way to configure per-wiki which meta dialog items are available for each namespace', 'description': {'raw': 'Under \"Advanced settings\" in the Page options menu, there are two items:\\n\\n  \"Let this page be indexed by search engines\"\\n\\nand\\n\\n  \"Show a tab on this page to add a new section\" \\n\\nthat should never be changed for Wikipedia articles.  (This will differ for other projects; both of these might be appropriate at Meta, for example.)\\n\\nCould these options be hidden at projects where they should not be used?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414016220, 'dateModified': 1643973176, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72396', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf5] Have to undo twice to reverse comment creation', 'description': {'raw': 'Environment- beta.\\n\\n1> In VE, insert a comment. Click done.\\n2> click to undo while the comment is still highlighted. Notice the label on the Comment  first changes to read “Comment” from the actual comment text, before removing it. See screencast.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416248773, 'spacePHID': None, 'dateCreated': 1413903900, 'dateModified': 1417571383, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72315', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf4] Language context menu appears outside the Content Editor', 'description': {'raw': 'Language context menu appearing outside the editor\\n\\nEnvironment-test2, beta\\n\\n1> Insert some Language in RTL direction.\\n2> insert a comment in the language text, right before the last word. Notice the word moves to the start of line.\\n3> Now place the cursor at the end of the last char in the langauge text, notice the language context menu appears outside the editor on the top left of page.See screenshot.\\n\\nIt happens only when the cursor is at the last character.\\n\\nRefer bug 71320 screencast, in case the above steps sound confusing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15040}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414003086, 'spacePHID': None, 'dateCreated': 1413828000, 'dateModified': 1417571395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72273', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create a meta dialog panel for setting page status indicators', 'description': {'raw': 'Not quite sure how this will work (and how it will know which ones are available), but this would probably be rather useful.\\n\\nhttps://www.mediawiki.org/wiki/Help:Page_status_indicators is no longer blank. :-)\\n'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1413586320, 'dateModified': 1531521584, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72199', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Advanced media dialog is shown with horizontal scrollbars because button labels don't fit\", 'description': {'raw': \"Advanced media dialog is shown with horizontal scrollbars because button labels don't fit.\\n\\n{F15974499}\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1523287949, 'spacePHID': None, 'dateCreated': 1413560700, 'dateModified': 1523287949, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72187', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove ve.bind()', 'description': {'raw': 'Un-used function. Clean-up is good. Etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416054855, 'spacePHID': None, 'dateCreated': 1413498240, 'dateModified': 1461271267, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72156', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'In VE, while adding any image using Firefox getting the error \"Image corrupt or truncated\" in Betalabs', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open any page with VE in Betalabs using Firefox\\n2.Go to Insert>Media\\n3.Search for any image and select it to add it in the page\\n\\n\\nObserved Result:\\nThe image gets added to the page but in the console there is an error:\\n\\nImage corrupt or truncated: http://upload.wikimedia.org/wikipedia/commons/1/1b/Ko_BuWe.jpg\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15306}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1418946432, 'spacePHID': None, 'dateCreated': 1413421680, 'dateModified': 1418946432, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72115', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression wmf3] The fields inside Citations dialog are appearing at a fixed rather than whole-screen width in mobile VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Open any citation dialog like Cite>Website/book\\n\\nObserved Result:\\nThe fields inside Citations dialog are appearing at a much smaller size\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15293}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414793146, 'spacePHID': None, 'dateCreated': 1413419940, 'dateModified': 1417571387, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72112', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Collaborative spelling dictionary building tool', 'description': {'raw': '* Originally proposed at at https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_9#Collaborative_spelling_dictionary_building_tool\\n* Currently ongoing work: https://www.mediawiki.org/wiki/Collaborative_spelling_dictionary/Progress\\n\\nThere are extensive spelling dictionaries for the major languages of the world: English, Italian, French and some others; at various degrees of coverage, Mozilla has over a hundred, LibreOffice dozens. They help make Wikipedia articles in these languages more readable and professional and provide an opportunity for participation in improving spelling. Many other languages, however, don’t have spelling dictionaries. One possible way to build good spelling dictionaries would be to employ crowdsourcing, and Wikipedia editors can be a good source for this, but this approach will also require a robust system in which language experts will be able to manage the submissions: accept, reject, filter and build new versions of the spelling dictionary upon them. This can be done as a MediaWiki extension integrated with VisualEditor, and possibly use Wikidata as a backend.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1413107460, 'dateModified': 1676144702, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71973', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Some file permissions are causing lintian warnings', 'description': {'raw': \"Dear Sir or Madam,\\n\\n0) Context\\n\\nDEB packages of `mediawiki' and many of its extensions, are prepared as part of the WP-MIRROR project (see <https://www.mediawiki.org/wiki/Wp-mirror>). \\n\\n1) Lintian\\n\\nDuring the build process, `lintian' performs a great number of sanity checks, including seeing if each file has file permissions appropriate to its file type.\\n\\nWhen `lintian' sees a non-executable file with 755 permissions, rather than 644, `lintian' will throw a warning like:\\n\\nW: wp-mirror-mediawiki-extensions: executable-not-elf-or-script usr/share/wp-mirror-mediawiki/extensions/VisualEditor/modules/ve-mw/ui/styles/images/broken-image.png\\n\\n2) Files which should have permissions set to 644\\n\\nVisualEditor/modules/ve-mw/tests/browser/Gemfile\\nVisualEditor/modules/ve-mw/ui/widgets/ve.ui.MWMediaResultWidget.js\\nVisualEditor/modules/ve-mw/ui/widgets/ve.ui.MWMediaSearchWidget.js\\n\\n3) Technical details\\n\\nDEB standards version: 3.9.6\\nGIT branch: wmf/1.24wmf22\\n\\nSincerely Yours,\\nKent\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-k3cyvvb2psrntxfcuyyr', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413081448, 'spacePHID': None, 'dateCreated': 1413006660, 'dateModified': 1417571397, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71933', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add an \"open\" button for link nodes too', 'description': {'raw': 'I\\'m editing, and I see a plain, unlabeled, auto-numbered link to an external website.  It says \"[2]\".  I can\\'t open that link without exiting VisualEditor.  The link dialog has an option to \"Add label\" but not \"Open link\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413947295, 'spacePHID': None, 'dateCreated': 1412902140, 'dateModified': 1417571396, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71904', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Support PDF export on private wikis', 'description': {'raw': 'mwlib is able to fetch credentials to access content on private wikis, though with some issues.\\n\\n* http://web.archive.org/web/20110800000000/http://code.pediapress.com/wiki/ticket/747\\n** Credentials not used to fetch license page \\n** new – ralf – normal – major – 23 months\\n** Needs someone with a private wiki able to set $wgCollectionLicenseURL for testing; not relevant for OCG?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1611522574, 'spacePHID': None, 'dateCreated': 1412805660, 'dateModified': 1611522574, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71849', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Content inside templates for translation of templates does not render in friendly ways', 'description': {'raw': 'translate syntax in VE\\n\\nTranslated text should probably not display with syntax in VE\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14987}'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1608232349, 'spacePHID': None, 'dateCreated': 1412653560, 'dateModified': 1611574317, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71730', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow in-line editing/suggesting/flagging of TemplateData when labels are unclear', 'description': {'raw': 'unclear fields in an infobox template\\n\\nsome labels are not clear, or have not been given \"human readable\" aliases, providing a way for end users to flag these, or even submit suggestions or edit them directly could help clean these up quickly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F14733}'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-u6ycqhfpa3k4yvlpxjt2', 'dateClosed': 1654869001, 'spacePHID': None, 'dateCreated': 1412370540, 'dateModified': 1654869001, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71626', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Does not load at all on IE 11 (unknown dependency \"ext.visualEditor.iehacks\")', 'description': {'raw': 'VisualEditor Mobile does not load at all on IE 11 right now (unknown dependency \"ext.visualEditor.iehacks\", gets stuck displaying the loading spinner).\\n\\nEither the module needs mobile target, or we need to stop trying to load it on mobile.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412380521, 'spacePHID': None, 'dateCreated': 1412367420, 'dateModified': 1417571398, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71622', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: CommentInspector doesn't update its size when the textarea gets resized\", 'description': {'raw': \"CommentInspector doesn't update its size when the textarea gets resized, only if it's closed and reopened. Split off from bug 71310.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412817205, 'spacePHID': None, 'dateCreated': 1412021640, 'dateModified': 1417571693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71427', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Automatically tag edits that make a redirect, or convert a redirected page to a normal page, or move a page across namespaces, etc.', 'description': {'raw': \"When one creates a redirect without filling an edit summary, MediaWiki automatically uses an edit summary to identify that the edit created a redirect. That's very useful. But the autosummary doesn't work if the user fills the edit summary. It also doesn't work when the user edits a redirected page to make it a normal page, by removing the #REDIRECT syntax.\\n\\nRedirections are very special edits that would be good to have them tagged for review on recent changes and watchlists.\\n\\nWith AbuseFilter one could write some tricky filters to tag those edits, but that's far from ideal.\\n\\nMy proposal is to have at least 2 new tags:\\n* One to tag when a redirect is created\\n* One when a redirect is removed (not by page deletion, but by removing the #REDIRECT)\\n\\nIt would be nice to also have a tag for when a redirect target is changed (pointing the redirect to another article) and also when a redirect is edited without changing the redirect (like for example adding a category, a comment, or simply content that won't be viewed anyway).\\n\\nA slight limitation of tags (as I understand) is that they won't display the redirect target as the autosummary does, but that's not important, I think. The autosummary would do the job when present.\"}, 'authorPHID': 'PHID-USER-jnta3z3spxto3vbxdngm', 'ownerPHID': 'PHID-USER-znn4xfvlp7e7mr2g3tvl', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'dateClosed': 1512071461, 'spacePHID': None, 'dateCreated': 1411573320, 'dateModified': 1660398905, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71236', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] When an image is the only item of the document , trying to delete it right after opening VE throws \"Error: offset was inside a handlesOwnChildren node\"', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a blank page with VE\\n2.Insert an image as the first item of the document\\n3.Save the page\\n4.Reopen the page\\n5.The image gets highlighted, now try to delete the image\\n\\n\\nObserved Result:\\nThe following error appears in the console:\\nUncaught Error: offset was inside a handlesOwnChildren node\\n\\nSee the screenshot attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F14961}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411681189, 'spacePHID': None, 'dateCreated': 1411497900, 'dateModified': 1417571692, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71187', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'BetaFeatures: the VisualEditor section appears before the introduction', 'description': {'raw': 'The VisualEditor section of BetaFeatures appears before the introduction\\n\\nIn my experimental setup, the VisualEditor section in the beta features appears as first item, just before the introductory text about beta features.\\n\\nIt appears that in the LocalSettings.php I load the VisualEditor extension before the BetaFeatures extension, and exchange the order results in a good placement of the VE as BF (normal order).\\n\\n--------------------------\\n**Version**: master\\n**Severity**: minor\\n\\n**Attached**: {F14687}'}, 'authorPHID': 'PHID-USER-2nopae2cxuamwcbndaih', 'ownerPHID': 'PHID-USER-2nopae2cxuamwcbndaih', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411236943, 'spacePHID': None, 'dateCreated': 1411229760, 'dateModified': 1411236943, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71088', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Comments in \"unsafe\" content locations are not displayed in VisualEditor', 'description': {'raw': 'See the 6 hidden comments I placed in https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/SandboxVE&action=edit .\\nOnly 2 of them are visible when VEditing, https://en.wikipedia.org/wiki/User:Elitre_(WMF)/SandboxVE?veaction=edit .\\nReported on fr.wp, see for example that they are missing from sections Personagges and Liens externes in https://fr.wikipedia.org/w/index.php?title=Détective_Conan&veaction=edit .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1424907502, 'spacePHID': None, 'dateCreated': 1411214460, 'dateModified': 1432289295, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71085', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paste from Microsoft Word converting spaces to line breaks', 'description': {'raw': 'original Word source causing issues\\n\\nSome spaces in Word documented are being converted into line breaks when pasting into VE.\\n\\nExample: https://www.mediawiki.org/wiki/User:Rosencrantz/Paste\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F15305}'}, 'authorPHID': 'PHID-USER-evwol34rsld7viokxokd', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1411157280, 'dateModified': 1416846057, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71067', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] The #contentSub should not be removed during loading phase', 'description': {'raw': \"1. View https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License\\n2. Observe whitespace between heading, subtitle and first paragraph\\n3. Click Edit beta\\n\\nExpected:\\n* Table of contents slide up and content remains in the same position and dims.\\n\\nActual:\\n* The content shift upwards due to #contentSub being display-none'ed. This element is empty by default (also on English Wikipedia) but it does have a line height and thus affects flow.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1530906969, 'spacePHID': None, 'dateCreated': 1410983640, 'dateModified': 1530906969, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70954', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression] In Transclusion (multi-template) dialog, moving a template past a content block then focuses the content block, not the selected template', 'description': {'raw': 'Environment- Production, Test2, beta\\n\\n1> open the transclusion for any citation (book/news/journal).\\n2> add a content and a template  below the citation in the modal.\\n3> Now highlight the Citation and click to move the citation down.\\n4> Notice that although the citation moves down and the Content moves up, but now the highlight moves to the content instead of staying at the Citation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1410797520, 'dateModified': 1462716700, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70849', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Duplicate resize handles appear on unhighlighted image nodes after resize', 'description': {'raw': \"1. Select image node at <https://www.mediawiki.org/wiki/VisualEditor/Basic_example_worksheet#Media_files>\\n2. Resize an image\\n3. While a new thumb is generated and fetched from Commons, highlight a different image.\\n\\n## Unexpected behaviour\\n\\nObserve, after the thumbnail fetch has completed the dimmed pixelated thumbnail preview will be replaced with a sharp opaque rendering. Unexpected is that this new rendering results in the appearance of a new resize handle at its bottom right corner.\\n\\nThis new highlight and resize handle aren't supposed to exist and aren't properly kept up to date either (when reflowing the document they mostly stay behind and only update during more general regenerations).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1530904132, 'spacePHID': None, 'dateCreated': 1410640380, 'dateModified': 1530904132, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70817', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Error: Cannot allocate memory - fork(2) on node mediawiki-vagrant', 'description': {'raw': \"```\\nreview/jdlrobson/mantleview x ~/Sites/w/extensions/MobileFrontend $ vagrant provision\\n==> default: Running provisioner: lsb_check...\\n==> default: Running provisioner: puppet...\\nRunning Puppet with site.pp...\\nWarning: Could not retrieve fact ipaddress\\nError: Cannot allocate memory - fork(2) on node mediawiki-vagrant\\nError: Cannot allocate memory - fork(2) on node mediawiki-vagrant\\nThe following SSH command responded with a non-zero exit status.\\nVagrant assumes that this means the command failed!\\n\\nFACTER_fqdn='mediawiki-vagrant.dev' FACTER_forwarded_port='8080' FACTER_shared_apt_cache='/vagrant/cache/apt/' FACTER_environment='vagrant' FACTER_port_fragment=':8080' FACTER_share_owner='502' FACTER_share_group='20' FACTER_provider_name='virtualbox' puppet apply --templatedir /vagrant/puppet/templates --verbose --config_version /vagrant/puppet/extra/config-version --fileserverconfig /vagrant/puppet/extra/fileserver.conf --logdest /vagrant/logs/puppet/puppet.20f0fbdd9.log --logdest console --write-catalog-summary --modulepath '/tmp/vagrant-puppet-1/modules-0:/etc/puppet/modules' --hiera_config=/tmp/vagrant-puppet-1/hiera.yaml --manifestdir /tmp/vagrant-puppet-1/manifests --detailed-exitcodes /tmp/vagrant-puppet-1/manifests/site.pp || [ $? -eq 2 ]\\n\\nStdout from the command:\\n\\n\\n\\nStderr from the command:\\n\\nWarning: Could not retrieve fact ipaddress\\nError: Cannot allocate memory - fork(2) on node mediawiki-vagrant\\nError: Cannot allocate memory - fork(2) on node mediawiki-vagrant\\n```\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7bifphmxtcqgvdofuzla', 'dateClosed': 1478539905, 'spacePHID': None, 'dateCreated': 1410541620, 'dateModified': 1478539905, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70774', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: After removing the Template:Top,trying to place cursor on content throws TypeError: Cannot read property 'Left'/'right'/'start' of null\", 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a template Top, specify a bg color code so you can see the effect better on CE.I tried with #FFFFE0\\n3.Now click on Insert and Save the page\\n4.You will see the entire content after that template (until references list) gets added as a Content section for that template and inherits the styling specified in the template parameters.\\n5.Reopen the page\\n6.Reopen the transclusion dialog for that template\\n7.Click on the Delete icon to remove the template \"Top\" to just retain the usual format of the text.\\n8.Click on \"Apply Changes\"\\n9.Now when you are back to CE, try to place your cursor on the content which was part of that template\\n\\nObserved Result:\\nIt throws the following error on each click:\\n\\n\\nUncaught TypeError: Cannot read property \\'right\\' of null\\nUncaught Error: ve.dm.Document.getNodeFromOffset(): offset 85 is out of bounds \\n\\nPage:https://en.wikipedia.org/wiki/User:RYasmeen_(WMF)/sandbox?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14694}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1410203160, 'dateModified': 1429293280, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70571', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'The font size of headings in the \"Format\" dropdown doesn\\'t match the font size in the page content (in MonoBook skin)', 'description': {'raw': 'The Sub-heading 4 font as shown in the Text Style drop-down does not match with the other Sub-headings in it.\\n\\nScreenshot:\\n{F25185708}\\n(old screenshot: F15333)\\n\\nTask: Update the styles for VisualEditor\\'s \"Format\" dropdown when using the [MonoBook](https://www.mediawiki.org/wiki/Skin:MonoBook) [skin](https://www.mediawiki.org/wiki/Manual:Skins), so that the text size for headings inside the dropdown is the same as their size on the page.'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-jjpnfravajuw7o7kvmso', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1541117002, 'spacePHID': None, 'dateCreated': 1410188100, 'dateModified': 1541696361, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70559', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Please add a 'close' box to the wikitext warning\", 'description': {'raw': \"It's not obvious to everyone that you can click the wikitext warning to make it go away.  Please add an 'X' or something that makes it look like you should click on it if you don't want it to be there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410207810, 'spacePHID': None, 'dateCreated': 1410155760, 'dateModified': 1417571845, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70548', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pasting of MediaWiki article title H1 should paste as a <p> instead of an <h1>', 'description': {'raw': \"A thing that happens to me frequently is that I paste the title of another article. When this happens, it's formatted as a heading. This is correct HTML-wise, but it's never what I mean - I usually mean to paste it as plain text or as a link.\\n\\nIt would be nice if the VE vould guess it.\\n\\nA long shot, I know, but it happens to me a lot and I wanted to write it down :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1482173397, 'spacePHID': None, 'dateCreated': 1410095760, 'dateModified': 1488917379, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70519', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Be able to make block-level edits (e.g. language of a <div> / <ol> not a <span>)', 'description': {'raw': \"We'll need a way of editing these for the rare but useful block-level editing concepts that sometimes crop up.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1410033900, 'dateModified': 1643973178, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70498', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor/WikiEditor: Consistent terminology', 'description': {'raw': 'The terminology between WikiEditor (aka \"Advanced toolbar\") and VisualEditor MUST be consistent so people will not get confused.\\n\\nFor example in VisualEditor there is \"Cite\" menu, while in WikiEditor it is called \"Reference\" (Cite options in enwiki is only a gadget). It is super important, so we can guide new editors with same terminology. If you don\\'t like the old terminology in some cases - use new one, but fix the WikiEditor to use it too.\\n\\n\\n[Longer story]\\nToday I participated in a workshop for new editors. We told the new editors they should use either VE or classic wikitext, and gave them printed instructions what to do, and they got confused of it...\\n[The first time ever for me to open terminology bug, yay :)]\\n\\nSuggested terminology\\n| VE | classic edit (including WikiEditor) | Suggestion | Description\\n| Review your changes | Show changes | Show changes \\n| Cite | Reference | Reference | Cite may have disambig with quote. Both buttons are actually for adding reference/source\\n| Media | Embedded file (title), Insert file (dialog title) | Media | Media is more specific than file (e.g it doesn\\'t mean you can upload article as txt file)\\n| Heading, Sub-heading 1, Sub-heading 2... | Heading, Level 2, Level 3 | Heading, Sub-heading 1, Sub-heading 2... \\n| Search pages (in link dialog) | Target page (in link dialog) | Target page \\n| External link (link dialog) | URL (link dialog) | External link | Not sure what is better. URL seems to be more technical'}, 'authorPHID': 'PHID-USER-cfsvvgbtlqnbt2yokfjf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409923320, 'dateModified': 1492198750, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70439', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Vector's styling for H2 headers (with a line underneath) does not expand to full width when the context of the surrounding changes\", 'description': {'raw': 'Screen cast of the sequence\\n\\nWhen editing a page with an infobox on the side, header lines that ended on the infobox does not expand to full width if content added above them pushes them down below the infobox. \\n\\nThe opposite works thouhg, i.e. deleting content so a header lines move up shortens the header line so that they do not overlap the infobox.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F14886}'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1525335811, 'spacePHID': None, 'dateCreated': 1409835480, 'dateModified': 1525335811, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70397', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor jumps to the start of the line, if link and Language style text present.', 'description': {'raw': 'screenshot\\n\\n1> open a page in VE, insert a link. And after a space or two, insert some Language style text. \\n2> Now place the cursor at the end of the line and move along the line, the cursor jumps to the start of the line when it reaches the first character of the language style text .See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14760}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409756940, 'dateModified': 1416846084, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70344', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link, Formula and Text Styles etc. should be disabled when focus is inside the comment/gallery/math/hieroglypics/… editors', 'description': {'raw': '{F14756}\\n1> open a page in VE, insert a comment.\\n2> Click to edit the comment and insert a link. Notice the link icon is selected in the toolbar, although no link gets inserted in the comment . Try the above steps, with Formula and text styles like Underline, Strikethrough. See screenshots.\\n\\n'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409755980, 'dateModified': 1535710597, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70343', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Distinguish better between media types in the search interface and in the editing surface', 'description': {'raw': 'Screenshot of embeded video\\n\\nI think it would be better to distinguish better videos and pictures:\\na) in media selection\\nb) in the text itself\\n\\na) if Id like to add video, I am not able to determine, which previous in media selections are videos and which not. Thus I must go to Wikimedia Commons anyway and add it like a unique filename.\\n\\nb) attached screenshot shows, I add somethink and it still looks like an image - even its a video file.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F14720}'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409651580, 'dateModified': 1643973179, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70284', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: There should be a link to the template page even if template description is available', 'description': {'raw': \"When a template doesn't have a description in TemplateData, a link is shown to the template's page in the Template namespace (using the visualeditor-dialog-transclusion-no-template-description message).\\n\\nThis link is very useful.\\n\\nI don't see such a link when a template does have a description. Compare, for example, how adding {{Reflist}} is different from adding {{LGBT Welcome}}.\\n\\nFor advanced users the description in TemplateData is not a replacement for the whole page, so there should always be a link to the template page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1434809964, 'spacePHID': None, 'dateCreated': 1409644740, 'dateModified': 1434809964, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70279', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make the CAPTCHA more visible when saving', 'description': {'raw': \"1. Sign up with a new username to a Wikimedia site.\\n2. Edit an article and add an external link.\\n3. Try saving.\\n\\nAfter entering an edit summary and pressing the button in the dialog, the dialog remains and the CAPTCHA is shown in its bottom. At least on my machine, I need to scroll down in the dialog to actually see the CAPTCHA. I saw new users puzzled over this - they thought that they already pressed the save button and couldn't understand why is the dialog still there.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-v7iovheqigasai3pzdax', 'dateClosed': 1546983912, 'spacePHID': None, 'dateCreated': 1409596440, 'dateModified': 1546987182, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70266', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Bugzilla: Create keyword for usability', 'description': {'raw': \"The design and accessibility keywords aren't sufficient to cover cases where usability is the main hurdle.\\n\\nBe it an existing implementation that is hard to use and needs input to improve it, or a new feature/bug that is blocked on having an intuitive interface.\\n\\nIn cleaning up bugs I often see this word in the title but would be interested in giving it its own keyword for interested parties (especially the Wikimedia UX team) to look at.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409588985, 'spacePHID': None, 'dateCreated': 1409582520, 'dateModified': 1409601718, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70259', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Create new topic\" does not work with $wgFlowContentFormat = wikitext', 'description': {'raw': '**Author:** `bsitu`\\n\\n**Description:**\\nIt throws invalid workflow exception\\n\\n---\\nSee {T88908}.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-kms5nmb5gvqzcdep3cnl', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kms5nmb5gvqzcdep3cnl', 'dateClosed': 1429264967, 'spacePHID': None, 'dateCreated': 1409272980, 'dateModified': 1429770288, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70148', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"data labels in imageinfo API don't make sense\", 'description': {'raw': 'The data currently returned by the imageinfo API assigns the author to \"artist\" and the source to \"credit\". Both of these are incorrectly labeled. In particular these labels make it difficult to figure out the proper attribution for the image, as it sounds like you should use \"credit\", but you should actually use \"artist\".\\n\\nhttps://en.m.wikipedia.org/w/api.php?action=query&format=json&prop=imageinfo&titles=File%3ALiber_Eliensis%2EPNG&iiprop=url%7Cextmetadata\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-a6p24cvyblhfzc7we7nc', 'dateClosed': 1603828394, 'spacePHID': None, 'dateCreated': 1408730400, 'dateModified': 1603828394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69914', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'MediaWiki should not expose any UI elements which require JavaScript when it is off (tracking)', 'description': {'raw': '**Author:** `gryllida`\\n\\n**Description:**\\nfrom bug 54730#c3\\n>The general design principle in MediaWiki is to only show functional user interface elements (for example, unprivileged users are not shown a delete tab or a protect tab)\\n\\nI would like MediaWiki to not expose any features which require JavaScript when it is off.\\n\\nThis means, for instance, not showing visual editor\\'s edit tab, bug 69779  (noting \\'requires javascript\\' where necessary in the beta tab).\\n\\nI hope to succeed in making this a tracking bug for enforcing the above-quoted design for the \"no JS enabled\" case.\\n\\n--------------------------\\n**Version**: 1.24rc\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410246503, 'spacePHID': None, 'dateCreated': 1408616100, 'dateModified': 1553164276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69845', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Categories go at the bottom, so please place the cursor above the categories', 'description': {'raw': 'Especially when there are only categories on the page, it does not appear to be possible to put text above the categories.  The result is things like this:\\n\\nhttp://en.wikipedia.beta.wmflabs.org/w/index.php?diff=122314&oldid=51987\\n\\nwhich is not normally wanted.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1408562280, 'dateModified': 1424891618, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69802', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"[collapsibleTabs] If a tab's width changes after initial page load, endless animation loop can happen\", 'description': {'raw': 'Alternative: {T254277}\\n\\nIf the \"View history\" tab changes size such that becomes too large where it before was not, an endless animation loop of collapse-expand-collapse-etc can be triggered. A resize could be caused by an ordinary zoom (frequently resizing the pixel width of the element by a few pixels), by a change in browser text size preferences (likely to significantly change the width), or by a user script modifying the text content of the element.\\n\\nThis appears to be caused by expandCondition in Vector.js using a cached version of the element\\'s width (collapsibleTabs.data\\'s expandedWidth passed as the eleWidth argument), while collapseCondition is checking .width() each time.\\n\\nThis happens when you enable `Editing mode: show both tabs is enabled in preferences` in VisualEditor and visit https://www.mediawiki.org/wiki/User:Martin_Urbanec?uselang=fr at certain screen resolutions. Demonstrated in image below:\\n{F5061717}\\n\\n== Solutions\\n\\n#### Option 1 - Remove the animation and fix the collapsibletabs code:\\n\\nRationale: The animation plays at times when it\\'s not meaningful, eg. after page load. The tabs should be collapsed immediately, without animation.\\nAbout half of the code is removed, including callbacks, resulting in a simple, less error-prone logic.\\nAnalysis of the bug, solution:  T71729#6183821 **Remove animation**\\n\\n#### Option 2 - Keep the animation, fix the collapsibletabs code:\\n\\nRationale: Keeps the old functionality (animation) while safeguarding against the oscillation.\\nSolution:  T71729#6183821 **Easy fix**\\n\\n#### Option 3 - Make the tabs responsive\\n\\nRationale: No more collapsing, the tabs wrap into any number of rows.\\nMostly CSS solution with a one-liner resize event handler.\\nSolution detailed: T71729#6183822 \\n\\n\\n\\n== Update 2020-05-30\\n\\nThis bug resurfaced as a more prominent regression after the #mw1.35.0-wmf.34 deployment:\\n{T253819}\\nThe difference is: the \"More\" (\"Plus\" / \"Mehr\") menu is //not// visible:\\n{F31848748}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'dateClosed': 1633640757, 'spacePHID': None, 'dateCreated': 1408416060, 'dateModified': 1696266662, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69729', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Please show the file name in the media dialog, and make it easy to copy it', 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Open a page that contains an image that has a really long or complicated name.\\n\\n2.  Think, \"Hey, I could use that image over at ______ article, too.\"\\n\\n3.  Click on the image.  What\\'s its name?  Well, it starts off as File:Foo bar baz bat... but who knows what the rest of it is.\\n\\n\\nIt would be nice to be able to see the entire name of the image and to copy that name as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1437955553, 'spacePHID': None, 'dateCreated': 1408405260, 'dateModified': 1439425494, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69726', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"New template\" is a confusing window title', 'description': {'raw': 'When adding a template to a page, the window title is \"New template\". This is quite confusing. Some users complained that it sounds like creating a whole new template.\\n\\nPlease consider retitling it to something like \"Add a template\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408587004, 'spacePHID': None, 'dateCreated': 1408366140, 'dateModified': 1443278029, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69692', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Investigate lenient handling of quotes in xml-tag attribute values', 'description': {'raw': 'https://en.wikipedia.org/wiki/Dachshund#Coat_and_color has a complex gallery tag:\\n\\n<gallery widths=\"200px\" heights=\"200px\" perrow=\"5\" caption= \"There are three types of dachshund, which can  be classified by their coats: short-haired, called \"smooth\"; long-haired; and wire-haired\">\\nFile:Wirehaired_Dachshund.jpg|A wire-haired dachshund\\nFile:Kurzhaardackel.jpg|A short-haired dachshund\\nStd Dachshund 600.jpg|A long-haired standard dachshund\\nFile:Piebald.jpg|A piebald dachshund\\nFile:Red-merle smooth Dachshund.jpg|A dapple dachshund</gallery>\\n\\n\\nIt\\'s being displayed as raw wikitext in VisualEditor on desktop.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66065'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1441764080, 'spacePHID': None, 'dateCreated': 1408231860, 'dateModified': 1441764080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69652', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Keyboard shortcut dialog style differs between standalone and MW, ugly line wraps in MW', 'description': {'raw': 'The keyboard shortcut styling is substantially different between the standalone demo and the MW integration in terms of font size. In MW, the font size is so much bigger that some shortcuts awkwardly break across lines. For instance, \"Ctrl+Shift+V\" is split with the \"V\" being on a line by itself. In SA, the font size is smaller (for the headings and the shortcuts, but not the descriptions) so this problem doesn\\'t happen, but there the font feels a bit *too* small.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1408636626, 'spacePHID': None, 'dateCreated': 1408173420, 'dateModified': 1443278029, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69643', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When changing Hovercards settings, does not default to my current setting', 'description': {'raw': 'When I go to \"Enable Hovercards\" to change my settings, it always defaults to \"Read Quickly\", even when I explicitly change it to \"Monitor or Edit\", save, then re-open the dialog to check the setting.\\n\\nTested in Firefox/Iceweasel 30.0\\n\\n--------------------------\\n**See Also**: {T71576}'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'dateClosed': 1470700163, 'spacePHID': None, 'dateCreated': 1408052580, 'dateModified': 1470747666, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69577', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide ability to deal easily with dead links', 'description': {'raw': \"I met User:Zoony at Wikimania and he said that something which he'd love to see in VE is a way to deal easily with dead (rotten) links.\\nHe suggested that a right click could launch a menu which provides access to several options, from searching on a search engine in a different tab (to try to fix one) to pasting the {{dead link}} template.\\n(More info about ways to deal with dead links at https://en.wikipedia.org/wiki/Wikipedia:Link_rot#Repairing_a_dead_link ).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1408030140, 'dateModified': 1643973181, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69547', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Run automated browser tests across set of Wikimedia wiki pages to ensure proper JavaScript', 'description': {'raw': 'Ideas of things to scan for:\\n\\n* Any request resulting in an error response (404 Not Found, 500 Internal Error, etc.).\\n* Uncaught JavaScript exceptions.\\n* Network requests made to third-party domains (images, stylesheets, scripts, xhr, etc.)\\n\\nFrom comment 13 at {T71445} :\\n> However it would be great to have automated tests running after changes in common.js and gadgets. Such general tests can at least validate no external resource is loaded, or no invalid syntax is added.\\n> The simplest option is to run it outside MW (such as a script in labs that runs X times a day), but an extension to do it while editing would be even better...\\n> \\n> BTW\\n> I just runned a simple phantomjs script on all wikipedia languages to catch simple errors:\\n> \\n> testing als\\n> ERROR: ReferenceError: Can\\'t find variable: ta\\n> TRACE:\\n> -> https://als.wikipedia.org/w/index.php?title=MediaWiki:If-pt-login.js&action=raw&ctype=text/javascript&dontcountme=s: 9\\n> \\n> testing kk\\n> ERROR: TypeError: \\'null\\' is not an object (evaluating \\'document.getElementById(\\'mw-vector-current-variant\\').innerHTML=wgULS(\"Кирил\",\"Latın\",\"توتە\")\\')\\n> TRACE:\\n> -> https://bits.wikimedia.org/kk.wikipedia.org/load.php?debug=false&lang=kk&modules=site&only=scripts&skin=vector&*: 9\\n> \\n> \\n> anyone wants to fix them? :)\\n> \\n\\nFrom comment 14 at T71445:\\n> Example for errors across wikis\\n> Maybe it is a bit off-topic but here are some cases of errors across wikis in simple read/edit transaction using phantomJS\\n\\nSee also:\\n* {T71519}\\n* {T106770}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1691360468, 'spacePHID': None, 'dateCreated': 1407983460, 'dateModified': 1691360468, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69519', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying from Microsoft Word adds XML cruft like \" <w:WordDocument>\\n\" (mso = Microsoft Office)', 'description': {'raw': 'Scan down these to find lots of garbage, including lines like:\\n\\n</xml><![endif]--><!--[if gte mso 9]><xml>\\n\\nor \\n\\n<!--[if gte mso 9]><xml>\\n\\nhttps://fr.wikipedia.org/w/index.php?title=Catherine_Lemorton&curid=1711917&diff=105874955&oldid=105753648\\n\\n\\nhttps://fr.wikipedia.org/w/index.php?title=Paul_C%C3%A8re&curid=8199909&diff=106116894&oldid=106116223\\n\\nhttps://fr.wikipedia.org/w/index.php?title=Paul_C%C3%A8re&curid=8199909&diff=106116209&oldid=106116068 \\n\\nhttps://fr.wikipedia.org/w/index.php?title=Andr%C3%A9_Grassi&curid=5857691&diff=106069630&oldid=105919440 \\n\\nhttps://fr.wikipedia.org/w/index.php?title=Capitulaire_de_Coulaines&curid=1578466&diff=106053129&oldid=90262123 \\n\\nhttps://fr.wikipedia.org/w/index.php?title=Charles_Ateba_Eyene&curid=7794227&diff=105959949&oldid=105470353\\n\\n\\nThis may be helpful in finding others:\\n\\nhttps://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Modifications_r%C3%A9centes&days=30&from=&tagfilter=balise+HTML+interdite\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=69821\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61371'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427402940, 'spacePHID': None, 'dateCreated': 1407974760, 'dateModified': 1438735643, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69513', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Page options icon is confusing', 'description': {'raw': 'From John Broughton:\\n\\nIt would be easier to remember what this menu does, and to tell others about it (say, in the User Guide) if the icon for it were the text “Page” (with a down-arrow) rather than three horizontal lines. This menu icon approach is used for the “Insert” and “Cite” menus, which helps users immediately understand (and/or remember) what type of items are on the menu.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1523017134, 'spacePHID': None, 'dateCreated': 1407972420, 'dateModified': 1523017134, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69509', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable Visual Editor for Math by default', 'description': {'raw': \"**Author:** `physik`\\n\\n**Description:**\\nI'm using the vagrant role visual-editor for my wiki.\\nAfter enabling the visual editor role I could not edit formulae... The message is available in source mode only.\\nI see that the visual editor for math is not super fancy now, but it should be somehow stable?\\nIf not this can become a tracking bug to trace of the bugs that need to be resolved.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407941455, 'spacePHID': None, 'dateCreated': 1407933840, 'dateModified': 1418755556, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69466', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Consider whether exiting the link dialog in create mode should remove the link', 'description': {'raw': '**Author:** `ronnirubin`\\n\\n**Description:**\\nRe bug 68101\\n\\n> Load VE. Say \"Foobar\" is the first word on the page.\\n> If you click on the link tool, by mistake or not, without selecting anything before, Foobar will automatically become a link to the Foobar page (it doesn\\'t help that pressing ESC doesn\\'t abort the action, the link gets applied anyway, as we know).\\n\\nESC _should not_ exit and save; it should either exit without saving, or revert the change (in this case, the link) without exiting.  I was going to set the Severity to \"blocker\", as it would block installation on en.Wikipedia, but that would be wrong.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1561738917, 'spacePHID': None, 'dateCreated': 1407776940, 'dateModified': 1561738917, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69407', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Highlight that you can incrementally adjust the edit summary', 'description': {'raw': 'When editing in VisualEditor, you can click \"save\", add some text to the edit summary, click \"resume editing\", edit some more, and repeat. This kind of incremental summary is a fairly common request from editors who add to the summary field when they make each successive change in an edit. \\n\\nSo we actually have the capability they\\'re requesting, but it\\'s not well designed for this use case\\n'}, 'authorPHID': 'PHID-USER-imut7wxehhy35ukuzaks', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1407758940, 'dateModified': 1439321001, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69393', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Find a way to make the link button is more discoverable', 'description': {'raw': '**Author:** `che`\\n\\n**Description:**\\nYesterday I tried VisualEditor for the first time, after nine years of editing wikitext. I took me several minutes to find out how to make a link. I have tried text styles drop-down (as it has an underlined letter, which I associated with hyperlinks), the the \"insert\" drop-down, which included several useful objects, but not the hyperlink option. I have tried typing \"[[\", which has shown me a warning that wiki syntax does not work, but did not tell how to create a link in VisualEditor. Then I went through citation and list-formatting menus, before finally stumbling onto the link button, which is sort of grey, and the only button in the line that has no drop-down arrow. In retrospect, I guess I though it is some kind of separator.\\n\\nSome things that might have made my life easier:\\n- a bit more obvious link button\\n- having another link option in \"insert\" menu (with the same icon, so I could discover it on the toolbar afterwards)\\n- having mr. Clippy\\'s \"It looks like you\\'re attempting to use wikitext\" message point me to the VisualEditor equivalent of what I\\'m trying to do (by showing the icon or highlighting the button on toolbar)\\n\\nAlternatively, interpreting wikitext in VisualEditor might make life easier for users experienced with it\\'s syntax, but that might be a stupid idea.\\n\\nIn any way, thank you for your work on VisualEditor. You\\'re pushing as all forward towards a better future :-)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1519404429, 'spacePHID': None, 'dateCreated': 1407676140, 'dateModified': 1519404429, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69364', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Label the \"Remove\" button in link inspector as \"Cancel\" if in link creation mode', 'description': {'raw': 'For example, if you open the link tool on a blank page, there is nothing to \"Remove\" and nothing to \"Open\", so those buttons should be grayed out.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429559683, 'spacePHID': None, 'dateCreated': 1407652020, 'dateModified': 1429559894, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69359', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Text style drop-down overridden by edit comment, in Monobook skin.', 'description': {'raw': 'screenshot\\n\\nenvironment- test2\\n\\n1> open page in VE, insert a comment.\\n2> Click to edit the comment.\\n3> Now click on the Text Style Menu, notice the  text style drop-down opens with edit comment dialog overriding it . Please see screenshot.\\n\\nOnly on Monobook skin, same issue found in FF.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14206}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409247899, 'spacePHID': None, 'dateCreated': 1407445440, 'dateModified': 1443278036, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69263', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Caret looks disconnected from link box in Monobook skin when going to first letter of line', 'description': {'raw': 'screenshot\\n\\n1> Open a page in VE, the skin is Monobook.\\n2> Insert a link.\\n3>While the link icon is visible, move the cursor to the beginning of the link. The link icon looks broken. See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows XP\\n\\n**Attached**: {F14152}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409247941, 'spacePHID': None, 'dateCreated': 1407422460, 'dateModified': 1443278036, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69242', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VE's beta help adds a question mark to 'Switch to source editing'\", 'description': {'raw': 'VE\\'s help icon popup includes this \"visualeditor-beta-warning\" text:\\n\\n... To switch back to source editing at any time without losing your changes, open the dropdown next to \"Cancel\" and select \"Switch to source editing?\".\"\\n\\nThe last message is \\'visualeditor-mweditmodesource-title\\'.  But the item in the dropdown is actually visualeditor-mweditmodesource-tool, which is \"Switch to source editing\" without a question mark. Trivial to fix.\\n\\n(Also \"Cancel\" is gone from the VE UI, I filed bug 69201.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407959184, 'spacePHID': None, 'dateCreated': 1407357360, 'dateModified': 1443278036, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69203', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add a proper way in MobileFrontend to load custom editors', 'description': {'raw': 'Currently the MobileFrontend provides two editors : one using wikitext and one based on the VisualEditor. It would be nice to have a proper editor loader in order to allow to the creation of customized editors by other extensions (an use case may be an editor for Wikisource Page: pages).\\n\\n**See Also**:\\n* {T67165}'}, 'authorPHID': 'PHID-USER-5paybpgtxjrhikdos3p5', 'ownerPHID': None, 'status': {'value': 'stalled', 'name': 'Stalled', 'color': 'yellow'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1407330780, 'dateModified': 1595557724, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69177', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: ResourcesTest::testUnsatisfiableDependencies: The module 'mobile.editor.ve' must not have target 'desktop'\", 'description': {'raw': \"With attachment 16112:\\n\\n119) ResourcesTest::testUnsatisfiableDependencies\\nThe module 'mobile.editor.ve' must not have target 'desktop' because its dependency 'ext.visualEditor.mobileViewTarget' does not have it\\nFailed asserting that an array contains 'desktop'.\\n\\n/srv/vagrant/mediawiki/tests/phpunit/structure/ResourcesTest.php:98\\n/srv/vagrant/mediawiki/tests/phpunit/MediaWikiTestCase.php:133\\n/srv/vagrant/mediawiki/tests/phpunit/MediaWikiPHPUnitCommand.php:42\\n/srv/vagrant/mediawiki/tests/phpunit/phpunit.php:160\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1438385391, 'spacePHID': None, 'dateCreated': 1406848200, 'dateModified': 1439331340, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68956', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: dm.Document seems to not get the right lang and dir settings inside the Media Dialog in insert mode', 'description': {'raw': \"… so instead it falls back to the built-in defaults (en and ltr), but really it shouldn't ever get to this position.\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1406764980, 'dateModified': 1449024310, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68888', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Metas at the end of a link annotation's anchor cause it to be split; should instead change with it\", 'description': {'raw': '(Taken from bug 52127.)\\n\\nPreviously, before comments were node-ified, editing\\n\\n  [[Foo|Bar<!--Foo!-->]]\\n\\n… to point to \"Baz\" would create the wikitext:\\n\\n  [[Baz|Bar]][[Foo|<!--Foo!-->]]\\n\\n… whereas it should have done\\n\\n  [[Baz|Bar<!--Foo!-->]]\\n\\n… (i.e., meta items inside annotations should get changed when the annotation changes, not keep their existing ones).\\n\\n\\nAs comments are (mostly) now nodes, this doesn\\'t apply to them, but will apply to other meta items like {{DISPLAYTITLE:Foo}} or whatever broken items might exist.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1517251219, 'spacePHID': None, 'dateCreated': 1406598120, 'dateModified': 1517251221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68779', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reconsider template tool tabbing behaviour to go to the next field (not the info or remove buttons)', 'description': {'raw': 'This is possibly by design, but I found it unexpected:\\n\\nUse the Cite tool with any example having multiple fields to fill in, e.g. Website or Book.\\n\\nEnter a field. Hit TAB.\\n\\nI would expect the cursor to go to the next editable field, but instead the cursor highlights first the Field description icon, then the Remove field icon, and only after that moves to the next editable field.  The user must tab three times to put the cursor into the next editable field.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1433458448, 'spacePHID': None, 'dateCreated': 1406581620, 'dateModified': 1611950093, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68768', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Increase indentation is not working when the list is wrapped around a left aligned image', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n4.Add a numbered list or bullet list after that\\n5.Make the image left aligned \\n6.When the list gets wrapped on the right side of the image,place the cursor on one item in the list\\n7.Try increasing the indentation\\n\\nObserved Result:\\nNothing happens.No indentation is added to the listed item.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1528134102, 'spacePHID': None, 'dateCreated': 1406243820, 'dateModified': 1528134102, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68540', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reconsider the \"Insert\" menu because it doesn\\'t always insert', 'description': {'raw': 'Use case:\\n\\n1. On a page with a heading and some text. Put cursor at start of the paragraph after the heading.\\n2. Insert a template (ends up selecting it after finishing insertion)\\n3. \"Insert\" another template.\\n\\nExpected:\\n\\nA dialog should appear with the ability to decide which template to insert etc.\\n\\nActual:\\n\\nA dialog appears to edit the selected transclusion that is already on the page.\\n\\n\\nAfter being genuinely confused for a minute I realised that the confusion came from the menu label being \"Insert\". A while back, the \"Template\" button was separate on the toolbar (or under \"More\" or \"Tools\" whatever it was). Back then, like still the case with Links and Text Style, it was more natural to assume it will edit and not create a template when a template is selected already because the button would be rendered in an \"active\" (pressed-down) state (like for links and text style). However, the menu was then relabelled to \"Insert\" and the items in the \"Insert\" menu do not have an \"active\" state to help correlate with the currently selected item on the page.\\n\\nPerhaps we should bring back the \"active\" state for the Insert menu items, for consistency with other buttons on the toolbar.\\n\\nOr make it actually insert a new one at/before the current cursor position, which would mean that to edit a transclusion users then need to use the context menu instead.'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1406168400, 'dateModified': 1655734476, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68494', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Chrome 36 and higher throws \"Discontiguous selection is not supported\" on opening the editor', 'description': {'raw': 'Might be related to bug 68492.\\n\\n> Discontiguous selection is not supported. rangy-core-1.3.js:2842\\n>> (anonymous function) rangy-core-1.3.js:2842\\n>> (anonymous function) rangy-core-1.3.js:2852\\n>> (anonymous function) rangy-core-1.3.js:327\\n>> init rangy-core-1.3.js:249\\n>> loadHandler rangy-core-1.3.js:365\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412591488, 'spacePHID': None, 'dateCreated': 1406167740, 'dateModified': 1443278062, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68493', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't use Range.detach (is now a no-op in Chrome per revised DOM spec)\", 'description': {'raw': \"Chrome emits this notice when using VisualEditor anywhere.\\n\\n> 'Range.detach' is now a no-op, as per DOM (http://dom.spec.whatwg.org/#dom-range-detach).\\n\\n\\nLooks like more than the typical deprecation, because it's been replaced with a no-op. No idea if we/Rangy are relying on it doing something. Could cause all kinds of weird state inconsistencies.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410404341, 'spacePHID': None, 'dateCreated': 1406167560, 'dateModified': 1443278062, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68492', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Consider changing behaviour on launch when the database is locked', 'description': {'raw': 'Environment- Betalabs\\n\\nSteps to Reproduce-\\n\\nFor Chrome-\\n1> Logged in and trying to switch to VE interface by clicking on \"Edit beta\" tab shows the spinner for a while and remains in the read mode.\\n2> Now click on \"Edit Source\" tab opens the Wikieditor interface.\\n3> Click on \"Edit beta\" tab again, takes you to the Read only mode instead.\\n\\nFor FF-\\n1>Logged in and trying to switch to VE interface by clicking on \"Edit beta\" tab shows the pop-up with message \"Error loading data from server: readonly: The wiki is currently in read-only mode. Would you like to retry?\", with the spinner in the background forever.\\n\\nFor Safari-\\n1>Logged in and trying to switch to VE interface by clicking on \"Edit beta\" tab shows the pop-up with message \"Error loading data from server: readonly: The wiki is currently in read-only mode. Would you like to retry?\"\\n\\nThis issue is related to Bug 59010 and Bug 60765.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1406041440, 'dateModified': 1643973185, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68383', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:While switching to edit source mode without making any edit through the Page Options , the confirmation dialog for saving change appears', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Without making any change , go to page options next to \"Save Page\" button\\n3.Select the option \"Switch to source editing\"\\n\\nObserved Result:\\nThe confirmation dialog to keep ot discard changes appears.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14213}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406075282, 'spacePHID': None, 'dateCreated': 1405710600, 'dateModified': 1443278068, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68229', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: [Regression wmf15] Pressing backspace to delete  the link target inside link inspector closes the inspector', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with Mobile VE\\n2.Open link inspector\\n3.Type something in the text field to bring up the suggestions\\n4.Select one suggestion from the drop down\\n5.Place the cursor at the end of the link target name in the field\\n6.Press backspace to delete it\\n\\nObserved Result:\\nInstead of deleting the link target , it takes user to the CE closing the inspector.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1434487702, 'spacePHID': None, 'dateCreated': 1405635060, 'dateModified': 1434492396, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68195', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'browser tests failing with \"getaddrinfo: Name or service not known (SocketError)\"', 'description': {'raw': 'This was mentioned on the \"[QA] Failing MobileFrontend browser tests\" thread in July. I have seen a few more  \"getaddrinfo: Name or service not known (SocketError)\" errors with Flow browser tests, and then today we got four of them. :-(\\n\\nSee https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/65/\\n\\nAll three tests failures in https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/65/ at Jul 16, 2014 6:26:46 PM (UTC?) were with this error.\\n\\n15 minutes earlier, https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/72/ also failed with \"getaddrinfo: Name or service not known (SocketError)\". The other test failure was an action that took longer than 5 seconds to complete.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'dateClosed': 1427725956, 'spacePHID': None, 'dateCreated': 1405546200, 'dateModified': 1427916531, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68125', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: there is no way to change the template name without re-filling all the params', 'description': {'raw': 'There are templates that have a different name, but the same parameters. For example, the many lang-XX templates. If I see that the parameter text is correct, but an incorrect template was used, and the template should be {{lang-ru}} and not {{lang-be}}, I can simply change the template name. In VE I need to delete the whole template and re-add it. This is silly, but tolerable, for a template with one parameter, but there are such templates with more parameters.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1405488660, 'dateModified': 1643973186, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68088', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Suppress being able to click on links in the error messages from mis-placed local wiki customisations', 'description': {'raw': 'window with message\\n\\nCalling message [[:en:Wikipedia:Edit filter]] \\n\\nFor example message \"redrect to itself\" (this filtermessage in ru-wiki; in en-wiki is no such call filter, but may work with other message)\\n* Edit page in VE\\n* Copy page title\\n* [Ξ] → Page settings → check \"Redirect this page to\" → past page title (page name of this article)\\n* Press Save page (in interface) → Save page (in floating window)\\n\\n* Start showing Edit filter message (1 image 1)\\n* Clik on link in this message - new page open in this floating window and this window i can\\'t close or go back to message (image 2)\\n\\nLink should open in a new window\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Windows 8.1\\n**Platform**: PC\\n\\n**Attached**: {F14349}'}, 'authorPHID': 'PHID-USER-5joeladhczukimiv4rwl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1562026815, 'spacePHID': None, 'dateCreated': 1405438800, 'dateModified': 1562026815, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68040', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Switching tabs in memory-limited browsers (esp. mobile ones) often causes page to refresh, causing data loss of session changes', 'description': {'raw': 'Invoke VE from iOS Safari on tablet,\\n\\nMake changes to page in VE \\n\\nOpen second tab, load another website, \\n\\nSwitch back to tab with VE instance, page is reloaded, and changes are lost'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1520342734, 'spacePHID': None, 'dateCreated': 1405412400, 'dateModified': 1520342734, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz68017', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'One-click system for setting user preferences', 'description': {'raw': 'This was an interesting comment from WhatamIdoing on T69826, so I thought I\\'d split it out for its own discussion.\\n\\n> Changing default user preferences means overriding the choices of \\n> registered editors who actually want the feature (including thousands of \\n> editors who voluntarily opted-in before MediaViewer was made avaialble \\n> by default).  \\n> \\n> It\\'s too bad that MediaWiki doesn\\'t have a good one-click system for \\n> changing prefs, like a \"Click here to enable X\" button or pop-up.  It\\'d be \\n> so much easier than telling hundreds of users \"Go to Special:Preferences, \\n> click to this tab, scroll halfway down, find this item, tick the box, scroll \\n> all the way down, save the page.\"\\n\\n--------------------------\\n**See Also**:\\n* {T34811}\\n* {T69883}'}, 'authorPHID': 'PHID-USER-uia2q3o33h5pb5lf7exz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1405075320, 'dateModified': 1706237329, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67846', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Deprecated param w/out description text \"no description\" isn\\'t in italic grey', 'description': {'raw': '**Author:** `gabrasca2`\\n\\n**Description:**\\nVisualEditor deprecated text\\n\\nWhen a param is indicated as \"deprecated\": true and it has no description, in the TemplateData parameters table the text \"no description\" isn\\'t in italic grey.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14398}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-je4a7kqdfgacwkyhtg4c', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421459299, 'spacePHID': None, 'dateCreated': 1404988140, 'dateModified': 1426055072, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67794', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Making an image Frame-left/Frame-right redraws the highlight beyond CE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Make it frame-left or frame-right.\\n\\nObserved Result:\\n\\nThe highlight for the image goes beyond the page\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14208}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1404864480, 'dateModified': 1416846363, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67706', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[DO NOT USE] Support non-image media (tracking) [superseded by #VisualEditor-MediaWiki-Media]', 'description': {'raw': \"We currently don't. We should.\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422403165, 'spacePHID': None, 'dateCreated': 1404850380, 'dateModified': 1500332617, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67690', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: While inserting an image for the first time, the label for the button in Media Settings dialog should be \"Insert {image|animation|audio|video}\" instead of \"Apply Changes\"', 'description': {'raw': 'Right now while inserting an image, the button that shows up in the Media Settings dialog is \"Apply Changes\", it should be \"Insert\" instead , since there is no change here rather insertion.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1422409248, 'spacePHID': None, 'dateCreated': 1404849960, 'dateModified': 1438735998, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67688', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"In HTML+RDFa DOM, make the 'params' block give a 'normalised' version of the parameter name (like done for template)\", 'description': {'raw': 'Copied from my Russian Wikipedia talk page: https://ru.wikipedia.org/wiki/%D0%9E%D0%B1%D1%81%D1%83%D0%B6%D0%B4%D0%B5%D0%BD%D0%B8%D0%B5_%D1%83%D1%87%D0%B0%D1%81%D1%82%D0%BD%D0%B8%D0%BA%D0%B0:Keegan_(WMF)#Bug_report_11\\n\\nI filled TemplateData for Шаблон:Малая планета\\n\\nearly, template with comments inserted in articles\\n{{Малая планета\\n<!-- Основной блок -->\\n | param        = \\n<!-- Орбитальные характеристики -->\\n | param        = \\n<!-- Физические характеристики -->\\n | param        = \\n}}\\nnow if i deleted comments https://ru.wikipedia.org/w/index.php?title=(87)_Сильвия&diff=64040824&oldid=62184664 then i can see parameters in VE editor\\nbut if comments still in text then VE editor for template staying on \"Загрузка...\" (\"Load...\") and don\\'t show parameters. sample: (25143) Итокава\\nSunpriat 08:40, 6 июля 2014 (UTC)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-56wtmb23orq4pu5liyj5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414693898, 'spacePHID': None, 'dateCreated': 1404797580, 'dateModified': 1414694346, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67657', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve.ui.FragmentInspector immediately closes after opening on Opera 12, when opened using the context tooltip', 'description': {'raw': \"The inspector for <syntaxhighlight /> node immediately closes after opening on Opera 12. I don't yet know why, but I am going to find out.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416090593, 'spacePHID': None, 'dateCreated': 1404473940, 'dateModified': 1417571679, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67530', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Changing language of a <syntaxhighlight /> node doesn't load styles for new language\", 'description': {'raw': 'Changing language of a <syntaxhighlight /> node doesn\\'t load styles for new language. \\n\\nSyntaxHighlight_GeSHi defines a module for each supported language (in the format \"ext.geshi.language.$lang\"), VE should ensure that the appropriate module is present. Not sure how the content is updated, but the information about required modules should be provided in the ParserOutput and by the action=parse API.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58388'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1435183523, 'spacePHID': None, 'dateCreated': 1404435480, 'dateModified': 1632170097, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67515', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: [Regression wmf12] The highlight for centered images is taking 100% width', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Make it centre aligned\\n4.Keep it selected\\n\\nObserved Result:\\nThe highlight for the centered image is taking 100% width\\n\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14351}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1410804238, 'spacePHID': None, 'dateCreated': 1404427980, 'dateModified': 1443278096, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67507', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"No results found\" message appearing even before entering a search term inside Media Settings dialog', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Go to Insert>Media\\n\\nObserved Result:\\n\"No results found\" message appearing even before entering a search term inside Media Settings dialog\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n\\n**Attached**: {F14200}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409960673, 'spacePHID': None, 'dateCreated': 1404338520, 'dateModified': 1443278098, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67438', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Parameter data doesn't always end up in the right parameter box in Firefox\", 'description': {'raw': 'Report from Jay8g about a bug that may be very hard to reproduce:\\n\\n\"After adding a parameter in the (advanced) template dialog, the focus briefly shifts to the previously added (edited) parameter before going to the one just added. This has led to me occasionally (about one in ten parameter additions) typing (generally just one character) in the wrong box\"\\n\\n\"I would type something *immediately* after clicking the parameter button and it would only happen occasionally\"\\n\\n\\nJay\\'s running Firefox 30 on Windows 7.  I\\'ve been unable to reproduce this, but I probably haven\\'t tried enough times or been fast enough.  I\\'ve been wondering whether this might be easier to reproduce on an old, slow computer.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1404324840, 'dateModified': 1426644332, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67427', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  TemplateData not being processed for a template that isn't in the Template: namespace\", 'description': {'raw': \"When we try to add this template:\\n\\nhttp://en.wikipedia.org/wiki/User:Jay8g/sandbox/Template:Airline fleet table/Start\\n\\nthe TemplateData does not appear in the dialog.\\n\\nIf we add the doc subpage directly:\\n\\nhttp://en.wikipedia.org/wiki/User:Jay8g/sandbox/Template:Airline fleet table/Start/doc \\n\\nthen TemplateData appears.\\n\\nWe have already made at least three null edits to the template.  I assume that the problem is due to the namespace, but it's not bug 52609, because the template itself adds correctly to the page:  \\n\\n{{User:Jay8g/sandbox/Template:Airline fleet table/Start}}\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405559011, 'spacePHID': None, 'dateCreated': 1404322800, 'dateModified': 1417572025, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67424', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid shouldn't convert external links to interwiki links when the interwiki prefix matches a local namespace name\", 'description': {'raw': \"This may be related to bug 42986:  VisualEditor and Parsoid autoconvert URLs in the external link format to local links, including for interlanguage and other interwiki links.\\n\\nThis means that if you paste https://outreach.wikimedia.org/wiki/Example in as your link on one of the Wikipedias, it gets saved as [[outreach:Example]].  \\n\\nThis is fabulous and should be kept. \\n\\nHowever, if the local wiki doesn't recognize the converted prefix for the link, then the result is a redlink.  At the moment, office.wiki doesn't know about the existence of outreach.wiki, but links are converted anyway.  \\n\\nThe result is that pasting https://outreach.wikimedia.org/wiki/Example as a link on office.wiki gets saved as [[outreach:Example]], and when you click on the resulting redlink, it takes you to the non-existent page https://office.wikimedia.org/wiki/Outreach:Example  \\n\\nThis is not so fabulous.  \\n\\nThe most flexible system is to find out which wikis are known locally, and only convert those.  The most immediate solution is probably to tell office.wiki where to find outreach.wiki.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1404235020, 'dateModified': 1583514742, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67373', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Prompt for edit summary preference breaks the save dialog', 'description': {'raw': 'If a user has the preference \"Prompt me when entering a blank edit summary\" selected, VisualEditor\\'s save dialog has to be closed and reopened to work. The \"Save\" button is greyed out even when an edit summary is entered.\\n\\nTo reproduce:\\n1. Enable Preferences>Editing>tick Prompt me when entering a blank edit summary\\n2. Attempt to save a VE edit and the prompt for an edit summary comes up, with save not an option\\n3. Enter an edit summary\\n4. Save is still not an option\\n5. Exit out of the dialog by clicking X and click save again\\n6. You can now save your edit with an edit summary\\n\\nFirefox 30 on Mac OS X Mavericks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fwlidikyeorzj35hufwu', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404232062, 'spacePHID': None, 'dateCreated': 1404185940, 'dateModified': 1443278105, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67345', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'MediaWiki:Visualeditor-wikitext-warning-link should link mediawiki.org', 'description': {'raw': \"On translatewiki.net I see a red link in messages and this page won't exist on most wikis, just link https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Formatting by default. See blocked bug for example and remember, Brion veto'ed the simple solution i.e. interwiki link [[mediawikiwiki:Special:MyLanguage/Help:Formatting]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416971385, 'spacePHID': None, 'dateCreated': 1404044760, 'dateModified': 1438735490, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67273', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor Mobile: Chrome for mobile keyboard doesn't fire useful key events for backspace\", 'description': {'raw': \"Key events fire without key codes (understandable as you can 'swipe' whole words) and backspace fires no key[up|down|press] event at all.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1403994660, 'dateModified': 1539445981, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67262', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Keyboard shortcut to access VE (Alt+Shift+v) is not working from action=edit in FF browser', 'description': {'raw': 'Setup- FF 30.0. \\nSteps to Reproduce-\\n1>Launch the FF browser.  And go to your user page in Beta labs.\\n2>Click on “Edit Source” tab.  Click anywhere on the Wikitext Editor pane.\\n3>Now while the cursor is still blinking in the editor pane, press the keyboard shortcut for the VE editor tab which is “Alt+Shift+v”.  \\n\\nActual Result-When the keyboard shortcut for the VE editor tab i,e. “Alt+Shift+v” is pressed, it just scrolls the window down, while the Wikitext Editor pane is still open and instead the “Show Changes” button gets highlighted(which apparently has the same keyboard shortcut combination).  The same behavior was observed in test2 environment for FF browser. But in Safari and Chrome no such similar behavior was found.\\n\\nExpected Result-When pressed the keyboard shortcut of “Alt+Shift+v” should access the Edit beta tab and open the VE pane.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**: {T54701}'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1464631574, 'spacePHID': None, 'dateCreated': 1403905980, 'dateModified': 1464643075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67218', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting a block item highlights the previous line', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE which contains a block item like reflist or image\\n2.Delete the image\\n\\nObserved Result:\\nA highlight appears from the end of the previous line covering up the rest of the line.\\n\\nInstead of highlighting, upon deleting the block item the cursor should just appear at the end of the previous line.\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14275}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403990886, 'spacePHID': None, 'dateCreated': 1403901720, 'dateModified': 1443278110, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67213', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Block items converted to inline initially show a flash of highlight trying to select the previous line, and then the selection normalises to just the item', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Make it Frameless-Left or Basic-Left\\n4.Now uncheck the wrapping option.\\n\\n\\nObserved Result:\\nThe previous line gets highlighted for a split second then the highlight goes away.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701963876, 'spacePHID': None, 'dateCreated': 1403901180, 'dateModified': 1701963876, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67212', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Text-only GeneratedContentNode rerenderings aren't highlighted correctly\", 'description': {'raw': '1. Create a page with {{echo|foo}} in the text somewhere\\n2. Observe that the word \"foo\" is highlighted and clickable and all those good things\\n3. Inspect \"foo\", and change the parameter to \"bar\"\\n4. Click the rerendering\\n\\nNote that there is no highlight, you\\'re able to select parts of the word (!), it\\'s not inspectable, etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404172141, 'spacePHID': None, 'dateCreated': 1403824740, 'dateModified': 1443278115, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67169', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor should support redirects to sections on a page', 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Go to Page settings and tick the box to make a redirect.\\n\\n2.  Type in not just a page title, but also a section:  Example#Foo\\n\\n3.  Now what?  If I click \"Example\" in the list, it deletes the #Foo part.\\n\\n\\nIt turns out that if you click outside the page settings dialog, that it actually will accept this, but it looks impossible.\\n\\nThen when you \"apply changes\", the redirect isn\\'t visible on the page (T63861) so you can\\'t tell whether it worked or did anything at all.'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1490714782, 'spacePHID': None, 'dateCreated': 1403805420, 'dateModified': 1490715828, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67147', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Broken Kloutify browser extension injects garbage into the page', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Lobstick&curid=43120379&diff=614082884&oldid=614013920\\n\\nThe user edited the page twice, resulting in two copies of this:\\n\\n<div id=\"kloutify\"><div></div><div id=\"kloutify-score\">10</div></div>\\n\\nat the top of the page.  The \"10\" is visible on the page.\\n\\nhttp://kloutify.com/ says that this can be installed on Firefox, Chrome, and Safari.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412114615, 'spacePHID': None, 'dateCreated': 1403562600, 'dateModified': 1417571699, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67006', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Offer ability to save without exiting (for saving your work in the middle of an editing session)', 'description': {'raw': 'Opening VisualEditor can be slow for some pages/some users.  Please offer the option of saving without exiting.\\n\\n(Original suggestion:  https://en.wikipedia.org/w/index.php?diff=613298543&oldid=613210959)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1403195460, 'dateModified': 1643973188, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66847', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Tapping on Return while cursor is at the end of a text, deletes that text in Nexus 7 (Android 4.4.2)', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with Mobile VE\\n2.Type a text \\n3.Tap on the \"Return\" key from the keyboard\\n\\nObserved Result:\\nInstead of adding a newline and moving the cursor to it, it deletes the preceding text.\\n\\nDevice:Nexus 7(Android 4.4.2)\\nEnvironment:Production (en.wiki) and Betalabs'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1403049840, 'dateModified': 1604088026, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66758', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Cannot save any edit in mobile VE for Nexus 7(Android 4.4.2)', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open any page with Mobile VE in Nexus 7(Android 4.4.2)\\n2.Type a text\\n3.Save the page\\n\\nObserved Result:\\nThe edit does not get saved\\n\\nDevice:Nexus 7(Android 4.4.2)\\nEnvironment: Production (en.wiki) and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'dateClosed': 1430339892, 'spacePHID': None, 'dateCreated': 1403047800, 'dateModified': 1430349752, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66756', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Tapping at the end of each link, does copy-paste of preceding link text in Nexus 7(Android 4.4.2)', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with mobile VE\\n2.Tap at the end of a link\\n\\nObserved Result:\\nThe link gets copied at the position your cursor was on and it will keep continue doing that everytime you place your cursor at the end of extended link.\\n\\nSee the screenshot attached\\n\\nDevice: Nexus 7(Android 4.4.2)\\nEnvironment:Production (en.wiki) and Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-v7iovheqigasai3pzdax', 'dateClosed': 1552401954, 'spacePHID': None, 'dateCreated': 1403047020, 'dateModified': 1552401954, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66755', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Make it possible to distinguish Wikitext headings and HTML headings', 'description': {'raw': 'Right now the HTML created for\\n- headings specified using Wikitext (e.g. \"==\")\\n- headings created using HTML tags (e.g. \"<h2>\")\\nlook basically the same.\\n\\n- Both have a wrapping heading element (without class or id)\\n- Both contain a <span> of class \"mw-headline\"\\n\\nThe only (but major) difference is that sections created by Wikitext are editable and therefore contain an additional <span> of class \"mw-editsection\".\\n\\nIt would be nice if there was an easy possibility to directly differentiate those types of headers on a CSS level (e.g. by an additional class applied to the parent <h*> element)\\n\\n\\nThis would make it much easier to create custom CSS and JS since often one would only want to style \"true\" (that is editable) article headers created by Wikitext instead of custom created headers that are mostly used for design of e.g. project pages.\\nRight now such CSS and JS often erroneously styles all headers the same, regardless of how the headers were created, often resulting in unintentional appearance.\\n\\n--------------------------\\n**Version**: 1.24rc\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-v3yn5qf233ggnnnmvejc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1402834020, 'dateModified': 1735855955, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66637', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Spaces at the start of a paragraph aren't very obvious\", 'description': {'raw': \"It is possible (if inadvisable) to have whitespace at the start of a paragraph in HTML; to readers it is mostly invisible. In MediaWiki, because whitespace at the start of a paragraph has magic meaning, Parsoid `<nowiki />`s it. To avoid users doing this accidentally, it might be nice to design a way to flag to the user what they've done when they create these.\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1434389039, 'spacePHID': None, 'dateCreated': 1402788000, 'dateModified': 1434474897, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66628', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Reconsider list functions' application and clearing\", 'description': {'raw': 'Highlighting entire paragraphs and applying or removing list formatting should consistently apply or remove formatting, currently some items are ignored.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=42115'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1655735445, 'spacePHID': None, 'dateCreated': 1402434120, 'dateModified': 1655735445, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Use rspec-expectations \"expect\" syntax instead of \"should\" syntax', 'description': {'raw': \"For list of repositories see https://www.mediawiki.org/wiki/Repositories_with_Ruby_code\\n\\nFor more information see https://www.mediawiki.org/wiki/Manual:Coding_conventions/Selenium#expect_or_should\\n\\nStill not implemented in:\\n\\n- mediawiki/extensions/ArticleFeedbackv5\\n- mediawiki/extensions/CirrusSearch\\n- mediawiki/extensions/ContentTranslation\\n- mediawiki/extensions/Flow\\n- mediawiki/extensions/Gather\\n- mediawiki/extensions/MultimediaViewer\\n- mediawiki/extensions/PdfHandler\\n- mediawiki/extensions/Translate\\n- mediawiki/extensions/TwnMainPage\\n- mediawiki/extensions/UniversalLanguageSelector\\n- mediawiki/extensions/UploadWizard\\n\\n```\\n$ grep --include *.rb  -R -F '.should' .\\n\\nmediawiki/vagrant/mediawiki/extensions/ArticleFeedbackv5/tests/browser/features/step_definitions/aftv5_steps.rb:    page.yes_element.when_present.should be_visible\\n...\\nmediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/page_steps.rb:    result.status.should eq 200\\n...\\nmediawiki/vagrant/mediawiki/extensions/ContentTranslation/tests/browser/features/step_definitions/basic_mt_steps.rb:  on(ContentTranslationPage).translation_editor_element.text.should == text\\n...\\nmediawiki/vagrant/mediawiki/extensions/Flow/tests/browser/features/step_definitions/description_steps.rb:    page.description.content.should eq(content)\\n...\\nmediawiki/vagrant/mediawiki/extensions/Gather/tests/browser/features/step_definitions/recent_collections_steps.rb:  on(GatherRecentPage).collection_one_hundred_element.should exist\\n...\\nmediawiki/vagrant/mediawiki/extensions/MultimediaViewer/tests/browser/features/step_definitions/mmv_options_steps.rb:  on(E2ETestPage).mmv_options_menu_disable_element.should be_visible\\n...\\nmediawiki/vagrant/mediawiki/extensions/PdfHandler/tests/browser/features/step_definitions/pdf_steps.rb:  on(PdfPage).download_as_pdf_element.should exist\\n...\\nmediawiki/vagrant/mediawiki/extensions/Translate/tests/browser/features/step_definitions/manage_translator_sandbox_steps.rb:\\ton(UserPage).babel_box_has_languages?(languages).should be_true\\n...\\nmediawiki/vagrant/mediawiki/extensions/TwnMainPage/tests/browser/features/step_definitions/signed_in_and_approved_user_steps.rb:\\t\\tpage.number_of_translators_element.should be_visible\\n...\\nmediawiki/vagrant/mediawiki/extensions/UniversalLanguageSelector/tests/browser/features/step_definitions/accept_language_steps.rb:  on(MainPage).main_page_element.text.should == text\\n...\\nmediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/chunked_upload_steps.rb:  on(UploadPage).continue_element.when_present(300).should be_visible\\n...\\n```\\n\\n\"}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'dateClosed': 1495811105, 'spacePHID': None, 'dateCreated': 1402321140, 'dateModified': 1495811105, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66369', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Come up with a sane way of including screenshots with skins and displaying them in the UI', 'description': {'raw': 'We should have a sane way of including screenshots with skins and displaying them in the UI. These would be useful on Special:Preferences, in the installer when it will ask you which skin to choose, on Special:Version…\\n\\nI coded up something that works but is probably not a good idea at https://gerrit.wikimedia.org/r/#/c/138110/ – this would just add support for a new key to $wgExtensionCredits.\\n\\nOne interesting issue is, what resolution should we expect the screenshot to be?\\n\\nAnother one is, how do we display it? Unless we want to push the whole thing through ResourceLoader CSS handling (which would be extremely silly), we need to know the URL path where the screenshot is available (relative to $wgStylePath?). This is not obvious :(\\n\\n**See Also**: {T70331}\\n\\n----\\n\\n**The new convention**:\\n* Every skin can include screenshots in the screenshots/ directory, which will be shown in the installer (and possibly elsewhere in the future).\\n* It should include at least one 1280x800px screenshot, plus any extra screenshots if your skin looks different at different screen resolutions or with different configuration options.\\n* You should disable any extensions or uncommon configuration options when taking the screenshots.\\n* Make sure not to include any copyrighted content in the screenshots – here\\'s some public domain content you can use:\\n** Page content: P5878\\n** Site logo: the MediaWiki logo (`$wgLogo = \"/w/resources/assets/mediawiki.png\";`)\\n** Images: [[https://commons.wikimedia.org/wiki/File:Turner,_J._M._W._-_The_Fighting_Téméraire_tugged_to_her_last_Berth_to_be_broken_(edit).jpg|1]] [[https://commons.wikimedia.org/wiki/File:Bierstadt_Albert_Indian_Summer_Hudson_River.jpg|2]] [[https://commons.wikimedia.org/wiki/File:Meisje_met_de_parel.jpg|3]]\\n**Examples**:\\n{F9028486,float} {F9028461,float} {F9028439,float}\\n\\n----'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1502484615, 'spacePHID': None, 'dateCreated': 1402099020, 'dateModified': 1512230552, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66295', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Citation dialog changes title after opening', 'description': {'raw': '1. Click Cite -> Newspaper\\n2. A dialog opens; while it\\'s opening, the title is \"Newspaper\"\\n3. Once it finishes opening, the title changes to \"Cite news\"\\n\\nThis is more visible on a slower system or with an artificially lengthened opening animation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1401752160, 'dateModified': 1416845535, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66059', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When the toolbar is disabled, clicking an image on the page does not select it', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Click somewhere outside the page where the VE toolbar will get disabled\\n4.Now click on the image.\\n\\nObserved Result:\\nClicking on the image tries to select the image first then cursor moves to the beginning of the document.\\n\\nEnvironment :Betalabs\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401391111, 'spacePHID': None, 'dateCreated': 1401300060, 'dateModified': 1417572220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65866', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Undo/redo should not (?) remain active when surface is blurred', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to the Media Settings dialog of the image\\n4.Type something in the caption field\\n5.Now place the cursor in the Alternative Test field\\n6.Observe that, the \"Undo\" button in the toolbar is still active\\n7.Click on the undo button\\n\\nObserved Result:\\nIt clears the text inside the caption field , this is a bit confusing , since the cursor was pointing to text inside Alternative Text and but it started clearing out the content inside caption field.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1505244676, 'spacePHID': None, 'dateCreated': 1400887980, 'dateModified': 1505244676, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65713', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Dialogs initially don't work in Safari 5.x (but do with 6.x+?)\", 'description': {'raw': \"**Author:** `wiki.nihiltres`\\n\\n**Description:**\\nI noticed today that dialogs are delayed or fail to work some of the time in VE, using Safari 5.1.10 on Mac OS 10.6.8. The first click on a button that produces a dialog, or first few clicks, don't seem to do anything, but clicking on the button a while later has the normal effect, suggesting something's taking a while to load.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**OS**: Mac OS X 10.6\\n**Platform**: Macintosh\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1583082370, 'spacePHID': None, 'dateCreated': 1400793900, 'dateModified': 1583082371, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65656', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Coordinates template is displaying in the wrong place', 'description': {'raw': 'Steps to reproduce:\\n\\n1.  Open any page that contains the {{coord}} template on en.wp  See, e.g., https://en.wikipedia.org/wiki/Harton,_North_Yorkshire \\n\\n\\nResults:\\n\\nThe coordinates template, which should be in the top right corner, displays in the far left—so far to the left that only the last few characters are visible.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400782860, 'dateModified': 1604263405, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65648', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support editing {{int:name}} blocks', 'description': {'raw': 'This is related to T52855 about parser functions and magic words.\\n\\nWhen I have a sentence on a page like this:\\n\\n   Choose the \"{{int:visualeditor-dialogbutton-reference-tooltip}}\" item in the \"{{int:visualeditor-toolbar-insert}}\" menu. \\n\\nI want to be able to:\\n\\n(1) copy and paste; \\n(2) edit; and\\n(3) create\\n\\nthe {{int:foo}} parts.  \\n\\nRight now, I can only copy them for re-use elsewhere on the page if I select a bigger block of text (so \"{{int:visualeditor-toolbar-insert}}\", but not just {{int:visualeditor-toolbar-insert}}).\\n\\nI can\\'t edit them at all; it\\'s an uneditable alienated text block.  Given the long strings of similar names for some of these items, it would be really handy to be able to copy and paste something like {{int:visualeditor-toolbar-insert}} and only need to change the \"insert\" bit to \"cite-label\", or to fix a typo in the name.\\n\\nIt would also be nice to have a sensible system for creating these things.  At the moment, it can only be done through this sequence:  Insert > Template, \"Other options\", Content, type in the wikitext, and Insert transclusion. \\n\\nHowever, my main concern is just being able to edit existing ones.'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437690685, 'spacePHID': None, 'dateCreated': 1400780640, 'dateModified': 1439331301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65644', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Move the reference, reference list and citation systems into the Cite extension's repo\", 'description': {'raw': 'I spent a lot of time wondering why my citations were not rendering properly.\\n\\nVisualEditor shows a cite menu which behaves strangely if the Cite extension not enabled.\\n\\nShould this throw an error or not show the citation tool when the Cite extension is not installed?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1432051337, 'spacePHID': None, 'dateCreated': 1400766240, 'dateModified': 1461271157, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65630', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Serializing images without data-parsoid normalizes image names incorrectly', 'description': {'raw': 'If you parse wikitext like `[[File:Ulmer M?nster-1024409.jpeg|frame]]` , Parsoid will produce a <figure> structure with href=\"./File:Ulmer_M%3Fnster-1024409.jpeg\" (which is correct, the question mark is urlencoded) and resource=\"./File:Ulmer_M%3Fnster-1024409.jpeg\" (not sure whether this is correct).\\n\\nWhen VisualEditor takes this information to build an inline image equivalent (taking the href and the resource, and dropping everything else including data-parsoid) we get [[File:Ulmer_M%3Fnster-1024409.jpeg|link=]] back. Note the space changed to an underscore and ? changed to %3F. There was information in data-parsoid to keep this from happening, but in this transformation VE discards it.\\n\\n```\\n$ echo \\'[[File:Ulmer M?nster-1024409.jpeg|frame]]\\' | node tests/parse.js --apiURL=http://localhost/w/api.php\\n<!DOCTYPE html>\\n<html prefix=\"dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/\"><head prefix=\"mwr: http://localhost/wiki/Special:Redirect/\"><meta property=\"mw:parsoidVersion\" content=\"0\"/><link rel=\"dc:isVersionOf\" href=\"//localhost/wiki/Main_Page\"/><title></title><base href=\"//localhost/wiki/Main_Page\"/></head><body data-parsoid=\\'{\"dsr\":[0,42,0,0]}\\'><figure class=\"mw-default-size\" typeof=\"mw:Image/Frame\" data-parsoid=\\'{\"optList\":[{\"ck\":\"framed\",\"ak\":\"frame\"}],\"dsr\":[0,41,2,2]}\\'><a href=\"./File:Ulmer_M%3Fnster-1024409.jpeg\" data-parsoid=\\'{\"a\":{\"href\":\"./File:Ulmer_M%3Fnster-1024409.jpeg\"},\"sa\":{},\"dsr\":[2,39,null,null]}\\'><img resource=\"./File:Ulmer_M%3Fnster-1024409.jpeg\" src=\"//localhost/w/images/f/f1/Ulmer_M%3Fnster-1024409.jpeg\" height=\"1024\" width=\"764\" data-parsoid=\\'{\"a\":{\"resource\":\"./File:Ulmer_M%3Fnster-1024409.jpeg\",\"height\":\"1024\",\"width\":\"764\"},\"sa\":{\"resource\":\"File:Ulmer M?nster-1024409.jpeg\"}}\\'/></a></figure>\\n</body></html>\\n\\n$ echo \\'<p><span typeof=\"mw:Image\" class=\"mw-default-size\"><span><img src=\"//localhost/w/images/f/f1/Ulmer_M%3Fnster-1024409.jpeg\" resource=\"./File:Ulmer_M%3Fnster-1024409.jpeg\" width=\"764\" height=\"1024\"></span></span></p>\\' | node tests/parse.js --html2wt\\n[[File:Ulmer_M%3Fnster-1024409.jpeg|link=]]\\n```\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400706840, 'dateModified': 1620150607, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65603', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'iOS: Shake to undo on mobile does not undo or redo typing', 'description': {'raw': '1. go to article on en.m.wiki\\n2. invoke WTE type characters\\n3. shake phone, [undo/cancel] dialog is displayed\\n4. choose undo\\n\\nexpected : typed characters should be removed\\nactual : typing is not undone\\n\\n5. once undo works, shaking phone again should trigger [redo/cancel] which should restore undone action.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'dateClosed': 1418251044, 'spacePHID': None, 'dateCreated': 1400704140, 'dateModified': 1438734933, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65600', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: Allow formatting editing', 'description': {'raw': \"It's impossible to create a new page / new content without this. :-(\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400686140, 'dateModified': 1535401005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65586', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Automatically convert inserted URLs to readable formatted links', 'description': {'raw': \"Quora has a lovely feature in its visual editor: paste a URL and it's immediately and automatically converted in a smart way.\\n\\n* If it's a link to another answer on Quora, it is given an appropriate title.\\n* If it's a link to YouTube, the video is embedded.\\n* If it's a link to some other website, the page's HTML <title> is inserted and automatically linked. (There may be other special cases, but you get the idea.)\\n\\nAfter the link is thus inserted, the user can edit the text or click another button to make the actual URL appear or to make the URL just plain text.\\n\\nI'd love such a feature in VE. It's especially relevant for newbies who link to other Wikipedia articles with full http links as if they were external. For external links, getting the title automatically is usually better than having a plain URL (in fact, there are some bots that automatically insert such titles). And pasting a Commons URL can embed the media as such.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1444743744, 'spacePHID': None, 'dateCreated': 1400608680, 'dateModified': 1451081071, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65540', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Font is too small in dialogs in standalone VE', 'description': {'raw': 'Compare the keyboard shortcut help dialog (Ctrl+/) in the standalone demo vs the MW integration. The one in standalone has a smaller font size.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405375966, 'spacePHID': None, 'dateCreated': 1400109240, 'dateModified': 1443278174, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65322', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'BetaFeatures: Provide an anchor link for each beta feature', 'description': {'raw': 'Add anchor links to each feature so that a user could send someone directly to a feature. For example, https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures#VisualEditor\\n'}, 'authorPHID': 'PHID-USER-flenunkasbjk4topxvaj', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400101980, 'dateModified': 1485555487, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65315', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor Mobile: The Link inspector icon remains highlighted in the toolbar for mobile VE even if no new link has been added', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a blank page with mobile VE\\n2.Click on the link inspector icon\\n3.Without adding any text just close the inspector\\n\\nObserved Result:\\nThe link inspector icon in the toolbar remains highlighted where as there is no link added in the CE\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13539}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429559528, 'spacePHID': None, 'dateCreated': 1400097300, 'dateModified': 1429635530, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65305', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"The page has been restored\" appearing on top of the page instead of \"your edit was saved\" after switching to edit source mode and saving the page from there', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Edit something\\n3.Switch to edit source mode\\n4.Save the page from edit source mode\\n\\nObserved Result:\\nThe message  \"The page has been restored\" appearing on top of the page instead of \\n\"your edit was saved\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F14068}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400103339, 'spacePHID': None, 'dateCreated': 1400002440, 'dateModified': 1443278177, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65269', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'jquery.client should support detecting Firefox Mobile', 'description': {'raw': 'A \"Request desktop site\" option exists in Chrome and Firefox on Android, and maybe in some other browsers too.\\n\\nI believe what that option affects is just a user-agent string, and does not change other behaviors of the browser. However (for example in Firefox), with \"Request desktop site\" on, VisualEditor works happily, while with that option off, VisualEditor refuses to load.\\n\\nWe should check whether VE actually works in these browsers, and have it whitelisted or blacklisted, regardless of whether that option is on or off.\\n\\n--------------------------\\n**Version**: 1.24rc\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1599505179, 'spacePHID': None, 'dateCreated': 1399982340, 'dateModified': 1599660276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65255', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Clearing float from a template like {{-}} doesn't work\", 'description': {'raw': 'In the linked article, the content is not cleared after floats of the tables when using the template {{-}} which transcludes as:\\n<br style=\"clear:both;\">\\n\\nThis is caused by the inline-block behavior of .ve-ce-mwTransclusionInlineNode\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/w/index.php?title=List_of_top_100_Major_League_Baseball_strikeout_pitchers&oldid=608135239\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57372'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427402228, 'spacePHID': None, 'dateCreated': 1399971600, 'dateModified': 1438734933, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65249', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Browser greylist notice alert not shown the second time you edit a page in the same JS session', 'description': {'raw': 'The \"notices\" thing (exclamation mark in a triangle) disappears from VE toolbar if you open a page for editing, close VE, then open it again (on the same page).\\n\\nTo reproduce:\\n1. Click \"Edit\" (or \"Edit beta\") on any page to open VisualEditor\\n2. Click \"Cancel\" to close it\\n3. Click \"Edit\" again\\n\\nThe toolbar will no longer have the \"notices\" item.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400190463, 'spacePHID': None, 'dateCreated': 1399921320, 'dateModified': 1443278177, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65236', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: References as part of a file description are misnumbered', 'description': {'raw': 'In https://en.wikipedia.org/w/index.php?title=Female_promiscuity&oldid=607751101 references [74], [75] and [76] show up as 1, 2 and 3 in VE in the references box, with the rest of the reference numbers \"pushed down\", but with their original numbering in the main VE editing interface.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-n27daagbl3wqf3ghr4nk', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1688060841, 'spacePHID': None, 'dateCreated': 1399921200, 'dateModified': 1688060841, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65235', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: (Possibly) Yet Another Broken Browser Plugin injecting mess into edits (Google Maps?)', 'description': {'raw': 'See link provided above.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=Anaconda,_Montana&diff=prev&oldid=608235426'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1407403982, 'spacePHID': None, 'dateCreated': 1399915320, 'dateModified': 1417571946, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65227', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Support for Parsoid-based extracts', 'description': {'raw': \"This is important since the extracts are currently generated with the old API which doesn't guarantee valid xhtml5. That prevents third-party developers using less forgiving markup environments from fetching the extracts to build tools on top of them, e.g. https://github.com/waldyrious/primerpedia/issues/20\\n\\nI'd work on this myself but I really don't have the background to understand the code in ApiQueryExtracts.php on my own (even after taking a look at VisualEditor's ApiVisualEditor.php to check an example implementation of a request to Parsoid, as suggested by Mark Traceur).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uazrhtptdqudzoqfefsc', 'ownerPHID': 'PHID-USER-uazrhtptdqudzoqfefsc', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'dateClosed': 1493660641, 'spacePHID': None, 'dateCreated': 1399764120, 'dateModified': 1493660695, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65169', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Set up dev.wikimedia.org portal', 'description': {'raw': 'There\\'s a few (not too many!) things that need a home, and I think this is a good time to start work on what will become the main entry point for developers to learn about Wikimedia (wiki) projects and Wikimedia (software) products.\\n\\ndeveloper.wikimedia.org\\n\\nThe initial portal wouldn\\'t be unlike some of these:\\n* https://developers.google.com/\\n* https://developers.facebook.com/\\n* https://dev.twitter.com/\\n\\nHere\\'s are some very specific use cases that have come up during the Zurich Hackathon that I think would be best served with this:\\n\\n- Where do I find out about the existence of:\\n  * gdash.wikimedia.org\\n  * graphite.wikimedia.org\\n  * noc.wikimedia.org\\n  * doc.wikimedia.org\\n  * git.wikimedia.org\\n  * wikitech.wikimedia.org\\n  * irc.wikimedia.org\\n  ( * stream.wikimedia.org/rc )\\n\\n  Current solution: None\\n\\n  Current workaround for regulars:\\n    https://wikitech.wikimedia.org/wiki/Category:Services\\n\\n- Where would I find out about xml dumps?\\n\\n  Current solution: None\\n\\n  Current workaround for regulars:\\n    http://dumps.wikimedia.org/backup-index.html\\n\\n- Where would I find out about pageview count data?\\n\\n  Current solution: None\\n\\n  Current workaround for regulars:\\n    http://dumps.wikimedia.org/\\n      http://dumps.wikimedia.org/other/\\n        http://dumps.wikimedia.org/other/pagecounts-raw/\\n\\nI\\'m sure the people from the \"Data API & Hub\" table from Zurich Hackathon 2014 have more specific stories and use cases. \\n\\nThis hub would act as delegate for the following cases (pointing to things on another domain or the same, some of which should probably move to it eventually):\\n\\n* Products\\n  Such as:\\n\\n  - MediaWiki\\n    -> Homepage\\n    -> Source code (git repo)\\n    -> Documentation (separate portal, on mediawiki.org for now, ultimately linking back to developer.wikimedia.org/mediawiki/{js,php,api} for documentation of individual classes and apis.\\n        We already have JS and PHP docs autogenerated for MediaWiki.\\n        Docs the API are still hardcoded on mediawiki.org and api.php/help\\n        exclusively, we should get API and Hooks documentation onto\\n        doc.wikimedia.org as well.\\n        See https://www.mediawiki.org/wiki/Requests_for_comment/Documentation_overhaul\\n\\n  - VisualEditor\\n    -> Source code\\n    -> Demo(s)\\n    -> Documentation\\n\\n* Data and APIs\\n  (APIs that are not related to MediaWiki or individual user-facing products, but Wikimedia services in general, MediaWiki\\'s API is one small part of that)\\n\\n  Such as:\\n\\n  * page view counts\\n  * xml dumps\\n  * OAuth?\\n  * irc.wikimedia.org\\n  ( * stream.wikimedia.org/rc )\\n  * \"See also: Wikidata\"\\n\\n* Communications\\n  - (e.g. link to tech blog, as currently linked from noc.wikimedia.org)\\n  - mailing lists\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=29936'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1597919448, 'spacePHID': None, 'dateCreated': 1399646220, 'dateModified': 1626968551, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65074', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  If you insert a gallery into a list, the list formatting remains visible but is removed in wikitext', 'description': {'raw': 'Intention:\\nAdd an image gallery at the top of a section.\\n\\nSteps to Reproduce:\\n1. Open a page that has a list at the top of the section.  \\n\\n2. Place your cursor at the top of the list, and Insert > Gallery.\\n\\n\\nActual Results:  \\nThe bullet remains visible.  The text of the list item is on the next line, but indented.\\n\\nHowever, when you save, the list formatting (the asterisk at the start of the line) has been removed.\\n\\nExpected Results:  \\nThe gallery would be inserted before the list.  That is,\\n\\n* List item\\n\\nwould turn into \\n```\\n<gallery>File:Example.jpg\\nFile:Example2.jpg</gallery>\\n\\n* List item\\n```\\ninstead of into\\n\\n```\\n <gallery>File:Example.jpg\\nFile:Example2.jpg</gallery>List item\\n```\\n(Notice the stray space at the start of the line.)\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: http://en.wikipedia.beta.wmflabs.org/w/index.php?diff=92775&oldid=92716'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1399497480, 'dateModified': 1712844845, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65022', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide an omnibar for quick keyboard access to tools', 'description': {'raw': \"From MediaWiki.org:\\n\\n> I would like to have an omnibar in VE. This is a single text field where\\n> a user can search for things they want to do, instead of clicking a\\n> button you can invoke omnibar with a keyboard shortcut and then search\\n> for the task you want to do. This would be helpful to easier access those\\n> buttons which don't have shortcuts now. Like managing category, inserting\\n> reference, changing to source editor etc.\\n\\nSeems like it could be a lot of work to implement – for example, internationalisation of such controls might be hard – but it might be particularly useful for power users (or for controls that don't have a keyboard shortcut, as the proposer notes).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-hdkktg27rkwebepkv6yw', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1688774052, 'spacePHID': None, 'dateCreated': 1399309080, 'dateModified': 1689964277, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64905', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tool to set/unset text as highlighted (<mark>)', 'description': {'raw': 'I want to use the HTML code <mark> in the newsletter and still be able to edit the draft page in VisualEditor.  Right now, adding <mark> produces nowiki tags, and opening a page with <mark> already on it prevents editing the marked text (alienated content).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1398362520, 'dateModified': 1643973192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64376', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make MW toolbar integrate into the new \"floating toolbar\" beta feature when enabled', 'description': {'raw': \"Right now it's a horrible mess. :-(\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1493662390, 'spacePHID': None, 'dateCreated': 1398113460, 'dateModified': 1493662390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64203', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: VE-core, OOjs and OOjs-UI update scripts share commonalities but don't share code\", 'description': {'raw': 'We should merge them together where appropriate.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1397873640, 'dateModified': 1643973193, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64121', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The bullet point does not show up in CE when it contains an image with a block slug', 'description': {'raw': 'Read mode\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Add a bullet list\\n3.Add an image as a bullet point \\n4.Save the page\\n5.Reopen the page \\n\\n\\nObserved Result:\\nThe bullet point appears on the read mode but not inside VE, but when you type something in that position the bullet point appears again.\\n\\nSee the screenshot attached\\n\\nPage:\\nhttp://en.wikipedia.beta.wmflabs.org/wiki/After_switch\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13837}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398110669, 'spacePHID': None, 'dateCreated': 1397863440, 'dateModified': 1443276212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64117', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Broken appearance when window is too small in Internet Explorer', 'description': {'raw': 'just ugh\\n\\nSee attached screenshot.  Green Highlight is the cursor bar -- showing the cursor and the top of the page is somehow ending up under the heading instead of just below it.  Red hightlight is the outline of the (not showing) warning about using an unsupported browser.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13658}'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409957935, 'spacePHID': None, 'dateCreated': 1397146020, 'dateModified': 1423674433, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63778', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Keyboard shortcuts help page should use kbd elements', 'description': {'raw': 'This page should be using the html5 element <kbd> to represent the keyboard keys.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397239182, 'spacePHID': None, 'dateCreated': 1397136240, 'dateModified': 1443276228, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63767', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide easy, backend way for extensions to show PostEdit notifications with custom content', 'description': {'raw': \"I've recently been working on an extension, and it would be nice for it to show a PostEdit success box when it successfully completes an operation. However, doing this at the moment would mean loading a Javascript file, the PHP setting a JS config var for whether to display the PostEdit box or not, JS checking this variable, JS getting a message for the text to display, etc.\\n\\nWhat would really be useful would be a way, just in PHP, for extensions to specify that a PostEdit box should be shown, with the text to display. The code would then ensure that JS to show the box is loaded on the page (which would possibly also save resources over the above method).\\n\\nI am not entirely sure how this would be best implemented, but possibly something like wfShowPostEdit( $text ), that could be easily called in an extension's code. Something like this would make it many more times easier for extensions to show PostEdit boxes.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-xpto4uqv737bawfiy53m', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1457647347, 'spacePHID': None, 'dateCreated': 1397069820, 'dateModified': 1474749964, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63740', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Design of the section 0 edit icon (often the sole initially visible one) looks like it applies to entire article, and there's no article button\", 'description': {'raw': 'On every page there is an icon of a pencil.\\n\\nIt is linked to #editor/0.\\n\\nI.e. there is no way to edit any other section than section 0.\\n\\nMaybe it was assumed that /0 meant the whole page.\\n\\nAnyway one must manually change the url to /1, /2 etc.'}, 'authorPHID': 'PHID-USER-awbqewknju4hbrnah6pm', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-pzp7mdlx7otgdlggnyhh', 'dateClosed': 1581836576, 'spacePHID': None, 'dateCreated': 1396838700, 'dateModified': 1581836576, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63604', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switch action=opensearch calls to list=prefixsearch where appropriate', 'description': {'raw': \"Gerrit af6d9ab introduced list=prefixsearch which can be used as a generator, which action=opensearch can't be. This would allows us to avoid taking the output of opensearch and turning around to make follow-up API requests for e.g. pageprops to see if they are redirects or whatever.\\n\\nWe shouldn't do this switch until MW1.23 is released, at least, however.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401324104, 'spacePHID': None, 'dateCreated': 1396659720, 'dateModified': 1443278193, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63555', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add Vietnamese (vi) input method', 'description': {'raw': \"(In reply to Minh Nguyễn from bug 5309 comment #45)\\n> many Vietnamese Wikipedia users rely on an IME script embedded via\\n> a gadget, but gadgets are disabled at [[Special:UserLogin/signup]]. We’d\\n> need to port the (rather complex) IME to ULS to keep the signup form\\n> accessible.\\n\\nWe definitely should! It shouldn't be hard, jquery.ime only needs a comma separated list of input keys -> result character pairs.\\nhttps://github.com/wikimedia/jquery.ime/wiki/Technical-Specification#input-method-definition\\nIf you can't prepare such a table, can you ask other vietnamese users?\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement\\n**See Also**:\\nhttps://github.com/wikimedia/jquery.ime/issues/342\"}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1396517460, 'dateModified': 1723267643, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63465', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs: Should be parseable by ES3 engines', 'description': {'raw': 'targetFn.super = originFn;\\n\\ntriggers a JS error in IE 8, and presumably in older versions of IE as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-papbtlagfolot4dzerne', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403118870, 'spacePHID': None, 'dateCreated': 1396274940, 'dateModified': 1597413034, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63303', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Yet Another Broken Browser Plugin Injecting Garbage in Pages (Norton?)', 'description': {'raw': 'The needcheck tag on it.wp recently detected half a dozen dirty diffs like this one: https://it.wikipedia.org/w/index.php?title=Respirazione_olotropica&curid=856162&diff=65014587&oldid=64980151 .\\n\\nThis seems to be due to a broken browser plugin, NortonInternetSecurityBF .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427402671, 'spacePHID': None, 'dateCreated': 1396015020, 'dateModified': 1492117851, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63229', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Show VisualEditor button label conditionally for GettingStarted tours', 'description': {'raw': 'Show the VisualEditor appendix conditionally for GettingStarted tours.  This is the same as {T63321}, but for GettingStarted tours.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1703380311, 'spacePHID': None, 'dateCreated': 1395868740, 'dateModified': 1703380311, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63147', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Automatically generate an edit summary for the user', 'description': {'raw': 'On stack overflow there is a nice feature that guess edit summary for user based on what they changed. So that when you edit something edit summary isn\\'t empty, but contains things like:\\n\\nReplace \"foo\" with \"bar\"\\n\\nOR\\n\\nInserted 20 words, removed 2 lines in paragraph \"blah\"\\n\\nOR\\n\\nPunctuation fixes\\n\\nUser is still able to modify it afterwards but this already save so much time. It would be nice if Visual Editor would do the same, so that users who do minor edits wouldn\\'t need to bother with writing the summary.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52859'}, 'authorPHID': 'PHID-USER-ppytiem7rcsbnstfsrvq', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1420999573, 'spacePHID': None, 'dateCreated': 1395865740, 'dateModified': 1556918750, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63142', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Web Thunder Helper Plugin (download) leaves garbage in pages', 'description': {'raw': 'See https://en.wikipedia.org/w/index.php?title=User:MGMT90018_Turnover/sandbox&curid=42095125&diff=599418792&oldid=599219453\\nThe \"Web Thunder\" plugin script from xunlei.com leaves the following litter at the top and bottom of pages:\\n\\n<embed id=\"xunlei_com_thunder_helper_plugin_d462f475-c18e-46be-bd10-327458d045bd\" type=\"application/thunder_download_plugin\" height=\"0\" width=\"0\" />\\n\\n<embed id=\"xunlei_com_thunder_helper_plugin_d462f475-c18e-46be-bd10-327458d045bd\" type=\"application/thunder_download_plugin\" height=\"0\" width=\"0\" />\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412114310, 'spacePHID': None, 'dateCreated': 1395856260, 'dateModified': 1417571831, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63121', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link can be applied on Cite Web/Book/Newspaper/Journal templates (but not reference nodes), which is confusing', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n\\n1.Open a page with VE\\n2.Add a text then a Cite>Website/Book/Newspaper/Journal just after that \\n3.Now select both the text and the cite\\n4.Apply link on it\\n\\nObserved Result:\\nThe link also gets applied on the Cite\\n\\nSee the screenshot attached\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Reference_numbering?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13245}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395787260, 'dateModified': 1416845695, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63091', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: IE9 doesn't load new page when when re-editing a page modified in another browser\", 'description': {'raw': 'To reproduce:\\n\\n1. Load a page in IE in the visual editor.\\n2. Load the same page in another browser, make a change, and save it.\\n3. Load the page view in IE, confirm you can see the edit.\\n4. Click \"Edit\" to enable the visual editor.  Old content appears in the editor.\\n5. Quit IE and restart.  Load page to edit in VE.  See new content in the editor.\\n\\nInitially I thought this was simply a server configuration issue (and maybe it still is), but I tested the same thing in FF and got the new page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1436996751, 'spacePHID': None, 'dateCreated': 1395704460, 'dateModified': 1436996751, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63048', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: IE9 places cursor inside ce=false table cell', 'description': {'raw': 'With the following wikitext:\\n\\n  __NOTOC__ \\n\\n  This is a test\\n\\n  {|\\n  |-\\n  | valign=\"top\" | \\n  == Header  ==\\n  * point one\\n  * point two\\n  ...\\n\\nVE starts up with the cursor on \"This\".  Pressing down once in FF ends up with the cursor on the \"Header\" line.  In IE, it ends up on the \"point one\" line.  Pressing up once in IE then puts the cursor on the \"Header\" line.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1491506647, 'spacePHID': None, 'dateCreated': 1395703680, 'dateModified': 1491506647, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63046', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Console shows \"Permission denied\" on IE9 when VE is first initiated', 'description': {'raw': 'From the console:\\n\\n SCRIPT70: Permission denied \\n Main_Page, line 1 character 1\\n\\nFiling to track this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1460994034, 'spacePHID': None, 'dateCreated': 1395701760, 'dateModified': 1461110524, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63039', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Can't create new paragraph by hitting return in IE9(?)\", 'description': {'raw': 'Typing return to generate a new paragraph in FF works.  Filing this to ask for a pointer to figure out how I might track it down and fix it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major'}, 'authorPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1460637023, 'spacePHID': None, 'dateCreated': 1395701460, 'dateModified': 1462842885, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63038', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: User should be able to add gallery inside reference', 'description': {'raw': 'Right now, Users can add image inside reference dialog box, similarly they should be able to add gallery inside it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395687900, 'dateModified': 1676676675, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63022', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Get rid of $.proxy, use native .bind()', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413498289, 'spacePHID': None, 'dateCreated': 1395097920, 'dateModified': 1417571689, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62762', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up SurfaceObserver usage', 'description': {'raw': 've.ce.Surface contains a bunch of calls to stopTimerLoop() and startTimerLoop() that are unnecessary and seem to have been added based on the false assumption that JavaScript can be multithreaded.\\n\\nThere are also duplicate calls to pollOnce that seem unneeded, or only exist to update state post-modification. We should audit these.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395097080, 'dateModified': 1643973196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62759', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Its possible to input a fraction value (with decimal point) in image size which results into showing wrong size in the review changes section', 'description': {'raw': 'Setting decimal value\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert a new image\\n3.Set the image size to a long value which becomes a number with scientific notation \\n4.Now start deleting the value from right to left\\n5.Once you have deleted the scientific notation (e) and the number becomes a value with decimal point , click on \"Apply Changes\"\\n\\nObserved Issue 1: it accepts that decimal value\\n\\n6.Click on Save Page and go to \"Review your Changes\"\\n\\nObserved Issue 2: The size value showing in the review changes section are completely different that what was set in step 5\\n\\nSee the screenshots attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=17marchff&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F13038}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399805347, 'spacePHID': None, 'dateCreated': 1395095100, 'dateModified': 1443276252, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62756', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  What you put into the template editor is not what it gives back (more Babel box bugs)', 'description': {'raw': \"Intention:\\nEdit a Babel box that I'd just created.\\n\\nSteps to Reproduce:\\n1. Create a Babel box using the workaround described in bug 62740 {T64740}.\\n\\n2. Apply changes.\\n\\n3. Select the transclusion and click the puzzle icon to edit it again.\\n\\n4. It looks confusingly different.\\n\\n\\nExpected Results:  \\nIf it can't add the function, then how is it able to edit it?  And if it can edit it, then why can't it add it normally?\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'bug', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395083820, 'dateModified': 1644071627, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62746', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Create a sensible system for adding Babel boxes (parser functions)', 'description': {'raw': 'Intention:\\nAdd a Babel box\\n\\nSteps to Reproduce:\\n1. Go to Insert > Template\\n\\n2. Type in #babel:en\\n\\n3. Click \"Add template\".\\n\\n4. Nothing happens.\\n\\n\\nExpected Results:  \\nEither it ought to Just Work™, or it ought to produce an error message about VisualEditor not supporting parser functions yet (see bug 50855).\\n\\nReproducible: Always\\n\\nWorkaround:  Go to complex transclusion mode; add \"Content\"; paste in wikitext source code for the parser function.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49996'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1395078720, 'dateModified': 1643973196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62740', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Merge the media editing and gallery editing dialogs', 'description': {'raw': \"Moved out of T40129's wishlist into its own bug.\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1519404558, 'spacePHID': None, 'dateCreated': 1394835240, 'dateModified': 1519404558, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62677', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Be able to set a over-ride link target (link=…) in the media edit dialog', 'description': {'raw': \"Moved out of bug 38129's wishlist into its own bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394834760, 'dateModified': 1643973196, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62672', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Centred images can appear in VE as overlapped by another image, then can't be selected\", 'description': {'raw': 'screenshot attached\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image \\n3.Insert another image just after it which is smaller than the previous one\\n4.Now align the first one to the left\\n5.Now align the second one to Centre \\n\\nObserved Result:\\n\\nThe smaller image overlaps with the previous bigger one in VE.If you save it and reopen the editor, you wont be able to see the image to select it.\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=Widthnullagainalways\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62850\\n\\n**Attached**: {F13301}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1521586640, 'spacePHID': None, 'dateCreated': 1394666940, 'dateModified': 1521629453, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62590', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Cannot read property cleardiff of null \" appearing while switching to Edit Source mode from VE', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page in VE\\n2.Edit the page\\n3.Switch to Edit Source mode\\n\\nObserved Result:\\nIn the console : an error is appearing :\"Uncaught TypeError:Cannot read property cleardiff of null\".\\nHowever, it does not hamper the functionality of switching/saving the page\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394673334, 'spacePHID': None, 'dateCreated': 1394564520, 'dateModified': 1443276258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62544', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Possibly unintended splitting of a table into two tables using VE', 'description': {'raw': \"Isn't VisualEditor supposed to be able to edit only the content of the table cells but not change the table structure? If so, I believe this should not happen:\\nhttps://pt.wikipedia.org/w/index.php?diff=38365876&uselang=en\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437696192, 'spacePHID': None, 'dateCreated': 1394487120, 'dateModified': 1438734952, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62510', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Hide action=visualeditor from the api.php documentation output, given it's internal and not intended for third party use\", 'description': {'raw': \"It seems to be possible to get the Parsoid HTML/RDF output through the standard Mediawiki API, but I can't figure out how.\\n\\nFor example, this fails:\\nhttps://en.wikipedia.org/w/api.php?action=visualeditor&paction=parse&page=Main_Page&oldid=598252063\\n\\nAn example would be really helpful.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61017\"}, 'authorPHID': 'PHID-USER-nwa6c3hm5nmv7ixrih4p', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1413246689, 'spacePHID': None, 'dateCreated': 1394363280, 'dateModified': 1512588750, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Advanced transclusion editor for complex templates eats parameters', 'description': {'raw': 'If you have a complex transclusion (e.g., a succession box), and you try to rearrange the order of the items, and if one or more of those items is a template that contains a parameter, then some or all of the parameter-containing templates will silently disappear.\\n\\nSee https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2014_1#Add_content_and_other_transclusion_mysteries for complaints.\\n\\n\\nDiffs of resulting problems:\\n\\nhttps://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=596891776&oldid=596891699\\n\\nhttps://en.wikipedia.org/w/index.php?title=User%3AFram%2Fsandbox&diff=597044161&oldid=596891923\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394238840, 'dateModified': 1426644327, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62415', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Empty references created in wikitext editor should be allowed to edit in VE', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with wikitext editor\\n2.Insert an empty reference for example: empty reference<ref />\\n3.Save the page\\n4.Now open the page with VE\\n\\nObserved Result:\\nIt does not let you edit the empty reference you just added and shows an error \"This reference is defined in a template or other generated block and for now can only be edited in source mode\"\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/Newpagereference?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F12863}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394220660, 'dateModified': 1422564675, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62401', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Save dialog throws \"Uncaught TypeError: Cannot read get getModel of undefined\" (IE9)', 'description': {'raw': 'Screenshot of bug.\\n\\nEncountered in IE9 using BrowserStack \"Windows 7/IE9\" using latest MediaWiki and VisualEditor master via a tunnel. Could either be a browser bug we have to work around, or something on our end applicable to other browsers as well.\\n\\n* Edit a simple document.\\n* Add two characters at the start.\\n* \"Save page\" enables itself.\\n* Click it.\\n\\nUncaught exception:\\n\\n> “Unable to get value of property ‘getModel’: object is null or undefined”.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13345}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1461148540, 'spacePHID': None, 'dateCreated': 1394128380, 'dateModified': 1461597369, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62334', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Weird repetition when using the editor in IE9', 'description': {'raw': 'Screenshot of bug.\\n\\nEncountered in IE9 using BrowserStack \"Windows 7/IE9\" using latest MediaWiki and VisualEditor master via a tunnel. Could either be a browser bug we have to work around, or something on our end applicable to other browsers as well.\\n\\n\\n* Load up the \"Worksheet\" page.\\n* Trying to put the cursor in the first paragraph and add text.\\n\\nIt repeats the first sentence many times and causes various weird scroll/focus events to occur all over the document.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13343}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1491506596, 'spacePHID': None, 'dateCreated': 1394128140, 'dateModified': 1491506596, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62332', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Why doesn't the Insert menu in the main editor have the same order as the Insert menu in the Image caption editor?\", 'description': {'raw': 'Open VisualEditor.  Click \\'Insert\\'.  First item in the main Insert menu:  Reference.  \\n\\nOpen (or insert) and image.  Under the Caption, click \\'Insert\\'.  First item:  Language.\\n\\nReference is still the most important item, and should be listed first.  (Should \"image\" even be listed at all?  It works, if you only go one deep, but...)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394060463, 'spacePHID': None, 'dateCreated': 1394058960, 'dateModified': 1443276262, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62286', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Shortcut system should support shifted punctuation characters', 'description': {'raw': \"Right now there is no way to express Ctrl+? in the trigger system. Attempting to type that on my keyboard registers as Ctrl+Shift+/ , but that's only because my keyboard layout is such that ? is above /. There should be a way to express Ctrl+? independent of the keyboard layout.\\n\\nThis may not be easy to do because Trevor tells me that charCode is less reliable than keyCode, so we may not be able to detect this correctly.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394056560, 'dateModified': 1643973197, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62282', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow enablement of VE on pages whose titles are matched by regexps, editable through an interface message', 'description': {'raw': 'Pages like:\\n* documentation - [[Template:Terminal/doc]]\\n* Wikipedia namespace = [[Wikipedia:Manual of Style]]\\n\\nNote that on many wikis there are custom subpages (like /doc) or namespaces which visual editing should be configurable.\\nI suggest MediaWiki interface - [[MediaWiki:Visualeditor-editable-pages]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-b27lopawgf2h6utuuqyi', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1393669740, 'dateModified': 1643973198, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62102', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"TypeError: $domNode.closest(...).data(...) is undefined\" appears while dragging an image inside Media Settings and Reference dialog box', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Open a reference dialog or Media Settings for an image\\n3.Insert two images inside that dialog.\\n4.Now drag one of them\\n\\nObserved Result:\\n\\nObserve that, the shadow of the image appears from the corner of CE instead of the dialog.Also an error appears after dragging the image shadow over itself:\\nTypeError: $domNode.closest(...).data(...) is undefined\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=New_pageon%24&gettingStartedReturn=true&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13253}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1393553040, 'dateModified': 1416845709, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62031', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Slashes in titles should be escaped when generating links', 'description': {'raw': '**Author:** `vigna`\\n\\n**Description:**\\nSome Wikipedia pages contain slashes in their title, e.g., \"/b/\" or \"/dev/null\". Such slashes should be escaped to %2F when they are not meant to separate paths components, as per RFC 1738/3986. Instead, for instance,\\n\\nhttp://en.wikipedia.org/w/index.php?title=B/&redirect=no\\n\\ncontains an A element\\n\\n<a href=\"/wiki//b/\" title=\"/b/\">/b/</a>\\n\\nthat should written\\n\\n<a href=\"/wiki/%2Fb%2F\" title=\"/b/\">/b/</a>\\n\\n\\nThis causes 2 problems:\\n\\n1) The URL above does not conform to the RFCs. This is a minor issue but it might rise other problems in the future.\\n\\n2) If the slash is initial, the URI is not normalized as per RFC. E.g., in Java\\n\\nbsh % print(URI.create(\"wiki//b/\").normalize());\\nwiki/b/\\n\\nThis might be a problem with crawlers, which usually normalize URLs to reduce the number of duplicates.\\n\\n\\n\\nNote that %2F-escaped slashes work perfectly, and \\n\\nhttp://en.wikipedia.org/wiki/%2Fb%2F\\n\\nbrings you exactly to /b/\\'s page. Bug 8254 seems to say the opposite, but it\\'s a few years old.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1393411620, 'dateModified': 1393606210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61944', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add a tooltip to the page menu button', 'description': {'raw': 'The button for the \"More settings\" menu has no tooltip.  Should it?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393637800, 'spacePHID': None, 'dateCreated': 1393309920, 'dateModified': 1443276274, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61892', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Blanking the page does not remove meta-data (categories, defaultsort keys, etc.)', 'description': {'raw': 'Intention:\\nBlank a page (prior to setting a redirect).\\n\\nSteps to Reproduce:\\n1. Select all (Command-a).\\n2. Press the delete key.\\n3. Save > Review changes.\\n\\nActual Results:  \\nCategories, defaultsort keys, and page protection templates are not removed.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/w/index.php?title=User:Whatamidoing_(WMF)&diff=914307&oldid=904077'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1393268400, 'dateModified': 1434928717, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61858', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding gallery as Heading creates inconsistency between readmode and VE mode', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add a heading\\n3.Select the text of the heading and insert a gallery\\n4.The gallery gets added as part of the heading\\n5.Save the page and observe the page content in the readmode\\n\\nObserved Result:\\n\\nIn readmode , the heading text and caption of the gallery gets repeated immediately following the heading section.Also gallery is not showing up as part of the heading where as in wikitext editor it is inside ==heading== and also in VE\\n\\nSee the screenshot attached\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser:  FF 25\\nOS: MAC OS X 10. 8. 5 \\nhttps://test2.wikipedia.org/w/index.php?title=Totalnewheading\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13262}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1442272451, 'spacePHID': None, 'dateCreated': 1393026840, 'dateModified': 1442930171, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61787', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Instapaper plug-in injects div tags into pages', 'description': {'raw': 'Instapaper is \"a simple tool for saving web pages to read later on your iPhone, iPad, Android, computer, or Kindle.\"  It adds div tags to the top and bottom of pages edited in VisualEditor.  \\n\\nSee https://en.wikipedia.org/w/index.php?title=Major_Arcana_%28album%29&diff=589184449&oldid=589116581 for an example.  It added this to the top and the bottom:\\n\\n<div id=\"sendToInstapaperResults\"></div>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/w/index.php?title=Major_Arcana_%28album%29&diff=589184449&oldid=589116581'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412114298, 'spacePHID': None, 'dateCreated': 1393018260, 'dateModified': 1417571831, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61776', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Data item\" link in sidebar disappears in classic edit mode', 'description': {'raw': 'Pages in View mode contain a convenient link to the related \"Data item\" (in the sidebar, under Tools). However, in the classic edit mode such links disappears. It is a convenient link for editors, and there is no reason why it should disappear.\\n\\nPS: the link is kept in VisualEditor since the \"page\" actually doesn\\'t change.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=45687'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414582689, 'spacePHID': None, 'dateCreated': 1393014300, 'dateModified': 1733934272, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61768', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Key performance indicator: Bugzilla response time', 'description': {'raw': 'http://korma.wmflabs.org/browser/bugzilla_response_time.html should answer these questions:\\n\\nHow long does it take to give a first response to reporters of Low-Immediate / trivial-blocker bugs? How long until acknowledged bugs are resolved? Are we using the importance parameters consistently? Are we improving?\\n\\n* Average time for an accepted bug report between bug creation date and PATCH_TO_REVIEW status being set\\n* Average time for an accepted bug report between PATCH_TO_REVIEW status being set and RESOLVED FIXED status being set.\\n* Average time for an accepted bug report between bug creation date and first comment by not the reporter her/himself.\\n\\nhttps://www.mediawiki.org/wiki/Community_metrics#Bugzilla_response_time\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1417699948, 'spacePHID': None, 'dateCreated': 1392848400, 'dateModified': 1418717747, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61561', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  ISBN link labels (from magic words) can be changed, but not the underlying links', 'description': {'raw': 'Intention:\\nChange an ISBN.\\n\\nSteps to Reproduce:\\n1. Open a page with a pre-existing ISBN number (using the magic word).\\n\\n2. Click in the link and open the link inspector.\\n\\n3. Correct the numbers in the ISBN.\\n\\n4. Close the link inspector.\\n\\n\\n\\nActual Results:  \\nThe link label does not change.  This is not surprising, given VisualEditor\\'s approach to links, but it is sometimes unfortunate; see https://fr.wikipedia.org/w/index.php?title=Massimo_Introvigne&diff=100272017&oldid=94374615\\n\\nHowever, the link itself does not change, and if you have done nothing else, it is not possible to save the page, because you have supposedly made no changes.\\n\\nExpected Results:  \\nIdeal behavior:\\n\\nChanging \"ISBN 1234567890\" to \"ISBN 1234567891\" simply updates the plain wikitext magic word.\\n\\nPossibly acceptable behavior:\\n\\nChanging \"ISBN 1234567890\" to \"ISBN 1234567891\" updates the link to [[Special:BookSources/1234567891|ISBN 1234567891]].\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52204'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1441133550, 'spacePHID': None, 'dateCreated': 1392846900, 'dateModified': 1660398906, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61558', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'GUI for VisualEditor Math plugin', 'description': {'raw': 'The original plan for the math plugin was to create a equation editor GUI, similar to that in Google Docs.\\nhttps://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Application\\n\\nThis would have ability to insert mathematical symbols and create structures like integrals, matrices etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392741898, 'spacePHID': None, 'dateCreated': 1392740220, 'dateModified': 1392850529, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61498', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Avoid mentioning wikitext on MediaWiki error messages (this confuses users who use VisualEditor instead of wikitext)', 'description': {'raw': 'Consider VisualEditor as the default editing method, and suppose you are a new user arriving at one of the articles currently listed under\\n[[Category:Pages with missing references list]]\\n(or its equivalents in other languages).\\n\\nSomewhere in the page there will be messages such as these:\\n* There are <ref> tags on this page, but the references will not show without a {{reflist}} template (see the help page).\\n\\n* There are <ref group=$1> tags on this page, but the references will not show without a {{reflist|group=$1}} template (see the help page).\\n\\nBut since your few edits were made using VisuaEditor, you have no idea what are \"<ref>\", \"<ref group=$1>\" and \"{{reflist|group=$1}}\".\\n\\nThere are many other messages like that which are exposed to (inexperienced) users (either by MediaWiki core or one of its extensions). They should try to describe the problem avoiding talking about the wiki syntax, which will not make sense if VisualEditor is the only way someone is able to edit.\\n\\n\\nThis bug report was inspired by the following feedback:\\nhttps://pt.wikipedia.org/wiki/WP:Editor_Visual/Comentários?oldid=38180789#fonte.2C_pede_sempre.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1392546660, 'dateModified': 1643973198, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61434', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CSS to add numbers to reference list items it vertically misaligned (should be top not bottom?)', 'description': {'raw': 'Screenshot\\n\\nNumber of reflist vertically misaligned, see screenshot\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://de.wikipedia.org/w/index.php?title=Wolfgang-Hahn-Preis_K%C3%B6ln&veaction=edit\\n\\n**Attached**: {F13043}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1525335436, 'spacePHID': None, 'dateCreated': 1392490020, 'dateModified': 1525335436, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61423', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Section preview in new wikitext editor shows Translate markup', 'description': {'raw': 'This is with Translate 2014-02-04.\\n\\nI\\'ve created a testcase which you can see by visiting https://www.mediawiki.org/w/index.php?title=User:SamB/tvar_bug&oldid=907218&action=edit&section=1 and clicking the \"preview\" button.\\n\\nNotice how all of the Translate markup shows up in the Preview because the <translate> tag isn\\'t in this section?  That\\'s kind of annoying.\\n\\n{F31698682}'}, 'authorPHID': 'PHID-USER-3bnjvlq3zbpzzxdh4g4g', 'ownerPHID': 'PHID-USER-ut3yptb7r45gfpwp33qn', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ut3yptb7r45gfpwp33qn', 'dateClosed': 1675189578, 'spacePHID': None, 'dateCreated': 1392487980, 'dateModified': 1675189578, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61422', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Phantoms showing in top left corner for no-longer visible objects', 'description': {'raw': 'screenshot\\n\\nsteps to reproduce:\\n\\n1.Open a page with VE\\n2.Insert an image\\n3.Go to the Media Settings of the image\\n4.Set the image to frameless and none as position\\n5.Now select the image\\n\\nObserved Result:\\n Image highlight box is appearing at the top left corner of the page\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=14thfebchrome&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n\\n**Attached**: {F12967}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393615223, 'spacePHID': None, 'dateCreated': 1392406080, 'dateModified': 1443276283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61390', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Span tags getting added to references when pasting from Microsoft Office', 'description': {'raw': 'See for instance\\nhttps://fr.wikipedia.org/w/index.php?title=Philippe_Juvin&diff=101226971&oldid=101177693 .\\nThe edit added `<span style=\"font-size:12.0pt;font-family:\"Times New Roman\",\"serif\"; mso-fareast-font-family:Calibri;mso-ansi-language:EN-GB;mso-fareast-language: EN-US;mso-bidi-language:AR-SA\">` to a newly added reference.\\nIt was reported by NicoV at fr.wp, I haven\\'t had a chance to see if it can be reproduced or how yet.\\n\\n**See Also**:\\n* {T60689}\\n* {T71821}\\n* {T71513}\\n* {T75292}'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701962897, 'spacePHID': None, 'dateCreated': 1392375360, 'dateModified': 1701962897, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61371', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'New VisualEditor translations not appearing in production as quickly as for other features(?)', 'description': {'raw': 'Intention:\\nWhenever a new VE feature is launched it seems as though existing translations are not included.\\n\\nSteps to Reproduce:\\n1. Go to https://sv.wikipedia.org/wiki/Bonsai?uselang=de&veaction=edit\\n2. Click on media settings for the first image\\n3. Click advanced settings (Erweiterte Einstellungen)\\n\\nActual Results:  \\n2. Alt_text dialogue reads \"Alternative text\"\\n3. Position dialogues read \"Position: Left, right, center, none \"\\n\\nExpected Results:  \\n2. Alt_text dialogue reads \"Alternativtext\" (per https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-alttext-section/de)\\n3. Should also be all in german (per e.g. https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-position-left/de)\\n\\nReproducible: Always\\n\\nThis is not just an issue with the above features (or with uselang=de) but rather happens at every launched VE feature. Since the translations have normally been done before there is no reason why they should not be included as part of the pushing of any new feature.\\n\\nThe VE translations also seem to take longer to go live then translations in other parts of the interface (seems to happen only when there are other VE updates).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=64230'}, 'authorPHID': 'PHID-USER-uu7wg6g3b37dcktbje3a', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-escte3psz5yfd2nj3jzr', 'dateClosed': 1723522286, 'spacePHID': None, 'dateCreated': 1392370920, 'dateModified': 1723522286, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61368', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Babel box not updated correctly upon editing', 'description': {'raw': \"Intention:\\nRemove extraneous items from a Babel box\\n\\nSteps to Reproduce:\\n1. Click on the Babel box to edit it. \\n2. Remove unwanted parameters (with trashcan icon).\\n3. Apply changes.\\n\\nActual Results:  \\nThree items were correctly removed, but two that were kept were not displayed in VisualEditor.  (See screenshot to compare diff to VisualEditor's display.)\\n\\nExpected Results:  \\nThe transcluded {{#babel:en}} function would display correctly. \\n\\nReproducible: Yes\\n\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1392340440, 'dateModified': 1533062497, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61356', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clear formatting remains selected even after re-applying the styles from the menu', 'description': {'raw': 'Highlighted clear formatting option\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Select a text and apply some text styles from the toolbar like \"Bold\", \"Italic\"\\n3.Now select \"Clear Formatting:\\n4.Again reapply these formats\\n\\nObserved Result:\\nObserve that, the though the text formats are reapplied the \"Clear formatting\" option remains selected.\\n\\n\\nSee the screenshot attached\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/11thfeb?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13203}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397787388, 'spacePHID': None, 'dateCreated': 1392147360, 'dateModified': 1417572416, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61229', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: default-thumbnail-size preferences are not being followed', 'description': {'raw': 'All thumbnails, eg [[File:example.jpg|thumb]], are displaying as 220px (which is the usual wikimedia/mediawiki default, per bug 21117). \\n\\nIf I change my \"Thumbnail size\" preferences (to 300px for example) at https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-rendering then the thumbnails in existing Flow posts do not change accordingly.\\n\\nThe same applies to new posts that I make, or posts that I edit: all thumbnails are 220px regardless.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409929682, 'spacePHID': None, 'dateCreated': 1391825160, 'dateModified': 1418953227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61081', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: All inspectors get broken after VE tab is idle for a while', 'description': {'raw': 'broken link inspector UI\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add an image\\n3.Go to some other tab/window\\n4.After an idle time (~5 mins) come back to VE\\n5.Open any inspector like galley/link/Math\\n\\nObserved Result:\\n\\nAll the inspectors are appearing with broken UI\\n\\nSee the screenshots attached.\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nSample Page:https://test2.wikipedia.org/wiki/Test2chromefeb7th?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70580\\n\\n**Attached**: {F12858}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429482758, 'spacePHID': None, 'dateCreated': 1391822100, 'dateModified': 1438734960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61078', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Block format=xml from action=visualeditor API', 'description': {'raw': 'Given url:\\nhttp://en.wikipedia.org/w/api.php?action=visualeditor&page=Berlin&paction=parse\\n\\nReturn this:\\n<?xml version=\"1.0\"?>\\n<api servedby=\"mw1193\">\\n  <error code=\"internal_api_error_MWException\" info=\"Exception Caught: Internal error in ApiFormatXml::recXmlPrint: (notices, ...) has integer keys without _element value. Use ApiResult::setIndexedTagName().\" xml:space=\"preserve\" />\\n</api>\\n\\nI guess, I make something wrong, but the error message does not really help me to understand what goes wrong.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62452'}, 'authorPHID': 'PHID-USER-nwa6c3hm5nmv7ixrih4p', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395873706, 'spacePHID': None, 'dateCreated': 1391769780, 'dateModified': 1443276294, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61017', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Spin out UnicodeJS', 'description': {'raw': \"If nothing else, it should probably be in the /lib directory rather than /modules (which will save us a directory's depth of file paths).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416343480, 'spacePHID': None, 'dateCreated': 1391306880, 'dateModified': 1443278209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60731', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid doesn't have a mode to tailor rendered content based on user preferences\", 'description': {'raw': ''}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1391281200, 'dateModified': 1632954586, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60728', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Providing clearer errors about invalid media item sizes on new Media Settings>Advanced Settings', 'description': {'raw': 'Right now, if I add an image for example:https://test2.wikipedia.org/wiki/File:Foo.jpg\\n\\nInitially in VE from Insert>Media it renders as 229x150.\\nIf a user attempts to resize it to 350x350 , it will show a message that \"Size Values are invalid\"  as it has exceeded the original dimension values.But unless user knows those original dimensions , he or she might keep trying with different values not knowing what should be the input limit.\\n\\nI think it will be better if we can have more clearer indication in the message saying something like \"the size values are invalid since it has exceeded original dimension\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1391216220, 'dateModified': 1643973200, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60705', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Character set in mathematical symbols is out of order (degree, seconds, minutes)', 'description': {'raw': 'Reproducible: Always\\n\\nhttp://mediawiki.org/wiki/MediaWiki:Visualeditor-specialcharinspector-characterlist-insert should have the logical order of degrees, minutes, seconds, not with seconds in the middle.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402335972, 'spacePHID': None, 'dateCreated': 1391106240, 'dateModified': 1443278211, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60626', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOjs UI: Constructive button has odd green border when disabled', 'description': {'raw': \"I'm not sure, but I think this is a regression (it didn't use to be this way).\\n\\nA button that is flagged as constructive and currently disabled has a green border around its otherwise grey button. When hovering the button the border becomes grey, so it doesn't seem intentional that the border is green (otherwise it should have a hover implementation as well).\\n\\nThis is most visible when opening VisualEditor, the save button has emits this behaviour.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396400187, 'spacePHID': None, 'dateCreated': 1390859100, 'dateModified': 1427403795, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60498', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'CodeEditor should support editing <syntaxhighlight> blocks on a page', 'description': {'raw': '**Author:** `gryllida`\\n\\n**Description:**\\nScript viewer software should support sections and section editing, using one-line comments (or special formatting therein) for heading syntax.\\n\\n---------------------------------------------\\n\\n/* Foo */\\n\\nFoo.prototype.bar = function(){\\n...\\n};\\nFoo.prototype.baz = function(){\\n...\\n};\\n\\n^^^^^ everything above is in the Foo section\\n\\n/* Foo 2 */ <---------- this becomes a heading\\n\\nFoo2.prototype.bar = function(){\\n...\\n};\\n\\nFoo2.prototype.baz = function(){\\n...\\n};\\n\\n^^^^^ everything above is in the foo 2 section\\n\\n\\n---------------------------------------------\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50962'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1649198234, 'spacePHID': None, 'dateCreated': 1390727760, 'dateModified': 1649198234, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60438', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"CodeEditor's drag and drop only works after a small delay\", 'description': {'raw': 'Dragging and dropping text (as an alternative to keyboard or context menu copy and paste commands) inside CodeEditor does not work.\\n\\nSince this is basic functionality in every other editor I know this should also be supported by CodeEditor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://github.com/ajaxorg/ace/issues/1879'}, 'authorPHID': 'PHID-USER-v3yn5qf233ggnnnmvejc', 'ownerPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-bxp7xrbobtrp5o3q3swv', 'dateClosed': 1422657292, 'spacePHID': None, 'dateCreated': 1390684080, 'dateModified': 1426055130, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60432', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Show a user's recent uploads in the MW insert media dialog (MediaSearchWidget)\", 'description': {'raw': 'This should especially useful as new images may not appear in the API search results due to caching.'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1594648967, 'spacePHID': None, 'dateCreated': 1390585980, 'dateModified': 1596141663, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60398', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Unclosed <dl> and <div> tags caused by absent {{refend}} template cannot be repaired', 'description': {'raw': \"Intention:\\nRemove a line that appears in the last section of a page, underneath a section that has an unclosed/unpaired {{refbegin}} template.\\n\\nSteps to Reproduce:\\n1. Open https://en.wikipedia.org/w/index.php?oldid=592187387 in VisualEditor.\\n\\n2. Try to select anything after the ==Bibliography== section, e.g., anything in the ==External links== section.\\n\\nActual Results:  \\nThe cursor knows only two positions:  before the refbegin template, and in the slug at the bottom of the page.  You can't select or edit anything in between.\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1617657078, 'spacePHID': None, 'dateCreated': 1390579800, 'dateModified': 1668031363, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60395', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Preview from MWAlienInspector of a syntaxhighlight block shows text HTML encoded when it shouldn't\", 'description': {'raw': 'Steps to reproduce:\\n\\n- create a simple page with just this text: <syntaxhighlight lang=\"xml\">></syntaxhighlight>\\n- example page: https://test2.wikipedia.org/wiki/Codez\\n- when the page is saved, only this is displayed, as expected: >\\n\\n- edit the page with visual editor\\n- edit the text using syntaxhighlight editor\\n- for example, add just this: <\\n- see attached screen shot #1\\n\\n- use \"back\" icon to see how the text will look like\\n- I was expecting to see this as page text: ><\\n- instead, the preview says page text is: &gt;&lt;\\n- see attached screen shot #2\\n\\n- when the page is saved, the text is displayed correctly: ><\\n- see attached screen shot #3\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404486826, 'spacePHID': None, 'dateCreated': 1390390860, 'dateModified': 1417596496, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60332', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Opening and closing the gallery inspector without making any change causes a transaction', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page which has a gallery inside it with VE\\n2.Select the gallery and open the gallery inspector\\n3.Close the gallery inspector \\n\\nObserved Result:\\n\\nThe \"Save page\" button of the page gets enabled although no change has been made in the gallery inspector\\n\\nTest Environment: https://test2.wikipedia.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:https://test2.wikipedia.org/wiki/Thedomtest\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-abybinou47zwmsranndg', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1489520963, 'spacePHID': None, 'dateCreated': 1390348020, 'dateModified': 1492042764, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60311', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Fully alphabetize Wikimedia configuration file visualeditor.dblist', 'description': {'raw': \"https://noc.wikimedia.org/conf/visualeditor.dblist\\n\\nThis should be fully alphabetized, in my opinion. While people with intimate knowledge of Wikimedia's structure can likely discern and explain the current order, it seems like a lot more overhead than any value provided. A simple alphabetical index is easier to maintain (including insertion), it's more consistent with the other lists of databases (as far as I know), etc.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390321562, 'spacePHID': None, 'dateCreated': 1390266360, 'dateModified': 1390321562, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60273', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Client-side previewing', 'description': {'raw': \"I'm not sure how well these would work, but at least here in China, it is slow to wait for previews of musical scores for each modification. If you could add client-side support to Score, perhaps via:\\n\\n* http://code.google.com/p/abcjs/\\n* https://github.com/incompleteopus/vexabc\\n\\n...I wonder whether client-side rendering support (ideally in SVG in case notes could be synchronized with the music play-back in the future) could be added, if not now, then maybe after the main Mediawiki WYSIWYG interface stabilizes?\\n\\nAnd support for the emerging Web Audio standard would be awesome for client-side audio play-back as well...\\n\\nAlso, with ABC seeming (to my quick glance) more like an open standard than Lilypond, might it make sense to make ABC the default?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-gljzp3uzec5ukggh6xdk', 'ownerPHID': 'PHID-USER-u66bgsaukythpwcdyjdu', 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-u66bgsaukythpwcdyjdu', 'dateClosed': 1502064207, 'spacePHID': None, 'dateCreated': 1390051560, 'dateModified': 1502290121, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60202', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Separate UploadWizard's data-handling, interface, and other controlling methods and put generally-applicable code into MediaWiki\", 'description': {'raw': \"In the past few years we've worked really hard to bring UploadWizard to a usable state, and now that we have a Multimedia team framework to actually do some good work on it, and we have the impetus to start making the upload pipeline way better, let's do it the right way: Let's make this project the organized, well-engineered machine it should have been in the first place.\\n\\nI would particularly emphasize code conventions being followed, jshint conformance, an eye towards an MVC-like structure (nothing strict, but as a general goal...), building toward libraries that can be used elsewhere, and a variety of different possible interfaces.\\n\\nIdeally none of the upload steps will be entangled unnecessarily with other steps, and we will be able to untangle them when necessary and put them in different pages or tools.\\n\\nIdeally we will use the brilliant work- and complexity-reducing technology (oojs, oojs-ui, jQuery promises, moment.js) that other projects have started using in recent times.\\n\\nIt is an absolute *must* that we build tests for this system as we are building it, if we want this to be a generally useful set of tools for other projects. Same for documentation.\\n\\nThe leaders in LOC for active frontend projects deployed on the cluster are* VisualEditor, UploadWizard, Flow, and MultimediaViewer (in no particular order). Let's start bringing the upload pipeline projects closer to the high standards that other projects are holding themselves to.\\n\\n* According to an unscientific survey based on guesswork\\n\\nSee https://www.mediawiki.org/wiki/Requests_for_comment/More_general_frontend_uploading_tools for more.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62513\"}, 'authorPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1442332652, 'spacePHID': None, 'dateCreated': 1389627360, 'dateModified': 1468261257, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60002', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Work correctly in Draft namespace (tracking)', 'description': {'raw': 'This is a tracking bug for any problems in VisualEditor associated with the Draft: namespace at the English Wikipedia.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415031855, 'spacePHID': None, 'dateCreated': 1389304860, 'dateModified': 1552743784, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59885', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: AbuseFilter \"Tag the edit for further review\" doesn\\'t work', 'description': {'raw': 'It\\'s not clear how the \"Tag the edit for further review\" option for AbuseFilter rules would work for Flow. Maybe it would add something to the Special:RecentChanges entry for FLow.\\n\\nThis is mentioned in https://www.mediawiki.org/wiki/Flow/Administration_notes\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n**See Also**: {T64750}'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1389145320, 'dateModified': 1670601226, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59811', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Scribunto pulls in jquery.ui.dialog for error reporting', 'description': {'raw': 'On wiki\\'s with Scribunto installed, when viewed in the mobile site, the exception \"Uncaught Error: Unknown dependency: ext.scribunto\" is thrown which prevents any further JavaScript from running.\\n\\nThis is because the module is not registered on mobile.\\n\\nIt also depends on jquery.ui.dialog code which pulls in the entire jquery.ui library - we certainly do not want on mobile where JavaScript load should be as tiny as possible.\\n\\nI doubt we\\'d want to run this code on mobile thus the use of addInlineScript needs to be avoided since the module doesn\\'t exist in the mobile environment. At the very least it should be wrapped with a try catch so say it is acceptable to fail.\\n\\nSeems to have been introduced by https://gerrit.wikimedia.org/r/#/c/5617/1,publish\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395858075, 'spacePHID': None, 'dateCreated': 1389142380, 'dateModified': 1602870223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59808', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Toolbar doesn't float properly in standalone demo\", 'description': {'raw': 'It either snaps to the top left of the screen (instead of lining up with the surface), or it tries to render with 0 width (especially if you switch page)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390863446, 'spacePHID': None, 'dateCreated': 1389017880, 'dateModified': 1443276316, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59720', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Cutting (removing) last section on the page leaves blank section heading == <nowiki /> ==', 'description': {'raw': 'Intention:\\nRearrange the sections on a page\\n\\nSteps to Reproduce:\\n1. Select the entire last section\\n2. Cut (Command-X) the section\\n3. Paste it elsewhere\\n\\nActual Results:  \\nThe formatting for the section heading (not the formatting for the last line) remains at the end of the page.\\n\\n\\nExpected Results:  \\nThe last line should either disappear entirely (be replaced by a slug) or be set to default/Paragraph styling\\n\\nReproducible: Always\\n\\nRemoving the blank section heading produced its own problems; look for the next bug report.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/w/index.php?title=Celebrity_branding&diff=589156664&oldid=583130311\\n**See Also**:\\n{T52100}\\n{T57769}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426893943, 'spacePHID': None, 'dateCreated': 1388853360, 'dateModified': 1428007120, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59647', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: A reference list directly after a list contnues that list in MW, so CE should make sure it does that', 'description': {'raw': 'In edit mode\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Now add a reference to the page\\n3,Add a bullet or numbered list\\n4.Add references list from Insert>References list\\n5.Save the page\\n\\nObserved Result:\\nThe references list appeared as a bulleted item or numbered item of the preceding list\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 \\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/30th_december?veaction=edit\\n\\nSee the screenshot attached\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F12662}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1388433240, 'dateModified': 1664896979, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59133', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Any changes made to an article by other users since switching into VE aren't reflected when switching back to read mode\", 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open an article in read mode in two different tabs of same browser or in two different browsers.\\n\\n2.Now edit the page using one browser or tab\\n\\n3.Save the change\\n\\n4.Now open the same article with VE using another browser or tab\\n\\n5.Click on \"cancel\"\\n\\nObserved Result:\\nAfter step 4 the change made in step 2 by another browser or tab are correctly reflected in the edit mode .\\n\\nBut after pressing cancel on step 5 , it has been observed that the readmode is still not showing the change done in step 2 unless user refreshes it.\\n\\nIt will be better if both Edit mode and Read mode shows consistent content even if the change is made by other user/browser session\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1388174160, 'dateModified': 1416846329, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59004', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: document.activeElement can change unexpectedly while typing in VE editor', 'description': {'raw': '**Author:** `jhall`\\n\\n**Description:**\\nAfter observing some strange results from an automated Ruby test for cursor movement in the Visual Editor CE surface, we did some digging, and it appears that while a user is typing away happily and making and edit, the document.activeElement flip-flop several times.  \\n\\nI\\'m assuming this is unintentional behavior, thus the bug ticket.\\n\\nRepro steps:\\n\\n1)  Visit this page: https://test2.wikipedia.org/wiki/User:Selenium_user/cursor_test_page_chromedriver_bug\\n2)  Click into VE editing mode.\\n3)  With cursor placed immediately in front of the letter \"a\" in the word \"after\", press the right arrow key several times in succession. \\n4)  When your right-arrow-clicking brings you to the reference, the document.activeElement switches from \"ve-ce-documentNode ve-ce-branchNode noime\" to \"ve-ce-surface-paste\"\\n\\nI\\'m assuming that when the user is typing in the \"editing box\", the document.activeElement should not be changing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57552'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'bug', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701962577, 'spacePHID': None, 'dateCreated': 1388165580, 'dateModified': 1701962577, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58998', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:Hiero is getting copied as Empty template while copying from Chrome to FF', 'description': {'raw': 'Steps to reproduce:\\n\\n1.Open a page with VE in Chrome\\n2.Copy a hiero\\n3.Open another page in FF\\n4.Paste the hiero into it\\n\\nObserved Result:\\nAn empty template table appears.The resulting wikitext is:\\n{|\\n\\n|\\n{|\\n\\n|\\n\\n|}\\n\\n|}\\n\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/w/index.php?title=26th_paste_ff&veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1453424212, 'spacePHID': None, 'dateCreated': 1388094480, 'dateModified': 1462807327, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58982', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Use colorful icons, or provide an option to use colorful icons / themes', 'description': {'raw': 'Gryllida suggests that VisualEditor have colorful icons.  Alternatively, the existing monochrome icons could be kept, but editors could be given the option of choosing a Microsoft-style \"theme\" to change the appearance of the icons.  \\n\\nIn addition to being fun, it is possible that other icon styles would improve accessibility for some users.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1555252646, 'spacePHID': None, 'dateCreated': 1387824900, 'dateModified': 1555252646, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58904', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Left and right arrow keys jump to images if image has previously been viewed in Media Viewer', 'description': {'raw': 'I have enabled the experimental Media Viewer feature on Wikipedia, and when I click on an image, left and right scroll through the images on the page in full-window mode.\\n\\nHowever, when editing a page in Visual Editor, this keeps happening (that is, images from the article keep appearing in full-window mode) when I am trying to move around with the cursor keys.\\n\\nVisualEditor should disable this \"feature\", as it\\'s obviously not wanted when editing a page!\\n\\nI use the Chromium browser.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: Linux\\n**Platform**: PC\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58266'}, 'authorPHID': 'PHID-USER-bug3zrlooz3bdmi4fyl7', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389379350, 'spacePHID': None, 'dateCreated': 1387747020, 'dateModified': 1417690503, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58873', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor:  Command-x (cut) triggers browser's Undo (Command-z) in Safari\", 'description': {'raw': \"Intention:\\nMove a section of a page by cutting it out of one place and pasting it into the right place.\\n\\nSteps to Reproduce:\\n1.  Close an unwanted browser tab.\\n2.  Select several paragraphs in VisualEditor.\\n3.  Press Command-x to cut (not just copy) the material.\\n4.  Notice that the just-closed browser window has reappeared.  (Command-z/Undo in Safari reopens a tab that you just closed.)\\n\\n\\n\\nReproducible: Always\\n\\nI am unable to reproduce this in Firefox, presumably because selecting text within VisualEditor seems to clear (or otherwise make unavailable) the 'undo' buffer.  So even if VisualEditor is telling Firefox to undo something, Firefox believes that there there's nothing to undo.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57217\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409240399, 'spacePHID': None, 'dateCreated': 1387498860, 'dateModified': 1443278215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58724', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Disable \"Beta\" suffixes on tabs for VisualEditor opt-in wikis', 'description': {'raw': 'On opt-in wikis, users already have to explicitly choose to be able to use VisualEditor, and they get a warning the first time they do so. Adding beta suffixes all over the UI is a leftover from opt-out status and only appropriate in wikis that are opt-out, and where communities explicitly request such notices to be present.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-766idcqt4jkngnnuhnrj', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1426002351, 'spacePHID': None, 'dateCreated': 1387305900, 'dateModified': 1660398905, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58583', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Outline widget in booklet layout responds to mouse up events even if they started elsewhere', 'description': {'raw': 'These should probably only respond to click events although it seems they currently support the click and drag functionality of a drop down box. If you are editing a textarea in the right hand panel and you click and drag from right to left to select all the text you will often end up with your mouse over the outline widget. Releasing your mouse here will cause you to jump to a random page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416325755, 'spacePHID': None, 'dateCreated': 1387298340, 'dateModified': 1427403801, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58580', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links should do pre-annotations in both directions (not just down-page but also up-page)', 'description': {'raw': 'When editing Wikipedia, I have repeatedly run into the following issue: \\n\\nThe article contains a link and I want to change the beginning of the link text (not the link\\'s target), usually because it is upper case and I want it lower case. So I use VisualEditor to delete the first letter of the link and replace it with its lower case version. The result is unexpected: the first letter is not marked up as part of the link, but this is very hard to see.\\n\\nThe source code is transformed from [[Link]] to l[[Link|ink]]. Links like the latter are almost never contained in human-created wikitext.\\n\\nSuggestion: link text should be \"magnetic\", so that changes at either end will automatically inherit the link markup.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'dateClosed': 1517159838, 'spacePHID': None, 'dateCreated': 1387231020, 'dateModified': 1517243600, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58554', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: support VisualEditor VE editing of header & topics (tracking)', 'description': {'raw': 'VisualEditor is currently disabled as an editor in Flow:\\n  $wgFlowEditorList = array( \\'none\\' );  // EXPERIMENTAL prepend \\'visualeditor\\'\\n\\nwhen we re-enable it, the VE bugs we discovered will probably still apply.\\n\\nThe WMF core features team plans the \"VisualEditor integration\" story in  Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/28\\n\\n--------------------------\\n**Version**: master\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'dateClosed': 1435083204, 'spacePHID': None, 'dateCreated': 1386884340, 'dateModified': 1635983647, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58411', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Pasting a syntaxhighlight block from another VE surface don't load syntaxhighlight's styling\", 'description': {'raw': 'After pasting a block of <syntaxhighlight> in to a target surface, I had to save and then reload the page before the syntax highlighting styling was applied. \\n\\nhttps://www.mediawiki.org/w/index.php?title=User:TheDJ/sandbox&oldid=841358\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=67515'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-mvx4x7ywk2flsaku2dbk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1474411555, 'spacePHID': None, 'dateCreated': 1386843900, 'dateModified': 1632170097, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58388', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Templated tables seem to fail in copy paste', 'description': {'raw': \"https://www.mediawiki.org/wiki/Manual:Code?veaction=edit\\n\\nCopy one of the tables there. You get an error in fixupInsertion\\n\\n[Error] TypeError: 'undefined' is not an object (evaluating 'source.clone')\\n\\tcopy (load.php, line 94)\\n\\tgetClonedElement (load.php, line 39)\\n\\tfixupInsertion (load.php, line 120)\\n\\tfixupInsertion (load.php, line 119)\\n\\tnewFromDocumentInsertion (load.php, line 71)\\n\\tafterPaste (load.php, line 299)\\n\\t(anonymous function) (load.php, line 294)\\n\\tproxy (load.php, line 10)\\n\\nThis does not seem related to bug 58318. The table also doesn't render as it should in the original surface, with slugs above and below it inside the table. Possibly caused by the usage of templates for row construction.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404172527, 'spacePHID': None, 'dateCreated': 1386843540, 'dateModified': 1443278215, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58387', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Clear formatting\" should never be highlighted', 'description': {'raw': 'I\\'m not sure if this was done on purpose, but when selecting text containing some formatting in some or all of the selected text (e.g. part of a link and some text after it, or part of a bolded string) the toolbar shows the \"Clear formatting\" button highlighted (similarly to how the \"Bold\" icon is highlighted when selecting bolded text).\\n\\nThe toolbar is supposed to reflect current state of selected text. Showing the \"Clear formatting\" button already activated seems like an impossible state (it would theoretically mean some hypothetical \"clear\" annotation is applied to the selected text, which is incorrect. The only case in which that would technically be correct is if you apply text that is already cleared of formatting).\\n\\nThis highlighting for the \"Clear formatting\" button is confusing from a UX point of view. I would associate it with how \"bold\" is highlighted when bolding is applied.\\n\\nWhen encountering this strange UX behaviour earlier today, it took me a while to figure out what it is supposed to mean (longer than it should for an intuitive editor). I don\\'t think this is because I\\'m familiar with VisualEditor\\'s previous state, but more in general.\\n\\nI think the correct approach would be to never highlight the clear formatting button in the toolbar, and have it be an \"apply\" button, you select text, and then activate (not deactivate) \"clear formatting\".\\n\\nThis concept also exists in other popular editors.\\n\\nAlternatively, though that would be a new concept for people to learn, perhaps change the icon to something that means the opposite of no formatting, so that it being turned on for selected text, and being able deactivate it, like it currently does, actually makes sense as an action take.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402332266, 'spacePHID': None, 'dateCreated': 1386821400, 'dateModified': 1443276329, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58371', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: Create a separate preference for the Visual Editor (opt-in/out) for Flow pages', 'description': {'raw': 'VisualEditor is currently not usable or well-tested in Flow. (Per feedback at http://ee-flow.wmflabs.org/w/index.php?title=Talk:Flow_bugs&workflow=050a7c69647ff00fc8b1fa163e68c4ac&action=view)\\n\\nPlease create a separate preference (opt-in/out) for the VisualEditor within Flow pages, so that editors who are happily using/testing VE, will still be able to use Flow.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409847331, 'spacePHID': None, 'dateCreated': 1386101640, 'dateModified': 1409847331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57949', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add ability to edit local language links (non-Wikidata ones)', 'description': {'raw': 'Though bug 52105 covers Wikidata-bourne language link editing, there are cases where local language link editing is still needed:\\n\\n* for Wikimedia wikis not (yet) hooked into Wikidata;\\n* for Wikimedia wikis which cannot (yet) be hooked into Wikidata (e.g. [[en:Maggie Simpson]] vs. [[de:Die Simpsons (Familie)#Maggie Simpson]]); and \\n* for MediaWiki installs without a Wikibase server (almost all third party users).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52105'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1386087840, 'dateModified': 1643973209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57929', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Global, better URL to citation conversion functionality', 'description': {'raw': '**Author:** `vladjohn2013`\\n\\n**Description:**\\nGlobal, better URL to citation conversion functionality\\n\\nSuppose, in Wikipedia, all that needed to be done to generate a perfect citation was to provide a URL? That would be a tremendous step toward getting a much higher percentage of text in Wikipedia articles to be supported by inline citations.\\n\\nThere are already expanders (for the English Wikipedia, at least) that will convert an ISBN, DOI, or PMID, supplied by an editor, into a full, correct citation (footnote). These are in the process of being incorporated into the reference dialog of the VisualEditor extension, making it almost trivial (two clicks, paste, two clicks) to insert a reference.\\n\\nFor web pages, however, the existing functionality seems to be limited to a Firefox add-on. Its limits, besides the obvious requirement to use that browser (and to install the add-on), include an inability to extract the author and date from even the most standard pages (e.g., New York Times), and the lack of integration with MediaWiki.\\n\\nFor a similar approach, using a different plug-in/program, see this Wikipedia page about Zotero.\\n\\nA full URL-to-citation engine would use the existing Cite4Wiki (Firefox add-on) code, perhaps, plus (unless these exist elsewhere) source-specific parameter specifications. For example, the NYT uses \"<meta name=\"author\" content=\"NICK BILTON\" />\" for its author information; that format would be known by the engine (via a specifications database). Each Wikipedia community would be responsible for coding these (except for a small starter set, as examples), in the way that communities are responsible for TemplateData for the new VisualEditor extension.\\n\\n(Project idea suggested by John Broughton.)\\n\\nURL:https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Global.2C_better_URL_to_citation_conversion_functionality\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1423649593, 'spacePHID': None, 'dateCreated': 1385913900, 'dateModified': 1433425288, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57804', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  The category tool should automatically strip the namespace \"Category:\" out of the cat name, if the editor types it in', 'description': {'raw': 'Intention:\\nAdd a category to a page\\n\\nSteps to Reproduce:\\n1. Open the page in VisualEditor and choose the categories tool.\\n2. Type the full name of the category, including the namespace:  Category:Example\\n\\n\\nActual Results:  \\nVisualEditor adds a non-existent, malformed category named [[Category:Category:Example]].\\n\\nExpected Results:  \\nThat VisualEditor would recognize that \"Category:Example\" already contained the namespace, and thus omit the duplication.  Ideally, at non-English wikis, it would recognize and remove both the local name for the namespace and the English name, since both are typically valid (e.g., strip out both \"Kategorie\" and \"Category\" at the German Wikipedia).\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1385856300, 'dateModified': 1643973209, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57786', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Wikitext warning needs to be updated to refer to switching to wikitext editor without losing unsaved changes', 'description': {'raw': 'Intention:\\nThe wikitext warning says:\\n\\n\"Click \"Edit source\" to edit the page in wikitext mode – unsaved changes will be lost.\"\\n\\nThis need to be changed to reference the new ability to switch to the source editor without losing unsaved changes, at least (currently) for non-Firefox users.\\n\\n\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57699'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400523785, 'spacePHID': None, 'dateCreated': 1385604180, 'dateModified': 1443278216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57700', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Beta warning should say that you can switch to wikitext without unsaved changes being lost', 'description': {'raw': 'Intention:\\nWhen you open VisualEditor for the first time, you get a message that says you can switch to wikitext, but that unsaved changes will be lost:\\n\\n\"You can keep using the wikitext editor by clicking the \"Edit source\" tab instead – unsaved changes will be lost.\"\\n\\nThis is not always true, since (currently for non-Firefox users) it is possible to switch to wikitext using the new menu item without losing any changes.\\n\\n\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57462\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57700'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400523798, 'spacePHID': None, 'dateCreated': 1385604120, 'dateModified': 1443278218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57699', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Features not yet available in a certain browser (but working in others) should be grayed out/unselectable', 'description': {'raw': 'Pretty much what the title says.\\nJames thinks this might eventually be done at some point, so this is a reminder.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1718626285, 'spacePHID': None, 'dateCreated': 1385499300, 'dateModified': 1718626285, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57621', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make jquery.byteLimit more user friendly and cleaner in usage', 'description': {'raw': \"Currently:\\n\\n* byteLimit() will internally do all kinds of event binding to get notice of changes.\\n* We have our own 'change' callback for InputWidget elements.\\n* in mw.ViewPageTarget we use our 'change' event, our own getValue, manually run it through byteLength (not byteLimit), in order to get the current length that we assume byteLimit got to as well.\\n* When the length is exceeded by user input, byteLImit internally will start chopping off characters (or rather, cancel user events after it hit the limit, and falls back to chopping off characters until it fits again).\\n\\nProblems:\\n* Mimics the change event.\\n* Duplicates logic for byteLength outside byteLimit, this will fail if the logic changes, and already fails if the byteLimit has a filter callback.\\n\\nIdeally: byteLimit (standalone)\\n* Its own on('change') - so we don't have to mimic it\\n* Ability to retrieve byte length as perceived by byteLimit - so we don't have to reverse engineer it\\n* Option to disable the chopping off (instead, more like Twitter where the underlying user interface element will allow new characters, but it will have an event like 'length-exceeded' and 'length-satisfied' or 'length-recovered' so we dan display a nicer user interface (e.g. make the number negative and red)\\n\\n\\nor:\\n\\nIdeally: byteLimit (utility mixin)\\n* Option to feed it change events instead of having it listen on its own.\\n* Get back from each event – the current state (length exceeded or not, and what the length is, having taken the filter in account).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1554174106, 'spacePHID': None, 'dateCreated': 1385472600, 'dateModified': 1554174106, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57587', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fire a hook before the page is saved', 'description': {'raw': \"Some Wikipedias have hooks for the source editor that process the wikitext before it is saved. The only thing to currently do this for the Visual Editor seems to be to hook in the 'wikipage.content' event and do an API edit that processes the text as intended.\\n\\nInstead, the visual editor should offer a different event, such as visualeditor.beforesave, that would allow such processing to take place when saving the content.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-2trxtywh5ma4onasf4kq', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397675923, 'spacePHID': None, 'dateCreated': 1385385360, 'dateModified': 1443657637, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57536', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Offer to retain changes when switching to the \"Edit Source\" tab', 'description': {'raw': 'When a user clicks on Switch to source editing option from the settings drop down it tells user that switching to source editing will keep the changes made in the document.But if a user attempts to switch from the tab it does not retain those changes.This seemed confusing to me because when user uses the \"switch to source editing\" , the \"Edit Source\" tab is selected ,indicating the same destination for both action.\\n\\nIf a user can switch to source editing in multiple ways, i think it is better both ways have similar mechanism of handling the changes to have uniform experience.\\nSpecially when switching from tab is one click away compared to the \"[]switch to source editing\" option.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57699\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=42141'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404177141, 'spacePHID': None, 'dateCreated': 1385165520, 'dateModified': 1443278218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57462', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: MWExtensionNode preview (<math>, <syntaxhighlight>, …) double-escapes HTML (angle brackets, ampersands)', 'description': {'raw': 'Repro:\\n\\n1. Create a page with text below:\\n\\n<math>\\n\\\\begin{matrix}\\nx & y \\\\\\\\\\nz & v\\n\\\\end{matrix}\\n</math>\\n\\n2. Default rendering, in PHP parser and Parsoid (VE initial state):\\n\\nx y\\nz v\\n\\n3. VE edit this matrix, change v to uv.\\n\\n4. Edited block becomes:\\n\\nx amp; y\\nz amp; uv\\n\\n(After saving it works fine)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54577'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405463766, 'spacePHID': None, 'dateCreated': 1385141220, 'dateModified': 1443278218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: <visualeditor-dialog-beta-welcome-content> does not mention new switch to wikicode feature', 'description': {'raw': \"**Author:** `raincity471`\\n\\n**Description:**\\nReproducible: Didn't try\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385136050, 'spacePHID': None, 'dateCreated': 1385125920, 'dateModified': 1385136050, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57422', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adjacent floating tables are offset by vertical space because of intervening <span>', 'description': {'raw': 'Reproducible: Always\\n\\nFram reports that when you try to VEdit pages like\\nhttps://en.wikipedia.org/wiki/List_of_top_100_Major_League_Baseball_strikeout_pitchers\\nhttps://en.wikipedia.org/wiki/List_of_Major_League_Baseball_players_with_2,500_games_played\\nor https://en.wikipedia.org/wiki/List_of_top_300_Major_League_Baseball_home_run_hitters ,\\nwhat you get is not exactly what you saw :) (see the tables and the following sections.)\\n\\nSsastry furtherly diagnosticated: \"Looks like some VE-clientside rendering issues with empty spans between multiple floating tables.\"\\nDoesn\\'t look specific to a browser or skin.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65249'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701962446, 'spacePHID': None, 'dateCreated': 1385068980, 'dateModified': 1701962446, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57372', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor on svwiktionary', 'description': {'raw': 'We would like to have VisualEditor enabled on some part of svwiktionary.\\n\\nSuggested namespace: User namespace.\\n\\nRationale:\\n\\nWe\\'re doing a proof-reading project[1] where we\\'ll need to do lots of style edits (mainly update italics and bold).\\n\\nThe idea is to extract useful information from the dictionary/thesaurus \"Ord för ord\"[2] and create new entries and improve existing ones using the information.\\n\\n\\n[1] https://sv.wiktionary.org/wiki/Wiktionary:Projekt/Ord_f%C3%B6r_ord\\n[2] http://runeberg.org/ordforord/\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-pwsgofaoir7tnszvfzqi', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386126509, 'spacePHID': None, 'dateCreated': 1385045940, 'dateModified': 1397521192, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57356', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Long links are not shown in full in the link searcher', 'description': {'raw': 'When a long string (24 characters or more) gets added in the link tool (a typical long URL, or a just a long article title), the external and internal link options get shortened with \"...\" in the middle. This can make it hard to know whether you put in the right string or not, and there doesn\\'t seem to be much downside to displaying the full link targets for at least moderately longer strings.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=69574'}, 'authorPHID': 'PHID-USER-nyv6rqxnzdy3oe323a3d', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1384795860, 'dateModified': 1441911419, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57200', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Unclosed strikethrough tag makes strikethrough formatting continue throughout page', 'description': {'raw': 'On this page [1], the \"Open questions\" section ends with a line that has starts with <s> but later has another <s> instead of </s>. The strikethrough ends with the second tag anyway, when the page is being viewed normally. With VisualEditor, however, the strikethrough formatting continues to the end of the page.\\n\\n[1] = https://www.mediawiki.org/w/index.php?title=Wikipedia_Education_Program&oldid=821826\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-nyv6rqxnzdy3oe323a3d', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1513635570, 'spacePHID': None, 'dateCreated': 1384790520, 'dateModified': 1513635570, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57196', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __STATICREDIRECT__ status in the page metadata panel', 'description': {'raw': 'Checkbox flag, redirect pages only.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392349774, 'spacePHID': None, 'dateCreated': 1384754820, 'dateModified': 1443276340, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57173', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __NOTITLECONVERT__ (and __NOTC__) status in the page metadata panel', 'description': {'raw': 'Checkbox flag, pages on variant wikis only.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398124377, 'spacePHID': None, 'dateCreated': 1384754580, 'dateModified': 1443276340, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57172', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __NOCONTENTCONVERT__ (and __NOCC__) status in the page metadata panel', 'description': {'raw': 'Checkbox flag, pages on variant wikis only.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398124361, 'spacePHID': None, 'dateCreated': 1384754580, 'dateModified': 1443276341, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57171', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __NOGALLERY__ status in the page metadata panel', 'description': {'raw': 'Checkbox flag, category namespace only.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398124338, 'spacePHID': None, 'dateCreated': 1384754520, 'dateModified': 1443276344, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57169', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __NEWEDITSECTION__ and __NONEWEDITSECTION__ status in the page metadata panel', 'description': {'raw': 'Trinary state (default, NEWEDITSECTION, NONEWEDITSECTION), all pages.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392879733, 'spacePHID': None, 'dateCreated': 1384754340, 'dateModified': 1443276344, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57168', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __INDEX__ and __NOINDEX__ status in the page metadata panel', 'description': {'raw': 'Trinary state (default, INDEX, NOINDEX), all pages.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392862666, 'spacePHID': None, 'dateCreated': 1384754220, 'dateModified': 1443276345, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57167', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __NOEDITSECTION__ status in the page metadata panel', 'description': {'raw': 'Checkbox flag on/off, all pages.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389062932, 'spacePHID': None, 'dateCreated': 1384754160, 'dateModified': 1443276347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57166', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Image searched for does not come back in results but does exist on server', 'description': {'raw': '**Author:** `anjana1`\\n\\n**Description:**\\nOS: Win 8\\nBrowser: Fire Fox 24 and Chrome 31.0\\n\\nNot able to insert an image in VE mode on Beta. The image (A nice pic.jpg) which is on commons is not seen in the list while trying to upload it using the \"Media\" in the toolbar (found in \"More\" pulldown menu)in \"Edit Beta mode\".\\n\\nThe same image is uploadable using wikitext syntax [[File:A Nice pic.jpg]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**Whiteboard**: cirrus-fixed'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399315766, 'spacePHID': None, 'dateCreated': 1384575840, 'dateModified': 1399315766, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57130', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: External links that point to the local wiki should be changed into internal links, not interwikis', 'description': {'raw': 'Reported by Mattho69 on frwiki [1].\\n\\nIf I try to add a link to a Wikipedia article using its full form (http://fr.wikipedia/org/wiki/…), it is saved as an interwiki (see [2]) instead of a local wikilink. \\n\\nI notice that it only happens with HTTP links, not with HTTPS ones (see [3]), which are not converted (maybe separate bug ?).\\n\\n[1] https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%89diteurVisuel/Avis#:fr:\\n[2] https://fr.wikipedia.org/w/index.php?title=Utilisateur:Ltrlg/tests&diff=98243431&oldid=98197987\\n[3] https://fr.wikipedia.org/w/index.php?title=Utilisateur:Ltrlg/tests&diff=98243523&oldid=98243431\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=45209\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=61672'}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397764105, 'spacePHID': None, 'dateCreated': 1384363680, 'dateModified': 1417572484, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57019', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Improve message for parameters that have no TemplateData (say \"undocumented\" instead of \"unknown\")', 'description': {'raw': 'When adding parameters of some templates like this:\\nhttps://cs.wikipedia.org/wiki/%C5%A0ablona:Citace_elektronick%C3%A9_monografie\\n it sais \"unknown parametr\" even the parametr is valid and works afterwords. \\n\\nThis information is confusing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1384164360, 'dateModified': 1655745711, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56889', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Appending to a line shows additions before end of line in diff', 'description': {'raw': 'Steps to reproduce:\\n1. Find a page that already has a category\\n2. Edit in VE, and add a category\\n3. Review changes\\n\\nExpected results:\\nThe diff is\\n```\\n+**[[Category:New cat]]**\\n```\\n\\nActual results:\\nThe diff is\\n```\\n-[[Category:Old cat]]\\n+[[Category:Old cat**]][[Category:New cat**]]\\n```\\nWith the chunk between the stars viewed as added.\\n\\nThis also happens in the source editor, but it is less common that people will append a category to an existing category as that is against all style guidelines.  However the Visual Editor is doing just that.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1565560030, 'spacePHID': None, 'dateCreated': 1384146180, 'dateModified': 1565560031, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56880', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit other behavioural flags in the page metadata panel', 'description': {'raw': 'Checkboxes (disabled for some/most namespaces), setting:\\n\\n__NEWSECTIONLINK__\\n  <meta property=\"mw:PageProp/newsectionlink\">\\n\\n__NONEWSECTIONLINK__\\n  <meta property=\"mw:PageProp/nonewsectionlink\">\\n\\n__NOGALLERY__\\n  <meta property=\"mw:PageProp/nogallery\">\\n\\n__HIDDENCAT__\\n  <meta property=\"mw:PageProp/hiddencat\">\\n\\n__NOCONTENTCONVERT__\\n  <meta property=\"mw:PageProp/nocontentconvert\">\\n\\n__NOCC__\\n  <meta property=\"mw:PageProp/nocc\">\\n\\n__NOTITLECONVERT__\\n  <meta property=\"mw:PageProp/notitleconvert\">\\n\\n__NOTC__\\n  <meta property=\"mw:PageProp/notitleconvert\">\\n\\n__NOEDITSECTION__\\n  <meta property=\"mw:PageProp/noeditsection\">\\n\\n__NOINDEX__\\n  <meta property=\"mw:PageProp/noindex\">\\n\\n__INDEX__\\n  <meta property=\"mw:PageProp/index\">\\n\\n__STATICREDIRECT__\\n  <meta property=\"mw:PageProp/staticredirect\">\\n\\n… and possibly others.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384755174, 'spacePHID': None, 'dateCreated': 1384101720, 'dateModified': 1417572754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56869', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow users to set/edit __FORCETOC__ status in the page metadata panel', 'description': {'raw': 'A checkbox, greyed out when there are more than 2 headings(?), setting:\\n\\n  <meta property=\"mw:PageProp/forcetoc\">\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388918601, 'spacePHID': None, 'dateCreated': 1384101180, 'dateModified': 1443276347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56867', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: VE should hide PageTriage bar on edit if it's visible on the page\", 'description': {'raw': 'PageTriage UI editing User page\\n\\nseen on beta enwiki:\\n\\n* log in as a user with PageTriage privileges e.g. Selenium_user\\n* visit http://en.wikipedia.beta.wmflabs.org/wiki/Special:NewPagesFeed\\n* visit your user page\\n\\nPageTriage UI appears\\n\\nPageTriage UI should not appear on User pages\\nPageTriage UI should not appear in the editor\\n\\nsee screen shot\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F12047}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1400108749, 'spacePHID': None, 'dateCreated': 1383850080, 'dateModified': 1443278222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56731', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: Agora CSS issues in IE8', 'description': {'raw': 'I visited a Flow page in IE8, which is 8% of WMF audience according to https://www.mediawiki.org/wiki/VisualEditor/Target_browser_matrix (and more elsewhere I think).\\n\\nScreenshot https://saucelabs.com/jobs/2a2680aeb681420381a5652ddf5fdca2/0001screenshot.png?auth=fc4f7362b9615cfceee0744b0f4bc93a\\n\\nThere are issues with Flow\\'s local Agora CSS override in IE8:\\n* Gray backgrounds on secondary buttons (they should appear without any button border).\\n* Buttons aren\\'t rounded.\\n* Thank icon goes away on mouseover.\\n* \"Start a new topic\" text field and textarea both have no blue bar on focus.\\n* Textarea has no placeholder (see http://www.jacklmoore.com/notes/form-placeholder-text/ ,also there\\'s a jquery.placeholder in core, and Matt Flaschen had a placeholder patch for Login forms).\\n* Green [Add topic] button text looks poor.\\n\\nFor now this is a Flow bug, but at some point a version of this CSS will migrate to core (bug 54360).  https://gerrit.wikimedia.org/r/#/c/93584 may already have relevant LESS workarounds.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n**URL**: http://ee-flow.wmflabs.org/wiki/User_talk:Spage'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1523277647, 'spacePHID': None, 'dateCreated': 1383785580, 'dateModified': 1523277647, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow must respect the per-wiki VE opt-in/out configuration', 'description': {'raw': 'VE on beta labs and on prod is opt-in, but VE on test2wiki/mw.o is enabled by default for everyone, including anons. Flow must appropriatly offer VE as configured by the wiki.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-r5pzlcquei6f4hb53rfg', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390958988, 'spacePHID': None, 'dateCreated': 1383758160, 'dateModified': 1418984831, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56680', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Hover effect inconsistent for Help icon', 'description': {'raw': 'Noticed on mediawiki.org, currently at 1.23wmf2 (88c7b3f)\\n\\nOn hover, the Help icon in the VisualEditor toolbar gets both the light gray border with all corners rounded, and the darker gray border that, if I look at the Menu icon for reference, should probably only appear when the button is pressed, not just hovered.\\n\\nFurthermore, the dark gray border only has the left corners rounded.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1562866095, 'spacePHID': None, 'dateCreated': 1383656340, 'dateModified': 1562866095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56617', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Show deprecation notices when accessing wg* JavaScript globals', 'description': {'raw': 'As the preferred way to access the `wg*` variables in JavaScript is to use mw.config.get()/.set(), accessing them as globals (i.e. as members of window) should show deprecation notices in debug mode, just like it is done for the functions from wikibits.js.'}, 'authorPHID': 'PHID-USER-tyjmn7xcw6s2b6rqagj7', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1420428214, 'spacePHID': None, 'dateCreated': 1383558360, 'dateModified': 1421104581, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56550', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: unintended ref change resulting in a dirty diff', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Guilt_(emotion)&diff=579908396&oldid=576819947\\n\\nI only intended to edit the \"See also\" section. VisualEditor edited a <ref> without my knowledge or consent.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1429226414, 'spacePHID': None, 'dateCreated': 1383422400, 'dateModified': 1438734463, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56520', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Faked keys don't trigger triggers\", 'description': {'raw': 'If you\\'re not pressing a \"\\\\\" key, OO\\'s trigger doesn\\'t see a \"\\\\\" key being pressed. This includes if you magically simulate a \"\\\\\" key with another key combination, like \"AltGr + 8\" on French keyboards. Should we support that?\\n\\nSplit from bug 53682.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1383283800, 'dateModified': 1643973212, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56452', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add advanced user option to review diff post-VisualEditor edit and easily report an issue', 'description': {'raw': 'I want to be able to test and give feedback for VisualEditor, so I\\'ve opted in on the English Wikipedia.\\n\\nVisualEditor has bugs, but identifying bugs caused in your own edits can be annoying.\\n\\nWhen I make an edit using VisualEditor, I want to be able to verify the edit (double-check VisualEditor\\'s behavior) by viewing a diff of the changes. (Unlike when I\\'m editing wikitext, where I\\'ll only preview and not use \"show changes\" to view a diff.) Clicking \"Review your edits\" in VisualEditor\\'s user interface is tedious and interrupts my workflow.\\n\\nIt might be nice to implement showing the diff post-save for advanced users who simply want to be able to report an issue with VisualEditor. Or perhaps we could restore the previous behavior where a diff was automatically shown. This is an advanced user option, so it could be JavaScript config or similar. It should not be a user preference or anything that\\'s user-facing. This feature would hopefully make reporting issues easier: rather than needing to request a diff from VisualEditor or navigate to the page history to check a diff link there, you would simply be presented with a diff.\\n\\nIn addition, if we\\'re implementing an advanced user auto-diff option, perhaps we can also add a \"report an issue\" link to more easily file a bug? (Or search for relevant bugs.)\\n\\nFiling as a Sunday afternoon thought.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1696087493, 'spacePHID': None, 'dateCreated': 1382894520, 'dateModified': 1696087493, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56221', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikitext warning not triggered when editing image captions, references', 'description': {'raw': 'Wikitext added to image captions is nowikied in the same way that markup added to the page body is. e.g. https://en.wikipedia.org/w/index.php?title=User%3AThryduulf%2Fsandbox&diff=578947711&oldid=574091986 however the wikitext warning is not generated.\\n\\nTo reproduce:\\n1. Load any page with an image in VE\\n2. Edit the image caption\\n3. Add any wiki markup in the caption (tested with bold, italic and links)\\n\\nExpected behaviour: The wikitext warning pops up.\\nAction behaviour: Nothing happens\\n\\nIf popping up the warning while in the image caption dialog is not possible, then it should do so immediately the dialog is closed. Displaying it at the same time would be preferable though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53839'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403125259, 'spacePHID': None, 'dateCreated': 1382877060, 'dateModified': 1443278223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56213', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Re-phrase message \"Visualeditor-preference-enable\" to not specify namespaces.', 'description': {'raw': 'Please rephrase the message \"Visualeditor-preference-enable\". Currently it says: \"Enable VisualEditor (only in the main and user namespaces)\"\\n\\nWith https://gerrit.wikimedia.org/r/#/c/90923/ the VE was enabled in NS_FILE, NS_HELP, NS_CATEGORY namespaces too.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382982325, 'spacePHID': None, 'dateCreated': 1382807280, 'dateModified': 1417572746, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56205', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove unused CSS classes', 'description': {'raw': \"For instance, there's a rule for .oo-ui-toolbar-bottom but no code adding that class to anything.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1382592120, 'dateModified': 1643973213, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56078', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Down-arrow in a slug with a <br> in it puts cursor inside slug rather than moving down or right in Firefox', 'description': {'raw': \"see page \\n\\nhttps://test2.wikipedia.org/wiki/User:Selenium_user/cursor_test_page2?veaction=edit\\n\\nIn Chrome, hit down-arrow 3 times to get to the line that begins with text 'Invisible'\\n\\nIn Firefox, it takes 4 times hitting down-arrow to get to that line.  The first time hitting down-arrow does nothing\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1423751013, 'spacePHID': None, 'dateCreated': 1382561640, 'dateModified': 1438734469, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56068', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove dual-type support for categories and language links', 'description': {'raw': \"Per https://gerrit.wikimedia.org/r/#/c/90339/ we should remove the dual-type support once it's been long enough since Parsoid has renamed the types.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386368117, 'spacePHID': None, 'dateCreated': 1382468760, 'dateModified': 1417572740, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56009', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE blanks syntax-highlight extension block after editing contents with \"<>\" popup', 'description': {'raw': 'screenshot\\n\\nVE blanks syntax-highlight extension block after editing contents with \"<>\" popup. :(\\n\\nIf you open the popup back up the source is there, but the preview in the editor is empty.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/Manual:CORS?veaction=edit\\n\\n**Attached**: {F12120}'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411404775, 'spacePHID': None, 'dateCreated': 1382271180, 'dateModified': 1417571836, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55935', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: veaction=edit should invoke VE irrespective of user prefs', 'description': {'raw': 'On English Wikipedia, the VE is now not offered for anons & people who have not enabled a user pref.\\n\\nHowever if the user loads a URL that invokes VE (i.e. includes ?veaction=edit), it would be nice if VE loaded irrespective of user preferences.  If ?veaction=edit in the URL isnt explicit enough to bypass some checks, ?veaction=edit&debug=true should just do it.\\n\\nThat would streamline testing in many browsers, as we wouldnt need to log in on each browser - which is a bugger because logging into a second browser causes the first browser to be logged out.(bug 49890)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51765\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=19415'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386028150, 'spacePHID': None, 'dateCreated': 1382133000, 'dateModified': 1417572678, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55900', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When indenting a list as a block, instead of putting it inside its own type, use <dl><dd>s', 'description': {'raw': 'example of a number list attempting to be indented\\n\\nThis may be similar to https://bugzilla.wikimedia.org/show_bug.cgi?id=48010\\n\\nIn the VisualEditor, entire lists cannot be indented. For example, to get an entire list to appear slightly indented, a user would type in wikitext:\\n\\n:* First\\n:** First sub one\\n:** First sub two\\n:** First sub three\\n:* Second\\n:** Second sub one...\\n\\nWhereas the VisualEditor is attempting to enter this wikitext:\\n\\n** First\\n*** First sub one\\n*** First sub two\\n*** First sub three\\n** Second\\n*** Second sub one...\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F12745}'}, 'authorPHID': 'PHID-USER-2mvmxqtefj5cyyzm7jks', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1381942020, 'dateModified': 1721164816, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55797', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding an image at the top of a list puts the image inside the list', 'description': {'raw': \"=Steps to reproduce=\\nStart with a section whose contents are: \\n```\\n ==Heading==\\n * Alice\\n * Bob\\n * Chris\\n```\\nPlace the cursor just before the 'A' in 'Alice' and insert an image.\\n\\nThe image will be placed inside the first list item:\\n```\\n==Heading==\\n* [[File:Example.jpg]]Alice\\n* Bob\\n* Chris\\n```\\n\\nEditors almost never place images inside list items so they are likely to expect this to produce the following wikitext instead:\\n```\\n==Heading==\\n[[File:Example.jpg]]\\n* Alice\\n* Bob\\n* Chris\\n```\\n\\nSee https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox&diff=577354576&oldid=577352415 for an example (look for the image of the apple).\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1381880400, 'dateModified': 1503703150, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55767', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Don't encourage users to set a group for reference lists (as that's only rarely used)\", 'description': {'raw': 'Maybe I havent understood, but I think it is not necessary to push user to add group to Reference list. Most of the references are used as a references. Other groups may be insert as an option. If you force it, it blocks to add references.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392860457, 'spacePHID': None, 'dateCreated': 1381816620, 'dateModified': 1443276356, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55725', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'No paragraphs/linebreaks in references by inserting empty lines', 'description': {'raw': 'In the software at Wikisource it not possible to have paragraphs (by inserting empty lines) in references similar to the normal text. See: https://en.wikisource.org/wiki/User:Aschroet/test. In the normal HTML view the empty lines are just ignored and only one text block is shown. Even more interesting is the behavior in case when the text is exported by \"Download as PDF\". There, the paragraphs are created but not in a correct way.\\n\\nThe usage of <nowiki><p></nowiki> helps for the HTML view but not for PDF. The usage if <nowiki><br /></nowiki> works but does not generate real paragraphs but only newline in HTML and PDF.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-nrfhx7zwxqc7nau5uyyz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1381677300, 'dateModified': 1680049037, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55674', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Broken link creation workflow', 'description': {'raw': \"I'm not sure exactly how I cause this bug but I've seen it twice now.\\n\\nWorks somewhat like this:\\nClick anywhere in the textarea and ensure there is whitespace before the cursor and nothing highlighted.\\n\\nClick the link button\\nenter text, save it.\\n\\nThe link doesn't get added anywhere and now clicking the link button to create a new link has no effect.\\n\\nI get JavaScript exception:\\nUncaught Error: Offset could not be translated to a DOM element and offset: 6306\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396470649, 'spacePHID': None, 'dateCreated': 1381361640, 'dateModified': 1417572495, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55540', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: SyntaxHighligherGeSHi: Bug in Converter throws \"Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.\"', 'description': {'raw': 'On editing a page on mediawiki.org\\n\\nNavigated to\\nhttps://www.mediawiki.org/wiki/Manual:Coding_conventions/CSS?veaction=edit#Less\\n\\nLooking in the console I see:\\nUncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist. \\n\\nThe save button is disabled.\\nI only noticed this after doing a long edit :(\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**URL**: https://www.mediawiki.org/wiki/Manual:Coding_conventions/CSS?veaction=edit'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'bug', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1381190760, 'dateModified': 1644961164, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55453', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up phantom mouse event code in ve.ce.ProtectedNode', 'description': {'raw': \"Currently, the mouse event handling in phantoms is:\\n```lang=js\\n// mouseenter on the protectednode\\nve.ce.ProtectedNode.prototype.onProtectedMouseEnter = function () {\\n\\tif ( !this.root.getSurface().dragging ) {\\n\\t\\tthis.createPhantoms();\\n\\t}\\n};\\n\\n// mousemove on the surface, bound by createPhantoms and unbound by clearPhantoms\\nve.ce.ProtectedNode.prototype.onSurfaceMouseMove = function ( e ) {\\n\\tvar $target = $( e.target );\\n\\tif (\\n\\t\\t!$target.hasClass( 've-ce-protectedNode-phantom' ) &&\\n\\t\\t$target.closest( '.ve-ce-protectedNode' ).length === 0\\n\\t) {\\n\\t\\tthis.clearPhantoms();\\n\\t}\\n};\\n\\n// mouseout on the surface, bound by createPhantoms and unbound by clearPhantoms\\nve.ce.ProtectedNode.prototype.onSurfaceMouseOut = function ( e ) {\\n\\tif ( e.toElement === null ) {\\n\\t\\tthis.clearPhantoms();\\n\\t}\\n};\\n```\\nIssues:\\n* the mousemove handler seems to permit moving the mouse directly to a different ProtectedNode without causing the phantoms to be cleared\\n* the mouseout handler uses e.toElement, which is a poorly documented property that's allegedly IE-only\\n* it's generally very difficult to reason about what this code does or convince oneself that it does something reasonable\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701813910, 'spacePHID': None, 'dateCreated': 1381185960, 'dateModified': 1701813910, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55448', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Call the \"transclusion\" dialog a \"template\" dialog (in the toolbar and elsewhere), even though it lets you add non-template transclusions', 'description': {'raw': \"Right now the way that you add a template through the VisualEditor is by choosing the Transclusion option from the toolbar.\\n\\n'Transclusion' is programmer jargon. Regular people have no idea what that means. 'Template' is a somewhat ambiguous term, but at least it matches all of our documentation and the name of the namespace. It is also less scary sounding.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398700163, 'spacePHID': None, 'dateCreated': 1381170240, 'dateModified': 1443276356, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55434', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikitext diff is not regenerated if VE content is the same but the page has subsequently changed', 'description': {'raw': '+++ This bug was initially created as a clone of Bug #55392 +++\\n\\nVE caches the diff, which means if no content is changed, the user is shown\\na) a stale diff and is allowed to proceed with saving the page, which means they are then\\nb) the page with their saved changes only\\nThe user is unaware that they have overwritten another persons changes.\\n\\nSteps to reproduce:\\n1. Create a page with some two lines\\n   https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=573748285\\n2. Open the page in two VE windows\\n3. In the second window, alter the first line and save\\n   https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=576079696\\n5. In the first window, alter the first line and review changes\\n   (the diff only shows the first line being modified\\n    against the page contents from step 3)\\n6. In the second window, add some lines and save\\n   https://en.wikipedia.org/w/index.php?title=User:John_Vandenberg/test&oldid=576079807\\n7. In the first window, review changes, and cancel the save\\n   (the diff is the same as in step 5; the VE page content doesnt change)\\n8. In the first window, save\\n\\nExpected results:\\nIn step 7, the diff should be refreshed even though the page content has not been modified.\\n\\nActual results:\\nThe diff from step 5 is displayed in step 7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=55392'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1381115640, 'dateModified': 1416845753, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55393', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The link suggestor should suggest links from the current namespace ahead of named links', 'description': {'raw': \"If the user is editing a content namespace, the link dialog should search the current namespace first, then all other content namespaces, when looking for link targets.\\n\\nSteps to reproduce\\n1. https://www.mediawiki.org/wiki/Manual:Page_table?veaction=edit\\n2. Write and select 'archive table'\\n3. Open link dialog\\n\\nExpected results:\\nLink target 'manual:archive table' automatically found\\n\\nActual results:\\nLink target 'archive table' (new page) is automatically provided\\n\\nThe same is needed for Wikisource which has, e.g. an Author: content namespace.\\n\\nWikipedias with a content namespace listed in InitialiseSettings.php:\\nArabic Wikipedia : T22623\\n  https://ar.wikipedia.org/wiki/%D8%AE%D8%A7%D8%B5:%D9%81%D9%87%D8%B1%D8%B3_%D8%A8%D8%A7%D8%AF%D8%A6%D8%A9/%D9%85%D9%84%D8%AD%D9%82:\\nSpanish Wikipedia : T41866\\n  https://es.wikipedia.org/wiki/Especial:P%C3%A1ginasPorPrefijo/Anexo:\\nNorth Frisian Wikipedia: T40023\\n  (Wikisource inside Wikipedia)\\nCroatian Wikipedia: T42732\\n  https://hr.wikipedia.org/wiki/Posebno:Prefiks_indeks/Dodatak:\\nPortuguese Wikipedia:\\n  https://pt.wikipedia.org/wiki/Especial:%C3%8Dndice_por_prefixo/Anexo:\\n\\n(and more potential ones listed at T41866)\\n\\nAs an aside, in 'Help' namespace, which isnt set as a content namespace, it would be nice to search within that namespace when linking, but that is a more blurry line.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T71780}\\n{T57390}\\n{T64917}\\n{T71716}\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1381111920, 'dateModified': 1643973214, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55390', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserted objects (references, templates, images) should not be selected after insertion', 'description': {'raw': '**Author:** `Wikifram`\\n\\n**Description:**\\nWhen you add a reference, it is automatically selected (blue), instead of having the cursor positioned directly after it (or better still, with a space after the ref and the cursor after that). The effec is that if you enter a ref and then start typing (which is rather normal editing behaviour), your ref immediately gets removed (overwritten) again, which makes it rather pointless. \\n\\nI think that it is much more often the intention to continue typing after adding a ref, than to have it highlighted, so please change the default behaviour.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386793449, 'spacePHID': None, 'dateCreated': 1380869940, 'dateModified': 1417572738, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54957', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When user changes a link anchor which has the same link target, suggest that they may wish to change the link target too', 'description': {'raw': \"When the text of a link is changed in VisualEditor, the link target does not change. This results in many, many edits which are entirely well-intentioned but for a patroller look like vandalism. E.g. a user tries to fix the wrong date `[[2000]]` and ends up with `[[2000|2001]]` - an erroneous link that is basically impossible to catch in visual view. (Some examples: [[https://de.wikipedia.org/w/index.php?title=Osmium(IV)-oxid&diff=prev&oldid=122526489|diff]], [[https://hu.wikipedia.org/w/index.php?title=Lengyelorsz%C3%A1g_f%C3%B6ldrajza&diff=19527995&oldid=18755093|diff]]) This is a major problem; even highly experienced users fall prey to this, and new editors all the more (and then they get treated as vandals by the patrollers who are not familiar with VE and have no idea what's going on).\\n\\nMaybe there could be some sort of notice asking whether the editor also wants to correct the actual target in case they change the displayed part of a wikilink (T55973#2792012 has a nice mockup).\\n\\nOn-wiki reports:\\n[[https://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=123123378#Wikilink-Korrektur|Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07#Wikilink-Korrektur]]\\n[[https://hu.wikipedia.org/wiki/Wikipédia:Kocsmafal_(egyéb)/Archív250#VisualEditor-hiba%3A_megtévesztő_belső_hivatkozások_létrehozása|Wikipédia:Kocsmafal_(egyéb)#VisualEditor-hiba: megtévesztő belső hivatkozások létrehozása]]\\n\\nSee Also:\\n* {T59506}\\n* {T55973}\"}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1380841680, 'dateModified': 1654539229, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54947', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make the isRedirect disable check look at the revision being considered, not current revision', 'description': {'raw': 'When a page is currently a redirect, but has none-redirect versions in its history those versions should be editable in VE but are not. e.g. https://en.wikipedia.org/w/index.php?title=Equality_Acts&oldid=570457856\\n\\nTo reproduce:\\n1. Load any page that is not a redirect in the source editor\\n2. Change the page into a redirect and save\\n3. View any revision prior to the redirect\\n\\nExpected behaviour: Old version is editable in VE\\nAction behaviour: No option is given to edit in VE\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50878'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398706803, 'spacePHID': None, 'dateCreated': 1380813300, 'dateModified': 1417572404, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54921', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Ability to change preferences without leaving current page', 'description': {'raw': \"When a user goes to change a preference, they are usually in one of the following states:\\n1. On a page that the preference would affect, and they wish to change the preference and have the change be effective asap.\\n2. About to go to a page, and know they need to change a preference in order that it is rendered the way they want.\\n\\nAn example of both of those scenarios is bug 52355, where a user wants to enable the VisualEditor on the current page, or enable it on the next page they visit (especially if it is a redlink).\\n\\nCurrently the typical workflow is\\n0. The user on a mediawiki page\\n1. Load special:preferences\\n2. Change the preference and Save (which loads preferences panel again)\\n3. Press 'Back' button twice\\n4. Reload or click a link\\n\\nDesired workflow:\\n1. Open a pref panel in the current page\\n2. Change the pref and close the panel\\n3. The changes become effective immediately, if that can be achieved without reloading the page and/or loosing any user data, or a small notice displayed near the preferences panel button to inform the users their changes will be effective by reloading.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52355\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1380686940, 'dateModified': 1643973216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54862', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'New keywords for dataloss and corruption', 'description': {'raw': \"All products occasionally cause the user to have their work disappear.  It could be the browser crashes, or the UI in a window becomes locked up.  The VisualEditor is having more than its fair share of these at the moment, and it would be good to track them with a keyword.\\n\\nThere are quite a few Parsoid/VisualEditor bugs that are behind 'corruption' of the wiki database.  'corruption' probably isnt the best name for the keyword.  It would include all the nowiki and pawn bugs, but also some parsoid round-trip issues.  These are not always high priority/severity, if they are rare or impossible in a 'normal configuration'.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1384462331, 'spacePHID': None, 'dateCreated': 1380675360, 'dateModified': 1384462331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54858', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'page-object Ruby gem deprecation warnings in VisualEditor browser tests', 'description': {'raw': 'this is like bug 46893.\\n\\n $ cd extensions/VisualEditor/modules/ve-mw/test/browser\\n $ bundle exec cucumber features/visual_editor_bullets.feature\\n\\nIf the tests progress, eventually they print out a lot of\\n\\n*** DEPRECATION WARNING\\n*** You are calling a method named class_name at /home/spage/projects/core/extensions/VisualEditor/modules/ve-mw/test/browser/features/step_definitions/visual_editor_bullets_steps.rb:81:in `block in <top (required)>\\'.\\n*** This method does not exist in page-object so it is being passed to the driver.\\n*** This feature will be removed in the near future.\\n*** Please change your code to call the correct page-object method.\\n*** If you are using functionality that does not exist in page-object please request it be added.\\n\\n*** DEPRECATION WARNING\\n*** You are calling a method named select_text at /home/spage/projects/core/extensions/VisualEditor/modules/ve-mw/test/browser/features/step_definitions/visual_editor_bullets_steps.rb:14:in `block in <top (required)>\\'.\\n*** [same last 4 lines]\\n\\nThe lines deprecated by the former are all of the form\\n  SOME_element.class_name.{should, should_not} match /disabled/\\nwhere the HTML has CSS class=\"ve-ui-widget ve-ui-tool ve-ui-tool-outdent ve-ui-widget-disabled\".  I don\\'t know the page-object equivalent to retrieving the CSS class (attribute( \\'class\\' ), but maybe instead the code could use page-object\\'s disabled? and enabled? methods.\\n\\nThe latter deprecation is odd since the test specifically requires \"watir-webdriver/extensions/select_text\"\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\\n**Whiteboard**: gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414406388, 'spacePHID': None, 'dateCreated': 1380084600, 'dateModified': 1414406388, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54590', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow inspectors to be left-aligned?', 'description': {'raw': \"Non-embedded inspectors are generally positioned to the bottom right of the node they're inspecting. In cases where we're dynamically altering the node, however (like the live preview feature for math), it probably makes more sense to position that kind of inspector at the bottom left. Then if the dimensions of the node change, the inspector will move around a bit less.\\n\\nThoughts? Other ideas to tackle this issue?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1442494980, 'spacePHID': None, 'dateCreated': 1380073020, 'dateModified': 1442494980, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54586', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: misleading exception is thrown if the parsoid service is down', 'description': {'raw': 'If the parsoid service is down (`sudo service parsoid stop`, or update extension/Parsoid and forget/fail `npm install`), then viewing flow pages fails with exception\\n\\n   Parser only supports wikitext to HTML conversion\\n\\n   Backtrace:\\n\\n   #0 /srv/mediawiki/extensions/Flow/includes/ParsoidUtils.php(24): Flow\\\\ParsoidUtils::parser(\\'html\\', \\'wikitext\\', \\'<p>It\\'s a long ...\\')\\n\\nThis is true, but it masks the real problem that parsoid has to work, and didn\\'t.  ParsoidUtils::convert has a try-catch block around using parsoid, and if that fails it will fall back to using parser. It would be helpful for wiki operators if the exception message included the parsoid failure, e.g.\\n   Parser only supports wikitext to HTML conversion (and parsoid earlier failed with exception \"VisualEditor is unavailable\")\\n\\nNow that I\\'ve figured out what\\'s going on, this has become a low-priority bug :-)\\n\\n--------------------------\\n**Version**: master\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386220039, 'spacePHID': None, 'dateCreated': 1380001740, 'dateModified': 1386220039, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54490', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow re-positioning of selected media items using arrow keys', 'description': {'raw': \"When an image is selected it should be possible to position it using the cursor keys.\\n\\nup/down should move it one line up/down. Whether left/right should move it one character or one word at a time I'm not sure about. Possibly shift/ctrl should modify this?\\n\\nThis would be useful for fine control and for systems with laggy mouse behaviour (not uncommon on slow connections in my experience).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51665\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1379954340, 'dateModified': 1643973216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54472', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Long lines in preformatted paragraphs should not wrap in VE', 'description': {'raw': \"When a pre-formatted paragraph with long lines is displayed in VE it word wraps. However it doesn't word-wrap in display mode (T2260), meaning that you have no idea that you need to add manual line breaks until after you have saved.\\n\\nSee https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&oldid=573792519#Section_number_three (rendered) and https://en.wikipedia.org/w/index.php?title=User:Thryduulf/sandbox3&oldid=573792519&veaction=edit&section=2 (in VE)\\n\\nThe word wrapping in VE is actually better than what happens in read mode, but the two should not be different. Fixing T2260 would be better, but as it's been open since 2004 adjusting VE to match the current behaviour seems more realistic :/\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=260\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429559880, 'spacePHID': None, 'dateCreated': 1379694420, 'dateModified': 1429560011, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54381', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a dialog with a list of all keyboard short-cuts (on Ctrl+? or similar?)', 'description': {'raw': 'See e.g. http://www.impressivewebs.com/demo-files/question-mark-js/ - similarly used in Reddit etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390677098, 'spacePHID': None, 'dateCreated': 1379661360, 'dateModified': 1443276360, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54365', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: OpenSearch results aren't perfect for searching for pages (some don't come up)\", 'description': {'raw': 'Screenshot of link inspector not listing a matching page\\n\\nWhen opening the link inspector on a link to dab page [[Department of Foreign Affairs and Trade]], the link inspector shows two items: the dab page, and the page [[Department of Foreign Affairs and Trade (Ireland)]].  It does not list [[Department of Foreign Affairs and Trade (Australia)]].  The unlisted page is not a new page.\\n\\nSteps to reproduce:\\n1. https://en.wikipedia.org/w/index.php?title=Heidi_Bootle&oldid=573475141\\n2. Open Visual Editor\\n3. Click on Department of Foreign Affairs and Trade\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51013\\n\\n**Attached**: {F11697}'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1433607117, 'spacePHID': None, 'dateCreated': 1379640720, 'dateModified': 1433607117, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54361', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Enwiki's {{divstyleamber}} (used in a parameter) turns into mw:ExpandedAttrs in Parsoid which VE doesn't handle yet.\", 'description': {'raw': \"Although it can't be used in articles, it is widely used elsewhere, including userpages.\\nIf you try and VEdit https://en.wikipedia.org/w/index.php?title=User:Elitre_(WMF)/Sandbox&oldid=573626556 you'll notice that this reflects in reference numbering being incorrect, since the ones in the divbox will be ignored.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54803\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1379590260, 'dateModified': 1643973216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54315', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'RTL language characters are displayed in LTR order in LTR languages (and vice versa)', 'description': {'raw': \"Incorrect reversed display of non Latin characters\\n\\nPlease see the attached image and Bugs #54308 & #54309.\\n\\nBy this time I resigned to utilize the advanced toolbar and after making an attempt, I feel very cynical because this effort is totally useless. There is a lot to be said for programmers and developers learning to proofread a chapter or so of text, to see how their ideas are working in the real world.\\n\\nIn the first place, It takes several steps to hide the header to gain additional viewing space or access various features. \\n\\nFinally, The non-Latin characters, like Hebrew and Arabic were inserted from left to right. For those who don't understand, that's the equivalent of displaying Latin characters from right to left, as in: . . . . L K J I H G F E D C B A\\n\\nIn view of my previous posts, please consider correcting this ASAP.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11606}\"}, 'authorPHID': 'PHID-USER-kdpydfvhr2l2qcrbvvz7', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1520505237, 'spacePHID': None, 'dateCreated': 1379579460, 'dateModified': 1564918799, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54310', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ResizableNode should show numeric dimensions when resizing.', 'description': {'raw': 'In a status bar/next to the cursor/on the image\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382026579, 'spacePHID': None, 'dateCreated': 1379549160, 'dateModified': 1417572821, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54297', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE \"edit\" link in section edit links of a remote file tries to create a new page on local wiki, not remote section', 'description': {'raw': 'Example image: https://www.mediawiki.org/wiki/File:MassMessage_submitted.png\\n\\nClicking on \"edit\" takes you to <https://www.mediawiki.org/wiki/File:MassMessage_submitted.png?veaction=edit&vesection=1>\\n\\nClicking on \"edit source\" tags you to <https://commons.wikimedia.org/w/index.php?title=File:MassMessage_submitted.png&action=edit&section=1>\\n\\nThe \\'edit\\' link should take you to commons and somehow gracefully fallback on the wikitext editor since VE is not enabled.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://www.mediawiki.org/wiki/File:MassMessage_submitted.png\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62071'}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398711424, 'spacePHID': None, 'dateCreated': 1379486100, 'dateModified': 1443276360, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54259', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Clicking VE edit after starting the wikitext 'firstedit' tour produces an incorrect step\", 'description': {'raw': \"**Author:** `swalling`\\n\\n**Description:**\\nScreenshot\\n\\nIf you start ?tour=firstedit and then click veaction=edit, you get the wikitext-related Preview step unattached (see screenshot).\\n\\nThis is a low priority issue, because users should only be getting the wikitext 'firstedit' tour if VE is not available. I am filing just in case the opposite situation might happen, i.e. users start a ?tour=vefirstedit, click Edit source, then get the VE tour step. If that's impossible, then this can be ignored for now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11439}\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1379459220, 'dateModified': 1680379241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54248', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Tech metrics missing IRC channels', 'description': {'raw': 'Currently there are only 4 IRC channels being scanned at \\n\\nhttp://korma.wmflabs.org/browser/irc-repos.html\\n\\nhttps://meta.wikimedia.org/wiki/IRC/Channels#MediaWiki_and_technical contains the list of tech channels\\n\\n#pywikipediabot should be added as well in order to keep consistency with https://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projects\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-kiwupwbdc2fe6dzsojnq', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1445360976, 'spacePHID': None, 'dateCreated': 1379440500, 'dateModified': 1447072897, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54230', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'InstantCommons no longer working in MediaWiki-Vagrant multimedia role', 'description': {'raw': \"InstantCommons does not work on Vagrant if you enable the 404 handler for images (the `thumb_on_404` role does that and most multimedia roles include it). The problem is related to thumbnail caching; similar to T101565, but the default wiki (`127.0.0.1`) is also affected.\\n\\nAs a workaround, caching can be disabled by creating `/vagrant/settings.d/10-DisableThumbnailCaching.php` with\\n```\\n<?php\\n$wgUseInstantCommons = false;\\n$wgForeignFileRepos[] = array(\\n\\t'class' => 'ForeignAPIRepo',\\n\\t'name' => 'wikimediacommons',\\n\\t'apibase' => 'http://commons.wikimedia.org/w/api.php',\\n\\t'fetchDescription' => true,\\n\\t'descriptionCacheExpiry' => 0,\\n\\t'apiThumbCacheExpiry' => 0,\\n);\\n```\\n\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-a6p24cvyblhfzc7we7nc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ll6tmaogat2b5q7tnqas', 'dateClosed': 1468099239, 'spacePHID': None, 'dateCreated': 1379384100, 'dateModified': 1468099239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54202', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If some content is selected when inserting a template, replace it with the template with the selection magically inserted as the first(?!) parameter', 'description': {'raw': '(Hopefully other reporters will improve the title and description if necessary!)\\nThe French Wikipedia has a number of templates which usually ask for some kind of clarification about a whole passage of text (see https://fr.wikipedia.org/wiki/Mod%C3%A8le:Refnec#Exemples ).\\nSo users are asking that, when they select that text and launch the template inspector, the text is already recognized as a \"parameter\" for that template.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1379367180, 'dateModified': 1643973217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54186', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Duplicating categories (and possibly also something else)', 'description': {'raw': \"NicoV reports this diff,\\nhttps://fr.wikipedia.org/w/index.php?title=Blood_Lad&diff=96657484&oldid=96506947 .\\nAssuming the user deleted the infobox without realizing it, I did not manage to reproduce the duplication of categories inside a reference tag (line 38); if I just copy/paste them they get nowikied, so it shouldn't be a vandalism.  \\n\\nCCing subbu and gwicke here. T52120 and T54238 come to mind, but I'm not sure if it's really a dupe.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nT54238\\nT52120\\nT76715\\nT89618\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1425592411, 'spacePHID': None, 'dateCreated': 1379347920, 'dateModified': 1438734473, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54169', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"MediaWiki:Editing\" notice did not parse  a link when tried so', 'description': {'raw': 'Change in MediaWiki:Editing notice to a links does not  parse\\n\\nHi,\\n\\n\\nWhen I tried to add a internal link (related to [[Special:Preferences#mw-prefsection-editing]])  to MediaWiki:Editing, it did not parse as shown in attachment.  \\n\\n\\n*Exact edit  difference which I tried https://mr.wikipedia.org/w/index.php?title=मिडियाविकी%3AEditing&diff=1200554&oldid=44085 the result is shown in the attachment.\\n\\n\\n*The purpose of edit was to request users to give a try to VisualEditor and report input issues . (Issues related to usability of Marathi Devnagari script are very crucial to us )\\n\\n\\nI am not sure whether this a normal limitation of MediaWiki messages  and so not sure whether this will be accepted as a bug.\\n\\nBut still prefered to report this bug since it is simmiller problem of parsing which I observed in Bug no 45195 also and just prefered to keep developers informed.\\n\\nThanks and regards\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: normal\\n**Whiteboard**: aklapper-moreinfo\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=45195\\n\\n**Attached**: {F11186}'}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379943675, 'spacePHID': None, 'dateCreated': 1379172900, 'dateModified': 1379943675, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54127', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Transclusion dialog: \"unknown parameter\" is confusing if TemplateData doesnt exist', 'description': {'raw': 'If adding w:cs:template:commonscat, it might be confusing for newbies even for older wikipadians to set parameters. As in this case parameters or numbers, but VE sais that such parameters are unknown.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50735'}, 'authorPHID': 'PHID-USER-vm462i2ffbawnuo4mh3n', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1381342230, 'spacePHID': None, 'dateCreated': 1379064360, 'dateModified': 1417572820, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54094', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Zero width no-break space is added to the end of the article (in a slug) in the editing element (but not the document)', 'description': {'raw': 'I am trying to run the test at https://gerrit.wikimedia.org/r/#/c/83966/\\n\\nIn the end it is trying to compare the text that was typed with the text that actually appears on the screen. The test fails, because the Zero width no-break space (U+FEFF) character is added to the string that appears on the screen.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1378949100, 'dateModified': 1643973218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54051', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Autocomplete for (local) image names', 'description': {'raw': \"It'd be nice if WikiLove had a javascripty autocomplete for image names (at least local ones)\\n\\n--------------------------\\n**Version**: master\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1378778340, 'dateModified': 1643973218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53976', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Reduce VisualEditor's memory usage\", 'description': {'raw': \"Editing of large pages can use a significant amount of memory; a spotcheck that Max did on [[United States]] showed an increase of 121MB usage in Chrome while editing the page.\\n\\nThis is a concern for us for mobile in particular, as today's mobile devices have the amount of memory of computers from several years ago -- most have 1GB or 512MB (or even less), which has to house the operating system, background apps, the web browser, and the *entire* article with a richly annotated DOM.\\n\\nPossible techniques for reducing memory usage were proposed at the VE mobile meeting yesterday:\\n\\n* Section editing -- if we only have to load up a single section at a time, large pages won't use up nearly as much memory. Note that on mobile we already divide the page up into sections surrounded by <div>s that can be replaced with the editable surface; the other sections on page might not even be open.\\n\\n* Limit full annotation processing to areas under active editing -- apparently it should be possible to delay some of the HTML processing on sections or even paragraphs that have not yet been edited. This might also save memory, but needs to be looked into.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1378411260, 'dateModified': 1692391382, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53825', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"[mediawiki.feedback.js] Provide a link to the article (and maybe the user's contributions)\", 'description': {'raw': \"Users seem to expect that the feedback link will automatically supply information, especially the title of the article they're working on.  I'd also like to have the version number they were actually using (cacheing issues) and a link to the user's contibutions.\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1378397100, 'dateModified': 1643973218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53801', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Insert external pasted content as \"unformatted\" if Ctrl+/Cmd+Shift+V rather than Ctrl+/Cmd+V trigger', 'description': {'raw': 'Right now external paste always writes the clipboard as formatted; in some cases, users will want to \"Paste Unformatted\".\\n\\nOn Mac, there\\'s a standard shortcut for this of Cmd+Shift+V - I\\'m assuming that Ctrl+Shift+V would be sensible as well.\\n\\nWould we also need a button? What about for the other standard 3 (Cut/Copy/Paste)?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385505229, 'spacePHID': None, 'dateCreated': 1378335600, 'dateModified': 1417570403, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53781', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: On opening a reference which includes a single template and nothing else, also open that template's dialog\", 'description': {'raw': 'When you open an existing reference in VE that only consists of one template the main use case should be that you want to edit that template. But now you need to first select it and then klick on the puzzle piece.\\n\\nInstead I suggest that in that case, you get forwarded to the template editor directly after choosing to open the reference editor without having to do it manually.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-bvi77f4zkvm3mrkrqvwp', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401472643, 'spacePHID': None, 'dateCreated': 1378220100, 'dateModified': 1443276361, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53713', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[EPIC] trigger browser tests from Gerrit (tracking)', 'description': {'raw': 'The VisualEditor and ULS MediaWiki extensions have recently been blessed with QA browser tests.  We would need them to be in the Contint Jenkins and triggered by Zuul whenever a patchset is submitted as well as in the gate-and-submit pipeline.\\n\\nThat needs several step:\\n\\n- describe the jobs in Jenkins\\n- add the triggers in Zuul configuration\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'ownerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'dateClosed': 1496054383, 'spacePHID': None, 'dateCreated': 1378194900, 'dateModified': 1623664182, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53697', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VIsualEditor: Allowing editing of attributes in MWAlienExtensionNode', 'description': {'raw': 'Need some UI to add/remove/edit the key value pairs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377906360, 'dateModified': 1643973219, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53614', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In the transclusion dialog, use \"Root#sets\" data to allow addition and/or completion of parameter > sets', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377905220, 'dateModified': 1643973219, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53609', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide some kind of template suggestion in the transclusion editor', 'description': {'raw': 'Adam Cuerden says,  \"I believe the VE team intends to have a some one click solutions in the near future, including adding templates of your choice to a bar? Although I\\'d hope there\\'d also be a few automatic lists you could choose to pull up - cleanup templates, etc.\"\\n\\nSo, it would be really comfy for users if the template editor, beyond being able to let them select what they need by typing the name, asked \"Which kind of template do you want to add?\" and provided lists of the most used/popular ones, divided per set (cleanup templates, citation templates and so on).\\nOr just a way to store one\\'s most used choices.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T52458}'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377873180, 'dateModified': 1732669010, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53590', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Pages should have metadata about their correct title (capitalisation, special characters, etc)', 'description': {'raw': \"As discussed at bug 50452 comment 9 it would be very useful for a page to have associated metadata about its title.\\n\\nFor most pages and by default* this would be identical to the all-lowercase rendering of its stored title, but where pages correctly start with a lowercase letter (on wikis where the first character is case insensitive), contain special characters or conflict with interwikis/namespaces, etc. the metadata would record the correct page title. It could also be used for titles that should be italicised.\\ne.g. on en.wp:\\nPage Title         - Correct Title\\n[[IPad]]           - iPad\\n[[Benzo(a)pyrene]] - Benzo[a]pyrene\\n[[Pilot No. 5]]    - Pilot #5\\n[[D Ream]]         - D:Ream\\n[[Computer]]       - computer [indicating a common noun]\\n[[Amy Studt]]      - Amy Studt [indicating the title is proper noun]\\n[[Animal Farm]]    - <i>Animal Farm</i> [italicised proper noun, the tags are not literal]\\n\\nThe displayed title would be taken from this metadata and as such would effectively supercede the DISPLAYTITLE magic word and the [[template:correct title]] family of templates (and the equivalents on other wikis).\\n\\nVisualEditor and any other tools that aid linking would be able to read the metadata and use it to determine what the default displayed name should be when linking to that article.\\n\\n*Actually the default should be configurable as I guess languages like German that capitalise common nouns may want the default to be capitalised and the upper/lower case distinction probably doesn't make sense in all scripts.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50452\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56868\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49076\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377811860, 'dateModified': 1734274074, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53566', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inspectors apply if you exit from them without a positive action, which can be a bit confusing', 'description': {'raw': 'If you start to add a link, and change your mind (e.g., you realized that you have the wrong word selected), there is no way to simply cancel adding a link.  You have to remove the link with the trashcan icon.\\n\\nSteps to reproduce:\\n\\n1. Select any word.\\n2. Press ctrl-K to enter link tool.\\n3. Attempt to cancel the link by closing the unwanted link tool dialog box using Esc key or the < button.\\n4. Discover that VisualEditor linked the word anyway.\\n\\nIf the Escape key and \"Cancel\" button are worthless for escaping/going back/cancelling, then they shouldn\\'t be present or have any effect.\\n\\n({T93749} altered this to re-add the cancel/close button.)'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1433183735, 'spacePHID': None, 'dateCreated': 1377799620, 'dateModified': 1660398906, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53546', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way for users to edit auto-numbered external links', 'description': {'raw': 'The Parsoid team is considering a simplification of the different mw:ExtLink/* variants to just a single mw:ExtLink type. \\n\\nFor most types this should not make much of a difference to VE, but for auto-numbered external links ([http://example.com]) it might, so I am looking for your input. I did some testing on https://www.mediawiki.org/wiki/User:GWicke/TestNumberedLinks. Changes to the text lead to corruption as in this diff:\\n\\nhttps://www.mediawiki.org/w/index.php?title=User%3AGWicke%2FTestNumberedLinks&diff=772988&oldid=772987\\n\\nThere also does not seem to be any automatic re-numbering when a numbered link is changed into a plain external link.\\n\\nWhat are you plans for the handling of numbered links?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386002036, 'spacePHID': None, 'dateCreated': 1377728940, 'dateModified': 1417572489, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53505', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: trouble with Template:Hlist', 'description': {'raw': \"Reporting user comment, some formatting is mine:\\n<<I made this http://en.wikipedia.org/wiki/User:Atethnekos/sandbox4 as a demonstration. \\n1) If the hlist template is used in an infobox or a table like on the page, when I go to VE, the list will end up be extended far into the page. \\n2) If it's used with [[File:Image]] as on the page, the list will end up being cut off, and then some weird things will happen if I try to click on the hlist template (e.g., the page will be extended to right and my browser will give a horizontal scroll bar). FF 23.0.1 Win7--Atethnekos 19:33, 25 August 2013 (UTC) >>\\n\\nI edited his sandbox a couple of times. In this version http://en.wikipedia.org/w/index.php?title=User:Atethnekos/sandbox4&oldid=570256245&veaction=edit the pics of the masks are moved to the left: the caption of the first one is not cut out, but you can't edit the pics at all since VE will consider them as a non editable block.\\nI can't reproduce the horizontal bar and I can correctly edit the hlist template inside the mask pic caption with both FF and Chrome.\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1590760929, 'spacePHID': None, 'dateCreated': 1377521880, 'dateModified': 1590760929, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53340', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Safari on iPad converts numbers that resemble phone numbers to href=tel: links', 'description': {'raw': 'Same as #51959, but it keeps hapenning on frwiki: some texts that look like telephone numbers are changed in <a href=\"tel:...\">...</a>.\\n\\nhttp://fr.wikipedia.org/w/index.php?title=Les_Visiteurs_(film,_1993)&diff=95954243&oldid=95559259\\n\\nhttp://fr.wikipedia.org/w/index.php?title=Transformers_3_:_La_Face_cach%C3%A9e_de_la_Lune&diff=96093057&oldid=95089445\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**OS**: other\\n**Platform**: Other\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51959'}, 'authorPHID': 'PHID-USER-o34e5i3eq4nstbvcf26w', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1430334450, 'spacePHID': None, 'dateCreated': 1377428640, 'dateModified': 1593527812, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53315', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Evernote Web Clipper inserts _clearly_component__css', 'description': {'raw': 'EverNote Web Clipper has a problem with the editable area and inserts:\\n\\n<style id=\"_clearly_component__css\" type=\"text/css\">#next_pages_container { width: 5px; hight: 5px; position: absolute; top: -100px; left: -100px; z-index: 2147483647 !important; } </style><div id=\"_clearly_component__next_pages_container\"></div>\\n\\nTriggering: https://en.wikipedia.org/wiki/Special:AbuseFilter/345\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412114353, 'spacePHID': None, 'dateCreated': 1377255600, 'dateModified': 1417571700, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53252', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Hieroglyphics tool inserts a new line at the cursor whether or not you actually insert a hieroglyphics block', 'description': {'raw': \"Screeshot of post hiero editor\\n\\nSafari 6\\n\\nI opened the editor inline, didn't do anything, pressed the back arrow, the editor closed and inserted a newline.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11956}\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377250800, 'dateModified': 1416845767, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53250', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Support Clipboard Based Image Upload', 'description': {'raw': \"**Author:** `lucashokanson`\\n\\n**Description:**\\nIt would be extraordinarily useful to mimic Imgur.com's clipboard based uploader.  Upon visiting the upload page, you would simply Paste - command/control v or click a button to use your clipboard's contents.  This would then upload the file and return to you the standard file:____ page.  \\n\\nIn addition to this, if this functionality is built it, it would even more useful to streamline this into the page editor as well. A simple button click could pop up a prompt and upon upload return the proper image reference in your article.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=37932\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65670\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1425600740, 'spacePHID': None, 'dateCreated': 1377203100, 'dateModified': 1425600886, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53235', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)', 'description': {'raw': 'In Chrome, edit any page in https://test2.wikipedia.org\\n\\nClick Transclusion, type \\'s\\' into input box.\\nResult is a list of suggestions that begin with \"Smaller\" and \"Sectstub\"\\n\\nIn Firefox, edit any page in https://test2.wikipedia.org\\n\\nClick Transclusion, type \\'s\\' into input box.\\nResult is a list of suggestions that begin with \"Succession box\" and \"South America\"\\n\\nThis suggests that at least one list of Template suggestions is absolutely incorrect.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58406'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1429301547, 'spacePHID': None, 'dateCreated': 1377199800, 'dateModified': 1429301547, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53231', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CSS munging causing absolutely-positioned <div>s used to create pie charts(!) to break', 'description': {'raw': \"https://he.wikipedia.org/wiki/%D7%A8%D7%90%D7%A9%D7%95%D7%9F_%D7%9C%D7%A6%D7%99%D7%95%D7%9F?veaction=edit\\n\\nThe template on the left has a pie chart (see in view mode in the extendable green section) -- but in edit mode it's all jumbled.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\n{T53932}\\n{T53166}\"}, 'authorPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429615773, 'spacePHID': None, 'dateCreated': 1377192840, 'dateModified': 1438734486, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53226', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Hieroglyphics tool operating on a selection replaces the content, rather than appending the hieroglyphics block', 'description': {'raw': 'Testing the hieroglyphics feature on MW.org just now:\\n\\n1. Open VE and select some text\\n2. Click \"Hieroglyphics\" button\\n\\nWhy can I \"apply\" hieroglyphics to a run of text, as if it was a kind of formatting? Doesn\\'t make any sense.\\n\\n3. Type some hiero codes (e.g. G26-t:Z4-A40) in the box\\n4. Leave the popup (by clicking away/clicking the < button)\\n\\nThe popup goes blank and can\\'t be dismissed (Firefox 23).\\nAlso notice that no hieroglyphics are seen.\\n\\n5. Review changes.\\n\\nThe hiero tag successfully appears in the wikitext, even though it is invisible in VE.\\n\\nSorry for three issues in one bug, but I guess you guys can figure this out.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1386337120, 'spacePHID': None, 'dateCreated': 1376996400, 'dateModified': 1417572741, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53090', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When \"section editing\", re-focus on that section after saving the page', 'description': {'raw': 'Some users on en.wp consider it a bug that VE shows the top of the page after you edit a \"section\", and demand instead that, as VE auto-scrolls to the relevant section when you click Edit, it does the same after you save. Thanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1541160256, 'spacePHID': None, 'dateCreated': 1376995620, 'dateModified': 1541696283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53089', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Incompatibility with Special:Preferences#mw-prefsection-editing item, \"Edit pages on double click (requires JavaScript)\"', 'description': {'raw': 'If you have the preference set to \"Edit pages on double click\", then double-clicking on a word while you\\'re already in VisualEditor tries to re-open the page so you can edit it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Double-click_asks_if_you_want_to_leave_page'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1411685035, 'spacePHID': None, 'dateCreated': 1376935080, 'dateModified': 1417571833, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53058', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show \"Review changes\" link in the toolbar all the time, or available somehow (on hover?) rather than just through save dialog', 'description': {'raw': 'I am editing a page and something untoward happens.  To review changes, I now have to click \"Save page\", which is sort of like a sign above a circular saw saying, \"To unplug, please saw through wall.  Thank you for your cooperation.\"\\n\\n:p\\n\\nPerhaps hovering over the \"save page\" button could drop down alternative actions, such as \"save draft of changes\", \"review...\" etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1376812680, 'dateModified': 1643973220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52980', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Broken Foxlingo Firefox extension injects javascript into page', 'description': {'raw': 'See reported diff on fr.wp\\nhttps://fr.wikipedia.org/w/index.php?title=Debra_Winger&action=historysubmit&diff=95823433&oldid=94552186\\n\\nThe js is from Foxlingo but the liberal sprinkling of nowikis is from VE or Parsoid.\\n\\nPrimeHunter at en.wp reports that a Google search for FoxlingoJS reveals several other internet forums are suffering the same problems.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412114336, 'spacePHID': None, 'dateCreated': 1376582220, 'dateModified': 1417571700, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52884', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Populate the edit summary for simple changes', 'description': {'raw': 'At T53903,  Elitre said:\\n\\n> A user at it.wp wonders: if VE could pre-populate the summary box, could it\\n> also auto-add the text that was added, in case of very short additions? i.e.,\\n> if someone added a parameter to a template, could it automatically detect\\n> what was added and write it in the edit summary? Thanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**: T53903, T50274'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1376506380, 'dateModified': 1643973220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52859', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add help page for all keyboard shortcuts', 'description': {'raw': \"GMail's keyboard shortcuts help page\\n\\nSimilar to GMail's modal when '?' is pressed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F11100}\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389836925, 'spacePHID': None, 'dateCreated': 1376487180, 'dateModified': 1443276369, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52844', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Broken DataVault browser plugin causes \"application/x-datavault\" to be injected into the page', 'description': {'raw': 'At https://en.wikipedia.org/w/index.php?title=Judi_Dench&curid=85432&diff=568314406&oldid=568147939 the article was top and tailed with\\n<embed type=\"application/x-datavault\" width=\"0\" height=\"0\" />\\n\\nSearching seems to suggest the most likely cause is the \"DataVault\" password manager browser plugin\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412114322, 'spacePHID': None, 'dateCreated': 1376392740, 'dateModified': 1417571830, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52791', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add support for making some templates directly \"visually editable\", as if they were tables (e.g. infoboxes)', 'description': {'raw': 'A user at it.wp asks if, in the long term, it will be possible to edit templates directly (i.e., infoboxes), without the transclusion dialog, as if one was changing something in a table. Thanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394074105, 'spacePHID': None, 'dateCreated': 1376386200, 'dateModified': 1417572583, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52786', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Newly-uploaded image doesn't immediately appear in image search results in VisualEditor\", 'description': {'raw': \"<< http://en.wikipedia.org/wiki/File:GreatNurse.jpeg is a headshot of Virginia Henderson that was uploaded to Commons yesterday. VisualEditor's image feature can't find it, and won't accept file names that it doesn't believe exist. WhatamIdoing (talk) 00:17, 13 August 2013 (UTC) >>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=37578\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1383013054, 'spacePHID': None, 'dateCreated': 1376382300, 'dateModified': 1389677511, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52782', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make each reference editable where it appears in the reference list as well as on the edit surface', 'description': {'raw': 'At https://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=568194420#I_can.27t_edit_the_references it has been proposed that it would be helpful to editors if they could edit references in the reference list, as well as where they appear inline.\\n\\n\"As just about every object you see on a page is directly editable with the VE, of course having the reflist not editable is counter-intuitive. \"\\n\\nThis proposal would make T54736 either unnecessary or just a \"workaround\"/interim measure, depending on the timescale to implement.\\n\\n--------------------------\\n\\n#2 in the 2023 wishlist: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Citations/Allow_citations_to_be_edited_in_the_references_section_with_VisualEditor\\n'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1688774070, 'spacePHID': None, 'dateCreated': 1376315340, 'dateModified': 1729667390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52750', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Alt+Shift+V access key in the wikitext editor switches to the visual one, so conflicts with 'show changes' which no longer works in Chrome, focus splits in Firefox\", 'description': {'raw': 'en.wp user JmCor reports that in Firefox on Windows 7 the shortcut \"<shift><alt>V (show the changes), which stopped working when the Visual Editor was introduced: currently, <shift><alt>V simply positions the cursor on the \"Show the changes\" button.\"\\n\\nI can confirm this also occurs in Firefox 23 on Linux.'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1376130000, 'dateModified': 1682937197, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tool to set/unset text as a variable (<var>)', 'description': {'raw': 'The <var> tag is used in many articles for variables, and there are css styling rules for it. An example article is Shading\\nhttp://en.wikipedia.org/w/index.php?title=Shading\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1376027640, 'dateModified': 1643973220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52664', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tool to set/unset text color', 'description': {'raw': 'VisualEditor needs a tool to set/unset font colour.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375956720, 'dateModified': 1732295481, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52645', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links can point to wrong page if not matching case exactly and when not first option in the list', 'description': {'raw': '**Author:** `sandrobt.wiki`\\n\\n**Description:**\\nHere is how to reproduce it, when trying to add a link to the page \"Maria\" on en.wiki.\\n\\n1) Select the add link icon and type \"maria\"\\n2) Select \"Maria\", which is at the end of the suggested list\\n3) Press Enter or the \"<\" button\\n4) Save\\n\\nThe link is added to Mariah Carey (which was on the top of the suggested list).\\nCf. https://en.wikipedia.org/w/index.php?title=User:Sandrobt/prova&diff=prev&oldid=567641122\\n\\nNote that this doesn\\'t happen if in 2) you had typed \"Maria\" (which is the exact title of the page you want to link to).\\nCf. https://en.wikipedia.org/w/index.php?title=User:Sandrobt/prova&diff=next&oldid=567641169\\n\\nThe same problem appears in similar situations in it.wiki (for example when adding a link to \"Sega\" you need to type it exactly like that, since the first option is always SEGA) \\n\\nI\\'m using Firefox 22.0 on Mac OS X 10.6.8.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402552412, 'spacePHID': None, 'dateCreated': 1375943460, 'dateModified': 1441912193, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52634', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Implement inferred templatedata as fallback based on the contents of the template', 'description': {'raw': 'if the template does not contain explicit \"templatedata\", the API call should return auto-generated \"templatedata\" structure, distilled from the template itself.\\n\\n\\nit\\'s trivial to do - basically parse the template, extract parameter names (including order based, aka 1,2,3), and return \"default\" templatedata where every param is of type string, without any special attributes (default, required, etc.)\\n\\nthis 15-line enhancement will make VE suddenly useful for templates, without detracting anything from current functionality.\\n\\nwe did this in hewiki with \"template param wizard\" (the equivalent of VE template editor, for the old wikitext editor), and it enhanced the wizard\\'s functionality tenfold.\\n\\nregretfully i can\\'t submit a patch - hopefully someone else will be able to do so.\\n\\npeace.\\n\\n--------------------------\\n\\n**See Also**:\\n{T54135} / https://bugzilla.wikimedia.org/show_bug.cgi?id=52135'}, 'authorPHID': 'PHID-USER-akv4ingxkspiiam6r2n4', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1526505693, 'spacePHID': None, 'dateCreated': 1375804800, 'dateModified': 1585739470, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52581', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow replacing file by changing the file name', 'description': {'raw': 'To replace a file it is currently neccessary to delete the file from the page and insert the new one.\\n\\nIt would be easier to replace the filename only. This avoids to add caption and file options again.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402608867, 'spacePHID': None, 'dateCreated': 1375804620, 'dateModified': 1417572222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52580', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When section edit is initiated with an actual page load, VE does not navigate to the section', 'description': {'raw': 'When VisEd is activated from a section edit link, the focus of the display normally stays on that section.  However, if the user activates from a section edit link while on a diff link (has to be diff of current version), the focus shifts to the top of the page as if the whole page edit link had been pressed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-imut7wxehhy35ukuzaks', 'ownerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399312671, 'spacePHID': None, 'dateCreated': 1375747320, 'dateModified': 1443278231, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52566', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When a link goes to a redirect, show the final destination as a tooltip (title attribute)', 'description': {'raw': \"Wikis use lots of shortcuts on the talk pages, and it can be quite frustrating for the uninitiated to figure out what WP:MOS, WP:N etc. mean, especially when several are used at once.\\n\\nHaving to click on the link to see that its about the 'Manual of Style' or 'Notability' would be unnecessary, if the same information was available in the tooltip when hovering the link.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-pwsgofaoir7tnszvfzqi', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375731240, 'dateModified': 1643973221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52558', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying of styles to dialog frame is dirty', 'description': {'raw': 'Screenshot where it works (VE copied it from <style>)\\n\\nWhen VE copies styles into the frame, in the case of copying from a friendly <link> tag (e.g. one that is readable, we inspect it and copy the contents over, as opposed to a foreign one we have to fetch again from the iframe).\\n\\nIn that case, the css we manage to extract from the remote <link> appears to be dirty and neither strictly or effectively roundtrips. Both the actual css it copied and the effective values are different.\\n\\nFor example, in the case of \"background: none;\"  it gets dirtied to \"background-image: none; background-position: initial initial; background-repeat: initial initial;\". Which means it no longer overrides background-color.\\n\\nNow, in some browsers background: none (old IE iirc) is indeed interpreted as the above, and it would be reasonable behaviour of it expands it to what it interprets it as.\\n\\nHowever in the case of Chrome, it does\\'t just normalise but actually gives us values that don\\'t match. See attached screenshots.\\n\\nThe side effects (e.g. broken styles) are currently (e.g. MediaWiki context) most visible in debug mode because then almost everything is loaded through <link> and as such subject to this bug. In production mode most things are loaded by ResourceLoader and thus evaluated inline. However it is a bug both in production as well, it is just a matter of time before we find random broken styles.\\n\\n\\n- Figure out if we can get the contents without normalisation\\n\\n- Perhaps fallback indefinitely to always using <link href> for remote stylesheets, thus costing a few extra http requests inside the dialog, but that might be the only way we can for now.\\n\\n- Figure out how many things are affected and in which browsers. Maybe we can get it fixed upstream reasonably fast (these seem to be genuine bugs in the browser).\\n\\n- If there\\'s only a few properties subject to dirty normalisation, we could consider changing our stylesheets to avoid those properties. E.g. instead of background: none; use background-color: none; (something less ambiguous, and probably correct in this case, though it is a bug still because it works in Chrome normally, but not after roundtripping to an iframe).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F11259}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415062594, 'spacePHID': None, 'dateCreated': 1375487160, 'dateModified': 1417571682, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52486', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Media selector should suggest media used on other language versions of the page', 'description': {'raw': 'en.wp user Wouterstomp suggests that the media selector should also suggest images that are used on other language versions of the article, not just based on the page title.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T53031}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375461120, 'dateModified': 1643973221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52464', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Media settings dialog should show a preview of the media item', 'description': {'raw': 'Wouterstomp at en.wp has requested that the media settings dialog shows a tumbnail/preview of the image so you can refer to it while writing the caption.\\n\\nI would add to this that ctrl+click on this preview image should load the media description page in another tab/window.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375459860, 'dateModified': 1643973221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52461', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Disallow (discourage?) placing references inside section headers', 'description': {'raw': '<<This is not really a VE bug (it is possible in the standard editing mode as well), but it is something that happens more often in VE, and that perhaps can be automatically disabled in VE as well; inserting references inside section headers. This is never needed or wanted (it is ugly, and the thing that needs to be referenced should be in the text of the section, not only in the title anyway). Example (spam, but the principle applies): http://en.wikipedia.org/w/index.php?title=Miniature_pig&diff=prev&oldid=566703074 . Fram (talk) 07:31, 2 August 2013 (UTC) >>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375436160, 'dateModified': 1643973221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52450', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Always show dialog icons for nodes (transclusion, media, reference, etc.)', 'description': {'raw': 'A user at en.wp asks:\\n\"Why hide the puzzle and content icons until mouse-over? In general, if a function is active, it should be always shown - no idea, what hiding tries to achieve here.\"\\n\\nPersonally I think this could be very confusing for links, but it should be ok for templates and media.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393632819, 'spacePHID': None, 'dateCreated': 1375434180, 'dateModified': 1417572589, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52447', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If an added category is a redirect to another, suggest adding the target instead', 'description': {'raw': 'If category:A is redirected to category:B \\nwhen user adds category:A it should switch it automatically to category:B like mediawiki:gadget-Hotcat.js\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-dswbdv7ibhsefllcqarz', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397702597, 'spacePHID': None, 'dateCreated': 1375383960, 'dateModified': 1443276372, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52414', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Invocation of \"lastmodifiedat\" message is not updated when page is saved', 'description': {'raw': 'The sentence \"This page was last modified on … \" (message lastmodifiedat) is not updated after an edit.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48560'}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414769362, 'spacePHID': None, 'dateCreated': 1375374540, 'dateModified': 1417571675, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52403', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ULS\\' \"Language Settings\" cog is confused with a way to edit language links', 'description': {'raw': 'The cog to the side of the \"Languages\" sidebar section does, in fact, not let you change anything about that section.\\n\\n### Concerns\\n\\n* The ULS \"cog\" is visually associated with the \"Languages\" sidebar section, despite being unrelated, other than (confusingly) relating to the word \"Language\" in some way. The placement of this cog should be reconsidered.\\n\\n* The \"Language\" sidebar does not currently have a way to quickly edit its contents. (Unlike HotCat for categories). It can be changed by performing a full page edit (via the main \"Edit\" button on top). Alternatively, the links can (sometimes) be edited using the \"Edit links\" placed at the end of the link, which relates to Wikidata.\\n\\n### Background\\n\\nThere are three things related here:\\n\\n1. Edit language links on current page: This is part of the content for the current page, and can be edited by clicking \"Edit\" and changing them in VisualEditor (under \"Page Settings  > Languages\"), or by using the source editor.\\n\\n2. Edit language links associated with current page\\'s Wikidata item: These are stored on Wikidata and can be edited by using the \"Edit links\" button at the bottom of \"Languages\" sidebar section.\\n\\n{F11931}\\n\\n3. User interface language: This is the language used for the interface of the software, names of input fields, sections, buttons, etc. This can be changed in three ways currently:\\n\\n| Preferences | \"Preferences\" among the personal tools. Available on all pages, all wikis. leading to Special:Preferences.  {F14222596} {F14222603}\\n|--\\n| ULS (personal)| The ULS link (language name) among the person tools. Available on all pages, but only certain wikis have it enabled. Leading to a ULS dialog dedicated to language selection.  {F14222782} {F14222792}\\n|--\\n| ULS (cog)| The ULS cog, aside the \"Languages\" section in the sidebar. Available only on content pages, all wikis. Leads to a different ULS dialog, one that also has other features, but among them language selection. {F11929} {F14223046}\\n|--\\n\\n\\n### Original task description\\n\\n>>! this-does-not-edit-languages wrote:\\n>\\n> languages should be editable out of a link besides languages. see attachment for a wheel which opens something else, on top of languages. clicking below drops you into wikidata. to really edit the languages one has to go to page settings! very confusing.\\n>\\n>\\n> **Attached**: {F11929}'}, 'authorPHID': 'PHID-USER-2ccnbnjo2s2q3diidydr', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375354680, 'dateModified': 1673582745, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52383', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: pasting with middle-click in X-Windows doesn't work when automatic scrolling is enabled\", 'description': {'raw': \"On Unix systems with an X-Windows desktop middle-clicking usually pastes text that was last selected with the mouse.\\n\\nIt doesn't work in the VisualEditor in Firefox if automatic scrolling is enabled in the preferences.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375295280, 'dateModified': 1416845820, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52336', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selecting with Shift-arrow selects the heading after a list item', 'description': {'raw': 'Go to https://www.mediawiki.org/wiki/User:Amire80/be-bullet-heading?veaction=edit, which contains the wikitext:\\n```\\n* list item 1\\n* list item 2\\n* list item 3\\n\\n==Heading==\\nparagraph text\\n```\\nPress Shift-↓ (down arrow) three times.\\n\\nThe first time, the first list item is selected.\\nThe second time, the second list item is selected.\\nThe third time, the third list item AND the heading are selected.\\n\\nSelecting the heading should require a forth press of Shift-↓.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701961099, 'spacePHID': None, 'dateCreated': 1375294800, 'dateModified': 1701961099, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52332', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Display of several float:left-ed tables side-by-side inserts slugs that break them up', 'description': {'raw': 'Screenshot of the bug as provided by user\\n\\nDepending on the display format, VE fails to get the display of several tables properly in line. See also attachment; test page here:\\n\\nhttp://de.wikipedia.org/wiki/Benutzer:Stefan_Knauf/Dateidurchsuchungsprogramm.cpp\\n\\nReport:\\n\\nhttp://de.wikipedia.org/w/index.php?title=Wikipedia:Technik/Text/Edit/VisualEditor/Beta2013-07&oldid=121040382#VisualEditor_ist_nicht_WYSIWYG\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11761}'}, 'authorPHID': 'PHID-USER-wswkm7jrcwes3tc7o34k', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375227780, 'dateModified': 1701962447, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52304', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reject (or at least loudly warn about) edits that contain pawns or other obvious placeholders', 'description': {'raw': 'Rather than simply quietly inserting pawns and other placeholder characters into the page text, VisualEditor should do a sanity-check pre-save and either outright reject or loudly warn about edits that will insert such characters.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1508930263, 'spacePHID': None, 'dateCreated': 1375118160, 'dateModified': 1508930263, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52231', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow users to customise keyboard shortcuts', 'description': {'raw': 'What it says on the in. Like in most desktop applications, it should be possible for users to customise the keyboard shortcuts to their liking. Including in VisualEditor and source editor.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374931980, 'dateModified': 1643973221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52143', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Edit summary box should be a text input box and not textarea', 'description': {'raw': '**Author:** `KilliondudeWP`\\n\\n**Description:**\\nThe edit summary box currently uses a textarea input box. Current functionality has the return key starting a new line in the textarea, but upon save the edit summary is truncated into one line in the page history (line breaks are turned into spaces). Thus, the textarea box is misleading.\\n\\nA more sane option would be to use a single line text input box, where the enter key processes the edit rather than starts a new line.\\n\\nSee T40042 and T42034, and specifically T42034#467450.\\n'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1437391823, 'spacePHID': None, 'dateCreated': 1374899820, 'dateModified': 1561611650, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52133', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Copying between editors with wikitext-irrelevant CRs pastes the ↵ as a literal character, not a CE newline placeholder', 'description': {'raw': 'Steps to reproduce\\n1. Create a page with a linefeed\\n2. Edit it in VE\\n3. Copy the block containing the ↵\\n4. In a new VE window, paste\\n\\nExpected results:\\nVE smartly removes the ↵\\n\\nActual results:\\nThe ↵ is pasted into the second VE as a literal character\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=53828'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378923398, 'spacePHID': None, 'dateCreated': 1374849360, 'dateModified': 1417570404, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52096', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces', 'description': {'raw': \"As perhaps a simpler case of copy and paste from 'external sources', pasting richtext that copied from the same wiki should work seamlessly.\\n\\nIn many cases, the 'html' already has the metadata needed. e.g. the image, or text-with-wikilinks, even the categories, should be paste-able\\n\\nhttps://en.wikipedia.org/wiki/Pelham_Parkway\\n\\nWith a tiny bit of additional html attributes, the navbox templates ({{Parkways in New York City}} & {{Bronx streets}}) could be copied as they are self-contained units - no parameter were used to invoke them.\\n\\nAgain with a bit of markup, the Infobox pasted into a VE session, but only the shell transclusion could set up - the parameters would need to be entered by the user in the VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51547\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374842820, 'dateModified': 1700062714, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52091', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Paste in Firefox with privacy option enabled behaves strangely: rich text appears, but in reality paste has failed', 'description': {'raw': 'The paste operation on Firefox behaves strangely when dom.event.clipboardevents.enabled = false\\n(which is exposed in the UI of several extensions)\\n\\nWhen disabled, rich text appears to have been pasted into VE, with links in blue (but the link isnt editable), but in reality the paste has failed to change the underlying data in VE.\\n\\nIf the user starts typing, the pasted richtext disappears.\\n\\nIf the user saves immediately after the paste, the richtext remains visible in the VE, but the save only adds blank lines instead.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374841620, 'dateModified': 1735598083, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52089', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog should also display the actual parameter name as well as the display name', 'description': {'raw': \"When you start a new transclusion dialog for a template which has the templatedata specified it shows a list of the parameters with the label on the left and the actual parameters in grey on the right. This is good for power users who know the parameters. \\n\\nWhen you choose a parameter which has a value specified you can see the label, but you can't see what the actual parameter is. This would be quite handy and could use the same grey style as in the list.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374838980, 'dateModified': 1643973222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52087', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide buttons for locally-configured frequent edit summary contents', 'description': {'raw': \"Wikipedias in some languages, among them Polish, Russian, Ukrainian and Hebrew, have a gadget that shows a list of frequent edit summaries near the edit summary field in source editing mode.\\n\\nHere are the source samples:\\n\\nPolish: https://pl.wikipedia.org/wiki/MediaWiki:Gadget-edit-summaries.js\\nHebrew: https://he.wikipedia.org/wiki/MediaWiki:Gadget-Summarieslist.js\\n\\nMany users in the Hebrew Wikipedia complained about the lack of this gadget in the VisualEditor. This could be an enhancement request, but given that for several languages it's an integral part of the editing interface for these languages, it's a regression for them.\\n\\nAdding this as a feature should be very easy, given that it's quite simple and the existing gadgets' code can be reused. Localization and customization for every project can be done on a MediaWiki page with a list of summaries for that project.\\n\\n--------------------------\\n**See Also**:\\n{T50274}\"}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1561117513, 'spacePHID': None, 'dateCreated': 1374828360, 'dateModified': 1561117514, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52085', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When user is saving a page subsequently deleted after they started editing, show them <confirmrecreate\\u200e>', 'description': {'raw': 'Steps to reproduce:\\n1. Open VE on a sandbox\\n2. In a different window, delete the sandbox\\n3. In the VE window, change the text in the sandbox and save the page\\n\\nExpected results:\\nSomething similar to the SE, which asks \"\\nUser xxx (talk) deleted this article after you started editing it, with a reason of:\\n\\n    blah \\n\\nPlease confirm that you really want to recreate this article.\" with a checkbox\\n\\nActual results:\\nBackend error message is displayed, and there is no option to ignore this error.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'dateClosed': 1416944610, 'spacePHID': None, 'dateCreated': 1374805260, 'dateModified': 1438734491, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52073', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make ve.ce.MWBlockImageNode.prototype.getCssClass nicer', 'description': {'raw': \"It should look at the attributes directly rather than take them as parameters. We should move the folding of all sorts of types into 'default' or 'none' in there. We should set the CSS class in one place rather than two different ones.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374792420, 'dateModified': 1643973222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52065', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Merge Poem extension into MediaWiki core', 'description': {'raw': 'The Poem extension has almost as much extension setup as it has functionality. Bundling it with MediaWiki is silly, it should simply be merged into core.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement\\n**Whiteboard**: migrate Poem extension bugs to core post-resolution'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374788640, 'dateModified': 1680395928, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52061', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Gracefully handle when available browser UI features are disabled (rather than refusing to load)', 'description': {'raw': 'VE should work as expected without clipboard access.  Currently it only half initalises.\\n\\n1. Install Kill Evil in Chrome or similar\\n2. Edit any page\\n\\n(https://chrome.google.com/webstore/detail/kill-evil/epieehnpcepgfiildhdklacomihpoldk)\\n\\nResult:\\nhttps://en.wikipedia.org/wiki/File:Missing-ui-ve.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1718626265, 'spacePHID': None, 'dateCreated': 1374713100, 'dateModified': 1718626265, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52008', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CSS munging causing absolutely-positioned chess diagrams(?) to break', 'description': {'raw': \"A very common chess template on many Wikipedias recommends using '|=' , and most instances of chess boards use this syntax\\nhttps://en.wikipedia.org/wiki/Template:Chess_diagram#Standard_diagram\\nhttps://de.wikipedia.org/wiki/Vorlage:Schachbrett#Standarddiagramm\\n\\nOn German Wikipedia, editing the template strips the '=' signs.  This article is on the parsoid topfails\\nhttps://de.wikipedia.org/wiki/Edward_Lasker?veaction=edit\\nhttp://parsoid.wmflabs.org:8001/topfails/1\\n\\nThere are 900 uses of these chess templates on German Wikipedia.\\nhttps://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/Vorlage:Schachbrett&limit=750\\nhttps://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/Vorlage:Schachbrett-klein&limit=115\\nA few more of\\nhttps://de.wikipedia.org/wiki/Vorlage:Schachbrett-10x10\\nhttps://de.wikipedia.org/wiki/Vorlage:Schachbrett-8x10\\nhttps://de.wikipedia.org/wiki/Vorlage:Schachbrett-Chaturanga\\n\\nThe syntax is used on many other WPs, incl. eswp, frwp, plwp and ruwp\\nhttps://es.wikipedia.org/wiki/Plantilla:Diagrama_de_ajedrez#Diagrama_est.C3.A1ndar\\nhttps://fr.wikipedia.org/wiki/Mod%C3%A8le:Diagramme_d%27%C3%A9checs\\nhttps://fr.wikipedia.org/wiki/Alexandre_Alekhine\\nhttps://pl.wikipedia.org/wiki/Szablon:SzachyDiagram\\nhttps://ru.wikipedia.org/wiki/%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:%D0%A8%D0%B0%D1%85%D0%BC%D0%B0%D1%82%D0%BD%D0%B0%D1%8F_%D0%B4%D0%B8%D0%B0%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B0\\n\\nOn English, the VE UI can go into massive layout problems, but the UI issues may all be due to the Parsoid issue.\\nhttps://en.wikipedia.org/wiki/French_Defence?veaction=edit\\nThe number of uses on enwp appears to be in the same ballpark as dewp\\nhttps://en.wikipedia.org/w/index.php?title=Special:WhatLinksHere/Template:Chess_diagram&limit=900\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\n{T55226}\\n{T53166}\\n{T73404}\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429477508, 'spacePHID': None, 'dateCreated': 1374655260, 'dateModified': 1438734495, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51932', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template parameters should be in TemplateData recommended order', 'description': {'raw': 'Several users on the English Wikipedia, most recently Salix, have requested that the parameters for templates should be in the recommended order not alphabetical order. \\n\\nFor example in {{tracklist}} it lists \"Track10\" before \"Track2\", and in the various citation templates, \"First\" and \"Last\" should be adjacent.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1389755241, 'spacePHID': None, 'dateCreated': 1374654480, 'dateModified': 1443276376, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51930', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Warning for blank reference list is confusing', 'description': {'raw': 'Removing the last reference on a page, with <references/> present, causes the waring:\\n\\nThere are no references with the group \"\" on this page.\\n\\nThat should be \\n\\nThere are no references on this page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380747863, 'spacePHID': None, 'dateCreated': 1374580740, 'dateModified': 1417572828, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51873', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow per-wiki/-namespace disabling of formatting styles e.g. page title', 'description': {'raw': 'On the English Wikipedia the page title formatting level is never used in article space, although I understand it is used on some other wikis. It might be that other wikis do not use a dfferent page style.\\n\\nAccordingly it would be nice to be able to remove/suppress/disable this item from the list on a per namespace (or, less ideally, per wiki) to avoid confusion to new editors. \\n\\nUnless this is absolutely trivial to implement, please regard it as a low priority enhancement request.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374576000, 'dateModified': 1643973222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51864', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Display name of transclusions as a tool-tip when selected', 'description': {'raw': 'At en.wp a user comments:\\n\"The tooltip with a \"puzzle\" icon that appears when clicking on a template should contain the name of the template used. This would allow readers to be aware of which template they\\'re about to change and would make the Templates interface [[self-documenting]], teaching by example the existence of the most common templates.\\n\\nFor example, the next screenshot would contain the word \"Chembox\" besides the puzzle icon:\"\\n\\nScreenshot: [[File:VisualEditor - Template editing 1.png]]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51827'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1416249978, 'spacePHID': None, 'dateCreated': 1374512400, 'dateModified': 1417571678, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51824', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Double-clicking on an image in the image finder inserts it twice', 'description': {'raw': 'If you open up the image finder, identify an image you want and /double/ click on it, the image finder closes and the selected image is inserted twice.\\n\\nDebian/Iceweasel 17.0.7.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1395355791, 'spacePHID': None, 'dateCreated': 1374511980, 'dateModified': 1424894631, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51823', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Note that Wikidata exists in the description text above the read-only language links section in the meta dialog', 'description': {'raw': 'In the site settings dialog you can see a list of language/interwiki links for the current article. There is a explanation text saying those can only be edited in the wikitext editor. Because of Wikidata this is now no longer true for most articles. The text should be adapted and maybe link to the corresponding Wikidata item?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385506384, 'spacePHID': None, 'dateCreated': 1374504240, 'dateModified': 1417572743, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51816', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'There should be help links in every context - dialog boxes, inspectors, etc.', 'description': {'raw': 'I could only find one major button that leads to the help pages - the one at the top toolbar. Ideally, there should be help buttons in every context - dialog boxes, inspector, plugins, etc.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T53237}'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374488460, 'dateModified': 1643973222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51798', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: TemplateData-provided parameters in list should show description in tooltip', 'description': {'raw': 'The description of a parameter in the list of parameters does not always fit in the width of the editing add-parameter box, particularly in firefox (where the font size is apparently larger in than chrome) and when users are using large fonts for accessibility reasons. Where this is the case (or always) the description should be shown in a tooltip on hover or when selected by up/down keyboard prior to insertion.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50354\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51436\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62142'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374419280, 'dateModified': 1643973222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51774', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Broken table, repeated section in diff after VisualEditor edit', 'description': {'raw': 'I recently ran across [https://en.wikipedia.org/w/index.php?title=Polycarbonate&diff=prev&oldid=564618311 this edit].  It seems as though they were trying to fix a spelling correction and inadvertently destroyed a table and had an entire section get repeated.\\n\\nThere was a little [https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Strange_Diff discussion about the diff on the Visual Editor feedback page], where it was mentioned that the diff \"is very strange and [the commenter didn\\'t] recall seeing anything similar\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-2qzpsivaeuezrxqtzhwn', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412977739, 'spacePHID': None, 'dateCreated': 1374416280, 'dateModified': 1469823942, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51772', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Have a \"remove from page\" button in media settings dialog', 'description': {'raw': \"An English Wikipedia user familiar with the transclusion dialog expected thatthe way to remove an  image from the article was using a remove option in the media dialog. Such an option does not exist, and they couldn't work out another way of removing the image other than selecting and deleting the characters around and including the slug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437787301, 'spacePHID': None, 'dateCreated': 1374362700, 'dateModified': 1437787301, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51764', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"sees unreviewed pages despite their ns isn't reviewable\", 'description': {'raw': 'After https://pl.wikipedia.org/w/index.php?title=Pomoc:VisualEditor/Skr%C3%B3ty_klawiszowe&oldid=37098556&diff=cur this edit it sees unreviewed pages and distinguishes between stable and unreviewed versions despite a) on this page, both versions are autoreviewed b) even if points [[Wikipedia:VisualEditor/Nawigacja]] (transcluded) out as pending rewiev - the project namespace is not reviewable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-gf5juv3z3p75bykrcrhf', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374328320, 'dateModified': 1443004385, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51747', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for ka (მ/კ)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633775, 'spacePHID': None, 'dateCreated': 1374266340, 'dateModified': 1417573080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51713', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for os (Б/???)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633751, 'spacePHID': None, 'dateCreated': 1374266340, 'dateModified': 1417573080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51712', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for ru/ky (Ж/K)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633741, 'spacePHID': None, 'dateCreated': 1374266340, 'dateModified': 1417573080, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51711', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for nl (V/C)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374636861, 'spacePHID': None, 'dateCreated': 1374266280, 'dateModified': 1417573076, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51710', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for eu (L/E)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633960, 'spacePHID': None, 'dateCreated': 1374266280, 'dateModified': 1417573077, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51709', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for es (N/C)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633947, 'spacePHID': None, 'dateCreated': 1374266220, 'dateModified': 1417573078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51707', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for pt (N/I)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633901, 'spacePHID': None, 'dateCreated': 1374266220, 'dateModified': 1417573078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51706', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for gl (N/C)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633878, 'spacePHID': None, 'dateCreated': 1374266220, 'dateModified': 1417573078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51705', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for it (G/C)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633829, 'spacePHID': None, 'dateCreated': 1374266220, 'dateModified': 1417573079, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51704', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for fr (G/I)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633813, 'spacePHID': None, 'dateCreated': 1374266220, 'dateModified': 1417573079, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51703', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Set correct text annotation buttons for hu (B/D)', 'description': {'raw': 'This is how it is configured in WikiEditor; will require icon creation.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374633800, 'spacePHID': None, 'dateCreated': 1374266220, 'dateModified': 1417573079, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51702', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Auto-hide \"You\\'ve entered wikimarkup\" warning when the user has removed the markup', 'description': {'raw': \"At the moment wikimarkup being entered into the VE triggers a notice warning the user that it won't work - this notice then has to be actively dismissed. It'd be nice if, should the user remove the problematic markup, the notice would vanish.\\n\\nI'm popping this in as a low-priority enhancement: I appreciate the VE team has active breakage to focus on.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52386\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=70168\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391815339, 'spacePHID': None, 'dateCreated': 1374265800, 'dateModified': 1444199717, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Move-dragging a media item shows the copy cursor on Mac/Safari', 'description': {'raw': 'If I move an image around, I see the \"copy\" cursor, even though I\\'m just moving.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437787097, 'spacePHID': None, 'dateCreated': 1374262740, 'dateModified': 1439331216, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51696', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Section edit links don't work like wikitext where the section is transcluded from elsewhere\", 'description': {'raw': \"http://it.wikipedia.org/wiki/Template:Cassetto is AFAIK the Italian version of Hidden (it shouldn't be used in articles).\\n\\nhttp://it.wikipedia.org/wiki/Utente:Superchilum features a cassetto named Tudù which transcludes the subpage Utente:Superchilum/do.\\n\\nIf you try and edit the first section in that cassetto, Varie, with the classic editor, you correctly manage to edit the /do subpage; VE instead only allows editing the main userpage.\\n\\nThanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1663955476, 'spacePHID': None, 'dateCreated': 1374231000, 'dateModified': 1663955476, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51675', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Editing window does not scroll when dragging', 'description': {'raw': 'When dragging an item in the visual editor (tested with image and text), the editing window does not scroll up or down when you reach the top or bottom of the window. This means you have to make several consecutive drag and drop actions to move an item within a long article/section. Per Bug 51665 the image must be separately selected before you are able to drag it (i.e. each movement requires two mouse clicks).\\n\\n**See Also**:\\n{T36307}\\n{T75240}'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374226320, 'dateModified': 1442446922, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51669', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When dragging content, possible places to place content (e.g. a line before the head of a section, or at the end of the page) should appear when the content gets near', 'description': {'raw': 'If you want to move an image to the start of a section in Visual Editor the logical course of action is to drag it to before the first character of the first word of the section.\\n\\nA user of Firefox 21 reports this does not work at all, in my testing in Firefox 22 it appears to work only occasionally.\\n\\nThe counter-intuitive dragging the image to after the last character of the section title does work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54756\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65883'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403061603, 'spacePHID': None, 'dateCreated': 1374225180, 'dateModified': 1443278238, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51666', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Surface should respect the default state of collapseable templates', 'description': {'raw': 'A user on English Wikipedia requests that templates such as navigation boxes that display as collapsed by default when viewing should display as collapsed by default when editing.\\n\\n\"Currently, navigation boxes are always uncollapsed when editing. This can be quite annoying when having to deal with big ones like {{The Beatles}}, e.g. on \"I\\'m a Loser\", also it might be confusing editors into believing that this part of a page can easily be edited.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374223320, 'dateModified': 1526492316, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51664', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tool to set/unset text as big/small', 'description': {'raw': ''}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1470421262, 'spacePHID': None, 'dateCreated': 1374158760, 'dateModified': 1476558749, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51613', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tool to set/unset text as subscript', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376619792, 'spacePHID': None, 'dateCreated': 1374158700, 'dateModified': 1417572946, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51612', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tool to set/unset text as superscript', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376619787, 'spacePHID': None, 'dateCreated': 1374158700, 'dateModified': 1417572946, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51611', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tool to set/unset text as strikethrough', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375865291, 'spacePHID': None, 'dateCreated': 1374158700, 'dateModified': 1417572950, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51610', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tool to set/unset text as underlined', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376619782, 'spacePHID': None, 'dateCreated': 1374158700, 'dateModified': 1417572946, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51609', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Show two editing/view source tabs at all times, even if you can't edit page because it's protected\", 'description': {'raw': 'When viewing an article you have permission to edit, you see two tabs at the top - \"Edit\" and \"Edit source\". When viewing an article you don\\'t have permission to edit, you see only one - \"view source\".\\n\\nThis is not good UI design There needs to always be the same number of tabs displayed. Ideally there should be tabs to \"view source\" and \"view visual source\" (with better wording though!), see Bug 51547.\\n\\nIf a read-only editor is not possible or not available then that tab needs to pop up a message saying that editing is restricted currently/until xx:xx for <log entry> and that they can view the wikitext source if they want (linked to an explanation what that means).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385386552, 'spacePHID': None, 'dateCreated': 1374077880, 'dateModified': 1427495377, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51549', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a \"view VE\" mode / disable editing for protected pages', 'description': {'raw': 'There should be a view-source equivalent for the visual editor so that people can see the page in VE as if the could edit it. It should allow them to interrogate things like template, so they can find out which template is producing what they see and how it does that. ~~When VE can cope with copy+paste, then~~ this will also allow them to copy and paste the relevant image/template/whatever to whatever article they are working on.\\n\\n**See Also**:\\n* T54004\\n* T54091'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1555440155, 'spacePHID': None, 'dateCreated': 1374077700, 'dateModified': 1558273688, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51547', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Broken OpenODBC browser plugin causes \"application/iodbc\" to be injected into the page', 'description': {'raw': \"I had OpenODBC's iODBC plugin installed in Safari (latest release, always). After any edit, EMBED tags would be inserted at the top and bottom of the article. This did not occur with the source editor, or any other editable widget, like this one I'm typing in now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51423\"}, 'authorPHID': 'PHID-USER-5tluooawvjfhtqywnxag', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412114235, 'spacePHID': None, 'dateCreated': 1374057480, 'dateModified': 1417571831, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51521', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Rewrite VisualEditor's converter to be bottom-up\", 'description': {'raw': \"The data->DOM converter should construct its DOM bottom-up, the way https://gerrit.wikimedia.org/r/74058 already does for annotations. This would enable us to do some cool things like:\\n\\n* Pass childDomElements to nodes and meta items (already done for annotations)\\n* Pass data content in addition to DOM content?\\n* Allow nodes and meta items to unwrap themselves by returning an empty array (already done for annotations)\\n** We could implement unwrapping of generated wrapper paragraphs using this feature\\n* Possibly change the API so that instead of returning an array of DOM elements, the toDomElements function is responsible for appending its children.\\n** This could replace handlesOwnChildren, and enable model types with complex output\\n\\nFor DOM->data it's not as straightforward. We could experiment with bottom-up (outside-in, really) building there too, but it would be a bit less clear how things would work, and whether the copying involved would affect performance (although I believe we may already do a fair bit of copying around as it is).\\n\\n\\nThis may be my pet project for my flight to Wikimania, or I may end up doing this sooner if there's time.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '40', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374029040, 'dateModified': 1643973223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51501', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Get rid of dmRendering stuff in ce.MWInternalLinkAnnotation', 'description': {'raw': \"Right now, ce.MWInternalLinkAnnotation obtains a DM rendering to get the computed href. We should factor out href computation so that this isn't needed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382985970, 'spacePHID': None, 'dateCreated': 1374014700, 'dateModified': 1417572819, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51487', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Switching to mobile view and back leaves cookie behind', 'description': {'raw': 'If someone is clicking on \"Mobile View\" and then back to \"Desktop\", a stopMobileRedirect cookie is left behind. This cookie will disable central notices on all wikimedia sites perpetually\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1376950515, 'spacePHID': None, 'dateCreated': 1374004080, 'dateModified': 1428477466, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51465', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Use a \"broken link\" icon as the \"remove\" button in the link inspector, instead of a rubbish bin', 'description': {'raw': 'There is consensus for a change to this element here: http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Dustbin_icon_not_intuitive_for_.22unlink.22\\n\\nTo summarize - the garbage can icon to remove a link is not intuitive.  Users may be unsure of its function, or believe it will remove the highlighted text, rather than just the link.  Most other editing UI\\'s employ a broken link for this function, so it will be more familiar.\\n\\nSuggested improvement:\\n\\n*Replace \"Garbage Can/Dustbin\" with a \"broken link\" icon (example:http://us.fotolia.com/id/49483380)\\n\\n*Replace current rollover text \"Remove\" with \"Unlink\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403977522, 'spacePHID': None, 'dateCreated': 1374002400, 'dateModified': 1441911419, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51464', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br> at the start of a heading\", 'description': {'raw': \"See:\\nhttp://en.wikipedia.org/w/index.php?title=User%3ACananian&diff=564446937&oldid=564446873\\n\\nI was adding a heading (after a <!-- ... --> comment) and the diff stuck a <br> inside the ==heading==.\\n\\nI'm assigning this bug to VE for the moment, but it could be a parsoid bug.  I need to see the intermediate parsoid HTML generated for the change to tell one way or the other.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1447795442, 'spacePHID': None, 'dateCreated': 1373986620, 'dateModified': 1447795454, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51444', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Leading colon in link label is wrongly removed from wikitext', 'description': {'raw': '```\\n[subbu@earth:~/work/wmf/parsoid] echo \\'<a rel=\"mw:WikiLink\" href=\"./Foobar\">:foobar</a>\\' | php bin/parse.php --html2wt\\n[[:foobar]]\\n\\n[subbu@earth:~/work/wmf/parsoid] echo \\'<a rel=\"mw:WikiLink\" href=\"./Foobar\">:foobar</a>\\' | php bin/parse.php --html2html --body_only\\n<p data-parsoid=\\'{\"dsr\":[0,11,0,0]}\\'><a rel=\"mw:WikiLink\" href=\"./Foobar\" title=\"Foobar\" data-parsoid=\\'{\"stx\":\"simple\",\"a\":{\"href\":\"./Foobar\"},\"sa\":{\"href\":\":foobar\"},\"dsr\":[0,11,2,2]}\\'>foobar</a></p>\\n```'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373984340, 'dateModified': 1589732496, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51442', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Display a useful message instead of an empty table for templates that take no parameters', 'description': {'raw': 'Currently, if you use TemplateData for a template without any parameters, you still have to create an empty \"params\" in the JSON (not really important), but you also end up with a \"Template parameters\" table with just the title line (Parameter\\tDescription\\tType\\tDefault\\tStatus).\\n\\nRather than displaying an empty table, I think it would be better to display no table at all, or a simple message saying that no parameters are defined for this template.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-o34e5i3eq4nstbvcf26w', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1424310501, 'spacePHID': None, 'dateCreated': 1373960160, 'dateModified': 1434061888, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Broken DivX browser plugin causes \"myEventWatcherDiv\" to be injected into the page', 'description': {'raw': 'Seeing this more often now with VE and think it may be a couple different issues (not all on our side) but want to see what we can do to stop it and or lessen impact. This is currently being added to the security queue because I\\'m a bit concerned about some of the symptoms and worry it could be an injection vulnerability (see below). If we rule out a security concern I\\'m obviously happy with it being moved.\\n\\nEditors are making a normal edit and div\\'s are being inserted like \\n\\n<div id=\"myEventWatcherDiv\" style=\"display:none;\"></div>\\n\\noften at the start and end of the page. \\n\\nGoogling around it seems they may be inserted by a common 3rd party plugin (divX?) but it is in no way clear. It also seems to be interacting weirdly with VE because it isn\\'t only being inserted it\\'s inserting WITHOUT <nowiki> tags which is what you\\'d expect if someone put a div in (see https://en.wikipedia.org/w/index.php?title=User:Jalexander/sandbox&diff=564465081&oldid=553572859 ). Could it be being injected somehow around VE and/or parser? \\n\\nExamples:\\nhttps://en.wikipedia.org/w/index.php?title=Spank!_The_Fifty_Shades_Parody&diff=prev&oldid=564448990\\nhttp://en.wikipedia.org/w/index.php?title=Kendra_Morris&diff=prev&oldid=564426900\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51521'}, 'authorPHID': 'PHID-USER-f6l3bchko2ogbi4poj24', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1427403001, 'spacePHID': None, 'dateCreated': 1373954100, 'dateModified': 1438734509, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51423', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide some way for out-of-skin places icons (e.g. featured star) to appear where they \"should\" and be editable', 'description': {'raw': \"In view mode, [[Template:Top icon]] places the featured star or good article at the top right hand corner.\\n\\nAfter loading a FA or GA or English Wikipedia, the featured star or good article icon appears where the template is, which is often down the bottom.  This is perfectly acceptable except for the 'where did it go?' feeling, but maybe a plugin could come up with a better UI design for topicons, geocoords, etc.\\n\\nAlso templates without any real estate (like {{Use dmy dates}} and {{Use Australian English}}) 'disappear' entirely.\\n\\nhttps://en.wikipedia.org/wiki/Angels_Brought_Me_Here?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51322\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373941680, 'dateModified': 1643973223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51420', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Automatically build the option description for visualeditor-enable', 'description': {'raw': 'Forked from the original request at bug 48666 which was solved by making the preference hidden, as intended.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398713475, 'spacePHID': None, 'dateCreated': 1373933760, 'dateModified': 1443276381, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51411', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Create i18n toolbar icon for bold for Portuguese, Spanish and Galician', 'description': {'raw': 'As in Bug T53330, I would like to request the icon for \"Bold\" to be an \"N\" (from \"Negrito\") in Portuguese (\"pt\" and \"pt-br\").\\n'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374771717, 'spacePHID': None, 'dateCreated': 1373919300, 'dateModified': 1689316952, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51392', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"mw.notify notifications can't be removed/hidden programmatically\", 'description': {'raw': \"Use case:\\n* The user opens VisualEditor\\n* The user types something that looks like wikitext\\n* VE notices and displays an mw.notify bubble with autoHide:false\\n* The user leaves VE by clicking on the Read tab\\n* The editor is torn down and we go back to view mode, but the bubble persists\\n\\nI would like to be able to remove this bubble when the editor is torn down, but mw.notification doesn't expose an API for this. There is a .close() method on Notification, but there's no way to get the Notification object created by mw.notify().\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1382188535, 'spacePHID': None, 'dateCreated': 1373853480, 'dateModified': 1382188535, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51338', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Deleting new line icon (\"↵\") between two links has no effect (?)', 'description': {'raw': 'If an article has \\n\\n[external link]\\n[external link]\\n\\nIt is rendered in VE as:\\n\\n[external link]↵[external link]\\n\\nSelecting the ↵ and pressing delete causes the ↵ to be removed, however the link break is not removed, and saving says that there are no changes.\\n\\nExample:\\nhttps://en.wikipedia.org/wiki/Otis_%28album%29?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429478524, 'spacePHID': None, 'dateCreated': 1373850900, 'dateModified': 1438734510, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51336', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support creation of auto-numbered external links and to convert them to labeled ones', 'description': {'raw': 'The way VisualEditor handles links with square brackets, but no explicit anchor, can be confusing.  These links are generally discouraged on English Wikipedia, but still occasionally used.\\n\\nAn example is https://en.wikipedia.org/w/index.php?title=User:Superm401/Sandbox&veaction=edit&oldid=564175896 .  The wikitext for this is just [http://example.com], which renders as a linked [1] (or whatever number it is in the page)\\n\\nHowever, you should edit the latest version of a page for testing this.  When you edit an oldid page, you won\\'t be able to reproduce the \"Save page\" disable behavior I mention below.\\n\\nVisualEditor lets you backspace to remove the characters one by one, which does not really reflect the model of how the link works.  After one or more is removed, \"Save page\" un-greys.  However, when you go to review the changes, it says, \"Could not start the review because your revision matches the latest version of this page.\"\\n\\nIt does let you remove the link entirely, but to do so you need to explicitly remove each character (not just backspace once to delete the whole thing).\\n\\nDo a fresh load of the edit page (separate test).  Then, click the chain icon next to the link.  Then, press enter twice to exit the link dialog.  This time, review changes works.  The wikitext becomes:\\n\\n[http://example.com <nowiki>[1]</nowiki>]\\n\\nIt probably should not change the link if you simply enter the link dialog and press enter without changing anything.  Also, forcing it to text like this is inconsistent with what happens if you delete the right bracket (see above).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409962487, 'spacePHID': None, 'dateCreated': 1373772420, 'dateModified': 1441912223, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51309', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Default search text for images should ignore text before / in namespaces which support sub-pages', 'description': {'raw': 'From English Wikipedia, John Broughton (♫♫) 22:40, 12 July 2013 (UTC):\\n\\nIt\\'s not a high priority, but still, a suggestion: the default search text, for an image search, is the complete page name. So, for example, if someone is editing a draft article, at User:WhateverEditorName/Article name, the default search text is \"WhateverEditorName/Article name\". It would be better if the default ignored the final slash and all text to the left of it; in this case, it would mean the default search would be \"Article name\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401923120, 'spacePHID': None, 'dateCreated': 1373722680, 'dateModified': 1417572290, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51290', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Maxthon mobile browser click on link opens the link', 'description': {'raw': 'When using the Maxthon browser, clicking on a link (wiki or external) opens the link instead of allow ther to alter the link object.\\n\\nAfter the linked page is opened, returning to the VE shows the link object icon which alllows the link to be altered.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1598732594, 'spacePHID': None, 'dateCreated': 1373671080, 'dateModified': 1598732594, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51269', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Initial (PHP-rendered) template display misaligned in Firefox', 'description': {'raw': 'Copied from English Wikipedia:\\n\\nEditing Gol Transportes Aéreos Flight 1907#Criminal proceedings I added two cleanup templates, {{update}} and {{prose}}. In the visual editor the two templates were differently left-aligned and different lengths, despite saving and displaying correctly. Reopening the page in the visual editor, the templates appear at their correct size and alignment, but do appear with an apparent blank line between them. Thryduulf (talk) 14:04, 12 July 2013 (UTC)\\n\\nSee screenshot: \\nhttp://en.wikipedia.org/wiki/File:Visual_Editor_screenshot_-_templates_not_aligned.png\\n\\n****\\nI could replicate this on Firefox (Windows 7) but not Chrome.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1421778486, 'spacePHID': None, 'dateCreated': 1373654340, 'dateModified': 1438734515, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51252', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If making a null change, the \"Your edit was saved\" message appears, even if there were no changes and so it wasn\\'t', 'description': {'raw': 'I was following Sherry\\'s kind advices in my sandbox at enwp http://en.wikipedia.org/wiki/User:Elitre_(WMF)/Sandbox:\\n<<you can create an {{Infobox person}}, with parameters like \"name\" and \"occupation\".  Within those parameters, you can type the wikicode for any templates you want.  For example, you can give it a name parameter of \"Alice Expert((citation needed|date=July 2013}}\", which later gets processed properly as a template. >>\\nAn infobox appeared (well, a box with my sandbox title, actually), I saved, \"your edit was saved\" message appeared, the box isn\\'t in the page anymore.\\nTried again, same thing. No trace of my activity in the history. Win 7, Vector, both Chrome and FF.\\n\\nThanks,\\nE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=52640'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1406680806, 'spacePHID': None, 'dateCreated': 1373644020, 'dateModified': 1443278241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51243', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Suppression of Cite error in templates still paints a phantom', 'description': {'raw': 'Screenshot\\n\\nPreviously we had an issue that the cite extension would throw an error if you had a reference inside a template. That message is now suppressed, but only suppressed - it generates a substantial visual artefact on mouseover that previously contained the error message. See screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11227}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392426157, 'spacePHID': None, 'dateCreated': 1373635140, 'dateModified': 1417572731, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51236', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Matching pages list in link dialog should support right-click / ctrl+click to open page in a new window/tab', 'description': {'raw': 'A few users at itwp requested that the list of articles you can choose as a wikilink target supports right-click on each title to view the page in another tab; and that disambiguation pages in the same list appear differently (maybe italicized as it currently happens in MediaWiki special pages?) Thanks!\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415310757, 'spacePHID': None, 'dateCreated': 1373580540, 'dateModified': 1441912228, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51205', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Context menu should appear in floated element, not in float origin', 'description': {'raw': 'Screenshot of problem\\n\\nWhen a page contains multiple floated blocks after one another that each have a context menu (e.g. both transclusion) the ones after the first get the context menu in the wrong place. Namely on the second \"line\" of the article instead of where the element actually is (much further down).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11059}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1525988938, 'spacePHID': None, 'dateCreated': 1373540820, 'dateModified': 1525993065, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51167', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: CSS munging causing CSS image cropping template {{Css Image Crop}} to display wrong portion of image', 'description': {'raw': 'Go to https://en.wikipedia.org/wiki/Mohammad_Azharuddin - look at the infobox image. Then hit \"edit\". I have no idea what\\'s happening, but it shouldn\\'t be.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\n{T53932}\\n{T55226}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429615760, 'spacePHID': None, 'dateCreated': 1373539980, 'dateModified': 1438734515, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51166', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Respect MediaWiki\\'s \"useeditwarning\" user preference to disable leaving while editing warning', 'description': {'raw': 'If would be nice for power users to have an option to disable the popup warning that occurs when you are trying to leave the edit mode while you have done some editing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1397849101, 'spacePHID': None, 'dateCreated': 1373395140, 'dateModified': 1443276385, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51057', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Ctrl+Shift+Space/Opt+Space to insert a non-breaking space (NBSP)', 'description': {'raw': 'Editor requests support for adding non-breaking spaces (&nbsp;), keyboard shortcut?\\n\\nFrom MediaWiki Feedback:\\n\\nHow do I enter a no-break space (& nbsp;) into the source text via the keyboard? Something like Ctrl+Space would be nice … And, BTW, can I see the difference between a regular space and a no-break space?\\n\\nTroubled @sset Work • Talk • Mail\\u200e18:03, 8 July 2013\\n\\n--------------------------\\nAlternative: {T70429}'}, 'authorPHID': 'PHID-USER-ttyyrgsrkyonct7hizgv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1618448301, 'spacePHID': None, 'dateCreated': 1373383320, 'dateModified': 1689773252, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51045', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Ability to switch image used whilst maintaining the caption and other settings', 'description': {'raw': 'You should be able not only to change image caption, but select another image.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54285'}, 'authorPHID': 'PHID-USER-s2t4lzis4swnj7hbvkgn', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404351379, 'spacePHID': None, 'dateCreated': 1373372220, 'dateModified': 1443278241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51033', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When inserting a media item, search Commons for the Wikidata item this page represents (if available) rather than title', 'description': {'raw': 'Try to add image to http://uk.wikipedia.org/wiki/29er_(%D0%B2%D0%B5%D0%BB%D0%BE%D1%81%D0%B8%D0%BF%D0%B5%D0%B4) \\n\\nIt suggests no images for article \"29er (велосипед)\", but it will if you search by Commonscat template parameter or english interwiki\\n\\n--------------------------\\n**See Also**:\\n{T54464}'}, 'authorPHID': 'PHID-USER-s2t4lzis4swnj7hbvkgn', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373372040, 'dateModified': 1551258678, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51031', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide simultaneous access to editor and edit summary', 'description': {'raw': 'Two editors have commented independent in different place over the weekend on English Wikipedia about how they wish they could access the edit summary while using the VE instead of on save, because they track their changes as they go.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373304120, 'dateModified': 1643973224, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50961', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reduce padding in editnotice popup because some existing edit notices already have some margin', 'description': {'raw': \"An editor from pt.wikipedia writes:\\n\\n[E]ditnotices seems strange inside the flyout because there's a weird padding inside the popup, without the padding the templates would look nicer (there´s already padding in most edinotices templates by default). Dianakc (talk) 23:56, 6 July 2013 (UTC)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373302800, 'dateModified': 1688418785, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50956', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Messing up Math formulas', 'description': {'raw': \"Several concerns noted about VisualEditor messing with math formulas when (evidently) the user was not attempting to edit the formula at all.\\n\\nhttps://en.wikipedia.org/w/index.php?title=Raising_and_lowering_indices&curid=11325244&diff=563062676&oldid=560490441\\n\\nhttps://en.wikipedia.org/w/index.php?title=Regression_analysis&curid=826997&diff=563265603&oldid=561802206\\n\\nhttps://en.wikipedia.org/w/index.php?title=Bipartite_double_cover&curid=21241712&diff=563327691&oldid=554035797\\n\\nI'm not sure if this is related to an existing bug or a different kind of thing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373592757, 'spacePHID': None, 'dateCreated': 1373289300, 'dateModified': 1373592757, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50938', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: License text in save dialog is light gray, giving it a 'disabled' appearance\", 'description': {'raw': \"The save dialog uses a gray color on a very small text. This isn't good for contrast, and gives it rather 'light' color which might communicate a 'disabled' state to some users, which you don't want with a license text.\\n\\nJust as with Special:UserLogin, I think we should switch to a slightly darker gray on small text.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-caadsxn4xg5gmxrpn6kz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-caadsxn4xg5gmxrpn6kz', 'dateClosed': 1483659684, 'spacePHID': None, 'dateCreated': 1373232780, 'dateModified': 1483664123, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50904', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide some way of enabling VE on arbitrary pages for all users (e.g. non-ns0 sandboxes)', 'description': {'raw': \"Perhaps when the [[WP:Tutorial]] on enwiki is updated for VE, we will want to enable VE on the tutorial sandboxes.\\n\\nAlso, when VE is enabled for anonymous editors, we might want to turn on VE in the enwiki [[WP:Sandbox]], because otherwise anons won't have anywhere to play with VE (they cannot create user pages).\\n\\nPerhaps a category (similar to the way AFTv5 does it) or MediaWiki page (like Echo blacklist) would be the way to do it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373193180, 'dateModified': 1722169176, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50883', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Place page meta-data in expected order', 'description': {'raw': '**Author:** `KilliondudeWP`\\n\\n**Description:**\\n1) Have categories on a page with a stub tag underneath - https://en.wikipedia.org/w/index.php?title=Rosebud_Ranch&oldid=563208475 (note that this is SOP on enwiki per https://en.wikipedia.org/wiki/Wikipedia:ORDER#ORDER )\\n\\n2) Edit the categories using VE to deleted one and modify another - https://en.wikipedia.org/w/index.php?title=Rosebud_Ranch&diff=563208669&oldid=563208475\\n\\n3) End up with newly formed category underneath the stub template as well as some line breaks taken out. \\n\\nI reported this in #mediawiki-visualeditor while everyone was sleeping. This is something that might just need an enwiki fix since we like to put stub tags under categories.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n* {T51143}\\n* {T55508}\\n* {T74048}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373181360, 'dateModified': 1643973224, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50882', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link input widget should suggest section links', 'description': {'raw': \"When I edited an internal link and pasted in Work_breakdown_structure#Terminal_element as the new link target, the link editor widget thought that it was a new page, because it didn't understand that the # referenced an anchor within that page.\\n\\nHowever, that was just a harmless warning - it did work. So I am classifying this as minor severity, because it is merely an incorrect warning message that could confuse editors.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-bug3zrlooz3bdmi4fyl7', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1718627142, 'spacePHID': None, 'dateCreated': 1373173500, 'dateModified': 1718750862, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50881', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Difficult for users to know what exact version of each extension is running on the cluster', 'description': {'raw': \"This bug was cloned from bug 50120.\\n\\n(In reply to bug 50120 comment #5)\\n> We believe that this is now fixed (due to fixes in Parsoid). Please re-open\\n> if it recurs.\\n\\nHow do you know what version of VisualEditor or Parsoid is running? Looking at Erik's comment (bug 50120 comment 6), I try to go to [[Special:Version]] to figure out what exact versions of Parsoid and VisualEditor are running (for debugging purposes and to figure out if this problem is still present in the latest bleeding edge code) and I find that Parsoid and VisualEditor are both marked as version 0.1.0. Not quite helpful for debugging. Splitting this issue out.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-ll6tmaogat2b5q7tnqas', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404841447, 'spacePHID': None, 'dateCreated': 1373161140, 'dateModified': 1404841447, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50879', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Escape key inside the main editor should cancel VE mode and return to action=view', 'description': {'raw': '**Author:** `gigs`\\n\\n**Description:**\\nI see that a cancel button has been added, which is an improvement, but the escape key should also cancel edit mode.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1645206828, 'spacePHID': None, 'dateCreated': 1373132460, 'dateModified': 1645206828, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50868', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusions editor should support parser functions and variables', 'description': {'raw': 'Parser function syntax is generally {{#function_name : expr1 | expr2 | expr3 | ...}}\\n\\nCurrently VE sees this as a template with name \"#function_name : expr1\" and arguments \"1 = expr2\", \"2 = expr3\", etc. This makes it impossible to edit expr1 in VE.\\n\\nSame for parserfunctions like urlencode and template messages. The transclusions editor should be able to handle them, preferably by invisibly detecting them and failing that with a special, user-selected mode. Until we can, we should show an explanatory message when the user attempts to add one. \\n\\n**See also:**\\n{T54607}'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373104140, 'dateModified': 1685107380, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50855', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide integration as an API service', 'description': {'raw': 'Original Bug title: \\nProvide an API to activate VE on arbitrary textareas for Gadgets and user scripts and document it at [[:mw:VisualEditor/API]]\\n\\nPlease also create a mailing-list for those API updates.\\n\\nIssue:\\nSince users will not be able to understand Wiki-Markup, please provide and API for turning-on VisualEditor on <textarea>s. Example use case would be the Translate Extension where translators still have to enter wiki-markup or LiquidThreads or whatever is adding Wiki-Markup to a page.\\n\\nProviding an API to Gadget authors and other tools is an important matter; nearly all edits are made through gadgets at certain pages; thus it is not just an \"enhancement\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fgjrqsoj4hk6ezzjdea4', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373053800, 'dateModified': 1643973225, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50827', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion display garbled after removing parameter (CSS caching issue)', 'description': {'raw': 'narrow display\\n\\nSeen in Chrome at least\\n\\n* click Transclusion\\n* add a Template; add-parameter display is fine\\n* add a parameter to the template\\n* click Remove parameter\\n\\nresulting display is too narrow and does not display fully\\n\\n* add a new parameter in the garbled display\\n\\ndisplay of parameter value show echoed/ghost characters as user types into parameter input\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11254}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373062869, 'spacePHID': None, 'dateCreated': 1373044920, 'dateModified': 1373062937, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50814', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add class name to protected pages, to allow for specific CSS styling of edit area', 'description': {'raw': 'The wikitext editor <textarea> element has a CSS class \"mw-textarea-protected\" when a protected page is being edited. This can be used to provide custom styling for this textarea, mainly in order to alert sysops that they are editing a fully protected page.\\n\\nA similar CSS class name should somehow be provided for VE.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398891900, 'spacePHID': None, 'dateCreated': 1372998120, 'dateModified': 1443276394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50783', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Show a different cursor when Ctrl (Cmd on Mac) is held down, as the interaction will be different', 'description': {'raw': \"If you Ctrl+Click a link in the VE, it'll open (discovered through trial and error). Presumably the cursor when hovering over links while Ctrl is depressed should be the hand icon, rather than the typing icon.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701797038, 'spacePHID': None, 'dateCreated': 1372938780, 'dateModified': 1701797038, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50741', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog informing you that there are \"no unused fields\" looks odd; improve message?', 'description': {'raw': \"Screenshot\\n\\nSee screenshot; not sure this is how it's meant to look, but it's how it looks. If there are no unused parameters it seems like the box notifying you of such should overwrite, rather than sit under, the search box - that's unnecessary functionality if all available parameters exist.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54094\\n\\n**Attached**: {F11039}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1724097630, 'spacePHID': None, 'dateCreated': 1372936920, 'dateModified': 1724097630, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50735', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Drop mw:ExtLink/URL', 'description': {'raw': 'Since Parsoid has dropped it in bug 46027\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373310499, 'spacePHID': None, 'dateCreated': 1372936500, 'dateModified': 1417573140, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50734', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Location map template does not display correctly', 'description': {'raw': '**Author:** `lunarjam.mcgahan`\\n\\n**Description:**\\nMS Word document describing and illustrating the bug\\n\\nSee attached document. O/S is iOS 6.1.3\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**OS**: other\\n\\n**Attached**: {F11914}'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'dateClosed': 1525739028, 'spacePHID': None, 'dateCreated': 1372904400, 'dateModified': 1586702198, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50714', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Compatiblity between the two editors', 'description': {'raw': \"Very often I find that there are some tools that both these editors (VE and the old editor) that I would want to use on the same article. But there is no way to do so.\\n\\nIt would be a very useful feature of the VE if there was some way (direct, or indirect; like through the show preview button) for editors opening an article in VE to be able to edit the same article in the old editor without having to save it or discard the changes made.\\n\\nSuch a feature could also come in handy for other editors who have started editing through VE but couldn't understand the interface/needed to switch because they realised VE could not do an action they wanted\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-65pjzcmoby2fsgzdrfjq', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1373855340, 'spacePHID': None, 'dateCreated': 1372890000, 'dateModified': 1373855340, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50698', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: User preference for reversing the order of [edit | edit source] section links', 'description': {'raw': 'Copied:\\nFor logged in user, can there be a formatting preference to display [edit | edit source] as [edit source | edit]? --J. D. Redding 18:47, 3 July 2013 (UTC)\\n\\nThe user finds it frustrating that he keeps inadvertently selecting \"edit\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=56337'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380214284, 'spacePHID': None, 'dateCreated': 1372879860, 'dateModified': 1417584817, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50688', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pre-annotation is from up-page, so deleting and replacing the first character in a link de-links it; deleting and replacing the first bold character in a word de-bolds it; etc.', 'description': {'raw': 'what it says on the tin; if you remove the first character from [[foo]] to change it to [[moo]], what you actually end up with is m[[oo]].\\n\\nSee also:\\n* T52745\\n* T52945\\n* T55495\\n* T52452'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1600713579, 'spacePHID': None, 'dateCreated': 1372872240, 'dateModified': 1600713580, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50678', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Search for images from fileRepos, rather than hard-coding use of local and Commons', 'description': {'raw': \"ve.init.mw.Platform.js currently hard-codes searching from Commons, even if the wiki doesn't actually load images from Commons. We should do this based on wiki config instead.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388900883, 'spacePHID': None, 'dateCreated': 1372865220, 'dateModified': 1443276395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50673', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Internal links should display the page's URL in the status bar on the browsers that do that\", 'description': {'raw': 'Not sure the technical term, but: if I hover over, for example, the bugzilla \"search bugs\" link, it shows as a URL in the bottom left of firefox, allowing me to identify the destination. The same is true in articles in read mode. It\\'d be good to have this functionality in the VisualEditor, or some other way of more prominently identifying where links are going to: hovering over every. single. one. doesn\\'t really work.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1415226643, 'spacePHID': None, 'dateCreated': 1372840860, 'dateModified': 1441911419, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50646', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Improve VisualEditor's loading performance in Firefox\", 'description': {'raw': 'I imagine this is mostly due to Firefox\\'s JS engine, but I commonly run across articles that take an extremely long time to load the new VisualEditor interface. For example, \"Domestic violence\" and \"Feminism\" take about 30 seconds. Really long articles like \"World War II\" take over a minute. The interface loads in about half that time in Safari. I\\'m using Firefox 21.\\n\\nComparative loading figures:\\n\\n| Article | FF 32, 2014-09 | Cr 37, 2014-09\\n|--|--|--|--|--\\n| Barack Obama | 17.6s | 17.2s\\n|--\\n| Cat | 16.4s | 16.0s\\n|--\\n| Beyoncé Knowles | 25.4s | 7.5s\\n|--\\n| India | 26.8s | 5.6s\\n|--\\n| Richard Nixon | 9.9s | 5.6s\\n|--\\n| Europe | 28.3s | 7.1s\\n|--\\n| English language | 18.2 | 8.0s\\n|--\\n\\n\\n| Article | FF 34.05 2014-12 |Cr 39 2014-12\\n|--|--|--|--|--\\n| Barack Obama | 13.23s | 10.61s\\n|--\\n| Cat | 11.59s |5.82s\\n|--\\n| Beyoncé Knowles | 8.01s|5.13s\\n|--\\n| India | 8.90s |5.64s\\n|--\\n| Richard Nixon | 8.85s|6.36s\\n|--\\n| Europe | 10.31s|6.52s\\n|--\\n| English language |6.98s|5.45s\\n|--\\n'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1595844165, 'spacePHID': None, 'dateCreated': 1372802220, 'dateModified': 1595844166, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50616', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reduce whitespace in transclusion dialog', 'description': {'raw': \"A contributor requests the following:\\n\\nI'm sure this is far down the list of problems, but I think the transclusion editor (and other bits with similar display) have way too much white space. For each parameter one gets two blank lines for every one line with parameter name. That is annoying and when templates have dozens of parameters, as many infoboxes and citation templates do, it creates a lot of extra scrolling to find what one is looking for. I'd suggest reducing the whitespace between parameter names by half. Dragons flight (talk) 18:18, 2 July 2013 (UTC)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385375733, 'spacePHID': None, 'dateCreated': 1372791060, 'dateModified': 1417572748, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50598', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link inspector should preview the linked page (à la Navigation Popups)', 'description': {'raw': 'Disambiguations and other oddities can mean that the first link you select in a typeahead search may not actually be right. You then have to follow the link (which is hard in edit mode) and go looking again.\\n\\nBeing able to get a short preview of the selected link target, similar to what Navigation Popups gadget does when hovering over links, would go miles (kilometers) towards making link selection *awesomer*.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=59208'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1431047236, 'spacePHID': None, 'dateCreated': 1372786320, 'dateModified': 1441911419, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50593', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Transclusion dialog makes it too easy for users to remove the newlines between parameters', 'description': {'raw': \"The template inspector's parameters contain the contents of each parameter, and also a line break, which represents, well, the break between two parameters. When modifying a param, it's all too easy to remove the line break, which results in user-unfriendly things like https://en.wikipedia.org/w/index.php?title=Kidz_Bop_20&diff=prev&oldid=562494239\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=69682\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'dateClosed': 1421036141, 'spacePHID': None, 'dateCreated': 1372775700, 'dateModified': 1438734525, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50584', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Be able to name references manually in the reference dialog', 'description': {'raw': 'If you create a new reference, you can specify a name - great! If you try to modify an existing reference to add a name... https://en.wikipedia.org/wiki/File:VEReferenceEdit.jpg oops.'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372760160, 'dateModified': 1724078774, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50568', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: {{clear}} template phantom generated too large', 'description': {'raw': \"See http://en.wikipedia.org/wiki/United_States_v._Windsor right above the 'Dissents' heading. Clear template covers most of quote box.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50395\"}, 'authorPHID': 'PHID-USER-f6l3bchko2ogbi4poj24', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1429479450, 'spacePHID': None, 'dateCreated': 1372738560, 'dateModified': 1438734530, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50551', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Direct link in revision history to report VisualEditor errors for specific change', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Colorado_River&diff=562465192&oldid=562442392\\n\\nWhen I go here, I have several options for what I can do with the edit:\\n\\n> Revision as of 19:24, 1 July 2013 (edit) (undo) (thank)\\n\\nI\\'d like another option that says \"(this edit was made with VisualEditor and introduced a problem; report it here)\" or something like that. A JavaScript gadget would be dandy, but I\\'m not picky about the implementation details.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1729515165, 'spacePHID': None, 'dateCreated': 1372734540, 'dateModified': 1729515165, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50548', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Drag to move image\" is buggy in Safari 6', 'description': {'raw': 'Screenshot of oddly collapsed resizable area\\n\\nNot sure whether it is specific to Safari 6 but it seems a bit buggy.\\n\\nSometimes when holding down the mouse button the cursor won\\'t change from a  \"move\" cursor to a \"drag/add\" cursor (as if it is a regular hover, \"move\" until it hits the edge of the image and then becomes a regular pointer).\\n\\nAlso when dragging and dropping sometimes it seems to separate the image itself and the thumb container is left behind (!).\\n\\nWhen resizing it seems to sometimes (sorry, can\\'t be move specific yet) collapse into a single dot (see screenshot).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11549}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-lliyevigiycjbybglftk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385379064, 'spacePHID': None, 'dateCreated': 1372721760, 'dateModified': 1417572815, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50537', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Unclosed formatting elements leaking out of transclusions', 'description': {'raw': 'http://parsoid.wmflabs.org/en/User:Adjwilley/sandbox10?oldid=562331693\\n\\nRelevant wikitext:\\n\\n*{{Cite book| last=Fádil-i-Mázindarání | first= Asadu\\'lláh | authorlink = Mírzá Asadu’llah Fádil Mázandarání | year=1967 | title=Asráu\\'l-Á<u>th<u>ár, Vol.I| pages= 453 | publisher=Bahá\\'í Publishing Trust, Tehran | url = http://www.h-net.org/~bahai/areprint/authors/mazandarani/asrar.htm | ref=harv}}\\n\\n(note the <u> isn\\'t opened then closed, but double-opened)\\n\\nOutput HTML (with data-*, about and a few others stripped):\\n\\n<li><span typeof=\"mw:Transclusion\"><a rel=\"mw:WikiLink\" href=\"...\">Fádil-i-Mázindarání, Asadu\\'lláh</a> (1967). <a rel=\"mw:ExtLink\" href=\"...\"><i>Asráu\\'l-Á<u>th<u>ár, Vol.I</u></u></i></a><u><u>. Bahá\\'í Publishing Trust, Tehran. p.<span typeof=\"mw:Entity\">&nbsp;</span>453.</u></u></span><u><u><span class=\"Z3988\"><span style=\"display:none;\"><span typeof=\"mw:Entity\">&nbsp;</span></span></span></u></u></li><u><u>\\n\\n<li>(next item here, note how we\\'re still inside of <u><u>)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'dateClosed': 1590072108, 'spacePHID': None, 'dateCreated': 1372721640, 'dateModified': 1590072108, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50536', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add a notice on load for users of slower computers advising them to use source mode instead of VisualEditor', 'description': {'raw': 'There should be an edit notice whenever someone tries to use VE which says something like \"Slower computers or users trying to use older markup should try editing in the older Editor.\" and link to the older editor. Otherwise we\\'re directly cutting off plenty of editors who can\\'t figure it out, and would have relatively slow internet.\\n\\nP.S. My internet is slow enough to not give a satisfactory VE experience, and I consider myself to have decent Indian speed internets\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-65pjzcmoby2fsgzdrfjq', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372710300, 'dateModified': 1643973225, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50518', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links to current page should show as bold', 'description': {'raw': 'When I add a link to the title of the page, it is displayed as a normal link instead of a <strong class=\"selflink\">.\\n\\nSame problem while editing a page with a \\'selflink\\' already present.\\n\\nThe contributor doesn’t see the article as it will be after saving.'}, 'authorPHID': 'PHID-USER-5pyvkdz65d5h5vxebodc', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1490885389, 'spacePHID': None, 'dateCreated': 1372684440, 'dateModified': 1490885389, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50497', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection over a line (with shift-down) applies formatting changes to second line (where logical selection ends), not just first line (where visible selection ends)', 'description': {'raw': 'Suppose an article contains two lines in Paragraph formatting, and we want to turn the first one into Heading formatting. Select the entire first line (Cursor at beginning of line, Shift-CursorDown) then choose Heading formatting from the selection box at the top. Result: both lines are turned into Headings, not just the first. (Bold and italics formatting changes work correctly and affect only the current line.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1704899273, 'spacePHID': None, 'dateCreated': 1372508580, 'dateModified': 1704899273, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50419', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Add a way to express dependencies between parameters', 'description': {'raw': 'Add a way to mark a parameter to be dependent on an other paramter. For example :\\nWe have following parameters:\\n\"foo1_bar\", \"foo1_baz\", \"foo1_quux\" \\n...\\n \"fooN_bar\", \"fooN_baz\", \"fooN_quux\"\\n\\nfooX_bar required fooX_baz to be used as well, it doesn\\'t require fooX_quux to be used, but if fooX_quux is used, then fooX_bar must have been defined as well\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-2mkpm2voxepwvz7abjug', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372464000, 'dateModified': 1713639918, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50407', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Categories deleted or misplaced when a reference is added (in Opera)', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Stand-your-ground_law&diff=562005779&oldid=561464750 is a good example (hat-tip to MatMaRex)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50120'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1374519751, 'spacePHID': None, 'dateCreated': 1372445760, 'dateModified': 1417573077, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50385', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Template:Listen (and similar sound files) doesn't render the TMH aspects correctly\", 'description': {'raw': 'Screenshot\\n\\nFirefox 21.0, Windows 7 - see screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49896\\n\\n**Attached**: {F11161}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1539835123, 'spacePHID': None, 'dateCreated': 1372417620, 'dateModified': 1540992926, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50365', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link input widget should somehow recognise input text that look like urls without protocol as external links (e.g. \"www.example.org/foo\") and then guess the right protocol', 'description': {'raw': 'This is a legacy of wiki-syntax, where all external links have to begin with the protocol. It would be nice to make the VE link inspector smarter than this.\\n\\n\"www.google.com\" is almost certainly meant to be an external link - if there is an article by this name, then it could be shown in the link inspector dropdown as well, but the option for \"External link\" definitely needs to be there. Even something like \"royal.gov.uk\" should be recognised as a URL.\\n\\nRequiring \"http://\" or some other protocol at the start is confusing for the newbie, as the protocol component of URLs is generally ignored nowadays.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372414560, 'dateModified': 1643973226, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50360', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: FlaggedRevs status box causes blank space down the right side of CE content div', 'description': {'raw': 'Screenshot of bug\\n\\n1. Go to [[de:Special:PendingChanges]]\\n2. Visit one of the linked articles and edit it in VE\\n\\nNotice the wide right margin, caused by the floating FlaggedRevs status box.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11085}'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1405449142, 'spacePHID': None, 'dateCreated': 1372388280, 'dateModified': 1417572027, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50340', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow the user to edit categories at the bottom of the page, similar to HotCat', 'description': {'raw': 'At the moment adding categories (through \"page settings\") involves turning away from the actual content. This is a problem because a lot of categories are dependent on the actual content, which needs to be referred back to - birth or death years, college, etc, etc.\\n\\nSuggestion is:\\n* Show the existing categories in the standard skin location (at the bottom of the page, in Vector)\\n* Make the categories editable there, in some way.\\n\\n----\\nOriginal onwiki comments were [[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_6#Categories_-_display_them.2C_please |archive 6]] \\n> I can see categories when I read an article. I can see them below the editing paraphernalia when I\\'m in Edit Source. But in VE I can only see them by clicking \"Page Settings\", which (a) takes a click and (b) means I can\\'t see any of the article content (eg the hard-to-remember-the-spelling district name, the birth date, etc which I might want to use in creating categories, having seen that they aren\\'t already there). Please display the categories in or around the article, not just as \"Page settings\".\\nand [[https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_7#Categories:_please_display_them_in_VE_-_not_the_right_bug |archive 7]]:\\n> I want to be able to see the categories when I\\'ve got an article open in VE: just as I can see them when reading the article, or when editing it in Edit Source. I don\\'t want to have to click on \"Page Data\" to find out whether or not it\\'s already got categories.\\n\\n--------------------------\\nSee also: {T67518}\\n\\nmerged duplicates: {T53153} and {T71506}\\n'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372262760, 'dateModified': 1574636552, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50239', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Wikitext \"review your changes\" is relatively unhelpful for page creations; consider behaviour', 'description': {'raw': \"See the screenshot. I get that it's sort of a one-sided diff in a <poem> box, but it isn't particularly useful to review since no tweaks made by the VE that are problematic could be picked out; one would have to review the entire article, in markup.\\n\\nI'm not sure if there's a better way to work it or if the answer is just to kill it for new page creations, but.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437786780, 'spacePHID': None, 'dateCreated': 1372171920, 'dateModified': 1437786780, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50180', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: sizing of footnote tags (e.g. [12]) inconsistent.', 'description': {'raw': 'See https://en.wikipedia.org/wiki/Joe_Flacco?veaction=edit - for example, references 24 and 25 under the section \"2012 season: Super Bowl MVP\". It looks like one of them is using Template:R, which may explain the problem, but I\\'m not sure if the icon not rendering properly is a template problem or a VE problem.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437783652, 'spacePHID': None, 'dateCreated': 1372081320, 'dateModified': 1439331198, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50095', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing of headings is broken in IE10', 'description': {'raw': 'Edit [[User:This, that and the other/sandbox/VE6]] in VE using IE10:\\n\\n1. Try modifying the heading text. You have to double-click on the heading to be able to modify it. Hopefully this stupid IE behavior can be worked around.\\n\\n2. Double-click, and modify the heading text. \"Save page\" button is still disabled.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sx63fwaih5kjt7bz4u6z', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409961747, 'spacePHID': None, 'dateCreated': 1372059540, 'dateModified': 1443278247, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50088', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Broken layout of inspector menu, link inspector (others?) in Monobook', 'description': {'raw': 'link icon not square\\n\\nSee attachments. Reproduced in Chrome and Firefox by the original reporter, and me.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11416}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404168883, 'spacePHID': None, 'dateCreated': 1372005420, 'dateModified': 1417572130, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50057', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OutputPage: Don\\'t output mw.loader.state \"loading\" and mw.loader.state \"ready\" for the same module', 'description': {'raw': 'It looks like we currently output both for some modules.\\n\\nCurrent output on a wiki with user and site css/js enabled[1] but empty:\\n\\n<script>if(window.mw){\\nmw.loader.state({\"site\":\"loading\",\"user\":\"loading\",\"user.groups\":\"loading\"});\\n}</script>\\n<script>if(window.mw){\\nmw.loader.load([\"mediawiki.action.view.postEdit\",\"mediawiki.user\",\"mediawiki.hidpi\",\"mediawiki.page.ready\",\"mediawiki.searchSuggest\",\"mediawiki.page.watch.ajax\",\"ext.vector.collapsibleNav\",\"ext.visualEditor.viewPageTarget\",\"skins.vector.js\"],null,true);\\n}</script>\\n<script>if(window.mw){\\nmw.loader.state({\"site\":\"ready\"});\\n}</script>\\n<script>if(window.mw){\\nmw.loader.state({\"user\":\"ready\"});\\n}</script>\\n<script>if(window.mw){\\nmw.loader.state({\"user.groups\":\"ready\"});\\n}</script>\\n\\nThe first one with \"loading\" is always output. The last 3 with \"ready\" are output by OutputPage::makeResourceLoaderLink if $module->isKnownEmpty is true.\\n\\nWe should probably optimise this to just output \"ready\" in the first place.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1412588792, 'spacePHID': None, 'dateCreated': 1371976440, 'dateModified': 1412588792, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50038', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way for users to insert variable magic words', 'description': {'raw': 'https://www.mediawiki.org/wiki/Help:Magic_words#Variables\\n\\n{{CURRENTYEAR}}, {{CURRENTMONTH}], etc. - possibly a pop-up inserter with a brief description of what each do (and their current value?)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62740'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371860100, 'dateModified': 1694173031, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49996', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Table of Contents should be a draggableNode and insert __TOC__ as needed', 'description': {'raw': 'It should be possible for users to modify the location of the TOC (see bug 49224 for getting it shown and updated as they edit), and the system should insert a __TOC__ identifier (that should be silently dropped by Parsoid when not needed?).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371859800, 'dateModified': 1734882892, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49994', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: No way to identify destination, rather than link text, of links', 'description': {'raw': \"Because the VE splits up the destination of a link and the text displayed for it (quite rightly) it's impossible, in VE mode, to identify where links point to without source editing. This is kind of a problem for disambiguation issues, for example. Is there any way that this could somehow be hunt-down-able?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402550246, 'spacePHID': None, 'dateCreated': 1371790440, 'dateModified': 1441912270, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49928', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Support \"substituting\" templates in transclusion dialog', 'description': {'raw': 'User:JohnCD at English Wikipedia writes the following:\\n\"If you enter, for instance, \"Welcome\" in the new template box, on clicking \"Apply changes\" you see the result; but if you enter \"subst:welcome\" you see only {{subst:welcome}}, though after clicking \"Save page\" the result is correct. Should there be a check-box for \"subst\" in the New template dialogue, (a) to save typing it out, (b) to arrange the correct display?\"\\n\\nJames F. suggested this would be good to enter as an enhancement request, since template substitution should be supported.\\n\\nMaggie\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66281'}, 'authorPHID': 'PHID-USER-joqqkabmjmvxeucx4ni2', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371756600, 'dateModified': 1701166677, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49904', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ResourceLoader does not process media queries for printable view with JS-added CSS', 'description': {'raw': 'It seems that the server part of this is already correct.  The client just needs to add printable=1 to requests for JS-wrapped CSS should include printable=1, when the page is in print mode (printabable=yes).\\n\\nThis is necessary to make sure that screen CSS is omitted and print CSS is not wrapped in @media print for this use case.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1507244402, 'spacePHID': None, 'dateCreated': 1371510780, 'dateModified': 1598605547, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49722', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Diff is done with current revision instead of old revision when editing an old revision', 'description': {'raw': 'When I am editing an old revision of a page and then view the diff before saving it is the diff between the current version of the page and my edited version it seems. I was expecting to see the diff between the old revision and my edited version.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1371585157, 'spacePHID': None, 'dateCreated': 1371475440, 'dateModified': 1660961712, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49692', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Caption of a thumb image starting with a link means link inspector icon appears in slug, confusingly', 'description': {'raw': 'Screenshot\\n\\nSee on https://en.wikipedia.org/wiki/Brainbuster for example, at the bottom - screenshot attached. Reproduced in Chrome, Firefox and Safari.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F11473}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402549729, 'spacePHID': None, 'dateCreated': 1371464940, 'dateModified': 1441912276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49680', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"<title> of editing page doesn't respect DISPLAYTITLE\", 'description': {'raw': 'See also: T51633, T52341'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371431700, 'dateModified': 1477600305, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49667', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Use Multimedia/Wikidata's proposed rich structured meta-data in the image insertion dialog\", 'description': {'raw': \"Some suggestions of improvements to the media insertion dialog; this is mostly a brain-dump which we might turn into a tracker later:\\n\\n- a way of accessing the file page, on Commons or elsewhere\\n- a more clear highlighting\\n- maybe slightly enlarging the image\\n- double-click to insert\\n- filter by: …\\n-* media type\\n-* language (mostly specific to audio/video but also maps/diagrams)\\n-* length (audio/video)\\n-* resolution (image/video)\\n-* video bit-depth (image/video)\\n-* audio bit-depth (video/audio)\\n-* sample rate (audio)\\n-* format\\n-* licence\\n-* local vs. Commons\\n\\nNotes:\\n\\nThe image size is based on the largest default thumbnail (the dialog asks for the 300x300px image and then shows it at 150x*px size). Changing this would need to have discussions with Ops about load on the image renderers and possibly changing the default sizes globally.\\n\\nThe filtering will have to wait for Solr faceted search, if that's indeed coing.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51032\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1613688042, 'spacePHID': None, 'dateCreated': 1371425280, 'dateModified': 1613688042, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49662', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Empty annotations which display are hidden as alienMetas', 'description': {'raw': 'Per Ed\\'s comment on T50605:\\n\\n> Above change fixes issue with annotations being dropped, but we still need to fix empty annotations not rendering (e.g. `<span style=\"display: block; background: red; width: 100px; height: 100px;\"></span>`), either here or in a new bug.\\n\\nThis is the new bug. :-)\\n'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371065040, 'dateModified': 1529602764, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49497', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE crash mid-edit in IE9', 'description': {'raw': '**Author:** `and.radiate`\\n\\n**Description:**\\nUsing alpha version as of 11JUN13. Did a small edit on Wikipedia English article \"Nagato-class battleship\" (deleting 3 letters from [Japanese] to form [Japan] in second sentence under section 5.1 World War II. Then scrolled down; after originally displayed area scrolled off screen, the screen went black in the TAB.  Other TABs in IE remained operative.  Back arrow did not produce any results on black screen or URL showing for the Wikipedia TAB.  Reloaded http://en.wikipedia.org in TAB with black screen; successfull load and correct operation thereafter.  Could not reproduce the error.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1465404791, 'spacePHID': None, 'dateCreated': 1370999220, 'dateModified': 1470077608, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49464', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Font weight is removed from \"article\" tab in Monobook', 'description': {'raw': 'VisualEditor is removing the font weight from the \"article\" tab when using Monobook on the English Wikipedia.\\n\\nSteps to reproduce:\\n\\n* Go to <https://en.wikipedia.org/wiki/Canada_Goose_(clothing)>\\n\\n* Click \"edit this page\".\\n\\n* The \"article\" tab loses its boldness.\\n\\n* Clicking the \"cancel\" button does not restore the boldness.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398881879, 'spacePHID': None, 'dateCreated': 1370896140, 'dateModified': 1443276404, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49407', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: It should be possible to create interwiki links and edit them subsequently', 'description': {'raw': 'E.g. [[:fr:Foo]] or [[m:Foo]].\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1396028566, 'spacePHID': None, 'dateCreated': 1370631180, 'dateModified': 1435267655, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49316', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Toolbar button text doesn't line up vertically\", 'description': {'raw': 'See http://imgur.com/wmAeHRD\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1392388033, 'spacePHID': None, 'dateCreated': 1370522640, 'dateModified': 1417572929, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49249', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Langlinks API query doesn't work outside of the main namespace because it uses wgTitle (so language links do not work in namespaces other than main)\", 'description': {'raw': 'This is bad, though in a relatively edge case of lanklinks outside the main namespace.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398108197, 'spacePHID': None, 'dateCreated': 1370489100, 'dateModified': 1443276404, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49226', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Category editor should also suggest categories which 'exist' but are without a description page\", 'description': {'raw': \"Users and categories should not be auto-completed based on page names (API action=opensearch) but instead based on their own respective query modules (list=allusers, list=allcategories) because the existence of a description page is optional and neither a subset nor superset of the database tables.\\n\\n* Pages can exist for inexistent objects.\\n* Objects often don't have an associated page.\\n\\n718db58f introduced category editing with autocompletion from opensearch (with hardcoded 'Category:' prefix). This should be switched to using list=allcategories instead.\\n\\nThat way the input field will no longer include results for inexistent categories, and no longer omit results for existing categories lacking a description page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=65517\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1401322108, 'spacePHID': None, 'dateCreated': 1370113020, 'dateModified': 1443278251, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49044', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: On save, warn the user about inconsistent header indexes', 'description': {'raw': 'It would be very nice if the Ve would warn you about inconsistencies in header levels (when you are skipping a level for instance)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1370005980, 'dateModified': 1643973227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Whitespace characters should not take a pre-annotation unless they have non-whitespace after them in the annotation', 'description': {'raw': 'In https://de.wikipedia.org/w/index.php?title=Anna_Zaja&curid=7691608&diff=118985342&oldid=118754158 a missing space was added after the name, but it should not be inside the bold part.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://de.wikipedia.org/w/index.php?title=Anna_Zaja&curid=7691608&diff=118985342&oldid=118754158'}, 'authorPHID': 'PHID-USER-tyjmn7xcw6s2b6rqagj7', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1369820460, 'dateModified': 1643973228, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48933', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'ResourceLoader: Remove obsolete closures from files', 'description': {'raw': 'Situation:\\n* ResourceLoader wraps modules in closures\\n* MediaWiki developers put a closure in each file\\n* As a result loading 1 module with 2 files will have 3 closures\\n\\n```\\nmw.loader.implement( \\'foo\\', function ( $ ) {\\n  --- foo.a.js\\n  ( function ( $, mw ) { \\n    ...\\n  }( jQuery, mediaWiki ) )\\n\\n  --- foo.b.js\\n  ( function ( $, mw ) { \\n    ...\\n  }( jQuery, mediaWiki ) )\\n} );\\n\\ninside mw.loader#execute:\\n\\n  script( jQuery );\\n```\\n\\nIt has been suggested we add \"mw\" to ResourceLoader\\'s closure and get rid of the per-file closure.\\n\\nThe downside of doing that would be that they are less safe to use \"standalone\". e.g. a jquery plugin would be using $ directly, which, outside MediaWiki ResourceLoader context is bad.\\n\\nThere is also the pending refactoring of ResourceLoader debug mode to not be completely different and near useless by executing in the global scope.\\n'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1554583100, 'spacePHID': None, 'dateCreated': 1369733580, 'dateModified': 1718295444, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48886', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Using up-arrow to scroll lets you put the cursor under the toolbar in Firefox, Internet Explorer', 'description': {'raw': \"Go to some long article (so long that it won't fit on one screen in your browser), start the visual editor, scroll down, then use up-arrow to walk all the way back up to the top of the article. It's not possible: the first lines of the article remain obscured by the visual editor's menu bar; the only way to make them visible is using the scroll bar or with PageUp.\\n\\n\\nThis is Windows 7, Firefox 16.0.2, Chrome 26.0.1410.64 m, Mediawiki 1.22wmf4 (646544a), VisualEditor 0.1.0\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-zzvqlvm6i6kml4tfnqvq', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-tuy2dac6pfhknbtqmqgh', 'dateClosed': 1680797345, 'spacePHID': None, 'dateCreated': 1369410540, 'dateModified': 1680797345, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48787', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Cursor position does not match point of insertion (when inline annotation has padding)', 'description': {'raw': 'Steps to reproduce bug:\\n\\n* Edit a page and add the following content: `Hello \"<code>world</code>\".`\\n* Place cursor before the first quote, then use the arrow keys to move right (after the quote, before W for world).\\n* Insert a character.\\n\\nExpected:\\n\\nThe place where the character appears, and the position of the blinking cursor should be the same. In actually, this is not the case.\\n\\nThe cursor is blinking **inside** the code annotation (close to the W, within the padded area of the code block).\\n\\nThe added character appeared **outside** the code annotation (close to the quote, outside the padded area of the code block).\\n\\nScreenshot of problem (from May 2013):\\n{F10475}\\n\\nVideo capture (July 2018):\\n{F23391729}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1369144560, 'dateModified': 1530906360, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48680', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Check for and warn user on unexpected badtoken event says they're now logged out\", 'description': {'raw': \"When ever the user does a load, save, diff (, other?) action with the server, we should check for whether the new edit token is an anonymous one when we're expecting the user to be logged in, so we can warn the user that they're now logged out (to prevent them asking for their IP to be over-sighted, etc.).\\n\\nThere's potentially utility in doing this in core (for the wikitext editor) as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1692047069, 'spacePHID': None, 'dateCreated': 1369077780, 'dateModified': 1692047069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48656', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Category sort key setting not done on click out, only on return', 'description': {'raw': 'In the Category inspector, start setting an over-ride for a category\\'s sort key, but instead of pressing return, click out; no sort key is set. If you change and click \"apply\", it seems like it should apply but doesn\\'t, confusingly.\\n\\nThoughts?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370985982, 'spacePHID': None, 'dateCreated': 1368745320, 'dateModified': 1417573217, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48555', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Auto-selection covers adjacent text over punctuation', 'description': {'raw': 'This seems weird to me, but it still might be intentional.\\n\\nIf you put the caret immediately after a sentence ending in a period (e.g. the last sentence of the lede from https://en.wikipedia.org/w/index.php?title=Kono_Statement_of_1993&oldid=546398254&veaction=edit), then click the Link button, it tries to link the last word, including the punctuation.\\n\\nI would expect it to let you create an new link, without assuming any existing anchor.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368978683, 'spacePHID': None, 'dateCreated': 1368583260, 'dateModified': 1417585431, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48487', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image in template gets cut off', 'description': {'raw': 'When editing http://de.wikipedia.org/wiki/Wikidata the top of the Wikimedia logo in the template at the bottom of the page is cut off. (It might also be hidden behind the grey bar or something.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1701795362, 'spacePHID': None, 'dateCreated': 1368550980, 'dateModified': 1701795362, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48461', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[Epic] Support editing parts of a page in VisualEditor-MediaWiki', 'description': {'raw': 'It should be possible to edit a part of a MediaWiki page such as a section or paragraph via VisualEditor without loading the entire article into the editor. This would be especially useful on mobile devices. This ticket is designated to serve as the parent task for all work related to such a goal.\\n\\nThe parsing-related work can be seen at [[https://phabricator.wikimedia.org/project/view/3331/|Parsoid: Section-Editing-Support board]].'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1368497160, 'dateModified': 1676333191, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48429', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"This is a minor edit\" is not auto checked in save dialog if the \"minordefault\" preference is on', 'description': {'raw': 'How to reproduce:\\n\\n1. Enable the \"Mark all edits minor by default\" option in the preferences.\\n2. Edit a page in the VisualEditor.\\n3. Press \"Review and save\", then \"Looks good to me\".\\n4. The edit summary entering bubble appears.\\n\\nObserved:\\n\\n* The \"This is a minor edit\" box is not checked.\\n\\nExpected:\\n\\n* The \"This is a minor edit\" box is checked.\\n\\nComment: The saved revision IS correctly marked as minor. It\\'s just the check box that appears incorrectly.\\n\\nGWT scenario for Cucumber:\\nGiven that I am editing an article while the minordefault preference is on\\nWhen I am saving the article\\nThen the \"This is a minor edit\" box is checked\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368638598, 'spacePHID': None, 'dateCreated': 1368250560, 'dateModified': 1417573282, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48347', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow extensions to automatically generate jsduck documentation on doc.wikimedia.org', 'description': {'raw': 'Core now has jsduck documentation on https://doc.wikimedia.org/mediawiki-core/master/js/ .  It would be useful to provide a standardized mechanism for extensions to have their jsduck documentation automatically added under doc.wikimedia.org as well.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48244'}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1394685438, 'spacePHID': None, 'dateCreated': 1368220260, 'dateModified': 1512588753, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48337', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Over-ride browser window/tab title to show you're in editing mode\", 'description': {'raw': 'Wikitext edit has page title \"Editing Foobar\", as opposed to reading-mode\\'s \"Foobar\". For people with a number of tabs open, it\\'d be great for them to get a handle on where they are by updating the window title to prepend \"Editing \" to it (and remove it on save).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368885131, 'spacePHID': None, 'dateCreated': 1368044160, 'dateModified': 1417573276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48272', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Scribunto/Lua should have a built-in method for retrieving categories used on a page', 'description': {'raw': 'It would be helpful to have a built-in method in Scribunto/Lua that allows retrieving a list of the categories used on a page.\\n\\nFor example, <https://en.wikipedia.org/wiki/Einar_Schleef> would return a list that includes:\\n\\n* German dramatists and playwrights\\n* 1944 births\\n* 2001 deaths\\n\\nAs these categories are included on this page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**: {T20596}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-52k2lmr37woy42l6kdmv', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-escte3psz5yfd2nj3jzr', 'dateClosed': 1723050710, 'spacePHID': None, 'dateCreated': 1367867880, 'dateModified': 1725575446, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48175', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support pasting of HTML from external sources', 'description': {'raw': 'many + signs\\n\\nTested: \\n\\nIn OpenOffice, create a small table with text in cells a1, a2, b1, b2, c2. \\n\\nCopy only the rows of the table. \\n\\nPaste into VE. \\n\\n* the view immediately in VE is of unusable information and some \"+\" characters apparently indicating cell boundaries. \\n\\nVersion:1.0StartHTML:0000000155EndHTML:0000000881StartFragment:0000000475EndFragment:0000000864➞➞➞➞➞➞➞➞➞➞➞➞➞a1➞➞➞b1➞➞➞➞➞➞➞➞➞➞a2➞➞➞b2➞➞➞c2➞➞➞\\n\\n* the view in the \"Review your changes\" panel is of a swath of white space with the contents of the table interspersed.\\n\\n* User tendency is to copy entire contents of rows, yielding many empty cells.  VE dutifully tracks these empty cells and displays an enormous number of \"+\" symbols in the immediate view and mostly empty space in the \"Review your changes\" view.\\n\\n* Upon save, no table is in the page when pasting from OpenOffice.\\n\\nOther anomalous results are reported when pasting from the Apple Pages application.  From another user: \\n\\n\"...number of cells didn\\'t match the number of columns. Since they don\\'t match, tried to delete the cells in order to recover the blank page, but they won\\'t delete.\"\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F11079}'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385505644, 'spacePHID': None, 'dateCreated': 1367866200, 'dateModified': 1417570401, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48170', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Sync source and editor like TeXShop', 'description': {'raw': '**Author:** `mstankus`\\n\\n**Description:**\\nIn TeXShop, you can click on a piece of content (for example,\\na word) and choose sync and you are sent directly to the \\npart of the source corresponding to that word. It would be great\\nif that could happen for wikis.\\n\\n--------------------------\\n**Version**: 1.22.0\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368010283, 'spacePHID': None, 'dateCreated': 1367686680, 'dateModified': 1368010283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48080', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Inconsistent close icon \"x\"  in Wikimedia product interfaces', 'description': {'raw': 'The close icon as defined by the [[ https://wikimedia.github.io/WikimediaUI-Style-Guide/visual-style_icons.html | WikimediaUI icon principles ]]. OOUI is already featuring the correct icon.\\n\\n| | Product | Description | Code | Screenshot | Screenshot after\\n| | -- | -- | -- | -- | --\\n| {icon check color=green} | OOUI | [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=icons&theme=wikimediaui&direction=ltr&platform=desktop#widgets-mediawiki-vector-ltr | Uses the correct icon ]] |  | {F9379666} | \\n| {icon check color=green} | Post-Edit Feedback popup | Uses the Unicode × glyph with hover behavior | Extension:PostEdit outputs CSS generated content `×` with style rules. | {F7451633} | {F26525706} \\n| {icon check color=green} | Recent CentralNotice banners | \"x in a circle\" icon, no `:hover` behavior | Extension:CentralNotice outputs an img tag showing :$wgNoticeCloseButton which defaults to [[https://upload.wikimedia.org/wikipedia/foundation/2/20/CloseWindow19x19.png|CloseWindow19x19.png]] | {F26525761} | \\n| - | ~~Visual Editor Feedback dialog~~ | As of 2017-09 not an issue any more => converted to OOUI | | {F9404470} | \\n| {icon check color=green} | ULS | ~~Thicker stroke “x” SVG, no :hover behavior~~ | Extension:UniversalLanguageSelector custom `.uls-icon-close` class | {F9362244} | {F9404483}\\n| {icon check color=green} | Extension:GuidedTour | different icon with different size |  `.guider_close` |  | \\n| {icon exclamation-triangle color=red} | Extension:MultimediaViewer | bolder, less contrast; Exempt from amending is the main close icon as it would need a full icon redesign. Will be revisited after T177432 |  | {F10595012} | \\n| {icon check color=green} | Extension:GettingStarted | different icon with different size and lighter grey |  `.mw-gettingstarted-cta-close` | {F10172642} | {F10188673}\\n| {icon check color=green} | Extension:PagePreviews | different icon, bolder and bigger | | {F10318266} | {F10319955}\\n| {icon check color=green} | Extension:Translate | ~~Similar to ULS, different icon though, as it\\'s minimally smaller in layout~~ | `.grid .tux-message-editor .close` | {F9405760} | \\n\\n\\nThe differences make WMF wikis feel unpolished.\\n\\n--------------------------\\nOriginal report: \\n**Version**: 1.22.0'}, 'authorPHID': 'PHID-USER-gbl4hfak3cfurt3c7skd', 'ownerPHID': 'PHID-USER-caadsxn4xg5gmxrpn6kz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-caadsxn4xg5gmxrpn6kz', 'dateClosed': 1517276198, 'spacePHID': None, 'dateCreated': 1367638620, 'dateModified': 1539276140, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48067', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Leave feedback\" link has confusing scope', 'description': {'raw': 'Component: UI\\n\\nThe speech bubble icon and \"Leave feedback\" link in Visual Editor look like they apply to the page being edited.  I was expecting a Talk: tool.\\n\\nIt would be more clear if the text were \"Report bug in Visual Editor\", but that\\'s annoyingly verbose.  Which is sort of the intention here, I assume ;)  Normally, this link would get buried in a dropdown menu or something, IMO.\\n\\nThe problem is exacerbated if you are sort of blind and zoom in your browser a lot, because the VE feedback link becomes very prominent once the toolbar is wrapped.\\n'}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'dateClosed': 1419610136, 'spacePHID': None, 'dateCreated': 1367214840, 'dateModified': 1621892239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47815', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Thumb\" images should display in wiki default thumb size', 'description': {'raw': 'Screenshot of page in view mode\\n\\nShow thumbnail in user preference size in edit mode.\\n\\n1. Set user preference to 300 pixel: \"Thumbnail size:\" of https://de.wikipedia.org/wiki/Spezial:Einstellungen?uselang=en#mw-prefsection-rendering\\n\\n2. Edit page with image included as standard thumb.\\n\\nThumbnail is shown in a smaller size instead of the user preference size.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/thumb\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50379\\n\\n**Attached**: {F10384}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393447280, 'spacePHID': None, 'dateCreated': 1367185680, 'dateModified': 1443276409, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47804', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Review your changes\" pop-over overlaps sidebar in monobook skin', 'description': {'raw': 'Review your changes\\n\\nSee screenshot.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n\\n**Attached**: {F10352}'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370298813, 'spacePHID': None, 'dateCreated': 1367136660, 'dateModified': 1417573221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47786', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tools to set/unset text with annotations (tracker)', 'description': {'raw': 'Given that these all exist in DM, it\\'s \"just\" a question of making a set of icons for each function and adding it to the tool bar (and then working out what to do with a toolbar with eight such icons when we wanted two.\\n\\nHave left off from the existing list in ve.dm.TextStyleAnnotation.js:\\n\\n* span - as that\\'ll need to be a distinct bug given the complexity (it\\'ll need at least an inspector, possibly a dialog)\\n* strong/em - should we just silently use these instead of b/i (or vice versa)? Either way, it feels confusing to give the user both options.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422405518, 'spacePHID': None, 'dateCreated': 1367087820, 'dateModified': 1544975585, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47780', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Report that the save dialog omits the save description entry box on hewiki/Windows/Firefox', 'description': {'raw': 'Cannot reproduce in Firefox/Mac or Chrome/Mac; asking user to reconfirm.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**Platform**: PC'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367254280, 'spacePHID': None, 'dateCreated': 1366931820, 'dateModified': 1367254280, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47679', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up the way that VE must be configured per wiki', 'description': {'raw': \"As suggested by Timo - currently we have 'wmgUseVisualEditor' and 'wmgVisualEditorParsoidPrefix' which both need to be defined for each wiki we're putting VE on, which is a bit annoying (and prone to mistakes) - when we have all 295 Wikipedias with it switched on, it will be even worse. We should probably clean this up a bit.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369920023, 'spacePHID': None, 'dateCreated': 1366731840, 'dateModified': 1417573222, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47557', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Always submit Parsoid bugs over https', 'description': {'raw': 'Please write your bugs report to http://parsoid.wmflabs.org/_bugs/ only with https to avoid a secure hole.\\n\\nPlease see this as a blocker for the coming roll out. Thanks.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-a6jwrurphpx6yl4coupk', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370629791, 'spacePHID': None, 'dateCreated': 1366641360, 'dateModified': 1417573218, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47508', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The old form <source> tag of <syntaxhighlight> extension is not supported', 'description': {'raw': \"It seems <syntaxhighlight is working just fine, but it's old deprecated 'redirect' <source is not recognized by VE, as can be seen in the link.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://en.wikipedia.org/wiki/User:TheDJ/Sandbox\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366790189, 'spacePHID': None, 'dateCreated': 1366465260, 'dateModified': 1372934095, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47454', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VE tab missing oldid when using edit source on an oldid', 'description': {'raw': 'https://en.wikipedia.org/w/index.php?title=Phil_Thompson&action=edit&oldid=535300833\\n\\nNote that in this mode, the VE tab is missing the oldid\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://en.wikipedia.org/w/index.php?title=Phil_Thompson&action=edit&oldid=535300833'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368809793, 'spacePHID': None, 'dateCreated': 1366464180, 'dateModified': 1417573280, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47453', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Edit source\" tab text should be \"Create source\" or similar when page is non-existent', 'description': {'raw': 'Currently the \"Edit source\" button\\'s label is the same whether the page is extant or not. This should change.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368885140, 'spacePHID': None, 'dateCreated': 1366394700, 'dateModified': 1417573277, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47421', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Use JSDuck syntax for inline examples in code documentation', 'description': {'raw': 'That is https://github.com/senchalabs/jsduck/wiki/Inline-examples\\n\\nFor instance:\\n\\nresources/js/ext.translate.editor.js\\n9:       * Example usage:\\n\\nresources/js/ext.translate.proofread.js\\n107:     * Example usage:\\n\\nresources/js/ext.translate.pagemode.js\\n10:      * Example usage:'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1487992074, 'spacePHID': None, 'dateCreated': 1365665640, 'dateModified': 1512588754, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47113', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Report problem\" button should give some feedback', 'description': {'raw': '- Edit an article on the English Wikipedia in the VE\\n\\n- Click \"Review and save\"\\n\\n- Click \"Something is wrong\"\\n\\n- Enter text into the field and click \"report problem\"\\n\\nNothing happens - either the error report is not sent, or the fact that it was sent is not conveyed to the user.\\n\\nReproduced three times in a current Chromium version (Chromium/25.0.1364.160) on Ubuntu.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wlku5ja6envbi4cz2etp', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366397733, 'spacePHID': None, 'dateCreated': 1365661620, 'dateModified': 1417573334, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47111', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add tracking category to pages with errors in <math>', 'description': {'raw': 'An automatic tracking category for pages with errors in <math> (when parsed by texvc) would help finding these pages and fixing the errors.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-tyjmn7xcw6s2b6rqagj7', 'ownerPHID': 'PHID-USER-4sfm3grxdo6hnogm4iqe', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-t7ue4j3fnqznjjs4z5ef', 'dateClosed': 1467323599, 'spacePHID': None, 'dateCreated': 1365503760, 'dateModified': 1660398906, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47037', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Part of MetaList should be moved into Document', 'description': {'raw': \"Per IRC discussion between me and Trevor:\\n\\n* Move list of MetaItems to dm.Document\\n* Keep MetaList (possibly rename it) with current API, wraps around list of items in Document\\n* MetaList takes a surface, and can make changes using that surface\\n* MetaItem.remove method will have to be removed, because it can't call back into the surface\\n\\n(This is for post-July)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1365460200, 'dateModified': 1643973232, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47025', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Any transaction which results in metadata being merged won't rollback cleanly\", 'description': {'raw': 'Take the document:\\n\\n<!-- meta -->content<!-- data -->\\n\\nIf you remove all of \"content\", the two comments now have to share an offset in the metadata array but this process is not recorded in the transaction. As a result, when the commit is rolled-back the comments aren\\'t re-split so the resulting doc is:\\n\\ncontent<!-- meta --><!-- data -->\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366664733, 'spacePHID': None, 'dateCreated': 1365265140, 'dateModified': 1417573332, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46954', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Remove \"sleep\" from tests', 'description': {'raw': 'We are using `sleep` in several places. Sleep is evil. The code should be refactored so the sleep is removed.\\n\\nThere are more robust ways to wait for something to happen than using sleep:\\n\\nhttp://watirwebdriver.com/waiting/\\nhttps://github.com/cheezy/page-object/wiki/Ajax-Calls\\n\\n```\\n$ grep --include *.rb  -R -F \\'sleep\\' .\\n\\n./wmde/WikidataBrowserTests/tests/browser/features/support/env.rb:  sleep env_no * 4 # sleep time to give webdriver time to setup\\n./wmde/WikidataBrowserTests/tests/browser/features/support/modules/entity_module.rb:    sleep(1.0 / 3) while execute_script(\\'return jQuery.active\\') != 0\\n./wmde/WikidataBrowserTests/tests/browser/features/support/modules/entity_module.rb:    sleep 1\\n\\n./mediawiki/selenium/features/step_definitions/environment_steps.rb:    sleep 0.3\\n\\n./mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/general_steps.rb:  sleep(Integer(seconds))\\n./mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/search_steps.rb:    sleep(5)\\n./mediawiki/vagrant/mediawiki/extensions/CirrusSearch/tests/browser/features/step_definitions/search_steps.rb:    sleep 1\\n\\n./mediawiki/vagrant/mediawiki/extensions/Gather/tests/browser/features/step_definitions/common_steps.rb:  sleep 5\\n./mediawiki/vagrant/mediawiki/extensions/Gather/tests/browser/features/step_definitions/edit_collection_steps.rb:  sleep 5\\n\\n./mediawiki/vagrant/mediawiki/extensions/MobileFrontend/tests/browser/features/step_definitions/editor_ve_steps.rb:    sleep 2 # this gets around a race condition bug in ChromeDriver where both the confirm and the toast are in the page at once, and Chrome reports either \"stale element reference: element is not attached to the page document\" or \"Element does not exist in cache\"\\n./mediawiki/vagrant/mediawiki/extensions/MobileFrontend/tests/browser/features/step_definitions/notification_steps.rb:  sleep 1\\n./mediawiki/vagrant/mediawiki/extensions/MobileFrontend/tests/browser/features/step_definitions/notification_steps.rb:  sleep seconds.to_i\\n\\n./mediawiki/vagrant/mediawiki/extensions/MultimediaViewer/tests/browser/features/step_definitions/mmv_download_steps.rb:  sleep 1\\n\\n./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu\\n./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu\\n./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu\\n./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:    sleep 1 # Sleep because of annoying JS animation happening in this menu\\n./mediawiki/vagrant/mediawiki/extensions/UploadWizard/tests/browser/features/step_definitions/upload_wizard_steps.rb:  sleep 0.5 # Sleep because of annoying JS animation happening in the date picker\\n\\n./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1\\n./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1\\n./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1\\n./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/cite_steps.rb:      sleep 1\\n./mediawiki/vagrant/mediawiki/extensions/VisualEditor/modules/ve-mw/tests/browser/features/step_definitions/media_interface_steps.rb:    sleep 1\\n```\\n\\n\\n\\n\\n\\n\\n\\n'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'dateClosed': 1495812867, 'spacePHID': None, 'dateCreated': 1365078180, 'dateModified': 1495812867, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46887', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: mw.ViewPageTarget tabLayout should be configurable as part of mw-config', 'description': {'raw': \"mw.ViewPageTarget tabLayout is currently hard-coded, which means that we can't have VE work in replace mode on one wiki and add mode on another.\\n\\n[No doubt other aspects of the integration configuration should not be hard-coded.]\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370485930, 'spacePHID': None, 'dateCreated': 1365032760, 'dateModified': 1417573220, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46871', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin to integrate with ProofreadPage', 'description': {'raw': 'Page: pages are not plain wikitext pages but are split into three textareas: header, footer and body and a proofreading level tag (note 1).\\nSo, an adaptation of the VisualEditor to these pages is needed in order to make edition of the pages work.\\n\\nThe UI need to be tweaked in order to allow the splitting of the main textarea into three and the edition of the Proofreading level at the save of page as it works currently for wikitext editing (example: https://en.wikisource.org/w/index.php?title=Page:La_Fontaine_-_The_Original_Fables_Of,_1913.djvu/20&action=edit ).\\n\\nAn other useful (but less important thing) things is to add modules to the Visual Editor to support specific tags used by Wikisource like <pages>, <section> and <poem>.\\n\\nnote 1: structure of the page as save in the database:\\n<noinclude><pagequality level=\"LEVEL\" user=\"LAST PROOFREADER\" />HEADER<div class=\"pagetext\">BODY<noinclude>FOOTER</noinclude>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\nThis card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey\\n\\nThis proposal received 41 support votes, and was ranked #23 out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Wikisource#Visual_Editor_adapted_for_Wikisource'}, 'authorPHID': 'PHID-USER-5paybpgtxjrhikdos3p5', 'ownerPHID': 'PHID-USER-h75guknmwivm6x37iute', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1466598904, 'spacePHID': None, 'dateCreated': 1364329860, 'dateModified': 1660398906, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46580', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Implement inline comment support using OKFN annotator', 'description': {'raw': \"Inline comments would be powerful addition to AFT.  It would be something like\\nhttps://en.wikipedia.org/wiki/Stet_%28software%29 integrated into MediaWiki.\\n\\nI think it would help people make useful comments that could more\\nquickly be acted on/resolved.\\n\\nI realize this would be a large enhancement, but I think it's worth considering at some point in the future.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: http://annotator.wmflabs.org/\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49603\"}, 'authorPHID': 'PHID-USER-dw53c5cb2qfhyemej57o', 'ownerPHID': 'PHID-USER-y3lag4tcfivaet2fsuln', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1511275456, 'spacePHID': None, 'dateCreated': 1363903320, 'dateModified': 1511275456, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46440', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Move wikibugs and gerrit-wm out of #mediawiki', 'description': {'raw': \"Various users find them inappropriate in #mediawiki because it is a support channel, not as much a developer discussion channel (#wikimedia-dev).\\n\\nWhether to move them there or to a dedicated channel isn't clear yet.\\n\\nSee discussions on bug 46282 and bug 46144.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398197924, 'spacePHID': None, 'dateCreated': 1363699500, 'dateModified': 1496862221, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46322', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Move wikibugs out of #mediawiki to #wikimedia-dev', 'description': {'raw': 'wikibugs has gone missing from #mediawiki.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://www.mediawiki.org/wiki/Git/IRC\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=28402'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398197844, 'spacePHID': None, 'dateCreated': 1363319760, 'dateModified': 1398197844, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46144', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Transaction with replaceMetadata then replace at the same offset doesn't rollback cleanly\", 'description': {'raw': \"This is kind of a ridiculous case, but it cost me an hour of debugging time, so documenting it here for posterity. It won't be a practical issue until we start composing transactions together.\\n\\nConsider:\\n\\nvar data = ve.dm.example.withMeta,\\n    oldDoc = new ve.dm.Document( ve.copyArray( data ) ),\\n    newDoc = new ve.dm.Document( ve.copyArray( data ) ),\\n    tx = new ve.dm.Transaction();\\ntx.pushRetain( 11 );\\ntx.pushReplaceMetadata( [], [ { metadata element here } ] );\\ntx.pushReplace( [] , [ 'a', 'b', 'c' ] );\\nve.dm.TransactionProcessor.commit( newDoc, tx );\\nve.dm.TransactionProcessor.rollback( newDoc, tx );\\n\\nAfter running this, you'd expect oldDoc.metadata and newDoc.metadata to be equal, but they're not:\\n\\n> oldDoc.metadata[11].length;\\n4\\n> newDoc.metadata[11].length;\\n5\\n\\nWhen the transaction is rolled back, the metadata element that was added was never removed. I think this is because the content insertion pushes the metadata back, and then when the rollback tries to remove the metadata again, it can't find it. When the metadata replacement and content replacement are swapped, it works fine, so that's my workaround for now.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1682006049, 'spacePHID': None, 'dateCreated': 1363300500, 'dateModified': 1682006049, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46138', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Redesign naming of canHaveChildren, ContentBranchNode, etc.', 'description': {'raw': \"Trevor complained the naming of these things doesn't make sense, so let's sit down and come up with a strategy for renaming this stuff at some point.\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1363284960, 'dateModified': 1422518093, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46133', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow testing dom<->data conversion with and without MW-specific nodes registered', 'description': {'raw': \"TODO comment in ve.dm.Converter.test.js:\\n\\n// TODO: this is a hack to make normal heading/preformatted\\n// nodes the most recently registered, instead of the MW versions\\n\\nIt's not entirely clear to me how we should fix this. Maybe once we hard-split the VE and MWVE code bases and each of these has its own test suite, then we won't have to worry about this as much.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372874201, 'spacePHID': None, 'dateCreated': 1363131420, 'dateModified': 1417573147, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46048', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When Parsoid is down, error message is parsoidserver-http-200', 'description': {'raw': 'When the Parsoid server is down completely (e.g. because you forgot to start it), the error message VE gives you is \"parsoidserver-http-200\". It\\'s kind of ridiculous that it\\'s presenting an error with 200, but it\\'s also a lie: 200 wasn\\'t the response code we got from Parsoid, we got no response whatsoever.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1363626420, 'spacePHID': None, 'dateCreated': 1362783660, 'dateModified': 1417573340, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45916', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add static name property to CE nodes', 'description': {'raw': \"DM nodes have a static name property which is used by the nodeRegistry. CE nodes currently have their names written out at least twice. It also creates unnecessary complexity when inheriting CE nodes as the parent constructor cannot be used (as it contains the parent's name hard coded).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1362705677, 'spacePHID': None, 'dateCreated': 1362405720, 'dateModified': 1417573342, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45701', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Kill global functions in test suites', 'description': {'raw': 'Functions like runConverterTests() and what not are often global functions in the test file. These should be un-global-ified somehow.\\n'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1361566080, 'dateModified': 1531524375, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45291', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: SurfaceFragment methods don't document their chainability properly\", 'description': {'raw': \"The hallmark of chainability in VE, dm.SurfaceFragment, doesn't actually use @chainable to document the chainability of most of its methods.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361748260, 'spacePHID': None, 'dateCreated': 1361494680, 'dateModified': 1417573343, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45264', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: newFromWrap() should perform validation', 'description': {'raw': \"ve.dm.Transaction.newFromWrap() currently doesn't check that the transaction it generates will be valid. That is, it will ensure that things are unwrapped correctly, but it doesn't check that the result doesn't end up violating parent/child restrictions.\\n\\nIt's not entirely clear to me whether we should try to rectify that or throw an exception, but either of those is better than generating a transaction that, when applied, will make the document nonconformant.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1361325660, 'dateModified': 1643973235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45183', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Warn user when saving page with <ref>s but not <references />', 'description': {'raw': 'When a user saves a page, VE should check for references (<ref>s) created without the de-referencing block (<references /> or {{reflist}} or...) and intervene:\\n\\n* prompt them to fix before saving (out of the notices area?);\\n* refuse to save before fixed (grey out the save button?); or\\n* auto-fix for them (insert a \"== References ==\\\\n<references />\" section just above the categories), though this (a) sucks, (b) enforces a particular wiki\\'s style on other wikis in code, and (c) would be difficult to internationalise\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54906\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51260'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1508927932, 'spacePHID': None, 'dateCreated': 1361220060, 'dateModified': 1508927932, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45132', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'The default (English) link trail ($linkTrail) only matches [a-z]', 'description': {'raw': 'Using a more extensive default $linkTrail regex was tried in 416c84480 (although I don\\'t know why it used `\\\\p{L&}` rather than `[[:alpha:]]` or `\\\\p{L}`), but this was reverted in 5b97a5bb due to {T17035}. We could probably try that again (without the apostrophe, see T16655) now that we require a more modern version of PHP with a more modern version of PCRE. It may not work correctly for alphabets other than Latin.\\n\\n----\\n\\nPlease have a look at \\nhttps://www.wikidata.org/wiki/MediaWiki:Gadget-rightsfilter/hu\\nwhere the link has the form [[:hu:Reguláris kifejezés|regex]]alapú\\nand \"ú\" is not linked.\\nThis is a multilingual project, so all letters should be included into links, or at least all Hungarian letters. :-)'}, 'authorPHID': 'PHID-USER-4c6srusxkc3xljf73qq6', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1361209560, 'dateModified': 1602867790, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45126', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ce.ContentBranchNode tests fails in Firefox due to object key order', 'description': {'raw': 'This test works in Chrome, but in Firefox it fails with:\\n\\nExpected: \\t\\n\\n\"a<b>b<span typeof=\\\\\"mw:Entity\\\\\" class=\\\\\"ve-ce-leafNode ve-ce-MWEntityNode\\\\\" contenteditable=\\\\\"false\\\\\">c</span>d<div class=\\\\\"ve-ce-leafNode ve-ce-alienNode ve-ce-alienInlineNode\\\\\" contenteditable=\\\\\"false\\\\\"><tt>e</tt></div></b>\"\\n\\nResult: \\t\\n\\n\"a<b>b<span class=\\\\\"ve-ce-leafNode ve-ce-MWEntityNode\\\\\" typeof=\\\\\"mw:Entity\\\\\" contenteditable=\\\\\"false\\\\\">c</span>d<div class=\\\\\"ve-ce-leafNode ve-ce-alienNode ve-ce-alienInlineNode\\\\\" contenteditable=\\\\\"false\\\\\"><tt>e</tt></div></b>\"\\n\\n(the difference is in the order of the class and typeof attributes)\\n\\nWe should probably implement DOM comparison instead of string comparison in the ce.ContentBranchNode test suite.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1443111590, 'spacePHID': None, 'dateCreated': 1360374780, 'dateModified': 1445465520, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44808', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clean up duplication of Mac/PC command/ctrl in all command registrars', 'description': {'raw': 'Should perhaps have some kind of magic alias \"trigger\" that maps to meta/ctrl respectively.\\n\\nThe flexibility of being able to bind something to ctrl on mac, and to meta on pc is useful but in the most common case we don\\'t to do that.\\n\\nAnd we\\'re currently duplicating this internal logic at the cost of decentralisation. So plugin authors providing Tools need to duplicate this logic also, meaning more maintenance when we change this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1359158880, 'dateModified': 1643973236, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44364', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Only tag edits via GettingStarted if the user is actually new', 'description': {'raw': 'The GettingStarted extension is tagging edits of new users (bug 43191). These tags should be temporary.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1369959989, 'spacePHID': None, 'dateCreated': 1359154380, 'dateModified': 1369959989, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz44361', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Delete all redundant \"MediaWiki\" pages for system messages', 'description': {'raw': 'I encountered many times now on wikis (usually the small wikis) that there are 100s of local MediaWiki pages with translations from before translatewiki.net covered that language.\\n\\nAnd even after twn covered it, there may have been local improvements that over time make it into twn, but then the local page stales.\\n\\nTo avoid translations from going out of sync (the longer we wait with this, the harder it is to clean them up as the difference between an override and an outdated translation becomes harder to tell), and also to avoid migration issues when messages change.\\n\\nLets run this asap.\\n\\n--------------------------\\n//EDIT//: deleteEqualMessages.php has been completed on the following wikis:\\n{P1988}'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1488864149, 'spacePHID': None, 'dateCreated': 1358039640, 'dateModified': 1537557999, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43917', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Batch Parsoid's API requests\", 'description': {'raw': \"We should amortize per-request overheads by batching API requests.\\n\\nAFAIK there is no generic batching support in the API currently, and adding it would probably be a bit too time-consuming for now. Instead we can add a unique string as a separator, for example something like \\n\\n<nowiki>d41d8cd98f00b204e9800998ecf8427e</nowiki>\\n\\nThis would work for for action=expandtemplates and action=parse which are the main workarounds we currently use. In the longer term we should switch to explicit methods that don't involve parsing wikitext, which is probably also a good moment to add real batching support.\\n\\nDecisions about batch sizes could be based on wikitext source size initially (based on the assumption that templates with a bazillion parameters also take longer to expand). A fixed number of templates per batch would be another simple alternative. Really fancy batching could use stats of previous processing times (returned by the PHP preprocessor per transclusion and stored in HTML).\\n\\nIdeally we would also enforce separation between batched requests to avoid non-deterministic behavior for stateful extensions.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'ownerPHID': 'PHID-USER-k6tmz5ylx4rzfl3bitse', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-gxcjmjpejlhfnrquksm2', 'dateClosed': 1447828111, 'spacePHID': None, 'dateCreated': 1357943520, 'dateModified': 1447828111, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43888', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: For article namespace, disable Heading-1s (<h1>), others?', 'description': {'raw': 'From user suggestion:\\n\\n| Heading 1 is very rare on enwiki, and indeed on most other installations.\\n| Where it is used (mostly on project discussion pages), it does not usually\\n| need to be edited. VisualEditor should not offer it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372274701, 'spacePHID': None, 'dateCreated': 1356129180, 'dateModified': 1417573156, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43334', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Firefox has issues using VE when cookies are disabled', 'description': {'raw': \"**Author:** `turb`\\n\\n**Description:**\\nWhen cookies are disabled, VisualEditor loads indef. It would better to either 1) be able to use it without cookies (I suppose that's not possible) or 2) display an adequate error message.\\n\\nTested on Firefox 17.0.1 with Cookie Monster 1.1.0.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380306435, 'spacePHID': None, 'dateCreated': 1355742780, 'dateModified': 1417573135, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43193', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Undo/Redo doesn't work in Chrome/Chromium/Firefox for WikiEditor 0.3.1 in MW 1.19.2\", 'description': {'raw': \"**Author:** `kartiksinghal`\\n\\n**Description:**\\nI am using WikiEditor 0.3.1 in my mediawiki (1.19.2) installation and found that for some weird reason, undo/redo (Ctrl+Z and Ctrl+Shift+Z) doesn't work in the editor with Chrome, Chromium and Firefox browsers; while it works for Rekonq and default KDE webbrowser.\\n\\nI found T33780 - a slightly different but probably relevant bug report.\\n\\nAlso, undo works just fine in default VisualEditor in Chrome.\\n\\nInteresting point to notice is that Undo/Redo work fine even on WikiEditor used on Wikipedia, but not in my mediawiki instance, looks like some good changes not pushed to upstream yet.\\n\\nI also tried test2.wikipedia.org, it works fine there as well.\\n\\n--------------------------\\n**Version**: REL1_19-branch\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=31780\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'dateClosed': 1426929084, 'spacePHID': None, 'dateCreated': 1355717820, 'dateModified': 1459676834, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43187', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Parsoid diff failure errors are not very descriptive', 'description': {'raw': 'Parsoid diff failure errors are not very descriptive - \"error loading data from server: unsuccessful request: diff failed.\" but not why (in this case, it was because the target oldid had been deleted subsequent to the user pressing save, but a more graceful message would be good.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=44354\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=39057\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=63149'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ogbcrxm45oo3n3xe5q25', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1409684401, 'spacePHID': None, 'dateCreated': 1355530860, 'dateModified': 1443278251, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43147', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fly-out wikitext editor for unsupported extensions\\' source blocks (\"alienated content\")', 'description': {'raw': 'For content which is alienated, provide a way for users to get a wikitext editing window for just the wikitext for that item. This allows users to modify content that does not have an inspector yet, and for \"power users\", make tweaks in an environment that is familiar to them, without overwhelming other users. Ideally, this would be syntax-highlighted and pretty and helpful, but anything at all would be a start. :-)\\n\\nThis will require some serious magic in Parsoid to identify the causal wikitext and allow partial document retrieval, and so this is very much in the \"enhancement\" pile for now; putting in UI as it\\'s an inspector, but it will have impacts all the way down through DM.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1414135494, 'spacePHID': None, 'dateCreated': 1355508900, 'dateModified': 1417571685, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43133', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to add/edit Poem blocks', 'description': {'raw': '<poem>....</poem> is unparsed but shown as plain wikitext:\\nhttps://en.wikipedia.org/wiki/User:Raymond/poem\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/wiki/User:Raymond/poem'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1355479800, 'dateModified': 1643973239, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43120', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to add/edit Timelines', 'description': {'raw': '<timeline>....</timeline> is unparsed but shown as plain wikitext:\\nhttps://en.wikipedia.org/wiki/User:Raymond/timeline\\n\\n**See Also**:\\n{T29157}'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1479204677, 'spacePHID': None, 'dateCreated': 1355477160, 'dateModified': 1682953313, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43115', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switch over edit-success notice to use the deployed one', 'description': {'raw': 'On successful save, VE informs the user with a notification; however, this is not the same as the one deployed to the English Wikipedia (and elsewhere?). We should just inherit that, if possible.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1368638967, 'spacePHID': None, 'dateCreated': 1355431920, 'dateModified': 1417573282, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43091', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Capture PHP warnings with stacktraces in MediaWiki and save to logstash', 'description': {'raw': \"//This task is about PHP errors, for fatals, see T89169.//\\n\\n-------\\n\\nAlthough we get PHP warnings in the apache syslogs, we don't really get much information about it:\\n\\nDec 13 18:30:43 10.0.11.48 apache2[9987]: PHP Warning:  preg_match() expects parameter 2 to be string, array given in /usr/local/apache/common-local/php-1.21wmf6/extensions/FundraiserLandingPage/FundraiserLandingPage.php on line 96\\nDec 13 18:30:43 10.0.2.198 apache2[24462]: PHP Warning:  preg_match() expects parameter 2 to be string, array given in /usr/local/apache/common-local/php-1.21wmf6/extensions/FundraiserLandingPage/FundraiserLandingPage.php on line 96\\n\\nWe could do with recording more information (to a different log file on fluorine), like we do for both the fatal log and the exception logs\\n\\n-------\\n\\nPatches: <https://gerrit.wikimedia.org/r/#/q/message:T45086>\\n\\nChecklist:\\n\\n* [x] Improve de-duplication and message counting by ensuring `normalized_message` does not include the exception_id. – Pending review: https://gerrit.wikimedia.org/r/374895\\n* [x] Introduce $wgPropagateErrors to avoid duplicate logging under `type:hhvm` – Pending review: https://gerrit.wikimedia.org/r/338911\\n* [x] Enable $wgPropagateErrors in Beta Cluster. https://gerrit.wikimedia.org/r/c/409171/\\n* [x] Enable $wgPropagateErrors in production Cluster.\\n* [x] Remove unused `exception-json` conversion filter from `filter-mediawiki.conf` in `operations/puppet.git`\\n\"}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1551732531, 'spacePHID': None, 'dateCreated': 1355424060, 'dateModified': 1629231704, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43086', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Parsoid: Square brackets sometimes (but not always) get escaped with <nowiki>s when PHP parser wouldn't\", 'description': {'raw': \"Visual Editor sometimes creates nowiki markup around simple square text brackets. Interestingly, it does that only in some cases, and not in others. For the same structure, it can also handle the text with nowiki, but does it in others. Text case:\\n\\n The example below shows that in some cases this is done, in others not:\\n\\n# Remains unchanged: Test text for the VisualEditor: [[Link target|These are ['''just''' normal brackets]]].\\n# Superflous nowiki-tags added on editing: Test text for the VisualEditor: [[Link target|These are '''just''' [normal brackets]]].\\n\\n\\nEdit with Visual Editor to see the effect.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**See Also**:\\n{T54268}\"}, 'authorPHID': 'PHID-USER-grpjkpfolt5gz4ljlbfg', 'ownerPHID': 'PHID-USER-nvavrb7ko66hv3xap6sb', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1362174611, 'spacePHID': None, 'dateCreated': 1355402040, 'dateModified': 1539403305, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43067', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Suppress \"Web link\" section in link inspector suggestion list if a wiki page link already exists', 'description': {'raw': 'Present situation: the Visual Editor, when clicking on an existing Wiki-Link, provides the chain-link icon which in turn opens a dialogue which contains a pick list. In the pick list two sections exist: \"Existing page\" (value e.g. \"Pretoria\") and \"Web link\" (e.g. \"http://Pretoria\"). \\n\\nThe present dialogue is good enough for creating new links. However, for existing links it is somewhat confusing to offer a nonsense http:// link as an equally valid alternative to an existing or previously confirmed wiki page.\\n\\nI suggest to keep the present behaviour for new links, but for existing wiki-page-links suppress the \"web link\" part of the pick list. It will still be possible to enter URLs directly in the dialogue box, the enhancement is only about suppressing it in the pick list.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=43841'}, 'authorPHID': 'PHID-USER-grpjkpfolt5gz4ljlbfg', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367544076, 'spacePHID': None, 'dateCreated': 1355397960, 'dateModified': 1417573293, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43063', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'mediawiki.action.view.dblClickEdit.dblClickEdit should trigger ca-edit click instead opening URL directly', 'description': {'raw': \"To account for editors that don't open a new page, simulate a click instead of using window.location directly.\\n\\nThat way editors such as VisualEditor will get the edit event and initiate the editor.\\n\\nVisualEditor works without this as it updates the ca-edit url with ?veaction=edit, so it'll work. But still, going through a useless reload is... useless.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358469835, 'spacePHID': None, 'dateCreated': 1355360100, 'dateModified': 1358469835, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43052', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Strange duplication of content after multiple save attempts', 'description': {'raw': \"Reported at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Error_saving_data_to_server:_error: the parsoid appears to time out(?) and reports that there's an error, while actually saving the page. Meanwhile, a second attempt at saving has the same problem, /also/ saves...but adds random duplication of sentence fragments. See \\nhttps://en.wikipedia.org/w/index.php?title=Cologne&diff=next&oldid=527666838\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366665489, 'spacePHID': None, 'dateCreated': 1355347080, 'dateModified': 1366665489, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43043', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Handling of double click when preference \"Edit pages on double click\" is active', 'description': {'raw': 'When using the VisualEditor and having the Preference \"Edit pages on double click (requires JavaScript)\" on, the Editor is stopped as soon as one tries to select a word  (= double click)or paragraph (= triple click). The javascript for \"Edit pages on double click (requires JavaScript)\" needs to be modified to check whether in VisualEditor mode or not (all works ok when in normal editing mode.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-grpjkpfolt5gz4ljlbfg', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1361748640, 'spacePHID': None, 'dateCreated': 1355333220, 'dateModified': 1417573345, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43023', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Uncaught TypeError: this.registry[name].static is undefined\"', 'description': {'raw': \"When trying to use VisualEditor on the English Wikipedia at <https://en.wikipedia.org/wiki/James_Mackay,_Baron_Mackay_of_Clashfern>, I get the following error in my browser's console:\\n\\n---\\n[11:35:31.120] TypeError: this.registry[name].static is undefined @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.visualEditor.core%2Cicons-raster%7Cext.visualEditor.viewPageTarget.icons-raster%7Cjquery.multiSuggest%7Crangy&skin=monobook&version=20121212T032708Z&*:207\\n---\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364318088, 'spacePHID': None, 'dateCreated': 1355330220, 'dateModified': 1364318088, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43017', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Fix \"Uncaught TypeError: Cannot read property \\'typePattern\\' of undefined\"', 'description': {'raw': \"When I try to use VisualEditor with <https://en.wikipedia.org/wiki/User:Trevor_Parscal>, I get the following error in my browser console: Uncaught TypeError: Cannot read property 'typePattern' of undefined.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1364318060, 'spacePHID': None, 'dateCreated': 1355327040, 'dateModified': 1417573338, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43014', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable Visual editor on test client', 'description': {'raw': 'Enable VisualEditor on test client and check if the two extensions do not interfere with each other.\\n\\nThey should not interfere with each other except for the additional parser function(s) introduced by Wikibase client.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-vlni4mhyozor7ghqnfkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378480597, 'spacePHID': None, 'dateCreated': 1355287440, 'dateModified': 1378480597, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42981', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable Visual editor on test repo', 'description': {'raw': 'Enable VisualEditor on test repo and check if the two extensions do not interfere with each other.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-vlni4mhyozor7ghqnfkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378480608, 'spacePHID': None, 'dateCreated': 1355285580, 'dateModified': 1378480608, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42980', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Avoid triggering \"XMLHttpRequest cannot load. Origin is not allowed by Access-Control-Allow-Origin.\"', 'description': {'raw': \"Feedback is one-way, we don't need to read the reponse (and we can't, due to origin policy). So we should convert this into a regular POST without XHR so that it doesn't error.\\n\\nApparently though the current method does work for one-way (the request isn't blocked in Chrome).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370629685, 'spacePHID': None, 'dateCreated': 1355277780, 'dateModified': 1417573219, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42974', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Integration in production should not ignoreHidden on user preference', 'description': {'raw': 'In VisualEditor.hooks.php the function to evaluate whether or not to show the VisualEditor has ignoreHidden set true on the user preference check; this should be false in production.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366929861, 'spacePHID': None, 'dateCreated': 1355190000, 'dateModified': 1417573331, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42936', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Redirects mask incorrect spellings (misspellings) in articles', 'description': {'raw': 'On a site such as the English Wikipedia, editors often create redirects for misspelled versions of page titles so that readers can have an easier time accessing the content they\\'re after. For example, if a reader enters \"Barrack Obama\" or \"Dave Chapelle\" or \"Steve Carrell\" into the search bar, they\\'ll be redirected automatically to \"Barack Obama\" or \"Dave Chappelle\" or \"Steve Carell\" (respectively) automatically. This is a good thing.\\n\\nHowever, these redirects can be problematic when editors insert this text into a page in the form of a link and don\\'t get any feedback that the text they\\'ve entered is a misspelling (that it\\'s likely wrong and not the text they intended to insert). In fact, the user gets the opposite feedback: they get feedback (a blue link) indicating that they\\'ve inserted an appropriate, working link.\\n\\nThese misspelled redirects can be tagged with templates such as \"{{R from misspelling}}\" which generally automatically categorize them.\\n\\nI\\'m not sure what the appropriate behavior here is. I believe that continuing to allow users to insert links to misspelled words or phrases unknowingly is a bug and should be addressed somehow.\\n\\nThere are a few options here, but I\\'m curious to read what others think about this. The goal here is to reduce the number of misspelled links that are added to a page by giving the user warning or notice that they\\'ve tried to insert a misspelled link (e.g., [[Hilary Clinton]] or [[Stephen Spielberg]]).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Linked_misspellings\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=13595'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1355001180, 'dateModified': 1643973240, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42880', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links should not be allowed to be created spanning only whitespace', 'description': {'raw': 'Select some whitespace and open the link inspector and create the link.\\nThe SurfaceFragment.trimRange method is not trimming the space if the range only contains space.\\n\\nThe correct behavior should be to trim the space then insert the location text into the document.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354921736, 'spacePHID': None, 'dateCreated': 1354917180, 'dateModified': 1417573354, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42839', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Page creation should have a customized save button', 'description': {'raw': 'Similar to bug 41865\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354758526, 'spacePHID': None, 'dateCreated': 1354749120, 'dateModified': 1417573357, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42750', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'en.wikipedia.org load takes 12+ seconds in specific Source IP range, as one specific call to bits.wikimedia.org/.../load.php times out', 'description': {'raw': \"**Author:** `bugzilla.wikimedia.org.76374`\\n\\n**Description:**\\ncurl -I 'http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.centralNotice.bannerController%7Cext.wikimediaShopLink.core%7Cjquery.client%2Ccookie%2CmwExtension%7Cmediawiki.cldr%2CjqueryMsg%2Clanguage%2Cnotify%2Cutil%7Cmediawiki.language.data%2Cinit%7Cmediawiki.legacy.ajax%2Cwikibits%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup&skin=vector&version=20121203T183954Z&*'\\ncurl: (52) Empty reply from server\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1490658160, 'spacePHID': None, 'dateCreated': 1354560840, 'dateModified': 1490687031, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42653', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Only replace url on veaction=edit if there is no other query', 'description': {'raw': 'Go to a VE wiki page directly in edit mode:\\n\\nhttp://mediawiki.org/wiki/VisualEditor:Test?uselang=he&veaction=edit\\n\\nThe integration changes the URL to:\\n\\nhttps://www.mediawiki.org/wiki/VisualEditor:Test\\n\\n... instead of:\\n\\nhttps://www.mediawiki.org/wiki/VisualEditor:Test?uselang=he\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354565570, 'spacePHID': None, 'dateCreated': 1354218360, 'dateModified': 1434236528, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42553', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Integration fails if an article has an '@' character in its title\", 'description': {'raw': \"VE/MW integration fails (does not trigger but instead throws two errors, below) if an article has an '@' character in its title, though these are valid\\n\\nUncaught Error: Bad constructor arguments    mediawiki.Uri.js:165\\nUri                     mediawiki.Uri.js:165\\nmw.UriRelative          mediawiki.Uri.js:318\\n(anonymous function)    mediawiki.Uri.js:325\\n(anonymous function)    mediawiki.Uri.js:328\\n\\nUncaught TypeError: undefined is not a function    ve.init.mw.ViewPageTarget.js:18\\nVeInitMwViewPageTarget    ve.init.mw.ViewPageTarget.js:18\\n(anonymous function)      ve.init.mw.ViewPageTarget.js:1121\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**URL**: https://www.mediawiki.org/wiki/VisualEditor:Test@4\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1358878792, 'spacePHID': None, 'dateCreated': 1353449520, 'dateModified': 1417573351, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42306', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Putting cursor immediately before link should display inspector icon', 'description': {'raw': 'Currently, putting the cursor inside a link displays the inspector icon (except for bug 42276). Putting the cursor immediately after a link (i.e. between the last linked character and the first non-linked character) also displays the icon, but putting it immediately before the icon (between the last non-linked character and the first linked character) does not. I think it should.\\n\\nOf course, the interesting question here is what should happen when you have two directly adjacent links and you put the cursor between them.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353539731, 'spacePHID': None, 'dateCreated': 1353379740, 'dateModified': 1417573399, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42281', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Pre-annotations code annotates characters with the empty set', 'description': {'raw': \"1. Open any document\\n2. Blank it\\n3. Type some text\\n4. Dump the model into the console (ve.instances[0].documentModel.data)\\n\\nExpected output: [ 'F', 'o', 'o', 'b', 'a', 'r' ]\\nActual output: [ 'F', ['o', ve.AnnotationSet([])], ['b', ve.AnnotationSet([])] ...\\n\\nThe pre-annotations code is applying the empty set as a pre-annotation to every character except the first. This shouldn't happen, it should just not annotate if it's got nothing to annotate with.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353546616, 'spacePHID': None, 'dateCreated': 1353378840, 'dateModified': 1417573397, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42279', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make MW\\'s core \"edit source\" functionality load in-page', 'description': {'raw': 'Currently to view the underlying wikitext of a page that\\'s in a namespace where VisualEditor is active, one clicks an \"edit source\" tab. However, when editing, if you want to see the underlying wikitext but not lose your changes or really just not have to reload the page, that isn\\'t possible. It\\'d be awfully nice if you could toggle between wikitext and the VisualEditor interface without needing to reload the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57462'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1352958180, 'dateModified': 1643973241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42141', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Toolbar \"Save page\" button is confusing as it merely opens the dialog to save the page', 'description': {'raw': 'Currently when using the VisualEditor extension, there\\'s a big green button that reads \"Save page\" in the top-right corner of the browsing window.\\n\\nWhen a user clicks this button labeled \"Save page\", the page is not saved. Instead, a dialog box appears in which the user is prompted to enter an edit summary. If the user then clicks the \"Save page\" button again (a second time), the page will be saved (maybe).\\n\\nI believe this is behavior is a little wrong. Historically the behavior of the \"Save page\" button has been to actually attempt to save the page to the database. This new workflow changes that behavior.\\n\\nRoan suggested perhaps changing \"Save page\" to read \"Save page...\", which would give the user a clue that it\\'s going to be a process, not an immediate action.\\n\\nThere\\'s also no warning within the \"Save page\" dialog box that says that the page has not yet been saved to the database. There\\'s no \"this is only a preview!\" text. Perhaps that\\'s a separate bug, though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1524049612, 'spacePHID': None, 'dateCreated': 1352957520, 'dateModified': 1525162037, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42138', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Watch this\" checkbox in Save dialog should use same logic as core EditPage', 'description': {'raw': 'When using VisualEditor currently when creating a page, the \"Save page\" dialog box has two checkboxes below the edit summary input: \"This is a minor edit\" and \"Watch this page\".\\n\\nThe \"Watch this page\" checkbox is not auto-checked, even though it is (for my account) via the non-VisualEditor editor. There\\'s a user preference (\"Add pages I create and files I upload to my watchlist\") that controls whether this checkbox is checked by default when creating a page. VisualEditor currently ignores the value of this user preference. It should respect it.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354835188, 'spacePHID': None, 'dateCreated': 1352957160, 'dateModified': 1417573356, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42136', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Merging behaviour of lists should be looked at', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=66452'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1352935080, 'dateModified': 1643973241, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42115', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When editing a non-current revision of a page, alter the \"Save page\" button behaviour', 'description': {'raw': 'Current behaviour on oldid pages is the same as for current ones - that is, the \"Save page\" button is greyed out and won\\'t activate until the content changes.\\n\\nHowever, for oldid pages the content is already \"changed\" compared to the current revision, so it should be active right from the start. Also, ideally it should say \"Restore page\" at first, changing to \"Save page\" when/if the page\\'s contents have been altered.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-mpfqwllylfkzpcgkdkvc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354737639, 'spacePHID': None, 'dateCreated': 1352324940, 'dateModified': 1417573358, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41865', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Context menu appears in the wrong place in IE10 (and IE9) when zoomed in', 'description': {'raw': \"**Author:** `orbit`\\n\\n**Description:**\\nInternet Explorer 10, the most cutting-edge browser on the planet, is displaying the context menu far away from the end of the selection. It looks to be about 300 pixels to the right and 150 pixels down - similar to the size of the inspector. Maybe it's related?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1460912828, 'spacePHID': None, 'dateCreated': 1350690900, 'dateModified': 1461095287, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41233', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Linktrail&prefix is wrongly applied to CJK characters', 'description': {'raw': 'Wikitext:\\n\\n[[汉]]字\\n\\nParsoid:\\n\\n<p data-parsoid=\"{&quot;dsr&quot;:[0,6]}\"><a rel=\"mw:WikiLink\" href=\"./汉\" data-parsoid=\"{&quot;tsr&quot;:[0,6],&quot;bsp&quot;:[0,6],&quot;a&quot;:{&quot;href&quot;:&quot;./汉&quot;},&quot;sa&quot;:{&quot;href&quot;:&quot;汉&quot;},&quot;stx&quot;:&quot;simple&quot;,&quot;tail&quot;:&quot;字&quot;,&quot;dsr&quot;:[0,6]}\">汉字</a></p>\\n\\nPHP Parser <https://www.mediawiki.org/w/index.php?title=Project:Sandbox&oldid=594926>:\\n\\n<p><a href=\"/w/index.php?title=%E6%B1%89&amp;action=edit&amp;redlink=1\" class=\"new\" title=\"汉 (page does not exist)\">汉</a>字</p>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-m2ezqyeb4uz67zq6bats', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1380741319, 'spacePHID': None, 'dateCreated': 1350544680, 'dateModified': 1380741319, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41151', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Iceweasel seems to (wrongly?) trigger browser blacklist', 'description': {'raw': 'See gerrit 21142\\n\\nThe latest Firefox (Iceweasel) version shipped with the latest \"working\"[1] Debian is 10.x[2], so unless they install a newer Firefox manually, Debian desktop users can\\'t use VisualEditor in Firefox.\\n\\n[1] http://en.wikipedia.org/wiki/Debian#Additional_repositories\\n[2] http://packages.debian.org/search?keywords=iceweasel\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1366999513, 'spacePHID': None, 'dateCreated': 1350539940, 'dateModified': 1513030089, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41147', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Implement repeated/fixed/floating/sticky table headers', 'description': {'raw': \"With longer tables it can be very difficult to identify the columns. It might be nice if table headers stayed in view when scrolling trough a long table.\\n\\nThis could be done with JS, but would need to be compatible with tablesorter of course.\\n\\nThinking about 'fixed' position headers once the header moves out of the screen viewport. Can possibly do similar stuff with footers.\\n\\n--------------------------\\n**Version**: 1.21.x\\n**Severity**: enhancement\\n**See Also**: {T12013}\"}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1349347020, 'dateModified': 1725954431, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40763', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'jquery.tablesorter: Add support for a \"fixed\" column of row numbers.', 'description': {'raw': '**Author:** `winne2i`\\n\\n**Description:**\\nColumn of fixed row numbers. \\n\\nIn tables where we enumerate something we usually add a first column with row numbers. Of course we set it as unsortable (class=unsortable) – BUT it doesn\\'t prevent the column from being sorted while we sort another column. Then the row numbers get all messed up.\\n\\nThere should be an additional parameter (class or something) for setting which column should not be sorted in any circumstance.\\n(I cannot think of anything more in that column than row numbers…)\\n\\nTemplate:Static_row_numbers creates tables with fixed row numbers:\\nhttps://en.wikipedia.org/wiki/Template:Static_row_numbers \\nhttps://en.wikipedia.org/wiki/Special:WhatLinksHere/Template:Static_row_numbers \\n\\nA deprecated method is used for tables in this category: \\n*https://en.wikipedia.org/wiki/Category:Articles_with_tables_with_fixed_row_numbers\\nSome of the tables in that category have row number columns that do not sort under any circumstance. Some only sort if that particular row number column header is clicked. For example; if ascending or descending ranking is desired. But none of the row number columns sort when other column heads are clicked.\\n\\nWikitext of fixed row numbers in a table on Polish Wikipedia below, and in use here: \\nhttps://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne_dyskusja/Archiwum/2012-grudzie%C5%84#Sortowanie_tabeli \\nThe row number column does not sort under any circumstance.\\n\\n```\\n{| class=\"wikitable sortable\" style=\"text-align:center;\" align=\"left\"\\n!class=\"unsortable\"|№\\n!color\\n!name\\n!city\\n|-\\n|1||white||John||New York\\n|-\\n|2||green||Alice||Warsaw\\n|-\\n|3||black||Mark||Rennes\\n|}\\n```\\n\\nTh attached chart images show what happens if the row number column is not fixed. For example; if the above table wikitext is used on English Wikipedia.\\n**Attached**: {F9709}\\n\\nThe best patch would add a column of fixed row numbers to any chart. Without having to manually enter the row numbers. Or reenter the numbers after every addition of more rows in the middle of the table. '}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1348933560, 'dateModified': 1708301369, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40618', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Cancel\" link when editing a page should either be a button or not be there at all.', 'description': {'raw': \"For consistency, when editing, the 'Cancel' link should really be a button along with the other buttons on the line, since it is an action like the rest of them even if it isn't directly tied to the form itself.\\n\\nThe help link should also probably be removed entirely from at least the default installation, as no help pages actually come with said installation and thus the link doesn't go anywhere. Expecting wikis at this point to write their own editing help pages is also pretty silly, as there tend to already be much more thorough such pages on other wikis such as enwp, meta, and similar, and new projects can merely refer to those instead if needed. For any projects using the WikiEditor extension, though, having a link at all is redundant anyway as the toolbar the extension provides includes a navigable help menu directly in it.\\n\\nIgnore the other stuff, but the line of buttons would look something like on this: http://commons.wikimedia.org/wiki/File:Enwp_edit_20120917_with_even_less_stuff.png\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-nv2bu7uh3huvidyjo4lk', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1391019141, 'spacePHID': None, 'dateCreated': 1348853520, 'dateModified': 1687919282, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz40601', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In link inspector, when you hover over a dropdown list item it should highlight (blue background), not only when using keyboard navigation', 'description': {'raw': 'Suggested by a user.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1354322608, 'spacePHID': None, 'dateCreated': 1346774100, 'dateModified': 1417573390, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39977', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Minimize unnecessary nowiki tags around quote marks', 'description': {'raw': 'The current wikitext escape algorithm adds excessive nowiki tags around quote marks.  While these are semantically correct and useful, for existing code, it introduces dirty diffs with the source wikitext.\\n\\nThis is not a problem if unmodified DOM subtrees are serialized using original wikitext source.  But, we dont this right now.\\n\\nTill such time, the code needs fixing to use heuristics to eliminate nowikis where the parser can figure out the right parse without nowikis.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-slccyo5rqasgpljxny7g', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1370993167, 'spacePHID': None, 'dateCreated': 1344977760, 'dateModified': 1370993167, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39352', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work', 'description': {'raw': 'The VisualEditor extension currently requires a Parsoid instance to handle wikitext (cf. $wgVisualEditorParsoidURL in VisualEditor.php). This makes installing and using the extension very difficult (or impossible) for third-party users wishing to use the extension with their MediaWiki installations.\\n\\nIdeally, calling out to an external Parsoid instance should not be necessary.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1555119418, 'spacePHID': None, 'dateCreated': 1342672800, 'dateModified': 1555119418, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38484', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: \"Edit Source\" link should preserve original query parameters (such as oldid)', 'description': {'raw': 'Currently just goes to latest revision, which is irritating.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1344295522, 'spacePHID': None, 'dateCreated': 1341265200, 'dateModified': 1417573406, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38125', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Automatically nowiki'ed magic links are shown differently after saving & re-editing round trip\", 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1362436146, 'spacePHID': None, 'dateCreated': 1340654640, 'dateModified': 1417585374, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37940', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Support for creating and editing definition-lists in VisualEditor', 'description': {'raw': 'As discussed.\\n\\nSee also:\\n* {T62411}\\n* {T54399}\\n* {T57797}'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1340654220, 'dateModified': 1721164816, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37938', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Highlight changes made since save in some way (e.g. with a text-background?) so users can see what changes they have outstanding', 'description': {'raw': \"From a VE test page:\\n\\nPerhaps a different colour font as you are editing...so you could keep track of what you're doing (TG)\\n\\nNot sure if we'd want to do this.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=60535\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1340643120, 'dateModified': 1643973253, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37931', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Selection popup arrow is overlapped by selection controls on iPad', 'description': {'raw': \"Screenshot of iPad simulator\\n\\niOS 5.1 simulator on Mac OS X. Screenshot attached.\\n\\niOS's selection handles overlap the arrow button we add, so it can't be clicked on.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9311}\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399324094, 'spacePHID': None, 'dateCreated': 1340472240, 'dateModified': 1417572394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37874', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"A link can span whitespace but won't be displayed, so cannot be edited or noticed\", 'description': {'raw': 'Take a two-word link (e.g. [[Example link]]). Use the VE inspector to select \"Example\" and press the remove-formatting button. Repeat with \"link\". Now the text is \"Example <a href=\\'...\\'> </a> link\", which is illegal wikitext, and renders as if there\\'s no link there.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': '40', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1340388420, 'dateModified': 1680974468, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37835', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'migrate MedaWiki from using BiDirectional characters by properly embedding any item using directionality syntax', 'description': {'raw': '**Author:** `gangleri`\\n\\n**Description:**\\nHi! It is long time ago since Nikerabbit installed Goylem a RTL testwiki. At that time I suggested the usage of BiDirectional characters to stabilize the common look and feel of pages as recent changes, etc.\\n\\nIt should be possible to obtain the same result by properly embed all objects and the delimiters (spaces or whatsoever) with directionality syntax.\\n\\nAn example is available at bug 36803#0\\nand http://en.wikipedia.org/?oldid=492307285#bugzilla ,\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1440920059, 'spacePHID': None, 'dateCreated': 1336886760, 'dateModified': 1440920059, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz36804', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Ctrl + K should trigger link inspector', 'description': {'raw': \"Pressing Ctrl + K doesn't work in chrome16/win7. It just produces a ? in the url bar instead with a dropdown option saying\\n\\n<Enter query> - Google search\\n\\nRepeated pressing does not solve the issue either.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340671640, 'spacePHID': None, 'dateCreated': 1335243600, 'dateModified': 1423061694, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz36201', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Sticky selection popup', 'description': {'raw': 'Playing around with text selection a bit I was able to find a \"sticky\" popup.\\n\\nEnvironment: Win7, Chrome 16\\n\\nWhat I did:\\n1. Select some text\\n2. Click on the small arrow that appears above the selected text\\n3. Select the \"create link\" icon\\n4. Neither input title for the link, nor close the popup\\n5. Instead take the caret somewhere else and select some other word\\n6. Repeat 4 and 5 a few times\\n\\nSoon, the following js error was generated:\\n\\nUncaught Invalid annotation error. Can not find non-annotation data in character.\\nbits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:54\\nve.dm.DocumentNode.getIndexOfAnnotation\\nbits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:54\\nve.ce.Surface.removeInsertionAnnotation\\nbits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:103\\nve.ce.Surface.annotate\\nbits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:102\\nve.ui.LinkInspector.onClose\\nbits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:133\\nve.ui.Inspector.close\\nbits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:123\\nve.ui.Context.closeInspector\\nbits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:129\\n(anonymous function)\\nbits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=ext.visualEditor.sandbox%2Cve%7Cext.visualEditor.special.sandbox%7Crangy&skin=vector&version=20120417T202352Z&*:122\\njQuery.event.dispatch\\nload.php:49\\njQuery.event.add.elemData.handle.eventHandle\\nload.php:42\\n\\nPlus, after a reload; I did the following:\\n1. Select text\\n2. Click on the arrow above it\\n3. Not click any icon but instead take the caret elsewhere. This should (as I see it) have ideally closed the popup, but it didn\\'t.\\n4. I clicked on bold and italics but that does nothing (since because the caret has moved there is currently no text selected).\\n5. Since the popup is still open, clicking on the link icon opens the link window, and closing it finally closes the popup.\\n\\nIf the first 4 steps are reproduced and step 5 is replaced by clicking on the tickmark instead of the close, nothing happens since no text is selected. The click neither inserts a link into the page, nor closes the popup. After this, even clicking on the close doesn\\'t close the popup. The caret can be moved and other text selected, but that just brings up the arrow and popup again. The previous popup still sticks. The popup finally went away on selecting an existing link in the text and clicking on the link icon in the toolbar. This made the link title appear in the popup and the close button finally worked.\\n\\nAfter another reload, I tried the following:\\n1. Select text\\n2. Click on the arrow\\n3. Select some other word. Now, selecting some other word automatically moves the popup to be near the new selection, i.e the popup is already open for the new selection if the popup for the original selection isn\\'t closed before making a new selection. Also, after step 2, since the popup is open, nothing below the popup can be selected without closing the popup first.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-4bjsher5mqcoikeqnnec', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343345020, 'spacePHID': None, 'dateCreated': 1335241260, 'dateModified': 1417573407, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz36200', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: All annotations are broken', 'description': {'raw': 'Editing annotations is broken in VisualEditor. Selecting some text and then clicking either Bold, Italics, Link, or Clear formatting has no effect. Tested in Chrome, Firefox 11, IE9, and Safari.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340403982, 'spacePHID': None, 'dateCreated': 1334532660, 'dateModified': 1340403982, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35999', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented\"', 'description': {'raw': 'Accessing http://www.mediawiki.org/ as a logged-in user with Konqueror 4.8.1, every page pops up a JavaScript alert: \"Rangy not supported in your browser. Reason: Neither Range nor TextRange are implemented\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-vk6mlmacfhx77egryy5i', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1353558325, 'spacePHID': None, 'dateCreated': 1334440320, 'dateModified': 1391610944, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35979', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Filter page listing specialpages by namespace (Special:ShortPages, Special:LonelyPages, Special:DeadendPages, Special:WantedPages, etc.)', 'description': {'raw': \"In pages such as Special:LonelyPages I would love to have an easy to access form which allowed filtering by namespace (à la Special:Allpages). Since MW 1.18, all $wgContentNamespaces are included in the default listing, but I think it would be nice to have some extra filtering.\\n\\nI've played a bit, by adding a $namespace parameter extracted from $wgRequest->getInt( 'namespace' ), but I would need some guiding about reusing it in more Special pages (for instance, also in WantedPages) and prepare a patch if this enhancement is considered interesting enough.\\n\\n= Additional context\\nSpun out of T170687:\\n\\nIt would be useful on many of the pages listed above in T170687#3439746\\n\\nE.g. \\nSpecial:ShortPages and Special:DeadendPages could then be used with the Help: and Project: namespace to find things to cleanup or merge\\nSpecial:LongPages could then be used with the usertalk namespace to find people to nag to archive their overwhelming talkpages.\\nSpecial:AncientPages could then be used with the Help: and Mediawiki: namespace to find things to update or reconsider the defaults.\\n\\nNote: Special:Random already has this functionality, similar to solution (f) but using full namespace names, per mw:Help:Random_page e.g. full list at https://en.wikipedia.org/wiki/Wikipedia:Random\\n\\n= Unknowns\\n[] Some design for how the filters should look. Tabs? A search form? A drop down? Is this covered in the UI standards spec?\\n[] More input\\n\\n\"}, 'authorPHID': 'PHID-USER-af2fdb5prucep2ihmjqc', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1333731000, 'dateModified': 1734098960, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35758', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: behavior switches are saved in parser environment', 'description': {'raw': \"parser patch to stub signature wikitext\\n\\nJust learning about the parser--these patches will match the __NOTOC__ etc. layout behavior switch keywords, and signature and timestamp strings.\\n\\nI'm not so confident about my decisions where to put these grammars.\\n\\nThe behavior switch keywords should probably turn into tokens which send control commands to set state in the sync23 stage.\\n\\nThe signature doesn't have access to the current username.  The timestamp has no locale or user timezone functionality.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F8819}\"}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340403756, 'spacePHID': None, 'dateCreated': 1332357960, 'dateModified': 1340403756, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35392', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: wrap parser output callback', 'description': {'raw': \"patch\\n\\nTotally trivial static function to abstract out __parseArgs[2] and explain.  It's possible that we want the flush() functionality to work differently in the future.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F9217}\"}, 'authorPHID': 'PHID-USER-p6hvqn5njgnxuagekh4b', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1341045649, 'spacePHID': None, 'dateCreated': 1332324900, 'dateModified': 1344281137, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35377', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'WikiEditor: Add SVG versions of editing toolbar icons', 'description': {'raw': 'WikiEditor toolbar icons are low-resolution raster images, and appear visibly pixelated on a high-resolution display such as iPad third-gen or when zoomed in.\\n\\nRecommend using SVG images with PNG fallbacks.\\n\\nNote that currently many of these images are sprited and may need to be re-separated and re-drawn.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-bxp7xrbobtrp5o3q3swv', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'dateClosed': 1435092327, 'spacePHID': None, 'dateCreated': 1332199740, 'dateModified': 1629487069, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35342', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide a way to \"sticky\" enable ResourceLoader\\'s debug mode', 'description': {'raw': '* If debug=true, remember in session\\n* the \"set debugmode\" code should check session in addition to GET query param\\n* going to debug=false will also unset it in the session\\n\\nAllows to navigate the wiki, submit forms (T37061), and stuff.\\n\\nTo prevent users from unknowingly staying in debug mode, JS should but up an informational notification on the page informing something short like: \"You\\'ve enabled debug mode of client resources delivery, click here to disable this\"\\n'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1331206980, 'dateModified': 1702397387, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz35063', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'mergeMessageFileList.php spews undefined notices of some extensions', 'description': {'raw': 'mergeMessageFileList.php spews undefined notices of some extensions for usages of DefaultSettings variables in their inclusion script\\n\\n\\nUpdating ExtensionMessages-1.19.php...\\nLoading data from /home/wikipedia/common/php-1.19/extensions/AbuseFilter/AbuseFilter.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/AntiBot/AntiBot.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/AntiSpoof/AntiSpoof.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ApiSandbox/ApiSandbox.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ArticleFeedback/ArticleFeedback.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ArticleFeedbackv5/ArticleFeedbackv5.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/AssertEdit/AssertEdit.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Babel/Babel.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CategoryTree/CategoryTree.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CentralAuth/CentralAuth.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CentralNotice/CentralNotice.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CharInsert/CharInsert.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CheckUser/CheckUser.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Cite/Cite.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Cite/SpecialCite.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/cldr/cldr.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ClientSide/ClientSide.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ClickTracking/ClickTracking.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CodeReview/CodeReview.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Collection/Collection.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CongressLookup/CongressLookup.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Contest/Contest.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CommunityApplications/CommunityApplications.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CommunityHiring/CommunityHiring.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CommunityVoice/CommunityVoice.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ConfirmEdit/ConfirmEdit.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ConfirmEdit/FancyCaptcha.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ContactPage/ContactPage.php\\nPHP Notice:  Undefined variable: wgSitename in /home/wikipedia/common/php-1.19/extensions/ContactPage/ContactPage.php on line 44\\n\\nNotice: Undefined variable: wgSitename in /home/wikipedia/common/php-1.19/extensions/ContactPage/ContactPage.php on line 44\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ContactPageFundraiser/ContactPage.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ContributionReporting/ContributionReporting.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ContributionTracking/ContributionTracking.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/CustomUserSignup/CustomUserSignup.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/DisableAccount/DisableAccount.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/DismissableSiteNotice/DismissableSiteNotice.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/DonationInterface/donationinterface_langonly.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/DoubleWiki/DoubleWiki.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/EditPageTracking/EditPageTracking.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/EmailCapture/EmailCapture.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ExpandTemplates/ExpandTemplates.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ExtensionDistributor/ExtensionDistributor.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/FeaturedFeeds/FeaturedFeeds.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/FlaggedRevs/FlaggedRevs.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/FormPreloadPostCache/FormPreloadPostCache.php\\nPHP Notice:  Undefined variable: wgUseFileCache in /home/wikipedia/common/php-1.19/extensions/FormPreloadPostCache/FormPreloadPostCache.php on line 11\\n\\nNotice: Undefined variable: wgUseFileCache in /home/wikipedia/common/php-1.19/extensions/FormPreloadPostCache/FormPreloadPostCache.php on line 11\\nLoading data from /home/wikipedia/common/php-1.19/extensions/FundraiserLandingPage/FundraiserLandingPage.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Gadgets/Gadgets.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/GlobalBlocking/GlobalBlocking.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/GlobalUsage/GlobalUsage.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/GoogleNewsSitemap/GoogleNewsSitemap.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ImageMap/ImageMap.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/InputBox/InputBox.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/intersection/DynamicPageList.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/LabeledSectionTransclusion/lst.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/LandingCheck/LandingCheck.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/LiquidThreads/LiquidThreads.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/LocalisationUpdate/LocalisationUpdate.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/MarkAsHelpful/MarkAsHelpful.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/MoodBar/MoodBar.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/MobileFrontend/MobileFrontend.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/MWSearch/MWSearch.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Narayam/Narayam.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/NewUserMessage/NewUserMessage.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Nuke/SpecialNuke.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/OAI/OAIRepo.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/OggHandler/OggHandler.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/OpenSearchXml/OpenSearchXml.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Oversight/HideRevision.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/PagedTiffHandler/PagedTiffHandler.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ParserFunctions/ParserFunctions.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/PdfHandler/PdfHandler.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Poem/Poem.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/PoolCounter/PoolCounterClient.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/PrefStats/PrefStats.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/PrefSwitch/PrefSwitch.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ProofreadPage/ProofreadPage.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Quiz/Quiz.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ReaderFeedback/ReaderFeedback.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Renameuser/SpecialRenameuser.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/RSS/RSS.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ScanSet/ScanSet.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/SecurePoll/SecurePoll.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ShortUrl/ShortUrl.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/SimpleAntiSpam/SimpleAntiSpam.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/SimpleSurvey/SimpleSurvey.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/SiteMatrix/SiteMatrix.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/SkinPerPage/SkinPerPage.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/skins/Schulenburg/Schulenburg.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/skins/Tomas/Tomas.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/SpamBlacklist/SpamBlacklist.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/SubPageList3/SubPageList3.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/SwiftCloudFiles/SwiftCloudFiles.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/UserThrottle/UserThrottle.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/timeline/Timeline.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/TitleBlacklist/TitleBlacklist.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/TitleKey/TitleKey.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/TorBlock/TorBlock.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Translate/Translate.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/TrustedXFF/TrustedXFF.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/UnicodeConverter/UnicodeConverter.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/UploadBlacklist/UploadBlacklist.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/UploadWizard/UploadWizard.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/Vector/Vector.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/WikiEditor/WikiEditor.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/VipsScaler/VipsScaler.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/VipsScaler/VipsTest.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/VisualEditor/VisualEditor.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/WebFonts/WebFonts.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/wikihiero/wikihiero.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/WikiLove/WikiLove.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php\\nPHP Notice:  Undefined variable: wgExtensionAssetsPath in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 27\\n\\nNotice: Undefined variable: wgExtensionAssetsPath in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 27\\nPHP Notice:  Undefined variable: wgLocalDatabases in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 115\\n\\nNotice: Undefined variable: wgLocalDatabases in /home/wikipedia/common/php-1.19/extensions/WikimediaIncubator/WikimediaIncubator.php on line 115\\nLoading data from /home/wikipedia/common/php-1.19/extensions/WikimediaMessages/WikimediaLicenseTexts.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/WikimediaMessages/WikimediaMessages.php\\nLoading data from /home/wikipedia/common/php-1.19/extensions/ZeroRatedMobileAccess/ZeroRatedMobileAccess.php\\n\\n--------------------------\\n**Version**: 1.19\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1343423081, 'spacePHID': None, 'dateCreated': 1329340740, 'dateModified': 1343423081, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34425', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'SemanticForms: Partial forms and nested templates.', 'description': {'raw': '**Author:** `van.de.bugger`\\n\\n**Description:**\\nI have a form with nested templates:\\n\\n> {{{info}}}\\n> {{{for template|Cache}}}\\n> ...Cache fields...\\n> {{{field|Locations|holds template}}}\\n> {{{end template}}}\\n> {{{for template|Cache/Location|multiple|embed in field=Cache[Locations]}}}\\n> ...Location fields...\\n> {{{end template}}}\\n\\nEverything works good. Page code looks as expected:\\n\\n> {{Cache\\n> |...Cache fields...\\n> |Locations={{Cache/Location|...}}{{Cache/Location|...}}...\\n> }}\\n\\nI have an additional *partial* form:\\n\\n> {{{info|partial form}}}\\n> {{{for template|Cache}}}\\n> <!-- No Cache fields, just next one. -->\\n> {{{field|Locations|holds template}}}\\n> {{{end template}}}\\n> {{{for template|Cache/Location}}}\\n> ...Location fields...\\n> {{{end template}}}\\n\\nAfter editing a page with this partial form, all the Location templates *moved* *out* of Cache, while Locations field receives strange value:\\n\\n> {{Cache\\n> |...Cache fields...\\n> |Locations=@replace_Cache___Locations@\\n> }}\\n> {{Cache/Location|...}}{{Cache/Location|...}}...\\n\\nThat\\'s obviously a big. Partial form should not move nested templates out of main template.\\n\\nHowever, there is a workaround: removing \"partial form\" specifier from partial form definition. Such a \"non-partial\" form produces correct result, but I am a bit afraid -- formally it is declared as partial form, so it does not have to save non-used fields of main template, does it?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'bug', 'closerPHID': 'PHID-USER-7jqnferdzzzwelhzchyo', 'dateClosed': 1682374235, 'spacePHID': None, 'dateCreated': 1328917020, 'dateModified': 1682374235, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34326', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Hitting enter on an empty list item should end the list', 'description': {'raw': 'Or at least Aryeh thinks so; I guess this is disputable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340401239, 'spacePHID': None, 'dateCreated': 1328023740, 'dateModified': 1368090037, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34096', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Ctrl+Home / Ctrl+End don't navigate the cursor to the beginning/end of the document\", 'description': {'raw': 'Pressing Ctrl+Home should send the cursor to the start of the document, but instead it sends it to the start of the line (same behavior as home). Similarly for Ctrl+End.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1349999703, 'spacePHID': None, 'dateCreated': 1328023500, 'dateModified': 1417573402, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34095', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"ApiQueryParseTree doesn't work when XML format is requested\", 'description': {'raw': \"**Author:** `neilk`\\n\\n**Description:**\\nSomething like this query:\\n\\n    http://wiki.ivy.local/w/api.php?action=query&prop=parsetree&titles=Main%20Page&format=json\\n\\nReturns a sensible data structure. However, when formatted as XML, an error is returned:\\n\\n    Warning: htmlspecialchars() expects parameter 1 to be string, object given in /Users/neilk/Sites/trunk/includes/Sanitizer.php on line 978\\n\\nI've tried other variants and sometimes I do get reasonable XML back but with empty contents. Is it not possible for the API to return arbitrary PHP data structures? Is there something to be done with 'indexed tags'?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1340400724, 'spacePHID': None, 'dateCreated': 1327970460, 'dateModified': 1350341879, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34058', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Add keyboard shortcut for heading level', 'description': {'raw': '**Author:** `utsavsabharwal`\\n\\n**Description:**\\nIt would be great if could add following shortcuts:\\n\\nctrl + { <-- For decreasing font size upto Heading 6\\nctrl + } <-- For increasing font size upto Heading 1\\n\\nLemme know if I can help you out :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1378254359, 'spacePHID': None, 'dateCreated': 1325686440, 'dateModified': 1417585270, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz33512', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'When translating a string at translatewiki.net, there should be a screenshot of the page where the string is used', 'description': {'raw': '- document the idea at [[ https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects | Mentorship programs/Possible projects ]]\\n- this project would use a lot of code from existing VisualEditor screenshots project'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'dateClosed': 1427800741, 'spacePHID': None, 'dateCreated': 1416494621, 'dateModified': 1428077477, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Imported items in actual sub-projects (VE, Parsoid, others?) should be tagged against the super-project too', 'description': {'raw': \"All the items in https://bugzillapreview.wmflabs.org/tag/visualeditor-data_model/ should also be in the main VisualEditor project, which is currently called https://bugzillapreview.wmflabs.org/tag/visualeditor-general/ (and per {T856} won't be re-named until after the import).\\n\\nI support the ~8000 bugs //could// all just be mass-added(?) after the import, but this feels like a perfect opportunity to get it done right from the start.\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'dateClosed': 1414491978, 'spacePHID': None, 'dateCreated': 1414167177, 'dateModified': 1416843686, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'High level overview of Phabricator projects', 'description': {'raw': \"Is this something that we want to have before the launch, right after the launch, or whenever it is ready?\\n\\n> [[ https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079117.html | On Wed, Oct 22, 2014 at 8:02 AM, David Cuenca  wrote ]]:\\n> \\n> Tagging is just a poor man's\\n> version of classing, since it doesn't let you define the relationship\\n> between tags. True that you can put any task in several projects/tags, the\\n> problem is that the project structure is nevertheless flat:\\n> https://phabricator.wikimedia.org/project/query/all/\\n> Which will become cumbersome to navigate for occasional visitors as the\\n> number of projects goes up.\\n\\nSure, but after years of Bugzilla we have also seen that the rigid tree structure of https://bugzilla.wikimedia.org/describecomponents.cgi causes many problems too, and occasional visitors probably find it cumbersome anyway.\\n\\nIf we want a high level overview of the projects, we can always have a wiki page identifying the main teams/projects, the starting points to understand the hundreds of projects that we will have soon. Now there is a task to discuss this.  :)\"}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 25, 'name': 'Low', 'color': 'yellow'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1453296382, 'spacePHID': None, 'dateCreated': 1414075117, 'dateModified': 1455052243, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'show avatar of assigned to field on cards displayed in workboard', 'description': {'raw': 'This would be useful to identify who is currently working on a card. Helps with visual scanning and clearly shows when certain people are \"hogging\" cards.'}, 'authorPHID': 'PHID-USER-5dwuaigmkz2vzg65lape', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '3', 'subtype': 'default', 'closerPHID': 'PHID-USER-lltif2drabccdkwhet7x', 'dateClosed': 1424274082, 'spacePHID': None, 'dateCreated': 1419872102, 'dateModified': 1464026626, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Use URL from foreign file repositories to search for images within VisualEditor', 'description': {'raw': 'What I want:\\n\\n1)  Open page.\\n2)  Insert > Image\\n3)  Paste in URL (from Commons)\\n4)  Insert image\\n\\n\\nWhat I got:\\n\\n1)  Open page.\\n2)  Insert > Image\\n3)  Paste in URL (from Commons)\\n4)  No image found.\\n5)  Remove most of the URL\\n6)  Insert image.\\n\\n'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1418779487, 'dateModified': 1418780592, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow to search tasks about MediaWiki core and core only (create MediaWiki umbrella project?)', 'description': {'raw': 'As a user looking for a report about a MediaWiki core bug, I want to quickly look for it without bothering about non-core reports or specific components/projects, so that I find what I\\'m looking for before I give up out of desperation.\\n\\n----\\n\\nCurrently, I must type N MediaWiki core projects manually in the \"Projects\" field. (Cf. https://secure.phabricator.com/T3670#65849, first bullet.)'}, 'authorPHID': 'PHID-USER-v7bwpq3rs3zdxegibdbh', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1417872973, 'dateModified': 1721662779, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Split off #Browser-Support-Opera-12 from #Browser-Support-Opera ', 'description': {'raw': 'Please split off a #Browser-Support-Opera-12 project from #Browser-Support-Opera. The Presto-based \"classic\" Opera 12.xx (and previous versions) is a completely different browser from the Chromium-based \"new\" Opera 15.xx (and later versions, currently at 26), having completely different and completely unrelated bugs. (There was no desktop Opera 13 or 14.)\\n\\nMost of the existing bugs under this project seem to be about Opera 12, but new reports are mostly about Opera 15+. I\\'ll be happy to re-triage them (getting the bulk task change permission would probably help).'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1421877681, 'spacePHID': None, 'dateCreated': 1417373028, 'dateModified': 1468889271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Tools in the toolbar do not have unique attributes', 'description': {'raw': 'This is a huge problem for test automation.\\n\\n- open any page in VisualEditor\\n- toolbar tools are located in `<div class=\"oo-ui-toolbar-tools\">`\\n- as far as I can see, there is no unique way to access a tool in the toolbar (example: click Insert tool)\\n- all of them share the same classes, and none of them have unique attributes, like `id`\\n- the only thing that is different is the string (Cite, Insert...), but since it changes when the UI language changes, it is not usable for us\\n- our test automation breaks all the time because elements in the toolbar move around, and the workarounds that we have at the moment are all fragile\\n- the best solution for us would be if every tool in the toolbar (undo, redo, paragraph...) had an unique id\\n- unique classes (or any other attribute, as long as it is unique) would work for us\\n- if there is an attribute used for translations, it would work for us, as long as each tool has and unique attribute\\n- this is not just a problem in toolbar, but let\\'s start somewhere'}, 'authorPHID': 'PHID-USER-fz7hkyvt4jypl76ieyol', 'ownerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'dateClosed': 1421988003, 'spacePHID': None, 'dateCreated': 1417094720, 'dateModified': 1438736469, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Insert media dialog appears to immediately abort request', 'description': {'raw': 'In test2 and production(betalabs does not display the error).\\n\\nIn VE, open any page for Edit and insert Media - \"Uncaught TypeError: undefined is not a function\" is immediately displayed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': 'PHID-USER-zq6nzfwxwkyliljd4lfy', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'bug', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1644536360, 'spacePHID': None, 'dateCreated': 1415381700, 'dateModified': 1644536360, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73141', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Don't trigger rubocop Jenkins job for changes that only modify php or js files\", 'description': {'raw': \"Change https://gerrit.wikimedia.org/r/#/c/171326/ shouldn't have to trigger bundle-rubocop.\\n\\nAffects at least mediawiki-extensions-VisualEditor and oojs-ui repos, probably more. \"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1422672525, 'spacePHID': None, 'dateCreated': 1415276340, 'dateModified': 1422672991, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73077', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Tool to set/unset background colour', 'description': {'raw': 'For completion.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1415217780, 'dateModified': 1643973261, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz73041', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: In the transclusion dialog, show the non-normalised parameter name if available?', 'description': {'raw': 'Per bug 67657, there\\'s now key.wt going to be available in the Parsoid output; if so, we should show that, not the key name, so that \"foo<!--OMG!-->bar\" is shown as \"foobar\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414694340, 'dateModified': 1416845506, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72771', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way to move pages through interacting with the displayed title', 'description': {'raw': 'An often encountered hurdle for new editors is that they can\\'t find out how to move a page. Generally they ask how to \"change the title\". Apparently - and understandably - in their mental model, the title of a page is part of the page. It would be nice if VE could accommodate that model. For that I suggest\\n* Make the page title editable\\n* If the new page title is a valid title, move the page to that location\\n** If the move fails, notify of the failure to automatically change the title, and link to the documentation of the move functionality, suggesting to do it manually.\\n* If the new page title isn\\'t a valid title, insert a {{DISPLAYTITLE}} element to the page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-n27daagbl3wqf3ghr4nk', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1414573980, 'dateModified': 1643973262, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72665', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Inserted images overlap preformatted text box', 'description': {'raw': 'images overlap preformatted text box\\n\\nBetalabs - desktop and mobile\\n\\nSteps to reproduce: \\n\\n1. In VE insert preformatted text \\n2. Insert an image  - observe that the image will be overlapping the preformatted text. \\n\\nThe two screenshots are attached.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F14713}'}, 'authorPHID': 'PHID-USER-4alekd35in5tg53zpsl4', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1437696733, 'spacePHID': None, 'dateCreated': 1414024200, 'dateModified': 1437696770, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz72411', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Blue link / red link logic should descend into links inside non-transclusion generated content nodes', 'description': {'raw': 'For the very few GCNs that generate wiki-link links (class=new etc.).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1491060374, 'spacePHID': None, 'dateCreated': 1412891220, 'dateModified': 1491865278, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71900', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Proposed external links should be validated before being created', 'description': {'raw': 'Open the link inspector and just type in double slash(forward), click done.It gets inserted in the CE as an external link.\\nThe external links should be validated for correct format.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ndwodmhxnp2vypdesdns', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1412776440, 'dateModified': 1643973263, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71795', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make it easier to see that there is an option to paste as plain text', 'description': {'raw': 'This suggestion comes from Gebruiker:Stratoprutser at nl.wp.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1412346900, 'dateModified': 1643973263, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz71612', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Be able to make block-level items centred (and other styles)', 'description': {'raw': 'A fr.wp editor uses centered lists in his sandbox, https://fr.wikipedia.org/wiki/Utilisateur:NemesisIII/Brouillon#Le_spectacle  (diff:  https://fr.wikipedia.org/w/index.php?diff=107080711&oldid=107080641 ).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409997000, 'dateModified': 1643973264, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70484', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Be able to search for an existing image by name', 'description': {'raw': 'Sometimes you know the name of an image, but need to be able to find it on a large page.  It would be convenient if searching (with Command-F or Control-F) could find the image this way.'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409542680, 'dateModified': 1437699249, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70243', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide three editing labels (\"Edit\", \"Edit source\" and \"Edit beta\") on it.wp', 'description': {'raw': 'Hello. As discussed in [[https://it.wikipedia.org/wiki/Discussioni_MediaWiki:Visualeditor-ca-editsource | :it:Discussioni_MediaWiki:Visualeditor-ca-editsource ]] we\\'d need a way to get the same editing labels of en.wiki (in italian, obviously), that are \"Edit\", \"Edit source\" and \"Edit beta\":\\n\\n* When VE is disabled by user, show these labels: \"EDIT\" (for wikitext)\\n* When VE is enabled, show these labels: \"EDIT SOURCE\" (for wikitext), \"EDIT BETA\" (for VE)\\n\\nNow on it.wiki there are \"Modifica sorgente\" (edit source) for the classic edit when VE is off and \"Modifica\" (edit) both for the VE edit and for the classic edit when VE is enabled. There\\'s a way to have three different labels to change according to the consensus that emerged?\\n\\nThanks,\\nHorcrux92\\n\\nP.S. Sorry for the probably erroneous categorization.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-vzowt52hw2qfnu2w3eim', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1409484180, 'dateModified': 1423953747, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz70230', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Allow setting all template parameters at once without having to pick which ones to enter', 'description': {'raw': 'A Wikipedia editor raised the following problem: When experienced Wikipedians want to add a template in the source editor, they can copy the template code without parameter values, which usually appears on template documentation pages, and then fill all the parameters one by one, and eventually delete the unneeded empty lines.\\n\\nIn VE, parameters must be added one-by-one, and this feels less efficient. As the default behavior this may be OK, but there can be a button that shows all the available parameters.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=72083'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1408434360, 'dateModified': 1643973264, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69734', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Entering \";\" does not trip the wikitext warning that it won\\'t work', 'description': {'raw': 'Lines starting with ; are not recognized as wikitext and just saved, only afterwards revealing their wikitext meaning:\\n\\nhttps://wikimania2014.wikimedia.org/w/index.php?title=User%3ADeryck_Chan%2FWMUK_report&diff=49488&oldid=49487\\n\\nReported: https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/;caption\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial'}, 'authorPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416971176, 'spacePHID': None, 'dateCreated': 1408359480, 'dateModified': 1442346024, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69689', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Please add an easy way to get from a citation template to the basic (manual) reference dialog', 'description': {'raw': 'Goal:   \\n\\n* Add something to an existing citation that the template shouldn\\'t include, like a {{verify credibility}} tag.\\n* Assign a citation to a references group.\\n\\n\\nSteps to reproduce:\\n\\n1.  Open a page containing a {{cite book}} template.\\n2.  Click on the citation to edit it.\\n3.  Think, \"Um, I don\\'t actually want this \\'\\'in\\'\\' the template; I want this \\'\\'after\\'\\' the template.\"\\n4.  Give up.\\n\\n\\n~~This can be done, if you happen to know that the thing to do is to select the ref, ignore the tag that pops up, go to the Cite menu, and choose Basic~~ (after Citoid replaced the old Cite menu, this is no longer possible).  But the ability to edit these refs would be more discoverable if the Cite Book dialog had a button at the bottom for \"Use reference editor\".\\n'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1601427334, 'spacePHID': None, 'dateCreated': 1407967980, 'dateModified': 1634144897, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69498', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Implement a proper code-review process for MediaWiki JS/CSS pages on Wikimedia sites', 'description': {'raw': \"MediaWiki: CSS/JS pages on any non-large wiki are usually a mess. Occasionally, we'll discover that wikis have been loading external resources for months and no one noticed. In addition, the local sysops maintaining those pages usually don't know JavaScript and are copy-pasting what someone else told them to do. Even when that's not the case, mistakes can result in code with [[https://szl.wikipedia.org/w/index.php?title=MediaWiki%3ACommon.js&diff=prev&oldid=208782|obvious syntax errors]] being sent to readers for long periods of time.\\n\\nVarious proposals have floated around over the years. The wikitech-l threads have some good discussion on some of the reasons why this is difficult for smaller wikis.\\n* Wikitech-l:\\n  * [[http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/74283|No longer allow gadgets to be turned on by default for all users on Wikimedia sites]] (specifically about Gadgets though)\\n  * [[http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/79080/|Deployment targets and preferences (was: Superprotect user right, Comming to a wiki near you)]]\\n* Wikimedia-l: \\n** [[http://thread.gmane.org/gmane.org.wikimedia.foundation/74166|Next steps regarding WMF<->community disputes about deployments]]\\n** [[http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/79055/|Superprotect user right, Comming to a wiki near you]]\\n\\n**See Also**:\\n* {T39230} (bug 37230)\\n* {T53651} (bug 51651)\\n* {T71550}\\n* {T121470}\\n* {T165981}\\n* {T120886}\\n* {T171563}\"}, 'authorPHID': 'PHID-USER-v7vgzvvcw7v2umf737ri', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1407872640, 'dateModified': 1722296813, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69445', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Reconsider whether you should be able to replace a selected node by typing / insertion tools', 'description': {'raw': 'Intention:\\nAttempting to replace a formula with text by selecting the formula does not work.  Simply nothing happens.  Either typing or pasting has the same null effect.  Attempting to replace a formula by inserting a template results in the template being inserted after the formula, not instead of it.\\n\\n\\n\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-imut7wxehhy35ukuzaks', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1407805620, 'dateModified': 1643973265, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69422', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: in the image advanced settings dialog, \"Wrap text around this item\" looks like a label of the alignment buttons', 'description': {'raw': 'The \"Wrap text around this item\" checkbox appears above the the alignment buttons and looks like a label for these buttons. The button group doesn\\'t have a label of itself. It should be moved around somehow so the separation between them will be clear.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1407316440, 'dateModified': 1416845524, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz69164', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Main application namespace should be capitalised and not 2 characters short (ve -> VisualEditor)', 'description': {'raw': \"Let's rename our global namespace to something longer than 2 characters and not identified by lowercase characters.\\n\\nProposing VisualEditor instead of 've'.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'dateClosed': 1530906840, 'spacePHID': None, 'dateCreated': 1404778500, 'dateModified': 1530906852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67642', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Only display the wikitext warning once per session', 'description': {'raw': \"1. '[[' to a paragraph and dismiss the wikitext warning\\n2. type in another paragraph then re-focus the [[ paragraph and type\\n3. the wikitext warning returns\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'ownerPHID': 'PHID-USER-x7ti5ksby4ubsabntlxa', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403811741, 'spacePHID': None, 'dateCreated': 1403710500, 'dateModified': 1417572135, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67083', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way to make images default sized without invoking a dialog', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1403637300, 'dateModified': 1643973266, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67048', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Image should not change size when going from read to edit', 'description': {'raw': 'When editing, \"default size\" in mw prefs is not honored.'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7x5ai23ne5qampjf3g7r', 'dateClosed': 1558739252, 'spacePHID': None, 'dateCreated': 1403637120, 'dateModified': 1558739256, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz67047', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Please strip trailing spaces and returns from media or image captions', 'description': {'raw': 'The solution for this may be related to Bug 61049:\\n\\nIf you add a caption to an image, and you press return in the text area box at the end (perhaps several times), then the caption includes those pointless blank lines, which makes for ugly wikitext when the page is saved.\\n\\nSee https://en.wikipedia.org/w/index.php?title=Sugar_candy&diff=613063549&oldid=611921250\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1403032080, 'dateModified': 1683796075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66736', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Problems changing image type from Thumbnail to Basic when surrounded by images with images in captions', 'description': {'raw': 'Go to this page:\\n\\nhttps://test2.wikipedia.org/w/index.php?title=User:RYasmeen_(WMF)/sandbox&oldid=87309\\n\\nChange the first image from Thumbnail to Basic and click on \"Apply Changes\"\\nThe following error appears in the console and cannot save page or cancel editing the page with VE.\\n \\n\\nUncaught Error: Offset could not be translated to a DOM element and offset: 55\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1530046412, 'spacePHID': None, 'dateCreated': 1402704660, 'dateModified': 1530051678, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz66604', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[DO NOT USE] Additional keyboard shortcuts (tracking) [superseded by #VisualEditor-EditingTools]', 'description': {'raw': '(Now tracked as part of #VisualEditor-EditingTools.)\\n\\nMore keyboard shortcuts help users.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416797403, 'spacePHID': None, 'dateCreated': 1401473640, 'dateModified': 1486690849, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65955', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Insert a <br /> when the user creates a new line from an existing blank link', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1529602058, 'spacePHID': None, 'dateCreated': 1400886180, 'dateModified': 1529602058, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65707', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow editing of a category link (not just add/remove)', 'description': {'raw': 'In the page options menu, you can add a category by typing its name in the \"add a category\" box and delete a category by clicking the the trash icon in the category inspector. However it\\'s not currently possible to **edit** the name of the category.\\n\\nFor example, if the page is currently in [[Category:Admirals of World War I]] and I want to put it in [[Category:Admirals of World War II]], I can do that easily in the wikitext editor by simply typing an extra \"I\".  In VisualEditor, I have to completely delete the first category and then add the second from scratch.'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400565600, 'dateModified': 1548593910, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65518', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"If a reference is defined in a template, and re-used outside of it, and you delete the template, then the reference contents get lost; similarly, copying citations defined inside a template doesn't work\", 'description': {'raw': 'Steps to Reproduce:\\n1. Start with a page that contains:\\n\\n(a) a template with a named ref inside it:  {{quote|Text.<ref name=Foo>Example citation</ref>}}\\n\\n(b) Some text outside the template that re-uses that citation:  Text.<ref name=Foo />\\n\\n2. Open the page in VisualEditor and remove the template.\\n\\n\\n\\nActual Results:  \\nThe named ref becomes undefined.  VisualEditor doesn\\'t \"see\" the citation inside the template, so it can\\'t rescue the re-used template-based citation content when the template is deleted.\\n\\nExpected Results:  \\nThat the citation content would be preserved, just like it is preseved when the first instance of a re-used citation in regular page text (outside of templates) is removed.\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1400094060, 'dateModified': 1683796075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz65301', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Translate and related extensions on AffCom wiki', 'description': {'raw': '**Author:** `admin`\\n\\n**Description:**\\nGreetings,\\nPlease enable the Translate and any related extensions to the affcom wiki (chapcom.wikimedia.org) to help us with drafting English based text that will later be utilized on Meta-Wiki. I recognize that actually marking the pages for translation could be problematic - the goal is primarily to utilize tags without making the wikipages difficult to proofread and edit.\\n\\nThank you!\\n-greg aka varnent\\nAffCom Member\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-xvs3y6hf6yrfn6sxrk5d', 'dateClosed': 1467150621, 'spacePHID': None, 'dateCreated': 1397876460, 'dateModified': 1467240667, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz64122', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a way (other than selection) to extend link (and other) annotations to more of the content', 'description': {'raw': 'When you add text on the left side of a link (external, internal) in article core the content is not merge with the link. T55210 asks to change this.\\n\\nWhen you add text on the left side of a link (external, internal) in the reference assistant the content is merge with the link. Someone asks to change this on https://fr.wikipedia.org/w/index.php?title=Wikipédia:ÉditeurVisuel/Avis&oldid=102556548#Gestion_des_liens\\n\\nA solution might be : On clicking a link, show 2 sliders (left/right of the current link) to handle easily  what is In what is Out of the link\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hhw22zfd2xzrsyc22lp5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1396823280, 'dateModified': 1643973267, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz63603', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Warn/stop users from inserting wikitext/bad inputs in the Gallery inspector', 'description': {'raw': 'Right now if , a user inserts wikitext inside gallery inspector such as <gallery></gallery> or <ref> inside gallery inserter, it adds an empty gallery inside the page and if you switch to edit source you will see something like:\\n<gallery><gallery><ref></ref></gallery></gallery>\\n\\n\\nOne possible solution to this issue could be let user know not to add any such wikitext/bad inputs inside gallery inspector\\n\\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: Chrome Version 26.0.1410.65 & FF 25\\nOS: MAC OS X 10. 8. 5\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1519255757, 'spacePHID': None, 'dateCreated': 1395169020, 'dateModified': 1519297363, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62799', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Be able to set a multimedia item's thumb position (thumbtime=) in the media dialog\", 'description': {'raw': \"Moved out of bug 38129's wishlist into its own bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394835120, 'dateModified': 1643973268, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62676', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Be able to set a multimedia item's start position (start=) and end position (end=) in the media dialog\", 'description': {'raw': \"Moved out of bug 38129's wishlist into its own bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394835000, 'dateModified': 1643973268, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62675', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Be able to set a multimedia item to not show an icon (noicon) in the media dialog', 'description': {'raw': \"Moved out of bug 38129's wishlist into its own bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394834880, 'dateModified': 1643973268, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62674', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Be able to set an item's alignment (baseline/middle/…) in the media edit dialog\", 'description': {'raw': \"Moved out of bug 38129's wishlist into its own bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394834640, 'dateModified': 1643973268, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62670', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Be able to set a over-ride thumbnail (thumb=…) in the media edit dialog', 'description': {'raw': \"Moved out of bug 38129's wishlist into its own bug.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394834520, 'dateModified': 1643973269, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62669', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Set up perceptual diffs (visual regression testing)', 'description': {'raw': \"This is something I've been experimenting with in spare time for a while.\\n\\nThe idea is: Render a visual diff for one or more pages and states thereof (comparing the result of the current change to the result of the latest master, or whatever target branch the commit has).\\n\\nThe screenshots would be created using PhantomJS' render() API. Or, while we don't need cross-browser per se, having a browser more representative than PhantomJS would be nice. Perhaps using Chromium under Xvfb with a large enough window (we don't need it to be very tall). And capture output from Xvfb using ImageMagic display `import`.\\n\\nRough idea for the Jenkins job:\\n\\n* Run project setup (e.g. build script for projects like OOjs UI and VisualEditor; installing MediaWiki for core/extensions). Then expose workspace to the local web server (We've got re-usable macros for this already).\\n\\n* Run the scenarios or urls for the current project and capture the screen after each scenario.\\n\\n* Compare them against the ones from the last run (e.g. for a commit to master, compare them to the latest master build). TODO: Will need to be stored somewhere. Shared NFS maybe? `store/{project}/{branch}`.\\n\\n* In test pipeline:\\n * If different, make sure the latest.png/change-after.png/change-diff.png for that url is kept and stored as build artefacts in Jenkins. Otherwise delete the image.\\n* In the post-merge pipeline:\\n * Replace the images in the store with those of this build.\\n\\nScenarios:\\n\\nI imagine we'll need to support two kinds of scenarios:\\n\\n* Plain url.\\n* Web driver steps (for large interfaces not accessible by url). This should *not* be used to trigger every possible dialog and component, that slows the test matrix and only tests for no reason. More useful would be to capture individual components via e.g. the OOjs UI demo page. Use these two assert the composition rather.\\n\\nA few urls we might want:\\n* mediawiki-core:\\n - /index.php?title=Main_Page\\n - /index.php?title=Main_Page&useskin=monobook\\n - /index.php?title=Main_Page&action=edit\\n - /index.php?title=Main_Page&action=history\\n - /index.php?title=Special:UserLogin\\n - /index.php?title=Special:UserLogin/signup\\n - /index.php?title=Special:Search&search=wiki\\n* VisualEditor:\\n - /demos/ve/#!/src/pages/empty.html\\n - /demos/ve/#!/src/pages/simple.html\\n - /demos/ve/#!/src/pages/complex.html\\n* oojs-ui:\\n - /demos/icons.html\\n - /demos/widgets.html\\n\\nA few implementations that exist:\\n* https://github.com/uber/image-diff/\\n* https://github.com/bslatkin/dpxdt/\\n* Talk (Velocity 2013): https://www.youtube.com/watch?v=1wHr-O6gEfc\\n* Talk (Google Developers): https://www.youtube.com/watch?v=UMnZiTL0tUc\\n\\nBehind these is basically just a ImageMagick compare command between two PNGs.\\n* https://github.com/bslatkin/dpxdt/blob/8e76f62e5/dpxdt/client/pdiff_worker.py#L115-L127\\n* https://github.com/uber/image-diff/blob/1.0.1/lib/image-diff.js#L53-L65\\n* http://www.imagemagick.org/Usage/compare/\\n````\\ncompare\\n      -verbose\\n      -metric RMSE\\n      -highlight-color RED\\n      -compose Src\\n      mytest-latest.png\\n      mytest-build.png\\n      mytest-diff.png\\n```\\n\\nSee also:\\n* {T64511}\"}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'stalled', 'name': 'Stalled', 'color': 'yellow'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394769900, 'dateModified': 1652228622, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62633', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'MultimediaViewer should work (or at least fail more gracefully)  on wikis where the images have no CORS headers', 'description': {'raw': \"Some MediaWiki installations have images hosted on a different domain than the wiki, and in some cases do not have an 'Access-Control-Allow-Origin' header on the image server domain. This causes the XMLHttpRequest for MultimediaViewer to fail, and nothing but a black screen appears. So that the usability isn't completely broken in these (and similar) situations, if the XMLHttpRequest to get the image fails for any reason, MultimediaViewer should fall back to simply displaying the image using an <img> tag.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-qze3uk4zsetjvgf7liey', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1394426460, 'dateModified': 1715810831, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz62469', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Apply styles for redirects/disambiguation links in suggestions in link inspector', 'description': {'raw': \"We apply red link styles to nonexistent titles in the link suggestions, so for redirects and disambig pages the corresponding styles/classes should be applied as well.\\n\\nI don't actually know what these are, ask James :)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1491060554, 'spacePHID': None, 'dateCreated': 1391818500, 'dateModified': 1567945039, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz61072', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Add a Preview feature to show actual version of page (minus slugs, etc.)', 'description': {'raw': 'VisualEditor has some deliberate/non-buggy differences in its display, compared to what readers will see on a saved page, such as the addition of blank lines/slugs to make adding new items at the top of a page.  These differences sometimes confuse users.\\n\\nAdd a preview button so that users can see the final version, rather than the slightly different VisualEditor version.\\n\\n**See Also**:\\n*{T49790}\\n*{T44139}\\n*{T39931}'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1390928460, 'dateModified': 1520384592, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60535', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor does not format hatnotes correctly', 'description': {'raw': 'comparison of screenshots\\n\\nCurrently, VisualEditor inserts blockSlugs around rellinks and dablinks (collectively known as hatnotes). This adds a lot of extra whitespace around them compared to how they are formatted normally. See attachment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n\\n**Attached**: {F13459}'}, 'authorPHID': 'PHID-USER-a5pveeqqwaddgfjiv2fq', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1390875300, 'dateModified': 1431049488, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz60516', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide option in media insertion dialog to only show local media', 'description': {'raw': \"**Author:** `gabriel.birke`\\n\\n**Description:**\\nThere is no way to make the VisualEditor Media selection to look only for local media (send iilocalonly when querying imageinfo). While this is ok for Wikipedia, it's not suitable for other wikis.\\n\\nThere should be a checkbox in the search dialog to switch to local only search.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1389260880, 'dateModified': 1643973271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59862', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Unable to select empty section heading (e.g., to remove it) at the end of a page', 'description': {'raw': 'Intention:\\nRemove a blank section heading (==<nowiki/>==) at the end of a page.\\n\\nSteps to Reproduce:\\n1. Place cursor on blank section heading at the end of the page.\\n2. Try to select it.\\n\\n\\nActual Results:  \\nNothing.  Also, it\\'s not possible to select the whole line (e.g., to cut and paste it, leaving nothing behind) even after you type something on the section heading.  If you type \"abc\", then you can select and cut \"abc\" (Note:  what it cuts is *not* \"==abc==\"), but the ==<nowiki/>== will remain.\\n\\n\\nReproducible: Always\\n\\nYou can test this at https://en.wikipedia.org/w/index.php?title=User:Whatamidoing_(WMF)/sandbox2&oldid=589158823\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1542996092, 'spacePHID': None, 'dateCreated': 1388854560, 'dateModified': 1542996093, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59651', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Console shows \"TypeError: jQuery1xxxxx is not a function\" when cross-domain ajax request is aborted', 'description': {'raw': 'Screenshot\\n\\nSteps to reproduce:\\n\\n1.Open a page with VE\\n2.Add any image\\n3.Open the dialog box to add image again\\n4.Type a different string in the textbox to search for matching images.\\n\\nObserved Result:\\nAn error appears TypeError: jQuery1830683983782510787_1388777743220 is not a function\\n\\nSee the screenshot attached \\nTest Environment: http://en.wikipedia.beta.wmflabs.org/\\nBrowser: FF 25\\nOS: MAC OS X 10. 8. 5 \\nPage:http://en.wikipedia.beta.wmflabs.org/wiki/New_pageimage?veaction=edit\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n\\n**Attached**: {F12791}'}, 'authorPHID': 'PHID-USER-24djtv3gj5gua2y6u2g5', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1403055051, 'spacePHID': None, 'dateCreated': 1388778000, 'dateModified': 1417571957, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz59604', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: If more than one section was changed, no section title should be shown in the edit summary', 'description': {'raw': 'To reproduce:\\n\\n0. Go to a page with two sections.\\n1. Click the \"Edit\" link on the second section.\\n2. Make some changes in the first section.\\n3. Press the save button.\\n\\nObserved: The second section\\'s name is shown in the summary.\\nExpected:\\n1. If only one section was changed, then that section\\'s title should be shown in the summary.\\n2. If more than section was changed, no section title should be shown.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: trivial\\n**See Also**: T53903'}, 'authorPHID': 'PHID-USER-xfe43w2lb5gpvglf4coa', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'bug', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1387043280, 'dateModified': 1695775729, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58488', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: When adding a reference, and a reference in a caption, in the same edit, then the ref in the caption is changed to the ref from the text', 'description': {'raw': '**Author:** `Wikifram`\\n\\n**Description:**\\nWhen I edit a page, and add a reference to the text and a different reference to an image caption, all in one edit, then the reference text for the image caption is not saved but gets changed to the reference text from the text (this already happens in the preview). You now get two references with the same text, even though you gave them a different text. \\n\\nExample: [https://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=840234&oldid=840227] (the image caption ref had a different text on typing)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-k5wpqok2x66oei3wguaf', 'dateClosed': 1726499498, 'spacePHID': None, 'dateCreated': 1386760560, 'dateModified': 1726499498, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58322', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: <ref> in media item caption in a <ref> isn't blocked, which means page can get into an uneditable state on load\", 'description': {'raw': '**Author:** `Wikifram`\\n\\n**Description:**\\nThis version of my sandbox at enwiki, [https://en.wikipedia.org/w/index.php?title=User:Fram/sandbox&oldid=585258547], is no longer editable in VE by me (FF25, W7). It opens, and I can make whatever changes I want, but the \"save\" button stays disabled, and when I open the reference interface, I can no longer close that one either. The category and media interface work allright though.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57573'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-k5wpqok2x66oei3wguaf', 'dateClosed': 1726500810, 'spacePHID': None, 'dateCreated': 1386683160, 'dateModified': 1726500810, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz58270', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'If the initial selection is a node (i.e. the document only contains nodes, no text), select the first node and display its context menu', 'description': {'raw': 'Steps to reproduce:\\n\\n1. Go to https://en.wikipedia.org/wiki/Wax_foundation\\n2. Click on \"Edit\".\\n\\nThe first image is automatically selected, and its four corners are replaced with image resizing icons, but \"Media\" image editing icon is not shown. I expected that the image would not be selected, or if selected that image editing icon is shown.\\n\\n3. Click on the second image.\\n4. Click again on the first image. Now the image editing icon should be shown.\\n5. Click on the image editing icon.\\n6. Click on the word \"frame\". Link editing icon should be shown.\\n7. Click on the link editing icon.\\n8. Enter \"Beehive frame\" (without quotes) in the text box.\\n9. Click on \"Apply changes\".\\n10. Click on \"Save page\". \"Save your changes\" dialogue appears.\\n11. Click on \"Save page\" in the new dialogue.\\n\\nThe VisualEditor displays \"Your changes to Wax foundation have been saved.\", but nothing has actually been saved.\\n\\nNow, I see three bugs here:\\n\\n1) The first image should not be selected automatically.\\n2) Possibly I have to do something after entering the link target in order for the target to be \"applied\" to the image caption? But I don\\'t see what it is that I should do.\\n3) The editor shouldn\\'t display \"changes have been saved\" message when there are no changes to be saved; doing so prevents the people from knowing that what they did was not saved, regardless of whether there was an error on their part or on the VisualEditor part.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=58248\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62542'}, 'authorPHID': 'PHID-USER-asiusr6cw73okn35tobw', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1385195700, 'dateModified': 1429559780, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57477', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor:  Automatic naming scheme for references produces meaningless names like <ref name=\":0\">', 'description': {'raw': 'Intention:\\nRe-use a reference.\\n\\n\\nActual Results:  \\nThe ref naming scheme needs improvements so that humans can remember which ref name they want to re-use, especially if they are using the wikitext editor, where they will not have any of the possible hints that VisualEditor may provide.\\n\\nExpected Results:  \\nA system that is \"xxx:0\", where \"xxx\" is text simply copied out from the beginning of the named ref would be an improvement.  We can assume that anything inside the ref is in a language that the editor is capable of coping with.  We can exclude the names of templates and their parameters, as well as \"http\" (otherwise, bare URLs in refs will produce a lot of equally unfriendly <ref name=htt:n> names).\\n\\nReproducible: Always\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-uf3buojo4ceizjywvyn5', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-vixhpqcaqfpdj6impfwy', 'dateClosed': 1431735575, 'spacePHID': None, 'dateCreated': 1385163660, 'dateModified': 1431735575, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57459', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Adding external link (wikitext style) should trigger wikitext warning', 'description': {'raw': 'In the linked diff I added an external link within single brackets.\\nIt didn\\'t trigger the markup warning - I wouldn\\'t know how to add such links in VE.\\nThe markup guide for en.wp says these links are \"Only used within article body for footnotes\", but of course they might be used also outside ns0.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/w/index.php?title=User%3AElitre_%28WMF%29%2Fsandbox&diff=582808389&oldid=582806629\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=57419'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398713139, 'spacePHID': None, 'dateCreated': 1385123700, 'dateModified': 1417572303, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57418', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Lots of CSS related noise in FF Web Console on enwiki', 'description': {'raw': \"Not urgent, but should probably be investigated and cleaned up were appropriate..\\n\\n[04:51:59.127] Unknown property '-moz-box-shadow'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.127] Expected 'none' or URL but found 'alpha('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.127] Unknown property 'zoom'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.127] Expected declaration but found '*'.  Skipped to next declaration. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.127] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.128] Error in parsing value for 'background'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.128] Error in parsing value for 'display'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.129] Error in parsing value for 'list-style-type'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.129] Unknown property 'user-select'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.130] Unknown property 'box-sizing'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.130] Error in parsing value for 'background-image'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.131] Unknown pseudo-class or pseudo-element '-webkit-input-placeholder'.  Ruleset ignored due to bad selector. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.131] Unknown pseudo-class or pseudo-element '-ms-input-placeholder'.  Ruleset ignored due to bad selector. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.gadget.DRN-wizard%2CReferenceTooltips%2Ccharinsert%2Cteahouse%7Cext.uls.nojs%7Cext.visualEditor.viewPageTarget.noscript%7Cext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cmw.PopUpMediaTransform%7Cskins.vector&only=styles&skin=vector&*:1\\n[04:51:59.168] Unknown property 'break-inside'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1\\n[04:51:59.169] Unknown property 'speak'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1\\n[04:51:59.169] Expected 'none' or URL but found 'chroma('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1\\n[04:51:59.170] Unknown property 'zoom'.  Declaration dropped. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1\\n[04:51:59.170] Expected media feature name but found '-webkit-min-device-pixel-ratio'. @ https://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=site&only=styles&skin=vector&*:1\\n[04:51:59.716] Unknown property 'box-sizing'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page\\n[04:51:59.812] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:4\\n[04:51:59.812] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:4\\n[04:51:59.812] Error in parsing value for 'unicode-bidi'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:6\\n[04:51:59.812] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10\\n[04:51:59.812] Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10\\n[04:51:59.812] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10\\n[04:51:59.812] Unknown property '-moz-box-shadow'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10\\n[04:51:59.812] Unknown property '-moz-background-clip'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10\\n[04:51:59.812] Expected 'none' or URL but found 'progid'.  Error in parsing value for 'filter'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10\\n[04:51:59.812] Error in parsing value for 'background'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:10\\n[04:51:59.812] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12\\n[04:51:59.812] Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12\\n[04:51:59.813] Unknown pseudo-class or pseudo-element '-o-prefocus'.  Ruleset ignored due to bad selector. @ https://en.wikipedia.org/wiki/Main_Page:12\\n[04:51:59.813] Error in parsing value for 'background'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12\\n[04:51:59.813] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12\\n[04:51:59.813] Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:16\\n[04:52:00.137] Unknown property '-moz-box-shadow'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:2\\n[04:52:00.138] Expected 'none' or URL but found 'alpha('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:2\\n[04:52:00.138] Expected 'none' or URL but found 'alpha('.  Error in parsing value for 'filter'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:12\\n[04:52:00.138] Unknown property '-moz-background-clip'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14\\n[04:52:00.138] Unknown property '-moz-background-origin'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14\\n[04:52:00.138] Unknown property '-moz-border-radius'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14\\n[04:52:00.138] Expected color but found 'bottom'.  Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14\\n[04:52:00.138] Error in parsing value for 'background-image'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14\\n[04:52:00.138] Unknown property '-moz-border-radius-topleft'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14\\n[04:52:00.138] Unknown property '-moz-border-radius-topright'.  Declaration dropped. @ https://en.wikipedia.org/wiki/Main_Page:14\\n\\n--------------------------\\n**Version**: 1.23.0\\n**Severity**: minor\"}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385065447, 'spacePHID': None, 'dateCreated': 1385009520, 'dateModified': 1385065447, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57339', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide dialog to enter and edit templates', 'description': {'raw': \"It would be very nice if WikiEditor had a dialog to work with templates the way VisualEditor has. There is also a user script: [[User:קיפודנחש/TemplateParamWizard]], but IIRC this script doesn't use the informations provided by TemplateData, but uses its own format.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-tyjmn7xcw6s2b6rqagj7', 'ownerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-wrimmmr5w2zt7nk2t753', 'dateClosed': 1542127013, 'spacePHID': None, 'dateCreated': 1384851900, 'dateModified': 1564918790, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz57232', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: do not remove line break before first category when a user deletes {{DEFAULTSORT}}', 'description': {'raw': 'There should be a line break (ENTER) between \"{{Álgebra}}\" and \"[[Categoria:Estruturas algébricas]]\" on these edits:\\nhttps://pt.wikipedia.org/wiki/Anel_%28matem%C3%A1tica%29?diff=37240720\\nhttps://pt.wikipedia.org/wiki/Corpo_%28matem%C3%A1tica%29?diff=37240730\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1383471540, 'dateModified': 1429549007, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz56530', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor inspector for SyntaxHighlight is too tiny with no resize option', 'description': {'raw': 'screenshot\\n\\nWhile we can\\'t yet just click into a <source> SyntaxHighlight extension chunk and edit it, I notice we can now click a \"<>\" button that opens a plaintext editor for the contents. Awesome!\\n\\nUnfortunately the popup box for this seems really small, and there doesn\\'t appear to be any way to resize it (no resize handles or zoom button that I can find).\\n\\nEspecially for editing source code blocks, being able to bump the size waaay up would be very helpful.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\\n**URL**: https://www.mediawiki.org/wiki/Manual:CORS?veaction=edit\\n\\n**Attached**: {F12119}'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1445531026, 'spacePHID': None, 'dateCreated': 1382271000, 'dateModified': 1446250276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55934', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow the veaction=edit URL to over-ride namespace restrictions', 'description': {'raw': \"On the English Wikipedia, I'd like to be able to use the VisualEditor on any namespace, but especially the project namespace.\\n\\nGiven that VisualEditor is opt-in and already regularly breaks pages anyway, I don't think lifting the arbitrary namespace restriction on wikis where VisualEditor is opt-in (such as the English Wikipedia) will be problematic.\\n\\nSubmitted for consideration. CC'ing James and Roan.\\n\\n--------------------------\\n\\nSee also: {T57968}\"}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'duplicate', 'name': 'Duplicate', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1558193302, 'spacePHID': None, 'dateCreated': 1381937700, 'dateModified': 1558193302, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55792', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Flow: VE takes significant time to manifest', 'description': {'raw': 'We have been encountering a number of performance issues and race conditions with VE and Chrome in recent times, this is probably one more of those. \\n\\n* In a fresh instance of Chrome 30 or Chrome 29, as a logged in user, visit https://en.wikipedia.beta.wmflabs.org/wiki/Special:Flow/Flow_QA\\n\\n* Enter a Message topic\\n\\nThe VE controls and CE field take significant time to appear while the user sees a spinner.  For an example causing a failure in a browser test, see https://wmf.ci.cloudbees.com/job/Flow-en.wikipedia.beta.wmflabs.org-linux-chrome/12/testReport/(root)/Create%20new%20topic%20logged%20in/Add_new_Flow_topic/ .  Note the test times out with the spinner still visible after 5 seconds. \\n\\nThis is not seen in Firefox\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-kqibbfgfpgocyzwe32lv', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1390958494, 'spacePHID': None, 'dateCreated': 1381877940, 'dateModified': 1418984708, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55766', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Use a hidden preference rather than cookie for logged-in users to remember hidebetawelcome', 'description': {'raw': \"**Author:** `swalling`\\n\\n**Description:**\\nThe introductory dialog for VE is supposed to be seen only once per person. However, it seems that the way it is hidden for users is dependent on session information, probably a cookie? \\n\\nThis means that every time I clear my cookies, open an incognito browser window, use a new browser, or use a new device, I get the intro again. Even if I'm using the same account. This stinks. \\n\\nIn GuidedTours we solve this problem (not showing users repeated intro tours across devices/sessions) by setting a hidden preference when someone completes a tour. I'd like to suggest we do that for the VE intro, unless someone can think of a more elegant way to avoid this annoying behavior.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399723505, 'spacePHID': None, 'dateCreated': 1381393200, 'dateModified': 1443278227, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz55551', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '\"Publish and submit\" button shouldn\\'t be available because it shouldn\\'t be used', 'description': {'raw': 'Per discussion with Krinkle on IRC, the \"publish and submit\" button in Gerrit should not be used.\\n\\nIf this is the case, it should not be present.\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-oetk6bbl6omm354ejz3b', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-oetk6bbl6omm354ejz3b', 'dateClosed': 1469470370, 'spacePHID': None, 'dateCreated': 1380910920, 'dateModified': 1469470370, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54987', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Parsoid treats [[[[Foo]]]] as plain text, but the PHP parser treats it as [[<a href=\"Foo\">Foo</a>]]', 'description': {'raw': \"(Where the word is the actual working part of the element).\\nProbably not a real bug, since it is triggered by a user mistake (who should remove the brackets), but since it's easily reproduceable, here are the steps:\\ntake any <nowiki>[[link]]</nowiki> created like this (by ignoring the markup warning).\\nVEdit the page and use the linking tool on the word inside the brackets.\\nSave, you now have [[[[link]]]], and of course the nowiki tags are gone.\\n\\nhttps://www.mediawiki.org/w/index.php?title=User:Elitre_(WMF)/SandboxVE&diff=prev&oldid=794483\\n\\nhttps://www.mediawiki.org/w/index.php?title=User%3AFram%2FSandbox&diff=794473&oldid=794472\\n\\nJust interested in understanding whether VE wants or can do something about it.\\n\\n(Note that it is absolutely possible to get the same result with the traditional editor as well, https://sl.wikipedia.org/w/index.php?title=Klerofa%C5%A1izem&diff=next&oldid=4101482 ).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': 'PHID-USER-hbtlbu4zftxnz4i6f7yf', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1388700395, 'spacePHID': None, 'dateCreated': 1380727020, 'dateModified': 1388700395, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54877', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[DO NOT USE] VisualEditor: Tracking bugs for VisualEditor (tracking) [superseded by #VisualEditor]', 'description': {'raw': \"[Unused; we don't do tracking bugs, post-Phabricator transition.]\\n\\nA central place for people to keep track of tracking bugs for VisualEditor. (Yay for bug meta-ness.)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416796877, 'spacePHID': None, 'dateCreated': 1379656500, 'dateModified': 1486690926, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54363', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Customized legacy edit toolbar does not always load correctly', 'description': {'raw': \"Missing scan and edit toolbar\\n\\nI am posting three separate bugs and mentioning this in this first report because they are somewhat related.\\n\\nThe user defined edit toolbar, defined in my very simple\\nhttps://en.wikisource.org/wiki/User:Ineuw/common.js stopped functioning in this latest version of the mw software. In versions previous, it worked reliably and always, permitting me greatly increased productivity. The toolbar does show up intermittently and occasionally. \\n\\nRegardless of the toolbutton definition syntax used, the same intermittent functioning is the result. The syntax is either the current definition one, or an older one:\\n\\nmw.toolbar.addButton(\\n        '',\\n        ' Æ ',\\n        'Æ',\\n        '',\\n        '',\\n        ''\\n);\\n\\nI also used the definitions without image buttons, thinking that this may be the cause, but it doesn't make a difference.\\n\\nThe problem is also not browser related. I tried other browsers and OS's as well:\\n\\nFirefox in Windows, Xubuntu, and Apple OSX.\\nSafari in Windows and Apple OSX.\\nGoogle Chrome in Windows and Linux (Xubuntu).\\nbut the intermittent behaviour is the same. . . . . \\n\\nFinally, this is also true on the Commons and Wikipedia, where it's less critical because I am not so active on those wikis.\\n\\nPlease see attached image.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n\\n**Attached**: {F11589}\"}, 'authorPHID': 'PHID-USER-kdpydfvhr2l2qcrbvvz7', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1379736095, 'spacePHID': None, 'dateCreated': 1379578860, 'dateModified': 1459674863, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz54308', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Link input widget should have separate inputs for target and display text', 'description': {'raw': 'The link input widget should have separate fields for the link target and the displayed text.\\n\\nFrom various comments at T50789\\n\\n> There are essentially two ways to create a link:\\n> \\n> […]\\n> \\n> #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.\\n> \\n> […]\\n> 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.)\\n> \\n> 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> \\n> a) the dialog popup window has a clear OK button, and [T54462]\\n> \\n> b) the dialog popup window contains separate clearly labeled boxes for the link text and the link target. \\n> \\n> I believe both of these changes make a lot of sense.\\n\\n---\\n>>! In T50789#510194, @Thryduulf wrote:\\n> An 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> \\n> 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. \\n>\\n> See also T53438\\n\\n---\\n>>! In T50789#510207, @Thryduulf wrote:\\n> 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. \"\\n> \\n> 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]]\\n> If someone gives a link title (e.g. Hedgehog) but doesn\\'t specify a target, produce the link: [[Hedgehog]].\\n\\n--------------------------\\n**See Also**: T52945'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '40', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1530193718, 'spacePHID': None, 'dateCreated': 1378772640, 'dateModified': 1622138005, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53973', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Let template's navboxes (VTE links) be used in VE edit move\", 'description': {'raw': '<< Currently when you click on a template with the \"VTE\" (view, talk page, edit) links, Visual Editor gives you the option of adding parameters to the transclusion of the template. Most of the templates with the \"VTE\" links are navigational boxes or other transcluded items without parameters, but as the VTE links suggest, we want people to easily view the template page itself. Maybe if someone clicks on a template with VTE links in Visual Editor, rather than being given the regular option to add parameters they should instead be given a dialogue box saying something along the lines of \"This is a template that appears on many pages. Would you like to open this template\\'s page in a new tab?\". —[[User:Arctic.gnome|Arctic Gnome]] <small>([[User talk:Arctic.gnome|talk]] • [[Special:Contributions/Arctic.gnome|contribs]])</small> 13:45, 20 August 2013 (UTC) >>\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-wil4b5lylrvf3krixlkl', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1377012600, 'dateModified': 1643973275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz53099', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: The alpha opt-in user preference description includes a hardcoded and incorrect list of namespaces', 'description': {'raw': '\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51527'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1385396577, 'spacePHID': None, 'dateCreated': 1375013100, 'dateModified': 1417572746, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52188', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Be able to set table cell background (and other formatting options)', 'description': {'raw': \"**Author:** `jonathan_haas`\\n\\n**Description:**\\nIt's currently impossible to change table cell background VE\\n\\nSee for example http://de.wikipedia.org/wiki/Suriyakati-Kalender\\n\\n**See also**\\n* Open subtasks of {T49780} \"}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '8', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1375007580, 'dateModified': 1656500386, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52180', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Make the edit summary a mini-VE surface so users can put in links etc.', 'description': {'raw': 'Links are frequently placed in edit summaries but the user is currently perversely required to revert to wikicode to insert them.  The VisEd menu should be available for the edit summary and the text should be displayed as it will be seen.  Wysiwyg should apply to all elements of the edit summary (eg, the recently added section title is displayed as code rather than the grey italics as it will be seen).\\n\\n=== Potential use cases/impacts/hypotheses \\n- **[potential impact]**: if people publishing edits write more expressive edit summaries, these edit summaries will be compelling/interesting to people whose primarily relationship to Wikipedia is as as a reader\\n-- //See more in {T379405}\\n- **[potential use case]**: enable people to relate edits to the events/campaigns that inspired them to make them (T373232)\\n-- //Inspired @AlexHollender-WMF and @ifried...//\\n- **[hypothesis]** If people have an easier time doing things like mentioning other people, inserting links, and formatting text within the edit summary input, they will invest more effort into writing edit summaries.\\n- **[potential impact]** If people write more descriptive edit summaries, then machine learning models will become more effecting at learning from the actions volunteers are taking because these models will have to make fewer inferences/assumptions about the semantic meaning of a change/changes someone is making. //This thought is inspired by the conversation we (the Editing Team) had with @diego on 27 July 2022.//\\n- **[potential impact]** If people write more descriptive edit summaries, then people visiting an article\\'s \"page history\"  will have an easier time: A) understanding how the article they are interested in evolved over time and B) identifying changes they are curious to learn more about\\n-- this could also open up the potential for edits/diffs being presented as small, standalone pieces of information people could \"consume\" \\n\\n=== Related\\n- T123529\\n- T323875\\n- https://hashtags.wmcloud.org/'}, 'authorPHID': 'PHID-USER-imut7wxehhy35ukuzaks', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374996120, 'dateModified': 1733258505, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52174', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a mechanism to disable VisualEditor on a given page (to be used if it corrupts said page)', 'description': {'raw': \"There are many pages for which VisualEditor is broken.  In some cases, the page syntax can be changed to avoid the problem.  In other cases (such as nlwp's largethumb, dewp dab pages, enwp episode lists), the design affects many pages, and the only feasible solution is to fix the parser.  While we wait for fixes, the VE should be disabled on those pages known to be affected.\\n\\nThe set of pages to be VE-disabled could be a category, if you trust the villagers..:-)\\nOr a page title blacklist in MediaWiki: namespace so it is admin only\\nOr a page content regex blacklist in MediaWiki: namespace so it is easier to blacklist all pages which include a certain element.\\n\\n**See Also**: {T55767} (also declined)\"}, 'authorPHID': 'PHID-USER-oxd6f6xemkuyttw7z7wl', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1437697879, 'spacePHID': None, 'dateCreated': 1374931800, 'dateModified': 1556353001, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52141', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Template dialog should make use of guessed/inferred TemplateData for templates without it', 'description': {'raw': \"The Visual Mode editor of Wikia is able to check all the available parameters automatically without the need for editors to edit the TemplateData for each template manually which is unrealistic to be done for over 505k templates on English Wikipedia.\\nHowever, Wikia's template editor has a severe flaw that it cannot handle a template to be included inside another template. The visual editor will deem the coding to be too complex and forcibly switch back to source mode editor.\\n\\n--------------------------\\n**See Also**:\\nT54581 / {T191756}\"}, 'authorPHID': 'PHID-USER-xnvlg7y5phtzugavv6wj', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374901500, 'dateModified': 1585736933, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz52135', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Allow preference to move toolbar to over navigation sidebar', 'description': {'raw': 'The editor an en.wp who signs as \"Josh, linguist\" has left the following suggestion about toolbar placement in the Visual Editor:\\n\\n\"I\\'ve encountered a sort of inconvenience which is the following: while editing, the toolbar occupies a significant area in the upper third visually and otherwise blocking the text, when we, at the same time, usually have an unoccupied area to the left (where the navigation column is which is often empty much below the existing items); the question is why not to devise a possibility, an option to change its place — I mean the toolbar could be opted to place it either where it\\'s offered to be now – or, otherwise, on the left side of the pane – where it should not be blocking an essential area of the text to edit, in this case the text available without scrolling will be by, approximately (depending on your zoom), a half more than it is now.\"\\n\\nFor RTL wikis read \"right\" instead of \"left\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374662220, 'dateModified': 1643973275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51951', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'If the user only has edited in one section, VisualEditor should insert the name of the edited section into the edit summary', 'description': {'raw': 'one thing that makes life better with existing editor is the fact that when editing a specific section, the section name is automatically added to the edit summary. often, this ends up being the entire edit summary.\\n\\nREQUESTED ACTION\\n1) when hitting \"save\", test to see if all the diffs are contained in a single section, and if so, add the section name to the edit summary automatically.\\n2) just like with existing editor, allow the user to modify or remove this part. i.e., the request is to pre-populate the summary box, not to add section name outside of summary box such that the user can\\'t touch it.\\n\\npeace.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**: T54859, T50274, T52872, T60488'}, 'authorPHID': 'PHID-USER-akv4ingxkspiiam6r2n4', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374605160, 'dateModified': 1643973275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51903', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide a web interface for customizing an MediaWiki instance and provisioning it in the cloud or locally', 'description': {'raw': 'The basic idea is to have a clear and pleasant-to-use web-based interface for generating a MediaWiki instance manifest. The interface should allow you to tick off the extensions you want, for example, and it would automate the configuration of supporting software like Apache and memcached. There\\'s an attractive example of such an interface at <https://puphpet.com/>.\\n\\nMediaWiki-Vagrant already implements the bulk of the work in that it provides a set of parametrized, MediaWiki-oriented Puppet modules and resource types. In plain English: MediaWiki-Vagrant can take a configuration file that says \"give me a MediaWiki instance with Scribunto and VisualEditor that is set up for development work\" and configure a machine to match these specifications.\\n\\nA number of cloud computing platforms provide hooks for uploading Puppet code to automate the creation and customization of servers. Some are event implemented as Vagrant \\'providers\\', which means that you can run \\'vagrant up\\' and Vagrant will create a cloud instance rather than a VirtualBox VM. Examples include vagrant-rackspace for Rackspace Cloud (<https://github.com/mitchellh/vagrant-rackspace>) and vagrant-aws (<https://github.com/mitchellh/vagrant-aws>) for Amazon AWS. A vagrant-openstack provider (<https://github.com/aodn/vagrant-openstack>) also exists; I don\\'t know how much work it would take to make it work with Labs.\\n\\nThe major work-item would be to build the web interface (or adapting the source code of <https://puphpet.com/> or some other project -- there are several), ideally as a MediaWiki extension so that we can offer the ability to provision a virtual server (either local or cloud-based) right on MediaWiki.org.\\n\\nI think that this could considerably broaden the appeal of MediaWiki to a new generation of internet users. The success of Wikia shows that there exists considerable demand for point-and-click wiki creation. It could also help drive third-party usage of VisualEditor / parsoid, if it is true that adoption is held back by anxiety over having to configure and maintain an additional software component.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-r7wrkcx7j2vutqs6hr3g', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1374439020, 'dateModified': 1643973275, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51782', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Clear formatting button should not remove links', 'description': {'raw': 'The \"clear formatting\" button returns bold and italic text to its plain state, as expected. However it also removes any links in the selection, which is not expected, rather there should be a separate \"unlink\" button to do this job - conceptually I regard a link as an attribute not as formatting.\\n\\nFor example selecting a bolded sentence with an italicised title and a linked word in it. I clicked the clear formatting intending to clear the bold and italic, which it did but it also removed the link. Similarly if using it to remove a link it also removes bold/italic which is unlikely to be the intention.'}, 'authorPHID': 'PHID-USER-ysftv67jxeaxdwcakvwo', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1445613258, 'spacePHID': None, 'dateCreated': 1374344100, 'dateModified': 1445613258, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51757', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support for SFN and similar references', 'description': {'raw': 'One of the major advances in wiki editing in the last few years has been support for the short template-based referencing systems like SFN. I\\'ve made it a basic rule to use SFN if a reference is used more than twice within the article, and an inline only in the rare case where it is used once or twice. I realize my editing patterns are not normal, but I think support for these templated refs would improve the editor greatly. \\n\\nPerhaps a \"toolbar-like\" editor to one side of the main editor could list of global references created so far, and allow the user to drag a handle from them into the article to place the ref in the body.\\n\\nEven better, perhaps the use could drag URLs or text into the bar to create semi-filled out master refs.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-5tluooawvjfhtqywnxag', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393541245, 'spacePHID': None, 'dateCreated': 1374057780, 'dateModified': 1442227600, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51522', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Feature request for VisualEditor language setting  +ULS +Wikidata interwikis', 'description': {'raw': 'Hi,\\n\\na: Currently language list displayed below MediaWiki:Visualeditor-dialog-meta-languages-readonlynote/mr does not open the respective language wiki but when that is possible along with that respective language item ULS should offer option to open up the respective language wiki with related display and/or input .May be this shall need to mingle three extensions VE,wikidata,ULS and also\\n\\nb When in menubar languages displayed by wikidata if curser hover over any wiki language name options as requested in 4a should display and available. (Whether this needs to split as a separate bug ?)\\n\\n\\n\\n*To understand further the need for above request,please do refer to survey\\ndata and analysis provided at\\nhttp://www.mediawiki.org/wiki/Talk:Universal_Language_Selector#feature_to_make_content_language_input__default_28864\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51431'}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373886360, 'dateModified': 1643973276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51355', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a tool to insert a talk signature in namespaces that need it', 'description': {'raw': \"The ability to sign posts is useful outside of talk name spaces. For instance http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback is in project space. While that might one day be in flow there are many other project space items where  its useful to be able to sign. For instance lists of project members. Some uses have guest books in the User: space which can be signed. \\n\\nYou can't even enter them manually due to T51820.\\n\\nA button to insert this would be good, possibly done at the same time as bug 38029 which would insert symbols.\\n \\nThis was discussed at http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback/Archive_2013_07#Let_me_sign.21\\n\\n----\\n\\nVisualEditor now allows you to insert signatures on pages that are in `$wgExtraSignatureNamespaces` (and any talk pages).\\n\\nThis was previously implemented as a user script / gadget is available at https://meta.wikimedia.org/wiki/User:Matma_Rex/visualeditor-signature.js.\"}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1447719434, 'spacePHID': None, 'dateCreated': 1373511180, 'dateModified': 1636670831, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz51154', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Come up with a different name for \"Preformatted\" in the text formatting menu', 'description': {'raw': '**Author:** `mcdevitd`\\n\\n**Description:**\\n\"Preformatted\" is HTML jargon which most of VisualEditor\\'s target users will not understand, and it actually produces an effect (text with less formatting) which is unexpected if you don\\'t know what it means beforehand. It should either be given a plain-language name so that people will expect the behavior, or removed.\\n\\nI actually don\\'t understand why this style effect is in the header-level pull-down when it is not a header-level. My preference is to remove it, since it is uncommon and mostly adding noise, but it should be renamed if kept.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1373247780, 'dateModified': 1643973276, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50918', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Remove Opera from blacklist', 'description': {'raw': \"I think we can (almost) remove Opera from the blacklist now, see blocking bug 36000. Opera < 12 should still probably be blacklisted, though, and < 10 should be blacklisted for sure (there's a bunch of people who insist that 9.64 was the ultimate version ever and stick to it).\\n\\nIt'd be cool if it could be added to the whitelist as well, but I guess that would be a promise to support it and you guys probably don't want to promise that ;)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375135090, 'spacePHID': None, 'dateCreated': 1373044680, 'dateModified': 1417572958, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50813', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: VisualEditor needs easter eggs', 'description': {'raw': 'Because.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-z6nzrwuaij3spgyg23jt', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1393642162, 'spacePHID': None, 'dateCreated': 1373035320, 'dateModified': 1496862178, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50804', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Adding or updating a reference in VisualEditor does not update fake references blocks inside templates', 'description': {'raw': \"When you add a new citation in VE, templates which wrap the `<references />` tag do not update to display it until the page is saved. Examples include [[https://en.wikipedia.org/wiki/Template:Reflist|`{{reflist}}`]] on the English Wikipedia and [[https://es.wikipedia.org/wiki/Plantilla:Listaref|`{{listaref}}`]] on the Spanish Wikipedia. This bug doesn't block any of the core citation workflows (creating, editing, and reusing) since those are accessed from the toolbar and the in-text reference numbers, but it's still very annoying. \\n\\nHowever, it remains unfixed because it's an //extraordinarily// hard technical challenge, verging on impossible given the current architecture of Mediawiki. No one has any idea what a workable solution would look like. Just to give one facet of the problem, you could implement this in VE right now //if// you completely re-parsed the entire page every time the user touched a template or a reference—which would be a //horrible// user experience and place //insane// loads on the servers. It's possible that in the future, someone will think up a brilliant solution that avoids all these huge issues, so this task remains open.\\n\\nIn the meantime, the planned solution is to update the `<references />` tag, which does update properly during editing, to support multiple columns and alternative list styles so they have all the functionality of these templates (T53260). When that task has been completed, communities will be able to replace the templates with references tags at whatever pace and with whatever tools they prefer (if there's demand for it, it would probably be possible to do a more immediate, bot-driven changeover).\\n\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-kve2ug5yc3dp6ighnmqk', 'dateClosed': 1518792292, 'spacePHID': None, 'dateCreated': 1372969200, 'dateModified': 1660398911, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50769', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Editing tool to changing case', 'description': {'raw': \"A user has requested a tool to alter the case of text that has been typed. Marking as lowest priority, since we've made clear it's not something anyone is likely to work on any time soon.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T55210}\\n{T52678}\\n{T55495}\\n{T52452}\"}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372943460, 'dateModified': 1651251693, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50745', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ./ inserted at the start of wikilinks when using Firefox 13 and 14, so we can unblacklist them', 'description': {'raw': \"Occasionally wiki links are being mangled adding ./ to the start and replacing spaces with underscores. For example replacing [[specific name (zoology)|specific epithet]] with [[./Specific_name_(zoology)|specific epithet]]. I've only noticed it with piped links.\\n\\nExamples\\n\\nhttps://en.wikipedia.org/w/index.php?title=Austropotamobius_pallipes&curid=3945333&diff=562783871&oldid=545518009\\nhttps://en.wikipedia.org/w/index.php?title=Ron_Davies_(songwriter)&curid=31118393&diff=562723238&oldid=553701771\\nhttps://en.wikipedia.org/w/index.php?title=Sibling_relationship&curid=22409572&diff=562636237&oldid=561958868\\nhttps://en.wikipedia.org/w/index.php?title=Double_Rainbow_(viral_video)&curid=28129724&diff=562626607&oldid=560477885\\nhttps://en.wikipedia.org/w/index.php?title=Roger_Mompesson&curid=39389398&diff=562625481&oldid=560045122 (also changed a category link)\\n\\npossibly related to bug 50428\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=50539\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48769\"}, 'authorPHID': 'PHID-USER-7hrs7wwclcldf7mm6a7o', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'dateClosed': 1464692505, 'spacePHID': None, 'dateCreated': 1372919760, 'dateModified': 1470077458, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50720', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'TemplateData: Get better error messages for JSON syntax errors', 'description': {'raw': 'Enhancement request for more informative error messages - as simple as \"Syntax error in JSON on line foo.\" would be better than the current message, which is just \"Syntax error in JSON.\"\\n\\n| {F34099979} | {F34099994}'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1372704060, 'dateModified': 1649500077, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50511', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Come up with a solution of section edit links' placement when they are floated right (due to a gadget)\", 'description': {'raw': 'Until a recent MediaWiki change the default behavior of edit section links was to float to the far side of the heading (right on LTR Wikis, assume this case in the following).\\n\\nThis was changed recently but almost all Wikis provide Gadgets to restore the old behavior (see http://en.wikipedia.org/wiki/MediaWiki:Gadget-righteditlinks.css or http://de.wikipedia.org/wiki/MediaWiki:Gadget-editsection-align-end.css for examples)\\n\\nThe problem is, that the VisualEditor\\'s fly-out-links reserve space to the right for the \"edit source\" link. Therefore when aligning the links right they actually appear with a large distance to the page-margin. The fly-outs should therefore be modified to not reserve any space so the \"edit\" link is correctly aligned right.\\n\\nTo prevent the fly-outs to shift the whole \"edit\" link left as soon as they become visible they could be changed to fly-out to the left in this case or to the bottom.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-v3yn5qf233ggnnnmvejc', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1663958347, 'spacePHID': None, 'dateCreated': 1372460880, 'dateModified': 1663958347, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50405', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Extend the rich TemplateData editor to be used inside VE', 'description': {'raw': 'It has been mentioned in some places[1][2] that the JSON syntax might be a problem for typical (non-technical) users, so I suggest creating a plugin for editing the content of the <templatedata> tags.\\n\\n[1] https://commons.wikimedia.org/wiki/Template_talk:Information#Adding_TemplateData_information\\n[2] https://pt.wikipedia.org/wiki/WP:Café_dos_programadores#Mais_uma_novidade:_TemplateData\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=51734'}, 'authorPHID': 'PHID-USER-sryrz6tgcfnnsiddx32p', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1483554630, 'spacePHID': None, 'dateCreated': 1372160580, 'dateModified': 1483554630, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50169', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[DO NOT USE] VisualEditor: Internet Explorer compatibility (tracking) [superseded by #VisualEditor × #Browser-Support-Internet-Explorer]', 'description': {'raw': 'A retread of bug 42847 for issues in the run-up to wider deployment.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1423674480, 'spacePHID': None, 'dateCreated': 1372053120, 'dateModified': 1488448078, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50085', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor by default for all users of all Wikimedia wikis', 'description': {'raw': \"One of our long-term objectives is for VisualEditor to be enabled by default on all (public) Wikimedia wikis; this is a tracker for that ambition.\\n\\nAs of August 2016, it isn't likely to be completed anytime soon, because some projects differ substantially from the Wikipedia use case for which VE has been primarily designed. For example, Wiktionary pages tend to be composed almost entirely of templates.\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '0', 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371860160, 'dateModified': 1681356623, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz50000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Enable VisualEditor by default for all users of all Wikipedias', 'description': {'raw': 'Current deployments listed at [[https://www.mediawiki.org/wiki/VisualEditor/Rollouts|mw:VisualEditor/Rollouts]].'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371860160, 'dateModified': 1715626643, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49999', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'OOUI: Dialogs should be repositionable/draggable', 'description': {'raw': '###Problem\\nThere are various workflows where a user wants to both interact with (or at least see) a page\\'s content, and also interact with a potentially complicated form/process, which may have many controls/inputs.\\n\\nSome VisualEditor examples:\\n - Adding/editing categories (T51969#548266)\\n - Adding/editing a template with many parameters\\nSome non-VE examples:\\n - Rater dialog (T51969#2847958)\\n - [[https://en.wikipedia.org/wiki/Wikipedia:Twinkle|Twinkle]] dialogs ([[https://github.com/azatoth/twinkle/issues/414]])\\n\\n###Feature request\\nDialogs that have no need to be modal (intended to interrupt the primary workflow, and requiring some action before you can get back to the primary workflow) should be draggable.\\nGadget/script/other developers using OOUI should have a simple way to enable this feature, e.g. a config setting that can be set to `true` to allow dragging.\\n\\nSome specific workflows may have viable alternatives to dialogs, e.g. {T52239}, but that doesn\\'t solve the general problem for more complicated dialog-based workflows.\\n\\n###Initial task description\\nQuoth requester: If I can\\'t read the article, because the \"page settings\" box is large and un-draggable and hides all the article, how can I see what defaultsort or categories I want to add (especially as for defaultsort I probably want to copy and paste all or part of the article title).\\n'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371833520, 'dateModified': 1708744818, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49969', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Transclusion dialogs panes should include a link to the template's definition page (for further documentation), even if there is TemplateData to document it\", 'description': {'raw': 'When in the template editing dialog, a link going to the [template:name] page, would be really helpful for:\\n* Reading detailed documentation\\n* Easy access to (edit or examine) template source code\\n\\n**See Also**:\\n* {T52354}\\n* {T52656}\\n* {T53311}'}, 'authorPHID': 'PHID-USER-hphmqcx66p6d6gvmjzp7', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1483459346, 'spacePHID': None, 'dateCreated': 1371589200, 'dateModified': 1484090818, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49772', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[DO NOT USE] VisualEditor: Performance issues (tracker) [superseded by #VisualEditor-Performance]', 'description': {'raw': 'This is more of a tracking bug than anything else, but it should be something people are aware of and something that\\'s formally logged; the VisualEditor is very slow on large articles, to the point where it causes confusing output.\\n\\nUsing the example of https://en.wikipedia.org/wiki/OpenOffice - I edited this and it took a good 20 seconds just to render \\'review changes\\', and another 20 to save. David Gerard did the same and the server popped up  \"Error saving data to server: timeout.\" with both \\'review\\' and \\'save\\'. Despite this, it saved anyway.\\n\\nObviously as a long-term thing: we shouldn\\'t have an editor so slow that someone in an industrialised, Western nation (i.e. the UK) can\\'t make things work.[1] As a short-term thing, we shouldn\\'t be informing users \"something has gone terribly, terribly wrong, abort!\" when it has actually saved.\\n\\n[1] It\\'s David Gerard, he\\'s not going to be using dial-up.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-j5ma2nageni56xp567v5', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417556322, 'spacePHID': None, 'dateCreated': 1371467880, 'dateModified': 1488448109, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49685', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Provide a get-me-into-the-wikitext-editor link on every header inside the VisualEditor', 'description': {'raw': 'From [[https://phabricator.wikimedia.org/T50429#518092|a comment]] on T50429.\\n\\n>It would be wonderful if the \"edit source\" links or icons for sections also showed up inside the Visual Editor. The Visual Editor could treat \"edit source\" links or icons as uneditable links. But the link would still work. So people could click \"edit source\" links or icons to open source editing of a section. \\n>\\n> People could go to source mode editing at anytime, even from inside the VisualEditor. That would be so convenient and so useful. Later on, this functionality could be extended to anything the VisualEditor can\\'t edit. People could click on templates, tables, etc. inside the VisualEditor and go directly to source mode editing of that section. Or they could right-click templates, tables, etc. to go to a new tab in source mode for that section.\\n\\n**See also:**\\nT50429\\nT51664\\nT49779'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1371430140, 'dateModified': 1489140945, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49665', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Switching to \"edit source\" tab within VE triggered via section-edit should be a wikitext section edit', 'description': {'raw': '[From bug 48429 comment 20.]\\n\\nSwitching to \"edit source\" tab when VE was triggered via a section-edit link should enter the wikitext editor for that section, rather than the entire page.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=48429\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49665'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372279963, 'spacePHID': None, 'dateCreated': 1371429960, 'dateModified': 1483620949, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz49664', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Links to new pages inside templates are coloured red in the content but not a dialog iframe', 'description': {'raw': 'These links being red at all come about because content of templates is rendered by the PHP parser, which sets class=\"new\" (Parsoid itself doesn\\'t hint about target colour yet). However, because dialogs are implemented as <iframe>s, we can\\'t inherit MW\\'s CSS for the body element, so they appear differently.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: minor'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1399324316, 'spacePHID': None, 'dateCreated': 1369932240, 'dateModified': 1417572394, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48984', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Implement a find/search and replace tool', 'description': {'raw': \"There's a search-and-replace tool in the wikiEditor which some users might miss and would like in VisualEditor somehow.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1417729605, 'spacePHID': None, 'dateCreated': 1368321420, 'dateModified': 1438734535, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48368', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: There is not enough UI difference between reading and editing mode', 'description': {'raw': \"The difference between editing and reading mode isn't obvious enough for the user.\\n\\n(reported at http://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/Alpha2013-04#Unterschied_Bearbeitungsfenster_und_gespeicherter_Artikel)\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1367512020, 'dateModified': 1643973278, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz48008', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor: Link inspector doesn't open in Opera\", 'description': {'raw': \"The link inspector doesn't open. Clicking the little button causes it to animate as if it was opening, then disappear completely.\\n\\nI'm investigating.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1372894482, 'spacePHID': None, 'dateCreated': 1367169780, 'dateModified': 1417573146, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47794', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve.ce.SurfaceObserver.prototype.stop() called without a subsequent call to ve.ce.SurfaceObserver.prototype.start()', 'description': {'raw': \"Something causes ve.ce.SurfaceObserver.prototype.stop() to be called without a subsequent call to ve.ce.SurfaceObserver.prototype.start().\\n\\nApparently happens after clicking on a link. I'm investigating.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375845262, 'spacePHID': None, 'dateCreated': 1367169660, 'dateModified': 1417573070, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47793', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: ve.ce.Surface.getSelectionRect() throws errors in Opera', 'description': {'raw': 've.ce.Surface.getSelectionRect() throws errors in Opera. I think this is the root cause of bug 37861 and likely various other issues.\\n\\nIt seems that rangySel.get{Start,End}DocumentPos consistently fails in Opera, because nativeRange.getClientRects() inside of the private createClientBoundaryPosGetter() function returns an empty collection. This causes the \"Cannot get position for range ...\" error to be thrown.\\n\\nI\\'m still investigating the why, I\\'m just putting this here. Changing getSelectionRect() to just always return some static value seems to work (or at least not fail miserably anymore).\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal'}, 'authorPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367595441, 'spacePHID': None, 'dateCreated': 1367065980, 'dateModified': 1417573291, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47772', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Provide basic source code editor features in VisualEditor SyntaxHighlight plugin', 'description': {'raw': '**Author:** `suitongbowgn`\\n\\n**Description:**\\nFeature request:\\n\\nA feature that supports insertion and simple editing of source code snippets in a general article. It may include a simple grammar checking mechanism which checks some fundamental grammatical errors such as having a { without closing it, having a () with a trailing period and nothing else, having solely a pair of brackets, etc.; an indentation correction tool which will perform indentation formatting on the codes; a beautify code tool which will reorganize code formatting, including indentation to make the code more reader-friendly in format.\\n\\n\\nFeatures:\\n* Insert or edit a code block.\\n* Basic IDE features (perhaps re-use WikiEditor/CodeEditor)\\n * Syntax validation (matching quotes/parenthesis/braces etc.)\\n * Follow indentation level when breaking lines.\\n * Live grammar highlighting.'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '1', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1445531108, 'spacePHID': None, 'dateCreated': 1366998060, 'dateModified': 1660398911, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47742', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Automatically propose/suggest a category for images', 'description': {'raw': 'Let\\'s crush the [categorisation backlog](https://commons.wikimedia.org/wiki/User:Multichill/Categorization_stats) once and for all!\\n\\nsome categorization could be automated already.\\n\\nSearching for pictures based on meta-data is called \"Concept Based Image Retrieval\", searching based on the machine vision recognized content of the image is called \"Content Based Image Retrieval\".\\n\\nWhat I understood of Lars\\' request, is an automated way of finding the \"superfluous\" concepts or meta-data for pictures based on their content. Of course recognizing an images content is very hard (and subjective), but I think it would be possible for many of these \"superfluous\" categories, such as \"winter landscape\", \"summer beach\" and perhaps also \"red flowers\" and \"bicycle\".\\n\\nThere exist today many open source \"Content Based Image Retrieval\" systems, that I understand basically works in the way that you give them a picture, and they find you the \"matching\" pictures accompanied with a score. Now suppose we show a picture with known content (pictures from Commons with good meta-data), then we could to a degree of trust find pictures with overlapping categories. I am not sure whether this kind of automated reverse meta-data labelling should be done for only one category per time, or if some kind of \"category bundles\" work better. Probably adjectives and items should be compounded (eg \"red flowers\").\\n\\nRelevant articles and links from Wikipedia:\\n\\n  # [w:Image_retrieval](https://en.wikipedia.org/wiki/Image_retrieval)\\n  # [w:Content-based_image_retrieval](https://en.wikipedia.org/wiki/Content-based_image_retrieval)\\n  # [w:List_of_CBIR_engines#CBIR_research_projects.2Fdemos.2Fopen_source_projects](https://en.wikipedia.org/wiki/List_of_CBIR_engines#CBIR_research_projects.2Fdemos.2Fopen_source_projects)\\n\\n Some demo links bawolff found:\\n\\n\\n  # [http://demo-itec.uni-klu.ac.at/liredemo/](http://demo-itec.uni-klu.ac.at/liredemo/ ) (Lire might even be integrated with CirrusSearch because it\\'s based on Lucene)\\n  # [http://image.mdx.ac.uk/time/demo.php](http://image.mdx.ac.uk/time/demo.php)\\n  # [http://mi-file.isti.cnr.it:8765/CophirSearch/](http://mi-file.isti.cnr.it:8765/CophirSearch/)\\n  # [http://orpheus.ee.duth.gr/anaktisi/](http://orpheus.ee.duth.gr/anaktisi/) (not free)\\n  # [https://youtube.com/2eaGwk4Xhks](https://youtube.com/2eaGwk4Xhks)\\n\\n\\n  - Skills: image recognition/analysis, possibly Natural language processing; language depending on implementation, e.g. python for a [PWB tool](https://www.mediawiki.org/wiki/Manual:Pywikibot), JavaScript and PHP for a MediaWiki extension, JavaScript for a [tool](https://www.mediawiki.org/wiki/Tool_Labs) similar to the [Wikidata Game](http://magnusmanske.de/wordpress/?p=203).\\n  - Possible mentors: Kristian Kankainen (Keeleleek); WereSpielChequers?\\n  - Additional info: \"I like the idea of automating categorisation, but I think we are a long way from being able to do much of it. So this would be a big longterm project. One of my concerns is that we are a global site, and we are trying to collect the most diverse set of images that anyone has ever assembled. Image recognition is a good way of saying that we now have another twenty images of this person, but it could be confused when we get our first images of one of the fox subspecies that we don\\'t yet have a picture of. Or rather it would struggle to differentiate the rare and the unique from their more common cousins. There are also some spooky implications for privacy re image recognition and our pictures of people, aside from the obvious things like identifying demonstrators in a crowd or linking a series of shots of one person in such a way as to identify that this photograph of a face belongs to the same person as this photo of pubic hair because the hand is identical; We have had some dodgy things happening on Wikipedia with people wanting to categorise people ethnically and I worry that someone might use a tool such as this to try and semi accurately categorise people as say Jewish. Another major route for improved categorisation is geodata, and I think this could be a less contentious route. Not that everything has geodata, but if things have it could be a neat way to categorise a lot of images, especially if we can get boundary data so we can categorise images as being shot from within a set of boundaries rather than centroid data with all its problems that the parts of one place maybe closer to the centre of an adjacent place than the centre of the area they belong to. WereSpielChequers (talk) 09:58, 20 June 2014 (UTC)\"\\n\\n----\\nProposed in #community-wishlist-survey-2016. Received 33 support votes, and ranked #45 out of 265 proposals. [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Commons#CW2016-R045 | View complete proposal with discussion and votes here. ]]'}, 'authorPHID': 'PHID-USER-azy72hrp3tpetr52aob6', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1366602900, 'dateModified': 1531771716, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz47492', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Jenkins: Set up job in gate-and-submit to avoid submitting \"DRAFT\" or \"WIP\" commits', 'description': {'raw': 'The job will vote -1. But only in gate-and-submit, when working on it the tests should pass (or have this one be non-voting).\\n\\n--------------------------\\n**Version**: wmf-deployment\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-sai77mtxmpqnm6pycyvz', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-orzyp3dswemhdgdznro5', 'dateClosed': 1490610800, 'spacePHID': None, 'dateCreated': 1365022920, 'dateModified': 1490610800, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46860', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Plugin editors to be created (tracking)', 'description': {'raw': \"This is a tracking bug for the creation of VisualEditor plugin editors, for each of which the primary bug should live in that product/component instead (where they're about an existing Extension etc.).\\n\\nThis task has been replaced by #VisualEditor-MediaWiki-Plugins\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '0', 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1422424777, 'spacePHID': None, 'dateCreated': 1364926560, 'dateModified': 1552745435, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz46803', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'no language links shown in edit mode', 'description': {'raw': 'When you are editing an article the language links from Wikidata are not shown in the sidebar. Local links are shown.\\n\\n(Reported at https://en.wikipedia.org/wiki/Wikipedia_talk:Wikidata/Archive_1#No_interwiki_links_when_you_are_in_edit_mode%3F)\\n\\n**See Also**:\\n{T48488}\\n{T63768}'}, 'authorPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'ownerPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-7n5fvppwj4ueprv2iuys', 'dateClosed': 1644158450, 'spacePHID': None, 'dateCreated': 1362396060, 'dateModified': 1644158450, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45687', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a \"zen mode\"/\"Distraction free mode\" MediaWiki extension', 'description': {'raw': 'Perhaps might be nice in MediaWiki core, but would definitely be nice as at least a MediaWiki extension, we should implement a \"zen mode\" capability from ?action=edit.\\n\\nGitHub and it seems like the Cloud9 IDE both have this mode. It\\'s demonstrated here: <https://docs.c9.io/zen_mode.html>.\\n\\nIn short, in the case of GitHub, it appears to be a bit of JavaScript that adds a \"zen mode\" button to the UI. When the user clicks this button, the non-essential page elements are hidden from the page, allowing the user to focus on the textarea (or other central input area) alone. Basically it reduces the amount of noise on the page in order to increase the signal.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\nhttps://bugzilla.wikimedia.org/show_bug.cgi?id=14501'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1361595420, 'dateModified': 1733641676, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz45300', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Port MW core changes back to 1.19.x, 1.20.x and 1.21.x series so VE can run on them', 'description': {'raw': '**Author:** `Coiby.Xu`\\n\\n**Description:**\\nI try a clean install of MW 1.20.2 and also install VE and Parsoid extension. When click \"VisualEditor\" button, the VE doesn\\'t appear and there\\'s a js error: \"Uncaught TypeError: Cannot read property \\'error\\' of null\".\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ynivjflmc2dcl6w5ut5v', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1404436245, 'spacePHID': None, 'dateCreated': 1357988100, 'dateModified': 1417572123, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43898', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Create a VisualEditor plugin tool to add/edit Hieroglyphics blocks', 'description': {'raw': '<hiero>....</hiero> is unparsed but shown as plain wikitext:\\nhttps://en.wikipedia.org/wiki/User:Raymond/hiero\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**URL**: https://en.wikipedia.org/wiki/User:Raymond/hiero'}, 'authorPHID': 'PHID-USER-3uecblbxq24ycewm2cog', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1355479200, 'dateModified': 1643973281, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz43118', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Setup wikibugs and gerrit-wm for #mediawiki-visualeditor', 'description': {'raw': 'Puppet config for wikibugs:\\n\\nhttps://gerrit.wikimedia.org/r/gitweb?p=operations/puppet.git;a=blob;f=manifests/misc/wikibugs.pp\\n\\nPuppet config for gerrit-wm:\\n\\nhttps://gerrit.wikimedia.org/r/gitweb?p=operations/puppet.git;a=blob;f=manifests/gerrit.pp\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1398113038, 'spacePHID': None, 'dateCreated': 1354738560, 'dateModified': 1398113588, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42735', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Two replacements within the same transaction and the same paragraph cause change markers to be off', 'description': {'raw': \"Test case:\\n\\n+                       'removing then inserting a character': {\\n+                               'calls': [\\n+                                       ['pushRetain', 41],\\n+                                       ['pushReplace', ['i'], []],\\n+                                       ['pushReplace', [], ['j']]\\n+                               ],\\n+                               'expected': function ( data ) {\\n+                                       data[41] = 'j';\\n+                                       ve.setProp( data[37], 'internal', 'changed', 'content', 2 );\\n+                               }\\n                        }\\n\\nThis sets the second change marker on data[36]. This happens because the start offsets handled in TransactionProcessor.replace are translated using this.adjustment , but that glosses over the fact that not all adjustments captured in this.adjustment actually apply if the offset is before the cursor. Instead, we need some sort of offset translation. I tried using ve.dm.Transaction.translateOffset() but that doesn't seem to work out of the box very well.\\n\\nI guess theoretically this might also be an issue with other uses of .start attributes in the replacement processor, but it hasn't led to issues so far.\\n\\nLow prio because we currently don't generate transactions that trigger this case.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: major\"}, 'authorPHID': 'PHID-USER-fovtl67ew4l4cc3oeypc', 'ownerPHID': 'PHID-USER-it53o2f2kyryqyj33uzt', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1360975473, 'spacePHID': None, 'dateCreated': 1353134520, 'dateModified': 1417573346, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz42222', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'LQT should intercept \"section=new\" edits through API as well as skin interface', 'description': {'raw': \"To quote Roan:\\n\\n| LQT hijacks section=new via the PerformAction hook, but it doesn't make\\n| any attempt to hijack section=new in the API. Instead, LQT has its own\\n| API for posting things\\n\\nThis leads to tools that use the edit API (such as the Feedback tool) being incompatible with LQT.\\n\\n--------------------------\\n**Version**: master\\n**Severity**: normal\\n**See Also**:\\n* {T54729}\\n* {T35260}\\n* {T59989}\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1350927300, 'dateModified': 1470643799, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41276', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Support Firefox 10-14', 'description': {'raw': 'More or less related to bug 41147 (T43147). Iceweasel team may consider Mozilla\\'s ESR version in their forking work. However that bug was turned into talk about Firefox forks, so I start a new bug here.\\n\\nFirefox is said to have an \"Extended Support Release\"[1] which is recommended to be used \"by enterprises, public institutions, universities and other organizations that centrally manage their Firefox deployments\"[2] by Mozilla. We may want to support that version too (just an older Firefox with security bugs fixed AFAIS).\\n\\n[1] http://en.wikipedia.org/wiki/History_of_Firefox#Extended_Support_Release\\n[2] http://blog.mozilla.org/blog/2012/01/10/delivering-a-mozilla-firefox-extended-support-release/\\n'}, 'authorPHID': 'PHID-USER-zjzhrhmn36icnzbckqy4', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-bf7nnwcm4i6wicvxtb77', 'dateClosed': 1616112511, 'spacePHID': None, 'dateCreated': 1350761460, 'dateModified': 1644737571, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41245', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Display \"Mobile Platform\" custom field only for relevant products/components', 'description': {'raw': 'I am after removing a bit of clutter from show_bug.cgi.\\n\\nMobile team prefers to keep Mobile Platform separate from Platform:\\n\"we don\\'t want *any* desktop os in the platform, they\\'re useless to us. it\\'ll be pure noise to have the desktop os list.\"\\n\\nHence we should show the \"Mobile Platform\" custom field only for products \"Wikipedia App\"/\"Wiktionary App\"/\"WikiLoves Monuments Mobile\" and for component \"MobileFrontend\".\\nThis requires Bugzilla 4.2 as per https://bugzilla.mozilla.org/show_bug.cgi?id=479400 .\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1416786013, 'spacePHID': None, 'dateCreated': 1350610560, 'dateModified': 1416786013, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41197', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Add unsubscribe links to email notifications', 'description': {'raw': 'Please add \"unsubscribe\" links to these:\\n\\n\\n>>>>> \"MM\" == MediaWiki Mail <wiki@wikimedia.org> writes:\\nMM> Hi Jidanni,\\n\\nMM> this is a notification from MediaWiki that a new thread on Talk:Download from Git, \\'Update error\\',\\nMM> was created on 14 October 2012 at 03:30 by Lukas9950\\n\\nMM> You can see it at <http://www.mediawiki.org/w/index.php?title=Talk:Download_from_Git&offset=20121013193053&lqt_mustshow=19695#Update_error_19695>\\n\\nMM> The text is:\\nMM> When I want to update all extensions, I get an error.\\n\\nMM> sh-4.1$ git submodule update --init\\nMM> fatal: reference is not a tree: 655d019b84689e37b3fb1018600f629c657fb575\\nMM> Unable to checkout \\'655d019b84689e37b3fb1018600f629c657fb575\\' in submodule path \\'Persona\\'\\nMM> sh-4.1$\\n\\nMM> Anyone can help me with this?\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-awbqewknju4hbrnah6pm', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1402005852, 'spacePHID': None, 'dateCreated': 1350158820, 'dateModified': 1402005852, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz41012', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': '[DO NOT USE] Support tables (tracking) [superseded by #VisualEditor-Tables]', 'description': {'raw': 'This was a tracking bug when tasks were managed in Bugzilla. It has been replaced by the #VisualEditor-Tables project.'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'dateClosed': 1416795729, 'spacePHID': None, 'dateCreated': 1345761660, 'dateModified': 1469824075, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz39596', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Automatically use \"smart quotes\" and convert other typing to more advance characters (as an option)', 'description': {'raw': 'From user suggestion, along the lines of how Microsoft Word works.\\n\\nThis would involve a number of language-specific substitutions (and probably some shared ones); for English, I believe it would at least involve:\\n\\n* If a user types the character string \\'foo \"bar\\', on the pressing of the \\'b\\' it would convert the \\'\"\\' character to a an &ldquo;.\\n* If a user types the \\'\"\\' character whilst in a string that has an &ldquo; in it earlier, convert the character to an &rdquo;.\\n* If a user types in \\' - \\', on the pressing of the space character after the hyphen, covert the hyphen to an &endash;.\\n* If a user types in \\' -- \\', on the pressing of the space character after the second hyphen, covert the two hyphens into one &emdash;.\\n\\nWorth considering as a nice to have; this would probably want to be both site-configurable (is it available at all; if yes, is it default-on), and user-configurable.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1343329080, 'dateModified': 1643973283, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38724', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Character inserter should re-use the code/config from WikiEditor somehow', 'description': {'raw': 'Inserting symbols, accented characters, and characters from other writing systems is a common task in encyclopedia-building.\\n\\nVisualEditor needs to provide this as much as WikiEditor does; preferably they should use the same configuration and avoid duplicating code or config if possible.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1387220701, 'spacePHID': None, 'dateCreated': 1340903580, 'dateModified': 1417573269, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz38029', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Review and deploy Drafts extension to Wikimedia wikis', 'description': {'raw': 'There is an eminently and patently useful extension called \"Drafts\" that was written a few years ago: <https://www.mediawiki.org/wiki/Extension:Drafts>.\\n\\nThis project kind of stagnated and/or died, I believe. I\\'d like to see it revived. This bug is about doing whatever is necessary to have this extension deployed to Wikimedia wikis.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\\n**See Also**:\\n{T57370}\\n{T75241}'}, 'authorPHID': 'PHID-USER-hyfm4swq76s4j642w46x', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'feature', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1340821500, 'dateModified': 1729681457, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37992', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Upload-by-insertion of images via copy-paste', 'description': {'raw': \"[Suggestion from community.]\\n\\nCopy-pasting in an image to the editor should automatically upload it to the wiki and insert it into the article.\\n\\nAfter/on insertion (but before saving) the editor should be prompted to add meta-data (e.g. name, licence, source, ...).\\n\\nI'd imagine we'd be less likely to accept this for Wikimedia wikis, but others (Wikia?) might be interested.\\n\\n**See Also**: {T23557}\"}, 'authorPHID': 'PHID-USER-ydswvwhh5pm4lshahjje', 'ownerPHID': 'PHID-USER-c5xwrfdyp3dckkh2nkoj', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': '8', 'subtype': 'default', 'closerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'dateClosed': 1540863713, 'spacePHID': None, 'dateCreated': 1340644620, 'dateModified': 1541696185, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37932', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor on Opera 12: editing existing link doesn't work, breaks selection logic\", 'description': {'raw': \"Testing in Opera 12 on Mac\\n\\nSteps:\\n* open https://www.mediawiki.org/wiki/VisualEditor:Welcome\\n* hit 'edit'\\n* select a link\\n* hit link button\\n\\nExpected behavior:\\n* link dialog pops up, lets you change the link\\n\\nActual behavior:\\n* nothing... usually\\n* sometimes - nothing, followed by the next attempt opening a link dialog at your first selection\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375118502, 'spacePHID': None, 'dateCreated': 1340419620, 'dateModified': 1417573271, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37861', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor on Opera 12: clicking selection arrow shows, then hides popup bar', 'description': {'raw': \"Testing in Opera 12 on Mac\\n\\nAfter making a selection, the little arrow shows up which you can click for a popup formatting bar. In Opera, the bar pops up then immediately hides itself, so can't be used.\\n\\nThis also kills the selection.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-pun3sjvg3cemjzbgyo2t', 'status': {'value': 'invalid', 'name': 'Invalid', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1367028832, 'spacePHID': None, 'dateCreated': 1340418600, 'dateModified': 1417573296, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37858', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"VisualEditor on Opera 12: selecting text with mouse 'backwards' fails\", 'description': {'raw': \"Selecting text from end to beginning with the mouse in Opera 12 doesn't work properly; the selection keeps resetting itself, so you end up with no selection.\\n\\nSelecting end to start via keyboard (shift+arrow keys) works as expected.\\n\\nSelecting from start to end works as expected.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: normal\"}, 'authorPHID': 'PHID-USER-yek7ymogrv4qc67oilhf', 'ownerPHID': 'PHID-USER-s7sn3zjthnxvep34c5ho', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1355350453, 'spacePHID': None, 'dateCreated': 1340418480, 'dateModified': 1417573353, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz37856', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'VisualEditor: Does not work in Opera (tracking)', 'description': {'raw': 'The VisualEditor does not display when using Opera. The header \"Visual editor sandbox\" is the only thing displayed.\\n\\n--------------------------\\n**Version**: unspecified\\n**Severity**: enhancement'}, 'authorPHID': 'PHID-USER-um3fhlwaza6ecwf67t77', 'ownerPHID': 'PHID-USER-wkpnidxoctuhawexig5p', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': 1375126546, 'spacePHID': None, 'dateCreated': 1334532780, 'dateModified': 1552744913, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz36000', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': None, 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Implement minification for SVG files in ResourceLoader', 'description': {'raw': 'This task is about implementing a high performance minifier for SVG content. It will also track the use of that minifier when embedding SVG files in file modules through CSSMin. \\n\\n**See Also**:\\n* {T175318}\\n* {T61086}\\n\\nTask T61086 tracks the use of this minifier (once implemented) by ResourceLoaderImage for SVGs served from that endpoint.\\n\\n--------------------------\\n\\n>>! **Original report**:\\n> \\n> \\n> This comes from bug 34810 (T36810)... Which could use this feature to dynamically do it (or the simpler older method of creating .min files)\\n> \\n> SVG are used as non page content files, they contain a lot of whitespace. Minify and serve!\\n> \\n\\n'}, 'authorPHID': 'PHID-USER-6vzzsmi22zem6yttr6vp', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1330547040, 'dateModified': 1692623210, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'bz34812', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Polish : Editing tools (VisualEditor and WTE) should display to user when server connection has been lost', 'description': {'raw': 'This will reduce instances where user submits changes and receives an error, possibly resulting in data loss. \\nsee — http://github.hubspot.com/offline/'}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'open', 'name': 'Open', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': None, 'dateClosed': None, 'spacePHID': None, 'dateCreated': 1415513322, 'dateModified': 1678106749, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Consolidate the many tech events calendars in Phabricator's calendar\", 'description': {'raw': 'We have three problems related to calendars that need to be resolved, which are related but perhaps may be fixed separately, even at different points in time:\\n\\n* **Introducing calendar data**. Now we are doing this in 1001 places. Ideally it would be just one place. The assumption of this task is that the one place would be Phabricator\\'s calendar ([[ https://secure.phabricator.com/T7924 | today a prototype ]]), but other candidates should be considered.\\n* **Pulling calendar data in other supports, mainly wiki pages**. While we could start linking from wiki pages to Phabricator calendar queries, the desired scenario would be a way for editors to embed calendars based on queries in wiki pages. This probably implies a Calendar API to query data ([[ https://secure.phabricator.com/T7944 | which is missing ]]) and a MediaWiki extension allowing to embed those queried calendars in wiki pages (which we don\\'t have). Maybe this is just too much, and at least the tech-inclined Wikimedians would be fine clicking a Phabricator link.\\n* **Integrating calendar data with other systems (mainly Google Calendar)**. \"[[ https://secure.phabricator.com/T7929 | Future work ]]\" upstream, no plans today.\\n\\nAs we can see, deciding on Phabricator Calendar as the one place to introduce data would not provide a quick path to use that data out of Phabricator. However, what would be the alternatives? Other than defaulting to Google Calendar (which I think would be wrong as a matter of Wikimedia principles), I don\\'t see a shortcut but others may have better ideas.\\n\\n== Phabricator Calendar in a nutshell ==\\n\\nAfter playing a bit with https://phabricator.wikimedia.org/calendar/, I think the most practical option is to focus on having that calendar up to date, and then link to it from the right places in mediawiki.org.\\n\\n* Entering events is simpler. The usual you can expect in a calendar application. There is no need to archive past events, since this is done automatically.\\n* Users can RSVP, getting notifications about the event and letting others know that they are attending.\\n* The calendars shown are the result of queries allowing for multiple parameters, including month view vs list, show only upcoming events, etc. These queries have static URLs.\\n* Events can be assigned to projects, which means that\\n** We could have projects for i.e. Tech Talks, Technical Office Hours, etc, people could subscribe to these projects and receive notifications when a new event is filed.\\n** By adding an event to existing related projects (i.e. #Web-APIs-hub, #Google-Summer-of-Code-2015), users following that project would receive notifications as well.\\n** Queries can be fine tuned to show a specific set of events.\\n\\nIf we agree on this, the implementation would be relatively simple, since (at least in Wikimedia tech) a few people create most of the events. Redirecting from the current calendar pages to their equivalent Phabricator calendar queries should be enough to tell current users about these calendars about the new way to create new events.\\n\\n=== Basic review of existing MediaWiki extensions ===\\n\\nI went through https://www.mediawiki.org/wiki/Extension:Calendar (a linkhub for the ~12 different extensions or methods of integrating calendars with MediaWiki). There was no extension surviving a basic check against our needs. In fact, most of them are more than abandoned, and in general they focus on presentation, not on easy input, even less on semantic data (except the SemanticMediaWiki one, perhaps). [[ https://www.mediawiki.org/wiki/Extension:SimpleCalendar | SimpleCalendar ]] looks like the only candidate if we would ever want to start from this point.\\n\\nThe reason for a lack of a proper MediaWiki Calendar extension may well be that MediaWiki was not designed to input calendar data, subscribe to events, etc.\\n\\nAfter this short investigation, I still think that it is better to start from something other than MediaWiki, and the main candidate keeps being Phabricator. Then work separately in a way to import Phabricator Calendar data and present it in MediaWiki pages.\\n\\n=== Background / previous description ===\\n\\nhttps://www.mediawiki.org/wiki/Project:Calendar has a lot of room for improvement. Creating tasks is not trivial, and although the calendar can be watched and the entries appear in the mediawiki.org homepage, it doesn\\'t have any of the features expected nowadays in an online calendar, i.e. integration with the calendar apps people use to organize their lives.\\n\\nAlso, for some low hanging fruit, a reporter explains in an email:\\n> the whole project:calendar page hierarchy is confusing - I would avoid subpages at more than one level deep\\n> It\\'s not clear to me why this page is in the Project: namespace to begin with\\n> https://www.mediawiki.org/wiki/Project:Namespaces seems to suggest the Project: namespace is for \"organization of mediawiki.org\", which does not describe this page\\n> see https://meta.wikimedia.org/wiki/Tech for a better way to provide consistent navigation/page structure across a set of dispersed pages without use of subpages you asked :)'}, 'authorPHID': 'PHID-USER-lluzkul4z7us4sxkayss', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1563466400, 'spacePHID': None, 'dateCreated': 1415025314, 'dateModified': 1611614207, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'attributes in a task should be modifiable in-line rather than having to go to an edit mode', 'description': {'raw': \"actions such as adding projects or tags, adding cc's or assigning owner, changing security should be more easily added, removed or modified. \"}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': 'PHID-USER-fn7qnpccfbitivgtw2rt', 'status': {'value': 'resolved', 'name': 'Resolved', 'color': 'green'}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-fn7qnpccfbitivgtw2rt', 'dateClosed': 1463618910, 'spacePHID': None, 'dateCreated': 1414186408, 'dateModified': 1464026775, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': 'Shortcut keys for description fields text formatting are needed. ', 'description': {'raw': 'Allow shortcut keys for text formatting and action in description fields like CMD+B, CMD+K, CMD+I, etc. '}, 'authorPHID': 'PHID-USER-z3kqk2bjnqneldcznht6', 'ownerPHID': None, 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'dateClosed': 1562205607, 'spacePHID': None, 'dateCreated': 1414018531, 'dateModified': 1562205607, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': None, 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n",
+      "{'name': \"Phabricator uses Yet Another Markup System and we'd really like to switch it to something else if possible\", 'description': {'raw': 'The [[https://secure.phabricator.com/book/phabricator/article/remarkup/|ReMarkup]] system is not wikitext and not Markdown. Sad.'}, 'authorPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'ownerPHID': 'PHID-USER-hgn5uw2jafgjgfvxibhh', 'status': {'value': 'declined', 'name': 'Declined', 'color': None}, 'priority': {'value': 10, 'name': 'Lowest', 'color': 'sky'}, 'points': None, 'subtype': 'default', 'closerPHID': 'PHID-USER-nyhmztvvw4luz5mlcuvg', 'dateClosed': 1410485106, 'spacePHID': None, 'dateCreated': 1397576333, 'dateModified': 1702504253, 'policy': {'view': 'public', 'interact': 'public', 'edit': 'users'}, 'custom.deadline.due': None, 'custom.train.status': None, 'custom.train.backup': None, 'custom.external_reference': 'fl100', 'custom.release.version': None, 'custom.release.date': None, 'custom.security_topic': 'default', 'custom.risk.summary': None, 'custom.risk.impacted': None, 'custom.risk.rating': None, 'custom.requestor.affiliation': None, 'custom.error.reqid': None, 'custom.error.stack': None, 'custom.error.url': None, 'custom.error.id': None, 'custom.points.final': None, 'custom.deadline.start': None}\n"
      ]
     }
    ],
    "source": [
     "for project in data:\n",
-    "    print(project['phid'])\n",
+    "    print(project['fields'])\n",
     "    for key,value in project['task_comments'].items():\n",
     "        if value != []:\n",
     "            for subcomment in project['task_comments'][key]:\n",
@@ -4648,20 +4648,35 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 4,
+   "execution_count": 9,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "#loading in the master list of \n",
+    "import pandas as pd\n",
+    "roster_path = \"/home/SOC.NORTHWESTERN.EDU/nws8519/git/mw-convo-collections/src/helper_scripts/cleaning_scripts/022825_wmf_master_phab_roster.json\"\n",
+    "with open(roster_path, 'r') as file:\n",
+    "    roster_data = json.load(file)\n",
+    "roster_df = pd.DataFrame(roster_data)\n",
+    "wmf_phids = roster_df['phid'].tolist()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
    "metadata": {},
    "outputs": [],
    "source": [
     "def generate_csv(data, output_file):\n",
     "    \"\"\"\n",
-    "    Generate a CSV file with four columns: comment_text, date_created, AuthorPHID, and comment_type.\n",
+    "    Generate a CSV file with four columns: comment_text, date_created, AuthorPHID, TaskPHID, comment_type, status.\n",
     "    \n",
     "    Args:\n",
     "    data (list): The list of project data.\n",
     "    output_file (str): The path to the output CSV file.\n",
     "    \"\"\"\n",
     "    with open(output_file, 'w', newline='') as csvfile:\n",
-    "        fieldnames = ['comment_text', 'date_created', 'AuthorPHID', 'TaskPHID', 'comment_type']\n",
+    "        fieldnames = ['task_title', 'comment_text', 'date_created', 'AuthorPHID', 'WMFaffil', 'TaskPHID', 'comment_type', 'status']\n",
     "        writer = csv.DictWriter(csvfile, fieldnames=fieldnames)\n",
     "        \n",
     "        writer.writeheader()\n",
@@ -4669,11 +4684,14 @@
     "        for project in data:\n",
     "            # Add project description as a comment\n",
     "            writer.writerow({\n",
+    "                'task_title': project['fields']['name'],\n",
     "                'comment_text': project['fields']['description']['raw'],\n",
     "                'date_created': project['fields']['dateCreated'],\n",
     "                'AuthorPHID': project['fields']['authorPHID'],\n",
+    "                'WMFaffil': project['fields']['authorPHID'] in wmf_phids,\n",
     "                'TaskPHID' : project['phid'],\n",
-    "                'comment_type': 'description'\n",
+    "                'comment_type': 'task_description',\n",
+    "                'status': project['fields']['status']['value']\n",
     "            })\n",
     "            \n",
     "            # Add task comments\n",
@@ -4681,21 +4699,24 @@
     "                if value:\n",
     "                    for subcomment in value:\n",
     "                        writer.writerow({\n",
+    "                            'task_title': project['fields']['name'],\n",
     "                            'comment_text': subcomment['content']['raw'],\n",
     "                            'date_created': subcomment['dateCreated'],\n",
     "                            'AuthorPHID': subcomment['authorPHID'],\n",
+    "                            'WMFaffil': project['fields']['authorPHID'] in wmf_phids,\n",
     "                            'TaskPHID' : project['phid'],\n",
-    "                            'comment_type': 'task_subcomment'\n",
+    "                            'comment_type': 'task_subcomment',\n",
+    "                            'status': 'NA'\n",
     "                        })"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 5,
+   "execution_count": null,
    "metadata": {},
    "outputs": [],
    "source": [
-    "generate_csv(data, \"0209_ve_phab_comments.csv\")"
+    "generate_csv(data, \"0228_ve_phab_comments.csv\")"
    ]
   }
  ],
diff --git a/src/helper_scripts/cleaning_scripts/cleaning_rfcs.ipynb b/src/helper_scripts/cleaning_scripts/cleaning_rfcs.ipynb
new file mode 100644
index 0000000..457e256
--- /dev/null
+++ b/src/helper_scripts/cleaning_scripts/cleaning_rfcs.ipynb
@@ -0,0 +1,452 @@
+{
+ "cells": [
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import json\n",
+    "import csv\n",
+    "import pandas as pd"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "def recursive_comment_parsing(dict_array, subcomment):\n",
+    "    # Append the current comment details to the dict_array\n",
+    "    dict_array.append({\n",
+    "        'comment_text': subcomment.get('text_blocks', ''),\n",
+    "        'date_created': subcomment.get('time_stamp', ''),\n",
+    "        'Author': subcomment.get('author', '')\n",
+    "    })\n",
+    "    \n",
+    "    # Process nested comments recursively\n",
+    "    if 'comments' in subcomment and subcomment['comments']:\n",
+    "        for nested_comment in subcomment['comments']:\n",
+    "            recursive_comment_parsing(dict_array, nested_comment)\n",
+    "    \n",
+    "    return dict_array"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "def generate_csv(data):\n",
+    "      comments = []\n",
+    "      for subsection in data:\n",
+    "            if subsection['comments'] != []:\n",
+    "                  for subcomment in subsection['comments']:\n",
+    "                        comments = recursive_comment_parsing(comments, subcomment)\n",
+    "      df = pd.DataFrame(comments)\n",
+    "      return df"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "fp =\"/data/users/mgaughan/mw-repo-lifecycles/discussion_data/visualeditor/ve-feedback-2011-12.json\"\n",
+    "with open(fp, 'r') as file:\n",
+    "        data = json.load(file)\n",
+    "data = data['sections']\n",
+    "test_df = generate_csv(data)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/html": [
+       "<div>\n",
+       "<style scoped>\n",
+       "    .dataframe tbody tr th:only-of-type {\n",
+       "        vertical-align: middle;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe tbody tr th {\n",
+       "        vertical-align: top;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe thead th {\n",
+       "        text-align: right;\n",
+       "    }\n",
+       "</style>\n",
+       "<table border=\"1\" class=\"dataframe\">\n",
+       "  <thead>\n",
+       "    <tr style=\"text-align: right;\">\n",
+       "      <th></th>\n",
+       "      <th>comment_text</th>\n",
+       "      <th>date_created</th>\n",
+       "      <th>Author</th>\n",
+       "    </tr>\n",
+       "  </thead>\n",
+       "  <tbody>\n",
+       "    <tr>\n",
+       "      <th>0</th>\n",
+       "      <td>[{{talkarchive}}\\n, \\n]</td>\n",
+       "      <td></td>\n",
+       "      <td></td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>1</th>\n",
+       "      <td>[== Link editing should work when cursor is on...</td>\n",
+       "      <td>20:38, 13 December 2011 (UTC)</td>\n",
+       "      <td>Dantman</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>2</th>\n",
+       "      <td>[\\n, :Yes, the little down-arrow with B/F/Link...</td>\n",
+       "      <td>22:16, 13 December 2011 (UTC)</td>\n",
+       "      <td>JakobVoss</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>3</th>\n",
+       "      <td>[\\n]</td>\n",
+       "      <td></td>\n",
+       "      <td></td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>4</th>\n",
+       "      <td>[== Collapse same text links ==\\n, \\n, &lt;small&gt;...</td>\n",
+       "      <td>20:43, 13 December 2011 (UTC)</td>\n",
+       "      <td>Dantman</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>...</th>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>429</th>\n",
+       "      <td>[\\n]</td>\n",
+       "      <td></td>\n",
+       "      <td></td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>430</th>\n",
+       "      <td>[== User Interface ==\\n, \\n, &lt;small&gt;User agent...</td>\n",
+       "      <td>12:02, 30 December 2011 (UTC)</td>\n",
+       "      <td>TJRana</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>431</th>\n",
+       "      <td>[\\n]</td>\n",
+       "      <td></td>\n",
+       "      <td></td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>432</th>\n",
+       "      <td>[== Feedback by users that see no feedback lin...</td>\n",
+       "      <td></td>\n",
+       "      <td></td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>433</th>\n",
+       "      <td>[== Usability ==\\n, \\n, It's great that you're...</td>\n",
+       "      <td></td>\n",
+       "      <td></td>\n",
+       "    </tr>\n",
+       "  </tbody>\n",
+       "</table>\n",
+       "<p>434 rows × 3 columns</p>\n",
+       "</div>"
+      ],
+      "text/plain": [
+       "                                          comment_text  \\\n",
+       "0                              [{{talkarchive}}\\n, \\n]   \n",
+       "1    [== Link editing should work when cursor is on...   \n",
+       "2    [\\n, :Yes, the little down-arrow with B/F/Link...   \n",
+       "3                                                 [\\n]   \n",
+       "4    [== Collapse same text links ==\\n, \\n, <small>...   \n",
+       "..                                                 ...   \n",
+       "429                                               [\\n]   \n",
+       "430  [== User Interface ==\\n, \\n, <small>User agent...   \n",
+       "431                                               [\\n]   \n",
+       "432  [== Feedback by users that see no feedback lin...   \n",
+       "433  [== Usability ==\\n, \\n, It's great that you're...   \n",
+       "\n",
+       "                      date_created     Author  \n",
+       "0                                              \n",
+       "1    20:38, 13 December 2011 (UTC)    Dantman  \n",
+       "2    22:16, 13 December 2011 (UTC)  JakobVoss  \n",
+       "3                                              \n",
+       "4    20:43, 13 December 2011 (UTC)    Dantman  \n",
+       "..                             ...        ...  \n",
+       "429                                            \n",
+       "430  12:02, 30 December 2011 (UTC)     TJRana  \n",
+       "431                                            \n",
+       "432                                            \n",
+       "433                                            \n",
+       "\n",
+       "[434 rows x 3 columns]"
+      ]
+     },
+     "execution_count": 7,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "test_df"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 65,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "fp2 =\"/data/users/mgaughan/mw-repo-lifecycles/discussion_data/parsoid/parsoid-talk-archive-2.json\"\n",
+    "with open(fp2, 'r') as file2:\n",
+    "        data2 = json.load(file2)\n",
+    "data2 = data2['sections']\n",
+    "test_df2 = generate_csv(data2)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 66,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/html": [
+       "<div>\n",
+       "<style scoped>\n",
+       "    .dataframe tbody tr th:only-of-type {\n",
+       "        vertical-align: middle;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe tbody tr th {\n",
+       "        vertical-align: top;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe thead th {\n",
+       "        text-align: right;\n",
+       "    }\n",
+       "</style>\n",
+       "<table border=\"1\" class=\"dataframe\">\n",
+       "  <thead>\n",
+       "    <tr style=\"text-align: right;\">\n",
+       "      <th></th>\n",
+       "    </tr>\n",
+       "  </thead>\n",
+       "  <tbody>\n",
+       "  </tbody>\n",
+       "</table>\n",
+       "</div>"
+      ],
+      "text/plain": [
+       "Empty DataFrame\n",
+       "Columns: []\n",
+       "Index: []"
+      ]
+     },
+     "execution_count": 66,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "test_df2"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 63,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "df_combined = pd.concat([test_df, test_df2], ignore_index=True)\n",
+    "df_cleaned = df_combined[df_combined['Author'] != '']"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 64,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/html": [
+       "<div>\n",
+       "<style scoped>\n",
+       "    .dataframe tbody tr th:only-of-type {\n",
+       "        vertical-align: middle;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe tbody tr th {\n",
+       "        vertical-align: top;\n",
+       "    }\n",
+       "\n",
+       "    .dataframe thead th {\n",
+       "        text-align: right;\n",
+       "    }\n",
+       "</style>\n",
+       "<table border=\"1\" class=\"dataframe\">\n",
+       "  <thead>\n",
+       "    <tr style=\"text-align: right;\">\n",
+       "      <th></th>\n",
+       "      <th>comment_text</th>\n",
+       "      <th>date_created</th>\n",
+       "      <th>Author</th>\n",
+       "    </tr>\n",
+       "  </thead>\n",
+       "  <tbody>\n",
+       "    <tr>\n",
+       "      <th>1</th>\n",
+       "      <td>[==Parsoid working but getting JSON error==\\n,...</td>\n",
+       "      <td>03:07, 31 May 2015 (UTC)</td>\n",
+       "      <td>Alex Mashin</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>2</th>\n",
+       "      <td>[\\n, ----\\n, \\n, I find out that when you use ...</td>\n",
+       "      <td>09:30, 20 Jun 2015 (UTC)</td>\n",
+       "      <td>mnrahimi</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>4</th>\n",
+       "      <td>[==Set up in web server?==\\n, My wiki is on th...</td>\n",
+       "      <td>15:37, 24 June 2015 (UTC)</td>\n",
+       "      <td>Arlolra</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>6</th>\n",
+       "      <td>[== Multiple wikis ==\\n, Can several Mediawiki...</td>\n",
+       "      <td>18:35, 13 October 2012 (UTC)</td>\n",
+       "      <td>Amire80</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>7</th>\n",
+       "      <td>[\\n, : Yes. The Parsoid takes a prefix when th...</td>\n",
+       "      <td>22:34, 15 October 2012 (UTC)</td>\n",
+       "      <td>Jdforrester (WMF)</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>...</th>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "      <td>...</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>160</th>\n",
+       "      <td>[== Installation on OS X {{Resolved}} ==\\n, \\n...</td>\n",
+       "      <td>13:53, 31 May 2015 (UTC)</td>\n",
+       "      <td>Dieudo</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>161</th>\n",
+       "      <td>[\\n, : Resolved by [https://www.mediawiki.org/...</td>\n",
+       "      <td>15:09, 24 June 2015 (UTC)</td>\n",
+       "      <td>Arlolra</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>163</th>\n",
+       "      <td>[== Error: Cannot find module '/etc/mediawiki/...</td>\n",
+       "      <td>16:35, 29 October 2015 (UTC)</td>\n",
+       "      <td>Krauss</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>164</th>\n",
+       "      <td>[\\n, : bin/server.js is in parsoid master and ...</td>\n",
+       "      <td>16:37, 29 October 2015 (UTC)</td>\n",
+       "      <td>SSastry (WMF)</td>\n",
+       "    </tr>\n",
+       "    <tr>\n",
+       "      <th>166</th>\n",
+       "      <td>[==Can see VisualEditor interface but can't us...</td>\n",
+       "      <td>00:44, 19 March 2016 (UTC)</td>\n",
+       "      <td>2A01:E35:2F5E:A0E0:948F:579B:2435:72DB</td>\n",
+       "    </tr>\n",
+       "  </tbody>\n",
+       "</table>\n",
+       "<p>106 rows × 3 columns</p>\n",
+       "</div>"
+      ],
+      "text/plain": [
+       "                                          comment_text  \\\n",
+       "1    [==Parsoid working but getting JSON error==\\n,...   \n",
+       "2    [\\n, ----\\n, \\n, I find out that when you use ...   \n",
+       "4    [==Set up in web server?==\\n, My wiki is on th...   \n",
+       "6    [== Multiple wikis ==\\n, Can several Mediawiki...   \n",
+       "7    [\\n, : Yes. The Parsoid takes a prefix when th...   \n",
+       "..                                                 ...   \n",
+       "160  [== Installation on OS X {{Resolved}} ==\\n, \\n...   \n",
+       "161  [\\n, : Resolved by [https://www.mediawiki.org/...   \n",
+       "163  [== Error: Cannot find module '/etc/mediawiki/...   \n",
+       "164  [\\n, : bin/server.js is in parsoid master and ...   \n",
+       "166  [==Can see VisualEditor interface but can't us...   \n",
+       "\n",
+       "                     date_created                                  Author  \n",
+       "1        03:07, 31 May 2015 (UTC)                             Alex Mashin  \n",
+       "2        09:30, 20 Jun 2015 (UTC)                                mnrahimi  \n",
+       "4       15:37, 24 June 2015 (UTC)                                 Arlolra  \n",
+       "6    18:35, 13 October 2012 (UTC)                                 Amire80  \n",
+       "7    22:34, 15 October 2012 (UTC)                       Jdforrester (WMF)  \n",
+       "..                            ...                                     ...  \n",
+       "160      13:53, 31 May 2015 (UTC)                                  Dieudo  \n",
+       "161     15:09, 24 June 2015 (UTC)                                 Arlolra  \n",
+       "163  16:35, 29 October 2015 (UTC)                                  Krauss  \n",
+       "164  16:37, 29 October 2015 (UTC)                           SSastry (WMF)  \n",
+       "166    00:44, 19 March 2016 (UTC)  2A01:E35:2F5E:A0E0:948F:579B:2435:72DB  \n",
+       "\n",
+       "[106 rows x 3 columns]"
+      ]
+     },
+     "execution_count": 64,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "df_cleaned"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 57,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "output_file = '0220_ve_rfcs_text.csv'\n",
+    "df_cleaned.to_csv(output_file, index=False)"
+   ]
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "base",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "codemirror_mode": {
+    "name": "ipython",
+    "version": 3
+   },
+   "file_extension": ".py",
+   "mimetype": "text/x-python",
+   "name": "python",
+   "nbconvert_exporter": "python",
+   "pygments_lexer": "ipython3",
+   "version": "3.10.15"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 2
+}
diff --git a/src/helper_scripts/cleaning_scripts/gerrit_cleaning.ipynb b/src/helper_scripts/cleaning_scripts/gerrit_cleaning.ipynb
index 0c69fc5..8f15695 100644
--- a/src/helper_scripts/cleaning_scripts/gerrit_cleaning.ipynb
+++ b/src/helper_scripts/cleaning_scripts/gerrit_cleaning.ipynb
@@ -2,7 +2,7 @@
  "cells": [
   {
    "cell_type": "code",
-   "execution_count": 10,
+   "execution_count": 17,
    "metadata": {},
    "outputs": [],
    "source": [
@@ -12,7 +12,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 11,
+   "execution_count": 18,
    "metadata": {},
    "outputs": [],
    "source": [
@@ -23,16 +23,16 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 12,
+   "execution_count": 19,
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "22646"
+       "22643"
       ]
      },
-     "execution_count": 12,
+     "execution_count": 19,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -22716,9 +22716,19 @@
   },
   {
    "cell_type": "code",
-   "execution_count": null,
+   "execution_count": 20,
    "metadata": {},
-   "outputs": [],
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "22643\n",
+      "22643\n",
+      "All IDs are unique.\n"
+     ]
+    }
+   ],
    "source": [
     "#checking for unique-ness\n",
     "ids = [item['id'] for item in data]\n",
@@ -22731,7 +22741,42 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 8,
+   "execution_count": 21,
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "Total IDs: 22643\n",
+      "Unique IDs: 22643\n",
+      "No duplicate IDs found.\n"
+     ]
+    }
+   ],
+   "source": [
+    "from collections import Counter\n",
+    "# Extract IDs\n",
+    "ids = [item['id'] for item in data]\n",
+    "\n",
+    "# Create a counter for the IDs\n",
+    "id_counter = Counter(ids)\n",
+    "\n",
+    "# Print the total number of IDs and the number of unique IDs\n",
+    "print(f\"Total IDs: {len(ids)}\")\n",
+    "print(f\"Unique IDs: {len(set(ids))}\")\n",
+    "\n",
+    "# Print duplicates\n",
+    "duplicates = [id for id, count in id_counter.items() if count > 1]\n",
+    "if duplicates:\n",
+    "    print(\"Duplicate IDs:\", duplicates)\n",
+    "else:\n",
+    "    print(\"No duplicate IDs found.\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 22,
    "metadata": {},
    "outputs": [],
    "source": [
@@ -22769,11 +22814,11 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 9,
+   "execution_count": 23,
    "metadata": {},
    "outputs": [],
    "source": [
-    "generate_csv(data, \"0214_ve_gerrit_test.csv\")"
+    "generate_csv(data, \"0214_https_gerrit_test.csv\")"
    ]
   }
  ],
diff --git a/src/helper_scripts/cleaning_scripts/https-talk-raw.txt b/src/helper_scripts/cleaning_scripts/https-talk-raw.txt
new file mode 100644
index 0000000..f337ce4
--- /dev/null
+++ b/src/helper_scripts/cleaning_scripts/https-talk-raw.txt
@@ -0,0 +1,884 @@
+== Organisation of the content page ==
+Here are the thoughts which drived my writing/expansion of the content page.
+
+I follow wikitech-l and wikitech-ambassadors since many years (less for the latter :) and I have difficulties to track the various topics. I’m interested in the HTTPS topic and  I find both the technical and community people should be involved in this question, hence a job for a wikitech ambassador.
+
+I find this page should be a portal/hub -- still better it is presently -- explaining the general topic, the various questions involved (better than only the keywords presently), the past and coming deployments, and a collection of pointers about the state of the discussion (wikitech-l and bugzilla mainly for this topic).
+
+Any thoughts about this organisation?<br />
+(Perhaps we can use this section -- with subsections -- to discuss specifically about the organisation, and let the other sections about true HTTPS questions.)<br />
+~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 09:34, 18 August 2013 (UTC)
+: [[w:en:WP:BOLD|Be bold]]. :-)  --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 16:40, 18 August 2013 (UTC)
+: Hi Seb35. Thanks for the dump. I am a little concerned, though, that people who are pointed to this page due to the planned Wednesday deploy of SecureLogin by default won't know where to begin; it's a little text heavy without much "what is going on, what this means for you" in simple and brief language. I hope you don't mind, but I'm going to [[w:en:WP:BOLD|Be bold]] and drastically rearrange this page to address the most common questions and conerns from users who are having problems with HTTPS. I'm going to keep much of what you wrote, just re-arrange, mostly. Thanks again! [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 22:49, 19 August 2013 (UTC)
+::Hi, thanks a lot for the rewritting, it’s better now with these simple explanations. I removed my paragraph about PRISM since you better summarised it in the introduction; I hesitated about adding a link, but it could distract the reader. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 12:14, 20 August 2013 (UTC)
+
+== Soft HSTS (HTTP Strict-Transport-Security) ==
+
+I wrote [[:mw:Extension:HSTS|an extension]] for MediaWiki to enable [[:en:HTTP Strict-Transport-Security|HSTS]] on a per-user basis. The rationale behind is to let the privacy-conscious users to opt-in to HTTPS-everytime (for all compatible browsers) independently of their current connected or unconnected status, and at the same time not force the other users to use HTTPS (particularly if they use to live in a HTTPS-unfriendly environment as the China).
+
+I find such an extension would be worth to be installed on the Wikimedia projects (in the first times on the test wikis and then the MediaWiki wiki) to balance between the advantages and drawbacks of HTTPS, as well as slowly increase the HTTPS load of the servers. HSTS coming with a high constraint (fatal error in case of bad TLS/HTTPS connection), I find it could be tested with increasing expiration times (1 hour; 1 day; 2 weeks; 1 month) with some volunteers during the next year to test if all works correctly (e.g. the users will obligatorily complain if their old browser’s cipher suite or SSL 3.0 is removed).
+
+~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 17:03, 18 August 2013 (UTC)
+:I misunderstood the deployment planned for August 21, 2013; I thought it was only the log-in page. This extension becomes almost useless if all HTTP traffic is 301-redirected to HTTPS, or it could be tweaked to remove the user preference and be activated for all logged-in users in order to remove the 301-redirect-over-HTTP step which can still be MITMed/spied. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 18:18, 18 August 2013 (UTC)
+:And the extension is now updated to give the server administrator the possibility to force anonymous and/or logged-in users to have a STS header, or to let the logged-in users choose if they want one. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 20:06, 18 August 2013 (UTC)
+
+== Load script from home wiki ==
+
+En.wiki is my homewiki, and in all other projects I have this in my vector.js:<br /><code>mw.loader.load( '//en.wikipedia.org/w/index.php?title=User:Edokter/MenuTabsToggle.js&action=raw&ctype=text/javascript' );</code>
+
+This fails in modern browsers as a XSS-violation when in HTTPS. Are there any provisions where the several Wikimedia domains are trusted with regard to eachother? <span style="font-family:'Trebuchet MS'"> — [[User:Edokter|<span style="color:#008"><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style="color:#080">talk</span>]]) — </span> 09:56, 20 August 2013 (UTC)
+
+:I don’t know well XSS, but this syntax works for me (Opera 12.16, I have it in my en.wp common.js). Else I see on [[:mw:ResourceLoader/Migration guide (users)#Migrating user scripts]] it is recommanded to keep importScript instead of switching to mw.loader to avoid problems; perhaps you can try with importScript. Else what browser+version do you have? ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 12:41, 20 August 2013 (UTC)
+: I see [[:en:User:Edokter/MenuTabsToggle.js]] itself calls <code>mw.loader.load</code> with 'http' explicitly specified, and Firefox 23.0 here complains about the mixed content due to that. Try making that protocol-relative as well? [[User:Anomie|Anomie]] ([[User talk:Anomie|talk]]) 13:47, 20 August 2013 (UTC)
+
+::A bug in Chrome (or was it IE?) prevents use of protocol-relative stylesheets in the .load method. XSS stands for 'Cross-site scripting'. Most moders browsers block loading scripts form another domain when you are on a secure connection. The only way to allow secure cross-site scripts to load is by whitelisting those domains in the certificate. That is what my question partains to: does our certificate has such a whitelist? <span style="font-family:'Trebuchet MS'"> — [[User:Edokter|<span style="color:#008"><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style="color:#080">talk</span>]]) — </span> 20:47, 20 August 2013 (UTC)
+:::Independently of XSS, about the HTTP/HTTPS in the scripts and problems with protocol-relative, you can use some script like
+:::<syntaxhighlight lang="javascript">mw.loader.load( window.location.protocol+'//en.wikipedia.org/w/...' );</syntaxhighlight>
+:::([https://developer.mozilla.org/en-US/docs/Web/API/window.location ref]) ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 22:03, 20 August 2013 (UTC)
+:::: Seb35's solution is what I most commonly see for addressing this issue, so that's probably a good solution in this case. Edokter, the enwiki certificate has most of the other domains in the Subject Alternative Name. I personally haven't encountered the issue with the browsers I user, but I'll see if I can reproduce if you let me know what you're using. [[User:CSteipp|CSteipp]] ([[User talk:CSteipp|talk]]) 22:42, 26 August 2013 (UTC)
+:::::HTTPS has just kicked in and to my surprise, all my scripts seem to load from en.wiki just fine. <span style="font-family:'Trebuchet MS'"> — [[User:Edokter|<span style="color:#008"><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style="color:#080">talk</span>]]) — </span> 22:09, 28 August 2013 (UTC)
+
+== Excluded language ==
+
+Please add ckb wikipedia to excluded language. All sysops of ckb.wiki are from Iran and we can not access to wikimedia projects via HTTPS.--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 19:01, 20 August 2013 (UTC)
+:What is the exact list of the excluded languages: is it only <code>zh</code> and <code>fa</code>? Or are there also the other Chinese languages: <code>yue/zh-yue</code>, <code>wuu</code>, <code>gan</code>, <code>cdo</code>, <code>nan/zh-min-nan</code>? +those of Iran? Is there a gerrit patch about the config? ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 20:25, 20 August 2013 (UTC)
+:Please see [https://bugzilla.wikimedia.org/show_bug.cgi?id=52846 bug 52846], these wikis mostly used in Iran and have same problem: fa, ckb, mzn, glk, ku. I don't know any thing about Chinese languages.--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 20:34, 20 August 2013 (UTC)
+:The current plan is to exclude based on the IP/location of the user, not the language wiki. This means that users from eg China will be able to login to English Wikipedia over HTTP if needed. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:40, 21 August 2013 (UTC)
+
+== update of automated editing tools ==
+
+Are pywikipediabot, autowikibrowser, etc, now https compliant? It would be extremely disruptive to implement this change without automated editing tools being able to accommodate it. [[User:DavidLeighEllis|DavidLeighEllis]] ([[User talk:DavidLeighEllis|talk]]) 19:24, 20 August 2013 (UTC)
+:According to [[:mailarchive:wikitech-ambassadors/2013-August/000349.html|this message]] (just sent), pywikipediabot was updated for HTTPS and the pywikipediabot users must update their code with the last version. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 21:27, 20 August 2013 (UTC)
+:Please let me know (preferably via IRC or email, greg{{@}}wikimedia.org) if you see any tools that are not ready as soon as possible. Thanks! [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:42, 21 August 2013 (UTC)
+
+== Commons, Wikidata and SUL ==
+
+Won't this create lots of trouble for people in China and Iran who need to upload an image to Commons or modify an interwiki link on Wikidata?
+
+* Commons: You must be logged in to upload an image. If HTTPS is unavailable and mandatory, then you can't log in.
+* Wikidata: It is possible to edit links without logging in, so I suppose that you can edit as an IP using HTTP? This however reveals your IP for everyone to see. Editing over HTTP also reveals your IP address, but only to anyone who is wiretapping you at the same time as you are accessing the Internet.
+* SUL: Logs you in automatically if you visit another project. Doesn't this mean that Chinese and Iranian users will have to log out in order to read an article in another language? This could be very inconvenient if you at the same time need to be logged in on Chinese or Iranian Wikipedia.
+
+You can presumably access HTTPS by using VPN or TOR and you can disable login on selected projects by changing your cookie settings. However, lots of users probably don't know how to do this and the result will instead be that logging in will be disabled. I am personally able to use HTTPS and have HTTPS Everywhere installed, but I understand that lack of unencrypted HTTP for logged in users may cause lots of problems to users in some countries. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 19:49, 20 August 2013 (UTC)
+:The current plan is to redirect based on the IP/location of the user, not based on language wiki. This should alleviate this issue as we'll whitelist users from China and Iran initially, along with potentially some locations that have a hard time using HTTPS. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:44, 21 August 2013 (UTC)
+
+== HTTPS problem ==
+
+Hello. Now we can't access to all WM projects (except Meta, Commons and Incubator)!--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 19:54, 20 August 2013 (UTC)
+*I guess Meta, Commons, and Incubator should all be excluded from the forced https until the "GeoIP" functions are available, in order not to cause any problems there for Iranian or Chinese users who e.g. want to complain here on Meta about https problems, are active with uploading files on Commons, or active in test-projects in their language on Incubator. --<small>[[User:MF-Warburg|MF-W]]</small> 20:01, 20 August 2013 (UTC)
+Now Bugzilla, MediaWiki and Wikidata have not any problem, but all WM projects are out of access. Now I am sysop on ckb wikipedia an I can't open even one page! What are we suppose to do?--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 20:07, 20 August 2013 (UTC)
+: Please see the "[[{{SUBJECTPAGENAME}}#Help!|Help!]]" section of the subject-space page. [[IRC]] is fastest. :-)  --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 21:23, 20 August 2013 (UTC)
+:I'm confused, Calek, can you honestly not access "even on page" *right now*? We haven't made any changes yet. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:45, 21 August 2013 (UTC)
+
+== why Chinese languages are excluded？ ==
+
+I think Chinese wikipedian community has made it clear that all Chinese language(Classical Chinees, Wuu chinese etc) should not be convert into https version, but here I see nothing. can somebody tell me why please? as A classical Chinese editor, I will no longer be able to do my work if it is true that Meta forget their promises. 
+
+----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 23:04, 20 August 2013 (UTC)
+: See also [[bugzilla:52846#c12]] and try to get a complete list of the languages. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 23:12, 20 August 2013 (UTC)
+
+The Chinese community has given a list, on that list, it shows what kind of Chinese language should not be https, that also include Tibetan, another Sino-Tibetan language that will be influenced. because most of the native speakers are '''located in China''' where HTTPs isn't an easy option. we have already got restrictions from Communist party. https is no help to us. ----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 23:16, 20 August 2013 (UTC)
+
+== Leave choice to users ==
+Please let users choose which transport they want to use. --[[User:Purodha|Purodha Blissenbach]] ([[User talk:Purodha|talk]]) 23:06, 20 August 2013 (UTC)
+* This. It will be complete crap if I will be forced to edit through HTTPS, it's slow on my instable connection. And FYI, forcing users should be only last resort, and I see no reason to change to HTTPS voluntarily. [[User:KPu3uC B Poccuu|KPu3uC B Poccuu]] ([[User talk:KPu3uC B Poccuu|talk]]) 02:32, 21 August 2013 (UTC)
+
+Please leave the choice to user, this is so wrong to force people to use HTTPS if they want to stay connected. --[[User:PierreSelim|PierreSelim]] ([[User talk:PierreSelim|talk]]) 05:19, 21 August 2013 (UTC)
+:You can [[HTTPS#Disabling|turn off HTTPS]] in the preferences. As of now I don’t see it, I guess it will be deployed in some hours at the same time HTTPS will become mandatory. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 06:33, 21 August 2013 (UTC)
+::Keep in mind that that will only disable the secure browsing and secure editing features; log-in remains only HTTPS even if that preference is selected. [[User:Risker|Risker]] ([[User talk:Risker|talk]]) 08:12, 21 August 2013 (UTC)
+:::That should be enough for my JavaScript bot and for web-debugging. I'd prefer if I don't have to make my browser trust the Fiddler certificate. -- [[User:Rillke|Rillke]] ([[User talk:Rillke|talk]]) 08:11, 22 August 2013 (UTC)
+
+
+Is there anyway to make the opting out of HTTPS a global preference?  I tend to go to the foreign language wikis to get more extensive articles about subjects of greater import to that language community, and I'm having to manually go to the preferences page the first time I visit them after the change and to opt out of HTTPS for that wiki. That has been and remains my biggest gripe about the HTTPS switchover. [[User:Carolina wren|Carolina wren]] ([[User talk:Carolina wren|talk]]) 02:31, 12 September 2013 (UTC)
+
+== Translation ==
+
+Hi. Why neither this page nor global message delivery post isn't/wasn't translatable? Do you think everybody on the planet is at least en-2? Althought I try to AGF but I can't consider it another way than not respect to local not English communities who are not obliged to learn English. WMF should never do that way again. --[[User:Base|Base]] ([[User talk:Base|talk]]) 23:26, 20 August 2013 (UTC)
+:Basically this is now possible in a manual way, although I’m personaly relunctant to use the Translated extension because the page is not stable and would ask frequent re-translations, but if someone wants to set up it, just do. I asked the Meta admins to [[Meta:Requests for help from a sysop or bureaucrat#Translate the link of Special:CentralNoticeBanners/edit/Genericmaintenancenotice|change the link in the banners]] (I would be very happy if someone could do that!). I sent a message to the [[:mailarchive:translators-l/2013-August/002362.html|translators-l mailing list]] about this translation. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 13:02, 21 August 2013 (UTC)
+
+== List of Chinese Wikipedia  ==
+
+Please Notice these languages also need to remain http.
+
+*[//zh-classical.wikipedia.org/wiki/%E7%B6%AD%E5%9F%BA%E5%A4%A7%E5%85%B8:%E5%8D%B7%E9%A6%96 Classical Chinese(lzh)]
+*[//wuu.wikipedia.org/wiki/%E5%B0%81%E9%9D%A2 Wuu Chinese(wuu)]
+*[//gan.wikipedia.org/wiki/%E8%B4%9B%E8%AA%9E Gan Chinese(Gan)]
+*[//hak.wikipedia.org/wiki/Th%C3%A8u-Ya%CC%8Dp Hakka Chinese(Hak)]
+*[//zh-yue.wikipedia.org/wiki/%E9%A0%AD%E7%89%88 Cantonese(zh-yue) ]
+*[//bo.wikipedia.org/wiki/%E0%BD%82%E0%BD%99%E0%BD%BC%E0%BC%8B%E0%BD%84%E0%BD%BC%E0%BD%A6%E0%BC%8D Tibetan(bo)]
+*[//zh-min-nan.wikipedia.org/wiki/Th%C3%A2u-ia%CC%8Dh Minnan Chinese(zh-min-nan)]
+
+----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 23:28, 20 August 2013 (UTC)
+
+Sorry there is two more languages:
+* [//cdo.wikipedia.org/wiki/T%C3%A0u_Hi%C4%95k Mindong Chinese(cdo)]
+*[//ug.wikipedia.org/wiki/%D8%A6%DB%87%D9%8A%D8%BA%DB%87%D8%B1%DA%86%DB%95_%DB%8B%D9%89%D9%83%D9%89%D9%BE%D9%89%D8%AF%D9%89%D9%8A%DB%95 Uyghur (ug)]
+
+Uyghur are Turkish language, a majority of Uighur people lives in the west part of China.  
+Thank you<br />{{unsigned|Benjamin Jiperus|23:49, 20 August 2013 (UTC)}}
+:I opened the [[:bugzilla:53144|bug 53144]] for tracking this problem and wrote the list you gave (+zh :) ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 07:39, 21 August 2013 (UTC)
+
+::[//ii.wikipedia.org Sichuan Yi (ii)] ([//ii.wikipedia.org/wiki/ 16 articles by now]) --<span style="font-family:Palatino">[[User:Geitost|Geitost]] [[User talk:Geitost|<sup>''diskusjon''</sup>]]</span> 07:31, 22 August 2013 (UTC)
+
+== Perfect forward secrecy ==
+
+Will the new https-including setup have the [http://en.wikipedia.org/wiki/Perfect_forward_secrecy Perfect forward secrecy] property? If not, it would be nice to have. There should be an option to prioritize Diffie-Hellman for key-exchange to achieve this. Wishing you good results for the procedure, good to see that coming. --[[User:Methossant|Methossant]] ([[User talk:Methossant|talk]]) 23:35, 20 August 2013 (UTC)
+:According to "[[:wmfblog:2013/08/01/future-https-wikimedia-projects/|The future of HTTPS on Wikimedia projects]]" PFS will not be enabled soon, but it is in the future plans. From the some things I read about PFS [https://www.imperialviolet.org/2011/11/22/forwardsecret.html this blog post] is interesting (activation of PFS by Google) and [http://vincent.bernat.im/en/blog/2011-ssl-perfect-forward-secrecy.html this one] says PFS only cost 15% more in computer time (ECDHE version, because the classical DHE is much more expensive -- 300% more in compute time). But PFS is not completely supported by all modern browsers: IE support lacks, Opera only have DHE; Chromium and Firefox have full support. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 07:05, 21 August 2013 (UTC)
+:: If you have any news in this regard, you want to upgrade to something like quantum cryptography? [[User:João bonomo|João bonomo]] ([[User talk:João bonomo|talk]]) 20:06, 11 September 2013 (UTC)
+
+== Unable to edit Wikidata ==
+
+It says to report trouble here.<br />
+I have not been able to edit Wikidata while logged in for the past couple of days.<br />
+The [edit] buttons all appear initially, then they vanish.<br />
+[[User:Varlaam|Varlaam]] ([[User talk:Varlaam|talk]]) 00:36, 21 August 2013 (UTC)
+:Hi Varlaam, I doubt this is due to the HTTPS (the topic of this Talk: page) as nothing has changed yet :-). I've reported it to the WikiData team in [https://bugzilla.wikimedia.org/show_bug.cgi?id=53200 this bug report]. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 05:07, 22 August 2013 (UTC)
+:: Greg, thanks for pointing this our way. Varlaam, can you give a bit more info? Browser used? Operating system? Can you try switching off your gadgets and see if there is some interplay? --[[User:Denny|denny]] ([[User talk:Denny|talk]]) 09:30, 22 August 2013 (UTC)
+::: I agree with Greg that it shouldn't be the HTTPS. You try disabling all your gadgets, then re-enable each individually to try to figure out if any is the problem. I remember some time ago a script caused a similar issue for me. If this doesn't help (if you still have the issue with all gadgets off, even after clearing your browser's cache, the extra information Denny asked for might be of some help. <b><span style="border:2px solid;font-variant:small-caps">[[User:Hazard-SJ|<span style="background:#00008B;color:#FFF">&nbsp;Hazard-SJ&nbsp;</span>]][[User talk:Hazard-SJ|<span style="color:#00008B;background:red">&nbsp;✈&nbsp;</span>]]</span></b> 23:25, 22 August 2013 (UTC)
+
+== Copy editing notes ==
+
+*Please add a link to some formal statement or roadmap or approved plan that says "[t]he continued work to improve the security and privacy of Wikimedia project users is a stated goal of the Wikimedia Foundation". (I'm not doubting it's true, but a footnote/reference helps.) 
+*It might also be useful to link to some internal or external site that confirms the use of Wikipedia as a site useful for tracking.  
+*I recall some discussion on how images would be handled with HTTPS enabled, but wasn't technically competent enough to follow the conversation. Are there any issues with images that will change the effectiveness of the HTTPS login and browsing? If so, and since we have a huge number of non-Commons pages with images on them, it would be appropriate to mention this.
+*Also appropriate to mention any other situations where HTTPS may not be as effective as expected.
+[[User:Risker|Risker]] ([[User talk:Risker|talk]]) 05:29, 21 August 2013 (UTC)
+
+:1. no idea about that
+:2. added a Jimmy Wales’ tweet with an image (perhaps the journal article is better, don’t know)
+:3 and 4. I guess you are speaking about the traffic analysis, allowing an attacker to guess the page you are reading by collecting the sizes of the pages, images, and ressources from all pages and comparing it afterwards to some specific request you made; if so, I think it is too technical and specific for being worth to be mentioned here (but it’s because of this fact I wrote in the introduction "you can have a reasonable expectation that nobody knows what pages you are visiting").
+:~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 13:22, 21 August 2013 (UTC)
+
+== A request of resolution  ==
+
+Here is all I know(forgive my English):
+*Chinese Wikipedian have send a list of Chinese language(that are not suitable for https) while the meeting was still going 2 weeks ago.I wasn't at the meeting, people who was there told me Wikimedia Foundation would take into account Chinese languages(for example Wuu, Cantonese and Classical.etc)
+*Now people are telling me except Chinese(standard), other dialects and Classical Chinese will still use https. 
+*this is not what we expected. 
+*I hope what is promised(if there is a promise made by Wikimedia Foundation) will be carried out. 
+*If I am wrong about what I say, please tell me the actual situation of converting into https version. 
+
+thank you----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 09:34, 21 August 2013 (UTC)
+:Hi Benjamin. Sorry for the confusion. The current status, as described on [[HTTPS]], is that users from countries where HTTPS is not an option (specifically, China and Iran) will not be redirected to HTTPS but instead will stay on HTTP. Thus, if you are a Chinese user access English Wikipedia, you will still be able to login and view everything because you will be going over HTTP (as you're computer is based in China). Hope that clarifies, let me know if it doesn't. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 20:18, 27 August 2013 (UTC)
+
+== Which documents? ==
+The preamble of this article mentions: "The Wikipedia project was referenced in several documents as a specific source for tracking users' behavior online". Which documents are referenced here? Was it discussed somewhere? -- [[User:Ace111|Ace111]] ([[User talk:Ace111|talk]]) 13:31, 21 August 2013 (UTC)
+:This was raised by [[User:Risker|Risker]] two sections above; I just added a link to one document I know, but I don’t know others. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 13:37, 21 August 2013 (UTC)
+:: Jimbo's twitter post refers to a NSA slide from [http://www.theguardian.com/world/2013/jul/31/nsa-top-secret-program-online-data Guardian] with a question: "Why are we interested in HTTP?" and an answer "Because nearly everything a typical user does on the Internet uses HTTP", followed by examples of web sites such as Facebook, Yahoo, Twitter, myspace, CNN, mail.ru, Wikipedia, Google and Gmail. I don't think this is a proper reference for Wikipedia as a specific source for tracking users' behavior. -- [[User:Ace111|Ace111]] ([[User talk:Ace111|talk]]) 14:55, 21 August 2013 (UTC)
+:::I remembered some people in the discussions (on wikitech-l probably) with a similar opinion. I don’t have real opinion myself if this constitutes an evidence or not; but it’s the only thing I know that people refered for this claim, but obviously perhaps there are others I missed. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 22:19, 21 August 2013 (UTC)
+
+== privacy concerns with images embedded in pages, served by Commons ==
+
+Is HTTPS fully supported as well for images hosted on Commons (if Commons does not have HTTPS support for now), when these images (most often thumbnailed) are embedded in Wikipedia pages ?
+Can you warranty that noone will know which Wikipedia you are consulting (including in Talk pages) if they embed these images in an unique way ? It is easy to deduce which pages you are reading if you can track the images embedded in them.
+Commons should then support HTTPS, including on the images server (but there's a huge scalability problem because Commons is extremely large and the thumbnail image servers have lots of work to do, probably much more than wikis themselves).
+
+Also a good thing to do would be to mutualize ALL WMF wikis on the same base domain, so that we could use the same logon domain and remain in it, even when navigating on foreign wikis (it would require only a new design for paths; e.g. allowing transparent remapping of
+: http(s)://(projectlangcode).(wikipedia).org/wiki/(pagename)
+to
+: http(s)://www.wikimedia.org/(wikipedia)/(lang)/wiki/(pagename)
+
+One bug advantage would be the unification of security, simplification of navigation. In fact we would just connect via HTTP or HTTPS to a single proxy with a single URL:
+: https://wikimedia.org/logon
+and then all navigation would occur within the same domain within the same session, to request any number of pages or images, from any wiki of the foundation. only within this encrypted HTTPS session would the legacy URLs be requested. This proxy domain would connect directly to any one of the existing Squid proxies, forwarding internally the requests to the appropriate project wiki and image servers (or other services, including Worpress blogs, IRC channels, submission APIs, etc. that are compatible with HTTP proxies).
+
+But the users won't see now any change in their address bar that will only show
+: https://wikimedia.org/logon
+during their navigation across pages, projects and services. Even when they will right click a link, they will be show anonymized URLs encrypted with their current secure session keys (e.g. https://go.wikimedia.org/(base-64 encoded encrypted string containing the service/project/language/page?get parameters).
+Note that the proxy delivering an HTML wiki page could transform as well these links using short URLs specific to the session, to make the base-64 strings short (the proxy would cache the URLs from the original page to build short URLs specific to the session and not comparable across users, using a simple SHA1 digest of the full URL, encrypted with the private session key, so that the delivered HTML pages would only contain relative links like "/(short base64 string)")
+
+The base-64 encoding is suggested, but a larger encoding alphabet could make the string even a bit shorter, similar to those strings used on services like TinyURL. As well the non-encrupted string could be cached internally with a mapping to make them even shorter (based on usage statistics) for frequently accessed URLs. The encryption of these short URLs would still remain private and specific to each user session.
+
+Note that this encyption of URLs does not require to deliver any encryption key to the client, it is purely internal to the proxy that manages the encryption/devyption keys internally. Also this encryption will not increase the length of short URLs.
+
+[[User:Verdy p|verdy_p]] ([[User talk:Verdy p|talk]]) 19:51, 21 August 2013 (UTC)
+
+:Commons and upload.wikimedia.org (where images are actually served from) support HTTPS. All of our projects have fully supported HTTPS for quite some time now.--[[User:Ryan Lane (WMF)|Ryan Lane (WMF)]] ([[User talk:Ryan Lane (WMF)|talk]]) 01:08, 29 August 2013 (UTC)
+
+== Loss of browser history ==
+
+I just had cause to use Internet Explorer and it seems as though it was not saving history for https pages. I have not investigated fully but if I was forced to use Internet Explorer, I would prefer to be subject to snooping by the NSA than lose my browsing history. [[User:RHaworth|RHaworth]] ([[User talk:RHaworth|talk]]) 21:07, 21 August 2013 (UTC)
+
+== Impossible Log out ==
+Since tonight, I can not log out. It's some feature of https? --[[User:ŠJů|ŠJů]] ([[User talk:ŠJů|talk]]) 20:50, 22 August 2013 (UTC)
+: I usually use the secure login and have never had that problem, so I wouldn't say it's a feature. Did you try going to [[Special:UserLogout]], at least o the secure server? [[Special:Contributions/72.252.242.170|72.252.242.170]] 23:20, 22 August 2013 (UTC)
+:: The page [[Special:UserLogout]] appeared and the login from the top of the page dissappeared but in 1 or 2 second appeared again. However, the bug seems to be eliminated now. --[[User:ŠJů|ŠJů]] ([[User talk:ŠJů|talk]]) 00:53, 23 August 2013 (UTC)
+
+== http/https link embedded in wiki text using the link tool … ==
+
+… does not work. If you select the link tool, and paste an url, it should be stripped off the protocol to get protocol relative urls automatically. At least for WP links like this (completely arbitrary): https://de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 the link tool shall strip the protocol. Adding //de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 to the link tool will create [http:////de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 //de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984] (url with prefix http:////de.wikipedia.org). Furthermore the wiki text (protocol relative url) //de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 should autolink like the non-protocol-relative-url does. --[[User:Herzi Pinki|Herzi Pinki]] ([[User talk:Herzi Pinki|talk]]) 23:02, 22 August 2013 (UTC)
+
+== API ==
+
+Is this going to affect browser logins only, or will pure API sessions (those that occur outside a browser environment) be affected as well? [[User:This, that and the other|This, that and the other]] ([[User talk:This, that and the other|talk]]) 09:17, 25 August 2013 (UTC)
+: This is only for browser logins, the api does not force a redirect [[User:CSteipp|CSteipp]] ([[User talk:CSteipp|talk]]) 22:47, 26 August 2013 (UTC)
+
+== Causing problems ==
+
+I have disabled this in my preferences, as the default left me totally unable to edit, or even view, Wikipedia. (Every time I clicked on a link, or even typed in a url, I was switched to an https url, with a popup window "couldn't parse page name from url ...". Previously, if directed to an https page, I have had to remove the s in order to open the page, but the new change made this impossible. Eventually I managed to open my preferences, find the relevant entry, and uncheck the tick; now everything works smoothly again.
+
+I have no idea what is causing the problem; whether it is my Wikipedia gadgewts, my Firefox add-ons, or my security settings. Nor do I feel inclined to experiment and see what tweaks, if any, would resolve the problem. But it is clear to me that this change should not become a default, or be made mandatory, since this would certainly lock out readers and editors.
+
+If anyone responds to this, please inform me at [http://en.wikipedia.org/wiki/User_talk:RolandR my talk page on English Wikipedia]; I have never before visited Wikimedia. [[User:RolandR|RolandR]] ([[User talk:RolandR|talk]]) 00:13, 29 August 2013 (UTC)
+
+: I'm pretty sure this is due to a script you have installed (as I indicated on the VPT thread). [https://en.wikipedia.org/w/index.php?title=User%3AQuarl%2Fwikipage.js&diff=570605025&oldid=38600544 I fixed it]. [[User:^demon|^demon]] ([[User talk:^demon|talk]])
+::That doesn't seem to have resolved the problem. I re-enabled the secure login in my preferences, and again started to get the "couldn't parse page name" pop-up. Which of my scripts might be causing this? [[User:RolandR|RolandR]] ([[User talk:RolandR|talk]]) 10:56, 29 August 2013 (UTC)
+:::In fact, this seems to have made the problem worse; now, although I have unticked the checkbox in Preferences, every link defaults to https, and I am unable to open any page easily. Please help! [[Special:Contributions/86.186.105.211|86.186.105.211]] 11:10, 29 August 2013 (UTC)
+::::If you wish to change the HTTPS setting back to HTTP, try going to [{{fullurl:en:Special:Preferences|useskin=modern}}] or [{{fullurl:en:Special:Preferences|useskin=cologneblue}}].
+::::If you wish to fix the problem, try going to [[w:User:RolandR/monobook.js]] and [[w:User:RolandR/vector.js]] and change "http://" to "//" everywhere on the pages. The JS files can only be edited by you or by an administrator at English Wikipedia.
+::::If this doesn't help, then it probably means that something is wrong in one of the scripts that you are importing. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 12:31, 29 August 2013 (UTC)
+
+Hello,
+
+I also have some problems. First, I didn't get the images until I clicked to access a Commons page and validate the security certificate; now solved. But it seems the scripts don't work. I have no personnalised JS or CSS (the /monobook.js page or the like don't exist).
+
+Any clue?
+
+[[User:Cdang|Cdang]] ([[User talk:Cdang|talk]]) 13:46, 29 August 2013 (UTC)
+
+== Google Translate ==
+
+When I paste "https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Gadgets" into either http://translate.google.com/ or https://translate.google.com/ I get the message:
+: Google Error
+: Sorry, this URL is invalid
+: http://fr.wikipedia.org:443/wiki/Sp%C3%A9cial:Gadgets
+But when I paste the regular "http://fr.wikipedia.org/wiki/Sp%C3%A9cial:Gadgets", it translates it fine. Can someone attest that this is a Wikimedia problem and, if so, submit a bug about it? - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 08:37, 29 August 2013 (UTC)
+:Looks like a bug in the google tool to me... Apparently it has existed [http://ubuntuincident.wordpress.com/2011/02/07/patch-to-google-translate-https-pages/ for years] already. Perhaps WMF operations can tickle their google contacts a bit. [[User:TheDJ|TheDJ]] ([[User talk:TheDJ|talk]]) 11:52, 29 August 2013 (UTC)
+::I've had this problem ever since I started using HTTPS (a while ago). It's a problem with Google Translate. {{ping|Snowolf}} didn't you write to a mailing list about this last year? [[User:PiRSquared17|PiRSquared17]] ([[User talk:PiRSquared17|talk]]) 18:55, 31 August 2013 (UTC)
+:::I did. I don't think they ever replied to me. <i><b>[[User:Snowolf|<font color = "darkmagenta">Snowolf</font>]] <sup><small>[[User talk:Snowolf|<font color = "darkmagenta">How can I help?</font>]]</small></sup></b></i> 22:09, 31 August 2013 (UTC)
+:::: Hmm. Maybe now that Wikimedia is going HTTPS for all logged-in users on all projects, they'll get more pressure to do something about it. - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 01:26, 2 September 2013 (UTC)
+
+I work for Google, and got the following answer from <b> Google Translate team: </b> <br>
+"Currently, the Google proxy-based web translation cannot translate HTTPS pages. It's a known limitation, and we'd like to remove that limitation."
+: OK, well, there's a very easy fix for that… - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 02:23, 17 September 2013 (UTC)
+
+== [[HTTPS#Various small problems]] ==
+
+I added this section to help users particularly with script problems or certificate problems. Be bold at rewriting it or adding issues, I have only my own experience of HTTPS problems or those reported on the village pumps (although always difficult to precisely understand what is wrong and consider solutions).
+
+For the scripts I guess this is quite important and many editors could wonder why their scripts suddently do no more work, see these few searches: [//fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Recherche&limit=20&offset=20&redirs=1&ns2=1&search=loadjs] (search the exact case loadJS), [//en.wikipedia.org/w/index.php?title=Special%3ASearch&limit=20&offset=20&redirs=1&ns2=1&search=loadjs], [https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=js+write&fulltext=Search&ns2=1&redirs=1&profile=advanced], [https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=js+http&fulltext=Search&ns2=1&redirs=1&profile=advanced]; even, some users call external scripts (sometimes the destination server don’t support https). For these scripts, I don’t know what exactly should be prefered, is it <code>importScriptURI</code>? not <code>mw.loader.load</code>?
+
+About the Authority certificate (DigiCert High Assurance EV Root CA), is there known issues with the devices which don’t have it in their certificate repository? I use to see it on the Internet and with my browsers (Opera, Firefox), but perhaps there are exotic devices or browsers or operating systems or combinaisons of these ones which don’t recognize it. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 19:15, 29 August 2013 (UTC)
+
+== Help Needed: Problems due to Secure site change ==
+
+I'm not even sure how I found my way here to this page, but I am in desperate need of help, as nothing I have tried has made any real difference. Rather than repeat what I've already written over at Wikipedia, I am going to re-post my own initial comment, followed by the entire contents of the discussion that ensued when I created a new section under the same heading I've used here -- which I think may be useful for other editors to read. [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 07:08, 2 September 2013 (UTC)
+
+I) My browser history is absolutely integral to how I do things on the internet. When my browser history first disappeared, I assumed that the problem was somewhere on MY end of things. I racked my brain, I checked everything -- all to no avail. I had no idea that Wiki had switched over to secure pages, so I was really at my wits' end until I just by chance finally noticed that little "https" in the URLs. <Light bulb goes on> I then spent an hour googling a variety of search strings in hopes of finding something that would help resolve the problem. Again to no avail. Finally, I came here [to the Village Pump - technical] to see if anybody had raised the issue.
+
+=== Wikipedia discussion at Village Pump (technical) talk page ===
+
+*ALL EMBEDDED LINKS ARE FOR '''WIKIPEDIA'''
+
+As other editors have [[:en:Wikipedia:Village pump (technical)#Secure site only?|already made note of]], the change-over to Secure URLs is causing problems for a lot of us. I've [[:en:Wikipedia:Village pump (technical)#Who is in charge|already explained above]] how upsetting it was to have my Wikipedia browsing history suddenly disappear. I mistakenly thought that unchecking the setting in my preferences had taken care of the problem. Not So. It turns out that when I specify one of the normal/non-secure Wikipedia URLs, the software no longer recognizes me as a logged-in user -- iow, the pages display as they do for any anon. IP user (and as I discovered by accident, my IP address shows up in the edit history, as one would expect). But as soon as I go to a secure URL, everything goes back to normal -- and that's without having to log in again; iow, it keeps me logged in, as it should. But those secure pages don't show up in my browser history, no matter what I do. Yes, I've changed & re-changed my preference setting and logged back in several times. And I've also looked for the trouble-making cookies that were mentioned above -- but curiously, I don't seem to have ANY cookies for Wikipedia, even though it is one of the few sites where I expressly allow them by default. <sigh> Any help on this would be hugely appreciated! [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 08:34, 1 September 2013 (UTC)
+::You don't actually say - either here or at <span class="plainlinks">[//en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&diff=prev&oldid=570904030 your previous post]</span> - which browser you're using. --[[:en:User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[:en:User talk:Redrose64|talk]]) 09:56, 1 September 2013 (UTC)
+:Ah, I was wondering  why when I  open a new browser window it shows me as not  logged in. [[:en:User:Kudpung|Kudpung กุดผึ้ง]] ([[:en:User talk:Kudpung|talk]]) 09:54, 1 September 2013 (UTC)
+
+:Well, if anyone is interested, I am  using  Ffox 23.0.1 on  MacOS 10.8.4. Looks as if the default  move to  https has thrown more than one spanner in  the works. [[:en:User:Kudpung|Kudpung กุดผึ้ง]] ([[:en:User talk:Kudpung|talk]]) 10:36, 1 September 2013 (UTC)
+::I too am using Firefox, although under Windows XP. Here's how I successfully went back to http:
+::#Go to <span class="example" style="font-family: Georgia, serif;">[[:en:Special:Preferences|Preferences]]</span>, switch off "Always use a secure connection when logged in" and save
+::#Log out of Wikipedia and close all browser tabs that contain Wikipedia pages - but keep the browser itself open
+::#In the browser menu bar, go to Tools → Options → Privacy
+::#Click the link "remove individual cookies", this opens a new window titled "Cookies" - maximise that, it makes things easier
+::#In the search bar of "Cookies", enter <kbd>forceHTTPS</kbd> exactly like that - it's case-sensitive
+::#Highlight a row and click <span class="nowrap" title="This is not a clickable button; it illustrates the button to look for" style="padding:.2em .6em; border:1px solid; border-color:#aaa #555 #555 #aaa; -moz-border-radius: 3px; -webkit-border-radius: 3px; border-radius: 3px; background-color:#f2f2f2; background-image: -moz-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -ms-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -o-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -webkit-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: linear-gradient(top, #fcfcfc, #e0e0e0);  ">Remove Cookie</span> (the <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; -moz-border-radius: 2px; -webkit-border-radius: 2px; border-radius: 2px; -moz-box-shadow: 1px 2px 2px #ddd; -webkit-box-shadow: 1px 2px 2px #ddd; box-shadow: 1px 2px 2px #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -ms-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(top, #eee, #f9f9f9, #eee); padding: 1px 3px; font-family: inherit; font-size: 0.85em;">Delete</kbd> key works on a PC, don't know about a Mac)
+::#Repeat until all are gone, then click <span class="nowrap" title="This is not a clickable button; it illustrates the button to look for" style="padding:.2em .6em; border:1px solid; border-color:#aaa #555 #555 #aaa; -moz-border-radius: 3px; -webkit-border-radius: 3px; border-radius: 3px; background-color:#f2f2f2; background-image: -moz-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -ms-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -o-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -webkit-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: linear-gradient(top, #fcfcfc, #e0e0e0);  ">Close</span>
+::#Visit http://en.wikipedia.org/wiki/ and log in
+::You should now be back on http: --[[:en:User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[:en:User talk:Redrose64|talk]]) 10:50, 1 September 2013 (UTC)
+:::Thanks for your detailed reply, Redrose64. Hopefully that will be very helpful for any Firefox users who find their way to this page. Unfortunately it doesn't help me, perhaps because I am using IE8 (although they are very similar). I had already tried to find those cookies (they were also mentioned above), but as I noted, I was unable to turn up ANY cookies at all for Wikipedia among the cookies listed in my TIF folder. Very puzzling, to say the least. [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 12:52, 1 September 2013 (UTC)
+::::Try looking in your Cookies folder. I don't quite understand why, but Internet Explorer's cookies can be found in both "Temporary Internet Files" and "Cookies". –&#160;'''[[:en:User:PartTimeGnome|PartTimeGnome]]''' <span style="font-size:79%">([[:en:User talk:PartTimeGnome|talk]]&#160;&#124; [[:en:Special:Contributions/PartTimeGnome|contribs]])</span> 20:28, 1 September 2013 (UTC)
+*'''New Wrinkle''' - For a time, I was able to move from page to page in the ''non-secure'' universe, and at least ''those'' pages would show up in my browser history. But something seems to have changed. Now I cannot access ANY non-secure pages -- even when I specify "http" in the address bar of my browser, it just redirects to "httpS", regardless of whether I am logged IN or logged OUT. I think I may be starting to lose my mind. [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 13:18, 1 September 2013 (UTC)
+**What kind of windows edition do you use  ? It seems that IE in the Windows server and possible professional editions seem to not store anything by default if the user is using https. —[[:en:User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[:en:User talk:TheDJ|talk]] • [[:en:Special:Contributions/TheDJ|contribs]]) 15:18, 1 September 2013 (UTC)
+***I'm using Windows 7. What's crazy about all of this is that unchecking the new default setting in preferences seems to have no effect whatsoever. To repeat, yes I've logged out and back in multiple times, and the setting remains unchecked. I've also looked and ''searched'' for those problem cookies, but cannot locate them, if they're even there at all. And I've never seen a Cookies folder, either. Please keep thinking about this -- your efforts are ''greatly'' appreciated! [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 01:36, 2 September 2013 (UTC)
+::::Update: I can now see my Cookies Folder. It took some doing -- no thanks to Microsoft! -- to find out how to get that folder to display. (It requires un-checking the default setting that hides all "protected operating system files".) Unfortunately, the only Wiki cookies I found were quite innocuous. No sign of those problem cookies that force the browser to use https. So I'm right back where I started: '''Still no way to get my browser to display non-secure pages -- and still no browser history for Wikipedia'''. :( [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 03:12, 2 September 2013 (UTC)
+
+== My experience with HTTP links ==
+
+The instructions here say, "''If a user wants to login, the login will happen over HTTPS… and after they are logged in they stay on the HTTPS version of the Wikimedia site they are using.''" We-e-ell... I suppose this is ''technically'' true, but it doesn't quite work the way most people would expect.
+
+After logging out and logging in again a couple of days ago (on the English Wikipedia) under the new HTTPS regime, I noticed that when following HTTP links to most other Wikimedia wikis from e-mails and bookmarks, I was not showing up as being logged in (was arriving under the HTTP protocol, of course). My bookmarks to the English Wikipedia and Meta seemed to be okay (I have visited those since the changeover, so presumably I already did something to fix the problem there), but if I tried my bookmark to, say, the Italian Wikibooks (to choose a random one I hadn't visited in a while), I showed up as being logged out. Reloading didn't help. Reloading bypassing the cache didn't help. Manually typing in the prefix "https://" in the address bar... that did it. Then I was logged in. (So... I have to actually use HTTPS to "remind" WM that I'm already logged in as a registered user?)
+
+Needless to say, I didn't want to manually type in a protocol every time I visited a new Wikimedia wiki (I help to maintain [[Wikimedia News]], so I have occasion to visit "random" WM wikis ''all the time'')! So I did something I ''really'' hate doing: I cleared all my cookies. And all my cookie settings (allow/deny/etc.). And my cache. And my browsing history. And then I closed and reopened Firefox (17.0.7).
+
+After logging in to the English Wikipedia (my "home wiki") again, I found that when I first visited another WM site (in this case, Meta) — via a regular wikilink, no less... not even bookmarks or e-mail links yet — I showed up as ''not logged in''! (And I had to accept a new cookie, which I expected, of course.) Then on to Commons: ''not logged in''! Hey! Whatever happened to SUL?? Okay, so then I reloaded the page. Only then did it tell me "You are centrally logged in… Reload the page to apply your user settings." Okaaay. Reloaded a second time. Fine. But before reloading, I noticed that I was actually ''already'' logged in as me after the first reload. Something's screwy here... Finally, by going to another "new" wiki, I noticed that the first and second reloads can be replaced by two "local" page loads of any sort (i.e., following links to other pages on the same wiki). In other words, I'm not logged in when I first bring up a wiki (a Main Page, in particular), but after either reloading or following an internal link, I am logged in. But only ''then'' do I get the message about "[applying my] user settings". But at that point that's already been done! Something tells me this is not how it's supposed to work.
+
+So then I tried an old HTTP bookmark (this time to the Czech Wikipedia — remember, I first logged in to the English Wikipedia). Not logged in. Not in HTTPS. Reloading didn't work. Back to where I started. So then I navigate through HTTPS links (via [[List of Wikipedias]]) back to the Czech Wikipedia. I ''am'' logged in under HTTPS. Okay, back to the List and then to the, oh, Ilokano Wikipedia. I am logged in under HTTPS.
+
+Hmm. Okay, back to an HTTP ''bookmark'' to the Ilokano Wikipedia. Nope. HTTP and not logged in. (But I was just here! Don't you recognize me?) Finally, to an HTTP bookmark to the English Wikipedia. This time, mercifully, I show up as logged in under HTTPS.
+
+So, the moral of this story seems to be: If you explicitly log in to a Wikimedia wiki, HTTP links to that wiki will come up as HTTPS and have you logged in. Following links to any other Wikimedia wiki (assuming they're HTTPS) works, but only after reloading or following a link. But visiting any other wiki through an HTTP link, even though you have purportedly been "CentralAuth" logged in to "all" of them, you don't get recognized as being logged in and remain an anon under HTTP. Pretty annoying.
+
+So now I have to go through 820 or so bookmarks changing "http:" to "https:" (not to mention actually visiting all 820 wikis again to set new cookies). Yay. - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 10:45, 2 September 2013 (UTC)
+:When I got "You are centrally logged in… Reload the page to apply your user settings.", I checked [[Special:Preferences]] and found that the setting for "Always use a secure connection when logged in" was opposite to what I thought it was. Flipping it and saving, then reloading the appropriate page, got things back in synch. It was necessary to do this separately for meta, commons, etc. --[[User:Redrose64|Redrose64]] ([[User talk:Redrose64|talk]]; [[:en:User:Redrose64|at English Wikipedia]]) 12:09, 2 September 2013 (UTC)
+::Is this [[bugzilla:53538]]? --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 13:40, 2 September 2013 (UTC)
+:::: My original report? Yeah, looks like it (although the thing about the late "centrally logged in" notice isn't mentioned there). I guess we'll see what happens when 1.22wmf16 is deployed ([[mw:MediaWiki 1.22/Roadmap|over the next few days]]). - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 12:47, 5 September 2013 (UTC)
+:::I've been having some trouble staying logged in between projects (i.e. Commons) for a long time - well before https.  But it happens only when I have some scripts enabled (NoScript), and admittedly... I might not have had them all enabled at the start, and so gotten to some state unexpected by the developers.  Have you been using the same sort of script control? [[User:Wnt|Wnt]] ([[User talk:Wnt|talk]]) 18:00, 2 September 2013 (UTC)
+::::What browser are you using? If the problem is that you are logged in when you use HTTPS but not when you use HTTP, then you might wish to install [https://www.eff.org/https-everywhere HTTPS Everywhere], provided that you use a browser compatible with that. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 18:20, 2 September 2013 (UTC)
+
+== Updates on the Https situation ==
+['''Note''': I've copied this from the Village Pump (technical) talk page over at Wikipedia.]
+*'''Update1''' - Hmmm. Has something been tweaked on ''your'' end? (i.e. some lines of code at Wikipedia/Wikimedia?) Just in the last hour I discovered that I was able to access Http pages while I'm logged in -- which I was NOT able to do before (except for a very short period over the weekend). They're also showing up in my browser history, as expected. And I can see that HotCat has returned, as well (though I haven't tried using it as of yet). However -- you knew that was coming, didn't you?? -- there's still some work to be done: When I accessed a couple of articles via redirects, they displayed as though I had suddenly logged out, even though I hadn't done so and was in fact ''demonstrably still logged in!'' (The links on those pages took me to normal pages that displayed properly.) I'll post another update later on today. Needless to say, I'm keeping my fingers crossed that things won't revert to dysfunctionality in the next couple of hours! [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 14:48, 2 September 2013 (UTC)
+::'''Addendum''' to Update1: Complicating the picture I described in my update above, I just had a couple of pages accessed via redirects display ''properly'' -- but a couple of Category pages displayed improperly, as though I had logged out. So it seems there's no real pattern to whatever the hell is going on. <sigh> [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 15:33, 2 September 2013 (UTC)
+*'''Update2''' - Okay, it is now many hours later in the day. The positive developments I noted earlier have held up without reverting to the intractable problems I experienced over the weekend. For the most part, I am able to access Http pages and they display properly -- i.e. the Wiki software recognizes that I am logged in. I can also report that HotCat is functioning normally for me -- another major relief. However, there is still a recurring problem that crops up in a ''seemingly'' random fashion, causing certain pages to display as though I was not logged in -- even though I can go directly to other pages that display normally, without having had to log in again first. I suspect, however, that these problem pages may not be ''entirely'' random -- iow, they may possibly have some feature in common that results in problems with the new software -- mainly because certain pages continue to exhibit this problem every time I access them. Case in point: [[:Category:Biological evolution]], which displays as though I'm just an Anon. IP editor every time.  Guess that'll do it for now. I hope I've given you techies enough "hints" to make some headway in tracking down the source of the problem. :) [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 04:32, 3 September 2013 (UTC)
+
+== Security information ==
+
+When browsing wikipedia (via firefox, if it makes a difference), now in https, getting the security information by pressing the lock icon next to the URL, the browser reports "you are connected to wikipedia.org which is run by (unknown)". Similarly, meta.wikimedia.org is also reported "unknown". When clicking "more information" the browser reports under identity "owner: This website does not supply ownership information". Methinks this warrants correction. [[Special:Contributions/87.68.44.102|87.68.44.102]] 10:02, 4 September 2013 (UTC)
+
+:I was curious, and checked, 12 days later. Using Google Chrome browser, both the identity and certificate seem proper, as <code>meta.wikimedia.org</code>, using SSL with DigiCert High Assurance CA-3 and 128-bit encryption connection SHA-1. I didn't check the entire CA chain, I confess. --[[User:FeralOink|FeralOink]] ([[User talk:FeralOink|talk]]) 13:26, 20 September 2013 (UTC)
+
+==Wikimedia sites and tracking, documentation==
+
+First, I wanted to mention that HTTPS is working perfectly for me, every time, on every WMf site, with the possible exceptions of Wikidata. '''Thank you'''!
+
+Earlier, on 21 August 2013, inquiries were made by [[User:Risker|Risker]]
+<blockquote>"Please add a link to some formal statement or roadmap or approved plan that says "[t]he continued work to improve the security and privacy of Wikimedia project users is a stated goal of the Wikimedia Foundation". (I'm not doubting it's true, but a footnote/reference helps.) It might also be useful to link to some internal or external site that confirms the use of Wikipedia as a site useful for tracking"</blockquote> and by [[User:Ace111|Ace111]]
+<blockquote>"The preamble of this article mentions: "The Wikipedia project was referenced in several documents as a specific source for tracking users' behavior online". Which documents are referenced here? Was it discussed somewhere?"</blockquote>
+These concerns were acknowledged and action was taken to address them by [[User:Seb35|Seb35]]
+<blockquote>"I just added a link to one document I know, but I don’t know others."</blockquote>
+However, I agree with [[User:Ace111|Ace111]]'s subsequent response:
+<blockquote>"Jimbo's twitter post refers to [http://www.theguardian.com/world/2013/jul/31/nsa-top-secret-program-online-data an NSA slide via The Guardian] with a question: "Why are we interested in HTTP?" and an answer "Because nearly everything a typical user does on the Internet uses HTTP", followed by examples of web sites such as Facebook, Yahoo, Twitter, myspace, CNN, mail.ru, Wikipedia, Google and Gmail. I don't think this is a proper reference for Wikipedia as a specific source for tracking users' behavior."</blockquote>
+[https://twitter.com/jimmy_wales/status/362626509648834560 Jimmy Wales' Twitter message] reads as follows:
+<blockquote>NSA snooping on what YOU are reading at Wikipedia means I want us to go to SSL sooner.  Bastards fuck off. Owly <!-- hxxp owly/nv3I6 Owly is a blacklisted site, so I sorta-obfuscated --></blockquote> 
+The Owly-shortened URL directs to [http://static.guim.co.uk/sys-images/Guardian/Pix/audio/video/2013/7/31/1375269604628/KS8-001.jpg this image via The Guardian], which I haven't uploaded, though I guess I should. It is not a COPYVIO, as it is an alleged screen shot of antiquated social media icons in the characteristically MS Paint, circa Win 95 style, of PRISM slides. There is some lettering at the top, in light orange colored font, on a darker orange background, which might say "COMINT" (or maybe HUMINT or NOfORN or one of those other acronyms we've had 4 months with which to become familiar). That isn't suficient as a proper reference for Wikipedia as a specific source for tracking users' behavior, just as Ace111 said.  In fact, Jimmy Wales message was directly [https://twitter.com/StevenWalling/status/363397737254879232 replied to by Steven Walling]
+<blockquote>"the Foundation has not received any requests to date" https://blog.wikimedia.org/2013/07/18/wikimedia-foundation-letter-transparency-nsa-prism/ …</blockquote> which leads me to wonder whether there were evidence of tracking by the NSA of Wikipedia users and/ or editors et al. Next, even though he sounds full of bravado, the content of Jimmy Wales' Twitter message is rather hostile, specifically,
+:'''Bastards fuck off.'''
+Jimmy Wales as an individual is entitled to tell the NSA to fuck of. But using his personal Twitter account as the basis for Wikimedia's decision to transition to SSL, with that particular content, is representing Wikimedia foundation I would think. We don't tell any government entity to fuck of as official policy, I don't think. We didn't tell Khazakhastan to fuck of, nor Syria, nor Libya, nor North Korea, nor the Taliban. I don't need to list further ''bete-noire'' perceived countries, as you get the idea.  Remember, the NSA is acting as explicitly directed by the elected government of the USA, the executive branch and/ or the Department of Homeland Security. Bad men tell the NSA to do bad things.
+
+I don't want that Twitter message linked in the article, here, please? I fully agree with, and applaud Wikimedia's decision to transition to HTTPS and SSL. If further encryption measures are added in the future, I wouldn't argue against it. 
+
+In fact, why is there any need to justify the switch to HTTPS at all? Someone needs to find some non-self-referential external source (or provide better detail from this one, The Guardian article, not Jimmy Wales), or just delete that section entirely, and thus resolve the pesky issue of explaining why SSL is needed. I will take it upon myself to do so, but wanted to explain myself first, and generate discussion, as the AfD folks say!  --[[User:FeralOink|FeralOink]] ([[User talk:FeralOink|talk]]) 01:22, 17 September 2013 (UTC)
+
+== Still being forced into using HTTPS on occasion ==
+
+Just now, I had to go thru the once every 30 days log in again.  And despite having that I do NOT want HTTPS, it forced me into HTTPS and I had go and manually delete the cookies yet again!  I understand why you are advocating HTTPS, but they don't apply to me or my use of Wikimedia, so I like to keep things as simple as possible. It's bad enough that each time I visit a Wikimedia site I haven't used since the change I have to go change the preferences for that site to undo the automatic HTTPS, but to have to keep deleting cookies is even worse. [[User:Carolina wren|Carolina wren]] ([[User talk:Carolina wren|talk]]) 02:15, 29 September 2013 (UTC)
+: This sounds like [[bugzilla:54626|bug 54626]], the fix for which should be deployed starting on Thursday, October 3 and finishing up on October 10. Unless it gets pushed out sooner. [[User:BJorsch (WMF)|BJorsch (WMF)]] ([[User talk:BJorsch (WMF)|talk]]) 13:58, 30 September 2013 (UTC)
+
+== Preference ==
+After this program is implemented, will individual contributors still be able to disable HTTPS if so they desire? [[User:Gryllida|Gryllida]] 22:21, 17 September 2014 (UTC)
+: Why is the above question written in the future tense? This was implemented last year. Individual contributors can disable HTTPS at [[Special:Preferences#mw-prefsection-personal]] by unchecking the "Always use a secure connection when logged in" checkbox. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 22:52, 17 September 2014 (UTC)
+::I'm referring to the planned change.  In October 2014, some projects (not globally; currently this is on Russian Wikipedia) plan to roll out https by default to unregistered contributors. Some others are considering following their example and I'm trying to access the implications of such change. [[User:Gryllida|Gryllida]] 23:03, 17 September 2014 (UTC)
+
+== API from contributor's username ==
+I understand that the program implies that where I visit a page, I will be automatically redirected to HTTPS.  Will the same happen for API queries I send from a bot/script? [[User:Gryllida|Gryllida]] 22:21, 17 September 2014 (UTC)
+::I'm referring to the planned change.  In October 2014, some projects (not globally; currently this is on Russian Wikipedia as a result of community consencus) plan to roll out https by default to unregistered contributors. Some others are considering following their example and I'm trying to access the implications of such change. [[User:Gryllida|Gryllida]] 23:04, 17 September 2014 (UTC)
+
+== Common HTTPS access issues ==
+What is the common nature of the HTTPS access issues the https{{@}}wikimedia.org folks encounter, as suggested [[HTTPS#Help.21|here]]? I e-mailed them in but got no response. I would like to know who we would be locking out here and why. [[User:Gryllida|Gryllida]] 22:21, 17 September 2014 (UTC)
+: HTTPS access is or has been blocked by the authorities in some countries (see [[{{SUBJECTPAGENAME}}#Excluded Countries]]). I assume that users in these countries may run into problems if they have to use an HTTPS connection. I do not know if users also may have other problems. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 22:55, 17 September 2014 (UTC)
+:I was told that this was addressed by extensive EventLogging tests that didn't reveal trouble of "random crappy ISP setup" sort, but only revealed country-specific issues (and this program is being rolled out outside of these countries as I understand). Would be useful to have some documentation of tests, for reference. [[User:Gryllida|Gryllida]] 22:57, 17 September 2014 (UTC)
+== Opting out for unregistered contributors ==
+This is perhaps a slightly useless question, as the folks can use another internet access point to register, and opt out ''then'' (if the preference is still available). But is there currently no means to opt out ''without'' registering? See also [[bugzilla:20151]]. Can we think about it again? To me, a lot of preferences appear to be harmless to expose to IP contributors (HTTPS/HTTP toggle being one of them). [[User:Gryllida|Gryllida]] 22:57, 17 September 2014 (UTC)
+:To clarify: I'm referring to the planned change.  In October 2014, some projects (not globally; currently this is on Russian Wikipedia) plan to roll out https by default to unregistered contributors. Some others are considering following their example and I'm trying to access the implications of such change. [[User:Gryllida|Gryllida]] 23:04, 17 September 2014 (UTC)
+::Where do I find information about the planned change? I hadn't heard of it until you mentioned it on this talk page.
+::Users who are not logged in can still change many settings by using a tool such as [[w:Greasemonkey]]. However, I realise that this method isn't very user-friendly. I don't know if this method provides a way to opt out from forced HTTPS.
+::Are you suggesting that some users won't be able to visit any Russian Wikipedia pages (including [[:ru:Special:UserLogin]]?) unless the users are logged in when the page is accessed? --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 23:28, 17 September 2014 (UTC)
+:::I have no idea what plans Gryllida is talking about, but official plans are at [[mw:Wikimedia Engineering/2014-15 Goals#Site Operations and Site Architecture]].
+:::So far zh.wiki and others had an opt-out from the forced HTTPS for registered users but I seriously doubt there will be any opt-in mechanism for further HTTPS changes. --[[User:Nemo_bis|Nemo]] 06:06, 18 September 2014 (UTC)
+::::No, they don't plan access changes. [[:ru:Википедия:Форум/Архив/Предложения/2013/09#.D0.92.D0.BA.D0.BB.D1.8E.D1.87.D0.B5.D0.BD.D0.B8.D0.B5_.D0.BF.D1.80.D0.BE.D1.82.D0.BE.D0.BA.D0.BE.D0.BB.D0.B0_https_.D0.B4.D0.BB.D1.8F_.D0.B2.D1.81.D0.B5.D1.85_.D0.BF.D0.BE.D0.BB.D1.8C.D0.B7.D0.BE.D0.B2.D0.B0.D1.82.D0.B5.D0.BB.D0.B5.D0.B9|Local consensus]] at Russian Wikipedia. Oh, and they opted in [[HTTPS/Beta_program|here]]. [[User:Gryllida|Gryllida]] 09:09, 18 September 2014 (UTC)
+:: [[User:Gryllida|Gryllida]], Where did you find this date "October 2014", сan you give a link to us? [[User:Sunpriat|Sunpriat]] ([[User talk:Sunpriat|talk]]) 20:08, 26 September 2014 (UTC)
+
+== Russian Wikinews ==
+Please, let me know when you turn on HTTPS for [[n:ru:|Russian Wikinews]] ([https://meta.wikimedia.org/w/index.php?diff=9957749&oldid=5989231 diff]). --sasha ([[User:Krassotkin|krassotkin]]) 07:36, 22 September 2014 (UTC)
+* [https://ru.wikinews.org/w/index.php?diff=336990&oldid=336650 Done]. Thanks! --sasha ([[User:Krassotkin|krassotkin]]) 07:16, 5 December 2014 (UTC)
+
+== Performance impact ==
+
+Do performance issues with HTTPS show up in any way on navigation timing EventLogging logs like those from which [https://gdash.wikimedia.org/dashboards/frontend/] is extracted? Consider the case "the page takes so long to load over HTTPS that it times out in my browser" for people with extremely slow connections. It would be nice to be at least ''able'' to assess the impact on specific countries or Wikimedia subdomains, for instance. IIRC even the simple but often-quoted [https://docs.google.com/presentation/d/1MtDBNTH1g7CZzhwlJ1raEJagA8qM3uoV7ta6i66bO2M/present] mention this need for breakdown. --[[User:Nemo_bis|Nemo]] 13:25, 12 June 2015 (UTC)
+
+==Turning off HTTPS==
+This article's content states: "If so, you can turn off HTTPS in your user preferences (unless HSTS is set for the domain in question[2]). Go to the "User profile" tab, then uncheck the box labelled "Always use a secure connection when logged in". You will need to logout and login for the preference to take effect. But remember, you will still need to log in using HTTPS."  Up until today, I did not use HTTPS and was editing just fine.  Today, I am being forced to use HTTPS and there is nothing in the preferences screen for me to control this.  I don't want HTTPS (loss of saved edit summary info).  What can I do to get back to HTTP? [[User:Hmains|Hmains]] ([[User talk:Hmains|talk]]) 17:14, 12 June 2015 (UTC)
+:Sorry, that's entirely my fault for not keeping this page as up to date as I'd had hoped to. This is the answer I got when I asked was that any form of opt-out would also leave potential security risks in our implementation which make it difficult to safeguard those who do not opt-out.  Because of this, we’ve made implementation decisions that preclude any option to disable HTTPS, whether logged in or not.  This renders the current opt-out option ineffective, and the option will be removed at a later date after we’ve completed the transition process.
+:I'm trying to figure out if there's a good solution to the edit summary info problem. /[[User:Johan (WMF)|Johan (WMF)]] ([[User talk:Johan (WMF)|talk]]) 19:27, 12 June 2015 (UTC)
+::The edit summary issue - Users are reporting that the issue only affects IE versions prior to IE 11. One potential work around is to upgrade IE or use a different browser. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]])
+
+== Bots ==
+
+"API requests are now being forced redirected to HTTPS on some languages. On most bot frameworks, this should just work, but a few bot maintainers have reported problems. If your bot has problems, make sure that the library you are using supports HTTPS, and has access to appropriate root certificates."
+*How do you fix a library that doesn't support https to make it support that?
+*What are root certificates, and what do I need to do regarding that?
+*Why is this notice posted ''after'' implementation?
+*My library (see [[en:User:RMCD bot/botclasses.php]]) is something I got off of the now-defunct German tool server, and was written by guys who have all apparently retired from Wikipedia, so I guess I need to assume the job of maintaining it, though I'm not really sure that someone isn't still maintaining it somewhere.
+*I've been aware of this (potential) issue since last December: [[en:Wikipedia:Village pump (technical)/Archive 133#PHP API for #ifexist function?]] My [[en:special:diff/638797589|last question in that thread]] never got a response.
+[[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 12:26, 14 June 2015 (UTC)
+
+=== Help! My code is broken! ===
+"Are you a bot maintainer... and you're seeing weird or broken behavior after this switch?" '''YES.''' "Hopefully you can fix that easily." ''Still hoping. It's apparently not as easy as simply changing "http:" to "https:" in the code''
+
+For Gadget authors, simply modifying any hardcoded urls from "<nowiki>http://...</nowiki>" to "//..." should fix the issue (this is called using "protocol relative urls"). ''My bot logs me in if I use http:// Neither https:// nor // work to even do that.
+
+"For bot maintainers, you have a couple of choices."
+# login as the bot and select the preference to not use HTTPS for that account ('''citation needed''')
+# update your code to use SSL instead. ''Do you mean [[en:Secure Sockets Layer|Secure Sockets Layer]]? How do I update my code to use it?
+
+"If you use Pywikipediabot, please update to the latest version (More technical details: [https://gerrit.wikimedia.org/r/80003],[https://gerrit.wikimedia.org/r/80006]) and read [[mailarchive:pywikipedia-l/2013-August/008214.html|this]] mailing list post for more information."
+:I don't believe I use Pywikipediabot. Can't you do better than linking to ''code reviews'' for "more information"?
+What's the difference between a "Secure Sockets Layer" and a "[[en:root certificate|root certificate]]? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 13:53, 14 June 2015 (UTC)
+
+*'''Curiouser and curiouser'''. Legobot, which uses the [https://github.com/legoktm/harej-bots same botclasses.php] library, is still [https://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_comment/Biographies&action=history working]. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 16:56, 14 June 2015 (UTC)
+:There has been some divergence between versions of the botclasses.php library. See [[en:Wikipedia:Village pump (technical)#Impending bot armageddon]] for the console output from my program. Based on the prior conversation linked above, I switched my version to use JSON. I just copied Legobot's version into my system, and that errors differently:
+
+Logging in...<br>
+POST: http://en.wikipedia.org/w/api.php?action=login&format=php (1.2910737991333 s) (194 b)<br>
+POST: http://en.wikipedia.org/w/api.php?action=login&format=php (1.1130640506744 s) (253 b)
+...done.
+
+Checking for transclusions...
+
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.23901295661926 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.34102010726929 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.52202987670898 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.37602114677429 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.53903079032898 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.35002017021179 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.51002883911133 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.57503318786621 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.5550320148468 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.36001992225647 s) (0 b)<br>
+GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.36002087593079 s) (0 b)<br>
+
+Fatal error: Uncaught exception 'Exception' with message 'HTTP Error.' in C:\php\botclasses.php:214<br>
+Stack trace:<br>
+#0 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 10)
+#1 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 9)
+#2 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 8)
+#3 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 7)
+#4 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 6)
+#5 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 5)
+#6 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 4)
+#7 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 3)
+#8 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 2)
+#9 C:\php\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 1)
+#10 C:\php\botclasses.php(494): wikipedia->query('?action=query&l...')
+#11 C:\php\requestedmoves.php(53): wikipedia->getTransclusions in C:\php\botclasses.php on line 214
+
+<syntaxhighlight lang="php">
+    /**
+     * Sends a query to the api.
+     * @param $query string The query string.
+     * @param $post string POST data if its a post request (optional).
+     * @param $repeat int how many times we've repeated this request
+     * @return array The api result.
+     * @throws Exception on HTTP errors
+     **/
+    function query ($query,$post=null,$repeat=0) {
+	    global $AssumeHTTPFailuresAreJustTimeoutsAndShouldBeSuppressed;
+        if ($post==null) {
+            $ret = $this->http->get($this->url.$query);
+        } else {
+            $ret = $this->http->post($this->url.$query,$post);
+        }
+	    if ($this->http->http_code() == "504" && $AssumeHTTPFailuresAreJustTimeoutsAndShouldBeSuppressed) {
+			return array(); // Meh
+	    }
+		if ($this->http->http_code() != "200") {
+			if ($repeat < 10) {
+				return $this->query($query,$post,++$repeat);
+			} else {
+				throw new Exception("HTTP Error.");    // this is line 214
+			}
+		}
+        return unserialize($ret);
+    }
+</syntaxhighlight>
+I don't know whether this would make any difference, but unlike most other bots, mine run under the Windows 7 operating system. -- [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:40, 14 June 2015 (UTC)
+
+It runs under [[en:Windows PowerShell|Windows PowerShell]]. I'm wondering whether I need to do anything special to enable HTTPS under PowerShell. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:55, 14 June 2015 (UTC)
+:'''BINGO!''' - this seems helpful: [https://github.com/AppVeyor/AppRolla/wiki/Configuring-Windows-PowerShell-remoting Enabling HTTPS protocol for PowerShell remoting] [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 19:07, 14 June 2015 (UTC)
+::...but complicated. Buy an SSL certificate? Generate my own?? Help! [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 19:19, 14 June 2015 (UTC)
+
+Sigh, it's awful quiet here today. Why was this implemented just before a weekend? So this is my current understanding (I have limited confidence in its accuracy). The library I'm using does not support HTTPS. It works for Legobot because that bot is on a "framework" (UNIX?) that supports HTTPS. I can either update my library code to support HTTPS, or update my Windows PowerShell "framework" to support HTTPS. I have no idea which is the easier approach. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 21:34, 14 June 2015 (UTC)
+
+That code you linked to does not support a redirect (HTTP status/code 301) which is what you get when you try to request a HTTP:// URL instead of HTTPS:// . Perhaps it works for you when you change the URLs you use with your bot from HTTP:// to HTTPS:// which is what I assume Legobot does. - [[User:JanZerebecki|Jan Zerebecki]] 11:00, 15 June 2015 (UTC)
+:My guess is that [[en:User:Legobot|Legobot]] works because the ''platform'' it runs on, the "Wikimedia Labs cluster" or whatever it's called these days, supports "301 redirects". I have copied and tried to run the identical code on my platform, Windows PowerShell, without success. Note, however, that despite claims that now absolutely no HTTP works anymore, the Logging in... POST: request (in the example above) still ''works'' for me. If I change that to try to login using HTTPS:, it does ''not'' work! [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 12:42, 15 June 2015 (UTC)
+::How does logging in via https fail? Can you post debug / log output? - [[User:JanZerebecki|Jan Zerebecki]] 13:31, 15 June 2015 (UTC)
+I just see in my console output:
+<syntaxhighlight lang="text">
+Logging in...
+POST: https://en.wikipedia.org/w/api.php?action=login&format=json (0.82604718208313 s) (0 b)
+Login error: 
+</syntaxhighlight>
+I guess I should see if I can write more diagnostic information to the console. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 15:20, 15 June 2015 (UTC)
+<syntaxhighlight lang="php">
+ /**
+     * This function takes a username and password and logs you into wikipedia.
+     * @param $user Username to login as.
+     * @param $pass Password that corrisponds to the username.
+     * @return array
+     **/
+    function login ($user,$pass) {
+    	$post = array('lgname' => $user, 'lgpassword' => $pass);
+        $ret = $this->query('?action=login&format=json',$post);
+        /* This is now required - see http://bugzilla.wikimedia.org/show_bug.cgi?id=23076 */
+        if ($ret['login']['result'] == 'NeedToken') {
+        	$post['lgtoken'] = $ret['login']['token'];
+        	$ret = $this->query( '?action=login&format=json', $post );
+        }
+        if ($ret['login']['result'] != 'Success') {
+            echo "Login error: \n";
+            print_r($ret);
+            die();
+        } else {
+            return $ret;
+        }
+    }
+</syntaxhighlight>
+So my 'login' 'result' != 'Success' and $ret seems to be null as nothing prints -- [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 15:32, 15 June 2015 (UTC)
+
+I printed out what it should look like when it works, which it does when I simple edit to remove the single character "s"
+<syntaxhighlight lang="text">
+Logging in...
+POST: http://en.wikipedia.org/w/api.php?action=login&format=json (0.86704897880554 s) (146 b)
+POST: http://en.wikipedia.org/w/api.php?action=login&format=json (1.4270820617676 s) (190 b)
+Array
+(
+    [login] => Array
+        (
+            [result] => Success
+            [lguserid] => 17216044
+            [lgusername] => RMCD bot
+            [lgtoken] => bd5ea22dde5601241c9a1da1eeedb5f5
+            [cookieprefix] => enwiki
+            [sessionid] => 324aa437fffa48afd8c7ac6db4754a7f
+        )
+
+)
+...done.
+</syntaxhighlight>
+Hopefully no beans spilled here. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 15:56, 15 June 2015 (UTC)
+
+Th sessionid and token are secrets. You should logout with that sessionid to make it invalid.
+
+Perhaps on your PHP installation the openssl extension is not enabled ( http://de2.php.net/manual/en/book.openssl.php ). You could try to run the following as a php script to test if a normal https request works:
+<syntaxhighlight lang="php">error_reporting(-1); var_dump(file_get_contents("https://en.wikipedia.org/wiki/Main_Page"));</syntaxhighlight>
+- [[User:JanZerebecki|Jan Zerebecki]] 16:06, 15 June 2015 (UTC)
+:I see. My bot logs in every 15 minutes, and each time it logs in it gets a new sessionid. I just changed my pw so now I have a new token.
+:Well, of course I don't have the openssl extension installed. I just have a minimum, bare-bones php installation, just what is needed to run my bots and nothing more. I will get right on installing http://www.openssl.org/
+:Nothing on the help page [[HTTPS]] says I needed to do that!! [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 16:40, 15 June 2015 (UTC)
+: So [http://www.openssl.org/source/ here], do I just need to get the one marked "[LATEST]", or do I need to get more than one of these? It's not clear on that page what I need to do. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:01, 15 June 2015 (UTC)
+: [http://www.openssl.org/support/faq.html#MISC2 The INSTALL file explains how to install this library.] Where is the "INSTALL file"? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:07, 15 June 2015 (UTC)
+: I guess I need to install WinZip to open up that GNU Zipped Archive file. What a user-unfriendly pain. I clicked the wrong button and it started zipping up every file on my machine. I had WinZip on an older machine of mine, seems that the newer software gets, the more cumbersome it gets. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:38, 15 June 2015 (UTC)
+::OK, my 21-day trial version has unpacked the .gz file, and fortunately it only was zipping up my old downloads, so I can probably just recycle-bin them. Now I have found the INSTALL.W64 file:
+<syntaxhighlight lang="text">
+INSTALLATION ON THE WIN64 PLATFORM
+ ----------------------------------
+
+ Caveat lector
+ -------------
+
+ As of moment of this writing Win64 support is classified "initial"
+ for the following reasons.
+
+ - No assembler modules are engaged upon initial 0.9.8 release.
+ - API might change within 0.9.8 life-span, *but* in a manner which
+   doesn't break backward binary compatibility. Or in other words,
+   application programs compiled with initial 0.9.8 headers will
+   be expected to work with future minor release .DLL without need
+   to re-compile, even if future minor release features modified API.
+ - Above mentioned API modifications have everything to do with
+   elimination of a number of limitations, which are normally
+   considered inherent to 32-bit platforms. Which in turn is why they
+   are treated as limitations on 64-bit platform such as Win64:-)
+   The current list comprises [but not necessarily limited to]:
+
+   - null-terminated strings may not be longer than 2G-1 bytes,
+     longer strings are treated as zero-length;
+   - dynamically and *internally* allocated chunks can't be larger
+     than 2G-1 bytes;
+   - inability to encrypt/decrypt chunks of data larger than 4GB
+     [it's possibly to *hash* chunks of arbitrary size through];
+
+   Neither of these is actually big deal and hardly encountered
+   in real-life applications.
+
+ Compiling procedure
+ -------------------
+
+ You will need Perl. You can run under Cygwin or you can download
+ ActiveState Perl from http://www.activestate.com/ActivePerl.
+
+ You will need Microsoft Platform SDK, available for download at
+ http://www.microsoft.com/msdownload/platformsdk/sdkupdate/. As per
+ April 2005 Platform SDK is equipped with Win64 compilers, as well
+ as assemblers, but it might change in the future.
+
+ To build for Win64/x64:
+
+ > perl Configure VC-WIN64A
+ > ms\do_win64a
+ > nmake -f ms\ntdll.mak
+ > cd out32dll
+ > ..\ms\test
+
+ To build for Win64/IA64:
+
+ > perl Configure VC-WIN64I
+ > ms\do_win64i
+ > nmake -f ms\ntdll.mak
+ > cd out32dll
+ > ..\ms\test
+
+ Naturally test-suite itself has to be executed on the target platform.
+
+ Installation
+ ------------
+
+ TBD, for now see INSTALL.W32.
+</syntaxhighlight>
+
+Sigh. Now I need to install Perl and Microsoft Platform SDK, then ''pray''. I'm not feeling good about this. Do I ''need'' to do all this to get it to work? Is there another way? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:39, 15 June 2015 (UTC)
+
+'''!''' [http://de2.php.net/manual/en/openssl.requirements.php Requirements] - for windows it might be better to just get the setup at http://gnuwin32.sourceforge.net/packages/openssl.htm
+
+instead of the sources and try to compile 'em yourself ^_~
+Thanks, poo flanders! I should have noticed that before! [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 19:37, 15 June 2015 (UTC)
+
+I heard that you only need to enable the extension, and that the Windows version of PHP already comes with everything needed for that, but I never tried it. - [[User:JanZerebecki|Jan Zerebecki]] 19:54, 15 June 2015 (UTC)
+
+:{{ping|Wbm1058}}: To unzip gzip files on windows, use the program 7zip. SSL and TLS are alternative names for HTTPS (technically that's lieing slightly, but its close enough for this conversation). Don't worry about root certificate store for now. I recommend against trying to compile php from scratch and link OpenSSL to it (I think that's what you are trying to do above). That's a really complicated way of doing it. The reason why other people's bots work and yours don't is probably because you're running windows, and php on windows is a bit iffy in what extensions it default installs.
+:Now for what you need to do, per http://php.net/manual/en/wrappers.http.php (I'm assuming your bot uses php's f_open wrappers to do its communication) you need the openssl extension installed, and at least php version 4.3. You need to enable the OpenSSL php extension (See http://www.herongyang.com/PKI/HTTPS-PHP-Configure-PHP-OpenSSL-on-Windows.html for some instructions). PHP also needs to have access to the libeay32.dll file. This should come with php, but may be in the wrong directory. http://php.net/manual/en/install.windows.extensions.php#install.windows.extensions.overview and http://php.net/manual/en/openssl.installation.php may also be helpful links. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 20:39, 15 June 2015 (UTC)
+::Hi, nice to see someone else join the party. My library source is at [[en:User:RMCD bot/botclasses.php]]. I see two fopen calls there, but both are commented out. Others wrote this, and I have only a limited understanding of how it works. It looks like it uses the [http://de2.php.net/manual/en/book.curl.php Client URL library]. I trust that can work under HTTPS. Some of your links are interesting; I'm reading more on those sites to see if I can gain more insight. Thanks, [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 21:45, 15 June 2015 (UTC)
+::Yes indeed, it claims to support HTTPS, and php_curl.dll is part of my installation. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 21:54, 15 June 2015 (UTC)
+::Oh yes, libeay32.dll is also required by php_curl.dll so I have that installed already. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 22:10, 15 June 2015 (UTC)
+
+'''Good news''': [http://www.herongyang.com/PKI/HTTPS-PHP-Test-OpenSSL-with-file_get_contents.html This test] to connect the yahoo login HTTPS server was successful!<br>
+'''Bad news''': I still get the '''Login error:''' as shown above, with (0 b) - zero bytes - returned. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 22:49, 15 June 2015 (UTC)
+:So there's two ways to make connections on PHP - fopen, or curl. Looks like you're using Curl. Most of my comment above was assuming fopen. http://stackoverflow.com/questions/316099/cant-connect-to-https-site-using-curl-returns-0-length-content-instead-what-c might be helpful to you. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]])
+::Thanks! Very helpful! Now I feel like the solution is in sight... I wonder why they commented out the curl_error lines? After activating them, I see:
+::'''Error: SSL certificate problem: unable to get local issuer certificate''' [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 00:29, 16 June 2015 (UTC)
+::This seems helpful: [https://web.archive.org/web/20190517065614/http://support.gnip.com/articles/curl-on-win7.html cURL on Windows]. I never did anything special before to install cURL, I've just used what came with PHP (in fact, I didn't realize until now that it was a separate package). [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 00:45, 16 June 2015 (UTC)
+
+===Root certificate issue===
+:::(This is the root certificate problem we were talking about earlier). You need to download http://curl.haxx.se/ca/cacert.pem , put it somewhere on your computer, then set <code>curl.cainfo=c:\php\cacert.pem</code> (replace c:\php\cacert.pem with where ever you saved the file) in your php.ini config file. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 04:31, 16 June 2015 (UTC)
+::::'''Q.''' Why did the site I linked above tell me to "Rename this file from cacert.pem to curl-ca-bundle.crt"? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 11:35, 16 June 2015 (UTC)
+::::'''A.''' I see, per http://curl.haxx.se/docs/sslcerts.html
+:::::If you're using the curl command line tool, you can specify your own CA cert path by setting the environment variable CURL_CA_BUNDLE to the path of your choice.
+
+:::::If you're using the curl command line tool on Windows, curl will search for a CA cert file named "curl-ca-bundle.crt" in these directories and in this order:
+
+:::::#application's directory
+:::::#current working directory
+:::::#Windows System directory (e.g. C:\windows\system32)
+:::::#Windows Directory (e.g. C:\windows)
+:::::#all directories along %PATH%
+::::-- [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 11:46, 16 June 2015 (UTC)
+
+'''OK'''. The instructions at [https://web.archive.org/web/20190517065614/http://support.gnip.com/articles/curl-on-win7.html cURL on Windows] moved me forward towards reviving my bot, though I'm not sure all of that was necessary for my application. However, I got to the instruction "Note that if you can not get cURL SSL enabled, you have the option to run cURL in an insecure mode" and I was still getting the same error. So I punted with help I found [http://stackoverflow.com/questions/24611640/curl-60-ssl-certificate-unable-to-get-local-issuer-certificate here], and solved this problem by adding one line of code <code>curl_setopt($this->ch, CURLOPT_SSL_VERIFYPEER, false);</code> which "helped to circumvent the problem, but totally missed the idea of https and the certification system". But I was able to sleep knowing that my bots were finally running again. Upon returning here, I found the missing piece waiting for me, commented out my "CURLOPT_SSL_VERIFYPEER → false" band-aid, and added <code>curl.cainfo=c:\php\curl-ca-bundle.crt</code> to my php.ini config file. So everything is happy now, and all that remains is for me to clean up, and update my [[en:User:RMCD bot/botclasses.php|online copy of the library]].
+
+Now I see that the setup at http://gnuwin32.sourceforge.net/packages/openssl.htm is way out of date, and for that reason I probably shouldn't have installed it. I picked one of the "Light" packages from [http://slproweb.com/products/Win32OpenSSL.html this site] (didn't really know which was best) and installed it as well, but I don't know if that was necessary either, or something already bundled in PHP.
+
+One trick to "downloading" the certificate file. All the places I've seen it just have it as a plain-text file that displays in the web browser. I haven't seen any places where you can just download it by clicking a button. I resorted to cut & paste into Notepad. Is there an easier way? When saving it you need to be careful not to save it as "curl-ca-bundle.crt.txt" -- when it's correctly saved, Windows recognizes it as a "Security Certificate" file type. Looking at the "properties" of the .crt file, I see that it opens with "Crypto Shell Extensions". There is also an option to "Install Certificate", which opens the "Certificate Import Wizard" which allows me to import the certificate to a "certificate store" which is automatically determined by the wizard. Apparently it isn't necessary to import it to a store. I see that the certificate is issued to and by Equifax Secure Certificate Authority, and is valid to 8/22/2018.
+
+One remaining question: It seems that the "Bundle of CA Root Certificates" is periodically updated. Will I be required to update this at some point in the future, and if so, how will I know when it's needed? What will happen if I don't update it in time? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:35, 16 June 2015 (UTC)
+:Probably not. Only if Wikimedia changes CA's to something currently not in the root certs. That sort of thing doesn't happen very often (Although it does happen). The current root certificate should have been in the bundle for about 7 years now. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 03:19, 18 June 2015 (UTC)
+::Do the [https://hexatomium.github.io/2015/06/26/ms-very-quietly-adds-18-new-trusted-root-certs/ changes to Windows root certificates] change anything for us? --[[User:Nemo_bis|Nemo]] 19:53, 27 June 2015 (UTC)
+:::No, it only matters (in terms of accessing Wikimedia websites) if either we change our root certificate at some point, which is unlikely in the near future (Or if MS for some reason decided to remove the GlobalSign Root CA cert that we use, but that would be extremely unlikely anytime soon). Although Microsoft's behaviour there is kind of odd... [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 11:09, 1 July 2015 (UTC)
+
+re: "{{tq|I see that the certificate is issued to and by Equifax Secure Certificate Authority, and is valid to 8/22/2018.}}" -- that's just the first of many certificates in the bundle that Windows shows you. After editing the bundle with Notepad to remove that expired certificate, Windows showed me the next certificate in the bundle, which hasn't expired yet: issued to and by GlobalSign Root CA, valid from 9/1/1998 to 1/28/2028 [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 01:42, 2 October 2021 (UTC)
+
+=== Updating from PHP version 7.0.12 to 7.0.28 ===
+{{collapse top|PHP problem solved}}
+I'm trying to upgrade from the version I successfully installed in October 2016 using the configuration described in the sections above. I wasn't expecting to run into any major roadblocks as I'm just trying to update for the latest bug and security fixes, and not to the next major release 7.1 or 7.2, but I've run into something I can't figure out.
+
+Version 7.0.12 has been successfully running in production since 10/2016. Here is what phpinfo() configuration information tells me:
+<syntaxhighlight lang="text">curl
+
+cURL support => enabled
+cURL Information => 7.50.3
+Age => 3
+Features
+AsynchDNS => Yes
+CharConv => No
+Debug => No
+GSS-Negotiate => No
+IDN => Yes
+IPv6 => Yes
+krb4 => No
+Largefile => Yes
+libz => Yes
+NTLM => Yes
+NTLMWB => No
+SPNEGO => Yes
+SSL => Yes
+SSPI => Yes
+TLS-SRP => No
+HTTP2 => No
+GSSAPI => No
+KERBEROS5 => Yes
+UNIX_SOCKETS => No
+PSL => No
+Protocols => dict, file, ftp, ftps, gopher, http, https, imap, imaps, ldap, pop3, pop3s, rtsp, scp, sftp, smtp, smtps, telnet, tftp
+Host => i386-pc-win32
+SSL Version => OpenSSL/1.0.2j
+ZLib Version => 1.2.8
+libSSH Version => libssh2/1.7.0</syntaxhighlight>
+
+When I tried to update to the current version 7.0.28 by simply overwriting files I saw:
+<syntaxhighlight lang="text">Warning: PHP Startup: Unable to load dynamic library 'c:/php/ext\php_curl.dll' - The specified module could not be found.
+ in Unknown on line 0</syntaxhighlight>
+
+The mix of linux and windows slashes was a giveaway that v 7.0.12 doesn't seem to need to load php_curl.dll but 7.0.28 now needs that.
+
+So I fixed my php.ini but that just gave me:
+<syntaxhighlight lang="text">Warning: PHP Startup: Unable to load dynamic library 'c:\php\ext\php_curl.dll' - The specified module could not be found.
+ in Unknown on line 0</syntaxhighlight>
+
+That file ''is'' found in that directory, so it's a kind of spurious / uninformative error message.
+
+Per the comments on [http://php.net/manual/en/function.curl-version.php the curl_version documentation page] I disabled the "openssl" extension in php.ini and confirmed that PHP v 7.0.12 and my application work fine without it. PHP cURL has nothing to do with that separated openssl extension but it has its own openssl.
+
+Perhaps I'm missing a dll file, as described in the [http://php.net/manual/en/curl.installation.php comments here three are needed] but I have all of those.
+
+Or are either my curl.exe or curl-ca-bundle.crt Security Certificate from June 2015 incompatible with PHP 7.0.28? They were still compatible with v 7.0.12 when I updated to that in October 2016.
+
+Help, please. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 15:36, 14 March 2018 (UTC)
+
+SO I tried just retroactively updating from 7.0.12 to 7.0.13 ...
+<syntaxhighlight lang="text">curl
+
+cURL support => enabled
+cURL Information => 7.51.0
+Age => 3
+Features
+AsynchDNS => Yes
+CharConv => No
+Debug => No
+GSS-Negotiate => No
+IDN => Yes
+IPv6 => Yes
+krb4 => No
+Largefile => Yes
+libz => Yes
+NTLM => Yes
+NTLMWB => No
+SPNEGO => Yes
+SSL => Yes
+SSPI => Yes
+TLS-SRP => No
+HTTP2 => No
+GSSAPI => No
+KERBEROS5 => Yes
+UNIX_SOCKETS => No
+PSL => No
+Protocols => dict, file, ftp, ftps, gopher, http, https, imap, imaps, ldap, pop3, pop3s, rtsp, scp, sftp, smtp, smtps, telnet, tftp
+Host => i386-pc-win32
+SSL Version => OpenSSL/1.0.2j
+ZLib Version => 1.2.8
+libSSH Version => libssh2/1.8.0</syntaxhighlight>
+
+Sometime between versions <s>7.0.14</s> 7.0.18 and <s>7.0.28</s> 7.0.21 some breaking change was introduced, and it's a bear to find any documentation of what that change was and how to fix installations to work with it. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 16:58, 14 March 2018 (UTC)
+: binary searching for the culprit ;) [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:22, 14 March 2018 (UTC) narrowing in on it... [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:39, 14 March 2018 (UTC)
+: 7.0.18 is the last one that works out-of-the-box; [http://php.net/ChangeLog-7.php#7.0.19 7.0.19] introduced some sort of change requiring a change in configuration.
+: Added OpenSSL 1.1.0 support.
+Version 7.0.18:
+<syntaxhighlight lang="text">curl
+
+cURL support => enabled
+cURL Information => 7.51.0
+Age => 3
+Features
+AsynchDNS => Yes
+CharConv => No
+Debug => No
+GSS-Negotiate => No
+IDN => Yes
+IPv6 => Yes
+krb4 => No
+Largefile => Yes
+libz => Yes
+NTLM => Yes
+NTLMWB => No
+SPNEGO => Yes
+SSL => Yes
+SSPI => Yes
+TLS-SRP => No
+HTTP2 => No
+GSSAPI => No
+KERBEROS5 => Yes
+UNIX_SOCKETS => No
+PSL => No
+Protocols => dict, file, ftp, ftps, gopher, http, https, imap, imaps, ldap, pop3, pop3s, rtsp, scp, sftp, smtp, smtps, telnet, tftp
+Host => i386-pc-win32
+SSL Version => OpenSSL/1.0.2k
+ZLib Version => 1.2.8
+libSSH Version => libssh2/1.8.0</syntaxhighlight> [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:21, 14 March 2018 (UTC)
+: [http://php.net/manual/en/openssl.requirements.php Requirements] "You are strongly encouraged to use the most recent OpenSSL version, otherwise your web server could be vulnerable to attack."
+: 0.9.8 is a minimal version for PHP 7.0. Other versions (PHP >= 7.1.0) require OpenSSL >= 1.0.1. -- [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:52, 14 March 2018 (UTC)
+
+So I compared php-7.0.18-nts-Win32-VC14-x86 and php-7.0.19-nts-Win32-VC14-x86 and found that the former had 37 items, while the latter has 38. Bingo! The new file added to the package is nghttp2.dll -- so now there is a fourth DLL to be added to the \php directory. Relatively few sites including this one as most discussions on this are stale, but I found one that mentions the latest DLL addition in the [https://superuser.com/questions/1201346/apache-and-php-curl-issue answer dated 31-October-2017]. It would be too easy if the spurious error message were actually truthful, and said:
+<syntaxhighlight lang="text">Warning: PHP Startup: Unable to load dynamic library 'c:\php\nghttp2.dll' - The specified module could not be found.</syntaxhighlight>
+Of course no mention of the addition of this new file in the release notes. Sigh. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 00:24, 15 March 2018 (UTC)
+: Your problems here seem to have nothing to do with MediaWiki. You should probably seek a help forum for PHP on Windows. [[User:Anomie|Anomie]] ([[User talk:Anomie|talk]]) 14:23, 16 March 2018 (UTC)
+:: Right, I solved this by myself. I could complain somewhere that their documentation of changes could be better, but I don't know where. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 21:14, 20 March 2018 (UTC)
+{{collapse bottom}}
+
+== HTTPS timeout with curl and wget ==
+
+Running these commands:
+
+*curl -s --trace o "https://en.wikipedia.org/wiki/Charlies"
+*wget -q -O- "https://en.wikipedia.org/wiki/Charlies"
+
+Results in intermittent timeouts as reported by the debug feature of both programs. It might work 3 times in a row then hang on the 4th etc..
+
+Traceroute shows I am located 10 hops from 208.80.154.224 in Virginia with a 6ms ping time with no dropped packets. I'm on Verizon FIOS. 
+
+Problem started the same time HTTPS was implemented. 
+
+curl debug (curl -s --trace o "https://en.wikipedia.org/wiki/Charlies"):
+ == Info: timeout on name lookup is not supported
+ == Info: About to connect() to en.wikipedia.org port 443 (#0)
+ == Info:   Trying 208.80.154.224...
+ == Info: Timed out
+ == Info: couldn't connect to host
+ == Info: Closing connection #0
+
+wget debug (wget -d -q -O- "https://en.wikipedia.org/wiki/Charlies"):
+ Setting --quiet (quiet) to 1
+ Setting --output-document (outputdocument) to -
+ DEBUG output created by Wget 1.16.3 on cygwin.
+ URI encoding = ‘UTF-8’
+ Certificates loaded: 170
+ Caching en.wikipedia.org => 208.80.154.224 2620:0:861:ed1a::1  <-- note: hangs here
+ Closed fd 4
+ Closed fd 4
+ Releasing 0x800ce0c0 (new refcount 1).
+
+-- [[User:Green Cardamom|Green Cardamom]] ([[User talk:Green Cardamom|talk]]) 14:49, 17 June 2015 (UTC)
+
+::In case anyone has similar timeout problems, I've worked around it with this:
+::: wget --retry-connrefused --waitretry=1 --read-timeout=2 --timeout=2 --no-dns-cache -q -O- "https://en.wikipedia.org/wiki/Charlies"
+::This is working. Might need to adjust the 2 second delay depending on your connection speed. If there is no response within 2 seconds (--timeout) It will retry 20 times .. but usually succeeds after the first retry. -- [[User:Green Cardamom|Green Cardamom]] ([[User talk:Green Cardamom|talk]]) 15:12, 17 June 2015 (UTC)
+:::Ping: [[User:BBlack (WMF)]]. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 03:25, 18 June 2015 (UTC)
+::::I don't think we're seeing this behavior in the general case (stats haven't shown it, and I can't reproduce it -- tried from a few places around the net over both v4 and v6).  If this wasn't a transient issue local to you that has since vanished, can you hop on our freenode #wikimedia-operations [https://meta.wikimedia.org/wiki/IRC/Channels IRC channel] to debug with us at some point? [[User:BBlack (WMF)|BBlack (WMF)]] ([[User talk:BBlack (WMF)|talk]]) 12:10, 18 June 2015 (UTC)
+:::: Ping: [[User:Green Cardamom]] ^
+:::: [[User:BBlack (WMF)|BBlack (WMF)]], it's working OK right now. I'll keep trying and if it starts happening again I'll get on IRC. Thanks. -- [[User:Green Cardamom|Green Cardamom]] ([[User talk:Green Cardamom|talk]]) 22:28, 18 June 2015 (UTC)
+
+== Yes indeed, My code is broken! ==
+
+
+<br>
+I have written communication programs to fetch data from Wikipedia and the dictionarys.<br>
+(this was done in an environment that is called Caché or MUMPS: http://www.intersystems.com/our-products/cache/cache-overview)<br>
+I made them in order to have the possibility to check the contents on errors and much more.
+<br><br>
+Unfortunately they do not work anymore.
+
+Somebody made the following statement:
+For bot maintainers, you have a couple of choices. Either login as the bot and select the preference to not use HTTPS for that account, or update your code to use SSL instead.<br>
+How do I realise the preference to not use HTTPS for an account?
+
+Untill now I have tried a lot to fix it but I did not succeed...
+
+Saludos,
+
+--[[User:Kvdrgeus|Kvdrgeus]] ([[User talk:Kvdrgeus|talk]]) 07:16, 21 June 2015 (UTC)
+
+:Disabling HTTPS is not possible anymore. Your only option is to fix it to work with HTTPS in some way. - [[User:JanZerebecki|Jan Zerebecki]] 10:23, 21 June 2015 (UTC)
+::Hi [[User:Kvdrgeus|Kvdrgeus]], the bot problems are noted, I hope to be able to put together some relevant information specifically for this. Due to security concerns, we haven't been able to leave the option of opting out open. See [[:en:special:diff/666682303|here]] for a technical explanation. /[[User:Johan (WMF)|Johan (WMF)]] ([[User talk:Johan (WMF)|talk]]) 13:44, 22 June 2015 (UTC)
+
+I finally did succeed in adapting the communication routines to the new TLS-protocols
+so this problem has been solved...
+
+--[[User:Kvdrgeus|Kvdrgeus]] ([[User talk:Kvdrgeus|talk]]) 12:43, 26 June 2015 (UTC)
+:Excellent, I'm glad to hear that. /[[User:Johan (WMF)|Johan (WMF)]] ([[User talk:Johan (WMF)|talk]]) 08:45, 1 July 2015 (UTC)
diff --git a/src/helper_scripts/repo_collection.py b/src/helper_scripts/repo_collection.py
index 6b8bb48..8c0cac4 100644
--- a/src/helper_scripts/repo_collection.py
+++ b/src/helper_scripts/repo_collection.py
@@ -10,8 +10,8 @@ repo_location = "/data/users/mgaughan/mw-repo-lifecycles/repo_artifacts/"
 cst = datetime.timezone(datetime.timedelta(hours=-6))
 
 repos = {
-        "wmf_config" : {
-            "url": "https://gerrit.wikimedia.org/r/operations/mediawiki-config",
+        "extensions_visualeditor" : {
+            "url": "https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor",
             "from_date": datetime.datetime(2010, 1, 1, 00, 00, 00, tzinfo=cst),
             "to_date": datetime.datetime(2024, 12, 31, 00, 00, 00, tzinfo=cst)
             },
diff --git a/src/lib/https-talk-page.json b/src/lib/https-talk-page.json
new file mode 100644
index 0000000..d5a50ec
--- /dev/null
+++ b/src/lib/https-talk-page.json
@@ -0,0 +1,2703 @@
+{
+    "sections": [
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Organisation of the content page ==\n",
+                        "Here are the thoughts which drived my writing/expansion of the content page.\n",
+                        "\n",
+                        "I follow wikitech-l and wikitech-ambassadors since many years (less for the latter :) and I have difficulties to track the various topics. I\u2019m interested in the HTTPS topic and  I find both the technical and community people should be involved in this question, hence a job for a wikitech ambassador.\n",
+                        "\n",
+                        "I find this page should be a portal/hub -- still better it is presently -- explaining the general topic, the various questions involved (better than only the keywords presently), the past and coming deployments, and a collection of pointers about the state of the discussion (wikitech-l and bugzilla mainly for this topic).\n",
+                        "\n",
+                        "Any thoughts about this organisation?<br />\n",
+                        "(Perhaps we can use this section -- with subsections -- to discuss specifically about the organisation, and let the other sections about true HTTPS questions.)<br />\n",
+                        "~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 09:34, 18 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ": [[w:en:WP:BOLD|Be bold]]. :-)  --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 16:40, 18 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "MZMcBride",
+                            "time_stamp": "16:40, 18 August 2013 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ": Hi Seb35. Thanks for the dump. I am a little concerned, though, that people who are pointed to this page due to the planned Wednesday deploy of SecureLogin by default won't know where to begin; it's a little text heavy without much \"what is going on, what this means for you\" in simple and brief language. I hope you don't mind, but I'm going to [[w:en:WP:BOLD|Be bold]] and drastically rearrange this page to address the most common questions and conerns from users who are having problems with HTTPS. I'm going to keep much of what you wrote, just re-arrange, mostly. Thanks again! [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 22:49, 19 August 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::Hi, thanks a lot for the rewritting, it\u2019s better now with these simple explanations. I removed my paragraph about PRISM since you better summarised it in the introduction; I hesitated about adding a link, but it could distract the reader. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 12:14, 20 August 2013 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Seb35|<small>[^_^]<",
+                                    "time_stamp": "12:14, 20 August 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Greg (WMF)",
+                            "time_stamp": "22:49, 19 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Seb35|<small>[^_^]<",
+                    "time_stamp": "09:34, 18 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Organisation of the content page "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Soft HSTS (HTTP Strict-Transport-Security) ==\n",
+                        "\n",
+                        "I wrote [[:mw:Extension:HSTS|an extension]] for MediaWiki to enable [[:en:HTTP Strict-Transport-Security|HSTS]] on a per-user basis. The rationale behind is to let the privacy-conscious users to opt-in to HTTPS-everytime (for all compatible browsers) independently of their current connected or unconnected status, and at the same time not force the other users to use HTTPS (particularly if they use to live in a HTTPS-unfriendly environment as the China).\n",
+                        "\n",
+                        "I find such an extension would be worth to be installed on the Wikimedia projects (in the first times on the test wikis and then the MediaWiki wiki) to balance between the advantages and drawbacks of HTTPS, as well as slowly increase the HTTPS load of the servers. HSTS coming with a high constraint (fatal error in case of bad TLS/HTTPS connection), I find it could be tested with increasing expiration times (1 hour; 1 day; 2 weeks; 1 month) with some volunteers during the next year to test if all works correctly (e.g. the users will obligatorily complain if their old browser\u2019s cipher suite or SSL 3.0 is removed).\n",
+                        "\n",
+                        "~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 17:03, 18 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":I misunderstood the deployment planned for August 21, 2013; I thought it was only the log-in page. This extension becomes almost useless if all HTTP traffic is 301-redirected to HTTPS, or it could be tweaked to remove the user preference and be activated for all logged-in users in order to remove the 301-redirect-over-HTTP step which can still be MITMed/spied. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 18:18, 18 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "18:18, 18 August 2013 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ":And the extension is now updated to give the server administrator the possibility to force anonymous and/or logged-in users to have a STS header, or to let the logged-in users choose if they want one. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 20:06, 18 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "20:06, 18 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Seb35|<small>[^_^]<",
+                    "time_stamp": "17:03, 18 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Soft HSTS (HTTP Strict-Transport-Security) "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Load script from home wiki ==\n",
+                        "\n",
+                        "En.wiki is my homewiki, and in all other projects I have this in my vector.js:<br /><code>mw.loader.load( '//en.wikipedia.org/w/index.php?title=User:Edokter/MenuTabsToggle.js&action=raw&ctype=text/javascript' );</code>\n",
+                        "\n",
+                        "This fails in modern browsers as a XSS-violation when in HTTPS. Are there any provisions where the several Wikimedia domains are trusted with regard to eachother? <span style=\"font-family:'Trebuchet MS'\"> \u2014 [[User:Edokter|<span style=\"color:#008\"><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style=\"color:#080\">talk</span>]]) \u2014 </span> 09:56, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "\n",
+                                ":I don\u2019t know well XSS, but this syntax works for me (Opera 12.16, I have it in my en.wp common.js). Else I see on [[:mw:ResourceLoader/Migration guide (users)#Migrating user scripts]] it is recommanded to keep importScript instead of switching to mw.loader to avoid problems; perhaps you can try with importScript. Else what browser+version do you have? ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 12:41, 20 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "12:41, 20 August 2013 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ": I see [[:en:User:Edokter/MenuTabsToggle.js]] itself calls <code>mw.loader.load</code> with 'http' explicitly specified, and Firefox 23.0 here complains about the mixed content due to that. Try making that protocol-relative as well? [[User:Anomie|Anomie]] ([[User talk:Anomie|talk]]) 13:47, 20 August 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "\n",
+                                        "::A bug in Chrome (or was it IE?) prevents use of protocol-relative stylesheets in the .load method. XSS stands for 'Cross-site scripting'. Most moders browsers block loading scripts form another domain when you are on a secure connection. The only way to allow secure cross-site scripts to load is by whitelisting those domains in the certificate. That is what my question partains to: does our certificate has such a whitelist? <span style=\"font-family:'Trebuchet MS'\"> \u2014 [[User:Edokter|<span style=\"color:#008\"><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style=\"color:#080\">talk</span>]]) \u2014 </span> 20:47, 20 August 2013 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                ":::Independently of XSS, about the HTTP/HTTPS in the scripts and problems with protocol-relative, you can use some script like\n",
+                                                ":::<syntaxhighlight lang=\"javascript\">mw.loader.load( window.location.protocol+'//en.wikipedia.org/w/...' );</syntaxhighlight>\n",
+                                                ":::([https://developer.mozilla.org/en-US/docs/Web/API/window.location ref]) ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 22:03, 20 August 2013 (UTC)\n"
+                                            ],
+                                            "comments": [
+                                                {
+                                                    "text_blocks": [
+                                                        ":::: Seb35's solution is what I most commonly see for addressing this issue, so that's probably a good solution in this case. Edokter, the enwiki certificate has most of the other domains in the Subject Alternative Name. I personally haven't encountered the issue with the browsers I user, but I'll see if I can reproduce if you let me know what you're using. [[User:CSteipp|CSteipp]] ([[User talk:CSteipp|talk]]) 22:42, 26 August 2013 (UTC)\n"
+                                                    ],
+                                                    "comments": [
+                                                        {
+                                                            "text_blocks": [
+                                                                ":::::HTTPS has just kicked in and to my surprise, all my scripts seem to load from en.wiki just fine. <span style=\"font-family:'Trebuchet MS'\"> \u2014 [[User:Edokter|<span style=\"color:#008\"><i>E</i>dokter</span>]] ([[User talk:Edokter|<span style=\"color:#080\">talk</span>]]) \u2014 </span> 22:09, 28 August 2013 (UTC)\n"
+                                                            ],
+                                                            "comments": [],
+                                                            "cosigners": [],
+                                                            "author": "Edokter",
+                                                            "time_stamp": "22:09, 28 August 2013 (UTC)"
+                                                        }
+                                                    ],
+                                                    "cosigners": [],
+                                                    "author": "CSteipp",
+                                                    "time_stamp": "22:42, 26 August 2013 (UTC)"
+                                                }
+                                            ],
+                                            "cosigners": [],
+                                            "author": "Seb35|<small>[^_^]<",
+                                            "time_stamp": "22:03, 20 August 2013 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Edokter",
+                                    "time_stamp": "20:47, 20 August 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Anomie",
+                            "time_stamp": "13:47, 20 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Edokter",
+                    "time_stamp": "09:56, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Load script from home wiki "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Excluded language ==\n",
+                        "\n",
+                        "Please add ckb wikipedia to excluded language. All sysops of ckb.wiki are from Iran and we can not access to wikimedia projects via HTTPS.--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 19:01, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":What is the exact list of the excluded languages: is it only <code>zh</code> and <code>fa</code>? Or are there also the other Chinese languages: <code>yue/zh-yue</code>, <code>wuu</code>, <code>gan</code>, <code>cdo</code>, <code>nan/zh-min-nan</code>? +those of Iran? Is there a gerrit patch about the config? ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 20:25, 20 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "20:25, 20 August 2013 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ":Please see [https://bugzilla.wikimedia.org/show_bug.cgi?id=52846 bug 52846], these wikis mostly used in Iran and have same problem: fa, ckb, mzn, glk, ku. I don't know any thing about Chinese languages.--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 20:34, 20 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Calak",
+                            "time_stamp": "20:34, 20 August 2013 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ":The current plan is to exclude based on the IP/location of the user, not the language wiki. This means that users from eg China will be able to login to English Wikipedia over HTTP if needed. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:40, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Greg (WMF)",
+                            "time_stamp": "23:40, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Calak",
+                    "time_stamp": "19:01, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Excluded language "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== update of automated editing tools ==\n",
+                        "\n",
+                        "Are pywikipediabot, autowikibrowser, etc, now https compliant? It would be extremely disruptive to implement this change without automated editing tools being able to accommodate it. [[User:DavidLeighEllis|DavidLeighEllis]] ([[User talk:DavidLeighEllis|talk]]) 19:24, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":According to [[:mailarchive:wikitech-ambassadors/2013-August/000349.html|this message]] (just sent), pywikipediabot was updated for HTTPS and the pywikipediabot users must update their code with the last version. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 21:27, 20 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "21:27, 20 August 2013 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ":Please let me know (preferably via IRC or email, greg{{@}}wikimedia.org) if you see any tools that are not ready as soon as possible. Thanks! [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:42, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Greg (WMF)",
+                            "time_stamp": "23:42, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "DavidLeighEllis",
+                    "time_stamp": "19:24, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " update of automated editing tools "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Commons, Wikidata and SUL ==\n",
+                        "\n",
+                        "Won't this create lots of trouble for people in China and Iran who need to upload an image to Commons or modify an interwiki link on Wikidata?\n",
+                        "\n",
+                        "* Commons: You must be logged in to upload an image. If HTTPS is unavailable and mandatory, then you can't log in.\n",
+                        "* Wikidata: It is possible to edit links without logging in, so I suppose that you can edit as an IP using HTTP? This however reveals your IP for everyone to see. Editing over HTTP also reveals your IP address, but only to anyone who is wiretapping you at the same time as you are accessing the Internet.\n",
+                        "* SUL: Logs you in automatically if you visit another project. Doesn't this mean that Chinese and Iranian users will have to log out in order to read an article in another language? This could be very inconvenient if you at the same time need to be logged in on Chinese or Iranian Wikipedia.\n",
+                        "\n",
+                        "You can presumably access HTTPS by using VPN or TOR and you can disable login on selected projects by changing your cookie settings. However, lots of users probably don't know how to do this and the result will instead be that logging in will be disabled. I am personally able to use HTTPS and have HTTPS Everywhere installed, but I understand that lack of unencrypted HTTP for logged in users may cause lots of problems to users in some countries. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 19:49, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":The current plan is to redirect based on the IP/location of the user, not based on language wiki. This should alleviate this issue as we'll whitelist users from China and Iran initially, along with potentially some locations that have a hard time using HTTPS. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:44, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Greg (WMF)",
+                            "time_stamp": "23:44, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Stefan2",
+                    "time_stamp": "19:49, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Commons, Wikidata and SUL "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== HTTPS problem ==\n",
+                        "\n",
+                        "Hello. Now we can't access to all WM projects (except Meta, Commons and Incubator)!--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 19:54, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "*I guess Meta, Commons, and Incubator should all be excluded from the forced https until the \"GeoIP\" functions are available, in order not to cause any problems there for Iranian or Chinese users who e.g. want to complain here on Meta about https problems, are active with uploading files on Commons, or active in test-projects in their language on Incubator. --<small>[[User:MF-Warburg|MF-W]]</small> 20:01, 20 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "MF-Warburg",
+                            "time_stamp": "20:01, 20 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Calak",
+                    "time_stamp": "19:54, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "Now Bugzilla, MediaWiki and Wikidata have not any problem, but all WM projects are out of access. Now I am sysop on ckb wikipedia an I can't open even one page! What are we suppose to do?--[[User:Calak|Calak]] ([[User talk:Calak|talk]]) 20:07, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ": Please see the \"[[{{SUBJECTPAGENAME}}#Help!|Help!]]\" section of the subject-space page. [[IRC]] is fastest. :-)  --[[User:MZMcBride|MZMcBride]] ([[User talk:MZMcBride|talk]]) 21:23, 20 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "MZMcBride",
+                            "time_stamp": "21:23, 20 August 2013 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ":I'm confused, Calek, can you honestly not access \"even on page\" *right now*? We haven't made any changes yet. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 23:45, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Greg (WMF)",
+                            "time_stamp": "23:45, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Calak",
+                    "time_stamp": "20:07, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " HTTPS problem "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== why Chinese languages are excluded\uff1f ==\n",
+                        "\n",
+                        "I think Chinese wikipedian community has made it clear that all Chinese language(Classical Chinees, Wuu chinese etc) should not be convert into https version, but here I see nothing. can somebody tell me why please? as A classical Chinese editor, I will no longer be able to do my work if it is true that Meta forget their promises. \n",
+                        "\n",
+                        "----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 23:04, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ": See also [[bugzilla:52846#c12]] and try to get a complete list of the languages. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 23:12, 20 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Stefan2",
+                            "time_stamp": "23:12, 20 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Benjamin Jiperus",
+                    "time_stamp": "23:04, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n",
+                        "The Chinese community has given a list, on that list, it shows what kind of Chinese language should not be https, that also include Tibetan, another Sino-Tibetan language that will be influenced. because most of the native speakers are '''located in China''' where HTTPs isn't an easy option. we have already got restrictions from Communist party. https is no help to us. ----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 23:16, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Benjamin Jiperus",
+                    "time_stamp": "23:16, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " why Chinese languages are excluded\uff1f "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Leave choice to users ==\n",
+                        "Please let users choose which transport they want to use. --[[User:Purodha|Purodha Blissenbach]] ([[User talk:Purodha|talk]]) 23:06, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "* This. It will be complete crap if I will be forced to edit through HTTPS, it's slow on my instable connection. And FYI, forcing users should be only last resort, and I see no reason to change to HTTPS voluntarily. [[User:KPu3uC B Poccuu|KPu3uC B Poccuu]] ([[User talk:KPu3uC B Poccuu|talk]]) 02:32, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "KPu3uC B Poccuu",
+                            "time_stamp": "02:32, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Purodha",
+                    "time_stamp": "23:06, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n",
+                        "Please leave the choice to user, this is so wrong to force people to use HTTPS if they want to stay connected. --[[User:PierreSelim|PierreSelim]] ([[User talk:PierreSelim|talk]]) 05:19, 21 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":You can [[HTTPS#Disabling|turn off HTTPS]] in the preferences. As of now I don\u2019t see it, I guess it will be deployed in some hours at the same time HTTPS will become mandatory. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 06:33, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::Keep in mind that that will only disable the secure browsing and secure editing features; log-in remains only HTTPS even if that preference is selected. [[User:Risker|Risker]] ([[User talk:Risker|talk]]) 08:12, 21 August 2013 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                ":::That should be enough for my JavaScript bot and for web-debugging. I'd prefer if I don't have to make my browser trust the Fiddler certificate. -- [[User:Rillke|Rillke]] ([[User talk:Rillke|talk]]) 08:11, 22 August 2013 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Rillke",
+                                            "time_stamp": "08:11, 22 August 2013 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Risker",
+                                    "time_stamp": "08:12, 21 August 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "06:33, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "PierreSelim",
+                    "time_stamp": "05:19, 21 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n",
+                        "\n",
+                        "Is there anyway to make the opting out of HTTPS a global preference?  I tend to go to the foreign language wikis to get more extensive articles about subjects of greater import to that language community, and I'm having to manually go to the preferences page the first time I visit them after the change and to opt out of HTTPS for that wiki. That has been and remains my biggest gripe about the HTTPS switchover. [[User:Carolina wren|Carolina wren]] ([[User talk:Carolina wren|talk]]) 02:31, 12 September 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Carolina wren",
+                    "time_stamp": "02:31, 12 September 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Leave choice to users "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Translation ==\n",
+                        "\n",
+                        "Hi. Why neither this page nor global message delivery post isn't/wasn't translatable? Do you think everybody on the planet is at least en-2? Althought I try to AGF but I can't consider it another way than not respect to local not English communities who are not obliged to learn English. WMF should never do that way again. --[[User:Base|Base]] ([[User talk:Base|talk]]) 23:26, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":Basically this is now possible in a manual way, although I\u2019m personaly relunctant to use the Translated extension because the page is not stable and would ask frequent re-translations, but if someone wants to set up it, just do. I asked the Meta admins to [[Meta:Requests for help from a sysop or bureaucrat#Translate the link of Special:CentralNoticeBanners/edit/Genericmaintenancenotice|change the link in the banners]] (I would be very happy if someone could do that!). I sent a message to the [[:mailarchive:translators-l/2013-August/002362.html|translators-l mailing list]] about this translation. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 13:02, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "13:02, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Base",
+                    "time_stamp": "23:26, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Translation "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== List of Chinese Wikipedia  ==\n",
+                        "\n",
+                        "Please Notice these languages also need to remain http.\n",
+                        "\n",
+                        "*[//zh-classical.wikipedia.org/wiki/%E7%B6%AD%E5%9F%BA%E5%A4%A7%E5%85%B8:%E5%8D%B7%E9%A6%96 Classical Chinese(lzh)]\n",
+                        "*[//wuu.wikipedia.org/wiki/%E5%B0%81%E9%9D%A2 Wuu Chinese(wuu)]\n",
+                        "*[//gan.wikipedia.org/wiki/%E8%B4%9B%E8%AA%9E Gan Chinese(Gan)]\n",
+                        "*[//hak.wikipedia.org/wiki/Th%C3%A8u-Ya%CC%8Dp Hakka Chinese(Hak)]\n",
+                        "*[//zh-yue.wikipedia.org/wiki/%E9%A0%AD%E7%89%88 Cantonese(zh-yue) ]\n",
+                        "*[//bo.wikipedia.org/wiki/%E0%BD%82%E0%BD%99%E0%BD%BC%E0%BC%8B%E0%BD%84%E0%BD%BC%E0%BD%A6%E0%BC%8D Tibetan(bo)]\n",
+                        "*[//zh-min-nan.wikipedia.org/wiki/Th%C3%A2u-ia%CC%8Dh Minnan Chinese(zh-min-nan)]\n",
+                        "\n",
+                        "----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 23:28, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Benjamin Jiperus",
+                    "time_stamp": "23:28, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n",
+                        "Sorry there is two more languages:\n",
+                        "* [//cdo.wikipedia.org/wiki/T%C3%A0u_Hi%C4%95k Mindong Chinese(cdo)]\n",
+                        "*[//ug.wikipedia.org/wiki/%D8%A6%DB%87%D9%8A%D8%BA%DB%87%D8%B1%DA%86%DB%95_%DB%8B%D9%89%D9%83%D9%89%D9%BE%D9%89%D8%AF%D9%89%D9%8A%DB%95 Uyghur (ug)]\n",
+                        "\n",
+                        "Uyghur are Turkish language, a majority of Uighur people lives in the west part of China.  \n",
+                        "Thank you<br />{{unsigned|Benjamin Jiperus|23:49, 20 August 2013 (UTC)}}\n",
+                        ":I opened the [[:bugzilla:53144|bug 53144]] for tracking this problem and wrote the list you gave (+zh :) ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 07:39, 21 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "::[//ii.wikipedia.org Sichuan Yi (ii)] ([//ii.wikipedia.org/wiki/ 16 articles by now]) --<span style=\"font-family:Palatino\">[[User:Geitost|Geitost]] [[User talk:Geitost|<sup>''diskusjon''</sup>]]</span> 07:31, 22 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Geitost",
+                            "time_stamp": "07:31, 22 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Seb35|<small>[^_^]<",
+                    "time_stamp": "07:39, 21 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " List of Chinese Wikipedia  "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Perfect forward secrecy ==\n",
+                        "\n",
+                        "Will the new https-including setup have the [http://en.wikipedia.org/wiki/Perfect_forward_secrecy Perfect forward secrecy] property? If not, it would be nice to have. There should be an option to prioritize Diffie-Hellman for key-exchange to achieve this. Wishing you good results for the procedure, good to see that coming. --[[User:Methossant|Methossant]] ([[User talk:Methossant|talk]]) 23:35, 20 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":According to \"[[:wmfblog:2013/08/01/future-https-wikimedia-projects/|The future of HTTPS on Wikimedia projects]]\" PFS will not be enabled soon, but it is in the future plans. From the some things I read about PFS [https://www.imperialviolet.org/2011/11/22/forwardsecret.html this blog post] is interesting (activation of PFS by Google) and [http://vincent.bernat.im/en/blog/2011-ssl-perfect-forward-secrecy.html this one] says PFS only cost 15% more in computer time (ECDHE version, because the classical DHE is much more expensive -- 300% more in compute time). But PFS is not completely supported by all modern browsers: IE support lacks, Opera only have DHE; Chromium and Firefox have full support. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 07:05, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":: If you have any news in this regard, you want to upgrade to something like quantum cryptography? [[User:Jo\u00e3o bonomo|Jo\u00e3o bonomo]] ([[User talk:Jo\u00e3o bonomo|talk]]) 20:06, 11 September 2013 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Jo\u00e3o bonomo",
+                                    "time_stamp": "20:06, 11 September 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "07:05, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Methossant",
+                    "time_stamp": "23:35, 20 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Perfect forward secrecy "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Unable to edit Wikidata ==\n",
+                        "\n",
+                        "It says to report trouble here.<br />\n",
+                        "I have not been able to edit Wikidata while logged in for the past couple of days.<br />\n",
+                        "The [edit] buttons all appear initially, then they vanish.<br />\n",
+                        "[[User:Varlaam|Varlaam]] ([[User talk:Varlaam|talk]]) 00:36, 21 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":Hi Varlaam, I doubt this is due to the HTTPS (the topic of this Talk: page) as nothing has changed yet :-). I've reported it to the WikiData team in [https://bugzilla.wikimedia.org/show_bug.cgi?id=53200 this bug report]. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 05:07, 22 August 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":: Greg, thanks for pointing this our way. Varlaam, can you give a bit more info? Browser used? Operating system? Can you try switching off your gadgets and see if there is some interplay? --[[User:Denny|denny]] ([[User talk:Denny|talk]]) 09:30, 22 August 2013 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "::: I agree with Greg that it shouldn't be the HTTPS. You try disabling all your gadgets, then re-enable each individually to try to figure out if any is the problem. I remember some time ago a script caused a similar issue for me. If this doesn't help (if you still have the issue with all gadgets off, even after clearing your browser's cache, the extra information Denny asked for might be of some help. <b><span style=\"border:2px solid;font-variant:small-caps\">[[User:Hazard-SJ|<span style=\"background:#00008B;color:#FFF\">&nbsp;Hazard-SJ&nbsp;</span>]][[User talk:Hazard-SJ|<span style=\"color:#00008B;background:red\">&nbsp;\u2708&nbsp;</span>]]</span></b> 23:25, 22 August 2013 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Hazard-SJ",
+                                            "time_stamp": "23:25, 22 August 2013 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Denny",
+                                    "time_stamp": "09:30, 22 August 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Greg (WMF)",
+                            "time_stamp": "05:07, 22 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Varlaam",
+                    "time_stamp": "00:36, 21 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Unable to edit Wikidata "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Copy editing notes ==\n",
+                        "\n",
+                        "*Please add a link to some formal statement or roadmap or approved plan that says \"[t]he continued work to improve the security and privacy of Wikimedia project users is a stated goal of the Wikimedia Foundation\". (I'm not doubting it's true, but a footnote/reference helps.) \n",
+                        "*It might also be useful to link to some internal or external site that confirms the use of Wikipedia as a site useful for tracking.  \n",
+                        "*I recall some discussion on how images would be handled with HTTPS enabled, but wasn't technically competent enough to follow the conversation. Are there any issues with images that will change the effectiveness of the HTTPS login and browsing? If so, and since we have a huge number of non-Commons pages with images on them, it would be appropriate to mention this.\n",
+                        "*Also appropriate to mention any other situations where HTTPS may not be as effective as expected.\n",
+                        "[[User:Risker|Risker]] ([[User talk:Risker|talk]]) 05:29, 21 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "\n",
+                                ":1. no idea about that\n",
+                                ":2. added a Jimmy Wales\u2019 tweet with an image (perhaps the journal article is better, don\u2019t know)\n",
+                                ":3 and 4. I guess you are speaking about the traffic analysis, allowing an attacker to guess the page you are reading by collecting the sizes of the pages, images, and ressources from all pages and comparing it afterwards to some specific request you made; if so, I think it is too technical and specific for being worth to be mentioned here (but it\u2019s because of this fact I wrote in the introduction \"you can have a reasonable expectation that nobody knows what pages you are visiting\").\n",
+                                ":~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 13:22, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "13:22, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Risker",
+                    "time_stamp": "05:29, 21 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Copy editing notes "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== A request of resolution  ==\n",
+                        "\n",
+                        "Here is all I know(forgive my English):\n",
+                        "*Chinese Wikipedian have send a list of Chinese language(that are not suitable for https) while the meeting was still going 2 weeks ago.I wasn't at the meeting, people who was there told me Wikimedia Foundation would take into account Chinese languages(for example Wuu, Cantonese and Classical.etc)\n",
+                        "*Now people are telling me except Chinese(standard), other dialects and Classical Chinese will still use https. \n",
+                        "*this is not what we expected. \n",
+                        "*I hope what is promised(if there is a promise made by Wikimedia Foundation) will be carried out. \n",
+                        "*If I am wrong about what I say, please tell me the actual situation of converting into https version. \n",
+                        "\n",
+                        "thank you----[[User:Benjamin Jiperus|Benjamin Jiperus]] ([[User talk:Benjamin Jiperus|talk]]) 09:34, 21 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":Hi Benjamin. Sorry for the confusion. The current status, as described on [[HTTPS]], is that users from countries where HTTPS is not an option (specifically, China and Iran) will not be redirected to HTTPS but instead will stay on HTTP. Thus, if you are a Chinese user access English Wikipedia, you will still be able to login and view everything because you will be going over HTTP (as you're computer is based in China). Hope that clarifies, let me know if it doesn't. [[User:Greg (WMF)|Greg (WMF)]] ([[User talk:Greg (WMF)|talk]]) 20:18, 27 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Greg (WMF)",
+                            "time_stamp": "20:18, 27 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Benjamin Jiperus",
+                    "time_stamp": "09:34, 21 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " A request of resolution  "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Which documents? ==\n",
+                        "The preamble of this article mentions: \"The Wikipedia project was referenced in several documents as a specific source for tracking users' behavior online\". Which documents are referenced here? Was it discussed somewhere? -- [[User:Ace111|Ace111]] ([[User talk:Ace111|talk]]) 13:31, 21 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":This was raised by [[User:Risker|Risker]] two sections above; I just added a link to one document I know, but I don\u2019t know others. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 13:37, 21 August 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":: Jimbo's twitter post refers to a NSA slide from [http://www.theguardian.com/world/2013/jul/31/nsa-top-secret-program-online-data Guardian] with a question: \"Why are we interested in HTTP?\" and an answer \"Because nearly everything a typical user does on the Internet uses HTTP\", followed by examples of web sites such as Facebook, Yahoo, Twitter, myspace, CNN, mail.ru, Wikipedia, Google and Gmail. I don't think this is a proper reference for Wikipedia as a specific source for tracking users' behavior. -- [[User:Ace111|Ace111]] ([[User talk:Ace111|talk]]) 14:55, 21 August 2013 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                ":::I remembered some people in the discussions (on wikitech-l probably) with a similar opinion. I don\u2019t have real opinion myself if this constitutes an evidence or not; but it\u2019s the only thing I know that people refered for this claim, but obviously perhaps there are others I missed. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 22:19, 21 August 2013 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Seb35|<small>[^_^]<",
+                                            "time_stamp": "22:19, 21 August 2013 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Ace111",
+                                    "time_stamp": "14:55, 21 August 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Seb35|<small>[^_^]<",
+                            "time_stamp": "13:37, 21 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Ace111",
+                    "time_stamp": "13:31, 21 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Which documents? "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== privacy concerns with images embedded in pages, served by Commons ==\n",
+                        "\n",
+                        "Is HTTPS fully supported as well for images hosted on Commons (if Commons does not have HTTPS support for now), when these images (most often thumbnailed) are embedded in Wikipedia pages ?\n",
+                        "Can you warranty that noone will know which Wikipedia you are consulting (including in Talk pages) if they embed these images in an unique way ? It is easy to deduce which pages you are reading if you can track the images embedded in them.\n",
+                        "Commons should then support HTTPS, including on the images server (but there's a huge scalability problem because Commons is extremely large and the thumbnail image servers have lots of work to do, probably much more than wikis themselves).\n",
+                        "\n",
+                        "Also a good thing to do would be to mutualize ALL WMF wikis on the same base domain, so that we could use the same logon domain and remain in it, even when navigating on foreign wikis (it would require only a new design for paths; e.g. allowing transparent remapping of\n",
+                        ": http(s)://(projectlangcode).(wikipedia).org/wiki/(pagename)\n",
+                        "to\n",
+                        ": http(s)://www.wikimedia.org/(wikipedia)/(lang)/wiki/(pagename)\n",
+                        "\n",
+                        "One bug advantage would be the unification of security, simplification of navigation. In fact we would just connect via HTTP or HTTPS to a single proxy with a single URL:\n",
+                        ": https://wikimedia.org/logon\n",
+                        "and then all navigation would occur within the same domain within the same session, to request any number of pages or images, from any wiki of the foundation. only within this encrypted HTTPS session would the legacy URLs be requested. This proxy domain would connect directly to any one of the existing Squid proxies, forwarding internally the requests to the appropriate project wiki and image servers (or other services, including Worpress blogs, IRC channels, submission APIs, etc. that are compatible with HTTP proxies).\n",
+                        "\n",
+                        "But the users won't see now any change in their address bar that will only show\n",
+                        ": https://wikimedia.org/logon\n",
+                        "during their navigation across pages, projects and services. Even when they will right click a link, they will be show anonymized URLs encrypted with their current secure session keys (e.g. https://go.wikimedia.org/(base-64 encoded encrypted string containing the service/project/language/page?get parameters).\n",
+                        "Note that the proxy delivering an HTML wiki page could transform as well these links using short URLs specific to the session, to make the base-64 strings short (the proxy would cache the URLs from the original page to build short URLs specific to the session and not comparable across users, using a simple SHA1 digest of the full URL, encrypted with the private session key, so that the delivered HTML pages would only contain relative links like \"/(short base64 string)\")\n",
+                        "\n",
+                        "The base-64 encoding is suggested, but a larger encoding alphabet could make the string even a bit shorter, similar to those strings used on services like TinyURL. As well the non-encrupted string could be cached internally with a mapping to make them even shorter (based on usage statistics) for frequently accessed URLs. The encryption of these short URLs would still remain private and specific to each user session.\n",
+                        "\n",
+                        "Note that this encyption of URLs does not require to deliver any encryption key to the client, it is purely internal to the proxy that manages the encryption/devyption keys internally. Also this encryption will not increase the length of short URLs.\n",
+                        "\n",
+                        "[[User:Verdy p|verdy_p]] ([[User talk:Verdy p|talk]]) 19:51, 21 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "\n",
+                                ":Commons and upload.wikimedia.org (where images are actually served from) support HTTPS. All of our projects have fully supported HTTPS for quite some time now.--[[User:Ryan Lane (WMF)|Ryan Lane (WMF)]] ([[User talk:Ryan Lane (WMF)|talk]]) 01:08, 29 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Ryan Lane (WMF)",
+                            "time_stamp": "01:08, 29 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Verdy p",
+                    "time_stamp": "19:51, 21 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " privacy concerns with images embedded in pages, served by Commons "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Loss of browser history ==\n",
+                        "\n",
+                        "I just had cause to use Internet Explorer and it seems as though it was not saving history for https pages. I have not investigated fully but if I was forced to use Internet Explorer, I would prefer to be subject to snooping by the NSA than lose my browsing history. [[User:RHaworth|RHaworth]] ([[User talk:RHaworth|talk]]) 21:07, 21 August 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "RHaworth",
+                    "time_stamp": "21:07, 21 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Loss of browser history "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Impossible Log out ==\n",
+                        "Since tonight, I can not log out. It's some feature of https? --[[User:\u0160J\u016f|\u0160J\u016f]] ([[User talk:\u0160J\u016f|talk]]) 20:50, 22 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ": I usually use the secure login and have never had that problem, so I wouldn't say it's a feature. Did you try going to [[Special:UserLogout]], at least o the secure server? [[Special:Contributions/72.252.242.170|72.252.242.170]] 23:20, 22 August 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":: The page [[Special:UserLogout]] appeared and the login from the top of the page dissappeared but in 1 or 2 second appeared again. However, the bug seems to be eliminated now. --[[User:\u0160J\u016f|\u0160J\u016f]] ([[User talk:\u0160J\u016f|talk]]) 00:53, 23 August 2013 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "\u0160J\u016f",
+                                    "time_stamp": "00:53, 23 August 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "72.252.242.170",
+                            "time_stamp": "23:20, 22 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "\u0160J\u016f",
+                    "time_stamp": "20:50, 22 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Impossible Log out "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== http/https link embedded in wiki text using the link tool \u2026 ==\n",
+                        "\n",
+                        "\u2026 does not work. If you select the link tool, and paste an url, it should be stripped off the protocol to get protocol relative urls automatically. At least for WP links like this (completely arbitrary): https://de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 the link tool shall strip the protocol. Adding //de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 to the link tool will create [http:////de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 //de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984] (url with prefix http:////de.wikipedia.org). Furthermore the wiki text (protocol relative url) //de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Koordinatenfreak&diff=118605869&oldid=118178984 should autolink like the non-protocol-relative-url does. --[[User:Herzi Pinki|Herzi Pinki]] ([[User talk:Herzi Pinki|talk]]) 23:02, 22 August 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Herzi Pinki",
+                    "time_stamp": "23:02, 22 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " http/https link embedded in wiki text using the link tool \u2026 "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== API ==\n",
+                        "\n",
+                        "Is this going to affect browser logins only, or will pure API sessions (those that occur outside a browser environment) be affected as well? [[User:This, that and the other|This, that and the other]] ([[User talk:This, that and the other|talk]]) 09:17, 25 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ": This is only for browser logins, the api does not force a redirect [[User:CSteipp|CSteipp]] ([[User talk:CSteipp|talk]]) 22:47, 26 August 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "CSteipp",
+                            "time_stamp": "22:47, 26 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "This, that and the other",
+                    "time_stamp": "09:17, 25 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " API "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Causing problems ==\n",
+                        "\n",
+                        "I have disabled this in my preferences, as the default left me totally unable to edit, or even view, Wikipedia. (Every time I clicked on a link, or even typed in a url, I was switched to an https url, with a popup window \"couldn't parse page name from url ...\". Previously, if directed to an https page, I have had to remove the s in order to open the page, but the new change made this impossible. Eventually I managed to open my preferences, find the relevant entry, and uncheck the tick; now everything works smoothly again.\n",
+                        "\n",
+                        "I have no idea what is causing the problem; whether it is my Wikipedia gadgewts, my Firefox add-ons, or my security settings. Nor do I feel inclined to experiment and see what tweaks, if any, would resolve the problem. But it is clear to me that this change should not become a default, or be made mandatory, since this would certainly lock out readers and editors.\n",
+                        "\n",
+                        "If anyone responds to this, please inform me at [http://en.wikipedia.org/wiki/User_talk:RolandR my talk page on English Wikipedia]; I have never before visited Wikimedia. [[User:RolandR|RolandR]] ([[User talk:RolandR|talk]]) 00:13, 29 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "\n",
+                                ": I'm pretty sure this is due to a script you have installed (as I indicated on the VPT thread). [https://en.wikipedia.org/w/index.php?title=User%3AQuarl%2Fwikipage.js&diff=570605025&oldid=38600544 I fixed it]. [[User:^demon|^demon]] ([[User talk:^demon|talk]])\n",
+                                "::That doesn't seem to have resolved the problem. I re-enabled the secure login in my preferences, and again started to get the \"couldn't parse page name\" pop-up. Which of my scripts might be causing this? [[User:RolandR|RolandR]] ([[User talk:RolandR|talk]]) 10:56, 29 August 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":::In fact, this seems to have made the problem worse; now, although I have unticked the checkbox in Preferences, every link defaults to https, and I am unable to open any page easily. Please help! [[Special:Contributions/86.186.105.211|86.186.105.211]] 11:10, 29 August 2013 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "::::If you wish to change the HTTPS setting back to HTTP, try going to [{{fullurl:en:Special:Preferences|useskin=modern}}] or [{{fullurl:en:Special:Preferences|useskin=cologneblue}}].\n",
+                                                "::::If you wish to fix the problem, try going to [[w:User:RolandR/monobook.js]] and [[w:User:RolandR/vector.js]] and change \"http://\" to \"//\" everywhere on the pages. The JS files can only be edited by you or by an administrator at English Wikipedia.\n",
+                                                "::::If this doesn't help, then it probably means that something is wrong in one of the scripts that you are importing. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 12:31, 29 August 2013 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Stefan2",
+                                            "time_stamp": "12:31, 29 August 2013 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "86.186.105.211",
+                                    "time_stamp": "11:10, 29 August 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "RolandR",
+                            "time_stamp": "10:56, 29 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "RolandR",
+                    "time_stamp": "00:13, 29 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n",
+                        "Hello,\n",
+                        "\n",
+                        "I also have some problems. First, I didn't get the images until I clicked to access a Commons page and validate the security certificate; now solved. But it seems the scripts don't work. I have no personnalised JS or CSS (the /monobook.js page or the like don't exist).\n",
+                        "\n",
+                        "Any clue?\n",
+                        "\n",
+                        "[[User:Cdang|Cdang]] ([[User talk:Cdang|talk]]) 13:46, 29 August 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Cdang",
+                    "time_stamp": "13:46, 29 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Causing problems "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Google Translate ==\n",
+                        "\n",
+                        "When I paste \"https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Gadgets\" into either http://translate.google.com/ or https://translate.google.com/ I get the message:\n",
+                        ": Google Error\n",
+                        ": Sorry, this URL is invalid\n",
+                        ": http://fr.wikipedia.org:443/wiki/Sp%C3%A9cial:Gadgets\n",
+                        "But when I paste the regular \"http://fr.wikipedia.org/wiki/Sp%C3%A9cial:Gadgets\", it translates it fine. Can someone attest that this is a Wikimedia problem and, if so, submit a bug about it? - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 08:37, 29 August 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":Looks like a bug in the google tool to me... Apparently it has existed [http://ubuntuincident.wordpress.com/2011/02/07/patch-to-google-translate-https-pages/ for years] already. Perhaps WMF operations can tickle their google contacts a bit. [[User:TheDJ|TheDJ]] ([[User talk:TheDJ|talk]]) 11:52, 29 August 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::I've had this problem ever since I started using HTTPS (a while ago). It's a problem with Google Translate. {{ping|Snowolf}} didn't you write to a mailing list about this last year? [[User:PiRSquared17|PiRSquared17]] ([[User talk:PiRSquared17|talk]]) 18:55, 31 August 2013 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                ":::I did. I don't think they ever replied to me. <i><b>[[User:Snowolf|<font color = \"darkmagenta\">Snowolf</font>]] <sup><small>[[User talk:Snowolf|<font color = \"darkmagenta\">How can I help?</font>]]</small></sup></b></i> 22:09, 31 August 2013 (UTC)\n"
+                                            ],
+                                            "comments": [
+                                                {
+                                                    "text_blocks": [
+                                                        ":::: Hmm. Maybe now that Wikimedia is going HTTPS for all logged-in users on all projects, they'll get more pressure to do something about it. - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 01:26, 2 September 2013 (UTC)\n"
+                                                    ],
+                                                    "comments": [],
+                                                    "cosigners": [],
+                                                    "author": "Dcljr",
+                                                    "time_stamp": "01:26, 2 September 2013 (UTC)"
+                                                }
+                                            ],
+                                            "cosigners": [],
+                                            "author": "Snowolf",
+                                            "time_stamp": "22:09, 31 August 2013 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "PiRSquared17",
+                                    "time_stamp": "18:55, 31 August 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "TheDJ",
+                            "time_stamp": "11:52, 29 August 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Dcljr",
+                    "time_stamp": "08:37, 29 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n",
+                        "I work for Google, and got the following answer from <b> Google Translate team: </b> <br>\n",
+                        "\"Currently, the Google proxy-based web translation cannot translate HTTPS pages. It's a known limitation, and we'd like to remove that limitation.\"\n",
+                        ": OK, well, there's a very easy fix for that\u2026 - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 02:23, 17 September 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Dcljr",
+                    "time_stamp": "02:23, 17 September 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Google Translate "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== [[HTTPS#Various small problems]] ==\n",
+                        "\n",
+                        "I added this section to help users particularly with script problems or certificate problems. Be bold at rewriting it or adding issues, I have only my own experience of HTTPS problems or those reported on the village pumps (although always difficult to precisely understand what is wrong and consider solutions).\n",
+                        "\n",
+                        "For the scripts I guess this is quite important and many editors could wonder why their scripts suddently do no more work, see these few searches: [//fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Recherche&limit=20&offset=20&redirs=1&ns2=1&search=loadjs] (search the exact case loadJS), [//en.wikipedia.org/w/index.php?title=Special%3ASearch&limit=20&offset=20&redirs=1&ns2=1&search=loadjs], [https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=js+write&fulltext=Search&ns2=1&redirs=1&profile=advanced], [https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=js+http&fulltext=Search&ns2=1&redirs=1&profile=advanced]; even, some users call external scripts (sometimes the destination server don\u2019t support https). For these scripts, I don\u2019t know what exactly should be prefered, is it <code>importScriptURI</code>? not <code>mw.loader.load</code>?\n",
+                        "\n",
+                        "About the Authority certificate (DigiCert High Assurance EV Root CA), is there known issues with the devices which don\u2019t have it in their certificate repository? I use to see it on the Internet and with my browsers (Opera, Firefox), but perhaps there are exotic devices or browsers or operating systems or combinaisons of these ones which don\u2019t recognize it. ~ [[User:Seb35|Seb35]] [[User talk:Seb35|<small>[^_^]</small>]] 19:15, 29 August 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Seb35|<small>[^_^]<",
+                    "time_stamp": "19:15, 29 August 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " [[HTTPS#Various small problems]] "
+        },
+        {
+            "subsections": [
+                {
+                    "subsections": [],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "=== Wikipedia discussion at Village Pump (technical) talk page ===\n",
+                                "\n",
+                                "*ALL EMBEDDED LINKS ARE FOR '''WIKIPEDIA'''\n",
+                                "\n",
+                                "As other editors have [[:en:Wikipedia:Village pump (technical)#Secure site only?|already made note of]], the change-over to Secure URLs is causing problems for a lot of us. I've [[:en:Wikipedia:Village pump (technical)#Who is in charge|already explained above]] how upsetting it was to have my Wikipedia browsing history suddenly disappear. I mistakenly thought that unchecking the setting in my preferences had taken care of the problem. Not So. It turns out that when I specify one of the normal/non-secure Wikipedia URLs, the software no longer recognizes me as a logged-in user -- iow, the pages display as they do for any anon. IP user (and as I discovered by accident, my IP address shows up in the edit history, as one would expect). But as soon as I go to a secure URL, everything goes back to normal -- and that's without having to log in again; iow, it keeps me logged in, as it should. But those secure pages don't show up in my browser history, no matter what I do. Yes, I've changed & re-changed my preference setting and logged back in several times. And I've also looked for the trouble-making cookies that were mentioned above -- but curiously, I don't seem to have ANY cookies for Wikipedia, even though it is one of the few sites where I expressly allow them by default. <sigh> Any help on this would be hugely appreciated! [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 08:34, 1 September 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::You don't actually say - either here or at <span class=\"plainlinks\">[//en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&diff=prev&oldid=570904030 your previous post]</span> - which browser you're using. --[[:en:User:Redrose64|<span style=\"color:#a80000; background:#ffeeee; text-decoration:inherit\">Red</span>rose64]] ([[:en:User talk:Redrose64|talk]]) 09:56, 1 September 2013 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Redrose64",
+                                    "time_stamp": "09:56, 1 September 2013 (UTC)"
+                                },
+                                {
+                                    "text_blocks": [
+                                        ":Ah, I was wondering  why when I  open a new browser window it shows me as not  logged in. [[:en:User:Kudpung|Kudpung \u0e01\u0e38\u0e14\u0e1c\u0e36\u0e49\u0e07]] ([[:en:User talk:Kudpung|talk]]) 09:54, 1 September 2013 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Kudpung",
+                                    "time_stamp": "09:54, 1 September 2013 (UTC)"
+                                },
+                                {
+                                    "text_blocks": [
+                                        "\n",
+                                        ":Well, if anyone is interested, I am  using  Ffox 23.0.1 on  MacOS 10.8.4. Looks as if the default  move to  https has thrown more than one spanner in  the works. [[:en:User:Kudpung|Kudpung \u0e01\u0e38\u0e14\u0e1c\u0e36\u0e49\u0e07]] ([[:en:User talk:Kudpung|talk]]) 10:36, 1 September 2013 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "::I too am using Firefox, although under Windows XP. Here's how I successfully went back to http:\n",
+                                                "::#Go to <span class=\"example\" style=\"font-family: Georgia, serif;\">[[:en:Special:Preferences|Preferences]]</span>, switch off \"Always use a secure connection when logged in\" and save\n",
+                                                "::#Log out of Wikipedia and close all browser tabs that contain Wikipedia pages - but keep the browser itself open\n",
+                                                "::#In the browser menu bar, go to Tools \u2192 Options \u2192 Privacy\n",
+                                                "::#Click the link \"remove individual cookies\", this opens a new window titled \"Cookies\" - maximise that, it makes things easier\n",
+                                                "::#In the search bar of \"Cookies\", enter <kbd>forceHTTPS</kbd> exactly like that - it's case-sensitive\n",
+                                                "::#Highlight a row and click <span class=\"nowrap\" title=\"This is not a clickable button; it illustrates the button to look for\" style=\"padding:.2em .6em; border:1px solid; border-color:#aaa #555 #555 #aaa; -moz-border-radius: 3px; -webkit-border-radius: 3px; border-radius: 3px; background-color:#f2f2f2; background-image: -moz-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -ms-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -o-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -webkit-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: linear-gradient(top, #fcfcfc, #e0e0e0);  \">Remove Cookie</span> (the <kbd class=\"keyboard-key nowrap\" style=\"border: 1px solid #aaa; -moz-border-radius: 2px; -webkit-border-radius: 2px; border-radius: 2px; -moz-box-shadow: 1px 2px 2px #ddd; -webkit-box-shadow: 1px 2px 2px #ddd; box-shadow: 1px 2px 2px #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -ms-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(top, #eee, #f9f9f9, #eee); padding: 1px 3px; font-family: inherit; font-size: 0.85em;\">Delete</kbd> key works on a PC, don't know about a Mac)\n",
+                                                "::#Repeat until all are gone, then click <span class=\"nowrap\" title=\"This is not a clickable button; it illustrates the button to look for\" style=\"padding:.2em .6em; border:1px solid; border-color:#aaa #555 #555 #aaa; -moz-border-radius: 3px; -webkit-border-radius: 3px; border-radius: 3px; background-color:#f2f2f2; background-image: -moz-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -ms-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -o-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: -webkit-linear-gradient(top, #fcfcfc, #e0e0e0); background-image: linear-gradient(top, #fcfcfc, #e0e0e0);  \">Close</span>\n",
+                                                "::#Visit http://en.wikipedia.org/wiki/ and log in\n",
+                                                "::You should now be back on http: --[[:en:User:Redrose64|<span style=\"color:#a80000; background:#ffeeee; text-decoration:inherit\">Red</span>rose64]] ([[:en:User talk:Redrose64|talk]]) 10:50, 1 September 2013 (UTC)\n"
+                                            ],
+                                            "comments": [
+                                                {
+                                                    "text_blocks": [
+                                                        ":::Thanks for your detailed reply, Redrose64. Hopefully that will be very helpful for any Firefox users who find their way to this page. Unfortunately it doesn't help me, perhaps because I am using IE8 (although they are very similar). I had already tried to find those cookies (they were also mentioned above), but as I noted, I was unable to turn up ANY cookies at all for Wikipedia among the cookies listed in my TIF folder. Very puzzling, to say the least. [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 12:52, 1 September 2013 (UTC)\n"
+                                                    ],
+                                                    "comments": [
+                                                        {
+                                                            "text_blocks": [
+                                                                "::::Try looking in your Cookies folder. I don't quite understand why, but Internet Explorer's cookies can be found in both \"Temporary Internet Files\" and \"Cookies\". \u2013&#160;'''[[:en:User:PartTimeGnome|PartTimeGnome]]''' <span style=\"font-size:79%\">([[:en:User talk:PartTimeGnome|talk]]&#160;&#124; [[:en:Special:Contributions/PartTimeGnome|contribs]])</span> 20:28, 1 September 2013 (UTC)\n"
+                                                            ],
+                                                            "comments": [],
+                                                            "cosigners": [],
+                                                            "author": "PartTimeGnome",
+                                                            "time_stamp": "20:28, 1 September 2013 (UTC)"
+                                                        }
+                                                    ],
+                                                    "cosigners": [],
+                                                    "author": "Cgingold",
+                                                    "time_stamp": "12:52, 1 September 2013 (UTC)"
+                                                }
+                                            ],
+                                            "cosigners": [],
+                                            "author": "Redrose64",
+                                            "time_stamp": "10:50, 1 September 2013 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Kudpung",
+                                    "time_stamp": "10:36, 1 September 2013 (UTC)"
+                                },
+                                {
+                                    "text_blocks": [
+                                        "*'''New Wrinkle''' - For a time, I was able to move from page to page in the ''non-secure'' universe, and at least ''those'' pages would show up in my browser history. But something seems to have changed. Now I cannot access ANY non-secure pages -- even when I specify \"http\" in the address bar of my browser, it just redirects to \"httpS\", regardless of whether I am logged IN or logged OUT. I think I may be starting to lose my mind. [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 13:18, 1 September 2013 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "**What kind of windows edition do you use  ? It seems that IE in the Windows server and possible professional editions seem to not store anything by default if the user is using https. \u2014[[:en:User:TheDJ|Th<span style=\"color: green\">e</span>DJ]] ([[:en:User talk:TheDJ|talk]] \u2022 [[:en:Special:Contributions/TheDJ|contribs]]) 15:18, 1 September 2013 (UTC)\n"
+                                            ],
+                                            "comments": [
+                                                {
+                                                    "text_blocks": [
+                                                        "***I'm using Windows 7. What's crazy about all of this is that unchecking the new default setting in preferences seems to have no effect whatsoever. To repeat, yes I've logged out and back in multiple times, and the setting remains unchecked. I've also looked and ''searched'' for those problem cookies, but cannot locate them, if they're even there at all. And I've never seen a Cookies folder, either. Please keep thinking about this -- your efforts are ''greatly'' appreciated! [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 01:36, 2 September 2013 (UTC)\n"
+                                                    ],
+                                                    "comments": [
+                                                        {
+                                                            "text_blocks": [
+                                                                "::::Update: I can now see my Cookies Folder. It took some doing -- no thanks to Microsoft! -- to find out how to get that folder to display. (It requires un-checking the default setting that hides all \"protected operating system files\".) Unfortunately, the only Wiki cookies I found were quite innocuous. No sign of those problem cookies that force the browser to use https. So I'm right back where I started: '''Still no way to get my browser to display non-secure pages -- and still no browser history for Wikipedia'''. :( [[:en:User:Cgingold|Cgingold]] ([[:en:User talk:Cgingold|talk]]) 03:12, 2 September 2013 (UTC)\n"
+                                                            ],
+                                                            "comments": [],
+                                                            "cosigners": [],
+                                                            "author": "Cgingold",
+                                                            "time_stamp": "03:12, 2 September 2013 (UTC)"
+                                                        }
+                                                    ],
+                                                    "cosigners": [],
+                                                    "author": "Cgingold",
+                                                    "time_stamp": "01:36, 2 September 2013 (UTC)"
+                                                }
+                                            ],
+                                            "cosigners": [],
+                                            "author": "TheDJ",
+                                            "time_stamp": "15:18, 1 September 2013 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Cgingold",
+                                    "time_stamp": "13:18, 1 September 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Cgingold",
+                            "time_stamp": "08:34, 1 September 2013 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n"
+                            ],
+                            "comments": [],
+                            "cosigners": []
+                        }
+                    ],
+                    "heading": " Wikipedia discussion at Village Pump (technical) talk page "
+                }
+            ],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Help Needed: Problems due to Secure site change ==\n",
+                        "\n",
+                        "I'm not even sure how I found my way here to this page, but I am in desperate need of help, as nothing I have tried has made any real difference. Rather than repeat what I've already written over at Wikipedia, I am going to re-post my own initial comment, followed by the entire contents of the discussion that ensued when I created a new section under the same heading I've used here -- which I think may be useful for other editors to read. [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 07:08, 2 September 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Cgingold",
+                    "time_stamp": "07:08, 2 September 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n",
+                        "I) My browser history is absolutely integral to how I do things on the internet. When my browser history first disappeared, I assumed that the problem was somewhere on MY end of things. I racked my brain, I checked everything -- all to no avail. I had no idea that Wiki had switched over to secure pages, so I was really at my wits' end until I just by chance finally noticed that little \"https\" in the URLs. <Light bulb goes on> I then spent an hour googling a variety of search strings in hopes of finding something that would help resolve the problem. Again to no avail. Finally, I came here [to the Village Pump - technical] to see if anybody had raised the issue.\n",
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Help Needed: Problems due to Secure site change "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== My experience with HTTP links ==\n",
+                        "\n",
+                        "The instructions here say, \"''If a user wants to login, the login will happen over HTTPS\u2026 and after they are logged in they stay on the HTTPS version of the Wikimedia site they are using.''\" We-e-ell... I suppose this is ''technically'' true, but it doesn't quite work the way most people would expect.\n",
+                        "\n",
+                        "After logging out and logging in again a couple of days ago (on the English Wikipedia) under the new HTTPS regime, I noticed that when following HTTP links to most other Wikimedia wikis from e-mails and bookmarks, I was not showing up as being logged in (was arriving under the HTTP protocol, of course). My bookmarks to the English Wikipedia and Meta seemed to be okay (I have visited those since the changeover, so presumably I already did something to fix the problem there), but if I tried my bookmark to, say, the Italian Wikibooks (to choose a random one I hadn't visited in a while), I showed up as being logged out. Reloading didn't help. Reloading bypassing the cache didn't help. Manually typing in the prefix \"https://\" in the address bar... that did it. Then I was logged in. (So... I have to actually use HTTPS to \"remind\" WM that I'm already logged in as a registered user?)\n",
+                        "\n",
+                        "Needless to say, I didn't want to manually type in a protocol every time I visited a new Wikimedia wiki (I help to maintain [[Wikimedia News]], so I have occasion to visit \"random\" WM wikis ''all the time'')! So I did something I ''really'' hate doing: I cleared all my cookies. And all my cookie settings (allow/deny/etc.). And my cache. And my browsing history. And then I closed and reopened Firefox (17.0.7).\n",
+                        "\n",
+                        "After logging in to the English Wikipedia (my \"home wiki\") again, I found that when I first visited another WM site (in this case, Meta) \u2014 via a regular wikilink, no less... not even bookmarks or e-mail links yet \u2014 I showed up as ''not logged in''! (And I had to accept a new cookie, which I expected, of course.) Then on to Commons: ''not logged in''! Hey! Whatever happened to SUL?? Okay, so then I reloaded the page. Only then did it tell me \"You are centrally logged in\u2026 Reload the page to apply your user settings.\" Okaaay. Reloaded a second time. Fine. But before reloading, I noticed that I was actually ''already'' logged in as me after the first reload. Something's screwy here... Finally, by going to another \"new\" wiki, I noticed that the first and second reloads can be replaced by two \"local\" page loads of any sort (i.e., following links to other pages on the same wiki). In other words, I'm not logged in when I first bring up a wiki (a Main Page, in particular), but after either reloading or following an internal link, I am logged in. But only ''then'' do I get the message about \"[applying my] user settings\". But at that point that's already been done! Something tells me this is not how it's supposed to work.\n",
+                        "\n",
+                        "So then I tried an old HTTP bookmark (this time to the Czech Wikipedia \u2014 remember, I first logged in to the English Wikipedia). Not logged in. Not in HTTPS. Reloading didn't work. Back to where I started. So then I navigate through HTTPS links (via [[List of Wikipedias]]) back to the Czech Wikipedia. I ''am'' logged in under HTTPS. Okay, back to the List and then to the, oh, Ilokano Wikipedia. I am logged in under HTTPS.\n",
+                        "\n",
+                        "Hmm. Okay, back to an HTTP ''bookmark'' to the Ilokano Wikipedia. Nope. HTTP and not logged in. (But I was just here! Don't you recognize me?) Finally, to an HTTP bookmark to the English Wikipedia. This time, mercifully, I show up as logged in under HTTPS.\n",
+                        "\n",
+                        "So, the moral of this story seems to be: If you explicitly log in to a Wikimedia wiki, HTTP links to that wiki will come up as HTTPS and have you logged in. Following links to any other Wikimedia wiki (assuming they're HTTPS) works, but only after reloading or following a link. But visiting any other wiki through an HTTP link, even though you have purportedly been \"CentralAuth\" logged in to \"all\" of them, you don't get recognized as being logged in and remain an anon under HTTP. Pretty annoying.\n",
+                        "\n",
+                        "So now I have to go through 820 or so bookmarks changing \"http:\" to \"https:\" (not to mention actually visiting all 820 wikis again to set new cookies). Yay. - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 10:45, 2 September 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":When I got \"You are centrally logged in\u2026 Reload the page to apply your user settings.\", I checked [[Special:Preferences]] and found that the setting for \"Always use a secure connection when logged in\" was opposite to what I thought it was. Flipping it and saving, then reloading the appropriate page, got things back in synch. It was necessary to do this separately for meta, commons, etc. --[[User:Redrose64|Redrose64]] ([[User talk:Redrose64|talk]]; [[:en:User:Redrose64|at English Wikipedia]]) 12:09, 2 September 2013 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::Is this [[bugzilla:53538]]? --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 13:40, 2 September 2013 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                ":::: My original report? Yeah, looks like it (although the thing about the late \"centrally logged in\" notice isn't mentioned there). I guess we'll see what happens when 1.22wmf16 is deployed ([[mw:MediaWiki 1.22/Roadmap|over the next few days]]). - [[User:Dcljr|dcljr]] ([[User talk:Dcljr|talk]]) 12:47, 5 September 2013 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Dcljr",
+                                            "time_stamp": "12:47, 5 September 2013 (UTC)"
+                                        },
+                                        {
+                                            "text_blocks": [
+                                                ":::I've been having some trouble staying logged in between projects (i.e. Commons) for a long time - well before https.  But it happens only when I have some scripts enabled (NoScript), and admittedly... I might not have had them all enabled at the start, and so gotten to some state unexpected by the developers.  Have you been using the same sort of script control? [[User:Wnt|Wnt]] ([[User talk:Wnt|talk]]) 18:00, 2 September 2013 (UTC)\n"
+                                            ],
+                                            "comments": [
+                                                {
+                                                    "text_blocks": [
+                                                        "::::What browser are you using? If the problem is that you are logged in when you use HTTPS but not when you use HTTP, then you might wish to install [https://www.eff.org/https-everywhere HTTPS Everywhere], provided that you use a browser compatible with that. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 18:20, 2 September 2013 (UTC)\n"
+                                                    ],
+                                                    "comments": [],
+                                                    "cosigners": [],
+                                                    "author": "Stefan2",
+                                                    "time_stamp": "18:20, 2 September 2013 (UTC)"
+                                                }
+                                            ],
+                                            "cosigners": [],
+                                            "author": "Wnt",
+                                            "time_stamp": "18:00, 2 September 2013 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Stefan2",
+                                    "time_stamp": "13:40, 2 September 2013 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Redrose64",
+                            "time_stamp": "12:09, 2 September 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Dcljr",
+                    "time_stamp": "10:45, 2 September 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " My experience with HTTP links "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Updates on the Https situation ==\n",
+                        "['''Note''': I've copied this from the Village Pump (technical) talk page over at Wikipedia.]\n",
+                        "*'''Update1''' - Hmmm. Has something been tweaked on ''your'' end? (i.e. some lines of code at Wikipedia/Wikimedia?) Just in the last hour I discovered that I was able to access Http pages while I'm logged in -- which I was NOT able to do before (except for a very short period over the weekend). They're also showing up in my browser history, as expected. And I can see that HotCat has returned, as well (though I haven't tried using it as of yet). However -- you knew that was coming, didn't you?? -- there's still some work to be done: When I accessed a couple of articles via redirects, they displayed as though I had suddenly logged out, even though I hadn't done so and was in fact ''demonstrably still logged in!'' (The links on those pages took me to normal pages that displayed properly.) I'll post another update later on today. Needless to say, I'm keeping my fingers crossed that things won't revert to dysfunctionality in the next couple of hours! [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 14:48, 2 September 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "::'''Addendum''' to Update1: Complicating the picture I described in my update above, I just had a couple of pages accessed via redirects display ''properly'' -- but a couple of Category pages displayed improperly, as though I had logged out. So it seems there's no real pattern to whatever the hell is going on. <sigh> [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 15:33, 2 September 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Cgingold",
+                            "time_stamp": "15:33, 2 September 2013 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "*'''Update2''' - Okay, it is now many hours later in the day. The positive developments I noted earlier have held up without reverting to the intractable problems I experienced over the weekend. For the most part, I am able to access Http pages and they display properly -- i.e. the Wiki software recognizes that I am logged in. I can also report that HotCat is functioning normally for me -- another major relief. However, there is still a recurring problem that crops up in a ''seemingly'' random fashion, causing certain pages to display as though I was not logged in -- even though I can go directly to other pages that display normally, without having had to log in again first. I suspect, however, that these problem pages may not be ''entirely'' random -- iow, they may possibly have some feature in common that results in problems with the new software -- mainly because certain pages continue to exhibit this problem every time I access them. Case in point: [[:Category:Biological evolution]], which displays as though I'm just an Anon. IP editor every time.  Guess that'll do it for now. I hope I've given you techies enough \"hints\" to make some headway in tracking down the source of the problem. :) [[User:Cgingold|Cgingold]] ([[User talk:Cgingold|talk]]) 04:32, 3 September 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Cgingold",
+                            "time_stamp": "04:32, 3 September 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Cgingold",
+                    "time_stamp": "14:48, 2 September 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Updates on the Https situation "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Security information ==\n",
+                        "\n",
+                        "When browsing wikipedia (via firefox, if it makes a difference), now in https, getting the security information by pressing the lock icon next to the URL, the browser reports \"you are connected to wikipedia.org which is run by (unknown)\". Similarly, meta.wikimedia.org is also reported \"unknown\". When clicking \"more information\" the browser reports under identity \"owner: This website does not supply ownership information\". Methinks this warrants correction. [[Special:Contributions/87.68.44.102|87.68.44.102]] 10:02, 4 September 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "\n",
+                                ":I was curious, and checked, 12 days later. Using Google Chrome browser, both the identity and certificate seem proper, as <code>meta.wikimedia.org</code>, using SSL with DigiCert High Assurance CA-3 and 128-bit encryption connection SHA-1. I didn't check the entire CA chain, I confess. --[[User:FeralOink|FeralOink]] ([[User talk:FeralOink|talk]]) 13:26, 20 September 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "FeralOink",
+                            "time_stamp": "13:26, 20 September 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "87.68.44.102",
+                    "time_stamp": "10:02, 4 September 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Security information "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "==Wikimedia sites and tracking, documentation==\n",
+                        "\n",
+                        "First, I wanted to mention that HTTPS is working perfectly for me, every time, on every WMf site, with the possible exceptions of Wikidata. '''Thank you'''!\n",
+                        "\n",
+                        "Earlier, on 21 August 2013, inquiries were made by [[User:Risker|Risker]]\n",
+                        "<blockquote>\"Please add a link to some formal statement or roadmap or approved plan that says \"[t]he continued work to improve the security and privacy of Wikimedia project users is a stated goal of the Wikimedia Foundation\". (I'm not doubting it's true, but a footnote/reference helps.) It might also be useful to link to some internal or external site that confirms the use of Wikipedia as a site useful for tracking\"</blockquote> and by [[User:Ace111|Ace111]]\n",
+                        "<blockquote>\"The preamble of this article mentions: \"The Wikipedia project was referenced in several documents as a specific source for tracking users' behavior online\". Which documents are referenced here? Was it discussed somewhere?\"</blockquote>\n",
+                        "These concerns were acknowledged and action was taken to address them by [[User:Seb35|Seb35]]\n",
+                        "<blockquote>\"I just added a link to one document I know, but I don\u2019t know others.\"</blockquote>\n",
+                        "However, I agree with [[User:Ace111|Ace111]]'s subsequent response:\n",
+                        "<blockquote>\"Jimbo's twitter post refers to [http://www.theguardian.com/world/2013/jul/31/nsa-top-secret-program-online-data an NSA slide via The Guardian] with a question: \"Why are we interested in HTTP?\" and an answer \"Because nearly everything a typical user does on the Internet uses HTTP\", followed by examples of web sites such as Facebook, Yahoo, Twitter, myspace, CNN, mail.ru, Wikipedia, Google and Gmail. I don't think this is a proper reference for Wikipedia as a specific source for tracking users' behavior.\"</blockquote>\n",
+                        "[https://twitter.com/jimmy_wales/status/362626509648834560 Jimmy Wales' Twitter message] reads as follows:\n",
+                        "<blockquote>NSA snooping on what YOU are reading at Wikipedia means I want us to go to SSL sooner.  Bastards fuck off. Owly <!-- hxxp owly/nv3I6 Owly is a blacklisted site, so I sorta-obfuscated --></blockquote> \n",
+                        "The Owly-shortened URL directs to [http://static.guim.co.uk/sys-images/Guardian/Pix/audio/video/2013/7/31/1375269604628/KS8-001.jpg this image via The Guardian], which I haven't uploaded, though I guess I should. It is not a COPYVIO, as it is an alleged screen shot of antiquated social media icons in the characteristically MS Paint, circa Win 95 style, of PRISM slides. There is some lettering at the top, in light orange colored font, on a darker orange background, which might say \"COMINT\" (or maybe HUMINT or NOfORN or one of those other acronyms we've had 4 months with which to become familiar). That isn't suficient as a proper reference for Wikipedia as a specific source for tracking users' behavior, just as Ace111 said.  In fact, Jimmy Wales message was directly [https://twitter.com/StevenWalling/status/363397737254879232 replied to by Steven Walling]\n",
+                        "<blockquote>\"the Foundation has not received any requests to date\" https://blog.wikimedia.org/2013/07/18/wikimedia-foundation-letter-transparency-nsa-prism/ \u2026</blockquote> which leads me to wonder whether there were evidence of tracking by the NSA of Wikipedia users and/ or editors et al. Next, even though he sounds full of bravado, the content of Jimmy Wales' Twitter message is rather hostile, specifically,\n",
+                        ":'''Bastards fuck off.'''\n",
+                        "Jimmy Wales as an individual is entitled to tell the NSA to fuck of. But using his personal Twitter account as the basis for Wikimedia's decision to transition to SSL, with that particular content, is representing Wikimedia foundation I would think. We don't tell any government entity to fuck of as official policy, I don't think. We didn't tell Khazakhastan to fuck of, nor Syria, nor Libya, nor North Korea, nor the Taliban. I don't need to list further ''bete-noire'' perceived countries, as you get the idea.  Remember, the NSA is acting as explicitly directed by the elected government of the USA, the executive branch and/ or the Department of Homeland Security. Bad men tell the NSA to do bad things.\n",
+                        "\n",
+                        "I don't want that Twitter message linked in the article, here, please? I fully agree with, and applaud Wikimedia's decision to transition to HTTPS and SSL. If further encryption measures are added in the future, I wouldn't argue against it. \n",
+                        "\n",
+                        "In fact, why is there any need to justify the switch to HTTPS at all? Someone needs to find some non-self-referential external source (or provide better detail from this one, The Guardian article, not Jimmy Wales), or just delete that section entirely, and thus resolve the pesky issue of explaining why SSL is needed. I will take it upon myself to do so, but wanted to explain myself first, and generate discussion, as the AfD folks say!  --[[User:FeralOink|FeralOink]] ([[User talk:FeralOink|talk]]) 01:22, 17 September 2013 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "FeralOink",
+                    "time_stamp": "01:22, 17 September 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": "Wikimedia sites and tracking, documentation"
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Still being forced into using HTTPS on occasion ==\n",
+                        "\n",
+                        "Just now, I had to go thru the once every 30 days log in again.  And despite having that I do NOT want HTTPS, it forced me into HTTPS and I had go and manually delete the cookies yet again!  I understand why you are advocating HTTPS, but they don't apply to me or my use of Wikimedia, so I like to keep things as simple as possible. It's bad enough that each time I visit a Wikimedia site I haven't used since the change I have to go change the preferences for that site to undo the automatic HTTPS, but to have to keep deleting cookies is even worse. [[User:Carolina wren|Carolina wren]] ([[User talk:Carolina wren|talk]]) 02:15, 29 September 2013 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ": This sounds like [[bugzilla:54626|bug 54626]], the fix for which should be deployed starting on Thursday, October 3 and finishing up on October 10. Unless it gets pushed out sooner. [[User:BJorsch (WMF)|BJorsch (WMF)]] ([[User talk:BJorsch (WMF)|talk]]) 13:58, 30 September 2013 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "BJorsch (WMF)",
+                            "time_stamp": "13:58, 30 September 2013 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Carolina wren",
+                    "time_stamp": "02:15, 29 September 2013 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Still being forced into using HTTPS on occasion "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Preference ==\n",
+                        "After this program is implemented, will individual contributors still be able to disable HTTPS if so they desire? [[User:Gryllida|Gryllida]] 22:21, 17 September 2014 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ": Why is the above question written in the future tense? This was implemented last year. Individual contributors can disable HTTPS at [[Special:Preferences#mw-prefsection-personal]] by unchecking the \"Always use a secure connection when logged in\" checkbox. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 22:52, 17 September 2014 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::I'm referring to the planned change.  In October 2014, some projects (not globally; currently this is on Russian Wikipedia) plan to roll out https by default to unregistered contributors. Some others are considering following their example and I'm trying to access the implications of such change. [[User:Gryllida|Gryllida]] 23:03, 17 September 2014 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Gryllida",
+                                    "time_stamp": "23:03, 17 September 2014 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Stefan2",
+                            "time_stamp": "22:52, 17 September 2014 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Gryllida",
+                    "time_stamp": "22:21, 17 September 2014 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Preference "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== API from contributor's username ==\n",
+                        "I understand that the program implies that where I visit a page, I will be automatically redirected to HTTPS.  Will the same happen for API queries I send from a bot/script? [[User:Gryllida|Gryllida]] 22:21, 17 September 2014 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "::I'm referring to the planned change.  In October 2014, some projects (not globally; currently this is on Russian Wikipedia as a result of community consencus) plan to roll out https by default to unregistered contributors. Some others are considering following their example and I'm trying to access the implications of such change. [[User:Gryllida|Gryllida]] 23:04, 17 September 2014 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Gryllida",
+                            "time_stamp": "23:04, 17 September 2014 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Gryllida",
+                    "time_stamp": "22:21, 17 September 2014 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " API from contributor's username "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Common HTTPS access issues ==\n",
+                        "What is the common nature of the HTTPS access issues the https{{@}}wikimedia.org folks encounter, as suggested [[HTTPS#Help.21|here]]? I e-mailed them in but got no response. I would like to know who we would be locking out here and why. [[User:Gryllida|Gryllida]] 22:21, 17 September 2014 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ": HTTPS access is or has been blocked by the authorities in some countries (see [[{{SUBJECTPAGENAME}}#Excluded Countries]]). I assume that users in these countries may run into problems if they have to use an HTTPS connection. I do not know if users also may have other problems. --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 22:55, 17 September 2014 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Stefan2",
+                            "time_stamp": "22:55, 17 September 2014 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ":I was told that this was addressed by extensive EventLogging tests that didn't reveal trouble of \"random crappy ISP setup\" sort, but only revealed country-specific issues (and this program is being rolled out outside of these countries as I understand). Would be useful to have some documentation of tests, for reference. [[User:Gryllida|Gryllida]] 22:57, 17 September 2014 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Gryllida",
+                            "time_stamp": "22:57, 17 September 2014 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Gryllida",
+                    "time_stamp": "22:21, 17 September 2014 (UTC)"
+                }
+            ],
+            "heading": " Common HTTPS access issues "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Opting out for unregistered contributors ==\n",
+                        "This is perhaps a slightly useless question, as the folks can use another internet access point to register, and opt out ''then'' (if the preference is still available). But is there currently no means to opt out ''without'' registering? See also [[bugzilla:20151]]. Can we think about it again? To me, a lot of preferences appear to be harmless to expose to IP contributors (HTTPS/HTTP toggle being one of them). [[User:Gryllida|Gryllida]] 22:57, 17 September 2014 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":To clarify: I'm referring to the planned change.  In October 2014, some projects (not globally; currently this is on Russian Wikipedia) plan to roll out https by default to unregistered contributors. Some others are considering following their example and I'm trying to access the implications of such change. [[User:Gryllida|Gryllida]] 23:04, 17 September 2014 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::Where do I find information about the planned change? I hadn't heard of it until you mentioned it on this talk page.\n",
+                                        "::Users who are not logged in can still change many settings by using a tool such as [[w:Greasemonkey]]. However, I realise that this method isn't very user-friendly. I don't know if this method provides a way to opt out from forced HTTPS.\n",
+                                        "::Are you suggesting that some users won't be able to visit any Russian Wikipedia pages (including [[:ru:Special:UserLogin]]?) unless the users are logged in when the page is accessed? --[[User:Stefan2|Stefan2]] ([[User talk:Stefan2|talk]]) 23:28, 17 September 2014 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                ":::I have no idea what plans Gryllida is talking about, but official plans are at [[mw:Wikimedia Engineering/2014-15 Goals#Site Operations and Site Architecture]].\n",
+                                                ":::So far zh.wiki and others had an opt-out from the forced HTTPS for registered users but I seriously doubt there will be any opt-in mechanism for further HTTPS changes. --[[User:Nemo_bis|Nemo]] 06:06, 18 September 2014 (UTC)\n"
+                                            ],
+                                            "comments": [
+                                                {
+                                                    "text_blocks": [
+                                                        "::::No, they don't plan access changes. [[:ru:\u0412\u0438\u043a\u0438\u043f\u0435\u0434\u0438\u044f:\u0424\u043e\u0440\u0443\u043c/\u0410\u0440\u0445\u0438\u0432/\u041f\u0440\u0435\u0434\u043b\u043e\u0436\u0435\u043d\u0438\u044f/2013/09#.D0.92.D0.BA.D0.BB.D1.8E.D1.87.D0.B5.D0.BD.D0.B8.D0.B5_.D0.BF.D1.80.D0.BE.D1.82.D0.BE.D0.BA.D0.BE.D0.BB.D0.B0_https_.D0.B4.D0.BB.D1.8F_.D0.B2.D1.81.D0.B5.D1.85_.D0.BF.D0.BE.D0.BB.D1.8C.D0.B7.D0.BE.D0.B2.D0.B0.D1.82.D0.B5.D0.BB.D0.B5.D0.B9|Local consensus]] at Russian Wikipedia. Oh, and they opted in [[HTTPS/Beta_program|here]]. [[User:Gryllida|Gryllida]] 09:09, 18 September 2014 (UTC)\n"
+                                                    ],
+                                                    "comments": [],
+                                                    "cosigners": [],
+                                                    "author": "Gryllida",
+                                                    "time_stamp": "09:09, 18 September 2014 (UTC)"
+                                                }
+                                            ],
+                                            "cosigners": [],
+                                            "author": "Nemo_bis",
+                                            "time_stamp": "06:06, 18 September 2014 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Stefan2",
+                                    "time_stamp": "23:28, 17 September 2014 (UTC)"
+                                },
+                                {
+                                    "text_blocks": [
+                                        ":: [[User:Gryllida|Gryllida]], Where did you find this date \"October 2014\", \u0441an you give a link to us? [[User:Sunpriat|Sunpriat]] ([[User talk:Sunpriat|talk]]) 20:08, 26 September 2014 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Sunpriat",
+                                    "time_stamp": "20:08, 26 September 2014 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Gryllida",
+                            "time_stamp": "23:04, 17 September 2014 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Gryllida",
+                    "time_stamp": "22:57, 17 September 2014 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Opting out for unregistered contributors "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Russian Wikinews ==\n",
+                        "Please, let me know when you turn on HTTPS for [[n:ru:|Russian Wikinews]] ([https://meta.wikimedia.org/w/index.php?diff=9957749&oldid=5989231 diff]). --sasha ([[User:Krassotkin|krassotkin]]) 07:36, 22 September 2014 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "* [https://ru.wikinews.org/w/index.php?diff=336990&oldid=336650 Done]. Thanks! --sasha ([[User:Krassotkin|krassotkin]]) 07:16, 5 December 2014 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Krassotkin",
+                            "time_stamp": "07:16, 5 December 2014 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Krassotkin",
+                    "time_stamp": "07:36, 22 September 2014 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Russian Wikinews "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Performance impact ==\n",
+                        "\n",
+                        "Do performance issues with HTTPS show up in any way on navigation timing EventLogging logs like those from which [https://gdash.wikimedia.org/dashboards/frontend/] is extracted? Consider the case \"the page takes so long to load over HTTPS that it times out in my browser\" for people with extremely slow connections. It would be nice to be at least ''able'' to assess the impact on specific countries or Wikimedia subdomains, for instance. IIRC even the simple but often-quoted [https://docs.google.com/presentation/d/1MtDBNTH1g7CZzhwlJ1raEJagA8qM3uoV7ta6i66bO2M/present] mention this need for breakdown. --[[User:Nemo_bis|Nemo]] 13:25, 12 June 2015 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Nemo_bis",
+                    "time_stamp": "13:25, 12 June 2015 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Performance impact "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "==Turning off HTTPS==\n",
+                        "This article's content states: \"If so, you can turn off HTTPS in your user preferences (unless HSTS is set for the domain in question[2]). Go to the \"User profile\" tab, then uncheck the box labelled \"Always use a secure connection when logged in\". You will need to logout and login for the preference to take effect. But remember, you will still need to log in using HTTPS.\"  Up until today, I did not use HTTPS and was editing just fine.  Today, I am being forced to use HTTPS and there is nothing in the preferences screen for me to control this.  I don't want HTTPS (loss of saved edit summary info).  What can I do to get back to HTTP? [[User:Hmains|Hmains]] ([[User talk:Hmains|talk]]) 17:14, 12 June 2015 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":Sorry, that's entirely my fault for not keeping this page as up to date as I'd had hoped to. This is the answer I got when I asked was that any form of opt-out would also leave potential security risks in our implementation which make it difficult to safeguard those who do not opt-out.  Because of this, we\u2019ve made implementation decisions that preclude any option to disable HTTPS, whether logged in or not.  This renders the current opt-out option ineffective, and the option will be removed at a later date after we\u2019ve completed the transition process.\n",
+                                ":I'm trying to figure out if there's a good solution to the edit summary info problem. /[[User:Johan (WMF)|Johan (WMF)]] ([[User talk:Johan (WMF)|talk]]) 19:27, 12 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::The edit summary issue - Users are reporting that the issue only affects IE versions prior to IE 11. One potential work around is to upgrade IE or use a different browser. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]])\n",
+                                        "\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": []
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Johan (WMF)",
+                            "time_stamp": "19:27, 12 June 2015 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Hmains",
+                    "time_stamp": "17:14, 12 June 2015 (UTC)"
+                }
+            ],
+            "heading": "Turning off HTTPS"
+        },
+        {
+            "subsections": [
+                {
+                    "subsections": [],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "=== Help! My code is broken! ===\n",
+                                "\"Are you a bot maintainer... and you're seeing weird or broken behavior after this switch?\" '''YES.''' \"Hopefully you can fix that easily.\" ''Still hoping. It's apparently not as easy as simply changing \"http:\" to \"https:\" in the code''\n",
+                                "\n",
+                                "For Gadget authors, simply modifying any hardcoded urls from \"<nowiki>http://...</nowiki>\" to \"//...\" should fix the issue (this is called using \"protocol relative urls\"). ''My bot logs me in if I use http:// Neither https:// nor // work to even do that.\n",
+                                "\n",
+                                "\"For bot maintainers, you have a couple of choices.\"\n",
+                                "# login as the bot and select the preference to not use HTTPS for that account ('''citation needed''')\n",
+                                "# update your code to use SSL instead. ''Do you mean [[en:Secure Sockets Layer|Secure Sockets Layer]]? How do I update my code to use it?\n",
+                                "\n",
+                                "\"If you use Pywikipediabot, please update to the latest version (More technical details: [https://gerrit.wikimedia.org/r/80003],[https://gerrit.wikimedia.org/r/80006]) and read [[mailarchive:pywikipedia-l/2013-August/008214.html|this]] mailing list post for more information.\"\n",
+                                ":I don't believe I use Pywikipediabot. Can't you do better than linking to ''code reviews'' for \"more information\"?\n",
+                                "What's the difference between a \"Secure Sockets Layer\" and a \"[[en:root certificate|root certificate]]? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 13:53, 14 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "\n",
+                                        "*'''Curiouser and curiouser'''. Legobot, which uses the [https://github.com/legoktm/harej-bots same botclasses.php] library, is still [https://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_comment/Biographies&action=history working]. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 16:56, 14 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "16:56, 14 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "13:53, 14 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ":There has been some divergence between versions of the botclasses.php library. See [[en:Wikipedia:Village pump (technical)#Impending bot armageddon]] for the console output from my program. Based on the prior conversation linked above, I switched my version to use JSON. I just copied Legobot's version into my system, and that errors differently:\n",
+                                "\n",
+                                "Logging in...<br>\n",
+                                "POST: http://en.wikipedia.org/w/api.php?action=login&format=php (1.2910737991333 s) (194 b)<br>\n",
+                                "POST: http://en.wikipedia.org/w/api.php?action=login&format=php (1.1130640506744 s) (253 b)\n",
+                                "...done.\n",
+                                "\n",
+                                "Checking for transclusions...\n",
+                                "\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.23901295661926 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.34102010726929 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.52202987670898 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.37602114677429 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.53903079032898 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.35002017021179 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.51002883911133 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.57503318786621 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.5550320148468 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.36001992225647 s) (0 b)<br>\n",
+                                "GET: http://en.wikipedia.org/w/api.php?action=query&list=embeddedin&eititle=Template%3ARequested+move%2Fdated&eilimit=500&format=php (0.36002087593079 s) (0 b)<br>\n",
+                                "\n",
+                                "Fatal error: Uncaught exception 'Exception' with message 'HTTP Error.' in C:\\php\\botclasses.php:214<br>\n",
+                                "Stack trace:<br>\n",
+                                "#0 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 10)\n",
+                                "#1 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 9)\n",
+                                "#2 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 8)\n",
+                                "#3 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 7)\n",
+                                "#4 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 6)\n",
+                                "#5 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 5)\n",
+                                "#6 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 4)\n",
+                                "#7 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 3)\n",
+                                "#8 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 2)\n",
+                                "#9 C:\\php\\botclasses.php(212): wikipedia->query('?action=query&l...', NULL, 1)\n",
+                                "#10 C:\\php\\botclasses.php(494): wikipedia->query('?action=query&l...')\n",
+                                "#11 C:\\php\\requestedmoves.php(53): wikipedia->getTransclusions in C:\\php\\botclasses.php on line 214\n",
+                                "\n",
+                                "<syntaxhighlight lang=\"php\">\n    /**\n     * Sends a query to the api.\n     * @param $query string The query string.\n     * @param $post string POST data if its a post request (optional).\n     * @param $repeat int how many times we've repeated this request\n     * @return array The api result.\n     * @throws Exception on HTTP errors\n     **/\n    function query ($query,$post=null,$repeat=0) {\n\t    global $AssumeHTTPFailuresAreJustTimeoutsAndShouldBeSuppressed;\n        if ($post==null) {\n            $ret = $this->http->get($this->url.$query);\n        } else {\n            $ret = $this->http->post($this->url.$query,$post);\n        }\n\t    if ($this->http->http_code() == \"504\" && $AssumeHTTPFailuresAreJustTimeoutsAndShouldBeSuppressed) {\n\t\t\treturn array(); // Meh\n\t    }\n\t\tif ($this->http->http_code() != \"200\") {\n\t\t\tif ($repeat < 10) {\n\t\t\t\treturn $this->query($query,$post,++$repeat);\n\t\t\t} else {\n\t\t\t\tthrow new Exception(\"HTTP Error.\");    // this is line 214\n\t\t\t}\n\t\t}\n        return unserialize($ret);\n    }\n</syntaxhighlight>\n",
+                                "I don't know whether this would make any difference, but unlike most other bots, mine run under the Windows 7 operating system. -- [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:40, 14 June 2015 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "18:40, 14 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "It runs under [[en:Windows PowerShell|Windows PowerShell]]. I'm wondering whether I need to do anything special to enable HTTPS under PowerShell. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:55, 14 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":'''BINGO!''' - this seems helpful: [https://github.com/AppVeyor/AppRolla/wiki/Configuring-Windows-PowerShell-remoting Enabling HTTPS protocol for PowerShell remoting] [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 19:07, 14 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "::...but complicated. Buy an SSL certificate? Generate my own?? Help! [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 19:19, 14 June 2015 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Wbm1058",
+                                            "time_stamp": "19:19, 14 June 2015 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "19:07, 14 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "18:55, 14 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "Sigh, it's awful quiet here today. Why was this implemented just before a weekend? So this is my current understanding (I have limited confidence in its accuracy). The library I'm using does not support HTTPS. It works for Legobot because that bot is on a \"framework\" (UNIX?) that supports HTTPS. I can either update my library code to support HTTPS, or update my Windows PowerShell \"framework\" to support HTTPS. I have no idea which is the easier approach. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 21:34, 14 June 2015 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "21:34, 14 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "That code you linked to does not support a redirect (HTTP status/code 301) which is what you get when you try to request a HTTP:// URL instead of HTTPS:// . Perhaps it works for you when you change the URLs you use with your bot from HTTP:// to HTTPS:// which is what I assume Legobot does. - [[User:JanZerebecki|Jan Zerebecki]] 11:00, 15 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":My guess is that [[en:User:Legobot|Legobot]] works because the ''platform'' it runs on, the \"Wikimedia Labs cluster\" or whatever it's called these days, supports \"301 redirects\". I have copied and tried to run the identical code on my platform, Windows PowerShell, without success. Note, however, that despite claims that now absolutely no HTTP works anymore, the Logging in... POST: request (in the example above) still ''works'' for me. If I change that to try to login using HTTPS:, it does ''not'' work! [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 12:42, 15 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "::How does logging in via https fail? Can you post debug / log output? - [[User:JanZerebecki|Jan Zerebecki]] 13:31, 15 June 2015 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "JanZerebecki",
+                                            "time_stamp": "13:31, 15 June 2015 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "12:42, 15 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "JanZerebecki",
+                            "time_stamp": "11:00, 15 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "I just see in my console output:\n",
+                                "<syntaxhighlight lang=\"text\">\nLogging in...\nPOST: https://en.wikipedia.org/w/api.php?action=login&format=json (0.82604718208313 s) (0 b)\nLogin error: \n</syntaxhighlight>\n",
+                                "I guess I should see if I can write more diagnostic information to the console. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 15:20, 15 June 2015 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "15:20, 15 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "<syntaxhighlight lang=\"php\">\n /**\n     * This function takes a username and password and logs you into wikipedia.\n     * @param $user Username to login as.\n     * @param $pass Password that corrisponds to the username.\n     * @return array\n     **/\n    function login ($user,$pass) {\n    \t$post = array('lgname' => $user, 'lgpassword' => $pass);\n        $ret = $this->query('?action=login&format=json',$post);\n        /* This is now required - see http://bugzilla.wikimedia.org/show_bug.cgi?id=23076 */\n        if ($ret['login']['result'] == 'NeedToken') {\n        \t$post['lgtoken'] = $ret['login']['token'];\n        \t$ret = $this->query( '?action=login&format=json', $post );\n        }\n        if ($ret['login']['result'] != 'Success') {\n            echo \"Login error: \\n\";\n            print_r($ret);\n            die();\n        } else {\n            return $ret;\n        }\n    }\n</syntaxhighlight>\n",
+                                "So my 'login' 'result' != 'Success' and $ret seems to be null as nothing prints -- [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 15:32, 15 June 2015 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "15:32, 15 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "I printed out what it should look like when it works, which it does when I simple edit to remove the single character \"s\"\n",
+                                "<syntaxhighlight lang=\"text\">\nLogging in...\nPOST: http://en.wikipedia.org/w/api.php?action=login&format=json (0.86704897880554 s) (146 b)\nPOST: http://en.wikipedia.org/w/api.php?action=login&format=json (1.4270820617676 s) (190 b)\nArray\n(\n    [login] => Array\n        (\n            [result] => Success\n            [lguserid] => 17216044\n            [lgusername] => RMCD bot\n            [lgtoken] => bd5ea22dde5601241c9a1da1eeedb5f5\n            [cookieprefix] => enwiki\n            [sessionid] => 324aa437fffa48afd8c7ac6db4754a7f\n        )\n\n)\n...done.\n</syntaxhighlight>\n",
+                                "Hopefully no beans spilled here. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 15:56, 15 June 2015 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "15:56, 15 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "Th sessionid and token are secrets. You should logout with that sessionid to make it invalid.\n",
+                                "\n",
+                                "Perhaps on your PHP installation the openssl extension is not enabled ( http://de2.php.net/manual/en/book.openssl.php ). You could try to run the following as a php script to test if a normal https request works:\n",
+                                "<syntaxhighlight lang=\"php\">error_reporting(-1); var_dump(file_get_contents(\"https://en.wikipedia.org/wiki/Main_Page\"));</syntaxhighlight>\n",
+                                "- [[User:JanZerebecki|Jan Zerebecki]] 16:06, 15 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":I see. My bot logs in every 15 minutes, and each time it logs in it gets a new sessionid. I just changed my pw so now I have a new token.\n",
+                                        ":Well, of course I don't have the openssl extension installed. I just have a minimum, bare-bones php installation, just what is needed to run my bots and nothing more. I will get right on installing http://www.openssl.org/\n",
+                                        ":Nothing on the help page [[HTTPS]] says I needed to do that!! [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 16:40, 15 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "16:40, 15 June 2015 (UTC)"
+                                },
+                                {
+                                    "text_blocks": [
+                                        ": So [http://www.openssl.org/source/ here], do I just need to get the one marked \"[LATEST]\", or do I need to get more than one of these? It's not clear on that page what I need to do. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:01, 15 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "17:01, 15 June 2015 (UTC)"
+                                },
+                                {
+                                    "text_blocks": [
+                                        ": [http://www.openssl.org/support/faq.html#MISC2 The INSTALL file explains how to install this library.] Where is the \"INSTALL file\"? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:07, 15 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "17:07, 15 June 2015 (UTC)"
+                                },
+                                {
+                                    "text_blocks": [
+                                        ": I guess I need to install WinZip to open up that GNU Zipped Archive file. What a user-unfriendly pain. I clicked the wrong button and it started zipping up every file on my machine. I had WinZip on an older machine of mine, seems that the newer software gets, the more cumbersome it gets. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:38, 15 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "17:38, 15 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "JanZerebecki",
+                            "time_stamp": "16:06, 15 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "::OK, my 21-day trial version has unpacked the .gz file, and fortunately it only was zipping up my old downloads, so I can probably just recycle-bin them. Now I have found the INSTALL.W64 file:\n",
+                                "<syntaxhighlight lang=\"text\">\nINSTALLATION ON THE WIN64 PLATFORM\n ----------------------------------\n\n Caveat lector\n -------------\n\n As of moment of this writing Win64 support is classified \"initial\"\n for the following reasons.\n\n - No assembler modules are engaged upon initial 0.9.8 release.\n - API might change within 0.9.8 life-span, *but* in a manner which\n   doesn't break backward binary compatibility. Or in other words,\n   application programs compiled with initial 0.9.8 headers will\n   be expected to work with future minor release .DLL without need\n   to re-compile, even if future minor release features modified API.\n - Above mentioned API modifications have everything to do with\n   elimination of a number of limitations, which are normally\n   considered inherent to 32-bit platforms. Which in turn is why they\n   are treated as limitations on 64-bit platform such as Win64:-)\n   The current list comprises [but not necessarily limited to]:\n\n   - null-terminated strings may not be longer than 2G-1 bytes,\n     longer strings are treated as zero-length;\n   - dynamically and *internally* allocated chunks can't be larger\n     than 2G-1 bytes;\n   - inability to encrypt/decrypt chunks of data larger than 4GB\n     [it's possibly to *hash* chunks of arbitrary size through];\n\n   Neither of these is actually big deal and hardly encountered\n   in real-life applications.\n\n Compiling procedure\n -------------------\n\n You will need Perl. You can run under Cygwin or you can download\n ActiveState Perl from http://www.activestate.com/ActivePerl.\n\n You will need Microsoft Platform SDK, available for download at\n http://www.microsoft.com/msdownload/platformsdk/sdkupdate/. As per\n April 2005 Platform SDK is equipped with Win64 compilers, as well\n as assemblers, but it might change in the future.\n\n To build for Win64/x64:\n\n > perl Configure VC-WIN64A\n > ms\\do_win64a\n > nmake -f ms\\ntdll.mak\n > cd out32dll\n > ..\\ms\\test\n\n To build for Win64/IA64:\n\n > perl Configure VC-WIN64I\n > ms\\do_win64i\n > nmake -f ms\\ntdll.mak\n > cd out32dll\n > ..\\ms\\test\n\n Naturally test-suite itself has to be executed on the target platform.\n\n Installation\n ------------\n\n TBD, for now see INSTALL.W32.\n</syntaxhighlight>\n",
+                                "\n",
+                                "Sigh. Now I need to install Perl and Microsoft Platform SDK, then ''pray''. I'm not feeling good about this. Do I ''need'' to do all this to get it to work? Is there another way? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:39, 15 June 2015 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "18:39, 15 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "'''!''' [http://de2.php.net/manual/en/openssl.requirements.php Requirements] - for windows it might be better to just get the setup at http://gnuwin32.sourceforge.net/packages/openssl.htm\n",
+                                "\n",
+                                "instead of the sources and try to compile 'em yourself ^_~\n",
+                                "Thanks, poo flanders! I should have noticed that before! [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 19:37, 15 June 2015 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "19:37, 15 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "I heard that you only need to enable the extension, and that the Windows version of PHP already comes with everything needed for that, but I never tried it. - [[User:JanZerebecki|Jan Zerebecki]] 19:54, 15 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "\n",
+                                        ":{{ping|Wbm1058}}: To unzip gzip files on windows, use the program 7zip. SSL and TLS are alternative names for HTTPS (technically that's lieing slightly, but its close enough for this conversation). Don't worry about root certificate store for now. I recommend against trying to compile php from scratch and link OpenSSL to it (I think that's what you are trying to do above). That's a really complicated way of doing it. The reason why other people's bots work and yours don't is probably because you're running windows, and php on windows is a bit iffy in what extensions it default installs.\n",
+                                        ":Now for what you need to do, per http://php.net/manual/en/wrappers.http.php (I'm assuming your bot uses php's f_open wrappers to do its communication) you need the openssl extension installed, and at least php version 4.3. You need to enable the OpenSSL php extension (See http://www.herongyang.com/PKI/HTTPS-PHP-Configure-PHP-OpenSSL-on-Windows.html for some instructions). PHP also needs to have access to the libeay32.dll file. This should come with php, but may be in the wrong directory. http://php.net/manual/en/install.windows.extensions.php#install.windows.extensions.overview and http://php.net/manual/en/openssl.installation.php may also be helpful links. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 20:39, 15 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "::Hi, nice to see someone else join the party. My library source is at [[en:User:RMCD bot/botclasses.php]]. I see two fopen calls there, but both are commented out. Others wrote this, and I have only a limited understanding of how it works. It looks like it uses the [http://de2.php.net/manual/en/book.curl.php Client URL library]. I trust that can work under HTTPS. Some of your links are interesting; I'm reading more on those sites to see if I can gain more insight. Thanks, [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 21:45, 15 June 2015 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Wbm1058",
+                                            "time_stamp": "21:45, 15 June 2015 (UTC)"
+                                        },
+                                        {
+                                            "text_blocks": [
+                                                "::Yes indeed, it claims to support HTTPS, and php_curl.dll is part of my installation. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 21:54, 15 June 2015 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Wbm1058",
+                                            "time_stamp": "21:54, 15 June 2015 (UTC)"
+                                        },
+                                        {
+                                            "text_blocks": [
+                                                "::Oh yes, libeay32.dll is also required by php_curl.dll so I have that installed already. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 22:10, 15 June 2015 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Wbm1058",
+                                            "time_stamp": "22:10, 15 June 2015 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Bawolff",
+                                    "time_stamp": "20:39, 15 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "JanZerebecki",
+                            "time_stamp": "19:54, 15 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "'''Good news''': [http://www.herongyang.com/PKI/HTTPS-PHP-Test-OpenSSL-with-file_get_contents.html This test] to connect the yahoo login HTTPS server was successful!<br>\n",
+                                "'''Bad news''': I still get the '''Login error:''' as shown above, with (0 b) - zero bytes - returned. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 22:49, 15 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":So there's two ways to make connections on PHP - fopen, or curl. Looks like you're using Curl. Most of my comment above was assuming fopen. http://stackoverflow.com/questions/316099/cant-connect-to-https-site-using-curl-returns-0-length-content-instead-what-c might be helpful to you. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]])\n",
+                                        "::Thanks! Very helpful! Now I feel like the solution is in sight... I wonder why they commented out the curl_error lines? After activating them, I see:\n",
+                                        "::'''Error: SSL certificate problem: unable to get local issuer certificate''' [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 00:29, 16 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "::This seems helpful: [https://web.archive.org/web/20190517065614/http://support.gnip.com/articles/curl-on-win7.html cURL on Windows]. I never did anything special before to install cURL, I've just used what came with PHP (in fact, I didn't realize until now that it was a separate package). [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 00:45, 16 June 2015 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Wbm1058",
+                                            "time_stamp": "00:45, 16 June 2015 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "00:29, 16 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "22:49, 15 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n"
+                            ],
+                            "comments": [],
+                            "cosigners": []
+                        }
+                    ],
+                    "heading": " Help! My code is broken! "
+                },
+                {
+                    "subsections": [],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "===Root certificate issue===\n",
+                                ":::(This is the root certificate problem we were talking about earlier). You need to download http://curl.haxx.se/ca/cacert.pem , put it somewhere on your computer, then set <code>curl.cainfo=c:\\php\\cacert.pem</code> (replace c:\\php\\cacert.pem with where ever you saved the file) in your php.ini config file. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 04:31, 16 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::::'''Q.''' Why did the site I linked above tell me to \"Rename this file from cacert.pem to curl-ca-bundle.crt\"? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 11:35, 16 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "11:35, 16 June 2015 (UTC)"
+                                },
+                                {
+                                    "text_blocks": [
+                                        "::::'''A.''' I see, per http://curl.haxx.se/docs/sslcerts.html\n",
+                                        ":::::If you're using the curl command line tool, you can specify your own CA cert path by setting the environment variable CURL_CA_BUNDLE to the path of your choice.\n",
+                                        "\n",
+                                        ":::::If you're using the curl command line tool on Windows, curl will search for a CA cert file named \"curl-ca-bundle.crt\" in these directories and in this order:\n",
+                                        "\n",
+                                        ":::::#application's directory\n",
+                                        ":::::#current working directory\n",
+                                        ":::::#Windows System directory (e.g. C:\\windows\\system32)\n",
+                                        ":::::#Windows Directory (e.g. C:\\windows)\n",
+                                        ":::::#all directories along %PATH%\n",
+                                        "::::-- [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 11:46, 16 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "11:46, 16 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Bawolff",
+                            "time_stamp": "04:31, 16 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "'''OK'''. The instructions at [https://web.archive.org/web/20190517065614/http://support.gnip.com/articles/curl-on-win7.html cURL on Windows] moved me forward towards reviving my bot, though I'm not sure all of that was necessary for my application. However, I got to the instruction \"Note that if you can not get cURL SSL enabled, you have the option to run cURL in an insecure mode\" and I was still getting the same error. So I punted with help I found [http://stackoverflow.com/questions/24611640/curl-60-ssl-certificate-unable-to-get-local-issuer-certificate here], and solved this problem by adding one line of code <code>curl_setopt($this->ch, CURLOPT_SSL_VERIFYPEER, false);</code> which \"helped to circumvent the problem, but totally missed the idea of https and the certification system\". But I was able to sleep knowing that my bots were finally running again. Upon returning here, I found the missing piece waiting for me, commented out my \"CURLOPT_SSL_VERIFYPEER \u2192 false\" band-aid, and added <code>curl.cainfo=c:\\php\\curl-ca-bundle.crt</code> to my php.ini config file. So everything is happy now, and all that remains is for me to clean up, and update my [[en:User:RMCD bot/botclasses.php|online copy of the library]].\n",
+                                "\n",
+                                "Now I see that the setup at http://gnuwin32.sourceforge.net/packages/openssl.htm is way out of date, and for that reason I probably shouldn't have installed it. I picked one of the \"Light\" packages from [http://slproweb.com/products/Win32OpenSSL.html this site] (didn't really know which was best) and installed it as well, but I don't know if that was necessary either, or something already bundled in PHP.\n",
+                                "\n",
+                                "One trick to \"downloading\" the certificate file. All the places I've seen it just have it as a plain-text file that displays in the web browser. I haven't seen any places where you can just download it by clicking a button. I resorted to cut & paste into Notepad. Is there an easier way? When saving it you need to be careful not to save it as \"curl-ca-bundle.crt.txt\" -- when it's correctly saved, Windows recognizes it as a \"Security Certificate\" file type. Looking at the \"properties\" of the .crt file, I see that it opens with \"Crypto Shell Extensions\". There is also an option to \"Install Certificate\", which opens the \"Certificate Import Wizard\" which allows me to import the certificate to a \"certificate store\" which is automatically determined by the wizard. Apparently it isn't necessary to import it to a store. I see that the certificate is issued to and by Equifax Secure Certificate Authority, and is valid to 8/22/2018.\n",
+                                "\n",
+                                "One remaining question: It seems that the \"Bundle of CA Root Certificates\" is periodically updated. Will I be required to update this at some point in the future, and if so, how will I know when it's needed? What will happen if I don't update it in time? [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:35, 16 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":Probably not. Only if Wikimedia changes CA's to something currently not in the root certs. That sort of thing doesn't happen very often (Although it does happen). The current root certificate should have been in the bundle for about 7 years now. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 03:19, 18 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "::Do the [https://hexatomium.github.io/2015/06/26/ms-very-quietly-adds-18-new-trusted-root-certs/ changes to Windows root certificates] change anything for us? --[[User:Nemo_bis|Nemo]] 19:53, 27 June 2015 (UTC)\n"
+                                            ],
+                                            "comments": [
+                                                {
+                                                    "text_blocks": [
+                                                        ":::No, it only matters (in terms of accessing Wikimedia websites) if either we change our root certificate at some point, which is unlikely in the near future (Or if MS for some reason decided to remove the GlobalSign Root CA cert that we use, but that would be extremely unlikely anytime soon). Although Microsoft's behaviour there is kind of odd... [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 11:09, 1 July 2015 (UTC)\n"
+                                                    ],
+                                                    "comments": [],
+                                                    "cosigners": [],
+                                                    "author": "Bawolff",
+                                                    "time_stamp": "11:09, 1 July 2015 (UTC)"
+                                                }
+                                            ],
+                                            "cosigners": [],
+                                            "author": "Nemo_bis",
+                                            "time_stamp": "19:53, 27 June 2015 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Bawolff",
+                                    "time_stamp": "03:19, 18 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "18:35, 16 June 2015 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "re: \"{{tq|I see that the certificate is issued to and by Equifax Secure Certificate Authority, and is valid to 8/22/2018.}}\" -- that's just the first of many certificates in the bundle that Windows shows you. After editing the bundle with Notepad to remove that expired certificate, Windows showed me the next certificate in the bundle, which hasn't expired yet: issued to and by GlobalSign Root CA, valid from 9/1/1998 to 1/28/2028 [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 01:42, 2 October 2021 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "01:42, 2 October 2021 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n"
+                            ],
+                            "comments": [],
+                            "cosigners": []
+                        }
+                    ],
+                    "heading": "Root certificate issue"
+                },
+                {
+                    "subsections": [],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "=== Updating from PHP version 7.0.12 to 7.0.28 ===\n",
+                                "{{collapse top|PHP problem solved}}\n",
+                                "I'm trying to upgrade from the version I successfully installed in October 2016 using the configuration described in the sections above. I wasn't expecting to run into any major roadblocks as I'm just trying to update for the latest bug and security fixes, and not to the next major release 7.1 or 7.2, but I've run into something I can't figure out.\n",
+                                "\n",
+                                "Version 7.0.12 has been successfully running in production since 10/2016. Here is what phpinfo() configuration information tells me:\n",
+                                "<syntaxhighlight lang=\"text\">curl\n\ncURL support => enabled\ncURL Information => 7.50.3\nAge => 3\nFeatures\nAsynchDNS => Yes\nCharConv => No\nDebug => No\nGSS-Negotiate => No\nIDN => Yes\nIPv6 => Yes\nkrb4 => No\nLargefile => Yes\nlibz => Yes\nNTLM => Yes\nNTLMWB => No\nSPNEGO => Yes\nSSL => Yes\nSSPI => Yes\nTLS-SRP => No\nHTTP2 => No\nGSSAPI => No\nKERBEROS5 => Yes\nUNIX_SOCKETS => No\nPSL => No\nProtocols => dict, file, ftp, ftps, gopher, http, https, imap, imaps, ldap, pop3, pop3s, rtsp, scp, sftp, smtp, smtps, telnet, tftp\nHost => i386-pc-win32\nSSL Version => OpenSSL/1.0.2j\nZLib Version => 1.2.8\nlibSSH Version => libssh2/1.7.0</syntaxhighlight>\n",
+                                "\n",
+                                "When I tried to update to the current version 7.0.28 by simply overwriting files I saw:\n",
+                                "<syntaxhighlight lang=\"text\">Warning: PHP Startup: Unable to load dynamic library 'c:/php/ext\\php_curl.dll' - The specified module could not be found.\n in Unknown on line 0</syntaxhighlight>\n",
+                                "\n",
+                                "The mix of linux and windows slashes was a giveaway that v 7.0.12 doesn't seem to need to load php_curl.dll but 7.0.28 now needs that.\n",
+                                "\n",
+                                "So I fixed my php.ini but that just gave me:\n",
+                                "<syntaxhighlight lang=\"text\">Warning: PHP Startup: Unable to load dynamic library 'c:\\php\\ext\\php_curl.dll' - The specified module could not be found.\n in Unknown on line 0</syntaxhighlight>\n",
+                                "\n",
+                                "That file ''is'' found in that directory, so it's a kind of spurious / uninformative error message.\n",
+                                "\n",
+                                "Per the comments on [http://php.net/manual/en/function.curl-version.php the curl_version documentation page] I disabled the \"openssl\" extension in php.ini and confirmed that PHP v 7.0.12 and my application work fine without it. PHP cURL has nothing to do with that separated openssl extension but it has its own openssl.\n",
+                                "\n",
+                                "Perhaps I'm missing a dll file, as described in the [http://php.net/manual/en/curl.installation.php comments here three are needed] but I have all of those.\n",
+                                "\n",
+                                "Or are either my curl.exe or curl-ca-bundle.crt Security Certificate from June 2015 incompatible with PHP 7.0.28? They were still compatible with v 7.0.12 when I updated to that in October 2016.\n",
+                                "\n",
+                                "Help, please. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 15:36, 14 March 2018 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "15:36, 14 March 2018 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "SO I tried just retroactively updating from 7.0.12 to 7.0.13 ...\n",
+                                "<syntaxhighlight lang=\"text\">curl\n\ncURL support => enabled\ncURL Information => 7.51.0\nAge => 3\nFeatures\nAsynchDNS => Yes\nCharConv => No\nDebug => No\nGSS-Negotiate => No\nIDN => Yes\nIPv6 => Yes\nkrb4 => No\nLargefile => Yes\nlibz => Yes\nNTLM => Yes\nNTLMWB => No\nSPNEGO => Yes\nSSL => Yes\nSSPI => Yes\nTLS-SRP => No\nHTTP2 => No\nGSSAPI => No\nKERBEROS5 => Yes\nUNIX_SOCKETS => No\nPSL => No\nProtocols => dict, file, ftp, ftps, gopher, http, https, imap, imaps, ldap, pop3, pop3s, rtsp, scp, sftp, smtp, smtps, telnet, tftp\nHost => i386-pc-win32\nSSL Version => OpenSSL/1.0.2j\nZLib Version => 1.2.8\nlibSSH Version => libssh2/1.8.0</syntaxhighlight>\n",
+                                "\n",
+                                "Sometime between versions <s>7.0.14</s> 7.0.18 and <s>7.0.28</s> 7.0.21 some breaking change was introduced, and it's a bear to find any documentation of what that change was and how to fix installations to work with it. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 16:58, 14 March 2018 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ": binary searching for the culprit ;) [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:22, 14 March 2018 (UTC) narrowing in on it... [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 17:39, 14 March 2018 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [
+                                        {
+                                            "author": "Wbm1058",
+                                            "time_stamp": "17:39, 14 March 2018 (UTC)"
+                                        }
+                                    ],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "17:22, 14 March 2018 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "16:58, 14 March 2018 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                ": 7.0.18 is the last one that works out-of-the-box; [http://php.net/ChangeLog-7.php#7.0.19 7.0.19] introduced some sort of change requiring a change in configuration.\n",
+                                ": Added OpenSSL 1.1.0 support.\n",
+                                "Version 7.0.18:\n",
+                                "<syntaxhighlight lang=\"text\">curl\n\ncURL support => enabled\ncURL Information => 7.51.0\nAge => 3\nFeatures\nAsynchDNS => Yes\nCharConv => No\nDebug => No\nGSS-Negotiate => No\nIDN => Yes\nIPv6 => Yes\nkrb4 => No\nLargefile => Yes\nlibz => Yes\nNTLM => Yes\nNTLMWB => No\nSPNEGO => Yes\nSSL => Yes\nSSPI => Yes\nTLS-SRP => No\nHTTP2 => No\nGSSAPI => No\nKERBEROS5 => Yes\nUNIX_SOCKETS => No\nPSL => No\nProtocols => dict, file, ftp, ftps, gopher, http, https, imap, imaps, ldap, pop3, pop3s, rtsp, scp, sftp, smtp, smtps, telnet, tftp\nHost => i386-pc-win32\nSSL Version => OpenSSL/1.0.2k\nZLib Version => 1.2.8\nlibSSH Version => libssh2/1.8.0</syntaxhighlight> [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:21, 14 March 2018 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ": [http://php.net/manual/en/openssl.requirements.php Requirements] \"You are strongly encouraged to use the most recent OpenSSL version, otherwise your web server could be vulnerable to attack.\"\n",
+                                        ": 0.9.8 is a minimal version for PHP 7.0. Other versions (PHP >= 7.1.0) require OpenSSL >= 1.0.1. -- [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 18:52, 14 March 2018 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Wbm1058",
+                                    "time_stamp": "18:52, 14 March 2018 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "18:21, 14 March 2018 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "So I compared php-7.0.18-nts-Win32-VC14-x86 and php-7.0.19-nts-Win32-VC14-x86 and found that the former had 37 items, while the latter has 38. Bingo! The new file added to the package is nghttp2.dll -- so now there is a fourth DLL to be added to the \\php directory. Relatively few sites including this one as most discussions on this are stale, but I found one that mentions the latest DLL addition in the [https://superuser.com/questions/1201346/apache-and-php-curl-issue answer dated 31-October-2017]. It would be too easy if the spurious error message were actually truthful, and said:\n",
+                                "<syntaxhighlight lang=\"text\">Warning: PHP Startup: Unable to load dynamic library 'c:\\php\\nghttp2.dll' - The specified module could not be found.</syntaxhighlight>\n",
+                                "Of course no mention of the addition of this new file in the release notes. Sigh. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 00:24, 15 March 2018 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ": Your problems here seem to have nothing to do with MediaWiki. You should probably seek a help forum for PHP on Windows. [[User:Anomie|Anomie]] ([[User talk:Anomie|talk]]) 14:23, 16 March 2018 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                ":: Right, I solved this by myself. I could complain somewhere that their documentation of changes could be better, but I don't know where. [[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 21:14, 20 March 2018 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Wbm1058",
+                                            "time_stamp": "21:14, 20 March 2018 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Anomie",
+                                    "time_stamp": "14:23, 16 March 2018 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Wbm1058",
+                            "time_stamp": "00:24, 15 March 2018 (UTC)"
+                        },
+                        {
+                            "text_blocks": [
+                                "{{collapse bottom}}\n",
+                                "\n"
+                            ],
+                            "comments": [],
+                            "cosigners": []
+                        }
+                    ],
+                    "heading": " Updating from PHP version 7.0.12 to 7.0.28 "
+                }
+            ],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Bots ==\n",
+                        "\n",
+                        "\"API requests are now being forced redirected to HTTPS on some languages. On most bot frameworks, this should just work, but a few bot maintainers have reported problems. If your bot has problems, make sure that the library you are using supports HTTPS, and has access to appropriate root certificates.\"\n",
+                        "*How do you fix a library that doesn't support https to make it support that?\n",
+                        "*What are root certificates, and what do I need to do regarding that?\n",
+                        "*Why is this notice posted ''after'' implementation?\n",
+                        "*My library (see [[en:User:RMCD bot/botclasses.php]]) is something I got off of the now-defunct German tool server, and was written by guys who have all apparently retired from Wikipedia, so I guess I need to assume the job of maintaining it, though I'm not really sure that someone isn't still maintaining it somewhere.\n",
+                        "*I've been aware of this (potential) issue since last December: [[en:Wikipedia:Village pump (technical)/Archive 133#PHP API for #ifexist function?]] My [[en:special:diff/638797589|last question in that thread]] never got a response.\n",
+                        "[[User:Wbm1058|Wbm1058]] ([[User talk:Wbm1058|talk]]) 12:26, 14 June 2015 (UTC)\n"
+                    ],
+                    "comments": [],
+                    "cosigners": [],
+                    "author": "Wbm1058",
+                    "time_stamp": "12:26, 14 June 2015 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " Bots "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== HTTPS timeout with curl and wget ==\n",
+                        "\n",
+                        "Running these commands:\n",
+                        "\n",
+                        "*curl -s --trace o \"https://en.wikipedia.org/wiki/Charlies\"\n",
+                        "*wget -q -O- \"https://en.wikipedia.org/wiki/Charlies\"\n",
+                        "\n",
+                        "Results in intermittent timeouts as reported by the debug feature of both programs. It might work 3 times in a row then hang on the 4th etc..\n",
+                        "\n",
+                        "Traceroute shows I am located 10 hops from 208.80.154.224 in Virginia with a 6ms ping time with no dropped packets. I'm on Verizon FIOS. \n",
+                        "\n",
+                        "Problem started the same time HTTPS was implemented. \n",
+                        "\n",
+                        "curl debug (curl -s --trace o \"https://en.wikipedia.org/wiki/Charlies\"):\n",
+                        " == Info: timeout on name lookup is not supported\n",
+                        " == Info: About to connect() to en.wikipedia.org port 443 (#0)\n",
+                        " == Info:   Trying 208.80.154.224...\n",
+                        " == Info: Timed out\n",
+                        " == Info: couldn't connect to host\n",
+                        " == Info: Closing connection #0\n",
+                        "\n",
+                        "wget debug (wget -d -q -O- \"https://en.wikipedia.org/wiki/Charlies\"):\n",
+                        " Setting --quiet (quiet) to 1\n",
+                        " Setting --output-document (outputdocument) to -\n",
+                        " DEBUG output created by Wget 1.16.3 on cygwin.\n",
+                        " URI encoding = \u2018UTF-8\u2019\n",
+                        " Certificates loaded: 170\n",
+                        " Caching en.wikipedia.org => 208.80.154.224 2620:0:861:ed1a::1  <-- note: hangs here\n",
+                        " Closed fd 4\n",
+                        " Closed fd 4\n",
+                        " Releasing 0x800ce0c0 (new refcount 1).\n",
+                        "\n",
+                        "-- [[User:Green Cardamom|Green Cardamom]] ([[User talk:Green Cardamom|talk]]) 14:49, 17 June 2015 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "\n",
+                                "::In case anyone has similar timeout problems, I've worked around it with this:\n",
+                                "::: wget --retry-connrefused --waitretry=1 --read-timeout=2 --timeout=2 --no-dns-cache -q -O- \"https://en.wikipedia.org/wiki/Charlies\"\n",
+                                "::This is working. Might need to adjust the 2 second delay depending on your connection speed. If there is no response within 2 seconds (--timeout) It will retry 20 times .. but usually succeeds after the first retry. -- [[User:Green Cardamom|Green Cardamom]] ([[User talk:Green Cardamom|talk]]) 15:12, 17 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        ":::Ping: [[User:BBlack (WMF)]]. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 03:25, 18 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [
+                                        {
+                                            "text_blocks": [
+                                                "::::I don't think we're seeing this behavior in the general case (stats haven't shown it, and I can't reproduce it -- tried from a few places around the net over both v4 and v6).  If this wasn't a transient issue local to you that has since vanished, can you hop on our freenode #wikimedia-operations [https://meta.wikimedia.org/wiki/IRC/Channels IRC channel] to debug with us at some point? [[User:BBlack (WMF)|BBlack (WMF)]] ([[User talk:BBlack (WMF)|talk]]) 12:10, 18 June 2015 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "BBlack (WMF)",
+                                            "time_stamp": "12:10, 18 June 2015 (UTC)"
+                                        },
+                                        {
+                                            "text_blocks": [
+                                                ":::: Ping: [[User:Green Cardamom]] ^\n",
+                                                ":::: [[User:BBlack (WMF)|BBlack (WMF)]], it's working OK right now. I'll keep trying and if it starts happening again I'll get on IRC. Thanks. -- [[User:Green Cardamom|Green Cardamom]] ([[User talk:Green Cardamom|talk]]) 22:28, 18 June 2015 (UTC)\n"
+                                            ],
+                                            "comments": [],
+                                            "cosigners": [],
+                                            "author": "Green Cardamom",
+                                            "time_stamp": "22:28, 18 June 2015 (UTC)"
+                                        }
+                                    ],
+                                    "cosigners": [],
+                                    "author": "Bawolff",
+                                    "time_stamp": "03:25, 18 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "Green Cardamom",
+                            "time_stamp": "15:12, 17 June 2015 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Green Cardamom",
+                    "time_stamp": "14:49, 17 June 2015 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n"
+                    ],
+                    "comments": [],
+                    "cosigners": []
+                }
+            ],
+            "heading": " HTTPS timeout with curl and wget "
+        },
+        {
+            "subsections": [],
+            "comments": [
+                {
+                    "text_blocks": [
+                        "== Yes indeed, My code is broken! ==\n",
+                        "\n",
+                        "\n",
+                        "<br>\n",
+                        "I have written communication programs to fetch data from Wikipedia and the dictionarys.<br>\n",
+                        "(this was done in an environment that is called Cach\u00e9 or MUMPS: http://www.intersystems.com/our-products/cache/cache-overview)<br>\n",
+                        "I made them in order to have the possibility to check the contents on errors and much more.\n",
+                        "<br><br>\n",
+                        "Unfortunately they do not work anymore.\n",
+                        "\n",
+                        "Somebody made the following statement:\n",
+                        "For bot maintainers, you have a couple of choices. Either login as the bot and select the preference to not use HTTPS for that account, or update your code to use SSL instead.<br>\n",
+                        "How do I realise the preference to not use HTTPS for an account?\n",
+                        "\n",
+                        "Untill now I have tried a lot to fix it but I did not succeed...\n",
+                        "\n",
+                        "Saludos,\n",
+                        "\n",
+                        "--[[User:Kvdrgeus|Kvdrgeus]] ([[User talk:Kvdrgeus|talk]]) 07:16, 21 June 2015 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                "\n",
+                                ":Disabling HTTPS is not possible anymore. Your only option is to fix it to work with HTTPS in some way. - [[User:JanZerebecki|Jan Zerebecki]] 10:23, 21 June 2015 (UTC)\n"
+                            ],
+                            "comments": [
+                                {
+                                    "text_blocks": [
+                                        "::Hi [[User:Kvdrgeus|Kvdrgeus]], the bot problems are noted, I hope to be able to put together some relevant information specifically for this. Due to security concerns, we haven't been able to leave the option of opting out open. See [[:en:special:diff/666682303|here]] for a technical explanation. /[[User:Johan (WMF)|Johan (WMF)]] ([[User talk:Johan (WMF)|talk]]) 13:44, 22 June 2015 (UTC)\n"
+                                    ],
+                                    "comments": [],
+                                    "cosigners": [],
+                                    "author": "Johan (WMF)",
+                                    "time_stamp": "13:44, 22 June 2015 (UTC)"
+                                }
+                            ],
+                            "cosigners": [],
+                            "author": "JanZerebecki",
+                            "time_stamp": "10:23, 21 June 2015 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Kvdrgeus",
+                    "time_stamp": "07:16, 21 June 2015 (UTC)"
+                },
+                {
+                    "text_blocks": [
+                        "\n",
+                        "I finally did succeed in adapting the communication routines to the new TLS-protocols\n",
+                        "so this problem has been solved...\n",
+                        "\n",
+                        "--[[User:Kvdrgeus|Kvdrgeus]] ([[User talk:Kvdrgeus|talk]]) 12:43, 26 June 2015 (UTC)\n"
+                    ],
+                    "comments": [
+                        {
+                            "text_blocks": [
+                                ":Excellent, I'm glad to hear that. /[[User:Johan (WMF)|Johan (WMF)]] ([[User talk:Johan (WMF)|talk]]) 08:45, 1 July 2015 (UTC)\n"
+                            ],
+                            "comments": [],
+                            "cosigners": [],
+                            "author": "Johan (WMF)",
+                            "time_stamp": "08:45, 1 July 2015 (UTC)"
+                        }
+                    ],
+                    "cosigners": [],
+                    "author": "Kvdrgeus",
+                    "time_stamp": "12:43, 26 June 2015 (UTC)"
+                }
+            ],
+            "heading": " Yes indeed, My code is broken! "
+        }
+    ]
+}
\ No newline at end of file
diff --git a/src/lib/phab_get.py b/src/lib/phab_get.py
index 4993175..9f1220d 100644
--- a/src/lib/phab_get.py
+++ b/src/lib/phab_get.py
@@ -16,7 +16,7 @@ def query_task_tag(
     ts1 = None, ts2 = None,
     api_url_base = 'https://phabricator.wikimedia.org/api/maniphest.search',
     api_token = "api-wurg254ciq5uvfxlr4rszn5ynpy4",
-    sleep = 7
+    sleep = 10
 ):
     '''
     query all tasks tagged with specific tag
@@ -79,7 +79,7 @@ def query_transactions_phid_task(
     limit = 100, 
     api_url_base = 'https://phabricator.wikimedia.org/api/transaction.search',
     api_token = 'api-grocgdq2767cx6v5ywckkjmetx2f',
-    sleep = 7, 
+    sleep = 10, 
 ):
     '''
     query all transactions for a task (task_phid).
@@ -107,11 +107,14 @@ def query_transactions_phid_task(
             'after':after,
         }
         response = requests.get( api_url_base, params=params)
-        result = json.loads(response.text)['result']
+        try:
+            result = json.loads(response.text)['result']
+            data_tmp = result['data']
+            data += data_tmp
+        except json.decoder.JSONDecodeError as e:
+            data = {}
 
         ## the data
-        data_tmp = result['data']
-        data += data_tmp
         ## check if there are more results to query
         cursor = result['cursor']
         ## if after == None, no more queries
@@ -122,34 +125,75 @@ def query_transactions_phid_task(
             after = cursor['after']
     return data
 
+def query_users(
+    api_url_base = 'https://phabricator.wikimedia.org/api/user.search',
+    api_token = 'api-grocgdq2767cx6v5ywckkjmetx2f',
+    sleep = 10, 
+    limit = 100,
+):
+    time.sleep(sleep)
+    to_query = 1
+    after = None
+
+    data = []
+
+    while to_query == 1:
+        time.sleep(sleep)
+        params = {
+            'api.token'  : api_token,
+            'constraints[nameLike]':'WMF',
+            'limit':limit,
+            'after':after,
+        }
+        response = requests.get( api_url_base, params=params)
+        try:
+            result = json.loads(response.text)['result']
+            data_tmp = result['data']
+            data += data_tmp
+        except json.decoder.JSONDecodeError as e:
+            data = {}
+
+        ## the data
+        ## check if there are more results to query
+        cursor = result['cursor']
+        ## if after == None, no more queries
+        if cursor['after'] == None:
+            to_query = 0
+        ## if after != None, query next page by passing after-argument
+        else:
+            after = cursor['after']
+    return data
+
+
+
+
 if __name__ == "__main__":
     # phab=Phabricator("https://phabricator.wikimedia.org/")
     tags = [
-        "Parsoid",
-        "https"
+        "http"
     ]
+    tag = "http"
     #set phabricator api token
     token = "api-wurg254ciq5uvfxlr4rszn5ynpy4"
     api_base = 'https://phabricator.wikimedia.org/api/'
 
-    p_ts1 = int(datetime.datetime.timestamp(datetime.datetime(2022, 1, 1, 0, 0, 0)))
-    p_ts2 = int(datetime.datetime.timestamp(datetime.datetime(2024, 12, 31, 0, 0, 0)))
-    for tag in tags:
+    p_ts1 = int(datetime.datetime.timestamp(datetime.datetime(2014, 12, 1, 0, 0, 0)))
+    p_ts2 = int(datetime.datetime.timestamp(datetime.datetime(2015, 12, 31, 0, 0, 0)))
 
-        if tag == "https":
-            p_ts1 = int(datetime.datetime.timestamp(datetime.datetime(2013, 1, 1, 0, 0, 0)))
-            p_ts2 = int(datetime.datetime.timestamp(datetime.datetime(2016, 12, 31, 0, 0, 0)))            
-
-        p_data = query_task_tag(tag, ts1=p_ts1, ts2=p_ts2)
-
-        for entry in p_data:
-            task_id = entry['phid']
-            print(task_id)
-            transactions = query_transactions_phid_task(task_id)
-            comments = {}
-            for item in transactions:
-                comments[item['id']] = item['comments']
-            entry['task_comments'] = comments
-        DATA_PREFIX = "/data/users/mgaughan/mw-repo-lifecycles/phab_data/"
-        with open(f"{DATA_PREFIX}{tag}_phab_data.json", "w") as outfile1:
-            json.dump(p_data, outfile1)
+    p_data = query_task_tag(tag, ts1=p_ts1, ts2=p_ts2)
+    for entry in p_data:
+        task_id = entry['phid'] 
+        print(task_id)
+        transactions = query_transactions_phid_task(task_id)
+        comments = {}
+        for item in transactions:
+            comments[item['id']] = item['comments']
+        entry['task_comments'] = comments
+    DATA_PREFIX = "/data/users/mgaughan/mw-repo-lifecycles/phab_data/"
+    with open(f"{DATA_PREFIX}{tag}_2015_phab_data.json", "w") as outfile1:
+        json.dump(p_data, outfile1)
+    '''
+    user = query_users()
+    with open(f"022825_wmf_master_phab_roster.json", "w") as outfile1:
+        json.dump(user, outfile1)
+    '''
\ No newline at end of file
diff --git a/src/lib/wiki_get.py b/src/lib/wiki_get.py
index d9080ca..97d3196 100644
--- a/src/lib/wiki_get.py
+++ b/src/lib/wiki_get.py
@@ -115,23 +115,22 @@ def parse_tech_news(wikitext):
 
 if __name__ == "__main__":
     
-    dir_path = "/data/users/mgaughan/mw-repo-lifecycles/discussion_data/raw/ve-rfcs"
+    #dir_path = "/data/users/mgaughan/mw-repo-lifecycles/discussion_data/raw/ve-rfcs"
     #ve-rfcs
-    files = os.listdir(dir_path)
-    print(files)
+    #files = os.listdir(dir_path)
+    #print(files)
     #file_wikitext = read_file(dir_path + "/" + 'bnb-archive-8-raw.txt')
     #json_discussion = parse_talkpage2(file_wikitext)
+    '''
     for file in files: 
         print(file)
         file_wikitext = read_file(dir_path + "/" + file)
         json_discussion = parse_talkpage2(file_wikitext)
         json_it(json_discussion, "/data/users/mgaughan/mw-repo-lifecycles/discussion_data/visualeditor/" + file.split(".")[0] + ".json")
     '''
-    file_wikitext = read_file("/data/users/mgaughan/mw-repo-lifecycles/discussion_data/raw/tech-news/tech-news-2022.txt")
-    json_discussion = parse_tech_news(file_wikitext)
-    print(json_discussion)
+    file_wikitext = read_file("/data/users/mgaughan/mw-repo-lifecycles/discussion_data/raw/https-talk-raw.txt")
+    json_discussion = parse_talkpage2(file_wikitext)
     json_it(json_discussion, "test.json")
     #json_discussion = parse_talkpage(file_wikitext)
     #json_it(json_discussion, "/data/users/mgaughan/mw-repo-lifecycles/discussion_data/parsoid/parsoid-talk-archive-2.json")
-    '''
     
\ No newline at end of file